Replies: 20 comments 115 replies
-
Great! I will start the implementation today! |
Beta Was this translation helpful? Give feedback.
-
Initial test - debug log from QZ attached and screenshots from NRF connect. Very possible that I screwed up the build on either smartspin or QZ... I haven't gone through the logs myself yet.
|
Beta Was this translation helpful? Give feedback.
-
Better luck this time. Got it connected. Physical buttons working. Couldn't get to log on smartspin for some reason so I'll have to figure that out. '-' on QZ moved the resistance approx. 5 levels down. '+' didn't seem to do anything. Attaching the log here just for information, hard to diagnose when I can't see what smartspin is seeing. Will get that working and update. |
Beta Was this translation helpful? Give feedback.
-
Sweet!
I'll do some more stability testing and work this into a new release this weekend then. Thanks for the help @cagnulein and @marklogan17
|
Beta Was this translation helpful? Give feedback.
-
@doudar check this out https://www.facebook.com/groups/149984563348738/permalink/235370781476782 !! |
Beta Was this translation helpful? Give feedback.
-
I actually don't have a Facebook account anymore. Can you summarize? Otherwise maybe I can check it out later with my wife's account. @marklogan17 , could you check out the and test the latest ss2k develop ? Huge and awesome changes in there and I'd like to make sure nothing is broken before I make a release with it. |
Beta Was this translation helpful? Give feedback.
-
It was just the post of mark about your latest development on the echelon!
You should create a fake account and join ;)
Il giorno dom 27 giu 2021 alle 20:33 Anthony Doud ***@***.***>
ha scritto:
@doudar <https://github.com/doudar> check this out
https://www.facebook.com/groups/149984563348738/permalink/235370781476782
!!
I actually don't have a Facebook account anymore. Can you summarize?
Otherwise maybe I can check it out later with my wife's account.
@marklogan17 <https://github.com/marklogan17> , could you check out the
and test the latest ss2k develop ? Huge and awesome changes in there and
I'd like to make sure nothing is broken before I make a release with it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#377 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWCGP27ETBCP77OTG5LTU5VF5ANCNFSM47AOV6NQ>
.
--
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
|
Beta Was this translation helpful? Give feedback.
-
Had a strange experience today. SS2K would start up and work properly - up and down physical buttons were fine. I set QZ on my iPhone to connect for the first time and it worked. So then I proceeded to do more UI config on QZ (which tiles, etc). Then I restarted it and connected and SS2K went right up to max resistance on the Echelon and tried to go further. I unplugged, manually turned down the resistance and tried again. Same thing. So then I killed the iOS app and tried on my Android. Same thing. Tried no QZ connection and it was fine. I eventually got it to settle down, I think by starting SS2K and hitting the physical up button and waiting a bit. Not sure if that actually did anything or I just got lucky. The target resistance on QZ was never 32 or above. Felt more like the 'zero' command wasn't working properly. Logs below (I hope they caught it). iOS_debug-Fri_Jul_2_16_06_40_2021.log |
Beta Was this translation helpful? Give feedback.
-
The problem that I saw now it’s fixed so probably was something else. I
will check it tomorrow
Il giorno sab 3 lug 2021 alle 22:04 marklogan17 ***@***.***>
ha scritto:
Grabbed the latest, built and installed. Just hit the same problem. This
time I started SS2K, started QZ, hit + on QZ and nothing, hit physical up
button and it went up, but then went up an extra level. Hit + on QZ and
nothing. Killed QZ, restarted and it started increasing up to 32 when I
unplugged SS2K.
debug-Sat_Jul_3_16_00_48_2021.log
<https://github.com/cagnulein/qdomyos-zwift/files/6758983/debug-Sat_Jul_3_16_00_48_2021.log>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWCITDMBYW3SHAQYEZTTV5UNJANCNFSM47AOV6NQ>
.
--
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
|
Beta Was this translation helpful? Give feedback.
-
Yea try to set it to 0 or 1
Il giorno dom 4 lug 2021 alle 17:28 marklogan17 ***@***.***>
ha scritto:
I don't remember changing it - certainly not on the iPhone. What should I
have it at? Zero?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWHVZPW75XRCZK3QL53TWB4YXANCNFSM47AOV6NQ>
.
--
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
|
Beta Was this translation helpful? Give feedback.
-
Yeah i was proposing to you the same solution while i was reading your
trials. So yes, if it works i guess you proved out your theory ;)
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno lun 5 lug 2021 alle ore 22:09 marklogan17 <
***@***.***> ha scritto:
… OK, I think I may be on to something here and it should be reasonably easy
to test. I've felt its a timing issue because sometimes it just works and
is quite stable. I spent a bunch of time getting SS2K to build and install
- turns out the logging I added in the move loop was causing a panic. Oops.
Anyway, long story short, once I got it running immediately I got the
problem. I had added some logging in the BLE server code in SS2K and I
could see it tell QZ that the current resistance was zero, then I saw QZ
put it in sync mode and set the resistance to 19 and then turn off sync
mode but the motor was running.
So what do I think may be happening? Well what if sync mode is getting
turned off before the move loop has a chance to process the 'update
location but don't move' request. I think when we turned on the sync mode
and sent 19 as the resistance, we turned off sync mode the move loop jumped
in and decided that it had to add 19 levels of resistance. That explains
why there's no logging of events or anything else happening and the
resistance on SS2K isn't changing - you've set 19 as the resistance and
darn it, its going to get to 19 :)
So what I'm going to do is put a nice big sleep in the code in QZ where it
syncs the resistance. I don't think that's the ideal answer but it should
prove out my theory. I'll let you know what I find out in the next few
hours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWA6GQVZJMGKVLC2W23TWIGOFANCNFSM47AOV6NQ>
.
|
Beta Was this translation helpful? Give feedback.
-
It’s very ugly but in the end if it works who cares :)
I guess it should be analyzed more in the SS2K code anyway
I will commit this in the master today
Thanks Mark!
R.
Il giorno mar 6 lug 2021 alle 01:17 marklogan17 ***@***.***>
ha scritto:
OK I'm convinced that's the problem. I added a 2 second sleep before
turning off 'notify' mode and it worked 100% of the time. Even better, when
I went back to my iPhone without the delay it failed 100% of the time. Then
to be doubly sure, I tested with the Android version which 'notified' SS2K
that the resistance was 20. Then I closed the Android QZ and opened QZ on
my iPhone. It worked perfectly because it 'notified' SS2K that the
resistance was 20, which already matched SS2K's expectations, so it didn't
try and move the resistance up 20 levels. I then shut down QZ, shutdown
SS2K, started SS2K, started QZ on iPhone and sure enough, it notified '20'
and the motor started turning.
This is the only change I made in QZ:
writeCharacteristic(enable_syncmode, sizeof(enable_syncmode),
"BLE_syncMode enabling", false, true);
forceResistance(startupResistance);
QThread::sleep(2);
writeCharacteristic(disable_syncmode, sizeof(disable_syncmode),
"BLE_syncMode disabling", false, true);
I'm not sure that's the best solution as SS2K should probably ensure the
motor doesn't move until the 'operation' of the notify mode is completed.
However this sleep in QZ isn't a bad thing either way...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWDNOJL6BQMCVQXQMBDTWI4RJANCNFSM47AOV6NQ>
.
--
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
|
Beta Was this translation helpful? Give feedback.
-
@marklogan17 / @cagnulein - I know this is a very old thread but I just stumbled on the QZ app in the apple app store. I have a SmartSpin2k that gets its power from assioma power pedals. I also have a peloton account so I paid for the swag bag in the QZ app, entered my peloton creds and restarted. The app upon first boot looks like it's cycling through a bunch of bluetooth devices - it flashes the smartspin2k but never seems to connect or at least nothing makes me think it connects (I've disabled bluetooth on the device that the smartspin2k was connected to). If I start a peloton ride it promps if I want it to use that ride...but no metrics on the screen ever change. I found the smartspin2k under the Settings>Accessories>SmartSpin2k which seems to force the bluetooth to the SmartSpin...but again nothing seems to happen - no cadence or power is showing in the app. Is there something else I need to do? |
Beta Was this translation helpful? Give feedback.
-
Oh! Interesting. I assumed that you were using the Peloton serial...I guess I should have noticed that in the logs. In either case, possibly the above logic still applies? |
Beta Was this translation helpful? Give feedback.
-
Where would I do this - and will the assiomas still connect? |
Beta Was this translation helpful? Give feedback.
-
This is what I mentioned in my response to you. All bluetooth set to 'none' in SS2K. Go into the settings find where its searching for bluetooth devices, set them to none and save. QZ needs to connect to your pedals, not SS2K in this scenario. The question is going to be whether there's enough information in the pedals to TELL QZ what it needs to set the resistance to without actual resistance information fed back from the bike. Maybe this is like the iC4 config?? |
Beta Was this translation helpful? Give feedback.
-
I agree with all of the above, but in addition, I think it would be FANTASTIC if @cagnulein could implement some smart switching logic as discussed above as this seems to be a common stumbling block for users on the integration of the two. |
Beta Was this translation helpful? Give feedback.
-
nope, leave it blank
yes
ss2k send me a debug log in this context |
Beta Was this translation helpful? Give feedback.
-
2.16.22 at least
Il giorno lun 27 nov 2023 alle 18:28 Lunchtime0614 ***@***.***>
ha scritto:
… ok I'll check in some time - even though the play store says i'm in the
beta - odd. What's the version number I should see so I know when it's
there?
—
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWFC67NJYIMAYIS6OK3YGTETJAVCNFSM47AOV6N2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TONRYGM3DKMY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Yes qz is also compatible with rowers and peloton rower classes
Il giorno lun 27 nov 2023 alle 22:22 Lunchtime0614 ***@***.***>
ha scritto:
… App updated to the beta version on android...it's working the same as
before on iOS. May try a peloton row class with my concept 2 rower tomorrow
- I see some row stuff in the settings.
—
Reply to this email directly, view it on GitHub
<#377 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWGJEAEU67SWJTFBGPTYGUABVAVCNFSM47AOV6N2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TONRYGU3DSOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Roberto, if you're interested, SmartSpin2k now has a custom characteristic developed for apps like yours to provide more or less direct control over the SS2K.
No doubt there are more overrides and variables that need to be added to the spec as well as probably some bugs to be worked out, however this has been pushed as a new OTA release so existing units have this capability today.
Service UUID is: 77776277-7877-7774-4466-896665500000
Characteristic UUID is: 77776277-7877-7774-4466-896665500001
Documentation:
https://github.com/doudar/SmartSpin2k/blob/develop/CustomCharacteristic.md
Beta Was this translation helpful? Give feedback.
All reactions