MIFARE DESFire (card already in use)

The following are also determined for MIFARE DESFire:

  1. Card type: MIFARE DESFire
  1. Read the card or consult the data sheet.
  2. Full report is displayed.
  3. Locate the available storage space (Section # Memory information).
  4. Full storage space is no longer available on this card. This suggests that at least one other application is active and uses storage space.
  5. Use the full report to determine the app IDs of the existing applications:
  6. App ID 0 is assigned in the factory, the app ID 1 is a third-party application with a 192 byte memory.
  7. From the drop-down menuCard type, selectMIFARE DESFire.
  8. Consider whether you need a physical access list or a virtual network for your cards.
  9. If you do: You need an AV template (="Audit trail and “Virtual network”).
  10. Determine the largest card configuration that fits into the available memory (see Card templates – example for AV: MD4000L_AV with 1600 bytes).
  11. Select the configuration you just specified from the Configuration drop-down menu (example: MD4000L_AV).
  12. Memory requirements shows the memory requirement on the card.
  13. Lock IDs shows the number of possible locking device IDs for this 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.
  14. Physical accesses in the log shows the number of possible entries in the physical access list (for AV templates only).
  15. 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.
  16. The physical access list is overwritten on a rolling basis, so it is not limited.
  17. A virtual network is possible.
  18. Click the Edit button next to the app ID for the parameters.
  19. The Enter parameter value window will open.
  20. Enter an unused app ID as a decimal value (in the example, 0 and 1 are assigned – 2 is thus possible) in the New value field.
  21. NOTE

    notice

    Number of applications for DESFire EV1 and EV2

    MIFARE DESFire EV1 supports a maximum of 28 applications (0-27). The highest app ID is therefore App ID 27.

    MIFARE DESFire EV2 has no limits in this respect.

  22. Click on the OK button.
  23. Enter parameter value window closes.
  24. Click the Edit button next to CryptoMode for the parameters.
  25. The Enter parameter value window will open.
  26. Select the AES entry from the New value drop-down menu.
  27. Click on the OK button.
  28. Enter parameter value window closes.
  29. Click the Edit button next to PiccCryptoMode for the parameters.
  30. The Enter parameter value window will open.
  31. Select the AES entry from the New value drop-down menu.
  32. Click on the OK button.
  33. Enter parameter value window closes.
  34. Only edit the PiccMasterKey if the manufacturer has not set the PiccMasterKey to a default value.
  35. Your AXM Classic will determine the right PiccMasterKey itself. If you specify a PiccMasterKey, AXM Classic will only use this one and will not determine one.
  36. Click on the Finish button.
  37. Window Locking system closes.
  1. Card configuration saved.

NOTE

notice

PiccMasterKey identical throughout the locking system

The same PiccMasterKey must be used for all cards within a locking system.

The following phenomena may also occur with the DESFire cards used: