When replacing an EtherCAT slave 053-1EC00 by 053-1EC01 an adaptation of your
project is required. When replacing the EtherCAT slaves, make sure that all settings and
parameters of the 053-1EC00 EtherCAT slave that deviate from the standard setting are
transferred to the EtherCAT slave 053-1EC01. Therefore, these settings should be saved
appropriately before the replacement. Precondition for replacing the EtherCAT slave
053-1EC00 by 053-1EC01 is that the ESI file for the EtherCAT slave 053-1EC01 is
installed in the configuration tool. The replacement takes place in the configuration by
deleting the EtherCAT slave 053-1EC00 and adding the EtherCAT slave 053-1EC01. In
the following all settings are listed, which should be noted.
n
EtherCAT station address
–
If the station address does not match that of the EtherCAT Slave 053-1EC00,
there is a topology error. The EtherCAT slave is not controlled.
n
Position of the EtherCAT slave on the bus
–
If the position of the EtherCAT slave on the bus does not match the position of the
EtherCAT slave 053-1EC00, there is a topology error. The EtherCAT slave is not
controlled.
n
Slot assignment of the modules
–
As long as the total IO size of the EtherCAT slave matches the configured size of
the master, the EtherCAT slave can switch to Operational (
Op
). If the slot assign-
ment is changed, the wrong process data of the modules is transmitted
n
Download the slot configuration
–
If this option was activated for the EtherCAT slave 053-1EC00, then this option
should also be activated for the EtherCAT slave 053-1EC01. Please pay attention
to an identical slot assignment. If the slot configuration fits between master and
053-1EC01 but deviates from the slot configuration of EtherCAT slave
053-1EC00, this deviation is not recognized!
n
PDO mapping of the modules
–
For modules with variable IO size, for this modules the PDO mapping of the
053-1EC01 should be set exactly the same as for the 053-1EC00. Otherwise, the
slave does not change to
Safe-Op
or
Op
.
n
CoE init commands
–
The CoE init commands at the 053-1EC01 should be made the same as with the
053-1EC00. If there are deviations, the EtherCAT slave can switch to
Op
, but
there is a possibility that the EtherCAT slave or its modules will not behave as
expected.
n
HotConnect
address
–
If the 053-1EC00 was addressed via a
HotConnect
address, then for the
053-1EC01 this
HotConnect
address is taken to the master configuration. Also
the 053-1EC01 must use this
HotConnect
address at the bus.
For this there are the following possibilities:
Explicit device ID via address switch:
If the
HotConnect
address is less than 128, you can set the
HotConnect
address
via the address switch on the EtherCAT slave.
Ä
Chap. 4.2 ‘Setting the HotCon-
nect address’ page 48
Configured Station Alias:
If the
HotConnect
address is greater than 128, you can set the
HotConnect
address via
Configured Station Alias
in the EtherCAT configuration.
Ä
Chap.
4.2.2 ‘HotConnect via Configured Station Alias’ page 49
n
Parameter - Advanced options
–
In addition, there are other parametrization options for the EtherCAT Slave as
advanced options. These settings, such as
SyncManager Watchdog
or
State
Change Timeouts
, are slave-specific settings. These parameters should be
checked.
Settings
VIPA System SLIO
Deployment
Replace EtherCAT slave 053-1EC00 with 053-1EC01
HB300 | IM | 053-1EC01 | en | 18-49
97
