Bind

The
BIND
 execute binds and unbinds a unit procedure step or operation step to or from a specified unit.
The format and return for this execute includes:
Format and return for this execute
Execute Format
A
FactoryTalk® Batch
 Server supports an execute with this format:
[BIND(
<Item>, <UserID>, <ProcedureID>, <UnitID>
)]
where:
<Item>
Item name on which to place the response.
<UserID>
User ID who issued the execute is entered into the event journal associated with this event.
<ProcedureID>
Recipe procedure path being bound to the specified unit: <FullPath>
<UnitID>
Unit Resource ID binds to the step. If the recipe is a procedure, use:
  • -1
     to unbind and change to PROMPT (for prompted binding)
  • -2
     to unbind and change to FIRST_AVAIL (for first available unit)
Prompt (-1) and First_Available (-2) are not valid options for a unit procedure recipe.
where:
<FullPath>
is
<CreateID>
/t
<Path>
<Path>
is
<StepIdentifier>
|
<StepIdentifier>
/t
<Path>
where:
Field
Format
Description
<CreateID>
ASCII - Integer
Unique batch ID assigned by the
FactoryTalk Batch
 Server.
<StepIdentifier>
ASCII – String
Step identifier (for example, Mix:1)
Action
A successful BIND execute results in the specified unit procedure step or operation step binding to the specified unit.
Return Format
The item populates with this data:
SUCCESS: | SUCCESS:
<ActionID>
| FAIL:
<message>
| FAILED
where:
Field
Format
Description
<ActionID>
ASCII – Integer
Action ID associated with signature(s) generates as a result of the bind request. The bind request will not process unless all signature requests are successfully signed off.
<message>
ASCII - String
Error message appropriately formatted for operator display.
The following table shows an example of the return on this execute.
Example:
An execute string for a procedure recipe example:
Bind(Item,Station2/View,34 /t sweetcream_up:1,55)
This could return:
SUCCESS:997
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal