[Mut@nt] HD51 Timer Problem

[Spoof]

Just to update:

My box is set to "transponder time" (default).
I have gone back to 6.0.006 and the same timers (restored from settings) work perfectly.

 

[Spoof]

This problem persists in 6.2.102

In the timer log, I get this entry:
Mon 30 May 2022 14:45 - record time chnged, start prepare is now Tue May 31... < CORRECT
Wed 1 Jun 2022 05:32 - record time chnged, start prepare is now : Wed Jun 1..... < ROGUE

The box was booted at 08:15, May 31, if that helps, so not sure where the 05:32 comes form.

This seems to happen overnight, booting from a deep standby.

 

[Joe_90]

We've been testing and have discovered an issue with NTP time during startup which can cause the clock to jump forward temporarily even if you have "time by transponder" set. The software has been changed and tested and I would expect that there will be a Release version available shortly.

 

[Huevos]

Wthere will be a Release version available shortly.

Yesterday.

 

[Joe_90]

This problem persists in 6.2.102

In the timer log, I get this entry:
Mon 30 May 2022 14:45 - record time chnged, start prepare is now Tue May 31... < CORRECT
Wed 1 Jun 2022 05:32 - record time chnged, start prepare is now : Wed Jun 1..... < ROGUE

The box was booted at 08:15, May 31, if that helps, so not sure where the 05:32 comes form.

This seems to happen overnight, booting from a deep standby.

Sorry - missed the fact that 6.2.002 was released yesterday

@Spoof - can you confirm that you updated/flashed 6.2.002 (your post says 6.2.102). If so, the time problem should definitely have been fixed. You need to turn on debug logs and attach them.

 

[Spoof]

Apologies, I am indeed now on 6.2.002 and had the problem this morning.
So will collect logs and post (assuming the problem repeats itself tomorrow morning).

Edit: debug logs already enabled but the log manager is empty.

 

[twol]

Apologies, I am indeed now on 6.2.002 and had the problem this morning.
So will collect logs and post (assuming the problem repeats itself tomorrow morning).

Edit: debug logs already enabled but the log manager is empty.

If logs are enabled… turn them off, take the reboot then enable and restart…should have debug log …. make sure that you have saved other than in flash

 

[Spoof]

After a few days of monitoring this, it seems the bug was indeed squashed!
Thanks to all for your help.