Message is not complete. Yes it's fixed by closing the file. Have only got it when working with Contour so far, and only in the last 2 or so days. It actually crashed yesterday so I sent the report.

Anyone seen this before? After I select chains and click OK. Doesn't crash Mastercam, just muddles the screen and hangs until I close this error warning.

I only nest toolpaths not geometry, even if there are 20 different parts. Then I can easily re-nest according to re-order quantity. As far as not nesting all parts goes, the only times I've had issues, I haven't checked "create necessary qty" on sheets tab and/or part rotation increment is too coarse.

Haven't found the work offsets in the control yet. The post developer set up the .RMD for me with the standard block drill configured in it, which I can edit according to my requirements. No horizontal drills exist as we are nesting only. I'm really just looking to use the block drill as a tool changer so I want to know how configure Mastercam to output the code required.

Does anyone have feedback on this model portable? I'm trying to evaluate options for an upgrade from my basic build HP xw4400 desktop which is slow on TP regen and dynamic manipulating solids, 2.13ghz, Nvdia FX1500, 2GB, XP pro 32. What should I be focussing on, CPU, RAM, Harddrive speed, Graphics???

I'll investigate this. Thanks for the pointer.

What Trevor said. We often drill 2 holes in discreet places on the part then shift it aligned with those holes.

Have switched to Ramp on almost everything I do. Thanks for the ideas, it's good to know some Router guys are still on this forum.

Working in X4 Router level 1, I created an elipse, converted it to arcs, then offset the arcs in X,Y and Z to create a ramp. I added perpendicular lines between top and bottom contours of the ramp and now I'm trying to create a 2D swept toolpath on just one arc segment of the geometry, to test. I get about ten zig-zag passes out of it. I've had success using arcs on the across and along boundaries. Any suggestions?

Can anyone provide some clarity for me by way of example code or guidance as to what to expect from MC block drill operations and how to configure the MD. I've been trying to get the post processor (via developer) to output suitable origin shifts for a variety of diameter drills used in the block drill. So far all I get is a temporary origin shift at the start of blockdrilling cycles which is calculated for the corner drill #25(which is my lead drill)and a cancellation of the temp origin shift at the end of blockdrill cycle. But when drill #26 or #24 is called individually, it still uses the same temp origin shift, which puts it 32 mm out of position in X or Y. I hope you can see my problem and the probably obvious solution. Any feedback on this would be really welcome.

When I Verify my block drill cycles, with show tool and holder on, I get collisions at each plunge because the tool definition is like 2mm long in a tool holder. Not sure how to get my block drill to show here the way it is defined. In back plot it shows exactly how it's defined in the tool list section of the op tree.

I think it is as you stated. G0 must be active when calling another tool. I've got our updated post so will see how that goes. You are the only other Osai user I have found so far. Our router has an Osai 10 control. It was built locally here in NZ and the Osai agent is resident in Australia so support is patchy. The manuals provided are reasonably comprehensive though so given the time I can usually find what I need. How do you get on?

My Osai control won't accept this. ...G81Z-15.R10.F4000. X2122.5Y1072. X2122.5Y817. M88 M06T26.26... Get "M and dynamic mode incongruent" error. So I go ahead and cancel the canned cycle before calling T26. Does this mean I must post the canned cycle mode every time a new drill is called? Is that what you would do? I don't edit our post so I want feedback before I ask our post developer to do it.

Thanks Tim, never thought of contour ramp. That's pretty much the perfect solution for me.

Why are all my sheets nesting with uneven margins? i.e. vertical margins are as set, horizontal margins are larger.

Thanks guys. Pocketing is one option. Time is a factor though with multiple holes (100's) up to 100mm dia and 3/8" my cutter of choice. I'll try exporting my strategy, thanks for the suggestion.

X4 Router level 1. I mill holes greater than 20mm diameter rather than drill them. Have been using helix for holes up to 35mm diameter but the finish at centre is not good for anything bigger than that - waste piece pops out and can damage workpiece and tool. As far as I can see this cannot be turned off so I resorted to contour using an arc lead in/out with overlap which left the centre piece alone but takes too long to program. Is anyone using a better solution?

Hey thanks for explaining the use of "Wait" Mike. That's a big help to me. Peter.

I selected 2 chains as before, and then reversed the second one, that worked too.

Thanks for the feedback Colin. "Solidnest" handles the solid nests and can be re-tasked to suit required quantities of individual. The Router toolpaths are somewhat limited but that probably stems from Plasma/Oxy cutting origins of the software. We are still evaluating it. As far as nesting toolpaths goes, I've just started using that as opposed to geometry nesting and toolpathing the nests. I think if we stick with Mastercam that's how we'll do it, with or without FBM.

Posted this in Woodwork too: In X3 I could cut a groove or T-slot along an axis with Comp off and return cut the same groove without retracting until free from the stock at the original start point. I would select the first cut from one end of the geometry and the second cut from the other end. This saved much rapiding and z positioning time. In X4 this doesn't work. It defaults to cutting both cuts from one end. Is this a bug? Peter.

In X3 I could cut a groove or T-slot along an axis with Comp off and return cut the same groove without retracting until free from the stock at the original start point. I would select the first cut from one end of the geometry and the second cut from the other end. This saved much rapiding and z positioning time. In X4 this doesn't work. It defaults to cutting both cuts from one end. Is this a bug? Peter.

We've got 2 x SW seats so we really must make the most of SW for design. We bought Nesting with Mastercam V9 but have really only used it to nest wireframe geometry as you noted. At present the SW operators create CAM layouts especially for opening in X4. That's one of the main reasons for wanting to move to nesting solids. To eliminate the need for the wireframe layout. It's all basic parts, nothing special, but holes, rebates and other features are already there in the SW file so it would be great to be able to nest them. I feel like we've been doing things the hard way, converting to dxf etc. I've heard ATP may be an answer to this. Do you know about that?

I guess the most guys will say we should only be nesting toolpaths off the solids anyway. If you think this is the way to go please let me know. Peter.

We did trial solids but can't see any immediate benefits if we can't nest the solids we get from SW assemblies. So we're more interested in solid nesting capabilities than simply manipulating solids. Peter.