<?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>Regarding BLE advertising packet&amp;#39;s transferring time on nrf52840</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/57470/regarding-ble-advertising-packet-s-transferring-time-on-nrf52840</link><description>HI I&amp;#39;m currently working on measuring distance between two points with two nrf52840 modules with the example &amp;quot;nRF52-ble-long-range-demo&amp;quot; (you can easily find it in github) 
 Both of my central and peripheral nrf52840 module have setup with Coded PHY &amp;amp;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 Feb 2020 16:45:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/57470/regarding-ble-advertising-packet-s-transferring-time-on-nrf52840" /><item><title>RE: Regarding BLE advertising packet's transferring time on nrf52840</title><link>https://devzone.nordicsemi.com/thread/234056?ContentTypeID=1</link><pubDate>Wed, 12 Feb 2020 16:45:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f49741db-1b9b-4309-ae71-44c9048fd1d9</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am not sure if I understand.&lt;/p&gt;
&lt;p&gt;You can get timestamps on logs, which means you can get a timestamp from locations in code. You cannot however get accurate timestamps from when the BLE stack (that is the SoftDevice) sends packets. You can get a timestamps from the callback function after having received an advertisement.&lt;/p&gt;
&lt;p&gt;What timings do you need to measure, and with what accuracy?&lt;/p&gt;
&lt;p&gt;A different way to get measurements like that may be use a BLE sniffer, such as the &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE"&gt;nRF Sniffer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Regarding BLE advertising packet's transferring time on nrf52840</title><link>https://devzone.nordicsemi.com/thread/233428?ContentTypeID=1</link><pubDate>Mon, 10 Feb 2020 05:00:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:367abe89-bbea-4c50-a2d7-d1a9812aebdd</guid><dc:creator>Thinking_HyunSoo</dc:creator><description>&lt;p&gt;Thanks for replying.&lt;/p&gt;
&lt;p&gt;So then can i make time logs whenever i send advertising packet from peri to central beacon?&lt;/p&gt;
&lt;p&gt;I want to measure the time whenever peripheral beacon sends the advertising packet to the central one while they are connected.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m try to analyze the code on peripheral beacon, but i feel like i&amp;#39;m stock.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Regarding BLE advertising packet's transferring time on nrf52840</title><link>https://devzone.nordicsemi.com/thread/233108?ContentTypeID=1</link><pubDate>Thu, 06 Feb 2020 15:29:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0178d341-3b70-4e37-8562-04fb0c0b5f6c</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The logger module allows for configuring logs to be time stamped. You will see that for the project you are running, in main.c, the logger module is initialized with the line &amp;quot;ret_code_t err_code = NRF_LOG_INIT(app_timer_cnt_get);&amp;quot;. The &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v16.0.0%2Fgroup__nrf__log__ctrl.html&amp;amp;anchor=ga7b31e89afb175ae644037fac337bcfbd"&gt;NRF_LOG_INIT() &lt;/a&gt;macro takes a function as an argument, and that function is the function that provides the timestamps. &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v16.0.0%2Fgroup__app__timer.html&amp;amp;anchor=gae36265bac1480fbb1522f63f70ac369f"&gt;app_timer_cnt_get()&lt;/a&gt; is from the app timer library. This is not a Real Time Clock (RTC). We do have something named RTC on our SoC, but that is a &amp;quot;Real Time Counter&amp;quot;. It is basically a low-frequency timer that can be used by e.g. real time operating systems, or any other purpose that needs a slower, but less power consuming, timer. In fact the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v16.0.0%2Flib_timer.html"&gt;application timer library&lt;/a&gt; uses the RTC (that is, the Real Time Counter), but as it is not a Real Time Clock it only gives the amount of time that has passed since enabling the library.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>