Messages
The information contained in the topic tabs above covers all the programming
interface messages the instrument generates in response to commands and
queries.
For most messages, a secondary message from the instrument gives detail about
the cause of the error or the meaning of the message. This message is part of the
message string and is separated from the main message by a semicolon.
Each message is the result of an event. Each type of event sets a specific bit in the
SESR and is controlled by the equivalent bit in the DESER. Thus, each message
is associated with a specific SESR bit. In the message tables, the associated
SESR bit is specified in the table title, with exceptions noted with the error
message text.
No Event
The following table shows the messages when the system has no events or status
to report. These have no associated SESR bit.
Table 31: No Event messages
Code Message
0 No events to report; queue empty
1 No events to report; new events pending *ESR?
Command Error
The following table shows the command error messages generated by improper
syntax. Check that the command is properly formed and that it follows the rules
in the section on command Syntax.
Table 32: Command error messages (CME bit 5)
Code Message
100 Command error
101 Invalid character
102 Syntax error
103 Invalid separator
104 Data type error
105 GET not allowed
108 Parameter not allowed
109 Missing parameter
110 Command header error
112 Program mnemonic too long
113 Undefined header
120 Numeric data error
121 Invalid character in numeric
123 Exponent too large
Status and Events
288 TBS2000 Series Programmer
To Next Page
Need help?
General
