Issue with SavvyCAN timestamps when log timestamps hit midnight

[jonnyspizza]

Hi there, I'm a new user of SavvyCAN with a CSS Electronics CL2000 logger, thanks for building such a great tool! I've got a strange issue with timestamps when importing logs into SavvyCAN. I'm in Australia with a CL2000 device that is configured in UTC time, which means a normal morning drive will start at 10-11pm device time (UTC) and carry on into the next day. It seems like SavvyCAN doesn't like it when the time wraps back around to midnight as the timestamp that SavvyCAN applies blows up (into the year 2160!). Below are some relevant screenshots. The raw CAN log originally included the date in the timestamp in the format YYYYMMDDThhmmsskkk but I manually removed the date in the hope that this would fix the problem, but it didn't change SavvyCAN's behaviour.

This behaviour means that graphs do not show correctly as the time axis is very wrong, and data exported from graphs (which is the method of data export that I've found works best for me) also doesn't work properly. So very keen for a fix for this.

Original raw CAN log with timestamps

SavvyCAN timestamps with "milliseconds" Time Keeping option

SavvyCAN timestamps with "system clock" Time Keeping option

Thanks!