search

Berg0162 / simcline

Simulation of Changing Road Inclination for Indoor Cycling
GNU General Public License v3.0
29 stars 7 forks source link

Test Zwift Hub FTMS #7

Closed Berg0162 closed 1 year ago

Berg0162 commented 1 year ago 
    Hello Jorghen,

Here is the first result with FTMSClient v022

I don't know if it's good?

Next test when I receive the dongle for the Pc

Friendship, Joel

[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 [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 000000681 F8:9C:FC:53:5E:49 -60 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_GAP_EVT_DISCONNECTED : Conn Handle = 0 [GAP ] Disconnect Reason: CONN_FAILED_TO_BE_ESTABLISHED Feather nRF52 (Central) connected to Trainer (Peripheral) device: [] 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 bool BLEDiscovery::_discoverService(uint16_t, BLEClientService&, uint16_t): 79: verify failed, error = BLE_ERROR_INVALID_CONN_HANDLE Not Found! Disconnecting since Client Cyling Power Service is mandatory! Client Disconnected, reason = 0x3E

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

--------- 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:

Originally posted by @le-joebar in https://github.com/Berg0162/simcline/issues/5#issuecomment-1342980419

le-joebar commented 1 year ago

Hello Jorgen,

For the connection with Companion I will deal with it later. LittleFS is fixed.

Here are the results with esp32_FTMS_Zwift_Bridge_v010

change as follows:

//#define DEBUG_FTM_CONTROLPOINT_RESPONSE // If defined allows for parsing the Data //#define DEBUG_FTM_CONTROLPOINT_OPCODE_DATA // If defined allows for parsing and decoding Data

Core Debug Level: "Error"

Baud Rate 115200

I also put the Zwift images because it is each time from the same page that the reboot begins.

The restart happens sometimes 1 or 2 times but as you can see in the 2nd attempt the restart lasted 4 minutes !!

As soon as we arrive at this:

16:07:52.948 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 01 ] 16:07:53.040 -> Request Control of Machine! 16:07:53.396 -> Start or Resume Machine! 16:07:53.568 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 04 ] 16:07:54.468 -> Set Indoor Bike Simulation Parameters! 16:07:54.468 -> Wind speed (1000): 0.00 | Rank (100): -0.58 | Crr(10000): 0.00 | Cw(100): 0.51 16:07:54.718 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [7] [ 12 00 00 C6 FF 28 33 ]

So it's stable

Be careful because when there is this:

16:07:53.568 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 04 ] 16:07:54.468 -> Set Indoor Bike Simulation Parameters! 16:07:54.468 -> Wind speed (1000): 0.00 | Rank (100): -0.58 | Crr(10000): 0.00 | Cw(100): 0.51 16:07:54.718 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [7] [ 12 00 00 C6 FF 28 33 ]

I'm still on the page seen above and not busy riding!!

Sincerely,

Joel

Now the result :

image

15:35:18.498 -> ets Jul 29 2019 12:21:46 15:35:18.498 -> 15:35:18.498 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 15:35:18.498 -> configsip: 271414342, SPIWP:0xee 15:35:18.498 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 15:35:18.498 -> mode:DIO, clock div:1 15:35:18.539 -> load:0x3fff0030,len:1184 15:35:18.539 -> load:0x40078000,len:13160 15:35:18.539 -> load:0x40080400,len:3036 15:35:18.539 -> entry 0x400805e4 15:35:19.006 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 15:35:19.006 -> ------------------ Version 01.0 -------------------- 15:35:19.309 -> Configuring the default Generic Access Service 15:35:19.309 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 15:35:19.309 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32] 15:35:19.309 -> Configuring the Server Nordic Uart Service 15:35:19.309 -> Configuring the Server Device Information Service 15:35:19.342 -> Configuring the Server Cycle Power Service 15:35:19.342 -> Configuring the Server Cadence and Speed Service 15:35:19.342 -> Configuring the Server Fitness Machine Service 15:35:19.342 -> Configuring the Server Heart Rate Service 15:35:19.342 -> Setting up the Server advertising payload(s) 15:35:19.342 -> Setting Appearance in Advertised data to [1152] 15:35:19.342 -> Server is advertising: CPS, CSC and FTMS 15:35:19.342 -> Client Starts Scanning for Server Device with CPS, CSC and FTMS! 15:35:22.234 -> Found advertising Peripheral with FTMS enabled! See data: 15:35:22.234 -> Name: Zwift Hub, Address: f8:9c:fc:53:5e:49, appearance: 1152, manufacturer data: 4a09065e49, serviceUUID: 0x1816 15:35:22.234 -> Service Data: 15:35:22.234 -> UUID: 0x1826, Data:  15:35:22.312 -> Client Connection Parameters -> Interval: [40] Latency: [0] Supervision Timeout: [256] 15:35:22.312 -> ESP32 Client connected to Server device with Name: [Zwift Hub] MAC Address: [F8:9C:FC:53:5E:49] Handle: [0] MTU: [244] 15:35:22.312 -> Now checking all Client Services and Characteristics! 15:35:22.312 -> If Mandatory Services Fail --> the Client will disconnect! 15:35:22.733 -> Client Generic Access: Found! 15:35:23.293 -> -> Client Reads Device Name: [Zwift Hub] 15:35:23.931 -> -> Client Reads Appearance: [1152] 15:35:24.100 -> Client Device Information Service: Found! 15:35:24.427 -> -> Client Reads Manufacturer Name: [Zwift] 15:35:24.893 -> -> Client Reads Model Number: [06] 15:35:25.483 -> -> Client Reads Serial Number: [06-F89CFC535E49] 15:35:25.745 -> Client_CyclingPower_Service: Found! 15:35:26.103 -> Client_CP_Measurement_Chr: Found! 15:35:26.850 -> Client_CP_Feature_Chr: Found! 15:35:26.944 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ] 15:35:26.944 -> Wheel revolution data supported 15:35:26.944 -> Crank revolution data supported 15:35:27.253 -> Client_CP_Location_Chr: Found! 15:35:27.456 -> -> Client Reads CP Location Sensor: Loc#: 12 Rear wheel 15:35:27.662 -> Client_CyclingSpeedCadence_Service: Found! 15:35:27.972 -> Client_CSC_Measurement_Chr: Found! 15:35:28.829 -> Client_CSC_Feature_Chr: Found! 15:35:29.095 -> -> Client Reads Raw CSC Feature bytes: [2] [ 03 00 ] 15:35:29.095 -> Wheel rev supported 15:35:29.095 -> Crank rev supported 15:35:29.593 -> Client_CSC_Location_Chr: Found! 15:35:29.687 -> -> Client Reads CSC Location Sensor: Loc#: 12 Rear wheel 15:35:29.999 -> Client_FitnessMachine_Service: Found! 15:35:30.247 -> Client_FTM_Feature_Chr: Found! 15:35:30.324 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ] 15:35:30.324 -> - Fitness Machine Features: 15:35:30.324 -> Average Speed Supported 15:35:30.370 -> Cadence Supported 15:35:30.370 -> Total Distance Supported 15:35:30.370 -> Resistance Level Supported 15:35:30.370 -> Heart Rate Measurement Supported 15:35:30.370 -> Power Measurement Supported 15:35:30.370 -> - Target Setting Features: 15:35:30.370 -> Resistance Target Setting Supported 15:35:30.370 -> Power Target Setting Supported 15:35:30.370 -> Indoor Bike Simulation Parameters Supported 15:35:30.370 -> Wheel Circumference Configuration Supported 15:35:30.370 -> Spin Down Control Supported 15:35:30.696 -> Client_FTM_IndoorBikeData_Chr: Found! 15:35:32.030 -> Client_FTM_TrainingStatus_Chr: Not Found! 15:35:32.293 -> Client_FTM_SupportedResistanceLevelRange_Chr: Found! 15:35:32.433 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 15:35:32.854 -> Client_FTM_SupportedPowerRange_Chr: Found! 15:35:33.150 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 15:35:33.428 -> Client_FTM_ControlPoint_Chr: Found! 15:35:34.302 -> Client_FTM_Status_Chr: Found! 15:35:35.183 -> Client_HeartRate_Service: Found! 15:35:35.445 -> Client_HR_Measurement_Chr: Found! 15:35:36.185 -> Client_HR_Location_Chr: Found! 15:35:36.354 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest

image

15:39:53.528 -> Server Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 15:39:53.571 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 15:39:53.571 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 15:39:53.571 -> MTU updated: 255 for connection ID: 1 15:39:54.957 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 15:39:58.214 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a63] 15:39:59.336 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a5b] 15:40:00.302 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ad2] 15:40:00.912 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 15:40:01.376 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 15:40:02.232 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37]

image

15:43:04.454 -> Request Control of Machine! 15:43:04.730 -> Reset Machine! 15:43:04.858 -> Request Control of Machine! 15:43:04.891 -> Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled. 15:43:04.891 -> Memory dump at 0x400d20f0: b26508a8 00f01dc3 81004136 15:43:04.891 -> Core 1 register dump: 15:43:04.891 -> PC : 0x400d20f5 PS : 0x00060430 A0 : 0x00000000 A1 : 0x3ffd03f0
15:43:04.891 -> A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
15:43:04.925 -> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x800d20f5 A9 : 0x3ffd03d0
15:43:04.925 -> A10 : 0x3ffd0dfc A11 : 0x00000001 A12 : 0x0000000a A13 : 0x3ffd0484
15:43:04.925 -> A14 : 0x00000000 A15 : 0x3ffc3d3c SAR : 0x00000002 EXCCAUSE: 0x00000000
15:43:04.925 -> EXCVADDR: 0x00000000 LBEG : 0x400913f4 LEND : 0x40091410 LCOUNT : 0x00000000
15:43:04.962 -> 15:43:04.962 -> 15:43:04.962 -> Backtrace:0x400d20f2:0x3ffd03f0 15:43:04.962 -> 15:43:04.962 -> 15:43:04.962 -> 15:43:04.962 -> 15:43:04.962 -> ELF file SHA256: 0000000000000000 15:43:04.962 -> 15:43:04.962 -> Rebooting... 15:43:04.962 -> ets Jul 29 2019 12:21:46 15:43:04.962 -> 15:43:04.962 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 15:43:04.962 -> configsip: 271414342, SPIWP:0xee 15:43:04.962 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 15:43:04.962 -> mode:DIO, clock div:1 15:43:04.962 -> load:0x3fff0030,len:1184 15:43:04.962 -> load:0x40078000,len:13160 15:43:04.962 -> load:0x40080400,len:3036 15:43:04.962 -> entry 0x400805e4 15:43:05.463 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 15:43:05.463 -> ------------------ Version 01.0 -------------------- 15:43:05.728 -> Configuring the default Generic Access Service 15:43:05.728 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 15:43:05.728 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32] 15:43:05.728 -> Configuring the Server Nordic Uart Service 15:43:05.728 -> Configuring the Server Device Information Service 15:43:05.761 -> Configuring the Server Cycle Power Service 15:43:05.761 -> Configuring the Server Cadence and Speed Service 15:43:05.761 -> Configuring the Server Fitness Machine Service 15:43:05.761 -> Configuring the Server Heart Rate Service 15:43:05.761 -> Setting up the Server advertising payload(s) 15:43:05.761 -> Setting Appearance in Advertised data to [1152] 15:43:05.761 -> Server is advertising: CPS, CSC and FTMS 15:43:05.761 -> Client Starts Scanning for Server Device with CPS, CSC and FTMS! 15:43:09.853 -> Found advertising Peripheral with FTMS enabled! See data: 15:43:09.853 -> Name: Zwift Hub, Address: f8:9c:fc:53:5e:49, appearance: 1152, manufacturer data: 4a09065e49, serviceUUID: 0x1816 15:43:09.853 -> Service Data: 15:43:09.853 -> UUID: 0x1826, Data:  15:43:10.021 -> Client Connection Parameters -> Interval: [40] Latency: [0] Supervision Timeout: [256] 15:43:10.021 -> ESP32 Client connected to Server device with Name: [Zwift Hub] MAC Address: [F8:9C:FC:53:5E:49] Handle: [0] MTU: [244] 15:43:10.021 -> Now checking all Client Services and Characteristics! 15:43:10.021 -> If Mandatory Services Fail --> the Client will disconnect! 15:43:10.348 -> Client Generic Access: Found! 15:43:10.907 -> -> Client Reads Device Name: [Zwift Hub] 15:43:11.312 -> -> Client Reads Appearance: [1152] 15:43:11.438 -> Client Device Information Service: Found! 15:43:11.858 -> -> Client Reads Manufacturer Name: [Zwift] 15:43:12.402 -> -> Client Reads Model Number: [06] 15:43:13.058 -> -> Client Reads Serial Number: [06-F89CFC535E49] 15:43:13.323 -> Client_CyclingPower_Service: Found! 15:43:13.509 -> Client_CP_Measurement_Chr: Found! 15:43:14.198 -> Client_CP_Feature_Chr: Found! 15:43:14.368 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ] 15:43:14.368 -> Wheel revolution data supported 15:43:14.368 -> Crank revolution data supported 15:43:14.600 -> Client_CP_Location_Chr: Found! 15:43:14.724 -> -> Client Reads CP Location Sensor: Loc#: 12 Rear wheel 15:43:15.037 -> Client_CyclingSpeedCadence_Service: Found! 15:43:15.457 -> Client_CSC_Measurement_Chr: Found! 15:43:16.095 -> Client_CSC_Feature_Chr: Found! 15:43:16.266 -> -> Client Reads Raw CSC Feature bytes: [2] [ 03 00 ] 15:43:16.266 -> Wheel rev supported 15:43:16.266 -> Crank rev supported 15:43:16.608 -> Client_CSC_Location_Chr: Found! 15:43:16.702 -> -> Client Reads CSC Location Sensor: Loc#: 12 Rear wheel 15:43:17.015 -> Client_FitnessMachine_Service: Found! 15:43:17.278 -> Client_FTM_Feature_Chr: Found! 15:43:17.435 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ] 15:43:17.468 -> - Fitness Machine Features: 15:43:17.468 -> Average Speed Supported 15:43:17.468 -> Cadence Supported 15:43:17.468 -> Total Distance Supported 15:43:17.468 -> Resistance Level Supported 15:43:17.468 -> Heart Rate Measurement Supported 5:43:17.468 -> Power Measurement Supported 15:43:17.468 -> - Target Setting Features: 15:43:17.468 -> Resistance Target Setting Supported 15:43:17.468 -> Power Target Setting Supported 15:43:17.468 -> Indoor Bike Simulation Parameters Supported 15:43:17.468 -> Wheel Circumference Configuration Supported 15:43:17.514 -> Spin Down Control Supported 15:43:17.637 -> Server Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 15:43:17.637 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 15:43:17.637 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 15:43:17.637 -> MTU updated: 255 for connection ID: 1 15:43:17.716 -> Client_FTM_IndoorBikeData_Chr: Found! 15:43:19.008 -> Client_FTM_TrainingStatus_Chr: Not Found! 15:43:19.416 -> Client_FTM_SupportedResistanceLevelRange_Chr: Found! 15:43:19.724 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 15:43:20.007 -> Client_FTM_SupportedPowerRange_Chr: Found! 15:43:20.182 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 15:43:20.569 -> Client_FTM_ControlPoint_Chr: Found! 15:43:21.300 -> Client_FTM_Status_Chr: Found! 15:43:22.021 -> Client_HeartRate_Service: Found! 15:43:22.237 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a63] 15:43:22.376 -> Client_HR_Measurement_Chr: Found! 15:43:23.014 -> Client_HR_Location_Chr: Found! 15:43:23.263 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest 15:43:23.310 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a5b] 15:43:23.964 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 15:43:24.275 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ad2] 15:43:24.777 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 15:43:24.856 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 15:43:25.357 -> Request Control of Machine! 15:43:25.468 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 15:43:25.930 -> Reset Machine! 15:43:26.134 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 01 ] 15:43:26.352 -> Request Control of Machine! 15:43:26.616 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37] 15:43:26.695 -> Start or Resume Machine! 15:43:26.912 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 04 ] 15:43:27.856 -> Set Indoor Bike Simulation Parameters! 15:43:27.856 -> Wind speed (1000): 0.00 | Grade (100): -0.58 | Crr (10000): 0.00 | Cw (100): 0.51 15:43:28.169 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [7] [ 12 00 00 C6 FF 28 33 ]

Second test

image

