<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

Dear Joel, I have asked you before --> Please set the Debug

I found this program: <a href="https://github.com/arduino-libraries/ArduinoBLE/blo

Test Zwift Hub FTMS,about berg0162/simcline

Comments (113)

Berg0162 commented on July 23, 2024

Dear Joel,
Please lets have this thread separated from Elite Direto thread!

Are you 100% sure that the Zwift Hub is not connected to another client application (i.c. Zwift)?
It looks like your Zwift Hub is advertising FTMS but is NOT exposing the FTMS Service when it is connected. That means it is controlled by another Client, since you do not have (a) BLE(dongle) that must be over ANT+. Or do you have an other setup?

--> Shut down your PC, remove the ANT+ dongle and restart the PC.
--> Please set the Debug level in the Arduoino IDE to RELEASE (level 0)!!
Like the instructions say:

Requirements: Running FTMS trainer and Feather nRF52 board
1. Start the trainer and do NOT connect it with other devices
1. Upload and Run this code on the Feather-nRF52

Good luck!
Jörgen.

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
Please have a look at this tool for your smartphone to help you inspecting and testing BLE devices:
nRF Connect by Nordic
You can perfectly inspect the Zwift Hub trainer and check for the presence of BLE services like CPS, CSC, FTMS and others. You can easily connect to the trainer and test all those different Characteristics.... and their behaviour. It should be part of your toolbox I.C.E.

I have uploaded a new version for the Client (v023) that is more robust when error states occur. It will not result in an other outcome of your previous test!
Regards,
Jörgen.

from simcline.

le-joebar commented on July 23, 2024

Hello Jorghen,

I redid the test with Ant+ disconnected and Bluethoot gsm switched off.

Here is the result with FTMS_Client_ v022:

Now I think it's good !

Joel

PS : I'm waiting for the dongle, maybe tomorrow

Feather nRF52 Client/Central: CPS, CSC and FTMS
----------------- Version 02.2 ------------------
Initialise the Bluefruit nRF52 module: Client (Central)
[CFG ] SoftDevice's RAM requires: 0x20002C78
FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000016641 F8:9C:FC:53:5E:49 -68 09-02-16-18-26-18-18-18-0A-18
[BLE ] BLE_GAP_EVT_CONNECTED : Conn Handle = 0
[GAP ] MAC = F8:9C:FC:53:5E:49, Type = 1, Resolved = 0
[GAP ] Conn Interval = 20.00 ms, Latency = 0, Supervisor Timeout = 2000 ms
[BLE ] BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST : Conn Handle = 0
[GAP ] ATT MTU is changed to 23
[BLE ] BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST : Conn Handle = 0
[GAP ] Data Length Request is (tx, rx) octets = (251, 251), (tx, rx) time = (2120, 2120) us
[BLE ] BLE_GAP_EVT_DATA_LENGTH_UPDATE : Conn Handle = 0
[GAP ] Data Length is (tx, rx) octets = (27, 27), (tx, rx) time = (1370, 1370) us
[BLE ] BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP : Conn Handle = 0
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking mandatory Client Services and Characteristics!
Discovering Client Cycling Power (CP) Service ... [DISC ] [SVC] Handle start = 1
[BLE ] BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP : Conn Handle = 0
[DISC ] [SVC] Service Count: 1
[DISC ] [SVC] Found 0x1818, Handle start = 41, end = 48

Found it! CPS Max Payload: 20 Data Length: 27
Discovering Client CP Measurement characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A63, handle = 43

[DISC ] [DESC] Handle start = 44, end = 48
[BLE ] BLE_GATTC_EVT_DESC_DISC_RSP : Conn Handle = 0
[DISC ] [DESC] Descriptor Count: 5
[DISC ] [DESC] Descriptor 0: uuid = 0x2902, handle = 44
[DISC ] [DESC] Descriptor 1: uuid = 0x2803, handle = 45
[DISC ] [DESC] Descriptor 2: uuid = 0x2A65, handle = 46
[DISC ] [DESC] Descriptor 3: uuid = 0x2803, handle = 47
[DISC ] [DESC] Descriptor 4: uuid = 0x2A5D, handle = 48
[DISC ] Found CCCD: handle = 44
Found it!
Discovering Client CP Control Point characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Handle start = 49, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 0
[DISC ] [CHR] Gatt Status = 0x0101
Not Found! NOT Mandatory!
Discovering Client CP Feature characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A65, handle = 46

Found it!
[BLE ] BLE_GATTC_EVT_READ_RSP : Conn Handle = 0
-> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ]
Wheel revolution data supported
Crank revolution data supported
Discovering Client CP Sensor Location characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A5D, handle = 48

Found it!
-> Client Reads CP Location Sensor: Loc#: 0 Other
Discovering Cycling Speed and Cadence (CSC) Service ... [DISC ] [SVC] Handle start = 1
bool BLEDiscovery::_discoverService(uint16_t, BLEClientService&, uint16_t): 79: verify failed, error = NRF_ERROR_BUSY
Not Found and disconnecting!
CSC Service is mandatory!
[BLE ] BLE_GATTC_EVT_READ_RSP : Conn Handle = 0
[BLE ] BLE_GAP_EVT_DISCONNECTED : Conn Handle = 0
[GAP ] Disconnect Reason: LOCAL_HOST_TERMINATED_CONNECTION
Client Disconnected, reason = 0x16

Restart the Feather nRF52 Client for a new run! <<<
Couldn't enable notify for Client CP Measurement Characteristic.
Couldn't enable indicate for Client CP Control Point Characteristic.
Couldn't enable notify for Client CSC Measurement Characteristic.
Couldn't enable notify for Client FTM Training Status Characteristic.
FTMS (trainer) is controlled by another Client (Training App)!
Client (Central) is Up and Running!

BSP Library : 1.3.0
Bootloader : s140 6.1.1
Serial No : C2BA380FAD3CBBC2

--------- SoftDevice Config ---------
Max UUID128 : 10
ATTR Table Size : 4096
Service Changed : 1
Central Connect Setting

Max MTU : 23
Event Length : 3
HVN Queue Size : 1
WrCmd Queue Size: 1

--------- BLE Settings ---------
Name : ItsyBitsy nRF52840 Express
Max Connections : Peripheral = 0, Central = 1
Address : E2:AA:F7:E9:06:E0 (Static)
TX Power : 0 dBm
Conn Intervals : min = 20.00 ms, max = 30.00 ms
Conn Timeout : 2000 ms
Central Paired Devices:

from simcline.

le-joebar commented on July 23, 2024

Test with FTMS_Client_v023 :

Feather nRF52 Client/Central: CPS, CSC and FTMS
----------------- Version 02.3 ------------------
Initialise the Bluefruit nRF52 module: Client (Central)
[CFG ] SoftDevice's RAM requires: 0x20002C78
FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
[BLE ] BLE_GAP_EVT_ADV_REPORT : Conn Handle = 65535
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000013719 F8:9C:FC:53:5E:49 -66 09-02-16-18-26-18-18-18-0A-18
[BLE ] BLE_GAP_EVT_CONNECTED : Conn Handle = 0
[GAP ] MAC = F8:9C:FC:53:5E:49, Type = 1, Resolved = 0
[GAP ] Conn Interval = 20.00 ms, Latency = 0, Supervisor Timeout = 2000 ms
[BLE ] BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST : Conn Handle = 0
[GAP ] ATT MTU is changed to 23
[BLE ] BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST : Conn Handle = 0
[GAP ] Data Length Request is (tx, rx) octets = (251, 251), (tx, rx) time = (2120, 2120) us
[BLE ] BLE_GAP_EVT_DATA_LENGTH_UPDATE : Conn Handle = 0
[GAP ] Data Length is (tx, rx) octets = (27, 27), (tx, rx) time = (1370, 1370) us
[BLE ] BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP : Conn Handle = 0
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking mandatory Client Services and Characteristics!
Discovering Client Cycling Power (CP) Service ... [DISC ] [SVC] Handle start = 1
[BLE ] BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP : Conn Handle = 0
[DISC ] [SVC] Service Count: 1
[DISC ] [SVC] Found 0x1818, Handle start = 41, end = 48

Found it! CPS Max Payload: 20 Data Length: 27
Discovering Client CP Measurement characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A63, handle = 43

[DISC ] [DESC] Handle start = 44, end = 48
[BLE ] BLE_GATTC_EVT_DESC_DISC_RSP : Conn Handle = 0
[DISC ] [DESC] Descriptor Count: 5
[DISC ] [DESC] Descriptor 0: uuid = 0x2902, handle = 44
[DISC ] [DESC] Descriptor 1: uuid = 0x2803, handle = 45
[DISC ] [DESC] Descriptor 2: uuid = 0x2A65, handle = 46
[DISC ] [DESC] Descriptor 3: uuid = 0x2803, handle = 47
[DISC ] [DESC] Descriptor 4: uuid = 0x2A5D, handle = 48
[DISC ] Found CCCD: handle = 44
Found it!
Discovering Client CP Control Point characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Handle start = 49, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 0
[DISC ] [CHR] Gatt Status = 0x0101
Not Found! NOT Mandatory!
Discovering Client CP Feature characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A65, handle = 46

Found it!
[BLE ] BLE_GATTC_EVT_READ_RSP : Conn Handle = 0
-> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ]
Wheel revolution data supported
Crank revolution data supported
Discovering Client CP Sensor Location characteristic ... [DISC ] [CHR] Handle start = 41, end = 48
[BLE ] BLE_GATTC_EVT_CHAR_DISC_RSP : Conn Handle = 0
[DISC ] [CHR] Characteristic Count: 3
[DISC ] [CHR] Found 0x2A5D, handle = 48

Restart the Feather nRF52 Client for a new run! <<<
Stopped!
BSP Library : 1.3.0
Bootloader : s140 6.1.1
Serial No : C2BA380FAD3CBBC2

--------- SoftDevice Config ---------
Max UUID128 : 10
ATTR Table Size : 4096
Service Changed : 1
Central Connect Setting

Max MTU : 23
Event Length : 3
HVN Queue Size : 1
WrCmd Queue Size: 1

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,

I have asked you before --> Please set the Debug level in the Arduino IDE to RELEASE (level 0) !! You did NOT do this...for a particular reason? Please realize that more elaborate debug levels cost processor capacity and might lead to BLE timing errors.... See above: Discovering the CSC service an error occurs: error = NRF_ERROR_BUSY ---> Busy? Doing what? Does this error also occur when you set Release level to zero at compile time ?
--------- BLE Settings --------- Name : ItsyBitsy nRF52840 Express
Did you have a particular reason why you bought this board and not the Feather nRF52840 Express that the Simcline projects use? I have no experience with the ItsyBitsy at all and nobody I know ever used it in this project....so I simply do not know if there are critical differences, that lead to unexpected results during operation and/or debugging in this stage or later.
The results are not very different from previous runs, the client detects a trainer [Zwift Hub] that advertises with CPS, CSC and FTMS... However when connected the discover actions (in the latest runs) for a mandatory service or characteristic fail at CSC. That is different from the first runs! The first runs failed when FTM was NOT detected! Does your Zwift hub not expose CSC? Is that typical for this type? Are there different types of Zwift Hubs with different specs.?
Please use nRF Connect to scan your Zwift hub when it is powered --> advertising -> connect -> detail the different services and characteristics that the hub is exposing... In previous issues (see Elite Direto) you can see how people made screen shots of screens of the nRF Connect tool and how instructive these images are!
What other devices (Treadmill(s), trainers, smartphone(s) et cetera) with BLE and/or ANT+ are present in the room that can disturb a smooth connection process.
Best wishes,
Jörgen.

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
After a night sleep.... I have made some changes in the Client software and uploaded version v024.

No longer is CSC a MANDATORY service, it is very well possible that Zwift Hub does not has it implemented... sofar we do not know! May be "nRF Connect" is giving soon better insight in what services are exposed exactly!
I have changed the order of the connect sequence (discover a service or characteristic). The sequence now starts with more general services that all BLE devices (must) have, only thereafter we check for FTMS... That is mandatory so if it fails -> end of exercise! If all goes well CPS (Mandatory) and CSC (Not Mandatory) are checked...
I hope this will give more decisive information!
Good luck,
Jörgen.

from simcline.

le-joebar commented on July 23, 2024

Dear Jörghen,

I ordered today Adafruit Feather nRF52840 Express

but there are many sites out of stock!
that's why I ordered the ItsyBitsy nRF52840 Express

Here is the first result with version V024.
At first I turn on the trainer and watch the results.
Here they are :

FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000016166 F8:9C:FC:53:5E:49 -64 09-02-16-18-26-18-18-18-0A-18
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking all Client Services and Characteristics!
If Mandatory Services Fail --> the Client will disconnect!
First checking Generic Access and Device Information Services and Characteristics!
Found Client Generic Access
-> Client Reads Device Name: [Zwift Hub]
-> Client Reads Appearance: [0]
Discovering Mandatory Client Fitness Machine (FTM) Service ... Not Found!
Disconnecting since Client FTM Service is mandatory!
Client Disconnected, reason = 0x16

Restart the Feather nRF52 Client for a new run! <<<
Stopped!

And here is the second if just after turning on I pedal to wake up the services.

This is the second result if i'm turn

Feather nRF52 Client/Central: CPS, CSC and FTMS
----------------- Version 02.4 ------------------
Initialise the Bluefruit nRF52 module: Client (Central)
FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000001764 F8:9C:FC:53:5E:49 -70 09-02-16-18-26-18-18-18-0A-18
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking all Client Services and Characteristics!
If Mandatory Services Fail --> the Client will disconnect!
First checking Generic Access and Device Information Services and Characteristics!
Found Client Generic Access
-> Client Reads Device Name: [Zwift Hub]
-> Client Reads Appearance: [1152]
Found Client Device Information
-> Client Reads Manufacturer: [Zwift]
-> Client Reads Model Number: [06]
-> Client Reads Serial Number: [06-F89CFC535E49]
Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
Discovering Client FTM Feature Characteristic ... Found it!
-> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ]
Discovering Client FTM Training Status Characteristic ... Not Found!
Disconnecting since Client FTM Characteristic is mandatory!
Client Disconnected, reason = 0x16

Restart the Feather nRF52 Client for a new run! <<<
Stopped!

Here with the V23:

Feather nRF52 Client/Central: CPS, CSC and FTMS
----------------- Version 02.3 ------------------
Initialise the Bluefruit nRF52 module: Client (Central)
FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000001160 F8:9C:FC:53:5E:49 -69 09-02-16-18-26-18-18-18-0A-18
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking mandatory Client Services and Characteristics!
Discovering Client Cycling Power (CP) Service ... Found it! CPS Max Payload: 20 Data Length: 27
Discovering Client CP Measurement characteristic ... Found it!
Discovering Client CP Control Point characteristic ... Not Found! NOT Mandatory!
Discovering Client CP Feature characteristic ... Found it!
-> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ]
Wheel revolution data supported
Crank revolution data supported
Discovering Client CP Sensor Location characteristic ... Found it!
-> Client Reads CP Location Sensor: Loc#: 0 Other
Discovering Cycling Speed and Cadence (CSC) Service ... Not Found and disconnecting!
CSC Service is mandatory!
Client Disconnected, reason = 0x16

Restart the Feather nRF52 Client for a new run! <<<
Stopped!

Here are the screenshots with nrf connect:

Sincerely,

Joel

from simcline.

le-joebar commented on July 23, 2024

I don't know if this can't help you? :
Conect nrf debug mode log

nRF Connect, 2022-12-10
Zwift Hub (F8:9C:FC:53:5E:49)
V 16:01:11.439 Connecting to F8:9C:FC:53:5E:49...
D 16:01:11.439 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 16:01:11.697 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 16:01:11.697 Connected to F8:9C:FC:53:5E:49
V 16:01:11.702 Discovering services...
D 16:01:11.702 gatt.discoverServices()
D 16:01:11.728 [Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I 16:01:12.541 Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D 16:01:15.576 [Callback] Services discovered with status: 0
I 16:01:15.577 Services discovered
V 16:01:15.615 Generic Access (0x1800)

Device Name [R W] (0x2A00)
Appearance [R] (0x2A01)
Peripheral Preferred Connection Parameters [R] (0x2A04)
Central Address Resolution [R] (0x2AA6)
Generic Attribute (0x1801)
Service Changed [I] (0x2A05)
Client Characteristic Configuration (0x2902)
Fitness Machine (0x1826)
Indoor Bike Data [N] (0x2AD2)
Client Characteristic Configuration (0x2902)
Fitness Machine Feature [R] (0x2ACC)
Supported Resistance Level Range [R] (0x2AD6)
Supported Power Range [R] (0x2AD8)
Fitness Machine Status [N] (0x2ADA)
Client Characteristic Configuration (0x2902)
Fitness Machine Control Point [I W] (0x2AD9)
Client Characteristic Configuration (0x2902)
Cycling Speed and Cadence (0x1816)
CSC Measurement [N] (0x2A5B)
Client Characteristic Configuration (0x2902)
CSC Feature [R] (0x2A5C)
Sensor Location [R] (0x2A5D)
SC Control Point [I W] (0x2A55)
Client Characteristic Configuration (0x2902)
Cycling Power (0x1818)
Cycling Power Measurement [N] (0x2A63)
Client Characteristic Configuration (0x2902)
Cycling Power Feature [R] (0x2A65)
Sensor Location [R] (0x2A5D)
Secure DFU Service (0xFE59)
Buttonless DFU [I W] (8ec90003-f315-4f60-9fb8-838830daea50)
Client Characteristic Configuration (0x2902)
Heart Rate (0x180D)
Heart Rate Measurement [N] (0x2A37)
Client Characteristic Configuration (0x2902)
Body Sensor Location [R] (0x2A38)
Unknown Service (c4630001-003f-4cec-8994-e489b04d857f)
Unknown Characteristic [R] (c4632b03-003f-4cec-8994-e489b04d857f)
Unknown Characteristic [N R] (c4632b05-003f-4cec-8994-e489b04d857f)
Client Characteristic Configuration (0x2902)
Characteristic User Description (0x2901)
Unknown Characteristic [I W] (c4632b04-003f-4cec-8994-e489b04d857f)
Client Characteristic Configuration (0x2902)
Device Information (0x180A)
Manufacturer Name String [R] (0x2A29)
Model Number String [R] (0x2A24)
Serial Number String [R] (0x2A25)
Hardware Revision String [R] (0x2A27)
Firmware Revision String [R] (0x2A26)
D 16:01:15.616 gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.621 gatt.setCharacteristicNotification(00002ad2-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.624 gatt.setCharacteristicNotification(00002ada-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.627 gatt.setCharacteristicNotification(00002ad9-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.630 gatt.setCharacteristicNotification(00002a5b-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.632 gatt.setCharacteristicNotification(00002a55-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.635 gatt.setCharacteristicNotification(00002a63-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.637 gatt.setCharacteristicNotification(00002a37-0000-1000-8000-00805f9b34fb, true)
D 16:01:15.640 gatt.setCharacteristicNotification(c4632b05-003f-4cec-8994-e489b04d857f, true)
D 16:01:15.643 gatt.setCharacteristicNotification(c4632b04-003f-4cec-8994-e489b04d857f, true)
I 16:01:15.766 Connection parameters updated (interval: 47.5ms, latency: 0, timeout: 5000ms)
I 16:01:18.099 Connection parameters updated (interval: 142.5ms, latency: 0, timeout: 4000ms)
I 16:01:51.051 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 01-94-00-00-00-B7-28
A 16:01:51.051 "Wheel rev: 148,
Last wheel event time: 10423 ms" received
I 16:01:52.035 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 01-96-00-00-00-E6-2D
A 16:01:52.035 "Wheel rev: 150,
Last wheel event time: 11750 ms" received
I 16:01:53.032 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 01-98-00-00-00-79-32
A 16:01:53.032 "Wheel rev: 152,
Last wheel event time: 12921 ms" received
I 16:01:54.032 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 01-99-00-00-00-C8-34
A 16:01:54.032 "Wheel rev: 153,
Last wheel event time: 13512 ms" received
I 16:01:54.887 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 01-9B-00-00-00-71-39
A 16:01:54.887 "Wheel rev: 155,
Last wheel event time: 14705 ms" received
I 16:01:56.023 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 03-9D-00-00-00-2F-3E-3C-00-FA-3A
A 16:01:56.023 "Wheel rev: 157,
Last wheel event time: 15919 ms,
Crank rev: 60,
Last crank event time: 15098 ms" received
I 16:01:56.883 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 03-9E-00-00-00-88-40-3D-00-C5-3F
A 16:01:56.883 "Wheel rev: 158,
Last wheel event time: 16520 ms,
Crank rev: 61,
Last crank event time: 16325 ms" received
I 16:01:57.878 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 03-A0-00-00-00-30-45-3E-00-2F-44
A 16:01:57.878 "Wheel rev: 160,
Last wheel event time: 17712 ms,
Crank rev: 62,
Last crank event time: 17455 ms" received
I 16:01:59.017 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 03-A2-00-00-00-B1-49-3F-00-7A-48
A 16:01:59.017 "Wheel rev: 162,
Last wheel event time: 18865 ms,
Crank rev: 63,
Last crank event time: 18554 ms" received
I 16:02:00.017 Notification received from 00002a5b-0000-1000-8000-00805f9b34fb, value: (0x) 03-A4-00-00-00-18-4E-40-00-b-0000-1000-8000-00805f9b34fb, value: (0x) 03-B8-00-00-00-9E-A4-49-00-

from simcline.

le-joebar commented on July 23, 2024

I found this program:
https://github.com/arduino-libraries/ArduinoBLE/blob/master/examples/Central/PeripheralExplorer/PeripheralExplorer.ino

for ESP32 BLE of which I did the test and here is the result of the services :

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0
Bluetooth�� Low Energy Central - Peripheral Explorer
Found 64:6c:58:a5:76:71 '' fe9f
Found 60:1e:b5:71:b8:93 '' fe9f
Found f8:9c:fc:53:5e:49 'Zwift Hub' 1816
Connecting ...
Connected
Discovering attributes ...
Attributes discovered

Device name: Zwift Hub
Appearance: 0x0

Service 1800
Characteristic 2a00, properties 0xA, value 0x5A7769667420487562
Descriptor 2803, value 0x020500012A
Descriptor 2a01, value 0x8004
Characteristic 2a01, properties 0x2, value 0x8004
Descriptor 2803, value 0x020700042A
Descriptor 2a04, value 0x4800780000009001
Characteristic 2a04, properties 0x2, value 0x4800780000009001
Descriptor 2803, value 0x020900A62A
Descriptor 2aa6, value 0x01
Characteristic 2aa6, properties 0x2, value 0x01
Service 1801
Characteristic 2a05, properties 0x20
Descriptor 2902, value 0x0000
Service 1826
Characteristic 2ad2, properties 0x10
Descriptor 2902, value 0x0000
Descriptor 2803, value 0x021300CC2A
Descriptor 2acc, value 0x874400000CE00000
Characteristic 2acc, properties 0x2, value 0x874400000CE00000
Descriptor 2803, value 0x021500D62A
Descriptor 2ad6, value 0x000064000100
Characteristic 2ad6, properties 0x2, value 0x000064000100
Descriptor 2803, value 0x021700D82A
Descriptor 2ad8, value 0x0000E8030100
Characteristic 2ad8, properties 0x2, value 0x0000E8030100
Descriptor 2803, value 0x101900DA2A
Descriptor 2ada, value 0x
Characteristic 2ada, properties 0x10
Descriptor 2902, value 0x0000
Descriptor 2803, value 0x281C00D92A
Descriptor 2ad9, value 0x
Characteristic 2ad9, properties 0x28
Descriptor 2902, value 0x0000
Service 1816
Characteristic 2a5b, properties 0x10
Descriptor 2902, value 0x0000
Descriptor 2803, value 0x0223005C2A
Descriptor 2a5c, value 0x0300
Characteristic 2a5c, properties 0x2, value 0x0300
Descriptor 2803, value 0x0225005D2A
Descriptor 2a5d, value 0x0C
Characteristic 2a5d, properties 0x2, value 0x0C
Descriptor 2803, value 0x282700552A
Descriptor 2a55, value 0x
Characteristic 2a55, properties 0x28
Descriptor 2902, value 0x0000
Service 1818
Characteristic 2a63, properties 0x10
Descriptor 2902, value 0x0000
Descriptor 2803, value 0x022E00652A
Descriptor 2a65, value 0x0C000000
Characteristic 2a65, properties 0x2, value 0x0C000000
Descriptor 2803, value 0x0230005D2A
Descriptor 2a5d, value 0x0C
Characteristic 2a5d, properties 0x2, value 0x0C
Service fe59
Characteristic 8ec90003-f315-4f60-9fb8-838830daea50, properties 0x28
Descriptor 2902, value 0x0000
Service 180d
Characteristic 2a37, properties 0x10
Descriptor 2902, value 0x0000
Descriptor 2803, value 0x023A00382A
Descriptor 2a38, value 0x01
Characteristic 2a38, properties 0x2, value 0x01
Service c4630001-003f-4cec-8994-e489b04d857f
Characteristic c4632b03-003f-4cec-8994-e489b04d857f, properties 0x2, value 0xFF0F0000
Descriptor 2803, value 0x123F007F854DB089E49489EC4C3F00052B63C4
Descriptor 857f, value 0x0000000000000000000000000000000000000000
Descriptor 4cec, value 0x
Descriptor 470a, value 0x
Characteristic c4632b05-003f-4cec-8994-e489b04d857f, properties 0x12, value 0x0000000000000000000000000000000000000000
Descriptor 2902, value 0x0000
Descriptor 2901, value 0x537461747573
Descriptor 2803, value 0x2843007F854DB089E49489EC4C3F00042B63C4
Descriptor 857f, value 0x
Descriptor 4cec, value 0x
Descriptor 470a, value 0x
Characteristic c4632b04-003f-4cec-8994-e489b04d857f, properties 0x28
Descriptor 2902, value 0x0000
Service 180a
Characteristic 2a29, properties 0x2, value 0x5A77696674
Descriptor 2803, value 0x024900242A
Descriptor 2a24, value 0x3036
Characteristic 2a24, properties 0x2, value 0x3036
Descriptor 2803, value 0x024B00252A
Descriptor 2a25, value 0x30362D463839434643353335453439
Characteristic 2a25, properties 0x2, value 0x30362D463839434643353335453439
Descriptor 2803, value 0x024D00272A
Descriptor 2a27, value 0x31
Characteristic 2a27, properties 0x2, value 0x31
Descriptor 2803, value 0x024F00262A
Descriptor 2a26, value 0x332E39
Characteristic 2a26, properties 0x2, value 0x332E39

Disconnecting ...
Disconnected

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
Only this Sunday morning I had time to look into your post.....
Wow! Super! That is a wealth of information!
This is more than one could have asked for, what a pity we did not start this way....
I have to study it all carefully and that will take some time!

One thing is immediately striking at my first scan:

And here is the second if just after turning on I pedal to wake up the services.

I have only met trainers that are awake all the time, may be after 20 minutes go to sleep, but never within seconds/minutes...
CPS (1818), CSC (1816) and FTMS (1826) are all present, NO DOUBT! I have to check if all the Chars are exposed and if there is a discrepancy in what the Client is instructed to be Mandatory and what the Zwift Hub is programmed with !!!
This explains definitely the behavior in all of the runs.
I will be back soon!
Thanks again, this will bring the solution!
Regards,
Jörgen.

from simcline.

Berg0162 commented on July 23, 2024

Let's give Client_FTMS version v025 a try!
I have changed several Service Characteristics to NOT Mandatory, hopefully this is now fully in accordance with the Zwift Hub settings....! (This is quite different from FTMS trainers I have met so far, but no reason for worries!)
Procedure is changed: run Feather code first and then start and wake up your trainer (we know now this is critical!)

1. Upload and Run this code on the Feather-nRF52
1. Start the Serial Monitor to catch verbose debugging and data info
1. Power ON and Wake UP trainer -> do NOT connect with other devices

Fingers crossed!

from simcline.

le-joebar commented on July 23, 2024

Dear jörghen,

Here are the results, You should know that the first attempt was a failure. The Zwift Hub is very temperamental to wake up.
On the second I had to hurry to wake him up or else I don't know what happened. But he woke up at just the right time!

Unfortunately I didn't copy everything because the serial monitor had already been closed!!!!

I'm trying to reproduce but I can't!!!

Feather nRF52 Client/Central: CPS, CSC and FTMS
----------------- Version 02.5 ------------------
Initialise the Bluefruit nRF52 module: Client (Central)
FTMS and Chars 'initialized'
CPS and Chars 'initialized'
CSCS and Chars 'initialized'
GA and Chars 'initialized'
DIS and Chars 'initialized'
Start Scanning for CPS, CSC and FTMS!
Found advertising Peripheral with FTMS service!, see the Raw Data packet:
Timestamp MAC Address Rssi Data
000021991 F8:9C:FC:53:5E:49 -69 09-02-16-18-26-18-18-18-0A-18
Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
Now checking all Client Services and Characteristics!
If Mandatory Services Fail --> the Client will disconnect!
First checking Generic Access and Device Information Services and Characteristics!
Found Client Generic Access
-> Client Reads Device Name: [Zwift Hub]
-> Client Reads Appearance: [0]
Discovering Mandatory Client Fitness Machine (FTM) Service ... Not Found!
Disconnecting since Client FTM Service is mandatory!
Client Disconnected, reason = 0x16

Restart the Feather nRF52 Client for a new run! <<<
Stopped!

15:54:24.551 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
15:54:26.523 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
15:54:26.643 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:26.643 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
15:54:28.645 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
15:54:28.694 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:28.694 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
15:54:30.682 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
15:54:30.915 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:30.915 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
15:54:32.764 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
15:54:32.888 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:32.888 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
15:54:34.867 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
15:54:35.131 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:35.131 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
15:54:36.980 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
15:54:37.072 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:37.072 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
15:54:39.043 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
15:54:39.168 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:39.168 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
15:54:41.168 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
15:54:41.261 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:41.261 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
15:54:43.265 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
15:54:43.310 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:43.310 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
15:54:45.302 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
15:54:45.361 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:45.382 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]
15:54:47.333 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 B8 FF 28 33 00 ]
15:54:47.519 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:47.519 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 B8 FF 28 33 ]
15:54:49.443 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
15:54:49.506 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:49.552 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
15:54:51.551 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A2 00 28 33 00 ]
15:54:51.627 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:51.627 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A2 00 28 33 ]
15:54:53.625 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 01 28 33 00 ]
15:54:53.658 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:53.658 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 01 28 33 ]
15:54:55.690 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 4F 01 28 33 00 ]
15:54:55.768 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:55.768 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 4F 01 28 33 ]
15:54:57.765 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 01 28 33 00 ]
15:54:58.198 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:58.198 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 01 28 33 ]
15:54:59.858 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 57 FF 28 33 00 ]
15:54:59.915 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:54:59.915 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 57 FF 28 33 ]
15:55:01.902 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 08 00 00 00 00 00 00 00 ]
15:55:02.041 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 08 03 ]
15:55:04.002 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 01 00 00 00 00 00 00 00 ]
15:55:04.081 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 01 01 ]
15:55:04.129 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 01 ]
15:55:06.110 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
15:55:06.186 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
15:55:08.190 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
15:55:08.236 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
15:55:10.225 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
15:55:10.537 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
15:55:10.537 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
15:55:12.340 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
15:55:12.466 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
15:55:12.511 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]

