Problems using IVI Drivers (CVI 8.1 / GPIB-USB-HS)

[-T]

I have a GUI set up that needs to control to Signal Generators through GPIB (USB-HS).  One is an HP8657A an the other is an Agilent E4432B. 

I downloaded drivers from NI for each.  The 8657A was listed as plug and play and with the "load instrument" in the CVI gui I was able to get this working in no time.  However the E4432B was an IVI driver which has me lost.  I have installed the compatability package and driver and then ran MAX.  Under the GPIB device I did a scan and located both devices (address 7 and 19).  In the "Hardware Assets" tree item I created a new item (AgilentE4432B) with the resource setting of GPIB::19::INSTR.  Then I set up a logical name (E4432B) in the "Logical Names" tree item and selected "agesg" for the Drive Session field.  In the "Driver Sessions" tree item for agesg I selected the hardware asset (AgilentE4432B) I created previously.  I saved all of the entries.

In the CVI gui a load the instrument and from the IVI/agesg directory add the agesg.fp.  Then I add the following line in my code:

agesg_InitWithOptions("E4432B",VI_TRUE,VI_TRUE,"Simulate=0,RangeCheck=1,QueryInstrStatus=1,Cache=1",&IDE4432B);

And nothing happens to my SigGen.  Using NiSpy I don't see any commands going to the 4432 only commands to the 8657.  Looking at the example provided with the esg driver I added the checkErr function around the init operation but the pop-up only produces a few invalid characters.

Is there anything obvious about the setup procedure?  Am I missing a step?

Any help appreciated.

[nayer]

Hello T
It looks you did everything correctly well just want to make sure that in MAX you are no simulating the instrument, under the IVI Drivers, I have attached the image that makes it more clear. Also about the spy capture, you will only see NI-VISA commands, and not IVI, if you want to see IVI you can deselect VISA and only select IVI, and then run your program and you will see only IVI calls, following knowledge base will explain you about it.

Try that and let me know how it goes.
Regards
Nikhil A.

[jcmochis]

this issue happen to me one time, and was solve by this option.