ni.com is currently experiencing unexpected issues.

Some services may be unavailable at this time.

Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Data on all channels is almost identical

I have a DAQPad-6015 and I am reading ACH0.  However, when I read any of the other channels, the data is almost identical.  Looking at the graph, the waveform from ACH0 (connected to an accelerometer) and another channel (ACH5 in this case, not hooked up, so it should be just noise) are right on top of each other.  Looking at the data, they are in fact different by a few percent. 
 
My accelerometer gives +/- 5V output, so I really don't see a way there should be that much leakage or coupling or any other physical effect.  However, because the data is not exactly identical, I have trouble pointing the finger at my code.
 
Also, running each channel seperately works fine.  That is, ACH0 by itself gives accerometer data, usually about 3V in amplitude centered around zero.  ACH5 by itself gives a few 10s of millivolts of noise centered around zero.  However, when running them both at the same time (wiring Dev1/ai0, Dev1/ai5 to the DAQmx Create Channel VI, then ACH5 rises to almost exactly follow ACH0.
 
I'm using Labview with the mx DAQ VIs.  Is there any reason that channels that are not hooked up to hardware should be reading similar data as the neighboring channels?
 
Thanks,
Casey
0 Kudos
Message 1 of 4
(3,329 Views)
Left unconnected, the high impedance inputs 'float'. Voltage signals on adjacent channels are 'ghosted' from the effect of input capacitance charging up on connected channels. When switching to adjacent unconnected channels, this capitance has stored the voltage charge and is read. Since the input impedance of the card is high, the voltage is not bled down to zero. I think there is an app note regrading this somewhere on this site.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 2 of 4
(3,327 Views)
But  why this is not occuring when I use PCI 6014 that has the same impedance 100 G ohms?
Anyway how can fix my s/w to identificate "not connected" signal from "ghosting" signal?
 
thanks
0 Kudos
Message 3 of 4
(3,234 Views)
It turns out there is a very large body of info on this in the Developer Zone.  I don't know if you've already looked through it or if it will be relavent to your particular card, but here's a few places to start reading:

http://digital.ni.com/public.nsf/websearch/B9BCDFD960C06B9186256A37007490CD?OpenDocument
http://zone.ni.com/devzone/conceptd.nsf/webmain/01F147E156A1BE15862568650057DF15?opendocument
http://digital.ni.com/public.nsf/websearch/5B86A63ECC0D48828625629800571743?OpenDocument
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/b9b5d37a04c772b58625686500695c20?OpenDocument
http://digital.ni.com/public.nsf/websearch/48CC15B99E99F87886256297005F69A8?OpenDocument
http://digital.ni.com/public.nsf/websearch/4E9B8B3F8FD3A31B862562B5004EA1D9?OpenDocument


Message 4 of 4
(3,226 Views)