microReticulum as used on the LilyGo T-Beam SUPREME
Startup timing is made slower and more forgiving: recoveryRailOffMs = 400 recoveryRailOnSettleMs = 1200 startupWarmupMs = 2500 If the initial cold-boot mount still fails, it now does one immediate second-chance remount after a short delay before proceeding. |
||
|---|---|---|
| docs | ||
| exercises | ||
| external | ||
| firmware/fieldtest_beacon | ||
| img | ||
| shared/boards | ||
| tools | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| LICENSE | ||
| notes_Feb_18_2026.txt | ||
| README.md | ||
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.