MeshCore Performance Tuning
Default settings work for most deployments, but understanding the trade-offs lets you optimize for your specific American terrain and use case.
Why Performance Tuning Matters
The default MeshCore configuration represents a reasonable compromise for typical scenarios. However, a repeater atop Pikes Peak has different requirements than a pocket device in downtown Phoenix.
Performance tuning involves understanding trade-offs. Longer range comes at the cost of slower transmission. Extended battery life means less frequent position updates. There exists no universal optimum.
This guide explains how to tune MeshCore for various American deployment scenarios: maximum range across the Cascades, fast messaging at festivals, or week-long battery life for backcountry rescue equipment.
Performance Dimensions
Range
Maximum distance between nodes with reliable communication
Speed
Time from sending to message arrival
Battery Life
Duration between charges under typical usage
Reliability
Percentage of messages successfully delivered
Throughput
Volume of traffic the network can sustain
Scalability
Maximum node count before performance degrades
Performance Optimization Tips
1. Adjust Spreading Factor For Terrain
Higher spreading factors (SF10-SF12) penetrate buildings and terrain better. Lower values (SF7-SF9) transmit faster but require clearer paths.
Impact: SF12 reaches four times further than SF7, but transmits sixteen times slower. For Rocky Mountain hilltop repeaters: SF11-12. For Denver neighborhood chat: SF7-8.
2. Balance Transmit Power
Maximum power is not always optimal. Excessive power can cause receiver overload at close range and drains batteries faster.
Impact: Doubling power (10dBm to 20dBm) extends range modestly while tripling battery consumption. Start at 15dBm, increase only if coverage gaps remain.
3. Select Appropriate Bandwidth
Narrower bandwidth (125 kHz) offers better sensitivity and building penetration. Wider bandwidth (250-500 kHz) enables faster data rates.
Impact: 125 kHz suits most American deployments where range matters more than speed. Use 250 kHz only for high-traffic nodes with assured line-of-sight.
4. Configure Hop Limits Thoughtfully
Each hop adds latency and consumes airtime. Too few hops limit coverage; too many waste resources on already-delivered messages.
Impact: Three hops covers most urban networks and small towns. Extend to 5-6 only for sparse rural deployments across the Great Plains or Sierra Nevada.
5. Tune Broadcast Intervals
Position and telemetry broadcasts consume airtime proportionally to their frequency. Balance network awareness against channel congestion.
Impact: Battery nodes: 15-30 minute intervals. Solar-powered repeaters: 5 minutes. Moving assets requiring tracking: 1-2 minutes during activity.
6. Monitor Channel Utilization
Air utilization above 10% causes collisions and message loss. The RegionMesh map shows local airtime usage.
Impact: At >15% utilization: lengthen broadcast intervals, disable non-essential telemetry, or coordinate channel separation with nearby network operators.
Configuration Examples
Ready-to-use configurations for common American deployment scenarios:
Maximum Range (Rural/Emergency)
Optimized for links across valleys and prairies where speed matters less than reach:
bandwidth: 125 kHz
tx_power: 20 dBm
broadcast_interval: 30 min
hop_limit: 5
Balanced (Urban Community)
Suitable for city and suburb deployments where moderate range and reasonable speed both matter:
bandwidth: 125 kHz
tx_power: 15 dBm
broadcast_interval: 15 min
hop_limit: 3
Fast Messaging (Events)
Optimized for festivals, conferences, and gatherings where nodes cluster closely:
bandwidth: 250 kHz
tx_power: 10 dBm
broadcast_interval: 5 min
hop_limit: 2
Best Practices For Optimization
-
✓
Measure before tuning: Record baseline metrics (range, battery life, delivery rate) before making changes.
-
✓
Change one parameter at a time: Simultaneous changes obscure which adjustment produced which effect.
-
✓
Test in realistic conditions: Laboratory performance rarely matches field reality with buildings, terrain, and interference.
-
✓
Monitor after changes: Verify improvements actually materialized in practice, not just theory.
-
✓
Document your configuration: Future troubleshooting requires knowing what settings are actually deployed.
-
✓
Start conservative: Begin with balanced defaults, optimize only after identifying specific deficiencies.
Frequently Asked Questions
What matters more: range or speed?
Depends entirely on use case. Emergency networks prioritize range, even if messages take seconds longer. Festival coverage benefits from speed since everyone is within feet of each other. Community networks need balance.
How do I measure optimization effectiveness?
Track key metrics: SNR (Signal quality), delivery rate (messages successfully received), air utilization (percentage of time channel is busy), battery runtime (days between charges).
Can different nodes use different configurations?
Partially. Spreading factor and bandwidth must match for communication. Power levels, broadcast intervals, and hop limits can vary. Hilltop repeaters often use higher power than valley devices.
What are the fundamental physical limits?
Theoretical maximum range: ~30 miles across water or flat terrain. Practical American limits: ~6 miles rural line-of-sight, ~1-2 miles urban with buildings. Maximum data rate: ~5.5 kbps. LoRa trades bandwidth for range.
How do I maximize battery life?
Lower transmit power (10dBm), extend broadcast intervals (30-60 minutes), disable Bluetooth when unused, configure aggressive sleep modes. These settings can extend runtime from days to 2-4 weeks.
Optimize Your MeshCore Network
Performance tuning transforms good coverage into excellent coverage. Whether spanning Colorado valleys or connecting Austin neighborhoods, these techniques help you extract maximum value from your mesh deployment.
Start with balanced configuration, then refine based on measured performance