5axes / cura-postprocessing-scripts Goto Github PK

Hi im trying to use the Multibrim.py script, i have tried with cura versions 4.13.1 and 5.0 but it does not work, theres no extra brims in the preview, please help i really wanna use this post processing script

Multibrim Successfully installed on cura 4.13.1 and cura 5.0, Multibrim tested and works on cura 4.13.1 but it does not work on cura 5.0, no extra brim is printed, can we please get an updated script for cura 5.0 ?? i will happily make a donation

Does this simply add the Cura settings to the gcode or can you somehow extract these into Cura as well?

I ask because people always want to know my settings so they can use them and often Cura fails to import profiles exported from a different version.

Either way it’s a beautiful script and I thank you.

Hi.
I've been looking for days for a way to do this then I found FastFirstInfill only to find its not working.
Is it because of changes made to 5.x? is there any way to fix it possibly?

Hello @5axes
I have been fooling around with Python and post-processors. I have a re-write of "Insert at Layer Change" that is finished and works. I added support for multi-line insertions, start and end layers, and options for insertion at every layer, every 2nd, 3rd, 5th, 10th, 25th, 50th and 100th (that seemed like enough). I'm not savvy enough to do a proper pull-request and at any rate it could use another set of eyeballs as I'm not good with Python.
The other project is a work-in-progress and I've taken it as far as I can. It's the Cooling Profile post-processor. I've got it loading properly and the dialog boxes appear to be correct. It doesn't work though. I think it's throwing errors when splitting a string and moving the data to a list "Layer/FanPercentage" (as "1123/50"). I think I have a good start to it and maybe you would care to take over or maybe steer me in the right direction.
You will notice that I've modestly named them after myself. That was actually to keep from over-writing the stock files.
If you want to disregard this I'll understand..

GregVInsertAtLayerChange.zip

GregVCoolingProfile.zip

My thoughts on the cooling profile design:
Remove all the M106 lines from the file.
Pull in {machine_scale_fan_speed_zero_to_one} from Cura.
If "by Layer" then the strings are split and the list is created. My thought was that it should be fixed length and so I've entered place keepers if a user doesn't need al 12 insertion options. As each value is appended to the list the actual fan speed is calculated and appended instead of the percent. There is an "if" for fan_mode 0 to 1 or 0 to 255.
As the gcode is parsed - lines with ";LAYER:" trigger a search through the list (called fan_array in the code) for a match. When a layer match is found then the new M106 string is put together and inserted.
If the user selects "By Feature" then the Layer setting boxes are disabled and the By Feature boxes are enabled. The fan speed for each feature is stored. There is a possible start and end layer. The data is parsed and every time a "TYPE:SKIRT" or "TYPE:WALL:INNER", etc. is encountered then the corresponding fan line is assembled and inserted. This goes on from the Start Layer to either the user defined End Layer, or to the end of the file. If the user selected an "end layer" than at that layer the "Final Fan Speed" is inserted.
Lastly, in either case, since all the M106 lines were removed (or maybe commented out) then M106 S0 needs to be inserted when ";End of Gcode" line is encountered.

So that's it. I've typed a little bit. All that's left is everything else.

I'd appreciate if you would let me know what you think.

Greg (Valiant) Foresi

the FanIroning.py are not working on cura 5.3.1 if you can please make an bugfix

Is there a way to show a popup menu to confirm with a yes or no if the script has to run?

Tryed with QT6 but failed

@IcarianOM at Telegram if this is not the correct way to ask this questions

Not sure if I am doing something wrong. I put the script in the scripts directory but it doesn't give the same output as it did in Cura v4.13.1
I attached a screenshot of the v5.4 window showing the plugin active as well as the v4.13.1 and v5.4 outputs.
The 4.13.1 output gives all the settings in plain english while the v5.4 doesn't.
I tried v5.3 as well and checked my gcode files and ever since v5.0 it looks like it went missing.
I am using Win11 Pro 64BIt v22H2
Can you assist ?

Hi, I was using your genius post processing script atm.
In particular the TempFanTower.
Was wondering if Change Layer and Change Layer Offset meant to be in mm cuz it's a float and layers alwas int. So i was struggeling a bit and want to check inside the code whats going on.

Whats about changing them into int? Or any specific reasons why it is a float? At the end you're casting it back to a int.
Temp and TempIncrement may seems okay with float.

Looking forward to discuss about :-) Hope it's okay that I use the issue-tool

Lars

I'm using:
Windows 11Pro 23H2
Cura 5.7.0
Ultimaker S5 gen1 printer with material station
_Edit:
I'm using AA 0,8mm printcores in both extruders and a 0,2mm layer height.
I've set the script settings to:

• offset layer 8
• start with 265 degrees C
• increments from 5 degrees C
• change at layerheight 50_

I used this model to perform a temperature test for PETG filament. I ran the post processing script: TempFanTower and set the settings...

I ran the test and noticed several unwanted temperature changes:

I unpacked the *.UFP file and looked at the Gcode and saw the added temperature changes as 'M140 S' but also other temperature changes also M104 S, probably generated by Cura (could't find out why).

I looked at the TempFanTower.py script on github and noticed there isn't a routine that does a check if there are more M104 S codes in between the added temperature settings for every layer change. It should do that.

Furthermore it's better to use the M109 R command; this waits for the nozzle to reach the setted temperature before moving on and it does this for both cooling off or heating up to that temperature (see here)

The retraction tower only goes to 5mm. I need up to 7mm. I followed the instructions to open Post Processing Script. I changed the value from 5 to 7. How does it save? I clicked on close. Closed Cura (5.1), reopened it and it still is only 5 tall(5mm). Now by the slice button, there is a </>1 next to it.

If I click on the </>1 it goes back to the Post Processing Script with the change made. But it doesn't change the tower.

The description for "Pause Layer" says "Enter the Number of the LAST layer you want to finish prior to the pause. Note that 0 is the first layer..."

Seems to me it doesn't work this way. Making 4 layers labels, the background being two layers, and the text being two layers, have to enter 2 in order to get text printed as third and fourth layers. 1+2 = background, 3+4 = text ; same numbering as Cura preview.

Shouldn't the help bubble say "Note that 1 is the first layer" ?