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

 

© Nedap N.V.

 

   

 

 

 

 

 

 

 

Nedap Readers Installation Guide   

 

Page 19 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 

AP1001_548v210 

 

AP1002 

AP1002_548v211 

 

AP1009 

AP1009_548v211 

 

AP4001 

AP4001_543v204 

 

AP4001X 

AP4001_543v305 

 

AP1003 

AP1003rs485NR2_543v200 
AP1003rs485NR_543v200 

 

AP4003 

AP4003rs485NR2_543v210 

 

AP4003X 

AP4003rs485NR2_543v210 
AP4003rs485NR_543v31x 

See 

remark 

AP4x03 

below 

AP6003 

AP6003rs485NR2_2368v100 
AP6003rs485NR_2368v100 

 

Accessor III on AEOS 

A3PNU_AEOS_v2.01 

 

SimpleXS on AEOS 

A0PNU_AEOS_v2.01 

 

AC3/2TR on AEOS 

H7A3U_AEOS_v2.02 

 

 

Remarks

 

X in above table means 

NOT

 possible. 

 

Two RS485 protocols are available: 

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

!

 

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 (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 

 

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: