Iridium 9602 SBD Transceiver Developer ’s Guide

7/31/2019 Iridium 9602 SBD Transceiver Developer s Guide

1/67

I r id ium 9602 SB D Tra nsceiver Developer s Guide

I r id ium Communicat ions Inc.

Propr ie tary & Conf ident ia l In format ion

Iridium Communications Inc.6707 Democracy Blvd., Suite 300

Bethesda, MD 20817 USAwww.iridium.com

Toll Free: +1.866.947.4348 [US Only]International +1.480.752.5155

email:[email protected]
http://www.iridium.com/http://www.iridium.com/mailto:[email protected]:[email protected]:[email protected]:[email protected]://www.iridium.com/


2/67

Iridium Communications Inc. Information Contained in this Guide9602 SBD Transceiver Product Developers Guide is Subject to Change Without Notice

Revision 6.0

Iridium Communications Inc. Distribution of Guide RestrictedProprietary & Confidential Information 2 to Product Developers Only

LEGAL DISCLAIMER AND CONDITIONS OF USE

This document contains information for the Iridium 9602 Short Burst Data Transceiver and accompanyingaccessories (Product)is provided as is. The purpose of providing such information is to enable ValueAdded 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 makethe information in this document reliable and consistent with specifications, test measurements and otherinformation. 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 discretionand without notice to you to change Product specifications and materials and/or revise this document orwithdraw it at any time. The Product Developer assumes the full risk of using the Product specificationsand any other information provided.

IRIDIUM MAKES NO REPRESENTATIONS, GUARANTEES, CONDITIONS OR WARRANTIES,EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIEDREPRESENTATIONS, GUARANTEES, CONDITIONS OR WARRANTIES OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, SATISFACTORY QUALITY,

NON-INTERFERENCE, ACCURACY OF INFORMATIONAL CONTENT, OR ARISING FROM ACOURSE OF DEALING, LAW, USAGE, OR TRADE PRACTICE, USE, OR RELATED TO THEPERFORMANCE OR NONPERFORMANCE OF ANY PRODUCTS, ACCESSORIES, FACILITIES ORSERVICES OR INFORMATION EXCEPT AS EXPRESSLY STATED IN THIS GUIDE AND/OR THEPRODUCT AND/OR SATELLITE SERVICE DOCUMENTATION. ANY OTHER STANDARDS OFPERFORMANCE, GUARANTEES, CONDITIONS AND WARRANTIES ARE HEREBY EXPRESSLYEXCLUDED AND DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW. THISDISCLAIMER AND EXCLUSION SHALL APPLY EVEN IF THE EXPRESS LIMITED WARRANTYCONTAINED 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 OTHERLEGAL THEORY, INCLUDING WITHOUT LIMITATION STRICT LIABILITY, GROSS NEGLIGENCE ORNEGLIGENCE, FOR ANY DAMAGES IN EXCESS OF THE PURCHASE PRICE OF THE PRODUCT,INCLUDING ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OFANY KIND, OR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF PRIVACY, LOSSOF USE, LOSS OF TIME OR INCONVENIENCE, LOSS OF INFORMATION OR DATA, SOFTWAREOR APPLICATIONS OR OTHER FINANCIAL LOSS CAUSED BY THE PRODUCT (INCLUDINGHARDWARE, SOFTWARE AND/OR FIRMWARE) AND/OR THE IRIDIUM SATELLITE SERVICES, ORARISING OUT OF OR IN CONNECTION WITH THE ABILITY OR INABILITY TO USE THE PRODUCT(INCLUDING HARDWARE, SOFTWARE AND/OR FIRMWARE) AND/OR THE IRIDIUM SATELLITESERVICES TO THE FULLEST EXTENT THESE DAMAGES MAY BE DISCLAIMED BY LAW ANDWHETHER ADVISED OF THE POSSIBILITIES OF SUCH DAMAGES. IRIDIUM IS NOT LIABLE FORANY 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 activityauthorized under the agreement(s) between you and Iridium, and is otherwise subject to allapplicable 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 orvisitwww.bis.doc.gov.
http://www.bis.doc.gov/http://www.bis.doc.gov/http://www.bis.doc.gov/http://www.bis.doc.gov/


3/67


Revision 6.0


Revision History

Revision Date Comment

1 Sep 11 2009 First revision adapted from 9601 Product Developers Guide v1.25

2 5 Oct 20 2009 Updated following feedback from ISLLC6 Mar 29 2010 Updated following feedback Iridium 9602 Factory Prototype 2(FP-2) build


4/67


Revision 6.0


Contents

Revision History ............................................................................................................................................ 3Contents ...................................................................................................................................................... 4

List of Abbreviations ...................................................................................................................................... 61 Product Overview ................................................................................................................................. 7

1.1 Key Features .......................................................................................................................... 71.2 Transceiver Packaging and Regulatory Certification ............................................................. 81.3 Software Revision .................................................................................................................. 9

2 Physical Specification ......................................................................................................................... 102.1 Module Dimensions ............................................................................................................. 102.2 Mechanical Dimensions Motherboard Mounting............................................................... 122.3 Environmental ...................................................................................................................... 15

2.3.4 Environmental Specification ................................................................................................. 152.3.5 Environmental Tests Performed .......................................................................................... 15

