usb 6501

[bobcook40]

I am trying to set up a virtual USB 6501 device and having no luck.  I have NI-DAQmx device driver 8.0.0f0 installed.  I have tried downloading the base driver but that has not helped.  I am a newer user and this is frustrating me!

[Dennis_Knutson]

You have an older version of DAQmx but even with the latest (8.3), there is no support for simulation of the USB-6501. You could instead try simulating the PCI-6503 which also has 24 digital I/O is is software timed. The latest version of DAQmx can be downloaded from https://www.ni.com/en/support/downloads/drivers/download.ni-daq-mx.html.

[Vicen]

Hello,

I have downloaded the example USB-6501 Interactive Control but I can’t use it. I plug in my computer with the adaptor box and I check the 25 pins of the tester. With a multimeter I can calibrate all the pins and I observe that some of them have 5volts and the others have 0, high and low level, as it is supposed to be.

However, when I run the program and I try to change from High to Low it appears this error:

Error -200220 occurred at an unidentified location

Possible reason(s):

Device identifier is invalid.

If I change the name I have a different error:

Error -200558 occurred at an unidentified location

Possible reason(s):

One task cannot contain multiple independent devices.

Create one task for each independent device.

I don’t know if I’m introducing bad the name or what can be wrong. I would thank if someone could help me.

Vicente

[Matthew_W]

Hi Vicente,

 The reason you are possibly seeing this error is that the USB-6501 Interactive Tutorial example has a control at the bottom of the screen, you must put the device alias that has been assigned in the Measurement & Automation Explorer to the USB-6501.
 

To find or assign a alias to the USB-6501 do the following:
  Click Start->Programs->National Instruments->Measurement & Automation
  Click the "Dev n", type in a new name for the device. I've highlighted this in the following picture.


Please bear in mind also that this example uses DAQmx Base. This is a subset of the DAQmx drivers, really the only reason you should be using DAQmx Base and not DAQmx is if you are
doing data acquisition on a Macintosh. 

The full DAQmx drivers can be downloaded here.  If you are using Labview then are examples that perform the same functionality (Statio DIO) as the USB 6501 Interactive example. These can be
found in Labview by going to the Help menu. Click Find examples, it will launch the NI Example Finder. Then click Hardware Input/Output->DAQmx->Digital Measurement (or Generation)->Read Dig Port.VI.

Have a great afternoon!

Best regards,

MatthewW
Applications Engineer
National Instruments

Message Edited by Matthew W on 09-05-2007 10:00 AM

Message Edited by Matthew W on 09-05-2007 10:21 AM

[vicente.salort@analog.com]

Hello,

Now I have a new problem. I finally got to use the USB-6501 Interactive Control.vi, but since yesterday I can not use it. When I open the program it starts loading all the files but before it finishes it stops, so I can not open the program, and that is something it didn't happen before. Labview works well, so should I download the drivers again?

[Matthew_W]

 Hi Vicente,

It sounds like either the .llb where the example comes from got corrupted or the firmware in the device got switched to DAQmx somehow.

The USB6501 Interactive Control.llb is a library file that contains all of the support files necessary for LabVIEW to run the example. From your description, partially loads the vi then stops, it sounds like there might be a problem with one of the included sub-vi's. Does LabVIEW generate any errors?

The USB-6501 can contain one of two firmwares: DAQmx or DAQmx Base. 

Please do post back if it still will not work and post any errors that LabVIEW is generating.

Have a great afternoon.

Best regards,

MatthewW
Applications Engineer
National Instruments

[Vicen]

Hi Mathew,

I couldn't open the elements of the library because they are in a higher version but I followed the steps that you attached me in ' a utility found here' and now it's working after having updated the drivers. Thank you very much.

Regards

Vicente