SECTION 10 SERIAL REMOTE INTERFACE
110
10.5.2 FUNCTIONAL EXCEPTIONS
Some functions applicable with the IEEE-488 interface are NOT applicable with the Serial Interface:
1. All IEEE-488.1 interface functions (5.6.1).
2. IEEE-488.2 commands: *SRE and *SRE?, are ignored, as Service Requests and Serial Polls are
not applicable (5.5.3.1).
(Use *STB? to obtain the Status Byte.)
10.5.3 FUNCTIONAL ADDITIONS
The following commands have been added to replace functions lost due to the lack of the IEEE-488.1
GPIB. These commands are similar to the IEEE-488.2 Common Commands and fall into the category of
DEVICE CONTROL COMMANDS (5.6.2).
Causes a Hardware RESET of the UPC
Puts the UPC into REMOTE with LOCAL LOCKOUT state
10.6 TESTING THE SERIAL REMOTE INTERFACE
1. Connect the UPC Serial Interface to a DTE serial port of a PC using a DB-25 cable. Most 25
pin connectors on PC's are DTE type. The UPC is a DCE type and must connect to a DTE
port. If using a 9 pin connector on the PC, verify the pinouts of the cable match the UPC to the
PC correctly.
2. Configure the PC Baud Rate to 19200 or 9600 Baud, No Parity, 8 Data bits, 1 stop, 1 start bit
using a terminal emulation program. Ensure the UPC is configured the same (10.4). Leave
the EOS set to CR/LF.
3. Enter the UPC STATUS display of the UPC (fn,3,3), do NOT press EDIT this time (5.1). Insert
for info on the COMMUNICATION MONITORING AID. Verify that "RTS" is displayed on the
UPC STATUS display.
4 Send Executable commands from the PC such as :SYST:BEEP, :VOLTS 100, :FREQ 50, and
verify the UPC responds correctly.
5. Send Query commands from the PC such as *IDN?, FETCH:VOLT1?, and verify that the PC
receives correct data from the UPC after each Query command is sent. No other operation is
needed to cause the UPC to send the response data.
To Next Page