I am venting about a dead XT, again.

[jfheath]

Well - I didn't know that. I knew that it dropped when the voltage was low, and assumed that it just went up to 100% when plugged in. I hadn't realised that it actually remembered the two different brightness levels.

Odd - because I know that it retains separate information for many of the options when it is powered by the USB cable (Car) and when it is powered by the motorcycle cradle.

I've got used to working at my desk with the Zumos, and the 590 / 595 rally need to be plugged in if I am using them for anything longer than 2 minutes.

[FrankB]

Hard to believe that I knew something you didn't

[Peobody]

I set the brightness level for battery very dim (20-30 %) for external power high (80-100%). When external power is lost, the display goes dim, and you will notice it.

My norm is to have battery brightness set at around 40% but I had pushed it to 100% early in the trip when looking at the GPS outside off the bike. If this is the only clue to power loss then power loss is indeed a possibility. I think it would have had to have started the previous day since I was only a couple hours into that days ride when it acted up. The first time it happened was a little different and I think less likely to have been a power loss although the one common factor was that it wouldn't wake up after going to sleep.

[jfheath]

Hard to believe that I knew something you didn't

Some of the stuff I know, I think that I know pretty well.
Some of the stuff that I think that I know turns out to be incorrect.
I don't necessarily know which is which !
All of the stuff I don't know - well - I don't know about.

Most of the stuff that is in the top two categories is gradually finding its way into the bottom category.

At some point I will know everything about nothing. Or I will know nothing about everything.
But I will forget about that, so everything I think I know will be wrong.

[jfheath]

My norm is to have battery brightness set at around 40% but I had pushed it to 100% early in the trip when looking at the GPS outside off the bike. If this is the only clue to power loss then power loss is indeed a possibility. I think it would have had to have started the previous day since I was only a couple hours into that days ride when it acted up. The first time it happened was a little different and I think less likely to have been a power loss although the one common factor was that it wouldn't wake up after going to sleep.

Have you viewed the battery diagnostic page ? Hold the battery icon on the main screen for about 10 seconds.

I'll attach a pic of mine in a minute. ............

This is just unplugged from the USB cable in the USB socket in the mains wall socket. It's fully charged.

Battery Screen.jpg (113.92 KiB) Viewed 1333 times

If I plug it back into the power -

Battery Screen Plugged In.jpg (143.7 KiB) Viewed 1326 times

The three buttons on the bottom are EXIT, BACK, NEXT.
If you press them it gets into a sequence of displays - go tot he next by tapping the screen.

If you get into a display of slowly expanding coloured concentric rectangles, then press bottom left, top left, top right, bottom right in order.

And don't ask how I managed to find that out.

DPPM is Dynamic Power Path Management - which allows hand held devices to be used eveb when they are charging.
THe screen display is dynamic - so if you plug in the USB cable, it changes immediately to reflect that. I guess that it will also reflect the change when it is attached to the cradle on the bike.

[Stu]

The support and comraderie I get on this forum gives a Garmin product an edge over TomTom but I would certainly look their way.

I'm not starting a TomTom forum either

[Peobody]

Yes, I had looked at the battery diagnostics page. I didn't notice anything unusual. This is with the XT on the bike mount with bike ignition in the On position (but not running).

clipimage.jpg (46.56 KiB) Viewed 1307 times

[Stu]

@Peobody

Go to view map click on the speed in the bottom left press and hold the speed in the top centre for 5 seconds or so

click on developer info then shutdown causes and see if anything in there can shed any light on the situation

I have had mine crash before and not start up properly and had to hold the power button for a long time before it came back to life

Sometimes software can do this

[Peobody]

Thanks @Stu. There is an entry that corresponds with the time of the failure.
The heading is "RTL Trap 0X6e5d8017".
Error type: RTL Trap (whatever that is).
RTL Message: Application suspend.

There are some odd entries.
Error Date: 11-03-23
Error Time: 11:23:19 AM
Boot Date: 11-02-23
Boot Time: 05:46:15 AM (I was asleep)
Uptime: 05:52:12 (Huh? Boot time was 30 hrs prior)

FWIW, there are 5 other "RTL Trap" entries in the list of Shutdown causes.

[FrankB]

Just guessing.

RTL= Run Time Library
"0X6e5d8017" The address in memory where the error occurred