Using DAQ Assistant to setup a Full-Bridge piezoresistive accelerometer with cRIO-9048 and NI-9237 modules

[CAJG37]

Hi, all.

I am new to NI hardware and LabVIEW and I'm having trouble using the DAQ Assistant to create a Bridge (V/V) task to setup an accelerometer (ENDEVCO Model 7264C) and using the "Device", "Calibration", and "Connection Diagram" options.

Whenever I try to use the "Device", "Calibration", and "Connection Diagram" options on the DAQ Assistant, I get error messages (see figure ErrorMessage1, 2, & 3). I also tried to create the Bridge (V/V) task through the NI MAX interface, but I got the same error message I did when I tried it through LabVIEW (see figure ErrorMessage5). I also get a similar error when I try to use the "Test Panel" functionality on NI MAX (see figure ErrorMessage4), so I wonder if the issue has to do with the way I setup the cRIO chassis.

Looking at the cRIO-9048 name in the NI MAX, it looks like it should work as it is named "cRIO1", but since I am new to NI hardware and software it is definitely possible that I am overlooking a critical detail. The hardware (both cRIO and NI-9237) pass the "Self-test", so I am not sure what could be the problem. Any assistance with this issue would be really appreciated :), so I thank you in advance for your time, support, and patience with a NI newbie.

I am currently using a trial version of LabVIEW 2024 Q3, with the LabVIEW Real-Time and FPGA modules installed, as well as the NI-DAQmx and NI CompactRIO drivers. My hardware consist of a NI cRIO-9048 and a NI-9237 module.

[GerdW]

Hi CAJG,

please show a screenshot of the "Devices" sub-tree in MAX.

---

@CAJG37 wrote:

Looking at the cRIO-9048 name in the NI MAX, it looks like it should work as it is named "cRIO1", but since I am new to NI hardware and software it is definitely possible that I am overlooking a critical detail.

---

With DAQmx you usually use the "name" of the IO card/module as "device name", so you should use something like "Mod1" when you didn't set a more distinctive label for that module in MAX.

[CAJG37]

Hi GerdW,

I have attached a screenshot of the devices sub-tree.

You are right. The NI 9237, that is the IO module, is called "Mod1". The DAQ Assistant should then look for "Mod1" instead of the "cRIO1"?

Let me know if you have any other thoughts and thank you for your time.

Kind regards, CAJG37

[GerdW]

Hi CAJG,

---

@CAJG37 wrote:

The NI 9237, that is the IO module, is called "Mod1". The DAQ Assistant should then look for "Mod1" instead of the "cRIO1"?

---

Yes, I would use "Mod1" as device name.

(I haven't worked with DAQmx on cRIO targets, but the driver should behave the same as on Windows targets.)

I recommend to stay away from DAQAssistent, instead use all the recommendations in this guide (except chapter one).

[CAJG37]

Thank you, GerdW! I will follow your advice and check the recommendations on the guide.

Have a good one!

Kind regards, CAJG