15:57:55.669 -> ets Jul 29 2019 12:21:46 15:57:55.716 -> 15:57:55.716 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 15:57:55.716 -> configsip: 271414342, SPIWP:0xee 15:57:55.716 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 15:57:55.716 -> mode:DIO, clock div:1 15:57:55.716 -> load:0x3fff0030,len:1184 15:57:55.716 -> load:0x40078000,len:13160 15:57:55.716 -> load:0x40080400,len:3036 15:57:55.716 -> entry 0x400805e4 15:57:56.214 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 15:57:56.214 -> ------------------ Version 01.0 -------------------- 15:57:56.478 -> Configuring the default Generic Access Service 15:57:56.478 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 15:57:56.478 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32] 15:57:56.478 -> Configuring the Server Nordic Uart Service 15:57:56.478 -> Configuring the Server Device Information Service 15:57:56.511 -> Configuring the Server Cycle Power Service 15:57:56.511 -> Configuring the Server Cadence and Speed Service 15:57:56.511 -> Configuring the Server Fitness Machine Service 15:57:56.511 -> Configuring the Server Heart Rate Service 15:57:56.511 -> Setting up the Server advertising payload(s) 15:57:56.511 -> Setting Appearance in Advertised data to [1152] 15:57:56.511 -> Server is advertising: CPS, CSC and FTMS 15:57:56.511 -> Client Starts Scanning for Server Device with CPS, CSC and FTMS! 15:57:56.547 -> Found advertising Peripheral with FTMS enabled! See data: 15:57:56.547 -> Name: Zwift Hub, Address: f8:9c:fc:53:5e:49, appearance: 1152, manufacturer data: 4a09065e49, serviceUUID: 0x1816 15:57:56.585 -> Service Data: 15:57:56.585 -> UUID: 0x1826, Data:  15:57:56.678 -> Client Connection Parameters -> Interval: [40] Latency: [0] Supervision Timeout: [256] 15:57:56.678 -> ESP32 Client connected to Server device with Name: [Zwift Hub] MAC Address: [F8:9C:FC:53:5E:49] Handle: [0] MTU: [244] 15:57:56.678 -> Now checking all Client Services and Characteristics! 15:57:56.678 -> If Mandatory Services Fail --> the Client will disconnect! 15:57:57.270 -> Client Generic Access: Found! 15:57:57.660 -> -> Client Reads Device Name: [Zwift Hub] 15:57:58.203 -> -> Client Reads Appearance: [1152] 15:57:58.315 -> Client Device Information Service: Found! 15:57:59.000 -> -> Client Reads Manufacturer Name: [Zwift] 15:57:59.516 -> -> Client Reads Model Number: [06] 15:57:59.907 -> -> Client Reads Serial Number: [06-F89CFC535E49] 15:58:00.311 -> Client_CyclingPower_Service: Found! 15:58:00.530 -> Client_CP_Measurement_Chr: Found! 15:58:01.261 -> Client_CP_Feature_Chr: Found! 15:58:01.465 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ] 15:58:01.465 -> Wheel revolution data supported 15:58:01.465 -> Crank revolution data supported 15:58:01.761 -> Client_CP_Location_Chr: Found! 15:58:01.853 -> -> Client Reads CP Location Sensor: Loc#: 12 Rear wheel 15:58:02.166 -> Client_CyclingSpeedCadence_Service: Found! 15:58:02.480 -> Client_CSC_Measurement_Chr: Found! 15:58:03.176 -> Client_CSC_Feature_Chr: Found! 15:58:03.364 -> -> Client Reads Raw CSC Feature bytes: [2] [ 03 00 ] 15:58:03.364 -> Wheel rev supported 15:58:03.364 -> Crank rev supported 15:58:03.598 -> Client_CSC_Location_Chr: Found! 15:58:03.770 -> -> Client Reads CSC Location Sensor: Loc#: 12 Rear wheel 15:58:04.096 -> Client_FitnessMachine_Service: Found! 15:58:04.517 -> Client_FTM_Feature_Chr: Found! 15:58:04.829 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ] 15:58:04.866 -> - Fitness Machine Features: 15:58:04.866 -> Average Speed Supported 15:58:04.866 -> Cadence Supported 15:58:04.866 -> Total Distance Supported 15:58:04.866 -> Resistance Level Supported 15:58:04.866 -> Heart Rate Measurement Supported 15:58:04.866 -> Power Measurement Supported 15:58:04.866 -> - Target Setting Features: 15:58:04.866 -> Resistance Target Setting Supported 15:58:04.866 -> Power Target Setting Supported 15:58:04.866 -> Indoor Bike Simulation Parameters Supported 15:58:04.907 -> Wheel Circumference Configuration Supported 15:58:04.907 -> Spin Down Control Supported 15:58:05.168 -> Client_FTM_IndoorBikeData_Chr: Found! 15:58:06.270 -> Client_FTM_TrainingStatus_Chr: Not Found! 15:58:06.548 -> Client_FTM_SupportedResistanceLevelRange_Chr: Found! 15:58:06.721 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 15:58:07.095 -> Client_FTM_SupportedPowerRange_Chr: Found! 15:58:07.423 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 15:58:07.751 -> Client_FTM_ControlPoint_Chr: Found! 15:58:08.451 -> Client_FTM_Status_Chr: Found! 15:58:09.562 -> Client_HeartRate_Service: Found! 15:58:09.796 -> Client_HR_Measurement_Chr: Found! 15:58:10.712 -> Client_HR_Location_Chr: Found! 15:58:10.964 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest

image

15:59:53.270 -> Server Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 15:59:53.270 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 15:59:53.270 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 15:59:53.270 -> MTU updated: 255 for connection ID: 1 15:59:54.501 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 15:59:57.848 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a63] 15:59:59.033 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a5b] 15:59:59.983 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ad2] 16:00:00.575 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 16:00:01.088 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 16:00:01.931 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37]

image

16:02:26.530 -> Request Control of Machine! 16:02:27.169 -> Reset Machine! 16:02:27.303 -> Request Control of Machine! 16:02:27.337 -> Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled. 16:02:27.337 -> Memory dump at 0x400d20f0: b26508a8 00f01dc3 81004136 16:02:27.337 -> Core 1 register dump: 16:02:27.337 -> PC : 0x400d20f5 PS : 0x00060630 A0 : 0x00000000 A1 : 0x3ffd0140
16:02:27.339 -> A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
16:02:27.370 -> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x800d20f5 A9 : 0x3ffd0120
16:02:27.370 -> A10 : 0x3ffd0b54 A11 : 0x00000001 A12 : 0x0000000a A13 : 0x3ffd01dc
16:02:27.370 -> A14 : 0x00000000 A15 : 0x3ffc3d3c SAR : 0x00000001 EXCCAUSE: 0x00000000
16:02:27.370 -> EXCVADDR: 0x00000000 LBEG : 0x400913f4 LEND : 0x40091410 LCOUNT : 0x00000000
16:02:27.416 -> 16:02:27.416 -> 16:02:27.416 -> Backtrace:0x400d20f2:0x3ffd0140 16:02:27.416 -> 16:02:27.416 -> 16:02:27.416 -> 16:02:27.416 -> 16:02:27.416 -> ELF file SHA256: 0000000000000000 16:02:27.416 -> 16:02:27.416 -> Rebooting... 16:02:27.416 -> ets Jul 29 2019 12:21:46 16:02:27.416 -> 16:02:27.416 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 16:02:27.416 -> configsip: 271414342, SPIWP:0xee 16:02:27.416 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 16:02:27.416 -> mode:DIO, clock div:1 16:02:27.416 -> load:0x3fff0030,len:1184 16:02:27.416 -> load:0x40078000,len:13160 16:02:27.416 -> load:0x40080400,len:3036 16:02:27.416 -> entry 0x400805e4 16:02:27.916 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 16:02:27.916 -> ------------------ Version 01.0 -------------------- 16:02:28.188 -> Configuring the default Generic Access Service 16:02:28.188 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 16:02:28.188 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32] 16:02:28.188 -> Configuring the Server Nordic Uart Service 16:02:28.188 -> Configuring the Server Device Information Service 16:02:28.188 -> Configuring the Server Cycle Power Service 16:02:28.229 -> Configuring the Server Cadence and Speed Service 16:02:28.229 -> Configuring the Server Fitness Machine Service 16:02:28.229 -> Configuring the Server Heart Rate Service 16:02:28.229 -> Setting up the Server advertising payload(s) 16:02:28.229 -> Setting Appearance in Advertised data to [1152] 16:02:28.229 -> Server is advertising: CPS, CSC and FTMS 16:02:28.229 -> Client Starts Scanning for Server Device with CPS, CSC and FTMS! 16:02:32.404 -> Found advertising Peripheral with FTMS enabled! See data: 16:02:32.404 -> Name: Zwift Hub, Address: f8:9c:fc:53:5e:49, appearance: 1152, manufacturer data: 4a09065e49, serviceUUID: 0x1816 16:02:32.404 -> Service Data: 16:02:32.404 -> UUID: 0x1826, Data:  16:02:32.527 -> Client Connection Parameters -> Interval: [40] Latency: [0] Supervision Timeout: [256] 16:02:32.527 -> ESP32 Client connected to Server device with Name: [Zwift Hub] MAC Address: [F8:9C:FC:53:5E:49] Handle: [0] MTU: [244] 16:02:32.528 -> Now checking all Client Services and Characteristics! 16:02:32.528 -> If Mandatory Services Fail --> the Client will disconnect! 16:02:32.858 -> Client Generic Access: Found! 16:02:33.467 -> -> Client Reads Device Name: [Zwift Hub] 16:02:34.077 -> -> Client Reads Appearance: [1152] 16:02:34.203 -> Client Device Information Service: Found! 16:02:34.701 -> -> Client Reads Manufacturer Name: [Zwift] 16:02:35.264 -> -> Client Reads Model Number: [06] 16:02:35.921 -> -> Client Reads Serial Number: [06-F89CFC535E49] 16:02:36.154 -> Client_CyclingPower_Service: Found! 16:02:36.465 -> Client_CP_Measurement_Chr: Found! 16:02:37.227 -> Client_CP_Feature_Chr: Found! 16:02:37.368 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ] 16:02:37.368 -> Wheel revolution data supported 16:02:37.368 -> Crank revolution data supported 16:02:37.772 -> Client_CP_Location_Chr: Found! 16:02:38.006 -> -> Client Reads CP Location Sensor: Loc#: 12 Rear wheel 16:02:38.146 -> Server Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 16:02:38.146 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 16:02:38.146 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 16:02:38.285 -> MTU updated: 255 for connection ID: 1 16:02:38.319 -> Client_CyclingSpeedCadence_Service: Found!

