TTTracklog
From OpenTom
| TTTracklog | |
|---|---|
| This application runs in background and saves a stream of NMEA GPS messages as well as a track log file in .gpx and .itn files. | |
| Properties | |
| Developer: | Markus Hoffmann |
| Version: | 1.04 (20.06.2008) |
| Architecture: | arm-linux |
| Language: | {{{language}}} |
| Comment: | |
| Dependencies | |
| Requires: | {{{requires}}} |
| See also: Software | |
TTTracklog is a tracklogger which is independant and uses minimal resources. The tracks are outputed as NMEA log, gpx files and .itn route files.
To make the program simple and not consuming noticable processing time on the TomTom it is designed to run completely in the background and will not be switched on or off. It simply logs all tracks and nmea-sentences in the three files:
/mnt/sdcard/statdata/xxxx-xx-xx.gpx /mnt/sdcard/statdata/nmea-xxxx-xx-xx.log /mnt/sdcard/itn/xxxx-xx-xx.itn
where 20xx-xx-xx is the actual date. The new log files automatically will be created every day. This prevents the files beeing split if used during midnight. The .log files can be easily merged togeter with cat.
The .gpx files can be uploaded to the http://www.openstreetmap.org/ project.
The .itn files can be directly used on the TomTom to find positions of the last stop etc. (Use the route managment function)
The Files can become as large as 10 MBytes each, containing up to approx. 130000 lines of log output which is about 43000 Trackpoints (if the tomtom is on 24h, recorded every two seconds). It is important to (re)move them before the SDCARD or internal FLASH memory is full.
Contents |
Download
- The binary package: http://www-cip.physik.uni-bonn.de/~hoffmann/TTconsole/TTTracklog-1.05-bin.zip (--Updated: 22:22, 31 Dec 2008 (CET))
- The source package: http://www-cip.physik.uni-bonn.de/~hoffmann/TTconsole/TTTracklog-1.04.tar.gz
Installation
Unpack the binary package (zip file) and move the contents to your tomtom Directory just as they are. Make sure, that the binary TTTracklog goes to the ./bin/ folder.
d 80 bin/ d 40 itn/ - 2638 README - 364 RELEASE_NOTES d 80 SDKRegistry/ d 40 statdata/ d 40 text/
Make sure, that these directories exist. They might be already there, which is fine. In that case make sure that the contents of bin/ and SDKRegistry/ get to the TomTom.
USAGE
Start
You need to start the tracklogging by activation the TTTracklog Icon in your TomTom menu. You should get a message, that TTTracklog has been started. From now on up to a reboot or a reset of the Device (which is also performed in case you connect the TomTom to your computer), the GPS track is logged and written to the files described above. If you are not sure, if TTTracklog is already running and you want to activate it, it is save to start it again from the icon menu.
Stop:
At the moment, there is no direct way forseen to stop tracklogging. If you have installed TTconsole, you can stop it by typing
killall TTTracklog
You can create a script to do this, if you want. But the simplest way is simply to reboot the device.
Automatic start
I do not know how to automatically start the program at boot time. Any help?
Start from TTconsole
The manual start of the program can be performed as follows:
- Install TTconsole
- Execute TTconsole and type in:
TTTracklog &
(The & is important)
Afterwards you can quit TTconsole. If you want to stop Tracklogging, it is easiest to simply reboot the Tomtom. If you want to check if TTTracklock is running, excecute TTconsole and type
ps x
If TTTracklog appears somwhere is the list you get, you can savely assume that it is still running.
Maintainance:
From Time to time you should remove the files
text/TTTracklog-20*.txt statdata/nmea-20*.log and statdata/20*.gpx
from the device to prevent it from consuming all the memory. But the memory will at least last for 10 Days of 24 hours permanent tracklogging. The itn files do not take much memory, so you can collect thousands of them without problems.
The itn files store the positions of all rests which last more than 30 seconds. Every 30 Minutes a point is stored as well. So you can reconstruct where you have been by selecting the route managment icon, then options, then load a route. The route of the actual day will be updated roughly every 10 Minutes. So you can easily navigate back to where you have been before.
COMMENTS
In addition there is a logfile created:
text/TTTracklog-2008-12-10.txt
This file can be viewed with the document viewer and contains information on the data processing of TTTracklog. This is normally not interesting to users. Only in case of strange behaviour (which is extremly seldom) and for debugging, this file becomes useful. So if you encounter problems with the application, you might send me this output.
Compile
Unpack the tar.gz file and read the README and follow the instructions. You will need the ARM-Linux crosscompiler development environment.
Release Notes
Release notes for Version 1.00 (Jun 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - first version. Release notes for Version 1.01 (Dec 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - now itn files are created from the log files. (they can be used for route planning). The Files do appear in the /mnt/sdcard/itn folder. Make sure that it exists. Release notes for Version 1.02 (Dec 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * We now have an icon to start TTTracklog. * minor changes Release notes for Version 1.03 (Dec 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * new: whereami Release notes for Version 1.04 (Dec 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * now course and speed included in .gpx file. Release notes for Version 1.05 (Dec 2008) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * now more digits of position is stored in .gpx file. The full acuracy is now saved. This was a bug. Release notes for Version 1.06 (Jan 2009) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * now the pdop,hdop and/or vdop values (precision of position) are also saved to the gpx files, as well as the number of sattelites used for position determination.
Usage
The nmea.log file
# NMEA log created with TTTlogger V.1.00 (c) Markus Hoffmann 2008 # date= timestamp=1227733602 $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,135954.50,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*52 $GPRMC,135954.50,V,,,,,,,231108,,,N*7E $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,135956.59,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*59 $GPRMC,135956.59,V,,,,,,,231108,,,N*75 $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,135958.57,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*59 $GPRMC,135958.57,V,,,,,,,231108,,,N*75 $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,140000.51,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*59 $GPRMC,140000.51,V,,,,,,,231108,,,N*75 $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,140002.58,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*52 $GPRMC,140002.58,V,,,,,,,231108,,,N*7E $GPGSA,A,1,,,,,,,,,,,,,6.7,3.0,6.0*34 $GPGGA,140004.61,,,,,0,00,3.0,,M,-1.127103,M,-8.8490599,0130*5E ...
The .gpx file
Beginning with Version 1.04, also the speed and course information is saved in the .gpx file. Speed is in knots (nautical miles per hour), course in degrees, elevation in meters.
<?xml version='1.0' encoding='ISO-8859-1' standalone='yes'?> <gpx version='1.1' creator='TTTracklog V.1.04' xmlns='http://www.topografix.com/GPX/1/1' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd'> <metadata> <link href="http://www.opentom.org/TTTracklog"> <text>TTTracklog (c) 2008-2009 by Markus Hoffmann</text> </link> <time>2008-08-08T07:02:28Z</time> <bounds maxlat="53.574" maxlon="9.92047" minlat="53.5524" minlon="9.8797"/> </metadata> <trk><name>TomTom ACTIVE LOG (1161/1818)</name> <trkseg> </trkseg><trkseg> <trkpt lat='57.5566' lon='9.97842'><ele>70</ele><time>2008-08-08T07:02:51Z</time><course>356</course><speed>2.5</speed></trkpt> <trkpt lat='57.5566' lon='9.97841'><ele>71</ele><time>2008-08-08T07:02:51Z</time><course>356</course><speed>4.9</speed></trkpt> <trkpt lat='57.5567' lon='9.97841'><ele>72</ele><time>2008-08-08T07:02:52Z</time><course>358</course><speed>7.7</speed></trkpt> <trkpt lat='57.5567' lon='9.97841'><ele>73</ele><time>2008-08-08T07:02:53Z</time><course>2</course><speed>8.1</speed></trkpt> <trkpt lat='57.5567' lon='9.97841'><ele>73</ele><time>2008-08-08T07:02:53Z</time><course>4</course><speed>11.3</speed></trkpt> <trkpt lat='57.5568' lon='9.97841'><ele>74</ele><time>2008-08-08T07:02:54Z</time><course>2</course><speed>11.1</speed></trkpt> <trkpt lat='57.5568' lon='9.97841'><ele>75</ele><time>2008-08-08T07:02:54Z</time><course>2</course><speed>11.1</speed></trkpt> <trkpt lat='57.5568' lon='9.9784'><ele>75</ele><time>2008-08-08T07:02:55Z</time><course>2</course><speed>14.5</speed></trkpt> <trkpt lat='57.5569' lon='9.9784'><ele>76</ele><time>2008-08-08T07:02:56Z</time><course>2</course><speed>14.9</speed></trkpt> <trkpt lat='57.5569' lon='9.97841'><ele>76</ele><time>2008-08-08T07:02:56Z</time><course>4</course><speed>15.5</speed></trkpt> </trkseg><trkseg> <trkpt lat='57.5542' lon='9.97792'><ele>78</ele><time>0208-10-31T08:25:09Z</time></trkpt> <trkpt lat='57.5542' lon='9.97791'><ele>78</ele><time>0208-10-31T08:25:10Z</time></trkpt> <trkpt lat='57.5542' lon='9.9779'><ele>78</ele><time>0208-10-31T08:25:11Z</time></trkpt> ...
The .itn file
The unit of speed (v) is km/h and of altitude (alt) is meters.
991830|5755430|12:23:10 Start (#1)|0 987952|5756882|08:32 1.1 min Pause (#627)|0 988054|5757365|08:35 4.2 h Pause (#871)|0 988052|5757331|12:52 0.5 min Pause (#1012)|0 987991|5756904|12:54 1.1 min Pause (#1146)|0 993943|5753134|12:58 2.9 min Pause (#1474)|0 947637|5728324|13:31 v=54.5 alt=79 (#3634)|0 942620|5725380|13:36 1.1 min Pause (#3998)|0 932316|5722139|13:50 0.8 min Pause (#4873)|0 932211|5722052|13:51 0.5 min Pause (#5004)|0 925493|5717283|13:58 0.7 min Pause (#5444)|0 886603|5703225|14:29 v=51 alt=59 (#7545)|0 820317|5679189|14:59 v=59.3 alt=79 (#9565)|0 803989|5636235|15:29 v=41.9 alt=141 (#11630)|0 755579|5598534|15:59 v=32.9 alt=123 (#13643)|0 767990|5567376|16:19 2.7 min Pause (#15019)|0 760707|5547803|16:41 0.5 min Pause (#16488)|0 759953|5547091|16:46 0.5 min Pause (#16864)|0 745312|5539863|17:17 v=4.3 alt=160 (#19002)|0 721724|5529706|17:37 2.6 min Pause (#20341)|0 698174|5519991|18:09 v=60.3 alt=202 (#22594)|0 695514|5510611|18:26:12 End (#23699)|2
The track summary statistics
Trackpoints: 4447/9519 Zeitraum: 2008-09-23 09:38:08 bis 2008-09-23 23:53:02 Ortsraum: lon=[9.87979:10.0536]; lat=[53.544:53.5741] Hoehen: [29:111] m Wegstrecke: 32.678 km Wegzeit: 01:01:39.2 Standzeit: 13:11:53.9 Maxspeed: 55.7452 km/h
addons
whereami
We now provide another tool, which you will find in the bin/ foler: whereami is a tool which allows to get information about a specified location from the TomTom Device.
e.g.
whereami --lon 53.1234 --lat 9.1234
will output the Streetname and City name of the Location closest to the specified point. If you do not provide the coordinates, per default the actual position will be used if it could be acheived.
TTTracklog can run without this tool. (it does not use it).
This tool is useful if you want to convert the position recorded into the .itn file (or any other waypoint like dataset) into adresses. But you will have to write your own script to do so.
log2itn
log2itn is another commandline tool, which allows to convert the nmea-logfile to .itn and/or .gpx files (e.g. this is useful in case TTTracklog was interrupted by a reboot of the device and could not write out these files.)
TTTracklog can run without this tool. (it does not use it).
known bugs
- The automatic startup (before ttn is started) does not work.
comments
- The tracklogger uses a 16 kBytes buffer, so only every 15 minutes and/or if the buffer is full, a write operation to the SDCARD is necessary. We might discuss what buffersize is best.
- It might be necessary to create the statdata and itn folders before TTTracklog can be used.
- Maybe log file size can be reduced if ony new coordinates are logged on one of three conditions are met: max. distance traveled in metres, max. time passed in seconds, max. heading change in degrees. This gives a similar output to that of Tripmaster. Answer: This is a good idea and might be applied to the gpx output (as an option) in future. But the nmea-logs will not be filtered. It is a specialty feature of TTTracklog, that the whole GPS data is stored, so really nothing is lost. The nmea-logs also contain GPS sattellite information as well as the PGLOR message, which is undocumented and probably is some device internal events. It is up to you (or better: to a postprocessing application like log2itn) these logfiles to extract the information you need.
