LoRa mesh should not require you to be the RF engineer.
Today a new user picks a spreading factor, a bandwidth preset, a role, and sometimes a different firmware for each role. Most people guess. BionicMesh makes those choices on the radio, per neighbor, and keeps making them as conditions change.
No radio settings to pick
DESIGNOne bandwidth per region and a rate chosen per neighbor from what each link reports. In the US that is 500 kHz with spreading factors 5 through 12, picked by the radio, not by you.
Every node can relay
DESIGNOne firmware per device. Relays are chosen by short timers for each broadcast, so no node has to be configured as a repeater.
Delivered means delivered
DESIGNA message shows Delivered only when the recipient’s node returns an authenticated receipt. One receipt can confirm many messages, and a reply carries it for free.
Messages wait for you
DESIGNYour node owns your inbox, relays hold messages for a sleeping neighbor, and the sender retries now, at 30 seconds, 2, 10 and 30 minutes, then every few hours for up to 48 hours.
Less flooding
DESIGNRoutes are found on demand with a backup next hop, and duplicates are filtered at every relay.
Keys stay on the device
DESIGNEach node makes its own keys on first boot. They are never in a firmware image, and a contact shows as unverified until you check it in person.
Each card is a recorded design decision, not a measured result. A claim moves from Design to Shipped only after bench and field tests, published with their numbers.
Forums on the mesh, the way BBSes used to work.
A Door is a message board that lives on the nodes themselves. Join one for your trailhead, your neighborhood, your search and rescue team or your ham club, read what was posted while you were out of range, and post back. No internet, no server, no account.
Public or private
A public Door is open to anyone who joins. A private Door can require the owner to approve each member, and its key changes when someone is removed.
Found by asking, not by flooding
Search for Doors by name when you want one. Doors are never announced on a timer, so they cost no airtime until someone looks.
Light on the channel
Joining fetches the newest 10 posts, then 10 more when you ask. Posts are numbered, so a device fetches only what it is missing.
Shared by the members
Any member’s node can serve the posts it holds, so a Door survives its host going offline. Battery devices read but do not serve.
Doors are designed and scheduled after direct messages and the mesh itself. Nothing here is built yet.
Five places, in the same order, on every node with a screen.
A one-button OLED, an e-ink pager and a keyboard handheld use the same five destinations, status row and message symbols. The phone app keeps it to three: Inbox, Outbox and Node.
What is done, and what is not
- DONEProtocol decisions recorded (v0.7). Firmware core with its scheduler, US 915 region gate, airtime math and the one-button OLED interface, all with automated tests.
- DONEFirmware for the Heltec WiFi LoRa 32 V3 and V4 builds and boots in an emulator. It shows SET REGION FIRST and keeps the radio silent until you choose.
- NOT YETNo radio driver. Nothing transmits, and no board has run this firmware.
- NEXTA simulator on the firmware core, then a wire format with test vectors, then two radios on a bench.
- LATERDirect messages with receipts, then the mesh, then Doors. An nRF52 board (RAK4631) comes before any battery claim.
Devices BionicMesh is built for
Each device is its own firmware build. A board with a different screen counts as a different device. Nothing here is ready to flash yet.
Heltec WiFi LoRa 32 V4
BUILD TARGETFirst build target. Builds and boots in the emulator. Not yet run on a board.
Heltec WiFi LoRa 32 V3
BUILD TARGETSecond build target, same state as the V4.
RAK WisBlock 4631
PLANNEDLow-power board. Comes before any battery-life claim.
LilyGO T-Deck Plus
PLANNEDFull keyboard device for typing on the node itself.