Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem initializing Spectrum Analyzer Agilent E7404A with agesa drivers

Hi,

I am trying to control an Agilent E7404A Spectrum Analyzer with Labview 2011 SP1. I'm using a GPIB connection,and I've installed the agesa drivers and GPIB drivers and the instrument actually can communicate with labview. 
When I run the vi (screenshoot attached on this message) labview returns to me the following error

"Driver Status: (Hex 0xBFFA0010) Primary Error: (Hex 0xBFFA0010) Invalid value for parameter or property." (I've attached the screenshoot of this error too)  

 

here my settings in the initizialize with option.vi :

resource name: GPIB0::18::INSTR            (verified with Mesurement & Automation)

id query "true"
reset device "true"

option strin:  Simulate=0,RangeCheck=1,QueryInstrStatus=1,Cache=1

 

 

 I can't figure out what is the problem, the instrument can communicate whit labview but the intialize vi returns me that error and the vi stops.
I thank you in advance for any help.

Best regards,


Simone 

 

Download All
0 Kudos
Message 1 of 5
(3,705 Views)

This is what happens when one blindly uses a driver without understanding what commands are being sent.

 

Compare what is command is being sent with what commands are allowed (read the programmer's manual).

 

0 Kudos
Message 2 of 5
(3,698 Views)

I would say open up the initialize.vi and run the vi in debug mode and see where it generates the error.

greetings from the Netherlands
0 Kudos
Message 3 of 5
(3,687 Views)
Since it's an IVI driver and since it seems related to a property, pretty doubtful it has anything to do with a command. Make sure you have the IVI Compliance Package installed and add the instrument as an IVI instrument on MAX.
0 Kudos
Message 4 of 5
(3,679 Views)

There is a powerful tool called "NI IO Trace" to debug the IVI driver and see which attribute caused this error. Please start the trace function during the time you run your instrument control VI. Then you could analyze the results to figure out the root cause of that error. Probably, it is caused by a out of range input of a parameter.

 

You could try it from Start >> Programs >> National Instruments >> NI IO Trace.

0 Kudos
Message 5 of 5
(3,671 Views)