Victron Energy

User Tools

Site Tools

You are here: Documentation » Open source » CCGX Hardware and software introduction » commandline
open_source:ccgx:commandline

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
open_source:ccgx:commandline [2019-04-15 21:10] – [5. VE.Direct products] mvaderopen_source:ccgx:commandline [2021-03-03 10:14] – [4.4 vreg: changing settings from the command line] mvader
Line 1: Line 1:
-====== Venus command-line manual ======+====== Venus OS operational commandline manual ======
  
 ===== 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-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|here]] 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]].
  
 +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 ==== ==== 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; 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. Our support staff on all official channels, Disqus and elsewhere, does not know how these tools can be used.
Line 22: 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 38: Line 39:
 Both firmware updating as well as changing settings is normally done with [[victronconnect:start|VictronConnect]]. Both firmware updating as well as changing settings is normally done with [[victronconnect:start|VictronConnect]].
  
-It is not possible to remotely change settings. Neither from the command line.+[[https://www.victronenergy.com/media/pg/VictronConnect_Manual/en/victonconnect-remote--vc-r----configuration-and-monitoring-via-vrm.html|VictronConnect Remote]] allows remote changing of settings. It is not available from the command line.
  
-Updating firmware remote is only possible from the command line, see below.+Updating firmware remotely is available via the [[vrm_portal:remote-firmware-update|Remote Firmware Update feature of VRM]] (in the device list), and via the command line, see below.
  
 ==== 1.3 Connecting to the command line and file transfer ==== ==== 1.3 Connecting to the command line and file transfer ====
Line 132: Line 133:
 On that computer, open the file by double clicking it, make the modifications, and save the file again. 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 === === Step 3. Writing the new settings to the system ===
Line 143: 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, and therefore proven. But not all. So use at you're own risk.
  
 Requires Venus v2.00 or later. Requires Venus v2.00 or later.
Line 155: 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: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. 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 339: Line 342:
  
 Victron Energy B.V. Victron Energy B.V.
 +</code>
 +
 +Example of switching a solar charger off, and then on
 +<code>
 +OFF: (vreg 0x0200, value 4)
 +ccgx:~# vreg -n 0x45 -s 0x0200 un8:0x04
 +# NAD 0x45, reg=0x200
 +0x04 0x00 0x00 0x00 
 +
 +ON: (vreg 0x0200, value 1)
 +root@ccgx:~# vreg -n 0x45 -s 0x0200 un8:0x01
 +# NAD 0x45, reg=0x200
 +0x01 0x00 0x00 0x00 
 +root@ccgx:~# vreg -n 0x45 -s 0x0200 un8:0x03
 +
 +Gets can be broadcasted, run this command, and press ctrl-C to make it stop listen for responses:
 +
 +vreg -c socketcan:can0 -g 0x200 -r
 +root@einstein:~# vreg -c socketcan:can0 -g 0x0200 -r
 +# reminder, there are no error indications when broadcasting!
 +# NAD 0x24, reg=0x200
 +0x01 0x00 0x00 0x00 
 +# NAD 0x25, reg=0x200
 +0x01 0x00 0x00 0x00 
 +# NAD 0x26, reg=0x200
 +0x01 0x00 0x00 0x00 
 +and so forth
 </code> </code>
 ===== 5. VE.Direct products ===== ===== 5. VE.Direct products =====
open_source/ccgx/commandline.txt · Last modified: 2023-05-07 10:00 by mvader
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki