Troubleshooting¶
Error during homing z: Eddy current sensor error¶
You might need to adjust your reg_drive_current, for more details:
https://github.com/bigtreetech/Eddy?tab=readme-ov-file#sometimes-i-get-error-during-homing-probe-eddy-current-sensor-error
MCU Protocol Error - mcu 'eddy' Unknown command: debug_read¶
If you get the following error, it means that the eddy is not connected to the printer. This is either because its physically not connected, the wiring is wrong, the usb subsystem has disconnected the eddy during a restart or the serial id is wrong
So from ssh run a lsusb and make sure you can see:
If you cannot see it in lsusb, then it very likely means either the eddy is wired incorrectly, or if was working, it just means that an attempt to restart the eddy failed because the K1 refused to recognise it, there is no recourse except to restart the host via Fluidd / Mainsail (or power cycle the printer)
If you can see the eddy in lsusb, then you should try to update the serial (see next)
Manual BTT Eddy Serial Device configuration¶
You can run the following command to fix your serial if you forgot to plug your btt eddy in during the installation or update:
Note
If you run the above and receive an error like:
```
root@K1Max-AF34 /root [#] ~/pellcorp/installer.sh --fix-serial
-sh: /root/pellcorp/installer.sh: not found
```
It means you are on an older version of Simple AF and you should instead use the old style commands:
```
/usr/data/pellcorp/k1/installer.sh --fix-serial
```
Eddy is not connected, aborting homing Z¶
If you see this error when trying to home your printer, it is a clear indication that the eddy was disconnected and
you should look for a mcu 'eddy' disconnected error in your klippy.log or gcode console, if the eddy was momentarily
disconnected (so if you run lsusb on the printer the eddy shows up), you can simply restart klipper from the services
menu in Fluidd or Mainsail, if the eddy completely disappeared you will need to power cycle the printer!