Link URL:

Only the registered members can see the Link URLs. Please Login OR Register.

Beside the error case, I can see this watchdogtrace.dat file is also updated with data, without reporting any fault, everytime my Tomtom (GO920) is manualy reset or connected to a PC.
This file can be safely removed, it will be created by the application as necessary.
To not having this file created or updated, the watchdog can be disabled, but, in this case, the Tomtom will not restart itself in case of application error.

Watchdog is term used in scripting ( (de ) compiling )
Leave it alone if don't know what that means

So (after a quick google) it's basically just a monitoring/logging method which can help reboot if the device crashes or needs to restart but does NOT report anything back to TT?

I have removed it from my 720T no problems so far

Do not worry about it Dave. It makes no difference to rebooting on an error. It is just monitoring file that TT may wish you to send to them if you have serious issues. They use their own hex coding of any issues, but it may point a finger to where they need to do some work.

We used to employ a similar strategy at the bank when trying to ascertain cause of probems
You can delete it safely enough. Most are not error codes, just showing what happens when you boot system.

And you need not worry about pluserror.txt either - ctrl a, delete save is fine too.

One serious word of caution which few ever mention. From time to time, it is a good idea, to fully back up your unit, and your SD Card or whatever to a known location. Delete the contents of your unit and card, preferably by formatting them, and then copying the contents back.

Just because they are solid state memory devices, they still suffer from file fragmentation. Over a period, this can make loading of maps significantly slower and of course if any corruption occurs, make lead to the recycling reboot. Seriously, if you are travelling with your unit, it makes sense to have few maps on your unit/memory card. At home, a different story. Like me, you may be using a 64GB USB stick with all the available maps - usually the emulator is more forgiving than the unit itelf, so beware. Also booting up your unit takes longer as it checks every map directory you own, or nicked (experiement with)

In a similar vein, remember the memory effect of NiCd batteries? Many of us have new units using Lithium Ion or Lithium Polymer batteries. So you have your unit powered in your vehicle whilst driving, and you attach it to the USB port when you are at home or in a hotel. Well over a period, the length of time it is effective when not attached to power input does go down. Easily fixed, let it totally discharge from time to time. Even turning it on when it has switched off when the battery is low will help. Then charge over 2 complete charging cycles. You will be amazed at the extra battery power you just reinstated.

Sometimes, you just have to replace the battery. NiMH handle approximately 1000 full charge cycles. Lithium Ion and Lithium Polymer batteries will handle many more, until the charging circuit within the battery gets goosed. (My Psion Series 7 is still good for 8 hours, and that battery is from 1999)

My company sells in excess of 40 million batteries a year, 20 million of which are AA and AAA. We do not sell Tomtom compatible replacement batteries, but should you need them and cannot be bothered to source them yourselves, you may PM me for a reliable company that does. You may wonder why two leading manufacturers of batteries advertise greatly, yet one of the major suppliers to industry never has to!


Dave or Yuri, you may edit this and put in threads of more relevance mates.

add to what he says, the Maverick
Watchdog is TT tracker when the device starts booting and detects any fayo, reboots or does not work very well generates the report listing errors can be patched by bad navcore, file corruption, lack of RAM, map error, etc ....
as stated above can be deleted, but I advise is to clear after you resolve the error has a clean installation.
regards

Good point simba. I meant to add that it should not be deleted whilst one has problems, but a day or so after the event, when things are fine.