from simcline.

le-joebar commented on July 23, 2024

Now I managed to get the full serial but I don't know how I woke up the Zwift hub.

I can't reproduce every time!!!!

16:35:25.068 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
16:35:25.068 -> ----------------- Version 02.5 ------------------
16:35:25.068 -> Initialise the Bluefruit nRF52 module: Client (Central)
16:35:25.071 -> FTMS and Chars 'initialized'
16:35:25.071 -> CPS and Chars 'initialized'
16:35:25.071 -> CSCS and Chars 'initialized'
16:35:25.071 -> GA and Chars 'initialized'
16:35:25.071 -> DIS and Chars 'initialized'
16:35:25.071 -> Start Scanning for CPS, CSC and FTMS!
16:35:25.071 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
16:35:25.071 -> Timestamp MAC Address Rssi Data
16:35:25.071 -> 000000717 F8:9C:FC:53:5E:49 -64 09-02-16-18-26-18-18-18-0A-18
16:35:25.071 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
16:35:25.071 -> Now checking all Client Services and Characteristics!
16:35:25.071 -> If Mandatory Services Fail --> the Client will disconnect!
16:35:25.071 -> First checking Generic Access and Device Information Services and Characteristics!
16:35:25.229 -> Found Client Generic Access
16:35:25.229 -> -> Client Reads Device Name: [Zwift Hub]
16:35:25.231 -> -> Client Reads Appearance: [1152]
16:35:25.231 -> Found Client Device Information
16:35:25.242 -> -> Client Reads Manufacturer: [Zwift]
16:35:25.242 -> -> Client Reads Model Number: [06]
16:35:25.378 -> -> Client Reads Serial Number: [06-F89CFC535E49]
16:35:25.378 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
16:35:25.425 -> Discovering Client FTM Feature Characteristic ... Found it!
16:35:25.832 -> -> Client Reads Raw FTM Feature bytes: [8] [ 00 00 00 00 00 00 00 00 ]
16:35:25.832 -> Discovering Client FTM Control Point Characteristic ... Found it!
16:35:26.374 -> Discovering Client FTM Status Characteristic ... Found it!
16:35:26.374 -> Discovering Client FTM Training Status Characteristic ... Ready to receive Client FTM Control Point Response Messages
16:35:26.409 -> Ready to receive Client FTM Status values
16:35:26.409 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic.
16:35:26.409 -> >>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic.
16:35:26.409 -> >>> Couldn't enable notify for Client CP Measurement Characteristic.
16:35:26.409 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic.
16:35:26.409 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic.
16:35:26.409 -> Client (Central) is Up and Running!
16:35:26.595 -> Not Found! Not Mandatory
16:35:26.595 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
16:35:26.750 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
16:35:26.750 -> Discovering Client FTM Supported Power Range Characteristic ... Found it!
16:35:27.058 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ]
16:35:27.058 -> Discovering Client FTM Indoor Bike Data Characteristic ... Found it!
16:35:27.291 -> Discovering Client Cycling Power (CP) Service ... Found it! CPS Max Payload: 20 Data Length: 27
16:35:27.383 -> Discovering Client CP Measurement characteristic ... Found it!
16:35:27.554 -> Discovering Client CP Control Point characteristic ... Not Found! NOT Mandatory!
16:35:27.816 -> Discovering Client CP Feature characteristic ... Found it!
16:35:27.987 -> -> Client Reads Raw CP Feature bytes: [4] [ 00 00 00 00 ]
16:35:27.987 -> Discovering Client CP Sensor Location characteristic ... NOT Found! NOT Mandatory!
16:35:27.987 -> Discovering Cycling Speed and Cadence (CSC) Service ... Not Found! CSC Service is Not Mandatory!
16:35:28.391 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
16:35:28.513 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
16:35:30.519 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
16:35:30.597 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
16:35:32.596 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
16:35:32.673 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
16:35:32.673 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
16:35:34.658 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
16:35:34.734 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:34.769 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
16:35:36.711 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
16:35:36.789 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:36.789 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
16:35:38.772 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
16:35:39.099 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:39.099 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
16:35:40.880 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
16:35:40.958 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:40.958 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
16:35:42.973 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
16:35:43.066 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:43.066 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
16:35:45.077 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
16:35:45.154 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:45.154 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
16:35:47.144 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
16:35:47.470 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:47.470 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
16:35:49.244 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
16:35:49.415 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:49.415 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
16:35:51.357 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
16:35:51.481 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:51.481 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
16:35:53.451 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
16:35:53.523 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:53.523 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
16:35:55.537 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
16:35:55.583 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:55.583 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
16:35:57.562 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
16:35:57.700 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:57.700 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
16:35:59.685 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
16:35:59.809 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:35:59.809 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
16:36:01.790 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
16:36:01.931 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:36:01.931 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
16:36:03.871 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
16:36:03.948 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
16:36:03.949 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]

from simcline.

Berg0162 commented on July 23, 2024

Did you feel resistance change when moving the pedals? Op zo 11 dec. 2022 16:41 schreef le-joebar ***@***.***>:

…

Now is OK ! 16:35:25.068 -> Feather nRF52 Client/Central: CPS, CSC and FTMS 16:35:25.068 -> ----------------- Version 02.5 ------------------ 16:35:25.068 -> Initialise the Bluefruit nRF52 module: Client (Central) 16:35:25.071 -> FTMS and Chars 'initialized' 16:35:25.071 -> CPS and Chars 'initialized' 16:35:25.071 -> CSCS and Chars 'initialized' 16:35:25.071 -> GA and Chars 'initialized' 16:35:25.071 -> DIS and Chars 'initialized' 16:35:25.071 -> Start Scanning for CPS, CSC and FTMS! 16:35:25.071 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet: 16:35:25.071 -> Timestamp MAC Address Rssi Data 16:35:25.071 -> 000000717 F8:9C:FC:53:5E:49 -64 09-02-16-18-26-18-18-18-0A-18 16:35:25.071 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49 16:35:25.071 -> Now checking all Client Services and Characteristics! 16:35:25.071 -> If Mandatory Services Fail --> the Client will disconnect! 16:35:25.071 -> First checking Generic Access and Device Information Services and Characteristics! 16:35:25.229 -> Found Client Generic Access 16:35:25.229 -> -> Client Reads Device Name: [Zwift Hub] 16:35:25.231 -> -> Client Reads Appearance: [1152] 16:35:25.231 -> Found Client Device Information 16:35:25.242 -> -> Client Reads Manufacturer: [Zwift] 16:35:25.242 -> -> Client Reads Model Number: [06] 16:35:25.378 -> -> Client Reads Serial Number: [06-F89CFC535E49] 16:35:25.378 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27 16:35:25.425 -> Discovering Client FTM Feature Characteristic ... Found it! 16:35:25.832 -> -> Client Reads Raw FTM Feature bytes: [8] [ 00 00 00 00 00 00 00 00 ] 16:35:25.832 -> Discovering Client FTM Control Point Characteristic ... Found it! 16:35:26.374 -> Discovering Client FTM Status Characteristic ... Found it! 16:35:26.374 -> Discovering Client FTM Training Status Characteristic ... Ready to receive Client FTM Control Point Response Messages 16:35:26.409 -> Ready to receive Client FTM Status values 16:35:26.409 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic. 16:35:26.409 -> >>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic. 16:35:26.409 -> >>> Couldn't enable notify for Client CP Measurement Characteristic. 16:35:26.409 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic. 16:35:26.409 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic. 16:35:26.409 -> Client (Central) is Up and Running! 16:35:26.595 -> Not Found! Not Mandatory 16:35:26.595 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it! 16:35:26.750 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 16:35:26.750 -> Discovering Client FTM Supported Power Range Characteristic ... Found it! 16:35:27.058 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 16:35:27.058 -> Discovering Client FTM Indoor Bike Data Characteristic ... Found it! 16:35:27.291 -> Discovering Client Cycling Power (CP) Service ... Found it! CPS Max Payload: 20 Data Length: 27 16:35:27.383 -> Discovering Client CP Measurement characteristic ... Found it! 16:35:27.554 -> Discovering Client CP Control Point characteristic ... Not Found! NOT Mandatory! 16:35:27.816 -> Discovering Client CP Feature characteristic ... Found it! 16:35:27.987 -> -> Client Reads Raw CP Feature bytes: [4] [ 00 00 00 00 ] 16:35:27.987 -> Discovering Client CP Sensor Location characteristic ... NOT Found! NOT Mandatory! 16:35:27.987 -> Discovering Cycling Speed and Cadence (CSC) Service ... Not Found! CSC Service is Not Mandatory! 16:35:28.391 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ] 16:35:28.513 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ] 16:35:30.519 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ] 16:35:30.597 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ] 16:35:32.596 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ] 16:35:32.673 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ] 16:35:32.673 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ] 16:35:34.658 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ] 16:35:34.734 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:34.769 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ] 16:35:36.711 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ] 16:35:36.789 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:36.789 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ] 16:35:38.772 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ] 16:35:39.099 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:39.099 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ] 16:35:40.880 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ] 16:35:40.958 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:40.958 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ] 16:35:42.973 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ] 16:35:43.066 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:43.066 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ] 16:35:45.077 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ] 16:35:45.154 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:45.154 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ] 16:35:47.144 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ] 16:35:47.470 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:47.470 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ] 16:35:49.244 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ] 16:35:49.415 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:49.415 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ] 16:35:51.357 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ] 16:35:51.481 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:51.481 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ] 16:35:53.451 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ] 16:35:53.523 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:53.523 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ] 16:35:55.537 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ] 16:35:55.583 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:55.583 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ] 16:35:57.562 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ] 16:35:57.700 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:57.700 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ] 16:35:59.685 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ] 16:35:59.809 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:35:59.809 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ] 16:36:01.790 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ] 16:36:01.931 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:36:01.931 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ] 16:36:03.871 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ] 16:36:03.948 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ] 16:36:03.949 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ] — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANS5LSUED4ZI4LVDL3XRNZLWMXY23ANCNFSM6AAAAAASZDERFE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

from simcline.

le-joebar commented on July 23, 2024

At the first test I turned the pedals with my hand and I would say yes, I think it was decreasing! On the second test I did not pay attention!

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
It looks like a successful run now! Feather and Trainer are connected, services/characteristics were detected or not. Focus was until now on establishing the connection, but what I am still missing is the response of the trainer to the resistance simulation parameters that the client is regularly sending...and how these data are decoded by the Feather..... This is critical information!

Move the trainer pedals and notice/feel changes in resistance...
The Client sends Resistance Parameters to the Trainer that coincide
with the first 5 minutes of the Zwift Volcano Circuit!

Inspect the info presented by Serial Monitor.....

This is what I miss in the output: -> Client Rec'd Raw FTM Indoor Bike Data: [##] [#####################]
Have a careful look at the complete debug output file that I have uploaded and notice the comment (physical experience) at the start of the tester's output file! If you want to be sure communication is working flawless you have to do the pedaling on the bike, Zwift Hub is clearly not doing it by itself! Or it is simply NOT working.... How do we know?
See Output
Good luck!
Jörgen.

from simcline.

le-joebar commented on July 23, 2024

Hello Jorghen,

Here are the results after several connection attempts I tried several ways to connect and wake up the services.

I have never managed to do it again 2 times in a row!!!

So I don't know how to make a successful connection!!!

But we have successful results!! And I really felt the different resistances.

20:01:34.256 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
20:01:34.256 -> ----------------- Version 02.5 ------------------
20:01:34.256 -> Initialise the Bluefruit nRF52 module: Client (Central)
20:01:34.348 -> FTMS and Chars 'initialized'
20:01:34.348 -> CPS and Chars 'initialized'
20:01:34.348 -> CSCS and Chars 'initialized'
20:01:34.348 -> GA and Chars 'initialized'
20:01:34.348 -> DIS and Chars 'initialized'
20:01:34.348 -> Start Scanning for CPS, CSC and FTMS!
20:01:35.186 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
20:01:35.186 -> Timestamp MAC Address Rssi Data
20:01:35.186 -> 000002583 F8:9C:FC:53:5E:49 -69 09-02-16-18-26-18-18-18-0A-18
20:01:35.277 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
20:01:35.277 -> Now checking all Client Services and Characteristics!
20:01:35.277 -> If Mandatory Services Fail --> the Client will disconnect!
20:01:35.277 -> First checking Generic Access and Device Information Services and Characteristics!
20:01:35.494 -> Found Client Generic Access
20:01:35.494 -> -> Client Reads Device Name: [Zwift Hub]
20:01:35.815 -> -> Client Reads Appearance: [1152]
20:01:35.815 -> Found Client Device Information
20:01:36.219 -> -> Client Reads Manufacturer: [Zwift]
20:01:36.219 -> -> Client Reads Model Number: [06]
20:01:36.389 -> -> Client Reads Serial Number: [06-F89CFC535E49]
20:01:36.389 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
20:01:36.467 -> Discovering Client FTM Feature Characteristic ... Found it!
20:01:36.653 -> -> Client Reads Raw FTM Feature bytes: [8] [ 00 00 00 00 00 00 00 00 ]
20:01:36.653 -> Discovering Client FTM Control Point Characteristic ... Not Found!
20:01:36.653 -> Disconnecting since Client FTM Control Point Characteristic is mandatory!
20:01:36.699 -> Client Disconnected, reason = 0x16
20:01:36.699 -> >>> Restart the Feather nRF52 Client for a new run! <<<
20:01:37.689 -> Stopped!

20:02:38.186 -> FTMS and Chars 'initialized'
20:02:38.186 -> CPS and Chars 'initialized'
20:02:38.186 -> CSCS and Chars 'initialized'
20:02:38.186 -> GA and Chars 'initialized'
20:02:38.186 -> DIS and Chars 'initialized'
20:02:38.186 -> Start Scanning for CPS, CSC and FTMS!
20:02:38.186 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
20:02:38.186 -> Timestamp MAC Address Rssi Data
20:02:38.186 -> 000001612 F8:9C:FC:53:5E:49 -67 09-02-16-18-26-18-18-18-0A-18
20:02:38.418 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [] MAC Address: F8:9C:FC:53:5E:49
20:02:38.418 -> Now checking all Client Services and Characteristics!
20:02:38.418 -> If Mandatory Services Fail --> the Client will disconnect!
20:02:38.418 -> First checking Generic Access and Device Information Services and Characteristics!
20:02:38.418 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Not Found!
20:02:38.418 -> Disconnecting since Client FTM Service is mandatory!
20:02:38.418 -> Client Disconnected, reason = 0x3E
20:02:38.418 -> >>> Restart the Feather nRF52 Client for a new run! <<<
20:02:39.988 -> Stopped!

20:03:28.928 -> FTMS and Chars 'initialized'
20:03:28.928 -> CPS and Chars 'initialized'
20:03:28.928 -> CSCS and Chars 'initialized'
20:03:28.928 -> GA and Chars 'initialized'
20:03:28.928 -> DIS and Chars 'initialized'
20:03:28.928 -> Start Scanning for CPS, CSC and FTMS!
20:03:28.928 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
20:03:28.928 -> Timestamp MAC Address Rssi Data
20:03:28.928 -> 000001315 F8:9C:FC:53:5E:49 -67 09-02-16-18-26-18-18-18-0A-18
20:03:28.943 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [] MAC Address: F8:9C:FC:53:5E:49
20:03:28.943 -> Now checking all Client Services and Characteristics!
20:03:28.943 -> If Mandatory Services Fail --> the Client will disconnect!
20:03:28.943 -> First checking Generic Access and Device Information Services and Characteristics!
20:03:28.943 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Not Found!
20:03:28.943 -> Disconnecting since Client FTM Service is mandatory!
20:03:28.943 -> Client Disconnected, reason = 0x3E
20:03:28.943 -> >>> Restart the Feather nRF52 Client for a new run! <<<
20:03:30.705 -> Stopped!

