Filtering Out Transponders Detected Due To Overshoot - Siemens SIMATIC RF600 Series Configuration Manual

Example A - further procedure
Follow the steps below to take inventories for 10 seconds if the light barrier is interrupted.
1. Create an If condition that then always triggers the command "getObservedTagIDs" when
the light barrier (input 1) is interrupted.
2. Specify the command parameters as follows;
– value_duration = 1000
– value_unit = Time
Example B - further procedure
Follow the steps below to take inventories if the light barrier is interrupted until the light
barrier is no longer interrupted:
1. Create an If condition that then always triggers the command "riggerSource"
(value_triggerMode = Start) when the light barrier (input 1) is interrupted.
2. Program the condition so that as soon as the light barrier is no longer interrupted, the
transponder data is fetched by the command getObservedTagIDs".
– value_duration = 0
– value_unit = Time
As an alternative the transponder data can also be fetched automatically using "Events".
3. End the If condition or the command with "value_triggerMode = Stop".
12.3

Filtering out transponders detected due to overshoot

Description
In this example there are production lines close together that are controlled by read points.
This can lead to the read point of a production line identifying the transponders of the other
production line due to overshoot.
The aim is that the read point involved recognizes these transponders and filters them out.
Antenna parameters and algorithms used
● RSSI threshold
● Input attenuation
● Smoothing
● RSSI delta
SIMATIC RF600
Configuration Manual, 11/2018, C79000-G8976-C386-07
12.3 Filtering out transponders detected due to overshoot
Application examples
235