RTS200 RFID Test Set - RFID Webshop

TAGnology RFID GmbH | Grazer Vorstadt 142 | 8570 Voitsberg | AUSTRIA 

phone: +43 (0)3142/ 28 9 28-10 | fax: +43 (0)3142/28 9 28-20 | office@tagnology.com | www.tagnology.com 

RTS200 RFID Test Set 

User´s Guide 

IBERWAVE 

©2009 TAGnology RFID GmbH; reserves the right to change specification without notice at any time 

>> 

your premium RFID-partner

Document Info 

DOCUMENT NAME 

DESCRIPTION 

FILE NAME 

RTS200 RFID Test Set 

RTS100 Software description. USER MODE Program Version 3.0 and later. 

RTS200 user guide.odt 

CODE 001.0036 

VERSION 1 

STATUS 

Draft 

CREATED BY JCPM DATE 9/1/07 

APROVED BY 

DATE 

HISTORY Version 1.0 Original version

T a b le of Contents 

1 INTRODUCTION..................................................................................................................................................................... 4 

1.1 Version 3.0 new features.................................................................................................................................................. 4 

2 GETTING STARTED.............................................................................................................................................................. 5 

2.1 Software Setup................................................................................................................................................................. 5 

2.2 USB Installation................................................................................................................................................................ 5 

2.2.1 Hardware Connection................................................................................................................................................. 5 

2.2.2 Driver Installation........................................................................................................................................................ 5 

2.2.3 Software Configuration............................................................................................................................................... 7 

2.2.4 Communication Verification........................................................................................................................................ 7 

2.3 Ethernet Installation.......................................................................................................................................................... 7 

2.3.1 Hardware Connection ................................................................................................................................................ 7 

2.3.2 IP Address / Port......................................................................................................................................................... 7 

2.3.3 Ping............................................................................................................................................................................. 7 

2.3.4 Deviceinstaller............................................................................................................................................................ 8 

2.3.5 Software Configuration............................................................................................................................................. 10 

2.4 Configuration................................................................................................................................................................... 11 

2.4.1 Opening a New Form................................................................................................................................................ 11 

2.4.2 Selecting the Communication Interface ................................................................................................................... 12 

2.4.3 Configuring the System............................................................................................................................................ 12 

3 MENU OPTIONS.................................................................................................................................................................. 13 

3.1 Context Sensitive Menu.................................................................................................................................................. 13 

3.2 Window Main Menu........................................................................................................................................................ 13 

3.2.1 Firmware update....................................................................................................................................................... 13 

3.2.2 Global Test Options.................................................................................................................................................. 14 

4 TAG ANALYSIS.................................................................................................................................................................... 17 

4.1 Tag Analyzer Screen...................................................................................................................................................... 17 

4.1.1 Display Section......................................................................................................................................................... 18 

4.1.2 Chart Options Menu.................................................................................................................................................. 20 

4.1.3 Results Section......................................................................................................................................................... 20 

4.1.4 Control Section......................................................................................................................................................... 22 

4.1.5 File formats............................................................................................................................................................... 23 

5 TEST SETUP........................................................................................................................................................................ 24 

5.1 Test types....................................................................................................................................................................... 26 

5.2 Test Arrangement........................................................................................................................................................... 26 

5.3 Machine Interface Configuration..................................................................................................................................... 27 

6 ONLINE TEST SCREEN....................................................................................................................................................... 28 

6.1 Control Section............................................................................................................................................................... 28 

6.1.1 Yield Section............................................................................................................................................................. 29 

6.1.2 Statistical Information Section.................................................................................................................................. 29 

6.1.3 Test Result Section................................................................................................................................................... 30 

6.1.4 report Section........................................................................................................................................................... 30 

6.1.5 Generated files......................................................................................................................................................... 31 

ANNEX 1 TEST REPORT FILE FORMAT............................................................................................................................... 32 

ANNEX 2 TEST PROPERTIES............................................................................................................................................... 33 

Annex 2.1 Write Format Definition......................................................................................................................................... 35 

ANNEX 3 ERROR CODES...................................................................................................................................................... 36 

Pag: 3 Document: RTS200 RFID Test Set Code: 001.0036 Version: 1

1 Intr o d uction 

The RTS200 is the evolution of the RTS100 RFID Test Set. It includes new features, as USB 

interface, higher RF power, improved receiver sensitivity, and UHF resonant frequency 

measurement. 

The controlling application, running under Windows © , includes system configuration, test setup, 

test suite automation, report generation, or graphical display of tag characteristics in time and 

frequency domains. 

1 .1 Ve rsion 3.0 new features 

The description in this document applies to software versions 3.0 and later. Some new features 

have been included: 

● 

● 

● 

● 

● 

● 

● 

● 

Improved report generation (see description in section Chart Options Menu) 

Improved Q factor determination (more stable and robust) 

USB support 

Printing and export of graphical information 

Improvement in communication (more robust) 

Debugging of identified problems in previous versions 

Change in installation folder (now under standard PROGRAM FILES folder) 

PDF documentation accessible from HELP menu option 


2 Getting Star t e d 

2 .1 Softw a re Setup 

To install the system in your computer, run the setup file provided. 

The files are installed into the windows PROGRAM FILES/IBW_RTS folder. The main files 

installed are: 

FILE TYPE COMMENT 

RTS100 DEV Application This is the main application program 

RTS100 USER Application Application for user mode with simplified user interface to be used in production line 

LOADER .H86 Loader file for RTS200 firmware updates 

* .PRO Several project files (.PRO) containing application and communication configuration 

information. There are project files for USB, Ethernet, RS232, ... This file also contains the 

test suite to be loaded when running the application. 

VERSION Text file Version information 

SofRFIDProtM .DLL Windows library implementing the communication protocol 

RTS100 .INI Contains the name of the .PRO file to be loaded at startup 

/TEST_DATA Folder Default directory for report generation 

/TEST_SETUP Folder Default directory containing pre-defined tests (.TST) and test suites (.TSU) files. 

/RTS_FIRM Folder Contains RTS200 firmware versions 

/TEST_SETUP/ 

RTS100 

.CFG 

Configuration file for RF characteristics of the RTS model, antenna models and calibration 

constants 

2 .2 USB Installation 

The new RTS200 is equipped with an USB interface (this is the default interface after the 

application is installed). The CD-ROM contains the required drivers. With the provided drivers, the 

device will be installed as a serial COM port under Windows. 

2.2.1 Hardware Connection 

Use a standard USB cable (as the one supplied with the RTS200 kit) to make the connection 

between the Host running the application and the RTS200. Once installed, it is convenient to 

connect the RTS200 always in the same computer USB port, so there is no need to reinstall the 

USB drivers. 

2.2.2 Driver Installation 

FTDI’s CDM drivers provide both D2XX (direct drivers) and VCP (virtual port) functionality through 

a single driver on PCs running the following Windows operating systems: 

• Windows 2000 

• Windows XP 

• Windows Server 2003 

The files included in a standard 32-bit CDM release are: 

• Installation files 

 

FTDIBUS.INF 


FTDIPORT.INF 

• Driver files 

FTDIBUS.SYS 

FTSER2K.SYS 

• Uninstaller 

FTDIUNIN.EXE 

FTDIUN2K.INI 

• D2XX Interface 

FTD2XX.DLL 

FTD2XX.LIB 

FTD2XX.H 

For latest driver versions, please, consult the manufacturer web page: 

http://www.ftdichip.com/FTDrivers.htm 

The driver installation procedure consists of the following steps: 

a.- 

Connect the RTS200 through the USB serial port to the computer 

b1.- If windows recognizes the new hardware, a message will appear with a text similar to “your 

new hardware is ready to be used”. 

b2.- If windows does not recognize the device, it will ask for a driver. You´ll have to select the 

Driver folder in the supplied CDROM. 

c.- The operating system will select one virtual serial port. To check the port configuration, and 

change it if needed, open Control Panel->System->Hardware->Device manager. The new serial 

port will appear under PORTS (COM & LPT): 


2.2.3 Software Configuration 

The IBW_RTS software has to be configured to use the USB port. To do that, run the software, 

and open the corresponding pre-defined project, default_USB.pro with the File->Open Project 

option in the application main menu. 

The System Config screen for the USB connection should look something like: 

2.2.4 Communication Verification 

It is possible to check the communication between the host and the RTS200 with a terminal 

application, like Windows HYPERTERMINAL. Run the application, and select the virtual serial 

port, as configured by Windows (check it in Windows Control Panel if needed). Once the 

connection is opened, write the characters: 

$GV 

Followed by ENTER. This corresponds to the GET VERSION command in the RTS200 protocol, 

and there should be an answer from the RTS200 in the HYPERTERMINAL screen. 

2 .3 Ethernet Installation 

2.3.1 Hardware Connection 

There are two ways to connect the RTS200 to a host through the ETHERNET interface. 

• Direct connection with a crossover cable 

• Connection through a hub or switch with a straight cable 

2.3.2 IP Address / Port 

The RTS200 is factory shipped with a fixed IP Address (192.168.1.33). The default IP Port is 

15001. Depending on the network configuration these settings may not be valid, and have to be 

changed. The procedure to change the default IP settings is described in the following sections. 

2.3.3 Ping 

The first verification can be done by sending a ping to the RTS200 IP Address: 

ping 192.168.1.33 

If there is answer from the RTS200, it means that the hardware connection is right, and that the IP 

Address is valid, so it is possible to skip the following sections and go to the section describing the 

APPLICATION CONFIGURATION. 


2.3.4 Deviceinstaller 

If there is no answer for the ping, it probably means that the IP Address is not reachable from the 

host, and it has to be changed. The way to do it is using an external utility from LANTRONIX (the 

manufacturer of the RTS200 Ethernet interface component, the XPORT). This utility is included in 

the installation CD-ROM, and can also be downloaded for free from the LANTRONIX web page: 

http://www.lantronix.com/support/downloads.html 

This configuration utility has to be installed and run. The following screen appears: 

The steps to follow to change the RTS200 IP Address are as follows: 

• Press the Search button in the Deviceinstaller screen 

• The RTS200 IP address will appear after some seconds. Attention: If the computer is 

equipped with local network and wireless (wi-fi) network connection, or in general, if it is 

connected to more than one network, it is important to select the right connection (usually 

local network, that is, cable connection) by clicking in the main menu Tools->Options. 


• If it does not appear it usually means that there is a problem (hardware, cables, ...) 

• If it appears in black font, the RTS200 is reachable (as in the screen above), and there is no 

need to change the IP Address 

• Usually (if the ping test was not successful), the address will appear in red font, meaning that 

a RTS200 has been found, but the address range is not accessible from the host. The 

RTS200 IP Address has to be changed. 

• To change the RTS200 IP Address, select the XPORT device whose address is to be 

changed in the right side of the Deviceinstaller screen, and press the Assign IP Address 

button. The following screen appears: 

• Select the Assign a specific IP address option, and press NEXT: 


• Set a IP address valid according to your computer and network configuration (subnet mask), 

and press NEXT. 

• Press the Assign button. The RTS200 will be configured with the new address. 

• Pressing the Search button again, will make the new address to be displayed, this time it will 

be in black font if the address was properly selected. 

• If you don´t know which IP Address is right for your network configuration, you can select the 

Obtain an IP address automatically. This option will give you a valid IP Address. As the 

RTS200 application needs a fixed IP Address, this automatically generated IP Address will 

have to be manually assigned again, following the same procedure described above. 

2.3.5 Software Configuration 

Once the RTS200 IP Address is valid, the IP Address on the application controlling the RTS100 

needs also to be changed accordingly. To do that, click on the RTS200 image on the System 

Config form: 


The Object Inspector form (in the left hand side of the screen shown above) shows the IP Address 

that the application will use to establish contact with the RTS200. This value will be changed to the 

new RTS200 address, pressing ENTER at the end, to make the change take immediate effect. 

The connection in the graphic between the RTS200 and the host has to be (as in the screen 

above) made between the LAN connections in the graphical representation of both elements. If it 

has to be changed, you have to right-click anywhere in the free space of this form, and some 

drawing tools will appear, choose the arrow (select option) to be able to move the host, the 

RTS200 or the connecting line. 

To check the communication with the new parameters (and once the RTS200 is connected), press 

the Get Test button on the tag analyzer screen. The signal should appear on the screen. (If the 

address is not properly configured, the application might seem to stall, as it will be waiting for some 

time to the answer from the operating system). 

After the communication is established, and in order to save the configuration, choose the File- 

>Save As options in the main screen menu, and choose a name for the new configuration (project 

file). The application will start with the latest saved or loaded configuration. 

2 .4 Configuration 

The RTS100 software stores the configuration (hardware connection and software status) in a 

project file (*.PRO). There are several sample project files in the installation directory that can be 

used to get familiar with the different configuration options. The results of loading the different files 

are graphically shown in the software configuration screen. The steps to start a project from 

scratch are described next. 

2.4.1 Opening a New Form 

First of all it is necessary to create a form, that is, a container where all the elements are going to 

be displayed. To do it, just press the New Form button on the screen. A default form appears (if 

the toolbar is not displayed, press Toolbar->Files to make it appear). 

In the configuration form, the Master Controller represents the controlling computer (the computer 

where the software application is running). A computer image appears showing the four interface 

options (Serial 1, Serial 2, USB and LAN). 


The other element in the configuration window represents the RTS200 itself, showing also the 

different interface options. There should be one RTS200 block for every real device to be 

controlled from the same host. To add a new RTS200, right-click on the form, and select Load 

Block, or in the menu, select Drawing Tools->Load Block. After that, a mouse click on the form will 

make the library file selection appear, where it is possible to choose between the different 

elements to include. The blocks are usually under the /LIB folder. 

2.4.2 Selecting the Communication Interface 

After the display matches the hardware configuration, it is very simple to choose the 

communication interface. Select the Draw Line in the menu (or in the context menu right-clicking 

on the form), or press the corresponding button in the toolbox. Then click on the host interface to 

be used (for instance USB), and drag to the RTS200 interface (USB also in this case). Both the 

Host and the RTS200 will use the selected interface. To change the interface is only a matter of 

selecting the line, and graphically changing the connection. 

2.4.3 Configuring the System 

Once the system hardware configuration is established, it is possible to configure the behaviour of 

each module. The modules or blocks are not just images. They have associated properties, that 

allow to select their operating parameters. To do it, click on the module image so the property 

editor shows the property values for the device. The main properties of the RTS200 are: 

Property 

Block_Type 

Name 

LAN_IP_Address 

LAN_IP_Port 

Explanation 

The type of the block. Can not be changed 

Choose a name for the unit and a caption to show when the module is selected 

LAN IP Address for Ethernet communication 

LAN IP Port for Ethernet communication 


3 Menu Options 

3 .1 Context Sensitive Menu 

The RTS200 module displays a context sensitive menu when right-clicked. The controller module 

displays a menu with the following options: 

Option 

Reset Unit 

Tag Analyzer 

Firmware Update 

Explanation 

Performs a soft reset to the unit 

Opens a new window with all the RF and tag test controls. All the manual and automatic tests are 

controlled and configured from this window, so it will be described in detail in the next chapter 

Programs new firmware versions into the RTS200 

3 .2 Window Main Menu 

This main menu shows the option described below. 

Option 

File 

Drawing Tools 

Toolbars 

Windows 

Help 

Explanation 

Shows file operations, like opening a new project, a new text file, an existing project or text file, save 

projects and text files, print operations, and exit from the program. Also the Global Test Options form 

can be accessed from here 

Tools for drawing into the system configuration form, adding or deleting blocks, wires, changing 

colours ... The same options can be reached from the toolbar if the corresponding toolbar section is 

active. 

Shows or hides the different toolbar sections (File, Drawing tools, Program control, Window 

management and Help). It is useful to keep maximum screen space for operation if needed. 

Window management. Ordering in cascade, tile horizontal or vertical, minimize or arrange. Also 

selection of a particular window from the list. 

Activation of the help documentation, and about box, with version information. The HELP files are 

organized as .PDF documents that can be accessed from this menu option. 

3.2.1 FIRMWARE UPDATE 

To update the RTS200 firmware, select the corresponding option in the device contextual menu in 

the configuration window. The following screen appears: 


The first line shows the Serial Number and Firmware versions as received from the RTS200. If the 

communication is not properly configured, a “Not Found” message appears instead. 

The firmware update procedure is as follows: 

• Click the Browse button, and select the .h86 (firmware) file supplied by the manufacturer 

• Click the Update Unit Firmware button 

• If the unit is being programmed through the serial port, press and release the programming 

button. This button is accessible through a hole in one side of the device. (if the unit is 

programmed through the Ethernet interface, there is no need to press this button) 

• Reset the unit (power supply off-on) to go back to normal operation 

3.2.2 GLOBAL TEST OPTIONS 

This option in the main window menu has been included to allow customization of some 

parameters of the program, like for instance the drop down menu for efficiency control in on-line 

mode, or the fields to be included in the generated reports. 

To access the parameters a password will be required, if it has been configured as non-empty. 

The following window appears: 

The first Tab Report Generation is provided to configure the fields to be included in each record in 

the generated report in on-line mode. Checking an option means that the corresponding field will 

be included. The additional option Include Efficiency Records makes it possible to include records 


corresponding to this option, according to the efficiency measurements settings in the tab 

described next. 

In the Efficiency Measurements tab, the operation of the efficiency measurement is defined. 

If the Enable Automatic Stop option is checked, a dropdown menu will appear automatically when 

in online mode after the time defined in the Time for Stop has elapsed without detecting any tag. 

This situation is considered a stop of the machine, and the operator will have to provide a reason 

for the pause. The option texts are defined in this screen. This text will also appear in the report if 

the Include Efficiency Records option in the previous tab is checked. 

The dropdown menu that appears for the efficiency control is shown as: 

To continue working, the operator will have to include a value for identification, and a reason for 

the stop, to be selected from the available options. This information is included in the report if the 

corresponding option in the Report Generation Tab is checked. 

The next tab Password Settings is used to handle the password to access this window. To modify 

the password, the old password has to be typed. 


The Test Grids Setup tab control allows configuration of the elements accessible to the operator in 

the test setup screen on the tag analyzer window. If an option is checked, the corresponding 

element is open for the operator to change: 


4 Ta g Analysis 

The Tag Analyzer window is shown by selecting the option in the context sensitive menu (rightclick 

on the RTS200 module image on the screen). 

The purpose of this window is to provide the user the control over all the relevant parameters in 

the tag testing process, both manually and on-line. It is possible to present three different screens 

on this window, by pressing the three buttons on the top-right: 

Button 

Tag Analyzer 

On-Line Test 

Test Setup 

Explanation 

Provides direct control over the test conditions (frequencies, levels, protocol, ...) in manual mode 

Operations related to Online Tests 

Provides access to test suites and individual tests, where the conditions and parameters of the 

tests are defined 

The three screens and their associated procedures are defined in following sections. 

4 .1 Tag Analyzer Screen 

The appearance of the screen is shown below. 

It is divided into three different sections. The Display section shows graphically the result of the 

measurement or data test. Sometimes it will display the results in the time domain and some other 

times it will be in the frequency domain, depending on the state of the other parameters in the 

screen. The X and Y axis titles and labels show the corresponding values and units. 


The Results Section below displays the numerical results of the test, along with the test 

identification, and test conditions, as defined in the corresponding test file. 

The Control Section in the middle contains all the buttons needed to operate the screen. 

The three sections are described in detail next. 

4.1.1 Display Section 

In the left part of the display section, the RF controls are shown. It is possible to change all the RF 

parameters (the values usually shown in white), by two different procedures. Where continuous 

values are shown (frequencies, for instance), it is possible to edit the value with the keyboard. 

Where only discrete values are allowed (BW filter, for instance), the change will be made by right 

(increase the parameter value) and left (decrease the parameter value) clicking on the value. 

There are three sets of parameters. Those related to the RF generator are on top. The parameters 

related with the Receiver come next, and finally the antenna selection control. The list of 

parameters and their meaning are described below. 

It is possible to specify the magnitudes in different units. A frequency parameter can be specified 

in terms of Hz, KHz or Mhz. 

A RF level value can be specified in voltage units, both logarithmic (dBm) or linear (V, mV, uV), 

and if the antenna and antenna-tag distance is specified, also in terms of Magnetic Field at the tag 

(A/m, mA/m or uA/m). The RTS200 software performs all the conversions needed to generate 

the specified field at the given distance. 

Frequency Generator 

Parameter 

Frequency 

RF Level 

Mod Index 

Tracking 

Explanation 

The frequency output by the RF generator. Continuous value. The parameter is also used as the 

carrier frequency for the functional tests 

The output level of the RF generator. It is a continuous value. 

The Modulation Index to be used in the RF generator for RTS200-TAG communication. Continuous 

value in % between 0 and 99. 

Used to enable/disable the Tracking (RF Generator sweep). Discrete value. It can only be Enabled or 


RF Output 

Disabled (the value of this parameter is always defined in the test file, according to the type of test there 

is no reason to change it manually in normal operation). 

Used to enable/disable the RF output. Discrete value. It can only be Enabled or Disabled (the value of 

this parameter is always defined in the test file, according to the type of test there is no reason to 

change it manually in normal operation). 

Receiver 

Parameter 

Mode 

Freq. Span 

Ref. Level 

Explanation 

Discrete value. It can be Single Freq. or Sweep. The single frequency mode (0 span) is used for 

functional tests, while the Sweep mode is used for electrical tests (the value of this parameter is always 

defined in the test file, according to the type of test there is no reason to change it manually in normal 

operation). 

This is a continuous frequency value. It is only shown when the Receiver mode is set to sweep. It 

controls the distance in frequency between the lower and upper frequency in the sweep. 

It is equivalent to the Ref Level control in a conventional spectrum analyzer. It defines the level that 

corresponds to the maximum to be measured. It is a discrete value. It can be 1mV-10mV (in 1mV 

steps), 30mV and 100mV. 

BW Filter IF Bandwith. The possible values are 2 Mhz, 200 Khz, 150 Khz, 100 Khz, 75 Khz, 50 Khz, 25 Khz, 10 

Khz, 1 Khz, and 100 Hz (the value of this parameter is usually defined in the test file, according to the 

selected protocol in functional tests, there is usually no need to change it manually in normal 

operation). 

HP Filter 

Video Filter 

Scale 

Samples 

Tag 

Demodulation high pass filter. Digital value from 1 to 15 (the value of this parameter is usually defined 

in the test file, according to the selected protocol in functional tests, there is usually no need to change 

it manually in normal operation). 

Video Filter. It is a discrete value and can be Enabled or Disabled. It is implemented as a FIR filter in 

the high level software used to smooth the signal in the spectrum analyzer display. The filter 

characteristics are automatically selected in the high level software for each span and centre 

frequency. 

It defines if the measurement is going to be made on the linear signal or on the logarithmic signal (the 

value of this parameter is always defined in the test file, according to the type of test there is no reason 

to change it manually in normal operation). 

It defines the number of samples to be taken in the measurement. In functional tests, this value 

corresponds to the necessary samples to have the whole signal to be demodulated. In electrical tests, 

it defines the frequency resolution of the measurement. It is a continuous value. 

Defines the protocol to be used to communicate with the tag. The options available for this version are 

shown below. The actual enabled protocols will depend on the system and device configuration. 

Available protocols in the current version are: 

ISO_15693 

ISO14443_A_MIFARE 

PHILIPS_ICODE 

UHF_EPC_CLASS_1_SLOW 

UHF_EPC_CLASS_1_FAST 

UHF_ISO_18000_6B 

UHF_EPC_GEN2 

UHF_EM4222 

Antenna 

Parameter 

Test Antenna 

Explanation 

Discrete value. It defines the type of antenna for the measurement. The value affects to the Magnetic 

Field magnitude to RF voltage correlation calculation. The antenna set and calibration constants are 

defined in a configuration file (RTS100.cfg) . In this software version the antenna set is: 

HTP100 

UTP100 

UTP200 

HTP200 


GENERIC 

(The values TESPR1000 and TESPR1006_UHF are maintained for backward compatibility, but they 

correspond to the HTP100 and UTP100 antenna models respectively) 

Distance 

Tag-Antenna distance in mm. The value affects to the Magnetic Field magnitude to RF voltage 

correlation calculation 

The graphical display shows the waveform (time or frequency domains, depending on the settings 

or the selected test), and some additional information, as marker and cursor positions, or axis 

limits. It is possible to make some operations directly on the display: 

Operation 

Zoom 

Pan 

Full View 

Explanation 

Click on the top-left part of the area to be displayed, and drag to the bottom-right. The selected area will 

be adjusted to fit in the whole display zone 

Right click and drag on the display to the desired position 

Click and drag starting from the bottom-right and finishing in the top-left 

It is also possible to write values in the lower part of this screen section, in the Start, Stop and 

Centre fields. 

4.1.2 Chart Options Menu 

The lower part of the Display Section shows the new Chart Options Menu. When clicked, a menu 

appears with options related to report generation and printing of measurement results: 

The operation of this menu allows automation of some measurement tasks. It is possible to select 

one or several options in the menu, that will be performed all at once by clicking in the Do It! label 

on the right. The idea is to simplify the report generation task by saving the relevant information to 

disk in an organized way, with a single mouse click. The following options are available: 

Menu Option 

Save Chart Data 

Save Image Data (bmp) 

Save Image Data (jpg) 

Print Chart 

Preview Chart 

Copy Chart to Clipboard 

Explanation 

Saves the numerical information corresponding to the graph that is being displayed, that is, the X-Y 

values of the curve that is displayed on the screen 

The Display Section image is saved as a bitmap file 

The Display Section image is saved as a jpeg file 

The Display Section image is sent to the system active printer 

There is a preview prior to sending the image to printer. It is possible to select another printer, or to 

change the printing options 

The Display Section image is sent to the clipboard. It is possible to Paste this image into any other 

Windows application (word processor, for instance). The graph colours are optimized for printing 

4.1.3 Results Section 


The test results section shows the results of the manual test performed. If it is a functional test, it 

displays the data read or written from/to the tag: 

In the case of an electrical test, it also displays the measurement value: 

The operation to be performed is selected in the Test Parameter Section (see description below). 

This operation will be performed once pressing the Single button, or continuously pressing the 

Cont button. The test result will be reflected in the results zone. 

If the Table button is down, and pressing the Get Test button, a special table format will be kept in 

the results area, allowing easy comparison between a set of tests: 

In this case, the Counter field reflects the number of tests performed. 

The Clear button clears all the information from the test results area. 

Pressing the Store button will make all the subsequent results to be appended, without clearing 

the previous information. The result is as follows: 


While the Store button is pressed the test results are stored in memory. When it is released, all the 

stored information is written into a file (see file formats section below in this chapter). 

4.1.4 Control Section 

In this section it is possible to choose between the different tests defined in the Test Setup screen 

(see description below in this document). Once a test from those included in the current test suite 

is selected (with the Select button), the Get Test button transfers all the test parameters to the 

corresponding Display Section parameters, that is, to the current settings on the screen. This is a 

very convenient way to select the right parameters for a particular test, as it is performed using the 

conditions defined in the test file. 