20:15:52.131 -> ----------------- Version 02.5 ------------------
20:15:52.131 -> Initialise the Bluefruit nRF52 module: Client (Central)
20:15:52.135 -> FTMS and Chars 'initialized'
20:15:52.135 -> CPS and Chars 'initialized'
20:15:52.135 -> CSCS and Chars 'initialized'
20:15:52.135 -> GA and Chars 'initialized'
20:15:52.135 -> DIS and Chars 'initialized'
20:15:52.135 -> Start Scanning for CPS, CSC and FTMS!
20:16:41.655 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
20:16:41.655 -> Timestamp MAC Address Rssi Data
20:16:41.655 -> 000052631 F8:9C:FC:53:5E:49 -63 09-02-16-18-26-18-18-18-0A-18
20:16:41.870 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
20:16:41.870 -> Now checking all Client Services and Characteristics!
20:16:41.870 -> If Mandatory Services Fail --> the Client will disconnect!
20:16:41.870 -> First checking Generic Access and Device Information Services and Characteristics!
20:16:42.087 -> Found Client Generic Access
20:16:42.087 -> -> Client Reads Device Name: [Zwift Hub]
20:16:42.351 -> -> Client Reads Appearance: [1152]
20:16:42.351 -> Found Client Device Information
20:16:42.816 -> -> Client Reads Manufacturer: [Zwift]
20:16:42.816 -> -> Client Reads Model Number: [06]
20:16:42.986 -> -> Client Reads Serial Number: [06-F89CFC535E49]
20:16:42.987 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
20:16:43.112 -> Discovering Client FTM Feature Characteristic ... Found it!
20:16:43.249 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ]
20:16:43.249 -> Discovering Client FTM Control Point Characteristic ... Found it!
20:16:43.974 -> Discovering Client FTM Status Characteristic ... Found it!
20:16:43.974 -> Discovering Client FTM Training Status Characteristic ... Ready to receive Client FTM Control Point Response Messages
20:16:44.310 -> Ready to receive Client FTM Status values
20:16:44.310 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic.
20:16:44.310 -> >>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic.
20:16:44.310 -> >>> Couldn't enable notify for Client CP Measurement Characteristic.
20:16:44.310 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic.
20:16:44.310 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic.
20:16:44.310 -> Client (Central) is Up and Running!
20:16:44.346 -> Not Found! Not Mandatory
20:16:44.346 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
20:16:44.516 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
20:16:44.516 -> Discovering Client FTM Supported Power Range Characteristic ... Found it!
20:16:44.870 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ]
20:16:44.870 -> Discovering Client FTM Indoor Bike Data Characteristic ... Found it!
20:16:45.056 -> Discovering Client Cycling Power (CP) Service ... Found it! CPS Max Payload: 20 Data Length: 27
20:16:45.149 -> Discovering Client CP Measurement characteristic ... Found it!
20:16:45.334 -> Discovering Client CP Control Point characteristic ... Not Found! NOT Mandatory!
20:16:45.569 -> Discovering Client CP Feature characteristic ... Found it!
20:16:45.752 -> -> Client Reads Raw CP Feature bytes: [4] [ 00 00 00 00 ]
20:16:45.752 -> Discovering Client CP Sensor Location characteristic ... NOT Found! NOT Mandatory!
20:16:45.752 -> Discovering Cycling Speed and Cadence (CSC) Service ... Not Found! CSC Service is Not Mandatory!
20:16:46.309 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:16:46.401 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:16:48.356 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:16:48.450 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:16:50.443 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
20:16:50.475 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
20:16:50.475 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
20:16:52.514 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
20:16:52.546 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:16:52.546 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
20:16:54.573 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
20:16:54.757 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:16:54.803 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
20:16:56.652 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:16:56.839 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:16:56.839 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:16:58.772 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
20:16:58.943 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:16:58.943 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
20:17:00.869 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
20:17:00.961 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:00.961 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
20:17:02.957 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
20:17:03.052 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:03.052 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
20:17:05.040 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
20:17:05.072 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:05.072 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
20:17:07.112 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
20:17:07.342 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:07.342 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
20:17:09.211 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
20:17:09.289 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:09.289 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
20:17:11.266 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:17:11.360 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:11.360 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:17:13.362 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
20:17:13.473 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:13.473 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
20:17:15.452 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
20:17:15.545 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:15.545 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
20:17:17.539 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
20:17:17.571 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:17.571 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
20:17:19.604 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
20:17:19.715 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:19.715 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
20:17:21.694 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
20:17:21.834 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:21.834 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
20:17:23.799 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
20:17:24.109 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:24.109 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
20:17:25.913 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
20:17:26.007 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:26.007 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
20:17:28.006 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
20:17:28.053 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:28.053 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
20:17:30.047 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
20:17:30.111 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:30.111 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
20:17:32.153 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
20:17:32.230 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:32.230 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]
20:17:34.207 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 B8 FF 28 33 00 ]
20:17:34.377 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:34.377 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 B8 FF 28 33 ]
20:17:36.308 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:17:36.433 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:36.433 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:17:38.431 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A2 00 28 33 00 ]
20:17:38.510 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:38.510 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A2 00 28 33 ]
20:17:40.534 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 01 28 33 00 ]
20:17:40.643 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:40.643 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 01 28 33 ]
20:17:42.606 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 4F 01 28 33 00 ]
20:17:42.682 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:42.682 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 4F 01 28 33 ]
20:17:44.682 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 01 28 33 00 ]
20:17:44.852 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:44.852 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 01 28 33 ]
20:17:46.768 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 57 FF 28 33 00 ]
20:17:46.845 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:46.845 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 57 FF 28 33 ]
20:17:48.847 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 08 00 00 00 00 00 00 00 ]
20:17:49.112 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 08 03 ]
20:17:50.939 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 01 00 00 00 00 00 00 00 ]
20:17:51.063 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 01 01 ]
20:17:51.063 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 01 ]
20:17:53.041 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:17:53.088 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:17:55.102 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:17:55.195 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:17:57.185 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
20:17:57.510 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
20:17:57.510 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
20:17:59.284 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
20:17:59.331 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:17:59.331 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
20:18:01.351 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
20:18:01.567 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:01.567 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
20:18:03.450 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:18:03.528 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:03.528 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:18:05.512 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
20:18:05.590 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:05.590 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
20:18:07.627 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
20:18:07.673 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:07.673 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
20:18:09.683 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
20:18:09.730 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:09.730 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
20:18:11.708 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
20:18:11.802 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:11.802 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
20:18:13.746 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
20:18:14.072 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:14.072 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
20:18:15.867 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
20:18:15.945 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:15.945 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
20:18:17.918 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:18:18.089 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:18.089 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:18:20.050 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
20:18:20.096 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:20.096 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
20:18:22.115 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
20:18:22.207 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:22.207 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
20:18:24.202 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
20:18:24.249 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:24.249 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
20:18:26.259 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
20:18:26.508 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:26.508 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
20:18:28.349 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
20:18:28.551 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:28.551 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
20:18:30.463 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
20:18:30.604 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:30.604 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
20:18:32.565 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
20:18:32.643 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:32.643 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
20:18:34.646 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
20:18:34.678 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:34.678 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
20:18:36.693 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
20:18:36.769 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:36.769 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
20:18:38.750 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
20:18:39.060 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:39.060 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]
20:18:40.868 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 B8 FF 28 33 00 ]
20:18:41.054 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:41.054 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 B8 FF 28 33 ]
20:18:42.968 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:18:43.187 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:43.187 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:18:45.072 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A2 00 28 33 00 ]
20:18:45.149 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:45.149 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A2 00 28 33 ]
20:18:47.124 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 01 28 33 00 ]
20:18:47.248 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:47.248 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 01 28 33 ]
20:18:49.238 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 4F 01 28 33 00 ]
20:18:49.332 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:49.332 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 4F 01 28 33 ]
20:18:51.311 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 01 28 33 00 ]
20:18:51.452 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:51.452 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 01 28 33 ]
20:18:53.427 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 57 FF 28 33 00 ]
20:18:53.613 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:18:53.613 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 57 FF 28 33 ]
20:18:55.519 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 08 00 00 00 00 00 00 00 ]
20:18:55.550 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 08 03 ]
20:18:57.571 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 01 00 00 00 00 00 00 00 ]
20:18:57.681 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 01 01 ]
20:18:57.681 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 01 ]
20:18:59.669 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:18:59.747 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:19:01.734 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:19:01.827 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:19:03.840 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
20:19:04.105 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
20:19:04.105 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
20:19:05.947 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
20:19:06.116 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:06.116 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
20:19:08.042 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
20:19:08.165 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:08.165 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
20:19:10.145 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:19:10.208 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:10.253 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:19:12.243 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
20:19:12.321 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:12.321 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
20:19:14.328 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
20:19:14.406 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:14.406 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
20:19:16.397 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
20:19:16.429 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:16.429 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
20:19:18.464 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
20:19:18.541 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:18.541 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
20:19:20.534 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
20:19:20.783 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:20.783 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
20:19:22.653 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
20:19:22.775 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:22.775 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
20:19:24.753 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:19:24.831 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:24.831 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:19:26.832 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
20:19:26.971 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:26.971 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
20:19:28.926 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
20:19:29.097 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:29.097 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
20:19:31.013 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
20:19:31.106 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:31.106 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
20:19:33.127 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
20:19:33.329 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:33.329 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
20:19:35.219 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
20:19:35.265 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:35.265 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
20:19:37.278 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
20:19:37.356 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:37.356 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
20:19:39.354 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
20:19:39.433 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:39.433 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
20:19:41.425 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
20:19:41.457 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:41.457 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
20:19:43.492 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
20:19:43.723 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:43.723 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
20:19:45.581 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
20:19:45.750 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:45.750 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]
20:19:47.678 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 B8 FF 28 33 00 ]
20:19:47.818 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:47.818 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 B8 FF 28 33 ]
20:19:49.788 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:19:49.865 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:49.865 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:19:51.859 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A2 00 28 33 00 ]
20:19:51.950 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:51.950 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A2 00 28 33 ]
20:19:53.940 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 01 28 33 00 ]
20:19:54.033 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:54.033 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 01 28 33 ]
20:19:56.027 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 4F 01 28 33 00 ]
20:19:56.462 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:56.462 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 4F 01 28 33 ]
20:19:58.105 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 01 28 33 00 ]
20:19:58.275 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:19:58.322 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 01 28 33 ]
20:20:00.213 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 57 FF 28 33 00 ]
20:20:00.290 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:00.337 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 57 FF 28 33 ]
20:20:02.267 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 08 00 00 00 00 00 00 00 ]
20:20:02.360 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 08 03 ]
20:20:04.371 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 01 00 00 00 00 00 00 00 ]
20:20:04.417 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 01 01 ]
20:20:04.417 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 01 ]
20:20:06.425 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:20:06.457 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:20:08.481 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
20:20:08.527 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
20:20:10.546 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
20:20:10.624 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
20:20:10.624 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
20:20:12.620 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
20:20:12.698 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:12.698 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
20:20:14.712 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
20:20:14.806 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:14.806 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
20:20:16.785 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:20:16.862 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:16.862 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:20:18.871 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
20:20:18.980 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:18.980 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
20:20:20.978 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
20:20:21.070 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:21.070 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
20:20:23.027 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
20:20:23.396 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:23.396 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
20:20:25.145 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
20:20:25.223 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:25.223 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
20:20:27.225 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
20:20:27.365 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:27.365 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
20:20:29.329 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
20:20:29.376 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:29.376 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
20:20:31.379 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
20:20:31.469 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:31.469 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
20:20:33.446 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
20:20:33.569 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:33.569 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
20:20:35.559 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
20:20:35.591 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:35.591 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
20:20:37.619 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
20:20:37.852 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:37.852 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
20:20:39.714 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
20:20:39.977 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:39.977 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
20:20:41.827 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
20:20:41.966 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:41.966 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
20:20:43.925 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
20:20:43.973 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:43.973 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
20:20:45.950 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
20:20:46.091 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:46.091 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
20:20:48.091 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
20:20:48.138 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:48.138 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
20:20:50.141 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
20:20:50.188 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:50.188 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
20:20:52.205 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
20:20:52.513 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
20:20:52.513 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]

Thanks,

Joel

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
This is different from how the Elite Direto is responding, but that seems not to be a problem since you experience changing resistance.
I have uploaded a new version that hopefully accounts for the slightly different timing of the itsybitsy.. (???) and should avoid message cluttering during connection phase.
Furthermore I have introduced a Request for Machine Control in an early stage of the connection procedure, may be this helps waking up your trainer....
Best wishes,
Jörgen.

from simcline.

le-joebar commented on July 23, 2024

Hello Jorghen,

I ordered the Feather but it hasn't arrived yet.

I had also started modifying the FTMS_Client_V25 to wait for feedback from everyone's services.

So I'm going to stop and try V.26 tonight.
I'll get back to you with the results.

I received the Bluethoot BLE dongle and tested the FTMS_Server_V.22.
It works so my key is good for the future.

Friendship
Joel,

from simcline.

le-joebar commented on July 23, 2024

I looked at your version V.26
I saw you change the time from 2.5 seconds to 5.
Personally I was looking at a different solution which consisted of:
Example:
if ( client_FitnessMachine_Service.discover(conn_handle) )
If false to restart the complete request and this for all the services which must answer!
I don't know if this is the right solution but its a lot of work.
if ( client_FitnessMachine_Service.discover(conn_handle) )
If False to restart the complete request and this for all the services that must respond!
I don't know if this is the right solution but its a lot of work.

from simcline.

le-joebar commented on July 23, 2024

Hello Jörghen,

Here are the results:
Unfortunately V0.26 does not work better than the others.
Here is the result of V0.25 modified by me.

And the code below

