XC-303 MN050005 - en PDF

Manual 02/18 MN050005EN
XC300
Modular control
All proprietary names and product designations are brand names or trademarks
registered to the relevant title holders.
Break-Down Service
Please call your local representative:
http://eaton.com/moeller/aftersales
or
Hotline After Sales Service:
+49 (0) 180 5 223822 (de, en)
[email protected]
For customers in US/Canada contact:

EatonCare Customer Support Center
Call the EatonCare Support Center if you need assistance with placing an order,
stock availability or proof of shipment, expediting an existing order, emergency
shipments, product price information, returns other than warranty returns, and
information on local distributors or sales offices.
Voice: 877-ETN-CARE (386-2273) (8:00 a.m. – 6:00 p.m. EST)
After-Hours Emergency: 800-543-7038 (6:00 p.m. – 8:00 a.m. EST)
Drives Technical Resource Center
Voice: 877-ETN-CARE (386-2273) option 2, option 6
(8:00 a.m. – 5:00 p.m. Central Time U.S. [UTC-6])
email: [email protected]
www.eaton.com/drives
Original operating manual

The German-language edition of this document is the original operating manual.
Translation of the original operating manual
All editions of this document other than those in German language are translations of
the original operating manual.
1. Edition 2018, publication date 02/18
© 2018 by Eaton Industries GmbH, 53105 Bonn
Author: Thomas Hettwer

Redaction: Antje Panten-Nonnen
All rights reserved, also for the translation.

No part of this manual may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means, electronic, mechanical, photocopying,
micro-filming, recording or otherwise, without the prior written permission of
Eaton Industries GmbH, Bonn.
Subject to alteration.
Danger!
Dangerous electrical voltage!
Before commencing the installation
• Disconnect the power supply of the device. • Wherever faults in the automation system may cause
damage to persons or property, external measures must
• Ensure that devices cannot be accidentally retriggered.
be implemented to ensure a safe operating state in the
• Verify isolation from the supply. event of a fault or malfunction (for example, by means of
separate limit switches, mechanical interlocks, etc.).
• Ground and short-circuit.
• During operation, and depending on their degree of
• Cover or enclose neighbouring units that are live.
protection, variable frequency drives may have live,
• Follow the engineering instructions (IL) of the device uninsulated, moving, and/or rotating parts, as well as hot
concerned. surfaces.
• Only suitably qualified personnel in accordance with • The impermissible removal of the required cover,
EN 50110-1/-2 (VDE 0105 Part 100) may work on this device/ improper installation or incorrect operation of the motor or
system. variable frequency drive can cause the failure of the
device and serious injury and/or material damage.
• Before installation and before touching the device ensure
that you are free of electrostatic charge. • Comply with all applicable national accident prevention
regulations (e.g. BGV A3) when working with energized
• The functional earth (FE) must be connected to the
variable frequency drives.
protective earth (PE) or to the potential equalizing.
The system installer is responsible for implementing this • The electrical installation must be carried out in
connection. accordance with the relevant regulations (e.g. with regard
to cable cross sections, fuses, PE).
• Connecting cables and signal lines should be installed so
that inductive or capacitive interference do not impair the • All transport, installation, commissioning and mainte-
automation functions. nance work must only be carried out by trained personnel
(observe IEC 60364, HD 384 or DIN VDE 0100 and national
• Install automation devices and related operating elements
accident prevention regulations).
in such a way that they are well protected against uninten-
tional operation. • If applicable, systems in which variable frequency drives
are installed must be equipped with additional monitoring
• Suitable safety hardware and software measures should
and protective devices in accordance with the applicable
be implemented for the I/O connection so that a cable or
safety regulations, e.g., the German Equipment and
wire breakage on the signal side does not result in
Product Safety Act, accident prevention regulations, etc.
undefined states in the automation device.
Making changes to the variable frequency drives by using
• Ensure a reliable electrical isolation of the low voltage for the operating software is allowed.
the 24 V supply. Only use power supply units complying
• Keep all covers and doors closed during operation.
with IEC 60364-4-41 or HD 384.4.41 S2 (VDE 0100 part 410).
• When designing the machine, the user must incorporate
• Deviations of the mains voltage from the nominal value
mechanisms and measures that limit the consequences of
must not exceed the tolerance limits given in the technical
a drive controller malfunction or failure (an increase in
data, otherwise this may cause malfunction and
motor speed or the motor’s sudden stop) so as to prevent
dangerous operation.
hazards to people and property, e.g.:
• Emergency-Stop devices complying with IEC/EN 60204-1
– Additional stand-alone devices for monitoring parame-
must be effective in all operating modes of the automation
ters that are relevant to safety (speed, travel, end
devices. Unlatching the emergency switching off devices
positions, etc.)
must not cause restart.
– Electrical and non-electrical safety devices (interlocks
Eaton Industries GmbH
• Built-in devices for enclosures or cabinets must only be or mechanical locks) for mechanisms that protect the
run and operated in an installed state, desk-top devices or
Safety instructions
entire system
portable devices only when the housing is closed. – Due to the possibility of there being capacitors that are
• Measures should be taken to ensure the proper restart of still holding a charge, do not touch live device parts or
programs interrupted after a voltage dip or failure. This terminals immediately after disconnecting the variable
should not cause dangerous operating states even for a frequency drives from the supply voltage. Heed the
short time. If necessary, emergency switching off devices corresponding labels on the variable frequency drives
should be implemented.
I
Content
0 About This Manual..................................................................... 7
0.1 Target group................................................................................. 7
0.2 Change protocol ........................................................................... 8
0.3 Additional documentation ............................................................ 8
0.4 Legal Disclaimer........................................................................... 8
0.5 I/O system XN300........................................................................ 9
0.6 Writing Conventions..................................................................... 10
1 Description.................................................................................. 11
1.1 System overview ......................................................................... 11
1.2 Communication and Interfaces – Decentralized Expansion ......... 12
1.3 Intended Use................................................................................ 13
1.4 Device Overview.......................................................................... 14
1.4.1 XC-303-C32-002 ........................................................................... 14
1.4.2 XC-303-C21-001 ........................................................................... 15
1.4.3 XC-303-C11-000 ........................................................................... 15
1.5 Model code XC300....................................................................... 16
1.5.1 Device Version Number ............................................................... 16
1.6 Functionality ................................................................................. 17
1.6.1 Supply Voltage ............................................................................. 17
1.6.2 Local Inputs/Outputs.................................................................... 17
1.6.3 Processor Unit.............................................................................. 17
1.6.4 Programming Interfaces............................................................... 19
2 Installation .................................................................................. 27
2.1 Control panel layout ..................................................................... 27
2.1.1 Ventilation .................................................................................... 27
2.2 Mounting XC300 .......................................................................... 28
2.3 Uninstalling and Disassembling the XC300.................................. 31
2.4 Terminals...................................................................................... 33
2.5 Potential conditions between the components ........................... 34
2.6 Wiring in accordance with EMC requirements ............................ 35
2.6.1 Cable routing and wiring .............................................................. 36
2.6.2 Suppressor circuit for interference sources ................................. 36
2.6.3 Shielding....................................................................................... 36
2.7 Lightning Protection ..................................................................... 37
2.7.1 External lightning protection ........................................................ 37
2.7.2 Internal lightning protection ......................................................... 37
XC300 Modular control 02/18 MN050005EN www.eaton.com 1

2.8 Connecting the power supply ...................................................... 38
2.9 Connecting Local Inputs/Outputs ................................................ 39
2.9.1 Connecting the Supply Voltage for Local Outputs ....................... 39
2.9.2 Connecting Outputs..................................................................... 40
2.9.3 Suppressor circuit for inductive loads .......................................... 40
2.9.4 Connecting Inputs........................................................................ 41
2.9.5 Connecting Interrupt Inputs ......................................................... 42
2.10 Interface assignment ................................................................... 43
2.10.1 USB host 2.0................................................................................ 43
2.10.2 Ethernet ....................................................................................... 43
2.10.3 RS485 .......................................................................................... 44
2.10.4 CAN/easyNet ............................................................................... 45
3 Commissioning .......................................................................... 47
3.1 General commissioning instructions............................................ 47
3.2 Startup Behavior XC300............................................................... 47
3.3 Program execution....................................................................... 49
3.3.1 DIP Switch S1 .............................................................................. 49
3.3.2 Program Start (STOP ￫ RUN) .................................................... 50
3.3.3 Program Stop (RUN ￫ STOP) .................................................... 50
3.4 Power Off/Interruption of the Supply Voltage............................. 51
3.4.1 Testing and Commissioning (Debugging) .................................... 51
3.4.2 Forcing ......................................................................................... 52
3.4.3 Reset ........................................................................................... 53
3.5 LED Indicators.............................................................................. 54
3.6 Operating statuses when starting the XC300.............................. 56
3.7 Programs and project................................................................... 57
3.7.1 Loading Programs on the Device................................................. 57
3.7.2 Storing and Deleting a Boot Application ...................................... 58
3.8 Updating the operating system.................................................... 59
3.9 Programming in Series Production via MicroSD or USB.............. 61
4 Configuring the Controller ........................................................ 63

4.1 Task Configuration ....................................................................... 63
4.1.1 Creating a Cyclic Task .................................................................. 64
4.1.2 Create Event-type task and program start set ............................. 65
4.2 System events ............................................................................. 66
4.3 Multitasking ................................................................................. 67
4.4 Task Monitoring with a Watchdog ............................................... 70
4.5 Limit Values for Memory Usage .................................................. 73
4.6 Addressing inputs/outputs and marker ........................................ 74
4.7 Diagnostics .................................................................................. 75
2 XC300 Modular control 02/18 MN050005EN www.eaton.com

5 Establishing a Connection with a PC – XC300 ........................ 77
5.1 Searching the Network with Automatic Controller Detection...... 77
5.2 Creating a new project ................................................................. 78
5.3 Changing the IP Address on the Controller.................................. 79
6 Configuring and parametizing Inputs/Outputs....................... 81

6.1 Configuring Local Inputs/Outputs of the Device .......................... 81
6.2 Interrupt Processing..................................................................... 81
6.3 Secure Communication................................................................ 85
7 Assigning System Parameters.................................................. 87

7.1 Overview...................................................................................... 87
7.2 File InitPLC with Default Parameters ........................................... 88
7.3 Switching On the Controller with Memory Card with
File “InitPLC” Inserted................................................................. 90
7.4 File “networkconfig”.................................................................... 91
8 Expansion ................................................................................... 93
8.1 Local expansion............................................................................ 93
8.1.1 Configuring Inputs/Outputs of the Central Expansion.................. 94
8.2 Remote expansion ....................................................................... 95
9 CAN ............................................................................................. 97
9.1 Configuring and commissioning CANopen .................................. 98
9.1.1 Adding the CAN manager ............................................................ 99
9.1.2 Setting the Baud Rate via CANbus .............................................. 100
9.1.3 CAN-Gateway XN-312-GW-CAN Integrating ................................ 101
9.1.4 Attach XN300 slice modules ........................................................ 102
9.1.5 Description Files for CANopen..................................................... 104
9.1.6 Integrating libraries for CANopen communication ....................... 105
9.1.7 LEDs on the device ...................................................................... 106
10 EtherCAT..................................................................................... 107
10.1 Integrating the EtherCAT Master ................................................. 107
10.2 Configuring the EtherCAT Master................................................ 108
10.3 Searching for and Integrating EtherCAT Subscribers................... 109
10.4 Manually Integrating EtherCAT Subscribers ................................ 110
10.5 Adding SWD Subscribers............................................................. 111
10.6 Description Files for EtherCAT..................................................... 112
10.6.1 Standard XML Files ...................................................................... 112
10.6.2 Installing an XML File ................................................................... 113
10.6.3 Integrating Libraries for EtherCAT Communication ..................... 113

11 Modbus ....................................................................................... 115
11.1 Configuring Modbus TCP............................................................. 115
11.1.1 Integrating the Ethernet Adapter ................................................. 115
11.1.2 Integrating the ModbusTCP Master and Device.......................... 115
11.1.3 Integrating Libraries for Modbus TCP Communication................ 116
11.2 Configuring Modbus RTU ............................................................ 117
11.2.1 Integrating the Modbus Master ................................................... 117
11.2.2 Integrating Modbus Subscribers.................................................. 117
11.3 Integrating Libraries for Modbus RTU-Communication ............... 118
12 Remote Access to the Controller ............................................. 119

12.1 SFTP Server ................................................................................. 120
12.1.1 Accessing the Device using the SFTP Server.............................. 120
12.1.2 Changing the STFP Server Password .......................................... 121
12.1.3 Switching Off the SFTP Server .................................................... 121
13 Web-Server................................................................................ 123
13.1 Web visualization ......................................................................... 123
13.2 Web Server for XSOFT-CODESYS-3............................................ 123
14 OPC UA ....................................................................................... 127
15 Libraries, function blocks, and functions................................. 129

15.1 Using libraries .............................................................................. 130
15.2 Installing additional system libraries ............................................ 130
15.3 “EA_Network.lib” library.............................................................. 132
16 PLC Shell Commands ................................................................ 133

16.1 Accessing PLC Shell Commands................................................. 133
16.2 Overview of PLC Shell Commands.............................................. 134
16.3 Shell Commands for CPU Utilization............................................ 135
17 Malfunctions............................................................................... 137
18 Maintenance............................................................................... 139
18.1 Cleaning and maintenance........................................................... 139
18.2 Repairs ......................................................................................... 139
18.3 Storage and transport .................................................................. 139
18.4 Disposal ....................................................................................... 141

19 Appendix..................................................................................... 143
19.1 Dimensions and Weights ............................................................. 143
19.2 Approvals and National Approvals for Devices XC300 ................. 144
19.3 Technical Data.............................................................................. 145
19.3.1 General ambient conditions ......................................................... 145
19.3.2 Supply voltage to device and system bus.................................... 148
19.3.3 Power Supply to Local Inputs/Outputs ........................................ 149
19.3.4 Local inputs .................................................................................. 150
19.3.5 Local outputs................................................................................ 151
19.3.6 CAN1 and CAN2 Interface ........................................................... 152
19.3.7 RS485 interface............................................................................ 153
19.4 Glossary ....................................................................................... 154
Index............................................................................................ 155

Target group
0 About This Manual

This manual contains information about the XC300 Modular control, types:
• XC-303-C32-002
• XC-303-C21-001
• XC-303-C11-000
￫ Shorter name XC300

Where this manual refers to all types, the shorter name XC300
is used.
If only one type is meant specifically, this is explicitly stated.
Work with the up-to-date documentation for the XC300 Modular control.
The current edition of this documentation and additional literature can be
found online, ￫ section 0.3, “Additional documentation”, page 8.
￫ For up-to-date information about the XC300 Modular control

refer to the product pages:
www.eaton.eu/xc300
and the EATON online catalog.
http://www.eaton.eu/ecat
Entering “XC300” in the search field will take you directly to this
product group.
0.1 Target group

This manual is intended for electricians and automation engineers, as well as
for the individuals who are in charge of performing the electrical installation
and those who will be using the XC300 Modular control as an integrated
operating and control device in their own applications.
Specialist knowledge of electrical engineering and physics is required for
commissioning, as is well-founded knowledge of the communication inter-
faces and procedures used.
CAUTION
Installation requires qualified electrician

Change protocol
0.2 Change protocol

The following table lists major amendments.
Publication Page Keyword new modified deleted
date
02/18 First edition – – –
0.3 Additional documentation

More information on the topic can be found
in the manual:
• “XN300 slice modules”– MN050002
• “CANopen Gateway XN-312-GW-CAN”– MN050003
• Manufacturer’s documentation on the XSOFT-CODESYS-3, online help
for the individual libraries
• Documentation on the CAN subscribers used
• PLC programming with CODESYS manual, Chapter “Online functions.”
in the installation leaflet:
• IL050018ZU, XC-303-...
￫ The documents mentioned in this manual, as well as this

manual itself, can also be downloaded free of charge from the
internet in PDF format at:
http://www.eaton.eu/doc
www.eaton.eu/DE/￫ Customer Support ￫
Download Center – Documentation
Enter the document number (“05005,” for example) or
“XC300” into the Quick Search text field.
0.4 Legal Disclaimer

All the information in this manual has been prepared to the best of our know-
ledge and in accordance with the state of the art. However, this does not
exclude the possibility of there being errors or inaccuracies. We assume no
liability for the correctness and completeness of this information.
This information in particular does not contain any guarantee for the provision
of specific properties.
Do not use the XC300 Modular control before you have read and understood
this manual.
It is assumed that the user of this manual is thoroughly familiar with the
information found in the manuals for incorporating the XC300 into automa-
tion processes.

I/O system XN300
Hazards posed by the XC300 cannot be eliminated if the safety instructions

are not observed – especially if the XC300 Modular control is commissioned
and maintained by insufficiently qualified personnel and/or the XC300 is used
improperly. Eaton assumes no liability for any damages resulting from cases
such as these.
0.5 I/O system XN300

The ultra-compact XN300 slice card modular I/O system, which features a
plug-in connection system, complements the XC300 Modular control with
application-oriented functions to achieve an optimized system solution.
There are XN300 slice card modules available for power distribution, power
supply, digital and analog input/output modules, and technology modules.
￫ For up-to-date information about the I/O system XN300, refer to

the product pages:
www.eaton.eu/xn300
and for the available product range, refer to the EATON online
catalog.
Entering “XN300” in the search field will take you directly to this
product group.
All modules are described in the “XN300 slice modules”
manual.

Writing Conventions
0.6 Writing Conventions

Symbols with the following meaning are used in this manual:
▶ indicates actions to be taken.
Hazard warnings of material damages
ATTENTION
Warns about the possibility of material damage.
Hazard warnings of personal injury
CAUTION
 Warns of the possibility of hazardous situations that may pos-

sibly cause slight injury.
WARNING
 Warns of the possibility of hazardous situations that could result

in serious injury or even death.
DANGER
 Warns of hazardous situations that result in serious injury or

death.
Notes
￫ Indicates useful tips.
▶ Indicates actions to be taken.

System overview
1 Description
1.1 System overview
b Assignment based on device type

n XC-303-S1 C32 C21 C1
STOP PLC √ √ √
m a TRSa, RS458 √ √ –
S1 TRSb
SD PLC ON OFF
STOP
TC1 CAN1 √ √ –
XC-303-C32-002
Micro
SD TRSa
PRG
h TRSb
TC1
c TC2 CAN2 √ – √
SD TC2
U1
USB X1
HOST
I/Q1
i I/Q2 Equipment based on device type
ETH2 USB
I/Q3 d
I/Q4 XC-303- C32 C21 C1
X2
UL X1, X2 I/Q √ – –
k X3
-
X3 RS485 √ √ –
ETH1 RS485
X4 CAN1 √ √ –
e
X4 X5 CAN2 √ – √
j CAN 1
f
ETH0 X5 XC-303- C32 C21 C1
CAN 2 U1 USBHost √ √ –
l X6 ETH2 √ √ –
V+
0V
g ETH1 √ √ √
ETH0 √ – –
Figure 1: Structure of the XC300
a Bus connector to the I/O system XN300

for expanding the local I/O level with up to 32 XN300 I/O slice cards
b Locking tabs for attachment to the DIN rail
c S1 (assignment based on device type)
DIP switch for switching on the operating status and termination resistors
External, push-in connection level (equipment based on device type)
d X1 four interruptible input/output channels with
X2 related supply voltage I/Q1, …, I/Q4
e X3 RS485 interface
f X4, X5 two CAN interfaces for connecting standard CAN components
g X6 supply voltage
External connections
h SD slot for MicroSD memory card
i U1 USB-Host for saving process data and carrying out program updates
Ethernet interface (equipment based on device type)
j ETH2: 10/100/1000 MBit, e.g., SCADA
k ETH1: 10/100 MBit, e.g., machine network
l ETH0: 10/100 MBit, e.g., cell network, I/O network
Displays
m Marker areas for individual labels
n Status indicator LEDs under the front panel

Communication and Interfaces – Decentralized Expansion
The XC300 Modular control is Eaton’s powerful and flexible control system,
allowing machine and plant builders to achieve a slim and modern automa-
tion concept in combination with the compact I/O system XN300 and the
innovative Multi-touch display XV300.
Thanks to the large number of interfaces, the PLC is suitable for use as a
universal and flexible data node for a wide range of applications.
The integrated OPC server allows for standardized data transfer in machine-
to-machine (M2M) communications and the web server supports visuali-
zation in HTML5 format.
Up to three Ethernet interfaces with individual IP addresses facilitate network
segmentation, whereby access is protected in accordance with current
standards in communication.
The XC300 can therefore be seamlessly integrated into modern automation
architectures in line with Industry 4.0.
The local functional level of the XC300 can be flexibly scaled to include all
modules of the I/O system XN300. The result: control solutions in the most
compact of spaces with a high number of connections.
The PLC consists of the:
• Controller with power supply adapter and local inputs/outputs
￫ page 14
• I/O system XN300 ￫ Separate manual “XN300 slice modules”.
￫ To program the XC300, the programming software

XSOFT-CODESYS-3 version 3.5.9 or higher is required.
1.2 Communication and Interfaces – Decentralized Expansion

The XC300 Modular control supports decentralized expansion via fieldbus
interfaces. The following protocols are supported for communication on the
respective interface:
Protocol Interfaces
CANopen Master / Device CAN1, CAN2
easyNet Master / Device CAN1, CAN2
Modbus RTU Master / Device RS485
EtherCAT Master (1x) ETH0, ETH1, ETH2 (fieldbus)
Modbus TCP Master / Device ETH0, ETH1, ETH2 (fieldbus)
Ethernet/IP Master ETH0, ETH1, ETH2 (fieldbus)
OPC-UA/SCADA Server ETH0, ETH1, ETH2 (SSL/TLS/IPSec)
WEB - VISU HTML5 server ETH0, ETH1, ETH2 (SSL/TLS/IPSec)
Ethernet HTTP, HTTPS, DHCP (client), ETH0, ETH1, ETH2
DNS, SFTP, SSL, TLS

Intended Use
1.3 Intended Use

The XC300 Modular control is designed for use in machine and plant building
as a compact, fanless PLC with extensive functions and interfaces that
enable the implementation of modern, flexible automation concepts.
The XC300 is only approved for use in automation technology to control
machines and systems in closed spaces.
The XC300 Modular control must not be used to implement safety functions
(in the sense of protecting people and machinery).
Observe the labels on the housing of the XC300 and the approval information
and technical data.
Any other use must be discussed and agreed upon with the manufacturer in
advance.
￫ section 19.2, “Approvals and National Approvals for Devices XC300”,
page 144
￫ section 19.3, “Technical Data”, page 145
The XC300 Modular control may only be operated if it has been correctly
mounted and connected by qualified electrical specialists. The installation
must conform to the regulations governing electromagnetic compatibility
(EMC).
DANGER
 DUE TO AUTOMATED START-UP

When the XC300 is switched on, the equipment being started
up must not pose any hazards, such as the inadvertent start-up
of motors or unexpected switch-on of voltage.

Device Overview
1.4 Device Overview

The following device types are available:
• XC-303-C32-002
• XC-303-C21-001
• XC-303-C11-000
1.4.1 XC-303-C32-002
a Local inputs/outputs
S1 ON OFF b 24 V DC supply voltage for local
SD
PLC STOP ⑫ inputs/outputs
⑦ Micro
TRSa
XC-303-C32-002
PRG TRSb
SD TC1 c RS485 with data cable A, data cable B, GND
TC2
SD
d CAN1 with CAN_H, CAN_L, GND
U1 X1 ①
USB
HOST
I/Q1 e CAN2 with CAN_H, CAN_L, GND
I/Q2
⑧ I/Q3 f 24 V DC POW supply voltage

USB
I/Q4 g Slot for MicroSD
X2 ②
ETH2 UL h USB-Host 2.0 host, type A
-
X3 ③ i ETH2, 10/100/1000 MBit/s
⑨
RS485
j ETH1, 10/100 MBit/s
k ETH0, 10/100 MBit/s
ETH1 X4 ④ l DIP switch for switching on the operating
CAN 1
⑩ status and termination resistors
X5 ⑤
ETH0 CAN 2
⑪ X6
V+
⑥
0V
Figure 2: XC-303-C32-002

Device Overview
1.4.2 XC-303-C21-001
a RS485 with data cable A, data cable B, GND
b CAN1 with CAN_H, CAN_L, GND
S1 ON OFF
SD
PLC STOP ⑧ c 24 V DC POW supply voltage
④ Micro
TRSa
d Slot for MicroSD
XC-303-C21-001
PRG TRSb
SD TC1
SD e USB-Host 2.0 host, type A
U1 f ETH2, 10/100/1000 MBit/s
USB
HOST
g ETH1, 10/100 MBit/s
⑤ h DIP switch for switching on the operating
USB
ETH2
status and termination resistors
⑥ X3 ①
RS485
ETH1 X4 ②
CAN 1
⑦
X6
V+
③
0V
Figure 3: XC-303-C21-001
1.4.3 XC-303-C11-000
a CAN2 with CAN_H, CAN_L, GND
S1 ON OFF
b 24 V DC POW supply voltage
PLC STOP ⑤ c Slot for MicroSD
③ SD
Micro
XC-303-C11-000
PRG
SD d ETH1, 10/100 MBit/s
TC2
SD
e DIP switch for switching on the operating
status and termination resistors
ETH1
④
X5 ①
CAN 2
X6
V+
②
0V
Figure 4: XC-303-C11-000

Model code XC300
1.5 Model code XC300

XC - 3 0 3 - Cx x - x x x
Expansion level
000 = basic version
xxx = additional expansions
Number of CAN interfaces

Number of Ethernet interfaces
Product series 300
Product family XC
1.5.1 Device Version Number

The device version number is shown on the left side of the housing of each
XC300 Modular control. These are the first two digits of the device number.
The device version number provides useful service information about the
hardware version and the version of the operating system.

Functionality
1.6 Functionality
1.6.1 Supply Voltage

A voltage supply is provided to supply power to the processor unit.
Terminal X6 (labeled V+/0V) has a 24 V connection for the processor unit and
all of the slice card modules connected to the system bus.
If there is a voltage dip of the 24-V supply voltage (switching threshold is
approx. 10 V) then a power-down logic switches off the 5-V-supply to the
signal modules (central I/O).
1.6.2 Local Inputs/Outputs

Equipment based on device type for the XC-303-C32-002
The four digital X1 inputs/outputs can be used either as inputs or outputs and
connected with sensors or actuators.
When used as outputs Q1 to Q4, they are designed for 24 V signals and have
another separate shared supply voltage at X2 (labeled UL/–), which is galvan-
ically isolated all the way to the bus.
Outputs Q1 to Q4 can be loaded with 500 mA, a duty factor (DF) of 100 %,
and a utilization factor (g) of 100 %.
The outputs are short-circuit proof.
1.6.3 Processor Unit

Belonging to the processor unit are:
• Real-time clock (RTC) ￫ page 18
• Memory ￫ page 18
• CPU Drives ￫ page 18
• Programming Interfaces ￫ page 19

Functionality
Real-time clock (RTC)

The XC300 is equipped with a real-time clock, which can be operated from
the user program.
Possible functions are:
• Display mode for hours (12/24 hour display),
• Reading and setting of the real-time clock.
A description of the functions can be found in the manufacturer’s documen-
tation for XSOFT-CODESYS-3 on the SysLibRTC.lib library.
You can also set or query the real-time clock using the following PLC shell
commands:
• setrtc (set the real-time clock)
• getrtc (query the real-time clock)
The real-time clock continues to run for up to 10 days even if the supply
voltage fails, thanks to buffering with a memory backup capacitor.
Memory
The XC300 Modular control has a 128 MB program memory (FLASH),
512 MB working memory, and a 128 kB memory for storing non-volatile
application data (NV-RAM).
CPU Drives
The XC300 has the following drives available:
• internal
• System memory \home
• external (optional)
• MicroSD memory card \home\disk_sd
• USB-Device \home\disk_usb.
The boot application and the operating system are stored in the transaction-
safe program memory in compressed format so they are safe even if a
power failure occurs.
The boot application and relevant parts of the operating system are
“unzipped” and copied to the working memory during operation.
The retentive data is stored in the NV-RAM.
Only the real-time clock (RTC) is buffered with a capacitor. This allows it to
continue running without power for 10 days.
￫ “Transaction-safe” means that if there is a voltage dip

when a file is being processed, the file system and the
opened file are generally not destroyed.
It is possible however, that data which you have written
into the file last opened may be lost.
Figure 5 shows the interaction between the different memory systems/

drives of the XC300.

Functionality
\disk_sd MicroSD memory card

Program
memory \home
(FLASH)
\disk_usb USB-Device
Working
memory
(SDRAM)
Figure 5: XC300 memory organization
1.6.4 Programming Interfaces

CAUTION
 INTERFERENCE
The values specified in the technical data, as well as the
device’s electromagnetic compatibility (EMC), cannot be guar-
anteed if the following are used: unsuitable cables, improperly
assembled and terminated cables, and/or wiring that does not
conform to the applicable standards. Only use cables assem-
bled and terminated by professionals.
The cables being used must be assembled and terminated as
required by the port/interface description in this document.
The wiring instructions for the interface in question must be
followed when wiring the device.
Generally applicable guidelines and standards must be
observed.
CAUTION
 NON-GALVANICALLY ISOLATED INTERFACES

The device may be damaged by potential differences.
▶ The GND terminals of all bus modules must be connected.
▶ Do not connect the interface to the device or disconnect it
without first de-energizing the system.
1.6.4.1 MicroSD memory card, USB-Device

MicroSD memory card and USB-Device are used as external mass storage.
You can load the recipe data, general data and the user program onto them.
The operating system (OS) supports memory types with the FAT32 file
system.
You can transfer the operating system to the MicroSD or the USB-Device in
order to load it onto other controllers when updating the operating system
￫ page 47.

Functionality
ATTENTION
The file system of the MicroSD memory card and USB-Device is
not transaction-safe.
Make sure that all the files of the program are closed before you
insert or remove a MicroSD and/or USB-Device or turn off the
voltage.
MicroSD memory card

The SD LED lights up green when a MicroSD is inserted.
￫ A MicroSD memory card that is suitable for industrial data

storage is recommended for use, e.g., article 191087,
MicroSD memory card 2 GB with adapter.

Functionality
USB-Device
Equipment based on device type for the XC-303-C32-002 and
XC-303-C21-001
The XC300 Modular control provides the option through the USB-Host to
connect USB peripheral devices supported by the hardware and operating
system, e.g., a USB stick as an external memory.
The USB interface can also be used as a programming interface, for loading
the user program or carrying out a system update.
CAUTION
 When using commercially available peripheral devices with the

USB-Host, it is important to keep in mind that their EMC inter-
ference immunity parameters may render them unsuitable for
use in industrial environments.
CAUTION
 NON-GALVANICALLY ISOLATED INTERFACES

The device may be damaged by potential differences.
▶ Do not connect the interface to the device or disconnect it
without first de-energizing the system.
￫ Note that the USB interface has a maximum load of 100 mA.
USB-Host
The USB interface is a USB 2.0 host interface.
Version: USB 2.0 host type A, downstream plug
Figure 6: USB-Host
USB cable
• Only use standard USB 2.0 cables with a shield.
• Max. cable length: 5 m.
See also:
• Interface assignment ￫ page 43
• Technical Data ￫ page 145

Functionality
1.6.4.2 Ethernet
Communication between the XC300 Modular control and the programming
device is possible using any Ethernet interface ETH0, ETH1, or ETH2.
The Ethernet interfaces of the device provide different transfer rates:
Interface Transfer rate XC-303-C32-002 XC-303-C21-001 XC-303-C11-000
MBit/s
ETH0 10, 100 ✓ – –
ETH1 10, 100 ✓ ✓ ✓
ETH2 10, 100, 1.000 ✓ ✓ –
Use the Ethernet interfaces for programming, debugging, and for updating
the controller operating system.
All Ethernet interfaces provided by the respective device can be used for
programming in the same way.
Recommendation: Connect a PC via Ethernet
Note the following:
• Each Ethernet interface must be correctly configured.
• Two Ethernet interfaces cannot connect on the same subnet.
Version: RJ45 socket, 8-pin
1 2 3 4 5 6 7 8
Ethernet (Patch) Cable

Decisive factors when selecting the connection cable are the environmental
conditions (interference, flexibility, data transfer rate) at the location where
they are used.
• Only use standard Ethernet (patch) cables with RJ45 plugs,
category Cat-5 or higher (IEC/EN 61131-2, EN 50178).
• Maximum cable length: 100 m
If the network extends beyond that range, suitable infrastructure
components must be used.
• Observe the installation guidelines for (Ethernet) cabling set out in
ISO/IEC 11801 and EN 50173.

Functionality
CAUTION
 FORCES ON THE ETHERNET INTERFACE

Communications may be affected, and the connection’s
mechanical components may be damaged, if the Ethernet inter-
face is subjected to strong vibrations or the RJ45 plug-in con-
nection is subjected to pulling.
• Protect the RJ45 plug-in connection from strong vibrations.
• Protect the RJ45 plug-in connection from tensile forces at
the socket.
To establish communication between the XC300 Modular control and the

programming device, follow the description for your connected device.
Default Addresses
The Ethernet interfaces are delivered with the following default
IP addresses:
ETH2: 192.168.138.248
ETH1: 192.168.137.248
ETH0: 192.168.119.248
Subnet mask: 255.255.255.0
See also:

Functionality
1.6.4.3 RS485
Equipment based on device type for the XC-303-C32-002 and
XC-303-C21-001
The serial RS485 interface (X3) can be used to connect an external display
unit, for example.
The RS485 port can connect to another controller as a Modbus RTU master
or Modbus RTU device.
The RS485 interface is isolated from the system supply.
Max. possible cable lengths 100 m:
Configurable baud rate Modbus RTU Serial interface

kBaud
1.2 x –
2.4 x –
4.8 x x
9.6 x x
19.2 x x
38.4 x x
57.6 x x
115.2 x x
Version: X3 plug connector, 3-pin, push-in spring-type terminal block
Termination Resistors
To connect the termination resistors for the RS485 cable, set the two DIP
switches S1 TRSa and TRSb to the ON position.
S1 ON OFF
STOP
TRSa
TRSb
TC1
TC2
RS485 Cable
• Only use the specified connection cable pre-assembled by an electrician.
• Max. cable length: 100 m.
See also:

Functionality
1.6.4.4 CAN/easyNet
Equipment based on device type
• XC-303-C32-002 CAN1, XC-303-C32-002 CAN2
• XC-303-C21-001 CAN1
• XC-303-C11-000 CAN2
Both CAN interfaces can be operated individually as CAN masters or CAN
devices.
The CAN1 interface (X4) is galvanically isolated from the Us (X6) supply, while
the CAN2 interface (X5) is not.
The connections of the interfaces are the same. The CPU can be operated on
the CAN bus both as a network (NMT) master and as an NMT device.
The CANopen and easyNet protocol can be run in parallel by the XC300.
Version: X4 and/or X5 plug connector, 3-pin, push-in spring-type terminal
block
Bus Termination Resistors

Bus termination resistors must be used at the first and last subscriber on the
CAN bus. A termination resistor of 120 Ω can be connected via the DIP
switch for the purpose.
To connect the termination resistor for CAN1, set DIP switch S1 TC1 to the
ON position.
S1 ON OFF
STOP
TRSa
TRSb
TC1
TC2
For CAN2, set DIP switch TC2 to the ON position.
S1 ON OFF
STOP
TRSa
TRSb
TC1
TC2

Functionality
CAN/easyNet baud rate Max. cable length

50 kBaud 1000 m1),2)
100 kBaud 600 m1)
125 kBaud 500 m1)
250 kBaud 250 m1)
500 kBaud 100 m
800 kBaud 50 m
1000 kBaud 25 m
1) From a cable length of 200 m, it is a good idea to use optocouplers in the CAN subscribers
2) From a bus length of approx. 1000 m, it may be necessary to use repeaters.
If an application attempts to activate a baud rate that is not supported,

the CAN controller switches to passive mode.
Reaction of the subscriber on the CAN bus
Monitoring subscribers/bus: CAN telegrams are sent and received directly
from the user program. An interruption on the CAN bus will only be detected
if the respective CAN subscriber is monitored by the PLC (node-guarding
function).
Start/Stop behavior: can be configured through the application.
• Reset to default value (usually 0).
• Current value is retained (user-specific)
Switch on voltage:
The order in which you switch on the power supply to the individual CAN
subscribers has no effect on how the CAN-bus functions. Depending on the
parameters set, the controller “waits” for subscribers that are not present or
starts them when the subscriber is connected to the CAN net.
Communication with CAN subscribers:
Communication with the CAN subscribers and their configuration are
described in the following documents:
• Manufacturer’s documentation XSOFT-CODESYS-3, online help
library description: CANUser.lib/CANUser_Master.lib
• Fieldbus support -> CAN-based fieldbuses
• CANopen -> CANopen Manager (master)
• Documentation on the CAN subscribers to be used
Data exchange on the CAN bus is indicated by a green flashing LED next to
the assigned X4 or X5 plug connectors. ￫ figure 33, page 54
CAN Connection Cable
• Only use a connection cable that meets the requirements set out in
ISO 11898.
• The maximum cable length is determined by the baud rate.
See also:

Control panel layout
2 Installation
CAUTION
DANGER OF ELECTRIC SHOCK!
 All (un)installation work must be carried out with the entire

system in a de-energized state.
Observe the safety rules set out in DIN VDE 0105:
• De-energize and isolate the system.
• Secure devices from inadvertently being switched on again.
• Ensure the installation is de-energized at all poles.
• Grounding and short-circuiting.
• Cover or enclose neighboring units that are live.
2.1 Control panel layout

The layout of the components inside the control panel is a major factor for
achieving interference-free functioning of the plant or machinery.
Ensure that power and control components are separated in the layout
during the planning, design, and implementation phases.
Power components include:
• Contactors
• Coupling/interfacing components,
• Transformers,
• Variable frequency drives,
• Current converters.
In order to effectively exclude any electromagnetic interference, it is advis-
able to divide the system into sections, according to their power and inter-
ference levels. In small control panels it is often enough to provide a sheet
steel dividing wall, to reduce interference factors.
2.1.1 Ventilation
In the project engineering phase, ensure that there is sufficient ventilation for
the XC300 Modular control.
In order to ensure that the maximum operating ambient temperature will not
be exceeded, make sure that there is enough clearance between the system
block's vents and any neighboring components, as well as between the
vents and the control panel’s back plate.
Maintain a minimum clearance of 50 mm from passive components.
If the adjacent components are active elements (e.g., power supplies,
transformers) a minimum clearance of 75 mm must be observed.

Mounting XC300
2.2 Mounting XC300

The XC300 is only mounted horizontally on a DIN rail (TS 35) in accordance
with EN/IEC 60715.
Observe the minimum clearances for ventilation.
Expand the XC300 Modular control by the required XN300 slice modules into
one system block before installation.
Ensure the following when installing the device in a control cabinet, installa-
tion distribution unit, or housing:
• The connections for the voltage supply and terminals are protected from
direct contact during operation.
• The DIN rail establishes a conductive connection to the control panel’s
back plate.
• The entire system block is mounted on the rail and secured by closing
the locking tabs.
￫ Detailed information on mounting the XN300 slice modules can

be found in the “XN300 slice modules” manual.
c
a
b
b
a
Figure 7: Mounting the XC300 as a system block
a b c ϑ
30 mm (1.18”) 30 mm (1.18”) 100 mm (3.94”) ≦ 55°C (≦ 131°F)

Mounting XC300
To mount the system block, follow the steps below:

▶ The XC300 Modular control takes the first position on the left in the
system block.
▶ Disengage the locking tabs on the sides of the XN300 slice modules by
pulling on the front cover (blue).
Ensure that all locking tabs (blue) are on the front so they catch the
inserted slice card. The locking function of the front cover helps with
this.
￫ The front cover of the XC300 Modular control is secure and

cannot be loosened.
▶ Insert one XN300 slice module each from the right in such a way that the
locking tabs engage the guide.
1
2
Figure 8: Assembling the XC300 and XN300 modules into one system block
▶ Grab the front cover from the top and bottom and push it back toward
the XN300 slice module so that the modules lock solidly into place with
each other.
Figure 9: Locking the system block in place

Mounting XC300
▶ Repeat these steps until all XN300 slice modules are combined with the
controller to form one system block.
▶ Pull the locking tabs up on the back of the XC300 Modular control and all
XN300 slice moduless. Use a screwdriver as an aid.
Figure 10: Securing the system block on the DIN-rail
▶ Tilt the system block forward and place it against the DIN-rail’s bottom
edge in an inclined position.
Figure 11: Placing the system block against the bottom edge of the DIN-rail
▶ Push the system block over the DIN-rail’s top edge.

▶ Secure the system block.
Press down the locking tabs on the back of the XC300 Modular control
and all XN300 slice moduless. Use a screwdriver as an aid.

Uninstalling and Disassembling the XC300
Figure 12: Locking the system block into place on the DIN-rail
▶ Check to make sure that the system block is solidly mounted.
2.3 Uninstalling and Disassembling the XC300

▶ De-energize the installation.
Observe the safety rules set out in DIN VDE 0105:
▶ Use a screwdriver, for example, to press the release mechanism in order
to disengage all contacts.
▶ Remove all plug connectors from the XC300 Modular control and the
XN300 slice modules.
To disassemble the system block, proceed as follows:
▶ Pull the locking tabs up on the back of the XC300 and the XN300 slice
modules. Use a screwdriver as an aid.
Figure 13: Loosening the system block fastening
▶ Tilt the system block forward, then pull the block, from its bottom edge,
away from the DIN-rail.

Uninstalling and Disassembling the XC300
Figure 14: Placing the system block against the bottom edge of the DIN-rail
▶ Unlock the locking tabs between the modules by pulling on the front

cover (blue).
￫ The front cover’s stay-put function will indicate that the locking
tabs have been unlocked. The front cover of the XC300 Modular
control is secure and cannot be loosened.
Figure 15: Unlocking the front cover

▶ When the locking tabs are unlocked, you can separate the modules from
each other.
Figure 16: Disassembling the system block

Terminals
2.4 Terminals
Plug connector
X1 – Xn: The plug connectors with push-in spring-type terminals are supplied
with the XC300 Modular control.
The cable, which is fitted with ferrules, is pushed into the corresponding
contact and locked into place.
In order to release the conductor, simply press on the release mechanism,
e.g., with a screwdriver, to pull out the cable from the corresponding contact.
Table 1: Connection specifications

Cable cross-sectional areas XC300
10 mm (0.39”) Solid mm2 0.2 - 1.5
10 mm (0.39”) Flexible with mm2 0.2 - 1.5

uninsulated ferrule
10 mm (0.39”) Flexible with mm2 0.2 - 0.75

insulated ferrule
d ⌀d
Ferrule d mm ≦ 2.8
AWG 24 – 16
Stripping length mm 10

Potential conditions between the components
2.5 Potential conditions between the components

The XC300 Modular control establishes a connection between the protective
ground and the DIN rail via a contact point. All ground connections for the
supply voltages are connected to the protective ground. One exception to
this is the supply voltage for the local inputs and outputs UL.
Common
• 0V
• 
XC300 Systembus
V+ UBP_24 V +24 V DC
X6
0V XN-322 XN-322
CPU-System GND
n=1 n ≦ 32
UBP_5 V +5 V DC
GND
GND GND
Figure 17: Potential relationships XC300 Modular control with I/O system XN300
XC300 I/Q 1
... X1
I/Q 4
IO UL 24 V DC X2
GNDL
X3
RS485 X4
CAN1
GNDCAN
X6 V+
0V
CPU-System Systembus
ETHO
ETH1
CAN2 X5
ETH2
GND GND
Figure 18: Potential Relationships XC300
The galvanic isolation of the Ethernet interfaces is listed in the appendix,

see Chapter “Appendix”, ￫ section “Galvanic isolation ETH0, ETH1, ETH2
from”, page 146.

Wiring in accordance with EMC requirements
2.6 Wiring in accordance with EMC requirements

Undesired faults can occur on the field bus and the analog inputs due to elec-
tromagnetic interference. This can be minimized beforehand by the imple-
mentation of suitable EMC-measures.
These include:
• EMC-conformant system configuration,
• Routing all analog input and field bus cables in a way that meets
EMC requirements,
• Measures designed to reduce potential differences,
• The correct installation of the fieldbus system
(cable, connection of the bus connectors, etc.),
• Using shielding
For the DIN rail
FM 4/TS 35
(Weidmüller)
M4
ZB4-102-KS1
Figure 19: Field bus shielded by using a shield
The XC300 Modular control has a protective ground on the back.
Figure 20: Side view XC300

a Functional earth

Wiring in accordance with EMC requirements
2.6.1 Cable routing and wiring

Cables are divided into the following categories:
• Power cables (e.g., cables that carry high currents, or cables to
converters, contactors or solenoid valves),
• Control and signal cables (e.g., digital input cables),
• Measurement and signal cables (e.g., fieldbus cables),
￫ Always route power cables, control cables, and signal cables as

far apart as possible. This avoids capacitive and inductive
coupling.
If separate cable routing is not possible, then the first priority
must be to shield the cable responsible for the interference.
Take care to implement proper cable routing both inside and outside the
control panel, to keep interference as low as possible:
▶ Avoid parallel routing of sections of cable in different power categories.
▶ As a basis rule, keep AC cable separated from DC cables.
▶ Keep to the following minimum clearance:
• at least 10 cm between power cables and signal cables;
• at least 30 cm between power cables and data or analog cables.
▶ When routing cables, make sure that the outgoing and return leads of a
circuit pair are routed together. The opposing currents on this cable pair
cause the sum of all currents to equal zero. The generated electromag-
netic fields cancel each other out.
2.6.2 Suppressor circuit for interference sources

▶ Connect all suppressor circuits as close to the source of interference
(contactors, relays, solenoids) as possible.
￫ Switched inductors should always have suppressor

circuitry fitted.
2.6.3 Shielding
▶ Use shielded cables for the connections to the data interfaces.
The general rule is:
the lower the coupling impedance, the better the shielding effect.

Lightning Protection
2.7 Lightning Protection
2.7.1 External lightning protection

All cables between buildings must be shielded. Metal conduits are recom-
mended for use here. Fit signal cables with overvoltage protection, such as
varistors or other surge arresters. Implement these measures ideally where
the cable enters the building and at least at the control panel.
2.7.2 Internal lightning protection

Internal lightning protection covers all measures to reduce the effects of a
lightning strike and the resulting electrical and magnetic fields on metallic
installations and electrical plants. These measures are:
• Potential equalizing/grounding,
• Shielding,
• Using surge protective devices.

Connecting the power supply
2.8 Connecting the power supply

DANGER
 The supply voltage of the XC300 Modular control must be

implemented as a SELV power adapter in safety-relevant appli-
cations.
The system bus is supplied via the XC300 Modular control with 5 V DC/1.6 A
and 24 V DC/1.6 A. The supply voltage for system bus communication with
the XN300 slice modules is provided via the 5 V on the system bus of the
XC300 Modular control.
The system bus also provides a 24 V DC supply voltage for internal power to
the XN300 slice modules. Modules with high energy requirements have an
additional power supply. Some XN300 slice modules need an external supply
of 24 V DC.
￫ Information on this can be found in the “XN300 slice modules”

manual.
The supply voltage is reverse polarity protected.

Ue
0V
Ie
F1
X6
3 mm (0.12”)
V+
0V
Ue = 24 V DC
(18 - 30 V DC SELV)
Ie ≦ 2,8 A
Figure 21: Connecting the power supply

Connecting Local Inputs/Outputs
2.9 Connecting Local Inputs/Outputs

The digital inputs/outputs at X1 are configured as inputs by default.
This configuration can be changed in the corresponding dialog of the
XSOFT-CODESYS-3, see ￫ section 6.1 “Configuring Local Inputs/Outputs
of the Device”, page 81.
2.9.1 Connecting the Supply Voltage for Local Outputs

UL
0V
IL
F1
X2
3 mm (0.12”)
UL
UL = 24 V DC
(18 - 30 V DC SELV)
IL ≦ 2 A
Figure 22: Supply voltage for outputs Q1 – Q4
The cable cross-section of the +24 V supply voltage for the inputs/outputs
must be designed for the maximum total current of all outputs.

2.9.2 Connecting Outputs

Connect the supply voltage at X2 for outputs Q1 – Q4.
A maximum current of 0.5 A is permitted per output. The maximum total cur-
rent for all four outputs is 2 A. The outputs are short-circuit-proof for 24 V DC
and GND.
If a short circuit or overload occurs at one of the digital outputs Q1 – Q4,
the outputs switch off. If the short circuit or overload is corrected, the output
automatically switches back on.
One LED is assigned to each output. A switched (active) output is indicated
by the LED lighting up green.
Connect the outputs to a connection cable measuring max. 30 m long with-
out a shield.
24 V
0V
PE
X1
 Q1
Q2
Q3
Q4
RL
X2UL
_
Figure 23: Connecting local outputs on the controller
￫ Wiring examples can be found in the “XN300 Slice Modules”

manual.
2.9.3 Suppressor circuit for inductive loads

High induced voltages may be produced when inductive loads are switched
off.
In order to prevent system malfunctions caused by voltage peaks (e.g., cou-
pling on analog cables), it is recommended to use a suppressor circuit
(RC suppressors or flyback diodes) directly on inductive loads.

2.9.4 Connecting Inputs

XC300 has four inputs with a +24 V level for reading in signal statuses “0”
and “1”. The modules feature input filters designed to suppress glitches on
the corresponding signal cables.
Inputs I1 to I4 can be configured as interrupt inputs.
Connect the inputs to a shielded connection cable measuring max. 30 m
long.
One LED is assigned to each input for the purposes of indicating the current
status of the input in question.
The logical state of the process image does not affect the status indication.
The status is indicated even if the controller is in RESET mode.
24 V
0V
PE
X1
 I1
I2
I3
I4
X2UL
Figure 24: Connecting local digital inputs

2.9.5 Connecting Interrupt Inputs

Inputs I1 to I4 can be used as interrupt inputs. The interrupts can be trig-
gered with a rising or falling edge or with an edge changeover.
The inputs must be configured for this in the parameter dialog of the
XSOFT-CODESYS-3.
24 V
0V
PE
X1
 I1
I2
I3
1
I4
X6
V+
0V
24 VI
0 VI
Figure 25: Interrupt input connections
The statuses at the terminals are registered in the controller with an input
delay of < 300 μs.
V
30
25
20
15
13
10
6.7
5
Figure 26: Switching thresholds for interrupts
See also:
• Time requirement at the interrupt inputs: Technical Data ￫ page 145

Interface assignment
2.10 Interface assignment
2.10.1 USB host 2.0
￫ Note that the USB interface has a maximum load of 100 mA.
The output voltage is protected against overload.
Table 2: USB interface assignment

USB host type A PIN Signal
1 +5 V H
2 USB–
1 2 3 4 3 USB+
4 GND
See also:
• Functionality ￫ page 17
2.10.2 Ethernet
Table 3: Ethernet interface assignment
RJ45 socket PIN Ethernet 10/100 MBit Ethernet 1000 MBit
8 – BI–_D4
1 2 3 4 5 6 7 8 7 – BI+_D4
6 Rx– Rx–_D2
5 – BI–_D3
4 – BI+_D3
3 Rx+ Rx+_D2
2 Tx– Tx–_D1
1 Tx+ Tx+_D1
See also:

2.10.3 RS485
Equipment based on device type for:
• XC-303-C32-002
• XC-303-C21-001
Table 4: RS485 interface assignment

l
Plug connector X3 RS485

1 Data cable A
1 2 Data cable B
2 3 GND RS485
3
Connecting the Termination Resistor

To connect the termination resistors for the RS485 cable, set the two DIP
switches S1 TRSa and TRSb to the ON position.
+5 V
390 Ω
S1 ON OFF S1 X3
STOP TRSb RS485 b
TRSa
TRSb
TC1
220 Ω
TC2
TRSa RS485 a
390 Ω
GND
Figure 27: Connecting the termination resistors for the RS485 interface
See also:

2.10.4 CAN/easyNet
Equipment based on device type
• XC-303-C32-002 CAN1, XC-303-C32-002 CAN2
• XC-303-C21-001 CAN1
• XC-303-C11-000 CAN2
Table 5: CAN/easyNet interface assignment

Plug connector X4, X5 CAN easyNet
1 CAN_H ECAN_H
1
2 2 CAN_L ECAN_L
3
3 GND CAN GND CAN
Connecting the Bus Termination Resistors

Bus termination resistors must be used at the first and last subscriber on the
CAN bus. A termination resistor of 120 Ω can be connected via the DIP
switch for the purpose.
To connect the termination resistor for CAN1, set DIP switch S1 TC1 to the
ON position.
S1 ON OFF S1 ON OFF
STOP STOP
TRSa TRSa
TRSb TRSb
TC1 TC1
TC2 TC2
For CAN2, set DIP switch TC2 to the ON position.
XC-303-... XC-303-... XC-303-...
S1 X4/X5 S1 X4/X5 S1 X4/X5

TC1/TC2 CAN_H TC1/TC2 CAN_H TC1/TC2
R R R
GND_L GND_L
GND GND
Figure 28: Connecting the termination resistors for the CAN interfaces (CAN1 or CAN2)
See also:


General commissioning instructions
3 Commissioning
The XC300 Modular control is commissioned in the system block together
with the XN300 slice moduless.
￫ Further information can be found in the “XN300 slice modules”

manual.
3.1 General commissioning instructions

The signals received by analog modules are very small in comparison to
digital signals. In order to ensure that these modules work properly, it is
absolutely necessary to route all cables carefully:
• The mounting rail (DIN rail) must have a proper ground connection.
• The cables used to connect to the analog signal sources must be as
short as possible and must not be routed parallel to digital signal cables.
• Analog signal cables must be shielded.
• The shielding must be terminated at a shielding bus.
• Do not route the input cables parallel to load circuits.
• Suppressor circuit for all contactor coils
(RC suppressors or flyback diodes)
3.2 Startup Behavior XC300

To update the operating system/user program, the drives are checked for the
most up-to-date versions and then copied into the internal memory.
The following flow diagrams show which program is used. The diagrams also
show the update process for the operating system (OS) using the MicroSD
memory card or USB-Host.
Once the power is restored, only the boot application saved in the XC300
Modular control will be started.

Startup Behavior XC300
Power ON
Start no
yes no Update and reboot

Several OS yes Determine newest version Version
OS on MicroSD Back up configuration
on MicroSD? MicroSD= “\home“?
(IP address, COM, user program)
no yes
CONTINUE
yes
yes no Update and reboot

Several OS yes Determine newest version Version
OS on USB? Back up configuration
on USB? USB = “\home“?
CIP/COM/user program
no
no
CONTINUE
Note:
yes If MicroSD memory card and USB-Device are both inserted,
User program Copy the user program to
on MicroSD? “\home” the MicroSD takes priority.
In file InitPLC the slot for the MicroSD is queried first.
no The update process for the operating system and/or user
yes program can be blocked via entries in file “\home\InitPlc”.
User program Copy the user program to
on USB? “\home”
no
CONTINUE
yes
File networkconfig Adoption of
on MicroSD? configuration in XC300
network settings
no
File networkconfig Adoption of

USB-Host configuration in XC300
network settings
no
Start of PLC
Figure 29: Startup sequence XC300 with MicroSD memory card and USB-Host

Program execution
Load retentive data
Startup behavior? STOP
Note:
Cold START/ The startup behavior of the XC300 is
warm START configured in file “\home\InitPlc.”
RUN/STOP no
switch in RUN?
yes
RUN STOP
a section „Program execution“
3.3 Program execution

The program execution is influenced by the position of DIP switch 1.
3.3.1 DIP Switch S1

DIP switch STOP switches the CPU operating status between ON and OFF.
S1 ON OFF S1 ON OFF
STOP STOP PLC stops PLC runs
TRSa Termination
TRSb
TC1 TASa,TASb X3 (RS485) –
TC2 TC1 X4 (CAN1) –
TC2 X5 (CAN2) –
ON OFF ON OFF ON OFF
STOP 1 STOP 1 STOP 1
TRSa 2 TRSa 2 2
TRSb 3 TRSb 3 3
TC1 4 TC1 4 4
TC2 5 5 TC2 5
XC-303-C32-002 XC-303-C21-001 XC-303-C11-000

Figure 30: DIP switch S1 version (based on device type)

Program execution
3.3.2 Program Start (STOP ￫ RUN)

You have the following possibilities to start the program:
Program exists in main memory Program should be loaded
Requirement • CPU in STOP • CPU in STOP

• STOP switch to ON • STOP switch to OFF
Action • Set STOP switch to OFF position • Load program
• In online operation, issue the “Start”
command.
Result for all CPU in RUN CPU in RUN
variables Values are retained at the start Initial values are activated.
3.3.3 Program Stop (RUN ￫ STOP)

A change of the STOP DIP switch to the ON position leads the CPU to the
STOP state after completion of the program cycle (ending of all active tasks).
What should happen when the CPU is in the STOP state is defined in the
XSOFT-CODESYS-3 Device tab, PLC settings.
Defaults:
• In the “Always update variables” field: “Disabled (only update when
used in a task)”
• In the “Behavior of outputs in STOP” field: “Retain current values”
With these settings, the output values used in the I/O tasks are retained
when the tasks are completed.
For test and simulation purposes, the “Always update variables” field should
be set to “Enabled 1 (use bus cycle when not used in any task).”
This is the only setting that ensures that the display of all inputs and outputs
is up to date during the simulation.
You can stop the program in one of two ways:
• In online operation, issue the STOP command.
• Set the STOP DIP switch to the ON position.

Power Off/Interruption of the Supply Voltage
3.4 Power Off/Interruption of the Supply Voltage

When the program is running, powering off or interrupting the (CPU) power
supply will cause the program cycle or all tasks to be aborted immediately.
The data may no longer be consistent in some cases.
All outputs used in the I/O tasks are set to 0 or switched off. The behavior of
retentive variables in shown in can be seen in ￫ table 7.
The remaining program cycle will not be completed when power is recon-
nected!
If the consistency of the data is absolutely necessary for an application, other
measures are required, such as the use of a uninterruptible power supply
with battery backup. The PLC is started as shown in ￫ figure 34 and
￫ figure 29.
Table 6: Behavior of the variables after a program start

Behavior of the variables after …
Variable type Cold start Warm start
Non-retentive Activation of initial values Activation of initial values

Retain Persistent Values remain in memory Values remain in memory
CPU operating state display

The operating status of the CPU is indicated by the LEDs under the front PLC
and PRG:
CPU status PLC LED

Green Red
RUN On Off
STOP Flashing Off
NOT READY Off On
If the runtime system starts up incorrectly, the status NOT READY is sig-
naled by the PLC LEDs. The CPU remains in STOP state. The CPU can be
restarted once the fault is corrected; see also ￫ section 3.5, “LED Indica-
tors”, page 54.
3.4.1 Testing and Commissioning (Debugging)

The XC300 Modular control supports the following testing and commission-
ing features:
• Breakpoint/Single step mode,
• Single cycle mode,
• Forcing,
• Online modification, ￫ PLC programming with CODESYS manual,
chapter “Online Functions.”

Breakpoint/single-step mode
Breakpoints can be set within the application program. If an instruction has a
breakpoint attached, then the program will halt at this point. The following
instructions can be executed in single-step mode. Task monitoring is deacti-
vated.
ATTENTION
At this point, any set outputs will remain set.
Single cycle mode

In single-cycle operation, one program cycle is performed in real time.
The outputs are enabled during the cycle. At the end of the cycle, the output
images are cancelled and the outputs are switched off. Task monitoring is
active.
3.4.2 Forcing
All variables of the user program can be preset.
A local output is only forced if the corresponding variable is forced and the
CPU is in the RUN state.
Status Indication
The inputs/outputs are to be referenced in order to visualize the states of the
configured inputs/outputs in an interval controlled task in the PLC configura-
tor. The following syntax is sufficient in the ST programming language in
order to be able to display individual I/O bits.
Example:
%IB0; (referencing of inputs I0.0 – I0.7)
%QB0; (referencing of outputs Q0.0 – Q0.7)
in the application list (AWL):

LD %IB0
ST Default byte
LD Default byte
ST %QB0

3.4.3 Reset
There are three different types of Reset commands:
• Reset-Warm,
• Reset-Cold,
• Reset-Origin.
￫ table 7: The commands also affect the state of the CPU: shows the com-
mands to use for initializing a retentive variable range. The commands also
affect the state of the CPU.
Table 7: Behavior of the program and variables after a reset

Reset command
Variable type Reset-Warm Reset-Cold Reset-Origin1)
Non-retentive Activation of initial values Activation of initial values Activation of initial values
Retain Persistent Values remain in memory Values remain in memory
Program paused; paused; deleted; controller in NOT
then restart then restart READY status;
PRG LED goes out;
then reload program on
the device and restart
1) After “Reset-Origin” the program must be reloaded on the XC300. In online operation,
the “Start” command can now be issued.
￫ More information can be found in the XSOFT-CODESYS-3

online help using the search term “RETAIN.”

LED Indicators
3.5 LED Indicators

The status indicator LEDs under the front panel indicate the signal status of
the XC300 Modular control, the interfaces, and the inputs and outputs.
a LED PLC RuntimeSystem loaded (green)/
communication with programming system active (green flashing)
PLC
① RUN (green)/STOP (green flashing)/ERROR (red)
SD
Micro
SD
PRG ② b LED PRG (red)/No Error(green)
SD
U1
USB
③ c LED MicroSD found (green/–)
HOST
④ d LED USB active (green/–)

USB
Figure 31: Indicators in example XC-303-C32-002
ETH2 ⑤ e LED Ethernet2 Activity (green)

f LED Ethernet2 Activity ETH2 [10/100] Mbps (orange) /1000 Mbps (green)
⑥
g LED Ethernet1 Activity (green)
ETH1 ⑦ h LED Ethernet1 Activity ETH1 [10/100] Mbps (orange)
⑧ i LED Ethernet0 Activity (green)
ETH0
⑨ j LED Ethernet0 Activity ETH0 [10/100] Mbps (orange)
I/Q1
X1 k LED Q1–Q4 (green)
I/Q2
I/Q3 ⑪ l LED 24 V found UL (green)
I/Q4
X2 m LED RS485 connected (green/red)

UL ⑫
X3
-
n LED CAN1 connected (green/red) flashes when data is being exchanged
⑬
RS485 (Rx + Tx)
X4
⑭ o LED CAN2 connected (green/red) flashes when data is being exchanged
CAN 1
(Rx + Tx)
X5
CAN 2
⑮ p LED 24 V DC found V+ (green)
X6
V+
0V
⑯

LED Indicators
Table 8: Status LED indicators

Status LED Description
red green
PLC – – RuntimeSystem not started
• No power supply at X6
– flashing Communication
– ON PLC RuntimeSystem started
ON – Error in RuntimeSystem
• Flash error
• Error in checksum
• SSL connection could not be started
Remedy: Inspect log file
ON ON RuntimeSystem is started and has an error.
PRG – – No application found on device
– ON Application running
flashing Communication (green flashing)
ON flashing Application is stopping, program has error
e.g., because
• Faulty access to memory
• Task interval time > watchdog time
– flashing Application is stopping
SD – No MicroSD memory card found
ON MicroSD memory card found
USB – – No USB-Host found
– ON USB-Host inserted
RS485 – –
– ON Communication channel opened
– flashing Bus activity
CAN1 – – No bus activity
CAN2
– flashing Bus activity OK (CAN), FLASH for each telegram
ON – Bus error
flashing flashing WARNING
orange green
ETH0, ETH1, ETH2 – – No active connection found
– ON Active connection found
flashing ON Active connection and data is being received or sent
Ethernet Activity – – Ethernet communication/link status
– ON
ON –
ON ON

Operating statuses when starting the XC300

– Green
Q1 – Q4 – – Input has LOW signal
The logical state of the process image does not affect the status
indication; the status is indicated even if the controller is in RESET
mode.
– ON Input has HIGH signal
POW – No power supply at X6
ON 24 V DC power supply found for device at X6
UL at Q1 – Q4 – No power supply
ON Power supply present
1) flashing: The flashing frequency may differ based on the transfer rate on the bus.
When large amounts of data are being exchanged the flashing LED may look like it is constantly on.
3.6 Operating statuses when starting the XC300

The operating statuses are indicated by PLC and PRG.

Programs and project
3.7 Programs and project
3.7.1 Loading Programs on the Device

You must log on in order to load recently created or modified programs on
the device. The question “Load the new program?” will appear. The load
operation will start once this prompt has been confirmed.
￫ Please note that the “Retain” variables are initialized during the
load process, but the “PERSISTENT” variables retain their
value.
In order to safely store the program, a boot application must be generated by

the user program. With the “Create boot application” command the program
is loaded from the PC into the system memory and saved as a zero-voltage
protected boot application.
The following steps are necessary in order to create a boot application:
▶ Change over to the “Online” folder.
▶ Select the “Login” command.
▶ Select the “Create boot application” command.
Alternatively, XSOFT-CODESYS-3 can be configured so that a boot applica-
tion is automatically created when the user program is downloaded. To cre-
ate a boot application automatically during download, proceed as follows:
▶ In the browser, select “Application.”
▶ In the context menu, select the “Properties” command.
▶ Select the “Boot application” tab.
▶ Enable the option “Create implicit boot application on download” by
activating the checkbox.

Programs and project
3.7.2 Storing and Deleting a Boot Application
Storing a Boot Application on MicroSD memory card

▶ Ensure that there is communication with the XC300 device.
▶ Ensure that the boot application has been converted without errors.
▶ Ensure that the MicroSD card is inserted into the device.
▶ Double-click on the device in the Explorer, e.g., “Device (XC-303),”
go to the “Device” tab, and select “PLC Shell.”
▶ Enter the command copyprojtosd in the command line.
A directory “XC303” with subfolder “project” is created for the boot applica-
tion. The boot application is stored in this subfolder under the name <Appli-
cation name>.app. For example: “Application.app”<Application name> refers
to the application in the Explorer. A file <Application name>.crc is also cre-
ated.
The boot application is stored on the MicroSD memory card in the specified
folder structure.
You can use the PLC shell command copyprojtosd to copy the boot applica-
tion (e.g., for a backup copy) or change the name of the file. In the XSOFT-
CODESYS-3 software, however, only the boot application with the name
<Application name>.app is active.
Storing a Boot Application on USB-Device
▶ Ensure that there is communication with the XC300 device.
▶ Ensure that the boot application has been converted without errors.
▶ Ensure that a USB-Device is inserted into the USB-Host.
▶ Double-click on the device in the configuration tree diagram, e.g.,
“Device (XC303),” go to the “Device” tab, and select “PLC Shell.”
▶ Enter the command copyprojtousb in the command line.
A directory XC303 with subfolder project is created for the boot application.
The boot application is stored in this subfolder under the name <Application
name>.app. For example: “Application.app”<Application name> refers to the
application in the Explorer. A file <Application name>.crc is also created.
The boot application is stored on the USB-Device in the specified folder
structure.
You can use the PLC shell command copyprojtousb to copy the boot applica-
tion (e.g., for a backup copy) or change the name of the file. In the XSOFT-
CODESYS-3 software, however, only the boot application with the name
<Application name>.app is active.
Deleting a Boot Application on MicroSD
Click on folder “Device ￫ PLC Shell” and for the XC300, enter command
remprojfromsd .
Deleting a Boot Application on USB-Device
Click on folder “Device ￫ PLC Shell” and for the XC300, enter command
remprojfromusb .

Updating the operating system
3.8 Updating the operating system

With the XC300 it is possible to replace the operating system with the latest
version. Eaton provides the most up-to-date operating system version online:
http://www.eaton.eu/XC300 ￫ Software
￫ If you transfer a current operating system to an older hardware

version, it is possible that not all functions of the operating sys-
tem will be supported by the hardware.
￫ When an operating system is imported into the controller, the

existing operating system will be overwritten.
￫ Note the information in file

XC303 Firmware_Release_Notes_DE.txt.
The operating system of the XC300 is updated within the

XSOFT-CODESYS-3 programming system.
Procedure:
▶ Establish a connection via the Ethernet interface of the PC with the
XC300.
￫ chapter 5, “Establishing a Connection with a PC – XC300”, page 77.
▶ In the XSOFT-CODESYS-3, go to the “Device” window and activate the
“Firmware” tab.
Figure 34: Device” window

Updating the operating system
Figure 35: “FTP installation” option
▶ Enter the PLC’s IP address and click on “Next. ”

▶ Select the “XC303” device type and click on the “Next” button.
▶ Select the “PLC operating system” component and click on “Next.”
▶ Stop the PLC.
Set DIP switch S1 Stop to the ON position.
▶ Click on the “Download” button to start downloading the firmware.
▶ Wait until the “Download successful” window appears.
Then close the window with “RETURN. ”
▶ Click on the “Close” button to exit the Setup wizard.
▶ Start the PLC. Set DIP switch S1 Stop to the OFF position.
▶ Perform a restart for the XC300 Modular control.
The update process when using removable media or a local directory
(￫ figure 35, page 60) is similar to that for FTP installation.
Procedure:
▶ Insert the USB-Device or MicroSD memory card into the PC.
▶ Select „Removeable Drive“ in the window „XC303 OperatingSystem
Download“ (￫ figure 35).
▶ Select the removable media directory and click on “Next.”
▶ Select the “XC303” device type and click on the “Next” button.
▶ Select the “PLC operating system” component and click on “Next.”
▶ Click on “Install” to start downloading the firmware.
▶ Click on “Done” to exit the Setup Wizard.

Programming in Series Production via MicroSD or USB
The firmware files are now located on the removable media in the directory
XC303/Firmware.
▶ Insert the USB-Device or the MicroSD memory card into the XC300.
The system will check whether there is a different operating system on the
removable medium. If one is found, the system will start updating the firm-
ware. You will recognize that this is happening when the status indicator
LEDs under the front panel, PLC and PRG (green), start to flash in alternating
sequence along with SF (red).
￫ The new firmware version will not be enabled until the PLC is
restarted.
3.9 Programming in Series Production via MicroSD or USB

The operating system and application can be programmed via MicroSD
memory card or USB-Device.
￫ section 3.2, “Startup Behavior XC300”, page 47

Programming in Series Production via MicroSD or USB

Task Configuration
4 Configuring the Controller
4.1 Task Configuration

Project processing can be controlled via tasks. Each task can be assigned a
range of programs which should be run during execution of the task.
The task is defined by a name, a priority and a type which defines under
which conditions a task starts. Task condition and priority determine the
sequence in which the tasks are to be processed.
You can set “Cyclic” or “Event-triggered” as the task condition. A cyclical
task is restarted after the set interval time has elapsed. An event-triggered
task is only started when the event occurs. You also have the option of con-
necting system events, such as “Start,” “Stop,” or “Reset,” to the execu-
tion of a program.
The task priorities can be configured with a value from 0 to 31 where 0 is the
highest priority and 31 is the lowest priority.
In principle the output image is written onto the physical outputs before
every task is called and the input image is read (updating of the input/output
map). The task is executed thereafter. In addition, all system activities are
carried out before or after the task call. This includes, for example, communi-
cation with the XSOFT-CODESYS-3 or online changes.
Updating of the input/output image by multiple tasks is described in the
￫ section 4.3, “Multitasking”, page 67.
All IEC tasks, including those with the highest priority can be interrupted by
an interrupt or an event controlled task.
Time monitoring (Watchdog) can be activated for each task.
￫ For a detailed task configuration description, please refer to the

manual for programming PLCs with XSOFT-CODESYS-3
At the end the control specific settings are explained on the basis of an
example.

Task Configuration
Creating a Task (Example)

First create the cyclic task “Basic” with the assigned program “Basic_prog”.
Then you can add the event controlled task “Param” with the program
“Param_prog”. In the program “Basic_prog” an event is programmed which
invokes the “Param” task.
The following steps are necessary in order to create a task:
• Add a task
• Define the program call
• Create the program
4.1.1 Creating a Cyclic Task

▶ In the configuration tree diagram for the project, select the device
“Device (XC303)” -> “PLC Logic” -> “Application.”
▶ In the configuration tree diagram, select “Task Configuration.”
▶ In the context menu, select the command “Add Object” and “Task.”
▶ Enter in the Name field a name such as “Basic.”
▶ Set the task in the dialog as in figure 36.
Define the program call
With the program call you define which program is to be called with the
“Basic” task.
▶ Right-click on the icon for the previously created “Basic” task and in the
context menu, select the command “Add Object” -> “Program Call.”
▶ Enter the name “basic_PRG” in the “Add Call” window.
▶ Confirm the program name by selecting “Add.”
1.
Figure 36: Configuring the cyclic task with program call

Task Configuration
Writing a program
▶ Open the Editor for the “basic_PRG” program element by double-click-
ing it.
▶ You can now enter a program. In the program example, the “bCount”
variable is incremented.
When the counter reaches 20 the global variable a = TRUE.
Figure 37: Program element for cyclic task
4.1.2 Create Event-type task and program start set

The procedure corresponds to the creation of a cyclic task.
▶ Create “Event”-type task with the name “Event” as shown in figure 40.
▶ Enter the global Boolean variable “a” as the event by clicking the button,
double-clicking the “GVL” folder in the “Input Help” window, selecting
the variable “a,” and confirming with “OK.”
▶ Enter the program call “Event_prog.”
Figure 38: Create Event-type task

System events
Writing a program
▶ Select “Application” and in the context menu, select the command
“Add Object” and choose (POU) as the object with the name
“Param_prog.”
▶ You can now enter a program. The program example Param_prog
(figure 39) increments the variable “value” by the value 1.
The “Param_prog” program is processed if variable a = TRUE.
Figure 39: Programmed element for event controlled task
Events can only be triggered by Boolean variables.
4.2 System events

A function can be activated using a system event. It can be used when the
PLC is started to initialize modules with new parameters, for example.
The system events are independent of the task!
Assigning a Function to a System Event
▶ In the task configuration, add an event handler in the “System Events”
tab.
▶ Select one of the prescribed events, such as “StartDone,” and enter a
function name in the “Function to be Called” field, such as “AfterStart.”
▶ “System Events” – the event, e.g., “Start,” and enter the name of the
POU (e.g., “Power_prog”) to be processed.
Figure 40: Assigning a function to the system event
▶ Double-click a function name to open the Editor and configure what is to

be processed after the start.

Multitasking
Figure 41: Programming a function
￫ Further information concerning the system events can be found

in the online help of the programming system.
4.3 Multitasking
The XC300 runtime system is a multitasking system. This means that multi-
ple tasks can be performed at the same time (in parallel).
Updating the Input/Output Image
If the local and central inputs/outputs are programmed in multiple tasks, the
input/output image in XSOFT-CODESYS-3 is updated according to special
rules:
By default, only the inputs are read before each task and the outputs to be
used in the task in question are set.
This means that the CPU does not work with a constant input/output image
within a cycle; instead, the input/output image changes during the cycle
depending on the task.
After starting, the system updates the inputs used in the first task, for exam-
ple. The name of the first task “Prog1” is in the figure 43. If the system
detects an input connected to an XN300 slice module by the configuration,
such as XN322-16DI, only this input of the module is updated in the image.
If further inputs exist in this task and they are assigned to other slice mod-
ules, the inputs of these modules are also updated.
The same process occurs for the outputs. For example, if outputs QX6.0 and
QX7.1 of output module “1” are used by different tasks, the outputs of this
module are not only updated before the first task. The first task could set out-
put QX6.0 and then the second task may reset the output due to the
changed input image.
￫ Do not access the same input or output from different tasks.

Multitasking
Examples
The examples are based on the following configuration:
input module 1
input module 2
output module 1
XC300 output module 2
CPU
4.0 6.0 4.0 6.0
5.7 7.7 5.7 7.7
Figure 42: XC300 configuration with local inputs/outputs and

I/O system XN300 inputs/outputs as central expansion
The task configuration appears as follows:
Figure 43: Task configuration for examples
Example 1
Table 9: Task details for example 1

Task name Priority Cycle time
Prog 1 2 50 ms
Prog 2 1 10 ms
In the first task “Prog1,” input IX4.0 of input module 1 and input IX6.0 of
input module 2 are used in the program “progtes(1).” Only these inputs are
updated before the first task “Prog1” starts.
In the second task “Prog2,” input IX4.1 of input module 1 is programmed in
the program “progtes(2).” Before the second task “Prog2” starts, this input
of this input module is updated.

Multitasking
Example 2
Table 10: Task details for example 2

Task name Priority Cycle time
Prog 1 2 50 ms
Prog 2 1 20 ms
In example 2, input IX4.0 is programmed in the first task and input IX4.1 and
output QX4.0 are programmed in the second task.
Input IX4.0 is updated at the start of the first task. If this input is set, output
QX4.0 is also set; otherwise it is reset.
At the start of the second task, input IX4.1 of the input module is updated
and output QX4.0 is set or reset.
The control sequence may therefore result in output QX4.0 being set in the
first task and then reset in the second task. The output is toggled.
Creating a Task with Consistent Inputs/Outputs
Avoid access to the physical outputs from several tasks. To ensure a clear
control sequence, create a task for the local inputs/outputs and the inputs/
outputs of the local expansion, in which all inputs are copied to global vari-
ables and at the end of the interval, all outputs of global variables are written
to the output modules (I/O update task). The I/Os are consistent (data integ-
rity) within this task. The global variables can then be used instead of the I/Os
in other tasks.
￫ Do not access the same input or output from different tasks.
￫ On the XC300 PLC a maximum of 50 tasks are possible.

“Free-running”-type tasks cannot be configured.
Note with parametric programming of the watchdog time that
the POU called with the interrupt service routines, extends the
task run times accordingly.

Task Monitoring with a Watchdog
4.4 Task Monitoring with a Watchdog

The processing time of a task can be monitored using a watchdog.
The following applies when defining the monitoring time:
Processing time < Task interval time < Watchdog (time)
If the processing time of the task exceeds the interval time, the end of the
second interval time is awaited until the task is restarted.
￫ Watchdog deactivated.
The watchdog interrupts the program processing if the processing time of
the task exceeds the watchdog time.
Furthermore, the frequency (sensitivity) can be set, which allows a certain
number of times the watchdog can be exceeded. In this case the outputs of
the PLC are switched off and the user program is set to the “Halt” state.
Afterwards, the user program must be reset with RESET.
￫ If the watchdog is deactivated, tasks are not monitored.
CAUTION
 If you want to parameterize a task without a Watchdog or want

to deactivate the Watchdog at a later time, all the outputs which
have been accessed up to this time can continue to remain
active. This is the case for example, when the task can't be
ended due to a continuous loop (programming error) and/or
missing end condition (stepping condition). The outputs con-
tinue to retain their “High” potential until the operating mode is
changed from RUN to STOP or until the control voltage for the
outputs is switched off.
Configuring a Watchdog
You can select the following settings in the task configuration:
• Watchdog on/off
• Watchdog time
• Watchdog sensitivity.
These settings apply for time controlled and event controlled tasks.
Watchdog active
The watchdog is started at the commencement of every processing cycle
and reset again at the end of the task.
￫ The following rule applies when defining the watchdog

time for multiple tasks: Each watchdog time must be
greater than the sum of the task interval times.

If the processing time is longer than the watchdog time (sensitivity = 1) –

e.g. with a continuous loop in a program – the watchdog becomes active.
If the processing cycle is shorter than the watchdog time, the watchdog is
not activated.
The triggering of the watchdog continues to be dependant on the watchdog
sensitivity. The watchdog sensitivity determines when the watchdog will be
triggered, after the watchdog time has been exceeded by a determined num-
ber of consecutive occasions.
The watchdog is triggered:
• immediately when the watchdog time is exceeded with a watchdog
sensitivity of “1”,
• immediately after the “x”th consecutive time that the watchdog time is
exceeded with a watchdog sensitivity of “x”.
For example, a task with a watchdog time of “10 ms” and a watchdog
sensitivity of “5” will end at the latest after 5 x 10 ms = 50 ms.
Example: Watchdog active
The interaction of interval time (IZ), task run time (TZ), watchdog time (WT)
and watchdog sensitivity are illustrated by the following configuration
example:
• Watchdog on
• Watchdog time (WT) = 15 ms
• Watchdog sensitivity = 2
The interval time (IZ) of the task is 10 ms.
Variant a: The watchdog is not triggered as the task time always remains
below the defined watchdog time.
Variant b: The watchdog is triggered 15 ms after commencement of the
second task , as both task times are longer than the defined watchdog
time and occur consecutively.
Variant c: The watchdog is triggered 15 ms after commencement of the
second consecutive task, which is longer than the defined watchdog time.
Variant d – infinite loop: The watchdog is triggered , as the task time is
longer than the watchdog time multiplied by the watchdog sensitivity
(2 x 15 ms = 30 ms).
IZ = 10 ms IZ IZ IZ IZ IZ IZ IZ IZ IZ IZ
a TZ < WT TZ < TZ < TZ <
b TZ > WT TZ > WT TT = WT
c TZ k WT TZ > WT TZ < TZ < TZ > WT TT = WT
d TZ > WT TZ > 2 x WT
(infinite
loop)
Figure 44: Watchdog active, multiple tasks with differing priority

Watchdog deactivated
The cycle time of a task is not monitored when the watchdog is deactivated.
The task ends when it has been processed and only starts again when the
next interval time starts.
Example: Watchdog deactivated
The interval time (IZ) is 10 ms.
Variant a: The interval time (IZ) of a task was set to 10 ms.
The actual task run time (TZ) is 15 ms. The task was started during the initial
call but only ended during the second cycle. Therefore, the task is not started
again in the second cycle. The task can only be restarted in the third cycle –
after 20 ms. This means that the task does not run every 10 ms but rather
only within a time interval of 2 x 10 ms.
Variant b: The running cycle is not ended.
IZ = 10 ms IZ IZ IZ IZ IZ IZ
a TZ > IZ TZ > IZ TZ > IZ TZ > IZ
b TZ > WT TZ f WZ
(infinite loop)
Figure 45: Watchdog deactivated
Multiple tasks with the same priority

You can assign several tasks with the same priority. The tasks are split
according to the “Time Slice” principle and are practically executed simulta-
neously as part intervals (Round Robin).

Limit Values for Memory Usage
4.5 Limit Values for Memory Usage

The data memory of the XC300 Modular control is divided into memory
segments. The segment sizes are shown in figure 46.
The global data utilizes multiple segments. The required amount can be
specified to suit the size of the loaded program.
You can see the segment size under ‹Device (XC303) l Device information
l memory-layout›:
Example
Figure 46: Memory segment size Device (XC303)
The maximum segment size for inputs, outputs, and markers is 1,280 bytes
each and for retain variables, 98 kB.

Addressing inputs/outputs and marker
4.6 Addressing inputs/outputs and marker

If you open the PLC configuration of a new project, you will receive the cur-
rent view of the default settings of the addressing. In this setting the
addresses are automatically assigned and address conflicts (overlaps) are
reported.
Figure 47: Default setting of the addressing
If you add a module to the PLC in the configurator, the configurator will
assign this module with an address. Further modules are assigned with the
next addresses in ascending order. You can also assign the addresses freely.
However, if you access the “Automatic calculation of addresses” function
later, the addresses are shown in reassigned ascending order.
Check for overlapping addresses
Duplicate addresses are identified during conversion and an error message is
generated.
Addressing by Data Type
If you assign a word-addressable variable of the module, such as I/O system
XN300 InputChannel2 of the XN322-4AI-PTNI, with an address that does not
match the data type (e.g., IB11) in the “Input Address” field, the word
address following the previous variables automatically appears in the control-
ler configurator (e.g., IW12).
Figure 48: Addressing by Data Type

Diagnostics
4.7 Diagnostics
The following diagnostics options are available:
• LED indicators
• Error messages when converting the project
• I/O system XN300 master diagnostic options
• Shell commands for diagnostics
Subscriber found / Subscriber not found
Runtime system started/not started
PLC LED Indicator
If the program is experiencing a fault, the status indicator LED under the
front PLC flashes red and green because the program is being stopped
automatically, ￫ figure 33, page 54.

red green
PLC – – RuntimeSystem not started
• No power supply at X6
– flashing Communication
– ON PLC RuntimeSystem started
ON – Error in RuntimeSystem
• Flash error
• Error in checksum
• SSL connection could not be started
Remedy: Inspect log file
ON ON RuntimeSystem is started and has an error.
A program error can be caused by the following:

• Watchdog: e.g., interval time of a task > watchdog time
• Faulty access to memory: e.g., an attempt was made to access a pro-
tected area
I/O system XN300 master diagnostic options
For errors that occur in the system block (local expansion XC303 with mod-
ules with I/O system XN300), the status of the XN300 master can be called
up for diagnostic purposes.
To do so, follow the steps below:
▶ Open XSOFT-CODESYS-3 and go to the device online.
▶ In the configuration tree diagram, select the device “Device (XC303)”
and “XN300_Master.”
▶ Double-click “XN300_Master” and select the “XN300Master Parame-
ter” tab.

Diagnostics
▶ In the event of an error, the “Current Value” column contains an error

number and a related description, such as that shown in the following
example with error number “47” and the description “The CoDeSys-
SDIAS configuration is not yet available in the PLC!”
Figure 49: XN300Master Parameter tab with error message

(Example German sreen with special error message)
Sample display of messages from local XN300 system bus
￫ More information on diagnostics can be found in the man-

ual for the I/O system XN300,
“XN300 slice modules”, or “CANopen Gateway XN-312-
GW-CAN”
Shell Commands for Diagnostics for Modules from the I/O system
XN300
▶ Double-click on the device in the Explorer, e.g., “Device (XC303),”
go to the “Device” tab, and select “PLC Shell.”
▶ Enter the command “?” in the command line.

Searching the Network with Automatic Controller Detection
5 Establishing a Connection with a PC – XC300

The connection between the PC and CPU can be established via one of the
Ethernet interfaces ETH0 to ETH2.
The transfer rate of the Ethernet connection is controlled with the autosens-
ing function. Components in (detect) mode automatically determine whether
the connection has a rate of 10- or 100-MBits per second.
This chapter describes what settings must be defined here in the XSOFT-
CODESYS-3 software. A new project is created in the following example.
5.1 Searching the Network with Automatic Controller Detection

The PC attempts to connect to the controller and reports the successful
connection by displaying green marker points.
Figure 50: Successful connection between PC and controller XC300

Creating a new project
5.2 Creating a new project

▶ First ensure that you have connected the PC to the Ethernet interface of
the device by cable using the Ether interfaces or USB/Ethernet adapter.
▶ Ensure that the IP addresses of the PC and device come from the same
number range.
▶ Start the XSOFT-CODESYS-3.
▶ Select “File,” “New Project,” “Standard Project” and enter a project
name, e.g., “Test.”
▶ In the window that follows, select “XC-303 (Eaton Automation)” as the
device and choose your desired programming method, such as
“Structured Text (ST).”
▶ Confirm the displayed information by clicking on “OK.”
The device will be added to the project. The standard tree diagram for the
project is created as the configuration tree diagram. The application contains
the library manager with all required libraries, and the main task “PLC_PRG”
is also created.
Establishing Communication
▶ The device name “Device (XC-303),” the application “Application,” and
the main program “PLC_PRG” can be edited and renamed.
▶ Double-click the device “Device (XC-303)” and select the “Communica-
tion” tab.
▶ Click on the “Search Network” button or enter the IP address of the
controller.
All devices that can be accessed are listed.
▶ You can use the “Flash” button to display a temporary flashing pattern
on the marked device.
￫ Use this to uniquely identify the controller.
Figure 51: Adding a device using its IP address

Changing the IP Address on the Controller
5.3 Changing the IP Address on the Controller

When changing the IP addresses, ensure that the IP address of the PC and
of the XC300 Modular control belong to the same network/subnet.
Example:
IP address of the PC: 192.168.138.100
Subnet mask: 255.255.255.0
IP address of the XC300: 192.168.138.248
Subnet mask: 255.255.255.0
There are three different ways to change the IP address of the controller:
1. PLC shell commands getipconfig; setip... ...addr/...netmask/...gateway
2. setipconfig and getipconfig function in the EA_Network library
3. networkconfig.templ on MicroSD memory card or USB-Device
PLC Shell Command
▶ Open the PLC browser, see ￫ section 16.1, “Accessing PLC Shell
Commands”, page 133.
▶ In the command line, enter setipconfig <IP-Adresse> On
▶ Confirm with <Eingabetaste>.
▶ Restart the device once you have changed the IP address.
setipconfig Function
Ensure that the EA_Network library is added to the library manager.
Use the function in your program, e.g., in “PLC_PRG.”
▶ Open the input tool with <F2> to do this.
Figure 52: Input Tool

Changing the IP Address on the Controller
▶ In the “Category,” select “Element Call.”

▶ Select “EA_Network,” “POUs,” “Configure local ethernet interface,”
“NET_SetIPConfig.”
▶ Enter the port, IP address, and subnet mask as parameters.
networkconfig
If you cannot establish a connection to the device, because the IP address is
not known, for example, you can use the “networkconfig.templ” file with the
aid of the MicroSD memory card or a USB-Device to reset the IP address of
the Ethernet interfaces of the XC300.
Setting the IP address of ETHx Ethernet interface:
Requirement: Variable NW_UPDATE_FROM_USB or
NW_UPDATE_FROM_SD must be set to “1.”
▶ Save file “networkconfig.templ” to a directory on your PC. The file is
located on the XC300 in directory “home”.
▶ Edit the file.
▶ Assign a valid IP-V4-IP address and subnet mask
e.g., ETH1_IP_ADDRESS=192.168.137.248 and
ETH1_SUBNET_MASK=255.255.255.0
￫ When changing the properties of an Ethernet adapter, all param-

eters must be entered completely in the file, even if they corre-
spond to the default settings.
▶ Save file networkconfig.templ under the name networkconfig.

▶ Copy the file to the MicroSD memory card/USB-Device in directory
XC303/update.
▶ Insert the MicroSD memory card into the XC300.
▶ Reboot the XC300 and then remove the file from the MicroSD memory
card/USB-Device.
Figure 53: File networkconfig.templ on the XC300

(Example German sreen)

Configuring Local Inputs/Outputs of the Device
6 Configuring and parametizing Inputs/Outputs
6.1 Configuring Local Inputs/Outputs of the Device

The local inputs/outputs of the controller, I/Q1 to I/Q4, are configured as
inputs by default. If you wish to change the configuration, proceed as
follows:
▶ Select the device in the configuration tree diagram and open the
“Device” tab by double-clicking it.
▶ Select “LOCAL_IO Parameter.”
▶ Double-click the “Value” column to get a selection field where you can
define the nodes as inputs or outputs or as interrupt inputs.
Figure 54: Configuring local inputs/outputs
6.2 Interrupt Processing

If an interrupt occurs, the operating system executes the program organiza-
tional unit (POU) which is linked to the interrupt source.
￫ The execution of the interrupt POU is not time monitored.

Programmed infinite loops are not terminated.
The local inputs I1 – I4 can be used as interrupt sources.

They are configured via Device -> local_IO parameter.
Available settings:
• Int falling
• Int rising
• Int falling + rising
The POU initiated by the interrupt is always run to completion and cannot be
interrupted by a new interrupt. A new interrupt is only carried out after the
current interrupt has ended.

Interrupt Processing
ATTENTION
All the outputs controlled (H signals) up to this point remain
active and can’t be switched off.
The interrupts are enabled in the RUN state of the CPU and disabled in the
STOP state. Interrupt sources which are not enabled in the configuration do
not initiate an interrupt. If a POU is not assigned to an enabled interrupt
source, the interrupt is recognized and executed but without running a POU.
Frequent interrupts during program execution can cause the programmed
task time to time out and result in a RESET being initiated by the Watchdog.
User interrupts can be inhibited and re-enabled from the program. The func-
tions Disableinterrupt and Enableinterrupt exist for this purpose. A call parame-
ter in the XSOFT-CODESYS-3 software determines if an individual interrupt
or all interrupts are enabled or disabled. A disabled interrupt must be
enabled with the same parameter used to disable it.
The two functions DisableInterrupt and EnableInterrupt belong to the library
EA_XC303Events.lib. This library must – if not already done so – be integrated
into the XSOFT-CODESYS-3 library manager, see ￫ section 15.2, “Installing
additional system libraries”, page 130.
DisableInterrupt
With this function, you disable (deactivate) a parameterized physical interrupt
by accessing it from the user program.
Figure 55: “DisableInterrupt” function

EnableInterrupt
With this function, the physical interrupt which was deactivated beforehand
can now be re-enabled as an active interrupt.
Figure 56: “EnableInterrupt” function
Configuration
The interrupt is configured and assigned a priority in the “PLC and Task Con-
figuration” of the CODESYS (activate the “Resources” tab and open the
“Task Configuration l System Events” folder). Each interrupt can be
assigned with a POU here.
Example for Interrupt Processing
A “Basic” task contains a POU “PLC_PRG”. A further POU “Fastprog”
should be processed if an L ￫ H edge at input I0.4 generates an interrupt.
▶ Create the POUs “FAST_PRG” as shown in ￫ figure 57.
Figure 57: PLC and Task Configuration

▶ Switch to the PLC configuration and assign input I0.4 (L ￫ H edge) the
interrupt source “Interrupt rising edge,” for example, from the drop-
down menu.
Figure 58: Assigning the I0.5 ￫ interrupt source
▶ Change over to the Task configuration and open the System Events
folder.
Figure 59: System events
▶ Select the “User_Interrupt_4.”

▶ Mark the area of the “Called POU” column.
▶ Select the FAST_PRG POU and confirm with “OK.”
▶ Save the project. You can now test it.
With each rising edge at input 4, the program FAST_PRG opens.

Secure Communication
6.3 Secure Communication

Information in the XSOFT-CODESYS-3 online help under:
• Security screen
• Certificate selection
• Encryption and signing with certificates
What can be protected?
• Communication with the controller
• Communication with the web server
• Boot project
• Online access to the application
• Access to the application via the programming PC

Secure Communication

Overview
7 Assigning System Parameters
7.1 Overview
System parameters independent of the project can be set by you and saved
on the memory card. They are compiled in the following files:
• netwerkconfig.templ -> networkconfig
• deleteboardapplication.templ -> deleteboardapplication
The memory card can be used in other controllers, too.
When started, the controller automatically adopts the parameters set in the
files.
• SD/USB in folder XC-303/update
• deleteboardapplication.templ -> deleteboardapplication
Templates on the controller in folder \home.

File InitPLC with Default Parameters
7.2 File InitPLC with Default Parameters

The InitPLC file is always generated with all controller-specific entries.
All parameters are already predefined. The following display contains the
parameters with their default values, which you can adapt as desired.
#-----------------------------------------------------------
# Comunication Protocols
#-----------------------------------------------------------
# Set to 1 to enable FTP Server. (Unsecure connection)

ENABLE_FTP=0
# Set to 1 to enable telnet Server. (Unsecure connection)
ENABLE_TELNET=0
# Set to 1 to enable SSH Server . (Secure connection, needs a valid certificate.)
# SSH can be enabled/disabled using the XSoft-Codesys "PLC Shell" command ssh_access.
ENABLE_SSH=1
# Set to 1 to enable SFTP Server. (Secure connection, needs a valid certificate.)
# SSH must be activated to use SFTP!
ENABLE_SFTP=1
# Set to 0 to prevent ping response send by the plc.
ENABLE_PING_RESPONSE=1
#-----------------------------------------------------------
# Bootproject behaviour
#-----------------------------------------------------------
# A bootproject can be copied form a distant location to "/home/Plc_Prg" and started as bootproject.
# the check for bootprojects will terminate at the first location a bootproject is found.
# Test order: SD-Card, USB-Stick, User defined path.
# Overwrite existing bootproject if it differs to the one found on the external location.
OVERWRITE_BP=1
# Set to 1 to copy a bootproject from "/home/disk_sd/XC303/Project" to local storage "./Plc_Prg"
COPY_BOOTPROJECT_FROM_SD=1
# Set to 1 to copy a bootproject from "/home/disk_usb/XC303/Project" to local storage "./Plc_Prg"
COPY_BOOTPROJECT_FROM_USB=1
# Set to 1 to copy a bootproject from a defined path (USER_DEFINED_BP_PATH) to local storage "./
Plc_Prg"
COPY_BOOTPROJECT_FROM_USER_DEFINED_BP_PATH=0
USER_DEFINED_BP_PATH=
# A bootproject located on the plc will be deleted if a file named "deletebootapplication" is found on an
# USB or SD folder /XC303/update
ALLOW_BOOTPROJECT_DELETION=1
#-----------------------------------------------------------
# Firmware update behaviour
#-----------------------------------------------------------
# Update firmware only if the version of the image to be updated is higher than the existing firmware.
FW_ONLY_NEWER_VERSION=0
# Overwrite existing firmware in any case. Flag will be removed on first firmware-update
FW_FORCED_OVERWRITE=0
# Take firmware from SD card "/home/disk_sd/XC303/Firmware"
FW_INSTALL_FROM_SD=1
# Take firmware from USB-storage "/home/disk_usb/XC303/Firmware"
FW_INSTALL_FROM_USB=1
# Set to 1 to install a firmware XSoft-Codesys Updater"
FW_INSTALL_FROM_XSOFTCODESYS=1
# Set to 1 to install a firmware from a defined path (USER_DEFINED_FW_PATH)"
FW_INSTALL_FROM_USER_DEFINED_FW_PATH=0
USER_DEFINED_FW_PATH=

File InitPLC with Default Parameters
#-----------------------------------------------------------
# Reset network settings
#-----------------------------------------------------------
# You should take care to move the networkconf file, once the reset values have been applied.
# A networkconf template file can be found on /home/etc/networkconfig.templ
# Reset network configuration by booting the plc with a config File located on /home/disk_usb/XC303/
update/networkconfig
NW_UPDATE_FROM_USB=1
# Reset network configuration by booting the plc with a config File located on /home/disk_sd/XC303/update/
networkconfig
NW_UPDATE_FROM_SD=1
#-----------------------------------------------------------
# Start behaviour
#-----------------------------------------------------------
# Delay the start of the runtime system for a given number of seconds.
# (This start delay may be needed to detect USB devices.)
PLC_START_DELAY_SEC=4
# Set to 1 to skip the plc-runtime start
DISABLE_PLC_START=0
# Restrict the processor core usage of the plc-runtime. Valid entries: "CORE_0", "CORE_1", "BOTH"
PLC_CORE_USAGE=CORE_1
# Set to 1 to constantly check rts-state.
PLC_SUPERVISE_RTS=1
# Set to 1 to Reboot the PLC if the runtimesystem terminates unexpectedly.
PLC_REBOOT_ON_RTS_TERMINATION=1
#-----------------------------------------------------------
# Log Files
#-----------------------------------------------------------
# Defined path used to safe log files.(Default path "/var/log" is volatile,
# log files located there are lost after a power cycle.)
LOGFILE_DIR=/var/log
# Name of log file containing messages during the start up process.
LOGFILE_STARTUP=XC303Log.txt
# Name of log file containing messages from the plc runtime system.
LOGFILE_RTS=codesyscontrol.log
#-----------------------------------------------------------
# Map network drive
#-----------------------------------------------------------
# A network drive may be mapped into the view of the plc filesystem using nfs (Linux/Unix) or cifs
(Windows).
# Using nfs (network file system). A path "/home/disk_nfs" will be created.
MAP_NFS_FOLDER=0
NFS_SOURCE_PATH=
# Using cifs (common internet file system). A path "/home/disk_cifs" will be created
MAP_CIFS_FOLDER=0
CIFS_SOURCE_PATH=
CIFS_USER_NAME=
CIFS_DOMAIN_NAME=
CIFS_PASSWORD=

Switching On the Controller with Memory Card with File “InitPLC” Inserted
7.3 Switching On the Controller with Memory Card with File “InitPLC” Inserted
These system parameters are also active after a new program is loaded.
The start process updates the following:
• Firmware
• Boot project (user program)
• Network configuration
See also ￫ section 3.2, “Startup Behavior XC300”, page 47.
In all checking processes, once the XC300 Modular control is started the
MicroSD slot is checked first and only then is the USB-Host checked.
If a boot application exists on the MicroSD memory card or USB-Device and
this application has a newer version then the version in the XC300, the boot
application in the controller is updated.
The retentive data is then loaded.
If the controller is in a warm/cold start and the “STOP” DIP switch is set to
the “OFF” position, the user program is started.
The DIP switch configuration is described in detail in ￫ section 3.3.1, “DIP
Switch S1”, page 49.

File “networkconfig”
7.4 File “networkconfig”

The device settings for the network can be changed in this file.
Empty entries are ignored.
To adjust the parameters, proceed as follows:
Requirement: Variable NW_UPDATE_FROM_USB or
NW_UPDATE_FROM_SD must be set to “1.”
▶ Open the file networkconfig and edit the desired parameters.
▶ Save the changed file under the name “networkconfig” in the directory
./XC303/update on the MicroSD memory card or USB-Device.
▶ Insert the MicroSD memory card into the slot or connect the USB-
Device.
▶ Start the XC300 Modular control.
Templates of file networkconfig and deleteBootproject can be found in the
Eaton Download Center.
Table 11: Predefined default parameters in file “networkconfig”

#--------------------------------------------
# ETH 0
#--------------------------------------------
ETH0_DISABLE=
# 1 will disable the interface.
# Default value:0
ETH0_ENABLE_DHCP=
# 1 will enable dhcp client on the interface.
# Default value:0
ETH0_IP_ADDRESS=
# Should containg a valid IP-v4 ip-address,
# if DHCP is enabled this field must be left blank.
# Default value:192.168.119.248
ETH0_SUBNET_MASK=
# Should containg a valid IP-v4 subnet mask
# Default value:255.255.255.0
ETH0_BROADCAST=
# Should containg a valid broadcast address
# Default value:255.255.255.255
ETH0_DEFAULT_GATEWAY=
# Should containg a valid IP-v4 ip-address of the default gateway.
# Default value: no default value.

File “networkconfig”
#--------------------------------------------
# ETH 1
#--------------------------------------------
ETH1_DISABLE=
# Default value:0
ETH1_ENABLE_DHCP=
# Default value:0
ETH1_IP_ADDRESS=
# Default value:192.168.137.248
ETH1_SUBNET_MASK=
ETH1_BROADCAST=
# Default value:255.255.255.255
#--------------------------------------------
# ETH 2
#--------------------------------------------
ETH2_DISABLE=0
# Default value:0
ETH2_ENABLE_DHCP=
# Default value:0
ETH0_IP_ADDRESS=
# Default value:192.168.138.248
ETH0_SUBNET_MASK=
ETH0_BROADCAST=
# Default value:255.255.255.255

Local expansion
8 Expansion
8.1 Local expansion

The XC300 controller can be expanded centrally by up to 32 XN300 slice
modules. To do so, the controller and the XN300 slice modules are con-
nected and mounted together on a mounting rail (DIN rail). The I/O system
XN300 provides a wide range of XN300 slice moduless, which offer special
functions in addition to digital and analog inputs and outputs, such as the
weighing module or the motor driver module.
￫ For up-to-date information about the I/O system XN300, refer to

the product pages:
www.eaton.eu/xn300
and for the available product range, refer to the EATON online
catalog.
Entering “XN300” in the search field will take you directly to this
product group.
All modules are described in the “XN300 slice modules”
manual.
input module 1
input module 2
output module 1
XC300 output module 2
CPU
4.0 6.0 4.0 6.0
5.7 7.7 5.7 7.7
Figure 60: Central XC300 expansion with XN300 slice modules

Local expansion
8.1.1 Configuring Inputs/Outputs of the Central Expansion

If you have expanded the XC300 controller with XN300 slice modules and
mounted them as a system block on the DIN rail, you can configure it in
XSOFT-CODESYS-3 as follows:
▶ Ensure that all XN300 slice modules are connected and supplied with
power.
▶ Open your XSOFT-CODESYS-3 project.
▶ Select the device “Device (XC-303)” in the device tree diagram.
▶ In the context menu, select the “Add Device...” command.
▶ In the “Add Device” window, go to “Miscellaneous” and select
“XN300 Master.”
▶ Confirm the selection by clicking the “Add Device” button.
The XN300 master appears in the device tree diagram.
▶ Select “XN300 master” in the device tree diagram.
▶ In the “Add Device” window, go to “Miscellaneous” and select the
XN300 slice modules that you installed with XC300 as one system block.
Select the XN300 slice modules in the same order as they were physi-
cally connected to XC300.
All devices are now shown in the device tree diagram.
Figure 61: Device tree diagram with XN300 slice modules

Remote expansion
Figure 62: Declaring values
Figure 63: Parameterize XN300 slice modules
8.2 Remote expansion
￫￫ Section “ The XC300 Modular control supports decentralized

expansion via fieldbus interfaces. The following protocols are
supported for communication on the respective interface:”,
page 12
The following chapters describe the individual fieldbus inter-
faces.

Remote expansion

9 CAN
The components of the I/O system XN300 can be networked via the Eaton
CAN-Gateway XN-312-GW-CAN with the XC300 Modular control into a CAN
node.
Each CAN node allows expansion through the I/O system XN300 by up to 32
XN300 slice modules.
XC300 XN-312 XN300
CPU
TN1 TN2 TN32
CANopen
Figure 64: CAN node as decentralized expansion of the XC300 Modular control
For this purpose the system block, consisting of a gateway and XN300 slice
moduless, is mounted on a DIN rail. The system block and controller can be
mounted separately. The XN300 system provides a wide range of XN300
slice moduless, which offer special functions in addition to inputs and out-
puts, such as the weighing module or the motor driver module.
￫ An overview of the XN300 slice modules can be found in the

“XN300 slice modules” manual.

Configuring and commissioning CANopen
9.1 Configuring and commissioning CANopen

The XC300 Modular control can communicate both via CAN and CANopen.
The following describes communication via CANopen.
Any CAN gateway can be connected to the CAN master via an EDS file.
The following shows an example of how the CANopen gateway XN-312-GW-
CAN, including XN300 slice modules, is connected to the CANopen master.
gateway CANopen
input module 1
input module 2
output module 1
XC300 XN-312 output module 2
CPU
4.0 6.0 4.0 6.0
CAN open
5.7 7.7 5.7 7.7
￫ If you are commissioning the fieldbus for the first time, you
must first set up the relevant PLC programming environment.
Initial Commissioning
The following steps must be carried out:
▶ Connect the XC300 Modular control to the programming PC.
▶ Connect the XC300 to the CAN-Gateway XN-312-GW-CAN via a CAN
bus cable.
▶ Set the DIP switch for the CAN.
￫ section 2.10.4, “CAN/easyNet”, page 45
▶ Set the node ID and baud rate.
▶ Save the configuration of the I/O system XN300 components connected
to the CAN-Gateway XN-312-GW-CAN in the “config check” in the
gateway.
▶ Open your project in XSOFT-CODESYS-3 or create a new one,
￫ section 5.2, “Creating a new project”, page 78.

9.1.1 Adding the CAN manager

▶ Right-click to open the context menu and select “Add Device...”
The “Add Device” dialog box will appear. You can leave the dialog box open.
▶ In the “Add Device” window, go to “Fieldbuses” and select the
“CANbus.”
The CANbus appears in the configuration tree diagram.
▶ Select “CANbus” in the configuration tree diagram.
▶ Select the baud rate.
“CANopen_Manager.”
The CANopen_Manager appears in the configuration tree diagram.
EDS files for the fieldbus subscribers from EATON are automatically
installed.
Figure 65: CANopen parameters for the CANopen_Manager

9.1.2 Setting the Baud Rate via CANbus

▶ In the configuration tree diagram, double-click “Devices” on
<CANbus (CANbus)>.
▶ Open the “CANbus” tab and select the Baudrate, e.g., <125000>.
Figure 66: CANopen_manager baud rate
￫ Detailed information can be found in the online help for

XSOFT-CODESYS-3, which can be opened by pressing the
<F1> function key.
▶ EDS files for fieldbus subscribers from other companies must be addi-
tionally installed in XSOFT-CODESYS-3, see ￫ section 9.1.5.2, “Install-
ing the EDS File”, page 105.

9.1.3 CAN-Gateway XN-312-GW-CAN Integrating

▶ To add the CANopen gateway to your configuration, right-click on
“CANopen_Manager (CANopen_Manager)”:
▶ Then select <Append device...>.
The list will show all the devices that can be configured:
Figure 67: Adding a CANopen device
▶ Select the corresponding CAN-Gateway XN-312-GW-CAN.

▶ Select <Add device> again.
The selected CAN-Gateway XN-312-GW-CAN will be added to the configura-
tion tree diagram.
▶ If the desired CAN device is not found in the list, update the X-SOFT-
CODESYS-3 version you are using or load the appropriate EDS file,
￫ section 9.1.5.2, “Installing the EDS File”, page 105.
▶ Check the settings for the parameters for XN_312_GW_CAN by double-
clicking in the configuration tree diagram on “XN_312_GW_CAN (XN-
312-GW-CAN).”
▶ Select the “XN_312_GW_CAN/General” tab and check the “Node ID”
for the device.
￫ All other gateway settings and information on mapping can be

found in the manual for the CAN-Gateway XN-312-GW-CAN.

9.1.4 Attach XN300 slice modules

▶ To configure the system block, right-click on the CANopen device, e.g.,
“XN_312_GW_CAN (XN-312-GW-CAN)” in the “Devices” configuration
structure.
▶ Then select <Add Device>.
The “Add Device” dialog box will appear if it is not open already. The dialog
box will show a list with all the XN300 slice modules that can be configured.
for
Figure 68: “Add Device” window for CAN module selection for the XN-312-GW-CAN
▶ Select the desired XN300 slice module and then select <Add Device>.
The XN300 slice module will be added to the “Devices” configuration tree
diagram.
￫ The order of the XN300 slice modules in the configuration tree

diagram can be changed as desired by dragging and dropping
elements.
A maximum of 32 XN300 slice modules can be added to the CANopen

device.

All devices are now shown in the device tree diagram.
Figure 69: XC300 with CANopen master,

CAN-Gateway XN-312-GW-CAN and 4 XN300 slice moduless
If you are using analog modules, observe the following requirements:

• If default mapping (index 0x6401/x) is used for analog modules, PDO-
based data transmission for these I/O slice modules must be enabled by
setting the value of object index 0x6423, subindex 0 to TRUE.
• Regulating the bus load on the CAN fieldbus
The following procedure is recommended in order to prevent the XN-
312-GW-CAN gateway from generating a heavy load on the CAN field-
bus:
• Use internal module filters,
see „XN-300 slice modules“, MN050002-EN“ manual.
• If using the default mapping (index 0x6401/x), a transmission filter
can be configured for each individual payload data object; SDO
objects: AI_DELTA_VALUE, index 0x6426/x).
When this filter is configured, the gateway will update and transmit
the corresponding value only if this value is different from the last
transmitted value by more than the configured delta.
By setting an inhibit time or selecting a synchronous transmission type,
TPDO properties can be configured in such a way as to avoid impermissible
bus loads.
ATTENTION
The short data refresh cycle times in the XN300 system can
result in the CAN transmission path being subjected to high
loads. Accordingly, it is recommended to limit the data being
transmitted by using the various PDO properties available (e.g.,
inhibit time), especially in the case of analog input and technol-
ogy modules featuring counters.

9.1.5 Description Files for CANopen

The gateway XN-312-GW-CAN is integrated into the CANopen structure with
the aid of a standardized EDS file (Electronic Data Sheet).
This EDS file lists all objects with the associated sub-indexes and the corre-
sponding entries.
The EDS file is automatically installed in XSOFT-CODESYS-3 with the
CANopen master.
9.1.5.1 Standard EDS files

Make sure that you are working with the latest version of the standard EDS
files in your PLC programming environment. If subscribers are not listed,
check whether there are updates for the files in the Download Center,
￫ page 8. To find it quickly, simply enter “XN300” or “EDS” as a search
term.

9.1.5.2 Installing the EDS File

If you want to install an updated EDS file or an EDS file from another device
manufacturer, proceed as follows:
▶ Select and download the latest version of the EDS file.
▶ Save and unzip the *.zip file to a project folder of your choice.
▶ In XSOFT-CODESYS-3, select <Tools | Device Repository …>.
▶ Click the “Install...” button.
▶ In the Explorer, select the desired EDS file.
▶ Confirm by clicking on “Open.”
▶ Confirm the prompt “The device has been successfully installed” by
clicking “OK.”
Figure 70: “Devices” pane with CANopen manager in the configuration structure
▶ Double-click on “CANopen_Manager” (CANopen manager).

▶ Check the settings under the “CANopen_Manager” tab.
9.1.6 Integrating libraries for CANopen communication

By default, all the libraries required for CANopen communication will be auto-
matically added after the CAN master is added and the project is compiled
for the first time.
• 3S CANopenStack
• CAA CiA405
• CANbusDevice
• EA_CAN types (when using EATON CAN devices)

9.1.7 LEDs on the device

The status indicator LEDs under the front panel report the status.
￫ figure 33, page 54

red green
CAN1 – – No bus activity
CAN2
– flashing Bus activity OK (CAN), FLASH for each telegram
ON – Bus error
flashing flashing WARNING
Each successfully sent/received CAN telegram triggers the LEDs.

Integrating the EtherCAT Master
10 EtherCAT
The following describes how the XC300 Modular control controller is config-
ured as an EtherCAT master in order to operate decentralized EtherCAT
subscribers.
EU5C-SWD-ETHERCAT is used here as an example of an EtherCAT sub-
scriber. This EtherCAT gateway acts as a coordinator for other SWD sub-
scribers and their input and output functions.
A target and project configuration must be saved in the gateway in order for
the EU5C-SWD-ETHERCAT gateway to exchange data with the XC300 con-
troller. How these configurations are applied and stored in the device is
described in the “ Gateway EU5C-SWD-ETHERCAT” manual. This manual
can be downloaded from the internet as a PDF from: www.hilscher.com
<Products | Partner Products | SmartWire-DT | EU5C-SWD-ETHERCAT |
Downloads>
Requirements:
• PC with installed PLC programming environment XSOFT-CODESYS-
3 V3.5.10 or higher and Ethernet adapter.
• The Ethernet adapter for the PC is connected to the XC300 controller via
Ethernet.
• XC300 is connected to the EU5C-SWD-ETHERCAT gateway.
• The gateway is connected to a SmartWire-DT network.
• The gateway contains a valid SmartWire-DT configuration (SWD LED on
the device lights up green constantly).
• You have access to the device description files for the
EU5C-SWD-ETHERCAT gateway.
10.1 Integrating the EtherCAT Master

“EtherCAT | Master | EtherCAT_Master.”
The EtherCAT master appears in the configuration tree diagram.
Figure 71: Device tree diagram with EtherCAT master

Configuring the EtherCAT Master
10.2 Configuring the EtherCAT Master

▶ Double-click “EtherCAT_Master (EtherCAT Master)” in the device tree
diagram for the controller configuration.
▶ In the “General” tab, click on the <Browse> button.
Figure 72: EtherCAT master parameters
XSOFT-CODESYS-3 reports the MAC addresses and names of the existing

Ethernet interfaces of the XC300 controller.
Figure 73: List of all found Ethernet interfaces of the XC-303-C32-002 controller
▶ Select the Ethernet interface to which you have connected or will

connect the EtherCAT gateway.
▶ In the “General” tab, select the setting “Choose Network by Name.”
This allows the controller to connect to the network using its name,
such as “ETH2” regardless of the MAC address.
▶ Activate the “Automatic Restart Slaves” option so that communication
with the subscribers starts automatically.

Searching for and Integrating EtherCAT Subscribers
Figure 74: EtherCAT Master settings
10.3 Searching for and Integrating EtherCAT Subscribers

To connect the XC300 controller to an EtherCAT subscriber, such as to the
EU5C-SWD-ETHERCAT gateway, proceed as follows:
▶ Log into the XC300 controller by entering the <Online|Login> command
sequence in the XSOFT-CODESYS-3 software.
▶ Right-click on “EtherCAT_Master (...)”
▶ Then select <Scan Devices…>.
The PLC programming software performs an automatic search for all devices
connected to the EtherCAT master XC300. The results window lists all found
devices.
Figure 75: Results list of search for devices
▶ Click the <Copy All Devices to Project> button.

The devices are displayed in the device tree diagram for the controller
configuration. SWD subscribers that are already connected to the EtherCAT
gateway are also automatically shown in the tree diagram, e.g.,
EU5E_SWD_8DX.

Manually Integrating EtherCAT Subscribers
Figure 76: Tree diagram with EU5C-SWD-ETHERCAT gateway and SWD subscribers
▶ If the desired EtherCAT subscriber is not found in the list, update the
X-SOFT-CODESYS-3 version you are using or load the appropriate XML
file, ￫ section 10.6, “Description Files for EtherCAT”, page 112.
▶ Check the parameter settings for the EtherCAT gateway by double-click-
ing in the tree diagram on “EU5C-SWD-ETHERCAT (...)”

found in the “Gateway EU5C-SWD-ETHERCAT” manual, see
note ￫ page 107, and in the XSOFT-CODESYS-3 online help.
10.4 Manually Integrating EtherCAT Subscribers

Alternatively to the description in ￫ section 10.3, “Searching for and Inte-
grating EtherCAT Subscribers”, page 109, you can also add EtherCAT sub-
scribers to the XC300 controller manually. To do so, follow the steps below:
▶ Right-click on “EtherCAT_Master (...)” in the device tree diagram.
▶ Then select <Add Device…>.
Figure 77: Adding an EtherCAT device

Adding SWD Subscribers
▶ Select the corresponding EtherCAT subscriber, e.g., in the “Hilscher...”

directory, “EU5C-SWD-ETHERCAT.”
▶ In the “Add Device” window, select <Add Device> again.
The EtherCAT subscriber is added to the device tree diagram.
10.5 Adding SWD Subscribers

▶ Right-click on “EU5C_SWD_ETHERCAT(…)” in the device tree diagram
and select <Add Device>.
▶ In the “Add Device” window, select the desired SWD subscribers, e.g.,
“DIL-SWD-32-001-…”
The SWD subscribers are displayed in the device tree diagram.

found in the “Gateway EU5C-SWD-ETHERCAT” manual, see
note ￫ page 107, and in the XSOFT-CODESYS-3 online help.

Description Files for EtherCAT
10.6 Description Files for EtherCAT

Device description files in XML format are needed in order to integrate and
configure EtherCAT subscribers in XSOFT-CODESYS-3. They contain stan-
dardized descriptions of the EtherCAT subscribers and their parameters.
The device description files are automatically installed in XSOFT-CODESYS-3
with the EtherCAT master.
10.6.1 Standard XML Files

Make sure that you are working with the latest version of the device descrip-
tion files in your PLC programming environment. If subscribers are not listed,
check whether there are updates for the files in the Download Center for the
device manufacturer in question.
Example:
As an example, the EU5C-SWD-ETHERCAT gateway will be integrated and
configured as an EtherCAT subscriber. The gateway coordinates communica-
tion to and between other subscribers from SmartWire-DT.
Several device description files for the gateway and the respective Smart-
Wire-DT subscribers are required in XSOFT-CODESYS-3 for this purpose.
The current versions of the device description files are available in a zipped
file in the AUTOMATION Download Center at the following link:
ftp://ftp.moeller.net/AUTOMATION/DOWNLOAD/CONFIGURATIONFILES_CFG_GSD_EDS/
SEVERAL_PARTS/ETHERCAT/EU5C-SWD/
Save the CODESYS.zip file on your PC and unzip the file. It contains several
device description files, such as
• Eaton_ETHERCAT_Modules.xml
• Dajo_EU5C_SWD-ETHERCAT_Modules.xml
• Hilscher_SWD_ETHERCAT_GW.xml
• Phoenix_ETHERCAT_Modules.xml
• Woehner_ETHERCAT_Modules.xml
Install the device description files in the PLC programming environment, e.g.,
XSOFT-CODESYS-3.

10.6.2 Installing an XML File

If you want to install an updated XML file or an XML file from another device
manufacturer, proceed as follows:
▶ Select and download the latest version of the device description files.
▶ Save and unzip the *.zip file to a project folder of your choice.
▶ In XSOFT-CODESYS-3, select <Tools | Device Repository …>.
▶ Click the <Install…> button.
▶ In the Explorer, select the desired XML file from the project folder.
▶ Confirm the prompt “The device has been successfully installed” by
clicking “OK.”
▶ Double-click “EtherCAT_Manager (EtherCAT Manager).”
▶ Check the settings in the “EtherCAT Manager” tab.
10.6.3 Integrating Libraries for EtherCAT Communication

By default, all the libraries required for communication will be automatically
added after the EtherCAT master is added and the project is compiled for the
first time.
• IODrvEtherCAT


Configuring Modbus TCP
11 Modbus
11.1 Configuring Modbus TCP
11.1.1 Integrating the Ethernet Adapter

XSOFT-CODESYS-3 offers two different Ethernet connection options.
An Ethernet adapter can be used to define the protocol: EthernetIP or Mod-
busTCP.

▶ In the “Add Device” window, go to “Fieldbuses” and select
“Ethernet/IP | Ethernet Adapter | Ethernet.”
The Ethernet master appears in the configuration tree diagram.
Figure 78: Ethernet master parameters
11.1.2 Integrating the ModbusTCP Master and Device

▶ To integrate the Modbus TCP master into your configuration, right-click
“Ethernet (Ethernet).”
The list shows the available Ethernet devices or Ethernet-based protocols
such as Modbus.
▶ Select “Modbus | Modbus TCP Master | Modbus TCP Master.”
▶ Then select <Add Device…>
▶ Select “Modbus TCP Master” in the device tree diagram.
▶ Select “Modbus TCP Slave.”
▶ Then select <Add Device…>

Configuring Modbus TCP
Figure 79: Adding a Modbus TCP slave
The TCP master does not need any information as to which Modbus TCP
slave is connected to the bus. It only needs the IP address and the register
number of the Modbus TCP slave.
▶ Select the slave connection “Modbus_TCP_Slave” in the configuration
tree diagram.
▶ Select <Insert device>.
The Modbus TCP device is added to the configuration tree diagram.
A maximum of 32 Modbus TCP masters can be added.
11.1.3 Integrating Libraries for Modbus TCP Communication

added after the Modbus TCP master is added and the project is compiled for
the first time.
• IODrvModbusTCP
• IODrvEthernet

Configuring Modbus RTU
11.2 Configuring Modbus RTU
11.2.1 Integrating the Modbus Master

▶ In the “Add Device” window, go to “Fieldbuses” and select
“Modbus | Modbus Serial Port | Modbus COM Port.”
The Modbus COM port appears in the configuration tree diagram.
Figure 80: Modbus COM port parameters
11.2.2 Integrating Modbus Subscribers

▶ To integrate the Modbus subscriber into your configuration, right-click
“Modbus_COM_Port.”
Figure 81: Adding a Modbus device

Integrating Libraries for Modbus RTU-Communication
▶ Select the corresponding Modbus device, e.g., “Modbus Serial Device.”

▶ Select <Add Device> again.
The selected Modbus device will be added to the configuration tree diagram.
11.3 Integrating Libraries for Modbus RTU-Communication

added after the Modbus master is added and the project is compiled for the
first time.
• IODrvModbus

12 Remote Access to the Controller
The controller supports remote access via the following mechanisms
• SSH (Port: 22)
• SFTP (Port: 22)
These communication protocols are enabled in the controller by default.
The PLC acts as a server, so it can also be operated from an external source.
Corresponding entries in file /home/InitPLC can be used to disable the com-
munication protocols individually, but keep in mind that the SFTP protocol
will not work without the SSH protocol enabled.
The communication protocols use the following login information:
• User Name: XC303_User
• Password: XC303_User
The password can be changed from the XSoft-Codesys using PLC shell
command “setuserpwd.”
Using SSH
The SSH protocol can be used for remote control of the PLC. It is a text-
based protocol that can be used both to display and modify files and to start
programs.
Using SFTP
The SFTP protocol offers a mostly graphical interface for displaying and mod-
ifying files. (e.g., /home/InitPLC file)
To connect to and operate the client interface, refer to the corresponding
documents for the client in question.

SFTP Server
12.1 SFTP Server

The SFTP server is started on the device by default. Once started, file InitPlc
is read and the system parameters are set.
By default the setting in InitPlc is ENABLE_SFTP = 1.
12.1.1 Accessing the Device using the SFTP Server

To access the device via WinSCP using the SFTP server, proceed as follows:
▶ Ensure that there is communication with the device.
▶ Open WinSCP and enter the IP address for the Ethernet connection.
▶ In the “Log in as” window, enter the standard user name
“XC303_User” and the standard password “SC303_User”.
Figure 82: Logging in as a standard user
You then have access to the directory /home on the device.

SFTP Server
Figure 83: /home directory on the XC300 Modular control
The /home directory is the only directory on the device that standard users are
allowed to write to.
Directory Description
home/etc Write-protected flash area; system-specific files such as InitPlc
home/PlcPrg Contains boot project
home/PlcRts Runtime system settings
home/disk_usb Optional: only available if a USB stick is inserted
12.1.2 Changing the STFP Server Password

The password for the SFTP server can be changed using the browser com-
mand SSH -> setuserpwd.
See ￫ section 16, “PLC Shell Commands”, page 133.
12.1.3 Switching Off the SFTP Server

To switch off the SFTP server, proceed as follows:
▶ Ensure that there is communication with the device.
▶ Log in to the device as an administrator.
▶ Edit file InitPlc on the device.
▶ Set the system parameter to “ENABLE_SFTP=0.”
▶ Save the file.
▶ Restart the device.
The SFTP server is now switched off.

SFTP Server

Web visualization
13 Web-Server
The XC300 controller has a web server for sharing the visualization created
by XSOFT-CODESYS-3.
The handling of the web visualization is explained in the XSOFT-CODESYS-3
help.
Keywords: CODESYS Visualization / Object “Web Visu”
13.1 Web visualization

A description of the web visualization interface can be found in section 7.4,
“Web Visualization,” of the manual for programming PLCs with CODESYS.
The visualization can be accessed via any of the Ethernet interfaces in your
XC300 Modular control.
If the device is being operated via Ethernet interface ETH2, for example, with
the default IP address, the XC300-specific access to the web visualization
would be:
http:\\192.168.138.248:8080/webvisu.htm
https:\\192.168.138.248/webvisu.htm
If you have changed the IP address, replace the IP address in the “http:\\...”
with the address you have selected.
ATTENTION
The number of clients with simultaneous access to the XC300 is
limited to 10.
13.2 Web Server for XSOFT-CODESYS-3

Access to the web server for XSOFT-CODESYS-3 projects can be estab-
lished via either http or https protocol.
The protocol that is available is defined in file CODESYSControl.cfg by 3S.
This file can be found on the device in directory \home\PlcRts.

Web Server for XSOFT-CODESYS-3
Figure 84: Directory “PlcRts” on XC300
To change the protocol for the web server, proceed as follows:

Open the file and search for the entry for [CmpWebServer].
Depending on the parameter connection type, the protocols are permitted as
follows:
ConnectionType =
0: Only http connections allowed

1: Only https connections allowed
2: http and https connections allowed
3: http and https connections allowed, but access via http is automatically
redirected to https.

Figure 85: ConnectionType


14 OPC UA
OPC Unified Architecture (OPC UA) is a standardized communication proto-
col for data exchange between machines and facilitates universal use of all
devices.
OPC UA is supported by CODESYS version V3.5.9 or higher.
The OPC UA server is integrated into the controller. When the controller
starts, the OPC UA server automatically starts, too.
The scope of function of OPC UA is the same as OPC DA. The URL of the
OPC UA server must be entered in the OPC UA client:
“opc.tcp://<IP-Address>:4840”
As with OPC DA, the symbol list in X-SOFT-CODESYS 3 must be set up.
Additional information must be loaded on the controller in order to operate
the OPC UA server. The symbol configuration is generated during download
for this purpose.
• Basic types of derived function blocks
• Contents of attributes allocated via compiler pragmas
• Variable type (INPUT / OUTPUT / IN-OUT)
To generate the symbol configuration, proceed as follows:
▶ Select the application and open the context menu.
▶ Select “Add Object” and “Symbol Configuration.”
▶ Specify a file name.
▶ Activate the checkbox option “Support OPC UA Functions.”
▶ Confirm with “OK.”
The symbol configuration editor opens.
Here you can define all variables that should be transferred.
The symbol configuration will be updated with the next download or online
change.

15 Libraries, function blocks, and functions
The libraries contain IEC function blocks and functions that you can use,
for example, for the following tasks:
• Data exchange through the CAN bus
• Controlling the real-time clock
• Determining bus load of the CAN bus
• Triggering interrupts
• Sending/receiving data through the interfaces
￫ CoDeSys supports the user with different functions and

function blocks that are managed in libraries.
Available libraries provide support for:
• Fieldbus communication (e.g., CAN)
• Real-time clock functions
• Communication via serial interfaces
• File handling functions
The following libraries are available:

• EA_Network library for Ethernet
• IODrvEtherCAT for EtherCAT
• EA_CANopen library for CANopen
• IODrvModbus for ModbusRTU
• IODrvModbusTCP for ModbusTCP
• IODrvEthernet for ModbusTXC300 Modular controlCP
• EA_CAN types (when using EATON CAN devices)
• EA_CAN library with function blocks for CAN
• EA_XC303Events library for interrupt processing
￫ Examples of libraries available to the user:

• EA_CANopen
• IODrvModbus
• SysCom
• SysFileAsync

Using libraries
15.1 Using libraries

Libraries with frequently used functions are automatically added to a project
when a standard project is created. These include Standard.lib, for example,
with well-known elements such as the counter, timer, trigger elements, etc.
Other libraries that are automatically added are the IoStandard.lib and
3SLicense.lib.
When a project is opened the following libraries are copied to the library
manager.
• 3SLicense (system library)
• Standard.lib
• IoStandard
• BreakPointLogging
If more libraries are required for the application, you will need to install these
in the library manager.
Once the project is saved, these libraries are assigned to the project and will
be available the next time the project is opened.
15.2 Installing additional system libraries

More libraries can be installed as needed.
The following steps are necessary for this:
Figure 86: Manually installing libraries
▶ Ensure that the library to be installed is saved in a folder on your PC.

▶ Double-click “Library Manager” in the configuration tree diagram.
▶ Click on the “Add Library” option.
Figure 87: Adding a library to the library manager

Installing additional system libraries
▶ Click the “Install” button.

▶ In the Explorer, select the library in the folder where it is saved.

The new window will show the libraries available, depending on the
target system.
▶ Select “Add Library.”
Figure 88: Searching for a library in the library manager
▶ Enter a search string, such as “XN300,” so the installed library can be

found quickly.
▶ Select the library to be installed and click “OK.”
The library now appears in the Library Manager.

“EA_Network.lib” library
Figure 89: Searching for a library in the library manager
￫ The user has the option of creating their own libraries, in order to
save recurring tasks as functions or blocks in custom libraries.
15.3 “EA_Network.lib” library

The EA_Network.lib library provides functions for all Eaton controllers with
Ethernet interfaces, in order to configure these Ethernet interfaces.
￫ Manufacturer’s documentation on XSOFT-CODESYS-3,

Online help for EA-NEtwork.lib library

Accessing PLC Shell Commands
16 PLC Shell Commands

The PLC shell is a text-based control monitor. PLC shell commands for scan-
ning particular information from the PLC are entered in an entry line and sent
to the PLC as a string. The response string is displayed in a results window in
the PLC shell. This functionality can be used for diagnostic and debugging
purposes.
16.1 Accessing PLC Shell Commands

To enter a PLC shell command, proceed as follows:
▶ Establish a connection to the device.
▶ In the CoDeSys software, double-click on the device “Device (XC303)”
in the configuration tree diagram.
▶ Select the “PLC Shell” tab.
▶ In the entry line below, enter the PLC shell command or click on the “...”
button and select the desired PLC shell command by double-clicking it.
▶ Add other information to the command, if necessary, such as the baud
rate for setcomconfig.
▶ Press the Return button.
The result will be displayed.
Figure 90: PLC shell tab with result of the browser command “?”

Overview of PLC Shell Commands
16.2 Overview of PLC Shell Commands

The following PLC shell commands are available.
Table 12: PLC shell commands in alphabetical order
Command Description
? Get a list of implemented commands
applist Print list of currently loaded applications.
caninfo Display CAN controller information
canload <arg> Display of the loading of the CAN fieldbus
<arg>
<none> show CAN-Bus load.
<reset> reset CAN-Bus load statistics.
cert-getapplist Display all registered applied certificates (Component ID and application)
cert-genselfsigned Generate all self-signed certificates
[<number retrieved by “cert-getapplist”>
<expdays=>]
cert-gendhparams [len in bits] Generate parameters needed for Diffie-Hellman key exchange.
Attention: may run for several minutes!
channelinfo Return communication channel information.
copyprojtosd Copy the (boot) project onto a Multi Media Card (incl. directory structure/project directory)
copyprojtousb1) Copy the (boot) project onto the USB drive (incl. directory structure/project directory)
enabledhcp <arg> Enable DHCP function for controller; <arg>= address of adapter number
getbattery Display battery status
getcmdlist Used internally to display all available commands.
gethwinfo Show hardware information
getipconfig Display Ethernet address
getipdns Display current DNS address
getipgateway Display Gateway address
getprgprop [not implemented yet]
getprgstat [<app name>|<app index>] Get the status of one specific or all loaded applications.
getrtc Display data and time [YY:MM:DD] [HH:MM:SS]
gettimezone Show actual time zone information (offset to UTC)
getversion Show device versions list
isdhcpenabled <arg> Query whether DHCP is enabled; <arg>= address of adapter number
mem <address> [<size]> Show free memory on disk_sys. Print hex dump of specified memory region
pid [<app name>|<app index>] Output project ID
pinf [<app name>|<app index>] Output project information
plcload1) Show system performance: CPU utilization
reboot Accept changes (registry save) and restart PLC
reflect1) Mirror current command line for test purposes.
reload [<app name>|<app index>] Reload boot application
remprojfromsd Delete backup project from MicroSD card
remprojfromusb Delete backup project from USB stick
resetprg [<app name>|<app index>] Reset user program

Shell Commands for CPU Utilization
Command Description
resetprgcold [<app name>|<app index>] User program cold reset
rtsinfo runtime system information (version, IO drivers)
setipdns Set DNS address [setipdns adr1.adr2.adr3.adr4]
setipaddr <arg> ) Set IP address (<arg> = AdapterNo Adr1.Adr2.Adr3.Adr4)
setipbroadcast <arg> Set IP of broadcast address (<arg> = AdapterNo Adr1.Adr2.Adr3.Adr4)
setipnetmask <arg> Set IP subnet mask (<arg> = AdapterNo Adr1.Adr2.Adr3.Adr4)
setipgateway <arg> Set IP default gateway (<arg> = AdapterNo Adr1.Adr2.Adr3.Adr4)
setrtc1) Set date and time [YY:MM:DD] [HH:MM:SS]; example: setrtc 03:07:24 10:46:33
settimezone <arg> Set new time zone information (<arg> = offset to UTC)
startprg Start user program
stopprg Stop user program
xngetversion Show version information, show current XN driver version
xnmodules Show currently configured and connected SDIAS modules
xnvariables Show XN module variables
xnconfig Show XN module configuration variables
xnstatistics Show statistical XN data
1) You can access help in the CoDeSys software with advanced information for this PLC shell command.
Enter a question mark followed by a space before the command in the command line of the PLC browser, e.g. ? plcload
16.3 Shell Commands for CPU Utilization
plcload
The PLC shell command plcload provides information on the current system
utilization of the CPU.
This information can also be accessed via the “SysGetPlcLoad” function in
the 3S standard library SysPlcCtrl23.
A utilization of more than 95 percent can cause a failure of the serial and
Ethernet communication and/or an impairment of the real-time response.
canload
The PLC shell command canload shows the utilization of the CAN bus.
caninfo shows the baud rates and statuses of the CAN buses.
The information on the CAN bus can also be accessed using the
CAN_GetBusLoad and CAN_GetBusState functions in the EA_CAN library.

Shell Commands for CPU Utilization

17 Malfunctions
This section provides troubleshooting information for your XC300 Modular
control in case it does not behave as expected.
Malfunction Cause Remedy

XC300 will not boot up There is no 24 V DC supply voltage Check the input wiring.XC300 Modular
control

Cleaning and maintenance
18 Maintenance
18.1 Cleaning and maintenance

The devices are maintenance-free.
The following tasks may be necessary:
▶ Clean the device if it is dirty.
CAUTION
 POINTED, SHARP OBJECTS, OR CORROSIVE LIQUIDS

Do not use pointed or sharp objects (such as knives) to clean
the device.
Do not use aggressive or abrasive cleaning agents or solvents.
Make sure that no liquids get into the unit (short-circuit hazard)
and that the unit is not damaged in any way.
▶ Clean the device carefully with a clean, soft, moist cloth.

If dirt is stubborn, first spray a small amount of cleaning agent on the
moist cloth.
18.2 Repairs
For repairs, please contact your distributor or Eaton’s Technical Support.
CAUTION
 DESTRUCTION OF THE DEVICE

The device should only be opened by the manufacturer or by an
authorized repair center. Operate the device only with the hous-
ing fully closed and sealed.
For repairs, please contact your distributor or Eaton’s Technical Support.

Use the original packaging to ship the device.
18.3 Storage and transport

CAUTION
 UV LIGHT
Plastics will become brittle when exposed to UV light.
This form of artificial aging will reduce the unit’s lifespan.
Protect the device from direct sunlight or other sources of
UV radiation.

Storage and transport
CAUTION
 SHORT-CIRCUIT HAZARD
If the device is or has been exposed to environmental fluctua-
tions (ambient temperature, air humidity), condensation may
form on or inside it. As long as this condensation is present,
there will be a short-circuit hazard.
Do not switch on the device when it has condensation in or on
it.
If the device has condensation in or on it, or if the device has
been exposed to environmental fluctuations, let the device set-
tle to the existing ambient temperature before switching it on.
Do not expose the device to direct thermal radiation from heat-
ing appliances.
The specified ambient conditions must be met when transporting and storing
the equipment.
The max. ambient temperature for storage/transport must not exceed the
specified value.
￫ Before commissioning
If storing/transporting the device in cold weather conditions or in
such a way that it will be exposed to extreme differences in
temperature, make sure that no condensation forms on or
inside the device.
If there is condensation in or on the device, do not switch on the
device until it is completely dry.
▶ Use the original packaging to ship the device.

The device is sturdily built, but the components inside it are sensitive to
excessively strong vibrations and/or mechanical shock.
Accordingly, make sure to protect the device from mechanical loads that
exceed the scope of the device’s intended use.
The device should only be transported in its original packaging after being
packed properly.

Disposal
18.4 Disposal
CAUTION
INSTRUCTION
Dispose of recyclables as required by your local recycling
regulations.
DANGER
 RISK OF EXPLOSION OF LITHIUM BATTERY

