• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Low Power RF & Wireless Connectivity » RFID/NFC Forum » ISO14443 Air Interface Timing
Share
Low Power RF & Wireless Connectivity
  • Forums
  • Announcements
  • Files
  • E2E Wiki
Options
  • Subscribe via RSS

ISO14443 Air Interface Timing

ISO14443 Air Interface Timing

This question is not answered
Vladimir Nohava
Posted by Vladimir Nohava
on Aug 09 2012 17:19 PM
Prodigy175 points

Hello,

Do you have either measured or calculated ISO14443 A/B air interface timing like you have done for the ISO15693? I am currently using the trf7960 eval board.

I would like to know the fastest possible read time for example the ISO15693 Read Single Block total time = 4.56mSec taken from your 7658.ISO_15693_timing_JDW_05_27_2011.pdf

Thanks

Vlad

 

TRF7960 14443a 15693 ISO14443A/B
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Josh Wyatt
    Posted by Josh Wyatt
    on Aug 11 2012 17:27 PM
    Expert8800 points

    Vlad -

    sorry - the ISO15693 command of Read Single Block is not available with any ISO144443A or B device. Instead, they would be using an ISO7816-4 command like 'Read Binary', after being activated and selected with the ISO14443-3 commands.

    So - the request is a little bit complicated - but just for ballpark idea, the ISO14443 devices in general are going to be at a minimum about 5 times faster than the ISO15693 devices. But, the lower level activation and selection would all happen at 106kbps most likely, as TypeA only allows a baud rate change in the ISO14443-4 layer (for Type A is is done with the PPS Request/PPS Response sequence, for Type B, this would happen in Layer 3 with the ATTRIB command.

    anyway - what could be estimated here is the amount of data you want to retireve with the baud rates available/possible with card you are wanting to use. (106, 212, 424, 848kbps) 

    then you could add on the other protocol overhead bytes required for the activaiton and selection and come close to how long it would take.

    BR-

    Josh

    ---------------------------------------------------------------------------------------------------------
    Please click the Verify Answer
    button on this post if it answers your question.
    ---------------------------------------------------------------------------------------------------------

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Josh Wyatt
    Posted by Josh Wyatt
    on Aug 11 2012 21:17 PM
    Expert8800 points

    Vlad  -

    to add to this, please see attached spreadsheet which i started here for you to use - this should help you out and if you are using the ISO standards along with it, then it should be easier to figure out how long your processes will take. Let me know if you get stuck, etc. I did not have a ton of time to do this, but next i would be adding the layer 4 times.Note all three sheets in here.

    3386.ISO14443_times.xlsx

     

    BR-

    Josh

    ---------------------------------------------------------------------------------------------------------
    Please click the Verify Answer
    button on this post if it answers your question.
    ---------------------------------------------------------------------------------------------------------

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Vladimir Nohava
    Posted by Vladimir Nohava
    on Aug 13 2012 18:16 PM
    Prodigy175 points

    Hello Josh,

    Let's say we only need to read 4 different tags and we know the ID of each tag (either programing a value or reading the ID). Anti-collision will never happen since we can make sure the sensor will never read more than 1 card/tag at the same time. Preferable choosing the fastest data rate can be beneficial (848kbps). I can control the distance between the tag and sensor (within 4 inches). Pretty much a controlled environment. Choosing an ISO14443 command with the least amount of header bits and data bits to identify that particular card out of the 4. I'm not sure which command would be the fastest in 14443 A or B? With all this can we still be faster than ISO15693?

    I saw your spreadsheet and to me looks like the fastest speed at 106Kpbs (14443B) is 5mS+ 2.93mS = 7.93mS. This seems way slower than the ISO15693 at 4.56mS.

    Can you tell me with the 14443 optimum setup at 848kbps can we get that 5 times faster than 15693 including header bits? I am not familiar with the ISO14443 protocol at this point.

    Can we write to memory blocks like we can using the 15693 tags?

     

    Thanks

    Vlad

     

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use