| submitted | available | document details (if available) | source link |
|---|---|---|---|
| January 07 2011 | May 07 2011 |
| various | manual | Users Manual | 797.68 KiB | January 07 2011 / May 07 2011 |
Nedap Readers Convexs & Invexs Installation Guide and User Manual 1 4 7 C 2 5 3 6 8 9 0 E 1 4 7 C 2 5 3 6 8 9 0 E 11 April 2011 Version 9 This information is furnished for guidance, and with no guarantee as to its accuracy or completeness; its publication conveys no licence under any patent or other right, nor does the publisher assume liability for any consequence of its use; specifica-
tions and availability of goods mentioned in it are subject to change without notice; it is not to be reproduced in any way, in whole or in part, without the written consent of the publisher. Nedap N.V., IDEAS P.O. Box 103 NL-7140 AC GROENLO The Netherlands Page 1 of 21 0 Convexs MN80(F)X, Convexs MND80(F)X (X is G or C) with FCC ID: CGDCONVEXS Convexs MND80G with IC ID: 1444A-CONVEXS Convexs M80(F)X, Convexs MD(F)X for USA acc. To Part 15 FCC ID: CGDCONVEXSM This device complies with part 15 of the FCC Rules and to RSS210 of Industry Canada. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation. Changes or modifications not expressly approved by party responsible for compliance could void the users authority to operate the equipment. Cet appareil se conforme aux normes RSS 210 exempts de license du Industry Canada. L'opration est soumis aux deux conditions suivantes (1) cet appareil ne doit causer aucune interfrence, et (2) cet appareil doit accepter n'importe quelle interfrence, y inclus interfrence qui peut causer une opration non pas voulu de cet appareil. Les changements ou modifications nayant pas t expressment approuvs par la partie responsable de la conformit peuvent faire perdre lutilisateur lautorisation de faire fonctionner le matrial. CONTENTS 1. Nedap Readers General Information ______________________________________________________ 4 1.1. Nedap readers principle ____________________________________________________________ 4 1.2. Availability Convexs 80 readers: ____________________________________________________ 4 1.3. Availability Invexs 170 readers: _____________________________________________________ 4 1.4. Availability Invexs 190 readers: _____________________________________________________ 5 1.5. Functionality ____________________________________________________________________ 5 2. Cards read by Convexs/Invexs ___________________________________________________________ 7 2.1. Nedap cards _____________________________________________________________________ 7 2.2. Mifare cards ____________________________________________________________________ 7 3. Convexs/Invexs Protocols ______________________________________________________________ 8 3.1. RS485NR (including RS485NR2) ___________________________________________________ 8 3.2. RF output _______________________________________________________________________ 8 3.2.1. RF output to AX1014 on AEpacks ____________________________________________ 8 3.2.2. RF output to Nedap XS readers for AEOS integration _____________________________ 9 3.2.3. RF output to Nedap XS readers at a WinXS system _______________________________ 9 3.3. Wiegand _______________________________________________________________________ 9 3.3.1. Wiegand formats _________________________________________________________ 10 3.3.2. Wiegand timing __________________________________________________________ 10 3.3.3. Wiegand 26 _____________________________________________________________ 10 3.3.4. Wiegand 32 _____________________________________________________________ 11 3.3.5. Wiegand 32bin __________________________________________________________ 11 3.3.6. Wiegand 37 _____________________________________________________________ 11 3.3.7. Wiegand 64bin __________________________________________________________ 11 3.3.8. Wiegand 128bin _________________________________________________________ 11 3.4. Serial RS485 (RS485 Ascii) _______________________________________________________ 12 3.4.1. Default settings __________________________________________________________ 12 3.4.2. Data format _____________________________________________________________ 12 3.5. USB Desktop reader _____________________________________________________________ 12 3.5.1. Default settings __________________________________________________________ 12 3.5.2. Data format _____________________________________________________________ 12 4. Convexs/Invexs connections ___________________________________________________________ 13 4.1. Convexs Connections ____________________________________________________________ 13 4.2. Invexs 170 Connections __________________________________________________________ 13 4.3. Invexs 190 Connections __________________________________________________________ 13 4.4. Connections using RS485 _________________________________________________________ 14 4.5. Connections using RF output ______________________________________________________ 14 4.6. Wiegand ______________________________________________________________________ 15 Nedap N.V. Nedap Readers Installation Guide Page 2 of 21 5. Convexs/Invexs LED and Beeper control _________________________________________________ 16 5.1. User LEDs ____________________________________________________________________ 16 5.2. Beeper ________________________________________________________________________ 16 5.3. Status LEDs ___________________________________________________________________ 16 6. Invexs PIN modes ___________________________________________________________________ 16 6.1. RS485NR _____________________________________________________________________ 16 6.2. Wiegand ______________________________________________________________________ 16 7. Configuring the Convexs/Invexs ________________________________________________________ 17 7.1. Nedap reader Configuration file ____________________________________________________ 17 7.2. Configuration card _______________________________________________________________ 18 8. Updating firmware of the Convexs/Invexs _________________________________________________ 18 9. Default settings of the Convexs/Invexs ___________________________________________________ 18 10. Available reader firmware _____________________________________________________________ 19 10.1. AEOS versions _________________________________________________________________ 19 11. Known problems ____________________________________________________________________ 20 11.1. Convexs/Invexs to AP1002 ________________________________________________________ 20 11.2. Convexs/Invexs to Nedap readers with AM badges _____________________________________ 20 11.3. Convexs/Invexs to AP4003 using RS485 _____________________________________________ 20 11.4. Convexs/Invexs to AP4003 using RS485 Tamperswith / PIN _____________________________ 20 11.5. Convexs/Invexs to AP4x03X series before production code W2 using RS485 ________________ 20 11.6. Invexs with display / screen ________________________________________________________ 20 12. AEreco cards enquiry information _______________________________________________________ 21 13. Document History ___________________________________________________________________ 21 Nedap N.V. Nedap Readers Installation Guide Page 3 of 21 1. Nedap Readers General Information The Nedap readers (e.g. Convexs or Invexs readers) enables smooth migration to Mifare card technology in both existing Nedap XS and Nedap AEOS Enterprise systems. It is capable of reading both Nedap and Mifare cards. The cards that are read are converted (and optionally filtered) to the selected output format. The readers output (the data the Convexs or Invexs reader sends) can be set to either Wiegand, XS RF modulation or RS485 protocol (encrypted for connection to AEOS or plain output). Installation aspects and technical data of the Nedap readers can be found in their corresponding Installation sheets (e.g. Convexs_InstallSheet_E) With Mifare also the Mifare Ultralight card is included, DESFire included EV1 card (check firmware version). 1.1. Nedap readers principle 1.2. 1 4 7 C 2 5 8 0 3 6 9 E Nedap reader configuration
(Conversion settings and formats) Outputs:
- Nedap RF data
- Nedap RF badge
- RS485 NR
- Wiegand
- Serial (RS485) plain Card credentials
- Nedap
- Mifare Availability Convexs 80 readers:
Convexs M80xx Convexs MD80xx Convexs MN80xx Convexs MND80xx Surface mounted G C 9856250 9856900 9856110 9896210 Gray 9895400 9895680 9895850 9896040 Charcoal Flush mounted FG 9856420 9857060 9856390 9896350 FC 9895540 9895710 9895990 9896180 Flush, Gray Flush, Charcoal Credentials Mifare Mifare - DESFire Mifare - Nedap Mifare - Nedap DESFire Gray=Light, Charcoal=Dark For both Surface mounting and flush mounting rugged Protectors are available, making the Convexs more vandal resistant. 1.3. Availability Invexs 170 readers:
Surface mounting Flush mounting Protectors The Invexs can read Mifare, DESFire and Nedap cards, and is equipped with keypad and / or a display. Following Invexs 170 readers are available (with white or black back plane, Screen / display only on request) M170 Mifare MD170 Mifare DESFire MN170 Mifare Nedap MND170 Mifare DESFire Nedap Colour Black White Black White Black White Black White Reader Keypad Screen / Display M170B M170W MD170B MD170W MN170B MN170W MND170B MND170W 9833900 MK170B 9832750 MK170W 9834400 MDK170B 9834370 MDK170W 9834060 MNK170B 9832890 MNK170W 9899570 MNDK170B 9899430 MNDK170W 9834230 MKS170B 9832920 MKS170W 9834680 MDKS170B 9834540 MDKS170W 9833730 MNKS170B 9833080 MNKS170W 9938761 MNDKS170B 9938753 MNDKS170W 9939822 9833390 9939849 9891820 9833870 9833420 9938796 9938788 Nedap N.V. Nedap Readers Installation Guide Page 4 of 21 1.4. Availability Invexs 190 readers:
The Invexs 190 is designed to be used on door pillars (mullion) and suitable for outside and inside use. A model with keypad is also available. Invexs 190 Reader Invexs 190 Reader + Keypad Credentials Invexs M190 Invexs MD190 Invexs MN190 Invexs MND190 9945512 9948406 9948392 9948414 Invexs MK190 Invexs MDK190 Invexs MNK190 Invexs MNDK190 9948422 Mifare 9948457 Mifare + DESFire 9948449 Mifare + Nedap 9948465 Mifare + Nedap + DESFire 1.5. Functionality Functionality and output format of the Convexs or Invexs reader is determined by the configuration of the Convexs reader. This configuration is defined using the program AEreco, and deployed by the Convexs configuration card or via AEmon (the configuration file is then uploaded to the Convexs as connected to the APx003). Depending of the used configuration the cards read by the Convexs (XS and/or Mifare) can be sent to the output using different communication principles:
RS485NR, all data read by the Convexs is transparently sent to AEOS. To be connected to o AEOS reader interface AEpacks
(e.g. AP1003, 1 2 34 5 67 8 9C 0 E AP4003), use firmware: APx003rs485NR2 Data read from card is transferred (encrypted) directly to AEpack. LEDs and Beeper are controlled by the communication over RS485. (No separate cables for the LEDs are used.). Beeper also can be controlled by hardware or configuration. Power must be supplied additionally to the Convexs/Invexs. Not all Nedap AEpacks have RS485 on board. Check the used AEpacks. Use the AX1012 to convert RS232 to RS485. RF output To be connected to o AEOS Nedap reader AEpacks (e.g. AP1001, AP4001) using AX1014. All data (Nedap RF data) or the (converted) badge
(Nedap RF badge) is sent over the existing RF cable. Check firmware in AEpack:
- New updated firmware ( 03-2008) transfers all data read from the card transparently to AX1014 AX1014 AX1014 AX1014 AX1014 1 2 3 4 5 6 7 8 9 C 0 E AEpack (no limitions to card number)
- Not advisable using the older firmware: the Mifare cards must be converted to XS code, max label number 999.999 o Nedap XS readers (AB350 on Accessor, SimpleXS, AC3/2TR), to be connected to AP1003 and AX1011 for integration with AEOS. All data (Nedap RF data) or the (converted) badge
(Nedap RF badge) is sent over the existing RF cable.
- New updated firmware ( 03-2008) transfers all data read from the card transparently to SimpleXS AC3/2TR Accessor III /
AB350 1 2 34 5 67 8 9 C 0 E AX1011 AEpack (no limitions to card number)
- Not advisable using the older firmware: the Mifare cards must be converted to XS code, max label number 999.999 o Nedap XS readers (AB350 on Accessor, SimpleXS, AC3/2TR), to be connected to WinXS systems. The (converted) badge (Nedap RF badge) is send over the existing RF cable. 1 2 34 5 67 8 9 C 0 E AB350 Accessor III /
SimpleXS AC3/2TR Nedap N.V. Nedap Readers Installation Guide Page 5 of 21 Mifare cards must be converted to XS code, max label number 220.000 depending of amount or RAM memory in XS reader. Attention: At the XS readers only one customer code for each type can be used!
LEDs controlled by separate connections between Convexs/Invexs and AX1014/AB350 (use existing cabling). Beeper controlled by hardware or configuration. Power at Convexs/Invexs is retrieved from RF line (no additional power cables needed, existing cabling is used). Convexs/Invexs readers cannot be connected parallel to a RF reader. (Despite using antennas, where in some situations it was possible to connected the antennas parallel, e.g. for In/Out usage at a single door). Wiegand To be used for connection to third party systems, using different Wiegand protocols. The card data can be transferred using different Wiegand protocols. LEDs are controlled by the two separate connections between Convexs/Invexs and the third party system. Beeper controlled by hardware or configuration. Power must be supplied additionally to the Convexs/Invexs. Serial RS485 (RS485 Ascii) To be used for connection to third party systems, using a serial connection. Requires special configuration in Convexs/Invexs:
NR9002.cfg LEDs can be controlled by the two separate connections between Convexs/Invexs and the third party system. Beeper controlled by hardware or configuration. Power must be supplied additionally to the Convexs/Invexs. USB Desktop reader Inside the USB Desktop reader the Convexs is used, with special configuration NR9004.cfg in Convexs:
Check the installation manual of the USB Desktop reader for more details Power can be supplied by USB (check power requirements). 1 2 34 5 67 8 9 C 0 E 1 2 34 5 67 8 9 C 0 E
- Third party systems
- AEOS Wiegand
- Third party systems
- Serial output
- USB output Remark: Depending of the used output the cable distances differ! (See for cabling details the corresponding installation sheets.) Nedap N.V. Nedap Readers Installation Guide Page 6 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 MN
: Mifare
: Mifare and Nedap MD MND : Mifare and Nedap and DESFire
: Mifare 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. Nedap N.V. Nedap Readers Installation Guide Page 7 of 21 3. Convexs/Invexs Protocols Depending of how the Convexs/Invexs is configurated several output protocols are available. 3.1. RS485NR (including RS485NR2) C 0 E 1 2 34 5 67 8 9 for handling the possibility to have bi-directional encrypted
(APx003rs485NR/APx003rs485NR2) RS485 enables communication. If possible use this protocol. The RS485 is used for connecting the Convexs/Invexs to the Nedap AEOS AEpacks APx003 These AEpacks must have the correct firmware the Convexs/Invexs. The APx003rs485NR2 is the successor of the APx003rs485NR, having more features and less limitations (see chapter 10, Available reader firmware) Using RS485 enables the option that the Nedap reader configuration file and firmware can be downloaded using AEmon. The Convexs/Invexs configuration file still is generated by AEreco. With RS485 the data from the cards read at the Convexs/Invexs is transmitted transparently (Direct transmission mode) and encrypted to the AEpack. If both Nedap and Mifare cards must be read use at the Access Point the Primarily- and Secondarily Identifier type can be defined. (Check is your AEOS version is capable of handling this.) Cabling distance: Max 1000 meters LED control:
Beeper control:
PIN code:
At AEreco the output format must be configured as: RS485NR. 3.2. LEDs are controlled over the RS485 communication line (by software) By hardware connection or software (configuration depending) For corresponding Invexs readers PIN code can be used over RS485 communication. RF output Using Convexs converters (AX1014 / AB350) enables re-use of existing cabling (both for antenna and LEDs) The RF output is to be used if the Convexs/Invexs have to be connected to the former Nedap XS readers
(Accessor/SimpleXS) or the Nedap AEpacks. Depending of the possibilities and firmware of the used Nedap readers following options are available:
Cabling distance: Max 50 meters LED control:
Beeper control:
PIN code:
For RF output following options are available LEDs are controlled by existing cabling (hardware connection) By hardware connection or software (configuration depending) Not possible Nedap RF data All data read is transparently sent the the AEpack (Direct transmission mode) Most preferable, but can not be used in combination with a WinXS system Nedap RF badge Mifare badges: data read is converted towards another customer code Use this only in case the Convexs/Invexs is used towards a WinXS system. XS badges:
sent directly or converted towards another customer code. RF output to AX1014 on AEpacks 3.2.1. Can be used if e.g. the existing Nedap RF antenna connected to an AEpack is replaced with the Convexs/Invexs, thus enabling that both Nedap and Mifare cards or Mifare cards replacing Nedap cards can be read. For each AEpack (or AEpack reader channel) one AX1014 (Convexs adapter) must be placed on the AEpack, on which the Convexs/Invexs is connected. If e.g. a AP4001 with 4 Nedap antennas is converted to Convexs/Invexs readers 4 AX1014 are needed. Depending on the type of firmware in the AEpack following options are possible:
1 2 34 5 67 8 9 C 0 E With new updated firmware at the AEpacks:
AX1014 AX1014 AX1014 AX1014 AX1014 Nedap N.V. Nedap Readers Installation Guide Page 8 of 21 The data from the cards read at the Convexs/Invexs is transparently sent (Direct transmission mode) to the AEpack. If both Nedap and Mifare cards must be read, use at the Access Point the Primarly and Secondarly Identifier type (check your AEOS version if this is available). At AEreco the output format must be configured as: Nedap RF data. Not advisable, but with older firmware at the AEpack the Mifare cards must be converted to XS code, The maximum label number 999.999 (in combination with a GF code). At the Access Point in AEOS the XS Identifier is choosen. So now both Mifare (GF) and the Nedap XS cards can be identified. XS cards will be transparently transmitted. The chosen XS code may not be used already with existing XS cards. At AEreco the output format must be configured as: Nedap RF badge. Remark: This option can at special request only be programmed at Nedap, so not with the standard AEreco programm. Accessor III /
SimpleXS AC3/2TR C 0 E 1 2 34 5 67 8 9 AB350 AX1011 Accessor III /
SimpleXS AC3/2TR RF output to Nedap XS readers for AEOS integration 3.2.2. Same as 3.2.1, but now for Nedap XS readers (AB350 on Accessor, SimpleXS). Connected using the MD300 to an AX1001 on the AP1003 for integration with AEOS. This option can be used if e.g. the existing Nedap RF antenna on the XS reader is replaced with the Convexs/Invexs, thus enabling that both Nedap and Mifare cards or Mifare cards replacing Nedap cards can be read. For each XS reader one AB350 (Convexs adapter) must be placed on the XS reader antenna connector, on which the Convexs/Invexs is connected. Possibilities and settings are identical as at 3.2.1. Preferable is to use the Nedap RF data output. 3.2.3. Same as 3.2.1, but now for Nedap XS readers (AB350 on Accessor, SimpleXS), to be connected to the WinXS system (using e.g. LanBoXS or InterVisor, or directly to the WinXS PC) . This option can be used if e.g. the existing Nedap RF antenna on the XS reader is replaced with the Convexs/Invexs, thus enabling that both Nedap and Mifare cards or Mifare cards replacing Nedap cards can be read. For each XS reader one AB350 (Convexs adapter) must be placed on the XS reader antenna connector, on which the Convexs/Invexs is connected. The Mifare cards must be converted to an XS code:
RF output to Nedap XS readers at a WinXS system AB350 1 2 3 4 5 6 7 8 9 C 0 E The maximum label number is 220.000 (in combination with a GF code) and depending on the amount of memory in the XS reader. If beside the Mifare still the Nedap XS cards are used, the Eprom at the XS readers must be capable of reading both factory codes. The chosen XS code may not be used already with existing XS cards. At AEreco the output format must be configured as: Nedap RF badge. Remark: This option can only be programmed at Nedap, so not with the standard AEreco programm. 3.3. Wiegand 1 2 34 5 67 8 9 C 0 E By hardware connection or software (configuration depending) 8 bits message 4 bits PIN + 4 bits complement, (Dorado format) Maximum cable distance is 150 meters, the LEDs on Convexs/Invexs are controlled by hardware signals on the Convexs/Invexs connector. Beeper control:
PIN code:
For the possible Wiegand protocols, see the section below. Depending of the data read (Card type and Customer code) a different Wiegand code can be transmitted. Also if the selected Wiegand protocol is capable of using facility codes for each code read a different Wiegand facility code can be transmitted Attention: The card number and customer code that is read must fit in the chosen Wiegand protocol.
- Third party systems
- AEOS Wiegand If no *bin Wiegand is used, the data format must be specified (AEreco in the Block decoder part). Nedap N.V. Nedap Readers Installation Guide Page 9 of 21 The Wiegand output can be used to connect to Third party systems or to the AEOS APx003 readers with the appropriate Wiegand protocol. At AEreco the output format must be configured as: Wiegand and the correct type of Wiegand protocol. 3.3.1. Wiegand formats Several Wiegand formats can be used:
- Wiegand 26
- Wiegand 32
- Wiegand 32bin
- Wiegand 37
- Wiegand 64bin
- Wiegand 128bin Tpw WDat0 WDat1 Wiegand data is been sent at D0 and D1, signals are active low. 3.3.2. Wiegand timing Timing:
3.3.3. Wiegand 26 Format: Facility code:
Label number:
3.3.3.1. Wiegand 26 data definition Pulse Interval Time : 60 usec Pulse Width Time range: 0..255 range: 1..65535 Tpw Tpi 8 bits:
16 bits:
2 bits
: 60usec Parity:
Tpi Tpi
+5V GND
+5V GND The Wiegand 26-bit format consists of a parity bit, followed by eight facility code bits, followed by 16 label number code bits and a final parity bit. The first parity bit shall create even parity when combined with the next twelve bits. The last parity bit shall create odd parity when combined with the remaining 12 bits. The data is represented in bits. (unsigned binary coded) The complete message consists of the following:
: 1 23456789 0123456789012345 6
: P FFFFFFFF NNNNNNNNNNNNNNNN P Bit position Bit contents Parity (even) : P FFFFFFFF NN
(odd) :
NNNNNNNNNNNNNN P Legend
: Facility code (8 bits: range: 0..255)
: F N : Label number (16 bits: range: 1..65535)
: Even parity over the first 12 bits Odd parity over the next 12 bits P Nedap N.V. Nedap Readers Installation Guide Page 10 of 21 3.3.4. Wiegand 32 Format: Facility code:
Label number:
3.3.4.1. Wiegand 32 data definition 16 bits:
16 bits:
range: 0..65535 range: 1..65535 The Wiegand 32-bit format consists 16 facility code bits, followed by 16 label number code bits. There are no parity bits. The data is sent in bits. (unsigned binary coded) The complete message consists of the following:
Bit position Bit contents
: 1234567890123456 7890123456789012
: FFFFFFFFFFFFFFFF NNNNNNNNNNNNNNNN
: Facility code (16 bits: range: 0-65535)
: F N : Label number (16 bits: range: 1..65535) Legend 3.3.5. Wiegand 32bin Format: Label number:
Data is represented in hex, first bit first. 3.3.6. Wiegand 37 Format: Label number:
3.3.6.1. Wiegand 37 data definition 35 bits:
32 bits:
range: 1..FF FF FF FF range: 1..34359738368 The Wiegand 37-bit format consists of one number, no facility code. There are 2 parity bits. The data is sent in bits. (unsigned binary coded) The complete message consists of the following:
: 1 23456789 0123456789 0123456789 0123456 7
: P NNNNNNNN NNNNNNNNNN NNNNNNNNNN NNNNNNN P Bit position Bit contents Parity (even) : P 12345678 9012345678
(odd) : 1 2345678901 2345678 P Legend
: N : Label number (35 bits)
: Even parity over the first 18 bits P Odd parity over the next 18 bits (starts from bit 18) 64 bits:
3.3.7. Wiegand 64bin Format: Label number:
Data is represented in hex, first bit first. 3.3.8. Wiegand 128bin Format: Label number:
Data is represented in hex, first bit first. range: 1.. FF FF FF FF FF FF FF FF 128 bits: range: 1.. FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Nedap N.V. Nedap Readers Installation Guide Page 11 of 21 3.4. Serial RS485 (RS485 Ascii) 1 2 3 4 5 6 7 8 9 C 0 E Maximum cable distance is 1000 meters, the LEDs on Convexs/Invexs are controlled by hardware signals on the Convexs/Invexs connector. Beeper control: By hardware connection or software (configuration depending) Requires configuration NR9002.cfg or NR9003.cfg. This configuration can be changed using AEreco. 3.4.1. Default settings
- Third party systems
- Serial output Nedap cards: Card number Mifare cards: CSN number No customer code is sent (default), no check on customer code
(CSN reversed: NR9003.cfg)
(Only Mifare, no DESFire at default file) Data format X 12AB56789 For other settings the NR9002.cfg or NR9003.cfg file must be changed by using AEreco. 3.4.2. Format: 9600 Baud, No parity, 8 bits, 1 stop bit Data: X 12AB56789 <CR> <LF>
Remark: If Mifare block data is used, the block decoder must be used to interpret the data. Using AEreco (from version 2.00) user specific header/trailer can be detemined. (Check AEreco user manual) 3.5. Identifier type : N Nedap M Mifare D Mifare DESfire U Mifare ultralight Identifier data (depending of type of identifier and configuration file !)
<CR> OD hex
<LF> OA hex USB Desktop reader Uses USB to communicate to other systems. Inside the USB Desktop reader a Convexs reader is used with special configuration NR9004.cfg or NR9005.cfg Two colour LED on the USB Desktop reader cannot be changed Configuration NR9004.cfg or NR9005.cfg can be changed using AEreco. 3.5.1. Default settings
- USB output Nedap cards: Card number Mifare cards: CSN number No customer code is sent (default), no check on customer code
(CSN reversed: NR9005.cfg) Data format For other settings the NR9004.cfg file must be changed by using AEreco. 3.5.2. Format: USB 2.0 Data:
Remark: If Mifare block data is used, the block decoder must be used to interpret the data. 12AB56789 12AB56789 Identifier data (depending of type of identifier and configuration file !) Nedap N.V. Nedap Readers Installation Guide Page 12 of 21 4. Convexs/Invexs connections The Convexs/Invexs is not hot-swappable, so when making or changing connections be sure power is Off. General:
- Check corresponding documentation of used AEpacks, Convexs converters and third party systems.
- Use correct shielded cables, cable shield must be connected to Power GND of Convexs (A2) Invexs (2) and GND of external device (or metal case)
- Beeper can also optional be controlled by configuration settings (see chapter 5).
- Check for Invexs 190 cabling colours 4.1. 4.2. 4.3. Convexs Connections Convexs Power /
XSMOD Function Power in (10-30VDC) /
XS modulator (120kHz) POWER GND/shield Power Ground A (-) B (+) D0 D1 BEEP UL*
GND NA*
RS485 RS485 Wiegand Data 0 Wiegand Data 1 Beep input UL led input Led/Beep Common Ground NA led input A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 Invexs 170 Connections Invexs Power /
XSMOD Function Power in (10-30VDC) /
XS modulator (120kHz) POWER GND/Shield Power Ground 1 2 3 4 5 6 7 8 9 10 A (-) B (+) D0 D1 BEEP UL*
GND NA*
Invexs 190 Connections Colour Red Black Grey Violet Green White Yellow Pink Blue Brown Wire w1 Remark:
w2 w3 w4 w5 w6 w7 w8 w9 w10 w11 RS485 RS485 Wiegand Data 0 Wiegand Data 1 Beep input UL led input Led/Beep Common Ground NA led input Function Power in (10-30VDC) /
XS modulator (120kHz) Power Ground / RF Ground RS485 A (-) RS485 B (+) Wiegand Data 0 (D0) Wiegand Data 1 (D1) Beep input (BEEP) UL led input (UL*) MD led input (MD*) NA led input (NA*) Convexs Rear view Invexs without display 1 10 Invexs with display 1 5 1 10 6 1 Cable shield (wire 11) must be connected to the metal case of the external device R Shield / Metal EM shield (connected to power ground) UL*,NA*, MD* and BEEP are Open Collector to GND. If Convexs adapters (AX1014 or AB350) are used, the original UL and NA signals of the reader are converted to be used with UL* and NA* of the Convexs/Invexs. Invexs 190 to AX1014 or AB350 needs additional connection between GND (for UL and NA) and Antenna GND on the AX1014 / AB350 (Invexs 190 has no separate cable for this connection) GND UL*/NA* / BEEP Nedap N.V. Nedap Readers Installation Guide Page 13 of 21 1 2 34 5 67 8 9 C 0 E 4.4. Connections using RS485 A1 AP4x03x Power / XSMOD POWER GND/shield AP6003 Lower 1 3) Convexs / Invexs 1 Convexs/Invexs connected to Nedap AEpacks using RS485: For those AEpacks not having RS485 on board use the additional AX1012 (RS485 to RS232 converter) Remarks:
8 A8 A9 9 A10 10 A2 A3 A4 A5 A6 A7 14 8 10
UL*
GND NA*
2 3 4 5 6 7 A (-) B (+) 14 8 10 1 3) D0 D1
16 4) BEEP Lower Upper Upper AP1003 1) Upper 1 3) AP1003+AX1012 2) 1 3) Upper Lower AX1012 AX1012 1 Rx+
Rx-
1 13 16 1 On AP1003 the RS485 is available on Upper Row connector points 13 - 16, only from PMS D or higher 2 For AP1003 with PMS below D use the additional AX1012 to convert RS232 from AP1003 to RS485 for Convexs 3 Power for Convexs can be supplied by
- External Power Supply
- AEpack, check correct voltage and current at given AEpack output 4 Beeper on Convexs can be optional controlled
- on AP6003 this can be done by pin 16
- on other AEpacks use Relais output 5 LED control is supplied over the RS485 communication, so no additional wiring is needed 6 Cable shield must be connected to Power GND of Convexs (A2) and GND of external device or metal 7 case of the external device (at housing of AP6003, AP4x03x, AEbox) If Convexs replaces e.g. DC130 antenna the existing cabling of the DC130 antenna (4 x 0,25qmm) can be reused for RS485 and Power only if cable length not exeeds 50 meters and cable shield is correct connected. 8 PIN code for the Invexs reader is transmitted using the RS485 communication. 4.5. Connections using RF output Remarks:
A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 Power / XSMOD POWER GND/shield A (-) B (+) Convexs / Invexs 1 2 3 4 5 6 7 8 9 10 D0 D1 BEEP UL*
GND 8 NA*
AX1014 AB350 11 ANT 12 GND ANT GND
relay 13 UL*
14 GND 15 NA*
relay--
UL*
GND NA*
1 2 34 5 67 8 9 C 0 E 1 2 34 5 67 8 9 C 0 E AX1014 AX1014 AX1014 AX1014 AX1014 Accessor III /
SimpleXS AC3/2TR AB350 1 For Nedap reader AEpacks the AX1014 must be applied to each AEpack 2 For the Accessor III / SimpleXS / AC3/2TR the AB350 must be applied 3 Existing cabling can be re-used when the Nedap antenna is replaced by the Convexs 4 Power is supplied to the Convexs by the RF signals on A1 and A2, no additional Power Supply is needed. 5 Beeper can be controlled optional by making the correct configuration settings or hardware connection. 6 Cable shield must be connected to Power GND of Convexs (A2) and GND of external device or metal case of the external device (at housing of Accessor, AP4x01, AEbox) 7 PIN code for Invexs readers is NOT possible 8 Invexs 190 to AX1014 or AB350 needs additional connection between GND (for UL and NA) and Antenna GND on the AX1014 / AB350 (Invexs 190 has no separate cable for this connection) Nedap N.V. Nedap Readers Installation Guide Page 14 of 21 1 2 34 5 67 8 9 C 0
- Third party systems
- AEOS Wiegand Remarks:
1 Beeper and LED control is depending of the third party system and optional from the used configuration. 2 Cable shield must be connected to Power GND of Convexs (A2) and GND of external device or metal case of the external device. 3 PIN code is possible over Wiegand 4.6. Wiegand 8 A8 w8 UL*
BEEP D0 D1 Power +
A9 A10 Power GND A (-) B (+) Data 0 Data 1 1 2 3 4 5 6 7 Power / XSMOD POWER GND/shield Convexs / Invexs Third party system 9 10 w10 A1 A2 A3 A4 A5 A6 A7 w1 w2 w3 w4 w5 w6 w7 If the Convexs is connected to a Third party system using Wiegand the Power must be supplied external or from the Third party system.
? 1)
? 1)
? 1)
? 1)
? 1) GND NA*
Cable shield Metal case MD*
w11 w9 Nedap N.V. Nedap Readers Installation Guide Page 15 of 21 5. Convexs/Invexs LED and Beeper control The Convexs/Invexs has three LEDs (red, green and blue) and a buzzer to give additional information to the user. At the backside of the Convexs/Invexs, a status LED (blue) and ID led (green) are available. 5.1. User LEDs UL LED (green), controlled by a hardware signal to connector A8 Or if rs485NR protocol is used, UL LED is controlled over the RS485 communication line. NA LED (red), controlled by a hardware signal to connector A10 Or if rs485NR protocol is used, NA LED is controlled over the RS485 communication line. Status LED (blue):
The blue LED is used as status indication to the user. Up from certain AEOS and firmware versions the blue LED can also be controlled over the RS485NR protocol. Otherwise it must be activated at the Configuration (AEreco). If activated the blue LED will be active if both other LEDs or OFF. So if both UL and NA are OFF )NA LED must be OFF 1 sec) , the blue LED automatically will be ON. 5.2. Beeper The Beeper can be controlled by:
Hardware signal to connector A7 Or if rs485NR2 protocol is used, Beeper is controlled over the RS485 communication line. Software if card is detected (at AEreco: NA/UL beep):
o o If UL LED is activated (valid card) beeper is shortly activated IF NA LED is activated (invalid card) beeper is 3 times shortly activated The volume of the beeper can also be controlled by AEreco (valid for both hardware and software setting). The beeper is also used for indicating the status of loading the configuration at the Convexs/Invexs. 5.3. Status LEDs The blue LED at the front side is used to indicate if a configuration is loaded at the Convexs/Invexs. The blue status LED at the backside is used to indicate the status of the Convexs/Invexs reader, the green ID LED to indicate the detection of a card. See Installation sheet for detailed information. 6. Invexs PIN modes On the Invexs different modes for using the PIN code are available. These are depending off the used communication protocol. 6.1. RS485NR The activation of the PIN is controlled over the RS485NR communication, by the used AEbcs. The AEbcs determine if the PIN code is activated or not (and if also the PIN code LEDs are activated then). 6.2. Wiegand The PIN code (if the LEDs behind the ciphers are activated) acts different, depending on the version of the Invexs firmware:
Invexs versions before 2.06 If card is detected by the Invexs, the PIN code LEDs are turned on. At Wiegand the PIN code LEDs are turned off by: change at NA or UL LED, or after time-out Invexs versions after 2.06 Up from 2.06 it is possible to make a setting on AEreco (version > 2.1.0) to set the PIN code always on. Default setting as with version before 2.06, if via AEreco the new option is activated, the PIN code is always on (independent of a badge detection) This option requires also modified firmware at the used AEpack (check AEpack version file for this). Nedap N.V. Nedap Readers Installation Guide Page 16 of 21 7. Configuring the Convexs/Invexs Functionality and output protocol of the Convexs/Invexs reader is determined by the configuration that is loaded in the reader. This configuration is defined using the program AEreco, and deployed by the configuration card or via AEmon (the specific configuration file is uploaded to the Convexs/Invexs, identical as AEpack firmware). With AEreco a Configuration file or Configuration card can be generated. These contain all settings for the Convexs/Invexs:
Configuration file:
The configuration card contains the configuration for a Convexs/Invexs and can be handled as follows:
o With AEmon this file can be loaded into the (or all) Convexs/Invexs o Can be used to generate a configuration card o With AEreco this file can be loaded directly into the connected Convexs/Invexs Configuration card By presenting this card to a Convexs/Invexs the configuration in this card is transferred to the Convexs/Invexs. DEScount card For situations where existing Convexs/Invexs MN or Convexs/Invexs M must be made suitable to read DESFire cards this special DEScount card is used. On this card the amount of Convexs/Invexs readers that must be made suitable to read DESFire is programmed. For each converted Convexs/Invexs to DESFire the amount on the DEScount card is decreased. DESFire available / enabled:
If DESFire is enabled (and this reader is suitable using DESFire) can be checked with AEmon at the View Hardware: (only with the rs485NR protocols):
Select the Nedap reader and check with options are available (OptionsAvailable) and which are enabled
(OptionsEnabled):
A configuration of a Convexs/Invexs can not be read back from the Convexs/Invexs, so when making changes to a configuration you always need to use AEreco with the (original) configuration settings for this specific customer. After loading the configuration the beeper is used to indicate if the loaded configuration is correct or not:
High sound:
Configuration is loaded, a second High sound indicates that this configuration can Low sound:
Configuration is not loaded, error has occurred. be used at this reader. 7.1. Nedap reader Configuration file The Configuration file can be uploading to the Nedap reader by:
Using AEmon, the Convexs/Invexs is connected to the AEOS reader AEpack (APx003rs485NR, the Convexs/Invexs must have the RS485NR output protocol) At AEmon in the Hardware view the connected Convexs/Invexs reader(s) are available. Selecting now these Convexs/Invexs reader(s) gives the opertunity to load a new configuration file. Using AEmon all connected Convexs/Invexs readers can easily be updated to a new configuration file. At the Hardware view the correct Configuration file can be checked (beside other important settings of the Nedap reader, e.g. Options, Firmware, Kernel versions, etc) Connect the Convexs/Invexs directly to AEreco and load the configuration file direct to this Convexs/Invexs Nedap N.V. Nedap Readers Installation Guide Page 17 of 21 Remark: If the Configuration file is uploaded as above to the Convexs/Invexs, no checks are made if this configuration file is suitable for this Convexs/Invexs. This is in contradiction with the use of the Configuration card (then only specific cards with specific keys can be used to program these Convexs/Invexs). 7.2. Configuration card The configuration made with AEreco can be stored on a configuration card. By presenting this configuration card to a new Convexs/Invexs (default, factory settings) the settings on the configuration card are programmed into the Convexs/Invexs reader. Up from now only these specific unique configuration cards can be used to program the configuration in the corresponding Convexs/Invexs readers. During the configuration process the beeper will sound, to indicate the configuration is loading (and the card should not be taken away from the Convexs/Invexs). This process takes about 5 seconds. The uniqueness of the combination of Configuration card and Convexs/Invexs is made with the Reader read key that is determined at AEreco (General Configuration card). This Reader read key is also stored in the Convexs/Invexs and every following time a Configuration card is offered, this Reader read key is compared against this key of the Configuration card. This principle results that only Configuration cards with the same Reader read key can change the configuration of a Convexs/Invexs. This key is independent of the Mifare keys. 8. Updating firmware of the Convexs/Invexs If new firmware must be loading into the Convexs/Invexs reader this can be done by:
Using AEmon, the Convexs/Invexs is connected to the AEOS reader AEpack (APx003rs485NR or APx003rs485NR2, the Convexs/Invexs must have the RS485NR output protocol). At AEmon in the Hardware view the connected Convexs/Invexs reader(s) are available. Selecting now these Convexs/Invexs reader(s) gives the opertunity to load a new firmware Using AEmon all connected Convexs/Invexs readers can easily be updated with new firmware. Connect the Convexs/Invexs directly to AEreco (RS485) and load the new firmware direct to this Convexs. Remark: After updating the firmware the configuration must be reloaded. Updating the firmware will automatically remove the configuration. 9. Default settings of the Convexs/Invexs Default settings (factory settings, NR9000.cfg) of the Convexs/Invexs are:
(CSN reversed: NR9001.cfg) Output Type RS485NR Nedap RF badge RS485NR Nedap RF data Input Type Nedap XS Nedap XS Mifare CSN Mifare CSN Mifare reader enabled, Mode: CSN Conversion table Beeper: No NA / UL beep Led Mode: Red / Green Preferred Card Type: Nedap XS Card Configuration card enable Reader read key: FC9011EE5339 With this default configuration (file NR9000.cfg and NR9001.cfg) the Convexs/Invexs acting for XS cards as a normal antenna, and can be connected to AEpacks (on RS485NR) or Nedap reader AEpacks (with AX1014) or XS readers (with AB350). Nedap N.V. Nedap Readers Installation Guide Page 18 of 21 10. Available reader firmware Pay attention that not for all output protocols suitable firmware is available at the applied readers. The Nedap RF badge can always be used on Nedap readers. Wiegand formats can always be used on APx003 series with corresponding firmware. For the Nedap RF data and RS485NR not for all readers the suitable firmware is available. Please check always for the correct firmware version. Nedap RF data RS485NR Remarks AP1001 AP1002 AP1009 AP4001 AP4001X AP1003 AP4003 AP4003X AP6003 AP1001_548v210 AP1002_548v211 AP1009_548v211 AP4001_543v204 AP4001_543v305 X X X X X X X X X AP1003rs485NR2_543v200 AP1003rs485NR_543v200 AP4003rs485NR2_543v210 AP4003rs485NR2_543v210 AP4003rs485NR_543v31x AP6003rs485NR2_2368v100 AP6003rs485NR_2368v100 See below remark AP4x03 Accessor III on AEOS SimpleXS on AEOS AC3/2TR on AEOS A3PNU_AEOS_v2.01 A0PNU_AEOS_v2.01 H7A3U_AEOS_v2.02 X X X Remarks:
X in above table means NOT possible. Two RS485 protocols are available:
o o rs485NR2 (up from 8-2009) able to show the Convexs/Invexs as an AEpack in AEmon, offering full implementation for AP4x03 and AP4x03X (PIN, tamper switch) and additional features such as Beeper control over RS485. Can be used for all most corresponding AEpacks (including AP4x03). Highly preferable to use always this protocol!
rs485NR: Convexs/Invexs is not visible in AEmon, only AEpack to it is connected is shown. First implementation of rs485NR protocol. Not available for AP4x03. The AP4x03 (RS485NR) is only available for the X version up from version v3.1x, and must have at least Kernel version 3.10. Tamper switch and PIN not available at the AP4x03X, only at the AP1003 with RS485. AP4003X (rs485NR) / AP4003 (rs485NR2) connected to o AP8001X: needs AP8001X_543v302 or higher o AP8001: needs AP8001_543v102 or higher (and kernel for AP8001 version 1.04 or higher) o AP4801X, AP4803X, AP4807X: needs kernel 3.11 or higher o AP4801, AP4803, AP4807:
needs kernel 2.11 or higher For XS readers connected to WinXS Nedap RF data is not possible (use always RF badge). When using RS485 check if the applied AEpack is equipped with RS485 interface. Otherwise the AX1012 (RS232 to RS485 converter) must be placed at the AEpack). 10.1. AEOS versions The Convexs/Invexs can be connected to AEOS for (almost) all versions; in-depending of the communication method between the AEpack and Convexs/Invexs (the AEpacks must have the correct firmware, see above). If the Convexs/Invexs is not supported by an older AEOS version, the data from the card will still be read by AEOS and normal handled, It is not possible to see these Convexs/Invexs in AEmon or to load (using AEmon) a new configuration in the Convexs/Invexs (in case RS485 is used):
Up from 2.2.0 Convexs/Invexs supported Up from 2.1.7 / 2.2.0: Primary and secondary identifier type at Access Points Nedap N.V. Nedap Readers Installation Guide Page 19 of 21 So if using the Convexs/Invexs with e.g. RS485 it can be connected to AEOS version before 2.2.0 or 2.1.7. If the configuration of the Convexs/Invexs differs from default this configuration must be loaded using a configuration card (using firmware APx003rs485NR) Remark: Check always the AEOS release notes for detailed information and the Know Problems in chapter 11. 11. Known problems 11.1. Convexs/Invexs to AP1002 In case the Convexs/Invexs reader is connected to an AP1002 (both Nedap RF data and Nedap RF badge) the potentiometer for the transmitter level must be set to minimum. Otherwise detection can be intermittend. 11.2. Convexs/Invexs to Nedap readers with AM badges In case the Convexs/Invexs reader is connected to Nedap readers (e.g. AP4001 or AP1001) with output Nedap RF badge the AM badges (A, B, C, D, G codes) will not be read on the Nedap reader. In this cases use as output the Nedap RF data. 11.3. Convexs/Invexs to AP4003 using RS485 Using rs485NR firmware: Connecting the Convexs/Invexs to the 4000 series using rs485NR can only to the AP4003X (and AP4803X), so not to AP4003 (or AP4803). The AP4x03X requires at least kernel 3.10 and corresponding firmware. For the AP4x03 (with kernel version 2) connecting the Convexs/Invexs with RS485 using the rs485NR firmware is NOT possible. This is solved with the rs485NR2 firmware. This firmware is suitable for both AP4x03 and APx03X (and AP1003, AP6003) Check always the version of firmware for the AEpu (see Remarks at chapter 10). 11.4. Convexs/Invexs to AP4003 using RS485 Tamperswith / PIN If rs485NR is used, the Tamperswitch and PIN at the Convexs/Invexs is only available at the AP1003 with RS485, not at the AP4000 series. Advisable is to use the rs485NR2 protocol, supporting these features on AP4003 series. 11.5. Convexs/Invexs to AP4x03X series before production code W2 using RS485 The first series of AP4803X and AP4003X (Production codes before W2) will put this AEpack out of order after uploading the Convexs/Invexs configurations and/or firmware to the Convexs/Invexs (or Nedap Readers), when using the RS485NR protocol. Solution for this is to replace this AEpacks. (These AEpacks can be used for other protocols without problems.) AP4x03X produced before June 2009 could sometimes have communication problems on the RS485 line. Due to this the Convexs/Invexs can malfunction. 11.6. Invexs with display / screen Invexs MNKS with display is only available on request, depending on the application to be used (what information must be shown on the screen). Nedap N.V. Nedap Readers Installation Guide Page 20 of 21 12. AEreco cards enquiry information For this part check the document AEreco cards enquiry Information (available on www.nedap.net). This document described the necessary data (regarding to Mifare cards) for making a configuration file with AEreco. 13. Document History Who REW REW REW REW REW REW REW REW REW REW REW REW REW REW REW REW Changes Invexs 190 to AB350/AX1014 needs additional GND, FCC changed Invexs 190, FCC certifications and UID 7 bytes added Invexs with screen / display only available on reques. Blue led always available (so not only with RS485 communication !), PIN code modes for Invexs added, Enquiry information removed to separate doc. Blue led only with RS485 communication available added MND added, check DESFire in AEmon added Known problems extended with Nedap readers instead of AP4001 (AM badge) rs485NR2 added (available also for AP4x03), LED/Beeper control changed Invexs added Known problem added about first AP4803X EV1 added in Enquiry part DES EV1 and Native settings Tamper switch not available on AP4000 added Configuration files naming changed to NRxxxx Serial output + USB reader added, DESfire enquiry changed Restrictions AP480x series added (in chapter 10) Conversion MN/M to DESFire added (DEScount). Using Convexs with older AEOS versions added Mifare DESFire added
9 8 7 6 5 5 4 4 3 Date 11-04-2011 17-01-2011 12-10-2010 18-05-2010 25-01-2010 23-11-2009 08-09-2009 16-07-2009 28-05-2009 12-03-2009 09-03-2009 26-11-2008 20-11-2008 28-10-2008 09-09-2008 15-08-2008 Nedap N.V. Nedap Readers Installation Guide Page 21 of 21
This product uses the FCC Data API but is not endorsed or certified by the FCC