DART 200 CDPD Modem User’s Guide 5 DART Supported Protocols
Sierra Wireless, Inc. 5-12
Table 5-1. Remote UDP setup (cont.)
AT Command Req Opt Def Description
ATE0 ONo command mode character echo
ATV0 OUse terse result codes
ATQ0 DUse default - Result codes are sent to
the RTU
ATF1 DUse default - Do not echo transmitted
data to the RTU
ATX1 DUse default - Extended result codes
AT&C1 DUse default - DCD follows state of
the connection
AT&D0 DUse default - You may want to
consider using DTR to escape if RTU
supports it
AT&E2 OFilter escape sequence from output
AT&S0 DUse default - DSR is always active
AT\F3 DUse default - Applies only if \M1
specified
AT\M0 DUse default - Do not recognize data
forwarding characters
AT\Q0 OMost RTUs do not use flow control
AT\T1 DTimed data forwarding - Always use
with binary data
AT*B0 DUse default - Many CDPD Carriers
have not implemented Broadcast.
AT*C1 DUse default - Does not apply to UDP
AT*G1 DUse default - Does not apply to UDP
AT*K0 DUse default - Does not apply to UDP
AT*R0 DUse default - Does not apply to UDP
AT*T0 DUse default - Does not apply to UDP
Host UDP setup
The host (client) modem is set up to support polling of remote devices by
the host computer. The specific host uses flow control and the data being
sent is binary, not character, data. The polling function does not require
the UDP server, but requires flow control, and timed data forwarding
because of the binary data.
Use this setup only for bench testing or a limited use trial. A production
application uses a leased line, frame relay, or Internet connection
between the host and the MDIS instead of a modem. In the latter
scenario, the production host application needs to interface with a
software stack (replacing the modem stack to operate with the CDPD
network).
In Table 5-2, only the line items marked with an R or an O are changed
from the default (D). After making changes, save them with an AT&W.