Repository navigation
ecat ecat-v0.23.1
Pre-releaseA bug-fix release for LinuxCNC 2.9 and 2.10: CiA 402 drives whose process data has no operation mode (such as the StepperOnline A6 with its default PDOs), and help for drives that will not stay enabled because frames are lost.
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). - LinuxCNC 2.10 run-in-place: unpack
ecat-rip-0.23.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.
Moving from the IgH kernel master (EtherLab)? Stop it and keep it from starting before you use the userspace master: sudo systemctl stop ethercat; sudo systemctl disable ethercat, and restart the computer if lsmod | grep ec_ still lists modules. Two masters on one network card take each other's frames.
The window, ecatsetup --gui, needs python3-pyqt5. See the README and getting started.
What is new in 0.23.1
Fixed: CiA 402 drives without the operation mode in their process data. The StepperOnline A6's default PDOs (0x1701/0x1B01) have neither 0x6060 (mode) nor 0x6061 (mode display). The cia402 profile then enabled the drive in whatever mode it had (0, no mode), and the drive dropped out of "Operation enabled" at once. Now the profile writes the configured mode by SDO when 0x6060 is not mapped, reads it back, and the master writes it again at each configuration; a drive that refuses the mode stops the load with a message. (cia402)
Fixed: EtherCAT Setup proposed generic for the A6. Its ESI gives the CiA 402 profile as Profile/ChannelInfo/ProfileNo, and the drive has no SDO information, so 0x1000 was never read. 0x1000 is now read from every CoE slave, and the ESI's dictionary decides what else is read. Propose again on the slave page turns a generic entry from an older version into cia402.
New: "What this means" for the event log. When the event log shows working counter zero while running, or the master's skipped, unmatched or timed-out datagrams, the Event log card on the Troubleshoot page starts with what it means (in such a cycle ecat shuts every drive down, which is why a drive reaches "Operation enabled" and falls back) and the usual causes, each judged on this computer: likely, possible, not checked (with how to find out) or ruled out. The causes looked at: the IgH kernel master still loaded or enabled for the next boot, the servo thread late, no PREEMPT_RT kernel, no isolated CPU, Energy Efficient Ethernet on the card, the card also carrying the LAN, the card's interrupt, a Realtek (r8169) card, and a cable or a slave's power. The same text is at the top of the report and after ecatsetup --events. (docs)
The report holds more of what decides whether frames get through (Save report... or ecatsetup --report): the EtherCAT masters on the computer (the IgH kernel master's device, modules and ethercat.service, free userspace masters, LinuxCNC), the running master's own status with its lost-frame counter, the transport, the computer as the real-time check reads it (kernel command line, isolated CPUs, network cards with driver, EEE and coalescing, ...), and where EtherCAT Setup runs from (a run-in-place archive's version). Disk UUIDs on the kernel command line, MAC addresses and your home folder's name are left out of the whole report.
Tried before the release: the A6 fix against a simulated A6 (an EaserCAT 3000 board acting as the drive, with the A6's identity, PDOs and missing SDO information) on a real bus; "What this means" and the report on this machine's own event log and bus. Not tried: a real A6 (a user is about to).