Table of Contents
Advertisement
Mini Card / AirCard / Compass USB Driver Developer's Guide
Note: You can customize port
mappings for AC8XX, MC8775,
MC8775V, MC8780, MC8781) in
non-MUX mode using the
AT!NVPORTMAP command.
For details, see the MC87xx
Modem Extended AT
Command Reference
(Document 2130616)
34
AC8XX, MC8775, MC8775V, MC8780, MC8781
•
mode, these modules use endpoints 5‐IN and 5‐OUT to
transport data, and endpoint 1‐IN for flow control of the
host. In MUX mode, they use DLCI‐1 for the data.
C8XX, MC8785V, MC8790, MC8790V, MC8791V, MC8792V
•
non‐MUX mode, these modules use endpoints 5‐IN and
4‐OUT to transport data. In MUX mode, they use DLCI‐1
for the data.
.
Note: (AC8XX, MC8775, MC8775V, MC8780, MC8781) For non-
MUX mode, the recommended configuration of endpoints 2 and 5 is:
2-IN / 2-OUT (Data 1), and 5-IN / 5-OUT (AT). AirCard modems may
need to be reconfigured using AT!NVPORTMAP.
Note: The Heatherington escape method (TIES) is not supported.
This channel supports the transfer of AT commands for
module control, and TCP/IP (or other transport protocol) data
via PPP for network communication.
For lists of supported AT commands, see:
AC595 / A C595U / M C572X
•
·
AT Command Set for User Equipment (UE) (Release 6)
·
AT Command Reference (Document 2130620)
·
Extended AT Command Reference (Document 2130621)
MC87XX
•
·
UMTS Modems Supported AT Commands (Document
2130617)
HIP (Host Interface Protocol)
HIP is a proprietary protocol developed to multiplex different
information types over a single interface (for example, carrying
CnS commands and DM logging data).
The HIP data channel is implemented as follows:
AC59X
•
are typically configured to transport HIP (carrying CnS) or
HIP (carring CnS and DM) messages using endpoints 4‐IN
and 4‐OUT. In MUX mode, they use DLCI‐3 to transport the
data.
Proprietary and Confidential
C59X
MC572X
,
,
—In non‐MUX mode, these modules
— I n non‐MUX
— I n
2130634
Advertisement
Table of Contents
