Public Access
Hardware: a reference Meshtastic node #22
Notifications
Due Date
No due date set.
Blocks
#24 Meshtastic: decrypt and decode packets (host-tested)
twisla/roro9stack
#25 Mesh Service: take part in the mesh, receive only
twisla/roro9stack
#29 Sweep: check it against a known transmitter
twisla/roro9stack
#38 M5 acceptance: two devices, messages both ways
twisla/roro9stack
Reference: twisla/roro9stack#22
Reference in New Issue
Block a user
What
Get a second LoRa device running stock Meshtastic, and set it up as the known-good end for M4 and M5.
Why
M3's listening hour (outside, on battery, LongFast) heard no packet from the six nodes known within 30 km, and the plan had a rule for that (M3, Q104): a reference node becomes a requirement for M4. Without one there's nothing to receive, and later nothing to tell us whether a failure is ours.
What's known
meshtasticPython CLI over USB.To do
Related
docs/milestones/M3.md(Q104 and the listening hour), #20.