How is $ROBRUNTIME evaluated internally ?

Hello,

KRC2 / KRR5.6

The manual states that $ROBRUNTIME gives the cumulated amount of time when drives are switched on.

But I could not find how to determine when drives are effectively switched on in the manual.
I've looked at $DRIVES_ON (pulse) and $PERI_RDY but it does not seem to be correlated as $PERI_RDY could be true while $ROBRUNTIME counter is stopped.

Can someone explain precisely how is $ROBRUNTIME computed ?
Would the time when PRO_STATE1 = P_ACTIVE be a good approximation ?

Nota : my goal is to compute a weighted value of $ROBRUNTIME (weighted by $OV_PRO).

Thanks,
Lionel

Ok,

So "I" in "SRI" is green when $PERI_RDY = true ... and the question remains fully open.

Indeed when $PERI_RDY is true the $ROBRUNTIME counter can be stopped (for instance if no program is selected).
So the manual (KSS 5.6 END V1 en p67/185) is possibly misleading :

Quote

Operating hours. The operating hours meter is running as long as
the drives are switched on. Alternatively, the operating hours can
also be displayed via the variable $ROBRUNTIME.

So what is the condition that makes $ROBRUNTIME count or not ? Could it be :

PRO_STATE1 == #P_ACTIVE && $PERI_RDY == true

Well, I still don't fully understand what you are saying.

See my screenshots : the "I" is green (PERI_RDY = true), no program is selected by the robot interpreter, and $Robruntime is idle (at 55809).

So you said "I is green" <=> "drives are on" <=> "$ROBRUNTIME is counting".
But I see that in some cases "$ROBRUNTIME is NOT counting" when "I is green" ...
What am I missing there ?

I am on KSS5.6 / KRC2ed2005

1) I am working on a maintenance plan so it's good to know what is precisely behind $ROBRUNTIME and the manual is visibly misleading.

2) I am developing a service that sends notifications when a src program is about to finished. The src programs are generated with Powermill and I get an expected simulation time from it. This simulation time is hard coded in the program when it is exported (postprocessing). My service reads this value when the src program is started and tracks the progress time of the program. The progress time must be 'normalized/weighted' to take into account the current $OV_PRO. When the progress time is about to reach the simulation time (lets say 5 minutes before) a notification is send to the operator.

=> So I was looking how to build an accurate progress time. I was thinking of $ROBRUNTIME but now I think I would better write my own counter timing when PRO_STATE1 == #P_ACTIVE.

=> So the question is still open What is the condition for $ROBRUNTIME to count ?!