User Tools

Site Tools


venus-os:large

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
venus-os:large [2023-12-21 10:42] – external edit 127.0.0.1venus-os:large [2024-05-02 00:04] (current) – [6.2 Documentation and support for Signal K] mvader
Line 129: Line 129:
 A good tutorial on how to work with Node-RED is here: https://nodered.org/docs/tutorials/first-flow. On https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows you can find example flows that use the Victron Energy nodes. Searching for [[https://flows.nodered.org/search?term=victron|Victron]] on [[https://flows.nodered.org/search?term=victron|https://flows.nodered.org/]] will give all community flows that have been tagged "victron". A good tutorial on how to work with Node-RED is here: https://nodered.org/docs/tutorials/first-flow. On https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows you can find example flows that use the Victron Energy nodes. Searching for [[https://flows.nodered.org/search?term=victron|Victron]] on [[https://flows.nodered.org/search?term=victron|https://flows.nodered.org/]] will give all community flows that have been tagged "victron".
  
-There is also a 3 part introductory webinar on Node-RED and Venus available at the Victron Tech YouTube channel:+==== 5.2 Three part introductory webinar ==== 
 + 
 +This is a 3 part introductory webinar on Node-RED and Venus available at the Victron Tech YouTube channel:
  
 [[https://www.youtube.com/watch?v=i_iaciqn_Fg| 1. Getting started]] [[https://www.youtube.com/watch?v=i_iaciqn_Fg| 1. Getting started]]
Line 142: Line 144:
 The Node-RED editor can be accessed from your LAN at https://venus.local:1881/. For some systems, you'll have to replace ''venus.local'' by the ip-address. You can also access the Node-RED editor from VRM, where it is available via the //Venus OS Large// menu.  The Node-RED editor can be accessed from your LAN at https://venus.local:1881/. For some systems, you'll have to replace ''venus.local'' by the ip-address. You can also access the Node-RED editor from VRM, where it is available via the //Venus OS Large// menu. 
  
-__Standard nodes + Victron nodes__+==== 5.3 Node specifications ==== 
 Node-RED comes with a core set of useful nodes, and within the Venus OS large install there is a set of Victron nodes added to that: the Victron Pallet. All of the different nodes are described [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Available-nodes|here]]. Node-RED comes with a core set of useful nodes, and within the Venus OS large install there is a set of Victron nodes added to that: the Victron Pallet. All of the different nodes are described [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Available-nodes|here]].
  
Line 325: Line 328:
  
   export NODE_EXTRA_CA_CERTS=/data/etc/ssl/venus.local.crt   export NODE_EXTRA_CA_CERTS=/data/etc/ssl/venus.local.crt
 +  
 === Q9: How often do the Victron input nodes send a msg? === === Q9: How often do the Victron input nodes send a msg? ===
  
 The input nodes send out a message on each value change. If the ‘//only changes//’ checkbox is set, this will be the only output of the node. If the '//only changes//' checkbox is not set, the node also sends out the current value each 5 seconds. If you want more fine grained control, consider storing the desired values in a context in combination with triggered intervals. See [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows#only-messages-at-regular-intervals|here]] for an example on how to do that. The input nodes send out a message on each value change. If the ‘//only changes//’ checkbox is set, this will be the only output of the node. If the '//only changes//' checkbox is not set, the node also sends out the current value each 5 seconds. If you want more fine grained control, consider storing the desired values in a context in combination with triggered intervals. See [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows#only-messages-at-regular-intervals|here]] for an example on how to do that.
  
 +=== Q10: How can I get Node-RED to also listen to http port 1880 ===
 +
 +There are some nodes that are only able to connect to a http site. In that case you probably also want to enable http on port 1880. This can be achieved by creating (or adding to) a user configuration file ''/data/home/nodered/.node-red/settings-user.js'', containing:
 +
 +  module.exports = {
 +     /* Make sure that we also listen on port 1880 on all interfaces */
 +     uiHost: "::"
 +  }
 +
 +And restart Node-RED.
 ===== 6. Signal K ===== ===== 6. Signal K =====
  
Line 381: Line 394:
   * [[https://demo.signalk.org/documentation/|The official Signal K documentation]]   * [[https://demo.signalk.org/documentation/|The official Signal K documentation]]
   * [[https://community.victronenergy.com/search.html?c=&includeChildren=&f=&type=question+OR+idea+OR+kbentry+OR+answer+OR+topic+OR+user&redirect=search%2Fsearch&sort=relevance&q=signal+k|Signal K topics on the Victron Community forum]]   * [[https://community.victronenergy.com/search.html?c=&includeChildren=&f=&type=question+OR+idea+OR+kbentry+OR+answer+OR+topic+OR+user&redirect=search%2Fsearch&sort=relevance&q=signal+k|Signal K topics on the Victron Community forum]]
-  * [[http://slack-invite.signalk.org/|Signal K Slack]] - a real time chat group including a special Victron channel.+  * [[https://discord.gg/uuZrwz4dCS |Signal K Discord]] - a real time chat group including a special Victron channel.
  
 Do not contact normal Victron support for any help on SignalK. Its based on community support, not official support. Do not contact normal Victron support for any help on SignalK. Its based on community support, not official support.
  
  
-==== 6.First use & configuring ====+==== 6.First use & configuring ====
  
 === Step 1. Opening the dashboard === === Step 1. Opening the dashboard ===
Line 404: Line 417:
 === Step 3. Configure can-bus connections === === Step 3. Configure can-bus connections ===
  
-For the Venus GX, SignalK comes pre-configured with a NMEA2000 listener for the VE.Can ports, its named "n2k-on-ve.can-socket", and uses the canboatjs.+For the Venus GX, and Cerbo GX, SignalK comes pre-configured with a NMEA2000 listener for the VE.Can ports, its named "n2k-on-ve.can-socket", and uses the canboatjs. Here is how you can see the same in the Signal K Admin UI:
  
 ;#; ;#;
 {{:venus-os:cerbo-gx-signalk-canboatjs.png?400|}} {{:venus-os:cerbo-gx-signalk-canboatjs.png?400|}}
 ;#; ;#;
- 
  
 Note that, to keep that operational, that port must be configured as a 250kbit VE.Can & NMEA2000 port in the Remote Console. Note that, to keep that operational, that port must be configured as a 250kbit VE.Can & NMEA2000 port in the Remote Console.
Line 417: Line 429:
 ;#; ;#;
  
 +For more information on CAN-busses, see chapter 6.4.
  
 === Step 4. Adding Signalk Plugins or Webapps === === Step 4. Adding Signalk Plugins or Webapps ===
Line 422: Line 435:
 TODO: explain & warn about data partition size & space (since thats where plugins are installed by signalk on Venus OS). Filling up the datapartition can corrupt Venus OS. More information about data partition on Venus OS here: https://github.com/victronenergy/venus/wiki/data-partition TODO: explain & warn about data partition size & space (since thats where plugins are installed by signalk on Venus OS). Filling up the datapartition can corrupt Venus OS. More information about data partition on Venus OS here: https://github.com/victronenergy/venus/wiki/data-partition
  
 +==== 6.4 CAN-bus ports ====
 +
 +Below lists documents the mapping from physical ports on the device to the interface within Venus OS. This information is needed when you want to deviate from the standard configuration.
 +
 +=== Cerbo GX ===
 +
 +^ Enclosure label ^ Interface ^ Notes ^
 +| VE.Can 1 | can0 | Non-isolated and default enabled in SignalK |
 +| BMS-Can | can1 | Non-isolated, not usable within SignalK for NMEA2000 |
 +
 +Within the Victron product range, CAN-bus ports that are labelled BMS-Can are limited in their functionality due to hardware constraints. Their only use is to connect to a managed battery such as BYD and Pylontech, used in landbased ESS & Off-grid systems - not in the marine market.
 +
 +=== Cerbo GX MK2 ===
 +
 +^ Enclosure label ^ Interface ^ Notes ^
 +| VE.Can 1 | can0 | Isolated and default enabled in SignalK |
 +| VE.Can 2 | can1 | Non-isolated |
 +
 +=== Ekrano GX ===
 +
 +^ Enclosure label ^ Interface ^ Notes ^
 +| VE.Can 1 | vecan0 | Isolated |
 +| VE.Can 2 | vecan1 | Non-isolated |
 +
 +When using SignalK on Venus OS on an Ekrano, there is currently no port enabled for N2K traffic in the default configuration. Configure it manually instead, see here for more information: https://community.victronenergy.com/questions/263126/ekrano-gx-vs-signal-k-no-n2k-on-vecan-socket.html?childToView=263206#answer-263206. 
 ==== 6.5 Signal K FAQ ==== ==== 6.5 Signal K FAQ ====
  
Line 552: Line 590:
 Note that Venus OS itself does **not** show a notification or warning when the data disk is full. And know that the other disks are read-only unless remounted to read/write as per [[https://www.victronenergy.com/live/ccgx:root_access|these root access instructions]]. Note that Venus OS itself does **not** show a notification or warning when the data disk is full. And know that the other disks are read-only unless remounted to read/write as per [[https://www.victronenergy.com/live/ccgx:root_access|these root access instructions]].
  
-The easy solution is to do full GX factory resetas per the instructions in the GX user manuals. This includes downloading file called venus-data.tgz.+Depending on what the issue is, there are few things you can do:
  
-A more detailed approach is logging in on SSH, and checking for disk space. Here are few useful commands.+  - Do full GX factory reset, as per the instructions in the GX user manuals. This includes downloading a file called venus-data.tgz; see GX manual for details. Disadvantage is that you'll need to reconfigure the GX. 
 +  - Remove all Signal K Server log files. In case you're using SignalK, then we recommend to try that option first. See next chapter on how to do that (requires a USB stick or SD Card), and once done make sure to double check you're Signal K log setup; Most importantly, enable the ''Keep only most recent data log files'' option. 
 +  - A more detailed approach is logging in on SSH, and checking for disk space
 + 
 +**Tips and tricks to login diagnose disk space** 
 + 
 +Require root access: https://www.victronenergy.com/live/ccgx:root_access.
  
 The ''df'' command shows disk space including percentage in user for all mounted storages. Note the 100% full of below data partition. That is a problem. It should show maybe 10, 20 or 30%, but never 100% in use. The ''df'' command shows disk space including percentage in user for all mounted storages. Note the 100% full of below data partition. That is a problem. It should show maybe 10, 20 or 30%, but never 100% in use.
Line 600: Line 644:
 744 /data/log/swupdate 744 /data/log/swupdate
 </code> </code>
 +
 +==== 8.2 Backup / Reset to factory defaults  ====
 +
 +There are scenarios where you want to make a backup of your data or when you want to clear logging or even start all over and go back to factory defaults. In order to make this process easy, you can put one (or more) of the following files on an USB stick and reboot your device. The files will be unpacked and the scripts within will execute. Once the script is ready with its tasks, a notification of 3 beeps can be heard (on a Multiplus-II GX the notification will be shown in the display). After which the USB stick can be removed.
 +
 +  * [[https://www.victronenergy.com/upload/software/venus-factory-default/venus-data-00-backup-data-partition.tgz|venus-data-00-backup-data-partition.tgz]] - copies all that is on the ''/data'' partition onto the usb stick
 +  * [[https://www.victronenergy.com/upload/software/venus-factory-default/venus-data-20-signalk-reset.tgz|venus-data-20-signalk-reset.tgz]] - wipes everything from ''/data/conf/signalk/''
 +  * [[https://www.victronenergy.com/upload/software/venus-factory-default/venus-data-30-signalk-delete-data-logs.tgz|venus-data-30-signalk-delete-data-logs.tgz]] - removes all SignalK loging
 +  * [[https://www.victronenergy.com/upload/software/venus-factory-default/venus-data-20-node-red-reset.tgz|venus-data-20-node-red-reset.tgz]] - wipes all in ''/data/home/nodered/''
 +
 +See [[https://www.victronenergy.com/live/ccgx:root_access#hooks_to_install_run_own_code_at_boot|here]] for more information on how this process works.
venus-os/large.1703151765.txt.gz · Last modified: 2023-12-21 10:42 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki