Thank you for choosing the Color Control Gateway transmitter (CCGX). It sits at the heart of your energy installation allowing you to view both live and archived data; change settings; instigate powerful functions; tailor your system to your needs; and to ensure that all the components of your system are working together, optimally.
All this can be done either with the CCGX in front of you - or from anywhere in the world using an internet connection, together with the VictonConnect application.
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/
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.
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.
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 'Load disconnect' on the VE.Bus BMS. Connect both negative leads to the negative stub of a common Battery.
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.
This deadlock can be avoided in two ways:
Cutting pin 7 of the VE.Bus cable to the CCGX (brown/white according to standard RJ45 ethernet cable colour coding) allows the VE.Bus products to start up without waiting for the CCGX to boot up first.
The disadvantage of cutting pin 7 is that switching the VE.Bus device off will be less effective: although it will stop charging and inverting, it will still be in standby mode and therefore drawing more current from the battery than if pin 7 had been left in place. Typically this is only relevant in Marine or Automotive systems where it's normal to regularly switch the VE.Bus device off. For those types of systems we recommend that you do not cut pin 7, but simply power the CCGX from the battery.
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.
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.
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.
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 pricelist.
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 pricelist.
Systems consisting of five or more VE.Bus products, connected to a CCGX with serial number HQ1628 or earlier require the 'CCGX dongle for large VE.Bus systems (Product Number: BPP900300100).
VE.Bus systems with Lithium batteries and a VE.Bus BMS
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, and changing it on the CCGX will not be possible.
Connecting multiple VE.Bus systems to a single CCGX
Only one VE.Bus system can be effectively 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 intend to connect more than one system to the same CCGX, use one VE.Bus to VE.Can interface (ASS030520105) for each additional system. Note that the VE.Can network needs to be terminated and powered. For powering the VE.Can network, see Q17 in our data communication whitepaper.
You may wonder if it is possible to use a USB-MK2 or USB-MK3 to connect the second system …but unfortunately that is not possible.
Either one or two compatible products can be connected directly on the back of the CCGX using a standard VE.Direct cable. There are two types of VE.Direct cable available:
VE.Direct cables have a maximum length of 10 metres. It is not possible to extend them. If longer lengths are required, use the VE.Direct to VE.Can interface. Note that this is only works for BMV700 and BMV702. Not for the BMV712, MPPT solar chargers and Inverters with a VE.Direct port. See next paragraph for more information on that VE.Can interface.
Connecting more than two devices to your CCGX using VE.Direct
The maximum number of VE.Direct devices that can be connected is 5. This is achieved by having two devices on a direct connection, and a maximum of three connected via USB.
From version 2.12 of the firmware the number is increased to 8 devices.
Notes about older VE.Direct MPPTs
To connect a product with a VE.Can port, use a standard RJ45 UTP cable. (Available with straight and elbow connectors)
Connect the BMV-600 using the VE.Direct to BMV-60xS cable supplied. (ASS0305322xx)
Connect the DC Link box, using the RJ-12 cable supplied. Then connect the BMV-700 to the CCGX - see 1.2.2 above for instructions.
See its page and manual on our website for details about the Adapter.
To connect a product with a VE.Can port, use a standard RJ45 UTP cable.
Don't forget to terminate the VE.Can network on both ends using a VE.Can terminator. A bag with two terminators is supplied with each VE.Can product. They are also available separately (ASS030700000). (Available with straight or elbow connectors.)
Make sure that the canbus is powered, see the Power chapter in the Tank Sender Adapter manual for details.
A tank sender must meet the following requirements to be visible on the CCGX:
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 VE.Can to NMEA2000 cable.
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.
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.
There are several ways to show the output of a PV Inverter:
Connect the CCGX to the internet to get all the advantages of the VRM Portal. The CCGX sends data from all connected products to the VRM portal - from where you can monitor energy usage, view the current status of connected products, configure email alarms and download data in CSV and Excel formats.
To monitor this data from your smartphone or tablet download the iOS or Android VRM App.
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:
The four chapters below describe these options in detail.
When you connect an ethernet cable between a router and CCGX, the Settings>Ethernet page of your CCGX will confirm connection.
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:
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.
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's Wi-Fi network.
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 H685 4G LTE from Proroute, as well as the Industrial 4G router range from Pepwave.
More information in this blogpost.
Note that the CCGX does not support USB 3G/4G dongles.
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:
…but not on:
Almost no installations will need the IP address configuration to be inserted manually as most systems support automatic IP configuration (DHCP) - and that is also the CCGX default setting. If you do need to configure the address manually, select the following template:
Complete details of IP requirements, as well as used port numbers will be found in the VRM FAQ - ports and connections used by the CCGX.
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.
In situations where internet traffic is expensive, for example a satellite uplink or with roaming GSM/cellular charges, you may want to minimize the internet traffic. The steps to take are:
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:
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 'excess' charges. Make sure you put a cap on your data usage; or use a pre-paid plan.
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.
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:
After completing the installation and setting up the internet connection (if required), go through the menu from top to bottom to configure the CCGX:
|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 'User' to prevent accidental and unwanted changes to the configuration.|
|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 'Off'.|
|Demo mode||Off||Turn 'On' to demonstrate product and installation features to a client or at an exhibition. This simulation mode will allow better understanding without (yet) changing any settings.|
|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 'Latest release'.|
|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.|
|Disable password check||Password authentication not required for remote consul 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. Trouble shooting Remote Console on VRM|
|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.|
|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. More details.|
|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's don't use the SOC for any other purpose. More information|
|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 'Synchronize VE.Bus SOC with battery' is not active. Requires Multi Firmware version >= 402. More information|
|Solar charger voltage control||Use the 'charge voltage' information provided by the VE.Bus device to control the amount of power fed from solar chargers back to the grid. Active if the ESS or Hub-1 assistant is present. (See also: 'Feed-in excess solar charger power' in the ESS settings.)|
|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; and any discrepancy between the DC current measured by the Multi, and by the BMV, will be attributed to a 'DC system'. This may be power-in from an alternator, or power-out from a pump, for example. Note that the value shown will always be an approximation. (In order make these changes in the system setup page, you have to change the access level to User & installer. The initial password is “zzz”)|
|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 On/Off/Charger-only settings and pump control. Also shows up to four tank levels.|
|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). More information about the Wireless AC sensors.|
|Configure the Energy meters, used for one of three things:
Measure the output of a PV Inverter
Measure and regulate a Hub-4 system
Measure and regulate a ESS system
Measure the output of an AC Generator.
|Configure Energy storage system (ESS) ESS system.|
|Configure Hub-4 system Hub-4 system.|
|Select the configuration type (DHCP vs. manual configuration) and IP settings.|
|Manage wireless networks and IP settings.|
|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.|
|Configure generator autostart settings and conditions. Generator auto start/stop on CCGX and Venus GX|
|Configure automatic starting and stopping of pump based on tank level(sender) information. Pump auto start/stop with Color Control GX|
|Function||Alarm relay||Select the relay function. Possible functions are 'Alarm relay', 'Generator start/stop', 'Tank pump' and 'None' (disabled).|
|Polarity||Normally open||Select the polarity of the relay on the back of the CCGX. 'Normally open' or 'Normally closed'. (Note that setting it to normally closed increases the CCGX power draw.)|
|ModbusTCP||Off||This setting enables the ModbusTCP service. More information about ModbusTCP in this document: https://www.victronenergy.com/upload/documents/Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|
|VRM two-way communication||No||Enable remote configuration and firmware updates. VE Power Setup manual|
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):
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:
The CCGX can be used in combination with the 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:
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:
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.
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 'Overruled by remote', configured with VEConfigure, is enabled:
Using the example of a boat with two AC inputs and a Quattro where:
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.)
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:
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.
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).
The configured input limit is the total limit per phase.
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:
For some systems types it is necessary to use a dedicated battery monitor, such as a BMV or Lynx Shunt VE.Can. For other systems it is not necessary.
Explaining the different system types one by one:
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.
Battery with Multi or Quattro and MPPT Solar Chargers -ALSO- An EasySolar with CCGX built-in
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.
Note that this feature requires recent firmware versions in both the Multis or Quattros (402 minimum), and the CCGX (v2.06 minimum).
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 here - a dedicated battery monitor is not required.
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.
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:
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.
(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 Automatic setting. When automatic is selected the System setup screen will be as shown in the image below.
The 'Automatic' function uses the following logic:
When should I use the 'No battery monitor' option?:
Use that in systems where:
A short explanation: the VE.Bus SOC as determined by the Multi or Quattro will be incorrect in above situation. As it will not take the discharge and charge currents by those other DC Loads, and also unmonitored chargers, into account.
With DVCC enabled, the Venus-device takes a more central role in the Victron system, improving and changing system behaviour.
Enabling and disabling DVCC:
Required minimum firmware versions:
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.
Do not use DVCC in cases where these requirements are not met.
Important: Where batteries are connected via CAN-bus, check the relevant page on the Battery Compatibility manual to see if enabling DVCC has been tested with your battery-type, and is OK. If DVCC is not mentioned in notes relating to your battery, do not enable DVCC.
For 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.
Minimum firmware for the Lynx Ion + Shunt
Below features apply to all types of systems, and all types of batteries. Both lead batteries and batteries with a CAN-bus BMS.
These features apply to all types of systems (ESS and not ESS), that have a CAN-bus BMS connected battery.
ESS-modeis set to
Optimizedin combination with the
Feed-in excess solar charger power-setting enabled, or when
ESS-modeis set to
Keep batteries charged.
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. See chapter 4 for more information.
Sustainmodes were added. In addition it also shows reasons for the state it is in: