TwinCAT PLC Control: Build Errors

Compiler Errors

Here you will find the error messages that the parser displays (italics) and possible causes. 

Warnings

Number Error Message Possible Cause
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! 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 with name <name> does not contain any elements. But Variables of this type will use 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 this Online Help 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 
... 
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 '%s' 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.

1700 Input box without assignment. An input box is used in CFC which has no assignment. For this no code will be generated.
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 '%s' 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 web- and target visualization.

A print action is assigned to an alarm configured in the visualization. This will not be regarded in the Web- or 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'.

1807

<name> (<number>): No message window for alarms for target visualization

Regard that action "message" is not supported for the Target-Visualization!

1850

Input variable at %IB<number> is used in task '<name>' but updated in another task

Please check which tasks are using this variable and whether the current programming is not causing undesirable effects. The update of the variable value usually is done in the task with the highest priority.

1851

Output variable at %IQ<number> is used in task '<name>' but updated in another task

Please check which tasks are using this variable and whether the current programming is not causing undesirable effects. The update of the variable value usually is done in the task with the highest priority.

1852

CanOpenMaster might not be called cyclically in event task '<name>'! Set modul parameter

UpdateTask!

Currently the CanOpen Master is called by the named event task. If you want to get it called cyclically, specify an appropriate task via parameter UpdateTask in the PLC Configuration in dialog 'Module

parameters'.

1853

A PDO (index: '<number>') might not be updated cyclically in event task '<name>'

Currently the named PDO is controlled via the named event task. But if you want to get it called cyclically, you must assign an appropriate task to the PDO by shifting IO-references to this task.

1900 POU '<name>' (main routine) is not available in the library The Start-POU (z.B. 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.
1902 '<name>': is no Library for the current machine type! The .obj file of the lib was generated for another device.
1903 <name>: is no valid Library The file does not have the format requested for the actual target.
1904

The constant '<name>' hides a constant of the same name in a library

In your project you have defined a constant which has the same name like one which is defined in a linked library. The library variable will be overwritten !

1970

Parameter manager: List '<name>' , Column '<name>', Value '<name>' could not be imported!

Check the Import-file *.prm for entries which do not match the current configuration (standard values resp. XML-description file) of the Parameter Manager.

1980

Global network variables '<name>' '<name>': simultaneous reading and writing may result in loss of data!

In the configuration of the network variables list (Select list in the Resources tab and open dialog 'Global variables list' via command 'Properties' in the context menu) options 'Read' and 'Write' are activated. Regard that this might result in data losses during communication.

1990

No 'VAR_CONFIG' for '<name>'

 

For this variable there is no address configuration available in the Variable_Configuration (VAR_CONFIG). Open window Variable_Configuration in the Resources tab and there insert the appropriate configuration (Command 'Insert 'All instance paths').

2500

Task '<task name>': no cycle time specified for cyclic task

In the Task configuration a cyclic task has been created, for which no cycle time has been defined. Enter an appropriate time span in dialog 'Taskattributes' at "Interval".

Compiler Errors

Number Error Message Possible Cause
3100 Code too large. Maximum size: '<number>' Byte (<number>K) The maximum program size is exceeded. Reduce project size.
3101 Total data too large. Maximum size: '<number>' Byte (<number>K) Memory is exceeded. Reduce data usage of the application.
3110 Error in library file '<name>'. The .hex file is not in INTEL Hex format.
3111 Library '<name>' is too large. Maximum size: 64K The .hex file exceeds the set maximum size.
3112 Nonrelocatable instruction in library. The .hex file contains a nonrelocatable instruction. The library code cannot be linked.
3113 Library code overwrites function tables. The ranges for code and function tables are overlapping.
3114 Library uses more than one segment. The tables and the code in the .hex file use more than one segment.
3115 Unable to assign constant to VAR_IN_OUT. Incompatible data types. The internal pointer format for string constants cannot get converted to the internal pointer format of VAR_IN_OUT, because the data are set "near" but the string constants are set " huge" or "far". If possible change these target settings.
3116

Function tables overwrite library code or a segment boundary.

Code 166x: The external library cannot be used with the current target settings. These must be adapted resp. the library must be rebuilt with appropriate settings.

3117

<Name> (<Zahl>): Expression too complex. No more registers available

The named expression is to complex to be handled by the available registers. Please try to reduce the expression by using interim variables.

3120 Current code-segment exceeds 64K. The currently generated code is bigger than 64K. Eventually to much initializing code is created.
3121 POU too large." A POU may not exceed the size of 64K. A POU may not exceed the size of 64K.
3122 Initialisation too large. Maximum size: 64K The initialization code for a function or a structure POU may not exceed 64K.
3123

Data segment too large: segment '<Number>%s', size <size> bytes (maximum <number> bytes)

Please contact your manufacturer.

3124

String-constant too large: <Number> characters (Maximum 253 characters)

The given constant must be reduced in number of characters.

3130 User-Stack too small: '<number>' DWORD needed, '<number>' DWORD available. The nesting depth of the POU calls is to big. Enter a higher stack size in the target settings or compile build project without option ‚Debug’ (can be set in dialog ‘Project’ ‘Options’ ‘Build’).
3131 User-Stack too small: '<number>' WORD needed, '<number>' WORD available. Please contact the PLC manufacturer.
3132 System-Stack too small: '<number>' WORD needed, '<number>' WORD available. Please contact the PLC manufacturer.
3150 Parameter <number> of function '<name>': Cannot pass the result of a IEC-function as string parameter to a C-function. Use a intermediate variable, to which the result of the IEC function is assigned.
3160 Can't open library file '<name>'. A library <name> is included in the library manager for this project, but the library file does not exist at the given path.
3161 Library '<name>' contains no codesegment A .obj file of a library at least must contain one C function. Insert a dummy function in the .obj file, which is not defined in the .lib file.
3162 Could not resolve reference in Library '<name>'(Symbol '<name>', Class '<name>', Type '<name>') The .obj file contains a not resolvable reference to another symbol. Please check the settings of the C-Compiler.
3163 Unknown reference type in Library '<name>' (Symbol '<name>' , Class '<name>' , Type '<name>') The .obj file contains a reference type, which is not resolvable by the code generator. Please check -the settings of the C-Compiler.
3200 "%s (%d): Boolean expression to complex The temporary memory of the target system is insufficient for the size of the expression. Divide up the expression into several partial expressions thereby using assignments to intermediate variables.
3201 <name> (<network>): A network must not result in more than 512 bytes of code Internal jumps can not be resolved. Activate option "Use 16 bit Sprungoffsets" in the 68k target settings.
3202 Stack overrun with nested string/array/structure function calls A nested function call CONCAT(x, f(i)) is used. This can lead to data loss. Divide up the call into two expressions.
3203 Expression too complex (too many used address registers). Divide up the assignment in several expressions.
3204 A jump exceeds 32k Bytes Jump distances may not be bigger than 32767 bytes.
3205 Internal Error: Too many constant strings" In a POU there at the most 3000 string constants may be used. In a POU there at the most 3000 string constants may be used.
3206 Function block data exceeds maximal size A function block may produce maximum 32767 Bytes of code.
3207 Array optimization The optimization of the array accesses failed because during index calculation a function has been called.
3208 Conversion not implemented yet A conversion function is used, which is not implemented for the actual code generator.
3209 Operator not implemented A operator is used, which is not implemented for this data type and the actual code generator. MIN(string1,string2).
3210 Function '<name>' not found A function is called, which is not available in the project.
3211 Max string usage exceeded A variable of type string can be used in one expression 10 times at the most.
3212

Wrong library order at POU <POU name>

The order of libraries for this POU does not match with that in the cslib.hex file. Correct the order accordingly. (only for 68K targets, if the checking option is activated in the target file.)

3250

Real not supported for 8 Bit Controller

The target is currently not supported.

3251

date of day types are not supported for 8 Bit Controller

The target is currently not supported.

3252

size of stack exceeds <number> bytes

The target is currently not supported.

3253

Could not find hex file: '<name>'

The target is currently not supported.

3254

Call to external library function could not be resolved.

The target is currently not supported.

3400 An error occurred during import of Access variables The .exp file contains an incorrect access variables section.
3401 An error occurred during import of variable configuration The .exp file contains an incorrect configuration variables section.
3402 An error occurred during import of global variables The .exp file contains an incorrect global variables section.
3403 Could not import <name> The section for object <name> in the .exp file is not correct.
3404 An error occurred during import of task configuration The section for the task configuration the .exp file is not correct.
3405 An error occurred during import of PLC configuration The section for the PLC configuration in the .exp file is not correct.
3406 Two steps with the name '<name'. Second step not imported. The section for the SFC POU in the .exp file contains two steps with equal names. Rename one of the steps in the export file.
3407 Predecessor step '<name>' not found The step <name> is missing in the .exp file.
3408 Successor step '<name>' not found The step <name> is missing in the .exp file.
3409 No successional transition for step '<´name>' In the .exp file a transition is missing, which requires step <name> as preceeding step.
3410 No successional step for transition '<name>' In the .exp file a step is missing which requires the transition <name> as preceeding condition.
3411 Step '<name>' not reachable from initial step In the .exp file the connection between step <name> and the initial step is missing.
3412

Macro '<name>' not imported

Check the export file.

3413

Error during import of the CAMs.

You have imported an export file (*.exp) which contains erroneous information on a CAM. Check the export file.

3414

Error during import of the CNC program list

You have imported an export file (*.exp) which contains erroneous information on a CNC program. Check the export file.

3415

Error during import of the Alarm configuration

 

You have imported an export file (*.exp) which contains erroneous information on the Alarm Configuration. Check the export file.

3450 PDO'<PDO-name>': Missing COB-Id! Click on the button ‚Properties’ in the PLC configuration dialog for the module and enter a COB ID for the PDO <PDO Name>.
3451 Error during load: EDS-File '<name>' could not be found, but is referenced in hardware configuration! Eventually the device file needed for the CAN configuration is not in the correct directory. Check the directory setting for configuration files in ‚Project' 'Options' 'Directories'.
3452 The module '<name>' couldn't be created! The device file for module <name> does not fit to the current configuration. Eventually it has been modified since the configuration has been set up or it is corrupted.
3453 The channel '<name>' couldn't be created! The device file for channel <name> does not fit to the current configuration. Eventually it has been modified since the configuration has been set up or it is corrupted.
3454 The address '<name>' points to an used memory! Option 'Check for overlapping addresses' is activated in the dialog ‚Settings’ of the PLC configuration and an overlap has been detected. Regard, that the area check is based on the size which results of the data types of the modules, the size which is given by the entry ‚size’ in the configuration file.
3455 Error during load: GSD-File '<name>' could not be found, but is referenced in hardware configuration! Eventually the device file required by the Profibus configuration is not in the correct directory. . Check the directory setting for configuration files in ‚Project' 'Options' 'Directories'.
3456 The profibus device '<name>' couldn't be created! The device file for module <name> does not fit to the current configuration. Eventually it has been modified since the configuration has been set up or it is corrupted.
3457 Error in module description! Please check the device file of this module.
3458

The PLC-Configuration couldn't be created! Check the configuration files.

Check if all required configuration and device files are available in the correct path (see defined compile directory in 'Project' 'Options' /Directories)

3460

3S_CanDrv.lib has the wrong version.

Make sure, that the 3S_CanDrv.lib which is included in the project is up to date.

3461

3S_CanOpenMaster.lib has the wrong version.

Make sure, that the 3S_CanOpenMaster.lib which is included in the project is up to date.

3462

3S_CanOpenDevice.lib has the wrong version.

Make sure, that the 3S_CanOpenDevice.lib which is included in the project is up to date.

3463

3S_CanOpenManager.lib has the wrong version.

Make sure, that the 3S_CanOpenManager.lib which is included in the project is up to date.

3464

3S_CanNetVar.lib has the wrong version.

Make sure, that the 3S_CanNetVar.lib which is included in the project, is up to date.

3465

CanDevice: Sub indices have to be numerated sequentially

In parameter lists used by the CanDevice the subindices must be numbered sequentially and without interruption. Check the corresponding list in the Parameter Manager.

3466

CAN network variables: No CAN controller found in the PLC configuration

There are network variables configured for a CAN network (Resources, Global Variables), but in the PLC Configuration there is no CAN Controller available.

3468

CanDevice: Update task not available in the task configuration.

The update task (used for calling the CANdevice), which is defined in the Base Settings dialog of the CANdevice in the PLC Configuration, must be configured in the Task Configuration of the project.

3469

The CanOpenMaster can not be called. Please assign a task manually.

Assign a task, which should call the Master, via parameter UpdateTask in the Module parameters dialog in the PLC Configuration.

3470

Invalid name in parameter UpdateTask

 

Open the CanMasters Module parameter dialog in the PLC Configuration. Check parameter UpdateTask. The specified task must be available in the project. If you cannot set an appropriate task here, the device file must be checked for the corresponding value definitions for UpdateTask.

3500 No 'VAR_CONFIG' for '<name>' Insert a declaration for this variable in the global variable list which contains the 'Variable_Configuration'.
3501 No address in 'VAR_CONFIG' for '<name>'. Assign an address to this variable in the global variable list which contains the 'Variable_Configuration'.
3502 Wrong data type for '<name>' in 'VAR_CONFIG In the global variables list which contains the ‚Variable_Configuration’ the variable is declared with a different data type than in the POU.
3503 Wrong data type for '<name>' in 'VAR_CONFIG' In the global variables list which contains the ‚Variable_Configuration’ the variable is declared with a different address than in the POU.
3504 Initial values are not supported for 'VAR_CONFIG A variable of the ‚Variable_Configuration’ is declared with address and initial value. But an initial value can only be defined for input variables without address assignment.
3505 '<name>’is no valid instance path The Variable_Configuration contains a nonexisting variable.
3506 Access path expected In the global variable list for Access Variables the access path for a variable is not correct. Correct: <Identifier>:'<Access path>':<Type> <Access mode>
3507 No address specification for 'VAR_ACCESS'-variables The global variable list for Access Variables contains an address assignment for a variable. This is not allowed. Valid variable definition: <Identifier>:'<Access path>':<Type> <Access mode>
3550 Duplicate definition of identifier '<name>' There are two tasks are defined with an identic same name. Rename one of them.
3551 The task '<name>' must contain at least one program call Insert a program call or delete task.
3552 Event variable '<name>' in task '%s' not defined There is an event variable set in the ‘Single’ field of the task properties dialog which is not declared globally in the project. Use another variable or define the variable globally.
3553 "Event variable '<name>' in task '%s' must be of type 'BOOL' Use a variable of type BOOL as event variable in the ‘Single’ field of the task properties dialog.
3554 Task entry '<name>' must be a program or global function block instance In the field ‚Program call’ a function or a not defined POU is entered. Enter a valid program name.
3555 The task entry '<name>' contains invalid parameters In the field ‚Append program call’ there are parameters used which do not comply with the declaration of the program POU.
3556

Tasks are not supported by the currently selected target

The currently defined task configuration cannot be used for the currently set target system. Change target or modify the task configuration correspondingly.

3557

Maximum number of Tasks ('<number>') exceeded

The currently defined number of tasks exceeds the maximum number allowed for the currently set target system. Change target or modify the task configuration correspondingly. Attention: Do not edit the XML description file of the task configuration!

3558

Priority of task '<name>' is out of valid range between '<lower limit>' and '<upper limit>'

The currently defined priority for the task is not valid for the currently set target system. Change target or modify the task configuration correspondingly.

3559

Task '<name>': Interval-Tasks are not supported by the current target

The current task configuration contains an interval task. This is not allowed by the currently set target system. Change target or modify the task configuration correspondingly.

3560

Task '<name>': free wheeling tasks are not supported by the current target

The current task configuration contains an free wheeling task. This is not allowed by the currently set target system. Change target or modify the task configuration correspondingly.

3561

Task '<name>': event tasks are not supported by the current target

The current task configuration contains event tasks which are not supported by the currently set target system. Change target or modify the task configuration correspondingly.

3562

Task '<name>': external event tasks are not supported by the current target

The current task configuration contains external event tasks which are not supported by the currently set target system. Change target or modify the task configuration correspondingly.

3563

The interval of task '<name>' is out of valid range between '<lower limit>' and '<upper limit>'

Change the interval value in the configuration dialog for the task.

3564

The external event '<name>' of task '<name>' is not supported by the current target

The currently set target system does not support the external event which is defined in the task configuration for this task. Change target or modify the task configuration correspondingly.

3565

Maximum number of event tasks ('<number>') exceeded

The currently set target system does not allow as many event tasks as are defined at the moment. Change target or modify the task configuration correspondingly.

3566

Maximum number of interval tasks ('<number>') exceeded

The currently set target system does not allow as many interval tasks as defined at the moment. Change target or modify the configuration correspondingly.

3567

Maximum number of free wheeling tasks ('<number>') exceeded

The currently set target system does not allow as many free wheeling tasks as defined at the moment. Change target or modify the configuration correspondingly.

3568

Maximum number of external interval tasks ('<number>') exceeded

The currently set target system does not allow as many external interval tasks as defined at the moment. Change target or modify the configuration correspondingly.

3569

POU '<name>' for system event '<name>' not defined

The POU which should be called by the named system event, as defined in the task configuration, is not available in the project. Modify the task configuration correspondingly or make sure that the POU is available in the project.

3570

The tasks '<name>' and '<name>' share the same priority

Modify the task configuration so that each task has a different priority.

3571

The library 'SysLibCallback' is not included in the project! System events can not be generated.

In order to create event tasks, the SysLibCallback.lib is needed. Link this library to the project in the library manager or modify the task configuration (task attributes) in that way that there is no task triggered by an event.

3575

Task <'name>': the cycle time has to be a multiple of <number> μs.

Correct the cycle time accordingly in the Taskattributes dialog for this task. The target system defines a base time and prescribes that the cycle time must be equal to or be a multiple of this base time.

3600 Implicit variables not found! Use command ‚Rebuild all’. If nevertheless you get the error message again please contact the PLC manufacturer.
3601 <name> is a reserved variable name The given variable is declared in the project, although it is reserved for the codegenerator. Rename the variable.
3610 '<name>' not supported The given feature is not supported by the current version of the programming system.
3611 The given compile directory '<name>' is invalid There is an invalid directory given in the ‚Project’ ‚Options’ ‚Directories’ for the Compile files.
3612 Maximum number of POUs (<number>) exceeded! Compile is aborted. Too many POUs and data types are used in the project. Modify the maximum number of POUs in the Target Settings / Memory Layout.
3613 Build canceled The compile process was cancelled by the user.
3614 Project must contain a POU named '<name>' (main routine) or a task configuration Create an init POU of type Program (e.g. PLC_PRG) or set up a task configuration.
3615 <name> (main routine) must be of type program A init POU (e.g. PLC_PRG) is used in the project which is not of type Program.
3616 Programs musn't be implemented in external libraries The project which should be saved as an external library contains a program. This will not be available, when the library will be used.
3617 Out of memory Increase the virtual memory capacity of your computer.
3618 BitAccess not supported in current code generator! The code generator for the currently set target system does not support bit access on variables.
3619

Object file '<name>' and library '<name>' have different versions!

Make sure that for the library there are available matching versions of *.lib and *.obj resp. *.hex files. These files must have the very same time stamp.

3620

The POU '<name>' must not be present inside a library

You want to save the project as a library of version 2.1. In this version a library may not contain a PLC_PRG object. Use a different POU name.

3621

"Cannot write compile file '<name>'"

 

Probably in the path which is specified for the compile file there is already a file of the same name, which is "read only". Remove that file resp. change the access rights.

3622

"The symbol file '<name>' could not be created"

 

Probably in the path which is specified for the symbol file (usually project directory) there is already a file of the same name, which is "read only". Remove that file resp. change the access rights.

3623

"Cannot write boot project file '<name>'"

 

Probably in the path which is specified for the symbol file (target specific) there is already a file of the same name, which is "read only". Remove that file resp. change the access rights.

3624

"Target setting <targetsetting1>=<set value> not compatible with <targetsetting2>=<set value>"

Check and correct these settings in the Targetsettings dialogs (Resources tab). If the settings are not visible resp. editable there, please contact the PLC Manufacturer.

3700 POU with name ‘<name>' is already in library '<name>' A POU name is used in the project, which is already used for a library POU. Rename the POU.
3701 Name used in interface is not identical with POU Name Use command ‘Project’ ‘Rename object’ to rename the POU in the object organizer, or change the name of the POU in the declaration window. There the POU name has to be placed next to one of the keywords PROGRAM, FUNCTION or FUNCTIONBLOCK.
3702 Overflow of identifier list Maximum 100 identifiers can be entered in one variable declaration.
3703 Duplicate definition of identifier '<name>' Take care that there is only one identifier with the given name in the declaration part of the POU.
3704 data recursion:
<POU 0> -> <POU 1> -> .. -> <POU 0>
A FB instance was used, which needs itself.
3705

<Name>: VAR_IN_OUT in Top-Level-POU not allowed, if there is no Task-Configuration

Create a task configuration or make sure that there are no VAR_IN_OUT variables used in PLC_PRG.

3720

Address expected after 'AT'

Add a valid address after the keyword AT or modify the keyword.

3721

Only 'VAR' and 'VAR_GLOBAL' can be located to addresses

Put the declaration to a VAR or VAR_GLOBAL declaration area.

3722

Only 'BOOL' variables allowed on bit addresses

Modify the address or modify the type of the variable to which the address is assigned.

3726

Constants can not be laid on direct addresses

Modify the address assignment correspondingly.

3727

No array declaration allowed on this address

Modify the address assignment correspondingly.

3728

Invalid address: '<address>'

This address is not supported by the PLC configuration. Check PLC configuration resp. modify address.

3729 Invalid type '<name>' at address: '<name>' The type of this variable cannot be placed on the given address. Example: For a target system working with ‘alignment 2’ the following declaration is not valid: var1 AT %IB1:WORD;
3740 Invalid type: '<name>' An invalid data type is used in a variable declaration.
3741 Expecting type specification A keyword or an operator is used instead of a valid type identifier.
3742 Enumeration value expected In the definition of the enumeration type an identifier is missing after the opening bracket or after a comma between the brackets.
3743 Integer number expected Enumerations can only be initialized with numbers of type INT.
3744 Enum constant '<name>' already defined. Check if you have followed the following rules for the definition of enumeration values:
- Within one enum definition all values have to be unique.
- Within all global enum definitions all values have to be unique.
- Within all local enum definitions all values have to be unique
3745 Subranges are only allowed on Integers! Subrange types can only be defined resting on integer data types.
3746 Subrange '<name>' is not compatible with Type '<name>' One of the limits set for the range of the subrange type is out of the range which is valid for the base type.
3747 unknown string length: '<name>' There is a not valid constant used for the definition of the string length.
3748 More than three dimensions are not allowed for arrays More than the allowed three dimensions are given in the definition of an array. If applicable use an ARRAY OF ARRAY.
3749 lower bound '<name>' not defined There is a not defined constant used to define the lower limit for a subrange or array type.
3750 upper bound '<name>' not defined There is a not defined constant used to define the upper limit for a subrange or array type.
3751

Invalid string length '<number of characters>'

The here defined string length exceeds the maximum value which is defined for the currently set target system.

3752

More than 9 dimensions are not allowed for nested arrays

An array can be 1- 2- or 3-dimensional. The number of dimensions reached by nesting of arrays (e.g "arr: ARRAY [0..2,0..2,0..2] OF ARRAY [0..2,0..2,0..2] OF ARRAY [0..2,0..2,0..2, 0..2] OF DINT" maximum may be 9 and is exceeded in the current error case. Reduce appropriately to max. 9 dimensions.

3760 Error in inital value Use an initial value which corresponds to the type definition. To change the declaration you can use the declaration dialog for variables (Shift/F2 or 'Edit''Autodeclare').
3761 'VAR_IN_OUT' variables must not have an inital value. Remove the initialization at the declaration of the VAR_IN_OUT variable.
3780 VAR, VAR_INPUT, VAR_OUTPUT or VAR_IN_OUT expected The first line following the name of a POU must contain one of these keywords.
3781 "'END_VAR' or identifier expected Enter a valid identifier of a END_VAR at the beginning of the given line in the declaration window.
3782 Unexpected end In the declaration editor: Add keyword END_VAR at the end of the declaration part. In the texteditor of the programming part: Add an instruction which terminates the last instruction sequence (e.g. END_IF).
3783 END_STRUCT' or identifier expected Ensure that the type declaration is terminated correctly.
3784

The current target doesn't support attribute <attribute name>

The target system does not support this type of variables (e.g. RETAIN, PERSISTENT)

3800 The global variables need too much memory. Increase the available memory in the project options. Increase the number of segments given in the settings in dialog ‚Project’ ‚Options’ ‚Build’.
3801 The variable '<name>' is too large (<Size> Byte) The variable uses a type which is bigger than 1 data segment. The segment size is a target specific parameter and can be modified in the target settings/memory layout. If you do not find this in the current target settings, please contact your PLC manufacturer.
3802 Out of retain memory. Variable '<name>', <number> bytes. The memory space available for Retain variables is exhausted. The size of the memory area can be set target-specific in the target settings /memory layout. If you do not find the settings field in the dialog, please contact your PLC manufacturer. (Please regard: If retain variables are used in an function block instance, the complete instance POU will be stored in the retain memory area !)
3803 Out of global data memory. Variable '<name>', ‚<number>’ bytes. The memory space available for global variables is exhausted. The size of the memory area can be set target-specific in the target settings /memory layout. If you do not find the settings field in the dialog, please contact your PLC manufacturer.
3820 "'VAR_OUTPUT' and 'VAR_IN_OUT' not allowed in functions In a function no output or in_output variables may be defined.
3821 At least one input required for functions Add at least on input parameter for the function.
3840 Unknown global variable '<name>'! In the POU a VAR_EXTERNAL variable is used, for which no global variable declared.
3841 Declaration of '<name>' do not match global declaration! The type given in the declaration of the VAR_EXTERNAL variable is not the same as that in the global declaration.
3850

Declaration of an unpacked struct '<name>' inside a packed struct '<name>' is not allowed!

This structure definition leads to misalignment in the memory. Modify the definition appropriately.

3900 Multiple underlines in indentifier Remove multiple underlines in the identifier name.
3901 At most 4 numerical fields allowed in addresses There is a direct assignment to an address which has more than four levels. (e.g. %QB0.1.1.0.1).
3902 Keywords must be uppercase Use capital letters for the keyword or activate option ‚Autoformat’ in ‚Project’ ‚Options’.
3903 Invalid duration constant The notation of the constant does not comply with the IEC61131-3 format.
3904 Overflow in duration constant. The value used for the time constant cannot be represented in the internal format. The maximum value which is representable is t#49d17h2m47s295ms
3905 Invalid date constant The notation of the constant dies not comply with the IEC61131-3 format.
3906 Invalid time of day constant The notation of the constant dies not comply with the IEC61131-3 format.
3907 Invalid date and time constant The notation of the constant dies not comply with the IEC61131-3 format.
3908 Invalid string constant The string constant contains an invalid character.
4000 Identifier expected Enter a valid identifier at this position.
4001 Variable '<name>' not declared Declare variable local or global.
4010 Type mismatch: Cannot convert '<name>' to '<name>'. Check what data type the operator expects (Browse Online Help for name of operator) and change the type of the variable which has caused the error, or select another variable.
4011 Type mismatch in parameter '<name>' of '<name>': Cannot convert '<name>' to '<name>'. The data type of the actual parameter cannot be automatically converted to that of the formal parameter. Use a type conversion or use another variable type.
4012 Type mismatch in parameter '<name>' of '<name>': Cannot convert '<name>' to '<name>'. A value with the invalid type <Typ2> is assigned to the input variable '<name>'. Replace the variable or constant to one of type <Typ1> or use a type conversion respectively a constant with type-prefix.
4013 Type mismatch in output '<name>' of '<name>': Cannot convert '<name>' to '<name>'. A value with the invalid type <Typ2> is assigned to the output variable '<name>'. Replace the variable or constant to one of type <Typ1> or use a type conversion respectively a constant with type-prefix.
4014 Typed literal: Cannot convert '<name>' to '<name> The type of the constant is not compatible with the type of the prefix. Example: SINT#255
4015 Data type ‘<name>' illegal for direct bit access Direct bit addressing is only allowed for Integer- and Bitstring data types. You are using a variable var1 of type REAL/LREAL or a constant in bit access <var1>.<bit>.
4016 Bit index '<number>' out of range for variable of type '<name> You are trying to access a bit which is not defined for the data type of the variable.
4017 'MOD' is not defined for 'REAL The operator MOD can only be used for integer and bitstring data types.
4020 Variable with write access or direct address required for 'ST', 'STN', 'S', 'R' Replace the first operand by a variable with write access.
4021 No write access to variable '%s' allowed Replace the variable by a variable with write access.
4022 Operand expected Add an operand behind the command.
4023 Number expected after '+' or '-' Enter a digit.
4024 <operator 0> or <operator 1> or ... expected before '<name>' Enter a valid operand at the named position.
4025 ':=' or '=>' expected before '<name>' Enter one of the both operators at the named position.
4026 'BITADR' expects a bit address or a variable on a bit address Use a valid bit address (e.g. %IX0.1).
4027 Integer number or symbolic constant expected Enter a integer number or the identifier of a valid constant.
4028 'INI' operator needs function block instance or data unit type instance Check the data type of the variable, for which the INI operator is used.
4029 Nested calls of the same function are not possible. At not reentrant target systems and in simulation mode a function call may not contain a call of itself as a parameter. Example: fun1(a,fun1(b,c,d),e); Use a intermediate table.
4030 Expressions and constants are not allowed as operands of 'ADR' Replace the constant or the expression by a variable or a direct address.
4031 'ADR' is not allowed on bits! Use 'BITADR' instead. Use BITADR. Please note: The BITADR function does not return a physical memory address
4032 ’<number>’ operands are too few for '<name>'. At least ‘<number>’ are needed Check how many operands the named operator requires and add the missing operands.
4033 ’<number>’ operands are too many for '<name>'. At least ‘<number>’ are needed Check how many operands the named operator requires and remove the surplus operands.
4034 Division by 0 You are using a division by 0 in a constant expression. If you want to provocate a runtime error, use – if applicable - a variable with the value 0.
4035 ADR must not be applied on 'VAR CONSTANT' if 'replaced constants' is activated An address access on constants for which the direct values are used, is not possible. If applicable, deactivate the option ‚Replace Constants’ in ‚Project’ ‚Options’ ‚Build’.
4040 Label '<name>' is not defined Define a label with the name <LabelName> or change the name <LabelName> to that of a defined label.
4041 Duplicate definition of label '<name>' The label '<name>' is multiple defined in the POU. Rename the label or remove one of the definitions.
4042 No more than %d labels in sequence are allowed The number of jump labels is limited to '<Anzahl>'. Insert a dummy instruction.
4043 Format of label invalid. A label must be a name optionally followed by a colon. The label name is not valid or the colon is missing in the definition.
4050 POU '%s' is not defined Define a POU with the name '<name>' using the command ‘Project’ ‘Add Object’ or change '<name>' to the name of a defined POU.
4051 '%s' is no function Use instead of <name> a function name which is defined in the project or in the libraries.
4052 '%s' must be a declared instance of FB '%s' Use an instance of data type '<name>' which is defined in the project or change the type of <Instance name> to '<name>' .
4053 '%s' is no valid box or operator Replace '<name>' by the name of a POU or an operator defined in the project.
4054 POU name expected as parameter of 'INDEXOF' The given parameter is not a valid POU name.
4060 'VAR_IN_OUT' parameter '%s' of '%s' needs variable with write access as input. To VAR_IN_OUT parameters variables with write access have to be handed over, because a VAR_IN_OUT can be modified within the POU.
4061 'VAR_IN_OUT' parameter '%s' of '%s' must be used. A VAR_IN_OUT parameter must get handed over a variable with write access, because a VAR_IN_OUT can be modified within the POU.
4062 No external access to 'VAR_IN_OUT' parameter '%s' of '%s'. VAR_IN_OUT Parameter only may be written or read within the POU, because they are handed over by reference.
4063 'VAR_IN_OUT' parameter '%s' of '%s' must not be used with bit addresses. A bit address is not a valid physical address. Hand over a variable or a direct non-bit address.
4064 'VAR_IN_OUT' must not be overwritten in local action call! Delete the parameters set for the VAR_IN_OUT variable in the local action call.
4070 The POU contains a too complex expression Decrease nesting depth by dividing up the expression into several expressions. Use intermediate variables for this purpose.
4071 Network too complex Divide up the network into several networks.
4072

Inconsistent use of an action identifier in FB type ('<name>') and instance ('<name>').

 

You have defined two actions of a function block fb: e.g. a1 and a2, but in the call of one of the actions in the FBD you are using a type (string within the box, e.g. fb.a1 different to that used in the instancename (e.g. inst.a2, above box). Correct the name correspondingly into the name of the desired action.

4100 '^' needs a pointer type You are trying to dereference a variable which is not declared as a pointer.
4110 '[<index>]' needs array variable [<index>] is used for a variable which is not declared as an array with ARRAY OF.
4111 Index expression of an array must be of type 'INT' Use an expression of the correct type or a type conversion.
4112 Too many indexes for array Check the number of indices (1, 2, oder 3), for which the array is declared and remove the surplus.
4113 Too few indexes for array Check the number of indices (1, 2, oder 3), for which the array is declared and add the missing ones.
4114 One of the constant indizes is not within the array range Make sure that the used indices are within the bounds of the array.
4120 '.' needs structure variable" The identifier on the left hand of the dot must be a variable of type STRUCT or FUNCTION_BLOCK or the name of a FUNCTION or a PROGRAM.
4121 '<name>' is not a component of <object name> The component '<name>' is not included in the definition of the object <object name>.
4122 '%s' is not an input variable of the called function block Check the input variables of the called function block and change ‘<name>' to one of these.
4200 'LD' expected Insert at least one LD instruction after the jump label in the IL editor.
4201 IL Operator expected Each IL instruction must start with an operator or a jump label.
4202 Unexpected end of text in brackets Insert a closing bracket after the text.
4203 <name> in brackets not allowed The operator <name> is not valid in a IL bracket expression. (not valid are: 'JMP', 'RET', 'CAL', 'LDN', 'LD', 'TIME')
4204 Closing bracket with no corresponding opening bracket Insert an opening bracket or remove the closing one.
4205 No comma allowed after ')' Remove comma after closing bracket.
4206 Label in brackets not allowed Shift jump label so that it is outside of the brackets.
4207 'N' modifier requires operand of type 'BOOL', 'BYTE', 'WORD' or 'DWORD' The N modifier requires a data type, for which a boolean negation can be executed.
4208 Conditional Operator requires type 'BOOL' Make sure that the expression gives out a boolean result or use a type conversion.
4209 Function name not allowed here Replace the function call by a variable or a constant.
4210 'CAL', 'CALC' and 'CALN' require a function block instance as operand Declare an instance of the function block which you want to call.
4211 Comments are only allowed at the end of line in IL Shift the comment to the end of the line or to an extra line.
4212 Accumulator is invalid before conditional statement The accu is not defined. This happens if an instruction is preceeding which does not submit a result (e.g. 'CAL').
4213 'S' and 'R' require 'BOOL' operand Use a boolean variable at this place.
4250 Another 'ST' statement or end of POU expected The line does not start with a valid ST instruction.
4251 Too many parameters in function '%s' There are more parameters given than are declared in the definition of the function.
4252 Too few parameters in function '%s' There are less parameters given than are declared in the definition of the function.
4253 'IF' or 'ELSIF' require 'BOOL' expression as condition Make sure that the condition for IF or ELSIF is a boolean expression.
4254 'WHILE' requires 'BOOL' expression as condition Make sure that the condition following the ‘WHILE’ is a boolean expression.
4255 'UNTIL' requires 'BOOL' expression as condition Make sure that the condition following the ‘UNTIL’ is a boolean expression.
4256 'NOT' requires 'BOOL' operand Make sure that the condition following the ‘NOT’ is a boolean expression.
4257 Variable of 'FOR' statement must be of type 'INT' Make sure that the counter variable is of an integer or bitstring data type (e.g. DINT, DWORD).
4258 Expression in 'FOR' statement is no variable with write access Replace the counter variable by a variable with write access.
4259 Start value in 'FOR' statement is no variable with write access The start value in the ‚FOR' instruction must be compatible to the type of the counter variable.
4260 End value of 'FOR' statement must be of type 'INT' The end value in the ‚FOR' instruction must be compatible to the type of the counter variable.
4261 Increment value of 'FOR' statement must be of type 'INT' The incremental value in the ‚FOR' instruction must be compatible to the type of the counter variable.
4262 'EXIT' outside a loop Use 'EXIT' only within 'FOR', 'WHILE' or 'UNTIL' instructions.
4263 Expecting Number, 'ELSE' or 'END_CASE' Within a ‘CASE' expression you only can use a number or a 'ELSE' instruction or the ending instruction 'END_CASE'.
4264 'CASE' requires selector of an integer type Make sure that the selector is of an integer or bitstring data type (e.g. DINT, DWORD).
4265 Number expected after ',' In the enumeration of the CASE selectors there must be inserted a further selector after a comma.
4266 At least one statement is required Insert an instruction, at least a semicolon.
4267 Function block call requires function block instance The identifier in the functionblock call is no instance. Declare an instance of the desired functionblock or use the name of an already defined instance.
4268 Expression expected Insert an impression here.
4269 'END_CASE' expected after 'ELSE'-branch Terminate the 'CASE' instruction after the 'ELSE' part with an 'END_CASE'.
4270 'CASE' constant '%ld' already used A 'CASE' selector may only be used once within a ‘CASE' instruction.
4271 The lower border of the range is greater than the upper border. Modify the area bounds for the selectors so that the lower border is not highte than the upper border.
4272 Exptecting parameter '%s' at place %d in call of '%s'! You can edit a function call in that way, that also the parameter names are contained, not only the parameter values. But nevertheless the position (sequence) of the parameters must be the same as in the function definition.
4273 Parts of the 'CASE'-Range '%ld..%ld' already used in Range '%ld..%ld'  Make sure that the areas for the selectors which are used in the CASE instruction, don’t overlap.
4274 Multiple 'ELSE' branch in 'CASE' statement A CASE instruction may not contain more than one ‚ELSE' instruction.
4300 Jump requires 'BOOL' as input type Make sure that the input for the jump respectively the RETURN instruction is a boolean expression.
4301 POU '%s' need exactly %d inputs The number of inputs does not correspond to the number of VAR_INPUT and VAR_IN_OUT variables which is given in the POU definition.
4302 POU '%s' need exactly %d outputs The number of outputs does not correspond to the number of VAR_OUTPUT variables which is given in the POU definition.
4303 '%s' is no operator Replace '<name>' by a valid operator.
4320 Non-boolean expression '<name>' used with contact The switch signal for a contact must be a boolean expression.
4321 Non-boolean expression '<name>' used with coil The output variable of a coil must be of type BOOL.
4330 Expression expected at input 'EN' of the box '<name>'  Assign an input or an expression to the input EN of POU '<name>’.
4331 Expression expected at input '<number>' of the box '<name>'  The input <number> of the operator POU is not assigned.
4332 Expression expected at input '<name>' of the box '<name>' The input of the POU is of type VAR_IN_OUT and is not assigned.
4333 Identifier in jump expected The given jump mark is not a valid identifier.
4334 Expression expected at the input of jump Assign a boolean expression to the input of the jump. If this is TRUE, the jump will be executed.
4335 Expression expected at the input of the return Assign a boolean expression to the input of the RETURN instruction. If this is TRUE, the jump will be executed.
4336 Expression expected at the input of the output Assign a suitable expression to the output box.
4337 Identifier for input expected Insert a valid expression or identifier in the input box.
4338 Box '%s' has no inputs To none of the inputs of the operator POU '<name>' a valid expression is assigned.
4339 Typemismatch at output: Cannot convert '<name>' to '<name>'. The type of the expression in the output box is not compatible to that of the expression which should be assigned to it.
4340 Jump requires 'BOOL' as input type Make sure that the input for the jump is a boolean expression.
4341 Return requires 'BOOL' as input type  Make sure that the input for the RETURN instruction is a boolean expression.
4342 Expression expected at input 'EN' of the box '<name>' Assign a valid boolean expression to the EN input of the box.
4343 Values of Constants: ‘<name>’ Input '<name>' of box '<name>' is declared as VAR_INPUT CONSTANT. But to this POU box an expression has been assigned in the dialog 'Edit Parameters' which is not type compatible.
4344 'S' and 'R' require 'BOOL' operand Insert a valid boolean expression after the Set resp. Reset instruction.
4345 Invalid Type for parameter '<name>' of '<name>': Cannot convert '<type>' to '<type>'. An expression is assigned to input '<name>' of POU box '<name>' which is not type compatible.
4346 Not allowed to use a constant as an output"  You can only assign an output to a variable or a direct address with write access.
4347 'VAR_IN_OUT' parameter needs variable with write access as input. To VAR_IN_OUT parameters only variables with write access can be handed over, because these can be modified within the POU.
4348

Invalid program name '<name>'. A variable with the same name exists already.

You have inserted a program box in the CFC editor, which has the same name as a (global) variable already existing in your project. You must rename accordingly.

4349

Input or output in POU <name> has been deleted: Check all connections to the box. This errormessage disappears only after the CFC was edited

Correct the POU appropriately.

4350 An SFC-Action can not be accessed from outside! SFC actions only can be called within the SFC POU in which they are defined.
4351 Step name is no identifier: '<name>' Rename the step or choose a valid identifier as step name.
4352 Extra characters following valid step name:'<name>' Remove the not valid characters in the step name.
4353 Step name duplicated: '<name>' Rename one of the steps.
4354 Jump to undefined Step: '<name>' Choose an existent step name as aim of the jump resp. insert a step with name ‚<name>’.
4355 A transition must not have any side effects (Assignments, FB-Calls etc.) A transition must be a boolean expression.
4356 Jump without valid Step Name: '<name>'  Use a valid identifier as aim (mark) of the jump.
4357 IEC-Library not found Check whether the library iecsfc.lib is inserted in the library manager and whether the library paths defined in ‘Project’ ‘Options’ ‘Paths’are correct.
4358 Action not declared: '%s'. Make sure that in the object organizer the action of the IEC step is inserted below the SFC POU and that in the editor the action name is inserted in the box on the right hand of the qualifier.
4359 Invalid Qualifier: '%s' In the box on the left hand of the action name enter a qualifier for the IEC action.
4360 Time Constant expected after qualifier '%s' Enter next to the box on the left hand of the action name a time constant behind the qualifier.
4361 '%s' is not the name of an action Enter next to the box on the right hand of the qualifier the name of an action or the name of a variable which is defined in the project.
4362 Nonboolean expression used in action: '%s' Insert a boolean variable or a valid action name.
4363 IEC-Step name already used for variable: '<name>' Please rename the step or the variable.
4364 A transition must be a boolean expression The result of the transition expression must be of type BOOL.
4365 Time Constant expected after qualifier '<name>' Open dialog ‚step attributes’ for the step '<name>' and enter a valid time variable or time constant
4366 The label of the parallel branch is no valid identifier: '<name>' Enter a valid identifier next to the triangle which marks the jump label.
4367 The label '<name>' is already used There is already a jump label or a step with this name. Please rename correspondingly.
4368 Action '<name>' is used in multiple step chains, where one is containing the other! The action '<name>' is used in the POU as well as in one or several actions of the POU.
4369 Exactly one network required for a transition  There are used several FBD resp. LD networks for a transition. Please reduce to 1 network.
4370 Additional lines found after correct IL-transition Remove the not needed lines at the end of the transition.
4371 Invalid characters following valid expression: '<name> Remove the not needed characters at the end of the transition.
4372

Step '<name>': Time limit needs type 'TIME'

Define the time limits of the step in the step attributes by using a variable of type TIME or by a time definition in correct format (e.g. "t#200ms").

4373

IEC-actions are only allowed with SFC-POUs

There is an action assigned to a non-SFC-POU (see in the Object Organizer), which is programmed in SFC and which contains IEC actions. Replace this action by one which contains no IEC actions.

4374

Step expected instead of transition '<name>'

The SFC POU is corrupt, possibly due to any export-import actions.

4375

Transition expected instead of step '<name>'

The SFC POU is corrupt, possibly due to any export-import actions.

4376

Step expected after transition '<name>'

The SFC POU is corrupt, possibly due to any export-import actions.

4377

Transition expected after step '<name>'

The SFC POU is corrupt, possibly due to any export-import actions.

4500 Unrecognized variable or address The watch variable is not declared within the project. By pressing <F2> you get the input assistant which lists the declared variables.
4501 Extra characters following valid watch expression Remove the surplus signs.
4520 Error in Pragma: Flag expected before '<name>'! The pragma is not correct. Check whether ‘<name>' is a valid flag.
4521 Error in Pragma: Unexpected element '<name>'! Check whether pragma is composed correctly.
4522 "flag off' pragma expected! The switch off of the pragma is missing, add a 'flag off' instruction.
4550 Index out of defined range : Variable OD "number>, Line <line number>. Ensure that the index is within the area which is defined in the target settings/ networkfunctionality.
4551 Subindex out of defined range : Variable OD "number>, Line <line number>. Ensure that the subindex is within the area which is defined in the target settings /networkfunctionality.
4552 Index out of defined range : Parameter OD "number>, Line <line number>. Ensure that the index is within the area which is defined in the target settings /networkfunctionality
4553 Subindex out of defined range : Parameter OD "number>, Line <line number>. Ensure that the subindex is within the area which is defined in the target settings /networkfunctionality.
4554 Variablename invalid: Variable OD <number>, Line <line number>. Enter a valid project variable in the filed ‚variable’. Use the syntax <POU name>.<variable name> resp. for global variables .<variable name>
4555 Empty table-entry, input not optional: Parameter OD <number>, Line <line number>  You must make an entry in this field.
4556 Empty table-entry, input not optional: Variable OD <number>, Line <number> You must make an entry in this field.
4557

The required parameter memory is too large

The maximum size of data which can be loaded via parameter lists of type Parameters to the controller has been exceeded. This size is defined by the target system. Information on the data size is displayed in the message window at compilation. Reduce the parameter lists size.

4558

The required variable memory is too large

The maximum size of data which can be loaded via parameter lists of type Variables to the controller has been exceeded. This size is defined by the target system. Information on the data size is displayed in the message window at compilation. Reduce the parameter lists size.

4560

Invalid value: Dictionary '<Name>', column '<Name>', line '<line number>'

Check this entry. It depends on the currently used column (attribute) definition which entries are valid for this field. This definition is given by the target-specific XML description file of the Parameter Manager resp. by the standard settings which will be used if there is no description file.

4561

Column not defined: '<Name>'

Entries in a column of the parameter list refer to another column, which is not defined however. The column definitions are given by the description file (XML) of the Parameter Manager for the current target. If a description file is not available, standard settings are used.

4562

Index/subindex used already: Dictionary '<Name>', line '<Line Number>'

The Index/Subindex-combination must be unique throughout all parameter lists, because it can be used for the parameter access. Correct the indices correspondingly.

4563

Identifier '<Name>' used already: Dictionary '<Name>', line '<Line Number>'

The name must be unique throughout all parameter lists, because it can be used for parameter access.

4564

Index '<Name>' is out of range: Dictionary '<Name>', line '<Line Number>'

Enter an index which is within the range defined in the target settings, category network functionality in field 'Index range...' for the respective list types (Variables, Parameters, Mappings).

4565

Subindex '<Name>' is out of range: Dictionary '<Name>', line '<Line Number>'

Enter an subindex which is within the range defined in the target settings, category network functionality in field 'SubIndex range'.

4566

An error occurred during import of the parameter manager

You have imported an export file which contains erroneous information on the Parameter Manager. Check the *.exp-file.

4600

Networkvariables: '<name>' expression is not from type bool!

 Make sure that the variable defined in the properties dialog of the network variables list at option 'Transmit on event', is of type BOOL.

4601

Network variables '<name>': No cyclic or freewheeling task for network variable exchange found

There is no cyclic or free-wheeling task resp. PLC_PRG in the project where the network variables of type CAN or UDP of the given list are used (only declaration is not sufficient!). You must take care that the variables are used in an appropriate task or in PLC_PRG. If you want to use them in several tasks, regard, that at data exchange the task with the highest priority will be regarded.

4602

'<name of network variables list>': The object uses UDP port '<port number>' instead of '<port number>'

In the Settings of the named network variables list a port number is used which is not the same as that which is used in the first network variables list found in the global variables folder. Take care that all network variables lists are using the same port!

4620

Unused variables have been found in the project.

Unused variables have been found in the project.

4621

There are overlaps at the assignment of variables to memory areas via the „AT"-declaration.

There are overlaps at the assignment of variables to memory areas via the „AT"-declaration.

4622

IEC addresses assigned to the same memory area are referenced in more than one task.

IEC addresses assigned to the same memory area are referenced in more than one task.

4623

The project gains write access to the same memory area at more than one place.

The project gains write access to the same memory area at more than one place.

4650

AxisGroup '<Name>': Task '<Name>' does not exist.

 

In the PLC Configuration in the definition of the axis group (dialog 'Module parameters', column 'Value') there is a name defined for the task which is controlling the data transfer of this axis group, which is not known in the Task Configuration. Correct Task Configuration resp. PLC Configuration correspondingly.

4651

AxisGroup '<Name>': Cycletime (dwCycle) not set.

In dialog 'Module parameters' of the axis group enter a value for the cycle time (dwCycle).

4670

CNC program '<Name>': Global variable '<Name>' not found.

In the CNC program a global variable is used (e.g. $glob_var$), which is not defined in the project. Add the appropriate declaration resp. correct the assignment to the variable in the CNC program.

4671

CNC program '<Name>': Variable '<Name>' has an incompatible type.

There is a variable assigned in a instruction of the CNC program , which is declared of a data type which is not valid in this place. Use another variable resp. correct the type specification.

4685

CAM '<Name>': CAM table type unknown.

Check the data type which is specified in the CAM Editor dialog ''Compile options.." for the equidistant resp. element optimized point table.

4686

CAM '<Name>': CAM point exceeds datatype range.

In this CAM points are used, which are out of the data range specified for the point table. For the current range definition see dialog 'Compile options..' in the CAM-Editor.

4700

'<Number>' ('<Name>'): Watch expression '<Name>' is not a numeric variable.

In the configuration of the visualization a variable is used which is not a number, as required in this place (e.g. at the configuration of XOffset or Angle values etc.).

4701

'<Name>' ('<Number>'): Watch expression '<name>' is not of type BOOL.

In the configuration of the visualization a variable is used which is not of type BOOL, as required in this place.

4702

'<Name>' ('<Number>'): Watch expression '<name>' is not of type STRING.

The visualization contains a variable which is not of type STRING although this is required in this place (e.g. at the tooltip configuration).

4703

'<Name>' ('<Number>' ): Invalid watch expression '<Name>'

The visualization contains an invalid variable.

4704

'<Name>'('<Number>'): Invalid initial value in watchlist '<Name>'.

In this watchlist, used in a visualization (INTERN command in category Input), there is a erroneous

initial value. Check the used list.

4705

'<name>' ('<number>'): No valid alarm group assigned to alarm table.

Enter a valid alarm group In the configuration dialog of the alarm table (category Alarm table).

4900

Invalid type for conversion

You are using a type conversion which is not supported by the currently chosen codegenerator.

4901

Internal error: Overflow in array access!

The array bounds are to large for a 32-bit-variable. Reduce the array index range.