gps, patch, tracking

Turn your Tom Tom GPS into a data logger (tracking device)

I’ve come across a way to enable data logging on the tomtom…. it will allow the unit to log trips in the standard *.gpx* format… then you can open a *.xml* file (found on the device under the folder called “int”) in Internet Explorer that will show your trip overlayed on a google map, it also plots speeds on the map.. direction changes.. rest points etc… could have various uses…. e.g. mapping the boundaries of a farm (by driving around the borner)… it saves the exact gps locations as raw data that can be manually read… or opened into google maps… etc..

The official site can be found here although for those new to this kind of thing it my be a bit complex.

Event_Logger is a tracking and logging application enhancing TomTom GO as well as any all-in-one TomTom GPS device. It can log TomTom GO events to Itinerary files that are managed by TomTom GO like native Itinerary files created through the ordinary user interface; besides, Event_Logger can produce standard GPX XML files where events are represented as waypoints and the whole route is logged through a sequence of track points obtained by querying TomTom GO for location information at short periodical intervals; the produced tracking will result bound to the roads through the assistance of both the TomTom GO mapping and the ASN feature (if active) in order to normalize tracking even without proper GPS reception; other than this default process to produce snapped-to-road GPX tracks, an additional option allows retrieving raw GPS data not intermediated by TomTom GO, useful for off-road tracking and also including altitude; Itinerary records and GPX waypoints take account of boot, resume, suspend events and optionally other information generated by manually tapping on the available (and extensible) logging menu icons. Other than generating Itinerary and GPX files, Event_Logger can create POIs (Points of Interest) for each event (or for a configurable subset).”

Hence to make it easier to setup i’ve done the hard work for you… just download this zip file, then uncompress its contents straight into the main directory of the memory card of your Tom Tom.

HERE IS THE OFFICIAL README INSTRUCTIONS:

“################################################################################
# Event_Logger for TomTom GO – QUICK INSTALLATION GUIDE
# Author: amacri@tiscali.it
# Event_Logger 8.1 – http://web.tiscali.it/macri/Event_Logger
################################################################################
#
# QUICK INSTALLATION AND UPGRADE GUIDE
#
################################################################################

Download software at: http://web.tiscali.it/macri/Event_Logger/Event_Logger-8.1.zip
______________________________________________
Legend:
- TTGO: TomTom GO (any model)
- ‘H:’: example of name of a TTGO file system when mounted to an external system via USB

______________________________________________
Compatibility: NavCore v5.x, v6.x, v7.x for all-in-one TomTom devices (see instructions).

Event_Logger is not compatible with PDA or Symbian devices.

Installing Event_Logger does not compromise and does not degrade the performance of the
normal TomTom operation, even for untested models or versions. Event_Logger can be
deinstalled or deactivated when needed.

______________________________________________
Installation files:
Place the following files in the TTGO SD card (or HD, depending on the models), respecting
cases for all file names and keeping the same directory tree (directories must be created
when not existing)

Program:
o    H:\cleanup.txt (notice that H:\ttn of any previous Event_Logger version must be deleted)
o    H:\Itn\gpx.xsl (should be also copied in all the directories including unzipped gpx files)
o    H:\Tracer\acal
o    H:\Tracer\bsh.bz2
o    H:\Tracer\bz2cat
o    H:\Tracer\Event_Logger.txt
(can be configured through any Windows editor, regardless of DOS or UNIX newlines)
o    H:\Tracer\mkel
o    H:\Tracer\toggledata
o    H:\Tracer\toggledmn
o    H:\Tracer\togglelog
o    H:\Tracer\top
o    H:\Tracer\zip
o    H:\Tracer\wd
o    H:\Tracer\gpsbabel (can be deleted if not needed)
o    H:\Tracer\zip3 (can be deleted if not needed)

Menu entries:
o    H:\SdkRegistry\acal.cap
o    H:\SdkRegistry\logpoi.cap
o    H:\SdkRegistry\logpos.cap
o    H:\SdkRegistry\toggledata.cap
o    H:\SdkRegistry\toggledmn.cap (can be deleted if “Toggle Event_Logger daemon” is unwanted)
o    H:\SdkRegistry\toggletrk.cap (can be deleted if “Toggle GPX Tracer” command is unwanted)
o    H:\SdkRegistry\togglelog.cap (can be deleted if “Toggle Debug Level” command is unwanted)
o    H:\SdkRegistry\top.cap (can be deleted if the “Top” command is unwanted)

