ccgx:ccgx_faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| ccgx:ccgx_faq [2020-05-27 17:54] – Q9 was outdated and no longer applies 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 111: | Line 111: | ||
| Remote support (default disabled): | Remote support (default disabled): | ||
| * 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. | * 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): | Two way communication (Remote VEConfig and Remote Firmware updates): | ||
| Line 121: | Line 121: | ||
| Remote Console on VRM (default disabled): | 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 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 | + | * 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, |
| * Remote console also relies on the data connection to the VRM portal using HTTPS (port 443), as describe above. | * Remote console also relies on the data connection to the VRM portal using HTTPS (port 443), as describe above. | ||
| * For troubleshooting, | * For troubleshooting, | ||
| 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 ==== | ==== 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. | + | 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. See FAQ for more information about this. | + | 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. | 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 202: | Line 205: | ||
| - | ===== DISQUS ===== | ||
| - | ~~DISQUS~~ | ||
ccgx/ccgx_faq.txt · Last modified: 2021-02-05 11:34 by marmour