Programming Guidelines; Typical Programming Flow For The Tester - Agilent Technologies N9360A Programming Manual

Multi ue tester
Hide thumbs Also See for N9360A:
Table of Contents

Advertisement

4
Programming Command Guidelines

Programming Guidelines

Typical Programming Flow for the Tester

4-10
• Overrun error: A receiver buffer overflows, and received
data is lost. This error is most commonly
caused by too fast communication speed
(Baud Rate). In this case, reduce the
communication speed (Baud Rate).
When you are going to write a test program, refer to the
following guidelines.
• When more than two query commands are sent, the
controller must read the output of each query command from
the Tester. Otherwise, the controller may not be able to read
the output of prior query after the next query is sent to the
Tester.
• To read the measurement results, wait until the
measurement ends. To check the measurement status, read
the Status Byte Register using the *STB? query command
and check the Data Ready Bit (Bit 0) and the Measuring Status Bit
(Bit 1).
• When testing by the Automatic Test mode or the Manual Test
mode, wait until the step of the Test flow ends. To check the
status of the Test flow, send the
TESTs:AUTO:MEASure:SIGNaling:STATe? query
command when the test mode is the Automatic Test mode, or
send the TESTs:MANual:SIGNaling:STATe? query
command when the test mode is the Manual Test mode.
When you write a test program for the Tester, insert the
following steps in your program.
Step 1
Reset the instrument and set the preset settings except for the
setting of serial, GP-IB and Ethernet interface.
< Send Command to the Tester> *RST
Step 2
Select the W-CDMA application, and display the [Initial] screen
of the W-CDMA system.
N9360A Multi UE Tester W-CDMA Programming Manual

Advertisement

Table of Contents
loading

Table of Contents