-50405

[Rgulbrandson]

Using a CompactDAQ chassis, cDAQ-9178.  Getting random occurrences of error Status Code: -50405  "No transfer is in progress because the transfer was aborted by the client.  The operation could not be completed as specified.

Is this a hardware communication problem?  Or is it caused by some error in my software?  If the later, what might be the failure mechanism?

We can run for hours without an occurrence, then suddenly within a period of 15minutes the error can occur several times. Attachment shows an example of the dialog we see.

The only way we can reset is to either power cycle the system or close our application, open MAX and reset the chassis.

OS: WindowsXP-SP3  Using LabWindows CVI V8.5 Running DAQmx9,3 on 2.93Ghz Dual Core with 2GRam

NI Hardware:  CompactDAQ Chassis 9178 with various Modules..

[Jake_G]

Hey Rgulbrandson,

I found an article online describing some of the troublshooting steps for this error:
http://ae.natinst.com/public.nsf/webPreview/3EA2432762C45B298625734D0061D527?OpenDocument

Here are the main troubleshooting steps as pertaining to you.
Issue 2 Restoration Options
Reset the device from the driver (niScope_ResetDevice or DAQmxResetDevice).
Open Measurement& Automation Explorer (MAX) and expand Devices and Interfaces to locate your device. Right-click the device in the list and select Reset Device.
Disconnect and reconnect your device from the system.
Reboot the system.

Another thing you may want to try is swapping the USB cables to see if there is a problem there.

[cath]

Dear Jake,

I think I have the same problem. I cannot open the link : http://ae.natinst.com/public.nsf/webPreview/3EA2432762C45B298625734D0061D527?OpenDocument
Do you have a pdf version or anythink else to read this article.

Thanks a lot

Cath

[Jake_G]

Hey Cath,

Are you sure you were logged in when you tried to view the page?

Either way, here is the solution information:

Solution -

Re-establishing Communication
To re-establish communication with a USB DAQ device, perform one of the following procedures. Not all procedures listed here work in every situation; therefore, if one option doesn't work, then try another one.

As a first step, try plugging in your device into a different USB port on your computer.  This can cause your computer to do another auto-detect on your hardware and re-establish communication.

Issue 1 Restoration Options

• Close the open driver session (niScope_close or DAQmxClearTask) and open a new one to the device (niScope_init or DAQmxCreateTask).
• Reset the device from the open driver session (niScope_ResetDevice or DAQmxResetDevice)
• Open Measurement& Automation Explorer (MAX) and expand Devices and Interfaces to locate your device. Right-click the device in the list and select Reset Device.

Issue 2 Restoration Options

• Reset the device from the driver (niScope_ResetDevice or DAQmxResetDevice).
• Open Measurement& Automation Explorer (MAX) and expand Devices and Interfaces to locate your device. Right-click the device in the list and select Reset Device.
• Disconnect and reconnect your device from the system.
• Reboot the system.

To verify that your NI USB device is now working, open Measurement& Automation Explorer (MAX) and expand Devices and Interfaces. Then right-click your NI USB device and click Self Test.

How to Avoid Communication Loss
Under normal circumstances your USB device should not stop responding during acquisition. However this issue can occur on some PCs when plugging or unplugging additional USB devices while the computer is powered on.

If your application requires plugging/unplugging of additional USB devices and you are experiencing communication loss with your USB data acquisition device, a quality powered hub connected to USB 2.0 may help. Alternatively, consider trying a different PC.

If you are using a laptop computer, check your power settings to make sure that the USB ports are not being turned off to conserve power.

[sankarapandian.s]

Hi Jake, 

I am also facing the same issue. Same LabVIEW application i am running on different computers.

Out of 9 Products ,  i am facing issue in two products.

1. cDAQ 9172 Chassis, 

2. cDAQ 9174 Chassis.

All other chassis are cDAQ9174 &  working fine without issues.

I can go for the solutions, which suggested by many guys around here. But i would like to know what is the root cause of this issue. ??

Either Windows or NI Drivers ??

Because, My mouse, keyboard are USB Based But not losing communication.

Thanks in Advance,

sankar

[JD_war_eagle]

Hi sankara,

I am not aware of all the internal workings of our USB drivers or the Windows USB driver, but it seems like the problem may related to both.  It seems like at times inserting a USB device in a Windows PC occasionally causes all connected devices to reset.  In the case of your mouse and keyboard, the device may be reset, but they are able to do so gracefully and almost instantaneously reconnect.  The USB DAQ devices are more complicated and are not always able to simply seemlessly reestablish that connection.  The situation is most likely complicated even more by the DAQ devices possibly losing connection while in the middle of communicating an acquisition leaving the device in an unknown state or error state.