#Performed Soft Recovery of Klipper, now getting error on startup

26 messages · Page 1 of 1 (latest)

proud nymph
#

Specifically the error is "Option 'split_delta_z' in section 'bed_mesh' must have minimum of 0.01". The only thing I changed in Klipper was raising the Neopixel limit. No idea why its failing now

📎 klippy_4.log
blazing charmBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

proud nymph
#

@willow knoll I'm not the one who originally had the error, but I didnt see them post a ticket. The same thing is happenning to me

proud nymph
#

note. adding this into the ratos.cfg as a workaround now fails with the error of 'Error loading kinematics 'ratos_hybrid_corexy'
'

willow knoll
#

@proud nymph please share a debug zip

#

And can you tell my why you performed a soft recovery of klipper?

proud nymph
#

Sure. That may take me a few hours as I got to work. The recovery was because when I tried to update klipper after I updated neopixel.py it failed

willow knoll
proud nymph
#

I had to raise the limit of neopixel lights. (I was using a board that I know can support higher amounts). I changed the limit from 500 to like 650 or something

willow knoll
#

So you manually edited the neopixel.py file on the pi?

proud nymph
#

yeah. I have no idea why that would affect the bed mesh though. that number was the only thing I changed.

willow knoll
#

RatOS uses a custom fork of klipper. It would seem that your soft reset (or some action you've not mentioned) switched klipper to the stock version or similar (I can't tell exactly what without seeing the debug zip). One of the changes in the custom fork is to allow smaller split_delta_z values.

#

So you should do the following:
ssh to the printer, then run:

ratos doctor

Then check that there are no errors.

Then, edit neopixel.py. This will make klipper show up as "dirty" in the mainsail update manager - because that's the truth, your klipper install is indeed now dirty. You will have to live with this. Your changes might get squashed by a future ratos update, or your changes might stop a future ratos update from working.

proud nymph
#

I suppose theres no way to write this change to a config file so I dont have to make the repository updates manually?

willow knoll
#

not unless the neopixel module offers it as a configurable setting. checking...

proud nymph
#

I believe its hard coded into klipper unfortunately.

willow knoll
#

yes, it is. MAX_MCU_SIZE. This is a klipper limitation.

#

maybe use one of those esp32 wled modules instead. I'd ask in #leds-and-automation , it's not something I've played with.

proud nymph
#

yeah. I was using a RP2040 that was laying around. Unfortunately they dont support WLED. I was doing another project that involved LEDs in the past, so I have a lot of experience with the neopixel lights

#

But I'll try the ratos doctor command as soon as I can

proud nymph
#

looks like the doctor failed

willow knoll
#

yeah, it noticed that there were uncommitted changes and did not want to stomp your changes.

#

I'd normally say to back up your change, but it's just tweaking one number at the top of the file so probably not worth "backing up". So ssh, then:

cd ~/klipper
git checkout .
cd ..
ratos doctor
ratos logs update-logs show
proud nymph
#

looks like that brought me back up. thanks!