Specifications

Remote Diagnostics and Debugging
Performing Remote Diagnostics 109
Remote Diagnostics Using a Direct Cable Connection
Developers of Omni 3200 applications and diagnostic test programs
can perform remote diagnostics on-site using a direct cable
connection. This method is much faster than telephone diagnostics,
with a data transfer rate up to 19200 baud.
The hardware and software environment required for direct
diagnostics is very similar when performing diagnostic tests and
when debugging applications:
• The diagnostic computer must be running a diagnostics test
program or a debugging program
• The terminal must have a variable stored in its CONFIG.SYS file
under the search key, *D. (For more information about the *D
variable, see below.)
• The diagnostic computer and the terminal must be connected by a
serial cable.
The *D Variable in CONFIG.SYS
Before you can perform direct remote diagnostics or debugging, you
must enter variable data in the terminal’s CONFIG.SYS file under the
search key, *D. This variable determines the terminal port and baud
rate to be used for diagnostics.
To enter the *D variable in CONFIG.SYS, you must enter System
Mode, activate the keyed file editor by pressing the [7] key, and type
in the record key and variable. If you do this, and then exit System
Mode, the terminal restarts and automatically enters Direct
Diagnostic Mode.
Note: In Direct Diagnostic Mode, the terminal surrenders control to
the remote diagnostic or debugging computer. This means that when
the *D variable is set, the terminal application cannot run. To run the
application, you must remove the *D variable from the terminal’s
CONFIG.SYS file, so that *D=(empty).
O3200 RM Book.book Page 109 Thursday, April 29, 1999 3:48 PM