Table of Contents
Advertisement
Iridium Communications, Inc.
Iridium 9523 Product Developers' Guide
Revision 2.6
0
No error
2
Session completed but the requested Location Update was not accepted
3..14
Reserved, but indicate Location Update failure if used
15
Access is denied
Iridium 9523-reported values:
16
Modem has been locked and may not make SBD calls (see +CULK command)
17
Gateway not responding (local session timeout)
18
Connection lost (RF drop)
19
Link failure (A protocol error caused termination of the call)
20..31 Reserved, but indicate failure if used
32
No network service, unable to initiate call
33..34 Reserved, but indicate failure if used
35
Iridium 9523 is busy, unable to initiate call
36
Try later, must wait 3 minutes since last registration
37..
Reserved, but indicate failure if used
Read Command: +SBDAREG?
Query the current automatic MT registration mode. The response is of the form:
+SBDAREG:<mode>
Test Command: +SBDAREG=?
List the supported mode settings. The response is of the form:
+SBDAREG:(supported <mode> settings)
5.7.111 +SBDSX - Short Burst Data: Status Extended
Exec Command: +SBDSX
This command returns current state of the mobile originated and mobile terminated buffers, and the SBD
ring alert status.
Command Response:
+SBDSX: <MO flag>, <MOMSN>, <MT flag>, <MTMSN>, <RA flag>, <msg waiting>
where:
<MO flag>:
The MO flag indicates the existence of a message in the mobile originated buffer. The response from the
Iridium 9523 is one of the following numeric codes:
0
No message in mobile originated buffer
1
Message in mobile originated buffer
<MOMSN>:
The MOMSN identifies the sequence number that will be used during the next mobile originated SBD
session.
<MT Flag>:
Iridium Communications, Inc.
Proprietary & Confidential Information
Only
Information Contained in this Guide
is Subject to Change Without Notice
Page 85 of 115
Distribution of Guide Restricted
to Product Developers
Advertisement
Table of Contents
