Labview/DAQ Problem: Accelerometer Measurement Troubleshooting

  • Thread starter Thread starter linford86
  • Start date Start date
  • Tags Tags
    Lab
AI Thread Summary
An individual encountered issues with an accelerometer connected to a NI 6025E DAQ board, where the LabVIEW graph showed a saturated flat 10V instead of the expected 0 to 5V signal. They confirmed correct wiring and signal presence using an oscilloscope but suspected a grounding issue with LabVIEW or the DAQ. A suggestion was made to use NI Measurement & Automation Explorer for data verification. The problem was ultimately resolved by ensuring the connector from the external circuitry to the DAQ was securely attached, confirming that loose connections can lead to erroneous readings. The discussion highlighted the importance of checking physical connections and verifying pinouts when troubleshooting DAQ issues.
linford86
Messages
14
Reaction score
0
I'm trying to use an accelerometer to take measurements. I have it physically wired to my computer's DAQ board (a NI 6025E). According to the manual, pin 1 is ground and pin 3 is analog input 0. Therefore, this is where I have the output from my accelerometer going. I checked the signal at those pins using an oscilloscope and confirmed that there is the correct signal at that location in the circuit. I'm trying to use one of the example Lab View files to view the data from the DAQ board. However, according to the graph in Lab view, the waveform just grows and eventually saturates. At that point, all the DAQ reads is a flat 10V. I know, however, that this is incorrect because the signal from the accelerometer is between 0 and 5 volts. I suspect that either Labview or the DAQ are not "seeing" ground correctly.

Does anyone have any suggestions on what might be wrong? Thanks.
 
Engineering news on Phys.org
linford86 said:
I'm trying to use an accelerometer to take measurements. I have it physically wired to my computer's DAQ board (a NI 6025E). According to the manual, pin 1 is ground and pin 3 is analog input 0. Therefore, this is where I have the output from my accelerometer going. I checked the signal at those pins using an oscilloscope and confirmed that there is the correct signal at that location in the circuit. I'm trying to use one of the example Lab View files to view the data from the DAQ board. However, according to the graph in Lab view, the waveform just grows and eventually saturates. At that point, all the DAQ reads is a flat 10V. I know, however, that this is incorrect because the signal from the accelerometer is between 0 and 5 volts. I suspect that either Labview or the DAQ are not "seeing" ground correctly.

Does anyone have any suggestions on what might be wrong? Thanks.

Welcome to the PF. Are you using the NI Measurement & Automation Explorer to look at the ADC data?

It took me a bit of googling to get the pinout (the NI page wasn't cooperating):

http://www.ni.com/pdf/manuals/370719c.pdf (page 12)

The pinout you mention in your post does not seem to match...?
 
I actually solved this problem today. The connector from the external circuitry to the DAQ on the back of the computer wasn't tight enough, so the ground wasn't actually being properly connected. Why the signal saturates when there's nothing connected beats the hell out of me.

At any rate, you wrote that the pin out I gave you was incorrect. However, the document you posted has exactly the same pin out. I'm looking at page 14 of that pdf. It says Al GND (Analog Ground) next to pin 1. Then it says Al 0 (Analog Input 0) next to pin 3. So the connections I posted before were correct.
 
linford86 said:
I actually solved this problem today. The connector from the external circuitry to the DAQ on the back of the computer wasn't tight enough, so the ground wasn't actually being properly connected. Why the signal saturates when there's nothing connected beats the hell out of me.

At any rate, you wrote that the pin out I gave you was incorrect. However, the document you posted has exactly the same pin out. I'm looking at page 14 of that pdf. It says Al GND (Analog Ground) next to pin 1. Then it says Al 0 (Analog Input 0) next to pin 3. So the connections I posted before were correct.

Glad the problem is fixed. The AI input will float someplace if nothing is connected to it, so floating up is reasonable.

Ah, on the pinout, I was looking at the wrong page. I was looking at the first page of 3 pages of pinouts, and didn't read that I was looking at the wrong card's pinout. Sorry for any confusion.
 
Very basic question. Consider a 3-terminal device with terminals say A,B,C. Kirchhoff Current Law (KCL) and Kirchhoff Voltage Law (KVL) establish two relationships between the 3 currents entering the terminals and the 3 terminal's voltage pairs respectively. So we have 2 equations in 6 unknowns. To proceed further we need two more (independent) equations in order to solve the circuit the 3-terminal device is connected to (basically one treats such a device as an unbalanced two-port...
suppose you have two capacitors with a 0.1 Farad value and 12 VDC rating. label these as A and B. label the terminals of each as 1 and 2. you also have a voltmeter with a 40 volt linear range for DC. you also have a 9 volt DC power supply fed by mains. you charge each capacitor to 9 volts with terminal 1 being - (negative) and terminal 2 being + (positive). you connect the voltmeter to terminal A2 and to terminal B1. does it read any voltage? can - of one capacitor discharge + of the...
Thread 'Weird near-field phenomenon I get in my EM simulation'
I recently made a basic simulation of wire antennas and I am not sure if the near field in my simulation is modeled correctly. One of the things that worry me is the fact that sometimes I see in my simulation "movements" in the near field that seems to be faster than the speed of wave propagation I defined (the speed of light in the simulation). Specifically I see "nodes" of low amplitude in the E field that are quickly "emitted" from the antenna and then slow down as they approach the far...
Back
Top