EDVR Error with 0xe01e005b error

[RClayton]

I'm controlling a rack of instruments with a GPIB-USB-HS controller.  My test program is written in VB6, running on a computer with XP pro and all my drivers were installed with Instrumentation & Automation Explorer v4.2.1.  I'm consistently loosing the handles (EDVR error) to my devices several hours into my test and am getting an error code of 0x0e01e005b.  Any ideas?  I searched on here and found where someone suggested adding a powered hub which I have done.  The problem still exists.  I have five other almost identical test stands running the same program, three run flawlessly but another one has the same problem periodically.  If you unplug and re-plug in the USB connection to the computer everything is fine - for a while.

[JVP]

Hey,

   Are all your GPIB-USB-HS controllers running on the same systems?

Jig P

[RClayton]

No, they are all slightly different.  I put a ferrite bead on the GPIB-USB-HS's cable near the USB end last night, re-routed the cable and didn't have the problem.  Have you guys had EMI issues with these?

[JasonSmith]

From the version of Measurement & Automation Explorer you have mentioned, it seems like you are running NI-488.2 version 2.5 or older. A lot of improvements have been made to the driver since then, including many impacting this USB interface.

I am not aware of any EMI issues, so I don't know if the ferrite is really solving the problem, or if it is just a coincedence at this point. I would recommend that you update to the latest version of NI-488.2 to see if it changes the behavior of the problem at all.

-Jason S.

[JVP]

Hi.

You can also try NI Spy capture, to see exactly where things might be going wrong. Also there is another post on this forum that suggests trying to upgrade to the drivers try version 2.8.1

Regards,

Jig P

[ni_emc]

We have seen issues with some EMI phenonena impacting the operation of USB ports. In these cases, the USB port typically loses the connection to the connected device and fails to re-initialize the broken connection. 

The first thing to try, as already recommended, is to install the latest NI driver for your product. The more recent drivers are much more robust.

If this does not work, wrapping the USB cable a time or two through a snap-on ferrite bead is very effective in preventing any EMI from upsetting the USB port. For this application, we recommend Fair-Rite type 43 or 44 material (www.fair-rite.com).

Regards,

NI EMC Engineering