-
-
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
Errors when running Fortius without Ant+ dongles #123
Comments
Hi Erik, welcome in thee FortiusANT community. |
Hi Wouter, Thank you very much for the warm welcome and the quick support! No problem, I directly tried version 3.4 and it seems to work: The errors are not present anymore and runoff + calibration are working as they should. Many thanks in advance again for your help! Edit: I'm not sure if makes any difference, but I don't have the cadence sensor connected as well. |
Please create testrun with -d127 flag and send created logfile [ + wrong button 😛] |
@torpedox88 I believe the Fortius does this when it doesn't detect cadence, it's a safety mechanism I think. |
After some internet search I indeed found that the Fortius does not work without cadence sensor (most probably because of the reason you mentioned), so I will try to make the cadence sensor work first before creating a logfile |
I've added it to the manual; to be uploaded next round. This issue (running without dongles) can be closed; even though real test is pending. |
Do you by any chance know how this works for the Tacx iFlow? In other words, does the iFlow work properly without cadence sensor? |
A Tacx Fortius does not work without cadence sensor |
That's what I know by now since it made my Fortius work earlier this week, but some people around me became enthousiastic about FortiusANT as well so I'm looking for another legacy Tacx. |
Post the question as a separate issue, who knows who will be able to respond |
I have an IFlow and works with its internal Cadence (box) and with an external Ble or Ant+ Speed & Cadence. |
Tacx Fortius does not know "who" is at the other end of the USB cable. To my knowledge Fortius does not work without cadense sensor. I do not know the other trainere |
Hello everyone,
My name is Erik, 32 years old and living in the middle of the Netherlands, just a bit south of Utrecht.
After discovering and becoming very enthousiastic about turning legacy Tacx trainers into smart ones last week, I bought a used Tacx Fortius last weekend and ordered 2 Ant+ dongles, which are on their way from an obvious place to the Netherlands.
Off course I cannot wait until the dongles arrive, so I was pretty happy about the possibility of running FortiusANT in manual mode, such that I can already do some easy riding as TTS3 does not work anymore after a fresh install. However, after directly running fortiusant.exe and trying slightly different commands as fortiusant.exe -g -m I get the following error:
Microsoft Windows [Version 10.0.18363.1139]
(c) 2019 Microsoft Corporation. Alle rechten voorbehouden.
C:\FortiusANT\WindowsExecutable>fortiusant.exe -g -m
19:26:04,656: Connected to Tacx Trainer T1932
Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.py", line 932, in _bootstrap_inner
File "threading.py", line 870, in run
File "FortiusAnt.py", line 370, in Tacx2DongleThread
File "FortiusAnt.py", line 111, in Tacx2Dongle
File "FortiusAntBody.py", line 467, in Tacx2Dongle
File "FortiusAntBody.py", line 479, in Tacx2DongleSub
AssertionError
I searched already through all other issues and this one seems to match partly with #107, but it's not clear to me if it was solved and if the manual mode without Ant+ dongles with the Fortius was working in the end.
Hopefully someone can help me out with this issue since I eagerly want to ride my indoor bike :)
The text was updated successfully, but these errors were encountered: