I started experimenting with meshtastic in December last year, but so far it has been a really quiet network, so I'm not seeing the congestion problems the author highlights. According to meshmap there should be a node ~2 miles from my house but I don't reliably see it. I don't see the next closest at 4.3 miles either. For some reason I saw the next furthest (~8.4 miles) for a few days, but it has since disappeared. Since Christmas I've seen 583 nodes from mine - none reliably.
My node is a solar powered tree hanger hanging maybe 25 ft above the ground, and I'm in southeast michigan with a typical ~30 minute commute into the suburban cities.
I really liked this article but in the end it reinforced my belief in meshtastic - I don't need a computer connected to my node and I'm not paying for any meshcore features. I just wish there were more fixed nodes out there to extend the network.
I'm an electrical engineer with 14 YoE. I'm currently a hardware project lead at ZF group, but will be transferring to Harman this year since our ADAS group was sold to them. I left my former job after a disappointing acquisition (Dana acquiring Pi Innovo), so I'm looking for options in case history repeats itself.
I'd love to get back to faster more agile development teams, but I'm open to anything.
It's a long running process, and the HW is mostly defined (but not laid out) but on pause while I work on porting TockOS to an ATSAMV71 to make sure I won't run into any project ending issues with the SW before I build the hardware.
My node is a solar powered tree hanger hanging maybe 25 ft above the ground, and I'm in southeast michigan with a typical ~30 minute commute into the suburban cities.
I really liked this article but in the end it reinforced my belief in meshtastic - I don't need a computer connected to my node and I'm not paying for any meshcore features. I just wish there were more fixed nodes out there to extend the network.