Menu icons:
o    H:\SdkRegistry\acal.bmp
o    H:\SdkRegistry\logpoi.bmp
o    H:\SdkRegistry\logpos.bmp
o    H:\SdkRegistry\toggledata.bmp
o    H:\SdkRegistry\toggledmn.bmp
o    H:\SdkRegistry\togglelog.bmp
o    H:\SdkRegistry\toggletrk.bmp
o    H:\SdkRegistry\top.bmp

Notice that H:\Sources (useless on the TomTom) should be deleted from TomTom to save space.
Also Event_Logger.pdf and ReadMe.txt can be safely deleted from the TomTom SD (or HD).
______________________________________________

INSTALLATION NOTES: copy all files (apart from “Sources“ directory, Event_Logger.pdf
and any ReadMe.txt). It is essential preserve the directory structure included in the
ZIP package. Edit Tracer\Event_Logger.txt with any editor (including notepad) and,
above all, check variables TIMEZONE and LANGUAGE. If the Tracer directory is missing
after the archive extraction, repeat the installation procedure preserving the directory
structure. See the Installation paragraph of the documentation for further information.

Verify that toggledmn.cap, toggletrk.cap, togglelog.cap and top.cap are really needed; if
not, remove them from the SdkRegistry directory.

Verify that \Tracer\gpsbabel and \Tracer\zip3 are really needed; if not, remove them
to save space.

UPGRADE NOTES: follow the same instructions of the INSTALLATION NOTES.
o remove H:\ttn (if existing) of any old Event_Logger version (important)
o rename _Logger.itn (if existing) to _Latest_Events.itn
o EventLogger.tgz and Event_Logger.tgz (if existing in “Itn” directory) can be moved in
Itn\Bkp directory (can be created if not existing, otherwise Event_Logger automatically
creates it).
o “Track” directory (inside “Tracer” directory) is no more used (can be archived and deleted)
o expr in the “Tracer” directory (if still existing) can be removed.
o    If using POIs, rename Tracker.ov2/Tracker.bmp (if existing) to POI_Tracker.ov2/POI_Tracker.bmp
See the Installation paragraph for further information.

FURTHER INSTALLATION NOTES:
o Notice that there is no specific switch for daylight saving, which must be managed changing
the TIMEZONE variable accordingly.
o    IMPORTANT WARNING: do not forget to copy the file named “cleanup.txt” to the root of the
SD or HD.
-    IMPORTANT WARNING: Do not exceed the maximum number of 10 “.cap” files in the “SdkRegistry”
directory.
o Verify that Debug is set to 0 inside Event_Logger.txt. If any of the files ttnlog-<date>.txt,
TtnLog.txt, TrxLog.txt, trxlog-<date>.txt are available in the Tracer directory, this means
that the Debug flag was not set to 0 in a previous Event_Logger version; all these files can
be safely deleted to save space; anyway, before deleting them, with the WordPad editor please
check the presence of the string _Event_Logger_Script_ERROR_ inside each of them; if this
string exists, email the files to amacri@tiscali.it in order to facilitate bug fixing.
o in case H:\cleanup.txt is already existing because a different SDK program is
installed, add the following line to the existing file instead of replacing it:
daemon|Tracer/mkel|
(NOTE: The H:\cleanup.txt file must only have one recurrence of the previous command)

In case there is a tomtom.mnu files available in the SdkRegistry directory of TTGO,
that file should be modified in order to include the new SDK entries (see Event_Logger.pdf
for further information). Notice that this file introduces limitations with NavCore 7.

Setting the owner’s preferences (a specific menu of TomTom) is discouraged with firmware version
6.210 (it might freeze SDK functions until the “Continue” button is pressed). Other v.6 versions
are untested against this issue.

A random menu reset to the initial menu page might happen while navigating into the menus
(typically after powering the device on; this is due to a small glitch in the TomTom
application while processing the Event_Logger command changing night/day colours).
________________________________________________

Donations are more than happily accepted! Event_Logger took a lot of days of development
within two years, as well as large number of testing and user support; if you really like
this software, you are kindly invited to send donations; email to amacri@tiscali.it with
subject Donation to know how to perform this.

Thanks

amacri”

Yeah it is a bit Techy… take a bit of reading… but once you get it all loaded on its easy enough to use…

an example of what it can achieve (i.e. the files it produces in the “itn” directory) can be found below…

click the link (its hosted on my home server – which isn’t always online):

Trk_08-07-09_12-04-40.xml

and it shows you one of the routes i took and plots it… (It only works with Internet Explorer… and you click yes to all the popups asking about “allowing” Active X scripts…)

Good luck!

About these ads
Standard

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s