Internal error on command:"PREP"

General Discussion
1

Basic Information:

Printer Model:Voron 2.4
MCU / Printerboard: 2-SKR 1.4 controllers, EBB SB2209 USB V1.0, AFC-Lite V1.1
Host / SBC: BTT pi
klippy.log

klippy (2).log (4.0 MB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I updated AFC and Klipper, Klipper Screen, and crowsnest. I am now getting errors on startup. I managed to boot Klipper if I comment out [include AFC/*.cfg] in the printer.cfg.

Internal error on command:"PREP"

I just noticed that there’s an update to steppers for stm32h723 (manta m8p and ADC-lite) could that be the cause?

2

It seems that PREP command does not belong to Klipper.

Git version: 'v0.13.0-193-gbcd451095-dirty'
Untracked files: klippy/extras/AFC.py, klippy/extras/AFC_BoxTurtle.py, klippy/extras/AFC_HTLF.py, klippy/extras/AFC_NightOwl.py, klippy/extras/AFC_QuattroBox.py, klippy/extras/AFC_assist.py, klippy/extras/AFC_buffer.py, klippy/extras/AFC_button.py, klippy/extras/AFC_error.py, klippy/extras/AFC_extruder.py, (+14 files)

You may ask those authors.

3

the command is used to PREP the Armored Box Turtle using an AFC-lite board with btt 2209’s

System was working fine until update.

4

From the link in my last post.

Update Implications

Another very important aspect is that Klipper’s internal methods are not guaranteed to remain stable. As a result, Klipper’s internal functions may change with each update. This can easily lead to a non-functional system (errors at startup) or some hard-to-diagnose unexpected behavior after an update.

The main-line development has no control over this, so the authors of modifications are fully responsible for keeping their changes in line with Klipper’s current development.

5

I don’t use BoxTurtle.
You’re not alone.

But, as Eddy stated, this is the wrong place to ask for help. I would contact JacquesRooswinkel. Maybe both of you can figure it out.

6

performed a roll back.

cd ~/klipper
sudo service klipper stop
git checkout 126275d1f
sudo service klipper start

verified 2209 uart address was 0.

Everything is working.

7

You should post your experience as a reply to the “issue report” linked above at github. The devs might be waiting for conformation that Klipper updates break their addins.

8

The main devs of both AFC software and Happy Hare are aware of the changes and announcements have been posted to both their Discord servers, along with instructions to roll back to a previous Klipper commit until the software can be updated for the new Klipper.

9

Armored Turtle discord provided a helpful solution.

10

So the rollback was his solution?

11

Affirmative.

12

So the author tells the users to downgrade Klipper (and missing improvements) instead of fixing his code.

13

Both HH and AFC devs are working on a an update to work with the new Klipper version, but while they work on the update, the current solution is to downgrade Klipper.

I looked into this when the issue first arose and the entirety of the motion code was pretty significantly refactored. The devs of both HH and AFC are, of course, doing this for free, so they have time constraints just like the Klipper team.

These changes also came out only a week or so ago, so it’s still pretty early to expect a fix.