RockBLOCK Plus 9704

Description

RockBLOCK Plus 9704 takes the RockBLOCK 9704 IMT module and packages it for field deployment.

 

It gives your system two way Iridium Messaging Transport over the Iridium network, with message payloads up to 100 KB. Use it when classic SBD message sizes are too limiting, but you still want a message-based satellite link rather than full IP connectivity.

 

The sealed IP67 enclosure includes the Iridium Certus 9704 transceiver, internal patch antenna, power handling, and onboard u-blox MAX-M10S GNSS. Your host system connects over RS-232, with separate serial access for Iridium and GNSS data.

 

The integrated GNSS receiver outputs raw location data over serial. It's not a fixed-function tracker; you decide how to parse, filter, combine, store, or transmit location data in your own application.

 

Choose RockBLOCK Plus 9704 when you want 100 KB IMT messaging and GNSS in a mountable outdoor device. Choose RockBLOCK 9704 if you want the board-level version for your own enclosure, or RockBLOCK Pro if you want more onboard application logic and I/O.

Key Features

  • Sealed IP67 enclosure for permanent outdoor installation
  • Iridium Messaging Transport for two-way satellite messages up to 100 KB
  • Internal Iridium antenna, built around the Iridium Certus 9704 IMT transceiver
  • Integrated u-blox MAX-M10S GNSS with raw NMEA or UBX output over serial
  • Dual RS-232 ports for separate Iridium and GNSS communication
  • Wide 7-30V DC input for field power systems
  • Low power modes for separate 9704, GNSS, sleep, and combined operation
  • Compatible with Ground Control’s open source C and Python libraries.

Tech Specifications

  • Message size: up to 100 KB
  • Core module: Iridium Certus 9704
  • GNSS: onboard u-blox MAX-M10S
  • GNSS output: NMEA or UBX over serial
  • Host interfaces: dual RS-232 ports for Iridium and GNSS
  • Iridium serial settings: 230400 baud, 8N1
  • GNSS serial settings: 9600 baud, 8N1
  • Power input: 7–30V DC
  • Cable: 8-core 0.25 mm² cable
  • Power consumption, transmitting: <2.0W
  • Inrush limit: <6.7W
  • Functional modes: 9704 only, GNSS only, 9704 + GNSS, sleep
    9704 ready time: up to 40 seconds after power-up if unpowered for several days
  • Power protection: 1A fuse required in-line with positive supply
  • Software support: compatible with Ground Control's open source C and Python libraries
  • Operating temperature: -40°C to +70°C
  • Storage temperature: -40°C to +85°C
  • Enclosure: sealed outdoor radome, UV-stable ASA
  • Ingress protection: IP67.

Cloudloop Platform

The RockBLOCK Plus 9704 interfaces directly with our API-first Cloudloop platform.

Cloudloop Data handles data conversion by reformatting raw satellite payloads for integration into your downstream applications, while the central Subscription Manager tool provides operational control over device activation statuses, fleet usage metrics, and commercial billing
Explore Cloudloop

Resources / Quick Links

RockBLOCK Plus 9704

FP-GC-RB-PLUS9704-3M

$479.00
$479.00
Sale Sold out
Taxes included.
Cable Length
Inquire

Frequently Asked questions

No. Although GNSS hardware is integrated, you must implement your own custom logic to interpret and contextualize the raw position data. It is not a tracking device.

No. RockBLOCK Plus features an integrated antenna within the sealed enclosure. External antenna hardware is not required.

All the SBD devices - RockBLOCK 9602, RockBLOCK 9603, RockBLOCK Plus, RockBLOCK RTU - utilize the same standardized AT command sequence, allowing developers to maintain software consistency across these systems.

However, the IMT-based RockBLOCK 9704 and RockBLOCK Plus 9704 do not use AT Commands. IMT devices use a proprietary protocol which Iridium call JSPR (JSON-Based Serial Protocol for REST). We've written open source C and Python libraries to save you having to digest this protocol, but easier still, RockBLOCK Pro and Pro OEM feature an AT command-based serial interface which helps smooth the transition to IMT.

Airtime is purchased separately from the hardware.

When your IMT device arrives, register it online at the Cloudloop Console. You can buy message credits, manage your device, and start sending messages without speaking to sales.

If you prefer post-pay airtime, contact our team at hello@groundcontrol.com and we can switch your account over.

You can find PAYG and post-pay airtime rates at https://www.groundcontrol.com/products/iridium-messaging-transport-imt-pricing/.

In ideal conditions, an already powered device can complete an Iridium IMT message session in around 10 seconds. That assumes a clear view of the sky, good antenna placement, and a successful session on the first attempt.


We wouldn't recommend designing your application around guaranteed 10 second reporting. In real installations, buildings, terrain, vehicle bodywork, ship structures, trees, antenna placement, RF interference, and satellite movement can all affect how quickly a session completes. Larger messages will also take longer to transmit than very small payloads.

For most applications, it's better to design around retries and occasional delays. Send when you have data to report, retry quickly if the first attempt fails, then back off to a longer retry interval if needed. IMT is well suited to larger telemetry packets, batched sensor data, logs, configuration files, and other message-based payloads, but it should not be treated as a fixed-interval real time link.

As a rule of thumb: around 10 seconds is a best case session time for small messages, not a guaranteed reporting interval.