https://devzone.nordicsemi.com/f/nordic-q-a/42652/nfc---communicaiton-problemDear Nordic, I am using nrf52DK I modified &quot;examples\nfc\writable_ndef_msg&quot; I am using an ingenico POS payment terminal The working flow is ; pos sends apdu-1, nrf52dk receives and responds pos sends apdu-2, nrf52dk receives and respondsen-USTelligent Community 13Mon, 21 Jan 2019 09:19:08 GMThttps://devzone.nordicsemi.com/thread/166748?ContentTypeID=1Mon, 21 Jan 2019 09:19:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:749b2b47-3734-4037-ae7e-57a161da79a8Kenneth<p><span>Have you tried shorter delays (10ms, 20ms, ... 90ms) to find the sweet spot where the field fails? I still think there is a timeout occurring&nbsp;for the transaction that cause the peer to turn OFF the field (this is not controlled by the nRF), and thereby you need to have two transaction in your case (the first will need to fail or you may consider send an empty packet for your first transaction).&nbsp;</span></p> <p><span>Best regards,<br />Kenneth</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/166253?ContentTypeID=1Thu, 17 Jan 2019 13:40:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6f21826c-3481-41c1-8b51-4af324eb5aadsami_ozen<p>I will go to a server process and comeback which is around 500ms. so i simulate this case.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/166239?ContentTypeID=1Thu, 17 Jan 2019 13:07:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:40b0db74-fc71-4a8f-bb26-e3c091046d54Kenneth<p>Why are you adding a 100ms delay? Back in the days (at least for wireless charging) I remember there were a timeout of 100ms if no response was received that caused the field to be turned OFF, have you tried shorter delays to find the sweet spot?</p> <p>Best regards,<br />Kenneth</p><div style="clear:both;"></div>