Using the UAGateway with an OPC UA server to give connectivity to Wonderware Intouch through FSGateway
That is
Intouch --> FSGateway --> (UAGateway --> OPC UA Server) --> SCADA application
We can read data from the application but the write fails when FSGateway tries to write to UAGateway. We've trialled Gateway/Wrapper products from other software companies & it has worked. However we do have a preference to use the UA product as our OPC UA Server is built on the UA toolkit.
Intouch - FSGateway can't write data
Moderator: uagateway
-
Support Team
- Hero Member
- Posts: 3068
- Joined: 18 Mar 2011, 15:09
Re: Intouch - FSGateway can't write data
Hello,
Could you please activate the trace functionality in the administration dialog of the UaGateway and send us the recorded trace file to support@unifiedautomation.com?
Best regards
Support Team
Could you please activate the trace functionality in the administration dialog of the UaGateway and send us the recorded trace file to support@unifiedautomation.com?
Best regards
Support Team
-
ghallibu
- Jr. Member
- Posts: 3
- Joined: 23 Nov 2015, 22:14
Re: Intouch - FSGateway can't write data
Hi,
thanks for the timely reply. For your information, below are our details for the OPC UA Server toolkit. Attached is the trace file. Data is read OK through the gateway. I did a write from Intouch which failed (5 retries)
You have access to:
Net based OPC UA Client Server SDK (Bundle) (Win32) Standard Support.
Account information removed to protect your privacy.
thanks for the timely reply. For your information, below are our details for the OPC UA Server toolkit. Attached is the trace file. Data is read OK through the gateway. I did a write from Intouch which failed (5 retries)
You have access to:
Net based OPC UA Client Server SDK (Bundle) (Win32) Standard Support.
Account information removed to protect your privacy.
-
Support Team
- Hero Member
- Posts: 3068
- Joined: 18 Mar 2011, 15:09
Re: Intouch - FSGateway can't write data
Hi,
COM OPC DA allows automatic conversions of data types in the server. This caused a lot of problems for language specific conversion between string and floating point values / date time values. Therefore OPC UA requires that a client writes the right data type and UaGateway must do the right conversion before forwarding the write value to the OPC UA server.
This conversion fails for abstract types. Therefore the write fails at the moment.
We have changed the behavior in UaGateway to skip the conversion for abstract types. The next version 1.4 that is currently in testing will provide this change.
But this requires that the client writes a value with a data type that is accepted by the OPC UA Server. We cannot solve this limitation of COM OPC DA completely in UaGateway. But the client has now a chance to write the right data type and to get the write working.
Best Regards,
Unified Automation Support Team
COM OPC DA allows automatic conversions of data types in the server. This caused a lot of problems for language specific conversion between string and floating point values / date time values. Therefore OPC UA requires that a client writes the right data type and UaGateway must do the right conversion before forwarding the write value to the OPC UA server.
This conversion fails for abstract types. Therefore the write fails at the moment.
We have changed the behavior in UaGateway to skip the conversion for abstract types. The next version 1.4 that is currently in testing will provide this change.
But this requires that the client writes a value with a data type that is accepted by the OPC UA Server. We cannot solve this limitation of COM OPC DA completely in UaGateway. But the client has now a chance to write the right data type and to get the write working.
Best Regards,
Unified Automation Support Team