dirty operations

[Jammer™]

Does anyone else have this happen? Sometimes I will be writing toolpaths and when I go back into my ops manager, some of the toolpaths will be flagged with the red x. I know I haven't messed with any of the toolpaths geometry in any way, so I don't understand why it thinks it needs regenerated. Could this be a ram issue? I am running v9sp1 with 256 ram. (I know it's weak, but it's all I got right now)

[iowajim62]

Hi jammer,

No it hasn't happened to me. And I don't think it would be ram. I would look at the NCI for each op and check those. Then I would look at my geometry for something changed or moved. Sorry can't help more.

[Mark H]

I remember you asked this question once before...

 

old post

 

Did you try locking the toolpaths?

 

[ 03-06-2003, 03:14 PM: Message edited by: Mark H ]

[Jammer™]

Mark, Yes I have locked the operations before. That works, but I was just trying to figure out why it keeps doing it. I have tested it several times by going back and forth to my ops manager and geometry screen without changing anything. I thought it might be a ram issue because I am only running 256 and from the flipping back and forth. Thanks for the reply guys.

[Mark H]

Yea I know, the locking of the toolpaths is just a band aid... Just curious, have you submitted the file to Mastercam or your dealer?

[Nominal]

Jammer,

 

Yes. Although not too often. I also have other strange anomolies occasionally. For example I have noticed that if I'm working in milling and then somebody bothers me with a lathe job and I run it at the same time, and post something, then close lathe and go back to mill and try to work with the ops manager in milling ( especially when deleting ops ) she'll give up the ghost or freeze my machine. I'm holding windows 98 responsible. I believe a single application shouldn't be able to crash an entire system. Probably by the time V12 comes out intel with have some kinda hardware level error checking like suns and those types of things will no longer happen.

[Jammer™]

I was going to send it in, but it's not just one particular file. It has happen on several jobs.

[G Caputo]

I have it happen to me also, but only on occasions. I have 512 ram, so i don't think it's your 256 ram issue. Not much help, but i just wanted to let you know that you weren't alone. I'm a newbie at this mastercam thing and I just wanted to tell everyone that this forum is awesome.

[Jammer™]

Darn, I was hoping it was a ram issue so I would have a reason for them to get me more. I guess I will go buy it myself now.

[Nominal]

I've got 512meg of ram and a P4-2.0. I don't think its a hardware issue either.

[mark l]

I did have this happen to me once, I don't really remember what I was doing but it seems to me I was copying toolpaths and then changing something like the size of the tool on the ones I copied and they would all go bad even the ones I had not done anything to, really frustrating seeing as how I had about 15 toolpaths. I don't really know what it was though, I finally finished the job and have not had it happen again.

 

I don't really think it was a ram issue I have 1.0g of it, but hey if you want your boss to buy some more ram I'm sure somebody here will say it is.

[Thad]

Sounds like RAM to me.

 

Thad

[Guest CNC Apps Guy 1]

Yeah, sounds like RAM to me too. (I'm all for helping him out too )

 

Though with Winblows98 you're not going to see any performance gain. Bump up to Win2k Pro or XP Pro and you'll see a jump in performance with the added RAM.

[Rick Damiani]

quote:

---

I'm holding windows 98 responsible.

---

Undobtedly Windows 98 is responsible for the troubles you are seeing. Before my school upgraded, we were using Windows 98 to run MC8, and would have occasional odd-ball results. The 'fix' is to save the file, exit MasterCAM, re-start MasterCAM, and re-open the file. Occasionally, you'll have to re-start the computer as well.

 

If you are using Windows 98, I urge you to upgrade to Windows 2000 or XP Pro as soon as you can.

[Greg Williams]

Sorry guys,

 

This is not a RAM issue, I have 1 Gig of EEC PC800 RAM running on Win2k and I have had this happen on a few occasions. My hunch is that this issue has somthing to do with the WPC system or the T/C planes.

[jeff]

It happens to me frequently.

I don't see how it could be a ram issue!?!

And it's not a big deal to me either because my toolpaths generally regen pretty quickly since they are relatively small usually 100k or smaller.

GO RED WINGS!!!

[Zero]

Yup, me too, win2k p4 2.4 512 RAM and also on the box I used to run MC in which is p3 800 512 RAM only once in a great while. And I think Budgie is right...I think it might be WCS or T/C Plane related too

[cadcam]

The only times I was having this trouble was between a file I did in 9.1 beta and bring it into 9.0sp1.

 

Other wise I do not fine this issue.

 

main boxs:

Box 1

XP pro

1 gig rambus

G4 ti video

2.53 proc.

IDE 7200rpm HD

 

Box 2

XP pro

1 gig DDR

G4 ti video

2 gig proc

SCSI Raid 5

5 Scsi 10,000rpm HD's

[Ray Culver]

Are the operations that end up dirtied dependant in any way on the operation you just changed (like a tranform operation would be) ?

[Jammer™]

All operations are completly independent. I am running windows nt 4.0 sp5

[perseid88]

I have experienced it in Win ME. (256mg RAM)

No trouble to re-generate but it just makes you wonder... what did I just do? I don't remember doing anything significant... Will it still be the same? Should I backplot to check? What am I looking for? Is everything alright?

Mastercam is not intended for those with OCD. (Obsessive Compulsive Disorder)

[Tony]

I have had operations go Dirty

Only because I opened up the parameters to see

What I did in there.

As soon as I closed out (after Changing Nothing)

It was Dirty.

No Biggie...

[iowajim62]

Hi jammer,

Another thought to check out for ya.

When I program, I save (Alt-A) after everything I do. Whether it's copying ops or changing Z depths or depth cuts or anything I save right away. It's just another idea to try.

HTH

[pactec]

Jammer...

 

Does this happen to every file? By that I mean can you make a file that may be clean dirty by just flipping back and forth. If you can then wait for 9.1 and see if it happens there. If some files behave themselve and some don't then there must be an identifiable difference between them. You'll have an easier time to identify where and how this dirtying of the op.s happens.

 

Good luck...

[Ray Culver]

*Sometimes* when you take another file from another computer and simply go into the parameters from the Operation Manager they will be marked "dirty" because inside the operation are stored file names for your destination NCI and for the reference tool file for the tool assigned. If any of these paths are found invalid (like pointing to a file or directory that doesn't exist) they will be updated to a vaild path - and it changes the operation to dirty.

 

Do this test: bring in the file, edit the operation, see it get marked dirty. Regen the operation. Now open up the parameters again and close and see if it again get marked dirty.

 

If it is dirty, then forget what I just said.

 

If it doesn't, then it may be doing what I've written. Now save the file, recall it, and try it again. It should no longer be getting marked dirty.