Differences

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

--- ccgx:start [2019-06-09 08:25] – [4.1 Introduction and features] mvader
+++ ccgx:start [2019-06-11 22:10] – [4.3 DVCC effects on the charge algorithm] mvader
@@ Line 584: / Line 584: @@
 Enabling DVCC changes a GX device from a passive monitor into an active controller.
-For example, in systems with an intelligent CAN-bus BMS battery connected, the GX receives a Charge Voltage Limit (CVL), Charge Current Limit (CCL), Discharge Current Limit (DCL) from that battery. And relays that to the connected inverter/chargers and solar chargers. These then disable their internal charge algorithms; and simply do what their told to do by the battery. There is no need to set-up charge voltages or choose the charge algorithm type.
+For example, in systems with an intelligent CAN-bus BMS battery connected, the GX receives a Charge Voltage Limit (CVL), Charge Current Limit (CCL), Discharge Current Limit (DCL) from that battery and relays that to the connected inverter/chargers and solar chargers. These then disable their internal charge algorithms and simply do what their told by the battery. There is no need to set-up charge voltages or choose the charge algorithm type.
 For systems with lead batteries, DVCC offers features such as a configurable system wide charge current limit and shared temperature sense.
-As also in above example, the available features, and effects of enabling DVCC, depend on the used type of battery. The also depends on the installed Victron components and their configuration.
+As also in above example, the available features and effects of enabling DVCC depend on the type of battery used. The also depends on the installed Victron components and their configuration.
-{{ :ccgx:dvcc_table.png?nolink&800 |}}
+{{ :ccgx:dvcc_table2.png?nolink&800 |}}
 For the details, carefully study below chapters to fully understand DVCC for a particular system.
@@ Line 599: / Line 599: @@
 === Battery compatilibity ===
-For CAN-bus connected batteries, check the relevant page on the [[battery_compatibility:start|Battery Compatibility manual]] to see if enabling DVCC has been tested with your battery-type, and is OK. If DVCC is not mentioned in notes relating to your battery, do not enable DVCC.
+For CAN-bus connected batteries, check the relevant page on the [[battery_compatibility:start|Battery Compatibility manual]] to see if enabling DVCC has been tested with your battery-type and is supported. If DVCC is not mentioned in notes relating to your battery, do not enable DVCC.
 For Gel, AGM, OPzS and other lead batteries, DVCC can be used without any problem. The same is true for Victron Energy lithium batteries with the VE.Bus BMS, the Lynx Ion + Shunt BMS or the Lynx Ion BMS. DVCC is the //preferred// operating mode for Redflow ZBM2/ZCell batteries using the Redflow CANBus BMS.
@@ Line 605: / Line 605: @@
 === Firmware versions ===
-Do not use DVCC in cases where these requirements are not met. In all cases, we recommend to install the latest available firmware during commissioning. Once running well, there is no need to pro-actively update firmware without reason. In case of trouble, the first action is to update firmware.
+Do not use DVCC in cases where these requirements are not met. In all cases we recommend to install the latest available firmware during commissioning. Once running well, there is no need to pro-actively update firmware without reason. In case of trouble, the first action is to update firmware.
 Required minimum firmware versions:
@@ Line 636: / Line 636: @@
 Inverter/charger indicated charge state: bulk, absorption, float, and-so-forth.
-MPPT indicated charge state: bulk, absorption, float and-so-forth. (firmware version v1.42 onwards. Earlier versions have a bug that, even though the algorithm is active, it still shows Ext. control when DVCC is enabled & a max charge current is enabled as well.
+MPPT indicated charge state: bulk, absorption, float and-so-forth. (firmware version v1.42 onwards. Earlier versions have a bug that make the MPPT say "Ext. Control" when it is only being current limited; its internal charge algorithm still active.
 === Inverter/charger (applies to MPPTs only) ===
@@ Line 668: / Line 668: @@
 This setting is available in the "Settings -> "System Setup" menu on the [[venus-os:start| GX device]].
-Note that this mechanism only works for Victron inverter/chargers and Solar chargers. Other chargers, such as Skylla-i’s are not controlled and also their charge current is not taken into account. Same for devices of that are not connected to the GX device, such as an alternator. Worded differently: the total charge current of the inverter/chargers and all MPPTs will be controlled, nothing else. Any other sources will be extra charge current, not accounted for, also not when installing a BMV or other battery monitor.
+Note that this mechanism only works for Victron inverter/chargers and Solar chargers. Other chargers, such as Skylla-i’s are not controlled and also their charge current is not taken into account. The same applies for devices that are not connected to the GX device, such as an alternator. Worded differently: the total charge current of the inverter/chargers and all MPPTs will be controlled, nothing else. Any other sources will be extra charge current, unaccounted for even when installing a BMV or other battery monitor.
 In all situations, the maximum charge limit configured in a device itself, ie. the Charge current limit set with VictronConnect or VEConfigure for the Solar chargers or Inverter/chargers will still be in effect. An example to illustrate: in case there is only an Inverter/charger in the system, and in VEConfigure is charge current is configured to 50 Amps. And on the GX Device, a limit of 100A is configured, then the working limit will be 50 Amps.
@@ Line 710: / Line 710: @@
   * The ESS Keep batteries charged mode works properly. It does not without DVCC.
-  * a fixed solar offset of 0.4V is used instead of a variable 2V. (values for 48V systems, divide by 4 for 12V). Note that this solar offset is only used by the system when ''ESS-mode'' is set to ''Optimized'' in combination with the ''Feed-in excess solar charger power''-setting enabled, or when ''ESS-mode'' is set to ''Keep batteries charged''.
+  * a fixed solar offset of 0.4V is used instead of a variable 2V. (values for 48V systems, divide by 4 for 12V). Note that this solar offset is only applied when ''ESS-mode'' is set to ''Optimized'' in combination with the ''Feed-in excess solar charger power''-setting enabled, or when ''ESS-mode'' is set to ''Keep batteries charged''.
   * Add Auto-recharge feature for the ESS Modes ''Optimized'' and ''Optimized (with BatteryLife)''. The system will automatically recharge the battery (from the grid) when the SOC drops 5% or more below the value of ‘Minimum SOC’ in the ESS menu. Recharge stops when it reaches the Minimum SOC.
   * ESS improved state display: In addition to the charger states (Bulk/Absorption/Float), additional ''Discharging'' and ''Sustain'' modes were added. In addition it also shows reasons for the state it is in:
@@ Line 741: / Line 741: @@
 ==== 5.3 Datalogging to VRM ====
-Data-logs are transmitted to the VRM Portal, over the Internet, if it's available. All related settings are available in the VRM Online Portal menu:
+Data-logs are transmitted to the VRM Portal over the Internet, if it's available. All related settings are available in the VRM Online Portal menu:
 {{ :ccgx:vrmsettings3.png?nolink |}}
@@ Line 833: / Line 833: @@
 If a Connection error is shown, the CCGX is not able to contact the VRM database. The connection error will show an error code that indicates the nature of the connectivity problem. Also, details of the error message are shown, to facilitate on site IT experts to diagnose the problem.
-  * Error #150 Unexpected response text: A connection succeeded, but the result was incorrect. This might indicate that a transparent proxy is hijacking the connection. Such as a WiFi login page, or a cellular providers payment page.
+  * Error #150 Unexpected response text: A connection succeeded, but the result was incorrect. This might indicate that a transparent proxy is hijacking the connection. Examples include a WiFi login page or a cellular providers payment page.
-  * Error #151 Unexpected HTTP Response: A connection succeeded, but the response did not indicate a successful HTTP result code (normally 200). This might indicate that a transparent proxy is hijacking the connection.
+  * Error #151 Unexpected HTTP Response: A connection succeeded, but the response did not indicate a successful HTTP result code (normally 200). This might indicate that a transparent proxy is hijacking the connection. See #150 above for examples.
   * Error #152 Connection time-out: this could indicate a poor quality internet connection, or a restrictive firewall.
   * Error #153 Connection error: this could indicate a routing problem. For details, check the shown error message: {{ :ccgx:vrm-connection-error.png?nolink |}}
@@ Line 841: / Line 841: @@
   * Error #159 Unknown error: this is a catch-all error for errors that cannot be directly categorised. In such cases the Error message will provide information about the problem. {{ :ccgx:vrm-unknown-error.png?nolink |}}.
-Check 'Last contact'. If this shows dashes, the GX device has not been able to contact the VRM Portal since power up. If it shows a time, but still an error is shown, then the GX device has been able to send data, but cannot send it any longer.
+Check 'Last contact'. If this shows dashes, the GX device has not been able to contact the VRM Portal since power up. If it shows a time, but still an error is shown, then the GX device has been able to send data, but has since lost contact.
 The 'Buffered items' indicates the number of logs that it has stored to send later. If this is larger than 0, it means that the CCGX can not connect to the VRM Portal. All data is sent using the First in First out principle: the VRM Portal will only show the most up to date information after all old data has been sent.