Code Monkey home page Code Monkey logo

postprocessingplugin's People

Contributors

alekseisasin avatar amedeebulle avatar awhiemstra avatar bagelorb avatar dim3nsioneer avatar dmwatson avatar electrocbd avatar fieldofview avatar ghostkeeper avatar jackha avatar jpfrancoia avatar lipufei avatar markwal avatar nallath avatar peteruithoven avatar rotzbua avatar samirabaza avatar thopiekar avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

postprocessingplugin's Issues

Remove this repository to prevent confusion.

We have merged the post processing plugin into the main Cura codebase, so this repo is now redundant. Maybe let's remove it to prevent confusion about where to file issues and PRs?

PauseAtHeight: Printing with multiple material types

I was trying to print with multiple types of materials that require different temperatures, on a Ultimaker 2, but I was having big problems when using the PauseAtHeight script as it is.

The problem seems to be that the current change material system of the Ultimaker 2 only asks which material type is inserted after its completely done, which means there is no step where it extrudes the new material at it's proper temperature.
I'm thinking now that this caused that, after the pause, it took another two layers before the material to start flowing properly, which meant that the parts fall apart.

As a short term solution I was thinking of adding a extrusion option to the PauseAtHeight script. This so that it can extrude after having the right material type selected and get a proper material flow going.
One downside will be that there extruded material might end up on the print.
I'll try doing a PR soon, but in the meantime I'm curious about opinions.

Load scripts from non-AppImage location

I'm interested in creating scripts for the PostProcessingPlugin but Cura is too complex to be built by a mere mortal and the plugin doesn't seem to load scripts that are just plain in the file system and is limited to only those in the AppImage.

Please add support to load user scripts from some user accessible location.

PauseAtHeight: raft hight fixed ?

Hi,

Fow a while the pauseAtHeight plugin had an issue: it wouldn't account for the height of the raft, so I had to manually add 1mm to the value of the actual pause.

Yesterday I updated the plugin and found out I have a problem with the height of my pauses. Did someone fix this bug ?

pause at height - fails if added more that once

For one pause at a single given Z this works fine, but if you need a 2nd or 3rd pause at another Z it fails.
if you try to add this plugin 2 or more times it fails by executing all the pauses to the same Z in the gcode and usually it not even close to any of the Z values asked for. It's been this way for years, maybe a note in the tool tips warning against multiple uses would be nice.

Clarify PauseAtHeight retraction

So the Ultimaker2 retracts a bit of material after it changed material. This can currently cause a problem when changing materials during a pause. From @TinkerGnome I understand that to compensate the retraction setting needs to be the same as the end-of-print retraction (20mm by default). See: Ultimaker/Ultimaker2Marlin#117 (comment)

Honestly I don't understand it, since the 4 extrudes in the PauseAtHeight script seem to cancel each other out in the end. Can someone confirm that this works?

Shouldn't 20mm be the default Retraction?
Should I do a PR to explain this in the Retraction setting description?

Allow printer definition to specify postprocessing script with parameters to be automatically run on export

I've been working on Makerbot Replicator 2 compatibility and one of the problems that I've run into is that these printers require the slicing software to insert percentage commands for the printer to show progress.
While this would probably be best handled in the slicer, one way of doing so is with a postprocessing script. Unfortunately though, the user experience of having to manually add a postprocessing script is not all that straightforward and has to be done each time slicing takes place.
It would be great if there was some automated way to do this.

settings do not show in cura-git

I'm not sure if the plugin is intended to work in git builds of cura, or only in regular releases. If that's the case, a hint would be great.

