Off Grid mesh network using cheap LoRa radios. Alternative to Meshtastic.
In Meshtastic all nodes are pretty much equal. All of them will repeat messages they hear. The TTL or how many hops a message can take is usually limited to 4.
MeshCore is a bit different. Devices are split into two categories, Companion and Repeater.
Companions is the one you carry with you. It connects to your phone or PC over bluetooth/usb/wifi. It never repeat messages and can only do direct packet sending (and receiving) to a another Companion or a Repeater.
Repeaters only have LoRa radio powered on and will only do message repeating. They are usually also quite stable in the sense of power and position. MeshCore message TTL or hop count is limited to 64 (compared to 4 in Meshtastic).
Meshtastic works better as adhoc network in a smaller area. MeshCore work better with stable repeaters and over a larger area. MeshCore also by default will be more quiet on the radio and only transmits if you trigger it to.
First time Companion and Repeater setup will require you to setup the radio. In Tallinn we use EU/UK (NARROW) preset. After that click on the apply tick in top right corner to save it.
| Frequency | Bandwith | Spreading Factor | Coding Rate |
|---|---|---|---|
| 869.618Mhz | 62.5Khz | 8 | 8 |
After Radio setting are configured, you will have to do a Advert to broadcast your device Public Key to the rest of the network. That will tell others your name and also provides them with your key for message encryption.
When ordering, Make sure to select 868Mhz model!
Most Meshtastic devices are also compatible with MeshCore by just flasing a new firmware usin a Web based flasher https://flasher.meshcore.co.uk/ (works only with Chromium based browsers)

The included antennas should be okay to start out with. But if you want you can upgrade to something better.
Flash OTAFIX bootloader on
nrfbased repeaters to make over the air updates safe https://github.com/oltaco/Adafruit_nRF52_Bootloader_OTAFIX
Baudrate is 115200.
CLI commands are documented here https://docs.meshcore.nz/cli_commands/
Basic setup commands that mirror the click-ops instructions look like this
set radio 869.618,62.5,8,8
set name Arti Energia
set owner.info meshcore@arti.ee
set lat 59.396755
set lon 24.767530
password changeme
reboot
If using this firmware then also set https://analyzer.letsmesh.net/observer/onboard?type=repeater&version=observer-uplink-native-dev
set wifi.ssid EnergiaWifi
set wifi.pwd changeme
set mqtt.iata TLL
set mqtt.owner YourCompanionPublicKey
set mqtt.email meshcore@arti.ee
reboot
Repeater Hops are identified by its first 2 hex character. Unique combinations are limited to 255 so in a large network there will be duplicates. To mitigate this a bit please check
https://analyzer.letsmesh.net/nodes/prefix-utilization?region=TLL for free prefixes and generate a new key using https://gessaman.com/mc-keygen/
K-Space has one Heltec T114 configured as a repeater connected to a raspberry pi for power.
We are also hosting K-Space Bot connected to Terminal Server on 100.103.0.10 using LilyGo T3 S3.
Arti is hosting one additional repeater in Energia street and few others around Tallinn.
Aka, driving/walking around and maping signal strength on a map.
And