I am losing connection to hardware because of time sincronization

[Sergey(PSU)]

We have hardware based on cDAQ9172 with some modules for signal generations and accelerometer module.

It works quite well but there is a problem with it. As far as I understand the problem appears when software/hardware tries to sincronize each other PC that is monitoring what happens on cDAQ9172 loses connection to the cDAQ9172. It still works  but there is no connection untill you will restart cDAQ9172.

It happens about the same time at 22.00.

Is it possible to turn off this sincronization on cDAQ9172 or there is another solution for it?

[rsw]

Hi Sergey,

That sounds like a very unusual issue with the 9172, I would suggest first checking that Windows has all its power settings set correctly to prevent turning off the USB. If you right click on "My Computer" and go to "Properties", then the "Hardware" tab and then to "Device Manager". This will open up your hardware manager, within here should be a list of USB Hubs, for example on my system I have "Universal Serial Bus > USB Hubs". If you double click on each of these (one at a time) a po-up dialog will appear, if you go to the "Power Management" tab on this and ensure the option "Allow the computer to turn this device off to save power" is not checked.

Sadly you will have to do this for each device listed under the "Universal Serial Bus Controllers".

If this doesn't work then my next question is why this appears to happen at 22:00 each night, if you start the program at the same time every day then it may be worth having a look at it's memory usage over the day to see if this is ramping up.

Let me know if these suggestions work or not and we can troubleshoot it further if needs be,

All the best,

[Sergey(PSU)]

I am really sorry it should be cRIO 9072 REal time controller.

I do not have an acces to it as it is installed on a plant.

But the question is still valid.

[rsw]

Hi Sergey,

No problems, as it's a cRIO I assume the connection loss issues occur over Ethernet to the device. If you could please let me know which driver versions this is loaded with - as the cRIO is on site if you have the machine that the cRIO was installed with and open up "Measurement and Automation Explorer >> Software". The specific driver versions for NI-RIO, also which modules are in the device?

You mention it is now installed on plant, when the same issue occurs would it be possible to ping the device via it's IP address to rule out any network issues.

Thanks,

[Sergey(PSU)]

Yes it is over the Ethernet.

I would contact people there with the ping request but unfortunately it would take some time up to a week to get it done.

The drivers verion is 3.1.1.

The modules installe are: NI9233 NI9263 and NI9211

[rsw]

Hi Sergey,

No problems I understand the time issues with the device now being on site, when they are able to I would check to see if they can run the following tests:

1. Is the device still pingable from the command line
2. Is the device directly connected to a PC or via a switch/hub, if the latter do IT perform any scheduled actions on these?
3. If the device has lost connection, would it be possible to reboot it to perform a resource check?
4. If yes to 3, go to Tools > Real-Time Module > System Manager in the project window after rebooting the cRI, check the boxes for "Track memory usage" and "Track CPU Usage" and leave this running until communication is lost to see if these continue to ramp up or remain stable
5. Is there anything else on the network that may attempt to use the same IP, a long shot but may be something to look out for
6. If on a network, does any other hardware on the network receive issues from communication drop outs, if so it may be a environmental issue - again a long shot but worth looking out for

All the best,

[Sergey(PSU)]

Rob,

I would ask them to check the issues but here is the info I could provide right now:

1)Most likely it is pingable as: first of all we are monitoring it through webpage and just this webpage is frozen(reloading it gives same picture)  secondly it is possible to do soft reboot using MAX.

 2)As it is on a plant it is conected using optical line: it comes out into converter of optical network and then in a control room it converts it back and connects straight intoPC. So there is no additional HUBs or other devices connected in this part of the network

[rsw]

Hi Sergey,

Thanks that rules out a lot of the potential issues it could be, I would recomment (when possible) performing the system monitor scan as mentioned previously, I will continue to have a look around and let you know if I have any other ideas/suggestions to try out.

All the best,

[Sergey(PSU)]

Rob,

Regarding your suggestion:

If yes to 3, go to Tools > Real-Time Module > System Manager in the project window after rebooting the cRI, check the boxes for "Track memory usage" and "Track CPU Usage" and leave this running until communication is lost to see if these continue to ramp up or remain stable

Is it in MAX?

[rsw]

Hi Sergey,

Sorry for the delay, no this is from the LabVIEW project window that includes your cRIO device, after ticking the monitoring checkboxes you also have to click the button that says "Start Monitoring" to ensure the procedure runs.

Thanks,