handbuch id rw01l.ab-a - sebeto.com rw r… · the obid® id rw01l.ab-a .....5 1.3. technical data...

MANUAL

finalpublic (B)2006-01-12H20801-1e-ID-B.doc

DATEINAMEFORMATVERBINDEN

OBID®

ID RW01L.AB-AFirmware version AB100 and higher

OBID® Manual ID RW01L.AB-A

FEIG ELECTRONIC GmbH of 39 H20801-1e-ID-B.doc

Note

© Copyright 2003 - 2006 byFEIG ELECTRONIC GmbHLange Strasse 4D-35781 Weilburg-WaldhausenTel.: +49 6471 3109-0http://www.feig.de

Edition: MD/06/01/12 - h20801-1e-id-b.docWith the edition of this manual, all previous editions become void. Indications made in this manual may be changed withoutprevious notice.

Copying of this document, and giving it to others and the use or communication of the contents thereof are forbidden withoutexpress authority. Offenders are liable to the payment of damages. All rights are reserved in the event of the grant of a patentor the registration of a utility model or design.

Composition of the information in this manual has been done to the best of our knowledge. FEIG ELECTRONIC GmbH doesnot guarantee the correctness and completeness of the details given in this manual and may not be held liable for damagesensuing from incorrect or incomplete information. Since, despite all our efforts, errors may not be completely avoided, we arealways grateful for your useful tips.

The installation instructions given in this manual are based on advantageous boundary conditions. FEIG ELECTRONICGmbH does not give any guarantee promise for perfect function in cross environments.

FEIG ELECTRONIC GmbH assumes no responsibility for the use of any information contained in this manual and makes norepresentation that they free of patent infringement. FEIG ELECTRONIC GmbH does not convey any license under its patentrights nor the rights of others.

OBID® is a registered trademarks of FEIG ELECTRONIC GmbH.

hitagTM is a registered trademark of Philips Electronics N.V.

General information's regarding this manual

• The sign " " indicates extensions or changes of this manual compared with the former issue.

• If bits within one byte are filled with "-", these bit spaces are reserved for future extensions or for internaltesting- and manufacturing-functions. These bit spaces must not be changed, as this may cause faulty op-eration of the Reader.

• The following figure formats are used:0...9: for decimal figures0x00...0xFF: for hexadecimal figures,b0...1 for binary figures.

• The hexadecimal value in brackets "[ ]" marks a control byte (command).

http://www.feig.de/



Contents:

1. Introduction 5

1.1. Principles of operation of the OBID®-System...................................................................5

1.2. The OBID® ID RW01L.AB-A ................................................................................................5

1.3. Technical data .....................................................................................................................6

1.4. Dimensions..........................................................................................................................7

1.5. Pin configuration.................................................................................................................8

1.6. Toggling Polling- / Scan-Mode...........................................................................................8

1.7. Connecting an external antenna........................................................................................9

1.8. Declaration of Conformity ................................................................................................10

2. Data traffic between Reader and Host 11

2.1. Asynchronous interface, data formats and protocol frames........................................12

2.2. Polling mode......................................................................................................................14

2.3. Scan mode.........................................................................................................................15

2.3.1. Scan mode over the asynchronous interface ..............................................................16

2.3.2. Scan mode over the data/clock interface ....................................................................17

3. Polling mode (read and write transponder data) 20

3.1. [0x11] GET_SNR................................................................................................................20

3.2. [0x14] WRITE_DB (Write data block(s)) ..........................................................................21

