Filament config?

[genghisnico13]

Inside each Filament Config Macro:

M350 E16 I1		;Back to 16 microstepping to set it. 
;NonLinear Extrusion 
M92 E433.5 ;Adjusted for optimal curve fitting
M592 D0 A-0.00051 B0.00061 ;Nonlinear Extrusion parameters
M221 S101		;Flow(Diameter Compensation)
;Restore Microstepping to its value
M98 P0:/Macros/MotorControl/SetExtruderMicrostepping.g
 
;Set Temperatures
M140 S60			; Set Bed Temperature
G10 P0 R140 S215		; Set Nozzle Active and Standby Temperature

In this case FW Retraction (Pressure Advance also) is not configured because its the same as the one in the General Config file for PLA. And you can ignore the microstepping part, it's there so I can change the microstepping without editing all the Filaments config Files.

The Slicer start G-code calls a PrePrint macro:

M703		; Load Filament specific config, including Temps
T100 P0		; Sets T0 to Standby Temperature, after the T0 issued by the Slicer
 
M116 H0		; Wait for Bed Temperature to be reached
T0 P0		; Selects Tool 0 (active temp), without executing Tool-change Macros
G28
G29 S1		; Load Grid Compensation
G0 X320		 ; Move X to ooze Land
M116		; Wait for All Heaters
 
M98 P0:/Macros/Priming/PrimeOnBed.g

[genghisnico13]

@briskspirit I disabled Temperature Control from the addon "printer settings" in the cura "marketplace".

[3dmntbighker]

I have dipped a toe in by setting baby stepping -0.2 for PLA since it likes more squish than PETG. M290 R0 S-0.2 Is this the wrong approach? I could set the offset in the slicer I suppose. genghisnico13, you are a mad man

edit: So much for that idea. It doesn't survive a power cycle.

[Phaedrux]

@3dmntbighker If you have a custom config.g setup for the filament you can load it at startup so it should be applied again after a power cycle.

Baby stepping is different than the live Z adjust in Marlin, etc. It's not a permanent change.

[3dmntbighker]

@phaedrux said in Filament config?:

@3dmntbighker If you have a custom config.g setup for the filament you can load it at startup so it should be applied again after a power cycle.

Baby stepping is different than the live Z adjust in Marlin, etc. It's not a permanent change.

I added it to my PLA profile in S3D. It works fine there. I'm sure there are multiple ways to accomplish a Z offset like that. It's nice to have a flat stable bed that a 0.05 offset is actually useful for. I think I got super lucky with my Ender 3. I have not even bothered to change the wimpy bed springs. My first layers are pr0n-O-graphic

[Phaedrux]

@3dmntbighker I think you may be missing M703 to execute the filament specific config.g file.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M703_Configure_filament

[3dmntbighker]

@phaedrux said in Filament config?:

@3dmntbighker I think you may be missing M703 to execute the filament specific config.g file.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M703_Configure_filament

Hmm, I added M703 to to tpost0.g and config.g still only runs at the time you load the filament. The filament name loaded survives a power cycle, but PLA/config.g is not run again after a power cycle? Or do you need the M703 in both tpost0.g and sys/config.g? If I deselect tool0 and select it again it looks like M703 doesn't run either. I have to unload and reload the filament.

[Phaedrux]

@3dmntbighker I could see needing to add it to config.g, but it doesn't sound like it's working as intended. I think @chrishamm developed this functionality?

[AlexLin]

I added M703 in start.g.so at the beginning of a print all filaments specifics are loaded

[3dmntbighker]

@alexlin said in Filament config?:

I added M703 in start.g.so at the beginning of a print all filaments specifics are loaded

I have a stop.g but no start.g?

[Phaedrux]

@3dmntbighker you can create it. It will be run first at the start of every print before the slicer start gcode.

I use it to do a preheat and home the printer, reset any extrusion or speed factors, reset baby stepping, and play a little tune.

[3dmntbighker]

@phaedrux said in Filament config?:

@3dmntbighker you can create it. It will be run first at the start of every print before the slicer start gcode.

I use it to do a preheat and home the printer, reset any extrusion or speed factors, reset baby stepping, and play a little tune.

S3D does a lot of that for you in the start code. But putting it in Duet code and purging your slicer means you don't have to worry what slicer you are using I suppose.

I was thinking yesterday that we need a pinned thread of people's musical code

[Phaedrux]

@3dmntbighker Agreed! Here's mine: https://www.dropbox.com/sh/24m8me9jieqk725/AACJMSA0qlxw3KPLf_cjIVT5a?dl=0