How to find/get Input overload condition from HP 35670A

[rann]

How to find/get Input overload condition from HP 35670A. I would like my program to check for Input
overload condition from my program and change the inputs. Are there any HP commands to do this from CVI.

[ScottieB]

Hello,

I'm unclear as to how you are interfacing your HP 35607A to your computer, if you have this setup already or if you are just getting started in setting up communication. If you could clarify that, it would be helpful.

CVI is capable of sending GPIB or Serial commands, if this is what you need. To find out exactly what command is appropriate for your instrument and whether or not gathering the data you would like is possible is up to the instrument manufacturer. Check HP/Agilent's website for a Programmer's Reference Manual as this is a good place to start looking for an appropriate command to send to your HP device. Then, you can look in the CVI samples folder for applications designed to communicate with external devices using the RS232 serial or GPIB
ports.

Scott B.
Applications Engineering
National Instruments

[rann]

HI Scott:
Thanks for the reply.
I currently communicate from my computer to the HP Analyzer through my CVI program. I could send commands and get data back from the HP Analyzer.I have a Programmers reference manual but i could not find a command that would let me know when the Analyzer INPUT conditions are overloaded.

I would like to know if this is possible OR if there are any CVI samples that solve this problem.

Any help or suggestions would be appreciated.

Thanking You,
RAN

[ScottieB]

Hi Ran,

This really depends on what interface you have connecting your device to your computer and also the capabilities of the device itself. If the device will not notify your program via the interface, then you cannot do this. Since you didn't find anything in the instrument's reference manual, it doesn't sound like this is possible if you are connected via GPIB or Serial. I understand that you communicate using your CVI program, but I'm guessing that the program simply makes calls to a hardware driver to send information to the instrument and vice versa. The limitations of what the instrument will respond to on this interface is what is preventing us from completing this task.

Scott B.
Applications Engineer
National Instruments