K2 shuts down for no reason/at random

OP
D

DesertBike

Active Member
Joined
Jun 27, 2018
Messages
257
Reaction score
144
Country
United States
there's no GPS tracking in DVPlayer unless it's registered so that's the expected result
That being the case I don't see any point in trying to use DVPlayer to diagnose the GPS weirdness.
 

OCD Tronic

Well-Known Member
Retailer
Joined
Nov 5, 2016
Messages
1,122
Reaction score
906
Location
Carson City, Nevada (USA)
Country
United States
Dash Cam
VIOFO, GitUp, INNOVV, QVIA, GUARD TRAK + More on Amazon.com
Video samples received, I'm passing them on to the dashcamviewer.com developer to help correct GPS data interpretation further.
 

traveler

Well-Known Member
App Developer
Joined
Jan 17, 2014
Messages
403
Reaction score
738
Location
Orange County, CA
Country
United States
Dash Cam
Viofo A119V2, SG9665GC, SG9663DCPro + many more
Video samples received, I'm passing them on to the dashcamviewer.com developer to help correct GPS data interpretation further.

Mystery solved I think:

I received and examined the problematic @DesertBike video files. There were 6 consecutive videos and each video is 1 minute long. The first video was filmed entirely inside an enclosed garage, as were the first 16 seconds of the 2nd video.

The first 3 videos had "0.00" for lat/lon throughout the entire course of the video. The fourth video starting picking up GPS at 52 seconds. The sixth video had GPS lock the entire time.

So a GPS lock wasn't obtained by the dashcam for the first 3m52s (1m16s of which were inside the garage). This means your GPS lock required 2m36, which is lengthy, but not unusual (especially for a cold start). Best to let your dashcam sit for a few minutes before riding, especially if it hasn't been out for a while.

John

Website: http://dashcamviewer.com
Facebook: https://www.facebook.com/dashcamviewer
 
OP
D

DesertBike

Active Member
Joined
Jun 27, 2018
Messages
257
Reaction score
144
Country
United States
What about the part where position is offset, about 4m 40s into the trip? Timestamp is 17:18:23, in the clip that starts at 17:17:43.

This is what I see in DV:



The curvy piece at the bottom of the snapshot follows some streets that are actually a few blocks north of where the path is shown. If one were to cut out the incorrect point(s) on that long straight yellow bit, the path overall would be correct.
 

traveler

Well-Known Member
App Developer
Joined
Jan 17, 2014
Messages
403
Reaction score
738
Location
Orange County, CA
Country
United States
Dash Cam
Viofo A119V2, SG9665GC, SG9663DCPro + many more
What about the part where position is offset, about 4m 40s into the trip? Timestamp is 17:18:23, in the clip that starts at 17:17:43.

The curvy piece at the bottom of the snapshot follows some streets that are actually a few blocks north of where the path is shown. If one were to cut out the incorrect point(s) on that long straight yellow bit, the path overall would be correct.

Ah, sorry I missed that. Yes, it looks like there's a problem with the latitude values in the 5th video up until point 41. Here's a snapshot of the raw GPS data embedded in that MP4 (red=bad lat, green=good lat). It appears that at point 41 the latitude suddenly jumps to the correct position. My guess is that a complete GPS lock wasn't achieved until that point, and the GPS unit just spewed out approximate position data until then.

pt: 37, time: 1599002255
pt: 37, lat: 35.057533, lon: -106.524689
pt: 38, time: 1599002256
pt: 38, lat: 35.057453, lon: -106.524757
pt: 39, time: 1599002257
pt: 39, lat: 35.057373, lon: -106.524803
pt: 40, time: 1599002258
pt: 40, lat: 35.057278, lon: -106.524872

pt: 41, time: 1599002259
pt: 41, lat: 35.059532, lon: -106.523766
pt: 42, time: 1599002260
pt: 42, lat: 35.059429, lon: -106.523811
pt: 43, time: 1599002261
pt: 43, lat: 35.059322, lon: -106.523857
pt: 44, time: 1599002262
pt: 44, lat: 35.059212, lon: -106.523911
 
Top