iCube Engineer Online Help

About iCube Engineer
About This Documentation
Before You Start
Safety-Related Hazard Messages
System requirements
System Limits of iCube Engineer
Software Licensing: Registering iCube Engineer
Quickstart: Overview on Engineering Steps
Passwords with PLCnext
User Interface - Reference
- Start Page
- Main Menu/Toolbar and Shortcuts
- Editor Toolbars, Context Menus and Shortcuts
- PLANT Area
- COMPONENTS Area
- Editors Area
- Cross Function Area
- Project Statistics
- Status Bar
- Other User Interface Functions
  - Tooltips
Keyboard Shortcuts
- Standard Windows Shortcuts
Security in iCube Engineer
- IEC 62443 Compliance
- Security Guideline for iCube Engineer
- Recommended Security Measures for Devices and Solutions
- Controller Security (Settings via WBM)
- Network Security: Certificates enable Secure Connection
- Network Security: Authentication with User Role and Password
- Network Security: OPC UA Server Security Settings
- Security terms and background information
Safety-Related Application/Area
- Safety-Related Area: General Information
- Safety-Related Area: Defining/Changing a Password
- Safety-Related Area: Logon to/Logoff from
iC9200 Series Controller Generation
- Hardware Feature license management
IEC 61131-3 Programming
- POUs
- Instantiation: Program and FB Instances
- Data Types
- Variables
- Literals according to IEC 61131-3
- Reserved Keywords in IEC Programming
- Object-oriented Programming
- Namespaces
- Programming ST
- Programming FBD/LD, NOLD and SNOLD
- Programming SFC
iCube Engineer Toolchain
- Installing IDE plug-ins for iCube Engineer Toolchain
- Managing SDKs
- Programming in C#
- Programming in C++
  - Working with Eclipse
  - Working with Visual Studio
Function/Function Block Reference
- Data Types: Generic and Elementary
- Implicit Data Type Conversion
- Function Block Instantiation
- Execution Control: EN/ENO
  - Inserting POUs with EN/ENO
  - Evaluating the ENO output for logic functions/function blocks
  - Writing user-defined FUs/FBs with EN/ENO - Best Practice
- Alarms and ErrorIDs
  - Function Block ErrorID List
  - Controller Alarm ID List
  - Sigma Servo Alarm Notification Details
- IEC 61131-3 Functions and Function Blocks
  - Arithmetic
    - ADD / ADD_S
    - ADD_LDT_LTIME
    - ADD_LTOD_LTIME
    - DIV / DIV_S
    - EXPT
    - MOD
    - MUL / MUL_S
    - NEG
    - SUB / SUB_S
    - SUB_LDATE_LDATE
    - SUB_LDT_LDT
    - SUB_LDT_LTIME
    - SUB_LTOD_LTIME
    - SUB_LTOD_LTOD
  - Arrays
    - LOWER_BOUND
    - UPPER_BOUND
  - Bistable
    - RS / RS_S
    - SR / SR_S
  - Bit Shift
    - ROL
    - ROR
    - SHL
    - SHL_WORD
    - SHR
    - SHR_WORD
  - Bitwise Boolean
  - Character String
    - CONCAT
    - CONCAT_WSTRING
    - DELETE
    - DELETE_WSTRING
    - FIND
    - FIND_WSTRING
    - INSERT
    - INSERT_WSTRING
    - LEFT
    - LEFT_WSTRING
    - LEN
    - MID
    - MID_WSTRING
    - REPLACE
    - REPLACE_WSTRING
    - RIGHT
    - RIGHT_WSTRING
  - Comparison Functions
    - EQ / EQ_S
    - GE / GE_S
    - GT / GT_S
    - LE / LE_S
    - LT / LT_S
    - NE / NE_S
    - IS_NAN
    - IS_NEG_INF
    - IS_POS_INF
  - Counter
  - Data Type Conversion
  - Edge Detection
    - F_TRIG / F_TRIG_S
    - R_TRIG / R_TRIG_S
  - Numerical and Arithmetic
    - ABS
    - ACOS
    - ASIN
    - ATAN
    - COS
    - EXP
    - LN
    - LOG
    - SIN
    - SQRT
    - TAN
  - Selection
    - LIMIT
    - MAX
    - MIN
    - MOVE
    - MUX
    - SEL / SEL_S
  - Timer
- Extended Functions and Function Blocks
  - Data Handling
  - Exception Infos
    - GET_EXCEPTION_INFOS
  - File Access
    - FILE_CLOSE
    - FILE_OPEN
    - FILE_READ
    - FILE_REMOVE
    - FILE_SEEK
    - FILE_TELL
    - FILE_WRITE
  - Hardware Access
    - RTC_S
    - RTC_WS
  - Loop Controller
  - Variable Access
    - GET_SYMBOL
- PLCnext Controller Function Blocks
  - Alarming
  - Data Handling
    - PACK
    - UNPACK
  - Device Information
  - Localization
    - GET_LANG_STRING
    - GET_LANG_WSTRING
  - Profinet
  - Timer
- Y_EtherCAT
  - Y_EtherCAT DataType
    - Yt_EC_COE_RecvEmergencyMessage
  - Y_EtherCAT FB
- Y_DataTypes_Toolbox
  - Y_DataTypes_Toolbox Data Type
- Y_SliceBus
  - Y_SliceBus FB
    - Y_SB_DataRecordWrite
    - Y_SB_DataRecordRead
- Y_IOModule_Toolbox
  - Y_IOModule_Toolbox FB
- Y_Math_Toolbox
  - Y_Math_Toolbox Information
    - Y_Math_Toolbox Change Log: Conversion from MotionWorksIEC
  - Y_Math_Toolbox Data Type
    - Yt_MA_ATAN2OutputType
    - Yt_MA_Matrix
  - Y_Math_Toolbox FB
- Y_Yaskawa_Toolbox
  - Y_Yaskawa_Toolbox Data Type
  - Y_Yaskawa_Toolbox FB
- Y_FileRW_Toolbox
  - Y_FileRW_Toolbox Information
    - Memory area available for user files in ic92xx
  - Y_FileRW_Toolbox Data Type
  - Y_FileRW_Toolbox FB
- Y_Comm_Toolbox
  - Y_Comm_Toolbox DataType
  - Y_Comm_Toolbox FB
- Y_PackML_Toolbox
  - Y_PackML_Toolbox Data Type
  - Y_PackML_Toolbox FB
- Y_PLCopenPart1_Toolbox
  - Y_PLCopenPart1_Toolbox Information
  - Y_PLCopenPart1_Toolbox FB
- Y_Axis_Toolbox
  - Y_Axis_Toolbox Data Type
  - Y_Axis_Toolbox FB
- Y_Cam_Toolbox
  - Y_Cam_Toolbox Information
    - Cam Curve Characteristics
  - Y_Cam_Toolbox DataType
  - Y_Cam_Toolbox FB
- Y_PLCopenPart4_Toolbox
  - Y_PLCopenPart4_Toolbox Information
  - Y_PLCopenPart4_Toolbox Data Type
  - Y_PLCopenPart4_Toolbox FB
- Y_Group_Toolbox
  - Y_Group_Toolbox Data Type
    - Y_GP_GroupTypes
      - Yt_GP_MachineStruct
      - Yt_GP_JointMap
    - Y_GP_PendantTypes
      - Yt_GP_UserApplicationData
  - Y_Group_Toolbox FB
- Safety FBs in PLCopen_SF Library
  - Safety of the Machine or System
  - Activating Function Blocks (Activate)
    - Individual Activation of Safety Equipment
    - Group Activation of Safety Equipment
    - Modular Machines/Systems with Safety Equipment
  - Interlocking in Accordance with DIN EN ISO 14119/14120
  - SF_Antivalent
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ChannelNC and S_ChannelNO inputs
    - DiscrepancyTime input
    - Ready output
    - S_AntivalentOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_EDM (External Device Monitoring)
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OutControl input
    - S_EDM1 and S_EDM2 inputs
    - MonitoringTime input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_EDM_Out output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_EmergencyStop
    - Functional description
    - Fault avoidance
    - Activate input
    - S_EStopIn input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_EStopOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_EnableSwitch
    - Functional description
    - Fault avoidance
    - Activate input
    - S_SafetyActive input
    - S_EnableSwitchCh1 and S_EnableSwitchCh2 inputs
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_EnableSwitchOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagram
    - Additional application example
  - SF_Equivalent
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ChannelA and S_ChannelB inputs
    - DiscrepancyTime input
    - Ready output
    - S_EquivalentOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_ESPE
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ESPE_In input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_ESPE_Out output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application example
  - SF_GuardLocking 2
    - Functional description
    - Fault avoidance
    - Activate input
    - S_GuardMonitoring input
    - S_SafetyActive input
    - S_GuardLock input
    - UnlockRequest input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_GuardLocked output
    - S_UnlockGuard output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
  - SF_GuardMonitoring
    - Functional description
    - Fault avoidance
    - Activate input
    - S_GuardSwitch1 and S_GuardSwitch2 inputs
    - DiscrepancyTime input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_GuardMonitoring output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_ModeSelector
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Mode0 to S_Mode7 inputs
    - S_Unlock input
    - S_SetMode input
    - AutoSetMode input
    - ModeMonitorTime input
    - Reset input
    - Ready output
    - S_Mode0Sel to S_Mode7Sel outputs
    - S_AnyModeSel output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_MutingPar
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - MutingSwitch11 and MutingSwitch12 inputs
    - MutingSwitch21 and MutingSwitch22 inputs
    - S_MutingLamp input
    - DiscTime11_12 input
    - DiscTime21_22 input
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_MutingPar_2Sensor
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - S_MutingSwitch11 and S_MutingSwitch12 inputs
    - S_MutingLamp input
    - DiscTimeEntry input
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_MutingSeq
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - MutingSwitch11 and MutingSwitch12 inputs
    - MutingSwitch21 and MutingSwitch22 inputs
    - S_MutingLamp input
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_OutControl
    - Functional description
    - Fault avoidance
    - Activate input
    - S_SafeControl input
    - ProcessControl input
    - StaticControl input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_OutControl output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application example
  - SF_Reset
    - Functional description
    - Fault avoidance
    - Activate input
    - ResetIn input
    - RisingEdge input
    - EdgeMonitoring input
    - MinEdgeTime input
    - MaxEdgeTime input
    - OperationStop input
    - Ready output
    - ResetOut output
    - ResetPossible output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
  - SF_SafetyRequest
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OpMode input
    - S_Acknowledge input
    - MonitoringTime input
    - Reset input
    - Ready output
    - S_SafetyActive output
    - S_SafetyRequest output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Details about the signal sequence diagram
    - Details of the application example
  - SF_TestableSafetySensor
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OSSD_In input
    - StartTest input
    - TestTime input
    - NoExternalTest input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_OSSD_Out output
    - S_TestOut output
    - TestPossible output
    - TestExecuted output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_TwoHandControlTypeII
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Button1 and S_Button2 inputs
    - Ready output
    - S_TwoHandOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Details of the application example
  - SF_TwoHandControlTypeIII
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Button1 and S_Button2 inputs
    - Ready output
    - S_TwoHandOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Details of the application example
