SIMATIC RF-MANAGER 2008
_
_________________
_
_
_________________
_
_
_______________
_
__
_
_________________
_
_
_________________
_
SIMATIC
RFID systems
SIMATIC RF-MANAGER 2008
Getting Started
06/2010
A5E01070047-03
Foreword 1
RF-MANAGER components
2
Installing the RF-MANAGER
3
Using the sample project
4
Project representation in the
RF-MANAGER
5
Legal information
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
A5E01070047-03
Ⓟ 07/2010
Copyright © Siemens AG 2010.
Technical data subject to change
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 3
Table of contents
1 Foreword ................................................................................................................................................... 5
1.1 About this manual ..........................................................................................................................5
1.2 Further information.........................................................................................................................6
2 RF-MANAGER components ...................................................................................................................... 7
3 Installing the RF-MANAGER...................................................................................................................... 9
3.1 System requirements .....................................................................................................................9
3.2 Software installation.....................................................................................................................10
3.3 Installation Service Pack..............................................................................................................12
4 Using the sample project ......................................................................................................................... 15
4.1 Description of the project .............................................................................................................15
4.2 Starting the project with the simulator..........................................................................................16
4.3 Using the project ..........................................................................................................................19
4.4 Connecting the project to the enterprise system .........................................................................28
4.5 Connecting the project to the ALE interface ................................................................................30
5 Project representation in the RF-MANAGER ........................................................................................... 33
5.1 Programming interface of the engineering system ......................................................................33
5.2 RFID function blocks....................................................................................................................35
5.2.1 RFID device .................................................................................................................................35
5.2.2 Workplaces ..................................................................................................................................39
5.2.3 RFID data link ..............................................................................................................................40
5.2.4 ALE connections ..........................................................................................................................41
5.3 Screens........................................................................................................................................42
5.3.1 Scenario screens .........................................................................................................................42
5.3.1.1 Basic settings and procedures.....................................................................................................43
5.3.1.2 Labeling........................................................................................................................................48
5.3.1.3 Sorting..........................................................................................................................................52
5.3.1.4 Gates (outgoing goods) ...............................................................................................................55
5.3.2 System screens............................................................................................................................58
5.3.2.1 Configuration................................................................................................................................59
5.3.2.2 Alarms..........................................................................................................................................59
Table of contents
SIMATIC RF-MANAGER 2008
4 Getting Started, 06/2010, A5E01070047-03
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 5
Foreword 1
1.1 About this manual
Purpose of the manual
This document introduces you to the fundamental configuration possibilities of RF-
MANAGER 2008 for RFID systems based on the RFID sample project
Getting_Started_2008.rfid that is included in the scope of supply. Since the project is
operated with a simulator, hardware connection of the readers is not necessary.
The sample project represents an extremely simplified RFID scenario. It makes no claim to
be implementable in practice.
The sample project can be found on the CD in the path: Documents\English\GettingStarted .
The manual is aimed at first-time users and project engineers who are employed in the areas
of project engineering, commissioning and servicing of RFID systems using SIMATIC RF-
MANAGER 2008.
Required basic knowledge
General experience in the field of automation technology and RFID technology is essential
for understanding this manual. Knowledge of the EPCglobal Application Level Events (ALE)
Specification is also required.
It is assumed that the reader is competent in the use of personal computers with the
Windows XP Professional operating system.
Conventions
In this manual, the product SIMATIC RF-MANAGER 2008 is also referred to as RF-
MANAGER.
Area of application
The manual is applicable to SIMATIC RF-MANAGER 2008 and describes the delivery status
of June 2010.
History
Edition Remark
02/2007 Initial release
04/2008 Edited version for RF-MANAGER 2008
06/2010 Edited version for RF-MANAGER 2008 with RF670R
Foreword
1.2 Further information
SIMATIC RF-MANAGER 2008
6 Getting Started, 06/2010, A5E01070047-03
1.2 Further information
You can obtain further information about SIMATIC RFID systems, for example, from the
following documentation:
● SIMATIC RF-MANAGER Information System
● SIMATIC RF-MANAGER Configuration and Operating Manual
● SIMATIC RF-MANAGER Function Manual
● SIMATIC RF600 System Manual
● SIMATIC RF-MANAGER Basic 2010 Configuration and Operating Manual
● SIMATIC RF670R Function Manual
● SIMATIC RF660R Configuration Software Programming and Operating Manual
● SIMATIC RF660R XML Interface Function Manual
● SIMATIC RF660R Getting Started
● SIMATIC RF610M Operating Instructions
● SIMATIC RF610M Function Manual
The documentation can be downloaded from the Siemens Service & Support pages.
Additional information regarding RFID and the EPCglobal Application Level Events (ALE)
Specification can be downloaded fromEPCglobal site at www.epcglobalinc.org.
Note
Detailed information is available in the Information System
The SIMATIC RF-MANAGER Configuration and Operating Manual offers a comprehensive
overview of the RF-MANAGER. You can find detailed information on the topics addressed
there in the online help (Information System).
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 7
RF-MANAGER components 2
The RF-MANAGER comprises the following components:
● RF-MANAGER Engineering System
● RF-MANAGER Runtime
RF-MANAGER Engineering System
The RF-MANAGER Engineering System is the software for handling all your essential
configuring tasks. You can use the Engineering System to create RFID projects on your PC
and to parameterize their components.
RF-MANAGER Runtime
RF-MANAGER Runtime is the software that is used to operate RFID systems. In Runtime,
you can execute the RFID projects during plant operation that you created and
parameterized in the Engineering System. The Runtime software can run either on the same
PC as the Engineering System, or on another Windows XP-PC of your choice. The SIMATIC
Microbox PC 420 and the SIMATIC PC Microbox 427B are also an option for Runtime.
Depending on the RF-MANAGER product version/license you have selected, you can
address up to 50 RFID readers with the Runtime software. Later license extensions for the
Runtime software can also be obtained.
RF-MANAGER components
SIMATIC RF-MANAGER 2008
8 Getting Started, 06/2010, A5E01070047-03
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 9
Installing the RF-MANAGER 3
3.1 System requirements
System requirements
RF-MANAGER Engineering System RF-MANAGER Runtime
Supported devices Standard PC Standard PC / SIMATIC Microbox PC 420 /
SIMATIC Microbox PC 427B
Operating system Windows XP Professional SP3 or higher
Windows XP Professional SP3 or higher
(standard PC)
Windows XP Embedded SP3 or higher
(SIMATIC Microbox PC 420/
SIMATIC Microbox PC 427B)
CPU Pentium IV or later
with 1.6 GHz processor
Pentium III or later
with 933 MHz processor
(standard PC)
Pentium III with at least 933 MHz processor
(SIMATIC Microbox PC 420/
SIMATIC Microbox PC 427B)
Graphic Resolution of at least 1024x768 / 1280x1024
recommended
at least 256 colors
Resolution of at least 640x480
at least 256 colors
RAM At least 1.0 GB / 2.0 GB recommended At least 512 MB / 1024 MB recommended
At least 1.5 GB At least 256 MB
excluding archives
(standard PC)
CompactFlash card with at least 512 MB
(SIMATIC Microbox PC 420/
SIMATIC Microbox PC 427B)
Free memory space /
hard disk
In addition to the space needed by RF-MANAGER, Windows also requires space on the hard
disk, e.g. for the swap file. For additional information, refer to your Windows documentation.
Additional hardware CD-ROM drive (for installing the software)
USB port for installing the licenses
Reader for document
display
Adobe Acrobat Reader 5.02
Internet browser Microsoft Internet Explorer V6.0 SP1 / SP2
Multiple screens The operating system function used to visualize the screen content on several monitors (Control
Panel > Display > Settings) is not released with RF-MANAGER.
Note
Engineering System and Runtime System on the same PC
Engineering System and Runtime can be operated on one PC at the same time.
Installing the RF-MANAGER
3.2 Software installation
SIMATIC RF-MANAGER 2008
10 Getting Started, 06/2010, A5E01070047-03
Reader
A simulator is supplied with RF-MANAGER. The configured readers and predefined tag
events and inputs of the reader can be simulated using a simulation file created for the
sample project. For this reason, a hardware connection between your PC and readers of the
RF600 family or a PLC is not necessary for using the sample project.
3.2 Software installation
Installation
The RF-MANAGER Engineering System software is located on the CD "SIMATIC RF-
MANAGER". A license (license key) is required to run the software.
NOTICE
If you start the RF-MANAGER without a valid license, the system alerts you that you are
working in non-licensed mode. You have the option, once only, of activating a trial license.
The trial license expires after 14 days.
If the trial license expires, one of the following applies:
On the computer in question, a main license was never installed
– RF-MANAGER cannot be started.
On the computer in question, a main license was once installed
– RF-MANAGER can be started, but the system alerts you at short intervals that you
are working in non-licensed mode.
1. If the autorun function is enabled for your CD-ROM drive, setup is run automatically when
the CD is inserted. Otherwise, start the program "setup.exe" from the CD.
2. Select the user interface language of the Setup program under "Language."
Installing the RF-MANAGER
3.2 Software installation
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 11
3. Display the product information and accept the licensing conditions in the subsequent
window.
4. Select the drives for the installation data. If you select the option "Transfer license key
automatically", you must also specify the source and destination of the license key. If you
do not select this option, messages will appear frequently during operation that must be
confirmed.
5. Select the components to be installed.
6. Follow the instructions on the screen.
Installing the RF-MANAGER
3.3 Installation Service Pack
SIMATIC RF-MANAGER 2008
12 Getting Started, 06/2010, A5E01070047-03
Note
If, when installing the software, you do not have a license, you can install this later using the
Automation License Manager.
3.3 Installation Service Pack
Requirement
SIMATIC RF-MANAGER 2008 must be installed.
Procedure
1. Start the file "SIMATIC_RF-MANAGER_2008_SP3.exe" by double-clicking the file name.
2. Follow the on-screen instructions.
Result
RF-MANAGER 2008 Service Pack 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 the
Service Pack:
● ALEDatabridgeClient
ALEDataBridgeClient is already fully installed following installation of the Service Pack,
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 the Service Pack,
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.
Installing the RF-MANAGER
3.3 Installation Service Pack
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 13
● 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.
Installing the RF-MANAGER
3.3 Installation Service Pack
SIMATIC RF-MANAGER 2008
14 Getting Started, 06/2010, A5E01070047-03
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 15
Using the sample project 4
The following will familiarize you with the sample project. As well as a description of the
project, this also includes a run down of the possible uses.
You can try out the individual components of the project in Runtime using the simulator
included in the scope of supply. The simulator is used to simulate operation of the readers
configured in the Runtime system as well as pre-defined tag events.
4.1 Description of the project
The sample project represents a simplified RFID scenario. This scenario consists of an RF-
MANAGER Workstation to which three readers and a PLC are connected. In addition, there
is an ALE connection between the RF-MANAGER Workstation and a higher-level enterprise
system. The readers and the functionalities connected with them are the central elements of
the scenario.
Labelling
The reader "Reader_Labeling" is controlled via a light barrier and uses two antennas to
monitor a conveyor belt via which goods are transported in crates. These goods are destined
for different recipients. Each crate is equipped with a tag.
Using the sample project
4.2 Starting the project with the simulator
SIMATIC RF-MANAGER 2008
16 Getting Started, 06/2010, A5E01070047-03
When a crate breaks through the light barrier, the conveyor belt stops automatically and the
reader reads the current tag. The current values are displayed in an appropriate screen. It is
now possible to edit the values and write the changed values to the tag. A distinction is made
between two types of crates here: After the write, the conveyor runs again.
Sorting
The goods must be sorted in a second step. There is a separating filter for this purpose
downstream of the conveyor that determines the pallet to which the goods should be
directed. When the light barrier is broken, the reader "Reader_Sorting" reads the tag with its
two antennas. The values are supplied to a PLC. The separating filter is set by the PLC
according to the read results.
Downstream of the separating filter, the crates are loaded onto pallets. Each crate is
equipped with a tag. An additional tag is also applied to each pallet. The additional tags too
receive tag data specific to the goods recipient.
Outgoing goods
The reader "Reader_Gates" uses two antennas to monitor each outgoing goods gate. At
each outgoing gate, the tags of the pallet and the crates that are located on it are read. The
values are evaluated in a script. This allows you to check whether the correct pallets
complete with the correct goods are ready at the recipient-specific outgoing goods gate.
Incorrect pallets are stopped and must be acknowledged. Permitted pallets are loaded
immediately.
The read results of the reader are forwarded by the Runtime software to the higher-level
enterprise system via the ALE interface.
4.2 Starting the project with the simulator
The RF-MANAGER is supplied with simulator software which you can use to test the
components of the sample project. The simulator is a separate application. You can use the
simulator to simulate operation of the readers configured in the Runtime system as well as
pre-defined tag events and reader inputs.
Using the sample project
4.2 Starting the project with the simulator
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 17
Simulation of readers and tags
The simulator works with pre-defined and modifiable simulation tables
"Getting_Started_2008.Device_1.rfidsim". These are opened automatically. RFID jobs with
tag events have already been created in the simulation tables for each of the three readers.
These jobs are mutually independent and can execute once only or in cycles.
Each job is assigned a tag ID for the simulation. The parameters "OnTime" / "OffTime" define
how long the tag of the corresponding job is within the measuring range of the reader
antenna (visibility). If the job is cyclical, the ratio of visible/invisible is set using the two
parameters.
When an input is configured for the trigger condition, the job is triggered in accordance with
the parameters set. Special characters (wildcards) can be used in the tag ID to generate
random tag IDs (see the online help of the simulator). Similarly one job can be used to
generate several tags when the number is greater than 1 and the random pattern is set
appropriately.
The created jobs can be set to active or inactive. If you want to modify the simulation table,
you can also reproduce the jobs, for example, and then delete individual jobs.
Note
Changes to existing tag jobs
If you change the type (leading characters), length of the tag or the trigger conditions, the
functionality in the project may no longer be assured.
Using the sample project
4.2 Starting the project with the simulator
SIMATIC RF-MANAGER 2008
18 Getting Started, 06/2010, A5E01070047-03
Starting the project with the simulator
Note
Engineering System and Runtime System on the same PC
The sequence of actions described below refers to the scenario in which the Engineering
System and Runtime are installed on the same PC.
If you operate the Engineering System and Runtime on different PCs, you will find the
information on transferring and starting projects in the
SIMATIC RF-MANAGER
Configuration and Operating Manual
.
1. Unzip the file "Getting_Started.exe" from the CD in the path:
Documents\English\GettingStarted into a directory of your choice.
2. Start the RF-MANAGER Engineering System, either by clicking the desktop icon on the
programming device or by selecting it from the Windows Start menu.
3. In the Engineering System, select the option "Open existing project".
4. Navigate in the path used above to the project file Getting_Started_2008.rfid".
5. Click "Open".
The project opens.
6. If you are asked if the project has been created with an older RF-MANAGER version and
if you would like to convert, confirm this message with "Yes". Usually this query is only
displayed if there is an installed ServicePack.
7. Click on "Project / Generator / Start Runtime with simulator".
The already created simulation table for the sample project is opened by the simulator
automatically. All the settings made for simulation of the project are stored in the
simulation table "Getting_Started_2008.Device_1.rfidsim". The simulator then starts the
Runtime software and starts to simulate the values.
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 19
4.3 Using the project
The Start screen appears after starting the project in Runtime. The sample scenario is
visualized on this screen.
You can reach other screens using the buttons of the start screen. These can be grouped as
follows:
Scenario screens:
● Labelling
● Sorting
● Outgoing goods
System displays:
● Configuration
● Alarms
In addition, language switching can take place in the start screen and Runtime can be
terminated. You can jump back to the start screen from any other screen.
If alarm events occur during operation of the sample project, these are automatically
visualized via the alarm window. The alarm window cannot be selected via a button, but
appears automatically at each alarm event.
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
20 Getting Started, 06/2010, A5E01070047-03
Labelling
The "Labeling" button takes you to a screen that shows the functionality of labeling:
1. Select the "Start conveyor" button.
When a crate breaks the light barrier, the conveyor belt is stopped and the tag is read.
The read data is supplied in the form of variables over an RFID data link and displayed
under "Current tag ID". The tag ID is presented in raw hexadecimal format and after
conversion in tag format. The serial number is then extracted from the tag format. You
can now check the serial number and change it if necessary.
2. This is done by editing the "Serial number" input field and confirming it with the <Return>
key.
The changed tag ID overwrites the current values in the display fields under "New tag ID".
3. Select the button "Write tag ID" to write the changed serial number to the tag.
After the ID has been written again, the conveyor will run. The crate will be displayed in
different colors in accordance with the assigned serial number:
– Odd serial number: Red crate
– Even serial number: Green crate
4. Select the "Stop conveyor" button to stop the scenario. Click the "Back" button to display
the start screen again:
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 21
Sorting
The "Sorting" button takes you to a screen that shows the functionality of sorting:
1. Select the "Start conveyor" button.
When a crate breaks the light barrier, the tag ID is read. The read data is supplied to the
PLC in the form of variables over an RFID data link. The PLC is switched offline for the
simulation. The control program evaluates the tag IDs and decides on the basis of the
serial number (even or odd) how the separating filter of the conveyor should be set:
– Red crates (uneven serial numbers) upwards
– Green crates (even serial numbers) downwards
The read-out data is also displayed in the top right-hand area of the screen.
The bottom section of the screen has an integral RFID view, via which the currently read
tag ID, the workplace used, the reader, the date and the time-of-day of the read
operation, as well as the status description of the read tag, can be displayed.
2. Select the "Stop conveyor" button to stop the scenario. Click the "Back" button to display
the start screen again:
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
22 Getting Started, 06/2010, A5E01070047-03
Outgoing goods
The "Outbound log." button takes you to a screen that shows the functionality of outbound
logistics:
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 23
1. Choose between red and green crates/pallets using the selection fields next to the
respective pallets.
In this manner you specify whether even (green) tag IDs or odd (red) tag IDs are
randomly generated.
2. The pallets can then be conveyed to an outgoing gate. Select the appropriate "Move
pallet" button for this.
At the top red outgoing gate, the reading procedure is automatically triggered by a light
barrier. At the lower green outgoing gate, the reading procedure must be activated
manually by clicking the "Read pallet" button.
During the reading procedure, all the tags on the pallet are read out. The read data is
supplied in the form of variables over the RFID data link. The tag IDs are evaluated in a
script.
– When a green pallet is located at the red gate of outbound logistics or vice-versa, a
red Stop sign flashes after the read and the pallet is stopped. The number of incorrect
tag IDs is displayed in the left-hand section of the screen. The pallet must then be
manually returned to its initial position using the appropriate "Reset pallet" button.
– If the pallet with its tag IDs is correct for the gate of outbound logistics, after reading it
is pushed through the gate and loaded.
The top section of the screen has an integral RFID view, via which the read tag read
events, the data source used, the time of the read operation, as well as the status
description of the read tag, can be displayed. The most recent read events are shown
above.
You can:
– Delete events
– Change the column sequence
– Change the respective column width
The buttons have the following functions:
button Function
Delete all events
1. Click the "Back" button to display the start screen again:
The following settings in the simulator are used for simulation:
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
24 Getting Started, 06/2010, A5E01070047-03
The crate/pallet to be simulated is controlled via the selection fields and the associated
Inport01 of the reader:
● Inport01 set to LOW ensures that the two top tag jobs are generated with odd tag IDs.
● Inport01 set to HIGH ensures that the two bottom tag jobs are generated with even tag
IDs.
The tag job with the number 4 represents 4 crates on the pallet and the other tag job
represents the tag on the pallet.
You can change the scenario by editing the number of crates or the tag IDs for the crates.
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 25
Configuration
The "Configuration" button takes you to a screen in which changes can be made to the
project configuration in Runtime:
Individual components of the project can be re-parameterized via this screen. In the left
window area, these components are visualized in the form of a tree structure. When
individual components are selected, the associated parameters and their values appear in
the right-hand window area. If you want to edit a value, click in the appropriate field and
make the change.
The status symbols in the tree structure have the following meaning:
Symbol Description
The components and their subcomponents are ready for operation
The component and its subcomponents are not ready for operation
The status of the components cannot be determined
The components and their subcomponents are not in a uniform state
You can:
● Edit the values of parameters
● Delete parameters
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
26 Getting Started, 06/2010, A5E01070047-03
● Add parameters
● Change the column sequence
● Change the respective column width
The buttons have the following functions:
button Function
Delete parameters
Add parameters
Open up the tree structure
Activate changes to the project. The changes are not saved and will be lost
when the runtime system is rebooted. It is generally recommended that the
changes be simply activated and then the new project configuration tested.
Activate and save changes to the project. Following a successful test, the
changes can be saved. Only saved changes can be synchronized with the
Engineering System. To prevent loss of data, note that all changes
implemented subsequent to the last archived status will be saved.
Undoing changes to the project. If a new project configuration results in
errors, you can undo the changes. To prevent loss of data, note that all
changes implemented subsequent to the last archived status will be undone.
When you make changes to your project on the screen, save them and save them back to
the Engineering System.
Note
Additional information
You can find further information on data synchronization with the Runtime system in the
SIMATIC RF-MANAGER Configuration and Operating Manual
.
Using the sample project
4.3 Using the project
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 27
Alarms
The "Alarms" button takes you to a screen that shows all the alarm events that have
occurred.
The button "Reset alarm buffer" is used to erase all the alarms from the memory.
Alarm window
The following is displayed in the alarm window:
● Critical RFID alarms
● System alarms that notify the operator about the operating states of the runtime system
The alarm window cannot be selected via a button, but appears automatically in the current
screen at each new alarm event and is also automatically closed again. In contrast to the
alarm screen, the alarm window only displays the currently active alarms.
Using the sample project
4.4 Connecting the project to the enterprise system
SIMATIC RF-MANAGER 2008
28 Getting Started, 06/2010, A5E01070047-03
The following alarms are supported:
● RFID alarms
RFID alarms provide information about the operating states of the reader and the plant,
and are activated by the reader. Apart from the predefined RFID alarms, it is also
possible to configure additional RFID alarms.
Important RFID alarms must be acknowledged using a button in the alarm window. The
alarm window is then automatically hidden.
● System alarms
System alarms are predefined to indicate certain system statuses of the runtime system.
These are activated by the Runtime system.
System alarms do not need to be acknowledged. After the alarm appears, the alarm
window is automatically hidden according to the time set.
The buttons have the following functions:
button Function
Acknowledgement of alarms
Note
Additional information
You can find further information on the structure of the alarm system in the
SIMATIC RF-
MANAGER Configuration and Operating Manual
.
4.4 Connecting the project to the enterprise system
The RF-MANAGER is supplied with a demo application which you can use to test the
connection between the enterprise system and the sample project. The ALE+Client Demo is
an individual application can be be started via "SIMATIC > RF-
MANAGER 2008 Runtime > ALE+Client Demo".
Using the sample project
4.4 Connecting the project to the enterprise system
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 29
Working with the demo application
1. The project is already running, so start the ALE+ client via the start menu "SIMATIC >
RF-MANAGER 2008 Runtime > ALE+Client Demo".
2. Select the current project under "Configuration > Import" in the ALE+ client. The name
corresponds to the current project name with the ending "xml.deployed". If necessary,
switch to the project directory beforehand.
After opening, the components used in the project are displayed.
3. Now select the menu item "ALE Commands > Subscribe" on the left-hand side. On the
right-hand side, select the "Default ALE connection" as the ALE connection and click the
green start button alongside the selection field for the ECSpec.
The ALE+ client is now logged on to the RF-MANAGER runtime system and receives a
report containing the relevant information for every newly detected tag. Several new
entries within an interval of 2 seconds are combined in a report.
Using the sample project
4.5 Connecting the project to the ALE interface
SIMATIC RF-MANAGER 2008
30 Getting Started, 06/2010, A5E01070047-03
4. In the table, you can open the individual nodes and navigate to the separate tag
information. Using the buttons below the table, you can switch between the read reports.
You will find further information regarding operator input in the documentation for the
ALE+ client on the CD "SIMATIC RF-MANAGER 2008" under the path:
"SIMATIC > RF-MANAGER 2008 Runtime > ALE+Client Demo\ ALE+ Function
Manual.pdf".
5. Click the "X" button under the green start button to log off the ALE+ client from the RF-
MANAGER runtime system. Then you can close the ALE+ client.
Every time the runtime system is restarted, the ALE+ client must be logged on to RF-
MANAGER runtime by pressing the green start button.
4.5 Connecting the project to the ALE interface
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.
Using the sample project
4.5 Connecting the project to the ALE interface
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 31
Figure 4-1 ALEDataBridgeClient
The ALEDataBridgeClient is already fully installed following installation of the RF-MANAGER
Service Pack, 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.
Using the sample project
4.5 Connecting the project to the ALE interface
SIMATIC RF-MANAGER 2008
32 Getting Started, 06/2010, A5E01070047-03
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 33
Project representation in the RF-MANAGER 5
The following will familiarize you with the program interface of the Engineering System (ES)
and the representation of the example project in the ES. The individual function blocks of the
project are outlined and their mutual dependencies are presented. In addition, the
fundamentals of configuring the most important screens are explained.
5.1 Programming interface of the engineering system
You can access all the functions provided by the RF-MANAGER Engineering System by
means of its menus and toolbars. When the mouse pointer is moved over an element, a
tooltip appears.
Project representation in the RF-MANAGER
5.1 Programming interface of the engineering system
SIMATIC RF-MANAGER 2008
34 Getting Started, 06/2010, A5E01070047-03
Elements of the program interface
The RF-MANAGER Engineering System comprises the following elements:
Elements of the RF-MANAGER Engineering System
1 Menus and toolbars The menus and toolbars provide access to all functions you need to configure your runtime
system. When the corresponding editor is activated, menu commands and toolbars specific
to that editor appear. When the mouse pointer is moved over a command, the
corresponding ToolTip appears.
2 Project view All component parts and editors available in a project appear in a tree structure in the
Project View. Folders are provided as sub-elements of each editor in which you can save
objects in a structured way. With some editors, especially with the editor RFID Device, you
have direct access to the configured objects. In the project window you have access to the
device settings of the runtime system and the language settings.
3 Workplace Project objects are edited in the workplace. All RF-MANAGER elements are arranged on
the borders of the workplace. With the exception of the workplace, you can organize,
configure and, for example, move or hide any of the elements to suit your individual
requirements.
4 Toolbox The Toolbox contains a selection of objects that you can add to your screens, e. g. image
objects or operator control elements.
5 Properties dialog box The property dialog box is used to edit object properties, e. g. the color of screen objects.
The properties dialog box is only available in specific editors.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 35
Elements of the RF-MANAGER Engineering System
6 Output view The output window displays system alarms generated, for example, in a project test run.
7 Object view The "Objects View" shows all elements of the area selected from the "Project View".
Note
With the exception of the workplace, you can show or hide all windows in the "View" menu.
5.2 RFID function blocks
The individual RFID function blocks of the sample project are outlined below and their mutual
dependencies are presented.
This includes:
● RFID device
● Workplaces
● RFID data link
● ALE connections
5.2.1 RFID device
The RFID device is a function block in RF-MANAGER and represents a reader. There are
three RFID devices in the sample project.
● Reader "Reader_Labeling" (labeling):
This reader reads and writes tag IDs.
● Reader "Reader_Sorting" (sorting):
This reader reads tag IDs. The read results of the reader influence the setting of the
separating filter.
● Reader "Reader_Gates" (outgoing goods):
This reader reads tag IDs and thus monitors both outgoing goods gates.
The configuring of the RFID devices can be traced using the editor "RFID Devices > (reader
name)" in the properties dialog box.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
36 Getting Started, 06/2010, A5E01070047-03
The following components are active in the relevant RFID device:
Antennas
The antennas read the data of the tags that are applied to the goods and pallets and transfer
the data to the corresponding data source. The readers "Reader_Labeling" and
"Reader_Sorting" use two antennas. The reader "Reader_Gates" uses all four antennas.
The configuring of the antennas can be traced using the editor "RFID Devices > (reader
name) > Antennas" in the properties dialog box.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 37
Data source
Data sources are the basic components for reading RFID data. They enclose the antennas
assigned to them and forward the data received via the antennas to the downstream function
units.
In general, one RFID device can contain several data sources. Different data sources can be
defined so that mutually independent tasks can be performed with one reader (see online
help
Understanding and optimizing the acquisition of tags
, chapter
Multiple data sources
).
The readers "Reader_Labeling" and "Reader_Sorting" each comprise one data source with
two assigned antennas. Two data sources are created in the reader "Reader_Gates" - one
for each outgoing goods gate with two assigned antennas in each case.
The configuring of the data sources can be traced using the editor "RFID Devices > (reader
name) > Sources" in the properties dialog box; and the connection of data source and
assigned antennas can be traced under "RFID Devices > (reader name) > Sources >
General".
One data source contains the following blocks:
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
38 Getting Started, 06/2010, A5E01070047-03
● Read trigger
Read triggers are activation mechanisms. They cause the data source to read the data
from the tags that are located in the antenna fields.
For the readers "Reader_Labeling" and "Reader_Sorting", the triggers for the data
sources are set to the edge of the I/O signal.. When the light barrier is interrupted, the
input Inport00 of the reader is set which triggers a read.
For the reader "Reader_Gates", the trigger for the automatic gate is also set to the edge
of the I/O signal. The trigger for the manual gate is set to the application request because
triggering is performed by the system function "ActivateTrigger".
The configuring of the read trigger can be traced using the editor "RFID Devices > (reader
name) > Trigger" in the properties dialog box. Triggers are assigned to data sources
under "RFID Devices > (reader name) > Sources > Properties > Triggers".
● Tag selector
Tag selectors are mechanisms used to route data on and to filter data. They determine
which tag data areas should be read or routed on. They also define which tags should be
supplied or filtered out on the basis of the contents of these data areas. In general, a tag
selector orientates itself according to the tag ID or the freely parameterizable user data of
the tag.
Note
No tag selector created in the sample project
To keep the sample project as simple as possible, no tag selector has been created.
● Smoothing
Smoothing is a technique that is used to optimize the read quality. The RF-MANAGER
marks the read event with a status description for the tag (e.g.: detected by the antennas
for the first time, detected with certainty, lost) and adds these states to the read results.
Time intervals are defined using this technique - for example, how long a tag detected for
the first time has to be "seen" for it to be regarded as reliably detected. This allows tags to
be excluded that have been unintentionally detected briefly in the boundary areas of the
reader.
The configuring of the smoothing can be traced using the editor "RFID Devices > (reader
name) > Sources > Properties > Smoothing" in the properties dialog box.
Notification channel
One or more data sources are assigned to one notification channel as data suppliers. In this
scenario, three notification channels are used, one per reader. The notification channels
route on the data from their data source.
The configuring of the notification channels can be traced using the editor "RFID Devices >
(reader name) > Notification channels" in the properties dialog box.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 39
One notification channel contains the following blocks:
● Notification channel trigger
Notification channel triggers are activation mechanisms. They cause the notification
channel to transfer the data from the data source assigned to it. In this project,
continuous triggers are configured for all readers which ensure the continuous transfer of
data.
The configuring of the notification channel triggers can be traced using the editor "RFID
Devices > (reader name) > Triggers" in the properties dialog box; and the connection of
notification channels and assigned triggers can be traced under "RFID Devices > (reader
name) > Notification channels > Properties > Triggers".
● Data selector
Data selectors are mechanisms that process tag information and filter it. In this scenario,
for example, filtering can be performed using filtering criteria that are defined in the data
sources: Information is only transferred from tags that are in the reliably detected state. It
can be assumed that these have been detected without errors.
In general, the data selectors can supply additional information (reader fields). This
includes, for example, the time of the read.
The configuring of the data selectors can be traced using the editor "Selectors > Data
selectors" in the properties dialog box.
5.2.2 Workplaces
Workplaces are function blocks in the RF-MANAGER and are used to abstract the hardware.
For this purpose, the relevant data sources and notification channels are grouped into
workplaces. In practice, workplaces are combinations of readers.
There are two workplaces in this example:
● One workplace refers to the reader "Reader_Labeling". This means that: This workplace
stands for the labeling of tag IDs.
● The other workplace refers to the readers "Reader_Sorting" and "Reader_Gates". This
means that: This workplace stands for sorting the goods and monitoring of the two
outgoing goods gates.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
40 Getting Started, 06/2010, A5E01070047-03
Is several readers are used per plant area, you can simplify the configuration by assigning
several readers to one work area. Instead of selecting many readers in one RFID view, it is
sufficient to select the encompassing workplace and you will obtain the data for all the
associated readers.
Note
Additional synchronous data sources for Workplace_Labeling
Additional synchronous data sources are configured for Workplace_Labeling, because it is
only possible to write via workplaces and the data sources that they contain.
The configuring of the workplaces can be traced using the editor of the same name in the
properties dialog box.
5.2.3 RFID data link
An RFID data link is used to supply read RFID data in variables.
In the runtime system, the RFID data link registers with the workplaces, readers or data
sources specified on configuring and receives the RFID data read there from this point
onwards.
Project representation in the RF-MANAGER
5.2 RFID function blocks
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 41
The read RFID data is supplied in variables. This ensures that the data can be reliably
evaluated in a PLC or with VB scripting in RF-MANAGER. The PLC can then trigger
appropriate actions, for example, in production in accordance with the evaluation results.
Through the use of variables, the data can be displayed in output fields in parallel.
● In the labeling scenario, the RFID data link "RFID_Data_link_Labeling" supplies the read
tag ID in the form of a variable. The tag ID is supplied in raw hexadecimal format without
a prefix. Only reliably detected tag IDs are required, so the event filter is set to observed.
Coordination is not necessary in this scenario, because only one tag is in the field at a
given time.
● In the sorting scenario, the RFID data link "RFID_Data_link_Sorting" supplies the read tag
data and additional data, such as the acquisition time, to the PLC in the form of variables.
The separating filters can be set for the conveyor belts via the PLC. The tag ID is
supplied in tag format without a prefix. Only reliably detected tag IDs are required, so the
event filter is set to observed. Coordination using an acknowledgement variable is
appropriate in this scenario to ensure that the separating filter has been set.
● In the outbound logistics scenario, the RFID data link "RFID_Data_link_Gates" supplies
the read tag IDs in the form of a variable. A script is used to check whether the tag data
satisfies the previously specified requirements. The tag ID is supplied in raw hexadecimal
format without a prefix. Only reliably detected tag IDs are required, so the event filter is
set to observed. Coordination using an acknowledgement variable is appropriate in this
scenario to ensure that all the read tag IDs are processed and checked in sequence.
Data from more than one tag is usually read in one read procedure, so data is buffered in the
RFID data link. The data is called in turn via a coordination mechanism, so it can be reliably
evaluated. For further details on using the RFID data link, and especially on the coordination
possibilities, please refer to the online help (Information System) for RF-MANAGER ES.
The configuring of the RFID data link can be traced using the editor of the same name in the
properties dialog box.
5.2.4 ALE connections
The data of the workplaces can be requested in the form of reports by the enterprise system
over the ALE interface (Application Level Events). When data are provided over the ALE
interface, it is generally the case that ALE clients only have a logical view of the workplaces,
precise knowledge of the hardware of the RFID system is no longer necessary.
Note
No user-defined ALE connection was created in the sample project
To keep the sample project as simple as possible, no user-defined ALE connection has been
created. A "Default ALE connection" is, however, always created automatically so that
reports can be accessed.
The data of a workplace can be requested in the form of reports by the enterprise system
over the ALE interface (Application Level Events). The is performed using the following read
procedure:
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
42 Getting Started, 06/2010, A5E01070047-03
● Asynchronous read procedure
An asynchronous read procedure is when an ALE client of the enterprise system logs
onto the report of the ALE interface and receives the data automatically. This continues
until the client logs off again.
● Synchronous read procedure
A synchronous read procedure is when an ALE client of the enterprise system logs onto
the report of the ALE interface and receives the required data automatically.
The data of an ALE report, however, are dependent on the activity of the following blocks:
● ALE selector
ALE selectors are filter mechanisms that further reduce the accumulated data in
accordance with the configuration settings. ALE selectors can only filter out EPC tags - to
perform, for example, filtering according to article classes.
Filtering of the freely parameterizable user data is not possible with ALE selectors - this
must be performed via the data source or the notification channel.
● ALE groups
ALE groups determine how the data records that have passed through the filter should be
grouped for the report to the ALE client. The data records can be grouped according to
serial numbers, for example.
Note
No ALE selector or no ALE group was created in the sample project
To keep the sample project as simple as possible, no ALE selector and no ALE group were
created.
5.3 Screens
Screens are used to control RFID systems and their components. When you create your
screens, the predefined objects support you in simulating your plant, displaying plant
processes and defining plant values. You will find information in this chapter on the structure
and component parts of the screens.
5.3.1 Scenario screens
Below is an explanation of the screens that represent RFID functionalities in the sample
project.
This includes:
● Labeling
● Sorting
● Gates (outgoing goods)
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 43
5.3.1.1 Basic settings and procedures
When you view the scenario screens in the project tree in the "Screens" editor, you can trace
the basic settings and procedures of the scenarios.
In this chapter, the basic mechanisms are described first that are used in all scenario
screens and which are therefore not described again later.
Motion sequences
In all scenario screens, the crates or pallets are moved with the help of a cyclically triggered
script. You will find the scripts in the project tree in the "Scripts" editor. Scripts that are
responsible for the movements have a name that starts with the name of the scenario and
contains the component "Move" (e.g. Labelling_Move_...).
The motion scripts are triggered by the variable "(scenario)_Cycle_100ms" that is
incremented at intervals of 100 ms. This is performed by the system function
"SimulateVariable".
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
44 Getting Started, 06/2010, A5E01070047-03
1. Click on the gray background in the respective scenario screen.
In the properties window under "Events > Loaded", you will see the system function
"SimulateVariable".
The effect of this configuration at runtime is that the function is started after the screen
has loaded and executes until the screen is exited.
Note
System function "SimulateVariable" can only be used to a limited extent
The system function "SimulateVariable" can not be used with any type of trigger, because
short update times and frequent use can cause excessive loading on the system. It
should also only be used for simulation applications such as those described here. For
cyclic triggering, a PLC variable is usually more suitable.
As long as the function executes, the variable "(scenario)_Cycle_100ms" is incremented
and triggers on every change of the event trigger "Change value" on the variable.
2. Open the "Variables" editor in the project window and select the variable
"Labeling_Cycle_100ms".
In the properties dialog box under "Events > Change value", you can see that the script
"Labeling_Move_Conveyor" was configured on this trigger.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 45
The result of this is that on every change in value of the variable "Labeling_Cycle_100ms"
the system function "SimulateVariable" will call the script "Labeling_Move_Conveyor". In
the script, depending on the position of the conveyor, different actions are performed that
will be described in detail below.
The basic principle of the motion sequences described applies to all scenario screens.
Only the name part of the components for the scenario differs.
Use of tags
In the sample project, many different variables are used. An overview of the variables can be
obtained by opening the "Variables" editor in the project view.
To enable a variable to be quickly associated with the scenario, the name of the scenario
precedes the variable name. All variables of the "Labeling" scenario are therefore called
"Labeling_……".
Most of the variables are internal variables, because the sample project executes without
hardware. By using a simulator, it is, however, possible to use variables whose addresses
are in the reader (e.g. inputs/outputs). One example is the "Labeling_Light_barrier" variable
that starts the reading procedure when an input changes.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
46 Getting Started, 06/2010, A5E01070047-03
In the "Sorting" scenario, variables are used whose addresses are located in the PLC
"PLC_Sorting". One example is the variable "Sorting_ID" which provides the read tag ID for
evaluation in the PLC. Online mode is deactivated for the PLC to enable the sample project
to execute without a PLC. As a result, the PLC variables behave as internal variables to the
runtime system.
Variables are the most important components of the runtime system. They serve on the one
hand to represent values from hardware modules, such as readers or PLCs, as well as to
display and input values from the user. On the other hand, they also serve as triggers for
actions within the runtime system. On a change in value or limit violation, system functions or
scripts can be triggered to control and monitor a plant.
You will find events and their actions in the properties dialog box under "Events".
In the case described above, on a value change in the variable "Labeling_Serial_number",
the script "Labeling_Modify_ID" is executed.
The basic principle of triggering system functions or scripts on a change in value is used in
many places in the sample project.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 47
Use of screen objects
As already described under the use of variables, actions in the form of system functions or
scripts can also be triggered by screen objects.
1. Click a button in the screen, e.g. the button "Start conveyor" in the "Labeling" screen.
In the properties window under "Events > Click", you can see that on clicking the button,
the script "Labeling_Reset" is executed and the value of the variable
"LabelingConveyorStatus" is set to 1.
In this sample project, screen objects are frequently dynamized. Depending on the value
of the variable, colors, operability, motion and visibility can be controlled. These
mechanisms are used, for example, to lock buttons.
2. Click a button in the screen, e.g. the button "Start conveyor" in the "Labeling" screen.
In the properties dialog box under "Animations > Enable object", you can see that the
button will only be active when the variable "Labeling_Conveyor_Status" is set to 0. This
means that when the scenario is started, the button is disabled.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
48 Getting Started, 06/2010, A5E01070047-03
For further details on using animations, please refer to the online help (Information System)
for RF-MANAGER ES.
5.3.1.2 Labeling
The "Labeling" screen represents the functionality of the reader "Reader_Labeling" in the
sample project. The central element here is the writing of tag IDs. This happens when the
conveyor belt is automatically stopped - after the goods fitted with tags break the light
barrier.
The configuring of the "Labeling" screen can be traced using the editor "Screens / Labeling"
in the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 49
Central sequence control is performed by the script "Labeling_Move_Conveyor", which is
triggered cyclically as already explained by a change in the variable
"Labeling_Cycle_100ms".
Script Labeling_Move_Conveyor
The script is used to control the movement sequences of the conveyor belt that can be
influenced using the function keys "Start conveyor" and "Stop conveyor".
The script is also responsible for stopping the conveyor belt automatically as soon as the
goods fitted with a tag breaks the light barrier.
Creation of the script can be traced using the editor "Scripts > Labeling_Move_Conveyor" in
the properties dialog box. The script is structured as follows:
Request: IF loop Description
Labeling_Conveyor_Status = 1 You activate the scenario via the "Start conveyor" button.
Labeling_Move_Status = 1 The conveyor will transport the crate 10 steps forwards until you stop the
conveyor manually by resetting the variable "Labeling_Move_Status". The
variable "Labeling_Move_Conveyor" determines the position on the conveyor.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
50 Getting Started, 06/2010, A5E01070047-03
Request: IF loop Description
Labeling_Move_Conveyor = 240 When the barrier is reached, the conveyor is stopped, because the variable
"Labeling_Move_Status" is reset.
At the same time the barrier is activated, due to the variable
"Labeling_Light_barrier" being set that points to the input Inport00 in the
reader "Reader_Labeling".
The change to the input trips the edge-triggered read trigger of the reader
"Reader_Labeling" that causes the data source to read out the tag ID.
The "Write tag ID" button is switched to active.
For the subsequent procedure, see "Workplace_Labeling"
Labeling_Move_Conveyor = 300 When the crate leaves the light barrier again, the light barrier is switched
inactive due to the variable "Labeling_Light_barrier" being reset.
Labeling_Move_Conveyor = 500 As soon as the crate has reached the end of the conveyor, the scenario is
started again.
Workplace_Labeling
The tag data that was read by the reader "Reader_Labeling" is supplied to the workplace
"Workplace_Labeling" over the notification channel. This supplies the data to the enterprise
system and also supplies it to "RFID_Data_link_Labeling".
The configuring can be traced using the editor "Workplaces" in the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 51
The data source for synchronous data access must also be connected so that tag IDs can
also be written by the reader "Reader_Labeling". This is performed in the properties dialog
box under "Properties > Synchronous data access".
RFID_Data_link_Labeling
The RFID data link "RFID_Data_link_Labeling" was configured such that all the data of the
workplace "Workplace_Labeling" and therefore of the reader "Reader_Labeling" is supplied
in the variables "Labeling_Current_ID_Hex_Format".
The configuring can be traced using the editor "RFID data link" in the properties dialog box.
As only one tag ID can be in the field in this scenario, no coordination is necessary.
You can see from the further properties which events and in which format the tag IDs are
provided as a string.
Labeling_Current_ID_Hex_Format
This variable is linked to the script "Labeling_Modify_ID" which is called on a value change in
"Split" mode.
Script Labeling_Modify_ID
At the beginning of the script, the read tag ID is converted from raw hex format to tag format
using the system function "TranslateEpc".
The subsequent procedure is in accordance with the mode on calling the script:
● With Split:
The tag format is broken up into its components separated by dots. For SGTIN tag
format, the serial number is in the final block. The serial number is assigned to the
variable "Labeling_Serial_number". This variable is displayed in the screen as an input
field and can be changed. If the value is changed by the user, this script is then called in
the mode "Join".
● With Join:
The components of the tag format are combined with a different serial number, if
applicable, to form the new tag ID and the tag format is then translated back to the
original hexadecimal format. This is necessary because the writing of tag IDs is only
possible in hexadecimal format.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
52 Getting Started, 06/2010, A5E01070047-03
Button for writing tag IDs
This button is used to write the new tag ID. This is performed by the script "Labeling_Write"".
The variable "Labeling_Move_Status" is then set so that the conveyor will start again.
Script Labeling_Write
The script "Labeling_Write" checks whether the ending of the tag ID is even or odd. For an
odd serial number, "Labeling_Product_Type" is set to 1 which results in a red crate. For an
even serial number, "Labeling_Product_Type" is set to 2 which results in a green crate. The
tag ID is then written with the system function "WriteTagId". Writing can only be performed
via a workplace for which a data source has been configured for the synchronous exchange
of data.
5.3.1.3 Sorting
The "Sorting" screen represents the functionality of the reader "Reader_Sorting" in the
sample project. The core element here is the evaluation of tag read results in cooperation
with an S7 PLC. The results are generated after the goods fitted with tags have broken the
light barrier. The separating filter downstream of the conveyor belt is set according to the tag
read results.
The configuring of the "Sorting" screen can be traced using the editor "Screens > Sorting" in
the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 53
Central sequence control is performed by the script "Sorting_Move_Conveyor", which is
triggered cyclically as already explained by a change in the variable "Sorting_Cycle_100ms".
Script Sorting_Move_Conveyor
The script is used to control the movement sequences of the conveyor belt that can be
influenced using the function keys "Start conveyor" and "Stop conveyor".
The script is also responsible for an automatic read as soon as the goods fitted with a tag
breaks the light barrier.
Creation of the script can be traced using the editor "Scripts > Sorting_Move_Conveyor" in
the properties dialog box. The script is structured as follows:
Request: IF loop Description
Sorting_Conveyor_Status = 1 You activate the scenario via the "Start conveyor" button.
Sorting_Move_Status = 1 The conveyor will transport the crate 10 steps forwards until you stop the
conveyor manually by resetting the variable "Sorting_Move_Status". The
variable "Sorting_Move_Conveyor" determines the position on the conveyor.
Sorting_Move_Conveyor = 100 When the barrier is reached, the light barrier is activated due to the variable
"Sorting_Light_barrier" being set that points to the input Inport00 in the reader
"Reader_Sorting".
The change to the input trips the edge-triggered read trigger of the reader
"Reader_Sorting" that causes the data source to read out the tag ID.
For the subsequent procedure, see "RFID_Data_link_Sorting"
Sorting_Move_Conveyor = 130 When the crate leaves the light barrier again, the light barrier is switched
inactive due to the variable "Sorting_Light_barrier" being reset.
Sorting_Move_Conveyor = 300 When the crate has reached the end of the fixed conveyor, depending on the
product type "Sorting _Product_Type" recognized, a different movement path
"Sorting_Direction" is activated.
Red crates must move upwards to the red pallet.
Green crates must move downwards to the green pallet.
Sorting_Move_Conveyor = 600 As soon as the crate has reached the end of the conveyor, the scenario is
started again.
RFID_Data_link_Sorting
The RFID data link "RFID_Data_link_Sorting" was configured such that all the data of the
reader "Reader_Sorting" is supplied in several "Sorting_..." variables. The variables have
addresses located in the PLC "PLC_Sorting" because in actual use, the data should be
evaluated in the PLC. The values are also displayed in the top right-hand screen area in the
form of output fields.
The configuring can be traced using the editor "RFID data link" in the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
54 Getting Started, 06/2010, A5E01070047-03
In this scenario, several variables from one read procedure are supplied, so coordination is
necessary. This is performed using the acknowledgement variable "Sorting_Quit_PLC".
You can see from the further properties which events and in which format the tag IDs are
provided as a string.
For further details on using the RFID data link, and especially on the coordination
possibilities, please refer to the online help (Information System) for RF-MANAGER ES.
Sorting_Quit_PLC
This variable is linked using the script "Sorting_PLC_Program" which is called every time that
new data is signaled through the RFID data link "RFID_Data_link_Sorting".
Script Sorting_PLC_Program
The script "Sorting_PLC_Program" checks whether the ending of the currently supplied tag
ID is even or odd.
● For an odd serial number, "Sorting_Product_Type" is set to 1 which results in a red crate.
● For an even serial number, "Sorting_Product_Type" is set to 2 which results in a green
crate.
The variable "Sorting_Product_Type" is used to determine the position of the separating filter
which is implemented in the form of a graphical display.
Finally, the acknowledgement variable "Sorting_Quit_PLC" is reset. When the
acknowledgement variable is not reset, no new tags will be provided by the RFID data link.
RFID view
The tags present in the field are also displayed below the conveyor.
The settings can be traced in the properties dialog box after the RFID display has been
selected.
To ensure that only the tags from the reader "Reader_Sorting" are displayed, an appropriate
display selector "Display_selector_Sorting" has been configured.
The configuring can be traced using the editor "Selectors" in the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 55
5.3.1.4 Gates (outgoing goods)
The "Gates" screen represents the functionality of the reader "Reader_Gates" in the sample
project. The core element here is checking the pallets at the outgoing goods gate. To ensure
that the right goods are delivered to the right customers, only red pallets are permitted to
pass through the red outgoing gate and green pallets through the green outgoing gate.
Incorrect pallets must be stopped.
The configuring of the "Gates" screen can be traced using the editor "Screens > Gates" in
the properties dialog box.
Central sequence control is performed by the script "Gates_Move_Pallet", which is triggered
cyclically as already explained by a change in the variable "Gates_Cycle_100ms".
Symbolic I/O field for product selection
In the left-hand area of the screen it is possible to select the products, and therefore the
color of the pallets that will be moved through the respective gate, via two symbolic I/O fields
(combination boxes). Using the text list "Product_Type_List", the value 1 (odd) is set for red
crates and the value 2 (even) is set for green crates. The values of the variables
"Gates_Product_Type_Red_Pallet" or "Gates_Product_Type_Green_Pallet" are then
evaluated in the script "Gates_Move_Pallet".
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
56 Getting Started, 06/2010, A5E01070047-03
Script Gates_Move_Pallet
The script is used to control the movement sequences of the pallets that can be started
using the "Move pallet" buttons.
The script is also responsible for an automatic read as soon as the goods fitted with a tag
breaks the light barrier on the red outgoing gate.
Creation of the script can be traced using the editor "Scripts > Gates_Move_Pallet" in the
properties dialog box.
The script is structured as follows:
● For the red outgoing gate ("Gates_Gate_Type"=1) in automatic mode with the light
barrier:
Request: IF loop Description
Gates_Conveyor_Status = 1 You activate the scenario via the appropriate "Move pallet" button.
Gates_Move_Status = 1 The pallet will move 10 steps forwards until you stop the motion manually by
resetting the variable "Gates_Move_Status". The variable
"Gates_Move_Red_Pallet" determines the position in the path.
Gates_Move_Red_Pallet = 20 The color set for the pallet above is evaluated. Depending on the value of the
variable "Gates_Product_Type_Red_Pallet", a temporary variable
"Gates_Product_Type_Simulation" is set, that will set the input Inport01 on the
reader "Reader_Gates" for simulation of the tag IDs to LOW (odd tag IDs) or
HIGH (even tag IDs).
Please refer to the description in the section "Using the project > Outbound
logistics screen > Settings in the simulator".
Gates_Move_Red_Pallet = 120 When the barrier is reached, the light barrier is activated due to the variable
"Gates_Light_barrier_Red_Gate" being set that points to the input Inport00 in
the reader "Reader_Gates".
The change to the input trips the edge-triggered read trigger of the reader
"Reader_Gates" that causes the data source to read out the tag ID.
For the subsequent procedure and checking the read tag IDs, see
"RFID_Data_link_Gates"
Gates_Move_Red_Pallet = 200 When the pallet leaves the light barrier again, the light barrier is switched
inactive due to the variable "Gates_Light_barrier_Red_Gate" being reset. The
check for detection of invalid tag IDs ("Gates_Wrong_Red_Tags" > 0) is
performed simultaneously. If the wrong tag IDs were detected, movement of
the pallets will be stopped. In this case, an acknowledgement is required via
the relevant "Reset pallet" button.
Gates_Move_Red_Pallet = 450 If the pallet was not stopped, at the end of the motion path, the scenario is
started again.
● For the green outgoing gate ("Gates_Gate_Type"=2) in manual read mode:
Request: IF loop Description
Gates_Conveyor_Status = 1 You activate the scenario via the appropriate "Move pallet" button.
Gates_Move_Status = 1 The pallet will move 10 steps forwards until you stop the motion manually by
resetting the variable "Gates_Move_Status". The variable
"Gates_Move_Green_Pallet" determines the position in the path.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 57
Request: IF loop Description
Gates_Move_Green_Pallet = 20 The color set for the pallet above is evaluated. Depending on the value of the
variable "Gates_Product_Type_Green_Pallet", a temporary variable
"Gates_Product_Type_Simulation" is set, that will set the input Inport01 on the
reader "Reader_Gates" for simulation of the tag IDs to LOW (odd tag IDs) or
HIGH (even tag IDs).
Please refer to the description in the section "Using the project > Outbound
logistics screen > Settings in the simulator".
Gates_Move_Green_Pallet = 150 When the position is reached, the movement is stopped by resetting the
variable "Gates_Move_Status" and the "Read pallet" button is activated for
manual reading.
The system function "ActivateTrigger" and setting of the variable
"Gates_Move_Status" is configured at the "Read pallet" button for the purpose
of resuming the movement.
The system function call "ActivateTrigger" with reference to the trigger
"SourceTrigger_AppRequest" trips the read trigger of the reader
"Reader_Gates" set to the application request, which in turn causes the data
source to read out the tag IDs.
For the subsequent procedure and checking the read tag IDs, see
"RFID_Data_link_Gates"
Gates_Move_Green_Pallet = 200 The check for detection of invalid tag IDs ("Gates_Wrong_Green_Tags" > 0) is
performed when the pallet leaves the outgoing gate following the manual read.
If the wrong tag IDs were detected, movement of the pallets will be stopped. In
this case, an acknowledgement is required via the relevant "Reset pallet"
button.
Gates_Move_Green_Pallet = 450 If the pallet was not stopped, at the end of the motion path, the scenario is
started again.
RFID-Data_link_Gates
The RFID data link "RFID_Data_link_Gates" was configured such that the read tag IDs of the
reader "Reader_Gates" is supplied in the variable "Gates_ID". More than one tag ID is
detected during the read procedure, so the tag IDs are supplied in sequence for evaluation.
They are supplied in sequence by means of coordination using the acknowledgement
variable "Gates_Quit_Script". Evaluation with a subsequent acknowledgement is performed
in the script "Gates_Script_Program".
The configuring can be traced using the editor "RFID data link" in the properties dialog box.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
58 Getting Started, 06/2010, A5E01070047-03
You can see from the further properties which events and in which format the tag IDs are
provided as a string.
For further details on using the RFID data link, and especially on the coordination
possibilities, please refer to the online help (Information System) for RF-MANAGER ES.
The read tag events are also displayed in the top section of the screen in the form of an
RFID view.
Gates_Quit_Script
This variable is linked using the script "Gates_PLC_Program" which is called every time that
new data is signaled through the RFID data link "RFID_Data_link_Gates".
Script Gates_Script_Program
The script "Gates_Script_Program" is executed when the RFID data link signaled through the
variable "Gates_Quit_Script" that a valid value was written to the variable "Gates_ID".
Depending on the outgoing gate at which the check was made,
● At the red gate ("Gates_Gate_Type"=1) for an even serial number (green tag IDs) the
variable "Gates_Wrong_Red_Tags" will be increased by 1.
● At the green gate ("Gates_Gate_Type"=2) for an odd serial number (red tag IDs) the
variable "Gates_Wrong_Green_Tags" will be increased by 1.
Several tag IDs were acquired during one read procedure and the values in the RFID data
link were buffered, so the acknowledgement variable "Gates_Quit_Script" is reset following
evaluation of the first tag ID. This ensures that the RFID data link supplies the next tag ID
and all read tag IDs are read in the manner described above.
The movement in the script "Gates_Move_Pallet" continues during the check, so the results
are evaluated and subsequent actions are activated as described above in the script from
position 200.
RFID view
The read tag events are also displayed above the outgoing gates.
The settings can be traced in the properties dialog box after the RFID display has been
selected.
To ensure that only the tag events from the reader "Reader_Gates" are displayed, an
appropriate display selector "Display_selector_Gates" has been configured.
The configuring can be traced using the editor "Selectors" in the properties dialog box.
5.3.2 System screens
Below is an explanation of the screens that present system information in the sample project.
This includes:
● Configuration
● Alarms
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 59
5.3.2.1 Configuration
The "Configuration" screen visualizes the configuration of the sample project. Configuration
changes can be made via this screen in Runtime. The screen is thus used for starting up and
optimizing the RFID system. Individual components can be reparameterized here. Individual
parameters can also be deleted.
The configuring of the "Configuration" screen can be traced using the editor "Screens >
Configuration" in the properties dialog box.
The screen mainly comprises the screen element "Configuration" in the "Standard" view (RF-
MANAGER ES). The poll cycle can be parameterized to specify an update interval for the
view.
5.3.2.2 Alarms
Below is an explanation of the functions that are used for further diagnostics in the sample
project.
This includes:
● The "Alarms" screen
● Alarm window
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
60 Getting Started, 06/2010, A5E01070047-03
Alarms screen
The "Alarms" screen is used to display the alarm events that have been triggered.
The configuring of the "Alarms" screen can be traced using the editor "Screens > Alarms" in
the properties dialog box.
The screen mainly comprises the screen element "Alarm view".
It is specified in the properties dialog box under "General" that alarm events and all alarm
classes (except for RFID_Debug) should be displayed.
The parameters visualized in the alarm view are specified in the properties dialog box under
"Properties > Columns". The following parameters are available:
Parameters Description
Alarm number The alarm number is used to reference an alarm.
Time The time-of-day of receipt of the alarm
Status Status description of the alarm: "Activated", "Acknowledged" or
"Deactivated"
Alarm text The alarm text contains a description of the alarm.
Alarm class The alarm classes mainly determine how alarms will appear when they are
displayed on the Runtime system. Alarm classes are also used to group
alarms for various means of display. RF-MANAGER has both predefined
alarm classes and the option to configure user-defined alarm classes.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
Getting Started, 06/2010, A5E01070047-03 61
Parameters Description
Date The date of receipt of the alarm
Device (fault location) Alarm trigger
A button is also configured with the system function "ClearAlarmBuffer". To trace the
settings, click the button and navigate through the properties dialog. You will find the system
function under "Events > Click".
Alarm window
During operation of the sample project, the "alarm window" visualizes incoming alarms and
the associated additional information. The alarm window cannot be selected via a button, but
appears automatically at each alarm event regardless of the screen. The layout and
operation of the alarm window correspond to that of the alarm view.
The configuring of the alarm window can be traced using the editor "Screens > Template" in
the properties dialog box.
It is specified in the properties dialog box under "General" that active alarms should be
displayed. Only the critical alarm classes and system alarms are displayed.
Project representation in the RF-MANAGER
5.3 Screens
SIMATIC RF-MANAGER 2008
62 Getting Started, 06/2010, A5E01070047-03
