Rubby
Rubby
PostsComments
RRCRat Rig Community [Unofficial]
Created by Rubby on 11/22/2024 in #ratos-support
RatOS Heat Soak Macro Help
I am looking to create a simple warm up macro that I can run at the start of the day to get my printer warmed up to help with the thermal expansion issues with the beacon sensor. I would like it to home everything, preheat bed to 60 and hotend to 220. Is that as simple as this: 
[gcode_macro Pre-Heat]

gcode:
  G28
  SET_HEATER_TEMPERATURE HEATER=extruder TARGET=210
  SET_HEATER_TEMPERATURE HEATER=heater_bed TARGET=60
[gcode_macro Pre-Heat]

gcode:
  G28
  SET_HEATER_TEMPERATURE HEATER=extruder TARGET=210
  SET_HEATER_TEMPERATURE HEATER=heater_bed TARGET=60
or is it more complex? I have never created / edited a macro before. Thanks!
5 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 10/29/2024 in #ratos-support
Inconsistent first layer between prints with Beacon
No description
20 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 10/3/2024 in #ratos-support
RatOS fails to connect to WiFi on reboot
No description
19 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 9/9/2024 in #fix-my-resonance
VC4 400 Hybrid Input Shaper Sanity Check
No description
8 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 9/6/2024 in #fix-my-mesh
VC4 400mm Bed Mesh - Bowed Gantry?
No description
33 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 9/6/2024 in #ratos-support
Outdated Beacon firmware
I am getting the following error on a fresh config of my VC4. 
MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-268-g0844388d7-dirty
MCU(s) which should be updated:
mcu: Current version v0.12.0-268-g0844388d7
rpi: Current version ?-20240727_132503-fv-az659-741
toolboard_t0: Current version v0.12.0-268-g0844388d7
beacon: Current version Beacon 1.1.0
Up-to-date MCU(s):
<none>

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.

Outdated Beacon firmware version 0.1.0, current version is 2.1.0.
Please run `install.sh` or `update_firmware.py update all` to update to the latest version.
Using an outdated firmware version can result in instability or failures.

mcu 'beacon': Unknown command: beacon_contact_home
MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-268-g0844388d7-dirty
MCU(s) which should be updated:
mcu: Current version v0.12.0-268-g0844388d7
rpi: Current version ?-20240727_132503-fv-az659-741
toolboard_t0: Current version v0.12.0-268-g0844388d7
beacon: Current version Beacon 1.1.0
Up-to-date MCU(s):
<none>

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.

Outdated Beacon firmware version 0.1.0, current version is 2.1.0.
Please run `install.sh` or `update_firmware.py update all` to update to the latest version.
Using an outdated firmware version can result in instability or failures.

mcu 'beacon': Unknown command: beacon_contact_home
I trying running install.sh and update_firmware.py but only got MCU protocol errors. Any advice?
6 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 5/2/2024 in #fix-my-print
SuperSlicer 2.5.59 random Tool Change GCode
Hello! I just downloaded the latest superslicer and I am having an issue where my custom tool change GCode is being inserted at the beginning of every print. I am not sure if I am missing a setting somewhere that would be causing this or if it is an issue with the slicer. Looking at the GCODE I feel like the M600 should be commented out but it is not? Would love any insight. 
;TYPE:Custom
; custom gcode: start_gcode
START_PRINT EXTRUDER_TEMP=250 BED_TEMP=108
; custom gcode end: start_gcode

G21 ; set units to millimeters
G90 ; use absolute coordinates
M82 ; use absolute distances for extrusion
G92 E0
; custom gcode: toolchange_gcode
M600
; custom gcode end: toolchange_gcode
; custom gcode: start_filament_gcode
; Filament gcode
SET_GCODE_OFFSET Z=0
SET_PRESSURE_ADVANCE ADVANCE=0.035
; custom gcode end: start_filament_gcode
M104 S250 T0 ; set temperature
M109 S250 T0 ; set temperature and wait for it to be reached
M190 S108 ; set bed temperature and wait for it to be reached
;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
; custom gcode: before_layer_gcode
;BEFORE_LAYER_CHANGE
;0.2
; custom gcode end: before_layer_gcode

G1 E-1.2 F2400
G1 Z0.2 F15000
; custom gcode: layer_gcode
;AFTER_LAYER_CHANGE
;0.2
; custom gcode end: layer_gcode
;TYPE:Custom
; custom gcode: start_gcode
START_PRINT EXTRUDER_TEMP=250 BED_TEMP=108
; custom gcode end: start_gcode

G21 ; set units to millimeters
G90 ; use absolute coordinates
M82 ; use absolute distances for extrusion
G92 E0
; custom gcode: toolchange_gcode
M600
; custom gcode end: toolchange_gcode
; custom gcode: start_filament_gcode
; Filament gcode
SET_GCODE_OFFSET Z=0
SET_PRESSURE_ADVANCE ADVANCE=0.035
; custom gcode end: start_filament_gcode
M104 S250 T0 ; set temperature
M109 S250 T0 ; set temperature and wait for it to be reached
M190 S108 ; set bed temperature and wait for it to be reached
;LAYER_CHANGE
;Z:0.2
;HEIGHT:0.2
; custom gcode: before_layer_gcode
;BEFORE_LAYER_CHANGE
;0.2
; custom gcode end: before_layer_gcode

G1 E-1.2 F2400
G1 Z0.2 F15000
; custom gcode: layer_gcode
;AFTER_LAYER_CHANGE
;0.2
; custom gcode end: layer_gcode
2 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 9/10/2023 in #fix-my-printer
Stepper skipping noise during primeblob
I have attached a video of the start sequence of my print. I am not actually sure if this is stepper skipping or not but as soon as the Z starts to increase during the purge blob I hear the same skipping / creaking noise. I don't believe it is coming from the extruder but actually sounds like it may be the front top left of the printer. I was wondering if this is a common issue and maybe I am missing something obvious.
6 replies
RRCRat Rig Community [Unofficial]
Created by Rubby on 3/8/2023 in #ratos-support
Trouble with [save_variables] on 2.0
In previous ratOS I had a couple of macros for adjusting my z-offset between smooth and textured plate using a variables.stb file. I just upgraded to 2.0 and am getting errors when trying to use the macros. My macros are as follows: 
filename: /home/pi/klipper/config/variables.stb

[gcode_macro SMOOTH_PLATE]
gcode:
  {% set value = printer.save_variables.variables.smooth %}
  SAVE_VARIABLE VARIABLE=active_offset VALUE={value}
  {action_respond_info("Smooth sheet active with offset %.3fmm" % (value))}
[gcode_macro  TEXTURED_PLATE]
gcode:
  {% set value = printer.save_variables.variables.textured %}
  SAVE_VARIABLE VARIABLE=active_offset VALUE={value}
  {action_respond_info("Textured sheet active with offset %.3fmm" % (value))}
[gcode_macro APPLY_PLATE_OFFSET]
gcode:
  {% set active_offset = printer.save_variables.variables.active_offset %}
  SET_GCODE_OFFSET Z={active_offset} MOVE=1
  {action_respond_info("Current Z offset %.3fmm" % (active_offset))}
filename: /home/pi/klipper/config/variables.stb

[gcode_macro SMOOTH_PLATE]
gcode:
  {% set value = printer.save_variables.variables.smooth %}
  SAVE_VARIABLE VARIABLE=active_offset VALUE={value}
  {action_respond_info("Smooth sheet active with offset %.3fmm" % (value))}
[gcode_macro  TEXTURED_PLATE]
gcode:
  {% set value = printer.save_variables.variables.textured %}
  SAVE_VARIABLE VARIABLE=active_offset VALUE={value}
  {action_respond_info("Textured sheet active with offset %.3fmm" % (value))}
[gcode_macro APPLY_PLATE_OFFSET]
gcode:
  {% set active_offset = printer.save_variables.variables.active_offset %}
  SET_GCODE_OFFSET Z={active_offset} MOVE=1
  {action_respond_info("Current Z offset %.3fmm" % (active_offset))}
and the variables.stb file is simple: 
  active_offset = 0.0
  smooth = 0.0
  textured = -0.335
  active_offset = 0.0
  smooth = 0.0
  textured = -0.335
The error I get when trying to select my plate is: 
Error evaluating 'gcode_macro SMOOTH_PLATE:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'smooth'
Error evaluating 'gcode_macro SMOOTH_PLATE:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'smooth'
Any help would be great! Or if there is a better build in way to do this now that would be awesome too!
5 replies