This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Training load - combine 2 devices

Hi,

got a replacement FR945 and added it to GC. When now looking to the training load screens (GC mobile and web), the training load and the training status is split in two devices (either the old or the new devices values are shown). VO2max is shown over both devices. Is there a way to combine the two devices?

thanks

  • The VO₂Max is being calculated directly on the watch, so unless you have copied all respective fit files from the old watch to the new one, it starts calculating anew. GC does not offer any option for merging the results.

  • That's clear to me. What i don't understand: the values (VO2max, trainingload) are calculated by the watch and then sent to GC for long term analysis. 

    Why, for V02max there is a combination of both devices (old and replacement) in one graph but for trainingload i need to select the device to show the whole period.

    OLD watchNEW watch

    Data is still there, just uncomfortable to display. I just don't get the "advantage" of separating it.

  • Why, for V02max there is a combination of both devices (old and replacement) in one graph but for trainingload i need to select the device to show the whole period.

    It comes from the design of the system. Currently, the data is always bound to the device (not to the user), and kept separately. In programming it is called an object. The devices may be used botth simultaneously and consequently, and since they do not give any true VO₂Max vvalues anyway, rather just estimates, which at each device may be diametrically different, it is safer to keep the data separate. All functions for displaying the data, plotting the graps, etc, are build for the object (the device), not for the user. 

    I am not telling that it is the right way. I agree that it would be still usefull to see the data merged, but I also understand that it would require a serious change in the handling of the data, which is currently device-based. So techically taken, your suggestion could be certainly implemented, but it would require an important structural change in the software with a load of new problems that it would trigger, and that would have to be addressed by the developers. For that reason, I do not believe much, that the change will happen any soon (unless there is a strong pressure from the competition offering a better solution).