#I bought an older voron 2.2 that had not been used since 2022, it worked fine then i updated it

69 messages · Page 1 of 1 (latest)

river bane
#

I now get this error message

Internal error during connect: PrinterProbe instance has no attribute 'sample_count'

I have my config attatched

📎 message.txt
silent umbra
river bane
silent umbra
#

Mainsail has a rollover logs button that could probably help with that

#

But messy is also fine. I think i can scroll past some out of date chaos

river bane
#

Im most likely just going to swap to an octopus pro v1.1 that have here
its running 2 skr boards but im very new to klipper, have only made configs for my cr10 s4 and s5 and thats very simple compared to the voron

silent umbra
#

Hmm, interesting

#

Did you remove a [probe] section?

river bane
#

I tried that as a fix

#

But it didnt help

silent umbra
#

Okay, the (different) error that caused is the most recent one in this log file you posted

river bane
#

Internal error during connect: PrinterProbe instance has no attribute 'sample_count'

This is the main error, i reverted back to the original config file

silent umbra
#

Could you put the section back in, restart klipper, then grab a fresh log?

river bane
#

sure, 1 moment

silent umbra
#

Yep!

#

And it helped

river bane
#

It was so nice when it was printing, did my first really fast benchy, then i hit update and its cooked

silent umbra
#

I can now see that the error is coming from the z calibration plugin

river bane
#

Ah

silent umbra
river bane
#

I was trying to fiddle with that as i saw in a thread but got lost

silent umbra
#

I believe you need to update that as well

#

Should clear the error

river bane
#

How do i do that, i have seen like 3 diff ways to do it and i dont wana mess it up lol

silent umbra
#

Is it not in your updater?

river bane
#

nope

#

I have updated everything on the printer, took ages to do

silent umbra
#

Then i would just run through the install instructions here:

river bane
#

Alright, gimmi 5

silent umbra
#

I should warn you, i think some config settings for that plugin have changed as well

#

So there may still be some tweaks to do after

#

But step 1 is still gonna be updating it, then we'll see what we've got

river bane
#

I am so new to programming, im never sure if i skipped something or there an issue lol

image.png
#

wait

#

i realize, i need to ssh
its really late

#

Well, i realize now, i cant log into the pi, as i bought the printer like this, i dont know username or pass

#

LMAO

#

i guessed it

silent umbra
#

We generally recommend backing up the config files, and then wiping second hand pis

#

Just as a common sense security measure

river bane
#

yee, i was going to do that. Only had it like 3 days,

silent umbra
#

Fair

river bane
#

I think we good ?

image.png
#

It then did this, should i carry on with this ?

image.png
silent umbra
#

Yep

river bane
#

its alive

#

Lemme heat up nozzle and see if it moves around

#

Error on 'SET_VELOCITY_LIMIT ACCEL_TO_DECEL=': unable to parse

#

Doesn't want to home z

silent umbra
#

Ah!

#

So there's a macro someplace (klicky macros Maybe?) Using the old "accel_to_decel" setting

#

You'll need to get rid of that

river bane
#

Ahh, yes
There are alot of clicky files

silent umbra
#

The good news is, the stuff that replaced it just works, without any intervention. So all you need to do is get rid of whatever is trying to set it, and the rest will take care of itself

river bane
#

Should i # out this whole block ?

image.png
silent umbra
#

Just the one line

river bane
#

cool

silent umbra
#

The ones above and below still apply

river bane
#

and it homed

#

I think that will be it for tonights fixing, i will prob find more issues tomorrow, but its nearly 2:30 lol

Im going to mark this as solved

#

I really appreciate the help

#

I would have taken me days to figure out that lol

silent umbra
#

No problem

river bane
#

enjoy the rest of your day/night

silent umbra
#

I've got a bit of evening left

#

Go sleep though!