You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After recently installing and using the new Beacon RevH probe, I noticed that during START_PRINT the printer skips the priming procedure after the Beacon does its bed mesh probing. I haven't changed anything in my printer.cfg other than the beacon config.
I'm up to date with all my packages and files at the time of this post.
This is what I have currently:
[gcode_macro RatOS]
variable_relative_extrusion: True
variable_preheat_extruder: True
variable_calibrate_bed_mesh: True
variable_adaptive_mesh: True
variable_nozzle_priming: "primeblob"
variable_start_print_park_in: "back"
variable_start_print_park_z_height: 30
variable_end_print_park_in: "back"
variable_pause_print_park_in: "back"
variable_macro_travel_speed: 300
variable_safe_home_x: "middle" # Possible Values: 'middle' or an absolute x coordinate
variable_safe_home_y: "middle" # Possible Values: 'middle' or an absolute y coordinate
What did you expect to happen
After probing, START_PRINT should go into priming such as PrimeLine or PrimeBlob but doesn't.
How to reproduce
Run a print with START_PRINT macro with latest versions of the Beacon and RATOS.
Additional information
No response
The text was updated successfully, but these errors were encountered:
What happened
After recently installing and using the new Beacon RevH probe, I noticed that during START_PRINT the printer skips the priming procedure after the Beacon does its bed mesh probing. I haven't changed anything in my printer.cfg other than the beacon config.
I'm up to date with all my packages and files at the time of this post.
This is what I have currently:
[gcode_macro RatOS]
variable_relative_extrusion: True
variable_preheat_extruder: True
variable_calibrate_bed_mesh: True
variable_adaptive_mesh: True
variable_nozzle_priming: "primeblob"
variable_start_print_park_in: "back"
variable_start_print_park_z_height: 30
variable_end_print_park_in: "back"
variable_pause_print_park_in: "back"
variable_macro_travel_speed: 300
variable_safe_home_x: "middle" # Possible Values: 'middle' or an absolute x coordinate
variable_safe_home_y: "middle" # Possible Values: 'middle' or an absolute y coordinate
What did you expect to happen
After probing, START_PRINT should go into priming such as PrimeLine or PrimeBlob but doesn't.
How to reproduce
Run a print with START_PRINT macro with latest versions of the Beacon and RATOS.
Additional information
No response
The text was updated successfully, but these errors were encountered: