Simple print file triggers 'ALL_HOME' followed by 'QUAD_GANTRY_LEVEL', but never actually prints | VORONDesign | Page 1

open raven May 29, 2025, 11:23 PM

#

I printed this little 3mm shim on my Prusa when I first started building my first Voron - a 300mm Voron 2.4 LDO (Rev D) kit. I'm now at the point where I have the extruder working, homing working, gantry leveled, and I'm trying my first print using this as a test part. I'm using Prusa Slicer with the Ellis_PIF_Standard_11mm3.ini (this .ini wouldn't load directly, so I created a 'custom' printer config in PS and edited it to be identical to the Ellis one).

Unfortunately, it doesn't actually print. The printer does a 'All Home', followed by a Quad Gantry Level, as if these were in the gcode (they aren't AFAICT), and then stops w/o printing. I looked at the file in Mainsail's gcode viewer and it looks OK. I looked through the log files looking for 'shim and found some in moonraker.log (attached), indicating something was wrong with the gcode file. Grok seems to think so too, but I have no idea what it might be. Any thoughts would be appreciated.

My intent in this test was just to see if the printer would actually print a simple model, so if someone has a 'known good' .gcode file compatible with a 300mm Voron 2.4 I'd love to try that to eliminate the Prusa Slicer variable. TIA

📎 Voron_2.4_Linear_Rail_Shim_V1.gcode 📎 Voron_Linear_Rail_Shim_V1.stl 📎 moonraker.log

shrewd relic May 29, 2025, 11:23 PM

#

are you using jontek2 a better print start macro?

#

if not you should consider it

#

upload a klippy log file

open raven May 29, 2025, 11:36 PM

#

Klippy log file. I'm a Voron noob, so I'm just following the 'startup' guide and all default stuff

📎 klippy_2.log

shrewd relic May 29, 2025, 11:37 PM

#

ok that print start is trash

#

implement this

#

https://github.com/jontek2/A-better-print_start-macro

GitHub

GitHub - jontek2/A-better-print_start-macro: This document aims to ...

This document aims to help you get a simple but powerful start_macro for your voron printer! - jontek2/A-better-print_start-macro

#

update your slicer settings per that site, then slice and try again

open raven May 29, 2025, 11:48 PM

#

working ... 😉

#

Made the changes... retrying...

#

Here's the updated .gcode file with (hopefully) the new start code

📎 Voron_Linear_Rail_Shim_v2.gcode

shrewd relic May 30, 2025, 12:03 AM

#

line 254

#

print_start EXTRUDER=240 BED=70 CHAMBER=0

#

looks good

open raven May 30, 2025, 12:03 AM

#

so, the printer is still doing a 'home all' and QGL...

shrewd relic May 30, 2025, 12:04 AM

#

did you remove ALL other print_start?

#

it should home all and qgl, every time

#

now its just doing it properly

open raven May 30, 2025, 12:04 AM

#

now that I thing about it, I guess my Prusa MK4 does the same thing ... sorta ; )

#

nope - errored out with Console = "extruder not hot enough" and "Extrude below minimum temps", but Prusa Slicer shows proper temps - same as before. As a test, I used the Mainsail console to set the extruder temp to 200C, and this worked fine. the command echoed in the console was "SET_HEATER_TEMPERATURE HEATER=extruder TARGET=200'

📎 klippy_3.log 📎 moonraker_1.log

shrewd relic May 30, 2025, 12:17 AM

#

then verify the slicer and the macro as per the site

#

did you copy in the info in the start macro in the slicer, for that slicer?

open raven May 30, 2025, 12:17 AM

#

#

Here's my PS 'start code' section

shrewd relic May 30, 2025, 12:18 AM

#

the config is wrong

#

where is the print start?

#

all i see is:


[gcode_macro PRINT_START]
gcode = 
    G32
    G90
    G1 Z20 F3000

#

remove that, and add the one fron jontek

#

the LAST one seen wins, so if you didnt r emove the original one, and did an include earlier, its overridden

open raven May 30, 2025, 12:21 AM

#

may not have saved the custom start code before slicing. Now working with Voron Linear Rail Shim V3.gcode (attached)

📎 Voron_Linear_Rail_Shim_V3.gcode

shrewd relic May 30, 2025, 12:22 AM

#

that is less important than having thge actual macro in config

#

the slicer is right

#

print_start EXTRUDER=240 BED=70 CHAMBER=0

#

the config is wrong

#

remove the old one, add the proper one

open raven May 30, 2025, 12:23 AM

#

aha - didn't execute that step. working.... 😉

shrewd relic May 30, 2025, 12:24 AM

#

that is the issue

open raven May 30, 2025, 12:29 AM

#

New printer config. Don't have nevermore installed, don't know about beacon, so left those commented out

📎 printer.cfg

shrewd relic May 30, 2025, 12:29 AM

#

as you should, if you dont have those things

open raven May 30, 2025, 12:29 AM

#

OK, now I'm getting action on the print bed temperature - yay!

shrewd relic May 30, 2025, 12:30 AM

#

you dont mesh?

open raven May 30, 2025, 12:30 AM

#

not yet - my assumption is that's not needed for first trial print. Bad assumption?

shrewd relic May 30, 2025, 12:30 AM

#

no, thats fine.

#

but you know how to adjust once yhou add it

#

just ujncomment those things

open raven May 30, 2025, 12:31 AM

#

yep

#

bed is up to temp, but 'State' is bouncing around, and no extruder action yet

#

spoke too soon. Extruder just fired up, but target is only 150C

#

what do the 'State' percentage values mean?

#

looks like the printer is doing another QGL

#

QGL done - extruder set to 240C

#

and... Printing! yay!

#

Thanks for your help Eric - this makes my day for sure 😉

open raven May 30, 2025, 2:31 PM

#

BED_MESH_CALIBRATE & BED_MESH_CLEAR produce 'Unknown Command' errors?

#Simple print file triggers 'ALL_HOME' followed by 'QUAD_GANTRY_LEVEL', but never actually prints