- Posts: 31
- Thank you received: 0
Online Forums
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.
Opc Ua ExtensionObject
Please Log in or Create an account to join the conversation.
More information:
- QuickOPC 2018.1 Released
- What's New in QuickOPC 2018.1
- OPC UA Complex Data Extension
- OPC UA Complex Data Reading
Best regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Next to that I will try to construct such an ExtensionObject from scratch in C# and send it. I'll keep you posted.
BR,
Carsten Voort
Please Log in or Create an account to join the conversation.
BR,
Carsten Voort
Please Log in or Create an account to join the conversation.
If so, and you then pass the extension object(s) to QuickOPC EasyUAClient.WriteXXXX method, things *may* work but we have never tested that. If you run into issues, let me know.
Please Log in or Create an account to join the conversation.
I assume I can also use the Opc.Ua.Core to write to the opc structures?
Please Log in or Create an account to join the conversation.
You may also be interested in knowing that you actually need these assemblies only during build time, and not in run time. Copies of them are inside OpcLabs.EasyOpcUA assembly and will be used during run-time automatically, if not found on disk.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
What I did, on your advice, is using reflection. I figured out that I needed runtime reflection, so TypeDescriptor.GetProperties() from the System.ComponentModel. Indeed I can find the "Body" property now.
Thanks for now!
BR,
Carsten
Please Log in or Create an account to join the conversation.