My OPC client app hangs when the OPC server dissapears from the net

[bere]

Ok.
I used to purchase National Instruments products through the Internet but I had in the past some contacts with the local support. I do not remember the names.
The information of my company is:
My name: Bernardo Baranek
Company: Ponis SA
Address: M Rodriguez 2233
City: Ciudad de Buenos Aires
Country: Argentina
Zip: 1416
Phone: 5411-4585-0900
Fax: 5411-4585-6693
email: bbaranek@ponis.com.ar

I hope you can find the right person.

Thank you and best regards

Bernardo

[bere]

I am sorry to say nobody contacted me regarding to this problem. Is there anything to do ?

Bernardo

[CFritz]

Hi Bernardo

I heard about a fault in the nids.dll. There is a new version 4.1.2.107. If you have an old one this could be a solution. Ask the NI support for a new version

[Mads]

We have the same isue now in LV 7.1.

Is this really the situation, or has anyone got this working now?

I do not understand how NI can leave such a critical bug alive if they knew about it even back in 2002...It makes data socket practically worthless when it comes to OPC.

[shahina]

Hello Mads,

We are aware of this issue and it is being addressed by our developers in R&D. This problem will be resolved in future releases of LabVIEW. We appreciate your feedback and patience on this.

Best regards,
Shakhina P.
Applications Engineer
National Instruments

[zmilet]

Hello there,

Where can I find any news about this issue?

This have been a serious problem for our customers for 2 years. I never thought that this could be a labview issue until I found this thread.

Best Regards

[TheDillo]

This is a known issue in LV 7.1 - to get this taken care of you can call us up and we can send you a new nids.dll file.  This is fixed in the newest version of LabVIEW, verison 8.20.

[Titor2]

Hello,

I am developing an application in LV 8.2.   If I the OPC server computer is available on the network,  the application connects with no problems and starts reading/writing.  If the connection to the server is lost either before starting the application and open the Datasocket connection or when read/write operations are running, the application will hang for minutes before reporting any error.  

Based on the KB http://digital.ni.com/public.nsf/allkb/c94e75af6deb344486256f59001b4f7b , I explored the lower level VIs at C:\Program Files\National Instruments\Labview xxx\vi.lib\platform\dataskt.llb  

I replaced the high level VI 'Datasocket Open.vi' from the pallete with the Lower lever 'Datasocket Open Connection.vi' from the library mentioned above.  Below the hierachy, there is a VI called 'Datasocket Connect.vi" (see pictured attached) which is calling a Component Works Datasocket Method from a DLL. After testing with and without connection, this is the VI that is hanging or freezing the application.  As can be seen at the block diagram picture (attached), no timeout input is available.

This makes me believe that there is no hope to handle Communications errors properly with datasocket.

I would appreciate any advise on this.

Thanks a lot

Art
 

[AdnanZ]

Hi Art,

I hope you are doing well today! Is it possible for you to edit the block diagram? If you use our Error Handler VIs, do you see an error being generated?

[stalky]

Hi I have the ssame problem, the INIDSCtl Connect to method hangs for minutes if it does not find the connection and it is not possible to do nothing. I use Labview 7 and it is not possible for the moment to migrate to new version (the applocation is quite big).  I've read here that it may be fixed with a new version of nids.dll. May someone know where I may find it e which version I have to install?
Thanks in advance