microReticulum as used on the LilyGo T-Beam SUPREME
Kept all units in transport mode with reticulum.transport_enabled(true). Removed physical blocking: SIM_PHY_BLOCK_BOB_CY=0, no per-unit block. Removed the extra deep transmission/debug flags from platformio.ini. Kept the 204 announcement schedule/protocol. Removed intentional Link teardown after message cycles. Every unit now attempts an outbound Link to every peer that announces. Added retry health behavior: 3 Link attempts within 3 minutes, then wait for a fresh announce before trying that peer again. Preserved substantive parseable logs: TX ANNOUNCE, RX ANNOUNCE, TX LINKREQUEST, LINK ACTIVE, TX LINK, RX LINK, retry/failure/reset events. Updated copied helper scripts to point at 205_sustained_link. Updated README for the new exercise behavior. |
||
|---|---|---|
| docs | ||
| exercises | ||
| external | ||
| firmware/fieldtest_beacon | ||
| img | ||
| lib | ||
| shared | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| LICENSE | ||
| notes_Feb_18_2026.txt | ||
| README.md | ||
| SETUP_REQUIRED.txt | ||
microReticulumTbeam
microReticulum For Field Testing With LilyGo T-Beam SUPREMES
Field Testing Only. Used to specially program a group of T-Beams, each having the others' contact information and keys, which are then deployed in the field with people moving about to capture what was successfully sent and received and at what coordinates. Data is stored on SD cards and then retrieved at the end of the test an dumped into a PostgreSQL databse for analysis.
Dependency Direction
This repo is migrating from external/microReticulum to external/microReticulum_Firmware.
Goal:
- Reuse upstream T-Beam SUPREME integration work in
microReticulum_Firmware. - Avoid reimplementing already-solved board integration (PMU, SD, RTC, GPS, LoRa setup).
Status:
- Migration plan is tracked in
docs/microreticulum_firmware_migration.md. - Existing exercises remain functional during migration.