system-manual id isc.lr2000...manual preliminary public (b) 2011-04-21 h01112-0e-id-b.docx id...

MANUAL

preliminary

public (B)

2011-04-21

H01112-0e-ID-B.docx

ID ISC.LR2500-A ID ISC.LR(M)2500-B

Standard-Reader

from Firmware-Version

RFC 1.1 and higher

OBID i-scan

System-Manual ID ISC.LR(M)2500

FEIG ELECTRONIC GmbH Page 2 of 220 H01112-0e-ID-B.docx

Note

Copyright 2011 by

FEIG ELECTRONIC GmbH

Lange Strasse 4

D-35781 Weilburg-Waldhausen

Tel.: +49 6471 3109-0

http://www.feig.de

With the edition of this document, all previous editions become void. Indications made in this manual may be

changed without previous notice.

Copying of this document, and giving it to others and the use or communication of the contents thereof are for-

bidden without express authority. Offenders are liable to the payment of damages. All rights are reserved in the

event of the grant of a patent or the registration of a utility model or design.

Composition of the information in this document has been done to the best of our knowledge. FEIG

ELECTRONIC GmbH does not guarantee the correctness and completeness of the details given in this manual

and may not be held liable for damages ensuing from incorrect or incomplete information. Since, despite all our

efforts, errors may not be completely avoided, we are always grateful for your useful tips.

The instructions given in this manual are based on advantageous boundary conditions. FEIG ELECTRONIC

GmbH does not give any guarantee promise for perfect function in cross environments and does not give any

guaranty for the functionality of the complete system which incorporates the subject of this document.

FEIG ELECTRONIC call explicit attention that devices which are subject of this document are not designed with

components and testing methods for a level of reliability suitable for use in or in connection with surgical implants

or as critical components in any life support systems whose failure to perform can reasonably be expected to

cause significant injury to a human. To avoid damage, injury, or death, the user or application designer must take

reasonably prudent steps to protect against system failures.

FEIG ELECTRONIC GmbH assumes no responsibility for the use of any information contained in this document

and makes no representation that they free of patent infringement. FEIG ELECTRONIC GmbH does not convey

any license under its patent rights nor the rights of others.

OBID® and OBID i-scan

® are registered trademarks of FEIG ELECTRONIC GmbH.

I-CODE® is a registered trademark of NXP Semiconductors

Tag-itTM

is a registered trademark of Texas Instruments Incorporated.

General information's regarding this manual

If bits within one byte are filled with "-", these bit spaces are reserved for future extensions or for internal

testing- and manufacturing-functions. These bit spaces must not be changed, as this may cause faulty opera-

tion of the Reader.

The following figure formats are used:

0...9: for decimal figures

0x00...0xFF: for hexadecimal figures,

b0...1 for binary figures.

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

http://www.feig.de/

OBID i-scan



Content

Revision History of documentation ........................................................................................ 9

Abbreviations ..........................................................................................................................10

1. Introduction 11

2. Data Transmission between OBID i-scan® ID ISC.LR2500-Reader and Host 13

2.1. Configuration Commands and Control Commands ......................................................13

2.2. ISO15693 Host Commands .............................................................................................14

2.3. Buffered Read Mode ........................................................................................................17

2.4. Notification Mode .............................................................................................................18

2.5. Scan Mode .......................................................................................................................19

2.6. Reader Multiplex Mode (Syncronisation) .......................................................................21

3. Interface 22

3.1. Protocol Frames of TCP/IP protocol ...............................................................................22

3.2. Serial Data Format and Protocol Frames .......................................................................23

CRC16 Calculation Algorithm ................................................................................................25

3.3. Interface data encryption (Only ID ISC.LR(M)2500-A) ...................................................26

4. Configuration Parameters (CFG) 27

4.1. CFG0: Passwords ............................................................................................................29

4.2. CFG1: Interface ................................................................................................................31

4.3. Wiegand and Magnetic Stripe description .....................................................................34

4.3.1. Magnetic Strip Emulation ............................................................................................35

4.3.2. Wiegand Emulation ....................................................................................................37

4.4. CFG2: Inputs/Outputs I ....................................................................................................41

4.4.1. Dedicated Input / Output Functions ............................................................................43

OBID i-scan



4.5. CFG3: RF-Interface ..........................................................................................................44

4.6. CFG4: Transponder Parameters .....................................................................................47

4.7. CFG5: Anticollision ..........................................................................................................50

4.8. CFG6: Customer Command Option Bytes .....................................................................52

4.9. CFG7 Reserved ................................................................................................................53

4.10. CFG8: People Counter ...................................................................................................54

4.11. CFG9: Input / Output II (Assignment – output to antenna read event) .......................57

4.12. CFG10: Trigger ...............................................................................................................60

4.13. CFG11: Read Mode / Read Data ...................................................................................62

4.14. CFG12: Read Mode - Filter ............................................................................................69

4.15. CFG13: Scan-Mode ........................................................................................................72

4.16. CFG14: Reserved ...........................................................................................................75

4.17. CFG15: Antenna Multiplexing I .....................................................................................76

4.18. CFG16: Persistence Reset .............................................................................................78

4.19. CFG17: Antenna Multiplexing II ....................................................................................79

4.20. CFG18: Reader Synchronisation ..................................................................................80

4.21. CFG19: Reserved ...........................................................................................................82

4.22. CFG20: RF-Parameter ....................................................................................................83

4.23. CFG24 .. 29: Reserved ...................................................................................................85

4.24. CFG63: Customer Parameter ........................................................................................86

4.25. CFG64: Crypto ................................................................................................................87

4.26. CFG66: LAN Settings, Part 1 .........................................................................................88



4.29. CFG69 : LAN Settings, Part 4 ........................................................................................92

4.30. CFG70: WLAN Settings, Part 1 (Only ID ISC.LR(M)2500-A).........................................94

OBID i-scan





4.33. CFG73 : WLAN Settings, Part 4 (Only ID ISC.LR(M)2500-A)........................................98

4.34. CFG74: WLAN Security Settings, Part 1 (Only ID ISC.LR(M)2500-A) ........................ 100








4.42. CFG82: Notification Channel, Part 1 ........................................................................... 109

4.43. CFG83: Notification Channel, Part 2 ........................................................................... 111

4.44. CFG84: Network Time Protocol (Only ID ISC.LR(M)2500-A) ..................................... 112

5. Protocols for Reader Configuration 114

5.1. [0x80] Read Configuration ............................................................................................. 114

5.2. [0x81] Write Configuration ............................................................................................ 115

5.3. [0x83] Set Default Configuration ................................................................................... 116

5.4. [0x87] Set System Time and Date ................................................................................. 117

5.5. [0x88] Get System Time and Date ................................................................................. 118

5.6. [0x8A] Read Configuration ........................................................................................... 119

5.7. [0x8B] Write Configuration ........................................................................................... 122

5.8. [0x8C] Reset Configuration .......................................................................................... 126

6. Protocols for Reader Control 128

6.1. [0x52] Baud Rate Detection ........................................................................................... 129

OBID i-scan



6.2. [0x55] Start Flash Loader .............................................................................................. 129

6.3. [0x63] RF Controller Reset ............................................................................................ 130

6.4. [0x64] System Reset ..................................................................................................... 130

6.5. [0x66] Get Reader Info .................................................................................................. 131

6.6. [0x69] RF Reset .............................................................................................................. 136

6.7. [0x6A] RF Output ON/OFF ............................................................................................. 137

6.8. [0x6D] Get Noise Level .................................................................................................. 138

6.9. [0x6E] Reader Diagnostic ............................................................................................. 139

6.10. [0x72] Set Output ........................................................................................................ 143

6.10.1. Set Output Examples .............................................................................................. 145

6.11. [0x74] Get Input ........................................................................................................... 146

6.13. [0xA0] Reader-Login ................................................................................................... 147

6.14. [0xAE] Reader Authent ................................................................................................ 148

6.15. [0xAD] Write Reader Authent-Key ............................................................................... 149

7. Protocols for ISO15693 Host Commands 150

7.1. [0xB0] Host commands for ISO15693 Mandatory and Optional Commands ............. 151

