User Guide for NAL RESEARCH models including: A3LA-RM Iridium Satellite Modem, A3LA-RM, Iridium Satellite Modem, Satellite Modem, Modem

Beverly Denny

A3LA-RM-MIL User Guide (Rev B 2023-03-07)

A3LA-RM-MIL - NAL Research

• Google Docs
• Google Drive
• Download [pdf]
• Download Optimized
• Document:
  • Text
  • References

File Info : application/pdf, 172 Pages, 2.67MB

451-93156-002C
A3LA-RM/A3LA-RM-MIL User Guide
Version C March 31, 2023
Copyright © 2023 by NAL Research Corporation 11100 Endeavor Ct., Suite 300 Manassas, Virginia 20109 USA Phone: 703-392-1136
Email: contact@nalresearch.com

AL3A-RM/A3LA-RM-MIL User Guide Version C
LEGAL DISCLAIMER AND CONDITION OF USE
This document contains information for the A3LA-RM and A3LA-RM-MIL modems and accompanying accessories ("Product"), which is provided "as is." Reasonable effort has been made to make the information in this document reliable and consistent with specifications, test measurements and other information. However, NAL Research Corporation and its affiliated companies, directors, officers, employees, agents, trustees or consultants ("NAL Research") assume no responsibility for any typographical, technical, content or other inaccuracies in this document. NAL Research 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. User assumes the full risk of using the Product specifications and any other information provided.
NAL Research 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 the 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 NAL Research 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, 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 to the fullest extent these damages may be disclaimed by law and whether advised of the possibilities of such damages. NAL Research is not liable for any claim made by a third party or made by you for a third party.

Document Number: 451-93156-002C

2 of 172

REVISION HISTORY

AL3A-RM/A3LA-RM-MIL User Guide Version C

Revision Date

Description

1.3

8/2/16

Initial version

Added revision history

Updated address

A

5/20/20

Updated document number

Added AT^VOLB command

A.1

06/09/2021 Updated to new template; proofread.

B

04/19/2022 Formal release

C

03-31-2023 Added A3LA-RM-MIL

Document Number: 451-93156-002C

3 of 172

REFERENCE DOCUMENTS

AL3A-RM/A3LA-RM-MIL User Guide Version C

The latest revisions of the NAL documents are available from the NAL Research website at https://www.nalresearch.com/.

Reference Title

Revision/Date

[1]

A3LA-RM Product Information

05/03/2019

[2]

Getting Started With Model A3LA-RM (TN2012-21V1.1)

04/08/2013

[3]

SatTerm Software Manual (TN451-94000-001A)

Version A, 06/01/2022

[4]

Additional Information on DirectIP SBD (TN2007-637V1.0)

02/01/2007

[5]

Additional Information on SBD (AN2012-04-V4.0)

02/01/2012

Document Number: 451-93156-002C

4 of 172

TABLE OF CONTENTS

AL3A-RM/A3LA-RM-MIL User Guide Version C

1 Introduction............................................................................................................... 17

2 Multi-interface Connector .......................................................................................... 19

2.1 RS232 Data Interface (Standard 9-Wire Configuration) ..................................................... 20

2.2 RS232 Data Interface (3-Wire Configuration)..................................................................... 20

2.3 DC Power Input ................................................................................................................... 21

2.4 Power On/Off Control......................................................................................................... 22

2.5 Audio Interface ................................................................................................................... 23

2.6 Digital Peripheral Link (DPL)................................................................................................ 24

3 Antenna Connector .................................................................................................... 25

4 SIM Card Interface ..................................................................................................... 27

5 LED Display ................................................................................................................ 28

6 Configuration Settings ................................................................................................ 29

7 Modes of Operation ................................................................................................... 30

8 AES-256 Bit Encryption ............................................................................................... 31

9 Self-monitoring to Prevent Modem Lockup ................................................................ 32

10 Mounting Recommendations ..................................................................................... 33

11 Technical Support ...................................................................................................... 34

12 Appendix A: AT Interface............................................................................................ 35

12.1 Command Types ................................................................................................................. 35

12.2 Basic Commands ................................................................................................................. 35

12.3 Extended Commands .......................................................................................................... 35

12.4 Command and Response Characters .................................................................................. 37

12.5 Command Entry .................................................................................................................. 37

12.6 Command Responses.......................................................................................................... 38

12.7 Hardware Failure Reporting................................................................................................ 39

Appendix B: AT Command Set Description ........................................................................ 40 (Iridium Radio Link Protocol)B.1 AT ­ Attention Code............................................................... 40 B.2 A/ ­ Repeat Last Command ................................................................................................ 40 B.3 +++ ­ Escape Sequence....................................................................................................... 40 B.4 En ­ Echo............................................................................................................................. 40 B.5 On ­ Online ......................................................................................................................... 40

Document Number: 451-93156-002C

5 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.6 Qn ­ Quiet Mode ................................................................................................................ 40 B.7 Vn ­ Verbose Mode ............................................................................................................ 41 B.8 Wn ­ Error Correction Message Control ............................................................................ 41 B.9 Zn ­ Soft Reset .................................................................................................................... 41 B.10 &Cn ­ DCD Option ................................................................................................................ 41 B.11 &Dn ­ DTR Option............................................................................................................... 41 B.12 &Fn ­ Restore Factory Settings........................................................................................... 42 B.13 &Kn ­ Flow Control ............................................................................................................. 42 B.14 &Mn ­ Asynchronous/Synchronous Mode......................................................................... 42 B.15 &Qn ­ Sync/Async Mode .................................................................................................... 42 B.16 &Sn ­ DSR Override ............................................................................................................ 43 B.17 &V ­ View Active and Stored Configuration ....................................................................... 43 B.18 &Wn ­ Store Active Configuration...................................................................................... 43 B.19 &Yn ­ Designate Default Reset Profile ............................................................................... 43 B.20 \Kn ­ Control Break............................................................................................................. 43 B.21 %R ­ Display Registers ........................................................................................................ 44 B.22 *Pn ­ Power ........................................................................................................................ 44 B.23 +CBST ­ Select Bearer Service Type.................................................................................... 44 B.24 +CGMI ­ Manufacturer Identification ................................................................................ 45 B.25 +CGMM ­ Model Identification .......................................................................................... 45 B.26 +CGMR ­ Revision ............................................................................................................... 45 B.27 +CGSN ­ Serial Number ...................................................................................................... 45 B.28 +CMEE ­ Report Mobile Equipment Error .......................................................................... 45 B.29 +CPAS ­ Modem Activity Status ......................................................................................... 47 B.30 +CR ­ Service Reporting Control ......................................................................................... 48 B.31 +DS ­ Set Data Compression Function................................................................................ 48 B.32 +DR ­ Data Compression Report Level ............................................................................... 49 B.33 +CEER ­ Extended Error Report .......................................................................................... 50 B.34 +CHUP ­ Hangup call........................................................................................................... 50 B.35 +CMGD ­ Delete SMS Message .......................................................................................... 51 B.36 +CMGF ­ SMS Message Format.......................................................................................... 53 B.37 +CMGL ­ List SMS Messages............................................................................................... 54

Document Number: 451-93156-002C

6 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.38 +CMGR ­ Read SMS Message ............................................................................................. 55 B.39 +CMGS ­ Send SMS Message.............................................................................................. 56 B.40 +CMGW ­ Write SMS Message To Memory ....................................................................... 56 B.41 +CMOD ­ Call Mode............................................................................................................ 57 B.42 +CNMI ­ New SMS Message Indications to DTE................................................................. 57 B.43 +COPS ­ Operator Select .................................................................................................... 59 B.44 +CPBF ­ Find Phonebook Entries ........................................................................................ 60 B.45 +CPBR ­ Read Phonebook Entries ...................................................................................... 61 B.46 +CPBS ­ Select Phonebook Storage .................................................................................... 61 B.47 +CPBW ­ Write Phonebook Entry....................................................................................... 62 B.48 +CPIN ­ Enter PIN................................................................................................................ 63 B.49 +CPMS ­ Select Preferred SMS Message Storage .............................................................. 64 B.50 +CREG ­ Network Registration ........................................................................................... 65 B.51 +CSCA ­ SMS Service Center Address ................................................................................. 66 B.52 +CSCB ­ Select Cell Broadcast Message Types ................................................................... 66 B.53 +CSCS ­ Select TE Character Set ......................................................................................... 67 B.54 +CSMS ­ Select SMS Message Service ................................................................................ 67 B.55 +CSTA ­ Select Type of Address.......................................................................................... 68 B.56 +GMI ­ Manufacturer Identification................................................................................... 68 B.57 +GMM ­ Model Identification ............................................................................................ 68 B.58 +GMR ­ Revision ................................................................................................................. 69 B.59 +GSN ­ Serial Number......................................................................................................... 69 B.60 +GCAP ­ General Capabilities ............................................................................................. 69 B.60.1A ­ Answer.......................................................................................................................... 69 B.62 D ­ Dial ................................................................................................................................ 69 B.62.1 D> ­ Direct Dial From Phonebook ..................................................................................... 70 B.63 Hn ­ Hangup........................................................................................................................ 70 B.64 S0=n ­ Auto-Answer ........................................................................................................... 71 B.65 Xn ­ Extended Result Codes ............................................................................................... 71 B.66 +CLVL ­ Volume Level Control ............................................................................................ 71 B.67 +CMUT ­ Mute Control....................................................................................................... 72 B.68 +CRC ­ Cellular Result Codes .............................................................................................. 73

Document Number: 451-93156-002C

7 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.69 +CVHU ­ Voice Hangup Control.......................................................................................... 73 B.70 +CCLK ­ Real-Time Clock ..................................................................................................... 74 B.71 ­MSVTS ­ DTMF Generation in Voice Call............................................................................ 74 B.72 ­MSVTR ­ DTMF Received in Voice Call ............................................................................. 75 B.73 ­MSVLS ­ Local DTMF Feedback Selection........................................................................... 76 B.74 ­MSSTM ­ Request System Time ......................................................................................... 76 B.75 ­MSGEO ­ Request Geolocation .......................................................................................... 77 B.76 +CCFC ­ Call Forward Service ............................................................................................... 78 B.77 +CLCC ­ Request Current Call Status .................................................................................. 80 B.78 +CNUM ­ Read MSISDN Numbers........................................................................................ 80 B.79 +CSSSC ­ Supplementary Services Shortcode ...................................................................... 80 B.80 +WIRLP ­ Iridium Radio Link Protocol .................................................................................. 81 B.81 +WFRNG ­ Force IRLP Renegotiation ................................................................................... 83 B.82 +WTM ­ IRLP Test Mode..................................................................................................... 83 B.83 +WDLDM ­ IRLP Dynamic Link Delay Measurement............................................................ 84 B.84 +WDAV ­ Register or Deregister an RS232 DAV Data Peripheral....................................... 84 B.85 +SBDWB ­ Short Burst Data: Write Binary Data................................................................. 85 B.86 +SBDRB ­ Short Burst Data: Read Binary Data ................................................................... 86 B.87 +SBDRT ­ Short Burst Data: Read Text Message ................................................................ 86 B.88 +SBDD ­ Short Burst Data: Clear SBD Message Buffer(s) ................................................... 87 B.89 +SBDC ­ Short Burst Data: Clear SBD MOMSN ................................................................... 88 B.90 +SBDS ­ Short Burst Data: Status........................................................................................ 88 B.91 +SBDTC ­ Short Burst Data: Transfer MO Buffer to MT Buffer .......................................... 89 B.92 +CAR ­ Audio Output Control ............................................................................................. 89 B.93 In ­ Identification ................................................................................................................ 89 B.94 +CIER ­ Indicator Event Reporting ...................................................................................... 90 B.95 +CRIS ­ Ring Indication Status ............................................................................................ 92 B.96 +CSQ[F] ­ Signal Quality...................................................................................................... 92 B.97 +CULK ­ Unlock ................................................................................................................... 93 B.98 +CVMI ­ Voicemail Indication ............................................................................................. 94 B.99 +CICCID ­ Read ICC ID from SIM ......................................................................................... 95 B.100 +CLIP ­ Calling Line Identification Presentation ................................................................. 95

Document Number: 451-93156-002C

8 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.101 +CLIR ­ Calling Line Identification Restriction .................................................................... 96 B.102 +IPR ­ Fixed DTE Rate ......................................................................................................... 97 B.103 +SBDWT ­ Short Burst Data: Write a Text Message........................................................... 98 B.104 +SBDDET ­ Short Burst Data: Detach ................................................................................. 99 B.105 +SBDI ­ Short Burst Data: Initiate an SBD Session............................................................ 100 B.106 +SBDIX[A] ­ Short Burst Data: Initiate an SBD Session Extended .................................... 101 B.107 +SBDDSC ­ Short Burst Data: Delivery Short Code........................................................... 104 B.108 +SBDMTA ­ Short Burst Data: Mobile-Terminated Alert ................................................. 105 B.109 +SBDREG ­ Short Burst Data: Network Registration ........................................................ 105 B.110 +SBDAREG ­ Short Burst Data: Automatic Registration ................................................... 108 B.111 +SBDSX ­ Short Burst Data: Status Extended ................................................................... 110 B.112 +CCWA ­ Call Waiting service........................................................................................... 111 B.113 +CLCK ­ Facility Lock ......................................................................................................... 113 B.114 +CPWD ­ Change Password .............................................................................................. 116 B.115 +CSDT ­ Sidetone .............................................................................................................. 117 B.116 +CDSI ­ Report SMS status ............................................................................................... 117 B.117 +GPSSTA ­ Configure GPS Status ...................................................................................... 119 B.118 +PA ­ GPS: List of NMEA Message Formats...................................................................... 119 B.119 +PLOC ­ GPS: Display Position to 5th Decimal Place ......................................................... 120 B.120 ^AA ­ Auto Answer Display............................................................................................... 120 B.121 ^AD ­ Auto Dial ................................................................................................................. 120 B.122 ^ADR ­ Auto Dial Retry ..................................................................................................... 121 B.123 ^CCOP ­ Change Crypto Officer Password (Encryption) .................................................. 121 B.124 ^CMGEC ­ Clear SMS Encrypted Storage ......................................................................... 121 B.125 ^FFW ­ Flash Firmware..................................................................................................... 122 B.126 ^KD ­ Key for Decryption (Encryption)............................................................................. 122 B.127 ^KE ­ Key for Encryption (Encryption).............................................................................. 122 B.128 ^KZ ­ Key Zeroization (Encryption)................................................................................... 123 B.129 ^MODRSTn ­ Modem Reset Information Message Displayed ......................................... 123 B.130 ^MPTDC- Modem Power Toggle Data Connection .......................................................... 123 B.131 ^MPTFP- Modem Power Toggle Forced Power-cycle ...................................................... 124 B.132 ^MPTFR- Modem Power Toggle Forced Registration ...................................................... 125

Document Number: 451-93156-002C

9 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.133 ^MPTNC- Modem Power Toggle Not in Data Connection ............................................... 125 B.134 ^MSB ­ Motion Sensor Begin ........................................................................................... 126 B.135 ^PKTS ­ Use Packets ......................................................................................................... 126 B.136 ^PKTST ­ Packet Send Timer............................................................................................. 127 B.137 ^PKTRT ­ Packet Resend Timer ........................................................................................ 127 B.138 ^PKTTH ­ Packet Send Threshold ..................................................................................... 128 B.139 ^RESETMODEMTG ­ Reset Modem Toggle ...................................................................... 128 B.140 ^RESETMODEMVF ­ Reset Modem Verify ....................................................................... 128 B.141 ^RLE ­ Use Run Length Encoding...................................................................................... 129 B.142 ^SE ­ Configure Streaming Encryption ............................................................................. 129 B.143 ^SMSD ­ SMS Delete ........................................................................................................ 130 B.144 ^SMSE ­ SMS Erase........................................................................................................... 130 B.145 ^SMSR ­ SMS Read ........................................................................................................... 130 B.146 ^SSI ­ Send Start-Up Information ..................................................................................... 131 B.147 ^STR ­ Self Test Run (Encryption)..................................................................................... 131 B.148 ^UE ­ Use Encryption ....................................................................................................... 131 B.149 ^VOLB ­ Volume Boost ..................................................................................................... 132 Appendix C: S-Register Definitions ..................................................................................... 133 C.1 S-Register Commands ....................................................................................................... 133 C.1.1 Sr ­ Direct S-Register Reference....................................................................................... 133 C.1.2 Sr? ­ Direct S-Register Read ............................................................................................. 133 C.1.3 Sr=n ­ Direct S-Register Write.......................................................................................... 133 C.1.4 Referenced S-Register Read ............................................................................................. 133 C.1.5 =n ­ Referenced S-Register Write .................................................................................... 133 C.2 Standard S-Registers ......................................................................................................... 134 C.3 Iridium Specific S-Register Extensions .............................................................................. 137 Appendix D: Summary of Result Codes .............................................................................. 141 Appendix E: Informative Examples..................................................................................... 145 E.1 Unit Identification ............................................................................................................. 145 E.2 Setting the Default Configuration..................................................................................... 146 E.3 Power-on to Sending an SBD Message ............................................................................. 146 E.4 SBD Automatic Notification Registration.......................................................................... 147

Document Number: 451-93156-002C

10 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
E.5 SBD Automatic Notification Message Reception.............................................................. 148 E.6 SBD Automatic Notification Automatic Registration ........................................................ 149 E.7 Originating a Data Call ...................................................................................................... 149 E.8 Answering a Data Call ....................................................................................................... 150 E.9 Disconnecting a Data Call ................................................................................................. 150 E.10 Coordination of +CLCC and +CPAS responses................................................................... 151 Appendix F: Power Consumption ....................................................................................... 153 Appendix G: The Iridium Network...................................................................................... 160 G.1 Iridium Network Data Capabilities.................................................................................... 161 G.2 Dial-up Data Service.......................................................................................................... 162 G.3 Direct Internet Connection ............................................................................................... 164 G.4 Short Burst Data................................................................................................................ 165 G.5 Short Messaging Service ................................................................................................... 165 G.6 RUDICS .............................................................................................................................. 166 G.7 Iridium Geolocation .......................................................................................................... 166 Appendix H: Standards Compliance ................................................................................... 167 Appendix I: MIL-STD-810G Certification ............................................................................. 168 Appendix J: Export Compliance .......................................................................................... 169 Appendix K: Design Specifications...................................................................................... 170 K.1 Mechanical Specifications................................................................................................. 170 K.2 RF Specifications ............................................................................................................... 170 K.3 Electrical Specifications..................................................................................................... 170 K.4 Environmental Specifications ........................................................................................... 171 K.5 Data I/O Specifications...................................................................................................... 171 K.6 Related Hardware ............................................................................................................. 171 Appendix L: Mechanical Drawing ....................................................................................... 172

Document Number: 451-93156-002C

11 of 172

TABLE OF FIGURES

AL3A-RM/A3LA-RM-MIL User Guide Version C

Figure 1: Iridium Satellite Modem A3LA-RM ................................................................................ 18 Figure 2: Power Input Setting for the A3LA-RM ........................................................................... 22 Figure 3: A3LA-RM Connected to a DPL Handset via the HRC-24-8R ........................................... 24 Figure 4: Location of the SIM Reader ........................................................................................... 27 Figure 5: Iridium Satellite Modem A3LA-RM ................................................................................ 28 Figure 6: Average Current Drawn During Standby ..................................................................... 154 Figure 7: Average Power Consumption During Standby ............................................................ 154 Figure 8: Average Current Drawn During Standby with DPL Handset........................................ 155 Figure 9: Average Power Consumption During Standby with DPL Handset............................... 155 Figure 10: Average Current Drawn During a Data Switch Call.................................................... 156 Figure 11: Average Power Consumption During a Data Switch Call........................................... 156 Figure 12: Average Current Drawn During an SBD Transmission ............................................... 157 Figure 13: Average Power Consumption During an SBD Transmission ...................................... 157 Figure 14: Average Current Drawn During an SMS Transmission .............................................. 158 Figure 15: Average Power Consumption During an SMS Transmission ..................................... 158 Figure 16: Average Current Drawn During a Voice Call Using DPL Handset .............................. 159 Figure 17: Average Power Consumption During a Voice Call Using DPL Handset ..................... 159 Figure 18: Iridium Network Major Components ........................................................................ 160 Figure 19: Iridium Network Data Capabilities............................................................................. 162 Figure 20: PSTN Dial-up Connectivity ......................................................................................... 163 Figure 21: Iridium Dial-up Data Service ...................................................................................... 164 Figure 22: Mil-STD-810G Certification ........................................................................................ 168 Figure 23: A3LA-RM Mechanical Drawing .................................................................................. 172

Document Number: 451-93156-002C

12 of 172

TABLE OF TABLES

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 1: Pin Assignment for the Multi-interface Connector......................................................... 19 Table 2: General RF Parameters ................................................................................................... 25 Table 3: Custom Antenna Specifications ...................................................................................... 25 Table 4: Numeric and Verbose Mode Formats............................................................................. 39 Table 5: Standard S-Registers ..................................................................................................... 134 Table 6: Iridium Specific S-Register Extensions .......................................................................... 137 Table 7: V.25ter/Hayes Result Codes.......................................................................................... 141 Table 8: GSM 7.07 Result Codes ................................................................................................. 143 Table 9: GSM 7.05 Result Codes ................................................................................................. 143 Table 10: Iridium Specific Result Codes ...................................................................................... 144 Table 11: Unit Identification ....................................................................................................... 145 Table 12: Default Configuration.................................................................................................. 146 Table 13: Sending an SBD Message ............................................................................................ 146 Table 14: SBD Automatic Notification Registration .................................................................... 147 Table 15: SBD Automatic Notification Message Reception ........................................................ 148 Table 16: SBD Automatic Notification Automatic Registration .................................................. 149 Table 17: Originating a Data Call................................................................................................. 149 Table 18: Answering a Data Call ................................................................................................. 150 Table 19: Disconnecting a Data Call............................................................................................ 150 Table 20: Coordination of +CLCC and +CPAS Responses ............................................................ 151

Document Number: 451-93156-002C

13 of 172

ACRONYM LIST

AL3A-RM/A3LA-RM-MIL User Guide Version C

3GPP ...........................3rd Generation Partnership Project AES .............................Advanced Encryption Standard ASCII ...........................American Standard Code for Information Interchange AT ...............................Two-letter sequence starting a string of modem commands. The AT is
intended to get the modem's attention prior to executing a command. BIS ..............................Bureau of Industry and Security CTS..............................Clear to send DAV ............................Data After Voice DC ...............................Direct current DCD ............................Data carrier detect DCE .............................Data circuit-terminating equipment DoD ............................Department of Defense DPL .............................Digital Peripheral Link DSN.............................Defense Switch Network D-sub ..........................D-subminiature DSR .............................Data set ready DTE .............................Data terminal equipment DTMF..........................Dual-tone multi-frequency DTR .............................Data terminal ready EAR .............................Export Administration Regulations EMI .............................Electromagnetic interference EMSS ..........................Enhanced Mobile Satellite Services ETSI.............................European Telecommunications Standards Institute FCC .............................Federal Communications Commission FDMA .........................Frequency-division multiple access GMT............................Greenwich Mean Time GND ............................Ground GPRS ...........................General Packet Radio Service GPS .............................Global Positioning System

Document Number: 451-93156-002C

14 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
GSM............................Global System for Mobile Communications IMEI ............................International Mobile Equipment Identification I/O ..............................Input/output IP ................................Internet Protocol IP67 ............................Ingress Protection Code 67 ISP...............................Internet Service Provider ISU ..............................Iridium subscriber unit (modems, phones, trackers) LAN .............................Local area network LBT..............................L-band transceiver LCD .............................Liquid-crystal display LED .............................Light-emitting diode LEO .............................low-earth orbit NIPRNet......................Non-classified Internet Protocol Router Network NMEA .........................National Marine Electronics Association NOC ............................Network Operation Center OFAC...........................Office of Foreign Asset Controls PCM ............................Pulse-code modulation PIN ..............................Personal identification number PPP .............................Point-to-point protocol PSTN ...........................Public switched telephone network RF................................Radio frequency RH ...............................Relative humidity RHCP...........................Right-handed circular polarization RI ................................Ring indicator RTS..............................Request to send RUDICS .......................Router-based unrestricted digital internetworking connectivity solution SBD .............................Short-burst data SIM .............................Subscriber identification module SMS ............................Short message service TBR .............................Time Between Reports

Document Number: 451-93156-002C

15 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
TCP .............................Transmission Control Protocol TDD.............................Time-division duplex TDMA .........................Time-division multiple access TNC.............................Threaded Neill­Concelman TON ............................Type of number UART...........................Universal asynchronous receiver-transmitter VDC.............................Volts (Direct Current) VSWR..........................Voltage standing wave ratio

Document Number: 451-93156-002C

16 of 172

1 INTRODUCTION

AL3A-RM/A3LA-RM-MIL User Guide Version C

This user guide provides you with information on the operational features, and electrical and mechanical interfaces of the A3LA-RM. The A3LA-RM is a satellite modem comprising a 9523 Lband transceiver (LBT) with an extended input voltage range. The A3LA-RM-MIL is a variation of the original A3LA-RM. It functions the same as the A3LA-RM, but is also certified to the environmental MIL-STD-810G standards and is IP67 rated.

NOTE: Unless otherwise noted, all references to the A3LA-RM also applies to the A3LA-RM-MIL.

The A3LA-RM has an internal microcontroller programmed to monitor the modem's connectivity status to prevent hardware lockup. It is designed to transmit either AES 256-bit encrypted or unencrypted data via the Iridium satellite network. Similar to a standard landline modem, the A3LA-RM can be controlled by any data terminal equipment (DTE) capable of sending standard AT commands via an RS232 serial port. A DTE can be a desktop computer, a laptop computer, a smartphone, or even a microcontroller. The A3LA-RM is functionally compatible with models 9522B, A3LA-R, and A3LA-RS. It is approximately 60% smaller in volume and 50% lighter than the 9522B. Model A3LA-RM-MIL is an A3LA-RM that has been certified to MIL-STD-810G standards and IP67 rating.

