I got in contact with Sulfuroid and he asked me if I could port Meshtastic6 to his LoRa Business Card or if I could write a simple LoRa Messenger for it . Say no more, Buddy!
[…] LoRa Only (with peer-to-peer or broadcast) or LoRaWAN through Gateways (could be super powerful to build a LoRaWAN messaging network all over the world)
Honestly, I am not sure about the Meshtastic port, never digged into the sourcecode before but I already gather some useful knowledge in the area of LoRa and Messaging in combination with LoRaWAN Gateways.
Me and my friends volunteered for a NGO and worked on a GPS Tracking and Emergency project. I can’t go too much into details, but the project was a big success.
So, I re-scheduled my plans and try now to squeeze LoRa projects series in between.
Why writing your own protocol if there is already a commercial adapted protocol like LoRaWAN outside?
I want a self-hosted solution. I want the advantages of LoRaWAN Gateways but I don’t want to rely on cloud based LoRaWAN servers that could get hand on sensible data of my clients. I don’t like the potential restrictions that comes with the LoRaWAN standard.
Writing my own protocol and own server gives me the advantages of both worlds. Receiving LoRa(WAN) packets on 8 channels simultaneously and forwarding them via Semtech UDP protocol7 over network is a big improvement compared to small peer-to-peer devices with limited range and unreliable network connectivity.
In the upcoming #LoRa blog posts, we will take a look at Semtech UDP Protocol and write a server in Python to interact with it.
After the bases are set, we can write the first applications like encrypted LoRa Messenger or monitoring and telemetry.
As Hardware we will use LilyGo TTGO T-Beam, one of my favorite LoRa development boards.
And if everyhing works out, we might get hands on Sulfuroid’s LoRa Business Card.
So stay tuned!