2.6Influencing of the PWMi output value by the parameters ............................................................. 16
3 Basics of EtherCAT .................................................................................................................................17
4 Mounting and cabling .............................................................................................................................27
7.4Support and Service ................................................................................................................... 114
EP8309-10224Version: 2.0.0
Page 5
Foreword
1Foreword
1.1Notes on the documentation
Intended audience
This description is only intended for the use of trained specialists in control and automation engineering who
are familiar with the applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing
and commissioning these components.
It is the duty of the technical personnel to use the documentation published at the respective time of each
installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, Safety over EtherCAT®, TwinSAFE®, XFC® and XTS® are registered
trademarks of and licensed by Beckhoff Automation GmbH.
Other designations used in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents: EP1590927, EP1789857, DE102004044764, DE102007017835 with corresponding applications or
registrations in various other countries.
The TwinCAT Technology is covered, including but not limited to the following patent applications and
patents: EP0851348, US6167425 with corresponding applications or registrations in various other countries.
EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany
Please note the following safety instructions and explanations!
Product-specific safety instructions can be found on following pages or in the areas mounting, wiring,
commissioning etc.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the
documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are
familiar with the applicable national standards.
Description of symbols
In this documentation the following symbols are used with an accompanying safety instruction or note. The
safety instructions must be read carefully and followed without fail!
DANGER
WARNING
CAUTION
Attention
Note
Serious risk of injury!
Failure to follow the safety instructions associated with this symbol directly endangers the
life and health of persons.
Risk of injury!
Failure to follow the safety instructions associated with this symbol endangers the life and
health of persons.
Personal injuries!
Failure to follow the safety instructions associated with this symbol can lead to injuries to
persons.
Damage to the environment or devices
Failure to follow the instructions associated with this symbol can lead to damage to the environment or equipment.
Tip or pointer
This symbol indicates information that contributes to better understanding.
EP8309-10226Version: 2.0.0
Page 7
Foreword
1.3Documentation Issue Status
VersionComment
2.0.0• Migration
• Technical data updated
1.1.0• Power Connection updated
1.0.0• First release
Firmware and hardware versions
This documentation refers to the firmware and hardware version that was applicable at the time the
documentation was written.
The module features are continuously improved and developed further. Modules having earlier production
statuses cannot have the same properties as modules with the latest status. However, existing properties
are retained and are not changed, so that older modules can always be replaced with new ones.
Documentation
Version
2.0.00606
1.0.00603
The firmware and hardware version (delivery state) can be found in the batch number (D-number) printed on
the side of the EtherCATBox.
Syntax of the batch number (D-number)
WWYYFFHH
WW - week of production (calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Example with D-no.: 25 13 06 03:
25 - week of production 25
13 - year of production 2013
06 - firmware version 06
03 - hardware version 03
EP8309-0002
FirmwareHardware
EP8309-10227Version: 2.0.0
Page 8
Product Overview
2Product Overview
2.1EtherCAT Box - Introduction
The EtherCAT system has been extended with EtherCAT Box modules with protection class IP67. Through
the integrated EtherCAT interface the modules can be connected directly to an EtherCAT network without an
additional Coupler Box. The high-performance of EtherCAT is thus maintained into each module.
The extremely low dimensions of only 126x30x26.5 mm (hxw xd) are identical to those of the Fieldbus
Box extension modules. They are thus particularly suitable for use where space is at a premium. The small
mass of the EtherCAT modules facilitates applications with mobile I/O interface (e.g. on a robot arm). The
EtherCAT connection is established via screened M8connectors.
Fig.1: EtherCAT Box Modules within an EtherCAT network
The robust design of the EtherCAT Box modules enables them to be used directly at the machine. Control
cabinets and terminal boxes are now no longer required. The modules are fully sealed and therefore ideally
prepared for wet, dirty or dusty conditions.
Pre-assembled cables significantly simplify EtherCAT and signal wiring. Very few wiring errors are made, so
that commissioning is optimized. In addition to pre-assembled EtherCAT, power and sensor cables, fieldconfigurable connectors and cables are available for maximum flexibility. Depending on the application, the
sensors and actuators are connected through M8 or M12connectors.
The EtherCAT modules cover the typical range of requirements for I/O signals with protection class IP67:
• digital inputs with different filters (3.0ms or 10μs)
• digital outputs with 0.5 or 2A output current
• analog inputs and outputs with 16bit resolution
• Thermocouple and RTD inputs
• Stepper motor modules
XFC (eXtreme Fast Control Technology) modules, including inputs with time stamp, are also available.
EP8309-10228Version: 2.0.0
Page 9
Fig.2: EtherCAT Box with M8 connections for sensors/actuators
Product Overview
Fig.3: EtherCAT Box with M12 connections for sensors/actuators
Basic EtherCAT documentation
You will find a detailed description of the EtherCAT system in the Basic System Documen-
Note
tation for EtherCAT, which is available for download from our website (www.beckhoff.com)
under Downloads.
XML files
You will find XML files (XML Device Description Files) for Beckhoff EtherCAT modules on
Note
our website (www.beckhoff.com) under Downloads, in the Configuration Files area.
EP8309-10229Version: 2.0.0
Page 10
Product Overview
2.2EP8309 - Introduction
Fig.4: EP8309
EtherCAT Box with different digital and analog inputs and outputs
The EP8309-x022 EtherCAT Box has various digital and analog inputs and outputs.
The analog signals can be processed and output in the range 0/4…20mA, the digital signals in the range
24VDC.
The possible output currents are different and can be found in the technical data.
The resolution for the current signals takes place with 12bits, signed. This applies to input and output
signals.
The signal channels and the 24VDC supply have a common ground potential.
A PWMi output is integrated for connecting a proportional valve. For valves with integrated electronics, this
output can alternatively be operated as an analog current output with continuous 24V supply for the valve.
Quick links
• Installation [}27]
• Configuration [}48]
• UL requirements [}44]
EP8309-102210Version: 2.0.0
Page 11
Product Overview
2.3EP8309 - Technical data
Fieldbus
Technical DataEP8309-x022
FieldbusEtherCAT
Fieldbus connection2 x M8 socket (green)
Tacho inputs
Technical DataEP8309-x022
Number of tacho inputs1 or 2 (dual-shaft mode or single-shaft mode)
Input typeSingle-shaft mode: two digital sensors on a
common axis
Dual-shaft mode: two digital sensors on two
different axes, no direction detection, no error
detection)
Tacho inputs connection [}41]
Rated input voltage24VDC (-15%/+20%)
Input filter2.5kHz
Signal voltage "0"-3...+5V (EN61131-2, type3)
Signal voltage "1"+11...+30V (EN61131-2, type3)
Input currenttypically 3mA (EN61131-2, type3)
Sensor supplyfrom the control voltage Us
Current consumption of the sensorsmax. 0.5A, short-circuit-proof overall
M12
Digital inputs and outputs (DIO)
Technical DataEP8309-x022
Number of digital inputs and outputs (DIO) [}42]
Inputs
Input connectionsM12
Rated input voltage24VDC (-15%/+20%)
Input filter3.0ms
Signal voltage "0"-3...+5V (EN61131-2, type3)
Signal voltage "1"+11...+30V (EN61131-2, type3)
Input currenttypically 3mA (EN61131-2, type3)
Sensor supplyfrom the control voltage Us
Current consumption of the sensorsmax. 0.5A, short-circuit-proof overall
Outputs
Output connectionsM12
Load typeohmic, inductive, lamp load
Rated output voltage24VDC (-15%/+20%)
Output currentmax. 0.5A per channel for sockets 4 and 5
Short circuit currenttypically 1.5A
Output driver supplyfrom load voltage Up
Output driver current consumptiontypically 8 mA per channel
8
max. 1.0A per channel for sockets 6 and 7
EP8309-102211Version: 2.0.0
Page 12
Product Overview
PWM outputs
Technical DataEP8309-x022
Number of PWM outputs (alternatively analog output)1
Output connections [}43]
Load typeohmic/inductive > 1mH
Supply for the output stage24VDC via power contacts
Output current per channel1.2 A (short-circuit-proof, common thermal overload
Signal type0…20 mA or 4…20 mA (can be set for each CoE)
Input resistance85 Ω typ. + diode voltage
Resolution12bit (including sign)
Input filter limit frequency5kHz
Conversion timeapprox. 100 µs
Measuring error< 0,3% (relative to full scale value)
M12
warning for both output stages)
M12 sockets
Analog outputs (AO)
Technical DataEP8309-x022
Number of analog outputs (alternatively PWMi output)1
Output connections [}43]
Signal type0…20 mA or 4…20 mA (can be set for each CoE)
Load<500Ω
Resolution12bit
Conversion timeapprox. 40 µs
Measuring error< 0,3% (relative to full scale value)
M12 sockets
EP8309-102212Version: 2.0.0
Page 13
Product Overview
General technical data
Technical DataEP8309-x022
Special featuresMulti-function module
Module electronic supplyfrom the control voltage Us
Module electronic current consumptiontypically 120mA
Sensor supplyfrom load voltage Up, DC, any value up to 30V
Actuator supplyfrom load voltage Up, DC, any value up to 30V
Power supply connectionPower supply: 1 x M8 plug, 4-pole
Onward connection: 1 x M8 socket, 4-pole
Process imageInputs: 2 x 16bit
Outputs: 2 x 16bit
Electrical isolationControl voltage/ fieldbus: 500V
Weightapprox. 165g
Permissible ambient temperature during operation-25°C ... +60°C
Permissible ambient temperature during storage-40°C ... +85°C
Vibration/ shock resistanceconforms to EN60068-2-6 / EN60068-2-27
EMC immunity/emissionconforms to EN61000-6-2 / EN61000-6-4
Protection classIP65, IP66, IP67 (according to EN 60529)
Installation positionvariable
ApprovalsCE, cULus
2.4EP8309 - Process image
In the default setting the EP8309 is configured for:
• analog input channel 1
• analog input channel 2
• Tacho signal from two sensors on one axis (single-shaft mode)
• 6 digital inputs
• Status of PWM output
• Acknowledge / Reset in the event of a PWM error.
• 6 digital outputs
• General EtherCAT process data
AI Inputs Channel1 and 2
The data for the first analog channel can be found under AI Inputs
Channel1.
Underrange: Value of the analog input is less than 0/4mA or -10/0V
Overrange: Value of the analog input is greater than 20mA or +10V
Limit 1: with activated Limit 1 (object 0x8000:07 [}80]= 1) means
1:value less than limit 1 (set in object 0x8000:13 [}80])
2:value greater than limit 1 (set in object 0x8000:13 [}80])
3:value equal to limit 1 (set in object 0x8000:13 [}80])
Limit 2: with activated Limit 2 (object 0x8000:08 [}80]= 1) means
1:value less than limit 2 (set in object 0x8000:14 [}80])
2:value greater than limit 2 (set in object 0x8000:14 [}80])
3:value equal to limit 2 (set in object 0x8000:14 [}80])
Error: This bit is set if over- or under-range was detected.
EP8309-102213Version: 2.0.0
Page 14
Product Overview
Tacho single-shaft mode (depending on the setting in the PDO assignment)
The data for the tacho input can be found under TACHO Single Shaft
Mode Input Channel 1.
see data under commissioning
Tacho dual-shaft mode (depending on the setting in the PDO assignment)
The data for the tacho input can be found under TACHO Dual Shaft
Mode Input Channel 1 or 2.
see data under commissioning
DIG Inputs
PWM Status
DEV Inputs
TACHO Output Channel 1
The data for the digital inputs can be found under DIG Inputs.
X4 Pin4 -> socket 4, pin 4
....
The data for the PWM output can be found under PWM Status
The diagnostic data for the two voltages Us and Up can be found under
DEV Inputs.
TRUE = voltage <= approx. 18 V
DC
....
The control data for the tacho input can be found under TACHO OutputChannel 1.
Reset Error - error reset
EP8309-102214Version: 2.0.0
Page 15
Product Overview
DO Outputs
The data for the digital outputs can be found under DO Outputs.
X5 pin4 -> socket 5, pin 4
....
PWM control (activated through PDO assignment 0x1602, default PWM, alternatively AO)
The control data for the PWM output can be found under PWM Control.
Enable Dithering -> activate dithering
Enable -> activate PWM output
Reset -> reset on error
PWM output -> load-independent current, depending on module rating
(e.g. 1.2 A and setting in object 0x8060:10)
AO outputs (activated throughPDO assignment 0x1603), not activated by default
The values for the analog output can be found under AO Outputs.
Analog Output - output value
2.5Pulse width modulation (PWM)
The Beckhoff terminals and box modules integrate compact PWM output stages in the smallest of designs.
PWM output stages control the output current through pulse width modulation (PWM) of the supply voltage.
This means that the full supply voltage is activated or deactivated at the output. The duty cycle (pulse width)
is modified, but not the voltage level. The current is built up based on the load connected to the inductance.
Fig.5: Operation at load with adequate inductance
Fig.6: Operation at load with inadequate inductance (near ohmic)
EP8309-102215Version: 2.0.0
Page 16
Product Overview
The figure Operation at load with inadequate inductance (virtually ohmic) illustrates operation with an
inadequate inductance. Continuous current flow is not reached. The current has "gaps". This mode of
operation is not permitted.
Pulse width current terminals require inductive loads
The load inductance should have a minimum inductance of 1 mH. Operation of the pulse
Note
width current terminals at loads with an inductance of less than 1 mH is not recommended,
since the intermittent current flow prevents reference between the set value and the arithmetic mean of the current.
2.6Influencing of the PWMi output value by the
parameters
Fig.7: Influencing of the PWMi output value
EP8309-102216Version: 2.0.0
Page 17
Basics of EtherCAT
3Basics of EtherCAT
3.1EtherCAT basics
Basic information on the EtherCAT fieldbus can be found in the EtherCAT system documentation.
3.2Watchdog setting
General information on watchdog settings
The ELxxxx Terminals and EPxxxx Box Modules are equipped with a safety device (watchdog) that switches
the outputs to a safe state after a time that can be preset, for example in the case of interrupted process data
traffic, or to OFF, for example depending on device and setting.
The EtherCAT Slave Controller (ESC) has two watchdogs:
• SM watchdog (default: 100 ms)
• PDI watchdog (default: 100 ms)
SM Watchdog (SyncManagerWatchdog)
The SyncManager watchdog is reset after each successful EtherCAT process data communication with the
terminal/box. If no EtherCAT process data communication takes place with the terminal/box for longer than
the set and activated SM watchdog time, e.g. in the event of a line interruption, the watchdog is triggered and
the outputs are set to FALSE. The OP status of the terminal/box is unaffected by this. The watchdog is only
reset after a successful EtherCAT process data access. Set the monitoring time as specified below.
The SyncManager watchdog monitors correct and timely process data communication with the ESC from the
EtherCAT side.
PDI watchdog (process data watchdog)
If no PDI communication with the EtherCAT slave controller (ESC) takes place for longer than the set and
activated PDI watchdog time, this watchdog is triggered.
PDI (Process Data Interface) is the internal interface between the ESC and local processors in the EtherCAT
slave, for example. The PDI watchdog can be used to monitor this communication for failure.
The PDI watchdog monitors correct and timely process data communication with the ESC but from the
application side.
The SM and PDI watchdogs should be set separately for each slave in the TwinCAT System Manager:
• Each watchdog has its own timer setting, which together with the multiplier results in a time.
• Important: The multiplier/timer setting is loaded into the slave on start-up, if the corresponding
checkbox is ticked. If the checkbox is not ticked, no download takes place, and the ESC setting
remains unchanged.
Multiplier
Both watchdogs receive their pulses from the local terminal/box clock, divided by the watchdog multiplier.
1/25 MHz * (watchdog multiplier + 2) = 100µs (for default setting of 2498 for the multiplier)
The standard setting of 1000 for the SM watchdog corresponds to a release time of 100 ms.
The value in multiplier + 2 corresponds to the number of basic 40ns ticks representing a watchdog tick.
The multiplier can be modified in order to adjust the watchdog time over a larger range.
Example "Set SM watchdog"
This checkbox enables manual setting of the watchdog times. If the outputs are set and the EtherCAT
communication is interrupted, the SM watchdog is triggered after the set time and the outputs are deleted.
This setting can be used for adapting a terminal to a slower EtherCAT master or long cycle times. The
default SM watchdog setting is 100 ms. The setting range is from 0 to 65535. Together with a multiplier in a
range from 1 to 65535, this covers a watchdog period of 0 to ~170 seconds.
Calculation
Multiplier = 2498 → watchdog base time = 1 / 25MHz * (2498 + 2) = 0.0001seconds = 100µs
SM watchdog = 10000 → 10000 * 100µs = 1second watchdog monitoring time
EP8309-102218Version: 2.0.0
Page 19
CAUTION
CAUTION
Note
Basics of EtherCAT
Caution! Unintended behavior of the system is possible!
The function for switching off of the SM watchdog via SM watchdog = 0 is only implemented in terminals from version -0016. In previous versions this operating mode should
not be used.
Caution! Damage to the equipment and unintended behavior of the system is
possible!
If the SM watchdog is activated and a value of 0 is entered the watchdog switches off completely. This is watchdog deactivation! Outputs are then NOT set to a safe state, in the
event of an interruption in communication!
Outputs in SAFEOP
Watchdog monitoring is activated by default. It sets the outputs in the module to a safe
state (e.g. OFF), depending on the SAFEOP and OP settings, and depending on the device
and its settings. If this is prevented due to deactivation of watchdog monitoring in the module, outputs can be switched or remain set in device state SAFEOP.
EP8309-102219Version: 2.0.0
Page 20
Basics of EtherCAT
3.3EtherCAT State Machine
The state of the EtherCAT slave is controlled via the EtherCAT State Machine (ESM). Depending upon the
state, different functions are accessible or executable in the EtherCAT slave. Specific commands must be
sent by the EtherCAT master to the device in each state, particularly during the bootup of the slave.
A distinction is made between the following states:
• Init
• Pre-Operational
• Safe-Operational and
• Operational
• Boot
The regular state of each EtherCAT slave after bootup is the OP state.
Fig.9: EtherCAT State Machine
Init
After switch-on the EtherCAT slave in the Init state. No mailbox or process data communication is possible.
The EtherCAT master initializes sync manager channels 0 and 1 for mailbox communication.
Pre-Operational (Pre-Op)
During the transition between Init and Pre-Op the EtherCAT slave checks whether the mailbox was initialized
correctly.
In Pre-Op state mailbox communication is possible, but not process data communication. The EtherCAT
master initializes the sync manager channels for process data (from sync manager channel 2), the FMMU
channels and, if the slave supports configurable mapping, PDO mapping or the sync manager PDO
assignment. In this state the settings for the process data transfer and perhaps terminal-specific parameters
that may differ from the default settings are also transferred.
Safe-Operational (Safe-Op)
During transition between Pre-Op and Safe-Op the EtherCAT slave checks whether the sync manager
channels for process data communication and, if required, the distributed clocks settings are correct. Before
it acknowledges the change of state, the EtherCAT slave copies current input data into the associated DPRAM areas of the EtherCAT slave controller (ECSC).
EP8309-102220Version: 2.0.0
Page 21
Basics of EtherCAT
Mailbox and process data communication is possible in the Safe-Op state, but the slave keeps its outputs in
the safe state. However, the input data are cyclically updated.
Operational (Op)
Before the EtherCAT master switches the EtherCAT slave from Safe-Op to Op it must transfer valid output
data.
In the Op state the slave copies the output data of the masters to its outputs. Process data and mailbox
communication is possible.
Boot
In the Boot state the slave firmware can be updated. The Boot state can only be reached via the Init state.
In the Boot state mailbox communication via the file access over EtherCAT (FoE) protocol is possible, but no
other mailbox communication and no process data communication.
EP8309-102221Version: 2.0.0
Page 22
Basics of EtherCAT
3.4CoE interface
General description
The CoE interface (CANopen over EtherCAT) is used for parameter management of EtherCAT devices.
EtherCAT slaves or the EtherCAT master manage fixed (read only) or variable parameters which they
require for operation, diagnostics or commissioning.
CoE parameters are arranged in a table hierarchy. In principle, the user has read access via the fieldbus.
The EtherCAT master (TwinCAT System Manager) can access the local CoE lists of the slaves via
EtherCAT in read or write mode, depending on the properties.
Different CoE parameter types are possible, including string (text), integer numbers, Boolean values or larger
byte fields. They can be used to describe a wide range of features. Examples of such parameters include
manufacturer ID, serial number, process data settings, device name, calibration values for analog
measurement or passwords.
Organization takes place on 2 levels by means of hexadecimal numbering: the (main) index is named first,
then the subindex. The value ranges are:
• Index 0 to 65535
• Subindex: 0…255
A parameter localized in this way is normally written as x8010:07, with preceding "x" to identify the
hexadecimal numerical range and a colon between index and subindex.
The relevant ranges for EtherCAT fieldbus users are:
• x1000: This is where fixed identity information for the device is stored, including name, manufacturer,
serial number etc., plus information about the current and available process data configurations.
• x8000: This is where the operational and functional parameters for all channels are stored, such as
filter settings or output frequency.
Other important ranges are:
• x4000: In some EtherCAT devices the channel parameters are stored here (as an alternative to the
x8000 range).
• x6000: Input PDOs ("input" from the perspective of the EtherCAT master)
• x7000: Output PDOs ("output" from the perspective of the EtherCAT master)
Availability
Not every EtherCAT device must have a CoE list. Simple I/O modules without dedicated
Note
If a device has a CoE list, it is shown in the TwinCAT System Manager as a separate tab with a listing of the
elements:
processor usually have no variable parameters and therefore no CoE list.
EP8309-102222Version: 2.0.0
Page 23
Basics of EtherCAT
Fig.10: CoE-Online tab
The CoE objects from x1000 to x1600, which are available in the example device "EL2502", can be seen in
the above figure; the subindices from x1018 are expanded.
Data management
Some parameters, particularly the setting parameters of the slave, are configurable and writeable. This can
be done in write or read mode
• via the System Manager (figure above) by clicking. This is useful for commissioning of the system/
slaves. Click on the row of the index to be parameterized and enter a value in the SetValue dialog.
• from the control system/PLC via ADS, e.g. through function blocks from the TcEtherCAT.lib library This
is recommended for modifications while the system is running or if no System Manager or operating
staff are available.
Data management
If CoE parameters on the slave are changed online, this is saved fail-safe in the device
Note
Startup list
(EEPROM) in Beckhoff devices. This means that the changed CoE parameters are still retained after a restart. The situation may be different with other manufacturers.
Startup list
Changes in the local CoE list of the terminal are lost if the terminal is replaced. If a termi-
Note
nal is replaced with a new Beckhoff terminal, it will have the factory settings. It is therefore
advisable to link all changes in the CoE list of an EtherCAT slave with the Startup list of
the slave, which is processed whenever the EtherCAT fieldbus is started. In this way a replacement EtherCAT slave can automatically be parameterized with the specifications of
the user.
If EtherCAT slaves are used which are unable to store local CoE values permanently, the
Startup list must be used.
Recommended approach for manual modification of CoE parameters
• Make the required change in the System Manager. The values are stored locally in the EtherCAT slave
EP8309-102223Version: 2.0.0
Page 24
Basics of EtherCAT
• If the value is to be stored permanently, enter it in the Startup list. The order of the Startup entries is
usually irrelevant.
Fig.11: Startup list in the TwinCAT System Manager
The Startup list may already contain values that were configured by the System Manager based on the ESI
specifications. Additional application-specific entries can be created.
Online/offline directory
While working with the TwinCAT System Manager, a distinction has to be made whether the EtherCAT
device is "available", i.e. switched on and linked via EtherCAT and therefore online, or whether a
configuration is created offline without connected slaves.
In both cases a CoE directory is visible according to the figure "CoE-Online tab", but the connectivity is
displayed as offline/online.
If the slave is offline
• the offline list from the ESI file is displayed. In this case modifications are not meaningful or possible.
• the configured status is shown under Identity
• no firmware or hardware version is displayed, since these are features of the physical device.
• Offline is shown in red
EP8309-102224Version: 2.0.0
Page 25
Basics of EtherCAT
Fig.12: Offline list
If the slave is online
• the actual current slave directory is read. This may take several seconds, depending on the size and
cycle time.
• the actual identity is displayed
• the firmware and hardware version of the equipment according to the electronic information is
displayed.
• Online is shown in green
Fig.13: Online list
EP8309-102225Version: 2.0.0
Page 26
Basics of EtherCAT
Channel-based order
The CoE directory is located in EtherCAT devices that usually encompass several functionally equivalent
channels. e.g. a 4-channel 0 – 10 V analog input terminal also has 4 logical channels and thus 4 identical
sets of parameter data for the channels. In order to avoid having to list each channel in the documentation,
the placeholder "n" tends to be used for the individual channel numbers.
In the CoE system 16 indices, each with 255 subindices, are generally sufficient for representing all channel
parameters. The channel-based order is therefore arranged in 16
dec
/10
steps. The parameter range x8000
hex
exemplifies this:
• Channel 0: parameter range x8000:00 ... x800F:255
• Channel 1: parameter range x8010:00 ... x801F:255
• Channel 2: parameter range x8020:00 ... x802F:255
• …
This is generally written as x80n0. Detailed information on the CoE interface can be found in the EtherCATsystem documentation on the Beckhoff website.
EP8309-102226Version: 2.0.0
Page 27
4Mounting and cabling
4.1Mounting
4.1.1Dimensions
Mounting and cabling
Fig.14: Dimensions of the EtherCAT Box Modules
All dimensions are given in millimeters.
Housing properties
EtherCAT Boxlean bodywide body
Housing materialPA6 (polyamide)
Casting compoundPolyurethane
Mountingtwo fastening holes Ø3mm for M3two fastening holes Ø3mm for M3
two fastening holes Ø4,5mm for M4
Metal partsBrass, nickel-plated
ContactsCuZn, gold-plated
Power feed throughmax. 4A
Installation positionvariable
Protection classIP65, IP66, IP67 (conforms to EN 60529) when screwed together
Dimensions (HxWxD) ca. 126 x 30 x 26,5mmca. 126 x 60 x 26,5mm
Weightapprox. 125g, depending on module type approx. 250g, depending on module
type
EP8309-102227Version: 2.0.0
Page 28
Mounting and cabling
4.1.2Fixing
Note or pointer
While mounting the modules, protect all connectors, especially the IP-Link, against contam-
Note
Modules with narrow housing are mounted with two M3 bolts.
Modules with wide housing are mounted with two M3 bolts to the fixing holes located at the corners or
mounted with two M4 bolts to the fixing holes located centrally.
The bolts must be longer than 15 mm. The fixing holes of the modules are not threaded.
When assembling, remember that the fieldbus connectors increases the overall height. See chapter
accessories.
Mounting Rail ZS5300-0001
The mounting rail ZS5300-0001 (500 mm x 129 mm) allows the time saving assembly of modules.
The rail is made of stainless steel, 1.5 mm thick, with already pre-made M3 threads for the modules. The rail
has got 5.3 mm slots to mount it via M5 screws to the machine.
ination! Only with connected cables or plugs the protection class IP67 is guaranteed! Unused connectors have to be protected with the right plugs! See for plug sets in the catalogue.
Fig.15: Mounting Rail ZS5300-000
The mounting rail is 500 mm long, that way 15 narrow modules can be mounted with a distance of 2 mm
between two modules. The rail can be cut to length for the application.
Mounting Rail ZS5300-0011
The mounting rail ZS5300-0011 (500 mm x 129 mm) has in addition to the M3 treads also pre-made M4
treads to fix 60 mm wide modules via their middle holes.
Up to 14 narrow or 7 wide modules may be mixed mounted.
EP8309-102228Version: 2.0.0
Page 29
Mounting and cabling
4.2Cabling
4.2.1Connections
The EP8309 has different signals that can be connected via the eight M12 sockets.
CommentConnectorComment
EtherCAT INEtherCAT OUT
Socket 1:
• analog In
Socket 2:
• analog In
Socket 3:
• digital In channel 1 / Tacho
input 1
• digital In channel 2 / Tacho
input 2
Socket 4:
• digital In/Out channel3
• digital In/Out channel4
Power InPower Out
Socket 5:
• digital In/Out channel1
• digital In/Out channel2
Socket 6:
• digital In/Out channel1
• digital In/Out channel2
Socket 7:
• digital In/Out channel3
• digital In/Out channel4
Socket 8:
• pulse width current output
or
• analog output
EP8309-102229Version: 2.0.0
Page 30
Mounting and cabling
4.2.2Nut torque for connectors
M8 connectors
It is recommended to pull the M8 connectors tight with a nut torque of 0.4 Nm. When using the torque control
screwdriver ZB8800 is also a max. torque of 0.5Nm permissible.
Fig.16: EtherCAT Box with M8 connectors
M12 connectors
It is recommended to pull the M12 connectors tight with a nut torque of 0.6 Nm.
Fig.17: EtherCAT Box with M8 and M12 connectors
EP8309-102230Version: 2.0.0
Page 31
7/8" plug connectors
We recommend fastening the 7/8" plug connectors with a torque of 1.5Nm.
Fig.18: 7/8" plug connectors
Torque socket wrenches
Mounting and cabling
Fig.19: ZB8801 torque socket wrench
Ensure the right torque
Use the torque socket wrenches available by Beckhoff to pull the connectors tight (ZB8800,
Note
ZB8801-0000)!
EP8309-102231Version: 2.0.0
Page 32
Mounting and cabling
4.2.3EtherCAT
4.2.3.1EtherCAT connection
For the incoming and ongoing EtherCAT connection,
• the EtherCAT Box (EPxxxx) has two M8 sockets, marked in green
• the Coupler Box (FBB-x110) has two M12 sockets
Fig.20: EtherCAT Box: M8 (30mm housing)
Fig.21: EtherCAT Box: M8 60mm housing (EP9214 for example )
EP8309-102232Version: 2.0.0
Page 33
Mounting and cabling
Fig.22: Coupler Box: M12
Assignment
There are various different standards for the assignment and colors of connectors and cables for Ethernet/
EtherCAT.
ZB9031 and old
versions
of ZB9030, ZB9032,
ZK1090-3xxx-xxxx
orange/white
orange
blue/white
3
blue
3
3
3
TIA-568B
white/orange
orange
white/green
green
Shield ShieldHousingShroudScreenScreenScreen
1
) colored markings according to EN 61918 in the four-pin RJ45 connector ZS1090-0003
2
) wire colors according to EN 61918
3
) wire colors
Assimilation of color coding for cable ZB9030, ZB9032 and ZK1090-3xxxxxxxx (with M8 connectors)
Note
For unification the prevalent cables ZB9030, ZB9032 and ZK1090-3xxx-xxxx this means
the pre assembled cables with M8 connectors were changed to the colors of EN61918 (yellow, orange, white, blue).So different color coding exists. But the electrical properties are
absolutely identical.
EtherCAT connectors
The following connectors can be supplied for use in Beckhoff EtherCAT systems.
EP8309-102233Version: 2.0.0
Page 34
Mounting and cabling
DesignationPlug connectorComment
ZS1090-0003RJ45four-pin, IP20, for field assembly
ZS1090-0004M12four-pin, IP67, for field assembly
ZS1090-0005RJ45eight-pin, IP20, for field assembly, suitable for GigaBit Ethernet
ZS1090-0006M8 malefour-pin, IP67, for field assembly, for ZB903x cable
ZS1090-0007M8 femalefour-pin, IP67, for field assembly, for ZB903x cable
ZS1090-1006M8 malefour-pin, IP67, for field assembly up to OD = 6.5mm
ZS1090-1007M8 femalefour-pin, IP67, for field assembly up to OD = 6.5mm
4.2.3.2EtherCAT - Fieldbus LEDs
Fig.23: EtherCAT-LEDs
LED display
LEDDisplayMeaning
IN L/Aoffno connection to the preceding EtherCAT module
LitLINK: connection to the preceding EtherCAT module
flashingACT: Communication with the preceding EtherCAT module
OUT L/Aoffno connection to the following EtherCAT module
LitLINK: connection to the following EtherCAT module
flashingACT: Communication with the following EtherCAT module
RunoffStatus of the EtherCAT module is Init
flashes quicklyStatus of the EtherCAT module is pre-operational
flashes slowlyStatus of the EtherCAT module is safe-operational
LitStatus of the EtherCAT module is operational
EtherCAT statuses
The various statuses in which an EtherCAT module may be found are described in the Ba-
Note
sic System Documentation for EtherCAT, which is available for download from our website
(www.beckhoff.com) under Downloads.
EP8309-102234Version: 2.0.0
Page 35
Mounting and cabling
4.2.4Power Connection
4.2.4.1Power Connection
The feeding and forwarding of supply voltages is done via two M8 connectors at the bottom end of the
modules:
• IN: left M8 connector for feeding the supply voltages
• OUT: right M8 connector for forwarding the supply voltages
Fig.24: EtherCAT Box, Connectors for power supply
Fig.25: Pin assignment M8, Power In and Power Out
Table1: PIN assignment
PinVoltage
1Control voltage Us, +24V
2Auxiliary voltage Up, +24V
DC
DC
3GNDs**) may be connected internally to each other depending on the module: see specific
4GNDp*
module descriptions
The pins M8 connectors carry a maximum current of 4A.
Two LEDs display the status of the supply voltages.
Don't confuse the power connectors with the EtherCAT connectors!
Never connect the power cables (M8, 24VDC) with the green marked EtherCAT sockets of
Attention
the EtherCAT Box Modules! This can damage the modules!
Control voltage Us: 24V
DC
Power is supplied to the fieldbus, the processor logic, the inputs and the sensors from the 24VDC control
voltage Us. The control voltage is electrically isolated from the fieldbus circuitry.
EP8309-102235Version: 2.0.0
Page 36
Mounting and cabling
Auxiliary voltage Up 24V
DC
The Auxiliary voltage Up supplies the digital outputs; it can be brought in separately. If the load voltage is
switched off, the fieldbus functions and the power supply and functionality of the inputs are retained.
Redirection of the supply voltages
The IN and OUT power connections are bridged in the module (not IP204x-Bxxx and IE204x). The supply
voltages Us and Up can thus easily be transferred from EtherCATBox to EtherCATBox.
Pay attention to the maximum permissible current!
Pay attention also for the redirection of the supply voltages Us and Up, the maximum per-
Attention
missible current for M8 connectors of 4A must not be exceeded!
EP8309-102236Version: 2.0.0
Page 37
Mounting and cabling
Supply via EP92x4-0023 PowerBox modules
If the machine requires higher current or if the EtherCAT Box Modules are installed far away from the control
cabinet with included power supply, the usage of four cannel power distribution modules EP9214 or EP9224
(with integrated data logging, see www.beckhoff.com/EP9224) is recommended.
With these modules intelligent power distribution concepts with up to 2x16A and a maximum of 2.5mm²
cable cross-section can be realized.
Fig.26: EP92x4-0023, Connectors for Power In and Power Out
Fig.27: Pin assignment 7/8”, Power In and Power Out
EP8309-102237Version: 2.0.0
Page 38
Mounting and cabling
Electrical isolation
Digital modules
In the digital input/output modules, the grounds of the control voltage (GNDs) and the auxiliary voltage
(GNDp) are connected to each other!
Check this at the documentation of each used EtherCAT Box.
Analog modules
In the analog input/output modules the grounds of the control voltage (GNDs) and the auxiliary voltage
(GNDp) are separated from each other in order to ensure electrical isolation of the analog signals from the
control voltage.
In some of the analog modules the sensors or actuators are supplied by Up - this means, for instance, that in
the case of 0...10 V inputs, any reference voltage (0...30 V) may be connected to Up; this is then available to
the sensors (e.g. smoothed 10 V for measuring potentiometers).
Details of the power supply may be taken from the specific module descriptions.
Electrical isolation may be cancelled!
If digital and analog fieldbus boxes are connected directly via four-core power leads, the
Attention
analog signals in the fieldbus boxes may be no longer electrically isolated from the control
voltage!
4.2.4.2Status LEDs for power supply
Fig.28: Status LEDs for power supply
LED display
LEDDisplayMeaning
Us (Control voltage)offThe power supply voltage Us is not present
green illuminatedThe power supply voltage Us is present
red illuminatedBecause of overload (current>0.5A) the sensor supply
generated from power supply voltage Us was switched off for
all sensors fed from this.
Up (Auxiliary voltage)offThe power supply voltage Up is not present
green illuminatedThe power supply voltage Up is present
EP8309-102238Version: 2.0.0
Page 39
4.2.4.3Power cable
Ordering data
Mounting and cabling
Order identifierPower cableScrew
ContactsCross-section Length
connector
ZK2020-3200-0020Straight socket, open
ZK2020-3200-00505.00m
end
M84-pole0.34 mm
2
2.00m
ZK2020-3200-010010.00m
ZK2020-3400-0020Angled socket, open
ZK2020-3400-00505.00m
Further available power cables and the associated data sheets can be found in the Beckhoff catalogue or on
our website (http://www.beckhoff.de).
Technical Data
Data
Rated voltage according to IEC61076-2-10130V
DC
Contamination level according to IEC 60 664-13/2
Insulation resistance IEC 60 512-2>109 Ω
Current carrying capacity according to IEC 60512-34A
Volume resistance according to IEC 60512-2< 5mΩ
Protection class conforms to IEC 60529IP65/66/67, when screwed together
Ambient temperature-30 °C to +80 °C
4.2.4.4Power cable conductor losses M8
The ZK2020-xxxx-yyyy power cables should not exceed the total length of 15m at 4A (with continuation).
When planning the cabling, note that at 24V nominal voltage, the functionality of the module can no longer
be assured if the voltage drop reaches 6V. Variations in the output voltage from the power supply unit must
also be taken into account.
EP8309-102239Version: 2.0.0
Page 40
Mounting and cabling
Fig.29: Power cable conductor losses
Example
8m power cable with 0.34mm² cross-section has a voltage drop of 3.2V at 4A.
EP92x4 Power Distribution Modules
With EP9214 and EP9224 Power Distribution Modules intelligent concepts for voltage sup-
Note
ply are available. Further information may be found under www.beckhoff.com/EP9224.
EP8309-102240Version: 2.0.0
Page 41
Mounting and cabling
4.2.5Signal connection
4.2.5.1Digital inputs M12
The digital input modules acquire the binary control signals from the process level and transmit them to the
higher-level automation device.
The signals are connected via M12 connectors.
Fig.30: Digital inputs M12
The sensors are supplied with a common maximum current of 0.5Afrom the control voltage Us.
Light emitting diodes indicate the signal state of the inputs.
EP8309-102241Version: 2.0.0
Page 42
Mounting and cabling
4.2.5.2Digital inputs/outputs M12
The digital input/output channels connect the binary control signals from the automation device for the
process level with the actuators or read digital input signals.
No configuration is required. For each channel one input or output can be connected.
If an output is used, the change in status can be verified on switch-on via the corresponding signal in the
input process image.
The signals are connected via M12 connectors.
Fig.31: Digital inputs/outputs M12
The outputs are short-circuit proof and protected against inverse connection.
LEDs indicate the signal state of the outputs.
4.2.5.3Analog inputs M12
The analog signal inputs pick up analog control signals from the process level and transmit them to the
higher-level automation device.
The signals are connected via M12 connectors.
Fig.32: Analog inputs M12
The sensors are supplied with a common maximum current of 0.5Afrom the control voltage Us.
LEDs indicate the status of the inputs.
EP8309-102242Version: 2.0.0
Page 43
Mounting and cabling
4.2.5.4Analog output and PWMi output M12
Via the multi-function output either an analog output or a PWMi output can be output to a proportional valve,
for example.
The signals are connected via M12 connectors.
Fig.33: Analog output and PWMi output M12
The outputs are short-circuit-proof.
LEDs indicate the signal state of the output.
4.2.5.5Status LEDs
Fig.34: Status LEDs
Status LEDs at the M12 connections
ConnectionLEDDisplayMeaning
M12 socket analog
inputs, PWMi
Correct function is indicated if the green Run LED is on and the red Error LED is off.
leftoffNo data transfer to the D/A converter
greenData transfer to the D/A converter
rightoffFunction OK
redAnalog error: broken wire or measured value outside the
measuring range
PWMi: general error, see status word
Status LEDs at the M12 connections
ConnectionLEDDisplayMeaning
M12 socket digital
inputs/outputs
EP8309-102243Version: 2.0.0
left /
right
offInput / output off or Low
greenInput / output on or High
Page 44
Mounting and cabling
4.2.6UL Requirements
The installation of the EtherCAT Box Modules certified by UL has to meet the following requirements.
Supply voltage
CAUTION!
This UL requirements are valid for all supply voltages of all marked EtherCAT Box Mod-
CAUTION
CAUTION
ules!
For the compliance of the UL requirements the EtherCAT Box Modules should only be supplied
• by a 24 VDC supply voltage, supplied by an isolating source and protected by means of
a fuse (in accordance with UL248), rated maximum 4 Amp, or
• by a 24 VDC power source, that has to satisfy NEC class 2.
A NEC class 2 power supply shall not be connected in series or parallel with another
(class 2) power source!
CAUTION!
To meet the UL requirements, the EtherCAT Box Modules must not be connected to unlimited power sources!
Networks
CAUTION!
To meet the UL requirements, EtherCAT Box Modules must not be connected to telecom-
CAUTION
Ambient temperature range
munication networks!
CAUTION!
To meet the UL requirements, EtherCAT Box Modules has to be operated only at an ambi-
CAUTION
Marking for UL
All EtherCAT Box Modules certified by UL (Underwriters Laboratories) are marked with the following label.
Fig.35: UL label
ent temperature range of 0 to 55°C!
EP8309-102244Version: 2.0.0
Page 45
Commissioning and Configuration
5Commissioning and Configuration
5.1Inserting into the EtherCAT network
Installation of the latest XML device description
Please ensure that you have installed the latest XML device description in TwinCAT. This
Note
At the Beckhoff TwinCAT System Manager the configuration tree can be build in two different ways:
• by scanning [}45] for existing hardware (called "online") and
• by manual inserting/appending [}45] of fieldbus devices, couplers and slaves.
Automatic scanning in of the box
• The EtherCAT system must be in a safe, de-energized state before the EtherCAT modules are
connected to the EtherCAT network!
• Switch on the operating voltage, open the TwinCAT System Manager [}48] (Config mode), and scan
in the devices (see Fig. 1). Acknowledge all dialogs with "OK", so that the configuration is in "FreeRun"
mode.
can be downloaded from the Beckhoff website (http://www.beckhoff.de/english/download/elconfg.htm?id=1983920606140) and installed according to the installation instructions.
Fig.36: Scanning in the configuration (I/O Devices -> right-click -> Scan Devices...)
Appending a module manually
• The EtherCAT system must be in a safe, de-energized state before the EtherCAT modules are
connected to the EtherCAT network!
• Switch on the operating voltage, open the TwinCAT System Manager [}48] (Config mode)
• Append a new I/O device. In the dialog that appears select the device EtherCAT (Direct Mode), and
confirm with OK.
EP8309-102245Version: 2.0.0
Page 46
Commissioning and Configuration
Fig.37: Appending a new I/O device (I/O Devices -> right-click -> Append Device...)
Fig.38: Selecting the device EtherCAT
• Append a new box.
Fig.39: Appending a new box (Device -> right-click -> Append Box...)
• In the dialog that appears select the desired box (e.g. EP2816-0008), and confirm with OK.
EP8309-102246Version: 2.0.0
Page 47
Commissioning and Configuration
Fig.40: Selecting a Box (e.g. EP2816-0008)
Fig.41: Appended Box in the TwinCAT tree
EP8309-102247Version: 2.0.0
Page 48
Commissioning and Configuration
5.2Configuration via TwinCAT
In the left-hand window of the TwinCAT System Manager, click on the branch of the EtherCAT Box you wish
to configure (EP2816-0008 in this example).
Fig.42: Branch of the EtherCAT box to be configured
In the right-hand window of the TwinCAT System manager, various tabs are now available for configuring
the EtherCAT Box.
General tab
Fig.43: General tab
NameName of the EtherCAT device
IdNumber of the EtherCAT device
TypeEtherCAT device type
CommentHere you can add a comment (e.g. regarding the system).
DisabledHere you can deactivate the EtherCAT device.
Create symbolsAccess to this EtherCAT slave via ADS is only available if this checkbox is
activated.
EP8309-102248Version: 2.0.0
Page 49
Commissioning and Configuration
EtherCAT tab
Fig.44: EtherCAT tab
TypeEtherCAT device type
Product/RevisionProduct and revision number of the EtherCAT device
Auto Inc Addr.Auto increment address of the EtherCAT device. The auto increment address can
be used for addressing each EtherCAT device in the communication ring through
its physical position. Auto increment addressing is used during the start-up phase
when the EtherCAT master allocates addresses to the EtherCAT devices. With
auto increment addressing the first EtherCAT slave in the ring has the address
0000
. For each further slave the address is decremented by 1 (FFFF
hex
, FFFE
hex
etc.).
EtherCAT Addr.Fixed address of an EtherCAT slave. This address is allocated by the EtherCAT
master during the start-up phase. Tick the checkbox to the left of the input field in
order to modify the default value.
Previous PortName and port of the EtherCAT device to which this device is connected. If it is
possible to connect this device with another one without changing the order of the
EtherCAT devices in the communication ring, then this combobox is activated and
the EtherCAT device to which this device is to be connected can be selected.
Advanced SettingsThis button opens the dialogs for advanced settings.
hex
The link at the bottom of the tab points to the product page for this EtherCAT device on the web.
Process Data tab
Indicates the configuration of the process data. The input and output data of the EtherCAT slave are
represented as CANopen process data objects (PDO). The user can select a PDO via PDO assignment and
modify the content of the individual PDO via this dialog, if the EtherCAT slave supports this function.
EP8309-102249Version: 2.0.0
Page 50
Commissioning and Configuration
Fig.45: Process Data tab
Sync Manager
Lists the configuration of the Sync Manager (SM).
If the EtherCAT device has a mailbox, SM0 is used for the mailbox output (MbxOut) and SM1 for the mailbox
input (MbxIn).
SM2 is used for the output process data (outputs) and SM3 (inputs) for the input process data.
If an input is selected, the corresponding PDO assignment is displayed in the PDO Assignment list below.
PDO Assignment
PDO assignment of the selected Sync Manager. All PDOs defined for this Sync Manager type are listed
here:
• If the output Sync Manager (outputs) is selected in the Sync Manager list, all RxPDOs are displayed.
• If the input Sync Manager (inputs) is selected in the Sync Manager list, all TxPDOs are displayed.
The selected entries are the PDOs involved in the process data transfer. In the tree diagram of the System
Manager these PDOs are displayed as variables of the EtherCAT device. The name of the variable is
identical to the Name parameter of the PDO, as displayed in the PDO list. If an entry in the PDO assignment
list is deactivated (not selected and greyed out), this indicates that the input is excluded from the PDO
assignment. In order to be able do select a greyed out PDO, the currently selected PDO has to be
deselected first.
EP8309-102250Version: 2.0.0
Page 51
Commissioning and Configuration
Activation of PDO assignment
• the EtherCAT slave has to run through the PS status transition cycle (from pre-opera-
Note
PDO list
List of all PDOs supported by this EtherCAT device. The content of the selected PDOs is displayed in the
PDO Content list. The PDO configuration can be modified by double-clicking on an entry.
ColumnDescription
IndexPDO index.
SizeSize of the PDO in bytes.
NameName of the PDO.
If this PDO is assigned to a Sync Manager, it appears as a variable of the slave with this
parameter as the name.
FlagsF Fixed content: The content of this PDO is fixed and cannot be changed by the System
M Mandatory PDO. This PDO is mandatory and must therefore be assigned to a Sync
SMSync Manager to which this PDO is assigned. If this entry is empty, this PDO does not take part
in the process data traffic.
SUSync unit to which this PDO is assigned.
tional to safe-operational) once (see Online tab [}54]),
• and the System Manager has to reload the EtherCAT slaves ( button)
Manager.
Manager! Consequently, this PDO cannot be deleted from the PDO Assignment list
PDO Content
Indicates the content of the PDO. If flag F (fixed content) of the PDO is not set the content can be modified.
Download
If the device is intelligent and has a mailbox, the configuration of the PDO and the PDO assignments can be
downloaded to the device. This is an optional feature that is not supported by all EtherCAT slaves.
PDO Assignment
If this check box is selected, the PDO assignment that is configured in the PDO Assignment list is
downloaded to the device on startup. The required commands to be sent to the device can be viewed in the
Startup [}51] tab.
PDO Configuration
If this check box is selected, the configuration of the respective PDOs (as shown in the PDO list and the
PDO Content display) is downloaded to the EtherCAT slave.
Startup tab
The Startup tab is displayed if the EtherCAT slave has a mailbox and supports the CANopen over EtherCAT
(CoE) or Servo drive over EtherCAT protocol. This tab indicates which download requests are sent to the
mailbox during startup. It is also possible to add new mailbox requests to the list display. The download
requests are sent to the slave in the same order as they are shown in the list.
EP8309-102251Version: 2.0.0
Page 52
Commissioning and Configuration
Fig.46: Startup tab
ColumnDescription
TransitionTransition to which the request is sent. This can either be
• the transition from pre-operational to safe-operational (PS), or
• the transition from safe-operational to operational (SO).
If the transition is enclosed in "<>" (e.g. <PS>), the mailbox request is fixed and cannot be
modified or deleted by the user.
ProtocolType of mailbox protocol
IndexIndex of the object
DataDate on which this object is to be downloaded.
CommentDescription of the request to be sent to the mailbox
Move UpThis button moves the selected request up by one position in the list.
Move Down This button moves the selected request down by one position in the list.
NewThis button adds a new mailbox download request to be sent during startup.
DeleteThis button deletes the selected entry.
EditThis button edits an existing request.
CoE - Online tab
The additional CoE - Online tab is displayed if the EtherCAT slave supports the CANopen over EtherCAT
(CoE) protocol. This dialog lists the content of the object directory of the slave (SDO upload) and enables the
user to modify the content of an object from this list. Details for the objects of the individual EtherCAT
devices can be found in the device-specific object descriptions.
EP8309-102252Version: 2.0.0
Page 53
Commissioning and Configuration
Fig.47: CoE - Online tab
Object list display
ColumnDescription
IndexIndex and subindex of the object
NameName of the object
FlagsRWThe object can be read, and data can be written to the object (read/write)
ROThe object can be read, but no data can be written to the object (read only)
PAn additional P identifies the object as a process data object.
ValueValue of the object
Update ListThe Update list button updates all objects in the displayed list
Auto Update If this check box is selected, the content of the objects is updated automatically.
AdvancedThe Advanced button opens the Advanced Settings dialog. Here you can specify which
objects are displayed in the list.
EP8309-102253Version: 2.0.0
Page 54
Commissioning and Configuration
Fig.48: Advanced settings
Online
- via SDO information
Offline
- via EDS file
Online tab
If this option button is selected, the list of the objects included in the object
directory of the slave is uploaded from the slave via SDO information. The list
below can be used to specify which object types are to be uploaded.
If this option button is selected, the list of the objects included in the object
directory is read from an EDS file provided by the user.
Fig.49: Online tab
EP8309-102254Version: 2.0.0
Page 55
Commissioning and Configuration
State Machine
InitThis button attempts to set the EtherCAT device to the Init state.
Pre-OpThis button attempts to set the EtherCAT device to the pre-operational state.
OpThis button attempts to set the EtherCAT device to the operational state.
BootstrapThis button attempts to set the EtherCAT device to the Bootstrap state.
Safe-OpThis button attempts to set the EtherCAT device to the safe-operational state.
Clear ErrorThis button attempts to delete the fault display. If an EtherCAT slave fails during
change of state it sets an error flag.
Example: An EtherCAT slave is in PREOP state (pre-operational). The master now
requests the SAFEOP state (safe-operational). If the slave fails during change of
state it sets the error flag. The current state is now displayed as ERR PREOP. When
the Clear Error button is pressed the error flag is cleared, and the current state is
displayed as PREOP again.
Current StateIndicates the current state of the EtherCAT device.
Requested StateIndicates the state requested for the EtherCAT device.
DLL Status
Indicates the DLL status (data link layer status) of the individual ports of the EtherCAT slave. The DLL status
can have four different states:
StatusDescription
No Carrier / OpenNo carrier signal is available at the port, but the port is open.
No Carrier / ClosedNo carrier signal is available at the port, and the port is closed.
Carrier / OpenA carrier signal is available at the port, and the port is open.
Carrier / ClosedA carrier signal is available at the port, but the port is closed.
File Access over EtherCAT
DownloadWith this button a file can be written to the EtherCAT device.
UploadWith this button a file can be read from the EtherCAT device.
EP8309-102255Version: 2.0.0
Page 56
Commissioning and Configuration
5.3Tacho analysis
Tacho analysis refers to velocity or frequency logging for two digital sensors mounted on one shaft (singleshaft mode)or on two shafts (dual-shaft mode).
In single-shaft mode a plausibility check can be run for the two sensors (e.g. velocity deviation of the two
sensors).
The targets (sensor markings) should show a 90° overlapping signal when triggered. The minimum ON of
OFF time must not be less than 0.2ms, otherwise detection is not possible due to the sampling frequency.
The number of targets on the axis can be set in CoE object 0x80x0:11. In this way slower velocity/speed
detection with many targets or high velocity with few targets can be achieved.
Mode selection via the PDOs
The different modes are activated via the PDO assignment.
Single-shaft mode
The input PDO 0x1A02 activates the corresponding setting. The output data are always set.
Fig.50: Tacho evaluation – single shaft mode
Process data
ValueDescription
Error Input AThe measured velocity/frequency is lower than that of track B, or it is 0 (sensor faulty)
Input Status AStatus of input A
Error Input BThe measured velocity/frequency is lower than that of track A, or it is 0 (sensor faulty)
Input Status BStatus of input B
Speed below
threshold
Rotational Speed Rotational speed and frequency, shown as a function of CoE object 0x80x0:15
Rotation Direction 0: rising edge of input A occurs before rising edge of input B
The velocity is lower than the limit in CoE 0x8020:12 Rotational Speed Threshold or = 0
EP8309-102256Version: 2.0.0
Page 57
Display of the rotational speed
Commissioning and Configuration
Fig.51: Tacho evaluation - display of the rotational speed
Dual Shaft Mode
The input PDOs 0x1A03 and 0x1A04 activate the two dual-shaft process data. The output data are always
set.
Fig.52: Tacho evaluation - dual shaft mode
EP8309-102257Version: 2.0.0
Page 58
Commissioning and Configuration
Process data (settings for the second channel equivalent)
ValueDescription
Digital inputStatus of input
Speed below
threshold
Rotational Speed Rotational speed and frequency, shown as a function of CoE object 0x80x0:15
Display of the rotational speed
see single-shaft mode
CoE settings
The behavior of the tacho inputs is set via the CoE objects.
The velocity is lower than the limit in CoE 0x8020:12 or = 0
Fig.53: Tacho evaluation -
The following settings apply to all channels:
CoEValueDescription
80xx:12 Input Signal TimeoutThe process record <Speed Below Threshold> is set after x msec
without signal change at the input.
The following settings are only available in single-shaft mode
CoE objects for tacho settings (0x8020 and 0x8030)
CoEValueDescription
80x0:0B Enable Error DetectionEnable/disable error display
80x0:0C Reversion of rotationReversion of rotation display in Rotation direction
80x0:11 No. of TargetsNumber of "cams" on the shaft/axis
80x0:12 Rotational Speed Threshold Limit value below which the corresponding status bit is set
80x0:15 PresentationDisplay of the measured value in RPM, Hz, …
EP8309-102258Version: 2.0.0
Page 59
Commissioning and Configuration
5.4Switching between PWMi and analog output
Mode selection via the PDOs
PWMi mode or analog mode can be selected for operating a proportional valve at socket 7, for example.
• In PWMi mode (default) the coil is controlled directly via a PWM signal. The valve requires no control
electronics.
• In analog mode a current value of 0...20mA or 4...20mA is output, via which the control electronics
integrated in the valve controls the valve travel.
The 24VDC supply is switched on continuously.
The different modes are activated via the PDO assignment.
PWMi mode
The output PDO 0x1602 activates the PWMi mode.
Fig.54: Switching the PWMi/analog output - PWMi mode
Analog mode
The output PDO 0x1603 activates the analog mode.
EP8309-102259Version: 2.0.0
Page 60
Commissioning and Configuration
Fig.55: Switching the PWMi/analog output - analog mode
5.5Quick start
Parameterization of the main settings
The module is factory-set such that in most applications it is operational without further parameterization.
Set the parameter Max Current [%] (0x8pp0:10 [}80]) such that the maximum inductance current is not
exceeded. If an EP8309 with 1.2 A rated current and an inductance with a maximum current of 600 mA is
used, this parameter can be set to 50 (50%). This means that, at a maximum process data value of 32767
a coil current of +600 mA is reached (not +1 A).
Info data objects
Via the info data objects additional information can be transferred synchronously. For each channel two of
these objects are available.
The synchronous info data can be activated in the TwinCAT System Manager via the "Process Data" tab
(0x1A07).
dec
EP8309-102260Version: 2.0.0
Page 61
Commissioning and Configuration
Fig.56: Info data objects - activation of the synchronous info data
Objects 0x8060:21 [}80] and 0x8060:22 [}80] can be used to set the value to be transferred
synchronously.
Fig.57: Info data objects – selection of the value to be transmitted
EP8309-102261Version: 2.0.0
Page 62
Commissioning and Configuration
The following entries are available:
ValueTextDescription
0Actual currentActual current in mA
1Set currentSet current in mA
2Duty CycleThe PWM duty cycle of the output stage. A value of 1000 corresponds to
100% duty cycle.
Watchdog
The analog output value can, e.g. in the case of a failure of communication with the controller, be set to a
user-specific value.
Fig.58: Watchdog
Three parameterization options are available for this purpose:
Watchdog object (0x8060:05
[}83])
0: Default watchdog value
1: Watchdog ramp active
2: Last output value activeIn the event of a fault (watchdog drop) the last process data is
Behavior
The substitute switching value (0x8060:0D [}83]) is output on error.
On error the output value is moved to the default value (0x8060:0D[}83]) with the ramp time set under 0x8060:0E [}83]
The ramp time is specified in digits / ms.
If the entry is 100 and the default value 0, forexample, it takes
327ms (32767/100) for the output value to change from the
maximum value (32767) to the default value in the event of a fault.
issued.
EP8309-102262Version: 2.0.0
Page 63
Commissioning and Configuration
Optimization of the current control parameters
In order to be able to support all possible loads ex factory, the terminal was parameterized with moderate
controller characteristics. Current regulation can be improved significantly by adapting the controller
parameters to the actual load.
To determine the settings a current pulse is applied to the load. This pulse can be picked up with an
oscilloscope or with TwinCAT ScopeView.
For evaluation with TwinCAT ScopeView the set and actual current is displayed in the synchronous info
data.
Fig.59: Selecting the synchronous info data
EP8309 standard parameters (20 ms/div)
Green: Set current
Red: Actual current
The required step response can be set using the parameters Kp,Ki, and Kd (0x8060:12 [}83] to 0x8060:14[}83]).
EP8309-102263Version: 2.0.0
Optimized parameters (20 ms/div)
Green: Set current
Red: Actual current
Page 64
Commissioning and Configuration
Dithering
Dithering involves modulating a square wave signal on top of the actual output value. The modulated signal
results in continuous movement of a valve piston, for example.
This reduces static friction and prevents sudden "breakaway" of the piston.
The configuration required for this depends a lot on the particular application.
To activate dithering, the object 0x8060:03 [}83] ("Enable dithering") and the corresponding control bit must
be set.
Fig.60: Enable dithering
The following parameters can be set:
ValueTextDescription
0x8060:1E
[}83]
0x8060:1F
[}83]
The controller parameters themselves (Kp,Ki, and Kd) also play a role.
In the diagrams a dither of 10 % of the rated current is shown as 100 Hz.
The controller has 5 ms for compensating a current pulse of 10 %. The steepness of the current rise is
limited by the controller parameters and the inductance.
The actual current should follow the set current. This is enabled through suitable settings of the controller
and dither parameters (frequency and amplitude).
Dithering frequency [Hz] Frequency of the applied dither in Hz
Dithering amplitude [%]Amplitude of the applied dither (in % of the rated terminal
current)
EP8309-102264Version: 2.0.0
Page 65
Commissioning and Configuration
EP8309 100 Hz dither with 10% amplitude,
poor parameterization (5ms/div)
Green: Set current
Red: Actual current
EP8309 100Hz dither with 10% amplitude,
better parameterization (5ms/div)
Green: Set current
Red: Actual current
5.6Range settings for inputs and outputs
CoE-Online tab
The CoE-Online tab lists the contents of the slave object directory of the slave (SDO upload) and enables
the user to modify the content of an object in this list.
Object 0xF800:0 [}84] contains the range settings for the inputs and outputs of channels 1 to 4.
Fig.61: CoE-Online tab
Click on objects 0xF800:01 to 0xF800:04 to change the settings.
EP8309-102265Version: 2.0.0
Page 66
Commissioning and Configuration
Fig.62: Changing the settings
5.7CoE objects
5.7.1CoE interface
General description
The CoE interface (CANopen over EtherCAT) is used for parameter management of EtherCAT devices.
EtherCAT slaves or the EtherCAT master manage fixed (read only) or variable parameters which they
require for operation, diagnostics or commissioning.
CoE parameters are arranged in a table hierarchy. In principle, the user has read access via the fieldbus.
The EtherCAT master (TwinCAT System Manager) can access the local CoE lists of the slaves via
EtherCAT in read or write mode, depending on the properties.
Different CoE parameter types are possible, including string (text), integer numbers, Boolean values or larger
byte fields. They can be used to describe a wide range of features. Examples of such parameters include
manufacturer ID, serial number, process data settings, device name, calibration values for analog
measurement or passwords.
Organization takes place on 2 levels by means of hexadecimal numbering: the (main) index is named first,
then the subindex. The value ranges are:
• Index 0 to 65535
• Subindex: 0…255
A parameter localized in this way is normally written as x8010:07, with preceding "x" to identify the
hexadecimal numerical range and a colon between index and subindex.
The relevant ranges for EtherCAT fieldbus users are:
• x1000: This is where fixed identity information for the device is stored, including name, manufacturer,
serial number etc., plus information about the current and available process data configurations.
• x8000: This is where the operational and functional parameters for all channels are stored, such as
filter settings or output frequency.
Other important ranges are:
• x4000: In some EtherCAT devices the channel parameters are stored here (as an alternative to the
x8000 range).
• x6000: Input PDOs ("input" from the perspective of the EtherCAT master)
• x7000: Output PDOs ("output" from the perspective of the EtherCAT master)
EP8309-102266Version: 2.0.0
Page 67
Commissioning and Configuration
Availability
Not every EtherCAT device must have a CoE list. Simple I/O modules without dedicated
Note
If a device has a CoE list, it is shown in the TwinCAT System Manager as a separate tab with a listing of the
elements:
processor usually have no variable parameters and therefore no CoE list.
Fig.63: CoE-Online tab
The CoE objects from x1000 to x1600, which are available in the example device "EL2502", can be seen in
the above figure; the subindices from x1018 are expanded.
Data management
Some parameters, particularly the setting parameters of the slave, are configurable and writeable. This can
be done in write or read mode
• via the System Manager (figure above) by clicking. This is useful for commissioning of the system/
slaves. Click on the row of the index to be parameterized and enter a value in the SetValue dialog.
• from the control system/PLC via ADS, e.g. through function blocks from the TcEtherCAT.lib library This
is recommended for modifications while the system is running or if no System Manager or operating
staff are available.
Data management
If CoE parameters on the slave are changed online, this is saved fail-safe in the device
Note
(EEPROM) in Beckhoff devices. This means that the changed CoE parameters are still retained after a restart. The situation may be different with other manufacturers.
EP8309-102267Version: 2.0.0
Page 68
Commissioning and Configuration
Startup list
Startup list
Changes in the local CoE list of the terminal are lost if the terminal is replaced. If a termi-
Note
Recommended approach for manual modification of CoE parameters
• Make the required change in the System Manager. The values are stored locally in the EtherCAT slave
• If the value is to be stored permanently, enter it in the Startup list. The order of the Startup entries is
usually irrelevant.
nal is replaced with a new Beckhoff terminal, it will have the factory settings. It is therefore
advisable to link all changes in the CoE list of an EtherCAT slave with the Startup list of
the slave, which is processed whenever the EtherCAT fieldbus is started. In this way a replacement EtherCAT slave can automatically be parameterized with the specifications of
the user.
If EtherCAT slaves are used which are unable to store local CoE values permanently, the
Startup list must be used.
Fig.64: Startup list in the TwinCAT System Manager
The Startup list may already contain values that were configured by the System Manager based on the ESI
specifications. Additional application-specific entries can be created.
Online/offline directory
While working with the TwinCAT System Manager, a distinction has to be made whether the EtherCAT
device is "available", i.e. switched on and linked via EtherCAT and therefore online, or whether a
configuration is created offline without connected slaves.
In both cases a CoE directory is visible according to the figure "CoE-Online tab", but the connectivity is
displayed as offline/online.
If the slave is offline
• the offline list from the ESI file is displayed. In this case modifications are not meaningful or possible.
• the configured status is shown under Identity
• no firmware or hardware version is displayed, since these are features of the physical device.
• Offline is shown in red
EP8309-102268Version: 2.0.0
Page 69
Commissioning and Configuration
Fig.65: Offline list
If the slave is online
• the actual current slave directory is read. This may take several seconds, depending on the size and
cycle time.
• the actual identity is displayed
• the firmware and hardware version of the equipment according to the electronic information is
displayed.
• Online is shown in green
Fig.66: Online list
EP8309-102269Version: 2.0.0
Page 70
Commissioning and Configuration
Channel-based order
The CoE directory is located in EtherCAT devices that usually encompass several functionally equivalent
channels. e.g. a 4-channel 0 – 10 V analog input terminal also has 4 logical channels and thus 4 identical
sets of parameter data for the channels. In order to avoid having to list each channel in the documentation,
the placeholder "n" tends to be used for the individual channel numbers.
In the CoE system 16 indices, each with 255 subindices, are generally sufficient for representing all channel
parameters. The channel-based order is therefore arranged in 16
dec
/10
steps. The parameter range x8000
hex
exemplifies this:
• Channel 0: parameter range x8000:00 ... x800F:255
• Channel 1: parameter range x8010:00 ... x801F:255
• Channel 2: parameter range x8020:00 ... x802F:255
• …
This is generally written as x80n0. Detailed information on the CoE interface can be found in the EtherCATsystem documentation on the Beckhoff website.
EP8309-102270Version: 2.0.0
Page 71
Commissioning and Configuration
5.7.2Object overview
EtherCAT XML Device Description
The display matches that of the CoE objects from the EtherCAT XML Device Description.
Note
Index (hex)NameFlags Default value
1000 [}85]
1008 [}85]
1009 [}85]
100A [}85]
1011
[}85]:0
1018
[}85]:0
10F0
[}85]:0
1402
[}86]:0
1403
[}86]:0
1600
[}86]:0
1601
[}86]:0
1602
[}86]:0
We recommend downloading the latest XML file from the download area of the Beckhoff
website and installing it according to installation instructions.
8060:1FDithering amplitude [%]RW0x0A (10
8060:21Select info data 1RW0x00 (0
8060:22Select info data 2RW0x00 (0
SubindexPWM Vendor dataRW0x02 (2
806F:01OffsetRW0x0000 (0
Flags:
RO (Read Only): this object can be read only
RW (Read/Write): this object can be read and written to
5.7.3Object description and parameterization
Parameterization
The terminal is parameterized via the CoE - Online tab [}52] (double-click on the respec-
Note
Note
Introduction
The CoE overview contains objects for different intended applications:
• Objects required for parameterization [}80] during commissioning
tive object) or via the Process Data tab [}49](assignment of PDOs).
EtherCAT XML Device Description
The display matches that of the CoE objects from the EtherCAT XML Device Description.
We recommend downloading the latest XML file from the download area of the Beckhoff
website and installing it according to installation instructions.
• Objects intended for regular operation [}84], e.g. through ADS access.
• Objects for indicating internal settings [}85] (may be fixed)
• Further profile-specific objects [}94] indicating inputs, outputs and status information
The following section first describes the objects required for normal operation, followed by a complete
overview of missing objects.
EP8309-102279Version: 2.0.0
Page 80
Commissioning and Configuration
5.7.3.1Objects to be parameterized during commissioning
Index 8000 AI Settings Ch.1
Index (hex) NameMeaningData typeFlagsDefault
8000:0AI SettingsMaximum subindexUINT8RO0x18 (24
8000:01Enable user scale1User scale is active.BOOLEANRW0x00 (0
The gain is represented in fixed-point format, with the
-16
factor 2
The value 1 corresponds to 65535
and is limited to +/- 0x7FFFF
.
(0x00010000
dez
8010:13Limit 1First limit value for setting the status bitsINT16RW0x0000 (0
8010:14Limit 2Second limit value for setting the status bitsINT16RW0x0000 (0
8010:15Filter settingsThis object determines the digital filter settings for all
channels of the module, if it is activated via Enable filter
(index 0x80n0:06 [}80]). The possible settings are se-
quentially numbered.
050Hz FIR
160Hz FIR
2IIR 1
3IIR 2
4IIR 3
5IIR 4
6IIR 5
7IIR 6
8IIR 7
9IIR 8
8010:17User calibration offset User calibration: OffsetINT16RW0x0000 (0
8010:18User calibration gain User calibration: GainINT16RW0x4000
BOOLEANRW0x00 (0
INT32RW0x00010000
)
hex
UINT16RW0x0000 (0
(65536
(16384
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
Index 8020 TACHO Settings Dual Shaft Mode Ch.1
Index (hex) NameMeaningData typeFlagsDefault
8020:0TACHO Settings Dual
UINT8RO0x15 (21
Shaft Mode Ch.1
8020:11No. of TargetsNumber of "cams" on the shaft/axisUINT16RW0x0001 (1
8020:12Input Signal Timeout The process record <Speed Below Threshold> is set af-
ter x msec without signal change at the input.
UINT16RW0x0064
(100
dec
)
8020:15PresentationDisplay of the measured value in RPM, Hz, …UINT16RW0x0001 (1
Index 8030 TACHO Settings Dual Shaft Mode Ch.2
Index (hex) NameMeaningData typeFlagsDefault
8030:0TACHO Settings Dual
UINT8RO0x15 (21
Shaft Mode Ch.2
8030:11No. of TargetsNumber of "cams" on the shaft/axisUINT16RW0x0001 (1
8030:12Input Signal Timeout The process record <Speed Below Threshold> is set af-
ter x msec without signal change at the input.
UINT16RW0x0064
(100
dec
)
8030:15PresentationDisplay of the measured value in RPM, Hz, …UINT16RW0x0001 (1
EP8309-102281Version: 2.0.0
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
Page 82
Commissioning and Configuration
Index 8031 TACHO Settings Single Shaft Mode
Index (hex) NameMeaningData typeFlagsDefault
8031:0TACHO Settings Sin-
UINT8RO0x15 (21
gle Shaft Mode
8031:0BEnable Error Detec-
Enable/disable error displayBOOLEANRW0x01 (1
tion
8031:0CReversion of Rotation Reversion of rotation display in Rotation directionBOOLEANRW0x00 (0
8031:11No. of TargetsNumber of "cams" on the shaft/axisUINT16RW0x0001 (1
8031:12Input Signal Timeout The process record <Speed Below Threshold> is set af-
ter x msec without signal change at the input.
UINT16RW0x0064
(100
dec
)
8031:15PresentationDisplay of the measured value in RPM, Hz, …UINT16RW0x0000 (0
Index 8040 DIG Safe State Active
Index (hex) NameMeaningData typeFlagsDefault
8040:0DIG Safe State ActiveUINT8RO0x08 (8
8040:01X4 Pin4Activation of Safe State Value if communication is can-
celed
8040:02X4 Pin2Activation of Safe State Value if communication is can-
celed
8040:03X5 Pin4Activation of Safe State Value if communication is can-
celed
8040:04X5 Pin2Activation of Safe State Value if communication is can-
celed
8040:05X6 Pin4Activation of Safe State Value if communication is can-
celed
8040:05X6 Pin2Activation of Safe State Value if communication is can-
celed
8040:07X7 Pin4Activation of Safe State Value if communication is can-
celed
8040:08X7 Pin2Activation of Safe State Value if communication is can-
celed
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
BOOLEANRWTRUE
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
Index 8041 DIG Safe State Value
Index (hex) NameMeaningData typeFlagsDefault
8040:0DIG Safe State ValueUINT8RO0x00 (0
8040:01X4 Pin4Output value if communication is canceledBOOLEANRWFalse
8040:02X4 Pin2Output value if communication is canceledBOOLEANRWFalse
8040:03X5 Pin4Output value if communication is canceledBOOLEANRWFalse
8040:04X5 Pin2Output value if communication is canceledBOOLEANRWFalse
8040:05X6 Pin4Output value if communication is canceledBOOLEANRWFalse
8040:05X6 Pin2Output value if communication is canceledBOOLEANRWFalse
8040:07X7 Pin4Output value if communication is canceledBOOLEANRWFalse
8040:08X7 Pin2Output value if communication is canceledBOOLEANRWFalse
Index 8043 DIG Safe State Delay
Index (hex) NameMeaningData typeFlagsDefault
8040:0DIG Safe State DelayUINT8RO0x00 (0
8040:01X4 Pin4Delay in msec after communication is canceledUINT16RWFalse
8040:02X4 Pin2Delay in msec after communication is canceledUINT16RWFalse
8040:03X5 Pin4Delay in msec after communication is canceledUINT16RWFalse
8040:04X5 Pin2Delay in msec after communication is canceledUINT16RWFalse
8040:05X6 Pin4Delay in msec after communication is canceledUINT16RWFalse
8040:05X6 Pin2Delay in msec after communication is canceledUINT16RWFalse
8040:07X7 Pin4Delay in msec after communication is canceledUINT16RWFalse
8040:08X7 Pin2Delay in msec after communication is canceledUINT16RWFalse
)
dec
)
dec
EP8309-102282Version: 2.0.0
Page 83
Commissioning and Configuration
Index 8060 PWM Settings
Index (hex) NameMeaningData typeFlagsDefault
8060:0PWM settingsMaximum subindexUINT8RO0x22 (34
8060:03Enable ditheringDithering is "enabled", activation via process dataBOOLEANRW0x00 (0
8060:04Invert polarityReverse current directionBOOLEANRW0x00 (0
8060:05Watchdog0: Default watchdog value
The default value (0x8pp0:0D) is active.
1: Watchdog ramp active
The ramp (0x8pp0:0E) for moving to the default value
((0x8pp0:0D)) is active.
2: Last output value active
In the event of a fault (watchdog drop) the last process
data is issued.
8060:0BOffsetThis is the user scaling offset
Scaling: 1 = rated terminal current / 1024
8060:0CGainThis is the user scaling gain. The gain is a fixed-point
number with the factor 2^-16.
The value one corresponds to 65536 (0x00010000).
8060:0DDefault outputThis is the default output value. The value is output if it is
activated via 0x8pp0:05.
8060:0EDefault output rampThis value defines the ramps for the ramp-down to the
default value. The value is specified in digits / ms.
If the entry is 100 and the default value 0, forexample, it
takes 327ms (32767/100) for the output value to change
from the maximum value (32767) to the default value in
the event of a fault.
8060:10Max current [%]Maximum output current mAUINT8RW0x64 (100
8060:12Kp factorThis is the user scaling gain. The gain is a fixed-point
number with the factor 2^-16. The value 1 corresponds to
65535 (0x00010000).
8060:13Ki factorThis is the default output valueUINT16RW0x0004 (4
8060:14Kd factorThis value defines the ramps for the ramp-down to the
default value. The value is specified in digits / ms.
If the entry is 100 and the default value 0, forexample, it
takes 327ms (32767/100) for the output value to change
from the maximum value (32767) to the default value in
the event of a fault.
8060:1EDithering frequency
Dither frequency in HertzUINT16RW0x0064
[Hz]
8060:1FDithering amplitude
[%]
Dithering amplitude in percent of the maximum permitted
current (rated box current * 0x8pp0:10)
8060:21Select info data 1Selection of synchronous info data (s. 0x6pp0:11)UINT8RW0x00 (0
8060:22Select info data 2Selection of synchronous info data (s. 0x6pp0:12)UINT8RW0x00 (0
BIT2RW0x00 (0
INT16RW0x0000 (0
INT32RW0x00010000
(65536
INT16RW0x0000 (0
UINT16RW0xFFFF
(65535
UINT16RW0x00FA
(250
)
dec
UINT16RW0x0032 (50
(100
)
dec
UINT8RW0x0A (10
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
EP8309-102283Version: 2.0.0
Page 84
Commissioning and Configuration
Index 8070 AO Settings
Index (hex) NameMeaningData typeFlagsDefault
8070:0AO SettingsUINT8RO0x16 (22
8070:01Enable user scaleThis entry activates the scaling for 0x8pp0:11 and
0x8pp0:12.
8070:02Presentation0: Signed presentation
The output value range 0x7pp1:11 is shown as 16bit
signed integer. For unipolar terminals (0-10Vor 0-20mA)
the negative range is set to zero.
1: Unsigned presentation The output value range
0x7pp1:11 is shown as 16 bit unsigned integer. Negative
values are not possible.
2: Absolute value with MSB as sign, signed amount representation is active.
3: Absolute value, the absolute value of the signed representation is formed.
8070:05Watchdog0: Default watchdog value
The default value (0x8pp0:13) is active.
1: Watchdog ramp
The ramp (0x8pp0:14) for moving to the default value
((0x8pp0:13)) is active.
2: Last output value
In the event of a fault (watchdog drop) the last process
data is issued.
8070:07Enable user calibra-
Enabling of the user calibrationBOOLEANRW0x00 (0
tion
8070:08Enable vendor cali-
Enable vendor calibrationBOOLEANRW0x01 (1
bration
8070:11User scale offsetThis is the user scaling offsetINT16RW0x0000 (0
8070:12User scale gainThis is the user scaling gain. The gain is a fixed-point
number with the factor 2^-16. The value 1 corresponds to
65535 (0x00010000).
8070:13Default outputThis is the default output valueINT16RW0x0000 (0
8070:14Default output rampThis value defines the ramps for the ramp-down to the
default value. The value is specified in digits / ms.
If the entry is 100 and the default value 0, forexample, it
takes 327ms (32767/100) for the output value to change
from the maximum value (32767) to the default value in
the event of a fault.
8070:15User calibration offset User calibration offsetINT16RW0x0000 (0
8070:16User calibration gain User gain compensationUINT16RW0x4000
BOOLEANRW0x00 (0
BIT3RW0x00 (0
BIT2RW0x00 (0
INT32RW0x00010000
(65536
UINT16RW0xFFFF
(65535
(16384
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
Index F800 AIAO Range settings
Index (hex) NameMeaningData typeFlagsDefault
F800:0AIAO Range settingsUINT8RO0x08 (8
F800:01Input type Ch1Select input type for Ch1UINT16RW0x0001 (1
F800:02Input type Ch2Select input type for Ch2UINT16RW0x0001 (1
F800:08Output typeSelect input type for Ch1UINT16RW0x0001 (1
5.7.3.2Objects for regular operation
The EP8309 has no such objects.
EP8309-102284Version: 2.0.0
)
dec
)
dec
)
dec
)
dec
Page 85
Commissioning and Configuration
5.7.3.3Standard objects (0x1000-0x1FFF)
The standard objects have the same meaning for all EtherCAT slaves.
Index 1000 Device type
Index (hex) NameMeaningData typeFlagsDefault
1000:0Device typeDevice type of the EtherCAT slave: The Low-Word con-
tains the CoE profile used (5001). The High-Word contains the module profile according to the modular device
profile.
Index 1008 Device name
Index (hex) NameMeaningData typeFlagsDefault
1008:0Device nameDevice name of the EtherCAT slaveSTRINGROEP8309-1022
Index 1009 Hardware version
Index (hex) NameMeaningData typeFlagsDefault
1009:0Hardware versionHardware version of the EtherCAT slaveSTRINGRO00
Index 100A Software Version
Index (hex) NameMeaningData typeFlagsDefault
100A:0Software versionFirmware version of the EtherCAT slaveSTRINGRO02
UINT32RO0x00001389
(5001
)
dec
Index 1011 Restore default parameters
Index (hex) NameMeaningData typeFlagsDefault
1011:0Restore default pa-
rameters
1011:01SubIndex 001If this object is set to "0x64616F6C" in the set value dia-
Restore default parametersUINT8RO0x01 (1
UINT32RW0x00000000
log, all backup objects are reset to their delivery state.
(0
)
dec
dec
Index 1018 Identity
Index (hex) NameMeaningData typeFlagsDefault
1018:0IdentityInformation for identifying the slaveUINT8RO0x04 (4
dec
1018:01Vendor IDVendor ID of the EtherCAT slaveUINT32RO0x00000002
(2
)
dec
1018:02Product codeProduct code of the EtherCAT slaveUINT32RO0x20754052
(544555090
)
1018:03RevisionRevision numberof the EtherCAT slave; the low word (bit
0-15) indicates the special terminal number, the high
UINT32RO0x00110016
(1114134
word (bit 16-31) refers to the device description
1018:04Serial numberSerial number of the EtherCAT slave; the low byte (bit
0-7) of the low word contains the year of production, the
high byte (bit 8-15) of the low word contains the week of
UINT32RO0x00000000
(0
)
dec
production, the high word (bit 16-31) is 0
Index 10F0 Backup parameter handling
Index (hex) NameMeaningData typeFlagsDefault
10F0:0Backup parameter
handling
10F0:01ChecksumChecksum across all backup entries of the EtherCAT
Information for standardized loading and saving of
backup entries
slave
UINT8RO0x01 (1
dec
UINT32RO0x00000000
(0
)
dec
)
)
dec
)
dec
)
EP8309-102285Version: 2.0.0
Page 86
Commissioning and Configuration
Index 1402 PWM RxPDO-Par Control
Index (hex) NameMeaningData typeFlagsDefault
1402:0PWM RxPDO-Par
Control
1402:06Exclude RxPDOsSpecifies the RxPDOs (index of RxPDO mapping ob-
PDO Parameter RxPDO 3UINT8RO0x06 (6
jects) that must not be transferred together with RxPDO
OCTETSTRING[2]
RO03 16
)
dec
3
Index 1403 AO RxPDO-Par Outputs
Index (hex) NameMeaningData typeFlagsDefault
1403:0AO RxPDO-Par Out-
puts
1403:06Exclude RxPDOsSpecifies the RxPDOs (index of RxPDO mapping ob-
PDO Parameter RxPDO 4UINT8RO0x06 (6
jects) that must not be transferred together with RxPDO
806F:01OffsetVendor calibration for +/-10 VINT16RW0x0000 (0
806F:02GainVendor calibration for +/-10 VINT16RW0x4000
(16384
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
EP8309-102296Version: 2.0.0
Page 97
Commissioning and Configuration
Index 807E AO Internal data
Index (hex) NameMeaningData typeFlagsDefault
807E:0AO Internal DataUINT8RO0x01 (1
807E:01DAC Raw ValueThis is the raw DAC value.UINT16RO0x0000 (0
Index 807F AO Vendor data
Index (hex) NameMeaningData typeFlagsDefault
807F:0AO Vendor DataUINT8RO0x06 (6
807F:01R0 Calibration Offset Vendor calibration for +/-10 VINT16RW0x0000 (0
807F:02R0 Calibration GainVendor calibration for +/-10 VUINT16RW0x4000
(16384
807F:03R1 Calibration Offset Vendor calibration for 0-20 mAINT16RW0x0000 (0
807F:04R1 Calibration GainVendor calibration for 0-20 mAUINT16RW0x4000
(16384
807F:05R2 Calibration Offset Vendor calibration for 4-20 mAINT16RW0x0000 (0
807F:06R2 Calibration GainVendor calibration for 4-20 mAUINT16RW0x4000
(16384
Index A060 PWM Diag data
Index (hex) NameMeaningData typeFlagsDefault
A060:0PWM Diag dataUINT8RO0x06 (6
A060:02OvertemperatureBOOLEANRO0x00 (0
A060:06Short circuitBOOLEANRO0x00 (0
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
Index F000 Modular Device Profile
Index (hex) NameMeaningData typeFlagsDefault
F000:0Modular device profile General information for the modular device profileUINT8RO0x02 (2
F000:01Module index dis-
Index distance of the objects of the individual channelsUINT16RO0x0010 (16
)
dec
tance
F000:02Maximum number of
Number of channelsUINT16RO0x0008 (8
modules
Index F008 Code word
Index (hex) NameMeaningData typeFlagsDefault
F008:0Code wordUINT32RW0x00000000
(0
)
dec
Index F010 Module List
Index (hex) NameMeaningData typeFlagsDefault
F010:0Module listUINT8RW0x08 (8
F010:01SubIndex 001UINT32RW0x0000012C
(300
F010:02SubIndex 002UINT32RW0x0000012C
(300
F010:03SubIndex 003UINT32RW0x00000208
(520
F010:04SubIndex 004UINT32RW0x00000208
(520
F010:05SubIndex 005UINT32RW0x00000064
(100
F010:06SubIndex 006UINT32RW0x000000C8
(200
F010:07SubIndex 007UINT32RW0x000000FA
(250
F010:08SubIndex 008UINT32RW0x00000190
(400
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
EP8309-102297Version: 2.0.0
Page 98
Commissioning and Configuration
Index F900 PWM Info data
Index (hex) NameMeaningData typeFlagsDefault
F900:0PWM Info dataUINT8RO0x02 (2
F900:02Temperature [°C]UINT8RO0x00 (0
)
dec
)
dec
Index FB00 PWM Command
Index (hex) NameMeaningData typeFlagsDefault
FB00:0PWM CommandUINT8RO0x03 (3
FB00:01RequestOCTET-
STRING[2]
FB00:02StatusUINT8RO0x00 (0
FB00:03ResponseOCTET
STRING[4]
RW{0}
RO{0}
)
dec
)
dec
5.8Restoring the delivery state
The CoE object Restore default parameters, Subindex 001 can be selected in the TwinCAT System
Manager (Config mode) in order to restore the delivery state of the back-up objects for the EPPxxxx Boxes.
Fig.67: Selecting the PDO restore default parameter
Double-click on SubIndex 001 to enter the Set Value dialog. Enter the value 1684107116 in the field Dec or
alternatively the value 0x64616F6C in the field Hex and confirm with OK.
All backup objects are reset to the delivery state.
EP8309-102298Version: 2.0.0
Page 99
Fig.68: Entering a restore value in the Set Value dialog
Alternative restore value
With some older modules the backup objects can be changed with an alternative restore
An incorrect entry for the restore value has no effect.
Commissioning and Configuration
EP8309-102299Version: 2.0.0
Page 100
Diagnostics
6Diagnostics
The module offers various diagnostic options for users. These messages are divided into hardware warnings
and hardware errors. The respective status words for the channels (except digital inputs and outputs) contain
a bit for warnings and errors. The exact cause is analyzed via the diagnostic data (0xA050). Warnings are
reset automatically. Errors may result in the output stage being switched off (PWMi) and have to be
acknowledged in the control word (0x7050:07 Reset)
Error/warning for the PWM stage
Index (hex) WarningMeaning
A050:02Overtemperaturefrom 100°C
A050:06Short circuitAn overcurrent/short circuit of more than 105% of the rated current has
occurred for more than 200 ms
Control voltage (Us) and peripheral voltage (Up) of the EP8309
Fig.69: Diagnostic control voltage (Us) and peripheral voltage (Up) of the EP8309