Nedap Convexs Series Скачать руководство пользователя страница 16

 

© Nedap N.V.

 

   

 

 

 

 

 

 

 

Nedap Readers Installation Guide   

 

Page 16 of 21 

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. 

 

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 LED’s 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

 

If UL LED is activated (valid card) beeper is shortly activated 

o

 

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 LED’s 

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 LED’s are activated then). 
 

6.2.

 

Wiegand 

The  PIN  code  (if  the  LED’s  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 LED’s are turned on. 
At Wiegand the PIN code LED’s 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). 

 

Содержание Convexs Series

Страница 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...

Страница 2: ...___________________________ 11 3 4 Serial RS485 RS485 Ascii _______________________________________________________ 12 3 4 1 Default settings __________________________________________________________...

Страница 3: ...Convexs Invexs _________________________________________________ 18 9 Default settings of the Convexs Invexs ___________________________________________________ 18 10 Available reader firmware ______...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Страница 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...

Отзывы: