The first three lines are the commands to change to the d: drive, and then to change directory cd to where GCodeClean lives on my system. Obviously yours will be different.
And then finally the cli command itself. Here I entered it without any options, and when you do that it shows help text for all of the available options.
More commonly, what you would enter would look something like this: cli --filename Samples\Facade\Facade.nc --minimise soft
The command above tells cli to get the file Facade.nc located in a sub-folder Samples\Facade and to do soft minimisation of the output GCode
Thanks! I have a large area to pocket with some intricate details. Using carbide create to pocket using a 1/4 bit then pocket using an 1/8" bit would gcodeclean clean up the duplicate paths? Thanks
Not really - It’s a line by line cleaner. It’s designed to simplify lines and arcs within tolerances.
However, it does have an --annotate option which adds comments to lines to help you understand what each one does, that can help with editing the gcode file by hand (although you should always be careful with that)
What I’ve done sometimes to reduce commands is to do two drawings. So one with the pocket for instance, and then another with a simple path. Then either run them as two separate GCode files, or use an editor to merge them into one.
Sign up for the Carbide3D forum, then ask how to do this in the Carbide Create sub forum. Will Adams will explain it much better than I can. Then use GCodeClean to clean up arcs and change rapids to retracts to improve the resulting gcode even more
One change that you will need to make is to put the whole file path in double quotes - where there are spaces in a value on a command line then that value needs to be in quotes.
e.g. cli --filename "C:\Users\Tim Seidlitz\Desktop\weapons pics\widow\somefilename.gc"
Tried using it again on Windows 10. Gcode created by carbide create. Ran zClamp and opened the newly saved file in webcontrol it was just the contour and not the pocket.
PS - In Windows you can go Windows Key+Shift+S (+Shift+S) to snip a part of the screen (or even the whole screen) - then just cut-n-paste it into anything. no need to use your phone
Minor housekeeping - v0.9.4 got the dedupLinear functionality working for an arbitrary number of colinear movements, but there was still multiple calls to dedupLinear in the main program, when only one would now be required. So the excess calls were removed.
Better handling of very terse GCode input (thanks @TimS for finding it and providing me with a code sample). This was fixed by moving the call to Augment much higher up the list, thereby injecting the commands necessary.
BREAKING CHANGE - addition of lineNumbers command line option. Normal behaviour is now to remove any line numbers from the GCode (they are NOT recommended). But by turning this flag on line numbers will be preserved (). Please don’t use line numbers, this is GCode not BASIC, but if you must, go out and take a programming course.
It seems to be working, I haven’t cut with it yet, will this weekend. Is there a cheatsheet that explains in newbie terms what each option really does? Thanks
run it manually on a test file. I’m pretty sure that you have to tell it the
name of the output file (or it creates it from the input file)
it just does not make sense to try to overwrite the file that you are reading,
that is just inherently unreliable. But it does happen, which is why I’m only
99% sure
GCodeClean takes the input filename and inserts a -gcc before the end. And if you feed that file back through it (although you shouldn’t because it is a one pass cleaner) then it will insert -gcc again.
+Shift+S) to snip a part of the screen (or even the whole screen) - then just cut-n-paste it into anything. no need to use your phone
). Please don’t use line numbers, this is GCode not BASIC, but if you must, go out and take a programming course.
