Netronix CTU-M Technical Data Sheet
Technical Data Sheet
RFID reader
CTU-M
CTU-Mxx-man-eng-v2.pdf
series
Fig. 1 CTU-M2R
ATTENTION! THIS CONFIDENTIAL DOCUMENT IS PROPERTY OF NETRONIX
SP. Z O.O.
DISTRIBUTION OF THIS DOCUMENT IN ANY WAY WITHOUT SPECIAL PERMISSION OF ITS
OWNER IS STRICTLY FORBIDDEN
1. INTRODUCTION ............................................................................................. 5
2. GENERAL SPECIFICATION........................................................................... 6
3. DIMENSION, TERMINAL DESCRIPTION....................................................... 7
4. MODULE SETTINGS BY ON-BOARD SWITCH............................................. 8
5. TRANSMISSION PROTOCOLS...................................................................... 8
5.1. RS-232/485 TRANSMISSION PROTOCOL ................................................ 8
5.2. Protocol for I2C transmission............................................................................. 8
5.2.1. Data exchange algorithm ............................................................................... 8
5.2.2. Timings............................................................................................................ 10
5.3. Protocol for 1WIRE (Dallas) bus...................................................................... 10
5.4. Wiegand protocol ................................................................................................ 12
5.5. Key management................................................................................................. 13
5.5.1. Key loading into dynamic key memory....................................................... 13
5.5.2. Key loading to key static memory ............................................................... 14
5.6. Commands for communication with transponder ..................................... 14
5.6.1. On/off switching of reader field.................................................................... 14
5.6.2. Selecting one of many transponders.......................................................... 15
5.6.3. Logging by means of Dynamic Key Buffer to selected sector of
transponder......................................................................................................................... 16
5.6.4. Logging by means of Static Key Buffer to selected sector of
transponder......................................................................................................................... 16
5.6.5. Reading-out the content of transponder block.......................................... 17
5.6.6. Writing the content of transponder block ................................................... 17
5.6.7. Copying the content of transponder block into other block..................... 18
5.6.8. Writing the page content into Mifare UL .................................................... 18
5.6.9. Reading the page content in Mifare UL ..................................................... 19
5.6.10. Writing values to transponder block ....................................................... 19
5.6.11. Reading-out the values from transponder block................................... 20
5.6.12. Increasing the value included in transponder block ............................. 20
5.6.13. Decreasing the value included in block transponder ........................... 21
5.6.14. Setting the transponder in field into sleep mode .................................. 21
5.7. Reader inputs and outputs ............................................................................... 22
5.7.1. Writing the output state................................................................................. 22
5.7.2. Reading the input state................................................................................. 22
5.7.3. Writing the settings to any port.................................................................... 23
5.7.4. Reading-out the configuration of freely selected port .............................. 25
5.8. Access password ................................................................................................ 25
5.8.1. Logging to reader........................................................................................... 25
5.8.2. Changing the password................................................................................ 26
5.8.3. Logging out of the reader ............................................................................. 26
5.9. Operating the transponder internal memory ............................................... 27
5.9.1. Reading-out the transponder number from memory................................ 27
5.9.2. Writing the transponder name to memory ................................................. 27
5.10. Operating the built-in access control ........................................................ 27
5.10.1. Writing the configuration of access control............................................ 27
5.10.2. Reading-out the configuration of access control .................................. 28
5.10.3. Writing the “automatic read” configuration............................................. 28
5.10.4. Reading-out the configuration of automatic device.............................. 30
5.10.5. Setting the date and time ......................................................................... 30
5.10.6. Reading-out the date and time ................................................................ 30
5.11. Configuring the UART serial interface....................................................... 31
5.11.1. Writing the configuration of serial port.................................................... 31
5.11.2. Reading the configuration of serial interface......................................... 31
5.12. Managing the events ...................................................................................... 32
5.12.1. Setting the event recorder........................................................................ 32
5.12.2. Reading the event recorder ..................................................................... 33
5.12.3. Reading the counters related to event memory. .................................. 33
5.12.4. Reading the events ................................................................................... 34
5.13. MAD – Mifare Application Directory ........................................................... 35
5.13.1. Card MAD formatting ................................................................................ 35
5.13.2. Adding the application to MAD directory................................................ 35
5.13.3. Pursuing the sector for given application............................................... 36
5.13.4. Pursuing the next sector of application .................................................. 36
5.14. Other commands ............................................................................................. 37
5.14.1. Remote reset of reader............................................................................. 37
5.14.2. Reading-out the reader software............................................................. 37
5.14.3. Change buzzer volume............................................................................. 37
5.15. Code meanings in response frames .......................................................... 38
6. MEANING OF SYMBOLS USED IN THE SPECIFICATION ......................... 38
7. MECHANISM OF MASTER ID ...................................................................... 38
8. RESET TO DEFAULT SETTINGS ................................................................ 39
9. OPERATION EXAMPLE OF TRANSPONDER............................................. 39
CTU
-
Mxx
NETRONIX CTU-Mxx
5
1. Introduction
CTU-M device series is OEM miniature RFID card reader operating at frequency of
13,56 MHz
Main features:
• Support of Mifare S50, S70, Ultralight, Desfire
• built-in antenna
• card memory with build-in lock driver,
• lots of communication interfaces type, depend on version (see table below)
• Built-in relay and buzzer
• Built-in push-button for reset to default settings
• 2 configurable inputs/outputs
• Two-state outputs control
• Read-out of two-state input
• changeable format of sending ID
• MAD functionality
• Data password protected
• Software update via serial interface using NEFIR program
CTU-M reader series
Module type
GPIO
Card memory
Event memory
Relay
Power supply
RS-232
CTU-M2R*
CTU-M4R
CTU-M5N*
CTU-M5R
CTU-M2RM
40
40
40
40
1000 4000
7-16
7-16
5
5
7-16
* - standard version, rest of version for special order
INTERFACES
RS-485
RS-232TTL
SPI
I2C
WIEGAND
1WIRE
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
6
2. General specification
Supported functionality depending on transponder / card type:
Transponder
type
ID number
read-out
Full write and read-out of memory blocks
S50 YES YES
S70 YES YES
Ultralight YES YES
Desfire YES NO
CTU-Mxx module parameters
Supply voltage (M2R, M4R model) 7-16 V
Supply voltage (M5R model ) 4,5 - 5,5 V
Max. supply current 120 mA
Rated operation radio frequency of module 13,56MHz
Working temperature
-20°c - +65°c
Max. relay current 2A
Appr. read distance for S50 7 cm
Max. output current for GPIO 20mA
Transmission parameters for
RS232/RS485/RSTTL
2400, 4800, 9600, 19200, 38400, 57600,
115200 bps,
8 data bits, 1 stop bit, no parity
compliant with „Netronix Protocol”
Address on I2C bus 0xC0
1WIRE family code,address (configurable) 0x01,0x01
WIEGAND number of bits 37
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
7
67 mm
3. Dimension, terminal description
4xφ3
67 mm
79.5mm
2 14
1 13
79.5 mm
Rys.2 top side view
Pin no. Description
1
RS232RX, RS485B, RSTTL_RX, 1WIRE, MOSI,
SDA
2 RS232TX, RS485A, RSTTL_TX, MISO
3 SCK, SCL
4 CS
5 MCLR
6 GND
7 VCC
8 GPIO 1
9 GPIO 2
10 GND
11 NC
12 NC
13 RELAY 1
14 RELAY 2
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
8
4. Module settings by on-board switch
Two function of build-in switch:
• configure to factory settings – press button for 8 seconds
• change interface and RFID transponder type – press button in schematic:
STEP
1 MENU1 – interface
Number of press 1
2 3 4 5 6
- RS232/485 SPI WIEGAND 1WIRE I2C
selection*
2 Triple beep
* - type of interface depends on CTU-M model
5. Transmission protocols
5.1. RS-232/485 transmission protocol
In this data sheet RS-232/485 protocol has been confined to descriptions of
commands, responses and their parameters. Header and CRC control sum exist
always and are compliant with full “Netronix Protocol” document.
Command frame:
Header C_CommandName Response_parameters1…n CRC
Response frame:
Header C_CommandName+1 Response_parametrers…m OperationCode CRC
RS protocol operation can be tested by means of development tools including free of
charge “FRAMER” software”.
5.2. Protocol for I2C transmission
5.2.1. Data exchange algorithm
A module configured depending on table showed on point 4. operates in I2C
interface mode in following sequences:
1. Master (external device) writes command with parameters if necessary into slave
device (CTU module)
2 The command is performed (immediately after receiving byte sent quantity declared
in frame)
3. Master device reads response, its parameters and operation code. In case of
receiving busy byte 0xCB, repeat attempt to read the response after ca. 1 ms
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
9
(N bytes)
START
0b110000a0
STOP
TAK
NIE
(commands connected with write to/and read from transponders can last up to 100
ms).
We write inquiry-command to CTU module:
START
SLAVE ADDRESS (1B)
0
NUMBER OF BYTES(1B)
COMMAND (1B)
PARAMETERS (0...n B)
The „number of bytes” field must contain information on byte quantity sent directly
“command” fields and “parameters”.
We have then:
START
SLAVE ADDRESS (1B)
1
Number of bytes N or 0xCB
PARAMETERS + OPERATION CODE
STOP
I2C SEND
I2C SEND:
Number of bytes,command,[data]
I2C SEND:
Wait 1ms
I2C START
I2C SEND:
0b110000a1
Wait for ACK
I2C READ 1 byte:N
N= 0xCB ?
Receive N bytes
I2C SEND
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
10
5.2.2. Timings
Module sends and receives data at 400 kHz clock frequency considering
timings showed below.
Note 2: Reader keeps in low state first clock pulse of each byte sent until
proper state is placed on SDA line.
5.3. Protocol for 1WIRE (Dallas) bus.
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
11
Family code ID1…ID5 Address CRC
1 byte 5 bytes 1 byte 1 bytet
ID1...5 – unique ID number of transponder
CRC_DAL- check sum of data send
The format conforms 1-WIRE Dallas (e.g.. DS1990A). It means, that described
module could be used as a replacement of DS1990A drop.
During operation, a module tries to read-out transponder periodically. If it fails (no
successful read-out), module does not response for pulses sent from 1-WIRE master
unit. Bus does not "see" the module, which corresponds with lack of reader applying, it
means applying the DS1990A drop to drop reader. If module reads out the
transponder, the module starts to send data via 1-WIRE bus.
Calculate the CRC value
According to DS1990A specification C value is calculated from equation
x^8+x^5+x^4+1 with initial value equal to 0x00. The CRC is calculated on basis of all
frame bytes excluding the last one.
An example of CRC value calculation procedure written in C language
unsigned char CalcCRCDallas(unsigned char *SourceAdr)
{
unsigned char i,k,In,CRC=0;
for(i=0;i<7;i++)
{
In=*SourceAdr;
for(k=0;k<8;k++)
{
if((In^CRC)&1) CRC=((CRC^0x18)>>1)|0x80;
else CRC=CRC>>1;
In>>=1;
}
SourceAdr++;
}
return(CRC);
}
where *SourceAdr is beginning flag of data buffer
NETRONIX .
CTU
-
Mxx
NETRONIX CTU-Mxx
12
......
DATA1
DATA0
H level
5.4. Wiegand protocol
The format conforms WIEGAND protocol specification for N bits. During operation,
a module tries to read-out transponder periodically. If it fails (no successful read-out),
module does not send data (bus does not "see" the module). If module reads out the
transponder, the module starts to send data via Wiegand bus.
Pulse sequence from left to right.
L level
H level
L level
1 1 0 0 1 ............. 1 0 0 encoding DATA
......
Total number of pulses (level L) is equal to N. The first being bit sent complements up
to parity the bits from first half of total bits. The last bit N complements up to non-parity
the bits from second half of bits being sent.
It means, that two bits out of N bits assure the transmission correctness. Information is
being sent is written by means bits 2 to N-1, it gives N information bits.
Check sums for bit sequence:
for even N:
EXXXXXXXXXXXXYYYYYYYYYYYYO
or for odd N:
EXXXXXXXXXXXXXXXXXX..................
..................YYYYYYYYYYYYYYYYYYO
Where:
E = bit complementing up to parity
O = bit complementing up to non-parity
X = mask for parity calculation
Y = mask for non-parity calculation
NETRONIX .
Loading...