® Nedap Readers Convexs & Invexs Installation Guide and User Manual 11 April 2011 1 4 7 2 5 8 3 6 9 C 0 E 1 4 7 2 5 8 3 6 9 C 0 E 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; specifications and availability of goods mentioned in it are subject to change without notice; it is not to be rep
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.
5. Convexs/Invexs LED and Beeper control _________________________________________________ 5.1. User LED’s ____________________________________________________________________ 5.2. Beeper ________________________________________________________________________ 5.3. Status LED’s ___________________________________________________________________ 16 16 16 16 6. Invexs PIN modes ___________________________________________________________________ 16 6.1.
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.
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 M190 9945512 Invexs MD190 9948406 Invexs MN190 9948392 Invexs MND190 9948414 1.5.
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! LED’s 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).
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.
3. Convexs/Invexs Protocols Depending of how the Convexs/Invexs is configurated several output protocols are available. 3.1. RS485NR (including RS485NR2) RS485 enables the possibility to have bi-directional encrypted 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 (APx003rs485NR/APx003rs485NR2) for handling the Convexs/Invexs.
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).
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 Wiegand data is been sent at D0 and D1, signals are active low. 3.3.2.
3.3.4. Format: Wiegand 32 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.
3.4. Serial RS485 (RS485 Ascii) 1 23 45 6 7 89 C0E Maximum cable distance is 1000 meters, the LED’s on Convexs/Invexs are controlled by hardware signals on the Convexs/Invexs connector. Beeper control: By hardware connection or software (configuration depending) - Third party systems - Serial output Requires configuration NR9002.cfg or NR9003.cfg. This configuration can be changed using AEreco. 3.4.1.
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.4.
4.6. Wiegand 1 23 45 6 7 89 C0 If the Convexs is connected to a Third party system using Wiegand the Power must be supplied external or from the Third party system. Convexs / Invexs A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 1 2 3 4 5 6 7 8 9 10 © Nedap N.V.
5. Convexs/Invexs LED and Beeper control The Convexs/Invexs has three LED’s (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 LED’s • 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.
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.
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.
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.
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.
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.
