<?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: CLRC663 and ILT-M tags in NFC</title>
    <link>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800310#M11238</link>
    <description>&lt;P lang="es-MX"&gt;Hello,&lt;/P&gt;
&lt;P lang="es-MX"&gt;Thank you for using our products.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Could you please test our &lt;A href="https://www.nxp.com/design/design-center/designs/nfc-reader-library-software-support-for-nfc-frontend-solutions:NFC-READER-LIBRARY" target="_blank"&gt;NFC Reader Library&lt;/A&gt;, the examples NfcrdlibEx3_NFCForum and, Nfcrdlib_SimplifiedAPI_ISO both examples should be able to detect 18000p3m3 tags.&lt;/P&gt;
&lt;P lang="es-MX"&gt;You shouldn't have any issues using our &lt;A href="https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/clrc663-iplus-i-nfc-frontend-development-kit-for-access-management-applications:OM26630FDK" target="_blank"&gt;CLRC663 Evaluation board&lt;/A&gt; for detecting these tags. In case you do, please share with us the log of the example. This will provide us with a little more information about what could be happening.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Feb 2024 22:21:50 GMT</pubDate>
    <dc:creator>Fabian_R</dc:creator>
    <dc:date>2024-02-01T22:21:50Z</dc:date>
    <item>
      <title>CLRC663 and ILT-M tags</title>
      <link>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800005#M11237</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;I'm currently tring to make our CLRC663 based board working with ILT-M tags.&amp;nbsp;&lt;/P&gt;&lt;P&gt;For that, I get some part of code in the NxpNfcRdLib_07.05.00 and other part in code provided in&amp;nbsp;SW335613.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The RFLibrary is not suitable as it cannot help to perform inventory of many tags.&amp;nbsp;&lt;/P&gt;&lt;P&gt;SW335613's&amp;nbsp; Inventory_18000p3m3 is more suitable for this purpose.&amp;nbsp; However please note that the code for Q adaptation is not working as the line fQ = round(fQ) (line 172) is not correct.&amp;nbsp; Q will never change if C is lower then 0.51. This line should be removed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whatever, with all settings from&amp;nbsp;NxpNfcRdLib_07.05.00 and algorithm based upon SW335613 I have very poor RF performances with the sample tags I get from you.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same board is working well up to 6cm range with ISO15693 tag but only 0.5 with ILT tags.&amp;nbsp; &amp;nbsp;This is very disappointing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How&amp;nbsp; much power does an ILT tag require ?&lt;/P&gt;&lt;P&gt;Does an ILT tag required such power that it is not suitable to be used with standard desktop RF reader with small antenna ?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 14:49:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800005#M11237</guid>
      <dc:creator>fredj0207</dc:creator>
      <dc:date>2024-02-01T14:49:39Z</dc:date>
    </item>
    <item>
      <title>Re: CLRC663 and ILT-M tags</title>
      <link>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800310#M11238</link>
      <description>&lt;P lang="es-MX"&gt;Hello,&lt;/P&gt;
&lt;P lang="es-MX"&gt;Thank you for using our products.&lt;/P&gt;
&lt;P lang="es-MX"&gt;Could you please test our &lt;A href="https://www.nxp.com/design/design-center/designs/nfc-reader-library-software-support-for-nfc-frontend-solutions:NFC-READER-LIBRARY" target="_blank"&gt;NFC Reader Library&lt;/A&gt;, the examples NfcrdlibEx3_NFCForum and, Nfcrdlib_SimplifiedAPI_ISO both examples should be able to detect 18000p3m3 tags.&lt;/P&gt;
&lt;P lang="es-MX"&gt;You shouldn't have any issues using our &lt;A href="https://www.nxp.com/products/rfid-nfc/nfc-hf/nfc-readers/clrc663-iplus-i-nfc-frontend-development-kit-for-access-management-applications:OM26630FDK" target="_blank"&gt;CLRC663 Evaluation board&lt;/A&gt; for detecting these tags. In case you do, please share with us the log of the example. This will provide us with a little more information about what could be happening.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 22:21:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800310#M11238</guid>
      <dc:creator>Fabian_R</dc:creator>
      <dc:date>2024-02-01T22:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: CLRC663 and ILT-M tags</title>
      <link>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800920#M11241</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We understand why we get such results.&amp;nbsp;&lt;/P&gt;&lt;P&gt;ILT Tags we have received from NXP (SMARTRAC 5x5cm) are turned to 53 MHz to support stacking.&lt;/P&gt;&lt;P&gt;With such tuning the RF performances are very limited when tags are not stacked. RF performances increase when stacking.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 14:36:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/CLRC663-and-ILT-M-tags/m-p/1800920#M11241</guid>
      <dc:creator>fredj0207</dc:creator>
      <dc:date>2024-02-02T14:36:58Z</dc:date>
    </item>
  </channel>
</rss>

