This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RF430CL330H: The way of thinking about Latency

Guru 24520 points
Other Parts Discussed in Thread: RF430CL330H

Hi community member,

Would you please teach me the way of thinking about the latency for RF430CL330H?

And can you estimated the latency in case of using RF430CL330HTB?

If you have any question, please let me know.

Best regards,

Kaka

  • Kaka,

    There are different points of latency when using a device like the RF430CL330H.  I will try to discuss them all below.

    Power up - RF430CL330H requires a maximum of 20ms to stabalize before you can begin I2C communications.  You can check the status register to determine when the device is ready.  Bit 0 will be set when it is ready for communication.

    Initialization(Configuring registers and writing NDEF message) - This time will vary based on clock speed and length of NDEF message being written.  Some examples are shown in this other thread... http://e2e.ti.com/support/wireless_connectivity/f/667/p/377085/1327435.aspx#1327435

    Time for PCD to read or write RF430CL330H - This will be dependent on the device used.  Some common Android phones measured throughput is shown in the users guide below, table 3.

    http://www.ti.com/lit/pdf/tidu378

    Interrupt Handling(optional) - Some additional time is required if your application is handling the interrupt which can be triggered at the end of a read or write via the NFC over the air interface.  If you need to analyze the data received from the interrupt, this could also add some latency.

    Error checking(optional) - The RF430CL330H offers CRC and BIP-8 modes for error checking.  If these modes are used, you need to take into account the additional time required for error checking.   

    Let me know if you have specific concerns and we can address those.  Thanks!