MeshCore channel configuration
How to tune MeshCore radio settings correctly: frequency, spreading factor, bandwidth, coding rate, and transmit power.
Radio configuration in MeshCore
In practice, MeshCore nodes use one compatible radio configuration per node. To communicate, nodes must share matching frequency and LoRa parameters.
Conversation separation is mainly logical via rooms and direct node messages, not through a slot-based multi-channel model per node.
This guide focuses on the settings that matter: frequency, spreading factor, bandwidth, coding rate, and transmit power within regional rules.
Practical configuration layers
Radio profile
Core RF settings that make communication possible: frequency, SF, bandwidth, coding rate, and power.
Logical grouping via rooms
Group communication is primarily handled via rooms and direct messaging, not by a fixed 0-7 channel-slot architecture.
Protocol-level encryption
MeshCore supports encryption. Avoid importing unverified per-channel PSK models from other projects.
Important radio parameters
Frequency
In Europe, operate within the 863-870 MHz ISM band. Many networks use 868.1, 868.3, or 868.5 MHz, depending on regional policy and rules.
Spreading factor (SF)
SF7-8 is faster with less range, SF9-10 is often a practical balance, SF11-12 gives more range at lower throughput.
Bandwidth
Bandwidth affects speed and robustness. Nodes need compatible settings to decode each other reliably.
Coding rate
Coding rate controls error correction versus speed. More correction improves resilience but lowers effective throughput.
Tx power
Set power within legal limits for your country and sub-band. EU deployments must respect EIRP and duty-cycle constraints.
Network consistency
Consistent RF settings across nodes are essential. Frequency/SF/BW/CR mismatches prevent communication.
Spreading factor in practice
| SF | Range (general) | Speed (general) | Typical use |
|---|---|---|---|
| SF7-SF8 | Shorter | Higher | Dense networks, lower latency, shorter links |
| SF9-SF10 | Medium | Medium | Common balance for mixed environments |
| SF11 | Longer | Lower | Longer links, more challenging terrain |
| SF12 | Maximum | Lowest | Range-first scenarios with low traffic pressure |
Benefits of correct configuration
More reliable reachability
Well-tuned SF/BW/CR settings increase successful delivery probability.
Better airtime efficiency
Appropriate settings reduce unnecessary channel load and improve practical network behavior.
Stronger repeater cooperation
Consistent RF profiles support discovery and targeted repeater forwarding.
Clear separation model
Rooms separate conversations logically; shared RF settings maintain compatibility.
Regulatory compliance
Keeping settings within local limits avoids interference and legal risk.
Easier maintenance
A clear RF profile per network segment makes troubleshooting more predictable.
Frequently asked questions
Which frequency should I use in Belgium or the Netherlands?
Operate within the 863-870 MHz ISM band under local rules. Many deployments use 868.x MHz frequencies depending on policy and compliance needs.
Which SF is best?
There is no universal best SF. Choose based on environment, link distance, and traffic load: lower SF for speed, higher SF for reach.
Does MeshCore use multiple channel slots per node?
Do not model this as a Meshtastic-style slot architecture. In MeshCore, focus on compatible RF settings plus logical separation via rooms and direct messages.
Can I reuse preset names from other LoRa projects?
Do not use external preset naming as general MeshCore guidance. Describe actual LoRa parameters instead (frequency, SF, BW, CR, power).
Is encryption based on separate per-channel PSKs?
Do not present that as a general MeshCore model. State only that encryption is supported, without unverified channel-slot assumptions.
How much transmit power is allowed in Europe?
Allowed power depends on country and sub-band. Follow local EIRP and duty-cycle limits; avoid fixed high-power universal advice.
Configure your MeshCore radio profile correctly
Start with consistent settings across nodes, then optimize step by step using real-world coverage and reliability results.