User Tools

Site Tools


ccgx:ccgx_faq

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
ccgx:ccgx_faq [2019-06-14 07:35]
guy_stewart [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]
ccgx:ccgx_faq [2019-08-14 04:08]
simonhackett [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]
Line 158: Line 158:
 ==== 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 ==== ==== 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 ====
  
-Make sure that the GX device and MultiPlus is running the latest firmware version. ​Earlier version prevented startup when the GX device was connected, but not powered.+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 (InverterMulti 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. 
 + 
 +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/​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? ==== ==== Q21: I love Linux, programming,​ Victron and the Color Control GX. Can I do more? ====
  
Line 188: Line 205:
 ===== DISQUS ===== ===== DISQUS =====
 ~~DISQUS~~ ~~DISQUS~~
- 
ccgx/ccgx_faq.txt · Last modified: 2019-08-15 12:34 by guy_stewart