EV Charge Control and Configuration
Solution Overview
The charger is connected as a subordinate device of the inverter. All the APIs below use the deviceSn of the inverter that the charger belongs to; the charger's own SN is only returned as device information.
There are two scenario types for calling the charger APIs: control and configuration.
| Scenario | Description | APIs |
|---|---|---|
| Charger control | 1. Start charging immediately. 2. Specify the charger's charging mode. 3. Stop charging or exit the current mode. | Set charging mode, Exit current charging mode |
| Charger configuration | 1. Save scheduled charging plans. 2. Set current, power, and charger behavior under EVC load limiting. | Set scheduled charging time groups, Device configuration delivery |
EV Charge Control
Before starting charging or switching the charging mode, you need to identify the charger's current control mode; stopping or exiting the current charging mode does not require distinguishing the control mode.
| Charger control mode | Description | Allowed operations |
|---|---|---|
| Inverter control | The charger works according to the current charging mode or scheduled plan. | Send FAST, GREEN, SCHEDULE. |
| Standalone running | Under EVC load limiting (inverter fault), the charger's working mode is configured as standalone running. | Send start charging. |
| Regardless of control mode | No need to determine whether the charger is under inverter control or standalone running, nor whether charging is in progress. | Send stop or exit current charging mode. |
Inverter Control
Under inverter control, call Set charging mode with deviceSn and chargeMode. The available charging modes of chargeMode are listed below.
| Charging mode | Description |
|---|---|
| FAST (Fast/Eco mode) | The charger outputs at the configured maximum charging power. |
| GREEN (Green charging mode) | The primary goal of this mode is to maximize the use of photovoltaic (PV) generation for charging. 1. If the battery is in forced discharge due to system settings, the charger consumes the energy of both PV and the battery at maximum power as far as possible. 2. Normally, if the battery is discharging or the grid is supplying power in the system, the charger charges at the minimum charging power. |
| SCHEDULE (Scheduled charging mode) | Executes FAST or GREEN charging according to the saved and enabled scheduled time groups. |
While charging is in progress, you cannot switch directly between FAST, GREEN, or SCHEDULE. First call Exit current charging mode, confirm the exit succeeded, and then deliver the new charging mode.
Standalone Running
When the inverter is faulty and EVC load limiting is triggered, and the standalone running mode and charging power have been pre-configured for this fault scenario, you can call Start charging to charge.
This mode is a fallback solution; the charging mode cannot be selected.
Under EVC load limiting (inverter fault), the charger is set to standalone running mode: energy comes only from the grid, and charging proceeds at the configured power.
Stop or Exit Current Charging Mode
Call Exit current charging mode in the following scenarios:
- You need to stop an ongoing charging session.
- You need to exit scheduled charging mode.
- You need to switch from FAST, GREEN, or SCHEDULE to another charging mode.
Exiting scheduled mode does not clear the saved scheduled time groups. The next time SCHEDULE is selected, the saved time groups can still be used.
Control API Error Codes
| API | Error code | Trigger scenario | How to handle |
|---|---|---|---|
| Set charging mode | error.47101 | The charger is currently in standalone running mode; FAST, GREEN, or SCHEDULE cannot be delivered. | Confirm whether the device is under EVC load limiting; deliver the charging mode again after the fault is resolved. |
| Set charging mode | error.47102 | The charger is not in standby, and switching the charging mode is not allowed. | Confirm the charger is in standby and retry. |
| Set charging mode | error.47103 | The charger is charging, and the charging mode cannot be switched directly. | First call Exit current charging mode, confirm success, then deliver the new mode. |
| Set charging mode | error.47104 | chargeMode is not FAST, GREEN, or SCHEDULE. | Check the charging mode parameter and submit again. |
| Start charging under EVC load limiting | error.47701 | The charger is not currently in standalone running mode under EVC load limiting. | Confirm the device has triggered EVC load limiting and the standalone running strategy is configured. |
| Start charging under EVC load limiting | error.47702 | The charger is not in standby, and switching the charging mode is not allowed. | Confirm the charger is in standby and retry. |
| Start charging under EVC load limiting | error.47703 | The charger is already charging. | No need to call start charging again; to stop, call Exit current charging mode. |
| EV Charge APIs | error.47311 | The target inverter has no charger connected. | Confirm deviceSn is the inverter the charger belongs to, and check device wiring and connection status. |
| Control APIs | error.70006 | The device or charger is offline. | Restore communication, read the status again, then perform control. |
| Control APIs | error.70007 | The calling account has no device operation permission. | Check whether the account owning the Token has been authorized for this inverter. |
| Query async control result | error.42003 | recordId does not exist. | Confirm you are using the recordId returned by this delivery API. |
EV Charge Configuration
Configuration scenarios are used to save charging plans and parameters that take effect later.
Scheduled Time Groups
Scheduled time groups define the automatic charging periods and charging method under SCHEDULE mode. Setting time groups does not automatically switch to SCHEDULE; the correct flow is as follows:
- Call Set scheduled charging time groups to save time group 1 and time group 2.
- When the scheduled plan needs to be executed, call Set charging mode with chargeMode set to SCHEDULE.
- Use the returned recordId to call Query async control result to confirm the time groups have been saved.
Only time groups 1 and 2 are available. Both groups must be submitted together each time, passed in ascending order of timeGroupId, without omission or duplication.
| Field | Required when | Description |
|---|---|---|
| timeGroupId | Always required | Time group identifier; only 1 and 2 are supported. |
| enable | Always required | 0 disabled; 1 enabled. |
| startTime | Required when enabled | Start time, format HH:mm. |
| endTime | Required when enabled | End time, format HH:mm; earlier than the start time means crossing midnight. |
| chargeMode | Required when enabled | Charging method within the time group; only FAST or GREEN is supported. |
Scheduling rules:
- When enabling a time group, start time, end time, and charging mode must all be provided.
- To disable a time group, you may pass only timeGroupId and enable=0; if any time or mode field is provided, all three fields must be provided together.
- The start time and end time cannot be the same; 22:00-06:00 represents a period crossing midnight.
- After the two time groups participating in this validation are expanded according to the cross-midnight rule, they must not overlap.
- Time group settings are not restricted by the current charging status, but they are only executed according to the plan after SCHEDULE is selected.
Use Get scheduled charging time groups to read the two groups currently saved on the device. Disabled time groups also return their saved times and mode, which is convenient for page display and re-enabling.
EV Charge Configuration Parameters
Charger configuration parameters are saved via the general Device configuration delivery; configuration items not submitted keep the device's current values.
Applicable Conditions for Standalone Running under EVC Load Limiting
Before setting the standalone running mode and charging power under EVC load limiting, confirm that the inverter model and firmware version meet the following conditions:
| Model | Supported firmware version |
|---|---|
| MHS 3-8K | V1-0623-0000 |
| MHT 4-20K | V1-0623-0000 |
| MHT 25-50K | V1-0623-0000 |
| M2HS 3-6K | V1-0600-0000 |
| M2HT 25-50K | V1-0600-0000 |
| M2HT 5-10K | No firmware version check required |
| M2HT 10-30K | No firmware version check required |
| M2HT-30K-120-AC | No firmware version check required |
| M2HT-125K-300 | No firmware version check required |
| Parameter | Description | Range | Unit |
|---|---|---|---|
| chargerMainBreakerCurrentLimit | Main breaker current limit | [6, 1000] | A |
| chargerMaxPower | Max charging power limit | Determined by the charger model chargerDeviceType ECA-S07K-BS0: [1.4, 7.0]; ECA-S11K-BS0: [4.2, 11.0]; ECA-S22K-BS0: [4.2, 22.0] | kW |
| chargerIndependentPower | Standalone running power under EVC load limiting | [minimum charging power, rated charging power] | kW |
| chargerInverterAbnormalStrategy | Charger running strategy under EVC load limiting | 0 standalone running; 1 inverter-controlled running | - |
These parameters are submitted via sendSettingItemList, and all values are passed as strings; a single delivery may contain multiple parameters, and configuration items not passed keep the device's current values.
After configuration delivery, use Query configuration result to check whether each configuration item was executed successfully.
Configuration API Error Codes
Scheduled Time Groups
| Error code | Trigger scenario | How to handle |
|---|---|---|
| error.47301 | Incomplete time group configuration, e.g., group 1 or 2 is missing, or an enabled group lacks the start time, end time, or charging mode. | Submit groups 1 and 2 together each time; when enabling a group, fill in all three fields completely. |
| error.47302 | Invalid start time of time group 1. | Check the time is in HH:mm format and the start time differs from the end time. |
| error.47308 | Invalid end time of time group 1. | Check the time is in HH:mm format and the end time differs from the start time. |
| error.47309 | Invalid start time of time group 2. | Check the time is in HH:mm format and the start time differs from the end time. |
| error.47310 | Invalid end time of time group 2. | Check the time is in HH:mm format and the end time differs from the start time. |
| error.47303 | Time groups overlap. | Expand both time groups according to the cross-midnight rule and adjust them to non-overlapping periods. |
| error.47304 | Invalid time group charging mode. | chargeMode only accepts FAST or GREEN. |
| error.47306 | Invalid timeGroupId. | Only use time groups 1 and 2. |
| error.47307 | Duplicate timeGroupId. | Submit time groups 1 and 2 once each. |
| error.47312 | Invalid enable value. | enable only accepts 0 or 1. |
| error.47313 | Partial optional fields passed for a disabled time group. | When disabling, pass only timeGroupId and enable, or pass the start time, end time, and charging mode together. |
| error.47311 | The target inverter has no charger connected. | Confirm deviceSn is the inverter the charger belongs to, and check device wiring and connection status. |
| error.70006 | The device or charger is offline. | Restore communication and submit the configuration again. |
| error.70007 | The calling account has no device operation permission. | Check whether the account owning the Token has been authorized for this inverter. |
Status, Alarms, and Charging Records
The charger's configuration data is returned with its parent inverter's configuration data, and its running data is returned with the parent inverter's real-time, historical, or MQTT data. See Inverter configuration data and Inverter telemetry data for field definitions.
The OpenAPI returns running sample points and does not directly generate charging sessions. The caller can form charging records as follows:
- Group the data of the same charging session by the parent inverter's deviceSn and chargerChargeCount.
- On first observing a count, chargerStartMethod=0 does not create a record; other values may create a pending record.
- Keep using eChargerSession to update the energy of the current session.
- When chargerEndReason is 1, 2, 4, 5, 6, 7, or 8, use the timestamp of that data packet as the end time, and the eChargerSession of that data packet as the final charged energy.
- Do not mark a charging record as finished before a valid end data packet is received. If data is interrupted, backfill sample points via historical telemetry data.
For alarm codes and handling suggestions, see the Alarm code list.