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 384.8 km/s
Aurora 1
Updated 13:30 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, iGate behavior, Direwolf, handheld settings and beacon rates

ci_cover.jpg

I'm putting together a checklist for people new to APRS who have a handheld (TH-D74, TH-D75 or FT5D) and may later add a Direwolf station at home. Here is how I understand the pieces. Corrections are welcome.

APRS sends unconnected AX.25 UI frames, normally 1200 baud AFSK, on a shared simplex channel. In North America that is 144.390 MHz. Europe and Africa mostly use 144.800 MHz, and other regions differ, so check your local band plan before programming a memory. Nothing is acknowledged at the RF level for position beacons, so every packet competes for the same channel. That is why beacon rate and digipeater path matter so much.

The roles break down like this. A tracker or handheld with a TNC transmits position, status, messages or weather. A digipeater repeats a packet on RF, using the path field to decide whether to do so. An iGate hears RF and forwards valid packets to the APRS-IS network over the internet. Sites like aprs.fi display what reached APRS-IS. A station showing on aprs.fi tells you someone gated it, not that you were heard directly by the digipeater you expected.

On paths, the usual advice for mobiles is a short one, such as WIDE1-1,WIDE2-1, or just WIDE1-1 where the area has good wide-area digipeater coverage. Long paths such as WIDE2-2 stacked on other hops multiply the same packet across the channel. Old aliases like RELAY or bare WIDE are best avoided. Local practice varies, so find out what digipeaters in your area actually respond to.

On the Direwolf side, the config file covers most of what is needed: ADEVICE for the sound interface, MYCALL with an SSID, MODEM 1200, a PTT method, then IGSERVER and IGLOGIN for the iGate. PBEACON sends fixed-position beacons and TBEACON handles GPS tracking. Receive-only iGating is the safe starting point. Gating internet traffic back to RF should be limited, deliberate and local, and the IGTXLIMIT settings exist for that reason.

Two things I'd like opinions on: how often a fixed station should beacon, and what is the cleanest way to get SmartBeaconing set up on a handheld without flooding the channel.

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For a fixed station, a position beacon every 10 to 30 minutes is plenty. Your location isn't changing, and each packet occupies a shared 1200 baud channel. A weather station can report more often, but ten minutes is a reasonable default. Sending every minute because the software allows it just adds QRM for everyone else.

For SmartBeaconing, the idea is that the beacon rate follows speed and heading. At speed on a straight road you send at a moderate interval. When you slow down or stop, the interval stretches out a lot. When your heading changes by more than a threshold (corner pegging), you send sooner. The parameters are fast speed and rate, slow speed and rate, minimum turn angle, turn slope and minimum time between turn-triggered beacons. The Direwolf documentation gives the exact directive and argument order, so copy from there rather than from memory. Start conservative and widen the rates only if tracks look choppy on aprs.fi.

On reading aprs.fi: the raw packet view is the most useful part. It shows the path, including digipeater callsigns marked with an asterisk and the iGate that injected the packet into APRS-IS. If your packet arrives with qAR or qAO and the iGate's callsign, you can see which station heard you. If only an iGate far away shows up, your local digipeaters may not be hearing you at all.

A common iGate mistake is gating things that should stay off the internet. Packets carrying TCPIP, TCPXX, NOGATE or RFONLY in the path must not be gated to APRS-IS. Direwolf handles this by default, but it is worth knowing if you ever debug duplicates or loops.

  • Moderators

On the handhelds, a few points that are easy to miss. The TH-D74 and TH-D75 have a built-in TNC and GPS, and both can be used as a KISS TNC for other software. The FT5D also has APRS with GPS built in. Menu structure and defaults differ between these radios, so check each manual for the packet speed, the beacon path (digipeater path) field, and whether the radio is using standard position format or Mic-E.

Mic-E is worth understanding. Instead of the longer plain-text position format, it puts latitude in the destination address field and packs longitude, speed and course into the information field. The result is a shorter packet, which suits mobile use. It also carries a standard status code (In Service, En Route, Off Duty, Emergency and so on) that you choose on the radio. Many decoders show that status next to the track.

For messaging, the format is the : data type, followed by the addressee padded to nine characters, then the text, with an optional message number after a {. Text is limited to 67 characters. The receiving station sends an ack with the same number, and the sender retries until it gets one or gives up. If you send messages to a callsign-SSID, the SSID must match exactly. Messaging to someone far away works through APRS-IS only if they were recently heard on RF at an iGate, so delivery is not guaranteed.

Objects use the ; type with a nine-character name and a live (*) or killed (_) flag. They are handy for marking an event, a repeater or a checkpoint, but they repeat on whatever schedule you set. Put a realistic interval on them and kill the object when you are done, otherwise it lingers on the map.

Test with a short path and low power first, and use a callsign-SSID scheme you will remember, such as one SSID for the handheld, another for the car and another for the home iGate.

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.