2.4 Physical Interface Connectors ............................................................................................. 153 Electrical Interfaces ............................................................................................................................ 17

3.1 User Connector .................................................................................................................... 173.1.4 User Connector Type ........................................................................................................... 173.1.5 User Connector Pin Allocation ............................................................................................. 18

3.2 DC Power Interface .............................................................................................................. 203.2.4 Power On/Off Control ........................................................................................................... 213.2.5 Typical Power Usage Profile ................................................................................................ 21

3.3 Serial Data Interface ............................................................................................................ 233.3.4 9-Wire and 3-Wire Operation ............................................................................................... 233.3.5 Configuration Settings .......................................................................................................... 243.3.6 Modes of Operation ............................................................................................................. 253.3.7 Serial port signal levels ........................................................................................................ 25

3.4 Hardware Failure Reporting ................................................................................................. 253.5 Network Available Output .................................................................................................... 263.6 DC Supply Indicator Output ................................................................................................. 26

4 RF Interface ........................................................................................................................................ 274.1 RF Connector Types ............................................................................................................ 274.2 ANT Connector .................................................................................................................... 27

4.2.4 Antenna Characteristics ....................................................................................................... 274.3 GPS Connector .................................................................................................................... 294.4 R F In te rface Specif icati ons ........................................................................................ 304.5 Radio Character ist ics ..................................................................................................... 304.6 S-meter Performance ........................................................................................................... 30

5 AT Command Set Description ............................................................................................................ 315.1 AT ATtention Code ........................................................................................................... 315.2 A/ - Repeat Last Command ................................................................................................. 315.3 En Echo ............................................................................................................................. 315.4 In Identification .................................................................................................................. 32

5.5 Qn Quiet Mode .................................................................................................................. 325.6 Vn Verbose Mode ............................................................................................................. 325.7 Zn Soft Reset .................................................................................................................... 325.8 &Dn DTR Option ............................................................................................................... 325.9 &Fn Restore Factory Settings ........................................................................................... 325.10 &Kn Flow Control .............................................................................................................. 335.11 &V View Active and Stored Configuration ........................................................................ 335.12 &Wn Store Active Configuration ....................................................................................... 335.13 &Yn Designate Default Reset Profile ................................................................................ 33


5/67


Revision 6.0


5.14 %R Display Registers ....................................................................................................... 335.15 *F Flush to EEPROM ........................................................................................................ 335.16 *Rn Radio Activity ............................................................................................................. 345.17 +CCLK Real time clock ..................................................................................................... 345.18 +CGMI Manufacturer Identification ................................................................................... 345.19 +CGMM Model Identification ............................................................................................ 345.20 +CGMR Revision .............................................................................................................. 345.21 +CGSN Serial Number...................................................................................................... 345.22 +CIER Indicator Event Reporting ...................................................................................... 355.23 +CRIS Ring Indication Status ........................................................................................... 365.24 +CSQ Signal Quality ......................................................................................................... 375.25 +CULK Unlock .................................................................................................................. 385.26 +GMI Manufacturer Identification ...................................................................................... 385.27 +GMM Model Identification ............................................................................................... 385.28 +GMR Revision ................................................................................................................. 385.29 +GSN Serial Number ........................................................................................................ 395.30 +IPR Fixed DTE Rate ....................................................................................................... 395.31 +SBDWB Short Burst Data: Write Binary Data to the ISU ................................................ 405.32 +SBDRB Short Burst Data: Read Binary Data from the Module ...................................... 415.33 +SBDWT Short Burst Data: Write a Text Message to the Module ................................... 42

5.34 +SBDRT Short Burst Data: Read a Text Message from the Module ............................... 435.35 +SBDI Short Burst Data: Initiate an SBD Session ............................................................ 445.36 +SBDDET Short Burst Data: Detach ................................................................................ 455.37 +SBDDSC Short Burst Data: Delivery Short Code ........................................................... 465.38 +SBDIX Short Burst Data: Initiate an SBD Session Extended ......................................... 475.39 +SBDMTA Short Burst Data: Mobile-Terminated Alert ..................................................... 495.40 +SBDREG Short Burst Data: Network Registration ......................................................... 495.41 +SBDAREG Short Burst Data: Automatic Registration .................................................... 525.42 +SBDD Short Burst Data: Clear SBD Message Buffer(s) ................................................. 535.43 +SBDC Short Burst Data: Clear SBD MOMSN ................................................................ 545.44 +SBDS Short Burst Data: Status ...................................................................................... 545.45 +SBDSX - Short Burst Data: Status Extended .................................................................... 555.46 +SBDTC Short Burst Data: Transfer MO Buffer to MT Buffer .......................................... 56

5.47 +SBDGW Short Burst Data: Gateway .............................................................................. 565.48 -MSSTM Request System Time ....................................................................................... 56

6 S-Register Definitions ......................................................................................................................... 586.1 S-Register Commands ......................................................................................................... 58

6.1.4 Sr Direct S-Register Reference ........................................................................................ 586.1.5 Sr? Direct S-Register Read .............................................................................................. 586.1.6 Sr=n Direct S-Register Write ............................................................................................ 586.1.7 ? Referenced S-Register Read ......................................................................................... 586.1.8 =n Referenced S-Register Write ....................................................................................... 58

