Hi All,
I have just purchased the mini 0806, which I find to be a great little dashcam.
I have one issue with the gps log data.
Shortly after the gps signal is locked, the timestamp in the gps log file skips some hours.
It doesn't affect the timestamp of files or the clock stamped on the video. It only shows in the log, which throws the dashcam viewer application I am using off for the first clip where the gps lock is acquired.
Excerpt from the log:
V,170316,153159.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,153200.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,153201.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+10.41,-01.84;
V,170316,153201.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,173851.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84; <-- point 32: 2h6m50s skip!
V,170316,173852.000,5535.9087,N,01208.4815,E,000.0,95.2M,-02.45,+09.80,-02.45;
V,170316,173853.000,5535.9087,N,01208.4815,E,000.0,95.2M,-02.45,+09.80,-01.84;
It is probably some time correction going on, because it happens shortly after the gps has locked on, and the time in the log actually looks correct after the skip.
In the cam menu I have set the time to my local time and timezone to +1 as I am in GMT+1, and the time after the correction looks like GMT time at the time of recording, so I guess that is correct.
Is this normal behavior for the mini0806 to be so much off before gps lock? Or have I set something incorrectly?
Again, I believe I have set the time correct in the settings as the time stamped on the video is correct.
I am running stock firmware (V1.0) on it, so perhaps a firmware update will fix it, which leads me to another question. Which firmware release is the latest stable one?
On mini0806.com I see a lot of releases where it is stated they are for testing.
Any suggestions/feedback is appreciated.
I have just purchased the mini 0806, which I find to be a great little dashcam.
I have one issue with the gps log data.
Shortly after the gps signal is locked, the timestamp in the gps log file skips some hours.
It doesn't affect the timestamp of files or the clock stamped on the video. It only shows in the log, which throws the dashcam viewer application I am using off for the first clip where the gps lock is acquired.
Excerpt from the log:
V,170316,153159.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,153200.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,153201.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+10.41,-01.84;
V,170316,153201.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84;
V,170316,173851.000,5535.9087,N,01208.4815,E,000.0,95.2M,-01.84,+09.80,-01.84; <-- point 32: 2h6m50s skip!
V,170316,173852.000,5535.9087,N,01208.4815,E,000.0,95.2M,-02.45,+09.80,-02.45;
V,170316,173853.000,5535.9087,N,01208.4815,E,000.0,95.2M,-02.45,+09.80,-01.84;
It is probably some time correction going on, because it happens shortly after the gps has locked on, and the time in the log actually looks correct after the skip.
In the cam menu I have set the time to my local time and timezone to +1 as I am in GMT+1, and the time after the correction looks like GMT time at the time of recording, so I guess that is correct.
Is this normal behavior for the mini0806 to be so much off before gps lock? Or have I set something incorrectly?
Again, I believe I have set the time correct in the settings as the time stamped on the video is correct.
I am running stock firmware (V1.0) on it, so perhaps a firmware update will fix it, which leads me to another question. Which firmware release is the latest stable one?
On mini0806.com I see a lot of releases where it is stated they are for testing.
Any suggestions/feedback is appreciated.