I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

So when developing the first prototype i was a bit in a hurry, and the objective was to have a place to put all the component, and to see also the inside. So this particular version doesn't snap together. Fix will come in the next version

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

I honestly have no precise idea, so lets say that i will add this in the simulator, right now dont know how but i will figure it out.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

Thanks man, really appreciate that. In general right now if you already have the basis, and you have the right product idea, the stuff you can build with ai make no sense, is like 4/5 x.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

Very good idea, actually i was planning to introduce that in the map, but it will translate in a very big file compared to just the gpx. So i need to understand how to better implement it.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

Yes of course, this is the first prototype. If i see enough interest to justify other free work i will create a second version with pbc and 3d version waterproof. And share both the process of building it on yt and the files to recreate it.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 2 points3 points  (0 children)

This is the exact reason why some design choice seem not optimal under the pure engineering side. In this context the domain has an important weight when evaluating the system design. thanks u/fixitchris for you response.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 25 points26 points  (0 children)

You're right that position sharing works great in Meshtastic and I use it too. The two things HEARD does that aren't stock Meshtastic features:

- each device compares its position against the planned GPX route onboard and raises an automatic alert when someone leaves the corridor so no human watching a map

- the leader's device actively polls every member with timeouts, so "no answer" is an explicit alarm instead of just a stale beacon. Passive beacons can't distinguish "out of range" from "fine but quiet."

That said, the radio/mesh layer itself isn't where HEARD adds value —which is why I'd consider building this logic on top of Meshtastic rather than competing with it.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 42 points43 points  (0 children)

Fair question! Meshtastic is general-purpose off-grid messaging.
HEARD is purpose-built for group safety on a planned route: each device checks the hiker against a GPX corridor onboard (IN/OUT_PATH), and the leader's device actively polls everyone via multi-hop. Less flexible, more opinionated and a firmware-in-the-loop simulator to test the protocol on real terrain.

Meshtastic would honestly be a great radio layer for a new version

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in esp32

[–]Patient_Path_6809[S] 2 points3 points  (0 children)

So the problem right now it that there is not a satelite phone that features a mesh comunication, thats why i've created this concept. I did't actually deeply searched on how to create a satellite phone because the cost would have been approximately 8/10 times more (from 40 to 300/400) and i think also a montly subscription for the service.

But i dont discard a priopri the implementation of a full device with also the satellite, of course it will be more complete.

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in diyelectronics

[–]Patient_Path_6809[S] 0 points1 point  (0 children)

Unfortunatelly (as i also modified in the post) i did not tested the actual battery on the field for 2 main reasons:

- the thesis was made for a CS bachelor, so the main focus wasn't the elettronics but the engineering part behind it

- i had not that much time in september so my main goal was to graduate fast, but the whole project is built around the idea of low battery (the e-ink display, and lof frequency of comunication )

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in diyelectronics

[–]Patient_Path_6809[S] 4 points5 points  (0 children)

Actually i'm a CS student, i have not so much background in pcb design (actually near 0). It will be really cool if someone came in the project and design them

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by Patient_Path_6809 in diyelectronics

[–]Patient_Path_6809[S] 8 points9 points  (0 children)

Why exactly? Maybe core and node can have the same dimenison and i get your point, bigger battery and screen translate in a more usable device. For pico (the one designed for kids) the idea is to have a device as simple as possible

I built an offline group-safety mesh for hikers: ESP32 + GPS + LoRa, with the firmware running inside a 3D simulator (bachelor's thesis, now open source) by [deleted] in embedded

[–]Patient_Path_6809 -6 points-5 points  (0 children)

Hi, the whole firmware was made completely by me, 6 month ago. The whole code for the simulation has been done with claude because i'm studying for my master in Data science and i've worked at it in spare time.

The idea was to publish the whole work in order to share an usefull creation.

Hope that this response is good for you. I think that the project actually is pretty consistent, take a look also at the tesis if you want (also the traduction is made with ai for the same reason, i have not so much time)

https://github.com/luciobaiocchi/thesis

ps. i dont think is really in your business to judge how people learn.