- Safety FBs in PLCopen_SF_V2_00 Library
  - Safety of the Machine or System
  - Activating Function Blocks (Activate)
    - Individual Activation of Safety Equipment
    - Group Activation of Safety Equipment
    - Modular Machines/Systems with Safety Equipment
  - Interlocking in Accordance with DIN EN ISO 14119/14120
  - SF_Antivalent
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ChannelNC and S_ChannelNO inputs
    - DiscrepancyTime input
    - Ready output
    - S_AntivalentOut output
    - SafetyDemand output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_EDM (External Device Monitoring)
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OutControl input
    - EDM1 and EDM2 inputs
    - MonitoringTime input
    - Reset input
    - Ready output
    - S_EDM_Out output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional application examples
  - SF_EmergencyStop
    - Functional description
    - Fault avoidance
    - Activate input
    - S_EStopIn input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_EStopOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_EnableSwitch
    - Functional description
    - Fault avoidance
    - Activate input
    - S_SafetyActive input
    - S_EnableSwitchCh1 and S_EnableSwitchCh2 inputs
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_EnableSwitchOut output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagram
    - Additional application example
  - SF_Equivalent
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ChannelA and S_ChannelB inputs
    - DiscrepancyTime input
    - Ready output
    - S_EquivalentOut output
    - SafetyDemand output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_ESPE
    - Functional description
    - Fault avoidance
    - Activate input
    - S_ESPE_In input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_ESPE_Out output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application example
  - SF_Guard
    - Functional description
    - Fault avoidance
    - Activate input
    - S_GuardSwitch1 and S_GuardSwitch2 inputs
    - DiscrepancyTime input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_GuardMonitoring output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_GuardLocking 2
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Guard input
    - S_SafetyActive input
    - S_GuardLock input
    - UnlockRequest input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_GuardLocked output
    - S_UnlockGuard output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
  - SF_ModeSelector
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Mode0 to S_Mode7 inputs
    - S_Unlock input
    - S_SetMode input
    - AutoSetMode input
    - ModeMonitorTime input
    - Reset input
    - Ready output
    - S_Mode0Sel to S_Mode7Sel outputs
    - S_AnyModeSel output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application examples
  - SF_MutingPar
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - MutingSwitch11 and MutingSwitch12 inputs
    - MutingSwitch11 and MutingSwitch12 inputs
    - DiscTime11_12 input
    - DiscTime21_22 input
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_MutingPar_2Sensor
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - S_MutingSwitch11 and S_MutingSwitch12 inputs
    - DiscTimeEntry input
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_MutingSeq
    - Functional description
    - Fault avoidance
    - Activate input
    - S_AOPD_In input
    - S_MutingSwitch11 and S_MutingSwitch12 inputs
    - S_MutingSwitch11 and S_MutingSwitch12 inputs
    - MaxMutingTime input
    - MaxOverrideTime input
    - MutingEnable input
    - S_StartStopOverride input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_AOPD_Out output
    - S_MutingActive output
    - OverridePossible output
    - OverrideActive output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_OutControl
    - Functional description
    - Fault avoidance
    - Activate input
    - S_SafeControl input
    - ProcessControl input
    - StaticControl input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_OutControl output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application example
  - SF_PSE
    - Functional description
    - Fault avoidance
    - Activate input
    - S_PSE_In input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_PSE_Out output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Additional application example
  - SF_Reset
    - Functional description
    - Fault avoidance
    - Activate input
    - ResetIn input
    - RisingEdge input
    - EdgeMonitoring input
    - MinEdgeTime input
    - MaxEdgeTime input
    - OperationStop input
    - Ready output
    - ResetOut output
    - ResetPossible output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
  - SF_SafetyRequest
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OpMode input
    - S_Acknowledge input
    - MonitoringTime input
    - S_StartReset input
    - Reset input
    - Ready output
    - S_SafetyActive output
    - S_SafetyRequest output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Details about the signal sequence diagram
    - Additional application example
  - SF_TestableSafetySensor
    - Functional description
    - Fault avoidance
    - Activate input
    - S_OSSD_In input
    - StartTest input
    - TestTime input
    - NoExternalTest input
    - S_StartReset input
    - S_AutoReset input
    - Reset input
    - Ready output
    - S_OSSD_Out output
    - S_TestOut output
    - TestPossible output
    - TestExecuted output
    - SafetyDemand output
    - ResetRequest output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Additional signal sequence diagrams
    - Details of the application example
  - SF_TwoHandControlTypeII
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Button1 and S_Button2 inputs
    - Ready output
    - S_TwoHandOut output
    - SafetyDemand output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Details of the application example
  - SF_TwoHandControlTypeIII
    - Functional description
    - Fault avoidance
    - Activate input
    - S_Button1 and S_Button2 inputs
    - Ready output
    - S_TwoHandOut output
    - SafetyDemand output
    - Error output
    - DiagCode output
    - Diagnostic codes
    - State machine diagram
    - Implementation of safety requirements from applicable standards
    - Details of the application example
- Y_MSync_Toolbox
  - Y_MSync_Toolbox Data Type
    - Yt_MS_MSync_CONVEYOR_REF_ARRAY
  - Y_MSync_Toolbox FB
  - Y_MSync_Toolbox Information
    - MotomanSync functionality supported with MSync group with PLCopen Part4 layout
- Y_DeviceDataTypes
  - Y_DeviceDataTypes Data Type
- Y_PackML2022_Toobox
  - Y_PackML2022_Toolbox Data Type
  - Y_PackML2022_Toolbox FB
Functionality
- Networking
- Device Configuration/Parameterization
- Controller Runtime Configuration and Tasks
  - Task Configuration
  - Extended Retain Handling
- Controller Commissioning: From Compiling to Debugging
- Project Comparison
- Library Management
- Importing / Exporting Project Data
- Data Lists and GDS port List
  - Data Lists
  - GDS Port Lists
- Project Management
Safety PLC Runtime Configuration
Safety PLC Simulation
Safety PLC Commissioning: From Compiling to Debugging
- Safety PLC Password Protection
- Connecting vs. Monitoring Mode vs. Debug Mode
- Rebuilding the Safety-Related Project (without Writing)
- Aborting the Build Process manually
- Safety Cockpit: Controlling the Safety Application
- Safety PLC Diagnostics out of the Safety Cockpit
- FSoE Communication/Device State Diagnostics
- Safety PLC States
- Monitoring/Debugging the Safety PLC
Application Notes
- PLANT
- COMPONENTS
  - Libraries
- Web Based Management
- Programming and Project Management using iCube Engineer
- Hardware
  - Effect of MRESET vs Archive delete vs Reset type1/2 on iC9200 series
