<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 3100RTC not accurate in NFC</title>
    <link>https://community.nxp.com/t5/NFC/3100RTC-not-accurate/m-p/1003818#M6592</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TFRO is calibrated during production at 30ºC but only for a short time, limiting costs and accuracy. With a fixed environment and steady battery voltage, the deviation will be constant - we didn't find any significant&amp;nbsp;aging effect. There is more information available in the SDK release zip file you downloaded under &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;lt;SDK&amp;gt;/docs/AN_NHS31xx_RTC_accuracy.pdf&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;BR /&gt;Dries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Jan 2020 21:11:48 GMT</pubDate>
    <dc:creator>driesmoors</dc:creator>
    <dc:date>2020-01-14T21:11:48Z</dc:date>
    <item>
      <title>3100RTC not accurate</title>
      <link>https://community.nxp.com/t5/NFC/3100RTC-not-accurate/m-p/1003817#M6591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;dear sir&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;i test 3100 rtc function with SDK release_mra2_10_1_nhs3100,i use the&amp;nbsp;app_demo_dp_tlogger project with the APP NHS3100 temperature logger.&lt;/P&gt;&lt;P&gt;i know the procedure when use the 3100 about rtc&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;when set config&amp;nbsp; the rtc will be set with&amp;nbsp;Chip_RTC_Time_SetValue function (this value is phone time )&lt;/LI&gt;&lt;LI&gt;when i get config ,i can get the rtc value from&amp;nbsp;Chip_RTC_Time_GetValue function ,(this value is time running by 3100)&lt;/LI&gt;&lt;LI&gt;in fact ,after running 1 day ,i get the rtc from 3100 is 2 minutes smaller than the phone time .&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;is there anything wrong ?why 3100 rtc is not&amp;nbsp; accurate as expect ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jan 2020 03:39:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/3100RTC-not-accurate/m-p/1003817#M6591</guid>
      <dc:creator>xiangxuejiao00</dc:creator>
      <dc:date>2020-01-14T03:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: 3100RTC not accurate</title>
      <link>https://community.nxp.com/t5/NFC/3100RTC-not-accurate/m-p/1003818#M6592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TFRO is calibrated during production at 30ºC but only for a short time, limiting costs and accuracy. With a fixed environment and steady battery voltage, the deviation will be constant - we didn't find any significant&amp;nbsp;aging effect. There is more information available in the SDK release zip file you downloaded under &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;lt;SDK&amp;gt;/docs/AN_NHS31xx_RTC_accuracy.pdf&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;BR /&gt;Dries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jan 2020 21:11:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/3100RTC-not-accurate/m-p/1003818#M6592</guid>
      <dc:creator>driesmoors</dc:creator>
      <dc:date>2020-01-14T21:11:48Z</dc:date>
    </item>
  </channel>
</rss>

