LoRa-APRS Tracker APRS Setup: Settings, Path & Live Users

Open-source LoRa-based APRS trackers and iGates built on ESP32 hardware. Uses 433 MHz LoRa modulation instead of 1200 baud AFSK, so it needs LoRa-aware iGates in range. Now one of the fastest-growing segments of the APRS network. Tracker tier.

6888 station(s) heard beaconing with a LoRa-APRS Tracker on the APRS-IS network in the last 7 days.

Live LoRa-APRS Tracker stations

How to set up APRS on the LoRa-APRS Tracker

LoRa APRS is a separate radio network that happens to carry APRS packets. A LoRa tracker cannot be heard by a normal 1200 bps digipeater and vice versa, so the one setting that decides whether it works at all is the frequency profile your local LoRa iGates use.

  1. Flash the firmware
    The common ESP32 LoRa boards are supported by community firmware with a browser-based flasher, so no toolchain is needed for a first install. Choose the tracker firmware for a mobile beacon, the iGate firmware for a fixed receiver that forwards to the internet.
  2. Open the configuration interface
    On first boot the board raises its own WiFi access point, LoRaTracker-AP, with the password 1234567890. Connect to it and open 192.168.4.1 in a Chromium-based browser. The board reboots into normal mode if nothing connects within about two minutes.
  3. Replace NOCALL-7 with your callsign
    The firmware ships with three beacon profiles, all set to NOCALL-7 with different symbols and SmartBeacon settings: a walking profile, a bicycle profile and a vehicle profile. Change the callsign on every profile you intend to use. Beacons still labelled NOCALL are visibly untouched configuration and will be ignored by everyone.
  4. Choose the right frequency profile
    This is the setting that decides whether you exist. 433.775 MHz with spreading factor 12 and coding rate 5 is used across Europe and most of the world. Poland uses 434.855 MHz with spreading factor 9 and coding rate 7. The UK uses 439.9125 MHz with spreading factor 12 and coding rate 5. Bandwidth is 125 kHz on all of them. A tracker on the wrong profile is invisible to an iGate a hundred metres away.
  5. Set path, comment and beacon rate
    The default path is WIDE1-1 and is fine. Keep the comment short or empty. A LoRa packet at spreading factor 12 occupies the channel for a long time, and the firmware can be told to append the comment only every tenth beacon for exactly that reason. With SmartBeacon off, the fixed rate defaults to 15 minutes.
  6. Save, reboot and check the map
    Save from the web interface; the board reboots and starts beaconing. Search for your callsign here; if it appears, a LoRa iGate heard you and forwarded the packet to APRS-IS.

Recommended APRS settings

SettingValueNotes
Frequency (EU and most of the world)433.775 MHz, SF12, CR5, BW 125 kHz—
Frequency (Poland)434.855 MHz, SF9, CR7, BW 125 kHz—
Frequency (United Kingdom)439.9125 MHz, SF12, CR5, BW 125 kHz—
CallsignYOURCALL-7replace NOCALL-7 on every beacon profile
PathWIDE1-1the firmware default
Beacon rateSmartBeacon on, or 15 minutes fixed—
Commentshort or emptySF12 packets are slow; long comments hurt
TX power20firmware default, in dBm

Troubleshooting

The tracker transmits but never appears on the map

Two causes, and the first is far more common: the frequency profile does not match your local network, or there is no LoRa iGate in range. LoRa APRS runs on its own frequencies and modulation, so ordinary 144 MHz APRS digipeaters cannot hear it however close they are. Find out which profile your region uses before assuming a hardware fault.

It still shows as NOCALL-7

The configuration was not saved, or the filesystem image was re-uploaded afterwards and overwrote it. Re-enter the callsign on every beacon profile, save from the web interface, and confirm the board rebooted.

Can I put my LoRa tracker on 144.800 MHz?

No. LoRa and 1200 bps AFSK are different modulations on different bands. A LoRa tracker only reaches the APRS network through a LoRa iGate, which is a separate piece of hardware from a conventional iGate.

Why is the beacon interval so long?

A spreading factor 12 packet takes a long time on air, and everyone in range shares one channel. Long intervals and short comments are what keep a LoRa APRS network usable as the number of trackers grows.

Which SSID should I use?

It is a convention, not a rule, and nothing rejects a packet for using the "wrong" one: -7 for a handheld, -9 for a vehicle, -10 for an internet gateway, and no SSID at all for a home station. Using the conventional one just means other operators can read your intent at a glance.

Source: github.com · github.com

Related guides

All APRS hardware · Live APRS map