13 TRX
167
13.3
DUmp
Default setting: 0
Parameter: 0 Dump
mode
disabled.
1
Dump
mode
enabled.
With the command
Dump
1
<Return>, the PTC-IIIusb is switched to transceiver dump
mode, this mode providing a very simple Host mode for direct communication between
the terminal program and the transceiver. The PTC-IIIusb only serves as a level converter
or baudrate converter, and delivers, as required, the necessary signal preamble (for SGC
transceivers), but the actual control sequences must be delivered by the host computer, or
terminal program. In dump mode, the information given out by the transceiver is
transferred direct to the host computer, and must be processed there.
TRX dump sequences from the host computer (terminal) to the PTC-IIIusb have the same
format as the TRX dump sequences from the PTC-IIIusb to the host computer, these
consisting of:
1.
TRX dump header, for unambiguous recognition of the TRX dump sequences.
2.
The actual data field, in hexadecimal form, (identical to the data field when using the
Transfer command for SGC, ICOM and YAESU).
3.
The end character, CR, (ASCII 13).
Dump sequences always begin with the TRX dump header, this header consisting of the
following; <Ctrl-E><#><T><X><:>, where <..> denotes in each case one byte (ASCII),
corresponding to 05H 23H 54H 58H 3AH.
The header is only then valid when it appears complete. If, for example, the third header
byte is defective, then the PTC-IIIusb behaves as if the Ctrl-E start character is an
accidental Ctrl-E, or an actual Ctrl-E that has not been input as a TRX control character,
the PTC-IIIusb then sending the buffered characters of the intended dump header into the
normal command interpreter or transmit buffer.
If one types, for example, Ctrl-E#TXXX, during an actual PACTOR link, then these
characters would be transmitted over the HF link, and would not be transferred to the
transceiver.
A restrictive processing of the header allows through transfer of transceiver sequences,
WITHOUT, in practice, limiting the data transparency, the danger of a piece of text being
swallowed
, due to an accidental Ctrl-E is virtually 0.
The host computer, or terminal program, should, naturally also thoroughly check the
transferred TRX dump sequence, and a "defective" header should be fed back into the
normal process, (e.g. output as text in the receive window).
The dump header can be followed by up to 256 bytes (or 512 places) of actual transfer
information in hexadecimal form, spaces in this data field being ignored, and if an uneven
number of hexadecimal places (nibbles) are given, then the PTC-IIIusb ignores the last
nibble.