#greetings from a new voron owner, with some issues.

33 messages · Page 1 of 1 (latest)

gleaming wasp
#

i recently purchased a printer from the original builder, a voron 2.4 350mm LDO kit. this unit has a klicky probe, a back left nozzle brush, and a z axis probe.

if i didnt build this printer but the previous owner never registered a serial number, am i able to get one anyway?

second question, and the more important one: i had a bed crash yesterday while trying to do some firmware modifications.

previous owner had no nozzle cleaning and i wanted it to. i used the very unhelpful chatgpt to help me configure a few things on it and tried to do a test print after these mods. i printed a few things prior to this so i know the printer works. i adjusted the ab belts with the prusa website on my phone.
i set up my print start macro to heat the nozzle,do a z probe, brush, then recheck z incase there was a blob or oozing present (i thought this might keep from potentially crashing into the brush) i realise that i dont need to do the first probe now but thats how it was. so everything went well, z probed, nozzle brushed, then when it went to recheck the z it missed the probe and crashed into the bed and i couldnt stop it in time to not drag the nozzle into the bed for the purge line. so now i have a nice gouge in the buildplate where the nozzle hit. i took the cover off the toolhead and made sure it didnt break anything and it appears that all is good. (if all is not good then im screwed cause i do not have another printer to reprint broken parts)

i will include my printer.cfg and macros.cfg once i figure out how to.

gleaming wasp
#

i had no idea chatgpt was so hated on here. someone told me that its useful for coding so i thought id give it a try. it does suck, i learned this on my own.

vocal tundra
#

I've got a similar setup, so if I get mine working, I'll let you know.. ChatGPT is the devil, FYI.. LOL ;P

#

And you're not screwed IF something broke, as there are ppl here that are able to PIF for you.. Just has a lil fee to it for materials, time, etc..

fathom axle
#

It also looks like there's a bunch of stuff thats been configured using the save_config section, which isn't reccomended since it makes tracking down things even more difficult

gleaming wasp
#

I can post a klippy file but idk if itd be the right one or cover the error if that makes sense

fathom axle
#

klippy.log includes your config as it was read in by klipper, so its far more useful than your raw config files.

gleaming wasp
#

Ok give me a sec ill load up what i got

fathom axle
#

If it was never registered for a serial you can get it registered to you afaik

fathom axle
# gleaming wasp Ok give me a sec ill load up what i got

Alright so I'm almost going to suggest you rebuild this config from scratch and use a more standardized default config because its doing some pretty bizzare stuff that's probably going to throw you for a loop if this is your first klipper machine. I'm also not entirely sure what chatgpt did to your print start routine but its set up to do a bunch of stuff bizzarely redundantly

gleaming wasp
#

Where do you suggest i start?

fathom axle
#

Like its loading some preset bedmeshes from the save_config section, promptly clears the saved bedmesh, runs a full plate calibration, then runs ANOTHER adaptive plate calibration???, saves the adaptive mesh to a named profile which you don't want to do since its an adaptive mesh???, preheats, rehomes Z then cleans the nozzle which is out of order?

#

I mean its really mangled

#

What I'd probably do that will both get you going, and familiarize yourself is use a stock LDO config for your machine. You should be able to transpose most of the settings, but I'd redo any of the initial setup for finding the Z endstop and stuff yourself so you know the values are good.

#

If you've got a LDO 350 kit with a klicky its probably a Rev C kit with a klicky addon.

#

Depending on your comfort level it might also be worth making a #request_help ticket so the helping crew can give you pointers along the way?

#

Its just really hard to get a grasp on someone else's configs that have also been messed up with chatgpt. You might be able to get it working, but you might also end up chasing gremlins forever or damaging something.

gleaming wasp
#

Ive already had a crash so i definitely dont want thay

gleaming wasp
#

are there a few things i can transfer over from my old messed up setup, like esteps, pid settings, ect?

#

to save a little time with setup>

gleaming wasp
#

im getting erros i never had before about sections that seem to be the same from the last setup

#

most recent i have yet to figure out is "Option 'lcd_type' is not valid in section 'board_pins'"

fathom axle
gleaming wasp
#

Existing command 'BED_MESH_CALIBRATE' not found in gcode_macro rename

#

current error im trying to fix

fathom axle
#

sounds like you've just got some comments out of order or something

#

stuff getting read in as part of stuff they shouldn't belong to

crimson cove
crimson cove