6.2 S-Registers .......................................................................................................................... 597 Summary of Result Codes ................................................................................................................. 628 Informative Examples ......................................................................................................................... 63

8.1 Setting the Default Configuration ......................................................................................... 63

8.2 Power-on to Sending a Message ......................................................................................... 638.3 Automatic Notification Registration ...................................................................................... 648.4 Automatic Notification Message Reception ......................................................................... 648.5 Automatic Notification Automatic Registration ..................................................................... 658.6 Sending a Message with Minimal Radio Activity ................................................................. 658.7 Powering Down .................................................................................................................... 65

9 Supported AT Commands .................................................................................................................. 66


6/67


Revision 6.0


List of Abbreviations

Abbreviation Description

CE Conformit Europene

CTS (V.24 signal) Clear To Send. This signal is used to control the flow of data tothe Iridium9602

DC Direct Current

DCD (V.24 signal) Data Carrier Detect

DCEData Communications Equipment. In this Product, DCE refers to the Iridium9602

DSR(V.24 signal) Data Set Ready. This signal, from the Iridium 9602, indicatesreadiness to accept communication over the data port

DTE Data Terminal Equipment. In this Product, DTE refers to the FA

DTR(V.24 signal) Data Terminal Ready. This signal, from the FA, requests theIridium 9602 to accept communication over the data port

ESS ETC SBD Subsystem (synonymous with GSS)

ETC Earth Terminal ControllerFA Field Application; the application controlling the Iridium 9602

FCC Federal Communications Commission

GND Ground

GSS Gateway SBD Subsystem (synonymous with ESS)

IC Industry Canada

IMEI International Mobile Equipment Identity

LBT L-Band Transceiver

MO Mobile Originated

MOMSN Mobile Originated Message Sequence Number

MT Mobile Terminated

MTMSN Mobile Terminated Message Sequence Number

RHCP Right Hand Circular Polarization

RI(V.24 signal) Ring Indicate. This signal, from the Iridium 9602, indicates thatan MT message is present at the GSS

RTS(V.24 signal) Request To Send. This signal is used to control the flow of datafrom the Iridium 9602.

SBD 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


7/67


Revision 6.0


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 aspecific application or vertical market. Examples of these solutions include tracking a maritime vessel orautomatic vehicle location.

The 9602 only supports Iridiums Short Burst Data (SBD) capability. It does not support voice, circuitswitched data, or short message service (SMS).

The 9602 is designed to meet the regulatory requirements for approval for FCC, Canada, and CEassuming an antenna with a gain of ~3 dBi and adequate shielding. This allows the 9602 to be integratedinto a variety of wireless data applications or retrofitted into existing SBD only applications that utilize SBDwith the current Iridium 9601, 9522A, 9522B or 9522 L-Band transceiver-based products. (Note thatadditional development work will be required). Such finished products, when integrated together, requireregulatory 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 deviceinterfaces provided by a single multi-pin interface connector in addition to the antenna connector. TheProduct 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 andantenna must be provided by the solution developer. The device interface across the user connectorconsists 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 known as a SIM Card) tobe inserted into the Transceiver. The 9602 is intended to be used as a transceiver module fitted withinanother host system. The 9602 module is designed to comply with the standards for Radio EmissionsCompliance, 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 cabledistribution 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 cardDesigned 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 theGateway

Global operating capability

RoHS compliant


8/67


Revision 6.0


1.2 Transceiver Packaging and Regulatory Certification

The 9602 SBD Transceiver is a regulatory approved daughter module transceiver that can be fitted withinan enclosed host system. With appropriate external connections, the host system can be designed tomeet 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.

RegulatoryApprovals

Radio Tests EMC Tests

Electrical /Mechanical /OperationalSafety Tests

CE ETSI EN 301 441 V1.1.1(2000-05)

ETSI EN301 489-1 V1.8.1(2008-04)

ETSI EN 301 489-20 V1.2.1(2002-11)

EN60950-1:2006Part 1

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:2006IndustryCanada

Industry CanadaRSS170 Issue 1, Rev 1,November 6, 1999

Note:The initial 9602 FP1 & FP2 prototype units are different from the commercially produced 9602 SBDTransceivers from a regulatory and certification perspective. Those initial units cannot and should not beused for any commercial purpose or for any regulatory certification or compliance purposes. Only thecommercial 9602 units conform to the regulatory approved design and the regulatory and technicalcertifications listed in Table 1.


9/67


Revision 6.0


1.3 Software Revision

Product Developers should read this document in conjunction with the Software Release Notes relevantto 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 transceivermay have an earlier software release and may therefore have different capabilities to those listed in thisdocument. Product Developers are advised to ensure that production procedures for finished goodsconfirm that the software used in the Product Developer application is designed for the Software Releaseloaded in the 9602 SBD Transceiver. This can be read out of the module using the AT commandinterface. A software upgrade utility is provided with each SW release. The utility runs on a Windowscompatible OS and will automatically upgrade the modem with the latest version.


10/67


Revision 6.0


2 Physical Specification

For illustrative purposes a picture of the Iridium 9602 SBD Transceiver Module is shown in Figure 1.

Figure 1 Iridium 9602 SBD Transceiver

2.1 Module Dimensions

The overall dimensions of the 9602 module and its weight are summarized in Table 2 and representedgraphically in Figure 2

Table 2: 9602 Mechanical Dimensions

Parameter ValueLength 41.0 mmWidth 45.0 mmDepth 13.0 mm

Weight (approximate) 30g

Additionally host system Product Developers should plan space for connection to the host systemmotherboard, including robust and electrically grounded connections to the antenna/cable distributionsystem.


11/67


Revision 6.0


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 specify the mechanical position of itsconnectors with respect to its mounting holes.

Note: Iridium is currently working on providing updated Figure 2, to reflect the diameter of the mountingholes and tolerance drawings for the cut out. At the time of this documentation release these items werenot available and will be provided in a later release.


12/67


Revision 6.0


2.2 Mechanical Dimensions Motherboard Mounting

The 9602 SBD Transceiver must be fitted within an enclosed host system. With appropriate externalconnections, the host system motherboard and host system enclosure can be designed to meet fulltransceiver regulatory tests.

The 9602 SBD Transceiver is provided with two mounting holes, one at each diagonal corner. Themodule should be assembled onto the motherboard of the host system, by pushing the module ontomatching connectors on the motherboard and then securing the diagonal mounting holes to themotherboard using mechanical fasteners.

The figures and tables below provide mechanical information design information to connect a 9602module to a host system motherboard.

Figure 3 General assembly of the 9602 onto motherboard of the host system.


13/67


Revision 6.0


Figure 4 Example host system motherboard footprint showing mounting position of 9602

(Not to scale. Dimensions in millimeters)


14/67


Revision 6.0


Notes for Error! Reference source not found.

1. This example of a host system motherboard footprint is shown for illustrative purposes only. The hostsystem may require a different PCB layout or mechanical arrangement.

2. The 9602 is designed to be incorporated within a host system. As such, the antenna or cabledistribution system that feeds the host system should be terminated in a robust RF connector that issuitable for the end-application.

3. Safety isolation requirements for external antennas or cable distribution systems should also be takeninto consideration when designing the motherboard. A suitably safe design for the RF connectionsshould be incorporated into the host system motherboard, ideally using a chassis-bonded groundconnection to the antenna cable shield.

4. The surface below the modem should be a conductive ground plane such that the modem bonds tothe motherboard ground system thus reducing the possibility of radiated emissions. This also requiresthat 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 temperaturesin excess of 60 deg C will make the caseworks considerably hot.


15/67


Revision 6.0


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 ValueOperating Temperature Range -40C to + 85C

Operating Humidity Range 75% RHStorage Temperature Range -40C to + 85C

Storage Humidity Range 93% RH

2.3.5 Environmental Tests PerformedThe 9602 has been tested to the specifications listed in Table 6.

Table 6: Environmental Tests

Test Name Test Reference Test Description

Thermal Shock EN60068-2-14:2000Change of Temperature,

-25C to +70C,5 cycles of 1 hour each

Humidity IEC60068-2-78:2002Damp heat steady state40

OC 93% RH for 4 days

Vibration EN 60068-2-36:19960.96 m2/s3 from 5Hz to 20Hz

21Hz to 500Hz dropping -3dB per octave

Vibration J1455 Society of Automotive Engineers10-40Hz at 0.02g /Hz

40-500Hz dropping 6dB per octave

ShockEN60068-2-27:1993

(NF c20-727)

Shock J1455 Society of Automotive EngineersDrop 1m onto concrete in 3 perpendicular

orientations (3 drops)Also 10G shock over a period of 12ms

2.4 Physical Interface Connectors

The Iridium 9602 SBD Transceiver incorporates three connectors:

A multiway user connector

An RF antenna connectorA GPS RF pass-through connector

The physical characteristics of the connectors and their electrical interfaces are described in more detail

1Operating Temperature Range based on a duty-cycled usage model with 9602 sending one SBD message per hour

and is otherwise turned off during the hour. Iridium has tested the 9602 per these temperature condition and

partners venturing outside of these stated conditions need to ensure they have engineered a solution appropriate to

the stated environmental conditions for the 9602.


16/67


Revision 6.0


in Sections 3.1.4 and 4.1 respectively.


17/67


Revision 6.0


3 Electrical Interfaces

The following subsections contain information for the electrical interfaces of the 9602 SBD Transceiver forthe non-RF connections. The RF interfaces are covered in section 4.

3.1 User ConnectorThe 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 thehost 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 numberCLP-110-02-L-D.
http://www.samtec.com/technical_specifications/overview.asp?series=EHThttp://www.samtec.com/technical_specifications/overview.asp?series=EHThttp://www.samtec.com/technical_specifications/overview.asp?series=EHThttp://www.samtec.com/technical_specifications/overview.asp?series=EHT


18/67


Revision 6.0


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 thelimits 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 onepin. Multiple signal grounds are provided to reduce cross-talk.

Table 7: User Connector Pin Allocation

PinNo.

Signal NameSignal

direction(WRT 9602)

Signal function Signal level

1 EXT_PWR Input Supply +5 V +/- 0.5 V2 EXT_PWR Input Supply +5 V +/- 0.5 V

3 EXT_GND Input Supply return 0 V4 EXT_GND Input Supply return 0 V

5 ON/OFF Input On/Off control input

Analog

On: >=2.0VOff:


19/67


Revision 6.0


Figure 5provides a reference for the pin designation. This view is not to scale and not representative ofthe connector mechanical layout. This view is for illustrative purposes only. This view designation iswhen looking into the user connector towards the 9602 module.

The numbers indicate pin designation. Additionally, on the 9602 PCB, pin 1 on the user connector isindicated on the board silkscreen.

Figure 5 User Connector Pin Number Designation (from below module)


20/67


Revision 6.0


3.2 DC Power Interface

The DC power interface is comprised of the DC power inputs and a control signals as summarized inTable 7. The +5V Inputs and 0V supply returns are used to supply DC power to the 9602 and ensure thatenough current can be drawn across the connector without the 9602 malfunctioning during transmit dueto 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 theserequirements apply to DC power measured at the 9602 User connector input and not at the output of thepower supply. Long power supply cables can cause a voltage drop sufficient to cause the voltage to beout of specification at the physical power supply input to the 9602.

Table 9: DC Power Input Specifications

Parameter ValueSupply Input Voltage Range 5.0V DC +/-0.5VSupply Input Voltage Ripple < 40 mV pp

Typical Power Consumption at +5.0 VDC Value

Idle Current (average*) 45mAIdle Current (peak) 195mATransmit Current (peak) 1.5 ATransmit Current (average*) 190mAReceive Current (peak) 195mAReceive Current (average*) 45mASBD message transfer - average current* 190 mASBD message transfer - average power*


21/67


Revision 6.0


3.2.4 Power On/Off ControlAn external on/off input is provided on a pin of the User connector. The 9602 starts up when power isapplied and the power on/off input is high. As long as the input voltage is applied, logic high on this lineturns the transceiver on and a logic low turns it off. If this line is not required then it must be connecteddirectly to the +5 V supply.

Note that this on/off control is similar to the 9601 product but it is not the same as the 9522, 9522A or9522B products.

Prior to turning off the modem a flush memory (AT*F) command should be issued to ensure all memorywrite activity is completed. When a transceiver has been turned off, Product Developers should notreapply 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 itback on.

When a 9602 is powered off the power on reset circuit requires 2 seconds for voltages to decay. If the 2second wait time is not adhered to the reset circuit may not operate and the modem could be placed in anon-operational state. The state is not permanent and can be rectified by the above procedure.

3.2.5 Typical Power Usage Profile

This section is designed to give the Product Developer some insight to the electrical power profile that the9602 uses. It does not describe every situation and permutation possible. It should be used as a startingpoint for the Product Developer to continue its own development design. The actual usage profile canvary 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 betweenthe transceiver and the satellite.

2) The higher the antenna VSWR the higher the current consumed3) How often the 9602 module is activated/deactivated by the Host Controller system4) Manufacturing variation from transceiver to transceiver.

The host system designer should ensure their design covers for worst case power consumptionscenarios. Figure 6 provides a graphical representation of the typical supply current profile of a 9602 SBDTransceiver sending and receiving SBD messages.


22/67


Revision 6.0


Figure 6 Typical Supply Current Profile

0

0.1

0.2

0.3

0.4

0.7

0.6

0.5

0.8

0.9

1.0

1.1

1.2

1.3

1.4

1.5

1.6

-10 0 10 20 30 40 50 60

SupplyC

urrent(A)

Time(mS)

70

Transmitterdataburst(Typically1.5A)

Background(Typically40mA)

Receiverdataburst(Typically195mA)


23/67


Revision 6.0


3.3 Serial Data Interface

