9602N Developers Guide-Revision by Beam

Transcription

1 Used in the Beam 9602N SBD DataModem EXTRACTED and EDITED by BEAM Communications from the 9602N Developers Guide-Revision by Beam Iridium Communications Inc Democracy Blvd., Suite 300 Bethesda, MD USA Toll Free: [US Only] International BEAM Communications Pty Ltd 5/8 Anzed Court, Mulgrave, Victoria, 3170, AUSTRALIA Tel: Fax: Information: info@beamcommunications.com Support: support@beamcommunications.com

2 LEGAL DISCLAIMER AND CONDITIONS OF USE This document contains information for the Iridium 9602N 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. Contents 1 Product Overview 4 2 Physical Specification 6 3 Electrical Interface 7 4 RF Interface 10 5 AT Command Set Description 11 6 S-Register Definitions 36 7 Summary of Result Codes 40 8 Informative Examples 41 9 Supported AT Commands 44 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 2 Distribution of Guide Restricted 3

3 1 Product Overview The Iridium 9602N Short Burst Data Only Transceiver (9602N) used in the Beam SBD DataMODEM 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 9602N only supports Iridium s Short Burst Data (SBD) capability. It does not support voice, circuit switched data, or short message service (SMS). The 9602N 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 9602N 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. Such finished products, when integrated together, require regulatory and safety testing to be conducted by the integrator. The 9602N does not incorporate nor require a Subscriber Identity Module (also known as a SIM Card) to be inserted into the Transceiver. The 9602N is intended to be used as a transceiver module fitted within another host system. The 9602N 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 9602N is described within this document as 9602N, 9602N SBD Transceiver, Transceiver, and ISU. All of these terms refer to the same product. 1.1 Key Features Small form factor 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 1.2 Transceiver Packaging and Regulatory Certification The 9602N 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 9602N is tested to the regulatory and technical certifications shown in Table 1 (See Note below). Regulatory Approvals CE Table 1: Regulatory and Technical Certifications. Radio Tests EMC Tests Electrical/ Mechanical/ Operational Safety Tests ETSI EN V1.1.1 ETSI EN V1.8.1( ) EN :2006 Part 1 ( ) ETSI EN V1.2.1( ) FCC FCC CFR47 parts 2, 15, and 25 Industry Canada Industry Canada RSS170 Issue 1, Rev 1, November 6, 1999 EN : 1995/A2 : 2001 Part 4.2 EN : 2002 Part 4.3 EN : 2004 EN : 1996/A1 : 2001 Part 4.6 EN55022:2006 Note: The initial 9602N FP1 & FP2 prototype units are different from the commercially produced 9602N 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 9602N units conform to the regulatory approved design and the regulatory and technical certifications listed in Table 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 9602N 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 9602N 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. 4 Distribution of Guide Restricted 5

4 2 Physical Specification 2.1 Environmental Environmental Specification The environmental specifications of the 9602N are summarized in Table 2 below. Table 2: Environmental Specifications Parameter Value Operating Temperature Range 1-40ºC to + 85ºC Operating Humidity Range 75% RH Storage Temperature Range -40ºC to + 85ºC Storage Humidity Range 93% RH 3 Electrical Interface 3.1 Serial Data Interface The Serial data interface is used to both command the 9602N and transfer user data to and from the Transceiver. The 9602N 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 9602N 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 9602N and DCE. Autobaud is not supported in 9602N SBD Transceiver. The baud rate can be set via the AT+IPR command. The default rate is bps Wire and 3-Wire Operation By default, the serial interface operates as a 9-wire connection. Table 4 describes each of the signals, where input means an input to the 9602N, and output means an output from the 9602N SBD Transceiver Environmental Tests Performed The 9602N has been tested to the specifications listed in Table 3. Table 3: Environmental Tests Test Name Test Reference Test Description Thermal Shock EN :2000 Change of Temperature, -25 C to +70 C, 5 cycles of 1 hour each Humidity IEC :2002 Damp heat steady state 40OC 93% RH for 4 days Vibration EN : m2/s3 from 5Hz to 20Hz 21Hz to 500Hz dropping -3dB per octave Vibration J1455 Society of Automotive Engineers 10-40Hz at 0.02g2/Hz Hz dropping 6dB per octave Shock EN :1993 (NF c20-727) Shock J1455 Society of Automotive Engineers Drop 1m onto concrete in 3 perpendicular orientations (3 drops) Also 10G shock over a period of 12ms 1 Operating Temperature Range based on a duty-cycled usage model with 9602N sending one SBD message per hour and is otherwise turned off during the hour. Iridium has tested the 9602N 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 9602N. 6 Distribution of Guide Restricted 7 Table 4: Serial Interface Signals Signal Description RX Active high data output [The DTE receives the data from the 9602N] TX Active high data input [Data is transmitted from the DTE to the 9602N] GND 0V RTS Active low flow control input CTS Active low flow control output RTS and CTS are used together to implement hardware flow control when enabled with AT&K3 DTR Active low handshaking input AT&Dn controls how the 9602N 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 9602N will stop responding to AT commands until the data port is returned to DCE mode. DSR Active low handshaking output The 9602N 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 9602N is powered up and ready to receive AT commands. RI Active low ring indicator output The 9602N 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. DCD Active low handshaking output DCD is driven OFF at all times. Note that the Ring Indicator (RI) pin is used by the 9602N 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.

5 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. Due to the small code space and limited processing resources of the 9602N 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 serial interface to prevent a possible latch-up condition Configuration Settings The 9602N 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 9602N power-up through use of the AT&Yn command. The 9602N 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 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 9602N. 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 9602N 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 9602N suspends transfer of data to the DTE; when CTS is OFF (high), the 9602N expects the DTE to suspend transfer of data to the 9602N. When in SBD session mode, the 9602N 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 9602N in response to the SBD AT Commands; the DTE has no other control over the mode. 3.2 Hardware Failure Reporting If the 9602N detects a hardware problem during initialisation, the 9602N may be unable to function correctly. The 9602N notifies the DTE of this situation by issuing an unsolicited result code at the end of initialisation: HARDWARE FAILURE: <subsys>,<error> where <subsys> identifies the software subsystem that detected the error, and <error> is the subsystemspecific error code. Any AT commands that cannot be handled in the failure condition will terminate with result code 4 ( ERROR ). 8 Distribution of Guide Restricted 9

6 4 RF Interface 4.1 RF Interface Specifications The RF interface requirements for the 9602N are summarized in Table 5 below. Table 5: General RF Parameters 5 AT Command Set Description This document specifies the AT Commands supported by the 9602N Transceiver. Informative examples are presented in Section 8. The 9602N 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 9602N, +SBDGW and it returns the default gateway on which the modem is programmed to operate. Parameter Frequency Range Duplexing Method Input/Output Impedance Multiplexing Method 4.2 Radio Characteristics Value 1616 MHz to MHz TDD (Time Domain Duplex) 50Ω TDMA/FDMA The 9602N is configured and operated through the use of AT commands. Only AT Commands that are relevant to the 9602N 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 9602N 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 9602N 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 9602Ns used for both development and commercial deployments. Table 6 contains radio characteristics of the 9602N SBD Transceiver. Table 6: Radio Characteristics Parameter Value Average Power during a transmit slot (max) 1.6W Receiver sensitivity (Typical level at module connector) -117dBm Max Cable loss permitted (Note 1) 2dB Link 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 should not exceed 3dB. The total cable loss between the antenna and the modem includes losses in the motherboard. 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. 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 9602N will respond. 5.2 A/ - Repeat Last Command Repeat the last command issued to the 9602N unless the power was interrupted or the unit is reset. A/ is not followed by <CR>. 5.3 En Echo Echo command characters. 0 Characters are not echoed to the DTE. 1 Characters are echoed to the DTE (default). 4.3 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 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 10 Distribution of Guide Restricted 11

