8Complex Posts - Answer Overflow

8Complex

•Created by 8Complex on 4/19/2023 in #ratos-support

Retraction Tuning

What is the process to do retraction tuning with RatOS? I've tried just doing a SuperSlicer Retraction Tuning print, but it seemingly didn't change along the height (print was perfect). I then went into my printer.cfg and commented out the "firmware_retraction" section altogether, no difference in the printing. Noticed the "Retract Length" in Mainsail shows 0.5... so I manually tried changing it while the print progressed with no results (you'd think something would change, right?). Now I just started digging around to find out where that 0.5 came from and found that the includes for the hotend (Rapido) and the extruder (Orbiter-1004) both have settings under the "firmware_retraction" group. As far as I can tell, there is no way for me to turn off those firmware retraction settings once they're set by the profile. So.... how do I get around this to do a test print with slicer retractions that vary?

31 replies

RRCRat Rig Community [Unofficial]

•Created by 8Complex on 3/4/2023 in #ratos-support

Broke PAM, not sure how...

Fresh install on RatOS 2.0, followed the instructions on the PAM site to install. @Helge Keck Have in printer.cfg (near end)

[include pam/ratos.cfg]

[include pam/ratos.cfg]

Have in SuperSlicer start code (middle lines from Mikl, worked fine in the past)

MESH_CONFIG X0={first_layer_print_min[0]} Y0={first_layer_print_min[1]} X1={first_layer_print_max[0]} Y1={first_layer_print_max[1]}
M190 S0 ; Prevents prusaslicer from prepending m190 to the gcode ruining our macro
M109 S0 ; Prevents prusaslicer from prepending m109 to the gcode ruining our macro
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]

MESH_CONFIG X0={first_layer_print_min[0]} Y0={first_layer_print_min[1]} X1={first_layer_print_max[0]} Y1={first_layer_print_max[1]}
M190 S0 ; Prevents prusaslicer from prepending m190 to the gcode ruining our macro
M109 S0 ; Prevents prusaslicer from prepending m109 to the gcode ruining our macro
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]

Error from Klippy.log (wish I could clear this entire log to get only current info)

Internal error on command:"PAM"
Internal error on command:"_START_PRINT_BED_MESH"
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/gcode.py", line 198, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/gcode.py", line 135, in <lambda>
    func = lambda params: origfunc(self._get_extended_params(params))
  File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 186, in cmd
    self.template.run_gcode_from_command(kwparams)
  File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 68, in run_gcode_from_command
    self.gcode.run_script_from_command(self.render(context))
  File "/home/pi/klipper/klippy/gcode.py", line 213, in run_script_from_command
    self._process_commands(script.split('\n'), need_ack=False)
  File "/home/pi/klipper/klippy/gcode.py", line 198, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/gcode.py", line 135, in <lambda>
    func = lambda params: origfunc(self._get_extended_params(params))
  File "/home/pi/klipper/klippy/extras/pam.py", line 67, in cmd_PAM
    self.gcode.respond_raw('Relative Reference Index {0}'.format(str(reference_index)))
UnboundLocalError: local variable 'reference_index' referenced before assignment
MCU 'mcu' shutdown: Command request

Internal error on command:"PAM"
Internal error on command:"_START_PRINT_BED_MESH"
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/gcode.py", line 198, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/gcode.py", line 135, in <lambda>
    func = lambda params: origfunc(self._get_extended_params(params))
  File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 186, in cmd
    self.template.run_gcode_from_command(kwparams)
  File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 68, in run_gcode_from_command
    self.gcode.run_script_from_command(self.render(context))
  File "/home/pi/klipper/klippy/gcode.py", line 213, in run_script_from_command
    self._process_commands(script.split('\n'), need_ack=False)
  File "/home/pi/klipper/klippy/gcode.py", line 198, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/gcode.py", line 135, in <lambda>
    func = lambda params: origfunc(self._get_extended_params(params))
  File "/home/pi/klipper/klippy/extras/pam.py", line 67, in cmd_PAM
    self.gcode.respond_raw('Relative Reference Index {0}'.format(str(reference_index)))
UnboundLocalError: local variable 'reference_index' referenced before assignment
MCU 'mcu' shutdown: Command request

27 replies

RRCRat Rig Community [Unofficial]

•Created by 8Complex on 3/4/2023 in #ratos-support

RatOS 2.0 Error Notifications (Solution)

2 replies

RRCRat Rig Community [Unofficial]

•Created by 8Complex on 1/19/2023 in #fix-my-printer

4028 Hookup Sanity Check

Have a SanAce 4028, although I am reasonably sure it's a re-stickered other model. This one seems to only run at 100% or 0% when playing with the speed, so I want to make sure my pins are good and it's really the fan that is the issue. Fan +12v is hooked to Octopus fan 1 positive (FAN0+) (jumped to 12v) Fan GND is hooked to Octopus heater 4 pin (PB11) Fan PWM is hooked to EBB 36 fan signal (PA0) Fan Tacho is hooked to EBB 36 unused pin (PB7) Code in printer.cfg:

pin: !fan_part_cooling_pin
cycle_time: 0.00004
tachometer_pin: toolboard:^PB7
tachometer_poll_interval: 0.0005
enable_pin: !toolboard:PA0

[output_pin 4028_POWER]
pin: PB11
value: 1
shutdown_value: 0

pin: !fan_part_cooling_pin
cycle_time: 0.00004
tachometer_pin: toolboard:^PB7
tachometer_poll_interval: 0.0005
enable_pin: !toolboard:PA0

[output_pin 4028_POWER]
pin: PB11
value: 1
shutdown_value: 0

As a side note, I have hooked this fan to an old printer directly to the fan port with the +/- wires and I was able to regulate it down to about 30% easily, which seemed to be very slow.

50 replies

RRCRat Rig Community [Unofficial]

•Created by 8Complex on 1/11/2023 in #ratos-support

RatOS 2 Setup Wizard

11 replies

RRCRat Rig Community [Unofficial]

•Created by 8Complex on 12/29/2022 in #fix-my-print

Guessing this is 4028 territory...?

15 replies

Gaming

Programming