DeskProto releases free CAM software for Linux.

Hi Lex,
.

We were late in realizing that indeed most parts to be machined are much simpler, and can be machined from a 2D drawing, at various Z-levels (2.5D machining). The current DeskProto V7 is the first version to really support this type of machining, so this still is fresh technology for us.

Being late does not mean, that you can't become better

CamBam has passed a long release cycle and this release is the first, that creates polylines on the fly. Older release created line-segments, which you had to convert into polylines. Then all segments of a curve had to be selected and combined into one polyline.
That was quite a lot of work - but compared with i.e. estlcam - you could workout any complicated figure.
Automatic solutions are a holy wish, but you can't foresee every complicated situation.
So in my opinion, cambams concept is not bad.

What I think is definitely better, is that cambam does not bind possible operations on the imported source. Instead operations are identified by their type like 3D-surface or 2D-paths. That reduces work for programmers and amount of possible user errors.

To workout stl like vector data from dxf, cambam supports smoothing of curves, which then converts mesh data into vector data. You could try to do the same. Differentiate between 3D-surface and 2D paths - the latter will save a lot of processing time.
Another possibility would be "boring" or pockets for 5-axis machines.
I read, that currently only holes with same diameter than current tool are recognized as holes.
There are lot of ways to create round holes and many holes need a traveling tool.
So recognizing holes with diameter, length and orientation will be a valuable feature.
.

DeskProto should be about "CNC machining for non-machinists". And the more options, the less easy to use....

Hm, I don't think, thats a good goal.
Estlcam already works that way - and it is pretty easy to break estlcam without way out.

There's a saying: if you make your app that easy, that fools can use it, then only fools will use it.

Many years ago, when I tried blender the first time - I thought: no, that app is not for me. Too complicated. Later some friends told me about the possibilities of blender and I thought I have to try again.
This time I decided: if I can not use blender, the way I like, I have to learn how to use blender and change my workflow. I started with tutorials, lessons, and lots of doing.
At the same time I started to learn freecad the same way.
After some weeks I got the conclusion, that freecad is crap and blender is a perfect substitute for my cad.
From that day, I used blender nearly every day and of cause became better and better.
Now - many years later, I stil believe, that my conclusion from old days is valid.

Therefore I believe, the best way to get used by serious users is by persuade with functionality. If functionality is reliable, users will learn how to use DP.

cheers Reinhard

Being late does not mean, that you can't become better

We are doing our best

What I think is definitely better, is that cambam does not bind possible operations on the imported source.

DeskProto does not impose that restriction either: in a project you can create any operation type that you need, and import any CAD data type that you need (in the normal user interface, not in the wizards). What differs is that Cambam adds some CAD functionality: it can generate vector curves from STL data.

Many years ago, when I tried blender the first time - I thought: no, that app is not for me. Too complicated.

You perfectly illustrate my point
The argument that Estlcam already offers this does not convince me, as numerous CAM programs are on the market that already offer complicated CAM.
Adding functionality is fine, and we do so all the time, however we try to keep the user interface simple. Which is not always easy...

Regards, Lex.

The argument that Estlcam already offers this does not convince me

I guess, you got me wrong.

I didn't cite Estlcam in the sense, that there's already an app, so you don't need to keep on working.
No. I cited Estlcam, as it claims to be an easy to use cam for non-machinists - and it fails. It works with simple parts and yes, it supports trochoidal milling, but on complicated parts it simply fails and there is no way out.
.
Cambam is feature rich but does nothing automatically. So its said to be complicated. But it offers a bunch of tools that enable you to work out the most complicated piece you can imagine.
.

... as numerous CAM programs are on the market that already offer complicated CAM.

That's true for sure

At work we have very expensive CAM (various), but as most if not all parts are technical pieces, there are 2 colleagues who are faster with manual GCode coding, than any other with using CAM. They won't never learn or use CAM - and its ok for the company.

I think that's the point. CAM, CAD or any other abbreviation with starts with C should help the user use his time efficiently and not waste his time. Many programmers have lost sight of that goal.
.

however we try to keep the user interface simple. Which is not always easy...

There's a saying: the genius of an invention does not present itself by function complexity but appears in its ease of use.

So keep on becoming better.
... and if you need a tester, I'm willing to spent my time to help you improve DP.

Ah, now I understand about Estlcam.

Thanks for your offer to cooperate in testing new software features !

BTW the post on Facebook is reaching a lot of people ( www.facebook.com/DeskProto/posts/3295983023771724 )
One comment might be interesting for you: "Wow, kommt mir bekannt vor.".

Lex.

Reinhard wrote:

Is that a good STL? It looks strange. I wonder if it has internal surfaces that are confusing the CAM?

I wonder if it has internal surfaces that are confusing the CAM?

Hm, should be ok.
Its a dualside part, which means, it has to be milled from upside and downside. Blender states some minor errors with 3D-printer check, but prusa slicer processes the file without errors.

If you're interested, I could send you blender file and/or stl.

Cambam gets not confused from the stl.