Invalid Responses - Motorola V.3600 User Manual

Access these formats using:
&M Asynchronous dial/asynchronous data
&M1
Asynchronous dial/synchronous data
&M2 Dials stored number when DTR off/on transition is detected/sync data
&M3 Manual dial/sync data
&M4
V.25 bis dialer/BISYNC protocol/sync data (ASCII)
&M5 V.25 bis dialer/SDLC protocol/sync data (NRZ)
&M6 V.25 bis async dial/sync data
&M7 V.25 bis async dial/async data
&M8 V.25 bis dialer w/BISYNC protocol/sync data (EBCDIC)
&M9 V.25 bis dialer w/SDLC protocol/sync data (EBCDIC) (NRZ)
&M10 V.25 bis dialer w/SDLC protocol/sync data (ASCII) (NRZI)
&M11 V.25 bis dialer w/SDLC protocol/sync data (EBCDIC) (NRZI)
• Separator fields depend on the data format.
for ASYNC {sep} = command <CR>
<FCS> where:
<sy> = 16 hexadecimal
<stx> = 02 hex
<etx> = 03 hex
<etb> = 17 hex
<Flag> = 7E hex
<Addr> = FF hex
<ctl> = 13 hex (last frame), 03 hex (not last frame)
<FCS> = Frame Check Sequence
<CR> = Carriage Return

Invalid Responses

Except when stated otherwise, the following explanations for invalid
INV responses apply:
INVCU
Any transmission error (parity, framing, etc.).
INVMS This message has one of three possible meanings:
1) Receiving too many characters for any command.
2) Any command followed by a semicolon ;
BISYNC {sep} = <sy><sy><stx> command <etx>
SDLC {sep} = <Flags><Addr><ctl> command
V.3600
V.25 bis Autodialer
11-3