[aprssig] Peculiar APRS data

[AE5PL Lists]

You have a poorly configured digipeater in the area which is holding the
digipeat and causing excessive delays in the repeating of packets.
Quite often, this is caused by a D700 configured.  Here is a
time-stamped printout:

1/12/2005 06:09 KD5YOU>RY4R3R,RELAY*,WIDE2-2,qAo,K5WH:`{:bq>H>/"4)}FBEOC
#4662 
1/12/2005 06:25
KD5YOU>RY4R8P,AI5TX-2*,WIDE2-2,qAo,KD5CFM:`{4Cl"u>/"3y}FBEOC #4662 
1/12/2005 06:52
KD5YOU>RY4R8P,AI5TX-2*,WIDE2-2,qAo,K5MBH-3:`{4Cl"u>/"3y}FBEOC #4662 
1/12/2005 06:53
KD5YOU>RY3S7V,RELAY,WIDE2-2,qAo,KD5CFM:`{E:l@|>/"4)}FBEOC #4662 
1/12/2005 07:01
KD5YOU>RY3V0Y,RELAY,WIDE2-2,qAo,KD5CFM:`{E$l"]>/"4"}FBEOC #4662 
1/12/2005 08:24
KD5YOU>RY4R8P,AI5TX-2*,WIDE2,qAo,K5MBH-3:`{4Cl"u>/"3y}FBEOC #4662

There is almost a 2 hour delay (beats the worst I have seen with is a
D700 which was 35 minutes).  Note, also, that there is almost a 30
minute delay between your packet being gated by KD5CFM and your packet
being gated by K5MBH-3.  Another possibility is someone replaying logs
on an out-of-date Xastir (Curt fixed this bug a couple of months back)
(K5MBH-3 is UI-View).  Looking at K5MBH-3's packets over the past hour,
there are a number of 30+ second delays with packets he is transmitting
which indicates that there may also be a digipeater in the area which is
improperly configured and has persistence <> 255 and slottime <> 0.

This is why it is important that digipeaters do not "buffer" packets.
As Bob has stated many times, set digipeater persistence=255 and
slottime=0 so they digipeat immediately when the frequency becomes
clear.

73,

Pete Loveall AE5PL
mailto:pete at ae5pl.net 

> -----Original Message-----
> From: John Denison
> Posted At: Wednesday, January 12, 2005 3:02 AM
> Subject: [aprssig] Peculiar APRS data
> 
> but I've been 27 miles away for over two hours. I know that 
> if you no longer transmit or if your signal isn't heard, then 
> the last position is displayed, but this isn't the case. The 
> data seems to be out of order.