<?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>Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47816/using-timestamp-in-nrf9160</link><description>I want to read timestamp in my nRF9160 device and found that &amp;quot;z_tsc_read()&amp;quot; function in Zephyr RTOS will do that. However, I am not able to include the main library of the timestamp in the code and so I get the &amp;quot;undefined reference to `z_tsc_read&amp;#39;&amp;quot; error</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 07 Jun 2019 15:36:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47816/using-timestamp-in-nrf9160" /><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/191696?ContentTypeID=1</link><pubDate>Fri, 07 Jun 2019 15:36:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a448735e-1be3-4fc2-925e-8fe877bd51a7</guid><dc:creator>Hadrien Kohl</dc:creator><description>&lt;p&gt;According to the doc:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;This routine returns the elapsed time since the system booted, in milliseconds.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Event though it&amp;#39;s fine we can use this it is not an ideal solution since it means computing the datetime manually.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The battery consumption and power mode are also important factors. On a non embedded context I could simply ask for the time via IP but I&amp;#39;d rather have a real clock that runs even during low power modes.&lt;/p&gt;
&lt;p&gt;Is the problem with de AT+CCLK commands something that you know about? Will it be fixed?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/191692?ContentTypeID=1</link><pubDate>Fri, 07 Jun 2019 15:16:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e92bc5c6-f49c-42ea-9470-425b64ba8f36</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;See my last reply. You can use the system clock.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/191657?ContentTypeID=1</link><pubDate>Fri, 07 Jun 2019 12:37:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f297b4df-4df0-472a-a695-a62727e36c6b</guid><dc:creator>Hadrien Kohl</dc:creator><description>&lt;p&gt;I tried that but I am getting ERROR back. Is there anything one should do to prepare the modem before sending this command?&lt;/p&gt;
&lt;p&gt;Same goes for the AT+CCLK? command. Just getting ERROR. Even when I start with this one.&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;&amp;nbsp;I tried to initialise the modem using lte_lc but it does not fix the problem.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I am using the latest alpha modem firmware.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/191133?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 13:33:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7019884-a235-48b2-a834-9887ffafa523</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;The driver should be working fine, but the counter/alarm sample is currently not fully supported.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/191009?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 08:48:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:871de9dd-3c7f-46b1-b0b0-cd73356083d6</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;You also have the&lt;a href="https://docs.zephyrproject.org/latest/reference/kernel/timing/clocks.html#_CPPv312k_uptime_getv"&gt; system clock&lt;/a&gt;, from which you can get a time stamp by using k_uptime_get().&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/190614?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2019 19:05:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e64787a1-6c3f-4c9a-a04a-07adde073469</guid><dc:creator>Hadrien Kohl</dc:creator><description>&lt;p&gt;I&amp;#39;ve been looking into this as well. It seems that the RTC/Counter API is not yet implemented for the nrf91. &lt;/p&gt;
&lt;p&gt;In this PR there is an implementation but I think it is related to the 52.&lt;br /&gt;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/pull/8743/files"&gt;https://github.com/zephyrproject-rtos/zephyr/pull/8743&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It is part of a bigger PR that unifies the timer and counter APIs in Zephyr.&amp;nbsp;&lt;br /&gt;&lt;a href="https://github.com/zephyrproject-rtos/zephyr/pull/8340"&gt;https://github.com/zephyrproject-rtos/zephyr/pull/8340&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Can someone from Nordic confirm?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/190549?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2019 13:57:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bad5393-ca2c-40dc-a815-3a3ff6883dd6</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Perhaps you can look at the counter example in the Zephyr sdk then. The library you are referring to is not supported on the nrf91 board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/189994?ContentTypeID=1</link><pubDate>Wed, 29 May 2019 23:35:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29896f70-1827-46fa-8219-e1745e52928a</guid><dc:creator>Mohammad Amin</dc:creator><description>&lt;p&gt;Thanks. But the problem is the accuracy of +CCLK is in seconds. I want to measure the time in microseconds. That&amp;#39;s why I want to use timestamp, however,&amp;nbsp;still I couldn&amp;#39;t solve its issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Timestamp in nRF9160</title><link>https://devzone.nordicsemi.com/thread/189850?ContentTypeID=1</link><pubDate>Wed, 29 May 2019 11:28:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab0fb13f-8d3a-4d52-b7f1-f07152a25d53</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello, you can use the +CCLK at command to read the real time clock from the modem. You need to manually set the time first with&lt;/p&gt;
&lt;p&gt;&amp;quot;&lt;code&gt;AT+CCLK=&amp;quot;yy/MM/dd,hh:mm:ss±zz&amp;quot;,&lt;/code&gt; as described &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=/ref_at_commands/REF/at_commands/mob_termination_ctrl_status/cclk.html&amp;amp;resultof=%22at%2bcclk%22%20%22cclk%22%20"&gt;here&lt;/a&gt;.&lt;code&gt;&lt;br /&gt;&lt;/code&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>