BindPhase
The
BINDPHASE
execute binds and unbinds a material-enabled phase to or from a specified container and phase. The BINDPHASE
execute does not check for valid Phase, Container, Lot, or Label. Ensure that the binding information provided to the FactoryTalk Batch
Server is accurate. The phase must not be active for the execute to be processed.The format and return for this execute includes:
Execute Format | A FactoryTalk Batch Server supports an execute with this format:[BINDPHASE( Item,UserID,PhasePath,ContainerName,EqModuleID,
Lot,Label )] The unbind requires: [BINDPHASE( Item,UserID,PhasePath, <sp>,PROMPT or AUTOMATIC ,<sp>,<sp>)] | ||
where: | Item | Response item name as specified by the client. | |
UserID | User Identification entered into the event journal associated with this event. | ||
PhasePath | Recipe phase path to be bound: <FullPath> Hierarchical phase paths: Procedure Level: CreateID \t UnitProcName \t OperName \t PhaseName Unit Procedure Level: CreateID \t OperName \t PhaseName Operation Level: CreateID \t PhaseName | ||
ContainerName | Name of the container to be selected for binding. Can be a space character <sp>. | ||
EqModuleID | New bind target for the recipe phase: <BindTarget> | ||
Lot | Lot name to further specify the container for binding. Can be a space character <sp> or blank to match any lot. | ||
Label | Label name to further specify the container for binding. Can be a space character <sp> or blank to match any label. | ||
where: | <BindPath> | is | <ResourceID> | <Prompt> | <Automatic> |
where: | |||
Field | Format | Description | |
<ResourceID> | ASCII - Integer | Equipment phase resource ID to which the recipe phase is binding. | |
<Prompt> | ASCII – String | String literal PROMPT. This indicates that the specified recipe phase is to be unbound and replaced with a prompt based binding mechanism. | |
<Automatic> | ASCII – String | String literal AUTOMATIC. This indicates that the specified recipe phase is to be unbound and replaced with a first-available based binding mechanism. | |
Action | A successful BINDPHASE execute results in the binding and unbinding of the specified recipe phase, or in the queuing of the bind request pending a signature. | ||
Return Format | The item populates with this data: SUCCESS: | SUCCESS: <ActionID> | FAIL: <message> | ||
where: | |||
Field | Format | Description | |
<ActionID> | ASCII – Integer | Action ID associated with signature(s) generates as a result of the bind request. The bind request is not processed 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 binding: BINDPHASE(Item,STATION5/Operator,34 \t MCLS_SWEETCREAM
_UP:1,TEMP_EGG,NP_ADDEGG_M1,,) An execute string for unbinding: BINDPHASE(Item,STATION5/Operator,34 \t MCLS_SWEETCREAM
_UP:1, ,PROMPT,,) or BindPhase(Item,Station2/View,34 /t SWEETCREAM_UP:1 /t WHIPIT_OP:1 /t DOSE:1, TANK1, 23, LOT_A, LABEL_GOODSTUFF) Could return: SUCCESS:997 |
Provide Feedback