I have several DAQmx tasks executing on a 9188 cDAQ ethernet chassis (LabVIEW 2011, latest drivers). Everything will be running fine for hours, and I will get a -201388 "Network device not reserved for this host" error from all of my running tasks. The only other devices on this private network are an ENET-232 (I'm talking with one serial device) and a PLC (which I am communicating with over TCP Modbus). There are no other PCs on the network. This has happened at least a dozen times, after running for hours or days without a problem. After going in to MAX and re-reserving and sometimes resetting the cDAQ everything works again. What could possibly cause the cDAQ to become unreserved? On one occassion my Modbus communication stopped working. As soon as I unreserved the cDAQ chassis it started working again. What could cause this to happen? What protocol is the cDAQ using to send its data back to the host? How could this be conflicting with my Modbus TCP communication and could this somehow be the cause of the chassis becoming unreserved?

Multifunction DAQ

The update does not solve my problem

My application is running on a ship wkere we have eveary night for 2 minutes a hadware reset from the router

So when the router is back I have to reconnect to my chassie

Jürgen

Message 11 of 11

(1,314 Views)