Hello All,
I have an application where I am using two cDAQ-9188 chassis and one custom (non-NI) module, all of which are on the same network.
The network has only four nodes, the PC and the three devices.
The custom module is a measurement module which has a non-LabVIEW API which is invoked in LabVIEW via a DLL.
When I communicate with the custom module via a LabVIEW VI it works perfectly fine. However, if I have a DAQmx call in a separate loop within the same LabVIEW VI, I get occasional timeout errors on the custom module calls.
Like I said before, there are no other nodes on this network, and the overall network utilization is very low (less than 1%) even when acquiring data via the 9188 chassis.
I have temporarily solved the problem by moving the custom module to a separate network controller on the PC. Keeping the module and NI-DAQ on separate networks makes the problem go away completely. However, I'd like to get back to the point where they are all on the same network. Has anyone run into a similar problem before? I am assuming it is parallel calls for the Network Adapter from the VI at the same time. I am wondering if it is because the custom module API is not written in LabVIEW. If I replaced the API with TCP calls using the built-in TCP VI's within LabVIEW, would you expect the results to be different? (i.e. - since the TCP calls are in LabVIEW the runtime would handle the calls appropriately along with the DAQmx calls for similar resources, rather than in my case where the runtime is just calling a DLL and doesn't necessarily know what the DLL is going to do?)
Hopefully I've provided adequate detail. I am unable to post example code, but would be happy to clarify if anyone has any additional questions.
Thanks!
