Differences

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

--- open_source:ccgx:commandline [2019-06-22 15:25] – [1. Introduction] mvader
+++ open_source:ccgx:commandline [2019-08-15 11:56] – [1.1 No support warning] - VicCom link guy_stewart
@@ Line 3: / Line 3: @@
 ===== 1. Introduction =====
-This page explains how to change settings and/or update firmware for various Victron products which are connected to a [[venus-os:start|Venus-device]], for example the Color Control GX, via the command line, ie ssh.
+This page explains how to change settings and/or update firmware for various Victron products which are connected to a [[venus-os:start|GX device]], for example the Color Control GX, via the command line, ie ssh.
-For more software developer oriented command line tips & tricks, see [[https://github.com/victronenergy/venus/wiki/commandline-introduction|the Venus OS commandline manual for software development]] on the Venus wiki.
+This document is part of the Venus OS developer documentation. The main document is [[https://github.com/victronenergy/venus/wiki|the Venus OS wiki on github]].
-To get started on Venus OS, start [[https://github.com/victronenergy/venus/wiki|here]].
+For more software developer oriented command line tips & tricks, see [[https://github.com/victronenergy/venus/wiki/commandline-introduction|the Venus OS commandline manual for software development]] on the Venus wiki.
 ==== 1.1 No support warning ====
 Note regarding support: this document is made available for convenience only. There is no support on this type of using our products. Using the command line is outside normal use;
-In case of questions, you can use the [[https://groups.google.com/forum/#!forum/victron-dev-venus|Venus developers mailing list]].
+In case of questions, you can use the [[https://groups.google.com/forum/#!forum/victron-dev-venus|Venus developers mailing list]], or the [[https://community.victronenergy.com/spaces/31/index.html|modifications space on Victron Community]].
 Our support staff on all official channels, Disqus and elsewhere, does not know how these tools can be used.
@@ Line 133: / Line 133: @@
 On that computer, open the file by double clicking it, make the modifications, and save the file again.
-Then transfer the new file back onto the [[venus-os:start|Venus-device]].
+Then transfer the new file back onto the [[venus-os:start|GX device]].
 === Step 3. Writing the new settings to the system ===
@@ Line 156: / Line 156: @@
 Updating a MultiGrid and also a MultiPlus-II is not (yet) possible with vbdup.
-Make sure that the [[venus-os:start|Venus-device]] (fe. CCGX), as well as routers or any other used communications equipment, are __not__ powered by the VE.Bus devices. If they are, you'll lose power and connection as soon as the update is started, resulting in a dead system.
+Make sure that the [[venus-os:start|GX device]] (fe. CCGX), as well as routers or any other used communications equipment, are __not__ powered by the VE.Bus devices. If they are, you'll lose power and connection as soon as the update is started, resulting in a dead system.
 The product that you want to update needs to have application firmware running: just bootloader is not enough. The update starts with requesting the hardware IDs (VE.Bus discovery) from the running application. Those hardware IDs are then used to address the VE.Bus devices once in bootloader mode. After the discovery, the hardware IDs aare stored in a file. In case, for example because of a power loss, the update fails, vbdup will automatically use the hardware IDs stored in that file.