OFFLINE

Because of hardware limitation, Rider 30/35 can support the planned trip up to 18 waypoints. If your trip is more than 18 waypoints, Rider 35 may not be able to direct you after the 18th waypoint.

OFFLINE

What is the distance for this?  I have completed rides up to around 15 miles using planned ride.  It seems like anything past that it wont work.

OFFLINE

Hi, Richard,

Distance should not be a factor. When you rode the trip of 15 miles, did you pass 18 waypoints?  Just need to figure out this in order to decide where the problem might be.  Thank you and have a nice weekend!  

OFFLINE

So, given that most routes of 18 waypoints are short enough not to need a route planner, how can you make a long route with only 18 waypoints? And when is this going to be fixed? At present, it looks like the Bryton Rider 20 will be the same as the Rider 35 minus the bits of the 35 that don't work properly.

Edit: I've tried to plot a route with minimal waypoints by dragging waypoints along the route but it just ends up by replotting the bit I've already done so that is no good.

OFFLINE

It doesn't do find and go,  no amount of fiddling will make it work.  Mine is back for the second time being looked at.  I want a refund as it froze up on me when rained on a few weeks ago.  Been at supplier for over 2 weeks now.  If they try to give me another one I will send it back as find ad go simply doesn't work and that's what I wanted.

OFFLINE

I thought I'd test out the 18 waypoint thing. The last attempt I made with Find and Go was an 18 mile commute. The route was plotted with 22 waypoints and ground to a halt at about 11 miles.

So I replotted the exact same route this time with only 5 waypoints - so in theory it should work all the way. I set the display to show distance to destination and both old and new routes gave it as 23 miles (somewhat oddly!).

On trying out the new route today I found it stopped at pretty much exactly the same point as before.

So therefore the number of waypoints appears to be irrelevant - 5, 22; it's all the same.

As I posted in the old forum, I think the limitation is the route plotted; the hillier and less straight the route, the seemingly longer the route can be. But I've not been able to test that properly as there aren't any flat, straight routes around here.

Thoughts from Bryton appreciated!

OFFLINE

I think there are several issues might cause the distance discrepancy between planned route and actual riding distance from GPS.  The linear route displayed on the screen is to provide reference points and directional guidances toward destinations.  The distance discrepancies between the planned route and the actual riding route calcuatled by GPS may due to 1. GPS tolerance error of +-10M 2. Since there is no map on Rider35, the riding route may not be perfectly in line with the planned route.

OFFLINE

Originally Posted by Emma Yeh:
I think there are several issues might cause the distance discrepancy between planned route and actual riding distance from GPS.  The linear route displayed on the screen is to provide reference points and directional guidances toward destinations.  The distance discrepancies between the planned route and the actual riding route calcuatled by GPS may due to 1. GPS tolerance error of +-10M 2. Since there is no map on Rider35, the riding route may not be perfectly in line with the planned route.

This is true but not quite relevant to my issue where the discrepancies are present before I've even got on the bike! In this case, the plotted route is shorter than distance to end of route displayed on screen. As to distance ridden - of course it never got to the end anyway.

Do Bryton - can you respond please?  

OFFLINE

Also just plotted a very short 21 waypoint route. It seems to load fully into the Bryton 30 confirming that there isn't an 18 waypoint limit (though the weather is too nasty for me to want to try riding it now - but I'll test it when I can).

The map doesn't display correctly though. As before, the route is shown in its (un-followable due to teeny scale) entirety. In earlier firmware iterations this didn't happen.

So, a repeat request - Bryton; please feed back.......