Resets and Defaults
The Charge Controller offers a sophisticated configuration framework allowing for robust setups for both Manufacturers and Operators. This page introduces:
- default values and how to set them
- the available reset actions and their effects
- and more.
1 The value hierarchy
Every configurable parameter on the Charge Controller has up to three layers of values:
Term | Meaning |
|---|---|
| # Delivery Baseline | The base setup delivered from Bender to the Manufacturer. Most often this only includes the Controller serial number |
| # Manufacturer Baseline | The default configuration after Manufacturer customization. This is the baseline Operators start from. When an Operator performs a factory reset, parameters return to these values |
| # Value | The current runtime configuration. This is what the Operator or Manufacturer sets during normal operation |
The next sections describe how these default values are set, and how the different reset actions move a parameter back up this hierarchy.
2 Delete Private Data
In addition to the reset actions, a Delete Private Data action is available to Operators. This is not a reset action in the sense of restoring default values, but it is a related function that clears sensitive data without changing any parameter values. It is covered here because it is easily confused with the reset actions described below, even though it does not move any parameter back up the value hierarchy.
What it does: Clears sensitive operational data:
- Clears RFID whitelist tokens (local and OCPP-cached)
- Clears the OCPP message queue
- Deletes the transaction/DLM database and related log files
- Deletes certificates related to secure communication and authentication, such as:
- ISO 15118 Plug & Charge certificates (will normally be re-provisioned automatically by the OCPP Backend)
- EEBus communication certificates
- HTTPS/TLS certificates for the Config UI
Preserved certificates:
- OCPP backend communication certificates. Preserved because losing these would break the backend connection, potentially leaving the station unmanageable remotely.
- GLS (Giro-e payment) certificates. Preserved because these are tied to the payment terminal identity and would require re-enrollment.
This action is available in the Config UI while logged in as an Operator under System > System Maintenance >
3 Setting default values
The Controller offers multiple methods for setting default values, depending on the use case and provisioning workflow:
Method | Info | Use case | Read more |
|---|---|---|---|
| # Legacy Config UI > Default pages | The Operator page has a corresponding > Default page in the Legacy Config UI where defaults can be set. | Quick manual default configuration during setup, zero overhead | This page |
| # USB stick | A USB stick with ParameterKey_<suffix>_default files can set defaults during provisioning. This is useful for offline configuration or when preparing stations in batches. | Offline provisioning, batch setup | |
| # Programmatic Provisioning | Manufacturers can write default value files through SSH to automate provisioning. | Streamlining production |
3.1 Setting defaults through the Legacy Config UI
Defaults can be set through the Legacy Config UI through the Operator > Default page.
On this page:
- All Operator parameters are displayed with their current default values
- You can modify any default value
- Submit your changes with to save the new defaults and reboot
To set Operator defaults, navigate to Operator > Default in the Legacy Config UI.
4 Reset Actions
The Charge Controller offers several reset actions.
Reset Action | What it resets to | Resets Operator parameters? | Resets Manufacturer parameters? | Clears whitelists & profiles? | Available through |
|---|---|---|---|---|---|
| # Operator Default & Restart | Manufacturer Baseline | (cached smart charging profiles) | Legacy Config UI, Config UI, RFID, OCPP | ||
| # Factory Reset & Restart | Delivery Baseline | (whitelists and cached smart charging profiles) | Legacy Config UI | ||
| # RFID Master Token Reset | RFID (120s hold) | ||||
4.1 Operator Default & Restart
Area | Item | Explanation |
|---|---|---|
| # Behavior | Purpose | Resets Operator-level parameters back to the Manufacturer Baseline. Use when Operator configuration changes should be removed and the station should return to the Manufacturer's intended Operator setup. |
Scope | This action only resets Operator-level parameters. It does not restore the controller to the Delivery Baseline. | |
| # Availability | Config UI | Available under System > System Maintenance as . |
Legacy Config UI | Available on the Operator page as . | |
RFID | Available through RFID Master Token Reset. | |
OCPP | Available via | |
| # Additional effects | Master-Slave setups | Selected network-related parameters are preserved to maintain connectivity, such as TCP/IP mode, network connection type (Ethernet/4G/...), and OCPP Backend connection URL. |
Smart charging profiles | Cached smart charging profiles are cleared. |
4.2 Factory Reset & Restart
Area | Item | Explanation |
|---|---|---|
| # Behavior | Purpose | Performs a true factory reset, restoring the controller to the Delivery Baseline. Use when a station must be fully wiped back to its original out-of-the-box state, for example before decommissioning or repurposing hardware. |
Scope | This is the only reset action listed here that resets all parameter groups back to the Delivery Baseline. | |
| # Availability | Config UI | |
Legacy Config UI | Available on the Manufacturer page as . | |
RFID | ||
OCPP | ||
| # Additional effects | RFID tokens | Local and cached RFID whitelist tokens are cleared. |
Smart charging profiles | All charging profiles, including cached smart charging profiles, are deleted. | |
Master-Slave setups | Unlike Operator Default & Restart, no network parameters are preserved: this action deletes all Master-Slave pairing and connectivity settings, and the setup must be reconfigured from scratch. | |
| # Notes | Some parameters don't get reset, this is by design. For example, the controller serial number remains unchanged. |
4.3 RFID Master Token Reset
Area | Item | Explanation |
|---|---|---|
| # Behavior | Purpose | The RFID Master Token Reset acts as an additional trigger for the Operator Default & Restart action. |
Underlying reset | The same reset behavior as Operator Default & Restart is performed, restoring the Manufacturer Baseline. See here for restore target, use case, and scope details. | |
| # Availability | Config UI | |
Legacy Config UI | ||
RFID | Triggered by holding a configured RFID master token against the RFID reader for 120 seconds. | |
OCPP | ||
| # Configuration | Master token setting | RFID master tokens are configured through the RFID tokens for reset to defaults setting. |
Timeout | The token must be held against the RFID reader for 120 seconds. | |
Number of tokens | Up to 2 master tokens can be configured, separated by a colon (:). |
Manufacturers may provide Operators with a pre-configured RFID Master Card for added convenience.