EFC communication with ctrlX CORE. EFC stuck in pre-op after adding a telegram

[Young_Chon]

Hello,

I have a test project using COREX-C-X3-11-ANNN-21.01-01RS-NN-NN with EtherCat master version 2.2.0.  When the EFC is configured with using the Rexroth mode with default 2 input words & 2 output words then everything seems to be working without an issue.  The problem is EFC does not come out of pre-op mode when additional telegram is added to the telegram (added addtional telegram using Expert mode).  After addtional telegram has been added then download new IO configuration and update the PLC program.    ctrlX Core master EtherCat status is OP but the EFC is stuck in "pre-op".   Even cycling power to the entire system still not fix the issue.  Once redownload the default configuration then the communication works again so it seem unlikely due to hardware issue. 

[CodeShepherd]

Could you give us some more information:

• Which parameter you did add?
• Are they even usable in cyclic communication?
• Is there an error message at the EtherCat master (e.g. drive parameter wrong)?
• Which firmware version of the EFC and the multi ethernet extension (MEP) is used?

[Young_Chon]

Added parameter(s) were selected from I/O Engineering drop down menu.  Tried parameters were typically "d0.xx" diagnostic parameters.  For example, I have tried d0.0, d0.1, d.12, d0.13......  Configured parameters were shown in the PLC engineering data layer after downloading to the Core.  EtherCat screen show all devices status with green circle with a check mark.  EtherCat Master does not show any error message and only indication of malfunction is xFC01_Rexroth_mode shows "pre-op".  All other devices in the EtherCat network showed "op".

No error message were shown other than xFC is stuck in the "pre-op" and will not transition out even after the system complete power cycle.

EFC firmware is "FWA-EFC01*-NNN-03V39-NN" and MEP fiemware is "FWAxFC01-MEP18" .

Thank you for your support and please let me know if you need further information.