Hi, for some reason aprs.fi has starting to report my beacon time as 30 mins later than my local time. I have been looking for a cause but have been unable to find the solution. It happened more or less overnight without making any changes to the configuration of YAAC. Any clues how to fix this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, for some reason aprs.fi has starting to report my beacon time as 30
mins later than my local time. I have been looking for a cause but have
been unable to find the solution. It happened more or less overnight
without making any changes to the configuration of YAAC. Any clues how to
fix this?
Hi Andrew, I believe there are some KPC-3 devices around but there was no
delay. I watched my beacon going out and a few seconds later the aprs.fi
time stamp would appear indicating a time 30 mins ahead of my local time.
It lasted from 36 to 48 hrs after which it rectified itself (!) and
indicated the correct time again. Bit of a mystery :)
Hi, for some reason aprs.fi has starting to report my beacon time as 30 mins later than my local time. I have been looking for a cause but have been unable to find the solution. It happened more or less overnight without making any changes to the configuration of YAAC. Any clues how to fix this?
After some 48 hrs the faulty time stamp has been repaired. The problem must
have been external to my system :)
On Mon, 25 Nov 2019 at 12:41, Rein Mann reica@users.sourceforge.net wrote:
Problem solved itself after 48hrs,,...external fault?
Could be the infamous KPC-3+ time delay "feature", where it sits on a packet for half an hour before transmitting it.
Any KPC-3 digipeaters in your area that you're being relayed through?
Hi Andrew, I believe there are some KPC-3 devices around but there was no
delay. I watched my beacon going out and a few seconds later the aprs.fi
time stamp would appear indicating a time 30 mins ahead of my local time.
It lasted from 36 to 48 hrs after which it rectified itself (!) and
indicated the correct time again. Bit of a mystery :)
On Wed, 27 Nov 2019 at 07:34, Andrew Pavlin apavlin@users.sourceforge.net
wrote: