Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

lock to road not work in 8.00

pabelleira
over 5 years ago 
With the 8.00 firmware, this option has stopped working correctly. Here is an example: 

The first image is with version 8.00 an 'lock to road' activated. The track seems to want to follow all the deviations it finds. 

The second is with 8.00 and the option deactivated: the track is correct. 

The third one is recorded with 7.30 and the option activated: the track is correct, it focuses on the road that I am really following, it does not go by detours. 

The first two are round trip, the third only one way.

  • 0 over 5 years ago

    "Lock on road" used to just change the display of the track (not the data).

    It appears that changed (presumably, it's a bug).

    It doesn't seem that useful to have it enabled.

  • 0 over 5 years ago in reply to dpawlyk 
    The data does change. The utility is in if you do road cycling, the result of the track improves by eliminating the "imperfections" of the GPS (several meters deviations depending on the GPS coverage)
  • 0 over 5 years ago in reply to pabelleira

    I misunderstood what was going on.

    Changing the data would mess up your distance.

    The device should record your actual track.Not some imaginary ride you didn't actually do.

    The historic/standard behavior of the Garmins was to have "lock on road" to only effect the display.

    So, it was broken before and 8.0 restores the standard behavior.

    =============

    This post appears to describe the opposite behavior (part of why I was confused).

    https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/192693/edge-1030-records-where-it-thinks-you-rode-not-where-you-actually-rode-worse-since-firmware-8-0-0-update

    Maybe, you two should swap units.

  • 0 over 5 years ago in reply to dpawlyk 
    It seems to me that we are not understanding each other.

The images I put correspond to the same route. 
    The first and third with 'lock to road' activated (firmwares 8.00 and 7.30).

As you can see, in the recording with 8.00, 
    the track goes where it feels like it, it doesn't really follow the route taken. 
    It is as if he wanted to leave for every detour of the road he finds.

    The correct operation is the third, from 7.30. The generated track correctly follows the path taken, but "smoothing" the path.

    Therefore, version 8.00 does not correct anything, but instead puts a new bug.


    You says:

    "Maybe, you two should swap units"

No. All units (with version 8.00) work the same. All with the same bugs. 
    Yes, yours too.
  • 0 over 5 years ago in reply to pabelleira

    As far as I know there is no "lock to road' functionality for GPS recording , if the track is bad , is something in GPS firmware/recording/implementation etc 

    For example if you will be in a area with poor GPS signal , , recording will be bad, but still it will display you on nearest road like the GPS will be good

    If I am wrong please correct me

  • 0 over 5 years ago in reply to krazyeone 
    No, it's not about that, I insist. I return to the example of the images.
The first one with 'lock to road "activated, the second deactivated. 
    As you can see what is recorded is different. 
    The correct one is the second one (and the third one, with 7.30). 
    With 8.00 and' lock to road" activated, a track that does not follow the actual route, 
    but deviations are invented (those that are found on the road), 
    and it is not a matter of GPS coverage, they are not deviations of a few meters 
    on the correct path, but a new path that is " invented " by the Edge
    Making assumptions of the deviations that I have taken. Notice that the lines that 
    leave the path are not "random" but follow other roads that intersect with 
    the one on which I was traveling
    . At no time have I left the general road, and ... you see what the Edge has generated. 
    Nor is it a matter of a specific path, but it is something completely repoducible. 
    All the records that I have made with 8.00 until I have noticed the bug, 
    show the same type of error. I realized when following a segment he 
    indicated "segment not completed", 
    and I was aware that I was following it correctly.
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
				
				
				
				
				
		
		
    
			
		
    
	
    

    

			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			


	
		
	
	



    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				over 5 years ago
			
												
						in reply to pabelleira
					
									
    
	
    

		
		
    
					
    It does look like a bug in 8.00 follow road where it's writing it to the file instead of just displaying. The strange thing is that it wants to deviate from a road that you're already on. Maybe it's using the routing functionality which in Europe can avoid main roads even if they're perfectly safe for cycling and very popular.
    

    Edit: Seems lock on road is on by default in 8.00, I just got my 1030 replaced for the blue screen of halo issue so it's a completely vanilla device and that setting is on. I thought that was previously off by default. I'll see if I can revert to an older version and check that.
    

    Edit#2, lock on road also on by default with 7.5
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
				
				
				
				
				
		
		
    
			
		
    
	
    

    

			
    
			
    
		
    

		
    
	
    •