Missing characteristics declaration value.

RE: Missing characteristics declaration value.

Jørgen Holmefjord — Thu, 02 Mar 2017 15:11:19 GMT

When you call sd_ble_gatts_characteristic_add(), the last parameter is where the handles for this characteristics is stored. If you want to check the content of a handle, you can call sd_ble_gatts_value_get() with the handle as parameter. For instance in the ble_app_uart example, the handles of the nus service is stored in the struct ble_nus_t m_nus, and you can access the handles with m_nus.tx_handles.value_handle, m_nus.rx_handles.value_handle, etc.

RE: Missing characteristics declaration value.

Swapnil — Tue, 28 Feb 2017 17:15:30 GMT

Well they are apperently already consecutive once the services and characteristics are initialized properly and I just wanted to have some option to read-back all handle-values after the initialization is done as an error-check.

Is there a way to access that handle-holder that you mentioned?

RE: Missing characteristics declaration value.

Jørgen Holmefjord — Wed, 22 Feb 2017 11:39:26 GMT

These handle numbers are most likely used somewhere else. Why do you want these numbers to be consecutive? They are stored in the handle holder, so that you could use the variable instead of the number.