simatic rfid systems rf-manager 2008 service pack 2...with a safety alert symbol, indicates that...

Answers for industry.

SIMATIC Sensors

SIMATIC RF-MANAGER 2008

Service Pack 2

Product Information · 01/2010

Introduction 1

Installation

2

New functionalities

3

Connection options through serial communication

4

Constraints

5

Appendix A

A

SIMATIC

RFID systemsRF-MANAGER 2008 Service Pack 2

Product Information

01/2010 A5E02472233-02

Legal information Warning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE indicates that an unintended result or situation can occur if the corresponding information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation for the specific task, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens products Note the following:

WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be adhered to. The information in the relevant documentation must be observed.

Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY

A5E02472233-02 Ⓟ 01/2010

Copyright © Siemens AG 2009. Technical data subject to change

RF-MANAGER 2008 Service Pack 2 Product Information, 01/2010, A5E02472233-02 5

Table of contents

1 Introduction................................................................................................................................................ 7

1.1 Preface...........................................................................................................................................7 1.2 Integration Service Pack ................................................................................................................9

2 Installation ............................................................................................................................................... 11 3 New functionalities................................................................................................................................... 13

3.1 RF660R according to ETSI EN 302208 V1.2.1 ...........................................................................13 3.2 Settings for frequency range CHINA ...........................................................................................15 3.3 Tag ID and user data ...................................................................................................................15 3.3.1 Use of user memory.....................................................................................................................16 3.3.2 User data also as Array of Bytes .................................................................................................18 3.4 System function "Delay"...............................................................................................................19 3.5 Setting parameters for serially connected readers ......................................................................19 3.6 Operating modes with serial readers ...........................................................................................23 3.7 Supported tag types.....................................................................................................................24 3.8 ALEDataBridgeClient ...................................................................................................................25

4 Connection options through serial communication................................................................................... 27 4.1 Connecting principle ....................................................................................................................27 4.2 Pin assignment for TRP-C06 interface converter ........................................................................28 4.3 Pin assignment connector EX-42054-9-8S interface converter card...........................................29 4.4 Number of readers .......................................................................................................................29

5 Constraints .............................................................................................................................................. 31 5.1 Operating modes .........................................................................................................................31 5.2 System functions and commands................................................................................................32 5.3 Further restrictions .......................................................................................................................32

A Appendix A .............................................................................................................................................. 33 A.1 Changes for SIMATIC RF-MANAGER 2008 ...............................................................................33 A.2 Reader RF380R (RS232) - PC ....................................................................................................35

Table of contents

RF-MANAGER 2008 Service Pack 2 6 Product Information, 01/2010, A5E02472233-02


Introduction 11.1 Preface

Purpose and background of this documentation This Product Information describes the new functionalities supported by RF-MANAGER 2008 Service Pack 2. RF-MANAGER 2008 Service Pack 2 includes all functionalities of the RF-MANAGER 2008 Service Pack 1. With RF-MANAGER 2008 Service Pack 2 or higher, the RF660R reader with new firmware version V1.3 according to the ETSI standard E 302 208 V1.2.1 is supported. 4 exclusive RFID channels have been defined within the frequency spectrum. The procedure "Listen Before Talk" is no longer used. ETSI-SRD no longer applies. Furthermore, the RF-MANAGER offers the possibility to address readers that can be operated according to the settings for the frequency range CHINA. There are, for example, two new system functions available in Service Pack 2 that permit easy and high-performance access to any tag memory areas. The mobile reader SIMATIC RF610M now also supports EPC IDs with a length of 240 bits. In production, RFID readers are generally connected to the corresponding SIMATIC S7 controllers via interface modules. These controllers manage the connected readers and process the read files or control the production sequence. However, in production scenarios there is also a certain percentage of PC-based RFID workplaces. The Service Pack permits that readers which generally are connected via interface modules can be operated direct on the RF-MANAGER instead.

Newly supported readers This Service Pack supports the following systems with the corresponding serially connected readers: ● RF600 system (UHF range):

– RF620R – RF630R

● RF300 system (HF range): – RF310M

(from the 2nd generation (G2) of the PSION basic device with the MLFB 6GT2803-0AB00)

– RF310R (also supports ISO tags) – RF340R (also supports ISO tags) – RF350R (also supports ISO tags) – RF380R (also supports ISO tags)

Introduction 1.1 Preface


Modified readers ● RF660R with firmware V1.3 ● RF610M Together with the readers that are already supported, the following system overview results:

Control layer

ONS or EDI

(Object Name Service,Electronic Data Interchange)

Acquisition area

Global integration

Business planning

Production control

via ALE interface

RS232 converter> RS422



* Readers are connected via one COM port each on PC ** Readers are connected individually via TCP/IP

Access Point

RF660RRF620R RF630R RF610M/ RF310M

RF310R/ RF340R/ RF350R

RF380R

SIMATIC S7

COM1 - COMx * TCP/IP **

MES(ManufacturingExecution System)

Industrial Ethernet

PROFIBUS

ERP(Enterprise Resource Planning)

SIMATIC RF-MANAGER

ERP(Enterprise Resource Planning)

Ethernet

SCM (Supply Chain Management)

Figure 1-1 RF-MANAGER 2008 SP1 system overview

ALEDataBridgeClient This ALEDataBridgeClient is already fully installed following installation of Service Pack 2, and it can be started via "SIMATIC > RF-MANAGER 2008 Runtime > AleDataBridgeClient". This demo application is based on the ALE+ Client API Library and uses the ALE interface to make files available in .csv (text), .sql (database), and .xml (structured text) formats.

Introduction 1.2 Integration Service Pack


1.2 Integration Service Pack The functionalities of Service Pack 1 and Hotfix 1 published for RF-MANAGER 2008 are already integrated into Service Pack 2. Details on the changes can be found in Annex A (Page 33).

Introduction 1.2 Integration Service Pack



Installation 2Procedure

1. Start the file "RF-MANAGER_2008_SP2.exe" by double-clicking the filename. 2. Follow the on-screen instructions.

Result RF-MANAGER 2008 Service Pack 2 is now installed on your computer. In the installation folder, usually "C:\Program Files\ Siemens\SIMATIC RF-MANAGER\RF-MANAGER 2008 Support", five additional folders have been created by launching Service Pack 2: ● ALEDatabridgeClient

ALEDataBridgeClient is already fully installed following installation of Service Pack 2, and it can be started via "SIMATIC > RF-MANAGER 2008 Runtime > AleDataBridgeClient". This demo application is based on the ALE+ Client API Library and uses the ALE interface to make files available in .csv (text), .sql (database), and .xml (structured text) formats. The documentation for the ALEDataBridgeClient can be found in the folder, along with the source files.

● ALE+Client Demo The ALE+Client Demo is already fully installed following installation of Service Pack 2, and it can be started via "SIMATIC > RF-MANAGER 2008 Runtime > ALE+Client Demo". This demo application is based on the ALE+ Client API Library and uses the ALE interface to provide an overview of the functional scope of the interface. All supported commands can be run, and reports for files and messages can be displayed. Along with the source files, the folder contains comprehensive documentation on the use of the ALE+ interface and the ALE+Client Demo.

● RF610M The "RF610M" folder contains components to be installed on the respective devices if RF610M units are used with RF-MANAGER, as well as the installation documentation.

● RF310M The "RF310M" folder contains components to be installed on the respective devices if RF310M units are used with RF-MANAGER, as well as the installation documentation. Prerequisites: RF310M from the 2nd generation (G2) of the PSION basic device with the MLFB 6GT2803-0AB00

● Project samples The "Project samples" folder contains numerous example configurations for the new devices. The mode of operation of the readers and their integration into the RF-MANAGER can be followed in the projects.

Installation



New functionalities 33.1 RF660R according to ETSI EN 302208 V1.2.1

The RF-MANAGER 2008 Service Pack 2 provides extensions that permit the full support of the new firmware version V1.3 of the SIMATIC RF660R.

Creating new projects When you create new projects for the RF660R reader in RF-MANAGER 2008 Service Pack 2, the new XML messaging version GR_XML_3.0 is automatically set. This ensures compatibility with the new firmware version V1.3 of the reader. The profile "Dense interrogator" is activated as modulation scheme. This XML messaging version is not compatible with older firmware versions of the RF660R reader.

Figure 3-1 System tab

Manual conversion of the XML messaging version If you open projects created with RF-MANAGER 2008 SP 1 or older, the readers in these projects initially keep their old XML messaging version. An automatic conversion to GR_XML_3.0 does not take place. In these projects, however, you can manually convert the XML messaging version of individual RF660R readers from GR_XML_2.0 to GR_XML_3.0. The result is that all channels except for the 4 channels permitted in the 4-channel plan are deactivated for this reader in this project. Therefore, only RF660R readers with firmware version V1.3 are permitted

No LBT/ETSI SRD Note that the procedure "Listen Before Talk" (LBT) is no longer supported with the new ETSI standard EN 302 208 V1.2.1. The "ETSI SRD" radio profile no longer applies.

New functionalities 3.1 RF660R according to ETSI EN 302208 V1.2.1


Compatibility RF-MANAGER versions/reader firmware versions Below you will find an overview of the compatibility of RF-MANAGER versions and RF660R reader firmware versions.

Older RF-MANAGER versions RF-MANAGER 2008 SP2 Reader firmware version GR_XML_2.0 GR_XML_2.0 GR_XML_3.0

V1.1 X X - V1.2 Restricted functionality 1) Restricted functionality 1) - V1.3 X 2) X 2) X

1) In this case the reader firmware's properties are compatible with firmware V1.1 (e.g. no CHINA radio profile permissible)2) No command parameters may be used that are no longer permitted in firmware V1.3.

NOTICE Avoidance of faults If you use RF-MANAGER projects with the old XML messaging version GR_XML_2.0, it is your responsibility to configure your project in agreement with the new ETSI standard EN 302 208 V1.2.1. If you do not do that, this may result in problems in the plant and you might infringe radio regulations. Further information on this and on the possible mixed operation of readers according to ETSI EN 302 208 V1.1.1 und V1.2.1 can be found in the RF600 System Manual.

New functionalities 3.2 Settings for frequency range CHINA


3.2 Settings for frequency range CHINA With RF-MANAGER 2008 Service Pack 2 and the new XML messaging version GR_XML_3.0, RF660R readers V1.3 can also be parameterized with the "CHINA" radio profile. The UHF band ranges from 920.125 MHz to 924.875 MHz in 250 kHz channel increments. There are 16 channels up to max. 2 W (ERP) and 20 channels up to max. 0.1 W (ERP). Further detailed information on the radio profile "CHINA" can be found in the RF600 System Manual, chapter Regulations for UHF frequency bands in China". Select the radio profile via the dropdown menu "Type".

Figure 3-2 Selecting the CHINA radio profile

3.3 Tag ID and user data

Basic procedure As with the previously configurable readers, the tag ID is shown in the RFID display. The recognition and processing of tags usually takes place using the tag ID as identification code. Reading and writing of user data (user memory) takes place using tag selectors with correspondingly configured addresses and lengths. User data or tag IDs can be processed through system functions, RFID data connections, or variables.

Note Please note that the tags of the RF300 series have preset tag IDs which cannot be changed.

New functionalities 3.3 Tag ID and user data


3.3.1 Use of user memory To read or write a tag's user memory via system functions, there are two options:

System functions "SetTagField" and "GetTagField" The following prerequisites must be fulfilled before the function can be used: ● The relevant tag selectors (determination of addresses and size of user memory) must be

defined. To address the user memory in RF300 systems, the value "0 - ISO / RF300" must be chosen as memory bank in the project.

● To read the user memory, the tag selectors must be assigned to the data sources. ● To access the user memory, the reader's data source must be addressed via a workplace

(see below for procedure).

Note For the RF620R/RF630R readers, tag selectors with the bank setting "1 – Gen2 – EPC" and offset "0 – 31" result in an error message. Access is only possible beginning with Offset 32.

System functions "SetTagMemory" and "GetTagMemory" With these new system functions you can read or write to any tag addresses. Tag selectors do not have to be predefined. These system functions can also be addressed via ALE. If no tag ID is indicated and exactly one tag is in the field, this tag is written or read unspecifically. The following prerequisite must be fulfilled before the function can be used: ● To access the user memory, the reader's data source must be addressed via a workplace

(see below for procedure). Further information on the use of user memory can be found in the RF-MANAGER 2008 documentation "Working with RFID Objects".



Creating a workplace 1. In the project window, click on the entry "Workplaces". 2. Then, in the table on the right, double-click an empty field below "Default Workplace".

A new Workplace is created.

Figure 3-3 Creating a workplace

3. Assign a unique name to the workplace. This name is used in the functions over system functions and over ALE as an interface to the reader.

4. Select via "Properties > Synchronous data access". 5. Select the RFID device in the table on the right. 6. Select the Source.



Optional settings for optimization 1. On the tab "Sources", set the Read cycles under Radio settings to 1.

Changing this value results in the following: – On the one hand, if a higher value is set, possible read errors are avoided by multiple

reading. – On the other hand, the read duration is increased, which results in a longer response

time.

Figure 3-4 Sources tab

2. On the tab "Trigger", set "Sources trigger" to "Application Request". If with this data source only system functions are used, the performance can thus be increased since no unnecessary read operations are carried out.

Figure 3-5 Trigger application request

3.3.2 User data also as Array of Bytes Previously, user data and alternative tag IDs could only be made available in the form of string variables. String variables are limited to a length of 255 characters. Because the RF300 tags have a large user memory, from RF-MANAGER Service Pack 1 it is possible to write user data and tag IDs in string variables or in arrays of bytes. Up to 8 KB per tag selector are allowed. If several different user data (different addresses) or larger data amounts are required, a correspondingly larger amount of tag selectors must be configured.

New functionalities 3.4 System function "Delay"


3.4 System function "Delay"

Function The new system function "Delay" is used for implementing an interval when processing function lists or scripts. Note that also subsequent scripts are delayed by executing this system function. You can define the length of the interval yourself.

3.5 Setting parameters for serially connected readers In the following dialog, the parameters of the readers that are now supported due to the Service Pack can be set:

Figure 3-6 Setting reader parameters

The parameters are entered in plain text form. The parameters in the Engineering System are not language-dependent. The parameters and their possible values are shown below. Please note that not all parameters are available to all readers. More detailed information on the significance of the parameters can be found in the RF620R/RF620R Parameterization Manual, the RF300 Product Information, and the manuals for the individual function blocks.

New functionalities 3.5 Setting parameters for serially connected readers


Parameters for RF300 readers Parameter Value range Default Description ComPort COM1 ... COMxx COM1 Serial interface to be used for communication with the

reader. Baudrate Decimal value:

19200, 57600, 115200

115200 Baud rate to be used for communication with the reader.

CommandTimeout 1 Decimal value: 20 ... 1000

100 Time in milliseconds in which the reader must process commands.

LongCommandTimeout Decimal value: 2000 ... 10000

3000 Time in milliseconds in which the reader must process long commands.

RF300Enabled Boolean value: true or false

true Activates the RF300 protocol on the air interface (transponder), see MOBY manuals, parameter "field_ON_time"

Iso15693Enabled Boolean value: true or false

false Activates the ISO15693 protocol on the air interface (transponder), see MOBY manuals, parameter "field_ON_time

IsoTagType Hexadecimal value: 01 ... 07

01 Type of ISO tag used 01 hex = Manufacturer-independent tag 03 hex = ISO my-d(Infineon SRF 55V10P) 04 hex = ISO(Fujitsu MB89R118) 05 hex = ISO I-Code SLI(NXP SL2 ICS20) 06 hex = ISO Tag-it HFI(Texas Instruments) 07 hex = ISO (ST LRI2K),

see MOBY manuals, parameter "field_ON_time"

WithPresence 2 Boolean value: true or false

false Activates presence control, see MOBY manuals, parameter "MDS_control"

