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.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- omron opc reading and writing variables
omron opc reading and writing variables
What I was looking for was the datatype the server reports about that variable. Without having to wait for version 2022.2, can you run a small program similar to opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...d%20DataType%20attributes.html (change it t your server, and to the one NodeID you are dealing with - you do not need three variables as in the example). Notice that the program asks for the value of the UAAttributeId.DataType attribute and not the the default UAAttributeId.Value attribute.
Best regards
Please Log in or Create an account to join the conversation.
OpcLabs.EasyOpc.UA.OperationModel.UAException: An OPC-UA operation failure with error ID 'Opc.UA.ServiceResult=0x80740000' occurred, originating from 'OpcLabs.EasyOpcUA' and with depth of 1. The inner OPC-UA service exception with service result 'BadTypeMismatch' contains details about the problem. ---> OpcLabs.EasyOpc.UA.UAServiceException: OPC UA service result - {BadTypeMismatch}. The value supplied for the attribute is not of the same type as the attribute's value.
+ The attribute Id used was 'Value'.
+ The node descriptor used was: NodeId="nsu=http://Rxx5/UA ;ns=4;i=1168".
+ The client method called (or event/callback invoked) was 'WriteMultiple[1]'.
--- Fine della traccia dello stack dell'eccezione interna ---
in OpcLabs.EasyOpc.UA.IEasyUAClientExtension.WriteValue(IEasyUAClient client, UAWriteValueArguments writeValueArguments)
in OpcLabs.EasyOpc.UA.IEasyUAClientExtension.WriteValue(IEasyUAClient client, UAEndpointDescriptor endpointDescriptor, UANodeDescriptor nodeDescriptor, Object value, Type valueType)
in OpcLabs.EasyOpc.UA.IEasyUAClientExtension.WriteValue(IEasyUAClient client, UAEndpointDescriptor endpointDescriptor, UANodeDescriptor nodeDescriptor, Object value)
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
So what I meant was to upgrade the library, primarily.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
The error message looks like from some older product version. In recent versions, we have enhanced it to contain more information needed to troubleshoot this kind of problem.
Which version are you using? (Help -> About)
Regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- omron opc reading and writing variables