Error Catalog
- Controller Configuration Errors
  - Configuration Error (PLCN0001): The task '...' must have a priority between ... and ....
  - Configuration Error (PLCN0002): The task '...' must have an interval time between ... and ... with the step of ....
  - Configuration Error (PLCN0003): The task '...' must have a watchdog time between ... and ... with the step of .... Use 0 to disable the watchdog.
  - Configuration Error (PLCN0004): The task '...' has an invalid type or event name.
  - Configuration Error (PLCN0005): The program instance '...' has an invalid program type '...'.
  - Configuration Error (PLCN0006): There are too many tasks defined in '...' (current : ..., max. allowed: ...).
  - Configuration Error (PLCN0007): The task '...' contains too many program instances defined in '...' (current : ..., max. allowed: ...).
  - Configuration Error (PLCN0008): The OPC UA configuration is not valid. ...
  - Configuration Error (PLCN0009): The task '...' uses the same event name value '...' as another task, which is not allowed.
  - Configuration Error (PLCN0010): The task '...' uses the event name value '...', which is reserved for a predefined event.
  - Configuration Error (PLCN0011): There are too many program instances defined in '...' (current : ..., max. allowed: ...).
  - Configuration Error (PLCN0012): The system variables update task '...' is invalid.
  - Configuration Error (PLCN0015): The ESM '...' already contains an idle task.
  - Configuration Error (PLCN0021): The connected port '...' is not referenced in any program instance.
  - Configuration Error (PLCN0022): There are too many tasks defined in '...' (current : ..., max. allowed: ...).
  - Configuration Error (PLCN0023): The task '...' must have a priority between ... and ....
  - Configuration Error (PLCN0051): The remote variable identifier format '' is invalid.
- FDCML Parser Errors
  - FDCML Error (FDCM0021): DNS segments must contain at least one character.
  - FDCML Error (FDCM0022): DNS segments may not exceed 63 characters. Segment "..." has a length of '...'.
  - FDCML Error (FDCM0023): DNS segments must consist of ASCII characters. Invalid character '...' encountered.
  - FDCML Error (FDCM0024): DNS segments may not begin or end with the delimiters '-' and '.'.
  - FDCML Error (FDCM0025): DNS hostnames must contain at least one character. Given length: '...'.
  - FDCML Error (FDCM0026): DNS hostnames may not exceed 253 characters. Given length: '...'.
  - FDCML Error (FDCM0027): DNS hostnames may not resemble IP addresses.
  - FDCML Error (FDCM0028): DNS hostnames may not start with "port-###".
- SliceBus Errors
- Controller Runtime Errors
  - Error: The system event must contain at least one program instance.
- Profinet Errors
  - Profinet Error (PNIO0001): The Profinet device '...' has an empty DNS hostname.
  - Profinet Error (PNIO0003): The Profinet controller '...' has '...' Profinet devices connected. The maximum number of devices is '...'.
  - Profinet Error (PNIO0004): The Profinet controller '...' has reached RAM capacity. Reduce the number of devices.
  - Profinet Error (PNIO0005): An internal error occurred while checking the Profinet data lengths of device '...'.
  - Profinet Error (PNIO0006): The Profinet input length '...' of device '...' exceeds the maximum number of bytes '...'.
  - Profinet Error (PNIO0007): The Profinet output length '...' of device '...' exceeds the maximum number of bytes '...'.
  - Profinet Error (PNIO0008): The monitor time of device '...' exceeds 1920 ms.
  - Profinet Error (PNIO0009): The Profinet controller '...' is overloaded. Consider decreasing the reduction ratios or removing a Profinet device.
  - Profinet Error (PNIO0011): The Profinet device '...' cannot operate in RT class IRT. It is not supported by the assigned Profinet Controller.
  - Profinet Error (PNIO0017): The Profinet device '...' needs a higher reduction ratio.
  - Profinet Error (PNIO0025): Profinet '...' module is missing a submodule
  - Profinet Error (PNIO0027): The I/O port update task '...' does not exist.
  - Profinet Error (PNIO0028): The system variables update task '...' is invalid.
  - Profinet Error (PNIO0029): The device system variables update task '...' is invalid.
  - Profinet Error (PNIO0030): There are connected Profinet devices without redundancy support.
  - Profinet Error (PNIO0040): The Profinet device ... does not support device sharing.
  - Profinet Error (PNIO0042): Fast startup for Profinet submodule ... cannot be configured as long as the master does not support fast startup.
  - Profinet Error (PNIO0100): MRP: Domain UUID "..." defined more than once. Every mrp manager must have a unique uuid.
  - Profinet Error (PNIO0101): MRP: Domain Name "..." defined more than once. Every mrp manager must have a unique name.
  - Profinet Error (PNIO0103): MRP: UUID "..." used in ring port configuration not declared.
  - Profinet Error (PNIO0104): Exactly two ports with same uuid "..." needed for a ring port to be configured.
  - Profinet Error (PNIO0106): MRP: Max number or supported client instances (50) per ring exceeded.
  - Profinet Error (PNIO0107): MRP: More than one manager defined "... / ...".
  - Profinet Error (PNIO0108): MRP: Two clients on one device must not have identical domain uuids "...".
  - Profinet Error (PNIO0109): MRP: Two clients on one device must not have identical domain names "...".
  - Profinet Warning (PNIO0112): The device "..." cannot be updated cyclically faster than "...".
- Ethernet Errors
  - Ethernet Error (TCPP0001): A unique DNS hostname could not be created for device .... Manually assign a DNS hostname.
  - Ethernet Error (TCPP0003): The DNS hostname '...' of device '...' is used more than once in the network.
  - Ethernet Error (TCPP0004): The DNS hostname '...' of device '...' has invalid syntax.
  - Ethernet Error (TCPP0005): The DNS hostname '...' of device '...' does not use the top-level domain '...' of the subnet.
  - Ethernet Error (TCPP0006): The IP address '...' of device '...' lies above the network's end address '...'.
  - Ethernet Error (TCPP0007): The IP address '...' of device '...' lies below the network's start address '...'.
  - Ethernet Error (TCPP0009): A free IP address could not be found for the new device type '...'. Increase the address range.
  - Ethernet Error (TCPP0011): The device '...' does not have an IP address.
  - Ethernet Error (TCPP0012): The IP address '...' of device '...' collides with the network address '...'.
  - Ethernet Error (TCPP0013): The IP address '...' of device '...' is used more than once in the network.
  - Ethernet Error (TCPP0014): The network does not contain a valid end IP address.
  - Ethernet Error (TCPP0015): The default gateway '...' lies above the subnet's visible IP range.
  - Ethernet Error (TCPP0016): The default gateway '...' lies below the subnet's visible IP range.
  - Ethernet Error (TCPP0017): The default gateway '...' is identical to the network's broadcast address.
  - Ethernet Error (TCPP0019): The default gateway '...' is identical to the network's network address.
  - Ethernet Error (TCPP0020): The subnet mask '...' of the network has an invalid format. Subnet masks must consist of adjacent 1s from the left.
  - Ethernet Error (TCPP0021): The network does not contain a valid subnet mask.
  - Ethernet Error (TCPP0022): The start IP address '...' of the network is greater than the end IP address '...'.
  - Ethernet Error (TCPP0023): The network does not contain a valid start IP address.
  - Ethernet Error (TCPP0024): The start IP address '...' and end IP address '...' do not lie in the same subnet.
  - Ethernet Error (TCPP0025): The domain suffix '...' of the network is invalid.
  - Ethernet Error (TCPP0026): The device '...' does not have a subnet mask.
  - Ethernet Error (TCPP0027): The default gateway ... of the device ... is not in its subnet.
