Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Site Specific Keys do not transfer to Cardax IV-connected T-Series readers

Use an Admin Card to update Site Specific Keys on Cardax IV-connected T-Series readers.

If a site has T-Series readers connected to controllers via a Cardax IV connection instead of HBUS, the Cardax IV protocol does not support transferring Site Specific Keys to the reader. Gallagher's alternative method is the Admin Card.

This issue is specific to Cardax IV-connected T-Series readers only. HBUS-connected readers receive keys directly from the controller.

Requirements

  • The Admin Card feature is found on the Server Properties tab in Configuration Client.

  • The card used as an admin card must be a blank MIFARE Plus 4k or DESFire 4k card, minimum.

  • The site does not need encoding enabled on the licence, just a USB encoder.

  • "Allow Admin card update at readers" must be checked for the card to work at Cardax IV-connected readers.

Generate Admin Card dialog for Cardax IV T-series reader key update

Update keys with an Admin Card

  1. Go to Server Properties tab in Configuration Client.

  2. Encode an Admin Card using a blank MIFARE Plus 4k or DESFire 4k card.

  3. Present the Admin Card to the reader. The reader will flash white 3 times, then resume functionality with the new keys.

Command Centre 8.30 and above

MIFARE keys, Classic, Plus and DESFire, are held on the controller, not in the reader. If the reader is connected as a Cardax IV reader, the reader can have its keys updated by presenting an Admin Card.


🔗 Related

Last updated

Was this helpful?