RFID AntennaPower Hexadecimal value: 02 ... 08

05 Antenna performance 02 hex = 0.5 W 03 hex = 0.75 W 04 hex = 1.0 W 05 hex = 1.25 W 06 hex = 1.5 W 07 hex = 1.75 W 08 hex = 2.0 W See MOBY manuals, parameter "distance_limiting"

ResetOfLed Boolean value: true or false

true Activates restart of the ERR-LED, see MOBY manuals, parameter "option_1"

HeartBeatInterval 1000 ... 20000 2000 Time in milliseconds in which the heartbeat is sent to the reader.



Parameter Value range Default Description scanning_time Hexadecimal value

00 Expert settings for air interface,

see MOBY manuals, parameter "scanning_time" field_ON_control Hexadecimal value

00 Expert settings for air interface,

see MOBY manuals, parameter "field_ON_control" 1) If errors in communications or in writing data to the transponder occur sporadically, it may be necessary to increase the

value for CommandTimeout. This is necessary if several protocols are simultaneously activated or if larger data amounts are written to ISO transponders (typical value: 300).

2) If presence is activated (WithPresence = true), only one protocol may be activated (either RF300enabled or Iso15693Enabled)

Parameters for RF620R/RF630R readers Parameter Value range Default Description ComPort COM1 ... COMxx COM1 Serial interface to be used for communication with the

reader. Baudrate Decimal value:

19200, 57600, 115200

115200 Baud rate to be used for communication with the reader.

CommandTimeout Decimal value: 100 ... 1000

250 Time in milliseconds in which the reader must process commands.

LongCommandTimeout Decimal value: 2000 ... 10000

3000 Time in milliseconds in which the reader must process long commands.

MultiTag

Boolean value: true or false

false Activates MultiTag mode, see MOBY manuals, parameter "MOBY_mode"

MaxNumberofTags Decimal value: 1 ... 40

15 Maximum number of tags in the field that can be processed in parallel. See MOBY manuals, parameter "Multitag"

WithPresence Boolean value: true or false

true Activates presence control, see MOBY manuals, parameter "MDS_control"

Antenna01Power Hexadecimal value: 00 ... 0F

00 Performance of Antenna 01 0 ≙ 18 dBm (65 mW) 1 ≙ 19 dBm (80 mW) ... 9 ≙ 27 dBm A(...F) ≙ 27 dBm (500 mW)

Antenna02Power Hexadecimal value: 00 ... 0F

00 Performance of Antenna 02 0 ≙ 18 dBm (65 mW) 1 ≙ 19 dBm (80 mW) ... 9 ≙ 27 dBm A(...F) ≙ 27 dBm (500 mW)



Parameter Value range Default Description RadioProfile Hexadecimal

value: 01 ... 05

01 Radio profile according to EPC Global 00 hex = no standard selected 01 hex = autodetect: Default profile depending on

reader type (ETSI, FCC) For ETSI readers: ETSI new: EU, EFTA, and Turkey ETSI EN 302 208 V1.2.1 (4-channel plan)

02 hex = ETSI new: EU, EFTA, and Turkey correspond to the standard ETSI EN 302 208 V1.2.1 (4-channel plan)

03 hex = ETSI old: EU, EFTA, and Turkey correspond to the standard ETSI EN 302 208 V1.1.2

04 hex = FCC (e.g. USA, Canada) 05 hex = China

Channels Hexadecimal value: 00 ... 0F

00 (all channels on)

Defines the active channel Bit 0=865.7 MHz Bit 1=866.3 MHz Bit 2=866.9 MHz Bit 3=867.5 MHz See MOBY manuals, parameter "field_ON_time"

ResetofLeds Boolean value: true or false

true Activates restart of the ERR-LED, see MOBY manuals, parameter "option_1"

HeartBeatInterval 1000 ... 20000 2000 Time in milliseconds in which the heartbeat is sent to the reader.

field_ON_control Hexadecimal value 02 Expert settings for air interface, see MOBY manuals, parameter "field_ON_control"

