NI cDAQ-9184 Connection Issues

[eLAB_RAT]

I am working on a network with multiple computers, but only one that had LabVIEW and NI MAX installed. I am making a program that can write to NI 9482 which is mounted on NI cDAQ-9184. On the computer with LabVIEW and NI MAX, I made sure to unreserve the network device and make sure that the program does the reservation itself, I am able to run a successful self-Test, and my program works as intended.

My issue lies with trying to install this program on other computers in the network. I created an executable, then an installer that I made sure had all of the required additional installers and the Hardware configuration file. But when I install and run my program I get Error -88705, that the device is not present in the system. So I checked NI MAX which was installed with my program installer, and I found that the device shows up and the status is "Connected - Running" although it says the device is not reachable. The self test also fails.

What can I do to be able to communicate with the devices from any computer on the network?

Thank you.

[Kyle97330]

More information would be helpful here.

I suggest starting with:

• Listing versions of whatever you are using (DAQmx, LabVIEW, Windows, etc.)
• Screenshot of the NI-MAX entry for the device on the working system
• Screenshot of the NI-MAX entry for the device on one of the non-working systems
• Attach the subVI from your code that makes the connection (back-saved to 2020 or so, if you're using anything newer)

[eLAB_RAT]

Here is some info about my working and non working systems. Please let me know if anything else would be helpful.

Thank you!

Working System: 

• LabVIEW version 20.0.1 
• NI MAX version 20.5.0f0
• Windows 10

 

Non Working System:

• NI MAX version 2024 Q2
• Windows 10

 

 

 

[DHerron]

Are all computers and the cDAQ on the same subnet? I've had strange behavior before when something's set to DHCP and I can see it in MAX but it won't connect. Usually MAX gives a hint if that's the case though because it says Inconsistent IP settings, which I don't see in your screenshots.