Problem connecting Fortius T1942 to FortiusAnt

yancart commented 3 years ago

Hi, similar problem as BarryO1. I have a Tacx Fortius (without steering) with T1932 display and a laptop with Windows10 64 bit on it. Have downloaded and installed FortiusAnt following the FortiusAnt manual and the libusb-win32_T19xx packaged USB driver. I am planning to run TTS4 and FortiusAnt on the same laptop as it seems this is possible from comments in sec 5.4. To start up FortiusAnt, I use the Windows executable and I installed the Windows prepacked drivers.

I started FortiusAnt without additional command-line parameters and the FortiusAnt GUI appeared. However, although my Fortius was connected to the computer by the Tacx USB device, FortiusAnt did not recognize my Fortius. I got the message 'No Tacx trainer found'.

Ive checked my drivers and this looks ok:-

Has anyone seen this problem? Thanks

switchabl commented 3 years ago

@yancart It seems the driver package doesn't automatically replace the Tacx driver in some cases, so you will have to select it manually. I will probably add that to the driver README.

Right-click on the "Fortius_Unint" device
Update Driver Software...
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
There should be an item "Tacx T1942 (no firmware)", install that.

You will likely have to repeat this once after you start FortiusANT for the first time (and the firmware is loaded). The device will then be called "Fortius" and the right driver is "Tacx T1942".

yancart commented 3 years ago

Hi, cant seem to find the Tacx T1942 driver. Which bundle should that have come with the t19xx_usb-main.zip or the libusb-win32-bin-1.2.6.0.zip? Thanks

switchabl commented 3 years ago

