-
-
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
Defining powercurve for Fortius... #7
Comments
Hi! If you want "more shifting" uphill adjust -r 150/100 to 250/100 and uphill must get heavier, compared to downhill. To make downhill even lighter, change -r into 150/-150 and see what happens. I did not try with a negative value and I'm curious to your experiences. Check "usbTrainer.py" function Grade2Resistance() shows that there has been quite some experimenting to get to an acceptable algorithm. option1 implements the formula from antifier and you could try that by changing the code "option=3" into "option=1". The comment in the code gives some more info. |
Ok, I will have a closer look at it.... at first sight looks very structured and the algorithms are well documented in code! |
As you probably know, FortiusANT can be run in manual mode. In that case you do not need Zwift or TrainerRoad, but the required power can be selected from the headunit. I have implemented the -M flag, for manual grade mode. Now you can test, setting the target grade. Start FortiusANT as follows: Of course: download the actual python files! (You linux updates have been incorporated) |
* TFT display proto#1 * TFT display proto#2 * TFT display final#3 * TFT display final#4 * TFT display final#5 * TFT display final#6 buttons #286 * TFT display #7 TFTdisplay for all trainers * TFT display #7 T1932 Windows, Raspberry * TFT display #8 GUI centered * TFT display #9 Manual + executable * Raspberry Pi installation update * Raspberry Pi Documentation update * TCX and Console cosmetics * Version 6.2 executable * Short message comment added
Just to be clear, I do not really have a lot of experience with Tacx, neither with Zwift. I primarily decided to buy the Fortius because I stumbled upon antifier and through antifier upon your solution.
I used the original Tacx software (3.5) once and did a video bike ride (Amstel Gold). During that ride I really noticed that the wheel speed is similar to the virtual speed. When I climbed a mountain, I really had to change gears to cope with the increased resistance.... downhill I really could stop pedalling because the rear wheel was driven bij the Fortius motor. I just finished my first real Zwift ride and noticed that it basically measures my power delivered and depending on the slope it changes my virtual bike speed (which really does not correspond with my real wheel speed). I have to read in detail through your wiki, but is this the behaviour you suspect? Apparently my Zwift trial period is ending... I think I will extend to continue optimising your solution....
Originally posted by @mtbiker22 in #3 (comment)
The text was updated successfully, but these errors were encountered: