Extrusion setup question [Solved]

3dmntbighker

@deckingman said in Extrusion setup question:

.........what DC said and also 413 (micro) steps per mm is about right for a Bondtech when using 16x micro stepping. So if you had calibrated the extruder using 16x micro-stepping, then changed it to 8, you'll get twice the extrusion amount.

Edit ........(depending on where in the gcode file you set steps per mm in relation to micro-stepping).

415 and 8 micro gives me 10mm of filament travel using 10mm in the GWI extrusion panel. 415 and 16 micro gives 5mm in the GWI when you ask for 10. But G1 E10 gives me 10mm of filament travel with 415 and 16. The GWI extrusion panel leaves no Gcode behind in the console so I don't actually know what it's doing.

Now that I'm running 16 M591 looks a lot more sane, and the print is in the ballpark.

Duet3D laser filament monitor on endstop input 3, disabled, allowed movement 40% to 120%, check every 3.0mm, current position 1.0, brightness 74, shutter 17, measured minimum 73%, average 84%, maximum 92% over 192.2mm

So I believed the extrusion panel to calibrate and got burned for it. I'm not sure if I fix that or it's a bug.

3dmntbighker

@dc42 said in Extrusion setup question:

What nozzle size are you using? The extrusion width needs to be greater than the nozzle size. So if you are using a 0.4mm nozzle, the extrusion width must be more than 0.4mm, e.g. 0.5 or 0.6mm.

Why are you using x8 microstepping for the extruder motor, instead of x16 or higher?

It's a 0.4 nozzle, and the test cube author says to use 0.4 extrusion width.

https://www.thingiverse.com/thing:2490893

I had to use 8 to get the GWI to extrude the amount requested. Now I'm using 16 and the GWI seems to be the only thing not working as expected.

3dmntbighker

Yeah, it's making a fantastic print now even with no part cooling yet. I should have resorted to bare Gcode in the first place and not believed the GWI was doing what it said it was doing.

Phaedrux

What is GWI?

3dmntbighker

@phaedrux said in Extrusion setup question:

What is GWI?

Graphical web interface.

dc42

Are you saying that when you ask Duet Web Control to extrude 10mm of filament, it only consumes 5mm?

What version number of DWC at you using?

3dmntbighker

@dc42 said in Extrusion setup question:

Are you saying that when you ask Duet Web Control to extrude 10mm of filament, it only consumes 5mm?

What version number of DWC at you using?

Brand new Maestro. I'll report back tonight when I get home with version. And yes, if you ask for 10 you get 5, where as asking for 10 with a gcode console command (G1 E10) gives you 10. I'll also try the other increment buttons to see if all of them are wrong.

dc42

Which version of Duet Web Control is it running? Look in the Settings General page to find out. The latest version is 1.22.4.

3dmntbighker

@dc42 said in Extrusion setup question:

Which version of Duet Web Control is it running? Look in the Settings General page to find out. The latest version is 1.22.4.

Web Interface Version: 1.20
Firmware Version: 2.01beta2(RTOS) (2018-07-14b5)

And now all the numbers are correct. No idea what was going on before. Obviously you guys put in code just to mess with me

I will update to current. I planned to wait until the beta goes gold on both my Duet boards.

Thanks

3dmntbighker

@dc42 said in Extrusion setup question:

Which version of Duet Web Control is it running? Look in the Settings General page to find out. The latest version is 1.22.4.

Thinking about this more I wonder? If I change the config file and reload the firmware without power cycling the board or force reloading the Web interface, what are the chances I would get some of the behavior I was seeing? What determines the button actions, and can they get out of sync with config.g?

BTW, I believe the default micro stepping when I installed the board was 16 for XYZ and 8 for E. With this as a starting point it's likely things went off the rails for reasons I didn't grasp at the time. There was definitely a period where the web interface was not in sync with what config.g was set to. And it persisted through reloading and power cycling because it happened of the course of several days.