GUI restarts and crashes (black window) when using BLE

[WouterJD]

I have a follow up question after issue #486:

Since this is working in manual mode now, I tried to connect the trainer to the Tacx app on my phone using BLE. When using my very first methode using the .exe and the settings, the GUI restarts and crashes (black window) and the command gives this respons:

When using the last methode you described, I used the Startup .bat file with the code: ..\WindowsExecutable\FortiusAnt.exe -g -a -bb. This works without any problem. I do not have a separate dongle for the BLE but when I scan with the Tacx app for trainers I find a device with my PC name. The only problem I'm having there is that it thinks it's only a heartrate monitor and not a trainer. So only the heartrate is shown. (This problem can be replicated with the Simulation of a trainer). Is this problem caused by a compatibility problem with my build in bluetooth connector or something else?

I saw a similar issue raised already but there was no reaction if it was solved.

Originally posted by @Nivran in #486

[WouterJD]

The BLE-python-interface is not always as stable is desired, especially in non-standard cases.

The Windows BLE driver never worked, a BLE/5 driver is required.
This will most probably be the reason for the problem.

Note that CTP's can work using the windows BLE; the python driver does not.

Bying a BLE/5 dongle is the way to go.

[WouterJD]

Since there is no communication here, I assume can be closed.
If not happy to reopen

[Nivran]

Hi Wouter,

Since our last conversation, I bought a BLE dongle ( the next one in line of the recommended one: https://www.bol.com/be/nl/p/asus-usb-bt500-bluetooth-adapter-usb-2-0/9300000005683717/?cid=1758133996662-9001518738260&bltgh=mdC1qPxPmK7oQ9vOIahOGQ.4_41.42.ProductTitle)

When I disable the build-in bluetooth connector and put in the dongle, I see my dongle is activated. But when I connect to my app of Tacx I again only see the heartrate like motioned above.

You mentioned that "The Windows BLE driver never worked, a BLE/5 driver is required.
This will most probably be the reason for the problem."
=> Do I need to install a new driver for the dongle or what do you recommand?

[WouterJD]

As far as I can see, the dongle seems ok.
You do not mentuon current FoetiusAnt settings, I assume you start with - bb (native ble).

• What messages are displayed on console?
• How do you check what devices are broadcasted?

A good tool to inspect (on android) is: "lightblue" which allows to look at available BLE devices.

Please let me know...

[Nivran]

Hi Wouter,

Thank you for re-opening the question.

I did start the software with the -bb like you mentioned. ( ..\WindowsExecutable\FortiusAnt.exe -g -a -m -bb -s
)
I scanned with the app "Lightblue" and I can actually see my a device with my PC name.

When I connect to my PC, I can see there is a part called: Fitness Machine & Heart Rate. On both there are properties where I can subscribe/read and see some value's coming in. Also writing is possible and I can see in the CMD that the program acts to the write value's.

Is it the tacxs software that is not recognizing the BLE donge correct? Is there another app that I can use on my phone that can control my Fortius for trainings?

[WouterJD]

What CTP do you use?
As I understand, tacx does only support their own hardware.

Please try software that is known to support the standard; zwift, trainer Road, rouvy, mywhoosh.

[Nivran]

The training app that I used was the Tacx app (like mentioned in the first post).

I tried mywhoosh (because it's also free) and there I can connect to the FortiusAnt software with all the value's of the FE-C connected. I even don't have to use the dongle and can use the internal BLE connector.

Thank you for the support with this problem. This problem can be closed.

[WouterJD]

I guess fortiusant uses the dongle and mywhooshthe internal device?

Please letme know.

[Nivran]

I connect the fortiusant on my PC to the Mywoosh app on my phone using my onboard internal BLE connector.

[WouterJD]

Great PC, evidently the BLE device fits the python library requirements.

Thanks