Version française - Manual in espanol - Norsk veiledning
Tripmaster v3.1 works on Tomtom v8.x or v9.x navcore, but it has no more the sound speed alarm functionality as these navcore versions do not provide a sound functionality to third party applications.
If you are using Tomtom v8.x or v9.x navcore, you must install Tripmaster v3.1 and another program to solve v8.x or v9.x problem with plugins .
If you are using another Tomtom navcore version than v8.x or v9.x and if you've already installed Tripmaster v2.4a, you can keep it, because Tripmaster v2.5 doesn't bring any new functionality. If you're installing Tripmaster for the first time, go ahead and install v3.1 which evidently includes all Tripmaster's features, except sound alarms.
Known problems : this version doesn't work on One V3 where it can't even be launched.
Tripmaster can not be installed with Tomtom Home because it is not known as a Tomtom software.
Proceed as follows to install it :
With Tripmaster, you can:
Tripmaster can also run in background, while Tomtom navigation application is used, and may be recalled on foreground when you want.
 |
 |
| Day screen, with a speed limit set | Night screen, with a speed limit set |
 |
|
| Day screen, without GPS signal and with a customized background | Night screen, with GPS signal and a customized background |
 |
 |
| Day screen, with a speed alert | Screen when the GPS signal is lost |
 |
 |
| Speed limit setup and maximum setup menu | Tracks parameters setup screen |
 |
 |
| Other parameters setup screen | Display parameters setup screen |
 |
 |
| Speed limits setup screen | Colors setup screen |
 |
|
| Customized backgrounds setup screen |
 |
GPS coordinates and altitude are those of the point where you are. Altitude is followed by a slope indicator which gives you the evolution of altitude on X last seconds, X being defined in Tripmaster setup.
The compass indicates the followed direction, by the triangle in top. North is indicated in a square.In the compass center, the steered course is provided in degrees or in literal form or both, according to what you chose. In the lower left corner of the compass zone, either the degrees are displayed or the literal form according to what is displayed in the compass center. In the upper right corner of the compass, the number of visible satellites is displayed, between 0 and 12.
The name of the tracking log file is displayed under the title when the logs are activated.
Maximum speed is displayed, if required. In a rectangle, the speed limit appears. The instantaneous speed is displayed in the center of the screen. On the upper right corner of the speed zone, is indicated the total average speed. In the lower right corner of the speed zone, the average speed while moving is displayed.
In the lower right zone of the screen , are displayed the total distance and the intermediate trip.
In the lower left zone, the total duration of the trip and the duration while moving are displayed.
When the Tripmaster screen is displayed, the whole of the functions is accessible while typing in the significant zones indicated below. For the GO equipped with a remote control, forget it, it is not managed by Tripmaster…
IMPORTANT: Tripmaster can cause you problems if you seized a protection code on your Tomtom. In this case, if you stop your Tomtom whereas Tripmaster is visible, the restart of your Tomtom is likely to be problematic and to end in a manual reset.
 |
To activate the tracking logs, just click on the zone where are displayed the GPS coordinates and altitude (upper left corner, symbol 0_0). When the recording is active, this is announced by the appearance of the tracking logs file name and by a Save button. in the compass zone. When Tripmaster did not acquire a GPS signal yet, the button with the symbol 0_0 does not appear, which means that the activation of tracks logging is not possible. If you're using a customized background, the symbol 0_0 is no more used and the Deactivate/Activate button is always visible, although the function may not be active, if no GPS signal is present.
To stop tracks logging, just click once again on the GPS coordinates zone.
At each click on the title zone, display switches from day to night, then night to automatic, then automatic to day. When Tripmaster is stopped, the current state of color display is saved and will be the state used at next start.
When the tracking logs are activated, a simple click on the compass records an additional tracking point in the tracking logs file, with GPS coordinates of the point where you are, the name of the place, the altitude and the hour of recording. A tracking point is also recorded when you reset the intermediate trip.
Clicking on the lower right corner of the screen will give you access to a first setup screen, where you'll be able to set up all the parameters linked with tracking logs. From this 1st screen, you may invoke a second one to set some other important parameters.
If you click anywhere in the durations zone (lower left corner), Tripmaster goes in background and you have again access to the Tomtom application. Tripmaster continues to run, in background, and records tracking logs, if you asked to do it.
To recall Tripmaster on the foreground, just click on its icon in Tomtom menu.
When clicking on the distance zone of the distances (lower right corner), you reset the intermediate trip. If the tracking logs are active, a tracking point with the current mileage of the intermediate trip is recorded.
You will stop Tripmaster by clicking on the cross in the upper right corner of the screen. When Tripmaster is stopped, all current parameters are stored, the tracking logs state and file name are also stored. All these parameters and states will be re-used at next start.
When clicking on the speed zone, the following menu will appear :
This menu will allow you to manage the speed limit and the maximum speed. It disappears automatically after a few seconds, if you don' use it or if you click outside of it.
The speed limit defines a speed value above which a "Speed Limit " road signal will appear on Tripmaster main screen with the current speed on it and/or an audible alarm will be played. The currently defined speed limit is shown in a small rectangle with a value."> 90", if limit is 90, in the lower middle part of speed zone.
When the above menu is displayed, you can perform the following actions :
When Tripmaster starts, the speed limit is set to the value defined in the speedlimit parameter. The value used when Tripmaster was stopped previously is lost.
These functions are invoked when you click on the speed zone, to display the above menu.
If you click on the Max button , you may display or hide the maximum speed. This value is displayed in the upper left corner of the speed zone.
If you click on the button under the Max button , the maximum speed is resetted.
When you stop Tripmaster, the maximum speed is recorded with its display state. At next Tripmaster start, Tripmaster will reuse this recorded value and will display it or not, depending of the recorded state at previous stop.
With the 2.1 version, you can set up some of the configuration parameters directly on the Tomtom. For the other parameters, you need to connect it to your computer and edit, with Wordpad, the file config.txt located in the /tripmaster directory. Take care to save the file, after changes, in text format.
[ Log files parameters : managed in the 1st setup screen ] trackformat kml tracksaving new trackcourse 30 trackdistance 2 0.5 trackperiod 60 autologging no records medium [ Setup parameters : managed in the 2nd setup screen ] inclinometer 1 processperiod 250 gmtoffset 1 geoidfix no 49 displayaltitude yes 30 [ Other parameters : managed in the 3rd setup screen ] colorscheme auto compass both coordinates decimal language english.lng units metric [ Speed limit parameters : managed in the 4th setup screen ] speedlimit 135 speedalarm both speedinterval 0 55 95 115 135 alarmfilename /mnt/sdcard/tripmaster/speed_alarm.ogg alarmperiod no 10 [ Colors parameters : managed in the 5th setup screen ] topforegroundcolors 0,0,0 255,192,64 204,204,204 bottomforegroundcolors 255,255,255 255,192,64 204,204,204 topbackgroundcolors 255,255,255 0,0,0 bottombackgroundcolors 0,0,128 0,0,128 linescolors 204,204,204 255,192,64 labelcolors 255,0,0 255,255,0 [ Backgrounds parameters : managed in the 6th setup screen ] daybackground /mnt/sdcard/tripmaster/images/bgnd_wide_day.bmp nightbackground /mnt/sdcard/tripmaster/images/bgnd_wide_night.bmp [ Parameters for Tripmaster internal use : don't modify ! ] maxspeeddisplay yes maxspeedvalue 146 logfilename none accelerometer 0 [ Parameters kept for memory and further usage ] bootstart no snapping yes [ End of parameters]
These parameters may be set up in the first setup screen.
These are the following parameters
[ Log files parameters : managed in the 1st setup screen ] trackformat kml tracksaving new trackcourse 30 trackdistance 2 0.5 trackperiod 60 autologging no records medium
Format (trackformat) parameter defines the format of tracking logs files :
If File (tracksaving) parameter is :
Course (trackcourse) parameter defines the minimal value of a course change which produces the recording of a tracking point. Value 0 stops the recording of tracking points on course change criterion.
Distance (trackdistance) parameter defines the elapsed minimal distance which produces the recording of a tracking point. Value 0 stops the recording of tracking points on distance criterion.
Period (trackperiod) parameter defines the interval of time which produces the recording of a tracking point. Value 0 stops tthe recording of tracking points on time criterion.
Distance, period and course (trackdistance, trackperiod and trackcourse) parameters can be used at the same time. As soon as a condition is matched for one of them, a tracking point of trace is recorded. If one of them is set to 0, it is then ignored.
Autologging (autologging) parameter tells if you want or not to have a tracking logs file automatically activated at each Tripmaster start. If you select Yes (yes), a file is created at each start, if the File (tracksaving) parameter is equal to New (new) or the same file is re-used if the File (tracksaving) parameter is equal to Append (append).
Records (records) parameter defines the contents of the tracking logs files records when the Format (trackformat) parameter is equal to itn or csv : each record contains obviously GPS coordinates and the hour of recording. According to the value of the Records (records) parameter, it may also contain the following elements :
These parameters may be set up in the second setup screen.
These are the following parameters
[ Setup parameters : managed in the 2nd setup screen ] inclinometer 1 processperiod 250 gmtoffset 1 geoidfix no 49 displayaltitude yes 30
Inclinometer (inclinometer) parameter defines the time in seconds (between 5 and 60) during which Tripmaster will store successive altitudes to determine the slope, rising or downward, of the current trip. The inclinometer is displayed after the altitude, in the form of a rising arrow, downward or horizontal.
Frequency (processperiod) parameter defines the time interval in 1/1000th of seconds between two execution cycles of Tripmaster. The default value is 500, which means that Tripmaster will be executed every 1/2 second. If you set a lower value for this parameter, Tripmaster will be executed more frequently, giving a smoother display and more frequent updates of the displayed values, but this may produce problems with the navigation application, because of a bigger CPU usage by Tripmaster.
GMT Offset (gmtoffset) parameter defines the time shift from GMT hour for the current timezone. The value may be decimal, e.g. 9.5 for a 9 hours and 30 minutes shift The value may be positive or negative, depending of your location relative to Greenwich meridian.
Geoid fix (geoidfix) parameter specifies if the GPS device corrects or not altitude, according to the rotundity of the Earth. Recent Tomtoms (One, Rider and GOx10) do not need this parameter, choose No (no). Older Tomtom (GO Classic, GOx00) need a geoid correction, choose Yes (yes) and seize on the same line the value of geoid correction in meters to apply.
Altitude (displayaltitude) parameter defines if Tripmaster will display the altitude in a flashing message, over Tomtom application screen, when Tripmaster is not on foreground. The figure on the same line defines the time interval between two messages, in seconds. The minimum value is 5 seconds, because the altitude is displayed for 5 seconds and a shorter interval would bring problems.
These parameters may be set up in the third setup screen.
These are the following parameters :
[ Other parameters : managed in the 3rd setup screen ] colorscheme auto compass both coordinates decimal language francais.lng units metric
Colors (colorscheme) parameter defines whether day colors or night colors or automatic colors are used for the main display. This parameter may also be changed in Tripmaster main screen by clicking on the title zone. The current value used when Tripmaster is stopped is stored. This parameters may be set to :
Compass (compass) parameter defines compass display :
Coordinates (coordinates) parameter defines whether the GPS coordinates are displayed in decimal mode Dec. (decimal) or sexagesimal mode D° m' s" (degminsec) or mixed mode D° mm.mmm' (degminute).
Language (language) parameter defines the language of Tripmaster displays and tracking logs language.
Units (units) parameter defines which units system will be used :
These parameters may be set up in the fourth setup screen.
These are the following parameters :
[ Speed limit parameters : managed in the 4th setup screen ] speedlimit 135 speedalarm both speedinterval 0 55 95 115 135 alarmfilename /mnt/sdcard/tripmaster/speed_alarm.ogg alarmperiod no 10
Speed alarm (speedalarm) parameter defines if you'll get a Visual or Audible alarm or Both at the same time when the current speed is over the defined speed limit.
Speed limit ( speedlimit) parameter defines the speed over which a speed signal will appear in the speed zone and/or an audible alarm will be played. This setup may be changed directly from the main screen, by touching the speed zone. At each Tripmaster start, this value will be the default speed limit. A null value deactivate this speed limit function.
The four values in the line below Speed limit define four different pre-defined speed limits, which may be directly chosen in the speed menu, displayed when you touch the speed zone, in the main screen of Tripmaster.
Alarm sounds (alarmfilename) allows you to choose which sound will be played when the speed limit is reached. Only the sound files present in /tripmaster directory are displayed in this list. They must in .OGG format and last only a few seconds.
Repeat (alarmperiod) parameters defines if the audible speed alarm will be replayed, if the speed remains over the speed limit, for the interval defined by the figure on the same line. If you set it to no, the audible alarm will be played only once. There is no minimum value for this parameter, but the interval must be bigger than the length of the chosen sound.
These parameters may be set up in the fifth setup screen.
These are the following parameters :
[ Colors parameters : managed in the 5th setup screen ] topforegroundcolors 0,0,0 255,192,64 204,204,204 bottomforegroundcolors 255,255,255 255,192,64 204,204,204 topbackgroundcolors 255,255,255 0,0,0 bottombackgroundcolors 0,0,128 0,0,128 linescolors 204,204,204 255,192,64 labelcolors 255,0,0 255,255,0
Each of these parameters defines the colors in Tripmaster main screen :
Each parameter has the following syntax :
The displayed values above correspond to the colors displayed in the different screens of this page.
These parameters may be set up in the sixth setup screen.
These are the following parameters :
[ Backgrounds parameters : managed in the 6th setup screen ] daybackground /mnt/sdcard/tripmaster/images/bgnd_wide_day.bmp nightbackground /mnt/sdcard/tripmaster/images/bgnd_wide_night.bmp
The Day (daybackground) and Night (nightbackground) parameters define the path to customized background files, for day and night screens. These files are Bitmap files (with 8 bits or 24 bits color depth), with size equal to 480 * 272 pixels for wide screen Tomtom and 320 * 240 pixels for small screen Tomtom. If one of these 2 parameters is empty, then the corresponding screen is displayed without background.
The displayed values above correspond to the colors displayed in the different screens of this page.
These parameters are used by Tripmaster to store some informations between two sessions. Do not modify them or you may encounter problems.
[ Parameters for Tripmaster internal use : don't modify ! ] maxspeeddisplay yes maxspeedvalue 146 logfilename none accelerometer 0
These parameters are kept for memory and may be a future re-activation of the functionality they are managing
[ Parameters kept for memory and further usage ] bootstart no snapping yes
It means that
The tracking logs file are stored in the /itn repertory.
The name of the files is of the form tm<yyyymmdd>.<suffix> when the File parameter is equal to Append or of the form tm<yyyymmdd_hhmmss>.<suffix> when the File parameter is equal to New. <yyyymmdd> represents the current date when the file is created, and <hhmmss> represents the hour of creation of the file. <suffix> is worth .itn, .csv, .kml or .gpx, according to the value of the trackformat parameter.
Whatever the format of recording chosen, the file contains a Start record and an Finish record, which are recorded respectively when the file is created and when it is closed.
In POI format, in New mode, the POI are stored in a category named as defined above. In Append mode, the POI are stored in a category named Tripmaster.
IMPORTANT: in KML or GPX format, the file is structured in language XML, it is imperatively necessary to close it before stopping Tripmaster. If the file is not closed, the XML structure of the file is incorrect and it will be unusable with Google Earth or any other software reading files GPX or KML. To close a tracking logs file, just click on the symbol 0_0 or on the zone which surrounds it and verify the display of a flashin message“Logs deactivated ”. When the name of the file is hidden, the file is closed correctly.
An ITN tracking logs file can be edited with Wordpad or directly used in the Tomtom navigation by the Itinerary planning function.
Important : a Tomtom route can contain only 48 steps, whereas an ITN tracking logs file may contain an infinite number of records. Only the 48 first will be used in Tomtom application.
Each line of an ITN file contains a tracking point with the following fields, separated by the character “|”:
The values which follow the comment can be:
Example of ITN file in long record format
-15xxxx|481xxxx|Start : Noyal-Sur-Vilaine - 23/11/2006 - 08:50: 26 - 37.2 m - 0.4 Km|0| -15xxxx|481xxxx|08: 50: 45 - Noyal-Sur-Vilaine - 42.4 m - 0.6 km - 29 Km/h|0| -15xxxx|481xxxx|08: 51: 25 - Km 1.4: Acigné - 26.5 m - 1.4 km - 69 Km/h|0| -15xxxx|481xxxx|08: 52: 16 - Cape 255: Acigné - 42.6 m - 2.0 km - 57 Km/h|0| -15xxxx|481xxxx|08: 52: 25 - Cape 155: Acigné - 39.4 m - 2.1 km - 54 Km/h|0| -15xxxx|481xxxx|08: 53: 25 - Km 3.0 - Acigné - 34.9 m - 3.0 km - 67 Km/h|0| -16xxxx|481xxxx|Finish : Cesson-Sévigné - 09:03: 23 - 51.9 m - 8.6 Km|0|
Example of ITN file in medium record format
-15xxxx|481xxxx|Start : Noyal-Sur-Vilaine - 23/11/2006 - 08:50: 26 - 37.2 m - 0.4 Km|0| -15xxxx|481xxxx|09: 00: 32 - Km 6.7: Patis Of the Winch (Thorigné-Fouillard) - 66.2 m - 6.7 Km|0| -15xxxx|481xxxx|09: 01: 31 - Cape 125: Cesson-Sévigné - 62.0 m - 7.1 Km|0| -15xxxx|481xxxx|09: 01: 32 - Cape 15: Cesson-Sévigné - 61.6 m - 7.1 Km|0| -16xxxx|481xxxx|Finish : Cesson-Sévigné - 09:03: 23 - 51.9 m - 8.6 Km|0|
Example of ITN file in short record format
-15xxxx|481xxxx|Start : Noyal-Sur-Vilaine - 23/11/2006 - 08:50: 26 - 37.2 m - 0.4 Km|0| -16xxxx|481xxxx|09: 02: 21 - 40.2 m|0| -16xxxx|481xxxx|09: 02: 43 - 47.5 m|0| -16xxxx|481xxxx|Finish : Cesson-Sévigné - 09:03: 23 - 51.9 m - 8.6 Km|0|
A CSV tracking logs file can be edited with Wordpad either imported in Excel or Autoroute Express, for example.
Each line of a file CSV contains a tracking point with the following fields, separated by the character “,”:
The field comment contains the same values as ITN format, described above.
Example of CSV file in long record format
"-1.6xxxx","48.xxxx","18:33:40","Départ : 23/11/2006 18:33:40 : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m","8.8 Km","7 Km/h","4" "-1.6xxxx","48.xxxx","18:33:46","Point : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m","8.8 Km","0 Km/h","4" "-1.6xxxx","48.xxxx","18:41:35","Cap 125 : Saint-Grégoire (Ille-Et-Vilaine)","28.2 m","0.0 Km","34 Km/h","4" "-1.6xxxx","48.xxxx","18:41:41","Durée 0:08:01 : Le Bignon (Rennes FR)","29.9 m","0.0 Km","26 Km/h","4" "-1.6xxxx","48.xxxx","18:42:35","Km 0.4 : Le Bignon (Rennes FR)","37.1 m","0.4 Km","16 Km/h","4" "-1.5xxxx","48.xxxx","Arrivée : 23/11/2006 18:54:46 : Noyal-Sur-Vilaine","79.5 m","16.9 Km","16 Km/h","4"
Example of CSV file in medium record format
"-1.6xxxx","48.xxxx","18:33:40","Départ : 23/11/2006 18:33:40 : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m","8.8 Km" "-1.6xxxx","48.xxxx","18:33:46","Point : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m","8.8 Km" "-1.6xxxx","48.xxxx","18:41:35","Cap 125 : Saint-Grégoire (Ille-Et-Vilaine)","28.2 m","0.0 Km" "-1.6xxxx","48.xxxx","18:41:41","Durée 0:08:01 : Le Bignon (Rennes FR)","29.9 m","0.0 Km" "-1.6xxxx","48.xxxx","18:42:35","Km 0.4 : Le Bignon (Rennes FR)","37.1 m","0.4 Km" "-1.5xxxx","48.xxxx","Arrivée : 23/11/2006 18:54:46 : Noyal-Sur-Vilaine","79.5 m","16.9 Km"
Example of CSV file in short record format
"-1.6xxxx","48.xxxx","18:33:40","Départ : 23/11/2006 18:33:40 : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m" "-1.6xxxx","48.xxxx","18:33:46","Point : Saint-Grégoire (Ille-Et-Vilaine)","28.1 m" "-1.6xxxx","48.xxxx","18:41:35","Cap 125 : Saint-Grégoire (Ille-Et-Vilaine)","28.2 m" "-1.6xxxx","48.xxxx","18:41:41","Durée 0:08:01 : Le Bignon (Rennes FR)","29.9 m" "-1.6xxxx","48.xxxx","18:42:35","Km 0.4 : Le Bignon (Rennes FR)","37.1 m" "-1.5xxxx","48.xxxx","18:54:46","Arrivée : 23/11/2006 18:54:46 : Noyal-Sur-Vilaine","79.5 m"
A GPX tracking logs file can be published with Wordpad or imported in Google Earth to directly visualize the points of passage and the recorded way.
Each line of a file GPX contains either a point of the waypoint type, or a point of the routepoint type and a point of the trackpoint type. In fact, for manually recorded points , Tripmaster records a waypoint, a routepoint and a trackpoint. For the automatically recorded points, Tripmaster records a routepoint and a trackpoint.
This allows then on other GPS or in Google Earth to obtain not only tracking passage, but also a route between these points, therefore an order of passage.
The points of the waypoint type have the following fields:
The comment field takes the same values as in format ITN, described above.
The points of the routepoint type and trackpoint have the same fields and the same values. The commentfield takes the same values as format ITN, described above.
The whole of this information is coded in XML syntax in accordance with GPX standards.
IMPORTANT: Only the closing of the file before stopping Tripmaster guarantees that information is gathered correctly to give a valid file GPX.
This particular point also explains why, for the GPX format, only the New mode is enabled for the File parameter in setup screen. In this manner, the file can be used only once and its XML structure is correct if one closes it well before stopping Tripmaster. The short, medium or long record format is also unavailable in the setup screen, because there is only one possible format for these GPX records.
Example of GPX file
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?> <gpx version="1.0" creator="Tripmaster (http://www.webazar.org)" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.topografix.com/GPX/1/0" xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/2" xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.topografix.com/GPX/Private/TopoGrafix/0/2 http://www.topografix.com/GPX/Private/TopoGrafix/0/2/topografix.xsd"> <time>2006-11-09T16:31:23Z</time> <wpt lon="3.0xxxx" lat="45.xxxx"><name>Départ : Ceyrat</name> <desc>11.7 Km</desc><time>2006-11-09T16:31:23Z</time><ele>480.2</ele></wpt> <wpt lon="3.0xxxx" lat="45.xxxx"><name>Arrivée : Orcines</name> <desc>21.8 Km</desc><time>2006-11-09T16:45:14Z</time><ele>816.6</ele></wpt> <rte> <name>2006-11-09T16:31:23Z</name> <rtept lon="3.0xxxx" lat="45.xxxx"><name>Départ : Ceyrat</name> <desc>11.7 Km</desc><time>2006-11-09T16:31:23Z</time><ele>480.2</ele></rtept> <rtept lon="3.0xxxx" lat="45.xxxx"><name>Cap 351 : Ceyrat</name> <desc>11.8 Km</desc><time>2006-11-09T16:31:37Z</time><ele>478.4</ele></rtept> <rtept lon="3.05837" lat="45.xxxx"><name>Point : Ceyrat</name> <desc>11.9 Km</desc><time>2006-11-09T16:31:51Z</time><ele>507</ele></rtept> <rtept lon="3.0xxxx" lat="45.xxxx"><name>Cap 338 : Ceyrat</name> <desc>12.0 Km</desc><time>2006-11-09T16:31:56Z</time><ele>512.9</ele></rtept> </rte> <trk> <name>2006-11-09T16:31:23Z</name> <trkseg> <trkpt lon="3.0xxxx" lat="45.xxxx"><name>Départ : Ceyrat</name> <desc>11.7 Km</desc><time>2006-11-09T16:31:23Z</time><ele>480.2</ele></trkpt> <trkpt lon="3.0xxxx" lat="45.xxxx"><name>Cap 351 : Ceyrat</name> <desc>11.8 Km</desc><time>2006-11-09T16:31:37Z</time><ele>478.4</ele></trkpt> <trkpt lon="3.0xxxx7" lat="45.xxxx"><name>Point : Ceyrat</name> <desc>11.9 Km</desc><time>2006-11-09T16:31:51Z</time><ele>507</ele></trkpt> <trkpt lon="3.0xxxx" lat="45.xxxx"><name>Cap 338 : Ceyrat</name> <desc>12.0 Km</desc><time>2006-11-09T16:31:56Z</time><ele>512.9</ele></trkpt> </trkseg> </trk> </gpx>
A KML tracking logs file can be edited with Wordpad or imported in Google Earth to directly visualize the points of passage and the recorded way.
The recorded points have the following fields :
The field comment takes the same values as in ITN format, described above.
The whole of this information is coded in XML syntax in accordance with GPX standards.
IMPORTANT: Only the closing of the file before stopping Tripmaster guarantees that information is gathered correctly to give a valid file GPX.
Example of KML file
<?xml version="1.0" encoding="UTF-8"?> <kml xmlns="http://earth.google.com/kml/2.0"> <Folder> <name>22/11/2006 21:14:59</name> <Folder> <name>Waypoints</name> <Placemark> <name>Départ : Noyal-Sur-Vilaine - 77.9 m</name> <description> - 22/11/2006 21:14:59 - 0.0 Km - 0 Km/h - 77.9 m</description> <Point> <coordinates>-1.5xxxx,48.xxxx,77.9</coordinates> </Point> </Placemark> <Placemark> <name></name> <description>21:30:33 - 0.0 Km - 3 Km/h - 76.0 m</description> <Point> <coordinates>-1.5xxxx,48.xxxx,76</coordinates> </Point> </Placemark> <Placemark> <name>Arrivée : Noyal-Sur-Vilaine - 77.9 m</name> <description> - 22/11/2006 21:14:59 - 0.0 Km - 0 Km/h - 77.9 m</description> <Point> <coordinates>-1.5xxxx,48.xxxx,77.9</coordinates> </Point> </Placemark> </Folder> <Folder> <name>Routes</name> <Placemark> <name>2006-11-22T20:14:59Z</name> <styleUrl>#lineStyle</styleUrl> <MultiGeometry> <LineString> <coordinates> -1.5xxxx,48.xxxx,77.9 -1.5xxxx,48.xxxx,76 -1.5xxxx,48.xxxx,77.9 </coordinates> </LineString> </MultiGeometry> </Placemark> </Folder> <Folder> <name>Trackpoints</name> <Folder> <name>2006-11-25T09:49:46Z</nam> <Placemark><visibility>0</visibility> <name>2006-11-25 09:49:46Z</name> <TimeInstant><timePosition>2006-11-25T09:49:46Z</timePosition></TimeInstant> <description></description> <Point><coordinates>-1.5xxxx,48.xxxx,77.9</coordinates></Point> </Placemark> <Placemark><visibility>0</visibility> <name>2006-11-25 09:50:06Z</name> <TimeInstant><timePosition>2006-11-25T09:50:06Z</timePosition></TimeInstant> <description></description> <Point><coordinates>-1.5xxxx,48.xxxx,76</coordinates></Point> </Placemark> <Placemark><visibility>0</visibility> <name>2006-11-25 09:50:48Z</name> <TimeInstant><timePosition>2006-11-25T09:50:48Z</timePosition></TimeInstant> <description></description> <Point><coordinates>-1.5xxxx,48.xxxx,77.9</coordinates></Point> </Placemark> </Folder> </Folder> </Folder> </kml>
This general log file is called tripsummary.log and it is stored /tripmaster directory. It may be edited with Wordpad or imported into Excel, because it is in CSV format.
Each time you use Tripmaster,when stopping it, a record is appended to this file with current values, generated during Tripmaster usage.
Each record contains, in the following order :
These fields are separated by commas.
If you have Tomtom standard menu (eg. if you have no tomtom.mnu file on your Tomtom), the Tripmaster icon is added at the end of Tomtom main menu.
If you have a tomtom.mnu file, you need to modify it to see Tripmaster icon in your personalized menu. To do that, add a line :
MENUITEM|TASK_SDK<n>|with <n> equal to the right number (between 1 and 9) for Tripmaster corresponding entry in /sdkregistry. <n> depends on the number and date of the .cap files in the /sdkregistry directory.
You may create as many buttons as you want, in Tomtom menu, for Tripmaster, to recall it, when it's running in background, to record specific waypoints with specific comments.
For example, to add a "Restaurant" waypoint, proceed as follows :
If you add the hide keyword after the comment field in the CMD line , Tripmaster, when recalled, will record the waypoint and will stay running in background.
.cap file example
Version|100| AppName|tripmaster| AppPath|/mnt/sdcard/tripmaster/| AppMainTitle|Restaurant| AppPort|2001| COMMAND|CMD|Restaurant hide|tripmaster.bmp|Restaurant|
If you want to uninstall Tripmaster, proceed as follows directly on your Tomtom :
None of these previous v1.x versions is supported and there's no guarantee they can run on v8 Tomtom system.
This version is the last stable version that works on Tomtom navcore, before v8.x.
This version includes :
This version avoids the systematic recording of a waypoint when a speed audible alarm is played
This version fixes the bug found in v1.7 : Tripmaster crashes when invoking the setup menu on One V1 and GOx00, and no possibility to input a value for the audible speed alarm replay interval.
This version includes :
This version includes :
This version includes :
With this version, you may use a specific background.
This version fixes a bug in KML and GPX tracking logs files
This version includes :