ⓘ Callsign lookups are in real time via the FCC database.
Vanity callsign availability is refreshed daily at 6:00 AM CST.
The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
APRS on 144.390: sorting out trackers, digipeater paths, Direwolf iGates and beacon rates
APRS looks simple (a radio sends a position, a map shows it), but a lot of the trouble people run into comes from the layers in between. This thread is for comparing notes on a few of those layers so beginners and returning operators can see how the pieces fit together.
The basics. In North America, APRS runs on 144.390 MHz using 1200 baud AFSK, carried in AX.25 unnumbered information (UI) frames. Other regions use different frequencies, for example 144.800 MHz across much of Europe and Africa and 145.175 MHz in Australia, so check your local band plan before programming a handheld. Everything shares one simplex channel, which makes beacon discipline matter much more than it first appears.
Handhelds and mobile trackers. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in GPS and APRS functions. The common setup mistakes are mostly the same across them:
The APRS frequency, or the band the radio treats as the APRS band, is not set to the local APRS frequency.
The data speed is set to 9600 when the local network is 1200.
The digipeater path is left at something unsuitable for the area.
The beacon is set to transmit on a fixed short interval instead of using SmartBeaconing.
Mic-E is the compact position format most of these radios use for tracking. It packs latitude into the destination address field and puts longitude, speed and course into the information field. That is why a Mic-E packet looks like gibberish in a raw packet monitor, while aprs.fi and most client software decode it without trouble.
Paths. A typical mobile path is WIDE1-1,WIDE2-1. The first hop lets a nearby fill-in digipeater pick you up, and the second hop gets you to a wide-area digipeater. Long paths like WIDE7-7 on a shared channel multiply your traffic across a whole region, which is why most local coordinators discourage them. What counts as a good path depends on how your area's digipeaters are configured, so ask your local APRS group.
SmartBeaconing varies the beacon rate with speed and turns. You set a fast speed and fast rate, a slow speed and slow rate, plus a minimum turn time, turn angle and turn slope. At a standstill you beacon rarely, and on a highway you beacon at a moderate interval. Corner pegging adds extra beacons when your heading changes, so the track follows the road.
Direwolf as a software TNC and iGate. Direwolf can decode from a sound card, act as a KISS or AGW TNC, digipeat, beacon, and gate packets to APRS-IS. A minimal receive-only iGate configuration looks something like this (callsign and passcode are placeholders):
The audio device name will differ on your system. Direwolf's log prints the received audio level, which is a quick way to see whether your receive audio is badly over- or under-driven.
Questions to get things started:
For a handheld used on foot and in a car, what SmartBeaconing numbers have you found sensible? Walking and driving want very different settings.
Is it better to run a receive-only iGate first, and when does enabling RF-side gating make sense?
For weather stations, objects and messages, what are the common formatting mistakes that make data show up wrong on aprs.fi?
APRS looks simple (a radio sends a position, a map shows it), but a lot of the trouble people run into comes from the layers in between. This thread is for comparing notes on a few of those layers so beginners and returning operators can see how the pieces fit together.
The basics. In North America, APRS runs on 144.390 MHz using 1200 baud AFSK, carried in AX.25 unnumbered information (UI) frames. Other regions use different frequencies, for example 144.800 MHz across much of Europe and Africa and 145.175 MHz in Australia, so check your local band plan before programming a handheld. Everything shares one simplex channel, which makes beacon discipline matter much more than it first appears.
Handhelds and mobile trackers. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in GPS and APRS functions. The common setup mistakes are mostly the same across them:
Mic-E is the compact position format most of these radios use for tracking. It packs latitude into the destination address field and puts longitude, speed and course into the information field. That is why a Mic-E packet looks like gibberish in a raw packet monitor, while aprs.fi and most client software decode it without trouble.
Paths. A typical mobile path is WIDE1-1,WIDE2-1. The first hop lets a nearby fill-in digipeater pick you up, and the second hop gets you to a wide-area digipeater. Long paths like WIDE7-7 on a shared channel multiply your traffic across a whole region, which is why most local coordinators discourage them. What counts as a good path depends on how your area's digipeaters are configured, so ask your local APRS group.
SmartBeaconing varies the beacon rate with speed and turns. You set a fast speed and fast rate, a slow speed and slow rate, plus a minimum turn time, turn angle and turn slope. At a standstill you beacon rarely, and on a highway you beacon at a moderate interval. Corner pegging adds extra beacons when your heading changes, so the track follows the road.
Direwolf as a software TNC and iGate. Direwolf can decode from a sound card, act as a KISS or AGW TNC, digipeat, beacon, and gate packets to APRS-IS. A minimal receive-only iGate configuration looks something like this (callsign and passcode are placeholders):
The audio device name will differ on your system. Direwolf's log prints the received audio level, which is a quick way to see whether your receive audio is badly over- or under-driven.
Questions to get things started:
Link to comment
https://www.hamradiobase.com/forums/topic/11769-aprs-on-144390-sorting-out-trackers-digipeater-paths-direwolf-igates-and-beacon-rates/Share on other sites