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-08-13 07:55] – [4.5 DVCC Features when using CAN-bus BMS Battery] andyalford
@@ Line 205: / Line 205: @@
   * USB Tethering on a mobile phone
-The chapters below describe these options in detail.
+This video explains how to connect LAN, WiFi and a GX GSM:
+{{youtube>645QrB7bmvY}}
+The chapters below describe the options in detail.
 === 1.6.1 Ethernet LAN port ===
@@ Line 329: / Line 332: @@
 |Change time zone|Select the correct time zone. ||
 |**Remote console** |
-|Disable password check |Password authentication not required for remote consul access.||
+|Disable password check |Password authentication not required for remote console access.||
 |Enable password check | Choose password to allow remote console access.||
 |Enable on VRM |No|Enabling on VRM will allow connection to the CCGX from anywhere via the VRM portal. [[vrm_portal:troubleshooting_ccgx_vrm_connectivity#trouble_shooting_remote_console_on_vrm|Trouble shooting Remote Console on VRM]]|
@@ Line 584: / Line 587: @@
 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 they're 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 effect 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 602: @@
 === 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 608: @@
 === 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 difficulty, the first action is to update firmware.
 Required minimum firmware versions:
@@ Line 622: / Line 625: @@
 ==== 4.3 DVCC effects on the charge algorithm ====
-Our inverter/chargers and MPPT Solar Chargers use their own internal charge algorithm when in stand alone mode. This means that they determine how long to remain in absorption, when to switch to float, when to switch back to bulk, or storage. And in the various phases they then use the configured parameters in VictronConnect and VEConfigure.
+Our inverter/chargers and MPPT Solar Chargers use their own internal charge algorithm when in stand-alone mode. This means that they determine how long to remain in Absorption, when to switch to Float, when to switch back to Bulk, or Storage. And in those various phases they use the configured parameters in VictronConnect and VEConfigure.
 In certain systems, the internal charge algorithm is disabled, and the charger is then working with an externally controlled charge voltage target.
@@ Line 636: / Line 639: @@
 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) ===
-The MPPTs internal charge algorithm is disabled; instead its being controlled by a charge voltage setpoint coming from the inverter/charger.
+The MPPTs internal charge algorithm is disabled; instead it's being controlled by a charge voltage setpoint coming from the inverter/charger.
 MPPT indicated charge state: Ext. control.
@@ Line 648: / Line 651: @@
 The internal charge algorithm is disabled; and instead, the device is being controlled by the battery.
-Inverter/charger indicated charge state: bulk when in current controlled mode, absorption when in voltage controlled mode. Never float; even tough currents might below / battery might be full.
+Inverter/charger indicated charge state: Bulk when in current controlled mode, Absorption when in voltage controlled mode. Never Float; even though currents might be low / battery might be full.
 MPPT indicated charge state: Ext. control.
@@ Line 661: / Line 664: @@
 {{ :ccgx:limit_charge_current.png?nolink&400 |}}
+This setting is available in the "Settings -> "System Setup" menu on the [[venus-os:start| GX device]].
 Particulars:
-In case a CANBUS-BMS is connected and the BMS requests a maximum charge current that is different from the user-configurable setting, the lower of the two will be used.
+) In case a CANBUS-BMS is connected and the BMS requests a maximum charge current that is different from the user-configurable setting, the lower of the two will be used.
-This setting is available in the "Settings -> "System Setup" menu on the [[venus-os:start| GX device]].
+) 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.
-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.
+) DC Loads are not accounted for. Even when a BMV or other battery monitor is installed. For example, with a configured maximum charge current of 50 Apms, and DC Loads drawing 20 Amps, the battery will be charged with 30 Amps. Not with the full allowed 50 Amps.
-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.
+) 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 this: 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.
 === Shared Voltage Sense (SVS) ===
@@ Line 691: / Line 696: @@
 Such intelligent BMS sends four parameters to the GX device:
-  - Charge current limit (CVL): the maximum charge voltage that the battery currently accepts.
+  - Charge voltage limit (CVL): the maximum charge voltage that the battery currently accepts.
   - Charge current limit (CCL): the maximum charge current requested by the battery.
   - Discharge current limit (DCL): the maximum discharge current as requested by the battery.
@@ Line 709: / Line 714: @@
 ==== 4.6 DVCC for systems with the ESS Assistant ====
-  * The ESS Keep batteries charged mode works properly. It does not without DVCC.
+  * 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:
-    * #1: SOC is low
+    * #1: Low SOC: discharge disabled
     * #2: BatteryLife is active
-    * #3: BMS disabled charging
+    * #3: Charging disabled by BMS
-    * #4: BMS disabled discharge
+    * #4: Discharging disabled by BMS
     * #5: Slow Charge in progress (part of BatteryLife, see above)
     * #6: User configured a charge limit of zero.
@@ Line 741: / Line 746: @@
 ==== 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 838: @@
 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 846: @@
   * 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.
@@ Line 853: / Line 858: @@
   - In VictronConnect, use the GX Log Converter feature to convert them to Excel sheets.
+==== 5.6 Remote Console on VRM ====
+This feature allows full remote control of a GX Device, over the internet:
+{{ :vrm_portal:vrm-remote-console-headline.png?nolink |}}
+Remote Console on VRM is disabled by default. Activate it by following these steps:
+  - Enabling the feature in the Settings -> Remote Console menu
+  - Either set a password; or disable the password
+  - Restart the GX Device.
+Now, the Remote Console option will appear in the menu on the VRM Portal. Click it to open the Remote Console:
+{{ :vrm_portal:vrm_remote_console.jpg?direct }}
+Trouble shooting tips:
+  - Make sure that basic communication with VRM works, see chapter 5.4.
+  - After enabling the feature, make sure to set (or disable) the password.
+  - Also make sure to restart the CCGX.
+  - Make sure to update the CCGX to the latest firmware version. The last stability improvement for Remote Console was made in version v2.30.
+  - After the restart, check the Remote Console on VRM status shows online or a port number. In case it says offline, or port number 0, the CCGX was unable to connect to the Remote Console server. This is normally caused by a (company) firewall, blocking the connection. The solution is then to configure an exception rules in the firewall.
+  - Verify that your local web browser can access the [[https://vncrelay.victronenergy.com/|websocket port (443 on vncrelay.victronenergy.com]]). If you click that link and get 'Error response, method not allowed', it means the connection between your PC and the VNC relay is working. If you get a timeout or another (browser) error, there may be a firewall blocking the connection.
+Remote Console on VRM uses the same reverse SSH tunnel as is used for Remote Support: outbound connection to supporthost.victronenergy.com on port 22, 80 or 443. It is not necessary to set up port forwarding in routers to use Remote Console on VRM. It is necessary for the firewall/router to which the CCGX is connected, to allow outbound connections to supporthost.victronenergy.com on at least one of the three mentioned port numbers. Most routers will allow this by default.
 ===== 6. Marine MFD Glass bridge integration =====