[DEFAULT] ; --------- Set logging level --------- ; ERROR: Only errors are logged ; WARNING: Errors and warnings are logged ; INFO: Errors, warnings, and info messages are logged ; DEBUG: Errors, warnings, info, and debug messages are logged LOGGING = INFO ; --------- Battery Current Limits --------- ; +++ Limits apply to each individual battery/BMS. +++ ; +++ If you have multiple batteries, you need a battery aggregator. +++ MAX_BATTERY_CHARGE_CURRENT = 50.0 MAX_BATTERY_DISCHARGE_CURRENT = 60.0 ; --------- Cell Voltages --------- ; Description: ; Minimum and maximum cell voltages used for: ; - Calculating the minimum and maximum battery voltage ; - Triggering the SoC reset when SoC calculation is enabled ; Example: ; 16 cells * 3.45 V/cell = 55.2 V max charge voltage ; 16 cells * 2.90 V/cell = 46.4 V min discharge voltage ; Minimum voltage (can be seen as cut-off voltage) MIN_CELL_VOLTAGE = 2.900 ; Maximum voltage (can be seen as absorption voltage) MAX_CELL_VOLTAGE = 3.450 ; Float voltage (can be seen as resting voltage) FLOAT_CELL_VOLTAGE = 3.375 ; --------- SoC Reset Voltage (must match BMS settings) --------- ; +++ This section is independent and unrelated to the "SoC calculation" section below. +++ ; This is used to reset the SoC to 100% periodically to correct SoC drift. ; Description: ; Some BMS systems may need to reset the SoC to 100% periodically due to SoC drift. ; For example, JKBMS resets its internal SoC value if it reaches the upper voltage level. ; Using this method, the charging voltage can be raised regularly to achieve that. ; (Other BMS systems like Daly need an active overwriting of the SoC parameter. This happens each time ; when the charging mode changes from Bulk/Absorption to Float and the cells are equalized. They do ; not need this feature here.) ; Specify the cell voltage at which the SoC should be reset to 100% by the BMS. ; - JKBMS: SoC is reset to 100% if one cell reaches the Over Voltage Protection (OVP) voltage. ; It is recommended to start with OVP voltage - 0.030 (see Example). ; - Increase (add) by 0.005 in steps if the system does not switch to float mode, even if ; the target voltage SOC_RESET_VOLTAGE * CELL_COUNT is reached. ; - Decrease (lower) by 0.005 in steps if the system hits the OVP too fast, before all ; cells could be balanced and the system goes into protection mode multiple times. ; Example: ; If OVP is 3.650, then start with 3.620 and increase/decrease by 0.005. ; Note: ; The value must be higher than the MAX_CELL_VOLTAGE. ; You also have to set CELL_VOLTAGES_WHILE_CHARGING accordingly if you set CCCM_CV_ENABLE to true, ; otherwise the charging current will be reduced to 0 before the target voltage is reached and the ; battery will never switch to float. SOC_RESET_VOLTAGE = 3.650 ; Specify after how many days the SoC reset voltage should be reached again. ; The timer is reset when the SoC reset voltage is reached. ; Leave empty if you don't want to use the SoC reset feature. ; Example: ; Value is set to 15 ; day 1: SoC reset reached once ; day 16: SoC reset reached twice ; day 31: SoC reset not reached since it's very cloudy ; day 34: SoC reset reached since the sun came out ; day 49: SoC reset reached again, since last time it took 3 days to reach SoC reset voltage SOC_RESET_AFTER_DAYS = ; --------- SoC Calculation --------- ; +++ This section is independent and unrelated to the "SoC reset voltage" section above. +++ ; This is used to calculate the SoC in the driver instead of using the SoC reported by the BMS. ; Description: ; Calculate the SoC in the driver. Do not use the SoC reported by the BMS. ; SOC_CALCULATION: ; True: Calculate SoC in the driver, do not use SoC reported from BMS. ; - The SoC is calculated by integrating the current reported. ; - The current reported can be corrected by the map ; (SOC_CALC_CURRENT_REPORTED_BY_BMS, SOC_CALC_CURRENT_MEASURED_BY_USER). ; - The SoC is set to 100% if the following conditions apply for at least SOC_RESET_TIME seconds: ; * Highest cell voltage is higher or equal to MAX_CELL_VOLTAGE. ; * Current is lower than SOC_RESET_CURRENT. ; - The SoC is set to 0% if the following conditions apply for at least SOC_RESET_TIME seconds: ; * Lowest cell voltage is lower or equal to MIN_CELL_VOLTAGE. ; * Battery is discharging. ; - The calculated SoC is stored in dbus to persist a driver restart. ; False: Use SoC reported from BMS (none of the other parameters apply). ; More info: https://github.com/Louisvdw/dbus-serialbattery/pull/868 SOC_CALCULATION = False SOC_RESET_CURRENT = 7 SOC_RESET_TIME = 60 SOC_CALC_CURRENT_REPORTED_BY_BMS = -300, 300 SOC_CALC_CURRENT_MEASURED_BY_USER = -300, 300 ; Example to set small currents to zero: ; SOC_CALC_CURRENT_REPORTED_BY_BMS = -300, -0.5, 0.5, 300 ; SOC_CALC_CURRENT_MEASURED_BY_USER = -300, 0, 0, 300 ; --------- Bluetooth BMS --------- ; +++ Bluetooth connections may be unstable on some systems. +++ ; +++ For a stable connection, use the serial connection. +++ ; Description: ; Specify the Bluetooth BMS and its MAC address that you want to use. Leave empty to disable. ; Available Bluetooth BMS: ; Jkbms_Ble, LltJbd_Ble ; Example for one BMS: ; BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00 ; Example for multiple BMS: ; BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00, Jkbms_Ble C8:47:8C:00:00:11, Jkbms_Ble C8:47:8C:00:00:22 BLUETOOTH_BMS = ; --------- Bluetooth use USB --------- ; Description: ; Some users reported issues with the built-in Bluetooth module. You can try to fix it with a USB ; module. After changing this setting, run reinstall-local.sh and manually reboot the device. ; The USB Bluetooth module must support BLE (Bluetooth version >= 4.0). ; Other Bluetooth devices such as Ruuvi tags have not been tested yet. ; False: Use the built-in Bluetooth module ; True: Disable the built-in Bluetooth module and use a USB module BLUETOOTH_USE_USB = False ; --------- CAN BMS --------- ; Description: ; Specify the CAN port(s) where the BMS is connected. Leave empty to disable. ; Show available CAN ports with: canshow ; Available CAN BMS: ; Daly_Can, Jkbms_Can ; Example for one CAN port (Cerbo GX MK2, Ekrano GX): ; CAN_PORT = vecan0, vecan1 ; Example for one CAN port (Cerbo GX, Raspberry Pi): ; CAN_PORT = can0 ; Example for multiple CAN ports: ; CAN_PORT = can0, can8, can9 CAN_PORT = ; --------- Modbus (multiple BMS on one serial adapter) --------- ; Description: ; Specify the Modbus addresses as hexadecimal numbers for which a dbus-serialbattery instance should be started. ; If left empty, the driver will connect only to the default address specified in the driver. ; Example: ; MODBUS_ADDRESSES = 0x30, 0x31, 0x32, 0x33 MODBUS_ADDRESSES = ; --------- BMS Disconnect Behavior --------- ; Description: ; Block charge and discharge when communication with the BMS is lost. If you are removing the ; BMS intentionally, you must restart the driver/system to reset the block. ; False: ; Charge and discharge are not blocked for 20 minutes if cell voltages are between ; BLOCK_ON_DISCONNECT_VOLTAGE_MIN and BLOCK_ON_DISCONNECT_VOLTAGE_MAX. Otherwise, the driver blocks charge and discharge ; after 60 seconds. ; True: ; Charge and discharge are blocked immediately on BMS communication loss. They are unblocked when the connection is re-established ; or the driver/system is restarted. This is the default behavior for Victron Energy devices. BLOCK_ON_DISCONNECT = False ; Specify in minutes how long the driver should continue to charge and discharge after BMS communication is lost. BLOCK_ON_DISCONNECT_TIMEOUT_MINUTES = 20 ; Specify a voltage range where the last fetched values of the driver should be to avoid blocking charging and discharging. ; This is needed since during this time the driver has no information about the battery status. ; The range should be safe for the battery to operate without information for 20 minutes. BLOCK_ON_DISCONNECT_VOLTAGE_MIN = 3.25 BLOCK_ON_DISCONNECT_VOLTAGE_MAX = 3.35 ; --------- Charge Mode --------- ; Choose the mode for voltage/current limitations (True/False). ; False: Step mode (default) with limitations on hard boundary steps. ; True: Linear mode with smoother values. ; For CCL and DCL, values between steps are calculated for smoother transitions. ; For CVL, the max battery voltage is calculated dynamically to ensure the max cell voltage is not exceeded. LINEAR_LIMITATION_ENABLE = True ; Specify in seconds how often the linear values should be recalculated. LINEAR_RECALCULATION_EVERY = 60 ; Specify the percentage change that triggers an immediate recalculation of linear values. ; Example: ; 33 means an immediate change when the value changes by more than 33%. LINEAR_RECALCULATION_ON_PERC_CHANGE = 33 ; --------- External Current Sensor --------- ; Specify the dbus device and path where the external current sensor is connected. ; You can find this information by executing the dbus-spy command. ; Example for a SmartShunt as external current sensor: ; EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = com.victronenergy.battery.ttyS2 ; EXTERNAL_CURRENT_SENSOR_DBUS_PATH = /Dc/0/Current EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = EXTERNAL_CURRENT_SENSOR_DBUS_PATH = ; --------- Charge Voltage Limitation (affecting CVL) --------- ; Description: ; Limit the maximum charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float ; voltage (FLOAT_CELL_VOLTAGE * cell count) and back. ; False: Max charging voltage is always maintained. ; True: Max charging voltage is reduced based on charge mode. ; Step mode: After max voltage is reached for MAX_VOLTAGE_TIME_SEC, it switches to float voltage. After ; SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT, it switches back to max voltage. ; Linear mode: After max voltage is reached and cell voltage difference is smaller or equal to ; CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL, it switches to float voltage after MAX_VOLTAGE_TIME_SEC ; additional seconds. ; After cell voltage difference is greater or equal to CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT ; OR ; SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT, ; it switches back to max voltage. ; Example when set to True: ; Step mode: ; The battery reaches a max voltage of 55.2 V and holds it for 900 seconds, then the CVL switches to ; float voltage of 53.6 V to reduce stress on the batteries. Max voltage of 55.2 V is allowed again if SoC ; drops below 80%. ; Linear mode: ; The battery reaches a max voltage of 55.2 V and the max cell difference is 0.010 V, then switch to float ; voltage of 53.6 V after 900 additional seconds to reduce stress on the batteries. Max voltage of ; 55.2 V is allowed again if the max cell difference exceeds 0.080 V or SoC drops below 80%. ; Enable charge voltage control management (True/False). CVCM_ENABLE = True ; -- CVL reset based on cell voltage difference (linear mode) ; Specify the cell voltage difference where CVL limit is maintained until the difference is equal or lower. CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL = 0.010 ; Specify the cell voltage difference where MAX_VOLTAGE_TIME_SEC restarts if the difference is larger. CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_TIME_RESTART = 0.013 ; Specify the cell voltage difference where CVL limit is reset to max voltage if the value exceeds this threshold. ; Cells are considered imbalanced if the cell difference exceeds 5% of the nominal cell voltage. ; Example: 3.2 V * 5 / 100 = 0.160 V CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT = 0.080 ; -- CVL reset based on SoC (step mode & linear mode) ; Specify how long the max voltage should be maintained. ; Step mode: If reached, then switch to float voltage. ; Linear mode: If cells are balanced, maintain max voltage for an additional MAX_VOLTAGE_TIME_SEC seconds. MAX_VOLTAGE_TIME_SEC = 900 ; Specify the SoC level where CVL limit is reset to max voltage. ; Step mode: If SoC drops below this level. ; Linear mode: If cells are unbalanced or if SoC drops below this level. SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 80 ; --------- Cell Voltage Limitation (affecting CVL) --------- ; This function prevents overcharging of the highest voltage cell in a poorly balanced battery, which could cause the BMS to ; switch off due to overvoltage. ; ; Example: ; 15 cells are at 3.4 V, 1 cell is at 3.6 V. The total battery voltage is 54.6 V, and the Victron System sees no reason to ; lower the charging current as the control voltage (Absorption Voltage) is 55.2 V. ; In this case, the Cell Voltage Limitation kicks in and lowers the control voltage to keep it close to the MAX_CELL_VOLTAGE. ; ; In theory, this can also be done with CCL, but doing it with CVL has 2 advantages: ; - In a well-balanced system, the current can be kept quite high until the end of charge by using MAX_CELL_VOLTAGE for charging. ; - In systems with MPPTs and DC-feed-in activated, the Victron systems do not respect CCL, so CVL is the only way to prevent the ; highest cell in a poorly balanced system from overcharging. ; ; There are 2 methods implemented to calculate CVL: ; 1. Penalty Sum Method (CVL_ICONTROLLER_MODE = False) ; The voltage overshoot of all cells that exceed MAX_CELL_VOLTAGE is summed up, and the control voltage is lowered by this "penalty sum". ; This is calculated every LINEAR_RECALCULATION_EVERY seconds. ; In effect, this is a P-Controller. ; 2. I-Controller (CVL_ICONTROLLER_MODE = True) ; An I-Controller tries to control the voltage of the highest cell to MAX_CELL_VOLTAGE + CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL. ; (for example, 3.45 V + 0.01 V = 3.46 V). If the voltage of the highest cell is above this level, CVL is reduced. If the voltage is below, CVL is ; increased until cell count * MAX_CELL_VOLTAGE. ; An I-Part of 0.2 V/Vs (CVL_ICONTROLLER_FACTOR) has proven to provide stable and fast control behavior. ; This method is not as fast as the Penalty Sum Method but is usually smoother and more stable against toggling and has no stationary deviation. ; More info: https://github.com/Louisvdw/dbus-serialbattery/pull/882 CVL_ICONTROLLER_MODE = False CVL_ICONTROLLER_FACTOR = 0.2 ; --------- Cell Voltage Current Limitation (affecting CCL/DCL) --------- ; Description: ; The maximum charge/discharge current will be increased or decreased depending on the minimum and maximum cell voltages. ; Example: ; 18 cells * 3.55 V/cell = 63.9 V max charge voltage ; 18 cells * 2.70 V/cell = 48.6 V min discharge voltage ; In reality, not all cells reach the same voltage at the same time. The (dis)charge current ; will be (in-/)decreased if even one single battery cell reaches the limits. ; Enable charge current control management based on cell voltage (True/False). CCCM_CV_ENABLE = True ; Enable discharge current control management based on cell voltage (True/False). DCCM_CV_ENABLE = True ; Set steps to reduce battery current. ; The current will be changed linearly between these steps if LINEAR_LIMITATION_ENABLE is set to True. CELL_VOLTAGES_WHILE_CHARGING = 3.55, 3.50, 3.45, 3.30 MAX_CHARGE_CURRENT_CV_FRACTION = 0, 0.05, 0.5, 1 CELL_VOLTAGES_WHILE_DISCHARGING = 2.70, 2.80, 2.90, 3.10 MAX_DISCHARGE_CURRENT_CV_FRACTION = 0, 0.1, 0.5, 1 ; --------- Temperature Limitation (affecting CCL/DCL) --------- ; Description: ; The maximum charge/discharge current will be increased or decreased depending on temperatures. ; NOTE: The temperatures are in °Celsius. Temperature sensors 1 to 4 are used for the calculation. ; Example: ; The temperature limit will be monitored to control the currents. If there are two temperature sensors, ; the worst case will be calculated, and the more secure lower current will be set. ; Enable charge current control management based on temperature (True/False). CCCM_T_ENABLE = True ; Enable discharge current control management based on temperature (True/False). DCCM_T_ENABLE = True ; Set steps to reduce battery current. ; The current will be changed linearly between these steps if LINEAR_LIMITATION_ENABLE is set to True. TEMPERATURES_WHILE_CHARGING = 0, 2, 5, 10, 15, 20, 35, 40, 55 MAX_CHARGE_CURRENT_T_FRACTION = 0.00, 0.10, 0.20, 0.40, 0.80, 1.00, 1.00, 0.40, 0.00 TEMPERATURES_WHILE_DISCHARGING = -20, 0, 5, 10, 15, 45, 55 MAX_DISCHARGE_CURRENT_T_FRACTION = 0.00, 0.20, 0.30, 0.40, 1.00, 1.00, 0.00 ; --------- SoC Limitation (affecting CCL/DCL) --------- ; Description: ; The maximum charge/discharge current will be increased or decreased depending on the State of Charge (SoC). ; Since the SoC is not as accurate as the cell voltage, this option is disabled by default. ; Example: ; The SoC limit will be monitored to control the currents. ; Enable charge current control management based on SoC (True/False). CCCM_SOC_ENABLE = False ; Enable discharge current control management based on SoC (True/False). DCCM_SOC_ENABLE = False ; Set steps to reduce battery current. ; The current will be changed linearly between these steps if LINEAR_LIMITATION_ENABLE is set to True. SOC_WHILE_CHARGING = 98, 95, 90, 85 MAX_CHARGE_CURRENT_SOC_FRACTION = 0.10, 0.20, 0.50, 1.00 SOC_WHILE_DISCHARGING = 5, 10, 15, 20 MAX_DISCHARGE_CURRENT_SOC_FRACTION = 0.10, 0.20, 0.50, 1.00 ; --------- CCL/DCL Recovery Threshold --------- ; Description: ; This threshold applies if any of the following limitations are enabled: ; - Cell Voltage Current Limitation (CCCM_CV_ENABLE, DCCM_CV_ENABLE) ; - Temperature Limitation (CCCM_T_ENABLE, DCCM_T_ENABLE) ; - SoC Limitation (CCCM_SOC_ENABLE, DCCM_SOC_ENABLE) ; Once the current reaches 0, it will only increase again if it exceeds this threshold. ; The threshold is a percentage of the maximum charge/discharge current. ; This prevents rapid switching (flapping) between allowing and blocking charge/discharge, which can cause system instability and excessive notifications. ; Example: ; If the maximum charge current is 50 A and the threshold is set to 0.02 (2%), the current must exceed 1A (50A * 0.02) before charging resumes. ; If the maximum discharge current is 60 A and the threshold is set to 0.02 (2%), the current must exceed 1.2A (60A * 0.02) before discharging resumes. CHARGE_CURRENT_RECOVERY_THRESHOLD_PERCENT = 0.015 DISCHARGE_CURRENT_RECOVERY_THRESHOLD_PERCENT = 0.015 ; --------- Time-To-Go --------- ; Description: ; Calculates the time remaining until the battery reaches a specific SoC, shown in the GUI. ; If ESS is enabled and an "Optimized..." option is selected, it uses the SoC limit of the ESS system. ; Otherwise, it uses SOC_LOW_WARNING from the config file. ; Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY. TIME_TO_GO_ENABLE = True ; --------- Time-To-Soc --------- ; Description: ; Calculates the time remaining until the battery reaches specific SoC levels. ; Example: ; TIME_TO_SOC_POINTS = 50, 25, 15, 0 ; 6h 24m remaining until 50% SoC ; 17h 36m remaining until 25% SoC ; 22h 5m remaining until 15% SoC ; 28h 48m remaining until 0% SoC ; Set of SoC percentages to report on dbus and MQTT. The more you specify, the more it will impact system performance. ; [Valid values 0-100, comma-separated list. More than 20 intervals are not recommended] ; Example: TIME_TO_SOC_POINTS = 100, 95, 90, 85, 75, 50, 25, 20, 10, 0 ; Leave empty to disable. TIME_TO_SOC_POINTS = ; Specify TimeToSoc value type [Valid values 1, 2, 3] ; 1 Seconds ; 2 Time string d h m s ; 3 Both seconds and time string " [d h m s]" TIME_TO_SOC_VALUE_TYPE = 1 ; Specify in seconds how often the TimeToSoc should be recalculated. ; Minimum is 5 seconds to prevent CPU overload. TIME_TO_SOC_RECALCULATE_EVERY = 60 ; Include TimeToSoC points when moving away from the SoC point [Valid values True, False] ; These will be shown as negative time. Disabling this improves performance slightly. TIME_TO_SOC_INC_FROM = False ; --------- Additional settings --------- ; Specify one or more BMS types (separated by a comma) to load, or leave empty to try to load all available. ; ; Available serial BMS: ; Daly, Daren485, Ecs, EG4_Lifepower, EG4_LL, HeltecModbus, HLPdataBMS4S, Jkbms, Jkbms_pb, LltJbd, Renogy, Seplos, Seplosv3 ; Disabled by default (just enter one or more to enable): ; ANT, MNB, Sinowealth ; ; Available CAN BMS: ; Daly_Can, Jkbms_Can ; ; Available Bluetooth BMS: ; Jkbms_Ble, LltJbd_Ble BMS_TYPE = ; Exclude these serial devices from the driver startup. ; Example: ; /dev/ttyUSB2, /dev/ttyUSB4 EXCLUDED_DEVICES = ; BMS poll interval in seconds. ; If the driver consumes too much CPU, you can increase this value to reduce the refresh rate ; and CPU usage. ; Default for most BMS is 1 second; some BMS may have a higher value. ; Leave empty to use the BMS default value; decimal values are allowed. POLL_INTERVAL = ; Publish the config settings to the dbus path "/Info/Config/". PUBLISH_CONFIG_VALUES = False ; Select the format of cell data presented on dbus. ; 0 Do not publish all the cells (only the min/max cell data as used by the default GX) ; 1 Format: /Voltages/Cell (also available for display on Remote Console) ; 2 Format: /Cell/#/Volts ; 3 Both formats 1 and 2 BATTERY_CELL_DATA_FORMAT = 1 ; Simulate Midpoint graph (True/False). MIDPOINT_ENABLE = False ; Battery temperature ; Specify how the battery temperature is assembled. ; 0 Get mean of temperature sensor 1 to sensor 4 ; 1 Get only temperature from temperature sensor 1 ; 2 Get only temperature from temperature sensor 2 ; 3 Get only temperature from temperature sensor 3 ; 4 Get only temperature from temperature sensor 4 TEMP_BATTERY = 0 ; Temperature sensor 1 name TEMP_1_NAME = Temp 1 ; Temperature sensor 2 name TEMP_2_NAME = Temp 2 ; Temperature sensor 3 name TEMP_3_NAME = Temp 3 ; Temperature sensor 4 name TEMP_4_NAME = Temp 4 ; Show additional info in GUI -> Serialbattery -> Parameters. ; This will show additional information to better understand how the driver works ; and what values are currently set which are not shown elsewhere in the GUI. ; You have to scroll down to see the additional information. GUI_PARAMETERS_SHOW_ADDITIONAL_INFO = False ; Telemetry settings ; To help us improve the driver, we are collecting telemetry data. This data is anonymous and ; will only be used to improve the driver. The data is sent once every week. ; You can disable this feature by setting this value to False. ; Some data we collect: Venus OS version, driver version, driver runtime, battery type, battery count. TELEMETRY = True ; --------- Voltage drop --------- ; If there is a voltage drop between the BMS and the charger due to wire size or length, ; you can specify the voltage drop here. The driver will then add the voltage drop ; to the calculated CVL to compensate. ; Example: ; Cell count: 16 ; MAX_CELL_VOLTAGE = 3.45 ; Max voltage calculated = 16 * 3.45 = 55.20 V ; CVL is set to 55.20 V, and the battery is charged until the charger reaches 55.20 V. ; The BMS measures 55.05 V due to a voltage drop of 0.15 V on the cable. ; Since the dbus-serialbattery reads 55.05 V from the BMS, the max voltage of 55.20 V is never reached, ; and max voltage is maintained indefinitely. ; By setting the VOLTAGE_DROP to 0.15 V, the voltage on the charger is increased, and the ; target voltage on the BMS is reached. VOLTAGE_DROP = 0.00 ; --------- BMS specific settings --------- ; Auto reset BMS SoC. ; If enabled, the BMS SoC is reset to 100% when the value switches from absorption to float voltage. ; Currently only works for Daly BMS and JKBMS BLE. AUTO_RESET_SOC = True ; -- Unique ID settings ; Some BMS units do not have a unique ID and cannot be assigned one. In this case, ; you can use the USB port as the unique ID. ; Note: VRM IDs and custom names may not be saved/restored correctly when using this option. USE_PORT_AS_UNIQUE_ID = False ; -- LltJbd settings ; SoC low levels ; Note: ; SOC_LOW_WARNING can be used to calculate the Time-To-Go, even if you are not using an LltJbd BMS. SOC_LOW_WARNING = 20 SOC_LOW_ALARM = 10 ; -- Daly settings ; Battery capacity (in amp-hours), if the BMS does not support reading it. BATTERY_CAPACITY = 50 ; Invert Battery Current. Default is non-inverted. Set to -1 to invert. INVERT_CURRENT_MEASUREMENT = 1 ; -- JKBMS CAN settings ; Predefined cell count for Jkbms_can. ; The cell count should be auto-detected by identifying the highest cell number, ; but this process may be slow, causing cell voltage updates to be delayed in VenusOS. ; Use this workaround if you experience problems with cell voltage updates. JKBMS_CAN_CELL_COUNT = 1 ; -- ESC GreenMeter and Lipro device settings GREENMETER_ADDRESS = 1 LIPRO_START_ADDRESS = 2 LIPRO_END_ADDRESS = 4 LIPRO_CELL_COUNT = 15 ; -- Seplos V3 settings ; Use min/max cell voltage, CVL, CCL, and DCL values from the BMS. SEPLOS_USE_BMS_VALUES = False