Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Help! USB6008 card driver conflict?

Solved!
Go to solution

I've been using usb6008 over a year with DAQmx 9.1.7 no issues.

P0.0 output (Hi or Lo) has been used for external switch.

 

Month ago, I purchased new usb6008 (it came with DAQmx 9.5.1).

I tried to used new usb6008 with the system (which has DAQmx 9.1.7) and

I found the port P0.0 doesn't change its state. It kept Hi all the time.

 

Then I tested new 6008 with Measurement and Automation Explore - digital output

section by selection All Output then P0.0 changed to hi to lo and it worked, changed to Lo!

 

This is my mystery: why newly purchased USB doesn't work with the system,

which has DAQmx 9.1.7? I just swapped the USB6006, all others are same!

Is it due to Driver conflict? It is confusing... Any thought or suggestion?

 

Thanks.

 

 

 

0 Kudos
Message 1 of 5
(2,424 Views)

Development or runtime environment?

 

WinXP or 7?

There's a data loss hotfix for XP with the later DAQmx drivers. 

 

Can you make a new VI and toggle the line high/low in there, or does it only do this in the code you have written?

0 Kudos
Message 2 of 5
(2,423 Views)
Solution
Accepted by topic author chunglee814

Does the program in your system hardcode the device name (by default, 'Dev1'), perhaps?

 

Devices are automatically 'named' based on the order that the driver sees them; assuming defaults and that you have no other NI devices, your first USB-6008 would be 'Dev1' and your second USB-6008 would be 'Dev2'.

 

Try using MAX to rename your new USB-6008 to 'Dev1', or whatever your old USB-6008 had been called. (You'll have to delete or rename the old USB-6008 from MAX.)

——
Brandon Streiff
ni.com/compactdaq · ni.com/daq
0 Kudos
Message 3 of 5
(2,410 Views)

@SnowMule wrote:

Development or runtime environment?

 

WinXP or 7?

There's a data loss hotfix for XP with the later DAQmx drivers. 

 

Can you make a new VI and toggle the line high/low in there, or does it only do this in the code you have written?



Thanks for reply.

 

1. Both system (old system with old USB6008 with DAQmx 9.1.7 and new system with new USB6008 with DAQmx 9.3.5)

are Win7.

 

2. System run by our own code.

 

Please let me know if have more suggestions.

 

 

0 Kudos
Message 4 of 5
(2,387 Views)

Thanks for the suggestion.

- It worked!!!

 

The point is rename the Dev#, which is automatically generated.

1. I deleted de-activated Dev1 and

2. Renamed the activated DEV2 (as soon as the usb cable was switched to new USB6008)

to Dev1.

 

Thanks again.

0 Kudos
Message 5 of 5
(2,382 Views)