GCodeClean steps up to v1.2.3 because ... another bug

Split Files Into Individual Cutting Actions :tada:

Yep, the split command now has functionality.

So, you can take your GCode file, clean it - which sets things up - and then split it into individual cutting actions.

But why? I hear you mumble unenthuasticially over your :beer: / :coffee:

Two main reasons

  1. This lets you extract some key cutting step from an existing GCode file as a self-contained Gcode file that you can run on its own.
  2. This is a key precursor for ā€˜travellingā€™ optimisation. ie. where you go between cuts.

As usual, please let me know if you find bugs.

An important note: previously you just ran GCodeClean through the command line, and it only did one thing. Now, it has two ā€˜commandsā€™ clean (the original) and split (the new). It does not (yet) do ā€˜all the thingsā€™ in one go - and that is not a priority. Solving the ā€˜travellingā€™ optimisation and back-porting to TypeScript (for inclusion with the new Maslow 4 code) are my priorities.

Release v1.2.0 - File Splitting Ā· md8n/GCodeClean (github.com)

2 Likes

And now v1.2.1 - with performance improvements

Read about it here Release Performance improvements - and getting git to play nice(r) Ā· md8n/GCodeClean (github.com)

2 Likes

But bugs :unamused: so now itā€™s v1.2.2

Go to the usual Release page in Github to get the executables; for Linux, Pi (Linux-arm) and Windows

So yeah, bugs with the deep copy code I had introduced - seriously if I had run my tests I would have found them - you would think Iā€™d have learned by now.

Also cleaned up some of the ā€œmagic charactersā€ throughout the code. These were the for some of the leading letters of certain GCode ā€˜wordsā€™.

I came across the weird ā€˜block deleteā€™ character in the NIST GCode spec. So Iā€™ve added support for that. Iā€™m guessing itā€™s not something that a Maslow will ever use but who knows :person_shrugging: And Iā€™ve added one test for it, and updated another.

Also Iā€™ve added support for putting the tool number into the travelling comment in the cleaned file, and into the filename for each cutting path split out of a file.

2 Likes

But another bug, so now its v1.2.3

I found a weird bug with the method that deletes superfluous G0 commands. Sometimes it deleted G0 commands that werenā€™t superfluous - oops.

Also, I got stuck into the ā€˜publishā€™ process again, and I think Iā€™ve finally got things to a much better place.

GCodeClean now comes as a single executable file, youā€™ll find a total of 3 files in the zip folder.

The total size is a lot smaller. Release v1.2.3 - Bug fix for ā€˜eliminate needless travellingā€™ Ā· md8n/GCodeClean (github.com)

And Iā€™m still working on the ā€˜Travelling Salesmanā€™ issue - finding a way to better organise the travelling between cutting paths.

1 Like