M2 Resets Common Varibles?

[jamesweed]

Does anyone know why my OI-MC control clears the common varibles (#100 - #199) when it reads a M2? Is this set with a parameter? All I find is a parameter that makes the common varibles not clear with a reset. The commons should not clear with a M2 right? Only a reset or power down should clear them?
-Jim

[jamesweed]

This is right outta my idocs...

When M02 or M30 (specified at the end of the main program) is read,
memory operation is terminated and the reset state is entered.

"I guess that reset state is clearing my commons."

[Bluesman]

Originally Posted by jamesweed This is right outta my idocs... When M02 or M30 (specified at the end of the main program) is read, memory operation is terminated and the reset state is entered. "I guess that reset state is clearing my commons."

Try these it should work it is how i have mine set up on our 16 i and 21 i but i think it will be the same for the O series

6001.0 =1 common varibles 1-33 are not cleard at reset

6001.1 =1 common varibles 100-199 are not cleard thru reset

Bluesman

[jamesweed]

"All I find is a parameter that makes the common varibles not clear with a reset."

#6001 is the one!
I was right there staring at the parameter to change, but wasn't understanding that M2 puts control in a reset state. Easy fix, but now I'm wondering if I want to change it? It would I suppose, be safer to have the commoms clear at a M2(reset)??? I come from Allen-Bradleys that M2 did not put control into reset state.

[Bluesman]

Originally Posted by jamesweed "All I find is a parameter that makes the common varibles not clear with a reset." #6001 is the one! I was right there staring at the parameter to change, but wasn't understanding that M2 puts control in a reset state. Easy fix, but now I'm wondering if I want to change it? It would I suppose, be safer to have the commoms clear at a M2(reset)??? I come from Allen-Bradleys that M2 did not put control into reset state.

It all depends on what yoiu are doing with the value of the varibles. For instance I use #100 to trac my process as the program runs. Sometimes my operators stop the program for whatever reason. (Some Legit some not) Rather than have them search out the correct position to start the program over what I do is look at #100 right at the first line. If it is not =1 then it knows it is a posible restart so it looks thru a series of logic to find out where it left off and starts at that point. It is called a safe start. It saves me from multitudes of crashes. It also tracs the tools so i know which one was dome last and at the end I enter a value that tells the program it has completed so it will only run thru each tool one time. I can send it to you if you want to see it

Bluesman

[jamesweed]

I'm tracking with you Bluesman. Thats what happened yesterday, I was using the commons for counters and whatnot and the M2s were clearing my counters. I changed #6001 parameter so they wouldn't clear, then got to wondering if that is "right with the world" or should I let M2 clear them and move my counters and whatnot over to the second set of commons(the non-volitile set). Just trying to stay on the same page as everyone else. Then I decided to make my new custom 4 axis mill with Fanuc oi-mc control match my other 2 older allen/bradley 3 axis mills that dont clear commons with M2, and to heck with "the world". I do profiling milling on round stock, making feed screws(augers). Very math intensive so I'm working on a math sub that all my main programs can call. So I need lots of counters and trackers in my math sub that dont clear at M2.