Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
Call method with NodeId as input parm
I have sent you my email contact to the email address you have used for registration wit the forums, for confidential parts of the conversation.
this specification comes from Bruderer specification.
They said us that the kind of interface regarding the job management is learned from euromap 83 and it is just adapted to stamping machines.
They also said that the attribute of the method "SetContinuousJobData" is of a complex data type who is defined in the type dictionary of the opc-ua interface.
If you want, I can send you (with a private message) the complete specification from the producer (Bruderer) who provide our custemer the OPC-UA server.
The tables you provided look like they come from (or are related to) the EUROMAP 83 spec.
But, the data passed to a method cannot be a UA *type* (such as the ContinuousJobInformationType). It must be a UA "data type*, which is quite different thing.
The signature of the SetContinuousJobData method makes no sense to me, in context of OPC UA, because it uses a type and not a data type. Where does that come from?
I am somewhat confused here. What is it that is not clear? Node ID is a very basic concept in OPC UA. You must already be working with node IDs practically everywhere. NodeId consists of a namespace (which as integer on the wire, for efficiency, but "logically" it is a URI), and of an identifier (integer, string, GUID or opaque). See e.g. opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...tml#OPC%20UA%20Node%20IDs.html .
The only different thing here is that, at least in my understanding, you have a method that requires an input argument that is actually of type NodeId . But you still need to construct the NodeId as you would elsewhere, it is the *same* thing. So, it has properties like NamespaceIndex, NamespaceUri, StringIdentifier - pick the ones you need/have, and set them .
(Note: I do not understand at all how the table (image) you have attached relates to this issue. It does not describe anything about the NodeID).
Does this help?
this should be possible by passing in a value that is an object of type UANodeId. So you would create this object and set its properties as needed first, and then send it to the "write".
Let me know if it does not work or if you need further help with it.