|
|
| Line 2: |
Line 2: |
| [[Main Page|← Home]] | | [[Main Page|← Home]] |
|
| |
|
| = Getting Started with MeshCore = | | = Getting Started with Meshtastic = |
|
| |
|
| MeshCore is a lightweight, repeater-focused mesh protocol. In Ottawa, most of the city runs MeshCore, with coverage provided by a network of solar-powered repeaters.
| | Meshtastic is a peer-to-peer LoRa mesh where every node can forward packets. This guide will help you flash Meshtastic firmware onto your device and configure it for use in the local mesh. |
| This guide will help you flash a node, configure it as a companion, or set it up as a repeater. | |
|
| |
|
| == Flashing a Node == | | == Flashing a Node == |
| The easiest way to flash a MeshCore-supported node is by using the official web flasher tool in Google Chrome: | | The easiest way to flash a Meshtastic node is by using the official web flasher tool in Google Chrome: |
|
| |
|
| [https://flasher.meshcore.co.uk/ MeshCore Web Flasher] | | [https://flasher.meshtastic.org/ Meshtastic Web Flasher] |
|
| |
|
| Only '''Google Chrome''' supports the serial connection required for flashing. | | Only '''Google Chrome''' supports the serial connection required for flashing. |
|
| |
|
| Steps:
| | For full step-by-step instructions, see the official guide: |
| # Plug your device into your computer via USB.
| | [https://meshtastic.org/docs/getting-started/flashing-firmware/ Meshtastic Flashing Firmware Guide] |
| # Open the [https://flasher.meshcore.co.uk/ MeshCore Web Flasher].
| |
| # Select your device type (for example: '''Companion Radio (Bluetooth)''' or the hardware model you’re flashing).
| |
| # Click '''Enter DFU Mode'''.
| |
| # Click '''Erase Flash'''.
| |
| # Click '''Flash''' to install the MeshCore firmware.
| |
| | |
| '''Note:''' Sometimes after erasing, the flash step may fail. If this happens, refresh the page, click '''Enter DFU Mode''' again, and then click '''Flash''' to retry.
| |
|
| |
|
| == Configuring a Companion Node == | | == Configuring a Companion Node == |
| After flashing, follow these steps to set up your companion node: | | After flashing, you’ll need to configure your device for local use. |
|
| |
|
| # Pair the node with your phone or computer (usually over Bluetooth).
| | Follow the official guides here: |
| # Give the node a descriptive '''name''' (e.g. your callsign, location, or handle).
| | * [https://meshtastic.org/docs/getting-started/initial-config/ Initial Configuration Guide] |
| # Set it to the Ottawa frequency defaults: '''910.525 MHz / BW: 62.5 kHz / SF7 / CR5'''.
| | * [https://meshtastic.org/docs/configuration/ General Configuration Reference] |
| # Test by sending a message in the '''Public channel'''.
| |
| * If a repeater hears you, the message will show '''Heard X Repeats''' instead of just '''Sent'''.
| |
|
| |
|
| '''Tip:''' You may wish to disable '''Message Settings → Auto Reset Path'''. This isn’t required, but many users find it helpful when testing links that aren’t fully stable, as it prevents the path from constantly resetting.
| | When configuring your node, ensure you set the Ottawa frequency preset: |
| | '''US/LongFast – 906.875 MHz''' |
|
| |
|
| == Configuring a Repeater == | | == Configuring a Repeater == |
| Repeaters cannot be managed over BLE. Once repeater firmware is flashed, BLE is disabled on the node.
| | Meshtastic does not use dedicated repeater-only nodes by default. |
| Configuration must be done either over '''USB''' or via '''MeshCore Remote Administration''' using a companion node and the mobile app.
| | Any stationary node left powered on can function as a repeater, forwarding packets between other users. |
| | |
| === Basic setup after flashing ===
| |
| # Using Google Chrome, open the repeater configuration tool: [https://config.meshcore.dev/ MeshCore Repeater Config].
| |
| # Give the node a descriptive '''name''' (e.g. '''Callsign_R1''' or a location-based name).
| |
| # Set an '''admin password''' for the repeater — this is required for remote management over MeshCore.
| |
| # Apply the Ottawa frequency defaults: '''910.525 MHz / BW: 62.5 kHz / SF7 / CR5'''.
| |
| # Click '''Save''' and reboot the node.
| |
| # Reconnect to the device using the configuration tool and click '''Send Advert'''.
| |
| * If your repeater is running correctly, you should see the advert appear on nearby companion nodes.
| |
| | |
| === Advert timings in Ottawa ===
| |
| After the repeater has been configured and discovered by your companion node, log into it via MeshCore Remote Administration and set the following advert intervals:
| |
| * '''Zero-hop adverts (direct):''' every 1 hour
| |
| * '''Flood adverts (forwarded across repeaters):''' every 3 hours
| |
| | |
| '''Tip:''' After every reboot, you must resync the repeater’s clock.
| |
| The repeater will still route messages without a clock, but its adverts will be ignored until the time is set.
| |
| | |
| == How Adverts Work ==
| |
| MeshCore uses a '''repeater-driven advert system''' for discovery (not a prerequisite to transmit).
| |
| | |
| * '''You do not need to have recevied an advert from a repeater to send a message.''' You can transmit at any time; any repeater that hears your packet will forward it.
| |
| * Adverts allow your node to '''discover repeaters''' (their ID and info). This enables features such as:
| |
| * Tracing paths to confirm connectivity
| |
| * Seeing repeater names in the path summary of a message
| |
| * Setting static paths to a specific user
| |
| * Repeaters periodically broadcast '''adverts''' (short beacon packets) across the mesh.
| |
| * In Ottawa, adverts are configured for:
| |
| * '''Zero-hop adverts (direct):''' every 1 hour
| |
| * '''Flood adverts (forwarded across repeaters):''' every 3 hours
| |
|
| |
|
| This approach keeps discovery traffic low while still ensuring that repeaters can be identified and messages are reliably forwarded across the mesh.
| | If you want to build a fixed repeater-like node: |
|
| |
|
| == The Public Channel ==
| | '''Steps:''' |
| By default, MeshCore companion nodes in Ottawa have access to the shared '''public channel'''.
| | # Place a node at height with good line-of-sight. |
| | # Power it continuously (mains or solar recommended). |
| | # Disable Bluetooth to save power and reduce interference (optional). |
|
| |
|
| * Any correctly flashed node set to the correct frequency can join immediately and begin passing traffic. | | **Important:** Do *not* change the device role from "Client" unless you understand the implications fully—and preferably only after consultation with the community. |
| * When you send a message and a repeater hears it, you will see '''Heard X Repeats''' under your message (instead of just '''Sent''').
| | Learn more on Meshtastic’s device roles to guide your decision: |
| * You can click and hold the message, then select '''Heard Repeats''' to see which repeaters heard it.
| | [https://meshtastic.org/blog/choosing-the-right-device-role/ Choosing the Right Device Role] |
| * If you have discovered the repeater through adverts, you will see its '''name'''.
| |
| * If not, you will see only its '''ID'''.
| |
|
| |
|
| == Next steps ==
| | This approach helps your node become reliable infrastructure for nearby users. |
| Once your node is flashed and configured, check out [[MeshCore/Frequency Settings]] for Ottawa defaults and [[MeshCore/Repeaters & Coverage]] for areas with established repeater links.
| |
← Home
Getting Started with Meshtastic
Meshtastic is a peer-to-peer LoRa mesh where every node can forward packets. This guide will help you flash Meshtastic firmware onto your device and configure it for use in the local mesh.
Flashing a Node
The easiest way to flash a Meshtastic node is by using the official web flasher tool in Google Chrome:
Meshtastic Web Flasher
Only Google Chrome supports the serial connection required for flashing.
For full step-by-step instructions, see the official guide:
Meshtastic Flashing Firmware Guide
Configuring a Companion Node
After flashing, you’ll need to configure your device for local use.
Follow the official guides here:
When configuring your node, ensure you set the Ottawa frequency preset:
US/LongFast – 906.875 MHz
Configuring a Repeater
Meshtastic does not use dedicated repeater-only nodes by default.
Any stationary node left powered on can function as a repeater, forwarding packets between other users.
If you want to build a fixed repeater-like node:
Steps:
- Place a node at height with good line-of-sight.
- Power it continuously (mains or solar recommended).
- Disable Bluetooth to save power and reduce interference (optional).
- Important:** Do *not* change the device role from "Client" unless you understand the implications fully—and preferably only after consultation with the community.
Learn more on Meshtastic’s device roles to guide your decision:
Choosing the Right Device Role
This approach helps your node become reliable infrastructure for nearby users.