Iridium 9601 Product Developer Manual page 57

Short burst data transceiver
Hide thumbs Also See for 9601:
Table of Contents

Advertisement

Iridium Satellite LLC
9601 SBD Transceiver Preliminary Product Developers Guide Appendix A –AT Command Reference
V1.24 120505
2.42 +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 9601 is one of the following numeric codes:
No message in mobile originated buffer
0
Message in mobile originated buffer
1
:
<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 9601 is one of the following numeric codes:
No message in mobile terminated buffer
0
Message in mobile terminated buffer
1
:
<MTMSN>
The MTMSN identifies the sequence number that was used in the most recent mobile
terminated SBD session. This value will be
buffer.
2.43 +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 9601 without actually initiating SBD sessions with the ESS.
Command Response:
T h e c o mma n d p r o d u c e s a r e s p o n s e o f t h e f o r m "
" f o l l o w e d b y "
SBD: size = <size>
:
<size>
The length of the message in bytes.
Iridium Satellite LLC Proprietary & Confidential Information
Information contained herein is subject to change without further notice
– 1
if there is nothing in the mobile terminated
SBDTC: Outbound SBD copied to Inbound
" , w h e r e :
OK
57

Advertisement

Table of Contents
loading

Table of Contents