Is there a way to save post processing plugin state?

[brzasshopper 1]

So I built a simple object in openscad, it is a topless cube of (parametric) size with (parametric) wall thickness that has a mark on it every (parametric) mm. My theory was to use it for generating test cubes for printing extrusion and temperature towers.

I have reproduced this code below, despite the fact that it is not germane to this in case anyone is interested.

In any case, the obvious question is how do you get it to get it to change temperatures or extrusion percentage every markOff (3) mm.

So I decided to use a bunch of "tweakatz" post processing calls. I added all the calls, sliced, and saved a project - and when I reloaded the project, it didn't reload my tweaks.

I had anticipated editing those calls - to change extrusion percentage, to produce a different range for ABS, Nylon, even PETG. Do I really have to add a bunch of these every time I want to do this with an object with different wall thicknesses, different temperatures, and the like?

I have looked, I don't see how to do this. Ancient versions of Cura used to save these, I think with the printer definition. They should be saved somewhere, maybe in the project.

Is this just another situation where I don't know the software that well? I have looked around the questions here and the doc, I found the explanation of how to use post processing, but nothing explains how to save the settings.

 

// This code is original code by Nicholas J. Simicich.// The copyright of this code is disclaimed and dedicated// to the public.cubeThickness = 0.48; // set to extruder size plus 20%cubeBase = true;cubeBaseThickness=0.5; // fill in the bottom.cubeHeight = 40; // As tall or short as you want.cubeSize = 15;  // typically 10mm or 20mm, your choice.// This allows you to divide the test cube into bands, marked by small // square protrusions on the outside of the tower.  We leave a minimum// of markOff clear at the top of the tower for measurements.// This test cube can't automatically change extrusion percentage as// we step up, nor can it change temperatures.  That can be handled in// kisslicer or using a cura add-on script very easily.// The marks are little triangular shelves.  They are supposed to// start the same width as the wall and then grow until they are // markSize larger.  A good first choice is cubeThickness.mark = true;markSize=cubeThickness;markOff = 3;// The above says produce a cube that is 15 by 15 by 40, with a 0.5mm // thick base.  The walls should be 0.48.mm thick.  Everything will be as// square as possible.module ring(size=cubeSize,markSize=1) {   difference() {       linear_extrude(height=markSize,            scale=(cubeSize+markSize)/cubeSize, convexity=25) {           square(cubeSize,true);           }       cube([cubeSize,cubeSize,markSize*4], true);   } // difference} // module// create the cube bodylinear_extrude(height=cubeHeight) {   difference() {       square(cubeSize,true);       offset(delta=-1*cubeThickness)           square(cubeSize,true);   } // difference} // linear_extrude// create the optional baseif(cubeBase) {   cube([cubeSize,cubeSize,cubeBaseThickness],true);} // if// create the optional marks on the tube sideif(mark) {   for(i = [markOff:markOff:cubeHeight-markOff]) {       translate([0,0,i-1]) ring(cubeSize,markSize);   }}

 

[nallath 1,124]

New Cura doesn't have a way to save post processing scripts. I'm not quite sure if we will ever have it though. It's not very high on the feature list.

[Jarery 0]

Interesting. I'm new to 3d printing, but pretty much everywhere says to run temp calibration towers with every new role of filament.

I think the tweakatz post processing scripts are brilliant and have used them a lot recently. But I also have already become tired of inputting the same 10 scripts for every roll, with the same Z height and same temps.

I then have to delete them after every temp calibration tower print since if they are there they get used. Its hard to imagine I'm alone in this frustration, but perhaps.

How about a checkbox beside each one that if unchecked doesn't get processed. Then they just save with the system like they do currently and no worries. When i want, i open the screen and activate the ones I want to run.

New Cura doesn't have a way to save post processing scripts. I'm not quite sure if we will ever have it though. It's not very high on the feature list.

[i00 0]

I really want this feature too...

Nice to be able to print layer 1 @ 210 and then down to 180 for the rest of the print, for good plate adhesion and minimal strings between objects.

[gMaker 0]

Same here. It would be a great start to be able to export and import the post processing list. That would make it a huge step less tedious.

