Can you send an export of your Control Nesting and the .twd you nested to create this code? I loaded your assembly into eCabinets and wrote to CNC without doing any material thickness changes. Loading into Control Nesting with a random export I had, nesting along X, filtering out only the Mel 16 Pbd HMR material, and writing to CNC cuts all the holes. I want to try to reproduce using your settings.
Does it happen every time with these cabinets, or is it a random occurrence on different cabinets and assemblies?
At the risk of sounding like a smarta$$, check your boring bit tips. If the pattern is there and the code is right, then you should see your machine try to make the moves, too. Witness the program as it cuts. I've had a bad bit twist the tip right off. Sometimes, the simplest answer is one overlooked.
_____________
Win 10 Pro 64 bit on MSI Z390M Pro4
Intel core i7 9700KF 3.6GHz (OC 4.2Ghz)
32 gig RAM, NVIDIA GeForce GTX 1050 Ti
NVME SSM2HD 1TB NTFS
Stuart Douglas wrote:At the risk of sounding like a smarta$$, check your boring bit tips. If the pattern is there and the code is right, then you should see your machine try to make the moves, too. Witness the program as it cuts. I've had a bad bit twist the tip right off. Sometimes, the simplest answer is one overlooked.
Unfortunately the file he has above does not have the code for the drills. I can generate a CNC file with the holes without issue, but I may not be doing the same thing he is.
Do you have the original .twd from when the holes were missing? If I have that we should be able to tell if eCabinets didn't send the information for the holes, or if Control Nesting didn't find the information.
Do you remember your exact steps when you created the original .twd? I'm sure I'm reaching but if you can remember it may help us narrow down whats happening. Are you loading the assembly into Cabinet Editor then writing to CNC, is it loaded in batch and wrote to CNC, is it in a room layout and wrote to CNC, do you say yes to material thickness change then OK without making changes, etc? I know you said it has been more random, but if we can narrow down repeatability we should be able to correct the issue.