CompactDAQ or CompactRIO for vibration DAQ

[linkedab]

---

What difference would it make whether CompactDAQ or CompactRIO was used to record vibration as listed below? Communication will be through nidaqmx Python library using Wifi.

1. Waveform data (sampling rate 10kHz, duration 2 seconds)

2. Hilbert transform applied to waveform.

3. FFT applied on waveform.

[ZYOng]

What model of cDAQ or cRIO you are using? cDAQ-913x has its own controller and behaves differently from other cDAQ chassis.

Are you using cRIO-904x/5x? Other models of cRIO do not support DAQmx.

How are you communicating using wifi? If you are using cDAQ or cRIO with controllers, the code must be deployed to the controller directly.

[linkedab]

I'm not using any yet but planning at this stage.

[ZYOng]

Running python on Windows host controlling cDAQ chassis is the cheapest and most simple solution if you are just planning to acquire the data without doing any feedback output. You might be able to connect to an Ethernet-based cDAQ chassis (cDAQ-918x) by plugging it to an office network and control it through your laptop's wifi.

[crossrulz]

Most of the modules will work with cRIO and cDAQ.  However...

---

@linkedab wrote:

---

Communication will be through nidaqmx Python library using Wifi.

---

Then you have to use an Ethernet cDAQ that does not have an embedded controller.  Look here and figure out which chassis will meet your requirements.  The biggest issue you need to solve is which C-Series modules you will need to take your measurements.  Once you have the those figured out, and how many you need, then you can choose the chassis.

[linkedab]

AM

Thanks ZYOng and crossrulz.

So can it's response include Hilbert transformed data or only waveform for processing by Python later? Say, if a Labview program including data transformations needs to be run at the cDAQ itself before the data is recieved, will a controller be required?

---

, will the same hardware be able to do it or something else is required?

---

@crossrulz wrote:

Most of the modules will work with cRIO and cDAQ.  However...

---

@linkedab wrote:

---

Communication will be through nidaqmx Python library using Wifi.

---

Then you have to use an Ethernet cDAQ that does not have an embedded controller.  Look here and figure out which chassis will meet your requirements.  The biggest issue you need to solve is which C-Series modules you will need to take your measurements.  Once you have the those figured out, and how many you need, then you can choose the chassis.

---

[crossrulz · Accepted solution]

---

@linkedab wrote:

AM

Thanks ZYOng and crossrulz.

So can it's response include Hilbert transformed data or only waveform for processing by Python later? Say, if a Labview program including data transformations needs to be run at the cDAQ itself before the data is recieved, will a controller be required?

---

, will the same hardware be able to do it or something else is required?

---

I was under the impression you wanted your Python code to do the transform.  If you want processing at the sensor then, yes, you will need a controller.  I would be inclined to go with a cRIO over a cDAQ if you are doing that.  You will need LabVIEW RT to program a cRIO and possibly LabVIEW FPGA if you want to add intelligence in the cRIO FPGA.

You will also have to develop your own TCP messaging protocol to pass the data to your PC.

[ZYOng]

---

You will also have to develop your own TCP messaging protocol to pass the data to your PC.

---

Or you can use ni-grpc-device

[linkedab]

ZYOng Awesome, Thank you.