As an example, to make the RTS200 perform a read test on an ISO15693 tag, instead of manually 

adjusting all the parameters (frequency, output level, number of samples ...), it is more convenient 

to select the pre-defined ISO15693 read test, where all those conditions are already defined. 

Pressing the Get Test button will also make the selected test to be performed. 

It is important to notice that the changes in the test will not be automatically saved to the test file. 

To do it, it is necessary to access to the Test Setup screen, substitute the old parameters with the 

new values, and save the test file and/or the test suite. This has been made to prevent accidental 

change of the test file contents. 

The Do All Tests button performs all the tests of the test suite in the manual operation mode. All 

the results will be displayed in the results section of this screen. All the limits defined in the test will 

also be checked, and a PASS/NO-PASS indication will be shown. 

Selecting Manual Operation makes it is possible to change any test parameter directly from the 

display section, and perform the test in the resulting condition. 

It is also possible to modify a test condition or test limit in the test setup window (see description in 

later section), and even without saving the test, the new test conditions will be taken into account, 

but will not be saved into the test file unless the save operation is performed (pressing the Save 

Test button). 

The Marker controls allow to display or hide a marker with the On button, to find the maximum with 

the Peak button, or to move the marker frequency to the centre of the display with the M->CF 

button. 


The Traces controls in this section are provided to control the displayed signal on the display 

section. 

Three traces have been defined (A, B and C). It is possible to show / hide any of them, with the 

View and Clear buttons. This mode of operation allows storing and displaying up to 2 reference 

data, to compare with the current waveform. The View and Clear buttons operates on the 

waveform selected by the A, B or C buttons. 

4.1.5 File formats 

There are several different file formats, resulting from the different operations in the Tag Analyzer 

screen. All files generated are stored in the /Test Data folder. Each new file generated is assigned 

a name starting with the date and time when the file is created, and followed by an identifier of the 

type of file. 

Save Chart Data 

The Save Chart Data option from the Chart Options menu generates a file with as many lines or 

records as samples displayed in the graph. Each line contains an X-Y pair of the form: 

... 

13000000 -58.159 

13010000 -58.159 

13020000 -58.373 

13030000 -58.346 

13040000 -58.239 

13050000 -58.266 

13060000 -58.293 

13070000 -58.293 

13080000 -58.213 

13090000 -58.186 

... 

This file section corresponds to a resonance curve. It means that, for instance, at 13000000 (that 

is, 13MHz), the signal value is -58.159 (in this case dBm). 

The file identifier, in this case, is the letter E for electrical tests or F for functional tests. For 

instance, the name of this file is: 

080110124756_E.txt 

It means that it was created on 10/01/08 at 12:47:56, and it corresponds to an electrical test 

(frequency in X Axis). 

Store Button 


When the Store Button is pressed, the test results are stored into memory, and when it is released, 

all this information is saved into a file. It is a text file, with all the fields separated by semicolon, so it 

can be easily imported into most spreadsheets. 

The file format is: 

Q Factor; 

Test Limits:;;;;;;;;;13 MHz;15 MHz;0.05 mV;-10 dBm;10 ;190 ; 

Tag;Status;Frequency;Unit;Amplitude;Unit;Gen.Amp.Lev;Unit;Qfac;Min Frq;Max Frq;Min Amp;Max Amp;Min 

Qfa;Max Qfa; 

0000;PASS;13850000;Hz;-41;dBm;4; mA/m;35;PASS;PASS;PASS;PASS;PASS;PASS; 




... 

When imported into a spreadsheet, the appearance is: 

Q Factor 

Test Limits: 13 MHz 15 MHz 0.05 mV -10 dBm 10 190 

Tag Status Frequency Unit Amplitude Unit Gen.Amp.Lev Unit Qfac Min Frq Max Frq Min Amp Max Amp Min Qfa Max Qfa 

0 PASS 13850000 Hz -41 dBm 4 mA/m 35 PASS PASS PASS PASS PASS PASS 




If there are several tests made at once (with the Do All button, for instance) a different file is 

generated for each test. 

The naming of the files follow the same rule as described above. The name is composed of the 

date and time, and then the type of test (the Identification parameter as defined in the test file). For 

instance, the name of this file could be: 

080116131720_Q Factor.txt 

5 Test Setup 

The type and characteristics of the test to be performed during the online test operation are 

configured in the Test Setup screen. All the tests are arranged in Test Suites. 

A test suite is a set of individual tests to be performed online to a particular type of tag and in a 

particular machine. 

For instance, a test suite could comprise a read functional test and a resonant frequency and Q 

electrical tests. Every test inside a test suite has its own conditions (parameters), and limits for 

validity. 

The Test Setup screen is included for the configuration of the tests to be performed in online 

operations. The selected test suite is saved in the project file, so opening the project will make the 

corresponding test suite to be automatically loaded. The Test Setup screen can be seen in the 

next image: 


The test suite structure is described in the tree on the left of the screen. The root of the tree is the 

test suite (Read_Data_ISO15693 in the example), while the branches correspond to individual 

tests (Read Tag Data, Resonant Frequency and Q Factor in the example). 

There is also a machine interface configuration file, which includes all the information needed for 

the RTS200 to interface with the machine where it is operating. Parameters defining the hardware 

signals used to control the operation, time characteristics … 

Selecting an item on the tree (the test suite or an individual test), makes it possible to see in the 

right side of the window the properties associated with the element. There are three different types 

of properties. They can be seen selecting the corresponding tab page on the screen. 

Property Type 

Identification 

Test Conditions 

Test Limits 

Explanation 

The name, date, comments, ... corresponding to the test suite or individual test are defined here. The 

parameter name and number are open, so the user can add as many identificative properties as 

needed. 

The conditions of the test are described here. This corresponds to values needed for some operating 

parameters. For instance, the RX frequency, the number of samples to take, ... The conditions also 

correspond to configuration parameters on the Tag Analyzer screen. 

These are the limits to consider a test result to be valid or not. When the test result falls between the 

limits, a PASS indication appear in Tag Analyzer mode, and the result is considered valid in Online 

mode. Other parameters defined here are used to control the appearance of the data results in the 

online test screen. 

The Test conditions and Test limits have special Keywords for the parameters. The keywords can 

not be changed. ANNEX 2 describes those pre-defined keywords. More keywords can be added in 

the future if more parameters have to be changed for different tests. 


The toolbar on top of the window allows performing the different operations to configure a test: 

Open and Save of a test suite, Adding, or removing new or existing tests to a test suite ... The 

caption on the buttons are self-explaining. It is important to mention that, when adding a new test, 

a test template will be required. The test templates are files with the extension .TPL, with default 

values for all the required parameters. In any case, it is usually simpler to use a pre-defined test, 

modify the required values, and save it with another name. 

The same operations can be carried out with a context-sensitive menu opened when right-clicking 

the selected tree items. 

After a test file has been selected, it is possible to transfer the settings (conditions) to the Tag 

