Network DAQ Connectivity Issue

[James.M]

Hello, I am having connectivity trouble with my NI cDAQ 9191, which is a network DAQ device.

The strange thing is that I can get it to work on one laptop, but not the client's laptop. Both laptops are actually the same model (HP Probook 5430s) running Windows 7. Here is a list of what my setup is:

• Ad Hoc network provided by cDAQ9191, no security
• Static IP address set on both ethernet and wireless settings on cDAQ 9191
• LabVIEW executable built and tested on both computers, running the code attached continuously
• Firewalls on both computer turned off
• IPv4 settings on both laptops set to all automatic
• Both computers connected to the ad-hoc network tried in all of the following configurations: one-by-one, both computers connected at the same time, with ethernet adapter disabled, with ethernet adapter enabled
• The code works on both computers when connected via ethernet, but the problem exists when the client's computer is connected to the ad-hoc wifi network (which is unfortunately a requirement).

The specific occurance is that the code will connect successfully, but then timeout the connection in the False case and then not connect again until i reset the network adapter. This can be repeated over and over again.

Does anyone on here know of some other network settings I can tweak to try to get this to work?

Thank you for any advice that could help me solve this problem.

Best,

[mikeporter]

When your IP settings are automatic on an ad hoc network, where are the IP addresses coming from?

Mike...

[James.M]

Sorry, I should have been more clear:
The 9191 is set to a static IP address "169.254.1.26" and the laptops have their IPv4 settings for the wifi adapter set to DHCP/automatic. This causes the laptops to adopt the subnet of the network to which they connect, and therefore the same subnet as the 9191. This works great on one laptop, but not the client's laptop.

I can connect to the ad-hoc network on the client's computer, and it stays connected, according to Windows. But the DAQmx network device connection disconnects right after connecting. The is not the case when I run the same executable on my computer, so I'm assuming it must be some difference between the laptops, most likely network setting related.

[mikeporter]

What IP addresses do the two laptops end up with after connecting?

Mike...

[James.M]

On our, working, laptop the auto-assigned IP address is currently "169.254.17.104".

The client's computer's auto-assigned IP address "169.254.4.241".

These both auto-assigned themselves to match the subnet of the 9191.

[smoores]

James,

What is the subnet mask for your network?  Do all of the devices conform to the same subnet mask?

Try pinging the cDAQ 9191 from the client computer after it disconnects.  Are all of the packets returned successfully?

What happens if you try to reserve the chassis on the client's computer in MAX rather than LabVIEW?  Are you then able to run test panels on the module that is in the 9191?

Try first unreserving the chassis in MAX on your computer then try running the code again on the client computer.  Any success?  What if you force chassis reservation by changing the boolean of the DAQmx Reserve Network Device to true?