Services supported include:

 Dial-up data switch  Direct Internet connection (or NIPRNet connection)  Direct Internet connection using Apollo Emulator (only for DoD EMSS gateway)  Short message service (SMS)  Short burst data (SBD)  Router-based unrestricted digital internetworking connectivity solution (RUDICS)  Voice when combined with the Digital Peripheral Link (DPL) audio handset

Document Number: 451-93156-002C

17 of 172

SIM Reader under the Lid

AL3A-RM/A3LA-RM-MIL User Guide Version C TNC Antenna Connector

DB25 Multi-interface Connector
Figure 1: Iridium Satellite Modem A3LA-RM
Important: Do not disassemble the A3LA-RM for repair or services. The warranty is voided if the A3LA-RM is disassembled. Return it to NAL Research for any services.

Document Number: 451-93156-002C

18 of 172

2 MULTI-INTERFACE CONNECTOR

AL3A-RM/A3LA-RM-MIL User Guide Version C

The multi-interface connector is a male 25-pin miniature D-sub type that includes five interfaces--RS232, DC input power, ON/OFF control line, analog audio, and DPL. The multiinterface connector pin assignments are summarized in Table 1, which is `pin-to-pin' the same as model A3LA-R, A3LA-XM, and A3LA-X.

Table 1: Pin Assignment for the Multi-interface Connector

Pin # Signal

Description

Interface

1 EXT_ON_OFF Power on/off control input

DC Power

2 +12VDC

Output voltage to power the DPL handset DC Power

3 EXT_GND External GND input

DC Power

4 EXT_B+

External 4.0 V ­ 5.4 V or 5.0 V ­ 32.0 V

DC Power

5 SPKR_AUD Speaker audio output

Analog Audio

6 DA_TX

PCM digital audio output

Digital Audio

7 RI

RS232 ring indicator

RS232 Data

8 RTS

RS232 request to send

RS232 Data

9 TX

RS232 transmit data (input)

RS232 Data

10 DCD

RS232 data carrier detect

RS232 Data

11 DA_FS

PCM digital audio frame sync output

Digital Audio

12 DA_CLK

PCM digital 2.048 MHz audio clock output Digital Audio

13 RX

RS232 receive data (output)

RS232 Data

14 SIGNAL GND Signal ground, 0 V signal reference and return GND

15 MIC_AUD Microphone audio input

Analog Audio

16 EXT_B+

External 4.0 V ­ 5.4V or 5.0 V ­ 32.0 V

DC Power

17 EXT_GND External GND input

DC Power

Document Number: 451-93156-002C

19 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 1: Pin Assignment for the Multi-interface Connector

Pin # Signal

Description

Interface

18 DPL_TX

Digital Peripheral Link (DPL) data output

DPL UART

19 DTR

RS232 data terminal ready

RS232 Data

20 DPL_RX

Digital Peripheral Link (DPL) data input

DPL UART

21 DSR

RS232 data set ready

RS232 Data

22 CTS

RS232 clear to send

RS232 Data

23 SIGNAL GND Signal ground, 0 V signal reference and return GND

24 DA_RX

PCM digital audio input

Digital Audio

25 SIGNAL GND Signal ground, 0 V signal reference and return GND

2.1 RS232 DATA INTERFACE (STANDARD 9-WIRE CONFIGURATION)
The A3LA-RM supports a standard RS232 data interface to a DTE incorporating hardware handshaking and flow control. The RS232 data interface comprises eight standard RS232 data, control, and status signals, plus a ground-level signal reference, as shown in Table 1. This interface allows a connected DTE to utilize the A3LA-RM's modem functionality through a set of AT commands. These commands are defined in Appendix A: AT Interface. The factory-set baud rate is 19,200 bps and can be changed using the +IPR command.

Note that the Ring Indicator is used by the A3LA-RM to indicate that a mobile-terminated SBD (MT-SBD) message is queued at the gateway. Application developers can monitor this pin and apply appropriate AT commands to the A3LA-RM to retrieve the MT-SBD message.

2.2 RS232 DATA INTERFACE (3-WIRE CONFIGURATION)
A 3-wire RS232 data interface may also be implemented. Because of risk of overrun and data loss, especially at high baud rates, the 9-wire interface is the recommended implementation. Several steps must be taken to allow 3-wire configuration (i.e., only using S_TX, S_RX, and SIGNAL GND). These steps ensure the A3LA-RM and DTE work together without having hardware handshaking.

Document Number: 451-93156-002C

20 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
1. The modem's DTR line must be held high. Using the modem's input voltage is fine for this purpose BUT ONLY if the input voltage is less than 5 VDC (see important note below). Looping back the modem's DSR line to DTR line will NOT work. Leave the DSR line on the modem unconnected.

2. Disconnect the CTS, DCD, DSR, DTR, RTS, and RI lines between the DTE and modem.

3. Set AT&Dn to AT&D0 to ignore the DTR input from the DTE.

4. Set AT&Kn to AT&K0 for no flow control.

5. The setting can be stored on the modem permanently (until another setting overwrites it) so that it remains after a power cycle. The modem allows two profiles in which settings are stored; you can choose either as a default profile. The relevant commands are &Wn and &Yn. &Wn stores the present configuration in profile <n>, where <n> can be either 0 or 1. &Yn designates which profile is loaded after reset or power-up; <n> is either 0 or 1.

6. Address any needs of the DTE separately.

Warning: DO NOT use the modem's input voltage to bring the DTR line high when the input voltage is higher than 5 VDC. Supplying voltage higher than 5 VDC to the DTR line will permanently damage the A3LA-RM.

Note: The Iridium's Direct Internet service when using the Windows-based Apollo client requires Data Carrier Detect (DCD) to be present; hence it is incompatible with a 3-wire serial configuration. The Direct Internet with Apollo client is available only on the EMSS DoD gateway and NOT on the commercial gateway.

2.3 DC POWER INPUT
The DC power input is through pin 4 & 16 (EXT_B+) and pins 3 & 17 (EXT_GND). Note that two pins are provided for the external DC input and two pins are also provided for the associated external ground input. This is done to distribute the current across two wires, and therefore all four pins should be utilized in the external power connection. Keep cables used to supply power to the A3LA-RM as short as possible to prevent significant voltage drop, which can cause the A3LA-RM to malfunction during a data call, an SMS session, or an SBD session. Power reset by

Document Number: 451-93156-002C

21 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
the A3LA-RM during a call is an indication that the DC power source is unable to sustain voltage above 4.0 V at peak current demand. Appendix F: Power Consumption provides the electrical power profile of the A3LA-RM.
The A3LA-RM accepts either +4.0 V to +5.4 V or +5.0 V to +32 V input. The A3LA-RM is shipped with hardware set for +5.0 V to +32 V input. It can be changed to +4.0 V to +5.4 V input through an internal jumper--POWER MUST BE DISCONNECTED BEFORE RESETTING THE JUMPER. Find the jumper by removing the modem's bottom plate. With the A3LA-RM held in the position shown in Figure 2 (DB25 connector to the left), the A3LA-RM is set for 4.0 V to +5.4 V when the red jumper is on the middle and left pins, and it is set for +5.0 V to +32 V when the jumper is on the middle and right pins. Each pin is also labeled with 5 V and 32 V to the left and right pins, respectively.
Note: Remember the input voltage setting on the A3LA-RM and do not apply voltage above the maximum limit (of either 5.4 V or 3 2V). The A3LA-RM will be damaged beyond repair with warranty voided if this were to occur.

Red jumper used to set input voltage range
Figure 2: Power Input Setting for the A3LA-RM
Important: You can remove the A3LA-RM's bottom plate to set the jumper but not for repair or services. The warranty is voided if the A3LA-RM is disassembled for any reason other than to set the jumper.
2.4 POWER ON/OFF CONTROL
With the EXT_ON_OFF pin left unconnected, the A3LA-RM automatically turns on or off when external DC power is applied or removed. Prior to turning the A3LA-RM off, issue command AT*P0 to ensure all memory write activity is completed. When the A3LA-RM is powered off, its

Document Number: 451-93156-002C

22 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
internal power-on-reset circuit requires two seconds for voltages to decay. Do not reapply power until this time has elapsed. If the two-second wait time is not adhered to, the reset circuit may not operate and the A3LA-RM could be placed in a nonoperational state. The state is not permanent and can be rectified by the above procedure.
The A3LA-RM automatically turns on/off when external DC power is applied/removed via the EXT_B+ and EXT_GND inputs. The EXT_ON_OFF (pin 1) control input is used to turn a powered A3LA-RM on and off in a toggle fashion. The EXT_ON_OFF control input is normally "floating" (i.e., high). When it is pulled to GND level (i.e., low) for at least 270 ms and released, the A3LARM alternates from its current on/off state. The current drawn on the external load used to pull the A3LA-RM to GND is no more than 0.5 mA. The signal on pin 1 is considered GND when it is at 0.5 V or less.
2.5 AUDIO INTERFACE
The A3LA-RM supports both digital and analog audio Input/output (I/O). The digital audio is in PCM format. In such format, digital audio cannot travel far (less than one foot); this is why the analog is chosen for the A3LA-RM audio handset. The analog audio input is a single-ended, unbalanced input with a minimum impedance of 10 k to ground. The A3LA-RM accepts a maximum input level of 2.0 V peak-to-peak without signal distortion. The analog audio output is also a single-ended, unbalanced output capable of driving an impedance of 600  or more to ground. The A3LA-RM delivers undistorted audio up to 2.0 V peak-to-peak.
The combined analog I/O audio interface (pins 5 and 15) and the DPL UART I/O interface (pins 18 and 20) enable an analog audio handset to be connected to the A3LA-RM. With the DPL audio handset model DPLS0401-X and DB25 data kit model HRC-24-8R, the A3LA-RM can be used both as a data modem and a satellite phone. This setup, as shown in Figure 3, can be an extremely useful developmental tool because the modem status can be seen on the handset Liquid-crystal display (LCD) similar to a 9555 Iridium phone.

Document Number: 451-93156-002C

23 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

A3LA-RM Modem HRC-24-8R Data Kit

DPL Handset

Figure 3: A3LA-RM Connected to a DPL Handset via the HRC-24-8R
2.6 DIGITAL PERIPHERAL LINK (DPL)
The DPL interface is composed of two ports--a full duplex asynchronous serial link for control messages and a Pulse-code modulation (PCM) digital audio link for audio traffic. The protocol used on these ports is made available to application developers only on a case-by-case basis and after appropriate non-disclosure agreements and/or license agreements are executed.

Document Number: 451-93156-002C

24 of 172

3 ANTENNA CONNECTOR

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM modem uses a single Threaded Neill­Concelman (TNC) female 50-ohm connector for both transmit and receive. Cable loss between the modem and the antenna is critical and must be kept less than 3 dB at the operating frequency of 1616 to 1626.5 MHz. The minimum link margin of 12 dB must also be maintained. General RF parameters are listed in the table below.

Table 2: General RF Parameters

Type

Description

Frequency Range

1616 to 1626.5 MHz

Input/Output Impedance 50 Ohms

Oscillator Stability

±1.5 ppm

NAL Research offers several types of antennas for use with the A3LA-RM modem. These antennas include the fixed mast, mobile magnetic/permanent mount, and portable auxiliary. For low cost and applications where small form factor and light weight are required, NAL Research recommends model SYN7391-C. If the specific application requires a custom antenna, it must meet the specifications below.

Table 3: Custom Antenna Specifications

Parameter

Value

Operating Temperature Range ­40°C/+85°C without loss of function

Measurement Frequency Range 1616 to 1626.5 MHz

VSWR

< 1.5 : 1

Maximum Gain

3 dBic

Nominal Impedance

50 Ohms

Polarization

Right-handed circular polarization (RHCP)

Basic Pattern

Omnidirectional and hemispherical

Document Number: 451-93156-002C

25 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Satellite signal strength reported by the A3LA-RM when issuing an AT+CSQ command indicates the signal strength of the ring channel. Be careful when using this signal reading for comparisons between devices. Of particular note are the following:
1. There is a 0.5 dB tolerance on the calibration. 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. If the reading is near the decision threshold, it would be easy to see a 1-bar difference.

Document Number: 451-93156-002C

26 of 172

4 SIM CARD INTERFACE

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM modem contains an integrated Subscriber identification module (SIM) reader. The modem uses and requires an Iridium SIM chip for operation. The SIM chip is inserted into the opening located on top of the modem, as shown in Figure 4. A plastic locking mechanism is used hold the SIM in place. Place the SIM chip (facing down) into the SIM reader's bracket. Ensure that the cutoff on the SIM chip aligns with the SIM reader.

SIM Reader
Figure 4: Location of the SIM Reader

Document Number: 451-93156-002C

27 of 172

5 LED DISPLAY

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM has three status LEDs depicted as P for power indicator, I for Iridium satellite signal strength, and S for status (see Figure 5). They provide a quick visual check to ensure proper modem operations and a way to optimize antenna locations during field installation. These LEDs provide the following information:

 P: LED lights up when power is provided to the A3LA-RM.  I: LED stays solid when the signal strength is between 3­5, blinks when the signal
strength is between 1 and 2, and is off when signal strength is 0. The Light-emitting diode (LED) also stays solid when the carrier detects (CD) line on the RS232 goes high during a data call.  S: LED lights up when the A3LA-RM is in data mode.

Power, Iridium, Status LEDs
Figure 5: Iridium Satellite Modem A3LA-RM

Document Number: 451-93156-002C

28 of 172

6 CONFIGURATION SETTINGS

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM allows users to configure its data port communication parameters. The three configuration types are active, factory default, and stored.

 Active: The active configuration is the set of parameters currently in use. They can be changed individually via specific AT commands.
 Factory default: The factory default configuration is stored in permanent memory. This configuration can be recalled at any time through use of the AT&Fn command.
 Stored: Two groups of settings, or "profiles," can be stored as user-defined configurations. o First create desired active configurations and then write them to memory using the AT&Wn command. o These profiles can be designated to be loaded as the active configuration upon A3LA-RM power-up through use of the AT&Yn command. o The A3LA-RM can be reset without loss of power to these profiles through use of the ATZn command. o The configuration settings are stored in "S-register" locations and are detailed in Appendix A: AT Interface.

Document Number: 451-93156-002C

29 of 172

7 MODES OF OPERATION

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM serial data port is always in one of two modes: command mode or data mode.

Command Mode

When the data port is in command mode, AT commands can be entered to control the A3LARM. In command mode, flow control has no effect, if the Request to send (RTS) input ignored and the CTS output driven ON (low).

Data Mode

When in data mode, the A3LA-RM transfers data over the Iridium network. In data mode:

1. All characters from the DTE are sent over the Iridium network to the remote side of the connection.

2. No unsolicited result codes are issued.

3. RTS/CTS flow control, if enabled, is active. When RTS is OFF (high), the A3LA-RM suspends transfer of data to the DTE; when Clear to send (CTS) is OFF (high), the A3LARM expects the DTE to suspend transfer of data.

Transitions between the modes of operation are performed automatically by the A3LA-RM in response to AT commands; the DTE has no other control over the mode.

Document Number: 451-93156-002C

30 of 172

8 AES-256 BIT ENCRYPTION

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM modem has a built-in AES-256 encryption software module. It can transmit either encrypted or unencrypted data in all modes--dial-up, direct Internet, RUDICS, SBD, and SMS. The A3LA-RM does not support encrypted voice calls. All voice calls are made in the `clear' unless an external encryption module is hooked to it, such as the General Dynamics® Sectéra. When encryption is enabled and for non-packetized data transmission modes (including dial-up, direct Internet, and RUDICS), the A3LA-RM sends data in NAL Research's proprietary format called packet send mode. Packet send mode is implemented to handle AES-256 frame synchronization between the A3LA-RM and a connected device. The encryption and decryption keys are matched in each frame to ensure NIST FIPS 140-2 compliance.