...

16:02:46.672 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest 16:02:47.050 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37] 16:02:47.563 -> Request Control of Machine! 16:02:47.594 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:02:48.550 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:02:52.678 -> Request Control of Machine! 16:02:52.912 -> Reset Machine! 16:02:53.038 -> Request Control of Machine! 16:02:53.152 -> Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled. 16:02:53.152 -> Memory dump at 0x400d20f0: b26508a8 00f01dc3 81004136 16:02:53.152 -> Core 1 register dump: 16:02:53.152 -> PC : 0x400d20f5 PS : 0x00060430 A0 : 0x00000000 A1 : 0x3ffd03d0
16:02:53.152 -> A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
16:02:53.152 -> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x800d20f5 A9 : 0x3ffd03b0
16:02:53.183 -> A10 : 0x3ffd0de4 A11 : 0x00000001 A12 : 0x0000000a A13 : 0x3ffd046c
16:02:53.183 -> A14 : 0x00000000 A15 : 0x3ffc3d3c SAR : 0x00000002 EXCCAUSE: 0x00000000
16:02:53.183 -> EXCVADDR: 0x00000000 LBEG : 0x400913f4 LEND : 0x40091410 LCOUNT : 0x00000000
16:02:53.183 -> 16:02:53.183 -> 16:02:53.183 -> Backtrace:0x400d20f2:0x3ffd03d0 16:02:53.183 -> 16:02:53.183 -> 16:02:53.183 -> 16:02:53.183 -> 16:02:53.183 -> ELF file SHA256: 0000000000000000 16:02:53.183 -> 16:02:53.183 -> Rebooting... 16:02:53.226 -> ets Jul 29 2019 12:21:46 16:02:53.226 -> 16:02:53.226 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 16:02:53.226 -> configsip: 271414342, SPIWP:0xee 16:02:53.226 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 16:02:53.226 -> mode:DIO, clock div:1 16:02:53.226 -> load:0x3fff0030,len:1184 16:02:53.226 -> load:0x40078000,len:13160 16:02:53.226 -> load:0x40080400,len:3036 16:02:53.226 -> entry 0x400805e4 16:02:53.726 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 16:02:53.726 -> ------------------ Version 01.0 -------------------- 16:02:53.994 -> Configuring the default Generic Access Service 16:02:53.994 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 16:02:53.994 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32]

....

16:03:11.966 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest 16:03:12.405 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 16:03:12.810 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:03:12.933 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 16:03:13.622 -> Request Control of Machine! 16:03:13.886 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37] 16:03:13.982 -> Reset Machine! 16:03:14.106 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:03:14.106 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 01 ] 16:03:14.232 -> Request Control of Machine! 16:03:14.361 -> Guru Meditation Error: Core 1 panic'ed (IllegalInstruction). Exception was unhandled. 16:03:14.361 -> Memory dump at 0x400d20f0: b26508a8 00f01dc3 81004136 16:03:14.361 -> Core 1 register dump: 16:03:14.361 -> PC : 0x400d20f5 PS : 0x00060d30 A0 : 0x00000000 A1 : 0x3ffd0460
16:03:14.394 -> A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
16:03:14.394 -> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x800d20f5 A9 : 0x3ffd0440
16:03:14.394 -> A10 : 0x3ffd0e70 A11 : 0x00000001 A12 : 0x0000000a A13 : 0x3ffd04f8
16:03:14.394 -> A14 : 0x00000000 A15 : 0x3ffc3d3c SAR : 0x00000002 EXCCAUSE: 0x00000000
16:03:14.425 -> EXCVADDR: 0x00000000 LBEG : 0x400913f4 LEND : 0x40091410 LCOUNT : 0x00000000
16:03:14.425 -> 16:03:14.425 -> 16:03:14.425 -> Backtrace:0x400d20f2:0x3ffd0460 16:03:14.425 -> 16:03:14.425 -> 16:03:14.425 -> 16:03:14.425 -> 16:03:14.425 -> ELF file SHA256: 0000000000000000 16:03:14.425 -> 16:03:14.425 -> Rebooting... 16:03:14.425 -> ets Jul 29 2019 12:21:46 16:03:14.425 -> 16:03:14.425 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 16:03:14.425 -> configsip: 271414342, SPIWP:0xee 16:03:14.425 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 16:03:14.464 -> mode:DIO, clock div:1 16:03:14.464 -> load:0x3fff0030,len:1184 16:03:14.464 -> load:0x40078000,len:13160 16:03:14.464 -> load:0x40080400,len:3036 16:03:14.464 -> entry 0x400805e4 16:03:14.932 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 16:03:14.932 -> ------------------ Version 01.0 -------------------- 16:03:15.197 -> Configuring the default Generic Access Service

.....