The Serial data interface is used to both command the 9602 and transfer user data to and from theTransceiver. The 9602 presents a 9-wire data port to the FA (Field Application), where the interface is at3.3V digital signal levels. With respect to this interface, the 9602 behaves as a DCE (DataCommunication 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 terms9602 and DCE. Autobaud is not supported in 9602 SBD Transceiver. The baud rate can be set via theAT+IPR command. The default rate is 19200 bps.

3.3.4 9-Wire and 3-Wire OperationBy 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 Description

RX Active high data output [The DTE receives the data from the 9602]

TX Active high data input [Data is transmitted from the DTE to the 9602]

GND 0VRTS Active low flow control input

CTSActive low flow control outputRTS and CTS are used together to implement hardware flow control when enabled withAT&K3

DTR

Active low handshaking inputAT&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 10seconds, or immediately on boot-up. A subsequent transition of DTR to ON returnsthe 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 FAshould never activate test mode; if it does, the 9602 will stop responding to AT

commands until the data port is returned to DCE mode.

DSR

Active low handshaking outputThe 9602 drives DSR ON when the data port is in DCE mode, and OFF when the dataport is in test mode.The DTE may use this signal as an indication that the 9602 is powered up and ready toreceive AT commands.

RI

Active low ring indicator outputThe 9602 drives RI ON when it receives a Automatic Notification from the network that aMobile Terminated SBD Message is queued at the Gateway, and drives RI OFF after 5seconds or when the DTE initiates an SBD session, whichever occurs first.

DCDActive low handshaking outputDCD is driven OFF at all times.

Note that the Ring Indicator (RI) pin is used by the 9602 SBD Transceiver to indicate that a MobileTerminated SBD (MT-SBD) message is queued at the Gateway. The Field Application can monitor thispin and use appropriate AT Commands to command the Transceiver to retrieve the MT-SBD message.


24/67


Revision 6.0


The serial interface may be operated with a 3-wire connection, where only transmit, receive and groundsignals are used. However the 9 wire interface offers better control and is the recommendedimplementation. Iridium is only able to provide limited 3-wire interface support. Due to the small codespace and limited processing resources of the 9602 the flow control is limited.

When operating with a 3-wire 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 serialinterface 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 configurationtypes are active, factory default, and stored. The active configuration is the set of parameters currently inuse. They can be changed by the DTE individually via specific AT commands. The factory defaultconfiguration is stored in permanent memory. This configuration can be recalled at any time through useof 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. Theseprofiles can be designated to be loaded as the active configuration upon 9602 power-up through use ofthe AT&Yn command. The 9602 can be reset without loss of power to these profiles through use of theATZn command.

The configuration settings are stored in S-register locations and are detailed further in section 6.


25/67


Revision 6.0


3.3.6 Modes of Operation

The serial interface is always in one of three modes: command mode, SBD data mode or SBD sessionmode. When the data port is in command mode, AT commands can be entered to control the 9602. Incommand 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 theDTE.

In SBD data mode:

All characters from the DTE not forming part of the message data are ignored (i.e. no ATcommands 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 transferof data to the DTE; when CTS is OFF (high), the 9602 expects the DTE to suspend transfer of data tothe 9602.

When in SBD session mode, the 9602 is attempting to conduct an SBD session with the network. In SBDsession 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 theSBD 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 RS232link 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).


26/67


Revision 6.0


3.5 Network Available OutputThis is a digital output that can be used by an application to know when the transceiver has visibil ity to thesatellite network. This is useful in applications where the transceiver may move around terrain thatreduces the amount of time that clear line of sight to the satellite constellation is available. The ProductDeveloper can use this output to preserve battery life by reducing the number of attempted transmissionsby including this logic output in the application decision logic.

Network Available means only that the 9602 can successfully receive the Ring Channel, or, put moresimply, it can see an Iridium satellite. Network Available is not a guarantee that a message can besuccessfully sent. The Network Available state is evaluated every time the Ring Channel is received ormissed. If the Ring Channel is visible, then that is typically every 4 seconds. If the Ring Channel is notcurrently visible, then the update period can be as long as 2 minutes, depending on how long the lack ofsatellite visibility existed. This is because the 9602 attempts to conserve power by increasing the ringsearch interval while the satellites are not visible. Every time a ring search fails, the time to wait isincreased and eventually limits at 120 seconds.

If Network Available is currently off, the Field Application may still attempt an SBDI[X] session. This willforce the 9602 Transceiver to look for the Ring Channel immediately, and on finding it, to attempt to sendthe 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 RingChannel is present. After the SBD session completes, the 9602 performs a new Ring Channel searchsequence, at the end of which Network Available gets turned on. That can take between 4 and 12seconds.

The wait time between search windows is reset to 4 seconds every time a search succeeds. Otherwise itcontinues to increase. So if the +SBDI attempt fails to find the ring channel, the search window does notreset 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 OutputA 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 usedin application logic to determine if the internal Transceiver power supply is on.


27/67


Revision 6.0


4 RF Interface

This section describes the physical characteristics of the RF connectors and specifications of the RFInterface.

4.1 RF Connector TypesWhen mating to the 9602 RF connector use MMCX male connectors from SAMTEC part number MMCX-P-P-H-ST-TH1. This is a thru hole printed circuit mount connector with the correct mechanical spacing to

allow the 9602 to fit flush on the motherboard.

Note - this 9602 module has a different antenna connector than Iridium transceivers.

Both RF connectors on the 9602 module are intended for an inter-board connection to the host systemmotherboard and should not be directly connected to an external antenna cable or cable distributionsystem.

Additional information can be found at: http://www.samtec.com

4.2 ANT ConnectorThe main RF connector for the 9602 is the antenna connector, labeled ANT in th e 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-boardconnection to the host system motherboard and should not be directly connected to an external antennacable or cable distribution system. The EN609502 compliance standard outlines that telecommunicationsequipment needs protection from a 2KV spike. The MMCX connectors are not capable of 2KV operationstherefore protection needs to be provided on the developers motherboard and a larger connector needs

to be used. Developers are encourages to review the EN609502 compliance standards for additionaldetails.

4.2.4 Antenna Characteristics

The 9602 should be connected to an Iridium-band antenna with the following antenna connectorcharacteristics as described in Table 11.

Table 11: Antenna Characteristics

Parameter ValueImpedance 50 Ohms nominal

Gain 3dBiPolarization RHCP

VSWR (maximum operational) 1.5 : 1

Note:

Existing qualified Iridium antennas may be used. (i.e. antennas designed for the 9601, 9522, 9522Aand 9522B)

Existing antennas will require different RF connector types to than those for the 9601, 9522, 9522Aand 9522B
http://www.samtec.com/http://www.samtec.com/http://www.samtec.com/


28/67


Revision 6.0



29/67


Revision 6.0


4.3 GPS Connector

The second RF connector, labeled GPS in the board silkscreen, is a pass-through connection from theantenna path and is provided for GPS receivers that wish to share the main antenna. An overview of thiscircuit is provided in Figure 7. The following operational points should be noted when using GPS

receivers connected to this point.

o The GPS pass-through path is activated by detecting the presence of a DC voltage on the center-pin of the GPS connector. The 9602 uses the voltage from the GPS center pin to switch on theRX path and requires minimal current (


30/67


Revision 6.0


4.4 RF 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 ValueAverage Power during a transmit slot (max) 1.6 W

Receiver sensitivity (Typical level at module connector) -117dBmMax Cable loss permitted (Note 1) 2dBLink Margin Downlink (Note 2) 13dB

Link Margin Uplink (Note 2) 7dB

Note 1: Cable losses should be minimized. The total implementation loss for an antenna, connectors,cable, lightening arrestor and any other RF component between the transceiver and the antenna shouldnot exceed 3dB. The total cable loss between the antenna and the modem includes losses in themotherboard. Implementation loss higher than this will affect the Iridium link performance and quality ofservice. Solutions with a loss higher than 3dB will not meet the requirements of Iridium SolutionCertification.

Note 2: Link Margins are given assuming a free-space propagation model.

4.6 S-meter Performance

The numbers 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 particularnote are the following:

1. There is a 0.5 dB tolerance on calibrating the S-meter.2. Each bar represents a 2 dB increment3. 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


31/67


Revision 6.0


5 AT Command Set Description

This document specifies the AT Commands supported by the 9602 Transceiver. Informative examplesare 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 the9601 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 arerelevant to the 9602 are included. AT Commands related to functionality of the 9522 and 9522A LBTs arenot included. Note that Commands may be modified, removed or added and that you should not rely onthis document as a definitive statement of the functionality of the commercial 9602 Transceiver. Thisdocument 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 isphysically loaded on the 9602 used in applications under development. Such release notes are madeavailable to authorized Iridium VARs and VAMs on the Iridium Developer Extranet. It is the responsibilityof Product Developers to check compatibility of applications software with the AT Commands on al l 9602s

used for both development and commercial deployments.

Product Developers should also consult the Iridium Short Burst Data Service Developers Guide inaddition to the Commands stated herein. That guide provides significant additional information that willaide 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/ isnot followed by .

5.3 En Echo

Echo command characters.

0 Characters are not echoed to the DTE.

1 Characters are echoed to the DTE (default).


32/67


Revision 6.0


5.4 In Identification

Requests the 9602 to display information about itself.

0 2400 (for compatibility only)


2 OK (for compatibility only)

3 XXXXXXXX (Software revision level)

4 IRIDIUM 9600 Family (Product description)


6 XXX (Factory identity)

7 XXXXXXXX (Hardware specification)

5.5 Qn Quiet Mode

Control 9602 responses.

0 9602 responses are sent to the DTE (default).

1 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.

0 Numeric responses.

1 Textual responses (default).

5.7 Zn Soft Reset

Reset the 9602s data port to a user-stored configuration that has been previously stored using &Wn.

0 Restores user configuration 0.

1 Restores user configuration 1.

5.8 &Dn DTR Option

Set the 9602 reaction to the DTR signal.

0 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 afterapproximately 10 seconds to enter the UART test mode. The data port will resume whenDTR 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.


33/67


Revision 6.0


0 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 ofSBD message data; it does not apply to AT commands and their responses.

0 Disables flow control.

3 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.

0 Store current (active) configuration as profile 0.

1 Store current (active) configuration as profile 1.

5.13&Yn Designate Default Reset Profile

Select profile for use after power-up.

0 Select profile 0 (default).

1 Select profile 1.

5.14%R Display Registers

Display all the S-registers in the system.

5.15*F Flush to EEPROMFlush 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 losingnon-volatile data.

Note: This command stops the 9602 from responding to any more commands, but does not actuallypower it down. The only way to power down the 9602 is for the FA to remove the power or to de-assertthe on/off control line.

Note: After an SBD session, the new SBD MOMSN is always flushed to EEPROM before the +SBDIresult is issued.


34/67


Revision 6.0


5.16*Rn Radio Activity

Control radio activity.

0 Disable radio activity.

1 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 periodsbetween SBD sessions, and also provides some, limited, power saving in cases where it may beinconvenient for the FA to power down the 9602.

5.17+CCLK Real time clockExec 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.


35/67


Revision 6.0


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 theDTE in case of indicator state changes. controls the processing of the +CIEV unsolicited resultcodes.

:

0 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).

1 Enable indicator event reporting; buffer the most recent +CIEV unsolicited result code foreach indicator when the data port is reserved (e.g. in SBD data mode) and flush them tothe DTE after reservation; otherwise forward them directly to the DTE.

:

Control reporting of "signal quality" indicator changes:

0 No "signal quality" indicator reporting.

1 Enable "signal quality" indicator reporting using result code

+CIEV:0,

where is:

0 Equivalent to 0 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:

0 No "service availability" indicator reporting.

1 Enable "service availability" indicator reporting using result code

+CIEV:1,

where is:

0 Network service is currently unavailable.

1 Network service is available.


36/67


Revision 6.0


Network service availability is equivalent to a signal strength greater than 0. The service availabilityindicator provides a way for the FA to wait until the 9602 can start an SBD session without receivingcontinual 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) ,(supporteds)

