Differences

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

--- ccgx:ccgx_faq [2018-10-16 21:53] – mvader
+++ ccgx:ccgx_faq [2020-10-15 10:33] – [Q15: What type of networking is used by the Color Control GX (TCP and UDP ports)?] ictbeheer
@@ Line 1: / Line 1: @@
 ====== Color Control GX FAQ =====
-==== Q1: I cannot switch my Multi/Quattro system on or off from the CCGX =====
+==== Q1: I cannot switch my Multi/Quattro system on or off =====
 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/Quattro system to a Color Control GX. In most systems they will be connected directly to the VE.Bus port on the back of the CCGX. And, option two, in some systems they are connected to the Color Control GX using a [[https://www.victronenergy.com/accessories/ve-can-to-ve-bus-interface|VE.Bus to VE.Can interface]].
 === Step by step instructions when connected to VE.Bus port on the CCGX ===
-  - Update the Color Control to the latest available version. See our blog posts in the [[https://www.victronenergy.com/blog/category/firmware/|firmware category]].
+  - Update the Color Control to the latest available version. See our blog posts in the [[https://www.victronenergy.com/blog/category/firmware-software/]].
   - 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 [[:ccgx:start#connecting_victron_products|CCGX manual]]
   - 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.
@@ Line 15: / Line 15: @@
   - 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 [[:ccgx:start#connecting_victron_products|CCGX manual]]
   - 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? =====
@@ Line 75: / Line 74: @@
-==== 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? ====
@@ Line 107: / Line 104: @@
 VRM Portal:
-  * Data to the VRM Portal is sent via HTTP POST and GET requests to http://ccgxlogging.victronenergy.com on port 80. Sensitive data is sent using HTTPS on port 443 to the same host.
+  * Data to the VRM Portal is sent via HTTP POST and GET requests to https://ccgxlogging.victronenergy.com on port 443, with a user configurable override to use plain HTTP on port 80. Note that, even when configured to use plain HTTP, some outgoing requests will always use HTTPS on port 443.
 Firmware updates:
-  * The CCGX connects to [[https://updates.victronenergy.com/|http://updates.victronenergy.com/]] on port 443.
+  * The CCGX connects to [[https://updates.victronenergy.com/|https://updates.victronenergy.com/]] on port 443.
 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.
+  * When enabled, an outbound SSH connection to supporthosts.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.
+  * Enabling Remote Support also enables the sshd daemon, listening for incoming SSH requests on port 22. See below 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
+   * Pre-v2.20: Uses HTTPS (port 443) to the Pubnub servers
+   * v2.20 and later: connects to mqtt-rpc.victronenergy.com on port 443
 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.
+   * When enabled, a local MQTT broker is started, which accepts TCP connections on port 1883. The CCGX will also try to connect to a victron MQTT cloud server  ranging from mqtt0.victronenergy.com to mqtt127.victronenergy.com), on port 443, using SSL. It uses port 443 to reduce the chance of using blocked outgoing ports.
 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.
+  * Remote Console on VRM uses the same reverse ssh tunnel as is used for Remote Support: outbound connection to supporthosts.victronenergy.com on port 22, 80 or 443. No port forwarding in routers is necessary to use Remote Console on VRM. Note that supporthosts.victronenergy.com resolves to multiple IP addresses: 84.22.108.49, 84.22.107.120, 3.25.10.245, 13.244.154.199 or 35.165.124.40, depending on where you are.
-  * See [[vrm_portal:troubleshooting_ccgx_vrm_connectivity#trouble_shooting_remote_console_on_vrm|here]] to trouble shoot Remote Console on VRM.
+  * Remote console also relies on the data connection to the VRM portal using HTTPS (port 443), as describe above.
+  * For troubleshooting, refer to the [[https://www.victronenergy.com/live/ccgx:start#remote_console_on_vrm_-_trouble_shooting|Remote Console on VRM trouble shooting guide]].
 Remote Console on LAN (default disabled):
@@ Line 135: / Line 134: @@
 ==== 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.
+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 a firewall. The SSH connection will be outbound, to port 80, 22 or 443 at 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? ====
@@ Line 156: / Line 155: @@
 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 ====
+==== Q20: Issues with Multi not starting when CCGX is connected / 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.
+NOTES:
+  - We recommend to power a GX device from the battery. Not from the AC-out. In case you still power it from AC-out, carefully read this FAQ item.
+  - This FAQ item applies to Venus GX, CCGX, and all other GX Devices, but not the Cerbo GX. It has an improved design due to which its no longer recommended to cut pin 7 of the VE.Bus cable when powering the GX device on the AC-out port.
+  - Make sure that the GX device and MultiPlus is running the latest firmware version.
+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 can 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.
@@ Line 166: / Line 171: @@
 Cutting/Removing 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.
+Note that when using a Redflow ZBM2/ZCell battery, pin 7 should be cut even if the CCGX is DC powered, to avoid the same deadlock at times when the Redflow battery cluster is at 0% SoC.
 {{:ccgx:ccgx_pin7.jpg?direct&400|}}
@@ Line 174: / Line 181: @@
 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:start|here]].
+==== 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://[ip-here]/logo.php  (inserting your device’s IP address between the square brackets).
+The IP address can be found by going to Settings > Ethernet or Wifi. Once the page is loaded, Choose an image file from your device. Re-boot the [[venus-os:start|GX 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.
+==== Q24: What is Error #42? ====
+If the GX Device shows an Error 42 - Hardware fault. In that case, the flash storage on the device is corrupt. As a result, settings will not be saved (rebooting resets back to default) and other problems will rise.
+This error is not recoverable in the field or by repair departments. Contact your dealer for a replacement.
+Firmware versions until v2.30 did not report the error. Since v2.30; its visible on the device itself (in the GUI) and on the VRM Portal.
 ===== GPL Note =====
@@ Line 179: / Line 204: @@
 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~~