Skip to content

Slaves go OP on first boot, but after EPOS4 power-cycle/reboot master/driver “launches” with no output and no slaves detected #209

Description

@alexxandresolana

I’m using 6 Maxon EPOS4 50/5 drives as EtherCAT slaves with a Linux PC as the master. After a clean boot, all slaves are detected and can reach OP. But after rebooting/power-cycling the EPOS4 drives, the bus no longer detects any slaves (this happens before ROS2/ethercat_ros2_driver, so it’s not ROS2-related). No errors are printed.
Tried ethercat stop / ethercat start but it didn’t help.

Expected behavior
After EPOS4 reboot/power-cycle, the master should still:
Detect all 6 slaves
Allow PREOP → SAFEOP → OP transitions

Question
Any way to force rediscovery after a slave power-cycle (rescan/service restart/link reset), or is a master reboot expected/required?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions