(10-27-2020, 07:30 AM)skicavs Wrote:(10-27-2020, 12:35 AM)Snowpelt Wrote: Nothing on your end to do to activate it, it should just work if the bike supports it. I can agree that looking at the connection on the back end it appears to not have been passing resistance. Will see if we can dig into what's going on here, it's very hard to do without the bike though! Eric may chime in with some more info.
Thanks! sounds good, I am fairly familiar with android, ADB and debugging tools (I worked for magic leap for a year) so if there is something I can run on my side let me know.
It's great that you could help like that! I will soon post an Android test tool that will output details to ADB log about FTMS details. Beyond having FTMS, it needs to support the "indoor bike data" characteristic, the "fitness machine control point", and the "indoor bike sim" capability for VZfit to control resistance.
UPDATE:
The link to that tool is https://drive.google.com/file/d/0B5eeLDx...sp=sharing
This will download a "biketest10.apk" which you can install on an Android 7+ phone or Go/Quest headset via adb or Sidequest.
You can then run it (on headset via Oculus TV) while running "adb logcat -s blueGigaBLE" to see our connection logging.
For successful FTMS resistance control you should see
blueGigaBLE: Connecting to <your device MAC>
blueGigaBLE: Type: FTMS device
blueGigaBLE: Found indoor bike data
blueGigaBLE: Found ftms control point
blueGigaBLE: Requesting ftms control
blueGigaBLE: Granted ftms control
blueGigaBLE: Initializing ftms resistance
blueGigaBLE: Granted ftms resistance
blueGigaBLE: Make: <your device make>
blueGigaBLE: Model: <your device model>
If it gets to make/model without all those, then we won't currently be able to control resistance, but would like to hear where it bails.