[hinksj]

I've written a program to be used instead of pcb-gcode.

I've tested it on Mach3 (Inactive mode) but I have not run the resulting gcode on a real machine yet.

I just received my WidgitMaster (Great Machine!!) but I'm about 4 weeks from getting everything completed so I can test it fully myself.

I'm looking for someone that is interest in the added capabilities (over pcb-gcode) to test it and provide feed back.

It run in two stages. Stage one as a ULP on Eagle to acquire raw data.

Stage two is a Windows program that processes the data and produces the gcode.

There are two big differences in this program and pcb-gcode.

#1 - you can use up to three different mill bits to do the routing. Use a Big bit to do most of the work and the smaller ones for cleaning up the tight places.

I download a test board from the Internet and operated on it with two bits. Bit one was .015 with an isolation width of .03 and the second pass using a .005 bit giving a isolation layer of .02. Most of the work with the .005 bit will be air since the .015 did most of the work. The bottom side results are depicted below. Up to three different tools can be specified.

#2 - Optimize the routing path to minimize the number of tool moves. The first example below is the tool path obtained using pcb-gcode. The other one is optimized.

I got the cart in front of the horse on this one .... getting my software developed prior to having a machine to test it on.

If you are interested in testing and providing me feed back - please let me know.

The actual board is 4.0 x 2.0 inches. The pics below are shots from the program and are enlarged for viewing.

[acondit]

The disadvantage of your program is that it won't run on a Mac or Linux, while pcb_gcode will run on both of them plus windows. There is also an optimizer for pcb_gcode.

Alan

[cwiliam]

I would like to test it hinksj

[hinksj]

I decided to start doing my own PCB work without having to make the boards commercially.

I did a lot of reviewing on this site and others about pcb-gcode.

I found people asking about using multiple size bits to preserve the smaller endmill bits and let heaver bits do all the work.

I also looked at the optimization additions to pcb-gcode and thought I could do better.

Since I create software for a living, I decide to create a tool that fit my wants and needs.

I am making it available to any of you that wish to use it.

I feel it provide more flexibility and control over the pcb-gcode options available (there is only so much Eagle lets you do in a ULP program).

I have received a lot from this site and others. --- This is my attempt to give something back.

I wrote a brief tutorial --- you can view it at:

http://joehinkle.com/Eagle2Gcode/Eagle2GCode.htm

If you would like the package ---- This link will download it for you:

http://joehinkle.com/Eagle2Gcode/Eagle2GcodePackage.exe

[vladdy]

does your software have some sort of 'intelligence, where ,say if you started with the largest bit size, that it would know where material was already removed, and save time by not having to 'remill' already removed excess material..

[hinksj]

It starts with what YOU specify as tool 1.

I would make this the largest bit.

Once tool 1 has completed its assign task, Tool 2 is loaded.

For me, this is a .005 endmill.

No, I do not look to see what has already been cut.

It does not take that much time to run the process using tool 2.

These tools have a limited life measured in feet of milling.

My .005 endmill cost $35.

I want to extend the life on it so ... yes it may pass over already cut areas of the PCB, but there are areas that were too small for the larger tool 1 to mill, so tool 2 will now mill them.

This strategy will greatly extend the number of PCBs that can be milled given the tools used.

[Greolt]

Can't get past first base.