NI 9144 DO behave strangely after updated to 2017

[Noriker]

Since upgrading from 2016 to 2017 we have had a problem with the digital outputs from a module on an expansion chassis NI 9144. We don't know how to go about debugging what the problem could be.

The expansion chassis is connected via Ethercat. We use shared variables to exchange information with the cRIO. The DO on the chassis are used to operate relays. Approx every 10 mins the relays that are on, turn off for about 3 seconds unpexpectedly. We seem to get values back from the shared variables that communicate DI's from the expansion chassis.

How can we investigate whether the chassis is rebooting, experience errors or there is some disruption to the ethercat comms etc.?

The controller and chassis are on a remote site, so we can't easily observe them.

Please advice on suitable debugging methods. Many thanks.

[Yin_W]

How can we investigate whether the chassis is rebooting, experience errors or there is some disruption to the ethercat comms etc.?

The easiest way would be carefully monitoring all error out terminals. Have you wired all error out terminals in your LV project?

I am also interested in how you upgrade the LV project after you upgrade to LV 2017. Did you format the controller and reinstall EtherCAT? Can you attach the MAX report here?

[Noriker]

---

@Yin_W wrote:

How can we investigate whether the chassis is rebooting, experience errors or there is some disruption to the ethercat comms etc.?

The easiest way would be carefully monitoring all error out terminals. Have you wired all error out terminals in your LV project?

I am also interested in how you upgrade the LV project after you upgrade to LV 2017. Did you format the controller and reinstall EtherCAT? Can you attach the MAX report here?

---

Hi, Thanks very much for your reply.

Well, what error output terminals? We do monitor every single one that we use, and nothing is reported, but there isn't one relating to Ethernet comms, unless there is a property node that we can add purely for monitoring? The only terminal in our project relevant to this is the shared variable.

The chassis was upgraded using MAX to upgrade the entire software set. We didn't specifically reformat the controller first. The NI Industrial comms for ethercat was upgraded to the correct version as part of this (v17.6 for LV 17sp1)

There is a possibility of hardware fault which we are in discussion with NI support. However any suggestions and comments are very welcome and appreciated. Regards

[Yin_W]

Can you please provide the Service Request number and your LV project?