USB-2416 Loses Communication with PC

[Coal Gas Tech]

I have an MC USB-2416 Multifunction DAQ Device that was purchased in August 2020.  It is powered by an independent high-quality power supply with all being internal to a cabinet.

Usually when the device is powered up, it functions normally with the Power LED on solid.  But then, while operating, and for no apparent reason, the board loses communication with the PC and the Power LED starts to blink.  This can only be corrected by manually cycling the power to the unit.

Communication with the DAQ is with a custom program written in C# using the drivers supplied by MC.  When the error occurs while our software is running, we receive an "Unhandled exception" error and it freezes the program.

Also, perhaps unrelated but maybe not, we recently received an "Error 259" dialog with no further text.  What is Error 256?

What may be the causes of losing USB communitactions with the DAQ?  We have several other devices that communicate through USBs and they all seem to maintain dependable connections to the PC.  Might it be a problem with the DAQ?

We need this system to operate dependably without the need for human interaction.  Frustrating.  Please help.

[Fausto]

Hello @Coal Gas Tech.

MCC's Universal Library (UL) error codes are listed in the UL Help file, but that error code is not listed.  https://www.mccdaq.com/pdfs/manuals/Mcculw_WebHelp/ULStart.htm

Has this been an issue from the start or recent?

If recent, has there been any system configuration changes, i.e. hardware, software?

How long after starting your system does it take for the USB communication to drop?

Do you have another USB-2416 device to swap in and test?

Can you remove that problematic USB-2416 device and run a long-term test with a different Windows system and in a different environment?

You can use MCC's DAQami software.  https://www.mccdaq.com/daq-software/DAQami.aspx

Lastly, what is the device's serial number shown in InstaCal or on the backside label?

Regards,

Fausto

Edited October 25, 2022 by Fausto
added DAQami link

[Coal Gas Tech]

Thank you for the response, Fausto.

The 259 error just occurred once, and as I said, may not be related to the communication error.

The communication error has been an issue from the start.  The USB-2416 is installed in a system that we shipped to Algeria and it is there now.  At first, with all of our testing and starting and stopping of the operating system, we ignored the problem and thought it would go away once we were in a stable operating environment.  But it has not gone away.  It seems to occur at random times, maybe once per day or less.  And it seems to occur when the system is idle and not collecting data.  When it is actively collecting data it seems to be ok.

I do not have another unit to swap out or test.  If it is defective, I will need to ship a new unit to Algeria and then wait for the old one to return.  We cannot ship from Algeria first, as this would cause the system to go down.

Although the unit was purchased 2 years ago, it has only been operating for a few months because of Covid causing Algeria to close its borders for a prolonged time.  We are still in a system-commissioning mode, and so warranty replacement would be appreciated even though we are beyond the original 1-year warranty.

It is S/N 1EF9CA6, P/N 199082C-02L.

Thank you for your help and suggestions.

[Fausto]

Hello @Coal Gas Tech.

That serial number was invoiced in August 2020, so it is out of warranty.  

Which version of Windows is on the target system?

You stated it was "an issue from the start".  Does that mean before shipping your system or once it arrived at its final destination?

What's the length of your USB cable?

Is the USB cable plugged directly into your target system or an USB hub?  If using an USB hub, is the hub powered by an external power supply?

Please check the Power Management setting for the USB Hub in Windows Device Manager.  Do not select the option "to turn off this device to save power".

 

 

Regards,

Fausto