Differences

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

--- ccgx:ccgx_ve_power_setup [2019-01-22 10:16] – external edit 127.0.0.1
+++ ccgx:ccgx_ve_power_setup [2019-08-15 12:03] – replace Venus-device with GX device guy_stewart
@@ Line 6: / Line 6: @@
 There are two more procedures that can be done with VE Power Setup, but those have each been replaced with better newer functions:
-  - (deprecated) Remotely updating firmware of a VE.Can product (requires an internet connected [[venus-os:start|Venus-device]]). Use the [[vrm_portal:remote-firmware-update|new mechanism]] instead.
+  - (deprecated) Remotely updating firmware of a VE.Can product (requires an internet connected [[venus-os:start|GX device]]). Use the [[vrm_portal:remote-firmware-update|new mechanism]] instead.
-  - (deprecated) Remotely changing the configuration of VE.Bus system: Remote VEConfigure (requires an internet connected [[venus-os:start|Venus-device]]). Use the new [[vrm_portal:remote-veconfigure|new mechanism]] instead.
+  - (deprecated) Remotely changing the configuration of VE.Bus system: Remote VEConfigure (requires an internet connected [[venus-os:start|GX device]]). Use the new [[vrm_portal:remote-veconfigure|new mechanism]] instead.
 To update the firmware of a VE.Can product, its typically most convenient to use the remote option. Since its then not necessary to obtain the CANUSB adapter.
@@ Line 108: / Line 108: @@
 ==== 4.2 Remote VEConfigure: Troubleshooting ====
-=== Problem in the communication link between your computer and the Remote [[venus-os:start|Venus-device]]. ===
+=== Problem in the communication link between your computer and the Remote [[venus-os:start|GX device]]. ===
 Check the [[ccgx:ccgx_ve_power_setup#two-way_communication|Two-way communication instructions]].
 === Error, remote Color Control gave VEConfig error code 30: MK2 communication error ===
-Verify that both the firmware of the VE.Bus system and the [[venus-os:start|Venus-device]] comply to the [[ccgx:ccgx_ve_power_setup#remote_veconfigurerequirements|requirements for Remote VEConfigure]].
+Verify that both the firmware of the VE.Bus system and the [[venus-os:start|GX device]] comply to the [[ccgx:ccgx_ve_power_setup#remote_veconfigurerequirements|requirements for Remote VEConfigure]].
 ===== 5. Two-way communication =====
-Two-way communication is the name of the technology used for the communication link between your computer and the [[venus-os:start|Venus-device]] during Remote Firmware updates and Remote VEConfigure.
+Two-way communication is the name of the technology used for the communication link between your computer and the [[venus-os:start|GX device]] during Remote Firmware updates and Remote VEConfigure.
 ==== 5.1 Configuration ====
   - Use the latest version of the [[https://www.victronenergy.com/support-and-downloads/software#ve-configuration-tools-for-ve-bus-products|VE Configuration Tools for VE.Bus products]].
   - Use the latest version of [[https://www.victronenergy.com/support-and-downloads/software#ve-power-setup|VE Power Setup]].
-  - Check that the [[venus-os:start|Venus-device]] runs the latest available firmware.
+  - Check that the [[venus-os:start|GX device]] runs the latest available firmware.
-  - Enable Two-way communication on the [[venus-os:start|Venus-device]].
+  - Enable Two-way communication on the [[venus-os:start|GX device]].
   - Make sure to have Full Control access on the installation: On the VRM Portal, navigate to the site, then to the Settings tab, and click Users. Your login needs to highlight in green and show Full Control.
    - CCGX must be connected to internet, and Two-way communication must show as up in the Device list on the VRM Portal.
-This screenshot shows the Device list on the VRM Portal. See [[venus-os:start|Venus-device]] firmware version, as well as Two-way communication status encircled in red:
+This screenshot shows the Device list on the VRM Portal. See [[venus-os:start|GX device]] firmware version, as well as Two-way communication status encircled in red:
 {{ :ccgx:remoteveconfig_requirements_version_and_comms.png?nolink |}}