#18 minute delay from print start to first layer start?

1 messages · Page 1 of 1 (latest)

white beacon
#

Voron/Klipper noob: Trying to get the first layer settings for my newly built Voron 2.4 LDO Rev D kit. Even with a very minimal printer.cfg (attached), it takes 18 minutes from the time I upload the .gcode for printing to the time the prime line is created. That seems like a lot compared to my Prusa MK4 which takes about 5 minutes from start to first layer print. I thought I could browse through the Klippy log and figure out what happened, but I couldn't make any sense from the Klippy.log contents. Any help would be appreciated.

📎 printer.cfg 📎 klippy_5.log IMG_6126.png
jovial patio
#

Your printer is heating up because of this part in the PRINT_START macro I suppose.

BED_MESH_CLEAR                                       # Clear old saved bed mesh (if any)
    SET_DISPLAY_TEXT MSG="Bed: {target_bed}c"           # Display info on display
    #STATUS_HEATING                                      # Set LEDs to heating-mode
    G1 X{x_wait} Y{y_wait} Z15 F9000                    # Go to center of the bed
    M190 S{target_bed}                                  # Set the target temp for the bed
    SET_DISPLAY_TEXT MSG="Soak for 5 min"               # Display info on display
    G4 P300000                                          # Wait 5 min for the bedtemp to stabilize
#

It takes time to heat the bed and then it waits 5 minutes. Look at messages in the console to check that.

#

let me check klippy log

candid zinc
#

For turning/troubleshooting I comment out the G4 line you skip the 5 min heat soak

jovial patio
candid zinc
#

I'd would also change that bed mesh to 5,5 instead of 5,3.

icy geyser
#

U have another Post already

icy geyser
white beacon
# jovial patio Can you roll over your logs (blue button where you would normally download your ...

Sorry, didn't think of it as the same issue. Before I was confused as to why Ellis' 'better PRINT_START macro had calls to 'STATUS_MACROS', and the status macros had the same calls to time-consuming processes. So I stripped all that out so there was no possibility of duplications. I thought that would dramatically reduce the delay from print start to first layer, and I guess it did - but not as much as I thought it would. So my real question now is this. "Is an 18 minute delay normal for Voron printers?". BTW, thanks for the tip about rolling over the logs - that will make things a lot easier. I"m actually a little surprised the Klippy log isn't time-stamped - or is it and I just missed it?

jovial patio
#

And everything depends on your configuration when it comes to time needed to start the print.

white beacon
#

Here is the Klippy l og from a single print of a 100x100 single layer patch, and I think the delay from start to first print was around 12 minutes.

📎 250601_GoodPrint_klippy.log
jovial patio
#

everything adds up for me if I'm not mistaken

5 minutes for heatsoaking (g4 gcode in the print start macro)
3 minutes for qgl and bed mesh
1 minute to heatup bed from 70 to 85 degree
0,5 minute to heat up hotend
and the rest for some other stuff

#

you can cut some time on qgl and bed mesh as it takes quite a lot of time. what kind of probe are you using?

#

and as for the question Is an 18 minute delay normal for Voron printers? the answer is, as always, depends.

#

there is some mandatory stuff you have to do like properly heat up a chamber when you are printing with asa/abs/etc, make bed mesh and qgl (the speed depends on probe you are using). it is not voron feature that it takes so much time but more like how physics works. you can cut some time here and there by changing some parts, by adding bed fans, but at the end you must wait for the chamber temperature anyway.

white beacon
#

I'm using the Omron TL-Q5MC inductive probe that came with the LDO Rev D kit. Yeah, I realize that physics doesn't care what I think 🙂

#

I have another, unrelated issue I'm trying to work (first layer print and Z position_endstop problems). Start another help topic?

jovial patio
#

I would get rid of this inductive probe tho and go with klicky / eddy

#

it will produce better results and will shorten the time needed for qol and bed mesh

#

what kind of issue do you have with z endstop?

#

and about first layer issue I would create new topic as it is quite different than print delay stuff

white beacon
#

I suspect that's what I'll do, based on other discussions here. I went this way because that's the default from LDO kit and I didn't want to complicate matters right at the start. LDO provides a 'klicky probe kit', and I had planned to do that, along with the Nevermore filter once I got basic print capability going

#

Thanks for the advice; I'll start a new topic on the first layer issue. I REALLY don't want to get crosswise with this discord, as everyone's help here is the only reason I've gotten this far 😉