dpConnect status for dist systems

[tpjctrl]

When a dpConnect is made to a dp in a dist location, it automatically goes to "sleep" when that dist location disconnects, when it comes back up online, the dpConnect will get re-initalised and becomes live again. Is there a way to somehow read the status of all dpConnects configured in the entire system (or even for selected dps?) so that I know which one is "disconnected" and which is alive and running?

[leoknipp]

A dpConnect() is still valid, even if the dist connection is lost.
The automatic refresh of connects when the connection is reestablished is a feature of WinCC OA.
If you want to give the user the information if a value for a distributed system is reliable you probably can display the information for the connected systems or for the specific system used at the dpConnect().

Best Regards
Leopold Knipp
Senior Support Specialist

[gschijndel]

You could add a dpe which always is in the good state like for example '<REMOTE_SYSTEM>:_Event.Heartbeat:_online.._bad'.
If the callback is called with TRUE for that dpe then the system is not connected anymore.

[tpjctrl]

Thanks for the replies, I already have a dist system monitor which I use for setting up dpconnects, so I can keep track of status using that.

It's interesting however that if you want to do a dpDisconnect for a dist system which just disconnected, it will throw an error saying that the argument is invalid, which on one hand makes sense, on the other, doesn't, based on your comment re dpConnect's staying valid forever.

[leoknipp]

I have tested it and the dpDisconnect() is executed without any errors, even if the distributed system is currently not connected.
Does the dpConnect()/dpDisconnect() in your script work while the system is connected?

Please take into account that the dpDisconnect() must be executed in the same script which did the dpConnect().

Best Regards
Leopold Knipp
Senior Support Specialist