18:07:13.207 -> GA and Chars 'initialized'
18:07:13.207 -> DIS and Chars 'initialized'
18:07:13.207 -> Start Scanning for CPS, CSC and FTMS!
18:07:13.207 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
18:07:13.207 -> Timestamp MAC Address Rssi Data
18:07:13.207 -> 000001374 F8:9C:FC:53:5E:49 -62 09-02-16-18-26-18-18-18-0A-18
18:07:13.207 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
18:07:13.207 -> Now checking all Client Services and Characteristics!
18:07:13.207 -> If Mandatory Services Fail --> the Client will disconnect!
18:07:13.207 -> First checking Generic Access and Device Information Services and Characteristics!
18:07:13.461 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
18:07:13.461 -> Discovering Client FTM Feature Characteristic ... Discovering Client FTM Control Point Characteristic ... Found it!
18:07:14.047 -> Discovering Client FTM Status Characteristic ... Found it!
18:07:14.601 -> Discovering Client FTM Training Status Characteristic ... Not Found! Not Mandatory
18:07:14.864 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
18:07:15.220 -> Ready to receive Client FTM Control Point Response Messages
18:07:15.267 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
18:07:15.267 -> Discovering Client FTM Supported Power Range Characteristic ... Ready to receive Client FTM Status values
18:07:15.267 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic.
18:07:15.267 -> >>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic.
18:07:15.267 -> >>> Couldn't enable notify for Client CP Measurement Characteristic.
18:07:15.267 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic.
18:07:15.267 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic.
18:07:15.267 -> Client (Central) is Up and Running!
18:07:15.392 -> Found it!
18:07:15.484 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 00 00 00 00 ]
18:07:15.484 -> Discovering Client FTM Indoor Bike Data Characteristic ... Not Found! Not Mandatory
18:07:15.484 -> Discovering Client Cycling Power (CP) Service ... Not Found!
18:07:15.484 -> Disconnecting since Client Cyling Power Service is mandatory!
18:07:15.531 -> Client Disconnected, reason = 0x16
18:07:15.531 -> >>> Restart the Feather nRF52 Client for a new run! <<<
18:07:26.723 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
18:07:26.723 -> ----------------- Version 02.5 ------------------
18:07:26.723 -> Initialise the Bluefruit nRF52 module: Client (Central)
18:07:26.724 -> FTMS and Chars 'initialized'
18:07:26.724 -> CPS and Chars 'initialized'
18:07:26.724 -> CSCS and Chars 'initialized'
18:07:26.724 -> GA and Chars 'initialized'
18:07:26.724 -> DIS and Chars 'initialized'
18:07:26.724 -> Start Scanning for CPS, CSC and FTMS!
18:07:26.724 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
18:07:26.724 -> Timestamp MAC Address Rssi Data
18:07:26.724 -> 000001192 F8:9C:FC:53:5E:49 -62 09-02-16-18-26-18-18-18-0A-18
18:07:26.743 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
18:07:26.743 -> Now checking all Client Services and Characteristics!
18:07:26.743 -> If Mandatory Services Fail --> the Client will disconnect!
18:07:26.743 -> First checking Generic Access and Device Information Services and Characteristics!
18:07:26.747 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
18:07:26.747 -> Discovering Client FTM Feature Characteristic ... Discovering Client FTM Control Point Characteristic ... Found it!
18:07:27.137 -> Discovering Client FTM Status Characteristic ... Found it!
18:07:27.555 -> Discovering Client FTM Training Status Characteristic ... Not Found! Not Mandatory
18:07:27.912 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
18:07:28.129 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
18:07:28.129 -> Discovering Client FTM Supported Power Range Characteristic ... Found it!
18:07:28.346 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ]
18:07:28.346 -> Discovering Client FTM Indoor Bike Data Characteristic ... Found it!
18:07:28.639 -> Discovering Client Cycling Power (CP) Service ... Ready to receive Client FTM Control Point Response Messages
18:07:28.731 -> Found it! CPS Max Payload: 20 Data Length: 27
18:07:28.731 -> Discovering Client CP Measurement characteristic ... Ready to receive Client FTM Status values
18:07:28.731 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic.
18:07:28.809 -> Ready to receive Client FTM Indoor Bike Data values
18:07:28.809 -> Found it!
18:07:28.809 -> Discovering Client CP Control Point characteristic ... Ready to receive Client CP Measurement values
18:07:28.809 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic.
18:07:28.809 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic.
18:07:28.809 -> Client (Central) is Up and Running!
18:07:28.932 -> Not Found! NOT Mandatory!
18:07:28.932 -> Discovering Client CP Feature characteristic ... Found it!
18:07:29.446 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ]
18:07:29.446 -> Wheel revolution data supported
18:07:29.446 -> Crank revolution data supported
18:07:29.446 -> Discovering Client CP Sensor Location characteristic ... Found it!
18:07:29.646 -> -> Client Reads CP Location Sensor: Loc#: 0 Other
18:07:29.646 -> Discovering Cycling Speed and Cadence (CSC) Service ... Not Found! CSC Service is Not Mandatory!
18:07:29.646 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:29.646 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:30.031 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:30.031 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:30.819 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:07:30.864 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:07:31.036 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:31.036 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:32.006 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:32.006 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:32.870 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:07:32.916 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:07:33.195 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:33.195 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:34.074 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:34.074 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:34.925 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
18:07:35.266 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 00 00 00 00 14 00 00 00 00 ]
18:07:35.266 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:07:35.313 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
18:07:35.313 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
18:07:36.008 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:36.008 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:37.011 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:37.011 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:37.011 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
18:07:37.213 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:37.213 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
18:07:37.972 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:38.018 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:38.984 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:38.984 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:39.110 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
18:07:39.188 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:39.188 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
18:07:39.989 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:39.989 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:41.147 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:41.147 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:41.193 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:07:41.286 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:41.286 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:07:41.978 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 00 00 00 ]
18:07:41.978 -> Speed: 0 KPH Instantaneous Cadence: 0 RPM Average Cadence: 0 RPM Total Distance: 0 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:07:43.072 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 09 05 88 00 00 00 00 00 03 00 00 14 00 78 00 0F 00 00 ]
18:07:43.072 -> Speed: 12 KPH Instantaneous Cadence: 68 RPM Average Cadence: 0 RPM Total Distance: 196608 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 120 Watt Heart Rate: 15 HBM
18:07:43.289 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
18:07:43.321 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:43.321 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
18:07:44.015 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A3 06 1A 01 00 00 00 00 07 00 00 14 00 D5 00 25 00 00 ]
18:07:44.015 -> Speed: 16 KPH Instantaneous Cadence: 141 RPM Average Cadence: 0 RPM Total Distance: 458752 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 213 Watt Heart Rate: 37 HBM
18:07:45.252 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 B5 06 8F 01 00 00 00 00 0B 00 00 14 00 91 00 2F 00 00 ]
18:07:45.252 -> Speed: 17 KPH Instantaneous Cadence: 199 RPM Average Cadence: 0 RPM Total Distance: 720896 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 145 Watt Heart Rate: 47 HBM
18:07:45.344 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
18:07:45.390 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:45.390 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
18:07:46.008 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 15 07 EF 01 36 00 04 00 0F 00 00 14 00 BE 00 3C 00 00 ]
18:07:46.008 -> Speed: 18 KPH Instantaneous Cadence: 247 RPM Average Cadence: 27 RPM Total Distance: 983044 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 190 Watt Heart Rate: 60 HBM
18:07:46.999 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 B4 07 5D 02 56 00 0B 00 14 00 00 14 00 C5 00 48 00 00 ]
18:07:46.999 -> Speed: 19 KPH Instantaneous Cadence: 302 RPM Average Cadence: 43 RPM Total Distance: 1310731 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 197 Watt Heart Rate: 72 HBM
18:07:47.416 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
18:07:47.667 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:47.667 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
18:07:48.011 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 15 08 BA 02 66 00 12 00 19 00 00 14 00 A4 00 4F 00 00 ]
18:07:48.011 -> Speed: 20 KPH Instantaneous Cadence: 349 RPM Average Cadence: 51 RPM Total Distance: 1638418 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 164 Watt Heart Rate: 79 HBM
18:07:49.075 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 6C 08 09 03 70 00 19 00 1E 00 00 14 00 9D 00 54 00 00 ]
18:07:49.075 -> Speed: 21 KPH Instantaneous Cadence: 388 RPM Average Cadence: 56 RPM Total Distance: 1966105 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 157 Watt Heart Rate: 84 HBM
18:07:49.490 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
18:07:49.568 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:49.568 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
18:07:50.015 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 C7 08 67 03 76 00 1F 00 24 00 00 14 00 99 00 59 00 00 ]
18:07:50.015 -> Speed: 22 KPH Instantaneous Cadence: 435 RPM Average Cadence: 59 RPM Total Distance: 2359327 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 153 Watt Heart Rate: 89 HBM
18:07:51.031 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 4D 09 B8 03 7A 00 25 00 2A 00 00 14 00 8E 00 5C 00 00 ]
18:07:51.031 -> Speed: 23 KPH Instantaneous Cadence: 476 RPM Average Cadence: 61 RPM Total Distance: 2752549 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 142 Watt Heart Rate: 92 HBM
18:07:51.570 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
18:07:51.849 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:51.849 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
18:07:51.973 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 70 09 00 04 80 00 2A 00 30 00 00 14 00 89 00 5F 00 00 ]
18:07:51.973 -> Speed: 24 KPH Instantaneous Cadence: 512 RPM Average Cadence: 64 RPM Total Distance: 3145770 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 137 Watt Heart Rate: 95 HBM
18:07:52.992 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 5E 09 40 04 86 00 2F 00 36 00 00 14 00 85 00 61 00 00 ]
18:07:52.992 -> Speed: 23 KPH Instantaneous Cadence: 544 RPM Average Cadence: 67 RPM Total Distance: 3538991 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 133 Watt Heart Rate: 97 HBM
18:07:53.670 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
18:07:53.748 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:53.748 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
18:07:53.978 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 65 09 7A 04 88 00 34 00 3C 00 00 14 00 78 00 62 00 00 ]
18:07:53.978 -> Speed: 24 KPH Instantaneous Cadence: 573 RPM Average Cadence: 68 RPM Total Distance: 3932212 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 120 Watt Heart Rate: 98 HBM
18:07:54.980 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 87 09 AD 04 8A 00 38 00 42 00 00 14 00 70 00 63 00 00 ]
18:07:54.980 -> Speed: 24 KPH Instantaneous Cadence: 598 RPM Average Cadence: 69 RPM Total Distance: 4325432 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 112 Watt Heart Rate: 99 HBM
18:07:55.749 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:07:55.886 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:55.886 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:07:56.009 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 5E 09 DC 04 8A 00 3C 00 48 00 00 14 00 5D 00 62 00 00 ]
18:07:56.009 -> Speed: 23 KPH Instantaneous Cadence: 622 RPM Average Cadence: 69 RPM Total Distance: 4718652 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 93 Watt Heart Rate: 98 HBM
18:07:57.015 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A8 09 06 05 8C 00 40 00 4E 00 00 14 00 70 00 63 00 00 ]
18:07:57.015 -> Speed: 24 KPH Instantaneous Cadence: 643 RPM Average Cadence: 70 RPM Total Distance: 5111872 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 112 Watt Heart Rate: 99 HBM
18:07:57.849 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
18:07:57.927 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:57.927 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
18:07:57.974 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 0A 3D 05 8C 00 43 00 55 00 00 14 00 74 00 64 00 00 ]
18:07:57.974 -> Speed: 25 KPH Instantaneous Cadence: 670 RPM Average Cadence: 70 RPM Total Distance: 5570627 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 116 Watt Heart Rate: 100 HBM
18:07:59.038 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 D4 09 60 05 90 00 46 00 5B 00 00 14 00 7D 00 65 00 00 ]
18:07:59.038 -> Speed: 25 KPH Instantaneous Cadence: 688 RPM Average Cadence: 72 RPM Total Distance: 5963846 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 125 Watt Heart Rate: 101 HBM
18:07:59.950 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
18:07:59.997 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:07:59.997 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
18:07:59.997 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 23 0A 8E 05 92 00 49 00 62 00 00 14 00 75 00 65 00 00 ]
18:07:59.997 -> Speed: 25 KPH Instantaneous Cadence: 711 RPM Average Cadence: 73 RPM Total Distance: 6422601 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 117 Watt Heart Rate: 101 HBM
18:08:01.066 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 0D 0A B9 05 92 00 4C 00 69 00 00 14 00 6B 00 66 00 00 ]
18:08:01.066 -> Speed: 25 KPH Instantaneous Cadence: 732 RPM Average Cadence: 73 RPM Total Distance: 6881356 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 107 Watt Heart Rate: 102 HBM
18:08:01.990 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 4F 0A E1 05 94 00 4E 00 70 00 00 14 00 6C 00 66 00 00 ]
18:08:01.990 -> Speed: 26 KPH Instantaneous Cadence: 752 RPM Average Cadence: 74 RPM Total Distance: 7340110 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 108 Watt Heart Rate: 102 HBM
18:08:01.990 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
18:08:02.113 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:02.113 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
18:08:02.993 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 28 0A 06 06 94 00 51 00 77 00 00 14 00 63 00 66 00 00 ]
18:08:02.993 -> Speed: 26 KPH Instantaneous Cadence: 771 RPM Average Cadence: 74 RPM Total Distance: 7798865 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 99 Watt Heart Rate: 102 HBM
18:08:04.087 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
18:08:04.211 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 62 0A 28 06 98 00 53 00 7E 00 00 14 00 5A 00 65 00 00 ]
18:08:04.211 -> Speed: 26 KPH Instantaneous Cadence: 788 RPM Average Cadence: 76 RPM Total Distance: 8257619 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 90 Watt Heart Rate: 101 HBM
18:08:04.303 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:04.303 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
18:08:04.996 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 2E 0A 48 06 96 00 56 00 85 00 00 14 00 51 00 65 00 00 ]
18:08:04.996 -> Speed: 26 KPH Instantaneous Cadence: 804 RPM Average Cadence: 75 RPM Total Distance: 8716374 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 81 Watt Heart Rate: 101 HBM
18:08:06.088 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 AF 0A 66 06 96 00 58 00 8C 00 00 14 00 52 00 64 00 00 ]
18:08:06.088 -> Speed: 27 KPH Instantaneous Cadence: 819 RPM Average Cadence: 75 RPM Total Distance: 9175128 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 82 Watt Heart Rate: 100 HBM
18:08:06.181 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
18:08:06.303 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:06.303 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
18:08:06.995 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 9B 0A 83 06 A0 00 5A 00 93 00 00 14 00 64 00 64 00 00 ]
18:08:06.995 -> Speed: 27 KPH Instantaneous Cadence: 833 RPM Average Cadence: 80 RPM Total Distance: 9633882 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 100 Watt Heart Rate: 100 HBM
18:08:08.181 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 CA 0A 9D 06 A6 00 5C 00 9A 00 00 14 00 61 00 64 00 00 ]
18:08:08.182 -> Speed: 27 KPH Instantaneous Cadence: 846 RPM Average Cadence: 83 RPM Total Distance: 10092636 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 97 Watt Heart Rate: 100 HBM
18:08:08.274 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
18:08:08.412 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:08.412 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
18:08:08.999 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 0D 0B B6 06 A6 00 5E 00 A1 00 00 14 00 5E 00 64 00 00 ]
18:08:08.999 -> Speed: 28 KPH Instantaneous Cadence: 859 RPM Average Cadence: 83 RPM Total Distance: 10551390 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 94 Watt Heart Rate: 100 HBM
18:08:10.090 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 0E 0B CD 06 A2 00 60 00 A8 00 00 14 00 51 00 63 00 00 ]
18:08:10.138 -> Speed: 28 KPH Instantaneous Cadence: 870 RPM Average Cadence: 81 RPM Total Distance: 11010144 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 81 Watt Heart Rate: 99 HBM
18:08:10.373 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
18:08:10.451 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:10.451 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
18:08:11.013 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 39 0B E4 06 A6 00 62 00 AF 00 00 14 00 58 00 63 00 00 ]
18:08:11.013 -> Speed: 28 KPH Instantaneous Cadence: 882 RPM Average Cadence: 83 RPM Total Distance: 11468898 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 88 Watt Heart Rate: 99 HBM
18:08:11.978 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 6C 0B 02 07 A6 00 64 00 B7 00 00 14 00 50 00 62 00 00 ]
18:08:11.978 -> Speed: 29 KPH Instantaneous Cadence: 897 RPM Average Cadence: 83 RPM Total Distance: 11993188 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 80 Watt Heart Rate: 98 HBM
18:08:12.432 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
18:08:12.668 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:12.668 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
18:08:12.992 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 70 0B 20 07 AA 00 66 00 BF 00 00 14 00 4D 00 62 00 00 ]
18:08:12.993 -> Speed: 29 KPH Instantaneous Cadence: 912 RPM Average Cadence: 85 RPM Total Distance: 12517478 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 77 Watt Heart Rate: 98 HBM
18:08:13.995 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 B7 0B 3B 07 AE 00 68 00 C7 00 00 14 00 50 00 61 00 00 ]
18:08:13.995 -> Speed: 29 KPH Instantaneous Cadence: 925 RPM Average Cadence: 87 RPM Total Distance: 13041768 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 80 Watt Heart Rate: 97 HBM
18:08:14.550 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 6F FF 28 33 00 ]
18:08:14.768 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:14.768 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 6F FF 28 33 ]
18:08:14.984 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A3 0B 56 07 B2 00 6A 00 CF 00 00 14 00 4C 00 61 00 00 ]
18:08:14.984 -> Speed: 29 KPH Instantaneous Cadence: 939 RPM Average Cadence: 89 RPM Total Distance: 13566058 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 76 Watt Heart Rate: 97 HBM
18:08:16.182 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 81 0B 6F 07 BA 00 6B 00 D7 00 00 14 00 39 00 60 00 00 ]
18:08:16.182 -> Speed: 29 KPH Instantaneous Cadence: 951 RPM Average Cadence: 93 RPM Total Distance: 14090347 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 57 Watt Heart Rate: 96 HBM
18:08:16.631 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 8A FF 28 33 00 ]
18:08:16.709 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:16.709 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 8A FF 28 33 ]
18:08:17.003 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 9F 0B 86 07 BC 00 6D 00 DF 00 00 14 00 42 00 5F 00 00 ]
18:08:17.003 -> Speed: 29 KPH Instantaneous Cadence: 963 RPM Average Cadence: 94 RPM Total Distance: 14614637 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 66 Watt Heart Rate: 95 HBM
18:08:18.191 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A0 0B 9D 07 BE 00 6F 00 E7 00 00 14 00 41 00 5E 00 00 ]
18:08:18.191 -> Speed: 29 KPH Instantaneous Cadence: 974 RPM Average Cadence: 95 RPM Total Distance: 15138927 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 65 Watt Heart Rate: 94 HBM
18:08:18.671 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 B8 FF 28 33 00 ]
18:08:18.794 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:18.794 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 B8 FF 28 33 ]
18:08:18.980 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 C3 0B B3 07 B6 00 71 00 EF 00 00 14 00 4E 00 5E 00 00 ]
18:08:18.980 -> Speed: 30 KPH Instantaneous Cadence: 985 RPM Average Cadence: 91 RPM Total Distance: 15663217 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 78 Watt Heart Rate: 94 HBM
18:08:20.077 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 99 0B C7 07 B2 00 72 00 F7 00 00 14 00 46 00 5D 00 00 ]
18:08:20.077 -> Speed: 29 KPH Instantaneous Cadence: 995 RPM Average Cadence: 89 RPM Total Distance: 16187506 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 70 Watt Heart Rate: 93 HBM
18:08:20.803 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:08:20.835 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:20.835 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:08:20.973 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 89 0B DB 07 B2 00 74 00 FF 00 00 14 00 47 00 5D 00 00 ]
18:08:20.973 -> Speed: 29 KPH Instantaneous Cadence: 1005 RPM Average Cadence: 89 RPM Total Distance: 16711796 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 71 Watt Heart Rate: 93 HBM
18:08:22.098 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 48 0B E6 07 AE 00 75 00 06 01 00 14 00 47 00 5C 00 00 ]
18:08:22.098 -> Speed: 28 KPH Instantaneous Cadence: 1011 RPM Average Cadence: 87 RPM Total Distance: 393333 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 71 Watt Heart Rate: 92 HBM
18:08:22.867 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A2 00 28 33 00 ]
18:08:22.913 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:22.913 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A2 00 28 33 ]
18:08:23.039 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 42 0B F1 07 B0 00 76 00 0D 01 00 14 00 59 00 5C 00 00 ]
18:08:23.039 -> Speed: 28 KPH Instantaneous Cadence: 1016 RPM Average Cadence: 88 RPM Total Distance: 852086 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 89 Watt Heart Rate: 92 HBM
18:08:24.006 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 0E 0B FC 07 AA 00 77 00 14 01 00 14 00 5F 00 5C 00 00 ]
18:08:24.006 -> Speed: 28 KPH Instantaneous Cadence: 1022 RPM Average Cadence: 85 RPM Total Distance: 1310839 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 95 Watt Heart Rate: 92 HBM
18:08:24.918 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 01 28 33 00 ]
18:08:25.012 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:25.012 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 01 28 33 ]
18:08:25.012 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 C9 0A 05 08 96 00 78 00 1B 01 00 14 00 70 00 5D 00 00 ]
18:08:25.012 -> Speed: 27 KPH Instantaneous Cadence: 1026 RPM Average Cadence: 75 RPM Total Distance: 1769592 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 112 Watt Heart Rate: 93 HBM
18:08:26.030 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 62 0A 0F 08 9C 00 78 00 22 01 00 14 00 95 00 5E 00 00 ]
18:08:26.030 -> Speed: 26 KPH Instantaneous Cadence: 1031 RPM Average Cadence: 78 RPM Total Distance: 2228344 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 149 Watt Heart Rate: 94 HBM
18:08:27.014 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 9F 0A 18 08 A0 00 79 00 29 01 00 14 00 A9 00 5F 00 00 ]
18:08:27.014 -> Speed: 27 KPH Instantaneous Cadence: 1036 RPM Average Cadence: 80 RPM Total Distance: 2687097 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 169 Watt Heart Rate: 95 HBM
18:08:27.014 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 4F 01 28 33 00 ]
18:08:27.107 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:27.107 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 4F 01 28 33 ]
18:08:27.989 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 FE 09 21 08 9C 00 7A 00 30 01 00 14 00 C0 00 61 00 00 ]
18:08:27.989 -> Speed: 25 KPH Instantaneous Cadence: 1040 RPM Average Cadence: 78 RPM Total Distance: 3145850 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 192 Watt Heart Rate: 97 HBM
18:08:28.992 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 02 0A 2A 08 98 00 7A 00 37 01 00 14 00 C9 00 63 00 00 ]
18:08:28.992 -> Speed: 25 KPH Instantaneous Cadence: 1045 RPM Average Cadence: 76 RPM Total Distance: 3604602 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 201 Watt Heart Rate: 99 HBM
18:08:29.114 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 01 28 33 00 ]
18:08:29.346 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:29.346 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 01 28 33 ]
18:08:29.995 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A3 09 2B 08 94 00 7B 00 3D 01 00 14 00 CD 00 65 00 00 ]
18:08:29.995 -> Speed: 24 KPH Instantaneous Cadence: 1045 RPM Average Cadence: 74 RPM Total Distance: 3997819 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 205 Watt Heart Rate: 101 HBM
18:08:30.983 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 6B 09 2D 08 92 00 7B 00 43 01 00 14 00 D0 00 67 00 00 ]
18:08:30.983 -> Speed: 24 KPH Instantaneous Cadence: 1046 RPM Average Cadence: 73 RPM Total Distance: 4391035 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 208 Watt Heart Rate: 103 HBM
18:08:31.216 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 57 FF 28 33 00 ]
18:08:31.309 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:31.309 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 57 FF 28 33 ]
18:08:32.004 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 FE 09 34 08 8E 00 7C 00 4A 01 00 14 00 C7 00 68 00 00 ]
18:08:32.004 -> Speed: 25 KPH Instantaneous Cadence: 1050 RPM Average Cadence: 71 RPM Total Distance: 4849788 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 199 Watt Heart Rate: 104 HBM
18:08:33.234 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 3C 0A 3C 08 8E 00 7C 00 51 01 00 14 00 D2 00 6A 00 00 ]
18:08:33.234 -> Speed: 26 KPH Instantaneous Cadence: 1054 RPM Average Cadence: 71 RPM Total Distance: 5308540 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 210 Watt Heart Rate: 106 HBM
18:08:33.310 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 08 00 00 00 00 00 00 00 ]
18:08:33.388 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 08 03 ]
18:08:33.974 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 A0 0A 43 08 92 00 7C 00 58 01 00 14 00 B2 00 6B 00 00 ]
18:08:33.974 -> Speed: 27 KPH Instantaneous Cadence: 1057 RPM Average Cadence: 73 RPM Total Distance: 5767292 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 178 Watt Heart Rate: 107 HBM
18:08:34.984 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 EE 0A 4A 08 96 00 7D 00 5F 01 00 14 00 6F 00 6C 00 00 ]
18:08:34.984 -> Speed: 27 KPH Instantaneous Cadence: 1061 RPM Average Cadence: 75 RPM Total Distance: 6226045 m Resistance Level: 1 Instantaneous Power: 20 Watt Average Power: 111 Watt Heart Rate: 108 HBM
18:08:35.386 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 01 00 00 00 00 00 00 00 ]
18:08:35.479 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 01 01 ]
18:08:35.479 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 01 ]
18:08:35.989 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 44 0A 9C 00 14 00 3A 00 00 ]
18:08:35.989 -> Speed: 26 KPH Instantaneous Cadence: 78 RPM Resistance Level: 20 Instantaneous Power: 58 Watt Heart Rate: 0 HBM
18:08:36.992 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 AC 09 00 00 14 00 00 00 00 ]
18:08:36.992 -> Speed: 24 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:08:37.486 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:08:37.579 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:08:37.997 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 18 09 00 00 14 00 00 00 00 ]
18:08:37.997 -> Speed: 23 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:08:39.290 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 8A 08 00 00 14 00 00 00 00 ]
18:08:39.290 -> Speed: 21 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:08:39.584 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:08:39.833 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:08:39.956 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 FC 07 00 00 14 00 00 00 00 ]
18:08:39.956 -> Speed: 20 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:08:40.991 -> -> Client Rec'd Raw FTM Indoor Bike Data: [11] [ 64 02 74 07 00 00 14 00 00 00 00 ]
18:08:40.991 -> Speed: 19 KPH Instantaneous Cadence: 0 RPM Resistance Level: 20 Instantaneous Power: 0 Watt Heart Rate: 0 HBM
18:08:41.684 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
18:08:41.793 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
18:08:41.793 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
18:08:42.024 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 ED 06 AC 05 00 00 00 00 04 00 00 14 00 00 00 00 00 00 ]
18:08:42.024 -> Speed: 17 KPH Instantaneous Cadence: 726 RPM Average Cadence: 0 RPM Total Distance: 262144 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:43.125 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 6A 06 AB 05 00 00 00 00 08 00 00 14 00 00 00 00 00 00 ]
18:08:43.125 -> Speed: 16 KPH Instantaneous Cadence: 725 RPM Average Cadence: 0 RPM Total Distance: 524288 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:43.770 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
18:08:43.863 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:43.863 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
18:08:43.987 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 E9 05 AB 05 00 00 00 00 0C 00 00 14 00 00 00 00 00 00 ]
18:08:43.987 -> Speed: 15 KPH Instantaneous Cadence: 725 RPM Average Cadence: 0 RPM Total Distance: 786432 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:44.988 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 6C 05 51 05 00 00 00 00 0F 00 00 14 00 00 00 00 00 00 ]
18:08:44.988 -> Speed: 13 KPH Instantaneous Cadence: 680 RPM Average Cadence: 0 RPM Total Distance: 983040 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:45.858 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
18:08:45.936 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:45.936 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
18:08:45.982 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 F0 04 1A 05 00 00 00 00 12 00 00 14 00 00 00 00 00 00 ]
18:08:45.982 -> Speed: 12 KPH Instantaneous Cadence: 653 RPM Average Cadence: 0 RPM Total Distance: 1179648 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:47.261 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 7B 04 F6 04 00 00 00 00 15 00 00 14 00 00 00 00 00 00 ]
18:08:47.261 -> Speed: 11 KPH Instantaneous Cadence: 635 RPM Average Cadence: 0 RPM Total Distance: 1376256 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:47.940 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:08:47.972 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 07 04 A8 04 00 00 00 00 17 00 00 14 00 00 00 00 00 00 ]
18:08:47.972 -> Speed: 10 KPH Instantaneous Cadence: 596 RPM Average Cadence: 0 RPM Total Distance: 1507328 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:48.003 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:48.003 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:08:49.051 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 98 03 6E 04 00 00 00 00 19 00 00 14 00 00 00 00 00 00 ]
18:08:49.096 -> Speed: 9 KPH Instantaneous Cadence: 567 RPM Average Cadence: 0 RPM Total Distance: 1638400 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:50.008 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 2B 03 40 04 00 00 00 00 1B 00 00 14 00 00 00 00 00 00 ]
18:08:50.008 -> Speed: 8 KPH Instantaneous Cadence: 544 RPM Average Cadence: 0 RPM Total Distance: 1769472 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:50.008 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
18:08:50.132 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:50.132 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
18:08:51.171 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 C2 02 F8 03 00 00 00 00 1C 00 00 14 00 00 00 00 00 00 ]
18:08:51.171 -> Speed: 7 KPH Instantaneous Cadence: 508 RPM Average Cadence: 0 RPM Total Distance: 1835008 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:52.014 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 5C 02 BC 03 00 00 00 00 1D 00 00 14 00 00 00 00 00 00 ]
18:08:52.014 -> Speed: 6 KPH Instantaneous Cadence: 478 RPM Average Cadence: 0 RPM Total Distance: 1900544 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:52.133 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
18:08:52.169 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:52.169 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
18:08:52.969 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 FC 01 8B 03 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:52.969 -> Speed: 5 KPH Instantaneous Cadence: 453 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:54.032 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 45 03 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:54.032 -> Speed: 0 KPH Instantaneous Cadence: 418 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:54.172 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
18:08:54.375 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:54.375 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 25 00 28 33 ]
18:08:55.011 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 09 03 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:55.056 -> Speed: 0 KPH Instantaneous Cadence: 388 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:55.994 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 D6 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:55.994 -> Speed: 0 KPH Instantaneous Cadence: 363 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:56.274 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 23 00 28 33 00 ]
18:08:56.366 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:56.366 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 23 00 28 33 ]
18:08:57.103 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 A8 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:57.103 -> Speed: 0 KPH Instantaneous Cadence: 340 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:58.006 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 80 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:58.006 -> Speed: 0 KPH Instantaneous Cadence: 320 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:58.393 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 1C 00 28 33 00 ]
18:08:58.486 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:08:58.486 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 1C 00 28 33 ]
18:08:59.043 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 5D 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:59.043 -> Speed: 0 KPH Instantaneous Cadence: 302 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:08:59.970 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 3D 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:08:59.970 -> Speed: 0 KPH Instantaneous Cadence: 286 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:00.484 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 0F 00 28 33 00 ]
18:09:00.562 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:00.562 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 0F 00 28 33 ]
18:09:00.982 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 20 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:00.982 -> Speed: 0 KPH Instantaneous Cadence: 272 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:02.154 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 06 02 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:02.154 -> Speed: 0 KPH Instantaneous Cadence: 259 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:02.545 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:09:02.671 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:02.671 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:09:03.077 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 EF 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:03.077 -> Speed: 0 KPH Instantaneous Cadence: 247 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:04.037 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 D9 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:04.037 -> Speed: 0 KPH Instantaneous Cadence: 236 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:04.670 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 F5 FF 28 33 00 ]
18:09:04.993 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 C5 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:04.993 -> Speed: 0 KPH Instantaneous Cadence: 226 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:05.039 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:05.039 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 F5 FF 28 33 ]
18:09:05.976 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 B3 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:05.976 -> Speed: 0 KPH Instantaneous Cadence: 217 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:06.769 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 E4 FF 28 33 00 ]
18:09:06.848 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:06.848 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 E4 FF 28 33 ]
18:09:06.988 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 A3 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:06.988 -> Speed: 0 KPH Instantaneous Cadence: 209 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:07.992 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 93 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:07.992 -> Speed: 0 KPH Instantaneous Cadence: 201 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:08.857 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 CF FF 28 33 00 ]
18:09:08.980 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 85 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:08.980 -> Speed: 0 KPH Instantaneous Cadence: 194 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:09.026 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:09.026 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 CF FF 28 33 ]
18:09:10.279 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 77 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:10.279 -> Speed: 0 KPH Instantaneous Cadence: 187 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:10.944 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 A8 FF 28 33 00 ]
18:09:10.990 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 6B 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:10.990 -> Speed: 0 KPH Instantaneous Cadence: 181 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:11.037 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:11.037 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 A8 FF 28 33 ]
18:09:12.001 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 5F 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:12.001 -> Speed: 0 KPH Instantaneous Cadence: 175 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:12.989 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 54 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:12.989 -> Speed: 0 KPH Instantaneous Cadence: 170 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:13.025 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 84 FF 28 33 00 ]
18:09:13.104 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:13.104 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 84 FF 28 33 ]
18:09:13.972 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 4A 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:13.972 -> Speed: 0 KPH Instantaneous Cadence: 165 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:14.978 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 40 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:14.978 -> Speed: 0 KPH Instantaneous Cadence: 160 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:15.116 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 67 FF 28 33 00 ]
18:09:15.194 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:15.194 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 67 FF 28 33 ]
18:09:16.125 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 37 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:16.125 -> Speed: 0 KPH Instantaneous Cadence: 155 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:17.013 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 2E 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:17.013 -> Speed: 0 KPH Instantaneous Cadence: 151 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:17.184 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5D FF 28 33 00 ]
18:09:17.263 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:17.263 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5D FF 28 33 ]
18:09:18.010 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 26 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:18.010 -> Speed: 0 KPH Instantaneous Cadence: 147 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:19.015 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 1E 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]
18:09:19.015 -> Speed: 0 KPH Instantaneous Cadence: 143 RPM Average Cadence: 0 RPM Total Distance: 1966080 m Resistance Level: 0 Instantaneous Power: 20 Watt Average Power: 0 Watt Heart Rate: 0 HBM
18:09:19.248 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 5E FF 28 33 00 ]
18:09:19.372 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:09:19.372 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 5E FF 28 33 ]
18:09:20.050 -> -> Client Rec'd Raw FTM Indoor Bike Data: [20] [ FE 02 00 00 17 01 00 00 00 00 1E 00 00 14 00 00 00 00 00 00 ]

