Chapter 12 Instruction List 12.1.3 Important Points About Instruction Lists Every line on an instruction list is regarded as an instruction except the instruction CAL, and therefore an operator and the operands for the operator can not be in different lines. If an operator and the operands for the operator are in two lines, these two lines will be regarded as two incomplete instructions. Besides, no spaces can be inserted into the instruction names, the function block names, and the operand names on an instruction list. Otherwise, the instructions, the function blocks, and the operands will not be recognized if the program is compiled.
As long as the format of an instruction is not destroyed, leaving blank spaces and starting new lines are allowed. Fullwidth characters and halfwidth characters in ISPSoft are regarded as different characters. Please avoid using fullwidth characters lest they should be identified incorrectly. Instruction lists are case-insensitive. “OUT” and “Out” are considered to be the equivalents of “out”. If users want to use constants in a program created by means of an instruction list in ISPSoft, the constants must be represented in the following ways. Decimal value: 23456 (A value which is not preceded by any mark will be regarded as a decimal value.) Hexadecimal value:
16#5BA0 (A value is preceded by 16#.) Octal value: 8#55640 (A value is preceded by 8#.) Binary value: 2#101101110100000 (A value is preceded by 2#.) String: “XYZ” (Characters are put in double quotes.) BOOL: Need to use normally-open contact / normally-closed contact AH/AS Series: SM400/ SM401 DVP Series: M1000/ M1001 When using ARRAY, the input format is Identifier[Index] and since IL currently does not support index value, therefore, users can use decimal-constant smaller than array, but must begin with 0. When using function blocks or APIs, if there is no LD commands or logic calculation area before giving an instruction, an error will occur during compiling. 12-5