Optimizer for PCB-Gcode

[Jay C]

I have posted a similar thread on this subject on www.millpcbs.com. I have taken some publicly available code posted on the PCB-Gcode Yahoo forum for optimizing the output from the Eagle CAD ulp PCB-Gcode and improved it. It is a DOS application and now I'm making plans to update it with a Windows GUI.

Long story short, I'd appreciate feedback on the UI. I'm only initially coding for PCB-gcode output, but if I see opportunities to modify it to be more generic I'll give them consideration. For now, if you have a current program that you like the UI on that would match the functionality of what you would like in a GUI for "Optimizer for PCB-Gcode" please post them here or on the www.millpcbs.com thread.

Jay

[Jay C]

I have updated the code to be more universal in how it treats the paths in the input files. It now looks for the first G00 X... Y... line to start the path, and the next G00 X... Y... line to end the path.

Using the code posted by Dan above here are the results:
Input: c:\temp\suice.nc
Output: c:\temp\suice_OPT.nc

Old Length : 60869.8 New Length :5376.26 saved 91.1676%
Optimizations took: 1.36 seconds.
Done! Please review the generated gcode before proceeding to use the output.

Yep that's 60 thousand units of travel reduced to 5 thousand!

Jay

[Jay C]

Before and after of the file I spoke about above:

http://picasaweb.google.com/jay.couture/CNC02

[Jay C]

800+ views and no feedback Anyone using this?

[Tester]

Hi,

I guess I'll be the first one to respond.
I'm observing the progress of your program almost from the beginning. It started at the pcb-gcode mailing list (which is btw not working at the moment), then at millpcbs.com forum and now on cnczone.
Personally I tried to optimize a few gcode files which I generated with pcb-gcode and all of them look just fine. Unfortunately I haven't had the chance to try them out in practice. Hhopefully I'll be milling a few PCBs next weekend - on my cheap DIY CNC .
I also have to say that I'm really glad that someone finally made a public and a working version of an optimizer because that "random" path selector from pcb-gcode generator really annoyed me, especially as my CNC doesn't have fast feedrates (25 cm/min or 9.8 inch/min) so any unnecessary movements add quite a lot to the final work time.

So, keep up the good work and keep us uposted with the progress of the GUI.

BTW, which IDE do you use with QT - Visual Studio, Eclipse or perhaps something else? I'm also starting to experiment with it but I have some difficulties with the Eclipse plugin for QT because g++ doesn't seem to find main.cpp

[Jay C]

Originally Posted by Tester Hi, I guess I'll be the first one to respond. ... So, keep up the good work and keep us posted with the progress of the GUI. BTW, which IDE do you use with QT - Visual Studio, Eclipse or perhaps something else? I'm also starting to experiment with it but I have some difficulties with the Eclipse plugin for QT because g++ doesn't seem to find main.cpp

I'm using the MingW C++ compiler. When I installed Qt, it sets up a link to a command line that sets all of the environment variables. To compile, you first do a qmake -project, then qmake which generates the make file. Finally, run make to compile and link which places the output into a new directory called release. I downloaded and have been reading the Qt book. I have my GUI planned out, just need some time to code it now

Jay

[Tester]

Today I tried to mill a smal PCB and found an error in optimized gcode.
When first path is milled CNC continues to the next path without raising the spindle thus braking one connection on its way. All other paths are milled without a problem.
I attached the original and optimized gcode files so you can analyze them. *The problematic line in optimized file is line number 34 (spindle should be raised to Z 0.5000 but instead it stays at Z -0.2000).

I hope I provided enough information so you can locate the cause of the problem.

EDIT: I'm not sure if line 34 is "the problematic one", but the path of the traveling spindle at the wrong height can be clearly seen in Mach3.

[Jay C]

The issue is that the Z up movement occurs after the (File Footer) tag and thus is not included in this path. HMMM, the best solution I can think of (which would also remove the need for the (File Footer) tag is to make the last path always the footer path (my terminology for the last path in the source file).

I will work on a solution and post an update. In the mean time, you can just add G00 Z0.5000 before the (File Footer) tag as a work around.

Jay

[Tester]

Yes, this seems to be the problem. Thanks for the temporary solution .

[Jay C]

Updated 7/21/2008

Modified the code to remove the (File Footer) tag requirement. This should make it pretty universal now. Still working on GUI development, but got sidetracked playing with my mill this weekend

Here

Jay

[dakiller322]

Hmm, your source code looks familiar nice to know it's going to good use.

I see you've put a bit more care into how it reads in the files, you've done a nice job with it. I'm surprised someone didn't make an optimiser for it sooner, it's such a crude algorithm but it works so well here.

Please feel free to make whatever you want with it, just as long as I get some credit

[Jay C]

Yes the code you posted is the kernel of the optimizer. At the top of the source file is:

/*
*   PCB-Gcode Optimiser
*   Original code: Daniel
*   Updated Code: Jay C
*
*   Release: Beta ... use at your own risk

I will gladly put anything more you wish. Just let me know and it will be included in all future releases. I neglected to give either of us credit in the Windows source I have fixed this. Oh, and I gave you full credits on PCB-Gcode, unfortunately that is now lost Not sure the Google Group is much of an improvement.

Jay