Tool select at beginning or end of tool change sequence?

tekstyle

I was wondering if lets say the machine has T0 selected and T1 command is evoked, does the firmware select T1 at the beginning or at the end of the Tfree0.g > Tpre1.g > Tpost1.g sequence?

what my goal is:
I have heat parameter settings in my filament config.g that I wish to use based on the Tn it is called from. I wish to place a m703 command in the Tpre1.g file but it will only work if the firmware selects T1 at the start of the tool change sequence, not at the end. Or else it will get the heater parameters for T0 instead.

can someone please confirm that it is at the beginning or the end? thank you.

fcwilt

@tekstyle

Have you considered using the Filament handling feature of the DWC?

Frederick

jay_s_uk

@tekstyle T1 will be "selected" between t1pre and t1post

tekstyle

@fcwilt said in Tool select at beginning or end of tool change sequence?:

Filament handling

are you referring to this? https://duet3d.dozuki.com/Wiki/Filaments#Section_Custom_per_filament_config_g

Yes, I use this currently for each filament I have. After loading a filament on a chosen tool, it will use those parameters in the config.g file.. however, it does not play well with CURA slicer (or any slicer I would think). In CURA, I have to specify what temperature to set the filament and bed temperature. I want firmware to override. so instead, what I do is set tool and bed temp to 0. If i start a print and uses a single TOOL throughout the whole entire print, it will load the associated filament config.g at the start of the print and everything goes fine. the problem is when it changes to another tool, it does not do a M703 command of the next tool, but instead load the CURA temperature parameter (which is 0 for both tool and bed).

thats why I want to place a M703 command after the firmware selects the next TOOL during a tool change, so it knows to apply the filament config.g of the tool that's going to be used and NOT the previous tool. I just don't know where in the whole process it makes the switch in software. based on the link above, it looks like tpost is the place to put it but if i do, that would mean I can not preheat the next tool to the active temperature before the tool changes (I thought DUET will preheat the next tool even when the current tool is still printing. maybe i am wrong on this). Does that mean there will ALWAYS be a pause between changes where the machine has to wait for the next tool to heat up from standby to active temperature.

fcwilt

@tekstyle said in Tool select at beginning or end of tool change sequence?:

are you referring to this? https://duet3d.dozuki.com/Wiki/Filaments#Section_Custom_per_filament_config_g

Yes.

Yes, I use this currently for each filament I have. After loading a filament on a chosen tool, it will use those parameters in the config.g file.. however, it does not play well with CURA slicer (or any slicer I would think). In CURA, I have to specify what temperature to set the filament and bed temperature.

I have tested Simplify3D, Cura, Prusa and IdeaMaker and they all can work fine with using M703 to execute the current filament config.g file.

I don't use the slicer to set the temperatures at all. The are all set in the filament config.g file along with other parameters, such as the extruder multipler.

Frederick

tekstyle

@fcwilt thats exactly what i want. i plan on having firmware handle all retraction, temp, extrusion multiplier, speed, jerk, accel.

what do you put as default temperature in cura? or do you just uncheck the material drop down list?

fcwilt

@tekstyle said in Tool select at beginning or end of tool change sequence?:

@fcwilt what do you put as default temperature in cura? or do you just uncheck the material drop down list?

Each one of those slicers I mentioned has a way to prevent the generation of temperature setting code. I would have to go back and determine what each one is as I don't remember off the top of my head.

It is necessary to include in the user code section something like M98 P"print_begin.g" so you can include your own startup code.

This is what Cura is currently generating for me:

M109 S0                        ; set extruder temp and but don't wait (no wait with S0)
M82                            ; absolute E moves
M98 P"print_begin.g"           ; invokes this file
G92 E0                         ; set E position
G92 E0                         ; set E position again (have no idea why)
G1 F1800 E-1                   ; do initial retract

As you can see there is nothing there with any meaningful affects on temperature settings.

Frederick

tekstyle

@fcwilt

i added this

echo "tpost" ; tfree, tpre, tpost
t

in my free, pre and post scripts.

to see the behavior during tool change. found it registers the change after running tpost#.g

i added the m703 command in my Tpost.g script to get the filament parameters assigned to the proper tool.

so far so good.