Hello Bjorn,
I didn't wanted to mention in my first reply as I don't think it a problem in your case, but one of the more common problems we encounter with Datasocket is that the network port used for Datasocket data transfer is often blocked on company networks. Datasocket uses port 3015, so please verify this port is open on your network.
I don't know the Softing application and if it uses the same network port for data data communication. I can't find the answer on the internet.
With the current available information it's very difficult to troubleshoot your problem. Can you post your VI so we can have a look?
If it includes custom Sub-VI's, please make a ZIP of all VI's.
I don't know if you added error handling in your application.
Without error handling it may happen that your application goes to the next step although no data was received.or an error occured.
What can happen for example.
Although Ethernet can transfer data at a reasonable speed, it has a high latency. This means that it takes a while before you receive an answer (data) after you did a request (read). I did some tests and a latency of 200ms was no exeption. So if I set a timeout of smaller than 200ms my application could, whithout error handling, simply go to the next step and return no data. Have a look at the default value of the timeout inputs of the Datasockets functions in LabVIEW, that's defaulting to 10 seconds.
Just a thought, but please if possible send us your VI so we can have a look at it.
Best regards,
Joeri
National Instruments
Servicesg