Replies: 1 comment 1 reply
-
That is part of OPC UA 1.04 which is not currently implemented. I "stole" these handful of built-in structs related to defining structures from 1.04 but otherwise Milo currently implements 1.03, so there is no definition attribute on DataType Node at the moment (it is defined as an attribute by OPC UA 1.04, not a separate Property Node). I think what you are asking will not technically be possible until I start implementing OPC UA 1.04 in version 2.0 of the library (work will begin soon). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello @kevinherron,
is it planned that by creation of custom DataTypes the
DataTypeDefinition
attribute will be added to theDataType Node
?If not what is the simplest way to add this attribute yourself during the creation of namespace (if it is possible)?
I mean the API access to the
UaDataTypeNode
for callingsetProperty()
-method (since in the constant for DataTypeDefinition-attribute isn't defined in the AttributeId-class). Then I can use thegetPropertyNodeAsync()
-method on the client side for reading it. Please correct me if I'm wrong with usage of methods.It would be nice if the DataTypeDictionary (or even DefaultDataTypeManager) will have some API for getting
TypeDescription
for custom DataTypes (currently I use the modified version ofDataTypeDictionaryReader
in the modifed version ofDataTypeDictionarySessionInitializer
for collecting this info since I need the info aboutFieldType
's of the customStructuredType
's).Thanks in advance for your answer
Beta Was this translation helpful? Give feedback.
All reactions