ccgx:ccgx_faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ccgx:ccgx_faq [2018-11-11 14:09] – mvader | ccgx:ccgx_faq [2021-02-05 11:34] (current) – marmour | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Color Control GX FAQ ===== | + | The content of this page has moved to the CCGX manual. |
- | ==== Q1: I cannot switch my Multi/ | + | |
- | To solve the problem, first find out how the system is connected, and then follow the right step by step instruction below. | + | |
- | There are two ways to connect a Multi/ | + | |
- | === Step by step instructions when connected | + | Please go to the Color Control |
- | - Update | + | |
- | - Do you have a Digital Multi Control or VE.Bus BMS in the system? In that case it is normal that on/off is disabled. See also the VE.Bus related notes in the [[: | + | |
- | - In case you have had a Digital Multi Control or VE.Bus BMS connected to your system, the Color Control remembers it and even when those accessories have been removed the On/off switch will still be disabled. To clear the memory, execute a Redetect system, the option is in the Multi or Quattro section of the Color Control GX menu. | + | |
- | - For parallel/ | + | |
- | === Step by step instructions when connected to CCGX via VE.Can === | ||
- | - Update the Color Control to the latest available version. See our blog posts in the [[https:// | ||
- | - Update the VE.Bus to VE.Can interface to the latest version. The easiest way to do that is by using [[: | ||
- | - Do you have a Digital Multi Control or VE.Bus BMS in the system? In that case it is normal that on/off is disabled. See also the VE.Bus related notes in the [[: | ||
- | - In case you have had a Digital Multi Control or VE.Bus BMS connected to your system, and it is now no longer connected, the Canbus interface remembers it. Therefore, even after those accessories have been removed, the On/off switch will still be disabled. Clearing this memory is unfortunately not possible yourself, please contact us so we can help you. | ||
- | |||
- | ==== Q2: Do I need a BMV to see proper battery state of charge? ===== | ||
- | |||
- | Moved [[https:// | ||
- | |||
- | ==== Q3: I have no internet, where can I insert a sim-card? ==== | ||
- | |||
- | There is no 3G modem in the Color Control, and therefore also no slot for a sim-card. Go to a local store and buy a 3G router with Ethernet ports. More information in the blog post link below and particularly in the comments section, as more users try differing equipment: | ||
- | |||
- | [[https:// | ||
- | |||
- | Note that it is not possible to use a VGR2 or VER for this. Also it will not be possible in the foreseeable future. | ||
- | |||
- | ==== Q4: Can I connect both a Color Control and a VGR2/VER to a Multi/ | ||
- | |||
- | No. Also, instead of this combination, | ||
- | |||
- | ==== Q5: Can I connect multiple Color Controls to a Multi/ | ||
- | |||
- | No. | ||
- | |||
- | |||
- | ==== Q6: I see incorrect current (amps) or power readings on my CCGX ==== | ||
- | Examples are: | ||
- | * I know that a load is drawing 40W from the Multi, but the CCGX shows 10W or even 0W. | ||
- | * I see that the Multi is supplying a load with 2000W, while in inverter mode, but from the battery only 1850W is being taken. Is those 150W coming out of nowhere? | ||
- | |||
- | The general answer is: the Multi and Quattros are not measurement instruments, | ||
- | |||
- | In more detail, there are several causes for measurement inaccuracies: | ||
- | - Part of the power taken from a battery by the inverter is being lost in the inverter, converted into heat: efficiency losses. | ||
- | - The Multi does not really measure the power being drawn from the battery. It measures the current at the output of the inverter, and then makes an assumption of the power being drawn from the battery. | ||
- | - Watts vs VA: depending on the Multi/ | ||
- | - Multis/ | ||
- | - If a current sensor assistant is loaded in a Multi/ | ||
- | - If a current sensor assistant is loaded in a Multi/ | ||
- | - A current sensor assistant measures and reports VAs, not Watts. | ||
- | |||
- | Notes for systems with multiple units in parallel: | ||
- | - Ccgx version prior to v1.20 use the power and current reported by the master of a phase and multiplied that by the number of devices in that phase. Since version v1.20 the values of all device is summed per phase and hence should be more accurate. | ||
- | |||
- | - This revealed a bug for in the firmware of the multi when running in parallel. Ccgx v1.21 workarounds this, by falling back to the original behavior when it sees an affected firmware version. For better readings the multi' | ||
- | |||
- | - Multi firmware versions since 26xx207 / xxxx300 can also freeze the Power values at a certain moment in time. | ||
- | |||
- | Tips to prevent measurement problems: | ||
- | - Do not connect VEConfigure while the CCGX is connected | ||
- | - VE.Bus is not a 100% plug and play system: if you disconnect the CCGX from one Multi, and very quickly connect it to another, it can result it wrong values. To make sure that this is not the case, use the ' | ||
- | |||
- | ==== Q7: There is a menu entry named " | ||
- | A VE.Bus system can be completely turned off, including its communication. If you turn a VE.Bus system off, and thereafter reset the CCGX, the CCGX cannot obtain the detailed product name and shows " | ||
- | |||
- | To get the proper name again, go into the Multi menu on the CCGX and set the Switch menu entry to On or in case a Digital Multi Control is present, set the physical switch to On. Note that when there is a BMS, above procedure only works when within battery working voltages. | ||
- | |||
- | ==== Q8: There is a menu entry named " | ||
- | If a CCGX ever saw a VE.Bus BMS or Digital Multi Control (DMC), it will remember them, until ' | ||
- | |||
- | After a minute, restart the CCGX: Settings -> General -> Reboot. | ||
- | |||
- | |||
- | ==== Q9: When I type the ip-address of the Color Control into my browser, I see a web page mentioning Hiawatha? ==== | ||
- | |||
- | Our plan is to at least run a website where you can change settings and see the current status. If all works out as we would like to, there might come be a fully functional version of the online VRM Portal running locally on the Color Control GX. This allows people without an internet connection, or an intermittent internet connection to have the same features and functionality. | ||
- | |||
- | ==== Q10: I have multiple Solar chargers MPPT 150/70 running in parallel. From which one will I see the relay status in the CCGX menu? ==== | ||
- | |||
- | From a random one. | ||
- | |||
- | ==== Q11: How long should an automatic update take? ==== | ||
- | |||
- | The size of the download typically is around 90MB. After download it will install the files which can take up to 5 minutes. | ||
- | |||
- | ==== Q12: I have a VGR with IO Extender, how can I replace this with a Color Control GX? ==== | ||
- | |||
- | It is not yet possible to replace the IO Extender functionality. | ||
- | |||
- | ==== Q13: Can I use Remote VEConfigure, | ||
- | |||
- | Yes, see [[ccgx: | ||
- | |||
- | ==== Q14: The Blue Power Panel could be powered through the VE.Net network, can I also do that with a Color Control GX? ==== | ||
- | |||
- | No, a Color Control GX always needs to be powered itself. | ||
- | |||
- | ==== Q15: What type of networking is used by the Color Control GX (TCP and UDP ports)? ==== | ||
- | |||
- | Basics: | ||
- | * The Color Control GX needs to get a valid IP address from a DHCP server, including a working DNS server and gateway, or a static IP configuration. | ||
- | * DNS port 53 UDP and TCP | ||
- | * NTP (time sync) UDP port 123 | ||
- | |||
- | VRM Portal: | ||
- | * Data to the VRM Portal is sent via HTTP POST and GET requests to http:// | ||
- | |||
- | Firmware updates: | ||
- | * The CCGX connects to [[https:// | ||
- | |||
- | Remote support (default disabled): | ||
- | * When enabled, an outbound SSH connection to supporthost.victronenergy.com is maintained. The CCGX will try to connect on port 22, 80 and 443, and the first that works is maintained. | ||
- | * Enabling Remote Support also enables the sshd daemon, listening for incoming SSH requests on port 22. See next FAQ entry for more information about the Remote Support functionality. | ||
- | |||
- | Two way communication (Remote VEConfig and Remote Firmware updates): | ||
- | * Uses HTTPS (port 443) to the Pubnub servers | ||
- | |||
- | MQTT (default disabled): | ||
- | * When enabled, a MQTT broker is started, which accepts TCP connections on port 1883. The CCGX will also try to connect to the victron MQTT cloud server (mqtt.victronenergy.com) using SSL on port 8883. | ||
- | |||
- | Remote Console on VRM (default disabled): | ||
- | * 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. No port forwarding in routers is necessary to use Remote Console on VRM. | ||
- | * See [[vrm_portal: | ||
- | |||
- | Remote Console on LAN (default disabled): | ||
- | * Remote Console on LAN requires port 80 (small website hosted on local hiawatha webserver on CCGX). And also requires port 81, which is the listening port for the websocket tunnel to VNC. | ||
- | |||
- | Modbus TCP (default disabled): | ||
- | * ModbusTCP server uses port 502 | ||
- | |||
- | |||
- | ==== Q16: What is the functionality behind the menu item Remote support (SSH), in the Ethernet menu? ==== | ||
- | |||
- | When enabled, the Color Control will open a SSH connection to our secure server, with a reverse tunnel back to the Color Control. Through this tunnel, Victron engineers can login to your Color Control GX and perform remote support. This works when the Color Control GX is installed on an internet connection. The connection will even work when installed behind most firewalls. The SSH connection will be outbound on port 80 to supporthost.victronenergy.com. Remote support function is by default disabled. | ||
- | |||
- | ==== Q17: I don’t see support for VE.Net products in the list, is that still coming? ==== | ||
- | |||
- | No. | ||
- | |||
- | ==== Q18: What is the data usage of the Color Control GX? ==== | ||
- | |||
- | Data usage depends heavily on amount of connected products, and behavior and usage of those products. The measurements below are an indication only, and taken from a system with one Color Control GX, one Multi, one BMV and one MPPT. Log interval set to 15 minutes. If you are on an expensive data-plan, do make some fail-safe. | ||
- | |||
- | Data consumption per month: | ||
- | * VRM logging: 15MB download, 45MB upload | ||
- | * Remote support: 22MB download, 40MB upload | ||
- | * Update checks: 8MB download, 0.3MB upload (This does not include the update itself) | ||
- | * 2 way communication: | ||
- | |||
- | Mentioned megabytes do not include the download of a Color Control firmware update. Firmware updates of 60MB are not uncommon. | ||
- | |||
- | ==== Q19: How many AC Current Sensors can I connect in one VE.Bus system? ==== | ||
- | The current maximum is 9 sensors (since CCGX v1.31). Note that each need to be configured separately with an assistant in the Multi or Quattro to which it is wired. | ||
- | |||
- | ==== Q20: Caution when powering the CCGX 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. See FAQ for more information about this. | ||
- | |||
- | 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: | ||
- | * Power the CCGX from the battery; or | ||
- | * Cut pin 7 in the VE.Bus cable connected to the CCGX | ||
- | |||
- | Cutting/ | ||
- | |||
- | {{: | ||
- | |||
- | The // | ||
- | |||
- | ==== Q21: I love Linux, programming, | ||
- | |||
- | Yes you can! We intend to release almost all code as open source, but we are not that far yet. What we can offer today is that many parts of the software are in script or other non-precompiled languages, such as Python and QML, and therefore available on your Color Control GX and easy to change. Root password and more information is available [[open_source: | ||
- | |||
- | ==== Q22: How do I change the logo ==== | ||
- | |||
- | Typic 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 VENUS device. | ||
- | |||
- | ==== Q23: Multi restarts all the time (after every ~10sec) ==== | ||
- | |||
- | Please check the remote switch connection on the Multi control PCB. There should be a wire bridge between the left and middle terminal. The CCGX switches a line which enables the power of the Multi control board. After 10 seconds this line is released and the Multi should take over from there. When the remote switch connection is not wired the Multi is unable to take over it's own supply. The CCGX will retry, the Multi will boot and after 10 seconds stop, and so on. | ||
- | |||
- | ===== GPL Note ===== | ||
- | |||
- | The software included in this product contains copyrighted software that is licensed under the GPL. You may obtain the Corresponding Source code from us for a period of three years after our last shipment of this product. | ||
- | |||
- | ===== DISQUS ===== | ||
- | |||
- | ~~DISQUS~~ |
ccgx/ccgx_faq.1541941783.txt.gz · Last modified: 2018-11-11 14:09 by mvader