When an EFC is on the ethercat network of the ctrlX core, an efc will not be seen in the scan for devices in the 'ctrlx Automation' or the 'control unit' cases.  However doing an IP address search will find an EFC drive via EOE.
Is it is possible in the future to support communiations to an EFC via the 'ctrlx Automation' method?
Â
Sorry for the late reply. Somehow lost track of this topic. The easiest way would be use EoE as communication method as you mentioned. I will check for EFC and ctrlX AUTOMATION scan method in the future as it is connected to the DriveConnect App.
EDIT: At the moment only SoE devices are considered but we are working on EoE support inside the DriveConnect app.