Beckhoff EL33-00 Series Documentation Download

Page: 185 / 204

Appendix

EL33xx-00x0

185

Version: 4.2

6.2

EtherCAT AL Status Codes

For detailed information please refer to the

EtherCAT system description

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.

Simplified update by bundle firmware

The update using so-called

bundle firmware

is more convenient: in this case the controller firmware and the

ESI description are combined in a *.efw file; during the update both the firmware and the ESI are changed in
the terminal. For this to happen it is necessary

• for the firmware to be in a packed format: recognizable by the file name, which also contains the

revision number, e.g. ELxxxx-xxxx_REV0016_SW01.efw

• for password=1 to be entered in the download dialog. If password=0 (default setting) only the firmware

update is carried out, without an ESI update.

• for the device to support this function. The function usually cannot be retrofitted; it is a component of

many new developments from year of manufacture 2016.

Following the update, its success should be verified

• ESI/Revision: e.g. by means of an online scan in TwinCAT ConfigMode/FreeRun – this is a convenient

way to determine the revision

• Firmware: e.g. by looking in the online CoE of the device

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 re-
quire re-commissioning by the manufacturer.