Lenze EtherCAT Controller-based Automation - Manual (Page 175)

Lenze · Controller-based Automation · EtherCAT® Communication Manual · DMS 6.4 EN · 04/2014 · TD17
175
12 Diagnostics
12.5 Error scenarios
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
12.5.1 The EtherCAT bus does not assume the "Pre-Operational" state.
During the start-up of the EtherCAT bus, a check is carried out at the transition from "Init" to "Pre-
Operational" to determine whether the physical bus configuration corresponds to the bus
configuration configured. If theses configurations are different, the master does not enter the "Pre-
Operational" state.
Furthermore, the slaves are initialised during the transition from "Init" to "Pre-Operational". If this
fails because, for instance, a slave denies the configuration, the master does not enter the "Pre-
Operational" state.
Cause Faulty bus configuration and bus structure
• Slaves are missing.
• Slaves have been inverted or their configuration is faulty.
• A wrong slave type has been configured or is at the fieldbus.
• The inputs and outputs of the EtherCAT communication module are reversed (IN/OUT
connections).
• Faulty wiring
Error message EtherCAT_Master: Start master failed. Bus mismatch
...
Lenze_EPM_T130_V10_18 (1002): Configuration mismatch. Check VendorID failed (0x3B /
missing )
Remedies Correct the bus configuration or the physical bus structure.
Afterwards, reload the »PLC Designer« application into the automation system.
Cause Wiring error: EtherCAT cable is not connected to the master.
Error message EtherCAT_Master: Start master failed. EtherCAT cable disconnected
Remedies Correct wiring.
Afterwards, reload the »PLC Designer« application into the automation system.