14-4 Common Commands
E) TRG — trigger Send bus trigger to Model 6514
Use the *TRG command to issue a GPIB trigger to Model 6514. It has the same effect as a
group execute trigger (GET).
Use the *TRG command as an event to control operation. Model 6514 reacts to this trigger if
BUS is the programmed arm control source. The control source is programmed from the
TRIGger subsystem.
NOTE Details on triggering are covered in Section 9.
Programming example — The following command sequence configures Model 6514 to be
controlled by bus triggers. The last line, which sends a bus trigger, triggers one measurement.
Each subsequent bus trigger will also trigger a single measurement.
*RST ‘ Restore RST defaults.
ARM:SOUR BUS ‘ Select BUS control source.
ARM:COUN INF ‘ Set arm layer count to infinite.
INIT ‘ Take 6514 out of idle.
*TRG ‘ Trigger one measurement.
F) TST? — self-test query Run self test and read result
Use this query command to perform a checksum test on ROM. The command places the
coded result (0 or 1) in the output queue. When Model 6514 is addressed to talk, the coded result
is sent from the output queue to the computer.
A returned value of zero (0) indicates that the test passed, and a value of one (1) indicates that
the test failed.
G) WAI — wait-to-continue Wait until previous commands are completed
Effectively, the *WAI command is a No-Op (no operation) for Model 6514 and thus, does not
need to be used.
Two types of device commands exist:
• Sequential commands — A command whose operations are allowed to finish before the
next command is executed.
•Overlapped commands — A command that allows the execution of subsequent com-
mands while device operations of the overlapped command are still in progress.
The *WAI command is used to suspend the execution of subsequent commands until the
device operations of all previous overlapped commands are finished. The *WAI command is not
needed for sequential commands.
To Next Page
Loading...
Need help?
General
