fluxcore
Your radio can probably do more.
Let’s find out.
FluxCore is a MeshCore fork for trying things. New features, fixes that shouldn’t have to wait, and experiments that might turn into something useful.
The goal is simple: move quickly and stay compatible with vanilla MeshCore. Keep using the network that’s already there. Give new ideas somewhere to run.
A few things to try
A second chance for missed packets. If your radio doesn’t hear a repeater forward its message, it sends the packet once more. Nodes that already have it ignore the duplicate. Retries ↗
One identity, several radios. Keep one at home and carry another. Pick a main radio; backups hold their replies when they hear it answer. This coordinates replies—it doesn’t sync your message history. Takeover ↗
Find the radio you put somewhere sensible. Make it beep from an authorized radio. Two supported LR2021 radios can also measure the distance between them, with a direct link in the supported 902–928 MHz band. Find me ↗
Also: packet parser fixes, improved key generation, radio diagnostics, and opt-in experimental encryption. All the changes.
Build it. Try it. Learn something.
FluxCore exists to shorten the distance between “what if?” and running code on a radio. Try ideas early. Test them on real hardware. Write down what works and what doesn’t. Bring useful changes back upstream.
Compatibility is the goal, and experiments should be explicit. Ordinary messages use MeshCore’s legacy format by default. Encryption v2 is opt-in and needs support at both ends; existing repeaters can forward it.
These builds track upstream dev. Things can break. Encryption v2 has not been independently reviewed. Check the supported boards and release notes before flashing.
Got an idea? Found something broken?
The code is here. ↗