VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-9216 Causes Primary Control Loop to Hang

Hello, 

 

I have in my project a NI-9216 which is an RTD module installed into a cRIO-9047. I've been having issues where the PCL hangs when deploying the project to the cRIO. See the image below. The PCL is set at 100Hz but then runs at less than 5Hz when the RTD module is enabled. I have attached an image of System Explorer showing the configuration. Everything suggests that this module should be compatible as per this article here DAQ Devices with Hardware-Timed Single Point Sampling Mode Support - NI

In another hardware setup, I'm using an EtherCAT Chassis (9145) which the NI-9216 seems to run without issue. Just only when deployed in the cRIO-9047. 

 

Zero_SR_0-1731423364986.png

 

Zero_SR_1-1731423530588.png

 

Additionally, when I try changing the programming mode in MAX to Scan Interface, I receive the following error when attempting to deploy in VeriStand

 

Zero_SR_3-1731424005073.png

 

I'm running VeriStand 2024 Q4 with all the latest driver sets as of todays date. Any information would be greatly appreciated 

0 Kudos
Message 1 of 2
(142 Views)

The HWTSP sampling rate of the module will be used as the timing source of PCL. You have only one NI-9216 which has the maximum sampling rate of 400S/s. If you want a higher PCL rate, you need to use another C module that supports a higher sampling rate.

The EtherCAT chassis uses its own Scan Engine as the timing source.

 

When you change the programming mode to Scan Interface, you cannot configure NI-9216 under the DAQ device. You must configure it under Scan Engine Custom Device.

-------------------------------------------------------
Control Lead | Intelline Inc
0 Kudos
Message 2 of 2
(106 Views)