Note For the newly supported readers, the antenna performance must be set in the properties table. The value under the antenna tab is not relevant. In general, in the overview of all readers many properties are shown that are only relevant for the RF660R and RF610M readers. Properties of the newly supported readers that cannot be set are ignored.

See also Support homepage (www.siemens.com/automation/service&support)

http://www.siemens.com/automation/service&support�

New functionalities 3.6 Operating modes with serial readers


3.6 Operating modes with serial readers The following operating modes are supported: ● Single tag without presence

Continuous cyclic reading from the RF-MANAGER takes place. ● Single tag with presence

Cyclic reading from the RF-MANAGER only takes place after a reader presence message has been received.

● MultiTag without presence (only RF620R/RF630R) Continuous cyclic reading from the RF-MANAGER takes place.

● MultiTag with presence (only RF620R/RF630R) Cyclic reading from the RF-MANAGER only takes place after a reader presence message has been received.

In all operating modes, the RF300 readers provide 8 bytes for the tag ID. The RF620R/RF630R readers provide 12 bytes for the tag ID to the RF-MANAGER.

Note The activation of the operating mode with presence (WithPresence = true) causes commands to be sent only to the reader if at least one tag is in the field.

In addition the presence is made available in the form of a virtual input (as InPort00). To be able to evaluate the presence in the application, this input can be addressed as a variable. Likewise, the input can be used to set a trigger. If a trigger of type "IO edge" or "I/O level" is linked to this input, the activation is dependent on presence. Examples: With the "IO edge" type, as soon as a tag enters the field, a single read process is initiated. With the "IO level" type, reading takes place as long as a tag is in the field.



New functionalities 3.7 Supported tag types


3.7 Supported tag types

RF300 reader All RF300 readers (RF310M, RF310R, RF340R, RF350R, and RF380R) support RF300 tags and ISO tags. Both tag types may be activated with RF-MANAGER. Both tag types (RF300 and ISO) can be used simultaneously - with reduced read performance, however.

RF600 reader All the tags released for the RF600 readers (RF660R, RF620R, RF630R, RF610M) are supported by RF-MANAGER. Check back regularly at the Siemens Service&Support site in the intranet to find out if new tag types have been released for the readers.

RF610M With EPC Global Gen 2 Tags, IDs with all defined lengths are now supported, also IDs with a length of 240 bits. The following new tag types are supported: ● RF680T ● RF630L Smartlabel: 6GT2810-2AB03 ● RF630T ● RF640T Gen 2

RF310M The following new tag types are supported: ● MDS D428 ● MDS D460

New functionalities 3.8 ALEDataBridgeClient


3.8 ALEDataBridgeClient In addition to the support for new RFID devices, the Service Pack also contains a further sample application to connect to the ALE interface of the RF-MANAGER.

Functions This "ALEDataBridgeClient" can transform RFID data that was collected by the readers, processed by RF-MANAGER, and provided to the client via the ALE interface into a series of standard formats. CSV and XML formats are supported, as well as writing to an SQL database. The contents of the table can be defined via the client. The client is also supplied as binary file and in source code. In this way, it can also serve as a basis for custom applications.

Figure 3-7 ALEDataBridgeClient

New functionalities 3.8 ALEDataBridgeClient



Connection options through serial communication 44.1 Connecting principle

RF-MANAGER connection options The readers of the RF300 series as well as the RF620R and RF630R UHF readers are connected to the PC via a serial COM interface. For this an RS232 to RS422 interface converter is needed. The RF380R reader has both RS422 and RS232 interfaces and can thus be directly connected to the PC using an RS232 cable (Page 35). The SIMATIC RF310M mobile handheld terminal operates via WLAN and is thus connected to the RF-MANAGER in the same way as the RF610M. More information on the SIMATIC RF310M mobile handheld terminal can be found in the Operating Instructions SIMATIC RF310M Mobile Reader.

Tested interface converters The following interface converters were used by Siemens in the test: ● Trycom IP interface converter: "TRP-C06". ● EXSYS GmbH interface converter card: "EX-42054-9-8S" with 8 interfaces. ● EXSYS GmbH interface converter card: "EX-42052-9-2S" with 2 interfaces. Interface converters that do not work with RS232 but are connected to the PC via, for example, Ethernet or USB are not recommended. In general, these do not meet the timing requirements demanded by the protocol. When using an interface converter, the following pin assignment should be observed.

