CUT AND PASTE OPS

[dprovost71]

There seems to be a problem with the cut and paste of operations.

I cut and pasted operations everything seemed fine. Posted and saved it.

I had to make a change and when I reopened the file the operations I had cut and pasted were dirty and it duplicated all the tools in those ops...it was a mess.

Work around is not to use cut & paste. Use the copy and paste,, then go back and delete the unwanted ones. Or the drag method can be used without losing the files integrity.

[Cuda84]

Never used cut and paste, always moved or copied.(drag method) Never had a problem.

 

[Guest SAIPEM]

I've never had a problem with Cut & Paste.

[Mark H]

I have had problems with coping and pasting operations. Long story short, it red Xed the original and copied toolpaths when I reopened the file. I emailed it to QC at mastercam and they said it would be fixed in a future release.

[Keith @ Solid Code Solutions]

I've had and continue to have problems with both methods.Duplicate tools, Duplicate...Duplicate Ops, Dirty Ops (not just the ones I was working with), dissorder in regards to "Grouping".

 

Yesterday I had three or four incidences when using HSM toolpaths (including being very slow and Crashing).

[Keith @ Solid Code Solutions]

quote:

---

I emailed it to QC at mastercam and they said it would be fixed in a future release.

---

I've been having problems with the OP manager for along time and am curious as to which future release QC is refering to. X3 or X4 maybe?

[Thad]

quote:

---

I've been having problems with the OP manager for along time

---

Care to elaborate? Maybe a new thread?

 

Maybe we can come up with some fixes or work arounds until they get fixed.

 

Thad

[dprovost71]

As I stated I use the copy & paste as a work around but Keith seems to have had trouble with that too. I haven't had any problems with the copy & paste.

[Keith @ Solid Code Solutions]

quote:

---

Maybe we can come up with some fixes or work arounds until they get fixed.

---

To be honest and not to be the doughnut hole I don't think there is a work around for these problems. They are at times very hard to reproduce and I've already posted threads talked to my reseller talked to CNC with no resolution. I also understand their everyones difficulty in solving a problem without having the facts surrounding the cause. I have worked for years with Mastercam as most of us have and have delt with issues and have been happy when a work around is available. This is not saying that I am complacent with the quircks in the software, I try to be a pro active as possible right down to working on the other side of the fence for the local reseller for a couple of years.

 

I've tried to get a sounding of this problem from other users on the forum so that we maybe able to find something common but there has been very little responce other that CNC suggesting that I become a "Beta Tester". I'm not really sure why this was suggested considering I feel at times I am beta testing the software.

 

quote:

---

Care to elaborate?

---

The OP manager seems to be unstable particularly when tha file size is large 100MB or more (ie. confused ,loses its structure, has a brain fart)

 

I not going to even presume that I can understand why or how these problems are present or persist and I am sure that there are more peolple than the handfull that have acknowledged the instability. I just know that they exist and are persistant.

[Mark H]

Below is a link to the problem that I had. My work around was by NOT doing any copyingcuttingpasting of the operations. Which took some time to reslect the geometry and set the parameters, but in the long run, this saved time because I didn’t have to regenerate all the toolpaths multiple times.

 

Topic: Toolpath red Xed

[Keith @ Solid Code Solutions]

Mark thats great and I'm glad that that works for you. That solution/work around will not work for me.

 

How many ops/toolpaths do you typically create per file?

[Keith @ Solid Code Solutions]

Thad,

 

Again not to be a pessimist but I know if they knew what the problem was they would/could fix it, but so far I don't think there has been enough people complaining about the problem. I am not in the business of dealing with constant inadequacies of the tools that I use. I'm in the business of producing in the most efficient cost effective manner. i.e. If the tool is broken and can't be fixed so that it works as intended, replace it with one that does work.

[Mark H]

quote:

---

Mark thats great and I'm glad that that works for you. That solution/work around will not work for me.

 

How many ops/toolpaths do you typically create per file?

---

The last file was only 20 operations when I first had problems, but I'm up to 32 toolpaths (and growing) as we speak... but some of my files contain 100+ toolpaths.

[Keith @ Solid Code Solutions]

The file that I am creating now is appox. 50 ops and 250 MB and I'm only roughing right now. This file will grow to appox. 200 path by the time I'm done with it.

[dprovost71]

It appears you have some very large files and I think these problems are due to how mastercam handles ram.

[Thee Rickster ™]

Keith,

 

I have this problem periodically on large 100mg+

files

 

and a solution to get by is to separate components

in its own mcx file, after you done with

the geometry editing, p/l etc.

 

EX: part01cor.mcx

part01cav.mcx

part01slide.mcs

part01coreinsert.mcx

 

It doesen't take much time to separate them

and i feel that paths crunch quicker if the

file are smaller this way.

 

I just keep a copy for the original model in

each file, in setup position to the component on

the cnc, so I can implement Engineering changes

with out confusion.

 

A bit of a PITA but CNC has to know of this

inconvenience.

 

(i have had 1 component create 100mg + file

and have to deal with that.)

 

HTH

[Keith @ Solid Code Solutions]

Could be. I only have my suspisions and that is one of my long standing thoughts.

[Keith @ Solid Code Solutions]

Rick,

 

Those are great suggestions and I do this already to a degree when needed (Such as the job I'm doing right now). The 250MB file is one mold plate. 2 Solid models original and a copy that is scaled for heat treat shrink. I abandoned selecting the solid model for the 2 1/2 ops and drilling right out of the gate choke...choke..sputter...gag! I find that using the solid geometry even for the simplest toolpaths is a PITA and a waste of time, you are better off going back to wireframe and not bother with the soild assocativity....waste of in that respect money especially when certain Solidworks integrated solutions it works awesome and quick.

[Thee Rickster ™]

I always get surface from solids, no question, till

they sort out why its a pain.

 

I even delete the solid after I am satified

with my mold devlopment

 

I separated an iregular contoured surface P/L

from its cavity and programmed them separatly

to keep the cav component in the 100mg + area.

 

Rick

[Keith @ Solid Code Solutions]

Dissmissing the solid from duty is not very practical is it.

 

Dude if that is your picture in your profile. You're a wildman.

[Thee Rickster ™]

Yeah, 3yrs ago,

it all came off...we made fun for the kids..lol

i went bald for my 2mon old, bald son at the time.

 

Past my shoulders now(reliving my yute)

[Keith @ Solid Code Solutions]

That's cool. I did the same years back and I can't stand it getting longer than a #2.

[Keith @ Solid Code Solutions]

Who is you In-House Rep?

[Mark H]

I have noticed problems only with Surface High Speed Toolpaths. Has anyone had problems with copyingcuttingpasting of other types toolpaths?

 

Just trying to narrow it down.

 

As far as solids... For doing toolpaths, I convert everthing to surfaces as well - saves a lot of time.

[dprovost71]

The problem we had was with simple contours.

The file isn't all that large, the one in reference is only about 2.5 meg.