I am currently using the 81150A and am encountering a strange error. I have a GPIB interface setup and programmed a set of instrument commands I need. I had it all working on the machines I was programming on, and had an install package and everything for a second machine.
Now though, on the second machine, I am getting a strange error.
FGPG is my Agilent81150Class object, and the interface seems to be referring to channel 2 (it is a channel call this is getting hung up on). I removed the [...], it was referencing the specific address of the instrument.
Anyone encounter this before? It compiles perfectly, and I have tested the same setup with a different 81150A and still get the same error. This would indicate there is a problem with the IVI drivers (it seems), but this machine has the exact same ones I was using...
Now though, on the second machine, I am getting a strange error.
FGPG is my Agilent81150Class object, and the interface seems to be referring to channel 2 (it is a channel call this is getting hung up on). I removed the [...], it was referencing the specific address of the instrument.
Anyone encounter this before? It compiles perfectly, and I have tested the same setup with a different 81150A and still get the same error. This would indicate there is a problem with the IVI drivers (it seems), but this machine has the exact same ones I was using...
My advice would be to first check the installed SW as the Agilent IO library is always needed, and installing the latest version is always a good idea
Some customers which have National Instruments libraries installed, encountered problems when using the Agilent SW, so Agilent IO Libraries is recommended. Also having both libraries instaleld at once can results in unexpected problems.
Then the normal 81150A IVI COM SW package needs to be installed.
One of the first steps to verify that everything is working properly is to run the Agilent interactive IO software and send a *IDN? SCPI command to the instrument.
Also verifying the GPIB address is matching between SW and HW or using a USB connection between PC and instrument could help to narrow down the problem!