Page 24 of 26

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 9:47 pm
by FrankB
OK.

First thing to do is navigate to the folder (directory) on your hard-drive where your GPX files are.
folder.jpg
folder.jpg (117.06 KiB) Viewed 1868 times
Open 'This PC', next open the folder where you keep them. A sample folder from myself:
BC.jpg
BC.jpg (49.06 KiB) Viewed 1868 times
Once you select a GPX file you can 'Add To Map' or 'Send To' to transfer the gpx to your XT2

https://frankbijnen.github.io/TripManag ... evice.html

Note 1: The Arrows are 'plain file transfer', no logic is performed. No need to use it to get started.
Note 2: There are some trip files on your device. But looking at the file names they are NOT transfered by TM

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 9:50 pm
by proofresistant
Oop North John wrote: Thu Mar 19, 2026 9:18 pm I shut down the XT2, closed Tripmanager and then reconnected the XT2 to my laptop, and opened up Tripmanager, and the check mark is still there. So either the programme remembers what the status that was last selected, or it does update the XT2.
Maybe, as I said, I’d have to check for myself whether it’s transferred automatically or not.


Oop North John wrote: Thu Mar 19, 2026 9:24 pm What I'm seeing on startup of Tripmanager is below.
But isn't that the contents of your computer on the right?
Can't you just go to to your local folders with your gpx files?
PNG-Bild (neu) (8).png
PNG-Bild (neu) (8).png (307.5 KiB) Viewed 1864 times

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 9:54 pm
by Oop North John
My problem, I think, is that Ive been taking the files from the XT2, not from the PC. Will try the working on them in Tripmanager, and then sending the "saved" route etc to the XT2.

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 9:57 pm
by Peobody
Oop North John wrote: Thu Mar 19, 2026 8:38 pm When I opened up Tripmanager I can see the routes and they had no check mark. So I added one to make it a "saved" route. Does this update the XT2 so that the route becomes a saved one, and avoids the RUT problem,
I am a little late to this party but wanted to chime in to specifically answer this question, which is "yes". The RUT problem is fixed by flipping the mimport bit in a .trp file. Routes without the checkmark are routes (.trp files) in which that bit indicates that the route is in the "Imported" state. When you add the checkmark you are telling TripManager to flip that bit which then changes it to the "Saved" state, which fixes RUT.

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 10:05 pm
by Oop North John
Peobody wrote: Thu Mar 19, 2026 9:57 pm
Oop North John wrote: Thu Mar 19, 2026 8:38 pm When I opened up Tripmanager I can see the routes and they had no check mark. So I added one to make it a "saved" route. Does this update the XT2 so that the route becomes a saved one, and avoids the RUT problem,
I am a little late to this party but wanted to chime in to specifically answer this question, which is "yes". The RUT problem is fixed by flipping the mimport bit in a .trp file. Routes without the checkmark are routes (.trp files) in which that bit indicates that the route is in the "Imported" state. When you add the checkmark you are telling TripManager to flip that bit which then changes it to the "Saved" state, which fixes RUT.
Thanks so that I have it 101%, as I'm feeling a little slow today, you can send data from the PC to the XT2 and then add the check mark to save it to prevent the RUT, or, look at a route already in the XT2 and add the check mark, and the end result is the same?

Re: Introducing TripManager

Posted: Thu Mar 19, 2026 10:13 pm
by proofresistant
Oop North John wrote: Thu Mar 19, 2026 10:05 pm Thanks so that I have it 101%
We're also happy to provide everything you need for 999%


Oop North John wrote: Thu Mar 19, 2026 10:05 pm you can send data from the PC to the XT2 and then add the check mark to save it to prevent the RUT
If you send it via TM, it's automatically set to be checked and RUT is prevented.


Oop North John wrote: Thu Mar 19, 2026 10:05 pm look at a route already in the XT2 and add the check mark, and the end result is the same?
yes

Re: Introducing TripManager

Posted: Sat Mar 28, 2026 9:09 am
by FrankB
Yesterday a new TripManager version was released: V1.7.0.382.

This version has some fixes for the XT3, sending routes to the XT3 should work better with regard to Vehicle profiles. Non XT3 users can skip this version.

Download link: https://github.com/FrankBijnen/TripManager/releases
Technical docs on the Vehicle Profile hash: https://frankbijnen.github.io/TripManag ... shxt3.html

Re: Introducing TripManager

Posted: Fri Apr 10, 2026 3:40 pm
by giuseppe66
Sorry if this question has already been asked. I use MRA and export to gpx1.1, then open TripManager and open the gpx with TRK2RT. Other points are added, and then, still using TripManager, I send the file to the Zumo XT2. When I turn on the GPS, I open the route, but it says that the route was created with a map not present in the GPS (I think it refers to OSM maps) and it recalculates. In the end, it offers to save the route and lets me navigate it. The problem is that turns or small detours are added and then it returns to the original route. Is it a problem with the different maps or is there something I can do to avoid this? Thanks

Re: Introducing TripManager

Posted: Fri Apr 10, 2026 4:04 pm
by FrankB
That is to be expected when using MRA. MRA does not (is unable to) export all the data in the GPX needed. Only GPX files exported with BaseCamp allow for 'non recalculating' trips.

Re: Introducing TripManager

Posted: Fri Apr 10, 2026 4:14 pm
by smfollen
Trk2Rt, optionally, adds route points (shaping points) only from the hidden points (route point extensions in some previously calculated routes) or from track points, if there are any, in the original gpx file. It does not do any routing calculations, so it should never cause any sort of deviation from the original route.

I don't want to speak for @FrankB, but I can't imagine any way that Trip Manager would cause any deviation form the original route either.

I suspect that the deviations occur on the zumo when it recalculates the route.

Differences in route calculation results can occur between any 2 route planners / navigation devices due to differences in maps, routing algorithms, and user setting for route preferences (e.g. fastest vs shortest) and avoidances (e.g. highways, ferries).

The best way to get the zumo results to match the MRA results is probably to add more points to the route where the deviations occur. Trk2Rt can do that automatically if the original gpx contains a track or route with route point extensions. Otherwise you can do it manually, either in the original route in MRA or later in the process with Trip Manager or on the zumo.

There are tradeoffs to adding points to a route. The more points, the less flexible the route becomes.

Trip Manager does have a helpful route compare capability.

The Trip Manager and Trk2Rt manuals have further discussion of all this, if you are brave enough to read all that very exciting prose :)