From 2020, this post asked about a generic gateway, but the response was that the codebase was getting there in 3+ months. Paul Mandal has a tool called ATAK Forwarder, which might be a great place to display GPS locations of meshtastic nodes. But if not, I would still need to write an app on a PC, requiring a gateway. I also understand that meshtastic is ideal for ‘stand-alone’ networks with no gateways, but it is the mesh aspect of extending LoRa that is essential to my tiny project.
I am just curious which hardware would be appropriate for a gateway that allowed node data to be exposed outside the mesh(es).
-There are a number of nodes deployed temporarily, and in a small-ish group, distance-wise. Less than 1KM in diameter.
-Each node will transmit it’s GPS coords, and a few integers every minute or 2.
-The destination for each transmission is the/a gateway, and not another node. To put it simply, all nodes communicate field data between themselves and a device on the other side of the gateway.
-The only reason one node would communicate with another is to utilize/maintain the mesh. Data from one node’s sensors is of no interest to another node.
-Ultimately, the GPS position information will be presented on a laptop, cell phone, etc., none of which are gateways themselves, and they do no LORA communication at all. An app out there (ATAK, …) or one I write will display data.
-Down the road, sending data from beyond the gateway will be useful, but t doesn’t seem that I need any special considerations-i.e. all components used in 1-way and mesh negotiation can accomplish this OOTB.
I have collected lots of LoRa chips over the years, but until I found meshtastic it seemed I had to write my own mesh layer on top of LoRa. You can imagine how excited I am at the prospect of not re-inventing something!
Can any of you share your own practical/theoretical experiences with using gateways like this?
Your insights deeply appreciated, as I have my hot little credit card in hand!