Error message 'PLL Error' when starting up the EtherCAT (corrected from V1.9)

Corrected from:
Cabinet Controller c520 V1.9
Cabinet Controller c550 V1.9

Response of the new version:
The error message 'PLL Error' does not occur under the conditions described below and the EtherCAT bus changes to 'Operational' without errors.

What happens?
When starting up the EtherCAT bus after 'Operational', the error message 'PLL Error' may sporadically occur on an EtherCAT slave. The EtherCAT only changes to the 'Pre-Operational' status and the following message is entered in the logbook:
Slave signals Error. AL state: 'PREOP' (0x12), AL state code: 'PLL Error' (0x32).

When does the behaviour occur?
The behaviour described above is more likely to occur with a large bus structure (many EtherCAT devices) and high task cycle times (=> 4ms).

Which products are affected?
Cabinet Controller c520 from V1.0
Cabinet Controller c550 from V1.0
Cabinet Controller c750 from V1.0

Short-term measures:
Restart the EtherCAT master of the Lenze controller, either
  • by carrying out a reset warm or reset cold.
or
  • by setting xRestart input on the EtherCAT_Master function module.

Evaluation / recommendations:
Due to this functional restriction, the Lenze controller sporadically cannot establish process data communication with the connected EtherCAT slaves. An application solution is described under Short-term measures.

Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202200162/1/
Kontaktformular