Filaments

sunToxx

I would like to move as much as possible of the slicers filaments profiles into Duet's filament files. However it seems I can't even set first layer temperature and other layer temperature. Slicers use variables for that, so that they can add the right code at the desired time. Can Duet kind of inject code at a certain layer, or how can this be done?

Also, Caribou by default calls in start.g for m703. Is this sufficient, or does the slicer startcode also need a m703?

dc42

@suntoxx most slicers allow you to define a layer change script. You could define that script to use M98 to call a macro, passing the layer number as a parameter.

sunToxx

@dc42 Would that mean that I add a command to the slicer, that executes a macro when changing to layer 2? And I can do it in a way, that the macro (eg 2ndLayertemp.g) will be chosen within the currently active Duet filament directory?

sunToxx

@dc42 said in Filaments:

@suntoxx most slicers allow you to define a layer change script. You could define that script to use M98 to call a macro, passing the layer number as a parameter.

How would that allow me to comfortably manage eg the first layer and other layer temperatures from within DWC's filaments? Unless Duet changes a macro on every material change with the corresponding values, so i can refer to it.

Or can the layer change script call for m703 again, which then might contain a temperature change limited by in IF statement, so it only becomes active at layer 2?

I am a bit lost here. It's not that I have any idea about all of this

Edit: And if for example, I would have 5 different types of PLA in my filaments section of DWC, and they share one value and differ in others, could I use the M98 command to manage that shared value in one single position?

sunToxx

Can I use the Echo command (https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands) in one of the files of the filaments section, in order to have it automatically create/overwrite a macro, according to the currently used filament? (the macro should have same name for all filaments, but then only contains the temperature for the currently selected filament).

So that i can call this macro with M98 custom gcode in the slicer and it would always set the other layer temperature to the one i define in the filaments section of dwc? Would config.g or load.g make the most sense to have it create that macro?

Also, is calling for M703 in start.g enough, or does it have to be included into the slicer start code too, in order so noting overrides it?

Edit: echo >"test.g" "M104 S210" does not seem to work