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 [2019-06-22 20:47] – [1. Introduction] mvader | open_source:ccgx:commandline [2021-03-06 14:38] – [8. Enabling VRM two-way communication (Remote VEConfigure aka vrmpubnub)] mvader | ||
---|---|---|---|
Line 12: | Line 12: | ||
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; | 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:// | + | In case of questions, you can use the [[https:// |
Our support staff on all official channels, Disqus and elsewhere, does not know how these tools can be used. | Our support staff on all official channels, Disqus and elsewhere, does not know how these tools can be used. | ||
Line 23: | Line 23: | ||
Changing settings with products featuring a VE.Bus comm. port (Inverters, Multis and Quattros) is normally done with VEConfigure. | Changing settings with products featuring a VE.Bus comm. port (Inverters, Multis and Quattros) is normally done with VEConfigure. | ||
- | Firmware updates are normally done with VEFlash, a computer tool that is installed together with VEConfigure. | + | Firmware updates are normally done with VEFlash, a computer tool that is installed together with VEConfigure, or VictronConnect. |
- | To change settings remotely, use [[ccgx:ccgx_ve_power_setup|Remote VEConfigure]]. | + | To change settings remotely, use [[vrm_portal:remote-veconfigure|Remote VEConfigure.]] |
Remotely updating firmware of a VE.Bus product is only possible from the command line, see below. | Remotely updating firmware of a VE.Bus product is only possible from the command line, see below. | ||
Line 39: | Line 39: | ||
Both firmware updating as well as changing settings is normally done with [[victronconnect: | Both firmware updating as well as changing settings is normally done with [[victronconnect: | ||
- | It is not possible to remotely change settings. Neither | + | [[https:// |
- | Updating firmware | + | Updating firmware |
==== 1.3 Connecting to the command line and file transfer ==== | ==== 1.3 Connecting to the command line and file transfer ==== | ||
Line 133: | Line 133: | ||
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-os: | + | 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 144: | Line 144: | ||
==== 3.2 Updating VE.Bus firmware === | ==== 3.2 Updating VE.Bus firmware === | ||
+ | |||
+ | WARNING: At Victron we don't use this tool. Part of the code is shared with the VE.Bus firmware update functionality in VictronConnect, | ||
Requires Venus v2.00 or later. | Requires Venus v2.00 or later. | ||
Line 156: | Line 158: | ||
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-os: | + | 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. | ||
Line 341: | Line 343: | ||
Victron Energy B.V. | Victron Energy B.V. | ||
</ | </ | ||
+ | |||
+ | Switching all devices on VE.Can off (careful, when having NMEA2000-out enabled, or having an Inverter RS, also AC will be switched off!): | ||
+ | < | ||
+ | vreg -c socketcan: | ||
+ | </ | ||
+ | |||
+ | switching a specific device off: | ||
+ | < | ||
+ | vreg -c socketcan: | ||
+ | </ | ||
+ | Note that in above example the VREG data field (un32) is padded with zeros; current firmware requires that, future fw won't any more. | ||
+ | |||
+ | Switch a specific device on: | ||
+ | < | ||
+ | vreg -c socketcan: | ||
+ | </ | ||
+ | |||
+ | Seeing which devices are off and which are on goes like this. Press ctrl-C to stop the command. | ||
+ | < | ||
+ | vreg -c socketcan: | ||
+ | </ | ||
+ | |||
===== 5. VE.Direct products ===== | ===== 5. VE.Direct products ===== | ||
Line 407: | Line 431: | ||
- If you want to set a password, go to Settings -> Remote Console -> Enable password check | - If you want to set a password, go to Settings -> Remote Console -> Enable password check | ||
- | ===== 8. Enabling VRM two-way communication (Remote VEConfigure aka vrmpubnub) ===== | ||
- | If you have a CCGX already installed, but VRM two-way communication is not enabled, follow these steps to enable it remotely: | ||
- | |||
- | - SSH into CCGX (make a root password by following instructions [[ccgx: | ||
- | - < | ||
- | - VE.Configure should now be able to connect to the CCGX | ||
open_source/ccgx/commandline.txt · Last modified: 2023-05-07 10:00 by mvader