Quest waypoint memoryissue/Mapsource 6.15.4

[Kritou]

Off to S France soon but all four Quests are having problems transferring our planned routes

We are using CN Europe v8 and Mapsource 6.15.4 (for the first time) and have tried an older version of Mapsource with the same result

No sweat with the minimum maptile set (197.6MB) but just before the transfer is complete the Quests start complaining about "Route Waypoint Memory Full" and the final route is truncated

There are only seventeen waypoints in the eleven routes, although there are 147 via points

Garmin customer service suggest a corrupt waypoint but the accompanying two Zumos load with no problem

We have never had an issue before with "waypoint memory" even on a Baltic circumnavigation so I wonder what is happening?

 

[Achim]

Sounds like a Mapsource problem. I had problems with 6.14 so went back to 6.13. Looks like I'll be skipping 6.15, too. Kinda glad I turned off the auto-update feature in Mapsource...

You might want to try 6.13, start with no waypoints, redo the waypoints and see what happens. Things cannot get any worse, I suppose... Had the waypoint problem, too. Starting from scratch fixed it. A bit of a bummer with 147 waypoints, however! You may want to use the pointer tool instead.

Achim

 

[ampthill]

Off to S France soon but all four Quests are having problems transferring our planned routes

We are using CN Europe v8 and Mapsource 6.15.4 (for the first time) and have tried an older version of Mapsource with the same result

No sweat with the minimum maptile set (197.6MB) but just before the transfer is complete the Quests start complaining about "Route Waypoint Memory Full" and the final route is truncated

There are only seventeen waypoints in the eleven routes, although there are 147 via points

Garmin customer service suggest a corrupt waypoint but the accompanying two Zumos load with no problem

We have never had an issue before with "waypoint memory" even on a Baltic circumnavigation so I wonder what is happening?

Had the same issue myself with a Quest when loading a number of preplanned for a European tour a few years ago. IIRC it will take about 2000miles but will not load anything more than this even if you split the route into segments or days. It transpires the quest has a limit to the number of waypoints it can manage - and this includes those that are inbuilt within the route so you can't do much about it. Only real solution is to load different routes onto a couple of quests or take a laptop with you to download routes onto quest as required.

Peter

 

[John Armstrong]

So they've managed to make the Quest obsolete by a back-handed means?

 

[ampthill]

So they've managed to make the Quest obsolete by a back-handed means?

No, I believe it is a quest issue not a mapsource issue. Certainly the problem existed with the version of mapsource that was current 2 years ago.

By the way always found the quest an excellent piece of kit. In some ways I prefered it to the zumo 550 i now have. Only problem is that the aerial would always fail every 12 months or so. but the service from garmin was top rate

peter

 

[Tomcat]

I had a similar message about waypoint memory full when I tried loading a route planned by someone else, in a later map version (in fact NT maps supplied with a Zumo). The route opened up in Mapsource on my earlier non-NT maps and looked OK, but it would not load correctly into the Quest. The solution was to re-plot the route on my map set.

I think I read somewhere that the Quest will take up to 500 via points, but if your routes only need 147 you're a way off this limit.

 

[barry.arthur]

My info is not to go past 6.13.7 in mapsource.
Works for me.
Barry.Arthur

 

[Kritou]

Thanks for the input folks - I wish it were a recent Mapsource scenario but I get the same result when using 6.12.x. By downloading a Baltic cicumnavigation from several years ago, having upped it's via-point count to 147, I'm now getting the same message

It would be interesting to know how memory is allocated - Garmin have not been able to shed much light

 

[Tomcat]

You might be best doing a full reset on the Quest to set it back to factory defaults. This should clear out any extraneous via points that are clogging up the memory.

 

[Kritou]

You might be best doing a full reset on the Quest to set it back to factory defaults. This should clear out any extraneous via points that are clogging up the memory.

On the advice of Garmin I did just that. Strange that is happening to all four Quests at the same time and to the "new" one that has just arrived from Taiwan

 

[worlestone]

Any resolution to this one? Having the same problem and dealing with an unresponsive Garmin support service.

Thanks in advance folks

Adrian in Somerset

 

[Achim]

Any resolution to this one? Having the same problem and dealing with an unresponsive Garmin support service.

Thanks in advance folks

Adrian in Somerset

6.13 works well .

Newer isn't always better, especially when it comes to software updates...