XT2 turns off and restarts

[FelixHauser]

For the sake of completion of my ongoing investigation I have the following info:

One of the tracks that made my Zumo crash has 16k+ points.
The other track that also made the device crash has 11k+ points.

According to the documentation (I used Perplexity to find it fast), theoretically the Zumo XT2 should be able to handle up to 100k points on a single gpx track.

[lkraus]

100k track points would be a huge increase over any previous Zumo.

On the Zumo 590/595/XT there is a file named GarminDevice.xml listing some limits, including

Code: Select all

<MaxTrackPts>15000</MaxTrackPts>

It might be interesting to see if the XT2 has a similar file.

If you still have the Navigator 6, BMW/Garmin are providing replacements that really have fixed the "ghosting" problem. I don't have the correct customer service number for Germany, but it reportedly only takes a phone call to arrange a replacement, no receipts, proof of purchase, etc. needed.

[smfollen]

From my XT2, MaxTrackPts = 100,000

Code: Select all

<LimitExtension xmlns="http://www.garmin.com/xmlschemas/GarminDeviceExtensions/Limits/v1">
<MaxRoutes>2147483647</MaxRoutes>
<MaxRoutePts>32768</MaxRoutePts>
<MaxShapingPtsBetweenVias>998</MaxShapingPtsBetweenVias>
<MaxRouteName>36</MaxRouteName>
<MaxSysRtePts>2147483647</MaxSysRtePts>
<MaxWaypoints>10000</MaxWaypoints>
<MaxWptName>120</MaxWptName>
<WptNameUnique>1</WptNameUnique>
<MaxTracks>2000</MaxTracks>
<MaxTrackPts>100000</MaxTrackPts>
<MaxTrackName>36</MaxTrackName>
<MaxMapTilesPerFile>400</MaxMapTilesPerFile>
<MaxImgFileMbSize>3</MaxImgFileMbSize>
<MaxJnxFiles>1000</MaxJnxFiles>
<MaxJnxTiles>5000</MaxJnxTiles>
</LimitExtension>

[lkraus]

Wow! Major increases compared to my XT:

Code: Select all

HTML:
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> 

I would be jealous, but I've never even approached these limits while using my XT.

[FelixHauser]

where do you get all that code from?

Today I am expecting a call from Garmin to talk about the problem. Let's see.

[smfollen]

Connect the XT2 to personal computer via USB cable. On the zumo tap to connect to computer. It takes a minute or so for the zumo to show up on the pc but it will. Navigate to and open GarminDevice.xml

GarminDevice.png (21.61 KiB) Viewed 716 times

[FelixHauser]

Oh, I see...

I tried to connect the Zumo to my Mac. It usually worked just fine, but now it doesn't work. I cannot connect it to Garmin Express and the "SD Cards" do not show on my desktop. I will wait until next software update.

[FelixHauser]

Meanwhile, I just got off the phone with the gentleman from Garmin.

He was really polite and nice, but the conversation was just a vicious circle. Me telling him that it cannot be that the Zumo cannot handle 3rd party gpx data and he telling me they cannot proofcheck everything. We finished the conversation with his suggestion to use shorter gpx tracks. He also told me that data from Calimoto and some other App I don't remember work fine. They don't know about Stegra.

So... nothing left to try but the following:

1- I will generate the same route with both Calimoto and Stegra
2- I will compare the formating of the underlying XML files
3- I will build a Python app which translates Stegra formating to calimoto formating.
4- we'll see how it works.

I don't expect both GPX files are much different to be honest, but it is now a freaking challenge.

Good thing, however, he will send me an email with the instructions for a BMW Nav 6 replacement... better than nothing!

[FelixHauser]

Well, it appears both files are more different than I expected.



On the left side, there is the Calimoto file. On the right side Stegra. As you can see in both cases it's just a collection of gps data, but with some differences:

- Stegra includes elevation data. Calimoto does not. That alone makes the file quite larger is size.
- the gps data are wrapped with <trkpt></trkpt> in Stegra and <rtept></rtept> in Calimoto.

I consulted my AI assistant regarding this matter. Apparently Calimoto's format is more typical for a route planner. On the other side what Stegra creates is more typical of a Track Recorder, such as what Zumo XT2 itself makes. The Stegra format is much more dense point-wise. That means, it creates a point every 2 meters (for instance) instead of every 10 or 20 meters on calimoto.

The combination of all together can lead to unexpected behavior on some SatNavs.

Solutions include preparing shorter tracks or converting and pruning the elevation data.

Again, in my opinion, it boils down to a memory management problem on the side of the device. Also in my opinion, it doesn't matter how much bigger the Stegra files are, this should not happen on modern devices. Period.

I also noticed that the last track which gave me problems had all the elevations set to 0. No idea why.

I will try to reach out to Stegra. I wanted to do that anyway to address some issues I've noticed with the App.

[smfollen]

As you probably know, tracks (what you have from Stegra) and routes (what you have from Calimoto) are very different things in terms of how they will be handled by most any SatNav device.

I would guess that the zumos ignore elevation, but I really don't know.