CR95HF UART no longer responding after a couple of days

[ooswald]

We've built several prototypes of an IoT device that uses the CR95HF to detect the presence of 14443A tags and read their UID. The devices work fine for days/weeks, until eventually no data is received from the CR95HF UART.

To work around the issue we've implemented sending ECHO (0x55) in a loop which sometimes brings the CR95HF back to life (after minutes/hours of echoes). Often the only way out is to power cycle the CR95HF which unfortunately is not a solution, as end users will have to pull the battery to achieve that.

This issue currently prevents us from going into manufacturing.

Is there a way to reset the CR95HF UART communication without power cycling it?

[Peter Boringer]

​Hello ooswald,

1st what are the settings of the CR95HF how it is configured and what are the wake up sources?

Then:

Can you provide more information on your error ?

Do you have a trace that shows the blocking point?

Does the UART communication  broken when the issue is coming? or it is a RF communication issue?

Do you know how many echo command have been sent to go back to life?

Thank for your feedbacks

PB

[LM]

Hi ooswald,

did you found the solution how to reset the CR95HF without power cycle?

Thank you