7.1.1. [0x01] Inventory ........................................................................................................ 152

7.1.2. [0x02] Stay Quiet ...................................................................................................... 155

7.1.3. [0x22] Lock Multiple Blocks ...................................................................................... 156

7.1.4. [0x23] Read Multiple Blocks ...................................................................................... 158

7.1.5. [0x24] Write Multiple Blocks ...................................................................................... 160

7.1.6. [0x25] Select ............................................................................................................. 162

7.1.7. [0x26] Reset to Ready .............................................................................................. 163

7.1.8. [0x27] Write AFI ........................................................................................................ 164

7.1.9. [0x28] Lock AFI ........................................................................................................ 165

7.1.10. [0x29] Write DSFID................................................................................................. 166

7.1.11. [0x2A] Lock DSFID ................................................................................................. 167

7.1.12. [0x2B] Get System Information ............................................................................... 168

OBID i-scan



7.1.13. [0x2C] Get Multiple Block Security Status ............................................................... 170

7.2. [0xBF] ISO15693 Transparent Command ..................................................................... 171

Supported ISO15693 Host commands 174

7.3. Supported ISO15693 Host commands for ISO15693 Transponders .......................... 174

7.3.1. EM Microelectronics (EM4034) ................................................................................. 174

7.3.2. EM Microelectronics (EM4135) ................................................................................. 175

7.3.3. Fujitsu (MB89R116) ................................................................................................ 176

7.3.4. Fujitsu (MB89R118) ................................................................................................ 177

7.3.5. Fujitsu (MB89R119) ................................................................................................ 178

7.3.6. Infineon (my-d page mode) 0x60 ............................................................................. 179

7.3.7. Infineon (ISO address mode) 0xE0 .......................................................................... 180

7.3.8. Infineon (My-d Light) ................................................................................................ 181

7.3.9. NXP (I-Code SLI)...................................................................................................... 182

7.3.10. NXP (I-Code SLI-S) ................................................................................................ 183

7.3.11. NXP (I-Code SLI-L) ................................................................................................ 184

7.3.12. STMicroelectronics (LRI512) ................................................................................ 185

7.3.13. STMicroelectronics (LRI64) .................................................................................. 186

7.3.14. STMicroelectronics (LRI2k, LRIS2k) ..................................................................... 187

7.3.15. STMicroelectronics (M24LR64-R) ......................................................................... 188

7.3.16. Texas Instruments (Tag-it HFI Pro / Standard) ..................................................... 189

7.3.17. Texas Instruments (Tag-it HFI Plus) ..................................................................... 191

7.4. Supported ISO15693 Host commands for non ISO15693 Transponders ................... 193

7.4.1. NXP I-Code 1 Transponders .................................................................................... 193

8. Protocols for Buffered Read Mode and Notification Mode 194

8.1. The Buffered Read Mode Procedure............................................................................. 194

8.2. The Notification Mode Procedure ................................................................................. 195

8.3. Transponder Access in the Buffered Read Mode and Notification Mode .................. 196

8.4. [0x22] Read Buffer ......................................................................................................... 197

8.5. [0x31] Read Data Buffer Info ......................................................................................... 200

OBID i-scan



8.6. [0x32] Clear Data Buffer ................................................................................................ 201

8.7. [0x33] Initialize Buffer .................................................................................................... 201

8.8. [0x34] Force Notify Trigger ............................................................................................ 202

ANNEX 203

ANNEX A: Codes of Transponder Types ............................................................................. 203

ANNEX B: Time Behavior of the Asynchronous Interface ................................................. 204

ANNEX C: Time Behavior of ISO15693 Host Commands ................................................... 205

Time Behaviour for [0x01] Inventory and ISO15693 Transponders .................................... 206

ANNEX D: Index of Status Bytes ......................................................................................... 207

ANNEX E: Codes of Reader Types ....................................................................................... 210

ANNEX F: Examples for Read Data .................................................................................... 211

ISO15693 Host Command (DB-Size of the Transponder = 4 bytes) ................................... 211

ISO15693 Host Command (DB-Size of the Transponder = 8 bytes) ................................... 211

ANNEX F: Labeling of configuration parameter ................................................................. 212

OBID i-scan



Revision History of documentation

Revision Date Page Description

0e xx.11.10 Initial version

OBID i-scan



Abbreviations

ADR Address

ASK Amplitude Shift Keying

CB Config Block

CFG Configuration Parameter Block

CRC Cyclic Redundancy Check

DB data block

DIP Dual Inline Plastic

FIFO First in First out

frq Frequency

FSK Frequency Shift Keying

h Hour

Hz Hertz

ID Identification

IN Input

LEN Length

LOC Location

LSB Least Significant Byte

min Minutes

ms Milliseconds

MSB Most Significant Byte

N Number

OUT Output

R/W Read / Write Access

RD Read

REL Relay

RF Radio Frequency

RSSI Received Signal Strength Indicator

RTC Real Time Clock

TAB Table

TR Transponder

TS Timeslot

UID Unique Identifier (read only Serial Number)

WO Write Only Access

WR Write

OBID i-scan



1. Introduction

The ID ISC.LR2500 Long Range Reader and the ID ISC.LRM2500 Long Range Reader Unit are the

top of the line Long Range Reader versions of the OBID i-scan HF Product line. The OBID i-scan

HF product line offers a complete range of products to choose from to address the entire spectrum of

RFID data capture applications: from vicinity detection, to proximity and mid-range distances to the

absolute limits of HF detection.

The ID ISC.LR2500 and ID ISC.LRM2500 are the most powerful reader in the OBID i-scan HF prod-

uct line. Both devices have identical RF performance. The ID ISC.LRM2500 differs from the ID

ISC.LR2500 in terms of housing, interface options and functionality for the host connectivity of the

device.

Each member of the LR2500 product series have the following key RF features:

- Highly sensitivity receiver increased the tag detection range so that the most transponders can be

read over the entire power up, field strength area.

- RF front end accommodates arbitrary cable lengths between the reader and the antenna without

adversely affecting the read range of the antenna

- RF front end has its own power control to protect the read range from external noise sources.

- The reader delivers a DC voltage on the antenna output to source DC powered devices con-

nected to the antenna cable, such as the FEIG Dynamic Antenna Tuning board (ID

ISC.ANT.DAT-A)

- RF source of the reader meets different national radio rules and can achieve the 60dbA/m ETSI

limits.

Table: Reading distance depending on regional radio rules 1

Region max. field

strength

Reading distance

with single antenna

Gate width with op-

timal Transponder

orientation

Gate width with any

Transponder orienta-

tion

Europe 60dbA/m 120cm 3,6

200cm 3,6

130cm 4

North America 42dbA/m 60cm 2 130cm

4 105cm

5

Notes: 1. All reading distances are typical reading distance measured with Transponders having ISO Card size and Trans-

ponders with sensitivity / minimum operating field Hmin=80mA/m rms

2. Measured with Antenna ID ISC.ANT310/310

3. Measured with Antenna ID ISC.ANT800/600-DA and label parallel orientation to the antenna

4. Measured with Antenna ID ISC.ANT1700/740-SLA and –SLB

5. Measured with Antenna ID ISC.ANT1700/740-A and –B

6. To comply with the radio approvals additional shielding may be needed

In addition to the ID ISC.LR2500 Reader series having the largest read range, the platform provides

the most extensive configuration possibilities and reader command set. The base set of commands

and features are compatible with the ISO Host commands used throughout the OBID i-scan product

line. The configuration possibilities of the ID ISC.LR2500 reader make it easy to adapt the reader to a

range of applications by software and hardware configuration.

OBID i-scan



The reader is able to directly control antenna multiplexing functions to handle complex antennas ar-

rayed in various gate and portal configurations. The reader is also able to directly control and monitor

the antenna tuning circuits of our Dynamic Tuning Board.

The RF section of the reader is controlled by a dedicated DSP based, RF controller. A second micro-

controller, the Application and Connectivity Controller (ACC), uses an ARM processor running a

µcLinux operating system. The ACC transforms the reader into a powerful and intelligent device, ca-

pable of running application software directly on the reader platform and capable of connecting and

