Hello,
we use WinCCOA V3.12 P022
If the functions like dpQeryConnect are called for a REMOTE system, that system must be connected at that moment, otherwise the connect will raise an error - No Such Remote system.
If this dpQueryConnect is used in control manager and connection is lost or not yet established to system specified in dpQeryConnect, this manager will crash - stop working.
This control manager will not start working by itself after connection to specified system is established.
Is there any way to prevent this manager to stop working?
Thank in advance,
Vedad Ramovic
dpQuery on REMOTE system throws an error when remote system is not connected
- vedadramovic
- Posts:121
- Joined: Mon Apr 07, 2014 10:36 am
dpQuery on REMOTE system throws an error when remote system is not connected
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: dpQuery on REMOTE system throws an error when remote system is not connected
Perhaps you could try a 'REMOTE ALL' dpQueryConnect and limit it with the '_SYS' keyword.
Otherwise you could connect/dpWaitForValue to the '_DistConnections' datapoint and wait until the right system is online before you execute the dpQueryConnect.
Otherwise you could connect/dpWaitForValue to the '_DistConnections' datapoint and wait until the right system is online before you execute the dpQueryConnect.
- vedadramovic
- Posts:121
- Joined: Mon Apr 07, 2014 10:36 am
Re: dpQuery on REMOTE system throws an error when remote system is not connected
Thank you Gertjan very much.