Getting Started with MeshCore
Overview
Follow these steps to get your node running on Acadiana Mesh:
- Set up your companion — flash the device, connect it, and set its name and radio settings.
- Use our radio settings — every node must use the same preset to hear each other (see Radio Settings).
- Join and test — advertise your node, find nearby repeaters and send a test message.
Setting Up Your Companion
Step 1: Flash your device
Flash your device with the MeshCore web flasher (Chrome or Edge on a computer).
- BLE (Bluetooth Low Energy) — pairs with the phone app; what most people want
- USB (wired)
- WiFi (wireless)
Step 2: Connect and configure
Install the MeshCore app (iOS / Android), connect to your companion, then:
- Tap the ⚙️ icon (top right).
- Set your name.
- Set the radio preset to USA/Canada (Recommended) — 910.525 MHz, BW 62.5 kHz, SF 7, CR 5.
- Tap ✔️ (top right) to save and wait for the green success notification.
Add channels:
- Tap ⋮ (top right) → + Add Channel → Join a Hashtag Channel.
- Enter the channel name (for example
test) and press Join Channel. - If you add the Public channel, set its scope to unscoped.
Or scan the QR codes on our Channels page.
Step 3: Join the mesh
Advertise your node: tap Advert (next to ⚙️) → Send Flood Advert. This announces your node name to the mesh.
Discover nearby repeaters: tap 🔧 → Discover Nearby Nodes → Discover Repeaters, wait for repeaters in range to respond, then tap + to add them to your contacts.
Step 4: Test your connection
Send a greeting on the Public channel, or send test, ping or path on #test. After sending, look for heard X repeats next to your message:
| Result | Meaning |
|---|---|
| heard 1+ repeats | ✅ Success — your message reached one or more repeaters |
| heard 0 repeats | ❌ No repeater heard your message |
test, path and ping can take up to 30 seconds to cross the mesh, get a reply and come back. If nothing happens right away, wait 30 seconds before trying again.If you see 0 repeats:
- Double-check your radio settings.
- Check the Live Map for repeaters near you.
- Step outside with the antenna pointing straight up.
- Find higher ground to clear buildings and trees — LoRa needs a reasonably clear path to a repeater.
Understanding repeater guest logins
Many repeaters have a guest login with no password. It lets anyone on the mesh view useful repeater information without the owner's password:
- Owner information — contact details and repeater specs, so you know who runs it and how it's built.
- Neighbors — the repeaters and nodes it can hear directly.
- Status — signal strength, uptime and connection statistics.
- Network health — real-time performance numbers.
Why a blank guest password? It makes repeater information available to everyone, which helps the community troubleshoot coverage, tune antenna placement and understand how the network fits together.
Understanding adverts
Adverts are how nodes announce themselves on the mesh. Each advert contains:
- Public key — your node's unique cryptographic identity (32 bytes)
- Timestamp — when the advert was made (used for routing and de-duplication)
- Digital signature — proof the advert is genuine (64 bytes)
- Node type — companion, repeater, room server or sensor
- Name — your node's display name
- Location — latitude/longitude, if you share it
| Advert type | How often | Reaches | Effect |
|---|---|---|---|
| Local (zero-hop) advert | Every 240 minutes on our repeaters | Directly connected nodes only | Announces to immediate neighbors without flooding the network |
| Flood advert | Rarely — set by the repeater owner | The entire mesh | Every repeater that hears it rebroadcasts it |
| Companion advert | Only when you send it | Your choice (zero-hop or flood) | Announces your companion |
Region Scope Finder
Find the region codes for a repeater. Tap the map where the repeater is installed, use your current location, or enter its coordinates — the commands to paste into the repeater appear below.
Pick a spot on the map to see its region codes.
* (unscoped) allowed — never run region denyf *, or the repeater stops forwarding normal unscoped traffic.Region boundaries from the community region registry at regions.caboosey.net — the same boundaries the Gulf Coast Mesh uses.
What these regions mean and how scoping works is on the Regions tab.
Radio Settings
Acadiana Mesh uses one radio preset: MeshCore's USA/Canada (Recommended). Every companion and repeater must use the same frequency, bandwidth and spreading factor to hear each other. These are the same settings used across the Gulf Coast mesh, so you can talk to neighboring networks.
| Setting | Value | Explanation |
|---|---|---|
| Frequency | 910.525 MHz | Inside the US 902–928 MHz license-free ISM band, which is shared with smart meters, IoT sensors and other LoRa devices. |
| Bandwidth | 62.5 kHz | A narrow channel. Thermal noise is about 3 dB lower than at 125 kHz and 6 dB lower than at 250 kHz, and a narrow channel picks up less interference. The trade-off is less tolerance for multipath and for radios whose frequency drifts. |
| Spreading Factor (SF) | 7 | 128 chirps per symbol, 2.048 ms per symbol. Decodes down to roughly −7.5 dB SNR (receiver sensitivity around −127 dBm). Faster on the air than higher spreading factors, so the mesh can carry more traffic. |
| Coding Rate (CR) | 5 (4/5) | 25% forward error correction — one parity bit for every four data bits. Keeps packets short on the air. |
Net result: a typical 100-byte packet takes about 350 ms on the air.
Acadiana Mesh regions
A repeater in the Acadiana area forwards these seven regions:
| Region | Covers |
|---|---|
us | United States-wide |
us-la | Louisiana-wide |
us-la-lft | Lafayette / Acadiana |
us-gc | Gulf Coast |
us-southeast | Southeastern US |
us-south | Southern US |
us-east | Eastern US |
Log into the repeater, open the Command Line, and send each command one at a time, waiting for each reply. Finish with region save:
region def us
region def us-la
region def us-la-lft
region def us-gc
region def us-southeast
region def us-south
region def us-east
region save
region def creates the region and allows it for flood in one step. Changes don't stick until you run region save. To check the result, run region to list every region, or region get <name> for one.
- If the repeater still has
gc-la-lft-mm(orus-la-lft-mm), remove it — we no longer use it:region remove gc-la-lft-mm, thenregion save. - If the repeater says
region defis an unknown command, update its firmware. On older firmware, useregion put <name>followed byregion allowf <name>for each region, thenregion save.
Region Scoping & IATA Codes
Region scoping lets each repeater decide which flood traffic it forwards, based on a region tag attached to the packet. Without scoping, a repeater rebroadcasts every flood packet it hears — including traffic from distant communities that has nothing to do with Acadiana. With scoping, only packets tagged with an allowed region are forwarded; everything else is quietly dropped.
This matters for mesh health. Every packet a repeater retransmits uses shared airtime. A Lafayette repeater forwarding traffic meant for another city burns channel time that local messages could have used. Across a busy network with many repeaters, unfiltered rebroadcasting means congestion, delays and dropped messages. Scoping keeps each part of the mesh carrying the traffic that belongs there.
Region naming format
Regions use a lower-case, hyphen-separated format. Pick the tightest scope that covers the people you want to reach.
<country>-<state>-<iata> example: us-la-lft
| Part | Example | Meaning |
|---|---|---|
| Country | us | United States |
| State | la | Louisiana |
| IATA | lft | The 3-letter airport code nearest the area — LFT is Lafayette Regional Airport |
Some regions cover several states instead: us-gc (Gulf Coast), us-southeast, us-south and us-east.
How transport codes work
When a client or room server sends a scoped flood packet (for example a channel message), it attaches a 16-bit transport code: an HMAC-SHA256 of the packet's payload, keyed with the region's 16-byte key. The packet is sent as ROUTE_TYPE_TRANSPORT_FLOOD (0x00), which tells receivers that transport codes are present. Plain flood packets with no transport code use ROUTE_TYPE_FLOOD (0x01) and are matched by the repeater's wildcard (*) region.
How a repeater matches a region
When a transport-flood packet arrives, the repeater works through its configured regions and computes the expected transport code for each one. If one matches the packet's code, the packet belongs to that region. If none match and the wildcard doesn't allow flood, the packet is dropped.
Every region stands on its own
Each region name produces its own independent key — us-la and us-la-lft share nothing — and there is no parent-chain lookup when matching packets. Any parent/child tree you see in the region CLI output is organizational only.
So allowing us-la does not forward packets tagged us-la-lft, or any other region. Every region you want to forward must be defined on the repeater individually — which is why the commands above list all seven. They add up: us carries national traffic, us-la carries state-wide traffic and us-la-lft carries local traffic.
Channels
QR codes for every channel are on the Channels page.
Core channels
| Channel | Key | Region scope | Purpose |
|---|---|---|---|
| Public | Built-in public key | None (unscoped) | General chat for all mesh users |
| Test | #test | None | Connection testing — send test, ping or path |
Regional channels
| Channel | Key | Region scope | Purpose |
|---|---|---|---|
| Acadiana | #acadiana | us-la-lft | General chat across the Acadiana region |
| Lafayette | #lafayette | us-la-lft | Local chat for the greater Lafayette area |
| SKYWARN | #skywarn | us-la-lft | Severe-weather spotting coordination for trained NWS storm spotters |
| Weather | #wx | us-la-lft | Weather alerts, storm reports and radar observations |
Channel bots
| Bot | Channel | Region scope | Commands |
|---|---|---|---|
| AcadianaWX | #wx | us-la-lft | wx, wx 70578, aqi, sun, moon, solar, satpass 25544, ping, help — full list on the Channels page |
| AcadianaBot | #bot | us-la-lft | ping, test, help, channels, sports scores, jokes and more — full list on the Channels page |
Privacy Considerations
What you should know
Treat messages, locations and other data you send on the mesh as public information.
| Concern | Details |
|---|---|
| 🌐 Internet-accessible tools | Maps and analyzers (including ours) display packet and location data publicly online |
| 🔓 No guaranteed privacy | A message is only as private as every person who receives it |
| 💾 Data persistence | Once transmitted, you have no control over how it is stored, shared or used |
| 📍 Location precision | Locations are transmitted with high precision |
Location privacy tip
You can set an approximate location instead of your exact address — close enough for coverage planning, but offset enough to give you a privacy buffer. Consider a nearby intersection, park or general area.
Best practices
✅ Do:
- Use direct messages for private conversations (with trusted contacts)
- Use private channels for group privacy (with trusted participants)
- Set approximate locations for your devices
❌ Don't:
- Share sensitive personal information on public channels
- Broadcast your exact home address
- Assume a public message is private
Encryption
| Type | Encryption | Privacy level |
|---|---|---|
| Public channel | AES-256-CTR | 🔓 Public (the key is shared) |
| # hashtag channels | AES-256-CTR | 🔓 Semi-public (key comes from the name) |
| Private channels | AES-256-CTR | 🔒 Private (if the key stays secret) |
| Direct messages | AES-256-CTR | 🔒 Private (unique per conversation) |
Repeater Naming & Setup
Naming convention
Name repeaters after where they are — a town, neighborhood or landmark — so anyone looking at a path or the map can tell where it is. Who runs the repeater goes in its owner information (Step 5), not the name.
| Type | Naming | Example |
|---|---|---|
| Fixed repeaters | [location] | Carencro, Downtown Lafayette, Rayne Water Tower |
| Mobile repeaters | Include "Mobile" in the name | Lafayette Mobile |
| Not yet installed | End with "TBA" | Scott TBA |
Step 1: Flash the firmware
Flash the repeater firmware with the MeshCore web flasher. Make sure an antenna is connected before powering the radio.
Step 2: Radio settings, name, location and owner info
Open the MeshCore USB config tool and set:
- Radio settings — frequency, bandwidth, spreading factor and coding rate (see Radio Settings)
- Name — its location, following the naming convention above
- Location — for mesh planning (an approximate location is fine)
- Owner information — your name or callsign, repeater specs, location type and an off-mesh contact
- Guest password — leave blank so other mesh users can check the repeater's status
- Send Advert — click it after configuring to announce the repeater to the mesh
Step 3: ⏰ Sync the clock — required
- Other nodes won't handle its adverts correctly, so it's effectively invisible
- Messages may not route properly
- It appears offline, at the bottom of contact lists
To sync the clock:
- Log into the repeater from your companion.
- Go to the Settings tab → scroll to Sync Clock → tap it.
- Wait for the green success notification.
- Tap Advert to have the repeater send an advert.
- ✅ Check that the repeater's Last Heard time is current, not May 2024.
Clock running ahead? Reset it first
Sync Clock only moves a repeater's clock forward. If the clock is ahead of the real time (the Clock Sync Report shows a + offset or "Ahead — needs reset"), syncing won't pull it back. Reset it instead:
- Log into the repeater and open its Command Line.
- Send
clkreboot. It resets the clock and reboots the repeater, and sends no reply. - Give it a minute to come back, log in again and tap Sync Clock.
- Send
clockto confirm it shows the right time (in UTC).
🛰️ Repeaters with GPS: let GPS keep the clock
If your repeater has a GPS module and runs firmware 1.14.1 or newer, turn GPS on and it will set its own clock from GPS — and keep re-syncing about every 30 minutes, so it stays correct even after a reboot or power outage. On the repeater's Command Line, send:
gps on
- The GPS needs a view of the sky (outdoors, or right at a window) to get a fix. The first fix can take several minutes.
- Check it with
gps(shows GPS status) andclock(shows the repeater's time in UTC). - To force an update once it has a fix, send
gps sync. - Not every board and GPS combination syncs the clock yet — some RAK and Heltec T114 setups don't. If
clockstill shows May 2024 after the GPS has had time to get a fix, sync the clock from your phone as above.
Step 4: Configure the repeater CLI settings
Once you're logged in and the clock is synced, apply the common settings, your repeater profile and the region commands.
- Go to the >_ Command Line tab.
- Copy a command, paste it and send it — one command at a time.
- Wait up to 30 seconds for an
OKreply. If none comes, send it again.
Step 5: Set owner information
Once the repeater is working, fill in its owner information so other users can plan around it, understand its type and limits, and know who to contact. Anyone can see this through the guest login.
- Log into the repeater from your companion.
- Go to the Settings tab (⚙️), scroll down and tap Owner Info.
- Type your owner information, pressing Enter between sections.
- Tap ✔️ to save and wait for the green success notification.
What to include:
- Owner — your name or callsign
- Specs — antenna (and its dBi rating), node model, power source (solar / wired / battery)
- Installation type — "rooftop", "window", "pole", "tower" — enough for planning, without exact coordinates
Example:
Owner: John Smith
5 dBi omni, Heltec V4, solar powered
House rooftop
Repeater Configuration Profiles
Choose the profile that matches your repeater's role and position in the network. Each profile sets one value, txdelay, which decides how long the repeater waits before retransmitting a flood packet. Repeaters that reach farther go first; lower ones wait.
How to choose your profile
| Profile | Elevation | Neighbors | Typical location |
|---|---|---|---|
| ⚫ BACKBONE | Variable | 1–2 | Dedicated point-to-point link |
| 🔴 CRITICAL | Highest | 20+ | Tower, tall building, high mast |
| 🟠 LINK | Mid | 15–20 | Elevated position bridging towers and neighborhoods |
| 🟡 STANDARD | Average | 5–10 | Suburban roof, elevated home |
| 🟢 LOCAL | Low | 1–3 | Indoor, ground level, low roof |
| 🔵 MOBILE | Variable | Variable (1–10+) | Vehicle, portable, hiking, bike |
| 🟣 BRIDGE | Variable | Variable | ESP32 node bridging two LoRa segments over ESP-NOW |
txdelay 0.5. The profiles below change that default. Mean delays are for a typical ~350 ms packet at our radio settings.⚫ BACKBONE — ultra-fast point-to-point link
Role: a dedicated backbone link between two specific high-value nodes. Use when your repeater is one end of a point-to-point link between two critical infrastructure nodes — minimal delay, maximum throughput.
set txdelay 0.25
Why: the lowest txdelay gives the fastest possible retransmission on a dedicated link — below the MeshCore default of 0.5. Mean delay ~219 ms.
🔴 CRITICAL — tower / tall-building infrastructure
Role: highest elevation, most neighbors, backbone of the mesh. Use when your repeater is on a tower, tall building or high mast with a clear view of many nodes — you can see 20+ neighbors and you're a key link in the network.
set txdelay 0.3
Why: the highest-reach nodes fire first, covering the most area in one transmission before the channel fills with retransmissions from lower nodes. Since MeshCore doesn't cancel pending retransmits, letting the widest-coverage node go early front-loads useful propagation. Mean delay ~263 ms.
🟠 LINK — mid-elevation bridge
Role: connects critical nodes to local coverage, with a moderate number of neighbors. Use when your repeater sits between tall infrastructure and neighborhood coverage — it sees some critical nodes and some local ones (15–20 neighbors is typical).
set txdelay 0.6
Why: fires shortly after the CRITICAL nodes have blanketed the area, filling gaps between tower infrastructure and neighborhood coverage. Mean delay ~525 ms.
🟡 STANDARD — suburban coverage
Role: average position, serves a local area. Use when it's a typical install — an elevated spot serving the surrounding area, seeing 5–10 neighbors.
set txdelay 1.0
Why: waits for CRITICAL and LINK nodes to propagate first, then fills in neighborhood coverage. Mean delay ~875 ms.
🟢 LOCAL — ground level / indoor
Role: low elevation, few neighbors, serves the immediate area. Use when it's an indoor repeater, low rooftop or ground-level install that sees only 1–3 neighbors.
set txdelay 1.4
Why: low nodes with few neighbors defer to higher infrastructure that covers more area per transmission. Mean delay ~1,225 ms.
🔵 MOBILE — vehicle / portable repeater
Role: a moving repeater that extends coverage as it travels. Use when it's mounted in a vehicle, carried on a hike or otherwise moving through the mesh. Neighbors change constantly, so it defers to fixed infrastructure.
set txdelay 2
Why: the maximum txdelay — the mobile node waits as long as allowed before retransmitting, deferring to fixed repeaters where possible. Mean delay ~1,750 ms.
🟣 BRIDGE — ESP-NOW bridge node
Role: links two physically separated LoRa mesh segments over ESP-NOW WiFi. Use when your ESP32-based node is set up as an ESP-NOW bridge, connecting two LoRa segments that can't hear each other. It works as a normal LoRa repeater on its own segment; after it transmits a packet over LoRa, it also forwards it over ESP-NOW to the peer bridge, which injects it into its own segment after a configurable delay.
set txdelay 0.25
set bridge on
set bridge.delay 1000
Why: a bridge is dedicated infrastructure, like BACKBONE, so fast LoRa retransmission keeps latency low on the bridged path. bridge.delay 1000 holds packets received over ESP-NOW for 1,000 ms before they enter the mesh's processing queue, preventing immediate processing conflicts. The bridge also keeps its own seen-packet table, so a packet that arrived over ESP-NOW isn't sent back over ESP-NOW — preventing feedback loops between the two bridges. Range is 0–10,000 ms.
Transmission Delay (txdelay) Explained
| Setting | Default | Range | What it controls | Rule of thumb |
|---|---|---|---|---|
txdelay | 0.5 | 0–2.0 | Wait before retransmitting floods | Higher = let other nodes go first |
The formula:
unit = estimated_airtime × txdelay
delay = random whole number of ms, uniformly from 0 to 5 × unit
For example, with txdelay 1.0 and a 350 ms packet: unit = 350 ms, so the actual delay is anywhere from 0 to 1,750 ms with equal probability — a mean of about 875 ms. It's a continuous spread, not fixed steps.
At our settings (SF 7, BW 62.5 kHz, CR 5) the symbol time is 2.048 ms and typical packets take about 225–460 ms on the air (60–140 bytes). At the ~350 ms midpoint, mean delays per profile are: BACKBONE 219 ms · CRITICAL 263 ms · LINK 525 ms · STANDARD 875 ms · LOCAL 1,225 ms · MOBILE 1,750 ms — the highest-reach nodes fire first and the lowest defer.
| txdelay | Delay window | Collision risk | Propagation speed |
|---|---|---|---|
| High (2.0) | Wide | ✅ Lower | Slower |
| Low (0.3) | Narrow | ⚠️ Higher | Faster |
Common Settings for Acadiana Repeaters
Apply these to every Acadiana Mesh repeater, whatever its profile.
set multi.acks 1
set advert.interval 240
set guest.password
set path.hash.mode 1
set loop.detect minimal
powersaving on
Quick reference
| Setting | Value | What it does |
|---|---|---|
multi.acks | 1 | Sends redundant ACKs for more reliable delivery confirmation |
advert.interval | 240 | Local (zero-hop) advert every 240 minutes, to neighbors only |
guest.password | (blank) | Lets community members check the repeater's status |
path.hash.mode | 1 | 2-byte repeater IDs in packet paths instead of 1-byte — far fewer collisions between repeaters |
loop.detect | minimal | Rejects flood packets that appear to be looping |
powersaving | on | Light sleep between activity, where the board supports it |
Understanding the Settings
Multiple acknowledgments
Controls whether redundant ACKs are sent for direct (point-to-point) messages. 1 sends two ACK packets — a "multi-ack" first, then the standard ACK; 0 sends only one. Redundant ACKs make delivery confirmations much more reliable.
Advert interval
Repeaters periodically announce themselves so other nodes can find them. The local advert every 240 minutes is a zero-hop broadcast to immediate neighbors only, so it doesn't add traffic across the whole mesh.
Path hash mode
When a repeater forwards a flood packet, it stamps a short identity hash (a prefix of its public key) into the packet's path. That path record is what makes MeshCore efficient: the destination can read exactly which repeaters the packet went through and send replies straight back along the same route, without flooding the whole network again. path.hash.mode sets the size of each stamp:
| Mode | Bytes per hop | Unique IDs | Max hops | Practical effect |
|---|---|---|---|---|
| 0 (default) | 1 | 256 | 64 | High collision risk in larger networks. Paths become ambiguous — you can't tell which repeaters a message really passed through, and replies may be misrouted. |
| 1 (recommended) | 2 | 65,536 | 32 | Collisions are negligible at our scale. Paths accurately identify each hop, so routing works correctly. 32 hops is well above real network depth. |
| 2 | 3 | ~16.7 million | 21 | Virtually no collisions. Only useful for very large or dense deployments; the lower hop limit may limit wide-area coverage. |
The hash size is recorded in each packet, so forwarding repeaters read it and adapt automatically. The mode only affects packets your node originates — a repeater set to any mode still forwards flood packets whatever mode the sender used.
Why collisions corrupt paths: with only 256 possible 1-byte values, two repeaters in the same network can easily share one. The path then becomes ambiguous — a hash could mean either repeater — so the path you see is unreliable and replies sent along it can be handed to the wrong repeater at the collision. With 2-byte stamps there are 65,536 values, and the chance of two Acadiana repeaters sharing one is negligible.
Loop detection
loop.detect protects the mesh from packet storms caused by looping flood packets. A misbehaving repeater (for example one running forked or custom firmware) can corrupt a packet and re-forward it, making the same packet circulate up to the 64-hop maximum.
When a flood packet arrives, the repeater looks for its own identity hash in the path. If it appears too many times, the packet is rejected as a likely loop. The threshold depends on the level and the packet's hash size:
- off — no loop checking (the default)
- minimal — tolerant: allows up to 4 repeats of its own hash with 1-byte hashes, 2 with 2-byte, 1 with 3-byte
- moderate — stricter thresholds
- strict — the most aggressive rejection
minimal catches clear loops while staying conservative enough to avoid false positives, so it's the recommended starting point. It works even with 1-byte paths.
Power saving mode
Puts the repeater into light sleep between activity to save power. The radio wakes on incoming packets or a scheduled timer. Power saving is handled by the firmware and board — powersaving on enables it where supported.