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

VP Screenshots

leginswal
3 months ago

These are some screenshots from todays ride following a course and why I deem VP datfields on a 530 unusable. The only method of seeing where the VP is, is by looking at the map page or the elevation profile:-

Early in the ride, the VP is a third of a mile in front, but, I am supposed to be only 10 seconds behind. If I could ride a third of a mile to catch up in 10 secs, I would have to be travelling at 110mph.

Further on, just over a quarter of a mile behind, but just a second behind, to catch up, I would have to do 500mph.

Only 17ft behind closing in fast on the VP, but note the time behind 1 min 21sec, and dist behind and also the elapsed time and compare to the next picture.

In the space of 9 secs. I am now just 1 foot in front of the VP, but already 1 minute 22 secs in front?????? For some unknown reason, in a screenshot, the VP datafields do not show up green despite they are green on the Garmin???????? The distance travelled to get in front, 18' does not equate to the time I was behind and to the amount of time I am now in front, 2 mins 43 secs.
The closing stages of the ride, over a mile behind but only 7 seconds behind, How????? This is why I do not use the VP datafields. On my Garmin Edge 800, they worked perfectly.

  • 0 3 months ago

    Yes. I agree that the VP is totally not working appropriately!

  • 0 3 months ago

    Has it ever worked for you? 

  • 0 3 months ago in reply to dochou

    The VP data fields have never worked for me properly, at times they can be right, but more times than not, they are wrong especially "Time Ahead", "Distance Ahead" can be right more often than not, so I never use them. I only enabled them past two days to get some screenshots to post to show how wrong they are. 

    The only way to see where the VP is, is on the map page, the elevation profile where you can set the scale and then you can estimate the distance of the VP away from you, unless it's behind you and it's not visible or too far in front, and the VP page with the graphic. If the VP is in front or behind in the graphics page, you know it is, but timewise, it's usually incorrect.

    I have a feeling most users accept what they see, and do not realize, the timings are way out.

    The 530, seems to have a Time/Distance calculation issue. It cannot give an accurate to the nearest second "Time to Destination" time, it can be way out, it's not based on current speed or even average speed, it has a mysterious alogarythm. That is why I use a third party app, which will give me accurate Time/Distance calculation to the nearest second. And once again, I think mist users do not notice the error and just accept what it says. The only time it becomes correct is when your virtually at your destination.

    I think the VP uses an odd calculation to work out it's "Time ahead" as well.

  • 0 3 months ago in reply to leginswal

    I agree that your VP is weird. I checked mine a couple of days ago on a free ride and the time and distance gaps all were correct, so it’s working as it should. My VP screen shows the set VP speed at the top of the screen and not a % like yours.

  • 0 3 months ago in reply to PeterK_55

    When you ride a course, the VP page will show a percentage, the average speed of the course was just over 16 mph so as it is showing 100%, that is the speed the VP will be moving. If you want to speed up or slow down the VP you can alter it as you ride and the percentage figure just changes. 

    If your freeriding, the VP will display the speed it is set at 

    Don't know why Garmin do it two different ways. Maybe when your training you can decide how hard you want to go as a percentage.

  • 0 3 months ago in reply to leginswal

    Thanks. I've never found the VP implementation with a course to be useful. For me, it would be better if the VP just rode at the on screen speed setting all the time.

  • 0 3 months ago in reply to PeterK_55

    Using VP with a course is a brilliant way of riding, but not with a course created from a course designer as the VP will "ride" at the speed set into the course. Invariably this means it will "ride" the course, up and down hill and on the flat at that set speed. 

    But, create a course from a history file, and it's different, it will match exactly all your speeds, slow down on hills and go like a rocket down hills etc and can lead to exciting rides. Many occasions I can be just yards and seconds in front or behind in the closing stages of a ride as I look at the map page.

    If I beat the VP, then I delete the course and create a new course from the history file which reflects the new fast time for the VP.

    Sadly the 530 VP data fields let it all down, so you have to watch the map page to see how things are going or as I mainly have to do, use a third party app to allow you to see your average speed to 3 decimal places and know what the average speed is to beat. If not, you could race the VP with an AVG speed of 16.5, you finish with the same AVG speed but find you was beat, basically the VP speed was 16.525 and your AVG speed was 16.495, both speeds would show as 16.5 on the Garmin, another failing of a Garmin edge to only show AVG speed to one decimal place .

    Just actually thought, this is probably why you see a percentage on the VP page, to get a faster time on a course from a history file, you can set the percentage to just 102% for example and by racing the VP you have a target to pace you to a faster time.