Connection options through serial communication 4.2 Pin assignment for TRP-C06 interface converter


4.2 Pin assignment for TRP-C06 interface converter

Pin assignment and wiring diagram for interface converter Trycom IP interface converter: "TRP-C06" is an external unit to convert RS232 to RS422 and vice versa. To commission the interface converter, connect the wires of the reader cable (Order No. 6GT2891-0EH50) to the correct terminals on the interface converter and the power supply/ground (GND). The following graphic shows an example of a wiring diagram:

Figure 4-1 TRP-C06 wiring diagram

Connection options through serial communication 4.3 Pin assignment connector EX-42054-9-8S interface converter card


4.3 Pin assignment connector EX-42054-9-8S interface converter card The interface converter card EX-42054-9-8S is installed in the PC. A driver is installed for each interface so that 8 additional COM ports become available. A connector matching the 8 interfaces must be mounted on the reader cable. The following figure gives an example of a pin assignment for a connector on an RS422 reader cable (Order No. 6GT2891-0EH50) as well as the power supply for the reader:

Figure 4-2 Connector pin assignment EX-42054-9-8S and reader power supply

Note Same pin assignment for the interface converter card EX-42052-9-2S For the interface converter card EX-42052-9-2S a connector with the same assignment as shown above must be installed.

4.4 Number of readers The maximum number of readers connected simultaneously to a single computer with serial communications depends largely on the computer's performance. In the system test a standard PC (see system requirements) with 8 readers was tested. Insufficient computer performance can lead to connection interruptions or communication errors. On the Microbox with a serial interface, a reader with serial communications was tested.

Connection options through serial communication 4.4 Number of readers



Constraints 55.1 Operating modes

The following constraints apply with regard to operating modes:

Note Constraints The "MultiTag" mode is not supported by the RF300. The "Repeat command" and "Command chaining" options are not supported.



Constraints 5.2 System functions and commands


5.2 System functions and commands

Constraints with RF300 system

NOTICE Error message in Runtime Note that the following presently available system functions are not supported by RF300 readers: Writing tag IDs LOCK and KILL functions Password protection of tags If such system functions are configured with an RF300 reader, they will not be intercepted in the Engineering System. A corresponding error message will appear in Runtime.

Command chaining is not supported. The following commands are supported by RF300 readers, but are not offered as system functions in RF-MANAGER: ● Initialization of tags ● SetAnt (switching antenna on and off) ● MDS status ● SLG status However, the general system function "SendCommand" is available. All reader commands can be mapped with this system function. A corresponding message frame (max. length: 254 bytes) is sent to the RFID reader and another message frame is received in reply. You must interpret the reply yourself. Changes to reader parameters set in the Engineering System (ES) cannot be accepted permanently by implementing this system function. For example, after restarting or a communication failure, the original values defined in ES are set in the reader by the Runtime.

5.3 Further restrictions In the Engineering System and in the configuration display in Runtime, the following special characters may not be used:


Appendix A AA.1 Changes for SIMATIC RF-MANAGER 2008

Changes regarding the RF-MANAGER 2008 The problems described below describe the status before introducing the Service Pack. These problems are resolved by installing the Service Pack. 1. Frequent reading and setting of the digital inputs/outputs of the RF660R

If the digital inputs/outputs of the RF660R reader are read or set frequently and at short intervals via an ALE client, this can block communication via the ALE interface of the RF-MANAGER.

2. Unnecessary setting of the digital outputs of the RF660R If a variable of the type "Byte" with the address "Inport00-Inport02", which displays the state of the reader inputs, is set incorrectly, the digital outputs of the reader are unnecessarily reset. In future, attempts to set the digital inputs via a byte variable will be rejected with a system message. This is analogous to the behavior with Boolean variables.

3. Digital inputs/outputs cannot be selected with the ALE demo client. The relevant digital inputs/outputs of the reader cannot be selected with the command "Get/SetIoPort" in the ALE demo client.

