MCC-DRV Error - USB-1608G Digital device not responding

[Supertech313]

New user here and new to Dasy Lab.

We're having an issue where about 5 min into running a program in Dasy Lab, it suddenly stops and give the following error.

USB-1608G (Device number 1)

Dev-Do0

Digital device not responding

 

Everything has worked fine in the past with the program, the layout and modules have not changed.

The DAQ's seem to be communicating just fine in InstaCal. So we're not sure what the issue is.

We tried the usual, swapping USB cables, shutdowns, restarts, and it keeps occurring.

I'm new to Dasy lab so if someone could at least point me in a direction to start troubleshooting it would be greatly appreciated.

 

Running

DASY Lab 13

Full version

Windows 10 Enterprise

InstaCal 6.52

 

I'll be glad to provide any screen shots or additional info if needed.

Thanks in advance.

[Fausto]

Hello @Supertech313.

Did your target system install a Windows update recently?

In Windows' Device Manager, expand the Universal Serial Bus Controllers branch and right-click on each of the USB Root Hub listings.  Click the Power Management tab.  Deselect the Allow the computer to turn off this device to save power option for each listing.  Also, disable any system OS sleep and/or hibernation modes.

 

Restart the system and retest the USB-1608G with your DASYLab worksheet.

If the issue continues, close DASYLab and install the current version of InstaCal.

If the issue continues after installing InstaCal, close InstaCal and DASYLab.  Run DAQami to test your USB-1608G.

If the issue is seen with DAQami, then you may have a hardware issue with your USB-1608G.

Let us know what you find out.

 

Regards,

Fausto

[Supertech313]

Hi @Fausto

Thanks for responding.

I really appreciate the help!

We've gone through everything you've suggested. The USB power saving was of course turned on, so we made sure it was off in the settings you showed, as well as in several other locations and also made sure all the power management settings for the hard drive, sleep mode, etc.. were changed to always on to avoid any issues anywhere else. We also updated InstaCal to version 6.74. Unfortunately the problem still persists. We got DAQami loaded today and we're going to go through that to try and troubleshoot. Being new to DAQami, Any tips or advice as far as simple steps to help diagnose the issue? 

[Fausto]

Hello @Supertech313.

On 8/7/2024 at 11:45 AM, Supertech313 said:

USB-1608G (Device number 1)

Dev-Do0

Digital device not responding

Do you have multiple USB-1608G devices connected to the target system?

Is the DASYLab worksheet accessing other supported capabilities of the USB-1608G or just the digital I/O?

Can you share your DASYLab worksheet or create and test a simple worksheet with your USB-1608G?

With regards to DAQami, I need to know more details about your DASYLab worksheet and which features of the USB-1608G are being used.

Regards,

Fausto

[NGCS]

Hello Fausto,
Yes, there are 2 USB-1608G Devices hooked up via Powered USB 2.0 Hub.

DasyLab worksheet only utilizes Analog and Digital I/O's from USB-1608G.  There are a total of 12 Analog and 6 digital I/O's utilized.

Good to note that when utilizing DAQami this afternoon and started testing the USB-1608G ports, the error was not seen and all prior channels displayed the signal until we reached to a specific Analog port which is used to measure current draw via an isolated shunt, which seems to have gone bad.  However, even when I manually de-populated those signal wires from the DAQ and changed the Dasylab to not use the I/O, the issue still persists.

Is it possible that a single Analog Port, which may or may not be compromised could cause this issue.

 

[Fausto]

Hello @NGCS.

Thank you for the additional details and test results.

Yes, it's possible that a single analog channel could have been compromised.  Have you looked at the PCB for any burnt marks?  If you have any burn marks, then the trace lines are damaged and we would not be able to repair that channel.

If you disconnect the other wires and connect the +5V terminal on the USB-1608G over to the questionable analog input channel, does DAQami or DASYLab read approximately +5V?  Verify the wire is secured by the screw terminals.  

Regards,

Fausto

[NGCS]

Hello Fausto,
The potential compromised channel has no input coming in, we simply took out the wires and took out the channel from the worksheet.  The issue still persists and we are in fact also getting additional MCC-DRV-Error and the following are the different MCC Errors we are getting:
-  USB-1608G (Devices number 2) Dev2-Do0 -> "Digital Device is not responding"

- USB-1608G (Devices number 2) Dev2-Do0 -> "Error number 300 has no text"

Once the above messages pop up, the DasyLab stops and the testing is halted.

While trouble shooting the issue observed, I did create a worksheet which has a few simple modules only, such as below and we still got the error in question above:

- Signal generator x1

- 5 Delay modules takin on the above signal  -> input to Digital output via USB-1608G, which actuated a 5V relays (x6)

Please advise on any other steps ... we have hit a wall and we ran out of any other troubleshooting ideas.

 

 

[NGCS]

Hello Fausto,
The potential compromised channel has no input coming in, we simply took out the wires and took out the channel from the worksheet.  The issue still persists and we are in fact also getting additional MCC-DRV-Error and the following are the different MCC Errors we are getting:
-  USB-1608G (Devices number 2) Dev2-Do0 -> "Digital Device is not responding"

- USB-1608G (Devices number 2) Dev2-Do0 -> "Error number 300 has no text"

Once the above messages pop up, the DasyLab stops and the testing is halted.

While trouble shooting the issue observed, I did create a worksheet which has a few simple modules only, such as below and we still got the error in question above:

- Signal generator x1

- 5 Delay modules takin on the above signal  -> input to Digital output via USB-1608G, which actuated a 5V relays (x6)

Please advise on any other steps ... we have hit a wall and we ran out of any other troubleshooting ideas.