Itinerary file causes TomTom to reboot

[twtw]

We have a scenario where loading an itinerary file causes a TomTom to reboot if GPS has been acquired yet loads successfully if GPS has been lost.


Details:
* We use TomTom XXL v9.061 and have several of these
* Our previous SatNavs were Garmin which have been replaced by the above mentioned TomTom
* We have a large number of routes held as .GPX files
* The number of waypoints in a .GPX file varies from 40 to 200
* The .GPX files are converted via TYRE v5.84 (Tyre.) into .ITN files
* Thus a .GPX file may generate from 1 to 4 .ITN files - this a large number of .ITN files are at the maximum of 48 waypoints
* 90+% of the .ITN files load successfully
* 10-% of the .ITN files cause the TomTom to reboot

Reboot Scenario
* Ensure TomTom has acquired GPS
* Start at the normal display
* Tap display, get "Main Menu 1 of 2"
* Tap "Right arrow", get "Main Menu 2 of 2"
* Tap "Itinerary planning", get waypoint list for last successfully loaded itinerary file
* Tap "Options", get "Itinerary" menu
* Tap "Load itinerary", get "Load Itinerary, Are you sure you want to delete all locations in the current itinerary?"
* Tap "Yes", get "Load Itinerary" and list of itineraries
* Tap selected itinerary, get waypoint list for selected itinerary
* Tap "Done", get "The first destination is....Navigate there now?"
* Tap "Yes", wait up to 30 seconds and TomTom will reboot. THAT IS THE PROBLEM

Non-reboot Scenario
* Ensure TomTom has lost GPS
* Start at the normal display
* Tap display, get "Main Menu 1 of 2"
* Tap "Right arrow", get "Main Menu 2 of 2"
* Tap "Itinerary planning", get waypoint list for last successfully loaded itinerary file
* Tap "Options", get "Itinerary" menu
* Tap "Load itinerary", get "Load Itinerary, Are you sure you want to delete all locations in the current itinerary?"
* Tap "Yes", get "Load Itinerary" and list of itineraries
* Tap selected itinerary, get waypoint list for selected itinerary
* Tap "Done", get "The first destination is....Navigate there now?"
* Tap "Yes", wait up to 30 seconds and get "You do not have any GPS reception. Do you want to define a starting points so you cane preview your itinerary?
* Tap "Yes", get "Depart from" menu
* Tap "Recent Destination", get list of Recent Destination
* Tap a recent destination, wait 20 seconds and get "Busy planning a route..." = SUCCESS

Anyone know why the itinerary does not load if GPS has been acquired?

Have we done something wrong in the conversion process?

Regards

Trevor

 

[dhn]

Was this an XXL IQ Routes -- Europe model?

If so, one thought I have is that the country chosen for the itinerary does not match the country (UK probably) selected in the specific Europe map you have active at the time.

 

[Andy_P]

Would it be possible for you to upload one of the problematic itinerary files to a file-sharing site, so we could try it on some other models? (or just email it to a couple of us?)

 

[canderson]

* 90+% of the .ITN files load successfully
* 10-% of the .ITN files cause the TomTom to reboot

Reboot Scenario
...
* Tap "Done", get "The first destination is....Navigate there now?"
* Tap "Yes", wait up to 30 seconds and TomTom will reboot. THAT IS THE PROBLEM

Non-reboot Scenario
* Tap "Done", get "The first destination is....Navigate there now?"
* Tap "Yes", wait up to 30 seconds and get "You do not have any GPS reception. Do you want to define a starting points so you cane preview your itinerary?

FWIW, I'm still on version 5.82 of Tyre.

OK - in your reboot scenario, the unit is actually attempting to plan a route based upon your itinerary, using your current (known) position as the starting point for the routing. In your non-reboot scenario, the device has no idea where it is, and is at least for a time, unable to even attempt a routing.

In both cases, the itinerary has been 'loaded', but only when you have a valid GPS signal the unit attempting to plan a route based upon that itinerary.

