LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI hardware detection

This is more of a conceptual question.

 

I have bought a number of NI USB6008 or similar and I am making various pieces of test equipment with them in. So if I have a user who plugs 2 pieces of equipment in that both contain USB6008's then what is the best way of telling them apart? I.e. which device number links to which piece of equipment. 

 

I could have a look up table for the serial number vs what the test equipment is. The down side to this is that some one will have to manage this look up table. 

 

Any suggestions? 

0 Kudos
Message 1 of 8
(3,104 Views)

Hi shave,

 

even MAX differs between your USB6008 boxes by their serial number, so it should be best to do the same…

 

You can read the serial number using some DAQmx property nodes!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 8
(3,099 Views)

In MAX each device will be assigned an alias.  If you plug in both devices at once they will be given unique aliases, and you can use this to destinguish one from the other.  If you want to do it programatically, and find the alias associated with a device based on the serial number, the DAQmx properties work, or you can use the System Configuration tools to find the hardware with a given set of filter criteria.

Message 3 of 8
(3,077 Views)

Do you have a spare analog or digital input available on each device?

 

You could set the port/line to a specific unique state on each device, read the input value, and thus identify which device is which.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 4 of 8
(3,067 Views)

Wouldn't wiring a specific port to a specific state so you could read this value be a lot more complicated than simply reading a property node, as already suggested?

0 Kudos
Message 5 of 8
(3,053 Views)

@natasftw wrote:

Wouldn't wiring a specific port to a specific state so you could read this value be a lot more complicated than simply reading a property node, as already suggested?


Not necessarily.  If you do this wiring as part of a harness going to a fixture or whatever else, then you have better information.  You know which device should be measuring what.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 6 of 8
(3,041 Views)

Another option is putting a potential divider between 5V+ and GND and measuring the voltage output from the divider on an analogue in. You can have different voltages for different pieces of equipment. This gives you more options on only 1 pin. It depends on your hardware and which pins you need to use. 

 

Ideally I would like a 20 byte storage on the hardware so you can add a device name however I know this isnt going to happen any time soon. 

 

Aliases are a good idea if the hardware is going to be static and always used with 1 PC. Mine will be used on different PC's so I think Im going to go down a look up table with the serial numbers in them.  

0 Kudos
Message 7 of 8
(3,032 Views)

Another option is putting a potential divider between 5V+ and GND and measuring the voltage output from the divider on an analogue in. You can have different voltages for different pieces of equipment. This gives you more options on only 1 pin. It depends on your hardware and which pins you need to use. 

 

Ideally I would like a 20 byte storage on the hardware so you can add a device name however I know this isnt going to happen any time soon. 

 

Aliases are a good idea if the hardware is going to be static and always used with 1 PC. Mine will be used on different PC's so I think Im going to go down a look up table with the serial numbers in them.  

0 Kudos
Message 8 of 8
(3,031 Views)