Support iFlow 1932 on Mac OS? about fortiusant HOT 145 CLOSED

@M4M4R2

Don't use the requirements.txt, try installing the things within one by one, e.g.

python3 -mpip install keyboard
python3 -mpip install pyusb
python3 -mpip install pygame
python3 -mpip install pynput
python3 -mpip install wxPython
python3 -mpip install wheel

Note you probably don't need all of these (some will already by installed), I think I only needed the following:

python3 -mpip install pyusb
python3 -mpip install wxPython

FYI I don't need the space between -m and pip

from fortiusant.

Get brew if you don't have it already: https://brew.sh/

Then run: brew install libusb

from fortiusant.

1x: manufacturer=Suunto, product=Movestick mini, vendor= 0xfcf, product=0x1008(4104)
2x: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)

I have modified logfile.py and antDongle.py to have better logging on .write() and .read().
Hope this helps

ExplorANT.2020-04-15 06-57-12.log
FortiusANT.2020-04-15 06-56-24.log

from fortiusant.

Hi Ian, welcome in the FortiusANT community!

I think FortiusANT will run on Mac and I willl help you in case there are issues, even adjust code if needed.

1. Install python 3
2. Download the code
3. Run the code and see where we get

What Tacx do you have?

from fortiusant.

Hey - awesome thanks.

I have a i-Flow with a T1932 Head unit. I was setting up after many years put away and found out the tacx software has been discontinued and mine doesn't work with the desktop app.

So I have x2 ANT+ sticks which arrived so trying to get this set up (ideally with Zwift)

I'll install python 3 and see how I go - not used Python before, it's the FortiusAnt.py I need to run once downloaded correct?

Huge thanks in advance!

from fortiusant.

Indeed, read wiki for instructions
Succes!

from fortiusant.

Hey!

So got the app working, it tries to calibrate, and I see this error message a few times in the terminal:

18:40:13,839: ReadFromDongle read error: [Errno 60] Operation timed out

And then the error it stops. I see all the dials as if it is sending/receiving.

Is calibration meant to automatically turn the trainer wheel to 20km p/hr? Been so long since I've used it couldn't remember if that was possible?

from fortiusant.

Also - if I start without calibrating I get the same error repeatedly (it doesn't stop)

18:40:13,839: ReadFromDongle read error: [Errno 60] Operation timed out

from fortiusant.

There someone else with an i-Flow/1932 and it seems that calibration does not work
Use the -n flag (no calibration) and see what happens

from fortiusant.

Yes if I start without calibrating I get the same error repeatedly (it doesn't stop)

18:40:13,839: ReadFromDongle read error: [Errno 60] Operation timed out

from fortiusant.

run with -d8 flag and send logfile please

from fortiusant.

Sure thing! I noticed someone had a similar issue on mac with antifier but no solution was every posted.

FortiusANT.2020-04-10 21-06-08.log

from fortiusant.

I have checked the logfile:

From 21:06:09 ... 21:06:11 message "[Errno 60] Operation timed out"
Then commands are sent (you probably pressed Start)
From 21:06:11 ... 21:06:33 als message "[Errno 60] Operation timed out"

But then it appears normal operation; FortiusANT sends command and receives an answer.
From 21:06:33 ... 21:06:53

Note that it is all within a minute.

Some questions:

1. Do the messages continue to appear?
2. What happens if you start cycling
3. Could it be that your system needs some time to start?

Sorry that I cannot check myself...please try ans see what happens!
Succes

PS. There is another user with an iFlow 1932. So .... fair chance it can work

from fortiusant.

1. Do the messages continue to appear? - Yes, repeatedly
2. What happens if you start cycling - within the app open I see the speed and power dials (I have a cadence too but not connected)
3. Could it be that your system needs some time to start? - Not sure what you mean?

I have x2 ANT+ dongles plugged into the mac, along with the USB from the trainer.

If I have only 1 ANT+ dongle connected, I receive the same message repeatedly.

from fortiusant.

The provided logfile shows that the messages stop (see my message from yesterday)
3. It may be that yoour Tacx needs some time to start and that messages disappear later-on

Provide logfile over more time than just one minute, please. Let's say 10 minutes at least.

from fortiusant.

I can see the speed etc immediately when I start pedaling, so the trainer sending the data doesn't seem to be the issue.

10min log file attached - the previous one was a minute because I only ran it for a minute (as it's just repeating over and over) - it just repeats, to end I clck stop (the errors still come through and the close the app and it exist in the terminal.

Thanks!

FortiusANT.2020-04-12 11-34-58.log

from fortiusant.

Sorry * 100

ReadFromDongle has nothing to do with the Tacx trainer, but is generated at the ANT usbDongle side. (As the error message says).

Check in antDongle.py

    except Exception as e:
        if "timeout error" in str(e):
            if debug.on(debug.Data1):
                logfile.Write ("Dongle    timeout")
            pass
        else:
            logfile.Write ("ReadFromDongle read error: " + str(e))

The code expects "timeout error" in the error-message, but (on your system) the message is "ReadFromDongle read error: [Errno 60] Operation timed out" and hence the error is given and not ignored as it should be. Note that the exception handling does not alter any data but only logs the error message.

You may simple ignore the message or replace "timeout error" with "timeout" and see what happens; behaviour should be the same in both cases.

I do not like this construction (checking text in message) and will check how to improve.

Please let me know...

from fortiusant.

The correct code would be:
except TimeoutError:
pass
except Exception as e:
logfile.Write ("ReadFromDongle read error: " + str(e))

If you don't mind checking that, then it's confirmed on your platform and I will implement in the baseline. Thanks

from fortiusant.

So replacing this:

except Exception as e:
        if "timeout error" in str(e):
            if debug.on(debug.Data1):
                logfile.Write ("Dongle    timeout")
            pass
        else:
            logfile.Write ("ReadFromDongle read error: " + str(e))

with:

except TimeoutError:
      pass
    except Exception as e:
      logfile.Write ("ReadFromDongle read error: " + str(e))

Still gives me:

13:06:22,863: ReadFromDongle read error: [Errno 60] Operation timed out

Repeated.

I also open Zwift with the app running, I can connect via Power Source and ANT+, but it receives no data (e.g. I start peddling but don't move or see any power). In the app I still see Power and Speed - but this is coming via the USB presumably.

from fortiusant.

If I change to this:

except Exception as e:
        if "timed out" in str(e):
            if debug.on(debug.Data1):
                logfile.Write ("Dongle    timeout")
            pass
        else:
            logfile.Write ("ReadFromDongle read error: " + str(e))

And just check against 'timed out' then the error goes, but I'm still not receiving any data in Swift - no power etc. So it is like the receiving ANT+ dongle is not receiving the data?

from fortiusant.

OK, you're doing good.

Please run FortiusANT with -d4 this will provide the ANT logging.
Sorry for keeping you budy on this sunny easter day :-)

https://github.com/WouterJD/FortiusANT/wiki#values

from fortiusant.

Okay cool - attached is the log file (kept on for 10mins).

No worries - thanks for helping me with this!

FortiusANT.2020-04-12 13-54-21.log

from fortiusant.

OK logfile looks good, but indeed - no commands are received from Zwift.

Did you pair Zwift with FortiusANT?
Note that a master (the trainer, FortiusANT) is unaware whether a slave (Zwift, ...) is looking at or pairing [with the master]..

Please send screen-shot of pairing-page, something like:

from fortiusant.

Okay great.

So here is what I am doing - just listing in case I'm missing something:

1. Plugging in the USB from my trainer
2. Plugging in both ANT+ dongles
3. Running the FortiusANT app (skipping calibration)
4. Opening Zwift

Here is what I see in Zwift:

(This is the only available device)

from fortiusant.

Checking the screen-print from FortiusANT (Trainer detected, Using Dynastream...) the hardware is found correctly and I would expect things to work. The logfile shows that data is transmitted.

What happens when you press SEARCH on cadence and controllable?
Both should should be paired with FortiusANT.

from fortiusant.

No nothing - I just get the searching screen..

Do I need to do anything to the ANT+ dongles? I read about having master/slave etc?

from fortiusant.

For some reason the Heart Rate one picks up an ANT+ device and connects, but not Cadence or Controllable. Power Source connects but receives not data

from fortiusant.

Also, if I simulate (with -s) I get the same results

from fortiusant.

No nothing - I just get the searching screen..

Do I need to do anything to the ANT+ dongles? I read about having master/slave etc?

master/slave is decided by software; a trainer is master, Zwift is slave

from fortiusant.

Also, if I simulate (with -s) I get the same results

-s simulates a trainer, this comes handy in this case - you do not need to cycle to test Zwift.
Good idea to use it

from fortiusant.

For some reason the Heart Rate one picks up an ANT+ device and connects, but not Cadence or Controllable. Power Source connects but receives not data

What is the deviceID of the heart rate monitor?

from fortiusant.

So it's simulating now:

And I can only connect via ANT+ to a power source and HRM in Zwift:

HRM ID:

from fortiusant.

But no watts or BPM received either

from fortiusant.

plse read #42

It sounds like similar and that case was never explained. It seems another dongle solved the problem. Anyway: FortiusANT was not changed to resolve...

What dongles / configuration do you use?
Where do you run Zwift?
Perhaps try Trainer Road or Rouvy

I have confidence it will work

from fortiusant.

It does seem to be something with Zwift now - I will try Rouvy tomorrow and let you know.

Thank you so much for all your help!

from fortiusant.

👍

from fortiusant.

So in Rouvy I get the same, when searching for a trainer I see only a HRM :(

I had to try on my phone because ANT+ is not supported on mac by Rouvy. But it seems that it's not just Zwift.

Here is what I get in ExplorAnt.py:

06:29:28,501: ExplorANT started
06:29:28,502: --------------------
06:29:28,502: Dongles in the system:
06:29:28,514: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
06:29:28,515: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
06:29:28,516: manufacturer=GenesysLogic, product=     USB2.1 Hub, vendor= 0x5e3, product= 0x610(1552)
06:29:28,516: manufacturer=Realtek, product=USB 10/100/1000 LAN, vendor= 0xbda, product=0x8153(33107)
06:29:28,517: manufacturer=GenesysLogic, product=     USB3.1 Hub, vendor= 0x5e3, product= 0x626(1574)
06:29:28,519: manufacturer=Apple Inc., product=Apple Internal Keyboard / Trackpad, vendor= 0x5ac, product= 0x340(832)
06:29:28,520: manufacturer=  Apple, product=           None, vendor= 0x5ac, product=0x8104(33028)
06:29:28,520: --------------------
06:29:29,060: Using Dynastream Innovations dongle
06:29:31,157: Pairing, press Ctrl-C to exit
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
06:29:41,268: Pairing stopped
06:29:41,269: --------------------
06:29:42,609: Listening, press Ctrl-C to exit
06:29:43,628: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:44,646: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:45,658: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:46,678: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:47,693: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:48,701: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:49,719: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:50,731: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:51,750: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:52,762: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
06:29:53,777: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1

Does this look right?

My set up is:

Macbook Pro 2019
x2 ANT+ Dongles
Tacx iFlow w/ 1932 Head Unit

from fortiusant.

Is FortiusANT running at the same time?

from fortiusant.

No that was just running ExplorAnt.py

So when running python3 FortiusAnt.py -g -a -n -s and then running ExplorAnt.py I get:

07:31:16,155: ExplorANT started
07:31:16,155: --------------------
07:31:16,155: Dongles in the system:
07:31:16,170: manufacturer=Realtek, product=USB 10/100/1000 LAN, vendor= 0xbda, product=0x8153(33107)
07:31:16,171: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
07:31:16,172: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
07:31:16,173: manufacturer=GenesysLogic, product=     USB2.1 Hub, vendor= 0x5e3, product= 0x610(1552)
07:31:16,174: manufacturer=GenesysLogic, product=     USB3.1 Hub, vendor= 0x5e3, product= 0x626(1574)
07:31:16,175: manufacturer=Apple Inc., product=Apple Internal Keyboard / Trackpad, vendor= 0x5ac, product= 0x340(832)
07:31:16,177: manufacturer=  Apple, product=           None, vendor= 0x5ac, product=0x8104(33028)
07:31:16,178: --------------------
Exception: [Errno 19] No such device (it may have been disconnected)
07:31:16,187: GetDongle: [Errno 19] No such device (it may have been disconnected)
07:31:16,187: We're done
07:31:16,187: --------------------

from fortiusant.

ExplorANT "listens" on the ANT-network and shows what master-devices broadcast data.

There are two dongles; one used by FortiusANT and the second by ExplorANT.
No other programs should be running, because then no dongle is free.

If problem persists, run ExplorANT with -d5 flag and send logfile.

from fortiusant.

Here is the log file:

ExplorANT.2020-04-13 07-48-23.log

from fortiusant.

For some reason, the dongle cannot be used (that's what the message says).
Since 2020-03-09 multiple dongles of the same type should be supported; before always the first dongle was taken, which would be in use by FortiusANT.

To get more info in the logfile, run ExplorANT -d7 so that functions are also logged.

from fortiusant.

Hi guys!
I'm happy to see some of you are managing to do what i've been trying to for month if not years!
Ok, i've been trying to install Antifier on my Raspberry pi 1 and it unfortunately didn't work properly as the ANT dongle could not be detected for some reason... Now I discover your work and I really find it great! Much like iainhay I'm a mac user very naive on programming with Python. I downloaded the Python code for FortiusANT but when running the module it says "ModuleNotFoundError: No module named 'numpy'". Would you please describe the installation process you used on mac???
THX

from fortiusant.

Just to be sure, I ran a FortiusANT -g -a -s test on Windows 10, without the Tacx trainer so using simulation mode.

Then ExplorAnt.py -d1; minimum logfile which produces the following result, which is as expected and immediatly shows what output is expected:
The dongle is initiated
Then a listening loop is done to check what devices are present (pairing) and HRM and FE is found. 57592 is the deviceID of the HRM like what Zwift shows you.
And then a listening loop is done to listen what the masters say and correct HRM- and FE-values are received.

13:17:11,894: ExplorANT started
13:17:11,894: -d 1 (0b1)
13:17:11,894: -D -1 (-0x1)
13:17:11,894: -H -1 (-0x1)
13:17:11,894: -F -1 (-0x1)
13:17:11,894: --------------------
13:17:11,894: Dongles in the system:
13:17:11,957: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)
13:17:11,957: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)
13:17:11,957: --------------------
13:17:12,499: Using Dynastream Innovations dongle
13:17:14,594: Pairing, press Ctrl-C to exit
13:17:24,784: Pairing stopped
13:17:24,784: HRM discovered on channel=0, number=57592 typeID=120 TrType=120
13:17:24,785: FE discovered on channel=1, number=57591 typeID= 17 TrType= 17
13:17:24,785: --------------------
13:17:26,307: HRM slave channel 5 opened; listening to device 57592
13:17:26,495: FE slave channel 4 opened; listening to device 57591
13:17:26,495: Listening, press Ctrl-C to exit
13:17:27,503: HRM#= 4 hr= 90 FE-C#= 3 Speed=35.7 Cadence=100 Power= 98 hr= 86
13:17:28,508: HRM#= 8 hr= 87 FE-C#= 7 Speed=35.7 Cadence=102 Power=103 hr= 87
13:17:29,384: Listening stopped
13:17:29,953: We're done
13:17:29,953: --------------------

ExplorAnt.py -d3; produces the following additional result:

...
13:21:50,994: GetDongle - Check for dongle 4100 Older
13:21:50,994: GetDongle - Check for dongle 4105 Garmin
13:21:51,010: GetDongle - Dongle found: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)
13:21:51,010: GetDongle - Send reset string to dongle
13:21:51,010: GetDongle - Dongle found: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)
13:21:51,010: GetDongle - Send reset string to dongle
13:21:51,512: GetDongle - Read answer
13:21:51,547: ReadFromDongle() returns: ["a4 01 6f 00 ca"]
13:21:51,547: GetDongle - Check for an ANT+ reply
13:21:51,547: GetDongle() returns: Using Dynastream Innovations dongle
13:21:51,547: Using Dynastream Innovations dongle
...

The software uses usb.core.find() which returns two dongles with type 4105; the first one gives an error on the "Send reset string" (because it's in use by FortiusANT), on the second device the "Send reset string" goes well, an answer is received and the software proceeds.
By the way: FortiusANT and ExplorANT use the exact same loop.

It COULD mean that, when I think I use the second dongle, that actually the first is tried and hence is in use.

from fortiusant.

Log files for -d1, -d3 and -d7

ExplorANT.2020-04-13 13-45-27.log
ExplorANT.2020-04-13 13-46-26.log
ExplorANT.2020-04-13 13-45-55.log

from fortiusant.

There is another error now, as if there are no dongles in your system Could not find ANT-dongle where previously you reported GetDongle: [Errno 19] No such device (it may have been disconnected).

In this case, I would power-down the system, take out the dongles (so that they are powered down as well), reboot and see whether there is any difference.

from fortiusant.

Please download logfile.py and antDongle.py and retry test with ExplorAnt -d3

The dongle that is tried is printed to the logfile, let's see whether the second attempt indeed tries the second dongle.

from fortiusant.

Hi guys!
...I downloaded the Python code for FortiusANT but when running the module it says "ModuleNotFoundError: No module named 'numpy'". Would you please describe the installation process you used on mac???
THX

Welcome on board!
pip install -r requirements.txt should do the job, please try

from fortiusant.

Log file attached. Still seeing a similar error - I've checked and my mac recognises both dongles as being plugged in. I also restarted etc as mentioned.

ExplorANT.2020-04-14 08-15-35.log

from fortiusant.

Hi,
Python shell doesn't accept pip install : "SyntaxError"! I didn't see that one since coding in Basic in the early eighties!
Here is the log :
Python 3.8.2 (v3.8.2:7b3ab5921f, Feb 24 2020, 17:52:18)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license()" for more information.

======= RESTART: /Applications/FortiusANT-master/pythoncode/FortiusAnt.py ======
Traceback (most recent call last):
File "/Applications/FortiusANT-master/pythoncode/FortiusAnt.py", line 119, in
import numpy
ModuleNotFoundError: No module named 'numpy'

pip install -r requirements.txt
SyntaxError: invalid syntax

from fortiusant.

I tried "python -m pip install". Didn't work neither! Now I'm confused!

from fortiusant.

Log file attached. Still seeing a similar error - I've checked and my mac recognises both dongles as being plugged in. I also restarted etc as mentioned.

Please download antDongle.py and re-test; I have changed the error-handling in the module.
It seems "in use" works different than under Windows/Linux

from fortiusant.

I tried "python -m pip install". Didn't work neither! Now I'm confused!

I do not have a Mac, so cannot test for you.
"Didn't work neither" is not very clear, what messages do you get?

Perhaps google helps...

from fortiusant.

Sorry for that!
python -m pip install -r requirements.txt
SyntaxError: invalid syntax

from fortiusant.

@M4M4R2

Try: python3 -mpip install - then what you are trying to install

e.g. python3 -mpip install pyusb

Note - I use python3 to use python v3 - my mac default is 2.7 (I think). Also requirements.txt didn't work for me so just installed one by one (think it's because we are on macs)

from fortiusant.

@WouterJD

Log file attached.

ExplorANT.2020-04-14 09-36-18.log

from fortiusant.

@iainhay 2.7 version for MacOs and 3.8 installed for me! The command you provided seems to be understood by the shell at least! I added an unnecessary space between -m and pip! Though when prompting pip install requirements.txt I get :
~ % python3 -mpip install requirements.txt
Collecting requirements.txt
ERROR: Could not find a version that satisfies the requirement requirements.txt (from versions: none)
ERROR: No matching distribution found for requirements.txt
WARNING: You are using pip version 19.2.3, however version 20.0.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

from fortiusant.

python -m pip install -r requirements.txt
SyntaxError: invalid syntax

Please check whether you have python 3 installed; refer this

from fortiusant.

I have reviewed and tested the error handling in antDongle.py GetDongle() on windows.
Please download and test
Version is 2020-04-14b which should be visible in logfile.

Succes!

from fortiusant.

Attached log file - which I think is working, I think it tries one dongle which doesn't work (because this is being used by FortiusANT) then the next one and then is sending and receiving) - is that correct?

ExplorANT.2020-04-14 13-19-36.log

I opened Zwift but still only see a HRM - same with Rouvy too :(

from fortiusant.

Thank you for persistance!

This is what happens on my system:

13:51:53,301: ExplorANT started
13:51:53,301: -d 1 (0b1)
13:51:53,302: -D -1 (-0x1)
13:51:53,302: -H -1 (-0x1)
13:51:53,302: -F -1 (-0x1)
13:51:53,303: --------------------
13:51:53,303: Dongles in the system:
13:51:53,351: manufacturer=Suunto, product=Movestick mini, vendor= 0xfcf, product=0x1008(4104)
13:51:53,355: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)
13:51:53,358: --------------------
13:51:53,920: Using Dynastream Innovations dongle
13:51:55,921: Pairing, press Ctrl-C to exit
13:52:06,001: Pairing stopped
13:52:06,001: HRM discovered on channel=0, number=57592 typeID=120 TrType=120
13:52:06,002:  FE discovered on channel=1, number=57591 typeID= 17 TrType= 17
13:52:06,002: --------------------
13:52:07,428: HRM slave channel 5 opened; listening to device 57592
13:52:07,588: FE  slave channel 4 opened; listening to device 57591
13:52:07,588: Listening, press Ctrl-C to exit
13:52:08,589: HRM#= 3 hr= 93 FE-C#= 3 Speed=34.3 Cadence= 98 Power= 99 hr= 91
13:52:09,589: HRM#= 7 hr= 91 FE-C#= 7 Speed=34.6 Cadence=101 Power= 98 hr= 91
13:52:10,589: HRM#=11 hr= 91 FE-C#= 9 Speed=34.6 Cadence= 98 Power= 98 hr= 91
13:52:11,458: Listening stopped
13:52:12,001: We're done
13:52:12,001: --------------------

It appears that the HRM from FortiusANT uses all channels.
Please restart with -H 0 which causes that no HRM-master is broadcasted and let me know the result.

from fortiusant.

Log attached.

ExplorANT.2020-04-14 14-01-40.log

Zwift doesn't find the HRM anymore but nothing else. It finds a Power Source as before but no watts coming through.

from fortiusant.

The logfile shows the same difference with Windows/Linux:

14:01:52,983: FE discovered on channel=0, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=1, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=2, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=3, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=4, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=5, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=6, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=7, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=8, number=57591 typeID= 17 TrType= 17
14:01:52,983: FE discovered on channel=9, number=57591 typeID= 17 TrType= 17

all channels are now receiving the FE-C information. I will try to investigate this...

Just to be sure; you pressed the earch button on CONTROLLABLE and did not get any devices?

from fortiusant.

PS. Do you have an ANT+ heart rate monitor?
In that case, please activate and show what ExplorANT shows...

from fortiusant.

Yes that's right, tried them all and came back with no results.

No sorry I don't have a HRM

from fortiusant.

Sorry I may ask again; on what system is Zwift running?

from fortiusant.

Macbook pro 2019 running macOS Catalina (10.15.4).

I have tried Zwift on my Android too with the same results (Samsung Galaxy S9)

from fortiusant.

Just to be sure: FortiusANT, ExplorANT and ZWIFT are running on the same system?

from fortiusant.

Correct.

Just to be clear - am I am running FortiusANT, then I am trying to start Zwift - if I run FortiusANT then ExplorANT and then open Zwift then ANT+ is unavailable.

In order to run I am only supposed to run FortiusANT right?

from fortiusant.

Also, when running FortiusANT (with -s) and then running ExplorAND I get the following output:

14:53:22,671: ExplorANT started
14:53:22,671: --------------------
14:53:22,671: Dongles in the system:
14:53:22,684: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
14:53:22,684: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
14:53:22,685: manufacturer=Realtek, product=USB 10/100/1000 LAN, vendor= 0xbda, product=0x8153(33107)
14:53:22,686: manufacturer=GenesysLogic, product=     USB2.1 Hub, vendor= 0x5e3, product= 0x610(1552)
14:53:22,687: manufacturer=GenesysLogic, product=     USB3.1 Hub, vendor= 0x5e3, product= 0x626(1574)
14:53:22,688: manufacturer=Apple Inc., product=Apple Internal Keyboard / Trackpad, vendor= 0x5ac, product= 0x340(832)
14:53:22,690: manufacturer=  Apple, product=           None, vendor= 0x5ac, product=0x8104(33028)
14:53:22,690: --------------------
14:53:23,227: Using Dynastream Innovations dongle
14:53:25,312: Pairing, press Ctrl-C to exit
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
14:53:35,417: Pairing stopped
14:53:35,417: --------------------
14:53:36,750: Listening, press Ctrl-C to exit
14:53:37,761: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:38,767: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:39,779: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:40,792: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:41,796: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:42,804: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:43,815: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:44,828: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:45,842: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:46,854: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:47,864: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:48,875: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:49,882: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:50,891: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:51,906: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:52,919: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:53,928: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:54,938: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1
14:53:55,948: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1

Which looks like it's not receiving any data?

from fortiusant.

ExplorANT is a support-tool to show what devices are available on the ANT+ network and normally not used. ExplorANT comes in handy to do the excercise we do now.

Now we are testing, start FortiusANT (gui, autostart, simulate, noHRM).
FortiusANT goes to operation and simulates activity, which should be visible from a slave.

FortiusAnt.py -g -a -s -d0 -H0

Then start ExplorANT to show what's happening, first pair with FE and then show activity.

ExplorAnt.py -d1

ExplorANT takes 10 seconds (40 ANT receive cycles) to pair and displays a dot on every cycle.
If a device is discovered you see * followed by HRM or FE.
After the 10 seconds, ExplorANT continues listening on the network.
Stop ExplorANT to free the second dongle.

If that's working, start ZWIFT and pair to FortiusANT.

While typing I received your message, so that is what you do.
It's not only ZWIFT that does not see a slave, ExplorANT does not see it either.

Resetting dongles can be done by removing them from the system (dongle power off); perhaps also rebooting the system helps (include power down!). Anyway, when testing and stopping/starting a lot, this does help on Windows. Not needed frequenly, though.

from fortiusant.

Okay that makes sense.

Just tried after powering down etc but the same output.

I am getting the dots for each cycle, but no * and no HRM or FE?

14:53:23,227: Using Dynastream Innovations dongle
14:53:25,312: Pairing, press Ctrl-C to exit
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
14:53:35,417: Pairing stopped
14:53:35,417: --------------------
14:53:36,750: Listening, press Ctrl-C to exit
14:53:37,761: HRM#= 0 hr= -1 FE-C#= 0 Speed=  -1 Cadence= -1 Power= -1 hr= -1

Starting Zwift I then get nothing except a power source (which is because the dongle is free) but nothing for anything else:

from fortiusant.

My configuration is as follows:
PC1- Windows system with USB and two ANT+ dongles (Suunto, Dynastream)
PC2- Windows system with ANT+ dongle

OnPC1 I run FortiusANT and PC2 I run Zwift; click here here for the pairing window.

This defines the expectation; in the pairing windows, ZWIFT displays the actual value as broadcasted from FortiusANT.

Note that, FortiusANT broadcastes ONE device (FE-C) where Zwift displays three. This does not mean that there are three devices; you can use parts of the device and select other (similar) devices at will.

from fortiusant.

What I did is the following

PC1:
1- Start FortiusANT; works in simulation mode
2- Start ExplorANT; does not find devices [not OK, no explanation]
3- Start Trainer Road; finds devices [OK]

PC2:
4- Start Zwift; finds FortiusANT devices (the video in previous message) [OK] (stop Zwift)
5- Start Trainer Road; finds devices [OK]

Reboot PC1:
6- Start FortiusANT like before [OK]
7- Start ExplorANT; now finds FE immediatly [OK] (stop ExplorANT)
8- Start Trainer Road; finds devices [OK]

While rebooting, Zwift shows "No Signal" and after restarting FortiusANT the connection is restored automatically [OK]

My conclusion is:

• FortiusANT AND a 2nd application (ExplorANT, Zwift, Trainer Road) can work on the same system
• Sometimes, ANT+ is funny, or there is a flaw in FortiusANT
  Well --- not very satisfactory, is it (step 2)?
• Rebooting helps

Question:
Any chance you can test with a second Mac?

from fortiusant.

Okay, interesting. I've tried rebooting a few times and nothing - so my mac has USB C ports, and I have an adapter plugged into one with the 2 ANT+ sticks. I just tried a different adapter for 1 ANT+ stick. So I now have 2 adapters each with 1 ANT+ stick in.

ExplorAnt now seems to pick it up!

16:10:36,668: ExplorANT started
16:10:36,668: -d 1 (0b1)
16:10:36,668: -D -1 (-0x1)
16:10:36,668: -H -1 (-0x1)
16:10:36,668: -F -1 (-0x1)
16:10:36,668: --------------------
16:10:36,668: Dongles in the system:
16:10:36,682: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
16:10:36,682: manufacturer=GenesysLogic, product=     USB2.1 Hub, vendor= 0x5e3, product= 0x610(1552)
16:10:36,683: manufacturer=Dynastream Innovations, product= ANT USBStick2, vendor= 0xfcf, product=0x1008(4104)
16:10:36,684: manufacturer=Realtek, product=USB 10/100/1000 LAN, vendor= 0xbda, product=0x8153(33107)
16:10:36,684: manufacturer=GenesysLogic, product=     USB3.1 Hub, vendor= 0x5e3, product= 0x626(1574)
16:10:36,686: manufacturer=Apple Inc., product=Apple Internal Keyboard / Trackpad, vendor= 0x5ac, product= 0x340(832)
16:10:36,687: manufacturer=  Apple, product=           None, vendor= 0x5ac, product=0x8104(33028)
16:10:36,687: --------------------
16:10:37,212: Using Dynastream Innovations dongle
16:10:39,105: Pairing, press Ctrl-C to exit
* FE * FE * FE * FE * FE * FE * FE * FE * FE * FE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 
16:10:49,154: Pairing stopped
16:10:49,154:  FE discovered on channel=0, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=1, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=2, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=3, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=4, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=5, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=6, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=7, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=8, number=57591 typeID= 17 TrType= 17
16:10:49,154:  FE discovered on channel=9, number=57591 typeID= 17 TrType= 17
16:10:49,154: --------------------
16:10:50,587: FE  slave channel 4 opened; listening to device 57591
16:10:50,587: Listening, press Ctrl-C to exit
16:10:50,858: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:10:51,588: HRM#= 0 hr= -1 FE-C#= 1 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:52,592: HRM#= 0 hr= -1 FE-C#= 1 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:53,364: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:10:53,597: HRM#= 0 hr= -1 FE-C#= 2 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:54,606: HRM#= 0 hr= -1 FE-C#= 2 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:55,618: HRM#= 0 hr= -1 FE-C#= 2 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:55,898: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:10:56,632: HRM#= 0 hr= -1 FE-C#= 3 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:57,639: HRM#= 0 hr= -1 FE-C#= 3 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:58,421: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:10:58,652: HRM#= 0 hr= -1 FE-C#= 4 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:10:59,659: HRM#= 0 hr= -1 FE-C#= 4 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:00,665: HRM#= 0 hr= -1 FE-C#= 4 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:00,939: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:11:01,669: HRM#= 0 hr= -1 FE-C#= 5 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:02,677: HRM#= 0 hr= -1 FE-C#= 5 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:03,454: IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
16:11:03,683: HRM#= 0 hr= -1 FE-C#= 6 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:04,693: HRM#= 0 hr= -1 FE-C#= 6 Speed=  -1 Cadence= -1 Power= -1 hr= -1
16:11:05,698: HRM#= 0 hr= -1 FE-C#= 6 Speed=  -1 Cadence= -1 Power= -1 hr= -1

But still nothing on Zwift - going to try Zwift on another mac now and see if that works, back soon!

from fortiusant.

No still nothing - same results on another mac.

The results above show it's connects - but there doesn't seem to be actually results passed in?

No speed / power etc?

from fortiusant.

Another interesting note:

If I run ExplorAnt, with the FortiusAnt (-s) running, I see:

IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"

If I stop FortiusANT then the IGNORED messages stop and I just see:

HRM#= 0 hr= -1 FE-C#= 6 Speed= -1 Cadence= -1 Power= -1 hr= -1

Over and over. If I start FortiusANT again then I start to see the IGNORED again.

Any ideas?!

from fortiusant.

Yes I can test with 2 macs if it helps!
I just plugged the all thing (i.e. 1932 head + 2 "1008" ANT+ dongles.
Running FortiusANT.py, got this :
=================== RESTART: /Applications/FortiusANT-master/pythoncode/FortiusAnt.py ===================
Exception: No backend available
Exception: No backend available
Exception: No backend available
16:33:34,174: Dongle - GetDongle - No backend, check libusb: No backend available
16:33:34,212: GetTrainer - No backend, check libusb: No backend available
16:33:34,239: Tacx - GetTrainer - No backend, check libusb: No backend available

Is that what it is supposed to do??

from fortiusant.

Exception: No backend available

Is that what it is supposed to do??

No, please check all previous messages which gives a lot of info what it is supposed to do.
It seems that the libusb library is missing @iainhay please advise...

from fortiusant.

Another interesting note:
IGNORED!! msg=0x4e ch=4 p=0 info="04 00 00 00 00 00 00 00 00"
Any ideas?!

Well; the same happens as in Zwift: the program sees that there is an FE-C device but does not receive info; the message contents is incorrect.

I always say Google my friend; searching and trying will be the solution; it seems that for some reason the ANT(usb) software is not stable.
I will ask around whether I know somebody who uses Mac / ANT / Zwift --> Tacx (neo) trainer.

from fortiusant.

Exception: No backend available
Is that what it is supposed to do??

No, please check all previous messages which gives a lot of info what it is supposed to do.
It seems that the libusb library is missing @iainhay please advise...

Sorry for that! I try to catch up! Sorry again!

from fortiusant.

@WouterJD Great thanks again for your help and patience, will have a play and see how I get on.

Out of interest, what ANT+ sticks do you use?

from fortiusant.

@WouterJD Also - could you provide me with a correct log file for ExplorAnt so that while working on this I can see the correct output - that would be super helpful!

Determined to get this working!!

from fortiusant.

@iainhay OK i had a missing lib problem!
Solved it with homebrew eventually!
Now where were you with the time out Errno 60 stuff?

from fortiusant.

What you will see is that .write() accepts a string, where .read() returns an array of binaries. This is according the specs.

I have added some links to https://github.com/WouterJD/FortiusANT/wiki/Sources-of-information#interfaces

from fortiusant.

Now where were you with the time out Errno 60 stuff?

@M4M4R2 if you download the latest version of antDongle.py then it should work as @WouterJD has made some changes we discussed earlier in this thread.

from fortiusant.

So last eve I managed to get to this

But this morning Zwift is unable to connect to anything... I've got the spinning ball spinning around and around...

from fortiusant.

What's your set up? That's correct and what is meant to happen.

If it's not working now, try and unplug the dongles and restart your mac, then plug in and try again (that got ExplorANT connecting for me)

Are you using Zwift, Fortius and 2 ANT sticks in the same Mac? If so it must be my ANT sticks that are the issue - @WouterJD do you agree?

from fortiusant.

Same set up as yesterday night! Ok I know why! I moved only the Dongle.py in the former folder replacing the old one... I trashed the FortiusANT folder and replaced it by the new one and I now get this :

from fortiusant.

Are you using two macs or one like me?

So you are saying the previous code worked for you and now you have updated the files it doesn't work?

from fortiusant.

As I said before I could use 2 but what I was intend to was to use only one. So right now (as yesterday) all is plug on ONE machine. And by the way my mac is a 2016 13" MBP with TouchBar running Catalina 10.15.4

from fortiusant.

That's right I got yesterday to the point that everything seemed to be working with the unupdated files but now only the powermeter seems to be connected! At least not the same info displayed by Zwift (see screenshots)

from fortiusant.

I didn't try with the magnetic wheel plugged yet! Only with the t1932 head and 2 dongles so far

from fortiusant.

Okay - let me see if I can review the changes and get it working for us.

from fortiusant.

When did you download the original code? I just went back to this version and get the same issues

from fortiusant.

I downloaded the full Master this morning!

from fortiusant.

This morning around 9:00 CET:

1x: manufacturer=Suunto, product=Movestick mini, vendor= 0xfcf, product=0x1008(4104)
2x: manufacturer=Dynastream Innovations, product=ANT USB-m Stick, vendor= 0xfcf, product=0x1009(4105)

I have modified logfile.py and antDongle.py to have better logging on .write() and .read().
Hope this helps

ExplorANT.2020-04-15 06-57-12.log
FortiusANT.2020-04-15 06-56-24.log

I see your remarks on your investigations.
I would suggest: run FortiusANT.py -g -a -s -H0 -d127 and ExplorANT.py -d127 and submit logfiles.

I think it is not a Zwift issue, it seems that the programs detect that there is an ANT+ FE-C device but that no data is received.
Using ExplorANT enables to see what is exactly happening on the ANT+ interface, where Zwift only shows the result.

Sorry that all log-data is also copied to the console, which does not make the console-interface understandable. I will check into this at a later stage and see to approve.

from fortiusant.

When did you download the original code? I just went back to this version and get the same issues

Just to be sure ... While testing, please do not use the .exe file; I will update that one as soon we have a final version that works.

from fortiusant.

Now I get this again :

from fortiusant.

If I understand right this means the following:

• Zwift has seen an ANT+ FE-C device 57591 is FortiusANT
• Zwift does NOT receive any data and hence displays "Aucune reception"

In my environment, this happens when:

• I start FortiusANT
• I start Zwift
• I press STOP in FortiusANT
  that's why I recognize the image. (refer to #45 (comment))

Please run ExplorANT.py -d127 and post logfile

from fortiusant.