// If FTM Feature is not found, disconnect, resume scanning, and return
while (!( client_FTM_Feature_Chr.discover() ))
{
if ( client_FTM_Feature_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Read FTM Feature Data
client_FTM_Feature_Chr.read(client_FTM_Feature_Data, 8);
#ifdef DEBUG
Serial.print(" -> Client Reads Raw FTM Feature bytes: [8] [ ");
for (int i = 0; i < sizeof(client_FTM_Feature_Data); i++) {
Serial.printf("%02X ", client_FTM_Feature_Data[i], HEX);
} // for
Serial.println("] ");
#endif
} else {
#ifdef DEBUG
Serial.println("Disconnecting since Client FTM Feature Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
Bluefruit.Connection(conn_handle);
Serial.print("Discovering Client FTM Feature not decouvert ... ");
// return;
}
}

As you can see in the second test it does not find the speed and cadence values.

Probably I should put more "While".

What is weird is the value of the heart rate because the sensor is not connected (battery removed)

18:26:23.470 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
18:26:23.470 -> ----------------- Version 02.5 ------------------
18:26:23.470 -> Initialise the Bluefruit nRF52 module: Client (Central)
18:26:23.718 -> FTMS and Chars 'initialized'
18:26:23.718 -> CPS and Chars 'initialized'
18:26:23.718 -> CSCS and Chars 'initialized'
18:26:23.718 -> GA and Chars 'initialized'
18:26:23.718 -> DIS and Chars 'initialized'
18:26:23.718 -> Start Scanning for CPS, CSC and FTMS!
18:26:23.720 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
18:26:23.720 -> Timestamp MAC Address Rssi Data
18:26:23.720 -> 000001552 F8:9C:FC:53:5E:49 -61 09-02-16-18-26-18-18-18-0A-18
18:26:23.720 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
18:26:23.720 -> Now checking all Client Services and Characteristics!
18:26:23.720 -> If Mandatory Services Fail --> the Client will disconnect!
18:26:23.720 -> First checking Generic Access and Device Information Services and Characteristics!
18:26:24.243 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
18:26:24.243 -> Discovering Client FTM Feature Characteristic ... Discovering Client FTM Control Point Characteristic ... Found it!
18:26:24.252 -> Discovering Client FTM Status Characteristic ... Found it!
18:26:24.544 -> Discovering Client FTM Training Status Characteristic ... Not Found! Not Mandatory
18:26:24.823 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
18:26:25.225 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
18:26:25.225 -> Discovering Client FTM Supported Power Range Characteristic ... Found it!
18:26:25.457 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ]
18:26:25.457 -> Discovering Client FTM Indoor Bike Data Characteristic ... Found it!
18:26:25.781 -> Discovering Client Cycling Power (CP) Service ... Ready to receive Client FTM Control Point Response Messages
18:26:25.827 -> Found it! CPS Max Payload: 20 Data Length: 27
18:26:25.827 -> Discovering Client CP Measurement characteristic ... Ready to receive Client FTM Status values
18:26:25.827 -> >>> Couldn't enable notify for Client FTM Training Status Characteristic.
18:26:25.906 -> >>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic.
18:26:25.906 -> >>> Couldn't enable notify for Client CP Measurement Characteristic.
18:26:25.906 -> >>> Couldn't enable indicate for Client CP Control Point Characteristic.
18:26:25.906 -> >>> Couldn't enable notify for Client CSC Measurement Characteristic.
18:26:25.906 -> Client (Central) is Up and Running!
18:26:26.045 -> Found it!
18:26:26.045 -> Discovering Client CP Control Point characteristic ... Not Found! NOT Mandatory!
18:26:26.541 -> Discovering Client CP Feature characteristic ... Found it!
18:26:26.726 -> -> Client Reads Raw CP Feature bytes: [4] [ 00 00 00 00 ]
18:26:26.726 -> Discovering Client CP Sensor Location characteristic ... NOT Found! NOT Mandatory!
18:26:26.726 -> Discovering Cycling Speed and Cadence (CSC) Service ... Not Found! CSC Service is Not Mandatory!
18:26:27.906 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:26:27.970 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:26:29.983 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 00 00 00 00 00 00 00 00 ]
18:26:30.029 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 00 01 ]
18:26:32.045 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 07 00 00 00 00 00 00 00 ]
18:26:32.122 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 07 01 ]
18:26:32.122 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [ 04 ]
18:26:34.127 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 01 28 33 00 ]
18:26:34.174 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:26:34.174 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 01 28 33 ]
18:26:36.191 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 09 00 28 33 00 ]
18:26:36.237 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:26:36.237 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 09 00 28 33 ]
18:26:38.240 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 00 00 28 33 00 ]
18:26:38.317 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:26:38.317 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 00 00 28 33 ]
18:26:40.324 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 14 00 28 33 00 ]
18:26:40.402 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:26:40.402 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 14 00 28 33 ]
18:26:42.383 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 22 00 28 33 00 ]
18:26:42.508 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]
18:26:42.508 -> -> Client Rec'd Raw FTM Machine Status Data: [7] [ 12 00 00 22 00 28 33 ]
18:26:44.510 -> Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ 11 00 00 25 00 28 33 00 ]
18:26:44.588 -> -> Client Rec'd Raw FTM Control Point Response Data: [ 80 11 01 ]

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
I am puzzled about how and what you have changed in the code version 025. I see a while loop that waits for ever until the FTM_Feature_Char is discovered: while (!( client_FTM_Feature_Chr.discover() )) { et cetera }
FTM_Feature was never a problem....??? Did you put while loops in all discover calls...? For what purpose?
Whatever you did: one of the runs now shows -> Client Rec'd Raw FTM Indoor Bike Data: et cetera
That never ever happened before ...... ????
So please detail more and better what you have changed otherwise I am only guessing and that does not help progress...
Greetings,
Jörgen.

from simcline.

Berg0162 commented on July 23, 2024

Dear Joel,
Still I would like to know more precisely what you have altered in the code of 025... that issue is still open!
Your code snippet is only relevant when you think a timing problem prevents the discovery of the relevant Char's..... (?)
Meanwhile I guessed that (along the same line of reasoning) enabling of the Char's with Notify or Indicate (at the Zwift Hub) might go wrong due to a timing problem...(ItsyBitsy? or Hub?). So I have inserted a timed check for notify/indicate result that gives the polling process two (2) seconds for response....
I wonder if this version 027 will bring us closer to a solution... (You still need to wake up your trainer and ride the trainer!!)

Do not take the IBD decoded data too serious, decoding the IBD data is very complicated and I would not be surprised that I understood it in a wrong way.... although it works fine with Elite Direto specifications! This is not critical for the final result, after all the MITM does not have to understand/decode everything, only what it is interested in...

By the way the FTMS_Zwift_Bridge code v023 can be tested with your setup.... (Notice that you have to pedal as well! Read the instructions)

Best wishes,
Jörgen.

from simcline.

le-joebar commented on July 23, 2024

Hello Jorghen,

To answer the question should I always wake him up?

No with the modification I made I just have to turn on the trainer.
No need to pedal.
So the problem was not a problem of waking up but probably of receiving "char"!

Here is the V.025 that I had to modify.
There are 3 "While" that I had added.

I will test your V0.27.

Sincerely,
Joel

/*********************************************************************
This is programming code for the nRF52 based Bluefruit BLE boards

The code uses heavily the Adafruit supplied Bluefruit BLE libraries !!
Adafruit invests time and resources providing open source code,
please support Adafruit and open-source hardware by purchasing
products from Adafruit!

MIT license, check LICENSE for more information
All text must be included in any redistribution
*********************************************************************/

This Feather-nRF52840 tested code scans for the CPS, CSC and FTMS
that the trainer is advertising, it tries to connect and then
enables .....
Requirements: FTMS trainer and Feather nRF52 board
1. Upload and Run this code on the Feather-nRF52
1. Start the Serial Monitor to catch verbose debugging and data info
1. Power ON and Wake UP trainer -> do NOT connect with other devices
1. Trainer and Feather should successfully pair or disconnect...
1. Keep the Serial Monitor visible on top of all windows
1. Move the trainer pedals and notice/feel changes in resistance...

The Client sends Resistance Parameters to the Trainer that coincide

with the first 5 minutes of the Zwift Volcano Circuit!

1. Inspect the info presented by Serial Monitor.....

// -------------------------------------------------------------------------------------------
// COMPILER DIRECTIVE to allow/suppress SERIAL.PRINT messages that help debugging...
// Uncomment to activate
#define DEBUG
//#define DEBUG_CP_MEASUREMENT
//#define DEBUG_CSC_MEASUREMENT
// --------------------------------------------------------------------------------------------

#include <bluefruit.h>

const uint8_t MAX_PAYLOAD = 20; // Max 20 byte data size for single packet BLE transfer
uint16_t client_Connection_Handle = BLE_CONN_HANDLE_INVALID;

/* Generic Access
#define UUID16_SVC_GENERIC_ACCESS 0x1800
#define UUID16_CHR_DEVICE_NAME 0x2A00
#define UUID16_CHR_APPEARANCE 0x2A01
#define UUID16_CHR_PERIPHERAL_PREFERRED_CONNECTION_PARAMETERS 0x2A04
#define UUID16_CHR_CENTRAL_ADDRESS_RESOLUTION 0x2AA6
*/
BLEClientService client_GenericAccess_Service(UUID16_SVC_GENERIC_ACCESS);
BLEClientCharacteristic client_GA_Appearance_Chr(UUID16_CHR_APPEARANCE); // Read
uint16_t client_GA_Appearance_Value = 0;
BLEClientCharacteristic client_GA_DeviceName_Chr(UUID16_CHR_DEVICE_NAME);// Read, Write
unsigned char client_GA_DeviceName_Data[MAX_PAYLOAD] = {};

/* Cycling Power Service

CP Service: 0x1818
CP Characteristic: 0x2A63 (Measurement)
CP Characteristic: 0x2A65 (Feature)
CP Characteristic: 0x2A5D (Location)
CP Characteristic: 0x2A66 (Control Point)
*/
BLEClientService client_CyclingPower_Service(UUID16_SVC_CYCLING_POWER);
BLEClientCharacteristic client_CP_Measurement_Chr(UUID16_CHR_CYCLING_POWER_MEASUREMENT); // Notify, Read
BLEClientCharacteristic client_CP_Feature_Chr(UUID16_CHR_CYCLING_POWER_FEATURE); // Read
uint32_t client_CP_Feature_Flags = 0;
BLEClientCharacteristic client_CP_Location_Chr(UUID16_CHR_SENSOR_LOCATION); // Read
uint8_t client_CP_Location_Value = 0; // UINT8
BLEClientCharacteristic client_CP_ControlPoint_Chr(UUID16_CHR_CYCLING_POWER_CONTROL_POINT); // Indicate, Write

const char* client_CP_Feature_Str[] = {
"Pedal power balance supported",
"Accumulated torque supported",
"Wheel revolution data supported",
"Crank revolution data supported",
"Extreme magnitudes supported",
"Extreme angles supported",
"Top/bottom dead angle supported",
"Accumulated energy supported",
"Offset compensation indicator supported",
"Offset compensation supported",
"Cycling power measurement characteristic content masking supported",
"Multiple sensor locations supported",
"Crank length adj. supported",
"Chain length adj. supported",
"Chain weight adj. supported",
"Span length adj. supported",
"Sensor measurement context",
"Instantaineous measurement direction supported",
"Factory calibrated date supported",
"Enhanced offset compensation supported" };

const char* client_Sensor_Location_Str[] = { "Other", "Top of shoe", "In shoe", "Hip", "Front wheel", "Left crank", "Right crank", "Left pedal",
"Right pedal", "Front hub", "Rear dropout", "Chainstay", "Rear wheel", "Rear hub", "Chest", "Spider", "Chain ring"};

Cycling Speed and Cadence Service
CSC Service: 0x1816
CSC Measurement Characteristic: 0x2A5B
CSC Feature Characteristic: 0x2A5C
/
/ CSC Control Point Characteristic:0x2A55 ---> not implemented
// CSC Control Point op codes
#define SC_CP_OP_SET_CUMULATIVE_VALUE 1
#define SC_CP_OP_START_SENSOR_CALIBRATION 2
#define SC_CP_OP_UPDATE_SENSOR_LOCATION 3
#define SC_CP_OP_REQ_SUPPORTED_SENSOR_LOCATIONS 4
#define SC_CP_OP_RESPONSE 16
// CSC Control Point response values
#define SC_CP_RESPONSE_SUCCESS 1
#define SC_CP_RESPONSE_OP_NOT_SUPPORTED 2
#define SC_CP_RESPONSE_INVALID_PARAM 3
#define SC_CP_RESPONSE_OP_FAILED 4
*/

/CSC Measurement flags/
#define CSC_MEASUREMENT_WHEEL_REV_PRESENT 0x01
#define CSC_MEASUREMENT_CRANK_REV_PRESENT 0x02

/* CSC Feature flags */
#define CSC_FEATURE_WHEEL_REV_DATA 0x01
#define CSC_FEATURE_CRANK_REV_DATA 0x02
#define CSC_FEATURE_MULTIPLE_SENSOR_LOC 0x04

const char* client_CSC_Feature_Str[] = {"Wheel rev supported", "Crank rev supported", "Multiple locations supported"};

BLEClientService client_CyclingSpeedCadence_Service(UUID16_SVC_CYCLING_SPEED_AND_CADENCE);
BLEClientCharacteristic client_CSC_Measurement_Chr(UUID16_CHR_CSC_MEASUREMENT); // Notify, Read
BLEClientCharacteristic client_CSC_Feature_Chr(UUID16_CHR_CSC_FEATURE); // Read
const uint8_t CSC_FEATURE_FIXED_DATALEN = 2; // UINT16
uint16_t client_CSC_Feature_Flags = 0;
BLEClientCharacteristic client_CSC_Location_Chr(UUID16_CHR_SENSOR_LOCATION); // Read
uint8_t client_CSC_Location_Value = 0;

/* Client Service Device Information
#define UUID16_SVC_DEVICE_INFORMATION 0x180A
#define UUID16_CHR_MODEL_NUMBER_STRING 0x2A24
#define UUID16_CHR_SERIAL_NUMBER_STRING 0x2A25
#define UUID16_CHR_FIRMWARE_REVISION_STRING 0x2A26
#define UUID16_CHR_HARDWARE_REVISION_STRING 0x2A27
#define UUID16_CHR_SOFTWARE_REVISION_STRING 0x2A28
#define UUID16_CHR_MANUFACTURER_NAME_STRING 0x2A29
*/
BLEClientService client_DIS_Service(UUID16_SVC_DEVICE_INFORMATION);
BLEClientCharacteristic client_DIS_ManufacturerName_Chr(UUID16_CHR_MANUFACTURER_NAME_STRING); // Read
char client_DIS_Manufacturer_Str[MAX_PAYLOAD] = {};
BLEClientCharacteristic client_DIS_ModelNumber_Chr(UUID16_CHR_MODEL_NUMBER_STRING); // Read
char client_DIS_ModelNumber_Str[MAX_PAYLOAD] = {};
BLEClientCharacteristic client_DIS_SerialNumber_Chr(UUID16_CHR_SERIAL_NUMBER_STRING); // Read
char client_DIS_SerialNumber_Str[MAX_PAYLOAD] = {};

