Particularities of ST editor

Please note the following when using the ST editor.

• There are no EN/ENO functions and function blocks in the ST editor. Use an IF or CASE statement instead to control the execution of the function or function block.

• For Boolean constants, TRUE and FALSE as well as the Boolean zero (0) and one (1) can be used.

• The FP Pulsed Library's P instructions are not available in the ST editor.

• The address functions of the FP Tool Library do not distinguish between input and output functions:

IF start then
    F10_BKMV( s1_Start:= source_Array[1],
        s2_End:= source_Array[3],
        d_Start=> target_Array[0]);
END_IF;

• When debugging an IF or CASE control structure, the program code within the control structure will run even if the control condition is not TRUE. However, the individual commands will not be executed.

• Do not use the value of the control variable after the loop is finished because different values have been assigned to it.

• Programming loops with many steps may extend the scan time of the PLC. Increase the settings (system register 30) or try to divide the program into several cycles.

• The data type of a Boolean or numeric literal can be specifiedby adding a type prefix to the literal, consisting of the name of an elementary data type and the '#' sign. For example INT#2 or REAL#-3.2.To identify literals, some competitor programming systems require typed literals. For this reason, Control FPWIN Pro7 also supports typed literals. Because internally the compiler of Control FPWIN Pro7 automatically assigns the right type to literals, it is not required to explicitly type literals as described above.

• The case of letters is not significant in:

  • identifiers (e.g., the identifiers abcd, ABCD and aBCd are equivalent)

  • keywords (e.g., the keywords "FOR" and "for" are equivalent).