Odd behavior with multiple filaments selected (MMU - Single tool)

[JesNoFear]

I am seeing some odd behaviors with multiple filaments selected.

1. When print starts, it pulls spool 0 (T1) filament offset (yay) - but pulls the bed offset from the last spool selected
2. when tool changes occur, offsets are not updated.
3. When print starts and T2 is the first tool, it still pulls filament offset for spool 0 (T1) and bed offset from the last spool listed (in my test case spool 2 - T3)

[WildRikku]

Please post your SpoolManager and OctoPrint version.

[JesNoFear]

Spoolmanager 1.7.7
Octoprint 1.10.3

[WildRikku]

Alright, I'll look into it.

[WildRikku]

@JesNoFear
Since I don't have a printer with multiple extruders, I'll investigate using virtual printers in OctoPrint. I'll need some more information for that.

The MMU has multiple extruders / filaments but one nozzle, correct? What exactly is the "tool" in your setup and what are T1, T2, T3 refering to?

I am seeing some odd behaviors with multiple filaments selected.

1. When print starts, it pulls spool 0 (T1) filament offset (yay) - but pulls the bed offset from the last spool selected

By "filament offset", you mean the "tool offset" configured in the filament?

2. when tool changes occur, offsets are not updated.

Could you provide a, preferably short, gcode file that includes such a change?

[JesNoFear]

No problem,
here is the extruder configuration

here is what the slicer looks like,

here is a 3mf and gcode file
V350-SS-HQ-MMU-Cute Bee Lg (0,1,3).zip

Tools refer to the toolhead, some printers may have multiple, but in a shared nozzle configuration, it refers to the filament channel on the MMU, they are called by gcode with T0, T1, T2, ... think of it as an automated M600.

this is probably the best layout i can show you,

T0 is what everyone uses, but when its the only one defined, there is no need to call it.

you are correct, when i said filament offset, i meant tool offset for the filament

if you start diving into the 3mf, it calls upon macros, i have attached them incase.
Macros and Klipper Config.zip

in the toolchange gcode in the slicer, i call M109 expecting octoprint to adjust based on the offset, but the offset isnt changing after initially set.

Here is a snip-it of a toolchange in the gcode i sent you.

; Filament-specific end gcode 
;END gcode for filament
; custom gcode end: end_filament_gcode
; custom gcode: toolchange_gcode
RESPOND PREFIX="info" MSG="Tool Change, Layer Height = 3.05"
G1 E-2 F1200
G0 Z5.05 F20000  ; move nozzle to remove stringing
G0 X215 Y357  ; parking toolhead xy
G0 Z4.5 ;  parking toolhead z

M109 S200  ; Tool Change Tool Temp

RESPOND PREFIX="info" MSG="Tool Change, Next Tool = 3"
T3 ; MMU Toolchange Command

RESPOND PREFIX="info" MSG="Tool Change, Next Tool = 3  Next Temp = 240"
M109 S240  ; set temp for now current tool for Octoprint to modify
CLEAN_NOZZLE
G0 X175 Y357  ; Safe zone
G0 Z5.05  ; current layer height
; custom gcode end: toolchange_gcode
; custom gcode: start_filament_gcode
; Filament gcode

; Macro syntax: https://help.prusa3d.com/article/macros_1775
; The "=~" operator uses regex enlosed by forward slashes (=~/regex/).
; The "==" operator can be used for an exact match instead if you wish (=="string").

; The below logic says:
; - IF printer settings profile name contains "Voron" (using regex)
; - AND nozzle size equals <value>
; - THEN insert the gcode (SET_ PRESSURE ADVANCE ADVANCE=<value>).
; Uncomment all lines below (and modify appropriately) if you wish to use this.

;SET_PRESSURE_ADVANCE ADVANCE=0.0495
;

; custom gcode end: start_filament_gcode
G1 E-1.000000 F1800
; stop printing object BeeLg.stl id:0 copy 7
EXCLUDE_OBJECT_END NAME=BeeLg_stl_id_0_copy_7
; printing object BeeLg.stl id:0 copy 0
EXCLUDE_OBJECT_START NAME=BeeLg_stl_id_0_copy_0
; acceleration to travel

Let me know what other information you would like details about
Thank you for looking into this

[JesNoFear]

By "filament offset", you mean the "tool offset" configured in the filament?

a little more detail on this,

lets say i have 4 spools defined,

when i start a print, the tool offset will pull from selected spool 0

where the bed offset will pull from the last defined selected spool, in this case spool 3

the other two spools defined are

as i am stepping through this to capture screen shots, i actively see the bed offset being applied to bed and chamber on not the last spool defined in the list, but the last spool chosen, whether its spool 0, 1, or 8. if they are entered out of order its the last one chosen.

i wish i knew/understood python better so i could help. because now i am wondering are the calculations correctly subtracting from the proper spools as the print goes. I have been using partial / junk spools for the setup and calibration of the MMU so the counts are already off.

if it will help and/or if you feel up to it, we can setup a screen share on teams or discord if you would like.

[WildRikku]

Thanks for all the additional info. I have an idea what might go wrong in the plugin code - there were issues with the bed temp before, which is why I asked for your plugin version. I'll check that in the next couple days and write again.

Regarding the amount of used filament, that's happening in a completely different part of the plugin and OctoPrint and I don't know of any issues there. If all your used spools show less filament after a print, I'd say it's probably reduced by the correct amounts. You could however check that quite easily by for example printing cubes using 1, 2 and 3 grams of filament (as calculated in the slicer) of one color each in the same gcode. Filament usage calculation is complex but should not be completely off.

[WildRikku]

related OctoPrint/OctoPrint#3144