From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

NI 9237 External Excitation - VeriStand 2013 SP1

Solved!
Go to solution

The recommended excitation voltage for my pressure transducers is + 10 VDC. I prefer to use external excitation as per the NI 9237 manual, total power for the module is limited to 150 mW, which in my case is "Four 350 ohm full bridges at 3.3 V". (I will be using (4) full bridge 350 ohm pressure transducers). I am using Scan Engine for EtherCat and have the NI 9237 in a NI 9144 Chassis connected to a cRIO-9081. For troubleshooting, I have two transducers on a pressure calibrator and another RJ50 connection to a NI 9949 breakout. If I select "External Excitation" and have my 10 V power supply connected to the lower EX+, EX- connector, I get an invalid value for my pressure transducer. This is after scaling the value in calibration. The Raw Value is also incorrect. If I leave it set to "External Excitation" but pull the EX+, EX- connector, the EX+, EX- voltage (pins 6 & 7) will go to 4.735 V and I will get a CORRECT pressure reading. If I select Internal Excitation of 3.3V, I will get a correct pressure reading, but I am a little concerned about resolution as the recommended excitation is + 10 VDC for the pressure transducers. My question is: why am I unable to use the external excitation? I have another application with a PXI and EtherCAT chassis and it works OK. I've also tried placing a NI 9237 module in the cRIO-9081 chassis and get the same invalid value that I describe above.

0 Kudos
Message 1 of 3
(4,869 Views)
Solution
Accepted by topic author ATarman

Do you have the latest version of the Scan Engine and EtherCAT custom device? On the community page for this custom device, the latest bug fix listed specifically refers to this module. Also there is a specific forum for this custom device that it may be a good idea to post on as well if you have not already posted there about this problem. 

Miles G.
National Instruments
Staff Applications Engineering Specialist
0 Kudos
Message 2 of 3
(4,805 Views)

Miles,

I upgraded to Scan Engine and EtherCAT 4.1.10 and it resolved the problem. 

Thanks so much for your help.

0 Kudos
Message 3 of 3
(4,759 Views)