¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. APRSISCE
  2. Topics

Undefined NWS messages?

 

With the new Development version, I have noticed a peculiar problem. When I receive a NWS warning object over IS, APRSIS32 commands the D710 to transmit the respective messages as follows:
?
K4VBX>APK102,WIDE1-1,WIDE2-1::AKQFFS ? :rej0
K4VBX>APK102,WIDE1-1,WIDE2-1::AKQSMW ? :rej0
?
I have restarted the program without activating the IGate, and it still does this. I have tried disabling messages in the IS port and the RF port, but this makes no difference. I do not see the packets in the Igate Test Filter. Strangely they are not in the Transmit log either. However, the TOCALL tells me something is commanding the D710 to create the packet, and I am connected to the D710 in APRS mode. To be sure, I disabled all digipeat options on my D710. Running several logs actively to try to narrow this down. Any thoughts?
 

On further inspection, this is not an APRSIS32 problem. I realize this a message rejection. However, it is a new observation that the NWS message warnings are requesting ACK.
Lynn Deffenbaugh
 

¿ªÔÆÌåÓý

Someone is directing messages FROM AKQFFS and AKQSMW directly TO K4VBX and your receive message buffer in the radio is full, so the radio is answering with a reject.?? Check the radio's messages list and you should see those NWS message sources listed.

What is your IGate's callsign-SSID?

Check your FilterTest log if you are using custom filters to gate these weather packets from -IS to RF.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.?? Nothing has changed in this area in a LONG time so it likely has nothing to do with the latest Development version.

On 7/20/2024 5:35 PM, peter.anoia@... wrote:

With the new Development version, I have noticed a peculiar problem. When I receive a NWS warning object over IS, APRSIS32 commands the D710 to transmit the respective messages as follows:
?
K4VBX>APK102,WIDE1-1,WIDE2-1::AKQFFS ? :rej0
K4VBX>APK102,WIDE1-1,WIDE2-1::AKQSMW ? :rej0
?
I have restarted the program without activating the IGate, and it still does this. I have tried disabling messages in the IS port and the RF port, but this makes no difference. I do not see the packets in the Igate Test Filter. Strangely they are not in the Transmit log either. However, the TOCALL tells me something is commanding the D710 to create the packet, and I am connected to the D710 in APRS mode. To be sure, I disabled all digipeat options on my D710. Running several logs actively to try to narrow this down. Any thoughts?
 

Yes, that seems to be the new development (little d). Currently working with the station that is gating the NWS traffic to resolve it (in Direwolf). Multiple clients in the area are responding to the ACK request, so there is a lot of QRM, especially with multiple alerts active.

1 - 4 of 4