GarminConnect does not "support" Forerunner 305

[Simon.X]

I have tested TCXs from my Forerunner 305. They work fine with MotionBased, but GarminConnect claims not to support it. However I have made two experimental modifications to my copy of garmin-sync.

1) Comment out the product.id and hard code the string to "717" i.e. a Forerunner 405. Then GarminConnect is happy.

2) Add Cadence to the Trackpoint

[Simon.X (simon-lp)]

A patch to:
a) hack that lies about the product ID in the TCX to keep GarminConnect from claiming that the TCX+product is "upsupported".
b) Added Cadence to the Trackpoint data. This isn't used by MotionBased but is shown on GarminConnect.

Should the "lie" feature be hardwired? If it is then all our Garmin products would be claimed to be Forerunner 405s. In the short-term this may be fine but not a long-term fix. I propose that it is switched with a small config file.

Could use a small XML read/write application to patch the product_id value, which will become vestigial when Garmin get their act together. Then this patch becomes partially redundant and then we just write a XML patcher application.

[Simon.X (simon-lp)]

Now Garmin have modified GarminConnect it now supports the older units (Forerunner 305, etc), so now we don't need to lie in the TCX to keep it working.

This new patch only adds Cadence to the track points.

[Simon.X (simon-lp)]

mostly obselete patch. See the separate trackpoint cadence patch.