¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Astronomical clock weird behaviour


 

However I set the ¡°Format¡± parameter in the aclock symbol, it is giving me the same Morning-Hour/Min analog outputs and what¡¯s more, those outputs are out by an hour. ¡°Actual¡± sunrise tomorrow is, for example, 5.01, but the output is 6.01, irrespective of the Format.

I am using the clock driver with DST (on an RMC3) and it is correctly showing that we are currently in DST and the Lat/Long/East/West parameters are correct as is the system time being used as input to the aclock.

Can anyone enlighten me as to the inventive way I have managed to screw up?


 

This is a known issue with 3-series processors (only 3-series) that's been discussed with TBS since November 2017 and was confirmed in April 2018 (able to replicate).
I haven't followed it closely since but haven't seen anything in recent software releases which would make me believe it was solved.?