ess:ess_mode_2_and_3
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
ess:ess_mode_2_and_3 [2021-06-28 12:27] – [3.2 Using ModbusTCP] iburger | ess:ess_mode_2_and_3 [2023-02-14 15:11] – [2.1 Available control points] iburger | ||
---|---|---|---|
Line 53: | Line 53: | ||
* 100: unlimited charging. Battery, VEConfigure settings, and BMS permitting. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | * 100: unlimited charging. Battery, VEConfigure settings, and BMS permitting. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | ||
- | Note that this setting has a higher priority than the //Grid power setpoint//. | + | Notes: |
+ | * This setting is deprecated and only works when DVCC is disabled. It is retained for backwards compatibility only. Use register 2705 instead to control battery charging. | ||
+ | * This setting has a higher priority than the //Grid power setpoint//. | ||
=== c) Enable/ | === c) Enable/ | ||
Line 59: | Line 61: | ||
* 100: enabled inverter. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | * 100: enabled inverter. Use value 100 here instead of 1 because this setting was originally designed to be used as a percentage. | ||
- | Note that this settings has a higher priority than the //Grid power setpoint//. | + | Notes: |
+ | * This setting is deprecated and only works when DVCC is disabled. It is retained for backwards compatibility only. Use register 2704 instead to control battery discharge. | ||
+ | * This settings has a higher priority than the //Grid power setpoint//. | ||
=== d) Maximum inverter power - Modbus-TCP register 2704 === | === d) Maximum inverter power - Modbus-TCP register 2704 === | ||
Line 66: | Line 70: | ||
=== e) DVCC maximum system charge current - Modbus-TCP register 2705 === | === e) DVCC maximum system charge current - Modbus-TCP register 2705 === | ||
- | * -1: No limit. Solar Chargers and the Multi will charge to their full capacity or individual | + | * -1: No limit. Solar Chargers and the Multi will charge to their full capacity or individual |
* Any positive number: Maximum combined current in Ampere for battery charging. This limits the solar chargers and the multi, and takes loads into account. Solar chargers take priority over the Multi. | * Any positive number: Maximum combined current in Ampere for battery charging. This limits the solar chargers and the multi, and takes loads into account. Solar chargers take priority over the Multi. | ||
Line 105: | Line 109: | ||
* com.victronenergy.settings / | * com.victronenergy.settings / | ||
* com.victronenergy.settings / | * com.victronenergy.settings / | ||
- | * com.victronenergy.settings / | + | * com.victronenergy.settings / |
* com.victronenergy.settings / | * com.victronenergy.settings / | ||
* com.victronenergy.settings / | * com.victronenergy.settings / | ||
Line 273: | Line 277: | ||
(Length, 0xFF, ‘W’, 0x85, Lo(ValueA), Hi(ValueA), Lo(ValueB)*, | (Length, 0xFF, ‘W’, 0x85, Lo(ValueA), Hi(ValueA), Lo(ValueB)*, | ||
- | ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates | + | ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates |
//*) Please note that you will get an extra ValueB. This is a feature of newer Multi firmware versions. Because the IDs range from 0..255 the Hi(ID) field would always be 0. | //*) Please note that you will get an extra ValueB. This is a feature of newer Multi firmware versions. Because the IDs range from 0..255 the Hi(ID) field would always be 0. | ||
Line 375: | Line 379: | ||
* Set register 37 to -1000 | * Set register 37 to -1000 | ||
- | ===== DISQUS ===== | + | |
- | ~~DISQUS~~ | + | |
ess/ess_mode_2_and_3.txt · Last modified: 2023-02-14 15:25 by mvader