16:07:32.643 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 16:07:32.643 -> ------------------ Version 01.0 -------------------- 16:07:32.910 -> Configuring the default Generic Access Service 16:07:32.910 -> Successfully Set Generic Access Appearance Chr value to: [1152] Generic Cycling 16:07:32.910 -> Successfully Set Generic Access Device Name Chr value to: [Sim ESP32] 16:07:32.944 -> Configuring the Server Nordic Uart Service 16:07:32.944 -> Configuring the Server Device Information Service 16:07:32.944 -> Configuring the Server Cycle Power Service 16:07:32.944 -> Configuring the Server Cadence and Speed Service 16:07:32.944 -> Configuring the Server Fitness Machine Service 16:07:32.944 -> Configuring the Server Heart Rate Service 16:07:32.944 -> Setting up the Server advertising payload(s) 16:07:32.944 -> Setting Appearance in Advertised data to [1152] 16:07:32.944 -> Server is advertising: CPS, CSC and FTMS 16:07:32.984 -> Client Starts Scanning for Server Device with CPS, CSC and FTMS! 16:07:34.699 -> Found advertising Peripheral with FTMS enabled! See data: 16:07:34.699 -> Name: Zwift Hub, Address: f8:9c:fc:53:5e:49, appearance: 1152, manufacturer data: 4a09065e49, serviceUUID: 0x1816 16:07:34.742 -> Service Data: 16:07:34.742 -> UUID: 0x1826, Data:  16:07:34.778 -> Client Connection Parameters -> Interval: [40] Latency: [0] Supervision Timeout: [256] 16:07:34.819 -> ESP32 Client connected to Server device with Name: [Zwift Hub] MAC Address: [F8:9C:FC:53:5E:49] Handle: [0] MTU: [244] 16:07:34.819 -> Now checking all Client Services and Characteristics! 16:07:34.819 -> If Mandatory Services Fail --> the Client will disconnect! 16:07:35.179 -> Client Generic Access: Found! 16:07:35.738 -> -> Client Reads Device Name: [Zwift Hub] 16:07:36.607 -> -> Client Reads Appearance: [1152] 16:07:36.794 -> Client Device Information Service: Found! 16:07:37.248 -> -> Client Reads Manufacturer Name: [Zwift] 16:07:37.760 -> -> Client Reads Model Number: [06] 16:07:38.148 -> -> Client Reads Serial Number: [06-F89CFC535E49] 16:07:38.459 -> Client_CyclingPower_Service: Found! 16:07:38.771 -> Client_CP_Measurement_Chr: Found! 16:07:39.550 -> Client_CP_Feature_Chr: Found! 16:07:39.675 -> -> Client Reads Raw CP Feature bytes: [4] [ 0C 00 00 00 ] 16:07:39.675 -> Wheel revolution data supported 16:07:39.721 -> Crank revolution data supported 16:07:39.939 -> Client_CP_Location_Chr: Found! 16:07:40.019 -> -> Client Reads CP Location Sensor: Loc#: 12 Rear wheel 16:07:40.436 -> Client_CyclingSpeedCadence_Service: Found! 16:07:40.702 -> Client_CSC_Measurement_Chr: Found! 16:07:41.358 -> Client_CSC_Feature_Chr: Found! 16:07:41.451 -> -> Client Reads Raw CSC Feature bytes: [2] [ 03 00 ] 16:07:41.451 -> Wheel rev supported 16:07:41.451 -> Crank rev supported 16:07:41.686 -> Client_CSC_Location_Chr: Found! 16:07:41.857 -> -> Client Reads CSC Location Sensor: Loc#: 12 Rear wheel 16:07:42.137 -> Client_FitnessMachine_Service: Found! 16:07:42.402 -> Client_FTM_Feature_Chr: Found! 16:07:42.480 -> -> Client Reads Raw FTM Feature bytes: [8] [ 87 44 00 00 0C E0 00 00 ] 16:07:42.480 -> - Fitness Machine Features: 16:07:42.480 -> Average Speed Supported 16:07:42.480 -> Cadence Supported 16:07:42.526 -> Total Distance Supported 16:07:42.526 -> Resistance Level Supported 16:07:42.526 -> Heart Rate Measurement Supported 16:07:42.526 -> Power Measurement Supported 16:07:42.526 -> - Target Setting Features: 16:07:42.526 -> Resistance Target Setting Supported 16:07:42.526 -> Power Target Setting Supported 16:07:42.526 -> Indoor Bike Simulation Parameters Supported 16:07:42.526 -> Wheel Circumference Configuration Supported 16:07:42.526 -> Spin Down Control Supported 16:07:42.903 -> Client_FTM_IndoorBikeData_Chr: Found! 16:07:43.575 -> Server Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 16:07:43.575 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 16:07:43.575 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 16:07:43.617 -> MTU updated: 255 for connection ID: 1 16:07:43.990 -> Client_FTM_TrainingStatus_Chr: Not Found! 16:07:44.364 -> Client_FTM_SupportedResistanceLevelRange_Chr: Found! 16:07:44.520 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 16:07:44.863 -> Client_FTM_SupportedPowerRange_Chr: Found! 16:07:44.957 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 16:07:45.409 -> Client_FTM_ControlPoint_Chr: Found! 16:07:46.309 -> Client_FTM_Status_Chr: Found! 16:07:47.510 -> Client_HeartRate_Service: Found! 16:07:47.806 -> Client_HR_Measurement_Chr: Found! 16:07:48.226 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a63] 16:07:49.007 -> Client_HR_Location_Chr: Found! 16:07:49.211 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest 16:07:49.537 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a5b] 16:07:50.408 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:07:50.502 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ad2] 16:07:51.185 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 16:07:51.405 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 16:07:51.718 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 16:07:52.542 -> Request Control of Machine! 16:07:52.775 -> Reset Machine! 16:07:52.901 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37] 16:07:52.948 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 01 ] 16:07:53.040 -> Request Control of Machine! 16:07:53.396 -> Start or Resume Machine! 16:07:53.568 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [1] [ 04 ] 16:07:54.468 -> Set Indoor Bike Simulation Parameters! 16:07:54.468 -> Wind speed (1000): 0.00 | Grade (100): -0.58 | Crr (10000): 0.00 | Cw (100): 0.51 16:07:54.718 -> -> Client Rec'd Raw FTM Machine Status Data: [1] [7] [ 12 00 00 C6 FF 28 33 ]

Berg0162 commented 1 year ago

Dear Joel, Again, I am not able to reproduce this fatal error but I have a suggestion, locate this task-function in the MITM/Simcline code :

void TaskWriteWithResponse(void *parameter) {
  // Just pass on and process later! 
  if( !pRemote_FTM_ControlPoint_Chr->writeValue(ftmcpData, true) ) { // true -> WithResponse (fatal if trainer is not responding: Guru paniced!!)
      pClient_FTMS->disconnect();
      DEBUG_PRINTLN(">>> Error: NOT responding to FTM Control Point -> Write Value!");
  }
  vTaskDelete(TaskWriteWithResponseHandle);
};

After you have changed true in false like below:

->writeValue(ftmcpData, true)) {

in

->writeValue(ftmcpData, false)) }

Compile and upload the code again and run....

Berg0162 commented 1 year ago

Undo!

Set Arduino IDE debug level to "debug"

And Run again!

Op vr 7 apr. 2023 15:56 schreef Joel @.***>:

Hello Jorgen,

After modifying the code

->writeValue(ftmcpData, false)) }

The system does not reboot anymore but the same thing in the code Simcline_v011 its does not reboot anymore but the system does not go up or down anymore!

15:42:43.082 -> Client_FTM_TrainingStatus_Chr: Not Found! 15:42:43.440 -> Client_FTM_SupportedResistanceLevelRange_Chr: Found! 15:42:43.612 -> -> Client Reads Raw FTM Supported Resistance Level Range bytes: [6] [ 00 00 64 00 01 00 ] 15:42:43.986 -> Client_FTM_SupportedPowerRange_Chr: Found! 15:42:44.159 -> -> Client Reads Raw FTM Supported Power Range bytes: [6] [ 00 00 E8 03 01 00 ] 15:42:44.497 -> Client_FTM_ControlPoint_Chr: Found! 15:42:45.167 -> Client_FTM_Status_Chr: Found! 15:42:46.175 -> Client_HeartRate_Service: Found! 15:42:46.547 -> Client_HR_Measurement_Chr: Found! 15:42:47.604 -> Client_HR_Location_Chr: Found! 15:42:47.790 -> -> Client Reads HR Location Sensor: Loc#: 1 Chest 15:43:54.121 -> erver Connection Parameters -> Interval: [48] Latency: [0] Supervision Timeout: [960] 15:43:54.121 -> ESP32 Server connected to Client device with MAC Address: [58:11:22:53:52:18] Conn Handle: [1] 15:43:54.121 -> Central (MyLaptop/Zwift) has to set CP/CSC/FTMS CCCD Notify/Indicate (enable) and start.... 15:43:54.653 -> Central (MyLaptop/Zwift) updated MTU to: [255] for connection ID: 1 15:43:55.389 -> All Client (Trainer) Characteristics are Notify/Indicate Enabled! 15:43:59.754 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a63] 15:44:00.895 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a5b] 15:44:01.975 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ad2] 15:44:02.540 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 15:44:03.073 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 15:44:03.938 -> Central Updated CCCD --> Notify Enabled for Char: [0x2a37] 15:45:35.241 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:45:35.241 -> Request Control of Machine! 15:45:40.309 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:45:40.309 -> Request Control of Machine! 15:45:45.417 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:45:45.417 -> Request Control of Machine! 15:45:50.457 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:45:50.457 -> Request Control of Machine! 15:45:55.596 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:45:55.596 -> Request Control of Machine! 15:46:00.645 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:46:00.646 -> Request Control of Machine! 15:46:05.678 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:46:05.678 -> Request Control of Machine! 15:46:10.727 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:46:10.727 -> Request Control of Machine! 15:46:15.884 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:46:15.884 -> Request Control of Machine! 15:46:20.878 -> --> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 15:46:20.878 -> Request Control of Machine!

— Reply to this email directly, view it on GitHub https://github.com/Berg0162/simcline/issues/7#issuecomment-1500312592, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANS5LSXHNS4A6QB4L4KGRWLXAAMKTANCNFSM6AAAAAASZDERFE . You are receiving this because you authored the thread.Message ID: @.***>

Berg0162 commented 1 year ago

Other suggestions: Focus on esp32_FTMS_Zwift_Bridge_v010 Experiment with the load balance (Tools ) "Events run on Core #" and "Arduino runs on Core #" and see how it influences the result... Have a nice weekend!

le-joebar commented 1 year ago

Hello Jorgen,

Should I do like this?

change as follows:

