Situation is an embedded system that has a requirement for be powered off when not in use.
And "scheduled" to be power on at a given AM time.
The problem is the definition of Power OFF.
If the components are drawing no power, include the motherboard, I will accept this as OFF.
To remotely activate the instrument (it has a 30 minute warm up time) from another system, I can have an existing Ethernet connection be used.
I would like to know how the Wake-on-LAN works.
Given that there will be be a cable from the "shut down" computer to a router and the router is not turned off, then what causes the Wake-on-LAN to activate? It can not be the detection of the carrier - that has to exist when plugged into the router.
Is there a signal or command sent from another system that is detected by the network card that then uses special circuitry to kick the "shut down" computer awake - firing up the OS and powering up components?
If there anything within the OS that needs to know about such a setup?
And "scheduled" to be power on at a given AM time.
The problem is the definition of Power OFF.
If the components are drawing no power, include the motherboard, I will accept this as OFF.
To remotely activate the instrument (it has a 30 minute warm up time) from another system, I can have an existing Ethernet connection be used.
I would like to know how the Wake-on-LAN works.
Given that there will be be a cable from the "shut down" computer to a router and the router is not turned off, then what causes the Wake-on-LAN to activate? It can not be the detection of the carrier - that has to exist when plugged into the router.
Is there a signal or command sent from another system that is detected by the network card that then uses special circuitry to kick the "shut down" computer awake - firing up the OS and powering up components?
If there anything within the OS that needs to know about such a setup?