Operation definition

From PlcWiki

Revision as of 15:34, 15 February 2011

Each operation needs to be defined by its index and type. All other parameters are optional, but some of them are necessary for a valuable operation definition:

Operation.name.Type = <Operation type>
Operation.name.Index = <Operation index>

for example:
Operation.AirbagSN.Type = Serial
Operation.AirbagSN.Index = 2

A parameter name joins all operation parameters together.

Operation type can be one of the following ones:

SequenceCheck
ProductConfiguration
LastWPCheck
Serial
PartCheck
PartCode
CableCheck (Poka-Yoke Check)
Tightening
VisualCheck
OutputCheckCorrection
OutputCheck
PidWrite
ixpioSignal
VisionSensor
PreSequence
Measurement
RackPartCheck
BlindAudit
SerialInput

Operation parameters

Stopping the conveyor

The conveyor can be stopped in case of NOK result of the operation. In case of an operation type OutputCheck the conveyor is stopped immediately after the product ID is scanned. The following parameter is used to define it:

(bool) Operation.name.SendConveyorStopWhenNOk = No | Yes

Automatic sent to rework

The product can be sent automatically to a rework procedure using this parameter:

(bool) Operation.name.SendToReworkWhenNOk = No | Yes

Restriction of a usage of Invalid label bar code

For safety critical operations like VW baugruppen it should be set to "No". Then the control bar code "Invalid label" (PLCIL) is not accepted. The logic is, that a product without safety critical documented items is not cempletely assembled and should not be released to the customer. If it is not possible to scan the part label, the part needs to be changed to the correct one. So then it is necessary to assemble another piece or sent the product to a rework station.

(bool) Operation.name.InvalidLabelAllowed = Yes | No

Operation dependencies

The possibility to fulfill the operation can depend on other operation(s). Starting the client release 1102151134 it is possible to define multiple dependencies. The full chain of dependencies is considered after this release as well.

If the operation dependencies are not satisfied, the operation can't be started.

In case of tightening operations the tightening machine is blocked.

In case of scanning operations the scanned bar code is not accepted (an invalid ID is reported). Enabled scanning operations are highlighted (white) on the screen. Operations with not-yet-satisfied dependecies are displayed in gray.

In case of pick-to-light operations the pick-to-light device is not activated.

The dependencies are defined by the following parameter:

(int) Operation.name.DependsOn[0-9]

For the back compatibility it is possible to use the parameter

(int) Operation.name.DependsOn
which is an equivalent to
(int) Operation.name.DependsOn[0]

Examples of configuration:

Operation.PartCheck_PassengerAirbag.Type = PartCheck
Operation.PartCheck_PassengerAirbag.Index = 3
Operation.PartCheck_PassengerAirbag.WindowTitle = Beifahrerairbag
Operation.PartCheck_PassengerAirbag.ToDoMessage = Scanne Seriennummer Airbag
Operation.PartCheck_PassengerAirbag.DependsOn[0] = 2
Operation.PartCheck_PassengerAirbag.DependsOn[1] = 5