norpchen / processgcode Goto Github PK

I wanted to use a Customizable Temp Calibration Tower.
Cura has a TweakAtZ feature that works, but the problem is that TweakAtZ settings are not saved.

So instead I hacked your code to do something similar:
process_g_code.py -i i.gcode --temperatureladder "3:200,13:202,23:204,33:206,43:208,Zn:Tn" -o o.gcode

The hack requires that a temperature is 'injected' at each layer before the temp ladder is applied:
process_g_code.py -i i.gcode --inject t200.gcode zheight 3 -o o.gcode

The code is still a bit rough around the edges (was a long time since I did anything python)

Question is, is this something you want to include (and fixup proper) in the repository?

Hey,
I don't know why, but after processing my gcode with your tool, your tool always add temp command into my gcode, that I don't want.

I tried using -j and -n to set my wanted Temperature, but it just changes my temp settings to 170C...

Is there a Way to turn it of?

Best Regards

Hi Lars,
Thank you for your excellent gcode manipulator script. This saved my day on a daily basis. But one drawback is that your tool assumes G2/G3 gcodes as any other linear movement such as G0/G1 and as a result behaves incorrectly. Think of a full (or quasi-full) circle. This has to be split by four since there may be up to 4 direction changes around the path. Only after then "atomic" arcs can be processed similar to a straight G0/G1 line and same linear backlash compensation functions could be applied through. Do you have any plans to alter and update arc part of your code?
Cheers

I'm currently searching for a proper backlash compensation gcode post-processor solution.
I have tested your post-processor and this guy's AntiBacklash solution.

Using your gcode-processor I'm getting some weird results, that don't make sense.

• I've highlighted them in these screenshots
• You can also compare them to the gcode generated by the AntiBacklash tool that I describe below.
  

I generated the gcode using the following command:
python3 process_g_code.py -i bc-small-x0000-y0000-G90.gcode -o bc-small-x0350-y0400-G90-gcodeproc.gcode --xc 0.350 --yc 0.40

You can find the gcode in the gcode-samples.zip I provided. In there you'll find:

• bc-small-x0000-y0000-G90.gcode (baseline without any backlash compensation)
• bc-small-x0350-y0400-G90-abl.gcode (generated gcode using AntiBacklash.exe)
• bc-small-x0350-y0400-G90-gcodeproc.gcode (generated gcode using process_g_code.py)

Is there something I am missing regarding the use of process_g_code.py? Appreciate any help :)

regarding the AntiBacklash.exe tool

Using the AntiBacklash I'm getting very good results, and the generated gcode makes sense. But...

• The problem with the AntiBacklash solution is that the tool needs some developer love in order to be scriptable using input/output as a CURA's post-processing solution. Without changing the underlying code, it is a valid manual solution, the caveat is that it can't be automated.