Driver Request - Every 15min

[RAV]

Wondering how practically it would be to have a driver that triggers every 15 minutes on the hour, quarter, half and quarter of, like a mantle clock chime?

Having a repeating timer won't be accurate to a clock over time.
Creating a bunch of scheduled items seems to be the other option, but a driver would be easier and more practical.

Recently did an office, and setup adjustable time drivers for the client, so they can control open hours, which block people from turning off lights inadvertently.

Could see many other uses for it as well.
For example - left open/on - each trigger if downstairs off scene isn't true, increase variable, if greater than 3 then .... or garage doors left open, outside lights, gate open, door not locked, etc.
Sure, those can be done by multiple timers, but this would be cleaner and very useful.

[RyanE]

Repeating timer that gets reset every day on a scheduled event would be easy enough and likely accurate enough.

If it's not accurate enough, you could have the scheduler reset it a few times throughout the day, or even every hour.

A lot easier to get going than a driver.

You certainly could create a timer managing driver, but after a certain set of scenarios, you'd basically have to recreate the scheduler plus your timer scheme.

I'm not going to discourage anyone from making a driver -- I'm very pro-driver...    But this seems like it's writing a driver for something the existing scheduler plus a timer could do pretty easily and satisfactorily.

RyanE

 

[Matt Lowe]

We do this for our showroom. Using Variables, the scheduler, and timers that repeat themselves when they expire if the conditions are met. If you needed exact times you could create scheduled events for each time you would need and set the schedule accordingly.

 

[RAV]

1 hour ago, RyanE said:

Repeating timer that gets reset every day on a scheduled event would be easy enough and likely accurate enough.

If it's not accurate enough, you could have the scheduler reset it a few times throughout the day, or even every hour.

A lot easier to get going than a driver.

You certainly could create a timer managing driver, but after a certain set of scenarios, you'd basically have to recreate the scheduler plus your timer scheme.

I'm not going to discourage anyone from making a driver -- I'm very pro-driver...    But this seems like it's writing a driver for something the existing scheduler plus a timer could do pretty easily and satisfactorily.

RyanE

 

Having a resetting timer running constantly won't adversely affect processing overhead any differently than if it was say an agent or driver doing the triggering?

[msgreenf]

10 minutes ago, RAV said:

Having a resetting timer running constantly won't adversely affect processing overhead any differently than if it was say an agent or driver doing the triggering?

No 

[Matt Lowe]

timers have hardly any effect on controller resources. Long programming delays can cause all kinds of weird things. so its best to use them in instants where they won't be issued multiple times. 

 

 

[RyanE]

25 minutes ago, RAV said:

Having a resetting timer running constantly won't adversely affect processing overhead any differently than if it was say an agent or driver doing the triggering?

The Timer Agent is just a C++ driver.

All agents are drivers, but are limited to a single instance, and they show up in the Agents tab instead of System Design, and have a different type of UI.  They don't require any more resources than any other driver, and as the Timer Agent is a native C++ agent, it likely requires fewer resources than the DriverWorks Lua drivers.

RyanE