Iridium Satellite 9601 Satellite SBD Transceiver module type 9601 User Manual

Iridium Satellite LLC Satellite SBD Transceiver module type 9601

UserManual.wiki >

Iridium Satellite >

9601 User Manual

User manual

9601 Short Burst Data Onl y TransceiverPreliminary Product Developers GuideR ev i s io n 1 .2Au gus t 28 t h 2005Iridium Satellite LLC Proprietary & Confidential InformationIridium Satellite LLC6701 Democracy Blvd., Suite 500Bethesda, MD 20817 USAwww.iridium.comToll Free: +1.866.947.4348 [US Only]International +1.480.752.5155email: info@iridium.com

Iridium Satellite LLC9601 SBD Transceiver Preliminary Product Developers GuideV1.2 082905Iridium Satellite LLC Proprietary & Confidential InformationInformation contained herein is preliminary and subject to change without further notice2Preliminary Product Information Purpose & DisclaimerThis document contains preliminary product information for the new Iridium 9601 Short BurstData Transceiver. The purpose of providing this information is to enable Value Added Resellersand Value Added Manufacturers to begin to understand the product and how to integrate it into acomplete wireless data solution.By providing the information contained herein, Iridium Satellite LLC makes no guarantee orwarranty, and does not assume liability with respect to the accuracy or the completeness of suchinformation, or to the results of use of the planned product in any specific instance, and herebyexpressly disclaims any implied warranties of merchantability or fitness for a particular purpose,or any other warranties or representations whatsoever, expressed or implied.Iridium Satellite LLC reserves the right to modify or change specifications, detailed herein, at anytime without notice.Export Compliance InformationThis product is controlled by the export laws and regulations of the United States of America. The U.S.Government may restrict the export or re-export of this product to certain individuals and/or destinations.For further information, contact the U.S. Department of Commerce, Bureau of Industry and Security orvisit www.bis.doc.gov.Revision HistoryRevision Date CommentV1.0 May 02 2005 First revisionV1.2 Aug 28 2005Second revision incorporating major updates. Key updates are:Product name change to “9601 SBD Transceiver”Physical packagingConnector types updatedAT Commands added and updated

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 2of 51Information contained herein is preliminary and subject to change without further notice2.43 +SBDTC –Short Burst Data: Transfer MO Buffer to MT Buffer 282.44 -MSSTM –Request System Time 283 S-Register Definitions 303.1 S-Register Commands 303.1.1 Sr –Direct S-Register Reference 303.1.2 Sr? –Direct S-Register Read 303.1.3 Sr=n –Direct S-Register Write 303.1.4 ? –Referenced S-Register Read 303.1.5 =n –Referenced S-Register Write 313.2 S-Registers 314 Summary of Result Codes 385 Informative Examples 395.1 Setting the Default Configuration 395.2 Power-on to Sending a Message 405.3 Ring Alert Registration 415.4 Ring Alert Message Reception 425.5 Ring Alert Automatic Registration 435.6 Sending a Message with Minimal Radio Activity 445.7 Powering Down 456 Table of AT Command Changes 46

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 3of 51Information contained herein is preliminary and subject to change without further noticeGlossaryCTS (V.24 signal) Clear To Send. This signal is used to control the flowof data to the 9601DCD (V.24 signal) Data Carrier DetectDCE Data Communications Equipment. In this product, DCE refers tothe 9601DSR (V.24 signal) Data Set Ready. This signal, from the 9601, indicatesreadiness to accept communication over the data portDTE Data Terminal Equipment. In this product, DTE refers to the FADTR (V.24 signal) Data Terminal Ready. This signal, from the FA,requests the 9601 to accept communication over the data portESS ETC SBD Subsystem (synonymous with GSS)ETC Earth Terminal Controller, part of the Iridium GatewayFA Field Application, the “host” of the 9601GSS Gateway SBD Subsystem (synonymous with ESS)IMEI International Mobile Equipment IdentityMO Mobile OriginatedMOMSN Mobile Originated Message Sequence NumberMT Mobile TerminatedMTMSN Mobile Terminated Message Sequence NumberRI (V.24 signal) Ring Indicate. This signal, from the 9601, indicatesthat an MT message is present at the ESSRTS (V.24 signal) Request To Send. This signal is used to control theflow of data from the 9601.SBD Short Burst DataUART Universal Asynchronous Receiver Transmitter

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 4of 51Information contained herein is preliminary and subject to change without further notice1 IntroductionThis document specifies the AT Commands supported by the 9601 Transceiver.Informative examples are presented in Section 3.2 AT CommandsThe 9601 is configured and operated through the use of AT commands. Only ATCommands that are relevant to the 9601 are included. AT Commands related tofunctionality of the 9522 and 9522A LBTs are not included. Note that Commandsmay be modified, removed or added and that you should not rely on this documentas a definitive statement of the functionality of the commercial 9601 Transceiver.2.1 AT –ATtention CodeThis is the prefix for all commands except A/. When entered on its own, the 9601will respond OK.2.2 A/ - Repeat Last CommandRepeat the last command issued to the 9601 unless the power was interrupted orthe unit is reset. A/ is not followed by <CR>.2.3 En –EchoEcho command characters.0Characters are not echoed to the DTE.1Characters are echoed to the DTE (default).2.4 In –IdentificationRequests the 9601 to display information about itself.0“2400” (for compatibility only)1“0000” (for compatibility only)2“OK” (for compatibility only)3“XXXXXXXX” (Software revision level)4“IRIDIUM 9601” (Product description)5“8816” (for compatibility only)6“XXX” (Factory identity)

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 5of 51Information contained herein is preliminary and subject to change without further notice7“XXXXXXXX” (Hardware specification)2.5 Qn –Quiet ModeControl 9601 responses.09601 responses are sent to the DTE (default).19601 responses are NOT sent to the DTE.2.6 Vn –Verbose ModeSet the response format of the 9601, which may be either numeric or textual.0Numeric responses.1Textual responses (default).2.7 Zn –Soft ResetReset the 9601’s data port to a user-stored configuration that has been previouslystored using &Wn.0Restores user configuration 0.1Restores user configuration 1.2.8 &Dn –DTR Option (modified)Set the 9601 reaction to the DTR signal.0DTR is ignored. A DTR signal input is not needed when set to &D0.1-3 DTR must be ON. If DTR transitions from ON to OFF, the data portwill be locked after approximately 10 seconds to enter the UART testmode. The data port will resume when DTR is restored to ON.There is no distinction between settings 1-3. (default is 2)2.9 &Fn –Restore Factory SettingsRecall factory default configuration without resetting the data port.0Recall factory default 0.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 7of 51Information contained herein is preliminary and subject to change without further notice2.16 *Rn –Radio Activity (new)Control radio activity.0Disable radio activity.1Enable radio activity (default).While the radio is disabled:SBD sessions can not be initiated; they will fail immediately.No SBDRING alerts will be issued for automatic-MT messages.No registration, i.e. location updates will be performed.The baseband circuitry is still active and the 9601 still accepts AT commands.This command allows the FA to reduce detectable emissions from the RF circuitryduring the idle periods between SBD sessions, and also provides a degree ofpower saving in cases where it may be inconvenient for the FA to power down the9601.2.17 +CGMI –Manufacturer IdentificationExec Command: +CGMIQuery the 9601 manufacturer.2.18 +CGMM –Model IdentificationExec Command: +CGMMQuery the 9601 model.2.19 +CGMR –RevisionExec Command: +CGMRQuery the 9601 revision.2.20 +CGSN –Serial NumberExec Command: +CGSNQuery the 9601 IMEI.2.21 +CIER –Indicator Event Reporting (new)Set Command: +CIER=[<mode>[,<sigind>[,<svcind>[,<antind>]]]]

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 8of 51Information contained herein is preliminary and subject to change without further noticeThe set command enables or disables sending of the +CIEV unsolicited result codefrom the 9601 to the DTE in case of indicator state changes. <mode> controls theprocessing of the +CIEV unsolicited result codes.<mode>:0Disable indicator event reporting; do not send +CIEV unsolicited resultcodes to the DTE; buffer the most recent indicator event for eachindicator in the 9601 (default).1Enable indicator event reporting; buffer the most recent +CIEVunsolicited result code for each indicator when the data port isreserved (e.g. in SBD data mode) and flush them to the DTE afterreservation; otherwise forward them directly to the DTE.<sigind>:Control reporting of "signal quality" indicator changes:0No "signal quality" indicator reporting.1Enable "signal quality" indicator reporting using result code+CIEV:0,<rssi>where <rssi> is:0Equivalent to 0 bars on the signal strength indicator1Equivalent to 1 bars on the signal strength indicator2Equivalent to 2 bars on the signal strength indicator3Equivalent to 3 bars on the signal strength indicator4Equivalent to 4 bars on the signal strength indicator5Equivalent to 5 bars on the signal strength indicatorThe reported signal strength is the same value that would be returned by the +CSQcommand.When enabled, the signal quality indicator is reported only when the signal strengthchanges.<svcind>:Control reporting of "service availability" indicator changes:0No "service availability" indicator reporting.1Enable "service availability" indicator reporting using result code+CIEV:1,<value>

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 9of 51Information contained herein is preliminary and subject to change without further noticewhere <value> is:0Network service is currently unavailable.1Network service is available.Network service availability is equivalent to a signal strength greater than 0. Theservice availability indicator provides a way for the FA to wait until the 9601 canstart an SBD session without receiving continual notifications of changes in signalstrength.<antind>:Control reporting of "antenna fault" indicator changes:0No "antenna fault" indicator reporting.1Enable "antenna fault" indicator reporting using result code+CIEV:2,<value>where <value> is:0No antenna fault detected, or antenna fault cleared.1Antenna fault detected, further transmission impossible.An antenna fault indicates that the antenna is not correctly attached, and in orderto protect the transmitter no more transmissions are permitted. On seeing anantenna fault, the user should check the antenna connection; the fault will beautomatically cleared once the 9601 detects network service availability again.Read Command: +CIER?Query the current indicator event reporting settings. The response is of the form:+CIER:<mode>,<sigind>,<svcind>,<antind>Test Command: +CIER=?List the supported settings. The response is in the form:+CIER:(supported <mode>s),(supported <sigind>s),(supported <svcind>s),(supported <antind>s)Note: In <mode> 1, the DTE may miss some indicator state changes if they occurwhile the data port is reserved. However, the buffering mechanism ensures thatthe most recent change for each indicator during reservation will be flushed to theDTE after reservation; thus the DTE is always made aware of the latest state ofeach indicator.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 10 of 51Information contained herein is preliminary and subject to change without further noticeNote: The DTE may initiate an SBD session even if service is unavailable; in thiscase, the 9601 makes an immediate search for the network and, if successful,starts the SBD session, otherwise the SBD session fails.2.22 +CSQ –Signal QualityExec Command: +CSQExecution command returns the received signal strength indication <rssi> from the9601. Response is in the form:+CSQ:<rssi>where:<rssi>:0Equivalent to 0 bars displayed on the signal strength indicator.1Equivalent to 1 bar displayed on the signal strength indicator.2Equivalent to 2 bars displayed on the signal strength indicator.3Equivalent to 3 bars displayed on the signal strength indicator.4Equivalent to 4 bars displayed on the signal strength indicator.5Equivalent to 5 bars displayed on the signal strength indicator.Test Command: +CSQ=?List the supported signal strength indications. The response is in the form:+CSQ:(supported <rssi>s)Note: A signal strength response may not be immediately available, but will usuallybe received within two seconds of issuing the command. If the 9601 is in theprocess of acquiring the system, a delay in response of up to 10 seconds may beexperienced.2.23 +CULK –Unlock (new)Exec Command: +CULK=<unlock key>Unlock the Transceiver after it has been locked by the Gateway. The unlock keymust be obtained by contacting Iridium’s customer support.<unlock key>:0000000000000000 .. FFFFFFFFFFFFFFFFA string of 16 hexadecimal digits.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 11 of 51Information contained herein is preliminary and subject to change without further noticeWhile the Transceiver is locked, it is unable to perform any SBD sessions. Anyattempts to start a session will return an error code indicating that the Transceiveris locked.Command Response:+CULK:<status>where:<status> indicates the lock status of the Transceiver following the unlock attempt:0Unlocked –Transceiver is not locked and is permitted to performSBD sessions.1Locked –Transceiver is locked and unable to perform SBD sessions.It must be unlocked by supplying the correct unlock key to the +CULKcommand.2Permanently locked –Transceiver is locked and unable to performSBD sessions. It cannot be unlocked and must be returned to thesupplier.Read Command: +CULK?Query the current lock status of the Transceiver. The response is of the form:+CULK:<status><status>:0Unlocked1Locked2Permanently locked2.24 +GMI –Manufacturer IdentificationExec Command: +CGMIQuery the 9601 manufacturer.2.25 +GMM –Model IdentificationExec Command: +CGMMQuery the 9601 model.2.26 +GMR –RevisionExec Command: +CGMR

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 12 of 51Information contained herein is preliminary and subject to change without further noticeQuery the 9601 revision.2.27 +GSN –Serial NumberExec Command: +CGSNQuery the 9601 IMEI.2.28 +IPR –Fixed DTE RateSet Command: +IPR=<rate>Set the data rate at which the 9601 will accept commands. The change in data ratetakes into effect after the result code (e.g., OK) is received by the DTE.where:<rate>:1600 bps21200 bps32400 bps44800 bps59600 bps619200 bps (default)738400 bps857600 bps9115200 bpsRead Command: +IPR?Query the current data rate. The response is in the form:+IPR:<rate>Test Command: +IPR=?List the supported data rates. The response is in the form:+IPR:(supported <rate> settings)2.29 +SBDWB –Short Burst Data: Write Binary Data to the ModuleExec Command: +SBDWB=<SBD message length>

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 13 of 51Information contained herein is preliminary and subject to change without further noticeThis command is used to transfer a binary SBD message from the DTE to thesingle mobile originated buffer in the 9601. The mobile originated buffer cancontain only one message at any one time.Once the command is entered, and the message length is acceptable, the 9601will indicate to the DTE that it is prepared to receive the message by sendingthe 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 SBDmessage not including the mandatory two-byte checksum.The maximum mobile originated SBD message length is specified at 205 bytes(and may be increased following actual performance testing). The minimummobile originated SBD message length is 1 byte. If the <SBD message length>parameter is out of range, the 9601 issues response 3(see below).Once the DTE receives the READY indication from the 9601, the SBD messagemust 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 entireSBD message. The high order byte must be sent first. For example if theDTE were to send the word “hello” encoded in ASCII to the 9601 the binarystream 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:0SBD message successfully written to the 9601.1SBD message write timeout. An insufficient number of bytes weretransferred to 9601 during the transfer period of 60 seconds.2SBD message checksum sent from DTE does not match thechecksum calculated at the 9601.3SBD message size is not correct. The maximum mobile originatedSBD message length is 1960 bytes. The minimum mobile originatedSBD message length is 1 byte.2.30 +SBDRB –Short Burst Data: Read Binary Data from the ModuleExec Command: +SBDRB

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 14 of 51Information contained herein is preliminary and subject to change without further noticeThis command is used to transfer a binary SBD message from the single mobileterminated buffer in the 9601 to the DTE. The mobile terminated buffer can containonly 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 theSBD message not including the length field or the mandatory two-bytechecksum. The high order byte will be sent first.The maximum mobile terminated SBD message length is length is specifiedat 135 bytes (and may be increased following actual performance testing).The checksum is the least significant 2-bytes of the summation of the entireSBD message. The high order byte will be sent first. For example if the9601 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 fromthe 9601, 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 9601 for this command.2.31 +SBDWT –Short Burst Data: Write a Text Message to the ModuleExec Command: +SBDWT[=<text message>]This command is used to transfer a text SBD message from the DTE to the singlemobile originated buffer in the 9601.The text message may be entered on the command line:For example, “AT+SBDWT=hello”.The length of <text message> is limited to 120 characters. This is due to thelength limit on the AT command line interface.The message is terminated when a carriage return is entered.Alternatively, the text message may entered separately:Upon entering the command “AT+SBDWT”, the 9601 will indicate to the DTE thatit is prepared to receive the message by sending the string “READY<CR><LF>” (hex 52 45 41 44 59 0D 0A) to the DTE.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 15 of 51Information contained herein is preliminary and subject to change without further notice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 maximummobile-originated SBD 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:0SBD message successfully written to the 9601.1SBD message write timeout. An insufficient number of bytes weretransferred to 9601 during 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.2.32 +SBDRT –Short Burst Data: Read a Text Message from the ModuleExec Command: +SBDRTThis command is used to transfer a text SBD message from the single mobileterminated buffer in the 9601 to the DTE. This command is similar to +SBDRB butdoes not provide a length indicator or checksum. The intent of this command is toprovide a human friendly interface to SBD for demonstrations and applicationdevelopment. It is expected that most usage of SBD will be with binary messages.Once the command is entered, the SBD message in the mobile terminatedbuffer is sent out of the port.This command is similar to +SBDRB except no length or checksum will beprovided.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}

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 16 of 51Information contained herein is preliminary and subject to change without further notice2.33 +SBDI –Short Burst Data: Initiate an SBD SessionNote: The +SBDI command is provided for backwards compatibility with existingFAs which do not use SBD Ring Alert functionality. For SBD calls invoked with thiscommand:The SBD Session Type is fixed at type 0 –MO call.The SBD Delivery Short Code will be the value specified by the +SBDDSCcommand.The Detach/Attach flag is fixed at the Detach setting.The Location Update flag is fixed at the No Update setting.FAs requiring SBD Ring Alert functionality should use the extended +SBDIXcommand.Exec Command: +SBDIThis command initiates an SBD session between the 9601 and the GSS. If there isa message in the mobile originated buffer it will be transferred to the GSS.Similarly if there is one or more messages queued at the GSS the oldest will betransferred to the 9601 and placed into the mobile terminated buffer.The message, if any, in the mobile originated buffer will be sent from the 9601to the GSS.If there is a message queued at the GSS it will be transferred to the 9601 andplaced 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 originatedtransaction. The field can take on the following values:0No SBD message to send from the 9601.1SBD message successfully sent from the 9601 to the GSS.2An error occurred while attempting to send SBD message from 9601to GSS.<MOMSN>:The Mobile Originated Message Sequence Number (MOMSN) is a value assignedby the 9601 when sending a mobile-originated message to the GSS. This value is

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 17 of 51Information contained herein is preliminary and subject to change without further noticeincremented each time an SBD session is successfully completed between the9601 to the GSS. This wrap around counter can range from 0 to 65535.<MT status>:The MT status provides an indication of the disposition of the mobile terminatedtransaction. The field can take on the following values:0No SBD message to receive from the GSS.1SBD message successfully received from the GSS.2An error occurred while attempting to perform a mailbox check orreceive a message from the GSS.<MTMSN>:The Mobile Terminated Message Sequence Number (MTMSN) is assigned by theGSS when forwarding a message to the 9601. This value is indeterminate if thefield <MT status> is zero. This wrap around counter can range from 0 to 65535.<MT length>:The MT length is the length in bytes of the mobile terminated SBD messagereceived 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 tobe transferred to the 9601.2.34 +SBDDET –Short Burst Data: Detach (new)Exec Command: +SBDDETInitiates an SBD session to detach the Transceiver from the Gateway.Command Response:+SBDDET:<status>,<error>where:<status>:0Detach successfully performed1An error occurred while attempting the detach<error>:Gateway-reported values0No error.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 18 of 51Information contained herein is preliminary and subject to change without further notice1..4 Reserved, but indicate success if used.5..14 Reserved, but indicate failure if used.15 Access is denied.Transceiver-reported values16 Transceiver has been locked and may not make SBD calls (see+CULK command).17 Gateway not responding (local session timeout).18 Connection lost (RF drop).19..31 Reserved, but indicate failure if used.32 No network service, unable to initiate call.33 Antenna fault, unable to initiate call.34 Radio is disabled, unable to initiate call (see *Rn command).35 Transceiver is busy, unable to initiate call (typically performing auto-registration).36.. Reserved, but indicate failure if used.This instructs the Gateway to disable (detach) SBD ring alerts for the callingTransceiver. Successful completion of the detach command implies that theGateway has performed the requested detach action and the Transceiver is nolonger registered. This session does not transfer any MO or MT messages.Note: A user can send an MO-SBD message and request a detach at the sametime by using the +SBDI command. The +SBDI command always requests a detach.2.35 +SBDDSC –Short Burst Data: Delivery Short CodeSet Command: +SBDDSC=<dsc>Set the Delivery Short Code (DSC), which provides dynamic routing information foruploaded messages. This is an 8-bit value providing the ability to set individualfields. Value 0x80 (hexadecimal) sets the most significant bit. Value 0x01 sets theleast significant bit. Flag values can be added together to achieve a combinationof settings. Some fields may be “locked” when the Transceiver is in a specialmode (e.g. Autoregistration locks the flag values 0x80 and 0x40).<dsc>:0..255 DSC to be used for subsequent uploaded messages (0 default)0x80 Hold MT message delivery

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 19 of 51Information contained herein is preliminary and subject to change without further notice0x40 Leave MT message in queue after delivery0x20 Destination in MO payloadRead Command: +SBDDSC?Query the current Delivery Short Code. The response is of the form:+SBDDSC:<dsc>2.36 +SBDIX –Short Burst Data: Initiate an SBD Session Extended (new)Note: The +SBDIX command must be used in place of the +SBDI command for FAswishing to make use of SBD Ring Alert functionality.Exec Command: +SBDIX[A][=<location>]This command initiates an SBD session between the 9601 and the GSS, settingthe 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 isprovided. If there is a message in the mobile originated buffer it will be transferredto the GSS. Similarly if there is one or more messages queued at the GSS theoldest will be transferred to the 9601 and placed into the mobile terminated buffer.The message, if any, in the mobile originated buffer will be sent from the 9601to the GSS.If there is a message queued at the GSS it will be transferred to the 9601 andplaced into the mobile terminated buffer.This command will always attempt an SBD registration, consisting of attach andlocation update, during the SBD session in order to support SBD Ring Alert. Ifthis is not desired, the +SBDI command should be used.The FA should append an ‘A’ to the command, i.e. +SBDIXA, when the SBDsession is in response to a ring alert.<location> has format:[+|-]DDMM.MMM,[+|-]dddmm.mmmwhere: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)

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 20 of 51Information contained herein is preliminary and subject to change without further noticemmm Thousandths of minutes longitude (000-999)The optional sign indicators specify latitude North (+) or South (-), and longitudeEast (+) or West (-). If omitted, the default is +.For example,AT+SBDIX=5212.483,-00007.350corresponds to 52 degrees 12.483 minutes North, 0 degrees 7.35 minutes West.Command Response:+SBDIX:<MO status>,<MOMSN>,<MT status>,<MTMSN>,<MT length>,<MT queued>where:<MO status>:MO session status provides an indication of the disposition of the mobile originatedtransaction. The field can take on the following values:Gateway-reported values0MO message, if any, transferred successfully.1MO message, if any, transferred successfully, but the MT message inthe queue was too big to be transferred.2MO message, if any, transferred successfully, but the requestedLocation Update was not accepted.3..4 Reserved, but indicate MO session success if used.5..8 Reserved, but indicate MO session failure if used.10 Gateway reported that the call did not complete in the allowed time.11 MO message queue at the Gateway is full.12 MO message has too many segments.13 Gateway reported that the session did not complete.14 Invalid segment size.15 Access is denied.Transceiver-reported values16 Transceiver has been locked and may not make SBD calls (see+CULK command).17 Gateway not responding (local session timeout).18 Connection lost (RF drop).19..31 Reserved, but indicate MO session failure if used.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 21 of 51Information contained herein is preliminary and subject to change without further notice32 No network service, unable to initiate call.33 Antenna fault, unable to initiate call.34 Radio is disabled, unable to initiate call (see *Rn command).35 Transceiver is busy, unable to initiate call (typically performing auto-registration).36.. Reserved, but indicate failure if used.<MOMSN>:The Mobile Originated Message Sequence Number (MOMSN) is a value assignedby the 9601 when sending a mobile-originated message to the GSS. This value isincremented each time an SBD session is successfully completed between the9601 to the GSS. This wrap around counter can range from 0 to 65535.<MT status>:The MT status provides an indication of the disposition of the mobile terminatedtransaction. The field can take on the following values:0No MT SBD message to receive from the Gateway.1MT SBD message successfully received from the Gateway.2An error occurred while attempting to perform a mailbox check orreceive a message from the Gateway.<MTMSN>:The Mobile Terminated Message Sequence Number (MTMSN) is assigned by theGSS when forwarding a message to the 9601. This value is indeterminate if thefield <MT status> is zero. This wrap around counter can range from 0 to 65535.<MT length>:The MT length is the length in bytes of the mobile terminated SBD messagereceived 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 tobe transferred to the 9601.2.37 +SBDMTA –Short Burst Data: Mobile-Terminated Alert (new)Set Command: +SBDMTA=<mode>Enable or disable ring indications for SBD Ring Alerts.<mode>:

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 22 of 51Information contained herein is preliminary and subject to change without further notice0Disable ring indication1Enable ring indication (default)When ring indication is enabled, the 9601 asserts the RI line and issues theunsolicited 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)2.38 +SBDREG –Short Burst Data: Network Registration (new)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. The session type will be set to 2 –registration. This session does not transfer any MO or MT messages.Note: The Transceiver restricts the number of manual and automatic registrationsto one every 3 minutes. Successive attempts within 3 minutes will return an errorcode indicating that the FA should try later (see error 36 below).Note: A user can send an MO SBD message and register at the same time byusing the +SBDIX command. The +SBDIX command always performs a registrationattempt and should be used for an application requiring SBD Ring Alert. The +SBDIcommand never includes an SBD registration and should be used for anapplication that does not require SBD Ring Alert.<location> has format:[+|-]DDMM.MMM,[+|-]dddmm.mmmwhere: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)

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 23 of 51Information contained herein is preliminary and subject to change without further noticemmm Thousandths of minutes longitude (000-999)The optional sign indicators specify latitude North (+) or South (-), and longitudeEast (+) or West (-). If omitted, the default is +.For example,AT+SBDIX=5212.483,-00007.350corresponds 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 Transceiver:0Detached –Transceiver is detached as a result of a successful+SBDDET or +SBDI command.1Not registered –Transceiver is attached but has not provided a goodlocation since it was last detached.2Registered –Transceiver is attached with a good location. Note thatthis may be the case even when the most recent attempt did notprovide a good location.3Registration denied –The gateway is denying service to theTransceiver.4Unknown<reg err>:Gateway-reported values0No error.2Session completed but the requested Location Update was notaccepted.3..14 Reserved, but indicate Location Update failure if used.15 Access is denied.Transceiver-reported values16 Transceiver has been locked and may not make SBD calls (see+CULK command).17 Gateway not responding (local session timeout).18 Connection lost (RF drop).

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 24 of 51Information contained herein is preliminary and subject to change without further notice19..31 Reserved, but indicate failure if used.32 No network service, unable to initiate call.33 Antenna fault, unable to initiate call.34 Radio is disabled, unable to initiate call (see *Rn command).35 Transceiver is busy, unable to initiate call (typically performing auto-registration).36 Try later, must wait 3 minutes since last registration.37.. Reserved, but indicate failure if used.Read Command: +SBDREG?Query the current SBD registration status of the Transceiver. The response is ofthe form:+SBDREG:<status><status>:0Detached1Not registered2Registered3Registration denied4UnknownThe registration status is stored in Transceiver non-volatile memory, and cantherefore be queried by the FA after powering up.2.39 +SBDAREG –Short Burst Data: Automatic Registration (new)Set Command: +SBDAREG=<mode>Set the Transceiver’s Auto-registration mode.<mode>:0Disable automatic registration (default)1Set the Auto-registration mode to “Automatic”2Set the Auto-registration mode to “Ask”When auto-registration is enabled, mode 1 or 2, the Transceiver monitors itscurrent location and triggers an auto-registration when it determines that theTransceiver has moved sufficiently far away from its last registered location. Note

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 25 of 51Information contained herein is preliminary and subject to change without further noticethat auto-registration runs only while the Transceiver is attached to the gateway,i.e. the registration status is “Not registered” or “Registered”.Auto-registration may only be used with system-provided location. If the FA isproviding its own location (e.g. GPS), the FA should use the manual registrationcommand, +SBDREG.Upon triggering in mode 1, “Automatic”, the Transceiver autonomously initiates anSBD session in order to perform a registration with the updated location of theTransceiver, with the session type set to 3 –auto-registration. This session doesnot transfer any MO or MT messages.Upon triggering in mode 2, “Ask”, the Transceiver reports to the FA that it shouldregister with the system because the Transceiver location has changed (see<event> below); it is then the responsibility of the FA to register via +SBDREG or+SBDIX.+SBDIX allows the FA to register while including an MO message and/orretrieving an MT message that is pending at the Gateway.When auto-registration is enabled, mode 1 or 2, the Transceiver reports relevantevents to the FA by issuing an unsolicited result code +AREG:<event>,<reg error>.<event>:0Suggest FA makes a registration attempt (mode 2 only)1Auto-registration has been performed successfully (mode 1 only)2Auto-registration has failed and will be retried after a delay (mode 1only)<reg error>:Gateway-reported values0No error.2Session completed but the requested Location Update was notaccepted.3..14 Reserved, but indicate Location Update failure if used.15 Access is denied.Transceiver-reported values16 Transceiver has been locked and may not make SBD calls (see+CULK command).17 Gateway not responding (local session timeout).18 Connection lost (RF drop).19..31 Reserved, but indicate failure if used.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 26 of 51Information contained herein is preliminary and subject to change without further notice32 No network service, unable to initiate call.33 Antenna fault, unable to initiate call.34 Radio is disabled, unable to initiate call (see *Rn command).35 Transceiver is busy, unable to initiate call (typically performing auto-registration).36 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)2.40 +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 terminatedbuffer or both.The <Delete type> parameter identifies which buffers are cleared.0Clear the mobile originated buffer.1Clear the mobile terminated buffer.2Clear both the mobile originated and mobile terminated buffers.Using this command or power cycling the 9601 are the only means by whichboth buffers are cleared.The mobile terminated buffer will be cleared when an SBD session is initiated.Sending a message from the 9601 to the ESS does not clear the mobileoriginated buffer.Reading a message from the 9601 does not clear the mobile terminated buffer.Command Response:0Buffer(s) cleared successfully.1An error occurred while clearing the buffer(s).

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 27 of 51Information contained herein is preliminary and subject to change without further notice2.41 +SBDC –Short Burst Data: Clear SBD MOMSNExec Command: +SBDCThis command will clear (set to 0) the mobile originated message sequencenumber (MOMSN) stored in the 9601.The MOMSN is maintained even after power cycle.Command Response:0The MOMSN was cleared successfully.1An error occurred while clearing the MOMSN.2.42 +SBDS –Short Burst Data: StatusExec Command: +SBDSThis command returns current state of the mobile originated and mobile terminatedbuffers.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 9601 is one of the following numeric codes:0No message in mobile originated buffer1Message in mobile originated buffer<MOMSN>:The MOMSN identifies the sequence number that will be used during the nextmobile originated SBD session.<MT Flag>:The MT flag indicates the existence of a message in the mobile terminated buffer.The response from the 9601 is one of the following numeric codes:0No message in mobile terminated buffer1Message in mobile terminated buffer<MTMSN>:

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 28 of 51Information contained herein is preliminary and subject to change without further noticeThe MTMSN identifies the sequence number that was used in the most recentmobile terminated SBD session. This value will be –1if there is nothing in themobile terminated buffer.2.43 +SBDTC –Short Burst Data: Transfer MO Buffer to MT BufferExec Command: +SBDTCThis command will transfer the contents of the mobile originated buffer to themobile terminated buffer. Developers of DTE can use this command to test readingand writing to the 9601 without actually initiating SBD sessions with the ESS.Command Response:The command produces a response of the form “SBDTC: Outbound SBD copied toInbound SBD: size = <size>” followed by “OK”, where:<size>:The length of the message in bytes.2.44 -MSSTM –Request System TimeExec Command: -MSSTMQuery 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 9601 has not yet received system time from thenetwork.XXXXXXX Where XXXXXXXX is the current Iridium system timeavailable from the network. The system time as receivedthrough the Iridium Air Interface, is a 32 bit integer countof the number of 90 millisecond intervals that haveelapsed since the epoch. The return value is formattedas an ASCII hexadecimal number. The counter willrollover approximately every 12 years.Iridium system time epoch: June 1, 1996, 00:00:13 (GMT):Iridium system time source: The system time is available and valid only after the9601 has registered with the network and has received the Iridium system timefrom the network. Once the time is received, the 9601 uses its internal clock toincrement the counter. In addition, at least every 8 hours, or on location update orother event that requires re-registration, the 9601 will obtain a new system timefrom the network.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 29 of 51Information contained herein is preliminary and subject to change without further noticeTime localization: None. The system time value is always expressed in GMT time.Resolution and accuracy: The resolution of the system time is one Iridium frametick, or 90 ms. Accuracy as measured by the difference between the time reportedand the actual time it is sent out the 9601 serial port should not exceed 4 frameticks (.36 seconds) and in most cases will be one frame tick (.09 seconds) or less.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 31 of 51Information contained herein is preliminary and subject to change without further notice3.1.5 =n –Referenced S-Register WriteSet the value of the current referenced S-register to n. The current referenced S-register is that which was last acted upon by a direct reference (ATSr), read (ATSr?),or write (ATSr=n) command.3.2 S-RegistersTable 1: 9601 Transceiver S-RegistersRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S0 0-255 0 Autoanswer. Assigning a value from 1 to255 in register S0 tells the ISU toautomatically answer incoming calls.The factory setting of 0 turns off theautomatic answer feature. S1 0-255 0 Ring count S2 0-255 43 Escape code character  S3 0-127 13 Carriage return character S4 0-127 10 Line feed character S5 0-32 8 Backspace character S6 0-255 4 Wait for dial-tone.  S7 0-255 50 Communication standard used by ISU  S8 0-255 4 Pause time for comma.  S9 0-255 6 Carrier detect response time.  S10 0-255 14 Carrier loss time.  S11 0-255 0 DTMF tone duration. S12 0-255 50 Escape guard time. Time, in 50ths of asecond, until OK displayed afterentering command mode by escapesequence 

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 32 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S13 0-255 49 Bitmap register:bits 0-1: DCE data bitsbits 2-3: DCE stop bitsbits 4-6: DCE parity settingS14 0-255 170 Bitmap register:bit 1: En setting (echo)bit 2: Qn setting (quiet)bit 3: Vn setting (verbose)bit 5: Pulse/tone dial mode S21 0-255 48 Bitmap register:bit 0: Telephone jack controlbit 2: RTS/CTS on/offbits 3-4: &Dn setting (DTR operation)bit 5: &Cn settingbit 6: Disconnecting long spaceS22 0-255 246 Bitmap register:bits 0-1: speaker volume settingbits 2-3: speaker on/off settingbits 4-6: Xn settingS23 0-255 61 Bitmap register:bits 1-4: +IPR setting (DTE baud rate)bits 6-7: guard toneS25 0-255 5 Sets length of time in hundredths of asecond that a change in the DTR statushas to persist for before it is recognized. S27 0-255 9 Bitmap register:bits 0-2: &Qn settingbit 3: leased line operation settingbits 4-5: synchronous clock settingS28 0-255 0 Bitmap register:bits 3-4: &Pn setting (pulse dialmake/break ratio)

$Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 33 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S30 0-255 0 Disconnect activity timer. Timer used todetermine how long the call connectionbeen inactive, in increments of1/10000ms. A value of 0 disables thisfunction. S31 0-255 0 Bitmap register:bit 1: line modulation method settingbits 2-3: Wn settingS34 0-255 0 Bitmap register:bits 0-1: data compression type (PT)bit 6: +DS compression negotiationsettingbit 7: +DR settingS35 0-255 7 Bearer service capabilities  S36 0-255 0 Bitmap register:bits 0-2: link type settingS37 0-255 0 Bitmap register:bits 0-4: Fn setting (line modulationstandard)S39 0-255 3 Bitmap register:bits 0-2: &Kn setting (flow control)S40 0-255 104 Bitmap register:bits 2-4: \K settingbits 3-5: \Kn settingbits 6-7: \An settingS41 0-255 0 Bitmap registers:bits 2, 6: enable retrain on bad signalquality settingbit 4: xon/xoff usage settingbit 5: DTE auto rate adjustment setting$

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 34 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S42 0-255 16 GSM Call clearing code as returned bythe network. Refer to GSM 04.08 Table10.86 Cause Information ElementValues.S43 0-255 32 Bitmap register:bit 0: +CMGF settingbit 1: +CBST parameter <name> settingbit 2: +CMEE settingbit 3: +CMEE settingbit 5: +CBST parameter <ce> settingbit 6: +CRC settingbit 7: +CR settingS44 0-255 4 Bitmap register:bits 0-2: +CPBS settingbits 5-6: +CREG settingbit 7: reservedS45 0-255 0 Bitmap register:bits 0-1: +CNMI parameter <mode>settingbits 2-3: +CNMI parameter <mt> settingbits 4-5: +CNMI parameter <bm> settingbits 6-7: +CNMI parameter <ds> settingS47 0-255 0 Bitmap register:bits 4-6: TON settings for dial string S49 0-255 1 Bitmap register:bits 0-3: NPI settings for dial string S51 0-255 2 V.42bis maximum codewords (P1), highbyteS52 0-255 0 V.42bis maximum codewords (P1), lowbyte S54 0-255 6 V.42bis maximum string size (P2)  

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 35 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S58 0-255 3 V.42 bis compression direction (P0)  S95 0-255 0 Bitmap register for extended resultcodes (overrides Wn setting):bit 0: CONNECT shows DCE speedbit 2: Enable CARRIER XXXXbit 3: Enable PROTOCOL: XXXXbit 5: Enable COMPRESSION: XXXX S96 0-255 0 IRLP version number (N0) parameter S98 1-105 105 IRLP k iwf->isu parameter S99 1-105 105 IRLP k isu->iwf parameter S1001-15 15 IRLP N2 parameter S10226-255 30 IRLP T1 parameter S10310-255 10 IRLP T2 parameter S1044-255 25 IRLP T4 parameter S1061-10 10 IRLP riwf->isu parameter S1071-10 10 IRLP risu->iwf parameter S1100-1 0 SBM max segment size (40-310) (highbyte)S1110-255 135 SBM max segment size (40-310) (lowbyte)S1120-255 0 SBD upload message sequence number(high byte)

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 36 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S1130-255 0 SBD upload message sequence number(low byte)S1210-15 1 New for 9601 TransceiverBitmap register:bit 0: +SBDMTA setting (ring indication)bit 1-2: +SBDAREG setting (automaticregistration)S1220-31 1 New for 9601 TransceiverBitmap register:bit 0: *R setting (radio activity)bits 1-4: +CIER setting (indicator eventreporting)S1230-255 8 Bitmap register:bit 1: +WTMbit 2: +WDLDM<dldm>bit 3: +WIRLP<mode>bits 4-5: +WFRNGS1240-255 15 Dynamic link measurement interval(+WDLM <mi> setting). Value in 1000 msunitS1251-100 10 Dynamic link delay measurement delaytolerance (+WDLM<dtl> setting). Value in% unit

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 37 of 51Information contained herein is preliminary and subject to change without further noticeRegisterRangeDefaultDescriptionSr=nwritable?ProfileSetting?S1260-255 2 Bitmap register:bit 0: Ignore &Dn command specifiedreaction to DTR ON to OFF transitions.Disconnect as reaction to Hn command.OK response givenbit 1: Ignore &Dn command specifiedreaction to DTR ON to OFF transitions.Ignore Hn command. OK response givenbit 2: Comply with &Dn commandspecified reaction to DTR ON to OFFtransitions. Disconnect as reaction to Hncommand.S1270-255 0 Bitmap Register containing copies ofMSVTR/MSVLS parameters:Bit 0: -MSVTR: 0 = Disabled (default) 1 =EnabledBit 1: -MSVLS: 0 = No Mute (default) 1 =Mute Enabled

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 38 of 51Information contained herein is preliminary and subject to change without further notice4 Summary of Result CodesTable 2: Result codesNumeric (V0) Verbose (V1) Description0‘OK’Acknowledges execution of command2‘SBDRING’MT messages present at gateway(unsolicited if enabled). See section2.344‘ERROR’Command not accepted127 ‘HARDWARE FAILURE:<subsys>,<error>’Issued at initialisation in case of ahardware failure.as verbose ‘READY’Ready to receive binary message datafrom DTEas verbose ‘+AREG: <event>,<regerror>’Auto-registration event report. Seesection 2.39as verbose ‘+CIEV: <sig>,<value>’Indicator event report (unsolicited ifenabled). See section 2.21

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 40 of 51Information contained herein is preliminary and subject to change without further notice5.2 Power-on to Sending a MessageThe FA will power up the Transceiver, wait for the Transceiver to acquire thenetwork, and send a 70-byte message.To Transceiver(from FA) To FA (from Transceiver) DescriptionApply power to the 9601Wait for DSR to become assertedAT+CIER=1,0,1,0OKEnable service indication reporting (notethat this can be stored in the defaultconfiguration)+CIEV: 1,1 Wait for the 9601 to acquire the networkAT+SBDWB=70READY<binary transfer>0Transfer message to 9601AT+SBDIX+SBDIX: 0,23,0,-1,0,0Perform SBD sessionAT+SBDD0OKClear the MO message buffer

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 41 of 51Information contained herein is preliminary and subject to change without further notice5.3 Ring Alert RegistrationThe FA verifies its registration state, performs a registration in order to be able toreceive ring alerts, and enables ring alert indications.To Transceiver(from FA) To FA (from Transceiver) DescriptionAT+SBDREG? Query the Transceiver registration status+SBDREG:0 Transceiver is detached, i.e. un-registeredAT+SBDREG Tell the Transceiver to register for ringalerts+SBDREG:2,0 Transceiver is now registeredAT+SBDREG? Query the Transceiver registration status+SBDREG:2 Transceiver is registeredAT+SBDMTA=1OKEnable SBD ring indications fromTransceiver to FA

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 42 of 51Information contained herein is preliminary and subject to change without further notice5.4 Ring Alert Message ReceptionThe FA verifies its registration state. Upon receiving a ring alert the FA initiates anSBD session to receive an MT message.To Transceiver(from FA) To FA (from Transceiver) DescriptionAT+SBDREG? Query the Transceiver registration status+SBDREG:2 Transceiver is registered…Vendor application sends an MT messageto the GSS+SBDRING Transceiver indicates an incomingmessage. The RI line also toggles.AT+SBDIXA FA initiates an SBD session in answer tothe ring alert+SBDIXA:0,23,1,237,90,2 Transceiver informs FA that a 90-bytemessage was successfully received withMTMSN 237, and that two further MTmessages are queued at the GSSAT+SBDRB<binary transfer>FA retrieves the received message fromthe Transceiver

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 43 of 51Information contained herein is preliminary and subject to change without further notice5.5 Ring Alert Automatic RegistrationThe FA verifies its registration state and enables automatic registration using the“Ask” mode.To Transceiver(from FA) To FA (from Transceiver) DescriptionAT+SBDREG? Query the Transceiver registration status+SBDREG:2 Transceiver is registeredAT+SBDAREG=2OKFA sets the automatic registration to “Ask” mode…Transceiver is moved+AREG:0,0 Transceiver notifies FA that it needs toregisterAT+SBDREG FA instructs the Transceiver to register+SBDREG:2,0 Registration is successful

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 44 of 51Information contained herein is preliminary and subject to change without further notice5.6 Sending a Message with Minimal Radio ActivityAssuming that service indication events have been turned on with AT+CIER=1,0,1,and the radio has been disabled with AT*R0.To Transceiver(from FA) To FA (from Transceiver) DescriptionAT+SBDWB=70READY<binary transfer>0Transfer message to 9601AT*R1OKActivate the radio and wait for theTransceiver to acquire the network+CIEV:1,1 Transceiver has acquired the networkAT+SBDI+SBDI: 0,23,0,-1,0,0Perform SBD sessionAT*R0OKDeactivate the radioAT+SBDD0OKClear the MO message buffer

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 45 of 51Information contained herein is preliminary and subject to change without further notice5.7 Powering DownThe FA flushes any pending Eeprom writes before powering down the Transceiver.To Transceiver(from FA) To FA (from Transceiver) DescriptionAT*FOKFA tells Transceiver to flush pendingwrites to Eeprom and waits for completion<binary transfer> FA may now safely disconnect theTransceiver power supply.

Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 46 of 51Information contained herein is preliminary and subject to change without further notice6 Table of AT Command ChangesTable 3 shows which 9522A Transceiver AT commands are modified or removed,and which AT commands are new for 9601 Transceiver. Removed commands areshaded.Table 3: Changes to AT commandsCommand DescriptionModifiedNewAT Attention codeA/ Repeat last command+++ Escape sequenceAAnswerBn Communication standardsCn Carrier controlDDialEn EchoFn Line modulationHn HangupIn IdentificationLn Loudspeaker volumeMn Speaker controlNn Automode enableOn OnlinePPulse dialQn Quiet modeTTone dialVn Verbose modeWn Error correction message control

$Iridium Satellite LLC9601 Transceiver –AT Command ReferenceIridium Satellite LLC Proprietary & Confidential Information Page 47 of 51Information contained herein is preliminary and subject to change without further noticeCommand DescriptionModifiedNewXn Extended result codesYn Long space disconnectZn Soft reset&Cn DCD option&Dn DTR option &Fn Restore factory settings&Gn Guard tone&Jn Jack control&Kn Flow control &Ln Leased line operation&Mn Asynchronous/synchronous mode&Pn Pulse dial make/break ratio&Qn Sync/async mode&Rn RTS/CTS option&Sn DSR override&V View active and stored configuration&Wn Store active configuration&Xn Select asynchronous clock&Yn Designate default reset profile\An MNP block size\Bn Transmit break\Gn XON/XOFF flow control\Jn DTE auto rate\Kn Control break\Nn Link type$

Iridium Satellite 9601 Satellite SBD Transceiver module type 9601 User Manual

Iridium Satellite LLC Satellite SBD Transceiver module type 9601

User manual

Navigation menu

Namespaces

Views

Navigation