Hello. I noticed when using your tool that the device is not appearing onto the Garmin Connect page. It used to show the watch I would be wearing that I could select on your tool. For curiosity, I tried it again and the same thing happened. I thought I should let you know.
The device I tried to set it to is a Garmin Edge 1000.
We usually just export it as a GPX file as you can see in the attached sample.
It used to show up with the device after uploading to Connect and or Strava but it no longer seems to be doing so.
Thank you.
FAQ: Device name not appearing on Garmin Connect (solved)
-
GotoesUser
- Posts: 26
- Joined: Wed Nov 25, 2020 2:32 pm
FAQ: Device name not appearing on Garmin Connect (solved)
Last edited by GotoesUser on Sat Aug 24, 2024 1:45 pm, edited 1 time in total.
FAQ: Device name not appearing on Garmin Connect (solved)
Yes. GPX does not allow for device name. When GPX was invented, the only purpose was positioning and time. Nevertheless, Strava created some extra (invalid) fields in GPX for things like power, temperature, and cadence. In GOTOES, I use the 'Cluetrust' schema, even though it is technically invalid on some other websites, it does work with Strava. It surprises me that this used to work with Garmin; it should never have worked.
TCX was created by Garmin when it became clear that people wanted to use GPS devices for athletic activities. TCX allowed for device name, position, heart rate, and cadence… but oddly not temperature. TCX generated HUGE but easy-to-read files, so it did not have a long life. It also allowed you to supply a device name - however ONLY A GARMIN NAME. In other words, instead of “Garmin Edge 1000,” the field would say, “Edge 1000”. The assumption back then was that Garmin was the only one making fitness devices. You could also put in a device serial number and Garmin could identify your device from the serial number as well. In TCX files, you can also insert a product ID number - but again, the assumption is that this is a Garmin product ID… so not very useful for other manufacturers as you will see below.
Most recently, Garmin created the FIT file format. This uses a numerical code to identify the manufacturer as well as another numerical code to identify the model. Put the two codes together, and you now know the exact device. Companies must pay Garmin to get on this list. Some companies (such as Polar) have not paid and they do not have an assigned manufacturer ID in the FIT world. Nevertheless, Polar still supplies a product ID. The problem is that you cannot identify a Polar device, because their product numbers overlaps with everyone else’s. Most manufacturers assign “1” to their first product.. so Suunto, Garmin, and everyone else all have a product #1; you do not know which is which unless you also know which company made the device.
Anyway, FIT is the best way to store the device ID. Garmin has become more strict lately, requiring a serial number in order for your activity to count towards challenges and badges.
Strava used to support interpreting (or “guessing”) devices from the text embedded in the TCX fieds and GPX fields. As a courtesy, GOTOES also supports this. If you open up a GOTOES TCX or GPX file using a text editor, you will see the name of your GPS in there - plain as day. However, Garmin seems to be dropping support for this (except maybe their own devices)… but GOTOES tries to be device agnostic, so GOTOES inserts “Garmin Edge 1000” instead of the more “correct” “Edge 1000”. Also, Garmin never supported this in GPX in the first place. Strava, on the other hand, seems to have grandfathered in older devices… and reluctantly updates their database to interpret TCX and GPX fields. They have a few bugs in their database that have persisted for years. The bottom line is that if you care about specifying the device type, FIT is the way to go.
TCX was created by Garmin when it became clear that people wanted to use GPS devices for athletic activities. TCX allowed for device name, position, heart rate, and cadence… but oddly not temperature. TCX generated HUGE but easy-to-read files, so it did not have a long life. It also allowed you to supply a device name - however ONLY A GARMIN NAME. In other words, instead of “Garmin Edge 1000,” the field would say, “Edge 1000”. The assumption back then was that Garmin was the only one making fitness devices. You could also put in a device serial number and Garmin could identify your device from the serial number as well. In TCX files, you can also insert a product ID number - but again, the assumption is that this is a Garmin product ID… so not very useful for other manufacturers as you will see below.
Most recently, Garmin created the FIT file format. This uses a numerical code to identify the manufacturer as well as another numerical code to identify the model. Put the two codes together, and you now know the exact device. Companies must pay Garmin to get on this list. Some companies (such as Polar) have not paid and they do not have an assigned manufacturer ID in the FIT world. Nevertheless, Polar still supplies a product ID. The problem is that you cannot identify a Polar device, because their product numbers overlaps with everyone else’s. Most manufacturers assign “1” to their first product.. so Suunto, Garmin, and everyone else all have a product #1; you do not know which is which unless you also know which company made the device.
Anyway, FIT is the best way to store the device ID. Garmin has become more strict lately, requiring a serial number in order for your activity to count towards challenges and badges.
Strava used to support interpreting (or “guessing”) devices from the text embedded in the TCX fieds and GPX fields. As a courtesy, GOTOES also supports this. If you open up a GOTOES TCX or GPX file using a text editor, you will see the name of your GPS in there - plain as day. However, Garmin seems to be dropping support for this (except maybe their own devices)… but GOTOES tries to be device agnostic, so GOTOES inserts “Garmin Edge 1000” instead of the more “correct” “Edge 1000”. Also, Garmin never supported this in GPX in the first place. Strava, on the other hand, seems to have grandfathered in older devices… and reluctantly updates their database to interpret TCX and GPX fields. They have a few bugs in their database that have persisted for years. The bottom line is that if you care about specifying the device type, FIT is the way to go.