User Tools

Site Tools


cvend

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
cvend [2026-03-16 05:39 UTC (2 weeks ago)] – [Card reader flow] penguinowlcvend [2026-03-17 20:08 UTC (2 weeks ago)] (current) – [Card reader flow] penguinowl
Line 83: Line 83:
 <- - Reader to Host <- - Reader to Host
  
-==== Card reader flow ====+==== Sample reader flow ====
  
   - Host enables desired card type with ''ProxCardFunction''.   - Host enables desired card type with ''ProxCardFunction''.
   - Reader acknowledges with ''ProxCardFunctionReply''.   - Reader acknowledges with ''ProxCardFunctionReply''.
-  - Reader waits for card, will eventually go to sleep without any stimuli. Can reawaken it with any host command (e.g. ''Status'').+  - Reader waits for card, seems like it eventually goes to sleep without any stimuli. Might have to keep it awake by sending packets occasionally (e.g. ''Status'').
   - When card is scanned, reader sends the corresponding read packet if the card type is enabled (e.g. ''DESFireRead'' for DESFire). If type is not enabled, sends ''UnhandledCard''.   - When card is scanned, reader sends the corresponding read packet if the card type is enabled (e.g. ''DESFireRead'' for DESFire). If type is not enabled, sends ''UnhandledCard''.
   - Card data can then be queried by sending the equivalent command packets. DESFire commands are documented in {{ 0:m075031_desfire.pdf }}. Example for reading a page off a DESFire ( all of the following packets are of type ''DESFireCommand'' and ''DESFireCommandReply''):    - Card data can then be queried by sending the equivalent command packets. DESFire commands are documented in {{ 0:m075031_desfire.pdf }}. Example for reading a page off a DESFire ( all of the following packets are of type ''DESFireCommand'' and ''DESFireCommandReply''): 
cvend.1773639573.txt.gz · Last modified: by penguinowl