john-38787364 / antifier

Convert the output from USB Tacx turbo trainers into ANT+ signals
MIT License
52 stars 20 forks source link

First tests with my Tacx Fortius Multiplayer #9

Open paha77 opened 6 years ago

paha77 commented 6 years ago

Yesterday I was able to assemble my trainer and my bike and made the first test.

Trainer: Tacx Fortius Multiplayer (https://static.bikehub.co.za/uploads/monthly_08_2017/hubmarket-19441-0-55170200-1502108820.jpg) Motor: T1941 (https://static.bike-components.de/cache/p/z1/2/0/Tacx-Motorbremse-T1941-fuer-Fortius-Fortius-Multiplayer-und-Cosmos-20336-0-1481266685.jpeg) Head unit: T1932 Fortius (https://i.ebayimg.com/00/s/MTA2NlgxNjAw/z/LREAAOSwzKBZ0D3a/$_58.JPG) OS: Ubuntu Linux 16.04, command line only, in a Virtualbox environment with OSX host

As you've suggested in the Zwift forum topic I've started with

python tacx_trainer_debug.py

I've attached the output:

tacx_trainer_debug.log

Note to the trainer debug: as my Tacx trainer tyre is not arrived yet, I was on normal road tyre and above resistance level 7-8000 I had the feeling that it wasn't harder to pedal any more until 13000. But this was the same feeling in the original training software.

Then I've started

sudo python antifier.py -l -c power_calc_factors_fortius.txt -d

run Zwift and started riding on the London track. After 1-2 kilometers something was broken and switching to Ubuntu I've seen the following error:

kp

Disconnecting the trainer and the sensors did not help, I hat to restart the whole virtual environment.

Then I've restarted Zwift and rode another 3-4 km's but somehow I had the feeling that there's no connection between the resistance I have from the trainer and the road in Zwift. I was riding with 8 km/h in a moment and in the next with 44 km/h.

That was my first test. Have I done something wrong or have I forgotten something?

Thank you.