Beat me to it.I knew it could be done but could'nt remember how. Thanks

Is there an easy way to convert a drafted note to line and arcs?Thanks

Mike, Are you working for the previous Mastercam VAR that you were associated with?What booth will you be in IMTS?

My guess is that you have a translated Pro-E file.To verify this right-click on the .stp file and open with any text editor.The header will state what system translated the .stp file.

Take a look at Cimatron.The electrode module is very good and you do not need a watertight model to start with.

Anyone have the Haas logo in solid or dxf format they would share? Thanks

To be fair most of the time when I post here it is with an issue that I am having with MCX.The majority of the modeling I do is in SolidEdge or ProE but lately I have had to do some patching and runoff surfs and I gotta say that Net Surf and Fence Surf are just killer.A real timesaver. Regards

PGW STEVE, Make sure that under "Linking Parameters" you have retract set to "Full".If your machine doglegs on a rapid you will violate every time. The other thing that happens when using the HSM routines is that when any change is made to your tool the system will reset itself to the default surface stock settings

Ray, Our motto is "Any question ask a McQuestion"

Just a follow up to this thread.I spent an hour or so yesterday with Ryan from CNC Software on a GoTo Meeting trying to reproduce the error that we are getting on file reopen.I reprogrammed the same part that I posted on the ftp site a few days back and could not get MCX to reproduce the errors.That being said I know that there are quite a few other users having the same problems that I am so I know at least I am not insane.

McamNut, I uploaded a file I sent in to QC about a week or so ago called "Wierd.zip" on the ftp under MCX files.Open it up and backplot.Make a note of what type of sequences exist in the operation manager and what actually backplots.

McamNut, Give QC a call.I have had this problem many times before.Gotta a couple of questions for ya Do you work across a network? Are you coping ops from 1 file to another? Are you doing a "Save As" to save for op2 keeping the existiong tool list?

I also have had this issue.Are any of the ops that are dirty High Speed Surfacing routines by anychance?I have noticed this with almost any file that I have that contains the Cimco Integrated toolpaths.

If you want a feel for some the issues current Cimatron users have check here: http://207.89.153.227/support/forum/

I am gonna jump in the fray here... I have many years experience on both Mastercam and Cimatron.Both are good products in their own right.I personally like Cimatron for mold and electrode design.I will also use Cimatron on occasion today if I need true stock model machining.Anything else it gonna be Mastercam or Gibbs.I kinda equate this to whether I am gonna program a specific item for a Mori or a Makino. The biggest problem I see with Cimatron is lack of users here in North America.It is much easier to find a programmer for Mastercam than Cimatron.Problay 100 to 1 ratio or better. Later

Thad, One of the things I have found is that when doing a "Save as" creates problems.If for instance I have a die blk that is programmed to be op1 and save it as op2 to keep my toolist intact after deleting the op1 sequences and programming the op2 sequences MCX seems to "hang on" to some of the op1 legacy NCI data. When I reopen the op2 file sequences will be "dirty" , out of order or completly different than what it was saved as.I contacted QC about this issue and what told that there is no way to purge the file of any legacy data. I have programmed this way for many years.Most of the time op2 will have some of the sequences that op1 did.Just reselect Geometry and regenerate.I do not know of a faster way to program than using stored ops and reusing sequences.At this point I am reprogramming my sequence library on the fly as needed and storing it in a different location to eliminate the hassle.I only have about 950 more stored sequences to go. Later

Thad, This in my opinion is a huge oversight/bug that I have seen since I started using Ver X.I have over 1000 stored ops in a master library.I run into this constantly.The only work around that I have found is to import the operation(s) and correct the errors and than re-export back to your library.This function also likes to change the D & H numbers so that they do not match your tool #. The other strange thing that i have seen is on imported drill ops Mastercam will "collect" phantom points when drilling.This and the above mentioned issuses have been logged recently with QC. Later

Thad, I have run into this also.I have probably over a 1000 or so stored ops.Be very careful when using stored ops.Check out each imported op very carefully.Tool numbering on imported ops is still messed up.If you change the tool number you must open the Op using the tool and reselect the tool or you D and H #'s will not match your tool #.

Toolman tell me alittle about Southern Kentucky...

File Merge imports the data into a group.Right click on Group and Delete.

This is something we do all the time.Run it like a production job.I program 1 die blk save and post and import the sequences into the next part.We have reduced our build time by half or more.Just finishing up a $125000.00 tool today that is in the press making parts.Started on it 3 weeks ago today with 1 HAAS and 1 Bed mill and a Solid Edge 3d design

No, Just a solid and 2d geo.

Smit, Almost every detail I program here is derived from a simular detail.I see no reason to reprogram a feature if I programmed it a week ago on a different job.In my opinion this is the true power of MCX and versions before it.Once it is programmed I can always pull it for an old job. I also over the years built an extensive custom tool library and custon operations library for common features such as cap screwsa dowels and even some surfacing .I use this day in and day out.Now every program I post I verify the tool# matches the D & H # at the top of my program in the tool list.If that is good it will run fine.

Thad, The answer to your question is yes.It does not matter if you have "assign tool #'s in order" checked or not.

Smit, I run into this all the time.There is no consistent pattern of behavior that I have been able to put my finger on.The thing that really blows is even if you correct the settings in the tool manager and regenerate the dirty ops you must open each op and reselect the tool for the changes to take effect.Maybe I am missing something but I can not seem to get it to come out right regardless of what I set my machine defintion settings to.If you fiqure it out let me know please. Later