[kmanstudios 1,120]

Being Devil's Advocate here, but shouldn't TweakatZ and other plugins be responsible for import and export of scripted values so they can be retrieved independently?

[gMaker 0]

Being Devil's Advocate here, but shouldn't TweakatZ and other plugins be responsible for import and export of scripted values so they can be retrieved independently?

No, I want to be able to export a dozen of TweakatZ instances. I don't think the plugin should reach beyond it's own instance.

It's really the responsibility of the 'post processing' facility.

Edited November 28, 2017 by Guest

[24c 1]

Has there been any update on this position? I was slightly surprised that I had to enter my post processing scripts again, when I thought they might be saved with the profile.

[mike-truly 3]

I also want them saved with the profile (as in the old Cura).  I also would like the option to save them independantly.  But having to re-enter these setups every time the profile is opened is absurd.

 

Thanks!

 

Mike

 

[24c 1]

I have to agree, and I wasn't expecting this at all, as Simplify3D saves them in its FFF file, and that is linked to the profile so to speak.

Oh well, worst case I suppose I can phone a friend and collate my search and replace into some generic post processing script, that will manipulate the Cura file output and move it elsewhere. Shame, as I've got Cura working with my QuickFill equipped Robox, and using both nozzles at will in different combinations, and controlling the needle valves at the nozzles too.

 

[AbeFM 35]

Another vote for saving these. Or edit the script to accept pasted data from a spreadsheet.

[24c 1]

@AbeFM This is what the Simplify3D interface is like, and you can cut & paste as well as save.

 

 

[ahoeben 1,991]

There is a pull request by @ghostkeeper that makes postprocessing settings “permanent”. It has not been merged sofar, but it could still be part of Cura 3.3

[24c 1]

Very good @ahoeben and @ghostkeeper that's one less thing to do... potentially. Thanks for the feedback.

Edited February 23, 2018 by 24c

[24c 1]

@ahoeben is this the pull request? https://github.com/Ultimaker/Cura/pull/3229 If so, is it possible further down the line, assuming these are saved and applied on a per printer preference, which seems sensible to me, that there might be plans to view these in some sort of dialog box? Possibly like this? or maybe thinking afterwards each instance of say "Search and Replace" could be given a more useful name in this example below...

 

@ghostkeeper a bit like this, so the user could track the scripts easier. Just an idea.  

 

Edited February 24, 2018 by 24c
get link right

[ghostkeeper 105]

That pull request is indeed the one, 24c. Keep track of that link

 

Giving Search and Replace scripts a custom name and a sort of summary like in Simplify3D would be nice, I agree, but it doesn't jive well with the other post-processing scripts in there. If you don't use Search and Replace, that summary basically just repeats the list of scripts above it.

[24c 1]

@ghostkeeper totally agree about the summary box I drew, but I sort of did think along the S3D lines when I initially posted, and then realised it was duplicating what the script types summary above was doing, especially if you added all the other options not just search and replace. The "relatable name" was the afterthought, and would be more useful if you are using the same script several times, so you could keep track of things.

 

Maybe that white box summary area should be retitled, conditional post processing scripts  Thanks for the update, as everything in Cura 3.2 is slicing and post processing nicely, when I look at the gcode, apart from that one conditional I need, but I have a Python script to play with, so maybe I can finish what I started a few days ago, and test this out in the meantime.

[Antiheadshot 0]

Just noticed that the post processing steps are attached to the printer configuration. So you could have a separate profile with the same printer but different pps.

[bartwybouw 0]

What is the current status of this?

I was disappearing in down the same rathole ...

 

Was S3D user, but starting to love Cura 4, but this is something that is boggling my mind why this is not implemented. Kind-of renders the whole post-processing stuff useless for any serious use ...

[nallath 1,124]

The pull request was merged well over a year ago, so it's been in Cura for a while now (up and including 4.0).

 

What is it exactly that you are missing?

[ahoeben 1,991]

Post processing script state is now stored between sessions. Has been so since Cura 3.3

[Kazymandias 0]

Not good enough. I want to create a file to upload to Thingify, that will let other uses interrupt the build in the middle, without them having to learn how to do it.