Tread Collections not synchronising to XT2

[jfheath]

I've noticed in the past that items do not synchronise unless something has changed. Makes sense. There has to be a flag which I think @Frankb mentioned in his TripManager documentation. There are a few similar ones relating to routing preferences too, Cant remember the name offhand. 'HasItBeenChanged' will do for now.

There has to be a direction indicator too. Something that lets it know where the data was last altered and when. (One of those three is probably not required.). But without keeping track if that, the newly modified data could be overwritten by the old.

In fact all you may have to do is to resave the route on Tread that you want to be re-synched to the XT2.

The system does get confused if you have a number of devices. So for example i have Tread on an Ipad. I also have it in a phone. Both will synch to the XT2. At some point the XT2 decides which version it is paired with and then only synchs with that, not the other. Something like that anyway.

Note also that synchronising a lot of data takes a lot if time. It has to go from the Tread App to the Explore database via t'interweb. Then back to the XT2 via your phone's web or data connection, then from your phone to the XT2 via BT This delay is noticeable with a single route. It will be very noticeable with lots if data.

[turbo19]

I've noticed in the past that items do not synchronise unless something has changed. Makes sense. There has to be a flag which I think @Frankb mentioned in his TripManager documentation. There are a few similar ones relating to routing preferences too, Cant remember the name offhand. 'HasItBeenChanged' will do for now.

There has to be a direction indicator too. Something that lets it know where the data was last altered and when. (One of those three is probably not required.). But without keeping track if that, the newly modified data could be overwritten by the old.

In fact all you may have to do is to resave the route on Tread that you want to be re-synched to the XT2.

The system does get confused if you have a number of devices. So for example i have Tread on an Ipad. I also have it in a phone. Both will synch to the XT2. At some point the XT2 decides which version it is paired with and then only synchs with that, not the other. Something like that anyway.

Note also that synchronising a lot of data takes a lot if time. It has to go from the Tread App to the Explore database via t'interweb. Then back to the XT2 via your phone's web or data connection, then from your phone to the XT2 via BT This delay is noticeable with a single route. It will be very noticeable with lots if data.

I think it's impossible to explain it better @jfheath . Exactly as you say. That's why I disabled the synchronization option a long time ago.

As far as I've been able to investigate, the problems start when we have a lot of synchronized collections. Everything slows down, the Bluetooth gets saturated, the disconnections begin, etc.

[ZumoGSer]

FIXED temporarily I guess ( no help from Garmin ), lots of trial , error and failure .
1) Make sure that Tread shows itself synchronising , if not redo the setup ( firstly ignore the fact that the faulty Collections do not synchronise )
2) Tread , open the MAP and create a new waypoint and call it TEST
3) Tread ; save the TEST waypoint in EVERY COLLECTION , by selecting them all

You will then discover that all collections will synchronise and abd vanished will reappear

Magic !!!
4) Delete TEST , from the map ( which opens them all )

Easy !

My thinking is that something has confused the gpx files
A gpx file is completely overwritten as a new data file, when a new waypoint is added
A Collection is simply a gpx file , containing all waypoints and or routes .
Adding a new file to the Collecton creates a new gps , so adding your all effectively generates a complete new Collection

Fixes that Garmin users have to make because their software is regrettable. Do Garmin engineers do any tests? because if they left me in their office for 2 hours I would find several bugs in their software .