controlling other real world devices. The reader has five hardware interface ports: Ethernet, RS232,

RS485, USB and a USB port for the support of a WLAN stick on the –A version of the reader. All

ports are under control of the ACC. Furthermore, the reader has digital I/O‟s for general or dedicated

use such as synchronization of the RF Process with nearby readers to avoid mutual interference.

In combination, the powerful and flexible RF transmitter and receiver and intelligent digital controller

form the basis of an agile, multi protocol reader that can be updated as future protocols and features

are created. The Reader supports the transponder protocols 18000-3-A. ISO15693. The ACC Firm-

ware can also be updated allowing the reader to adapted to different applications. FEIG Electronic

provides a library which allows the user to develop their own applications to run on the ACC.

OBID i-scan



2. Data Transmission between OBID i-scan® ID ISC.LR2500-Reader and Host

Five different ways of data transmission between OBID® i-scan Readers and host (terminal, PC) are

possible. The Host Commands, Buffered Read Mode and Notification Mode are used for the data

exchange between Transponder and host, whereas the Configuration Commands and the Reader

Control Commands serves for adapting the Reader parameters to the individual range of applica-

tions. The following chart shows which method of data transmission is supported by which interface:

interface

RS232 RS485 LAN WLAN* USB

Configuration Commands

Reader Control Commands

Host Commands

Buffered Read Mode

Scan Mode

Notification Mode

* Only available on the ID ISC.LR(M)2500-A reader version and using an external WLAN stick on

the host USB port.

2.1. Configuration Commands and Control Commands

This method of data transmission is used for Reader configuration and the diagnosis via the asyn-

chronous interface or Ethernet Interface

The Reader-configuration parameters will be stored in the Reader memory. To store the current con-

figuration during a power down of the Reader the Reader-Configuration has to be stored in the

EEPROM. After power up the Reader reads the configuration out of the EEPROM.

The Reader control is immediately processed and the response from the Reader contains status or

data information of the control command.

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

parameter- / control command parameter received and stored / control

command processed

yes no

status /

data

error status

OBID i-scan



2.2. ISO15693 Host Commands

The ISO Host Commands provide the exchange of data between a host and Transponders via the

Reader as long as the Transponder remains in the detection range of the Reader.

Note:

During the writing of data on a Transponder, it must be ensured that the Transponder is lo-

cated within the detection range of the Reader during the entire process. If the Transponder

removed from detection range of the Reader during a writing process, this will cause a loss of

data.

The Reader distinguishes between three different modes:

Addressed mode:

Before reading or writing data in addressed mode, the UID of the Transponder has to be

known. This is executed by sending the protocol “7.1.1. [0x01] Inventory If a Transponder is

located within the detection range of the Reader at that time, it answers with its UID. For all

following read- / write orders the Transponder must be addressed with its correct UID.

The following chart will show the necessary steps for the communication with a Transponder

in addressed mode:


Inventory

to get the UID

Transponder in antenna field ?

Yes No

status /

number of Trans-

ponders / UID

status =

no Transponder

read data from Transponder with UID Transponder with

correct UID in antenna field ?

Yes No

status /

Transponder read

data

status =

no Transponder

in Reader field

write data to Transponder with UID Transponder with


Yes No

OK status status =

no Transponder

in Reader field

OBID i-scan



Non-addressed mode:

In non-addressed mode, it is not necessary to know the UID of the Transponder. This mode

is useful-, if only one Transponder is located within the range of the Reader.


in non-addressed mode:


read data Transponder in antenna field ?

Yes No

status /

Transponder read

data

status = no Trans-

ponder

in Reader field

write data Transponder in antenna field ?

Yes No

OK status status = no Trans-

ponder

in Reader field

OBID i-scan



Selected:

In this mode the Reader communicates only with the one, selected Transponder.

Before reading or writing data in selected mode, the UID of the Transponder has to be

known. This is executed by sending at first the protocol “7.1.1. [0x01] Inventory“. In a second

step the Transponder must be selected with the select command (see: 7.1.6. [0x25] Select)

which must include its UID.


in selected mode:


Inventory

to get the UID

Transponder in antenna field ?

Yes No

status /

number of Trans-

ponders / UID

status =

no Transponder

select Transponder with UID Transponder with the


Yes No

status /

Transponder read

data

status =

no Transponder

in Reader field

read data selected Transponder in antenna field ?

Yes No

status /

Transponder read

data

status =

no Transponder

in Reader field

write data selected Transponder in antenna field ?

Yes No

OK status status =

no Transponder

in Reader field

OBID i-scan



2.3. Buffered Read Mode

The Buffered Read Mode is a high level operating mode to detect Transponders which are within the

detection range of the Reader. This operation mode is especially designed for applications which use

Transponders to identify objects. The Buffered Read Mode processes all Transponder read data and

filter operations to make the user interface transparent to Transponder data and to minimize data

transfers between Reader and host. There are only three commands used to control Buffered Read

Mode.

In this operating mode the Reader automatically selects Transponders which are within the detection

range of the Reader and reads their requested data. The read Transponder data is stored in a „FIFO‟

organized data buffer.

The sampled Transponder data can be read with the 8.3. Transponder Access in the Buffered Read

Mode and Notification Mode command. This command always reads the first available data sets from

the data buffer. However already read data has to be deleted with the 8.6. [0x32] Clear Data Buffer

command before the next data sets in the data buffer can be reached with the read command.

If the Buffered Read Mode is enabled in the 4.2. CFG1: Interface configuration block the Reader im-

mediately starts sampling Transponder data after power up. The Buffered Read Mode can be reinitia-

lized with the 8.7. [0x33] Initialize Buffer command.

If turned to Buffered Read Mode the Reader answers every valid message with data- or status-

protocol. The answer includes the control byte which has been received by the Reader.


read data Transponder data in data buffer ?

Yes No

status /

data protocol

status = no valid

data

clear data Transponder data read ?

Yes No

OK status status = no valid

data

Note:

Only read operations are available with the Buffered Read Mode.

The Buffered Read Mode is only available if Scan Mode is disabled

The Buffered Read Mode can be used with the 2.6. Reader Multiplex Mode.

OBID i-scan



2.4. Notification Mode

The Notification Mode is an extended option of the Buffered Read Mode: queued Transponder data

and optionally Input/Status events are notified automatically and asynchronously to a host with the

8.4. [0x22] Read Buffer response protocol. The destination address and the notification conditions

can be set in 4.42. CFG82: Notification Channel, Part 1 configuration block. In general, the notifica-

tion channel can be used simultaneously with the host interface.

In difference to the Buffered Read Mode procedure, a notification is normally not acknowledged by

the host. Thus, the deletion of the transferred data with the 8.6. [0x32] Clear Data Buffer command

is not necessary. As an option, this acknowledgement can be enabled to synchronize the notifications

with the host to prevent notification overflow in the host application.

The notification message format depends on trigger settings in 4.12. CFG10: Trigger and settings for

the read mode in 4.13. CFG11: Read Mode / Read Data and 4.14. CFG12: Read Mode - Filter as

well as settings for the notification trigger in 4.42. CFG82: Notification Channel, Part 1. The follow-

ing table lists the message formats:

Notification Trigger: continuous or time-triggered

Input/Status Event Data Event

Read Trigger disabled Input/Status and Data Events are notified together in one or multiple messag-

es.

The message format depends on settings in TR-DATA of CFG11.

Read Trigger enabled Notification separately and immediately,

if in:

CFG11: IN flag in TR-DATA2 is set

and

CFG12: flag is set for input and/or

status to be observed

NOTE: One notification can contain

more than one input/status event, if

multiple events occur at the same time.

Notification shortly after notification

of input/status event.

The message format depends on

settings in TR-DATA of CFG11.

Notification Trigger: host-triggered

Input/Status Event Data Event

Independent of Read Trigger Input/Status and Data Events are notified together in one message. The notifi-

cation is activated by command [0x34] Force Notify Trigger.

The message format depends on settings in TR-DATA of CFG11.

An additional option of the Notification Mode is the Keepalive message, which can be sent periodically

to the host. The Keepalive message transports valuable information about the reader hardware and

antenna tuning status. Keepalive messages are never acknowledged by the host. The Keepalive

message should not be mistake with the keepalive option (s. CFG66/CFG81) of a LAN/WLAN con-

nection initiated by a host.

OBID i-scan



protocol block

protocol cycle

ts + tr

2.5. Scan Mode

In this operation mode the Reader autonomously sends out data to the Host as soon as a Trans-

ponder is within the detection range and valid data could be read.

In Scan Mode the contents of the message block (UID, data block) can be adapted to each user-

application. Scan mode is available via the asynchronous Interface.

The Reader starts the output of the protocol block as soon as all required data have been read cor-

rectly from the Transponder. If the Reader is not able to read all data of a protocol block completely

and without error, it does not send data. For example, if the address of the data block is invalid, the

UID of the Transponder will not be sent out.

Scan-Mode via asynchronous interface:

The data will be sent out depending on their configuration according to the following scheme,

the sequence of which cannot be changed.

Depending to the configuration and the number of Transponders in the detection range of

the Reader the transmitted protocols have a different format.

Example 1:

One Transponder in detection range and UID and data block should be read:

PR UID SC data EC PR UID

Example 2:

3 Transponder in detection range only UID should be read:

PR UID1 EC UID2 EC UID3 EC

Example 3:

3 Transponder in detection range only data block should be read:

PR data1 EC data2 EC data3 EC

Example 4:

2 Transponder in detection range UID and data block should be read:

PR UID1 SC data1 EC UID2 SC data2 EC

PR: Com-Prefix (optional) ts: SCAN-LOCK-TIME

UID: Serial-Number (fix) tr: time to the next new Transponder reading

data: data blocks (free programmable)

SC Separation character (optional)

EC End character (optional)

OBID i-scan



Note:

If configuration protocols shall be sent to the Reader while the Scan Mode is active, no

Transponder should be within the detection range of the Reader during this time.

Only read operations are available with the Scan Mode.

Scan Mode is only available if Buffered Read Mode is disabled

The Scan Mode can be used with the 2.6. Reader Multiplex Mode.

OBID i-scan



2.6. Reader Multiplex Mode (Syncronisation)

To enable more than one Reader to be used in close proximity, the RF operations executed by the

Readers must be multiplexed to prevent unwanted interference.

This is achieved by using the Multiplex (Sychronisation) Mode.

In combination with Buffered Read Mode the Multiplex Mode allows maximum speed of operation. In

this case each Reader passes control to the next after it has completed its task. This is effectively a

round-robin control, but it is much faster than single host control since it is controlled at a Reader lev-

el.

To setup the Multiplex (Sychronisation) Mode a reader automatic mode must be enabled in the 4.2.

CFG1: Interface and 4.13. CFG11: Read Mode / Read Data configuration block and the Multiplex

Mode must be selected in the SYNC setting in the 4.20. CFG18: Reader Synchronisation configura-

tion block. The Reader that should trigger the multiplex chain must be configured as MASTER in the

SYNC setting in the 4.20. CFG18: Reader Synchronisation.

In the Multiplex Mode the signal input IN and the signal output OUT on connector X2 are used for

synchronization cable connections. Please refer the manual “Mounting Instructions ID

ISC.LR(M)2500” (M01111-0de-ID-B..pdf / M10210-0de-ID-B.pdf) for details.

Note:

Multiplex Mode will only be available in Buffered Read Mode, Notification Mode and Scan

Mode.

Multiplex

Reader 1

Multiplex

Reader 3

Multiplex

Reader 2

IN1 IN1 IN1 OUT1 OUT1 OUT1

OBID i-scan



3. Interface

The Reader ID ISC.LR2500 has 2 interface ports. The protocol frame of this ports can be different.

On the asynchronous serial interface the whole protocol frame is described in 3.2. Serial Data Format

and Protocol Frames. The TCP/IP protocol frame is described below.

3.1. Protocol Frames of TCP/IP protocol

If the Reader use the Ethernet Interface the data is packaged in a TCP/IP protocol frame. This means

the whole data format and protocol frame which is described in 3.2. Serial Data Format and Protocol

Frames is packaged as the data of a TCP/IP protocol frame. By using the FETCP.DLL you can easily

extract or packaging the application data you receive from the reader or you sent to the Reader.

If you use the TCP/IP protocol please be aware that the data packaged in the TCP/IP frame is trans-

ferred with Protocol frame: Advanced Protocol-Length as describe below.

LAN and WLAN sockets on the reader side uses the keepalive option for detecting interrupted con-

nections. The default parameters for keepalive are initialized as listed in the table:

Parameter Value Note

idle time 5 seconds The reader sends every 5 seconds a keepalive probe which has to be

acknowledged by the client

repeat count 2 If a keepalive probe is not acknowledged, the reader repeats the

probe only two times with an interval of 5 seconds. interval 5 second

If the 15 second time span is expired and no keepalive probe response is obtained from the client the

connection is closed and the client application must enable a new connection. The keepalive parame-

ters can be modified in the configuration pages for LAN and WLAN. This keepalive option should not

be mistake with the Keepalive message for notification mode.

OBID i-scan



3.2. Serial Data Format and Protocol Frames

The Reader ID ISC.LR2500 can be configured by different interfaces and data may be written on

Transponders or read from Transponders. The communication between Reader and connected host

(terminal, PC, etc.) is executed by means of fixed protocols. The used protocol is intended for data

bus use and is equipped with a bus address.

During data transfer via the asynchronous interface the Reader supplies the required data or a status

byte. The reply contains the transmitted control byte.

There is no reply from the Reader if there is a protocol frame failure.

Protocol frame: Standard Protocol-Length (up to 255 Byte)

Host Reader

1 2 3 4...n-2 n-1 n

LENGTH =

n COM-ADR

CONTROL-

BYTE (DATA)

LSB

CRC16

MSB

CRC16

Host Reader

1 2 3 4 (5...n-2) n-1 n

LENGTH

(n) COM-ADR

CONTROL-

BYTE STATUS (DATA)

LSB

CRC16

MSB

CRC16

Protocol frame: Advanced Protocol-Length

Reader Host

1 2 3 4 5 (6...n-2)

STX

(0x02)

MSB

ALENGTH

LSB

ALENGTH COM-ADR

CONTROL-

BYTE (DATA)

n-1 n

LSB

CRC16

MSB

CRC16

Host Reader

1 2 3 4 5 6 (7...n-2)

STX

(0x02)

MSB

ALENGTH

LSB

ALENGTH COM-ADR

CONTROL-

BYTE STATUS (DATA)

n-1 n

LSB

CRC16

MSB

CRC16

OBID i-scan



The Reader supports both Protocol frames, standard and advanced protocol frame. The Host Appli-

cation can chose which protocol frame is used. If the host application chose advanced protocol frame

the Reader will always response with advanced protocol frame. If the host application chose the

Standard Protocol frame the Reader response is depending on the length of the response. If the host

request leads to a response with more than 255Byte the Reader will chose the advanced protocol

frame as response frame otherwise the Reader response uses the standard protocol frame.

Information on:

STX:

If the responded protocol of the Reader starts with the STX sign (0x02) the protocol

frame is Advanced Protocol-Length. Then the protocol length is defined by the 2

Byte Parameter ALENGTH.

ALENGTH (n = 8...65535):

Number of protocol bytes including STX, ALENGTH and CRC16

LENGTH (n = 6...255): Standard Protocol-Length (up to 255 Byte)

Number of protocol bytes including LENGTH and CRC16.

COM-ADR:

0..254 address of device in bus mode

Note:

The Reader can be addressed via COM-ADR 255 at any time!

CONTROL-BYTE:

Defines the Command which the Reader should operate.

STATUS 1:

Includes the status message or protocol data from or to the Reader.

DATA:

Is a optional data field with variable length. The number of DATA byte depends on

the command. The data will be send always as MSB first if the Reader is in the ISO-

Host Command Mode.

CRC16:

Cyclic redundancy check of the protocol bytes from 1 to n-2, as specified by CCITT-

CRC16

Polynom: x16

+ x12

+ x5 + 1 (0x8408)

Start Value: 0xFFFF

Direction: Backward

