First the device will connect, that time the event CYBLE_EVT_GAP_DEVICE_CONNECTED
When the device paired successfully and authentication completed, it will trigger event CYBLE_EVT_GAP_AUTH_COMPLETE
After Bonding, no events will get triggered. But you can confirm whether bonding was successfull by checking the API result of CyBle_StoreBondingData API.
I am attaching a basic bonding example project. Please go through it for reference.
Thanks & Regards,
Thank you. So, just to be certain, after CYBLE_EVT_GAP_AUTH_COMPLETE, devices are connected until disconnect is issued. Then (provided bonded device is stored) what event would be triggered on reconnect? Specifically if the the 4.2 device was advertising directly to the central device. I know there's a scan event that triggers on the central side when direct advertising is used, which then the central can call a connection, but after connection?
1 of 1 people found this helpful
After connection always CYBLE_EVT_GAP_DEVICE_CONNECTED event will get trigger (Even it is a reconnect after disconnection).
And if the device passed authentication process successfully , the event CYBLE_EVT_GAP_AUTH_COMPLETE will get triggered (if not disconnected).