V.25 bis Autodialer

&M3Manual dial/sync data

&M4V.25 bis dialer/BISYNC protocol/sync data (ASCII) &M5V.25 bis dialer/SDLC protocol/sync data (NRZ) &M6V.25 bis async dial/sync data

&M7V.25 bis async dial/async data

&M8V.25 bis dialer w/BISYNC protocol/sync data (EBCDIC) &M9V.25 bis dialer w/SDLC protocol/sync data (EBCDIC) (NRZ) &M10V.25 bis dialer w/SDLC protocol/sync data (ASCII) (NRZI) &M11V.25 bis dialer w/SDLC protocol/sync data (EBCDIC) (NRZI)

Separator fields depend on the data format.

for ASYNC {sep} = command <CR>

BISYNC {sep} = <sy><sy><stx> command <etx> SDLC {sep} = <Flags><Addr><ctl> command

<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:

INVCUAny transmission error (parity, framing, etc.).

INVMSThis message has one of three possible meanings:

1)Receiving too many characters for any command.

2)Any command followed by a semicolon ;

INVPSThis message has one of three possible meanings:

1)Any parameter set ending with a semicolon ;

2)Any parameter set containing too many or not enough parameters; this includes

-any command entered without parameters that requires parameters

-any command entered with parameters that

does not require parameters.

Modem 3600

11-3

Page 177
Image 177
Black Box 3600 MODEM manual Invalid Responses