EVENT_LOGGER FOR TOMTOM GO
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Event_Logger
for TomTom GO
http://web.tiscali.it/macri/Event_Logger
Event_Logger for TomTom GO
Summary
1. Introduction............................................................................................................................................. 3
2. What's new ............................................................................................................................................. 5
2.1. What's new in 8.1 ............................................................................................................................ 5
2.2. What's new in 8.0 ............................................................................................................................ 5
2.3. What's new in 7.2 ............................................................................................................................ 6
2.4. What's new in 7.1 ............................................................................................................................ 7
2.5. What's new in 7.0 ............................................................................................................................ 7
2.6. What's new in 6.5 ............................................................................................................................ 8
2.7. What's new in 6.4 ............................................................................................................................ 8
2.8. What's new in 6.3 ............................................................................................................................ 9
2.9. What's new in 6.2 ............................................................................................................................ 9
2.10. What's new in 6.1 .......................................................................................................................... 9
2.11. What's new in 6.0 .......................................................................................................................... 9
2.12. What's new in 5.9beta ................................................................................................................... 9
2.13. What's new in 5.8beta ................................................................................................................. 10
2.14. What's new in 5.7beta ................................................................................................................. 10
2.15. What's new in 5.6beta ................................................................................................................. 10
2.16. Features available in release 5.4beta.......................................................................................... 10
2.17. Features available in release 5.2beta.......................................................................................... 10
2.18. Previous versions ........................................................................................................................ 10
3. Function list .......................................................................................................................................... 10
4. Menu Buttons and Icons....................................................................................................................... 11
5. Examples.............................................................................................................................................. 13
6. GPX Tracking System .......................................................................................................................... 16
7. Itinerary file format................................................................................................................................ 22
8. Astronomical data................................................................................................................................. 24
9. Event_Logger GPX Browser ................................................................................................................ 26
10. Compatibility ....................................................................................................................................... 34
11. Installation .......................................................................................................................................... 35
12. Configuration ...................................................................................................................................... 38
13. Localization......................................................................................................................................... 39
14. Altitude and distance calibration......................................................................................................... 40
15. Basic usage ........................................................................................................................................ 41
16. Aggregate Records............................................................................................................................. 41
17. Points of Interest................................................................................................................................. 42
18. Logging details ................................................................................................................................... 42
19. Management of old information .......................................................................................................... 44
20. Directories, pathnames and temporary resources.............................................................................. 45
21. Calling Event_Logger ......................................................................................................................... 45
22. Current limitations............................................................................................................................... 46
23. Technical information related to the Menu Buttons ............................................................................ 46
24. Customizing TomTom menus............................................................................................................. 46
25. Performance, tracing and profiling...................................................................................................... 47
26. Privacy concerns ................................................................................................................................ 48
27. How to remove Event_Logger (data and executables) ...................................................................... 51
28. Development Guide............................................................................................................................ 51
28.1. Testing Event_Logger with Cygwin ............................................................................................. 51
28.2. Notes on TomTom ....................................................................................................................... 53
28.3. BSH interpreter ............................................................................................................................ 55
28.4. Customizing the BSH interpreter ................................................................................................. 81
29. Acknowledgements and references ................................................................................................... 83
30. Brand Name ....................................................................................................................................... 85
31. Disclaimer of warranty and license conditions.................................................................................... 85
Page 2 of 86
Event_Logger for TomTom GO
Event_Logger
for TomTom GO
Version 8.1
related pressure is logged by Event_Logger.
1. Introduction Besides, Event_Logger automatically defines
Event_Logger is a tracking and logging a new path each time the TomTom device is
application enhancing TomTom GO as well switched off and then switched on again after
as any all-in-one TomTom GPS device. It can six minutes or more. If the docking station is
log TomTom GO events to Itinerary files that connected to the vehicle ignition, the driver’s
are managed by TomTom GO like native interaction with the vehicle will automatically
Itinerary files created through the ordinary raise ‘resume’ and ‘suspend’ events, caught
user interface; besides, Event_Logger can by Event_Logger. This means that each
produce standard GPX XML files where ignition will automatically catalogue a new
events are represented as waypoints and the path (unless a short break is performed).
whole route is logged through a sequence of
track points obtained by querying TomTom A boot happens when the user manages the
GO for location information at short periodical USB, the SD Card as well as the reset hole
intervals; the produced tracking will result on the unit’s bottom (the last action also
bound to the roads through the assistance of resets the TomTom GO system clock); boot
both the TomTom GO mapping and the ASN events are accounted by Event_Logger too.
feature (if active) in order to normalize
tracking even without proper GPS reception; All Itinerary records include date and time of
other than this default process to produce each event occurrence as well as the
snapped-to-road GPX tracks, an additional associated duration data and possibly the
option allows retrieving raw GPS data not current position, altitude, speed, course and
intermediated by TomTom GO, useful for off- address. Depending on Event_Logger
road tracking and also including altitude; configuration settings (e.g., snap-to-road/off-
Itinerary records and GPX waypoints take road) and on the NavCore version, GPX data
account of boot, resume, suspend events and can potentially deal with all parameters
optionally other information generated by produced by the GPS device, including also
manually tapping on the available (and number of used satellites, HDOP, PDOP,
extensible) logging menu icons. Other than VDOP, magnetic variation (when available)
generating Itinerary and GPX files, and geoid separation (see related
Event_Logger can create POIs (Points of description).
Interest) for each event (or for a configurable
subset). A special selection activates a snapshot
report displaying advanced statistics related
The production and archiving of Itinerary and to the current trip, also including slope
GPX tracks is completely automatic; no user computation. An additional panel included in
intervention is needed to regularly split files Event_Logger provides an astronomical
upon new paths, save and catalogue them as calendar in textual format where data depend
well as store old information in compressed on the current local time and position.
archives. The history of all travelled paths Besides, switching between day and night
can be accessed by browsing the Itn colours of TomTom GO is automatically
directory of the SD card (or HD). performed according to the elevation of the
sun.
As the power button of TomTom GO is
actually a suspend/resume button, any
Page 3 of 86
Event_Logger for TomTom GO
For instance, Event_Logger helps answering Event_Logger today delivers the most
the following questions: comprehensive set of functionalities that
complement TomTom and is a reference for
o What itinerary did I travel yesterday? independent tools on top of the TomTom
o When did I start driving this morning? firmware and of the NavCore application.
o How long did I take?
o Which is the current altitude and Differently from the majority of similar
speed? applications, Event_Logger also provides
o How can I remind precise positions? fully commented source code, allowing
o When exactly I travelled there? verification of the implementation quality and
o Which is the altitude of this place? sharing the innovation; with its pervasive
o Which was the maximum uphill and documentation including development guide,
downhill slope of my previous trip? Event_Logger not only details functions and
o Where is the moon now? customisation aspects to users, but also is a
And so on. common reference for independent
developers. Great care was taken in
The GPX files collected by Event_Logger preparing the whole documentation,
allow performing any kind of post-processing, constantly updated upon each release of new
batch analysis, statistics and file conversion features.
together with XSLT stylesheets or external
applications (file converter, GIS, mapping and Pioneering the methods to add software into
analysis tools running on PC or legacy the TomTom device, Event_Logger was the
systems). first to automatically intercept and log
TomTom events like “switch on”, “switch off”
An XSL file included with Event_Logger and “boot”, exploiting them in a core
allows Internet Explorer to automatically functional process that is able to
transform each GPX file into an HTML automatically split trips through the analysis
interactive report with zoomable graphical of the switch off time; any derived process of
map from Google Maps, including coloured Event_Logger is based on this automation;
tracks and fully clickable waypoints; the map this provides great help to users which have
provides advanced functionalities and is not to remind to manually mark the beginning
followed by detailed tables analyzing almost of a new trip. This method, which is
all data registered inside the GPX file, with innovative on a TomTom device, has been
computation of distance, speed, altitude and inspired from the behaviour of software
slope related to each fix, segment, trace or odometers embedded in some vehicles.
whole file. Each table can be easily imported
to Excel. Besides, two delimiters can be Event_Logger perfectly harmonizes with
easily set over the map in order to allow TomTom, avoiding any redundant information
interactive trip analysis. already provided by the standard application
and introducing a lot of additional trip based
Event_Logger virtually supports any all-in- data to users; it was the first application to
one GPS TomTom device and is designed to successfully interface NavCore through its
be independent from specific models (e.g., “file transportation layer” without requiring the
display size and geometry), firmware SDK platform; the result was the
versions (including NavCore v7) and GPS implementation of a free method which allows
device (SiRF Star II, SiRF Star III, Star SiRF NavCore to display messages and to retrieve
III with QuickGPSfix and Global Locate's normalized fixes through the TomTom map
Hammerhead GPS units are all supported). assistance (the basis of the “snap-to-road”
method). Event_Logger was also the first
The subsequent chapters describe all these application exploiting the Itinerary
functionalities in detail. management of TomTom, to allow user
Page 4 of 86
Event_Logger for TomTom GO
reading externally collected fixes through the compression, please verify that a modern UnZip
program with bzip2 support will be used to read the
NavCore function “Itinerary Planning”, resulting zip archives so that entries compressed
introduced with NavCore 5. with bzip2 can be read. Set “Bzip=9Zbzip2
ZipExec=zip3” in the configuration section to enable
bzip2 compression.
Besides, Event_Logger first introduced GPS • Now Event_Logger can automatically create an
tracking and since the beginning adopted the optional Itinerary file (ITN) and an optional POI file
GPX standard; it is also the only application (OV2) including detailed tracking of each travelled
route (e.g., basing on each produced GPX file and
providing both “snap-to-road” and “off-road” transforming it through GPSBabel). Both ITN and
collection methods. OV2 tracks can exploit a simplification method
which removes points that have the smallest effect
on the overall shape of the route; this filter is
With the goal to allow smooth execution into particularly important for ITN files, because
the limited resources of embedded systems NavCore allows browsing only the first 48 lines of
(CPU, RAM memory, SD memory), them. Check ItnTrkPt and Ov2TrkPt variables to
enable these transformations and control the
Event_Logger singularly implemented the simplification factor. Enable this feature only if
functional process through scripting and the really needed: each file generation takes some
building blocks by extending an efficient seconds to the power-on, power-off and boot
interpreter with C functions; zsh was selected procedures; consider that these files can
as the basis for the script interpreter, not only always be manually generated basing on
XML/GPX tracks.
because much tinier and lighter than external • Corrected bug related to NoWatchDog=yes when
perl or java portings, but also because it running NavCore 7, that was causing cyclic
outperforms the system tools available inside reboots; now NoWatchDog=yes should inhibit all
unattended reboots even with slow TomTom
the TomTom firmware; a considerable set of devices or SD memories. Besides, a specific
customizations have been applied to zsh in description on how to manage possible cyclic
order to increase functionalities and in reboots after the initial Event_Logger installation
has been added in the Installation chapter.
parallel to further reduce its executable size. • Corrected bug causing wrong computation of
Event_Logger also integrates the infoZIP motion duration.
archiver into an unmatched functional • Corrected bug in GPX.XSL related to the rendering
management process to classify and of distance calculations in case of initial GPX
segment with zero elements.
incrementally save data on the SD card. The • Removed a bug preventing correct renaming of ITN
result is an architecture that provides robust and GPX archive backups.
functionalities without introducing • Now splash messages more appropriately manage
TomTom screens with different sizes.
performance degradation. • Corrected mistype in icons.
• Documentation corrected and updated.
Notice that it is mandatory to carefully
INSTALLATION AND UPGRADE NOTES: same as in
read and accept the disclaimer of “What's new in 7.2” below.
warranty and license conditions at the end
of this document before downloading and Donations are more than happily accepted!
Event_Logger took a lot of development time, as well as
using Event_Logger. large number of testing and user support; if you like this
software, you are kindly invited to send donations; email
to amacri@tiscali.it to know how to perform this.
2. What's new 2.2. What's new in 8.0
(January 20, 2008)
2.1. What's new in 8.1 This version includes minor changes and corrections versus
7.2.
(March 11, 2008) • Corrected bug in SirfBinToAscii (bsh) setting some
This version includes the following changes and corrections latitudes or longitudes to zero
versus 8.0. • Corrected bug in geoid (bsh) not accepting
• Optional support of the bzip2 compression method longitude values between +/-90 and +/-180 degrees
in zip files produced by Event_Logger (often gives a • Corrected bug in Event_Logger.txt resetting
better compression ratio than standard zip deflate, GeoidSeparation (altitude shift issue)
at the cost of greater CPU time). Before using bzip2
Page 5 of 86Event_Logger for TomTom GO
• Corrected bug in Event_Logger.txt when computing apart from enabling the off-road option from the related
altitude in feet (besides, altitude computation in menu button.
GPX files has been slightly improved) • Support of TomTom devices hosting Hammerhead GPS
• Corrected bug in GPX.XSL related to the rendering unit.
of time calculations in case of initial GPX segment • A further tuning has been performed to the NMEA driver
with zero elements. which decodes information produced by TomTom
• Now the Astronomical Calendar has an increased devices and now GPX files should always include
timeout for the fix retrieval operation; besides, the PDOP, VDOP, HDOP and Number of satellites in each
fix retrieval to start the Astronomical Calendar also GPX fix.
exploits the direct GPS device interface if NavCore • Slope computation has been added, including
fails to provide data via SDK. instantaneous slope, average slope for the last stretch
• Now, when the "advanced statistics" splash screen of the path, maximum downhill and uphill slope, all
is selected, no event is recorded unless the accurately tuned for pretty reliable values. These
IgnLongList variable is set to yes. parameters are included in the Event_Logger advanced
• Added WaitBeforeHold variable related to the statistics pop-up, which is the splash screen shown after
"advanced statistics" splash screen, which allows selecting "Log Position to Itinerary" and when then
configuring the timeout in seconds to keep the keeping the touchscreen pressed for more than five
touchscreen pressed before the splash is frozen, so seconds. Max uphill and downhill slope values also
that the finger can be immediately released with the appear in the tag of the GPX file.
splash frozen if WaitBeforeHold=0 (as usual, a • As many users found difficulties in opening GPX files
second pressure will make the splash disappear). with Internet Explorer, now a new configuration setting
• Documentation corrected and updated. allows saving GPX track files with either the “.gpx” or the
“.xml” extension. By default, the latter is configured
INSTALLATION AND UPGRADE NOTES: same as in (rather than the previous versions, where .gpx was
“What's new in 7.2” below. used), enabling easy GPX browsing: Internet Explorer
opens XML files and automatically starts the XSL parser
when the file “gpx.xsl” is available in the same directory
of the GPX/XML files. Check the GpxFileExt variable in
2.3. What's new in 7.2 the configuration section of Event_Logger to select the
wanted extension type. Notice that switching among the
(December 30, 2007) two extensions is a standard rename operation, which
This version could be considered like a major upgrade for can be manually accomplished by any user in any
the relevant enhancements included. The most noticeable moment. Besides, an Event_Logger function
one is the support of virtually all the TomTom devices now automatically renames un-archived GPX files (the last
available, including the various embedded GPS units and five ones by default) according to the value set in the
also NavCore 7 (with some limitation; ref. to the GpxFileExt variable.
“Compatibility” paragraph). Considering the occasionally • GPX files can now be correctly edited with notepad,
very slow SDK API response of NavCore 7 used by because the DOS/Windows - character
Event_Logger in snap-to-road mode, a specific feature (that sequence is used for line separator. A new CR0 variable
can be configurable) automatically gets positioning has been introduced for this; it can be configured for
information from the GPS when NavCore 7 does not provide Windows or UNIX formats.
any answer within a predefined timeframe. All other changes • Previous version 7.1 reported the issue to lock the
are described here below. TomTom auto-reboot when extracting the SD card or
• Setting the GeoidHeight variable is no more needed: for when connecting the USB; this is a side effect of
older TomTom devices, this value is now dynamically disabling the kernel watchdog feature (thanks Franz
calculated by Event_Logger basing on latitude and Haas of the OpenTom list for this hint), which
longitude; besides, for newer models, this value is sometimes happens to generate a device reboot when
directly generated by the internal GPS device and Event_Logger takes too many seconds to perform its
fetched by Event_Logger. The algorithm used by internal operations (e.g., including archiving, file backup
Event_Logger exploits a function available in the GPSD and zip compressions); notice this should never happen
project (http://gpsd.berlios.de/). Basing on the in normal operation, but only in debug mode, e.g., when
automatically computed values, GeoidHeight is still in resuming while tracing at level 5. Now this no-watchdog
place (and defaulted to 0) to allow statically setting a setting is configurable and by default is disabled
further translation correction, when really needed. As a (watchdog enabled, WatchDog=yes). If some user
reminder, the altitude is logged only when the off-road happens to verify reboots once in a while and wants to
options are selected (not the snap-to-road ones). ensure avoiding them, the WatchDog variable in the
• Now an important limitation of the off-road feature of configuration section can be set to no (and it needs a
Event_Logger has been removed; it prevented retrieving manual reboot via suspend button after inserting the
direct information from the GPS devices in newer USB cable or extracting the SD card).
TomTom models, e.g., those ones hosting a SiRF Star • Now each single backed-up archive inside itn\Bkp will
III GPS unit which is set to use the SiRF binary protocol never exceed a predefined size (which is configurable
rather than the NMEA one. Event_Logger can now auto- for Itn and Gpx types) in order to prevent too slow
detect the GPS unit type and decode both NMEA and update operations. This should avoid that an automatic
binary SiRF frames, managing the off-road feature for reboot might happen while resuming.
any TomTom model; this allows tracking real • New button icons are available, thanks to Herbert
coordinates, altitude, number of satellites and position Macho. The installation package also includes
error estimations with no specific configuration to apply, alternative TomTom button icons in a separate directory
Page 6 of 86Event_Logger for TomTom GO
(provided by Herbert Macho and by Francesco used: they can be archived out in the Bkp directory; “Track”
Bombassei); simply select the icons you prefer. directory (inside "Tracer" directory) is no more used (can be
• The accuracy of distance computation has been saved out and then deleted); expr in the "Tracer" directory (if
improved by ignoring fixes with HDOP = 20 or greater. still existing) can be removed. Edit Tracer\Event_Logger.txt
• Now the radius of the Earth has been set to 6378.137 with any editor (including notepad) and, above all, check
kilometres (E_RADIUS variable) in the Event_Logger variables TIMEZONE and LANGUAGE. If using POIs,
configuration, in order to produce values compatible rename Tracker.ov2/.bmp (if existing) to
with Google Maps. POI_Tracker.ov2/.bmp. See the Installation paragraph for
• Removed a bug preventing ITN and GPX archiving in further information.
some cases.
• Removed rare syntax bugs in GPX tracks (now GPX Verify that Debug is set to 0 inside Event_Logger.txt. If any
files should always be syntactically correct or 'well of the files ttnlog-.txt, TtnLog.txt, TrxLog.txt, trxlog-
formed', e.g., should never generate errors when .txt are available in the Tracer directory, this means
opened with Internet Explorer). that the Debug flag was not set to 0 in a previous
• Reduced refresh rate in the Astronomical Calendar, Event_Logger version; all these files can be safely deleted to
allowing improved readability. save space; anyway, before deleting them, with the
• Now bsh and zip (Info-ZIP) are compiled optimizing WordPad editor please check the presence of the string
performance (-O3) rather than size (-Os). _Event_Logger_Script_ERROR_ inside each of them; if this
• Minor bug fixing. string exists, email the files to amacri@tiscali.it in order to
• Revised documentation. facilitate bug fixing.
• New BSH commands: SirfEnvelope, SirfBinToAscii,
dumps and geoid (see documentation, in the last part of FURTHER INSTALLATION NOTES:
the development section). - Do not forget to copy the file named “cleanup.txt” to the
• Further improvement to the Google Maps integration of root of the SD or HD. If this file already exists, see the
the GPX browser, with a number of relevant additions Installation paragraph for further information.
included in GPX.XSL: - Do not exceed the maximum number of 10 “.cap” files in
1. Automatic management of locale settings (with the “SdkRegistry” directory.
very limited need of configuration) - Setting the owner's preferences (a specific menu of
2. Local search component, which can be TomTom) is discouraged (it might freeze the TomTom
activated via key S or through the options SDK functions until the "Continue" button is pressed).
panel (see documentation)
3. New map layers (including other 13 maps from
- A random menu reset to the initial menu page (e.g.,
page 1) might happen while navigating into the menu
external providers other than the three
pages (typically after powering the device on; this is due
standard Google maps types) and online
to a small glitch in NavCore while processing the
altitude retrieval for any selected point
Event_Logger command changing night/day colours).
4. Support of the new Google Map Layer named
“Terrain”
5. Fixes are now highlighted with small coloured 2.4. What's new in 7.1
square blocks than square icons, highly
improving performance and allowing a wider
(June 11, 2007)
default of concurrently managed fix elements.
• Significantly improved browsing of GPX files with the
6. All waypoint markers can be dragged to
addition of interactive analysis through Internet Explorer.
improve readability, especially in case they are
overlapped. Delimiters can also be dragged. • Slightly revised behaviour of “Toggle snap-to-road or
7. Now all shown graphic elements have a tooltip. raw GPS” button.
8. Simplified management of X key. • Some bug fixed (now the produced GPX file is always
9. New blue colour for the “delimiter” markers. browsable with Internet Explorer and the
10. Minor additions and fixes. suspend/resume operations are a bit more robust when
11. Tested to also run inside Firefox through the IE the trace/profiling level is maximized).
Tab addon http://ietab.mozdev.org. • Revised documentation.
INSTALLATION NOTES: copy all files (apart from “Sources“ INSTALLATION AND UPGRADE NOTES: same as in
directory, Event_Logger.pdf and any ReadMe.txt). It is “What's new in 6.5” below.
essential to preserve the directory structure included in the
ZIP package unaltered. Edit Tracer\Event_Logger.txt with 2.5. What's new in 7.0
any editor (including notepad) and, above all, check
variables TIMEZONE and LANGUAGE. If the Tracer
directory is missing after the archive extraction, this mean (March 17, 2007)
that the directory structure of the package has not been • When opening the GPX files with Internet Explorer (e.g.,
respected. See the Installation paragraph for further "Open with… Internet Explorer" or drag and drop a GPX
information. file to IE), Google Maps is started inside the browser,
graphically representing the recorded path, together
with many additional tables of statistics about the trip.
UPGRADE NOTES: replace all files (apart from “Sources“
Check to be connected to the Internet and that "gpx.xsl"
directory, Event_Logger.pdf and any ReadMe.txt); remove
is available in the same directory of the new gpx files.
H:\ttn (if existing) of any old Event_Logger version
• Event_Logger can calculate the travelled distance (km
(important), then rename _Logger.itn (if existing) to
or miles) while producing GPX logging; consequently,
_Latest_Events.itn; files EventLogger.tgz and
the average speed of a trip (km/h or miles per hour) and
Event_Logger.tgz (if existing) in “Itn” directory are no more
Page 7 of 86Event_Logger for TomTom GO
other new statistics can be produced. Besides, the GPX
agent can trace the max and min altitude (meters or INSTALLATION AND UPGRADE NOTES: same as in
feet) as well as the motion duration (minutes) and max. “What's new in 6.4” below.
speed. Verify that Debug is set to 0 inside Event_Logger.txt. If any
• When selecting "Log Position to Itinerary", a new mask of the files ttnlog-.txt, TtnLog.txt, TrxLog.txt, trxlog-
can be activated by keeping the pop-up message .txt are available in the Tracer directory, this means
pressed for some seconds. The new splash page shows that the Debug flag was not set to 0 in a previous
advanced statistics related to the current trip. As soon Event_Logger version; all these files can be safely deleted to
as the touchscreen is released, the mask disappears save space; anyway, before deleting them, with the
unless the screen is kept pressed for additional five WordPad editor please check the presence of the string
seconds: in the latter case the mask remains frozen on _Event_Logger_Script_ERROR_ inside each of them; if this
the screen until a new pressure is performed. string exists, email the files to amacri@tiscali.it to facilitate
• The GPX logging and GPX segmentation have been bug fixing.
improved, with more precise timings and values. The
process also monitors possible cases of wide distance
between adjacent fixes, reporting conditions of nearby 2.7. What's new in 6.4
or faraway restarts (the former as new segment, the
latter as new track). (July 25, 2006)
• Event_Logger now allows promiscuous usage; an • Added off-road option to the GPX Tracker in order to
appropriate chapter describes how to properly configure allow processing data directly fetched from the raw GPS
the application. GPX and ITN generation can be device (through the NMEA driver of Event_Logger).
disabled, with decoupled behaviour to the day/night Check TTGOtoGPX and GpsToGPX variables for this;
colour switcher. Besides, ITN and GPX archives can tracking can be tuned through TrackingGranularity and
now include password protected files. DelayToBreakTracks (representing intervals in
• ITN and GPX archives now take advantage of an seconds). (Off-road setting means GpsToGPX=yes,
additional automatic backup copy of old archives inside TrackingGranularity=5, DelayToBreakTracks=180).
the Bkp directory; this improves resilience in case of • Improved GPX Tracker with superior accuracy; each
fault while producing a ZIP archive. now includes geodecoded data; The NMEA driver
• Event_Logger has been further tuned for performance has been enhanced to support additional messages and
with NavCore version 6.520 (SpeedNotAvailable names.
variable is now set to yes, disabling the related NMEA • Revised framebuffer and touchscreen calls in fb.c, (but
feature). without embedded touchscreen calibration); a printf
• The “Toggle GPX Tracker” icon is revised not to wrapper is included, supporting bold attribute,
interfere with the day/night colour switcher. A new icon ink/background/numeric colours, configurable shifts and
"Toggle Event_Logger Agent" in now available, with ISO-8859-1 charset. Associated refinements in Top,
similar functions to what available in previous versions. Astronomical Calendar, bsh.
(It is not really useful, so not suggested to be installed • Slight revisions in Event_Logger.txt (added Norwegian
for normal operation.) language; now GeoidHeight supports decimals; other
• A bug introduced with version 6.5 about archiving old refinements)
Itinerary files is now fixed. Other minor bugs have been • Tested with TomTom GO version 5.450.
fixed. SyncTime capability has been restored. • Ported and tuned to NavCore 6.120. Due to v6 busybox
• The documentation has been revised in all parts. limitations, archiving is completely revised: the “Track”
directory is no more used (can be saved out and then
INSTALLATION AND UPGRADE NOTES: same as in deleted). All ITN and GPX files are now stored in “itn”
“What's new in 6.5” below. directory, including related archives (ItnArchive.zip and
GpxArchive.zip) which are compressed in standard ZIP
format (gzipped tar format is no more used). NavCore 6
2.6. What's new in 6.5 automatically syncs Linux time to UTC; by consequence
of this, browsing SD (or HD) files through a PC will
(November 12, 2006) produce “last modification times” set to UTC time zone
• Ported to NavCore 6.140, 6.150 and 6.520. (not local times); this feature is correctly managed by
• Fixed bug when setting negative values of GeoidHeight. Event_Logger 6.4.
• Improved NMEA driver including validation of the • Revised documentation:
commands generated by the GPS device through the • new information related to the additional features of
new NmeaChkSum function added in BSH. this version and specifically to the GPX format;
• GpxFileName variable with revised format in order to • Added mention of GPSBabel, a conversion tool
avoid two dots in GPX files, for better Google Earth which can be used to translate the GPX files
compatibility produced by Event_Logger into many different
• Debug now defaulted to 0 (it was set to 2 in version 6.4). output formats;
• SyncTime capability is now disabled for better • for developers, revised usage of zstat, framebuffer
compatibility with NavCore 6. and touchscreen (now ts_press automatically
• NewGpxWhenDateChanges changed to removes bounces with no need of additional
NewGpxWhenDateAdjusted in order to avoid confusion. coding).
• Added Dutch translation.
• All programs recompiled with the latest TomTom INSTALLATION AND UPGRADE NOTES: replace all files
toolchain. (apart from Sources directory, Event_Logger.pdf and any
• Some errors corrected in the documentation. ReadMe.txt); remove H:\ttn (if existing) of any old
Event_Logger version (important), then rename _Logger.itn
Page 8 of 86Event_Logger for TomTom GO
(if existing) to _Latest_Events.itn; files EventLogger.tgz and (Apr 11, 2006)
Event_Logger.tgz (if existing) in “Itn” directory are no more • Corrected GPX bug occurring when coordinates are
used: they can be archived out and then deleted; “Track” smaller than 1 degree.
directory (inside "Tracer" directory) is no more used (can be • Fixed TIMEZONE bug.
saved out and then deleted); expr in the "Tracer" directory (if • Corrected a small bug preventing VERSION expansion
still existing) can be removed. Edit Tracer\Event_Logger.txt in GPX headers.
with any editor (including notepad) and, above all, check • Further performance improvement (sleep builtin
variables TIMEZONE, LANGUAGE and GeoidHeight. If command of BSH now accepts decimals).
using POIs, rename Tracker.ov2/.bmp (if existing) to • Updated documentation.
POI_Tracker.ov2/.bmp. See the Installation paragraph for Upgrade note: same as in “What's new in 6.0” below. For
further information. programmers: usage of “ts_press” is discouraged in this
Do not exceed the maximum number of 10 “.cap” files in the version.
“SdkRegistry” directory.
Setting the owner's preferences (a specific menu of
TomTom) is discouraged with NavCore 6.210 (it might freeze 2.11. What's new in 6.0
SDK functions until the "Continue" button is pressed).
A random menu reset to the initial menu page (e.g., page 1) (Apr 6, 2006)
might happen while navigating into the menu pages (typically • Now Event_Logger.txt can be configured with any
after powering the device on; this is due to a small glitch in editor including notepad.
NavCore while processing the Event_Logger command
• Simplified timezone setting.
changing night/day colours).
• Performance enhancements. The busybox ash
interpreter as well as the external expr command are no
2.8. What's new in 6.3 more used by Event_Logger, which now exploits a new
265KB shell (called bsh, with sources and programming
manual included) based on zsh 3.0.5
(May 20, 2006)
(http://www.zsh.org) and implemented by simplifying
• Fixed a display bug with RIDER (e.g., now Top, the original zsh code from one side and extending it
Astronomical Calendar and splash messages are from another. The Event_Logger script (now called
correctly shown on the screen of the RIDER). Now the Event_Logger.txt and placed inside the Tracer
display should support any TomTom model, including directory) was ported to efficiently support bsh.
those with increased screen sizes.
• Improved tracking accuracy.
• Corrected small bugs in Astronomical Calendar
• Bug fixing and further tuning for TomTom GO version
(computation of moonrise and moonset; slightly
5.420 and 5.440.
improved descriptions). Added horizontal coordinates of
• The new “Top” menu button is now available, producing
the moon.
the same output of the UNIX top command: it
Upgrade note: same as in “What's new in 6.2” below.
continuously monitors the system until the touchscreen
is pressed.
2.9. What's new in 6.2 • Updated documentation.
NOTE: Upgrade by replacing all files; then rename
_Logger.itn to _Latest_Events.itn and EventLogger.tgz to
(May 6, 2006)
Event_Logger.tgz in the “Itn” directory; expr in the "Tracer"
• Corrected a bug preventing Bluetooth to work.
directory can be removed. Check above all variables
• Fixed ts_press bug in bsh.
TIMEZONE, LANGUAGE and GeoidHeight. If using POIs,
• Improved pen management in “top” command; added rename Tracker.ov2/.bmp to POI_Tracker.ov2/.bmp. See the
“df” command (disk free) too (keep the screen pressed Installation paragraph for further information. NOTE: do not
for more than 5 sec.). exceed the maximum number of 10 “.cap” files in the
• Corrected small bugs in GPX description fields. “SdkRegistry” directory. For programmers: usage of
• Further tuning for TomTom GO version 5.440. “ts_press” is discouraged in this version.
• Added Astronomical Calendar.
• Added Automatic Switching between Night and Day
colours basing on the elevation of the sun (original idea 2.12. What's new in 5.9beta
by ScaredyCat).
• Updated documentation. (Jan 9, 2006)
• Revised installation process. • Added geoid height correction constant, to be manually
NOTE: Upgrade by replacing all files; remove H:\ttn (if edited in order to generate Mean See Level altitude
existing) of any old Event_Logger version (important), then (TomTom GO GPS does not support geoid separation:
rename _Logger.itn to _Latest_Events.itn and altitude values returned by NMEA GGA messages are
EventLogger.tgz to Event_Logger.tgz in the “Itn” directory; WGS84 ellipsoid heights; MSL altitude should be
expr in the "Tracer" directory can be removed. Check above obtained by adding the relative geoid height;
all variables TIMEZONE, LANGUAGE and GeoidHeight. If Event_Logger approximates this with the constant
using POIs, rename Tracker.ov2/.bmp to GeoidHeight).
POI_Tracker.ov2/.bmp. See the Installation paragraph for • Additional tuning for TomTom GO version 5.420. Added
further information. NOTE: Do not exceed the maximum variable DoAnotherGpsRead, to be used in order to
number of 10 “.cap” files in the “SdkRegistry” directory. improve GPS retrieval (but reducing performance); it
might be appropriate when using TomTom GO version
5.420.
2.10. What's new in 6.1
• Unit conversion functions (km/h to miles/h and meters
to feet)
Page 9 of 86Event_Logger for TomTom GO
• Updated documentation • Computation of the duration of aggregated periods,
including total journey time, total run time, time of small
stops.
2.13. What's new in 5.8beta • Archiving of past itinerary files into a single TGZ file (tar
archive compressed with gzip).
(Dec 31, 2005) • This release also includes a bug correction in the GPX
• Additional tuning for TomTom GO version 5.420 speed format (m/sec instead of km/h).
• fixed other minor bugs
2.18. Previous versions
2.14. What's new in 5.7beta
• Release 5.1beta (Sep 19, 2005), including GPX
(Dec 29, 2005) Tracking system with the following issues:
• Added German translation (LANGUAGE variable now • geodecoding of waypoints generated by switch-off
supports IT, FR, EN, DE) events do not work; related GPX information missing.
• Added menu entry to toggle the logging level • code not tuned ("sed" usage should be substituted by
• improved configuration and tracing internal loops); very slow suspend time; usage of the
• the NMEA interpreter has been rewritten to avoid usage enbedded version of busybox "ash" + external "expr"
of the 'sed' command with so many process forks and pipes might reduce the
• Improved flashing messages readability used filesystem size to the minimum but I do not think
• support of an additional optional newline in GPX files to not the best choose...
improve readability (see CR1 and CR2 variables) • release 5.0beta, exploiting SDK
• fixed a bug related to the startup and shutdown of the • release 4.0beta (Sep 3, 2005), aggregating events
GPX tracker through the menu button occurred within short intervals
• fixed other minor bugs • release 3.0beta (Aug 5, 2005), (Single ttn file.
GpsLogger can be deleted.)
• release 2beta (July 19, 2005, slight improvement)
2.15. What's new in 5.6beta • release 1beta (July 14, 2005): POIs replaced by
Itinerary files. Two separated files: GpsLogger (to be
(Dec 12, 2005) placed in the directory "Tracer" of the SD card) and
• Fixed an error that prevented managing negative TTN (to be placed in the root filesystem of the SD card).
coords in itinerary files Many bugs and limitations.
• AllowDateTranslation substituted with LANGUAGE; • release 0beta and initial development called Event POI
support of IT, FR, EN Category Manager (June 2005), creating dummy POIs
• Improved procedure to show date changes upon events.
• The GPX tracker can now be started and stopped
through new menu button It is my intention to provide my valued users with
• included optional GPX counter the best documentation possible to ensure
• support of optional newline in GPX files to improve successful use of Event_Logger. To this end, I will
readability continue to improve my manual to better suit all
users’ needs; it will be refined and enhanced as
2.16. Features available in release 5.4beta new requests and updates are introduced.
(Nov 28, 2005)
• Fixed bug which prevented date sync.
• Fixed bug which prevented GPX logging of negative
coords. 3. Function list
• First porting to TomTom GO version 5.420
The following features are available in Event_Logger
release 8.1.
2.17. Features available in release 5.2beta
o Application fully integrated with NavCore and with
(Oct 8, 2005) the TomTom device.
• GPX Tracking system (GPX files automatically archived o Support of the following GPS units: SiRFstar
with gzip compression) IIe/LP, SiRF Star III with and without QuickGPSfix
• Automatic track segmentation inside GPX files based (SiRF binary and NMEA protocols), Global
on stop periods. Locate's Hammerhead.
• Geodecoding o Management of the following hardware events:
• POI creation
boot, resume (switch-on), suspend (switch-off).
• Integration with TomTom GO via file SDK (display
o Management of software events manually
message; more accurate positioning in case of poor
radio coverage) produced by pressing appropriate menu button
• Management of short intervals, with the introduction of keys.
the aggregate items. o Aggregation of events occurred within short
intervals (period is configurable).
Page 10 of 86Event_Logger for TomTom GO
o Creation of Itinerary files including all events direction arrows, traffic layer, local search,
occurred within one or more consecutive journeys; additional map layers, draggable waypoint
information is shown by TomTom GO so that start markers, tooltip, altitude retrieval for any selected
of journey, end of journey and waypoints can be point, etc.
clearly distinguished. o When selecting "Log Position to Itinerary" and then
o Computation of the duration of each travel and keeping the touchscreen pressed for some
stop period. seconds, a mask appears, showing advanced
o Flashing message within TomTom GO, showing statistics related to the current trip, also including
collected information slope computation.
o GPX Tracking system, creating standard GPX files o Event_Logger allows both personal and
(GPX or XML file extensions) supporting full promiscuous usage. GPX and ITN generation can
tracking as well as waypoints for all occurred be disabled. Besides, ITN and GPX archives can
events; tracks are automatically segmented by include password protected data.
managing short stop periods, including o An astronomical calendar is included, based on
geodecoded data for each stop. Event_Logger the current time and coordinates, providing
also calculates the travelled distance, the average standard calendar data, Ephemerides of sun and
speed of a trip, the max and min altitude as well as moon, rise and set time, twilight time, moon
the motion duration and slope. phase, etc.
o All events occurred in one day are grouped in the o The Event_Logger Agent includes a silent feature
same Itinerary file; when a file is going to exceed which automatically switches between night
the max. number of allowed lines, data are colours and day colours of TomTom GO basing on
automatically segmented into more files including the elevation of the sun at the current position and
sequencing reference. time.
o A GPX file by default includes only information o Two additional menu buttons easily allow toggling
related to a single journey (configurable) in order the tracing level and stopping/restarting the
to improve management. Event_Logger Agent; besides, a service button
o GPX files are produced by either querying implements the UNIX “top” utility which easily
TomTom GO (producing snap-to-road traces) or allows to verify CPU and memory consumption as
directly the GPS device (this is useful when well as disk usage of the TomTom GO processes.
performing off-road travels). Related control is
facilitated through appropriate menu icons. The
direct access to the GPS device can extensively
decode both the NMEA protocol and the SiRF 4. Menu Buttons and Icons
binary one. Event_Logger adds the following menu buttons and
o GPS data are automatically retrieved from the icons to TomTom GO:
TomTom cache in case the GPS device does not
produce valid information. “Log Position to Itinerary”: this is the main
o Past Itinerary and GPX files are automatically function for end-users; each time this icon
archived into single ZIP files to save space on the is pressed, a flashing message appears
SD card (or HD); anyway, the most recent files are showing speed, altitude and current
not archived so that they can be easily managed position; besides, the GPX file related to
(and, in case of ITN files, they can be opened the current journey collects the event in
within TomTom GO). waypoint fashion and a line is also
o Each position is possibly geodecoded. The current recorded in the Event_Logger itinerary file
speed and altitude is also collected in case the “_Latest_Events.itn”; both records will
GPX device provides the data. Values can be include the shown data as well as position
shown in km/h, miles/h, m, feet. Slope is also and time. When _Latest_Events.itn is
computed, together with pretty reliable maximum opened through TomTom GO, it will report
and minimum values. Altitude is automatically the updated list of events occurred during
calibrated when needed. the current day. Also past events of
o Optionally, POIs (Points of Interest) are created previous days are stored and
upon each event. automatically archived inside the “itn”
o When opening the GPX files created by directory.
Event_Logger with Internet Explorer (e.g., drag
and drop a GPX file to IE), a GPX browser is If the touchscreen is being kept pressed
started, graphically representing the recorded path for more than five additional seconds, a
through Google Maps, together with many splash screen appears, showing advanced
additional tables analyzing the path in detail. The statistics related to the current trip. See
GPX browser also allows interactive analysis the examples in the following chapter for
through the usage of mouse, keyboard and with further information.
the support of a comprehensive option menu.
Functionalities include centre/zoom, fixes,
Page 11 of 86Event_Logger for TomTom GO
“Log Position and add POI”: this function perceivable by the user) and the accuracy
is similar to the previous one, but also of the retrieved information is much more
adds a Point of Interest in TomTom GO dependent on the quality of the GPS
each time the icon is pressed. Search and reception.
open the POI category _Tracker with
TomTom GO in order to browse all the “Toggle Event_Logger Agent”: this button
POIs generated by Event_Logger. is not strictly necessary and is suggested
not to be installed in normal operation; it
“Astronomical Calendar”: this icon allows to switch off and on the
produces an ordinary report of Event_Logger background agent, which is
georeferenced astronomical data related automatically activated by default after
to sun and moon, including current TomTom GO boots and has the goal to
calendar, ephemerides, rise and set time, ordinarily retrieve on-line tracking
civil, nautical and astronomical twilight, information to GPX files as well as
moon phase, etc. (The process first automatically switch day and night colours
retrieves the current coordinates and then depending on the sun. When this agent is
repeatedly calls the external program shut down, available memory and idle
“acal” which calculates all the related data CPU period are slightly increased, but the
using the current time.) automatic switching between day and
night colours is not performed and no track
“Toggle snap-to-road or raw GPS”: this information is recorded (e.g., the GPX files
icon allows controlling the method and will still be created by Event_Logger upon
sampling period used by the GPX Tracker events, but only including waypoints and
to retrieve GPS information when with no additional track, so resulting very
producing GPX files; this button is an small in size and with very limited
alternative way to manually modifying the information); by default, this agent takes
Event_Logger.txt configuration variables irrelevant resources, which can negligibly
TTGOtoGPX, GpsToGPX, increase for a short fraction of time,
DelayToBreakTracks and especially while calculating the position of
TrackingGranularity. the sun (this feature can be disabled if not
needed); if raw GPS retrieval is activated,
It provides four switching options: the background agent takes some
- snap-to-road tracking with 5 seconds additional resources to TomTom GO
sampling granularity (which is the (using default parameters the interference
standard and default option, useful for is still unperceivable).
normal driving);
- raw GPS coordinates with 5 seconds “Toggle GPX Tracker”: without interfering
sampling granularity and long breaks with the capability that automatically
(for off road trekking and racing); switches day and night colours depending
- snap-to-road coordinates with 10 on the sun, this icon allows to disable and
seconds sampling granularity useful enable the function collecting on-line
for long driving or slow road biking tracking information to GPX files. When
(e.g., standard settings with half the GPX Tracker is disabled, the GPX files
granularity rate, producing reduced will only be created by Event_Logger upon
logging); events, simply including waypoints and
- raw GPS coordinates with 10 seconds with no additional track, so resulting very
sampling granularity for long off road small in size, but with very limited
driving or slow off road biking and information. When enabling the GPX
sailing (half granularity rate and short Tracker, the Event_Logger agent is
breaks). automatically started if not running.
Conversely, when disabling the tracker
The GPX Tracker will automatically load and in case the day/night display switcher
the new settings after some seconds from is found disabled, the Event_Logger agent
the last change (this allows quickly is automatically shut down.
toggling among various settings until
selecting the most appropriate one); “Toggle Debug Level”: this button is only
alternatively, the GPX Tracker can be for tracing errors and should not be
switched off and then on again in order to installed/used in normal operation: users
activate the new settings. Notice that can simply ignore it (or possibly not install
when “off-road” is selected, the GPX SdkRegistry\togglelog.cap). The button
Tracker takes significant resources to allows activating/deactivating internal
TomTom GO (even if not clearly logging and tracing at any available level
Page 12 of 86You can also read
