NI MyDaq Analog input always returning error -201381

[Wouter.Sas]

Hi all,

I have a mydaq which always returns error 201381 on random timestamps (overcurrent protection kicked in) when trying to read any analog input (ai0/ai1). 

This is even the case when nothing is connected. Could it be the ADC is broken?

What could I do/test to try to resolve/pinpoint the issue?

thx

[wsimpson0050]

Could you please attach photo and/or the VI's you are referencing to the post? Also describe all the physical connection you have to your device with nothing plugged into the mydaq.  

[Bob_Schor]

A few suggestions:

• What version of LabVIEW (year and revision, bit-ness) and Windows are you using?
• MAX is your friend.  Open MAX, find your myDAQ, and open a Test Panel.
• Describe what is wired to what.  You say "ai0/ai1" -- what does this mean?
• Are you recording single-ended or differentially?  Describe what is connected to each Analog Input line (or say they are "floating in the breeze").
• What happens if you put a resistor (or, alternatively, a wire) across the two inputs you are using?  With a resistor, do you pick up A/C "noise" at 60 (or 50) Hz?

I have a myDAQ at home.  I can try it out this evening (if I remember).  I'll be using Windows 11 and LabVIEW 2024 64-bit.  [Oops -- it might not run with 64-bit LabVIEW ...].

Bob Schor

[Bob_Schor]

Sorry about the delay in responding.  I am sitting with my Windows 11 PC running LabVIEW 2024 (64-bit).  I've plugged in my myDAQ, and opened MAX, which "sees" the myDAQ!

The Good News is that the myDAQ shows up on the Devices and Interfaces.  The Bad News is that it basically is not "recognized" by MAX (notice the name by which it is addressed:  "USB\VID..." and the fact that there is no sub-panels on the right part of the MAX screen, such as "Test Panels", which I've learned means that MAX cannot really "see" the device and work with you to test its functionality.

It does appear that LabVIEW 2019 will work with myDAQ.  LabVIEW 2024 is "on the edge" of the 5-year backward compatibility.  However, there's one more "trick" that might work -- while rooting around, I found a mention of NI-ElLVISmx, which I vaguely remember might be the myDAQ device driver.  I'm going to see if I can download and install it -- will be back shortly (I hope).

Bob Schor

[Bob_Schor]

Nope, adding the Elvismx (2019) Driver didn't help.  I think that "software" (meaning Windows 11 vs Windows 10 and the implications for older NI software, particularly its device drivers) has rendered the myDAQ obsolete.

Needless to say, I haven't recently plugged my personal myDAQ into my PC.  I do think I tried this maybe 2-4 years ago (to research something for the LabVIEW Forum regarding the myDAQ), but time passes ...  Think I may surplus this device ...

Bob Schor

[softball]

Hi

Response to Bob surplussing his myDAQ. It is not quite time for that yet.

I got curious because 2024 is clearly out of the four year will-work time span, relative to the ELVIS final software release in 2019. So is it 'dead' ..

I am happy to report myDAQ still works with LabVIEW 2024 :

The computer used is a MacBook Pro 2010 running Windows 10 22H2. Old stuff that just works.

So inspect and compare the drivers I have installed on this configuration to yours.

An early Happy New Year to ALL.

PS : Maybe restricting LabVIEW installed versions to one per partition, when also installing drivers ( and more ) helps ..

[JÞB]

AO0 to AO1 is not a differential set of inputs.   You have hardware that is not correct.