RFID/NFC Troubleshooting: Partial Read, Wrong UID, or Garbled Data
A “read” that flickers, shows the wrong UID once in a while, or returns half-meaningful bytes is usually not cryptography—it is coupling, interference, wrong band/mode, or a multi-tag field where anticollision never completed cleanly.
1) What this symptom usually means
- Unstable UID: the physical link is marginal; bits flip occasionally.
- “Almost right” data: often a framing/interpretation issue (wrong tag family selected in software).
- Intermittent success: multiple tags in the field, or noisy environment near readers with poor shielding.
2) Coupling, distance, and orientation
HF (13.56 MHz) and LF (125 kHz) antennas are not interchangeable in behavior: HF is more orientation-sensitive; LF is often more forgiving but slower and more sensitive to coil alignment.
- Move slowly: find the “hot spot” a few millimeters at a time.
- Hold steady for 2–3 seconds: some stacks need time to complete all frames.
- Reduce wobble: micro-movements look like garbled bytes in logs.
3) Metal, liquid, and stacked tags
- On-metal tags exist for a reason: standard tags detune badly on metal surfaces.
- Wallets and stacks: two cards in the same field can confuse anticollision or reduce coupling to both.
- Phone NFC: active polling and shielding can interact with your reader—test with phone radios off when isolating issues.
4) Wrong band or protocol mode
If your tool is in the wrong mode, you can still get something—but it may be nonsense or a mis-decoded UID.
- LF vs HF: confirm the tag family (Prox/HID-style LF vs MIFARE/NTAG-style HF).
- Software profile: selecting “generic” vs a specific tag type changes how bytes are parsed.
- UID vs memory: reading UID is not the same as reading user memory; don’t mix up command outputs.
5) Multiple tags and anticollision
NFC HF uses anticollision when more than one tag answers. If the field is messy, you can get partial inventory rounds or odd results.
- Isolate one tag physically (remove other cards/keyfobs from the area).
- Use a smaller antenna coil or reduce power if your tool allows—shrinks the interrogation zone.
- Retry with a slower workflow: rapid re-scans can catch the tag mid-state.
6) Auth-required memory vs “UID only”
Some outputs look “half empty” because sectors require keys. That is different from a bad physical read: the protocol completes, but the data you want is behind authentication.
- Document what reads without keys (often UID/public pages).
- Don’t treat key-gated failures as RF noise—treat them as access control working.
Validation criteria
- With a single lab tag isolated, you can read the same UID three times in a row without edits to setup.
- You can explain any remaining instability as coupling/metal/multi-tag—not “random magic.”
- You have written down band, tag family, and whether keys are required for the memory you care about.