Recommended Settings
These are the recommended MeshCore settings for TennMesh to help keep the network stable, efficient, and easy to join. These values are designed to reduce unnecessary airtime, improve reliability, and maintain compatibility across the mesh. Whether you're setting up a new companion or configuring a repeater, use the guidance below to ensure your device works seamlessly with the rest of the TennMesh network.
Note: Start by selecting the USA/Canada (Recommended) preset, and then only change the Coding Rate as desired. When the Coding Rate is changed, the preset will then say "Custom" instead of USA/Canada. This is normal.
Companion Settings
- Preset
- USA/Canada (Recommended)
- Frequency
- 910.525 MHz
- Bandwidth
- 62.5 kHz
- Spread Factor
- 7
- Coding Rate
- 5 or 8 for weak signals
Repeater Settings
- Preset
- USA/Canada (Recommended)
- Frequency
- 910.525 MHz
- Bandwidth
- 62.5 kHz
- Spread Factor
- 7
- Coding Rate
- 8
2-Byte Path Hash
As TennMesh has grown well beyond 256 nodes, we're moving to 2-byte path hashes to eliminate collisions. See the blog post for full details on why this matters and how the transition works.
Repeater (firmware 1.14+ required)
Run this command from the Command Line tab after remotely logging in as admin.
set path.hash.mode 1Companion Node
From the home screen: Gear icon → Experimental Settings → Default Path Hash Size → 2-Byte (max 32 hops)
Note: Only make this change after most repeaters in your area have updated to firmware 1.14+. Repeaters still running older firmware will not repeat your 2-byte traffic.
Advert Interval Settings
Since we've seen a rapid increase in growth, we're now dialing back the recommended advert settings for East TN where we're starting to see congestion.
East TN Repeater Advert Intervals
- Zero Hop
- 0 Minutes
- Flood
- 48 hours
Middle TN Repeater Advert Intervals
- Zero Hop
- 60 Minutes
- Flood
- 3 hours
West TN Repeater Advert Intervals
- Zero Hop
- 60 Minutes
- Flood
- 3 hours
Repeater TX Delay Settings
This section is for the repeater transmission delay settings along with some additional recommended settings. The goal of these settings is simple: repeaters that hear more neighbors should wait longer before transmitting. This lets nearby repeaters serve their local areas first, reduces on-air collisions, and keeps packets flowing.
If your repeater was just deployed, wait a few days for your repeater to collect data on how many neighbors it has, then use the specfic settings based on your neighbor count below.
| Neighbors | txdelay | direct.txdelay |
|---|---|---|
| 0–1 | 0.3 | 0.1 |
| 2–4 | 0.5 | 0.3 |
| 5–9 | 1.0 | 0.5 |
| 10–14 | 1.5 | 1.0 |
| 15+ | 2.0 | 2.0 |
Each section below will have a command with a copy button to the right. These are to be copied and pasted into the Command Line tab in the MeshCore app after remotely logging into as an admin on the repeater you're managing.
Common Settings (all repeaters)
These settings are recommended for all repeaters, regardless of neighbor count.
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3Neighbor Count: 0–1
set txdelay 0.3
set direct.txdelay 0.1
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3Neighbor Count: 2–4
set txdelay 0.5
set direct.txdelay 0.3
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3Neighbor Count: 5–9
set txdelay 1
set direct.txdelay 0.5
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3Neighbor Count: 10–14
set txdelay 1.5
set direct.txdelay 1
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3Neighbor Count: 15+
set txdelay 2
set direct.txdelay 2
set agc.reset.interval 4
set multi.acks 1
set rxdelay 3