I'm not accustomed to seeing Tyre blow the creation of an *.itn file, but I can imagine one situation where this might not go well. Are ALL of your destination waypoints in the 'problem' itineraries actually routable? By that, I mean, are they all close enough to a known road that, if you attempted to manually route to them as coordinates, you would not receive a "No Route Found" error for any of them?

Just to see how it goes, and I apologize, but I cannot think of a less tedious way to accomplish this, print (or just read it with a text editor) the ASCII of a problem *.itn file, and using the coordinate data found within that file, attempt a simple "Navigate to" to the coordinates as they are specified for each of the itinerary points in that file. If one is invalid, I'd suspect the problem will be with the first entry. See if the unit is able to establish a route to each of those points, especially that first one in the list. Look for any other anomalous looking entries while you're there. Beware of the use of punctuation marks within waypoint names. While they always route for me, I've seen characters like # and - cause some very peculiar displays of the waypoint names.

If that test does not turn something up, I'll ask you to send me one of the *.itn files that is causing you grief to dissect it here and see if there's any other explanation.

 

[twtw]

I will try and use the coordinate data from .int file attempt a simple "navigate to".

However, in the non-reboot scenario, the TomTom will plan a route (whilst it has not acquired GPS) and after the "Busy planning a route..." has completed:
* it will draw the route.
* If you then tap "Details", get "Route Information" menu
* Tap Browse map of route", get a google earth type view
* Zoom in and move centre of view, you can then see the line of route with all waypoints shown


Re characters like #. The only non alphanumeric characters are shown in the example of first and last lines below (obtained using notepad)
Here is the first line of the .itn file
-291416|5341734|Liverpool Route 3 Dual Start|0|

Here are the last 2 lines of the file
-293022|5342159|16BrainerdStree|2|
"MapSource 6.15.11"

 

[canderson]

Here are the last 2 lines of the file
-293022|5342159|16BrainerdStree|2|
"MapSource 6.15.11"

""MapSource 6.15.11"" <= That last bit ought NOT be there.
Looks like you used Garmin's MapSource product (vs. Tyre) to generate the original *.gpx file. While it should be ignored as an unparsable line, I have no idea what that might be causing.

Are you in a position to send an offending *.itn file for me to work with?

As a completely irrelevant aside, 6.16.3 is the current version for MapSource.

 

[Andy_P]

Are you in a position to send an offending *.itn file for me to work with?

Or upload it to a file-sharing site as I suggested, so we can ALL have a look.
It'll obviously need someone with UK maps...

By the way 'twtw'... VERY nice reporting of your issue! :thumb:
If only everyone was so clear and concise with their descriptions.

 

[canderson]

Are you in a position to send an offending *.itn file for me to work with?

Or upload it to a file-sharing site as I suggested, so we can ALL have a look.
It'll obviously need someone with UK maps...

By the way 'twtw'... VERY nice reporting of your issue! :thumb:
If only everyone was so clear and concise with their descriptions.

Amen to that. And TomTom should be so lucky as to receive reports like that!

Several of us have UK maps over here, too (useful when they let us out of our cages from time to time )

 

[twtw]

All the routes were in Garmin Mapsource and were downloaded into Garmin Satnavs.

The routes were read into Tyre and adjusted to suit the Google Map used by Tyre and a number of waypoints deleted to so that less waypoints were used so as to give a smaller number of .int files - the 48 waypoint restriction for a TomTom .int file.

So the Tyre/Tomtom version is not a 100% match to the original Garmin version.

Here is an offending route - Liverpool is in the north west of England:

