I just copied a spot drill 90 deg from one machine group to another and had change the angle to 118 deg. Has anyone else noticed this happenning? Its happened to me a couple of times this week.

quote: Try using import and importing the toolpath then you will be prompted "A similar tool exists would you like to add a second" You will also have the option to import the geometry too if you want the tool path to run the same path which will save you from reselecting drill points and chains I don't think he is refering to importing from a OP library or another MCX file, rather just copying a toolpath from within the OP Manager. Is this correct? quote: it is a bug. i don't recall if its been fixed but numerous posts have been made about it. I haven't had it happen for some time now but i don't drag and drop anymore. I wasn't aware that a bug report had been done on this problem. Do you have a bug # Linky

Remember this is occuring once all is set and I am programming with in a given machine group.

Understandable, but that is not the case here. I have multiple machine groups but when I change from one Machine group to another..I first change to another level if the geometry differs then go to the View Manager to check that the T/C planes are equal to my WCS wich automaticaly changes (if defined from with in the Machine Group)when the marker (Red Arrow) is moved from the group to another. I'll then be programming away and then I notice that the T/C planes change from what I had set them to.

Zero, Are yopu talking about dragging the marker from one Machine group to another, if so it is patially understandable. This is happening from within one machine machine group.

I don't have a problem changing one or all to the appropriate planes. This is more as I am programming on a particular face with a defined WCS and then having the T/C Plane switch at one point to something else I suspect during the processing of a toolpath.

quote: I use this setting and it has reduced my probs. in the planes manager set it to planes ALWAYS = WCS. have had few probs since. just wish we could make it default to this. With this set "ALWAYS = WSC" the T/C Planes are still not staying = to the WCS.

Thanks Steve, I'll take a look and let you know any results.

Ya that's great, there hust doden't seem to be any rhym or reason for the T/C planes to be switching the way they are and yes there should be an option to make this a default.

Ya that's great, there hust doden't seem to be any rhym or reason for the T/C planes to be switching the way they are and yes there should be an option to make this a default.

Matt, I always leave the normal 8 alone and only modify the copies. If I am to copie the Top for instance and then redefine the Z origin periodically the T/C planes will scramble and move to other planes and sometimes not together. As you know this is very dangerous and I maintain a vigilant eye on it all the time.

Bump

I've copied some of the normal system planes and then redifined them to work with muliple stacked mold plate plates and set up a different Machine group for each of the plates and defined "Stock View" and "Safety Zone View" to the appropriate copied/define plane. Now the problem is that I can be working on a particular plate (working within the same machine group. I will go into the view manager and set my T and C plane = to Gview and the seem to keep changing and not staying as it set. Am I missing something?

Sweet

Wow! Good point!

Thanks, I better get another coffee

quote: is there a way to make this my default setting for planes? as it is now everytime i bring up mastercam i have to go in and change it. if i don't i have had some bad code because it didn't have correct home position. Make what your default setting for planes?

Bogusmill, I will have to check the actual amount of procsses running but really the only thing that is running of that is of any great size is sql network. I will take another look and let you know.

I ran a few more comparative test on my M90 and all come in at around 11 minutes.

Set affinity to 1 CPU 11min 5sec.

11 min 4 sec. After setting ajustment.

thanks I'll give it a go and let you know.

quote: quote: -------------------------------------------------------------------------------- I would expect at least a 10% advantage wit the the 2.16 GHz cpu over my 2.0 GHZ CPU ( The CPU's are more like "1968 MHz" and rounded up to 2GHz. -------------------------------------------------------------------------------- My 8 min. 5 sec vs. your 10 min. 2sec. is closer to 24%. I was coming in at 10min 55sec with the 2.16 GHz machine just with the 1500fx card as opposed to the 2500fx.

Same here just no Symantec to turn off. I am running MS "Onecare" which by the way is not such a system hog and seems to be doing the job. I just did a new install from formatted Drive right before I ran the bench mark. I think I'm going to revisit the test.

bogusmill, Is that the first time around or second?