Repository navigation
Userspace EtherCAT master for LinuxCNC uspace-v1.3
Pre-releasePackages of the userspace EtherCAT master for LinuxCNC's ecat component: debian12 for Debian 12 (bookworm), debian13 for Debian 13 (trixie). Since 1.1 without lcec_uspace (frozen; keep uspace-v1.0 from MetalMusings/linuxcnc-ethercat for it). See packaging/linuxcnc/README.md.
Install: sudo apt install ./linuxcnc-ethercat-uspace_*_amd64.deb (the file for your Debian).
New in 1.3
Messages through the master's log. With the AF_XDP transport (xdp-skb, xdp-native), libbpf and libxdp printed straight to stderr, and the raw, XDP and CCAT transports printed their own errors the same way. None of it reached the master's log, so an application that takes the log through ecrt_lib_init() (ecat's event log, EtherCAT Setup's Messages from the master, its report) never saw why a transport failed to open. Now:
- libbpf's and libxdp's messages go through the master's log with their level (debug messages are dropped);
- the lines they print on every start of a working system are left out: the ELF sections libbpf does not know (
skipping unrecognized data section) and libxdp's fallback to a single program without a mounted bpffs; - the transports' errors are logged as errors (
EtherCAT ERROR: XDP: Failed to create XSK socket: ...), a stale XDP program as a warning.
Only the list of transport names that the tool prints stays on stderr. All of it runs when a transport opens or closes, never in the cyclic path.
Tried on a bus with xdp-native on an igc card (no libbpf lines any more) and on lo, which has no native XDP (the kernel's message, libxdp's and the transport's error come as WARN, INFO and ERR log lines).
Works with ecat 0.12 and later (LinuxCNC 2.10) and ecat 0.11 (LinuxCNC 2.9); needs the fork's ecrt_master_request_al_state(), ecrt_master() and ecrt_master_get_slave() (all in 1.1 and later).