Labview/DAQ Problem: Accelerometer Measurement Troubleshooting

  • Thread starter Thread starter linford86
  • Start date Start date
  • Tags Tags
    Lab
Click For Summary

Discussion Overview

The discussion revolves around troubleshooting issues with an accelerometer measurement setup using a National Instruments (NI) DAQ board (NI 6025E) and LabVIEW software. Participants explore potential wiring and configuration problems that could lead to incorrect readings, specifically focusing on signal saturation and ground connections.

Discussion Character

  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant describes their setup, noting that the accelerometer is wired to the DAQ board according to the manual, but the LabVIEW graph shows a saturated signal at 10V instead of the expected 0-5V range.
  • Another participant suggests checking the NI Measurement & Automation Explorer for ADC data and questions the accuracy of the provided pinout information.
  • A participant later reports that the issue was resolved by tightening the connector, which improved the ground connection, but expresses confusion about why the signal saturates when nothing is connected.
  • There is a discussion about the pinout, with one participant asserting that their original pinout was correct based on the manual, while another admits to referencing the wrong page for the pinout information.

Areas of Agreement / Disagreement

Participants do not reach a consensus on the initial cause of the problem, as one participant resolves their issue while another questions the pinout accuracy. The discussion reflects both agreement on the solution and disagreement on the interpretation of the pinout documentation.

Contextual Notes

The discussion highlights potential limitations in understanding the pinout documentation and the implications of loose connections on signal integrity. There is also an acknowledgment of the behavior of floating inputs in DAQ systems.

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.
 

Similar threads

Replies
7
Views
2K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 8 ·
Replies
8
Views
3K
  • · Replies 1 ·
Replies
1
Views
5K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 9 ·
Replies
9
Views
2K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 6 ·
Replies
6
Views
4K
  • · Replies 78 ·
3
Replies
78
Views
6K