Programmer’s Log Programmers Writing Stuff – Garry Bodsworth

15Feb/093

Open-Source CAD/CAM

I spent over seven years working in the CAD/CAM industry. It's a very archaic industry with virtually no open-source building blocks available, and those that are tend be be extremely old or not even useful.

There are a few green shoots of open-source out there. First up there is wildcat-cad which is an attempt to create an open-source 3D solid modelling kernel and associated tools.

There is also heekscad which is a modelling program using the OpenCascade solid modelling kernel (GPL licensed I believe). There is also a CAM add-on for heekscad called heekscnc with a lot of associated libraries providing some good functionality.

An additional program is voxelcut which allows for a solid machining simulation to see what damage you'll do to your hardened steel.

One of the libraries is libarea which is for area-clearance algorithms in CAM. This is normally one of the most closely guarded secrets in commercial CAD/CAM so it is interesting to see an open implementation.

libactp is an adaptive clearance toolpath which originated from Freesteel. They've got it integrated into heekscnc so you can try it out for yourself.

You can keep track of a lot of this stuff through Dan Heek's blog.

Another unrelated program is monocam which uses C-sharp as a development language and has soem interesting algorithms like the drop cutter which provides the basis for most 3D machining algorithms.

14Oct/081

New Macbooks and Manufacturing

The most exciting thing for me about the new MacBooks announced today is seeing the manufacturing process. You can watch the video here.

You see I used to write software that did exactly that kind of machining up until about 10 months ago. CAM programming is not for the faint-hearted. Seeing proper videos online of what CAM software actually does is something of a rarity since most CAD/CAM companies obfuscate their online presence.

In the video you can see lots of liquid coolant being pumped onto the solid block whilst the cutter does the hard work. I'm just wondering what software is being used to create the toolpaths, especially since there are only a handful of packages capable of doing it, as well as a lot of them use the same algorithms internally. In fact whoever's software is doing it should be shouting it from the rooftops, its the closest thing the CAM industry has had to publicity

When you see the "back" of the laptop shell you can see the toolpath's route around the job. It seems to have a large stepover (the gap between paths). I'd be interested to know how long each one takes to run the toolpath because I know someone who is really good at writing this type of software. I'd also be interested to know whether the software I used to work on would have done the job.