IDEA - dynamic acl/jerk with S3D but settings stored in firmware

dragonn

I used long time with S3D post process to add M204 and M566 to change acl and jerk depending on the part of the print. But now I good an better idea, what about only using M98

  {REPLACE "; inner perimeter\n" "; inner perimeter\nM98 Pinner_perimeter.g\n"}
  {REPLACE "; outer perimeter\n" "; outer perimeter\nM98 Pouter_perimeter.g\n"}
  {REPLACE "; solid layer\n" "; solid layer\nM98 Psolid_layer.g\n"}
  {REPLACE "; infill\n" "; infill\nM98 Pinfill.g\n"}
  {REPLACE "; gap fill\n" "; gap fill\nM98 P gap_fill.g\n"}
  {REPLACE "; skirt\n" "; skirt\nM98 Pskirt.g\n"}

Like that, now in firmware in sys you only need to create files like inner_perimeter.g and others and put desired commands into it.
Advantages:

easier testing, I think it should be possible to adjust values even during printing
settings are independent from slicer, if you change it will apply to old g-codes too

Not tested yet but I don't see why this shouldn't work.

deckingman

By "settings stored in firmware" you mean use macros yes?

dc42

@dragonn said in IDEA - dynamic acl/jerk with S3D but settings stored in firmware:

I used long time with S3D post process to add M204 and M566 to change acl and jerk depending on the part of the print. But now I good an better idea, what about only using M98
  {REPLACE "; inner perimeter\n" "; inner perimeter\nM98 Pinner_perimeter.g\n"}
  {REPLACE "; outer perimeter\n" "; outer perimeter\nM98 Pouter_perimeter.g\n"}
  {REPLACE "; solid layer\n" "; solid layer\nM98 Psolid_layer.g\n"}
  {REPLACE "; infill\n" "; infill\nM98 Pinfill.g\n"}
  {REPLACE "; gap fill\n" "; gap fill\nM98 P gap_fill.g\n"}
  {REPLACE "; skirt\n" "; skirt\nM98 Pskirt.g\n"}
Like that, now in firmware in sys you only need to create files like inner_perimeter.g and others and put desired commands into it.
Advantages:

easier testing, I think it should be possible to adjust values even during printing

settings are independent from slicer, if you change it will apply to old g-codes too

Not tested yet but I don't see why this shouldn't work.

Neat!

dragonn

@deckingman Yeah, exactly. Technical it is stored in firmware

Phaedrux

Cura already has per move jerk and accel settings. Been using it to great effect for a while now. I thought about doing something similar to this to get the same functonality into Slic3r PE.

alt text

deckingman

@dragonn

In that case, I don't see why it wouldn't work. I've started to use macros in my slicer start and end gcode - or more precisely I put calls to macros in the start and end gcode files. The macros themselves have filament specific commands such as hot end and bed temperatures, retraction settings, extrusion multiplier, and things like tool definitions and mixing ratios. That means I can slice an object once but by editing the macro calls, I can print it again using a different filament and/or colour combination without having to re-slice it.

T3P3Tony

@dragonn Yes great idea