Professional OPC
Development Tools


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.

Automatic reconnect after OpcException

08 Mar 2012 10:36 #788 by support
After a server is disconnected in an unwanted way, our component reconnects - but not immediately, but after a delay. The delay depends on the kind of problem detected, and there are currently three of them:

ServerFailedReconnectDelay (defaults to 1 minute) - when the OPC Server indicates through OPC functions that it has failed.
ServerShutdownReconnectDelay (defaults to 1 minute) - when the OPC Server wants to shutdown and has asked its OPC clients to disconnect.
ClientReconnectDelay (defaults to 1 minute) - in all other cases, when the connection is detected "dead".

So, in default configuration, after 1 minute, you should get your live data back. The delays are configurable via properties on the object.
I can theoretically imagine a situation in which the connection to the server is not fully "lost" but somehow damaged, leading to a situation in which we do not consider the connection "dead", and still attempt to work with it. If this is the case, and you never get the connection back until you restart the service, we will have to investigate further. For start, we will need to know the precise exceptions you are receiving.
BTW, we never generate or change Qualities. Connection (or other) problems detected in the component are indicated via Exceptions, either thrown or passed as an object. If you are seeing bad qualities, then they are coming from the OPC server itself. The fact that you mention Bad quality is actually suspicious, and indicates something on the server side as well.

Please Log in or Create an account to join the conversation.

08 Mar 2012 08:43 #785 by DKahlert
we are using the Library as part of a Windows-Service for reading OPC-Data via a VPN-connection. This connection is not very stable and crashs once or twice a day. After the VPN-connection is recreated by the Service (needs 5 to 10 seconds), we still get OpcExceptions (with several HRESULT-values) or bad quality-values. If we start the Demo-Client in parallel, everything is ok - for the client, the Windows-Service has still problems until we restart the app. So what's the fastest way to get a proper reconnect?
Thanks in advanced.

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.050 seconds