Instructions on how to use encryption can be found in the AT Command Reference manual in Appendix B: AT Command Set Description. The list of AT commands used to set encryption include ^CCOP, ^KD, ^KE, ^KZ, ^STR, and ^UE. The encryption algorithm implemented into the A3LA-RM complies with NIST FIPS 140-2 as defined in the following documents (https://csrc.nist.gov/publications/detail/fips/140/2/final):

 Security Requirements for Cryptographic Modules, FIPS PUB 140-2, US Department of Commerce, National Institute of Standards and Technology, May 25, 2001
 Security Requirements for Cryptographic Modules, Annex A: Approved Security Functions for FIPS PUB 140-2, US Department of Commerce, National Institute of Standards and Technology, February 19, 2003

Document Number: 451-93156-002C

31 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
9 SELF-MONITORING TO PREVENT MODEM LOCKUP
The 9523 RF board can sometimes `lock up' when inactive over a long period of time (a day or longer). The only way to recover is to power cycle the Iridium subscriber (ISU). The A3LA-RM has safeguards put in place with a watchdog timer to keep the 9523 RF board from locking up. These were done by having another microcontroller in-line with the serial communications, monitoring the communications, and ensuring the 9523 is responding correctly. Each of the safeguards is enabled by default. Below is a description of each of the four safeguards. These safeguards were also employed on the A3LA-MPT and A3LA-XM.
 Check When Not in a Data Call: The microcontroller has a timer that is reset every time a character arrives from the 9523 board. The timer is set to end every 2 minutes. When the timer expires, the microcontroller sends an AT command to the 9523 to verify it is still responding. If the 9523 responds, it starts the counter over again. If there is not response, it power cycles the 9523. This can be enabled or disabled with the ^MPTNC command.
 Check When in a Data Call: The microcontroller has a timer that is reset every time a character arrives from the 9523 board during data calls. The timer is set to end every 4 minutes during data calls. When the timer expires, the microcontroller verifies the 9523 is still responding by sending it the +++ sequence. If the 9523 responds, it returns to the data connection and starts the counter over again. If there is no response, it power cycles the 9523. This can be enabled or disabled with the ^MPTDC command.
 Registrations Every 23 Hours: The microcontroller forces manual registration by implementing the command AT+COPS=1 every 23 hours to ensure the 9523 stays registered. Registration will not occur during a data/voice call. This can be enabled or disabled with the ^MPTFR command.
 Forced Power Cycles Every 24 Hours: The microcontroller forces a power cycle of the 9523 board every 24 hours. Power cycle will not happen during a data/voice call. This can be enabled or disabled with the ^MPTFP command.

Document Number: 451-93156-002C

32 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
10 MOUNTING RECOMMENDATIONS
The A3LA-RM has four features on its bottom surface that can aid in its mounting (see Appendix L: Mechanical Drawing). These four features are predrilled at a minimum depth of 0.25 inch to accept 6-32 thread type.

Document Number: 451-93156-002C

33 of 172

11 TECHNICAL SUPPORT
For technical support, please contact us at:
Phone: 571-833-2169 Fax: 703-392-6795 Email: Support@Nalresearch.com

AL3A-RM/A3LA-RM-MIL User Guide Version C

Technical documents are also available to download on NAL Research's website www.nalresearch.com.

Document Number: 451-93156-002C

34 of 172

12 APPENDIX A: AT INTERFACE

AL3A-RM/A3LA-RM-MIL User Guide Version C

12.1 COMMAND TYPES
The A3LA-RM employs two principal types of AT commands: basic and extended. The two types have differing syntax used to query and adjust their settings. They also have unique reference standards. A specific basic AT command is used to reference S-registers and query and adjust their settings. Its syntax is similar to that of extended AT commands.

12.2 BASIC COMMANDS
Basic commands are industry standard and originally developed for Hayes-compatible PSTN modems. In many cases, basic commands consist of a single ASCII alpha character. In other cases, a special character precedes the alpha character. Prefix characters used in A3LA-RM basic commands include &, \, %, and *.

Most alpha characters in basic commands are followed by a numeric parameter, n. To adjust its setting, a basic command is entered with the appropriate numeric value of n. Note that if the numeric parameter n is omitted from the basic command entry, a value of zero is assumed for n. For example, ATXn is set to a value of 4 by entering ATX4, whereas it is set to value of 0 by entering either ATX0 or ATX.

To query a basic command setting, enter the AT&V command to view the active configuration of a group of basic commands. Some basic commands listed in this document are marked with "No action, compatibility only." In these cases, the basic command is accepted in the same fashion as it is with other modems, but has no effect on the operation of the A3LA-RM because it has no meaning in the Iridium environment.

12.3 EXTENDED COMMANDS
Extended commands perform actions or set parameters that extend the capability of the A3LARM beyond that which is allowed by basic commands. In some cases, they were designed for non-PSTN networks, such as the GSM network.

Most extended commands include a prefix of + followed by a single alpha character. Prefixes used in A3LA-RM extended commands include +C, +D, +G, +I, and +S. Extended commands

Document Number: 451-93156-002C

35 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
designed specifically for Iridium products include a ­MS prefix. Most extended commands include three alpha characters after the prefix, but some commands include just one or two alpha characters after the prefix.
Some extended commands have a single execution mode. No further syntax is added after the prefix and body of the command. For example, AT+GSN is entered as shown to query the A3LARM for its assigned serial number (i.e., IMEI). Some extended commands incorporate a test mode to query their range of valid responses. Some extended commands incorporate set, read, and test modes. For example, AT­MSVTR is entered as AT­MSVTR=n in set mode to enable/disable receipt of DTMF messages. It is entered as AT­MSVTR? in read mode to query its current setting and is entered as AT­MSVTR=? in test mode to query its range of valid settings. Extended commands are grouped as shown below.
Extended Cellular Commands:
 +C prefix  Used for GSM cellular phone-like functions  Standards: ETSI specifications GSM 07.07 [2] and GSM 07.05 [3]
Extended Data Compression Commands:
 +D prefix  Used for data compression  Standard: V.25ter [1]
Extended Generic Commands:
 +G prefix  Used for A3LA-RM issues such as identities and capabilities  Standard: V.25ter [1]
Extended Interface Control Commands:
 +I prefix  Used to control the DTE interface  Standard: V.25ter [1]

Document Number: 451-93156-002C

36 of 172

Extended Short Burst Data Commands:

AL3A-RM/A3LA-RM-MIL User Guide Version C

 +S prefix  Used for SBD messaging

Iridium Satellite Product Proprietary Commands:

 ­MS prefix  Proprietary to the Iridium product line

12.4 COMMAND AND RESPONSE CHARACTERS
The execution of a command string follows a left-to-right execution of each command followed by the reporting of a result code for the entire string. The ASCII character set (CCITT T.50 International Alphabet 5, American Standard Code for Information Interchange) is used for the issuance of commands and responses. Only the low-order 7 bits of each character are used for commands or parameters; the high-order bit is ignored. Uppercase characters are equivalent to lowercase characters.

12.5 COMMAND ENTRY
An AT command is a string of characters sent by the DTE to the A3LA-RM while it is in command mode. A command string has a prefix, a body, and a terminator.

 The prefix consists of the ASCII characters AT or at.  The body is a string of commands restricted to printable ASCII characters.  The default terminator is the <CR> character.

AT command entry syntax is critical, and the following rules apply:

 All commands (apart from A/ and +++) begin with a prefix of AT or at.  The commands in a command string (apart from A/ and +++) are executed only after
the Return or Enter key is pressed.  Use of uppercase or lowercase letters is allowed.  The maximum number of characters in a command string is 128.  If the numeric parameter n is omitted from the basic command entry, a value of zero is
assumed for n.

Document Number: 451-93156-002C

37 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
 If an optional parameter is omitted from an extended command, the current value is implied. Optional parameters are enclosed by square brackets ([...]) in this document.
 Spaces entered into a command string for clarity between the AT prefix and the body of the command are ignored. Likewise, spaces entered for clarity within the command body between alpha characters and decimal parameters are ignored.
 The Backspace or Delete keys can typically be used to edit commands.  Characters that precede the AT prefix are ignored.  Ctrl-x can be used to abort a command line input.
Consider the following six commands to be entered in a single command line:
 ATX0 (set basic command ATXn to n=0)  AT&V (execute basic command AT&V)  AT+GSN (execute extended command AT+GSN)  AT+CMEE=? (query the valid range of responses of extended command AT+CMEE)  AT+CPBR=1,12 (execute extended command AT+CPBR with parameters 1 and 12)  AT­MSVTR? (query the current setting of extended command AT­MSVTR)
The following are valid single command line entries of the above six commands:
 at x 0 &v +gsn +cmee=? +cpbr=1,12 -msvtr? (all lowercase)  AT X 0 &V +GSN +CMEE=? +CPBR=1,12 ­MSVTR? (all uppercase)  ATX 0 &V +GSN +CMEE=? +CPBR=1,12 ­MSVTR? (space omitted between AT and X)  ATX0 &V +GSN +CMEE=? +CPBR=1,12 ­MSVTR? (space omitted between ATX and 0)  ATX &V +GSN +CMEE=? +CPBR=1,12 ­MSVTR? (0 omitted from ATX0)  ATX;&V;+GSN;+CMEE=?;+CPBR=1,12;­MSVTR? (semicolon separators)  ATX&V+GSN+CMEE=?+CPBR=1,12­MSVTR? (no separators)
12.6 COMMAND RESPONSES
A result code is sent to the DTE in response to the execution of a command. It may also occur unsolicited from other conditions, such as an incoming call (e.g., RING). Responses returned as a result of a query are called information responses.

Document Number: 451-93156-002C

38 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Result codes can be represented by text if the A3LA-RM is in verbose mode or with numbers if in numeric mode. The command ATVn informs the A3LA-RM whether to respond in verbose or numeric mode. Responses can be suppressed by setting the command ATQn to ATQ1. Table 4 below shows the difference in format between these modes.

Table 4: Numeric and Verbose Mode Formats

Numeric Mode ATQ0 ATV0

Verbose Mode ATQ0 ATV1

Result codes
Information Responses

<NUMERIC_CODE><CR> <TEXT><CR><LF>

<CR><LF><VERBOSE_CODE><CR><LF> <CR><LF><TEXT><CR><LF>

Command entries with invalid syntax typically respond with ERROR. Command entries of valid syntax with an out-of-range parameter can respond in one of three following manners:

 Disallow out-of-range entry and respond with ERROR.  Disallow out-of-range entry and respond with OK.  Disallow out-of-range entry, accept the closest in-range value, and respond with OK.

12.7 HARDWARE FAILURE REPORTING
If the A3LA-RM detects a hardware problem during initialization, it may be unable to function correctly. The A3LA-RM notifies the DTE of this situation by issuing an unsolicited result code at the end of initialization:

HARDWARE FAILURE: <subsys>,<error>

where <subsys> identifies the software subsystem that detected the error, and <error> is the subsystem-specific error code. Any AT commands that cannot be handled in the failure condition terminate with result code 4 ("ERROR").

Document Number: 451-93156-002C

39 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX B: AT COMMAND SET DESCRIPTION
(IRIDIUM RADIO LINK PROTOCOL) B.1 AT ­ ATTENTION CODE
This is the prefix for all commands except A/ and +++. When entered on its own, the A3LA-RM will respond OK.
B.2 A/ ­ REPEAT LAST COMMAND
Repeat the last command issued to the A3LA-RM unless the power was interrupted or the unit is reset. A/ is not followed by <CR>.
B.3 +++ ­ ESCAPE SEQUENCE
The escape sequence is used to transfer from in-call data mode to in-call command mode without disconnecting from the remote modem. After a pause, the A3LA-RM will respond with OK. Register S2 can be used to alter the escape character from +, the factory default, to any hexadecimal value in the range 0 to 255.
B.4 EN ­ ECHO
Echo command characters. 0 Characters are not echoed to the DTE 1 Characters are echoed to the DTE (default)
B.5 ON ­ ONLINE
Enter in-call data mode. This is used to return to in-call data mode from in-call command mode using an existing connection. An error is reported if on-hook.
0 Switch from in-call command mode to in-call data mode Any value for n accepted
B.6 QN ­ QUIET MODE
Control A3LA-RM responses. 0 A3LA-RM responses are sent to the DTE (default)

Document Number: 451-93156-002C

40 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
1 A3LA-RM responses are NOT sent to the DTE
B.7 VN ­ VERBOSE MODE
Set the response format of the A3LA-RM, which may be either numeric or textual. 0 Numeric responses 1 Textual responses (default)
B.8 WN ­ ERROR CORRECTION MESSAGE CONTROL
Set the format of the CONNECT messages. Upon connection, the A3LA-RM reports the DTE speed (default) Upon connection, the A3LA-RM reports the line speed, the error correction protocol and the DTE speed in that order Upon connection, the A3LA-RM reports its data port speed
B.9 ZN ­ SOFT RESET
Reset the A3LA-RM to a user-stored configuration. Restores user configuration 0 Restores user configuration 1
B.10 &CN ­ DCD OPTION
Select how the A3LA-RM controls the DCD behavior. DCD always indicates the connection status.
No action, compatibility only. Allowed values for n are 0 and 1.
B.11 &DN ­ DTR OPTION
Set the A3LA-RM reaction to DTR signal when auto dialing is disabled (see the ^AD command).
0 DTR is ignored. A DTR signal input is not needed when set to &D0. 1 If DTR transitions from ON to OFF during a data call and is not restored ON
within approximately 10 seconds, the call will be dropped.

Document Number: 451-93156-002C

41 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
2 If DTR transitions from ON to OFF during a data call, the call will be dropped (default).
B.12 &FN ­ RESTORE FACTORY SETTINGS
Recall factory defaults. 0 Recall factory default 0
B.13 &KN ­ FLOW CONTROL
Select the flow control method between the A3LA-RM and DTE. Disables flow control Enables RTS/CTS flow control (default)
B.14 &MN ­ ASYNCHRONOUS/SYNCHRONOUS MODE
Select the DTR operating mode. 0 Selects normal asynchronous operation (default). (See &Qn)
B.15 &QN ­ SYNC/ASYNC MODE
Select asynchronous mode. This is an extension of the &M command and is used to control the connection modes permitted.
Note: The register is not updated right after the user requests new values because the requested values may or may not be what Iridium Radio Link Protocol (IRLP) will use once a data call is established due to negotiations with the other peer. If the register is updated right away, this may give the user the impression that those values will be used during the data call, but there is no guarantee that will be the case. The real values will only be known once a data call is established and the negotiation phase is done. For that reason, the values are written to the register only after a call is established and both sides have negotiated parameter values (such as mode of operation). The value of the register will be reset to default value (5) after the call completed.
0, 6 Normal asynchronous operation with no error correction (unacknowledged mode)

Document Number: 451-93156-002C

42 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
5 Asynchronous operation with error correction (acknowledged mode) (default)

B.16

&SN ­ DSR OVERRIDE
Define the behavior of DSR. DSR always active (default) Same as 0

B.17

&V ­ VIEW ACTIVE AND STORED CONFIGURATION
View the current active configuration and stored profiles.

B.18

&WN ­ STORE ACTIVE CONFIGURATION
Store the active profile in non-volatile memory. This is used to store user configurations for later use.
Store current (active) configuration as profile 0 Store current (active) configuration as profile 1

B.19

&YN ­ DESIGNATE DEFAULT RESET PROFILE
Select profile for use after power-up. Select profile 0 (default) Select profile 1

B.20

\KN ­ CONTROL BREAK
Control the response of the A3LA-RM to a break received from the DTE or the remote modem according to the parameter specified. The response is different in three separate states:
When a break is received from DTE when A3LA-RM is in data transfer mode: Enter in-call command mode, no break sent to remote modem Clear data buffers and send break to remote modem Same as 0 Send break to remote modem immediately Same as 0

Document Number: 451-93156-002C

43 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Send break to remote modem in sequence with transmitted data (default) When a break is received from the remote modem during a non-error corrected connection: Clear data buffers and send break to DTE Same as 0 Send break to DTE immediately Same as 2 Send break to DTE in sequence with received data Same as 4 (default)

B.21

%R ­ DISPLAY REGISTERS
Display all the S registers in the system.

B.22

*PN ­ POWER
Turn A3LA-RM off. 0 Turn A3LA-RM OFF

B.23

+CBST ­ SELECT BEARER SERVICE TYPE
Set Command: +CBST=[<speed>[,<name>[,<ce>]]] Select the bearer service type for mobile originated calls. <speed> can have the following values:
Autobauding 300 bps V.21 1200 bps V.22 2400 bps V.22bis 4800 bps V.32 9600 bps V.32 (default) 300 bps V.110 1200 bps V.110 2400 bps V.110 4800 bps V.110

Document Number: 451-93156-002C

44 of 172

9600 bps V.110 <name> takes the following value:
data circuit asynchronous <ce> can only take the following value:
non-transparent

AL3A-RM/A3LA-RM-MIL User Guide Version C

Read Command: +CBST? Query the current bearer service type settings. Response is in the form:
+CBST: <speed>,<name>,<ce>

Test Command: +CBST=? List the supported <speed>, <name>, <ce>. Response is in the form:
+CBST: (supported <speed>s),(supported <name>s),(supported <ce>s)

B.24

+CGMI ­ MANUFACTURER IDENTIFICATION
Exec Command: +CGMI Query A3LA-RM RF board manufacturer.

B.25

+CGMM ­ MODEL IDENTIFICATION
Exec Command: +CGMM Query A3LA-RM RF board model.

B.26

+CGMR ­ REVISION
Exec Command: +CGMR Query A3LA-RM RF board revision.

B.27

+CGSN ­ SERIAL NUMBER
Exec Command: +CGSN Query A3LA-RM IMEI.

B.28

+CMEE ­ REPORT MOBILE EQUIPMENT ERROR
Set Command: +CMEE=[<x>] Set mobile equipment error reporting level.

Document Number: 451-93156-002C

45 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
<x> takes the following values: Disable error reporting (use ERROR result code) (default) Enable numeric error reporting Enable verbose error reporting
An example of an error report is: +CME ERROR: <y>
where <y> can be the number or text listed below: A3LA-RM RF board failure no connection to A3LA-RM A3LA-RM RF board-adaptor link reserved operation not allowed operation not supported PH-SIM PIN required PH-FSIM PIN required PH-FSIM PUK required SIM not inserted SIM PIN required SIM PUK required SIM failure SIM busy SIM wrong incorrect password SIM PIN2 required SIM PUK2 required memory full invalid index not found memory failure text string too long invalid characters in text string

Document Number: 451-93156-002C

46 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
dial string too long invalid characters in dial string number is SIM fixed dialing restricted no network service network timeout emergency calls only network personalization PIN required network personalization PUK required network subset personalization PIN required network subset personalization PUK required service provider personalization PIN required service provider personalization PUK required corporate personalization PIN required corporate personalization PUK required unknown

Read Command: +CMEE? Query mobile equipment error reporting level. The response is in the form:
+CMEE: <x>

Test Command: +CMEE=? List the supported error reporting level. The response is in the form:
+CMEE: (supported <x>s)

B.29

+CPAS ­ MODEM ACTIVITY STATUS
Exec Command: +CPAS Query A3LA-RM activity status. The response is in the form:
+CPAS: <x> where <x> can take the following values:
Ready (allows commands) Unavailable (does not allow commands) Unknown (may not respond to commands)

Document Number: 451-93156-002C

47 of 172

Data Call Ringing (allows commands) Data Call In Progress (allows commands)

AL3A-RM/A3LA-RM-MIL User Guide Version C

B.30

+CR ­ SERVICE REPORTING CONTROL
Set Command: +CR=[<mode>] Set the service reporting level. <mode> takes the following values:
Disable reporting (default) Enable reporting

If reporting is enabled, the intermediate result code +CR: <serv> is returned by the

A3LA-RM.

<serv> can have one of the following values:

ASYNC

asynchronous transparent

SYNC

synchronous transparent

REL ASYNC asynchronous non-transparent

REL SYNC synchronous non-transparent

Read Command: +CR? Query the current service reporting level settings. The response is in the form:
+CR: <mode>

Test Command: +CR=? List the supported reporting levels. The response is in the form:
+CR: (supported <mode>s)

B.31

+DS ­ SET DATA COMPRESSION FUNCTION
Set Command: +DS=[<direction>[,<comp_neg>[,<max_dict>[,<max_string]]]] Set the V.42bis data compression function. <direction> can take on the following values:
No compression Transmit only Receive only

Document Number: 451-93156-002C

48 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Both directions (default) <comp_neg> can take on the following values:
Do not disconnect if V.42bis is not negotiated by the A3LA-RM as specified in <direction> (default) Disconnect if V.42bis is not negotiated by the A3LA-RM as specified in <direction> <max_dict> can take on the following values: 512 to 2048. Default is 512. <max_string> can take on the following values: 6 to 250. Default is 6.

Read Command: +DS? Query the current data compression parameter settings. The response is in the form:
+DS: <direction>,<comp_neg>,<max_dict>,<max_dict>

Test Command: +DS=? List the supported data compression parameters. The response is in the form:
+DS: (supported<direction>s),(supported<comp_neg>s,(supported <max_dict>s),(supported<max_dict>s)

Data compression will not work if IRLP is in unacknowledged mode.

Note: The register is not updated right after the user requests new values because the requested values may or may not be what IRLP will use once a data call is established due to negotiations with the other peer. If the register is updated right away, this may give the user the impression that those values will be used during the data call, but there is no guarantee that will be the case. The real values will only be known once a data call is established and the negotiation phase is done. For that reason, the values are written to the register only after a call is established and both sides have negotiated parameter values. The value of the register will be reset to default value (3) after the call is completed.

B.32

+DR ­ DATA COMPRESSION REPORT LEVEL

Set Command: +DR=[<mode>] Set the data compression reporting level. <mode> can take on the following values:
Disable data compression reporting (default)

Document Number: 451-93156-002C

49 of 172

Enable data compression reporting

AL3A-RM/A3LA-RM-MIL User Guide Version C

If reporting is enabled, the following intermediate result codes are transmitted by the A3LA-RM:
+DR: NONE No data compression +DR: V42B Data compression in use in both directions +DR: V42B RD Data compression in use in receive direction only +DR: V42B TD Data compression in use in transmit direction only

Read Command: +DR? Query the current reporting level setting. The response is in the form:
+DR: <mode>

Test Command: +DR=? List the supported parameter settings. The response is in the form:
+DR: (supported <mode>s)

B.33

+CEER ­ EXTENDED ERROR REPORT
Exec Command: +CEER Execution command causes the A3LA-RM to return information text <report> which offers the user an extended report of the reason of the failure in the last unsuccessful call setup (originating or answering) or the reason for last call release. The response is in the form:
+CEER: <report>

An example of a <report> is: User alerting, no answer

B.34

+CHUP ­ HANGUP CALL
This command causes the A3LA-RM to hangup the current data call.

Document Number: 451-93156-002C

50 of 172

B.35

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CMGD ­ DELETE SMS MESSAGE
Exec Command: +CMGD=<index> Execution command deletes message from preferred message storage <mem1> (<mem1> is the selected message storage from the +CPMS command) location <index>. If deleting fails, final result code +CMS ERROR: <cms_err> is returned.

An example of an error report is: +CMS ERROR: <cms_err>
where <cms_err> can be one of the numbers below: 1 unassigned number operator barred operation not allowed (identical to 302) call barred SM transfer rejected destination out of service unidentified subscriber facility rejected unknown subscriber network out of order temporary failure congestion resources unavailable facility not subscribed facility not implemented invalid SM reference value invalid message invalid mandatory information element nonexistent message type incompatible message nonexistent information element protocol error

Document Number: 451-93156-002C

51 of 172

interworking telephony interworking not supported SM type 0 not supported cannot replace SM unspecified TP-PID error coding scheme not supported message class not supported unspecified TP-DCS error command not actioned command unsupported TPDU not supported SC busy no SC subscription SC system failure invalid SME address destination SME barred SM rejected SIM SMS storage full no SMS storage capability in SIM error in MS memory capacity exceeded unspecified error A3LA-RM failure SMS service reserved operation not allowed operation not supported invalid PDU mode parameter invalid text mode parameter no SIM SIM PIN required
Document Number: 451-93156-002C

AL3A-RM/A3LA-RM-MIL User Guide Version C 52 of 172

PH-SIM PIN required SIM failure SIM busy SIM wrong memory failure invalid memory index memory full SM-SC address unknown no network service network timeout unknown error

AL3A-RM/A3LA-RM-MIL User Guide Version C

B.36

+CMGF ­ SMS MESSAGE FORMAT
Set Command: +CMGF=[<mode>] Set command tells the A3LA-RM, which input and output format of messages to use. <mode> indicates the format of messages used with send, list, read and write commands and unsolicited result codes resulting from received messages. Mode can be either PDU mode (entire TP data units used) or text mode (headers and body of the messages given as separate parameters). Only PDU mode is supported at this time.

Valid values for <mode> are: PDU mode (default)

Read Command: +CMGF? Read command returns the current <mode> set. Response is in the form:
+CMGF: <mode>

Test Command: +CMGF=? Test command returns the list of supported <mode>s. Response is in the form:
+CMGF: (list of supported <mode>s)

Document Number: 451-93156-002C

53 of 172

B.37

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CMGL ­ LIST SMS MESSAGES
Exec Command: +CMGL[=<stat>] Execution command returns messages with status value <stat> from message storage <mem1> (<mem1> is the selected message storage from the +CPMS command) to the DTE. If listing fails, final result code +CMS ERROR: <cms_err> is returned.

Valid values for <stat> are: PDU Text "REC UNREAD" received unread message (i.e. new message) (default) "REC READ" received read message "STO UNSENT" stored unsent message (only applicable to SMs) "STO SENT" stored sent message (only applicable to SMs) "ALL" all messages (only applicable to +CMGL command)

Response is in the following format for PDU mode: +CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>[<CR><LF>+CMGL:<ind ex>,<stat>,[<alpha>],<length><CR><LF><pdu> [...]]
where: <alpha>: string type alphanumeric representation of TP-destination address or TPoriginating address corresponding to the entry found in the phonebook (optional field);

<length>: in PDU mode, this is the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length)

<pdu>: GSM 04.11 [8] SC address followed by GSM 03.40 [9] TPDU in hexadecimal format.

Test Command: +CMGL=? Test command gives a list of all status values supported by the A3LA-RM. Response is in the form:
+CMGL: (list of supported <stat>s)

Document Number: 451-93156-002C

54 of 172

B.38

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CMGR ­ READ SMS MESSAGE
Exec Command: +CMGR=<index> Execution command returns the SMS message with location value <index> from message storage <mem1> (<mem1> is the selected message storage from the +CPMS command). If status of the message is 'received unread', status in the storage changes to 'received read'. If reading fails, final result code +CMS ERROR: <cms_err> is returned.

Response is in the following format for PDU mode: +CMGR: <stat>,[<alpha>],<length><CR><LF><pdu>
where: <stat>: 0 - MT message unread 1 - MT message read 2 - MO message unsent 3 - MO message sent (When reading an MT message the first time, the status is reported as 0 (unread). The status is then changed to 1 (read), and that is reported on subsequent reads of that message.)

<alpha>:string type alphanumeric representation of TP-destination address or TPoriginating address corresponding to the entry found in the phonebook (optional field);

<length>:in PDU mode, this is the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length)

<pdu>: GSM 04.11 [8] SC address followed by GSM 03.40 [9] TPDU in hexadecimal format.

Document Number: 451-93156-002C

55 of 172

B.39

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CMGS ­ SEND SMS MESSAGE
Exec Command: +CMGS=<length><CR><pdu><ctrl-Z/ESC> (PDU mode) Execution command sends message from the DTE to the network (SMS-SUBMIT). In PDU mode, <length> is the length of the actual TP data unit in octets; <pdu> is the GSM 04.11 [8] SC address followed by GSM 03.40 [9] TPDU in hexadecimal format.

PDU entry must be terminated by <ctrl-Z>. Sending can be cancelled by the <ESC> character.

Response is in the following format for PDU mode: +CMGS: <mr>
where <mr> is the message reference value of the message. If sending fails, final result code +CMS ERROR: <cms_err> is returned.

B.40

+CMGW ­ WRITE SMS MESSAGE TO MEMORY
Exec Command: +CMGW=<length>[,<stat>]<CR><pdu><ctrl-Z/ESC> (PDU mode) Execution command stores a message to memory storage <mem2> (<mem2> is selected by the +CPMS command). In PDU mode, <length> is the length of the actual TP data unit in octets; <pdu> is the GSM 04.11 [8] SC address followed by GSM 03.40 [9] TPDU in hexadecimal format. By default, message status will be set to 'stored unsent', but parameter <stat> allows also other status values to be given.

PDU entry must be terminated by <ctrl-Z>. Storing can be cancelled by sending the <ESC> character.

Response is in the following format for PDU mode: +CMGW: <index>
where <index> indicates the memory location where the message is stored. If storing fails, final result code +CMS ERROR: <cms_err> is returned.

Document Number: 451-93156-002C

56 of 172

B.41

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CMOD ­ CALL MODE
Set Command: +CMOD=[<mode>] Set command selects the call mode of further dialing commands (D) or for next answering command (A). Mode can be either single or alternating (the terms "alternating mode" and "alternating call" refer to all GSM bearer and tele-services that incorporate more than one basic service (voice, data, fax) within one call). For the satellite modem, only a single call is supported. <mode>:
single mode (default)

Read Command: +CMOD? Query the current call mode settings. The response is in the form:
+CMOD: <mode>

Test Command: +CMOD=? List the supported call modes. The response is in the form:
+CMOD: (supported <mode>s)

B.42

+CNMI ­ NEW SMS MESSAGE INDICATIONS TO DTE
Set Command: +CNMI=[<mode>[,<mt>[,<bm>[,<ds>[, <bfr>]]]]] Set command selects the procedure, how receiving of new messages from the network is indicated to the DTE when DTE is active, e.g. DTR signal is ON.

Valid values for <mode> are: Buffer unsolicited result codes in the A3LA-RM. If result code buffer is full, older indications are discarded and replaced with the new received indications. (default) Discard indication and reject new received message unsolicited result codes when A3LA-RM-DTE link is reserved (e.g. in in-call data mode). Otherwise forward them directly to the DTE. Buffer unsolicited result codes in the A3LA-RM when A3LA-RM-DTE link is reserved (e.g. in in-call data mode) and flush them to the DTE after reservation. Otherwise forward them directly to the DTE.

Document Number: 451-93156-002C

57 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Valid values for <mt> are: No SMS-DELIVER indications are routed to the DTE. (default) If SMS-DELIVER is stored in the A3LA-RM, indication of the memory location is routed to the DTE using unsolicited result code: +CMTI: <mem>,<index> SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code: +CMT: [<alpha>],<length><CR><LF><pdu> (PDU mode) Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in <mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1.
Valid values for <bm> are: No CBM indications are routed to the DTE. (default)
Valid values for <ds> are: No SMS-STATUS-REPORTs are routed to the DTE. (default) SMS-STATUS-REPORTs are routed to the DTE using unsolicited result code: +CDS: <length><CR><LF><pdu> (PDU mode)
Valid values for <bfr> are: 0 Buffer of unsolicited result codes defined within this command is flushed to the DTE when <mode> 1...3 is entered (OK response is returned before flushing the codes). (default) 1 Buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered.
Read Command: +CNMI? Read command returns the current settings for the SMS message indication. Response is in the form:
+CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>
Test Command: +CNMI=?

Document Number: 451-93156-002C

58 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Test command returns the supported settings of the A3LA-RM. Response is in the form:
+CNMI: (list of supported <mode>s),(list of supported <mt>s),(list of supported <bm>s),(list of supported <ds>s),(list of supported <bfr>s)

B.43

+COPS ­ OPERATOR SELECT
Set Command: +COPS=[<mode>[,<format>[,<oper>]]] Set command forces an attempt to manually register the A3LA-RM to the network. Only IRIDIUM as <oper> is supported. Valid values for the parameters are outlined below. <mode>:
automatic (<oper> field is ignored) (default) manual (<oper> field is optional) <format>: long format alphanumeric <oper> short format alphanumeric <oper> numeric <oper> <oper> is of string type enclosed by quotes""; for example "IRIDIUM". <format> indicates if the format is alphanumeric or numeric; long alphanumeric format can be up to 16 characters long and short format up to 8 characters; numeric format is the Location Area Identification number which consists of a three BCD (Binary Coded Decimal) digit country code plus a two BCD digit network code; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 2)(network code digit 1). Since IRIDIUM is the only operator, the short and long format is "IRIDIUM" and the numeric format is "90103". These are the only values accepted.

Note that setting the <mode> to manual does not disable automatic registration of the A3LA-RM to the network. It just forces a manual registration procedure when entered.

Read Command: +COPS?

Document Number: 451-93156-002C

59 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read command returns the current mode, and will always respond with "000" for <mode>. This is due to the continually enabled nature of the automatic registration mode. The response is in the form:
+COPS: <mode> For example:
+COPS:000
Test Command: +COPS=? Test command returns the list of operators present in the network. Response is in the form:
+COPS: [list of supported (<stat>,long alphanumeric <oper>,short alphanumeric <oper>,numeric <oper>)s] [,,(list of supported <mode>s),(list of supported <format>s)] where <stat> indicates: 2 current For example: +COPS:(002),"IRIDIUM","IRIDIUM","90103",,(000-001),(000-002)

B.44

+CPBF ­ FIND PHONEBOOK ENTRIES
Exec Command: +CPBF=<findtext> Execution command returns phonebook entries (from the current phonebook memory storage selected with +CPBS) which alphanumeric fields start with string <findtext>. <findtext> should be of string type enclosed by ""; for example, "John".

Entry fields returned are location number <index n>, phone number stored there <number> (of address type <type>), and text <text> associated with the number. Response is in the following format:
+CPBF: <index1>,<number>,<type>,<text>[[...]<CR><LF>+CBPF: <index2>,<number>,<type>,<text>]

Test Command: +CPBF=? Test command returns the maximum lengths of <number> and <text> fields for phonebook entries. Response is in the form:

Document Number: 451-93156-002C

60 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CPBF: <nlength>,<tlength> where <nlength> indicates the maximum length of <number> and <tlength> shows the maximum length of <text>.

B.45

+CPBR ­ READ PHONEBOOK ENTRIES
Exec Command: +CPBR=<index1>[,<index2>] Execution command returns phonebook entries in location number range <index1>... <index2> from the current phonebook memory storage selected with +CPBS. If <index2> is left out, only location <index1> is returned.

Entry fields returned are location number <index n>, phone number stored there <number> (of address type <type>) and text <text> associated with the number. Response is in the form:
+CPBR: <index1>,<number>,<type>,<text>[[...] <CR><LF>+CPBR: <index2>,<number>,<type>,<text>]

Test Command: +CPBR=? Test command returns location range supported by the current storage and the maximum lengths of <number> and <text> fields. Response is in the form:
+CPBR: (list of supported <index>s),<nlength>,<tlength> where <nlength> indicates the maximum length of <number> and <tlength> shows the maximum length of <text>.

B.46

+CPBS ­ SELECT PHONEBOOK STORAGE

Set Command: +CPBS=<storage>

Set command selects phonebook memory storage <storage>, which is used by other

phonebook commands. <storage> should be of string type enclosed by ""; for

example, "FD". <storage> takes the following values:

FD SIM fixed dialing phonebook

LD Last ten calls dialed phonebook

ME A3LA-RM phonebook

MT combined A3LA-RM and SIM phonebook (default)

SM SIM phonebook

Document Number: 451-93156-002C

61 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: +CPBS? Read command returns currently selected memory, the number of used locations and total number of locations in the memory. Response is in the form:
+CPBS: <storage>,<used>,<total> where <used> indicates the number of used locations and <total> shows the total capacity of <storage>.

Test Command: +CPBS=? Test command returns supported storages.

B.47

+CPBW ­ WRITE PHONEBOOK ENTRY
Exec Command: +CPBW=[<index>][,<number>[,<type>[<text>]]] Execution command writes phonebook entry in location number <index> in the current phonebook memory storage selected with +CPBS. Entry fields written are phone number <number> (of address type <type>) and text <text> associated with the number. If those fields are omitted, phonebook entry is deleted. If <index> is left out, but <number> is given, entry is written to the first free location in the phonebook. Both <text> and <number> should be of string type enclosed by ""; for example, "John","1234".

Test Command: +CPBW=? Test command returns the location range supported by the current storage, the maximum length of <number> field, supported number formats of the storage, and the maximum length of <text> field. Response is in form:
+CPBW: (list of supported <index>s),<nlength>,(list of supported <type>s),<tlength>

Document Number: 451-93156-002C

62 of 172

B.48

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CPIN ­ ENTER PIN
Set Command: +CPIN=<pin>[,<newpin>] Set command sends to the A3LA-RM a password which is necessary before it can be operated (SIM Card PIN Code, SIM PUK, etc.). If no password request is pending, no action is taken by the A3LA-RM. If the password required is SIM PUK, then <newpin> is required, where <newpin> is the new SIM Card PIN to replace the old SIM Card PIN. If the password required is SIM PUK2, then <newpin> is required, where <newpin> is the new SIM Card PIN2 to replace the old SIM Card PIN2 Both <pin> and <newpin> should be of string type enclosed by " "; for example, "1234".

Read Command: +CPIN?

Read command returns an alphanumeric string indicating whether some password is

required or not. Response is in the form:

+CPIN: <code>

where <code> can be one of the following:

READY

A3LA-RM is not waiting for any password.

PH PIN

A3LA-RM is waiting for Phone Unlock Code to be given.

SIM PIN

A3LA-RM is waiting for SIM Card PIN1 Code to be given.

SIM PUK A3LA-RM is waiting for SIM PUK to be given (because SIM PIN1 is

blocked).

SIM PIN2 A3LA-RM is waiting for SIM PIN2 to be given.*

SIM PUK2 A3LA-RM is waiting for SIM PUK2 to be given (because SIM PIN2 is

blocked).

*Note: The response "SIM PIN2" is somewhat misleading, because it indicates one of three possible scenarios: 1. PIN1 has already been successfully entered (thus equivalent to the READY
response). 2. No PIN1 is required (thus equivalent to the READY response).

Document Number: 451-93156-002C

63 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
3. The A3LA-RM is waiting for PIN2 (used to access Fixed Dialing settings and other subscription-based features).

In any of these three cases, the A3LA-RM should be available to place and receive calls.

Note: +CPIN is closely related to +CLCK and +CPWD. See these commands for additional information.

B.49

+CPMS ­ SELECT PREFERRED SMS MESSAGE STORAGE
Set Command: +CPMS=<mem1>[, <mem2>[,<mem3>]] Set command selects memory storages <mem1>, <mem2> and <mem3>. <mem1> is the memory from which messages are read and deleted; <mem2> is the memory to which writing and sending operations are made; <mem3> is the memory to which received SMS messages are to be stored. If a chosen storage is not appropriate for the A3LA-RM, final result code +CMS ERROR: <cms_err> is returned.

Valid values for <mem1>, <mem2> and <mem3> are: "SM" SIM message storage

Response is in the form: +CPMS: <used1>,<total1>,<used2>,<total2>,<used3>,<total3>
where <used1>: number of messages currently in <mem1> <total1>: total number of message locations in <mem1> <used2>: number of messages currently in <mem2> <total2>: total number of message locations in <mem2> <used3>: number of messages currently in <mem3> <total3>: total number of message locations in <mem3>

Read Command: +CPMS? Read command returns the current storage selected, usage and capacity. Response is in the form:

Document Number: 451-93156-002C

64 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CPMS: <mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>,<mem3>,<used3>, <total3>

Test Command: +CPMS=? Test command returns lists of memory storages supported by the A3LA-RM. Response is in the form:
+CPMS: (list of supported <mem1>s),(list of supported <mem2>s), (list of supported <mem3>s)

B.50

+CREG ­ NETWORK REGISTRATION
Set Command: +CREG=[<n>] Set command controls the presentation of an unsolicited result code +CREG: <stat> when <n>=1 and there is a change in the A3LA-RM network registration status, or code +CREG: <stat>[,<lac>,<ci>] when <n>=2 and there is a change in the registration status of the A3LA-RM.

Valid values for <n> are: disable network registration unsolicited result code (default) enable network registration unsolicited result code +CREG: <stat> enable network registration and location information unsolicited result code +CREG: <stat>[,<lac>,<ci>]. <lac> indicates the location area code in string format; <ci> is in the cell identifier which is not applicable to IRIDIUM.

<stat> can be one of the following: not registered, A3LA-RM is not currently searching a new operator to register to registered, home network not registered, but A3LA-RM is currently searching a new operator to register to registration denied unknown registered, roaming

Read Command: +CREG?

Document Number: 451-93156-002C

65 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read command returns the status of result code presentation and an integer <stat> which shows the network registration status of the A3LA-RM. Location information elements <lac> and <ci> are returned only when <n>=2 and A3LA-RM is registered in the network. Response is in the form:
+CREG: <n>,<stat>[,<lac>,<ci>]

Test Command: +CREG=? Test command lists the supported settings for +CREG. Response is in the form:
+CREG: (list of supported <n>s)

B.51

+CSCA ­ SMS SERVICE CENTER ADDRESS
Set Command: +CSCA=<sca>[,<tosca>] Set command updates the SMSC address, through which mobile originated SMs are transmitted. In PDU mode, setting is used by the send and write commands, but only when the length of the SMSC address coded into <pdu> parameter equals zero.

<sca>: GSM 04.11 [8] RP SC address Address-Value field in string format (i.e., enclosed by quotes "");

<tosca>: GSM 04.11 [8] RP SC address Type-of-Address octet in integer format;

Read Command: +CSCA? Read command returns the current service center address. Response is in the form:
+CSCA: <sca>,<tosca>

B.52

+CSCB ­ SELECT CELL BROADCAST MESSAGE TYPES
Read Command: +CSCB? Read command returns the current values for <mode>, <mids> and <dcss>. Response is in the form:
+CSCB: <mode>,<mids>,<dcss>

Test Command: +CSCB=? Test command returns supported modes. Response is in the form:
+CSCB: (list of supported <mode>s)

Document Number: 451-93156-002C

66 of 172

B.53

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CSCS ­ SELECT TE CHARACTER SET
Set Command: +CSCS=[<chset>] Set command informs the A3LA-RM which character set <chset> is used by the DTE. Only the IRA character set is currently supported. <chset> should be of string type enclosed by ""; for example, "IRA".

Valid values for <chset> are: "IRA" international reference alphabet (ITU-T T.50)

Read Command: +CSCS? Read command returns the current character set used. Response is in the form:
+CSCS: <chset>

Test Command: +CSCS=? Test command returns the supported character set of the A3LA-RM. Response is in the form:
+CSCS: (list of supported <chset>s)

B.54

+CSMS ­ SELECT SMS MESSAGE SERVICE
Set Command: +CSMS=<service> Set command selects short messaging service <service>. It returns the types of messages supported by the A3LA-RM: <mt> for mobile terminated messages, <mo> for mobile originated messages and <bm> for broadcast type messages. If chosen service is not supported, final result code +CMS ERROR:<cms_err> shall be returned. Only message service type 0 is currently supported.

Valid values for <service> are: 0 GSM 03.40 [9] and 03.41 [10] (the syntax of SMS AT commands is compatible with GSM 07.05 [3] Phase 2 version 4.7.0) (default)

Response is in the form: +CSMS: <mt>,<mo>,<bm>
where, <mt>, <mo>, <bm>: type not supported type supported

Document Number: 451-93156-002C

67 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: +CSMS? Read command returns the current message service type set. Response is in the form:
+CSMS: <service>,<mt>,<mo>,<bm>

Test Command: +CSMS=? Test command returns the supported message services of the A3LA-RM. Response is in the form:
+CSMS: (list of supported <service>s)

B.55

+CSTA ­ SELECT TYPE OF ADDRESS
Set Command: +CSTA=[<type>] Select the type of number for the dial command D. <type> is the type of address in integer format specified in GSM 4.08 subclause 10.5.4.7. Typical values for <type> are:
129 Unknown type (default) 145 International number

Read Command: +CSTA? Query the current address type settings. The response is in the form:
+CSTA: <type>

Test Command: +CSTA=? List the supported address type settings. The response is in the form:
+CSTA: (supported <type>s)

B.56

+GMI ­ MANUFACTURER IDENTIFICATION
Exec Command: +GMI Query the A3LA-RM RF board manufacturer. This command is similar to +CGMI.

B.57

+GMM ­ MODEL IDENTIFICATION
Exec Command: +GMM Query the A3LA-RM RF board model. This command is similar to +CGMM.

Document Number: 451-93156-002C

68 of 172

B.58

AL3A-RM/A3LA-RM-MIL User Guide Version C
+GMR ­ REVISION
Exec Command: +GMR Query the A3LA-RM RF board revision. This command is similar to +CGMR.

B.59

+GSN ­ SERIAL NUMBER
Exec Command: +GSN Query the A3LA-RM IMEI. This command is similar to +CGSN.

B.60

+GCAP ­ GENERAL CAPABILITIES
Exec Command: +GCAP Query the A3LA-RM' overall capabilities.

B.60.1 A ­ ANSWER
Answer immediately. This causes the A3LA-RM to answer the incoming data or voice call.

B.62

D ­ DIAL

Dial a data or voice call number. The dial command causes the A3LA-RM to enter

originate mode and act as an auto dialer for connection to other modems or voice

lines. The usual format is ATDnx..x where n is a Dial Modifier and x is a number. The following are valid numbers: 0123456789*#ABC. Dial modifiers are used to alter the

manner in which the A3LA-RM dials.

L Redial last number

+ International dialing prefix. Allows the international access code to be

omitted from dial string.

> Direct dial from phonebook locations. See subsection below for further

details.

;

Start up a voice call. This modifier should be given after the dialing digits

(or modifiers).

Any character received from the DTE during the call establishment phase will cause the call attempted to be terminated.

Document Number: 451-93156-002C

69 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.62.1 D> ­ DIRECT DIAL FROM PHONEBOOK
The A3LA-RM and SIM contain phonebooks which have a phone number and an alphanumeric field for each phonebook entry location. The use of V.25ter dialing command ensures that direct dialing from phone memory and SIM phonebook is possible through ordinary communications software which just gives the phone number field to be filled and then uses the D command to originate the call. Available memories may be queried with Select Phonebook Storage test command +CPBS=?, and location range for example with Read Phonebook Entries test command +CPBR=?.

Execute commands: D><str>[;] Originate call to phone number which corresponding alphanumeric field is <str> (if possible, all available memories should be searched for the correct entry). <str> is of string type value and should enclosed by "" (e.g., "John").

D> mem<n>[;] Originate call to phone number in memory mem entry location <n> (available memories may be queried with Select Phonebook Storage test command +CPBS=?). mem can be one of the following:
FD SIM fixed dialing phonebook LD Last ten calls dialed phonebook ME Phone memory MT combined phone and SIM phonebook locations SM SIM phonebook

D><n>[;] Originate call to phone number in entry location <n> (the command Select Phonebook Memory Storage +CPBS setting determines which phonebook storage is used).

B.63

HN ­ HANGUP
Control the hook switch. This command is used to clear a data call connection. It is also used to clear a voice call connection when the A3LA-R/RM/RGS has originated the voice call with the ATD dial command or terminated the voice call with the ATA or ATS0=n answer command.

Document Number: 451-93156-002C

70 of 172

0 Place the A3LA-RM on hook.

AL3A-RM/A3LA-RM-MIL User Guide Version C

B.64

S0=N ­ AUTO-ANSWER
Auto-answer. This causes the A3LA-RM to auto-answer the incoming data or voice call.
Disable auto-answer. n>0 Enable auto-answer after n rings

B.65

XN ­ EXTENDED RESULT CODES
Select the response set to be used by the A3LA-RM when informing the DTE of the results of a command or data or voice call.
0 OK, CONNECT, RING, NO CARRIER, NO ANSWER and ERROR CONNECT response is used to inform of a data call connection; OK response is used to inform of a voice call connection (only for A3LAR/RM/RGS).
1 As X0 plus CONNECT x, where x is the DTE speed CONNECT x response is used for data calls only.
2 As X1 plus NO DIALTONE 3 As X2 plus BUSY 4 As X3 plus CARRIER x, PROTOCOL: and COMPRESSION:, where x is the line
speed (default) CARRIER x, PROTOCOL:, and COMPRESSION: responses are used for data calls only.

Note that the Wn command limits which connection related responses will be reported.

B.66

+CLVL ­ VOLUME LEVEL CONTROL
Exec Command: +CLVL=<level> This command is used to select the `volume' of the audio on the audio path. <level> is an integer type value with the smallest value representing the lowest sound level.

Document Number: 451-93156-002C

71 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: +CLVL? Query the current volume level settings. The response is in the form:
+CLVL: <level> 0 Equivalent to level 0 displayed on a handset's volume indicator 1 Equivalent to level 1 displayed on a handset's volume indicator 2 Equivalent to level 2 displayed on a handset's volume indicator 3 Equivalent to level 3 displayed on a handset's volume indicator 4 Equivalent to level 4 displayed on a handset's volume indicator 5 Equivalent to level 5 displayed on a handset's volume indicator 6 Equivalent to level 6 displayed on a handset's volume indicator 7 Equivalent to level 7 displayed on a handset's volume indicator

Test Command: +CLVL=? List the supported volume level settings. The response is in the form:
+CLVL: (supported <level>s)

B.67

+CMUT ­ MUTE CONTROL
Exec Command: +CMUT=<n> This command is used to enable and disable the uplink voice muting during a voice call. <n> can take one of the following values:
0 mute off 1 mute on

Read Command: +CMUT? Query the current mute setting. The response is in the form:
+CMUT: <n>

Test Command: +CMUT=? List the supported mute settings. The response is in the form:
+CMUT: (supported <n>s)

Document Number: 451-93156-002C

72 of 172

B.68

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CRC ­ CELLULAR RESULT CODES
ExecSet Command: +CRC=[<mode>] Set the extended format of incoming data or voice call indication. <mode> takes the following values:
0 Disable extended format (default) 1 Enable extended format

If extended format is enabled, the unsolicited result code +CRING: <type> is returned

by the A3LA-RM instead of RING, where <type> can be one of the following:

ASYNC

asynchronous transparent

SYNC

synchronous transparent

REL ASYNC asynchronous non-transparent

REL SYNC synchronous non-transparent

FAX

facsimile

VOICE

normal voice

Read Command: +CRC? Query the current result code settings. The response is in the form:
+CR: <mode>

Test Command: +CRC=? List the supported result code settings. The response is in the form:
+CR: (supported <mode>s)

B.69

+CVHU ­ VOICE HANGUP CONTROL
Set Command: +CVHU=[<mode>] Selects whether the Hn (hangup) command shall cause a voice call connection to be disconnected or not. <mode> can take one of the following values:
0 Disconnect as reaction to Hn command. OK response given. 1 Ignore Hn command. OK response given. 2 Disconnect as reaction to Hn command (default).

Read Command: +CVHU?

Document Number: 451-93156-002C

73 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Query the current voice control hangup settings. The response is in the form: +CVHU: <mode>

Test Command: +CVHU=? List the supported voice control hangup settings. The response is in the form:
+CVHU: (supported <mode>s)

B.70

+CCLK ­ REAL-TIME CLOCK
Set Command: +CCLK=[<time>] Sets the real-time clock of the A3LA-RM. If setting fails, ERROR is returned. <time>: string type value; format is "yy/MM/dd,hh:mm:ss zz", where characters indicate year two last digits), month, day, hour, minutes, seconds and time zone. There is no blank space between the two double quotes. Since time zone feature is not supported in Iridium, this particular field ( zz) is ignored if it is entered. The range of valid years is between 1970 and 2058.

