PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI-8232 how do I change GPIB Device ID programmatically?

We build hundred of systems using multiple PXI-8232 cards. The cards are always installed in specific slots, and are cabled to different destinations. I have been able to figure out how to identify which card is which using the system configurator (version 15), and can set the network settings ok, but for the life of me I can't figure out how to change the GPIB device IDs to the correct order (i.e. from GPIB2,GPIB0,GPIB1 to GPIB0,GPIB1,GPIB2). I looked at exporting and importing the configuration with changes, but couldn't get it tor work for some reason. Am I missing something? Is there a registry hack to do this?

 

Thanks!

0 Kudos
Message 1 of 4
(3,861 Views)

Just to get more information from you, what software and OS are you working with? Are you using LabWindows CVI or LabVIEW? Also, I'm not sure what you mean by system configurator v15. Do you mean NI-MAX or the NI System Configuration API? Additionally, have you tried using these KBs:

 

Can I Give My GPIB Instruments Custom Names?

http://digital.ni.com/public.nsf/allkb/C063FA3D7C71CE80862569B60074F4A6

 

Renaming a GPIB Device (Device Template) in the NI-488.2 for Windows Version 2.x Driver

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/f105528e876b22c986256ba3005cbd9c?O...

 

 

0 Kudos
Message 2 of 4
(3,846 Views)

We are currently using a mix of Windows XP and Windows 7 systems. The configuration and installation of the system is performed by scripts, and we are trying to eliminate this manual configuration step as it takes time to sort it out and introduces human error. Currently we are using VS2010 applications when we can't use VBS or PowerShell. If I have to create some kind of exe using LW/CVI or LV then I can, but I'm trying to avoid that (we don't use LV for anything, but have licenses). I have been looking at the System Configuration API as a means to do this, but the only thing I have found so far is creating an alias. I would rather change the device ID based on the slot like I can in MAX as we open VI sessions with a wide number of instrments using the GPIB<x>::<address>::INSTR resource string. Having to create custom aliases for everything based on each system seems like an added level of complexity that I'd like to avoid.

0 Kudos
Message 3 of 4
(3,835 Views)

The NI System Configuration API seems like your best bet. If you want to use LabVIEW, here is the list of System Config VIs:

 

NI System Configuration VIs

http://zone.ni.com/reference/en-XX/help/373107E-01/TOC2.htm

 

You can probably use this to get information about the slot:

http://zone.ni.com/reference/en-XX/help/373107E-01/nisyscfg/property_node_hardware/

 

And then use Rename Alias.vi to rename the device:

http://zone.ni.com/reference/en-XX/help/373107E-01/nisyscfg/rename_alias/

 

If you would prefer to use LabWindows CVI, here are the function references:

http://zone.ni.com/reference/en-XX/help/373242H-01/

 

NISysCfgGetResourceProperty:

http://zone.ni.com/reference/en-XX/help/373242H-01/nisyscfgcvi/nisyscfggetresourceproperty/

 

Resource Property Descriptions:

http://zone.ni.com/reference/en-XX/help/373242H-01/nisyscfgcvi/prop_hw/

 

NISysCfgRenameResource

http://zone.ni.com/reference/en-XX/help/373242H-01/nisyscfgcvi/nisyscfgrenameresource/

 

Let me know if this helps.

 

0 Kudos
Message 4 of 4
(3,831 Views)