Nedap Convexs Series Installation Manual And User'S Manual Download Page 18

 

© Nedap N.V.

 

   

 

 

 

 

 

 

 

Nedap Readers Installation Guide   

 

Page 18 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: 

 

Mifare reader enabled, Mode: CSN  

 

(CSN reversed: 

NR9001.cfg

 

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). 
 

Input Type 

Output Type 

Nedap XS 

RS485NR 

Nedap XS 

Nedap RF badge 

Mifare CSN 

RS485NR 

Mifare CSN 

Nedap RF data 

 

Summary of Contents for Convexs Series

Page 1: ...bility 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 t...

Page 2: ...___________________________ 11 3 4 Serial RS485 RS485 Ascii _______________________________________________________ 12 3 4 1 Default settings __________________________________________________________...

Page 3: ...Convexs Invexs _________________________________________________ 18 9 Default settings of the Convexs Invexs ___________________________________________________ 18 10 Available reader firmware ______...

Page 4: ...90 9895990 Mifare Nedap Convexs MND80xx 9896210 9896040 9896350 9896180 Mifare Nedap DESFire Gray Charcoal Flush Gray Flush Charcoal Gray Light Charcoal Dark For both Surface mounting and flush mounti...

Page 5: ...d by the communication over RS485 No separate cables for the LED s are used Beeper also can be controlled by hardware or configuration Power must be supplied additionally to the Convexs Invexs Not all...

Page 6: ...s 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 In...

Page 7: ...d 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 Direc...

Page 8: ...as RS485NR 3 2 RF output Using Convexs converters AX1014 AB350 enables re use of existing cabling both for antenna and LED s The RF output is to be used if the Convexs Invexs have to be connected to t...

Page 9: ...or 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 ante...

Page 10: ...55 Label number 16 bits range 1 65535 Parity 2 bits 3 3 3 1 Wiegand 26 data definition The Wiegand 26 bit format consists of a parity bit followed by eight facility code bits followed by 16 label numb...

Page 11: ...hex first bit first 3 3 6 Wiegand 37 Format Label number 35 bits range 1 34359738368 3 3 6 1 Wiegand 37 data definition The Wiegand 37 bit format consists of one number no facility code There are 2 p...

Page 12: ...type of identifier and configuration file CR OD hex LF OA hex 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 hea...

Page 13: ...GND for UL and NA and Antenna GND on the AX1014 AB350 Invexs 190 has no separate cable for this connection Convexs Function A1 Power XSMOD Power in 10 30VDC XS modulator 120kHz A2 POWER GND shield Pow...

Page 14: ...sing RF output Remarks 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...

Page 15: ...he third party system and optional from the used configuration 2Cable shield must be connected to Power GND of Convexs A2 and GND of external device or metal case of the external device 3PIN code is p...

Page 16: ...olume 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...

Page 17: ...able 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 optio...

Page 18: ...iguration 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...

Page 19: ...able to use always this protocol o 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 R...

Page 20: ...east 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 fi...

Page 21: ...iry information removed to separate doc 25 01 2010 5 REW Blue led only with RS485 communication available added 23 11 2009 5 REW MND added check DESFire in AEmon added 08 09 2009 4 REW Known problems...

Reviews: