¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Yaac-Users
  2. Messages
Expanded Topics Messages Polls
Date
Re: next build#193 of YAAC, created 2024-Jan-20

 

¿ªÔÆÌåÓý

Well, now I have a very red face. I launched YAAC 1.0-beta193(20-Jan-2024) to collect the requested data and now it¡¯s coming up and looks good. In trying to solve my own issues today I did reload Java this is now what I have;

logdir % java -version

openjdk version "16.0.1" 2021-04-20

OpenJDK Runtime Environment AdoptOpenJDK-16.0.1+9 (build 16.0.1+9)

OpenJDK 64-Bit Server VM AdoptOpenJDK-16.0.1+9 (build 16.0.1+9, mixed mode, sharing)

logdir %?


But something is niggling at my brain saying this doesn¡¯t seem right, what say you?


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

On Jan 20, 2024, at 9:18?PM, Carl Makin <carl@...> wrote:

Hi Keith,

On 21 Jan 2024, at 3:00?am, Keith Kaiser <wa0tjt@...> wrote:

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?

I¡¯m running a M1 Max MacBook Pro on the latest Sonoma and am having no issues. ?The current version (and the few previous) all run fine. ?As Andrew asks, can you tell us what version of Java you are using and launch it in a terminal session (or send us the relevant parts of the logdir/YAAC.out log).

FYI I¡¯m using the Bellsoft Liberica Full JDK v20.0.2 (needed for SDRTrunk).

Carl,
vk1kcm.
Re: next build#193 of YAAC, created 2024-Jan-20

 

Hi Keith,

On 21 Jan 2024, at 3:00?am, Keith Kaiser <wa0tjt@...> wrote:

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?
I¡¯m running a M1 Max MacBook Pro on the latest Sonoma and am having no issues. The current version (and the few previous) all run fine. As Andrew asks, can you tell us what version of Java you are using and launch it in a terminal session (or send us the relevant parts of the logdir/YAAC.out log).

FYI I¡¯m using the Bellsoft Liberica Full JDK v20.0.2 (needed for SDRTrunk).

Carl,
vk1kcm.
Re: next build#193 of YAAC, created 2024-Jan-20

 

Thanks for the update Andrew, everything is working perfectly with AIS-Catcher!

Best de N2UGS
Re: next build#193 of YAAC, created 2024-Jan-20

 

Actually, if you can send me that startup log, that would help immensely in debugging the problem, since I don't have a copy of your hardware to replicate it. You can find the log in your log directory in the file YAAC.out.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Saturday, January 20, 2024 11:13 AM
To: [email protected]
Subject: Re: [yaac-users] next build#193 of YAAC, created 2024-Jan-20

I have no idea. I just upgraded my Mac (x86, alas) on Sonoma 14.2.1, and YAAC ran fine. All I can think of is that you have a security setting in Mac OS X that is preventing YAAC from opening some of the data files.

Have you tried running YAAC from a Terminal window, so you can see the progress and error messages it spews out? Those messages would probably tell why you're having the problem (such as an IOException for permission reasons).

Also, what version and vendor of the Java runtime are you using?

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Saturday, January 20, 2024 11:00 AM
To: [email protected]
Subject: Re: [yaac-users] next build#193 of YAAC, created 2024-Jan-20

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?

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

On Jan 19, 2024, at 11:24?PM, Andrew P. <andrewemt@...> wrote:

next beta build#193 of YAAC ("Yet Another APRS Client"), created 2024-Jan-20

downloadable from
or

changes and updates include:
1. write JUnit unit test cases that will be executed when using Maven
as the build tool. This covers part of core YAAC and the AISdecoder
and marineports plugins.
2. make changes in core YAAC code to permit unit tests to run.
3. fix bug in packet creation where AX.25 frames didn't have the last
digipeater address marked with the "last" bit as required by the AX.25
protocol specification.
4. fix formatting error in NMEA-0183 format GPS logger.
5. fix getting access to Help files in a newly-installed plugin.
6. minor non-functional code cleanup in ADS-B decoder plugin.
7. fix AIS decoder to properly support AIS-Catcher as a data source,
and add JUnit tests to verify it.
8. fix marineports plugin to remove unwanted check for port callsign
and to collect port throughput statistics, and add JUnit test cases
to verify correct operation.
Re: next build#193 of YAAC, created 2024-Jan-20

 

