Meshtastic: A Review
tylercipriani.com
tylercipriani.com
Would also be nice not to connect with bluetooth. Either connect with a cable, make it an all-in-one texter/transmitter, or make it all-in-one but detachable. I guess this is starting to reach, but bluetooth is just too finicky for something with this use case IMO. I can see the value in wireless pairing though - you could put the transmitter up a bit higher and text on the ground.
Looks like they don’t encrypt, though.
https://pocket.popcorncomputer.com/
Not much activity during last year, however.
The concept is of interest to me, as I like writing code to help people that help people. I’ll bet I could write a really nice Apple SDK and iOS app. I noticed the reviewer wasn’t too thrilled with their iOS app.
I did try working with goTenna, but they won’t open up their low-level API, and I don’t like using closed-source SDKs (that other people wrote —I have issues), for the most part.
I’m having difficulty with their documentation. It seems a bit scattershot. I’ll keep looking, but it appears as if there isn’t a place that simply lists the interface parameters. I would probably use BLE, and I suspect they do serial over BLE (I think goTenna does the same). Not a problem, as long as the AT commands are listed and explained, somewhere.
It appears as if we are supposed to figure out what various commands are, by reading the firmware spec, at different parts of the docs.
Without that unified AT command reference, I'm not even gonna try (for now, at least). My dance card is too full, to spend a bunch of time, with my BLE explorer, testing out commands.
If they published it, I’d probably scare up a cross-[Apple]-platform BLE-based SDK. I already have the BLE part written[0]. This is used in my BLE Explorer App[1], or the test harnesses could be used to explore the device. It would just be a matter of writing the command interpreter.
[0] https://github.com/RiftValleySoftware/RVS_BlueThoth
[1] https://riftvalleysoftware.com/work/ios-apps/bluevanclef/
I wanted to enable global delivery by having gateways that would join a DHT and help different mesh's to have global delivery with via a raspberry pi or similar gateway. That received a hard no on their mailing list. Was even considering using the bittorrent DHT, there's a BEP to use up to 1KB of storage on DHT peers.
A few months later I saw they were offering global delivery to their enterprise customers.
It would allow a cheaper emergency connection to society than satphones, and could potentially allow for some waypoint following with modern gps trail navigating phone apps.
Curious if anyone has experience with Meshtastic and/or outdoor adventuring and could weigh in.
If you use the default meshtastic build you can forego a screen and use the cli to tweak the node and even disable it's gps for better battery.
There is work happening on a dedicated "repeater" codebase too.
The discord is pretty active: https://discord.gg/ktMAKGBnBs
https://www.etsy.com/listing/1048791528/solar-powered-off-gr...
> The T-Beams run off big honkin’ 18650 batteries—the same lithium-ion cells used in Tesla battery packs.
While this is true, it seems unnecessarily alarming. 18650 are also the type of cells inside old-ish laptop removable batteries, which are far more common and don't frighten people.
"Yes, they literally wire 'em together to power a lawn mower."
I wonder if Meshtastic can bring back some of that experience, and be used as a way to access my own bandwidth from miles away? Anyone know if SLIP/PPP is usable over LoRA?
I don't know what it is, but from the article it appears to be a secondary device (Meshtastic) you pair with your iPhone/Android phone via Bluetooth. This secondary device has the giant Lithium cells and microcontroller with the LoRa antenna setup.
Some software package on the phone, perhaps a messaging like app, sends message data (AES encrypted) between your phone and the Meshtastic device. The Meshtastic device somehow knows which other Meshtastic devices to send/receive from?
Feels like the phone shouldn't even be needed is a simple LCD display and tiny keyboard were added to the Meshtastic? (And I suppose the en(de)cryption would have to be done on the device now.
The phone provides a familar interface AND the GPS cords for texting locations (and possibly pinning on maps already present on phone when WEB-Maps are offline (google, bing, other, etc).
Once matured it will have some application for hikers on trails away from cell tower coverage sans Starlink access.
I'm used to rural fire brigade trucks and SES rescue vehicles that have a slew of standalone radio gear and multiple GPS units already fitted .. but I can see some scope for this when looking for lost tourists and city folk.
It also took 20 minutes for first GPS sync, which was less fun.
This is true in a common base case (LilyGO T-Beam neo6m with stock antenna) but is easily fixed. The stock antennas are absolutely pathetic and something like https://www.mouser.com/c/?q=GP.1575.25.4.A.02 is much much better. The other significant improvement is using a board with a better GPS module, like the M8N version of the T-Beam.
While the T-beams are nice for having screens and gps, the RAK based devices have better battery life.
I don't know why but there doesn't really seem to be a push to so better on FM digital modes compared to what you see with FT-8.
It feels like outdated tech to me, all the hardware is generally big, slow, power hungry, and expensive.
The APRS system also has issues with timing and flooding a channel if there are too many stations in one area.
Seems pretty common to put similar bare boards in people playing with high altitude balloons.
Sure APRS has limits, but keep in mind that you don't have to use the "APRS" frequencies, for high density uses like say a bike/horse/foot race it's pretty common for support teams to have APRS to help coordinate and to use a non-standard frequency.
So tracking 1000s of devices second by second, sure that's not going to work well.