Fitness Machine Service, uuid 0x1826 or 00001826-0000-1000-8000-00805F9B34FB
#define UUID16_SVC_FITNESS_MACHINE 0x1826
#define UUID16_CHR_FITNESS_MACHINE_FEATURE 0x2ACC
#define UUID16_CHR_INDOOR_BIKE_DATA 0x2AD2
#define UUID16_CHR_TRAINING_STATUS 0x2AD3
#define UUID16_CHR_SUPPORTED_SPEED_RANGE 0x2AD4
#define UUID16_CHR_SUPPORTED_INCLINATION_RANGE 0x2AD5
#define UUID16_CHR_SUPPORTED_RESISTANCE_LEVEL_RANGE 0x2AD6
#define UUID16_CHR_SUPPORTED_HEART_RATE_RANGE 0x2AD7
#define UUID16_CHR_SUPPORTED_POWER_RANGE 0x2AD8
#define UUID16_CHR_FITNESS_MACHINE_CONTROL_POINT 0x2AD9
#define UUID16_CHR_FITNESS_MACHINE_STATUS 0x2ADA
*/
BLEClientService client_FitnessMachine_Service(UUID16_SVC_FITNESS_MACHINE); // FTM Service
// Service characteristics exposed by FTM Service
BLEClientCharacteristic client_FTM_Feature_Chr(UUID16_CHR_FITNESS_MACHINE_FEATURE); // Fitness Machine Feature, mandatory, read
const uint8_t FTM_FEATURE_FIXED_DATALEN = 8;
uint8_t client_FTM_Feature_Data[FTM_FEATURE_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_IndoorBikeData_Chr(UUID16_CHR_INDOOR_BIKE_DATA); // Indoor Bike Data, optional, notify
BLEClientCharacteristic client_FTM_TrainingStatus_Chr(UUID16_CHR_TRAINING_STATUS); // Training Status, optional, read & notify
BLEClientCharacteristic client_FTM_SupportedResistanceLevelRange_Chr(UUID16_CHR_SUPPORTED_RESISTANCE_LEVEL_RANGE); // Supported Resistance Level, read, optional
const uint8_t FTM_SRLR_FIXED_DATALEN = 6;
uint8_t client_FTM_SupportedResistanceLevelRange_Data[FTM_SRLR_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_SupportedPowerRange_Chr(UUID16_CHR_SUPPORTED_POWER_RANGE); // Supported Power Levels, read, optional
const uint8_t FTM_SPR_FIXED_DATALEN = 6;
uint8_t client_FTM_SupportedPowerRange_Data[FTM_SPR_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_ControlPoint_Chr(UUID16_CHR_FITNESS_MACHINE_CONTROL_POINT); // Fitness Machine Control Point, optional, write & indicate
BLEClientCharacteristic client_FTM_Status_Chr(UUID16_CHR_FITNESS_MACHINE_STATUS); // Fitness Machine Status, mandatory, notify

#define TIME_SPAN 2500 // Time span (delay) in millis 1000 = 1 second
#define CONTROL_POINT_TIME_SPAN 2000 // Time span for sending Control Point data
unsigned long TimeInterval = 0;

// TEST DATA set -----------------------------------------------------
// Test set (Zwift Volcano Circuit) with Control and 2D Resistance data to be sent to Control Point
uint8_t ControlPointMessageCount = 0;
const uint8_t ControlPointData[32][8] = {
{0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00}, // Request Control
{0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00}, // Request Control
{0x07,0x00,0x00,0x00,0x00,0x00,0x00,0x00}, // Start or Resume
{0x11,0x00,0x00,0x22,0x01,0x28,0x33,0x00}, // Set Indoor Bike Simulation Parameters..
{0x11,0x00,0x00,0x09,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x00,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x14,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x22,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x25,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x23,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x1C,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x0F,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x00,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0xF5,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0xE4,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0xCF,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0xA8,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x84,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x67,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x5D,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x5E,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x6F,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x8A,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0xB8,0xFF,0x28,0x33,0x00},
{0x11,0x00,0x00,0x00,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0xA2,0x00,0x28,0x33,0x00},
{0x11,0x00,0x00,0x09,0x01,0x28,0x33,0x00},
{0x11,0x00,0x00,0x4F,0x01,0x28,0x33,0x00},
{0x11,0x00,0x00,0x67,0x01,0x28,0x33,0x00},
{0x11,0x00,0x00,0x57,0xFF,0x28,0x33,0x00},
{0x08,0x00,0x00,0x00,0x00,0x00,0x00,0x00}, // Stop or Pause
{0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00}};// Reset
// TEST DATA set ---------------------------------------------------

void setup()
{
#ifdef DEBUG
Serial.begin(115200);
while ( !Serial ) delay(10); // for nrf52840 with native usb

Serial.println(" Feather nRF52 Client/Central: CPS, CSC and FTMS");
Serial.println("----------------- Version 02.5 ------------------");
Serial.println("Initialise the Bluefruit nRF52 module: Client (Central)");
#endif
// Initialize Bluefruit module
// begin (Peripheral = 0, Central = 1)
Bluefruit.begin(0, 1);

Setup_Client_FTMS();
Setup_Client_CPS();
Setup_Client_CSC();
Setup_Client_DIS();
Client_Start_Scanning();

while (Bluefruit.Scanner.isRunning()) { // do nothing else but scanning....
}
TimeInterval = millis() + TIME_SPAN; // ADD just enough delay
// wait enough time or go on when Client/Central is connected and all set!
while( TimeInterval > millis() ) {
}
// Scanning is finished! Are we connected?
// If NO connection is established -> Stop!
if( !(Bluefruit.connected()) ) {
#ifdef DEBUG
Serial.println("Stopped!");

#endif
return;
}
// Try to enable Client (Trainer) CPS, CSC and FTMS data streams...
Client_Enable_Notify_Indicate();
if( !(Bluefruit.connected()) ) { // Are we meanwhile disconnected?
#ifdef DEBUG
Serial.println("Stopped!");

#endif
return;
}
// After successful enable notify/indicate of all mandatory Char's continue!
#ifdef DEBUG
Serial.println("Client (Central) is Up and Running!");
#endif
// Set first timing for sending first set of Control Point Data
TimeInterval = millis() + CONTROL_POINT_TIME_SPAN;
}

void Setup_Client_FTMS(void)
{
// Initialize client FTM Service
client_FitnessMachine_Service.begin();
while( !(client_FitnessMachine_Service.begin()) ) {
Serial.println("Wait for FitnessMachine_Service.begin ");
}
// Initialize client FTM Feature characteristic
client_FTM_Feature_Chr.begin();

// Initialize client FTM Training Status characteristic
client_FTM_TrainingStatus_Chr.setNotifyCallback(client_FTM_TrainingStatus_Notify_callback);

client_FTM_TrainingStatus_Chr.begin();

// Initialize client FTM Supported Power Range characteristic
client_FTM_SupportedPowerRange_Chr.begin();

// Initialize client FTM Supported Resistance Level Range characteristic
client_FTM_SupportedResistanceLevelRange_Chr.begin();

// Initialize client FTM Indoor Bike Data characteristic
client_FTM_IndoorBikeData_Chr.setNotifyCallback(client_FTM_IndoorBikeData_Notify_callback);
client_FTM_IndoorBikeData_Chr.begin();

// Initialize client FTM Control Point characteristic
// For receiving Control Point Responses
client_FTM_ControlPoint_Chr.setIndicateCallback(client_FTM_ControlPoint_Indicate_callback);
client_FTM_ControlPoint_Chr.begin();

// Initialize client FTM Status characteristic
client_FTM_Status_Chr.setNotifyCallback(client_FTM_Status_Notify_callback);
client_FTM_Status_Chr.begin();
#ifdef DEBUG
Serial.println("FTMS and Chars 'initialized'");
#endif
}

void Setup_Client_CPS(void)
{
// Initialize CPS client
client_CyclingPower_Service.begin();

// Initialize CP Feature characteristics of client_CyclingPower_Service.
client_CP_Feature_Chr.begin();

// Initialize CP sensor location characteristics of client_CyclingPower_Service.
client_CP_Location_Chr.begin();

// set up callback for receiving measurement
client_CP_Measurement_Chr.setNotifyCallback(client_CP_Measurement_Chr_notify_callback);
client_CP_Measurement_Chr.begin();

// Initialize Control Point and set up Indicate callback for receiving responses (indicate!)
client_CP_ControlPoint_Chr.setIndicateCallback(client_CP_ControlPoint_Chr_indicate_callback);
client_CP_ControlPoint_Chr.begin();
#ifdef DEBUG
Serial.println("CPS and Chars 'initialized'");
#endif
}

void Setup_Client_CSC(void)
{
// Initialize CSC client
client_CyclingSpeedCadence_Service.begin();

// Initialize client characteristics of CSC.
client_CSC_Location_Chr.begin();

// Initialize CSC Feature characteristics of client_CSC.
client_CSC_Feature_Chr.begin();

// set up callback for receiving measurement
client_CSC_Measurement_Chr.setNotifyCallback(client_CSC_Measurement_Chr_notify_callback);
client_CSC_Measurement_Chr.begin();
#ifdef DEBUG
Serial.println("CSCS and Chars 'initialized'");
#endif
}

void Setup_Client_DIS(void)
{
// Initialize client Generic Access Service
client_GenericAccess_Service.begin();
// Initialize some characteristics of the Generic Access Service.
client_GA_DeviceName_Chr.begin();
client_GA_Appearance_Chr.begin();
#ifdef DEBUG
Serial.println("GA and Chars 'initialized'");
#endif
// Initialize client Device Information Service
client_DIS_Service.begin();
// Initialize some characteristics of the Device Information Service.
client_DIS_ManufacturerName_Chr.begin();
client_DIS_ModelNumber_Chr.begin();
client_DIS_SerialNumber_Chr.begin();
#ifdef DEBUG
Serial.println("DIS and Chars 'initialized'");
#endif
}

void loop()
{

if ( Bluefruit.connected() )
{
// If time is there, send test values of Indoor Bike Simulation Parameters to
// the Trainer's FTM Control Point to drive the FTM...
if(millis() > TimeInterval)
{
if(ControlPointMessageCount > 31) { ControlPointMessageCount = 0; } // start all over again!
uint8_t CPData[8] = {};
#ifdef DEBUG
Serial.print("Client sends Indoor Bike Simulation Parameters to Trainer's FTM Control Point: [ ");
#endif
// Transfer multidimensional test data to CPData buffer
for (int i = 0; i < sizeof(CPData); i++) {
CPData[i] = ControlPointData[ControlPointMessageCount][i];
#ifdef DEBUG
Serial.printf("%02X ", CPData[i], HEX);
#endif
}
#ifdef DEBUG
Serial.println("] ");
#endif
// client_FTM_ControlPoint_Chr.write(CPData, 8);
client_FTM_ControlPoint_Chr.write_resp(CPData, 8);
TimeInterval = millis() + CONTROL_POINT_TIME_SPAN;
ControlPointMessageCount++;
} // TimeInterval
} // Bluefruit connected
} // end loop

void Client_Start_Scanning(void)
{
/* Start Central Scanning

- Enable auto scan if disconnected
- Interval = 100 ms, window = 80 ms
- Don't use active scan
- Filter only accept CP service
- Start(timeout) with timeout = 0 will scan forever (until connected)
  */

// Client/Central Callbacks defined
Bluefruit.Central.setDisconnectCallback(client_disconnect_callback);
Bluefruit.Central.setConnectCallback(client_connect_callback);

Bluefruit.Scanner.setRxCallback(client_scan_callback);
Bluefruit.Scanner.restartOnDisconnect(false); // default -> true !!! in test stage we do not want to RESTART -> false
Bluefruit.Scanner.filterRssi(-70); // original value of -80 , we want to scan only nearby peripherals, so get close to your device !!
Bluefruit.Scanner.setInterval(160, 80); // in unit of 0.625 ms
// only invoke callback if one of these services are advertised --> check for FTMS only later
Bluefruit.Scanner.filterUuid(UUID16_SVC_CYCLING_POWER, UUID16_SVC_CYCLING_SPEED_AND_CADENCE, UUID16_SVC_FITNESS_MACHINE);
Bluefruit.Scanner.useActiveScan(true);
Bluefruit.Scanner.start(0); // 0 = Don't stop scanning or n = after n/100 seconds
#ifdef DEBUG
Serial.println("Start Scanning for CPS, CSC and FTMS!");
delay(100); // To show print message !
#endif
}

void Client_Enable_Notify_Indicate(void)
{
// Reaching here means we are ready to go, let's enable Chars with Indicate/Notify
// ------------------------- Enable FTMS Notify and Indicate ---------------------------------------
if ( client_FTM_ControlPoint_Chr.enableIndicate() ) { // MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client FTM Control Point Response Messages");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable indicate for Client FTM Control Point Characteristic.");
Serial.println("FTMS (trainer) is controlled by another Client (Training App)!");
#endif
Bluefruit.disconnect(client_Connection_Handle);
return;
}

if ( client_FTM_Status_Chr.enableNotify() ) { // MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client FTM Status values");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable notify for Client FTM Status Characteristic.");
Serial.println("FTMS (trainer) is controlled by another Client (Training App)!");
#endif
Bluefruit.disconnect(client_Connection_Handle);
return;
}

if ( client_FTM_TrainingStatus_Chr.enableNotify() ) { // NOT MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client FTM Training Status values");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable notify for Client FTM Training Status Characteristic.");
#endif
}

if ( client_FTM_IndoorBikeData_Chr.enableNotify() ) { // NOT MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client FTM Indoor Bike Data values");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable notify for Client FTM Indoor Bike Data Characteristic.");
#endif
}
// ------------------------- Enable FTMS Notify and Indicate ---------------------------------------
// --------------------- Enable CP and CSC Notify and Indicate ------------------------------------
if ( client_CP_Measurement_Chr.enableNotify() ) { // NOT MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client CP Measurement values");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable notify for Client CP Measurement Characteristic.");
#endif
}

if ( client_CP_ControlPoint_Chr.enableIndicate() ) { // NOT MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client CP Control Point Responses");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable indicate for Client CP Control Point Characteristic.");
#endif
}

if ( client_CSC_Measurement_Chr.enableNotify() ) { // NOT MANDATORY
#ifdef DEBUG
Serial.println("Ready to receive Client CSC Measurement values");
#endif
} else {
#ifdef DEBUG
Serial.println(">>> Couldn't enable notify for Client CSC Measurement Characteristic.");
#endif
}
// ------------------------- Enable CP and CSC Notify and Indicate --------------------------------
}

/**

Hooked callback that triggered when a value is sent
@param chr Pointer client characteristic that event occurred,
@param data Pointer to received data
@param len Length of received data
/
void client_FTM_TrainingStatus_Notify_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG
uint8_t SDataLen = (uint8_t)len;
uint8_t SDataBuf[SDataLen] = {};
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw FTM Training Status Data: [%d] [ ", len);
for (int i = 0; i < sizeof(SDataBuf); i++) {
SDataBuf[i] = *data++;
Serial.printf("%02X ", SDataBuf[i], HEX);
}
Serial.println("] ");
#endif
}

/**

Hooked callback that triggered when a value is sent
@param chr Pointer client characteristic that event occurred,
@param data Pointer to received data
@param len Length of received data
/
void client_FTM_IndoorBikeData_Notify_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG
// testing
ParseIndoorBikeData(data, len);
#endif
}

#ifdef DEBUG
void ParseIndoorBikeData(uint8_t* data, uint16_t len)
{
// ---> IBD Buffer Data Length depends on data flagged to be present !!!!
uint8_t IBDDataLen = (uint8_t)len;
uint8_t IBDDataBuf[IBDDataLen] = {};
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw FTM Indoor Bike Data: [%d] [ ", len);
for (int i = 0; i < sizeof(IBDDataBuf); i++) {
IBDDataBuf[i] = *data++;
Serial.printf("%02X ", IBDDataBuf[i], HEX);
}
Serial.println("]");
uint8_t offset = 0;
uint16_t flags = 0;
memcpy(&flags, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
offset += 2; // UINT16
if ((flags & 1) != 0) {
// More Data
Serial.print("More Data!");
}
// if ((flags & 2) != 0) { // (flags & 2) --> true or false Average Speed is always(?) there (tested with Elite Direto XR)
// Average Speed 0.01
uint16_t sim_Speed = 0;
memcpy(&sim_Speed, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Speed: %d KPH", (sim_Speed/100));
offset += 2; // UINT16
// }
if ((flags & 4) != 0) {
// Instantaneous Cadence 0.5
uint16_t inst_Cadence = 0;
memcpy(&inst_Cadence, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Instantaneous Cadence: %d RPM", (inst_Cadence/2));
offset += 2; // UINT16
}
if ((flags & 8) != 0) {
// Average Cadence 0.5
uint16_t av_Cadence = 0;
memcpy(&av_Cadence, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Average Cadence: %d RPM", (av_Cadence/2));
offset += 2; // UINT16
}
if ((flags & 16) != 0) {
// Total Distance 1
// Little endian format, transfer 24 bit to 32 bit variable
uint32_t tot_Distance = 0;
memcpy(&tot_Distance, &IBDDataBuf[offset], 3); // Transfer buffer fields to variable
Serial.printf(" Total Distance: %d m", tot_Distance);
offset += 3; // UINT24 16 + 8
}
if ((flags & 32) != 0) {
// Resistance Level 1
uint16_t res_Level = 0;
memcpy(&res_Level, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Resistance Level: %d ", res_Level);
offset += 2; // UINT16
}
if ((flags & 64) != 0) {
// Instantaneous Power 1
uint16_t inst_Power = 0;
memcpy(&inst_Power, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Instantaneous Power: %d Watt", inst_Power);
offset += 2; // UINT16
}
if ((flags & 128) != 0) {
// Average Power 1
uint16_t av_Power = 0;
memcpy(&av_Power, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Average Power: %d Watt", av_Power);
offset += 2; // UINT16
}
if ((flags & 256) != 0) {
// Expended Energy -> UINT16 UINT16 UINT8
// Total Energy UINT16 1
uint16_t tot_Energy = 0;
memcpy(&tot_Energy, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Tot. Energy: %d kCal", tot_Energy);
offset += 2; // UINT16
// Energy per hour UINT16 1
uint16_t Energy_hr = 0;
memcpy(&Energy_hr, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Energy/hr: %d kCal/hr", Energy_hr);
offset += 2; // UINT16
// Energy per minute UINT8 1
uint8_t Energy_pm = 0;
memcpy(&Energy_pm, &IBDDataBuf[offset], 1); // Transfer buffer fields to variable
Serial.printf(" Energy/m: %d kCal/m", Energy_pm);
offset += 1; // UINT8
}
if ((flags & 512) != 0) {
// Heart Rate 1
uint8_t Heart_Rate = 0;
memcpy(&Heart_Rate, &IBDDataBuf[offset], 1); // Transfer buffer fields to variable
Serial.printf(" Heart Rate: %d HBM", Heart_Rate);
offset += 1; // UINT8
}
if ((flags & 1024) != 0) {
// Metabolic Equivalent 0.1
uint8_t Mets = 0;
memcpy(&Mets, &IBDDataBuf[offset], 1); // Transfer buffer fields to variable
Serial.printf(" Metabolic Equivalent: %d ", Mets/10);
offset += 1; // UINT8
}
if ((flags & 2048) != 0) {
// Elapsed Time 1
uint16_t elap_time = 0;
memcpy(&elap_time, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Elapsed time: %d s", elap_time);
offset += 2; // UINT16
}
if ((flags & 4096) != 0) {
// Remaining Time 1
uint16_t rem_time = 0;
memcpy(&rem_time, &IBDDataBuf[offset], 2); // Transfer buffer fields to variable
Serial.printf(" Remaining time: %d s", rem_time);
offset += 2; // UINT16
}
Serial.println();
}
#endif

/**

Hooked callback that triggered when a value is sent
@param chr Pointer client characteristic that event occurred!
@param data Pointer to received data
@param len Length of received data
/
void client_FTM_ControlPoint_Indicate_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG
uint8_t RespBufferLen = (uint8_t)len;
uint8_t RespBuffer[RespBufferLen] = {}; // It is max 6 bytes long
// Transfer first the contents of data to buffer (array of chars)
Serial.print(" -> Client Rec'd Raw FTM Control Point Response Data: [ ");
for (int i = 0; i < sizeof(RespBuffer); i++) {
RespBuffer[i] = *data++;
Serial.printf("%02X ", RespBuffer[i], HEX);
}
Serial.println("]");
#endif
}

/**

Hooked callback that triggered when a value is sent
@param chr Pointer client characteristic that event occurred,
@param data Pointer to received data
@param len Length of received data
/
void client_FTM_Status_Notify_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG
uint8_t SDataLen = (uint8_t)len;
uint8_t SDataBuf[SDataLen] = {};
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw FTM Machine Status Data: [%d] [ ", len);
for (int i = 0; i < sizeof(SDataBuf); i++) {
SDataBuf[i] = *data++;
Serial.printf("%02X ", SDataBuf[i], HEX);
}
Serial.println("] ");
#endif
}

// Byte swap unsigned short
uint16_t swap_uint16( uint16_t val )
{
return (val << 8) | (val >> 8 );
}

// Find certain uuid in the data of the received advertising packet
bool checkForUuidPresent(const uint16_t uuid, const uint8_t* reportData, uint8_t reportDataLen)
{
// Enter uuid in printed format like 0x1826 for UUID16_SVC_FITNESS_MACHINE
// uuid is internally stored in Little Endian
for (int i = 0; i < (reportDataLen); i++) { // step 1: never miss out a position!
if( memcmp(&uuid, (reportData+i), 2) == 0) {
return true;
}
}
return false;
}

/**

Callback invoked when scanner pick up an advertising data
@param report Structural advertising data
/
void client_scan_callback(ble_gap_evt_adv_report_t report)
{
// Since we configure the scanner with filterUuid(CPS, CSC, FTMS)
// scan_callback is invoked for devices with usually CPS service advertised.
// However, we only do business with FTMS enabled Trainer types so check
// for UUID16_SVC_FITNESS_MACHINE to be present, if not --> keep scanning!
if (!checkForUuidPresent(UUID16_SVC_FITNESS_MACHINE, report->data.p_data, report->data.len)) {
return; // Keep scanning for FTMS trainer !!
}
#ifdef DEBUG
Serial.println("Found advertising Peripheral with FTMS service!, see the Raw Data packet:");
Serial.println(F("Timestamp MAC Address Rssi Data"));
Serial.printf("%09d ", millis());
// MAC is in little endian --> print reverse
Serial.printBufferReverse(report->peer_addr.addr, 6, ':');
Serial.print(F(" "));
Serial.print(report->rssi);
Serial.print(F(" "));
Serial.printBuffer(report->data.p_data, report->data.len, '-');
Serial.println();
#endif
Bluefruit.Central.connect(report);
}

#ifdef DEBUG
void PrintPeerAddress(uint8_t addr[6])
{
for (int i = 1; i < 6; i++) {
// Display byte by byte in HEX reverse: little Endian
Serial.printf("%02X:",addr[(6-i)], HEX);
}
Serial.printf("%02X ",addr[0], HEX);
}
#endif

/**

Callback invoked when an connection is established
@param conn_handle
/
void client_connect_callback(uint16_t conn_handle)
{
char peripheral_name[MAX_PAYLOAD] = { 0 };
uint8_t peripheral_addr[6] = {0};
// Get the reference to current connection
BLEConnection connection = Bluefruit.Connection(conn_handle);
connection->getPeerName(peripheral_name, sizeof(peripheral_name));
ble_gap_addr_t peer_address = connection->getPeerAddr();
memcpy(peripheral_addr, peer_address.addr, 6);
#ifdef DEBUG
Serial.printf("Feather nRF52 (Central) connected to Trainer (Peripheral) device: [%s] MAC Address: ", peripheral_name);
PrintPeerAddress(peripheral_addr);
Serial.println();
#endif
client_Connection_Handle = conn_handle;
#ifdef DEBUG
Serial.println("Now checking all Client Services and Characteristics!");
Serial.println("If Mandatory Services Fail --> the Client will disconnect!");
#endif
// ---------------------------- GA and DIS SERVICE ------------------------------------------
#ifdef DEBUG
Serial.println("First checking Generic Access and Device Information Services and Characteristics!");
#endif
// If Generic Access is not found then go on.... NOT FATAL !

while (!(client_GenericAccess_Service.discover(conn_handle))) {
if ( client_GenericAccess_Service.discover(conn_handle) ) {
#ifdef DEBUG
Serial.print(F("Found Client Generic Access\n"));
#endif
if ( client_GA_DeviceName_Chr.discover() ) {
client_GA_DeviceName_Chr.read(client_GA_DeviceName_Data, sizeof(client_GA_DeviceName_Data));
#ifdef DEBUG
Serial.printf(" -> Client Reads Device Name: [%s]\n", client_GA_DeviceName_Data);
#endif
}
if ( client_GA_Appearance_Chr.discover() ) {
client_GA_Appearance_Value = client_GA_Appearance_Chr.read16();
#ifdef DEBUG
Serial.printf(" -> Client Reads Appearance: [%d]\n", client_GA_Appearance_Value);
#endif
}
} // GA
}
while (!( client_DIS_Service.discover(conn_handle) )){
// If DIS is not found then go on.... NOT FATAL !
if ( client_DIS_Service.discover(conn_handle) ) {
#ifdef DEBUG
Serial.print(F("Found Client Device Information\n"));
#endif
// 1
if ( client_DIS_ManufacturerName_Chr.discover() ) {
// read and print out Manufacturer
if ( client_DIS_ManufacturerName_Chr.read(client_DIS_Manufacturer_Str, sizeof(client_DIS_Manufacturer_Str)) ) {
#ifdef DEBUG
Serial.printf(" -> Client Reads Manufacturer: [%s]\n", client_DIS_Manufacturer_Str);
#endif
}
} // 1
// 2
if ( client_DIS_ModelNumber_Chr.discover() ) {
// read and print out Model Number
if ( client_DIS_ModelNumber_Chr.read(client_DIS_ModelNumber_Str, sizeof(client_DIS_ModelNumber_Str)) ) {
#ifdef DEBUG
Serial.printf(" -> Client Reads Model Number: [%s]\n", client_DIS_ModelNumber_Str);
#endif
}
} // 2
// 3
if ( client_DIS_SerialNumber_Chr.discover() ) {
// read and print out Serial Number
if ( client_DIS_SerialNumber_Chr.read(client_DIS_SerialNumber_Str, sizeof(client_DIS_SerialNumber_Str)) ) {
#ifdef DEBUG
Serial.printf(" -> Client Reads Serial Number: [%s]\n", client_DIS_SerialNumber_Str);
#endif
}
} // 3
} // DIS
}

// ---------------------------- END GA and DIS SERVICE ------------------------------------------------

// -----------------------------FTM SERVICE ------------------------------------------------------------
#ifdef DEBUG
Serial.print("Discovering Mandatory Client Fitness Machine (FTM) Service ... ");
#endif
// If FTM is not found, disconnect, resume scanning, and return
if ( client_FitnessMachine_Service.discover(conn_handle) )
{
#ifdef DEBUG
BLEConnection* conn = Bluefruit.Connection(conn_handle);
uint16_t max_payload = conn->getMtu()-3;
uint16_t data_length = conn->getDataLength();
Serial.print("Found it! ");
Serial.printf("FTMS Max Payload: %d Data Length: %d\n", max_payload, data_length);
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client FTM Service is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
}

#ifdef DEBUG
Serial.print("Discovering Client FTM Control Point Characteristic ... ");
#endif
// If FTM Control Point is not found, disconnect, resume scanning, and return
if ( client_FTM_ControlPoint_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client FTM Control Point Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
}

#ifdef DEBUG
Serial.print("Discovering Client FTM Status Characteristic ... ");
#endif
// If FTM Status is not found, disconnect, resume scanning, and return
if ( client_FTM_Status_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client FTM Status Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
}

#ifdef DEBUG
Serial.print("Discovering Client FTM Training Status Characteristic ... ");
#endif
// FTM Training Status is NOT MANDATORY
if ( client_FTM_TrainingStatus_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! Not Mandatory");
#endif
}
/*
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client FTM Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
*/

#ifdef DEBUG
Serial.print("Discovering Client FTM Supported Resistance Level Range Characteristic ... ");
#endif
// FTM SupportedResistanceLevelRange is not mandatory!
if ( client_FTM_SupportedResistanceLevelRange_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Read Supported Resistance Level Range Data
client_FTM_SupportedResistanceLevelRange_Chr.read(client_FTM_SupportedResistanceLevelRange_Data, 6);
#ifdef DEBUG
Serial.print(" -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ ");
for (int i = 0; i < sizeof(client_FTM_SupportedResistanceLevelRange_Data); i++) {
Serial.printf("%02X ", client_FTM_SupportedResistanceLevelRange_Data[i], HEX);
} // for
Serial.println("] ");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! NOT mandatory!");
#endif
}
/*
Serial.println("Disconnecting since Client FTM Supported Resistance Level Range Characteristic is mandatory!");
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
*/

#ifdef DEBUG
Serial.print("Discovering Client FTM Supported Power Range Characteristic ... ");
#endif
// FTM SupportedPowerRange is not mandatory!
if ( client_FTM_SupportedPowerRange_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Read Supported Resistance Level Range values
client_FTM_SupportedPowerRange_Chr.read(client_FTM_SupportedPowerRange_Data, 6);
#ifdef DEBUG
Serial.print(" -> Client Reads Raw FTM Supported Power Range bytes: [6] [ ");
for (int i = 0; i < sizeof(client_FTM_SupportedPowerRange_Data); i++) {
Serial.printf("%02X ", client_FTM_SupportedPowerRange_Data[i], HEX);
} // for
Serial.println("] ");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! NOT mandatory!");
#endif
}
/*
#ifdef DEBUG
Serial.println("Disconnecting since Client FTM Supported Power Range Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
*/

#ifdef DEBUG
Serial.print("Discovering Client FTM Indoor Bike Data Characteristic ... ");
#endif
// FTM Indoor Bike Data is not mandatory
if ( client_FTM_IndoorBikeData_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! Not Mandatory");
#endif
}
/*
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client FTM Indoor Bike Data Characteristic is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
/
// ---------------------------- End FTM SERVICE ---------------------------------------------
// ---------------------------- CP SERVICE --------------------------------------------------
#ifdef DEBUG
Serial.print("Discovering Client Cycling Power (CP) Service ... ");
#endif
// If CPS is not found, disconnect, resume scanning, and return
if ( client_CyclingPower_Service.discover(conn_handle) )
{
#ifdef DEBUG
BLEConnection conn = Bluefruit.Connection(conn_handle);
uint16_t max_payload = conn->getMtu()-3;
uint16_t data_length = conn->getDataLength();
Serial.print("Found it! ");
Serial.printf("CPS Max Payload: %d Data Length: %d\n", max_payload, data_length);
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client Cyling Power Service is mandatory!");
#endif
// MANDATORY so disconnect since we couldn't find the service
Bluefruit.disconnect(conn_handle);
return;
}

#ifdef DEBUG
Serial.print("Discovering Client CP Measurement characteristic ... ");
#endif
if ( !client_CP_Measurement_Chr.discover() )
{
// Measurement chr is mandatory, if it is not found (valid), then disconnect
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client CP Measurement Characteristic is mandatory!");
#endif
Bluefruit.disconnect(conn_handle);
return;
} else {
#ifdef DEBUG
Serial.println("Found it!");
#endif
}

#ifdef DEBUG
Serial.print("Discovering Client CP Control Point characteristic ... ");
#endif
if ( client_CP_ControlPoint_Chr.discover() )
{
// CP Control Point chr is not mandatory
#ifdef DEBUG
Serial.println("Found it!");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! NOT Mandatory!");
#endif
}

#ifdef DEBUG
Serial.print("Discovering Client CP Feature characteristic ... ");
#endif
if ( client_CP_Feature_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Configure the Cycle Power Feature characteristic
// Properties = Read
// Min Len = 1
// Max Len = 32
// B0:3 = UINT8 - Cycling Power Feature (MANDATORY)
// b0 = Pedal power balance supported; 0 = false, 1 = true
// b1 = Accumulated torque supported; 0 = false, 1 = true
// b2 = Wheel revolution data supported; 0 = false, 1 = true
// b3 = Crank revolution data supported; 0 = false, 1 = true
// b4 = Extreme magnatudes supported; 0 = false, 1 = true
// b5 = Extreme angles supported; 0 = false, 1 = true
// b6 = Top/bottom dead angle supported; 0 = false, 1 = true
// b7 = Accumulated energy supported; 0 = false, 1 = true
// b8 = Offset compensation indicator supported; 0 = false, 1 = true
// b9 = Offset compensation supported; 0 = false, 1 = true
// b10 = Cycling power measurement characteristic content masking supported; 0 = false, 1 = true
// b11 = Multiple sensor locations supported; 0 = false, 1 = true
// b12 = Crank length adj. supported; 0 = false, 1 = true
// b13 = Chain length adj. supported; 0 = false, 1 = true
// b14 = Chain weight adj. supported; 0 = false, 1 = true
// b15 = Span length adj. supported; 0 = false, 1 = true
// b16 = Sensor measurement context; 0 = force, 1 = torque
// b17 = Instantaineous measurement direction supported; 0 = false, 1 = true
// b18 = Factory calibrated date supported; 0 = false, 1 = true
// b19 = Enhanced offset compensation supported; 0 = false, 1 = true
// b20:21 = Distribtue system support; 0 = legacy, 1 = not supported, 2 = supported, 3 = RFU
// b22:32 = Reserved

// Read 32-bit client_CP_Feature_Chr value
client_CP_Feature_Flags = client_CP_Feature_Chr.read32();
#ifdef DEBUG
const uint8_t CPFC_FIXED_DATALEN = 4;
uint8_t cpfcData[CPFC_FIXED_DATALEN] = {(uint8_t)(client_CP_Feature_Flags & 0xff), (uint8_t)(client_CP_Feature_Flags >> 8),
(uint8_t)(client_CP_Feature_Flags >> 16), (uint8_t)(client_CP_Feature_Flags >> 24)};
Serial.print(" -> Client Reads Raw CP Feature bytes: [4] [ ");
for (int i = 0; i < CPFC_FIXED_DATALEN; i++) {
if ( i <= sizeof(cpfcData)) {
Serial.printf("%02X ", cpfcData[i], HEX);
}
}
Serial.println("] ");
for (int i = 0; i < sizeof(client_CP_Feature_Str); i++) {
if ( client_CP_Feature_Flags & (1 << i) )
{
Serial.println(client_CP_Feature_Str[i]);
}
}
#endif
} else {
#ifdef DEBUG
Serial.println("NOT Found! NOT Mandatory!");
#endif
}

#ifdef DEBUG
Serial.print("Discovering Client CP Sensor Location characteristic ... ");
#endif
if ( client_CP_Location_Chr.discover() )
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// The Sensor Location characteristic
// Properties = Read
// Min Len = 1
// Max Len = 1
// B0:1 = UINT8 - Sensor Location

// Read 8-bit client CP sensor location value
client_CP_Location_Value = client_CP_Location_Chr.read8();

#ifdef DEBUG
Serial.print(" -> Client Reads CP Location Sensor: ");
Serial.printf("Loc#: %d %s\n", client_CP_Location_Value, client_Sensor_Location_Str[client_CP_Location_Value]);
#endif
} else {
#ifdef DEBUG
Serial.println("NOT Found! NOT Mandatory!");
#endif
}
// ---------------------------- END CP SERVICE ------------------------------------------------
// ---------------------------- CSC SERVICE --------------------------------------------------
#ifdef DEBUG
Serial.print("Discovering Cycling Speed and Cadence (CSC) Service ... ");
#endif
if ( client_CyclingSpeedCadence_Service.discover(conn_handle) ) // UUID16_SVC_CYCLING_SPEED_AND_CADENCE
{
#ifdef DEBUG
BLEConnection* conn = Bluefruit.Connection(conn_handle);
uint16_t max_payload = conn->getMtu()-3;
uint16_t data_length = conn->getDataLength();
Serial.print("Found it! ");
Serial.printf("CSCS Max Payload: %d Data Length: %d\n", max_payload, data_length);
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! CSC Service is Not Mandatory!");
#endif
return; // NO CSC -> end of client_connect_callback !!
}
/*
// Is Mandatory
#ifdef DEBUG
Serial.println("Not Found and disconnecting!");
Serial.println("CSC Service is mandatory!");
#endif
Bluefruit.disconnect(conn_handle);
return;
*/

// Test for client CSC Characteristics when the client CSC Service is existing
#ifdef DEBUG
Serial.print("Discovering Client CSC Measurement CHR ... ");
#endif
if ( client_CSC_Measurement_Chr.discover() ) // UUID16_CHR_CSC_MEASUREMENT
{
#ifdef DEBUG
Serial.println("Found it! ");
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! Not Mandatory!");
#endif
}
/*
// Is Mandatory
#ifdef DEBUG
Serial.println("Not Found!");
Serial.println("Disconnecting since Client CSC Measurement CHR is mandatory!");
#endif
Bluefruit.disconnect(conn_handle);
return;
*/

#ifdef DEBUG
Serial.print("Discovering Client CSC Location CHR ... ");
#endif
if ( client_CSC_Location_Chr.discover() ) // UUID16_CHR_SENSOR_LOCATION
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Read 16-bit client CSC sensor location value
client_CSC_Location_Value = client_CSC_Location_Chr.read8();
#ifdef DEBUG
Serial.print(" -> Client Reads CSC Location Sensor: ");
Serial.printf("Loc#: %d %s\n", client_CSC_Location_Value, client_Sensor_Location_Str[client_CSC_Location_Value]);
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! NOT Mandatory!");
#endif
}

#ifdef DEBUG
Serial.print("Discovering Client CSC Feature CHR ... ");
#endif
if ( client_CSC_Feature_Chr.discover() ) // UUID16_CHR_CSC_FEATURE
{
#ifdef DEBUG
Serial.println("Found it!");
#endif
// Read sensor CSC Feature value in 16 bit
client_CSC_Feature_Flags = client_CSC_Feature_Chr.read16();
#ifdef DEBUG
uint8_t cscfcData[CSC_FEATURE_FIXED_DATALEN] = { (uint8_t)(client_CSC_Feature_Flags & 0xff), (uint8_t)(client_CSC_Feature_Flags >> 8) }; // Little Endian Representation
Serial.printf(" -> Client Reads Raw CSC Feature bytes: [2] [ ");
for (int i = 0; i < sizeof(cscfcData); i++) {
Serial.printf("%02X ", cscfcData[i], HEX);
}
Serial.println("] ");
for (int i = 0; i < sizeof(client_CSC_Feature_Str); i++) {
if ( (client_CSC_Feature_Flags & (1 << i)) != 0 )
{
Serial.println(client_CSC_Feature_Str[i]);
}
}
#endif
} else {
#ifdef DEBUG
Serial.println("Not Found! NOT Mandatory!");
#endif
}
// ---------------------------- END CSC SERVICE ---------------------------------------------
} // End client_connect_callback

/**

Callback invoked when a connection is dropped
@param conn_handle
@param reason is a BLE_HCI_STATUS_CODE which can be found in ble_hci.h
*/
void client_disconnect_callback(uint16_t conn_handle, uint8_t reason)
{
client_Connection_Handle = BLE_CONN_HANDLE_INVALID;
#ifdef DEBUG
Serial.print("Client Disconnected, reason = 0x"); Serial.println(reason, HEX);
Serial.println(">>> Restart the Feather nRF52 Client for a new run! <<<");
#endif
}

/**

Hooked callback that triggered when a measurement value is sent from peripheral
@param chr Pointer client characteristic that even occurred,

         in this example it should be cpmc

@param data Pointer to received data
@param len Length of received data
/
void client_CP_Measurement_Chr_notify_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG_CP_MEASUREMENT
uint8_t buffer[len]= {}; /*{ (uint8_t)(cpmcDef & 0xff), (uint8_t)(cpmcDef >> 8), // flags
(uint8_t)(powerOut & 0xff), (uint8_t)(powerOut >> 8), // inst. power
0, // bal
0, 0, // torque
0, 0, 0, 0, // cum. rev
0, 0, // wheel time
0, 0, // cum. crank
0, 0, // crank time
0, 0, // max force
0, 0, // min force
0, 0, // max tor
0, 0, // min tor
0, 0, // max ang
0, 0, // min ang
0, 0, // tdc
0, 0, // bdc
0, 0 }; // total energy
*/
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw CP Data: [%d] [ ", len);
for (int i = 0; i < sizeof(buffer); i++) {
if ( i <= sizeof(buffer)) {
buffer[i] = *data++;
Serial.printf("%02X ", buffer[i], HEX);
}
}
Serial.print("] ");

uint8_t offset = 0;
// Get flags field
uint16_t flags = 0;
memcpy(&flags, &buffer[offset], 2); // Transfer buffer fields to variable
offset += 2; // UINT16
// Get Instantaneous Power values UINT16
uint16_t PowerValue = 0;
memcpy(&PowerValue, &buffer[offset], 2); // Transfer buffer fields to variable
offset += 2; // UINT16
Serial.printf("Instantaneous Power: %4d\n", PowerValue);
// Get the other CP measurement values
if ((flags & 1) != 0) {
// Power Balance Present
Serial.print(" --> Pedal Power Balance!");
}
if ((flags & 2) != 0) {
// Accumulated Torque
Serial.println(" --> Accumulated Torque!");
}
// etcetera...
#endif
} // End cpmc_notify_callback

/**

Hooked callback that triggered when a measurement value is sent from peripheral
@param chr Pointer client characteristic that even occurred,

         in this example it should be client_CP_ControlPoint_Chr

@param data Pointer to received data
@param len Length of received data
/
void client_CP_ControlPoint_Chr_indicate_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
/*
static const unsigned MAX_CONTROL_BYTES = 5;
const uint8_t RESPONSE_SUCCESS = 1;
const uint8_t RESPONSE_OP_CODE_NOT_SUPPORTED = 2;
const uint8_t RESPONSE_INVALID_PARAMETER = 3;
const uint8_t RESPONSE_OPERATION_FAILED = 4;
const uint8_t OPCODE_RESPONSE_CODE = 32;
Len = 3
cpcpData[0] = Response Code = 0x20 // 32 Decimal
cpcpData[1] = OpCode
cpcpData[2] = responseValue
Len = 5
cpcpData[3] = (uint8_t)(responseParameter & 0xFF);
cpcpData[4] = (uint8_t)(responseParameter >> 8);
*/

// Handle the response message

#ifdef DEBUG
uint8_t cpcpDataLen = (uint8_t)len;
uint8_t cpcpData[cpcpDataLen]= {};
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw CP Control Point Data: [%d] [ ", len);
for (int i = 0; i < sizeof(cpcpData); i++) {
cpcpData[i] = *data++;
Serial.printf("%02X ", cpcpData[i], HEX);
}
Serial.print("] ");
#endif
}

/**

Hooked callback that triggered when a measurement value is sent from peripheral
@param chr Pointer client characteristic that even occurred,

         in this example it should be cpmc

@param data Pointer to received data
@param len Length of received data
/
void client_CSC_Measurement_Chr_notify_callback(BLEClientCharacteristic chr, uint8_t* data, uint16_t len)
{
#ifdef DEBUG_CSC_MEASUREMENT
uint8_t buffer[len]= {};
// Transfer first the contents of data to buffer (array of chars)
Serial.printf(" -> Client Rec'd Raw CSC Data: [%d] [ ", len);
for (int i = 0; i < len; i++) {
if ( i <= sizeof(buffer)) {
buffer[i] = data++;
Serial.printf("%02X ", buffer[i], HEX);
}
}
Serial.print("] ");
uint8_t offset = 0;
// we define the offset that is to be used when reading the next field
// Size of variables (e.g. 2 (16) or 4 bytes (32)) are constants in BluetoothGattCharacteristic
// these represent the values you can find in the "Value Fields" table in the "Format" column
// Read the Flags field at buffer[0]
uint8_t flags = buffer[offset];
offset += 1; // UINT8
// we have to check the flags' nth bit to see if C1 field exists
if ((flags & 1) != 0) {
uint32_t cum_wheel_rev = 0;
memcpy(&cum_wheel_rev, &buffer[offset], 4);
offset += 4; // UINT32
uint16_t last_wheel_event = 0;
memcpy(&last_wheel_event, &buffer[offset], 2);
offset += 2; // UINT16
Serial.printf(" Cum. wheel rev.: %d Last wheel event: %d ", cum_wheel_rev, last_wheel_event);
/ Calculation of speed at the Collector can be derived from the wheel circumference and
data in two successive measurements. The Collector calculation can be performed as
shown below:
Speed = (Difference in two successive Cumulative Wheel Revolution values * Wheel Circumference)

    / (Difference in two successive Last Wheel Event Time values)

/
}
// we have to check the flags' nth bit to see if C2 field exists
if ((flags & 2) != 0) {
uint16_t cum_cranks = 0;
memcpy(&cum_cranks, &buffer[offset], 2);
offset += 2; // UINT16
uint16_t last_crank_event = 0;
memcpy(&last_crank_event, &buffer[offset], 2);
offset += 2; // UINT16
Serial.printf(" Cum cranks: %d Last crank event: %d", cum_cranks, last_crank_event);
/ Calculation of cadence at the Collector can be derived from data in two successive

measurements. The Collector calculation can be performed as shown below:
Cadence = (Difference in two successive Cumulative Crank Revolution values)

      / (Difference in two successive Last Crank Event Time values)

*/
}
// etcetera...
Serial.println();
#endif
}

