<?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>How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36849/how-to-get-thingy-data-on-nrf52840</link><description>Hi. 
 I want to get thingy&amp;#39;s sensor data on nRF52840. 
 I found that &amp;#39;ble_app_multi_link_multi_role&amp;#39; example, but there are only get button and led state. 
 By using that project, i wrote sd_ble_gattc_char_value_by_uuid_read funtion to get data. But i</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Aug 2018 13:46:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36849/how-to-get-thingy-data-on-nrf52840" /><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/144560?ContentTypeID=1</link><pubDate>Thu, 16 Aug 2018 13:46:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7afd507-8ad5-4766-b30a-1d32a91876d1</guid><dc:creator>Rasit Eskicioglu</dc:creator><description>&lt;p&gt;Hi Bjorn,&lt;/p&gt;
&lt;p&gt;I think when I tested the demo, I answered the question myself. I guess, by properly formatting the output that comes over UART, one can capture them and process them later. Nevertheless, I&amp;#39;ll open up another question to see the alternatives other than 91 kit to push the data up.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/144550?ContentTypeID=1</link><pubDate>Thu, 16 Aug 2018 13:11:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfb7d3a5-5800-446c-a9fd-821de9d33a51</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Hi Rasit,&lt;/p&gt;
&lt;p&gt;In this demo, we wanted to transfer the Thingy sensor data over BLE to a nrf52 &amp;amp; connect the nRF52 to the cloud via an nrf91 kit. The nRF52 is connected to the 91 kit via serialization. Then, the data is visualized on a website.&lt;/p&gt;
&lt;p&gt;Could you please open a new devzone question regarding your second question?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/144498?ContentTypeID=1</link><pubDate>Thu, 16 Aug 2018 10:50:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2519e2da-9b2d-4582-a27c-6cbc5e0724f6</guid><dc:creator>Rasit Eskicioglu</dc:creator><description>&lt;p&gt;What is the purpose of getting the thingy data onto a nrF52xx? I can adopt the example to retrieve the motion data, but I need to store this data so that I can process later. What am I missing?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;--Rasit&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142640?ContentTypeID=1</link><pubDate>Thu, 02 Aug 2018 13:46:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a814c98-891b-498a-910a-e3c2550419a4</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;No worries. &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt; If you liked the demo code, would you mind upvoting Carl&amp;#39;s answer? Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142496?ContentTypeID=1</link><pubDate>Thu, 02 Aug 2018 06:18:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5bbc4a77-0c00-4d93-a767-91cbcaacca83</guid><dc:creator>wanna</dc:creator><description>&lt;p&gt;Thank you!!! :^)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142495?ContentTypeID=1</link><pubDate>Thu, 02 Aug 2018 06:18:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c581870-7506-4728-941a-c931133aa9b2</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;No problem!! :)&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142494?ContentTypeID=1</link><pubDate>Thu, 02 Aug 2018 06:16:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bacfe4d-46f6-40e5-8420-cf7fe2eba891</guid><dc:creator>wanna</dc:creator><description>&lt;p&gt;Thank you!! :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142417?ContentTypeID=1</link><pubDate>Wed, 01 Aug 2018 13:16:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5e2696a-48e6-4b91-8529-7e43cfe2b83e</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;Here is the example for transferring environment sensor data from the Thingy:52 to a nRF52xx DK:&amp;nbsp;&lt;a href="https://github.com/crfosse/Thingy-52-to-nRF52xx"&gt;https://github.com/crfosse/Thingy-52-to-nRF52xx&lt;/a&gt;. The readme should explain how to use it, but if you are struggling don&amp;#39;t hesitate to ask.&lt;br /&gt;&lt;br /&gt;It&amp;#39;s still work in progress, but it is functional!&lt;/p&gt;
&lt;p&gt;- Carl Richard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to get thingy data on nRF52840?</title><link>https://devzone.nordicsemi.com/thread/142304?ContentTypeID=1</link><pubDate>Wed, 01 Aug 2018 07:12:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:84488daa-5ed5-4558-bc80-779cf05b15fb</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;div&gt;Sorry for the delayed response. We are working an example where the Thingy:52 will communicate with a nRF52 DK. I will let you know when this example is finished. Until then, you can start by&amp;nbsp;using the&amp;nbsp;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/ble_sdk_app_multilink.html?cp=4_0_0_4_1_0_2"&gt;multilink central example&lt;/a&gt;&amp;nbsp;from sdk 15. Change the&amp;nbsp;m_target_periph_name[] in main.c to be the name that you gave to your Nordic Thingy (if you have not defined a new name, it is most likely &amp;quot;Thingy&amp;quot;).&lt;/div&gt;
&lt;div&gt;Then, you can essentially just copy what the lbs button service does to connect to the environment services of the Thingy device (for example temperature) instead. I will assume below that you want to get the temperature data from the Thingy:52.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Start by taking a look at how the lbs_c_init function initializes the LED button collector. The struct&amp;nbsp;ble_lbs_c_init_t can be changed to be an event handler for the Thingy temperature service. Also take a look at the&amp;nbsp;ble_lbs_c_s struct &amp;amp; make sure to change the peer_lbs_db &amp;amp; evt_handler to conform to the new event handler for the temperature service. The&amp;nbsp;lbs_db_t struct should be changed to include the include the cccd_handle of the temperature characteristic &amp;amp; the temperature_handle I believe.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Also make sure to take a look at the lbs_c_evt_handler &amp;amp; update this function to handle a BLE_TES_C_EVT_DISCOVERY_COMPLETE instead of&amp;nbsp;BLE_LBS_C_EVT_DISCOVERY_COMPLETE. Take a look at&amp;nbsp;ble_lbs_on_db_disc_evt() for more info too.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Make sure to update the&amp;nbsp;BLE_LBS_C_EVT_BUTTON_NOTIFICATION event too to be a BLE_TES_C_EVT_TEMPERATURE_NOTIFICATION instead. Take a look at on_hvx() for more info.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;There are most likely more lines of code to change, but this is a good starting point. I would definitely make sure to take a good look at the multilink central example &amp;amp; the ble_app_blinky peripheral example (from SDK 15) &amp;amp; make sure you understand how the LED button service (LBS) is initialized, handled &amp;amp; sent over BLE on the peripheral side. Then, take a look at how the LBS is handled on the central side.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;Once you have fully understood this, you can take a look at the Thingy SDK code, see how the temperature service is initialized, handled &amp;amp; sent over BLE &amp;amp; do something similar to the LBS on the central side.&lt;/div&gt;
&lt;div&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/33673/thingy-52-receive-microphone-data-on-nrf52840"&gt;This devzone case&lt;/a&gt;&amp;nbsp;could also be a helpful starting point. It might also be useful to take a look at this custom service tutorial to see how to work with services in general, as well as these three links: &lt;a href="https://devzone.nordicsemi.com/tutorials/5"&gt;link 1&lt;/a&gt;, &lt;a href="https://devzone.nordicsemi.com/tutorials/8"&gt;link 2&lt;/a&gt;, &lt;a href="https://devzone.nordicsemi.com/tutorials/17"&gt;link 3&lt;/a&gt;.&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>