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

Setting up APRS properly on 144.390: Direwolf iGate, handheld trackers, Mic-E, SmartBeaconing and what to put on the channel

ci_cover.jpg

I want to collect the practical parts of APRS in one thread, because the same questions keep coming up: why a position doesn't show on aprs.fi, why messages don't get acknowledged, and why the local channel is full of packets nobody can use. Please correct anything below that doesn't match how your region runs it.

The basics. APRS is unconnected AX.25 (UI frames) at 1200 baud AFSK, Bell 202 tones, on FM. In North America the shared frequency is 144.390 MHz. Other regions use different frequencies, for example 144.800 MHz across much of Europe and Africa, with others elsewhere, so check your local band plan before you transmit. Every station shares one simplex channel. That channel has very little capacity, so most of the etiquette is about not wasting airtime.

The chain. A tracker sends a packet. A digipeater may repeat it, based on the path in the header. An iGate that hears it on RF can forward it to APRS-IS over the internet, and sites like aprs.fi show what APRS-IS received. If your position isn't on the map, either no iGate heard you, or an iGate heard you but dropped the packet, for example because it was a duplicate or the path was unsuitable. Aprs.fi shows what the network heard, not what your radio sent, so the raw packet view is the first place to look when debugging.

Paths. A common mobile path is WIDE1-1,WIDE2-1. WIDE1-1 lets a fill-in digi pick the packet up first, and WIDE2-1 lets a wide-area digi carry it further. Many areas discourage long paths such as WIDE2-2 or higher, or cap them. A fixed home station usually needs a short path such as WIDE1-1, or no digipeating at all if an iGate hears it directly. Ask your local APRS group what the region recommends before you copy a path from a forum post.

Direwolf. Direwolf is a software TNC and can act as a digipeater, an iGate, a beacon source and a KISS or AGWPE server for other software. A minimal iGate configuration looks roughly like this, with placeholders you'll need to replace:

ADEVICE plughw:1,0
CHANNEL 0
MYCALL N0CALL-10
MODEM 1200
PTT GPIO 25
IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345
PBEACON delay=1 every=30 symbol="igate" overlay=R lat=42^37.14N long=071^20.83W comment="RF iGate" via=WIDE1-1

Check the Direwolf documentation for your platform's audio device names and PTT options. The passcode comes from your own callsign, so don't paste someone else's. Set audio levels carefully. If Direwolf's receive level is clipped or very low, you will decode fewer packets, and a transmit level that over-deviates will splatter and sound bad to every other decoder on the channel.

For discussion: what are people using for the RF side of a home iGate? A dedicated radio, an RTL-SDR in receive-only mode, or a TNC on a separate box?

Handhelds. The Kenwood TH-D74 and TH-D75 and the Yaesu FT5D all have built-in APRS and GPS, so they can send beacons and handle messages without an external TNC. Menu names and defaults differ between models and firmware versions, so use the manual for yours. The points that matter on any of them are the same: set your callsign and SSID correctly, choose a sensible path, pick a beacon interval that matches how you move, and don't leave a fixed handheld beaconing every minute.

Mic-E and SmartBeaconing. Mic-E is a compact position format used by many radios and trackers. Latitude is encoded in the AX.25 destination address, and the info field carries longitude, speed, course and the symbol. That is why a raw Mic-E packet shows an odd-looking destination callsign and an unreadable info field. Mic-E also carries a status code (In Service, En Route, Emergency and so on). SmartBeaconing varies the beacon rate with speed and course changes. You set a slow speed and slow rate, a fast speed and fast rate, a minimum turn time, a turn angle and a turn slope, and the radio beacons more often while turning or moving fast and rarely while parked. Treat any default numbers as starting points and tune them for your own driving and area.

  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

A few notes on the iGate side that save time. Start with the IGSERVER and login: if the passcode is wrong, Direwolf will connect but APRS-IS will treat you as receive-only, so your packets get no gating. Check the Direwolf output for the login result.

On RF-to-internet traffic, it is normal for a well-run iGate to gate only packets it heard directly, or after a limited number of hops, and it should not forward packets that already came from the internet. Internet-to-RF gating is typically limited to messages, and only for stations heard locally on RF within a recent time window. If you enable it on a busy channel, keep it tight. It is easy to create loops or flood a shared frequency with traffic nobody needs.

For the beacon, give the iGate an accurate position, a clear symbol and a short comment, and beacon rarely. Every 30 minutes is plenty for a fixed station. Longer comments mean longer packets and more collisions on 1200 baud. On the radio side, if you have a choice, use the data or discriminator audio connection rather than the speaker output. Speaker audio is shaped for voice and may lose volume or add distortion at the tones. If you run an RTL-SDR instead, the same Direwolf decoder applies, but you will not be able to transmit digipeated or beaconed packets without a separate transmitter.

  • Moderators

Adding to the handheld and content side. If your message doesn't get acknowledged, check three things: the addressee, the message number and the path. Messages use the format :ADDRESSEE:text{msgno, with the addressee padded to nine characters. The receiver should reply with an ack carrying the same number, and the sender retries until it sees one. If the recipient is only reachable through an iGate, remember that the internet-to-RF gate only works if that iGate heard the recipient recently on RF.

Objects and weather are useful but easy to overdo. An object has a nine-character name and is marked live or killed. A repeater, an event or a storm cell can be sent as an object by someone other than the thing's location. Send it at a sensible interval and kill it when it's no longer valid, otherwise it hangs around on maps. A weather station sends a position packet with the weather symbol and then wind direction, speed, gust, temperature, rain and humidity in a fixed format. In most cases, once every ten minutes or less often is enough.

For SmartBeaconing on a mobile, keep the slow rate really slow when you stop. Many unneeded packets come from a parked vehicle beaconing as if it were moving. On handhelds in particular, expect the GPS fix and your antenna to limit things more than the settings. A rubber-duck antenna inside a vehicle is a weak signal to a digipeater. An external antenna and a decent path matter more than tuning the beacon parameters any further.

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.