© Nedap N.V.
Nedap Readers Installation Guide
Page 7 of 21
2.
Cards read by Convexs/Invexs
The Convexs/Invexs is capable of reading different card credentials simultaneously. The letter stands for the card
credentials:
•
M
: Mifare
MD
: Mifare and DESFire
•
MN
: Mifare and Nedap
MND
: Mifare and Nedap and DESFire
Depending of the configuration of the Convexs/Invexs the user itself can determine how the cards that are read
must be sent to the output.
The Convexs/Invexs
MN
and Convexs/Invexs
M
can be made suitable for reading DESFire cards at the customer
using a special card (
DEScount
card); contact Nedap for more details. (Or order the Convexs/Invexs MD at
Nedap.)
2.1.
Nedap cards
All Nedap cards can be read:
•
CF, DF and GF codes, C, D and G codes, A and B codes
At the ‘Direct transmission mode’ (all data read is sent unchanged to the output, defined with AEreco as
Nedap
RF data
or
RS485NR
), no additional configurations have to be made.
If needed a check at the customer code is possible. If this is configured, only cards with one of the defined
customer codes are read and sent to the output.
If the data read is been translated to another code (e.g. Wiegand) you can state for each Nedap customer code a
specific Wiegand customer code (or another Wiegand code). (Keep in mind if this makes any sense!)
2.2.
Mifare cards
For Mifare the common used types can be read (Mifare, Mifare Ultralight and DESFire, including EV1):
•
Card Serial Number (CSN, 7 bytes or 4 bytes)
•
Data direct from one of the sectors / files
•
Data from one of the sectors, using MAD (Mifare Application Directory)
All necessary settings (MAD or sector number, used security keys, location of data, interpretation of the data,
etc) have to be made using AEreco. If desired this can be done by the customer itself so the customer keeps the
control over the Mifare security keys.
At the ‘Direct transmission mode’ (all data read is sent unchanged to the output, defined with AEreco as
Nedap
RF data
or
RS485NR
), no additional configurations have to be made. The interpretion of the card data is now
done at AEOS, not at the Convexs/Invexs.
The Mifare cards can also be transferred to the output as Nedap cards (pay attention of the maximum card
number and the chosen customer code, this is depending of the Nedap device that is connected to the
Convexs/Invexs).
Remark
: This last option can only at special request be programmed at Nedap, so not with the standard AEreco
program.
At the Mifare part it is possible to determine a part of the Mifare data as customer code. This customer code of
the Mifare part can be used to expand the data read to different codes to the output.
Attention
:
For programming the correct settings at AEreco for the reading and handling the Mifare cards,
knowledge of Mifare cards must be available. E.g. for retrieving the data from the Mifare card it must be know
where the data is located, which principle is used, what the keys are, etc, etc.
