6.4Support and Service ........................................................................................................................35
EPP1111-00003Version: 1.2
Table of contents
EPP1111-00004Version: 1.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®, 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.
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.
EPP1111-00006Version: 1.2
Foreword
1.3Documentation Issue Status
VersionComment
1.2• Front page updated
• Structure update
1.1• Chapter “Process image” updated
• Chapter "Commissioning" extended
1.0First release
0.1Preliminary version
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.
DocumentationFirmwareHardware
1.20500
1.10500
1.00500
0.10500
The firmware and hardware version (delivery state) can be found in the batch number (D-number) printed on
the side of the EtherCAT Box.
Syntax of the batch number (D-number)
D: WW YY FF HH
WW - week of production (calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Further information on this topic: Version identification of EtherCAT devices [}29].
Example with D no. 29 10 02 01:
29 - week of production 29
10 - year of production 2010
02 - firmware version 02
01 - hardware version 01
EPP1111-00007Version: 1.2
Product group: EtherCATP Box modules
2Product group: EtherCATP Box modules
EtherCATP
EtherCATP supplements the EtherCAT technology with a process in which communication and supply
voltages are transmitted on a common line. All EtherCAT properties are retained with this process.
Two supply voltages are transmitted per EtherCATP line. The supply voltages are electrically isolated from
each other and can therefore be switched individually. The nominal supply voltage for both is 24 VDC.
EtherCAT P uses the same cable structure as EtherCAT: a 4-core Ethernet cable with M8 connectors. The
connectors are mechanically coded so that EtherCAT connectors and EtherCATP connectors cannot be
interchanged.
EtherCATP Box modules
EtherCATP Box modules are EtherCATP slaves with IP67 protection. They are designed for operation in
wet, dirty or dusty industrial environments.
Fig.1: EtherCATP
EtherCAT basics
A detailed description of the EtherCAT system can be found in the EtherCAT system documentation.
EPP1111-00008Version: 1.2
3Product overview
3.1Introduction
Product overview
Fig.2: EPP1111-0000
EPP1111-0000 | EtherCAT P Box with ID switch
The EPP1111 EtherCAT P Box has three decimal ID switches for assigning an ID to a group of EtherCAT
components. This group can be present in any position in the EtherCAT P network, as a result of which
variable topologies and Hot Connect groups can be realised in a simple manner.
The EtherCAT P connection is established via shielded EtherCAT-P-coded M8 screw type sockets with
direct display of link and activity status. The Run LED indicates the status of the EPP1111.
EPP1111-00009Version: 1.2
Product overview
3.2Technical data
All values are typical values over the entire temperature range, unless stated otherwise.
Technical dataEPP1111-0000
Fieldbus
FieldbusEtherCAT
ConnectionEtherCAT P: Combined connection for EtherCAT and supply
voltages
Input: 1 x M8 socket, 4-pin, P-coded
Downstream connection: 1 x M8 socket, 4-pin, P-coded
Supply voltages
ConnectionSee Fieldbus connection
Control voltage U
Nominal voltage24VDC (-15%/ +20%)
Sum currentmax. 3A
ConsumersModule electronics: 100mA
Peripheral voltage U
Nominal voltage24VDC (-15%/ +20%)
Sum currentmax. 3A
ConsumersNone. UP is only forwarded.
Make sure that the following components are included in the scope of delivery:
• 1x EtherCAT P Box EPP1111-0000
• 2x protective cap for EtherCATP socket, M8, red (pre-assembled)
• 10x labels, blank (1 strip of 10)
Pre-assembled protective caps do not ensure IP67 protection
Protective caps are pre-assembled at the factory to protect connectors during transport. They may
not be tight enough to ensure IP67 protection.
Ensure that the protective caps are correctly seated to ensure IP67 protection.
Product overview
EPP1111-000011Version: 1.2
Product overview
3.4Process image
Fig.3: Process image in TwinCAT
ID inputs
ID
Data type: UINT
The input variable ID contains the value that is set by
the ID switches.
EPP1111-000012Version: 1.2
4Mounting and connection
119
126
23
3026.5
13.5
Ø 3.5
4.1Mounting
4.1.1Dimensions
Mounting and connection
Fig.4: Dimensions
All dimensions are given in millimeters.
Housing features
Housing materialPA6 (polyamide)
Sealing compoundpolyurethane
Mountingtwo fastening holes Ø 3.5 mm for M3
Metal partsbrass, nickel-plated
ContactsCuZn, gold-plated
Installation positionvariable
Protection classIP65, IP66, IP67 (conforms to EN 60529) when screwed together
Dimensions (H x W x D)approx. 126 x 30 x 26.5 mm (without connectors)
Weightapprox. 165g
EPP1111-000013Version: 1.2
Mounting and connection
FE
4.1.2Fixing
NOTE
Dirt during assembly
Dirty connectors can lead to malfunctions. Protection class IP67 can only be guaranteed if all cables and
connectors are connected.
• Protect the plug connectors against dirt during the assembly.
Mount the module with two M3 screws on the fastening holes in the corners of the module. The fastening
holes have no thread.
4.1.3Functional earth (FE)
The upper fastening hole also serves as a connection for functional earth (FE).
Make sure that the box is grounded to low impedance via the functional earth (FE) connection. You can
achieve this, for example, by mounting the box on a grounded machine bed.
Fig.5: Connection for functional earth (FE)
4.1.4Tightening torques for plug connectors
Screw M8 connectors tight with a torque wrench. (e.g. ZB8801 from Beckhoff)
Torque: 0.4Nm.
EPP1111-000014Version: 1.2
Mounting and connection
12
1
2
3
4
4.2EtherCATP
NOTE
Risk of damage to the device!
Bring the EtherCAT/EtherCATP system into a safe, powered down state before starting installation, disassembly or wiring of the modules!
NOTE
Pay attention to the maximum permissible current!
Pay attention also for the redirection of EtherCATP, the maximum permissible current for M8 connectors of
3A must not be exceeded!
4.2.1Connectors
Fig.6: Plug connectors for EtherCAT P
1 - input
2 - downstream connection
Connection
Fig.7: M8 socket, P-coded
ContactSignalVoltageCore color
1Tx +GND
2Rx +GND
S
P
3Rx -UP: Peripheral voltage, +24V
4Tx -US: Control voltage, +24V
DC
DC
yellow
white
blue
orange
HousingShieldShieldShield
1)
The core colors apply to EtherCAT P cables and ECP cables from Beckhoff.
1)
EPP1111-000015Version: 1.2
Mounting and connection
4.2.2Status LEDs
4.2.2.1Supply voltages
Fig.8: Status LEDs for the supply voltages
EtherCAT P Box Modules have two LEDs that display the status of the supply voltages. The status LEDs are
labelled with the designations of the supply voltages: Us and Up.
A status LED lights up green when the respective supply voltage is present.
A Status LED lights up red if the respective supply voltage is short-circuited.
4.2.2.2EtherCAT
Fig.9: Status LEDs for EtherCAT
L/A (Link/Act)
A green LED labelled "L/A" or “Link/Act” is located next to each EtherCAT/EtherCATP socket. The LED
indicates the communication state of the respective socket:
LEDMeaning
offno connection to the connected EtherCAT device
litLINK: connection to the connected EtherCAT device
flashesACT: communication with the connected EtherCAT device
Run
Each EtherCAT slave has a green LED labelled "Run". The LED signals the status of the slave in the
EtherCAT network:
LEDMeaning
offSlave is in "Init" state
flashes uniformlySlave is in "Pre-Operational“ state
flashes sporadicallySlave is in "Safe-Operational" state
litSlave is in "Operational" state
Description of the EtherCAT slave states
EPP1111-000016Version: 1.2
Mounting and connection
I = 3 A
1020
5
10
15
20
300
0
25
40
Vert. Faktor: 0,22 cm / V
Voltage drop (V)
Cable length (m)
0.14 mm²
0.22 mm²
0.34 mm²
4.2.3Conductor losses
Take into account the voltage drop on the supply line when planning a system. Avoid the voltage drop being
so high that the supply voltage at the box lies below the minimum nominal voltage.
Variations in the voltage of the power supply unit must also be taken into account.
Use the planning tool for EtherCAT P in TwinCAT.
Voltage drop on the supply line
Fig.10: Voltage drop on the supply line
EPP1111-000017Version: 1.2
Mounting and connection
4.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.11: UL label
EPP1111-000018Version: 1.2
Commissioning
3
4
5
6
5Commissioning
5.1Integration in TwinCAT
The procedure for integration in TwinCAT is described in this Quick start guide.
5.2Creating a Hot Connect group
The EtherCAT system documentation contains a complete description of the Hot Connect function. It also
contains general instructions for creating a Hot Connect group.
However, please use the following special instructions for the EPP1111-0000:
1. Arrange the EtherCAT devices so that the EPP1111-0000 is the first EtherCAT device in the planned
Hot Connect group.
2. Right-click on the EPP1111 IO module.
3. Click on "Add to HotConnect group" in the context menu.
4. Select the EtherCAT devices for the Hot Connect group:
With the shift key held down, click on the desired EtherCAT devices in the "Select Connected Slaves"
box to mark them.
5. Make sure that the checkboxes are set correctly:
- "Identification Value" checkbox is checked
- "EtherCAT Addr. of previous Slave" is unchecked
6. Set the desired ID under "Identification Value". (0..999)
Fig.12: Creating a Hot Connect group
EPP1111-000019Version: 1.2
Commissioning
902
decimal
ID =
5.3ID switches
The units, tens and hundreds digits of the ID each have their own ID switch. The ID switches are labelled
accordingly:
• X 1
• X 10
• X 100
Sample
Fig.13: ID switches sample
EPP1111-000020Version: 1.2
Commissioning
1
2
4
3
5.4Troubleshooting
• Check whether the EPP1111-0000 is the first EtherCAT device in the Hot Connect group: The first
EtherCAT device in a Hot Connect group is marked by a red "HC" symbol.
Remedy:
1. In the Solution Explorer, right-click on the EtherCAT device with the red "HC" symbol.
2. Click on "Delete from HotConnect group" in the context menu.
3. Create the Hot Connect group again: Procedure [}19]
• Check whether the correct addressing method, "Explicit Device Identification", is set:
1. Double-click on the "EPP1111" IO module.
2. Click on the "Hot Connect" tab.
3. Click on the "Configure" button.
4. Make sure that "Explicit Device Identification" is selected.
EPP1111-000021Version: 1.2
Commissioning
5.5CoE objects
5.5.1Directory
Index (hex)Name
1000
1008
1009
100A
1018
1A00
1C00
1C12
1C13
1C33
F000
F008
F600
Device type [}23]
Device name [}23]
Hardware version [}23]
Software version [}23]
Identity [}23]
ID TxPDO-Map Inputs [}23]
Sync manager type [}23]
RxPDO assign [}23]
TxPDO assign [}24]
SM input parameter [}24]
Modular device profile [}25]
Code word [}25]
DIG Inputs Ch.1 [}25]
5.5.2Object description and parameterization
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 in-
stalling it according to installation instructions.
Parameterization via the CoE list (CAN over EtherCAT)
The EtherCAT device is parameterized via the CoE-Online tab (double-click on the respective object) or via the Process Data tab (allocation of PDOs). Please note the following general CoE notes
when using/manipulating the CoE parameters:
• Keep a startup list if components have to be replaced
• Differentiation between online/offline dictionary, existence of current XML description
• use “CoE reload” for resetting changes
EPP1111-000022Version: 1.2
Commissioning
5.5.2.1Standard objects
Index 1000 Device type
Index (hex) NameMeaningData typeFlagsDefault
1000:0Device typeDevice type of the EtherCAT slave: The Lo-Word con-
tains the CoE profile used (5001). The Hi-Word contains the module profile according to the modular device profile.
Index 1008 Device name
Index (hex) NameMeaningData typeFlagsDefault
1008:0Device nameDevice name of the EtherCAT slaveSTRINGROEPP1111-0000
Index 1009 Hardware version
Index (hex) NameMeaningData typeFlagsDefault
1009:0Hardware versionHardware version of the EtherCAT slaveSTRINGRO-
Index 100A Software version
Index (hex) NameMeaningData typeFlagsDefault
100A:0Software versionFirmware version of the EtherCAT slaveSTRINGRO-
UINT32RO0x00001389
(5001
)
dec
Index 1018 Identity
Index (hex) NameMeaningData typeFlagsDefault
1018:0IdentityInformation for identifying the slaveUINT8RO0x04 (4
)
dec
1018:01Vendor IDVendor ID of the EtherCAT slaveUINT32RO0x00000002 (2
1018:02Product codeProduct code of the EtherCAT slaveUINT32RO0x04574052
1018:03RevisionRevision numberof the EtherCAT slave; the Low Word
(72826962
UINT32RO-
dec
(bit 0-15) indicates the special terminal number, the
High Word (bit 16-31) refers to the device description
1018:04Serial numberSerial number of the EtherCAT slave; the Low Byte (bit
UINT32RO0x00000000 (0
0-7) of the Low Word contains the year of production,
the High Byte (bit 8-15) of the Low Word contains the
week of production, the High Word (bit 16-31) is 0
1C00:0Sync manager type Using the Sync ManagersUINT8RO0x04 (4
1C00:01SubIndex 001Sync-Manager Type Channel 1: Mailbox WriteUINT8RO0x01 (1
1C00:02SubIndex 002Sync-Manager Type Channel 2: Mailbox ReadUINT8RO0x02 (2
1C00:03SubIndex 003Sync-Manager Type Channel 3: Process Data Write
UINT8RO0x03 (3
(Outputs)
1C00:04SubIndex 004Sync-Manager Type Channel 4: Process Data Read (In-
UINT8RO0x04 (4
puts)
)
dec
)
dec
)
dec
)
dec
)
dec
)
dec
)
)
dec
Index 1C12 RxPDO assign
Index (hex) NameMeaningData typeFlags Default
1C12:0RxPDO assignPDO Assign OutputsUINT8RW0
EPP1111-000023Version: 1.2
Commissioning
Index 1C13 TxPDO assign
Index (hex) NameMeaningData typeFlags Default
1C13:0TxPDO assignPDO Assign InputsUINT8RW0x02 (2
1C13:01Subindex 0011. allocated TxPDO (contains the index of the associ-
UINT16RW0x1A00 (6656
dec
ated TxPDO mapping object)
Index 1C33 SM input parameter
Index (hex) NameMeaningData typeFlags Default
1C33:0SM input parameter Synchronization parameters for the inputsUINT8RO0x20 (32
1C33:01Sync modeCurrent synchronization mode:
UINT16RW0x0000 (0
• 0: Free Run
• 1: Synchron with SM 3 Event (no outputs
available)
• 2: DC - Synchron with SYNC0 Event
• 3: DC - Synchron with SYNC1 Event
• 34: Synchron with SM 2 Event (outputs
available)
1C33:02Cycle timeCycle time (in ns):
• Free Run: Cycle time of the local timer
UINT32RW0x000186A0
(100000
• Synchron with SM 2 Event: Master cycle time
• DC mode: SYNC0/SYNC1 Cycle Time
1C33:03Shift timeTime between SYNC0 event and reading of the inputs
UINT32RO0
(in ns, only DC mode)
1C33:04Sync modes sup-
ported
Synchronization modes supported:
• Bit 0: free run is supported
UINT16RO0x0001 (1
• Bit 1: Synchron with SM 2 Event is supported
(outputs available)
• Bit 1: Synchron with SM 3 Event is supported (no
outputs available)
• Bit 2-3 = 01: DC mode is supported
• Bit 4-5 = 01: Input Shift through local event
(outputs available)
• Bit 4-5 = 10: Input Shift with SYNC1 Event (no
outputs available)
• Bit 14 = 1: dynamic times (measurement through
writing of 1C33:08 [}24])
1C33:05Minimum cycle time Minimum cycle time (in ns)UINT32RO0x000124F8
(75000
1C33:06Calc and copy time Time between reading of the inputs and availability of
UINT32RO0
the inputs for the master (in ns, only DC mode)
1C33:07Minimum delay timeUINT32RO0
1C33:08Command• 0: Measurement of the local cycle time is
UINT16RW0
stopped
• 1: Measurement of the local cycle time is started
The entries 1C33:03, 1C33:06 and 1C33:09 are updated
with the maximum measured values.
For a subsequent measurement the measured values
are reset
1C33:09Maximum Delay
time
1C33:0BSM event missed
counter
1C33:0CCycle exceeded
counter
Time between SYNC1 event and reading of the inputs
(in ns, only DC mode)
Number of missed SM events in OPERATIONAL (DC
mode only)
Number of occasions the cycle time was exceeded in
OPERATIONAL (cycle was not completed in time or the
UINT32RO0
UINT16RO0
UINT16RO0
next cycle began too early)
1C33:0DShift too short
counter
1C33:20Sync errorThe synchronization was not correct in the last cycle
Number of occasions that the interval between SYNC0
and SYNC1 event was too short (DC mode only)
UINT16RO0
BOOLEANRO0
(outputs were output too late; DC mode only)
dec
dec
)
dec
)
)
dec
)
)
dec
)
)
dec
EPP1111-000024Version: 1.2
Commissioning
5.5.2.2Profile-specific objects
Index F000 Modular device profile
Index (hex) NameMeaningData typeFlags Default
F000:0Modular device pro-
file
F000:01Module index dis-
tance
F000:02Maximum number of
modules
Index F008 Code word
Index (hex) NameMeaningData typeFlags Default
F008:0Code wordUINT32RW0x00000000 (0
Index F600 DIG Inputs CH.1
Index (hex) NameMeaningData typeFlagsDefault
F600:0DIG Inputs Ch.1UINT8RO0x01 (1
F600:01IDThe value that is set by the ID switches.UINT16RO0x0000 (0
General information for the modular device profileUINT8RO0x02 (2
dec
Index distance of the objects of the individual channels UINT16RO0x0010 (16
Number of channelsUINT16RO0x0002 (2
dec
)
dec
dec
)
dec
)
)
)
dec
)
EPP1111-000025Version: 1.2
Commissioning
5.6Decommissioning
WARNING
Risk of electric shock!
Bring the bus system into a safe, de-energized state before starting disassembly of the devices!
Disposal
In order to dispose of the device, it must be removed.
In accordance with the WEEE Directive 2012/19/EU, Beckhoff takes back old devices and accessories in
Germany for proper disposal. Transport costs will be borne by the sender.
Return the old devices with the note "for disposal" to:
Beckhoff Automation GmbH & Co. KG
Service Department
Stahlstraße 31
D-33415 Verl
EPP1111-000026Version: 1.2
Appendix
6Appendix
6.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 IP 67 modules 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
EPP1111-000027Version: 1.2
Appendix
6.2Accessories
Mounting
Ordering informationDescription
ZS5300-0001Mounting rail (500mmx129mm)
Labeling material, protective caps
Ordering informationDescription
ZS5000-0010Protective cap for M8 sockets, IP67 (50 pieces)
ZS5100-0000Inscription labels, unprinted, 4 strips of 10
ZS5000-xxxxPrinted inscription labels on enquiry
Cables
A complete overview of pre-assembled cables for EtherCAT Box modules can be found here.
Ordering informationDescription
ZK700x-xxxx-xxxx
EtherCAT P cable M8 Link to website
Tools
Ordering informationDescription
ZB8801-0000Torque wrench for plugs, 0.4…1.0Nm
ZB8801-0001Torque cable key for M8/ wrench size 9 for ZB8801-0000
Further accessories
Further accessories can be found in the price list for fieldbus components from Beckhoff and online
at https://www.beckhoff.com.
EPP1111-000028Version: 1.2
Appendix
6.3Version identification of EtherCAT devices
Designation
A Beckhoff EtherCAT device has a 14-digit designation, made up of
• family key
• type
• version
• revision
ExampleFamilyTypeVersionRevision
EL3314-0000-0016EL terminal
(12 mm, nonpluggable connection
level)
ES3602-0010-0017 ES terminal
(12 mm, pluggable
connection level)
CU2008-0000-0000 CU device2008 (8-port fast ethernet switch) 0000 (basic type) 0000
3314 (4-channel thermocouple
terminal)
3602 (2-channel voltage
measurement)
0000 (basic type) 0016
0010 (highprecision version)
0017
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
EPP1111-000029Version: 1.2
Appendix
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
• IP67: EtherCAT Box
• Safety: TwinSafe
• Terminals with factory calibration certificate and other measuring terminals
Examples of markings
Fig.14: EL5021 EL terminal, standard IP20 IO device with serial/ batch number and revision ID (since
2014/01)
EPP1111-000030Version: 1.2
Fig.15: EK1100 EtherCAT coupler, standard IP20 IO device with serial/ batch number
Appendix
Fig.16: CU2016 switch with serial/ batch number
Fig.17: EL3202-0020 with serial/ batch number 26131006 and unique ID-number 204418
EPP1111-000031Version: 1.2
Appendix
Fig.18: EP1258-00001 IP67 EtherCAT Box with batch number/ date code 22090101 and unique serial
number 158102
Fig.19: EP1908-0002 IP67 EtherCAT Safety Box with batch number/ date code 071201FF and unique serial
number 00346070
Fig.20: EL2904 IP20 safety terminal with batch number/ date code 50110302 and unique serial number
00331701
Fig.21: ELM3604-0002 terminal with unique ID number (QR code) 100001051 and serial/ batch number
44160201
EPP1111-000032Version: 1.2
Appendix
6.3.1Beckhoff 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.22: 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:
EPP1111-000033Version: 1.2
Appendix
Item
Type of
no.
information
1Beckhoff order
number
2Beckhoff Traceability
Number (BTN)
3Article descriptionBeckhoff article
4QuantityQuantity in packaging
5Batch numberOptional: Year and week
6ID/serial numberOptional: Present-day
7Variant numberOptional: Product variant
...
ExplanationData
Beckhoff order number 1P81P072222
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
Number of digits
identifier
S12SBTNk4p562d7
1K321KEL1809
Q6Q1
2P142P401503180016
51S1251S678294104
30P3230PF971, 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.
EPP1111-000034Version: 1.2
Appendix
6.4Support 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