Hi All,
This may also belong in the Labview forum, but I figured I should start here, since I think the issue is outside of Labview. We have a TC-32 that we are using in an automated test system, being run by a Labview application. Our application keeps crashing intermittently and we get the following error message:
Error 1024 occurred at Measurement.lvlibp:ULx Read (Analog 1D DBL NChan 1Samp).vi
Possible reason(s):
Network device already in use by another process.
This happens very intermittently, and no one is opening Instacal or doing anything on the computer when this happens.
I was poking around in Instacal to check config settings and test the TC32, when all of a sudden it stopped responding, and Instacal displayed the same error message: "Network device already in use by another process." I closed Instacal, but the "Activity" light on the TC32 remained on, as if it was still talking to something. When I reopened, Instacal, I could no longer talk to the device, and kept getting the same error message: "Network device already in use by another process." Power cycled everything, and it went back to normal, but I can't help but feel that it was the same issue that's causing our application to crash.
The TC32 is on a local network with a few other instruments and a PC that runs the application. Everything on the local network has static IP addresses, so shouldn't be any issues with something "stealing" the IP address of the TC32. Does anyone know what other process could be talking to the TC32 and interrupting comms? Can anything other than Instacal and the Labview ULx libraries talk to these instruments? Any ideas on what I could try next to make these comms issues stop? Like I said, the issue is very intermittent, so very hard to debug.
Thank You!