4. RFID data connection with internal acknowledge variable If an RFID data connection is operated in the coordination mode "Acknowledge variable", and if the provided tag data is evaluated within a script and then the acknowledge variable is reset in the same script, the result can be that the acknowledgment is not detected and consequently no more tag data is provided. This effect only occurs if the acknowledge variable is an internal variable.

5. Ethernet connection to the S7 controller Without this hotfix, the Ethernet connections between the RF-MANAGER and a SIMATIC S7 controller only function fully if WinCC flexible or STEP7 is installed on the runtime PC.

6. Selection of the "Dense interrogator" mode for the RF660R only with activated frequency-hopping procedure If the tag protocol "EPC Class1 Gen2" with the modulation scheme "Dense interrogator" is selected for the RF660R, the frequency-hopping procedure will necessarily be activated in the radio settings. This option cannot be used with a fixed channel.

7. No data forwarding if there are several data sources on one notification channel If a large number of tag readings occurs over several data sources on one notification channel, this can block forwarding of the tag data.

8. Double transfer of tag readings to the ALE client If the ALE client acknowledges the transfer of tag readings very quickly in transaction mode, it can happen in rare cases that data is transferred twice to the ALE client after timeout of the set transaction.

9. Optimization of the project tree In future, after opening or creating a project in RF-MANAGER Engineering System, only the "Topology" folder will still be opened automatically.

Appendix A A.1 Changes for SIMATIC RF-MANAGER 2008


10. Executing the RFID function "ReadTagField" When executing the RFID function "ReadTagField", errors could occur in some rare cases.

11. Linking system functions to RFID device messages If you wanted to link system functions to specific events of RFID device messages, it was possible that error messages were displayed when generating the project.

Changes with regard to the RF610M operating together with RF-MANAGER 2008 1. No forwarding of tag data on the RF610M

If the handheld RF610M is operated in connection with the RF-MANAGER, it can happen that not all data is transferred from the RF610M to the RF-MANAGER. This can be the case if there is currently no WLAN connection to the RF-MANAGER, and RF-MANAGER Runtime on the PC is stopped and restarted again (e.g. through activation of a new configuration). If the WLAN connection is then established again, tag data that was read on the RF610M in the meantime can be lost.

2. Delayed display of barcode on the RF610M If the "Target help duration" for the barcode is activated in the RF-MANAGER, it can happen that the scanned barcode is recorded, but not displayed until the next read operation.

3. The trigger "Read first ID" does not function correctly on the RF610M If the read trigger is set to "Application" with the key type "Read first ID" in the RF-MANAGER for the RF610M, the read operation on the RF610M will be triggered after this function is initiated, but it will not be completed on detection of the first tag ID. Only after the trigger is set several times (using the scan button) will the read process be ended.

4. No access to the read head of the RF610M after execution of "StopReader" If the API function "StopReader" is executed in a customized application, a connection can no longer be made to the read head of the RF610M. The status can only be corrected when the customized application is restarted on the RF610M.

Appendix A A.2 Reader RF380R (RS232) - PC


A.2 Reader RF380R (RS232) - PC The connecting cable (6GT2891-0KH50) is 5 m long. Special feature of the cable: additional branch for the power supply.

Figure A-1 Connecting cable RF380R (RS232) to the PC

Suitable power supply unit: e.g. wide-range power supply unit

Table A- 1 Ordering data for wide-range power supply unit

Wide-range power supply unit for SIMATIC RF-systems (100 - 240 V AC / 24 V DC / 3 A) with 2 m connecting cable with country-specific plug

EU: 6GT2898-0AA00 UK: 6GT2898-0AA10 US: 6GT2898-0AA20

www.siemens.com/automation

subject to changeA5E02472233-02© Siemens AG 2009

Siemens AGIndustry SectorFactory Automation SensorsPostfach 48 4890327 NÜRNBERGDEUTSCHLAND

www.siemens.com/simatic-sensors

Get more Information

simatic rfid systems rf-manager 2008 service pack 2...with a safety alert symbol, indicates that...

Documents