07-12-2020 09:34 PM
07-13-2020 01:23 AM
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?
07-13-2020 01:58 AM - edited 07-13-2020 02:00 AM
07-13-2020 02:10 AM
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?)
07-13-2020 02:47 AM
The other channel is not used, but when the output end is measured with a multimeter, Ao0 is 3.3V and Ao1 is 2V
07-13-2020 02:53 AM
07-13-2020 03:40 AM
Two channels have just been tested, both of which output the wrong waveform, where AO1 was not used before
07-13-2020 09:16 AM
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
07-14-2020 01:18 AM
07-14-2020 01:25 AM
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…