sam sokolik wrote: > I have had very good luck with gcode.ulp. The gcode will require some > editing (or changing of the script) if you don't have a tool length sensor. > It has a roughing mill and fine mill. You can also tell it how many > passes for each tool. > I set the first tool length manually - then it touches the tool length > sensor - then after each subsequence tool change - the tool length is > automatically set with the tool length sensor. > > http://git.unpy.net/view/eagle.git > > a few trys... :) > http://www.electronicsam.com/images/KandT/servostart/amp.JPG > http://www.electronicsam.com/images/KandT/servostart/top.JPG > http://www.electronicsam.com/images/KandT/servostart/schem/newcurrentlimit/bottom.JPG > http://www.electronicsam.com/images/KandT/servostart/schem/newcurrentlimit/top.JPG > > sam > > > > Andy Pugh wrote: > >> 2009/12/2 Jon Elson <[email protected]>: >> >> >> >>>> http://www.pcbgcode.org/ >>>> >>>> >>>> >>> This requires you to use Eagle as the PCB package, I'm guessing that it >>> doesn't accept input from any other packages. >>> >>> >> It also "cuts round the traces for the circuit" which seems to not >> meet the requirements of the original query. >> >> Pretty darned nice boards.
Gary K8IZ ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
