Look great!
As far as the Duty Cycle on the main page:
From my Dream UI Thread (viewtopic.php?f=11&t=2754) where I was thinking Out Setpoint Adjustment on the Main Control Panel:
On Oct 13 Jon:
"Some things to consider:
A single temp probe may have multiple outputs and setpoints being activated against it. e.g. a kettle with two heating elements or a fermenter with a heater and chiller. How do you reference a single setpoint on the temperature gauge to accommodate more than one active output/setpoint?
A setpoint value is established at a specific Process/State/Output:
- Multiple process/state/outputs could be trying to assert an output & setpoint simultaneously and only the highest priority process/state/output will actually be used.
- When needing to adjust a setpoint, the actual process/state/output that is currently controlling the setpoint is where the new setpoint must be written, thus changing the current stored value of the process/state/output. What if you also have exit conditions tied to the setpoint value?”
If you put a Duty Cycle Adjustment on the Main Control Panel with just an “out”, you could have the same issue as the Setpoints if you had more than one Process Trying to assert an Out with Duty Cycle. Which one would you be updating?
I would love some method of setting either the Duty Cycle or the Setpoints on the Main Control Panel. If you could do it like Baron Keen has shown in his response just above, you could have the Setpoint and the Duty Cycle on the Main Control Panel and it is associated with the Active State in that Active Process.
Maybe a way of saving some screen space is only have those States that are in Next State of Exit Conditions be shown. In many cases then you would have the Active State and a maximum of 4 additional States. I think generally it would be two (Active State and the Next State where you only have one)
Here is a mock up of yours and Baron Keens combined with my Active and Next State only.
- c.png (26.74 KiB) Viewed 10907 times
Since you no longer have the Web Buttons and they were somewhat replaced by being able to jump to a State by clicking on it in the Proccess Display, you would only be able to jump to the Next States shown. On Processes that were not Active and displayed Always, all states would be shown as now and you could jump to any of those States