Scheduled wake up and shutdown
In this modern day green age the server should be able to shutdown/wakeup the screens at defined intervals.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Alex Harrington
Related branches
Related bugs
Sprints
Whiteboard
Alex H: Do you have any plans on how that might be implemented? We're planning RS232 control of the screens which will allow the client to power the screen down (which accounts for the greater part of the power usage).
Wake-on-lan isn't suitable as the model we have means that the server may not be able to see the client over the internet (behind NAT) and would be on a different subnet anyhow (WOL isn't routable).
I suppose you could find a way to integrate with the BIOS timer, however once you'd put a client to sleep, there would be no way of changing its wake up time - until it woke and connected to the server again.
The clients I'm running are Intel Atom / Via EPIA based and use between 5 and 20W of power, which is pretty low. For me, I'm more interested in turning the screen off (which uses 150W+) and having the flexibility to wake it on demand by simply scheduling something over the sleep time - but I'm interested to hear what priorities other people have?
---
KEJ - Hiya, whiteboards are pretty bad at feedback :-)
I'm going to give this feedback to your request and another one that asks a similar question.
Much as I love RS-232 (for many more reasons than you can guess) you might be able to avoid specifically playing with RS-232 to handle screen power. If you have a PC attached to the display (which seems reasonable if you're running xibo!) there's a couple of API calls that can be used to ask ACPI to send calls to the video card. If your gear is directly attached then it's probably easier to look at that as a way to trigger monitor power suspension :-)
I'll be back shortly...
---
I wrote up a blueprint that suggests using windows API and providing custom command support that should cover the use cases from this: see https:/
