All you have to do is select Files->Run->outlines_gcode.ulp and it pops up a window asking for Device (Select gcode), Width (of cut), Layer (for a single sided board use 16), and Output file. At first I just pulled a width out of the air (well from Ian's post) so I typed in "0.1" and after some flashes on the screen got a lovely file containing wonderous gcode!!! The flashes were actually the script figuring out how to do things, but my machine just chews the work up and spits it out. This is near magic to me...I love it! At the moment however, the code doesn't mirror the image for bottom traces, so it's not 100% usable out of the box. I'll just have to change the rotation of my X drive to suit, or bite the bullet and make the code changes myself as time permits (right now building something seems like more fun). |
![]() |
Ok, so now I have Gcode, but I'm away from home and my EMC machine. How do I have a look at what the code is actually doing? Using a combination of UltraEdit32 and Excel I converted the gcode to a spreadsheet so I could plot the results. The final data plot looked like this. |
![]() |
| So I tried the same thing again this time with the width set to 0.025". | ![]() |
| Better, but many traces are still attached. So I set out to figure out what the actual cutting diameter might be. Looking at the G-code resulting from the outline_gcode.ulp, they mentioned "Think&Tinker Mechanical Etching Bit with 60-degree tip angle" and a cutting depth of 0.007". Ok so we're dealing with a 60 degree isocelese triangle. That means (if my trigonometry holds), we're dealing with approximately 0.008" cutting diameter. | ![]() |
So I tried outline_gcode.ulp again with a width of 0.008, and the resulting tool path looked much more promising. I don't pretend that this is the proper value, as I have nothing on which to run the code, but with my Excel model at least all the traces were isolated and clean. |
![]() |
