Morph is a pretty slick toolpath. I agree with Ron on that... But I need some advice. What am I missing for controlling feedrates in the slice linking. I have it set to blend spline currently and this helps the machine slow down, but I am getting gouging as it is a gantry router and I am running 15000mm/min. AICC isn't for some reason recognizing the blend spline for what it is and isn't slowing the machine down enough. Maybe I need more control options, but for now, can it be controlled through either toolpath parameters, or the post? I am guessing the post might be one way to tackle it as the nci shows 50 and as the cutpos status during linking and the last retract. But I am guessing control flags would be a better way to look at this in the post.

Planes were off on one that wasn't completing, but the other wasn't so in this case nothing seemed to help other than a full reboot, which took care of it. Seems there are multiple issues with stock model... When are they going to improve on it a bit more, seems to be very buggy. Large ball tools + rotary = crash, crash, or just crunchin forever. NCI is only like 2000k. Not that big in terms of surfacing paths that I normally create.

Have you ever had a stubborn stock model? You calculate, it take 10 minutes, finishes, then doesn't show up still as dirty. Seems this used to happen and a reboot would take care of it, now its being stubborn and won't come up. ugh, feels i am making a career out of this darn part.

Just money.... then they will send you a hasp update file to get the added options onto your hasp. Same process as maintenance.

I have been getting used to the old coons patch path. I wish it had linking, roughing, translating and tool axis controls like in the moduleworks paths, would be stupid powerful for creating smooth no bs five axis paths for ball mills.

Wouldn't the || return only if the left or if the left and the right are true. But would return false if only the right is true?

I am not a c# guy, it was just a guess. I was just guessing that the .Contains object was returning a Boolean value. By no means was I suggesting something based on direct knowledge. That being said, hopefully Mick or someone else can chime in and educate us a little bit. Would be nice to add to the memory bank for down the road.

Ben, You said it better than I. But that's how I did it last and there wasn't any error.

Change your method a little bit, I just did this the other day... Draw a line tangent to the two arcs, Draw a line with its direction the way you want the tangent line to be pointed. Then use dynamic xform to rotate the solid plus the tangent line you first created. I don't think this method had an issue out there that far as I checked the angle of the tangent line and it was perfect on 0.

Try var faceMill = description.Contains("FACE MILL") + description.Contains("SHEAR HOG");

When will the full release of 2018 be?

Ron, Can I email you a file for a sanity check?

Folks, I have been trying to edit some surface paths to eliminate some studder points. Mostly I have been successful with filter setting but there are a few points I still need to delete so the machine won't studder at them. Toolpath editor seems to take forever to do anything, I remember you used to be able to just scroll through real quick, now it takes 20 seconds to switch from pass to pass or up to a minute to close the dialog. I am wondering if it is graphics related. I have a K3100M and 32gig's of ram. I appears if I change the graphics settings to integrated, it works better, but still laggy, and closes super slow, but still faster than with the quardo card. Something just doesn't seem right. The path I am playing with is only 238k. I have routinely worked with paths 20 - 30 times larger in the past with no issues. Ideas? Maybe need to play with video card settings? Or is something else wonky causing excess calculations, system tolerances? I am stuck here, my system has seemingly been sucking pretty bad lately. I have run some benchmarks on the card, not sure on how well it did as I have not been able to compare it to anything. But didn't seem to choke at all on the open gl test, it ran better than the integrated card did.

No kidding....

If he proves he has a valid SIM people will gladly help. Sounds like it could be in the op or the post or both. All are pretty easy fixes.

I am thinking it isn't solids aware. This would likely be an enhancement request?

I want to resurrect and add to this. Used to be you could also select any point on a solid as your limit between point. Now I can't select anything other than a point and it catches me all the time.... Have to close, go back and create points, then reopen select and whatnot. What am I missing here?

0i or 31i? i doesn't mean much.

No, but its not terribly hard to get some values that will work well for you. What is the machine?

You need to look at 8465 and 8466, see if they are zero, if they are. Then look at 13626 and 13627. They are the R1 and R10 values that will be interpolated depending on if you select something other than 1 or 10 and written to 1432. If they are zero when you command R1 it will write them to zero. You may need to setup all of the 13600 parameters if you want to use R1-R10. Otherwise you will want to not use that code and restore your original settings.

Cutting Wood, It is an Inserted Cutter is made by Fapil in Italy. Were you referring to use Morph to save out geo from to then generate surfaces from using net surface or coons?

So I have a minor annoyance. I am looking to create a tried and true method to alleviate this issue. From a cutting perspective I can create a great toolpath. One hitch, it runs slow on the machine because of sharp internal corners due to size of tool. Even a small radius (1-2mm) helps significantly to keep the rotary moving instead of stopping. There isn't really anything I can do about the size of the tool, and I go in after and rest machine it with some surface blend paths, or sometimes pencil, but rarely, I can usually get better motion by manually determining where I need to cut. I think if there is a good method to create these blends it would help me identify where I will need to rest machine as well. I am sure it will help set me up for faster creation of rest machining geometry. Smoothness of path is key as I try to keep moving between 10,000 and 20,000 mm per minute. Sooo. Anywho. I think the answer is the create surface blends with a larger internal radius. This is where I am weak, lazy, or both. I need to gather some advice from the masters. I have never been known to be lazy if I have a path to follow that will be successful, otherwise I will drag my feet and ponder too much. Sample file attached. I am looking to create a blend between blue and pink without violating green, my rough tool is an 80mm lolipop. So I am thinking something like a 45mm radius would be a good place to start. I am not looking for people to do this for me, just need to be led down a good path. End_of_Part.mcam

Would it be possible to check during preread, or when you output with the post if you have the check box checked for the approach/retract in the op? Is it flagged differently in the NCI?

Looking at the video it was just the camera perspective that made it look like the head C was moving. I believe it was parked and the table was moving. If you look how the head is pointed at the window, it seems to me to be parked. If you had the time, I suppose you could spend the time to split the about "Z" movement between two rotaries, this would in turn lower accelleration on that "result". However you would also need to be aware of other axis movement/acceleration. I am guessing you would not be using tcp in this case and would let the post figure it all out. It would be interesting to see if any controls out there these days can handle tcp with three rotaries, vs just two like normal. I have a machine with three rotaries... Would be interesting to see if I could apply wsec or tcp on my rotary table as well.

Worked! Pain in the butt, however, since this has cost me a spindle before, not terribly worried about the extra effort.