Force M703 execution

genghisnico13

Hi, I am trying to remove as much filament/printer specifics config from sliced Gcodes as possible, so I started using Filament specific configs, to set flow, nonlinear extrusion, retraction, etc...
Right now I have M703 in Tpost0, but since I only have 1 tool it is never executed, so I put it in my slicer start Gcode.
Is there a chance to force tool selection to load filament config even if that tool is already selected? So the slicer T0 implicitly executes a M703.
Or maybe have a Talwaysx.g that is executed even if the tool is already selected?

wilriker

@genghisnico13 Why don't you keep it in your start codes but move these out of the slicer into a custom macro and only call this macro in slicer's start codes with

M98 P...

At least that is how I do it. Another way would be to have it in your config.g.

P.S.: If you have T0 also in your config.g this should then execute tpost0.g which would then also run M703.

Or do you have any need to explicitly run it before each print?

genghisnico13

@wilriker Thanks, last night I configure it that way, but i'm not so sure about this:
"If you have T0 also in your config.g this should then execute tpost0.g", as far as I understand it all the t macros are only executed if a different tool is selected, and since I only have one, T0 doesn't execute any macro.
I tried putting T0 in config and no, tpost0 is not executed.
It would be nice to execute it before each print because I usually tweak it between prints until I find the perfect settings.

wilriker

@genghisnico13 said in Force M703 execution:

@wilriker Thanks, last night I configure it that way, but i'm not so sure about this:
"If you have T0 also in your config.g this should then execute tpost0.g", as far as I understand it all the t macros are only executed if a different tool is selected, and since I only have one, T0 doesn't execute any macro.
I tried putting T0 in config and no, tpost0 is not executed.

Actually, I never bothered to check because my tpost0.g is more or less empty (I also have just this one tool)

It would be nice to execute it before each print because I usually tweak it between prints until I find the perfect settings.

In this case it would make most sense to have it in the start codes, I think. This does what you need plus it does not require any changes in the firmware.