<?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>nRF51 --&amp;gt; wireshark , absolute time (as in not a date in 1970 but 2018-04-15-ish :) )</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33409/nrf51----wireshark-absolute-time-as-in-not-a-date-in-1970-but-2018-04-15-ish</link><description>Using some of our nRF51 dongles as sniffers to debug BLE. 
 Sniffer software --&amp;gt; &amp;quot;w&amp;quot; --&amp;gt; Wireshark, no problems. 
 Post processing wireshark export *.csv files. No problems 
 Cannot figure out how to get real time in the wireshark .csv files. 
 Multitudinous</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Apr 2018 12:29:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33409/nrf51----wireshark-absolute-time-as-in-not-a-date-in-1970-but-2018-04-15-ish" /><item><title>RE: nRF51 --&gt; wireshark , absolute time (as in not a date in 1970 but 2018-04-15-ish :) )</title><link>https://devzone.nordicsemi.com/thread/128472?ContentTypeID=1</link><pubDate>Mon, 16 Apr 2018 12:29:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:770f8f7b-7267-407d-85ef-aac5c7d16ad6</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Timeline in the sniffer is relative and it has 2 points that are usable and 1 that is not.&lt;/p&gt;
&lt;p&gt;1. The timestamp that wireshark places is the PC timestamp when the packet is received in Wireshark.&lt;/p&gt;
&lt;p&gt;2. The timestamp that is included in the packet i.e. &lt;strong&gt;delta time end to start&lt;/strong&gt; is being measured in the firmware and is the delta from the end of one packet to the start of the next. This can be used to build the timeline in combination with the lengths of the sniffed packets. You must take care to account for packet overhead to get the timeline correct.&lt;/p&gt;
&lt;p&gt;3 (not usable): the delta time start to start is buggy and is not reliable. This is calculated in wireshark.&lt;/p&gt;
&lt;p&gt;===CSV===&lt;/p&gt;
&lt;p&gt;It may be possible to use tshark and dump it out in CSV but tshark does not support the BTLE sniffer as it requires a device to be selected.&lt;/p&gt;
&lt;p&gt;Can you use the python sniffer API that is bundled with the sniffer (see snifferAPI.zip) or the&amp;nbsp;&lt;a href="https://learn.adafruit.com/introducing-the-adafruit-bluefruit-le-sniffer/python-api"&gt;sniffer library from adafruit&lt;/a&gt;&amp;nbsp;to achieve what you want ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Does this help ?&lt;br /&gt;David&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>