Adaptive Mesh and Orca Slicer
Hello,
I've activated adaptive_mesh in the printer.cfg ([gcode_macro RatOS]
variable_adaptive_mesh: True) and added the start Gcode to Orca Slicer. However, it still probed the whole bed.
Now I've seen, that the gcode does not contain X/Y coordinates but rather the variables:
"; machine_start_gcode = START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single] X0={first_layer_print_min[0]} Y0={first_layer_print_min[1]} X1={first_layer_print_max[0]} Y1={first_layer_print_max[1]}
"
The variable "first_layer_print_min" is not defined anywhere else in the Gcode, so I assume that's the reason it is not working.
Can anyone tell me, how I can fix this?
13 Replies
Show me a screenshot of your machines start gcode from OrcaSlicer
It should look like this (this works)
What you've pasted is a gcode comment, not actual gcode
quickest-silver•16mo ago
test also the new mesh have used pam until now.
if the new acuh only scans a small area like pam, it always does the whole area for me
Did you enable it? Did you update RatOS? Did you pass it the coordinates from the slicer like it says in the docs? What does the console say?
quickest-silver•16mo ago
Got it working now thanks, had to restart raspi for whatever reason
like-gold•16mo ago
This is what mine looks like
like-gold•16mo ago
I found the right line in the Gcode now: "START_PRINT EXTRUDER_TEMP=260 BED_TEMP=105 X0=124.774 Y0=179.94 X1=275.226 Y1=220.06
"
So the Gcode seems to be correct
In the printer.cfg I have the following entry:
[gcode_macro RatOS]
variable_adaptive_mesh: True
And RatOS is updated?
like-gold•16mo ago
like-gold•16mo ago
I am currently printing, that's probably why they are greyed out
So I guess I have to update
Yeah you're are way out of date, that's why it's not doing anything 🙂
(it doesn't exist in the code on your pi)
like-gold•16mo ago
Great thank you 🙂