<?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 About Type B PICC's data length setting. in NFC</title>
    <link>https://community.nxp.com/t5/NFC/About-Type-B-PICC-s-data-length-setting/m-p/684178#M2313</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Community team,&lt;/P&gt;&lt;P&gt;Customers are using PR5331C3HN/C360 in HSU mode.&lt;BR /&gt;PICC is Type B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although 256 bytes of data are transmitted from PICC, PR 533 can receive only 253 bytes.&lt;BR /&gt;I think that this is "Truncated Received data in HSU transparent mode" described in the User Manual.&lt;BR /&gt;It has the following description:&lt;BR /&gt;&amp;nbsp; With ISO1443 cards, the size can be limited by sending an FSDI of 7 during &lt;BR /&gt;&amp;nbsp; RATS. Then the card will send frame with a max size of 128 bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Type B PICC, I think that the above RATS command can not be done, is it correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of Type B PICC, there is no data length setting in ISO 14443 which is the standard specification, and will it be necessary to adjust the data length with its own specification of PICC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Yasushi Hasegawa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Jul 2017 00:31:46 GMT</pubDate>
    <dc:creator>yasushihasegawa</dc:creator>
    <dc:date>2017-07-05T00:31:46Z</dc:date>
    <item>
      <title>About Type B PICC's data length setting.</title>
      <link>https://community.nxp.com/t5/NFC/About-Type-B-PICC-s-data-length-setting/m-p/684178#M2313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Community team,&lt;/P&gt;&lt;P&gt;Customers are using PR5331C3HN/C360 in HSU mode.&lt;BR /&gt;PICC is Type B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although 256 bytes of data are transmitted from PICC, PR 533 can receive only 253 bytes.&lt;BR /&gt;I think that this is "Truncated Received data in HSU transparent mode" described in the User Manual.&lt;BR /&gt;It has the following description:&lt;BR /&gt;&amp;nbsp; With ISO1443 cards, the size can be limited by sending an FSDI of 7 during &lt;BR /&gt;&amp;nbsp; RATS. Then the card will send frame with a max size of 128 bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Type B PICC, I think that the above RATS command can not be done, is it correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of Type B PICC, there is no data length setting in ISO 14443 which is the standard specification, and will it be necessary to adjust the data length with its own specification of PICC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;BR /&gt;Yasushi Hasegawa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jul 2017 00:31:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/About-Type-B-PICC-s-data-length-setting/m-p/684178#M2313</guid>
      <dc:creator>yasushihasegawa</dc:creator>
      <dc:date>2017-07-05T00:31:46Z</dc:date>
    </item>
  </channel>
</rss>

