Greetings.

When you set up the Pseudo-APRS-IS plugin, are you sure you updated its configuration to enable "Forward authorized transmissions from client through YAAC's upstream connection"? If that isn't checked, APRS packets from sub-clients of YAAC won't be sent onwards. And you have to use a valid passcode for the callsign specified by your sub-client, or the packets won't be forwarded either; I'm assuming the sub-clients are using your same callsign, but different SSID, so the same passcode used for your upstream Internet connection can be used in the sub-clients.

Also, incorrectly formatted packets won't go on upstream either, so make sure every packet you're injecting is compliant with the APRS Protocol Specification.

If your sub-client's packets show up in YAAC's Raw Packets display in magenta (sort of hot pink) text, that means there's some sort of syntax error in the packets.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of vas22 <vassilis@...>
Sent: Sunday, November 26, 2023 2:19 PM

Hi,

I installed the Pseudo APRS-IS Server plug-in and I can successfully connect and receive packets using the Python aprslib client. However when I try to transmit a packet, I can see the packet in the raw messages log of YAAC but no actual transmission is happening. I have both option checkboxes checked and successfully logged in as an authenticated user.

I have a single port setup (Direwolf) and have enabled transmission, I can send beacon and messages from YAAC with no issues, problem is when connecting to the pseudo APRS-IS server.

Any suggestions on how to send messages from a Python script?

Thanks,
Vassilis

Hi,

I installed the?Pseudo APRS-IS Server plug-in and I can successfully connect and receive packets using the Python aprslib client. However when I try to transmit a packet, I can see the packet in the raw messages log of YAAC but no actual transmission is happening. I have both option checkboxes checked and successfully logged in as an authenticated user.

I have a single port setup (Direwolf) and have enabled transmission, I can send beacon and messages from YAAC with no issues, problem is when connecting to the pseudo APRS-IS server.

Any suggestions on how to send messages from a Python script?

Thanks,
Vassilis

There was a problem in build#185 that would cause the upgrader to fail if you had your operating system distro's copy of the JSSC library installed. So if you are upgrading from that version, it won't work.

Just shut down YAAC and manually unzip the YAAC.zip file over your existing installation (bypassing the broken checks in the upgrade logic) and you should be good.

Andrew, KA2DDO
author of YAAC

________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of KC0TAF Mike <kc0taf@...>
Sent: Monday, November 13, 2023 5:59 AM

I can't update my YAAC, getting the following error message:
[image.png]

Have uninstall and reinstall OpenJDK and YAAC. Still get the error.
--
------------------------------------------------

Mike Wisniewski
KC0TAF
COMT, AUXCOM

Note this new build includes some non-backwards-compatible changes
to the YAAC importing of OpenStreetMap data. The updated map data
(as of the October 30th snapshot) is also available, but requires taking
the code update to use it.

next beta build#191 of YAAC ("Yet Another APRS Client"), created 2023-Nov-13

downloadable from
or

changes and updates include:
1. add support for decoding USGS river flood gauges (from FireNet).
2. remove duplicates from received text messages display.
3. fix scaling of weather flood level value.
4. support maxweight limits in units of persons, i.e., elevator or foot
bridge capacity.
5. allow monitoring APRS Objects the same way specific Stations can be
monitored, including right-clicking to monitor.
6. improve the interface for drawing extra information on line-of-sight
plots, and provide an implementation that can add OpenStreetMap Nodes
and Ways that might obstruct a line-of-sight, but is selectively
enabled by the expert-mode configuration dialog so small machines
running YAAC won't be driven into the ground from the memory demand
if not explicitly chosen.
7. add the ability for code launching line-of-sight panes to get feedback
from antenna height sliders.
8. fix marking start point for line-of-sight plots.
9. add hook for creating non-standard popup menus.
10. work around XML limitation that XML strings cannot contain US-ASCII
NUL control characters, which causes problems for saving Status
message configurations when they don't send Maidenhead locators
with APRS symbol codes.
11. make compatibility-breaking change to OpenStreetMap data storage
format to support more RF line-of-sight blocking structures that can
be plotted by the new line-of-sight plot additions. Users of older
versions of YAAC will need to upgrade to handle the new ways and
nodes files.
12. fix splitting of extremely long OSM Ways (from Relations) that are
multiply-concave.
13. tweak APRS-IS Pseudo Server plugin to allow not having an administrator
name appearing on the status web page.
14. add functionality to the AREDN Objects plugin to plot line-of-sight
for all detected AREDN nodes reported by the local AREDN node's
routing table, and also for proposed new nodes to add to the network.
Note this is a first draft of this functionality, and may be enhanced
in future builds. Also, it depends on the new OpenStreetMap import
functionality introduced in build 191 of core YAAC, and on the
topgraphic data.