//#define DEBUG_FTM_CONTROLPOINT_RESPONSE // If defined allows for parsing the Data //#define DEBUG_FTM_CONTROLPOINT_OPCODE_DATA // If defined allows for parsing and decoding Data

Core Debug Level: "Error"

Baud Rate 115200

and in addition: ->writeValue(ftmcpData, false)) }

Set Arduino IDE debug level to "debug"

and test?

Berg0162 commented 1 year ago

Dear Joel, set the ->writeValue(ftmcpData, false)) } to its original value: true (Write with response) Other settings are ok! Do not hesitate to experiment with the load balance!

le-joebar commented 1 year ago

Here is :

so esp32_FTMS_Zwift_Bridge_V010 modify as follows:

//#define DEBUG_FTM_CONTROLPOINT_RESPONSE // If defined, allows to analyze the data //#define DEBUG_FTM_CONTROLPOINT_OPCODE_DATA // If defined, allows to analyze and decode the data

Baud rate 115200

Main debug level: "Debug"

16:05:52.931 -> D NimBLEClient: Got Client event 16:05:52.931 -> D NimBLEClient: Notify Recieved for handle: 43 16:05:52.931 -> D NimBLEClient: checking service 0x180a for handle: 43 16:05:52.931 -> D NimBLEClient: checking service 0x1818 for handle: 43 16:05:52.931 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:52.964 -> Descriptor: uuid: 0x2902, handle: 44 16:05:52.964 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:52.964 -> Descriptor: uuid: 0x2902, handle: 44 16:05:52.964 -> D NimBLECharacteristic: >> setValue: length=4, data=00000000, characteristic UUID=0x2a63 16:05:52.964 -> D NimBLECharacteristic: << setValue 16:05:52.964 -> D NimBLECharacteristic: >> notify: length: 4 16:05:53.009 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:53.009 -> D NimBLEServer: >> handleGapEvent: 16:05:53.009 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:53.009 -> D NimBLECharacteristic: << notify 16:05:53.900 -> D NimBLEClient: Got Client event 16:05:53.900 -> D NimBLEClient: Notify Recieved for handle: 16 16:05:53.933 -> D NimBLEClient: checking service 0x180a for handle: 16 16:05:53.933 -> D NimBLEClient: checking service 0x1818 for handle: 16 16:05:53.933 -> D NimBLEClient: checking service 0x1816 for handle: 16 16:05:53.933 -> D NimBLEClient: checking service 0x1826 for handle: 16 16:05:53.933 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:53.967 -> Descriptor: uuid: 0x2902, handle: 17 16:05:53.967 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:53.967 -> Descriptor: uuid: 0x2902, handle: 17 16:05:53.967 -> D NimBLECharacteristic: >> setValue: length=11, data=6402000000001400000000, characteristic UUID=0x2ad2 16:05:53.967 -> D NimBLECharacteristic: << setValue 16:05:54.000 -> D NimBLECharacteristic: >> notify: length: 11 16:05:54.000 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:54.000 -> D NimBLEServer: >> handleGapEvent: 16:05:54.000 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:54.000 -> D NimBLECharacteristic: << notify 16:05:54.000 -> D NimBLEClient: Got Client event 16:05:54.000 -> D NimBLEClient: Notify Recieved for handle: 43 16:05:54.000 -> D NimBLEClient: checking service 0x180a for handle: 43 16:05:54.000 -> D NimBLEClient: checking service 0x1818 for handle: 43 16:05:54.033 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:54.033 -> Descriptor: uuid: 0x2902, handle: 44 16:05:54.033 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:54.033 -> Descriptor: uuid: 0x2902, handle: 44 16:05:54.033 -> D NimBLECharacteristic: >> setValue: length=4, data=00000000, characteristic UUID=0x2a63 16:05:54.071 -> D NimBLECharacteristic: << setValue 16:05:54.071 -> D NimBLECharacteristic: >> notify: length: 4 16:05:54.071 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:54.071 -> D NimBLEServer: >> handleGapEvent: 16:05:54.071 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:54.071 -> D NimBLECharacteristic: << notify 16:05:54.888 -> D NimBLEClient: Got Client event 16:05:54.888 -> D NimBLEClient: Notify Recieved for handle: 16 16:05:54.888 -> D NimBLEClient: checking service 0x180a for handle: 16 16:05:54.888 -> D NimBLEClient: checking service 0x1818 for handle: 16 16:05:54.888 -> D NimBLEClient: checking service 0x1816 for handle: 16 16:05:54.888 -> D NimBLEClient: checking service 0x1826 for handle: 16 16:05:54.888 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:54.921 -> Descriptor: uuid: 0x2902, handle: 17 16:05:54.921 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:54.921 -> Descriptor: uuid: 0x2902, handle: 17 16:05:54.921 -> D NimBLECharacteristic: >> setValue: length=11, data=6402000000001400000000, characteristic UUID=0x2ad2 16:05:54.954 -> D NimBLECharacteristic: << setValue 16:05:54.954 -> D NimBLECharacteristic: >> notify: length: 11 16:05:54.954 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:54.954 -> D NimBLEServer: >> handleGapEvent: 16:05:54.954 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:54.954 -> D NimBLECharacteristic: << notify 16:05:54.954 -> D NimBLEClient: Got Client event 16:05:54.954 -> D NimBLEClient: Notify Recieved for handle: 43 16:05:54.954 -> D NimBLEClient: checking service 0x180a for handle: 43 16:05:54.988 -> D NimBLEClient: checking service 0x1818 for handle: 43 16:05:54.988 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:54.988 -> Descriptor: uuid: 0x2902, handle: 44 16:05:54.988 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:55.023 -> Descriptor: uuid: 0x2902, handle: 44 16:05:55.023 -> D NimBLECharacteristic: >> setValue: length=4, data=00000000, characteristic UUID=0x2a63 16:05:55.023 -> D NimBLECharacteristic: << setValue 16:05:55.023 -> D NimBLECharacteristic: >> notify: length: 4 16:05:55.023 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:55.023 -> D NimBLEServer: >> handleGapEvent: 16:05:55.023 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:55.023 -> D NimBLECharacteristic: << notify 16:05:55.842 -> D NimBLEClient: Got Client event 16:05:55.842 -> D NimBLEClient: Notify Recieved for handle: 16 16:05:55.842 -> D NimBLEClient: checking service 0x180a for handle: 16 16:05:55.842 -> D NimBLEClient: checking service 0x1818 for handle: 16 16:05:55.842 -> D NimBLEClient: checking service 0x1816 for handle: 16 16:05:55.842 -> D NimBLEClient: checking service 0x1826 for handle: 16 16:05:55.876 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:55.876 -> Descriptor: uuid: 0x2902, handle: 17 16:05:55.876 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:05:55.876 -> Descriptor: uuid: 0x2902, handle: 17 16:05:55.876 -> D NimBLECharacteristic: >> setValue: length=11, data=6402000000001400000000, characteristic UUID=0x2ad2 16:05:55.909 -> D NimBLECharacteristic: << setValue 16:05:55.909 -> D NimBLECharacteristic: >> notify: length: 11 16:05:55.909 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:55.909 -> D NimBLEServer: >> handleGapEvent: 16:05:55.909 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:55.909 -> D NimBLECharacteristic: << notify 16:05:55.909 -> D NimBLEClient: Got Client event 16:05:55.942 -> D NimBLEClient: Notify Recieved for handle: 43 16:05:55.942 -> D NimBLEClient: checking service 0x180a for handle: 43 16:05:55.942 -> D NimBLEClient: checking service 0x1818 for handle: 43 16:05:55.942 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:55.942 -> Descriptor: uuid: 0x2902, handle: 44 16:05:55.942 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:05:55.975 -> Descriptor: uuid: 0x2902, handle: 44 16:05:55.975 -> D NimBLECharacteristic: >> setValue: length=4, data=00000000, characteristic UUID=0x2a63 16:05:55.975 -> D NimBLECharacteristic: << setValue 16:05:55.975 -> D NimBLECharacteristic: >> notify: length: 4 16:05:55.975 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:55.975 -> D NimBLEServer: >> handleGapEvent: 16:05:55.975 -> D NimBLECharacteristicCallbacks: onStatus: default 16:05:56.010 -> D NimBLECharacteristic: << notify 16:05:56.167 -> D NimBLECharacteristic: Characteristic 0x2ad9 Write event 16:05:56.167 -> D NimBLECharacteristic: >> setValue: length=1, data=00, characteristic UUID=0x2ad9 16:05:56.167 -> D NimBLECharacteristic: << setValue 16:05:56.167 -> ReqD NimBLERemoteCharacteristic: >> writeValue(), length: 1 16:05:56.167 -> uest Control of Machine! 16:05:56.167 -> D NimBLECharacteristicCallbacks: onWrite: default 16:05:56.325 -> I NimBLERemoteCharacteristic: Write complete; status=0 conn_handle=0 16:05:56.325 -> D NimBLERemoteCharacteristic: << writeValue, rc: 0 16:05:56.325 -> D NimBLEClient: Got Client event 16:05:56.325 -> D NimBLEClient: Notify Recieved for handle: 28 16:05:56.325 -> D NimBLEClient: checking service 0x180a for handle: 28 16:05:56.325 -> D NimBLEClient: checking service 0x1818 for handle: 28 16:05:56.325 -> D NimBLEClient: checking service 0x1816 for handle: 28 16:05:56.357 -> D NimBLEClient: checking service 0x1826 for handle: 28 16:05:56.357 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad9, handle: 28 0x001c, props: 0x28 16:05:56.357 -> Descriptor: uuid: 0x2902, handle: 29 16:05:56.357 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad9, handle: 28 0x001c, props: 0x28 16:05:56.389 -> Descriptor: uuid: 0x2902, handle: 29 16:05:56.389 -> D NimBLECharacteristic: >> setValue: length=3, data=800001, characteristic UUID=0x2ad9 16:05:56.389 -> D NimBLECharacteristic: << setValue 16:05:56.389 -> D NimBLECharacteristic: >> notify: length: 3 16:05:56.389 -> D NimBLECharacteristicCallbacks: onNotify: default 16:05:56.389 -> Guru Meditation Error: Core 0 panic'ed (Unhandled debug exception). 16:05:56.422 -> Debug exception reason: Stack canary watchpoint triggered (CP Indicate) 16:05:56.422 -> Core 0 register dump: 16:05:56.422 -> PC : 0x40096c93 PS : 0x00060f36 A0 : 0x80094a2d A1 : 0x3ffcfe10
16:05:56.422 -> A2 : 0x3ffce144 A3 : 0xb33fffff A4 : 0x0000abab A5 : 0x00060f23
16:05:56.422 -> A6 : 0x00060f20 A7 : 0x0000cdcd A8 : 0xb33fffff A9 : 0xffffffff
16:05:56.456 -> A10 : 0x00000003 A11 : 0x00060f23 A12 : 0x00060f20 A13 : 0x00000024
16:05:56.456 -> A14 : 0x007ce144 A15 : 0x003fffff SAR : 0x00000008 EXCCAUSE: 0x00000001
16:05:56.456 -> EXCVADDR: 0x00000000 LBEG : 0x40091b11 LEND : 0x40091b21 LCOUNT : 0xfffffffc
16:05:56.456 -> 16:05:56.456 -> 16:05:56.456 -> Backtrace:0x40096c90:0x3ffcfe100x40094a2a:0x3ffcfe50 0x40094af4:0x3ffcfe90 0x40085fbd:0x3ffcfeb0 0x400860c9:0x3ffcfee0 0x400f8636:0x3ffcff00 0x400f78db:0x3ffcff20 0x400f7549:0x3ffcff40 0x40091856:0x3ffcff60 0x40090b0d:0x3ffcff80 0x40090b9c:0x3ffcffa0 0x400910e7:0x3ffcffd0 0x4012d60a:0x3ffd0000 0x40125ec6:0x3ffd0020 0x4011b176:0x3ffd0330 0x400da801:0x3ffd0380 0x400df27d:0x3ffd03f0 0x400df2c7:0x3ffd0410 0x400e0917:0x3ffd0430 0x400e211b:0x3ffd0490 0x400d6481:0x3ffd04b0 0x400d64dd:0x3ffd0540 0x400d64ed:0x3ffd0560 0x400d2361:0x3ffd0580 16:05:56.521 -> 16:05:56.521 -> 16:05:56.521 -> 16:05:56.521 -> 16:05:56.521 -> ELF file SHA256: 0000000000000000 16:05:56.521 -> 16:05:56.521 -> Rebooting... 16:05:56.521 -> ets Jul 29 2019 12:21:46 16:05:56.521 ->

