Charge entraînement

Bonjour, j’ai un décalage important entre ma charge affichée sur garmin et ma charge sur interval. Exemple séance de fractionné de ce matin sur garmin charge 134. Sur interval charge de 57. Y un t’il un souci dans la récupération des données de charge sur interval ? Merci d’avance

Garmin Exercise Load is NOT the same as TSS.
Garmin displays both Exercise Load and TSS. Make sure to compare the correct values. TSS will be the same within a couple decimals, off course only if you are using Power for load.
If not using Power (HR or Pace) values for load will be different, but trend will be the same. There’s no ‘standard’ for HR and/or Pace load.

I don’t speak French, but Google says OP is talking about the HR itself, not the load? Forum translates like so:

Hello, I’m experiencing a significant discrepancy between my heart rate displayed on Garmin and my interval training heart rate. For example, this morning’s interval session showed a heart rate of 134 on Garmin, but only 57 on interval training. Is there a problem with the retrieval of heart rate data for interval training? Thank you in advance.

@Boris_Savary , can you show screenshots of what you mean?

1 Like

That’s wild, I don’t know why Google translate it with heart rate (I see it too), but charge should be load, not heart rate.

I do speak French. He’s talking Load.

Cool… and wild in this day and age. :man_shrugging:

Living in a country with three ‘official’ languages, Dutch, French and German, and being a tech guy, for which English is a must, doesn’t leave you much choice to have at least basic skills, I guess.

No I meant wild that Google translate makes such a basic error. :blush:

It is cool that you guys are so multi langual over there, though. Here in Germany only English is mandatory, we can freely pick further languages in school… for some reason my parents back then thought that Latin would make me wiser than French. Nunc est bibendum, hic.

Ah, I interpreted that differently.
And yes, one would expect that AI translations didn’t make that kind of errors, simply assuming that load = HR Load.