open_source:ccgx:commandline
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| open_source:ccgx:commandline [2018-07-17 14:26] – [5. VE.Direct products] mvader | open_source:ccgx:commandline [2019-01-22 10:43] – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== 1. Introduction ===== | ===== 1. Introduction ===== | ||
| - | This page explains how to change settings and/or update firmware for various Victron products which are connected to a 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: |
| For more software developer oriented command line tips & tricks, see [[https:// | For more software developer oriented command line tips & tricks, see [[https:// | ||
| Line 132: | Line 132: | ||
| On that computer, open the file by double clicking it, make the modifications, | On that computer, open the file by double clicking it, make the modifications, | ||
| - | Then transfer the new file back onto the Venus device. | + | Then transfer the new file back onto the [[venus-os: |
| === Step 3. Writing the new settings to the system === | === Step 3. Writing the new settings to the system === | ||
| Line 155: | Line 155: | ||
| Updating a MultiGrid and also a MultiPlus-II is not (yet) possible with vbdup. | Updating a MultiGrid and also a MultiPlus-II is not (yet) possible with vbdup. | ||
| - | Make sure that the 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: |
| 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. | 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. | ||
open_source/ccgx/commandline.txt · Last modified: 2023-05-07 10:00 by mvader