If there are any SB20 users here who also owns a SB20 bike, I would like to connect w/ you in an effort to improve support for the SB20 bike.
Reason:
Got a negative review on the App Store saying it’s not working well w/ the SB20 and while I’ve worked on this before and did some fixes, those fixes were not verified.
What I basically need you to do is simply, put in “loglevel10” (no quotes into the Settings Tab at the Developer Text Field) execute a workout (any), pedal for some time and then collect the logs. The SB20 bike is sending POWER and SPD data in it’s packets in alternate formats each other second and I need to separate it out. If it’s working well, you won’t see the power going from 100w, 0w, 100w, 0w, 100w etc…
After that, you should be able to download the beta version (right now, the beta version is the same as the App Store Version so you could choose to download either one, but I suggest the testflight version since w/ your help, I would be making changes and uploading the Beta version anyhow.
For logging:
Please enter “loglevel10”(no quotes) within the SETTINGS tab on the developer Text Field (all the way at the bottom of the SETTINGS tab).
Once this is done, please wait ~10sec for the settings to take effect.
After this:
Wait for the app to connect to all your sensors
Once all sensors are connected, execute / start a workout (any would do)
Pedal for a while, maybe 1min+ for it to gather some data
Stop, Save the workout.
The Logfile will get generated and will be in the HISTORY tab as a plain text file. I think it should be called as DebugLog.txt. You should be able to tap on the filename in the HISTORY tab and it would prompt out a Mail Client (only apple mail supported). Otherwise, you can use the Files App / Auto Upload to DropBox / iTunes File Sharing to send me the file.
Feedback needed from you:
is the Power values showing up as expected? (no 100w,0w, 100w or some weird number that is not the same as what you would expect. eg: connect the BreakAway app AND your Garmin and see if the numbers match)
I’ll leave here 2 videos, which demonstrate the application working together with the Garmin Edge 830, to point out that all the attempts I made the application automatically crashes after 1 minute, crashes and jumps out.
One thing that may or may not influence,
in all applications when using this bike we have to select only the left power sensor and the bike, in this case as seen in the movie it automatically turns on all sensors, I don’t know if it uses all of them but if so it causes problems,
I with several applications when trying to connect the 2 power meters always gave errors and did not work, until I realized that only the left power sensor is connected and it works well because it receives the information from the right sensor and sends both information to whatever it is switched on.
I can confirm that the Crash at the 1min mark is due to the LR power Balance that you’re seeing as 101- -1 (basically 101% L and -1% R). The app is continuously saving the FIT file every 1min (hence the crash at 1min) and the LR Balance is in error w/ a -ve number not being permitted.
I actually saw this from a crash report sent back to Apple so i have actually sort-of fixed that in the (not yet approved by Apple) BETA. [There’s a workaround for this crash, which is to turn off “Save as FIT” in the Settings/Advanced Options and this will save the output as TCX (which does not support LR bal)]
w/ regard to the left power sensor… how do you know which is L and which is R from the 2 sensors? (Since I don’t see any noticeable diff in the names)
Does the SB20 work if ONLY connected as FTMS Trainer? (w/o connecting to the Cycling Power? If yes, what would be omitted? LR data I presume?)
Finally, I am not entirely sure, is the Power Data (power 3s) correct? From the video, it does look like it is. At least for the 1st video. I don’t see things like 100w, 0w or 100w, 50w, 100w so that may mean prev fixes is working.
While waiting for Apple to approve the new beta, could you please send me some logs?
It’s easy, on both cranks the number is marked, in my case and as you can see in the movie are (4994 Left, 11484 right)
That I don’t know, I just know that in every application I tested I just turned on the cycling power and the left crank arm power meter, and it always worked great
Yes it is correct, but in some attempts and we can see that in one of the movies it is showing the values below the target, and it is seen that in Garmin the values are correct with the target.
But we no longer have abnormal values like these 100w, 0w or 100w, 50w, 100w.
Yes… it is, unfortunately it doesn’t tell the App that. (I’m trying to make manually connecting to sensors a thing of the past and have it “just work” - clearly this needs more work given the myriad diffs of trainers)
haha… crash reports from Apple are anonymous, as are reports from TestFlight (if joined using a public link -eg: per one of the msg above)
I see…
Noted… possibly some mixing w/ the Cycle Power Meter AND the Trainer Power. Need to dive into it…
TQ again, while waiting for the new Beta to be approved
Cool… Thanks… you can send it to app4g.devel AT gmail.com
I’ve made a bunch of changes to the SB20 code to cater for that pesky Right Side Power Meter which seems to be messing up the Power Numbers & the LR Balance Data. With your logs, I should be able to pinpoint if the fix i did fixes it.
Also - from the “recommended settings” from stages, Power Match is recommended to be turned off (I think you should also do the same thing for BreakAway when testing since I believe that Stages itself is already doing the power matching internally)
I think my fix is successful for filtering out the Right Power Meter Data and this would help in providing the correct LRBalance Data (as well as Power Data coming from the Power Meter Cranks - since R power is broadcasting 1/2 power).
Looking back at the 2 videos you posted, remember I said that 1 video shows the Power Looks in-sync w/ the Garmin and the other doesn’t? I think I found the reason why.
In the App, if Power Match is enabled, The app will default Power Priority to “Cycle Power” (meaning, it will display & write Cycle Power values to the FIT file and user will not be given a choice to select any other options)
This combo will cause the incorrect power being displayed (due to Right Power Meter Data)
However, if you disabled PowerMatch, Notice that the Power Priority options are now available and you can select to display the power from any of the sensors
In your case, The video w/ the power that looks OK, I believe you’re selected Trainer Power. The video w/ the power that looks BAD, it’s highly likely due to Cycle Power being selected.
If you can help confirm:
Test One:
Power Match - Disabled
Power Priority - Trainer
Execute a workout
What I expect:
Displayed Power would be in-sync w/ the Garmin
LR Bal would still be problematic
Test Two:
Power Match - Disabled
Power Priority - Cycle Power
Execute a workout
What I expect:
Displayed Power would have issues and be like 20-50% lower Than expected
LR Bal would still be problematic
Note: If you want to test beyond 60seconds, go to Advanced Options and disable this option. That should fix the crash at 60seconds. (i think you don’t even need to be pedaling, just start a workout and if the app is OK > 60s then that confirms it)
@Joao_Samora New Beta Version 61.3 has now been approved by Apple.
Please see if this fixes the issues.
LR Bal
– No More showing 100 - -1 and is showing proper values
Power Priority = CyclePower
– Power is now similar to that as your Garmin
– Choosing Either Power Priority = Trainer / Power Priority = CyclePower will not matter anymore. Both will show correct Power Values
No More Crash at 60seconds
– with Save Workout as FIT File enabled
BTW - please “swipe to delete” the old DebugLog file prior to clear up all the old data.
YOu should still see all sensors connected to the app automatically as previous (L power, R power, HR, Spd/Cad, Trainer)
Yes, I already received the update, in fact I even received two, one yesterday and another today lol. I already do a new test to see if everything is correct.
I’ve done some more tests today and sent an email with the videos, and with the other records, there are still small flaws, in terms of reading on the left/right side and in cycle trainer mode
