Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

MAX does not see PCMCIA-GPIB or GPIB-USB-B

Solved!
Go to solution

I am using a legacy Windows XP SP3 system with MAX 3.1 and NI-488.2 V2.1. I use either a PCMCIA-GPIB card or a GPIB-USB-B.

 

When logged into an administrator account there are no problems; both devices appear in MAX and in the WIndows device manager.

 

When logged into a user account with limited privileges, the devices appear in the WIndows device manager, but not in MAX, but the VIs and compiled EXEs I user still operate correctly. However, if I convert the user account to an admin account the devices are visible, but this is not a solution because 'Security'.

 

The problem lies within the compiled EXEs as their respective VIs have been lost over time and the address of the PCMCIA or USB interface are hardcoded, and are not the same in all EXEs. I would appreciate any insight you may have.

0 Kudos
Message 1 of 6
(5,635 Views)
I don't know what problem you are trying to solve. You say the VIs and exe's operate properly. Only an admin should be able to change properties and you seem to agree with the security it provides.

The address of the gpib controller should always be left as the default of 0 so I really am confused by your last statement. Do you really mean the address of the instruments?
0 Kudos
Message 2 of 6
(5,632 Views)

Apologies.

 

The actaul problem I'm trying to solve is that when logged into a user account with limited privileges, the PCMCIA-GPIB and GPIB-USB devices appear in the WIndows device manager, but not in MAX.

0 Kudos
Message 3 of 6
(5,602 Views)
But what is the problem with not seeing it? You said the programs work. What do you want the user to do?
0 Kudos
Message 4 of 6
(5,597 Views)
Solution
Accepted by Maelmorde

Hi Maelmorde,

 

If some features aren't working for users with reduced privileges you may need to grant them privileges to the National Instruments installation directory, the method is detailed in the KB article here.

 

I'd recommend trying this to see if it helps.

Message 5 of 6
(5,589 Views)

Thanks for that article. Changing the permissions on the NI folder and a reboot sorted it. You have my gratitude.

0 Kudos
Message 6 of 6
(5,556 Views)