larryllix Posted August 16, 2016 Posted August 16, 2016 It would be nice to have a pull down option to enable run (If) at startup run (Then) at startup run (Else) at startup Programs like this may fool users into thinking they will run at start-up since triggers are never true. If time is 3:00 AM Or time is 6:00 AM Or time is 9:00 AM Then whatever lines EDIT: Sleeping on this, I thought this may be more in line with current ISY style. Add a condition line in the program section to be visible from inside the program instead of hidden in the summary only. If startup or time is 3:00 AM or time is 6:00 AM Then whatever program lines would run Then section at startup ------------------------------------------ If startup AND time is 3:00 AM Then not at startup lines Else whatever program lines would run Else section at startup -------------------------------------------
PurdueGuy Posted August 17, 2016 Posted August 17, 2016 I only have 1 program set to run at startup. Then inside that program, I call whatever other programs I went. That way, I can call runIf, runThen, or runElse.
larryllix Posted August 17, 2016 Author Posted August 17, 2016 I only have 1 program set to run at startup. Then inside that program, I call whatever other programs I went. That way, I can call runIf, runThen, or runElse. I use both techniques right now. The 'Enable Run at Startup' in the program summary page is too obscure to the programmer. If logic is added to the If section later, the option doesn't function anymore, and the programmer isn't aware the option is enabled.
Chris Jahn Posted August 17, 2016 Posted August 17, 2016 I use both techniques right now. The 'Enable Run at Startup' in the program summary page is too obscure to the programmer. If logic is added to the If section later, the option doesn't function anymore, and the programmer isn't aware the option is enabled. Either changing the 'Run at Startup' checkbox to a 'run if/then/else' option, or using a 'startup' event/condition may make it more intuitive for new users. I'll open up a feature request to track this, but not sure when it will be prioritized.
rccoleman Posted August 17, 2016 Posted August 17, 2016 I do like the idea of having a single run-at-startup program that spawns everything else. I didn't think of that, and it really simplifies the process. Thanks!
larryllix Posted August 17, 2016 Author Posted August 17, 2016 Either changing the 'Run at Startup' checkbox to a 'run if/then/else' option, or using a 'startup' event/condition may make it more intuitive for new users. I'll open up a feature request to track this, but not sure when it will be prioritized. I prefer the in program line more but it may make backward compatibility difficult. On that note, I would be fine with a warning about backward incompatibilities. It would make more room on the summary chart.
jrainey Posted September 11, 2017 Posted September 11, 2017 My preference would be that there be a standard empty program called "Startup" included in the firmware. This program would always be the first program to run at startup, and scheduled to run at a well defined point after all of the required system startup procedures have run. The user would configure it in the same manner as any other program, excepting that the If condition would be predefined as "startup", and not editable, and lines could only be added to the then section. A last action in the startup program would be to reset "Startup", to prevent the routine from being run again. Setups such as these are standard features in real time control systems such as PLC's and DCS's, although the implementation could be something as simple as an on/off variable 'First Scan' or Startup In Progress' that is readable by programs and set by the operating system at startup and reset at the end of the first scan.
G W Posted September 11, 2017 Posted September 11, 2017 You want an "OnApplicationStart" and I think that's a great idea. Sent from my Nexus 6P using Tapatalk
KeviNH Posted September 11, 2017 Posted September 11, 2017 I like the idea of "If ... Startup". Easy to understand and use. Should run program to completion even if it contains Wait commands, etc.
larryllix Posted September 11, 2017 Author Posted September 11, 2017 I like the idea of "If ... Startup". Easy to understand and use. Should run program to completion even if it contains Wait commands, etc. In the style of other ISY programs, run to completion can be easily effected by unchecking the existing enable option.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.