Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

LabWindows\CVI "C" NI Driver for Associated Research (AR) 7650 HIPOTUltraIII IEEE 488.2 (GPIB)

The HPultra.c file contains a command call "HPultra_FindTester (int *model,
                         int *tester_interface, int *testerCOM, int *testerAddr)".

The HPultra_FindTester funnction contains an "INIFILE" read satement: tag = getenv ("INIFILE"); this requires an INIFILE which is not part of the driver package and not defined.  The resultant "tag" string becomes a {NULL} set, and an error message results : (-50, "Cannot find INI file path"), erroring out of the driver.

 

AR is not aware of the INI file omission.

 

How is the "INIFILE" generated and how is it included in order for the arhpultra.zip to communicate with the instrument?

 

0 Kudos
Message 1 of 2
(3,445 Views)

Hi fdrgski,

 

The INI format is common and fairly easy to use.  The code is looking for values from this INI file, for example Comport.  You can put together the .ini file based on the values the code is expecting.  Here is a link to more information on .ini files: http://en.wikipedia.org/wiki/INI_file

 

Cheers, 

0 Kudos
Message 2 of 2
(3,418 Views)