How to store GPS routes in the Suunto GPS Pod

I found out how to, without changing the firmware in the GPS pod, can store GPS-points and later export them to for example Google Earth.









You need 2 things

• the DOS program for configuring and starting the logger.
  http://isuite.fastrax.fi/sdk/341/Logging/logtool.html
  

• And a cable to connect to the unit. TTL-232R-3V3. Buy it here for example: http://www.lawicel-shop.se/shop/

You have to solder cables to the gold plated test point-pads inside the GPS pod, and put 3V power supply instead of the battery. I used clips for the + and - from a 3V power supply. I have not figured out how to put a connector inside without making holes in the plastic.

* Black is ground
* Orange is TX to the Pod
* Yellow is RX from the Pod
* Note that the signal levels has to be 3.3V

* Power on the unit with the power-on button.
* Connect the USB pin connector to the PC.
* Install the drivers from FTDI page (if needed)
* Make note of which COM number is used
* Start the log program with "logtool.exe -PORT 25", where 25 is the number where your USB port is initialized.
* Start logging by "S" and the "3"
* then choose for example "0x173" as logging mask
* use the following as example: 0, 1, 10, 5, 20, 0, 25.

• See this page for more info, download the 3.41 tool (for iSuite protocol):

http://isuite.fastrax.fi/downloads.html

• Use the POD as normal
• After use, turn off with button (if not auto shut-off already was activated)
• Use the logtool again to extract and save logfile.

• Use the log file and import it with www.gpsvisualizer.com

You can use the cut+paste method
Change the column of "H.Vel" to "Speed" and "Dir" to "Heading" to make the conversion recognize these columns.
I'm not finished with how to convert Week/TowSec to date and time. It should be quite easy.

Example of log file:
Lat Lon Alt Week TowSec H.Vel Dir V.Vel NumSVs FixInfo HDOP
59.6229663 17.9122084 0.000 1484 402395.000 25.70 219.36 0.00 6 1 1.1
59.6221188 17.9107953 0.000 1484 402400.000 25.38 219.94 0.00 6 1 1.1
59.6214219 17.9096339 0.000 1484 402404.000 25.52 221.32 0.00 4 1 5.7
59.6208064 17.9082934 0.000 1484 402408.000 25.30 230.73 0.00 6 1 1.1
59.6202879 17.9068213 0.000 1484 402412.000 25.06 239.73 0.00 6 1 1.1
59.6198951 17.9051879 0.000 1484 402416.000 25.58 248.04 0.00 7 1 1.8
59.6196104 17.9034713 0.000 1484 402420.000 25.26 254.10 0.00 6 1 1.1
59.6193868 17.9017109 0.000 1484 402424.000 25.58 256.01 0.00 6 1 1.3
59.6191211 17.8999788 0.000 1484 402428.000 24.98 252.58 0.00 6 1 1.2
59.6186985 17.8983940 0.000 1484 402432.000 25.42 236.09 0.00 7 1 1.3
59.6180869 17.8970510 0.000 1484 402436.000 25.68 221.91 0.00 6 1 1.9
59.6172961 17.8960658 0.000 1484 402440.000 26.38 206.65 0.00 7 1 1.0
59.6163538 17.8954978 0.000 1484 402444.000 27.70 190.56 0.00 7 1 1.0
59.6153458 17.8954339 0.000 1484 402448.000 27.68 175.44 0.00 7 1 1.1
59.6143722 17.8959146 0.000 1484 402452.000 27.52 159.70 0.00 7 1 1.1

Update:
I have now changed to thinner wirewrap cables.
It is now possible to close the unit and use the batteries as power while communicating. I keep the connector while using it, it is maybe a bit less watertight. The pin connector fits directly to the FTDI cable















I have made some test of the logging, and it seems like it will log while doing running on average every 2 seconds. This will make with 4686 "items" a total log time of 2 hours and 36 minutes.
For safety reason the GPS will not fill the entire memory so you can expect a bit less usable time.

CAUTION: I will not be held responsible if you use this info, and brick your GPS unit. (Though it should be quite safe, since there is no firmware upgrades involved).