Skip to main content

Error Messages

This section contains a list of the error messages of the compiler for the CODESYS Safety for EtherCAT Safety Module extension of the CODESYS development system.

In the case of a safety application, the user can use the standard command Build (F11) of an application to manually initiate the safety-specific function for the development system part of the error checks. To do this, the safety application must be set as the active application. Before the safety application is downloaded, this process is executed automatically. At this time, error messages may appear in the standard message view, where it is possible to jump from an error code to its position in the source code.

Tip

As of SP17, the manual check is no longer performed together with F11. However, the check can be performed with the Create EtherCAT Safety Module Application command from the Build menu.

Table 60. Error in the EL6900/EL6910/EK1960 application

Error Number

Category

Error Text

Explanation

[SELC0001]

Build

Assignment at input '{0}' not permitted

Depending on the function block type, the inputs can be linked with variables or fixed values can be specified (example: times). The direct linking of inputs with assignments is not permitted.

[SELC0002]

Build

Function block expected

No type name is specified or an invalid type name is specified.

A function block must have a valid type name. The following type names are valid:

  • FB_AND

  • FB_CS

  • FB_DECOUPLER

  • FB_EDM

  • FB_ESTOP

  • FB_MODE

  • FB_MON

  • FB_MUTING

  • FB_OR

  • FB_SR

  • FB_RS

  • FB_TOF

  • FB_TON

  • FB_TWOHAND

  • FB_ADD

  • FB_CAMMONITOR

  • FB_COMPARE

  • FB_COUNTER

  • FB_DIV

  • FB_ENVELOPE

  • FB_LIMIT

  • FB_LOADSENSING

  • FB_MUL

  • FB_SCALING

  • FB_SLI

  • FB_SPEED

  • FB_SUB

  • FB_VIOLATIONCNT

[SELC0003]

Build

Identifier '{0}' already defined

The identifier has already been assigned in the project. A unique identifier must be used.

[SELC0004]

Build

Invalid COM ERR output

The output of a group is linked with an invalid variable (not a safe output or a standard output).

[SELC0005]

Build

Invalid ERR Ack input

The input of a group is linked with an invalid variable (not a safe input or a standard input).

The ERR ACK input is not linked.

[SELC0006]

Build

Invalid FB ERR output

The output of a group is linked with an invalid variable (not a safe output or a standard output) or with an unknown variable.

[SELC0007]

Build

Invalid FSoE address

The code is checked whether or not the address is a value of the data type UINT. The address is read from the parameter and checked for the value range from 0 to a maximum value of 65535 (UINT).

[SELC0008]

Build

Invalid identifier '{0}'

The input of a function block is linked with an invalid variable (not a safe input or a standard input) or with an unknown variable.

[SELC0009]

Build

Invalid input

The element at the input of the FB is not a box and not a variable.

[SELC0010]

Build

Invalid input '{0}'

The value at the input has the wrong data type.

[SELC0011]

Build

Invalid instance name '{0}'

Wrong or missing instance name.

[SELC0012]

Build

No connections defined

At least one FSoE/TwinSAFE-SC connection must be defined in a safety application.

[SELC0013]

Build

No function blocks defined

At least one function block must be defined in a safety application.

[SELC0014]

Build

No groups defined

At least one group must be defined in a safety application.

[SELC0015]

Build

No output mappings defined

At least one output mapping must be defined in a safety application.

[SELC0016]

Warning

More than {0} bits of exchange data into the module

The maximum total length of incoming exchange data supported by the device from the standard controller is exceeded.

[SELC0017]

Warning

More than {0} bits of exchange data from the module

The maximum total length of outgoing exchange data supported by the device to the standard controller is exceeded.

[SELC0018]

Build

Invalid operand

The name or type of the FB main output is empty.

[SELC0019]

Build

Invalid operand '{0}'

The name of the FB main output is not found in the process image.

[SELC0020]

Build

Invalid OUT ERR output

The output of a group is linked with an invalid variable (not a safe output or a standard output) or with an unknown variable.

[SELC0021]

Build

Invalid output mapping: {0} -> {1}

The mapping of a group output or the FB output (not a main output) is invalid. Local safe outputs, safe outputs, and unsafe outputs are permitted.

