© Nedap N.V.
Nedap Readers Installation Guide
Page 12 of 21
3.4.
Serial RS485 (RS485 Ascii)
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)
Requires configuration
NR9002.cfg
or
NR9003.cfg
. This configuration can be changed using AEreco.
3.4.1.
Default settings
•
Nedap cards:
Card number
No customer code is sent (default), no check on customer code
•
Mifare cards:
CSN number
(CSN reversed:
NR9003.cfg
)
(Only Mifare, no DESFire at default file)
For other settings the
NR9002.cfg or NR9003.cfg
file must be changed by using AEreco.
3.4.2.
Data format
Format:
9600 Baud, No parity, 8 bits, 1 stop bit
Data:
X 12AB56789 <CR> <LF>
X
Identifier type :
N Nedap
M Mifare
D Mifare DESfire
U Mifare ultralight
12AB56789
Identifier data (depending of 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 header/trailer can be detemined. (Check
AEreco user manual
)
3.5.
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
•
Nedap cards:
Card number
No customer code is sent (default), no check on customer code
•
Mifare cards:
CSN number
(CSN reversed:
NR9005.cfg
)
For other settings the
NR9004.cfg
file must be changed by using AEreco.
3.5.2.
Data format
Format:
USB 2.0
Data:
12AB56789
12AB56789
Identifier data (depending of type of identifier and configuration file !)
Remark: If Mifare block data is used, the block decoder must be used to interpret the data.
- Third party systems
- Serial output
- USB output
1 2 3
4 5 6
7 8 9
C 0 E
