Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 412.9 km/s
Aurora 1
Updated 14:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ 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 — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

APRS on 144.390: sorting out paths, iGates, Mic-E and SmartBeaconing across a handheld, Direwolf and aprs.fi

ci_cover.jpg

This is a technical thread on how the pieces of APRS fit together, since the same questions come up repeatedly. A station beacons a position or message as an AX.25 UI frame at 1200 baud AFSK on 144.390 MHz (North America). A digipeater may repeat it, and an iGate may pass it into APRS-IS, the internet backbone. Sites like aprs.fi are a window onto the APRS-IS data stream. They are not the radio network itself.

Start with the frequency. 144.390 MHz is the North American APRS channel. Other regions use other frequencies, for example 144.800 MHz in Europe and Africa. Check your local band plan and set the radio before travelling, otherwise the radio will beacon into the void and never hear local traffic.

On the radio side, the Kenwood TH-D74 and TH-D75 have a built-in TNC and GPS, so they can beacon with no extra hardware. They also offer a KISS mode, so the radio can act as a TNC for software on a phone or PC. The Yaesu FT5D also has integrated GPS and APRS. Details such as supported baud rates, path presets and beacon options vary by model and firmware, so check the current manual rather than relying on what someone remembers.

The beacon path decides how far a packet travels and how much channel it burns. A common mobile setting is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi pick up a low-power handheld, and WIDE2-1 allows one more hop through a wide-area digi. Long paths such as WIDE1-1,WIDE2-2 or larger multi-hop paths flood a shared 1200 baud channel quickly. Fixed stations that are already well heard should usually use a shorter path, or none.

Mic-E is the position format most Kenwood and Yaesu radios use for mobile tracking. It packs latitude into the destination address field and puts longitude, speed and course in the information field. This makes packets short, which matters on a slow channel. It also means that if your decoder shows odd destination calls like "T5SQPX", that is normal and not corruption.

The questions for discussion:

1. For a mobile tracker, what SmartBeaconing settings (fast/slow speed, fast/slow rate, minimum turn time, turn angle, turn slope) give a clean track without hammering the channel?

2. For a Direwolf station used as a digipeater and iGate, what is the sanest way to avoid gating loops and duplicates?

3. When your beacon shows up on aprs.fi but nobody can message you, where do you look first?

Weather stations, objects and bulletins can follow later in the thread.

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On SmartBeaconing, the logic is easier to tune once you see what each parameter does. The beacon rate scales between a slow rate when you are below the slow speed and a fast rate when you are above the fast speed. In between it interpolates. Separately, corner pegging sends an extra beacon when your heading changes by more than a threshold that depends on speed, with a minimum time between turn-triggered beacons so you don't spam during a roundabout or a winding road.

The usual mistake is a fast rate that is too fast. Beaconing every 60 seconds on a highway gives a decent breadcrumb trail. Going much shorter mostly adds collisions on 144.390 without making the map noticeably better. Also set the slow rate to something long, like 20 to 30 minutes, so a parked vehicle is not chattering away all day.

The other thing to check is the path, not just the timing. If the handheld sends WIDE1-1,WIDE2-1 and you are already in range of a wide-area digi, the extra hop only adds duplicate traffic. Many people use the same path everywhere and that is fine for a mobile, but be conservative at home. For a fixed station with decent coverage, a single WIDE2-1, or nothing, is usually plenty.

On the TH-D74/D75 and the FT5D, use the radio's own SmartBeaconing menu. The names and ranges differ between brands, so copy the logic, not just the numbers. One caution: a radio in the car with the GPS on a dashboard may report poor course and speed at low speeds. If you see the position jittering while stopped, a longer slow rate and a higher slow-speed threshold help.

  • Moderators

For Direwolf as a digipeater plus iGate, keep the roles separate in your head. Digipeating is an RF-to-RF function, while iGating moves traffic between RF and APRS-IS. In the config you set the audio device, the channel, MYCALL and the modem speed. Then you add DIGIPEAT rules for what you will repeat, and IGSERVER, IGLOGIN and the filter or transmit settings for the iGate side. Check the Direwolf user guide for the current syntax, because those directives have options that are easy to get subtly wrong.

Loop avoidance is mostly about not gating things that already came from the internet. Packets with TCPIP, TCPXX, NOGATE or RFONLY in the path should not be sent to APRS-IS, and the same applies in reverse. IS-to-RF traffic should be limited to messages for stations you have actually heard on RF recently. Gating everything from the internet onto 144.390 is how a local frequency gets clogged. If you transmit anything from the iGate, keep it minimal.

Audio level matters more than people expect. Direwolf prints an audio level at decode time. If it is far out of range, either clipping or very weak, the decode rate suffers. Fix that before blaming the antenna. If you have a hardware TNC or a radio's KISS mode, Direwolf can talk to it over KISS, but the sound-card path is usually the simplest to start with.

On the third question, when you appear on aprs.fi but can't receive messages, remember what a message is. It is an addressed packet of the form :ADDRESSEE:text{id, with the addressee padded to nine characters, and the sender expects an ack. To reach you via the internet, an iGate near you must have heard you on RF recently, and your radio's callsign-SSID must match exactly. Check the raw packets page on aprs.fi for your call and see whether the beacon arrived via an iGate or only as a direct RF hit. Also confirm that your radio is set to receive messages and is not stuck on a different SSID.

For weather and objects: a weather packet uses the underscore symbol with fields such as wind direction, speed and gust, temperature in degrees Fahrenheit, rain, humidity and barometric pressure. Objects are a different thing. They represent something other than the sending station, such as an event, a net location or a storm, and they use a name field fixed at nine characters. They need to be refreshed periodically by the originator, and a killed object is marked with an underscore in place of the asterisk. If you plan to send objects, keep the interval sensible, since every refresh is airtime for everyone else.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.