1 see ANNEX D: Index of Status Bytes

OBID i-scan



Data format:

Start bits: 1

Data bits: 8

Stop bits: 1

Parity: even (default)

odd

none

Timing conditions:

Starting delay:

Before sending a starting sign (length byte) of a protocol, there must be a delay of

minimum 5 ms.

Host Reader: .. Reaction time Starting delay .. ..

5...n ms min. 5 ms

Host Reader: .. .. ..

Data timeout:

Within one protocol, the characters have to follow each other in intervals of maxi-

mum 12 ms.

max. 12 ms max. 12 ms max. 12 ms

Host Reader: Char n Char n+1 Char n+2 ..

CRC16 Calculation Algorithm

Polynom: x16

+ x12

+ x5 + 1 CRC_POLYNOM = 0x8408;

Start Value: 0xFFFF CRC_PRESET = 0xFFFF;

C-Example:

unsigned int crc = CRC_PRESET;

for (i = 0; i < cnt; i++) /* cnt = number of protocol bytes without CRC */

{

crc ^= DATA[i];

for (j = 0; j < 8; j++)

{

if (crc & 0x0001)

crc = (crc >> 1) ^ CRC_POLYNOM;

else

crc = (crc >> 1);

}

}

OBID i-scan



3.3. Interface data encryption (Only ID ISC.LR(M)2500-A)

The ID ISC.LR2500-A / ID ISC.LRM2500-A readers can secure the data transmission over Ethernet

(TCP/IP) with the 128 / 192 / 256 bit AES algorithm. The Authentication Key (Password) is stored in

the Reader and cannot read back. The crypto mode is disabled by default.

The encrypted data transmission will be enabled by activating the crypto mode in the Reader configu-

ration with a following CPU-Reset. After that, the Reader accepts only enciphered protocols. To get

access rights in crypto mode, the first command must be an authentication command 6.14. [0xAE]

Reader Authent, transporting the enciphered password (password contains only nulls by default), to

open a new session. Every successive protocol will then enciphered automatically. After the first au-

thentication a new password should be saved in the Reader and a new authentication with the new

password should be executed. This procedure – to switch into the crypto mode first and to change the

password secondly – ensures that the new password will be transmitted enciphered! Otherwise the

new password will be transmitted plain.

Notes:

- A Reader with activated crypto mode ignores all plain protocols and returns the status

0x19 (Crypto Processing Error).

- A Reader in plain mode ignores all enciphered protocols and returns the status 0x82

(Command not available). An authentication into the Reader with a false password will be

returned with status 0x12 (Authent Error).

- A Reader with activated crypto mode signals with status 0x19 (Crypto Processing Error) an

error case in the enciphered transmission. The Host must execute an authentication into

the Reader again.

OBID i-scan



4. Configuration Parameters (CFG)

The configuration memory of the Reader is organized in configuration blocks of 16 byte each. These

are divided into 14 byte configuration parameters and a 2 byte CRC16 checksum. Each of these con-

figuration blocks takes a number (CFG 0...CFG n).

Structure of a configuration blocks in Reader configuration memory and Reader EEPROM (CFG):

Byte 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Contents PARAMETER CRC16

The parameters are stored in two different configuration memory locations:

Reader RAM

Backup EEPROM (used for storing parameter over power down)

Multiple configuration memory locations can be addressed by the value of the parameter CFG-ADR

used in chapter 5. Protocols for Reader Configuration

CFG-ADR:

CFGn: memory-address of the required configuration block

LOC: specifies the location of the configuration block (RAM / EEPROM)

MODE: specifies one or all configuration blocks

Bit: 7 6 5 4 3 2 1 0

Function LOC MODE CFGn: address of configuration block

The EEPROM configuration blocks are protected by a 16 bit CRC-checksum. The examination of

these checksums is executed after each reset of the Reader. If an checksum is found, the Reader

goes into an error status "EE-Init-Mode" and sets the configuration block which is faulty to the default-

values.

While the EE-Init-Mode is active, the LED blinks alternately red and green and the Reader answers

external commands with the status "0x10 EEPROM Failure". The "EE-Init-Mode" can be exited now

by a new reset (cold start or 6.4. [0x64] System Reset command). If after this the checksums of all

data records are correct, the Reader shifts to the configured operation mode.

Notes:

Malfunctions may occur if parameters are configured without their described range or if

unspecified parameters have been changed!

A firmware update resets the EEPROM to default settings and the Reader goes into the

error status “EE-Init-mode”.

OBID i-scan



Structure of configuration parameter description.

Byte 0 1 2 ......n

contents RAM-eff. EEPROM-

eff.

00

res

.....

not marked

Changing of this parame-

ter becomes immediately

effective after writing /

saving this configuration

block to RAM

marked with “00“

these bits or bytes are reserved for

future extensions or for internal

testing and manufacturing-

functions. These bits or bytes and

also any not described bits and

bytes must not be changed, as

this may cause faulty operation of

the Reader.

gray marked

Changing of this parame-

ter only becomes effective

after writing / saving this

configuration block to

EEPROM and a Reader

reset

OBID i-scan



4.1. CFG0: Passwords

The parameters of the CFG0 configuration block contain the identification codes to personalize the

Reader for a user to prevent outside access to some features of the Reader. For security reasons

data from this configuration block cannot be read from the host, they are “write-only”. Also the com-

mand 5.3. [0x83] Set Default Configuration isn‟t available for this configuration block.

Byte 0 1 2 3 4 5 6

Contents READER-ID 0x00 0x00 0x00

Default 0x00000000

Byte 7 8 9 10 11 12 13

Contents 0x00 CFG_ACCESS 0x00 0x00

Default

READER-ID: (AccessProtection.Password)

Defines the password with which the host logs into the Reader for a read / write access to

the configuration parameter blocks.

CFG_ACCESS: (AccessProtection.Lock_CFGx)

Defines the Configuration blocks which are accessible only if the user has had a successful

login to the Reader.

Byte: 8 9

Bit: 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8

CFG No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Byte: 10 11

Bit: 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8

CFG_NO. 16 17 18 19 20 21 22-

29

30-

39

64-

84

- - -63 - - - - 0

CFG_NO

The Bit in CFG_NO defines if the access to the configuration block is free or if the

use should login to the Reader to get access to the configuration block.

b0 Access if free

b1 Access need a login

OBID i-scan



To change the READER-ID you must write to the CFG0 immediately after the Login to the Reader

with the command 6.13. [0xA0] Reader-Login

Notes:

A READER-ID = 0x00000000 disables the password function.

A read with the command 5.1. [0x80] Read Configuration will always get

„0x00000000‟.

A changed password becomes valid after a Reader reset.

The command 5.3. [0x83] Set Default Configuration doesn‟t change the CFG0 regis-

ter if all configuration blocks are used.

The command 6.13. [0xA0] Reader-Login is used to enable configuration data

access.

It is possible to disable the READER-ID with an activation code, if the READER-ID is

unknown. The activation code must be ordered by your supplier or FEIG Electronic

GmbH.

Config Protection

By means of Config Protection, the access to the configuration parameters stored within the Reader

is protected by a 32-bit password, the "READER-ID". This means that only after a "Login" with a valid

READER-ID with the command 6.13. [0xA0] Reader-Login can configuration parameters in the

EEPROM of the Reader may be read and changed in the EEPROM of the Reader.

OBID i-scan



4.2. CFG1: Interface

The parameters of the CFG1 configuration block contains the data communication settings.

Byte 0 1 2 3 4 5 6

Contents COM-ADR 0x00 BAUD1 TRANS-

FORM1

0x00

0x00 TR-

RESPONSE-

TIME

Default 0x00 0x08 0x01 0x00

0x00 38400 Baud e,8,1

Byte 7 8 9 10 11 12 13

Contents TR-

RESPONSE-

TIME

0x00 0x00 SCAN-

INTERFACE

INTERFACE READER -

MODE

Default 0xF0 0x00 0x05 0x00

1,2 sec.

COM-ADR: (HostInterface.Serial.BusAddress)

Bus address of the Reader (0 .. 254) for communication via the asynchronous interface, es-

pecially for applications with the RS485 interface.

Notes:

Do not configure address 255!

Via the COM-Adr 255 in the send protocol, the Reader is able to be addressed at any

time. It answers then with the configured address.

1 A reasonableness check is performed by writing this parameter to the Reader. If an error occurs the Reader answers with STATUS = 0x11.

OBID i-scan



BAUD1: (HostInterface.Serial.Baudrate)

By means of this byte the baud rate of the asynchronous interface can be defined.

0x05: 4800 baud

0x06: 9600 baud

0x07: 19200 baud

0x08: 38400 baud

0x09: 57600 baud

0x0A: 115200 baud

Note:

Changing of BAUD only becomes effective after writing / saving configuration

block CFG1 to EEPROM and a reset of the Reader.

The Reader sets the baud rate to 38400 baud, if the user sets an invalid baudrate.

TRANS-FORM1: (HostInterface.Serial...)

By means of this byte, several parameters for the data transmission format of the asyn-

chronous interface can be defined.

Bit: 7 6 5 4 3 2 1 0

Function: 0 0 0 0 S D P

P: (HostInterface.Serial.Parity)

Kind of Parity

b00: non Parity

b01: even Parity

b10: odd Parity

b11: - do not use -

D: (HostInterface.Serial.Databits)

Number of Data Bits

b0: 8 Data Bits

b1: - do not use -

S: (HostInterface.Serial.Stopbits)

Number of Stop Bits

b0: 1 Stop Bit

b1: - do not use –


OBID i-scan



Note:

Changing of TRANS-FORM only becomes effective after writing / saving configura-

tion block CFG1 to EEPROM and reset of the Reader.

Always 8 Data Bits and 1 Stop Bits should be used

TR-RESPONSE-TIME: (AirInterface.TimeLimit)

By means of this parameter the maximum duration for the Transponder command can be de-

fined.

The TR-RESPONSE-TIME starts after the Reader has received a new command. At the lat-

est after the TR-RESPONSE-TIME elapsed the Reader will send an answer protocol. In this

case, the current commands between Reader and Transponder are aborted. If this time is to

short the Interface Status “ 0x83 RF Communication Error“ will appear.

max. response duration

TR-RESPONSE-TIME 0...65535 * 5 ms

Note:

TR-RESPONSE-TIME has no effect with the protocols for Reader Configuration and the

protocols for Reader Control.

The TR-RESPONSE Time must be < “Block Timeout” in the Host COM-Port settings.

SCAN-INTERFACE: (OperatingMode.ScanMode.Interface)

Selection of the communication port for Scan-Mode

Bit: 7 6 5 4 3 2 1 0

Function: - - DC Format IF-NO

IF-NO: Interface Number

b000: RS232

b001: RS485

b010: USB

b011: Data/Clock

b1xx: - do not use -

Note:

The USB interface in Scan Mode works like a Human Interface Device (HID).

The digital Outputs 1/2 can be used for Data Clock interface. The “Clock” signal is pro-

vided on Output1 and the “Data” is provided on Output2.

OBID i-scan



4.3. Wiegand and Magnetic Stripe description

DC-FORMAT:

By means of this parameter the kind of data transmission via data-/clock interface could be selected:

b000: Wiegand emulation; data format: binary 1:1, according written to Transponder.

b001: magnetic stripe; data format: binary 1:1, according written to Transponder.

b010: magnetic stripe; data format: according ISO 7811-2, track 2+3 (5 Bit)

b011: magnetic stripe; data format: according ISO 7811-2, track 1 (7 Bit)

b100: Wiegand emulation; data format: Wiegand formatted protocol frame with start and stop sign.

b101: magnetic stripe; data format: according ISO 7811-2, track 2+3 (5 Bit)

additional a prefix of 16 leading zero clocks before the start character and

additional a trailer of 16 attached zero clocks following to the LRC character.

b110: Wiegand emulation; data format: Wiegand formatted protocol frame

Note:

The data-clock interface is only available in Scan Mode.

With the data-clock interface the length of the data is interpreted as Bit.

There will be a break of 100ms between two following data sets.

OBID i-scan



4.3.1. Magnetic Strip Emulation

Data Format:

The following table shows data coding depending on DC-FORMAT

For cutting the length of data output the parameters D_LGT and D_START can be used

(see: 4.13. CFG11: Read Mode / Read Data)

DC-FORMAT b001 b010

b101

b011

binary 1:1 according

ISO 7811-2

(5 bit)

according

ISO 7811-2