7 5.4 In Identification Requests the 9602N to display information about itself (for compatibility only) (for compatibility only) 2 (for compatibility only) 3 XXXXXXXX (Software revision level) 4 IRIDIUM 9600 Family (Product description) (for compatibility only) 6 XXX (Factory identity) 7 XXXXXXXX (Hardware specification) 5.5 Qn Quiet Mode Control 9602N responses N responses are sent to the DTE (default) N responses are NOT sent to the DTE. 5.6 Vn Verbose Mode Set the response format of the 9602N, which may be either numeric or textual. 0 Numeric responses. 1 Textual responses (default). 5.7 Zn Soft Reset Reset the 9602N s data port to a user-stored configuration that has been previously stored using &Wn. 0 Restores user configuration 0. 1 Restores user configuration &Dn DTR Option Set the 9602N reaction to the DTR signal. 0 DTR is ignored. A DTR signal input is not needed when set to &D 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.10 &Kn Flow Control Select the flow control method between the 9602N and DTE. Flow control is only applied to the transfer of SBD message data; it does not apply to AT commands and their responses. 0 Disables flow control. 3 Enables RTS/CTS flow control (default) &V View Active and Stored Configuration View the current active configuration and stored profiles &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 &Yn Designate Default Reset Profile Select profile for use after power-up. 0 Select profile 0 (default). 1 Select profile %R Display Registers Display all the S-registers in the system *F Flush to EEPROM Flush all pending writes to EEPROM, shut down the radio, and prepare the 9602N to be powered down. The command returns upon completion, at which point it is safe to remove the power without losing non-volatile data. Note: This command stops the 9602N from responding to any more commands, but does not actually power it down. The only way to power down the 9602N 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. 5.9 &Fn Restore Factory Settings Recall factory default configuration without resetting the data port. 0 Recall factory default Distribution of Guide Restricted 13

8 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 9602N 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 9602N CCLK Real time clock Exec Command: +CCLK Query the 9602N for Iridium system time if available CGMI Manufacturer Identification Exec Command: +CGMI Query the 9602N manufacturer CGMM Model Identification Exec Command: +CGMM Query the 9602N model CGMR Revision Exec Command: +CGMR Query the 9602N revision CGSN Serial Number Exec Command: +CGSN Query the 9602N IMEI CIER Indicator Event Reporting Set Command: +CIER=[<mode>[,<sigind>[,<svcind>]]] The set command enables or disables sending of the +CIEV unsolicited result code from the 9602N to the DTE in case of indicator state changes. <mode> controls the processing of the +CIEV unsolicited result codes. <mode>: 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 9602N (default). 1 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. <sigind>: Control reporting of signal quality indicator changes: 0 No signal quality indicator reporting. 1 Enable signal quality indicator reporting using result code +CIEV:0,<rssi> where <rssi> is: 0 Equivalent to 0 bars on the signal strength indicator 1 Equivalent to 1 bars on the signal strength indicator 2 Equivalent to 2 bars on the signal strength indicator 3 Equivalent to 3 bars on the signal strength indicator 4 Equivalent to 4 bars on the signal strength indicator 5 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. <svcind>: Control reporting of service availability indicator changes: 0 No service availability indicator reporting. 1 Enable service availability indicator reporting using result code +CIEV:1,<value> where <value> is: 0 Network service is currently unavailable. 1 Network service is available. 14 Distribution of Guide Restricted 15

9 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 9602N 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:<mode>,<sigind>,<svcind>,<antind> Where <antind> is not used and is included for compatibility only. Test Command: +CIER=? List the supported settings. The response is in the form: +CIER:(supported <mode>s),(supported <sigind>s),(supported <svcind>s),(supported <antind>s) Note: In <mode> 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 9602N makes an immediate search for the network and, if successful, starts the SBD session, otherwise the SBD session fails 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:<tri>,<sri> where <tri> indicates the telephony ring indication status (for compatibility): 0 No telephony ring alert received. and <sri> indicates the SBD ring indication status: 0 No SBD Ring Alert received. 1 SBD Ring Alert received CSQ Signal Quality Exec Command: +CSQ[F] Execution command returns the received signal strength indication <rssi> from the 9602N. Response is in the form: +CSQ:<rssi> where: <rssi>: 0 Equivalent to 0 numbers displayed on the signal strength indicator. 1 Equivalent to 1 number displayed on the signal strength indicator. 2 Equivalent to 2 numbers displayed on the signal strength indicator. 3 Equivalent to 3 numbers displayed on the signal strength indicator. 4 Equivalent to 4 numbers displayed on the signal strength indicator. 5 Equivalent to 5 numbers displayed on the signal strength indicator. Test Command: +CSQ=? List the supported signal strength indications. The response is in the form: +CSQ:(supported <rssi>s) Each number represents about 2 db improvement in link margin over the previous value. A reading of 0 is at or below the minimum receiver sensitivity level. A reading of 1 indicates about 2 db of link margin. A reading of 5 indicates 10 db or more link margin. These are not calibrated output and provides relative information about the units receive signal, and not an absolute receiver 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 9602N 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. Note: The <tri> response is included for compatibility with 9522A applications. The results in the <tri> response should be ignored for 9602N applications. For the 9602N only the <sri> response should be evaluated. 16 Distribution of Guide Restricted 17