For example, May 15, 2011, 22:10:00 hours can be set using +CCLK= "11/05/15,22:10:00".

Read Command: +CCLK? Read command returns the current setting of the clock.
+CCLK: <time>

B.71 ­MSVTS ­ DTMF GENERATION IN VOICE CALL
Set Command: ­MSVTS=<string> Generate the specified DTMF tone (i.e., send tone DTMF message to network). The parameter <string> shall consist of elements in a list where each element is separated by a comma. Each element should either be (1) a single ASCII character; or (2) string that follows the format: <tone>[,<time>] with each string enclosed in square brackets "[]". The string parameter values are defined as follows:
<tone> specifies the string of tones to be played or generated. The valid values are (in ASCII): `0'-'9', `#', `*'

Document Number: 451-93156-002C

74 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
<time> specifies the duration of each tone in 180-millisecond unit. Default value is 1 for 180 ms.
For example, the command string ­MSVTS=1,[9,2],[5,3] will: 1. Generate DTMF 1 with a duration of 180 ms (default) 2. Generate DTMF 9 with a duration of 360 ms (2 * 180 ms) 3. Generate DTMF 5 with a duration of 540 ms (3 * 180 ms)
Test Command: ­MSVTS=? List the supported parameter settings. The response is in the form:
­MSVTS: (supported <tone>s),(supported <time>s)
Note: DTMF generated with the ­MSVTS command is never played back locally as tones and is therefore neither played nor muted under control of the ­MSVLS command.
B.72 ­MSVTR ­ DTMF RECEIVED IN VOICE CALL
Set Command: ­MSVTR=[<mode>] Disable or enable the receiving of DTMF messages from the network. <mode> takes one of the following values:
0 Receiving of DTMF disabled (default) 1 Receiving of DTMF enabled
If receiving DTMF is enabled, the A3LA-R/RM/RGS sends the following unsolicited result code every time a DTMF inband signaling data is received from the network while in a voice call:
­MSTRX: <tone>,<event> where <tone> is the DTMF tone received (`0'-'9', `#', `*', `A'-'D') and <event> can be one of the following:
0 tone stopped (i.e. key released) 1 tone started (i.e. key pressed)
Read Command: ­MSVTR? Query the current parameter settings. The response is in the form:

Document Number: 451-93156-002C

75 of 172

­MSVTR: <mode>

AL3A-RM/A3LA-RM-MIL User Guide Version C

Test Command: ­MSVTR=? List the supported parameter settings. The response is in the form:
­MSVTR: (supported <mode>s)

B.73 ­MSVLS ­ LOCAL DTMF FEEDBACK SELECTION
Set Command: ­MSVLS=[<mode>] Disable or enable playing of DTMF tones locally (i.e. feedback tones) while in a voice call. <mode> takes one of the following values:
0 No mute. Play all DTMF tones (default) when pressed or received while in voice call.
1 Enable mute mode. Mute both pressed or received DTMF tones while in voice call.

Read Command: ­MSVLS? Query the current parameter settings. The response is in the form: ­MSVLS: <mode>

Test Command: ­MSVLS=? List the supported parameter settings. The response is in the form:
­MSVLS: (supported <mode>s)
Note: DTMF generated with the ­MSVTS command is never played back locally as tones and is therefore neither played nor muted under control of the ­MSVLS command.

B.74 ­MSSTM ­ REQUEST SYSTEM TIME
Exec Command: ­MSSTM Query the latest system time received from the network. The response is the form:
­MSSTM: <system_time>

<system_time> can take one of the following forms: no network service The A3LA-RM has not yet received system time from the network.

Document Number: 451-93156-002C

76 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
XXXXXXX Where XXXXXXXX is the current Iridium system time available from the network. The system time as received through the Iridium Air Interface, is a 32 bit integer count of the number of 90 millisecond intervals that have elapsed since the epoch. The return value is formatted as an ASCII hexadecimal number. The counter will rollover approximately every 12 years or be changed to prevent a rollover and as a result should not be used as a time source for user applications.
Iridium system time epoch: March 8, 2007, 03:50:21.00 GMT. (Note: the original Iridium system time epoch was June 1, 1996, 00:00:11 GMT, and was reset to the new epoch in January, 2008).
Iridium system time source: The system time is available and valid only after the A3LARM has registered with the network and has received the Iridium system time from the network. Once the time is received, the A3LA-RM 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 A3LA-RM will obtain a new system time from the network. Time localization: None. The system time value is always expressed in GMT time. 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 this message is sent out of the A3LA-RM' serial port should not exceed 4 frame ticks (.36 seconds) and in most cases will be one frame tick (.09 seconds) or less.
B.75 ­MSGEO ­ REQUEST GEOLOCATION
Exec Command: ­MSGEO Query the geolocation grid code received from the network in the last Access Decision Notification message. The response is of the form:
­MSGEO: <x>,<y>,<z>,<time_stamp> <x>, <y>, <z> is a geolocation grid code from an earth centered Cartesian coordinate system, using dimensions, x, y, and z, to specify location. The coordinate system is aligned such that the z-axis is aligned with the north and south poles, leaving the xaxis and y-axis to lie in the plane containing the equator. The axes are aligned such

Document Number: 451-93156-002C

77 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
that at 0 degrees latitude and 0 degrees longitude, both y and z are zero and x is positive (x = +6376, representing the nominal earth radius in kilometers). Each dimension of the geolocation grid code is displayed in decimal form using units of kilometers. Each dimension of the geolocation grid code has a minimum value of ­ 6376, a maximum value of +6376, and a resolution of 4. <time_stamp> is assigned by the A3LA-RM when the geolocation grid code received from the network is stored to the A3LA-RM internal memory. Current Iridium system time, which is a running count of 90 millisecond intervals, is used for the time stamp. Time stamp is a 32-bit integer displayed in hexadecimal form.
B.76 +CCFC ­ CALL FORWARD SERVICE
Exec Command: +CCFC=<reason>,<mode>[,<number>[,<type>[,class>[,<subaddr>[,<satype>[,<time >]]]]]] This command is based on GSM 07.07 [2] subclause 7.10, and allows control of the call forwarding supplementary service according to GSM 02.82 [11]. Registration, erasure and status query are supported. The valid values for the parameters are as follows: <reason> takes one of the following values:
0 unconditional 1 mobile busy 2 no reply 3 not reachable 4 all call forwarding (refer GSM 02.30 [5]) 5 all conditional call forwarding (refer GSM 02.30 [5])
<mode> takes one of the following values: 0 disable (not used in Call Forward) 1 enable (not used in Call Forward) 2 query status 3 registration

Document Number: 451-93156-002C

78 of 172

4 erasure

AL3A-RM/A3LA-RM-MIL User Guide Version C

<number>:quoted string type phone number of forwarding address. It contains digits only, or empty string if not applicable.

<type>: type of address octet in integer format (refer to GSM 04.08 [7] subclause 10.5.4.7); default 145 when dialing string is international number, otherwise 129

<classx>: is a sum of integers each representing a class of information: 1 voice (telephony) 2 data

<subaddr>:

string type sub-address, not supported by Iridium

<satype>: type of sub-address, not supported by Iridium

<time>: string containing number of seconds (up to 30, in multiples of 5). When `no reply' is enabled or queried, this gives the time in seconds to wait before call is forwarded.

if <mode>=2 and command is successful, the A3LA-RM returns a response in the form: +CCFC:<status>,<class>[,<number>,<type>]
where <status> may be as follows: not active active
For example: +CCFC:0,1 +CCFC:1,1,"+441223420024",145 +CCFC:2,3,"00881662990000",,1,,,"30"

Test Command: +CCFC=? List supported <reason>s. The response is in the form of a range rather than a list:
+CCFC:(000-005)

Document Number: 451-93156-002C

79 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.77 +CLCC ­ REQUEST CURRENT CALL STATUS
Exec Command: +CLCC Returns the current call status of the A3LA-RM. The response is a comma separated list of call states. The number of call states in the response depends on the number of active call instances e.g. incoming calls and held calls.
+CLCC: <stat>[,<stat>[,<stat>]] where <stat> (State of the A3LA-RM):
000 Active 001 Call Held 002 Dialing (MO Call) 004 Incoming (MT Call) 006 Idle
Note: the form of this announcement currently differs from the standard given in 3GPP TS 27.007 [12] subclause 7.18. A change to the interface may be made to become more standard.
B.78 +CNUM ­ READ MSISDN NUMBERS
Exec Command: +CNUM Get the MSISDN numbers of the SIM. If returning fails, ERROR is returned. Response is in the form:
+CNUM:<text>,<number>,<type> <text>: alpha tag of the phone numbers <number>: MSISDN numbers <type>: if the number starts with a `+', then the type is 145; otherwise the type is 129
Note: MSISDN numbers are only available if they were intentionally stored on the SIM.
B.79 +CSSSC ­ SUPPLEMENTARY SERVICES SHORTCODE
Exec Command: +CSSSC="<shortcode>" Execute the given shortcode. If the shortcode fails, a CME ERROR code is returned. Otherwise, OK is returned.

Document Number: 451-93156-002C

80 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Note: Shortcode functionality is only available if provisioned.

Note: This command does not support command concatenation.

B.80 +WIRLP ­ IRIDIUM RADIO LINK PROTOCOL
Set Command: +WIRLP=[<ver>[,<k1>[,<k2>[,<t1>[,<n2>[,<t2>[,<r1>[,<r2>[,<t4>[,<mode>]]]]]]]]]] Set desired IRLP parameters to be negotiated with the peer at the start of the next data call. Note that these desired parameters are reset to hardcoded defaults at the end of a data call, so this command should be issued while a call is not in progress.

<ver> specifies the desired IRLP version and can take the following values: 0 Default IRLP version (N0)

<k1> represents the maximum number of sequentially numbered I frames that may be outstanding at any given time at downlink direction (IWF->A3LA-RM) and can take the following values:
1-105. Default is 105.

<k2> represents the maximum number of sequentially numbered I frames that may be outstanding at any given time at uplink direction (A3LA-RM->IWF) and can take the following values:
1-105. Default is 105.

<t1> is used to supervise the acknowledgment of transmitted unnumbered frames.

The values are defined to be the earliest instant to enter the recovery procedure and

can take on the following values:

27-255 (in 50-ms unit).

Default is 30.

<n2> is used to represent the maximum number of re-transmission attempts of a frame (e.g. I,S,N,U frame) and can take on the following values:
1-255. Default is 15.

<t2> is used to indicate the amount of time available within which the acknowledging frame must be transmitted and can take on the following values:
1-255 (in 10-ms unit). Default is 10.

Document Number: 451-93156-002C

81 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
<r1> is used to represent the maximum number of S frames that are used to acknowledge I frames at downlink direction (IWF->A3LA-RM) and can take on the following values:
1-10. Default is 10.

<r2> is used to represent the maximum number of S frames that are used to acknowledge I frames at uplink direction (A3LA-RM->IWF) and can take on the following values:
1-10. Default is 10.

<t4> is used to supervise the re-sequencing of misordered frames. The values are

defined to be the earliest instant to consider a tardy frame as lost. It can take on the

following values:

20-255 (in 10-ms unit).

Default is 25.

<mode> is used to indicate the mode of operation and can take on the following values:
0 unacknowledged mode of operation 1 acknowledged mode of operation (default)

NOTE: For the proper operation of the IRLP procedures, t2 should be less than t1 and 2*t4 should be less than t1.

Read Command: +WIRLP? Query the actual IRLP parameters resulting from the negotiation (XID exchange) at the start of the most recent data call. Note that these may differ from the desired parameters set using "+WIRLP=..."; from power-up they are set to hardcoded defaults, and will only change as the result of the negotiation. The response is in the form:
+WIRLP: <ver>, <k1>, <k2>, <t1>, <n2>, <t2>, <r1>, <r2>, <t4>, <mode>

Test Command: +WIRLP=? List the supported IRLP parameter settings. The response is in the form:
+WIRLP: (supported <ver>s), (supported <k1>s), (supported <k2>s), (supported <t1>s),

Document Number: 451-93156-002C

82 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
(supported <n2>s), (supported <t2>s), (supported <r1>s), (supported <r2s), (supported <t4>s), (supported <mode>s)
B.81 +WFRNG ­ FORCE IRLP RENEGOTIATION
Set Command: +WFRNG=<frng> Set forced renegotiation of IRLP parameters. <frng> can take the following values:
Do not renegotiate (default) Renegotiate Disconnect
Read Command: +WFRNG? Query the current parameter setting. The response is in the form:
+WFRNG: <frng>
Test Command: +WFRNG=? List the supported parameter settings. The response is in the form:
+WFRNG: (supported <frng>s)
B.82 +WTM ­ IRLP TEST MODE
Set Command: +WTM=<tm> Select DCE mode of operation. <tm> can take the following values:
0 IRLP test mode off (default) 1 IRLP test mode on
Read Command: +WTM? Query the current parameter setting. The response is in the form:
+WTM: <tm>
Test Command: +WTM=? List the supported parameter settings. The response is in the form:
+WTM: (supported <tm>s)

Document Number: 451-93156-002C

83 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.83 +WDLDM ­ IRLP DYNAMIC LINK DELAY MEASUREMENT
Set Command: +WDLDM=[<dldm>[,<mi>[,<dtl>]]] Set the DCE dynamic link delay measurement parameters. <dldm> can take the following values:
0 measurement off (default) 1 measurement on

<mi> denotes the measurement interval and can take the following values: 1-255 (in 1000-ms unit). Default is 15 for 15000 ms.

<dtl> denotes the delay tolerance in the link delay difference and can take the following values:
1-100 (in 1% unit). Default is 10%.

Read Command: +WDLDM? Query the current parameter settings. The response is in the form:
+WDLDM: <dldm>,<mi>,<dtl>

Test Command: +WDLDM=? List the supported parameter settings. The response is in the form:
+WDLDM: (supported <dldm>s), (supported <mi>s), (supported <dtl>s)

B.84 +WDAV ­ REGISTER OR DEREGISTER AN RS232 DAV DATA PERIPHERAL
Set Command: +WDAV=[<DP type>[,<encrypt>]] Register or deregister an RS232 DAV Data Peripheral (DP). <DP type> can take on the following values:
0 Deregister peripheral 1 Register Type 1 RS232 DAV Data Peripheral <encrypt> can take on the following values: 0 Encryption is not supported at this time

Read Command: +WDAV? Query the current DP registration parameter settings. The response is in the form:

Document Number: 451-93156-002C

84 of 172

+WDAV:<DP type>,<encrypt>

AL3A-RM/A3LA-RM-MIL User Guide Version C

Test Command: +WDAV=? List the supported DP registration parameters. The response is in the form:
+WDAV:(supported <type>s),(supported <encrypt>s)

B.85

+SBDWB ­ SHORT BURST DATA: WRITE BINARY DATA
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 A3LA-RM. The mobile originated buffer can contain only one message at any one time. Once the command is entered, the A3LA-RM 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 1960 bytes. The minimum mobile originated SBD message length is 1 byte. Once the Dte receives the READY indication from the A3LA-RM, 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 A3LA-RM the binary stream would be hex 68 65 6c 6c 6f 02 14. The mobile originated buffer will be empty upon power-up. If any data is currently in the mobile originated buffer, it will be overwritten.

Command Response: 0: SBD message successfully written to the A3LA-RM. 1: SBD message write timeout. An insufficient number of bytes were transferred to the A3LA-RM during the transfer period of 60 seconds.

Document Number: 451-93156-002C

85 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
2: SBD message checksum sent from DTE does not match the checksum calculated at the A3LA-RM.
3: SBD message size is not correct. The maximum mobile originated SBD message length is 1960 bytes. The minimum mobile originated SBD message length is 1 byte.

B.86

+SBDRB ­ SHORT BURST DATA: READ BINARY DATA
Exec Command: +SBDRB This command is used to transfer a binary SBD message from the single mobile terminated buffer in the A3LA-RM 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 1890 bytes. 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 A3LARM 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 A3LA-RM, 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 A3LA-RM for this command.

B.87

+SBDRT ­ SHORT BURST DATA: READ TEXT MESSAGE
Exec Command: +SBDRT This command is used to transfer a text SBD message from the single mobile terminated buffer in the A3LA-RM to the DTE. This command is similar to +SBDRB but

Document Number: 451-93156-002C

86 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
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 1890 bytes. The mobile terminated message buffer will be empty upon power-up.
Command Response: +SBDRT: <CR> {mobile terminated buffer}
B.88 +SBDD ­ SHORT BURST DATA: CLEAR SBD MESSAGE BUFFER(S)
Exec Command: +SBDD[<Delete type>] This command is used to clear the mobile originated buffer, mobile terminated buffer or both. The <Delete type> parameter identifies which buffers are cleared.
0: Clear the mobile originated buffer 1: Clear the mobile terminated buffer 2: Clear both the mobile originated and mobile terminated buffers Using this command or power cycling the phone 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 A3LA-RM to the ESS does not clear the mobile originated buffer. Reading a message from the A3LA-RM does not clear the mobile terminated buffer.
Command Response: 0: Buffer(s) cleared successfully 1: An error occurred while clearing the buffer(s)

Document Number: 451-93156-002C

87 of 172

B.89

AL3A-RM/A3LA-RM-MIL User Guide Version C
+SBDC ­ SHORT BURST DATA: CLEAR SBD MOMSN
Exec Command: +SBDC This command will clear (set to 0) the mobile originated message sequence number (MOMSN) stored in A3LA-RM. The MOMSN is maintained even after power cycle. Command Response:
0: The MOMSN was cleared successfully 1: An error occurred while clearing the MOMSN

B.90

+SBDS ­ SHORT BURST DATA: STATUS
Exec Command: +SBDS This command returns current state of the mobile originated and mobile terminated buffers.

Command Response: +SBDS: <MO flag>, <MOMSN>, <MT flag>, <MTMSN> where: <MO flag>: The MO flag indicates the existence of a message in the mobile originated buffer. The response from the A3LA-RM is one of the following numeric codes:
0: No message in mobile originated buffer 1: Message in mobile originated buffer

<MOMSN>: The MOMSN identifies the sequence number that will be used during the next mobile originated SBD session.

<MT Flag>: The MT flag indicates the existence of a message in the mobile terminated buffer. The response from the A3LA-RM is one of the following numeric codes:
0: No message in mobile terminated buffer 1: 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.

Document Number: 451-93156-002C

88 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

B.91

+SBDTC ­ SHORT BURST DATA: TRANSFER MO BUFFER TO

MT BUFFER

Exec Command: +SBDTC This command will transfer the contents of the mobile originated buffer to the mobile terminated buffer. Developers of DTE can use this command to test reading and writing to the A3LA-RM without actually initiating SBD sessions with the ESS.

Command Response: 0: Mobile originated buffer transferred successfully 1: An error occurred while transferring the mobile originated buffer

B.92

+CAR ­ AUDIO OUTPUT CONTROL
Set Command: +CAR=<n> This command switches the type of audio output between analog, digital and mute (no audio output). Valid values for <n> are as follows:
0 mute 1 analog (Codec port) 2 digital (User Connector port)

Read Command: +CAR? This command queries the current audio setting. Response is in the form:
+CAR: <n>

Test Command: +CAR=? This command lists the supported values of <n>. Response is in the form:
+CAR: (list of supported values of <n>)

B.93

IN ­ IDENTIFICATION

Requests the A3LA-RM to display information about itself. 0 "2400" (traffic channel rate for IRIDIUM data/fax) 1 "0000" (ROM checksum which is not supported so zero is output) 2 "OK" (result of ROM checksum verification which is not supported so OK is always

Document Number: 451-93156-002C

89 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
output) 3 "XXXXXXXX" (Software revision level) 4 "IRIDIUM" (Product description) 5 "XXXX" (Country code) 6 "XXX" (Factory identity) 7 "XXXXXXXX" (Hardware specification)

B.94

+CIER ­ INDICATOR EVENT REPORTING
Set Command: +CIER=[<mode>[,<sigind>[,<svcind>]]] The set command enables or disables sending of the +CIEV unsolicited result code by the A3LA-RM 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 A3LA-RM. (default) 1 Enable indicator event reporting; buffer the most recent +CIEV unsolicited result code for each indicator when the data port is not in command mode, and flush them to the DTE on return to command mode; otherwise forward events 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 displayed on the signal strength indicator 1 Equivalent to 1 bar displayed on the signal strength indicator 2 Equivalent to 2 bars displayed on the signal strength indicator

Document Number: 451-93156-002C

90 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
3 Equivalent to 3 bars displayed on the signal strength indicator
4 Equivalent to 4 bars displayed on the signal strength indicator
5 Equivalent to 5 bars displayed on the signal strength indicator
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 currently unavailable 1 Network service is available
Network service availability is equivalent to a signal strength greater than 0. The service availability indicator provides a way for the DTE to wait until the A3LA-RM 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>
Test Command: +CIER=? List the supported settings. The response is of the form:
+CIER: (supported <mode>s),(supported <sigind>s),(supported <svcind>s)
Note: In <mode> 1, the DTE may miss some indicator state changes if they occur while the data port is reserved (not in command mode). However, the buffering mechanism ensures that the most recent change for each indicator during reservation will be

Document Number: 451-93156-002C

91 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
flushed to the DTE on return to command mode; thus the DTE is always made aware of the latest state of each indicator.

B.95

+CRIS ­ RING INDICATION STATUS
Exec Command: +CRIS Query the ring indication status, returning the reason for the most recent assertion of the Ring Indicate signal. 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: 0 No telephony ring alert received 1 Incoming voice call 2 Incoming data call 3 Incoming fax call
and <sri> indicates the SBD ring indication status: 0 No SBD ring alert received 1 SBD ring alert received

Note: It is valid for the A3LA-R/RM/RGS to receive a telephony ring alert and an SBD ring alert at the same time. Assertion of the RI signal indicates only the presence of an alert; this command may be used to determine the type(s) of ring alert.

B.96 +CSQ[F] ­ SIGNAL QUALITY

Exec Command: +CSQ[F] Execution command returns the received signal strength indication <rssi> from the

A3LA-RM.

Response is in the form: +CSQ: <rssi>
where <rssi> is: 0 Equivalent to 0 bars displayed on the signal strength indicator 1 Equivalent to 1 bar displayed on the signal strength indicator
Document Number: 451-93156-002C

92 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
2 Equivalent to 2 bars displayed on the signal strength indicator 3 Equivalent to 3 bars displayed on the signal strength indicator 4 Equivalent to 4 bars displayed on the signal strength indicator 5 Equivalent to 5 bars displayed on the signal strength indicator

Note: The +CSQ form of the command waits for an updated signal strength reading to become available. This will usually be within two seconds of issuing the command. If the A3LA-RM is in the process of acquiring the system, or in a satellite handoff, a delay in response of up to 10 seconds may be experienced.

If the A3LA-RM has no SIM, is awaiting a SIM PIN entry, has an invalid SIM, or has otherwise not proceeded to successful registration, the delay in response may exceed the 50 second timeout limit. Under such condition, an ERROR response will be received. To avoid a delayed response due to registration problems, issue the +CREG command to verify registration prior to entering the +CSQ command to obtain signal strength.

Note: The +CSQF form of the command returns immediately, reporting the last known signal strength.

Test Command: +CSQ=? List the supported signal strength indications. The response is in the form:
+CSQ: (supported <rssi>s)

B.97

+CULK ­ UNLOCK
Exec Command: +CULK=<unlock key> Unlock the SBD functionality of the A3LA-RM after it has been locked by the Gateway. The unlock key must be obtained by contacting Iridium's customer support. <unlock key>:
0000000000000000 .. FFFFFFFFFFFFFFFF (a string of 16 hexadecimal digits)

While the A3LA-RM is locked, it is unable to perform any SBD sessions. Any attempts to start a session will return an error code indicating that the A3LA-RM is locked.

Command Response: +CULK:<status>

Document Number: 451-93156-002C

93 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
where: <status> indicates the lock status of the A3LA-RM following the unlock attempt:
0 Unlocked ­ A3LA-RM is not locked and is permitted to perform SBD sessions. 1 Locked ­ A3LA-RM 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 ­ A3LA-RM 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 SBD lock status of the A3LA-RM. The response is of the form:
+CULK:<status> <status>:
0 Unlocked 1 Locked 2 Permanently locked

B.98

+CVMI ­ VOICEMAIL INDICATION
Exec Command: +CVMI Query the status of the voicemail indication flag. The response is of the form:
+CVMI:<vmi> where <vmi> is:
0 No voicemail indication has been received 1 A voicemail indication has been received

The voicemail indication flag indicates whether a voicemail notification message has been received from the voicemail system. The flag is set to 1 when an indication is received, and is cleared to 0 after being queried with the +CVMI command.

Note: For this feature to function, the voicemail number must be programmed into the A3LA-R/RM/RGS.

Document Number: 451-93156-002C

94 of 172

B.99

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CICCID ­ READ ICC ID FROM SIM
Exec Command: +CICCID Query the status ICC ID of the SIM:
+CICCID This returns the 19 or 20 digit Integrated Circuit Card Identification of the SIM.

Note: This value is cached from the SIM and thus is not available until the caching has completed ~5-10 seconds after startup.

B.100 +CLIP ­ CALLING LINE IDENTIFICATION PRESENTATION
Exec Command: +CLIP=<n>

Note: While this command is implemented in the A3LA-RM, it may not yet be supported in the Iridium network. Stand by for an Iridium Technical Bulletin announcing network support for this feature.

This command controls the presentation of the Calling Line Identity of the calling party

in a mobile terminated call via the +CLIP unsolicited result code. <n> controls only the

presentation of the unsolicited result code; the delivery of Calling Line Identity

information to the A3LA-RM is controlled by the provisioning of the CLI Presentation

supplementary service in the network where <n> is:

0 Disable the +CLIP unsolicited result code. (default)

1 Enable the +CLIP unsolicited result code to be sent to the DTE following

the RING result code when a mobile terminated call is received and Calling

Line Identity information is present.

The unsolicited result code has the format:

+CLIP:<number>,<type>

where:

<number> is the phone number of the calling party in "quotes", in the format specified

by <type>.

<type> indicates the type of number:

129 Dial string without the international access character

145 Dial string which includes the international access character `+'

Document Number: 451-93156-002C

95 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: +CLIP? Query the current CLI Presentation provisioning status and the status of the +CLIP unsolicited result code. The response is of the form:
+CLIP:<n>,<m> <m>:
0 CLIP not provisioned 1 CLIP provisioned 2 Unknown (e.g. no network, etc.)

B.101 +CLIR ­ CALLING LINE IDENTIFICATION RESTRICTION
Exec Command: +CLIR=<n>

Note: While this command is implemented in the A3LA-RM, it may not yet be supported in the Iridium network. Stand by for an Iridium Technical Bulletin announcing network support for this feature.

This command controls the presentation of the Calling Line Identity of the calling party to the called party in the next mobile originated call. <n>:
0 Presentation is determined by the subscription of the CLIR service 1 CLIR invocation ­ i.e. hide the CLI for the next mobile originated call. This
requires CLIR to be provisioned in one of the temporary modes. 2 CLIR suppression ­ i.e. show the CLI for the next mobile originated call. This requires CLIR to be provisioned in one of the temporary modes.

Note: If the CLIR service is not provisioned, and either invocation or suppression is requested for the next call, the next call may be rejected by the network. It is the DTE's responsibility to check whether CLIR is provisioned using the +CLIR? read command.

Read Command: +CLIR? Query the current CLI Restriction provisioning status and the CLIR invocation/suppression status for the next call. The response is of the form:
+CLIR:<n>,<m> <m>:

Document Number: 451-93156-002C

96 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
0 CLIR not provisioned 1 CLIR provisioned in permanent mode 2 Unknown (e.g. no network, etc.) 3 CLIR provisioned in temporary mode, defaulting to presentation restricted 4 CLIR provisioned in temporary mode, defaulting to presentation allowed
B.102 +IPR ­ FIXED DTE RATE
Set Command: +IPR=<rate>[,<autoflag>] Set the data rate at which the A3LA-RM will accept commands. The change in data rate takes effect after the result code (e.g. OK) is received by the DTE. <rate> takes the following values:
1 600 bps 2 1200 bps 3 2400 bps 4 4800 bps 5 9600 bps 6 19200 bps (default) 7 38400 bps <autoflag> takes the following values: 0 Fixed rate ­ automatic rate adjustment is disabled 1 Automatic rate adjustment is enabled (default)
Read Command: +IPR? Query the current data rate and automatic rate adjustment setting. The response is in the form:
+IPR: <rate>,<autoflag>
Test Command: +IPR=? List the supported data rates. The response is in the form:
+IPR: (supported <rate>s),(supported <autoflag>s)

Document Number: 451-93156-002C

97 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.103 +SBDWT ­ SHORT BURST DATA: WRITE A TEXT MESSAGE
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 A3LA-RM.
The text message may be entered on the command line: For example, "AT+SBDWT=hello" The length of <text message> is limited to 120 bytes. 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 A3LA-RM 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 the maximum mobile originated message length of 1960 bytes The mobile originated buffer will be empty upon power-up If any data is currently in the mobile originated buffer, it will be overwritten
Command Response: For the "AT+SBDWT" form:
0 SBD message successfully stored in mobile originated buffer 1 SBD message write timeout. No terminating carriage return was sent
within the transfer period of 60 seconds.
For the "AT+SBDWT=<text message>" form: OK SBD message successfully stored in mobile originated buffer ERROR An error occurred storing SBD message in mobile originated buffer

Document Number: 451-93156-002C

98 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.104 +SBDDET ­ SHORT BURST DATA: DETACH
Exec Command: +SBDDET Initiates an SBD session to detach the A3LA-RM from the Gateway.

Command Response: +SBDDET:<status>,<error>

where:

<status>:

0

Detach successfully performed

1 An error occurred while attempting the detach

<error>:

Gateway-reported values:

0 Detach successfully performed

1..4 Reserved, but indicate success if used

5..14 Reserved, but indicate failure if used

15 Access is denied

A3LA-RM-reported values:

16 Modem has been locked and may not make SBD calls (see +CULK

command)

17 Gateway not responding (local session timeout)

18 Connection lost (RF drop)

19 Link failure (A protocol error caused termination of the call)

20..31 Reserved, but indicate failure if used

32 No network service, unable to initiate call

33..34 Reserved, but indicate failure if used

35 A3LA-RM is busy, unable to initiate call

36.. Reserved, but indicate failure if used

This instructs the GSS to disable (detach) SBD ring alerts for the calling A3LA-RM. Successful completion of the detach command implies that the GSS has performed the requested detach action and the A3LA-RM is no longer registered for SBD ring alerts. This session does not transfer any MO or MT messages.

Document Number: 451-93156-002C

99 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
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.
B.105 +SBDI ­ SHORT BURST DATA: INITIATE AN SBD SESSION
Note: The +SBDI command is provided for backwards compatibility with existing DTEs which do not use SBD Ring Alert 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 An SBD Detach is performed as part of the call No SBD location update is performed
DTEs requiring SBD Ring Alert functionality should use the extended +SBDIX command.
Exec Command: +SBDI This command initiates an SBD session between the A3LA-RM and the GSS. If there is a message in the mobile originated buffer it will be transferred to the GSS. Similarly, if there are one or more messages queued at the GSS the oldest will be transferred to the A3LA-RM and placed into the mobile terminated buffer. The message, if any, in the mobile originated buffer will be sent from the A3LA-RM to the GSS If there is a message queued at the GSS it will be transferred to the A3LA-RM and placed into the mobile terminated buffer
Command Response: +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 A3LA-RM 1 SBD message successfully sent from the A3LA-RM to the GSS

Document Number: 451-93156-002C

100 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
2 An error occurred while attempting to send SBD message from A3LA-RM to GSS

<MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by the A3LA-RM when sending a mobile-originated message to the GSS. This value is incremented each time an SBD session is successfully completed between the A3LA-RM to the GSS. This wraparound 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 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 forwarding a message to the A3LA-RM. This value is indeterminate if the field <MT status> is zero. This wraparound 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 A3LA-RM.

B.106 +SBDIX[A] ­ SHORT BURST DATA: INITIATE AN SBD SESSION EXTENDED
Note: The +SBDIX command must be used in place of the +SBDI command for DTEs wishing to make use of SBD Ring Alert functionality.

Exec Command: +SBDIX[A][=<location>]

This command initiates an SBD session between the A3LA-RM 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

Document Number: 451-93156-002C

101 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
message in the mobile originated buffer it will be transferred to the GSS. Similarly, if there are one or more messages queued at the GSS the oldest will be transferred to the A3LA-RM and placed into the mobile terminated buffer. The message, if any, in the mobile originated buffer will be sent from the A3LA-RM to the GSS If there is a message queued at the GSS it will be transferred to the A3LA-RM and placed into the mobile terminated buffer This command will always attempt an SBD registration, consisting of attach and location update, during the SBD session in order to support SBD Ring Alert. If this is not desired, the +SBDI command should be used. The DTE should append an `A' to the command, i.e. +SBDIXA, when the SBD session is in response to an SBD ring alert

<location> has format: [+|-]DDMM.MMM,[+|-]dddmm.mmm
where: DD Degrees latitude (00-89) MM Minutes latitude (00-59) MMM Thousandths of minutes latitude (000-999) ddd Degrees longitude (000-179) mm Minutes longitude (00-59) mmm Thousandths of minutes longitude (000-999)

This command initiates an SBD session between the A3LA-RM and the GSS, setting the SBD Session. The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example,
AT+SBDIX=5212.483,-00007.350 corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.

Command Response: +SBDIX:<MO status>,<MOMSN>,<MT queued>

status>,<MTMSN>,<MT

length>,<MT

Document Number: 451-93156-002C

102 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
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 3..4 Reserved, but indicate MO session success if used 5..8 Reserved, but indicate MO session failure if used 10 GSS reported that the call did not complete in the allowed time 11 MO message queue at the GSS is full 12 MO message has too many segments 13 GSS reported that the session did not complete 14 Invalid segment size 15 Access is denied A3LA-RM-reported values: 16 Modem has been locked and may not make SBD calls (see +CULK command) 17 Gateway not responding (local session timeout) 18 Connection lost (RF drop) 19 Link failure (A protocol error caused termination of the call) 20..31 Reserved, but indicate failure if used 32 No network service, unable to initiate call 33..34 Reserved, but indicate failure if used 35 A3LA-RM is busy, unable to initiate call 36.. Reserved, but indicate failure if used
<MOMSN>: The Mobile Originated Message Sequence Number (MOMSN) is a value assigned by A3LA-RM when sending a mobile-originated message to the GSS. This

Document Number: 451-93156-002C

103 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
value is incremented each time an SBD session is successfully completed between the A3LA-RM to the GSS. This wraparound 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 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 forwarding a message to the A3LA-RM. This value is indeterminate if the field <MT status> is zero. This wraparound 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 A3LA-RM.

B.107 +SBDDSC ­ SHORT BURST DATA: DELIVERY SHORT CODE
Set Command: +SBDDSC=<dsc>

Set the Delivery Short Code (DSC), which provides dynamic routing or control information for MO or 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 are overridden during certain SBD sessions (e.g. a +SBDREG registration session sets flag 0x80). Enable or disable ring indications for SBD Ring Alerts. <dsc>:
0..255 DSC to be used for subsequent MO messages (0 default) 0x80 Hold MT message delivery 0x40 Leave MT message in queue after delivery 0x20 Destination in MO payload

Document Number: 451-93156-002C

104 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: +SBDDSC? Query the current Delivery Short Code. The response is of the form:
+SBDDSC:<dsc>
B.108 +SBDMTA ­ SHORT BURST DATA: MOBILE-TERMINATED ALERT
Set Command: +SBDMTA=<mode> Enable or disable ring indications for SBD Ring Alerts. <status>:
0 Disable ring indication 1 Enable ring indication (default)
When SBD ring indication is enabled, the A3LA-RM 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)
B.109 +SBDREG ­ SHORT BURST DATA: NETWORK REGISTRATION
Exec Command: +SBDREG[=<location>]
Triggers an SBD session to perform a manual SBD registration.
This command initiates an SBD session to perform a manual SBD registration, consisting of an attach and location update. This session does not transfer any MO or MT messages.
Note: The A3LA-RM 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 DTE should try later (see error 36 below).

