tiles

I grouted the tiles in my bathroom. The next step will be to put the toilet and sink back in.

adaptive roughing

I got adaptive roughing to work in HeeksCNC for Windows using the Python module of libactp ( http://code.google.com/p/libactp/ ). I need to make a Python function that does the toolpath extracting loops instead of having the loop in each machining program, then I need a tree icon.

Profile operation

I now have profile operation working.
Draw some sketches and then press the Profile button on the toolbar in the "Program" window.
Edit the properties of the operation in the "Properties" window. Then press the "Python" button to make the text program ( I will skip this step eventually ), then press the "Post-Process" button to make the NC code and see the toolpath. The operation has been added in the "Objects" window in the tree under "Operations" which is under "Program".

Zig Zag ( thanks to pycam )

( Click to see full size picture )
I have now got a Zig Zag surface machining operation working in HeeksCNC.
Now I need to make simple profile operation work again.
Then, I will make an a rough machining operation using libactp.

pycam DropCutter

I made a sphere, saved it as an stl file.
I ran this DropCutter test in pycam, see picture ( click on it for full size )
I opened the NC file in HeeksCNC output window; which backplots it.
At the line of code shown ( for example )
X6.8000
X-7.0000 Y-4.0000
X-6.8000
It cuts back through the sphere!
What am I doing wrong?

libactp

Martin Bogomolni has made a Google Code project for the freesteel library. http://code.google.com/p/libactp/
I have been added as an owner. I plan to help Martin strip away the graphical user interface code and make some easy to use interface functions. I hard coded the view in the existing demo ( because interactive viewing is broken ), so that I could see the toolpath from an angle.

simple backplot

I have written a simple backplot.py which goes through the NC code and makes the XML file needed to display the toolpath. This will be done properly at some point ( with object oriented, machine specific classes ), so now, when the user presses "post process", he can see the NC code and the toolpath, which are interactively linked.