-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Power curve validation #463
Comments
Hi! Good that you look into this. How do you know the power isincorrect; feeling or power meter? The latter is a good help. Please note that these legacy trainers should be compared to the modern tacxes. Yes we can connect to modern software, the trainer is "old design and capabilities". Succes and let me know |
My setup is following: |
Q1: please explain how you know that it's toomuch🤔 Rouvy transmits the real value for slope. 10% is received as 10%, whereas Zwift Shows 10% in it's own windows but transmits a lower value. Real slope percentages cause noticeable resistances. You can adjust this in FortiusAnt using the - G parameter, see manual |
I would say -c works, but you have to provide the correct value |
What am I doing wrong? I put there -c 14 or -c14 as decribed on page 42 of Manual and I receive error message "command line error" |
I modified https://github.com/WouterJD/FortiusANT/blob/master/pythoncode/FortiusAntCommand.py#L368 Sorry for the inconvenience |
See comment |
Thnx. It works somehow. It seems, that powercurve is slightly different in low power, like 110W, but still in tollerance I use |
Greate that the issue is sufficiently solved! |
I have i-Magic 1902 + Rouvy. The trainer breaks more, then it is required. Is it enough to calibrate it by decreasing parameter -c or should I implement some function described in 6.3 section of Manual?
The text was updated successfully, but these errors were encountered: