Sleep functions¶
There are two ways you can make use of the sleep functions: an automatic one, or one were a digital input is used as a sleep request.
Note that the sleeping and waking-up events are themselves pretty "snappy", so they don't introduce any appreciable delays from the user point-of-view.
Automatic sleep¶
In the configuration file, under the [hardware] section, you have an option named auto_sleep.
By default it is false. Set it to true to enable it.
When enabled, every time the controller is cycling back to the Waiting_For_EVSE idle state
(including on the first start), it will immediately go to sleep.
Sleep request IO¶
You can assign a digital input to serve as a sleep request. In the configuration file, under the
[hardware] section, set one of the input (eg. dig_in1) to the value Sleep.
This work on inverted logic, so you need to set it low to request a sleep. Note that it has effect
only when the controller is in (or enter) Waiting_For_EVSE idle state. If you request the controller
to sleep during charging (and keep the request on), it will not go into sleep immediately but rather
wait that the charge session finishes.
You can also keep it low all the time, as it will not prevent a wake-up event to happen and trigger
a new charge session. You could even permanently wire it to ground, though at this point you will be
better off using the auto_sleep function described above, as it will have the exact same effect.
Wake-up events¶
When the controller is asleep it will not respond to any event on the CAN bus or ethernet port. The controller can be woken-up either by:
- Setting
2C2 - SWITCHED_POWERterminal high. - Plugging-in an active charger, as we detect the rise in voltage on the CP line.
Timings¶
- Wake-up from power off (cold boot): ~30s before being available for charging.
- Wake-up from sleep: < 1s, starting charge immediately.
Power requirements¶
The controller should remain powered even when it sleeps. Otherwise it will loose its state and next time power is applied it will do a full boot.
Note
Our charge controllers are designed to withstand harsh power off without damage to the internal file system. The only penalty you incur when removing power during sleep is just longer boot time.
In terms of power consumption, here are some rough measurements:
| State | Voltage | Current | Power |
|---|---|---|---|
| Awake, idle | 24 V | \~80 mA | \~1.9 W |
| Asleep | 24 V | \~47 mA | \~1.1 W |
| Awake, idle | 12 V | \~134 mA | \~1.6 W |
| Asleep | 12 V | \~72 mA | \~0.88 W |
Other considerations¶
When users are logged on the system (eg. by SSH), the sleep is prevented. Note also when there are no longer any user logged in, it will NOT go to sleep automatically. You will have to make the controller go through the