Introduction
Last updated: May 8, 2002
The Getting Started Guide is organized around the basic set of tasks a control program normally performs when testing a mobile station in a manufacturing environment.
Click on any step in the flowchart below to learn more about how to program the Agilent Technologies 8960 to perform these tasks.
Programming Flowchart
You can also use the buttons on each page to navigate between steps, return to the flowchart, or to find more detailed information about each step.
Conventions used in this Getting Started Guide
Throughout this Getting Started Guide the term "test set" refers to an Agilent Technologies 8960 Series 10 wireless communications test set with the E1960A GSM mobile test application installed.
The variable
Test_set
used in the steps of the Getting Started Guide refers to the test set's GPIB address.
How to use this Getting Started Guide
The most effective way to use this Getting Started Guide is with the Programming Flowchart included inside this guide and the 8960 User Documentation. This documentation is found in two locations:
-
the 8960 Family Support Site (updated frequently) on the Internet, or
-
the User Documentation CD-ROM shipped with your test application.
Each step on the Programming Flowchart is illustrated with example program code in this guide. Using this Getting Started Guide, the Programming Flowchart, and the on-line information about 8960 programming, you will be able to generate a control program to perform fundamental mobile station manufacturing tests.
Useful on-line links
Go to the 8960 Family Support Site on either the CD-ROM or the Internet. The CD-ROM should self-launch to its home page. The URL for the website is:
www.agilent.com/find/8960support/
Navigate to the Programming page for this test application. The illustrations on the back of the Programming Flowchart show you how to navigate to this page.
The following links are under the heading Getting Started on the Programming page:
-
Programming: Getting Started Guide
-
This online version of this guide contains links to more detailed information about each step which may be useful as you develop your control program.
-
Control Program Examples
-
These examples are for you to download. You may want to use these as templates for your own control program or to execute.
-
The control program explained in the Getting Started Guide is also available here for you to download. It is a fully functional control program.
About the Programming Examples Presented in this Guide
Programming Language:
Programming examples presented in this guide are written in the HP BASIC programming language, also known as RMB or Rocky Mountain BASIC. The use of HP BASIC is not an endorsement of the HP BASIC product.
Line Numbers
All of the programming examples in the guide with line numbers are sections from a control program example available on-line for you to download.
Code that is not part of the download control program example does not have line numbers. This code may represent an alternate method of performing the task or may illustrate a feature not used by the control program example.
Syntax used in Programming Examples:
-
The programming examples use the shortened form of the command syntax to minimize GPIB bus transactions. The shortened form of a command is defined by use of capital letters in the command syntax. For the command syntax:
RFANalyzer:CONTrol:MEASurement:FREQuency:AUTO?
the shortened form would be:
RFAN:CONT:MEAS:FREQ:AUTO?
-
The programming examples do not include optional nodes. Optional nodes in the command syntax are defined by enclosing the node inside the [ ] brackets. For example, the command syntax:
CALL[:CELL]:POWer[:SAMPlitude] -80dBm
appears in the programming examples as:
CALL:POW -80dBm
-
Programming examples make extensive use of compound commands using the ; and the ;: separators. Refer to the on-line information for the definition and use of these command separators.
Complex Commands
Complex commands are used to configure the state and assign values to parameters simultaneously. Complex commands can be used to save programming steps and minimize GPIB bus transactions.
-
The syntax below turns the state of the parameter on.
OUTPUT Test_set;"SET:DTXP:TIM:STAT ON"
-
The syntax below is used to assign a value to the parameter.
OUTPUT Test_set;"SET:DTXP:TIM:TIME 10 S"
-
Both of the above actions can be accomplished with one syntax command:
OUTPUT Test_set;"SET:DTXP:TIM:STIM 10 S"
The command above sets the parameter state to ON and the value of the parameter to 10 seconds. Note that in this example the optional command mnemonic :STIMe has been included to clarify that this complex command was used to set both the state and the value.
-
This command can be shortened further by removing the optional command mnemonic :STIMe, as shown below.
OUTPUT Test_set;"SET:DTXP:TIM 10 S"
This is the format that will be used throughout this guide.