-291416|5341734|Liverpool Route 3 Dual Start|0|
-291511|5341938|DerbyLaneandUnd|0|
-291688|5342439|7QuarryRoad|0|
-292193|5342484|HughendenRoadan|0|
-292378|5342893|15HewitsonRoad|0|
-293881|5343916|QueensDriveWalt|0|
-295969|5344402|WaltonVillagean|0|
-296439|5344726|Ramp|0|
-298308|5344548|HawthorneRoadan|0|
-298777|5344320|128WadhamRoad|0|
-299334|5344277|KingsRoadandKeb|0|
-299647|5344419|MillersBridgean|0|
-299942|5343862|RegentRoad|0|
-299844|5342523|9BlackstoneStre|0|
-298773|5342810|134CommercialRo|0|
-299293|5343049|SandhillsLane|0|
-299420|5343271|DerbyRoad|0|
-298729|5343895|StanleyRoadandA|0|
-298401|5344282|31BenedictStree|0|
-298091|5344386|220BedfordRoad|0|
-297227|5344543|StuartRoadandBe|0|
-296725|5344512|18ChurchRoadWes|0|
-296454|5344343|129CityRoad|0|
-296828|5343982|57AndrewStreet|0|
-297279|5344303|39HaleRoad|0|
-298065|5344016|MelroseRoad|0|
-298540|5343393|StanleyRoadandP|0|
-298180|5343076|LambethRoadandL|0|
-297468|5343577|BradewellStreet|0|
-297074|5343820|LanghamStreet|0|
-296134|5343679|240PrioryRoad|0|
-295537|5343201|68ArklesLane|0|
-296918|5343110|WaltonBreckRoad|0|
-297652|5342977|NetherfieldRoad|0|
-297205|5341878|PrinceEdwinStre|0|
-297896|5341548|StAnneStreetand|0|
-296701|5341205|BrunswickRoad|0|
-296760|5341906|HeyworthStreet|0|
-296836|5342578|MereLaneandLans|0|
-295467|5341904|BoundaryLaneand|0|
-294900|5342222|8BelmontRoad|0|
-294686|5342921|TownsendLaneand|0|
-294231|5343256|PinehurstAvenue|0|
-295077|5343501|UttingAvenueand|0|
-294214|5343762|CherryLaneandWo|0|
-293519|5343282|31MaidenLane|0|
-292927|5342445|GreenLaneandSan|0|
-293022|5342159|16BrainerdStree|2|
"MapSource 6.15.11"

Regards

Trevor

 

[canderson]

Thanks. I've trapped that for the experiment. But DO understand that the additional tag added by MapSource may well be detrimental to any of these *.itn files.

 

[Andy_P]

Here is an offending route - Liverpool is in the north west of England:

-291416|5341734|Liverpool Route 3 Dual Start|0|
-291511|5341938|DerbyLaneandUnd|0|
etc.
etc.
-293022|5342159|16BrainerdStree|2|
"MapSource 6.15.11"

Well, it's not quite the same as having an ACTUAL .itn file to look at, but it might give us some clues...

I think it is all down to the number "Flag" at the end of each line.

My reference notes from the old Software Developer's Kit says this:

Each line consists of the following fields, terminated by bar characters (‘‘|’’)

Field 0 Longitude in WGS84 format (in 100 000th of degrees)
Field 1 Latitude in WGS84 format (in 100 000th of degrees)
Field 2 Name of this point in the itinerary
Field 3 Flag

Flags in itinerary lines:
The flags in the itinerary lines can be ORed together. Currently, the following flags exist:
0x00 None
0x01 Itinerary location is enabled
0x02 Itinerary location is a stop−over (as opposed to a
pass−by location)
0x04 Itinerary location is departure point (Should only
be set for the first item in the itinerary file)

EDIT:
I found a better (newer?) description of the flags elsewhere...

Currently, the following flags are available:

0 Waypoint

1 Waypoint disabled (will be skipped when navigating the itinerary, appears dimmed in the itinerary overview)

2 Stopover or destination

3 Stopover disabled (will be skipped when navigating the itinerary, appears dimmed in the itinerary overview)

4 Departure point (should only be set for the first item in the itinerary file)