Note: In 1, the DTE may miss some indicator state changes if they occur while the data port isreserved. However, the buffering mechanism ensures that the most recentchange for each indicatorduring reservation will be flushed to the DTE after reservation; thus the DTE is always made aware of thelatest state of each indicator.

Note: The DTE may initiate an SBD session even if service is unavailable; in this case, the 9602 makesan immediate search for the network and, if successful, starts the SBD session, otherwise the SBDsession 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):

0 No telephony ring alert received.

and indicates the SBD ring indication status:

0 No SBD Ring Alert received.

1 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 beevaluated.


37/67


Revision 6.0


5.24+CSQ Signal Quality

Exec Command:+CSQ[F]

Execution command returns the received signal strength indication from the 9602. Response is inthe form:

+CSQ:

where:

:

0 Equivalent to 0 numbers displayed on the signal strength indicator.

1 Equivalent to 1 number displayed on the signal strength indicator.





Test Command:+CSQ=?

List the supported signal strength indications. The response is in the form:

+CSQ:(supported s)

Each number represents about 2 dB improvement in link margin over the previous value. Areading of 0 is at or below the minimum receiver sensitivity level. A reading of 1 indicates about2db of link margin. A reading ofr 5 indicates 10 dB or more link margin. These are not calibratedoutput and provies relative information about the units receive signal, and not an absolutereceiver level or even a calibrated signal to noise ratio.

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 inresponse of up to 50 seconds may be experienced.

