Navigation: Filtering & Collection > Event Bindings > Available Bindings > PLC Automation Bindings >


Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →



Binding Function



Binding ID



Binding Description

Sends Part Tag Data to PLC and SQL



This Binding combines both RFDPLC1 and RFDHDSP logic into one Binding for performance purposes to avoid the latency in between synchronous bindings.  RFDPLC1 communicates directly with the PLC gateway controller via an IP address and RFDHDSP calls a SQL Stored procedure. This Binding was initially developed for paint load use cases but can also be used for other robotic operations such as Stripe, Buff, etc.


This Binding function performs the following logic:

Collects whatever tags are read during a given read event cycle from a given portal, and sends them in real time.

Supports full GPIO script as a result of standard match / nomatch / notag variables. Typically a sensor input is used to trigger the read cycle for the specified time period (e.g. 2 seconds)

Can optionally pass a UDA payload to robotic controller as specified in the UDA Grouping 1 or 2.

Max Tags in read event cannot be > 6 (the max parts that can be mounted on post fixture), if more in read event cycle (because of signal bounce) then drops tags >6 with the weakest RSSI and does not update TAGVS (for those tags dropped).  The assumption is that the weak tag(s) dropped were seen upstream prematurely and will be seen again when the post gets closer to portal. This modified tag list (from PHLOG) will be now be used for the RFDHDSP logic so both systems are in sync.  Note: PLC side is already dropping more than 6 currently if received so we are missing tags today until this fix is put into place.

Splits out 'Color Flag' tags from those of parts if the read cycle were to actually see parts in the same payload as the color flag (rouge tag read from upstream signal bounce). So if the Inventory type of tag is ‘COLOR FLAG’ then this will be included in separate XML payload.  However, in order not to confuse the post indexing logic (two) payloads for a single trigger event will not occur.  Operationally, whenever there is a paint flag there will be (3) empty posts behind it, therefore the color flag read event will be held back and associated to the next empty post.  So in this case instead of sending an 'no tag' XML payload for an empty post the part tags read will be associated with the previous (correct) Color flag event.

Both PLC1 and HDSP use TAGVS as tag last seen entity (reader/antenna name level) to determine dwell. Note when multiple bindings used together there is a flag that is passed to each binding that dictates whether it is the last Binding to be processed for a given schedule and thus the last binding updates TAGVS at that time. With this in place there is no contention between PEVG and PLC1 or HDSP when used together as bindings associated with a reader schedule.


None at this time.


This binding can be tested with a PLC_LOAD_EMULATOR that will return various reply states. Note: this utility uses Port 10002 and the IP address of your testing machine. So an example would be in the IP address of the Binding.

If triggered the dwell time can be removed

Files Updated


Program Name

URI set to RFDPLC2

Binding Setup

Binding Properties

Email Notification Receipient

The email address to send binding specific alerts. Note: This overrides the default SMTP Recipient value under System Settings


UDA Grouping

Specifies a UDA grouping (User Defined Attributes) to be included with the XML payload.


Dwell Time

This is the time period that TagNet will ignore further read events until the dwell period has expired. For example on a paint conveyor, when a tagged part goes through the read zone and TagNet changes its location state from A to B, the dwell period gives it time to move away from the read zone (ignores it) before it is evaluated again and send to PLC/MES as an event. The dwell time should be long enough to allow the part to move away from the portal read zone but not too long that if it is seen back on the same conveyor (e.g. 55 minutes later) for a 2nd pass through the choke point  it will be not be ignored. Refer to the the Binding Change for detailed explanations of this directive.


Interface IP Address

The IP address of the device that the Tag data is to be sent to. Example here would be the PLC gateway controller communicating with the PLC or the actual PLC Robotic IP address.


Terminate With

Indicates to receiving endpoint that XML document is complete. Allows for NULL, CR (Carriage Return), EOT (End-of-Transmission char), LF (Line Feed) or TAB (tab to next column) making it flexible depending on the requirements of the interface.



Copyright © 2024 Stratum Global, Inc.