...And the Travelling Salesman arrives at GCodeClean v1.3.0

I was also thinking that there was a bug because you had a T1 at the top of your GCode. But the ‘travelling’ comment showed the tool as notset.

Then I reviewed my code and realised that your GCode had no M6 (tool change) after the T1 (tool select), so technically the active tool was ‘not set’

Office Dishrack.nc (67.2 KB)

I’m not sure what’s giong on there. Is it still happening? I can’t replicate that

I still get Sorry an error has occurred, so it must be me

1 Like

Weird! If you have any idea what it is or if want me to try something let me know

Dishrack-gcc-ts.nc (78.1 KB)
Yep - and it works for me.

1 Like

It happens on both my Windows laptop and a Flex 5i chromebook, so it could be either my account here or something to do with chrome which is on both. Let me give M$ Edge a try.

Same think. Guessing it’s something related to my account here, although I can’t find anything in the settings. I haven’t tried firefox in years, I’ll try that when it finishes updating

1 Like

ChipCarve-TB11.nc (45.9 KB)

It’s chrome style browser related, FF looks like it works. Odd. Guess there was a reason I never removed Firefox :slight_smile:

1 Like

Interesting. That makes sense that I didn’t see it then because I’m on Firefox.

Hopefully Discourse gets it fixed soon because I imagine that most of us are using chrome style browsers at the point so it’s going to be a common problem

Lee

I got around to doing some more cuts, using 1.3.3. similar to the names I did above. Happy to report that depth increments were cut in order. Now, I have to check out the GUI

2 Likes

@md8n

Is this still the most current version?

Still using it and still very pleased.

If anyone is new to the maslow, check out Lee’s GcodeClean, it saves me a ton of cutting time by optimizing cut paths and reducing traveling. Works great for off shape pockets like those around lettering.

1 Like

Just discovered this thread and…color me “intrigued.”

So far, my work has been:

  1. Assemble my Maslow 4
  2. Get it working
  3. Get it working reliably
  4. Cut lots of profiles in sheet stock for set pieces

If, however, this might reduce the “mileage” when doing large cuts (and thereby reduce cut times), that will be a nice addition going forward.

In my workflow, would this look something like:

  1. Design (I use Fusion)
  2. Tool paths (Fusion Manufacture environment)
  3. Post-process (using Maslow Post-process or in Fusion Manufacture)
  4. Run GCodeClean on resulting NC file (I’m not clear yet on the steps—is it ‘clean,’ ‘split,’ ‘merge?’)
  5. Run output of ‘merge’ on Maslow 4?

This community is so awesome! I’ve learned so much!

That’s part of the reason why I bumped it.

You can see the visual reduction in travel in my post above.

2 Likes

yep, and then yep

1 Like

It is.

I am planning to do an upgrade of all the 3rd party libraries it uses sometime soon, and then look to switch over to using a different framework for the UI (although the console version won’t change).

However, all of that requires time, and my current focus is chasing another income stream. So it’s waiting while my focus is elsewhere. Currently my M4 is being used for templates for furniture - which might start making an income before the end of this year.

PS. programmer needs a job …

This does a lot in its own right. Quite frankly almost all GCode generated is a pile of :poop: (just of different flavours). Whereas GCodeClean wipes up a lot of this mess and attempts to ‘standardise’ it (or is that ‘standardize’?)

It will usually reduce the number of lines of GCode, although not always. However, it will definitely leave you with GCode that’s in a much more consistent format that reflects actual CNC processing operations.

2 Likes

Copy. Just got the maslow set up after the move and after a few cuts. I was curious if you had another version that needed testing. This version works great!

I’ve been playing with this, and “Clean” works fine, but then when I try to run the cleaned gcode file through “Split” the program says that the file has not been pre-processed with a Clean command. (Even though it is the new file that Clean created a moment before.)

The clean command renames the file. You have to split the new file. Then merge the created folder. Are you using the new file name. I have used it >100 times without issues. However, I don’t split/merge for contours only pockets

2 Likes

Yes, when I try to split, I am changing the filename parameter to the newly created/cleaned file. The cleaned file adds “-gcc” to the end of the filename, and that’s the file I’m trying to split. It still tells me that the file has not been cleaned though. I’ve tried with a couple different files now and same results.

Here are pics of my command lines for comparison. Clean, split, merge