mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced 2026-09-17 10:15:12 +00:00
iceman1001andClaude Opus 5 (1M context)
a967560335
The inter frame delay was 3600us for a 128 bit payload and 2400us for 256 bit, sized so that either one holds a constant 4.8ms repeat period. That is the wrong target. A Kovio tag is never transacted with - the reader captures it during a poll slot and hands the bytes up as an activation, see nfa_dm_disc_handle_kovio_activation() in libnfc-nci, which reads the barcode straight out of rf_tech_param.param.pk.uid - so the only thing that matters is how often a frame is on the air. Measured repeat period before today was 8.66ms, ie 14% duty cycle. A fixed 500us gap takes a 128 bit payload to roughly 2.2ms. The gap cannot go to zero, a reader needs unmodulated carrier to find the frame start and our own demod wants three quiet bytes, but 500us is an order of magnitude clear of that. Also drop the 'not correct' caveat from 'hf thinfilm list', the sim side traces properly now. Tested on RDV4 against an Android reader. Builds clean for PM3RDV4 and PM5. Co-Authored-By: Claude Opus 5 (1M context)
