Cannot calculate route/route memory full

[Tiger900BD]

Hi,
New to Zumo Xt and finding it very frustrating to use.
Created a route on MRA, got it into the unit but when I select the track it gets stuck at 'calculating 99%' for several minutes followed by 'cannot calculate the route' if I acknowledge, followed by 'route memory full'
There is only one track on the unit.

[jfheath]

Welcome to the forums from the UK.

Tracks shouldn't need to be calculated, although I believe that there is a limit on the number of points that make up the track.
How long is the track approximately in miles / km ?

Are you converting the track to a trip ? Or just selecting the original track ?

I assume that you are using HERE maps on MRA ? It might be that points on your MRA map are slightly displaced - but a track should be able to load whether it is on a road or not.

If the track is in Europe, and you could attach it to a private message, I'll take a look.

I'll try to find out what the limit is for the number of track points in a track. I know I have seen what it id, but d not remember.

In the meantime - try the same with a shorter track.


edit -

Garmin says that the maximum number of track points per route is 10,000 for the XT. Link here. A few sources in Google search suggests 15,000 but I haven't seen anything to say that the software has been updated. 15000 was the figure for the slightly earlier Zumo 590 and 595.

You cannot see the track points, and I have never hit the 10,000 limit for rides of 250 miles. The longer the track in miles, the more points there will be, but the distance is not an accurate indication of the number of points. Curvy routes need more points than routes on straighter roads. But if your route went over 300 miles, that is beyond my experience, so I would suspect you may have hit a limit - but I cannot possibly say that for certain.

Load your track into Basecamp. That lets you see the track points, it tells you how many there are, and has some pretty good editing tools - eg you can trim the number of points by specifying a maximum, or get it to remove every (say) third point.

[FrankB]

Just a few suggestions:
Check your maps. (Map & Vehicle/myMaps). Make sure CN Europe NTU North and South are checked. Parkopedia, DEM and Foursquare are also known to be ok. Topo Active Powersports are for offroad usage, not needed for road usage. If you have other maps checked, try unchecking them.

What is your calculation mode? (Settings/Navigation/Calculation Mode). Set it to 'Faster time'

Have you set any route avoidances? (Settings/Navigation/Avoidances) Uncheck em all to begin with, except 'Unpaved routes'.

If it still does not work, post your GPX file.

[Tiger900BD]

Just some background.
When I bought the XT last October everything worked fine, create a route, export it and off I go.
The bike and the Garmin have been lying up all winter, started up the Garmin last week and the problems began.
XT checked for updates and all good.
MRA route created on the HERE map.
120Km long.
On MyMaps only 'installed maps' available but up to date.
Calculation mode is set to 'faster time'
Avoidances all unchecked except'unpaved routes'
Out of curiosity I exported the same route to my TomTom 410. It imported the route no problem. Only thing is I can't see it because of the blob of condensation on the screen (known issue) hence the change to Garmin, although the 410 becoming more compelling by the day.

[jfheath]

All good points - but he said that "when I select the track it gets stuck". I have never come across that before - but I don't have long tracks, and I don't know what the XT does when you give it a long track.

He raises an interesting question if it is related to tracks. GPS Expert (according to a Google search) reckons that the value for the XT is 15,000, but the manual says 10,000 - so one of them is now wrong. It could be old information that Google is still reporting. Garmin may have changed it.
It's interesting though, to see how information gets spread seemingly without it being checked.

So I will check this out. I'm bored. and its either this or go and balance my throttle bodies. No - its cold outside. So I've just plotted the CRUK4000. It doesn't exist, but I've just come up with it - it will be interesting to see how long it takes to catch on ! Its a brilliant route roughly 4,000 miles long. It took me a lot of very careful planning over the last few minutes and the resulting track has 78,619 points. It would be tedious to ride. But hey, it has a catchy name and a big number - so its bound to attract a lot of attention.

cruk4000.jpg (9.43 KiB) Viewed 1717 times

This route has three really useful purposes:
1. It will give me a large number of track points to experiment with.
2. It will give me a large number of route points to experiment with.
3. If it does catch on, it'll keep those that like to ride such routes away from the Yorkshire Dales. It's OK. They won't read any further than the picture.

Right I'm off to see what 78,619 track points do to my Zumo XT. I may be some time.

Some people do confuse tracks, routes, trips. Even Garmin seem to use the word 'trip' in two completely different contexts - which I think will confuse.
Just waiting for a response from @Tiger900BD

[lkraus]

I think the XT track point limit is 15,000. I can't think of a reason to reduce the limit from the 590/595 when the XT has so much more memory.

I don't know the exact purpose of the "GarminDevice.xml file on the XT, but it does show some familiar limits:

Code: Select all

xmlns="http://www.garmin.com/xmlschemas/GarminDeviceExtensions/CustomMaps/v1">
            <MaxImages>400</MaxImages>
            <MaxImageFileSize>3145728</MaxImageFileSize>
            <AllowedFileType>jpg</AllowedFileType>
        </CustomExtension>
        <LimitExtension xmlns="http://www.garmin.com/xmlschemas/GarminDeviceExtensions/Limits/v1">
            <MaxRoutes>100</MaxRoutes>
            <MaxRoutePts>5971</MaxRoutePts>
            <MaxShapingPtsBetweenVias>198</MaxShapingPtsBetweenVias>
            <MaxRouteName>36</MaxRouteName>
            <MaxSysRtePts>20000</MaxSysRtePts>
            <MaxWaypoints>1000</MaxWaypoints>
            <MaxWptName>120</MaxWptName>
            <WptNameUnique>1</WptNameUnique>
            <MaxTracks>200</MaxTracks>
            <MaxTrackPts>15000</MaxTrackPts>
            <MaxTrackName>36</MaxTrackName>
            <MaxMapTilesPerFile>400</MaxMapTilesPerFile>
            <MaxImgFileMbSize>3</MaxImgFileMbSize>
            <MaxJnxFiles>250</MaxJnxFiles>
            <MaxJnxTiles>5000</MaxJnxTiles>
        </LimitExtension> 

Granted, there are some UNfamiliar numbers also, like 198 MaxShapingPtsBetweenVias. I typically only use three or four via points and less than a dozen shaping points on a entire route, so I've never tested any of the XT limits.

[FrankB]

Sometimes, not very often, it helps to do a cold start.

First power on
Hold the power button, until it asks to shut off.
Confirm

Power on again. You'll notice it takes longer to start.

[jfheath]

The XT accepted tracks with 10001 points and 15001 points. It took about 5 minutes to calculate after selecting from the list if tracks.

I got bored and didn't try any larger number of points. But it doesn't sound like track points is his issue.

Wondering now about MRA and the type of gpx file created. MRA have a new feature which puts their 'waypoints' on the route - loads of them. Im not sure what the advantage is. They are stripped out with MRA gpx 1.2, but are left in as shaping points with MRA 1.1. That is likely to meet the issue with the number of shaping points permitted between Vias. (125 I think - but @lkraus's excellent contribution above indicates 198.

Need more info from @Tiger900BD to be able to help.