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.
Working wery slow
There are, however, strange symptoms leading to a possibility that the use of the analyzer won't be of much help. Specifically
a) The fact that you claim that the problem is "... blocking all other threads in the program.". I can't understand how a bug in the client component could cause this. Normally when an operation blocks, it is just the one thread that is affected.
What are the other threads in your app doing?
b) We have a timeout (default to 60 seconds), so even if the server does not respond, the method should return much faster - and not in a time that exceeds 1 hour.
The reason I think it is the client is that my costumer uses a Beijer Electronic OPC server for connecting to a Siemens step 7.
I do not have this equipment so I use a NapOPC server from IPC-DAS fro controling a Wise module.
In both cases we see that after 1 hour 40 minutes and 50 sec (take or leave 5 sec) the system is hanging in the write function.
If a read function is executed before write function, we see no problem other than the extra time used.
I can try to run the analyzer. But it is a long time before tha failure somes.
best regards René
Is there something that leads you to belief that the problem is rather on the client side?
The program is hanging in the write function and blocking all other threds in the program.
As I wrote before I have found a workaround by first reading the register and then write to the register.
Doing it this way I have no problems, besides the time used for reading.
best regards René
If I read theitem before I write every thing is working fine.
Not sure of version. Have QuickOPC-5.32 and use EasyDAClient.
No loss of memory. Computer reboot before it can run again.
Client and server on same computer.
Do not have another client but can access the OPCserver by webinterface. No problem.
1. Are you using OPC "Classic" or OPC UA ?
2. Is your application also using subscriptions?
3. Are you observing some memory or CPU consumption increase on the server side?
4. Are you observing some memory or CPU consumption increase on the client side?
5. If you stop the client and restart it, does it resolve the issue?
6. If you connect a different client at the time your application is showing the slowness symptoms, is the other client working fine, or does it also show the slowness?
7. Is the server and the client on the same machine ?
I have got a problem.
After running my program using OPC the system gets so slow, but program stil run.
And every time it is a write command and it happens after 1 hour 40 minutes and 50 seconds.
And I have tried against different OPC servers.
Anybody seen same behavior.