Problems reading Thermocouples on a 9214 in a 9144 EtherCAT chassis

[RichardvL]

I have a PXIe-1078 chassis with a PXIe-8135 Controller and a 9144 EtherCAT chassis with multiple C-modules, including a couple of 9213's and a 9214, running Veristand 2014 and Inertia 2014. I updated last week so I believe I have the latest updates for the hardware and software.

The problem I am experiencing is that I can read my K-Type thermocouples with the 9213 Thermocouple modules, but when I connect them to the 9214 Thermocouple module I see only TC0 changing and all the rest of the 9214 TC channels are 0 degC. I tried using High Speed and High Resolution modes, but no difference. I also moved the module to slot 8 in the EtherCAT chassis, also without success. I then moved the 9214 with its connector and thermocouples to another machine with a cDAQ 9188XT chassis and I could read all the thermocouples with NI MAX. This proves that the module is functioning and that the connections to the module are good.

I need to use the 9214 because of its ability to handle higher common mode voltages. I need help. Please.

Thank you in anticipation

Richard

[ATarman]

Richard,

I recently had issues reading analog inputs on 9144 EtherCAT chassis.  Some worked and some didn't. 

My issue was related to a conflict between my version of NI-RIO and Industrial Communications for EtherCAT. I am now using VeriStand 2013 SP1, NI-RIO 13.1, and IndCom 2.7.  

You may confirm compatibility here:  http://digital.ni.com/public.nsf/allkb/95C89EC992A412A986257CD6007525B7

Regards,

Andy Tarman

[ATarman]

Also - you may have to reinstall the Scan Engine Add-On (https://decibel.ni.com/content/docs/DOC-15510) after changing the above-mentioned drivers

**wishing you had a red or blue tractor avatar 🙂 **

Good luck.

[RichardvL · Accepted solution]

It ended up being that I had to download the latest update, 14.0.1 for the NI-RIO. This resolved the issue. I did not have to reinstall Veristand, Labview or any other driver.

Thank you for your responses.