Differences

This shows you the differences between two versions of the page.

--- ess:ess_mode_2_and_3 [2021-03-20 03:19] – guystewart
+++ ess:ess_mode_2_and_3 [2024-10-14 15:20] (current) – [2.1 Available control points] iburger
@@ Line 42: / Line 42: @@
 ==== 2.1 Available control points ====
-=== a) Grid power setpoint - Modbus-TCP register 2700 ===
+Please note that the power setpoint register changed in Venus 3.50. Prior to Venus 3.50, the power setpoint would be written to register 2700 or 2703 instead. While this is still supported, it is recommended that future implementations use the 32-bit setting at registers 2716 and 2717 to avoid constantly logging the new setpoint to VRM, and wearing the flash on the GX-device with repeated writes.
+=== a) Grid power setpoint - Modbus-TCP register 2716  ===
+For venus versions before 3.50, use register 2700 instead.
   * Positive: take power from grid.
   * Negative: send power to grid.
-  * Default: 30 W.
+  * Default: 50 W.
-  * This register has range -32768W to 32767W (scale factor=1). Use register 2703 for a larger range (scale factor=0.01).
+  * Note that register 2700 has range of -32768W to 32767W (scale factor=1). On venus versions before v3.50, use register 2703 for a larger range (scale factor=0.01). On Venus 3.50 and later, use register 2716-2717, which is a 32-bit value.
-=== b) Enable/Disable charge - Modbus-TCP register 2701 ===
+=== b) Enable/Disable charge - Modbus-TCP register 2701 (deprecated in favour of 2705) ===
   * 0: disable charging. This setting may be used for time shifting. For example by disabling charging the battery when feeding back to the grid is profitable, and leaving battery capacity for later.
   * 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/Disable inverter - Modbus-TCP register 2702 ===
+=== c) Enable/Disable inverter - Modbus-TCP register 2702 (deprecated in favour of 2704) ===
   * 0: disable inverter
   * 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 ===
@@ Line 66: / Line 74: @@
 === 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 configurd limits.
+  * -1: No limit. Solar Chargers and the Multi will charge to their full capacity or individual configured limits.
   * 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 113: @@
   * com.victronenergy.settings /Settings/CGwacs/MaxDischargePower      (Maximum inverter power)
   * com.victronenergy.settings /Settings/SystemSetup/MaxChargeCurrent  (DVCC maximum charge current)
-  * com.victronenergy.settings /Settings/CGwacs/MaxFeedInPower         (Maximum system grid feed-in)
+  * com.victronenergy.settings /Settings/CGwacs/MaxFeedInPower         (Maximum system grid feed-in of excess power)
   * com.victronenergy.settings /Settings/CGwacs/OvervoltageFeedIn      (Feed-in excess DC-coupled PV)
   * com.victronenergy.settings /Settings/CGwacs/PreventFeedback        (Don't feed in excess AC-coupled PV)
@@ Line 161: / Line 169: @@
   * Register 68: Overvoltage feed-in limit for L3
+=== f) Power Setpoints acts as limit - Modbus-TCP register 71 ===
+When this register is set to 1, the Multi will feed in overvoltage up to the value in registers 37, 40 and 41. This is useful when powering loads with excess DC-coupled PV, while still keeping the batteries fully charged. The Power setpoints are then set to match the loads as normal, but the Multi will feed in only excess PV and not energy from the batteries.
+=== g) Overvoltage offset - Modbus-TCP register 72 ===
+When feeding excess DC-coupled PV to loads or into the grid, the Multi has two possible settings. It can either add a 1V offset to the solar charger charge voltage, or a 100mV offset. These values are for a 12V setup, and must be multiplied by 2 or 4 for a 24V or 48V setup respectively.
+The larger 1V setting is a legacy setting and is now discouraged. When using ESS mode 3 with the overvoltage feed-in feature, it is recommended that you set this register to 1, which will use the lower 100mV offset.
 ==== 3.3 Running software on the GX device and using DBus paths ====
@@ Line 266: / Line 281: @@
 (Length, 0xFF, ‘W’, 0x85, Lo(ValueA), Hi(ValueA), Lo(ValueB)*, Hi(ValueB)*, Checksum)
-ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates ESS with 2 extra RAMIDs.
+ValueA is the contents of RAMID 128. In this example it is 0x0032 which indicates AssistantID = 3 with 2 extra RAMIDs. (3 is the ID of HUB-4 which is the predecessor of the ESS assistant)
 //*) 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 368: / Line 383: @@
   * Set register 37 to -1000
-===== DISQUS =====
-~~DISQUS~~