(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

OBID i-scan



Example: Output of raw data 0x19BF

Sign

DC-FORMAT

prefix

(16*0)

Start

%

0x1

0x9

0xB

0xF

Stop

?

LRC

trailer

(16*0)

b001 - - 0001 1001 1011 1111 - - -

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

b101 000...000 1101/0 1000/0 1001/1 1101/0 1111/1 1111/1 0001/0 000...000

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

Time

LRC:

XOR operation on Start-, Data and Stop-sign

Timing:

The following diagram represents the signal response of the 3 data lines of the data-/clock-

interface in magnetic strip emulation.

tn = 0,5 ms

ta(n) tn / 3

tb(n) tn / 2

OBID i-scan



4.3.2. Wiegand Emulation

Data Format:

The following description represents the data coding depending on DC-FORMAT

DC-FORMAT = b000 binary 1:1

In this configuration the output data format is equal to the data coding on the Transponder. The

Reader doesn't add a protocol frame e.g. parity Bits or start or stop signs across the data

stream.

DC-FORMAT = b100 Wiegand formatted protocol frame with start and stop sign

In this configuration the Reader build the protocol frame with one even parity bit at the beginning

and one odd parity bit at the end and one start and one stop sign:

4 Bit 1 Bit n Bit 1 Bit 4 Bit

START EVEN DATA ODD STOP

START: b1011

EVEN: Even parity bit calculated across the first half DATA bits.

DATA: Data bits as read from the Transponder and defined in scan-mode settings.

ODD: Odd parity bit calculated across the last half DATA bits.

STOP: b1111

DC-FORMAT = b110 Wiegand formatted protocol frame

In this configuration the Reader build the protocol frame with one even parity bit at the beginning

and one odd parity bit at the end

1 Bit n Bit 1 Bit

EVEN DATA ODD

EVEN: Even parity bit calculated across the first half DATA bits.

DATA: Data bits as read from the Transponder and defined in scan-mode settings.

ODD: Odd parity bit calculated across the last half DATA bits.

OBID i-scan



Example of parity calculation

Example 1: 18 DATA bit

DATA bin 011110110010110101101001

OUTPUT 1 011110110010110101101001 0

`- Even Parity Bit `- Odd Parity Bit

Example 1: 19 DATA bit DATA bin 0111101100101101011010011

OUTPUT 0 0111101100101101011010011 1

`- Even Parity Bit `- Odd Parity Bit

Timing

The following diagram represents the signal response of the 3 data lines of the data-/clock-

interface in Wiegand emulation.

tn = 0,5 ms

OBID i-scan



INTERFACE: (HostInterface.Interfaces)

Flags for enabling the communication ports

Bit: 7 6 5 4 3 2 1 0

Function: - - - USB - LAN RS4xx RS232

RS232: b0: disable

b1: enable

RS4xx: b0: disable

b1: enable

LAN: b0: disable

b1: enable

USB: b0: disable

b1: enable

WLAN: b0: disable (only available with ID ISC.LR(M)2500-A)

b1: enable

Note:

If the Gate People Counter is connected with the RS485 interface the RS485 interface

can be not used for host communication.

OBID i-scan



READER-MODE: (OperatingMode.Mode)

By means of this byte, the Reader mode can be defined.

Bit: 7 6 5 4 3 2 1 0

Function: BRM-E NF-E 0 0 0 0 0 SCAN-E

SCAN-E:

By setting of this bit the Scan-Mode can be enabled

b0: Host Mode (see chapter 7. Protocols for ISO15693 Host Commands)

b1: Scan Mode

BRM-E:

By setting of this bit the Buffered Read Mode can be enabled

b0: Host Mode or Scan Mode

b1: BRM-Mode

NF-E:

By setting of this bit the Notification Mode can be enabled

b0: Off

b1: On (only together with BRM-Mode)

The following table lists the bit combinations for the reader modes:

Bit

7 6 5 4 3 2 1 0

Rea

de

r M

od

e Host-Mode 0 0 0 0 0 0 0 0

Scan Mode 0 0 0 0 0 0 0 1

Buffered Read

Mode 1 0 0 0 0 0 0 0

Notification Mode 1 1 0 0 0 0 0 0

OBID i-scan



4.4. CFG2: Inputs/Outputs I

The parameters of the CFG2 configuration block contains the digital-input and -output settings.

Byte 0 1 2 3 4 5 6

Contents IDLE-MODE FLASH-IDLE IN-ACTIVE OUT2-TIME REL1-TIME

Default 0x88A8 0xCC00 0x00 0x00

Byte 7 8 9 10 11 12 13

Contents REL1-TIME OUT1-TIME REL2-TIME REL3-TIME 0

Default 0x00 0x0000 0x0000 0x0000

IDLE-MODE: (DigitalIO.Output.No1.IdleMode), (DigitalIO.Relay.Nox.IdleMode)

Defines the status of the signal emitters (OUT1 and RELx) during the idle mode.

Bit: 15 14 13 12 11 10 9 8

Function: REL1 mode OUT2 mode OUT1 mode 0 0

7 6 5 4 3 2 1 0

REL2 mode REL3 mode 0 0 0 0

Mode Function

b 0 0 UNCHANGED no effect on the status of the signal emitter

b 0 1 ON signal emitter on

b 1 0 OFF signal emitter off

b 1 1 FLASH signal emitter alternating on

FLASH-IDLE: (DigitalIO.Output.No1.IdleFlashMode), (DigitalIO.Relay.Nox.IdleFlashMode)

Allocates its own flashing-frequency to each output.

Bit: 15 14 13 12 11 10 9 8

Function: REL1 frq OUT2 frq OUT1 frq 0 0

7 6 5 4 3 2 1 0

REL2 frq REL3 frq 0 0 0 0

Bit combination flashing frequency

b 1 1

b 1 0

b 0 1

b 0 0

1 Hz

2 Hz

4 Hz

8 Hz

OBID i-scan



IN-ACTIVE: (DigitalIO.Input.Nox.Mode)

Determines if the input is active with the closed or open contact:

Bit: 7 6 5 4 3 2 1 0

Function 0 0 0 0 0 IN3 IN2 IN1

Bit = 0 closed contact activates input

Bit = 1 open contact activates input

OUT2-TIME : (DigitalIO.Output.No2.SettlingTime)

Defines the holding time of the digital output OUT2. If the Reader receives a valid Trans-

ponder response the antenna assigned to the Relay by 4.11. CFG9: Input / Output II (As-

signment – output to antenna read event) is activated for the value in RELx-TIME.

If RELx-TIME is zero the function is disabled.

If RELx is high in idle mode, RELx will low for RELx-TIME.

If the flash mode is enabled, the output goes low.

Range: 0x00 ... 0xFF ( * 100ms) = 0s ... 25,6s.

OUT1-TIME and RELx-TIME (x=1, 2) : (DigitalIO.Output.No1.SettlingTime),

(DigitalIO.Relay.Nox.SettlingTime)

Defines the holding time of the digital output OUT1 / RELx. If the Reader receives a valid

Transponder response the antenna assigned to the output by 4.11. CFG9: Input / Output II

(Assignment – output to antenna read event) is activated for the value in OUT1 / RELx -

TIME.

If OUT1 / RELx -TIME is zero the function is disabled.

If OUT1 / RELx is high in idle mode, OUT1 / RELx will low for OUT1 / RELx -TIME.


Range: 0x0000 ... 0xFFFF ( * 100ms) = 0s ... 6553,5s.

RELx-TIME (x=3) : (DigitalIO.Relay.No3.SettlingTime)

Defines the holding time of the digital output RELx. If the Reader receives a valid Trans-

ponder response the antenna assigned to the Relay by 4.11. CFG9: Input / Output II (As-

signment – output to antenna read event) is activated for the value in RELx-TIME.

If RELx-TIME is zero the function is disabled.

If RELx is high in idle mode, RELx will low for RELx-TIME.


Range: 0x00 ... 0xFF ( * 100ms) = 0s ... 25,6s.

Note:

BRM-mode (reading of serial number and data):

if the serial number was read OK and the data not, no data set will be transferred, but the

assigned RELx and / or the OUTx will be active.

If the OUT1 and OUT2 is used for the Data Clock Interface the settings for OUT1 and OUT2

will be ignored.

OBID i-scan



4.4.1. Dedicated Input / Output Functions

IN1 is reserved for the trigger, if the trigger is enabled in 4.12. CFG10: Trigger

The LED‟s are used for system monitoring.

LED Color Dedicated Function

1 green 1. 1 second blink.

2. Alternately blink with LED2 after an EEPROM error.

2 blue

1. The RF interface has an faultless communication with a Trans-

ponder.

2. Alternately blink with LED1 after an EEPROM error.

3 yellow The interface sends data to the host or Application and communica-

tion Board.

4 yellow res.

5 red

1. The Reader is initializing after power up or a 6.3. [0x63] RF

Controller Reset command.

RF-Warning:

- mismatch of the antenna tuning

- See chapter 6.9. [0x6E] Reader Diagnostic for details.

Notes:

LED1 (green) and LED2 (blue) are blinking alternately if a read error of the EEPROM oc-

curred after power-up or a 6.3. [0x63] RF Controller Reset command. A Firmware update

sets the EEPROM to initial state and the LED1 and LED2 are also blinking alternately.

OBID i-scan



4.5. CFG3: RF-Interface

The parameters of the CFG3 configuration block contain global Transponder drivers and Reader set-

tings.

Byte 0 1 2 3 4 5 6

Contents TAG-DRV1 RF-POWER

1 EAS-LEVEL 0x00 0x00 0x00

Default 0x0009

0x04 0x80

Byte 7 8 9 10 11 12 13

Contents 0x00 0x00 0x00 0x00 0x00 0x00 FU_COM

Default 0x01

TAG-DRV1: (Transponder.Driver.HF.Drivers.)

Defines the Transponder types that are operated by the Reader.

Byte: 0 1

Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Driver 0 0 0 0 0 0 0 0 0 0 0 0 .D 0 0 .A

b0 Driver for the Transponder type is inactive

b1 Driver for the Transponder type is active

.A: (Transponder.Driver.HF.ICode1)

Driver for I-Code 1

.D: (Transponder.Driver.HF.ISO_15693)

Driver for ISO15693

In principle, only those Transponder drivers should be active that are used in the ac-

tual application. Thus, the reaction time of the Reader for Transponder read- / write-

operations is reduced and the danger of a parasitic Transponder access is mini-

mized.

1 A reasonableness check is performed by writing this parameter to the Reader. If an error occurs the Reader answers with STATUS = [0x11].

OBID i-scan



RF-POWER1: (AirInterface.Antenna.HF.No1.OutputPower)

Defines the RF output power.

Bit: 7 6 5 4 3 2 1 0

Function MUL LEVEL

MUL

Selects the multiplier for LEVEL

b0 RF-POWER = LEVEL * 1W

b1 RF-POWER = LEVEL * ¼W

LEVEL

Level of the RF output power, range: (2Watt – 12Watt and Low Power)

LEVEL RF-POWER (MUL = b1)

04 Low Power

08 2.00W

09 2,25 W

10 2,50 W

... ...

39 11,50 W

40 11,75 W

48 12,00 W

Notes:

A monitor is continuously checking the RF hardware and if an error occurs the

Reader answers every command with the error code 0x84.

Changing of RF-POWER only becomes effective after writing / saving configuration

block CFG3 to EEPROM and a reset of the Reader

EAS-LEVEL: (Transponder.HF.ICode1.Miscellaneous.EASLevel)

(only I-Code 1 Transponders and I-Code SLI (ISO15693))

Defines the number of correct bits received during a EAS command.

Range (0x10...0xFF)

FU-COM: (AirInterface.Antenna.HF.Miscellaneous.Enable_...)

Defines if the Reader is allowed to control functional unit via the RF Line.

Bit: 7 6 5 4 3 2 1 0

Function DC 0 0 0 0 0 0 STune

STune (AirInterface.Antenna.HF.Miscellaneous.Enable_PowerUpTuning)

defines whether the Reader tunes the antenna connected to the Reader after the

1 A plausibility check is performed by writing this parameter to the Reader. If an error occurs the Reader answers with STATUS = [0x11].

OBID i-scan



Reader power up. This option works only if a ID ISC.DAT is integrated in the anten-

na connected to the Reader and if the ID ISC.DAT has DC power.

b0 disabled

b1 enabled

DC (AirInterface.Antenna.HF.Miscellaneous.Enable_DCPower)

defines whether the Reader supplies DC voltage on the RF line to supply Function

Units in the RF line with DC power.

b0 DC voltage OFF

b1 DC voltage ON

OBID i-scan



4.6. CFG4: Transponder Parameters

The parameters of the CFG4 configuration block contain general Transponder settings.

Byte 0 1 2 3 4 5 6

Contents ICODE-

MODE FAM-CODE APP-ID 0x00

ISO 15693

MODE

ISO 15693

AFI1

ISO15693

OPTION

Default 0x00 0x00 0x00 0x0B 0x00 0x00

Byte 7 8 9 10 11 12 13

Contents ISO-CMD-

OPTION

ISO 15693

AFI2

ISO 15693

AFI3

ISO 15693

AFI4 0x00 0x00

ISO-

Blocksize

Default 0x03 0x00 0x00 0x00 0x04

ICODE-MODE: (only I-Code 1 Transponders)

Bit: 7 6 5 4 3 2 1 0

Function 0 0 0 0 0 0 0 FAST

FAST (Transponder.HF.ICode1.LinkRate.FastMode)

b0: Normal Mode (1 / 256)

b1 Fast Mode (1 / 1)

FAM-CODE: (only I-Code 1 Transponders) (Transponder.HF.ICode1.SelectionMask.FamilyCode)

Family Code to select a Transponder

APP-ID: (only I-Code 1 Transponders) (Transpond-

er.HF.ICode1.SelectionMask.ApplicationIdentifier)

Application ID to select a Transponder

Note:

If FAM-CODE and APP-ID are zero, all I-Code 1 Transponders will respond.

Otherwise only the Transponders with matching FAM-CODE and APP-ID will respond.

ISO 15693 MODE:

Bit: 7 6 5 4 3 2 1 0

Function 0 0 AFI NO-TS DATA-

RATE

SUB-

CARRIER

MOD DATA

CODING

DATACODING (Transponder.HF.ISO_15693.LinkRate.DataCoding)

b0 1 out of 256

b1 Fast Mode (1 / 4)

MOD

b0 - do not use -

b1 10% (the modulation depth in the setting in 4.22. CFG20: RF-Parameter)

are used

OBID i-scan



SUB-CARRIER

b0 ASK (one sub-carrier)

b1 - do not use -

DATA-RATE

b0 - do not use -

b1 high

NO-TS (Transponder.HF.ISO_15693.Anticollision.NoOfTimeslots)

b0 16 timeslots

b1 1 timeslot

AFI (Transponder.HF.ISO_15693.SelectionMask.Enable_AFI)

b0 Disabled

b1 Enabled

ISO 15693 AFI1: (Transponder.HF.ISO_15693.SelectionMask.AFI1)

First Application Family Identifier to select a Transponder

ISO 15693 OPTION:

Bit: 7 6 5 4 3 2 1 0

Function 0 0 0 0 WR-OPTION 0 0

WR-OPTION: (Transponder.HF.ISO_15693.Miscellaneous.WriteOption)

b00: automatically set

b10: Tag Option = 0

b11: Tag Option = 1

Note:

If WR-OPTION is automatically set, the Reader sets the WR-OPTION to 0, if the ISO15693

Host Command is in non-addressed mode

ISO-CMD-OPTION: (only ISO15693 Transponder driver)

Bit: 7 6 5 4 3 2 1 0

Function 0 0 0 0 0 0 BREAK

BREAK (Transponder.HF.ISO_15693.Miscellaneous.CommandBreak)

b10 break timeslot at “NO Transponder” Break is always 100% modulated EOF

This option speeds up the anticollision process, but increases

modulation band width

b11 Complete timeslot length at “NO Transponder”

OBID i-scan




Second Application Family Identifier to select a Transponder


Third Application Family Identifier to select a Transponder


Third Application Family Identifier to select a Transponder

Note:

If the AFI2/3/4 is different to 0x00 a second and a third or fourth Inventory with differ-

ent AFI-Bytes will be performed.

ISO-Blocksize:

Bit: 7 6 5 4 3 2 1 0

Function Read Mode Blocksize DB-Blocksize

DB-Blocksize: (Transponder.HF.ISO_15693.Miscellaneous.ReadOption.BlockSize)

Defines the block size of an ISO-transponder which is not listed in the MFR-table

(see: 7.3. Supported ISO15693 Host commands for ISO15693 Transponders) or if

the transponder is used in the non-addressed mode.

Range: 0x01 ... 0x1F

A value of 0x00 will be automatically set to a block size of 4byte.

Blocksize:

(Transponder.HF.ISO_15693.Miscellaneous.ReadOption.BlockSizeSelection)

b0: Automatic (If transponder is known)

b1: Manuel (As specified in DB-Blocksize)

Read Mode: (Transponder.HF.ISO_15693.Miscellaneous.ReadOption.ReadMode)

b00: Automatic Mode (If transponder is known)

b01 Single Read

b10 Multiple Read

OBID i-scan



4.7. CFG5: Anticollision

The parameters of the CFG5 configuration block contain anticollision settings.

Byte 0 1 2 3 4 5 6

Contents TIMESLOTS1 0x00 0x00 0x00 0x00 0x00 0x00

Default 0x30

Byte 7 8 9 10 11 12 13

Contents 0x00 0x00 0x00 Session ONT 0x00 0x00

Default 0x05

TIMESLOTS1: (only I-Code 1)

Number of timeslots with which Transponders will be read.

Bit: 7 6 5 4 3 2 1 0

Function MAX-TS MIN-TS

MIN-TS: (Transponder.HF.ICode1.Anticollision.MinimalTimeslots)

Minimum number of timeslots.

MAX-TS: (Transponder.HF.ICode1.Anticollision.MaximalTimeslots)

Maximum number of timeslots.

MIN-TS / MAX-TS Number of Timeslots

b0101

b0100

b0011

b0010

b0001

b0000

64

32

16

8

4

1

The I-Code 1 can be used with maximum 64Timeslots.

Choosing too many timeslots compared to the number of Transponders in the antenna field

means that only a small number of Transponders can be selected at one time. On the other

hand too many timeslots is very time consuming. The optimum number of timeslots is about

twice the number of Transponders expected in the antenna field at the same time.

The Reader calculates the expected number of Transponders and sets the corresponding

number of timeslots between MIN-TS and MAX-TS. To set up a fixed timeslot, both MIN-TS and

MAX-TS must contain the value of the desired timeslot.


OBID i-scan



ONT:

Defines which Transponder will sent to the host.

Bit: 7 6 5 4 3 2 1 0

Function 0 0 0 0 0 ACOLL 0 1

ACOLL: (Transponder.Anticollision.Enable)

This bit activates the Anticollision Mode. In Anticollision Mode the Reader automati-

cally sets Transponder specific communication parameters.

b0: disabled

In this case the Reader doesn‟t processes any anticollision procedure with

the Transponders inside the antenna field.

b1: enabled (default)

In this case the Reader processes the anticollision procedure with the

Transponders inside of the antenna field.

OBID i-scan



4.8. CFG6: Customer Command Option Bytes

Byte 0 1 2 3 4 5 6

Contents 0x00 EM FUJITSU Infineon KSW 0x00 NXP

Default 0x00 0x00 0x00 0x00 0x00 0x00

Byte 7 8 9 10 11 12 13

Contents ST 0x00 TI 0x

system-manual id isc.lr2000...manual preliminary public (b) 2011-04-21 h01112-0e-id-b.docx id...

Documents