LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

USB 6211 outputs Voltage

Hi,I have encountered such a problem that after using 6211 for a period of time, a 3.3V constant voltage is output after 6211 is connected to the computer. After 6211 is output voltage controlled by the program, the sine wave displayed by the oscilloscope is not complete, only the positive semi-axis waveform
0 Kudos
Message 1 of 12
(1,257 Views)

Hi Daisy,

 


@daisy_11 wrote:
I have encountered such a problem that after using 6211 for a period of time…

And what have you done to understand/prevent that problem?

What is a "period of time"? Seconds, minutes, hours, days?

What changes when that "period of time" has elapsed?

Does the DAQ device (and whatever is connected to that device) work as expected before the "period of time" has elapsed?

What is connected to your DAQ device?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 12
(1,220 Views)
6211 was connected to the computer and the output end was connected to the oscilloscope. I wrote the data into DAQmx, and the output voltage and oscilloscope showed waveform, which showed no problem. After testing for one or two days, the voltage waveform of 6211 output the same data appeared problem, and 6211 output constant 3.3V voltage
Download All
0 Kudos
Message 3 of 12
(1,216 Views)

Hi Daisy,

 

what happens when you use another AO channel?

What happens when you use a simple handheld DMM to measure the output of the USB6211?

(Is the USB6211 still ok or did there happen some voltage spike damaging your DAQ device?)

 

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 12
(1,212 Views)

The other channel is not used, but when the output end is measured with a multimeter, Ao0 is 3.3V and Ao1 is 2V

0 Kudos
Message 5 of 12
(1,208 Views)

Hi Daisy,

 

does your test work as expected when you use AO1 instead of AO0?

When the answer is "yes" then there might be a hardware problem with AO0…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 12
(1,202 Views)

Two channels have just been tested, both of which output the wrong waveform, where AO1 was not used before

0 Kudos
Message 7 of 12
(1,185 Views)

Please post your code *and* the waveform data you're writing to the task.

 

In the case of the Finite Sampling code screenshot, the last sample in that Waveform global will be held indefinitely after you stop the task.  That's the nature of AO on M-series devices, they maintain their last value.  Is it possible that the last waveform value is 3.3V?

 

In the case of the Continuous Sampling code screenshot, it isn't clear when the task will be stopped.  It seems unlikely that it'd always get stopped at the same sample #, but I also don't know how your data values vary with sample #.

 

Code and data will help clear that up.

 

 

-Kevin P

 

CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
0 Kudos
Message 8 of 12
(1,155 Views)
The program stops the task and resets the device after the stop button is pressed The final voltage in a finite sample is 0V instead of 3.3V Thank you for your reply. I contacted the supplier and learned that this problem was caused by the hardware damage of 6211
0 Kudos
Message 9 of 12
(1,117 Views)

Hi Daisy,

 


@daisy_11 wrote:
I contacted the supplier and learned that this problem was caused by the hardware damage of 6211

You might think about implementing a buffer/protection circuit to prevent other hardware damages of your DAQ devices…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 12
(1,114 Views)