Beckhoff EL7037 User Manual download pdf (Page 210)

Appendix

8.2 EtherCAT AL Status Codes

For detailed information please refer to the EtherCAT system description.

8.3 Firmware 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 for storing its own device description, a so-called

EEPROM. 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.com . All ESI files (EtherCAT Slave Information) are available in ZIP format.

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.

Attention

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 Lost Frames must be

avoided.

• The power supply must adequately dimensioned. The signal level must meet the specifi-

cation.

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

Attention

Notice regarding update of the ESI description/EEPROM

Some slaves have stored calibration and configuration data from the production in the EEP-

ROM. 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:

EL70x7210 Version 1.0

1 2 ... 205 206 207 208 209 210 211 212 213 214 215 ... 226 227

No comments

Beckhoff EL7037 User Manual Page 210