Rein Mann

Hi Andrew. Problem solved. The open jdk version of Debian 10 (for arm) is version 11. This has to be installed with 'default-jdk' :)

The standard debian on raspi 4 is 32 bit. The version I have is 64bit. I have not been able to find a Java jdk version . I tried to install a version 15 from the Java site but failed. The Ubuntu 20.04 and 20.10 distros did not present any issues. Thanks for you quick response. On Mon, 14 Dec 2020 at 13:57, Andrew Pavlin apavlin@users.sourceforge.net wrote: You're not using standard Raspbian? Are there any versions of OpenJDK (from Java release 8 to 15) available in your distro's repository? java...

I am running 64bit Debian 10 on raspberry 4. I have sofar been unable to find a java jdk version that will install. Has anyone found a solution for this problem ? Rein vk4alj

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: Could be the infamous KPC-3+ time delay "feature", where it sits on a packet...

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: 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? aprs.fi time reporting...

Problem solved itself after 48hrs,,...external fault?

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?

Thanks Andrew for this clear explanation...very useful!