Impossible to set extruder micro stepping above 16ms

[JoergS5]

@observatoer can you please check config-override.g and the start codes of the printed g-code file, maybe they are changing the E setting. Do the startup macros include M501 maybe?

[observatoer]

@JoergS5 Did this in the beginning of the test already. I cleared the content of it and omitted the loading in config.g.

[JoergS5]

@observatoer you seem to use IdeaMaker, is there something in the startup code which could change E?
https://forum.raise3d.com/viewtopic.php?t=12893
https://support.raise3d.com/ideaMaker/5-1-3-13-gcode-15-445.html
especially the "Extruder Switch GCode tab". Lot of places to change something...

[observatoer]

@JoergS5 Thanks for the hint, but I have removed all the default settings in Ideamaker from the start code and call a start macro on the duet3. This is all that remains:

M98 P"0:/sys/print/start.g" ; call start.g

M290 R0 S0 ;reset babystepping
M290 S-0.05 ; set babystepping height delta

M572 D0 S0.025 ;set pressure advance

And nothing in the extruder level. Totally empty.

[JoergS5]

@observatoer next I would check content of start.g and if babystepping or pressue advance change the E by disabling them.

[observatoer]

@JoergS5 Looks OK to me.

G29 S1 P"heightmap.csv" ; Load the height map from file and activate bed compensation.
G90 ; use absolute coordinates
M83 ; extruder relative mode

M98 P"0:/sys/G828.g" ; home if not homed
M98 P"0:/sys/G832.g" ; if not already leveled, level bed and re-home Z

; prime nozzle
G1 X0 Y0 F99999.0 ; Go home
G1 Z0.15 ; lower extruder

G1 X2 Y20 Z0.3 F5000.0 ; move to start-line position
G1 X2 Y200.0 Z0.3 F1500.0 E15 ; draw 1st line
G1 X2 Y200.0 Z0.4 F5000.0 ; move to side a little
G1 X3 Y20 Z0.4 F1500.0 E30 ; draw 2nd line
G92 E0.0

And the two calls look clean, too:

; G828.g
; Conditional variant of G28 home command.
; Homes all axes if not already homed.
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
G28

; G832.g
; Conditional variant of G32 bed command.
; Perform bed leveling if not already leveled.
if move.calibration.numFactors == 0 ; if leveling has not yet been performed...
G32 ; level bed
G28 Z ; re-home Z
else
echo "Bed already leveled. Skipping..."

[JoergS5]

@observatoer then I have no more ideas at the moment. I would remove and disable or comment out all and readd step by step to find the reason. It is also possible that there is a bug somewhere, because you have a lot of settings, macros etc. To be sure it's not IdeaMaker I would try a different program and g-code file first.

[observatoer]

@JoergS5 Thank you for your time and hints!

[JoergS5]

@observatoer sorry that I could not help. I think it's something trivial, a syntax error e.g., but I didn't see one.

Maybe M350 E16 I0 changing the E without interpolation behaves other than expected. You could try changing it to I1 as a test.

[JoergS5]

@observatoer I have one more idea: according the information in some threads like https://forum.duet3d.com/topic/4939/m350-not-working-wrt-m584/6 the order of the drives seem to play a role in the M584 command. In you config you have E first, so this may not be seen as an extruder drive in some code for other program parts. You could try changing
M584 E0 X1 Y2 Z3:4:5
to
M584 X1 Y2 Z3:4:5 E0

[dc42]

If anyone thinks that M350 is not behaving as described in the wiki GCodes page, please supply files that replicate the different behaviour.

[observatoer]

@JoergS5 That would make sense and I will give it a try. Stii the change will be a bag of hurt to get the order of the z drives and the related measurements for ABL right.
Thank you very much for your help! I will report, how this turns out.

[observatoer]

@dc42 I guess, this tread is full of all related logs and describes the issue in detail. Still I understand, it's a pain to go thru the logs.

[dc42]

One of the reports says that the steps/mm changes when starting a print, but I didn't see a print file posted. Also, the config files have changed, so it's hard to be sure what the current ones look like.

[observatoer]

@dc42 Thank you, this was the right question.
Ideamaker is setting the E value to 822s/mm and writes this at the beginning of the code.
That was the reason, why this issue came up.

Thanks again and I guess, the solution is found.