3.3. [0x15] READ_DB (Read data block(s) .............................................................................22

3.4. [0x1A] Halt (ID DTx.B only)...............................................................................................23

4. Commands for reader control and configuration 24

4.1. [0x62] CONFIG_READ.......................................................................................................24

4.2. [0x82] CONFIG_WRITE .....................................................................................................24

4.3. [0x64] CONFIG_RESET.....................................................................................................25



4.4. [0x63] CPU_RESET ...........................................................................................................25

4.5. [0x65] GET_VERSION .......................................................................................................26

4.6. [0x69] RF_RESET..............................................................................................................27

4.7. [0x52] BAUDRATE_DETECTION......................................................................................28

5. Reader Configuration 29

5.1. CFG0: Reader Parameters................................................................................................29

5.1.1. COM_PARA ................................................................................................................30

5.1.2. READER_MODE.........................................................................................................31

5.1.3. SCAN_MODE..............................................................................................................32

5.1.4. DB_ADR......................................................................................................................34

5.1.5. D_LGT.........................................................................................................................34

5.1.6. D_START ....................................................................................................................35

5.1.7. SCAN_PREFIX............................................................................................................35

5.1.8. SCAN_TERM ..............................................................................................................35

5.1.9. TAG_DRV....................................................................................................................35

APPENDIX 36

APPENDIX A: Timing ................................................................................................................36

APPENDIX B: List of status bytes ...........................................................................................37

APPENDIX C: Memory model ID DTx.B...................................................................................38

APPENDIX C1: Philips Hitag 1...............................................................................................38

APPENDIX C2: Philips Hitag S ..............................................................................................39



1. Introduction

1.1. Principles of operation of the OBID®-System

The OBID® Identification System is an inductive transmission system for non-contact identification(ID) of objects. Use of the components in the read/write system makes it possible to read and writepassive transponders. This system consists of a reader, antenna and a transponder as storagemedium for the data.

When a transponder enters the local magnetic field of the antenna, it is supplied with energy and canbe written to or read. The received data are received by the same reader antenna which generates themagnetic field and sends the data to the transponder.

The magnetic field and the send and received transponder data can penetrate all non-conductingmaterials, so that even hidden reading and writing is possible.

1.2. The OBID® ID RW01L.AB-A

The OBID® ID RW01L.AB-A reader is designed for typical applications involving personnelidentification, access control, time tracking, billing systems, etc.

It features multi-tag capability. This means it can:

• read read-only data carriers (OBID® ID CTx.A)e.g. H4001, H4002, H4022, H4102, etc. from EM Microelectronics andUnique from SOKYMAT as well as

• read/write transponders (OBID® ID DTx.B)HITAG 1 and HITAG S from Philips Semiconductors.

The reader has a bi-directional, asynchronous interface (RS232-TTL) and a unidirectional data/clockinterface which can run in Wiegand or magnetic card reader emulation. The emulation modes of thedata/clock interface ensures easy conversion from traditional identification readers to the OBID® IDRW01L.AB-A.

The OBID® ID RW01L.AB-A can be easily software-configured for any application.

The OBID® ID RW01L.AB-A offers access to the entire physical memory range of the supportedtransponders (see: 3.2. [0x14] WRITE_DB (Write data block(s)) / 3.3. [0x15] READ_DB (Read datablock(s)



1.3. Technical data

Circuit board dimensions (W x H x D) 45mm x 40mm x 16mm +/- 1mmConnection 2 x 10-pin connector on the solder side

(pins: 0.7x0.7/ long incl. approx. 8mm insulatorTemperature range (operating and storage) -20°C to +70°CSupply voltage 5V DC± 5 %

Current consumption ca. 40 mAOperating frequency 125 kHzAntenna Integrated (mounted on circuit board)Supported transponders • read-only:

- ID CTx.A- H4001, H4002, H4022, H4102,- Unique- Q5, e5555 (plain manchester 64 Bitread-only mode)

• read/write- ID DTx.B- Hitag 1- Hitag S

Reading Range with ISO transponder card1• ca. 80 mm

Interfaces • RS232-TTL• Data / Clock

- Magnetic card emulation(to (ISO 7811 Track1 or Track2)

- Wiegand EmulationFunctions • Polling mode (over RS232-TTL)

Reading and writing transponder data• Scan mode (over RS232-TTL and Data / Clock)

Autonomous reading of transponder data

Applicable NormsEuropean RF Approval EN 300 330EMC EN 300 683

1 Depending on the antenna size and Q-factor of the antenna in the transponder



1.4. Dimensions

Fig. 1: Dimensions (mm)

1

4

40,0+0,5-0,5

2,5

8,0+0,5-0,5

45,0

+0,5

-0,5

2,54

110

8,0+0,5-0,5

B2 B1

32,4+0,1-0,1

33,0

+0,1

-0,1

X1

X2

6

1

X3



1.5. Pin configuration

Terminal Pin Name Function1 /CLS Data/clock interface: valid data2 ANT13 ANT2

External antenna

4 NC - Not connected -5 /RCP Data/clock interface: clock output6 /RDP Data/clock interface: data output7 TxD RS232-TTL TxD8 RxD RS232-TTL RxD9 NC - Not connected -

X1

10 NC - Not connected -1 /RST Reset input (active to GND ⇒ Reset)

2 NC. - Not connected -3 GND Ground (0 V)

X2

4 VCC Supply voltage (+5V)

1 MOD1Toggling Polling-Mode / Scan-ModeMOD1 = open ⇒ Polling-ModeMOD1 = closed (GND) ⇒ Scan-Mode

2 NC - Not connected -3 NC - Not connected -4 NC - Not connected -5 NC - Not connected -

X3

6 NC - Not connected -

1.6. Toggling Polling- / Scan-Mode

There are two ways to toggle between polling and scan mode.

• By soldering a 0 Ω resistor in B1 (see: 1.3. Technical data) scan mode is permanently activated.

• To temporarily activate scan mode, you can tie input MOD1 to potential GND (X2 / Pin 3).

The following table shows the possible configurations.

B1 MOD1Closed X

Scan-ModeOpen GND

Polling-Mode Open Open



1.7. Connecting an external antenna

In place of the antenna on the ID RW01L.AB-A, you may connect an external antenna to terminalsANT1 and ANT2 (X1). When connecting an external antenna, you must separate the two connectionson the onboard antenna.

Note the following when dimensioning and tuning the antenna.

Antenna parameters- Recommended max. dimensions 70 x 70 mm- Antenna coil material : Lacquered copper wire- Antenna coil wire thickness: 0.2 mm- Inductance: 737 ± 7 µH- Resistance: 10 ± 1 Ω- Intrinsic capacitance < 120 pF

Test points:ANT2 Antenna signal:GND Reference potential

Fig. 2: Antenna signal between ANT2 and GND

Test valuesUpp: 10 Vf: 125 kHz

NOTE:The reader is designed for operating only one antenna. Operating 2 parallel switched antennasmay damage the reader, or at least have a negative impact on the read range of the reader.



1.8. Declaration of Conformity



2. Data traffic between Reader and Host

There are three different kinds of data traffic between the reader and a host (terminal, PC, etc.).Polling and scan modes are used for data exchange between the transponder and host, whereasconfiguration mode is used to configure the reader parameters to the particular application. Which kindof data traffic is supported by which interface is shown in the table below.

Asynchronous interface(RS232-TTL)

Data- / Clock interface

Polling-Mode -

Scan-Mode

Configuration-Mode -

NOTES:

• A hardware solution is used for toggling between polling and scan mode (see: 1.6. TogglingPolling- / Scan-Mode)

• When scan mode is active, neither polling nor configuration mode is allowed!



2.1. Asynchronous interface, data formats and protocol frames

The asynchronous interface can be used to configure the ID RW01L.AB-A, write data to thetransponder and read data from the transponder. Communication between reader and host (terminal,PC, etc.) takes place using fixed protocols. The protocol used is designed for data bus exchange andincludes a bus address.

In data traffic over the asynchronous interface the reader replies with the requested data and a statusmessage. The reply always includes the sent control byte.

Protocol structure:

Host → Reader:1 2 3 4...n-1 n

Length = n COM-Adr Control byte Protocol data CSUM

Host ← Reader1 2 3 4 (5...n-1) n

Length = n COM-Adr Control byte Status1 (protocol data) CSUM

Length n:Number of protocol bytes 1- n incl. length byte and checksum

COM-Adr:0..7 Device address for bus operation

NOTE(S):The reader can always be accessed at COM-Adr = 255.

Status / protocol data:Contains the status message or protocol data to or from reader

CSUM:XOR operation of the protocol byte from 1 to n-1

1 see APPENDIX B:



Data format:Start bit: 1

Data bit: 8

Stop bit: 1

Parity: even (default)No

Timing:

• Protocol start gap:Before the start character (length byte) of the protocol a time gap of at least 5 ms must bemaintained.

Host → Reader: .. Response time Start gap .. ..

5...n ms min. 5 ms Host ← Reader: .. .. ..

• Data timeout:Within a protocol the characters must follow at an interval of max. 12 ms.

max. 12 ms max. 12 ms max. 12 ms Host → Reader: Char n Char n+1 Char n+2 ..



2.2. Polling mode

In polling mode you can exchange data between the host and a transponder via the reader in anysequence and as often as desired as long as the transponder is in the detection zone of the readerand the host has “selected” the transponder. Scan mode must be inactive in order to exchange data inpolling mode.

Before reading or writing any data, a transponder must be selected. In addition you must use theprotocol for reading the serial no. (see: 3.1. [0x11] GET_SNR). If at this time a transponder is locatedin the detection zone of the reader, the former is selected and all following read/write commands affectthis transponder only.

Required steps for communication with a transponder in polling mode:1. Select transponder (Protocol: Read serial no.)2. Send any command to transponder

Host (Terminal / PC / ....) Reader (Reader)

Select transponder → Transponder in field ?

(read serial no.) Yes No

← Transponder typeand serial no.

Status = notransponder

←

Read data → Selected transponder in field ?

Yes No

← Status / dataprotocol

Status = notransponder

selected

←

Write data → Selected transponder in field ?

Yes No

← Status protocol Status = notransponder

selected

←

NOTE(S):While writing data to a transponder, be sure that it remains in the read range for the entireduration of the write procedure. If the transponder is removed from the detection zone during awrite procedure, you may lose data.



2.3. Scan mode

In this mode the reader autonomously sends data to the host as soon as a transponder is located in itsdetection zone and it has read the required data. Scan mode can be configured within a broad scope,so that it can be adapted to virtually any application.

In scan mode the data are generally output one time. Only when the transponder has left the detectionzone for time SCAN_LOCK_TIME (see: 5.1.3. SCAN_MODE) are the data output again.

In scan mode you can read and output either the serial number or a data block from a transponder.The data format depends on the selected interface (asynchronous or data/clock interface).


FEIG ELECTRONIC GmbH Pag

2.3.1. Scan mode over the asynchronous interface

If scan mode is used over the asynchronous interface, the transponder data are output either in hexformat or in ASCII format (see: 5.1.3. SCAN_MODE). In addition, it is possible to preface an individualstart character (SCAN_PREFIX) and/or append a terminating character (SCAN_TERM).

The following examples show how 5 bytes of raw transponder data can be output over the serialinterface for various configurations:

Hex format:Raw data = 0x041F25D361

without SCAN_PREFIX or SCAN_TERM1 2 3 4 5

0x04 0x1F 0x25 0xD3 0x61

with SCAN_PREFIX and SCAN_TERM1 2 3 4 5 6 7

DATA

0x02 0x04 0x1F 0x25 0xD3 0x61 0x0D

ASCII format:Raw data = 0x041F25D361

without SCAN_PREFIX or SCAN_TERM1 2 3 4 5 6 7 8 9 10

0x30 0x34 0x31 0x46 0x32 0x35 0x44 0x33 0x36 0x31

with SCAN_PREFIX and SCAN_TERM1 2 3 4 5 6 7 8 9 10 11 12

0x02 0x30 0x34 0x31 0x46 0x32 0x35 0x44 0x33 0x36 0x31 0x0D

SCAN PREFIX SCAN TERM

SCAN TERMSCAN PREFIX
DATA
DATA

DATA

DATA

e 16 of 39 H20801-1e-ID-B.doc



2.3.2. Scan mode over the data/clock interface

In addition to the asynchronous interface, a synchronous data/clock interface is available which worksunidirectional in either Wiegand or magnetic card emulation. The serial number or data can be outputon this interface. The data/clock interfaces can be used only in scan mode.

2.3.2.1. Magnetic card emulation

Data format:Magnetic card emulation offers three various data formats for data output. These formats areshown in the following table and are configured using parameter 5.1.2. READER_MODE.

The data volume can be defined using parameter 5.1.5. D_LGT and 5.1.6. D_START.b000 b010 b011

DC_FORMATbinary 1:1

Conforms toISO 7811-2 (5 bit)

Conforms toISO 7811-1 (7 bit)

Raw data MSB......LSB P / MSB.....LSB P / MSB..........LSB

0x0 b 0 0 0 0 b 1 / 0 0 0 0 b 0 / 0 1 0 0 0 0

0x1 b 0 0 0 1 b 0 / 0 0 0 1 b 1 / 0 1 0 0 0 1

0x2 b 0 0 1 0 b 0 / 0 0 1 0 b 1 / 0 1 0 0 1 0

0x3 b 0 0 1 1 b 1 / 0 0 1 1 b 0 / 0 1 0 0 1 1

0x4 b 0 1 0 0 b 0 / 0 1 0 0 b 1 / 0 1 0 1 0 0

0x5 b 0 1 0 1 b 1 / 0 1 0 1 b 0 / 0 1 0 1 0 1

0x6 b 0 1 1 0 b 1 / 0 1 1 0 b 0 / 0 1 0 1 1 0

0x7 b 0 1 1 1 b 0 / 0 1 1 1 b 1 / 0 1 0 1 1 1

0x8 b 1 0 0 0 b 0 / 1 0 0 0 b1 / 0 1 1 0 0 0

0x9 b 1 0 0 1 b 1 / 1 0 0 1 b 0 / 0 1 1 0 0 1

0xA b 1 0 1 0 b 1 / 1 0 1 0 b 1 / 1 0 0 0 0 1

0xB b 1 0 1 1 b 0 / 1 0 1 1 b 1 / 1 0 0 0 1 0

0xC b 1 1 0 0 b 1 / 1 1 0 0 b 0 / 1 0 0 0 1 1

0xD b 1 1 0 1 b 0 / 1 1 0 1 b 1 / 1 0 0 1 0 0

0xE b 1 1 1 0 b 0 / 1 1 1 0 b 0 / 1 0 0 1 0 1

0xF b 1 1 1 1 b 1 / 1 1 1 1 b 0 / 1 0 0 1 1 0

Start „%“ - b 0 / 1 0 1 1 b 1 / 0 0 0 1 0 1

Stop „?“ - b 1 / 1 1 1 1 b 0 / 0 1 1 1 1 1



Example: Output raw data 0x19BF in the 3 various formats

DC-FORMAT

Start% 0x1 0x9 0xB 0xF

Stop?

LRC

b001 - b 0001 b 1001 b 1011 b 1111 - -

b010 b 1101/0 b 1000/0 b 1001/1 b 1101/0 b 1111/1 b 1111/1 b 0001/0

b011 b 101000/1 b 100010/1 b 100110/0 b 010001/1 b 011001/0 b 111110/0 b 011010/0

Time

LRCXOR operation on the start, data and stop characters

Signals:

1 01 0

tnta

tb

/RCP

/RDP

/CLStv ts

0

Fig. 3: Interface signals for magnetic card emulation

tn = 0,. msta(n) ≈ tn / 3tb(n) ≈ tn / 2

tv = ts = 10...12 ms



2.3.2.2. Wiegand emulation

Data format:In Wiegand emulation the data are output with no conversion, just as they are coded on thetransponder.

The data volume can be defined using parameter 5.1.5. D_LGT and 5.1.6. D_START.

Signals:

/RCP = DATA0

/RDP = DATA1

/CLStv ts

1 1 1

0 0 0

tn

Fig. 4: Interface signals for Wiegand emulation

tn = 0.5 mstv = ts = 10..12 ms



3. Polling mode (read and write transponder data)

3.1. [0x11] GET_SNR

The polling command [0x11] GET_SNR performs two functions:

1. It selects the transponder.

2. It returns the serial number of the transponder and its type to the host

Host → Reader:1 2 3 4

4 COM-Adr [0x11] CSUM

Host ← Reader:1 2 3 4 5 6........10 11

11 COM-Adr [0x11] Status1 TR_TYP SNR CSUM

TR_TYPTransponder type identifier

0x00: ID-CTx.A (Read-Only)0x01: ID-DTx.B (Read/Write)

SNR:Transponder serial number. It is 5 bytes in length and is output in hex.

1 see APPENDIX B: List of status bytes



3.2. [0x14] WRITE_DB (Write data block(s))

Command for writing data to the selected transponder

Host → Reader:1 2 3 4 5...8, 12, 16, 20 n

9, 13, 17, 21 COM-Adr [0x14] DB-ADR DB CSUM

Host ← Reader1 2 3 4 5

5 COM-Adr [0x14] Status1 CSUM

DB-ADR:Physical address of the transponder starting at which the data contained in DB will be writtento the transponder (see also: APPENDIX C: Memory model ID DTx.B).

NOTE:In contrast to the readers in the OBID® ID RW family, the OBID® ID RW01L.AB-A readerworks directly with the physical addresses of the transponder. DB-ADR = 1 is used forexample to read and write the configuration of the transponder for a transponder typeID DTx.B.

DB:Data of any desired content for writing to the transponder. DB has a length of 4, 8, 12 or 16bytes.




3.3. [0x15] READ_DB (Read data block(s)

Command for reading data from the selected transponder

Host → Reader:1 2 3 4 5 6

6 COM-Adr [0x15] DB-ADR DB-N CSUM

Host ← Reader1 2 3 4 5...8, 12, 16, 20 9, 13, 17, 21

9, 13, 17, 21 COM-Adr [0x15] Status1 DB: 1...4 á 4 bytes CSUM

DB-ADR:Physical address of the transponder starting at which the data DB will be read from thetransponder (see also: APPENDIX C: Memory model ID DTx.B).

NOTE:In contrast to the readers in the OBID® ID RW family, the OBID® ID RW01L.AB-A readerworks directly with the physical addresses of the transponder. DB-ADR = 1 is used forexample to read and write the configuration of the transponder for a transponder typeID DTx.B.

DB-N: (0...4)The DB-N parameter defines the number of data blocks to be read from the transponderstarting at address DB-ADR.

DB:Data block that was read from the transponder.




3.4. [0x1A] Halt (ID DTx.B only)

The ID DTx.B transponders can be silenced using the “Halt” command. This makes it possible to turnoff individual transponders located in the antenna field until you can select the transponder you wantto exchange data with. The transponder must be selected before executing this command.


4 COM-Adr [0x1A] CSUM

Host ← Reader:1 2 3 4 5

5 COM-Adr [0x1A] Status1 CSUM

A transponder to which this command was applied can only be accessed again after leaving the RFfield of the reader or if the command 4.6. [0x69] RF_RESET is sent to the reader.




4. Commands for reader control and configuration

4.1. [0x62] CONFIG_READ

The command CONFIG_READ can be used to read the current configuration of the reader block byblock. The configuration is stored in a block with 14 bytes (see also 5. Reader Configuration).

Host → Reader:1 2 3 4 5

5 COM-Adr [0x62] CFG_ARD CSUM

Host ← Reader1 2 3 4 5...18 19

19 COM-Adr [0x62] Status1 CFG (14 Byte) CSUM

CFG_ADR:Address of the configuration block you want to read.

CFG:Configuration block

4.2. [0x82] CONFIG_WRITE

The command CONFIG_WRITE is used to save a configuration block in the reader.

Host → Reader:1 2 3 4 5...18 19

19 COM-Adr [0x82] CFG_ADR CFG CSUM

Host ← Reader:1 2 3 4 5


CFG_ADR:Address of the configuration block you want to read.

CFG:Configuration block

NOTE:In order for the reader to work with the modified configuration, you must perform a reset on thereader after saving a modified configuration (e.g., 4.4. [0x63] CPU_RESET).

1 see APPENDIX B: List of status bytes2 see APPENDIX B: List of status bytes



4.3. [0x64] CONFIG_RESET

The protocol CONFIG_RESET is used to reset the configuration parameters to their factory defaultsetting (see 5. Reader Configuration).





4.4. [0x63] CPU_RESET

This protocol can generate a reset of the microcontroller on the reader.





NOTE:Sometimes the reader reply will be followed by one byte with 0xFF. This character is to beignored by the host.

1 see APPENDIX B: List of status bytes2 see APPENDIX B: List of status bytes



4.5. [0x65] GET_VERSION

This protocol is used to get the software version of the reader, its model number and the modelnumbers of the transponders which the software supports.



Host ← Reader1 2 3 4 5...6 7

10 COM-Adr [0x65] Status1 SW-Rev -

8 9 10

RD-Typ TR_TYP CSUM

SW-Rev:Software revision status

RD-Typ:Reader model

RD-Typ Reader model20 ID RW01L

TR_TYP:Displays those transponders supported by the software.

Bit: 7 6 5 4 3 2 1 0

Function: - - - - - - DTx.B CTx.A

1 see APPENDIX B:



4.6. [0x69] RF_RESET

The command RF_RESET turns off the RF field of the reader antenna for a short time. Alltransponders located in the reader’s antenna field are set to their base state.





NOTE(S):

• Following an RF reset the reader requires at least 100 ms before it can receive a newtransponder.

• Following an RF reset a transponder located in the antenna field must be reselected.




4.7. [0x52] BAUDRATE_DETECTION

This protocol is used to get the current baud rate of the reader’s asynchronous interface.

Host → Reader:1 2 3 4 5

5 COM-Adr [0x52] 0x00 CSUM



The return protocol is sent only if the query is made with the baud rate and current parity of the reader.




5. Reader Configuration

5.1. CFG0: Reader Parameters

The reader configuration is contained in a 14-byte block (CFG0).

Byte 0 1 2 3 4 5 6 Contents COM_PARA READER_

MODE SCAN_MODE

DB_ADR D_START D_LGT SCAN_PREFIX

Default 0x05 0x02 0x00 0x00 0x00 0x0F 0x02

"STX"

Byte 7 8 9 10 11 12 13

Contents SCAN_TERM

- - - - - TAG_DRV

Default 0x0D 0x01

"CR"



5.1.1. COM_PARA

Transmission parameters for the asynchronous interfaceBit: 7 6 5 4 3 2 1 0

Function: - COM_ADR P BAUDdefault: b0 b000 b0 b101

BAUD:Baud rate

COM-BR Baud rate

b100b101b110

4800 baud9600 baud

19200 baud

P:0 ⇒ Data transmission with even parity1 ⇒ Data transmission with no parity

COM_ADR (0...7):This parameter is intended for using the reader with a bus-compatible interface (e.g.,RS485) when assigning the bus address. Bus addresses from 0 to 7 can beassigned via software. The reader can be accessed at any time using the configuredaddress or address 255. Protocols with an incorrect address are ignored, regardlessof whether the reader is operated in a data bus or in a point-to-point connection.

NOTE(S):The reader can be accessed at any time using COM-Adr 255 in the sentprotocol. It will reply with its configured address.



5.1.2. READER_MODE

This byte defines the operating mode of the reader. Bit: 7 6 5 4 3 2 1 0

Function: - - - DC-FORMAT SCAN-IF - default b0 b0 b0 b000 b1

SCAN_IF:This byte is used to select the interface for scan mode

b0: Scan mode over the asynchronous interfaceb1: Scan mode over the data/clock interface

DC_FORMAT:This parameter is used to specify data transmission for the data/clock interface.

b000: Wiegand Emulation (see 2.3.2.2. Wiegand emulation)Data format: Hex (binary) 1:1, as stored on the transponder.

b001: Magnetic card emulation (see: 2.3.2.1. Magnetic card emulation)Data format: Hex (binary) 1:1, as stored on the transponder.

b010: Magnetic card emulation (see: 2.3.2.1. Magnetic card emulation)Data format: per ISO 7811-2, Track 2 (5 bits)

b011: Magnetic card emulation (see: 2.3.2.1. Magnetic card emulation)Data format: per ISO 7811-1, Track 1 (7 bits)



5.1.3. SCAN_MODE

This parameter is used to further define the behavior of scan mode.Bit: 7 6 5 4 3 2 1 0

Function

PR

EFI

X_E

TER

M_E

-

FOR

MA

T-

SC

AN

_LO

CK

_TIM

E

DA

TA

default b0 b0 b0 b0 b00 b00

DATA:Defines which data are output in scan mode

b00: Serial no.

b01: Data blockThe data block defined by DB_ADR, D_LGT and D_START is output.

b10 - reserved -

b11 - reserved -

SCAN_LOCK_TIMEThis parameter defines the time for which the transponder is locked by the reader forfurther processing. Only when the transponder has left the detection zone of thereader for SCAN_LOCK_TIME are its data output again.

b00: 0 secWith this setting the data are output continuously as fast as they are readfrom the transponder.

b01: 0.5 sec

b10: 1.0 sec

b11: 2.0 sec



FORMAT:This bit is used to specify the data output format when the asynchronous interface isactivated for scan mode.

b0 unformatted hex dataIn this case the raw data are output just as they are read from thetransponder.

b1 ASCII formatted hex dataIn this case the raw data are reformatted into ASCII code. First the databytes are broken down into their nibbles, and then converted into ASCIIaccording to the following table.

raw data(hex / binary)

ASCII data(ASCII / hex)

0x0 b0000 '0' 0x300x1 b0001 '1' 0x310x2 b0010 '2' 0x320x3 b0011 '3' 0x330x4 b0100 '4' 0x340x5 b0101 '5' 0x350x6 b0110 '6' 0x360x7 b0111 '7' 0x370x8 b1000 '8' 0x380x9 b1001 '9' 0x390xA b1010 'A' 0x410xB b1011 'B' 0x420xC b1100 'C' 0x430xD b1101 'D' 0x440xE b1110 'E' 0x450xF b1111 'F' 0x46

TERM_EThis bit is used to specify whether the data should have a terminating characterwhen outputting over the asynchronous interface (see: 5.1.8. SCAN_TERM).

b0: SCAN_TERM is not usedb1: SCAN_TERM is appended

PREFIX_EThis bit is used to specify whether the data should have a prefix (start character)when outputting over the asynchronous interface (see: 5.1.7. SCAN_PREFIX).

b0: SCAN_PREFIX is not usedb1: SCAN_PREFIX is prefixed


FEIG ELECTRONIC GmbH

5.1.4. DB_ADR

The start address of a data block from where transponder data should be read in scan mode.

Valid addresses depend on the transponders used and may be found in their respectivedocumentation.

5.1.5. D_LGT

D_LGT defines the number of raw data which should be output in scan mode. The interpretationD_LGT depends on the configured data output interface for scan mode (see also: 5.1.2.READER_MODE, Parameter SCAN_IF).

Scan mode over asynchronous interface :D_LGT defines the number of raw data bytes that are sent.

NOTE:The reader can output a maximum of 16 bytes of raw data.

Example.:Data Block

Byte 0 1 2 3 4 5 6 7Data 0x01 0x23 0x45 0x67 0x89 0xAB 0xCD 0xEF

Output Data

Scan mode over data/clock inD_LGT the number of r

Example:Data Block

Byte 0Data 0x0

Output Data

D_START = 1

P

0x23 0

terface:aw data bits

11 0x23 0

b0010 001

1

D_LGT = 4

x45 0x67 0x89

that are sent.

2 3 4 5 6 7x45 0x67 0x89 0xAB 0xCD 0xEF

D START =

ag

1

D_LGT = 26

e 34 of 39 H20801-1e-ID-B.doc

b0100 0101 b0110 0111 b10



5.1.6. D_START

This parameter defines the first byte of the raw data (defined by DB_ADR and D_LGT) which shouldbe sent in scan mode. If you want to output a complete block, D_START = 0 must be set.

5.1.7. SCAN_PREFIX

This parameter is used to define any desired start character for scan mode over the asynchronousinterface.

As soon as the reader outputs data in scan mode over the asynchronous interface and the bitPREFIX_E = 1 is set (see: 5.1.3. SCAN_MODE), this character is prefixed to the data stream.

5.1.8. SCAN_TERM

This parameter is used to define any desired terminating character for scan mode over theasynchronous interface.

As soon as the reader outputs data in scan mode over the asynchronous interface and the bitTERM_E = 1 is set (see: 5.1.3. SCAN_MODE), this character is appended to the data stream.

5.1.9. TAG_DRV

This parameter is used to exclusively define which transponder model is processed. The reader willonly process the transponder model configured here (or compatible derivative versions of this model).

TAG_DRV:0: ID CTx.A (read-only)1: ID DTx.B (read / write)



APPENDIX

APPENDIX A: Timing

1. Time values stored in the EEPROM have an accuracy of ± 5 ms.

2. The response times of the asynchronous interface depend on:

• The amount of data to be read or written,

• The type and number of transponders supported by the reader,

• The location of the transponder when the request is made,

• Any existing local electromagnetic interference,

• The success of failure of the request.

typ.1

CTx.A DTx.BGET_SNR

Status: 0x010x002

38 ms80 ms

36 ms25 - 86 ms

READ_DB:1 block2 blocks3 blocks4 blocks

25 ms48 ms71 ms94 ms

WRITE_DB:1 block2 blocks3 blocks4 blocks

-

60 ms112 ms165 ms217 ms

EEPROM Parameter 65 ms

1 Measured and average laboratory values, allowance must be made for deviations2 xx / yy:

xx ⇒ Read serial number first (select)yy ⇒ Read serial number of selected transponder



APPENDIX B: List of status bytes

Hexvalue

General

0x00 OK• Data/parameter was/were read or saved without error• Control command was executed

Hexvalue

Transponder Status

0x01 No Transponder:There is no transponder in the detection zone of the reader.• The transponder in the detection zone was silenced.• Communication between the reader and transponder was interfered with to the

point that the reader can no longer read the transponder.• A non-permitted read/write action results in the transponder being turned off.

0x03 Write-Error• The distance between the transponder and reader antenna may be too great.• An attempt was made to write in an electrically noisy environment.

0x05 Wrong Transponder-TypeThe command is not supported by the transponder.

0x06 Read-ErrorNegative plausibility check of the read data:• The distance between the transponder and reader antenna may be too great.• An attempt was made to read in an electrically noisy environment

0x07 Select-Error:Read/write command without first selecting a transponder.

Hexvalue

Interface status

0x80 Unknown Command• Reader does not support the selected function.• To save the password for a transponder not supported by the software in the

reader.0x81 Length-Error:

Protocol is too short or too long



APPENDIX C: Memory model ID DTx.B

APPENDIX C1: Philips Hitag 1

OBID®Hitag 1

ID RW01L ID RWA ID RWBlock Page DB-ADR Address Address

Access Note

0 0 S-No. S-Nr. • read-only

1 1 C0 C0public transponder

configura-tion

• read/write• read-only config-

urable2 2 C1 C1

0

3 3 C2 C2

• secret write-only• read/write-log

configurable4 4 C3 C35 5 C4 C46 6 C5 C51

7 7 C6 C6

CryptoKeys • read/write• secret• read/write-log

1

configurable2 8 - 11 8 - 11 DB10 S0 - S3

3 12 - 15 12 - 15 DB11 S4 - S7

secret

• read/write• read/only config-

urable

4 16 - 19 16 - 19 DB8 D32 - D35S8 - S11

5 20 - 23 20 - 23 DB9 D36 - D39S12 - S15

6 24 - 27 24 - 27 AC0DB12

D40 - D43S16 - S19

7 28 - 31 28 - 31 ID0DB13

ID-No (12Byte)D96 - 99

public /secret


urable• secret configur-

able

8 32 - 35 32 - 35

DB0ID1AC1DT0

D0 – D3

9 36 - 39 36 - 39

DB1ID2AC2DT1

D4 – D7

10 40 - 43 40 - 43

DB2ID3AC3DT2

D8 – D11

11 44 - 47 44 - 47DB3LK0DT3

D12 – D15

12 48 - 51 48 - 51 DB4SK0 D16 – D19

public

13 52 - 55 52 - 55DB5SK1LK1

D20 – D23

14 56 - 59 56 - 59DB6SK2LK3

D24 – D27

15 60 - 63 60 - 63DB7SK3LK3

D28 – D31

Optionalfreely

availablememory

• read/write

1 Data cannot be read or written.



APPENDIX C2: Philips Hitag S

OBID®Hitag S

ID RW01L ID RWA ID RWBlock Page DB-ADR Address Address

Access Note

0 S-No S-No. S-Nr. • read-only1 1 C0 C02 2 C1 C10

3 3 C2 C2

transponderconfigura-

tion1 4 - 7 4 - 7 DB14 D44 - D472 8 - 11 8 - 11 DB10 D48 - D513 12 - 15 12 - 15 DB11 D52- D554 16 - 19 16 - 19 DB8 D32 - D355 20 - 23 20 - 23 DB9 D36 - D39

6 24 - 27 24 - 27 AC0DB12 D40 - D43

7 28 - 31 28 - 31 ID0DB13

ID-No (12Byte)D96 - 99

8 32 - 35 32 - 35

DB0ID1AC1DT0

D0 – D3

9 36 - 39 36 - 39

DB1ID2AC2DT1

D4 – D7

10 40 - 43 40 - 43

DB2ID3AC3DT2

D8 – D11

11 44 - 47 44 - 47DB3LK0DT3

D12 – D15

12 48 - 51 48 - 51 DB4SK0 D16 – D19

13 52 - 55 52 - 55DB5SK1LK1

D20 – D23

14 56 - 59 56 - 59DB6SK2LK3

D24 – D27

15 60 - 63 60 - 63DB7SK3LK3

D28 – D31

publicOptional

freelyavailablememory


urable

handbuch id rw01l.ab-a - sebeto.com rw r… · the obid® id rw01l.ab-a .....5 1.3. technical data...

Documents