5.3Support and Service ........................................................................................................................78
EP3744-0041 and EP3744-10413Version: 2.2
Table of contents
EP3744-0041 and EP3744-10414Version: 2.2
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®, EtherCATP®, SafetyoverEtherCAT®, 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 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.
EP3744-0041 and EP3744-10416Version: 2.2
1.3Documentation Issue Status
VersionModifications
2.2• Update technical data
2.1• Update Safety instructions
• Correction in chapter Process image
• Correction in chapter Power cable
• Update chapter Mounting
2.0.0• Migration
1.3.0• Chapter Settings added
1.2.0• Power Connection updated
1.1.0• Front page updated
• EP3744-1041 added to EP3744-x041 introduction
• EP3744-1041 added to Technical Data
• Process image heading adapted
• Support and Service updated
• Safety instructions updated
• Notes on the documentation updated
• EtherCAT connection updated
• Nut torques for connectors updated
• EtherCAT cables updated
1.0.0• First release
0.1.0• Preliminary version
Foreword
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.
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):
D: WWYYFFHH
WW - week of production (calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Example with D no. 50 13 03 01:
50 - week of production 50
13 - year of production 2013
03 - firmware version 03
01 - hardware version 01
EP3744-0041 and EP3744-10417Version: 2.2
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.
EP3744-0041 and EP3744-10418Version: 2.2
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 Documentation for
EtherCAT, which is available for download from our website (www.beckhoff.com) under Downloads.
EtherCAT XML Device Description
You will find XML files (XML Device Description Files) for Beckhoff EtherCAT modules on our website (www.beckhoff.com) under Downloads, in the Configuration Files area.
EP3744-0041 and EP3744-10419Version: 2.2
Product overview
2.2Introduction
Fig.4: EP3744-0041, EP3744-1041
EtherCAT Box with 6 digital inputs (24VDC, 10µs), 2 digital outputs (24V
pressure inputs
The EP3744-x041 EtherCAT Box with six digital inputs and two digital outputs records binary control signals
from the process level and transfers them, electrically isolated, to the controller. The signal status is
indicated by LEDs, the signals are connected via 3-pole M8 plug connectors (sockets).
Four pneumatic connections (6mm) offer the possibility to directly measure differential pressure. This value
is measured or calculated in relation to the fifth reference pressure connection (6mm).
The sensors and outputs are supplied from the control voltage Us. Since only one GND is available on the
M8 plug for the inputs and outputs, this alternative supply was selected.
The load voltage Up is not used in the input module, but may optionally be connected in order to be relayed
downstream.
Pressure measurement with EP3744-0041
The pressure is measured as an absolute value or as a differential value relative to the fifth connection via
an integrated 6mm fitting. The pressure values are available as 16-bit values. Measurement can take place
between -1bar and +1bar, wherein the value is output relative to the fifth connection, e.g. for vacuum
measurement in relation to the ambient pressure at the suction grippers. In absolute pressure mode,
pressures between 0 and 1bar can be measured.
0.5A) and reference
DC,
Pressure measurement with EP3744-1041
The pressure is measured as an absolute value or as a differential value relative to the fifth connection via
an integrated 6mm fitting. The pressure values are available as 16-bit values. Measurement can take place
between -7bar and +7bar, wherein the value is output relative to the fifth connection, e.g. for vacuum
measurement in relation to the ambient pressure at the suction grippers. In absolute pressure mode,
pressures between 0 and 7bar can be measured.
• Installation [}14]
• UL requirements [}29] for UL-approved modules
EP3744-0041 and EP3744-104110Version: 2.2
Product overview
2.3Technical data
Technical dataEP3744-0041EP3744-1041
FieldbusEtherCAT
Fieldbus connection2 x M8 socket (green)
Number of digital inputs6 digital inputs
Input connections [}27]
Rated input voltage24VDC (-15%/+20%)
Input filter10µs (for digital inputs)
"0" signal voltage-3...+5V (EN61131-2, type3)
"1" signal voltage+11...+30V (EN61131-2, type3)
Input currenttypically 3mA (EN61131-2, type3)
Number of outputs2 digital outputs
Output connections [}27]
Rated output voltage24VDC (-15%/+20%)
DiagnosticsUndervoltage detection <18VDC for Us and Up
Number of pressure inputs4 pressure inputs + 1 reference pressure input, d = 6mm
Pressure connectorsFittings, d=6mm
Pressure sensors15psi / 1034hPa100psi / 6894hPa
Technology (optional)• Differential pressure measurement relative to reference
Measuring range differential pressure
measurement
Measuring range absolute pressure
measurement
Permissible mediaNon-aggressive gases
Resolution1mbar per digit
Measuring error3% of full scale value
Max. overload3 x P
Resolution (raw value)16bit
Conversion time5 x cycle time
Min. cycle time700µsec
Supply of the module circuitryfrom the control voltage Us
Current consumption of the module circuitry typically 120mA
Sensor supplyfrom the control voltage Us
Sensor current consumptionmax. 0.5A, short-circuit proof overall
Power supply connectionPower supply: 1 x M8 plug, 4-pole
Electrical isolationControl voltage/fieldbus: yes
Permissible ambient temperature during
operation
Permissible ambient temperature during
storage
Vibration/ shock resistanceconforms to EN60068-2-6/ EN60068-2-27
EMC immunity/emissionconforms to EN61000-6-2/ EN61000-6-4
Protection classIP65, IP66, IP67 (conforms to EN 60529)
Installation positionvariable
Approvals
-25°C ... +60°C
0 °C ... +55 °C (according to cULus, see UL requirements[}29])
-40°C ... +85°C
CE,cULus [}29]
EP3744-0041 and EP3744-104111Version: 2.2
Product overview
2.4Process image
Channel 1 to channel 16
The six digital inputs of the module can be found under DIG inputs 1 to 6.
• Input 1 - socket 0, pin 4
• Input 2 - socket 0, pin 2
• Input 3 - socket 1, pin 4
• Input 4 - socket 1, pin 2
• Input 5 - socket 2, pin 4
• Input 6 - socket 3, pin 4
The four pressure measuring inputs of the module can be found under AIinputs Channel 1 to 4.
• Underrange: the pressure has fallen below the underrange value
• Overrange: the pressure has exceeded the overrange value
• Limit1: the Limit1 value specified in the CoE objects was reached
• Limit2: the Limit2 value specified in the CoE objects was reached
• Error: one of the above events has occurred
• Value: the measured pressure value in the unit pre-scaled in the CoE
objects (e.g. mbar)
The diagnostic data for the module can be found under DEV Inputs Device.
• Safe State Active: there was an interruption in communication, causing the
outputs to change to the safe state
• Sync error: a synchronization error has occurred
• Undervoltage Us: the voltage Us is less than approx. 18V
• Undervoltage Up: the voltage Up is less than approx. 18V
DC
DC
• TxPDO Toggle: EtherCAT variable for displaying a transmitted date of
receipt (see general EtherCAT documentation)
The two digital outputs of the module can be found under DIG outputs 1 and
2.
• Output 1 - socket 2, pin 2
• Output 2 - socket 3, pin 2
EP3744-0041 and EP3744-104112Version: 2.2
Product overview
The output variables for setting or resetting the outputs of the module can be
found under DEV Output Device.
• Set safe state: outputs assume the defined value (see CoE objects)
• Reset Outputs: reserved
These are standard EtherCAT variables; more information in the general
EtherCAT manual.
EP3744-0041 and EP3744-104113Version: 2.2
Mounting and connection
3Mounting and connection
3.1Mounting
3.1.1Dimensions
Fig.5: Dimensions of the EtherCAT Box Modules
All dimensions are given in millimeters.
Housing properties
EtherCAT Boxlean bodywide bodies
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 through max. 4A (M8)
max. 16A (7/8“)
max. 15.5A (B17 5G 1.5mm2)
Installation positionvariable
Protection classIP65, IP66, IP67 (conforms to EN 60529) when screwed together
Dimensions
(HxWxD)
app. 126 x 30 x 26.5mmapp. 126 x 60 x 26,5mm
app. 150 x 60 x 26.5mm (without 7/8", B17)
EP3744-0041 and EP3744-104114Version: 2.2
Mounting and connection
3.1.2Fixing
Protection of connectors against contamination!
While mounting the modules, protect all connectors, especially the IP-Link, against contamination!
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.
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.
Fig.6: 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.
EP3744-0041 and EP3744-104115Version: 2.2
Mounting and connection
3.1.3Nut 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.7: 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.8: EtherCAT Box with M8 and M12 connectors
EP3744-0041 and EP3744-104116Version: 2.2
7/8" plug connectors
We recommend fastening the 7/8" plug connectors with a torque of 1.5Nm.
Fig.9: 7/8" plug connectors
Torque socket wrenches
Mounting and connection
Fig.10: ZB8801 torque socket wrench
Ensure the right torque
Use the torque socket wrenches available by Beckhoff to pull the connectors tight (ZB8800,
ZB8801-0000)!
EP3744-0041 and EP3744-104117Version: 2.2
Mounting and connection
3.2Connection
CAUTION
Druckluft
• Before connecting or disconnecting the module, check that the system is under pressure.
ð The compressed air connections must not be opened while the system is under pressure.
• The general safety and installation instructions for handling compressed air must be observed.
3.2.1EtherCAT connection
For the incoming and ongoing EtherCAT connection,
• the EtherCAT Box (EPxxxx) has two M8 sockets, marked in green
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
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-3xxxx-xxxx (with
M8 connectors)
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 connector
The following connectors can be supplied for use in Beckhoff EtherCAT systems.
NameConnectorComment
ZS1090-0003RJ45four-pole, IP20, field-configurable
ZS1090-0004M12, malefour-pin, IP67, for field assembly
ZS1090-0005RJ45eight-pole, IP20, field-configurable, suitable for gigabit Ethernet
ZS1090-0006M8 plug connectorfour-pole, IP67, field-configurable, for cable type ZB903x
ZS1090-0007M8 socketfour-pole, IP67, field-configurable, for cable type ZB903x
ZS1090-1006M8 plug connectorfour-pole, IP67, field-configurable up to OD=6.5mm
ZS1090-1007M8 socketfour-pole, IP67, field-configurable up to OD=6.5mm
EP3744-0041 and EP3744-104119Version: 2.2
Mounting and connection
3.2.2EtherCAT - Fieldbus LEDs
Fig.14: 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 Basic System Documentation for EtherCAT, which is available for download from our website (www.beck-hoff.com) under Downloads.
EP3744-0041 and EP3744-104120Version: 2.2
Mounting and connection
3.2.3Power 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.15: EtherCAT Box, Connectors for power supply
Fig.16: Pin assignment M8, Power In and Power Out
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.
NOTE
Don't confuse the power connectors with the EtherCAT connectors!
Never connect the power cables (M8, 24VDC) with the green marked EtherCAT sockets of the EtherCAT
Box Modules! This can damage the modules!
Control voltage Us: 24V
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.
DC
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.
EP3744-0041 and EP3744-104121Version: 2.2
Mounting and connection
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.
NOTE
Pay attention to the maximum permissible current!
Pay attention also for the redirection of the supply voltages Us and Up, the maximum permissible current
for M8 connectors of 4A must not be exceeded!
EP3744-0041 and EP3744-104122Version: 2.2
Mounting and connection
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.17: EP92x4-0023, Connectors for Power In and Power Out
Fig.18: Pin assignment 7/8”, Power In and Power Out
EP3744-0041 and EP3744-104123Version: 2.2
Mounting and connection
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.
NOTE
Electrical isolation may be cancelled!
If digital and analog fieldbus boxes are connected directly via four-core power leads, the analog signals in
the fieldbus boxes may be no longer electrically isolated from the control voltage!
3.2.4Status LEDs for power supply
Fig.19: 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
EP3744-0041 and EP3744-104124Version: 2.2
Mounting and connection
3.2.5Power cables
Ordering data
Order designation Power cableScrew-in connector Contacts Cross-section Length
ZK2020-3200-0020 Straight socket, open endM84-pin0.34 mm
ZK2020-3200-00505.00 m
ZK2020-3200-010010.00 m
ZK2020-3400-0020 Angled socket, open end2.00 m
ZK2020-3400-00505.00 m
ZK2020-3400-010010.00 m
ZK2020-3132-0001 Straight socket, straight
ZK2020-3132-00050.50 m
socket
ZK2020-3132-00101.00 m
ZK2020-3132-00202.00 m
ZK2020-3132-00505.00 m
ZK2020-3334-0001 Angled socket, angled
ZK2020-3334-00050.50 m
socket
ZK2020-3334-00101.00 m
ZK2020-3334-00202.00 m
ZK2020-3334-00505.00 m
2
2.00 m
0.15 m
0.15 m
Further available power cables may be found in the Beckhoff catalog or on our internet pages (http://www.beckhoff.com).
Technical data
Technical 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 according to IEC 60529IP65/66/67, when screwed together
Ambient temperature-30°C to +80°C
EP3744-0041 and EP3744-104125Version: 2.2
Mounting and connection
3.2.6Power 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.
Fig.20: 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 supply are
available. Further information may be found under www.beckhoff.com/EP9224.
EP3744-0041 and EP3744-104126Version: 2.2
3.2.7Signal connection
Mounting and connection
Fig.21: Signal connection
Digital inputs/outputs M8, 4-pin
The EP3744 has four 4-pin M8 sockets.
Sockets 0 and 1 each have two digital inputs; sockets 2 and 3 each have one input and one output.
The signals are connected via M8 connectors
Fig.22: Socket 0 and 1
EP3744-0041 and EP3744-104127Version: 2.2
Mounting and connection
Fig.23: Socket 2 and 3
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.
Pressure measuring inputs, 6mm pneumatic hose
The connection for pressure measurement is made via fittings for standard pneumatic hoses (6mm). The
values are output as a reference to the lower left measuring channel.
The values of the reference channel are not available in the process data, but in the CoE objects.
3.2.8Status LEDs at the signal connections
LED displays
LEDDisplayMeaning
STATUS
1-4
UsoffThe supply voltage, Us, is not present
UpoffThe supply voltage, Up, is not present
green
illuminated
green
illuminated
red illuminated short circuit on the power supply for sensor outputs of Us
green
illuminated
a signal (24V) is present on at least one input of channels 1-6 or one of the
outputs 1 or 2 is switched on
The supply voltage, Us, is present
The supply voltage, Up, is present
EP3744-0041 and EP3744-104128Version: 2.2
Mounting and connection
3.3UL Requirements
The installation of the EtherCAT Box Modules certified by UL has to meet the following requirements.
Supply voltage
CAUTION
CAUTION!
This UL requirements are valid for all supply voltages of all marked EtherCAT Box Modules!
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
CAUTION!
To meet the UL requirements, the EtherCAT Box Modules must not be connected to unlimited power
sources!
Networks
CAUTION
CAUTION!
To meet the UL requirements, EtherCAT Box Modules must not be connected to telecommunication networks!
Ambient temperature range
CAUTION
CAUTION!
To meet the UL requirements, EtherCAT Box Modules has to be operated only at an ambient temperature
range of 0 to 55°C!
Marking for UL
All EtherCAT Box Modules certified by UL (Underwriters Laboratories) are marked with the following label.
Fig.24: UL label
EP3744-0041 and EP3744-104129Version: 2.2
Commissioning/Configuration
4Commissioning/Configuration
4.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 can be
downloaded from the Beckhoff website (http://www.beckhoff.de/english/download/elconfg.htm?id=1983920606140) and installed according to the installation instructions.
At the Beckhoff TwinCAT System Manager the configuration tree can be build in two different ways:
• by scanning [}30] for existing hardware (called "online") and
• by manual inserting/appending [}30] 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 [}33] (Config mode), and scan
in the devices (see Fig. 1). Acknowledge all dialogs with "OK", so that the configuration is in "FreeRun"
mode.
Fig.25: 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 [}33] (Config mode)
• Append a new I/O device. In the dialog that appears select the device EtherCAT (Direct Mode), and
confirm with OK.
EP3744-0041 and EP3744-104130Version: 2.2
Commissioning/Configuration
Fig.26: Appending a new I/O device (I/O Devices -> right-click -> Append Device...)
Fig.27: Selecting the device EtherCAT
• Append a new box.
Fig.28: 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.
EP3744-0041 and EP3744-104131Version: 2.2
Commissioning/Configuration
Fig.29: Selecting a Box (e.g. EP2816-0008)
Fig.30: Appended Box in the TwinCAT tree
EP3744-0041 and EP3744-104132Version: 2.2
Commissioning/Configuration
4.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.31: 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.32: 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.
EP3744-0041 and EP3744-104133Version: 2.2
Commissioning/Configuration
EtherCAT tab
Fig.33: 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.
EP3744-0041 and EP3744-104134Version: 2.2
Commissioning/Configuration
Fig.34: 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.
EP3744-0041 and EP3744-104135Version: 2.2
Commissioning/Configuration
Activation of PDO assignment
• the EtherCAT slave has to run through the PS status transition cycle (from pre-operational to
safe-operational) once (see Online tab [}39]),
• and the System Manager has to reload the EtherCAT slaves ( button)
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.
Column Description
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
Manager.
M Mandatory PDO. This PDO is mandatory and must therefore be assigned to a Sync Manager!
Consequently, this PDO cannot be deleted from the PDO Assignment list
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.
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 [}36] 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.
EP3744-0041 and EP3744-104136Version: 2.2
Fig.35: 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
Commissioning/Configuration
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.
EP3744-0041 and EP3744-104137Version: 2.2
Commissioning/Configuration
Fig.36: 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.
EP3744-0041 and EP3744-104138Version: 2.2
Commissioning/Configuration
Fig.37: 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.38: Online tab
EP3744-0041 and EP3744-104139Version: 2.2
Commissioning/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.
EP3744-0041 and EP3744-104140Version: 2.2
Commissioning/Configuration
4.3Object overview
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.
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.
Parameterization via the CoE list (CAN over EtherCAT)
The EtherCAT device is parameterized via the CoE - Online tab [}37] (double-click on the respective object) or via the Process Data [}34] tab (allocation of PDOs).
Introduction
The CoE overview contains objects for different intended applications:
• Objects required for parameterization [}47] during commissioning
• Objects for indicating internal settings [}51] (may be fixed)
• Further profile-specific objects [}58] 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.
4.4.1Objects to be parameterized during commissioning
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-
Index 8010 Safe state active
Index (hex) NameMeaningData typeFlagsDefault
8010:0Safe state activeUINT8RO0x02 (2
8010:01Output 10Output State will remain unchanged during OP->
8010:02Output 20Output State will remain unchanged during OP->
Restore default parametersUINT8RO0x01 (1
log, all backup objects are reset to their delivery state.
SafeOP
1Output will go to Safe State during OP-> SafeOP
SafeOP
1Output will go to Safe State during OP-> SafeOP
UINT32RW0x00000000
BOOLEANRW0x00 (0
BOOLEANRW0x00 (0
(0
)
dec
)
dec
)
dec
)
dec
)
dec
Index 8011 Safe state value
Index (hex) NameMeaningData typeFlagsDefault
8011:0Safe state valueUINT8RO0x02 (2
8011:01Output 10Output -> 0 in case of Safe State conditionBOOLEANRW0x00 (0
1Output -> 1 in case of Safe State condition
8011:02Output 20Output -> 0 in case of Safe State conditionBOOLEANRW0x00 (0
1Output -> 1 in case of Safe State condition
EP3744-0041 and EP3744-104147Version: 2.2
)
dec
)
dec
)
dec
Commissioning/Configuration
Index 8020 AI settings Ch.1 (parameterization of channel 1)
6050:05Limit 2Bit0: Value greater than Limit2 Bit1: Value smaller than
BIT2RO0x00 (0
Limit2
6050:07ErrorBit set when Over- or UnderrangeBOOLEANRO0x00 (0
6050:0FTxPDO StateBOOLEANRO0x00 (0
6050:10TxPDO ToggleBOOLEANRO0x00 (0
dec
dec
dec
dec
dec
dec
dec
dec
6050:11ValueINT32RO0x00000000
(0
)
dec
Index 6000 Dig Inputs
Index (hex) NameMeaningData typeFlagsDefault
6000:0Dig InputsUINT8RO0x06 (6
6000:01Input 1BOOLEANRO0x00 (0
6000:02Input 2BOOLEANRO0x00 (0
6000:03Input 3BOOLEANRO0x00 (0
6000:04Input 4BOOLEANRO0x00 (0
6000:05Input 5BOOLEANRO0x00 (0
6000:06Input 6BOOLEANRO0x00 (0
dec
dec
dec
dec
dec
dec
dec
)
)
)
)
)
)
)
)
)
)
)
)
)
)
)
Index 7010 Dig Outputs
Index (hex) NameMeaningData typeFlagsDefault
7010:0Dig OutputsUINT8RO0x02 (2
7010:01Output 1BOOLEANRO0x00 (0
7010:02Output 2BOOLEANRO0x00 (0
dec
dec
dec
Index 802E AI Internal data Ch.1
Index (hex) NameMeaningData typeFlagsDefault
802E:0AI Internal data Ch.1UINT8RO0x01 (1
dec
802E:01ADC raw valueINT32RO0x00000000
(0
)
dec
Index 802F AI Vendor data Ch.1
Index (hex) NameMeaningData typeFlagsDefault
802F:0AI Vendor data Ch.1UINT8RO0x04 (4
802F:01Calibration offset
INT32RW0x00000000
pressure
802F:02Calibration gain pres-
INT16RW0x4000
sure
802F:03Calibration offset
INT32RW0x00000000
temp
802F:04Calibration gain tempINT16RW0x0000 (0
(0
)
dec
(16384
(0
)
dec
dec
)
dec
)
)
)
)
)
)
dec
Index 803E AI Internal data Ch.2
Index (hex) NameMeaningData typeFlagsDefault
803E:0AI Internal data Ch.2UINT8RO0x01 (1
dec
803E:01ADC raw valueINT32RO0x00000000
(0
)
dec
EP3744-0041 and EP3744-104159Version: 2.2
)
Commissioning/Configuration
Index 803F AI Vendor data Ch.2
Index (hex) NameMeaningData typeFlagsDefault
803F:0AI Vendor data Ch.2UINT8RO0x04 (4
803F:01Calibration offset
INT32RW0x00000000
pressure
803F:02Calibration gain pres-
INT16RW0x4000
sure
803F:03Calibration offset
INT32RW0x00000000
temp
(0
)
dec
(16384
(0
)
dec
dec
)
dec
803F:04Calibration gain tempINT16RW0x0000 (0
Index 804E AI Internal data Ch.3
Index (hex) NameMeaningData typeFlagsDefault
804E:0AI Internal data Ch.3UINT8RO0x01 (1
dec
804E:01ADC raw valueINT32RO0x00000000
(0
)
dec
Index 804F AI Vendor data Ch.3
Index (hex) NameMeaningData typeFlagsDefault
804F:0AI Vendor data Ch.3UINT8RO0x04 (4
804F:01Calibration offset
INT32RW0x00000000
pressure
804F:02Calibration gain pres-
INT16RW0x4000
sure
804F:03Calibration offset
INT32RW0x00000000
temp
804F:04Calibration gain tempINT16RW0x0000 (0
(0
)
dec
(16384
(0
)
dec
dec
)
dec
)
)
dec
)
)
)
dec
Index 805E AI Internal data Ch.4
Index (hex) NameMeaningData typeFlagsDefault
805E:0AI Internal data Ch.4UINT8RO0x01 (1
dec
805E:01ADC raw valueINT32RO0x00000000
(0
)
dec
Index 805F AI Vendor data Ch.4
Index (hex) NameMeaningData typeFlagsDefault
805F:0AI Vendor data Ch.4UINT8RO0x04 (4
805F:01Calibration offset
INT32RW0x00000000
pressure
805F:02Calibration gain pres-
INT16RW0x4000
sure
805F:03Calibration offset
INT32RW0x00000000
temp
(0
)
dec
(16384
(0
)
dec
dec
)
dec
805F:04Calibration gain tempINT16RW0x0000 (0
Index F000 Modular device profile
Index (hex) NameMeaningData typeFlagsDefault
F000:0Modular device profile general information about the Modular Device ProfileUINT8RO0x02 (2
F000:01Module index dis-
Index distance between the objects of two channelsUINT16RO0x0010 (16
tance
F000:02Maximum number of
number of channelsUINT16RO0x0006 (6
modules
dec
)
)
)
dec
)
)
dec
)
dec
Index F008 Code word
Index (hex) NameMeaningData typeFlagsDefault
F008:0Code wordUINT32RW0x00000000
(0
)
dec
EP3744-0041 and EP3744-104160Version: 2.2
Commissioning/Configuration
Index F010 Module list
Index (hex) NameMeaningData typeFlagsDefault
F010:0Module listUINT8RW0x06 (6
)
dec
F010:01SubIndex 001UINT32RW0x00000118
(280
)
dec
F010:02SubIndex 002UINT32RW0x00000118
(280
)
dec
F010:03SubIndex 003UINT32RW0x0000012C
(300
)
dec
F010:04SubIndex 004UINT32RW0x0000012C
(300
)
dec
F010:05SubIndex 005UINT32RW0x0000012C
(300
)
dec
F010:06SubIndex 006UINT32RW0x0000012C
(300
)
dec
Index F600 DEV Inputs Safe State Active
Index (hex) NameMeaningData typeFlagsDefault
F600:0DEV Inputs Safe
State Active
F600:01Safe State Active1: Outputs are in Safe State 0: Outputs are in Normal
State
UINT8RO0x01 (1
BOOLEANRO0x00 (0
)
dec
)
dec
Index F611 DEV Inputs Undervoltage
Index (hex) NameMeaningData typeFlagsDefault
F611:0DEV Inputs Under-
voltage
F611:01Undervoltage UsUs ≤ 18VBOOLEANRO0x00 (0
F611:02Undervoltage UpUp ≤ 18VBOOLEANRO0x00 (0
F611:10TxPDO ToggleBOOLEANRO0x00 (0
UINT8RO0x10 (16
dec
dec
dec
dec
Index F700 DEV Outputs Set Safe State
Index (hex) NameMeaningData typeFlagsDefault
F700:0DEV Outputs Set
Safe State
F700:01Set safe stateSet Device to Safe StateBOOLEANRO0x00 (0
UINT8RO0x01 (1
dec
dec
Index F800 AI Settings Reference
Index (hex) NameMeaningData typeFlagsDefault
F800:0AI Settings ReferenceUINT8RO0x18 (24
F800:0AEnable user calibra-
BOOLEANRW0x00 (0
tion
F800:0BEnable vendor cali-
BOOLEANRW0x01 (1
bration
F800:17User calibration offsetINT32RW0x00000000
(0
F800:18User calibration gainINT16RW0x4000
(16384
dec
dec
dec
)
dec
)
dec
)
)
)
)
)
)
)
)
)
Index F80E AI Internal data Reference
Index (hex) NameMeaningData typeFlagsDefault
F80E:0AI Internal data Refer-
ence
UINT8RO0x02 (2
dec
F80E:01ADC raw value 1Pressure ValueINT32RO0x00000000
(0
)
dec
F80E:02ADC raw value 2Pressure ValueINT32RO0x00000000
(0
)
dec
EP3744-0041 and EP3744-104161Version: 2.2
)
Commissioning/Configuration
Index F80F AI Vendor data Reference
Index (hex) NameMeaningData typeFlagsDefault
F80F:0AI Vendor data Refer-
ence
F80F:01Calibration offset
pressure
F80F:02Calibration gain pres-
sure
F80F:03Calibration offset
temp
F80F:04Calibration gain tempINT16RW0x0000 (0
UINT8RO0x04 (4
INT32RW0x00000000
(0
INT16RW0x4000
(16384
INT32RW0x00000000
(0
)
dec
)
dec
)
dec
)
dec
dec
)
4.5Settings
FIR and IIR filter
The EP3744 Box is equipped with a digital filter which, depending on its settings, can adopt the
characteristics of a Finite Impulse Response filter (FIR filter), or an Infinite Impulse Response filter (IIR filter).
The filter can also be deactivated.
The filter characteristics are set via index 0x8020:15
The filter frequencies are set centrally for all channels of the EP3744 Box via index 0x8020:15
(channel1). The corresponding indices 0x80n0:15 [}48] of the other channels have no parameteri-
zation function.
FIR filter
The filter works as a notch filter and determines the conversion time of the box. It is parameterized via the
index 0x8020:15 [}48]. The higher the filter frequency, the faster the conversion time. A 50Hz and a 60Hz
filter are available.
Notch filter means that the filter has zeros (notches) in the frequency response at the filter frequency and
multiples thereof, i.e. it attenuates the amplitude at these frequencies.
The FIR filter functions as a non-recursive filter, which can be adjusted by the parameterization of the object
0x8020:15 [}48].
Fig.39: Typical attenuation curve of notch filter at 50Hz
EP3744-0041 and EP3744-104162Version: 2.2
Commissioning/Configuration
Filter data FIR filter (1-4-channel boxes)
FilterAttenuationLimit frequency (-3dB)
50HzFIR>50dB22Hz
60HzFIR>40dB26Hz
Filter data FIR filter (8-channel boxes)
FilterAttenuationLimit frequency (-3dB)
50HzFIR>50dB23Hz
60HzFIR>50dB27Hz
IIR filter
The filter with IIR characteristics is a discrete time, linear, time invariant filter that can be set to eight levels
(level 1 = weak recursive filter, up to level 8 = strong recursive filter).
The IIR can be understood to be a moving average value calculation after a low-pass filter.
By means of the synchronization mode FreeRun, the IIR filter works with an internal cycle time of 500µs (1,
2 or 4 channels) or 1ms (8 channels).
Filter data for IIR filter
IIR filterLimit frequency with internal box cycle time 1ms (-3dB)
Conversion time & FIR and IIR filters, index 0x80n0:06 [}48]
The typical conversion time and trigger mode depend on
• the selected filter setting (default: 50Hz)
• the setting in the CoE register 0x1C33:01 [}57]
◦ by manual parameterization in the System Manager. CAUTION: Enter any changes made in the
StartUp list!
◦ by the StartUp list as an automatic parameter download during the EtherCAT start phase.
CAUTION: Entries are implemented only after activation of the configuration!
The conversion time is the time interval in which the EP3744 makes a new measured value available. A new
measured value is displayed by toggling “TxPDO Toggle” (index 0x60n0:10 [}58]).
Limit 1 and Limit 2, Index 0x80n0:13 [}48], Index 0x80n0:14 [}48]
If the limits of the values that can be entered in indices 0x80n0:13 [}48] and 0x80n0:14 [}48] are violated,
the bits in indices 0x60n0:03 [}59] and 0x60n0:05 [}59] are set accordingly (see sample below). The indices
0x80n0:07 [}48] or 0x80n0:08 [}48] serve to activate the limit value monitoring.
Output limit n (2-bit):
• 0: not active
EP3744-0041 and EP3744-104163Version: 2.2
Commissioning/Configuration
• 1: Value is smaller than the limit value
• 2: Value is larger than the limit value
• 3: Value is equal to the limit value
Linking in the PLC with 2-bit values
The limit information consists of 2bits. Limitn can be linked to the PLC or a task in the System Manager.
• PLC:
IEC61131-PLC contains no 2-bit data type that can be linked with this process data directly. To transfer the limit information, you
should therefore define an input byte, for example, and link the limit to the VariableSizeMismatch dialog, as described in the
diagram Linking 2-bit variable with additional task.
Fig.40: Input byte definition
• Additional task
2-bit variables can be created in the System Manager.
Fig.41: Linking of 2-bit variable to additional task
Sample for EL3062:
Channel 1;Limit1 and Limit2 enabled, Limit 1 = 2.8V, Limit 2 = 7.4V, representation: signed integer
Entry in Index 0x80n0:13 [}48](Limit 1):
(2.8V/10V) x 216 / 2 - 1 = 9,174
dec
Entry in Index 0x80n0:14 [}48] (Limit 2):
(7.4V/10V) x 216 / 2 - 1 = 24,247
dec
Output:
Input channel 1
1.8V0x01
2.8V0x03
4.2V0x02
8.5V0x02
Index 0x6000:03 [}59]Index 0x6000:05 [}59]
, (Limit1, limit value undershot)0x01
hex
, (Limit1, limit value reached)0x01
hex
, (Limit1, limit value exceeded)0x01
hex
, (Limit1, limit value exceeded)0x02
hex
, (Limit2, limit value undershot)
hex
, (Limit2, limit value undershot)
hex
, (Limit2, limit value undershot)
hex
, (Limit2, limit value exceeded)
hex
EP3744-0041 and EP3744-104164Version: 2.2
Commissioning/Configuration
4.6Restoring the delivery state
To restore the delivery state for backup objects in ELxxxx terminals / EPxxxx- and EPPxxxx boxes, the CoE
object Restore default parameters, SubIndex 001 can be selected in the TwinCAT System Manager (Config
mode).
Fig.42: Selecting the Restore default parameters PDO
Double-click on SubIndex 001 to enter the Set Value dialog. Enter the value 1684107116 in field Dec or the
value 0x64616F6C in field Hex and confirm with OK.
All backup objects are reset to the delivery state.
Fig.43: Entering a restore value in the Set Value dialog
Alternative restore value
In some older terminals / boxes the backup objects can be switched with an alternative restore
value:
Decimal value: 1819238756
Hexadecimal value: 0x6C6F6164
An incorrect entry for the restore value has no effect.
EP3744-0041 and EP3744-104165Version: 2.2
Commissioning/Configuration
4.7Firmware Update EL/ES/EM/EPxxxx
This section describes the device update for Beckhoff EtherCAT slaves from the EL/ES, EM, EK and EP
series. A firmware update should only be carried out after consultation with Beckhoff support.
Storage locations
An EtherCAT slave stores operating data in up to 3 locations:
• Depending on functionality and performance EtherCAT slaves have one or several local controllers for
processing I/O data. The corresponding program is the so-called firmware in *.efw format.
• In some EtherCAT slaves the EtherCAT communication may also be integrated in these controllers. In
this case the controller is usually a so-called FPGA chip with *.rbf firmware.
• In addition, each EtherCAT slave has a memory chip, a so-called ESI-EEPROM, for storing its own
device description (ESI: EtherCAT Slave Information). On power-up this description is loaded and the
EtherCAT communication is set up accordingly. The device description is available from the download
area of the Beckhoff website at (http://www.beckhoff.de). All ESI files are accessible there as zip files.
Customers can access the data via the EtherCAT fieldbus and its communication mechanisms. Acyclic
mailbox communication or register access to the ESC is used for updating or reading of these data.
The TwinCAT System Manager offers mechanisms for programming all 3 parts with new data, if the slave is
set up for this purpose. Generally the slave does not check whether the new data are suitable, i.e. it may no
longer be able to operate if the data are unsuitable.
NOTE
Risk of damage to the device!
Note the following when downloading new device files
• Firmware downloads to an EtherCAT device must not be interrupted
• Flawless EtherCAT communication must be ensured. CRC errors or LostFrames must be avoided.
• The power supply must adequately dimensioned. The signal level must meet the specification.
In the event of malfunctions during the update process the EtherCAT device may become unusable and require re-commissioning by the manufacturer.
Device description ESI file/XML
NOTE
Notice regarding update of the ESI description/EEPROM
Some slaves have stored calibration and configuration data from the production in the EEPROM. These are
irretrievably overwritten during an update.
The ESI device description is stored locally on the slave and loaded on start-up. Each device description has
a unique identifier consisting of slave name (9 characters/digits) and a revision number (4 digits). Each slave
configured in the System Manager shows its identifier in the EtherCAT tab:
EP3744-0041 and EP3744-104166Version: 2.2
Commissioning/Configuration
Fig.44: Device identifier consisting of name EL3204-0000 and revision -0016
The configured identifier must be compatible with the actual device description used as hardware, i.e. the
description which the slave has loaded on start-up (in this case EL3204). Normally the configured revision
must be the same or lower than that actually present in the terminal network.
For further information on this, please refer to the EtherCAT system documentation.
Update of XML/ESI description
The device revision is closely linked to the firmware and hardware used. Incompatible combinations
lead to malfunctions or even final shutdown of the device. Corresponding updates should only be
carried out in consultation with Beckhoff support.
Display of ESI slave identifier
The simplest way to ascertain compliance of configured and actual device description is to scan the
EtherCAT boxes in TwinCAT mode Config/FreeRun:
Fig.45: Scan Boxes
Scan the subordinate field by right-clicking on the EtherCAT device in Config/FreeRun mode
If the found field matches the configured field, the display shows
EP3744-0041 and EP3744-104167Version: 2.2
Commissioning/Configuration
Fig.46: Configuration is identical
otherwise a change dialog appears for entering the actual data in the configuration.
Fig.47: Change dialog
In this example in Fig. Change dialog, an EL3201-0000-0017 was found, while an EL3201-0000-0016 was
configured. In this case the configuration can be adapted with the Copy Before button. The ExtendedInformation checkbox must be set in order to display the revision.
Changing the ESI slave identifier
The ESI/EEPROM identifier can be updated as follows under TwinCAT:
• Trouble-free EtherCAT communication must be established with the slave.
• The state of the slave is irrelevant.
• Right-clicking on the slave in the online display opens the EEPROM Update dialog, Fig. EEPROM
Update
EP3744-0041 and EP3744-104168Version: 2.2
Commissioning/Configuration
Fig.48: EEPROM Update
The new ESI description is selected in the following dialog, see Fig. Selecting the new ESI. The checkbox
Show Hidden Devices also displays older, normally hidden versions of a slave.
Fig.49: Selecting the new ESI
A progress bar in the System Manager shows the progress. Data are first written, then verified.
The change only takes effect after a restart.
Most EtherCAT devices read a modified ESI description immediately or after startup from the INIT.
Some communication settings such as distributed clocks are only read during power-on. The EtherCAT slave therefore has to be switched off briefly in order for the change to take effect.
Determining the firmware version
Determining the version on laser inscription
Beckhoff EtherCAT Box feature batch numbers (D number) applied by laser. The D-number has the
following structure: KK YY FF HH
KK - week of production (CW, calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Example with D-no.: 12 10 03 02:
EP3744-0041 and EP3744-104169Version: 2.2
Commissioning/Configuration
12 - week of production 12
10 - year of production 2010
03 - firmware version 03
02 - hardware version 02
Determining the version via the System Manager
The TwinCAT System Manager shows the version of the controller firmware if the master can access the
slave online. Click on the E-Bus Terminal whose controller firmware you want to check (in the example
terminal 2 (EL3204)) and select the tab CoE Online (CAN over EtherCAT).
CoE Online and Offline CoE
Two CoE directories are available:
• online: This is offered in the EtherCAT slave by the controller, if the EtherCAT slave does supported it. This CoE directory can only be displayed if a slave is connected and operational.
• offline: The EtherCAT Slave Information ESI/XML may contain the default content of the CoE.
This CoE directory can only be displayed if it is included in the ESI (e.g. Beckhoff EL5xxx.xml).
The Advanced button must be used for switching between the two views.
In Fig. Display of EL3204 firmware version the firmware version of the selected EL3204 is shown as 03 in
CoE entry 0x100A.
Fig.50: Display of EL3204 firmware version
In (A) TwinCAT 2.11 shows that the Online CoE directory is currently displayed. If this is not the case, the
Online directory can be loaded via the Online option in Advanced Settings (B) and double-clicking on
AllObjects.
Updating controller firmware *.efw
CoE directory
The Online CoE directory is managed by the controller and stored in a dedicated EEPROM, which
is generally not changed during a firmware update.
Switch to the Online tab to update the controller firmware of a slave, see Fig. Firmware Update.
EP3744-0041 and EP3744-104170Version: 2.2
Commissioning/Configuration
Fig.51: Firmware Update
Proceed as follows, unless instructed otherwise by Beckhoff support.
• Switch slave to INIT (A)
• Switch slave to BOOTSTRAP
• Check the current status (B, C)
• Download the new *efw file
• After the download switch to INIT, then OP
• Switch off the slave briefly
FPGA firmware *.rbf
If an FPGA chip deals with the EtherCAT communication an update may be accomplished via an *.rbf file.
• Controller firmware for processing I/O signals
• FPGA firmware for EtherCAT communication (only for terminals with FPGA)
The firmware version number included in the terminal serial number contains both firmware components. If
one of these firmware components is modified this version number is updated.
Determining the version via the System Manager
The TwinCAT System Manager indicates the FPGA firmware version. Click on the Ethernet card of your
EtherCAT strand (Device 2 in the example) and select the Online tab.
The Reg:0002 column indicates the firmware version of the individual EtherCAT devices in hexadecimal and
decimal representation.
EP3744-0041 and EP3744-104171Version: 2.2
Commissioning/Configuration
Fig.52: FPGA firmware version definition
If the column Reg:0002 is not displayed, right-click the table header and select Properties in the context
menu.
Fig.53: Context menu Properties
The Advanced Settings dialog appears where the columns to be displayed can be selected. Under
Diagnosis/Online View select the '0002 ETxxxx Build' check box in order to activate the FPGA firmware
version display.
EP3744-0041 and EP3744-104172Version: 2.2
Commissioning/Configuration
Fig.54: Dialog Advanced Settings
Update
For updating the FPGA firmware
• of an EtherCAT coupler the coupler must have FPGA firmware version 11 or higher;
• of an E-Bus Terminal the terminal must have FPGA firmware version 10 or higher.
Older firmware versions can only be updated by the manufacturer!
Updating an EtherCAT device
In the TwinCAT System Manager select the terminal for which the FPGA firmware is to be updated (in the
example: Terminal 5: EL5001) and click the Advanced Settings button in the EtherCAT tab.
EP3744-0041 and EP3744-104173Version: 2.2
Commissioning/Configuration
Fig.55: Select dialog Advanced Settings
The Advanced Settings dialog appears. Under ESC Access/E²PROM/FPGA click on Write FPGA button,
Fig.56: Select dialog Write FPGA
EP3744-0041 and EP3744-104174Version: 2.2
Commissioning/Configuration
Fig.57: Select file
Select the file (*.rbf) with the new FPGA firmware, and transfer it to the EtherCAT device.
NOTE
Risk of damage to the device!
A firmware download to an EtherCAT device must never be interrupted! If this process is cancelled, the
supply voltage switched off or the Ethernet connection interrupted, the EtherCAT device can only be recommissioned by the manufacturer!
In order to activate the new FPGA firmware a restart (switching the power supply off and on again) of the
EtherCAT device is required.
Simultaneous updating of several EtherCAT devices
The firmware and ESI descriptions of several devices can be updated simultaneously, provided the devices
have the same firmware file/ESI.
Fig.58: Multiple selection and firmware update
Select the required slaves and carry out the firmware update in BOOTSTRAP mode as described above.
EP3744-0041 and EP3744-104175Version: 2.2
Appendix
5Appendix
5.1General operating conditions
Protection degrees (IP-Code)
The standard IEC 60529 (DIN EN 60529) defines the degrees of protection in different classes.
1. Number: dust protection and
touch guard
0Non-protected
1Protected against access to hazardous parts with the back of a hand. Protected against solid
2Protected against access to hazardous parts with a finger. Protected against solid foreign ob-
3Protected against access to hazardous parts with a tool. Protected against solid foreign objects
4Protected against access to hazardous parts with a wire. Protected against solid foreign objects
5Protected against access to hazardous parts with a wire. Dust-protected. Intrusion of dust is not
6Protected against access to hazardous parts with a wire. Dust-tight. No intrusion of dust.
Definition
foreign objects of Ø50mm
jects of Ø12.5mm.
Ø2.5mm.
Ø1mm.
totally prevented, but dust shall not penetrate in a quantity to interfere with satisfactory operation
of the device or to impair safety.
2. Number: water* protectionDefinition
0Non-protected
1Protected against water drops
2Protected against water drops when enclosure tilted up to 15°.
3Protected against spraying water. Water sprayed at an angle up to 60° on either side of the ver-
4Protected against splashing water. Water splashed against the disclosure from any direction
5Protected against water jets
6Protected against powerful water jets
7Protected against the effects of temporary immersion in water. Intrusion of water in quantities
tical shall have no harmful effects.
shall have no harmful effects
causing harmful effects shall not be possible when the enclosure is temporarily immersed in water for 30min. in 1m depth.
*) These protection classes define only protection against water!
Chemical Resistance
The Resistance relates to the Housing of the Fieldbus/EtherCAT Box and the used metal parts. In the table
below you will find some typical resistance.
CharacterResistance
Steamat temperatures >100°C: not resistant
Sodium base liquor
(ph-Value > 12)
Acetic acidnot resistant
Argon (technical clean)resistant
at room temperature: resistant
> 40°C: not resistant
Key
• resistant: Lifetime several months
• non inherently resistant: Lifetime several weeks
• not resistant: Lifetime several hours resp. early decomposition
EP3744-0041 and EP3744-104176Version: 2.2
5.2EtherCAT Box- / EtherCATPBox - Accessories
Fixing
Ordering informationDescription
ZS5300-0001Mounting rail (500mmx129mm)
Marking material, plugs
Ordering informationDescription
ZS5000-0000Fieldbus Box set M8 (contact labels, plugs)
ZS5000-0002Fieldbus Box set M12 (contact labels, plugs)
ZS5000-0010plugs M8, IP67 (50 pieces)
ZS5000-0020plugs M12, IP67 (50 pieces)
ZS5100-0000marking labels, not printed, 4 stripes at 10 pieces
ZS5100-xxxxprinted marking labels, on request
Tools
Ordering informationDescription
ZB8800torque wrench for M8 cables with knurl, incl. ratchet
ZB8800-0001M12 ratchet for torque wrench ZB8800
ZB8800-0002M8 ratchet (field assembly) for torque wrench ZB8800
ZB8801-0000torque wrench for hexagonal plugs, adjustable
ZB8801-0001torque cable key, M8/wrench size 9, for torque wrench ZB8801-0000
ZB8801-0002torque cable key, M12/wrench size 13, for torque wrench ZB8801-0000
ZB8801-0003torque cable key, M12 field assembly/wrench size 13, for torque wrench
ZB8801-0000
Appendix
Further accessories
Further accessories may be found at the price list for Beckhoff fieldbus components and at the internet under https://www.beckhoff.com
EP3744-0041 and EP3744-104177Version: 2.2
Appendix
5.3Support and Service
Beckhoff and their partners around the world offer comprehensive support and service, making available fast
and competent assistance with all questions related to Beckhoff products and system solutions.
Beckhoff's branch offices and representatives
Please contact your Beckhoff branch office or representative for local support and service on Beckhoff
products!
The addresses of Beckhoff's branch offices and representatives round the world can be found on her internet
pages:
http://www.beckhoff.com
You will also find further documentation for Beckhoff components there.
Support offers you comprehensive technical assistance, helping you not only with the application of
individual Beckhoff products, but also with other, wide-ranging services:
• support
• design, programming and commissioning of complex automation systems
• and extensive training program for Beckhoff system components