Specifications
Table Of Contents
- E6392-90042.pdf
- E6392-90042_manual
- Front Matter
- Contents
- 1 Preparing for Use
- 2 Programming Command Guidelines
- 3 Programming Command Reference
- IEEE Common Command
- CONFigure Subsystem
- DISPlay Subsystem
- HCOPy Subsystem
- RFGenerator Subsystem
- SMONitor Subsystem
- SYSTem Subsystem
- TESTs Subsystem for AUTOMATIC TEST
- All Tests Results
- All Tests Results
- Command Reference for Burst Timing/Power Ramp Measurement Screen
- Command Reference for DC Current Measurement Screen
- Command Reference for MS Information
- Command Reference for Peak TX Power Measurement Screen
- Command Reference for Phase/Frequency Error Measurement Screen
- Command Reference for Sensitivity/RX Quality/RX Level Measurement Screen
- Command Reference for Stand-by/Measuring Screens
- TESTs Subsystem for MANUAL TEST
- Command Reference for DC Current Measurement Screen
- Command Reference for Measuring Screens
- Command Reference for MS Information
- Command Reference for Peak TX Power /Burst Timing/Power Ramp Measurement Screen
- Command Reference for Phase/Frequency Error Measurement Screen
- Command Reference for Sensitivity/RX Quality/RX Level Measurement Screen
- Command Reference for Spectrum Monitor Measurement Screen
- Command Reference for Stand-by Screens
- TRIGger Subsystem
- 4 Programming Command Cross Reference
- 5 Example Programs
- A Syntax Diagram
- B Command Difference between E6392A & E6392B
- Index

Chapter 2 23
Programming Command Guidelines
Getting Started with Programming Commands
2. Programming Command
Guidelines
Character Format Parameters
To define the character format, you must know the requirements of the peripheral
device for the following parameters:
• Data Length: Eight data bits are used for each character, excluding start, stop,
and parity bits.
• Stop Bits: One stop bit is included with each character.
• Parity: Parity is disabled (absent) for each character.
Modem Line Handshaking
To use modem line handshaking for data transfer, set the Request-to-Send (RTS)
and Clear-to-Send (CTS) modem lines to active state on your controller.
Setting Xcontrol to Xon/Xoff allows the Test Set to stop data transmission from
the controller when the buffer of the Test Set is full and then start it again when the
Test Set is ready.
Data Transfer Errors
The serial interface can generate several types of errors when certain conditions
are encountered while receiving data from the peripheral device. Errors can be
generated by any of the following conditions:
• Parity error. The parity bit on an incoming character does not match the parity
expected by the receiver. This condition is most commonly caused by line
noise.
• Framing error. Start and stop bits do not match the timing expectations of the
receiver. This can occur when line noise causes the receiver to miss the start bit
or obscures the stop bits.
• Overrun error. Incoming data buffer overrun caused a loss of one or more data
characters. This is usually caused when data is received by the interface, but no
ENTER statement has been activated to input the information.
• Break received. A BREAK was sent to the interface by the peripheral device.
The computer program must be able to properly interpret the meaning of a
break and take appropriate action.