Differences

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

--- ccgx:ccgx_faq [2019-05-17 16:18] – [Q1: I cannot switch my Multi/Quattro system on or off] john_r
+++ ccgx:ccgx_faq [2019-08-15 12:34] – replace venus-device with GX device guy_stewart
@@ Line 157: / Line 157: @@
 ==== 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.
+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. 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.
@@ Line 166: / Line 169: @@
 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|}}
 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.
 ==== Q21: I love Linux, programming, Victron and the Color Control GX. Can I do more? ====
@@ Line 178: / Line 184: @@
 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|Venus-device]].
+The IP address can be found by going to Settings > Ethernet or Wifi. Once the page is loaded, Choose an image file from your device. Re-boot the [[venus-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 191: / Line 205: @@
 ===== DISQUS =====
 ~~DISQUS~~