CamBam plus V1.0 (new development release)

[kvom]

I've been on R14 exclusively since it's release and haven't had any problems.

[Dragonfly]

And while we are discussing some future changes I'd like just to remind about CamBam behavior doing profiles when the distance between objects is <= 2xTD. With more than one object selected for the MOP CamBam does the profiles level first switching sequentially between objects for each depth level.
And 'Depth first'/'Level first' options are ignored, no way to change the behavior to do each profile down to the defined depth and then move to the next.
I seem to understand the logic behind that but in practice it is not always the best approach.

[10bulls]

And while we are discussing some future changes I'd like just to remind about CamBam behavior doing profiles when the distance between objects is <= 2xTD...

Hi Dragonfly,

Sorry, can you point me at a post or example file.  I am not 100% sure I follow... 

If objects are <2xTD apart, the toolpaths will overlap an be 'unioned' together, to prevent the toolpaths from overcutting each part.

If you set the Collision Detection property of a profile to False, the toolpaths will be kept seperate (but this will result in overcutting).
I tested this with Cut Ordering = Level First in a simple example, and it seemed to order the cuts as expected.

[pixelmaker]

This is a bug I reported in 2012.
In 2014 Dragonfly reportet it again and the bug finds the way on the bugreport #15
http://www.cambam.co.uk/forum/index.php?topic=2628.0

In the attached file you can see the bug in the side view if you switch through the toolpath.
There is no overcut, it doesn't matter if Collision Detection is true or false.
If a Optimisiation Mode is on the cut changes every second layer and break the tool.
But never you get a depth first.

ralf

[dh42]

Hello

and also here
http://www.cambam.co.uk/forum/index.php?topic=4372.0

but in addition a new bug appears with the 1.0 with the radius_rod file.

If I change the max crossover distance to 0.4, I get toolpath in air !

++
David

[Dragonfly]

Hi Andy,
here is an example and a visual representation. Tool diameter is 4 mm and objects are 8 mm apart from each other. Tool paths touch at a single point and no damage to the part is going to happen. But the way CB makes it looks sporadic and my usage of spiral lead-in is totally ruined. The profile is set with a width larger than the TD. First pass with full engagement at each level should go down in spiral and the second would mill a small layer with better finish. If, of course, each profile is done one by one to the defined depth.
Milling the parts in reality I applied two profiles selecting shapes in pairs diagonally. To avoid the unwanted behavior.

[10bulls]

Thanks everyone, I will look into those.

but in addition a new bug appears with the 1.0 with the radius_rod file.

This looks like a new problem introduced in alpha16 while attempting to fix the lead-in within holding tabs problems.

OK, I know what I will be working on next week. 

[dh42]

Hello

OK, I know what I will be working on next week.

Lol, and it's solved for tangent leadout but the same problem remain with the spiral leadout. (bug #37)

bugs #26 and bug #39 also cause problem with leadin and tabs ...

++
David

[Sn3akyP3t3]

Hope to see this version come to light.  Last stable release being 9/2015 is a long time ago.