Locking Operations

[gcode]

We had a new programmer start this week and he locks every operation is every file

I've never used Lock and felt that if you needed to lock your operations you weren't doing things right.

IMO it's a hold over from early days and has no place in a modern Cad/Cam system 

 

What are your thoughts on locking operations

 

Pro's Cons?

 

 

[Guest]

I only lock them if I have in some way manually altered them, other than that, never

[RaiderX]

it doesnt hurt anything?

I do what the panther does.

[MIL-TFP-41]

When using the toolpath editor it automatically locks them...other than that...never

[Müřlıń®]

We had a new programmer start this week and he locks every operation is every file

I've never used Lock and felt that if you needed to lock your operations you weren't doing things right.

IMO it's a hold over from early days and has no place in a modern Cad/Cam system 

 

What are your thoughts on locking operations

 

Pro's Cons?

Used to.... your ops would not go dirty if you locked them.   you could delete all the geometry, make changes, do eo's and still be able to keep your NCI files you had previously made...sometimes your ops would just go dirty and you did nothing wrong....

 

But now locking the ops does nothing...they will still go dirty so it is a useless function.

[neurosis]

I find myself constantly having to lock operations due to changes in mastercam tool path settings. Mostly in the dynamic tool paths.

 

 Some of the new changes haven't always been better. When I figure that out, I lock those operations so I don't end up regenerating them. 

[crazy^millman]

Mixed on it. I have done i and I have not done it. As long as the code is good keep on trucking.

[Rick46]

I use it as a way to mark what paths have been run in my list of groups of paths. It helps when the next shift comes in along with notes to let them know whats been run and what is left to do.

[GoetzInd]

Only when doing something with the toolpath editor. But like others have said, that locks it automatically.

 

Mike

[Guest]

RARELY do I lock an op. When I do, 90% of the time it's in Lathe and I'm forcing something it doesn't want to do and when I get it to finally do it I lock that $#!+ up because if I chance something in a previous op it just hoses it.

 

One time I got a little surly on a crash report, I told 'em the software should just f*****g do what I tell it to, I know what the f**k I'm doing better than some code geek.

 

[Henk]

I use them sometimes.

When a file comes back after a couple of months, i'm thinking why did i lock that operation???

I would prefer to lock individual 'data entry boxes', requested here : http://forum.mastercam.com/Topic5593.aspx

 

 

 

 

But now locking the ops does nothing...they will still go dirty so it is a useless function.

 

They will go dirty..........., BUT the toolpath data is still there, and you can post them.

[Thee Rickster ™]

I use it as a way to mark what paths have been run in my list of groups of paths. It helps when the next shift comes in along with notes to let them know whats been run and what is left to do.

I use it for the same reason,as i never understood what the heck it actually is used for.

[betts]

We used to lock right angle drill ops before post updates that automate the process. Problem was, as mentioned above if someone tried to mass edit something the lock was worthless.

[dan.w]

Sorry for bringing up an old topic where it seems everyone agreed the tool path locking was of limited value, but I thought it might be of value if anyone else comes across this topic. 

 

When you do lock a tool path -

 

What is the difference between a gold colored lock and a grey one?

 

Thanks,

Dan

[guitar]

By locking everything, you have no clue what really needs to be locked when editing. I just keep the high feed paths locked so I know it has been applied.

[dan.w]

I noticed in the original post the consensus is they are of limited value but I'm curious why there are two different colors.

 

Is there something wrong with the underlying operation?

 

More curious then anything else.

 

 

 

[Pilot Plant Supervisor]

I think its gray when you hide the toolpath with the toggle button.

[Jayson Kramer]

Usually it greys if you have two machine defs one being for example mill and the other lath. when you are working on the the mill the ops will grey on the lathe as you are in a Mill machine def ops.

[Teh Bear without Brains kinda idiot]

People who prefare to use lock operations instead of other ways are waiting for trouble and it will

come .

Like Chekhov used to say that if at theater in first act on stage the rifle hanges on the wall

it will shoot in the last act.

Lock is the same rifle.

Enough is to move the part and your part will be scrapped .

I prefer the safe ways and I always find alternatives to lock .

 

This is my humble personal opinion not to offend anyone

JM5a

BR

[Teh Bear without Brains kinda idiot]

I noticed in the original post the consensus is they are of limited value but I'm curious why there are two different colors.

 

Is there something wrong with the underlying operation?

 

More curious then anything else.

~~~~~~~~~~~~~~

some are locked and are locked and masked .

HTH

[Colin Gilchrist]

For anyone curious about the color difference; go click on the "?" Help button in the Operations Manager.

 

Use the Search Tab and search for "Toolpath manager quick reference".

 

On the Toolpath Manager quick reference page, there is a description for every icon that is displayed in the Ops Manager. From that page of descriptions, here is the following info:

 

• A Yellow Padlock indicates that the Operation is "Locked".
• A Gray Padlock indicates that the Operation is "Locked", and the Toolpath Display is turned "off"
• If the Operation is Locked, and Posting is toggled "off", the icon will display half a padlock, and half a "ghost" icon.

[Oppiz]

If I'm in the middle of programming a part and I need to switch to a different part. I use lock  sometimes as a bookmark to remind myself what I was working on when I return to the unfinished program.

[Teh Bear without Brains kinda idiot]

If I'm in the middle of programming a part and I need to switch to a different part. I use lock  sometimes as a bookmark to remind myself what I was working on when I return to the unfinished program.

~~~~~~~~~~~~~~~~~~

I use manual input and write there a note for myself

BR

[Müřlıń®]

 

 

 

They will go dirty..........., BUT the toolpath data is still there, and you can post them.

Ya know I never tried posting them once they went dirty...

Maybe not so us less now thanks.....

[Festus]

grey I think means it is being used by a different toolpath. such as a translate or convert. therefore it will not post. the yellow ones will post