https://devzone.nordicsemi.com/f/nordic-q-a/3388/s110-v7-hvx-notification-bugI am not sure, but i think we found bug or some interesting feature in sending notification values. Here is the code i used: uint32_t ble_meas_on_ext_adc_change(ble_meas_t * p_meas, uint32_t adcread){ uint32_t err_code = NRF_SUCCESS; staticen-USTelligent Community 13Wed, 06 Aug 2014 14:53:56 GMThttps://devzone.nordicsemi.com/thread/12306?ContentTypeID=1Wed, 06 Aug 2014 14:53:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d7bcdf31-5511-4b81-b4de-8939dff48ed1Wojtek<p>Everything is clear now, thanks!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/12305?ContentTypeID=1Wed, 06 Aug 2014 14:36:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3cb8c0e9-267d-458c-a764-786675eb9986Carles<p>Hi there,</p> <p>Both notifications and indications will send the complete contents of the characteristic value (up to the MTU or Maximum Transmission Unit currently active).</p> <p>Your characteristic is probably 5 bytes long and fixed length (i.e. you did not set the ble_gatts_attr_md_t :: vlen bit when creating it) meaning that what you are actually doing is modifying <strong>only the first 2 bytes of the 5</strong> but then sending the contents of the value to the peer. Since the characteristic is fixed length, even if you write it only partially the length remains 5, and the whole 5 bytes are sent as a notification.</p> <p>Hope that helps,</p> <p>Carles</p><div style="clear:both;"></div>