User Tools

Site Tools


ccgx:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ccgx:start [2019-04-06 07:48]
mvader [3.2 Generic features]
ccgx:start [2019-07-18 09:35] (current)
vosser changed "consul" to "console"
Line 9: Line 9:
 The CCGX also provides Remote firmware updates and even allows the settings to be Changed Remotely. The CCGX also provides Remote firmware updates and even allows the settings to be Changed Remotely.
  
-The Color Control GX is part of the [[https://​www.victronenergy.com/​live/​venus-os:​start|GX product family]]. GX products are Victron'​s state-of-the-art monitoring solution that run our VENUS operating system.+The Color Control GX is part of the [[https://​www.victronenergy.com/​live/​venus-os:​start|GX product family]]. GX products are Victron'​s state-of-the-art monitoring solution that run our Venus OS operating system.
  
 All the information in this manual refers to the latest software. Your device will update itself to the latest version automatically. Check our blog posts to see that your device has the latest firmware:​[[https://​www.victronenergy.com/​blog/​category/​firmware-software/​]] All the information in this manual refers to the latest software. Your device will update itself to the latest version automatically. Check our blog posts to see that your device has the latest firmware:​[[https://​www.victronenergy.com/​blog/​category/​firmware-software/​]]
Line 167: Line 167:
 Alternatively,​ instead of a VE.Can to NMEA200, you can use a 3802 cable from Oceanic Systems: https://​osukl.com/​ve-can-adaptor/​. The difference is that it lends itself well to connecting a single NMEA-2000 device into a VE.Can network. It's also able to power a lower voltage NMEA-2000 network directly from a 48V Victron system. Alternatively,​ instead of a VE.Can to NMEA200, you can use a 3802 cable from Oceanic Systems: https://​osukl.com/​ve-can-adaptor/​. The difference is that it lends itself well to connecting a single NMEA-2000 device into a VE.Can network. It's also able to power a lower voltage NMEA-2000 network directly from a 48V Victron system.
  
-==== 1.5 Monitoring ​PV Inverter ​output ​====+==== 1.5 Connecting a PV Inverter ==== 
 Measuring the output of a PV Inverter will provide the user with an overview of both actual power balance and the energy distribution. Note that these measurements are only used to display information. They are not needed, nor used, by the installation for its performance. Measuring the output of a PV Inverter will provide the user with an overview of both actual power balance and the energy distribution. Note that these measurements are only used to display information. They are not needed, nor used, by the installation for its performance.
  
-There are several ways to get the system to show the output ​of PV Inverter: +Besides monitoring, ​the GX device can also curtail some types and brands ​of PV Inverters, iereduce their output powerThis is usedand required, for the [[ess:design-installation-manual|ESS Zero feed-in feature]]. 
-  - [[https://​www.victronenergy.com/​accessories/​ac-current-sensor|An AC Current Sensor]]wired to the analog inputs of a Multi or Quattro provides the information at the lowest cost - though it is the least accurate. ​[[ac_current_sensor:start|AC Current Sensor Manual]]. + 
-  - [[http://​www.fronius.com/​|Fronius ​PV Inverters]] can be read digitally via the local LAN. See the [[ccgx:ccgx_fronius|GX - Fronius ​manual]]. +=== Direct connections === 
-  - [[https://​www.sma.de/en/|SMA PV Inverters]] can be read digitally via the local LAN. See the [[ccgx:ccgx_sma|GX - SMA manual]]. +^ Type  ^ Zero feed-in ^ Details ^ 
-  - [[https://​www.solaredge.com/|SolarEdge PV Inverters]] can be read digitally via the local LANSee the [[venus-os:gx_solaredge|GX - SolarEdge manual]]. +| Fronius |  Yes  | LAN Connection, see [[ccgx:ccgx_fronius|GX - Fronius ​manual]] 
-  - Using a [[https://​www.victronenergy.com/​accessories/​energy-meter|Victron ​Energy Meter]], either ​wired to the CCGX, or connected wirelessly using our Zigbee to USB/RS485 interfaces. See the [[energy-meters:​start]]. +| SMA |  No  | LAN Connection, see [[ccgx:ccgx_sma|GX - SMA manual]] ​| 
-  - By using [[https://​www.victronenergy.com/​accessories/​wireless-ac-sensor|Wireless AC sensors]]See the [[ccgx:​ccgx_wireless_ac_sensor]].+| SolarEdge |  No  | LAN Connection, see [[venus-os:​gx_solaredge|GX - SolarEdge manual]] | 
 +| ABB |  Yes  | LAN Connection, see [[https://​www.victronenergy.com/live/ccgx:abb|GX ABB manual]] ​| 
 + 
 +=== Using a meter === 
 + 
 +For PV Inverters that cannot be interfaced digitally, a meter can be used: 
 + 
 +^ Type ^ Zero feed-in ^ Details ^ 
 +[[https://​www.victronenergy.com/accessories/​ac-current-sensor|AC Current Sensor]] |  No  | Connected to inverter/​charger analog input. Lowest cost - least accurate. [[ac_current_sensor:start|AC Current Sensor Manual]] | 
 +[[https://​www.victronenergy.com/​accessories/​energy-meter|Energy Meter]] ​|  No  | wired to the CCGX, or connected wirelessly using our Zigbee to USB/RS485 interfaces. The best solution. See the [[energy-meters:​start]] ​| 
 +[[https://​www.victronenergy.com/​accessories/​wireless-ac-sensor|Wireless AC sensors]] ​|  No  | See the [[ccgx:​ccgx_wireless_ac_sensor]] ​|
  
 ==== 1.6 Internet connectivity ==== ==== 1.6 Internet connectivity ====
Line 194: Line 205:
   * USB Tethering on a mobile phone   * 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 === === 1.6.1 Ethernet LAN port ===
Line 206: Line 220:
 Using a Wi-Fi dongle it is possible to connect to WEP, WPA and WPA2 secured networks. There are four supported USB Wi-Fi dongles. Two of them are also available from stock at Victron Energy: Using a Wi-Fi dongle it is possible to connect to WEP, WPA and WPA2 secured networks. There are four supported USB Wi-Fi dongles. Two of them are also available from stock at Victron Energy:
  
-  * CCGX WiFi module simple (Nano USB), small, low cost. Victron part number BPP900100200 +  * Partno. BPP900100200 - CCGX WiFi module simple (Nano USB), small, low cost. 
-  * [[https://​www.google.nl/​search?​q=Gembird+WNP-UA-002|Gembird WNP-UA-002]], slightly higher cost and also better reception. ​Victron part number: BPP900200200 +  * Partno. BPP900200300 - [[https://​www.google.nl/​search?​q=Asus+USB-N14|Asus USB-N14]], slightly higher cost and also better reception ​than the Nano USBSupported since software version 2.23.
-  * [[https://​www.google.nl/​search?​q=Startech+USB300WN2X2D|Startech USB300WN2X2D]] +
-  * [[https://​www.google.nl/​search?​q=zyxel+NWD2105|Zyxel NWD2105]]+
  
-New model coming early 2019: [[https://​www.google.nl/​search?​q=Asus+USB-N14|Asus USB-N14]], slightly higher cost and also better reception. Victron part number: BPP900200300. Requires a firmware version not released yet.+WiFi modules that are no longer available, but still supported, are: 
 +  * Partno. BPP900200100 - [[https://​www.google.nl/​search?​q=Startech+USB300WN2X2D|Startech USB300WN2X2D]] 
 +  * Partno. BPP900100100 ​[[https://​www.google.nl/​search?​q=zyxel+NWD2105|Zyxel NWD2105]] 
 +  * Partno. BPP900200200 - [[https://​www.google.nl/​search?​q=Gembird+WNP-UA-002|Gembird WNP-UA-002]], slightly higher cost and also better reception.
  
 Although other Wi-Fi dongles may work, they have not been tested and we do not offer support for other dongles. Although other Wi-Fi dongles may work, they have not been tested and we do not offer support for other dongles.
Line 317: Line 332:
 |Change time zone|Select the correct time zone. || |Change time zone|Select the correct time zone. ||
 |**Remote console** | |**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 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]]| |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 376: Line 391:
  
 {{:​ccgx:​menustructure_ccgx.jpeg?​direct&​200 ​ }} {{:​ccgx:​menustructure_ccgx.jpeg?​direct&​200 ​ }}
-==== 2.2 Logging data for the VRM portal ==== 
  
-The CCGX can be used in combination with the [[https://​vrm.victronenergy.com/​|Victron Remote Management (VRM) portal]]: The CCGX monitors all products connected to it and the VRM portal makes the statistics easily accessible. 
- 
-Since version 1.40, dealing with an absent or intermittent internet connection has changed. Data is sent out via the Internet if it's available, and will fall back to non-volatile storage when there is a (temporary) Internet outage. The built-in non-volatile storage can contain 48 hours worth of data. To extend this period, one can insert an microSD card or USB stick, and the CCGX will automatically transfer any data that may reside on the internal storage to it, and will start using this external memory as backlog buffer. You can see that it's active in the settings menu: 
- 
-{{ :​ccgx:​vrmsettings.png?​nolink |}} 
- 
-When using this external memory, it will still make use of an active internet connection to send its backlog. That means that even with months worth of backlog, once the CCGX re-acquires an Internet connection, all of the backlog is sent out. And because of an enhanced algorithm, this takes considerably less time and traffic than before. 
- 
-When a CCGX is permanently without Internet, one can choose to upload the backlog buffer manually. The first step is to use the GUI (Graphical User Interface) to eject the storage (don't just remove the SD-card/​USB-stick). The storage device can then be removed from the CCGX and inserted into a computer or laptop, the data file on it can be uploaded on the VRM Portal with the '​Upload CCGX File' option: 
- 
-{{ :​drafts:​upload_sqlite_menu_option.png?​nolink |}} 
- 
-It's important to know that when the microSD card or USB stick is re-inserted,​ the existing buffer - including its data - is used again. This allows for removing the microSD card temporarily for whatever reason, **but this also means that when the data file has been uploaded to VRM, it needs to be renamed or cleared from the microSD card / USB stick before re-inserting**,​ otherwise the data will be transmitted again, sooner or later, on-line or off-line. 
- 
-Because of the aforementioned improvement in sending of backlog data, the data logging is also highly resillient to bad internet connections. Lines of up to 70% permenant packet loss are still  sufficient to get the data out, albeit somewhat delayed. 
- 
-With a log interval of once per minute, the required storage space roughly amounts to about 25 MB per month, depending on the number of connected products. So with a 1 GB microSD card, you can store about 3 years of backlog. In other words, any microSD card or USB stick should be sufficient to store the 6 months of data which VRM retains. ​ 
- 
-When the storage device is full, no more data will be logged. This is due to the nature of Sqlite files. Removing data from the Sqlite database doesn'​t free-up usable disk space; and because of internal fragmentation,​ it doesn'​t guarantee more data storage. 
- 
-If both a microSD card and a USB flash drive are connected to the CCGX, then data is logged to the one that was inserted first. If one is removed, the CCGX will not try to write to the other, but will create an internal backlog buffer until a new storage medium is inserted when it will use that storage medium. ​ 
- 
-  *MicroSD cards or USB flash drives must be formatted as FAT12, FAT16 or FAT32 file systems - and not exFAT or NTFS. 
-  *SD and SDHC type microSD cards of 32 GB capacity and smaller are sold containing FAT12, FAT16 or FAT32. They can be used without a problem, unless they are subsequently re-formatted to a different file system. 
-  *SDXC type microSD cards which have greater than 32 GB capacity are often formatted with exFAT, and therefore cannot be used with the CCGX without reformatting and possibly re-partitioning. 
-==== 2.3 Using the Multi and Quattro input current-limiter setting ==== 
- 
-=== '​Overruled by remote'​ setting in VEConfigure === 
-This chapter explains the implications of enabling or disabling user control of the input current-limiter setting, as seen here in the menu: 
- 
-{{ :​ccgx:​snapshot.png?​nolink |}} 
- 
-The limit as set by the user in the CCGX will be applied to all inputs where '​Overruled by remote',​ configured with VEConfigure,​ is enabled: 
- 
-{{ :​ccgx:​inputcurrentlimitersettings.png?​nolink |}} 
- 
-Using the example of a boat with two AC inputs and a Quattro where: 
-  - A Genset capable of delivering 50A is connected to input 1; 
-  - Shore power is connected to input 2. (Available power depends on the rating of the harbour power-supply.) 
- 
-Configure the system exactly as in above VEConfigure screenshot. Input 1 has priority over input 2, therefore the system will automatically connect to the genset whenever it is running. The fixed input current limit of 50A will be applied. And when the genset is not available, and mains is available on input 2, the Quattro will use the input current limit as configured in the CCGX. 
- 
-Two more examples: (In both cases if you //disable// '​Overrule by remote',​ setting a current limit in the CCGX will have no effect. And if you //enable// '​Overrule by remote'​ for both inputs, the current limit set in the CCGX will be applied to both inputs.) 
- 
-=== Systems where it is not possible to control the input current limit === 
-It is not possible to control the input current limit in certain installations. In these cases, the CCGX menu will not allow changing the setting: 
-  - Installations with a VE.Bus BMS 
-  - Installations with a Digital Multi Control (or its predecessors) 
-{{:​ccgx:​ccgx_inverter_switch_disabled.png?​nolink|}} 
-{{:​ccgx:​ccgx_inverter_currentlimit_disabled.png?​nolink|}} 
- 
-Also the //​on/​off/​charger only// switch in the CCGX will be disabled in the case. 
- 
-In installation with a VE.Bus BMS, use the rocker switch instead - or add a Digital Multi Control to the installation. 
- 
-=== Minimum input current limit values === 
-When PowerAssist is enabled in VEConfigure,​ there is a minimum input current limit. The actual limit differs for each model. 
- 
-After setting the input current to a value below the limit, it will automatically be increased again to the limit. 
- 
-Note that is still possible to set the input current limit to 0. When set to 0, the system will be in passthrough (charger disabled). 
- 
-=== Parallel and three phase systems === 
-The configured input limit is the total limit //per phase//. 
 ==== 2.4 Battery State of Charge (SOC) ==== ==== 2.4 Battery State of Charge (SOC) ====
  
Line 566: Line 516:
 http://​[ip-here]/​logo.php ​ (inserting your device’s IP address between the square brackets). ​ http://​[ip-here]/​logo.php ​ (inserting your device’s IP address between the square brackets). ​
 The IP address can be found by going to Settings > Ethernet or Wifi. Once the page is loaded, Choose an image file from your device. Re-boot the VENUS device. The IP address can be found by going to Settings > Ethernet or Wifi. Once the page is loaded, Choose an image file from your device. Re-boot the VENUS device.
-===== 3 DVCC - Distributed Voltage and Current Control ===== 
  
-==== 3.1 Introduction and requirements ​====+===== 3 VE.Bus Inverter/​charger monitoring =====
  
-With DVCC enabled, the [[venus-os:​start|Venus-device]] takes a more central role in the Victron system, improving and changing system behaviourDVCC allows you to set a maximum charge ​current setting ​that applies to the whole system. ​+==== 3.1 Input current-limiter ​setting ​====
  
-For example, an Off-grid system ​with MPPTsMultis ​and a diesel generator. The MPPTs are sized and configured ​such that they charge ​the battery ​with the maximum allowed charge ​current. If the genset starts while there are no AC loadswith DVCC enabled, the Multi will be limited ​and prioritise ​the MPPTsWithout ​DVCC, the Multi would also start charging ​with its maximum configured ​charge current. ​+=== '​Overruled by remote'​ setting in VEConfigure === 
 +This chapter explains the implications of enabling or disabling user control of the input current-limiter setting, as seen here in the menu: 
 + 
 +{{ :​ccgx:​snapshot.png?​nolink |}} 
 + 
 +The limit as set by the user in the CCGX will be applied to all inputs where '​Overruled by remote',​ configured ​with VEConfigureis enabled: 
 + 
 +{{ :​ccgx:​inputcurrentlimitersettings.png?​nolink |}} 
 + 
 +Using the example of a boat with two AC inputs ​and a Quattro where: 
 +  - A Genset capable of delivering 50A is connected to input 1; 
 +  - Shore power is connected to input 2. (Available power depends on the rating of the harbour power-supply.) 
 + 
 +Configure the system exactly as in above VEConfigure screenshot. Input 1 has priority over input 2, therefore the system will automatically connect to the genset whenever it is running. The fixed input current limit of 50A will be applied. And when the genset is not available, ​and mains is available on input 2, the Quattro will use the input current limit as configured ​in the CCGX. 
 + 
 +Two more examples: (In both cases if you //disable// '​Overrule by remote',​ setting a current limit in the CCGX will have no effect. And if you //enable// '​Overrule by remote'​ for both inputs, the current limit set in the CCGX will be applied to both inputs.) 
 + 
 +=== Systems where it is not possible to control the input current limit === 
 +It is not possible to control the input current limit in certain installations. In these cases, the CCGX menu will not allow changing the setting: 
 +  - Installations ​with a VE.Bus BMS 
 +  - Installations with a Digital Multi Control (or its predecessors) 
 +{{:​ccgx:​ccgx_inverter_switch_disabled.png?​nolink|}} 
 +{{:​ccgx:​ccgx_inverter_currentlimit_disabled.png?​nolink|}} 
 + 
 +Also the //​on/​off/​charger only// switch in the CCGX will be disabled in the case. 
 + 
 +In installation with a VE.Bus BMS, use the rocker switch instead - or add a Digital Multi Control to the installation. 
 + 
 +=== Minimum input current ​limit values === 
 +When PowerAssist is enabled in VEConfigure,​ there is a minimum input current limit. The actual limit differs for each model. 
 + 
 +After setting the input current to a value below the limit, it will automatically be increased again to the limit. 
 + 
 +Note that is still possible to set the input current limit to 0. When set to 0, the system will be in passthrough (charger disabled). 
 + 
 +=== Parallel and three phase systems === 
 +The configured AC input current limit is the total limit //per phase//. 
 + 
 +==== 3.2 Phase rotation warning ==== 
 + 
 +The AC supply, either Generator or Grid, to a three phase inverter/​charger system needs to be in the correct rotation, also known as sequence. If not, then the Inverter/​chargers will not accept ​the AC supply and remain in Inverter mode. 
 + 
 +The ''​Phase rotation warning''​ will be raised in such case. To resolve the issuechange the wiring on the AC input: swap either one of the phaseseffectively changing ​the rotation from ''​L3 -> L2 -> L1''​ to ''​L1 -> L2 -> L3''​. 
 + 
 +On the GX device itself, the warning ​will be popup as a notification on the GUI: 
 + 
 +{{ :​ccgx:​phase-rotation-gui-notification.png?​nolink |}} 
 + 
 +Also, it is visible in the menus: 
 + 
 +{{ :​ccgx:​phase-rotation-gui-menus.png?​nolink |}} 
 + 
 +And on the VRM Portal, it is visible on the VE.Bus Alarms & warnings widget on the Advanced page: 
 + 
 +{{ :​ccgx:​phase-rotation-vrm_widget.png?​nolink |}} 
 + 
 +And also it will be listed in the Alarm Log on VRM, and an email will be sent; using [[:​vrm_portal:​alarms#​automatic_alarm_monitoring|the VRM Alarm Monitoring system]]. 
 + 
 + 
 + 
 +===== 4 DVCC - Distributed Voltage and Current Control ===== 
 + 
 +==== 4.1 Introduction and features ==== 
 + 
 +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 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 type of battery used. The effect also depends on the installed Victron components and their configuration. 
 + 
 +{{ :​ccgx:​dvcc_table2.png?​nolink&​800 |}} 
 + 
 +For the details, carefully study below chapters to fully understand DVCC for a particular system. 
 + 
 +To enable or disable DVCC, see Settings -> System Setup in the menus. 
 +==== 4.2 DVCC Requirements ==== 
 + 
 +=== 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 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.
  
-This system is also used to apply the various charge and discharge current limits for various CAN-bus BMS connected batteries. ​+=== Firmware versions ===
  
-Enabling and disabling ​DVCC+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.
-  * Go to Settings ​-> System Setup+
  
 Required minimum firmware versions: Required minimum firmware versions:
   * Multi/​Quattro:​ 422   * Multi/​Quattro:​ 422
 +  * MultiGrid: 424
   * CCGX / Venus GX: v2.12   * CCGX / Venus GX: v2.12
   * VE.Direct MPPTs: v1.29   * VE.Direct MPPTs: v1.29
Line 589: Line 621:
 In case of an ESS System, the ESS Assistant needs to be version 164 or later (Released in November 2017). In case of an ESS System, the ESS Assistant needs to be version 164 or later (Released in November 2017).
  
-In case of installing a MultiGrid 48/3000 the firmware needs to be version 424 or later.+{{ :​ccgx:​dvcc_page2.png?nolink |}}
  
-Do not use DVCC in cases where these requirements are not met.+==== 4.3 DVCC effects on the charge algorithm ====
  
-Important: Where batteries are connected via CAN-buscheck the relevant page on the [[battery_compatibility:​start|Battery Compatibility manual]] ​to see if enabling DVCC has been tested with your battery-typeand is OK. If DVCC is not mentioned in notes relating ​to your batterydo not enable DVCC.+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 Absorptionwhen to switch to Floatwhen to switch back to Bulkor Storage. And in those various phases they use the configured parameters in VictronConnect and VEConfigure.
  
-For GelAGMOPzS 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.+In certain systemsthe internal charge algorithm is disabled, and the charger ​is then working ​with an externally controlled charge voltage target.
  
-{{ :ccgx:​dvcc_page2.png?​nolink |}} +This guide explains the different possibilities:
-==== 3.2 Generic features ====+
  
-Below features apply to all types of systems when DVCC is enabledOffgrid, Backup, ESS, marine and others. And applies to all types of batterieslead batteries as well as lithium batteries, both with and without a CAN-bus BMS connected to the Victron system.+{{:ccgx:dvcc_and_charge_algorithm.png?​nolink&​700 |}}
  
-  * A user-configurable maximum charge current setting. It works across the whole system. MPPTs are automatically prioritized over the mains/​generator. 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|Venus-device]]. Note that this mechanism only works for Victron inverter/​chargers and Solar chargers. Other chargers, such as Skyllai’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. Ofcourse, in theory it might be possible to use the BMV current reading to somewhat overcome this limitation; but thats not so easy to make stable; and hence we’ve decided to not go there. Worded differently:​ the total charge current of the inverter/​chargers and all MPPTs will be controlled. Any other sources will be extra charge current, not accounted for, also not when installing a BMV or other battery monitor. +=== Internal ​===
-  * Shared voltage sense (SVS) for VE.Bus devices and VE.Direct Solar Chargers. +
-    * The system automatically selects the best available voltage measurement. It will use the voltage from the BMS or a BMV battery monitor, if possible, otherwise it will use the battery voltage reported by the VE.Bus system. +
-    * The voltage displayed on the GUI reflects the same voltage measurement. +
-    * Shared Voltage Sense (SVS) is by default enabled when DVCC is enabled. It can be disabled with a switch in the Settings -> System Setup menu. +
-==== 3.3 Features for systems using a CAN-bus BMS systems ====+
  
-These features apply to all types of systems ​(ESS and not ESS), that have a CAN-bus BMS connected battery.+The internal charge algorithm ​(bulk -> absorption -> float -> re-bulk), and the configured charge voltages are active.
  
-  * CAN-bus BMS control is no longer tied into ESS. It now works for other systems as well, including Off-grid and plain backup systems. It is not longer necessary to wire allow-to-charge ​and allow-to-discharge connections to the AUX inputs on a Multi or a Quattro. +Inverter/​charger indicated ​charge ​state: bulkabsorptionfloat, and-so-forth.
-  * VE.Direct MPPT Solar Chargers are now also controlled with the max charge currentjust like Multis and Quattros already were. +
-  * When invertingie in Island modeMultis ​and Quattros will shut down when the max discharge current is zero. They will automatically start again as soon as either AC mains returns, or when BMS increases the max discharge current again. +
-  * New for Off-grid systems only (for ESS systems this was already happening): setting up charge voltages in VEConfigure is no longer necessary: the Multis, Quattros and also MPPT Solar Chargers will charge with the voltage as received via CAN-bus from the battery.+
  
-==== 3.4 Features for ESS ====+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.
  
-  * Fix keep batteries charged. +=== Inverter/​charger (applies to MPPTs only) === 
-  * Change ​the solar offset ​from a variable 2V to a fixed 0.4V. These values ​are for 48V systems, divide by 4 for 12V. This fixes over voltage warnings and shut-downs as seen on several systems with CAN-bus BMSes. 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''​.+ 
 +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. 
 + 
 +=== Battery === 
 + 
 +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 though currents might be low / battery might be full. 
 + 
 +MPPT indicated charge state: Ext. control. 
 + 
 +==== 4.4 DVCC features for all systems ==== 
 + 
 +These features apply to all types of systems when DVCC is enabled: with or without ESS Assistant, and with lead or other normal ​batteries ​as well as when an intelligent CAN-bus BMS connected battery is installed:​ 
 + 
 +=== Limit charge current === 
 + 
 +This is a user-configurable maximum charge current setting. It works across the whole system. MPPT Solar Chargers are automatically prioritized over the mains/​generator. 
 + 
 +{{ :​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:​ 
 + 
 +1) 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.  
 + 
 +2) 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. 
 + 
 +3) 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
 + 
 +4) 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) === 
 + 
 +Works with VE.Bus devices and VE.Direct Solar Chargers. 
 + 
 +The system automatically selects the best available voltage measurement. It will use the voltage ​from the BMS or BMV battery monitor, if possible, otherwise it will use the battery voltage reported by the VE.Bus system. 
 + 
 +The voltage displayed on the GUI reflects the same voltage measurement. 
 + 
 +Shared Voltage Sense (SVS) is by default enabled when DVCC is enabled. It can be disabled with a switch in the Settings -> System Setup menu. 
 + 
 +=== Shared Temperature Sense (STS) === 
 + 
 +tbd 
 +==== 4.5 DVCC Features when using CAN-bus BMS Battery ==== 
 + 
 +This chapter applies ​to all systems where an intelligent battery BMS is installed, and connected via CAN-bus. Note that this does not include the Victron VE.Bus BMS. 
 + 
 +Such intelligent BMS sends four parameters to the GX device: 
 + 
 +  - Charge current 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. 
 + 
 +For all three parameters, some types of batteries transmit dynamic values. For example they determine the maximum charge voltage based on cell voltages, state of charge, or for example temperature. Other makes and brands use a fixed value. 
 + 
 +Here is the page in the menus showing the parameters:​ 
 + 
 +{{ :​ccgx:​battery_parameters.png?​nolink&​400 |}} 
 + 
 +For such batteries, there is no need to wire allow-to-charge and allow-to-discharge connections to the AUX inputs on a Multi or a Quattro. 
 + 
 +When inverting, ie in Island mode, Multis and Quattros will shut down when the max discharge current is zero. They will automatically start again as soon as either AC mains returns, or when the BMS increases the max discharge current again. 
 + 
 +All above means that setting up charge voltages or charge profiles in VEConfigure or VictronConnect is not necessary, and will also have no effect. The Multis, Quattros and MPPT Solar Chargers will charge with the voltage as received via CAN-bus from the battery. 
 + 
 +==== 4.6 DVCC for systems with the ESS Assistant ==== 
 + 
 +  * 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 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.   * 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:   * 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     * #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)     * #5: Slow Charge in progress (part of BatteryLife,​ see above)
     * #6: User configured a charge limit of zero.     * #6: User configured a charge limit of zero.
     * #7: User configured a discharge limit of zero.     * #7: User configured a discharge limit of zero.
-  + 
-===== 4 More information resources =====+ 
 +===== 5. VRM Portal ===== 
 + 
 +==== 5.1 VRM Portal Introduction ==== 
 + 
 +When connected to the internet, a GX device can be used in combination with the [[https://​vrm.victronenergy.com/​|Victron Remote Management (VRM) portal]], which enables: 
 +  * Easy remote access to all statistics and systems status online 
 +  * Remote Console on VRM: access and configure your system as if you were standing besides it 
 +  * Remote Firmware updates of connected Solar Chargers and other Victron products. 
 + 
 +See chapter 1 for how to connect the device to the internet. 
 + 
 +==== 5.2 Registering on VRM ==== 
 + 
 +Instructions are in the [[vrm_portal:​getting_started|VRM Portal Getting Started document]]. 
 + 
 +Note that any system will need to first have been able to successfully send data to the VRM Portal. As long is there has been no successful connection, it will not be possible to register the system to your VRM user account. In such case, refer to below Troubleshooting section 5.7. 
 + 
 +==== 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: 
 + 
 +{{ :​ccgx:​vrmsettings3.png?​nolink |}} 
 + 
 +The transmission of the data logs has been designed to work also on bad internet connections. Lines of up to 70% permenant packet loss are still sufficient to get the data out, even if delayed in some cases. 
 + 
 +=== Adding an external storage device === 
 + 
 +When unable to transmit the logs, then the GX device will store them to non-volatile storage (ie. data is not lost on a power loss or reboot). 
 + 
 +The GX device can store 48 hours worth of logs internally. To extend this period, insert a microSD card or USB stick. You can see the internal storage status in the settings. 
 + 
 +Note that, when inserting such storage device, any internally stored logs will automatically be transferred to the inserted stick: no data is lost. 
 + 
 +With or without an external storage device inserted, the GX Device will always keep trying to connect to the portal and transmit all backlogged logs. That means that even with months worth of backlog, once it re-acquires an Internet connection, all of the backlog is sent out. The data is sent in a compressed manner: sending a lot of backlogged data will use considerably less bandwidth than than sending the data with a continuously available internet connection. 
 + 
 +=== Storage device requirements === 
 + 
 +  * MicroSD cards or USB flash drives must be formatted as FAT12, FAT16 or FAT32 file systems - and not exFAT or NTFS. 
 +  * SD and SDHC type microSD cards of 32 GB capacity and smaller are sold containing FAT12, FAT16 or FAT32. They can be used without a problem, unless they are subsequently re-formatted to a different file system. 
 +  * SDXC type microSD cards which have greater than 32 GB capacity are often formatted with exFAT, and therefore cannot be used with the CCGX without reformatting and possibly re-partitioning. 
 + 
 +=== Manually transferring datalogs to VRM === 
 + 
 +For devices permanently without Internet, it is possible to take the data out, and then upload it manually from a laptop. 
 + 
 +  - go to Settings -> VRM Portal, and click ''​Eject the storage''​. Make sure to never just remove the SD-card/​USB-stick,​ this can lead to corruption and data loss. 
 +  - now, remove the storage device and insert it into a computer or laptop that is connected to the internet. 
 +  - open a webbrowser, and navigate to the [[https://​vrm.victronenergy.com|VRM Portal]]. 
 +  - Login, and then click the '​Upload CCGX File' option, and follow instructions:​ {{ :​drafts:​upload_sqlite_menu_option.png?​nolink |}} 
 +  - Remove the file from the storage device, and then it re-insert it into the GX Device. Note that uploading the same data twice does not cause any problems; but still it is better not to do that. 
 + 
 +With a log interval of once per minute, the required storage space roughly amounts to about 25 MB per month, depending on the number of connected products. So with a 1 GB microSD card, you can store about 3 years of backlog. In other words, any microSD card or USB stick should be sufficient to store the 6 months of data which VRM retains.  
 + 
 +When the storage device is full, no more data will be logged. 
 + 
 +If multiple storage devices are inserted, the GX device will store the data on the one inserted first. When that is removed, it will **not** use the other one. Instead, it will create an internal backlog buffer. Only inserting a new one will make it switch to using external storage again. 
 + 
 +=== Network watchdog: auto-reboot === 
 + 
 +{{ :​ccgx:​vrm-reboot-setting.png?​nolink&​400 |}} 
 + 
 +This feature, disabled by default, makes the GX device automatically reboot itself in case it has not been able to connect to the VRM Portal. 
 +==== 5.Trouble shooting data logging ==== 
 + 
 +This chapter explains what to do when the GX Device cannot transmit data to the VRM Portal. 
 + 
 +The communication required to send logs to the VRM Portal is: 
 +  - Working DNS 
 +  - Proper IP address 
 +  - Working internet connection 
 +  - Outbound http(s) connection to http://​ccgxlogging.victronenergy.com on port 80 and 443. Note that should never be an issue, unless on very specialized company networks. 
 + 
 +Note that the CCGX does not support a proxy setup. For more details on the required networking, see [[https://​www.victronenergy.com/​live/​ccgx:​ccgx_faq#​what_type_of_networking_is_used_by_the_color_control_gx_tcp_and_udp_ports|here]]. 
 + 
 + 
 +=== Step 1: Update the GX Device to the latest available firmware === 
 +[[ccgx:​firmware_updating|GX Device firmware update instructions]] 
 + 
 +=== Step 2: Verify the network status === 
 + 
 +In the menu Settings → Ethernet or Settings → Wi-Fi, check the following:​ 
 + 
 +  - State must be ‘Connected’ 
 +  - There must be an IP address, that does not start with 169. 
 +  - There must be a gateway 
 +  - There must be DNS servers 
 + 
 +In case the IP address starts with 169, check whether your network has a DHCP server running. 99% of all networks have a DHCP server running and it is enabled by default on all well-known ADSL, cable and 3G routers. If there is no DHCP server running, then configure the ip address manually. 
 + 
 +__Ethernet__ 
 + 
 +{{ :​drafts:​troubleshooting_ccgx_vrm_connectivity_ethernet_menu.png?​360,​nolink |}} 
 + 
 +When using Ethernet and State shows '​Unplugged',​ verify that the Ethernet network cable is not faulty: try another one. The two lights at the back of the CCGX, where the Ethernet RJ45 cable plugs in, should be lit or blinking. Two dead lights indicate a connection problem. 
 + 
 +__WiFi__ 
 + 
 +{{ :​drafts:​troubleshooting_ccgx_vrm_connectivity_wifi_menu.png?​360,​nolink |}} 
 + 
 +When using Wi-Fi and the menu shows 'No Wi-Fi adapter connected'​ check the USB connection to the Wi-Fi dongle. Try to remove the dongle and insert it again. 
 + 
 +When using Wi-Fi and the State shows '​Failure',​ it might be that the Wi-Fi password is incorrect. Press '​Forget network'​ and try to connect again with the correct password. 
 + 
 + 
 +=== Step 3. Verify VRM Portal Connectivity === 
 + 
 +Navigate to Settings → VRM online portal, and check the Connection error status: 
 + 
 +{{ :​ccgx:​vrm_connection_no_error.png?​nolink |}} 
 + 
 +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. 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. 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 |}} 
 +  * Error #154 DNS Failure: Make sure that a valid DNS server is configured in the Ethernet or WiFi menu. Typically this is assigned automatically by a DHCP server in a network. 
 +  * Error #155 Routing error: VRM is unreachable. This error occurs if an ICMP error is received indicating that no route exists to the VRM server. Make sure your DHCP server assigns a working default route, or that the gateway is correctly configured for static configurations. 
 +  * 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 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. 
 + 
 +==== 5.5 Analysing data offline, without VRM ==== 
 + 
 +In certain cases, for example for very remote sites where there is no internet available, it can be useful to be able to analyse the data without first having to upload it to the VRM Portal. 
 + 
 +  - Install VictronConnect on a Windows or Apple laptop 
 +  - Insert the storage device containing the log file(s) 
 +  - 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:​8080/​|websocket port (8080 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 ===== 
 + 
 +==== 6.1 Introduction & requirements ==== 
 + 
 +A Glass Bridge is a MFD (Multi-Functional Display) that integrates a boat’s systems and navigation status into a large screen or screens at the helm of the vessel, so doing away with multiple gauges, brackets and wiring complications. 
 + 
 +A Victron system can be easily integrated into that, as shown in this video: 
 + 
 +https://​www.youtube.com/​watch?​v=RWdEQfYZKEs 
 + 
 +Functionalities:​ 
 + 
 +  * Monitor shore power and generator status. 
 +  * Monitor battery status for one or more batteries. By using the voltage of for example battery chargers, it can also visualise secondary batteries such as Generator starter batteries. 
 +  * Monitor the power conversion equipment: chargers, inverters, inverter/​chargers. 
 +  * Monitor AC loads, and DC loads. 
 +  * Control shore power input current limit. 
 +  * Control the inverter/​charger:​ switch it off, on, or set it to charger-only. 
 +  * Optionally open the Victron Remote Console panel; allowing access to further parameters. 
 + 
 +Power equipment compatibility:​ 
 +  * All Victron inverter/​chargers:​ From a 500VA single phase device up to a large 180kVA three phase-system,​ including Multis, Quattros, 230VAC and 120VAC models. 
 +Battery Monitors: BMV-700, BMV-702, BMV-712 and newer, Lynx Shunt VE.Can, Lynx Ion BMS. 
 + 
 +Requirements:​ 
 +  * Battery system. 
 +  * Victron inverter/​charger. 
 +  * Victron Battery monitor. 
 +  * Network cable connection between MFD and a Venus-device such as a Color Control GX, Venus GX or an Octo GX. 
 +  * UTP network cable. 
 + 
 +==== 6.2 Detailed instructions ==== 
 + 
 +  * [[https://​docs.victronenergy.com/​gx/​mfd-garmin.html|Instructions for Garmin MFDs]] 
 +  * [[venus-os:​mfd-navico|Instructions for Navico MFDs]] 
 + 
 +Raymarine: support on Raymarine MFDs is pending a Raymarine firmware update. [[https://​www.victronenergy.com/​blog/​|Subscribe to our blog (link at the bottom)]], or for direct customers, monitor our weekly e-mail, to be informed about that release. 
 + 
 +Furuno: support on Furuno MFDs is in the pipeline. There is no expected date of availability. 
 + 
 +===== 7 More information resources =====
   * [[:​ccgx:​generator_start_stop|CCGX Genset start/​stop]]   * [[:​ccgx:​generator_start_stop|CCGX Genset start/​stop]]
   * [[:​ccgx:​ccgx_faq|CCGX Frequently asked questions]]   * [[:​ccgx:​ccgx_faq|CCGX Frequently asked questions]]
ccgx/start.1554529736.txt.gz · Last modified: 2019-04-06 07:48 by mvader