Document Number: 451-93156-002C

105 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Note: A user can send an MO SBD message and register at the same time by using the +SBDIX command. The +SBDIX command always performs a registration attempt and should be used for an application requiring SBD Ring Alert. The +SBDI command never includes an SBD registration and should be used for an application that does not require SBD Ring Alert. <location> has format:
[+|-]DDMM.MMM,[+|-]dddmm.mmm where:
DD Degrees latitude (00-89) MM Minutes latitude (00-59) MMM Thousandths of minutes latitude (000-999) ddd Degrees longitude (000-179) mm Minutes longitude (00-59) mmm Thousandths of minutes longitude (000-999)
This command initiates an SBD session between the A3LA-RM and the GSS, setting the SBD Session.
The optional sign indicators specify latitude North (+) or South (-), and longitude East (+) or West (-). If omitted, the default is +. For example,
AT+SBDIX=5212.483,-00007.350 corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.
Command Response: +SBDREG:<status>,<reg err> where: <status> indicates the resulting registration status of the A3LA-RM:
0 Detached ­ A3LA-RM is detached as a result of a successful +SBDDET or +SBDI command
1 Not registered ­ A3LA-RM is attached but has not provided a good location since it was last detached

Document Number: 451-93156-002C

106 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
2 Registered ­ A3LA-RM 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 GSS is denying service to the A3LA-RM <reg err>:
Gateway-reported values: 0 No error 2 Session completed but the requested Location Update was not accepted 3..14 Reserved, but indicate Location Update failure if used 15 Access is denied A3LA-RM-reported values: 16 Modem has been locked and may not make SBD calls (see +CULK
command) 17 Gateway not responding (local session timeout) 18 Connection lost (RF drop) 19 Link failure (A protocol error caused termination of the call) 20..31 Reserved, but indicate failure if used 32 No network service, unable to initiate call 33..34 Reserved, but indicate failure if used 35 A3LA-RM is busy, unable to initiate call 36 Try later, must wait 3 minutes since last registration 37.. Reserved, but indicate failure if used
Read Command: +SBDREG? Query the current SBD registration status of the A3LA-RM. The response is of the form:
+SBDREG:<status> <status>:
0 Detached 1 Not registered 2 Registered

