Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Programming Agilent N6700B Trigger with IVI DCPowerSupply

I want to program an Agilent N6700B DCPowerSupply in TestStand.
 
The IVI "Configure" step does not configure the channel voltage trigger mode (which needs to be "STEP" instead of "FIXED").
 
Thus I need to access the IVI attribute.
 
I tried without success to use the names in IVI driver help :
   AGN6700_VAL_TRIGGER_VOLTAGE_MODE_FIXED
   AGN6700_VAL_TRIGGER_VOLTAGE_MODE_STEP
but it doesn't work.
 
Anybody can help ?
 
Is it possible to get the header of Agilent N6700B IVI-C driver ?
 
Best regards,

Jean-Louis SCHRICKE
CTA - Certified TestStand Architect (2008 - 2022)
CTD - Certified TestStand Developer (2004 & 2007)
CLD - Certified LabVIEW Developer (2003 & 2005)

0 Kudos
Message 1 of 5
(4,534 Views)

The driver header file is installed under \Program Files\IVI (or IVI Foundation)\Include.

 

Message 2 of 5
(4,507 Views)

I need the header file for the Agilent N6700B IVI specific driver.
The function i need to call is not in the IVI DCPower Class.

I did the same with niDMM IVI driver. The Offset_Compensated_Ohm is not in the driver class but it can be accessed through the specific driver.

The nidmm.h is in Program Files\IVI\include bit not the agn6700b.h

 

Jean-Louis SCHRICKE
CTA - Certified TestStand Architect (2008 - 2022)
CTD - Certified TestStand Developer (2004 & 2007)
CLD - Certified LabVIEW Developer (2003 & 2005)

0 Kudos
Message 3 of 5
(4,498 Views)
Did you do a search for the .h file? I just downloaded and installed it and it is in the \program files\ivi\include. In the past, ivi drivers were installed in \vxipnp\winnt\include so you can look there as well.
Message 4 of 5
(4,491 Views)
All IVI specific drivers get installed in \program files\ivi\include. NI IVI-C drivers also get installed in VXIpnp directory. Therefore, if you are not able to find the agn6700.h file in both directories, there is probably something wrong with the specific driver installation. You should uninstall the driver from Add/Remove Programs and try to install it again. 
Message 5 of 5
(4,473 Views)