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.
- Forum
- Discussions
- QuickOPC-Classic in COM
- Connections, Reconnections, COM/DCOM
- Random Disconnect from OPC server
Random Disconnect from OPC server
Can you please figure out whether the EASYOPCL process is running at (=right after) the time the errors occur.
And, what OPC server are you connecting to, and is it a local or remote connection? Are there other OPC clients connecting to it?
Thank you
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
With setting Isolated = True form all services, we would create 6 separate connections to the OPC server, which means somewhat higher load.
But, unless we are speaking of large number of variables changing very quickly, the differences should not matter. What are you numbers?
The reason I am asking to watch for the presence of EASYOPL process is because I want to determine whether it has "fully" crashed (and terminated), or just stopped responding.
Best regards
Please Log in or Create an account to join the conversation.
I went with this approach (6 services) because for this application there are six separate operations that all require their own high priority for heartbeating and performing handshakes with the PLC. Would it be better to have one service that is subscribed to all the heartbeats and handshaking for all operations? Logically I guess that never made much sense to me so I didn't give it any thought. I'd like to hear what you think though.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Thank you
Please Log in or Create an account to join the conversation.
All the services crashed in about 3 hours with this error when writing one bit:
exception 'com_exception' with message 'Error [0x800706be] The remote procedure call failed
I've done what you recommended to do earlier, but it doesn't look like it has solved the problem.
Please Log in or Create an account to join the conversation.
However, now the heartbeat seems so slow. The heartbeat I am doing with the PLC is the PLC increments an integer tag that I'm subscribed to. On change I simply set a different integer tag equal to what the PLC set. I'm noticing that sometimes after the PLC changes, it takes sometimes 3 seconds for the other tag to update.
Is this Isolated mode causing performance issues? Is there a setting in the EasyOpc Options to make this more responsive?
Please Log in or Create an account to join the conversation.
What I meant by using two separate objects was that instead of using $opcSender for "WriteItemValue" call, you would use a separate, second EasyDAClient, which you will keep just for the purpose of operations done form inside the "item changed" event handlers. And, set its Isolated to 'true'.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in COM
- Connections, Reconnections, COM/DCOM
- Random Disconnect from OPC server