APRS on 144.390: how mic-E, SmartBeaconing, digipeater paths and iGates fit together (and where Direwolf, the D74/D75 and FT5D come in)
- Replies 2
- Views 36
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to lay out how an APRS packet gets from a handheld or mobile to a dot on aprs.fi, and then ask for corrections and additions. The aim is a mental model that helps when something doesn't show up on the map.
Start with the RF layer. In North America APRS runs on 144.390 MHz using 1200 baud AFSK (Bell 202) carrying AX.25 unnumbered information (UI) frames. These are unconnected broadcasts. There is no handshake and no guarantee anyone heard you. Other regions use different frequencies, so check your local APRS frequency before assuming 144.390 applies to you.
A packet has a source callsign with SSID, a destination field, an optional digipeater path, and an information field. The path (for example WIDE1-1,WIDE2-1) tells digipeaters how far they may repeat the packet. Each digipeater that repeats it decrements the hop count, and the packet is dropped when the count reaches zero. The usual advice is to keep paths short. Long paths such as WIDE2-2 or more multiply every transmission across a shared 1200 baud channel, and the channel gets crowded fast.
Mic-E is worth understanding because the Kenwood and Yaesu handhelds use it. It is a compact position format that hides part of the latitude in the destination address field, and the information field carries longitude, speed, course and symbol. It also carries one of a small set of preset status codes (In Service, En Route, Off Duty and so on). That is why a Mic-E packet looks odd in a raw monitor: the destination looks like a random string rather than a callsign or the usual APRS software identifier. It is not corrupt.
SmartBeaconing is a beaconing algorithm, not a packet format. Instead of transmitting every N minutes, the radio adjusts its rate to your behaviour. It beacons often at speed, slowly when stopped or crawling, and sends an extra beacon when you turn by more than a threshold. The tunable parameters are roughly slow speed and slow rate, fast speed and fast rate, minimum turn angle, turn slope and minimum turn time. Poor settings are a common cause of a cluttered trail or a track that cuts corners, so tune them to how you actually drive or walk rather than copying values blindly.
The radios: the Kenwood TH-D74 and TH-D75 have an integrated GPS, APRS, a built-in TNC and a KISS mode, so they can serve as a TNC for a computer. The Yaesu FT5D has GPS and APRS built in as well. All of them transmit at handheld power, usually with a compromise antenna, so being decoded by a digipeater is the limiting factor, not the radio's features. A mobile with an external antenna often gets into the network where a handheld on the belt does not.
On the infrastructure side, an iGate receives RF packets and forwards them to APRS-IS, the Internet backbone. aprs.fi is one of several sites that reads from APRS-IS. If your dot isn't on aprs.fi, the packet may not have been heard by any iGate, or it may have been malformed or filtered. The site's raw packet view is the first place to look.
Direwolf is a popular software TNC and can also act as digipeater and iGate. It decodes audio from a sound interface, speaks KISS and AGW to client programs, and can beacon itself. A minimal iGate config is conceptually just a few lines:
Treat that as a sketch. Check the Direwolf documentation for the exact syntax and current options, and use your own callsign and passcode. Also be conservative about gating from the Internet back to RF. It should be limited, for example to messages addressed to stations recently heard locally, so you don't add unnecessary traffic to the channel.
Finally, the less glamorous packet types. Objects (the ; type) let one station place a named item on the map, such as an event or a hazard, with a nine-character name that can be marked live or killed. Messages go to an addressee padded to nine characters, can carry a message number, and are acknowledged by the receiver; the text is short, around 67 characters. Weather stations send a weather report with position, containing wind direction and speed, gust, temperature in Fahrenheit, rain, humidity and barometric pressure in tenths of millibars. Each of these is a different information-field format on the same shared channel.
What have I got wrong or oversimplified? I'm especially interested in sensible path choices for a fixed station versus a mobile, and in what reasonable SmartBeaconing starting values look like for a car and for walking.
Link to comment
https://www.hamradiobase.com/forums/topic/11601-aprs-on-144390-how-mic-e-smartbeaconing-digipeater-paths-and-igates-fit-together-and-where-direwolf-the-d74d75-and-ft5d-come-in/Share on other sites