Two holes selected, only one drilled

ltomuta
Advisor

Two holes selected, only one drilled

ltomuta
Advisor
Advisor

In this test project I have two slots that I want to mill using 2D Adaptive with predrilled holes.
So I select two faces where the hole should be drilled and all looks fine at first until suddenly the operation drops one of the faces and only one hole is drilled. The result is a stock collision when the mill tries to plunge in the missing hole. #notfunny

 

Test project: https://a360.co/2T0DJV0
Update: Just in case when you open it the 4.7mm drill operation has only one face selected it was saved with two, like so: 

ltomuta_0-1589295518078.png

 

0 Likes
Reply
264 Views
4 Replies
Replies (4)

Anonymous
Not applicable

I selected both holes, drilled both holes, saved file and closed it then opened it again and nothing was missing,....... your computer is messing with you.🤣

0 Likes

seth.madore
Community Manager
Community Manager

No...I'm seeing the same thing

Edit Toolpath

Select 2 circle faces

Click ok.

Toolpath looks good

Edit toolpath again, face is dropped

 

-EDIT-

This is a known bug, logged as CAM-21997. There is a little workaround; switch away from the Geometry tab after selecting faces (in toolpath dialog) and the face won't be dropped.


Seth Madore
Customer Advocacy Manager - Manufacturing
0 Likes

Anonymous
Not applicable

In my chain of events I did not edit tool path again because it worked first time,.......... nothing triggered need to edit  anything but if I repeat your steps I guess I'll discover same problem.

0 Likes

ltomuta
Advisor
Advisor

Thanks @seth.madore, the workaround will help for now.

Speaking of broken drilling, I also have a problem with a spot drilling operation where top height is model top and bottom height is set to model top with a -x.x mm offset.

I get a warning saying that bottom height should be lower than top height. Which does not make sense, since it is. I regenerate the operation and now it all looks good. For a while at least. If somehow this warning shows-up again unnoticed just before the post-processing phase the generated code is for a 0 depth drilling operation.

I tried to reproduce it now but without success. I though I'd mention it just in case it you can confirm it as a known issue as well, maybe with a know workaround.

0 Likes