APRS on 144.390: tuning a tracker, a Direwolf iGate and a handheld so they don't clog the channel
- Replies 2
- Views 117
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chad 1 post
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 compare notes on how people set up the pieces of an APRS system so they work together instead of fighting over one 1200 baud channel. In North America the shared frequency is 144.390 MHz, using AFSK (Bell 202 tones) carrying AX.25 UI frames. Other regions use different frequencies, such as 144.800 in much of Europe and 145.175 in Australia, so confirm your local APRS frequency before transmitting.
The pieces I'm interested in:
1. Handheld and mobile trackers. The Kenwood TH-D74 and TH-D75 have a built-in GPS and TNC, and the Yaesu FT5D has built-in GPS and APRS. Both families send position beacons with no external hardware. Most radios of this type default to Mic-E encoding for position. Mic-E packs latitude into the destination address field and puts longitude, speed and course in the information field. That makes packets shorter than plain-text position reports, which matters when every packet takes airtime on a shared channel.
2. Beacon timing. A fixed beacon every 3 minutes from a moving car is wasteful when you're stopped at a light and too slow when you're turning through switchbacks. SmartBeaconing varies the rate with speed and adds extra beacons when your heading changes. The parameters are fast speed and fast rate, slow speed and slow rate, minimum turn time, minimum turn angle and turn slope. The defaults suit a car, and walking or cycling needs a much lower speed threshold and a longer slow rate.
3. Digipeater path. The usual advice is to keep it short. For many areas, WIDE1-1,WIDE2-1 is the standard for mobiles, and some regions recommend just WIDE2-1 where fill-in digipeaters are rare. Avoid long paths such as WIDE7-7. Each extra hop multiplies the traffic that the whole channel has to carry.
4. A Direwolf iGate or digipeater. Direwolf is a software TNC that uses a sound card to decode and encode 1200 baud packets. It can also run as a digipeater and an RF-to-Internet gateway to APRS-IS. A rough skeleton of the relevant
direwolf.conflines looks like this. It is not a complete config, so check it against the Direwolf documentation for your version:Replace the callsign, passcode and coordinates with your own. Use a sensible beacon interval for a fixed station, because 30 minutes is plenty. Think carefully before enabling Internet-to-RF gating (
IGTXVIAand related settings). RX-only is the safer default, and a licensed operator should understand the local rules and the traffic load before turning on transmit.5. Seeing the result. aprs.fi is useful for checking whether your packet reached an iGate and was posted to APRS-IS. If your station appears there with a raw packet, you know at least one iGate heard it. If it doesn't, either nobody was in range or something is wrong with your path or settings. Note that purely local RF-to-RF digipeating is invisible there unless an iGate also heard it.
6. Beyond position reports. APRS also carries weather reports (wind, gust, temperature in Fahrenheit, rain, humidity, barometric pressure), objects and items (for example a net control point or a marked hazard), and messages. A message is addressed to a callsign padded to 9 characters, with a message number for acknowledgement. Objects use a 9-character name and a live or killed marker.
Questions for the thread: What beacon rate and path do you use for a fixed station versus a mobile? How have you handled Mic-E versus uncompressed position when decoding on other software? And has anyone found a reliable way to confirm that a message was acknowledged end-to-end when using a handheld in a fringe area?
Link to comment
https://www.hamradiobase.com/forums/topic/10952-aprs-on-144390-tuning-a-tracker-a-direwolf-igate-and-a-handheld-so-they-dont-clog-the-channel/Share on other sites