So we can eg change polling loop frequency by setting TOTAL_DURATION

currently, in the NCI stateMachine, the first check is for timeOut and then we check for having received a message.
If for some reason the DH runs the NCI stateMachine after the timeOut (eg due to being blocked somewhere else in code) but the NFC device answered in time, the timeOut will still trigger.
By checking for having received a msg first, and only when nothing received checking for timeOut, the behaviour will be more robust.

Make ReaderWriter activate/deactivate certain tag types.
Then during initialization, the NCI stateMachine pulls the list and makes the necessary RF_DISCOVER_MAP_CMD requests to the NFC device

or move the readerWriter to the examples

According to the PN7150 datasheet, it should support these tags, but with its default config I can't get them detected.

After detecting tags, you can deActivate the reader. Then it goes idle and back to discovery. This happens in the order of milliseconds, so a single tag, is detected several times.

It would be better to not clear the list of Tags and :

• add only new ones. Overwrite the oldest if the list is full
• indicate the difference between a new one and a re-detected tag

refactor the code to extract the timer into an embedded runTimer object

whenever an unexpected message is received, or no message at all is received (timeout)

You mentioned membership in NFC Forum is needed to get the reference documents you require. It looks like the entry level is 1500$, which is too much for me, but if there are alternatives I could be able to chip in. Also I found one implementation that you may not be aware of here: https://libstock.mikroe.com/projects/download/4732/0/4732_nfc_2_click.zip
For my project I will be polling 6 off PN7150, and I need both Active mode, Passive mode, and Point-to-pint communication. My language of preference is Python (CircuitP), but anything goes. Please tell if there is anything I can do to help.

Currently only detecting the UniqueID length and the UniqueID itself.
Could add other info such as tagType, Data-exchange protocols, DiscoverID etc.