- REPLACE error messages
  - Replace Error (REPLACE0008): Adding submodule "..." to module "..." failed.
- Lexical Errors
  - Lexical Error (LEX0001): Invalid constant '...'.
  - Lexical Error (LEX0002): Invalid direct variable '...'.
  - Lexical Error (LEX0003): Invalid identifier '...'.
  - Lexical Error (LEX0004): Invalid token '...'.
  - Lexical Error (LEX0006): New line in string literal.
  - Lexical Error (LEX0007): '}' expected.
  - Lexical Error (LEX0008): Invalid LINE pragma.
  - Lexical Error (LEX0009): The nested comment was not correctly closed. '...' expected.
  - Lexical Error (LEX0005, LEX0010): '...' expected.
  - Lexical Error (LEX0011): Invalid Partial Access of ANY_BIT Variable '...'.
  - Lexical Error (LEX0012): String literal contains Invalid escape characters.
- Syntactical Errors (Various Parsers)
  - ST Parser Errors (STP)
  - FBD/LD Parser Errors (FBDP)
  - Data Types Parser Errors (DTP)
- Semantic Errors and Warnings
  - Semantic Error (SEM1001): The lower bound of the array dimension must not be greater than the upper bound.
  - Semantic Error (SEM1004): An array must have at least one dimension.
  - Semantic Error (SEM1006): The data type '...' is not an array.
  - Semantic Error (SEM1008): A library with the name '...' does already exist.
  - Semantic Error (SEM1011): Invalid constant '...'.
  - Semantic Error (SEM1012): A data type with the name '...' does already exist.
  - Semantic Error (SEM1013): Invalid data type '...'.
  - Semantic Error (SEM1014): Recursive dependency found in data type '...'.
  - Semantic Error (SEM1023): The label '...' does not exist.
  - Semantic Error (SEM1024): A label with the name '...' does already exist.
  - Semantic Error (SEM1027): A program organization unit with the name '...' does already exist.
  - Semantic Error (SEM1030): Recursive dependency found in program organization unit '...'.
  - Semantic Error (SEM1036): The variable '...' does not exist.
  - Semantic Error (SEM1037): The data type '...' is not a structure or program organization unit.
  - Semantic Error (SEM1038): The field or variable '...' does not exist in '...'.
  - Semantic Error (SEM1041): '...' is not a valid function block.
  - Semantic Error (SEM1042): '...' is not a valid function.
  - Semantic Error (SEM1045): The function block instance '...' does not exist.
  - Semantic Error (SEM1046): The function '...' expects only ... input parameter(s).
  - Semantic Error (SEM1047): The function '...' expects ... input parameter(s).
  - Semantic Error (SEM1051): A variable with the name '...' does already exist.
  - Semantic Error (SEM1063): Assignments to constant variables are not valid.
  - Semantic Error (SEM1064): The function '...' expects at least ... input parameter(s).
  - Semantic Error (SEM1065): Invalid implicit address '...'.
  - Semantic Error (SEM1066): Invalid base data type '...' for enumeration '...'.
  - Semantic Error (SEM1067): A value with the name '...' does already exist in enumeration '...'.
  - Semantic Error (SEM1068): Invalid value '...' in enumeration '...'.
  - Semantic Error (SEM1070): The data type of value '...' is not equal to the base data type '...' of enumeration '...' .
  - Semantic Error (SEM1072): A value with the name '...' does not exist in the enumeration '...'.
  - Semantic Error (SEM1074): An enumeration with the name '...' does not exist.
  - Semantic Error (SEM1075): The data type '...' is not an enumeration.
  - Semantic Error (SEM1076): The enumeration value '...' does not exist.
  - Semantic Error (SEM1077): Ambiguous enumeration value '...'.
  - Semantic Error (SEM1078): The data type of the case list element ('...') is not 'ANY_INT'.
  - Semantic Error (SEM1079): The data type of the expression ('...') is not 'ANY_INT'.
  - Semantic Error (SEM1080): The data type of the control variable ('...') is not 'ANY_INT'.
  - Semantic Error (SEM1081/SEM1082/SEM1083): The data type of the ... value expression ('...') is not 'ANY_INT'.
  - Semantic Error (SEM1085): The '...' statement expects an expression of type 'BOOL'.
  - Semantic Error (SEM1086): 'EXIT' is only allowed in the scope of an iteration statement.
  - Semantic Error (SEM1087): The variable '...' does not exist in '...'.
  - Semantic Error (SEM1089): The data type of the array index ('...') is not 'ANY_INT'.
  - Semantic Error (SEM1091): The function '...' does not define any input parameters.
  - Semantic Error (SEM1093): A field with the name '...' does already exist.
  - Semantic Error (SEM1094): The function block '...' does not contain a method '...' with the name.
  - Semantic Error (SEM1097): Invalid function call.
  - Semantic Error (SEM1099): The method '...' has no return value.
  - Semantic Error (SEM1100): The expression data type '...' is not equal to the variable data type '...'.
  - Semantic Error (various between SEM1101 and SEM1113): Wrong or mismatching operand data types.
  - Semantic Error (SEM1115, SEM1116): The function block '...' does not have an output/input parameter with the name '...'.
  - Semantic Error (SEM1117): The data type '...' of the parameter '...' and the data type '...' of assigned value are not equal.
  - Semantic Error (SEM1118): The data type '...' of the expression attached to the parameter '...' of the function '...' is invalid. (Expected data type: '...')
  - Semantic Error (SEM1126): The data types of the external variable '... : ...' and the related global variable '... : ...' are not equal.
  - Semantic Error (SEM1133): Assignments to read-only variables are not valid.
  - Semantic Error (SEM1134): The assignment of function blocks is not supported.
  - Semantic Error (SEM1139): VAR_IN_OUT parameter '...' must not be unassigned.
  - Semantic Error (SEM1140): Constant variables cannot be assigned to VAR_IN_OUT parameters.
  - Semantic Error (SEM1141): Read-only variables cannot be assigned to VAR_IN_OUT parameters.
  - Semantic Error (various between SEM1170 and SEM1179): State-machine relating errors
  - Semantic Error (SEM1173): The transition expects a condition of type 'BOOL'.
  - Semantic Error (SEM1186, SEM1187, SEM1188): There are too many ... defined in the project (current: ..., max. allowed: ...).
  - Semantic Error (SEM1189): The data type '...' of the expression attached to the parameter '...' of the function '...' cannot be implicitly converted to '...'.
  - Semantic Error (SEM1190): The specified IEC type '...' is inaccessible.
  - Semantic Error (SEM1191): The specified function block type '...' does not match the type '...' of the already defined function block instance '...'.
  - Semantic Error (SEM1192): There exists already an idle task in resource '...'
  - Semantic Error (SEM1194): The identifier is too long. (current length: ..., max. allowed length: ...)
  - Semantic Error (SEM1195): There are ... indices specified but the array ... defines ... dimension(s).
  - Semantic Error (SEM1196): Invalid index value.
  - Semantic Error (SEM1197): Index value exceeds the bounds of the array dimension.
  - Semantic Error (SEM1198): Assignment to step status is not allowed.
  - Semantic Error (SEM1200): The pragma with the name '...' cannot be found.
  - Semantic Error (SEM1201): The pragma '...' has invalid parameters.
  - Semantic Error (SEM1202): The pragma '...' has no parameter with name '...'.
  - Semantic Error (SEM1203): Invalid value '...' of parameter '...' of pragma '...'.
  - Semantic Error (SEM1205): The initialization value of the variable exceeds the size of the array data type '...'.
  - Semantic Error (SEM1207): The string constant is longer than the maximum length of the data type '...'.
  - Semantic Error (SEM1222): 'THIS' is not allowed in functions.
  - Semantic Error (SEM1225): 'CONTINUE' is only allowed in the scope of an iteration statement.
  - Semantic Error (SEM1230): Unconnected function input.
  - Semantic Error (SEM1232): The function '...' does not have an output parameter with the name '...'.
  - Semantic Error (SEM1233): The value '...' is already handled by a previous case.
  - Semantic Error (SEM1234): One or more values in the range '... .. ...' are already handled by a previous case.
  - Semantic Error (SEM1237): The usage of the function block VAR_IN_OUT parameter '...' is not allowed in user methods.
  - Semantic Error (SEM1238): A variable named '...' is already defined in this scope.
  - Semantic Error (SEM1239): '...' is inaccessible due to its protection level.
  - Semantic Error (SEM1245): Argument ...: Cannot convert from '...' to '...'.
  - Semantic Error (SEM1246): Method '...' does not take '...' arguments.
  - Semantic Error (SEM1251): Invalid partial access '...'.
  - Semantic Error (SEM1253): The data type '...' of variable '...' is not valid. It is required to be of type '...'.
  - Semantic Error (SEM1255): There are too many elements used in the program organization unit: '...' (current: ..., max. allowed: ...).
  - Semantic Error (SEM1259): Recursive method call found in method '...'
  - Semantic Error (SEM1265): The function '...' expects '...' output parameter(s).
  - Semantic Error (SEM1266): The function '...' expects only '...' output parameter(s).
  - Semantic Error (SEM1267): The function '...' expects the parameter '...' instead of '...'.
  - Semantic Error (SEM1268): Invalid method call.
  - Semantic Error (SEM1269): The parameter '...' has changed in the definition of the function.
  - Semantic Error (SEM1270): Invalid access to VAR_IN_OUT parameter '...' of function block '...'.
  - Semantic Error (SEM1275): The value '...' exceeds the range '...' to '...' of data type '...'.
  - Semantic Error (SEM1276): Reading values of generic formal parameters is not allowed.
  - Semantic Warning (SEM2001): Ambiguous identifier '...'.
  - Semantic Warning (SEM2004, SEM2005, SEM2006): The POU '...' is not used.
  - Semantic Warning (SEM2007): There are no resources defined.
  - Semantic Warning (SEM2008): The variable '...' was named like a program organization unit that does already exist.
  - Semantic Warning (SEM2009): The variable '...' was named like a data type that does already exist.
  - Semantic Warning (SEM2010): The external usage of VAR_IN_OUT parameters is not allowed. No code will be generated for this statement.
  - Semantic Warning (SEM2013): The parameters of function block '...' have changed in definition.
  - Semantic Warning (SEM2014): Not all array elements are initialized.
  - Semantic Warning (SEM2015): The field '...' of '...' is initialized more than once.
  - Semantic Warning (SEM2016): The identifier is ambiguous between the variable '... : ... : ...' and the enumeration value '...'. The value of the variable is used.
  - Semantic Warning (SEM2017): The parameter '...' has changed in the definition of the method.
  - Semantic Warning (SEM2018): A program organization unit with the name '...' does already exist.
