EtherCAT stopped working after Reboot

Hello,
I've followed rodw instructions for installing EtherCAT on a Pi 4 with the 2.9.2 Pi OS, afterThe activity lights on the Pi and the servo driver ethernet ports started blinking.recognized the servo driver, and all is good so far, but after I created the udev rule and rebooted the EtherCAT seemed to stop working.
Now returns "Failed to obtain number of masters: Failed to open master device /dev/EtherCAT0" No such file or directory" I've looked at the /dev folder and the EtherCAT0 file that was there before the reboot was gone and the activity lights on the Pi and the Servo driver stopped blinking.
Did not return any error and 
returned this


I'm new to LinuxCNC and Linux in general, please let me know what command to run or what logs to get to help diagnose this, Thank you!

 

Sounds like you forgot the udev rule to load on startup. PLease read carefully.
forum.linuxcnc.org/ethercat/45336-etherc...-how-to-step-by-step

Hello rodw, thank you for the reply.

I've followed your instructions and did not forget to add the udev rule. I've checked after a reboot, the rule file and it is still in the /etc/udev/rules.d folder.

Edit:

I've tried following your instructions on an old desktop computer and there was no problem after a reboot. Maybe it's something to do with Pi or Pi OS?

Hello dear members, I reinstalled it maybe 50 times and when it restarted, ethercat master raspberry pi 4 8gb ==== Failed to obtain number of masters:
Failed to open master device /dev/EtherCAT0" No such file or directory
There is no problem before restarting, it sees the server, everything is fine. Is this a raspberry pi problem?????
I tried many times before writing here, no matter what I did, Linuxcnc 2.9.2 Rasberry Pi is installed, please help.

This is exactly the same problem I had on the same 8 GB Pi 4, I've given up on the Pi and switched to an old desktop PC without this problem.

  Please help me, there is no way I can solve this myself, as it can be seen now, ethercat is working, if I start it again, I have to install it again and again, please.

If it's not working at boot but it does work after re-installing, then either the permissions in /dev are wrong or the module isn't getting loaded.

So, after rebooting, try `ls -l /dev/EtherCAT*`. Does that show anything? Are the permissions `rw-rw-rw-` or `rw

---

`? If the file exists, then you just have a permissions problem. Run `sudo chmod 666 /dev/EtherCAT*` to fix for this session and then share your udev rule so we can figure out why it's not working.

If there are no /dev/EtherCAT* files, then something's wrong with the underlying kernel module. First, let's see what systemd thinks: `systemctl status ethercat.service`. That *should* say something like this:

If it says that it's not running but there's no error then run `sudo systemctl enable ethercat.service` and `sudo systemctl start ethercat.service`, then re-verify that permissions are right, above.

If there's an error, then it's *probably* something related to the module not being available. Try `lsmod | grep ^ec_`. It should list `ec_master` and one other `ec_` module, depending on your Ethernet driver in the EtherCAT config file. If they aren't there, then try `sudo modprobe ec_master` and report the error that you get.

Also, try running `sudo apt install -y linux-headers-$(uname -r)`; if your kernel was upgraded recently, then there's a decent chance that you're missing one of the components needed to recompile the EtherCAT module, and that will fix it until the next kernel upgrade.

They went out. is this? Can I provide enough information? Again, the results are as follows: ethercat is not connecting. The file path in the installation file is not /dev/EtherCAT* files =sudo geany /etc/udev/rules.d/99-ethercat.rules[img]chrome-extension://bpggmmljdiliancllaapiggllnkbjocb/logo/48.png[/img]