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.

Looking for TI NFC solution

Other Parts Discussed in Thread: TRF7964A, TRF7970A, RF430CL330H, RF37S114, TIDA-00217

Hello:

I am looking for the TI NFC solution and is there any good reference design for that application.

Kind regards

Fengzhou

  • Hi,

    if you are interested in a NFC Reader the TRF7964A or TRF7970A are the right choice. The FAQ document for this device contains more information:

    https://www.ti.com/lit/sloa246

    Best Regards,

    Helfried 

  • Hi Helfried: Thank you for your reply. I am interested in the NFC for data transfer and the writable NFC is my interest. Is there any suggested TI NFC with EEROM and energy harvesting function? Kind regards. Fz

  • Hi Fengzhou,

    depending on what your application is, you may have a look to the following devices:

    RF430CL330H (https://www.ti.com/product/RF430CL330H), which can provide data as NDEF message. This device needs in addition a MCU but a complete passive operation is possible. See this passive TI-Design:

    http://www.ti.com/tool/TIDA-00217

    RF430FRL15xH (https://www.ti.com/product/RF430FRL154H) this device can work passive and offers 2k of FRAM.

    RF37S114 (https://www.ti.com/product/RF37S114) a small 4x4mm transponder with 256 bit memory.

    Best Regards,

    Helfried

  • Hi Helfried: Thank you for your suggestion which is very useful. I will try the RF430CL330H although it only with RAM rather than ROM on board. However, the addition of MCU gives me the option to chose an ultra-low-power processor for other propurse. The only problem might require more energy consumption and a longer time for data transfer from MCU ROM to the NFC RAM. Any suggestions on that, especially for batterless operation mode?

  • Hi Fengzhou,

    the TI-Design TIDA-00217 is a battery less solution and has a rectifier with two diodes connect to the resonance circuit to generate the supply voltage for the MCU.

    Best Regards,

    Helfried

  • Hi Helfried: Thank you for commenting. If I am right, RF430CL330H does not energy harvesting feature and the batteryless solution is created manually by using half rectifier and a capcitor (100uF). However, it did not mention how to chose the capacitor? I suppose the capacitor selection must balance the charging and discharging time. If I use this circuit(for temperature measurement might consume less energy 10uA), and it might not good enough to provide enough energy for my applications. Is there any suggestion on that? Many thanks. Looking forward your reply. Kind regards.

  • Hello Fengzhou,

    I'm covering for Helfried during his vacation. The buffer capacitor size of the rectifier should be uncritical. There is no fix charge and discharge time frame from RF430CL330H or MCU perspective. The continuous RF is charging the MCU supply, which starts when enough voltage level is reached. The discharge is happening if you remove the passive system from the reader field. The only possible timing limitation would be your application needs.

    Best regards,

    Andreas Mueller.

  • Hi Andreas:

    Thank you for your reply and covering. Yes, I agree that the timing limitation is from my applications. I wonder to know how to control the voltage and current level for my applications. Does the RF430CL330H have a power management unit? If not, is there any suggested product to do this work?

    Looking forward to your reply.

    Kind regards

    Fengzhou 

  • Hello Fengzhou,

    The RF430CL330H current consumption depends on its activity and is automatically minimized.
    The voltage levels of your external energy harvesting circuitry could be controlled by any suitable voltage regulator or DCDC converter.

    Best regards,
    Andreas.

  • Hi,

    I haven’t heard back from you for a while, so this tread is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Best Regards,
    Andreas.