NI Home
Cart Cart | Help
Hello Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI
You are here: 
NI Home > NI Developer Zone > NI Discussion Forums


Reply
Member
_KL_
Posts: 5
0 Kudos
Accepted Solution

Device name changed but still communicating with the same device

Hi!

 

I have two 6501 NIDAQs that I'm using in two different PCBA test equipments. The names I've given them are "Dev1" and "Dev2".  For some reason they can't be plugged into the same computer at the same time (USB), since my LabView/TestStand application doesn't seem to be able to tell the one from the other.

If I run my first test, using Dev1, and later try to run the second test, now using Dev2, my DAQAssistant - even though I can see that Dev2 is sent to its "DeviceName" - still is communicating with Dev1.

Now, if I unplug either one of them and then run any of the tests, it will crash because of "unnamed task". If I then go to NI Max and just click "Create Task..." and the cancel, it will work until I plug in the other device and disconnect my current one. I now will have to repeat the "Create Task..." step to get my new device to work properly.

Is there anyone who has had a similar problem and have been able to solve it?

Member DsX
Member
DsX
Posts: 32
0 Kudos

Re: Device name changed but still communicating with the same device

Hi,

 

If you create a task in MAX (or DAQAssistant) it also saves device info with that task.

For example: Lets say you create a "Voltage" task with device "Dev1"; you then connect "Dev2". The "Voltage" task won't be able to use "Dev2" because it has "Dev1" channels assigned to it.

 

The solutions would be:

  • create separate tasks for Dev1 and Dev2 and decide in your program which to use,
  • put both devices in one task and simply ignore the data from the other one,
  • use the option to generate DAQmx code and select physical channels each time you start your tests.

These are some of the options of the top of my head, there are probably more.

 

Best regards

Matej

CLAD using LV 8.2, 2010 and 2012
R&D Laboratories
Domel d.o.o.
www.domel.com
Member
_KL_
Posts: 5
0 Kudos

Re: Device name changed but still communicating with the same device

Hi

 

Thanks for the help.

It turns out the problem was the TestStand load option. If I choose to unload every step after the execution of the sequence file, the problem is solved.

 

Regards

Kristian

Member DsX
Member
DsX
Posts: 32
0 Kudos

Re: Device name changed but still communicating with the same device

Hi,

 

Just an update; I'm not sure the second solution will work. I tried something similar and it didn't.

 

Matej

CLAD using LV 8.2, 2010 and 2012
R&D Laboratories
Domel d.o.o.
www.domel.com
By using this web site, you accept the Terms of Use for this web site. Please read these Terms of Use carefully before using any part of this site. Please go here for information on ni.com's copyright infringement policy.
My Profile | Privacy | Legal | Contact NI © 2011 National Instruments Corporation. All rights reserved.    |    E-Mail this Page E-Mail this Page