Jörgen van den Berg

Two successive calls to write-with-response cause fatal error when NimBLE is handling the write acknowledgement(s)

3

When the client calls pRemoteCharacteristic->writeValue(ftmcpData, true), **write-with-response**, it takes some time (about 300-400ms?) before the server has acknowledged the write action.... However, if within that time period a second call...

Is the Zwift Steerer code still working?

7

I have been testing the Zwift-Steerer code with little success. The code connects (successful) via the Power Pairing screen but the steering activation is hanging with "Activating" forever... No transfer...

Please post here when you come across any erratic behavior of the Simcline FTMS when connected with an Elite Direto Trainer!

Arduino-ESP32 version 3.0.0 does not compile with LilyGo T-display S3 and TFT_eSPI

6

Board: LilyGo T-display S3 --> Board manager setting: "ESP32S3 Dev Module" with the right Tools settings Arduino IDE version: 2.3.2; CLI Version: 0.35.3 TFT_eSPI version: 2.5.43; previous version: 2.5.34 Arduino-ESP32...

The new NimBLE version 2 is disruptive for all existing code. It has a very large number of code breaking changes! Any existing code that is developed with version NimBLE...

NimBLEClientCallbacks::onConnectFail() is not working with failing regular client connection

1

I have been testing a connection problem and was happy to insert the onConnectFail() to see when and why the connection failed. Everywhere in the NimBLE-Arduino code and documentation **onConnectFail()**...