9602N SBD Modem (SBD9602N)

All wireless devices, including satellite telephones, are susceptible to RF (Radio Frequency) interference from other electronic devices. This problem is especially evident when numerous antennas and broadcasting devices are located within close proximity to each other.

A good example would be onboard a ship. It is important that certain considerations be taken into account for best performance when an Iridium/Inmarsat system is installed.

Causes of RF Interference:

Some subscribers have contacted Iridium regarding the loss of signal quality when they operate their equipment near active Inmarsat terminals. The power with which Inmarsat units transmit can overpower the Iridium unit’s ability to properly maintain a quality connection with the Iridium satellite constellation. Inmarsat terminals are often found in the same locations as Iridium subscribers, such as harbors, airports and especially onboard ships.

The location of the Inmarsat unit’s antenna in relation to the Iridium unit’s antenna plays a significant role in determining the degree of signal degradation that an Iridium subscriber can expect to experience. All Iridium units are susceptible to this interference, regardless of the type of antenna being used.

Generally speaking, an Iridium unit, be it a handset using its internal antenna or a fixed terminal when attached to an externally mounted antenna and located within 15 and 45 meters (50 to 150 feet, respectively) of an operating Inmarsat Standard-C terminal, will likely experience degraded performance.

Other sources of RF interference such as Globalstar units, radar devices and broadcast stations can provide interference for Iridium units, but usually are not encountered as frequently as Inmarsat terminals.

Also refer to “Assuring Quality of Iridium Service” in the Antenna Installation Guide.

Make sure the following are observed:

• Power supply level is steady and never fluctuates.
• Antenna is connected to the dock or terminal with a Beam approved cable.
• Antenna installation guide is followed.
• The sim is active, else request service provider to reset the service on the sim.

The IP Address is 12.47.179.11

directip.sbd.iridium.com / port 10800 which should resolve to 12.47.179.12:10800

Yes, the source IP address that will be utilized to connect to the Iridium gateway needs to be included within the Iridium network firewalls, to allow for successful connection.

This request for DMT access needs to be sent to the partners Iridium Account Manager.

Before an SBD can be sent, the LBT (in the Beam Device) or Iridium satellite phone must be provisioned for SBD. This includes Data being activated on your account and a destination address setup for the SBD to be sent to.

The destination address can be set to a specific IMEI number, an email address, or a direct IP Address / port.

Your service provider will be able to assist you in provisioning of your device.

Refer to the Beam Data Guide for more information on sending SBD's.

Messages sent to an ISU from the Host are sent to the email address: This email address is being protected from spambots. You need JavaScript enabled to view it.

1. Placing at least one, and up to a total of four, IMEI(s) into the subject line of the email identifies the destination ISU(s).
2. If there is more than one destination IMEIs then list the additional IMEIs on the subject line separated with a single space between each IMEI.
3. White listing may be used to restrict the originator of MT-SBD messages to particular IMEIs. This restriction will fork for email and Direct IP.
4. The message must contain a properly formatted sender (“From:” address), otherwise the message will be dropped by the GSS.
5. The data message to the ISU must be carried as an attachment to the email:
   1. The attachment name must have a ‘.sbd’ file name extension: E.g. ‘importantdata.sbd’
   2. File names must be 80 characters or less. (Including the .sbd extension.)
   3. File names are not case sensitive.
      1. The maximum size of the binary message (not the Base64 version) is ISU specific and is between one byte and the maximum MT message size stated in Section 1.5
      2. The GSS will reject message sizes that are too large for a particular ISU type.
6. The attachment must use standard Multipurpose Internet Mail Extensions (MIME) Base64 encoding as defined in RFC 2045.
7. Multiple messages may be queued by a single email by including the additional separate attachments in the email message, subject to the maximum number of messages permitted in the queue.
   1. Note that if one of the attachments has an incorrect extension (.sbd), while others are correct then no error indication email will be sent.
   2. A single email with multiple attachments creates a MT-SBD message from each attachment. In other words – one email with ten attachments creates ten entries for the destination ISU.
8. The message body plays no role in the message transfer process; any information contained in the body will be discarded.
9. A maximum of 50 messages may be in any ISU’s queue at any one time regardless of whether they where sent as an individual message with attachment or a single message with multiple attachments. The GSS will reject any message over this limit.

The 9601 / 9602(N) / 9603(N)  only supports Iridium's Short Burst Data (SBD) capability. It does not support voice, circuit switched data, or short message service (SMS).

The default baud rate is 19200 8N1 with hardware hand-shaking (CTS/RTS). The 9602 SBD Modem does not have an autobaud facility. The baud rate can be set via the AT+IPR=n where n is one of the following:

N     BAUD
1      600
2      1200
3      2400
4      4800
5      9600
6      19200 (Default)
7      38400
8      57600
9      115200

Check power is connected and correct DC voltage is available.

Check power connection.  

Check with your Service Provider that the service has been activated

Check Antenna connection and location.

Check that the correct cable is used on the correct port, and that the bit rate is set the same for both PC and 9602 SBD Modem. If using the USB connection, ensure the correct drivers have been installed.

Beam products are not certified for safety in explosive environments.