Repeater Firmware
The Repeater firmware intelligently extends the range of your MeshCore network. Unlike other LoRa mesh systems that indiscriminately retransmit all received packets, a MeshCore repeater only transmits packets intended for specific devices, thus optimizing bandwidth and battery life.
MeshCore supports a configurable number of hops between devices, balancing maximum range and network efficiency. This design contributes to the decentralized and "self-healing" nature of the network, capable of adapting to topology changes such as the movement or disappearance of mobile repeaters.
Deployment & Administration
For optimal performance, repeaters should be positioned at height. Remote administration can be performed via a T-Deck with unlocked features or from a smartphone connected to a BLE Companion client.
Remote administration is possible via RF, offering remarkable flexibility in difficult environments or during temporary deployments.
Mobile Repeater Disconnection
When a node learns a route via a mobile repeater that subsequently disappears, the MeshCore protocol adapts using its "direct paths when possible, flood as fallback" philosophy. If the known path becomes inaccessible after three attempts, the system automatically resets this path and reverts to flooding to attempt to restore connectivity.
Hop Limit Configuration
MeshCore implements a configurable limit of hops between network nodes. Internally, the firmware has a theoretical maximum limit of 64 hops, although in real deployments, this limit is rarely reached due to environmental and temporal constraints.
set flood.max {max-hops}This command allows defining the maximum number of hops for incoming packets in flood mode - when a packet reaches this limit, it is no longer retransmitted, thus avoiding network congestion.