Beckhoff EL5032, EL5032-0090 Documentation
Documentation
EL5032, EL5032-0090
2 channel EnDat2.2-Interface
Version:
Date:
2.4
2019-10-30
Table of contents
Table of contents
1 Foreword ....................................................................................................................................................5
1.1 Two-channel ENDAT 2.2 interface - product overview......................................................................5
1.2 Notes on the documentation..............................................................................................................5
1.3 Safety instructions .............................................................................................................................6
1.4 Documentation issue status ..............................................................................................................7
1.5 Version identification of EtherCAT devices .......................................................................................7
1.5.1 Beckhoff Identification Code (BIC)................................................................................... 12
2 Product overview.....................................................................................................................................14
2.1 EL5032-00x0 - Introduction .............................................................................................................14
2.2 Technical data .................................................................................................................................16
2.3 Start .................................................................................................................................................16
3 Basics communication ...........................................................................................................................17
3.1 EtherCAT basics..............................................................................................................................17
3.2 EtherCAT cabling – wire-bound.......................................................................................................17
3.3 General notes for setting the watchdog...........................................................................................18
3.4 EtherCAT State Machine.................................................................................................................20
3.5 CoE Interface...................................................................................................................................22
3.6 Distributed Clock .............................................................................................................................27
4 Basics of EnDat 2.2 technology .............................................................................................................28
4.1 EnDat 2.2 - Bidirectional interface for position measuring devices .................................................28
4.2 Connection technology ....................................................................................................................30
4.3 Compatibility ....................................................................................................................................30
4.4 Functional description......................................................................................................................31
4.5 Data transfer....................................................................................................................................33
5 Mounting and wiring................................................................................................................................34
5.1 Instructions for ESD protection........................................................................................................34
5.2 Installation on mounting rails ...........................................................................................................34
5.3 Installation instructions for enhanced mechanical load capacity .....................................................38
5.4 Connection ......................................................................................................................................38
5.4.1 Connection system .......................................................................................................... 38
5.4.2 Wiring............................................................................................................................... 41
5.4.3 Shielding .......................................................................................................................... 42
5.5 Installation positions ........................................................................................................................42
5.6 Positioning of passive Terminals .....................................................................................................45
5.7 ATEX - Special conditions (standard temperature range) ...............................................................46
5.8 ATEX Documentation ......................................................................................................................47
5.9 UL notice .........................................................................................................................................47
5.10 LEDs and connection ......................................................................................................................48
6 Commissioning........................................................................................................................................50
6.1 Quick start........................................................................................................................................50
6.2 TwinCAT Development Environment ..............................................................................................50
6.2.1 Installation of the TwinCAT real-time driver..................................................................... 51
6.2.2 Notes regarding ESI device description........................................................................... 56
EL5032, EL5032-0090 3Version: 2.4
Table of contents
6.2.3 TwinCAT ESI Updater ..................................................................................................... 60
6.2.4 Distinction between Online and Offline............................................................................ 60
6.2.5 OFFLINE configuration creation ...................................................................................... 61
6.2.6 ONLINE configuration creation ........................................................................................ 66
6.2.7 EtherCAT subscriber configuration.................................................................................. 74
6.3 General Notes - EtherCAT Slave Application..................................................................................83
6.4 Process data....................................................................................................................................91
6.4.1 Sync Manager (SM)......................................................................................................... 91
6.4.2 PDO Assignment ............................................................................................................. 91
6.4.3 Predefined PDO Assignment........................................................................................... 93
6.4.4 Overview of commands and samples.............................................................................. 93
6.5 TwinSAFE SC..................................................................................................................................96
6.5.1 TwinSAFE SC - operating principle ................................................................................. 96
6.5.2 TwinSAFE SC - configuration .......................................................................................... 96
6.6 EL5032-0090 - TwinSAFE SC process data .................................................................................100
6.7 EL5032-00x0 - object description and parameterization ...............................................................100
6.7.1 Restore object................................................................................................................ 101
6.7.2 Configuration data ......................................................................................................... 101
6.7.3 Command object............................................................................................................ 102
6.7.4 Input data....................................................................................................................... 102
6.7.5 Information data............................................................................................................. 103
6.7.6 Diagnostic data .............................................................................................................. 104
6.7.7 Standard objects............................................................................................................ 106
6.8 EL5032-0090 - TwinSAFE Single Channel objects .......................................................................113
7 Diagnostics ............................................................................................................................................116
7.1 Diagnostics – basic principles of diag messages ..........................................................................116
8 Appendix ................................................................................................................................................126
8.1 Firmware compatibility...................................................................................................................126
8.2 Firmware Update EL/ES/EM/ELM/EPxxxx ....................................................................................126
8.2.1 Device description ESI file/XML..................................................................................... 127
8.2.2 Firmware explanation .................................................................................................... 130
8.2.3 Updating controller firmware *.efw................................................................................. 131
8.2.4 FPGA firmware *.rbf....................................................................................................... 133
8.2.5 Simultaneous updating of several EtherCAT devices.................................................... 137
8.3 Restoring the delivery state ...........................................................................................................138
8.4 Support and Service ......................................................................................................................139
EL5032, EL5032-00904 Version: 2.4
Foreword
1 Foreword
1.1 Two-channel ENDAT 2.2 interface - product overview
EL5032 [}14]
EL5032-0090 [}14]
2-channel ENDAT 2.2 interface
2-channel ENDAT 2.2 interface (TwinSAFE Single Channel)
1.2 Notes 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®, EtherCATG®, EtherCATG10®, EtherCATP®, SafetyoverEtherCAT®,
TwinSAFE®, XFC®, XTS® and XPlanar® 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, EP1456722, EP2137893, DE102015105702 with corresponding
applications or registrations in various other countries.
EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany.
Copyright
© Beckhoff Automation GmbH & Co. KG, Germany.
The reproduction, distribution and utilization of this document as well as the communication of its contents to
others without express authorization are prohibited.
Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a
patent, utility model or design.
EL5032, EL5032-0090 5Version: 2.4
Foreword
1.3 Safety instructions
Safety regulations
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 instructions
In this documentation the following instructions are used.
These instructions must be read carefully and followed without fail!
DANGER
Serious risk of injury!
Failure to follow this safety instruction directly endangers the life and health of persons.
WARNING
Risk of injury!
Failure to follow this safety instruction endangers the life and health of persons.
CAUTION
Personal injuries!
Failure to follow this safety instruction can lead to injuries to persons.
NOTE
Damage to environment/equipment or data loss
Failure to follow this instruction can lead to environmental damage, equipment damage or data loss.
Tip or pointer
This symbol indicates information that contributes to better understanding.
EL5032, EL5032-00906 Version: 2.4
1.4 Documentation issue status
Version Comment
2.4 • Update chapter “Basics of EnDat 2.2 technology”
• Structural update
2.3 • EL5032-0090 added
• Structural update
• Update revision status
2.2 • Chapter "Principles of EnDat 2.2 technology" updated
• Update revision status
• Structural update
2.1 • Update chapter "Notes on the documentation"
• Update chapter "Technical data"
• Note on ESD protection added
• Chapter "Installation instructions for enhanced mechanical load capacity" added
• Chapter "ATEX - special conditions" replaced by chapter "ATEX - special conditions
(standard temperature range)"
• Chapter "TwinCAT 2.1x" -> "TwinCAT Development Environment" updated
• Chapter "Diagnosis" updated
• Update revision status
2.0 • Migration
1.2 • Structural update
• Update chapter "Technical data"
• Revision status updated
1.0.1 • Complements, corrections
1.0 • Addenda, corrections, 1st public issue
0.3 • Complements, corrections
0.2 • Complements, corrections
0.1 • Provisional documentation for EL5032
Foreword
1.5 Version identification of EtherCAT devices
Designation
A Beckhoff EtherCAT device has a 14-digit designation, made up of
• family key
• type
• version
• revision
Example Family Type Version Revision
EL3314-0000-0016 EL terminal
(12 mm, nonpluggable connection
level)
ES3602-0010-0017 ES terminal
(12 mm, pluggable
connection level)
CU2008-0000-0000 CU device 2008 (8-port fast ethernet switch) 0000 (basic type) 0000
EL5032, EL5032-0090 7Version: 2.4
3314 (4-channel thermocouple
terminal)
3602 (2-channel voltage
measurement)
0000 (basic type) 0016
0010 (highprecision version)
0017
Foreword
Notes
• The elements mentioned above result in the technical designation. EL3314-0000-0016 is used in the
example below.
• EL3314-0000 is the order identifier, in the case of “-0000” usually abbreviated to EL3314. “-0016” is the
EtherCAT revision.
• The order identifier is made up of
- family key (EL, EP, CU, ES, KL, CX, etc.)
- type (3314)
- version (-0000)
• The revision -0016 shows the technical progress, such as the extension of features with regard to the
EtherCAT communication, and is managed by Beckhoff.
In principle, a device with a higher revision can replace a device with a lower revision, unless specified
otherwise, e.g. in the documentation.
Associated and synonymous with each revision there is usually a description (ESI, EtherCAT Slave
Information) in the form of an XML file, which is available for download from the Beckhoff web site.
From 2014/01 the revision is shown on the outside of the IP20 terminals, see Fig. “EL5021 EL terminal,
standard IP20 IO device with batch number and revision ID (since 2014/01)”.
• The type, version and revision are read as decimal numbers, even if they are technically saved in
hexadecimal.
Identification number
Beckhoff EtherCAT devices from the different lines have different kinds of identification numbers:
Production lot/batch number/serial number/date code/D number
The serial number for Beckhoff IO devices is usually the 8-digit number printed on the device or on a sticker.
The serial number indicates the configuration in delivery state and therefore refers to a whole production
batch, without distinguishing the individual modules of a batch.
Structure of the serial number: KKYYFFHH
KK - week of production (CW, calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Example with
Ser. no.: 12063A02: 12 - production week 12 06 - production year 2006 3A - firmware version 3A 02 hardware version 02
Exceptions can occur in the IP67 area, where the following syntax can be used (see respective device
documentation):
Syntax: D ww yy x y z u
D - prefix designation
ww - calendar week
yy - year
x - firmware version of the bus PCB
y - hardware version of the bus PCB
z - firmware version of the I/O PCB
u - hardware version of the I/O PCB
Example: D.22081501 calendar week 22 of the year 2008 firmware version of bus PCB: 1 hardware version
of bus PCB: 5 firmware version of I/O PCB: 0 (no firmware necessary for this PCB) hardware version of I/O
PCB: 1
Unique serial number/ID, ID number
In addition, in some series each individual module has its own unique serial number.
See also the further documentation in the area
EL5032, EL5032-00908 Version: 2.4
• IP67: EtherCAT Box
• Safety: TwinSafe
• Terminals with factory calibration certificate and other measuring terminals
Examples of markings
Fig.1: EL5021 EL terminal, standard IP20 IO device with serial/ batch number and revision ID (since
2014/01)
Foreword
Fig.2: EK1100 EtherCAT coupler, standard IP20 IO device with serial/ batch number
Fig.3: CU2016 switch with serial/ batch number
EL5032, EL5032-0090 9Version: 2.4
Foreword
Fig.4: EL3202-0020 with serial/ batch number 26131006 and unique ID-number 204418
Fig.5: EP1258-00001 IP67 EtherCAT Box with batch number/ date code 22090101 and unique serial
number 158102
Fig.6: EP1908-0002 IP67 EtherCAT Safety Box with batch number/ date code 071201FF and unique serial
number 00346070
Fig.7: EL2904 IP20 safety terminal with batch number/ date code 50110302 and unique serial number
00331701
EL5032, EL5032-009010 Version: 2.4
Foreword
Fig.8: ELM3604-0002 terminal with unique ID number (QR code) 100001051 and serial/ batch number
44160201
EL5032, EL5032-0090 11Version: 2.4
Foreword
1.5.1 Beckhoff Identification Code (BIC)
The Beckhoff Identification Code (BIC) is increasingly being applied to Beckhoff products to uniquely identify
the product. The BIC is represented as a Data Matrix Code (DMC, code scheme ECC200), the content is
based on the ANSI standard MH10.8.2-2016.
Fig.9: BIC as data matrix code (DMC, code scheme ECC200)
The BIC will be introduced step by step across all product groups.
Depending on the product, it can be found in the following places:
• on the packaging unit
• directly on the product (if space suffices)
• on the packaging unit and the product
The BIC is machine-readable and contains information that can also be used by the customer for handling
and product management.
Each piece of information can be uniquely identified using the so-called data identifier
(ANSIMH10.8.2-2016). The data identifier is followed by a character string. Both together have a maximum
length according to the table below. If the information is shorter, spaces are added to it. The data under
positions 1 to 4 are always available.
The following information is contained:
EL5032, EL5032-009012 Version: 2.4
Item
Type of
no.
information
1 Beckhoff order
number
2 Beckhoff Traceability
Number (BTN)
3 Article description Beckhoff article
4 Quantity Quantity in packaging
5 Batch number Optional: Year and week
6 ID/serial number Optional: Present-day
7 Variant number Optional: Product variant
...
Explanation Data
Beckhoff order number 1P 8 1P072222
Unique serial number,
see note below
description, e.g.
EL1008
unit, e.g. 1, 10, etc.
of production
serial number system,
e.g. with safety products
number on the basis of
standard products
Foreword
Number of digits
identifier
S 12 SBTNk4p562d7
1K 32 1KEL1809
Q 6 Q1
2P 14 2P401503180016
51S 12 51S678294104
30P 32 30PF971, 2*K183
incl. data identifier
Example
Further types of information and data identifiers are used by Beckhoff and serve internal processes.
Structure of the BIC
Example of composite information from item 1 to 4 and 6. The data identifiers are marked in red for better
display:
BTN
An important component of the BIC is the Beckhoff Traceability Number (BTN, item no.2). The BTN is a
unique serial number consisting of eight characters that will replace all other serial number systems at
Beckhoff in the long term (e.g. batch designations on IO components, previous serial number range for
safety products, etc.). The BTN will also be introduced step by step, so it may happen that the BTN is not yet
coded in the BIC.
NOTE
This information has been carefully prepared. However, the procedure described is constantly being further
developed. We reserve the right to revise and change procedures and documentation at any time and without prior notice. No claims for changes can be made from the information, illustrations and descriptions in
this information.
EL5032, EL5032-0090 13Version: 2.4
Product overview
2 Product overview
2.1 EL5032-00x0 - Introduction
EL5032-0000
Fig.10: EL5032
Two-channel EnDat2.2 interface
The EL5032 EnDat 2.2 EtherCAT Terminal is used for direct connection of two encoders with EnDat2.2
interface.
The EL5032 enables reading of position values, diagnosis encoder data, internal and external temperature
values and the electronic type plate. With the electronic type plate all measuring device-specific information
is directly available.
In addition, user-defined data can be stored in the encoder. This enables cost-effective and quicker
commissioning. The position value is output with up to 48 bits, depending on the resolution of the connected
measuring device. In addition to the position value, further information such as status information, addresses
and data can be transferred.
A list of additional information supported by the encoder is stored in the parameters.
The EL5032 features distributed clocks, which means that the position value can be read in exact synchrony
with the system. If the distributed clock function is deactivated, the EL5032 cycles synchronous with the
EtherCAT cycle.
EL5032, EL5032-009014 Version: 2.4
EL5032-0090
Product overview
Fig.11: EL5032-0090
In addition to the full functionality of the EL5032-0000, the EL5032-0090 supports TwinSAFE SC (Single
Channel) technology. This enables the use of standard signals for safety tasks in any networks of fieldbuses.
Quick links
• Basic Function Principles [}28]
• Quick start [}50]
• EL5032-00x0 - object description and parameterization [}100]
• EL5032-0090 - TwinSAFE Single Channel objects [}113]
• EL5032-0090 - TwinSAFE process data [}100]
EL5032, EL5032-0090 15Version: 2.4
Product overview
2.2 Technical data
Technical data EL5032-0000 EL5032-0090
Technology ENDat2.2 interface
Number of channels 2
Encoder connection, encoder clock
frequency
Commands Reading position values including additional information available for
Distributed Clocks yes
Power supply 24V via power contacts
Nominal voltage 24V at power contact, encoder supply included in the installation,
Current cons. power contacts typ. 150mA
Encoder supply optionally 5VDC or 9V
Resolution max. 48bit for position value
Electrical isolation 500V (E-bus/field voltage)
Current consumption via E-bus typ. 120mA
Special features EL5032-00x0: Saving the zero offset shift, electronic type plate,
Configuration via EtherCAT master/CoE
MTBF (+55 °C) - >790,000h
Weight app.50g
Permissible ambient temperature
range during operation
Permissible ambient temperature
range during storage
Permissible relative air humidity 95%, no condensation
Dimensions (WxHxD) approx. 15mm x 100mm x 70mm (width aligned: 12mm)
Mounting on 35mm mounting rail according to EN60715
Vibration/shock resistance conforms to EN60068-2-6/ EN60068-2-27,
EMC immunity/emission conforms to EN61000-6-2/ EN61000-6-4
Protection class IP20
Installation position variable
Approvals CE
D+, D-, C+, C-; 8MHz
selection via MRS code (Memory Range Select), reading and writing
parameters, reset functions
total current max. 0.5A for both channels
DC
diagnostics, warning, including cable length compensation up to
100m, reading the encoder temperature values
EL5032-0090: TwinSAFE SC
0°C ... +55°C
-25°C...+85°C
see also Installation instructions for enhanced mechanical load
capacity [}38]
cULus [}47]
2.3 Start
For commissioning:
• mount the EL5032 as explained in the chapter Mounting and wiring [}34]
• configure the EL5032 in TwinCAT as described in the chapter Commissioning [}50].
For fast commissioning please refer to chapter Commissioning -> Quick start [}50].
EL5032, EL5032-009016 Version: 2.4
Basics communication
3 Basics communication
3.1 EtherCAT basics
Please refer to the EtherCAT System Documentation for the EtherCAT fieldbus basics.
3.2 EtherCAT cabling – wire-bound
The cable length between two EtherCAT devices must not exceed 100 m. This results from the FastEthernet
technology, which, above all for reasons of signal attenuation over the length of the cable, allows a maximum
link length of 5 + 90 + 5 m if cables with appropriate properties are used. See also the Design
recommendations for the infrastructure for EtherCAT/Ethernet.
Cables and connectors
For connecting EtherCAT devices only Ethernet connections (cables + plugs) that meet the requirements of
at least category 5 (CAt5) according to EN 50173 or ISO/IEC 11801 should be used. EtherCAT uses 4 wires
for signal transfer.
EtherCAT uses RJ45 plug connectors, for example. The pin assignment is compatible with the Ethernet
standard (ISO/IEC 8802-3).
Pin Color of conductor Signal Description
1 yellow TD + Transmission Data +
2 orange TD - Transmission Data 3 white RD + Receiver Data +
6 blue RD - Receiver Data -
Due to automatic cable detection (auto-crossing) symmetric (1:1) or cross-over cables can be used between
EtherCAT devices from Beckhoff.
Recommended cables
Suitable cables for the connection of EtherCAT devices can be found on the Beckhoff website!
E-Bus supply
A bus coupler can supply the EL terminals added to it with the E-bus system voltage of 5V; a coupler is
thereby loadable up to 2A as a rule (see details in respective device documentation).
Information on how much current each EL terminal requires from the E-bus supply is available online and in
the catalogue. If the added terminals require more current than the coupler can supply, then power feed
terminals (e.g. EL9410) must be inserted at appropriate places in the terminal strand.
The pre-calculated theoretical maximum E-Bus current is displayed in the TwinCAT System Manager. A
shortfall is marked by a negative total amount and an exclamation mark; a power feed terminal is to be
placed before such a position.
EL5032, EL5032-0090 17Version: 2.4
Basics communication
Fig.12: System manager current calculation
NOTE
Malfunction possible!
The same ground potential must be used for the E-Bus supply of all EtherCAT terminals in a terminal block!
3.3 General notes for setting the watchdog
ELxxxx terminals are equipped with a safety feature (watchdog) that switches off the outputs after a
specifiable time e.g. in the event of an interruption of the process data traffic, depending on the device and
settings, e.g. in OFF state.
The EtherCAT slave controller (ESC) in the EL2xxx terminals features 2 watchdogs:
• SM watchdog (default: 100 ms)
• PDI watchdog (default: 100 ms)
SM watchdog (SyncManager Watchdog)
The SyncManager watchdog is reset after each successful EtherCAT process data communication with the
terminal. If no EtherCAT process data communication takes place with the terminal 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 state of the terminal is unaffected. The watchdog is only reset after a
successful EtherCAT process data access. Set the monitoring time as described 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 from the
application side.
The settings of the SM- and PDI-watchdog must be done for each slave separately in the TwinCAT System
Manager.
EL5032, EL5032-009018 Version: 2.4
Basics communication
Fig.13: EtherCAT tab -> Advanced Settings -> Behavior -> Watchdog
Notes:
• the multiplier is valid for both watchdogs.
• each watchdog has its own timer setting, the outcome of this in summary with the multiplier is a
resulting time.
• Important: the multiplier/timer setting is only loaded into the slave at the start up, if the checkbox is
activated.
If the checkbox is not activated, nothing is downloaded and the ESC settings remain unchanged.
Multiplier
Multiplier
Both watchdogs receive their pulses from the local terminal cycle, 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 40 ns ticks representing a watchdog tick.
The multiplier can be modified in order to adjust the watchdog time over a larger range.
EL5032, EL5032-0090 19Version: 2.4
Basics communication
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 erased.
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 0..65535. Together with a multiplier with a range
of 1..65535 this covers a watchdog period between 0..~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
CAUTION
Undefined state 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 of devices and undefined state possible!
If the SM watchdog is activated and a value of 0 is entered the watchdog switches off completely. This is
the deactivation of the watchdog! Set outputs are NOT set in a safe state, if the communication is interrupted.
3.4 EtherCAT 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.
EL5032, EL5032-009020 Version: 2.4
Fig.14: States of the EtherCAT State Machine
Basics communication
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).
In Safe-Op state mailbox and process data communication is possible, although the slave keeps its outputs
in a safe state, while the input data are updated cyclically.
Outputs in SAFEOP state
The default set watchdog [}18] monitoring sets the outputs of the module in a safe state - depending on the settings in SAFEOP and OP - e.g. in OFF state. If this is prevented by deactivation of the
watchdog monitoring in the module, the outputs can be switched or set also in the SAFEOP state.
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.
EL5032, EL5032-0090 21Version: 2.4
Basics communication
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.
3.5 CoE 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 attributes.
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.
The order is specified in 2 levels via hexadecimal numbering: (main)index, followed by subindex. The value
ranges are
• Index: 0x0000 …0xFFFF (0...65535
• SubIndex: 0x00…0xFF (0...255
dez
)
dez
)
A parameter localized in this way is normally written as 0x8010: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:
• 0x1000: 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.
• 0x8000: This is where the operational and functional parameters for all channels are stored, such as
filter settings or output frequency.
Other important ranges are:
• 0x4000: In some EtherCAT devices the channel parameters are stored here (as an alternative to the
0x8000 range).
• 0x6000: Input PDOs ("input" from the perspective of the EtherCAT master)
• 0x7000: 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 processor
usually have no variable parameters and therefore no CoE list.
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:
EL5032, EL5032-009022 Version: 2.4
Basics communication
Fig.15: "CoE Online " tab
The figure above shows the CoE objects available in device "EL2502", ranging from 0x1000 to 0x1600. The
subindices for 0x1018 are expanded.
Data management and function "NoCoeStorage"
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 (Fig. "CoE Online " tab) by clicking
This is useful for commissioning of the system/slaves. Click on the row of the index to be
parameterised and enter a value in the "SetValue" dialog.
• from the control system/PLC via ADS, e.g. through 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 slave CoE parameters are modified online, Beckhoff devices store any changes in a fail-safe
manner in the EEPROM, i.e. the modified CoE parameters are still available after a restart.
The situation may be different with other manufacturers.
An EEPROM is subject to a limited lifetime with respect to write operations. From typically 100,000
write operations onwards it can no longer be guaranteed that new (changed) data are reliably saved
or are still readable. This is irrelevant for normal commissioning. However, if CoE parameters are
continuously changed via ADS at machine runtime, it is quite possible for the lifetime limit to be
reached. Support for the NoCoeStorage function, which suppresses the saving of changed CoE values, depends on the firmware version.
Please refer to the technical data in this documentation as to whether this applies to the respective
device.
• If the function is supported: the function is activated by entering the code word 0x12345678 once
in CoE 0xF008 and remains active as long as the code word is not changed. After switching the
device on it is then inactive. Changed CoE values are not saved in the EEPROM and can thus
be changed any number of times.
• Function is not supported: continuous changing of CoE values is not permissible in view of the
lifetime limit.
EL5032, EL5032-0090 23Version: 2.4
Basics communication
Startup list
Changes in the local CoE list of the terminal are lost if the terminal is replaced. If a terminal is replaced with a new Beckhoff terminal, it will have the default 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
• If the value is to be stored permanently, enter it in the Startup list.
The order of the Startup entries is usually irrelevant.
Fig.16: 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 list
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 list as shown in Fig. “’CoE online’ tab” is displayed. The connectivity is shown 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.
EL5032, EL5032-009024 Version: 2.4
Basics communication
Fig.17: Offline list
• If the slave is online
◦ The actual current slave list 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.18: Online list
EL5032, EL5032-0090 25Version: 2.4
Basics communication
Channel-based order
The CoE list is available in EtherCAT devices that usually feature several functionally equivalent channels.
For example, a 4-channel analog 0..10 V input terminal also has 4 logical channels and therefore 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
hex
0x8000 exemplifies this:
• Channel 0: parameter range 0x8000:00 ... 0x800F:255
• Channel 1: parameter range 0x8010:00 ... 0x801F:255
• Channel 2: parameter range 0x8020:00 ... 0x802F:255
• ...
This is generally written as 0x80n0.
Detailed information on the CoE interface can be found in the EtherCAT system documentation on the
Beckhoff website.
EL5032, EL5032-009026 Version: 2.4
Basics communication
3.6 Distributed Clock
The distributed clock represents a local clock in the EtherCAT slave controller (ESC) with the following
characteristics:
• Unit 1 ns
• Zero point 1.1.2000 00:00
• Size 64 bit (sufficient for the next 584 years; however, some EtherCAT slaves only offer 32-bit support,
i.e. the variable overflows after approx. 4.2 seconds)
• The EtherCAT master automatically synchronizes the local clock with the master clock in the EtherCAT
bus with a precision of < 100 ns.
For detailed information please refer to the EtherCAT system description.
EL5032, EL5032-0090 27Version: 2.4
Basics of EnDat 2.2 technology
4 Basics of EnDat 2.2 technology
Basic information on the technological field of "EnDat interface" is to be given below. It is up to users to
check to what extent this information refers to their application.
4.1 EnDat 2.2 - Bidirectional interface for position measuring devices
Digital drive systems and position control loops with position measuring devices for data sampling require
measuring equipment offering fast data transfer with high transmission integrity.
In addition, further data such as drive-specific characteristic values, correction tables etc. should be
provided. To ensure high system reliability, the measuring devices should be integrated in error detection
routines and offer diagnostic capabilities.
The EnDat 2.2 interface is a digital, bidirectional interface for measuring devices. It is able to output position
values of incremental and absolute measuring devices and read and update information stored in the
measuring device, as well as store new information. 4 signal cables are sufficient, due to the fact that the
data transfer is serial. The data is transferred synchronous with the clock signal specified by the downstream
electronics. The transmission type (position values, parameters, diagnostics ...) is selected via mode
commands, received by the measuring device from the downstream electronics. As a purely serial interface,
EnDat 2.2 is also suitable for safety applications.
Fig.19: Signal cables and power supply for the EnDat 2.2 interface**
Incremental signals and ordering designation (HEIDENHAIN EnDat interfaces)**
Some encoders also provide incremental signals. These are usually used to increase the resolution of the
position value, or to serve a second subsequent electronics unit.
Current generations of encoders have a high internal resolution, and therefore no longer need to provide
incremental signals.
EL5032, EL5032-009028 Version: 2.4
Basics of EnDat 2.2 technology
The order designation indicates whether an encoder outputs incremental signals:
• EnDat 01 with 1 VPP incremental signals
• EnDat H with HTL incremental signals
• EnDat T with TTL incremental signals
• EnDat 21 without incremental signals
• EnDat 02 with 1 VPP incremental signals
• EnDat 22 without incremental signals
**) Source: Dr. Johannes HEIDENHAIN GmbH
Connection of HEIDENHAIN EnDat-interfaces to the EL5032
The EL5032 can only be connected to measuring instruments that support a clock frequency of 8
MHz. This corresponds to the order designation EnDat22.
Encoders with the ordering designation EnDat02 can be operated at 8MHz on the EL5032 without
incremental signals using an appropriate adapter cable.
EL5032, EL5032-0090 29Version: 2.4
Basics of EnDat 2.2 technology
4.2 Connection technology
EnDat02 encoder connection**
EnDat02 encoders can feature a pluggable cable assembly. In choosing the version of the adapter
cable, the customer also decides whether the encoder will be operated with incremental signals
[}28] or without them.**
If an adapter cable without incremental signals is selected for the EnDat-02 measuring device, the
clock frequency of 8 MHz can be implemented and the EL5032 can be used.
**) Source: Dr. Johannes HEIDENHAIN GmbH
Data transfer from incremental or absolute sensors to the EL5032 can take place with a simple shielded 8wire cable (Fig. Connection of measuring sensors and EL5032).
Fig.20: Connection of measuring sensor and EL5032
4.3 Compatibility
The extended interface version EnDat 2.2 is compatible to the previous version 2.1 as regards
communication, the instruction sets and time conditions, but offers considerable advantages. For sample, it
is possible to transmit so-called additional information with the position value without having to start a
separate query for this. To this end the interface protocol has been extended and the time conditions
optimized as follows:
• Increased clock frequency (CLOCK)
• Optimized computing time (determination of position value within 5 µs)
• Minimized dead time (recovery time) (1.25 to 3.75 µs)
• Extended voltage supply range (UP = 3.6 to 5.25 V or 3.6 to 14 V at the measuring device)
Fig. Illustration of instruction set for EnDat 2.2 and 2.1** shows the instruction set for the extended EnDat 2.2
interface:
EL5032, EL5032-009030 Version: 2.4
Loading...