from simcline.

le-joebar commented on July 23, 2024

Dear Jörghen,

Here is the disappointing result.

The problem is still the same no feedback with V0.27

Let's not lose heart!

123456789101112131415161718192021
/*********************************************************************
This is programming code for the nRF52 based Bluefruit BLE boards

MIT license, check LICENSE for more information
All text must be included in any redistribution

Message (Enter to send message to 'Adafruit ItsyBitsy nRF52840 Express' on 'COM11')
New Line
115200 baud
16:59:01.080 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
16:59:01.080 -> ----------------- Version 02.7 ------------------
16:59:01.080 -> Initialise the Bluefruit nRF52 module: Client (Central)
16:59:01.205 -> FTMS and Chars 'initialized'
16:59:01.205 -> CPS and Chars 'initialized'
16:59:01.205 -> CSCS and Chars 'initialized'
16:59:01.205 -> GA and Chars 'initialized'
16:59:01.205 -> DIS and Chars 'initialized'
16:59:01.205 -> Start Scanning for CPS, CSC and FTMS!
16:59:01.434 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
16:59:01.434 -> Timestamp MAC Address Rssi Data
16:59:01.434 -> 000091471 F8:9C:FC:53:5E:49 -59 09-02-16-18-26-18-18-18-0A-18
16:59:01.575 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
16:59:01.575 -> Now checking all Client Services and Characteristics!
16:59:01.575 -> If Mandatory Services Fail --> the Client will disconnect!
16:59:01.575 -> First checking Generic Access and Device Information Services and Characteristics!
16:59:01.668 -> Found Client Generic Access
16:59:01.808 -> -> Client Reads Device Name: [Zwift Hub]
16:59:02.042 -> -> Client Reads Appearance: [0]
16:59:02.042 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Not Found!
16:59:02.042 -> Disconnecting since Client FTM Service is mandatory!
16:59:02.121 -> Client Disconnected, reason = 0x16
16:59:02.121 -> >>> Restart the Feather nRF52 Client for a new run! <<<
16:59:12.257 -> Feather nRF52 Client/Central: CPS, CSC and FTMS
16:59:12.257 -> ----------------- Version 02.7 ------------------
16:59:12.257 -> Initialise the Bluefruit nRF52 module: Client (Central)
16:59:12.257 -> FTMS and Chars 'initialized'
16:59:12.257 -> CPS and Chars 'initialized'
16:59:12.257 -> CSCS and Chars 'initialized'
16:59:12.257 -> GA and Chars 'initialized'
16:59:12.257 -> DIS and Chars 'initialized'
16:59:12.257 -> Start Scanning for CPS, CSC and FTMS!
16:59:12.258 -> Found advertising Peripheral with FTMS service!, see the Raw Data packet:
16:59:12.258 -> Timestamp MAC Address Rssi Data
16:59:12.258 -> 000001100 F8:9C:FC:53:5E:49 -55 09-02-16-18-26-18-18-18-0A-18
16:59:12.258 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
16:59:12.258 -> Now checking all Client Services and Characteristics!
16:59:12.258 -> If Mandatory Services Fail --> the Client will disconnect!
16:59:12.258 -> First checking Generic Access and Device Information Services and Characteristics!
16:59:12.266 -> Found Client Generic Access
16:59:12.266 -> -> Client Reads Device Name: [Zwift Hub]
16:59:12.266 -> -> Client Reads Appearance: [1152]
16:59:12.266 -> Found Client Device Information
16:59:12.266 -> -> Client Reads Manufacturer: [Zwift]

from simcline.

le-joebar commented on July 23, 2024

Here is the result of FTMS_Zwift_Bridge_v023:

17:15:10.800 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS
17:15:10.800 -> ------------------ Version 02.3 ---------------------
17:15:10.804 -> FTM Service and Chars are 'initialized'
17:15:10.804 -> CP Service and Chars are 'initialized'
17:15:10.804 -> CSC Service and Chars are 'initialized'
17:15:10.804 -> Generic Access Service and Chars are 'initialized'
17:15:10.804 -> Device Information Service and Chars are 'initialized'
17:15:10.804 -> Start Client-side Scanning for CPS, CSC and FTMS!
17:15:10.805 -> Found advertising Peripheral with FTMS enabled! See Raw data packet:
17:15:10.805 -> Timestamp Addr Rssi Data
17:15:10.805 -> 000001606 F8:9C:FC:53:5E:49 -55 09-02-16-18-26-18-18-18-0A-18
17:15:10.805 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
17:15:10.805 -> Now checking all mandatory Client Services and Characteristics!
17:15:10.805 -> If Mandatory Services Fail --> the Client will disconnect!
17:15:10.805 -> First checking Generic Access and Device Information Services and Characteristics!
17:15:10.828 -> Found Client Generic Access
17:15:10.828 -> -> Client Reads Device Name: [Zwift Hub]
17:15:10.828 -> -> Client Reads Appearance: [1152]
17:15:10.828 -> Found Client Device Information
17:15:10.828 -> -> Client Reads Manufacturer: [Zwift]
17:15:10.829 -> -> Client Reads Model Number: [06]
17:15:10.920 -> -> Client Reads Serial Number: [06-F89CFC535E49]
17:15:10.920 -> Discovering Mandatory Client Fitness Machine (FTM) Service ... Found it! FTMS Max Payload: 20 Data Length: 27
17:15:11.008 -> Discovering Client FTM Feature Characteristic ... Found it!
17:15:11.124 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ]
17:15:11.124 -> Discovering Client FTM Control Point Characteristic ... Found it!
17:15:11.703 -> Discovering Client FTM Status Characteristic ... Found it!
17:15:11.984 -> Discovering Client FTM Training Status Characteristic ... Not Found! Not Mandatory
17:15:12.285 -> Discovering Client FTM Supported Resistance Level Range Characteristic ... Found it!
17:15:12.402 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ]
17:15:12.402 -> Discovering Client FTM Supported Power Range Characteristic ... Found it!
17:15:12.742 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 00 00 00 00 ]
17:15:12.742 -> Discovering Client FTM Indoor Bike Data Characteristic ... Not Found! Not Mandatory
17:15:12.742 -> Discovering Client Cycling Power (CP) Service ... Not Found!
17:15:12.742 -> Disconnecting since Client Cyling Power Service is mandatory!
17:15:12.834 -> Client disconnected from Peripheral Device: [Zwift Hub], reason: [16]
17:15:27.560 -> Feather nRF52840 MITM supporting: CPS, CSC and FTMS
17:15:27.560 -> ------------------ Version 02.3 ---------------------
17:15:27.822 -> FTM Service and Chars are 'initialized'
17:15:27.822 -> CP Service and Chars are 'initialized'
17:15:27.822 -> CSC Service and Chars are 'initialized'
17:15:27.822 -> Generic Access Service and Chars are 'initialized'
17:15:27.822 -> Device Information Service and Chars are 'initialized'
17:15:27.822 -> Start Client-side Scanning for CPS, CSC and FTMS!
17:15:27.836 -> Found advertising Peripheral with FTMS enabled! See Raw data packet:
17:15:27.836 -> Timestamp Addr Rssi Data
17:15:27.836 -> 000001270 F8:9C:FC:53:5E:49 -60 09-02-16-18-26-18-18-18-0A-18
17:15:27.836 -> Feather nRF52 (Central) connected to Trainer (Peripheral) device: [Zwift Hub] MAC Address: F8:9C:FC:53:5E:49
17:15:27.836 -> Now checking all mandatory Client Services and Characteristics!
17:15:27.836 -> If Mandatory Services Fail --> the Client will disconnect!
17:15:27.836 -> First checking Generic Access and Device Information Services and Characteristics!

from simcline.

le-joebar commented on July 23, 2024

I'll see if with the "While" in the "Bridge V23" version if it's better

The cadence is OK but I don't have the Watts!?

Here is the modified code and the results :

/*********************************************************************
This is programming code for the nRF52 based Bluefruit BLE boards

    MIT license, check LICENSE for more information
    All text must be included in any redistribution

*********************************************************************/