Analyzer screen (see description of the Get button in the Test Parameter section of the Tag 

Analyzer screen description). 

5 .1 Te s t t yp e s 

There are two different types of tests attending to the test purpose: 

• Characterisation tests To be performed in manual mode, the purpose of the 

characterisation tests is to provide all the relevant electrical and functional test parameters. 

The emphasis is put into the accuracy, so they are not optimized for speed. 

• Production tests To be performed mainly in online mode, the purpose of the 

production tests is to provide a way to reject all transponders not meeting a specific criteria or 

performance limit. They are optimized for speed. 

There are different default folders for the different type of tests. Characterisation tests are usually 

under Test_Setup/Test_Characterisation, while Production tests are under 

Test_Setup/Test_Production. (the SETUPDIR global constant has been defined with the path of 

the Test_Setup directory). Please, note that the tests provided with the installation CD-ROM, are 

generic tests. The user may need to modify them to adapt the RTS operation to their specific 

requirements. It is very common, for example, to change the RF level, or the frequency for a 

particular test to work with a certain type of tag. 

There are two different types of tests attending to the test characteristics: 

• Electrical tests Measurement of electrical characteristics of the transponder. 

Resonant Frequency or Q factor are examples of Electrical tests. 

• Functional tests To check the transponder operation. Reading data or Writing 

information into the tag memory are examples of functional tests. 

Electrical and functional test characteristics are defined by a different set of parameters. ANNEX 2 

shows the detail of the parameters allowed in the different type of tests. 

5 .2 Te s t A rrangement 

All the test parameters can be defined in both the test suite of the individual test file. The test suite 

parameters will be read first, and if the same parameter is defined again in the individual test, this 

value will overwrite the previous parameter value. 

It is a good practice (and the default test files included in the installable make use of this 

philosophy), to use test files that are common for all the test suites, in order to minimize the 

number of test files to be defined. 


All the common test files are usually together under the /common folder in the 

Test_Setup/Test_Characterisation or Test_setup/Test_Production directories. A test suite is 

usually composed of one or several common test files, defining all the standard parameters, being 

the parameters specific for this test suite, defined in the test suite file. 

It is important to understand that if a parameter is defined in the file corresponding to an individual 

test, the scope of this parameter will only be this particular test. All the previous and later tests 

make use of the parameter defined in the test suite. 

5 .3 Machine Interface Configuration 

There is an additional type of file that defines the interface between the RTS200 and the machine 

where it runs in online mode. This file includes information about some special parameters to 

describe the operation of the hardware interface with the machine, that is, the polarities and timing 

of the signals sent from the machine to the RTS200 to start the test or from the RTS200 to the 

machine to signal the end of the test or its result. (See RTS HARDWARE MANUAL for a 

description of the hardware interface). 

This option has been included to provide flexible hardware interface, having in mind the diverse 

specification of the interfaces in different machines. The configuration parameters that have been 

introduced are described in ANNEX 2. 

The interface is synchronous parallel. The machine sends a SOT (Start of Test) to signal the 

RTS200 that the transponders are in place for the test. The RTS200 shows the result of the test in 

the Result line. Then it activates the EOT (End of Test) signal as an indication of finished test. 

As an example, see the parameters for the drawing below: 

Start of Test (SOT) 

Tag In 

Place 

Tag In 

Place 

Tag In 

Place 

Tag In 

Place 

Result (R) 

End of Test (EOT) 

PASS FAIL PASS PASS 

Valid data Valid data Valid data Valid data 

Test Time 

The parameter definition for this interface would be: 

Parameter Value Explanation 

RESULT_FAIL_LEVEL 0 High Level when active 

EOT_ACTIVE_EDGE RISING Rising edge for EOT signal 

TRIGGER_ACTIVE_EDGE FALLING Falling edge for SOT (Trigger) signal 

RESULT_ACTIVE FAIL The result line is active in the FAIL condition 

T_RESULT_ACTIVE 0 The EOT and RESULT signals are active till next trigger 

The machine configuration file is specific for each machine where the RTS200 is operating, and it is 

usually located in the SETUPDIR/Machine_Config directory. 


6 ONLINE TEST SCREEN 

The Online test screen is designed to provide control over the online-test process, showing also 

the results of the test being performed. The screen appearance is shown here: 

6 .1 Control Section 

The control section is used to start/stop the online-test operation. To start a test, just press the 

Run button. The label box should display the message Running if the operation was successful, 

that is, if the RTS200 is now in online test mode. To stop this mode, press again the same button. 

When the run button is pressed, the window shown below appears, asking the operator to type the 

reel identification code. The buttons included are intended to start the test or to cancel the test 

(close the window). There is an option check to initialize statistics (yield and statistical information). 

The operator will also be able to introduce a text field for Run. This could be needed when the 

same reel has to be processed several times. 


The Pause button is used to make adjustments on the system; the trigger point ... The RTS200 

keeps operating in online mode, but the host software will discard all the data coming from the 

reader, so it will not affect the yield or appear on the report files. The display goes to the Manual 

Screen, where it is possible to test performance, or change parameters. After the Pause button is 

pressed again, the test continues from the situation when it was stopped. 

6.1.1 YIELD SECTION 

The yield value of the current run, is shown in numerical and graphical formats. The total, pass 

and fail numbers are also shown. Two yield values are shown. One is for the whole run (long term 

yield), and the other is for a defined number of the last tags (short term yield used to describe 

tendencies). The number of tags taken into account for this Short Term Yield is defined in the 

Machine Configuration file. The parameter is ST_YIELD_SAMPLES, and the default value is 16. 

The counters and values are reset by means of the Initialize Statistics option in the Reel 

Identification window. 

There is a configurable minimum value for the yield, so the Yield indication will go red is the value 

is lower to what is expected. This is only an indication to the operator, as the program does 

nothing in this event. 

6.1.2 STATISTICAL INFORMATION SECTION 

This section shows some real time Statistical Process Control information derived from one of the 

Electrical Measurement tests included in the test suite. 


The display shows the graph of the statistical distribution of the parameter selected in the Graph 

Selection box (resonant frequency in this case), as a bar chart with the number of occurrences of 

the different parameter values. The upper and lower limits for the chart and the number of bars are 

controlled by means of the parameters MIN_GRAPH, MAX_GRAPH and NUM_GRAPH in the 

test definition file. 

6.1.3 Test Result Section 

This section presents the results of the last tests performed in online mode in a grid. 

The following fields are shown: 

Field 

Index 

Gerror 

Serror_x 

Tries 

Date, Time 

Explanation 

Shows the ordinal number of the processed transponder in the current run 

General Error. It is 0 if there is no error in any of the tests performed. A non-zero value means that an 

error has been produced in at least one of the tests of the test suite. The list of possible values for 

Gerror is described in ANNEX 3 

Specific error code for an individual test. A non-zero value means that an error has happened in the 

test number x.The list of possible values for this parameter is described in ANNEX 3 

Number of tries that have been necessary for the test to give the PASS condition. The maximum 

number of tries is defined for each individual test. This value can be enabled or disabled in the 

Global Test Option screen, and it provides indication of how often the test is giving wrong results 

The date and time of the test carried out 

There are additional fields for each test showing the result of the test. For instance, the serial 

number of the tag chip, or the value obtained for the resonant frequency. 

6.1.4 REPORT SECTION 

The name of the Reel as introduced by the operator is shown here. 

The Open File button opens the report file generated by the whole operation, where the results for 

all the transponders processed are stored. 


6.1.5 GENERATED FILES 

There are two types of files generated by the application when online mode: 

• Report File A file containing the results of the test for each individual 

transponder. It is described in detail in ANNEX 1. 

• Exchange File A file to be used by other applications needing real time information 

for synchronization. The name of the file is exchange.dat, and it is located in the Test_data 

directory. The file contents format is shown in the line: 

C:\Ibw_Rts\test_data\123_12.txt,100,100,2,EFBD4C0000000001D608,EFBD4C0000000 

001D608, EFBD4C0000000001D608 

This single line includes, separated by commas, the following fields: 

• The file being generated C:\Ibw_Rts\test_data\123_12.txt 

• The long term yield 100 

• The short term yield 100 

• The N_RESULT_DELAY parameter 2 

• The last 3 serial numbers EFBD4C0000000001D608 

EFBD4C0000000001D608 

EFBD4C0000000001D608 


ANNEX 1 

T EST REPORT F ILE FORMAT 

A report is generated for every online test run. The file name is the reel name introduced by the 

operator. If several tests are performed with the same reel number, the characters _xx are 

appended to the file name, where xx is a number between 00 and 99. The file format is shown 

next: 

;**************************************************************** 

;Test Suite = SETUPDIR\\test_production\testpr_1000\data_test_icode.tsu (Data_Test_ICODE) 

;Test 0 = SETUPDIR\\test_production\common\data_test.tst (Data Test) 

;Start of test = 15/12/3 12:54 

;Roll ID = 123 

;Run = 

;Chip = PHILIPS_ICODE 

;TesterID = RTS100 – IberWave SLL Ver 1.01 SN - 010.0001.0.0006 

;Antenna Type = TESPR1000 

;Suite Identification = ICODE Data test 

;Suite Created By = FN 

;Suite Date = 14/12/03 

;Suite Reference = - 

;Fields = Index, GError,Data Test, SError_1, Tries, Date, Time 

;**************************************************************** 

0,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

1,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

2,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

3,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

4,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

5,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

6,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

7,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:31 

8,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:32 

9,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:32 

13,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:32 

14,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:32 

..... 

334,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:44 

335,00,3FF28001000000018C1E,00,01,15/12/2003,12:54:44 

;**************************************************************** 

;Total number of tags processed = 336 

;Pass = 258 

;Fail = 78 

;Yield = 76 % 

;Number of failures at Data Test test = 78; 

;End of test = 15/06/05 12:54 

;Elapsed time = 0:19 (minutes:seconds) 

;**************************************************************** 

The file is composed of three sections: 

• Header Showing the test identification information. 

• Tests Showing the test result for each different test performed 

• Footer Showing statistics of tests performed for each antenna and the 

accumulated values. 

The example shows a run with only one data test defined. If more than one test is performed, 

additional fields will be included to show the individual results and error codes. 


ANNEX 2 

T EST PROPERT IES 

The next table shows the set of properties defined for the current RTS200 version for electrical 

tests. 

Property name Description Comments 

TEST CONDITIONS 

TEST_TYPE 

Type of test to be 

performed 

* Tests marked with (*) are not 

implemented in the firmware. 

They are only intended for 

laboratory use 

TST_RES_FRQ 

TST_UN_RES_FRQ (*) 

TST_LO_RES_FRQ (*) 

TST_Q 

Resonant frequency test 

Unloaded resonant frequency test 

Loaded resonant frequency test 

Q test 

START_FREQ Lower freq. For the test In Hz, KHz or MHz 

STOP_FREQ Upper freq. For the test In Hz , KHz or MHz 

RF_LEVEL RF level for the test In terms of field (mA/m, A/m , ...) or voltage (V, mV, uV) 

N_SAMPLES Samples Number of measuring points between low and up. Freq 

TRIES Number of times to test Repeats until NTRIES if the test is not successful. 0 means Level Trigger, that is, the test 

will be repeated until a good result is obtained or the trigger signal goes back to its 

original state. 

TEST_PERIOD Periodicity of test The test is performed every TEST_PERIOD tests 

POSDET_FILTER 

IF_BANDWIDTH 

VIDEO_FILTER (for 

compatibility reasons) 

Post-detection filter The post-detection filter bandwidth. It can take the values 100 Hz, 1 KHz, 10 KHz, 25 

KHz, 50 KHz, 75 KHz, 100 KHz, 150 KHz or 200 Khz. 

(Any of the three property names are valid and equivalent) 

REFERENCE_LEVEL Analyzer ref. Level In voltage units (V, mV, uV, ...) 

HP Filter Demod. High Pass filter Selection of filter. Digital value from 1 to 15 

DETECTOR Demodulator Only Linear option can be selected here 

TEST_ANTENNA_TYPE Model of antenna to use TESPR1000,TESPR1001,TESPR1002,TESPR1003 

DISTANCE_TO_ANTENNA Antenna-tag distance Used to control Field level in tag with precision 

TRACKING_GENERATOR Enabling of tracking ON/OFF 

RF_GENERATOR_ENABLED 

YIELD_THRESHOLD_LT 

YIELD_THRESHOLD_ST 

TEST LIMITS 

Enabling of tracking 

generator 

Long term yield threshold 

(defined in test suite) 

Short term yield threshold 


ON/OFF 

For lower values of LT yield, a red alarm indication appears on screen 

For lower values of ST yield, a red alarm indication appears on screen 

RESULT TYPE Type of result of the test Int, string, bool 

MIN_GRAPH Lower limit for SPC graph Should be minimum expected value for measurement 

MAX_GRAPH Upper limit for SPC graph Should be maximum expected value for measurement 

NUM_GRAPH 

Number of points in SPC 

graph 

LIMIT_MIN_FRQ Freq. Lower limit for test Minimum frequency measurement to consider the test valid 

LIMIT_MAX_FRQ Freq. Upper limit for test Maximum frequency measurement to consider the test valid 

LIMIT_MIN_LEV Level lower limit for test Minimum level measurement to consider the test valid 

LIMIT_MAX_LEV Level upper limit for test Maximum level measurement to consider the test valid 

LIMIT_MIN_Q Lower limit for Q In electrical measurements 


The next table shows the set of properties defined for the current RTS200 version for functional 

tests. 



TEST_TYPE 

Type of test to be performed 

TST_READ_TAG 

Read test 

* Tests marked with (*) are not 

implemented in the firmware. 

They are only intended for 

laboratory use 

TST_FAST_READ 

TST_WRITE_TAG 

Fast read test (no decoding) 

Write test 

TST_READ_THRS* 

Read Threshold 

TAG_TYPE Type of chip (protocol) to use ISO_15693, ISO14443_A_MIFARE, PHILIPS_ICODE, 

UHF_EPC_CLASS_1_SLOW, UHF_EPC_CLASS_1_FAST, 

UHF_ISO_18000_6B 

INICADDR Initial address The starting tag memory address 

LENGTH Length in bytes Number of bytes in tag memory to perform the test 

TX_FREQ Carrier frequency for the test Sometimes not the standard carrier, but the optimal for the tag 

RX_FREQ Reception frequency Frequency where the receiver is tuned (See note below) 

MOD_INDEX Modulation Index Selected modulation index for the test 

N_SAMPLES Samples Number of samples to digitize the tag answer 

TRIES Number of times to test Repeats until NTRIES if the test is not successful. 0 means Level Trigger, that is, the 

test will be repeated until a good result is obtained or the trigger signal goes back to its 

original state. 

TEST_PERIOD Periodicity of test The test is performed every TEST_PERIOD tests 

POSDET_FILTER 

IF_BANDWIDTH 

VIDEO_FILTER (for 

compatibility reasons) 

Post-detection filter The post-detection filter bandwidth. It can take the values 100 Hz, 1 KHz, 10 KHz, 25 

KHz, 50 KHz, 75 KHz, 100 KHz, 150 KHz or 200 Khz. 

(Any of the three property names are valid and equivalent) 

REFERENCE_LEVEL Analyzer ref. Level In voltage units (V, mV, uV, ...) 

DEMOD_GAIN Gain of the demodulator In dB 

ATTENUATOR Input attenuator Selection of input attenuator. 0dB-70dB in 10dB steps 

DETECTOR Demodulator Only Linear option can be selected here 

IF_BANDWIDTH IF filter bandwidth Only 100KHz option can be selected here 

TEST_ANTENNA_TYPE Model of antenna to use TESPR1000,TESPR1001,TESPR1002,TESPR1003 

DISTANCE_TO_ANTENNA Antenna-tag distance Used to control Field level in tag with precision 

TRACKING_GENERATOR Enabling of tracking ON/OFF 

RF_GENERATOR_ENABLED 

Enabling of tracking 

generator 

ON/OFF 

WRITE_DATA 

Data to be written into the tag For personalization. See below for format description 

CHECK_CRC 

YIELD_THRESHOLD_LT 

YIELD_THRESHOLD_ST 

TEST LIMITS 

Enable or disable CRC 

checking 

Long term yield threshold 


Short term yield threshold 


To be used for debugging purposes, or when the tag has not been initialized with the 

right CRC value. 

For lower values of LT yield, a red alarm indication appears on screen 

For lower values of ST yield, a red alarm indication appears on screen 

RESULT TYPE Type of result of the test Int, string, bool (usually string for functional tests) 

LIMIT_MIN_FRQ Freq. Lower limit for test Minimum frequency measurement to consider the test valid 

LIMIT_MAX_FRQ Freq. Upper limit for test Maximum frequency measurement to consider the test valid 

LIMIT_MIN_LEV Level lower limit for test Minimum level measurement to consider the test valid 

LIMIT_MAX_LEV Level upper limit for test Maximum level measurement to consider the test valid 


The next table shows the test conditions in the Machine Configuration files. 



RESULT_FAIL_LEVEL 

Level of RESULT signal when 

FAIL condition 

Binary number with 8 bits. Each bit describes the polarity of the result line for the 

corresponding antenna 

EOT_ACTIVE_EDGE Active edge for EOT signal FALLING or RISING are possible values 

TRIGGER_ACTIVE_EDGE Edge active for trigger signal FALLING or RISING are possible values 

RESULT_ACTIVE 

T_RESULT_ACTIVE 

N_RESULT_DELAY 

ST_YIELD_SAMPLES 

RESULT2_LEVEL 

N_RESULT2_DELAY 

Condition of result to become 

active 

Time the RESULT signals 

remain active 

Delay for output in number of 

tags 

Tags to be considered for 

Short term yield calculation 

Active level for RESULT2 

signal 

Delay for output 2 in number 

of tags 

PASS, FAIL, BOTH or NONE are possible values 

In ms 

Describes the delay in terms of number of tags for the corresponding output signal to 

be generated after the test has been made 

The system will consider the last ST_YIELD_SAMPLES transponder for short term 

yield calculation 

HIGH or LOW to activate the RESULT2 signal (additional FAIL indication) to 1 or to 

0 when there is a FAIL condition 

Same meaning as N_RESULT_DELAY for RESULT2 output (additional FAIL 

indication) 

A nnex 2.1 Write Format Definition 

Some protocols include the possibility of encoding the information into the tag chip memory. For 

instance, the RTS200 current version supports ISO15693 and ISO14443-A writing operations. 

There are two Test Suites supplied as example for writing: 

• Write_Mifare.tsu 

• Write_ISO15693.tsu 

One block of information is written. The data to be written is specified as a string of hexadecimal 

information, in the parameter WRITE_DATA of the test suite: 

WRITE_DATA 

05A1A2A3A4 

The first hexadecimal byte (05 in the example) defines the block number to write (block 5 in this 

case), while the rest of the string defines the actual data to write (hexadecimal bytes A1, A2, A3 

and A4 in this case). 

There are some special cases for information that is not mapped in the memory chip address 

space. For instance, to activate or deactivate the SLI EAS bit, the block number has to be 

specified as FF, and the data has to be FF to activate and 00 to deactivate the bit. 

If writing more than one block is needed, it is possible to build a special test suite including as 

many test files (.tst) as needed. Each test file has to include one WRITE_DATA parameter with the 

information to write on a particular block (remember that the parameter in the test has precedence 

over the same parameter if it is defined on the test suite also). 


ANNEX 3 

E RROR CODES 

Global error (for the test suite), in the “ERROR CODE” field 

OK 0 Test result correct 

FAIL 1 Fail in read operation 

Individual error (for the individual test), in each field, bitwise format 

OK 0 Test result correct 

FAIL 1 Fail in read operation 

UPPER_FREQ 2 The frequency is higher that upper freq. limit 

LOWER_FREQ 4 The frequency is lower than lower freq. limit 

MAX_AMPLITUDE 8 The amplitude is higher that upper limit 

MIN_AMPLITUDE 16 The amplitude is lower than lower limit 

Q MIN 32 The Q is higher than higher limit 

Q MAX 64 The Q is lower than lower limit 

READ FAIL 128 Fail in read operation 

WRITE FAIL 256 Fail in write operation 

CRC ERROR 512 Fail in CRC in functional test 

FORMAT ERROR 1024 Format error (protocol specific)

RTS200 RFID Test Set - RFID Webshop

Create successful ePaper yourself

Delete template?

Save as template?