Albuquerque and Trail Configuration
Start Here
ABQ Mesh uses the default LongFast channel and settings. A new radio can connect with almost no configuration beyond setting the country, provided another node is within RF range.
This guide is intentionally not a general Meshtastic tutorial. If Meshtastic itself is new to you, start with the official Meshtastic Introduction or browse the Meshtastic documentation, then come back here for the Albuquerque and trail-specific configuration.
Outside the mesh itself, the group is most active on its public Discord server.
Quick Setup
- Get a Meshtastic radio. The LILYGO T-Echo is a ready-to-go first radio, while the T1000-E is a compact pocket node. Meshtastic maintains a list of supported hardware.
- Install the app. Download the Meshtastic app for iPhone or Android.
- Pair the radio. Connect your phone to the radio with Bluetooth.
- Set your region. If the region is UNSET, select United States and allow the radio to reboot.
- Say hi. Open the Primary / LongFast channel and send a message.
Detailed Setup
Apple / iOS
LoRa
- Region
- United States
- Use Preset
- On
- Preset
- Long Range - Fast
- Ignore MQTT
- Off
- OK to MQTT
- On
Primary Channel
- Channel details
- Do not modify
- Positions
- Enabled
- Approx. location
- 0.5 mi
- MQTT Uplink
- Enabled
- MQTT Downlink
- Enabled
User
- Long name
- Up to 36 characters
- Short name
- Up to 5 characters
- HAM mode
- Off
Position
- Broadcast
- 60 minutes
- Smart Position
- Enabled
- Minimum interval
- 30 seconds
Android
Pair the radio, open the app, add the device, enter the displayed PIN (or 123456 for a node without a screen), allow notifications, and set the region to United States if it is UNSET.
LoRa
- Hop limit
- 3–4
- OK to MQTT
- Enabled
- Ignore MQTT
- Off / disabled
LongFast
- Channel details
- Do not modify
- Uplink / Downlink
- Enabled
- Position
- Enabled
- Precise location
- Disabled
- Location slider
- 1.8 mi or less
User
- Long name
- Up to 36 characters
- Short name
- Up to 4 characters
- HAM mode
- Off
Device + Position
- Role
- Client
- Rebroadcast mode
- All
- Node info broadcast
- 3600 seconds
- Position broadcast
- 3600 seconds
- Smart Position
- Enabled
- Minimum interval
- 1800 seconds
- Minimum distance
- 100
- GPS update
- 1800 seconds
Best Practices
| Everyday reference | Recommended setting | Why |
|---|---|---|
| Role | Client | Not Router & Client |
| Hop Count | 3–4 | Use the minimum needed |
| Broadcasts | 1 hr | Info, position, telemetry |
Device role
Client Mute is recommended for mobile users and poorly placed nodes, while Client is appropriate for well-placed nodes. Avoid casually choosing infrastructure roles because poorly placed infrastructure nodes can create undesirable routing paths.
Hop count
Start at 3–4 and use the minimum number of hops needed. A hop count of 5 may make sense when a home client routinely goes through a relay. A hop count of 6 may help at the network edge, but only after node hardware and placement have been optimized.
Broadcast intervals
For everyday use, keep routine broadcasts conservative to reduce channel utilization: position at one hour, Smart Position enabled, a 30-minute minimum interval, minimum distance 100, and a 30-minute GPS update interval.
MQTT
MQTT can bridge physically separated meshes through an Internet-connected gateway. ABQ Mesh uses MQTT as part of its local network design, but the broker, topic, credentials, and other Albuquerque-specific connection details remain deferred until they can be verified.
Meshtastic for Overlanding
Add a private convoy channel
Keep LongFast intact for Albuquerque interoperability, then add a separate channel for the vehicles and people traveling together. Give that channel its own strong pre-shared key (PSK) and share the channel configuration only with the group.
This does not replace GMRS, ham, CB, or another voice radio. Meshtastic works well as a quiet data layer: short messages and positions that remain available when somebody misses a voice call or moves beyond direct radio range.
Public LongFast
- Purpose
- Local mesh participation
- Audience
- Public / local community
- Position
- Approximate / fuzzy
- Configuration
- Keep ABQ baseline
Private Convoy
- Purpose
- Trip coordination
- Audience
- Your traveling group
- Encryption
- Unique strong PSK
- Position
- Useful trail precision
Position: public vs. group
On LongFast, approximate position protects some privacy while still providing useful presence. Within a trusted traveling group, more accurate position data can make it possible to navigate back to a separated or disabled vehicle.
Position frequency on a trip
The everyday one-hour ABQ interval is intentionally conservative. During an active trail day, a group may choose a shorter interval so the last-known position remains useful. Terrain, convoy spacing, battery capacity, node count, and mesh congestion all matter.
Trail scenarios
“I stopped at the fork. Continue to camp; I’ll catch up.” The instruction remains visible even if the voice call was missed.
“Stopped with a tire issue. Come back to my location.” The request can arrive with the vehicle’s reported position.
“Bring fresh AA batteries to my location.” A short message can communicate the need while the node still has power and a packet path exists.
“Road blocked. Turning around. Meet at the last junction.” The group has a written instruction that can be compared with last-known positions.
Last known means last known
A position report is not proof that a vehicle is still there. If the last position was received 38 minutes ago, read it as last known position, 38 minutes old, not “the vehicle is here.”
Power planning
The radio only helps while it is operating. Include Meshtastic nodes in the same pre-trip power check as phones, satellite messengers, and voice radios.
Useful, not guaranteed
- Packets can be lost and terrain can isolate nodes.
- Nodes can be switched off, damaged, or run out of power.
- GPS and displayed positions can be stale.
- A mesh path can disappear after vehicles move.
MQTT on the trail
MQTT can connect separate meshes when an Internet path exists somewhere in the system. Treat it as an optional bridge when infrastructure is available, not as the foundation of an off-grid trail workflow.