Value fields

Value fields in →FBD may contain expressions according to ST. Use value fields for:

logi.CAD 3 provides the following types of value fields :

images/s/b2ic8e/9012/1ca6q62/_/images/icons/emoticons/information.svg If the FBD-editor and its elements are displayed differently in your logi.CAD 3 version, the system integrator has changed the styles for the FBD-editor. In this case and for information about the changed representation, please contact your system integrator.

Value field within the drawing field

Use a value field within the drawing field in order to create an →assignment.

Such a value field may get a value from another FBD-element (e.g. from another value field) via its input, the value of the value field may be assigned to another FBD-element via its output. The assignments are visualized by lines connecting the value field with the other FBD-elements.

Representation

Example for assigning a value for In1 to Var1 and further to Out1:

images/download/attachments/443058580/ValueFieldsAndLines-version-1-modificationdate-1589278331851-api-v2.png

The input connection point (short: input) is located on the left side of the value field left, the output connection point (short: output) on the right side.

Labels within the value field inform you to which variable section the entered variable belongs.

Example

Meaning

images/download/thumbnails/414777645/ValueFieldVAR-version-1-modificationdate-1534167497826-api-v2.png

value field with an internal variable (also known as "local variables") or with a →global variable

images/download/thumbnails/414777650/ValueFieldIN-version-1-modificationdate-1534167519201-api-v2.png

value field with an →input variable

images/download/thumbnails/414777655/ValueFieldOUT-version-1-modificationdate-1534167537427-api-v2.png

value field with an →output variable

images/download/thumbnails/414777660/ValueFieldINOUT-version-1-modificationdate-1534167556998-api-v2.png

value field with an →in-out variable

images/download/thumbnails/414777665/ValueFieldEXT-version-1-modificationdate-1534167575879-api-v2.png

value field with an →external variable

images/download/thumbnails/414777670/ValueFieldLit-version-1-modificationdate-1534167596686-api-v2.png

value field with a →literal

Color/style of a value field is determined by the data type that is assigned to the variable resp. that is valid for the literal. The alignment of the value field content depends on the connection of the value field (see the example with the connected value fields).

Value field within the interface for a block

Value fields that are created within the interface of a block are also identified as internal value fields. Use such a value field in order to set a →literal as default. As the value field is attached to a specific input of the block, this default value is valid for the input when the block is →called within the drawing field .

You are able to change the default value for the block call by:

  • entering a different literal or even a →variable within the value field displayed within the interface (see "Editing expression in value field")

  • connecting the input with a different FBD-element (see "Connecting FBD-elements by lines")
    Subsequently, the value field within the block interface disappears. The input within the value field is no longer significant for the execution of the block because the value of the FBD-element is used.

Representation

Example for the block interface in which the value of the input is assigned to its opposite output (the value is predefined by the 2 value fields within the interface) :

images/download/thumbnails/431556346/FBDCall_IntVF1-version-1-modificationdate-1568616185634-api-v2.png

images/s/b2ic8e/9012/1ca6q62/_/images/icons/emoticons/information.svg The →OLT-fields on the right indicate which value is assigned to the respective output.

Example for the same block interface after each input has been connected with a value field within the drawing field:

images/download/attachments/431556352/FBDCall_IntVF2-version-1-modificationdate-1568616214731-api-v2.png