Solved-Start Gcode
I noticed that the default Start_print routine does the following before every print (memory may be out of order):
1) home all axis.
2) z tilt adjust
3) mesh the bed
4)heat up the bed
5) then heat up the hot end
6) prime a blob of filament
7) print part
I’d like to adjust things so that:
1) printer just loads a pre-scanned mesh so it doesn’t need to mesh again
2) sets the bed and extruder at the same time at very beginning. Before home all. Just waits for temps to hit target before prime blob.
Is there an easy way to do this?✌️
23 Replies
1) https://os.ratrig.com/docs/configuration/macros#bed-mesh-calibration
2) You don't want to heat the nozzle to it's full printing temp before you've done z_tilt adjustment, it'll ooze everywhere. Furthermore, the start_print macro is currently timed so that starting a print results in consistent behavior.
It goes
1) home
2) heat bed
3) heat extruder to 150 (or otherwise configured nozzle preheat temp). The time this takes allows the heat to spread within the bed (more time would actually be better, rapido is too fast).
4) z_tilt
5) mesh
6) Park extruder and heat to print temp
7) Prime
8) Print.
Configuring RatOS Macros | RatOS
RatOS comes with a bunch of flexible predefined macro's that can be customized via variables and macro hooks.
Also, consider adaptive_mesh instead of disabling bed_meshing altogether, it's more reliable.
Thanks for reply. I’ll read thru macros docs. Sounds like any flexibility will be in there (start print macro). Why does one need to mesh before every print? If the bed mounts allow for minimal thermal shifts, wouldn’t you mesh basically remain the same regardless of temp? ✌️
Yes, it should, if everything is at the same temp each time you print (frame, ambient, bed, nozzle, probe) as it was one you made your mesh.
But with adaptive_mesh and fast probe/mesh settings it takes seconds to mesh, there's no point in skipping and compromising reliability.
Also bed shape changes ever so slightly over time (compounding factors from frame, connectors, fasteners, toolhead, rails, gantry etc etc).
So what it comes down to is reliability and confidence in hitting that start button vs shaving around a minute off of the START_PRINT procedure.
Got it. Thanks for the details. I also see the variables for skipping and naming a pre mesh in the macro docs. Thank you.
Regarding KAMP things, I think it’s not compatible with Beacon? I’m temporarily running a QuickDraw until the new Beacon drops next month.
It is, it just won't prime (will be fixed soon ™️ ).
Oh. Sweet. Thanks. Guess I should go to Kamp then. 😁✌️
Just to clarify KAMP is a klipper plugin which isn't RatOS compatible, RatOS comes with it's own adaptive mesh implementation.
(just in case you were gonna go try and install KAMP 😅)
Oh. Man. Thanks for saying something. I was going to do exactly that. So you’re prob going to say RTFM again?😁
Good i mentioned it then! Well yes 😂 just look for Adaptive Mesh in the macro docs
full docs here https://os.ratrig.com/docs/configuration/adaptive-meshing
Adaptive Meshing (BETA) | RatOS
RatOS comes with it's own adaptive meshing (functionality was previously handled by PAM by Helge Keck), similar to KAMP. When enabled and configured in your slicer, RatOS will only probe the print area and your configured probe location, potentially saving a lot of time on smaller prints on bigger printers. RatOS will keep the resolution of your...
As always. Thanks for speedy replies. And thanks for putting in all the work. I thought I was going to want to scrap ratos and do a custom raspi lite install, but the more I use rat os the more I like all these “EZ” setups. 😁
My pleasure! 🙂
2.1 should make it an even better experience 🤞
The initialization time on boot up is a tad slow. But other than that it’s been really great so far.
2.1 in dev?
Yes latest update from last night: https://discord.com/channels/582187371529764864/859890291591217162/1175645180309798932
I never power off my pi, so i guess i never really noticed. Disabling klipperscreen may help with that.
I’ve been scared to update anything. I’ve had 3 day fix sessions with other machines. And wasn’t sure about this new build. First time using ratos. First time in mainsail. Or crows nest and a few others. So… I go slow with updates.
Thanks. I’ll disable the kscreen. I have a web client for interface. Didn’t even put at mini display on this one.
Maybe a raspi5 will speed things up. 😁
Oh yeah, 2.1 isn't released yet, so you won't get that one anyway.
Generally i'd say update once you install, then don't update again unless there's something you know you want or there's a notification telling you you should
Not supported yet, still need to get my hands on one. I'm afraid that one may take some time, haven't looked into it yet.
on the other hand my RPi 4 is bored, so i don't really see a need for a Pi 5 😄
like:
Yeah. Same over here. My raspi lite builds are just so fast to boot. Klipper and Fluidd and moonraker. Not much else. I think it’s like 30 seconds on a 4b
A minimal installation will always boot faster. There's no way around it. That's just the price of convenience.
You know what's even faster though? Not booting at all, just let it run 😅
Yeah. Maybe I will once the machine is up and running at 100%. I’m still tuning a bit.
First print. 250mms@10k. YOLO. 😁
Mouse on Estop
Thx again for the help! 🙏
PA and SCV might still need some work. But for a first go I’m really pleased with the minimal Z banding and line quality. I think that was 0.36 LH too. Anyway. I’ve had much worse first prints. 😊👍
@miklschmidt <:ratrig_heart:1064311078290456727> adaptive mesh implementation. 
👍
👍