ccgx:start
Differences
This shows you the differences between two versions of the page.
ccgx:start [2019-10-03 13:32] – [5.4 Trouble shooting data logging] mvader | ccgx:start [2023-01-19 15:08] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Color Control GX manual ====== | + | The content |
- | + | ||
- | {{: | + | |
- | + | ||
- | The Color Control GX (CCGX) sits at the heart of your energy installation. All the other system-components - such as inverter/ | + | |
- | + | ||
- | Monitoring can be done either with the CCGX in front of you - or from anywhere in the world using an internet connection and the [[https:// | + | |
- | + | ||
- | 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:// | + | |
- | + | ||
- | 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: | + | |
- | ===== 1. Installation ===== | + | |
- | + | ||
- | ==== 1.1 Overview of connections ==== | + | |
- | {{ : | + | |
- | + | ||
- | ==== 1.2 Snap-on ferrite beads for class B EMI compliance ==== | + | |
- | + | ||
- | In order to reduce Electromagnetic emissions in compliance with class B EMI you should place the provided snap-on ferrite beads around every connection cable as close as possible to the Color Control. | + | |
- | + | ||
- | === HQ1700 and later === | + | |
- | + | ||
- | For serial numbers HQ1700 and later, mount a single snap-on ferrite bead (supplied with the unit) around the power leads like this: | + | |
- | {{: | + | |
- | + | ||
- | === HQ1654 and earlier === | + | |
- | + | ||
- | For serial numbers HQ1654 and earlier, mount the snap-on ferrite beads as below: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== 1.3 Power ==== | + | |
- | + | ||
- | Power the device using the //Power in V+// connector. It accepts 8 to 70 V DC. The device will not power itself from any of the network connections. Be sure to use a 1A slow blow fuse. | + | |
- | + | ||
- | === Powering in systems with VE.Bus BMS === | + | |
- | When the CCGX is used in an installation with a VE.Bus BMS, connect the //Power in V+// on the CCGX to the terminal labelled '// | + | |
- | + | ||
- | === A Cautionary word about Powering from the AC-out terminal of a VE.Bus Inverter, Multi or Quattro: === | + | |
- | If you power the CCGX from an AC adaptor connected to the AC-out port of any VE.Bus product (Inverter, Multi or Quattro), then a deadlock will occur after the VE.Bus products are powered-down for any reason (after any operational fault or during a black start). The VE.Bus devices will not boot-up until the CCGX has power ...but the CCGX will not boot-up until //it// has power. This deadlock can be rectified by briefly unplugging the CCGX VE.Bus cable at which point you will observe the VE.Bus products will immediately begin to boot-up. | + | |
- | + | ||
- | Or a modification can be done to the RJ45 cabling. See | + | |
- | [[ccgx_faq## | + | |
- | + | ||
- | === Isolation === | + | |
- | Because the CCGX is connected to many different products, please ensure that proper care is taken with isolation to prevent ground loops. In 99% of installations this will not be a problem. | + | |
- | + | ||
- | * The VE.Bus ports are isolated | + | |
- | * The VE.Direct ports are isolated | + | |
- | * The VE.Can ports are isolated | + | |
- | * The USB ports are not isolated. Connecting a Wi-Fi Dongle or GPS Dongle will not create a problem as it is not connected to another power supply. Even though there will be ground loop when you mount a separately-powered USB hub, during extensive testing we have not found that it caused any issues. | + | |
- | * The Ethernet port is isolated, except for the shield: use unshielded UTP cables for the Ethernet network | + | |
- | + | ||
- | === Extending USB ports by use of a self-powered USB hub === | + | |
- | Although the number of USB ports can be extended by using a hub, there is a limit to the amount of power that the //onboard USB port// can provide. When extending the number of USB ports, we recommend you always use //powered// USB hubs. And to minimize the chance of issues, be sure to use good-quality USB hubs. As Victron also offers a VE.Direct to USB adapter, you can use this arrangement to increase the number of VE.Direct devices you can connect to your system, [[https:// | + | |
- | + | ||
- | ==== 1.4 Connecting Victron products ==== | + | |
- | + | ||
- | === 1.4.1 Multis/ | + | |
- | + | ||
- | In order to keep this document short we are going to refer to all Multis, Quattros and Inverters as //VE.Bus// products. | + | |
- | + | ||
- | The earliest version of the VE.Bus devices which can be connected to the CCGX is 19xx111 or 20xx111, which were released in 2007. VE.Bus firmware 26xxxxx and 27xxxxx are also supported ...but 18xxxxx is not. | + | |
- | + | ||
- | Note that it is not possible to use the Remote On/Off (header on the VE.Bus control PCB) in combination with a CCGX. There should be wire between the left and middle terminal, as it is when shipped from the factory. In case a wired switch that disables the system is required, use the [[assistants: | + | |
- | + | ||
- | __Single VE.Bus products__\\ | + | |
- | To connect a single VE.Bus product, connect it to one of the VE.Bus sockets on the back of the CCGX. Both sockets are identical, use either one. Use a standard RJ45 UTP cable, see our [[https:// | + | |
- | + | ||
- | __Parallel, split- and three-phase VE.Bus systems__\\ | + | |
- | To connect multiple VE.Bus products, configured as a parallel, split-phase or three phase VE.Bus system, connect either the first or the last VE.Bus product in the chain to either one of the VE.Bus sockets on the back of the CCGX. Use a standard RJ45 UTP cable, see our [[https:// | + | |
- | + | ||
- | Systems consisting of five or more VE.Bus products, connected to a CCGX with serial number HQ1628 or earlier require the ' | + | |
- | + | ||
- | __VE.Bus systems with Lithium batteries and a VE.Bus BMS__\\ | + | |
- | * Connect the CCGX to the socket labelled ‘MultiPlus/ | + | |
- | * Note that it will not be possible to control the On/ | + | |
- | * Combining MultiPlus/ | + | |
- | * To allow auto-power-down in the CCGX in case of a low battery, make sure the CCGX is powered via the VE.Bus BMS: connect //Power in V+// on the CCGX to //Load disconnect// | + | |
- | + | ||
- | __Combining the CCGX with a Digital Multi Control__\\ | + | |
- | + | ||
- | It is possible to connect both a CCGX and a Digital Multi control to a VE.Bus system. The ability to switch the product On, Off or set it to Charger Only via the CCGX will be disabled. The same applies to the input current limit: when there is a Digital Multi Control in the system, the input current limit which is set at that control panel will be the master-setting, | + | |
- | + | ||
- | __Connecting multiple VE.Bus systems to a single CCGX__\\ | + | |
- | + | ||
- | Only one VE.Bus system can be connected to the VE.Bus ports on the back of the CCGX. The professional way to to monitor more systems is to add a second CCGX. | + | |
- | + | ||
- | If you do require to connect more than one system to the same CCGX, use an MK3-USB. Functionality will be limited: | + | |
- | + | ||
- | * Only the system connected to the built-in VE.Bus ports is used to generate the data on the Overview pages. | + | |
- | * All connected systems will be visible on the Device-list | + | |
- | * All connected systems will be taken into account for Energy consumption and distribution calculations (kWh graphs on VRM) | + | |
- | * Only the system connected to the built-in VE.Bus ports is used for the Generator start/stop logic | + | |
- | * The CCGX will not send proper data to VRM any more. The Venus GX does send information of both systems to VRM: its therefor better to use a Venus GX for systems like this. | + | |
- | * In case of an ESS system, only the system connected to the built-in VE.Bus ports is used in the ESS mechanisms. The other one is displayed in the device list only. | + | |
- | + | ||
- | Alternatively the VE.Bus to VE.Can interface (ASS030520105) can be used. Add one for each additional system. Note that we advise against it; this interface is a deprecated product. Make sure that the VE.Can network is terminated and powered. For powering the VE.Can network, see Q17 in our [[https:// | + | |
- | + | ||
- | === 1.4.2 Battery Monitor BMV-700 series; and MPPTs with a VE.Direct port === | + | |
- | Either one or two compatible products can be connected directly on the back of the CCGX using a standard [[https:// | + | |
- | - Straight VE.Direct cables, ASS030530xxx | + | |
- | - VE.Direct cables with an angled connector on one end. These are designed to minimize the required depth behind a panel, ASS030531xxx | + | |
- | + | ||
- | VE.Direct cables have a maximum length of 10 metres. It is not possible to extend them. If longer lengths are required, use the [[https:// | + | |
- | + | ||
- | __Connecting more than two devices to your CCGX using VE.Direct__ | + | |
- | + | ||
- | First of all, note that the maximum of VE.Direct devices that can be connected is 5 for the CCGX. How they are connected, so direct, via USB or via CAN, does not change the maximum. See [[venus-os: | + | |
- | + | ||
- | *Option 1: Use the [[https:// | + | |
- | + | ||
- | *Option 2: The BMV700 and BMV702 | + | |
- | + | ||
- | __Notes about older VE.Direct MPPTs__\\ | + | |
- | * The MPPTs need to run firmware version v1.09 or later. See the Victron Professional website [[https:// | + | |
- | * An MPPT 70/15 needs to be from year/week 1308 or later. Earlier 70/15s are not compatible with the CCGX, and unfortunately upgrading the MPPT firmware will not help. To find the year/week number of your model, look for the serial number which is printed on a label on its back. For example number HQ**1309**DER4F means 2013, week 09. | + | |
- | + | ||
- | + | ||
- | === 1.4.3 Skylla-i, Lynx Shunt VE.Can, Lynx Ion + Shunt and MPPTs with a VE.Can port === | + | |
- | To connect a product with a VE.Can port, use a standard [[https:// | + | |
- | + | ||
- | Don't forget to terminate the VE.Can network at both ends using a [[https:// | + | |
- | + | ||
- | Other notes: | + | |
- | - In order to work with the CCGX an MPPT 150/70 needs run firmware v2.00 or newer. | + | |
- | - You can combine a Skylla-i control panel with a CCGX. | + | |
- | - You can combine a Ion Control panel with a CCGX. | + | |
- | - The Skylla-i, Lynx Shunt VE.Can, Lynx Ion + Shunt and the MPPTs with a VE.Can port all power the VE.Can network ...so it won't be necessary to power the VE.Can network separately in these circumstances. All the protocol converters - for example the VE.Bus to VE.Can interface; and the BMV to VE.Can interface, do not power the VE.Can network. | + | |
- | + | ||
- | === 1.4.4 BMV-600 series === | + | |
- | + | ||
- | Connect the BMV-600 using the VE.Direct to BMV-60xS cable supplied. (ASS0305322xx) | + | |
- | + | ||
- | === 1.4.5 DC Link box === | + | |
- | + | ||
- | Connect the [[https:// | + | |
- | + | ||
- | === 1.2.6 VE.Can Resistive Tank Sender Adapter === | + | |
- | See [[https:// | + | |
- | + | ||
- | To connect a product with a VE.Can port, use a standard [[https:// | + | |
- | + | ||
- | Don't forget to terminate the VE.Can network on both ends using a [[https:// | + | |
- | + | ||
- | Make sure that the canbus is powered, see the [[https:// | + | |
- | + | ||
- | === 1.4.7 NMEA Tank senders from other manufacturers === | + | |
- | + | ||
- | A tank sender must meet the following requirements to be visible on the CCGX: | + | |
- | * Transmit the NMEA2000 Fluid Level PGN, 127505 | + | |
- | * The NMEA2000 device class needs to be ' | + | |
- | * The NMEA2000 function needs to be ' | + | |
- | + | ||
- | Since v2.17 the following functions are accepted as well: | + | |
- | * The NMEA2000 device class ' | + | |
- | * The NMEA2000 device class ' | + | |
- | + | ||
- | A single function reporting multiple Fluid Levels is currently not supported. | + | |
- | + | ||
- | For some tank senders it is also possible to configure the capacity and the fluid type from the CCGX - for example the Maretron TLA100. This facility may be available with other senders made by other manufacturers - it's well-worth trying. | + | |
- | + | ||
- | To connect an NMEA2000 network to the VE.Can port on the CCGX, use a [[https:// | + | |
- | + | ||
- | Alternatively, | + | |
- | + | ||
- | ==== 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. | + | |
- | + | ||
- | Besides monitoring, the GX device can also curtail some types and brands of PV Inverters, ie. reduce their output power. This is used, and required, for the [[ess: | + | |
- | + | ||
- | === Direct connections === | + | |
- | ^ Type ^ Zero feed-in ^ Details ^ | + | |
- | | Fronius | Yes | LAN Connection, see [[ccgx: | + | |
- | | SMA | No | LAN Connection, see [[ccgx: | + | |
- | | SolarEdge | No | LAN Connection, see [[venus-os: | + | |
- | | ABB | Yes | LAN Connection, see [[https:// | + | |
- | + | ||
- | === Using a meter === | + | |
- | + | ||
- | For PV Inverters that cannot be interfaced digitally, a meter can be used: | + | |
- | + | ||
- | ^ Type ^ Zero feed-in ^ Details ^ | + | |
- | | [[https:// | + | |
- | | [[https:// | + | |
- | | Wireless AC sensors | No | See the [[ccgx: | + | |
- | + | ||
- | ==== 1.6 Internet connectivity ==== | + | |
- | + | ||
- | Connect the CCGX to the internet to get all the advantages of the [[http:// | + | |
- | + | ||
- | To monitor this data from your smartphone or tablet download the [[https:// | + | |
- | + | ||
- | In addition to remote monitoring, an active internet connection allows the CCGX to regularly check for a new firmware versions - which will be automatically downloaded and installed. | + | |
- | + | ||
- | There are several ways to connect a CCGX to the internet: | + | |
- | + | ||
- | * Run a network cable between a router and the CCGX Ethernet LAN port | + | |
- | * Connect to a router wirelessly using a USB Wi-Fi dongle plugged into the CCGX | + | |
- | * Via the mobile (cellular) network, using a 3G or 4G router | + | |
- | * [[venus-os: | + | |
- | * USB Tethering on a mobile phone | + | |
- | + | ||
- | This video explains how to connect LAN, WiFi and a GX GSM: | + | |
- | {{youtube> | + | |
- | + | ||
- | The chapters below describe the options in detail. | + | |
- | + | ||
- | === 1.6.1 Ethernet LAN port === | + | |
- | + | ||
- | When you connect an ethernet cable between a router and CCGX, the Settings> | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | === 1.6.2 Wi-Fi USB dongle === | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | * Partno. BPP900100200 - CCGX WiFi module simple (Nano USB), small, low cost. | + | |
- | * Partno. BPP900200300 - [[https:// | + | |
- | + | ||
- | WiFi modules that are no longer available, but still supported, are: | + | |
- | * Partno. BPP900200100 - [[https:// | + | |
- | * Partno. BPP900100100 - [[https:// | + | |
- | * Partno. BPP900200200 - [[https:// | + | |
- | + | ||
- | Although other Wi-Fi dongles may work, they have not been tested and we do not offer support for other dongles. | + | |
- | + | ||
- | The Wi-Fi menu shows the available networks. When a network is selected, it is possible to fill in the password (if the password is not already known) to connect to the network. Setting up via WPS (Wi-Fi Protected Setup) is not supported. | + | |
- | + | ||
- | When the CCGX finds multiple Wi-Fi networks of which the password is known, the strongest network is selected automatically. When the signal of the connected network becomes too weak, it will automatically switch to a stronger network - if it knows the password of that network. | + | |
- | + | ||
- | === 1.6.3 Mobile (cellular) network using a 3G or 4G router === | + | |
- | + | ||
- | To connect the CCGX to a mobile (cellular) network, such as a 3G or 4G network, use a cellular router. Connect the CCGX to that router with either a LAN cable or the router' | + | |
- | + | ||
- | Make sure you use a router that is designed for unattended setups. Do not use low cost consumer-grade routers intended for business or leisure travel. A more expensive professional router will quickly pay for itself, and you won't have wasted journeys simply to perform a re-set. Examples of such professional routers are the [[http:// | + | |
- | + | ||
- | More information in [[https:// | + | |
- | + | ||
- | Note that the CCGX does not support USB 3G/4G dongles. | + | |
- | + | ||
- | === 1.6.4 USB tethering using a mobile phone === | + | |
- | + | ||
- | This is a useful facility when it works - but don't rely on it because it has not proved very dependable. Consult the internet for instructions about tethering for your phone and its particular operating system. We have heard of it working on: | + | |
- | + | ||
- | * Samsung Galaxy S4 | + | |
- | + | ||
- | ...but not on: | + | |
- | + | ||
- | * iPhone 5s with iOS 8.1.1 | + | |
- | + | ||
- | === 1.6.5 IP Configuration === | + | |
- | + | ||
- | Almost no installations will need the IP address configuration | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | Complete details of IP requirements, | + | |
- | + | ||
- | === 1.6.6 Connecting both Ethernet and Wi-Fi (failover) === | + | |
- | + | ||
- | It is possible to connect the CCGX to both Ethernet and Wi-Fi. In this case, the CCGX will try to determine which interface provides an active internet connection and then use that interface. When both have an active internet connection, the Ethernet connection is used. The CCGX will automatically check again for active internet connections when something changes on the interfaces. | + | |
- | + | ||
- | === 1.6.7 Minimize internet traffic === | + | |
- | + | ||
- | In situations where internet traffic is expensive, for example a satellite uplink or with roaming GSM/ | + | |
- | + | ||
- | * Disable auto-update | + | |
- | * Do not enable remote support | + | |
- | * Reduce the Logging interval to a very low frequency. Note that state changes (charging → inverting, or bulk→float) and also alarms will cause extra messages to be sent | + | |
- | + | ||
- | To find out how much data allowance you need to buy the best way is to let the system run for a couple of days and monitor the internet RX and TX counters in your 3G or 4G router. Or even better, some mobile companies will report the data used via a website. \\ | + | |
- | + | ||
- | The amount of data used is also very dependent on the system: | + | |
- | + | ||
- | * More products connected to the CCGX will generate more data. | + | |
- | * A state change (from inverter to charger for example) will trigger a data transmission, | + | |
- | + | ||
- | Note that CCGX versions prior to v1.18 will check for software updates daily even when auto-update is switched off. This was changed in v1.18. Disabling auto-update also disables the check - saving a lot of data. | + | |
- | + | ||
- | We recommend setting-up your data plan in such a way as to avoid costly ' | + | |
- | + | ||
- | One customer - burdened with global costs of between twenty cents and several euros per mb of data - invented a clever solution: Using a VPN he modified the IP to route ALL traffic to and from the CCGX via his VPN. Using a firewall at the VPN server allows him to control traffic according to time, connection type, place and destinations. Although this is beyond the scope of this manual it works, and - with the help of a Linux and networking expert - it can work for you. | + | |
- | + | ||
- | === 1.6.8 More information about setting up an internet connection and VRM === | + | |
- | + | ||
- | * [[: | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[: | + | |
- | + | ||
- | + | ||
- | ==== 1.7 Connecting a USB GPS ==== | + | |
- | + | ||
- | Use a GPS to track remote vehicles or boats and, optionally, get an alarm when they leave a designated area (geofencing). It is also possible to download a gps-tracks.kml file which can be opened with Navlink and Google Earth for example. | + | |
- | + | ||
- | Victron does not sell USB-GPS, but the CCGX will support third-party GPS modules which use the NMEA0183 command-set - almost all do. It can communicate at both 4800 and 38400 baud rates. Plug the unit into either of the two USB sockets ...connection may take a few minutes, but the CCGX will automatically recognize the GPS. The unit's location will automatically be sent to the VRM online portal and its position shown on the map. | + | |
- | + | ||
- | The CCGX has been tested for compatibility with: | + | |
- | + | ||
- | * Globalsat BU353-W SiRF STAR III 4800 baud | + | |
- | * Globalsat ND100 SiRF STAR III 38400 baud | + | |
- | * Globalsat BU353S4 SiRF STAR IV 4800 baud | + | |
- | * Globalsat MR350 + BR305US SiRF STAR III 4800 baud | + | |
- | + | ||
- | ==== 1.8 Connecting a Fischer Panda Generator ==== | + | |
- | + | ||
- | See [[ccgx: | + | |
- | ===== 2 Configuration ===== | + | |
- | + | ||
- | ==== 2.1 Configurable parameters ==== | + | |
- | + | ||
- | After completing the installation and setting up the internet connection (if required), go through the menu from top to bottom to configure the CCGX: | + | |
- | + | ||
- | ^Item ^Default ^Description | | + | |
- | |**General** ||| | + | |
- | |Remote support |Off |Enable this to allow Victron engineers to access your system in case there is a problem. | | + | |
- | |Access level |User and installer |Set this to ' | + | |
- | |Audible alarm |On |When there is an alarm on the CCGX or a connected product, the CCGX will beep - unless this setting is set to ' | + | |
- | |Demo mode |Off |Turn ' | + | |
- | |**Firmware** ||| | + | |
- | |Online updates: Auto update | Check and update | We recommend the factory default. A reason to disable it would be to eliminate the risk of a firmware update causing problems. | + | |
- | |Online updates: Update to |Latest release |Use the default setting unless you want to participate in test versions. End-user systems should certainly be set to ' | + | |
- | |Offline updates || Use this menu to install a new version from a microSD card or USB stick. Insert the card or stick that holds the new firmware .swu file. | | + | |
- | |Stored backup firmware || With this feature you can go back to the previously installed firmware version. | | + | |
- | |**Date & time** ||| | + | |
- | |Date/Time local| Automatic from internet | When connected to the internet, time will be automatically synchronised regardless of this setting. Toggle the setting Manually input the time where no internet connection is present.| | + | |
- | |Change time zone|Select the correct time zone. || | + | |
- | |**Remote console** | | + | |
- | |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: | + | |
- | |Enable on LAN |No|Enabling will allow direct connection to the CCGX by typing it's IP address into a web browser. Only Enable this function on trusted networks. Disable password check, or set password first| | + | |
- | |**System setup** ||| | + | |
- | |AC input 1 |Generator |Select Generator or Grid. (We will shortly be adding the setting 'Shore power' instead of grid.) | | + | |
- | |AC input 2 |Grid |Same choices as above. | | + | |
- | |Battery monitor | Automatic | Select the SOC source. This function is useful where there is more than one BMV. [[ccgx: | + | |
- | |Synchronize VE.Bus SOC with battery||Continuously copies the SOC from the battery monitor to the VE.Bus system. This feature is automatically enabled when the active SOC source is not a VE.Bus device, and there is no Hub-2 Assistant configured. The purpose of this is to be able to use the BMV SOC to trigger some Multi or Quattro features - such as Genset start/stop. Multis and Quattro' | + | |
- | |Use solar charger current to improve VE.Bus SOC||Send the total charge current from all connected Solar chargers to the VE.Bus device to improve its SOC computations. This feature is automatically active when ' | + | |
- | |Solar charger voltage control||Use the ' | + | |
- | |Solar charger current control||Limit the charge current of the connected solar chargers if a CAN.bus BMS is present - using the //maximum charge current// information provided by the BMS.| | + | |
- | |Has DC system |No |Enable this for boats, vehicles and installations with DC loads and chargers - in addition to Multi and MPPT chargers. This won't be applicable to most off-grid installations; | + | |
- | |**Display & language** ||| | + | |
- | |Brightness | Configure the brightness between 0 and 100%|| | + | |
- | |Display off time | Set time-to-off between 10s / 30s - 1m / 10m /30m - or never|| | + | |
- | |Show mobile overview | No |Enable this to show the mobile overview page which is designed for Marine and Remote Vehicle applications. This overview gives direct access to the AC Current limit as well as the // | + | |
- | |Language |English |Choose between English, Dutch, Chinese, German, Spanish, French, Italian, Swedish, Turkish and Arabic. | | + | |
- | |**VRM online portal** ||| | + | |
- | |Log to |Internet |Choose between //no logging//, //logging via the internet// directly to the VRM Portal, and //logging to a microSD card or USB flash drive//. See chapter 2.2 below for more information. | | + | |
- | |Log interval |15 minutes |Set to anything between 1 minute and 1 day. Choose longer times on systems with an unreliable connection. Note that this setting does not affect reporting problems and state changes (bulk → absorption) to the VRM Portal. These events initiate an immediate transmission of all parameters. | | + | |
- | |**Wireless AC Sensors** ||| | + | |
- | |Select the position for each AC sensor (PV Inverter on AC-input 1, 2 or on AC-output). [[: | + | |
- | |**Energy meters**||| | + | |
- | |Configure the Energy meters, used for one of three things: \\ Measure the output of a PV Inverter \\ Measure and regulate a [[system_integration: | + | |
- | |**ESS**||| | + | |
- | |Configure Energy storage system (ESS) [[ess: | + | |
- | |**Hub-4**||| | + | |
- | |Configure Hub-4 system [[system_integration: | + | |
- | |**Ethernet** ||| | + | |
- | |Select the configuration type (DHCP vs. manual configuration) and IP settings. ||| | + | |
- | |**Wi-Fi** ||| | + | |
- | |Manage wireless networks and IP settings. ||| | + | |
- | |**GPS** ||| | + | |
- | |Format |Select the format in which to show the Latitude and Longitude. || | + | |
- | |Speed unit |km/h |Choose between km/h, meters per second, miles per hour, or knots. | | + | |
- | |**Generator start/ | + | |
- | |Configure generator autostart settings and conditions. [[ccgx: | + | |
- | |**Tank pump** ||| | + | |
- | |Configure automatic starting and stopping of pump based on tank level(sender) information. [[ccgx: | + | |
- | |**Relay** ||| | + | |
- | |Function |Alarm relay |Select the relay function. Possible functions are 'Alarm relay', | + | |
- | |Polarity |Normally open |Select the polarity of the relay on the back of the CCGX. ' | + | |
- | |**Services** ||| | + | |
- | |ModbusTCP |Off |This setting enables the ModbusTCP service. More information about ModbusTCP in this document: [[https:// | + | |
- | |VRM two-way communication|No| Enable remote configuration and firmware updates. [[ccgx: | + | |
- | + | ||
- | + | ||
- | When using a VE.Bus system, it is possible to configure the severity of problems on the VE.Bus system that should cause a notification to show up on the CCGX (and make it beep): | + | |
- | + | ||
- | * Disabled: The CCGX will never beep or show a notification | + | |
- | * Alarm only: The CCGX will only beep and a show a notification when the VE.Bus system switched off in an alarm condition. | + | |
- | * Enabled (default): The CCGX will beep and show a notification | + | |
- | + | ||
- | When all done, don't forget to change the access level to user when required. | + | |
- | + | ||
- | Click the thumbnail below to see the complete menu-tree: | + | |
- | + | ||
- | {{: | + | |
- | ==== 2.4 Battery State of Charge (SOC) ==== | + | |
- | + | ||
- | === 2.4.1 Which device should I use for SOC calculation? | + | |
- | There are three products types that calculate State Of Charge (SOC). The CCGX itself does not calculate SOC, it only retrieves it from the connected devices. | + | |
- | + | ||
- | The three products that calculate SOC are: | + | |
- | + | ||
- | - Battery Monitors, such as the BMVs, the Lynx Shunt, or the Lynx Ion BMS | + | |
- | - Multi and Quattro inverter/ | + | |
- | - Batteries with built-in battery monitor and a (mostly CAN bus) connection to the CCGX. | + | |
- | + | ||
- | __When to use what?__ | + | |
- | + | ||
- | If you have a battery with build-in battery monitor, such as a BYD or Freedomwon battery; its easy. Use that. | + | |
- | + | ||
- | If not, then the options depend on the type of system: | + | |
- | + | ||
- | 1. If the MultiPlus or Quattro inverter/ | + | |
- | + | ||
- | 2. If the systems consists of an inverter/ | + | |
- | + | ||
- | 3. For any other system types, such as a boat or vehicle with DC lights and other loads, a dedicated battery monitor will be required. | + | |
- | + | ||
- | + | ||
- | === 2.4.2 The different solutions explained in detail === | + | |
- | + | ||
- | __(A) Battery and Multi or Quattro (a typical backup system)__ | + | |
- | + | ||
- | No battery monitor is required: the Multi or Quattro is the only product connected to the battery and has full control over all charge and discharge currents. Therefore it can calculate the correct SOC itself. | + | |
- | + | ||
- | Configuration: | + | |
- | + | ||
- | - Enable and configure the Battery Monitor in VEConfigure. | + | |
- | - In the CCGX, in Settings -> System setup, verify the selected Battery Monitor. It should be set to the Multi or Quattro. | + | |
- | + | ||
- | __(B) Battery with Multi or Quattro and MPPT Solar Chargers__ | + | |
- | + | ||
- | No battery monitor is required, as long as all MPPT Solar Chargers are //Victron// products and are connected to the CCGX. The CCGX will continuously read the actual charge current from all solar chargers, and send the total to the Multi (or Quattro) which then uses that information in its SOC calculations. | + | |
- | + | ||
- | Configuration: | + | |
- | + | ||
- | - Enable and configure the Battery Monitor in VEConfigure. | + | |
- | - On the CCGX, in Settings -> System setup, verify the selected Battery Monitor. It should be the Multi or Quattro. | + | |
- | - In the same menu, verify that the option 'Use solar charger current to improve VE.Bus SOC' is enabled. Note that this is not a setting - it just an indicator of an automatic process. | + | |
- | + | ||
- | Note that this feature requires recent firmware versions in both the Multis or Quattros (402 minimum), and the CCGX (v2.06 minimum). | + | |
- | + | ||
- | + | ||
- | __(C) Batteries with a built-in battery monitor__ | + | |
- | + | ||
- | In cases where the system includes a battery which has a built-in battery monitor and SOC calculation - such as many of the batteries listed [[battery_compatibility: | + | |
- | + | ||
- | Configuration: | + | |
- | + | ||
- | - Connect the battery communications cable to the CCGX according to the instructions. | + | |
- | - In the CCGX, in Settings -> System setup, verify that the selected Battery Monitor is the battery. | + | |
- | + | ||
- | Note that the //Battery Monitor// setting in VEConfigure3 is irrelevant. For systems like this, changing this setting will have no effect on the charge or any other parameters in this type of system. | + | |
- | + | ||
- | __(D) Other system types__ | + | |
- | + | ||
- | When there are more chargers, or loads, connected to the battery than just the Multi or MPPT Solar Chargers, a dedicated Battery Monitor will be required. Examples are: | + | |
- | + | ||
- | * House loads in Marine or Vehicle system. | + | |
- | * PWM Solar Chargers | + | |
- | * AC chargers, such as Skylla-is, Phoenix chargers, non Victron chargers, etc. | + | |
- | * Alternators | + | |
- | * DC-DC chargers | + | |
- | * Wind turbines | + | |
- | * Hydro turbines | + | |
- | + | ||
- | In case a battery with built-in monitor is used, such as explained in (C), then that is the dedicated battery Monitor. Refer to section (C). | + | |
- | + | ||
- | Otherwise, install a BMV or Lynx Shunt VE.Can. | + | |
- | + | ||
- | Configuration: | + | |
- | + | ||
- | - Configure the battery monitor as per its documentation. | + | |
- | - In the CCGX, in Settings -> System setup, verify the selected Battery Monitor. It should be the BMV or Lynx Shunt Battery Monitor. | + | |
- | - Finished. | + | |
- | + | ||
- | Note that the //Battery Monitor// setting in VEConfigure3 is irrelevant. For systems like this, changing this setting will have no effect on the charge - or any other parameters - in this type of system. | + | |
- | + | ||
- | === 2.4.3 Notes === | + | |
- | * Note that this is all about showing an accurate state of charge to the user, rather than being required for an efficient system. The SOC percentage is not used for battery charging. It is, however, required when a generator needs to be started and stopped automatically based on battery SOC. | + | |
- | * For hub-2 installations we recommend you do **not** add a BMV to the system as it will only confuse the user when there are two SOCs with different readings being displayed. | + | |
- | + | ||
- | More information: | + | |
- | * [[vrm_portal: | + | |
- | * [[ccgx: | + | |
- | + | ||
- | === 2.4.4 Selecting SOC source === | + | |
- | + | ||
- | (Settings -> System Setup -> Battery monitor) | + | |
- | + | ||
- | In the image below you can see a range of selectable choices for the SOC values which are shown in the main Overview screen. Choose the source you want to see on the main Overview screen of your CCGX. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | In the image above we have chosen the // | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | The ' | + | |
- | + | ||
- | - When available, it will use a dedicated Battery Monitor, such as the BMV or a Lynx Shunt, or a battery with built-in battery monitor. | + | |
- | - When there is more than one of those connected, it will use a random one - although you can select one manually. | + | |
- | - when there is no dedicated Battery Monitor, it will use the VE.Bus SOC. | + | |
- | + | ||
- | + | ||
- | When should I use the 'No battery monitor' | + | |
- | + | ||
- | Use that in systems where: | + | |
- | + | ||
- | - there is a Multi or Quattro installed | + | |
- | - no BMV or other battery monitor is installed | + | |
- | - the system has other DC loads, or other chargers, connected to the same battery, which are not connected to the CCGX. | + | |
- | + | ||
- | A short explanation: | + | |
- | + | ||
- | === 2.4.5 Details on VE.Bus SOC === | + | |
- | + | ||
- | * While the Inverter/ | + | |
- | + | ||
- | ==== 2.5 Customize the logo on the Boat & Motorhome page ==== | + | |
- | + | ||
- | It is possible to use a custom logo onto the Boat & Motorhome page. | + | |
- | + | ||
- | Type the following address into the web browser of a device connected to the same network. Using this address as a template: | + | |
- | http:// | + | |
- | 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 GX device. | + | |
- | + | ||
- | ===== 3 VE.Bus Inverter/ | + | |
- | + | ||
- | ==== 3.1 Input current-limiter setting ==== | + | |
- | + | ||
- | === ' | + | |
- | This chapter explains the implications of enabling or disabling user control of the input current-limiter setting, as seen here in the menu: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | The limit as set by the user in the CCGX will be applied to all inputs where ' | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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// ' | + | |
- | + | ||
- | === 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) | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | Also the // | + | |
- | + | ||
- | 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, | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | The '' | + | |
- | + | ||
- | On the GX device itself, the warning will be popup as a notification on the GUI: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | Also, it is visible in the menus: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | And on the VRM Portal, it is visible on the VE.Bus Alarms & warnings widget on the Advanced page: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | And also it will be listed in the Alarm Log on VRM, and an email will be sent; using [[: | + | |
- | + | ||
- | + | ||
- | + | ||
- | ===== 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/ | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | 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 // | + | |
- | + | ||
- | === 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 difficulty, the first action is to update firmware. | + | |
- | + | ||
- | Required minimum firmware versions: | + | |
- | * Multi/ | + | |
- | * MultiGrid: 424 | + | |
- | * CCGX / Venus GX: v2.12 | + | |
- | * VE.Direct MPPTs: v1.29 | + | |
- | * VE.Can MPPT Solar Chargers cannot be used: they do not yet support the new control mechanisms. | + | |
- | * Lynx Ion + Shunt: v2.04 | + | |
- | * Lynx BMS: v1.09 | + | |
- | + | ||
- | In case of an ESS System, the ESS Assistant needs to be version 164 or later (Released in November 2017). | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | ==== 4.3 DVCC effects on the charge algorithm ==== | + | |
- | + | ||
- | Our inverter/ | + | |
- | + | ||
- | In certain systems, the internal charge algorithm is disabled, and the charger is then working with an externally controlled charge voltage target. | + | |
- | + | ||
- | This guide explains the different possibilities: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | === Internal === | + | |
- | + | ||
- | The internal charge algorithm (bulk -> absorption -> float -> re-bulk), and the configured charge voltages are active. | + | |
- | + | ||
- | Inverter/ | + | |
- | + | ||
- | 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" | + | |
- | + | ||
- | === Inverter/ | + | |
- | + | ||
- | The MPPTs internal charge algorithm is disabled; instead it's being controlled by a charge voltage setpoint coming from the inverter/ | + | |
- | + | ||
- | MPPT indicated charge state: Ext. control. | + | |
- | + | ||
- | === Battery === | + | |
- | + | ||
- | The internal charge algorithm is disabled; and instead, the device is being controlled by the battery. | + | |
- | + | ||
- | Inverter/ | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | This setting is available in the " | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | 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 Amps, and DC Loads drawing 20 Amps, the battery will be charged with 30 Amps. Not with the full allowed 50 Amps. | + | |
- | + | ||
- | 4) Current drawn from the system by the inverter/ | + | |
- | + | ||
- | 5) 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/ | + | |
- | + | ||
- | === 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 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. | + | |
- | + | ||
- | === 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 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. | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | See previous chapter, “Limit charge current”, the user setting, for details about how the Maximum charge current is used, how it prioritises solar and more. | + | |
- | + | ||
- | 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 '' | + | |
- | * 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 '' | + | |
- | * Add Auto-recharge feature for the ESS Modes '' | + | |
- | * ESS improved state display: In addition to the charger states (Bulk/ | + | |
- | * #1: Low SOC: discharge disabled | + | |
- | * #2: BatteryLife is active | + | |
- | * #3: Charging disabled by BMS | + | |
- | * #4: Discharging disabled by BMS | + | |
- | * #5: Slow Charge in progress (part of BatteryLife, | + | |
- | * #6: User configured a charge limit of zero. | + | |
- | * #7: User configured a discharge limit of zero. | + | |
- | + | ||
- | + | ||
- | ===== 5. VRM Portal ===== | + | |
- | + | ||
- | ==== 5.1 VRM Portal Introduction ==== | + | |
- | + | ||
- | When connected to the internet, a GX device can be used in combination with the [[https:// | + | |
- | * 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: | + | |
- | + | ||
- | 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: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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 '' | + | |
- | - 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:// | + | |
- | - Login, and then click the ' | + | |
- | - 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 === | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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.4 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:// | + | |
- | + | ||
- | Note that the CCGX does not support a proxy setup. For more details on the required networking, see [[https:// | + | |
- | + | ||
- | + | ||
- | === Step 1: Update the GX Device to the latest available firmware === | + | |
- | [[ccgx: | + | |
- | + | ||
- | === Step 2: Verify the network and internet connection === | + | |
- | + | ||
- | 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 | + | |
- | + | ||
- | For a GX GSM, see the [[https:// | + | |
- | + | ||
- | 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__ | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | When using Ethernet and State shows ' | + | |
- | + | ||
- | __WiFi__ | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | When using Wi-Fi and the menu shows 'No Wi-Fi adapter connected' | + | |
- | + | ||
- | When using Wi-Fi and the State shows ' | + | |
- | + | ||
- | + | ||
- | === Step 3. Verify VRM Portal Connectivity === | + | |
- | + | ||
- | Navigate to Settings → VRM online portal, and check the Connection error status: | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | 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: {{ : | + | |
- | * 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. {{ : | + | |
- | + | ||
- | Check 'Last contact' | + | |
- | + | ||
- | The ' | + | |
- | + | ||
- | ==== 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, | + | |
- | + | ||
- | ==== 5.6 Remote Console on VRM ==== | + | |
- | + | ||
- | This feature allows full remote control of a GX Device, over the internet: | + | |
- | {{ : | + | |
- | + | ||
- | 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: | + | |
- | {{ : | + | |
- | + | ||
- | 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:// | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | ===== 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:// | + | |
- | + | ||
- | 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/ | + | |
- | * Monitor AC loads, and DC loads. | + | |
- | * Control shore power input current limit. | + | |
- | * Control the inverter/ | + | |
- | * Optionally open the Victron Remote Console panel; allowing access to further parameters. | + | |
- | + | ||
- | Power equipment compatibility: | + | |
- | * All Victron inverter/ | + | |
- | Battery Monitors: BMV-700, BMV-702, BMV-712 and newer, Lynx Shunt VE.Can, Lynx Ion BMS. | + | |
- | + | ||
- | Requirements: | + | |
- | * Battery system. | + | |
- | * Victron inverter/ | + | |
- | * Victron Battery monitor. | + | |
- | * Network cable connection between MFD and a GX device such as a Color Control GX, Venus GX or an Octo GX. | + | |
- | * UTP network cable. | + | |
- | + | ||
- | ==== 6.2 Compatible MFDs and instructions ==== | + | |
- | + | ||
- | * [[https:// | + | |
- | * [[venus-os: | + | |
- | + | ||
- | Raymarine: support on Raymarine MFDs is pending a Raymarine firmware update. [[https:// | + | |
- | + | ||
- | Furuno: support on Furuno MFDs is in the pipeline. There is no expected date of availability. | + | |
- | + | ||
- | ===== 7 More information resources ===== | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[ccgx: | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[https:// | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[: | + | |
- | * [[open_source: | + | |
- | + | ||
- | + | ||
- | ===== DISQUS ===== | + | |
- | ~~DISQUS~~ | + | |
+ | Please go to your product on our [[https:// |
ccgx/start.1570102339.txt.gz · Last modified: 2019-10-03 13:32 by mvader