Thermwood / eCabinet Systems

the other two people using the machine get overwhelmed in that view so that's why I prefer it unless i'm loading in straight cnc code files.

would it be possible in a future control nesting update for the controller to display the what the max pen value is when cutting eg (next op: pocket (max penetration 6.5mm)) the controller obviously knows what the value is already it would just be nice to see it on screen or even have it in the bott...

thanks

please see attached video demonstrating the issue I nested the door and drawers for 3 cabinets, cut the three drawer fronts on the first nested sheet and then clicked on a part in the second and it gave the error message in the picture error code here error message.PNG video here : https://www.scree...

I just tried that no issues. are you sure its not a settings grouping issue? try with ignore settings grouping checked off

it might not be the board that's an issue its that the toolman file is corrupt and thinks the daylight value is different then reality

this might help you.
http://www.thermwood.com/forums/viewtop ... man#p47256

thanks

cant get this file to turn into a .tol keep getting this error message
im attaching the original dxf and my tool

Having to change the name of a cabinet after its placed in the batch editor instead of when I'm putting all the sizes in for it. lots of extra clicking

thanks for doing this its a big quality of life improvement for us.

could you add the new program time estimator as a custom action as well. I see us using that frequently

I took 52 seconds to finished "calculating" but when I used version 6.06 it happened in a blink of an eye. so something is off

if you have a part with a profiled edge and have a custom tool checked off in your mdf door tool options and then nest a job with a profiled edge and move a part and try and recalculate the off fall it stalls then hard crashes with out the crash reporter popping up. attached a control nesting export...

this is cool i've never seen it either

same here I rolled back to version 6.06 which is stable