Specifications

PAD Commands
Rev. 8 May.12 Proprietary and Confidential 245
!PADCONF (continued)
Configure profile trigger conditions for packetization (continued)
<fwdopt> (Forwarding character trigger)
• Packetization begins when the <fwdchar> character appears in the data stream.
• 0=Trigger disabled
• 1=Trigger enabled. Character is included in message.
• 2=Trigger enabled. Character is not included in message.
<fwdchar> (Character that forces packetization to occur.)
• Used in combination with <fwdopt>.
• Valid range: 0–255—ASCII value of forwarding character
!PADCONN
Supporting chipsets:
• MDM6200
• MDM6270: (min f/w rev:
S2.0)
• MSM6290 (min f/w rev:
K2.0 Release 2)
• QSC6270 (min f/w rev:
S2.0)
Note: This command is not
password-protected.
Initiate PAD client connection
Initiate a PAD (Packet Assembler/Disassembler) client connection for a specific profile
ID.
Note: The modem must have a data connection on the network with an open TCP or
UDP socket on the remote agent, and at least one trigger condition must be defined for
the specified profile ID. See !PADCONF on page 244.
Usage:
• Execution: AT!PADCONN=<PADprofile>
Response (multipad not supported):
CONNECT PAD
or NO CARRIER
or ERROR
Response (multipad supported):
OK
CONNECT PAD: <PADprofile>,<connectionState>
or ERROR
Purpose: Initiate a connection for the specified profile. For multipad, the
“CONNECT PAD” response indicates the start of the PAD connection.
• Query: AT!PADCONN?<PADprofile>
Response:
AT!PADCONN:<PADprofile>,<connectionState>
OK
Purpose: Display the current connection state of the specified profile.
Parameters:
<PADprofile> (PAD profile ID number)
• Valid range depends on multipad support:
• Multipad not supported: 1–3
• Multipad supported: 1–10
<connectionState> (Current connection state of the <PADprofile> session)
• 0=Disconnected
• 1=Connected
Table 11-2: PAD command details (Continued)
Command Description