Document Number: 451-93156-002C

107 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
3 Registration denied The registration status is stored in A3LA-RM non-volatile memory, and can therefore be queried by the DTE after powering up.

B.110 +SBDAREG ­ SHORT BURST DATA: AUTOMATIC REGISTRATION
Exec Command: +SBDAREG=<mode> Set the A3LA-RM' Auto-registration mode. <mode>:
0 Disable automatic registration (default) 1 Set the Auto-registration mode to "Automatic" 2 Set the Auto-registration mode to "Ask"

When auto-registration is enabled, mode 1 or 2, the A3LA-RM monitors its current location and triggers an SBD auto-registration when it determines that it has moved sufficiently far away from its last registered location. Note that auto-registration runs only while the A3LA-RM is attached to the GSS, i.e. the registration status is "Not registered" or "Registered".

Auto-registration may only be used with system-provided location. If the DTE is providing its own location (e.g. GPS), the DTE should use the manual registration command, +SBDREG. Upon triggering in mode 1, "Automatic", the A3LA-RM autonomously initiates an SBD session in order to perform a registration with its updated location. This session does not transfer any MO or MT messages.

Upon triggering in mode 2, "Ask", the A3LA-RM reports to the DTE that it should register with the system because its location has changed (see <event> below); it is then the responsibility of the DTE to register via +SBDREG or +SBDIX. +SBDIX allows the DTE to register while including an MO message and/or retrieving any MT message that is pending at the GSS.

When auto-registration is enabled, mode 1 or 2, the A3LA-RM reports relevant events to the DTE by issuing an unsolicited result code +AREG:<event>,<reg error>. <event>:
0 Suggest DTE makes a registration attempt (mode 2 only)

Document Number: 451-93156-002C

108 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
1 Auto-registration has been performed successfully (mode 1 only) 2 Auto-registration has failed and will be retried after a delay (mode 1 only)
<reg error>: Gateway-reported values: 0 No error 2 Session completed but the requested Location Update was not accepted 3..14 Reserved, but indicate Location Update failure if used 15 Access is denied A3LA-RM-reported values: 16 A3LA-RM has been locked and may not make SBD calls (see +CULK command) 17 Gateway not responding (local session timeout) 18 Connection lost (RF drop) 19 Link failure (A protocol error caused termination of the call) 20..31 Reserved, but indicate failure if used 32 No network service, unable to initiate call 33..34 Reserved, but indicate failure if used 35 A3LA-RM is busy, unable to initiate call 36 Try later, must wait 3 minutes since last registration 37.. Reserved, but indicate failure if used
Read Command: +SBDAREG? Query the current automatic MT registration mode. The response is of the form:
+SBDAREG:<mode>
Test Command: +SBDAREG=? List the supported mode settings. The response is of the form:
+SBDAREG:(supported <mode> settings)

Document Number: 451-93156-002C

109 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.111 +SBDSX ­ SHORT BURST DATA: STATUS EXTENDED
Exec Command: +SBDSX This command returns current state of the mobile originated and mobile terminated buffers, and the SBD ring alert status.
Command Response: +SBDSX: <MO flag>, <MOMSN>, <MT flag>, <MTMSN>, <RA flag>, <msg waiting> where:
<MO flag>: The MO flag indicates the existence of a message in the mobile originated buffer. The response from the A3LA-RM is one of the following numeric codes:
0 No message in mobile originated buffer 1 Message in mobile originated buffer
<MOMSN>: The MOMSN identifies the sequence number that will be used during the next mobile originated SBD session.
<MT Flag>: The MT flag indicates the existence of a message in the mobile terminated buffer. The response from the A3LA-RM is one of the following numeric codes:
0 No message in mobile terminated buffer 1 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 No SBD ring alert 1 SBD ring alert has been received and needs to be answered
Note: The RA flag is set whenever the A3LA-RM receives an SBD ring alert; this happens even if the +SBDMTA setting specifies that SBD ring indications are disabled.

Document Number: 451-93156-002C

110 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
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 A3LA-RM.
<msg waiting>: The message waiting flag indicates how many SBD mobile terminated messages are currently queued at the gateway awaiting collection by the A3LA-RM. This flag is updated after every SBD session, including +SBDI, +SBDIX, +SBDIXA, +SBDREG and +SBDDET.
B.112 +CCWA ­ CALL WAITING SERVICE

Command

Possible Response(s)

+CCWA=

None (command ignored without error)

+CCWA=<n>[,<mode>,<classx>]

When command unsuccessful +CME ERROR: <err>
When <mode>=2 command successful +CCWA:<status>,<class1> [<CR><LF>+CCWA:<status>,<class2> [...]] (but the A3LA-RM will in practice only report a single line, <class1> = 1)
When <mode> not 2 and command successful None

+CCWA?

Current unsolicited result presentation status +CCWA:<n>

Test command +CCWA=?

List of supported <n>s +CCWA:(0,1)

None

Unsolicited result notifying that a call is waiting +CCWA:<number>,<type>,<class>

Note: While this command is implemented in the A3LA-RM, it may not yet be

supported in the Iridium network. Stand by for an Iridium Technical Bulletin

announcing network support for this feature.

This command is based on GSM 07.07 [2] subclause 7.11, and allows control of the Iridium Call Waiting supplementary service similar to GSM 02.83 [6]. Activation, deactivation and status query are supported. Parameter <n> is used to disable/enable

Document Number: 451-93156-002C

111 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
the presentation of the unsolicited result code to the DTE when the Call Waiting service is enabled.
Command is abortable in the cases when the network is interrogated. The interaction of this command with other commands based on other GSM supplementary services is described in the GSM standard.
Defined values <n> (sets/shows the result code presentation status in the A3LA-RM):
0 disable unsolicited result presentation 1 enable unsolicited result presentation On a DTE-DCE command, <n> will set the result code presentation status in the A3LA-RM, regardless of the value of any <mode> parameter. <mode> (when <mode> parameter is not given, network is not interrogated): 0 disable Call Waiting service for specified class(es) 1 enable Call Waiting service for specified class(es) 2 query status of Call Waiting service for specified class(es) <classx> is a sum of integers each representing a class of information: 1 voice 2 data 4 fax
This parameter defaults to 7, equal to all classes, but the A3LA-R/RM/RGS only supports Voice Call Waiting so this is illegal. Therefore in practice the DTE must supply <classx>=1. <status>: 0 Call Waiting service not active for specified Class 1 Call Waiting service active for specified Class <number>: quoted string type phone number of calling address in format specified by <type>

Document Number: 451-93156-002C

112 of 172

<type>:

AL3A-RM/A3LA-RM-MIL User Guide Version C
type of address octet in integer format (refer GSM 04.08 [7] subclause 10.5.4.7);default 145 when dialing string is international number, otherwise 129.

If the network rejects a request to activate/deactivate the Call Waiting service due to it not being provisioned (or for other reasons), the reported CME ERROR code will be 133 "requested service option not subscribed". This is strictly speaking a GPRS-related code (GSM 07.07 [2] subclause 9.2.2), but is the most informative choice in this case.

Informative examples:

The status of only the Voice class can be queried: AT+CCWA=1,2,1

If the command is successful, the A3LA-RM might return (after contacting the network):
+CCWA:1,1

If a remote caller tries to place a voice call to the A3LA-RM while it already has a call in progress, and the Call Waiting service has been made active for class Voice, then the network will send a message to the A3LA-RM. Then, if <n> has previously been set to `1', the A3LA-RM will send an unsolicited result code to the DTE, e.g.:
+CCWA:"+441223420024",145,1

B.113 +CLCK ­ FACILITY LOCK

Command +CLCK= +CLCK=<fac>,<mode>[<passwd>[,<classx>]]
Test command

Possible Response(s)
None (command ignored without error)
When command unsuccessful +CME ERROR: <err> When <mode>=2 and command successful +CLCK:<status>[,<class1> [<CR><LF>+CLCK:<status>,<class2> [...]] (but the A3LA-RM will in practice only report a single line, <class1> = 1) When <mode> not 2 and command successful None
List of supported <fac>s

Document Number: 451-93156-002C

113 of 172

+CLCK=?

AL3A-RM/A3LA-RM-MIL User Guide Version C
+CLCK:("CS","SC","FD","AO","AI","AB")

This command is based on GSM 07.07 [2] subclause 7.4, and is used to enable, disable or interrogate an ME or a network facility <fac>.
Command is abortable in the cases when network facilities are set or interrogated. The interaction of this command with other commands based on other GSM supplementary services is described in the GSM standard.
Execute command is used to activate or deactivate Call Barring Supplementary Services, SIM Fixed Dialling feature, the SIM card PIN Code, or to enable or disable the Phone Lock feature in the A3LA-RM. A password code (detailed below) may be required, depending on the action chosen.
Not all Call Barring services detailed in GSM 07.07 [2] subclause 7.4 are supported. A subset of those implemented in the H1 menu MMI is supported.
Note: This command will not work unless the SIM PIN has been entered using the +CPIN command.
Note: Once this command has been issued to disable the PIN, neither it nor the +CPIN need to be issued again unless the PIN function is reactivated.
The following parameter values are currently supported: <fac>:
"CS" CNTRL Surface (Enable/Disable Phone Lock feature). The current Phone Unlock Code is required as <passwd>.
"SC" SIM: Activate/Deactivate SIM card PIN Code, in which the SIM asks password in ME power-up. The PIN code is required as <passwd>.
"FD" SIM fixed dialling memory feature (PIN2 is required as <passwd>) "AO" BAOC (Bar All Outgoing Calls) (refer GSM 02.88 [4] clause 1). The Call
Barring password is required as <passwd>. "AI" BAIC (Bar All Incoming Calls) (refer GSM 02.88 [4] clause 2). The Call Barring
password is required as <passwd>.

Document Number: 451-93156-002C

114 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
"AB" All Barring services (refer GSM 02.30 [5]) (applicable only for <mode>=0). The Call Barring password is required as <passwd>.

Note: Several GSM standard facility codes including the following are NOT supported:

"OI" BOIC (Bar Outgoing International Calls) (refer GSM 02.88 [4] clause 1). All Iridium calls are International, so this facility should not be exercised by a user interface.
"OX" BOIC-exHC (Bar Outgoing International Calls except to Home Country) (refer GSM 02.88 [4] clause 1). All Iridium calls are International, so this facility should not be exercised by a user interface.
"IR" BIC-Roam (Bar Incoming Calls when Roaming outside the home country) (refer GSM 02.88 [4] clause 2). In Iridium it is not possible to roam (there is only one "home country"), so this facility should not be exercised by a user interface.
"AG" All outGoing barring services (refer GSM 02.30 [5]) (applicable only for <mode>=0). This subgroup of services cannot be addressed; the user interface should just use "AB".
"AC" All inComing barring services (refer GSM 02.30 [5]) (applicable only for <mode>=0). This subgroup of services cannot be addressed; the user interface should just use "AB".

<mode>: 0 Disable (Deactivate) 1 Enable (Activate)

<passwd>: string type, enclosed by " "; for example, "1234".

Note: Factory default SIM card PIN Code is "1111"

Note: Factory default Phone Unlock Code is "1234"

<classx> is a sum of integers each representing a class of information: 1 voice 2 data 4 fax
Document Number: 451-93156-002C

115 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
This parameter defaults to 7, equal to all classes, but the A3LA-RM only supports Voice Call Barring so this is illegal. Therefore in practice the DTE must supply <classx>=1 when querying or changing the status of any Call Barring facility. When querying (<mode>=2), <passwd> is irrelevant and should be supplied as "" in order to allow the <classx>=1 parameter to be supplied.
For facilities "CS", "SC"and "FD", the <passwd> and <classx> parameters are not relevant and will be ignored if supplied.
Test Command: +CLCK=? Test command returns the facility values supported by the phone. The response is in the form:
+CLCK:(list of supported <fac>s)
Note: Only "CS" will appear as a supported value if there is no SIM card in the device.
Note: +CLCK is closely related to +CPIN and +CPWD. See these commands for additional information.
B.114 +CPWD ­ CHANGE PASSWORD
Exec Command: +CPWD=<fac>,<oldpwd>,<newpwd> This command sets a new password for the facility lock function defined by the AT command Facility Lock +CLCK. The following parameter values are currently supported: <fac>:
"CS" CNTRL Surface (Phone Unlock Code) "SC" SIM (SIM Card PIN Code) "P2" SIM PIN2 (SIM Card PIN2 Code) "AB" Call Barring password (single password used for all call barring supplementary services)
Note: AT+CPWD="SC",<oldpwd>,<newpwd> will return "Error" unless the SIM Card Pin Code is currently activated (see AT command Facility Lock +CLCK).

Document Number: 451-93156-002C

116 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Note: A user interface may prompt the user for two copies of the new password, in which case it should check the two are identical as only one copy is needed for this command.
Test Command: +CPWD=? Test command returns a list of pairs which present the available facilities and the maximum length of their password. Response is in the form:
+CPWD: list of supported (<fac>,<pwdlength>)s where <pwdlength> indicates the maximum length for the password.
Note: +CPWD is closely related to +CLCK and +CPIN. See these commands for additional information.
B.115 +CSDT ­ SIDETONE
Exec Command: +CSDT=<sidetone enabled> This command controls the A3LA-RM RF board sidetone generation. Enabling sidetone will cause the A3LA-RM to start sidetone generation. Disabling sidetone will cause the A3LA-RM to stop sidetone generation. The following parameter values are currently supported: < sidetone enabled >:
1 Enable sidetone 0 Disable sidetone
Query Command: +CSDT? This command returns the current transceiver board sidetone generation state. 1 = enabled, 0 = disabled.
Test Command: +CSDT=? Test command returns a list of valid values. Response is in the form:
+CSDT: list of supported modes
B.116 +CDSI ­ REPORT SMS STATUS
This announcement is sent when the network responds after a mobile-originated SMS send attempt.

Document Number: 451-93156-002C

117 of 172

Exec Command: none

AL3A-RM/A3LA-RM-MIL User Guide Version C

Unsolicited Announcement: +CDSI:<status>
where: <status>:
0..255 Success code or failure cause (TD_SMS_RP_CAUSE_*) 1 Unassigned Number 8 Operator Barring 10 Call Barred 21 SM Transfer Rejected 22 Memory Capacity Exceeded 27 Destination Out Of Order 28 Unidentified Subscriber 29 Facility Rejected 30 Unknown Subscriber 38 Network Out Of Order 41 Temporary Failure 42 Congestion 47 No Resources 50 Facility Not Subscribed 69 Facility Not Implemented 81 Invalid RP MR 95 Semantic Error 96 Mandatory IE Error 97 RP MT Not Implemented 98 Bad State 99 IE Not Implemented 111 Unspecified Error 127 Interworking Error 128 Success

Document Number: 451-93156-002C

118 of 172

129 Success Ack 253 No Transaction Id 254 CM Internal Error 255 RL Timeout

AL3A-RM/A3LA-RM-MIL User Guide Version C

Values up to 127 are defined by GSM for SMS-PP Relay Layer messages and values 128 and above are internal codes introduced by Iridium.

B.117 +GPSSTA ­ CONFIGURE GPS STATUS
This command enables and disables the GPS receiver when the module is idle. When the module is in a call, then the GPS receiver is disabled to avoid interference between the module's Iridium band transmitter and the GPS band receiver.

Note: the GPS receiver (and associated circuitry) is optional and is not fitted to some revisions of the A3LA-RM RF board. In this case all forms of the +GPSSTA command will return an error.

Exec Command: +GPSSTA=<mode> where: <mode>:
0 disable GPS receiver 1 enable GPS receiver

Query Command: +GPSSTA? This command returns the current GPS receiver state. 1 = enabled, 0 = disabled.

Test Command: +GPSSTA=? Test command returns a list of valid values. Response is in the form:
+GPSSTA: list of supported modes

B.118 +PA ­ GPS: LIST OF NMEA MESSAGE FORMATS
Exec Command: +PA=<n> No action, compatibility only. Only allows a value of 1 for <n>. The NMEA string returned does not contain any GPS information.

Document Number: 451-93156-002C

119 of 172

B.119

AL3A-RM/A3LA-RM-MIL User Guide Version C
+PLOC ­ GPS: DISPLAY POSITION TO 5TH DECIMAL PLACE

Exec Command: +PLOC No action, compatibility only. This command always returns the string "+PLOC: For Compatibility Only".

B.120 ^AA ­ AUTO ANSWER DISPLAY
Exec Command: ^AA=<n> This command sets whether or not to display the ^AAI unsolicited result code when attempting to auto answer a call. <n>:
0 URC is not displayed 1 URC is displayed. ^AAI:1 is displayed when auto answering starts and ^AAI:0 is displayed when auto answering is finished whether or not it was successful.

Read Command: ^AA? Queries the current setting

Test Command: ^AA=? Returns the accepted values

B.121 ^AD ­ AUTO DIAL
Exec Command: ^AD=<enabled>,<number> This command enables or disables auto dialing. If auto dialing is enabled, the A3LARM will go into auto dial mode when the DTR line is brought low and will go back to command mode when the DTR line is brought high again. While in auto dial mode, the A3LA-RM will not respond to AT commands. Instead, the A3LA-RM will continuously dial the number that is setup for auto dialing. The ^ADR command controls the retry delay in between dial attempts. <enabled>:
0 Do not auto dial when the DTR line is low (default) 1 Auto dial when the DTR line is low

Document Number: 451-93156-002C

120 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
<number>: The phone number to dial. The number must be enclosed in double quotes and cannot be more than 20 characters long.

B.122 ^ADR ­ AUTO DIAL RETRY
Exec Command: ^ADR=<delay> This command sets the time to delay in between dial attempts in auto dial mode. <delay>: The number of seconds to delay. The value must be between 5 and 255 seconds.

B.123 ^CCOP ­ CHANGE CRYPTO OFFICER PASSWORD (ENCRYPTION)

Exec Command: ^CCOP=<old>,<new>

Change the Crypto Officer's password from factory-set/old value to new value. The

password must include all printable keyboard characters. The password will not be

reset by AT command &F. When the A3LA-RM is set to echo, all entries are replaced

with asterisks (*) instead of the actual typed value. All passwords must be between 8

and 16 characters in length. The factory-set password is `temp password' and must be

changed before encryption can be used.

<old>: Old password and must be enclosed by two single quotes (`old password`)

<new>:

New password and must be enclosed by two single quotes (`new

password`)

B.124 ^CMGEC ­ CLEAR SMS ENCRYPTED STORAGE
This command is a synonym for ^SMSE for backward compatibility. See the ^SMSE command for details.

Document Number: 451-93156-002C

121 of 172

B.125 ^FFW ­ FLASH FIRMWARE
Exec Command: ^FFW Puts the firmware into flashing mode

AL3A-RM/A3LA-RM-MIL User Guide Version C

B.126 ^KD ­ KEY FOR DECRYPTION (ENCRYPTION)
Exec Command: ^KD=<password>,<key> Allow entering the 32 bytes for the AES decryption key. These bytes must be entered with mandatory leading 0s, where each byte is represented by 2 hexadecimal uppercase characters for a total of 64 digits. The password and key will not be reset by &F. The password and key will not be echoed. This command must be entered twice before an update is made.

NOTE: The decryption key must match the encryption key at the base station or network operation center (NOC).

NOTE: A decryption key of all 0s and a TBR (Time Between Reports) value of 64801 will cause requested reports not to be sent out in tracking mode.

<password>: The Crypto Officer Password must be enclosed by two single quotes (` `). The Crypto Officer Password must be changed from its factory-set value before this command will work.

<key>:

The key that must be enclosed by two single quotes (` `). This can only have characters 0-9 or A-F and must be 64 bytes long. For example,
`0102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F20'.

B.127 ^KE ­ KEY FOR ENCRYPTION (ENCRYPTION)
Exec Command: ^KE=<password>,<key> Allow entering the 32 bytes for the AES encryption key. These bytes must be entered with mandatory leading 0s, where each byte is represented by 2 hexadecimal uppercase characters for a total of 64 digits. The password and key will not be reset by &F. The password and key will not be echoed. This command must be entered twice before an update is made.

Document Number: 451-93156-002C

122 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
NOTE: The Encryption key must match the Decryption key at the base station or NOC.
<password>: The Crypto Officer Password must be enclosed by two single quotes (` `). The Crypto Officer Password must be changed from its factory-set value before this command will work.
<key>: The key that must be enclosed by two single quotes (` `). This can only have characters 0-9 or A-F and must be 64 bytes long. For example,
`0102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F20'.
B.128 ^KZ ­ KEY ZEROIZATION (ENCRYPTION)
Exec Command: ^KZ=<password> Reset or zeroize the encryption and the decryption keys and stop encryption until the keys are re-entered with the AT^KD and AT^KE commands.
<password>: The Crypto Officer Password must be enclosed by two single quotes (` `). The Crypto Officer Password must be changed from its factory-set value before this command will work.
B.129 ^MODRSTN ­ MODEM RESET INFORMATION MESSAGE DISPLAYED
Whether to display the information message ^MODRST:1 when the modem is automatically recovered. Command has read.
0 Information message is not displayed 1 Information message is displayed.
B.130 ^MPTDC- MODEM POWER TOGGLE DATA CONNECTION
Exec Command: ^MPTDC = [<mode>] Enable or disable the modem power toggle functionality during a data connection.
When in a data connection, after there has been a four minute period of inactivity, there will be a check sent to determine if the modem is still responding. If it is not, the modem will power cycle and return in command mode.
<mode> takes the following values:

Document Number: 451-93156-002C

123 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
0 Disable the MPT functionality during a data call. 1 Enable the MPT functionality during a data call.
Read Command: ^MPTDC? Query the current modem power toggle data connection mode. The response is in the form:
^MPTDC: <mode>
Test Command: ^MPTDC=? List the supported modem power toggle data connection modes. The response is in the form:
^MPTDC: (supported <mode>s)
B.131 ^MPTFP- MODEM POWER TOGGLE FORCED POWER-CYCLE
Exec Command: ^MPTFP = [<mode>] Enable or disable the modem power toggle forced power-cycle functionality. Every twenty-four hours the modem will attempt to find a period of inactivity to cycle the power. If it cannot find a period of inactivity, it will retry a set number of times, after which it will force a power-cycle. The forced power-cycle will not occur during a data connection.
<mode> takes the following values: 0 Disable the MPT forced power-cycle functionality. 1 Enable the MPT forced power-cycle functionality.
Read Command: ^MPTFP? Query the current modem power toggle data connection mode. The response is in the form:
^MPTFP: <mode>
Test Command: ^MPTFP=? List the supported modem power toggle data connection modes. The response is in the form:
^MPTFP: (supported <mode>s)

Document Number: 451-93156-002C

124 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.132 ^MPTFR- MODEM POWER TOGGLE FORCED REGISTRATION
Exec Command: ^MPTFR = [<mode>] Enable or disable the modem power toggle forced registration functionality. Every hour the modem will attempt to find a period of inactivity to make a registration. If it cannot find a period of inactivity, it will retry a set number of times, after which it will force a registration. The modem is registered to the Iridium network by dialing a dummy number. The forced registration will not occur during a data connection because it is assumed that the modem is registered. <mode> takes the following values:
0 Disable the MPT forced registration functionality. 1 Enable the MPT forced registration functionality.
Read Command: ^MPTFR? Query the current modem power toggle forced registration. The response is in the form:
^MPTFR: <mode>
Test Command: ^MPTFR=? List the supported modem power toggle forced registration. The response is in the form:
^MPTFR: (supported <mode>s)
B.133 ^MPTNC- MODEM POWER TOGGLE NOT IN DATA CONNECTION
Exec Command: ^MPTNC = [<mode>] Enable or disable the modem power toggle functionality out of a data connection. When not in a data connection, after there has been a two-minute period of inactivity, there will be a check sent to determine if the modem is still responding. If it is not, the modem will power cycle and return in command mode.
<mode> takes the following values: 0 Disable the MPT functionality out of a data call. 1 Enable the MPT functionality out of a data call.

Document Number: 451-93156-002C

125 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: ^MPTNC? Query the current modem power toggle not data connection mode. The response is in the form:
^MPTNC: <mode>
Test Command: ^MPTNC=? List the supported modem power toggle not data connection modes. The response is in the form:
^MPTNC: (supported <mode>s)
B.134 ^MSB ­ MOTION SENSOR BEGIN
Exec Command: ^MSB=<m>,<s> This determines the number of minutes to look for motion for before the unit wakes up.
<m>: Number of minutes to wait to determine movement. The range is from 0 to 60. The value of 0 means that the unit wakes up after sensing a single motion. Default is 3.
<s>: Sensitivity. How vigorous and consistent the motion must be every minute for the unit to determine it is in motion. The range is 1 to 26 where 1 requires the least motion and 26 requires the most motion.
Read Command: ^MSB? Returns the current state for this command.
Test Command: ^MSB=? Returns a fixed message indicating the ranges this can be set to.
B.135 ^PKTS ­ USE PACKETS
Exec Command: ^PKTS=<pkts> Set the unit to send data using packets during a data connection.
<pkts> can have the following values: Do not use packets

Document Number: 451-93156-002C

126 of 172

Use packets Use streaming encryption

AL3A-RM/A3LA-RM-MIL User Guide Version C

Read Command: ^PKTS? Query the current setting if the unit will use packets. Response is in the form:
^PKTS: <pkts>

Test Command: ^PKTS=? List the supported <pkts> Response is in the form:
^PKTS: (supported <pkts>s)

B.136 ^PKTST ­ PACKET SEND TIMER
Exec Command: ^PKTST=<timer> Sets the timeout interval for when to send a packet if the packet threshold size has not been reached.

<timer> can have the following values: 1..600 Timeout value in 10th of seconds

Read Command: ^PKTST? Query the current value of the send timeout if the packet size threshold is not reached. Response is in the form:
^PKTST: <timer>

Test Command: ^PKTST=? List the supported <timer> Response is in the form:
^PKTST: (supported <timer>s)

B.137 ^PKTRT ­ PACKET RESEND TIMER
Exec Command: ^PKTRT=<timer> Sets the timeout interval for when to resend a packet if an acknowledgement has not been received.

<timer> can have the following values: 1..200 Timeout value in 10th of seconds.

Document Number: 451-93156-002C

127 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
Read Command: ^PKTRT? Query the current value of the packet resend timeout delay. Response is in the form:
^PKTRT: <pktrt>
Test Command: ^PKTRT=? List the supported <timer> Response is in the form:
^PKTRT: (supported <timer>s)
B.138 ^PKTTH ­ PACKET SEND THRESHOLD
Exec Command: ^PKTTH =<threshold> Set the threshold size in bytes of the payload of a packet.
<threshold> can have the following values: 1..112 Size in bytes of the payload of a packet.
Read Command: ^PKTTH? Query the current value of the packet payload threshold. Response is in the form:
^PKTTH: <threshold>
Test Command: ^PKTTH=? List the supported <threshold> Response is in the form:
^PKTTH: (supported <threshold>s)
B.139 ^RESETMODEMTG ­ RESET MODEM TOGGLE
Exec Command: ^RESETMODEMTG Causes the modem to toggle its power state. When the controller receives this it brings the modem's on/off pin to ground for 300ms and releases it. Command must be the only command following the AT.
B.140 ^RESETMODEMVF ­ RESET MODEM VERIFY
Exec Command: ^RESETMODEMVF Causes the modem to be recovered and to have the recovery verified. When the controller receives this it runs the same code as is run when the checks have failed. Command must be the only com

Document Number: 451-93156-002C

128 of 172

B.141 ^RLE ­ USE RUN LENGTH ENCODING

AL3A-RM/A3LA-RM-MIL User Guide Version C

Exec Command: ^RLE=<rle> Set the modem to utilize run length encoding for data transfers.

<rle> can have the following values: Do not use run length encoding Use run length encoding

Read Command: ^RLE? Query the current setting if the unit will use packets. Response is in the form:
^RLE: <rle>

Test Command: ^RLE=? List the supported <rle> Response is in the form:
^RLE: (supported <rle>s)

B.142 ^SE ­ CONFIGURE STREAMING ENCRYPTION

Exec Command: ^SE=<imei>,<blocks>,<timeout> <imei>: Whether or not to send the unencrypted IMEI at the beginning of the call.
0 Do not send IMEI (Default) 1 Send IMEI
<blocks>: Max number of encrypted blocks to send before a sync byte is required. Allowable range is 1 - 255. Default is 1.
<timeout>: Milliseconds to wait before sending a partial block. Allowable range is 1 ­ 65535 in units of milliseconds. Default is 1000.
Note: The timeout value will be rounded up to the nearest tens of milliseconds.
Read Command: ^SE?

Read command returns the current streaming encryption settings. Response is in the form:

Document Number: 451-93156-002C

129 of 172

^SE: =<imei>,<blocks>,<timeout>

AL3A-RM/A3LA-RM-MIL User Guide Version C

Test Command: ^SE=? Test command returns lists of memory storages supported by the A3LA-RM. Response is in the form: ^SE: (list of supported <imei >s),(list of supported <blocks>s), (list of supported <timeout>s)
mand following the AT.
B.143 ^SMSD ­ SMS DELETE
Exec Command: ^SMSD=<n> This command deletes a message from SMS flash memory. <n>: The index of the message to delete. The index must be between 1 and 100.
Test Command: ^SMSD=? Returns a fixed message indicating the range of acceptable values.
B.144 ^SMSE ­ SMS ERASE
Exec Command: ^SMSE This command erases the SMS flash memory. This command is a synonym for ^CMGEC.
B.145 ^SMSR ­ SMS READ
Exec Command: ^SMSR[=<index>] This command will display the message from SMS flash memory for the provided index or all of the messages in SMS flash memory if the index is not specified. <index>: The index of the message to display. The index must be between 1 and 100.
Read Command: ^SMSR? Returns the number of messages in SMS flash memory.
Test Command: ^SMSR=? Returns a fixed message indicating the range of acceptable values.

Document Number: 451-93156-002C

130 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
B.146 ^SSI ­ SEND START-UP INFORMATION
Exec Command: ^SSI=<n> This command sets whether or not to display the start-up information. <n>:
0 Do not display the start-up information 1 Display the start-up information

Read Command: ^SSI? Returns the current value

Test Command: ^SSI=? Returns a fixed message indicating the range of acceptable values.

B.147 ^STR ­ SELF TEST RUN (ENCRYPTION)
Exec Command: ^STR Cause the modem to run self-test. This is the same test performs by the modem at each power up.

B.148 ^UE ­ USE ENCRYPTION
Exec Command: ^UE=<password>,<n> Set the modem on whether to use encryption or not at power up. The factory-default setting is not to use encryption at power up. Setting the ^UE command will take effect only after power has been cycled. This command will return an error if the encryption password has not been set.

<password>:The Crypto Officer Password which must be enclosed by two single quotes (` `)

<n>:

0 is not to use encryption and 1 is to use encryption at power up

Read Command: ^UE? Returns whether <n> is set to 0 or 1 and then one of the following messages will appear:
"Encryption Disabled No Keys Entered"

Document Number: 451-93156-002C

131 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
("Encryption Currently Enabled" OR "Encryption Currently Disabled") AND ("Set to be Enabled Next Power Cycle" OR "Set to be Disabled Next Power Cycle") "Encryption Feature Not Included"
B.149 ^VOLB ­ VOLUME BOOST
Exec Command: ^VOLB=<n> This command controls the volume boost function. Enabling it will increase the analog audio output by 16dB <n>:
0 Disable volume boost 1 Enable volume boost
Read Command: ^VOLB? Returns the current value
Test Command: ^VOLB=? Returns a fixed message indicating the range of acceptable values.

Document Number: 451-93156-002C

132 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX C: S-REGISTER DEFINITIONS

S-registers allow control over specific A3LA-RM operations. Some S-registers contain a single numeric value. Other S-registers are bit mapped where individual bits, or sets of bits, control specific functions.

C.1 S-REGISTER COMMANDS
Commands allow S-registers to be read, written, or simply referenced (i.e., set a pointer to designate the current, referenced S-register). S-register commands are described in the following subsections.

Commands allow S-registers to be read, written, or simply referenced (i.e. set a pointer to designate the
current, referenced S-register). S-register commands are described in the following subsections.

C.1.1 SR ­ DIRECT S-REGISTER REFERENCE
Set a pointer to reference S-register r.

C.1.2 SR? ­ DIRECT S-REGISTER READ
Read the value of S-register r.

C.1.3

SR=N ­ DIRECT S-REGISTER WRITE
Set the value of S-register r to n, where n is a decimal value in the range 0 to 255.

C.1.4

REFERENCED S-REGISTER READ
Read the value of the current referenced S-register. The current referenced S-register is that which was last acted upon by a direct reference (ATSr), read (ATSr?), or write (ATSr=n) command.

C.1.5

=N ­ REFERENCED S-REGISTER WRITE
Set the value of the current referenced S-register to n. The current referenced Sregister is that which was last acted upon by a direct reference (ATSr), read (ATSr?), or write (ATSr=n) command.

Document Number: 451-93156-002C

133 of 172

C.2 STANDARD S-REGISTERS

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 5: Standard S-Registers

Register Number

Range

Default Description

Sr=n Command Write-Protected in SAC0201

S3

0 ­ 127 13

Carriage return character

S4

0 ­ 127 10

Line feed character

S5

0 ­ 32 8

Backspace character

Wait for dial tone

S6

0 ­ 255 4

No action, compatibility only

Communication standard used by A3LA-

S7

0 ­ 255 50

RM

No action, compatibility only

Pause time for comma

S8

0 ­ 255 4

No action, compatibility only

Carrier detect response time

S9

0 ­ 255 6

No action, compatibility only

Carrier loss time

S10

0 ­ 255 14

No action, compatibility only

DTMF tone duration

S11

0 ­ 255 0

Yes

No action, compatibility only

Escape guard time. Time, in 50ths of a

S12

0 ­ 255 40

second, until OK displayed after entering

command mode by escape sequence.

Bitmap register where bit 1 reflects the En

S14

0 ­ 255 170

setting, bit 2 turns off command responses, bit 3 reflects the Vn setting, and

bit 5 reflects pulse/tone dial mode.

Document Number: 451-93156-002C

134 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 5: Standard S-Registers

Register Number

Range

Default Description

Sr=n Command Write-Protected in SAC0201

Bitmap register where bit 0 reflects

telephone jack control, bit 2 reflects

S21

0 ­ 255 48

RTS/CTS on/off, bits 3 and 4 reflect the &Dn setting, bit 5 reflects the &Cn setting,

Yes

bit 6 reflects DSR on/off, and bit 7 reflects

disconnecting long space.

Bitmap register where bits 0 and 1 reflect

S22

0 ­ 255 246

the speaker volume setting, bits 2 and 3 reflect the speaker on/off setting, and bits

Yes

4, 5 and 6 reflect the Xn setting.

Bitmap register:

bit 0: autobaud setting

S23

0 ­ 255 61

bits 1-3: DTE baud rate

Yes

bits 4-5: parity

bits 6-7: guard tone

S25

0 ­ 255 5

Sets length of time in hundredths of a second that a change in the DTR status has to persist for before it is recognized.

S27

0 ­ 255 9

Bitmap register where bits 0, 1 and 3

reflect the &Qn setting, bit 3 reflects leased line operation setting, and bits 4

Yes

and 5 reflect synchronous clock setting.

S30

0 ­ 255 0

Disconnect activity timer. Timer used to determine how long the call connection has been inactive, in increments of 1/10000 ms. A value of 0 disables this function.

S31

0 ­ 255 0

Bitmap register where bit 1 reflects line modulation method setting, and bits 2 and Yes 3 reflect the Wn setting.

Document Number: 451-93156-002C

135 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 5: Standard S-Registers

Register Number

Range

Default Description

Sr=n Command Write-Protected in SAC0201

Bitmap register where bits 0, 1, and 2

S36

0 ­ 255 7

reflect the link type setting.

Yes

No action, compatibility only

S39

0 ­ 255 3

Bitmap register where bits 0, 1 and 2 reflect the &Kn setting.

Yes

Bitmap register where bits 2, 3, and 4

reflect the \K setting, and bits 6 and 7

S40

0 ­ 255 192

reflect the \An setting, bits 3-5 reflects the Yes

\Kn setting.

No action, compatibility only

S41

0 ­ 255 3

Bitmap registers where bits 2 and 6 enable retrain on bad signal quality setting, bit 4 reflects xon/xoff usage setting, and bit 5 Yes reflects DTE auto rate adjustment setting.
No action, compatibility only

S95

0 ­ 255 0

Bitmap register for extended result codes (overrides Wn setting). 0 = CONNECT shows DCE speed 2 = Enable CARRIER XXXX 3 = Enable PROTOCOL: XXXX
5 = Enable COMPRESSION: XXXX

Document Number: 451-93156-002C

136 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
C.3 IRIDIUM SPECIFIC S-REGISTER EXTENSIONS

Table 6: Iridium Specific S-Register Extensions

Register Number

Range Default

Description

Sr=n Command Write-Protected
in SAC0201

Bitmap register where bits 0­1 reflect

S13

0 ­ 255 0

the DCE data bits, bits 2­3 reflect the DCE stop bits, bits 4­6 reflect the DCE

Yes

parity settings, and bit 7 is not used.

Auto-answer mode selection

Bits 0­1: 0 (auto-answer voice and data

S15

0­2 0

calls)

1 (auto-answer voice calls only)

2 (auto-answer data calls only)

Bitmap register where bit 7 reflects the

S34

0 ­ 255 0

+DR setting, bits 0­1 reflect the data compression type (PT), and bit 6 reflects

Yes

the +DS compression negotiation setting.

S35

0 ­ 255 5

Bearer service capabilities

GSM Call clearing code as returned by

S42

0 ­ 255 0

the network. Refer to GSM 04.08 [7] Table 10.86 Cause Information Element

Yes

Values.

Bitmap register:

0 = +CMGF setting

1 = +CBST parameter <name> setting

2 = +CMEE setting

S43

0 ­ 255 32

Yes

3 = +CMEE setting

5 = +CBST parameter <ce> setting

6 = +CRC setting

7 = +CR setting

Document Number: 451-93156-002C

137 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 6: Iridium Specific S-Register Extensions

Register Number

Range Default

Description

Sr=n Command Write-Protected
in SAC0201

Bitmap register:

0­2 = +CPBS setting

S44

0 ­ 255 4

Yes

5-6 = +CREG setting

7 = +CLIP setting

Bitmap register:

0­1 = +CNMI parameter <mode> setting

S45

0 ­ 255 0

2­3 = +CNMI parameter <mt> setting

Yes

4­5 = +CNMI parameter <bm> setting

6­7 = +CNMI parameter <ds> setting

S47

0 ­ 255 0

Bits 4, 5, and 6 reflect TON settings for dial string

S49

0 ­ 255 1

Bits 0­3 reflect NPI settings for dial string

S51

0 ­ 255 0

V.42bis maximum codewords (P1), high byte

Yes

S52

0 ­ 255 128

V.42bis maximum codewords (P1), low byte

S54

0 ­ 255 20

V.42bis maximum string size (P2)

S58

0 ­ 255 0

V.42bis compression direction (P0)

S96

0 ­ 255 0

IRLP version number (N0) parameter

S98

0 ­ 105 105 IRLP k iwf->isu parameter

S99

0 ­ 105 105 IRLP k isu->iwf parameter

S100

1 ­ 15 15

IRLP N2 parameter

S102

26 ­ 255 30

IRLP T1 parameter

S103

10 ­ 255 10

IRLP T2 parameter

Document Number: 451-93156-002C

138 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 6: Iridium Specific S-Register Extensions

Register Number

Range Default

Description

Sr=n Command Write-Protected
in SAC0201

S104

4 ­ 255 4

IRLP T4 parameter

S106

1 ­ 10 10

IRLP riwf->isu parameter

S107

1 ­ 10 10

IRLP risu->iwf parameter

S112

0 ­ 255 0

SBD upload message sequence number (high byte)

Yes

S113

0 ­ 255 0

SBD upload message sequence number (low byte)

Yes

Bitmap register:

bit 0: +SBDMTA setting (SBD ring indication)

S121

0 ­ 31 1

bits 1-2: +SBDAREG setting (SBD

Yes

automatic registration)

bit 3: +CCWA<n> setting

bit 4: +GPSSTA<n> setting

S122

0 ­ 31 0

Bitmap register:

bit 0: unused:

Yes

bits 1-3: +CIER setting (indicator event

reporting)

Bitmap register:

bit 0: unused

bit 1 = +WTM

S123

0 ­ 255 8

Yes

bit 2 = +WDLDM<dldm>

bit 3 = +WIRLP<mode>

bits 4-5 = +WFRNG

Dynamic link measurement interval

S124

0 ­ 255 15

(+WDLM <mi> setting). Value in 1000 ms

unit.

Document Number: 451-93156-002C

139 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 6: Iridium Specific S-Register Extensions

Register Number

Range Default

Description

Sr=n Command Write-Protected
in SAC0201

Dynamic link delay measurement delay

S125

1 ­ 100 10

tolerance (+WDLM<dtl> setting). Value in

% unit.

S126

0 ­ 255 2

Bitmap register:

0 = Ignore &Dn command specified reaction to DTR ON to OFF transitions. Disconnect as reaction to Hn command. OK response given.

1 = Ignore &Dn command specified

Yes

reaction to DTR ON to OFF transitions.

Ignore Hn command. OK response given

2 = Comply with &Dn command specified reaction to DTR ON to OFF transitions. Disconnect as reaction to Hn command.

S127

0 255 0

Bitmap Register containing copies of MSVTR/MSVLS parameters:

Bit 0 = ­MSVTR: 0 = Disabled (default) 1 =

Enabled

Yes

Bit 1 = ­MSVLS: 0 = No Mute (default) 1 = Mute Enabled

Bits 2-5 = Reserved (see IID#2600)

Document Number: 451-93156-002C

140 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX D: SUMMARY OF RESULT CODES
The following tables list the result codes returned by the A3LA-RM.

Table 7: V.25ter/Hayes Result Codes

Numeric (V0)

Verbose (V1)

Description

0

`OK'

Acknowledges execution of command; voice call connection has been established.

1

`CONNECT'

Data call connection has been established.

2

`RING'

Incoming data or voice call received (unsolicited).

3

`NO CARRIER'

Data or voice call connection terminated.

4

`ERROR'

Command not accepted.

5

`CONNECT 1200'

Data call connection established at 1200 bps.

6

`NO DIALTONE'

No dial tone detected.

7

`BUSY'

Busy signal detected.

8

`NO ANSWER'

Data or voice call connection completion timeout.

9

`CONNECT 0600'

Data call connection established at 600 bps.

10

`CONNECT 2400'

Data call connection established at 2400 bps.

11

`CONNECT 4800'

Data call connection established at 4800 bps.

12

`CONNECT 9600'

Data call connection established at 9600 bps.

13

`CONNECT 7200'

Data call connection established at 7200 bps.

14

`CONNECT 12000'

Data call connection established at 12000 bps.

15

`CONNECT 14400'

Data call connection established at 14400 bps.

16

`CONNECT 19200'

Data call connection established at 19200 bps.

17

`CONNECT 38400'

Data call connection established at 38400 bps.

18

`CONNECT 57600'

Data call connection established at 57600 bps.

Document Number: 451-93156-002C

141 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 7: V.25ter/Hayes Result Codes

Numeric (V0)

Verbose (V1)

Description

19

`CONNECT 115200'

Data call connection established at 115200 bps.

40

'CARRIER 300'

Data rate detected at 300 bps.

44

'CARRIER 1200/75`

Data rate detected at V.23 backward channel.

46

'CARRIER 1200'

Data rate detected at 1200 bps.

47

'CARRIER 2400'

Data rate detected at 2400 bps.

48

'CARRIER 4800'

Data rate detected at 4800 bps.

49

'CARRIER 7200'

Data rate detected at 7200 bps.

50

'CARRIER 9600'

Data rate detected at 9600 bps.

51

'CARRIER 12000'

Data rate detected at 12000 bps.

67

`COMPRESSION: V.42bis'

Data call connected with V.42bis compression enabled.

69

`COMPRESSION: NONE' Data call connected with no data compression.

126

`SBDRING'

SBD ring alert received, indicating presence of a mobile-terminated SBD message at gateway.

127

`HARDWARE FAILURE: <subsys>,<error>'

Issued at initialization in case of a hardware failure.

as verbose

`+DR: V42B NONE'

Data call connected with no data compression.

as verbose

`+DR: V42B TD'

Data call connected with V.42bis compression enabled on transmit direction.

as verbose

`+DR: V42B RD'

Data call connected with V.42bis compression enabled on receive direction.

as verbose

`+DR: V42B'

Data call connected with V.42bis compression enabled on both transmit and receive direction.

Document Number: 451-93156-002C

142 of 172

Numeric (V0)
as verbose as verbose as verbose
as verbose
as verbose as verbose as verbose

AL3A-RM/A3LA-RM-MIL User Guide Version C
Table 8: GSM 7.07 Result Codes

Verbose (V1)

Description

`+CR: ASYNC' `+CR: REL ASYNC' `+CME ERROR: <error> `+CREG: <stat>[,<lac>,<ci>] `+CRING: ASYNC` `+CRING: REL ASYNC` `+CRING: VOICE`

Asynchronous transparent data connection Asynchronous nontransparent data Command not accepted Registration indication status (unsolicited if enabled) Asynchronous transparent data call indication Asynchronous nontransparent data Voice call connection

Table 9: GSM 7.05 Result Codes

Numeric (V0)

Verbose (V1)

Description

as verbose `+CMTI: <mem>,<index>'

SMS-DELIVER message indication (unsolicited if enabled).

as verbose

`+CMT: <alpha>],<length><CR><LF><pdu>' (PDU mode)

SMS-DELIVER message indication (unsolicited if enabled).

`+CDS:<length><CR><LF><pdu>' (PDU as verbose
mode)

SMS-STATUS-REPORT message indication (unsolicited if enabled).

as verbose `+CMS ERROR: <error>

SMS command failed.

Document Number: 451-93156-002C

143 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 10: Iridium Specific Result Codes

Numeric (V0)

Verbose (V1)

Description

as verbose `READY'

Ready to receive SBD binary message data from DTE.

as verbose `+AREG:<event>,<reg error>' Auto-registration event report.

