OPs Dirty upon file open

[Guest]

Has anyone any insight as to why files that are fine when closed, open with all of their ops dirty.

 

I have been regenning a file, that WAS fine. I opened it, all ops have gone dirty. Mean while I am in the middle of what has been a 25 minute regen so far and I am none to pleased at the moment.

[Glenn Stephens. from CCCS]

Often times something is corrupted that doesn't show up upon any kind of inspection. The best way to make sure stuff is really clean is to import the operations with their geometry into a new clean file. That usually will tell you what the deal is.

You said that ALL of the operation came back dirty? I would try regenning them one at a time and saving/reopening the file to see where the problem lies.

Are any of the operations tied to a solid? Mastercam occasioanlly will try to regenerate a solid in a different order than how if was created causing much grief.

[Nils N]

That’s what happened to me when I installed MR2, all the op’s were dirty every time I opened MCX. I found I needed to install net Framework and the problem went away. Now, every once in awhile when I change a parameter and try to regen I get a dialog box saying it’s a corrupted file and it won’t regen. Then I make a new op. Not sure if it’s related too your problem.

[JBowman]

All my ops come up dirty also. It doesn’t make a difference if it’s a simple square in wire or a complex 3d in mill. It’s been that way since I started using X

[bestguest]

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.

[thoskins]

I had this happen again today. 183 operations X'd.

I haven't had this happen in quite a while, well since before MR1. The only thing that has changed is I went to dual 15 monitors and oh yea I got an apprentice. No machining or computer background at all. I've got aboout 2 months before I have to turn him loose to solo on third shift. anyway I haven't done anything else but update to MR2. I feel your frustration John.

[P_Scott]

To All,

 

Have you checked the System Configuration to make sure the switch "Restore entire toolpath data in File Open" is active on the Files topic page? That was what happened to me when I first updated to MR1. I couldn't understand why a file I had just saved moments before would open with every op needing regeneration. Until I checked that switch and then it made sense to me. HTH

[Guest]

On my part Peter, yes it is checked

[thoskins]

Mine is checked as well

[beej]

John, I've had this problem since I started using mr1 (using mr2 now). The one thing that I have noticed is that I never ever get it when I'm only using 1 session at a time. If i'm using 2 and one of them is a "heavy hitter", I get it pretty often.

 

the problem usually happens before you close it. I will get some bogus error that says something like, "error regenerating operation", when I know the operation is fine. When I get that, if I save, close and reopen all the ops are dirty. Occasionaly, one get's saved without my realizing that happened. once I reopen I can regen the files fine with no problems.

[bellyup]

i've also had this problem at times, but i haven't noticed a pattern. seems more like a random event for me.

[Keith @ Solid Code Solutions]

I've had this problem a number of time with no discernable pattern. Every now and then it just seems to wigout. When I open a file and all the ops are dirty, at first glance there seems to be geometery in every operation but when I open the geometry manager for the operation there is nothing there. if this is not the root of the problem it is definitely part odf it and is not good. I must say that I havent had tis problem since MR2 was released.

[Ralph@Faustson]

This would be a MAJOR problem for me. It would take weeks to regen the current project I'm working on. As it is I'm using MCam 9.1 SP2...with out any MR's installed because toolpath generation is a factor of 10 slower with mr0105.. using surf rough pocket and restmill toolpaths. Any comments from CNC Software?

[Keith @ Solid Code Solutions]

Ralph S,

 

It is odd that you find MR0105 slower processing your paths.

 

The refinements in X verses V9 and are not measurable in my books.

[edmBosto]

I'm beginning to wonder if it has something to with tweeking the control definition. I find myself changing things there and that may be the reason I get toolpaths that need regenerating upon opening them.

[P_Scott]

Ralph S,

 

quote:

---

with out any MR's installed because toolpath generation is a factor of 10 slower with mr0105..

---

I found when using the MR's in V9 that surface toolpath generation was just the opposite of what you describe. Without the MR's the toolpath regen would take 10 times or more longer than with them. Can you upload any of the files you're working with to the FTP site? Are you working with the files on a local drive or server location? I've found that working with files that are saved locally is noticeably faster than with those that are located on a network drive. HTH

[Roger D]

I think it's the control definition,I did soom work at home and every file had dirty ops when opened at

work.I know the definitions were slightly different

on each computer.I have also had it happen at random

with no particular cause,but that is not very often.

Roger

[Guest]

It should not matter, when you move files the control and machine defs become part of the file. The only time it should see a different MD/CD def is if they are changed.

 

You can change your global copy all you want, it will not affect your .mcx file local copies until you change it out.

[Keith @ Solid Code Solutions]

John,

 

If you move your MCX file to a system that does not have the MD or CD resident on it, will it not reside to your specified default upon opening the file?

[Guest]

They stay in your file if it has toolpaths in it.

[Keith @ Solid Code Solutions]

Right O!

[Roger D]

Thanks John I did't realise that.

Roger

[beej]

Here's a good example of dirty ops. I opened this file this morning, changed a rapid plane, went to regen and got this error. I saved, closed and reopened and now the file looks like the second picture. All I had to do was Regen all. But that took 2 hours.

 

 

after I saved and reopened it looked like this. Regen all and 2 hours later it's fine.

 

[Fred @ Slate Industries]

Beej

That seems to happen when your file gets bigger

and bigger with more and more toolpaths.

 

My work around is to have multiple

Files with the same model

 

Core model (All Drilling )

Core Model (All Roughing )

Core model (finishing Left Half)

Core Model (Finishing Right Half)

Core Model (Weld)

Core Model (Revision 6_23)

 

Etc.

The Real Ball buster is when you lock the Toolpaths and They get Poisioned Anyways

When you open up your file and everything is dirty even though they were locked

Pfffft.

[Zoober]

I just got Dscked by this problem. 200+ ops.

 

Thank God for our network previous version software, 'cause I would be in MAJOR pain right now.

I have over 50 ops that I have tweeked by using toolpath editor to fine adjust. If I were to regen, I would lose ALL my toolpath edits!!!

 

ALL of my ops were locked, and I just went in to make some manual entries for macros.

 

Where is CNC on this!! This could cause a lot of $$ and time lost.

 

I think that it may have something to do with running multiple X's at a time, 'cause I have never had this problem 'till now, and I just had 2 MC sessions opened yesterday, which I very seldom do. I will be running only one from now on till CNC says what this bug is!!

 

Yea, John, I'm pi$$ed like you are!!!