lcec_conf exited without becoming ready

Hello!

My experience with LinuxCNC goes back for 15-16 years and now I am taking my first steps in getting it to work with EtherCAT. I am doing a retrofit of Biesse CNC machine and customer wants to use VFD for spindle that is made by ABB (model ACS380). Since by default that VFD has 2 digital inputs and 0 analog inputs, I could only get "start/stop" function to work so they got EtherCAT module (FECA_01 with firmware 1.30) for that VFD that I am now trying to get to work.
I have (at least I think so) successfully installed ethercat libraries as per first post by RodW in this thread:
forum.linuxcnc.org/ethercat/45336-etherc...-how-to-step-by-step
I have got XML file from ABB for the VFD drive (they provide ZIP archive with large collection of them and I picked the one that had matching firmware number of the EtherCAT module in filename), I have attached it.
Attached is also a screenshot that shows that EtherCAT service is active, those few lines in HAL file that I used to start lcec module, the thunar window to show actual location of XML file (to show that it matches the line in HAL file) and the error message of LinuxCNC.
Is there anything obvious I am missing?
In many forum posts I see that people also use cia402 module. Is it required here? I have not found any explanation of what exactly it is used for.
Thanks in advance!

The provided xml is useless for our purposes.Its for twincat on windows You could try typing: lcec_configgen to generate an xml file
cia402 is a standard for drives (and vfds). It essentially uses the cia402 state machine to safely power drives on. so for ethercat drives, we load the lcec driver then for each drive we load the cia402 state machine. Then at the end of our servo thread cycle, we write cia402 back to the ethercat layer and  then write everything back to the ethercat bus

ok, thank you!
I tried lcec_configgen and the result is xml file with 2 lines which, based on the error message, seem insufficient (please see attached image). note that it was before I tried adding cia402 module. Is that a mistake and is cia402 module mandatory? because the way I understand it now is that cia402 helps connecting HAL pins, but the VFD should be discovered over ethercat even without it. is that correct? one more thing is that cia402.comp in the comments contains suggested HAL file lines and there lcec_conf is loaded in line 50 before cia402 in line 52:
github.com/dbraun1981/hal-cia402/blob/main/cia402.comp#L50
so I think that it should work like it is, the problem most probably is the XML file
I was expecting at least some kind of output from "ethercat slaves" command - there was totally nothing. is that ok? I was expecting some message that shows discovered slave device or a message that no devices were found

one step at a time. you need to get rid of the error messages. comment out classicladder.
I have never used it so on a starting config, why do you?
Why are you still showing us useless xml?
It seems you are not finding your xml file.
I can't see any relevant messages or that 2 line generated file. it may be correct.

a little update - it turns out that the EtherCAT adapter works better if it is enabled in VFD settings. so I did that and then "ethercat slaves" command does recognize it and also lcec-configgen creates a lot more meaningful xml file and installing cia402 component did the trick - now it complains about invalid modparam "enable VLAccel" but that is expected because I brought the laptop in house and left VFD in workshop

do not worry about classicladder - I am using a sample config with classicladder because I wanted to create some basic logic for carousel toolchanger

so I tried again with VFD connected and got still the same error (see attached image "error present")
what I did is cut out lines 24-28, saved and tried again and LinuxCNC did run! see attached image "error gone".
how do I proceed from here to actually get the VFD running? is it enough to set the correct HAL pin from 0 to 1 to mimic "run/stop" signal together with providing some frequency/speed value on second pin or does this process require any more steps?

Nobody knows  you VFD so you need to work it out yourself, it seems there is a syntax error in your xml and it reports the line number.
Sharing your xml file now you have  made some progress would be helpful. as we are flying blind
I suspect you will need to command it more like it was a servo except use a mode that commands RPM (velocity) not position 

I found this document:
library.e.abb.com/public/52b4831c464449e..._CiA402_Rev_A_EN.pdf

that is where I found which parameters to set to enable the ethercat module. at the moment I have:
1) set 50.01 parameter to 1 (enable the module)
2) 51.01 to 135 (set to EtherCAT)
3) 50.04 to 4 (reference is speed)
4) 51.02 to 0 (CiA402 drive profile)
and attached is the XML file. I would appreciate any hints on how to get it move the motor (I am looking for basic functions - start/stop and set the rotation speed). any extras, like spindle-at-speed signal, what is motor load etc is optional
I am looking at that manual and it is very confusing for me about the bits of command word and status word. I believe it is handled by cia402 component and I just need to connect proper HAL pins. is that correct?

It seems that its recognized as a cia402 device. at this point, with LinuxCNC open, open another window and type: halcmd show pin lcec

This will list the pins they were found. You can use them in your hal file and follow the cia402 templates.
I have a feeling you need to command your drive using a mode not supported by the cia402 component. It will need modifying and rebuilding to support it. But I can't help you there as I have no expereince. Someone else may be able to help.

I do know one user using an abb VFD but they are using MODBUS 485 to avoid buying the FECA-01 interface

please find attached 3 screenshots - left side are all the pins for cia402 component (they did all fit in screen) and right side is list of lcec pins in terminal. do you have any idea, which of these is "enable" pin? lcec.0.state-preop, lcec.0.state-safeop and lcec.0.state-op seem suspicious to me but then I do not understand why would 3 pins be needed. I would appreciate some hints on which pins should I try for enabling the drive and which would be most suitable candidate for making the motor spin. cia402.0.velocity-cmd would seem like most obvious candidate but is there anything else to add (so far in my experience it would have been 2 pins - one sets velocity, the other would be a bit output for "run/stop")
BTW cia402.0.controlword has value 4, which seem to match instructions in manual to set the parameter 50.04 to 4 (which means that reference is speed). does that help in any way? and since the manual says this:"Ensure the drive profile parameter 51.02 is set to CiA402 (0)" I would like to think that it's all good regarding the suspicion about needing different mode rather than cia402.
could you please share some link where I could see some cia402 templates that you mentioned?