MeshCore/Getting Started: Difference between revisions

From Ottawa Mesh
Jump to navigation Jump to search
← Older edit
No edit summary
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Configuring a Repeater ==
__NOTOC__
Repeaters cannot be managed over BLE. Once repeater firmware is flashed, BLE is disabled on the node. 
[[Main Page|← Home]]
Configuration must be done either over '''USB''' or via '''MeshCore Remote Administration''' using a companion node and the mobile app.


=== Basic setup after flashing ===
This guide will help you flash a node, configure it as a companion.
'''Important:''' Before configuration, you must update the bootloader on RAK boards. 
Without this fix, failed OTA updates can leave the repeater in an unusable state that requires physical recovery.


# Download the OTA bootloader fix from [https://github.com/oltaco/Adafruit_nRF52_Bootloader_OTAFIX/releases/download/0.9.2-otafix1/update-wiscore_rak4631_board_bootloader-0.9.2-otafix1_nosd.uf2 this link]. 
== Flashing & Configuring a Companion Node ==
# Connect your repeater to your computer. 
=== Flashing a Companion Node ===
# It should appear in your file explorer as a '''USB Drive'''. 
The easiest way to flash a MeshCore-supported node is by using the official web flasher tool in Google Chrome:
# Drag the '''.uf2''' file into the mounted drive. 
# The file copy will appear to fail, and the device will restart and remount as a USB drive — this is expected and indicates a successful update. 
# To confirm, open the '''INFO.TXT''' file on the drive and check that it shows version '''0.9.2 bootloader firmware'''. 


Once the bootloader is updated, continue with repeater configuration:
[https://flasher.meshcore.co.uk/ MeshCore Web Flasher]


# Using Google Chrome, open the repeater configuration tool: [https://config.meshcore.dev/ MeshCore Repeater Config]. 
Only '''Google Chrome''' supports the serial connection required for flashing.
# After connecting to the device, navigate to [[MeshCore/Repeaters & Coverage#Ottawa Repeater IDs|Ottawa Repeater IDs]] and make sure the first two characters of your public key are not already in use. 
  * Currently, MeshCore repeater IDs are based on the first two characters of the public key. 
  * As the mesh has grown, duplicate IDs have caused conflicts. It is important to avoid duplicates. 
  * Developers are working on a long-term fix, but for now, each new repeater must use a unique ID. 
  * If you have a conflict, the only way to generate a new public key is to reflash the firmware. Follow [[MeshCore/Getting Started#Flashing a Node|Flashing a Node]] from the beginning. You can skip the bootloader fix if you have already applied it once. 
# 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.


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:  
Steps:
# Plug your device into your computer via USB.
# Open the [https://flasher.meshcore.co.uk/ MeshCore Web Flasher].
# Select your device hardware
# Select the firmware choice '''Companion Radio (Bluetooth)'''
# Click '''Enter DFU Mode'''.
# Click '''Erase Flash'''.  
# Click '''Flash''' to install the MeshCore firmware.


# '''Zero-hop adverts (direct):''' every 1 hour 
'''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.
# '''Flood adverts (forwarded across repeaters):''' every 3 hours 
# Click Save 


'''Tip:''' After every reboot, you must resync the repeater’s clock.   
=== Configuring a Companion Node ===
The repeater will still route messages without a clock, but its adverts will be ignored until the time is set.
After flashing, follow these steps to set up your companion node:
 
# Pair the node with your phone or computer (usually over Bluetooth). 
# Give the node a descriptive '''name''' (e.g. your callsign, location, or handle). 
# Set it to the Ottawa frequency defaults: '''910.525 MHz / BW: 62.5 kHz / SF7 / CR5'''. 
# 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.

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.

Retrieved from "https://ottawamesh.ca/index.php?title=MeshCore/Getting_Started&oldid=254"