Sorry for the delayed response everyone. I broke my Z endstop/probe and had to wait for a new one in the mail to continue printing. The problem persists.
@deckingman said in Extreme over extrusion when upgrading from 3.2.2 to 3.3:
@makestuffmakestuff I don't see anything in your config.g that would cause the machine to extrude more than 20X the required amount of filament. About the only thing I can think of which might cause that behaviour is perhaps an M82 has crept in somewhere which is overriding the M83 you have in your config.g. So instead of expecting the gcode from the slicer to have relative moves, it is expecting them to be absolute. Possible laces to look would be config-overide.g if you use it, or the slicer start gcode, or any macros you run prior to printing. Either that, or maybe the gcode file itself is corrupted. What happens if you manually extrude using DWC?
There is no M82 or M83 anywhere in the gcode, config, config-override or homing files. If I manually extrude with DWC I get the expected extrusion length.
@percar said in Extreme over extrusion when upgrading from 3.2.2 to 3.3:
Check out the M82 M83 issue
I recently had the same issue and i was pulling out my hair
Ensure that your slicer is not inserting M82 or M83 someplace it shouldnt
I found my issuer on my Z homing file that i had written years ago
No luck finding M82 or M83 anywhere.
@phaedrux said in Extreme over extrusion when upgrading from 3.2.2 to 3.3:
@makestuffmakestuff said in Extreme over extrusion when upgrading from 3.2.2 to 3.3:
E3:4:8:9
Not sure if it will matter but you've got 4 extruder drives mapped, but only have values for 2 extruders in your other settings.
M350 X16 Y16 Z16 E16:16
Either unbind the additional extruders, or define their settings as well.
What do you have in your slicer start gcode? The fact that it stuck around between 3.3 and going back to 3.2 seems to indicate the firmware change is a red herring. Did something else change in the slicer?
I'll remove the 2 extra extruder definitions, but they've been there since before this issue showed up.
As for the slicer changing, I have a gcode file that printed perfectly. When I run the same exact file now I get the extreme over extrusion. That is what indicates to me that it has to be a configuration issue. I can't for the life of me remember changing anything before the 3.3 upgrade though. And when I extrude with DWC I get the expected filament length. Just for fun, I'll post the beginning of a sliced file for analysis.
T-1 ; make sure we don't have a tool in the holder
T1 P0 ; Turn on the first layer tool to get temp rising without running change macros
T-1 P0 ; Set it back to no tool, again running no tool change macro to set Tool 0 to standby
M568 P1 R220 S240 ; Set the first tool to standby and set the active and standby temps
M140 S90 ; Set first layer bed temp
G28 ; home all axes
M190 S90 ; Set first layer bed temp and wait before leveling bed
G32 ; level the bed
G28 Z ; Home the Z axis only
G1 Z20 F5000 ; lift nozzle
T1 ; Get the first tool to be used
M116 ; Wait for all temperatures to reach printing values
; Filament gcode
M290 R0 S0 ; Reset babystepping to 0
;M290 S-0.2 ; Set babystep to 0.05 farther from the bed
M107
;LAYER_CHANGE
;Z:0.34
;HEIGHT:0.34
G1 Z0.340000 F9000
G1 E-2.00000 F2400
G1 X94.939 Y65.392 F9000
G1 E0.00000 F2400
;TYPE:Skirt
;WIDTH:0.37
G1 F900
G1 X95.955 Y64.044 E0.07231
G1 X97.002 Y62.975 E0.13639
;Gcode continues after this...