EXFO FTB-1v2 - Consulting Data Types

Using Your Unit and Modules in an Automated Test Environment
FTB-1v2 and FTB-1v2 Pro 263
Consulting Data Types
There are also several conventions regarding command syntax:
 Spelling errors will cancel the command or query.
 Commands and queries are not case-sensitive. You can type your
program messages using either lower-case or upper-case letters.
 The command or query can be written using only the three- or
four-letter shortcuts, only full words, or a combination of both.
The example below shows the long and the short forms of a same
query.
Consulting Data Types
If you need information about data types used in EXFO’s documentation,
see the appendix on data types.
;
 Mandatory to separate the different commands of a program
message when more than one command is sent at a time. In this
case, it is called <PROGRAM MESSAGE UNIT SEPARATOR>.
 Also used to separate responses when multiple queries were sent in
a single program message. In this case, it is called <RESPONSE
MESSAGE UNIT SEPARATOR>.
,
 Mandatory to separate parameters in a command or a query. In this
case, it is called <PROGRAM DATA SEPARATOR>.
 Also used to separate the various responses from a query. In this
case, it is called <RESPONSE DATA SEPARATOR>.
Item Meaning
:SYSTem:ERRor?
:SYST:ERR?
:syst:err?
Long form
Short form (small words
represented by the capital letters
of the long form)