Makro with variables

sunToxx

It would select the filament config profile, according to the selected option in the "Filament Type" drop down menu in Prusaslicer in the active Filament profile, for example?

sunToxx

So i would have to have, eg pla_silk or pla_blue or whatever, as an option in that filament type drop down menu, in the filament profiles in Prusaslicer?

engikeneer

@suntoxx you select the filament that you have loaded with a dropdown in DWC. That way it is not at all embedded in the gcode file s9 you can use the same file for multiple different filaments

Schild0r

@engikeneer said in Makro with variables:

@suntoxx you select the filament that you have loaded with a dropdown in DWC. That way it is not at all embedded in the gcode file s9 you can use the same file for multiple different filaments

...the same * Slicer Filament Setting * for multiple different filaments.

As long as you set everything (temperatures, fan speeds, offsets,...) in the RRF filament config. You only need to call M703 for that to apply (regardless of the filament that is being loaded)

@sunToxx you can edit a comment btw

sunToxx

@engikeneer said in Makro with variables:

@suntoxx you select the filament that you have loaded with a dropdown in DWC. That way it is not at all embedded in the gcode file s9 you can use the same file for multiple different filaments

Where do I find this dropdown menu in duet web control? I only know the one in Prusaslicer Filament settings, as part of the selected filament profile. In dwc I only have a filament section, where i can edit the configs it seems. Do i need a different version or a plugin? This setting would override any slicer selected filament type selection?

@schild0r said in Makro with variables:

@engikeneer said in Makro with variables:

@suntoxx you select the filament that you have loaded with a dropdown in DWC. That way it is not at all embedded in the gcode file s9 you can use the same file for multiple different filaments

...the same * Slicer Filament Setting * for multiple different filaments.

As long as you set everything (temperatures, fan speeds, offsets,...) in the RRF filament config. You only need to call M703 for that to apply (regardless of the filament that is being loaded)

@sunToxx you can edit a comment btw

Sorry, will do

This is a bit confusing for a beginner. M703 says it applies the configuration of the currently loaded (as far as the printer knows) filament. So off course it doenst matter which filament is currently in the extruder, but it does matter what filament is loaded according to the software and it applies the config of the according filament that is listed in the filaments section of dwc? So I don't quite understand why you say "regardless of the filament being loaded".

Schild0r

@suntoxx it is in the dashboard right below the name of the tool. There should be a button "load filament" and if you click it, it should give you a selection of all the filaments you have created in the firmware.

So not in the left toolbar but where you would change your tool temperature manually at any time

For me it says PLA because it is currently loaded.
You can also load/unload filaments via gcodes M701 S"filamentname" and M702 and it will update this in DWC as well

sunToxx

@schild0r Oh, I missed that one, thanks! This seems to trigger a macro, which is not in my macro folder. That must be the filament specific macro in the load.g and unload.g files of the filament.

So I have to trigger the unload/change filament in DWC and can then continue the process on the printer display, or type for example
M702 and then M701 S"Pla_Silk"
directly into the printer display?

So if I always use this method to change my filaments, it always knows what filament is active (also after power off) and it will always override all slicer settings that might collide with the filament settings in the filament's config.g?

This is nice!

So I could also create macros in the main macro folder with for example, M702, M701 S"Pla" or M701 S"PETG" to quickly change between my most used filaments, without using dwc or typing gcodes? As it appears that the first 4 of them are displayed on the duet display.

I can just put the M703 command at the end of the regular custom Caribou Start gcode script for prusaslicer?

sunToxx

@schild0r I have tried it out and it seems to work, except for the fact that he applies the M290 Z0.08 i entered into the PETG config.g two times. Once shortly after he starts, before he probes the middle and then once more after creating the heightmap, right when he starts doing the first layer. So he ends up with an 0.16 offset instead of 0.08.

Any idea what's going on there? I removed the m290 custom gcode from the filament section in prusaslicer and sliced the file again. I checked the sliced gcode, there are no m290 commands in there. The m703 command is in there 2 times, once at the start and once in the prusaslicer config section at the end.

I just use half the value for now, but that is probably not the way to go.

dc42

@suntoxx said in Makro with variables:

I have tried it out and it seems to work, except for the fact that he applies the M290 Z0.08 i entered into the PETG config.g two times. Once shortly after he starts, before he probes the middle and then once more after creating the heightmap, right when he starts doing the first layer. So he ends up with an 0.16 offset instead of 0.08.

Use the R0 parameter in the M290 command to set absolute instead of relative babystepping.

sunToxx

@dc42 said in Makro with variables:

Use the R0 parameter in the M290 command to set absolute instead of relative babystepping.

I already printed with half the value, but this is much better and makes it perfect, thanks!

Thanks for the help @everyone, this is exactly what I have been looking for!

Could someone maybe post the code of a well filled filament config.g so i can look at it? I am specifically wondering how to set first layer and other layers temperature in a way that all slicers understand, as they seem to utilize differently named variables. That's already more than I aimed for, but I like the idea of having all my filament configuration in one place on the printer, a lot.