The navigation device will always guide the driver to the first stopover of the itinerary, via the preceding waypoints if present. Passing a waypoint automatically disables it (ie. its flag gets changed to "1"). Stopovers can be disabled manually only and this,sets the flag for that stopover to "3" and the flags of all the waypoints leading to the stopover to "1". When passing a stopover, the navigation device will guide the driver back to the stopover until the driver disables the stopover.

Example:
Here’s an example of an itinerary file representing a small itinerary in France:
80417|4821030|Unnamed road, Gu? (Le) (Vendeuvre−Du−Poitou)|4|
98140|4799585|Unnamed road, Boursay|1|
107833|4804246|Unnamed road, Drou?|1|
115927|4800041|Unnamed road, Haies (Les) (Bourdonn?)|3|
This itinerary consists of a starting point, an end point and two stop−overs in between.

Now, I don't think that is entirely correct any more, because I have working itineraries on my machines that don't have a departure point with a {4} flag,

Maybe it's only set if you DON'T have a GPS reception to use as your start point.

But having found the updated info, maybe it's not to do with flags after all!

I'll try pasting your list as ASCII text into an .itn file BUT there may be hidden characters which mess it up as an experiment.

Can you not SEND an .itn file as we've asked?

 

[Andy_P]

OK, here's what I did.

I opened a working itinerary file in NOTEPAD and deleted all the text.
I then copied the list of locations from your post and pasted it into the open file
I saved it and put it onto my Go940.

I waited until I had GPS reception and then loaded and ran the itinerary.

It did not fail and re-boot.

It stayed on the "Yes/No" screen for quite a long time, but then calculated the route including all the waypoints (From my starting point in London, up to Liverpool and then round a lot of small streets there).

I suppose I should try it on my XL, but that will have to wait until the morning, it's bedtime now.

Can you try doing the same copy and paste in Notepad as I did, and see if that works?

 

[canderson]

Sorry from my end. 5 yard penalty for delay of game. Can't find my bloody 720 that has my European maps! I'm looking!

 

[Andy_P]

RESULT!

The same itinerary (that I created from your text file) which worked on my Go940 last night, when loaded onto my XL DOES cause a re-boot during the route calculation.
But only if there is a valid GPS location, just as the OP found.

Interestingly, both units have the same version number of software - v9.058.

So... I'll have another play with the "flags", but I'm beginning to think it could be a memory issue.

 

[canderson]

OK - found the 720 with the Euro maps. I am unable to duplicate the problem with that unit. It runs 8.351.

 

[twtw]

Sorry but I am not able to use the email function on this site - not enough posts.

Care to suggest a file sharing site? Dropbox perhaps but then that needs email addresses!

Or email me.

 

[Andy_P]

Are you able to use the attachments function?
Open a reply window and click on "Go advanced"

Then click on the paper-clip icon at the top of the post window.

That's usually used for uploading pictures, but you can also upload text files.
So you'll need to rename your itinerary file to have a .txt extension.

Once you've done that click on "Browse" to find it and then click on "Upload"

Go back to the forum post window and click on the paper-clip icon again. Your file should be listed, so click on it and an attachment should aprear in your post.

I'll upload the test itinerary I created using your text from an earlier post.

View attachment Test_fails_on_XL.txt

 

[twtw]

View attachment LIVERPOOL_p3 (1).txt

The LIVERPOOL_p3(1) file is now attached as a .txt file.

Thanks Andy_P

 

[Andy_P]

I've had no luck with my file so far. Nothing I've tried has enabled it to work on the XL, but it does work fine on a Go.

When I tried it again today, it failed even if there was no GPS signal lock, so maybe that's a red herring.

Time to pass it on to TomTom and see if I have any luck there.

 

[twtw]

Re TomTom.

I tried TomTom support a few weeks ago and after several message toing and froing they responded that because I had used a 3rd party, i.e. TYRE, to convert the files, there was nothing they would do as files created via 3rd party software could generate incompatible files!!!!

Hence, I found this forum which I have found very useful.