开云体育

To clearify. I am not sending those, they are being sent by firenet.us.?

So yes they all have the same format?

Alas, the problem here is that your flood gauge Object is not sending weather station data (in particular, the "Fnnnn" flood level field according to the APRS protocol specification for weather data), so it is not recognized as weather data. Also, you're using the Water Station symbol /w (as in a drinking stop on a public service event course) instead of the Flood Gauge symbol \w (or one of its overlay variants specified in the APRS 1.2 extended symbols list) or one of the weather station codes like /_ (this latter code means the packet contents would actually be interpreted as weather data).

Is the format you're sending the standard for all flood gauges? I might be able to add those additional fields to the Weather Alert plugin. What information are the NNNgh and NNNcfs values, and in what units?

Andrew, KA2DDO
author of YAAC

________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Glen Briggs <kb0rpj.glen@...>
Sent: Monday, November 6, 2023 11:00 PM

i have added a river gauge to the weather station monitor but it reports no data.

However, the gauge is actually reporting the "flood level"



it would be nice if this was fixed and we add alarms for gauge height along with wind and rain to the alerts settings?

i have added a river gauge to the weather station monitor but it reports no data.?

However, the gauge is actually reporting the "flood level"



it would be nice if this was fixed and we add alarms for gauge height along with wind and rain to the alerts settings?

The odd "Q19700 pour Wikidata" is a strange ref="" key somebody attached to the OSM Relation id#11888769 for the River Taff. YAAC treats ref="" attributes of a tag as a highway route number (like the M5 symbol you can see near Gloucestershire). But this one is very poorly formatted, as the value provided could not be used automatically to look up other data about the geographical feature (due to the "pour Wikidata" suffix in the text).

开云体育

I just got it to work (with the correct spelling). Noticed that the YAAC drop-down defaults to the incorrect spelling.
Repeated tests fail however. Is there a limit on traffic through aprslink?

Double check your spelling. There isn't an "i" in WLNK-1. Not sure about your password not working though. It works for mine using WLNK-1. It's case sensitive.

73, de KM4ACK

There were other JDK bugs outstanding indicating that 64-bit Java and 32-bit Java use different subtrees in the Windows registry to store the Preferences, so if you changed JREs, you might move to a different registry tree. Whether your info would still be in the other JRE's tree is a question.

I put that removal of callsigns and APRS-IS passcodes in during config restoration to prevent duplicates if someone decided to use the XML backup for cloning stations; I originally only wrote the config export menu choice to support making easy-to-send config snapshots to help debugging (rather than having to ask people to hand-copy all that information).

With this JDK bug, I may have to allow actually using it for alternate backups. Any regular operating system backup that backed up the registry would probably also back up the old version of the Java runtime.

I wonder if later releases of Java (11, 17, 21, etc.) have the same problems with their upgrades, or if this is a not-so-subtle hint from Oracle to get people to upgrade past Java 8.

Andrew, KA2DDO
author of YAAC

________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of wavetel1 <wavetel@...>
Sent: Thursday, October 26, 2023 8:09 PM

I just changed back to execution from java.exe to javaw.exe and the whole process reoccurred . I had to use the xml backup to get Yaac going again quickly with the callsigns for each port and IS passcode reentered after the xml.
The registry entries must be separate for each of the Java runtimes .

Tony

I just changed back to execution from java.exe to javaw.exe and the whole process reoccurred . I had to use the xml backup to get Yaac going again quickly with the callsigns for each port and IS passcode reentered after the xml.?
The registry entries must be separate for each of the Java runtimes .

Tony

Thanks Andrew for the info.

I had a read of that bug report.? Thats been there or some time unresolved. We are on the same path in the end. We both have an interest in fixing problems and making Yaac work better. I like it as a APRS software package and Ive run a few over the years.
Will just have to be patient now I know whats behind the issue.

Thanks again? Tony VK5AH

开云体育

Think I see the problem. In the drop down menu, "WLINK" is prefilled as the recipient. Instead of using the drop down option, manually type "WLNK-1" in the to field. Then type anything in the message field and send the message. The Winlink system should respond with something like "Login [176:]" which starts the connection. Details on logging in and reading messages in the video link above.

73, de KM4ACK

See the topic/thread I started on this July14 .

Tony