Models 707B and 708B Switching Matrix Reference Manual
Section 7: TSP command reference
707B-901-01 Rev. B / January 2015
7-123
localnode.prompts
This attribute determines if the instrument generates prompts in response to command messages.
Type
TSP-Link accessible
Affected by
Where saved
Default value
Attribute (RW)
Yes
Power cycle
Not saved
0 (disabled)
Usage
prompting
= localnode.prompts
localnode.prompts =
prompting
prompting
Do not generate prompts:
1
Generate prompts:
0
Details
When the prompting mode is enabled, the instrument generates prompts when the instrument is
ready to take another command. Because the prompt is not generated until the previous command
completes, enabling prompts provides handshaking with the instrument to prevent buffer overruns.
When prompting is enabled, the instrument might generate the following prompts:
•
TSP>.
The standard prompt, which indicates that the previous command completed normally.
•
TSP?.
The prompt that is issued if there are unread entries in the error queue when the prompt is
issued. Like the TSP> prompt, it indicates that processing of the command is complete. It does
not mean the previous command generated an error, only that there were still errors in the queue
when the command processing was complete.
•
>>>>.
The continuation prompt, which occurs when downloading scripts. When downloading
scripts, many command messages must be sent as a group. The continuation prompt indicates
that the instrument is expecting more messages as part of the present command.
Commands do not generate prompts. The instrument generates prompts in response to command
completion.
Prompts are enabled or disabled only for the remote interface that is active when you send the
command. For example, if you enable prompts when the GPIB connection is active, they will not be
enabled for a subsequent USB connection.
Do not disable prompting when using Test Script Builder. Test Script Builder requires prompts and
sets the prompting mode automatically. If you disable prompting, the instrument will stop responding
when you communicate using Test Script Builder because it is waiting for a common complete
prompt from Test Script Builder.
Example
localnode.prompts = 1
Enable prompting.
Also see
(on page 7-124)
(on page 7-127)
(on page 7-217)
