LogieBears Posts - Answer Overflow

LogieBears

•Created by LogieBears on 9/4/2024 in #ratos-support

Can not update MCU 'mcu' error after updating

This is a new Vcore4 build. I've put RatOS 2.1 on the SD card in the raspberry pi, and gone through the initial configuration. The MCU and toolboard flash correctly and everything looks good. When I open Mainsail, there were a couple orange errors. I unfortunately did not document these but they had to do with a T0 range error. I browsed to the machine tab and update RatOS, then did a full update. After the update I get the MCU update error in the title. If I browse back to the configurator, it now says that the Octopus 1.1 446 is detected but is unresponsive.

30 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 8/8/2024 in #fix-my-print

Is this z wobble or flow issues?

3 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 7/29/2024 in #fix-my-resonance

Unenclosed vcore3.1 500mm issues

2 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 7/26/2024 in #fix-my-print

What does this look like?

5 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 7/8/2024 in #ratos-support

How Can I delay the activation of the filament sensor until after the prime blob - will this work?

I'd like to delay the filament sensor until after the prime blob. Will something like this work? I'm trying to piece this together with other information I've found online and am unsure as to the formatting.

[gcode_macro enable_filament_sensor]
# Helper macro to enable runout sensor
gcode:
    # Activate the sensor
    SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1
    
[gcode_macro _PRIME]
gcode:
    # disable the sensor
    SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0
    # prime blob
    {% if printer["gcode_macro RatOS"].nozzle_priming|lower == 'primeblob' %}
        PRIME_BLOB INITIAL_TOOLHEAD={params.INITIAL_TOOLHEAD} BOTH_TOOLHEADS={params.BOTH_TOOLHEADS} IDEX_MODE={params.IDEX_MODE} Y1={params.Y1}
    {% endif %}
   # call enable_runout_sensor with a delay of 1 sec
    UPDATE_DELAYED_GCODE ID=enable_filament_sensor DURATION=1

[gcode_macro enable_filament_sensor]
# Helper macro to enable runout sensor
gcode:
    # Activate the sensor
    SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1
    
[gcode_macro _PRIME]
gcode:
    # disable the sensor
    SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0
    # prime blob
    {% if printer["gcode_macro RatOS"].nozzle_priming|lower == 'primeblob' %}
        PRIME_BLOB INITIAL_TOOLHEAD={params.INITIAL_TOOLHEAD} BOTH_TOOLHEADS={params.BOTH_TOOLHEADS} IDEX_MODE={params.IDEX_MODE} Y1={params.Y1}
    {% endif %}
   # call enable_runout_sensor with a delay of 1 sec
    UPDATE_DELAYED_GCODE ID=enable_filament_sensor DURATION=1

4 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 7/5/2024 in #ratos-support

Multiple IP addresses assigned to one printer?

I updated my vcore3 from ratos 1.x to 2.1 and am running into an issue. I am connected via ethernet, but during the setup I also gave the Wifi network+password which I think might be the main problem. My router is showing 2 IP addresses for the printer, and Orca Slicer crashes when I try to send a file (I am using the hostname instead of the IP in Orca Slicer) . A window pops up and says something about multiple IP addresses, then crashes. Prusaslicer sends files just fine even using just the Hostname, but it still remains that there are multiple IP addresses. Is there somewhere in RatOS that I can either disable the Wifi or is there another problem here?

7 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 2/24/2023 in #fix-my-print

Same print settings, slightly different model, what's going on?

4 replies

RRCRat Rig Community [Unofficial]

•Created by LogieBears on 2/13/2023 in #fix-my-resonance

VC3.1 500 issues. FMMM and Extrusionless X

26 replies

Gaming

Programming