Gotta step in here and say +100 to Watcher. I have been off the forum for a week or due to the populating and configuring our new facility in Houston. The main reason I didn't have time for the forum is because of wearing out Cimco customer support. I have our DNC system up and runnig now and Cimco customer support now has limp due to our IT B1t3h that has no diplomacy skills. My hat is off to the collective effort of Cimco Customer Support. Saipem, If you really have a problem I can give you an couple of #s to call and I bet you will experience same. I also use your MC reseller (bases in Austin) and couln't get satisfactory service and almost didn't go with Cimco because of that. I don't know if they are learning or just don't have the staff to support Cimco but I know they are Excellent at their base of products. Bottom Line CIMCO ROCKS!!!!!!

How are you doing tool comp. I think I saw that you had it set to tip. If thats the case then its only slowing on G2 and not G3. Maybe it's a post prob.

Sorry robk you beat me to the add reply.

Still doesn't change the fact we are cutting a full radius with a bull nose. Thats a lot of surface area engagement at those rpms. Just my thoughts.

Faden, see mcxbottom cap1. this prolly won't help but I added a .5 bottom up roughing pass to keep the 5/16 from a full rad cut in the inside corners. I think thats where the problem is. It added 10 min. to the cycle time but if it saves a broken tool... IF it don't work you don't have to pay

If it's a full tool radius (.5 tool .25 r) then its a square corner right? How about .0001 chamfer then tighten min. arc rad in configuration. Is the problem chatter in the corner?

quote: As far as operators who 'like to remove sections of programs' I have and easy solution for that: 'Go tell your wife you got fired because you are an a$$hole' Gotta wonder where your at with this. I have a constant problem with this very thing. I know I am personally an a$$hole but thats beside the point. Just run the program, it aint for readin!

I can help you with this, but I had a problem breaking out the angles from your surfaces. Do you have the geo laid out flat. How many degrees does the slot need to span around the circle. What angle does the slot need to be from the X axis. Finally does the cutter need to start off center in the Y axis (I assume you have a rotary and the center of the rotary is parallel with X axis).

Ok let me see if I can get the hang of this insanity. I don't know but this seems to me.

So just for S&G, is there a way to post is some form of macro instead of G code?

I too noticed that the thread switched gears from the beginnig. I expected to open it and read all about Macro-B. But then I just thought strawson was reffering to modeling as programming, which I have heard before.

I fatfingered the - John, I meant +100 for John the fence sitter.

If you have to use plastic pipe for air lines or volume storage, use irrigation piping its much stronger. I have a similar setup at home but 3 phase with a static converter. I fried the spindle servo amp with a similar situation. Sure wished I had bought a pancake compressor that operates on 110v for the toolchanger supply. Still havn't repaired the amp yet.

-100 John the fence sitter. Solidworkd rocks Mastercam X rocks. Would love them combined. From Mcam standpoint, there is a radio button when installing solidworks that asks "allow model changes from sketches" maybe for those who like non parametric this would work. My .02

Hardmill I think your emoticon thingy broke

Thats why I try to remain politically inert. Too much like children when emotions get involved with posting.

This thread almost turned as nasty as a g-string on a fat girl. Glad to see a partial recovery.

Thanks Andrew, your account is almost identical to mine accept I didn't modify surfaces but I did have about 10 solids in the file with between simple to medium complexity that I was working with. I have learned to save a copy of all solids and geometry used to create them on seperate levels for this very problem. I am not sure just how I got unwanted copies of the solids and some of them were corrupt but I deleted them and repaired (re-boolean subtracted) with copies of the solids and it's ok now. I'm betting someone has an idea what is happening. quote: using "X" makes me want to gouge out my eyes with searing steak knives. Persevere I was the same way 3 months into it. Now you coudln't pry X from my processors grip. I found that a dull rusty spoon causes enough pain in the eye socket area that it almost overcomes the X agony.

Yes, that is how I clean up the levels, by blanking the geo I created the solids with. I also copied the geo to its own level just to insure no problems. I don't know what happened but I had to recreate my solid and now everythings ok. Don't know what happened but thought someone might be able to help.

Anyone seen the error quote: No Matching Op File All I did was get out of MCX and when I returned and tried to rotate some geo I receive this error many times. WTF I'm sure I did something stupid Anyone??

Ok I tried the STL based stock representation however I am only allowed to choose one file for stock and there is an op performed outside of MCX (the part gets sawed in two) that I will need to represent. Also does anyone know how to convert an STL into a solid format like X_T or SAT or IGS? Thanks for the responses

Thanks John

John,I haven't used the WCS function yet I remember it in the X videos. What is a quick way to enact it. Also Mark thanks for the information it looks like I'm not the only one this bothers. Imo verify is one of the main reasons I use CAM, other than hopelessly complex programing. This was a feature I especially liked in my former life as a Gibbs Cam programer. Hopefully this will be fixed in the near future.

Hi John, this is what I normally do. One level called stock with nothing else on it. The problem is many parts have many ops and I usually have a MCX file for each op which makes this simple. I have recently started including all ops in one MCX file. I could go into each stock level and turn it on b4 each toolpath group however I thought there might be an easy way to hide the solid until verify needs it. Rick and David, I have tried the STL route but don't think it is as streamlined as using solids. Maybe I will try again, there may be something I have missed. Thanks for all your help

I am machining several ops with one file and have created a solid for the end result of each op. My question is, is there a way in mcx to hide a solid (like turn off it's level) and have the verify show and use it when running. In other words I don't want to see the solids when I am programming toolpaths but I don't want to go back in and turn of every level in sequence to verify the part. I know, I'm dreaming but this will really help save time if anyone knows the solution. Thanks