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

Route calculation stops at 80% when navigating to another country

I have problems navigating to another country with my Edge 1030 (Navigation> Search> .......).
Last weekend I had a tour in Luxembourg and wanted to navigate from Germany to Vianden in Luxembourg. But the route calculation stops at 80%.
Now that I am back home I have tried to navigate to Kleve in Germany from the Netherlands. Again the route calculation stops at 80%.
Navigating within the borders goes without problems.
I run software 5.00 and the new maps 2018.10
My brother with the same Edge 1030 has no problems with navigating. He runs the same software but still the old maps 2017.10
I do not know if this has anything to do with it, but with the new maps 2018.10 the country code behind the city names has disappeared.
I have already installed the maps for a second time. But the problem remains.
The helpdesk talks about installing the maps on a MicroSD card. But I do not get that option when using Garmin Express. Probably because there is still enough space on the internal memory of the Garmin.
But I do not understand this solution because with the new maps I still have 5 Gb of space left.
Who has the same experience and / or has a possible solution?
Thanks in advance.

0 Visionary over 6 years ago

Problem solved by downgrade to the old 2017 maps!!
After all the problems with the 2018 maps described on this forum I came to this solution.

But still I want to complain about the Garmin customer support.

On 11 June I called Product Support about this problem.
The answer was: You have a storage problem, just put the maps on a SD card.
So I moved the maps from the internal memory to the SD card.
As I thought, this was not the solution.

I have submitted two help questions:
The first on 15 June at the US customer support, after nine days still no answer.
The second on 24 June at the Dutch (European) customer support, till now no answer.

If I buy a bike navigation for so much money, I expect faster and better help.

0 Former Member over 6 years ago

Yep.. same problem here, but inside a country.

Sworn very loud about that BETA rubbish and tried it again. It worked :)

0 SUSSAMB over 6 years ago

Problem solved by downgrade to the old 2017 maps!!
After all the problems with the 2018 maps described on this forum I came to this solution.

Sounds to me like you only have part of the map, the EU map is now so large I believe it's in two parts. You need to run Express again and ensure both parts download.

0 Visionary over 6 years ago

All separate countries where present. So that's not the issue.
I did two times the map install through Garmin Express.
And I have seen that Europe now consists of two files.
But is that just not the problem?
These were the new files (maps) after the update:
D4728090A.img
D4713060C.img
gmapprom.img
D6017000A.img

0 Freek_H over 6 years ago

The fact that the new map is in two parts could be the reason that navigation fails while travelling from one part to the other. Gmapprom.img contains the North/East part, including Germany, while
D6017000A.img contains the South/West part including Luxemburg and The Netherlands, coïncidence? If this is the cause then Garmin should solve this problem.

Customer Suppport mostly suggests a customer fault or keeps mum if you report serious problems with software or hardware is my experience.
It is probably a good advice to downgrade to the 2017.10 version when you live near the borders of those two maps. Does somebody know how to do this?

0 Former Member over 6 years ago

Just encountered the same problem as you this morning.
My route was Luxembourg to Trier, Germany and back.
I did this exact one 2 months ago and it worked fine.

I haven't tried many settings changed to make it work as I was pressured by time. I ended up using my phone for navigation instead. Garmin 1030 was completely useless.

In Luxembourg-Germany Calculation of map was stuck at 80%.
In Germany-Luxembourg Calculation didn't even occur, but the Ride button on the screen was disabled, not accessible at finger touch.

0 SirBikeAlot over 6 years ago

Faced around two weeks ago the same issue. Tour was planned with Garmin Connect. Started in Germany and worked fine, but as soon as I was in Austria calculation stopped at 80%. Worked again, when I was back in Germany. Same problem a few days later with a tour from Germany to Czechia and back again. So I think this is not a user related problem, but a Garmin Software Problem. So fix this asap. Otherwise there will be a lot more 1 star ratings on Amazon...not that great for the Garmin Top Device.

0 Former Member over 6 years ago

I just conducted a test with a set of 17 courses I created for a tour we're doing in a few weeks, which takes us from central Switzerland to Austria, Germany, back to Austria, Lichtenstein, and finally back to Switzerland. However, as my Australian 1030 only came with Australian maps, I'm using the Velomap map of Europe, which Basecamp sends to the 1030 as six separate files totalling about 16.4Gb. I loaded each day's course and let it calculate, and all courses calculated to 100% without any problem. Three of those courses cross a country border and another crosses two country borders. So probably, as has already been suggested, there's a screwup with the latest Garmin Europe map that causes the problem. My 1030 is running 5.00 firmware.

0 SirBikeAlot over 6 years ago

at AuldNik: The calculation of a tour worked for me also fine...when I did it at home or when a started the tour. The problem occured during the real tour, as soon as I left country 1 and entered country 2 of the tour. Suddenly the Edge showed the wrong distance to the next waypoint, started recalculating and then it was stuck at 80%. This only started working again, as soon as I was back in Country 1.

0 Microkid over 6 years ago

Just did a 128km ride from The Netherlands to Germany and back, crossed the border several times. Route calculation was fine, the navigation was fine, no errors of hick-ups or other strange things. Just as I expected: all works great. Using firmware 5.0 with Maps 2018.10.