I have no idea. I just upgraded my Mac (x86, alas) on Sonoma 14.2.1, and YAAC ran fine. All I can think of is that you have a security setting in Mac OS X that is preventing YAAC from opening some of the data files.

Have you tried running YAAC from a Terminal window, so you can see the progress and error messages it spews out? Those messages would probably tell why you're having the problem (such as an IOException for permission reasons).

Also, what version and vendor of the Java runtime are you using?

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Saturday, January 20, 2024 11:00 AM
To: [email protected]
Subject: Re: [yaac-users] next build#193 of YAAC, created 2024-Jan-20

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?

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

On Jan 19, 2024, at 11:24?PM, Andrew P. <andrewemt@...> wrote:

next beta build#193 of YAAC ("Yet Another APRS Client"), created 2024-Jan-20

downloadable from
or

changes and updates include:
1. write JUnit unit test cases that will be executed when using Maven
as the build tool. This covers part of core YAAC and the AISdecoder
and marineports plugins.
2. make changes in core YAAC code to permit unit tests to run.
3. fix bug in packet creation where AX.25 frames didn't have the last
digipeater address marked with the "last" bit as required by the AX.25
protocol specification.
4. fix formatting error in NMEA-0183 format GPS logger.
5. fix getting access to Help files in a newly-installed plugin.
6. minor non-functional code cleanup in ADS-B decoder plugin.
7. fix AIS decoder to properly support AIS-Catcher as a data source,
and add JUnit tests to verify it.
8. fix marineports plugin to remove unwanted check for port callsign
and to collect port throughput statistics, and add JUnit test cases
to verify correct operation.
Re: next build#193 of YAAC, created 2024-Jan-20

 

FWIW, may be not related, but I have been seeing a lot of complaints recently from users of MacBooks that various ham applications are not working correctly. I'm wondering if there has been some recent update to the OS that does something different to files.

Just a thought.

Michael WA7SKG



Keith Kaiser wrote on 1/20/24 8:00 AM:

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?
Keith, WA0?TJT
Author:
ARRL ARES?Communicator?Level 2, AEC for?Platte Co. MO
KCHEART Radio Operator - St. Lukes Barry Road Hospital

On Jan 19, 2024, at 11:24?PM, Andrew P. <andrewemt@...> wrote:

next beta build#193 of YAAC ("Yet Another APRS Client"), created 2024-Jan-20

downloadable from
??????????????or

changes and updates include:
1. write JUnit unit test cases that will be executed when using Maven
???as the build tool. This covers part of core YAAC and the AISdecoder
???and marineports plugins.
2. make changes in core YAAC code to permit unit tests to run.
3. fix bug in packet creation where AX.25 frames didn't have the last
???digipeater address marked with the "last" bit as required by the AX.25
???protocol specification.
4. fix formatting error in NMEA-0183 format GPS logger.
5. fix getting access to Help files in a newly-installed plugin.
6. minor non-functional code cleanup in ADS-B decoder plugin.
7. fix AIS decoder to properly support AIS-Catcher as a data source,
???and add JUnit tests to verify it.
8. fix marineports plugin to remove unwanted check for port callsign
???and to collect port throughput statistics, and add JUnit test cases
???to verify correct operation.
Re: next build#193 of YAAC, created 2024-Jan-20

 

¿ªÔÆÌåÓý

The last two versions of YAAC will not open properly on a M1 MacBook Air. The window opens but nothing is in it, the menu bar is empty. I have plenty of RAM, and I¡¯ve been using YAAC for years. Whats up?

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

On Jan 19, 2024, at 11:24?PM, Andrew P. <andrewemt@...> wrote:

next beta build#193 of YAAC ("Yet Another APRS Client"), created 2024-Jan-20

downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html
??????????????or https://sourceforge.net/p/yetanotheraprsc

changes and updates include:
1. write JUnit unit test cases that will be executed when using Maven
???as the build tool. This covers part of core YAAC and the AISdecoder
???and marineports plugins.
2. make changes in core YAAC code to permit unit tests to run.
3. fix bug in packet creation where AX.25 frames didn't have the last
???digipeater address marked with the "last" bit as required by the AX.25
???protocol specification.
4. fix formatting error in NMEA-0183 format GPS logger.
5. fix getting access to Help files in a newly-installed plugin.
6. minor non-functional code cleanup in ADS-B decoder plugin.
7. fix AIS decoder to properly support AIS-Catcher as a data source,
???and add JUnit tests to verify it.
8. fix marineports plugin to remove unwanted check for port callsign
???and to collect port throughput statistics, and add JUnit test cases
???to verify correct operation.
Re: Open GPX at Start

 

