PHYSICAL READER DIAGNOSTICS
Meet your cards.
Know their limits.
Identify what your PN532 can detect before provisioning patient identities. Import a sanitized reader report—no raw card UIDs, no medical records, no hidden cloud connection.
◉UNPROVISIONED TEST CARD
▧
PN532ARDUINO · USB
⌁
SANITIZED REPORTLOCAL DESKTOP
UNIQUE TAGS—
READ EVENTS—
PN532 STATUSNO REPORT
PRIVATE AUTHENTICATIONNOT TESTED
01 / LOCAL IMPORT
↓Import a scan report
The Arduino inspector produces a serial event stream. The desktop collector removes UIDs and saves a JSON report that you can open here.
⌗
Choose a sanitized JSON reportOnly parsed by this browser tab · Up to 1 MB
No physical reader has been connected to this browser.
02 / RUN CAPTURE
python tools/nfc_probe.py --list-ports python tools/nfc_probe.py --port COM4 --seconds 30 --output reports/bench.json
For Linux, replace COM4 with your actual port, such as /dev/ttyACM0. Install requirements-hardware.txt first. Close Arduino Serial Monitor before capture.
03 / TEST CARD INVENTORY
◎Detected NFC samples
READER FIRMWARE—INTERFACE—
Import the sample report or scan physical test tags to see device findings here.
ENGINEERING GATE / 04
What qualifies a card for Hospital OS?
Do not choose a production card based on scan success alone. Each chip family needs an explicit security capability assessment.
Ordinary NTAG / UltralightPublic NDEF contact linkPUBLIC ONLY
MIFARE ClassicLegacy test cards; not recommended for strong protectionNOT APPROVED
DESFire EV3Target for authenticated private file access after provisioningCANDIDATE
125 kHz RFIDNot compatible with the PN532 HF readerSEPARATE READER