[SELC0022]

Build

Invalid RUN/STOP input

The input of a group is linked with an invalid variable (not a safe input or a standard input) or with an unknown variable.

[SELC0023]

Build

Invalid write access '{0}'

The output of a function block is linked with an invalid variable (not a safe output or a standard output) or with an unknown variable.

[SELC0024]

Build

Instance name ‘{0}’ already exists

The instance name of a function block within a safety POU is not unique.

[SELC0025]

Build

Input '{0}' must be used.

Specific inputs must exist. A required input must be used.

[SELC0026]

Build

Physical device for logical device '{0}' is missing

A physical device belonging to the logical device does not exist.

[SELC0027]

Build

Negation not permitted for input '{0}'

Specific inputs of function blocks can be normally closed or normally open contacts. Whether an input should be a normally closed contact or a normally open contact can be defined for this input in the editor by means of the Negation command. A non-negated input is a normally closed contact and a negated input is a normally open contact. If an input which can only be a normally closed contact but not a normally open contact is negated, then the error is issued.

[SELC0028]

Build

No function blocks defined in the group

At least one function block must exist in a safety application in one of the safety POUs inserted below.

[SELC0029]

Build

Output already mapped: {0} -> {1}

There must not be any double output linking with an safe output within a safety POU. If a safe output is used twice, then this error is issued.

[SELC0030]

Build

Process image larger than {0} bytes

The maximum supported total length of the local process image has been exceeded.

[SELC0031]

Build

Missing source operand

The FB output is not found in the process image.

[SELC0032]

Build

Unknown function block ‘{0}’

The FB type is unknown. It is possible that the library is not installed or has not been added to the Library Manager. Only FBs from TcEL6900FBs or TcEL69xxAnalogFBs may be used.

[SELC0033]

Build

Connection: Invalid user parameters

The parameter cannot be found. Possible error in the device description.

[SELC0034]

Build

Connection: Invalid connection parameter length

The length of the connection parameters of a safe logical exchange device is invalid. Possible error in the device description.

[SELC0035]

Build

Connection: ‘Safe User Parameter’ must not be larger than {0} bytes

The maximum supported length of the FSoE Safe user parameters assigned to the connection has been exceeded.

[SELC0036]

Build

Connection: Invalid user parameters

The length of the user parameters is greater than 32 bytes.

Only for EL6900

[SELC0037]

Build

Invalid mapping

  • Internal error when creating the mappings

  • For input mappings (EK1960/EL6910), if:

    • The source is not an FB output, standard input, safe input.

    • The target is not an FB input or group input.

  • For output mappings (EK1960/EL6910/EL6900), if:

    • The source is not an FB output or group output.

    • The target is not a standard output, safe output, or local safe output.

[SELC0038]

Build

Invalid formal parameter

The name and type of an FB input in the internal structure is empty.

[SELC0039]

Build

Unknown input parameter ‘{0}’

The name of an FB input is not known because the function blocks from the TcEL6900FBs or TcEL69xxAnalogFBs libraries have not been used.

[SELC0040]

Build

Unknown output parameter ‘{0}’

The name of an FB output is not known because the function blocks from the TcEL6900FBs or TcEL69xxAnalogFBs libraries have not been used.

[SELC0041]

Build

Invalid output parameter

The names and types of the FB outputs in the internal structure are wrong.

[SELC0042]

Build

Invalid output parameter type

The type of an FB output in the internal structure is empty.

[SELC0043]

Build

{0}: Invalid message length parameter

The parameter cannot be found or has an invalid value. Possible error in the device description.

[SELC0044]

Build

Connection: Safety input message must not be larger than {0} bytes

The maximum supported length of the FSoE input message per connection has been exceeded.

[SELC0045]

Build

Connection: Safety output message must not be larger than {0} bytes

The maximum supported length of the FSoE output message per connection has been exceeded.

[SELC0047]

Build

The logical device ‘{0}’ is used in different groups (‘{1}’)

It is not allowed to use a connection in different groups.

[SELC0048]

Build

Invalid number of input mappings

There are no input mappings or too many input mappings. For example, an input mapping is a mapped FB input.

No input mappings occur if an FB is inserted but no variables are defined at the inputs or no variables are defined at the group inputs (Run and Ack).

The maximum number of input mappings is 65535.

For EK1960/EL6910

[SELC0049]

Build

Invalid input parameter

The names and types of the FB inputs in the internal structure are wrong.

[SELC0050]

Build

Invalid input parameter type

The type of an FB input in the internal structure is empty.

For EK1960/EL6910

[SELC0051]

Build

Invalid input mapping: {0} -> {1}

The assignment of a group input, FB input, or input of an FSoE/TwinSAFE-SC connection is invalid. Local safe inputs, safe inputs, and unsafe inputs are permitted.

FSoE/TwinSAFE-SC connection

[SELC0052]

Build

Input already mapped: {0} -> {1}

A group input, FB input, or input of a FSoE/TwinSAFE-SCconnection already has a mapping.

[SELC0053]

Build

Logical exchange device ‘{0}‘ is not used in safety application and should be removed

Logical exchange devices are permitted below the EtherCAT safety application only if they are in use. If no variable from the logical exchange device is used in the FSoE safety application, then the logical exchange device must be removed.

[SELC0054]

Build

Input ‘{0}’ is not supported by the device.

Only for EL6900

As of version 4.0.3.0 of the TcEL6900FBs library, the FB_ESTOP, FB_MON, and FB_MUTING function blocks have the tEDM1ResetTime and tEDM2ResetTime inputs. These inputs are not supported by EL6900, but only by EL6910 and EK1960. If these inputs are used with the EL6900, then a compiler error is displayed.

[SELC0059]

Build

Value of input ‘{0}’ is not in valid range ({1})

[SELC0072]

Build

Value of ‘{0}’ does not meet the condition ‘{1}’

For some FBs, different conditions apply to the configured values. If one of these conditions is not fulfilled, then the error is issued.

For EL6910/EK1960: FB_CAMMONITOR

For EL6900: FB_TON and FB_TOF

[SELC0081]

Build

At least two inputs of the function block must be connected.

For FB_AND and FB_OR, at least two inputs must be connected.

[SELC0082]

Build

This device does not support substitute values.

Only for EL6900

[SELC0089]

Build

More than {0} groups defined

The maximum supported total number of groups in the safety application is exceeded.

[SELC0090]

Build

More than {0} function blocks defined

The maximum supported total number of function blocks in the safety application is exceeded.

[SELC0091]

Build

More than {0} connections defined

The maximum supported total number of FSoE/TwinSAFE-SCconnections in the safety application is exceeded.

[SELC0092]

Build

More than {0} connections defined in group

The maximum supported total number of FSoE connections in a group is exceeded (EL6900 only).

[SELC0093]

Build

More than {0} output mappings defined

The maximum supported total number of output mappings in the safety application is exceeded.

[SELC0094]

Build

Invalid number of function blocks in group

Internal error: This error only occurs with an invalid internal configuration and is normally not relevant for the user.

Only for EL6900

[SELC0095]

Build

No connections defined in group

At least one FSoE connection must be assigned to a group.

[SELC0103]

Build

The Standard Inputs Size of zero is not permitted.

The total length of the standard inputs must not be 0.

[SELC0104]

Build

The function block {0} is not supported by the device.

According to the device description, the function block used is not supported by the device.



Table 61. Error in the EL6910/EK1960 application

Error Number

Category

Error Text

Explanation

[SELC0055]

Build

Only one of the inputs ‘{0}’ may be set to TRUE

For FB_COMPARE, the b1oo2, b2oo3, and b3oo5 inputs are available. Only one of these inputs may be TRUE. If that is not the case, then the error is issued during the build.

For FB_DIV and FB_SCALING, the bFloor, bCeil, and bRound inputs are available. Only one of these inputs may be TRUE. If that is not the case, then the error is issued during the build.

For FB_CAMMONITOR, the bExcentricMode and bPendulumMode inputs are available. Only one of these inputs may be TRUE. If that is not the case, then the error is issued during the build.

[SELC0056]

Build

At least one of the inputs ‘{0}’ may be set to TRUE

For FB_COMPARE, the b1oo2, b2oo3, and b3oo5 inputs are available. At least one of these inputs must be TRUE. If that is not the case, then the error is issued during the build.

For FB_DIV and FB_SCALING, the bFloor, bCeil, and bRound inputs are available. At least one of these inputs must be TRUE. If that is not the case, then the error is issued during the build.

For FB_CAMMONITOR, the bExcentricMode and bPendulumMode inputs are available. At least one of these inputs must be TRUE. If that is not the case, then the error is issued during the build.

[SELC0057]

Build

At least one of the inputs '{0}' must be active

For FB_EDM, at least one of the tSwitchOnMonitoring and tSwitchOffMonitoring inputs must be active. If that is not the case, then the error is issued during the build.

For FB_TWOHAND, at least one of the bTwoHand1 and bTwoHand2 inputs and at least one of the bTwoHand3 and bTwoHand4 inputs must be active. If that is not the case, then the error is issued during the build.

[SELC0058]

Build

Invalid output ‘{0}’.

The function block output is connected to a variable of the wrong data type (bool <-> analog).

[SELC0060]

Build

Value of the input ‘{0}’ is not in valid range of the data type specified for ‘{1}’

[SELC0061]

Build

Value of input ‘{0}’ exceeds the maximum value of the data type specified for ‘{1}’

[SELC0062]

Build

Input ‘{0}’ has a {1}-bit data type, but is connected to a {2}-bit variable

An analog input configured for a 16-bit data type must not be connected to a variable of 32-bit data type and vice versa. An analog input configured for a 16-bit data type may only be connected to a variable of 16-bit data type. An analog input configured for a 32-bit data type may only be connected to a variable of 32-bit data type.

[SELC0063]

Build

The data type of input ‘{0}’ has to be the same as the data type of the connected function block output

If an input of a function block is connected to an output of another function block, then both must be of the same data type.

[SELC0064]

Build

Output ‘{0}’ has a {1}-bit data type, but is connected to a {2}-bit variable

An analog output configured for a 16-bit data type must not be connected to a variable of 32-bit data type and vice versa. An analog output configured for a 16-bit data type may only be connected to a variable of 16-bit data type. An analog output configured for a 32-bit data type may only be connected to a variable of 32-bit data type.

[SELC0065]

Build

The data type of ‘{0}’ has to be the same as the data type of ‘{1}

For FB_LIMIT, the same data type must be configured for the MinValue, MaxValue, and AnalogIn inputs. If that is not the case, then the error is issued during the build.

[SELC0066]

Build

The {0}-values of the ‘Value Settings’ table do not match with the selected data type of input ‘{1}’

For FB_LOADSENSING: The x values of the value table must be within the range of the data type which is configured for the AnalogInX input. The y1, y2, wy1, wy2 values in the value table must lie within the value range of the data type which is configured for the AnalogInY input. If that is not the case, then the error is issued during the build.

[SELC0067]

Warning

The X-values of the ‘Value Settings’ table must be written in ascending order

For FB_LOADSENSING: The x-values in the value table must be in ascending order. If that is not the case, then the error is issued during the build.

[SELC0068]

Warning

The Y-values of the ‘Value Settings’ table must meet the condition Y1[i] <= WY1[i] < WY2[i] <= Y2[i]

For FB_LOADSENSING: If bOutsideY1Y2 == FALSE, then the y values in the value table must fulfill the condition Y1[i] <= WY1[i] < WY2[i] <= Y2[i]. If that is not the case, then the error is issued during the build.

[SELC0069]

Build

The Y values of the 'Value Settings' table must fulfill the condition WY1[i] <= Y1[i] < Y2[i] <= WY2[i]

For FB_LOADSENSING: If bOutsideY1Y2 == TRUE, then the y values in the value table must fulfill the condition WY1[i] <= Y1[i] < Y2[i] <= WY2[i]. If that is not the case, then the error is issued during the build.

[SELC0070]

Build

Inputs ‘{0}’ have to be connected (operating mode ‘{1}’)

For FB_COMPARE: If b1oo2 == TRUE, then CompIn1 and CompIn2 must be connected. If b2oo3 == TRUE, then CompIn1,CompIn2, and CompIn3 must be connected. If b3oo5 == TRUE, then CompIn1,CompIn2,CompIn3, CompIn4, and CompIn5 must be connected. If that is not the case, then the error is issued during the build.

