Model info

TripManager was initially created with the Zumo XT in mind. To my knowledge TripManager was the first program to be able to read, write, and create the trip file format. Thereby fixing some of the problems found when importing GPX files by the unit itself.

Since the trip file format is not officially documented reverse engineering the trip files is about the only way to support more models. This takes time and usually a lot of testing.

Over time more trip file formats were supported. Like the formats for the XT2 and the Tread 2.

Nearly every model has its own trip file format and it is important to identify the model when reading and writing trip files.

Identification methods used are:

· Device name as reported by Windows.

· Reading GarminDevice.xml, usually located in the Garmin folder, to get the device name, the part number, and the path locations. The device name and part number can be used if the model could not be identified by the device name as reported by Windows.

· To get additional information needed to properly create the trip files TripManager can read the Settings.db and Vehicle_profile.db in .System\SQlite

Note: Required files are first copied to the Temp directory. Use the Temp path button and look in the Device sub directory to see the files.

In addition to the trip file format TripManager can also read/write POI files (.gpi) that are used to mark Points of interest. And has experimental support for .fit files used on for example Edge models.

For many Garmin models it is supported to transfer GPX files to the unit. The GPX file(s) should be imported on the unit to be able to use it. See 16) Using older Zumo's.

This document aims to provide an overview of the models and what is supported in TripManager.

Models that TripManager does identify as compatible with the trip file format.
Model	Identification	Trip	Poi	Gpx	Fit	Remarks

Zumo XT	Device name GarminDevice.xml	RW	RW	RW	N/A	Fully supported. Unique feature: Grouping Trips Need to enable the .System directory .
Zumo XT2	Device name GarminDevice.xml Settings.db Vehicle_profile.db	RW	RW	RW	N/A	Fully supported. Grouping Trips is replaced by Collections Route preference per segment. Need to enable the .System directory AND make sure it is created by first loading at least 1 trip
Tread 2	Device name GarminDevice.xml Settings.db Vehicle_profile.db	RW	RW	RW	N/A	Fully supported. In addition to the XT2 it supports multiple vehicle profiles
RW=Read/Write, RO=ReadOnly, N/A=Not Applicable

Models that TripManager does not identify as compatible with the trip file format, because writing is not supported. Reading the trip files however is supported. But you will need to select the trip files manually.

TripManager will use these devices as Generic Garmin.

Model

Identification

Trip

Poi

Gpx

Fit

Remarks

Zumo 3x0

(340 + 350)

Device name

GarminDevice.xml

System.db

N/A

Can be identified, but writing trip files is not considered safe.

Hidden menu/MTP Settings:

MTP	Device	Trips	GPX\POI
Auto Detect	Internal storage	No	Yes
Mass Storage	Drive lettter	Yes	Yes

Zumo 590 + 595

Device name

GarminDevice.xml

N/A

Can be identified, but writing trip files is not considered safe.

In the Hidden menu/MTP Settings:

Hidden menu/MTP Settings:

MTP	RWFS	Device	Trips	GPX\POI
Auto Detect	Hide	Internal storage	No	Yes
Mass Storage	Hide	Drive lettter	No	Yes
Mass Storage	Show	Drive lettter	Yes	Yes

So: Trips are only visible in Mass Storage Mode with RWFS enabled. In that mode the trip files are only visible on System1, the GPX\POI are only visible on an other device/ drive letter: System

Drive 51

N/A

Identification needs testing.

Note: The format is very similar to the 595 trip file format. The only difference is that it has no mIsRoundTrip item.

Nuvi 2595

N/A

Can be identified, but writing trip files is not considered safe.

Hidden menu/MTP Settings:

MTP	Device	Trips	GPX\POI
Auto Detect	Internal storage	No	Yes
Mass Storage	Drive lettter	Yes	Yes

RW=Read/Write, RO=ReadOnly, N/A=Not Applicable

Models that TripManager does not identify as compatible with a trip file format, because the trip file format is not used by the unit.
Model	Identification	Trip	Poi	Gpx	Fit	Remarks

Generic Garmin Tested: Zumo 220 Zumo 660 Zumo 340 + 350 Zumo 590 + 595 Dakota 20 Nuvi 2595	Device name GarminDevice.XML	N/A	RW	RW	N/A	Only the GPX and POI files are supported. The operation mode is much like copying the files traditionally via Windows Explorer, or BaseCamp. The TM fixes (RUT, Location changes) are not applicable. Using TM could still be useful for Post processing GPX files, creating GPX files with tracks and waypoint, and POI files.
Edge Tested: Edge 1030	Device name GarminDevice.xml	N/A	N/A	RW	RW	These devices don't use trip files, but fit files. These files can be stored on the Courses, or NewFiles, directory. After a reboot they are ready to navigate. In the NewFiles you can also store GPX files. These will be converted by the unit to Courses. The NewFiles directory is emptied by the unit after conversion. In Activities you can find also find fit files. These are the recorded courses. Comparable to track logs.
RW=Read/Write, RO=ReadOnly, N/A=Not Applicable