I have YAAC configured as a two way iGate. I'd like the packets I send from my phone using APRSDroid to be transmitted locally by my iGate. The phone packets are reaching APRS-IS as I seem them on aprs.fi. But they do not transmit from the IGate. I must be missing something. Thanks

Tom - KG2U

The supplemental I-gate filters are saved when you press the ENTER key (on a PC-type keyboard). If you change the field again, press ENTER to confirm the change.

There are several solutions to your request. Obviously, YAAC will be promoted here (since I wrote it for exactly this kind of work), although there are other Linux/Unix APRS programs. However, a 10" monitor is probably going to be too small for a bicycle event if you are at the Net Control station and need to be able to see the entire course in detail. I typically use a laptop computer connected to a 40" flat screen for those events, but I have AC power available at those events. Other events I know of that have indoor Net Control locations use projectors as monitors. Now, if you're using APRS in a support vehicle, then the 10" screen is probably enough.

Now using a USB-connected SDR (such as the RTL SDR dongle) instead of a conventional amateur radio rig requires a bit more. A program called rtl_fm can configure such a stick to demodulate FM radio (such as 2M ham transmitters), and couple its output into Direwolf as the software modem/TNC for AX.25 packets. YAAC then connects to Direwolf to provide the graphical views of the received APRS packets.

Here's a link with directions for setting things up with the SDR and Direwolf:


Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Chuck Berry <n7chs.qsx@...>
Sent: Tuesday, April 28, 2020 7:15 PM
To: yaac-users@groups.io
Subject: [yaac-users] APRS decode/map display, No Internet

Previously posted on Facebook-APRS. It was suggested that I post here.

Looking for a APRS receive/decode/display map solution for a upcoming
race event. Most solutions revolve around an IGate. I would like to do
with a SDR, Raspberry Pi and 10" monitor. Suggestions Please. Note:
Internet unavailable. There are two digipeaters in the surroundings
hills that will cover the race course. Thx, Chuck N7CHS

Previously posted on Facebook-APRS. It was suggested that I post here.

Looking for a APRS receive/decode/display map solution for a upcoming race event.? Most solutions revolve around an IGate. I would like to do with a SDR, Raspberry Pi and 10" monitor. Suggestions Please. Note: Internet unavailable. There are two digipeaters in the surroundings hills that will cover the race course. Thx, Chuck N7CHS

Thanks Andrew,?

I knew the problem was on my side somewhere.?

It's been running steady for a few hours now.?

Thanks
Tim KD9DBG

It looks like the problem is in the filter you specified for the APRS-IS port. You have a filter of "r/100". However, that is not correct syntax for an "r" filter. For your location, an expression similar to "r/42/-88/100" (latitude/longitude/range) would work correctly. You might have intended to use an "m" filter, where the circle center is assumed from your beacon position. I'm not sure if any of the different programs used for APRS-IS backbone servers would accept the invalid syntax of the "r" filter you are using and assume you meant a "m" filter, so the variation might depend on which specific backbone server you connected to at any time.

Andrew, KA2DDO
author of YAAC

Andrew,
First Thanks for all that you have done with YAAC I've been using it for years without issue for tracking my school's race cars.?

Since everything is shutdown I though I would take this time to finally build a full APRS station at home.?

Fresh new install of Raspbian on a Pi 3+
Fresh compile and install of Direwolf 1.6 DEV
Fresh download of YAAC


Good news: I can send and receive packets!
Inconsistent is getting packets from aprs-is?

I've tried just configuring via Direwolf ... I can get APRIS packets but they don't show up in YAAC
I've tried just using direwolf for TNC and configure ports through YAAC ... Sometimes I get a flow of packets ... sometimes not at all ... (I'm near Milwaukee and Chicago there is traffic I should be seeing)

Sometimes everything works flawless ... shutdown and come back later and nothing. ...

I've tried changing the filter.?
I've configured GDPS and Manually put in GPS Location ...?

I'm just scratching my head. I know it is a configuration error on my part, but where?

I've attached both my direwolf config and the export from YAAC.?

Any clarity would be helpful.?
Thanks

Excellent. Thanks Andrew!

No, that's perfectly normal. Most mobile and portable APRS radios transmit the Mic-E format of position report message, which is a highly compact, compressed, and human-illegible format for encoding the station latitude, longitude, status code and APRS symbol. The gory details of this message format are documented in chapter 10 of the APRS Protocol Specification. What is being displayed in the Radio View are the exact characters in the APRS packet, not the decoded human-meaningful data.