10 5.25 +CULK Unlock Exec Command: +CULK=<unlock key> GSN Serial Number Exec Command: +CGSN Query the 9602N IMEI. Unlock the Transceiver after it has been locked by the Gateway. The unlock key must be obtained by contacting Iridium s customer support. <unlock key>: 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. +CULK:<status> where: <status> 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. 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:<status> <status>: 0 Unlocked 1 Locked 2 Permanently locked IPR Fixed DTE Rate Set Command: +IPR=<rate> Set the data rate at which the 9602N will accept commands. The change in data rate takes into effect after the result code (e.g., ) is received by the DTE. where: <rate>: bps bps bps bps bps bps (default) bps bps bps Read Command: +IPR? Query the current data rate. The response is in the form: +IPR:<rate> Test Command: +IPR=? List the supported data rates. The response is in the form: +IPR:(supported <rate> settings) GMI Manufacturer Identification Exec Command: +CGMI Query the 9602N manufacturer GMM Model Identification Exec Command: +CGMM Query the 9602N model GMR Revision Exec Command: +CGMR Query the 9602N revision. 18 Distribution of Guide Restricted 19

11 5.31 +SBDWB Short Burst Data: Write Binary Data to the ISU SBDRB Short Burst Data: Read Binary Data from the Module Exec Command: +SBDWB=<SBD message length> This command is used to transfer a binary SBD message from the DTE to the single mobile originated buffer in the 9602N. 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 9602N will indicate to the DTE that it is prepared to receive the message by sending the ASCII encoded string READY<CR><LF> (hex D 0A) to the DTE. The <SBD message length> 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 <SBD message length> parameter is out of range, the 9602N issues response 3 (see below). Once the DTE receives the READY indication from the 9602N, 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 9602N the binary stream would be hex c 6c 6f The mobile originated buffer will be empty upon power-up. If any data is currently in the mobile originated buffer, it will be overwritten. 0 SBD message successfully written to the 9602N. 1 SBD message write timeout. An insufficient number of bytes were transferred to 9602N during the transfer period of 60 seconds. 2 SBD message checksum sent from DTE does not match the checksum calculated by the 9602N. 3 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. Exec Command: +SBDRB This command is used to transfer a binary SBD message from the single mobile terminated buffer in the 9602N 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 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 c 6c 6f If there is no mobile terminated SBD message waiting to be retrieved from the 9602N, the message length and checksum fields will be zero. The mobile terminated message buffer will be empty upon power-up. There are no response codes generated by the 9602N for this command. 20 Distribution of Guide Restricted 21

12 5.33 +SBDWT Short Burst Data: Write a Text Message to the Module Exec Command: +SBDWT[=<text message>] This command is used to transfer a text SBD message from the DTE to the single mobile originated buffer in the 9602N. The text message may be entered on the command line: For example, AT+SBDWT=hello. The length of <text message> 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 9602N will indicate to the DTE that it is prepared to receive the message by sending the string READY<CR><LF> (hex D 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. For the AT+SBDWT form: 0 SBD message successfully written to the 9602N. 1 SBD message write timeout. An insufficient number of bytes were transferred to 9602N during the transfer period of 60 seconds. For the AT+SBDWT=<text message> form: : SBD message successfully stored in mobile originated buffer. ERROR: An error occurred storing SBD message in mobile originated buffer 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 9602N 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. +SBDRT:<CR> {mobile terminated buffer} 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 9602N 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 9602N and placed into the mobile terminated buffer. The message, if any, in the mobile originated buffer will be sent from the 9602N to the GSS. If there is a MT-SBD message queued at the GSS it will be transferred to the 9602N and placed into the mobile terminated buffer. +SBDI:<MO status>,<momsn>,<mt status>,<mtmsn>,<mt length>,<mt queued> where: <MO status>: MO session status provides an indication of the disposition of the mobile originated transaction. The field can take on the following values: 0 No SBD message to send from the 9602N. 1 SBD message successfully sent from the 9602N to the GSS. 2 An error occurred while attempting to send SBD message from 9602N to GSS. <MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the 9602N when sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is successfully completed between the 9602N to the GSS. This wrap around counter can range from 0 to <MT status>: The MT status provides an indication of the disposition of the mobile terminated transaction. The field can take on the following values: 0 No SBD message to receive from the GSS. 1 SBD message successfully received from the GSS. 2 An error occurred while attempting to perform a mailbox check or receive a message from the GSS. <MTMSN>: The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when sending a message to the 9602N. This value is indeterminate if the field <MT status> is zero. This wrap around counter can range from 0 to Distribution of Guide Restricted 23

13 <MT length>: 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>: MT queued is a count of mobile terminated SBD messages waiting at the GSS to be transferred to the 9602N 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). +SBDDET:<status>,<error> where: <status>: 0 Detach successfully performed 1 An error occurred while attempting the detach <error>: Gateway-reported values 0 No error Reserved, but indicate success if used 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) 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) 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 SBDDSC Short Burst Data: Delivery Short Code Set Command: +SBDDSC=<dsc> 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). <dsc>: 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:<dsc> 24 Distribution of Guide Restricted 25

14 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][=<location>] This command initiates an SBD session between the 9602N 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 9602N and placed into the mobile terminated buffer. The message, if any, in the mobile originated buffer will be sent from the 9602N to the GSS. If there is a MT message queued at the GSS it will be transferred to the 9602N 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. <location> has format: [+ -]DDMM.MMM,[+ -]dddmm.mmm where: DD Degrees latitude (00-89) MM Minutes latitude (00-59) MMM Thousandths of minutes latitude ( ) ddd Degrees longitude ( ) mm Minutes longitude (00-59) mmm Thousandths of minutes longitude ( ) The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example, AT+SBDIX= , corresponds to 52 degrees minutes North, 0 degrees 7.35 minutes West. Note: The <location> feature is a future capability and has not been implemented. +SBDIX:<MO status>,<momsn>,<mt status>,<mtmsn>,<mt length>,<mt queued> where: <MO status>: 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 0 MO message, if any, transferred successfully. 1 MO message, if any, transferred successfully, but the MT message in the queue was too big to be transferred. 2 MO message, if any, transferred successfully, but the requested Location Update was not accepted Reserved, but indicate MO session success if used 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) 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) Reserved, but indicate failure if used. <MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the 9602N when sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is successfully completed between the 9602N to the GSS. This wrap around counter can range from 0 to <MT status>: The MT status provides an indication of the disposition of the mobile terminated transaction. The field can take on the following values: 0 No MT SBD message to receive from the Gateway. 1 MT SBD message successfully received from the Gateway. 2 An error occurred while attempting to perform a mailbox check or receive a message from the Gateway. <MTMSN>: 26 Distribution of Guide Restricted 27

15 The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when forwarding a message to the 9602N. This value is indeterminate if the field <MT status> is zero. This wrap around counter can range from 0 to <MT length>: 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>: MT queued is a count of mobile terminated SBD messages waiting at the GSS to be transferred to the 9602N SBDMTA Short Burst Data: Mobile-Terminated Alert Set Command: +SBDMTA=<mode> Enable or disable the ISU to listen for SBD Ring Alerts. <mode>: 0 Disable SBD Ring Alert indication 1 Enable SBD Ring Alert ring indication (default) When SBD Ring Alert indication is enabled, the 9602N 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:<mode> Test Command: +SBDMTA=? List the supported mode settings. The response is of the form: +SBDMTA:(supported <mode> 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 SBDREG Short Burst Data: Network Registration Exec Command: +SBDREG[=<location>] 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. <location> has format: [+ -]DDMM.MMM,[+ -]dddmm.mmm where: DD Degrees latitude (00-89) MM Minutes latitude (00-59) MMM Thousandths of minutes latitude ( ) ddd Degrees longitude ( ) mm Minutes longitude (00-59) mmm Thousandths of minutes longitude ( ) The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example, AT+SBDIX= , corresponds to 52 degrees minutes North, 0 degrees 7.35 minutes West. Note: The <location> feature is a future capability and has not been implemented. +SBDREG:<status>,<reg err> where: <status> indicates the resulting registration status of the Transceiver: 0 Detached Transceiver is detached as a result of a successful +SBDDET or +SBDI command. 1 Not registered Transceiver is attached but has not provided a good location since it was last detached. 2 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. 3 Registration denied The gateway is denying service to the Transceiver. <reg err>: Gateway-reported values 0 No error. 2 Session completed but the requested Location Update was not accepted 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). 28 Distribution of Guide Restricted 29