Manual

18-4 Appendix H
If you are using Hardwired DTR, be sure the Automove's Pin 20 is connected to the host's
Pin 4 or Pin 5 (if the host is a DTE) and that either the interface hardware or the software
stops transmitting when this handshake line goes low.
If you are using Xon/Xoff or Enq/Ack, be sure you have sent the correct escape sequences to
set up the handshake; see Chapter 5 and 6. Also be sure your host software responds quickly
to the particular Xoff character you have set up in the Automove System.
Be sure the host computer operating system or low-level driver software is not interfering
with what the application program is trying to send to the Automove System. For example,
the driver might not be passing through the escape sequences or handshake characters, or
might be inserting Carriage Returns or Linefeeds in the middle of escape sequences.
Downloading Doesn't Work
Perhaps the rear-panel Write Protect switch is disabling non-volatile memory writes; flip it
to the Down position to enable them.
The download sequences may be too large, or old download sequences (under different <id>
numbers) might be occupying part of the memory. Use
ESC.S2: to find out how much
memory is available, or
ESC.S5;n: to find out how much memory sequence "n" uses. Use
ESC.!7: to be sure the memory is clear.
Part of the download memory may have become corrupt or inaccessible due to a reset or
power failure during downloading. If you have erased sequences 0 through 255 (by sending
BD 0; ED; BD 1; ED; ... BD 255; ED; ) and some memory is still unavailable, use
ESC.!7:
to recover the lost memory.
You may have used the wrong download sequence number, or used the number twice, thus
overwriting the old sequence with the new.
In general, it is a good idea to execute and debug your move sequence before downloading
it. Some errors are not caught during downloading, but instead occur when the download
sequence is executed. If you don't have a computer or terminal hooked up to the Automove
System at that time, you won't see the "?".
Download Sequences Don't Seem To Execute Correctly
Try inserting debugging commands into the Download Sequences with the OU ("Output
Literal String") command. Run the move sequence with a host computer connected to the
RS-232C port, running a terminal emulator program.
The OU shows that execution reached that point. If you follow the OU with an OA, OE,
OV, or other output command, you can get a better idea of what the move sequence is doing.