itsMrJimbo
-
Posts
2 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by itsMrJimbo
-
-
Good evening all, I'm trying to implement the new Input Shaping calculation test print using Marlin 2.1.2 - Marlin Source here: https://marlinfw.org/docs/gcode/M593.html
My question is around how Cura functions when trying to use a "Insert at layer change" post processing script, specifically 'after' as advised in the above marlin link, the function is just inserted, rather than calculated. Is it possible for Cura to view the function and enact it accordingly? I've tried slicing in Prusa Slicer which generates this for example:
"G1 Z42.000 F720
;AFTER_LAYER_CHANGE
;42.2
M593 F46.5152 ; Hz Input Shaping Test"which shows that the function was calculated properly (based on layer number) and the line edited accordingly to change the F value, however in Cura, the function isn't calculated, so you get this:
;TIME_ELAPSED:3459.382106
M593 F{(layer < 2 ? 0 : 15 + 45.0 * (layer - 2) / 297)} ; Hz Input Shaping TestUnfortunately, Prusa slicer isn't currently playing nicely with my machine, and I'd rather use Cura as I do for all my printing.
So really what I'd like to know, is this just an issue that the format for the macro/function is not correct for Cura, or is it not possible for functions/macros to be calculated by Cura? I have tried both the function examples given by Marlin, but get the same issue as above, it's just the raw function inserted into the Gcode. I'm not at all familiar with coding and naming terminology so I'm not sure if this is something that is at all possible using Cura or a fairly simple macro change.
Thanks in advance for the help!
James
Cura 5.2.1 GCODE macro/function not post processing correctly
in UltiMaker Cura
Posted
Thanks for the help Mari, confirm I'm on 5.2.1
Oddly enough the { and } work within my start Gcode just fine (e.g.:
M140 S{material_bed_temperature_layer_0}
M104 S{material_print_temperature_layer_0}
as this was one of the first things that PrusaSlicer complained about when I tried to configure it using my existing start code.
I was wondering if this might be the case. I can confirm it works in PrusaSlicer as my example above, the function generates an F value based on the calculations and inserts at each layer.
As a work around I may try to slice it like a temperature tower just with a range of M593 F values rather than temperature changes.