Differences

This shows you the differences between two versions of the page.

--- packet:lora_vhf_aprs_gateway [2025/03/30 15:46] – [Beacons] 2e0hkd
+++ packet:lora_vhf_aprs_gateway [2025/03/30 15:52] (current) – 2e0hkd
@@ Line 1: / Line 1: @@
-====== VHF-LoRa APRS Gateway ======
+====== VHF-LoRa APRS Gateway Experiment by 2E0HKD ======
-**Work-in-Progress by 2E0HKD**
 LoRa based APRS has taken off, but still remains largely separate from classic 2m FM APRS other than both being ingested into APRS-IS. As LoRa was fairly quiet in my area, I wanted to try and make a cross-band gateway where LoRa and VHF APRS could interact, giving more local info to LoRa users and allowing messaging between the two.
@@ Line 111: / Line 109: @@
 Also included in this example is a similar process for placing an object for my packet node GB7BSK, and the same object pseudo-digi'd on the other band, solving the competing objects issue again.
+===== Results =====
+I only ran the gateway for a few weeks until my 2m port was needed for other packet duties. During that time it seemed to perform well, and didn't hog either frequency too much. I had seem warnings about avoiding digipeating loops between the bands, but from my testing it seemed to properly identify when a packet had already been digipeated (even cross band) and behaved well. (This is one reason to use Digimap and not BRIDGE if you were to do this kind of thing in BPQ, because you want digipeated packets with their modified paths, and not just blindly copied, unmodified packets). Obviously if you have more activity in your area you'll want to keep an eye on things to make sure it doesn't generate too much traffic.
 ===== References =====
 [[https://thelifeofkenneth.com/aprx/aprx-manual.pdf|APRX documentation]]