-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
64bit Bullseye: GUI not displaying with Bless/bleak version of FortiusANT #386
Comments
Hi malkus. The GUI is disabled for raspberry, because wxpython is not available in standard environment without compilation etc. Enabling is not difficult; check UseGui: |
In my constants.py file its already set to true. Do I need rebuild FortiusANT.sh file in the raspberry folder that I use to start for it to use the info in the constants.py file in python folder? Im not sure how the files are linked / connected... |
If wx cannot be imported, UseGui is set to False
|
HI @WouterJD ! Tried your latest build on github. I now get the gui! Having new issues though. Power output is about 4x normal to zwift. Connection is now stable. during restarts I get error messeges often when trying to autostart FortiusAnt that the bluetooth name is already in use and BLE can not be startes. (I did run through the installation steps to double check that missing) Dont know if it was a good idea or not to install the nodejs stuff as well but I did.. |
Node.js does not conflict |
Why do you restart? |
If it autostarts during bootup it never works.
I have manually close the app and start it again. Then ble ant and
everything connects.
I will provide better feedback / screendumps / logs
Cheers
lör 9 apr. 2022 kl. 15:29 skrev Wouter Dubbeldam ***@***.***>:
… during restarts
Why do you restart?
I can start / stop as many times as I like.
—
Reply to this email directly, view it on GitHub
<#386 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXSFJBXWJIOOKDWR5ZTVM7TVEGA2NANCNFSM5R5DXPOQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
As if FortiusAnt starts too early... |
Heartrate values are recieved by Fortiusant through Ant+ but not transmitted over BLE. Updates picture @WouterJD |
Power values (W) are now back to normal. Nothing changed, several restarts only. Magnetic braie seems to work really well. The Vortex controll display powers down after some minutes. When eaking it up it wont reconnect to FortiusAnt. Stays in standalone mone not showing "pc" on display. Buttons then no longer work for the digital gear selection |
See #373 to be investigated and solved. |
https://github.com/WouterJD/FortiusANT/blob/Implement-BLE-using-bless/pythoncode/bleBless.py#L196 I can do sone tests to check this, using the simulator AND bleak test program |
https://github.com/WouterJD/FortiusANT/blob/Implement-BLE-using-bless/pythoncode/usbTrainer.py#L1187 Since I have no vortex I cannot test this |
Thanks for all your responses @WouterJD ! |
Please test with current version; JSON should be improved now as well. https://github.com/WouterJD/FortiusANT/tree/Implement-BLE-using-bless |
GUI works now! Many thanks |
Hi!
FortiusAnt is up and running and I use it with Zwift. All good :)
Im not getting the gui to display with the -g parameter though.
(The included wxpython video test works well during installation of it)
It likely that I did something wrong due to quite extensive install procedure and I'm all new to this and don't know anything about programming.
Im not receiving any error messages.
I installed the latest versions of everything and compiled a 64bit wxpython pypi and a new wheel along with all other stuff that I found during the way it complained about.
Could someone assist what to do next when I don't see any error messages?
//
I did not install using the all steps of the steps included in the raspberry directory and did not install "node" stuff. Just ran the Fortius straight off except granting accesses.
//
Cheers
Malkus
The text was updated successfully, but these errors were encountered: