Differences

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

--- system_integration:hub4_grid_parallel_external_control_loop [2016-08-25 16:47] – [Hub-4 mode 2 and 3] mvader
+++ system_integration:hub4_grid_parallel_external_control_loop [2019-01-22 10:16] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 Note that it is also possible to run a Victron grid parallel storage system without designing and implementing your own control loop, logic or measurements. See the  [[system_integration:hub4_grid_parallel|Hub-4 manual]].
-For firmware version requirements, refer to the [[system_integration:hub4_grid_parallel|main hub-4 manual]].
+Note that though this page mentions Hub-4, which is deprecated, it also applies to ESS.
-In case you want to install custom software on the CCGX, as opposed to adding an additional PLC or other device at the side, start reading [[open_source:start|here]]
-Three/split-phase systems possible too.
-{{ :system_integration:hub4-modes2and3.png?nolink&600 |}}
 ===== 1. Overview of Hub-4 operating modes =====
 ==== 1.1 Mode 1 - Standard ====
-Standard \\ 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.
+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 [[system_integration:hub4_grid_parallel|main hub-4 manual]].
-Necessary Victron equipment:
-  - Multi or Quattro inverter/charger
-  - Color Control GX
-  - AC sensor used for control loop
-For details refer to the [[system_integration:hub4_grid_parallel|main hub-4 manual]].
 ==== 1.2 Mode 2 - Advanced ====
-Same as standard operating mode, but more flexibility is given to implement time shifting, load management or other energy management optimization algorithms.
+Same as standard operating mode, but customer adds custom control doing time shifting, load management or other energy management optimization algorithms. The required components in the system, as well as the general software setup, is 100% equal to the default, Mode 1. The available control points are:
-In standard mode the Hub-4 control system tries to keep the power flowing through the grid meter at 0 Watt (so no power is taken in from the grid, nor is any power fed back to the grid). Mode 2 means you set the target for the grid power. Setting the target to 100 Watt means that the system tries to take 100 Watt from the grid. The power will be used to feed the loads or charge the battery. Similar, a negative value will instruct the system to feed back power to the grid. This will be PV power when possible, otherwise the battery will be discharged. Reset the setpoint back to 0 Watt, and you are back in standard mode again.
-In addition you can also control battery charge and discharge. This allows you to control when the battery is charged and discharged.
-There are two ways to do this:
-  - Send commands to the CCGX via ModbusTCP: see [[ccgx:modbustcp_faq|here]] for more information about ModbusTCP on the CCGX.
-  - Run self-implemented code on the Color Control GX: complete flexibility and benefit from the VRM Portal and all other functionality already available on the CCGX, without having to add additional cost of extra PLCs or other control modules.
-Necessary Victron equipment:
-    - Same as mode 1, Standard.
-Available control points:
   * Grid power setpoint
   * Maximum charge percentage
   * Maximum discharge percentage
+There are two ways access those control points:
+  - Send commands to the CCGX via ModbusTCP, from an external control module, a PLC for example.
+  - Run self-implemented scripts on the CCGX, same functionality, but then it is not needed to add a PLC to the system.
+For more information, see [[#details_of_operating_mode_2_-_advanced|the Mode 2 details]].
 ==== 1.3 Mode 3 - Custom ====
 Customer self implements their control loop and grid measurements, and uses the MultiPlus and/or Quattros as simple, remote controllable, bidirectional inverter/chargers that can be set to either charge or discharge an x amount of Watts. Note that the point of control is the AC-input, not the charger itself.
@@ Line 58: / Line 39: @@
   * Disable charge flag
   * Disable feedback flag
+For more information, see [[#details_of_operating_mode_3_-_custom|the Mode 3 details]].
 ===== 2. Details of operating mode 2 - Advanced =====
-==== 2.1 Operation ====
+==== 2.1 Available control points ====
-  * Grid power setpoint. A positive value: power is taken from grid. Negative value: power fed back to grid. Note that the maximum charge and discharge percentages documented below have priority over the grid power setpoint.
-    * D-Bus: com.victronenergy.hub4 /AcPowerSetpoint
+=== a) Grid power setpoint - Modbus-TCP register 2700 ===
-    * Modbus: Register 2700, unit ID 0
+  * Positive: take power from grid.
-  * Maximum charge percentage. Limits the power taken in by the Multi through AC-In.
+  * Negative: send power to grid.
-    * 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.
+  * Default: 0W.
-    * 100%: no charge power not limited by CCGX (max charge current on multi still applies).
-    * >0% and <100%: The maximum allowed AC-In power is\\ ''max charge percentage * max charge current * battery voltage / 100''\\ The maximum charge current is taken from the settings on the Multi (which can be changed using VE configure). \\ Because this setting limits the power taken in on the Ac-In of the multi, it may give unexpected results when the AC-Out of the multi is also in use (for example to connect critical loads).
+=== b) Max charge current (fractional) - Modbus-TCP register 2701 ===
-    * D-Bus: com.victronenergy.hub4 /MaxChargePercentage
+Reduces the charge current relative to the maximum charge current. Note that this settings has a higher priority than the //Grid power setpoint//.
-    * Modbus: Register 2701, unit ID 0
-  * Maximum discharge percentage. Can be used to enabled or disable battery discharge. Value < 50 means that discharge is disabled. Otherwise discharge current is limited only by the battery and/or the Multi.
+  * 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.
-    * D-Bus: com.victronenergy.hub4 /MaxDischargePercentage
+  * 100%: unlimited charging. Battery, VEConfigure settings, and BMS permitting.
-    * Modbus: Register 2702, unit ID 0
+  * >0% and <100%: The maximum allowed AC-In power is\\ ''max charge percentage * max charge current * battery voltage / 100''\\ The maximum charge current is taken from the settings on the Multi (which can be changed using VE configure). \\ Because this setting limits the power taken in on the Ac-In of the multi, it may give unexpected results when the AC-Out of the Multi is also in use.
+=== c) Enable discharge - Modbus-TCP register 2702 ===
+Though presented as a percentage, it is really a on/off mechanism. Setting the percentage below 50% will disable discharge. And setting it equal to or above 50% will enable discharge.
+See the Modbus-TCP excel sheet for scaling and datatypes, available [[https://www.victronenergy.com/support-and-downloads/whitepapers|here]].
+==== 2.2 Accessing the control points ====
+=== A) Via ModbusTCP ===
+See above mentioned register numbers. Use ModbusTCP unitid 100.
+=== B) Via MQTT ===
+Recently we have added MQTT to the protocols on the CCGX. For more information, see [[https://groups.google.com/forum/m/#!forum/victron-dev-venus|the developer mailing list]] as well as the [[https://github.com/victronenergy/dbus-mqtt|mqtt github repo]].
+=== C) Running your own scriptson the CCGX ===
+Start reading [[open_source:start|here]].
+The Hub-4 related D-Bus paths are:
+  * com.victronenergy.hub4 /AcPowerSetpoint
+  * com.victronenergy.hub4 /MaxChargePercentage
+  * com.victronenergy.hub4 /MaxDischargePercentage
+==== 2.3 Background ====
+In standard mode the Hub-4 control system tries to keep the power flowing through the grid meter at 0 Watt (so no power is taken in from the grid, nor is any power fed back to the grid). Mode 2 means you set the target for the grid power. Setting the target to 100 Watt means that the system tries to take 100 Watt from the grid. The power will be used to feed the loads or charge the battery. Similar, a negative value will instruct the system to feed back power to the grid. This will be PV power when possible, otherwise the battery will be discharged. Reset the setpoint back to 0 Watt, and you are back in standard mode again.
+In addition you can also control battery charge and discharge. This allows you to control when the battery is charged and discharged.
+==== 2.4 Notes ====
-==== 2.1 Notes ====
   * The above settings are intended for power management, and will be overridden by battery safety mechanisms. For example: if the multi is in sustain mode - because the battery is almost empty - it will start charging the battery, event if the grid power setpoint is negative or the maximum charge percentage is set to zero.
   * Sustain will always remain in operation. Disabling charge will not disable sustain. Note that this was added to the Hub-4 Assistant released in january 2016 (version 154).
@@ Line 186: / Line 197: @@
   * 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
 ===== DISQUS =====
 ~~DISQUS~~