Hi Henrik,

Quite a bit to digest there. Good food for thought. Thanks.

I missed the fact that the custom characters for the medium digits was constantly loading in the loop. I've moved that to the beginning now out of the loop, it is loaded at start up.

The BigDigit clock did only load it's characters once then entered it's own loop, so that's taken care of.


The main problem as I see it is that the gps string start occurs at the same time as the 'seconds' rise point. In the gps module the start of the rise of the PPS also triggers the NMEA string output. In other words the seconds epoch occurs for both. I don't know if it's possible to receive the string and trigger the display code at the same time. I was just trying to get to a more accurate time.

The time is very close now anyway allowing for code run timing. I could add a small pause to bring it closer I suppose.