-
Notifications
You must be signed in to change notification settings - Fork 3
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
How to detect Headunit and Motorbrake Tacx Types #8
Comments
As far as I understand it: the newer T1904 and T1932 head units have their own power model for the eddy current trainers inside their firmware and they emulate what you call "type 2" formula. EDIT #1 I think, I cannot help in the refactoring issue, because I am not experienced in writing high quality python code - the tty1941 project was also one of my first python programs .. EDIT #2 fine if someone else can benefit from the information I found during my investigations ... |
|
|
Went through this and the wiki again... My take of it is that in FortiusANT I should consider two USB-interfaces 1902 and 1904/1932/1942 and not worry about all kinds of commercial names and combinations. (ANT+ Vortex aside). At the software side all I can know is these USB-id's and the related buffer length. If you agree: issue close - else I like to read. |
Thanks. |
Hit @totalreverse !
I get questions about a "Tacx Flow i-Magic T1901 trainer with the T1932 head unit"
Untill now life seemed easy, checking the USB deviceID
and I lived in the easy world:
But now we have 64byte interface with Power2Resistance-formula type 1
How do I know what is what?
Any suggestions?
PS. I will have a meeting with @mattipee shortly discussing the refactoring of the usbTrainer interface. If you like to join in, ping me on messenger.
Thanks for all the information you share; it's a very nice experience to be connecting around the globe through the inhouse-Tacx adventures people play - even though at times sadly triggered by the Corona situation.
The text was updated successfully, but these errors were encountered: