GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Hi all:

I tell you my little contribution on the subject:

I have carried out the tests as it says to the companion Alfred_ML in a device One of chip GL1, changing the values ​​that comments in the file ee_meta.txt 1924909261 (Tue, 31 Dec 2030 01:01:01 GMT) and the result of the hour , it is always the same: 0.00

I have made many more changes even I have placed the values ​​of the year 2101: 4133984461 Sat, 01 Jan 2101 01:01:01 GMT and also continues with the same problem of the time: 0.00.

I think we should study this gltt file, in case my help is useful, since I have accessed several of those files, and although they all have the same weight, of 877 KBs, the internal content between them is quite different.

As for the hexadecimal lines, comment that I do not dominate any of it, but I think, that there must be the problem. Let's see if between all we can find the solution.

Comment also that I have done different tests with DSA navcores generated by me, and the result always and with all, has been the same.

[Login or Register to remove this advertisement]

For any questions or help, you have me HERE

Translated with the help of google translator

regards

beraun Reviewed by beraun on 8th May 2019. GPS Week Number Rollover [WNRO] JUST Findings, Fixes, and Frustrations Let's keep this new topic JUST for what we see AFTER the "magic" end-of-the-world WNRO on Sunday 07-Apr-19 morning. If you do post anything here; good, bad or indifferent and/or any successful workarounds, then please remember to tell us which device and navcore you're using to get these findings so it may help others. thankyou Rating: 5