I am using YAAC 1.0 beta on my Raspberry Pi.? ?It has been working fine for the default configuration but I am trying to create a alternate configuration for mobile use.

At the command line I am using? "$ java -jar /yaac/YAAC.jar -profile mobile"??The problem is that after the first setup, the new configuration is not involkable and keeps opening a non-configured version at susbsequent running of the command line.? I am sure I must be overlooking something that is pretty fundamental.? Any help would be appreciated.

Brien - KE7WB

Let's take a look at your problem.

Re: timing: that is entirely possible. Are you receiving the QRU response directly or via a digipeater? If the latter, how long do you wait before querying again? I ask because New-N paradigm digipeaters are specifically designed to not digipeat any given packet more often than once every 30 seconds; so are the APRS-IS backbone servers. So, if you make the same query in under 30 seconds, the response may get sent by the QRU server station, but blocked by the digipeater because it's the exact same Object message(s) and the exact same text message of the quantity report.

So bear in mind that not receiving the second occurrence is not the same as it not being sent. Check the transmit logs on the sending station to see if the response was transmitted a second time. Note that the query and query ack can get through because the querying text message has a sequence number, so each query packet (and corresponding ack) has different contents (even if the actual QRU query text is identical).

Also, what kind of station are you using to make the queries? Fixed or mobile? Note on the YAAC expert-mode configuration tab Transmit, there is not only a checkbox to enable QRU service, but a control to specify the default maximum range the station will respond to. For example, if a station 100 miles away sends the query over digipeaters, but the QRU server only has a 50-mile maximum QRU response radius (or the query specifies an explicit 50-mile limit), the server won't answer; after all, why would that distant station care about a resource it's too far away to reach? And if the querying station has not yet sent a position report that the YAAC QRU server can receive, YAAC will assume the querying station is at the Coast-of-Africa point (latitude 0, longitude 0), which is hundreds to thousands of miles away from any real station location, so it's likely to be out of range for a response.

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Scott Gillins <scott@...>
Sent: Friday, January 5, 2024 1:46 AM

Hey everyone I have a quick question to see if anyone else has experienced this issue before I file a bug.

I have a simple setup with YAAC using kiss over ip connected to Direwolf on the same system. I have been playing around with the QRU fuctionality in YAAC and have seen some behavior that is presenting as a timing issue I just don’t know how to validate where the issue is.

I can create an object in YAAC and set a QRU group. The QRU server is turned on in the configuration. Once I add this object the object gets transmitted out as expected and I see the packet on a second station.

When I send a message to QRU with the group name I see one of two responses. Response 1 is what I expect I get an acknowledgement, then the object information is sent, and finally a message back with the summary on the number of objects in that group.

The second response looks the same in the raw packet sniffer as the first response however when watching the logs on direwolf only the initial ack is sent. Not the objects or the summary message.

If anyone has seen this or has some ideas on how to further debug to try and figure out what it is working sometimes but not other please let me know.

Thanks,
Scott – W2KP

开云体育

Now that drones are required to transmit RemoteID, kind of like ADS-B and AIS systems, anybody know how to receive these and may there be any plans to include it in the APRS display?

IIRC, there are plugins to show ADS-B and AIS objects.

I just learned about this RemoteID stuff, so I don't know much about it yet. I don't know what it takes to receive and decode it.

Thoughts?


--
73,
Michael WA7SKG

"Any day you do not learn one new thing is a wasted day."

On 30 Dec 2023, at 2:52?pm, Andrew P. <andrewemt@...> wrote:

OK, I just tried upgrading YAAC on my Mac (x86 running Sonoma 14.1.2). No problem.

So I'm guessing something strange with the Java runtime on the M2 (ARM) processor, or a new security "feature" in Sonoma 14.2.1. Try starting YAAC from a Terminal window, and saving all the messages that get printed to the Terminal window. There will probably be some error message in there explaining why the other menus didn't get created (such as a failure exception message before it gets to the "YAAC creating main menu bar..." log message.

I just upgraded on Sonoma 14.2.1 with no issues.

I’m using Liberica Full JDK v20.0.2. (Another app I use, sdrtrunk needs that.)


Carl.

OK, I just tried upgrading YAAC on my Mac (x86 running Sonoma 14.1.2). No problem.

So I'm guessing something strange with the Java runtime on the M2 (ARM) processor, or a new security "feature" in Sonoma 14.2.1. Try starting YAAC from a Terminal window, and saving all the messages that get printed to the Terminal window. There will probably be some error message in there explaining why the other menus didn't get created (such as a failure exception message before it gets to the "YAAC creating main menu bar..." log message.

By the way, which version of the Java runtime are you using? In the Terminal window, type the command

java -version

to get it to print out the JRE version.

Looking forward to your response.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Friday, December 29, 2023 4:20 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#192 of YAAC, created 2023-Dec-29

Oh boy!
Not a good start for me. I clicked the usual way of doing things and asked YAAC to download the new version. Then open it, the only thing that opened was the main window with no maps, and no menu items except the default 'YAAC'. Not sure where to go from here.
I’m running a MacBook Air M2 Sonoma 14.2.1. I’ve been running YAAC for years on various Macs this is my first issue with a new version.

Ideas?

Keith, WA0?TJT
Author:
ARRL ARES Communicator Level 2, AEC for Platte Co. MO
KCHEART Radio Operator - St. Lukes Barry Road Hospital

On Dec 29, 2023, at 2:04?PM, Andrew P. <andrewemt@...> wrote:

next beta build#192 of YAAC ("Yet Another APRS Client"), created 2023-Dec-29

downloadable from
or

changes and updates include:
1. general source code cleanup to reduce IDE warnings.
2. fix more issues reported by UMD find_bugs utility.
3. clean up missing Javadocs.
4. remove support for obsolete X-APRS software in weather reports and
add radiation level weather data field in its place.
5. support negative values for Position Report altitude parameter
"/A=nnnnnn".
6. more minor performance improvements.
7. fix YAAC digipeater core logic to support transmissions from
subclients attached through the pseudo-APRS-IS-server plugin, and
ensure the beacons fromn YAAC direct to APRS-IS don't send
spurious digipeat aliases.
8. fix issues with "right-clicking" on a Mac with a one-button mouse
by properly mapping the Option keys in the mouse click handlers.
This also required updating some plugins with custom screen views.
9. rescale line-of-sight plot to display more useful vertical range.
10. fix popup station window to be reasonable size and scrollable if
there are hundreds of stations at the point (such as for the
Coast-of-Africa point for stations without positions).
11. fix OSM downloader to optionally download sways (unlabeled way)
files if preferences say to use them.
12. fix pseudo-APRS-IS-server plugin to properly send APRS frames
upstream (working with the core YAAC fixes to support it).
13. make "right-click" fixes in smallscreen plugin.
14. fix marineports and aisdecoder plugins to support AIS-Catcher
application.

开云体育

开云体育

Oh boy!

next beta build#192 of YAAC ("Yet Another APRS Client"), created 2023-Dec-29

downloadable from
or

changes and updates include:
1. general source code cleanup to reduce IDE warnings.
2. fix more issues reported by UMD find_bugs utility.
3. clean up missing Javadocs.
4. remove support for obsolete X-APRS software in weather reports and
add radiation level weather data field in its place.
5. support negative values for Position Report altitude parameter
"/A=nnnnnn".
6. more minor performance improvements.
7. fix YAAC digipeater core logic to support transmissions from
subclients attached through the pseudo-APRS-IS-server plugin, and
ensure the beacons fromn YAAC direct to APRS-IS don't send
spurious digipeat aliases.
8. fix issues with "right-clicking" on a Mac with a one-button mouse
by properly mapping the Option keys in the mouse click handlers.
This also required updating some plugins with custom screen views.
9. rescale line-of-sight plot to display more useful vertical range.
10. fix popup station window to be reasonable size and scrollable if
there are hundreds of stations at the point (such as for the
Coast-of-Africa point for stations without positions).
11. fix OSM downloader to optionally download sways (unlabeled way)
files if preferences say to use them.
12. fix pseudo-APRS-IS-server plugin to properly send APRS frames
upstream (working with the core YAAC fixes to support it).
13. make "right-click" fixes in smallscreen plugin.
14. fix marineports and aisdecoder plugins to support AIS-Catcher
application.

Andrew,
? ? ? ? ? ?First thank you for replying. And the answer to your first two questions are yes and no.
The grid squares that I have noticed with the blue conditions are (these are coordinates with in the square)
1. 35 29.55N - 84 22.08W
2. 33 30.42N - 87 32.01W
3. 33 29.15N - 96 32.70W

I am brand new to YAAC and have most likely caused most of these issues trying to learn what is what and for that i apologize.

Andrew,

You are correct and I will change to the Yaesu cable. ?I need to get dire wolf working on my M1 Mac to have this work like I would like. ?

Tim?
KM4ESU

Greetings.

It sounds like you're viewing an area of the YAAC-imported OpenStreetMap data where there are some errors in determining ocean boundaries. Per chance, have you:

1. imported the OSM data snapshot yourself, rather than downloading from my website? and
2. used the osmcoastline utility to get the ocean boundaries?

Please let me know the approximate lat/lon of the blue squares so I can check the data there. I don't look at the entire planet on a regular basis.

Since approximately the October 2nd 2023 snapshot of OSM, there have been errors in the coastline/shoreline tagged Ways in the database where the oceans aren't decoded correctly. If the osmcoastline utility reports _any_ erroneous Ways in the dataset, then YAAC will probably import the ocean data incorrectly. So I haven't used any snapshot more recent than that to identify coastlines, even though I have used more recent snapshots for the rest of the map data (I figured that the coastlines weren't going to move much, regardless of how much highway construction was going on). When I used a more recent snapshot with osmcoastline, it put all of Europe and western Russia underwater. I'm not sure when this will be fixed in the OSM database, and I am attempting to work around it, but haven't released the latest workarounds yet.

Re: heap limits: The Java Runtime Environment virtual machine allocates a certain limited amount of heap memory for running the YAAC program (if you don't specify the -Xmx command line option, it defaults to half the physical RAM on your system). All the YAAC code, JRE library code, and third-party library code in use, plus all the data objects manipulated by this code are allocated memory from the heap. So, you can have a heap shortage if YAAC is trying to hold too much data in memory. The YAAC OSM Importer is an extreme heap pig, trying to use the heap to cache data to reduce the amount of disk I/O when importing the OSM data. However, you can over-demand your available heap without running the OSM Importer if any of the following conditions apply:

1. You are displaying topographic terrain data on the map (a certain amount of the terrain data in use is cached in heap for more efficient rendering). This gets worse if you chose to use 1-arc-second resolution data (takes up 9 times as much heap per 1-degree square as 3-arc-second data).
2. You have very large raster images superimposed on the map.
3. You are using an APRS-IS connection with either a very wide filter or an unfiltered connection, such that YAAC is having to keep track of the state of multiple thousands of APRS stations and objects.
4. You have YAAC configured to have an long in-memory retention interval for historical data about stations and objects (more data in heap per station for long-life-span heard stations).
5. You are running YAAC with an undersized heap for your use case (for example, half the RAM on a Raspberry Pi 2 is only 128MB).

Those heap error messages come out when YAAC detects that the heap is near its limit. Because the default behavior for Java is to crash if heap garbage collection (the process of reclaiming heap memory that is no longer being used) happens excessively (i.e., YAAC keeps needing to allocate more memory, but there isn't enough unused heap even after forcing a garbage collection), YAAC tries to take action to keep the heap under control before the Java runtime crashes. YAAC's behavior in this case is to shorten the in-memory retention interval (reason#4 above) so that more not-quite-as-old APRS packets can be garbage collected and thereby free up more heap before the heap state reaches critical. The "heap error" message is displayed when this happens so you know you're losing in-memory data.

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of W4ACR-Randy Shell
Sent: Wednesday, December 20, 2023 10:14 AM

Hello,
??????I have a couple of questions.

1. Why are some of the grid squares shaded blue? And can they be removed?
2. How do i correct heap limit errors?

开云体育

What operating system / audio interface software are you using?

开云体育

开云体育

Hi Tim,?

Hello, I am using the Digirig with my FTM-400 and YAAC. ?I can't get any data to flow from the FTM-400 and YAAC. ?Ideally, it should send the APRS data out to the Audio port of the Digirig. ?That would then be input to YAAC to show the data. ?I can't seem to get the data from the FTM-400 to show on YAAC. ?

Tim?
KM4ESU

开云体育

Greetings,
I've got fldigi configured to listen on port 8001, TCP/IP, Listen/Bind, Auto Connect/Retry.

In YAAC, I configure a KISS-over-TCP port, localhost, 8001. Sometimes when I save the port it doesn't actually save properly. I'll go back in and my callsign would be missing and, when I was using a port other than 8001, the port number would be missing. Every time I try to enable the port I get the following error:

1702507944738: PortEditor: starting to create editor
1702507944739: PortEditor: starting to create per-driver cards
1702507944739: PortEditor: loading editor class for KISS-over-TCP
1702507944739: PortEditor: creating card for KISS-over-TCP
1702507944803: PortEditor: creating card selector
1702507944812: PortEditor: selected appropriate default card KISS-over-TCP
1702507944812: PortEditor: created.
Wed Dec 13 17:52:29 EST 2023: opening TCP socket to KISS TNC at localhost/127.0.0.1:8001
Error Opening Port; Discard This Port?: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.ka2ddo.yaac.io.KissOverTcpConnector.configure(KissOverTcpConnector.java:277)
at org.ka2ddo.yaac.gui.BlinkenLight$1.itemStateChanged(BlinkenLight.java:262)
at java.desktop/javax.swing.AbstractButton.fireItemStateChanged(AbstractButton.java:2000)
at java.desktop/javax.swing.AbstractButton$Handler.itemStateChanged(AbstractButton.java:2320)
at java.desktop/javax.swing.DefaultButtonModel.fireItemStateChanged(DefaultButtonModel.java:458)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setSelected(JToggleButton.java:374)
at java.desktop/javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:392)
at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
at java.desktop/java.awt.Component.processMouseEvent(Component.java:6626)
at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3389)
at java.desktop/java.awt.Component.processEvent(Component.java:6391)
at java.desktop/java.awt.Container.processEvent(Container.java:2266)
at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5001)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948)
at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4575)
at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516)
at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310)
at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2780)
at java.desktop/java.awt.Component.dispatchEvent(Component.java:4833)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:775)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:720)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:714)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:747)
at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:744)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)

I had it working once but then fldigi froze up and wouldn't respond. Any ideas?

73,
Eric WG3K

开云体育