Appendix J: - Compiler Errors and Warnings

Appendix J: Compiler Errors and Warnings

10.33 Warnings

1100

"Unknown function '<name>' in library."

An external library is used. Please check, whether all functions, which are defined in the .hex file, are also defined in the .lib file.

1101

"Unresolved symbol '<Symbol>'."

The code generator expects a POU with the name <Symbol>. It is not defined in the project. Define a function/program with this name.

1102

"Invalid interface for symbol '<Symbol>'."

The code generator expects a function with the name <Symbol> and exactly one scalar input, or a program with the name <Symbol> and no input or output.

1103

"The constant '<name>' at code address '<address>' overwrites a 16K page boundary!"

A string constant exceeds the 16K page boundary. The system cannot handle this. It depends on the runtime system whether the problem could be avoided by an entry in the target file. Please contact the PLC manufacturer.

1200

"Task '<name>', call of '<name>' Access variables in the parameter list are not updated"

Variables, which are only used at a function block call in the task configuration, will not be listed in the cross reference list.

1300

"File not found '<name>'"

The file, to which the global variable object is pointing, does not exist. Please check the path.

1301

"Analyze-Library not found! Code for analyzation will not be generated."

The analyze function is used, but the library analyzation.lib is missing. Add the library in the library manager.

1302

"New externally referenced functions inserted. Online Change is therefore no longer possible!"

Since the last download you have linked a library containing functions which are not yet referenced in the runtime system. For this reason you have to download the complete project.

1400

"Unknown Pragma '<Name>' is ignored!"

Appendix J: - Compiler Errors and Warnings

This pragma is not supported by the compiler. See keyword ‘pragma’ for supported directives.

1401

"The struct '<name>' does not contain any elements."

The structure does not contain any elements, but variables of this type allocate 1 Byte of memory.

1410

"'RETAIN' and 'PERSISTENT' do not have any effect in functions"

Remanent variables which are defined locally in functions are handled like normal local variables.

1411

"Variable '<name>' in the variable configuration isn't updated in any task"

The top level instance of the variable is not referenced by a call in any task. Thus it will not be copied from the process image.

Example:

Variable Configuration:

VAR_CONFIG

plc_prg.aprg.ainst.in AT %IB0 : INT; END_VAR

plc_prg:

index := INDEXOF(aprg);

The program aprg is referenced but not called. Thus plc_prg.aprg.ainst.in never will get the actual value of %IB0.

1412

"Unexpected token '<Name>' in pragma {pragma name}"

You are using a pragma which is not written correctly resp. which cannot be used at this location. See keyword 'pragma' in the CoDeSys Online Help or Users Guide for getting help for a correction.

1413

"'<Name>' is not a valid key for list '<Name>'. The key will be ignored"

In the pragma a nonexistent parameter list is specified. Check the list name resp. have a look in the Parameter Manager for the currently available lists.

1500

"Expression contains no assignment. No code was generated."

The result of this expression is not used. For this reason there is no code generated for the whole expression.

1501

"String constant passed as 'VAR_IN_OUT': '<Name>' must not be overwritten!"

The constant may not be written within the POU, because there no size check is possible.

1502

"Variable '<Name>' has the same name as a POU. The POU will not be called!"

A variable is used, which has the same name like a POU. Example:

PROGRAM a

...

Appendix J: - Compiler Errors and Warnings

VAR_GLOBAL a: INT;

END_VAR

...

a; (* Not POU a is called but variable a is loaded. *)

1503

"The POU ‘<name>’ has no outputs. Box result is set to 'TRUE'."

The Output pin of a POU which has no outputs, is connected in FBD or KOP. The assignment automatically gets the value TRUE.

1504

"’<name>’ (‘<number>’): Statement may not be executed due to the evaluation of the logical expression"

Eventually not all branches of the logic expression will be executed. Example:

IF a AND funct(TRUE) THEN ....

If a has is FALSE then funct will not be called.

1505

"Side effect in '<Name>'! Branch is probably not executed !"

The first input of the POU is FALSE, for this reason the side branch, which may come in at the second input, will not be executed.

1506

"Variable '<name>' has the same name as a local action. The action will not be called!"

Rename the variable or the action.

1507

"Instance '<name>' has the same name as a function. The instance will not be called."

You call in ST an instance which has the same name like a function. The function will be called ! Use different names.

1550

"Multiple calls of the POU '<Name>' in one network may lead to undesired side effects"

Check, whether the multiple call of this POU is really necessary. By a multiple call unwanted value overstrikes may occur.

1600

"Open DB unclear (generated code may be erroneous)."

The original Siemens program does not tell, which POU is opened.

1700

"Input not connected."

An input box is used in CFC which has no assignment. For this no code will be generated.

Appendix J: - Compiler Errors and Warnings

1750

"Step '<Name>': the minimal time is greater than the maximal time!"

Open dialog 'Step attributes' for this step and correct the time definitions.

1800

"<name>(element #<element number>): Invalid watchexpression '<name>'"

The visualization element contains an expression which cannot be monitored. Check variable name and placeholder replacements.

1801

"'<name> (number): No Input on Expression '<name>' possible"

In the configuration of the visualization object at field input a composed expression is used. Replace this by a single variable.

1802

"<Visualization object>(Element number): Bitmap '<name>' was not found"

Make sure, that an external bitmap-file is available in that path which is defined in the visualization configuration dialog.

1803

"'<name>'('<number>'): "The print action would not supported for weband target visualization"

A print action is assigned to an alarm configured in the visualization. This will not be regarded in the Webor Target-Visualization.

1804

"'<name>'('<number>'): The font '<name>' is not supported by the target."

In the visualization you are using a font, which is not supported by the target system. See in the target settings, category 'Visualization' for the supported fonts.

1805

"'<name>'('<number>'): 'Store trend data in PLC' should be set."

You are using a visualization element for storing trend data. This however will not be regarded on the PLC, because option 'Store trend data' is not activated in the target settings, category Visualization.

1806

"'<name>'('<number>'): The target setting 'Alarm handling in the PLC' should be set."

You are using an element for alarm visualization. This however will not be regarded on the PLC because option 'Alarm handling in the PLC' is not activated in the target settings, category 'Visualization'.

1900

"POU '<name>' (main routine) is not available in the library"

The Start-POU (e.g. PLC_PRG) will not be available, when the project is used as library.

1901

"Access Variables and Variable Configurations are not saved in a library!"

Access variables and variable configuration are not stored in the library.