Issue with macro variable #3002

[grweldon]

Good day folks,

I've exhausted all my search options and found nothing that address my specific issue.

I have a 35i milling control. I am trying to use the #3002 hour timer to extract cutting times. From what I've read, I reset #3002 to zero before the start of my cutting path. At the end, set another non-volatile variable to the value of #3002. I'm expecting this value to be expressed in some expected format. I don't actually know what I'm getting.

At around the 15 minute mark after I've reset the #3002 variable to zero, the elapsed time (by setting another NV variable to #3002's value) is reading a value of .00099111111. I can't even imagine what this is telling me. I thought it was supposed to be expressed as hours in a decimal format...say 15 minutes would be .25. Obviously this isn't the case. I'm not a newby as far as macro programming, but this has me baffled.

Can anybody fill me in on what I'm seeing and what to do with it?

Many thanks!

Similar Threads:

• Newbie- Accessing Macro Variable from another macro
• Problem- Macro b variable order
• Need Help!- Macro Variable #500
• Macro/Variable Programing
• Problem- macro error 3002

[sinha_nsit]

#3002 is a read/write variable.
Its value is preserved even after a power cycle.
It measure ON time of CYCLE START lamp in 1-hr increment.

[Hardym1]

Have you tried using something like this:

#500=[#3002*60]

[sinha_nsit]

It would give 60, 120, 180 etc.

[Hardym1]

sinha_nsit,
No disrespect intended but we do this all the time. Is something different with the 35i control?

[sinha_nsit]

I do not think it is control dependent. Same behaviour is expected.

The manual says "1-hr increment". Without checking, I just assumed that fractional time is not stored.
Thank you for useful information.
So, for 15 minutes, #500 stores 15?

[Hardym1]

I do not think it is control dependent. Same behaviour is expected.

The manual says "1-hr increment". Without checking, I just assumed that fractional time is not stored.
Thank you for useful information.
So, for 15 minutes, #500 stores 15?

For 15 minutes #500=.25

[sinha_nsit]

I have a doubt.
When the time is in hour, and you multiply it by 60, it should be in minutes.
How to explain 0.25 for 15 minutes?

[grweldon]

.25 hour = 15min.

Thank you all for your posts. I have decided to use a millisecond timer instead since it is giving me output that I expect.

Obviously you may all continue this discussion if you believe it is productive.

[sinha_nsit]

For 15 minutes #500=.25

It should be 0.25 WITHOUT multiplying by 60. Please check and confirm. I am relying on what is written in Fanuc manual. But, mistakes can be there.

[Hardym1]

It should be 0.25 WITHOUT multiplying by 60. Please check and confirm. I am relying on what is written in Fanuc manual. But, mistakes can be there.

There are 60 minutes in 1 hour which means that if you run your machine for 60 minutes then #500 would equal 1 (for 1hr), but anything less than 60 minutes is now equivalent to 1/3600 (the 3600 is the # of seconds in 1 hr.). So if you run your machine for 6 minutes #3002 will equal .0002777778 x 6 (.0016666668). You then have to multiply that by 60 to get the portion of the hour the machine was running. In this case #500 would equal .1 (.0016666668 x 60), if you run your machine for 15 minutes then #3002 equals .0002777778 x 15 (.004166667). Multiply that by 60 and #500 would equal .25 (.004166667 x 60).

[sinha_nsit]

What you are saying is correct with regard to #3002.
But, #500 is not same as #3002.
You have defined #500 as #3000 x 60

[Hardym1]

What you are saying is correct with regard to #3002.
But, #500 is not same as #3002.
You have defined #500 as #3000 x 60

Your right, #3002 is not the same as #500. #3002 is a system variable (you can not see this). #500 is the common variable where we store the data so we can see it.

[sinha_nsit]

Because #500 is #3002 multiplied by 60, what you are saying about the value stored in #500 is not correct.

[Hardym1]

Because #500 is #3002 multiplied by 60, what you are saying about the value stored in #500 is not correct.

This is now becoming unproductive. I do this everyday on my machines as does every other machinist that works here, I don't just read it in a manual.

[sinha_nsit]

Somehow I am not able to convey to you what I have in my mind.
Never mind. Let us stop this unproductive discussion.