If you want to see what the data decodes to, click the right arrow button on the Radio View window to cycle through the different views modes.

Andrew, KA2DDO
author of YAAC
________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Thomas Utesch <tom@...>
Sent: Tuesday, April 28, 2020 8:52 AM

When observing the radio display on YAAC when and my separate Yaesu FT-100DR beacons I get this on the YAAC radio display:

`g2Nl"+[/`"6+}_0

What do I have configured wrong, either on my HT or YAAC?

Thanks.

Tom - KG2U

When observing the radio display on YAAC when and my separate Yaesu FT-100DR beacons I get this on the YAAC radio display:

`g2Nl"+[/`"6+}_0

What do I have configured wrong, either on my HT or YAAC?

Thanks.

Tom - KG2U

When I beacon from my handheld (Yaesu FT-3DR) and it appears on the radio display of YAAC I see this:

Re: running YAAC as root: DON'T DO IT!

The reason it works as root and then fails horribly as an ordinary user is that root has access to everything, and doesn't need to be granted access to serial ports, the lock directory, etc. Furthermore, it creates the YAAC log files as owned by root, so that a later run of YAAC as ordinary user doesn't have permission to append to the log files.

Grant your ordinary user account membership in the appropriate groups (lock and dialout) and ensure the /run/lock directory's group is lock and it is group-writeable.

The I-gate symbols are documented on the YAAC help page on configuring an I-gate. However, as a short reminder, there are several symbol choices, depending on how your I-gate is set up.

I& is the typical I-gate symbol (& is the symbol code for gateways of all types, and the overlay indicates the type).
T& indicates a transmit-capable I-gate (since so many are receive-only).
2& indicates a transmit-capable I-gate that uses a digipeat path allowing a second RF hop (one digipeat).
R& indicates a receive-only I-gate (unable or unwilling to forward Internet packets to local RF stations).
I# is a variant of the digipeater symbol indicating a station functioning as both a digipeater and an I-gate.

Don't use D&, as that indicates a D-star gateway.

Hope this helps.

Andrew, KA2DDO
author of YAAC

Greetings. Playing catch-up on things I didn't answer, or answered privately instead of to the list.

The Track Station option just keeps the station on the visible part of the map. It only pans if the station would move off the edge of the map. This is because map re-drawing is expensive, especially on machines like the Raspberry Pi with extremely slow mass storage (the SD card). So I wanted to minimize the map redraws to only when necessary.

Note that, if you are tracking multiple mobile stations that are going off opposite sides of the map, the map may zoom out to keep both stations on the map simultaneously.

There is a new choice on the View menu, the Tracked Station List, which allows you to customize the map behavior on a per-station basis. One useful option there is the Double-Sized Icon; if you are not already using double-sized icons for all stations, this could make it easier to spot tracked stations because they would be drawn larger on the map.

Hope this helps.

Andrew, KA2DDO
author of YAAC

More improvements in the map importer for the upcoming build 149, improving the rendering of large bodies of water (and the shorelines near them) significantly.

Good idea. Notes about installing the relevant Linux packages will be added in the build 149 version of the Bluetooth plugin.

开云体育

Andrew,

thanks a lot for getting back to me on this. ?I wasn’t sure if I’d posted correctly and I apologize for not following up. ?After this I checked my setup again and I think I’ve figured out that I had the tx delay on the TNCPI set to short such that even though it was transmitting when my radios heard the “ack” from the Digipeater from a Igated device my radios wouldn’t hear it, they just heard the last part of the transmission I guess. So i got on and programmed a 250ms preamble delay and haven’t had any problems with the outbound transmissions. ?

Great software, I’m deploying this on a popular repeater site to cover the east / central side of phoenix area. ?

Hi, Joe.

After much tearing of hair and taking the names of several famous mathematicians in vain :-) I have found a new algorithm for the map importer that fixes your issues on Lake Ontario (and several other places). I'm still resolving some corner cases for Lake Superior and Lake Michigan, but I hope to have them fixed as well in a few days. It's just painful that it takes 20 hours (!) to run the entire planet OSM dataset through the importer so I can check the results. I fixed most of the Lake Ontario issues using a map data excerpt for just the lake and its immediate surrounds, but even that took an hour per run.

Andrew, KA2DDO

To avoid this issue for other users, I am making a change in the configuration wizard in build 149, such that changing your callsign will check for every port using the old callsign and ask whether you want to update the callsign on those ports. It will also account for SSID changes (even if the callsign doesn't change).