Highland T560, Technical Manual

Page: 22 / 49

22 T560MANK5.DOCX
command sends its reply characters, typically a requested value or the
OK
response, as the
command is executed. Any additional incoming characters following the command-line <cr>
are ignored until the entire command line is processed and the final response-line <cr> <lf>
is returned.
Most simple commands execute in hundreds of microseconds, and their realtime execution
rate is dominated by the 38.4 kbaud (3840 characters/second) serial communications rate.
Shortform commands reduce communications overhead. Long reports are of course baud
rate limited, with the
STatus
report or the longer
HElp
pages taking as long as 500
milliseconds.
When delay/width settings are changed via the
INstall
command (or an end-of-line
autoinstall) or the trigger, burst, or gate parameters are changed, the firmware will
immediately force the end-of-delay reset state, which will abort any timing cycles currently
in progress. EOD will be asserted for about 350 microseconds, after which triggers will be
re-enabled.
If aborting timing cycles is undesirable, one can disable triggers, wait until any possible
timing cycle has finished, then do the desired operation. For example, if it were known that
all delay+width settings total under 40 milliseconds, one could send the T560 the
sequence...
TRIGGER OFF; WAIT 50000; CDELAY 2.5m; INSTALL; TRIGGER POS
to which it would reply
OK;OK;OK;OK;OK
with an additional 50 millisecond pause before the second
OK
.
One can also use the realtime USEC counter to measure actual command execution times
in microseconds...
US 0; SY 3.579545M; US
which might respond
OK;OK;0,000,001,128
Again, command execution times are usually dominated by the 38 kbaud communications
rate.