as verbose `+CIEV:<sig><value>'

Indicator event report.

as verbose '+ADJANT:<deployed>'

User antenna adjustment is required.

Document Number: 451-93156-002C

144 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX E: INFORMATIVE EXAMPLES
The examples below are presented in two different formats. The format used in each example has no significance. A single format will be used in a future revision of this document.
E.1 UNIT IDENTIFICATION
When beginning to build a communication link, a general DTE application controlling the A3LARM should confirm the type of Iridium device to which it is connected.

Table 11: Unit Identification

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

AT+CGMI

Get manufacturer name

Iridium OK

AT+CGMM

Get model number

<model ID> OK

AT+CGMR

Get revision

Call processor version: <revision> DSP version: <revision> ... OK

AT+CGSN

Get IMEI

300001000000000 OK

Document Number: 451-93156-002C

145 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
E.2 SETTING THE DEFAULT CONFIGURATION
The DTE sets the A3LA-RM's default configuration to no flow control, SBD automatic notifications enabled.

To A3LA-RM (from DTE) AT&K0 AT+SBDMTA=1 AT&W0 AT&Y0

Table 12: Default Configuration To DTE (from A3LA-RM)

Description

Disable RTS/CTS flow control OK

Enable SBD ring indications OK

Store the configuration as

OK

profile 0

Select profile 0 as the power-up

OK

default

E.3 POWER-ON TO SENDING AN SBD MESSAGE
The DTE will power up the A3LA-RM, wait for the A3LA-RM to acquire the network, and send a 70-byte message.

To A3LA-RM (from DTE)
AT+CIER=1,0,1
AT+SBDWB=70

Table 13: Sending an SBD Message

To DTE (from A3LA-RM)

Description

Wait for DSR to become asserted

OK +CIEV: 1, 1

Enable service indication reporting (note that this can be stored in the default configuration)
Wait for the A3LA-RM to acquire the network

Document Number: 451-93156-002C

146 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 13: Sending an SBD Message

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

READY

<binary transfer>

Transfer message to A3LA-RM

0

AT+SBDIX

+SBDIX: 0, 23, 0, - Perform SBD session 1, 0, 0

AT+SBDD0

Clear the MO message buffer OK

E.4 SBD AUTOMATIC NOTIFICATION REGISTRATION
The DTE verifies its registration state, performs a registration in order to be able to receive automatic notifications, and enables automatic notification indications.

To A3LA-RM (from DTE) AT+SBDREG?
AT+SBDREG
AT+SBDREG?
AT+SBDMTA=1

Table 14: SBD Automatic Notification Registration

To DTE (from A3LA-RM)

Description

Query the A3LA-RM registration status

+SBDREG: 0 A3LA-RM is detached, i.e., unregistered

Tell the A3LA-RM to register for automatic notifications

+SBDREG: 2,0 A3LA-RM is now registered

Query the A3LA-RM registration status

+SBDREG: 2 A3LA-RM is registered

Enable SBD ring indications from A3LA-RM to DTE

Document Number: 451-93156-002C

147 of 172

To A3LA-RM (from DTE)

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 14: SBD Automatic Notification Registration

To DTE (from A3LA-RM)

Description

OK

E.5 SBD AUTOMATIC NOTIFICATION MESSAGE RECEPTION
The DTE verifies its registration state. Upon receiving automatic notification, the DTE initiates an SBD session to receive an MT message.

Table 15: SBD Automatic Notification Message Reception

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

AT+SBDREG?

Query the A3LA-RM registration status

+SBDREG: 2

A3LA-RM is registered

...

Vendor application sends an MT message to the GSS

+SBDRING

A3LA-RM indicates an incoming message. The RI line also toggles.

AT+SBDIXA

DTE initiates an SBD session in answer to the automatic notification

+SBDIXA:0,23,1,237,90,2

A3LA-RM informs DTE that a 90-byte message was successfully received with MTMSN 237, and that two further MT messages are queued at the GSS

AT+SBDRB

<binary transfer>

DTE retrieves the received message from the A3LA-RM

Document Number: 451-93156-002C

148 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
E.6 SBD AUTOMATIC NOTIFICATION AUTOMATIC REGISTRATION
The DTE verifies its registration state and enables automatic registration using the "Ask" mode.

Table 16: SBD Automatic Notification Automatic Registration

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

AT+SBDREG?

Query the A3LA-RM registration status

+SBDREG: 2 A3LA-RM is registered

AT+SBDAREG=2

DTE sets the automatic registration to "Ask" mode OK

...

A3LA-RM is moved

+AREG: 0, 0 A3LA-RM notifies DTE that it needs to register

AT+SBDREG

DTE instructs the A3LA-RM to register

+SBDREG: 2, 0 Registration is successful

E.7 ORIGINATING A DATA CALL
An example of how to make a data call is given below:

Table 17: Originating a Data Call

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

AT+CBST=6,0,1

Asynchronous modem 4800 bps and IRLP OK

AT+CR=1

Enable reporting OK

ATD1234567890

Dial remote modem OK

Document Number: 451-93156-002C

149 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 17: Originating a Data Call

To A3LA-RM (from DTE)

To DTE (from A3LA-RM)

Description

+CR: REL ASYNC

Call connected at DTE rate of 9600 CONNECT ASYNC 9600

E.8 ANSWERING A DATA CALL
The A3LA-RM is capable of accepting mobile-terminated data calls. The following is a sequence of commands that can be used to establish the connection.

To A3LA-RM (from DTE)
ATA
ATS0=2

Table 18: Answering a Data Call

To DTE (from A3LA-RM)

Description

RING

Indicates arrival of call request

Manually answer the call

CONNECT 9600 Call connected at DTE rate of 9600

To automatically answer a call, register 0 should be set to a non-zero value

RING

Indicates arrival of call request

CONNECT

Call connected at DTE rate of 9600

E.9 DISCONNECTING A DATA CALL

To A3LA-RM (from DTE)
AT+CBST=6,0,1
AT+CR=1

Table 19: Disconnecting a Data Call

To DTE (from A3LARM)

Description

Asynchronous modem 4800 bps and

OK

IRLP

Enable reporting

Document Number: 451-93156-002C

150 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 19: Disconnecting a Data Call

To A3LA-RM (from DTE)

To DTE (from A3LARM)

Description

OK

ATD1234567890

Dial remote modem OK

+CR: REL ASYNC

Call connected at DTE rate of 9600 CONNECT ASYNC 9600

...

...

Data transfer

<+++>

Send escape sequence OK

ATH0

Hang up call OK

E.10 COORDINATION OF +CLCC AND +CPAS RESPONSES
In order to determine the call state of the A3LA-RM, the +CLCC and +CPAS commands may be used. The following table demonstrates how the output of the two commands, as well as the Extended Ring Message, can be combined to provide a more detailed definition of the call state than any one of the results provides by itself.

Table 20: Coordination of +CLCC and +CPAS Responses

Call State

+CLCC Response

+CPAS Response

Extended Ring Message

Idle

+CLCC: 006

+CPAS: 000 or 003

n/a

Handset dialing ­ Voice

+CLCC: 002

+CPAS: 000 or 003

n/a

ATD dialing ­ Voice command aborts call

command aborts call

n/a

Document Number: 451-93156-002C

151 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Table 20: Coordination of +CLCC and +CPAS Responses

Call State

+CLCC Response

+CPAS Response

Extended Ring Message

ATD dialing ­ Data command aborts call

command aborts call

n/a

Alerting after ATD dialing ­ Voice

command aborts call

command aborts call

n/a

Alerting after ATD dialing ­ Data

command aborts call

command aborts call

n/a

Ringing ­ Voice

+CLCC: 004

+CPAS: 003 CRING: VOICE

Ringing ­ Data

+CLCC: 004

+CPAS: 003 CRING: DATA

In call ­ Voice

+CLCC: 000

+CPAS: 000 or 003

n/a

In call ­ Data

+CLCC: 000

+CPAS: 004 n/a

On hold ­ Voice

+CLCC: 001

+CPAS: 000 or 003

n/a

Call waiting ­ Voice

2 or more call states, one of which +CPAS: 000 or

is 004, e.g., +CLCC: 000,004

003

n/a

Document Number: 451-93156-002C

152 of 172

APPENDIX F: POWER CONSUMPTION

AL3A-RM/A3LA-RM-MIL User Guide Version C

This section provides the electrical power profile of the A3LA-RM. It does not describe every situation; however, it does offer a starting point to continue your own development design. The actual usage profile can vary for a number of reasons, including manufacturing variation from unit-to-unit. Optimize your setup to attain the lowest possible power consumption. Some of the setup parameters to be carefully observed include:

1. Have a clear view of the sky for the antenna--poor visibility of the sky is when a clear line-of-sight is not available between the A3LA-RM and the satellites.

2. Keep the antenna's VSWR low--the higher the antenna VSWR, the higher the current consumed by the A3LA-RM.

3. Keep the antenna cables' loss to less than 3 dB--the higher the antenna cable loss, the higher the current consumed by the A3LA-RM.

4. Keep the power cable between the A3LA-RM and the power source as short as possible.

5. Use both power input pins on the multi-interface connector.

Power consumption of the A3LA-RM can be divided into five distinct operating segments: (1) standby, (2) data-switch/RUDICS call, (3) SBD transmission, (4) SMS transmission, and (5) audio call. Typical current drawn and power consumption for these cases are shown in plots below.

The A3LA-RM is designed to accept input power at two different voltage ranges--either from 4.0 V to 5.4 V or from 5.0 V to 32 V. A different internal DC-DC converter is used for each range. In each figure below, electrical profile for both ranges are displayed in separate curves.

The A3LA-RM can be connected to a DPL handset through an HRC-24-8R data kit to make voice calls. The DPL handset requires 12 V, which is supplied by the A3LA-RM through pin 2 of the multi-interface connector. When the DPL handset is on with the backlight turned on, the DPL handset current drawn is about 350 mA at 12 V or about 500 mA at 5 V. Therefore, when a DPL handset is connected to an A3LA-RM, you must account for the added current drawn.

Document Number: 451-93156-002C

153 of 172

Current (A)

AL3A-RM/A3LA-RM-MIL User Guide Version C
0.20
4.0V to 5.5V 5.0V to 32V
0.15

0.10

0.05

0.00 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 6: Average Current Drawn During Standby

1.25 1.00

4.0V to 5.5V 5.0V to 32V

0.75

0.50

0.25 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 7: Average Power Consumption During Standby

Power (W)

Document Number: 451-93156-002C

154 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
0.8
4.0V to 5.5V 5.0V to 32V
0.6

Current (A)

0.4

0.2

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 8: Average Current Drawn During Standby with DPL Handset

4
4.0V to 5.5V 5.0V to 32V
3

Power (W)

2

1

0

0

5

10

15

20

25

30

35

Voltage (DC)

Figure 9: Average Power Consumption During Standby with DPL Handset

Document Number: 451-93156-002C

155 of 172

Current (A)

AL3A-RM/A3LA-RM-MIL User Guide Version C
0.8
4.0V to 5.5V 5.0V to 32V
0.6

0.4

0.2

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 10: Average Current Drawn During a Data Switch Call

4
4.0V to 5.5V 5.0V to 32V
3

2

1

0

0

5

10

15

20

25

30

35

Voltage (DC)

Figure 11: Average Power Consumption During a Data Switch Call

Power (W)

Document Number: 451-93156-002C

156 of 172

Current (A)

AL3A-RM/A3LA-RM-MIL User Guide Version C
0.5
4.0V to 5.5V 5.0V to 32V
0.4

0.3

0.2

0.1

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 12: Average Current Drawn During an SBD Transmission

2.0
4.0V to 5.5V 5.0V to 32V
1.5

1.0

0.5

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 13: Average Power Consumption During an SBD Transmission

Power (W)

Document Number: 451-93156-002C

157 of 172

Current (A)

AL3A-RM/A3LA-RM-MIL User Guide Version C
0.5
4.0V to 5.5V 5.0V to 32V
0.4

0.3

0.2

0.1

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 14: Average Current Drawn During an SMS Transmission

3.0
4.0V to 5.5V 5.0V to 32V
2.4

1.8

1.2

0.6

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 15: Average Power Consumption During an SMS Transmission

Power (W)

Document Number: 451-93156-002C

158 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
1.5
4.0V to 5.5V 5.0V to 32V
1.2

Current (A)

0.9

0.6

0.3

0.0 0

5

10

15

20

25

30

35

Voltage (DC)

Figure 16: Average Current Drawn During a Voice Call Using DPL Handset

6
4.0V to 5.5V 5.0V to 32V
5

Power (W)

4

3

2

0

5

10

15

20

25

30

35

Voltage (DC)

Figure 17: Average Power Consumption During a Voice Call Using DPL Handset

Document Number: 451-93156-002C

159 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX G: THE IRIDIUM NETWORK
The Iridium satellite network is owned and operated by Iridium Communications Inc. It is constructed as a constellation of 66 satellites in low-earth orbit (LEO), terrestrial gateways, and Iridium subscriber units (ISUs). An ISU can either be an Iridium satellite phone or various types of modems. The satellites are placed in an approximate polar orbit at an altitude of 780 km. There are 6 polar planes populated with 11 satellites per orbit constituting the 66-satellite constellation. The near polar orbits of the Iridium constellation provide truly real-time and global coverage from pole-to-pole.

Figure 18: Iridium Network Major Components
The Iridium network is designed to operate in the band of 1616.0 to 1626.5 MHz, although the exact frequencies used depend on the local regulating authorities and issued licenses in any particular region. Each satellite projects 48 beams on the surface of earth, which may be viewed as providing coverage cells on the ground similar to terrestrial systems. Each beam is approximately 600 km in diameter. The 66-satellite constellation has the potential to support a total of 3,168 spot beams; however, as the satellite orbits converge at the poles, overlapping

Document Number: 451-93156-002C

160 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
beams are shut down. The satellite footprint is approximately 4,700 km in diameter. Under each footprint, a satellite is power-limited to approximately 1,100 simultaneous circuits.
The Iridium network uses a time division duplex (TDD) method and transmits and receives in an allotted time window within the frame structure. Since the system is TDD, the ISUs transmit and receive in the same frequency band. The access technology is a frequency division multiple access/time division multiple access (FDMA/TDMA) method whereby an ISU is assigned a channel composed of a frequency and time slot in any particular beam. Channel assignments may be changed across cell/beam boundaries and are controlled by the satellite. The system provides an average link margin of 12 dB.
Although there are multiple gateways, a user is registered to a single gateway. The gateways perform call connection setup and administrative duties such as billing and resource management. The satellite constellation provides connectivity between users, from a user to the Iridium system gateway, and between gateways. Within the Iridium network architecture, the satellites are cross-linked, which allows ISU-to-ISU communication independent of gateway intervention once the call connection is established.
There are currently two commercial Iridium gateways located in Arizona, United States; and Fucino, Italy. The U.S. government owns and operates an Iridium gateway located in Hawaii, United States. Each gateway generates and controls all user information pertaining to its registered users, such as user identity, geolocation, and billing items. The gateway also provides connectivity from the Iridium system to the terrestrial-based networks such as the Public Switched Telephone Network (PSTN).
G.1 IRIDIUM NETWORK DATA CAPABILITIES
For data communications, the Iridium network supports five different modes of operation, as shown in Figure 19: dial-up data service, direct internet connection, SBD, SMS, and RUDICS.

Document Number: 451-93156-002C

161 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Figure 19: Iridium Network Data Capabilities
G.2 DIAL-UP DATA SERVICE
Dial-up data service provides connectivity through the Iridium satellite network to another Iridium modem, to the public switched telephone network (PSTN), to the Defense Switch Network (DSN), to a remote LAN (e.g., a corporate network), or to an internet service provider (ISP) at a nominal data rate of 2.4 kilobits per second (kbps). The connection time involving user authentication and handshaking (or modem training) can range from 15 to 30 seconds. For an Iridium-to-Iridium call, dial-up data service offers an additional option known as Data After Voice (DAV). Similar to a voice call, a DAV call is routed directly from one Iridium modem to another Iridium modem without going through the gateway.
Many desktop and laptop computers are equipped with either an internal or external modem to perform dial-up data applications across the landline telephone network (PSTN). On these computers, terminal emulator software or a dial-up networking connection can be configured

Document Number: 451-93156-002C

162 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
to a specific modem with a phone number to dial, user identification, and password. The modem can then be used to call another computer, a remote Local area network (LAN), or an Internet service provider(ISP), as shown in Figure 20. The handshaking and protocols are established between the modems independent of the landline.

Antenna
NAL Research

RS232

4.4 VDC

ISP (Internet)

Antenna
NAL Research

RS232

4.4 VDC

Corporate Network
Figure 20: PSTN Dial-up Connectivity
The Iridium dial-up data service, as shown in Figure 21, functions in much the same way as the PSTN dial-up connectivity. From the perspective of a computer, the Iridium modem is just another external modem. The only difference is that the dialed telephone number must conform to the international dialing pattern used by Iridium. When a data call is placed, the Iridium modem actually dials and initiates a connection with the Iridium gateway through the Iridium satellite constellation. Because the Iridium modem is requesting to establish a data connection, the switch at the gateway routes the call through another modem. The modem at the Iridium gateway then dials into and connects to another modem at the other end. Figure 21 illustrates how an Iridium dial-up data service call is routed. The handshaking and protocols established between the modems are independent of the Iridium network.
For those ISU-to-ISU dial-up calls where data transmission delay is critical, such as the application of TCP/IP protocol, DAV should be considered in the design. This option eliminates the Iridium gateway once authentication and registration is completed, allowing ISU-to-ISU communication without the gateway in the loop.

Document Number: 451-93156-002C

163 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C

Figure 21: Iridium Dial-up Data Service

G.3 DIRECT INTERNET CONNECTION

The Iridium Direct Internet service allows users to connect to the internet via the Iridium gateway without having to sign up with an internet service provider. This service utilizes a dedicated Apollo Server at the Iridium gateway, which provides high-speed connectivity to the internet and optimizes server-to-Iridium modem communications. The dial-up networking setup is similar to the dial-up networking setup for a landline telephone. The only difference is that the dialed telephone number is an international number provided by Iridium. Figure 21 illustrates how an Iridium internet call is routed.

Direct Internet service can be enhanced using Windows-based emulated point-to-point

protocol (PPP) called the Apollo Emulator. With the use of the Apollo Emulator software instead

of Microsoft Windows® dial-up networking, Direct Internet service can reduce connection time

and improve data throughput. In addition, the Apollo Emulator offers a feature called Smart

ConnectTM, which manages airtime by seamlessly connecting and disconnecting a user through

the Iridium system. Airtime charges accumulate only while the call is connected. Improved

Document Number: 451-93156-002C

164 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
effective data throughput is achieved through the use of user-transparent data compression. The channel rate is still 2.4 kbps. However, 10 kbps effective throughput can be achieved depending on content (graphics and images result in lower effective throughput).
G.4 SHORT BURST DATA
SBD is a simple and efficient bidirectional transport capability used to transfer messages with sizes ranging from zero (a mailbox check) to 1960 bytes. SBD takes advantage of signals within the existing air interface but without using the dedicated traffic channels. As a result, small amounts of data can be transferred more efficiently than those associated with circuit-switched data calls. Messages that originate from an Iridium modem can be delivered to a variety of destinations. Commonly, data are delivered across terrestrial communications networks (NIPRNet and internet) to servers and applications that process data from one or multiple fielded Iridium modems. SBD service also supports the transfer of messages to Iridium modems, where messages may originate from terrestrial sources. Delivery methods and options are initially configured when the Iridium modem is first purchased and may be easily modified via webpages at a later time.
G.5 SHORT MESSAGING SERVICE
SMS is a mechanism to deliver short data messages over the Iridium satellite network to the NIPRNet/internet. Iridium SMS incorporates a subset of the GSM SMS features. Each SMS message can be up to 160 text characters (7-bit coded) in length. The text characters are based on a 7-bit alphabet, which is encoded and transmitted as 8-bit data, hence the 140 octet (byte) maximum message size.
SMS is a store-and-forward method of transmitting messages to and from an Iridium modem. The short message from the modem is stored in a central Short Message Service Center (SMSC), which then forwards it to the destination. If the recipient is not available, the SMSC attempts to deliver the SMS message until it is delivered or the validity period expires. SMS supports a limited confirmation of message delivery. The sender of the short message can request to receive a return message notifying them whether or not the short message has been delivered. With this option, the originator gets a confirmation that the message was delivered to the

Document Number: 451-93156-002C

165 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
SMSC. Unlike standard GSM, the Iridium SMS can only acknowledge that the message was delivered to the SMSC and not the end destination.

SMS messages can be sent and received simultaneously while a voice call is in progress. This is possible because SMS messages travel over and above the radio channel using the signaling path, whereas the voice call uses a dedicated "traffic" radio channel for the duration of the call.

G.6 RUDICS
Router-based unrestricted digital internetworking connectivity solution (RUDICS) is an enhanced gateway termination and origination capability for circuit-switched data calls across the Iridium satellite network. When an Iridium modem places a call to the RUDICS Server located at the Iridium gateway, the RUDICS server connects the call to a predefined IP address, allowing an end-to-end IP connection between the host application and the Iridium modem. There are three key benefits of using RUDICS over the conventional PSTN circuit-switched data connectivity or mobile-to-mobile data solutions: (1) elimination of analog modem training time, (2) increased call connection quality, reliability, and maximized throughput, and (3) protocol independence.

G.7 IRIDIUM GEOLOCATION
The Iridium network makes calculations of the geographical location (geolocation) of an ISU each time a call is placed. The technique employed to determine the geolocation of an ISU is based on measurements of the ISU and satellite propagation delay and Doppler frequency shift. These measurements are used to estimate cosines of spherical angles that identify the ISU's location relative to the satellite by the gateway.

The Iridium network can locate an ISU to within 10 km only about 78% of the time. The so-

called error ellipse can have a large eccentricity with the major axis oriented in the azimuth

dimension and the minor axis oriented in the radial dimension. The position of the ISU in the

radial dimension relative to the satellite can almost always be determined to within 10 km with

just one measurement. Errors in the azimuth dimension relative to the satellite are largest

along the satellite's ground path and tend to increase with distance from the satellite.

Geolocation errors in the east-west dimension, therefore, are sometimes more than 100 times

greater than in the north-south dimension.

Document Number: 451-93156-002C

166 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX H: STANDARDS COMPLIANCE
The A3LA-RM comprises an Iridium 9523 L-band transceiver board. The 9523 is a regulatory approved daughter module transceiver that can be fitted within an enclosed host system. The 9523 is designed to comply with the standards for Radio Emissions Compliance, Electromagnetic Compatibility, and AC Safety in the United States, European Union, and Canada, assuming an antenna with a gain of ~3 dBi and adequate shielding.
FCC Compliance: The 9523 is certified under FCC CFR47 Parts 2, 15, and 25 as FCC ID: Q639523. Operation is subject to the condition that this device does not cause harmful interference. Any changes or modifications, including the use of a nonstandard antenna not expressly approved by the party responsible for compliance, could void the user's authority to operate the equipment.
CE Compliance: The 9523, when marked with the CE symbol, complies with the European Community Council Directive for R&TTE, 99/5/EC, provided that the integrator/user adheres to the instructions detailed in this LBT Interface Specification. This product is in compliance with applicable ETSI standards. Compliance with the requirements of ETSI EN 301 441 V1.1.1 requires the use of a shielded digital data interface cable.
Industry Canada: The 9523 is compliant with Industry Canada RSS-170 Issue 2 for RF Exposure.
Important: Output power listed is conducted. Peak power is 5.16 W and mean power is 0.48 W. The antenna gain, including cable loss, must not exceed 3 dBi. To comply with FCC RF exposure experiments, a minimum separation of 20 cm is required between the antenna and all persons. Additional testing and certification are required for applications that combine the 9523 with another radio element or are intended for use within 20 cm of a person.

Document Number: 451-93156-002C

167 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX I: MIL-STD-810G CERTIFICATION

Figure 22: Mil-STD-810G Certification
Document Number: 451-93156-002C

168 of 172

APPENDIX J: EXPORT COMPLIANCE

AL3A-RM/A3LA-RM-MIL User Guide Version C

The A3LA-RM is controlled by the export laws and regulations of the United States of America (USA). It is the policy of NAL Research to fully comply with all U.S. export and economic sanction laws and regulations. The export of NAL Research products, services, hardware, software and technology must be made only in accordance with the laws, regulations and licensing requirements of the U.S. government. NAL Research customers must also comply with these laws and regulations. Failure to comply can result in the imposition of fines and penalties, the loss of export privileges, and termination of your contractual agreements with NAL Research.

The export and re-export of NAL Research products and services are subject to regulation by the Export Administration Regulations (15 CFR 730-744), as administered by the U.S. Department of Commerce, Bureau of Industry and Security (BIS).

See: https://www.bis.doc.gov/index.php/regulations/export-administration-regulations-ear for further information on BIS and the Export Administration Regulations (EAR). Additional export restrictions are administered by the U.S. Department of the Treasury's Office of Foreign Asset Controls (OFAC). See: http://www.ustreas.gov/ofac for further information on OFAC and its requirements.

Document Number: 451-93156-002C

169 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
APPENDIX K: DESIGN SPECIFICATIONS

K.1 MECHANICAL SPECIFICATIONS
Dimensions:................................................................102 mm x 61 mm x 24 mm (4.0" x 2.43" x 0.95")
Weight:.......................................................................198 g (7.0 ounces) Multi-interface connector:.........................................25-pin male D-sub Iridium antenna: ........................................................TNC female connector SIM chip reader:.........................................................Located beneath a cover plate on top of the
A3LA-RM Status display: ............................................................Power, Iridium, and Status Cooling: ......................................................................Convection Enclosure:...................................................................Aluminum/EMI shielding

K.2 RF SPECIFICATIONS
Operating frequency: .................................................1616 to 1626.5 MHz Duplexing method: ....................................................TDD Multiplexing method: ...............................................TDMA/FDMA Link margin: ...............................................................12 dB average Average power during a transmit slot (max): ............7 W Average power during a frame (typical): ...................0.6 W Receiver sensitivity at 50 (typical):..........................­118 dBm

K.3 ELECTRICAL SPECIFICATIONS
Main input voltage range:..........................................+4.0 V to +5.4 V or +5.0 V to +32.0 V Average standby current: ..........................................~130 mA @ 5.0 VDC (with +5.0 V to +32.0 V
setup) Average data call current:..........................................~400 mA @ 5.0 VDC (peak of 2 A)

Note: The power requirements apply to DC power measured at the A3LA-RM multi-interface connector input. The average data call current may vary depending on the field of view between the modem antenna and the Iridium satellite.

Document Number: 451-93156-002C

170 of 172

AL3A-RM/A3LA-RM-MIL User Guide Version C
K.4 ENVIRONMENTAL SPECIFICATIONS
Operating temperature range: ..................................­30°C to +70°C (­22°F to +158°F) Operating humidity range:.........................................< 75% RH Storage temperature range: ......................................­40°C to +85°C (­40°F to +185°F) Storage humidity range: ............................................< 93% RH

K.5 DATA I/O SPECIFICATIONS
Dial-up data/RUDICS: .................................................2.4 kbps (average) Direct Internet: ..........................................................2.4 kbps (average) Short-burst data:........................................................1960 bytes for mobile-originated and 1890
bytes for mobile-terminated Short messaging:........................................................160 characters (maximum) Hardware interface: ...................................................RS232 Software interface: ....................................................Standard AT commands

K.6 RELATED HARDWARE
Antennas: ...................................................................SYN7391 series, SAF2040 series, SAF5340 series, SAF5350 series
Data kit/connector:....................................................HRC-24-7R, HRC-24-8R Power adapters:.........................................................LA-3098, LA-7021

Audio handset:

DPLS0401-X

Document Number: 451-93156-002C

171 of 172

APPENDIX L: MECHANICAL DRAWING

451-93156-002B

Document Number: 451-93156-002C

Figure 23: A3LA-RM Mechanical Drawing

172 of 172



References

• mailto:Support@Nalresearch.com
• Home - NAL Research
• Home - NAL Research
• Home - NAL Research