<div dir="ltr"><span class="gmail-im" style="color:rgb(80,0,80)">On Tue, Sep 6, 2022 at 12:43 AM Dana Myers <<a href="mailto:k6jq@comcast.net" target="_blank">k6jq@comcast.net</a>> wrote:<br>> Has anyone proposed/implemented APRS functionality on LoRaWAN?<br><br></span>I've been thinking of something similar for a student group I've been<br>working with. We're making a system that does both "traditional" APRS<br>and LoRa APRS (and LoRa sensor data) with a raspberry pi pico. The<br>main reason why we're using traditional APRS is because of the<br>excellent existing network infrastructure compared to LoRa, but things<br>like LoRaWAN (e.g., Helium, Things Network, etc.) are challenging<br>that. Of course with the caveats that Helium is encrypted, not<br>licensed amateur radio, and costs fractional pennies per packet (for<br>better or worse).<br><br>First a, a distinction: LoRa is just the physical and link layers (and<br>can be used as licensed amateur radio when operating at higher powers,<br>at least in the US). LoRaWAN is the network layer added on top of the<br>LoRa link layer (it is encrypted and generally thought to be<br>incompatible with licensed amateur radio). Therefore, there are at<br>least two strategies:<br><br>1) You can implement the APRS network as a whole just using LoRa as<br>the physical and network layers (kind of like how HF implements APRS<br>using a different physical layer than VHF APRS). Justin KD8IAY's link<br>is a great example of LoRa implementation of the APRS network (with<br>digipeating and igates). This approach is not LoRaWAN, but is in the<br>spirit of amateur radio in that the network is entirely over-the-air<br>and unencrypted (there's some whitening and proprietary encoding, but<br>it's open to anyone listening):<br><a href="https://github.com/sh123/esp32_loraprs" rel="noreferrer" target="_blank">https://github.com/sh123/esp32_loraprs</a><br>There's also at least one other project for trackers and igates:<br><a href="https://github.com/lora-aprs" rel="noreferrer" target="_blank">https://github.com/lora-aprs</a><br>That can be used for licensed amateur operation when used with higher<br>powers (although, like with APRS, more power doesn't necessarily mean<br>better). These implementations are basically the APRS network, just<br>not using VHF AX.25 (i.e., not using the physical and link layers that<br>VHF APRS uses). However, this isn't exactly what you are asking.<br><br>2) You can use LoRaWAN instead of the APRS network (no digipeating nor<br>explicit igate hardware). This is actually just using APRS at the<br>highest levels (application/presentation) and using completely<br>different physical, link, and network layers. Since LoRaWAN does its<br>own networking (and relies on network servers to be the endpoints of<br>uplinks), I believe you'd need something at a higher level in the<br>stack to act as a broker for the APRS packets. This centralization is<br>a "weakness" of LoRaWAN compared to the APRS networking, but the<br>benefit is that not every packet needs to be relayed constantly - and<br>you can more efficiently send a packet exactly where you want. This<br>might look like an APRS MQTT server or "MQTT Integration" (using<br>Helium terminology) where APRS clients subscribe to their callsign and<br>altnets to receive messages, and then an aprs-is bridge between<br>LoRaWAN/aprs-is would subscribe to all messages and forward them to<br>aprs-is (and take messages from aprs-is and put them on the APRS<br>MQTT). This MQTT server would essentially be something like a "LoRaWAN<br>APRS domain name server" that points packets to their recipients.<br>Maybe there's a way to directly message another device, I just haven't<br>found how yet.<br><br><br>This does bring up another question: if the future of APRS is actually<br>messaging between devices on different networks (e.g., VHF, HF, LoRa,<br>& several LoRaWANs), it's crucial that there is some specification<br>about how all these networks interact (what Steve Dimse K4HG points<br>out). Maybe HF APRS should be able to send a message to a LoRaWAN APRS<br>device, but the exact way LoRaWAN APRS and HF APRS communicate with<br>each other within their own network will be different. That is<br>something I think might be good for the foundation to discuss: what is<br>APRS? Right now it's kind of defined as VHF AX.25 packets with<br>specific data format. Maybe modular specifications would be more<br>appropriate where APRS just defines the interfaces rather than the<br>whole stack, because new innovations will keep coming - the key might<br>be to spend energy that allows all these innovations to be<br>interoperable.<br><br>-Scott KD9PDP<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 6, 2022 at 12:43 AM Dana Myers <<a href="mailto:k6jq@comcast.net">k6jq@comcast.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
I've done some experimenting with a GPS tracker (Dragino LGT-92)<br>
fitted with an external mag-mount antenna. While this operates<br>
in the 902-928MHz band, it falls under Part 15 unlicensed operation.<br>
Transmit power on the LGT-92 is +20dBm (100mW).<br>
<br>
In several test drives, I've found excellent coverage via Helium hotspots.<br>
Yes, Helium costs money ($1 for 100,000 packets) but the infrastructure<br>
is pretty amazing.<br>
<br>
I appreciate the change here from licensed amateur radio operation<br>
to unlicensed operation - but consider this makes it available to all.<br>
With a bit of planning, this easily permits global coverage.<br>
<br>
I also appreciate the LoRa radios are Semtech proprietary IP. They're cheap<br>
enough and widely available.<br>
<br>
LoRaWAN uses AES-128 encryption from edge devices, so there's<br>
little eavesdropping that can be done. Note that encryption is not<br>
an issue for Part 15 operation.<br>
<br>
Has anyone proposed/implemented APRS functionality on LoRaWAN?<br>
<br>
73,<br>
Dana K6JQ<br>
<br>
<br>
<br>
<br>
On 8/7/2022 11:07 AM, Polymath wrote:<br>
> Hopefully folks are checking out the multitude of LoRa trackers already being worked on... so that there is a convergence of implementations instrad of a Tower of Babel...<br>
><br>
><br>
> Sent from my iPhone - my apologies for autocorrection and thumb typing mistakes<br>
><br>
>> On Aug 7, 2022, at 18:00, <a href="mailto:aprssig-request@lists.tapr.org" target="_blank">aprssig-request@lists.tapr.org</a> wrote:<br>
>> <br>
>> From: Jason KG4WSV <<a href="mailto:kg4wsv@gmail.com" target="_blank">kg4wsv@gmail.com</a>><br>
>><br>
>> Are you using LoRa or the full LoRaWAN stack?<br>
>><br>
>> -Jason<br>
> _______________________________________________<br>
> aprssig mailing list<br>
> <a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a><br>
> <a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><b style="font-size:12.8px"><img src="http://onmessage.nd.edu/assets/203921/monogrambanner.png"><br></b></div><div><b style="font-size:12.8px"><br></b></div><div><font face="times new roman, serif"><b style="font-size:12.8px">Scott Howard, PhD</b><br></font></div></div><div><font face="times new roman, serif"><i>Associate Professor</i></font></div><div><font face="times new roman, serif">Department of Electrical Engineering</font></div><div><font face="times new roman, serif">College of Engineering Bioengineering Program<br>University of Notre Dame</font></div><div><a href="http://ee.nd.edu" target="_blank"><font face="times new roman, serif">http://ee.nd.edu</font></a></div><div><font face="times new roman, serif"><br></font></div><div><font face="times new roman, serif"><span style="font-size:12.8px">574-631-2570 (direct)</span><br style="font-size:12.8px">574-631-4393 (fax)</font></div><div><font face="times new roman, serif"><br></font></div><div><div style="font-size:12.8px"><font face="times new roman, serif"><a href="https://howardphotonics.nd.edu" target="_blank">https://howardphotonics.nd.edu</a></font></div><div><font face="times new roman, serif">Follow me on <a href="https://twitter.com/HowardPhotonics" target="_blank">Twitter @HowardPhotonics</a></font></div></div><div><span style="font-size:12.8px"><font face="times new roman, serif"><br></font></span></div><div><font face="times new roman, serif"><span style="font-size:12.8px">262 Fitzpatrick Hall</span><br></font></div><div><font face="times new roman, serif">Notre Dame, IN 46556</font></div><div><br></div><div><img src="http://onmessage.nd.edu/assets/203920/academicmark.png"><br></div></div></div></div></div></div></div></div></div></div></div>