We use dxf files from our design tools to generate our parts and a parts list.
Our problem is that when we define a backpocket, thermwood isn't picking it up or cutting it. I have checked the files against a regular pocket layer and all appears the same except for changing pocket z11p0 to backpocket z8p0 (19mm material) and the geometry in the LWPOLYLINE is set to cut from the bottom.
I'd start by specifying a tool / tool diameter. Since Thermwood introduced the ability to call a tool by name instead of diameter, that's how we've done it.
For instance:
the old way: pocket d9p5 z8p0
the new way: pocket z8p0 [3185]
Either way, a tool is specified. Your code isn't specifying one, so I'd try that first.
Jeremy Schiffer wrote:I'd start by specifying a tool / tool diameter. Since Thermwood introduced the ability to call a tool by name instead of diameter, that's how we've done it.
For instance:
the old way: pocket d9p5 z8p0
the new way: pocket z8p0 [3185]
Either way, a tool is specified. Your code isn't specifying one, so I'd try that first.
I've never specified anything other than pocket zXXpX, drill zXXpX, etc.
What is the nomenclature you're referring to? I don't see anything about it in the dxf reference.
Jacob Janzen wrote:We use dxf files from our design tools to generate our parts and a parts list.
Our problem is that when we define a backpocket, thermwood isn't picking it up or cutting it. I have checked the files against a regular pocket layer and all appears the same except for changing pocket z11p0 to backpocket z8p0 (19mm material) and the geometry in the LWPOLYLINE is set to cut from the bottom.
The files look good in IntelliCAD so I'm really at a loss here.
As far as I can tell it is working as I would expect it to.
Part of the disconnect may be an understanding of how Control Nesting handles operations. With DXFs, singled sided material isn't an option. If the material isn't defined as single sided for any file type Control Nesting looks at which side of the material has the most amount of operations and that becomes the top of the material. So in your flip DXF with the pocket, the pocket and drills that are labeled as back operations outnumber the other operations. That makes the other operations backside operations, while the ones you defined as "back" are now front operations. The code that is output looks like depths are adjusting correctly for the reorientation of operations.
I believe I'm on the same path, but if I'm way out in left field let me know and I'll look towards other issues.
It wasn't showing the pocket on the backside operation on the Nest Overview... Was it in fact going to cut the backpocket? It didn't look like it was going to on the display.
It wasn't showing the pocket on the backside operation on the Nest Overview... Was it in fact going to cut the backpocket? It didn't look like it was going to on the display.
I'll take another look at it.
Thanks,
Jacob
Jacob,
Ignore my previous reply, I was in left field (or somewhere left of that). I see what you are saying about it missing. I suspect it is an issue in how the software is creating the DXF. If I load your DXF into Mastercam, and just resave it, it shows the pocket in the nest and creates the code to cut. Mastercam is likely repairing the DXF in some fashion. You can look to see if there is an AutoCAD output version when saving the DXFs. Usually saving in the AutoCAD version 2004-2006 has worked well for other customers in different softwares.
Thanks I'm going to try tomorrow I was doing some geometry changes because it didn't work before but maybe we've run an update where my "fix" has now broken things. You just reminded me of flipping geometries around that I'd forgotten about so I'll try reverting that and seeing if it works.