Docs · Node firmware · Hardware · What is proven · Bench manual · meshsat.net
The v0 node on its bench: a garden ledge with a limited view of the sky.
This is the small MeshSat node. It puts a Meshtastic LoRa radio and a RockBLOCK 9603 Iridium modem in one pocket-size case. A phone connects to it over one Bluetooth link and gets both: the mesh through the normal Meshtastic service, and the satellite modem through a second MeshSat service next to it.
The MeshSat Android app does the routing, the queueing and the credit accounting, so the node itself stays simple. While the app is connected, the modem is the app's. Routing on the node itself, for when no phone is around, comes next.
Status: pre-release. This is a prototype under active development, not a finished product. It has never been deployed to a real user and has never been used in an actual emergency. See What is proven, and what is not before you rely on it for anything.
flowchart LR
mesh["Meshtastic mesh<br/>LoRa 868 MHz"] <--> fw
subgraph node["MeshSat node"]
fw["ESP32-S3<br/>meshsat-firmware"] <-->|UART| rb["RockBLOCK 9603"]
end
phone["MeshSat Android"] <-->|"Bluetooth LE<br/>Meshtastic + Iridium services"| fw
rb <-->|"Iridium SBD"| sat(("Iridium"))
sat <--> gc["Ground Control"] <--> hub["MeshSat Hub"]
phone <-.->|"internet, when there is any"| hub
The node runs meshsat-firmware, a fork of the Meshtastic firmware with one addition: a binary-safe serial pipe from Bluetooth to the RockBLOCK. The app speaks the 9603's AT commands through that pipe, exactly as it would over a cable. The pipe's contract (UUIDs, owner status, pairing) is in docs/IRIDIUM-BLE.md.
Two versions. v0 proved the idea on the bench; v1 is the one meant to become a product.
| v0 (bench) | v1 (prototype) | |
|---|---|---|
| Board | Seeed Studio XIAO ESP32-S3 + Wio-SX1262 | LILYGO T-Beam Supreme (ESP32-S3, SX1262, u-blox M10S GPS) |
| Satellite | RockBLOCK 9603 | RockBLOCK 9603 |
| Power | USB power bank | one 18650 cell in the T-Beam, charged over USB-C; the modem runs from the T-Beam's power chip |
| Case | Peli 1050 | Peli 1020, IP68 USB-C and a panel power button |
| Firmware env | meshsat-xiao-s3-rockblock |
meshsat-tbeam-s3-rockblock |
| State | Tested on the bench, September 2026; retired from the phone role on 21 Sep | Running since 21 Sep 2026 on the bench and in the garden; the Peli build is not finished |
The RockBLOCK needs an active Ground Control line rental and message credits. Every satellite session is billed, even one that only checks for mail.
RockBLOCK wiring, four wires either way. Pin 7 (OnOff) and pin 9 (Li-Ion) stay unconnected.
| RockBLOCK pin | v0: XIAO ESP32-S3 | v1: T-Beam Supreme, label printed on the long header |
|---|---|---|
| 1 RXD (modem output) | D7, GPIO44 | RXD (GPIO44) |
| 6 TXD (modem input) | D6, GPIO43 | TXD (GPIO43) |
| 8 power in | a 5 V source rated ≥ 500 mA | DC5 (the 3.7 V rail the firmware switches on for the modem; never DC1, the board's own 3.3 V) |
| 10 GND | GND, shared with the 5 V source | GND |
On v1 the labels are the ones printed beside the pins (LilyGO's pinout image); TXD and RXD are also on the 4-pin QWIIC socket. The 2.4 GHz antenna for Bluetooth is on the board; only the LoRa antenna is external, and it must be on before the region is set. On v0, use the XIAO's own D6/D7 pads. The Wio-SX1262's D5/D6/D7 pads are not connected on the ESP32-S3 kit. A step-by-step build guide for both versions is on docs.meshsat.net. The full v0 wiring, power notes and troubleshooting are in the bench manual, and every hardware fact with its source is in docs/REFERENCES.md.
| State | |
|---|---|
| Meshtastic to the MeshSat Android app over Bluetooth (v0) | Verified on the bench, 19 Sep 2026: bonded with a fixed PIN, full config sync |
| Iridium modem over the same Bluetooth link (v0) | Verified on the bench, 19 Sep 2026: AT commands, and a binary loopback of up to 270 bytes |
| A satellite message out, Hub to phone to node to Iridium | One message delivered, 19 Sep 2026 |
| A satellite message in, fetched by the app after a ring alert | One message received, 19 Sep 2026 |
| The app reconnecting after its own restart and taking the modem back | Verified 19 Sep 2026 |
| Recovery from a Bluetooth drop, even mid-session | Bench, 26 Sep 2026: six forced drops, six reclaims within a second, one session held through the drop and its result caught |
| The node rebooting itself when its Bluetooth stack no longer serves | Bench, 26 Sep 2026: three unpaired links, five minutes, reboot, the reason read back at boot |
| v1 on the T-Beam Supreme | Running since 21 Sep 2026: flashed, paired with the app (fixed PIN), modem answering through the BLE pipe, satellite messages both ways from the garden |
| Routing on the node with no phone connected | Proven 27 Sep 2026 in the garden: a text typed on a T-Deck on the channel i9603 reached the Hub over LoRa and Iridium through the node alone, and the Hub's reply came back to the T-Deck the same way, 14 s after it was queued |
| The modem changing hands between the phone and the node | Bench, 2 Oct 2026: a message the phone left unread in the modem was passed on to the mesh instead of deleted, a text sent while the phone held the modem was not sent a second time, and the node took its own text out of the modem before the phone took over |
| A second device pairing without the phone losing its bond | Bench, 2 Oct 2026, a phone and a laptop: the phone reconnected without pairing again. Not tried with three devices |
| The node recovering when its Bluetooth stops advertising | Bench, 2 Oct 2026, with advertising stopped on purpose: started again within a minute, and the node rebooted itself when that did not help |
| The node saying why it last went down | Bench, 2 Oct 2026: a flash, a restart and a watchdog reboot each read back at the next start. Low battery, a switch-off, a crash and a brownout were not provoked |
| A RockBLOCK 9704 behind the node's pipe (compact v2 firmware) | Bench, 8 Oct 2026, from a laptop through the pipe: the modem answered JSPR, took its SIM and API version, registered as active, and accepted a text with its segment. Not transmitted yet: no sky at the desk. It ran on the T-Beam's DC5 rail for 1 h 48 min and counting on a full cell with no USB (verified through the pipe at 02:03), and dropped out on a cell at 3.67 V. Later that night the node routed on its own: a text on i9603 went from the mesh into the modem in 190 ms with no phone involved (meshsat-firmware 2cb9788); the firmware now switches the rail off itself under a provisional 3.7 V on the cell. Since meshsat-firmware cd6dcfc the node says which modem it carries, and MeshSat Android 2.19.9 left on Auto brought the 9704 up through the pipe from that word in 1.5 s (12:47 the same day). After a reboot of the node, Android 2.19.10 had the 9704 back by itself 65 s later. 24 Oct 2026 on MSC-2 unit 0001 with the cell feeding the modem and I_EN/I_BTD in the firmware (meshsat-firmware c695a589d): start sequence to an active modem, a text from the node's serial and a preset from a T-Watch over LoRa both in the modem's queue within half a second, a warm reboot that kept the modem up. Under sky the same afternoon (meshsat-firmware 4012de597, MeshSat Android 2.22): six texts from the phone through the pipe went up between 12:36 and 16:21 CEST and reached Cloudloop, and three texts came down to the phone through the pipe, the first two at 15:53 after waiting while the unit was indoors. Still owed: the node on its own under sky. The night's queued texts never left, because the 9704 keeps no queue across its own restart, and a text from a T-Deck Plus at about 16:43 with the phone's Bluetooth off had not reached the Hub when rain ended the session |
| A firmware update from the phone over Bluetooth | 24 Oct 2026, MSC-2 unit 0001: MeshSat Android 2.22.5 handed the node to Meshtastic's Bluetooth update loader and sent meshsat-firmware 4012de597 (2.4 MB) in about two and a half minutes; the node came back with its bond, its config and the modem. The image came from a file on the phone; fetching it from a release is not built yet |
| The status light and the screen switched from the app | 24 Oct 2026, MSC-2 unit 0001 on meshsat-firmware 4012de597: both off and on again from MeshSat Android 2.22.6. Not yet seen across a reboot of the node |
| The panel switch as a satellite beacon | 4 Nov 2026, MSC-2 unit 0001 on meshsat-firmware 993af59c6, indoors by a window: the switch-on message waited in the modem until a satellite came into view, then went up with the 10-minute message, and the Hub passed both on by SMS to a preset contact within half a minute. No GPS fix indoors, so neither carried a position |
| Battery life | Not measured |
| Range, weather, long-term reliability | Not tested |
| Deployment to a real end user | Never |
| Use in an actual emergency | Never |
The satellite results come from a garden with a limited view of the sky. There the signal read zero bars minutes before and after a session that got through, so the app never waits for bars before it sends.
- Bench firmware for v0 in
src/, with host tests intests/and a Bluetooth console client intools/. It tests the modem link and passes AT commands through over USB or Bluetooth. How to build and use it: docs/BENCH.md. - The Iridium Bluetooth service contract in docs/IRIDIUM-BLE.md: what a client writes, reads and subscribes to.
- Hardware references in docs/REFERENCES.md: pin maps checked against the schematics, the 9603 facts, and the places where official documents disagree.
The node's product firmware lives in meshsat-firmware.
- MeshSat, the Bridge: a Raspberry Pi gateway that bonds Meshtastic, Iridium, cellular SMS, APRS, ZigBee and TCP
- MeshSat Android, the phone gateway this node pairs with
- meshsat-firmware, the node's firmware
- MeshSat Field Kit, the hardware for the larger field kits
- MeshSat Hub, multi-tenant fleet management
MeshSat does not work with any organisation that develops, produces, integrates or operates weapon systems, and provides nothing for use in one. The licence below is unchanged: the policy covers whom we work with, not what you may do with the code. Read the MeshSat Mission and Use Policy.
Copyright 2026 Elli and Kyriakos. GNU General Public License v3.0.
