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

Getting a handheld tracker, a Direwolf iGate and aprs.fi to agree on 144.390

ci_cover.jpg

A common first APRS setup has three parts: a handheld or mobile beaconing on 144.390 MHz (the North American frequency; Europe uses 144.800), a Raspberry Pi or PC running Direwolf as an RX iGate, and aprs.fi to confirm that packets are reaching the internet. When it works, the track appears on the map. When it doesn't, the cause is usually one of a few things, and this thread is for sorting those out.

Quick recap of the chain. A tracker such as a Kenwood TH-D74/TH-D75 or a Yaesu FT5D sends an AX.25 UI frame at 1200 baud AFSK. A digipeater may repeat it, depending on the path. An iGate that hears it on RF forwards it to APRS-IS, and aprs.fi reads it from there. A missing station could mean a failure at any hop: bad RF, a path nobody answers, an iGate that isn't logging in, or a beacon that isn't being sent at all.

Here is a minimal Direwolf config for a receive-only iGate. The callsign, passcode, audio device and coordinates are placeholders. Check the server name against the current APRS-IS rotate for your region.

ADEVICE plughw:1,0
ACHANNELS 1
CHANNEL 0
MYCALL N0CALL-10
MODEM 1200

IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345

PBEACON sendto=IG delay=1 every=30 symbol="igate" lat=42^37.14N long=071^20.83W comment="RX iGate"

The sendto=IG option sends the iGate's own position straight to APRS-IS instead of over RF, which is the usual choice for an RX-only station. Without a transmit configuration the station only listens, which suits a first test.

Questions to start with: what do you check first when a beacon doesn't show on aprs.fi? And how do you decide between WIDE1-1,WIDE2-1 and a shorter path once you know what the local digipeaters are doing?

  • Replies 2
  • Views 54
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start by separating RF problems from internet problems. In Direwolf's console output, check whether the tracker's packets are decoded at all. If they are, the RF side is fine and the question becomes whether the iGate is logged in. Look for a successful APRS-IS connection message. A wrong passcode is a classic cause. Direwolf can connect and sit there, but the server won't accept the packets.

If the packet is decoded and the login is good, look at the raw packet on aprs.fi. The path shows the q-construct that was added at the server. Something like qAR followed by your iGate callsign means a gateway heard it directly on RF. qAO marks a receive-only iGate. Digipeaters in the path are marked with an asterisk once they've repeated the frame. That lets you see whether a packet reached you directly or through a digipeater.

On audio level: Direwolf prints an audio level figure for each decoded frame, and a decode that is clipped or very low is more fragile than it looks. Set the sound card input so typical packets sit comfortably mid-range. Also keep in mind that the shared channel is mostly a collision game. A weak iGate that hears every second packet won't give you a clean track no matter how good the config is.

On IS-to-RF: leave it off until the RX side is solid. Gating internet traffic to RF should mostly be limited to messages for stations the iGate has recently heard locally. It is not a way to rebroadcast position data to the channel, and Direwolf's gating rules are written with that in mind. A full iGate also needs to be configured carefully so it doesn't create duplicate traffic.

  • Moderators

On the tracker side, what the radio sends depends heavily on its beacon settings, and the defaults are often not ideal. Both the TH-D74/D75 and the FT5D can get position from their internal GPS and beacon it, and they typically encode it as Mic-E. Mic-E is a compact format that puts the latitude in the destination address field and the longitude, speed and course in the information field. That keeps the packet short, which matters on a 1200 baud shared channel. It also carries a status code such as In Service or Emergency. Some aprs.fi pages and decoders show the raw destination as odd characters, and that is normal. Check each radio's manual for exact menu names, because they vary by model and firmware.

For beacon timing, a fixed interval is wasteful. Sending every 30 seconds while parked fills the channel with identical positions, and sending every 10 minutes at highway speed gives a track that cuts corners. SmartBeaconing addresses both. Its parameters are typically a fast speed with a short rate, a slow speed with a long rate, and a turn-detection group: minimum turn angle, minimum time between turn beacons, and a turn slope that scales the threshold with speed. It beacons often when moving fast, rarely when slow or stopped, and extra when the heading changes. Start with the radio's defaults and adjust from the observed track. If the track is jagged at low speed, the turn settings are usually the place to look.

For path, WIDE1-1,WIDE2-1 is the usual mobile setting, because it works with fill-in digipeaters and wide-area ones. Long paths like WIDE2-2 or higher are best avoided unless the area really needs them. Each extra hop multiplies the traffic on the channel.

Two extras once the basics work. First, objects: an object has a 9-character name and can be marked live or killed, so a station can place things like an event or a net location on the map. Because it is retransmitted on a timer, a long period is better than a short one. Second, messaging: addressees are padded to 9 characters, the text is limited to 67 characters, and a message number lets the receiver acknowledge it. If the message goes via an iGate, the recipient generally has to have been heard on RF recently. That is why a message to a station that only ever beacons from the internet may not reach a radio.

For a weather station, use a proper weather report, with wind, temperature, rain, humidity and pressure in the APRS fields, not a plain text comment. Keep the interval modest. A weather update every 10 minutes or so is generally plenty for a conditions display.

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.