Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

E3633A connection with RS-232 (Can't READ)

I have a bit of a strange problem with my E3633A Power Supply.  I don't seem to be able to get the Connect Expert to connect properly, to READ from the instrument.

 

My setup is: COM1, 9600, 8, none, 1 (verified on instrument and PC).  I have updated the instrument drivers for the PC.  I have the latest I/O drivers (16.3) and the VISA interface, from Agilent.

 

What I have found so far:

 

1) The first problem comes when I "Add Instrument" to my COM1 port.  After the instrument is found and added to the interface, it has a red X, instead of the green check mark.  The red X has an indication on the right that says, "There was a communication failure"

 

2) I notice is that the IDN string is blank in the connection expert, which suggests it couldn't be read from the instrument.

 

3) I noticed was that if I select the instrument (ASRL1::INSTR), the Interactive I/O option is grayed out.  However, if I create an alias, I can use that line to select the interactive I/O and send commands.

 

4) I have verified that I can send most commands to (Write) the instrument (i.e. *CLS, Volt 12, OUTP ON, etc).  Those seem to work.  One of the commands is self test, and when I Write that command, the instrument does a self test and displays PASS on the PS.

 

5) However, any of the Read commands (IDN?, etc) produce a timeout error, after 15+ seconds.  That error is: VI_ERROR_TMO: A timeout occurred.  I have also used the I/O Monitor to monitor the COM traffic and the only thing that appears not to work are the Read commands.

 

6) The Read timeouts don't produce an error on the Power Supply.  But I have found that multipe Writes will produce the "Error" on the PS.  For instance, if I execute *TST?, followed by another *TST?.  The second one will produce the Error, on the PS.  It still does the tests in both cases but the 2nd one will turn on the Error indicator.  Same for most Write commands.

 

7) I thought it might just be my cable but I tried another with the same results.

 

Any idea what I may have forgotten or what might be wrong? 

0 Kudos
Message 1 of 3
(4,265 Views)

Isn't connection expert an Agilent program? Why are you posting to NI's site?

 

In any case, if you can transmit but not receive, it is either the cable, the instrument, or the port on the pc. You can check both the cable and the pc with a simple loopback test. Short tx and rx at the far end of the cable with the instrument disconnected. Use a terminal emulation program such as Hyperterminal and just start typing. You will receive everything you type if the cable and the pc's port are okay.

0 Kudos
Message 2 of 3
(4,257 Views)

Oh Duh!  You are correct.    I just asked it here because I saw someone else asked a qestion  about this particular instrument, regarding Labview.  I'm trying to use it with Labview too, and am also having connection problems with labview.  But you are correct. I should ask this on the Agilent site.

 

I did jump pin 2 to pin 3 on my cable and used a terminal program to verify that I have loopback. If I remove the jumper, there is no loopback.  So the cable looks good.

 

Thanks,

 

Moderators: Please delete this post.

0 Kudos
Message 3 of 3
(4,252 Views)