Messages; No Event; Command Error - Tektronix TBS2000 Series Programmer's Manual

Status and Events

Messages

No Event

Command Error

288
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.
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
0
1
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
100
101
102
103
104
105
108
109
110
112
113
120
121
123
Message
No events to report; queue empty
No events to report; new events pending *ESR?
Message
Command error
Invalid character
Syntax error
Invalid separator
Data type error
GET not allowed
Parameter not allowed
Missing parameter
Command header error
Program mnemonic too long
Undefined header
Numeric data error
Invalid character in numeric
Exponent too large
TBS2000 Series Programmer