| Author |
|
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: September 09 2011 at 21:01 | IP Logged
|
|
|
Hi Dave (as I think this is new feature request).
I'm anal, so I have PH integrated in my PC such that when it starts up after reboot, it has to successfully control a device and then write to a file within a minute, or the PC reboots again (once in a while communications to the PLm don't come up clean). The problem comes after an outage, where PH tries to Execute Past Events before communication is clear. I'd like a way from a command script to Disable/Enable "Execute Past Events @Startup", so that it can come up disabled, and only be enabled after communications are established. It's an annoyance more than a problem, so don't bother if it's tricky, but figured it couldn't hurt to ask.
thanks!
best
/j
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: September 19 2011 at 22:30 | IP Logged
|
|
|
Jeff,
The capability you want should already be there  .
Just uncheck "Activate Timed Events @ Startup" in PowerHome Explorer in PowerHome|Setup|Preferences. Reinit. This will prevent PowerHome from starting timed events or executing past due events.
Once you've established communications are going and you want to start the timed events, just use the ph_timedeventsctrl function (its in the help file). This will allow you start the timed events process (and optionally execute past due events).
Hope this helps,
Dave.
|
| Back to Top |
|
| |
jeffw_00
Super User
Joined: June 30 2007
Online Status: Offline
Posts: 929
|
| Posted: September 20 2011 at 09:40 | IP Logged
|
|
|
ahh - ok - thanks!!!
/j
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: New Feature Request w.r.t Startup
