Iridium Satellite 9602 Iridium Satellite Transceiver Module 9602 User Manual manual

Iridium Satellite LLC Iridium Satellite Transceiver Module 9602 manual

manual

Download:
Mirror Download [FCC.gov]
Document ID	1265166
Application ID	kFdiD36oULwuys99r9lgVQ==
Document Description	manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	38.02kB (475210 bits)
Date Submitted	2010-04-12 00:00:00
Date Available	2010-04-12 00:00:00
Creation Date	2010-03-10 14:44:03
Producing Software	Acrobat Distiller 7.0.5 (Windows)
Document Lastmod	2010-03-10 14:44:03
Document Title	Microsoft Word - 9602 SBD Transceiver Product Developers Guide v4_0.doc
Document Creator	PScript5.dll Version 5.2.2
Document Author:	mc3

>>>>>>>>>>>>>DRAFT COPY ONLY<<<<<<<<<<<
RELEASE RESTRICTED TO PRODUCT DEVELOPERS ONLY
9 6 0 2 S B D Product Developer’s Guide
Iridium Communications Inc.
Proprietary & Confidential Information
Iridium Communications Inc.
6707 Democracy Blvd., Suite 300
Bethesda, MD 20817 USA
www.iridium.com
Toll Free: +1.866.947.4348 [US Only]
International +1.480.752.5155
email: info@iridium.com
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
LEGAL DISCLAIMER AND CONDITIONS OF USE
This document contains information for the Iridium 9602 Short Burst Data Transceiver and accompanying
accessories (“Product”) is provided “as is.” The purpose of providing such information is to enable Value
Added Resellers and Value Added Manufacturers (collectively, “Product Developer(s)”) to understand the
Product and how to integrate it into a wireless data solution. Reasonable effort has been made to make
the information in this document reliable and consistent with specifications, test measurements and other
information. However, Iridium Communications Inc. and its affiliated companies, directors, officers,
employees, agents, trustees or consultants (“Iridium”) assume no responsibility for any typographical,
technical, content or other inaccuracies in this document. Iridium reserves the right in its sole discretion
and without notice to you to change Product specifications and materials and/or revise this document or
withdraw it at any time. The Product Developer assumes the full risk of using the Product specifications
and any other information provided.
IRIDIUM MAKES NO REPRESENTATIONS, GUARANTEES, CONDITIONS OR WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED
REPRESENTATIONS, GUARANTEES, CONDITIONS OR WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, SATISFACTORY QUALITY,
NON-INTERFERENCE, ACCURACY OF INFORMATIONAL CONTENT, OR ARISING FROM A
COURSE OF DEALING, LAW, USAGE, OR TRADE PRACTICE, USE, OR RELATED TO THE
PERFORMANCE OR NONPERFORMANCE OF ANY PRODUCTS, ACCESSORIES, FACILITIES OR
SERVICES OR INFORMATION EXCEPT AS EXPRESSLY STATED IN THIS GUIDE AND/OR THE
PRODUCT AND/OR SATELLITE SERVICE DOCUMENTATION. ANY OTHER STANDARDS OF
PERFORMANCE, GUARANTEES, CONDITIONS AND WARRANTIES ARE HEREBY EXPRESSLY
EXCLUDED AND DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW. THIS
DISCLAIMER AND EXCLUSION SHALL APPLY EVEN IF THE EXPRESS LIMITED WARRANTY
CONTAINED IN THIS GUIDE OR SUCH DOCUMENTATION FAILS OF ITS ESSENTIAL PURPOSE.
IN NO EVENT SHALL IRIDIUM BE LIABLE, WHETHER IN CONTRACT OR TORT OR ANY OTHER
LEGAL THEORY, INCLUDING WITHOUT LIMITATION STRICT LIABILITY, GROSS NEGLIGENCE OR
NEGLIGENCE, FOR ANY DAMAGES IN EXCESS OF THE PURCHASE PRICE OF THE PRODUCT,
INCLUDING ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OF
ANY KIND, OR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF PRIVACY, LOSS
OF USE, LOSS OF TIME OR INCONVENIENCE, LOSS OF INFORMATION OR DATA, SOFTWARE
OR APPLICATIONS OR OTHER FINANCIAL LOSS CAUSED BY THE PRODUCT (INCLUDING
HARDWARE, SOFTWARE AND/OR FIRMWARE) AND/OR THE IRIDIUM SATELLITE SERVICES, OR
ARISING OUT OF OR IN CONNECTION WITH THE ABILITY OR INABILITY TO USE THE PRODUCT
(INCLUDING HARDWARE, SOFTWARE AND/OR FIRMWARE) AND/OR THE IRIDIUM SATELLITE
SERVICES TO THE FULLEST EXTENT THESE DAMAGES MAY BE DISCLAIMED BY LAW AND
WHETHER ADVISED OF THE POSSIBILITIES OF SUCH DAMAGES. IRIDIUM IS NOT LIABLE FOR
ANY CLAIM MADE BY A THIRD PARTY OR MADE BY YOU FOR A THIRD PARTY.
Your use of the information contained in this Guide is restricted to the development activity
authorized under the agreement(s) between you and Iridium, and is otherwise subject to all
applicable terms and conditions of such agreement(s), including without limitation software
license, warranty, conditions of use and confidentiality provisions.
Export Compliance Information
This Product is controlled by the export laws and regulations of the United States of America. The U.S.
Government may restrict the export or re-export of this Product to certain individuals and/or destinations.
For further information, contact the U.S. Department of Commerce, Bureau of Industry and Security or
visit www.bis.doc.gov.
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Revision History
Revision
0.1
0.2
4.0
Date
Sep 11 2009
Oct 20 2009
Mar 1 2010
Comment
First revision adapted from 9601 Product Developers Guide v1.25
Updated following feedback from ISLLC
Update following FP-1 build
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Contents
Revision History ............................................................................................................................. 3
Contents ........................................................................................................................................ 4
List of Abbreviations ...................................................................................................................... 6
Product Overview ................................................................................................................... 6
1.1
Key Features .............................................................................................................. 6
1.2
Transceiver Packaging and Regulatory Certification ................................................ 6
1.3
Software Revision...................................................................................................... 6
Physical Specification............................................................................................................. 6
2.1
Module Dimensions................................................................................................... 6
2.2
Mechanical Dimensions – Motherboard Mounting................................................... 6
2.3
Environmental ........................................................................................................... 6
2.3.4 Environmental Specification ..................................................................................... 6
2.3.5 Environmental Tests Performed ................................................................................ 6
2.4
Physical Interface Connectors ................................................................................... 6
Electrical Interfaces ................................................................................................................ 6
3.1
User Connector .......................................................................................................... 6
3.1.4 User Connector Type................................................................................................. 6
3.1.5 User Connector Pin Allocation.................................................................................. 6
3.2
DC Power Interface ................................................................................................... 6
3.2.4 Power On/Off Control ............................................................................................... 6
3.2.5 Typical Power Usage Profile ..................................................................................... 6
3.3
Serial Data Interface .................................................................................................. 6
3.3.4 9-Wire and 3-Wire Operation.................................................................................... 6
3.3.5 Configuration Settings............................................................................................... 6
3.3.6 Modes of Operation ................................................................................................... 6
3.3.7 Serial port signal levels.............................................................................................. 6
3.4
Hardware Failure Reporting ...................................................................................... 6
3.5
Network Available Output......................................................................................... 6
3.6
DC Supply Indicator Output...................................................................................... 6
RF Interface ............................................................................................................................ 6
4.1
RF Connector Types .................................................................................................. 6
4.2
ANT Connector ......................................................................................................... 6
4.2.4 Antenna Characteristics ............................................................................................. 6
4.3
GPS Connector .......................................................................................................... 6
4.4
R F Interface Specifications ............................................................................... 6
4.5
Radio Characteristics ............................................................................................ 6
4.6
S-meter Performance ................................................................................................. 6
AT Command Set Description................................................................................................ 6
5.1
AT – ATtention Code ................................................................................................ 6
5.2
A/ - Repeat Last Command ....................................................................................... 6
5.3
En – Echo................................................................................................................... 6
5.4
In – Identification ...................................................................................................... 6
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.5
Qn – Quiet Mode ....................................................................................................... 6
5.6
Vn – Verbose Mode................................................................................................... 6
5.7
Zn – Soft Reset .......................................................................................................... 6
5.8
&Dn – DTR Option ................................................................................................... 6
5.9
&Fn – Restore Factory Settings................................................................................. 6
5.10
&Kn – Flow Control.................................................................................................. 6
5.11
&V – View Active and Stored Configuration ........................................................... 6
5.12
&Wn – Store Active Configuration........................................................................... 6
5.13
&Yn – Designate Default Reset Profile .................................................................... 6
5.14
%R – Display Registers ............................................................................................. 6
5.15
*F – Flush to EEPROM............................................................................................. 6
5.16
*Rn – Radio Activity................................................................................................. 6
5.17
+CCLK – Real time clock ......................................................................................... 6
5.18
+CGMI – Manufacturer Identification ...................................................................... 6
5.19
+CGMM – Model Identification ............................................................................... 6
5.20
+CGMR – Revision ................................................................................................... 6
5.21
+CGSN – Serial Number........................................................................................... 6
5.22
+CIER – Indicator Event Reporting .......................................................................... 6
5.23
+CRIS – Ring Indication Status ................................................................................ 6
5.24
+CSQ – Signal Quality .............................................................................................. 6
5.25
+CULK – Unlock ...................................................................................................... 6
5.26
+GMI – Manufacturer Identification......................................................................... 6
5.27
+GMM – Model Identification .................................................................................. 6
5.28
+GMR – Revision...................................................................................................... 6
5.29
+GSN – Serial Number.............................................................................................. 6
5.30
+IPR – Fixed DTE Rate............................................................................................. 6
5.31
+SBDWB – Short Burst Data: Write Binary Data to the ISU................................... 6
5.32
+SBDRB – Short Burst Data: Read Binary Data from the Module .......................... 6
5.33
+SBDWT – Short Burst Data: Write a Text Message to the Module ....................... 6
5.34
+SBDRT – Short Burst Data: Read a Text Message from the Module..................... 6
5.35
+SBDI – Short Burst Data: Initiate an SBD Session................................................. 6
5.36
+SBDDET – Short Burst Data: Detach ..................................................................... 6
5.37
+SBDDSC – Short Burst Data: Delivery Short Code ............................................... 6
5.38
+SBDIX – Short Burst Data: Initiate an SBD Session Extended.............................. 6
5.39
+SBDMTA – Short Burst Data: Mobile-Terminated Alert....................................... 6
5.40
+SBDREG – Short Burst Data: Network Registration.............................................. 6
5.41
+SBDAREG – Short Burst Data: Automatic Registration........................................ 6
5.42
+SBDD – Short Burst Data: Clear SBD Message Buffer(s) ..................................... 6
5.43
+SBDC – Short Burst Data: Clear SBD MOMSN .................................................... 6
5.44
+SBDS – Short Burst Data: Status ............................................................................ 6
5.45
+SBDSX - Short Burst Data: Status Extended.......................................................... 6
5.46
+SBDTC – Short Burst Data: Transfer MO Buffer to MT Buffer ............................ 6
5.47
+SBDGW – Short Burst Data: Gateway ................................................................... 6
5.48
-MSSTM – Request System Time............................................................................. 6
S-Register Definitions............................................................................................................. 6
6.1
S-Register Commands ............................................................................................... 6
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
6.1.4 Sr – Direct S-Register Reference............................................................................... 6
6.1.5 Sr? – Direct S-Register Read..................................................................................... 6
6.1.6 Sr=n – Direct S-Register Write ................................................................................. 6
6.1.7 ? – Referenced S-Register Read ................................................................................ 6
6.1.8 =n – Referenced S-Register Write............................................................................. 6
6.2
S-Registers................................................................................................................. 6
Summary of Result Codes ...................................................................................................... 6
Informative Examples............................................................................................................. 6
8.1
Setting the Default Configuration.............................................................................. 6
8.2
Power-on to Sending a Message................................................................................ 6
8.3
Automatic Notification Registration ......................................................................... 6
8.4
Automatic Notification Message Reception.............................................................. 6
8.5
Automatic Notification Automatic Registration........................................................ 6
8.6
Sending a Message with Minimal Radio Activity..................................................... 6
8.7
Powering Down ......................................................................................................... 6
Supported AT Commands....................................................................................................... 6
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
List of Abbreviations
Abbreviation
Description
CE
ESS
ETC
FA
FCC
GND
GSS
IC
IMEI
LBT
Conformité Européene
(V.24 signal) Clear To Send. This signal is used to control the flow of data to
the 9602
Direct Current
(V.24 signal) Data Carrier Detect
Data Communications Equipment. In this Product, DCE refers to the 9602
(V.24 signal) Data Set Ready. This signal, from the 9602, indicates readiness
to accept communication over the data port
Data Terminal Equipment. In this Product, DTE refers to the FA
(V.24 signal) Data Terminal Ready. This signal, from the FA, requests the
9602 to accept communication over the data port
ETC SBD Subsystem (synonymous with GSS)
Earth Terminal Controller
Field Application; the application controlling the 9602
Federal Communications Commission
Ground
Gateway SBD Subsystem (synonymous with ESS)
Industry Canada
International Mobile Equipment Identity
L-Band Transceiver
MO
Mobile Originated
MOMSN
Mobile Originated Message Sequence Number
MT
Mobile Terminated
MTMSN
Mobile Terminated Message Sequence Number
RHCP
SBD
Right Hand Circular Polarization
(V.24 signal) Ring Indicate. This signal, from the 9602, indicates that an MT
message is present at the GSS
(V.24 signal) Request To Send. This signal is used to control the flow of data
from the 9602.
Short Burst Data
SMS
Short Message Service
TBA
To Be Advised
UART
Universal Asynchronous Receiver Transmitter
VAM
Value Added Manufacturer
VAR
Value Added Reseller
VSWR
Voltage Standing Wave Ratio
CTS
DC
DCD
DCE
DSR
DTE
DTR
RI
RTS
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
1 Product Overview
The Iridium 9602 Short Burst Data Only Transceiver (9602) is designed to be integrated into a wireless
data application with other host system hardware and software to produce a full solution designed for a
specific application or vertical market. Examples of these solutions include tracking a maritime vessel or
automatic vehicle location.
The 9602 only supports Iridium’s Short Burst Data (SBD) capability. It does not support voice, circuit
switched data, or short message service (SMS).
The 9602 is designed to meet the regulatory requirements for approval for FCC, Canada, and CE
assuming an antenna with a gain of ~3 dBi and adequate shielding. This allows the 9602 to be integrated
into a variety of wireless data applications or retrofitted into existing SBD only applications that utilize SBD
with the current Iridium 9601, 9522A, 9522B or 9522 L-Band transceiver-based products. (Note that
additional development work will be required). Such finished products, when integrated together, require
regulatory and safety testing to be conducted by the integrator.
The 9602 is a single board transceiver provided as a ‘black box’ transceiver module with all device
interfaces provided by a single multi-pin interface connector in addition to the antenna connector. The
Product only provides the core transceiver. All other end user Field Application functions such as GPS,
microprocessor based logic control, digital and analog inputs, digital and analog outputs power supply and
antenna must be provided by the solution developer. The device interface across the user connector
consists of a serial-data interface, DC power input, network available output and a power on/off control line.
The 9602 does not incorporate nor require a Subscriber Identity Module (also know as a SIM Card) to be
inserted into the Transceiver. The 9602 is intended to be used as a transceiver module fitted within
another host system. The 9602 module is designed to comply with the standards for Radio Emissions
Compliance, Electromagnetic Compatibility, and AC Safety in the United States, European Union and
Canada, for host systems that provide safe connections to power supply and external antenna or cable
distribution system.
The 9602 is described within this document as “9602,” “9602 SBD Transceiver,” “Transceiver,”and “ISU.”
All of these terms refer to the same product.
1.1 Key Features
•
•
•
•
•
•
•
•
•
•
Single board transceiver
Small form factor
Aluminum alloy casework (LM2 / LM24) with Alodine 2600 passivation coating
No SIM card
Designed to be incorporated into an OEM solution
Maximum mobile originated message size 340 bytes
Maximum mobile terminated message size 270 bytes
Automatic Notification to the Transceiver that a mobile terminated message is queued at the
Gateway
Global operating capability
RoHS compliant
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
1.2 Transceiver Packaging and Regulatory Certification
The 9602 SBD Transceiver is a regulatory approved daughter module transceiver that can be fitted within
an enclosed host system. With appropriate external connections, the host system can be designed to
meet full transceiver regulatory tests and sold as a Regulatory Certified product that meets CE, FCC and
IC requirements.
The 9602 is tested to the regulatory and technical certifications shown in Table 1 (See Note below).
Table 1: Regulatory and Technical Certifications.
Regulatory
Approvals
CE
Radio Tests
ETSI EN 301 441 V1.1.1
(2000-05)
Electrical /
Mechanical /
Operational
Safety Tests
EMC Tests
ETSI EN301 489-1 V1.8.1(2008-04)
EN60950-1:2006
Part 1
ETSI EN 301 489-20 V1.2.1(2002-11)
FCC
FCC CFR47 parts 2, 15,
and 25
EN61000-4-2 : 1995/A2 : 2001 Part 4.2
EN61000-4-3 : 2002 Part 4.3
EN61000-4-4 : 2004
EN61000-4-6 : 1996/A1 : 2001 Part 4.6
EN55022:2006
Industry
Canada
Industry Canada
RSS170 Issue 1, Rev 1,
November 6, 1999
Note: The initial 9602 FP1 & FP2 prototype units are different from the commercially produced 9602 SBD
Transceivers from a regulatory and certification perspective. Those initial units cannot and should not be
used for any commercial purpose or for any regulatory certification or compliance purposes. Only the
commercial 9602 units conform to the regulatory approved design and the regulatory and technical
certifications listed in Table 1.
Iridium Communications Inc.
Proprietary & Confidential Information
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
1.3 Software Revision
Product Developers should read this document in conjunction with the “Software Release Notes” relevant
to the revision of the software that is loaded into their 9602 SBD Transceiver.
Product Developers should take into account in their software design that it is possible that a transceiver
may have an earlier software release and may therefore have different capabilities to those listed in this
document. Product Developers are advised to ensure that production procedures for finished goods
confirm that the software used in the Product Developer application is designed for the Software Release
loaded in the 9602 SBD Transceiver. This can be read out of the module using the AT command
interface. A software upgrade utility is provided with each SW release. The utility runs on a Windows
compatible OS and will automatically upgrade the modem with the latest version.
Iridium Communications Inc.
Proprietary & Confidential Information
10
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
2 Physical Specification
For illustrative purposes a picture of the 9602 SBD Transceiver Module is shown in Figure 1.
Figure 1 The 9602 SBD Transceiver Module
2.1 Module Dimensions
The overall dimensions of the 9602 module and its weight are summarized in Table 2 and represented
graphically in Figure 2
Table 2: 9602 Mechanical Dimensions
Parameter
Length
Width
Depth
Weight (approximate)
Value
41.0 mm
45.0 mm
13.0 mm
30g
Additionally host system Product Developers should plan space for connection to the host system
motherboard, including robust and electrically grounded connections to the antenna/cable distribution
system.
Iridium Communications Inc.
Proprietary & Confidential Information
11
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Figure 2 General Assembly and Dimensions of the 9602 SBD Transceiver Module
(Not to scale, dimensions in millimeters)
This drawing shows some of the key dimensions within the 9602 module, and specified
the mechanical position of its connectors with respect to its mounting holes.
Iridium Communications Inc.
Proprietary & Confidential Information
12
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
2.2 Mechanical Dimensions – Motherboard Mounting
The 9602 SBD Transceiver must be fitted within an enclosed host system. With appropriate external
connections, the host system motherboard and host system enclosure can be designed to meet full
transceiver regulatory tests.
The 9602 SBD Transceiver is provided with two mounting holes, one at each diagonal corner. The
module should be assembled onto the motherboard of the host system, by pushing the module onto
matching connectors on the motherboard and then securing the diagonal mounting holes to the
motherboard using mechanical fasteners.
The figures and tables below provide mechanical information design information to connect a 9602
module to a host system motherboard.
Figure 3 General assembly of the 9602 module onto motherboard of the host system.
Iridium Communications Inc.
Proprietary & Confidential Information
13
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Figure 4 Example host system motherboard footprint showing mounting position of 9602
(Not to scale. Dimensions in millimeters)
Notes for Figure 4
1. This example of a host system motherboard footprint is shown for illustrative purposes only. The host
system may require a different PCB layout or mechanical arrangement.
2. The 9602 module is designed to be incorporated within a host system. As such, the antenna or cable
distribution system that feeds the host system should be terminated in a robust RF connector that is
suitable for the end-application.
3. Safety isolation requirements for external antennas or cable distribution systems should also be taken
into consideration when designing the motherboard. A suitably safe design for the RF connections
should be incorporated into the host system motherboard, ideally using a chassis-bonded ground
connection to the antenna cable shield.
4. The surface below the modem should be a conductive ground plane such that the modem bonds to
the motherboard ground system thus reducing the possibility of radiated emissions. This also requires
that the mounting screws get properly tightened to 7 pound-inches of torque.
5. The modem is to be installed in a “service access only” area not accessible by untrained personnel.
Warning- Although the modem dissipates very little power, its use in ambient temperatures
in excess of 60 deg C will make the caseworks considerably hot.
Iridium Communications Inc.
Proprietary & Confidential Information
14
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
2.3 Environmental
2.3.4 Environmental Specification
The environmental specifications of the 9602 are summarized in Table 5 below.
Table 5: Environmental Specifications
Parameter
Operating Temperature Range1
Operating Humidity Range
Storage Temperature Range
Storage Humidity Range
Value
-40ºC to + 85ºC
≤ 75% RH
-40ºC to + 85ºC
≤ 93% RH
2.3.5 Environmental Tests Performed
The 9602 has been tested to the specifications listed in Table 6.
Table 6: Environmental Tests
Test Name
Test Reference
Thermal Shock
EN60068-2-14:2000
Humidity
IEC60068-2-78:2002
Vibration
EN 60068-2-36:1996
Vibration
J1455 Society of Automotive Engineers
Shock
EN60068-2-27:1993
(NF c20-727)
Shock
J1455 Society of Automotive Engineers
Test Description
Change of Temperature,
-25°C to +70°C,
5 cycles of 1 hour each
Damp heat steady state
40OC 93% RH for 4 days
0.96 m2/s3 from 5Hz to 20Hz
21Hz to 500Hz dropping -3dB per octave
10-40Hz at 0.02g2/Hz
40-500Hz dropping 6dB per octave
Drop 1m onto concrete in 3 perpendicular
orientations (3 drops)
Also 10G shock over a period of 12ms
2.4 Physical Interface Connectors
The 9602 SBD Transceiver incorporates three connectors:
•
•
•
A multiway user connector
An RF antenna connector
A GPS RF pass-through connector
The physical characteristics of the connectors and their electrical interfaces are described in more detail
in Sections 3.1.4 and 4.1 respectively.
Based on a duty-cycled usage model with 9602 sending one SBD message per hour and is otherwise turned off
during the hour
Iridium Communications Inc.
Proprietary & Confidential Information
15
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3 Electrical Interfaces
The following subsections contain information for the electrical interfaces of the 9602 SBD Transceiver for
the non-RF connections. RF interfaces are covered in section 4
3.1 User Connector
The User connector provides the following connections to the 9602 module:
•
•
•
•
•
DC power supply input
Power on/off control
Serial data interface
Network available output
Supply power indicator output
3.1.4 User Connector Type
The connector on the 9602 is a Samtec low-profile header connector, part number FTSH-110-01-L-DV.
This connector provides the ability for a stackable board to board configuration, allowing connection to the
host system motherboard.
Data sheets on these connectors can be found at: http://www.samtec.com
A suitable motherboard female socket that matches this connector is the SAMTEC header part number
CLP-110-02-L-D.
Iridium Communications Inc.
Proprietary & Confidential Information
16
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3.1.5 User Connector Pin Allocation
The user connector is a 2-row 20-way header. Individual pin assignments are shown in Table 7 and the
limits for the digital signals are listed in Table 8. Multiple supply grounds are provided and all supply and
supply grounds are required to be connected to the power supply in order to limit the current on any one
pin. Multiple signal grounds are provided to reduce cross-talk.
Table 7: User Connector Pin Allocation
Pin
No.
Signal Name
EXT_PWR
EXT_PWR
EXT_GND
EXT_GND
Signal
direction
(WRT 9602)
Input
Input
Input
Input
ON/OFF
Input
On/Off control input
10
11
12
13
14
15
16
17
18
DF_S_TX
DF_S_RX
SIG_GND
DF_ DCD
DF_ DSR
DF_ CTS
DF_RI
DF_ RTS
DF_ DTR
SIG_GND
Reserved
Reserved
SIG_GND
Input
Output
Input
Output
Output
Output
Output
Input
Input
Input
Data port, serial data input
Data port, serial data output
Signal ground
Data port, Data Carrier Detect
Data port, Data Set Ready
Data port, Clear-to-Send
Data port, Ring Indicator
Data port, Request-to-Send
Data port, Data Terminal Ready
Signal ground
Input
Signal ground
19
NETWORK
AVAILABLE
Output
Signals when the 9602 can see an
available satellite network
20
SUPPLY_OUT
Output
Supply power indicator output
Signal function
Signal level
Supply
Supply
Supply return
Supply return
+5 V +/- 0.5 V
+5 V +/- 0.5 V
0V
0V
Analog
On: >=2.0V
Off: <=0.5V
3.3V Digital
3.3V Digital
0V
3.3V Digital
3.3V Digital
3.3V Digital
3.3V Digital
3.3V Digital
3.3V Digital
0V
0V
3.3V Digital
Available = high
Not available= low
+3.3 V
5mA maximum
Table 8: Limits for 3.3V Digital Signals
Parameter
Symbol
Min
Input High Voltage
Input Low Voltage
Output High Voltage
Output Low Voltage
Low Level Output Current
High Level Output Current
VIH
VIL
VOH
VOL
IOL
IOH
2.0
-0.3
2.4
Iridium Communications Inc.
Proprietary & Confidential Information
17
Typ
Max
Unit
5.5
0.8
mA
mA
0.4
4.4
5.5
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Figure 5 provides a reference for the pin designation. Note that this designation is when looking into the
User connector towards the 9602 module. It is not to scale and not representative of the connector
mechanical layout.
Figure 5 User Connector Pin Number Designation (from below module)
Notes:
1.
2.
3.
4.
View looking into connector towards 9602 module
Numbers indicate pin designations
Not to scale, for illustrative purposes only
On the 9602 PCB, pin 1 of the User connector is indicated on the board silkscreen
Iridium Communications Inc.
Proprietary & Confidential Information
18
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3.2 DC Power Interface
The DC power interface is comprised of the DC power inputs and a control signals as summarized in
Table 7. The +5V Inputs and 0V supply returns are used to supply DC power to the 9602 and ensure that
enough current can be drawn across the connector without the 9602 malfunctioning during transmit due
to lack of current supply. Note that all power and ground pins should be connected externally.
The DC power supply requirements for the 9602 are summarized in Table 9 below. Note that these
requirements apply to DC power measured at the 9602 User connector input and not at the output of the
power supply. Long power supply cables can cause a voltage drop sufficient to cause the voltage to be
out of specification at the physical power supply input to the 9602.
Table 9: DC Power Input Specifications
Parameter
Supply Input Voltage Range
Supply Input Voltage Ripple
Value
5.0V DC +/-0.5V
< 40 mV pp
Typical Power Consumption at +5.0 VDC
Value
Idle Current (average*)
Idle Current (peak)
Transmit Current (peak)
Transmit Current (average*)
Receive Current (peak)
Receive Current (average*)
SBD message transfer - average current*
SBD message transfer - average power*
45mA
195mA
1.5 A
190mA
195mA
45mA
190 mA
<= 1.0 W
* Note: The average power consumption will vary depending on the view of the satellite constellation from
the antenna.
The external power supply needs to guarantee the following:
•
•
•
•
The supply voltage droop over for a 8.3ms burst of 1.5A current should not be more than 0.2 Volts.
The power supply should limit the in-rush current to 4 Amps maximum
The power source shall provide for over current protection in case of device malfunction.
The supply noise should be less than the limits in the following profile:
100 mVpp
from 0 to 50 kHz
5 mVpp
at 1 MHz measured in 50 kHz bandwidth
10 mVpp
at 1 MHz measured in 1MHz bandwidth
5 mVpp
above 5 MHz measured in 1 MHz bandwidth.
3.2.4 Power On/Off Control
An external on/off input is provided on a pin of the User connector. The 9602 starts up when power is
applied and the power on/off input is high. As long as the input voltage is applied, logic high on this line
turns the transceiver on and a logic low turns it off. If this line is not required then it must be connected
directly to the +5 V supply.
Note that this on/off control is similar to the 9601 product but is not the same as the 9522, 9522A or
Iridium Communications Inc.
Proprietary & Confidential Information
19
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
9522B products.
Prior to turning off the modem a “flush memory” (AT*F) command should be issued to ensure all memory
write activity is completed. When a transceiver has been turned off, Product Developers should not
reapply power on a unit until more than 2 seconds has elapsed after power has reached 0V. Additionally,
if a unit does not respond to AT commands, power off the module, wait for 2 seconds and then power it
back on.
3.2.5 Typical Power Usage Profile
This section is designed to give the Product Developer some insight to the electrical power profile that the
9602 uses. It does not describe every situation and permutation possible. It should be used as a starting
point for the Product Developer to continue its own development design. The actual usage profile can
vary for a number of reasons:
1) View of the sky – if in poor visibility of the sky where a clear line of sight is not available between
the transceiver and the satellite.
2) The higher the antenna VSWR the higher the current consumed
3) How often the 9602 module is activated/deactivated by the Host Controller system
4) Manufacturing variation from transceiver to transceiver.
The host system designer should ensure their design covers for worst case power consumption
scenarios. Figure 6 provides a graphical representation of the typical supply current profile of a 9602
SBD Transceiver sending and receiving SBD messages.
1.6
1.5
1.4
1.3
1.2
Transmitter data burst
(Typically 1.5A )
Supply Current (A)
1.1
1.0
0.9
0.8
0.7
0.6
Receiver data burst
(Typically 195mA)
0.5
0.4
Background
(Typically 40mA)
0.3
0.2
0.1
-10
10
20
30
40
50
60
70
Time (mS)
Figure 6 Typical Supply Current Profile
Iridium Communications Inc.
Proprietary & Confidential Information
20
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3.3 Serial Data Interface
The Serial data interface is used to both command the 9602 and transfer user data to and from the
Transceiver. The 9602 presents a 9-wire data port to the FA (Field Application), where the interface is at
3.3V digital signal levels. With respect to this interface, the 9602 behaves as a DCE (Data
Communication Equipment), and the FA behaves as a DTE (Data Terminal Equipment).
The terms “FA” and “DTE” are used interchangeably throughout this document; similarly for the terms
“9602” and “DCE”. Autobaud is not supported in 9602 SBD Transceiver. The baud rate can be set via the
AT+IPR command. The default rate is 19200 bps.
3.3.4 9-Wire and 3-Wire Operation
By default, the serial interface operates as a 9-wire connection. Table 10 describes each of the signals,
where “input” means an input to the 9602, and “output” means an output from the 9602 SBD Transceiver.
Table 10 – Serial Interface Signals
Signal
RX
TX
GND
RTS
CTS
DTR
DSR
RI
DCD
Description
Active high data output [The DTE receives the data from the 9602]
Active high data input [Data is transmitted from the DTE to the 9602]
0V
Active low flow control input
Active low flow control output
RTS and CTS are used together to implement hardware flow control when enabled with
AT&K3
Active low handshaking input
AT&Dn controls how the 9602 uses DTR:
• If set to AT&D0, DTR is always ignored.
• Otherwise DTR set to OFF places the data port into UART test mode after 10
seconds, or immediately on boot-up. A subsequent transition of DTR to ON returns
the data port to DCE mode and resets it to its power-on state.
• The UART test mode is provided for factory testing of the data port UART. An FA
should never activate test mode; if it does, the 9602 will stop responding to AT
commands until the data port is returned to DCE mode.
Active low handshaking output
The 9602 drives DSR ON when the data port is in DCE mode, and OFF when the data
port is in test mode.
The DTE may use this signal as an indication that the 9602 is powered up and ready to
receive AT commands.
Active low ring indicator output
The 9602 drives RI ON when it receives a Automatic Notification from the network that a
Mobile Terminated SBD Message is queued at the Gateway, and drives RI OFF after 5
seconds or when the DTE initiates an SBD session, whichever occurs first.
Active low handshaking output
DCD is driven OFF at all times.
Note that the Ring Indicator (RI) pin is used by the 9602 SBD Transceiver to indicate that a Mobile
Terminated SBD (MT-SBD) message is queued at the Gateway. The Field Application can monitor this
pin and use appropriate AT Commands to command the Transceiver to retrieve the MT-SBD message.
Iridium Communications Inc.
Proprietary & Confidential Information
21
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
The serial interface may be operated with a 3-wire connection, where only transmit, receive and ground
signals are used. However the 9 wire interface offers better control and is the recommended
implementation. Iridium is only able to provide limited 3-wire interface support. When operating with a 3wire connection, the following rules apply:
•
•
•
AT&Dn must be set to AT&D0 to ignore the DTR input
AT&Kn must be set to AT&K0 to disable RTS/CTS flow control
The other output signals may be connected, and operate as follows:
• CTS driven ON (low)
• DSR operates as normal
• RI operates as normal
• DCD driven ON (low)
Notes:
1. RTS/CTS flow control, when enabled, is only used when the data port is in SBD data mode. In
AT command mode, RTS is ignored and CTS is driven ON (low).
2. If the DC input to the modem is to be disconnected, the developer will need to “tri-state” the serial
interface to prevent a possible latch-up condition.
3.3.5 Configuration Settings
The 9602 allows the DTE to configure the data port communication parameters. The three configuration
types are active, factory default, and stored. The active configuration is the set of parameters currently in
use. They can be changed by the DTE individually via specific AT commands. The factory default
configuration is stored in permanent memory. This configuration can be recalled at any time through use
of the AT&Fn command.
Two groups of settings, or “profiles”, can be stored as user-defined configurations. The DTE first creates
desired active configurations and then writes them to memory using the AT&Wn command. These
profiles can be designated to be loaded as the active configuration upon 9602 power-up through use of
the AT&Yn command. The 9602 can be reset without loss of power to these profiles through use of the
ATZn command.
The configuration settings are stored in “S-register” locations and are detailed further in Section 6.
Iridium Communications Inc.
Proprietary & Confidential Information
22
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3.3.6 Modes of Operation
The serial interface is always in one of three modes: command mode, SBD data mode or SBD session
mode. When the data port is in command mode, AT commands can be entered to control the 9602. In
command mode, flow control has no effect, with the RTS input ignored and the CTS output driven ON
(low). When in SBD data mode, the 9602 is transferring binary or text SBD message data to or from the
DTE.
In SBD data mode:
• All characters from the DTE not forming part of the message data are ignored (i.e. no AT
commands may be entered)
• No unsolicited result codes are issued.
• RTS/CTS flow control, if enabled, is active. When RTS is OFF (high), the 9602 suspends transfer
of data to the DTE; when CTS is OFF (high), the 9602 expects the DTE to suspend transfer of data to
the 9602.
When in SBD session mode, the 9602 is attempting to conduct an SBD session with the network. In SBD
session mode:
• The DTE must wait for the +SBDI [X][A]session result code.
• All characters from the DTE are ignored.
• Unsolicited result codes are issued where those codes have been enabled.
Transitions between the modes of operation are performed automatically by the 9602 in response to the
SBD AT Commands; the DTE has no other control over the mode.
3.3.7 Serial port signal levels
3.3.7.1 Data Port Inputs
The inputs on the 9602 serial port (RTS, DTR and TXD) will operate correctly at 3.3V digital signal levels.
RS-232 interface chips can be fitted to the host system motherboard if connection to an external RS232
link is required. Note that these may invert the digital logic level, so another inversion may be required.
3.3.7.2 Data Port Outputs
The five outputs from the 9602 serial port (DCD, DSR, CTS, RI and RXD) are all at 3.3V digital levels.
3.4 Hardware Failure Reporting
If the 9602 detects a hardware problem during initialisation, the 9602 may be unable to function correctly.
The 9602 notifies the DTE of this situation by issuing an unsolicited result code at the end of initialisation:
HARDWARE FAILURE: ,
where identifies the software subsystem that detected the error, and is the
subsystem-specific error code.
Any AT commands that cannot be handled in the failure condition will terminate with result code 4
(“ERROR”).
Iridium Communications Inc.
Proprietary & Confidential Information
23
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
3.5 Network Available Output
This is a digital output that can be used by an application to know when the Transceiver has visibility to
the satellite network. This is useful in applications where the Transceiver may move around terrain that
reduces the amount of time that clear line of sight to the satellite constellation is available. The Product
Developer can use this output to preserve battery life by reducing the number of attempted transmissions
by including this logic output in the application decision logic.
Network Available means only that the 9602 can successfully receive the Ring Channel, or, put more
simply, it can see an Iridium satellite. Network Available is not a guarantee that a message can be
successfully sent. The Network Available state is evaluated every time the Ring Channel is received or
missed. If the Ring Channel is visible, then that is typically every 4 seconds. If the Ring Channel is not
currently visible, then the update period can be as long as 2 minutes, depending on how long the lack of
satellite visibility existed. This is because the 9602 attempts to conserve power by increasing the ring
search interval while the satellites are not visible. Every time a ring search fails, the time to wait is
increased and eventually limits at 120 seconds.
If Network Available is currently off, the Field Application may still attempt an SBDI[X] session. This will
force the 9602 Transceiver to look for the Ring Channel immediately, and on finding it, to attempt to send
the message. In this case Network Available will not come on immediately. The Network Available does
not turn on while in a +SBDI session. It will however turn on 4 seconds later assuming that the Ring
Channel is present. After the SBD session completes, the 9602 performs a new Ring Channel search
sequence, at the end of which Network Available gets turned on. That can take between 4 and 12
seconds.
The wait time between search windows is reset to 4 seconds every time a search succeeds. Otherwise it
continues to increase. So if the +SBDI attempt fails to find the ring channel, the search window does not
reset to 4 seconds.
Note that the behavior of +CIEV:1 is identical in to that of the Network Available output.
3.6 DC Supply Indicator Output
A DC supply indicator signal is provided by the 9602 which could be used directly for driving an LED to
provide a visible indication that the Transceiver supply is on. Alternatively the output signal could be used
in application logic to determine if the internal Transceiver power supply is on.
Iridium Communications Inc.
Proprietary & Confidential Information
24
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
4 RF Interface
This section describes the physical characteristics of the RF connectors and specifications of the RF
Interface.
4.1 RF Connector Types
Both the antenna and GPS connectors on the 9602 use a male MMCX type connector from SAMTEC,
part number MMCX-J-P-H-ST-TH1.
Note - this 9602 module has a different antenna connector to other Iridium transceivers.
Both RF connectors on the 9602 module are intended for an inter-board connection to the host system
motherboard and should not be directly connected to an external antenna cable or cable distribution
system.
Additional information can be found at: http://www.samtec.com
4.2 ANT Connector
The main RF connector for the 9602 is the antenna connector, labeled “ANT” in the board silkscreen.
This provides the RF connection between the 9602 module and the host system motherboard.
Note that for safety reasons, both RF connectors on the 9602 module are intended for an inter-board
connection to the host system motherboard and should not be directly connected to an external antenna
cable or cable distribution system.
4.2.4 Antenna Characteristics
The 9602 should be connected to an Iridium-band antenna with the following antenna connector
characteristics as described in Table 11.
Table 11: Antenna Characteristics
Parameter
Impedance
Gain
Polarization
VSWR (maximum operational)
Value
50 Ohms nominal
3dBi
RHCP
1.5 : 1
Notes:
• Existing qualified Iridium antennas may be used. (i.e. antennas designed for the 9601, 9522, 9522A
and 9522B)
• Existing antennas will require different RF connector types to those for the 9601, 9522, 9522A and
9522B
Iridium Communications Inc.
Proprietary & Confidential Information
25
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
4.3 GPS Connector
The second RF connector, labeled “GPS” in the board silkscreen, is a pass-through connection from the
antenna path and is provided for GPS receivers that wish to share the main antenna. An overview of this
circuit is provided in Figure 7. The following operational points should be noted when using GPS
receivers connected to this point.
The GPS pass-through path is activated by detecting the presence of a DC voltage on the centrepin of the GPS connector. The 9602 uses the voltage from the GPS centre pin to switch on the
RX path, requires minimal current (<100uA). The GPS path activated when this centre-pin
voltage is higher than 1.2V.
There is a path loss of approximately 3dB in the receive direction from ANT to GPS.
N.B. The GPS receive path is temporarily switched off during transmissions from the 9602.
As long as the 5V supply to the 9602 is connected and the DC voltage on the GPS connector is
present, the GPS pass-through path is made available. The GPS path is available even when the
9602 module has been turned off using its ON/OFF control signal.
If the GPS port is not used it may be left un-terminated with no adverse affect.
The GPS receiver must present 50 ohm impedance across the Iridium band or SBD performance
could be degraded.
The output return loss is typically -8 dB.
Equivalent circuit for GPS connection when GPS path is active and 9602 is not transmitting
Figure 7
Iridium Communications Inc.
Proprietary & Confidential Information
26
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
4.4 R F Interface Specifications
The RF interface requirements for the 9602 are summarized in Table 12 below.
Table 12: General RF Parameters
Parameter
Value
Frequency Range
1616 MHz to 1626.5 MHz
Duplexing Method
TDD (Time Domain Duplex)
Input/Output Impedance
50Ω
Multiplexing Method
TDMA/FDMA
4.5 Radio Characteristics
Table 13 contains radio characteristics of the 9602 SBD Transceiver.
Table 13: Radio Characteristics
Parameter
Average Power during a transmit slot (max)
Receiver sensitivity (Typical level at module connector)
Max Cable loss permitted (Note 1)
Link Margin – Downlink (Note 2)
Link Margin – Uplink (Note 2)
Value
1.6 W
-117dBm
2dB
13dB
7dB
Note 1: Cable losses should be minimized. Note that the total implementation loss for an antenna,
connectors, cable, lightening arrestor and any other RF component between the transceiver and
the antenna should not exceed 3dB. Implementation loss higher than this will affect the Iridium
link performance and quality of service. Solutions with a loss higher than 3dB will not meet the
requirements of Iridium Solution Certification.
Note 2: Link Margins are given assuming a free-space propagation model.
4.6 S-meter Performance
The “bars” reported over the AT command interface indicate the signal strength of the ring channel. Care
should be taken when using the S-meter readings for comparisons between devices. Of particular note
are the following:
1. There is a 0.5 dB tolerance on calibrating the S-meter.
2. Each bar represents a 2 dB increment
3. Multiple ring channels can be present at the same time so units can lock to different signals.
4. The Test Interface Card (TIC board) implementation adds about 0.6 dB loss in the antenna path.
5. If the reading is near the decision threshold it would be easy to see a 1 bar difference
Iridium Communications Inc.
Proprietary & Confidential Information
27
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5 AT Command Set Description
This document specifies the AT Commands supported by the 9602 Transceiver. Informative examples
are presented in Section 8. The 9602 is compatible with all previous 9601 with the exception of +CCLK.
The +CCLK command is still supported but the value returned is now the Iridium system time while the
9601 returned its internal “real time clock” time. A new AT command has been added for the 9602,
+SBDGW and it returns the default gateway on which the modem is programmed to operate.
The 9602 is configured and operated through the use of AT commands. Only AT Commands that are
relevant to the 9602 are included. AT Commands related to functionality of the 9522 and 9522A LBTs are
not included. Note that Commands may be modified, removed or added and that you should not rely on
this document as a definitive statement of the functionality of the commercial 9602 Transceiver. This
document will be periodically updated to reflect the addition, deletion or modification of AT Commands.
Product Developers should also consult the software release notes for the version of software that is
physically loaded on the 9602 used in applications under development. Such release notes are made
available to authorized Iridium VARs and VAMs on the Iridium Developer Extranet. It is the responsibility
of Product Developers to check compatibility of applications software with the AT Commands on all 9602s
used for both development and commercial deployments.
Product Developers should also consult the “Iridium Short Burst Data Service Developers Guide” in
addition to the Commands stated herein. That guide provides significant additional information that will
aide in Product Developers understanding of the Iridium system.
5.1 AT – ATtention Code
This is the prefix for all commands except A/. When entered on its own, the 9602 will respond OK.
5.2 A/ - Repeat Last Command
Repeat the last command issued to the 9602 unless the power was interrupted or the unit is reset. A/ is
not followed by .
5.3 En – Echo
Echo command characters.
Characters are not echoed to the DTE.
Characters are echoed to the DTE (default).
Iridium Communications Inc.
Proprietary & Confidential Information
28
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.4 In – Identification
Requests the 9602 to display information about itself.
“2400” (for compatibility only)
“0000” (for compatibility only)
“OK” (for compatibility only)
“XXXXXXXX” (Software revision level)
“IRIDIUM 9600 Family” (Product description)
“8816” (for compatibility only)
“XXX” (Factory identity)
“XXXXXXXX” (Hardware specification)
5.5 Qn – Quiet Mode
Control 9602 responses.
9602 responses are sent to the DTE (default).
9602 responses are NOT sent to the DTE.
5.6 Vn – Verbose Mode
Set the response format of the 9602, which may be either numeric or textual.
Numeric responses.
Textual responses (default).
5.7 Zn – Soft Reset
Reset the 9602’s data port to a user-stored configuration that has been previously stored using &Wn.
Restores user configuration 0.
Restores user configuration 1.
5.8 &Dn – DTR Option
Set the 9602 reaction to the DTR signal.
DTR is ignored. A DTR signal input is not needed when set to &D0.
1-3
DTR must be ON. If DTR transitions from ON to OFF, the data port will be locked after
approximately 10 seconds to enter the UART test mode. The data port will resume when
DTR is restored to ON.
There is no distinction between settings 1-3. (Default is 2)
5.9 &Fn – Restore Factory Settings
Recall factory default configuration without resetting the data port.
Iridium Communications Inc.
Proprietary & Confidential Information
29
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Recall factory default 0.
5.10 &Kn – Flow Control
Select the flow control method between the 9602 and DTE. Flow control is only applied to the transfer of
SBD message data; it does not apply to AT commands and their responses.
Disables flow control.
Enables RTS/CTS flow control (default).
5.11 &V – View Active and Stored Configuration
View the current active configuration and stored profiles.
5.12 &Wn – Store Active Configuration
Store the active profile in non-volatile memory. This is used to store user configurations for later use.
Store current (active) configuration as profile 0.
Store current (active) configuration as profile 1.
5.13 &Yn – Designate Default Reset Profile
Select profile for use after power-up.
Select profile 0 (default).
Select profile 1.
5.14 %R – Display Registers
Display all the S-registers in the system.
5.15 *F – Flush to EEPROM
Flush all pending writes to EEPROM, shut down the radio, and prepare the 9602 to be powered down.
The command returns OK upon completion, at which point it is safe to remove the power without losing
non-volatile data.
Note: This command stops the 9602 from responding to any more commands, but does not actually
power it down. The only way to power down the 9602 is for the FA to remove the power or to de-assert
the on/off control line.
Note: After an SBD session, the new SBD MOMSN is always flushed to EEPROM before the +SBDI
result is issued.
Iridium Communications Inc.
Proprietary & Confidential Information
30
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.16 *Rn – Radio Activity
Control radio activity.
Disable radio activity.
Enable radio activity (default).
While the radio is disabled:
•
SBD sessions can not be initiated; they will fail immediately.
•
No SBD Automatic Notifications will be issued for automatic-MT messages.
•
No registration, i.e. location updates will be performed.
•
The baseband circuitry is still active and the 9602 still accepts AT commands.
This command allows the FA to reduce detectable emissions from the RF circuitry during the idle periods
between SBD sessions, and also provides some, limited, power saving in cases where it may be
inconvenient for the FA to power down the 9602.
5.17 +CCLK – Real time clock
Exec Command: +CCLK
Query the 9602 for Iridium system time if available.
5.18 +CGMI – Manufacturer Identification
Exec Command: +CGMI
Query the 9602 manufacturer.
5.19 +CGMM – Model Identification
Exec Command: +CGMM
Query the 9602 model.
5.20 +CGMR – Revision
Exec Command: +CGMR
Query the 9602 revision.
5.21 +CGSN – Serial Number
Exec Command: +CGSN
Query the 9602 IMEI.
Iridium Communications Inc.
Proprietary & Confidential Information
31
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.22 +CIER – Indicator Event Reporting
Set Command: +CIER=[[,[,]]]
The set command enables or disables sending of the +CIEV unsolicited result code from the 9602 to the
DTE in case of indicator state changes. controls the processing of the +CIEV unsolicited result
codes.
:
Disable indicator event reporting; do not send +CIEV unsolicited result codes to the DTE;
buffer the most recent indicator event for each indicator in the 9602 (default).
Enable indicator event reporting; buffer the most recent +CIEV unsolicited result code for
each indicator when the data port is reserved (e.g. in SBD data mode) and flush them to
the DTE after reservation; otherwise forward them directly to the DTE.
:
Control reporting of "signal quality" indicator changes:
No "signal quality" indicator reporting.
Enable "signal quality" indicator reporting using result code
+CIEV:0,
where is:
Equivalent to 0 bars on the signal strength indicator
Equivalent to 1 bars on the signal strength indicator
Equivalent to 2 bars on the signal strength indicator
Equivalent to 3 bars on the signal strength indicator
Equivalent to 4 bars on the signal strength indicator
Equivalent to 5 bars on the signal strength indicator
The reported signal strength is the same value that would be returned by the +CSQ command.
When enabled, the signal quality indicator is reported only when the signal strength changes.
:
Control reporting of "service availability" indicator changes:
No "service availability" indicator reporting.
Enable "service availability" indicator reporting using result code
+CIEV:1,
where is:
Network service is currently unavailable.
Network service is available.
Iridium Communications Inc.
Proprietary & Confidential Information
32
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Network service availability is equivalent to a signal strength greater than 0. The service availability
indicator provides a way for the FA to wait until the 9602 can start an SBD session without receiving
continual notifications of changes in signal strength.
Read Command: +CIER?
Query the current indicator event reporting settings. The response is of the form:
+CIER:,,,
Where is not used and is included for compatibility only.
Test Command: +CIER=?
List the supported settings. The response is in the form:
+CIER:(supported s),(supported s),(supported s) ,(supported
s)
Note: In 1, the DTE may miss some indicator state changes if they occur while the data port is
reserved. However, the buffering mechanism ensures that the most recent change for each indicator
during reservation will be flushed to the DTE after reservation; thus the DTE is always made aware of the
latest state of each indicator.
Note: The DTE may initiate an SBD session even if service is unavailable; in this case, the 9602 makes
an immediate search for the network and, if successful, starts the SBD session, otherwise the SBD
session fails.
5.23 +CRIS – Ring Indication Status
Exec Command: +CRIS
Query the ring indication status, returning the reason for the most recent assertion of the Ring Indicator.
The response contains separate indications for telephony and SBD ring indications.
The response is in the form:
+CRIS:,
where indicates the telephony ring indication status (for compatibility):
No telephony ring alert received.
and indicates the SBD ring indication status:
No SBD Ring Alert received.
SBD Ring Alert received.
Note: The response is included for compatibility with 9522A applications. The results in the
response should be ignored for 9602 applications. For the 9602 only the response should be
evaluated.
Iridium Communications Inc.
Proprietary & Confidential Information
33
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.24 +CSQ – Signal Quality
Exec Command: +CSQ[F]
Execution command returns the received signal strength indication from the 9602. Response is in
the form:
+CSQ:
where:
:
Equivalent to 0 bars displayed on the signal strength indicator.
Equivalent to 1 bar displayed on the signal strength indicator.
Equivalent to 2 bars displayed on the signal strength indicator.
Equivalent to 3 bars displayed on the signal strength indicator.
Equivalent to 4 bars displayed on the signal strength indicator.
Equivalent to 5 bars displayed on the signal strength indicator.
Test Command: +CSQ=?
List the supported signal strength indications. The response is in the form:
+CSQ:(supported s)
Note: A signal strength response may not be immediately available, but will usually be received within
two seconds of issuing the command. If the 9602 is in the process of acquiring the system, a delay in
response of up to 50 seconds may be experienced.
Note: The +CSQF form of the command returns immediately, reporting the last known calculated signal
strength. Note that the signal strength returned by this command could be different from the current actual
signal strength if the +CSQ form is used. This form is included for Product Developer application
compatibility as it provides a Fast response.
Iridium Communications Inc.
Proprietary & Confidential Information
34
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.25 +CULK – Unlock
Exec Command: +CULK=
Unlock the Transceiver after it has been locked by the Gateway. The unlock key must be obtained by
contacting Iridium’s customer support.
:
0000000000000000 .. FFFFFFFFFFFFFFFF
A string of 16 hexadecimal digits.
While the Transceiver is locked, it is unable to perform any SBD sessions. Any attempts to start a
session will return an error code indicating that the Transceiver is locked.
Command Response:
+CULK:
where:
indicates the lock status of the Transceiver following the unlock attempt:
Unlocked – Transceiver is not locked and is permitted to perform SBD sessions.
Locked – Transceiver is locked and unable to perform SBD sessions. It must be
unlocked by supplying the correct unlock key to the +CULK command.
Permanently locked – Transceiver is locked and unable to perform SBD sessions. It
cannot be unlocked and must be returned to the supplier.
Read Command: +CULK?
Query the current lock status of the Transceiver. The response is of the form:
+CULK:
:
Unlocked
Locked
Permanently locked
5.26 +GMI – Manufacturer Identification
Exec Command: +CGMI
Query the 9602 manufacturer.
5.27 +GMM – Model Identification
Exec Command: +CGMM
Query the 9602 model.
5.28 +GMR – Revision
Exec Command: +CGMR
Query the 9602 revision.
Iridium Communications Inc.
Proprietary & Confidential Information
35
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.29 +GSN – Serial Number
Exec Command: +CGSN
Query the 9602 IMEI.
5.30 +IPR – Fixed DTE Rate
Set Command: +IPR=
Set the data rate at which the 9602 will accept commands. The change in data rate takes into effect after
the result code (e.g., OK) is received by the DTE.
where:
:
600 bps
1200 bps
2400 bps
4800 bps
9600 bps
19200 bps (default)
38400 bps
57600 bps
115200 bps
Read Command: +IPR?
Query the current data rate. The response is in the form:
+IPR:
Test Command: +IPR=?
List the supported data rates. The response is in the form:
+IPR:(supported settings)
Iridium Communications Inc.
Proprietary & Confidential Information
36
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.31 +SBDWB – Short Burst Data: Write Binary Data to the ISU
Exec Command: +SBDWB=
This command is used to transfer a binary SBD message from the DTE to the single mobile originated
buffer in the 9602. The mobile originated buffer can contain only one message at any one time.
•
Once the command is entered, and the message length is acceptable, the 9602 will indicate to the
DTE that it is prepared to receive the message by sending the ASCII encoded string
“READY” (hex 52 45 41 44 59 0D 0A) to the DTE.
•
The parameter represents the length, in bytes, of the SBD message not
including the mandatory two-byte checksum.
•
The maximum mobile originated SBD message length is specified at 340 bytes. The minimum mobile
originated SBD message length is 1 byte. If the parameter is out of range,
the 9602 issues response 3 (see below).
•
Once the DTE receives the READY indication from the 9602, the SBD message must be sent from
the DTE formatted as follows:
{binary SBD message} + {2-byte checksum}
•
The checksum is the least significant 2-bytes of the summation of the entire SBD message. The
high order byte must be sent first. For example if the DTE were to send the word “hello” encoded
in ASCII to the 9602 the binary stream would be hex 68 65 6c 6c 6f 02 14.
•
The mobile originated buffer will be empty upon power-up.
•
If any data is currently in the mobile originated buffer, it will be overwritten.
Command Response:
SBD message successfully written to the 9602.
SBD message write timeout. An insufficient number of bytes were transferred to 9602
during the transfer period of 60 seconds.
SBD message checksum sent from DTE does not match the checksum calculated by the
9602.
SBD message size is not correct. The maximum mobile originated SBD message length
is 340 bytes. The minimum mobile originated SBD message length is 1 byte.
Iridium Communications Inc.
Proprietary & Confidential Information
37
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.32 +SBDRB – Short Burst Data: Read Binary Data from the
Module
Exec Command: +SBDRB
This command is used to transfer a binary SBD message from the single mobile terminated buffer in the
9602 to the DTE. The mobile terminated buffer can contain only one message at any one time.
•
•
The
SBD
message
is
transferred
formatted
{2-byte message length} + {binary SBD message} + {2-byte checksum}
as
follows:
•
The {2-byte message length} field represents the length, in bytes, of the SBD message not
including the length field or the mandatory two-byte checksum. The high order byte will be sent
first.
•
The maximum mobile terminated SBD message length is length is specified at 270 bytes (and
may be increased following actual performance testing).
•
The checksum is the least significant 2-bytes of the summation of the entire SBD message. The
high order byte will be sent first. For example if the 9602 were to send the word “hello” encoded in
ASCII to the DTE the binary stream would be hex 00 05 68 65 6c 6c 6f 02 14.
•
If there is no mobile terminated SBD message waiting to be retrieved from the 9602, the message
length and checksum fields will be zero.
The mobile terminated message buffer will be empty upon power-up.
Command Response:
There are no response codes generated by the 9602 for this command.
Iridium Communications Inc.
Proprietary & Confidential Information
38
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.33 +SBDWT – Short Burst Data: Write a Text Message to the
Module
Exec Command: +SBDWT[=]
This command is used to transfer a text SBD message from the DTE to the single mobile originated buffer
in the 9602.
The text message may be entered on the command line:
•
For example, “AT+SBDWT=hello”.
•
The length of is limited to 120 characters. This is due to the length limit on the AT
command line interface.
•
The message is terminated when a carriage return is entered.
Alternatively, the text message may be entered separately:
•
Upon entering the command “AT+SBDWT”, the 9602 will indicate to the DTE that it is prepared to
receive the message by sending the string “READY” (hex 52 45 41 44 59 0D 0A) to the
DTE.
•
Once the DTE receives the READY indication, the text message must be sent, terminated by a
carriage return.
•
The length of the text message entered in this way is limited only by maximum mobile-originated SBD
message length of 340 bytes.
•
The mobile originated buffer will be empty upon power-up.
•
If any data is currently in the mobile originated buffer, it will be overwritten.
Command Response:
For the “AT+SBDWT” form:
SBD message successfully written to the 9602.
SBD message write timeout. An insufficient number of bytes were transferred to 9602
during the transfer period of 60 seconds.
For the “AT+SBDWT=” form:
OK:
SBD message successfully stored in mobile originated buffer.
ERROR: An error occurred storing SBD message in mobile originated buffer.
Iridium Communications Inc.
Proprietary & Confidential Information
39
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.34 +SBDRT – Short Burst Data: Read a Text Message from the
Module
Exec Command: +SBDRT
This command is used to transfer a text SBD message from the single mobile terminated buffer in the
9602 to the DTE. This command is similar to +SBDRB but does not provide a length indicator or
checksum. The intent of this command is to provide a human friendly interface to SBD for demonstrations
and application development. It is expected that most usage of SBD will be with binary messages.
•
Once the command is entered, the SBD message in the mobile terminated buffer is sent out of the
port.
•
This command is similar to +SBDRB except no length or checksum will be provided.
•
The maximum mobile terminated SBD message length is 270 bytes.
•
The mobile terminated message buffer will be empty upon power-up.
Command Response:
+SBDRT: {mobile terminated buffer}
Iridium Communications Inc.
Proprietary & Confidential Information
40
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.35 +SBDI – Short Burst Data: Initiate an SBD Session
Note: The +SBDI command is provided for backwards compatibility with existing FAs which do not use
SBD Automatic Notification functionality. For SBD calls invoked with this command:
•
The SBD Session Type is fixed at type 0 – MO call.
•
The SBD Delivery Short Code will be the value specified by the +SBDDSC command.
•
The Detach/Attach flag is fixed at the Detach setting.
•
The Location Update flag is fixed at the No Update setting.
FAs requiring SBD Automatic Notification functionality should use the extended +SBDIX command.
Exec Command: +SBDI
This command initiates an SBD session between the 9602 and the GSS. If there is a message in the
mobile originated buffer it will be transferred to the GSS. Similarly if there is one or more messages
queued at the GSS the oldest will be transferred to the 9602 and placed into the mobile terminated buffer.
•
The message, if any, in the mobile originated buffer will be sent from the 9602 to the GSS.
•
If there is a MT-SBD message queued at the GSS it will be transferred to the 9602 and placed into
the mobile terminated buffer.
Command Response:
+SBDI:,,,,,
where:
:
MO session status provides an indication of the disposition of the mobile originated transaction. The field
can take on the following values:
No SBD message to send from the 9602.
SBD message successfully sent from the 9602 to the GSS.
An error occurred while attempting to send SBD message from 9602 to GSS.
:
The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the 9602 when
sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is
successfully completed between the 9602 to the GSS. This wrap around counter can range from 0 to
65535.
:
The MT status provides an indication of the disposition of the mobile terminated transaction. The field can
take on the following values:
No SBD message to receive from the GSS.
SBD message successfully received from the GSS.
An error occurred while attempting to perform a mailbox check or receive a message from
the GSS.
:
The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when sending a
message to the 9602. This value is indeterminate if the field is zero. This wrap around
counter can range from 0 to 65535.
Iridium Communications Inc.
Proprietary & Confidential Information
41
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
:
The MT length is the length in bytes of the mobile terminated SBD message received from the GSS. If no
message was received, this field will be zero.
:
MT queued is a count of mobile terminated SBD messages waiting at the GSS to be transferred to the
9602.
5.36 +SBDDET – Short Burst Data: Detach
Exec Command: +SBDDET
Initiates an SBD session to stop sending SBD Ring Alerts to the Transceiver from the Gateway (detach).
Command Response:
+SBDDET:,
where:
:
Detach successfully performed
An error occurred while attempting the detach
:
Gateway-reported values
No error.
1..4
Reserved, but indicate success if used.
5..14
Reserved, but indicate failure if used.
15
Access is denied.
Transceiver-reported values
16
Transceiver 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..31 Reserved, but indicate failure if used.
32
No network service, unable to initiate call.
33
Antenna fault, unable to initiate call.
34
Radio is disabled, unable to initiate call (see *Rn command).
35
Transceiver is busy, unable to initiate call (typically performing auto-registration).
36..
Reserved, but indicate failure if used.
This command instructs the GSS to stop sending SBD Ring Alerts (detach) for the calling Transceiver.
Successful completion of the detach command implies that the GSS has performed the requested detach
action and the Transceiver will no longer receive any notifications of queued MT Messages from the GSS.
This session does not transfer any MO or MT messages.
Note: A user can send an MO-SBD message and request a detach at the same time by using the +SBDI
command. The +SBDI command always requests a detach.
Iridium Communications Inc.
Proprietary & Confidential Information
42
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.37 +SBDDSC – Short Burst Data: Delivery Short Code
Set Command: +SBDDSC=
Set the Delivery Short Code (DSC), which provides some additional options for control of MT messages.
This is an 8-bit value providing the ability to set individual fields. Value 0x80 (hexadecimal) sets the most
significant bit. Value 0x01 sets the least significant bit. Flag values can be added together to achieve a
combination of settings. Some fields may be “locked” when the Transceiver is in a special mode (e.g.
Autoregistration locks the flag values 0x80 and 0x40).
:
0x00 to 0xFF
DSC to be used for subsequent uploaded messages (0x00 is default)
0x80
Hold MT message delivery
0x40
Leave MT message in queue after delivery
Read Command: +SBDDSC?
Query the current Delivery Short Code. The response is of the form:
+SBDDSC:
Iridium Communications Inc.
Proprietary & Confidential Information
43
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.38 +SBDIX – Short Burst Data: Initiate an SBD Session Extended
Note: The +SBDIX command must be used in place of the +SBDI command for FAs wishing to make use
of SBD Automatic Notification functionality.
Exec Command: +SBDIX[A][=]
This command initiates an SBD session between the 9602 and the GSS, setting the SBD Session Type
according to the type of command +SBDIX or +SBDIXA, Delivery Short Code according to the value
specified by the +SBDDSC command, and the type of location according to whether the optional location
value is provided. If there is a message in the mobile originated buffer it will be transferred to the GSS.
Similarly if there is one or more MT messages queued at the GSS the oldest will be transferred to the
9602 and placed into the mobile terminated buffer.
•
The message, if any, in the mobile originated buffer will be sent from the 9602 to the GSS.
•
If there is a MT message queued at the GSS it will be transferred to the 9602 and placed into the
mobile terminated buffer.
•
This command will always attempt an SBD Network Registration, consisting of attach and location
update, during the SBD session in order to support SBD Automatic Notification. If this is not desired,
the +SBDI command should be used.
•
The FA should append an ‘A’ to the command, i.e. +SBDIXA, when the SBD session is in response to
SBD Ring Alert. If this option is not used, more than one SBD Ring Alert may be received.
has format:
[+|-]DDMM.MMM,[+|-]dddmm.mmm
where:
DD
Degrees latitude (00-89)
MM
Minutes latitude (00-59)
MMM
Thousandths of minutes latitude (000-999)
ddd
Degrees longitude (000-179)
mm
Minutes longitude (00-59)
mmm
Thousandths of minutes longitude (000-999)
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If
omitted, the default is +.
For example,
AT+SBDIX=5212.483,-00007.350
corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
Command Response:
+SBDIX:,,,,,
where:
:
MO session status provides an indication of the disposition of the mobile originated transaction. The field
can take on the following values:
Gateway-reported values
MO message, if any, transferred successfully.
Iridium Communications Inc.
Proprietary & Confidential Information
44
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
MO message, if any, transferred successfully, but the MT message in the queue was too
big to be transferred.
MO message, if any, transferred successfully, but the requested Location Update was not
accepted.
3..4
Reserved, but indicate MO session success if used.
5..8
Reserved, but indicate MO session failure if used.
10
Gateway reported that the call did not complete in the allowed time.
11
MO message queue at the Gateway is full.
12
MO message has too many segments.
13
Gateway reported that the session did not complete.
14
Invalid segment size.
15
Access is denied.
Transceiver-reported values
16
Transceiver 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..31 Reserved, but indicate MO session failure if used.
32
No network service, unable to initiate call.
33
Antenna fault, unable to initiate call.
34
Radio is disabled, unable to initiate call (see *Rn command).
35
Transceiver is busy, unable to initiate call (typically performing auto-registration).
36..
Reserved, but indicate failure if used.
:
The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the 9602 when
sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is
successfully completed between the 9602 to the GSS. This wrap around counter can range from 0 to
65535.
:
The MT status provides an indication of the disposition of the mobile terminated transaction. The field can
take on the following values:
No MT SBD message to receive from the Gateway.
MT SBD message successfully received from the Gateway.
An error occurred while attempting to perform a mailbox check or receive a message from
the Gateway.
:
The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when forwarding
a message to the 9602. This value is indeterminate if the field is zero. This wrap around
counter can range from 0 to 65535.
:
Iridium Communications Inc.
Proprietary & Confidential Information
45
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
The MT length is the length in bytes of the mobile terminated SBD message received from the GSS. If no
message was received, this field will be zero.
:
MT queued is a count of mobile terminated SBD messages waiting at the GSS to be transferred to the
9602.
5.39 +SBDMTA – Short Burst Data: Mobile-Terminated Alert
Set Command: +SBDMTA=
Enable or disable the ISU to listen for SBD Ring Alerts.
:
Disable SBD Ring Alert indication
Enable SBD Ring Alert ring indication (default)
When SBD Ring Alert indication is enabled, the 9602 asserts the RI line and issues the unsolicited result
code SBDRING when an SBD Ring Alert is received.
Read Command: +SBDMTA?
Query the current ring indication mode. The response is of the form:
+SBDMTA:
Test Command: +SBDMTA=?
List the supported mode settings. The response is of the form:
+SBDMTA:(supported settings)
Note: There are a number of required steps in both the ISU and the GSS in order to successfully enable
SBD Automatic Notifications. Consult the SBD Developers Guide section on Automatic Notifications for
Mobile Terminated Messages.
5.40 +SBDREG – Short Burst Data: Network Registration
Exec Command: +SBDREG[=]
Triggers an SBD session to perform a manual SBD Network Registration.
This command initiates an SBD session to perform a manual SBD Network Registration, consisting of an
attach and location update. The session type will be set to 2 – registration. This session does not
transfer any MO or MT message(s).
Note: The Transceiver restricts the number of manual and automatic registrations to one every 3
minutes. Successive attempts within 3 minutes will return an error code indicating that the FA should try
later (see error 36 below).
Note: A user can send an MO SBD message and perform a SBD Network Registration at the same time
by using the +SBDIX command. The +SBDIX command always performs a SBD Network Registration
attempt and should be used for an application requiring SBD Automatic Notification. The +SBDI
command never includes an SBD Network registration and should be used for an application that does
not require SBD Automatic Notification.
Note: If you are not using MT-SBD messages there is no requirement or benefit to using this command.
has format:
[+|-]DDMM.MMM,[+|-]dddmm.mmm
Iridium Communications Inc.
Proprietary & Confidential Information
46
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
where:
DD
Degrees latitude (00-89)
MM
Minutes latitude (00-59)
MMM
Thousandths of minutes latitude (000-999)
ddd
Degrees longitude (000-179)
mm
Minutes longitude (00-59)
mmm
Thousandths of minutes longitude (000-999)
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If
omitted, the default is +.
For example,
AT+SBDIX=5212.483,-00007.350
corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
Command Response:
+SBDREG:,
where:
indicates the resulting registration status of the Transceiver:
Detached – Transceiver is detached as a result of a successful +SBDDET or +SBDI
command.
Not registered – Transceiver is attached but has not provided a good location since it was
last detached.
Registered – Transceiver is attached with a good location. Note that this may be the
case even when the most recent attempt did not provide a good location.
Registration denied – The gateway is denying service to the Transceiver.
:
Gateway-reported values
No error.
Session completed but the requested Location Update was not accepted.
3..14
Reserved, but indicate Location Update failure if used.
15
Access is denied.
Transceiver-reported values
16
Transceiver 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..31 Reserved, but indicate failure if used.
32
No network service, unable to initiate call.
33
Antenna fault, unable to initiate call.
34
Radio is disabled, unable to initiate call (see *Rn command).
35
Transceiver is busy, unable to initiate call (typically performing auto-registration).
Iridium Communications Inc.
Proprietary & Confidential Information
47
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
36
Try later, must wait 3 minutes since last registration.
37..
Reserved, but indicate failure if used.
Read Command: +SBDREG?
Query the current SBD registration status of the Transceiver. The response is of the form:
+SBDREG:
:
Detached
Not registered
Registered
Registration denied
Unknown
The SBD Network Registration status is stored in Transceiver non-volatile memory, and can therefore be
queried by the FA after powering up. Note that if the Transceiver is powered off and then moved any
significant distance (> 150Kilometers) that the location information will be incorrect when the Transceiver
is subsequently powered on. It is recommended that Product Developers initiate a SBD Network
Registration following power on if the application is using Mobile Terminated Messages in conjunction
with SBD Ring Alerts.
Note: There are a number of required steps in both the ISU and the GSS in order to successfully enable
SBD Automatic Notifications. Consult the SBD Developers Guide section on Automatic Notifications for
Mobile Terminated Messages.
Iridium Communications Inc.
Proprietary & Confidential Information
48
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.41 +SBDAREG – Short Burst Data: Automatic Registration
Set Command: +SBDAREG=
Set the Transceiver’s automatic SBD Network Registration mode.
:
Disable Automatic SBD Network Registration (default)
Set the Automatic SBD Network Registration mode to “Automatic”
Set the Automatic SBD Network Registration mode to “Ask”
When Automatic SBD Network Registration is enabled, mode 1 or 2, the Transceiver monitors its current
location and triggers an Automatic SBD Network Registration when it determines that the Transceiver has
moved sufficiently far away from its last registered location. Note that Automatic SBD Network
Registration runs only while the Transceiver is attached to the gateway, i.e. the registration status is “Not
registered” or “Registered”.
Automatic SBD Network Registration may only be used with system-provided location. If the FA is
providing its own location (e.g. GPS), the FA should use the manual SBD Network Registration
command, +SBDREG.
Upon triggering in mode 1, “Automatic”, the Transceiver autonomously initiates an SBD session in order
to perform a SBD Network Registration with the updated location of the Transceiver, with the session type
set to 3 – auto-registration. This session does not transfer any MO or MT messages.
Upon triggering in mode 2, “Ask”, the Transceiver reports to the FA that it should register with the system
because the Transceiver location has changed (see below); it is then the responsibility of the FA
to register via +SBDREG or +SBDIX. +SBDIX allows the FA to register while including an MO message
and/or retrieving an MT message that is pending at the Gateway.
When auto-registration is enabled, mode 1 or 2, the Transceiver reports relevant events to the FA by
issuing an unsolicited result code +AREG:,.
:
Suggest FA makes a registration attempt (mode 2 only)
Auto-registration has been performed successfully (mode 1 only)
Auto-registration has failed and will be retried after a delay (mode 1 only)
:
Gateway-reported values
No error.
Session completed but the requested Location Update was not accepted.
3..14
Reserved, but indicate Location Update failure if used.
15
Access is denied.
Transceiver-reported values
16
Transceiver 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..31 Reserved, but indicate failure if used.
32
No network service, unable to initiate call.
Iridium Communications Inc.
Proprietary & Confidential Information
49
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
33
Antenna fault, unable to initiate call.
34
Radio is disabled, unable to initiate call (see *Rn command).
35
Transceiver is busy, unable to initiate call (typically performing auto-registration).
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:
Test Command: +SBDAREG=?
List the supported mode settings. The response is of the form:
+SBDAREG:(supported settings)
Note: There are a number of required steps in both the ISU and the GSS in order to successfully enable
SBD Automatic Notifications. Consult the SBD Developers Guide section on Automatic Notifications for
Mobile Terminated Messages.
5.42 +SBDD – Short Burst Data: Clear SBD Message Buffer(s)
Exec Command: +SBDD
This command is used to clear the mobile originated buffer, mobile terminated buffer or both.
•
The parameter identifies which buffers are cleared.
Clear the mobile originated buffer.
Clear the mobile terminated buffer.
Clear both the mobile originated and mobile terminated buffers.
•
Using this command or power cycling the 9602 are the only means by which both buffers are cleared.
•
The mobile terminated buffer will be cleared when an SBD session is initiated.
•
Sending a message from the 9602 to the ESS does not clear the mobile originated buffer.
•
Reading a message from the 9602 does not clear the mobile terminated buffer.
Command Response:
Buffer(s) cleared successfully.
An error occurred while clearing the buffer(s).
Iridium Communications Inc.
Proprietary & Confidential Information
50
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.43 +SBDC – Short Burst Data: Clear SBD MOMSN
Exec Command: +SBDC
This command will clear (set to 0) the mobile originated message sequence number (MOMSN) stored in
the 9602.
•
The MOMSN is maintained even after power cycle.
Command Response:
The MOMSN was cleared successfully.
An error occurred while clearing the MOMSN.
5.44 +SBDS – Short Burst Data: Status
Exec Command: +SBDS
This command returns current state of the mobile originated and mobile terminated buffers.
Command Response:
+SBDS:,,,
where:
:
The MO flag indicates the existence of a message in the mobile originated buffer. The response from the
9602 is one of the following numeric codes:
No message in mobile originated buffer
Message in mobile originated buffer
:
The MOMSN identifies the sequence number that will be used during the next mobile originated SBD
session.
:
The MT flag indicates the existence of a message in the mobile terminated buffer. The response from the
9602 is one of the following numeric codes:
No message in mobile terminated buffer
Message in mobile terminated buffer
:
The MTMSN identifies the sequence number that was used in the most recent mobile terminated SBD
session. This value will be –1 if there is nothing in the mobile terminated buffer.
Iridium Communications Inc.
Proprietary & Confidential Information
51
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
5.45 +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: , , , , ,
where:
:
The MO flag indicates the existence of a message in the mobile originated buffer. The response from the
ISU is one of the following numeric codes:
No message in mobile originated buffer.
Message in mobile originated buffer.
:
The MOMSN identifies the sequence number that will be used during the next mobile originated SBD
session.
:
The MT flag indicates the existence of a message in the mobile terminated buffer. The response from the
ISU is one of the following numeric codes:
No message in mobile terminated buffer.
Message in mobile terminated buffer.
:
The MTMSN identifies the sequence number that was used in the most recent mobile terminated SBD
session. This value will be –1 if there is nothing in the mobile terminated buffer.
:
The RA flag indicates whether an SBD Ring Alert has been received and still needs to be answered.
No SBD ring alert.
SBD ring alert has been received and needs to be answered.
Note: The RA flag is set whenever the ISU receives an SBD Ring Alert; this happens even if the
+SBDMTA setting specifies that SBD ring indications are disabled.
The RA flag is cleared only on successful completion of an SBD mailbox check, i.e. an SBD session
invoked with +SBDI[X[A]] in which the returned MT status indicates that no error occurred.
The value of the RA flag is stored in non-volatile memory so it is preserved across power cycling of the
ISU.
:
Iridium Communications Inc.
Proprietary & Confidential Information
52
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
The message waiting flag indicates how many SBD Mobile Terminated messages are currently queued at
the gateway awaiting collection by the ISU. This flag is updated after every SBD session, including
+SBDI, +SBDIX, +SBDIXA, and +SBDREG.
5.46 +SBDTC – Short Burst Data: Transfer MO Buffer to MT Buffer
Exec Command: +SBDTC
This command will transfer the contents of the mobile originated buffer to the mobile terminated buffer.
Product Developers of DTE can use this command to test reading and writing to the 9602 without actually
initiating SBD sessions with the ESS.
Command Response:
The command produces a response of the form “SBDTC: Outbound SBD copied to Inbound SBD: size =
” followed by “OK”, where:
: The length of the message in bytes.
5.47 +SBDGW – Short Burst Data: Gateway
Exec Command: +SBDGW
This command will read back the Iridium gateway that the Short Burst Data messages are being sent to.
Command Response:
The command produces a response of the form “SBDGW: ”
Where is either EMSS or non-EMSS.
5.48 -MSSTM – Request System Time
Exec Command: -MSSTM
Query the latest system time received from the network. The response is the form:
-MSSTM:
can take one of the following forms:
no network service
The 9602 has not yet received system time from the network.
XXXXXXX
Where XXXXXXXX is the current Iridium system time available from the
network. The system time as received through the Iridium Air Interface, is
a 32 bit integer count of the number of 90 millisecond intervals that have
elapsed since the epoch. The return value is formatted as an ASCII
hexadecimal number. The counter will rollover approximately every 12
years.
Iridium system time epoch: Mar 8, 2007, 03:50:35 (GMT):
Iridium system time source: The system time is available and valid only after the 9602 has found the
network and has received the Iridium system time from the network. Once the time is received, the 9602
uses its internal clock to increment the counter. In addition, at least every 8 hours, or on location update
or other event that requires re-registration, the 9602 will obtain a new system time from the network.
Time localization: None. The system time value is always expressed in GMT time.
Iridium Communications Inc.
Proprietary & Confidential Information
53
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Resolution and accuracy: The resolution of the system time is one Iridium frame tick, or 90 ms. Accuracy
as measured by the difference between the time reported and the actual time it is sent out the 9602 serial
port should not exceed 4 frame ticks (.36 seconds) and in most cases will be one frame tick (.09 seconds)
or less.
Iridium Communications Inc.
Proprietary & Confidential Information
54
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
6 S-Register Definitions
S-registers allow control over specific 9602 operations. Some S-registers contain a single numeric value,
other S-registers are bit-mapped where individual bits, or set of bits, control specific functions.
Table 6-1 defines the S-registers used for 9602 Transceiver. Some legacy S-registers from the 9522A are
obsolete for 9602 Transceiver, and 9602 Transceiver requires some new S-registers. To prevent
reallocation of obsolete S-registers, they are reserved and shaded out in the table, and the new Sregisters are registers that are unused in 9522A Transceiver and are marked as “new for 9602
Transceiver.”
All S-registers, from S0 to S127, are readable. All write permissions remain unchanged from 9522A
Transceiver, even where a writable register is not used in 9602 Transceiver. Writable registers are
highlighted in the “Sr=n writable?” column. An FA could use the unused writable S-registers to store
application-specific data.
The final column in the table indicates which S-registers are stored in non-volatile memory as part of a
user profile; the 9602 can be reset to a stored profile using the Zn command.
6.1 S-Register Commands
Commands allow S-registers to be read, written, or simply referenced (i.e. set a pointer to designate the
current, referenced S-register). S-register commands are described in the following subsections.
6.1.4 Sr – Direct S-Register Reference
Set a pointer to reference S-register r.
6.1.5 Sr? – Direct S-Register Read
Read the value of S-register r.
6.1.6 Sr=n – Direct S-Register Write
Set the value of S-register r to n, where n is a decimal value in the range 0 to 255.
6.1.7 ? – Referenced S-Register Read
Read the value of the current referenced S-register. The current referenced S-register is that which was
last acted upon by a direct reference (ATSr), read (ATSr?), or write (ATSr=n) command.
6.1.8 =n – Referenced S-Register Write
Set the value of the current referenced S-register to n. The current referenced S-register is that which
was last acted upon by a direct reference (ATSr), read (ATSr?), or write (ATSr=n) command.
Iridium Communications Inc.
Proprietary & Confidential Information
55
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
6.2 S-Registers
Table 6-1: 9602 Transceiver S-Registers
Profile Setting?
43
Not applicable to 9602Escape code character
S3
0-127
13
Carriage return character
S4
0-127
10
Line feed character
S5
0-32
Backspace character
Default
0-255
Range
S2
Register
Sr=n writable?
[Note: To prevent reallocation of obsolete S-registers, they are reserved and shaded out in the
table, and the new S-registers are registers that are unused in 9522A Transceiver and are marked
as “new for 9602 Transceiver.”]
Description
S0
Not applicable to 9602
S1
Not applicable to 9602
S6
Not applicable to 9602
S7
Not applicable to 9602
S8
Not applicable to 9602
S9
Not applicable to 9602
S10
Not applicable to 9602
S11
Not applicable to 9602
S12
Not applicable to 9602
S13
0-255
49
Bitmap register:
bits 0-1: DCE data bits
bits 2-3: DCE stop bits
bits 4-6: DCE parity setting
S14
0-255
170
Bitmap register:
bit 1: En setting (echo)
bit 2: Qn setting (quiet)
bit 3: Vn setting (verbose)
bit 5: Not applicable to 9602
S21
0-255
48
Bitmap register:
bit 0: Not applicable to 9602
bit 2: Not applicable to 9602
bits 3-4: &Dn setting (DTR operation)
bit 5: Not applicable to 9602
bit 6: Not applicable to 9602
S22
Not applicable to 9602
Iridium Communications Inc.
Proprietary & Confidential Information
56
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
61
Bitmap register:
bits 1-4: +IPR setting (DTE baud rate)
bits 6-7: Not applicable to 9602
S25
Not applicable to 9602
S27
Not applicable to 9602
S28
Not applicable to 9602
S30
Not applicable to 9602
S31
Not applicable to 9602
S34
Not applicable to 9602
S35
Not applicable to 9602
S36
Not applicable to 9602
S37
Not applicable to 9602
S39
0-255
Bitmap register:
bits 0-2: &Kn setting (flow control)
S40
Not applicable to 9602
S41
Not applicable to 9602
S42
Not applicable to 9602
S43
Not applicable to 9602
S44
Not applicable to 9602
S45
Not applicable to 9602
S47
Not applicable to 9602
S49
Not applicable to 9602
S51
Not applicable to 9602
S52
Not applicable to 9602
S54
Not applicable to 9602
S58
Not applicable to 9602
S95
Not applicable to 9602
S96
Not applicable to 9602
S98
Not applicable to 9602
S99
Not applicable to 9602
S100
Not applicable to 9602
S102
Not applicable to 9602
S103
Not applicable to 9602
Iridium Communications Inc.
Proprietary & Confidential Information
57
Profile Setting?
0-255
Description
Sr=n writable?
Default
S23
Range
Register
Revision 4
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Description
S104
Not applicable to 9602
S106
Not applicable to 9602
S107
Not applicable to 9602
S110
Not applicable to 9602
S111
Not applicable to 9602
S112
0-255
SBD upload message sequence number (high byte)
S113
0-255
SBD upload message sequence number (low byte)
S121
0-15
New for 9602 Transceiver
Profile Setting?
Sr=n writable?
Default
Range
Register
Revision 4
Bitmap register:
bit 0: +SBDMTA setting (ring indication)
bit 1-2: +SBDAREG setting (automatic registration)
S122
0-31
New for 9602 Transceiver
Bitmap register:
bit 0: *R setting (radio activity)
bits 1-4: +CIER setting (indicator event reporting)
S123
Not applicable to 9602
S124
Not applicable to 9602
S125
Not applicable to 9602
S126
Not applicable to 9602
S127
Not applicable to 9602
Iridium Communications Inc.
Proprietary & Confidential Information
58
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
7 Summary of Result Codes
Table 7- 2: Result codes
Numeric (V0)
126
Verbose (V1)
‘OK’
‘SBDRING’
127
as verbose
‘ERROR’
‘HARDWARE FAILURE:
,’
‘READY’
as verbose
‘+AREG:,’
as verbose
‘+CIEV: ,’
Iridium Communications Inc.
Proprietary & Confidential Information
59
Description
Acknowledges execution of command
MT-SBD message(s) present at gateway
(unsolicited if enabled). See section 5.39
Command not accepted
Issued at initialization in case of a hardware
failure.
Ready to receive binary message data from
DTE
Auto-registration event report. See section
5.41
Indicator event report (unsolicited if enabled).
See section 5.22
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
8 Informative Examples
8.1 Setting the Default Configuration
The FA sets the Transceiver’s default configuration to no handshaking, no flow control, radio enabled,
SBD automatic notifications enabled.
To Transceiver
(from FA)
AT&K0
To FA (from Transceiver)
Description
Disable RTS/CTS flow control
OK
AT*R1
Enable the radio
OK
AT+SBDMTA=1
Enable SBD ring indications
OK
AT&W0
Store the configuration as profile 0
OK
AT&Y0
Select profile 0 as the power-up default
OK
8.2 Power-on to Sending a Message
The FA will power up the Transceiver, wait for the Transceiver to acquire the network, and send a 70-byte
message.
To Transceiver
(from FA)
To FA (from Transceiver)
Description
Apply power to the 9602
Wait for DSR to become asserted
Enable service indication reporting (note
that this can be stored in the default
configuration)
Wait for the 9602 to acquire the network
AT+CIER=1,0,1,0
OK
+CIEV: 1,1
AT+SBDWB=70
READY
Transfer message to 9602

AT+SBDIX
+SBDIX: 0,23,0,-1,0,0
AT+SBDD0
Clear the MO message buffer
OK
Iridium Communications Inc.
Proprietary & Confidential Information
Perform SBD session
60
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
8.3 Automatic Notification Registration
The FA verifies its registration state, performs a registration in order to be able to receive automatic
notifications, and enables automatic notification indications.
To Transceiver
(from FA)
AT+SBDREG?
To FA (from Transceiver)
Description
Query the Transceiver registration status
Transceiver is detached, i.e. un-registered
Tell the Transceiver to register for
automatic notifications
Transceiver is now registered
Query the Transceiver registration status
Transceiver is registered
Enable SBD ring indications from
Transceiver to FA
+SBDREG:0
AT+SBDREG
+SBDREG:2,0
AT+SBDREG?
+SBDREG:2
AT+SBDMTA=1
OK
8.4 Automatic Notification Message Reception
The FA verifies its registration state. Upon receiving a automatic notification the FA initiates an SBD
session to receive an MT message.
To Transceiver
(from FA)
AT+SBDREG?
To FA (from Transceiver)
+SBDREG:2
…
+SBDRING
AT+SBDIXA
+SBDIXA:0,23,1,237,90,2
AT+SBDRB

Iridium Communications Inc.
Proprietary & Confidential Information
61
Description
Query the Transceiver registration status
Transceiver is registered
Vendor application sends an MT message
to the GSS
Transceiver indicates an incoming
message. The RI line also toggles.
FA initiates an SBD session in answer to
the automatic notification
Transceiver informs FA that a 90-byte
message was successfully received with
MTMSN 237, and that two further MT
messages are queued at the GSS
FA retrieves the received message from
the Transceiver
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
8.5 Automatic Notification Automatic Registration
The FA verifies its registration state and enables automatic registration using the “Ask” mode.
To Transceiver
(from FA)
AT+SBDREG?
To FA (from Transceiver)
Description
Query the Transceiver registration status
Transceiver is registered
FA sets the automatic registration to “Ask”
mode
Transceiver is moved
Transceiver notifies FA that it needs to
register
FA instructs the Transceiver to register
Registration is successful
+SBDREG:2
AT+SBDAREG=2
OK
…
+AREG:0,0
AT+SBDREG
+SBDREG:2,0
8.6 Sending a Message with Minimal Radio Activity
Assuming that service indication events have been turned on with AT+CIER=1,0,1, and the radio has
been disabled with AT*R0.
To Transceiver
(from FA)
AT+SBDWB=70
To FA (from Transceiver)
READY
Description
Transfer message to 9602

AT*R1
Activate the radio and wait for the
Transceiver to acquire the network
Transceiver has acquired the network
OK
+CIEV:1,1
AT+SBDI
+SBDI: 0,23,0,-1,0,0
AT*R0
Perform SBD session
Deactivate the radio
OK
AT+SBDD0
Clear the MO message buffer
OK
8.7 Powering Down
The FA flushes any pending Eeprom writes before powering down the Transceiver.
To Transceiver
(from FA)
AT*F
To FA (from Transceiver)
FA tells Transceiver to flush pending
writes to Eeprom and waits for completion
FA may now safely disconnect the
Transceiver power supply.
OK

Iridium Communications Inc.
Proprietary & Confidential Information
Description
62
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
9 Supported AT Commands
Table 9-3, lists the AT commands supported by the 9602 module. This list of supported commands is a
subset of commands taken from Iridium’s AT Command Specification.
Table 9-3: Supported AT commands
Command
Description
AT
A/
En
In
Qn
Vn
Zn
&Dn
&Fn
&Kn
&V
&Wn
&Yn
%R
*F
*Rn
Attention code
Repeat last command
Echo
Identification
Quiet mode
Verbose mode
Soft reset
DTR option
Restore factory settings
Flow control
View active and stored configuration
Store active configuration
Designate default reset profile
Display registers
Flush to EEPROM
Radio activity
+CCLK
Real-time clock
+CGMI
+CGMM
+CGMR
+CGSN
+CIER
+CRIS
+CSQ
+CULK
+GMI
+GMM
+GMR
+GSN
+IPR
+SBDAREG
+SBDC
+SBDD
+SBDDET
+SBDDSC
+SBDI
+SBDIX
+SBDIXA
+SBDMTA
Manufacturer identification
Model identification
Revision
Serial number
Indicator event reporting
Ring Indicator Status
Signal quality
Unlock
Manufacturer identification
Model identification
Revision
Serial number
Fixed DTE rate
Short burst data: Automatic registration
Short burst data: Clear SBD MOMSN
Short burst data: Clear SBD message buffers
Short burst data: Detach
Short burst data: Delivery short code
Short burst data: Initiate an SBD session
Short burst data: Initiate an SBD session extended
Short burst data: Initiate an SBD session extended
Short burst data: Mobile-terminated alert
Iridium Communications Inc.
Proprietary & Confidential Information
Note
Reads Iridium Network time if
available
63
Manual
Distribution of Guide Restricted
to Product Developers Only
Iridium Communications Inc.
9602 SBD Transceiver Product Developers Guide
Information Contained in this Guide
is Subject to Change Without Notice
Revision 4
Command
Description
+SBDRB
+SBDREG
+SBDRT
+SBDS
+SBDSX
+SBDTC
+SBDWB
+SBDWT
-MSSTM
Short burst data: Read binary data from ISU
Short burst data: Automatic registration
Short burst data: Read a text message from the ISU
Short burst data: Status
Short Burst data Status Extended
Short burst data: Transfer MO buffer to MT buffer
Short burst data: Write binary data to the ISU
Short burst data: Write a text message to the ISU
Request system time
Iridium Communications Inc.
Proprietary & Confidential Information
Note
64
Manual
Distribution of Guide Restricted
to Product Developers Only

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : Yes
XMP Toolkit                     : 3.1-701
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Creator Tool                    : PScript5.dll Version 5.2.2
Modify Date                     : 2010:03:10 14:44:03Z
Create Date                     : 2010:03:10 14:44:03Z
Format                          : application/pdf
Title                           : Microsoft Word - 9602 SBD Transceiver Product Developers Guide v4_0.doc
Creator                         : mc3
Document ID                     : uuid:3767355c-931a-44b9-9563-bca2c70e89f2
Instance ID                     : uuid:b82a5d2c-85d9-47b7-9b27-459a941afc5c
Page Count                      : 64
Author                          : mc3

EXIF Metadata provided by EXIF.tools

Iridium Satellite 9602 Iridium Satellite Transceiver Module 9602 User Manual manual

Iridium Satellite LLC Iridium Satellite Transceiver Module 9602 manual

Contents

manual

FCC ID Filing: Q639602

Navigation menu

Namespaces

Views

Navigation