Open
Description
Hello
This is not really an issue but rather a comment on a possible improvement.
In current implementation, ArduinoBLE is managing events via polling :
// poll for BLE events
BLE.poll();
This can be an issue because you can experience delays on BLE communication if the loop()
function is managing a time-consuming code before / after the BLE.poll()
call.
The only events currently handled as interrupts are for connected/disconnected: https://www.arduino.cc/en/Reference/ArduinoBLEBLEsetEventHandler.
Is it possible to manage all BLE events by interrupts, for example triggering an IT attached to a given characteristic when a central take an action on it ?
Best regards
Yannick