Corrected from:
Controller 3200 C from V3.3.2
Controller p500 from V3.3.2
Behaviour of the new version?
When the EtherCAT bus is started, there is no SDO timeout for 8400 slaves anymore.
What happens?
The EtherCAT logbook and the IPC logbook contain SDO timeouts of the EtherCAT stacks.
Not all parameters of the 8400 startup list are transmitted. The configuration of the 8400 frequency inverters in the PLC project has not been carried out completely.
When does the problem occur?
When the EtherCAT bus is started, SDO timeouts may occur for 8400 slaves.
Which products are affected?
Controller 3200 C from V3.2
Controller p500 from V3.3
8400 frequency inverter
Diagnostics options?
Check whether SDO timeout messages have been entered in the IPC/PLC logbook.
Short-term measures/recommendations?
Activate the 'Expert setting' in the EtherCAT slave tab. Increase the value under SDO Timeout, e.g. to 5000ms.
Evaluation:
When the EtherCAT bus is started, SDO timeouts may occur during the parameterisation of 8400 frequency inverters. In this case, the 8400 have not been configured completely.