The lithium battery inside the device may explode if handled
incorrectly.
▶ Dispose of the device properly.
Devices no longer being used must be professionally disposed of as per local

regulations or returned to the manufacturer or the relevant sales office.

Disposal

Dimensions and Weights
19 Appendix
19.1 Dimensions and Weights
XC-303-…
Dimensions (H x D x W) mm 80.3 x 72 x 50
inch 3.16 x 2.83 x 1.97
Space units (SU) width
Weight kg 0.3
lb 0.66
Mounting DIN-rail IEC EN 60715, 35 mm
Mounting position vertical, upright
80.3 mm (3.16")
72 mm (2.83")
50 mm (1.97")
(0.16")
4 mm
51 mm (2.01")
104.7 mm (4.12")
101.8 mm (4.01")
97 mm (3.82")
Figure 91: Dimensions of the XC303-…

Approvals and National Approvals for Devices XC300
19.2 Approvals and National Approvals for Devices XC300

XC300 and devices of the XN300 system are approved for use in several
countries and regions.
Product standards IEC/EN 61131-2

CE mark
NA Certification cULus (in progress)
Protection rating IEC: IP20

Technical Data
19.3 Technical Data
19.3.1 General ambient conditions

Unit XC-300
Ambient climatic conditions

Standards IEC/EN/DIN EN 61131-2
Ambient temperature °C -25 - +55
Storage temperature °C -40 - +80
Mounting position horizontal,
based on DIN rail
Relative humidity, no condensation (IEC/EN 60068-2-30) % 5 - 95
Air pressure (in operation) m max. 2000
Ambient mechanical conditions
Protection rating IEC: IP20
Vibration resistance
Constant amplitude (5 - 8.4 Hz) mm ±3.5 mm
Constant acceleration (8.4 - 150 Hz) g ±1.0
Shock resistance (half sinewave, 15 g/11 ms) Shocks 9
Dropped fall height (EN 60068-2-31) mm 50
Free fall, packaged (EN 60068-2-32) m 0.3
Overvoltage category II
Pollution level 2
Insulation resistance (UL 61010-2) Veff 500
Terminals Plug-in terminal block
Terminal cross-sections
Spring-type terminals
Solid mm2 0.2 - 1.5
Flexible with uninsulated ferrule mm2 0.25 - 1.5
Flexible with insulated ferrule mm2 0.25 - 0.75
Collar d mm ≦ 2.8
AWG 24–16
Stripping length mm 10
Electromagnetic compatibility (EMC) ￫ page 147
PLC
PLC microprocessor XC300 Freescale CORTEX A7 Dual core with 960 MHz
Memory
Program memory MB QSPI-FLASH: 128 MB
Working memory MB DDR-RAM: 512 MB
Data memory kByte NV-RAM: 128
Retentive data kByte 96

Technical Data
Unit XC-300
Operating System Embedded Linux Version 3.12 or higher

Watchdog yes
RTC (Real-Time Clock) yes
External storage media
Micro Secure Digital Card yes, optional
USB stick yes, optional
PLC status indicator LED, one color, green
LED, one color, red
System bus
Maximum number of bus subscribers 32
Update rate I/O image ms <1
Ethernet interfaces
Connection technology RJ45
Data transfer rate
ETH0, ETH1 MBit/s 10/100
ETH2 MBit/s 10/100/1.000
Galvanic isolation ETH0, ETH1, ETH2 from
each other yes
System bus yes
UL supply voltage I/Q1 – I/Q4 yes
RS485 yes
CAN1 yes
CAN2 yes
Local inputs yes
Local outputs yes
Connection technology RJ45
USB interface
Type of interface USB 2.0 host type A, downstream plug
Power supply for connected devices:
Rated voltage V DC 5 (-5 % +10 %)
max. current mA 100
Galvanic isolation from
System bus no
POW no
UL supply voltage I/Q1…I/Q4 yes
RS485 yes
CAN1 yes
CAN2 no
Local inputs yes
Local outputs yes

Technical Data
Electromagnetic compatibility
Interference immunity
ESD (IEC/EN 61000-4-2) Contact discharge 4 kV
Air discharge 8 kV
Electromagnetic fields (RFI): criterion A
0.8 - 1.0 GHz V/m 10
1.4 - 2.0 GHz V/m 3
2.0 - 2.7 GHz V/m 1
Burst (EN 61131-2, POW kV 2
Level 3) criterion B
ETH 0…2 kV 1
Local inputs/outputs kV 1
Surge, (EN 61131-2, POW, kV 0.5
Level 1), criterion B symmetric,
asymmetric
ETH0…2/CAN/RS485, kV 1
symmetric
Local inputs/outputs, kV 1
symmetric
Cable-controlled interference, V 10
induced by high-frequency fields
EN61131-2

Technical Data
19.3.2 Supply voltage to device and system bus

POW supply voltage to CPU Unit
Mains failure bridging
Duration of dip ms 20
Rated operating voltage
Nominal value Ue V DC 24
Permissible range V DC 18 - 30
Residual ripple % ≦5
Protection against polarity reversal yes
Input current Ie A max. 2.8A
Maximum current consumption at 24 V 8W
Galvanic isolation of POW from
system bus) no
RS485 yes
CAN1 yes
CAN2 no
Local inputs yes
Local outputs yes
ETH0, ETH1, ETH2 yes
POW status indicator LED, one color, green
UBP_24 output voltage for the XN300 slice modules
Output rated voltage V DC 24
Output current A 1.6
Short-circuit rating yes
Galvanic isolation from POW no
UBP_5 output voltage for the XN300 slice modules
Output rated voltage V DC 5
Output current A 1.6
Short-circuit rating yes
Galvanic isolation from POW no

Technical Data
19.3.3 Power Supply to Local Inputs/Outputs

Power supply to local inputs/outputs Unit
Rated operational voltage UL
Nominal value Ue V DC 24
Permissible range V DC 18 - 30
Residual ripple % ≦5
Protection against polarity reversal yes
Input current IL A max. 2
Galvanic isolation UL from
System bus yes
POW yes
RS485 yes
CAN1 yes
CAN2 yes
Local inputs no
Local outputs no
Status Indication LED, one color, green

Technical Data
19.3.4 Local inputs

Each of the transistor inputs I1 – I4 can alternatively be operated as an output
Q1 – Q4.
Digital inputs (EN 61131-2, type 1) Unit

Inputs Number 4
Input rated voltage V DC 24, observe polarity
Voltage range V DC 24 - 30
Input current per channel at rated operating voltage of 24 V mA typ. 2
Switching levels as per EN 61131-2
Limit values type “1” V DC low < 5, high > 15
Debounce setting
Off r On ms < 0.2
On r Off ms < 0.2
Can be used as interrupt inputs I1 – I4
each other no
Local outputs no
System bus yes
POW yes
RS485 yes
CAN1 yes
CAN2 yes
Cable length (unscreened) m < 30

Technical Data
19.3.5 Local outputs

Each of the transistor outputs Q1 – Q4 can alternatively be operated as
inputs I1 – I4.
The outputs are switched off when the controller is RESET.
Digital outputs
Channels Numbe 4
r
Short-circuit proof yes
Insulation voltage VAC 500
Heat dissipation per channel
Q1 – Q4 W < 0.1
Load circuits
Q1 to Q4 A 0.5
Output delay
Off r On typ 0,1 ms
On r Off typ 0,1 ms
Duty factor DF % 100
Simultaneity factor g 1
each other no
from the inputs no
System bus yes
POW yes
RS485 yes
CAN1 yes
CAN2 yes
ETH0…ETH2 yes
Cable length (unscreened) m < 30

Technical Data
19.3.6 CAN1 and CAN2 Interface

CAN(open)/easyNet Unit
Data transfer rate CAN1, CAN2 Kbits/s 50/100/125/250/500/1000
Device profile As per DS 301 V4 ???
29 Bit Identifier yes
PDO type asyn., cyc., acyc.
Connection Plug connector, 3-pin, push-in
Bus termination resistors for the first and last CAN subscriber 120 Ω switchable for
CAN1 with DIP switch TC1
CAN2 with DIP switch TC2
CANopen/easyNet subscribers Number max. 126/8
Galvanic isolation of CAN1 from
UPOW supply voltage yes
System bus yes
RS485 no
CAN2 yes
Local inputs yes
Local outputs yes
Galvanic isolation of CAN2 from
UPOW supply voltage no
System bus no
RS485 yes
CAN1 yes
Local inputs yes
Local outputs yes
ETH0…ETH2 yes
Status Indication LED, multicolor, green, red
Connection cable A shielded cable must be used for the interface.
The shield must be placed externally on two sides.

Technical Data
19.3.7 RS485 interface

RS485 serial interface (without handshaking)
Connection technology Plug connector, 3-pin, push-in
Data transfer rate as
Modbus RTU Bit/s 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200
Serial interface Bit/s 4800, 9600, 19200, 38400, 57600, 115200
Bus termination resistors for the first and last subscriber 220 Ω switchable;
For connection both DIP switches TRSa and TRSb must be set to
ON position
Galvanic isolation of RS485 from
UPOW supply voltage yes
System bus yes
CAN1 no
CAN2 yes
Local inputs yes
Local outputs yes
Status Indication LED, multicolor, green, red
Connection cable A shielded cable must be used for the interface.
The shield must be placed externally on two sides.

Glossary
19.4 Glossary
AWL Application list
Boot project Project loaded from the non-volatile memory of the CPU
Debounce setting The debounce setting defines the delay of a pulse edge from the input terminal I1 – I4
to the GPIO of the CPU.
Forcing Presetting of changed operators/variables to a fixed value
/home Top file directory in the controller XC300 XC300 Modular control which a user with status
“XC-303_user” can access
MicroSD Micro Secure Digital Card
OS Operating System
PLC Memory Programmable Logic Controller
POU Programming Organizational Unit
A POU type object is a programming organizational unit in a CoDeSys project.
Source code for your PLC program is written in POUs.
PRG Program
RC Remote Control
RTS Runtime System
Task Process, task carried out by the operating system

Index
Symbols E
/home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 easyNet Interface . . . . . . . . . . . . . . . . . . . . . . 24, 45
EA_XC303Events . . . . . . . . . . . . . . . . . . . . . . . . . 82
A EDS file
Address overlaps . . . . . . . . . . . . . . . . . . . . . . . . . . 74 installing . . . . . . . . . . . . . . . . . . . . . . . . . 105, 113
Addressing Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Inputs/outputs and markers . . . . . . . . . . . . . 74 Electromagnetic interference . . . . . . . . . . . . . . . 27
Addressing markers . . . . . . . . . . . . . . . . . . . . . . . 74 Electronic data sheet . . . . . . . . . . . . . . . . . . . . . 104
Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . 22
B EU5C-SWD-ETHERCAT
Boot application Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
On MicroSD . . . . . . . . . . . . . . . . . . . . . . . . . . 58
On USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 F
Boot project Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
deleting, on SD/MMC . . . . . . . . . . . . . . . . . . 58 Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
deleting, on USB stick . . . . . . . . . . . . . . . . . . 58 Function blocks . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Browser commands . . . . . . . . . . . . . . . . . . . . . . 133 DisableInterrupt . . . . . . . . . . . . . . . . . . . . . . . 82
EnableInterrupt . . . . . . . . . . . . . . . . . . . . . . . . 83
C Read…Direct . . . . . . . . . . . . . . . . . . . . . . . . . 73
Cable protection . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Write…Direct . . . . . . . . . . . . . . . . . . . . . . . . . 73
Cable routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CAN H
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Help for browser commands . . . . . . . . . . . . . . . 135
interface, assignment . . . . . . . . . . . . . . . . . . 45 Home directory . . . . . . . . . . . . . . . . . . . . . . . . . . 120
telegrams, sending/receiving from user
program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 I
CAN Connection Cable . . . . . . . . . . . . . . . . . . . . . 26 Inductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 InitPLC file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Connect PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Inputs
Connection addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Inputs/outputs . . . . . . . . . . . . . . . . . . . . . . . . . 40 Signal status . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Interrupt actuators . . . . . . . . . . . . . . . . . . . . . 42 Wiring example . . . . . . . . . . . . . . . . . . . . . . . 40
PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Installation instructions . . . . . . . . . . . . . . . . . . . . . . 8
Connection setup . . . . . . . . . . . . . . . . . . . 80, 81, 87 Interface
CPU CANopen, assignment . . . . . . . . . . . . . . . . . 45
Operating status indicators . . . . . . . . . . . . . . 51 easyNet, assignment . . . . . . . . . . . . . . . . . . . 45
Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 USB, assignment . . . . . . . . . . . . . . . . . . . . . . 43
Cyclic task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
D actuators, connecting . . . . . . . . . . . . . . . . . . 42
Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . 51, 133 CAN Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Device arrangement . . . . . . . . . . . . . . . . . . . . . . . 28 inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Documentation, online . . . . . . . . . . . . . . . . . . . . . . 8
Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

L RJ45 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
LED RS485 cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
PRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 S
LED display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Library,installing . . . . . . . . . . . . . . . . . . . . . . . . . . 130 SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120, 123
Lightning Protection . . . . . . . . . . . . . . . . . . . . . . . 37 Shielding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Limit values, for memory usage . . . . . . . . . . . . . 73 Signal status of inputs/outputs . . . . . . . . . . . . . . 17
Loading programs . . . . . . . . . . . . . . . . . . . . . . . . . 57 Simulation, updating outputs . . . . . . . . . . . . . . . . 50
Single Cycle Mode . . . . . . . . . . . . . . . . . . . . . . . . 52
M Single-step mode . . . . . . . . . . . . . . . . . . . . . . . . . 52
Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Standards
Memory IEC 60364 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 IEC 60364-4-41 . . . . . . . . . . . . . . . . . . . . . . . . . I
usage, limit values . . . . . . . . . . . . . . . . . . . . . 73 IEC/EN 60204-1 . . . . . . . . . . . . . . . . . . . . . . . . I
MMC memory card . . . . . . . . . . . . . . . . . . . . . . . . 19 Startup Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Monitoring time, Task . . . . . . . . . . . . . . . . . . . . . . 70 Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Mounting position . . . . . . . . . . . . . . . . . . . . . . . . . 28 Status indicators under the front panel . . . . . . . 54
Mounting the XC300 . . . . . . . . . . . . . . . . . . . . . . . 28 Stripping length . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Multimedia card . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Supply Voltage
Multitasking . . . . . . . . . . . . . . . . . . . . . . . . . . . 63, 67 For processor unit and local inputs/outputs 17
switching off/interruption (behavior) . . . . . . 51
O Suppressor Circuit for Interference Sources . . . 36
Online documentation . . . . . . . . . . . . . . . . . . . . . . 8 Switching threshold . . . . . . . . . . . . . . . . . . . . . . . 17
Operating states CPU (LED display) . . . . . . . . . . 51 System
Operating System, Update . . . . . . . . . . . . . . . . . 59 events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Outputs libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Signal status . . . . . . . . . . . . . . . . . . . . . . . . . . 17 parameters, assigning (in file InitPLC) . . . . . 88
Wiring example . . . . . . . . . . . . . . . . . . . . . . . . 40 times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
utilization, CPU . . . . . . . . . . . . . . . . . . . . . . . 135
P System block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
plcload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 System events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Potential Relationships . . . . . . . . . . . . . . . . . . . . . 34 System memory
Power down logic . . . . . . . . . . . . . . . . . . . . . . . . . 17 disk_sd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Priority (task) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Disk_USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Program
call (task) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 T
processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Task
start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 cyclic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
programming software monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Testing and Commissioning . . . . . . . . . . . . . . . . 51
R Type (task condition) . . . . . . . . . . . . . . . . . . . . . . . 63
Real-time clock (RTC) . . . . . . . . . . . . . . . . . . . . . . 18
Removing the XN300 slice modules . . . . . . . . . 31
Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

U
Updating outputs during simulation . . . . . . . . . . 50
USB interface, assignment . . . . . . . . . . . . . . . . . 43
USB stick . . . . . . . . . . . . . . . . . . . . . . . . . . 18, 19, 21
V
Ventilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Voltage dip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
W
Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Monitoring a task . . . . . . . . . . . . . . . . . . . . . . 70
Web visualization . . . . . . . . . . . . . . . . . . . . . . . . . 123
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Wiring example
Inputs/outputs . . . . . . . . . . . . . . . . . . . . . . . . . 40
Working memory . . . . . . . . . . . . . . . . . . . . . . . . . . 19
X
XML file
Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
XN300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

At Eaton, we’re energized by the challenge of powering a world that Eaton addresses worldwide:
demands more. With over 100 years experience in electrical power
management, we have the expertise to see beyond today. www.eaton.com
From groundbreaking products to turnkey design and engineering
services, critical industries around the globe count on Eaton.
E-Mail: [email protected]
We power businesses with reliable, efficient and safe electrical power
management solutions. Combined with our personal service, support Internet: www.eaton.eu/xc300
and bold thinking, we are answering tomorrow’s needs today.
Follow the charge with Eaton. Eaton Industries GmbH
Hein-Moeller-Str. 7 – 11
Visit: www.eaton.com/electrical D-53115 Bonn
© 2018 by Eaton Corporation

All rights reserved
MN050005EN ETN/ICPD MOC 02/18

XC-303 MN050005 - en PDF

Uploaded by

Copyright:

Available Formats

XC-303 MN050005 - en PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XC-303 MN050005 - en PDF

Uploaded by

Copyright:

Available Formats

Manual 02/18 MN050005EN

For customers in US/Canada contact:

Original operating manual

Author: Thomas Hettwer

All rights reserved, also for the translation.

Before commencing the installation

XC300 Modular control 02/18 MN050005EN www.eaton.com 1

4 Configuring the Controller ........................................................ 63

2 XC300 Modular control 02/18 MN050005EN www.eaton.com

6 Configuring and parametizing Inputs/Outputs....................... 81

7 Assigning System Parameters.................................................. 87

XC300 Modular control 02/18 MN050005EN www.eaton.com 3

12 Remote Access to the Controller ............................................. 119

14 OPC UA ....................................................................................... 127

15 Libraries, function blocks, and functions................................. 129

16 PLC Shell Commands ................................................................ 133

4 XC300 Modular control 02/18 MN050005EN www.eaton.com

XC300 Modular control 02/18 MN050005EN www.eaton.com 5

0 About This Manual

￫ Shorter name XC300

￫ For up-to-date information about the XC300 Modular control

0.1 Target group

XC300 Modular control 02/18 MN050005EN www.eaton.com 7

0.2 Change protocol

02/18 First edition – – –

0.3 Additional documentation

￫ The documents mentioned in this manual, as well as this

0.4 Legal Disclaimer

8 XC300 Modular control 02/18 MN050005EN www.eaton.com

Hazards posed by the XC300 cannot be eliminated if the safety instructions

0.5 I/O system XN300

￫ For up-to-date information about the I/O system XN300, refer to

XC300 Modular control 02/18 MN050005EN www.eaton.com 9

0.6 Writing Conventions

Hazard warnings of personal injury

 Warns of the possibility of hazardous situations that may pos-

 Warns of the possibility of hazardous situations that could result

 Warns of hazardous situations that result in serious injury or

￫ Indicates useful tips.

▶ Indicates actions to be taken.

10 XC300 Modular control 02/18 MN050005EN www.eaton.com

1.1 System overview

b Assignment based on device type

Figure 1: Structure of the XC300

a Bus connector to the I/O system XN300

XC300 Modular control 02/18 MN050005EN www.eaton.com 11

￫ To program the XC300, the programming software

1.2 Communication and Interfaces – Decentralized Expansion

12 XC300 Modular control 02/18 MN050005EN www.eaton.com

1.3 Intended Use

 DUE TO AUTOMATED START-UP

XC300 Modular control 02/18 MN050005EN www.eaton.com 13

1.4 Device Overview

⑧ I/Q3 f 24 V DC POW supply voltage

14 XC300 Modular control 02/18 MN050005EN www.eaton.com

XC300 Modular control 02/18 MN050005EN www.eaton.com 15

1.5 Model code XC300

Number of CAN interfaces

Product series 300