¿ªÔÆÌåÓý

  1. Direwolf
  2. Topics

Question on APRS error messages

 

Hello All!
?
I am seeing the following error messages regarding bad APRS packet segments, but? these are from packet stations and are valid. Is there anyway to turn off, or adjust, APRS error messages?
?
?


[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0] N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the destination field is obsolete. ?You can help to improve the quality of APRS signals.
Tell the sender (N6CTA-7) to use the proper product identifier from https://github.com/aprsorg/aprs-deviceid?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place as BEACON. For example if one station is contacting another.? XXXX>KXXXX-1 there is a message that comes up and says that K is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
?
 

¿ªÔÆÌåÓý


Hello Chris,

Is your packet station on an APRS frequency or a BBS frequency?? If you want to disable the APRS packet repair heuristics, you can add the following "ax25" parameter to your direwolf.conf file:

?? FIX_BITS 0 AX25

Please note that you might want to actually ENABLE the FIX_BITS feature (changing the "0" parameter to one of the valid higher numbers) to improve weak packet decoding at the risk of some incorrect decodes.? See the Direwolf User Manual for more detail.

--David
KI6ZHD





On 12/04/2024 05:29 PM, Christopher Molnar KO4YAW via groups.io wrote:

Hello All!
?
I am seeing the following error messages regarding bad APRS packet segments, but? these are from packet stations and are valid. Is there anyway to turn off, or adjust, APRS error messages?
?
?


[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0] N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the destination field is obsolete. ?You can help to improve the quality of APRS signals.
Tell the sender (N6CTA-7) to use the proper product identifier from ?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place as BEACON. For example if one station is contacting another.? XXXX>KXXXX-1 there is a message that comes up and says that K is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
?
 

Thanks David!
?
I am on an HF BBS frequency. Thanks for the suggestion and I am going to have to dig out the most recent manual and take a look.
?
-Chris
?
On Wed, Dec 4, 2024 at 09:16 PM, David Ranch wrote:


Hello Chris,

Is your packet station on an APRS frequency or a BBS frequency?? If you want to disable the APRS packet repair heuristics, you can add the following "ax25" parameter to your direwolf.conf file:

?? FIX_BITS 0 AX25

Please note that you might want to actually ENABLE the FIX_BITS feature (changing the "0" parameter to one of the valid higher numbers) to improve weak packet decoding at the risk of some incorrect decodes.? See the Direwolf User Manual for more detail.

--David
KI6ZHD





On 12/04/2024 05:29 PM, Christopher Molnar KO4YAW via groups.io wrote:
Hello All!
?
I am seeing the following error messages regarding bad APRS packet segments, but? these are from packet stations and are valid. Is there anyway to turn off, or adjust, APRS error messages?
?
?


[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0] N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the destination field is obsolete. ?You can help to improve the quality of APRS signals.
Tell the sender (N6CTA-7) to use the proper product identifier from ?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place as BEACON. For example if one station is contacting another.? XXXX>KXXXX-1 there is a message that comes up and says that K is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
?
?
 

Hi Chris,

If you are on a BBS frequency, then you may wish to disable APRS decoding completely. You can do this with the direwolf commandline option " -q d " (be quiet about decoding APRS).

73,
Thomas
KK6FPP
 

¿ªÔÆÌåÓý


I think Thomas's response is actually the correct solution to stop PRINTING these errors on the console.? My answer really only impacts the BIT_FIX feature.? Sorry for the noise.

--David
KI6ZHD


On 12/04/2024 09:26 PM, Thomas Leibold via groups.io wrote:

Hi Chris,

If you are on a BBS frequency, then you may wish to disable APRS decoding completely. You can do this with the direwolf commandline option " -q d " (be quiet about decoding APRS).

73,
Thomas
KK6FPP

1 - 5 of 5