Thermwood / eCabinet Systems

I have located what was causing this problem. It will be fixed in V5.03.

I would like to avoid brushing this one under the rug. There were some changes in 5.02 that caused this issue. Would you please post your twd file with this cut out so that I can resolve it. Thanks!

Larry

The .mvdxf requirement is no longer needed. The manual needs to be updated for that.

I did find a problem for rout operations. It appears that Microvellum may be sending a tool number that is not being read by Control Nesting. I will address this, but to make sure I get you up and running PM me ...

Also make sure your Drill Bank Boundaries are set properly.

We have found the problem and will have an update out next week to address it. For now if you need to load a particular Off-Fall you can do it through the dialog reached through the OffFall button. Just find the matching number and click load. You can also type it in while in the Add Sheet dialog ...

Paul,

Are you running Control Nesting 5.0? If so please send your .twd, machine.ini, and tools.thm to cabinets@thermwood.com and I'll look into it.

The machine.ini and tool.thm files are in c:\\Rolling Nest directory on your machine.

The first file I attached was not a zip file. Just change the extension to .dll. It's the actual file.

There is a possibility you may need one more dll. Here it is. This attachment is an actual zip file so extract the file in it and put it in your c:\\Profile Modeler directory on your control.

Of ...

Since your having email trouble here's the file. It's a dll so change the zip extension to dll.

You don't need to go back on Control Nesting Versions. The latest 5-0 will be fine. There is simply a version mismatch with Profile Modeler that is causing you this problem.

Paul,

We have had this construction technique listed as a feature for a while. Hopefully we will be able to integrate it in the near future.

We will work on generating a detailed result for the no tooling available error.

The LWPolyine feature is NOT a layer name option. It simply means that Control Nesting now supports this type of DXF entity. In the past the DXF Import utility had problem with this. LWPolylines are a form of Polyline ...

We'll work on it!

I just noticed that! You make a great point as well. When lines from different 'intended' operations are connected it screws up the algorithm in place for optimizing the DXF data. It is always good practice to keep all the entity's end points connected to only the other entities that are part of ...

I just read your first post and realized you wanted to use a 6mm tool. I believe the actual tool diameter is 6.22mm so you can change the layer name to 'pocket z4p0 d6p22' and it should then choose the correct tool for you.

Hi Paul. Give this file a try. I moved your lines a bit for radius purposes and used pocket in the layer name. This should get you going as well as help you understand how the pocket functionality can be used.