Trainer Not Detected

[RodeTheAlpe]

Seems like everything is working up until locating head unit (drivers, VendId, etc.).
Running from the build_x64 directory gave me a couple of errors looking for fxload-libusb.exe and FortiusSWPID1942Renum.hex which are in the main directory. I tried copying those two into the build_x64 directory and still no luck.
Any ideas, I'd love to get this working. Thanks!

[WouterJD]

If antifier does not work at this point, I probably do not have a solution either.
You might check https://github.com/WouterJD/FortiusANT/ which is a successor of antifier.

[RodeTheAlpe]

Thanks I’ll check it out. Jeff

…

On Jan 22, 2020, at 1:39 PM, WouterJD ***@***.***> wrote: If antifier does not work at this point, I probably do not have a solution either. You might check https://github.com/WouterJD/FortiusANT/ which is a successor of antifier. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[WouterJD]

In case of questions, please post on https://github.com/WouterJD/FortiusANT/ thanks

[Lorangaw]

I had the same problem with my I-magic 1904. It seems that I managed to solve it. In the bottom section of the trainer.py file, there is a function "def get_trainer()".
In this function is a variable definition "idpl = [0x1904, 0x1932, 0x1942, 0xe6be]#iflow, fortius, uninitialised fortius" . The function scans the USB ports for one value at a time from that list valuue. My trainer was missing in that list definition. In my pasted quote you can find 0x1904. That is added by me and is the i-magic trainer that I have. I am running Ubuntu Linux and used the command sudo lsusb while trainer was connected to the computer. From that output did I get the "1904" value.

I would propose you do the following to solve the issue:

1. plug in the trainer
2. open a text promt and type the command sudo lsusb
3. see if you find the trainer in that list (see my screenshot, it was easy to find the trainer. Note that you also find the ant dongle)
4. open a text editor and add your trainer number to the list variable "idpl"
5. save and close trainer.py file
6. sudo python antifier

I suppose problem and solution is the same in Windows. Only different tools.

[WouterJD]

Thanks for your feedback!

The 1904 was implemented in 2020-02-25 version of usbTrainer.py, introducing variables for the constants.:
tt_iMagicWG = 0x1904 # New "white green" iMagic headunit (firmware inside)

I have implemented the constants from @totalreverse interface definitions; when new types are required I will update the list. I do not expect many updates.
The code detects known trainers but does not detect unknown trainers but simply ignores them. This is not the nicest approach (a message "unsupported Tacx trainer" would be nicer), but perhaps (considering where we are in the lfe-time of USB-trainers) acceptable.

Regarding "I would propose you do the following to solve the issue:" do you mean additional updates are required?

[WouterJD]

Please sign WouterJD/FortiusANT#14 thanks

[Lorangaw]

Hi, my proposal is more as a proposal to quick fix the issue. The intended recipient for that message was the person who raised the issue. Thanks for a great project. It will keep my trainer alive now after Tacx has ended the support for the software. Best regards Morgan Den fre 13 mars 2020 10:08WouterJD <[email protected]> skrev:

…

Thanks for your feedback! The 1904 was implemented in 2020-02-25 version of usbTrainer.py, introducing variables for the constants.: tt_iMagicWG = 0x1904 # New "white green" iMagic headunit (firmware inside) I have implemented the constants from @totalreverse <https://github.com/totalreverse> interface definitions; when new types are required I will update the list. I do not expect many updates. The code detects known trainers but does not detect unknown trainers but simply ignores them. This is not the nicest approach (a message "unsupported Tacx trainer" would be nicer), but perhaps (considering where we are in the lfe-time of USB-trainers) acceptable. Regarding "I would propose you do the following to solve the issue:" do you mean additional updates are required? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJLCTCYTHL6ANMZ33LGC6DRHHZYJANCNFSM4KKLE4RA> .

[WouterJD]

Anxious to see your results on Strava/insta👍 Met vriendelijke groeten Wouter Dubbeldam On Fri, Mar 13, 2020 at 12:14 PM +0100, "Lorangaw" <[email protected]> wrote: Hi, my proposal is more as a proposal to quick fix the issue. The intended recipient for that message was the person who raised the issue. Thanks for a great project. It will keep my trainer alive now after Tacx has ended the support for the software. Best regards Morgan Den fre 13 mars 2020 10:08WouterJD <[email protected]> skrev:

Thanks for your feedback! The 1904 was implemented in 2020-02-25 version of usbTrainer.py, introducing variables for the constants.: tt_iMagicWG = 0x1904 # New "white green" iMagic headunit (firmware inside) I have implemented the constants from @totalreverse <https://github.com/totalreverse> interface definitions; when new types are required I will update the list. I do not expect many updates. The code detects known trainers but does not detect unknown trainers but simply ignores them. This is not the nicest approach (a message "unsupported Tacx trainer" would be nicer), but perhaps (considering where we are in the lfe-time of USB-trainers) acceptable. Regarding "I would propose you do the following to solve the issue:" do you mean additional updates are required? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJLCTCYTHL6ANMZ33LGC6DRHHZYJANCNFSM4KKLE4RA> .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[Lorangaw]

I tried to use only a windows 10 computer with two ANT dongles. I got the same problem and the solution was obviously the same. I added 0x1904 to the trainer.py and it works!

[WouterJD]

Thanks I’ll check it out. Jeff
…

Hi Jeff, any results?

[RodeTheAlpe]

Thanks I’ll check it out. Jeff
…

Hi Jeff, any results?

Have not had time to get back to this but it's on my list of things to do. I'll definitely update here when it's up and running. Thanks for the fix!

[RodeTheAlpe]

WouterJD no luck so I moved over to FortiusANT but having some strange results there. I'll post on that page and see if you can help. Thanks

[WouterJD]

Jeff, I will try to assist as soon as info provided👍