If it is supposed to work, at least in my setup it doesn't: I'm using the AUR (ArchLinux) build of the cura git state (https://github.com/Ultimaker/Cura.git), and while the plugin shows in the menu and I can add scripts to the list, I cannot set (or even see) any values. See the attached screenshot and log.

screenshot_20160628_153714

cura_log.txt

Tweaking a value on Layer 0 doesn't work - Tweaks Layer 1 instead

If Tweak Layer is set to 0, the tweaks are added on Layer 0 (where expected) and on layer 1 (not expected). It also resets the tweaked values right after they are set on layer 0, effectively moving the tweak to layer 1.

In this example, I used Single Layer Behavior. The same problem happens if Keep Value is used instead.

Steps to reproduce

  1. Set Layer Number to 0
  2. Tweak a value

Expected Results

; ...
;LAYER:0
;...
;TweakAtZ V5.1: executed at Layer 0
M117 Printing... tw@L   0
M104 S250.000000 T0
;...
;LAYER:1
;...
;TweakAtZ V5.1: reset on Layer 1
M104 S240.000000 T0

Actual Results

; ...
;LAYER:0
;...
;TweakAtZ V5.1: executed at Layer 0
M117 Printing... tw@L   0
M104 S250.000000 T0
;TweakAtZ V5.1: reset below Layer 0
M104 S240.000000 T0
;LAYER:1
;...
;TweakAtZ V5.1: executed at Layer 1
M117 Printing... tw@L   1
M104 S250.000000 T0
;...
;LAYER:2
;...
;TweakAtZ V5.1: reset on Layer 2
M104 S240.000000 T0

automaticaly add a PostProcessing Script

hello,

it's not really an issue, but I don't find where to post my request.
I wrote a postprocessing script which works well.
I want to use it all the time, but I forget sometimes to load it when I open CURA.

How can I modify PostPressingPlugin.py to automatically load my script ?

my script for exemple is
name : PH1
key : PH2

I tryed to add at the end off def init(self,parent = None):
...
self._script_list.append(self._loaded_scripts"PH2")

but it does not work :(

thanks for your help

regards

Pause at height and redo layers

Hi,

I'm using cura 2.5 beta (downloaded from the website), on Linux.
I have a problem with the pause at height plugin. When I choose to redo some layers (let's say 2 layers) after a pause, I can see in the Gcode that the layers a redone before the pause. It's not the expected behaviour.

UM2O_POC_extraction_cartridge_broken.txt

I attached my gcode. I would like to redo layers 81 and 82 after the pause. But you can see in the Gcode that these layers are redone before the pause. After the pause, the printing resumes at layer 83.

Gcode unaltered directly outputed by Cura.

Is there a way to solve this issue ?

Arbitrary order of the entry boxes?

After I realised the PostProcessPlugin does not keep the order as specified in 'getSettingData' for display, I restarted Cura. After restart I got a different order, then another one after next Cura restart, ...
Could you please remove that random generator? ;-)

PauseAtHeight broken in 2.4

There is a typo in PauseAtHeight - ammount instead of amount

It is a bit strange because it has been fixed in master 6 months ago, but it is still in 2.4 and 2.5 branches for that particular line.

creating to post-processing script

Hi team,

I am looking to create a post processing script that will examine gcode and make some modification to the g0 / g1 x/y values for my DIY printer. I am not quite sure where to start. I tried to edit script directly in C:\Program Files\Cura 2.3\plugins\PostProcessingPlugin\scripts . It would work if I just change a value but if I add additional lines of codes Cura would not recognize the script t all.

Is there are way to create own script and added to cura? Thanks.

TweakAtZ plugin not working in Cura 2.1

Not sure if this is the place to log the issue.

When using the TweakAtZ 5.0 plugin, the generated gcode doesn't output the configured changes.

2016-05-15 10_49_46-text pdf - foxit reader

Notice an error in the cura log.

Script raised the following exception 'bedTemp'

Attached cura log and screenshot of tweakAtZ Settings.
tweakAtZerror.txt

Version on ppa?

@thopiekar I noticed this plugin is included separately in your Cura ppa . I've updated my system, giving me (I think) the latest version of this plugin:

Package: cura-extra-plugin-postprocessing
Version: 2.3.99-truely-2.3.1-0~201611281637~106~ubuntu16.04.1
Priority: optional
Section: science
Source: cura-extra-plugins
Maintainer: Thomas Karl Pietrowski <[email protected]>
Installed-Size: 117 kB
Depends: cura-plugin-api-3
Download-Size: 24,5 kB
APT-Manual-Installed: yes
APT-Sources: http://ppa.launchpad.net/thopiekar/cura/ubuntu xenial/main amd64 Packages
Description: Cura plugin - PostProcessing
 For more info see: https://github.com/nallath/PostProcessingPlugin

But what does this contain? I notice it doesn't include my merged (to master) pull request, which already included in the latest release / tag (https://github.com/nallath/PostProcessingPlugin/releases/tag/2.3.1).

I can never wrap my head around Lauchpad... I'd love to get more information about cura-extra-plugins which seems to be the source of cura-extra-plugin-postprocessing. After clicking through lot's of links I found this page: http://ppa.launchpad.net/thopiekar/cura/ubuntu/pool/main/c/cura-extra-plugins/ which indicates that this plugin was modified only days ago.
Is there a separate git repo for cura-extra-plugins?

Gcode does not re-postprocess after changing postprocessing script setting values

Due to the logic at https://github.com/nallath/PostProcessingPlugin/blob/master/PostProcessingPlugin.py#L59, it is assumed that once gcode is postprocessed it won't change. However, if gcode is in the buffer and changes to the postprocessing script setting values are made, those changes will not reflect in the output.

This was previously reported here: Ultimaker/Cura#1856

My suggestion is to just remove that logic that looks for ;POSTPROCESSED in the gcode, as it doesn't seem straightforward to tell if the settings were changed — but perhaps there is a way to do this.

PauseAtHeight: E instructions after pause

Hi,

I don't understand something. I use the PauseAtHeight plugin very often. Here is a sample of what it generates:

G1 F2100 E94.54111
G0 F2400 X154.614 Y82.071
G0 X152.988 Y81.313
G0 X151.244 Y80.741
G0 X149.274 Y80.371
G0 X116.957 Y75.362
G0 X114.566 Y75.211
G0 X113.119 Y75.263
G0 X110.771 Y75.561
G0 X109.369 Y75.885
G0 X107.123 Y76.62
G0 X104.922 Y77.65
G0 X103.746 Y78.347
G0 X94.384 Y85.158
G0 X90.7 Y86.864
G0 X83.301 Y84.582
G0 X81.941 Y84.321
G0 X80.562 Y84.235
G0 X79.184 Y84.321
G0 X72.221 Y85.181
G0 X72.158 Y85.104
;TIME_ELAPSED:57957.372119
;TYPE:CUSTOM
;added code by post processing
;script: PauseAtHeight.py
;current z: 51.580000 
M83
G1 E-30.000000 F1500.000000
G1 Z52.580000 F300
G1 X190.000000 Y190.000000 F9000
M84 E0
M104 S0; standby temperature
M0 ;Do the actual pause
M109 S260; resume temperature
G1 E30.000000 F1500.000000
G1 E100.000000 F199.998000
G1 Z52.580000 F300
G1 X72.158000 Y85.104000 F9000
G1 F9000
M82
G92 E94.541110
;LAYER:166
G0 X72.158 Y85.104 Z51.28
M204 S1000
M205 X10 Y10
;TYPE:WALL-INNER
G1 F900 E6.79673
G1 F600 X72.823 Y84.588 E6.83235
G1 X73.497 Y84.13 E6.86684
G1 X74.226 Y83.7 E6.90266

As you can see before the pause the extruder is set to position 94.54111. During the pause, extruder is set to relative mode, does some stuff, and then reset to absolute mode. Previous position is then restored (G92 E94.541110).

But then, the extruder is set to odd values:

;TYPE:WALL-INNER
G1 F900 E6.79673

It seems after the pause the absolute values are reset.

I'm asking this question as an introduction for a bigger problem: after the pause and after the printhead moves back into position, some material is retracted. I observed that for all my prints. The amount of material retracted varies. I've been chasing this bug for some time now.

Feature request: checkboxes and comboboxes

Hi Nallath

If you add the possibility to have checkboxes and comboboxes as input fields (cf. legacy Cura) it would be possible to implement e.g. TweakAtZ 4.0.x for the new Cura. Without it only a TweakAtZ 3.x would be possible.

thx,
Dim3nsioneer

'active_if' lets PostProcessingPlugin hang

When an 'active_if' element is used within the settings the PostProcessingPlugin dialog doesn't open. It's the same behavior as for any syntax error within the script. Unfortunately Cura/PostProcessingPlugin is extremely non-verbose... nothing in Cura.log.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.