<?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>where do we receive the battery value in s130,ble_central_and_peripheral</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8005/where-do-we-receive-the-battery-value-in-s130-ble_central_and_peripheral</link><description>The codes i am using is
nRF51_SDK_8.1.0_b6ed55fnnn\examples\ble_central_and_peripheral and nRF51_SDK_8.1.0_b6ed55fnnn\examples\ble_peripheral\ble_app_hrs 
 From the peripheral, it sends heart rate value and battery value over bluetooth.We receive the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Jul 2015 10:18:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8005/where-do-we-receive-the-battery-value-in-s130-ble_central_and_peripheral" /><item><title>RE: where do we receive the battery value in s130,ble_central_and_peripheral</title><link>https://devzone.nordicsemi.com/thread/28670?ContentTypeID=1</link><pubDate>Mon, 13 Jul 2015 10:18:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38412466-c588-47e4-9087-f8b062af9174</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@deepu: You can do a scanning. And when you capture an advertising packet, you will receive a BLE_GAP_EVT_ADV_REPORT event. In that event you can find the address, advertising data. Please have a look at the ble_app_hrs_c project in ble_central folder.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: where do we receive the battery value in s130,ble_central_and_peripheral</title><link>https://devzone.nordicsemi.com/thread/28671?ContentTypeID=1</link><pubDate>Sat, 11 Jul 2015 05:49:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85d4ace4-2427-425a-9a74-6c0796581e64</guid><dc:creator>deepu</dc:creator><description>&lt;p&gt;ty hung,&lt;/p&gt;
&lt;p&gt;where do we receive the slave address and name in ble_central_and_peripheral so that,we can connect even to an unknown slave by giving the received address rather than giving the address in the beginning&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: where do we receive the battery value in s130,ble_central_and_peripheral</title><link>https://devzone.nordicsemi.com/thread/28669?ContentTypeID=1</link><pubDate>Mon, 06 Jul 2015 11:05:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b6af16e-59d0-4af5-833a-40f23a168379</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@deepu: In the ble_central_and_peripheral () we don&amp;#39;t look for the battery service and only forcus on the heart rate measurement service as you can find in discovery() function in main.c.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s only an experimental project, so it&amp;#39;s pretty modest. You would need to add the code to scan for Battery service UUID, look for the CCCD and enable it to be able to receive notification for battery.&lt;/p&gt;
&lt;p&gt;I would also suggest you to use the device_manager_central and ble_db_discovery.c library as we used in the S120 example (ble_central) to do the task.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>