- CIL Generator Errors and Warnings
  - CIL Generator Error (CILG0001): Internal Error.
  - CIL Generator Error (CILG0006): The size of the variable data type is greater than the available memory in the data area at '... . ...'.
  - CIL Generator Error (CILG0007): Assignments to read-only variables are not valid.
  - CIL Generator Error (CILG0009): The specified assembly reference '...' could not be found.
  - CIL Generator Error (CILG0011): STRUCTs and ARRAYs are not allowed in functions.
  - CIL Generator Error (CILG0012): CIL Code generation aborted.
  - CIL Generator Error (CILG0013/CILG0014/CILG0015): There exists a name conflict between ...
  - CIL Generator Error (CILG0016): The conversion of '...' values to data type '...' is not supported.
  - CIL Generator Error (CILG0021): There exists a name conflict between the task and the global variable '...'.
  - CIL Generator Error (CILG0022): There exists a name conflict between the program instance and the global variable '...'.
  - CIL Generator Error (CILG0025): The conversion of '...' BCD values to data type '...' is not supported.
  - CIL Generator Error (CILG0027): The method name '...' in program organization unit '...' is not allowed for user defined methods.
  - CIL Generator Error (CILG0028): The action is not found as BOOL variable nor as method.
  - CIL Generator Error (CILG0030 to CILG0036): The selected resource '...' does not support ...
  - CIL Generator Error (CILG0037): The output parameter '...' is not connected.
  - CIL Generator Error (CILG0038/CILG0039/CILG0040): There exists a name conflict between ...
  - CIL Generator Error (CILG0054): There exists a name conflict between the program organization unit '...' and an interlock with the same name inside the program organization unit.
  - CIL Generator Error (CILG0055): The function '...' defines ... input parameters which exceeds the limit of 29
  - CIL Generator Error (CILG1003): Invalid string constant ... for data type STRING
- CIL Compiler Errors and Warnings
  - CIL Compiler Error (CILC0001): Error during generating native code.
  - CIL Compiler Error (CILC2003): The fieldnames associated to the class/struct exceeds the limit
  - CIL Compiler Error (CILC2005): Field offset exceeds the limit of 16MB
  - CIL Compiler Error (CILC2007): Amount of fields exceeds the limit of 130K
  - CIL Compiler Error (CILC3014): The branch operation exceeds the limit of the current CPU
  - CIL Compiler Error (CILC3019): Meta format of the generated image exceeds the internal limit
  - CIL Compiler Error (CILC3020): The internal memory of the compiler is exceeded
  - CIL Compiler Error (CILC3021): The offset is too large, please move the variable into front of the variable list
  - CIL Compiler Error (CILC3026): The fixed array layout size of the type does not match the array boundary
- OPC UA PubSub Configuration Errors
  - OPC UA PubSub Configuration Error (PLCN0024): The OPC UA PubSub configuration is not valid.
  - OPC UA PubSub Configuration Error (PLCN0026): '...': Connection name must be unique.
  - OPC UA PubSub Configuration Error (PLCN0027): '...': Publisher ID must be unique.
  - OPC UA PubSub Configuration Error (PLCN0028): '...': Network address must be an url with the following pattern: opc.udp://(:port)
  - OPC UA PubSub Configuration Error (PLCN0029): '...': The network interface must be one of the interfaces provided by the controller.
  - OPC UA PubSub Configuration Error (PLCN0030): '...': The name of the published data set must be unique within the configuration.
  - OPC UA PubSub Configuration Error (PLCN0031): '...': The variable '...' was not found in the current configuration or it does not have a supported type.
  - OPC UA PubSub Configuration Error (PLCN0032): '...': The name of the reader group must be unique within the configuration.
  - OPC UA PubSub Configuration Error (PLCN0033): '...': The name of the reader must be unique within the configuration.
  - OPC UA PubSub Configuration Error (PLCN0034): '...': The target variable '...' was not found in the current configuration or it does not have a supported type.
  - OPC UA PubSub Configuration Error (PLCN0035): '...': The name of the writer group must be unique within the connection.
  - OPC UA PubSub Configuration Error (PLCN0036): '...': The ID of the writer group must be unique within the connection.
  - OPC UA PubSub Configuration Error (PLCN0037): '...': The name of the writer must be unique within the connection.
  - OPC UA PubSub Configuration Error (PLCN0038): '...': The ID of the writer must be unique within the connection.
  - OPC UA PubSub Configuration Error (PLCN0039): '...': The specified data set does not exist in the current configuration.
  - OPC UA PubSub Configuration Error (PLCN0040): '...': The published variable '...' may not also be subscribed.
  - OPC UA PubSub Configuration Error (PLCN0041): '...': The subscribed variable '...' may not also be published.
  - OPC UA PubSub Configuration Error (PLCN0042): '...':
  - OPC UA PubSub Configuration Error (PLCN0043): '...': The id must not have the value '...'.
  - OPC UA PubSub Configuration Error (PLCN0044): '...': The publishing interval must not be less than 20 ms.
- Data Logger Configuration Errors
  - Data Logger Error (DL0001): The task context for the data logger session '...' is not defined. Please select an existing task.
  - Data Logger Error (DL0002): The trigger condition operand for the data logger session '...' is not defined. Please select a variable or define a constant.
- Data List Build Errors
  - Data List Build Error (DL0001): Invalid connection due to incompatible data types.
  - Data List Build Error (DL0002): Invalid port connection! Please disconnect to remove invalid port ("...").