le-joebar commented 1 year ago

I don't know what to do anymore because it's really a funny problem !!

What if I thought of delivering my trainer to you by post?

Belgium to Netherlands 11 euro!

What do you think about it ?

Berg0162 commented 1 year ago

Dear Joel, I have been asking around if someone knows someone that has a Zwift Hub... So I have been thinking in the same direction... I find it so annoying for you (and me) that we are confronted with these "funny" (really?) problems... I would say very confronting and bad problems.... Ik woon dichtbij Utrecht (centraal NL), bij welke grote stad woon jij?

Debug exception reason: Stack canary watchpoint triggered (CP Indicate) See

So we have a stack problem, when TaskWriteWithResponse is called from server_FTM_ControlPoint_Chr_callback. I was expecting a timeout problem not a stack problem!
I suggest that you make a simple change in the code again, locate the following code snippet:

 // write with response !!! writeValue(string, bool response = false);
  if(Trainer.IsConnected) { 
    xTaskCreate(&TaskWriteWithResponse, "Write w Response", 2048, (void *)NULL, 1, &TaskWriteWithResponseHandle); 
  } 
  memset(server_FTM_Control_Point_Data.bytes, 0, sizeof(server_FTM_Control_Point_Data.bytes));

Change the "stack depth" value from 2048 in 4096 ; we just double it and see if that is helping us out.....

Lets add some extra debug messages (uncomment these defines again, to activate):

#define DEBUG_FTM_CONTROLPOINT_RESPONSE // If defined, allows to analyze the data
#define DEBUG_FTM_CONTROLPOINT_OPCODE_DATA // If defined, allows to analyze and decode the data

Run the program and fingers crossed!

le-joebar commented 1 year ago

Hallo Jorgen, Ik kom uit Brussel maar woon nu in Charleroi. Het is 60 km verder naar het zuiden. Met de auto van Charleroi naar Utrecht is het 2 u 26 min (233,7 km) via E19 en A27.

I will try your suggestion tomorrow!

Vriendelijk

Joel

le-joebar commented 1 year ago

Hello Jorgen,

Here are the results with esp32_FTMS_Zwift_Bridge_v010

change as follows:

define DEBUG_FTM_CONTROLPOINT_RESPONSE // If defined, allows to analyze the data

define DEBUG_FTM_CONTROLPOINT_OPCODE_DATA // If defined, allows to analyze and decode the data

++++

if(Trainer.IsConnected) { xTaskCreate(&TaskWriteWithResponse, "Write w Response", 4096, (void *)NULL, 1, &TaskWriteWithResponseHandle); } memset(server_FTM_Control_Point_Data.bytes, 0, sizeof(server_FTM_Control_Point_Data.bytes));

+++++

->writeValue(ftmcpData, false)) } ???????????????????????????????

Main debug level: "Debug"

Baud rate 115200

:

