moggieuk / Happy-Hare

MMU software driver for Klipper (ERCF, Tradrack, Prusa)
GNU General Public License v3.0
443 stars 107 forks source link

Problem on Print Start #175

Open MattiaFontanaErrepinet opened 7 months ago

MattiaFontanaErrepinet commented 7 months ago

Hello after doing the whole homing and bed leveling routine. I noticed that he doesn't check the gates that will be used.

In fact it gives me this error: 17:03:21 An issue with the MMU has been detected. Print paused. Reason: Gate #0 is empty! Use 'MMU_CHECK_GATE GATE=0' to reset. Occured when changing tool: Unknown > T0 17:03:21 After fixing the issue, call RESUME to continue printing (MMU_UNLOCK can restore temperature)

The G-Code I'm using inside OrcaSlicer is as follows PRINT_START REFERENCED_TOOLS=!referenced_tools! INITIAL_TOOL={initial_tool}

And i have added this to my printer.cfg
` {% set REFERENCED_TOOLS = params.REFERENCED_TOOLS|default("")|string %} {% set INITIAL_TOOL = params.INITIAL_TOOL|default(0)|int %}

{% if REFERENCED_TOOLS == "!referenced_tools!" %}
    RESPOND MSG="Happy Hare gcode pre-processor is diabled"
    {% set REFERENCED_TOOLS = INITIAL_TOOL %}
{% elif REFERENCED_TOOLS == "" %}
    RESPOND MSG="Happy Hare single color print"
    {% set REFERENCED_TOOLS = INITIAL_TOOL %}
{% endif %}

:

MMU_CHECK_GATE TOOLS={REFERENCED_TOOLS}

MMU_CHANGE_TOOL STANDALONE=1 TOOL={INITIAL_TOOL}    # Optional: load initial tool

:`
moggieuk commented 7 months ago

Assuming you have verified that mmu_server in moonraker is enabled, can you try a separate upload to klipper virtual_sd card then initiate the print. Or better still, upload the file, then open it with your favorite editor and search for PRINT_START to see that it has been expanded.

This does work (at least uploading, then printing as two separate operations), but you need to verify what is happening after the gcode is uploaded.

MattiaFontanaErrepinet commented 7 months ago

They load correctly but it doesn't seem to check

PRINT_START REFERENCED_TOOLS=0,1 INITIAL_TOOL=0

This is full print_start gcode


[gcode_macro PRINT_START]
#   Use PRINT_START for the slicer starting script - please customise for your slicer of choice
gcode:
    G32                            ; home all axes
    G90                            ; absolute positioning
    G1 Z20 F3000                   ; move nozzle away from bed
    #BED_MESH_CALIBRATE
    {% set REFERENCED_TOOLS = params.REFERENCED_TOOLS|default("")|string %}
    {% set INITIAL_TOOL = params.INITIAL_TOOL|default(0)|int %}

    {% if REFERENCED_TOOLS == "!referenced_tools!" %}
        RESPOND MSG="Happy Hare gcode pre-processor is diabled"
        {% set REFERENCED_TOOLS = INITIAL_TOOL %}
    {% elif REFERENCED_TOOLS == "" %}
        RESPOND MSG="Happy Hare single color print"
        {% set REFERENCED_TOOLS = INITIAL_TOOL %}
    {% endif %}

    MMU_CHECK_GATE TOOLS={REFERENCED_TOOLS}

    MMU_CHANGE_TOOL STANDALONE=1 TOOL={INITIAL_TOOL}
moggieuk commented 7 months ago

That looks correct. MMU_CHECK_GATE TOOLS={REFERENCED_TOOLS} actually initiates the check.

What does mmu.log say? You can attach here..

One thing I want to check is that you upload the gcode first and then print rather than "update and print" from the slicer?

MattiaFontanaErrepinet commented 6 months ago

mmu (2).log Hi this is MMU.log

LostFool commented 1 week ago

Note the spelling "Happy Hare gcode pre-processor is diabled" diabled instead of "disabled"

Also I get the same issue after verifying my Print Start, plus start gcode, and mmu_server