Satellite IoT for Off-Grid Sensor Projects: Swarm, RockBLOCK, and Iridium Compared
LoRa will get a sensor node a few kilometers from its gateway, and a cellular modem will work anywhere there's a tower, but plenty of maker projects live past both of those limits: a weather station on a remote ridge, a water-level sensor on a backcountry cistern, a tracker on a sailboat three days offshore, a wildlife camera in a canyon with no signal at all. For that last mile — or last hundred miles — satellite IoT has quietly become something a hobbyist can actually afford and wire up in an afternoon, instead of a service reserved for oil-and-gas telemetry budgets. This guide covers the three practical options for makers today: Swarm, Iridium Short Burst Data through a RockBLOCK modem, and full Iridium Edge modules, plus how to wire one to an ESP32 and budget the power it needs.
Why Satellite Instead of LoRa or Cellular
The decision is really about coverage guarantees. A LoRa link needs a gateway you control or one already in range — great for a farm or a large property, useless past the treeline on a mountain. Cellular NB-IoT/LTE-M (covered in our guide to adding cellular connectivity with SIM7000/SIM800L modules) needs a carrier tower, which rules out oceans, deep wilderness, and a lot of the rural world outside populated corridors. Satellite IoT constellations — Swarm's VHF smallsats and the Iridium mesh — cover essentially the entire globe, including open ocean and polar regions, because the satellites are the infrastructure. The tradeoff is message size and latency: this is not a channel for streaming video or even a JSON blob with much padding. It's built for short, infrequent packets — a GPS fix, a battery voltage, a soil moisture reading — sent every few minutes to a few times a day.
The Three Practical Options
OptionNetworkMessage sizeTypical hardware costSubscriptionNotes Swarm M138Swarm (SpaceX-owned) VHF smallsat constellation192 bytes per packet~$99 modem (Swarm has been folded into SpaceX/Starlink direct-to-device plans; check current availability)~$5/month per device, packet-basedCheapest entry point historically; UART interface; small low-gain antenna RockBLOCK 9603 (Iridium SBD)Iridium (66-satellite polar mesh)340 bytes outbound / 270 bytes inbound~$250 modemRock7 Core airtime, pay-as-you-go or monthly bundlesMature, well-documented, used in maritime and expedition gear for two decades Iridium Edge / Edge SolarIridiumSimilar SBD limits, some models add GNSS$150–$400+Carrier-managed data plans, often higher minimumsBuilt for OEM integration; less hobbyist documentation than RockBLOCKFor most maker projects, the practical shortlist is Swarm (if you can still get a modem and airtime plan — availability has shifted since the SpaceX acquisition, so check current status before designing around it) or a RockBLOCK 9603 breakout. The RockBLOCK is the safer bet for a guide like this: it has been the go-to satellite modem for the ham radio, expedition, and open-source telemetry crowd since long before "satellite IoT" was a marketing term, and Rock7's SBD service is stable and well-documented.
How Iridium SBD Actually Works
Short Burst Data (SBD) is a store-and-forward messaging protocol, not a persistent connection. Your microcontroller writes a short binary payload into the modem's outbound buffer over UART, then issues an AT command (AT+SBDIX) to trigger a session. The modem finds the nearest overhead Iridium satellite, hands off the packet, and the satellite relays it either to a ground station or across its inter-satellite links until it reaches one. Rock7's servers then deliver it to you as an HTTP POST, an email, or through their API — typically within seconds to a couple of minutes if the modem has a clear sky view. Downlink works the same way in reverse, letting you push short commands back to the device (a "check in now" trigger, a configuration change) the next time it polls.
Wiring a RockBLOCK to an ESP32
- Interface: 3.3V UART (TX/RX), so it wires directly to an ESP32 hardware UART without a level shifter — check your specific breakout, since some RockBLOCK carrier boards are 5V tolerant only on certain pins.
- Power: The modem idles under 20mA but pulses up to 180–200mA for roughly a second during each transmit burst. A weak 3.3V regulator or long thin wire run will brown out mid-transmission and silently fail the send — use a regulator rated well above the peak, with a bulk capacitor (100–220µF) right at the modem's supply pins.
- Antenna: Needs a genuine sky view — mounted under a fiberglass enclosure lid is fine, under a metal box or dense tree canopy is not. Indoor testing will mostly fail; do your first-light test outside with a clear view of open sky.
- Library: The Arduino IridiumSBD library (Mikal Hart) handles the AT command handshake, signal quality polling (AT+CSQ), and session retries, and runs fine on an ESP32 under the Arduino core.
Power Budgeting for an Off-Grid Node
Satellite transmission is the most power-hungry thing your node will do, so duty cycle drives your whole power budget. A rough example for a Swarm or RockBLOCK node reporting every 30 minutes: the ESP32 wakes from deep sleep (a few µA), reads sensors (tens of mA for a few hundred ms), keys up the satellite modem for one send attempt (150–200mA for 1–5 seconds, more if it needs several attempts to find a satellite), then goes back to sleep. Over a day that averages out to well under 5mAh in the deep-sleep-dominated math from our ESP32 deep sleep guide, but a failed send that retries for a full minute can blow that budget for the hour — size your battery and solar panel around worst-case retry behavior, not the best-case single-attempt number, and cap the retry timeout in firmware so a bad pass doesn't drain the pack chasing a satellite that already set.
Choosing Between Them
Use caseRecommendation Remote weather station, water tank sensor, occasional check-insRockBLOCK 9603 — mature, documented, predictable Rock7 billing Asset tracker with frequent short pings and tightest budgetSwarm, if a modem and plan are currently available in your region Marine or aviation-grade reliability requirementIridium Edge / commercial OEM module with a managed carrier plan Anything within LoRa gateway range or cell coverageDon't use satellite — it's the most expensive and slowest option per byteRegistration, Regulatory, and Cost Traps
Both networks require you to activate the modem's IMEI on an account before it will transmit — there's no "just solder it and go" path, and a modem bought used may already be tied to a prior owner's account. Budget for the recurring airtime cost, not just hardware: even light usage plans run real monthly dollars per device, and per-message data plans can surprise you if a firmware bug puts the node into a retry loop. Neither service requires an amateur radio license since these are commercial satellite bands, not ham allocations, but keep antennas oriented and mounted as the vendor documentation specifies — a mis-oriented antenna is the single most common reason a "working" node reports intermittent failures in the field.
Satellite IoT won't replace LoRa or WiFi for anything that has coverage already, but for the genuinely remote end of maker projects — the sensor nobody can walk out to check every week — it's the piece that turns "we'll find out when we get there" into a text message that shows up on your phone from the middle of nowhere.