/* -----------------------------------------------------------------------------------------------------
This code should work with all indoor cycling trainers that fully support,
Fitness Machine Service, Cycling Power Service and Cycling Speed & Cadence Service

The code links a BLE Server (a peripheral to Zwift) and a BLE Client (a central to the Trainer) with a bridge
in between, the Feather nRF52 being man-in-the-middle (MITM).
The nRF52-bridge can control, filter and alter the bi-directional interchanged data!
The client-side (central) scans and connects with the trainer relevant services: FTMS, CPS and CSC. It collects
all cyling data of the services and passes these on to the server-side....
The client-side supplies the indoor trainer with target and resistance control data.
The server-side (peripheral) advertises and enables connection with cycling apps like Zwift and collects the app's
control commands, target and resistance data. It passes these on to the client-side....
The server-side supplies the app with the generated cycling data in return.

The client plus server (MITM) are transparent to the indoor trainer as well as to the training app Zwift or alike!

Requirements: Zwift app or alike, Feather nRF52 board and a FTMS/CPS/CSC supporting indoor trainer
1) Upload and Run this code on the Feather nRF52
2) Start the Serial Monitor to catch debugging info
3) Start/Power On the indoor trainer
4) Feather nRF52 and trainer (with <name>) will pair as reported in the output
5) Start Zwift on your computer or tablet and wait....
6) Search on the Zwift pairing screens for the Feather nRF52 a.k.a. "Sim <name>"
7) Pair: Power, Cadence and Controllable one after another with "Sim <name>"
8) Optionally one can pair as well devices for heartrate and/or steering (Sterzo)
9) Start the default Zwift ride or any ride you wish

Make Serial Monitor output window visible on top of the Zwift window
Hop on the bike: do the work and feel resistance change with the road
Inspect the info presented by Serial Monitor.....

Your trainer's device <name> is modified by the bridge to "Sim <name>", to allow for a clear distinction
between the bridge (simulating your trainer) and your original trainer, when advertising the trainer's services!
You will notice this only when connecting to Zwift on the pairing screens! Notice: Zwift extends device names with
additional numbers for identification!

// -------------------------------------------------------------------------------------------
// COMPILER DIRECTIVE to allow/suppress SERIAL.PRINT messages that help debugging...
// Uncomment to activate
#define DEBUG
// Restrict activating one or more of the following DEBUG directives --> process intensive
// Have caused spurious side effects like a loss of quality of service handling!!
//#define DEBUG_CP_MEASUREMENT
//#define DEBUG_CSC_MEASUREMENT
//#define DEBUG_FTM_INDOORBIKEDATA
// --------------------------------------------------------------------------------------------

#include <bluefruit.h>

const uint8_t MAX_PAYLOAD = 20; // Max 20 byte data size for single packet BLE transfer

// Struct containing Device info to administer dis/connected devices
typedef struct
{
uint8_t PeerAddress[6];
char PeerName[MAX_PAYLOAD];
uint16_t conn_handle;
bool IsConnected;
} Device_info_t;
// -----------------------------------------------------------------
// Your hardware MAC/DEVICE ADDRESSES
// Laptop/Desktop Device Address that runs Zwift, in printed format: [00:01:02:03:04:05]
// Little Endian: in reversed order !!!!
#define LAPTOPADDRESS {0x18,0x52,0x53,0x22,0x11,0x58}
// Trainer FTMS enabled Device Address, in printed format: [00:01:02:03:04:05]
// Little Endian: in reversed order !!!!
#define TRAINERADDRESS {0x49,0x5E,0x53,0xFC,0x9C,0xF8}

// -----------------------------------------------------------------
// Initialize connectable device registration
Device_info_t Trainer = {TRAINERADDRESS, {0x00}, BLE_CONN_HANDLE_INVALID, false};
Device_info_t Laptop = { LAPTOPADDRESS, {0x00}, BLE_CONN_HANDLE_INVALID, false};
Device_info_t Smartphone = { {0x00}, {0x00}, BLE_CONN_HANDLE_INVALID, false};
// ----------------------------------------------------------------------------------

/* Generic Access
#define UUID16_SVC_GENERIC_ACCESS 0x1800
#define UUID16_CHR_DEVICE_NAME 0x2A00
#define UUID16_CHR_APPEARANCE 0x2A01
#define UUID16_CHR_PERIPHERAL_PREFERRED_CONNECTION_PARAMETERS 0x2A04 ---> not implemented
#define UUID16_CHR_CENTRAL_ADDRESS_RESOLUTION 0x2AA6 ---> not implemented
*/
BLEClientService client_GenericAccess_Service(UUID16_SVC_GENERIC_ACCESS); // Optional
BLEClientCharacteristic client_GA_Appearance_Chr(UUID16_CHR_APPEARANCE); // Read
uint16_t client_GA_Appearance_Value = 0;
BLEClientCharacteristic client_GA_DeviceName_Chr(UUID16_CHR_DEVICE_NAME); // Read, Write
unsigned char client_GA_DeviceName_Data[MAX_PAYLOAD] = {};

/* Cycling Power Service
CP Service: 0x1818
CP Characteristic: 0x2A63 (Measurement)
CP Characteristic: 0x2A65 (Feature)
CP Characteristic: 0x2A5D (Location)
CP Characteristic: 0x2A66 (Control Point)
/
BLEClientService client_CyclingPower_Service(UUID16_SVC_CYCLING_POWER); // Mandatory
BLEClientCharacteristic client_CP_Measurement_Chr(UUID16_CHR_CYCLING_POWER_MEASUREMENT); // Notify, Read, Mandatory
BLEClientCharacteristic client_CP_Feature_Chr(UUID16_CHR_CYCLING_POWER_FEATURE); // Read, optional
uint32_t client_CP_Feature_Flags = 0;
const uint8_t CP_FEATURE_DATALEN = 4; // Set MaxLen to 4
const char client_CP_Feature_Str[] = {
"Pedal power balance supported", "Accumulated torque supported", "Wheel revolution data supported", "Crank revolution data supported",
"Extreme magnitudes supported", "Extreme angles supported", "Top/bottom dead angle supported", "Accumulated energy supported",
"Offset compensation indicator supported", "Offset compensation supported", "Cycling power measurement characteristic content masking supported",
"Multiple sensor locations supported", "Crank length adj. supported", "Chain length adj. supported", "Chain weight adj. supported",
"Span length adj. supported", "Sensor measurement context", "Instantaineous measurement direction supported", "Factory calibrated date supported",
"Enhanced offset compensation supported"
};
BLEClientCharacteristic client_CP_Location_Chr(UUID16_CHR_SENSOR_LOCATION); // Read, optional
uint8_t client_CP_Location_Value = 0; // UINT8
const char* client_Sensor_Location_Str[] = { "Other", "Top of shoe", "In shoe", "Hip", "Front wheel", "Left crank", "Right crank", "Left pedal",
"Right pedal", "Front hub", "Rear dropout", "Chainstay", "Rear wheel", "Rear hub", "Chest", "Spider", "Chain ring"
};
BLEClientCharacteristic client_CP_ControlPoint_Chr(UUID16_CHR_CYCLING_POWER_CONTROL_POINT); // Indicate, Write, optional
const uint16_t CP_CONTROL_POINT_DATALEN = 5;

/*
Cycling Speed and Cadence Service
CSC Service: 0x1816
CSC Measurement Characteristic: 0x2A5B
CSC Feature Characteristic: 0x2A5C
CSC Location Characteristic: 0x2A5D
CSC Control Point Characteristic:0x2A55 ---> not implemented
/
BLEClientService client_CyclingSpeedCadence_Service(UUID16_SVC_CYCLING_SPEED_AND_CADENCE); // Mandatory
BLEClientCharacteristic client_CSC_Measurement_Chr(UUID16_CHR_CSC_MEASUREMENT); // Notify, Read, Mandatory
BLEClientCharacteristic client_CSC_Feature_Chr(UUID16_CHR_CSC_FEATURE); // Read, optional
const uint8_t CSC_FEATURE_FIXED_DATALEN = 2; // UINT16
uint16_t client_CSC_Feature_Flags = 0;
const char client_CSC_Feature_Str[] = {"Wheel rev supported", "Crank rev supported", "Multiple locations supported"};
BLEClientCharacteristic client_CSC_Location_Chr(UUID16_CHR_SENSOR_LOCATION); // Read, optional
uint8_t client_CSC_Location_Value = 0;
// Shared with CPS --> client_Sensor_Location_Str[]

/* Service Device Information
#define UUID16_SVC_DEVICE_INFORMATION 0x180A
#define UUID16_CHR_MODEL_NUMBER_STRING 0x2A24
#define UUID16_CHR_SERIAL_NUMBER_STRING 0x2A25
#define UUID16_CHR_FIRMWARE_REVISION_STRING 0x2A26 ---> not implemented
#define UUID16_CHR_HARDWARE_REVISION_STRING 0x2A27 ---> not implemented
#define UUID16_CHR_SOFTWARE_REVISION_STRING 0x2A28 ---> not implemented
#define UUID16_CHR_MANUFACTURER_NAME_STRING 0x2A29
*/
BLEClientService client_DIS_Service(UUID16_SVC_DEVICE_INFORMATION); // Optional
BLEClientCharacteristic client_DIS_ManufacturerName_Chr(UUID16_CHR_MANUFACTURER_NAME_STRING); // Read
char client_DIS_Manufacturer_Str[MAX_PAYLOAD] = {};
BLEClientCharacteristic client_DIS_ModelNumber_Chr(UUID16_CHR_MODEL_NUMBER_STRING); // Read
char client_DIS_ModelNumber_Str[MAX_PAYLOAD] = {};
BLEClientCharacteristic client_DIS_SerialNumber_Chr(UUID16_CHR_SERIAL_NUMBER_STRING); // Read
char client_DIS_SerialNumber_Str[MAX_PAYLOAD] = {};

/* Fitness Machine Service
#define UUID16_SVC_FITNESS_MACHINE 0x1826
#define UUID16_CHR_FITNESS_MACHINE_FEATURE 0x2ACC
#define UUID16_CHR_INDOOR_BIKE_DATA 0x2AD2
#define UUID16_CHR_TRAINING_STATUS 0x2AD3
#define UUID16_CHR_SUPPORTED_SPEED_RANGE 0x2AD4 ---> not implemented
#define UUID16_CHR_SUPPORTED_INCLINATION_RANGE 0x2AD5 ---> not implemented
#define UUID16_CHR_SUPPORTED_RESISTANCE_LEVEL_RANGE 0x2AD6
#define UUID16_CHR_SUPPORTED_HEART_RATE_RANGE 0x2AD7 ---> not implemented
#define UUID16_CHR_SUPPORTED_POWER_RANGE 0x2AD8
#define UUID16_CHR_FITNESS_MACHINE_CONTROL_POINT 0x2AD9
#define UUID16_CHR_FITNESS_MACHINE_STATUS 0x2ADA
*/
BLEClientService client_FitnessMachine_Service(UUID16_SVC_FITNESS_MACHINE); // Mandatory
// Service characteristics exposed by FTM Service
BLEClientCharacteristic client_FTM_Feature_Chr(UUID16_CHR_FITNESS_MACHINE_FEATURE); // Mandatory, Read
const uint8_t FTM_FEATURE_FIXED_DATALEN = 8;
uint8_t client_FTM_Feature_Data[FTM_FEATURE_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_IndoorBikeData_Chr(UUID16_CHR_INDOOR_BIKE_DATA); // Optional, Notify
BLEClientCharacteristic client_FTM_TrainingStatus_Chr(UUID16_CHR_TRAINING_STATUS); // Optional, Read & Notify
BLEClientCharacteristic client_FTM_SupportedResistanceLevelRange_Chr(UUID16_CHR_SUPPORTED_RESISTANCE_LEVEL_RANGE); // Mandatory, Read
const uint8_t FTM_SRLR_FIXED_DATALEN = 6;
uint8_t client_FTM_SupportedResistanceLevelRange_Data[FTM_SRLR_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_SupportedPowerRange_Chr(UUID16_CHR_SUPPORTED_POWER_RANGE); // Mandatory, Read
const uint8_t FTM_SPR_FIXED_DATALEN = 6;
uint8_t client_FTM_SupportedPowerRange_Data[FTM_SPR_FIXED_DATALEN];
BLEClientCharacteristic client_FTM_ControlPoint_Chr(UUID16_CHR_FITNESS_MACHINE_CONTROL_POINT); // Mandatory, Write & Indicate
BLEClientCharacteristic client_FTM_Status_Chr(UUID16_CHR_FITNESS_MACHINE_STATUS); // Mandatory, Notify

// ------------------------------------ START of SERVER DEFINITIONS -----------------------------------------------------
/* Cycling Speed and Cadence Service */
BLEService server_CyclingSpeedCadence_Service = BLEService(UUID16_SVC_CYCLING_SPEED_AND_CADENCE);
BLECharacteristic server_CSC_Measurement_Chr = BLECharacteristic(UUID16_CHR_CSC_MEASUREMENT); // Notify, Read
BLECharacteristic server_CSC_Feature_Chr = BLECharacteristic(UUID16_CHR_CSC_FEATURE); // Read
BLECharacteristic server_CSC_Location_Chr = BLECharacteristic(UUID16_CHR_SENSOR_LOCATION); // Read

/* Cycling Power Service */
BLEService server_CylingPower_Service = BLEService(UUID16_SVC_CYCLING_POWER);
BLECharacteristic server_CP_Measurement_Chr = BLECharacteristic(UUID16_CHR_CYCLING_POWER_MEASUREMENT); // Notify, Read
BLECharacteristic server_CP_Feature_Chr = BLECharacteristic(UUID16_CHR_CYCLING_POWER_FEATURE); // Read
BLECharacteristic server_CP_Location_Chr = BLECharacteristic(UUID16_CHR_SENSOR_LOCATION); // Read
BLECharacteristic server_CP_ControlPoint_Chr = BLECharacteristic(UUID16_CHR_CYCLING_POWER_CONTROL_POINT); // Indicate, Write

/* Fitness Machine Service */
BLEService server_FitnessMachine_Service = BLEService(UUID16_SVC_FITNESS_MACHINE);
BLECharacteristic server_FTM_Feature_Chr = BLECharacteristic(UUID16_CHR_FITNESS_MACHINE_FEATURE); // Read
BLECharacteristic server_FTM_IndoorBikeData_Chr = BLECharacteristic(UUID16_CHR_INDOOR_BIKE_DATA); // Notify
BLECharacteristic server_FTM_TrainingStatus_Chr = BLECharacteristic(UUID16_CHR_TRAINING_STATUS); // Notify, Read
const uint8_t FTM_TRAINING_STATUS_FIXED_DATALEN = 2; // Fixed len
BLECharacteristic server_FTM_SupportedResistanceLevelRange_Chr = BLECharacteristic(UUID16_CHR_SUPPORTED_RESISTANCE_LEVEL_RANGE); // Read
BLECharacteristic server_FTM_SupportedPowerRange_Chr = BLECharacteristic(UUID16_CHR_SUPPORTED_POWER_RANGE); // Read
BLECharacteristic server_FTM_ControlPoint_Chr = BLECharacteristic(UUID16_CHR_FITNESS_MACHINE_CONTROL_POINT); // Write & Indicate
BLECharacteristic server_FTM_Status_Chr = BLECharacteristic(UUID16_CHR_FITNESS_MACHINE_STATUS); // Notify
const uint8_t FTM_STATUS_DATALEN = 7; // Max Len was: [3] --> Notice that with de Elite Direto the size is: [7] !!

/* Device Information Service helper class instance */
BLEDis server_bledis; // Read
unsigned char FirmwareRevStr[] = "0.0.0";
unsigned char HardwareRevStr[] = "0.0.0";
unsigned char SoftwareRevStr[] = "0.0.0";

/* NORDIC UART SERVICE a.k.a. NUS
NUS Service: 6E400001-B5A3-F393-E0A9-E50E24DCCA9E
NUS RXD : 6E400002-B5A3-F393-E0A9-E50E24DCCA9E
NUS TXD : 6E400003-B5A3-F393-E0A9-E50E24DCCA9E
*/
const uint8_t UUID_NUS_SERVICE[] = {0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x01, 0x00, 0x40, 0x6E};
const uint8_t UUID_NUS_CHR_RXD[] = {0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x02, 0x00, 0x40, 0x6E};
const uint8_t UUID_NUS_CHR_TXD[] = {0x9E, 0xCA, 0xDC, 0x24, 0x0E, 0xE5, 0xA9, 0xE0, 0x93, 0xF3, 0xA3, 0xB5, 0x03, 0x00, 0x40, 0x6E};
BLEService server_NordicUart_Service = BLEService(UUID_NUS_SERVICE);
BLECharacteristic server_NUS_RXD_Chr = BLECharacteristic(UUID_NUS_CHR_RXD); // Read (Receiving Data)
BLECharacteristic server_NUS_TXD_Chr = BLECharacteristic(UUID_NUS_CHR_TXD); // Notify (Sending Data)

// ----------------------------- The Fitness Machine Control Point data type structure --------------------------------
// ---------------------------- Decoding is done in: server_FTM_ControlPoint_Chr_callback ------------------------------
const uint8_t ftmcpRequestControl = 0x00;
const uint8_t ftmcpReset = 0x01;
const uint8_t ftmcpSetTargetSpeed = 0x02;
const uint8_t ftmcpSetTargetInclination = 0x03;
const uint8_t ftmcpSetTargetResistanceLevel = 0x04;
const uint8_t ftmcpSetTargetPower = 0x05;
const uint8_t ftmcpSetTargetHeartRate = 0x06;
const uint8_t ftmcpStartOrResume = 0x07;
const uint8_t ftmcpStopOrPause = 0x08;
const uint8_t ftmcpSetTargetedExpendedEngery = 0x09;
const uint8_t ftmcpSetTargetedNumberOfSteps = 0x0A;
const uint8_t ftmcpSetTargetedNumberOfStrided = 0x0B;
const uint8_t ftmcpSetTargetedDistance = 0x0C;
const uint8_t ftmcpSetTargetedTrainingTime = 0x0D;
const uint8_t ftmcpSetTargetedTimeInTwoHeartRateZones = 0x0E;
const uint8_t ftmcpSetTargetedTimeInThreeHeartRateZones = 0x0F;
const uint8_t ftmcpSetTargetedTimeInFiveHeartRateZones = 0x10;
const uint8_t ftmcpSetIndoorBikeSimulationParameters = 0x11;
const uint8_t ftmcpSetWheelCircumference = 0x12;
const uint8_t ftmcpSetSpinDownControl = 0x13;
const uint8_t ftmcpSetTargetedCadence = 0x14;

const uint8_t FTM_CONTROL_POINT_DATALEN = 19; // Control point consists of 1 opcode (byte) and maximum 18 bytes as parameters
// This ftmcp_data_t structure represents the control point data. The first octet represents the opcode of the request
// followed by a parameter array of maximum 18 octects
typedef struct attribute( ( packed ) )
{
uint8_t OPCODE;
uint8_t OCTETS[(FTM_CONTROL_POINT_DATALEN - 1)];
} ftmcp_data_t;
typedef union // The union type automatically maps the bytes member array to the ftmcp_data_t structure member values
{
ftmcp_data_t values;
uint8_t bytes[FTM_CONTROL_POINT_DATALEN];
} ftmcp_data_ut;
// Fitness Machine Control Point Data variable
ftmcp_data_ut server_FTM_Control_Point_Data;
// ----------------------- end of server_FTM_ControlPoint_Chr_callback definitions ----------------------------

// -------------------------------------- END OF SERVER DEFINITIONS -------------------------------------------

// --------------------------------------------------------------------------------
// Global Server variables for decoding of INDOOR BIKE RESISTANCE PARAMETERS
// --------------------------------------------------------------------------------
float wind_speed = 0; // meters per second, resolution 0.001
float grade = 0; // percentage, resolution 0.01
float crr = 0; // Coefficient of rolling resistance, resolution 0.0001
float cw = 0; // Wind resistance Kg/m, resolution 0.01;
// --------------------------------------------------------------------------------

#define TIME_SPAN 5000 // Time span in millis 1000 = 1 second
unsigned long TimeInterval = 0;

void setup()
{
#ifdef DEBUG
Serial.begin(115200);
while ( !Serial ) delay(10); // for nrf52840 with native usb
Serial.println("Feather nRF52840 MITM supporting: CPS, CSC and FTMS");
Serial.println("------------------ Version 02.3 ---------------------");
#endif
// Initialize Bluefruit with maximum connections as Peripheral = 1, Central = 1
Bluefruit.begin(1, 1);
Setup_Client_FTMS();
Setup_Client_CPS();
Setup_Client_CSC();
Setup_Client_DIS();
Client_Start_Scanning();

while (Bluefruit.Scanner.isRunning()) { // do nothing else but scanning....
yield();
}
// wait enough time or go on when Client/Central is connected and all set!
TimeInterval = millis() + TIME_SPAN; // ADD just enough delay
while ( (millis() < TimeInterval) || (!Trainer.IsConnected) ) {
yield();
}

// Configure and Start the Device Information Service
#ifdef DEBUG
Serial.println("Configuring the Server Device Information Service");
#endif
server_setupDIS();
// Setup the Cycle Power Service, Speed & Cadence Service and FTMS
#ifdef DEBUG
Serial.println("Configuring the Server Cycle Power Service");
#endif
server_setupCPS();
#ifdef DEBUG
Serial.println("Configuring the Server Cadence and Speed Service");
#endif
server_setupCSC();
#ifdef DEBUG
Serial.println("Configuring the Server Fitness Machine Service");
#endif
server_setupFTMS();
#ifdef DEBUG
Serial.println("Configuring the Server NUS Service");
#endif
server_setupNUS();
// Setup and start advertising
#ifdef DEBUG
Serial.println("Setting up the Server-side advertising payload(s)");
#endif
server_startADV();
#ifdef DEBUG
Serial.println("Server-side is CPS, CSC and FTMS advertising!");
#endif
while (Bluefruit.Advertising.isRunning()) { // ONLY advertise!
yield();
}
TimeInterval = millis() + TIME_SPAN; // ADD just enough DELAY
// wait enough time or go on when Server/Peripheral is connected and set!
while ( (millis() < TimeInterval) || (!Laptop.IsConnected) ) {
yield();
}
#ifdef DEBUG
Serial.println("Client- and Server-side are Up and Running!");
#endif
}

// ---------------------- CLIENT SIDE FUNCTIONS -------------------------
void Setup_Client_FTMS(void)
{
// Initialize client FTM Service
client_FitnessMachine_Service.begin();

// Initialize client FTM Feature characteristic
client_FTM_Feature_Chr.begin();

// Initialize client FTM Training Status characteristic
client_FTM_TrainingStatus_Chr.setNotifyCallback(client_FTM_TrainingStatus_Notify_callback);
client_FTM_TrainingStatus_Chr.begin();