Repository navigation
ecat ecat-v0.22.1
Pre-releaseecat for LinuxCNC 2.9 and 2.10: from this release the same ecat is built for both series. LinuxCNC 2.9 (2.9.4 or newer, Debian's or linuxcnc.org's packages) gets a package; 2.10, which has no Debian packages yet, gets the run-in-place archive and a package as before.
Install
First the userspace master, linuxcnc-ethercat-uspace 1.5 from MetalMusings/ethercat (unchanged since 0.21): sudo apt install ./linuxcnc-ethercat-uspace_*_amd64.deb. Then the file for your LinuxCNC:
- LinuxCNC 2.9 (2.9.4 or newer, as packages):
linuxcnc-ecat_*+lcnc2.9.debian13_amd64.deb(or.debian12). It replaces ecat 0.11. - LinuxCNC 2.10 run-in-place: unpack
ecat-rip-0.22.1-debian13.tar.gz(or-debian12) and run./install.ecat.sois built against LinuxCNC commit b0e7b191b9 (2.10.0~pre2-436); the installer refuses if your tree's HAL headers differ and says how to build from source. - LinuxCNC 2.10 package:
linuxcnc-ecat_*.debwithout+lcnc2.9.
The window, ecatsetup --gui, needs python3-pyqt5. To try ecat without disturbing your setup: getting started. See the README.
What is new in 0.22.1
ecatsetup --check names HAL names that are too long for your LinuxCNC. LinuxCNC 2.9 takes at most 47 characters in a pin or parameter name, 2.10 takes 55. A longer one (often a pin named after a long ESI entry) made the component refuse to load, with only "length 48 too long for name" in LinuxCNC's error window. --check and the window's check now say which pin and how long it may be, so you can give it a shorter name before you start LinuxCNC. Found when 0.22 was first run in LinuxCNC 2.9.
Tried in LinuxCNC 2.9.4 with motion (0.22 + this check): a plasma cutter with three Rtelligent ECT60 drives in CSP and an I/O board, 500 us servo period: homing, jogging, all slaves in OP, two cycles from output to status, no events while it ran.
What is new in 0.22
LinuxCNC 2.9. Everything up to 0.21 (tuning, feedforward, EoE, serial channels, unused slaves, the DC reference clock, From lcec, the window) now works on 2.9 too. The component is written against 2.10's HAL API; on 2.9 one header gives that API on 2.9's pins, so there is no separate 2.9 code. Where the series differ:
- Integer pins have 32 bits on 2.9 (64 on 2.10). Commands are held within the PDO entry's range anyway, so entries up to 32 bits behave the same.
- LINT/ULINT entries and the encoder's 64-bit count are
floatpins on 2.9 (exact up to 2^53).ecatsetup --checkrefuseshal-type: sint/uinton a LINT/ULINT entry on 2.9 and proposesreal;extendis for 8- and 16-bit entries only. - The same
ethercat.yamlworks on both, when its HAL names have at most 47 characters. - EtherCAT Setup finds the series by itself (HAL types, INI keys such as
HOME_SEARCH_DISTonly on 2.10, component names, LinuxCNC's pins).
ecat 0.11.x is closed. 2.9 users move to this package; 0.11 gets no more fixes.
Fixed: the 2.10 package lacked the shipped SYNC0 measurements (ecatsetup/measured/) since 0.20; the run-in-place archive had them.
Tried on 2.9.4 before 0.22.1: ecatsetup --check and the I/O test in the window on a plasma cutter's bus (three ECT60 drives and an I/O board): all slaves in OP, DC phased, two cycles from output to status, the drives without fault. Not tried on 2.9 yet: 2.9.5 to 2.9.10 (same HAL API), Debian 12.