Thread with notes on my #meshcore experiment 🧵
Given the most recent issues with #meshtastic (uncollaborative MQTT chatters, limited number of hops, difficulty in convincing others to change device roles), I decided to give MC a try. I'll document the journey here as I go.
I've just used the #meshcore web flasher for the first time. For some reason, I never got the #meshtastic web flasher to work with any of my devices (Heltec or RAK). Must be something with my laptop.
Surprisingly, the MC web flasher worked in the first try! Okay, we're off to a good start I guess.
The process of flashing a #meshcore repeater is slightly more cumbersome than #meshtastic. There's no BLE connectivity, so I'm forced to do it either via a Chrome-based browser or a CLI tool (I suppose) through the serial interface.
[I'm thinking of my camouflaged Gitfos GAT562 node. I'll have to solder the pins and dust off my UART cable.]
Other than that, configuring it is super straightforward. There's no Brazilian preset in the list, so falling back to 'Australia' which works here.
Flashing the #meshcore companion now and... I must choose the firmware that has either USB connectivity or BLE, but not both.
That's unexpected. Anyone knows the reason for this limitation?
@py2toz From an earlier, cursory examination of the #meshcore repo, it looked like the structure of the companion app was to await upon commands from only one source. So either it's compiled to look at the BLE interface, or from the USB UART.
It's a very single-threaded way of doing things, but it kinda makes sense since this application is meant to accompany the mobile app or a desktop app. But not necessarily both simultaneously.
Lots of impressions with the #meshcore app so far, good and bad.
* Remote management pops up an alert that it's a "freemium" app, and that I should support the developers (& wait for the count down to finish). Fair enough, but a bit intrusive.
* Node position is not updated from phone.
* SNR is 12 dB vs #meshtastic's 7 db in avg. I wonder which one is right?
* The Noise Floor tool is a REALLY nice touch!
* Source code not available, so I can't contribute.
Can't wait for the field test!
@py2toz as far as I know the project is under a mit license.
Look for example at the
https://nodakmesh.org/blog/meshcore-open-app-free-open-source-meshcore-client
for an alternative.
Possible Alternative firmware:
https://github.com/mattzzw/MeshCore-Evo
I haven’t tried out but looks promising.
MeshCore Open is a free, open-source companion app for MeshCore LoRa mesh devices. Available on Android, iOS, Linux, Windows, macOS, and web — with repeater management, offline maps, path tracing, and 15 languages. No subscription, no paywall.
Brazil has only 30 #meshcore devices vs. ~1400 #meshtastic ones. But it's been only 8 hours since I started dabbling in MC and I've already connected with an operator who does maintenance work for ham radio towers. They are all located around São Paulo's tallest hills, and he's totally into deploying some MC nodes in the coming weeks.
If that happens, this is going to be a complete game changer for the MC scene in the state of São Paulo.
@py2toz I'll be interested to see how it goes for you.
I was running meshtastic repeaters in my area, but had all the same issues you mentioned (plus a bunch of jerky behavior by other operators).
I switched to MC in January, and it's a whole new ball game. The local MC mesh is a collaborative effort that now stretches across all inhabited (and many uninhabited) areas of our county. It stretches about 400mi N/S and 150mi E/W at present.
It's a huge amount of progress so far, all of which has involved folks deploying nodes in the dead of winter on pretty rugged terrain.
Bruno PY2TOZ
Node Star
Charlie
Alec Perkins
Litchralee
kresse
𝕕𝔼cⒶ𝕪