doc:appunti:hardware:gps_logger_i_blue_747
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:hardware:gps_logger_i_blue_747 [2019/10/10 20:39] – [MTKBabel] niccolo | doc:appunti:hardware:gps_logger_i_blue_747 [2019/10/11 15:47] (current) – [Week Rollover Bug] niccolo | ||
---|---|---|---|
Line 65: | Line 65: | ||
If you encounter some problems, please run the program with the '' | If you encounter some problems, please run the program with the '' | ||
- | ===== Week Rollover Bug ===== | + | ===== Weeks Rollover Bug ===== |
- | It turned out that several GPS based on the MTK chipset are affected by a **Week Rollover Bug**. You discover that your device is affected by the bug because the GPX you save from it, will have a **timestamp badly in the past**. | + | It turned out that several GPS based on the MTK chipset are affected by a **Weeks Rollover Bug**. You discover that your device is affected by the bug because the GPX files you save from it, will have a **timestamp badly in the past**. |
- | Actually I have two i-Blue 747 GPS data loggers. The older one is **Model ID 001B**, which has already manifested the problem: today is **2019-10-10**, | + | Actually I have two i-Blue 747 GPS data loggers. The older one is a **Model ID 001B**, which has already manifested the problem: today is **2019-10-10**, |
- | ==== Credits ==== | + | The other logger of mine is a **Model ID 001D**, which instead is still recording correct timestamps today. I suspect that the weeks counter is nevertheless 10 bits, and just the hard-coded EPOCH is more recent. So the bug is **just to come in the near future**. |
+ | |||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | ===== Credits | ||
I wish to thank all the people behind the **[[http:// | I wish to thank all the people behind the **[[http:// |
doc/appunti/hardware/gps_logger_i_blue_747.1570739974.txt.gz · Last modified: 2019/10/10 20:39 by niccolo