Probably because there isn't a feature in core YAAC to automatically open a GPX (or KML) map drawing at YAAC startup. If YAAC is shut down, you presently have to manually reload any map drawings at YAAC restart from the File->Load menu.

However, the routes used by the Dynamic Objects plugin can be persisted over YAAC restarts. So, if you install that plugin, and load your GPX file as a route rather than a plain map drawing overlay, you can specify that the route is persisted.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jeff <KO4NCC@...>
Sent: Friday, January 12, 2024 5:19 PM
To: [email protected]
Subject: [yaac-users] Open GPX at Start

I'm probably just missing something obvious but I can't figure out how to get a GPX to open at start.
73 KO4NCC Jeff
Open GPX at Start

 

I'm probably just missing something obvious but I can't figure out how to get a GPX to open at start.
73 KO4NCC Jeff
next build#193 of YAAC, created 2024-Jan-20

 

next beta build#193 of YAAC ("Yet Another APRS Client"), created 2024-Jan-20

downloadable from
or

changes and updates include:
1. write JUnit unit test cases that will be executed when using Maven
as the build tool. This covers part of core YAAC and the AISdecoder
and marineports plugins.
2. make changes in core YAAC code to permit unit tests to run.
3. fix bug in packet creation where AX.25 frames didn't have the last
digipeater address marked with the "last" bit as required by the AX.25
protocol specification.
4. fix formatting error in NMEA-0183 format GPS logger.
5. fix getting access to Help files in a newly-installed plugin.
6. minor non-functional code cleanup in ADS-B decoder plugin.
7. fix AIS decoder to properly support AIS-Catcher as a data source,
and add JUnit tests to verify it.
8. fix marineports plugin to remove unwanted check for port callsign
and to collect port throughput statistics, and add JUnit test cases
to verify correct operation.
New Version 1.0 (1.8.0_331) Issues

 

¿ªÔÆÌåÓý

I¡¯ve been running YAAC for many, many years so am pretty accustomed to having no issues with updates but this version?1.0 (1.8.0_331) is the exception. I did this update from the Help==>Check for Updates menu item as I¡¯ve done many times before.

I¡¯m running it on a M2 MacBook Air, lots of disk space, lots of RAM, Sonoma 14.2.1.?

The update seemed to go just fine as it always does. But on launch the map window opens but no maps or banners or buttons or anything open with it. There is also no menu bar opened with it, pretty much just a white page the size of what the map should be.

If I go back to the previous version of 16-Jul-2023 everything opens correctly and all functionality is restored.?

Has anyone experienced this issue and if so how did you recover from it?

Thanks...

Keith, WA0?TJT
Author: https://net-control.us
ARRL ARES?Communicator?Level 2, AEC for?Platte Co. MO
KCHEART Radio Operator - St. Lukes Barry Road Hospital
Re: Unknown zoneType='C' for advisory...

 

Yes, this fixed the issue. I really wish there was a decent way of scripting downloading and keeping these files up to date.

Thanks,
Eric WG3K

On Tuesday, January 9th, 2024 at 19:07, Andrew P. <andrewemt@...> wrote:


There are three categories of severe weather zones: "Z"ones, "C"ounty, and "M"arine. If you didn't install all three categories and receive a NWS_WARN message referencing a missing category, this will happen.
Hope this helps.

Andrew, KA2DDO
author of YAAC


[email protected] <[email protected]> on behalf of Eric H. Christensen via groups.io <eric@...>
From:
Tuesday, January 9, 2024 6:41:51 PM
Sent:
Andrew,

