开云体育

Thank you. Nice setup you have there.

Regarding your feature requests:

1. Track all stations is already available. Turn it on from View->Map Layers->Show Track Stripes. This is persisted over YAAC restarts so the next time you open YAAC it will be doing it again (or not) as you left it before. You can also specify plotting track stripes on a per-station basis from the Tracked Stations table. Also, if you don't mind having your computer talking to you, you can install the sounds plugin and the espeak application, attach a speaker to the audio out jack on the Pi, and then YAAC can verbally announce when new stations come into range. I don't recommend doing this on a major digipeater site, however; a friend of mine who's on a major Interstate highway leading to Dayton, Ohio, did that just before Hamvention a few years ago and YAAC just would not shut up about all the hams en-route to Dayton. :-)

2. I never thought one person would be simultaneously chatting with multiple people over APRS (unless it was to a single group alias for a round-table). But that sounds like a reasonable re-design of that particular window. I'll look into it. It might also be a good addition for the smallscreen plugin as well.

3. There is some control over traffic routing already.
a. Each RF port specifies which digipeating aliases it supports (suitable to ensure a VHF/HF cross-band digipeater doesn't accidentally flood the slow HF channel with local VHF traffic), which beacon it transmits (you can have a different beacon per port), and what types of traffic that port will transmit (APRS, OpenTRAC, or raw connected-mode AX.25, or any combination thereof). You can't control what it will receive (YAAC accepts anything it hears), but then you can't control what other stations are going to transmit anyway.
b. connected-mode traffic tries to use the RF port pointing at the specified station if there are multiple ports that the traffic could go through (per the traffic type settings above).
c. Each RF and APRS-IS port can be selectively enabled for transmit (so you can have a receive-only port if needed). APRS-IS ports also support beacon choice.
d. The transmit log file lists the port each packet was transmitted through.
e. You can filter the raw packet and map displays based on the port traffic was received through.

Let me know what kind of additional traffic control you need.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of KG7KMV <jonglauser@...>
Sent: Thursday, December 10, 2020 12:06 PM
To: [email protected]
Subject: [yaac-users] Success story

Just wanted to share my success story:

* Raspberry Pi 3 B
* NinoTNO from tarpn.net
* Baofeng UV5R for now, just ordered a better radio as it's too weak/deaf in my area
* KM4ACK Build-a-Pi script to install VHF related software including YAAC
* Using realVNC to access the PI from a laptop/desktop/tablet
* all housed in a small HF/Apache weatherproof case
* The case has a N type bulkhead antenna connector and waterproof power connector. The radio is modified to run on 12V and the Pi has a 12V-5v converter.
* There is room to add a small battery for off-grid operation.

I've had this up for a few weeks and it's been great as a 2-way igate. There is one other RF-IS igate in my town and another 20 miles away in another town.
It was fairly easy to setup entirely through the GUI, no command line required!
I have been using it to message as many stations as I can and have made a few contacts. One is a neighbor running a BBS on 145.010 so I'm interested in adding another TNC/radio for the other frequency as long as I can make sure to direct traffic out the appropriate ports.

For a comparison I tried using Xastir, but didn't like it as much. YAAC is more responsive in map rendering and UI features. I like the messaging capabilities in YAAC better as well

pie-in-the-sky features I'd like to see:

* option to automatically start tracking new (mobile) stations so I don't have to enable it individually

* bring all the individual "chat with station" windows together into a single window with tabs or other way to select who you're chatting with.

* visibility into and/or control over which port data is being sent to (RF, IP, second RF, etc)