[SELC0071]

Build

Input ‘{0}’ is connected, but it is not activated (operating mode ‘{1}’)

. For FB_COMPARE: The error is issued, if:
  • b1oo2 == TRUE and CompIn3, CompIn4, or CompIn5 is connected

  • b2oo3 == TRUE and CompIn4 or CompIn5 is connected

[SELC0073]

Build

All analog inputs and outputs must have the same data type

For FB_CAMMONITOR, the same data type must be configured for all analog inputs and outputs.

[SELC0074]

Build

Input ‘{0}’ must not be used in pendulum mode.

For FB_CAMMONITOR, the OverrunMax, bBackwardsMove, bOverrunCAM, and bUpwardCAM inputs must not be connected in pendulum mode.

[SELC0075]

Build

Input ‘{0}’ must not be used in excentric mode.

For FB_CAMMONITOR, the TDC2LowerLimit and TDC2UpperLimit inputs must not be connected in excentric mode.

[SELC0076]

Build

Output '{0}' must be used in excentric mode

For FB_CAMMONITOR, the OverrunTDC output must be connected in excentric mode.

[SELC0077]

Build

Output ‘{0}’ must be used if the input ‘{1}’ is used

For FB_CAMMONITOR, the OverrunStop output must be connected if the bPressStarted input is connected.

[SELC0078]

Build

A constant value must be set at input ‘{0}’ if the input ‘{1}’ is used.

For FB_CAMMONITOR, constant values must be specified at the TDC1LowerLimit, TDC1UpperLimit, TDC2LowerLimit, TDC2UpperLimit, BDCLowerLimit, BDCUpperLimit, and OverrunMax inputs, and no assignment to variables if the bSettingMode input is connected.

[SELC0079]

Build

Number of ‘Safe User Parameter’ configuration data pages exceeded the maximum of {0}

The maximum supported number of data pages required for the Safe User Parameters has been exceeded.

[SELC0080]

Build

Output ‘{0}’ must be used

Specific outputs must exist. A required output must be used.

[SELC0083]

Build

Too many substitute values in the application

The size of the data set for the substitute values has been exceeded.

All substitute values of an application are stored in one data record. The maximum size of this data set is 2048 bytes.

[SELC0084]

Build

In a passivatable group, only one connection may be defined

A POU whose properties allow passivation may only access the I/O channels of a single field device.

[SELC0085]

Build

This group is not deactivatable. The configured substitute values are ignored.

Substitute value have been defined for signals in a POU, but deactivation is not enabled in the properties of this POU.

[SELC0086]

Build

A substitute value for an output must not be defined more than one time.

Several substitute values are defined for one output in a safety POU. However, only one substitute value is permitted.

[SELC0087]

Build

Substitute value does not match the data type of the output '{0}'

The data type of the replacement value must be compatible with the data type of the output.

[SELC0096]

Build

More than {0} TwinSAFE-SC Master connections

The maximum number of TwinSAFE-SC Master connections supported by the device has been exceeded.

[SELC0097]

Build

Near process image size exceeds the maximum of {0} bytes

The maximum total length of the near-process image (process image without FB status data) supported by the device has been exceeded.

[SELC0098]

Build

EtherCAT input size exceeds the maximum of {0} bytes

The maximum total length of standard inputs and FSoE input messages supported by the device has been exceeded. During the check, an additional 1 byte each is taken into account for the Safe Logic State and Cycle Counter values.

[SELC0099]

Build

EtherCAT output size exceeds the maximum of {0} bytes

The maximum total length of standard outputs and FSoEoutput messages supported by the device has been exceeded. During the check, an additional 1 byte each is taken into account for the Safe Logic State and Cycle Counter values.

[SELC0100]

Build

Cyclic FRAM data size exceeds the maximum of {0} bytes

The maximum length supported by the device in FRAM for customizing has been exceeded.

[SELC0101]

Build

Number of 'Safe Logic' configuration data records exceeds the maximum of {0}

The maximum supported number of Safe Logic data records required for the safety application has been exceeded.

[SELC0102]

Build

Mapping code size has exceeded the maximum of {0} bytes

The maximum supported size of the code generated for the mappings in the device has been exceeded.