I'm not seeing many of the NWS advisories on my map even though I'm seeing the APRS data going across.? Just found this in my error log: Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,FLASH_FLOOD,NCC071,NCC119,SCC091{G00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN



Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,FLASH_FLOOD,NCC115,NCC121,NCC199{E00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Re: YAAC and AIS-Catcher?

 

How embarrassing. You found a bug. Lots of the code in the NMEA0183OverTcp port driver was copied from the APRS-IS port driver, and I forgot to take out the callsign check. And I don't have a TCP-based NMEA-0183 data source to test this code with. :-(

I will have a fix out very soon.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jeremy N2UGS <jmedinac@...>
Sent: Tuesday, January 9, 2024 7:46 PM
To: [email protected]
Subject: Re: [yaac-users] YAAC and AIS-Catcher?

I do have both plugins installed and when I use the NEMA TCP port I get some error along the lines of "not a valid callsign". Where would I input a callsign?

[cid:[email protected]]

Best Regards

Jeremy N2UGS

Capture19a.JPG

Re: YAAC and AIS-Catcher?

 

I do have both plugins installed and when I use the NEMA TCP port I get some error along the lines of "not a valid callsign". Where would I input a callsign?



Best Regards?

Jeremy N2UGS
Re: Unknown zoneType='C' for advisory...

 

¿ªÔÆÌåÓý

There are three categories of severe weather zones: "Z"ones, "C"ounty, and "M"arine. If you didn't install all three categories and receive a NWS_WARN message referencing a missing category, this will happen.

Hope this helps.

Andrew, KA2DDO
author of YAAC

From: [email protected] <[email protected]> on behalf of Eric H. Christensen via groups.io <eric@...>
Sent: Tuesday, January 9, 2024 6:41:51 PM

Andrew,
I'm not seeing many of the NWS advisories on my map even though I'm seeing the APRS data going across.? Just found this in my error log:

Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,FLASH_FLOOD,NCC071,NCC119,SCC091{G00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,FLASH_FLOOD,NCC115,NCC121,NCC199{E00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Unknown zoneType='C' for advisory...

 

Andrew,
I'm not seeing many of the NWS advisories on my map even though I'm seeing the APRS data going across. Just found this in my error log:

Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,FLASH_FLOOD,NCC071,NCC119,SCC091{G00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,FLASH_FLOOD,NCC115,NCC121,NCC199{E00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS_WARN:100015z,FLASH_FLOOD,NCC115,NCC121,NCC199{E00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:33:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}RAHFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100030z,FLASH_FLOOD,NCC007,NCC123,NCC125,NCC153,NCC167{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}RAHFFW>APRS,qAO,AE5PL-WX::NWS_WARN:100030z,FLASH_FLOOD,NCC007,NCC123,NCC125,NCC153,NCC167{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}HFOFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,FLASH_FLOOD,HIC009{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}HFOFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100015z,FLASH_FLOOD,HIC009{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}AKQFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100330z,FLASH_FLOOD,VAC007,VAC049,VAC111,VAC117,VAC135,VAC147{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}AKQFFW>APRS,qAO,AE5PL-WX::NWS_WARN:100330z,FLASH_FLOOD,VAC007,VAC049,VAC111,VAC117,VAC135,VAC147{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101115z,FLOOD,GAC089,GAC247{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101115z,FLOOD,GAC089,GAC247{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}RAHFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100200z,FLASH_FLOOD,NCC063,NCC069,NCC077,NCC181,NCC183,NCC185{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}RAHFFW>APRS,qAO,AE5PL-WX::NWS_WARN:100200z,FLASH_FLOOD,NCC063,NCC069,NCC077,NCC181,NCC183,NCC185{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}MLBSVR>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,SVR_STORM,FLC009,FLC095,FLC117,FLC127{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:33:51 EST 2024 error parsing NWS zone message "}MLBSVR>APRS,qAO,AE5PL-WX::NWS_WARN:100015z,SVR_STORM,FLC009,FLC095,FLC117,FLC127{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}CAEFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100030z,FLASH_FLOOD,SCC025{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}CAEFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101330z,FLOOD,SCC047,SCC071,SCC081{600AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}ILMSVR>APRS,qAO,AE5PL-WX::NWS-WARN:092345z,SVR_STORM,NCC017,NCC047,NCC155,SCC033,SCC041,SCC043,SCC051,SCC067,SCC089{C00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}ILMSVR>APRS,qAO,AE5PL-WX::NWS_WARN:092345z,SVR_STORM,NCC017,NCC047,NCC155,SCC033,SCC041,SCC043,SCC051,SCC067,SCC089{C00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}CAEFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101330z,FLOOD,SCC037,SCC065{700AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}CAEFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101330z,FLOOD,SCC037,SCC065{700AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}RLXFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101600z,FLOOD,WVC075,WVC083{700AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}RLXFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101600z,FLOOD,WVC075,WVC083{700AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}MHXSVR>APRS,qAO,AE5PL-WX::NWS-WARN:100015z,SVR_STORM,NCC013,NCC049,NCC095,NCC103,NCC117,NCC137,NCC187{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}MHXSVR>APRS,qAO,AE5PL-WX::NWS_WARN:100015z,SVR_STORM,NCC013,NCC049,NCC095,NCC103,NCC117,NCC137,NCC187{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}MLBSVR>APRS,qAO,AE5PL-WX::NWS-WARN:092345z,SVR_STORM,FLC095,FLC097,FLC117,FLC127{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}MLBSVR>APRS,qAO,AE5PL-WX::NWS_WARN:092345z,SVR_STORM,FLC095,FLC097,FLC117,FLC127{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}RNKFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100115z,FLASH_FLOOD,NCC189{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}RNKFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100115z,FLASH_FLOOD,NCC189{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101130z,FLOOD,GAC117,GAC121{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:50 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101130z,FLOOD,GAC117,GAC121{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:34:51 EST 2024 error parsing NWS zone message "}KB2EAR-13>APDW16,WIDE2-2,qAR,KD2CIF-1::NWS_WARN:110336z,Areal Flood,NJC005-007-015-021-PAC017-029-045-091-101{A4p00" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=Areal Flood WARN
Tue Jan 09 18:34:51 EST 2024 error parsing NWS zone message "}KB2EAR-13>APDW16,WIDE2-2,qAR,KD2CIF-1::NWS_WARN:110336z,Areal Flood,NJC005-007-015-021-PAC017-029-045-091-101{A4p00" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=Areal Flood WARN
Tue Jan 09 18:34:53 EST 2024 error parsing NWS zone message "}WG3K-15>APMI06,N3KTX-7,MD2*,qAR,WG3K-15:LWXFLS>APRS,TCPIP,WG3K-15*::NWS-WARN:101030z,FLOOD,WVC065{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}GSPFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,FLASH_FLOOD,NCC003,NCC035{J00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}CHSFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101500z,FLOOD,SCC015,SCC043,SCC089{d10AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}CHSFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101500z,FLOOD,SCC015,SCC043,SCC089{d10AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}JANFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100400z,FLOOD,MSC067{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}JANFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100400z,FLOOD,MSC067{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RLXFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100030z,FLOOD,VAC027,VAC051{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RLXFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100030z,FLOOD,VAC027,VAC051{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100545z,FLOOD,GAC117{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101200z,FLOOD,NCC005,NCC009,NCC171,NCC189,NCC193,NCC197{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101200z,FLOOD,NCC005,NCC009,NCC171,NCC189,NCC193,NCC197{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS-WARN:100945z,FLOOD,GAC021,GAC153,GAC169,GAC207,GAC289{V00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}FFCFLS>APRS,qAO,AE5PL-WX::NWS_WARN:100945z,FLOOD,GAC021,GAC153,GAC169,GAC207,GAC289{V00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RAHSVR>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,SVR_STORM,NCC051,NCC085,NCC101,NCC163,NCC183{O00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RAHSVR>APRS,qAO,AE5PL-WX::NWS_WARN:100000z,SVR_STORM,NCC051,NCC085,NCC101,NCC163,NCC183{O00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RAHTOR>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,TORNADO,NCC101{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=TORNADO WARN
Tue Jan 09 18:35:51 EST 2024 error parsing NWS zone message "}RAHTOR>APRS,qAO,AE5PL-WX::NWS_WARN:100000z,TORNADO,NCC101{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=TORNADO WARN
Tue Jan 09 18:36:34 EST 2024 error parsing NWS zone message "}KB2EAR-13>APDW16,KC2GOW-1,WA2FPB-5*,qAR,KC2MDN-1::NWS_WARN:110629z,Flood,NJC023-035{A8s00" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=Flood WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100330z,FLASH_FLOOD,VAC007,VAC049,VAC111,VAC117,VAC135,VAC147{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100330z,FLASH_FLOOD,VAC007,VAC049,VAC111,VAC117,VAC135,VAC147{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101200z,FLOOD,NCC033,NCC157,NCC169,VAC009,VAC019,VAC023,VAC067,VAC089,VAC143,VAC163,VAC690{800AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101200z,FLOOD,NCC033,NCC157,NCC169,VAC009,VAC019,VAC023,VAC067,VAC089,VAC143,VAC163,VAC690{800AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101200z,FLOOD,VAC005,VAC017,VAC023,VAC163,VAC580,WVC025,WVC063,WVC089{A00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101200z,FLOOD,VAC005,VAC017,VAC023,VAC163,VAC580,WVC025,WVC063,WVC089{A00AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100100z,FLASH_FLOOD,VAC007,VAC111,VAC135,VAC147{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100100z,FLASH_FLOOD,VAC007,VAC111,VAC135,VAC147{300AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFFW>APRS,qAO,AE5PL-WX::NWS-WARN:100130z,FLASH_FLOOD,NCC033,NCC157,VAC143,VAC590{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFFW>APRS,qAO,AE5PL-WX::NWS_WARN:100130z,FLASH_FLOOD,NCC033,NCC157,VAC143,VAC590{400AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}TBWSVR>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,SVR_STORM,FLC015,FLC027,FLC071,FLC081,FLC115{800AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}TBWSVR>APRS,qAO,AE5PL-WX::NWS_WARN:100000z,SVR_STORM,FLC015,FLC027,FLC071,FLC081,FLC115{800AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100415z,FLASH_FLOOD,VAC007,VAC041,VAC049,VAC075,VAC085,VAC087,VAC109,VAC145{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}AKQFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100415z,FLASH_FLOOD,VAC007,VAC041,VAC049,VAC075,VAC085,VAC087,VAC109,VAC145{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFFS>APRS,qAO,AE5PL-WX::NWS-WARN:100100z,FLASH_FLOOD,NCC157,NCC169,VAC089,VAC141,VAC690{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}RNKFFS>APRS,qAO,AE5PL-WX::NWS_WARN:100100z,FLASH_FLOOD,NCC157,NCC169,VAC089,VAC141,VAC690{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLASH_FLOOD WARN
Tue Jan 09 18:36:50 EST 2024 error parsing NWS zone message "}MRXFLS>APRS,qAO,AE5PL-WX::NWS-WARN:101215z,FLOOD,TNC029{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:51 EST 2024 error parsing NWS zone message "}MRXFLS>APRS,qAO,AE5PL-WX::NWS_WARN:101215z,FLOOD,TNC029{100AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=FLOOD WARN
Tue Jan 09 18:36:51 EST 2024 error parsing NWS zone message "}MHXSVR>APRS,qAO,AE5PL-WX::NWS-WARN:092345z,SVR_STORM,NCC031,NCC049,NCC103,NCC133{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:36:51 EST 2024 error parsing NWS zone message "}MHXSVR>APRS,qAO,AE5PL-WX::NWS_WARN:092345z,SVR_STORM,NCC031,NCC049,NCC103,NCC133{200AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=SVR_STORM WARN
Tue Jan 09 18:36:51 EST 2024 error parsing NWS zone message "}RAHTOR>APRS,qAO,AE5PL-WX::NWS-WARN:100000z,TORNADO,NCC101{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=TORNADO WARN
Tue Jan 09 18:36:51 EST 2024 error parsing NWS zone message "}RAHTOR>APRS,qAO,AE5PL-WX::NWS_WARN:100000z,TORNADO,NCC101{500AA" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=TORNADO WARN
Tue Jan 09 18:36:52 EST 2024 error parsing NWS zone message "}KB2EAR-13>APDW16,KB2EAR-1*,WIDE2-1,qAR,N2HRJ-10::NWS_WARN:101845z,Flood,NJC021{A4A00" :java.lang.UnsupportedOperationException: unknown zoneType='C' for advisory type=Flood WARN
Re: YAAC and AIS-Catcher?

 

¿ªÔÆÌåÓý

Unfortunately, the way you're hooked up won't work. The External Message Source port type is for transmitting proper APRS packets originated by a script on the same computer as YAAC, and your !AIVDM packets don't comply with the APRS specification.

What you need to do is also install the marineports plugin, which supports NMEA-0183 over TCP/IP, and connect a port of that type to your AIS-Catcher.

Then see if the combination of both plugins works.

Hope this helps.

Andrew, KA2DDO
author of YAAC

From: [email protected] <[email protected]> on behalf of Jeremy N2UGS <jmedinac@...>
Sent: Monday, January 8, 2024 8:15:31 PM

Thank you for adding AIS-Catcher to the plugin! Though I am still having issues with YAAC reading the messages. I have it set up through an External source port.

This is the error received from YAAC :

ExtMsgSrc unable to parse line !AIVDM,1,1,,B,ENkaSQLHh@@@@@@@@@@@@@@@@@@=;I<E<@lMh00003vP000,2*6E
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

Below is a screen shot of the port setup:



I guess my question is what is the proper way to import the messages from AIS-Catcher into YAAC? I may be doing this completely the wrong way...

Best Regards

Jeremy N2UGS
Re: YAAC and AIS-Catcher?

 

Just to confirm the version numbers...
Re: YAAC and AIS-Catcher?

 

Thank you for adding AIS-Catcher to the plugin! Though I am still having issues with YAAC reading the messages. I have it set up through an External source port.

This is the error received from YAAC :

ExtMsgSrc unable to parse line !AIVDM,1,1,,B,ENkaSQLHh@@@@@@@@@@@@@@@@@@=;I<E<@lMh00003vP000,2*6E
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

Below is a screen shot of the port setup:



I guess my question is what is the proper way to import the messages from AIS-Catcher into YAAC? I may be doing this completely the wrong way...

Best Regards

Jeremy N2UGS

?
Re: QRU server timing issues

 

Thanks for reaching with suggestions and questions.? here is a bit more info on the setup.

I have been running this exercise on a non standard ARPS frequency to cut down on the noise.

There are no digipeters in the mix.? I have a radio connected to a Rasperrypi running Direwolf and YAAC.? YAAC is talking to Direwolf as the TNC via KISS over IP.? in the logs as W2KP-4

I am sending QRU message from Yaesu FT2D as KI7YRY-1 in the logs

Below are the logs that I captured that show the miss I originally described.? I have tried to explain what was happening I hope it makes sense.

You can see yaac logs
23:22:33 are the original object announcements? These were sent and seen
23:23:33 are the original object announcements? These were sent and seen
23:22:53 beacon from test handheld with position report

23:23:51 First QRU message sent and heard by yaac
23:23:51 object packet sent out

in the direwolf logs starting at 23:23:51
23:23:51 message in from client
23:23:51 ack from yaac back to clent
23:23:52 object sent out
23:23:52 summary message sent out to client

23:24:37 random beacon from YAAC out.

Second test

yaac raw packets
23:24:39 QRU from client
23:24:39 obj sent from YAAC

Direwolf logs
23:24:39 QRU packet
23:24:39 ACK


???? Never see the OBJ packet seen in yaac logs at 23:24:39 in the Direwolf logs.



Direwolf Logs:
KI7YRY-1 audio level = 27(6/7) ? ?||||||___
[0.2 23:23:51] KI7YRY-1>APY02D,WIDE1-1,WIDE2-1::QRU ? ? ?:RACE{11<0x0d>
The APRS protocol specification says nothing about a possible carriage return after the
message id.? Adding CR might prevent proper interoperability with with other applications.
APRS Message, number "11", from "KI7YRY-1" to "QRU", Yaesu FT2D series
RACE
[0L 23:23:51] QRU>APJYC1::KI7YRY-1 :ack11
[0L 23:23:52] W2KP-4>APJYC1,WIDE1-1,NOGATE,RFONLY:;obj3 ? ? *062233h3334.82N\11157.06W!bj3
[0L 23:23:52] QRU>APJYC1::KI7YRY-1 :Sent 1 RACE Objects Max 1 de W2KP-4
[0L 23:24:37] W2KP-4>SSSTXR,WIDE1-1,WIDE2-1:`'Rul s//"8R} Truck Pi<0x0d>


KI7YRY-1 audio level = 26(6/6) ? ?||||||___
[0.2 23:24:39] KI7YRY-1>APY02D,WIDE1-1,WIDE2-1::QRU ? ? ?:RACE{12<0x0d>
The APRS protocol specification says nothing about a possible carriage return after the
message id.? Adding CR might prevent proper interoperability with with other applications.
APRS Message, number "12", from "KI7YRY-1" to "QRU", Yaesu FT2D series
RACE
[0L 23:24:39] QRU>APJYC1::KI7YRY-1 :ack12

YAAC raw packet log:

image.png


On Fri, Jan 5, 2024 at 6:20?PM Andrew P. <andrewemt@...> wrote:
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 ¨C W2KP
721 - 740 of 2944