-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Steering on Zwift (iOS) #2486
base: master
Are you sure you want to change the base?
Steering on Zwift (iOS) #2486
Conversation
This reverts commit e66db6b.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I think you may have implemented this via the Zwift Ride characteristic, but if not, There's another characteristic that I think you're missing from the steerzo: https://github.com/sebastienb/zwift-steering-joystick/blob/main/steering.ino |
Thanks I will check it!
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno ven 8 nov 2024 alle 01:51 Anthony Doud ***@***.***>
ha scritto:
… I think you may have implemented this via the Zwift Ride characteristic,
but if not, There's another characteristic that I think you're missing from
the steerzo:
https://github.com/sebastienb/zwift-steering-joystick/blob/main/steering.ino
—
Reply to this email directly, view it on GitHub
<#2486 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWCAIXB6TXOVJROZU6LZ7QDJTAVCNFSM6AAAAABLR4KSZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRTGUZDONRWGY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Unfortunately, there's a lot more to it than all this. I found a great youtube video that explains it. (And check the comments for the current state ... broken) |
Actually my code is working, did you try?
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno ven 8 nov 2024 alle 03:47 Anthony Doud ***@***.***>
ha scritto:
… Unfortunately, there's a lot more to it than all this. I found a great
youtube video that explains it. (And check the comments for the current
state ... broken)
https://www.youtube.com/watch?v=BPVFjz5zD4g&t=5s
—
Reply to this email directly, view it on GitHub
<#2486 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWFDXYSLW46767TQKCLZ7QQ3TAVCNFSM6AAAAABLR4KSZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRTGY2DSNBZGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Mine works, I just get this notification on the pairing screen: |
I will try it ASAP, very busy in these days |
That's with this as the authentication callback. Previous to the flip, I was looking for the response length to send the 03 11 ff ff or 03 10 ff ff
|
No description provided.