- Safety-Related Semantic Errors
  - Safety Semantic Error: Non-safe input writes on safe output ...!
  - Safety Semantic Error: Unknown Function or Function Block '...'.
  - Safety Semantic Error: The Function or Function Block '...' cannot be used in safety programs.
  - Safety Semantic Error: Invalid data type '...'.
  - Safety Semantic Error: The defined FB instance '...' is never used.
  - Safety Semantic Error: The FB instance '...' is used more than once.
  - Safety Semantic Error: Invalid overwriting of input variable '...'.
  - Safety Semantic Error: Feedback not allowed.
  - Safety Semantic Error: Short circuits not allowed in ladder.
  - Safety Semantic Error: The variable '...' is read and written in the same network.
  - Safety Semantic Error: The output '...' is written more than once.
  - Safety Semantic Error: The global variable '...' is written more than once.
  - Safety Semantic Error: The variable '...' is declared local as well as global.
  - Safety Semantic Error: The variable '...' is read before written.
  - Safety Semantic Error: The output '...' is read before written.
  - Safety Semantic Warning: The variable '...' is not used.
  - Safety Semantic Warning: The global variable '...' is used within a single POU. Consider to use a local variable.
  - Safety Semantic Error: Invalid statement in FBD / LD worksheet.
  - Safety Semantic Warning: The global variable '...' may have a storing behavior as its write access can be jumped over.
  - Safety Semantic Warning: The output '...' may have a storing behavior as its write access can be jumped over.
  - Safety Semantic Error: Backward jumps are not allowed.
  - Safety Semantic Error: The variable '...' is written more than once in the same network.
  - Safety Semantic Error: Instance signature diverges from type signature.
  - Safety Semantic Error: No corresponding jump found!
  - Safety Semantic Error: Variable with usage type 'Input' is written to.
  - Safety Semantic Error: Invalid parameter! The input parameter of the function block must be a variable.
  - Safety Semantic Error: Invalid parameter! The input parameter of the function block must be a constant.
  - Safety Semantic Error: The variable '...' is not defined.
  - Safety Semantic Error: The variable usages 'Program', 'IN Port' and 'OUT Port' are not supported in safety POUs.
  - Safety Semantic Error: The global variable '...' is not defined.
- Miscellaneous Safety-Related Errors
  - Error (Assemble Download File): The file '...' is missing.
  - Error: Creating the build output folder '...' failed.
- Safety Intermediate Code Generator Errors
  - Error (Safety Intermediate Code Generator): Invalid statement.
  - Error (Safety Intermediate Code Generator): Undefined Variable '...'.
  - Error (Safety Intermediate Code Generator): Undefined Function Block instance '...'.
  - Error (Safety Intermediate Code Generator): Unknown data type '...'.
  - Error (Safety Intermediate Code Generator): Unknown Function or Function Block '...' used by the Function or Function Block '...'.
  - Error (Safety Intermediate Code Generator): Invalid initial value expression.
- Safety Specific Code Generator Errors
  - Error (Safety Specific Code Generator): Illegal data type: '...'.
  - Error (Safety Specific Code Generator): Unknown variable.
  - Error (Safety Specific Code Generator): Unknown global variable '...'.
  - Error (Safety Specific Code Generator): Invalid processor type specified in the device profile: '...'.
  - Error (Safety Specific Code Generator): Missing file in the device profile: '...'.
  - Error (Safety Specific Code Generator): Unknown POU '...'.
- Safety Backend Compiler Errors
  - Internal Error (Safety Backend Compiler)! Call the technical support.
  - Internal Error '...' (Safety Backend Compiler). Call the technical support.
  - Error (Safety Backend Compiler): Stack limit exceeded ... Shrink the project.
  - Error (Safety Backend Compiler): Maximum limit of stack elements exceeded ... Shrink the project. (Safety Backend Compiler)
- Safety Violation Messages and Data Integrity Errors
  - Error (Data Integrity Check): The worksheet 'POUname:WSname' has no valid safety seal.
  - Error (Data Integrity Check): The worksheet 'POUname:WSname' has no safety seal.
  - Error (Data Integrity Check): Internal error (SafetyViolation).
  - Error (Data Integrity Check): The POU '...' has no valid safety seal.
  - Error (Data Integrity Check): The POU '...' has no safety seal.
- Safety Library Parser Errors
  - Error (Safety Library Parser): Invalid Type of POU '...' specified in the Safety Library '...'.
  - Error (Safety Library Parser): Error parsing the library '...': Invalid file format.
  - Error (Safety Library Parser): Invalid safety seal for the POU '...' in the Safety Library '...'.
  - Error (Safety Library Parser): POU '...': Definition mismatch between the Safety Library '...' and the Standard Library '...'.
  - Error (Safety Library Parser): Error parsing the library '...': Invalid or missing definition for the POU '...'.
  - Error (Safety Library Parser): Safety violation! Safety seal for library '...' is missing.
  - Error (Safety Library Parser): Safety violation! Safety seal for Firmware POU '...' is missing.
  - Error (Safety Library Parser): Invalid safety seal for the safety library '...'.
  - Error (Safety Library Parser): Invalid safety library '...'.
  - Error (Safety Library Parser): The default library '...' is missing or empty.
- Safety Library Export Errors
  - Error (Safety Library Export): The safety inventory of the created library is missing.
  - Error (Safety Library Export): Only visible POUs can be released.
  - Error (Safety Library Export): Adding a time stamp to the signature of the safety inventory failed.
  - Error (Safety Library Export): Releasing the item '...' failed.
  - Error (Safety Library Export): Creating the signature of the safety inventory failed.
  - Error (Safety Library Export): Saving the safety inventory failed.
- Error Messages of the Safety PLC
  - Error: Code in POU '...' exceeds 64K limit! Shrink the POU.
  - Error: Error occurred in POU '...' during code generation!
  - Error: Failure State: Service not possible. Please reset the Safety PLC or download a project!
  - Error: Debug watchdog (10 min) elapsed! The debug mode is active but the client is logged out. (Safety PLC time: '...')
  - Error: Maximum number of errors reached at WN '...'! Code generation stopped!
  - Error: Memory error! Not enough memory on Safety PLC for POU '...'! Shrink the project.
  - Error: Memory error! POU '...' exceeds 64K module size! Shrink the POU.
  - Error: Memory error! Project does not fit into Safety PLC memory! Shrink the project.
  - Error: Not enough memory for force list! Reduce the amount of forced variables.
  - Error: Too many FB instances! Shrink the project. (Safety PLC time: '...')
  - Error: Too many function calls! Shrink the project. (Safety PLC time: '...')
  - Error: Too many marker! Shrink the project. (Safety PLC time: '...')
  - Error: Wrong project file version number! The project cannot be processed with this Safety PLC. Update your Safety PLC hardware.
  - Error: Stack overflow during execution of the IEC 61131 user program! Safety PLC stopped!
  - Error: Division by zero during execution of the IEC 61131 user program! Safety PLC stopped!
  - Internal Error
  - Safety PLC event! '...'
Glossary: Terms and Abbreviations
Contact