Update the OPC DA Service Provider status.......
Hi,
I have interfaced flow metering computers to 800xA(Test configuration)...I used OPCUA tunnel....I have OPCUAServer(Kepserver) running on both connectivity servers.....OPC UA client(3rd party machine) providing data to OPC UA server......configuration is working....I have uploaded the data to the 800xA network using the OPCUA server on connectivity server.....Now I have one problem....even I lost the connection to the 3rd party machine.....my service provider is always in service state....?
How I can make the service state to something different(Initializing) when I lost the connection...?
Any idea?
Answers
More importantly, does the status for the OPC data go to "Bad" when the remote OPC server shuts down ?
The OPC DA service state depends on whether the Kepware tunneller is running properly. If the tunneller reports that it is healthy when the third party OPC server is down, theres not really much that you can do - the OPC DA Service is correctly reporting that it has sucessfully connected to an OPC Server. However, the KepWare tunneller should report that the OPC data is bad.
If only one tunneller reports bad data, the 800xA service group should still fail over to the good values. So the service not going into failure state should not matter as long as the OPC quality is correctly reported by the tunneller software.
I agree with Rob's answer and would like to add two more things (item 1 + 3 below).
1. System 800xA does not support OPC UA (yet). I believe your 800xA system and external OPC server/tunnel server has negotiated an OPC v2.05A connection (the version supported by 800xA).
2. The OPC server must not set "good" quality on an item where data is not available.
3. The OPC server must not issue "OPC_STATUS_RUNNING" when it is not.
Both item 2) and 3) are easy to test with the built-in 800xA OPC client test tool; advdsopcclient.
When 2) fail properly designed graphics will show error indication, e.g. a red cross
When 3) fail, the OPC DA Connect service provider will abort, restart and remain in synchronizing state until the OPC server reports a healthy state. Service providers in non-service state will be ignored by clients. Lack of any server in service state will result in bad quality indication (item 2 above).
Add new comment