⚠️ Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
The user_svc1_adc_val_1_cfg_ind_handler() is the ADC value 1 configuration indication handler and it will be triggered when you get a SVC1_IDX_ADC_VAL_1_NTF_CFG message. This message will be handled by the user_catch_rest_hndl(). The user_svc1_adc_val_1_ntf_cfm_handler() will be executed when you get a notification confirmation massage, CUSTS1_VAL_NTF_CFM. For your information, be aware that the indication has confirmation of data receiving but notify does not. The CUSTS1_VAL_NTF_CFM is a confirmation from the stack that you pushed successfully a CUSTS1_VAL_NTF_REQ message to the BLE stack. It is not a confirmation from the central that the data have successfully been received. Whenever you send a notification you will get a CUSTS1_VAL_NTF_CFM (for the custom profile), as soon as you get this you will know that the notification just send will be delivered to the central, so you can directly place the second notification. You will have to wait for the CUSTS1_VAL_NTF_CFM to arrive before sending the next notification for the same characteristic, if not you will update the value's database with the latter value and when the kernel pushes the notification into the buffer it will push two notifications with the same value, since the values of the notifications are acquired from the database.
Hi MADHUSF,
The user_svc1_adc_val_1_cfg_ind_handler() is the ADC value 1 configuration indication handler and it will be triggered when you get a SVC1_IDX_ADC_VAL_1_NTF_CFG message. This message will be handled by the user_catch_rest_hndl(). The user_svc1_adc_val_1_ntf_cfm_handler() will be executed when you get a notification confirmation massage, CUSTS1_VAL_NTF_CFM. For your information, be aware that the indication has confirmation of data receiving but notify does not. The CUSTS1_VAL_NTF_CFM is a confirmation from the stack that you pushed successfully a CUSTS1_VAL_NTF_REQ message to the BLE stack. It is not a confirmation from the central that the data have successfully been received. Whenever you send a notification you will get a CUSTS1_VAL_NTF_CFM (for the custom profile), as soon as you get this you will know that the notification just send will be delivered to the central, so you can directly place the second notification. You will have to wait for the CUSTS1_VAL_NTF_CFM to arrive before sending the next notification for the same characteristic, if not you will update the value's database with the latter value and when the kernel pushes the notification into the buffer it will push two notifications with the same value, since the values of the notifications are acquired from the database.
Thanks, PM_Dialog