Beijer Electronics X2 control User manual

Quick Start Guide
X2/BoX2 series with CODESYS control
SUEN00392E - Recommendations and limitations

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
2 (61)
Normal.dotm, 2020-09-09
1 Function and area of use
This document provides guidelines when working with the X2/BoX2 series range of products
with embedded CODESYS runtime.
2About this Startup document
This Startup document should not be considered as a complete manual. It is an aid to be able to
Startup a normal application quickly and easily.
Use the following software and drivers in order to obtain a stable application:
In this document we have used following software and hardware
-BCS Tools 3.30
-CODESYS 3.5 SP13 patch 3
-iX Developer 2.40 SP5
For further information refer to
-iX Developer Reference Manual (MAxx831) iX Developer User's Guide (MAxx832D),
Driver help in iX Developer
-CODESYS online help
This document and other Startup documents can be obtained from our homepage.
Please use the address [email protected] for feedback about our Startup documents.
Copyright © Beijer Electronics, 2022
This documentation (below referred to as ‘the material’) is the property of Beijer Electronics. The holder or user has a non-exclusive right
to use the material.
The holder is not allowed to distribute the material to anyone outside his/her organization except in cases where the material is part of a
system that is supplied by the holder to his/her customer.
The material may only be used with products or software supplied by Beijer Electronics.
Beijer Electronics assumes no responsibility for any defects in the material, or for any consequences that might arise from the use of the
material.
It is the responsibility of the holder to ensure that any systems, for whatever applications, which is based on or includes the material
(whether in its entirety or in parts), meets the expected properties or functional requirements.
Beijer Electronics has no obligation to supply the holder with updated versions.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
3 (61)
Normal.dotm, 2020-09-09
3Table of Contents
1Function and area of use .......................................................................................................................................2
2About this Startup document................................................................................................................................2
3Table of Contents...................................................................................................................................................3
4BCS Tools or CODESYS.......................................................................................................................................5
BCS Tools 3.30 or newer..............................................................................................................................5
CODESYS.....................................................................................................................................................5
5X2 series Soft control with CODESYS.................................................................................................................6
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro SC (v2.1.1 Build 906) ...................6
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC (v2.0 Build 368)................................6
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro SC (v2.0 Build 775) ......................7
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC (v2.0 Build 367)................................7
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro SC (v1.5.1 Build 693)...................8
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC (v1.2.1 Build 287).............................8
Installation of CODESYS runtime X2 control (v1.4 Build 581) ...................................................................9
CODESYS device handling >= image v2.0 (b775/b367) .............................................................................9
CODESYS runtime version dependencies...................................................................................................10
Version compatibility chart X2 control/X2 marine SC/Box2 pro SC..........................................................12
Version compatibility chart X2 extreme/BoX2 extreme SC ........................................................................13
Persistent function (X2 control/extreme, BoX2 pro SC/BoX2 extreme SC)................................................13
Declaration of Persistent Variables ...........................................................................................................14
Boot application .........................................................................................................................................16
Interrupt and watchdog ..............................................................................................................................16
Performance tuning....................................................................................................................................17
Error checking and error log .....................................................................................................................19
Code transparency CODESYS vs BCS Tools .............................................................................................21
6Supported fieldbus combinations X2 series.......................................................................................................22
7EtherCAT.............................................................................................................................................................23
Installation..................................................................................................................................................23
Ethernet port mapping................................................................................................................................24
Image version ≥1.5 Build 693 with CODESYS runtime 3.5.13.30.4 or newer..........................................24
Image version 1.4 Build 581 with CODESYS runtime 3.5.10.10.16...........................................................25
Bus cycle task and I/O updating.................................................................................................................26
Output status in STOP mode ......................................................................................................................27
Performance ...............................................................................................................................................27
Limitations and recommended settings.......................................................................................................28
Error checking............................................................................................................................................29
Links ...........................................................................................................................................................29
8Modbus RTU........................................................................................................................................................30
Installation..................................................................................................................................................30
Cables.........................................................................................................................................................30
COM port mapping.....................................................................................................................................31
Bus cycle task and I/O updating.................................................................................................................32
Output status in STOP mode ......................................................................................................................33
Limitations and recommended setting........................................................................................................34
Error checking............................................................................................................................................34
Performance ...............................................................................................................................................35
Dynamic configuration and application triggers .......................................................................................35
Links ...........................................................................................................................................................35
9Modbus TCP ........................................................................................................................................................36
Installation..................................................................................................................................................36
Ethernet port mapping................................................................................................................................36
36
36
Image version ≥ 1.5.1 Build 693 with CODESYS runtime 3.5.13.30.4 or newer.......................................36
Image version 1.4 Build 581 with CODESYS runtime 3.5.10.10.16...........................................................37

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
4 (61)
Normal.dotm, 2020-09-09
Bus cycle task and I/O updating.................................................................................................................37
Output status in STOP mode ......................................................................................................................38
Performance ...............................................................................................................................................38
Limitations and recommended settings.......................................................................................................39
Communication with Modbus TCP to Modbus RTU gateways...................................................................39
Dynamic configuration and application triggers .......................................................................................39
Error checking............................................................................................................................................40
Links ...........................................................................................................................................................40
10 CANopen ..............................................................................................................................................................41
Installation..................................................................................................................................................41
Cables.........................................................................................................................................................41
CAN port mapping......................................................................................................................................44
Bus cycle task and I/O updating.................................................................................................................45
Output status in STOP mode ......................................................................................................................45
Node guarding and Heartbeat....................................................................................................................46
Performance ...............................................................................................................................................46
Limitations and recommended settings.......................................................................................................47
Error checking............................................................................................................................................48
Links ...........................................................................................................................................................48
11 project backup .....................................................................................................................................................49
CODESYS, create backup files...................................................................................................................49
CODESYS, project Archive ........................................................................................................................49
CODESYS - Source Download...................................................................................................................51
12 Performance.........................................................................................................................................................52
CPU load and tuning..................................................................................................................................52
13 Communication iX and CODESYS....................................................................................................................53
Driver .........................................................................................................................................................53
Recommended settings................................................................................................................................53
Configuration in CODESYS .......................................................................................................................54
14 iX Developer.........................................................................................................................................................56
Configuration of iX Developer ...................................................................................................................56
Rename the driver.......................................................................................................................................56
Import of variables .....................................................................................................................................57
Parameter setting and Help file for the driver, CODESYS ARTI ...............................................................58
Download iX project to iX Panel................................................................................................................59
15 About Beijer Electronics .....................................................................................................................................61
Contact us...................................................................................................................................................61

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
5 (61)
Normal.dotm, 2020-09-09
4BCS Tools or CODESYS
The following chapter describes the relation between BCS Tools and CODESYS and when to
use what.
BCS Tools 3.30 or newer
Starting from BCS Tools 3.30 this is the software platform to be used in combination with
X2/BoX2 series with embedded CODESYS control.
BCS Tools requires a minimum version in terms of image and CODESYS to be installed in the
X2/BoX2 device.
All version related functions and components are prepared and they are the only ones available
for the specific target. This means that for the BCS Tools 3.30 user following the minimun
requirements stated below there is no need to consider the specific versions.
To meet the requirements follow these links for details.
X2 Control/Marine SC/BoX2 Pro SC
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro SC (v2.0 Build 775)
X2 Extreme SC/BoX2 Extreme SC
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC (v2.0 Build 367)
BCS Tools can be downloaded here
https://smartstore.beijerelectronics.com/
CODESYS
CODESYS with correct settings according to the specifications described in this document can
still be used but it is recommended to use BCS Tools due to future enhancements, integration
and support.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
6 (61)
Normal.dotm, 2020-09-09
5X2 series Soft control with CODESYS
The following chapter describes important procedures and settings needed for a well functioning
system. Chapter 5.1 and chapter 5.2 reflects the latest released versions.
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro
SC (v2.1.1 Build 906)
At delivery of a X2/BoX2 series hardware with image version 2.1.1 build 906 or newer, the
CODESYS runtime is already installed. This can be verified by checking the welcome screen
down at the bottom left corner. This should state the installed CODESYS version (3.5.13.30.12)
bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30_12 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68971
Image loader v2.1.1 Build 906
https://www.beijerelectronics.com/en/support/Help___online?docId=68969
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC
(v2.0 Build 368)
At delivery of a X2/BoX2 Extreme SC series hardware with image version 2.0 build 368 or
newer, the CODESYS runtime is already installed. This can be verified by checking the welcome
screen down at the bottom left corner. This should state the installed CODESYS version
(3.5.13.30.7) bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30.7 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68403
Image loader v2.0 Build 368
https://www.beijerelectronics.com/en/support/Help___online?docId=68497

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
7 (61)
Normal.dotm, 2020-09-09
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro
SC (v2.0 Build 775)
At delivery of a X2/BoX2 series hardware with image version 2.0 build 775 or newer, the
CODESYS runtime is already installed. This can be verified by checking the welcome screen
down at the bottom left corner. This should state the installed CODESYS version (3.5.13.30.7)
bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30.7 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68403
Image loader v2.0 Build 775
https://www.beijerelectronics.com/en/support/Help___online?docId=68407
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC
(v2.0 Build 367)
At delivery of a X2/BoX2 Extreme SC series hardware with image version 2.0 build 367 or
newer, the CODESYS runtime is already installed. This can be verified by checking the welcome
screen down at the bottom left corner. This should state the installed CODESYS version
(3.5.13.30.7) bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
8 (61)
Normal.dotm, 2020-09-09
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30.7 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68403
Image loader v2.0 Build 367
https://www.beijerelectronics.com/en/support/Help___online?docId=68408
Installation of CODESYS runtime X2 control/X2 marine SC/BoX2 pro
SC (v1.5.1 Build 693)
At delivery of a X2/BoX2 series hardware with image version 1.5.1 build 693 or newer, the
CODESYS runtime is already installed. This can be verified by checking the welcome screen
down at the bottom left corner. This should state the installed CODESYS version (3.5.13.30.4)
bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30.4 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68234
Image loader v1.5.1 Build 693
https://www.beijerelectronics.com/en/support/Help___online?docId=68235
Installation of CODESYS runtime X2 extreme SC/BoX2 extreme SC
(v1.2.1 Build 287)
At delivery of a X2/BoX2 Extreme SC series hardware with image version 1.2.1 build 287 or
newer, the CODESYS runtime is already installed. This can be verified by checking the welcome
screen down at the bottom left corner. This should state the installed CODESYS version
(3.5.13.30.4) bundled with the image version. (Check the compatibility chart for details)
For BoX2 series the image loader must be used to check the installed CODESYS version.
The CODESYS runtime is preinstalled with the following options:
1. EtherCAT without the support of distributed clock for LAN A
2. The Persistent function is Power fail mode.
CODESYS runtime 3.5.13.30.3 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=68136
Image loader v1.2.1 Build 287
https://www.beijerelectronics.com/en/support/Help___online?docId=68135

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
9 (61)
Normal.dotm, 2020-09-09
Installation of CODESYS runtime X2 control (v1.4 Build 581)
At delivery of a X2 control panel with image version 1.4 build 581 or older, the CODESYS
runtime has to be installed by the user. The installer is provided as a zip file and must be
extracted to the root of a USB stick.
Mount the USB stick and recycle the power, the installation will start once the device has booted.
Three questions requires user interaction in order to complete the setup.
1. Confirm the install of the CODESYS runtime version
2. For the EtherCAT driver select without distributed clock
3. For persistent function select Power fail mode.
CODESYS runtime 3.5.10.10.16 and device description file(s)
https://www.beijerelectronics.com/en/support/Help___online?docId=67658
Image loader v1.4 Build 581
https://www.beijerelectronics.com/en/support/Help___online?docId=67655
CODESYS device handling >= image v2.0 (b775/b367)
With the introduction of the 2.0 release for X2 control/BoX2 pro SC and X2 extreme SC/Box2
extreme SC there is a change of how to handle the devices out of a CODESYS perspective.The
handling of different X2 models are now treated as unique devices.
Unique properties are:
-Display size
-Persistent mode: Cyclic
-Persistent mode: Power-fail
Depending on these properties the corresponding device must be selected in the project.
X2 control/X2 marine SC/X2 extreme SC/BoX2 pro SC/Box2 extreme SC are all shipped with
power-fail mode.
By default CODESYS scans for devices with the filter enabled meaning that the search result will only
contain such devices available on the network.
Disable the filter to find additional devices.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
10 (61)
Normal.dotm, 2020-09-09
If the image and CODESYS runtime are upgraded in an existing installation the device in the
CODESYS project must also be updated to correspond to the display size and installation of the
CODESYS runtime.
CODESYS runtime version dependencies
It’s important to take notice of the runtime version for the CODESYS devices in use.
Based on the runtime version there are several dependencies in terms of versions for drivers,
compile version etc. To make sure the correct versions are in use refer to the compatibility chart.
Using the wrong versions can result in errors and unwanted behaviour!
Note !
When using a CODESYS development version with a higher version than the CODESYS device
(which is ok) check the following:
When you add an object in CODESYS, for example a driver, this have to be of a certain version
according to match the Runtime (compiler) version that the device uses. There are specific
libraries that are bound to the device runtime and therefore it’s recommended to install the
matching CODESYS Engineering version to make sure that all libraries are available.
After this version has been installed it is OK to download later CODESYS versions as long as
the correct versions of compiler, drivers, libraries are used.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
11 (61)
Normal.dotm, 2020-09-09
Another approach is to use a *.projectarchive file with the supported versions and make an
extract of that to the currently installed development version.
For details regarding the installation procedure of Image and CODESYS runtime use this link.
X2 image manual MAEN205
https://www.beijerelectronics.com/en/support/Help___online?docId=67122
Note!
The image upgrade consists of two parts, the EBOOT and the OS. When upgrading with the
image loader via ethernet the EBOOT version is not upgraded therefore it is always
recommended to use the option “Make recovery SD-card” to make sure that the EBOOT
version is upgraded to the correct one.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
12 (61)
Normal.dotm, 2020-09-09
Version compatibility chart X2 control/X2 marine SC/Box2 pro SC
Image
Device
description
file
CODESYS
Engineering
*1
CODESYS
runtime
package
Compiler
COM
adapter
Ethernet
adapter
Canbus
adapter
EtherCAT
Master
Modbus
RTU
Master *2
Modbus
TCP Client
*3
CANopen
Manager
1.2 b508
3.5.10.10.1
V3.5 SP10
Patch1
3.5.10.10_5
3.5.10.10
3.4.0.0
3.5.10.0
-
3.5.10.0
3.5.10.0
3.5.10.0
1.3 b569
3.5.10.10.1
V3.5 SP10
Patch1
3.5.10.10_5
3.5.10.10
3.4.0.0
3.5.10.0
-
3.5.10.0
3.5.10.0
3.5.10.0
1.4 b581
3.5.10.10.2
V3.5 SP10
Patch1
3.5.10.10_16
3.5.10.10
3.4.0.0
3.5.10.0
-
3.5.10.0
3.5.10.0
3.5.10.0
1.5.1 b693 *5
3.5.13.30
V3.5 SP13
Patch3
3.5.13.30_4
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
2.0 b775
3.5.13.30.1
V3.5 SP13
Patch3
3.5.13.30_7
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
2.1.1 b906
3.5.13.30_12
V3.5 SP13
Patch3
3.5.13.30_12
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
*1 Use stated version or newer with the version settings as described in the chart.
*2 Modbus RTU slave is not available.
*3 Modbus Server is not available
*4 Version of configured slave (located under the Master in the project tree)
*5 First version to include X2 marine SC/BoX2 pro SC

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
13 (61)
Normal.dotm, 2020-09-09
Version compatibility chart X2 extreme/BoX2 extreme SC
Image
Device
description
file
CODESYS
Engineering
*1
CODESYS
runtime
package
Compiler
COM
adapter
Ethernet
adapter
Canbus
adapter
EtherCAT
Master
Modbus
RTU
Master *2
Modbus
TCP Client
*3
CANopen
Manager
1.2.1 b287
3.5.13.30
V3.5 SP13
Patch3
3.5.13.30_3
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
2.0 b367
3.5.13.30.1
V3.5 SP13
Patch3
3.5.13.30_7
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
2.0 b368*5
(Hotfix)
3.5.13.30.1
V3.5 SP13
Patch3
3.5.13.30_7
3.5.13.30
3.5.11.20
3.5.13.0
3.5.12.0
3.5.11.10
3.5.13.10
(Modbus
RTU Slave
device
3.5.10.30 *4)
3.5.13.0
(Modbus
TCP Slave
device
3.5.12.0
*4)
3.5.10.0
*1 Use stated version or newer with the version settings as described in the chart.
*2 Modbus RTU slave is not available.
*3 Modbus Server is not available.
*4 Version of configured slave (located under the Master in the project tree)
*5 Hotfix version due to iX download issue.
Persistent function (X2 control/extreme, BoX2 pro SC/BoX2
extreme SC)
The PLC functionality have support for storing non-volatile variables.
Those variabels can be stored dynamically in two different modes:
Power-fail mode (Default setting):
If the voltage drops below a hardware given threshold (that is, during a power loss or power dip),
the system instantly copies all persistent data defined in the PLC application from RAM into the
battery backed SRAM. They are verified and restored when the device is restarted.
Cyclic mode:
the PLC is instructed to store all retain and persistent data directly into SRAM synchronously
with every PLC cycle. This means all device types can use the whole available memory, which is
128 kiB. However, writing to the SRAM might increase the configured PLC cycle depending on
the size of used retain and persistent data, because a SRAM is naturally slower then a RAM.
This possible increase is dependent of the application and to find out about the possible increase
one would need to monitor the configured task(s) of the project.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
14 (61)
Normal.dotm, 2020-09-09
Available persistent area
To change the between Power-fail and Cyclic mode the CODESYS runtime must be reinstalled.
We recommend to install the image first and after that the CODESYS runtime with the
new setting for Persistent mode.
Declaration of Persistent Variables
Persistent variables (non-volatile memory) can ONLY be declared in a special global variables
list, which is assigned to an application. There might be only ONE such list per application.
-Highlight Application.
-Right click and select Add Object.
-Choose PersistentVariables..
The persistent variables must be declared within the VAR_GLOBAL PERSISTENT RETAIN
section.
Device
Power-fail
mode
Cyclic mode
X2 control 4, 7
32kB
128kB
X2 control 10, 12, 15
64kB
128kB
BoX2 pro SC
32kB
128kB
X2 extreme SC
64kB
128kB
BoX2 extreme SC
64kB
128kB
X2 marine 7
32kB
128kB
X2 marine 7 HB SC, 15
SC, 15 HB SC
64kB
128kB

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
15 (61)
Normal.dotm, 2020-09-09
The table below shows how the Persistent variables are affected depending on the online
command sent.
Please note that in terms of Persistent variables it is only the VAR PERSISTENT RETAIN that
is supported by the X2 series.
“-“ = values get initiated
“Cold reset” equals a reboot of the panel or from within CODESYS.
Hint!
If you declare PERSISTENT function to variables declared in other GVL:s these must be
referenced to the PersistentVars object (registered) This can be made with the function
“Declarations\Add all instance paths”
This will trigger a register function where all variables declared as PERSISTENT is
inserted in the PersistentVars object.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
16 (61)
Normal.dotm, 2020-09-09
Boot application
Boot application can be regarded as the compiled, executable code. Default setting when creating
a new project is that, when performing an Online Change, the boot application is not overwritten
automaticly but instead saved in temporary memory which will result in that the project will
“return” to previous program (=before changes) on application restart.
Following should be default setting and to make sure that the online changes is always “saved”:
-Highlight the “Application” in the “Device” and right click
-Select “properties” / “Boot application”
-Select “Create implicit boot application on Online Change”
Interrupt and watchdog
When creating a task in CODESYS they have a configured priority, the lower number the higher
priority.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
17 (61)
Normal.dotm, 2020-09-09
Priority 0 = highest
Priority 31 = lowest
Example
Priority 0 will not be interrupted by any other task priority.
Priority 0 will interrupt a task with priority 1.
The configured BusTask would typically have the highest priority.
In combination with the task priority there is a Watchdog setting for each task. This can be handy to
use in order to make sure that a specific task doesn’t take longer then the specified time to execute.
If the time to execute is longer CODESYS will generate a watchdog error and STOP.
In the example below the task will generate and exception if time to execute is longer than 200ms.
In combination with the time setting a sensivity can be set. By setting 2 means that if 2 consecutive
executions takes more than 200ms to execute a watchdog error will be generated.
Performance tuning
To have a well functional system it is important to take notice of the overall cpu load for the
CODESYS core. The CODESYS runtime is bound to Core 1 and the load on that core can be
monitored by using the system tag available in iX Developer.
The recommended maximum load is approx. between 70-75% having a load higher than that
might lead to unwanted behavior especially in combination with EtherCAT communication.
The normal reason for having a high load would be the setup of task or tasks in the application,
and/or a lot of communicating tags more than 2000, from the HMI or the amount
A general approach is to have a minimum amount of active tasks, the type of task and also the
processing time for the task.
Note!

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
18 (61)
Normal.dotm, 2020-09-09
Task of type Freewheeling is not recommended, use a Cyclic task instead with a fixed
interval.
To tune the system and create a time window for the core to perform other things, monitor the
Task Configuration to see the Average Cycle Time for each task configured. Compare the
Average Cycle Time with the configured interval for the task and check that Average Cycle Time
is not higher than 30% of the configured cycle time.
Another aspect is to consider the amount of slaves for I/O communication, it is up to the user to
gather enough knowledge of how the configuration will load the system this includes amount of
slaves, configured update rates etc. More details about recommendations can be found in the
section of each protocol supported.
The amount of communicating tags has a direct impact on the performance in terms of changing
screens, updating of screens and also the load on the controller itself. This chart represents the
recommended amount of tags depending on the model in use.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
19 (61)
Normal.dotm, 2020-09-09
Error checking and error log
For troubleshooting the hardware and the running application CODESYS has a built-in logger
which contains information about different events and errors inside the runtime system. This log
can be viewed from the CODESYS IDE and can be found when double clicking the device in
the project tree.
As an example the following application entered an Exception state due to a division by zero.
If an application enters the exception state this is indicated by the message field.
To open up the log proceed as described above or simply just double click the message field.

X2 series with embedded CODESYS control –Recommendations and limitations
SUEN00392E 2022-03
20 (61)
Normal.dotm, 2020-09-09
To find out where the exception occurred double click the row with the *SOURCEPOSITION*
information and the editor with the error should open up.
The error log can be exported as an xml file.
When contacting the support team about exception errors always include the *.projectarchive file
and an export of the log.