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

RFDLOAD

Still need help? Create a Support Ticket with Stratum Support

Send comments on this topic.

← Previous Next →

 

 

Binding Function

RFDLOAD

 

Binding ID

ROBOTIC_LOAD_UNLOAD 

 

Binding Description

Robotic Load & Unload to PLC

 

Purpose

This Binding is designed to communicate with a Material Handling Robot that picks up the tagged object and provides a trigger for TagNet to identify the object. The Binding resolves the tag to that object and initiates a simple XML exchange to the Robotic PLC controller. The Binding uses GPIO script and ADAM I/O controller to listen for trigger events as well as turn on stack light conditions as configured.  This function makes use of the power of TagNet UDA's and the ability to group those UDA's for variable content in the XML.

Logic

Reader operation at a given robot is controlled by trigger events as configured in the Binding:

There are two modes of operation based on which Trigger input is provided. The XML Schema chart below shows what 'Core' attributes are sent in the XML and what 'variable' attributes are included based on the UDA Grouping  

1.When the Robot provides a trigger state as specified with Antenna 1 Trigger (e.g. Input-1-ON), it instructs TagNet to perform a read cycle to scan the door tag and send a Robotic_Load XML payload as configured in UDA Grouping 1. This XML tells the Robot what the Item # it is and its manufacturing UDA attributes including what antenna saw the tag (on all 4 corners of the robotic EOAT). This antenna value dictates what the orientation of the door is when picked up so the Robot can rotate/swivel as necessary before loading onto conveyor.

Note: the trigger from the robot is only provided when the door is picked up and in safe area for read event singulation (e.g. away from the stack of doors on the WIP pallet feed).

2.Currently Antenna 2 Trigger does not send any XML payload. This is an future trigger based on the Line determining there is a defect associated with door as it is removed by a robot.  Currently only an IMOVE action would take place (if configured) however a future consideration was for the binding to insert a record into LOCEX with a defect UDA code and/or set Lot status on LOCIN. 

IMOVE rules are applied are the very end of logic only if enabled.

Supports full GPIO script as a result of standard MATCH / NOMATCH / ERROR / NOTAG variables.

Restrictions

None identified

Comments

 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 192.168.1.140:10002 in the IP address of the Binding.

Files Updated

RFDLOCIN, RFDLOCIH (Insert), RFDTAGVS

Program Name

URI set to RFDLOAD

Binding Setup

Binding Properties

Email Notification

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

 

Antenna Trigger

Specifies the state of a Trigger that will initiate a UDA grouping payload (e.g. Antenna 1 trigger value sends UDA Grouping 1).  Note: this directive should not be confused with the physical 'Antenna 1' as all antennas enabled in the physical reader profile are activated.

 

UDA Grouping

Specifies a UDA grouping (User Defined Attributes) to be included with the XML payload based on the Antenna Trigger directive (e.g. Antenna 1 trigger value sends UDA Grouping 1).

 

Inventory Movement Rules

In the example below, the Inventory Movement Rules are set to *YES. Refer to the the Binding Change for detailed explanations of each directive.

 

 

Shown below are the XML transaction sets:

 

Action

XML Schemas

Robotic Load Operation

<?xml version="1.0" encoding="UTF-8"?>

 

<Bayer-Robotic-Load>

 

  <DoorItemNo>16688HB</DoorItemNo>

  <TagLocation>TOPRH</TagLocation>

  <DoorAttributes>

    <THICKNESS>1.375</THICKNESS>

    <OUT_SERVICE_COLOR>Brown</OUT_SERVICE_COLOR>

    <RECIPE_CONFIG>001</RECIPE_CONFIG>

    <WIDTH>32</WIDTH>

    <HANDING>LH</HANDING>

  </DoorAttributes>

 

</Bayer-Robotic-Load>

 

** DoorItemNo Mapped to the ERP field in the Product Master

** TagLocation is the actual Antenna Name as user defined in Reader profile

Robotic Load Operation

(Response)

<?xml version="1.0" encoding="UTF-8"?>

 

<Bayer-Robotic-Load-Response>

 

  <DoorItemNo>16688HB</DoorItemNo>

  <TagLocation>TOPRH</TagLocation>

  <DoorAttributes>

    <THICKNESS>1.375</THICKNESS>

    <OUT_SERVICE_COLOR>Brown</OUT_SERVICE_COLOR>

    <RECIPE_CONFIG>001</RECIPE_CONFIG>

    <HANDING>LH</HANDING>

  </DoorAttributes>

  <Status>OK</Status>

 

</Bayer-Robotic-Load-Response>

 

** It is expected that the PLC mirror the payload sent and include OK Status in the response back to TagNet to close the socket.

 

 


Copyright © 2023 Stratum Global, Inc.