LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

crashes in combination with datasocket

Hi All

I have some stragnge bahavior in Labview 8.5.1 in combination with datasocketes. I have written a set of objects to handle OPC variables using DataSocket Labview objects. Things run fine until I start changing my app. When I change my code (not even my custom OPC datasocket objects), sometimes LV crashes. All LV VIs and other windows close and LV is completly gone (windows is still fine). When I open an application which was running fine before at this point and run it, it crashes the same way as the failing one. To resolve, I have to delete and recreate a wire which connects to every datasocket object (datasocket open, datasocket read, datasocket write and datasocket close). Once I have redone those wires, my application works fine, until the next such crash happens. Unfortunately, this happens so frequent, while developing that it gets unusable.

I'm accessing a Siemens OPC server.

I have done an other approach using an OPC DA auto ActiveX and this seems to be much more stable, however, I was not able to get the DataChanged callback functionality to work and therefore I would have to do a constant polling of the OPC data, which I don't like.

Any help would be grat.

regardes,

Herbert
Download All
0 Kudos
Message 1 of 3
(2,427 Views)
Hi Herbert,
 
which changes in code are you doing before LV crashes? How long does it takes before LV crashes when running the VI. I think using the shared variable instead of DataSocket won't make LabVIEW to crash.  
 
Best regards
Rüdiger
0 Kudos
Message 2 of 3
(2,365 Views)
Hi Rüdiger

Thanks for your answer!

The changes can be basically anywhere which is just "close" to where my objects are used and the error happens when the the DS object executes.

I have contacted NI support and they were able to reproduce the problem. The conclusion was that the DataSocket objects do not work correctly in dynamic class VIs. They also found that with LV 8.6, which is not yet released, the problem does no longer exist. That probably means it is an other bug in the dataSocket tools. Meanwhile I have rewritten the whole thing to use an ActiveX element which provides access to the OPC server I'm accessing.

Regards,

Herbert
0 Kudos
Message 3 of 3
(2,357 Views)