JUMO LOGOSCREEN 601 Manual
  1. Manuals
  2. Brands
  3. JUMO Manuals
  4. Voice Recorder
  5. LOGOSCREEN 601
  6. Manual

JUMO LOGOSCREEN 601 Manual

Paperless recorder, st editor
Hide thumbs Also See for LOGOSCREEN 601:
Table of Contents

Advertisement

Quick Links

JUMO LOGOSCREEN 601/700
Paperless recorder
ST Editor Manual
70653000T96Z001K000
V1.00/EN/00710350

Advertisement

Table of Contents
loading

Related Manuals for JUMO LOGOSCREEN 601

Summary of Contents for JUMO LOGOSCREEN 601

  • Page 1 JUMO LOGOSCREEN 601/700 Paperless recorder ST Editor Manual 70653000T96Z001K000 V1.00/EN/00710350...

  • Page 3: Table Of Contents

    Contents Contents Introduction ........... . 5 Safety information .
  • Page 4 Contents Function modules ..........49 Software up/down counter .

  • Page 5: Introduction

    Introduction 1 Introduction Safety information Note symbols NOTE! This symbol refers to important information about the product, its handling, or additional benefits. REFERENCE! This symbol refers to additional information in other sections, chapters, or other manuals. Intended use The device is designed for use in an industrial environment as specified in the technical data. Other uses beyond those defined are not viewed as intended uses.
  • Page 6 1 Introduction...

  • Page 7: Operation

    Operation 2 Operation The ST editor is part of the setup program and is started by clicking on the corresponding button in the "ST code" window (see operating manual). The finished application is transmitted to the device as ST code and continuously processed in the inte- grated ST module.
  • Page 8 2 Operation Some functions of the menu bar are also available in the toolbar and can be selected by a simple mouse click. The meaning of the symbols is briefly described by a tool tip function (hover over the respective symbol with the mouse pointer).
  • Page 9 2 Operation Edit window The program is created in the edit window by declaring variables and constants, creating program code and using commentary texts. It is possible to change the font size using Ctrl+Mouse wheel or Ctrl+Shift+Arrow key. Version name In order to assign a version name to the program, the keyword @VERSION followed by the version name must be used in a comment line.
  • Page 10 2 Operation Status bar The status bar is located at the bottom of the program interface and indicates whether the editor or debug mode is active. In the case of debug mode, the individual states (STOP, RUN, PAUSE) are displayed. Further information about the functions of the menu bar and the toolbar is also displayed in the status bar (hover over the individual function in the respective menu or over the symbol in the toolbar with the mouse pointer).
  • Page 11 2 Operation NOTE! The "Definitions" tab is device-dependent and contains definitions (names for fixed values) that are fac- tory-set or created by the user. If the ST module of the respective device supports definitions, these are described in a separate chapter "Definitions". Force window The force window consists of three parts (tabs).
  • Page 12 2 Operation NOTE! Variables that are stored via power off (retain variables) are not supported by all device types. Variables and constants can be displayed and observed during debugging in the "Monitoring" tab. To do so, they must be copied from the edit window or the "Variables" tab by dragging and dropping and pasted into the "Monitoring"...
  • Page 13 2 Operation • Current program will remain loaded on the control. The program last loaded onto the device in debugging mode must be used. • Load previous program onto the control. The program last loaded onto the device in debugging mode must not be used. Instead, the previous (continuously loaded onto the device) program is used, if available.
  • Page 14 2 Operation...

  • Page 15: Definitions

    Definitions 3 Definitions The "Definitions" tab is device-dependent and contains definitions (names for fixed values) that are fac- tory-set or created by the user. The "User-defined" (empty) and "Texts" folders are available per default. Depending on the configuration (setup program), further folders with the designation "Process screen x" (x = number of the process screen in the setup program) are used.
  • Page 16 3 Definitions Example: CASE integer_variable OF definition1: integer_variable := 5; definition2, definition3: integer_variable := 10; END_CASE; Texts The folder "Texts" lists all definitions (TxtNo1 to TxtNo...) which represent the numbers of the texts in the text list of the setup program. These definitions can be used in the ST code, for example, to address a batch text.
  • Page 17 3 Definitions These definitions - as well as the possibility of changing texts in the ST editor - are intended in particular for the following purposes: – Process screen: Control of the text in an object by an ST analog output (object "Text selection by value") –...
  • Page 18 3 Definitions The folder contains the definitions for the process screen (here: P1_ProcPicIndex) and for each object for which a name was assigned in the process screen. The object name assigned by the user (here: ob- ject 1, ...) is preceded by a "Px_" for the relevant process screen (here: P1_Object_1, ...). This ensures that object names that are used in several process screens are unique in the ST code.

  • Page 19: System Variables

    System variables 4 System variables The system variables include the input and output variables as well as the internal variables. The input and output variables can be used to exchange values of different data types between the de- vice and the ST module integrated in the device. The internal variables are only relevant within the ST module and can be used to implement certain functions.

  • Page 20: Output Variables

    4 System variables Output variables The output variables are used to transfer the values generated in the ST module to the device. The output variables are available for configuration in the setup program and in the selectors (analog selector or digital selector) on the device, and can be used individually. For certain output variables there are associated variables in the variable window with the designations "...conf"...
  • Page 21 4 System variables real_out Designation Designation in the setup Description program and on the device real_out01 ST analog output 1 Real output variables; flexible use in the setup pro- gram and on the device (analog selector) real_out40 ST analog output 40 A description text can be assigned to each variable in the setup program.

  • Page 22: Internal Variables

    4 System variables Internal variables The internal variables can be used in the ST code to implement certain functions. ext_error Designation Description ext_error Integer variable The variable indicates errors that occurred during accesses outside the ST module. In the event of an error, the variable returns a value > 0 (no error = 0). reset_flag Designation Description...

  • Page 23: Alias Names

    4 System variables Alias names Alias names can be assigned to system variables: The function of the system variable can be described by using an alias name. In this example the alias name "Switch" is assigned to the system variable bool_in01. When the dialog is closed with "OK", the name entered is checked for uniqueness.
  • Page 24 4 System variables...

  • Page 25: Data Types And Fields

    Data types and fields 5 Data types and fields Data types The ST module supports the following data types: • Boolean value (BOOL) • Integer without prefix sign, 2 bytes (UINT) • Double integer without prefix sign, 4 bytes (UDINT) •...
  • Page 26 5 Data types and fields Double integer (4 bytes) Keyword: UDINT Value range: 0 to 4294967295 (0 to 2 Declaration of a variable (example): udExample : UDINT; END_VAR Declaration of a constant (example): VAR CONSTANT udConstExample : UDINT := 100000; END_VAR Assignment (example): udExample := 200000;...

  • Page 27: Fields

    5 Data types and fields Fields All data types can also be declared as a one-dimensional or two-dimensional field (array) (see standard DIN IEC 61131-3). The following sections use the data type REAL as an example. One-dimensional field Declaration of variables (example: field with 3 variables): rArrayExample : ARRAY [0..2] OF REAL;...
  • Page 28 5 Data types and fields...

  • Page 29: Operators

    Operators 6 Operators All operators supported by the ST module are shown in the following table. The order in the table de- pends on the ranking of the operators, starting with the highest rank. Operation Symbol Admissible data types Example Brackets (expression) a := 3.0 * (b - 1.0);...
  • Page 30 6 Operators...

  • Page 31: Instructions

    Instructions 7 Instructions The ST module supports the following types of instructions: • Selection instructions (IF, CASE) • Repeat instructions (FOR, WHILE, REPEAT) Selection instructions A selection instruction executes an instruction or group of instructions based on a specified condition. IF instruction The IF instruction specifies that a group of instructions is only executed if the corresponding Boolean expression returns the value TRUE.
  • Page 32 7 Instructions CASE instruction The CASE instruction combines several conditional instructions. It consists of an expression that con- tains an integer variable and a list of instruction groups. Each group is identified by a mark consisting of one or more integers (separated by commas). The value of the variable determines the mark and thus the instruction group to be executed.

  • Page 33: Repeat Instructions

    7 Instructions Repeat instructions With repeat instructions (iterations), instructions and groups of instructions are executed repeatedly. There are three types of repeat instructions: • • WHILE • REPEAT UNTIL FOR instruction The FOR instruction is used if the number of repeats is fixed. Keywords: FOR, TO, BY, DO, END_FOR Examples:...
  • Page 34 7 Instructions REPEAT instruction The REPEAT instruction causes a group of instructions up to the keyword UNTIL to be repeatedly exe- cuted until the associated Boolean condition is true (TRUE). Keywords: REPEAT, UNTIL, END_REPEAT Example: REPEAT i := i - 2; a := a + 2.0;...

  • Page 35: Functions

    Functions 8 Functions The ST module supports the following functions: • Type conversion • Arithmetic functions • Numerical functions • Bit sequence functions (shift functions) • Logical functions • Selection (statistics) • Comparison • Date and time • Other functions Type conversion Admissible data types Argument: UINT, UDINT...
  • Page 36 8 Functions DINT_TO_INT Converts a DOUBLE INTEGER into an INTEGER. Only the lower two bytes are evaluated (bit 0 to bit 15). Examples: a := DINT_TO_INT(1); (* a = 1; 1 = 0000 0000 0000 0001 = 0x0001 *) b := DINT_TO_INT(65535); (* b = 65535; 65535 = 1111 1111 1111 1111 = 0xFFFF *) c := DINT_TO_INT(65536);...

  • Page 37: Arithmetic Functions

    8 Functions Arithmetic functions Admissible data types Argument: UINT, UDINT, REAL (only REAL for negation, only UINT or UDINT for modulo) Result: UINT, UDINT, REAL Addition Addition is an expandable function. The sum of the arguments is returned as the result. Example: OUT := IN1 + IN2 + ...

  • Page 38: Numerical Functions

    8 Functions Numerical functions Admissible data types Argument: REAL Result: REAL ABS (IN) Returns the absolute value of IN. Example: IN := -2.3; OUT := ABS(IN); (* OUT = 2.3 *) SQRT (IN) Returns the square root of IN. If IN is negative, the error value 5.0E+37 is returned. Example: IN := 4.0;...
  • Page 39 8 Functions SIN (IN) Returns the sine of IN (radian). Example: IN := 1.5708; OUT := SIN(IN); (* 1.5708 corresponds to 90°; OUT = 1.0 *) COS (IN) Returns the cosine of IN (radian). Example: IN := 0.0; OUT := COS(IN); (* 0.0 corresponds to 0°;...

  • Page 40: Bit Sequence Functions

    8 Functions Bit sequence functions Admissible data types Argument: UINT, UDINT Result: UINT, UDINT SHL (IN, n) Moves the bit sequence of the IN argument to the left by n bits. Subsequent digits are filled with 0 from the right. Example: IN := 255;...

  • Page 41: Logical Functions

    8 Functions Logical functions Boolean variables are linked logically, UINT and UDINT variables are linked bit-by-bit. If there are more than two parameters, each pair is always linked from left to right. Admissible data types Operand: BOOL, UINT, UDINT Result: BOOL, UINT, UDINT AND link Examples: Logical link:...
  • Page 42 8 Functions Inversion (form complement) Examples: IN := 1; OUT := NOT IN; (* OUT = 0 *) IN := 43690; (* 1010 1010 1010 1010 *) OUT := NOT IN; (* 0101 0101 0101 0101; OUT = 21845 *)

  • Page 43: Selection

    8 Functions Selection Admissible data types Argument: UINT, UDINT, REAL (with SEL, additionally BOOL for the selector) Result: UINT, UDINT, REAL Returns the biggest argument as a result. Example: OUT := MAX(8, 9, 10, 11, 12); (* OUT := 12 *) Returns the smallest argument as a result.

  • Page 44: Comparison

    8 Functions Comparison Admissible data types Argument with LT, LE, GT, GE: UINT, UDINT, REAL, DT Argument with EQ and NE: BOOL, UINT, UDINT, REAL, DT Result: BOOL < (lower than) Compares arguments on whether one is smaller than another. Examples: bOUT := IN1 <...

  • Page 45: Date And Time

    8 Functions Date and time These are specific functions that are not part of the DIN IEC 61131-3 standard. For example, these functions can be used to query the input variable rtc.cdt, which returns date and time of the device. Admissible data types Argument: DT, DATE_AND_TIME Result: UINT...

  • Page 46: Other Functions

    8 Functions Other functions These are specific functions that are not part of the DIN IEC 61131-3 standard. IS_VALID Checks the validity of a REAL number. The result is a Boolean value (valid = TRUE, invalid = FALSE). Values ≥ 1.00E+37 (general error value) are considered as invalid, as are the values "Infinity" (INF) and "No number"...
  • Page 47 8 Functions The return value (BOOL) indicates whether the function was executed successfully (TRUE) or whether an error occurred (FALSE). Order of arguments: SET_OBJECT_COLOR (ProcPicIndex, ObjectIndex, ColorType, ValueRed, ValueGreen, ValueBlue) Example: bOUT := SET_OBJECT_COLOR(0, 9, 0, 255, 0, 0); (* Sets the foreground color of process screen 1, object 10 to red. *) GET_OBJECT_COLOR_RED The return value (UINT) returns the RGB value (UINT) of the red portion of an object in a process screen.
  • Page 48 8 Functions Order of arguments: GET_OBJECT_VISIBLE (ProcPicIndex, ObjectIndex) Example: bOUT := GET_ OBJECT_VISIBLE(1, 4); (* Returns the status of the parameter "Visible" of process screen 2, object 5. *) SET_OBJECT_EDITABLE Sets the editability of an object in a process screen. The return value (BOOL) indicates whether the function was executed successfully (TRUE) or whether an error occurred (FALSE).

  • Page 49: Function Modules

    Function modules 9 Function modules Instance A function module – called a function block in the ST editor – is a program organizational unit that returns one or more values when executed (see also standard DIN IEC 61131-3). A function module can exist in several instances (copies).

  • Page 50: Software Up/Down Counter

    9 Function modules Software up/down counter The counter provides the following functions: • Counting up • Counting down • Reset the counter to 0 • Set an upper counter value • Query in case the upper counter value is exceeded •...

  • Page 51: Impulse Generator

    9 Function modules Impulse generator The following diagram illustrates the operating principle of the impulse generator: Call TP<instance> (IN, PT, TimeBase); Inputs Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL Positive edge at IN sets Q for the time PT to TRUE UINT Time (unit: TimeBase), for Q = TRUE, IN = TRUE TimeBase...
  • Page 52 9 Function modules The time resolution of the pulse length depends on the cycle time of the device (example: 150 ms). Example TP01(IN, 5, 3); (* Positive edge at IN sets TP01.Q for approx. 5 minutes to TRUE (note time resolu- tion).

  • Page 53: Switch-On Delay

    9 Function modules Switch-on delay The following diagram illustrates the operating principle of the switch-on delay: Call TON<instance> (IN, PT, TimeBase); Inputs Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL IN = TRUE sets Q = TRUE, after the time PT is expired UINT Delay time (unit: TimeBase) TimeBase...
  • Page 54 9 Function modules The time resolution of the delay time depends on the cycle time of the device (example: 150 ms). Example TON01(IN, 6, 2); (* IN = TRUE sets after 6 seconds TON01.Q to TRUE. TON01.Q remains TRUE as long as IN = TRUE. TON01.ET returns the elapsed time in seconds from IN = TRUE to TON01.Q = TRUE (max.

  • Page 55: Switch-Off Delay

    9 Function modules Switch-off delay The following diagram illustrates the operating principle of the switch-off delay: Call TOF<instance> (IN, PT, TimeBase); Inputs Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL IN = TRUE sets Q = TRUE IN = FALSE sets Q around the time PT delayed to FALSE UINT Delay time (unit: TimeBase)
  • Page 56 9 Function modules Comment The TimeBase parameter is an extension to DIN IEC 61131-3. This extension does not constitute a lim- itation to the standard. According to the standard, the time limit is "implementation-dependent". The values of the inputs/outputs are not retained when the power is turned off. The time resolution of the delay time depends on the cycle time of the device (example: 150 ms).

  • Page 57: Rising Edge Detection

    9 Function modules Rising edge detection This function module detects a rising edge (transition 0 -> 1) . Call R_TRIG<instance> (CLK); Input Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL Due to a rising edge (0 -> 1) at CLK, Q = TRUE Output Parameter Data type...

  • Page 58: Falling Edge Detection

    9 Function modules Falling edge detection This function module detects a falling edge (transition 1 -> 0) . Call F_TRIG<instance> (CLK); Input Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL Due to a falling edge (1 -> 0) at CLK, Q = TRUE Output Parameter Data type...
  • Page 59 9 Function modules F_TRIG01 (bool_in01); (* detection of a falling edge at input bool_in01 *) bool_out02 := F_TRIG01.Q; (* short pulse at output bool_out02 for falling edge at input *)

  • Page 60: Bistable Function Sr

    9 Function modules Bistable function SR Bistable function (set priority) with lock Call SR<instance> (S1, R); Inputs Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL S1 = TRUE sets Q1 = TRUE BOOL R = TRUE sets Q1 = FALSE, if S1 = FALSE Outputs Parameter Data type...

  • Page 61: Bistable Function Rs

    9 Function modules Bistable function RS Bistable function (reset priority) with lock Call RS<instance> (S, R1); Inputs Parameter Data type Description <Instance> 01 to xx (specify instance with two digits) BOOL R1 = TRUE sets Q1 = FALSE BOOL S = TRUE sets Q1 = TRUE, if R1 = FALSE Outputs Parameter Data type...
  • Page 62 9 Function modules...
  • Page 64 JUMO GmbH & Co. KG JUMO Instrument Co. Ltd. JUMO Process Control, Inc. Street address: JUMO House 6733 Myers Road Moritz-Juchheim-Straße 1 Temple Bank, Riverway East Syracuse, NY 13057, USA 36039 Fulda, Germany Harlow, Essex, CM20 2DY, UK Delivery address:...

This manual is also suitable for:

Logoscreen 700706521706530

Table of Contents