Appendix
EL31xx-00xx
211
Version: 5.9
EL3164
Hardware (HW) Firmware (FW) Revision no.
Date of release
00 - 15*
01
EL3164-0000-0016
2010/07
02
2011/01
03
2012/03
EL3164-0000-0017
2012/08
04*
EL3164-0000-0018
2013/12
EL3164-0000-0019
2016/06
EL3164-0000-0020
2017/02
EL3174
Hardware (HW) Firmware
Revision-Nr.
Release-Datum
01*
03*
EL3174-0000-0016
2017/07
EL3174-0002
Hardware (HW) Firmware
Revision-Nr.
Release-Datum
00 - 03*
01
EL3174-0002-0016
2016/12
02*
EL3174-0002-0017
2017/01
EL3174-0032
Hardware (HW) Firmware
Revision-Nr.
Release-Datum
00*
02*
EL3174-0032-0016
2016/12
EL3174-0090
Hardware (HW) Firmware
Revision-Nr.
Release-Datum
01*
04*
EL3174-0090-0016
2018/04
*) This is the current compatible firmware / hardware version at the time of the preparing this documentation.
Check on the Beckhoff web page whether more up-to-date
documentation
is available.
6.3
Firmware 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.
Содержание EL3101
Страница 1: ...Documentation EL31xx 00xx Analog Input Terminals 16 Bit 5 9 2018 08 28 Version Date...
Страница 2: ......
Страница 6: ...Table of contents EL31xx 00xx 6 Version 5 9...
Страница 52: ...Mounting and wiring EL31xx 00xx 52 Version 5 9 Fig 33 Other installation positions...
Страница 123: ...Commissioning EL31xx 00xx 123 Version 5 9 Fig 118 Incorrect driver settings for the Ethernet port...
Страница 134: ...Commissioning EL31xx 00xx 134 Version 5 9 Fig 137 EtherCAT terminal in the TwinCAT tree left TwinCAT 2 right TwinCAT 3...