Who owns a characteristic's value ?

RE: Who owns a characteristic's value ?

Thomas — Wed, 23 Mar 2016 09:07:27 GMT

I thought that vloc =... USER meant that I could give a pointer of my state to the characteristic, and the characteristic value would always point to my state. is it wrong ?

RE: Who owns a characteristic's value ?

Thomas — Wed, 23 Mar 2016 09:06:12 GMT

your solution works when I used attr_md.vloc = BLE_GATTS_VLOC_STACK. thanks!

RE: Who owns a characteristic's value ?

Thomas — Wed, 23 Mar 2016 09:02:56 GMT

this doesn't work. I did that in the on_write() method, of my ble service, just after calling my write_handler.

RE: Who owns a characteristic's value ?

MartinBL — Wed, 23 Mar 2016 08:47:22 GMT

Maybe you can to a control check of the received value at the write event. You can read the value with e.g. p_ble_evt->evt.gatts_evt.params.write.data. If the value is '0' or '1' everything is good, but if it is something else you can do:

uint8_t your_state = 0x01;     // Your desired alternate state
ble_gatts_value_t value;       // Variable to hold desired state value with length and offset information
value.len = 1;                 // Lenght of your state characteristic
value.offset = 0;              // Offset of your state characteristic
value.p_value = &your_state;   // Alternate state
sd_ble_gatts_value_set("current connection handle", "characteristic handle", &value); // Write new state to characteristic

to overwrite the new value.