<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Which is the call back for BLE Custom Characteristic Value Read</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44913/which-is-the-call-back-for-ble-custom-characteristic-value-read</link><description>Hi all, 
 At Peripheral end, I will get an callback &amp;quot;BLE_GATTS_EVT_WRITE&amp;quot; whenever I do a write on charcteristic write value from Mobile App. 
 Can you please point me to the callback need to be registered for the read of charcteristic write value from</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 18 Mar 2019 12:32:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44913/which-is-the-call-back-for-ble-custom-characteristic-value-read" /><item><title>RE: Which is the call back for BLE Custom Characteristic Value Read</title><link>https://devzone.nordicsemi.com/thread/176694?ContentTypeID=1</link><pubDate>Mon, 18 Mar 2019 12:32:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9261d26-f218-4696-a456-9241a0513abb</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can find the message sequence charts the events that will occur:&lt;br /&gt;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/s132_msc_overview.html?cp=2_3_1_1_0_1"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/s132_msc_overview.html?cp=2_3_1_1_0_1&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Typically you will not be informed of any event when a peer read a characteristic, unless you enable authorization on the characteristic, then you will get an event every time the peer try to read the characteristic:&lt;br /&gt;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/group___b_l_e___g_a_t_t_s___r_e_a_d___r_e_q___a_u_t_h___m_s_c.html"&gt;http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.0/group___b_l_e___g_a_t_t_s___r_e_a_d___r_e_q___a_u_t_h___m_s_c.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can transfer any kind of data, just cast the data to (uint8) and then&amp;nbsp;convert it back afterwards.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>