microReticulum as used on the LilyGo T-Beam SUPREME
John Poole
23fbc569c6
Sender/recipient use board IDs for easier log aggregation. Iteration count is still included and increments per peer. Send cadence is now once per minute at the node’s allocated slot only. Removed the previous slot + 30s second send. Removed noisy app-internal diagnostics like APP LINK..., APP RX..., and TX LINK SKIP. Set Reticulum library logging to LOG_WARNING, which suppresses heap/path-store/entries/byte-count style diagnostics while preserving warnings/errors. Fixed inherited physical slot label Fay to Flo. Updated the README with the message cadence and examples |
||
|---|---|---|
| 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.