Datasocket write and close / remote OPC server / PC freeze when no connection

Question

[Labview 8.21, Windows XP SP2]
Hello
I am getting data from a remote OPC server using the Datasocket techniques. Depending on the DS family of routine that I use the behavior is different when the OPC server shuts down or Ethernet link is cut.
In the NOK application attached, as soon as the link to the OPC server is cut the application and the whole Labview environment gets stalled, either in the DS Write or in the DS Close icon. Never in the DS Read icon.
Also the Timeout to read or write does not work in neither application. Whatever the number I set it will never be taken into account.
Is there some sort of 'miracle' setting in the Labview.ini file that can make the NOK application to work correctly and step out of the DS Write or Close vi when such link cut occur? More generally could someone explain why the behavior is different between the two applications, if there are new Datasocket routines that would handle these kind of communication in a clean way?
Thanks
Christophe
Attachments:
Datasocket - OK version.vi ‏19 KB
Datasocket - NOK version.vi ‏19 KB

Answer 1

I am desesperate. The Datasocket - OK version.vi 19 KB that seemed to work so well (no freeze at all) creates a huge memory leakage as you can see in the attached file. I am only reading a tag (local OPC tag, not even remote tag on another PC's OPC server) and the word document attached shows the issue:
After 15-20min during which no increase of memory is noticed (first picture) the situation starts to worsen. In 12 hours (about 7200 read operations) it reaches a consumption of 65Mb ! (to read everytime the same OPC tag). Something that I never noticed with the Datasocket - NOK version.vi 19 KB that had the freezing issue...
I really do not know what to do.
Thanks for your prompt feedback
Christophe
Attachments:
Benchmark Datasokets.vi ‏38 KB
Benchmark Datasocket Memory Consumption.doc ‏392 KB