6:29:55.383 -> D NimBLECharacteristicCallbacks: onStatus: default 16:29:55.419 -> D NimBLECharacteristic: << notify 16:29:55.419 -> D NimBLEServer: >> handleGapEvent: 16:29:55.419 -> I NimBLEServer: subscribe event; attr_handle=62, subscribed: false 16:29:55.419 -> I NimBLECharacteristic: New subscribe value for conn: 1 val: 2 16:29:55.419 -> Central Updated CCCD --> Indicate Enabled for Char: [0x2ad9] 16:29:55.594 -> D NimBLEClient: Got Client event 16:29:55.594 -> D NimBLEClient: Peer requesting to update connection parameters 16:29:55.594 -> D NimBLEClient: MinInterval: 72, MaxInterval: 120, Latency: 0, Timeout: 400 16:29:55.594 -> D NimBLEClientCallbacks: onConnParamsUpdateRequest: default 16:29:55.637 -> D NimBLEClient: Accepted peer params 16:29:55.946 -> D NimBLEServer: >> handleGapEvent: 16:29:55.946 -> I NimBLEServer: subscribe event; attr_handle=49, subscribed: true 16:29:55.946 -> I NimBLECharacteristic: New subscribe value for conn: 1 val: 1 16:29:55.946 -> Central Updated CCCD --> Notify Enabled for Char: [0x2ada] 16:29:56.024 -> D NimBLEClient: Got Client event 16:29:56.024 -> I NimBLEClient: Connection parameters updated. 16:29:56.070 -> D NimBLECharacteristic: Characteristic 0x2ada Read event 16:29:56.070 -> D NimBLECharacteristicCallbacks: onRead: default 16:29:56.070 -> D NimBLECharacteristicCallbacks: onRead: default 16:29:56.141 -> D NimBLEClient: Got Client event 16:29:56.141 -> D NimBLEClient: Notify Recieved for handle: 16 16:29:56.141 -> D NimBLEClient: checking service 0x180a for handle: 16 16:29:56.141 -> D NimBLEClient: checking service 0x1818 for handle: 16 16:29:56.141 -> D NimBLEClient: checking service 0x1816 for handle: 16 16:29:56.141 -> D NimBLEClient: checking service 0x1826 for handle: 16 16:29:56.141 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:29:56.174 -> Descriptor: uuid: 0x2902, handle: 17 16:29:56.174 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad2, handle: 16 0x0010, props: 0x10 16:29:56.174 -> Descriptor: uuid: 0x2902, handle: 17 16:29:56.174 -> D NimBLECharacteristic: >> setValue: length=11, data=6402000000001400000000, characteristic UUID=0x2ad2 16:29:56.174 -> D NimBLECharacteristic: << setValue 16:29:56.209 -> D NimBLECharacteristic: >> notify: length: 11 16:29:56.209 -> D NimBLECharacteristicCallbacks: onNotify: default 16:29:56.209 -> D NimBLEServer: >> handleGapEvent: 16:29:56.209 -> D NimBLECharacteristicCallbacks: onStatus: default 16:29:56.209 -> D NimBLECharacteristic: << notify 16:29:56.369 -> D NimBLEClient: Got Client event 16:29:56.369 -> D NimBLEClient: Notify Recieved for handle: 43 16:29:56.369 -> D NimBLEClient: checking service 0x180a for handle: 43 16:29:56.369 -> D NimBLEClient: checking service 0x1818 for handle: 43 16:29:56.369 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:29:56.403 -> Descriptor: uuid: 0x2902, handle: 44 16:29:56.403 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2a63, handle: 43 0x002b, props: 0x10 16:29:56.403 -> Descriptor: uuid: 0x2902, handle: 44 16:29:56.403 -> D NimBLECharacteristic: >> setValue: length=4, data=00000000, characteristic UUID=0x2a63 16:29:56.403 -> D NimBLECharacteristic: << setValue 16:29:56.436 -> D NimBLECharacteristic: >> notify: length: 4 16:29:56.436 -> D NimBLECharacteristicCallbacks: onNotify: default 16:29:56.436 -> D NimBLEServer: >> handleGapEvent: 16:29:56.436 -> D NimBLECharacteristicCallbacks: onStatus: default 16:29:56.436 -> D NimBLECharacteristic: << notify 16:29:56.436 -> D NimBLECharacteristic: Characteristic 0x2ad9 Write event 16:29:56.436 -> D NimBLECharacteristic: >> setValue: length=1, data=00, characteristic UUID=0x2ad9 16:29:56.436 -> D NimBLECharacteristic: << setValue 16:29:56.473 -> -->D NimBLERemoteCharacteristic: >> writeValue(), length: 1 16:29:56.473 -> Raw FTM Control Point Data [len: 1] [OpCode: 00] [Values: 00 ] 16:29:56.473 -> Request Control of Machine! 16:29:56.473 -> D NimBLECharacteristicCallbacks: onWrite: default 16:29:56.741 -> I NimBLERemoteCharacteristic: Write complete; status=0 conn_handle=0 16:29:56.741 -> D NimBLERemoteCharacteristic: << writeValue, rc: 0 16:29:56.741 -> D NimBLEClient: Got Client event 16:29:56.741 -> D NimBLEClient: Notify Recieved for handle: 28 16:29:56.741 -> D NimBLEClient: checking service 0x180a for handle: 28 16:29:56.741 -> D NimBLEClient: checking service 0x1818 for handle: 28 16:29:56.741 -> D NimBLEClient: checking service 0x1816 for handle: 28 16:29:56.741 -> D NimBLEClient: checking service 0x1826 for handle: 28 16:29:56.774 -> D NimBLEClient: Got Notification for characteristic Characteristic: uuid: 0x2ad9, handle: 28 0x001c, props: 0x28 16:29:56.774 -> Descriptor: uuid: 0x2902, handle: 29 16:29:56.774 -> D NimBLEClient: Invoking callback for notification on characteristic Characteristic: uuid: 0x2ad9, handle: 28 0x001c, props: 0x28 16:29:56.774 -> Descriptor: uuid: 0x2902, handle: 29 16:29:56.774 -> D NimBLECharacteristic: >> setValue: length=3, data=800001, characteristic UUID=0x2ad9 16:29:56.808 -> D NimBLECharacteristic: << setValue 16:29:56.808 -> D NimBLECharacteristic: >> notify: length: 3 16:29:56.808 -> D NimBLECharacteristicCallbacks: onNotify: default 16:29:56.808 -> Guru Meditation Error: Core 0 panic'ed (Unhandled debug exception). 16:29:56.808 -> Debug exception reason: Stack canary watchpoint triggered (CP Indicate) 16:29:56.808 -> Core 0 register dump: 16:29:56.808 -> PC : 0x40096c93 PS : 0x00060d36 A0 : 0x80094a2d A1 : 0x3ffcfdf0
16:29:56.841 -> A2 : 0x3ffce144 A3 : 0xb33fffff A4 : 0x0000abab A5 : 0x00060d23
16:29:56.841 -> A6 : 0x00060d20 A7 : 0x0000cdcd A8 : 0xb33fffff A9 : 0xffffffff
16:29:56.841 -> A10 : 0x00000003 A11 : 0x00060d23 A12 : 0x00060d20 A13 : 0x00000024
16:29:56.841 -> A14 : 0x007ce144 A15 : 0x003fffff SAR : 0x00000008 EXCCAUSE: 0x00000001
16:29:56.874 -> EXCVADDR: 0x00000000 LBEG : 0x40091b11 LEND : 0x40091b21 LCOUNT : 0xfffffffc
16:29:56.874 -> 16:29:56.874 -> 16:29:56.874 -> Backtrace:0x40096c90:0x3ffcfdf00x40094a2a:0x3ffcfe30 0x40094af4:0x3ffcfe70 0x40085fbd:0x3ffcfe90 0x400860c9:0x3ffcfec0 0x400f872a:0x3ffcfee0 0x400f79cf:0x3ffcff00 0x400f763d:0x3ffcff20 0x40091856:0x3ffcff40 0x40090b0d:0x3ffcff60 0x40090b9c:0x3ffcff80 0x400910e7:0x3ffcffb0 0x4012d6fe:0x3ffcffe0 0x40125fba:0x3ffd0000 0x4011b26a:0x3ffd0310 0x400da8f5:0x3ffd0360 0x400df371:0x3ffd03d0 0x400df3bb:0x3ffd03f0 0x400e0a0b:0x3ffd0410 0x400e220f:0x3ffd0470 0x400d6575:0x3ffd0490 0x400d65d1:0x3ffd0520 0x400d65e1:0x3ffd0540 0x400d2371:0x3ffd0560 16:29:56.907 -> 16:29:56.907 -> 16:29:56.907 -> 16:29:56.907 -> 16:29:56.907 -> ELF file SHA256: 0000000000000000 16:29:56.907 -> 16:29:56.907 -> Rebooting... 16:29:56.907 -> ets Jul 29 2019 12:21:46 16:29:56.952 -> 16:29:56.952 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 16:29:56.952 -> configsip: 271414342, SPIWP:0xee 16:29:56.952 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 16:29:56.952 -> mode:DIO, clock div:1 16:29:56.952 -> load:0x3fff0030,len:1184 16:29:56.952 -> load:0x40078000,len:13160 16:29:56.952 -> load:0x40080400,len:3036 16:29:56.952 -> entry 0x400805e4 16:29:57.169 -> [ 4][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz 16:29:57.435 -> [ 229][I][esp32-hal-psram.c:96] psramInit(): PSRAM enabled 16:29:57.435 -> ESP32 NimBLE MITM supporting: CPS, CSC, HBM and FTMS 16:29:57.435 -> ------------------ Version 01.0 -------------------- 16:29:57.689 -> I NimBLEDevice: BLE Host Task Started

le-joebar commented 1 year ago

It's really and only when you're on this page!! What info does Zwift send to the trainer that it doesn't when it's on the previous page?

image

And after he rebooted the trainer properly resumes the connection with Zwift but as he is on this page he reboots !!

Once you have chosen your course then it's good time that it does not reboot! sometimes 20 minutes sometimes more sometimes less!

Berg0162 commented 1 year ago

Stuur even een antwoord via e-mail naar mijn email dan gaan we zo verder...