Diagram InterlockInstance

InterlockInstance

class InterlockInstance extends RootVariableLibrary, RootVariableName, BaseControllerInstanceInteraction

Level

The hierarchy of the ControllerTree is defined by levels. The number of levels used is not limited. Within the levels the controller is instantiated.

The usual levels are defined as follows:

Level 4, Top Level: MAIN controllers and "general services" like HMI, Filehandler, ... which have nothing to do with the control function.

Level 3, Group: Group controller, strongly machine-related, head of an entire function group.

Level 2, module: Modules which perform a corresponding function in a group can also be instantiated several times within group or within a whole machine.

Level 1, Element group: Smallest group of similarities, summary of simple element controllers, which do not necessarily have to be addressed separately.

Level 0, Element: Lowest level of the controller, fulfills exactly one task, reusable, interface to the hardware.

Driver, Driver: Hardware-specific configuration, interface between element controller and hardware (typical application for controllers with motion tasks -> controller is identical, drivers differ depending on the drive used).

class Level extends NamedResource

BaseInputPort

abstract class BaseInputPort extends Resource

AbstractInterlock

abstract class AbstractInterlock extends NamedResource

InterlockRef

abstract class InterlockRef extends Decorator

BaseOutputPort

abstract class BaseOutputPort extends Resource

DataTypeOutput

Use DataType output to define type of output. As example for analog types, structured types or array outputs.

If a ScaleFunction is defined, the analog output is not available in the project (only the scaled value).

class DataTypeOutput extends DataTypeIoType

AbstractMessageDefinition

abstract class AbstractMessageDefinition extends AnnotableComment

DigitalOutput

Name has to be defined without prefix do_ and also without Datatyp in name

class DigitalOutput extends DigitalType