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

Direwolf iGate plus fill-in digi for a mixed HT fleet (TH-D74/D75, FT5D): paths, Mic-E, SmartBeaconing and messaging

ci_cover.jpg

I'm planning an APRS node on 144.390 MHz (North America) built around Direwolf and a sound-card interface. It would run as an iGate, and maybe as a fill-in digipeater if the coverage gap justifies it. The users would carry a mix of Kenwood TH-D74 and TH-D75 radios and a Yaesu FT5D. I'd like to compare notes on the details that cause trouble in practice, so here is my current understanding. Please correct anything wrong.

Channel basics. APRS on VHF is 1200 baud AFSK carrying AX.25 UI frames. Nothing is acknowledged at the link layer, so every packet competes for the same shared channel. Other regions use different frequencies, for example 144.800 MHz in Europe and 145.175 MHz in Australia, so check the local band plan before configuring a radio.

Direwolf skeleton. This is a sketch of the iGate side only. Substitute your own callsign, audio device, PTT method and the passcode generated for your callsign.

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

IGSERVER noam.aprs2.net
IGLOGIN N0CALL-10 12345

PBEACON delay=1 every=30 overlay=R symbol="igate" lat=DD^MM.MMN long=DDD^MM.MMW comment="RX iGate"

Direwolf also has a DIGIPEAT directive that takes alias and wide patterns. I'd read the User Guide section on it before enabling it, because a badly written pattern can make the node repeat things it shouldn't.

Handheld settings I'm trying to standardize:

  • Position format: Mic-E is compact. Course, speed and a status code (En Route, In Service, Emergency and so on) are packed into the destination address and the information field. It costs less airtime than a plain-text position report with a comment.
  • Beaconing: use SmartBeaconing, not a fixed interval, for anything that moves. It beacons more often at speed and when heading changes, and less often when slow or stopped. The usual parameters are low speed, high speed, slow rate, fast rate, turn slope, turn angle and turn time.
  • Path: WIDE1-1,WIDE2-1 is the common default for mobiles and handhelds. I'm wary of longer paths in a dense area.
  • SSIDs: a consistent scheme such as -7 for handhelds and -9 for vehicles makes aprs.fi much easier to read.

Open questions: how should the beacon path be set for a station that is already well covered by a wide-area digipeater? And what is the best way to confirm that an iGate really passes messages to RF, and not just position data to the Internet?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the path question: if a wide-area digi already hears you well, there is little reason to ask for WIDE1-1,WIDE2-1 from a fixed station. A single WIDE2-1, or no digipeater path at all if an iGate hears you directly, costs the channel much less. The two-hop default mostly helps a mobile that moves between coverage zones. For a home station it just adds duplicate transmissions.

On messaging, remember that iGating to RF is not symmetrical. Position reports normally flow from RF to the Internet. In the other direction, most iGates transmit only messages addressed to a station they have recently heard on RF. They usually do not gate arbitrary Internet traffic. So a handheld that is out of your iGate's range will not receive Internet-originated messages through it, even if aprs.fi shows the handheld as active.

A practical test is to send a message from the Internet side, for example through an aprs.fi-linked client, to a handheld that has just beaconed through your node. Then watch the Direwolf log for the transmitted :ADDRESSEE:text{id packet and for the ack coming back. If the message was transmitted but nothing came back, the cause is likely radio-side, such as a retry timer or the radio receiving on the wrong band.

Format reminders: the addressee field is padded to 9 characters, the message text is limited to 67 characters, and the message number follows {. Any gateway or script that builds raw frames has to get those right.

  • Moderators

Some notes on the handhelds. All three radios can transmit Mic-E, but menu names and defaults differ by model and firmware. Don't trust that they match. Compare the actual on-air packets in Direwolf's log or on the aprs.fi raw packets page. The settings worth checking on each radio are the APRS band, the packet frequency, the beacon type, the comment and status text, and the SmartBeaconing parameters. A radio left on a voice frequency, or with APRS assigned to the wrong band, is a common reason a station never appears on the map.

The D74 and D75 can also act as a KISS TNC over USB or Bluetooth, according to their manuals. That is useful for pairing with a phone or laptop, but it is a separate mode from using the internal APRS function. Check the manual for which settings apply to which.

For SmartBeaconing, start from conservative values and adjust based on what the aprs.fi track looks like. Corner pegging that fires too often on winding roads will generate many packets. Slow rates that are too long leave straight-line gaps in the track. Remember that at 1200 baud one position packet occupies roughly a second or more of airtime, and every station in range has to share that.

For checking the iGate path, the raw packet view on aprs.fi is more useful than the map. In the path you can see the Q-construct and the iGate callsign that injected the packet. A qAR entry followed by your iGate's callsign means the packet came from RF through that station. If your own beacon never shows up with your callsign in the path, the problem is either the RF receive chain or the APRS-IS login.

If you later add a weather station or objects, give each its own SSID or object name and a slow beacon rate. Weather data is sent as an APRS weather report with fields such as wind direction and speed (c/s), gust (g), temperature in degrees F (t), rain (r, p, P), humidity (h) and pressure (b). Objects use the ; data type with a 9-character name padded with spaces, and * marks the object live while _ kills it. Treat objects as something you retransmit sparingly, and kill them when the event is over.

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.