Note: The +CSQF form of the command returns immediately, reporting the last known calculated signalstrength. Note that the signal strength returned by this command could be different from the current actualsignal strength if the +CSQ form is used. This form is included for Product Developer applicationcompatibility as it provides a Fast response.


38/67


Revision 6.0


5.25+CULK Unlock

Exec Command:+CULK=

Unlock the Transceiver after it has been locked by the Gateway. The unlock key must be obtained bycontacting Iridiums customer support.

:

0000000000000000 .. FFFFFFFFFFFFFFFFA string of 16 hexadecimal digits.

While the Transceiver is locked, it is unable to perform any SBD sessions. Any attempts to start asession 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:

0 Unlocked Transceiver is not locked and is permitted to perform SBD sessions.1 Locked Transceiver is locked and unable to perform SBD sessions. It must be

unlocked by supplying the correct unlock key to the +CULK command.

2 Permanently locked Transceiver is locked and unable to perform SBD sessions. Itcannot 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:

:

0 Unlocked

1 Locked

2 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.


39/67


Revision 6.0


5.29+GSN Serial Number

Exec Command:+CGSN

Query the 9602 IMEI.

5.30+IPR Fixed DTE RateSet Command:+IPR=

Set the data rate at which the 9602 will accept commands. The change in data rate takes into effect afterthe result code (e.g., OK) is received by the DTE.

where:

:

1 600 bps

2 1200 bps

3 2400 bps

4 4800 bps

5 9600 bps

6 19200 bps (default)

7 38400 bps

8 57600 bps

9 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)


40/67


Revision 6.0


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 originatedbuffer 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 theDTE that it is prepared to receive the message by sending the ASCII encoded stringREADY (hex 52 45 41 44 59 0D 0A) to the DTE.

The parameter represents the length, in bytes, of the SBD message notincluding the mandatory two-byte checksum.

The maximum mobile originated SBD message length is specified at 340 bytes. The minimum mobileoriginated 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 fromthe 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. Thehigh order byte must be sent first. For example if the DTE were to send the word hello encodedin 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:

0 SBD message successfully written to the 9602.

1 SBD message write timeout. An insufficient number of bytes were transferred to 9602during the transfer period of 60 seconds.

2 SBD message checksum sent from DTE does not match the checksum calculated by the

9602.

3 SBD message size is not correct. The maximum mobile originated SBD message lengthis 340 bytes. The minimum mobile originated SBD message length is 1 byte.


41/67


Revision 6.0


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 the9602 to the DTE. The mobile terminated buffer can contain only one message at any one time.

The SBD message is transferred formatted as follows:{2-byte message length} + {binary SBD message} + {2-byte checksum}

The {2-byte message length} field represents the length, in bytes, of the SBD message notincluding the length field or the mandatory two-byte checksum. The high order byte will be sentfirst.

The maximum mobile terminated SBD message length is length is specified at 270 bytes (andmay be increased following actual performance testing).

The checksum is the least significant 2-bytes of the summation of the entire SBD message. Thehigh order byte will be sent first. For example if the 9602 were to send the word hello encoded inASCII 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 messagelength 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.


42/67


Revision 6.0


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 ATcommand 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 toreceive the message by sending the string READY (hex 52 45 41 44 59 0D 0A) to theDTE.

Once the DTE receives the READY indication, the text message must be sent, terminated by acarriage return.

The length of the text message entered in this way is limited only by maximum mobile-originated SBDmessage 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:

0 SBD message successfully written to the 9602.

1 SBD message write timeout. An insufficient number of bytes were transferred to 9602during 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.


43/67


Revision 6.0


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 orchecksum. The intent of this command is to provide a human friendly interface to SBD for demonstrationsand 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 theport.

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}


44/67


Revision 6.0


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 useSBD 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 themobile originated buffer it will be transferred to the GSS. Similarly if there is one or more messagesqueued at the GSS the oldest will be transferred to the 9602 and placed into the mobi

Iridium 9602 SBD Transceiver Developer ’s Guide

Documents

Transcript of Iridium 9602 SBD Transceiver Developer ’s Guide