MIFARE Classic (card already used)

- : MIFARE Classic or DESFire
- Card templates) : Card template (see
- The card template decides on:
- : must be available in free memory space on the card.
- AXM Classic automatically assigns lock IDs with LID 0-127 reserved for internal functions. : shows the number of possible locking device IDs for this card.
- See Cards and locking device IDs for background information.
- : shows the number of entries that can be written on this card’s physical access list. For AV templates only (Audit trail & Virtual network).
- : indicates whether a virtual network is possible. AV templates only.
The following is also determined for MIFARE Classic:
- SectList: List of sectors where the data from your locking system is stored.
- TransportSectorTrailer: Encryption of your locking system data on the card
- Card type: MIFARE Classic
- Read the card or consult the data sheet.
- Full report is displayed.
- Determine the available memory space or sectors (EXTRA # Memory size section).
- Card contains 16 sectors.
- Sector 0 is internal for MIFARE Classic and sector 1 should not be used, so there are 14 sectors available.
NOTE
Sector structure, card-specific
The sector structure may differ for your card. Cards with a larger memory in particular may have more master sectors (e.g. often sector 16) and different sector sizes, i.e. more storage space per sector.
Even on new cards, the manufacturer may have blocked sectors and these must first be unblocked.
In some cases, third-party applications also block all sectors, although they do not even use all sectors.
Example: MIFARE Classic EV1 4k: 4kB memory, divided into Sectors 0-31 with 4 blocks each and Sectors 32-39 with 16 blocks each. Sector 16 is another master sector here.
- Read the report carefully to determine master sectors and sector size.
- If you decide to have your card checked by SimonsVoss: Feel free to contact one of our sales representatives in your region.
- If necessary, unlock blocked unused sectors with the TransportSectorTrailer.
- Each sector consists of three writeable blocks and one block for encryption: 3*16 bytes = 48 bytes per sector.
- Available sectors can be identified in the report by three blocks marked [rwi]: read/write/increment – the fourth block is for encryption.
- Internal card sectors can be identified in the report by the fact that not all three blocks are marked with [rwi]:
- Sectors that have already been used can be recognised by the fact that the data can no longer be read in plain text:
- Sectors 2, 3, 4 and 5 have already been written on (e.g. by another application) and are not available for the locking system.
- Sectors 0 and 1 cannot be used either. As a result, the sectors available are: 6, 7, 8, 9, 10, 11, 12, 13, 14 and 15 (= 10 sectors available for the locking system).
- Calculate the available storage space: Bytes per sector * available sectors (example: 48 bytes * 10 sectors = 480 bytes).
- From the drop-down menu , select .
- Consider whether you need a physical access list or a virtual network for your cards.
- If you do: You need an AV template (="Audit trail and “Virtual network”).
- Determine the largest card configuration that fits into the available memory (see Card templates – example: MC1200L with 192 bytes).
- Select the configuration you just specified from the drop-down menu (example: MC1200L).
- shows the memory requirement on the card.
- AXM Classic automatically assigns lock IDs with LID 0-127 being reserved for internal functions). See Cards and locking device IDs for background information. shows the number of possible locking device IDs for this card (
- The number of entries for locking devices in the matrix is limited to the number of possible locking device IDs. Locking devices can also consume more than one entry, e.g. freely rotating Digital Cylinder AX.
- Physical access list not available (it is not an AV template).
- Virtual network not possible.
- Calculate the number of sectors actually needed: / bytes per sector (example: 192 bytes / 48 bytes = 4 sectors). Round off the result to the next integer if necessary.
- Click the button in the SectList field.
- The window will open.
- Enter as many free sectors as you need in the
Numbers separated by commas, without spaces. field (example: 7,8,9,10). Do not use sectors that are not writeable or used as a master sector (example: Sector 0 is not writeable and Sector 1 is a master sector). NOTE
Saved storage space thanks to own sector list
Obviously, you can also use the default sector list. However, it may even be the case that not all sectors from this list are used because the card configuration also fits into fewer sectors.
- Enter your own sector list.
- This allows you to save sectors on your cards that you might want to use for other applications in the future.
NOTE
Sectors do not need to be contiguous
The sector list does not have to be contiguous. If sectors in the middle of the sector list are used for other purposes, this is not a problem for AXM Classic.
- Click on the button.
- window closes.
- Leave the TransportSectorTrailer field unchanged.
- TransportSectorTrailer is an integral part of card encryption. Your AXM Classic will automatically generate this entry for you.
- Click on the button.
- Window Locking system closes.
- Card configuration saved.
AXM Classic only writes on the sectors specified in the sector list. All other sectors remain unchanged.
Other applications (e.g. canteen billing) simply continue to write on their “own” sectors. They work – completely separately from your AXM Classic as before.
Unlocking blocked sectors with the TransportSectorTrailer

In exceptional cases, another application may block sectors, but may not actually use them. In this case, you can use your AXM Classic to unlock these sectors and use them for your locking system.
NOTE
Malfunctions in other applications and/or your locking system
Data in sectors used by a specific application may only be modified by the application in question.
For example, if your locking system changes the data in a sector used by your canteen system, then the canteen system will most likely no longer be able to process data. Conversely, the canteen system can also render your locking system data unusable.
- Before unlocking “third-party” sectors, ensure that they are not really used.
- Consult the third-party application operator or the owner of the sectors.
- If you decide to have your card checked by SimonsVoss: Feel free to contact one of our sales representatives in your region.
- Click the button in the TransportSectorTrailer section.
- The window will open.
- Enter the TransportSectorTrailer into the field that the other application uses.
- Repeat the entry in the field.
- Click on the button.
- window closes.
- AXM Classic unlocks blocked sectors and uses them for the locking system.