MeshCore/Getting Started: Difference between revisions

From Ottawa Mesh
Jump to navigation Jump to search
No edit summary
No edit summary
 
(23 intermediate revisions by the same user not shown)
Line 2: Line 2:
[[Main Page|← Home]]
[[Main Page|← Home]]


= Getting Started with MeshCore =
This guide will help you flash a node, configure it as a companion.


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. 
== Flashing & Configuring a Companion Node ==
This guide will help you flash firmware onto a companion node and understand how adverts and the public channel work.
=== Flashing a Companion Node ===
 
The easiest way to flash a MeshCore-supported node is by using the official web flasher tool in Google Chrome:
== Flashing Firmware onto a Companion Node ==
The easiest way to flash a MeshCore companion node is by using the official web flasher tool in Google Chrome:


[https://flasher.meshcore.co.uk/ MeshCore Web Flasher]
[https://flasher.meshcore.co.uk/ MeshCore Web Flasher]
Line 15: Line 13:


Steps:
Steps:
# Plug your companion node into your computer via USB.
# Plug your device into your computer via USB.
# Open the [https://flasher.meshcore.co.uk/ MeshCore Web Flasher].
# Open the [https://flasher.meshcore.co.uk/ MeshCore Web Flasher].
# Select your device type: '''Companion Radio (Bluetooth)'''.
# Select your device hardware
# Select the firmware choice '''Companion Radio (Bluetooth)'''
# Click '''Enter DFU Mode'''.
# Click '''Enter DFU Mode'''.
# Click '''Erase Flash'''.   
# Click '''Erase Flash'''.   
# Click '''Flash''' to install the MeshCore firmware.
# Click '''Flash''' to install the MeshCore firmware.
# When complete, the device will reboot and begin listening on the Ottawa defaults ('''910.525 MHz / BW: 62.5 kHz / SF7 / CR5''').


'''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.
'''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.


== How Adverts Work ==
=== Configuring a Companion Node ===
MeshCore uses a '''repeater-driven advert system''' for discovery (not a prerequisite to transmit).
After flashing, follow these steps to set up your companion node:
 
* '''You do not need to hear an advert 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.
 
== The Public Channel ==
By default, MeshCore companion nodes in Ottawa have access to the shared '''public channel'''. 


* Any correctly flashed node set to the correct frequency can join immediately and begin passing traffic.   
# Pair the node with your phone or computer (usually over Bluetooth).   
* When you send a message on the public channel and a repeater hears it, you will see '''Heard X Repeats''' under your message (instead of just '''Sent''').   
# Give the node a descriptive '''name''' (e.g. your callsign, location, or handle). 
* You can click and hold the message, then select '''Heard Repeats''' to see which repeaters heard it.   
# Set it to the Ottawa frequency defaults: '''910.525 MHz / BW: 62.5 kHz / SF7 / CR5'''.   
  * If you have discovered the repeater through adverts, you will see its '''name'''
# Test by sending a message in the '''Public channel'''.   
  * If not, you will see only its '''ID'''.   
  * If a repeater hears you, the message will show '''Heard X Repeats''' instead of just '''Sent'''.   


== Next steps ==
'''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.
Once your node is flashed and connected, check out [[MeshCore/Frequency Settings]] for Ottawa defaults and [[MeshCore/Repeaters & Coverage]] for areas with established repeater links.''

Latest revision as of 19:54, 2 September 2025

← Home

This guide will help you flash a node, configure it as a companion.

Flashing & Configuring a Companion Node

Flashing a Companion Node

The easiest way to flash a MeshCore-supported node is by using the official web flasher tool in Google Chrome:

MeshCore Web Flasher

Only Google Chrome supports the serial connection required for flashing.

Steps:

  1. Plug your device into your computer via USB.
  2. Open the MeshCore Web Flasher.
  3. Select your device hardware
  4. Select the firmware choice Companion Radio (Bluetooth)
  5. Click Enter DFU Mode.
  6. Click Erase Flash.
  7. 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

After flashing, follow these steps to set up your companion node:

  1. Pair the node with your phone or computer (usually over Bluetooth).
  2. Give the node a descriptive name (e.g. your callsign, location, or handle).
  3. Set it to the Ottawa frequency defaults: 910.525 MHz / BW: 62.5 kHz / SF7 / CR5.
  4. 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.