question

I made you an example solution. It's attached to this answer. Here's how it works:

First, I made a Fixed Resource Process Flow, and then I attached that flow to all of the time tables (you can attach a process flow to anything with object data). The purpose of this flow is to listen to the up and down events of the time tables. The process flow looks like this:

The Scheduled Source creates a token for each table. That token creates a TrackedVariable on a label called Timer. The TrackedVariable is a Kinetic tracked variable, meaning it can have a rate.

Then the token creates two children; one child listens for down events, and the other listens for resume events. When a down event happens, the child sets the rate on the label to 0. When a resume event happens, that child token sets the rate on the label to 1.

What this means is that there is a tracked variable for each time table, continually summing the amount of time it is up.

To use this value in the experimenter as a performance measure, you can use this code:

return getlabel(gettoken(node("Tools/TimeTables/L8", model()), "Wait", 1), "Timer");

This code gets the current value of the label, which is the total "running" time.

maclas-nov-23-updated.fsm