During testing of SRS and implementing conversion to UNIX Timestamp, I found some path of syncing the OBC time to be 'unreliable'. There are Values which do sync to incorrect offsets:
e.g. when using "t 19700101 000000" -> should generate a UNIX time with very low number -> but does generate UNIX time on 2.1.1970 !? (using "t 19700101 001000" -> seems to work correct and shows 1.1.1970 00:10:00!
There was a bug by not storing the Year in all path of syncing (not used for TLE at all, but very confusing not to have!)
at this moment there are 2 code places where leap Years are generated -> unify
The situation that reset occures shortly before Midnight and especially before 31.12.20xx 23:59:59 should be considered correctly ->I think the year, day of year and day of month could cause problems here!!!!
-> make more (automated!?) tests to show all path are good !!!!
During testing of SRS and implementing conversion to UNIX Timestamp, I found some path of syncing the OBC time to be 'unreliable'. There are Values which do sync to incorrect offsets:
-> make more (automated!?) tests to show all path are good !!!!