Connect Agilent 33220A to computer, and showed in MAX, but 33220A not in remote mode？

[PeterChen]

I connect the Agilent 33220A to my computer through Agilent 82357B USB-GPIB cable. Both Agilent connection expert (Agilent IO control) and NI-MAX can detect the equitment and query the *IDN? successfully, but the display board of Agilent 33220A shows it is not in remote mode. Is it matter? Or how can I activate the remote mode of Agilent 33220A?

[GerdW]

Hi Peter,

to force a GPIB device into REMOTE mode you could try some LLO (LocalLockOut) command.

Or you read the manual of your device for some more detailed explanations…

[PeterChen]

Thanks for your answer. I try LLO, but seems 33220A can not recognize it. I also check the mannul and can not find any related command.

The weird thing is that sometimes 33220A can in remote mode automatically, but sometimes not. When 33220A shows not in remote mode, I still can query *IDN? successfully.

[GerdW]

Hi Peter,

the manual of your device should explain how to go into Remote mode and also how to get back to local mode!

GPIB devices usually respond to GPIB request even in local mode. Some of them automatically go into remote mode when they receive GPIB request. And other devices need a special command to go into Remote/Local mode.

But the bottom line is: all the GPIB devices I used so far had a manual with explanations on this very topic! (RTFM!)

[PeterChen]

Thanks for you suggestion, I find the command finally, it is SYSTem:REMote.

Now I write a new program, showed as below:

I can successfully run the program and 33220A also doesn't report any errors.

But the problem is that I can not receive any string and the numeric indicator also shows 0.

I try to write reset commad, I find 33220A can reset.

Above all, now my situation is that 33220A can not send information back...............

Note:

 I do not understand that why there is a coercion dot in VISA read function.

Many thanks!

[GerdW]

Hi Peter,

Note: I do not understand that why there is a coercion dot in VISA read function.

Because YOU didn't use the correct datatype for that constant!

(Or you created that constant the wrong way. Did you right-click the input of VISARead and selected "Create Constant"?)