USB-6009 NI Platform Services: No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified Status Code: -50405

[claflamme]

Hi,

I am currently working on a system that uses 2 USB-6009 devices to acquire and to output both analog and digital signals. We are faced on a regular basis on the following error message :

NI Platform Services:  No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified.
Task Name: _unnamedTask<1>

Status Code: -50405

I have read on different NI forums about other devices having the same error and it all seems to be related to power and grounding. After many validations, this does not seem to be my problem.

I am using a pc and both USB devices are connected via a powered USB Hub. The error happens on both USB-6009 at the same time.

Can anyone give me more details about this error and the possible causes ?

[The_Red_Barron]

Howdy claflamme!

The 50405 error occurs when the USB communication is lost or interrupted for some reason.  This KnowledgeBase article lists several possible causes for a USB DAQ device to stop responding.

If possible, connect the USB-6009's directly to the system rather than through the hub.  Even though the hub is powered, it may not maintain a consistent communication stream.

Also, verify that your computers power settings will not try to power down the USB ports to conserve power.  This is the default setting on many systems and can cause the USB device to lose communcation after a certain period of time.

Regards,

[martzak]

I wanted to chime in here and hopefully help out someone else out there who's experienced the 50405 error.

I was using my USB-6351 to read two pressure transducers (0-5V input) and control 3 digital output lines controlling a pump and two solenoid valves (via relays, of course). The pressure transducers were powered with a 5V plug-in isolated power adapter whose ground I did connect to my DAQ GND, pin3. However, DAQ's GND was floating with respect to the Building Ground.

After running my VI for about 2 minutes I would get 50405 error.
This continued despite changing the VI in every conceivable way. Finally, I tied all my grounds (including DAQ's) to the Building Ground and the error vanished.

I'm not entirely sure how this type of a grounding issue should affect USB communication, but in my case it did. I hope this explanation helps some one out there who is on the verge of pulling their hair out.