Skip to content

Diagram ControllerInterface

Design_UserDoc_ControllerInterface ControllerInterface ControllerInterface ControllerInterface->ControllerInterface implements 0..N Command Command ControllerInterface->Command command 0..N IfaceState IfaceState ControllerInterface->IfaceState state 0..N AInterfaceData AInterfaceData ControllerInterface->AInterfaceData data 0..N PassThroughParameter PassThroughParameter ControllerInterface->PassThroughParameter passThroughParameter 0..N InputOutput InputOutput ControllerInterface->InputOutput inputOutput 0..N Controller Controller Controller->ControllerInterface controllerInterface 1..1 Controller->Controller extends > extends 0..1 AbstractChild AbstractChild Controller->AbstractChild child 0..N InterfaceData InterfaceData InterfaceData->InterfaceData extends > extends 0..1 CustomDataGroup CustomDataGroup InterfaceData->CustomDataGroup dataGroup 1..1 AbstractChild->ControllerInterface requiresInterface 1..1 AInterfaceData->InterfaceData DataTypeIoType DataTypeIoType InputOutput->DataTypeIoType DigitalType DigitalType InputOutput->DigitalType DataTypeInput DataTypeInput DataTypeIoType->DataTypeInput DataTypeOutput DataTypeOutput DataTypeIoType->DataTypeOutput DigitalInput DigitalInput DigitalType->DigitalInput DigitalOutput DigitalOutput DigitalType->DigitalOutput

ControllerInterface

Definition of public informations of a [Controller]. A Controller interface can implement other interfaces and inherits all its elements.

class ControllerInterface extends NamedResource, AnnotableComment, DatatypeLibraryOwner

Controller

The controller is the central element of a UP application. A controller defines the smallest, intrinsically functional unit.

A controller essentially consists of two main elements: * Interface and data * [UP - Statemachine]

In addition, the controller has the definition of relations to [Child] controllers.

A controller can also be described as an instantiable type that is instantiated in the [UP - ControllerTree].

class Controller extends NamedResource, AControllerDescription, AnnotableComment, DatatypeLibraryOwner, RootVariableLibrary, RootVariableName, AOoDomainRoot, ACallingBaseElement, AResourceWithType

Command

Commands are typically used to trigger transitions between states. Each controller has a command interface through which actions can be triggered on the controller. Commands are defined globally. However, a controller only knows the commands to which it should respond. The parent-child relationship in the controller tree automatically establishes a command channel for top-down commands.

class Command extends NamedResource, AnnotableComment, ATextSourceProperty, AResourceWithType

InterfaceData

All public data of a controller is defined in the interface data.

class InterfaceData extends AInterfaceData, FieldUnit, AOoExtendable

IfaceState

class IfaceState extends AState

AbstractChild

abstract class AbstractChild extends NamedResource, RangeChildFieldRef, AOoDomain, APrefixedResource

AInterfaceData

This abstract interface data class is only used for backward compatibility of deprecated Recipe, Parameter, Current, Config classes. It will be removed in future.

abstract class AInterfaceData extends InterfaceArrayVariable

CustomDataGroup

class CustomDataGroup extends NamedResource, AOmitFromFieldbusOwner

PassThroughParameter

Input and output variable that is part of a controller interface and serves as a formal pass-through parameter.

class PassThroughParameter extends Variable

InputOutput

Input and output variables ensure the connection to the real hardware. In the specific hardware configuration, these signals are mapped to inputs and outputs.

abstract class InputOutput extends APrefixedResource, AMainVariable, AnnotableComment

DataTypeIoType

abstract class DataTypeIoType extends Variable, InputOutput

DigitalType

abstract class DigitalType extends NamedResource, InputOutput, AResourceWithType

DigitalInput

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

class DigitalInput extends DigitalType

DigitalOutput

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

class DigitalOutput extends DigitalType

DataTypeInput

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

class DataTypeInput extends DataTypeIoType

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