Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-9234/Sound and Vibration Assistant: Input signals being zeroed (tared) automatically

Solved!
Go to solution

Hello everyone,

 

I have a voltage source and a force sensor as inputs into a 9234 DAQ module.

 

The software zeroes both signals every time they change. For example, if the voltage being read by the DAQ increases to a constant value, the software will plot an increase in voltage, followed by a slow return to zero. Similarly, if I increase the force applied on the force sensor and hold it at a constant value, the program will plot an increase in force, followed by a return to zero.

 

Here is a graphical representation of the problem, which uses the force sensor as an example:

forum question.png

 

The sensors are passive. The force sensor is a PCB 208C02, and the voltage source is from an LDM-1000 signal conditioner, which recieves signal from an MHR 250 LVDT. The changes in displacement by the LVDT core are interpreted by the signal conditioner, which translates the position to a voltage value that can be read by the DAQ.

 

Thank you in advance.

 

 

0 Kudos
Message 1 of 6
(5,325 Views)

And what is the question/problem?

The force sensor has a 1 mHz Highpass, so it will go to zero 🙂

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 2 of 6
(5,300 Views)

Thank you for your help. This does not explain what I am seeing with the LVDT, however.

 

Before using the NI-9234, I checked the output voltage from the signal conditioner with a multimeter. Sure enough, the voltage remained at a constant nonzero value for any LVDT position that is not at zero. If I were to move the LVDT core and keep it still, for example, the voltage would change and remain at a constant value correlating with the core position.

 

The problem here is that either the DAQ or the NI Sound and Vibration Assistant is zeroing the voltage signal after every displacement, in the same manner as is displayed in the picture in my initial post.

 

Do you know if there is a way to stop this from happening?

0 Kudos
Message 3 of 6
(5,289 Views)
Solution
Accepted by KFod

I would guess you have the 9234 set to AC Coupling mode, whereas you should be using DC Coupling.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Message 4 of 6
(5,283 Views)

@AnalogKid2DigitalMan wrote:

I would guess you have the 9234 set to AC Coupling mode, whereas you should be using DC Coupling.

 

-AK2DM


😄

 https://www.youtube.com/watch?v=Zk5Il6KQrd8

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 5 of 6
(5,274 Views)
Solution
Accepted by KFod

Additionally the IEPE input only allow the 9234 AC input with a 0.5 Hz -3dB cutoff ...

So to get a dF/dl  (delta Force to delta length) it's not a bad idea to set both to AC (maybe add an additional  1mHz 1or2 order highpass to the length for better long term match)

To get an absolute length you can read the LVDT with a 3. channel in DC mode.

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


Message 6 of 6
(5,270 Views)