Skip to content

ecat ecat-v0.16

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 07:56
· 134 commits to main since this release

ecat for LinuxCNC 2.10. There are no 2.10 packages for Debian yet, so the main way to install is for a run-in-place LinuxCNC; there is a package too.

Install

First the userspace master, linuxcnc-ethercat-uspace 1.1 or newer (1.2 recommended) from MetalMusings/ethercat: sudo apt install ./linuxcnc-ethercat-uspace_*_amd64.deb.

  • Run-in-place LinuxCNC: unpack ecat-rip-0.16-debian13.tar.gz (or -debian12) and run ./install. It puts ecat.so in your tree's rtlib and ecatsetup in ~/.local/bin; ./install --uninstall takes it away. ecat.so is built against one LinuxCNC, commit b0e7b191b9 (2.10.0~pre2-436): the installer compares your tree's HAL headers with that build's and refuses on any difference (a different HAL API could crash a machine), and then says how to build ecat for your LinuxCNC from source.
  • LinuxCNC 2.10 package: linuxcnc-ecat_*.deb (debian12, debian13).

LinuxCNC 2.9 users take ecat-v0.11. The window, ecatsetup --gui, needs python3-pyqt5. To try ecat without disturbing your setup: getting started. See the README.

What is new in 0.16

The component (first change since 0.12)

  • The master's own messages (its log, up to level info) go into the event log beside the events, such as "Slave seems not to support distributed clocks!" or an SDO abort while a slave is configured. The event log file is version 2; EtherCAT Setup reads both.
  • The master's messages also go to ecat's output: the terminal of halrun, the I/O test's log, or LinuxCNC's print file.

Distributed clocks: what a slave can do (docs)

  • From four sources: the slave's EtherCAT chip, its SII, the ESI file, and CoE 0x1C32/0x1C33. The slave's page shows them under the Sync choice, which offers free run, the slave's own DC modes, and any AssignActivate.
  • Warnings, never prohibitions: DC on a slave whose chip has no DC clock (it stays in PREOP with no status code), an AssignActivate the slave does not describe, DC off on a slave that only lists DC modes, a servo period below the slave's minimum, and more. Also from ecatsetup --check FILE with a master running.
  • Each slave's messages from the master on the Slave status page and in --diagnose; no CoE questions to slaves without CoE.

A capture of the bus, for a device the developer does not have (docs)

  • Save capture... on the Slave status page, or ecatsetup --capture: one file with every slave's identity, SII, object dictionary and values, PDO assignment, registers, the report, the ESI descriptions and, with tcpdump, a few seconds of frames. Take it while the I/O test runs to have the bus in OP. It only reads.
  • ecatsetup --from-capture FILE runs the proposal, --diagnose, --check and the window against a capture instead of the bus. --capture-c turns a capture into fake slaves for the component's C tests, with the process data of each cycle.

Documentation

  • Troubleshooting a slave: five questions and the steps to answer them.
  • New screenshots of the window, and scripts/docs-screenshots to take them again.

Also

  • The I/O test removes the folders of earlier tests from /tmp.

Tried: the DC checks on turner's bus (EK1100, EL1008, EL2008, EL5101, two ECT60); the master's messages there; captures of the plasma cutter's bus in PREOP and in OP (ecat in halrun, no enable), read back without the bus. Not tried yet on LinuxCNC 2.10: the new component in LinuxCNC itself (only in halrun), cutting with the arc, PV, zero-at-start, opmode-cmd, sync0-shift-ns: auto while moving, modular devices, analog terminals, the EL7041, drives with several axes.