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

**URL:** <https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688>\
**Category:** Software\
**Tags:** gcode\
**Created:** [December 29, 2023, 3:46am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688 "2023-12-29T03:46:36Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [January 22, 2024, 2:05am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/42 "2024-01-22T02:05:44Z")

</div>

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’

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [January 22, 2024, 6:13pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/43 "2024-01-22T18:13:57Z")

</div>

> [@mooselake](#):
>
> @bar I’m unable to upload pictures, zipped files, or dot nc files, every attempt gets “Sorry, an error has occurred.” . I was able to post pics in the past, is it me or something else?

[Office Dishrack.nc](https://forums.maslowcnc.com/uploads/short-url/sFuWGcuq2bmvFelah9vfMouyLlp.nc) (67.2 KB)

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

---

<div class="post-metadata">

**Author:** ![mooselake](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mooselake/32/6218_2.png) [@mooselake](https://forums.maslowcnc.com/u/mooselake)\
**Post date:** [January 22, 2024, 9:55pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/44 "2024-01-22T21:55:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [January 22, 2024, 10:12pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/45 "2024-01-22T22:12:39Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [January 22, 2024, 11:47pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/46 "2024-01-22T23:47:49Z")

</div>

[Dishrack-gcc-ts.nc](https://forums.maslowcnc.com/uploads/short-url/yfPCiIkS6xzqgMmO381TEg0mZg2.nc) (78.1 KB)  
Yep - and it works for me.

---

<div class="post-metadata">

**Author:** ![mooselake](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mooselake/32/6218_2.png) [@mooselake](https://forums.maslowcnc.com/u/mooselake)\
**Post date:** [January 24, 2024, 10:14pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/47 "2024-01-24T22:14:10Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![mooselake](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mooselake/32/6218_2.png) [@mooselake](https://forums.maslowcnc.com/u/mooselake)\
**Post date:** [January 24, 2024, 10:16pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/48 "2024-01-24T22:16:14Z")

</div>

[ChipCarve-TB11.nc](https://forums.maslowcnc.com/uploads/short-url/yCiNfWNYkZ0qGvbV6YdbHAdyMG4.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 🙂

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [January 24, 2024, 10:20pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/49 "2024-01-24T22:20:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [March 7, 2024, 5:19am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/50 "2024-03-07T05:19:06Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [October 13, 2024, 1:08am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/51 "2024-10-13T01:08:03Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![MrN808](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/mrn808/32/22275_2.png) [@MrN808](https://forums.maslowcnc.com/u/MrN808)\
**Post date:** [October 13, 2024, 11:35pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/52 "2024-10-13T23:35:39Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [October 14, 2024, 1:55am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/53 "2024-10-14T01:55:35Z")

</div>

> [@MrN808](#):
>
> Just discovered this thread and…color me “intrigued.”

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

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

> [@...And the Travelling Salesman arrives at GCodeClean v1.3.0](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/4):
>
> Great Job!!! Here are a few web control pics from gcode I cleaned up, split and merged. The original gcode was created with Carbide Create v6 build 652. According to GCC my original traveling distance was 12,192 and new traveling distance is 1,165! I am cutting it now.

---

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [October 14, 2024, 6:34am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/54 "2024-10-14T06:34:03Z")

</div>

> [@MrN808](#):
>
> - Run GCodeClean on resulting NC file (I’m not clear yet on the steps—is it ‘clean,’ ‘split,’ ‘merge?’)
> - Run output of ‘merge’ on Maslow 4?

yep, and then yep

---

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [October 14, 2024, 6:39am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/55 "2024-10-14T06:39:07Z")

</div>

> [@TimS](#):
>
> Is this still the most current version?

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 …

---

<div class="post-metadata">

**Author:** ![md8n](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/md8n/32/28197_2.png) [@md8n](https://forums.maslowcnc.com/u/md8n)\
**Post date:** [October 14, 2024, 6:44am UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/56 "2024-10-14T06:44:22Z")

</div>

> [@MrN808](#):
>
> clean

This does a lot in its own right. Quite frankly almost all GCode generated is a pile of 💩 (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.

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [October 14, 2024, 3:33pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/57 "2024-10-14T15:33:45Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Andith](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@Andith](https://forums.maslowcnc.com/u/Andith)\
**Post date:** [October 14, 2024, 4:31pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/58 "2024-10-14T16:31:47Z")

</div>

> [@md8n](#):
>
> 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).

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.)

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [October 14, 2024, 6:51pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/59 "2024-10-14T18:51:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Andith](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@Andith](https://forums.maslowcnc.com/u/Andith)\
**Post date:** [October 14, 2024, 7:05pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/60 "2024-10-14T19:05:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![TimS](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/tims/32/17329_2.png) [@TimS](https://forums.maslowcnc.com/u/TimS)\
**Post date:** [October 14, 2024, 7:23pm UTC](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688/61 "2024-10-14T19:23:03Z")

</div>

![IMG_20241014_121819278](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/c/a/ca80d094c45ddb671d04fe1f906d6c8274e8bf40.jpeg)

 ![IMG_20241014_121839645](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/c/5/c58ca9421367b3495810cc2f99b0c22b67aadb9c.jpeg)

 ![IMG_20241014_121900330](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/3X/2/3/23ece2fa1591969e3310eb11b22e36b2fdc179f5.jpeg)

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

[Previous page](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688.md?page=2)

[Next page](https://forums.maslowcnc.com/t/and-the-travelling-salesman-arrives-at-gcodeclean-v1-3-0/19688.md?page=4)
