Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Revision 6.0
Revision 6.0
Revision History
Revision 1 25 6 Date Sep 11 2009 Oct 20 2009 Mar 29 2010 Comment First revision adapted from 9601 Product Developers Guide v1.25 Updated following feedback from ISLLC Updated following feedback Iridium 9602 Factory Prototype 2(FP-2) build
Revision 6.0
Contents
Revision History ............................................................................................................................................ 3 Contents ...................................................................................................................................................... 4 List of Abbreviations ...................................................................................................................................... 6 1 Product Overview ................................................................................................................................. 7 1.1 Key Features .......................................................................................................................... 7 1.2 Transceiver Packaging and Regulatory Certification ............................................................. 8 1.3 Software Revision .................................................................................................................. 9 2 Physical Specification ......................................................................................................................... 10 2.1 Module Dimensions ............................................................................................................. 10 2.2 Mechanical Dimensions Motherboard Mounting............................................................... 12 2.3 Environmental ...................................................................................................................... 15 2.3.4 Environmental Specification................................................................................................. 15 2.3.5 Environmental Tests Performed .......................................................................................... 15 2.4 Physical Interface Connectors ............................................................................................. 15 3 Electrical Interfaces ............................................................................................................................ 17 3.1 User Connector .................................................................................................................... 17 3.1.4 User Connector Type ........................................................................................................... 17 3.1.5 User Connector Pin Allocation ............................................................................................. 18 3.2 DC Power Interface .............................................................................................................. 20 3.2.4 Power On/Off Control ........................................................................................................... 21 3.2.5 Typical Power Usage Profile ................................................................................................ 21 3.3 Serial Data Interface ............................................................................................................ 23 3.3.4 9-Wire and 3-Wire Operation ............................................................................................... 23 3.3.5 Configuration Settings .......................................................................................................... 24 3.3.6 Modes of Operation ............................................................................................................. 25 3.3.7 Serial port signal levels ........................................................................................................ 25 3.4 Hardware Failure Reporting ................................................................................................. 25 3.5 Network Available Output .................................................................................................... 26 3.6 DC Supply Indicator Output ................................................................................................. 26 4 RF Interface ........................................................................................................................................ 27 4.1 RF Connector Types ............................................................................................................ 27 4.2 ANT Connector .................................................................................................................... 27 4.2.4 Antenna Characteristics ....................................................................................................... 27 4.3 GPS Connector .................................................................................................................... 29 4.4 R F Inte r f ac e S p ec if ic a ti o ns ........................................................................................ 30 4.5 Radio C h ar ac t er is t ic s ..................................................................................................... 30 4.6 S-meter Performance ........................................................................................................... 30 5 AT Command Set Description ............................................................................................................ 31 5.1 AT ATtention Code ........................................................................................................... 31 5.2 A/ - Repeat Last Command ................................................................................................. 31 5.3 En Echo............................................................................................................................. 31 5.4 In Identification .................................................................................................................. 32 5.5 Qn Quiet Mode .................................................................................................................. 32 5.6 Vn Verbose Mode ............................................................................................................. 32 5.7 Zn Soft Reset .................................................................................................................... 32 5.8 &Dn DTR Option ............................................................................................................... 32 5.9 &Fn Restore Factory Settings ........................................................................................... 32 5.10 &Kn Flow Control .............................................................................................................. 33 5.11 &V View Active and Stored Configuration ........................................................................ 33 5.12 &Wn Store Active Configuration ....................................................................................... 33 5.13 &Yn Designate Default Reset Profile ................................................................................ 33
Revision 6.0 5.14 %R Display Registers ....................................................................................................... 33 5.15 *F Flush to EEPROM ........................................................................................................ 33 5.16 *Rn Radio Activity ............................................................................................................. 34 5.17 +CCLK Real time clock ..................................................................................................... 34 5.18 +CGMI Manufacturer Identification ................................................................................... 34 5.19 +CGMM Model Identification ............................................................................................ 34 5.20 +CGMR Revision .............................................................................................................. 34 5.21 +CGSN Serial Number...................................................................................................... 34 5.22 +CIER Indicator Event Reporting ...................................................................................... 35 5.23 +CRIS Ring Indication Status ........................................................................................... 36 5.24 +CSQ Signal Quality ......................................................................................................... 37 5.25 +CULK Unlock .................................................................................................................. 38 5.26 +GMI Manufacturer Identification ...................................................................................... 38 5.27 +GMM Model Identification ............................................................................................... 38 5.28 +GMR Revision ................................................................................................................. 38 5.29 +GSN Serial Number ........................................................................................................ 39 5.30 +IPR Fixed DTE Rate ....................................................................................................... 39 5.31 +SBDWB Short Burst Data: Write Binary Data to the ISU ................................................ 40 5.32 +SBDRB Short Burst Data: Read Binary Data from the Module ...................................... 41 5.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 ............................... 43 5.35 +SBDI Short Burst Data: Initiate an SBD Session ............................................................ 44 5.36 +SBDDET Short Burst Data: Detach ................................................................................ 45 5.37 +SBDDSC Short Burst Data: Delivery Short Code ........................................................... 46 5.38 +SBDIX Short Burst Data: Initiate an SBD Session Extended ......................................... 47 5.39 +SBDMTA Short Burst Data: Mobile-Terminated Alert..................................................... 49 5.40 +SBDREG Short Burst Data: Network Registration ......................................................... 49 5.41 +SBDAREG Short Burst Data: Automatic Registration .................................................... 52 5.42 +SBDD Short Burst Data: Clear SBD Message Buffer(s)................................................. 53 5.43 +SBDC Short Burst Data: Clear SBD MOMSN ................................................................ 54 5.44 +SBDS Short Burst Data: Status ...................................................................................... 54 5.45 +SBDSX - Short Burst Data: Status Extended .................................................................... 55 5.46 +SBDTC Short Burst Data: Transfer MO Buffer to MT Buffer .......................................... 56 5.47 +SBDGW Short Burst Data: Gateway .............................................................................. 56 5.48 -MSSTM Request System Time ....................................................................................... 56 S-Register Definitions ......................................................................................................................... 58 6.1 S-Register Commands ......................................................................................................... 58 6.1.4 Sr Direct S-Register Reference ........................................................................................ 58 6.1.5 Sr? Direct S-Register Read .............................................................................................. 58 6.1.6 Sr=n Direct S-Register Write ............................................................................................ 58 6.1.7 ? Referenced S-Register Read ......................................................................................... 58 6.1.8 =n Referenced S-Register Write ....................................................................................... 58 6.2 S-Registers .......................................................................................................................... 59 Summary of Result Codes ................................................................................................................. 62 Informative Examples ......................................................................................................................... 63 8.1 Setting the Default Configuration ......................................................................................... 63 8.2 Power-on to Sending a Message ......................................................................................... 63 8.3 Automatic Notification Registration ...................................................................................... 64 8.4 Automatic Notification Message Reception ......................................................................... 64 8.5 Automatic Notification Automatic Registration ..................................................................... 65 8.6 Sending a Message with Minimal Radio Activity ................................................................. 65 8.7 Powering Down .................................................................................................................... 65 Supported AT Commands .................................................................................................................. 66
7 8
Revision 6.0
List of Abbreviations
Abbreviation CE CTS DC DCD DCE DSR DTE DTR ESS ETC FA FCC GND GSS IC IMEI LBT MO MOMSN MT MTMSN RHCP RI RTS SBD SMS TBA UART VAM VAR VSWR Description Conformit Europene (V.24 signal) Clear To Send. This signal is used to control the flow of data to the Iridium9602 Direct Current (V.24 signal) Data Carrier Detect Data Communications Equipment. In this Product, DCE refers to the Iridium 9602 (V.24 signal) Data Set Ready. This signal, from the Iridium 9602, indicates readiness to accept communication over the data port Data Terminal Equipment. In this Product, DTE refers to the FA (V.24 signal) Data Terminal Ready. This signal, from the FA, requests the Iridium 9602 to accept communication over the data port ETC SBD Subsystem (synonymous with GSS) Earth Terminal Controller Field Application; the application controlling the Iridium 9602 Federal Communications Commission Ground Gateway SBD Subsystem (synonymous with ESS) Industry Canada International Mobile Equipment Identity L-Band Transceiver Mobile Originated Mobile Originated Message Sequence Number Mobile Terminated Mobile Terminated Message Sequence Number Right Hand Circular Polarization (V.24 signal) Ring Indicate. This signal, from the Iridium 9602, indicates that an MT message is present at the GSS (V.24 signal) Request To Send. This signal is used to control the flow of data from the Iridium 9602. Short Burst Data Short Message Service To Be Advised Universal Asynchronous Receiver Transmitter Value Added Manufacturer Value Added Reseller Voltage Standing Wave Ratio
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 a specific application or vertical market. Examples of these solutions include tracking a maritime vessel or automatic vehicle location. The 9602 only supports Iridiums Short Burst Data (SBD) capability. It does not support voice, circuit switched data, or short message service (SMS).
The 9602 is designed to meet the regulatory requirements for approval for FCC, Canada, and CE assuming an antenna with a gain of ~3 dBi and adequate shielding. This allows the 9602 to be integrated into a variety of wireless data applications or retrofitted into existing SBD only applications that utilize SBD with the current Iridium 9601, 9522A, 9522B or 9522 L-Band transceiver-based products. (Note that additional development work will be required). Such finished products, when integrated together, require regulatory and safety testing to be conducted by the integrator. The 9602 is a single board transceiver provided as a black box transceiver module with all device interfaces provided by a single multi-pin interface connector in addition to the antenna connector. The Product only provides the core transceiver. All other end user Field Application functions such as GPS, microprocessor based logic control, digital and analog inputs, digital and analog outputs, power supply and antenna must be provided by the solution developer. The device interface across the user connector consists of a serial-data interface, DC power input, network available output and a power on/off control line. The 9602 does not incorporate nor require a Subscriber Identity Module (also known as a SIM Card) to be inserted into the Transceiver. The 9602 is intended to be used as a transceiver module fitted within another host system. The 9602 module is designed to comply with the standards for Radio Emissions Compliance, Electromagnetic Compatibility, and AC Safety in the United States, European Union and Canada, for host systems that provide safe connections to power supply and external antenna or cable distribution system. The 9602 is described within this document as 9602, 9602 SBD Transceiver, Transceiver, and ISU. All of these terms refer to the same product.
Revision 6.0
Regulatory Approvals
Radio Tests
EMC Tests
CE
FCC
EN61000-4-2 : 1995/A2 : 2001 Part 4.2 EN61000-4-3 : 2002 Part 4.3 EN61000-4-4 : 2004 EN61000-4-6 : 1996/A1 : 2001 Part 4.6 EN55022:2006
Industry Canada
Note: The initial 9602 FP1 & FP2 prototype units are different from the commercially produced 9602 SBD Transceivers from a regulatory and certification perspective. Those initial units cannot and should not be used for any commercial purpose or for any regulatory certification or compliance purposes. Only the commercial 9602 units conform to the regulatory approved design and the regulatory and technical certifications listed in Table 1.
Revision 6.0
Revision 6.0
2 Physical Specification
For illustrative purposes a picture of the Iridium 9602 SBD Transceiver Module is shown in Figure 1.
Additionally host system Product Developers should plan space for connection to the host system motherboard, including robust and electrically grounded connections to the antenna/cable distribution system.
10
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 its connectors with respect to its mounting holes. Note: Iridium is currently working on providing updated Figure 2, to reflect the diameter of the mounting holes and tolerance drawings for the cut out. At the time of this documentation release these items were not available and will be provided in a later release.
11
Revision 6.0
Figure 3 General assembly of the 9602 onto motherboard of the host system.
12
Revision 6.0 Figure 4 Example host system motherboard footprint showing mounting position of 9602 (Not to scale. Dimensions in millimeters)
13
Revision 6.0
1. This example of a host system motherboard footprint is shown for illustrative purposes only. The host system may require a different PCB layout or mechanical arrangement. 2. The 9602 is designed to be incorporated within a host system. As such, the antenna or cable distribution system that feeds the host system should be terminated in a robust RF connector that is suitable for the end-application. 3. Safety isolation requirements for external antennas or cable distribution systems should also be taken into consideration when designing the motherboard. A suitably safe design for the RF connections should be incorporated into the host system motherboard, ideally using a chassis-bonded ground connection to the antenna cable shield. 4. The surface below the modem should be a conductive ground plane such that the modem bonds to the motherboard ground system thus reducing the possibility of radiated emissions. This also requires that the mounting screws get properly tightened to 7 pound-inches of torque. 5. The modem is to be installed in a service access only area not accessible by untrained personnel.
Warning- Although the modem dissipates very little power, its use in ambient temperatures in excess of 60 deg C will make the caseworks considerably hot.
14
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 1 Operating Temperature Range Operating Humidity Range Storage Temperature Range Storage Humidity Range Value -40C to + 85C 75% RH -40C to + 85C 93% RH
Operating 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.
15
16
Revision 6.0
3 Electrical Interfaces
The following subsections contain information for the electrical interfaces of the 9602 SBD Transceiver for the non-RF connections. The RF interfaces are covered in section 4.
17
Revision 6.0
Signal Name EXT_PWR EXT_PWR EXT_GND EXT_GND ON/OFF DF_S_TX DF_S_RX SIG_GND DF_ DCD DF_ DSR DF_ CTS DF_RI DF_ RTS DF_ DTR SIG_GND Reserved Reserved SIG_GND NETWORK AVAILABLE SUPPLY_OUT
Signal function Supply Supply Supply return Supply return On/Off control input Data port, serial data input Data port, serial data output Signal ground Data port, Data Carrier Detect Data port, Data Set Ready Data port, Clear-to-Send Data port, Ring Indicator Data port, Request-to-Send Data port, Data Terminal Ready Signal ground
Signal level +5 V +/- 0.5 V +5 V +/- 0.5 V 0V 0V Analog On: >=2.0V Off: <=0.5V 3.3V Digital 3.3V Digital 0V 3.3V Digital 3.3V Digital 3.3V Digital 3.3V Digital 3.3V Digital 3.3V Digital 0V
Signal ground Signals when the 9602 can see an available satellite network Supply power indicator output
0V 3.3V Digital Available = high Not available= low +3.3 V 5mA maximum
Table 8: Limits for 3.3V Digital Signals Parameter Input High Voltage Input Low Voltage Output High Voltage Output Low Voltage Low Level Output Current High Level Output Current Symbol VIH VIL VOH VOL IOL IOH Min 2.0 -0.3 2.4 Typ Max 5.5 0.8 0.4 4.4 5.5 Unit V V V V mA mA
18
Revision 6.0
Figure 5 provides a reference for the pin designation. This view is not to scale and not representative of the connector mechanical layout. This view is for illustrative purposes only. This view designation is when 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 is indicated on the board silkscreen.
ANT
GPS
19
USER
20
Revision 6.0
* Note: The average power consumption will vary depending on the view of the satellite constellation from the antenna. The external power supply needs to guarantee the following: The supply voltage droop over for a 8.3ms burst of 1.5A current should not be more than 0.2 Volts. 2 The power supply should limit the in-rush current to 4 Amps maximum The power source shall provide for over current protection in case of device malfunction. The supply noise should be less than the limits in the following profile: 100 mVpp from 0 to 50 kHz 5 mVpp at 1 MHz measured in 50 kHz bandwidth 10 mVpp at 1 MHz measured in 1MHz bandwidth 5 mVpp above 5 MHz measured in 1 MHz bandwidth.
In rush limit refers to the impedance of the modem when it is unpowered is very low. When power is supplied from an unlimited supply the instantaneous current can exceed 4 Amps If the current exceeds this value damage can occur. This can be limited in several ways, included using a supply that cannot provide more than 4 Amps instantaneously; or providing some series inductance/resistance to the supply lead.
20
Revision 6.0
21
Revision 6.0
1.6 1.5 1.4 1.3 1.2 1.1
1.0 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 -10 0 10 20 30 40 50 60 70
Time (mS)
22
Revision 6.0
DTR
DSR
RI
DCD
Note that the Ring Indicator (RI) pin is used by the 9602 SBD Transceiver to indicate that a Mobile Terminated SBD (MT-SBD) message is queued at the Gateway. The Field Application can monitor this pin and use appropriate AT Commands to command the Transceiver to retrieve the MT-SBD message.
23
Revision 6.0 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 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 serial interface to prevent a possible latch-up condition.
24
Revision 6.0
25
Revision 6.0
26
Revision 6.0
4 RF Interface
This section describes the physical characteristics of the RF connectors and specifications of the RF Interface.
Table 11: Antenna Characteristics Parameter Impedance Gain Polarization VSWR (maximum operational) Value 50 Ohms nominal 3dBi RHCP 1.5 : 1
Note: Existing qualified Iridium antennas may be used. (i.e. antennas designed for the 9601, 9522, 9522A and 9522B) Existing antennas will require different RF connector types to than those for the 9601, 9522, 9522A and 9522B
27
Revision 6.0
28
Revision 6.0
o o o o o o
Figure 7: Equivalent circuit for GPS connection when GPS path is active and 9602 is not transmitting
29
Revision 6.0
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.
30
Revision 6.0
5.3 En Echo
Echo command characters.
0 1
Characters are not echoed to the DTE. Characters are echoed to the DTE (default).
31
Revision 6.0
5.4 In Identification
Requests the 9602 to display information about itself.
0 1 2 3 4 5 6 7
2400 (for compatibility only) 0000 (for compatibility only) OK (for compatibility only) XXXXXXXX (Software revision level) IRIDIUM 9600 Family (Product description) 8816 (for compatibility only) XXX (Factory identity) XXXXXXXX (Hardware specification)
0 1
&Wn.
0 1
32
33
Revision 6.0
While the radio is disabled: SBD sessions can not be initiated; they will fail immediately. No SBD Automatic Notifications will be issued for automatic-MT messages. No registration, i.e. location updates will be performed. The baseband circuitry is still active and the 9602 still accepts AT commands. This command allows the FA to reduce detectable emissions from the RF circuitry during the idle periods between SBD sessions, and also provides some, limited, power saving in cases where it may be inconvenient for the FA to power down the 9602.
34
Revision 6.0
<sigind>: Control reporting of "signal quality" indicator changes: 0 1 No "signal quality" indicator reporting. Enable "signal quality" indicator reporting using result code +CIEV:0,<rssi> where <rssi> is: 0 1 2 3 4 5 Equivalent to 0 bars on the signal strength indicator Equivalent to 1 bars on the signal strength indicator Equivalent to 2 bars on the signal strength indicator Equivalent to 3 bars on the signal strength indicator Equivalent to 4 bars on the signal strength indicator Equivalent to 5 bars on the signal strength indicator
The reported signal strength is the same value that would be returned by the +CSQ command. When enabled, the signal quality indicator is reported only when the signal strength changes.
<svcind>: Control reporting of "service availability" indicator changes: 0 1 No "service availability" indicator reporting. Enable "service availability" indicator reporting using result code +CIEV:1,<value> where <value> is: 0 1 Network service is currently unavailable. Network service is available.
35
Revision 6.0 Network service availability is equivalent to a signal strength greater than 0. The service availability indicator provides a way for the FA to wait until the 9602 can start an SBD session without receiving continual notifications of changes in signal strength.
Read Command: +CIER? Query the current indicator event reporting settings. The response is of the form: +CIER:<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 9602 makes an immediate search for the network and, if successful, starts the SBD session, otherwise the SBD session fails.
and <sri> indicates the SBD ring indication status: 0 1 No SBD Ring Alert received. SBD Ring Alert received.
Note: The <tri> response is included for compatibility with 9522A applications. The results in the <tri> response should be ignored for 9602 applications. For the 9602 only the <sri> response should be evaluated.
36
Revision 6.0
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 about2 db of link margin. A reading ofr 5 indicates 10 dB or more link margin. These are not calibrated output and provies 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 9602 is in the process of acquiring the system, a delay in response of up to 50 seconds may be experienced.
Note: The +CSQF form of the command returns immediately, reporting the last known calculated signal strength. Note that the signal strength returned by this command could be different from the current actual signal strength if the +CSQ form is used. This form is included for Product Developer application compatibility as it provides a Fast response.
37
Revision 6.0
Read Command: +CULK? Query the current lock status of the Transceiver. The response is of the form: +CULK:<status> <status>: 0 1 2 Unlocked Locked Permanently locked
38
Revision 6.0
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)
39
Revision 6.0
5.31 +SBDWB Short Burst Data: Write Binary Data to the ISU
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 9602. The mobile originated buffer can contain only one message at any one time. Once the command is entered, and the message length is acceptable, the 9602 will indicate to the DTE that it is prepared to receive the message by sending the ASCII encoded string READY<CR><LF> (hex 52 45 41 44 59 0D 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 9602 issues response 3 (see below). Once the DTE receives the READY indication from the 9602, the SBD message must be sent from the DTE formatted as follows: {binary SBD message} + {2-byte checksum} The checksum is the least significant 2-bytes of the summation of the entire SBD message. The high order byte must be sent first. For example if the DTE were to send the word hello encoded in ASCII to the 9602 the binary stream would be hex 68 65 6c 6c 6f 02 14. The mobile originated buffer will be empty upon power-up. If any data is currently in the mobile originated buffer, it will be overwritten. Command Response: 0 1 2 3 SBD message successfully written to the 9602. SBD message write timeout. An insufficient number of bytes were transferred to 9602 during the transfer period of 60 seconds. SBD message checksum sent from DTE does not match the checksum calculated by the 9602. SBD message size is not correct. The maximum mobile originated SBD message length is 340 bytes. The minimum mobile originated SBD message length is 1 byte.
40
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 the 9602 to the DTE. The mobile terminated buffer can contain only one message at any one time. The SBD message is transferred formatted {2-byte message length} + {binary SBD message} + {2-byte checksum} as follows:
The {2-byte message length} field represents the length, in bytes, of the SBD message not including the length field or the mandatory two-byte checksum. The high order byte will be sent first. The maximum mobile terminated SBD message length is length is specified at 270 bytes (and may be increased following actual performance testing). The checksum is the least significant 2-bytes of the summation of the entire SBD message. The high order byte will be sent first. For example if the 9602 were to send the word hello encoded in ASCII to the DTE the binary stream would be hex 00 05 68 65 6c 6c 6f 02 14. If there is no mobile terminated SBD message waiting to be retrieved from the 9602, the message length and checksum fields will be zero. The mobile terminated message buffer will be empty upon power-up. Command Response: There are no response codes generated by the 9602 for this command.
41
Revision 6.0
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 9602. 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 9602 will indicate to the DTE that it is prepared to receive the message by sending the string READY<CR><LF> (hex 52 45 41 44 59 0D 0A) to the DTE. Once the DTE receives the READY indication, the text message must be sent, terminated by a carriage return. The length of the text message entered in this way is limited only by maximum mobile-originated SBD message length of 340 bytes. The mobile originated buffer will be empty upon power-up. If any data is currently in the mobile originated buffer, it will be overwritten. Command Response: For the AT+SBDWT form: 0 1 SBD message successfully written to the 9602. SBD message write timeout. An insufficient number of bytes were transferred to 9602 during the transfer period of 60 seconds.
For the AT+SBDWT=<text message> form: OK: SBD message successfully stored in mobile originated buffer.
42
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 or checksum. The intent of this command is to provide a human friendly interface to SBD for demonstrations and application development. It is expected that most usage of SBD will be with binary messages. Once the command is entered, the SBD message in the mobile terminated buffer is sent out of the port. This command is similar to +SBDRB except no length or checksum will be provided. The maximum mobile terminated SBD message length is 270 bytes. The mobile terminated message buffer will be empty upon power-up. Command Response: +SBDRT:<CR> {mobile terminated buffer}
43
Revision 6.0
44
Revision 6.0 <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 9602.
Transceiver-reported values 16 17 18 Transceiver has been locked and may not make SBD calls (see +CULK command). Gateway not responding (local session timeout). Connection lost (RF drop).
19..31 Reserved, but indicate failure if used. 32 33 34 35 36.. No network service, unable to initiate call. Antenna fault, unable to initiate call. Radio is disabled, unable to initiate call (see *Rn command). 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.
45
Revision 6.0
Read Command: +SBDDSC? Query the current Delivery Short Code. The response is of the form: +SBDDSC:<dsc>
46
Revision 6.0
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example, AT+SBDIX=5212.483,-00007.350 corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
Note: The <location> feature is a future capability and has not been implemented. Command Response: +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:
47
Revision 6.0 Gateway-reported values 0 1 2 3..4 5..8 10 11 12 13 14 15 MO message, if any, transferred successfully. MO message, if any, transferred successfully, but the MT message in the queue was too big to be transferred. MO message, if any, transferred successfully, but the requested Location Update was not accepted. Reserved, but indicate MO session success if used. Reserved, but indicate MO session failure if used. Gateway reported that the call did not complete in the allowed time. MO message queue at the Gateway is full. MO message has too many segments. Gateway reported that the session did not complete. Invalid segment size. Access is denied.
Transceiver-reported values 16 17 18 Transceiver has been locked and may not make SBD calls (see +CULK command). Gateway not responding (local session timeout). Connection lost (RF drop).
19..31 Reserved, but indicate MO session failure if used. 32 33 34 35 36.. No network service, unable to initiate call. Antenna fault, unable to initiate call. Radio is disabled, unable to initiate call (see *Rn command). 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 9602 when sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is successfully completed between the 9602 to the GSS. This wrap around counter can range from 0 to 65535. <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 1 2 <MTMSN>: No MT SBD message to receive from the Gateway. MT SBD message successfully received from the Gateway. An error occurred while attempting to perform a mailbox check or receive a message from the Gateway.
48
Revision 6.0 The Mobile Terminated Message Sequence Number (MTMSN) is assigned by the GSS when forwarding a message to the 9602. This value is indeterminate if the field <MT status> is zero. This wrap around counter can range from 0 to 65535. <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 9602.
When SBD Ring Alert indication is enabled, the 9602 asserts the RI line and issues the unsolicited result code SBDRING when an SBD Ring Alert is received. Read Command: +SBDMTA? Query the current ring indication mode. The response is of the form: +SBDMTA:<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.
49
Revision 6.0 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 MM MMM ddd mm mmm Degrees latitude (00-89) Minutes latitude (00-59) Thousandths of minutes latitude (000-999) Degrees longitude (000-179) Minutes longitude (00-59) Thousandths of minutes longitude (000-999)
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example, AT+SBDIX=5212.483,-00007.350 corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
Note: The <location> feature is a future capability and has not been implemented.
Command Response: +SBDREG:<status>,<reg err> where: <status> indicates the resulting registration status of the Transceiver: 0 1 2 3 <reg err>: Gateway-reported values 0 2 3..14 15 No error. Session completed but the requested Location Update was not accepted. Reserved, but indicate Location Update failure if used. Access is denied. Detached Transceiver is detached as a result of a successful +SBDDET or +SBDI command. Not registered Transceiver is attached but has not provided a good location since it was last detached. Registered Transceiver is attached with a good location. Note that this may be the case even when the most recent attempt did not provide a good location. Registration denied The gateway is denying service to the Transceiver.
Transceiver-reported values 16 17 Transceiver has been locked and may not make SBD calls (see +CULK command). Gateway not responding (local session timeout).
50
19..31 Reserved, but indicate failure if used. 32 33 34 35 36 37.. No network service, unable to initiate call. Antenna fault, unable to initiate call. Radio is disabled, unable to initiate call (see *Rn command). Transceiver is busy, unable to initiate call (typically performing auto-registration). Try later, must wait 3 minutes since last registration. Reserved, but indicate failure if used.
Read Command: +SBDREG? Query the current SBD registration status of the Transceiver. The response is of the form: +SBDREG:<status> <status>: 0 1 2 3 4 Detached Not registered Registered Registration denied Unknown
The SBD Network Registration status is stored in Transceiver non-volatile memory, and can therefore be queried by the FA after powering up. Note that if the Transceiver is powered off and then moved any significant distance (> 150Kilometers) that the location information will be incorrect when the Transceiver is subsequently powered on. It is recommended that Product Developers initiate a SBD Network Registration following power on if the application is using Mobile Terminated Messages in conjunction with SBD Ring Alerts. Note: There are a number of required steps in both the ISU and the GSS in order to successfully enable SBD Automatic Notifications. Consult the SBD Developers Guide section on Automatic Notifications for Mobile Terminated Messages.
51
Revision 6.0
When Automatic SBD Network Registration is enabled, mode 1 or 2, the Transceiver monitors its current location and triggers an Automatic SBD Network Registration when it determines that the Transceiver has moved sufficiently far away from its last registered location. Note that Automatic SBD Network Registration runs only while the Transceiver is attached to the gateway, i.e. the registration status is Not registered or Registered. A registration status is Not registered when the modem has not yet attempted communications with the gateway. The registration status is Registered when (1) the device has been provisioned and (2) is ready to communicate and (3) if the Ring Alert has been configured then the application will get notification of messages waiting for subscriber terminated delivery. If a registration is denied the device is prohibited from communications on the network (most likely a provisioning issue.) If in a detached state the unit will not receive ring alerts. This may be due to unknown location at the gateway or because the unit has been reconfigured to not receive alerts. Automatic SBD Network Registration may only be used with system-provided location. If the FA is providing its own location (e.g. GPS) and the FA should use the manual SBD Network Registration command, +SBDREG. Upon triggering in mode 1, Automatic, the Transceiver autonomously initiates an SBD session in order to perform a SBD Network Registration with the updated location of the Transceiver, with the session type set to 3 auto-registration. This session does not transfer any MO or MT messages. Upon triggering in mode 2, Ask, the Transceiver reports to the FA that it should register with the system because the Transceiver location has changed (see <event> below); it is then the responsibility of the FA to register via +SBDREG or +SBDIX. +SBDIX allows the FA to register while including an MO message and/or retrieving an MT message that is pending at the Gateway. When auto-registration is enabled, mode 1 or 2, the Transceiver reports relevant events to the FA by issuing an unsolicited result code +AREG:<event>,<reg error>. <event>: 0 1 2 <reg error>: Gateway-reported values 0 2 3..14 15 No error. Session completed but the requested Location Update was not accepted. Reserved, but indicate Location Update failure if used. Access is denied. Suggest FA makes a registration attempt (mode 2 only) Auto-registration has been performed successfully (mode 1 only) Auto-registration has failed and will be retried after a delay (mode 1 only)
52
Revision 6.0 Transceiver-reported values 16 17 18 Transceiver has been locked and may not make SBD calls (see +CULK command). Gateway not responding (local session timeout). Connection lost (RF drop).
19..31 Reserved, but indicate failure if used. 32 33 34 35 36 37.. No network service, unable to initiate call. Antenna fault, unable to initiate call. Radio is disabled, unable to initiate call (see *Rn command). Transceiver is busy, unable to initiate call (typically performing auto-registration). Try later, must wait 3 minutes since last registration. Reserved, but indicate failure if used.
Read Command: +SBDAREG? Query the current automatic MT registration mode. The response is of the form: +SBDAREG:<mode> Test Command: +SBDAREG=? List the supported mode settings. The response is of the form: +SBDAREG:(supported <mode> settings) 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.
Using this command or power cycling the 9602 are the only means by which both buffers are cleared. The mobile terminated buffer will be cleared when an SBD session is initiated. Sending a message from the 9602 to the ESS does not clear the mobile originated buffer. Reading a message from the 9602 does not clear the mobile terminated buffer. Command Response: 0 1 Buffer(s) cleared successfully. An error occurred while clearing the buffer(s).
53
Revision 6.0
54
Revision 6.0
<MOMSN>: The MOMSN identifies the sequence number that will be used during the next mobile originated SBD session.
<MT Flag>: The MT flag indicates the existence of a message in the mobile terminated buffer. The response from the ISU is one of the following numeric codes: 0 1 No message in mobile terminated buffer. Message in mobile terminated buffer.
<MTMSN>: The MTMSN identifies the sequence number that was used in the most recent mobile terminated SBD session. This value will be 1 if there is nothing in the mobile terminated buffer.
<RA flag>: The RA flag indicates whether an SBD Ring Alert has been received and still needs to be answered. 0 1 No SBD ring alert. SBD ring alert has been received and needs to be answered.
Note: The RA flag is set whenever the ISU receives an SBD Ring Alert; this happens even if the +SBDMTA setting specifies that SBD ring indications are disabled. The RA flag is cleared only on successful completion of an SBD mailbox check, i.e. an SBD session invoked with +SBDI[X[A]] in which the returned MT status indicates that no error occurred. The value of the RA flag is stored in non-volatile memory so it is preserved across power cycling of the ISU. <msg waiting>:
55
Revision 6.0 The message waiting flag indicates how many SBD Mobile Terminated messages are currently queued at the gateway awaiting collection by the ISU. This flag is updated after every SBD session, including +SBDI, +SBDIX, +SBDIXA, and +SBDREG.
Iridium system time epoch: Mar 8, 2007, 03:50:35 (GMT): Iridium system time source: The system time is available and valid only after the 9602 has found the network and has received the Iridium system time from the network. Once the time is received, the 9602 uses its internal clock to increment the counter. In addition, at least every 8 hours, or on location update or other event that requires re-registration, the 9602 will obtain a new system time from the network. Time localization: None. The system time value is always expressed in GMT time.
56
Revision 6.0 Resolution and accuracy: The resolution of the system time is one Iridium frame tick, or 90 ms. Accuracy as measured by the difference between the time reported and the actual time it is sent out the 9602 serial port should not exceed 4 frame ticks (.36 seconds) and in most cases will be one frame tick (.09 seconds) or less.
57
Revision 6.0
6 S-Register Definitions
S-registers allow control over specific 9602 operations. Some S-registers contain a single numeric value, other S-registers are bit-mapped where individual bits, or set of bits, control specific functions. Table 6-1 defines the S-registers used for 9602 Transceiver. Some legacy S-registers from the 9522A are obsolete for 9602 Transceiver, and 9602 Transceiver requires some new S-registers. To prevent reallocation of obsolete S-registers, they are reserved and shaded out in the table, and the new Sregisters are registers that are unused in 9522A Transceiver and are marked as new for 9602 Transceiver. All S-registers, from S0 to S127, are readable. All write permissions remain unchanged from 9522A Transceiver, even where a writable register is not used in 9602 Transceiver. Writable registers are highlighted in the Sr=n writable? column. An FA could use the unused writable S-registers to store application-specific data. The final column in the table indicates which S-registers are stored in non-volatile memory as part of a user profile; the 9602 can be reset to a stored profile using the Zn command.
58
Revision 6.0
6.2 S-Registers
Table 6-1: 9602 Transceiver S-Registers [Note: To prevent reallocation of obsolete S-registers, they are reserved and shaded out in the table, and the new S-registers are registers that are unused in 9522A Transceiver and are marked as new for 9602 Transceiver.]
Description
Not applicable to 9602 Not applicable to 9602 Not applicable to 9602Escape code character Carriage return character Line feed character Backspace character Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Bitmap register: bits 0-1: DCE data bits bits 2-3: DCE stop bits bits 4-6: DCE parity setting Bitmap register: bit 1: En setting (echo) bit 2: Qn setting (quiet) bit 3: Vn setting (verbose) bit 5: Not applicable to 9602 Bitmap register: bit 0: Not applicable to 9602 bit 2: Not applicable to 9602 bits 3-4: &Dn setting (DTR operation) bit 5: Not applicable to 9602 bit 6: Not applicable to 9602 Not applicable to 9602
S14
0-255
170
S21
0-255
48
S22
59
Profile Setting?
Sr=n writable?
Register
Default
Range
Register
Default
Range
Description
S23
0-255
61
Bitmap register: bits 1-4: +IPR setting (DTE baud rate) bits 6-7: Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602
S25 S27 S28 S30 S31 S34 S35 S36 S37 S39 S40 S41 S42 S43 S44 S45 S47 S49 S51 S52 S54 S58 S95 S96 S98 S99 S100 S102 S103 0-255 3
Bitmap register: bits 0-2: &Kn setting (flow control) Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602
60
Register
Default
Range
Description
S104 S106 S107 S110 S111 S112 S113 S121 0-255 0-255 0-15 0 0 1
Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 SBD upload message sequence number (high byte) SBD upload message sequence number (low byte) New for 9602 Transceiver Bitmap register: bit 0: +SBDMTA setting (ring indication) bit 1-2: +SBDAREG setting (automatic registration)
S122
0-31
New for 9602 Transceiver Bitmap register: bit 0: *R setting (radio activity) bits 1-4: +CIER setting (indicator event reporting)
Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602 Not applicable to 9602
61
Revision 6.0
62
Revision 6.0
8 Informative Examples
8.1 Setting the Default Configuration
The FA sets the Transceivers default configuration to no handshaking, no flow control, radio enabled, SBD automatic notifications enabled.
To FA (from Transceiver) OK OK
Description Disable RTS/CTS flow control Enable the radio Enable SBD ring indications Store the configuration as profile 0 Select profile 0 as the power-up default
AT+CIER=1,0,1,0 OK +CIEV: 1,1 AT+SBDWB=70 READY <binary transfer> 0 AT+SBDIX +SBDIX: 0,23,0,-1,0,0 AT+SBDD0 OK
63
Revision 6.0
Description Query the Transceiver registration status Transceiver is detached, i.e. un-registered Tell the Transceiver to register for automatic notifications Transceiver is now registered Query the Transceiver registration status Transceiver is registered Enable SBD ring indications from Transceiver to FA
Description Query the Transceiver registration status Transceiver is registered Vendor application sends an MT message to the GSS Transceiver indicates an incoming message. The RI line also toggles. FA initiates an SBD session in answer to the automatic notification Transceiver informs FA that a 90-byte message was successfully received with MTMSN 237, and that two further MT messages are queued at the GSS FA retrieves the received message from the Transceiver
AT+SBDIXA
64
Revision 6.0
Description
Transfer message to 9602 Activate the radio and wait for the Transceiver to acquire the network Transceiver has acquired the network Perform SBD session Deactivate the radio Clear the MO message buffer
To FA (from Transceiver) OK
Description FA tells Transceiver to flush pending writes to Eeprom and waits for completion FA may now safely disconnect the Transceiver power supply.
65
Revision 6.0
9 Supported AT Commands
Table 9-3, lists the AT commands supported by the 9602 module. This list of supported commands is a subset of commands taken from Iridiums AT Command Specification. Table 9-3: Supported AT commands
Command AT A/ En In Qn Vn Zn &Dn &Fn &Kn &V &Wn &Yn %R *F *Rn +CCLK +CGMI +CGMM +CGMR +CGSN +CIER +CRIS +CSQ +CULK +GMI +GMM +GMR +GSN +IPR +SBDAREG +SBDC +SBDD +SBDDET +SBDDSC +SBDI +SBDIX +SBDIXA +SBDMTA +SBDRB
Description Attention code Repeat last command Echo Identification Quiet mode Verbose mode Soft reset DTR option Restore factory settings Flow control View active and stored configuration Store active configuration Designate default reset profile Display registers Flush to EEPROM Radio activity Real-time clock Manufacturer identification Model identification Revision Serial number Indicator event reporting Ring Indicator Status Signal quality Unlock Manufacturer identification Model identification Revision Serial number Fixed DTE rate Short burst data: Automatic registration Short burst data: Clear SBD MOMSN Short burst data: Clear SBD message buffers Short burst data: Detach Short burst data: Delivery short code Short burst data: Initiate an SBD session Short burst data: Initiate an SBD session extended Short burst data: Initiate an SBD session extended Short burst data: Mobile-terminated alert Short burst data: Read binary data from ISU
Note
Manual
66
Revision 6.0
Description Short burst data: Automatic registration Short burst data: Read a text message from the ISU Short burst data: Status Short Burst data Status Extended Short burst data: Transfer MO buffer to MT buffer Short burst data: Write binary data to the ISU Short burst data: Write a text message to the ISU Request system time
Note
Manual
67