@yancart That should have been installed with the libusb-win32_T19xx.exe package (https://github.com/switchabl/t19xx_usb/releases/download/v1/libusb-win32_T19xx.exe). Looks like that didn't work for some reason?

Anyway, if all else fails, use Zadig (https://zadig.akeo.ie/) to install manually. In my experience, that almost always works, it is just a few clicks more.

Run Zadig
Options -> List All Devices
Find the "Fortius_Unint" device in the drop-down list
Choose libusb-win32 (v1.2.6.0) as driver
Click "Replace Driver" (or possibly "Install Driver")
Run FortiusANT to load the firmware and repeat with the "Fortius" device if necessary

yancart commented 3 years ago

Hi switchabl, Many thanks for the info. Tried the driver update and all seemed ok but still having problems...

So ran Zadig and selected Fortius-Unint:-

Then selected the correct libusb-win32 driver:-

Then rebooted laptop and ran FortiusAnt and still no connection to Fortius trainer:-

Then rechecked the drivers and now I get this:- Seems Jungo has changed from Fortius-Unint to Fortius => is this correct?

Then recheked with Zadig and now I get this:- So no drivers listed now?

Any thoughts...? Thanks

switchabl commented 3 years ago

@yancart The change from "Fortius_Unint" to "Fortius" is as expected and the procedure needs to be repeated for "Fortius". After you have started FortiusANT and the firmware is loaded, the "Fortius" should show up in Zadig. Did you enable "Options -> List All Devices"?

The T1942 is slightly annoying in this respect. That is the reason the driver package was created as it normally takes care of this automatically. But for some reason it didn't work for you so you need to take the long way 'round.

yancart commented 3 years ago

Hi @switchabl, Progress at last and FortiusAnt now seems to be connected to the Fortius unit and is showing pwr/speed and cadence. But next step is to get this connected to Zwift and there now seems to be an issue with the USB ANT device in that its pairing with Zwift ok but not sending any data? Its interesting to see that there is a regular error/dropout of the FortiusAnt info display (see below):-

The Zwift app seems to be all paired ok, just no data is being Rx:-

Ive swapped the ANT dongles around and same problem. Im running FortiusAnt and one win10 laptop and Zwift on another win10 laptop and both are running at about 30/40% CPU capacity... Have you seen this before? Thanks

WouterJD commented 3 years ago

Unfortunately yes: yesterday evening. This afternoon -same configuration- no issues.

Please try to powerdown and reboot to check.

WouterJD commented 3 years ago

At my side I can confirm: had the same problem, did not happen before and after a good night's rest (I was done with it yesterday) I cannot reproduce. Systems has been in sleep-mode, so a sort-of restart.

MeanHat commented 3 years ago

Hi @yancart and @WouterJD - I have had similar issues with "Connected" and "No Signal" messages. Once I confirmed that the Bluetooth devices were within range the problem was caused by other programs/apps hijacking the Bluetooth connection. Searching for and then removing these apps or their permissions resolved the problem.

yancart commented 3 years ago

Hi tried rebooting both laptops still the and same issue. For ref Ive got two ANT dongles, one in each laptop. Does ExplorAnt help for diagnosing these issues, seems to show similar ANT dropout/restart issues.... Thanks

MeanHat commented 3 years ago

Sorry @yancart - my comment related to BLE and you are using ANT.

WouterJD commented 3 years ago

OK. I have done some more tests. A write() appears to fail when there are (many) messages waiting to be processed. At my side I was improving the ANT-loop and it appears I have to flush the pending messages before sending.

I do not understand why this would occur in your case, because (I think) you did not change anything there.

Please provide logfile as created with the -d127 flag

WouterJD commented 3 years ago

Well... issue not solved:

12:55:14,914: ---------- ANT-devices are activated ----------
12:55:14,914: Tacx2Dongle; start main loop
12:55:14,914: clsTacxTrainer.Refresh(True, 2)
12:55:14,914: clsTacxNewUsbTrainer._ReceiveFromTrainer()
12:55:14,914: Trainer recv hdr=0x21303 data="array('B', [32, 208, 32, 0, 0, 2, 0, 0, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 223, 3, 0, 0, 0, 0, 3, 19, 2, 0, 50, 90, 20, 0, 188, 22, 128, 89, 0, 0, 65, 252, 0, 0, 0, 0, 0, 0, 3, 241, 252, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0])" (len=64)
12:55:14,914: ReceiveFromTrainer() = hr=0 Buttons=0 Cadence=0 Speed=20.1 TargetRes=0 CurrentRes=-959 CurrentPower=-43, pe=0 hdr=0x21303 Connected to Tacx Trainer T1932
12:55:14,914: clsTacxNewUsbTrainer.TargetPower2Resistance(100, 5820) = 2214
12:55:14,914: clsTacxUsbTrainer.SendToTrainer(T=2, M=1, P=100, G=0, R=2214, W=85, PE=0, S=20.1, C=0)
12:55:14,914: Trainer send data="01 08 01 00 a6 08 00 00 02 0a 10 04" (len=12)
12:55:14,914:                   tacx mode=2 target=2214 pe=0 weight=10 cal=1040
12:55:14,914: Flush ANT dongle buffer
12:55:14,914: devAntDongle.__ReadAndRetry(0x81,1000,1) ...
12:55:14,914: ... done
12:55:14,914: devAntDongle.read() returns ["a4", "03", "40", "00", "01", "03", "e5"] 
12:55:14,914: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,914: devAntDongle.__ReadAndRetry(0x81,1000,1) ...
12:55:14,930: ... done
12:55:14,930: AntDongle.Read() returns: ["a4 03 40 00 01 03 e5"]
12:55:14,930: Dongle    send   : synch=0xa4, len= 9, id=0x4e Broadcast Data       , check= 0xf, info="02 10 01 ff 00 00 00 00 00" (ch=2 p=16(Main data page))
12:55:14,930: devAntDongle.write(0x01,"a4 09 4e 02 10 01 ff 00 00 00 00 00 0f") ...
12:55:14,930: ... done
12:55:14,932: devAntDongle.__ReadAndRetry(0x81,1000,1) ...
12:55:14,932: ... done
12:55:14,932: devAntDongle.read() returns ["02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef"] 

12:55:14,932: Dongle.Read: 4 characters skipped

12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,932: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:55:14,947: Dongle    receive: synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)

WouterJD commented 3 years ago

Second example

12:52:51,952: Calibrate()
12:52:51,952: ResetDongle()
12:52:51,952: Dongle    send   : synch=0xa4, len= 1, id=0x4a Reset System         , check=0xef, info="00"
12:52:51,952: devAntDongle.write(0x01,"a4 01 4a 00 ef") ...
12:52:51,952: ... done
12:52:52,467: Dongle    send   : synch=0xa4, len= 2, id=0x4d Request Message      , check=0xbf, info="00 54" (ch=0, msg=0x54)
12:52:52,467: devAntDongle.write(0x01,"a4 02 4d 00 54 bf") ...
12:52:53,483: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n'
12:52:53,483: ... done
12:52:53,483: Dongle    send   : synch=0xa4, len= 2, id=0x4d Request Message      , check=0xd5, info="00 3e" (ch=0, msg=0x3e)
12:52:53,485: devAntDongle.write(0x01,"a4 02 4d 00 3e d5") ...
12:52:54,501: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n'
12:52:54,501: ... done
12:52:54,501: Dongle    send   : synch=0xa4, len= 9, id=0x46 Set NetworkKey       , check=0x64, info="00 b9 a5 21 fb bd 72 c3 45"
12:52:54,503: devAntDongle.write(0x01,"a4 09 46 00 b9 a5 21 fb bd 72 c3 45 64") ...
12:52:55,518: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n'
12:52:55,518: ... done
12:52:55,518: Dongle    send   : synch=0xa4, len= 9, id=0x46 Set NetworkKey       , check=0xea, info="01 00 00 00 00 00 00 00 00"
12:52:55,520: devAntDongle.write(0x01,"a4 09 46 01 00 00 00 00 00 00 00 00 ea") ...
12:52:56,536: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n'
12:52:56,536: ... done
12:52:56,536: devAntDongle.__ReadAndRetry(0x81,1000,1) ...
12:52:56,538: ... done
12:52:56,538: devAntDongle.read() returns ["a4", "03", "40", "00", "01", "03", "e5"] 
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,538: devAntDongle.__ReadAndRetry(0x81,1000,1) ...
12:52:56,538: ... done
12:52:56,538: devAntDongle.read() returns ["a4", "03", "40", "00", "01", "03", "e5", "a4", "09", "4f", "00", "31", "ff", "ff", "ff", "ff", "ff", "c8", "00", "e4", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "03", "e7", "a4", "09", "4f", "02", "02", "fd", "ff", "ff", "fc", "fc", "fd", "fc", "1e", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "09", "4f", "02", "46", "ff", "ff", "fe", "ff", "04", "02", "01", "a0", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "09", "4f", "00", "31", "ff", "ff", "ff", "ff", "ff", "c8", "00", "e4", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "03", "e6", "a4", "03", "40", "00", "01", "03", "e5", "a4", "03", "40", "06", "01", "03", "e3", "a4", "03", "40", "02", "01", "03", "e7", "a4", "03", "40", "03", "01", "09", "ec", "a4", "03", "40", "00", "01", "09", "ef", "a4", "03", "40", "06", "01", "09", "e9", "a4", "03", "40", "02", "01", "09", "ed", "a4", "03", "40", "03", "01", "09", "ec", "a4", "01", "6f", "20", "ea"] 
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 9, id=0x4f Acknowledged Data    , check=0xe4, info="00 31 ff ff ff ff ff c8 00" (ch=0 p=49(Target Power))
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,538: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 9, id=0x4f Acknowledged Data    , check=0x1e, info="02 02 fd ff ff fc fc fd fc" (ch=2 p=2(HRM Manufacturer info))
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 9, id=0x4f Acknowledged Data    , check=0xa0, info="02 46 ff ff fe ff 04 02 01" (ch=2 p=70(Request Datapage))
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 9, id=0x4f Acknowledged Data    , check=0xe4, info="00 31 ff ff ff ff ff c8 00" (ch=0 p=49(Target Power))
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe6, info="03 01 03" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe5, info="00 01 03" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe3, info="06 01 03" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe7, info="02 01 03" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xef, info="00 01 09" (ch=0, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xe9, info="06 01 09" (ch=6, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xed, info="02 01 09" (ch=2, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 3, id=0x40 Channel Response     , check=0xec, info="03 01 09" (ch=3, msg=0x1)
12:52:56,554: Dongle    drop   : synch=0xa4, len= 1, id=0x6f Start up             , check=0xea, info="20"

WouterJD commented 3 years ago

In both cases above (incorrect received message and reap-error) after this error, a burst of messages come from the ANT-interface.

yancart commented 3 years ago

where isthe -d127 log file stored and is that the actual name "-d127.log"...? Thanks

WouterJD commented 3 years ago

please check manual. The logfile is stored in the current directory.

yancart commented 3 years ago

Have checked as per the manual? I have the FortiusAnt app as a shortcut on the desktop. Searched the whole hdd and cant see any log file? Thanks

WouterJD commented 3 years ago

If you check the StartUp directory You can use "FortiusAnt (gui) d.bat" as an example The logfile will be found in that directory

yancart commented 3 years ago

Hi, sorry still no luck finding the .log file. There are no FortiusAnt files in either of the StartUp dirs:- C:\Users\Clive\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup or C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

The FortiusAnt app is kept here and started by a shortcut on the desktop, but there are no log files here: C:\Tacx\FortiusAnt sw

Any other places it might be? Thanks

yancart commented 3 years ago

Hi, still no luck finding the log file... Any other ideas where I might it? Thanks

MeanHat commented 3 years ago

Hi @yancart - have you tried searching you C: drive for a *.log file? If this still does not find any log files please let me know and I will check my Windows installation. Are you launching using the Windows executable or through python?

yancart commented 3 years ago

Yes tried that and yes lots of .log files but no FortiusAnt files. Is it called -d127.log or FortiusAnt.log as cant see these? I'm using the windows exe... Thanks

MeanHat commented 3 years ago

Yes tried that and yes lots of .log files but no FortiusAnt files. Is it called -d127.log or FortiusAnt.log as cant see these? I'm using the windows exe... Thanks

Hi @yancart - I started up Windows version of FortiusANT using argument -d1 and the log files were with the python code (in my case C:/Github/FortiusAnt/FortiusANT-master/pythoncode. From memory the files are named something like FortiusAnt-dd-mm-yy-hh-mm-ss.log and FortiusAntGUI-dd-mm-yy-hh-mm-ss.log. Let me know if you need the exact name.

RodeTheAlpe commented 3 years ago

When I use the Windows Executable the log file winds up in the FourtiusANT-master/WindowsExecutable directory ex. FortiusAnt.2021-01-23 15-36-50.log

Take a look there

WouterJD commented 3 years ago

Is this issue still active? If there is no communication here, I assume can be closed.

yancart commented 3 years ago

Hi, Yes still trying to get this to work correctly. The -d1 option seems to workok and generates a txt file. I have been able to connect to zwift occasionally but it seems very intermittent. Also when it has connected ok and a session is running on zwift, the motor seems to change between harder and easier every minuite or so whan on the flat which isnt right as it work fine for TX4. I thought this might smthg to do with the motor calibration, but after calibtrating several times successfully its had no effect on this "hunting". Is this smthg youve seen before? I'll send through the txt file if this helps.. Thanks

BarryO1 commented 3 years ago

Hi,

The way that was succesful for me, is the following:

I use TTS4 while the trainer is connected to USB port 1. So, check that the trainer is connected to the USB port you want to use with TTS.
Switch the trainer to the USB port you want to use with FortiusANT (I use USB port 3), the device manager should automatically assign the Jungo driver by default
Download the libusb driver as described in chapter 3.6.2. of the manual. Do not uninstall the TTS-driver.
Install the libusb driver (by executing the 64 bit version in case of Windows 10) and follow install option 1 in chapter 3.6.2 of the manual so that the driver is now assigned to the trainer. -Then, I put my Suunto ANT+ dongle in USB port 1 and I start FortiusAnt with parameters -a -g -A.
Calibrate as described in 4.1.4. of the manual.
After calibration, my heart rate is shown in the GUI and I put my second ANT+ dongle (brand: Anself) in USB port 2.
Now I am ready and I start Zwift.

For me this works perfect as Windows remembers which driver to choose for which USB port. So I don't have to fiddle with the drivers anymore. I just marked the USB ports so it is easy to see where to put in the trainer for which use case ;)

WouterJD commented 3 years ago

@BarryO1 thanks, I have added it to the manual

WouterJD commented 3 years ago

It seems we are discussing different issues in one thread:

Connect T1942, seems solved
TTS or FortiusAnt
Stuttering power

Regarding "motor seems to change between harder and easier every minuite or so"; I would suggest to have a clear installation avoiding that multiple packages are addressing the same trainer.

yancart commented 3 years ago

Hi WouterJD, the connection to Zwift still seems to be intermittent and was thinking the stuttering power was the same/similar issue? The log file now seems to work fine with d1 added. Below is the log file for an attempt to connect to Zwift and a flat route. Seems there are regular wrire exception messages, whichcoulld be tying in with the load change on the motor? The calibration seems to complete ok without issue? I can start a new thread if that helps? Thanks

09:46:38,377: FortiusANT started 09:46:38,379: Restart=False debug=1 09:46:38,379: -c False 09:46:38,379: -C 0/0 09:46:38,379: -d 1 (0b1) 09:46:38,379: -D None 09:46:38,379: -H None 09:46:38,379: -p 1.0 09:46:38,387: -R defines Runoff: maxSpeed=40 dip=2 minSpeed=1 targetTime=7 power=100 09:46:38,387: -t False 09:46:38,387: -T [34, 50] x [34, 30, 27, 25, 23, 21, 19, 17, 15, 13, 11] (start=50x19) 09:46:38,387: ------------------ 09:46:38,387: Windows executable started 09:46:38,387: Version info for the components 09:46:38,550: Version=Fortius Antifier v5.2, on github=Fortius Antifier v5.2. 09:46:38,550: Fortius Antifier v5.2 09:46:38,550: FortiusAnt = 2021-01-10 09:46:38,550: antDongle = 2020-12-30 09:46:38,550: antFE = 2020-12-28 09:46:38,550: antHRM = 2020-12-27 09:46:38,550: antPWR = 2020-12-28 09:46:38,550: antSCS = 2020-12-27 09:46:38,550: bleDongle = 2021-01-04 09:46:38,550: constants = 2021-01-18 09:46:38,550: debug = 2020-12-18 09:46:38,550: FortiusAntBody = 2021-02-03 09:46:38,550: FortiusAntCommand = 2021-02-01 09:46:38,550: FortiusAntGui = 2021-02-01 09:46:38,550: logfile = 2020-11-25 09:46:38,550: RadarGraph = 2020-05-07 09:46:38,550: settings = 2021-01-19 09:46:38,550: structConstants = 2020-01-25 09:46:38,550: TCXexport = 2020-12-20 09:46:38,550: usbTrainer = 2021-01-12 09:46:38,550: argparse = 1.1 09:46:38,550: numpy = 1.19.4 09:46:38,550: os = nt 09:46:38,550: windows = 10.0 09:46:38,550: pickle = 4.0 09:46:38,550: platform = 1.0.8 09:46:38,550: sys (python) = 3.8.1 (tags/v3.8.1:1b293b6, Dec 18 2019, 22:39:24) [MSC v.1916 32 bit (Intel)] 09:46:38,550: usb = 1.1.0 09:46:38,550: wx = 4.1.1 09:46:38,550: FortiusANT code flags 09:46:38,550: UseMultiProcessing = True 09:46:38,550: UseGui = True 09:46:38,550: UseBluetooth = True 09:46:38,550: ------------------ 09:46:38,550: Scan for hardware 09:46:38,550: Get Dongle 09:46:39,166: Dongle - Using CYCPLUS dongle 09:46:39,166: Get Tacx Trainer 09:46:39,197: Connected to Tacx Trainer T1942 09:46:39,598: Motor Brake Unit Firmware=0x1004 Serial= 5395 year=2007 type=T1941 Version2=3077 MotorBrake=True 09:46:39,744: FortiusAnt applies the MotorBrake power curve 09:46:39,980: Tacx - Connected to Tacx Trainer T1942 09:46:39,996: AntHRM - Heartrate expected from Tacx Trainer 09:46:39,996: Scan for hardware - end 09:46:41,493: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:46:41,694: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:46:41,895: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:46:42,095: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:46:42,311: FortiusANT receives commands from an ANT+ Generic Remote Control 09:46:42,543: Ctrl-C to exit 09:46:42,543: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:46:49,236: Tacx - C A L I B R A T I N G (Do not pedal) 09:46:49,299: Target= 0W Speed=19.5kmh hr= 0 Current= 0W Cad=120 r= 628 T= 0 0 0 09:46:50,522: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=118 r=1072 T= 0 0 0 09:46:51,579: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=117 r=1074 T= 0 0 0 09:46:52,656: Target= 0W Speed=19.9kmh hr= 0 Current= 0W Cad=116 r=1076 T= 0 0 0 09:46:53,783: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=115 r=1073 T= 0 0 0 09:46:54,833: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=114 r=1063 T= 0 0 0 09:46:55,926: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=113 r=1059 T= 0 0 0 09:46:56,967: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=112 r=1045 T= 0 0 0 09:46:58,016: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad=111 r=1047 T= 0 0 0 09:46:59,073: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=110 r=1036 T= 0 0 0 09:47:00,123: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=109 r=1034 T= 0 0 0 09:47:01,163: Target= 0W Speed=20.2kmh hr= 0 Current= 0W Cad=108 r=1039 T= 0 0 0 09:47:02,198: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad=107 r=1021 T= 0 0 0 09:47:03,339: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=106 r=1021 T= 0 0 0 09:47:04,425: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=105 r=1014 T= 0 0 0 09:47:07,141: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=105 r=1014 T= 0 0 0 09:47:08,437: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=104 r= 999 T= 0 0 0 09:47:09,777: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=102 r= 991 T= 0 0 0 09:47:10,840: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=101 r= 986 T= 0 0 0 09:47:12,080: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad=100 r= 984 T= 0 0 0 09:47:13,174: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 99 r= 975 T= 0 0 0 09:47:14,241: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 98 r= 978 T= 0 0 0 09:47:15,353: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 97 r= 980 T= 0 0 0 09:47:16,383: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 96 r= 971 T= 0 0 0 09:47:17,439: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 95 r= 968 T= 0 0 0 09:47:18,474: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 94 r= 959 T= 0 0 0 09:47:19,523: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 93 r= 966 T= 0 0 0 09:47:20,596: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 92 r= 955 T= 0 0 0 09:47:21,681: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 91 r= 954 T= 0 0 0 09:47:22,746: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 90 r= 946 T= 0 0 0 09:47:23,811: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 89 r= 949 T= 0 0 0 09:47:24,865: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 88 r= 947 T= 0 0 0 09:47:25,899: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 87 r= 954 T= 0 0 0 09:47:26,945: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 86 r= 944 T= 0 0 0 09:47:28,192: Target= 0W Speed=19.9kmh hr= 0 Current= 0W Cad= 85 r= 934 T= 0 0 0 09:47:29,196: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 84 r= 937 T= 0 0 0 09:47:30,232: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 83 r= 931 T= 0 0 0 09:47:31,273: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 82 r= 928 T= 0 0 0 09:47:32,323: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 81 r= 927 T= 0 0 0 09:47:33,528: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 80 r= 932 T= 0 0 0 09:47:34,779: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 79 r= 929 T= 0 0 0 09:47:35,841: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 78 r= 926 T= 0 0 0 09:47:36,882: Target= 0W Speed=19.9kmh hr= 0 Current= 0W Cad= 77 r= 921 T= 0 0 0 09:47:37,932: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 76 r= 927 T= 0 0 0 09:47:38,972: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 75 r= 918 T= 0 0 0 09:47:40,007: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 74 r= 917 T= 0 0 0 09:47:41,094: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 73 r= 911 T= 0 0 0 09:47:42,279: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 72 r= 907 T= 0 0 0 09:47:43,409: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 71 r= 909 T= 0 0 0 09:47:44,581: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 70 r= 913 T= 0 0 0 09:47:45,622: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 69 r= 903 T= 0 0 0 09:47:46,672: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 68 r= 899 T= 0 0 0 09:47:47,701: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 67 r= 906 T= 0 0 0 09:47:48,751: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 66 r= 898 T= 0 0 0 09:47:49,788: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 65 r= 895 T= 0 0 0 09:47:50,822: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 64 r= 893 T= 0 0 0 09:47:51,872: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 63 r= 902 T= 0 0 0 09:47:52,912: Target= 0W Speed=19.9kmh hr= 0 Current= 0W Cad= 62 r= 891 T= 0 0 0 09:47:53,947: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 61 r= 897 T= 0 0 0 09:47:54,996: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 60 r= 885 T= 0 0 0 09:47:56,037: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 59 r= 891 T= 0 0 0 09:47:57,087: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 58 r= 896 T= 0 0 0 09:47:58,128: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 57 r= 889 T= 0 0 0 09:47:59,162: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 56 r= 882 T= 0 0 0 09:48:00,212: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 55 r= 882 T= 0 0 0 09:48:01,253: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 54 r= 883 T= 0 0 0 09:48:02,302: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 53 r= 884 T= 0 0 0 09:48:03,345: Target= 0W Speed=19.9kmh hr= 0 Current= 0W Cad= 52 r= 878 T= 0 0 0 09:48:04,395: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 51 r= 882 T= 0 0 0 09:48:05,436: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 50 r= 882 T= 0 0 0 09:48:06,470: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 49 r= 885 T= 0 0 0 09:48:07,520: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 48 r= 880 T= 0 0 0 09:48:08,560: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 47 r= 876 T= 0 0 0 09:48:09,610: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 46 r= 876 T= 0 0 0 09:48:10,651: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 45 r= 875 T= 0 0 0 09:48:11,685: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 44 r= 871 T= 0 0 0 09:48:12,735: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 43 r= 875 T= 0 0 0 09:48:13,776: Target= 0W Speed=20.1kmh hr= 0 Current= 0W Cad= 42 r= 867 T= 0 0 0 09:48:14,826: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 41 r= 867 T= 0 0 0 09:48:15,866: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 40 r= 871 T= 0 0 0 09:48:16,900: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 39 r= 870 T= 0 0 0 09:48:17,950: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 38 r= 867 T= 0 0 0 09:48:18,991: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 37 r= 863 T= 0 0 0 09:48:20,041: Target= 0W Speed=20.0kmh hr= 0 Current= 0W Cad= 36 r= 867 T= 0 0 0 09:48:20,558: Tacx - Connected to Tacx Trainer T1942 09:48:20,558: ---------- ANT-devices are activated ---------- 09:48:20,564: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [submit_async] submitting request failed, win error: The device does not recognize the command.\r\n' 09:48:20,580: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [submit_async] submitting request failed, win error: The device does not recognize the command.\r\n' 09:48:20,580: ANT Dongle not available; try to reconnect after 1 second 09:48:22,116: ANT Dongle reconnected, application restarts 09:48:22,232: Tacx2Dongle; Processing time 1.667 is 1.417 longer than planned 0.250 (seconds) 09:48:22,733: Dongle - Using CYCPLUS dongle 09:48:23,868: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:48:24,068: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:48:24,269: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:48:24,476: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:48:24,692: FortiusANT receives commands from an ANT+ Generic Remote Control 09:48:24,940: Ctrl-C to exit 09:48:24,940: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:48:24,940: Tacx - Connected to Tacx Trainer T1942 09:48:24,955: Target=100W Speed=20.0kmh hr= 0 Current= 0W Cad= 0 r=2221 T= 1 6 1 09:48:25,974: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:27,050: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:28,084: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:29,134: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:30,174: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:31,224: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:32,265: Target=100W Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:33,299: Target=2.5% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:34,349: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:35,390: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:36,440: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:37,480: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:38,515: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:39,564: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:40,605: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:41,176: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:48:42,093: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.\r\n\n' 09:48:42,093: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [submit_async] submitting request failed, win error: A device which does not exist was specified.\r\n' 09:48:42,093: ANT Dongle not available; try to reconnect after 1 second 09:48:43,936: ANT Dongle reconnected, application restarts 09:48:44,159: Tacx2Dongle; Processing time 3.554 is 3.304 longer than planned 0.250 (seconds) 09:48:44,668: Dongle - Using CYCPLUS dongle 09:48:45,819: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:48:46,019: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:48:46,220: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:48:46,436: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:48:46,637: FortiusANT receives commands from an ANT+ Generic Remote Control 09:48:46,891: Ctrl-C to exit 09:48:46,891: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:48:46,891: Tacx - Connected to Tacx Trainer T1942 09:48:46,906: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:47,940: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:48,981: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:50,015: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:51,065: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:52,106: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:53,156: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:54,196: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:55,231: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:56,280: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:57,321: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:58,371: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:48:59,412: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:00,446: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:01,496: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:02,753: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:49:03,123: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.\r\n\n' 09:49:03,138: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [submit_async] submitting request failed, win error: A device which does not exist was specified.\r\n' 09:49:03,138: ANT Dongle not available; try to reconnect after 1 second 09:49:04,166: ANT Dongle not available; try to reconnect after 1 second 09:49:05,943: ANT Dongle reconnected, application restarts 09:49:05,973: Tacx2Dongle; Processing time 3.954 is 3.704 longer than planned 0.250 (seconds) 09:49:06,493: Dongle - Using CYCPLUS dongle 09:49:07,882: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:49:08,166: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:49:08,450: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:49:08,854: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:49:09,055: FortiusANT receives commands from an ANT+ Generic Remote Control 09:49:09,302: Ctrl-C to exit 09:49:09,302: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:49:09,302: Tacx - Connected to Tacx Trainer T1942 09:49:09,324: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:10,343: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:11,377: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:12,427: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:13,468: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:14,517: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:15,558: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:16,592: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:17,655: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:19,154: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:49:19,197: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:49:19,199: ANT Dongle not available; try to reconnect after 1 second 09:49:20,224: ANT Dongle not available; try to reconnect after 1 second 09:49:22,095: ANT Dongle reconnected, application restarts 09:49:22,370: Tacx2Dongle; Processing time 4.182 is 3.932 longer than planned 0.250 (seconds) 09:49:22,873: Dongle - Using CYCPLUS dongle 09:49:24,007: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:49:24,208: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:49:24,409: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:49:24,609: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:49:24,810: FortiusANT receives commands from an ANT+ Generic Remote Control 09:49:25,079: Ctrl-C to exit 09:49:25,079: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:49:25,079: Tacx - Connected to Tacx Trainer T1942 09:49:25,095: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:26,129: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:27,170: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:28,204: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:29,254: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:30,295: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:31,345: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:32,385: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:33,420: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:34,469: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:35,581: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:36,618: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:37,652: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:38,703: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:39,690: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:49:39,706: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:49:39,712: ANT Dongle not available; try to reconnect after 1 second 09:49:41,908: ANT Dongle reconnected, application restarts 09:49:42,133: Tacx2Dongle; Processing time 3.430 is 3.180 longer than planned 0.250 (seconds) 09:49:42,639: Dongle - Using CYCPLUS dongle 09:49:43,776: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:49:43,976: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:49:44,199: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:49:44,400: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:49:44,600: FortiusANT receives commands from an ANT+ Generic Remote Control 09:49:44,832: Ctrl-C to exit 09:49:44,832: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:49:44,832: Tacx - Connected to Tacx Trainer T1942 09:49:44,848: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:45,882: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:46,923: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:47,972: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:49,013: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:50,047: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:51,097: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:52,138: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:53,188: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:54,228: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:55,263: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:56,312: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:57,353: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:58,403: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:49:59,444: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:00,478: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:01,450: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:01,465: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:01,465: ANT Dongle not available; try to reconnect after 1 second 09:50:03,435: ANT Dongle reconnected, application restarts 09:50:03,653: Tacx2Dongle; Processing time 3.175 is 2.925 longer than planned 0.250 (seconds) 09:50:04,173: Dongle - Using CYCPLUS dongle 09:50:05,343: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:50:05,544: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:50:05,744: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:50:05,945: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:50:06,145: FortiusANT receives commands from an ANT+ Generic Remote Control 09:50:06,377: Ctrl-C to exit 09:50:06,377: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:50:06,377: Tacx - Connected to Tacx Trainer T1942 09:50:06,399: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:07,418: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:08,452: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:09,502: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:10,543: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:11,593: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:12,633: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:13,668: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:14,717: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:15,805: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:16,850: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:17,884: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:19,035: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:19,050: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:19,057: ANT Dongle not available; try to reconnect after 1 second 09:50:20,083: ANT Dongle not available; try to reconnect after 1 second 09:50:21,714: ANT Dongle reconnected, application restarts 09:50:21,783: Tacx2Dongle; Processing time 3.636 is 3.386 longer than planned 0.250 (seconds) 09:50:22,294: Dongle - Using CYCPLUS dongle 09:50:23,669: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:50:23,870: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:50:24,070: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:50:24,271: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:50:24,472: FortiusANT receives commands from an ANT+ Generic Remote Control 09:50:24,710: Ctrl-C to exit 09:50:24,710: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:50:24,710: Tacx - Connected to Tacx Trainer T1942 09:50:24,726: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:25,744: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:26,794: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:27,835: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:28,885: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:29,925: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:30,960: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:32,009: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:33,050: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:34,100: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:35,141: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:36,175: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:37,225: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:38,112: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:38,127: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:38,127: ANT Dongle not available; try to reconnect after 1 second 09:50:39,137: ANT Dongle not available; try to reconnect after 1 second 09:50:41,258: ANT Dongle reconnected, application restarts 09:50:41,422: Tacx2Dongle; Processing time 4.197 is 3.947 longer than planned 0.250 (seconds) 09:50:41,924: Dongle - Using CYCPLUS dongle 09:50:43,043: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:50:43,243: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:50:43,460: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:50:43,660: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:50:43,861: FortiusANT receives commands from an ANT+ Generic Remote Control 09:50:44,099: Ctrl-C to exit 09:50:44,099: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:50:44,099: Tacx - Connected to Tacx Trainer T1942 09:50:44,115: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:45,149: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:46,189: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:47,236: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:48,286: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:49,327: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:50,361: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:51,411: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:52,452: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:53,502: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:54,542: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:55,576: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:56,633: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:50:56,965: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:58,009: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n' 09:50:58,009: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:50:58,009: ANT Dongle not available; try to reconnect after 1 second 09:50:59,916: ANT Dongle reconnected, application restarts 09:51:00,149: Tacx2Dongle; Processing time 3.516 is 3.266 longer than planned 0.250 (seconds) 09:51:00,665: Dongle - Using CYCPLUS dongle 09:51:01,799: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:51:02,000: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:51:02,254: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:51:02,454: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:51:02,655: FortiusANT receives commands from an ANT+ Generic Remote Control 09:51:02,887: Ctrl-C to exit 09:51:02,887: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:51:02,887: Tacx - Connected to Tacx Trainer T1942 09:51:02,902: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:03,937: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:04,977: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:06,027: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:07,068: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:08,118: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:09,152: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:10,193: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:11,242: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:12,283: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:13,317: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:14,367: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:15,408: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:16,458: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:17,499: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:19,003: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:51:19,003: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:51:19,003: ANT Dongle not available; try to reconnect after 1 second 09:51:20,237: ANT Dongle not available; try to reconnect after 1 second 09:51:22,208: ANT Dongle reconnected, application restarts 09:51:22,298: Tacx2Dongle; Processing time 4.282 is 4.032 longer than planned 0.250 (seconds) 09:51:22,817: Dongle - Using CYCPLUS dongle 09:51:24,010: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:51:24,211: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:51:24,427: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:51:24,628: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:51:24,844: FortiusANT receives commands from an ANT+ Generic Remote Control 09:51:25,082: Ctrl-C to exit 09:51:25,082: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:51:25,082: Tacx - Connected to Tacx Trainer T1942 09:51:25,098: Target=1.0% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:51:26,116: Target=1.0%(158W) Speed=24.4kmh hr= 0 Current= 17W Cad= 48 r=2876 T= 1 6 1 09:51:27,166: Target=0.0%(95W) Speed=23.6kmh hr= 0 Current= 48W Cad= 90 r=1792 T= 1 6 1 09:51:28,207: Target=0.0%(88W) Speed=22.9kmh hr= 0 Current= 60W Cad= 88 r=1706 T= 1 6 1 09:51:29,257: Target=0.0%(88W) Speed=22.9kmh hr= 0 Current=104W Cad= 83 r=1711 T= 1 6 1 09:51:30,298: Target=0.0%(94W) Speed=23.5kmh hr= 0 Current=116W Cad= 83 r=1775 T= 1 6 1 09:51:31,332: Target=0.0%(101W) Speed=24.2kmh hr= 0 Current=109W Cad= 84 r=1854 T= 1 6 1 09:51:32,382: Target=0.0%(103W) Speed=24.3kmh hr= 0 Current=114W Cad= 85 r=1886 T= 1 6 1 09:51:33,422: Target=0.0%(103W) Speed=24.3kmh hr= 0 Current=118W Cad= 86 r=1883 T= 1 6 1 09:51:34,472: Target=0.0%(96W) Speed=23.7kmh hr= 0 Current= 68W Cad= 85 r=1802 T= 1 6 1 09:51:35,608: Target=0.0%(98W) Speed=23.9kmh hr= 0 Current=129W Cad= 80 r=1824 T= 1 6 1 09:51:36,610: Target=0.0%(102W) Speed=24.2kmh hr= 0 Current=120W Cad= 81 r=1877 T= 1 6 1 09:51:37,650: Target=0.0%(103W) Speed=24.3kmh hr= 0 Current=127W Cad= 81 r=1888 T= 1 6 1 09:51:38,685: Target=0.0%(107W) Speed=24.7kmh hr= 0 Current=129W Cad= 82 r=1928 T= 1 6 1 09:51:39,734: Target=0.0%(115W) Speed=25.4kmh hr= 0 Current=121W Cad= 83 r=2017 T= 1 6 1 09:51:40,474: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:51:41,107: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.\r\n\n' 09:51:41,107: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [submit_async] submitting request failed, win error: A device which does not exist was specified.\r\n' 09:51:41,115: ANT Dongle not available; try to reconnect after 1 second 09:51:42,151: ANT Dongle not available; try to reconnect after 1 second 09:51:43,920: ANT Dongle reconnected, application restarts 09:51:43,950: Tacx2Dongle; Processing time 3.961 is 3.711 longer than planned 0.250 (seconds) 09:51:44,460: Dongle - Using CYCPLUS dongle 09:51:45,639: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:51:45,846: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:51:46,062: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:51:46,263: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:51:46,463: FortiusANT receives commands from an ANT+ Generic Remote Control 09:51:46,695: Ctrl-C to exit 09:51:46,711: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:51:46,711: Tacx - Connected to Tacx Trainer T1942 09:51:46,726: Target=0.0%(109W) Speed=24.9kmh hr= 0 Current=131W Cad= 83 r=1947 T= 1 6 1 09:51:47,745: Target=0.0%(118W) Speed=25.7kmh hr= 0 Current= 58W Cad= 84 r=2039 T= 1 6 1 09:51:48,786: Target=0.0%(121W) Speed=26.0kmh hr= 0 Current=132W Cad= 81 r=2072 T= 1 6 1 09:51:49,836: Target=0.0%(126W) Speed=26.4kmh hr= 0 Current=136W Cad= 81 r=2123 T= 1 6 1 09:51:50,876: Target=0.0%(129W) Speed=26.7kmh hr= 0 Current=135W Cad= 81 r=2148 T= 1 6 1 09:51:51,881: Target=0.0%(133W) Speed=27.1kmh hr= 0 Current=140W Cad= 82 r=2186 T= 1 6 1 09:51:53,003: Target=-0.0%(124W) Speed=26.4kmh hr= 0 Current=145W Cad= 83 r=2090 T= 1 6 1 09:51:54,030: Target=-0.0%(124W) Speed=26.4kmh hr= 0 Current=136W Cad= 83 r=2090 T= 1 6 1 09:51:55,075: Target=-0.0%(126W) Speed=26.6kmh hr= 0 Current=142W Cad= 83 r=2104 T= 1 6 1 09:51:56,110: Target=-0.0%(130W) Speed=26.9kmh hr= 0 Current=149W Cad= 83 r=2149 T= 1 6 1 09:51:57,159: Target=-0.0%(133W) Speed=27.1kmh hr= 0 Current=135W Cad= 83 r=2183 T= 1 6 1 09:51:58,200: Target=-0.0%(135W) Speed=27.3kmh hr= 0 Current=129W Cad= 84 r=2197 T= 1 6 1 09:51:59,335: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:51:59,350: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:51:59,350: ANT Dongle not available; try to reconnect after 1 second 09:52:01,449: ANT Dongle reconnected, application restarts 09:52:01,656: Tacx2Dongle; Processing time 3.193 is 2.943 longer than planned 0.250 (seconds) 09:52:02,184: Dongle - Using CYCPLUS dongle 09:52:03,354: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:52:03,555: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:52:03,777: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:52:03,993: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:52:04,194: FortiusANT receives commands from an ANT+ Generic Remote Control 09:52:04,457: Ctrl-C to exit 09:52:04,464: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:52:04,464: Tacx - Connected to Tacx Trainer T1942 09:52:04,479: Target=-0.0%(130W) Speed=26.9kmh hr= 0 Current=140W Cad= 83 r=2153 T= 1 6 1 09:52:05,498: Target=-0.0%(166W) Speed=29.5kmh hr= 0 Current= 32W Cad= 82 r=2499 T= 1 6 1 09:52:06,548: Target=-0.0%(158W) Speed=29.0kmh hr= 0 Current= 86W Cad= 91 r=2423 T= 1 6 1 09:52:07,535: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:07,551: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:07,551: ANT Dongle not available; try to reconnect after 1 second 09:52:09,890: ANT Dongle reconnected, application restarts 09:52:10,080: Tacx2Dongle; Processing time 3.532 is 3.282 longer than planned 0.250 (seconds) 09:52:10,597: Dongle - Using CYCPLUS dongle 09:52:11,756: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:52:11,972: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:52:12,188: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:52:12,389: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:52:12,589: FortiusANT receives commands from an ANT+ Generic Remote Control 09:52:12,837: Ctrl-C to exit 09:52:12,843: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:52:12,843: Tacx - Connected to Tacx Trainer T1942 09:52:12,859: Target=-0.0%(163W) Speed=29.3kmh hr= 0 Current= 87W Cad= 91 r=2475 T= 1 6 1 09:52:13,893: Target=-0.0%(167W) Speed=29.6kmh hr= 0 Current= 65W Cad= 85 r=2505 T= 1 6 1 09:52:14,943: Target=-0.0%(164W) Speed=29.4kmh hr= 0 Current=130W Cad= 85 r=2480 T= 1 6 1 09:52:15,984: Target=-0.0%(161W) Speed=29.2kmh hr= 0 Current=157W Cad= 84 r=2452 T= 1 6 1 09:52:17,034: Target=-0.0%(164W) Speed=29.4kmh hr= 0 Current=168W Cad= 84 r=2483 T= 1 6 1 09:52:18,074: Target=-0.0%(163W) Speed=29.3kmh hr= 0 Current=168W Cad= 84 r=2472 T= 1 6 1 09:52:19,109: Target=-0.0%(165W) Speed=29.4kmh hr= 0 Current=161W Cad= 84 r=2498 T= 1 6 1 09:52:20,158: Target=-0.0%(171W) Speed=29.8kmh hr= 0 Current=159W Cad= 84 r=2554 T= 1 6 1 09:52:21,199: Target=-0.0%(176W) Speed=30.1kmh hr= 0 Current=164W Cad= 84 r=2604 T= 1 6 1 09:52:22,249: Target=-0.0%(170W) Speed=29.7kmh hr= 0 Current=155W Cad= 84 r=2546 T= 1 6 1 09:52:23,290: Target=-0.0%(168W) Speed=29.6kmh hr= 0 Current=161W Cad= 84 r=2524 T= 1 6 1 09:52:24,324: Target=-0.0%(161W) Speed=29.2kmh hr= 0 Current=168W Cad= 84 r=2453 T= 1 6 1 09:52:25,374: Target=-0.1%(160W) Speed=29.3kmh hr= 0 Current=183W Cad= 85 r=2425 T= 1 6 1 09:52:26,415: Target=-0.1%(161W) Speed=29.4kmh hr= 0 Current=177W Cad= 85 r=2439 T= 1 6 1 09:52:27,464: Target=-0.1%(161W) Speed=29.4kmh hr= 0 Current=178W Cad= 85 r=2431 T= 1 6 1 09:52:28,505: Target=-0.1%(162W) Speed=29.5kmh hr= 0 Current=174W Cad= 85 r=2442 T= 1 6 1 09:52:29,455: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:29,470: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:29,470: ANT Dongle not available; try to reconnect after 1 second 09:52:32,072: ANT Dongle reconnected, application restarts 09:52:32,565: Tacx2Dongle; Processing time 4.060 is 3.810 longer than planned 0.250 (seconds) 09:52:33,080: Dongle - Using CYCPLUS dongle 09:52:34,222: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:52:34,438: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:52:34,638: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:52:34,839: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:52:35,062: FortiusANT receives commands from an ANT+ Generic Remote Control 09:52:35,325: Ctrl-C to exit 09:52:35,325: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:52:35,325: Tacx - Connected to Tacx Trainer T1942 09:52:35,347: Target=-0.1%(170W) Speed=30.0kmh hr= 0 Current=158W Cad= 85 r=2523 T= 1 6 1 09:52:36,366: Target=-0.0%(234W) Speed=33.5kmh hr= 0 Current= 32W Cad= 84 r=3106 T= 1 6 1 09:52:37,443: Target=-0.0%(220W) Speed=32.7kmh hr= 0 Current= 90W Cad= 94 r=2993 T= 1 6 1 09:52:38,474: Target=0.0%(215W) Speed=32.3kmh hr= 0 Current= 63W Cad= 93 r=2963 T= 1 6 1 09:52:39,525: Target=0.1%(201W) Speed=31.3kmh hr= 0 Current=118W Cad= 82 r=2859 T= 1 6 1 09:52:40,606: Target=0.1%(198W) Speed=30.9kmh hr= 0 Current=162W Cad= 82 r=2845 T= 1 6 1 09:52:41,624: Target=0.2%(197W) Speed=30.6kmh hr= 0 Current=188W Cad= 81 r=2867 T= 1 6 1 09:52:42,676: Target=0.2%(198W) Speed=30.7kmh hr= 0 Current=191W Cad= 81 r=2869 T= 1 6 1 09:52:43,704: Target=0.3%(206W) Speed=30.6kmh hr= 0 Current=176W Cad= 80 r=2998 T= 1 6 1 09:52:44,745: Target=0.4%(211W) Speed=30.6kmh hr= 0 Current=158W Cad= 80 r=3066 T= 1 6 1 09:52:45,795: Target=0.5%(204W) Speed=29.9kmh hr= 0 Current=179W Cad= 80 r=3032 T= 1 6 1 09:52:46,835: Target=0.5%(213W) Speed=30.1kmh hr= 0 Current=193W Cad= 79 r=3151 T= 1 6 1 09:52:47,885: Target=0.5%(220W) Speed=30.5kmh hr= 0 Current=191W Cad= 79 r=3212 T= 1 6 1 09:52:48,957: Target=0.6%(218W) Speed=29.9kmh hr= 0 Current=193W Cad= 79 r=3242 T= 1 6 1 09:52:50,430: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:50,446: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:50,446: ANT Dongle not available; try to reconnect after 1 second 09:52:52,481: ANT Dongle reconnected, application restarts 09:52:52,703: Tacx2Dongle; Processing time 3.229 is 2.979 longer than planned 0.250 (seconds) 09:52:53,282: Dongle - Using CYCPLUS dongle 09:52:54,479: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:52:54,696: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:52:54,896: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:52:55,097: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:52:55,297: FortiusANT receives commands from an ANT+ Generic Remote Control 09:52:55,529: Ctrl-C to exit 09:52:55,529: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:52:55,529: Tacx - Connected to Tacx Trainer T1942 09:52:55,551: Target=0.6%(221W) Speed=30.1kmh hr= 0 Current=192W Cad= 79 r=3262 T= 1 6 1 09:52:56,686: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:56,686: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:52:56,686: ANT Dongle not available; try to reconnect after 1 second 09:52:58,425: ANT Dongle reconnected, application restarts 09:52:58,535: Tacx2Dongle; Processing time 2.752 is 2.502 longer than planned 0.250 (seconds) 09:52:59,092: Dongle - Using CYCPLUS dongle 09:53:00,287: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:53:00,488: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:53:00,704: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:53:00,927: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:53:01,128: FortiusANT receives commands from an ANT+ Generic Remote Control 09:53:01,359: Ctrl-C to exit 09:53:01,359: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:53:01,359: Tacx - Connected to Tacx Trainer T1942 09:53:01,375: Target=0.6%(196W) Speed=28.6kmh hr= 0 Current=190W Cad= 82 r=3048 T= 1 6 1 09:53:02,409: Target=1.1%(301W) Speed=32.7kmh hr= 0 Current= 53W Cad= 84 r=4088 T= 1 6 1 09:53:03,450: Target=1.1%(296W) Speed=32.4kmh hr= 0 Current= 91W Cad= 93 r=4066 T= 1 6 1 09:53:04,500: Target=1.1%(271W) Speed=31.1kmh hr= 0 Current=100W Cad= 89 r=3872 T= 1 6 1 09:53:05,541: Target=1.1%(258W) Speed=30.3kmh hr= 0 Current=127W Cad= 86 r=3791 T= 1 6 1 09:53:06,575: Target=1.1%(246W) Speed=29.6kmh hr= 0 Current=139W Cad= 85 r=3693 T= 1 6 1 09:53:07,631: Target=1.1%(232W) Speed=28.8kmh hr= 0 Current=129W Cad= 83 r=3588 T= 1 6 1 09:53:08,665: Target=1.2%(217W) Speed=27.8kmh hr= 0 Current=157W Cad= 81 r=3469 T= 1 6 1 09:53:09,731: Target=1.2%(216W) Speed=27.7kmh hr= 0 Current=171W Cad= 80 r=3467 T= 1 6 1 09:53:10,772: Target=1.2%(207W) Speed=27.0kmh hr= 0 Current=165W Cad= 78 r=3410 T= 1 6 1 09:53:11,821: Target=1.2%(213W) Speed=27.3kmh hr= 0 Current=171W Cad= 78 r=3466 T= 1 6 1 09:53:12,862: Target=1.3%(211W) Speed=26.9kmh hr= 0 Current=216W Cad= 78 r=3485 T= 1 6 1 09:53:13,896: Target=1.4%(218W) Speed=27.0kmh hr= 0 Current=235W Cad= 78 r=3592 T= 1 6 1 09:53:14,946: Target=1.5%(239W) Speed=27.9kmh hr= 0 Current=214W Cad= 78 r=3810 T= 1 6 1 09:53:15,987: Target=1.6%(231W) Speed=26.9kmh hr= 0 Current=224W Cad= 78 r=3812 T= 1 6 1 09:53:16,958: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:53:17,992: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n' 09:53:17,992: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:53:17,992: ANT Dongle not available; try to reconnect after 1 second 09:53:20,120: ANT Dongle reconnected, application restarts 09:53:20,262: Tacx2Dongle; Processing time 4.012 is 3.762 longer than planned 0.250 (seconds) 09:53:20,770: Dongle - Using CYCPLUS dongle 09:53:21,911: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:53:22,127: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:53:22,344: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:53:22,544: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:53:22,872: FortiusANT receives commands from an ANT+ Generic Remote Control 09:53:23,245: Ctrl-C to exit 09:53:23,247: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:53:23,257: Tacx - Connected to Tacx Trainer T1942 09:53:23,278: Target=1.6%(246W) Speed=27.8kmh hr= 0 Current=223W Cad= 78 r=3941 T= 1 6 1 09:53:24,533: Target=1.6%(378W) Speed=34.4kmh hr= 0 Current= 19W Cad= 76 r=4892 T= 1 6 1 09:53:25,655: Target=1.6%(337W) Speed=32.6kmh hr= 0 Current=100W Cad= 97 r=4594 T= 1 6 1 09:53:26,725: Target=1.5%(308W) Speed=31.4kmh hr= 0 Current=104W Cad= 91 r=4359 T= 1 6 1 09:53:27,760: Target=1.5%(278W) Speed=29.9kmh hr= 0 Current=129W Cad= 88 r=4141 T= 1 6 1 09:53:28,801: Target=1.5%(260W) Speed=29.0kmh hr= 0 Current=165W Cad= 85 r=3985 T= 1 6 1 09:53:29,851: Target=1.5%(253W) Speed=28.6kmh hr= 0 Current=183W Cad= 83 r=3936 T= 1 6 1 09:53:30,891: Target=1.5%(239W) Speed=27.8kmh hr= 0 Current=198W Cad= 81 r=3826 T= 1 6 1 09:53:31,926: Target=1.5%(248W) Speed=28.4kmh hr= 0 Current=189W Cad= 81 r=3881 T= 1 6 1 09:53:32,975: Target=1.5%(235W) Speed=27.6kmh hr= 0 Current=190W Cad= 80 r=3780 T= 1 6 1 09:53:34,016: Target=1.5%(227W) Speed=27.2kmh hr= 0 Current=236W Cad= 79 r=3710 T= 1 6 1 09:53:35,066: Target=1.5%(229W) Speed=27.3kmh hr= 0 Current=218W Cad= 79 r=3733 T= 1 6 1 09:53:36,115: Target=1.4%(241W) Speed=28.1kmh hr= 0 Current=208W Cad= 79 r=3808 T= 1 6 1 09:53:37,139: Target=1.4%(224W) Speed=27.1kmh hr= 0 Current=222W Cad= 79 r=3677 T= 1 6 1 09:53:37,937: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:53:38,990: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] timeout error\n' 09:53:38,998: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:53:39,000: ANT Dongle not available; try to reconnect after 1 second 09:53:41,183: ANT Dongle reconnected, application restarts 09:53:41,244: Tacx2Dongle; Processing time 4.206 is 3.956 longer than planned 0.250 (seconds) 09:53:41,763: Dongle - Using CYCPLUS dongle 09:53:42,912: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:53:43,112: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:53:43,328: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:53:43,545: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:53:43,745: FortiusANT receives commands from an ANT+ Generic Remote Control 09:53:43,984: Ctrl-C to exit 09:53:43,984: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:53:43,984: Tacx - Connected to Tacx Trainer T1942 09:53:43,999: Target=1.4%(239W) Speed=28.0kmh hr= 0 Current=220W Cad= 79 r=3792 T= 1 6 1 09:53:45,033: Target=1.3%(351W) Speed=34.0kmh hr= 0 Current= 37W Cad= 77 r=4590 T= 1 6 1 09:53:46,074: Target=1.3%(320W) Speed=32.7kmh hr= 0 Current=133W Cad= 95 r=4346 T= 1 6 1 09:53:47,108: Target=1.3%(298W) Speed=31.7kmh hr= 0 Current=178W Cad= 93 r=4183 T= 1 6 1 09:53:48,158: Target=1.3%(287W) Speed=31.2kmh hr= 0 Current=167W Cad= 90 r=4092 T= 1 6 1 09:53:49,199: Target=1.2%(265W) Speed=30.2kmh hr= 0 Current=113W Cad= 89 r=3908 T= 1 6 1 09:53:50,249: Target=1.2%(229W) Speed=28.3kmh hr= 0 Current= 24W Cad= 89 r=3600 T= 1 6 1 09:53:51,290: Target=1.2%(201W) Speed=26.7kmh hr= 0 Current= 10W Cad= 89 r=3350 T= 1 6 1 09:53:52,324: Target=1.1%(177W) Speed=25.3kmh hr= 0 Current= 11W Cad= 0 r=3116 T= 1 6 1 09:53:53,374: Target=1.1%(154W) Speed=23.8kmh hr= 0 Current= 12W Cad= 0 r=2874 T= 1 6 1 09:53:54,414: Target=1.0%(137W) Speed=22.7kmh hr= 0 Current= 13W Cad= 0 r=2679 T= 1 6 1 09:53:55,464: Target=0.9%(121W) Speed=21.6kmh hr= 0 Current= 13W Cad= 0 r=2494 T= 1 6 1 09:53:56,505: Target=0.8%(59W) Speed=14.9kmh hr= 0 Current= 9W Cad= 0 r=1760 T= 1 6 1 09:53:57,539: Target=0.8% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:53:58,589: Target=0.5% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:53:59,630: Target=0.4% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:54:00,601: AntDongle.Write exception (message lost): [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:54:00,601: devAntDongle.read exception: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning.\r\n\n' 09:54:00,617: ANT Dongle not available; try to reconnect after 1 second 09:54:03,457: ANT Dongle reconnected, application restarts 09:54:03,863: Tacx2Dongle; Processing time 4.233 is 3.983 longer than planned 0.250 (seconds) 09:54:04,411: Dongle - Using CYCPLUS dongle 09:54:05,638: FortiusANT broadcasts data as an ANT+ Controlled Fitness Equipent device (FE-C), id=57591 09:54:06,544: FortiusANT broadcasts data as an ANT+ Heart Rate Monitor (HRM), id=57592 09:54:06,745: FortiusANT broadcasts data as an ANT+ Bicycle Power Sensor (PWR), id=57596 09:54:06,961: FortiusANT broadcasts data as an ANT+ Speed and Cadence Sensor (SCS), id=57595 09:54:07,162: FortiusANT receives commands from an ANT+ Generic Remote Control 09:54:07,400: Ctrl-C to exit 09:54:07,400: Tacx - G I V E A P E D A L K I C K T O S T A R T C A L I B R A T I O N 09:54:07,400: Tacx - Connected to Tacx Trainer T1942 09:54:07,416: Target=0.4% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1 09:54:08,450: Target=0.4% Speed= 0.0kmh hr= 0 Current= 0W Cad= 0 r= 0 T= 1 6 1

WouterJD commented 3 years ago

09:53:41,763: Dongle - Using CYCPLUS dongle

Please refer to #61 CYCPLUS is always problematic

yancart commented 3 years ago

Hi I thought my CYCPLUS might have been ok as it bought well over a yr ago but maybe not? Ok will tray and find smthg else on UK ebay. Thanks

yancart commented 3 years ago

Trouble is most USB Ant+ on Ebay now are CYCPLUS/ANSELF....

MeanHat commented 3 years ago

Hi I thought my CYCPLUS might have been ok as it bought well over a yr ago but maybe not? Ok will tray and find smthg else on UK ebay. Thanks

@yancart - This one (Dynastream) from Wiggle UK works OK : https://www.wiggle.co.uk/lifeline-ant-usb

yancart commented 3 years ago

Thanks for that although will need two and that will be £30 each, pity there is nothing cheaper on Ebay..

WouterJD commented 3 years ago

BLE is cheaper. For this money you can consider to by a Raspberry. Raspberry is in last test-cycles and fully supported.

WouterJD / FortiusANT

Problem connecting Fortius T1942 to FortiusAnt #256