Differences

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

--- ess:ess_mode_2_and_3 [2020-07-08 15:48] – [2.1 Available control points] iburger
+++ ess:ess_mode_2_and_3 [2021-03-20 03:19] – guystewart
@@ Line 9: / Line 9: @@
 ==== 1.1 - Mode 1 ====
-The system runs automatically, and uses excess energy harvested during the day to fill the gaps when there is not enough PV power available. Typically in the evening and night. Easy configuration in Assistants and on the Color Control GX. For details refer to the [[ess:design-installation-manual|ESS manual]].
+The system runs automatically, and uses excess energy harvested during the day to fill the gaps when there is not enough PV power available. Typically in the evening and night. Easy configuration in Assistants and on the GX device. For details refer to the [[ess:design-installation-manual|ESS manual]].
 ==== 1.2 - Mode 2 ====
@@ Line 96: / Line 96: @@
 MQTT is available both on the local broker on the [[venus-os:start|GX device]], as well as remotely through the secure cloud connection.
-=== C) Running your own scripts on the CCGX ===
+=== C) Running your own scripts on the GX device ===
 Start reading [[open_source:start|here]].
@@ Line 103: / Line 103: @@
   * com.victronenergy.settings /Settings/CGwacs/MaxChargePercentage    (Enable/Disable charger)
   * com.victronenergy.settings /Settings/CGwacs/MaxDischargePercentage (Enable/Disable inverter)
+  * 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/OvervoltageFeedIn      (Feed-in excess DC-coupled PV)
+  * com.victronenergy.settings /Settings/CGwacs/PreventFeedback        (Don't feed in excess AC-coupled PV)
+  * com.victronenergy.hub4 /PvPowerLimiterActive                       (Read-only value indicating if limiting is active)
-Note that the paths are represented as percentage, but should be used as on/off switch (0: off,
+Note that the MaxChargePercentage and MaxDischargePercentage paths are represented as percentage, but should be used as on/off switch (0: off,
 : on).
@@ Line 144: / Line 150: @@
   * When both Charge and Feed-in is disabled, the Multi will go into Passthru.
-==== 3.3 Running software on the CCGX and using DBus paths ====
+=== d) Disable overvoltage Feed-in - Modbus-TCP register 65 ===
+Overvoltage feed-in can be used to feed excess DC-tied PV into the grid. Note that DVCC needs to be enabled to properly use this feature.
+  * 0: Feed overvoltage into the grid.
+  * 1: Do not Feed overvoltage into the grid.
-When controlling the Multi using software running on the CCGX, you should set //Settings->ESS->Mode// to //external control//. The following dbus paths can then be adjusted on the com.victronenergy.vebus.ttyO1 service.
+=== e) Maximum Feed-in power due to overvoltage - Modbus-TCP register 66 to 68 ===
+When overvoltage feed-in is enabled, these registers can be used to limit how much power is fed in. To disable the limit, write a large number to the register.
+  * Register 66: Overvoltage feed-in limit for L1
+  * Register 67: Overvoltage feed-in limit for L2
+  * Register 68: Overvoltage feed-in limit for L3
+==== 3.3 Running software on the GX device and using DBus paths ====
+When controlling the Multi using software running on the GX device, you should set //Settings->ESS->Mode// to //external control//. The following dbus paths can then be adjusted on the com.victronenergy.vebus.ttyO1 service.
 === a) Grid Power Setpoints - /Hub4/Lx/AcPowerSetpoint ===
@@ Line 171: / Line 188: @@
     * When set to -400W, it will feed 400W back through its input. This energy will be taken from the battery. If there is also a 200W AC load connected to AC output the total energy taken from the battery will be 600W. The batteries will always be discharged when the setpoint is negative.
     * When set to 400W, it will take 400W from the AC input. When the load on the output is lower than 400W, it will charge the battery with the difference. When the load on the AC output is higher, it will discharge the battery with the difference. So with a positive setpoint charge/discharge depends also on the connected loads.
-    * **Important note**: The above examples describe operation from the point of view of the CCGX. When communicating directly with the ESS assistant (see further on) you should bear in mind that the CCGX inverts the setpoint: Positive becomes negative and vice versa.
+    * **Important note**: The above examples describe operation from the point of view of the GX device. When communicating directly with the ESS assistant (see further on) you should bear in mind that the GX device inverts the setpoint: Positive becomes negative and vice versa.
   * Note that it will always remain within battery and maximum inverter power limits: when the battery is full or when the maximum charge current as configured in VEConfigure is already met, it will not draw more power, and when instructed to discharge with 10000 watt while it only has a 2500W inverter capacity, it will discharge with 2500W until the battery is empty.
   * To force the Multi to Inverter Mode, set the switch to Inverter-only. Note that when you do that, there will be no grid assist. On an overload the Inverter will switch off and signal an overload alarm instead of switching back to the grid.
@@ Line 184: / Line 201: @@
   * Note that there are various ramp-up and ramp-down restrictions, enforced by grid-codes and compliancy as well as for stability reasons; which might make the system respond slow to large load commands.
   * The 'VE.Bus to VE.Can interface' does not support reading and writing the ESS/grid-parallel setpoint.
-  * If your system contains a ESS compatible AC-Sensor which is set up as grid meter, the CCGX will automatically enter mode 1 and start updating the AC power setpoint continuously. You can disable this behavior by setting //Settings->ESS->Mode// to //external control//. This will also disable [[ess:design-installation-manual#batterylife|BatteryLife]]. To do this via D-Bus or MQTT: set the value of /Settings/CGwacs/Hub4Mode in the com.victronenergy.settings service to 3 (=ESS control disabled).
+  * If your system contains a ESS compatible AC-Sensor which is set up as grid meter, the GX device will automatically enter mode 1 and start updating the AC power setpoint continuously. You can disable this behavior by setting //Settings->ESS->Mode// to //external control//. This will also disable [[ess:design-installation-manual#batterylife|BatteryLife]]. To do this via D-Bus or MQTT: set the value of /Settings/CGwacs/Hub4Mode in the com.victronenergy.settings service to 3 (=ESS control disabled).
-==== 3.6 Using the MK3 directly instead of via CCGX ====
+==== 3.6 Using the MK3 directly instead of via GX device ====
 === 3.6.1 Introduction ===
-In this setup, it is not necessary to use a CCGX for the control interface. Instead an MK3 is used. We have both MK2-RS232 and an MK3-USB available, see the pricelist.
+In this setup, it is not necessary to use a GX device for the control interface. Instead an MK3 is used. We have both MK2-RS232 and an MK3-USB available, see the pricelist.
 The MK3-USB has replaced the MK2-USB. There are no differences in the protocol.
-A direct connection to the VE.Bus RS485, without MK3 or CCGX, is not possible.
+A direct connection to the VE.Bus RS485, without MK3 or GX device, is not possible.
 Note that, as also indicated on the Data Communication whitepaper, the MK2/3 protocol is not an easy protocol. That is unfortunate, but it is what it is. We cannot give support on it unless there is a huge commercial value behind the project, read thousands of Multis or Quattros.
@@ Line 284: / Line 301: @@
     * when you do not want to discharge, set the switch to charger-only. Note that when the switch is set to charger-only, and there is no grid available, there will still be a small power draw on the battery to power the control board.
     * when you do not want to charge, disable charging via the disable-charge flag.
-  * As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the CCGX itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the CCGX, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, and path /Hub4/AcPowerSetpoint
+  * As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the GX device itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the GX device, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, and path /Hub4/AcPowerSetpoint
 ===== 5. Response times and ramp speed =====