Get reception confirmation in BLE (indication)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 4:43 AM
I am using an STM32WB5MMG for a BLE application. The device acts as a server. I have configured a number of characteristics with indication permissions. How can I confirm the correct reception of the characteristics updates by the client? I mean, where can I get the indication confirmation?
Best regards and thanks.
Solved! Go to Solution.
- Labels:
-
BLE
-
STM32WB series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 11:41 PM
Hi @thealbertdev,
If what you are looking for is some kind of event telling the CPU1 that the ACK from the client has been received, you can add the ACI_GATT_SERVER_CONFIRMATION_VSECT_CODE in the switch case of the function
static SVCCTL_EvtAckStatus_t Custom_STM_Event_Handler(void *Event){} (if you are using the CubeMX BLE custom option) between the user code comments
/* USER CODE BEGIN BLECORE_EVT */
/* USER CODE END BLECORE_EVT */
Description of the event in the AN5270
Hope this works as it worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 11:41 PM
Hi @thealbertdev,
If what you are looking for is some kind of event telling the CPU1 that the ACK from the client has been received, you can add the ACI_GATT_SERVER_CONFIRMATION_VSECT_CODE in the switch case of the function
static SVCCTL_EvtAckStatus_t Custom_STM_Event_Handler(void *Event){} (if you are using the CubeMX BLE custom option) between the user code comments
/* USER CODE BEGIN BLECORE_EVT */
/* USER CODE END BLECORE_EVT */
Description of the event in the AN5270
Hope this works as it worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-26 7:02 AM
Thank you!
Doing it as you indicate works. Although now that it is working, I can see that it is much more difficult to manage the non-receipt of the confirmation than the confirmation itself :grinning_face_with_sweat:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-26 7:09 AM
well, sometimes you can't have it all. Setting some type of Timeout after the sending of data would help? there is this timer service (based on the RTC) which could help you out with this.
