It does seem to be updating the holders correctly when making changes.

I only use holders when I have to. It's a mess.

I can say this. Change a tools Name or T/D/H # and it actually updates all of them.... Before you had to go into each Op and click on the tool so it would update the name. THANK YOU CNC! Now if the lathe tools would not change the feedrate I would be happy!

I seen it at the Tech Expo in Seattle. Looks real nice. Uses a new feature called "Extensions". From what I can tell both Tool Library/Manager and Sync Manager (For multiple turrets) will be an Extension and use the new UBVS (MachSim) for simulation. The Stock/pick/pull/cutoff looks a lot like the current pick/pull/cut function. This is all public info.

All fixed. I didn't see the forced output for live tooling. This is a modified mplmaster post. Works like a charm now!

It's not there. I had a section that was forcing the output to be M45/M245. Now I have this if not (livetool_flg), [ if spindle_no$ = 0, pbld, n$, sm23, , e$ if spindle_no$ = 1, pbld, n$, sm223, , e$ livetool_flg = 1 ] Thanks guys! Josh-

I'm assuming it knows that it's pltype3 based on the "Upper Right" turret specified in my Sub Spindle Milling Op. I'm also assuming it's something that needs changed in the corresponding post block. pltype3 #Top turret/Right spindle if cuttype = one, [ #Lathe max_speed = max_speedl3 min_speed = min_speedl3 sw_string = scase_tr_c1 ] else, [ #Mill max_speed = max_speedm3 min_speed = min_speedm3 sw_string = scase_tr_c2 #case two is the default if cuttype = -2,sw_string = scase_tr_c_2 if cuttype = three, sw_string = scase_tr_c3 if cuttype = -3, sw_string = scase_tr_c3r if cuttype = four & abs(c1_millcc) = one, sw_string = scase_tr_c4c if cuttype = four & c1_millcc = zero, sw_string = scase_tr_c4 if cuttype = five, sw_string = scase_tr_c5 ]

Thanks for that info. I'm using the inhouse post and it has that logic. Problem is when milling the only way to tell the post your on the side is "Left View" and "Upper Right Turret". I could have it check for which side of the turret? Josh-

Can anybody help? I need to get this last bit worked out. Thanks, Josh-

I honestly never use the c-axis toolpaths. Just use a mill toolpath.

Colin, This works great, got my main spindle (Upper Left) outputting M14 and my Sub Spindle (Upper Right) outputting M13 like it should. Now I need it to output a M245 for the Sub instead of a M45. How can I do this? How does it decide between *sm24 and *sm224/ *sm23 *sm223? Thanks, Josh-

MultiCam is a pretty popular machine.

Ron, I'm assuming you are the lone "yes". EDIT: I like the level set function but that only ties levels together. Viewsheets does this already. I wish my active toolpath group could be assigned to a viewsheet.

I probably could. I've had countless emails back and forth with CNC Software about this and they say its "as designed". I figured putting up a poll might open their eyes to how people expect it to work. Josh-

The problem now is by the time you get to Op4 all the other viewsheets have the wrong levels turned on. You have to go back and turn levels off and re-save the bookmark.

Lets say you have 4 Ops to make a part. Each with 3 levels and a separate WCS. This is how I lay out my work flow: ToolPath Group Name (Op1 - XXXX.NC) WCS - Top G54 Levels - 1 Op1 Geo, 2 Op1 Solid, 3 OP1 Notes. ToolPath Group Name (Op2 - XXXX.NC) Op2 WCS - Bottom G55 Levels - 4 Op2 Geo, 5 Op2 Solid, 6 Op2 Notes. ToolPath Group Name (Op3 - XXXX.NC) Op3 WCS - Bottom G56 Levels - 7 Op3 Geo, 8 Op3 Solid, 9 Op3 Notes. ToolPath Group Name (Op4 - XXXX.NC) Op4 WCS - Bottom G57 Levels - 10 Op4 Geo, 11 Op4 Solid, 12 Op4 Notes. Now during the process I create the following viewsheets that are bookmarked with the correct WCS and Levels turned on. OP1 OP2 OP3 OP4 I can now clearly see what toolpath group is what Op and if I click on the corresponding viewsheet what wcs, geometry, workholding and notes. This really helps the next guy who opens your file!

Updated the Poll.

Not using them would exclude you from answering the question.... You SHOULD be using them.

This relates to saving bookmarks in Viewsheets. There's two camps when it comes to the way Viewsheets should work. The current method: 1. Levels turn on- Create a Viewsheet and save the bookmark. Now create or move Geometry to a level that was previously empty. Go back to the Viewsheet and this level is now turned on. This forces the user to go back to every Viewsheet they have defined and resave them with the new level off. I'm told this is "as-designed". Viewsheets are supposed to keep track of which levels are OFF, not which ones are on. So if you add new levels after a Viewsheet is created they will all be visible in the already existing viewsheets. Just the way it's supposed to work Alternate method: 2. Levels turn off- Create a Viewsheet and save the bookmark. Now create or move Geometry to a level that was previously empty. Go back to the Viewsheet and this level is turned off. Only levels that were turned on when the bookmark was saved will be on when you come back. This is how I feel it should work. I build viewsheets as I make operations. Operation is done, save viewsheet, open a new viewsheet, rename to the next op and move forward. Currently I have to go back through every viewsheet and clean up the mess. Even worse if someone wants to come into your file, make a new level for an op and then have to go back through again and clean up the viewsheets and re-bookmark. To me this makes Viewsheets an amazing feature that is almost unusable. Josh-

Never seen this, should rapid.

ViseVersa will monitor all your files and synchronize them automatically. Works flawlessly. http://www.tgrmn.com

Crappy vacuum through Masisa (MDF). I always screw the Masisa right to the deck so it can't move around. I also generally clamp the edges and place strategic screws through the sheet along with tabs. As long as you do all the roughing passes while leaving a skin the sheet stays in place. I always go with a max DOC of 0.200". There's a lot of technique involved in how/when you cut section of the sheet. Yes the Onsrud sight is atrocious. Josh-

My experience is on MultiCam routers. I used do onsite training and support for this very thing. Josh-

You want the 63-600 series. I ran these at 18-25K, 0.200" DOC and 320-400IPM with only air blast. Router Bits last days/weeks depending on the cut time. I've cut literally thousands of sheets this way ranging from 0.020" to 1" thick. The trick is cutting within say 0.010" of breaking through and tabbing the last pass (cutting through) with interconnecting tabs. You can use "remachine" and have MasterCam drop in and just remove the tabs.... Josh-

Sorry I edited my last post a few times.... Josh-