Java program to fix the routing behaviour of the XT(2).

[Plainmad]

No as with both the programs saying no modifications needed and file explorer not updating the time changed I just assumed that nothing has been done.

Interestingly enough this time I imported them by plugging the Zumo in to the computer and saving them to the GPX folder. I’ve just sent them all across by the Drive app and when running the trip program it says modification successful so I’ve all done it that way.

Don’t know if that is related to the under lying issue though

[Peobody]

It shouldn't make a difference how the .gpx files arrived on the XT. Once imported, the XT creates a .trip file for each route.

1. Copy the .trip files from the XT to your local HD
2. Process them through the Java tool or the JaVaWa web utility
3. Replace the .trip files on the XT with the modified ones

[FrankB]

Interestingly enough this time I imported them by plugging the Zumo in to the computer and saving them to the GPX folder.

Not sure what you've done. But the .trip files dont belong in the GPX folder. They go in to .System\Trips.

[Scarecrow]

It shouldn't make a difference how the .gpx files arrived on the XT. Once imported, the XT creates a .trip file for each route.

1. Copy the .trip files from the XT to your local HD
2. Process them through the Java tool or the JaVaWa web utility
3. Replace the .trip files on the XT with the modified ones

Done this All good
Now my Question is:-
If I share this route by Bluetooth will it be the Fixed Route that's transferred?

[Peobody]

If I share this route by Bluetooth will it be the Fixed Route that's transferred?

I would say yes. This is based on the fact a .trip file is created when a route is imported and routes not imported are not listed as available to share.

[jfheath]

I don't think so. The fix isn't in the route, it is on the Zumo itself.
Any route coming from outside is regarded as imported.
The trip file that contains the mImported byte is only created when the route is imported into the main storage.

[Peobody]

My "yes" response is assuming that the Bluetooth transfer is originating from a device (Apps > Share Route), and that the route being transferred is a 'fixed' route. I am not certain that the Share Route function exists on the XT2 though.

[Peobody]

My "yes" conjecture is WRONG!!!! I just did a share to my SD card. I then edited the route name in the resulting .gpx file and imported it. The imported route shows up in Trip Planner under Imported Trips and not Saved Trips.

[jfheath]

Nothing getting into the XT2 from outside (except synched from the tread app) is treated as 'Saved'. They are all imported.

The XT2 has a nice little 'copy' function, and it can be used before the XT2 gets to recalculate it. That copy is identical to the original except that it is flagged as not imported - so it behaves perfectly and will not display RUT behaviour. (From tests comparing the copied route with the original imported route in identical circumstances.)

[FrankB]

My "yes" conjecture is WRONG!!!! I just did a share to my SD card. I then edited the route name in the resulting .gpx file and imported it. The imported route shows up in Trip Planner under Imported Trips and not Saved Trips.

That doesn't surprise me. I noticed that when you share a saved route from one XT to another XT (Directly via Bluetooth) the route arrives on the destination XT as imported.
viewtopic.php?t=2333&hilit=fixed