C DAQ- 9189 ETHERNET Chassis losses communication to host PC after some time of running the acquisition.

[RCAP_339]

cDAQ-9189 ETHERNET Chassis is configured with a static IP 192.168.1.10 , sub net 255.255.255.0 and default gateway 192.168.1.1 and host PC is configured with IP 192.168.1.5, sub net 255.255.255.0 ,default gateway 192.168.1.1.

Chassis is detected in MAX and is reserved to the host PC. All the modules are detected and self test is passed. Laptop OS is windows 10 , DAQ MX 17.6, Labview 2017 is used for the development. I am running the code since last 3 months from the development laptop and have not faced any issues in communication with the chassis. After the application was built the same was tested from the development laptop. 

Now i have a brand new windows 10 updated , 8 GB ,1 TB laptop which i want to use at customer place to which the application is installed and since then i have trouble with communication losses to the chassis. 

I ran ping test in command window alongside with application running, to look for any losses and found that the error is "General failure" and this lasts for couple of seconds and again the ping test is back to OK. This causes the acquisition loops to throw error and crash the application.

I tried the same ping test after installing the full Labview development platform and DAQMX 17.6, to this laptop and run the code itself but the issue is not solved. If i switch to the other lenovo laptop, everything works fine and good and i never saw this behavior. This is happening in a random fashion . Some times the application will run smoothly for 1 hr and more and sometimes will not last for more than 10 minutes. I don''t see any memory build up or processor build up.

We have updated the firmware in chassis as well. 

The screen shot was taken when IP was set to 169.254.175.48.

There is only one laptop communicating to this chassis . 

Any ideas or updates are welcome . 

Thank you.

[JiwhanS]

Hi RCAP_339,

I've attached some links below that might be helpful in looking at the issue with the cDAQ. Since it works on the old laptop but not on the new laptop, my first guess would be to look into any network settings that might be preventing the laptop from communicating with the cDAQ properly.

Troubleshooting Network cDAQ Connectivity Issues

http://www.ni.com/tutorial/54485/en/

Configuring Software and Hardware Firewalls to Support National Instruments Products

http://www.ni.com/product-documentation/12402/en/

Configure Ethernet cDAQ on Computer With Two Network Ports

https://natinst.lightning.force.com/lightning/r/Knowledge__kav/ka00Z0000011OanQAE/view