1# Charging Current and Voltage Limit Customization
2
3## Overview
4
5### Introduction
6
7By default, OpenHarmony supports setting of charging current and voltage limits. When a device is being charged, the battery temperature may become excessively high due to the impact of ambient environment. In such a case, the charging current or voltage needs to be limited to ensure safety use of the device. However, the impact of charging current or voltage on device safety varies according to product specifications. To address this issue, OpenHarmony provides the function of customizing charging current and voltage limits.
8
9### Constraints
10
11The configuration path for battery level customization is subject to the [configuration policy](https://gitee.com/openharmony/customization_config_policy). In this development guide, `/vendor` is used as an example of the configuration path. During actual development, you need to modify the customization path based on the product configuration policy.
12
13## How to Develop
14
15### Setting Up the Environment
16
17**Hardware requirements:**
18
19Development board running the standard system, for example, the DAYU200 or Hi3516D V300 open source suite.
20
21**Environment requirements:**
22
23For details about the requirements on the Linux environment, see [Quick Start](../quick-start/quickstart-overview.md).
24
25### Getting Started with Development
26
27The following uses [DAYU200](https://gitee.com/openharmony/vendor_hihope/tree/master/rk3568) as an example to illustrate customization of charging current and voltage limits.
28
291. Create the `battery` folder in the product directory [/vendor/hihope/rk3568](https://gitee.com/openharmony/vendor_hihope/tree/master/rk3568).
30
312. Create a target folder by referring to the [default folder of charging current and voltage limit configuration](https://gitee.com/openharmony/powermgr_battery_manager/tree/master/services/native/profile), and install it in `//vendor/hihope/rk3568/battery`. The content is as follows:
32
33    ```text
34    profile
35    ├── BUILD.gn
36    ├── battery_config.json
37    ```
38
393. Write the custom `battery_config.json` file by referring to the `battery_config.json` file in the default folder of charging current and voltage limit configuration. For example:
40
41    ```json
42    {
43        "charger": {
44            "current_limit":{
45                "path": "/data/service/el0/battery/current_limit"
46            },
47            "voltage_limit":{
48                "path": "/data/service/el0/battery/voltage_limit"
49            }
50        }
51    }
52    ```
53
544. Write the `BUILD.gn` file by referring to the `BUILD.gn` in the default folder of charging current and voltage limit configuration to pack the `battery_config.json` file to the `//vendor/etc/battery` directory. The configuration is as follows:
55
56    ```shell
57    import("//build/ohos.gni")                # Reference build/ohos.gni.
58
59    ohos_prebuilt_etc("battery_config") {
60        source = "battery_config.json"
61        relative_install_dir = "battery"
62        install_images = [ chipset_base_dir ] # Required configuration for installing the battery_config.json file in the vendor directory.
63        part_name = "product_rk3568"          # Set part_name to product_rk3568 for subsequent build.
64    }
65    ```
66
675. Add the build target to `module_list` in [ohos.build](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/ohos.build) in the `/vendor/hihope/rk3568` directory. For example:
68
69    ```json
70    {
71    "parts": {
72        "product_rk3568": {
73        "module_list": [
74            "//vendor/hihope/rk3568/default_app_config:default_app_config",
75            "//vendor/hihope/rk3568/image_conf:custom_image_conf",
76            "//vendor/hihope/rk3568/preinstall-config:preinstall-config",
77            "//vendor/hihope/rk3568/resourceschedule:resourceschedule",
78            "//vendor/hihope/rk3568/etc:product_etc_conf",
79            "//vendor/hihope/rk3568/battery/profile:battery_config" # Add the configuration for building of battery_config.
80        ]
81        }
82    },
83    "subsystem": "product_hihope"
84    }
85    ```
86    In the preceding code, `//vendor/hihope/rk3568/battery/` is the folder path, `profile` is the folder name, and `battery_config` is the build target.
87
886. Build the customized version by referring to [Quick Start](../quick-start/quickstart-overview.md).
89
90    ```shell
91    ./build.sh --product-name rk3568 --ccache
92    ```
93
947. Burn the customized version to the DAYU200 development board.
95
96### Debugging and Verification
97
981. Build the battery-specific hats test cases. For details about the build commands and framework setup, see [XTS Subsystem](https://gitee.com/openharmony/xts_hats).
99
1002. Run the test cases, and check the test report.
101
102    ![battery_limit_current_test_report](figures/battery_limit_current_test_report.jpg)
103
104## Reference
105
106During development, you can refer to the [default charging current and voltage configuration](https://gitee.com/openharmony/powermgr_battery_manager/blob/master/services/native/profile/battery_config.json), as shown below:
107
108```json
109{
110    "charger": {
111        "current_limit":{
112            "path": "/data/service/el0/battery/current_limit"
113        },
114        "voltage_limit":{
115            "path": "/data/service/el0/battery/voltage_limit"
116        }
117    }
118}
119```
120
121Packing path: `/system/etc/battery`
122