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 [2024-02-09 16:54] – [8.1 Disk space issues / data partition full] dfabervenus-os:large [2024-10-18 14:37] (current) – [5.9. Node-RED FAQ] mvader
Line 28: Line 28:
 There is and will be no official support on the functionalities of Venus OS large. There is and will be no official support on the functionalities of Venus OS large.
  
-For support, turn to the [[https://community.victronenergy.com/spaces/31/index.html|Modifications Space on Victron Community]] and/or the [[https://community.victronenergy.com/smart-spaces/71/node-red.html|Node-RED Space on Victron Community]].+For support, turn to the [[https://community.victronenergy.com/c/modifications/|Modifications Space on Victron Community]]. Another good resource is [[https://community.victronenergy.com/tag/node-red|all posts tagged as Node-RED]].
  
-There, first search if someone else had a similar question already. And if you can’t find such, then create a new question. Make sure you add Node-RED to the topic.+On Community, first search if someone else had a similar question already. And if you can’t find such, then create a new question. Make sure to tag it with Node-RED.
  
 For support on SignalK, there is a #victron channel in [[http://slack-invite.signalk.org/|the SignalK Slack]] workspace. For support on SignalK, there is a #victron channel in [[http://slack-invite.signalk.org/|the SignalK Slack]] workspace.
Line 120: Line 120:
 ===== 5. Node-RED ===== ===== 5. Node-RED =====
  
-{{ :venus-os:node-red-contrib-victron-nodes.png?nolink |}}+{{:venus-os:node-palette.png?direct&nolink |}}
 ==== 5.1 Introduction ==== ==== 5.1 Introduction ====
  
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 181: Line 184:
  
 ==== 5.4 Controlling relays ==== ==== 5.4 Controlling relays ====
 +
 +For a relay to be controllable via Node-RED, it needs to be switched to manual control first. In most cases this needs to be done by using [[https://www.victronenergy.com/panel-systems-remote-monitoring/victronconnect|VictronConnect]].
 +
 +;#;
 +{{:venus-os:victron-connect-relay-manual.png?400|}}
 +;#;
  
 === GX Device relays === === GX Device relays ===
Line 197: Line 206:
  
 === SolarCharger MPPT Relay === === SolarCharger MPPT Relay ===
-Currently it is not possible to control the relay in a MPPT Solar Chargereven though there is a Victron node offering such functionality. The reason it doesn't work, is that VictronConnect does not have the required "Manual control" option in the list of selectable Relay modes for the MPPTs. This will be fixed at some point.+In order to switch the relay via Node-REDfirst use VictronConnect to switch the operation mode to //manual control//.
  
 Note that only the larger model solar chargers feature a relay. Note that only the larger model solar chargers feature a relay.
Line 205: Line 214:
  
 === RS series (inverter, multi) relays === === RS series (inverter, multi) relays ===
-Currently not controllableWill be controllable in the future.+First set the relay to //manual control// using VictronConnectOnce that has been done, the relay can be controlled using Node-RED.
  
 === Charger relays === === Charger relays ===
Line 284: Line 293:
 In case you see that there is a newer version Victron pallette available online, and thats not yet shipping in a Venus OS Large version, then the only option is to wait: a new Venus OS Large version is usually made available shortly after updating that pallette. In case you see that there is a newer version Victron pallette available online, and thats not yet shipping in a Venus OS Large version, then the only option is to wait: a new Venus OS Large version is usually made available shortly after updating that pallette.
  
-=== Q3: How can I password protect Node-RED ===+=== Q3: How can I password protect Node-RED / My Node-RED is password protected ===
  
-Password protection of Node-Red is linked to the remote console. If a password is set for the remote console, this password is also used for securing Node-Red. The username is ''admin'', the password is the remote console password.+__Venus OS v3.50 and later__ 
 + 
 +For systems that have a security profile set (under Settings -> General -> Security Profile), the password protection is linked to the chosen security profile. The password that has been set for either security profile "weak" or "secured" is also used to access Node-RED, in combination with username ''admin''.  
 + 
 +__ Venus OS versions prior to v3.50__ 
 + 
 +The Node-RED's password protection is tied to the remote console. If a password is set for the remote console, this password is also used for securing Node-Red. The username is ''admin'', the password is the remote console password.
  
 === Q4: How do I restart Node-RED from the Venus GUI? === === Q4: How do I restart Node-RED from the Venus GUI? ===
Line 340: Line 355:
  
 And restart Node-RED. And restart Node-RED.
 +
 +=== Q11: Is there a way to have the context survive reboots? ===
 +
 +By default the context is stored in memory of the GX device only. If the GX device gets rebooted, the
 +content of the memory gets reset and you loose the context information.
 +
 +In order to keep the context data, it is needed to [[https://nodered.org/docs/api/context/store/localfilesystem|store the context to disk]]. This can be achieved by creating (or adding to) a user configuration file ''/data/home/nodered/.node-red/settings-user.js'', containing:
 +
 +  module.exports = {
 +    contextStorage: {
 +      default: {
 +        module: "localfilesystem",
 +        config: {
 +          flushInterval: 300 // Save context data every 5 minutes
 +        }
 +      }
 +    }
 +  }
 +  
 +With the above settings, context files will get created periodically in ''/data/home/nodered/.nodered/context/''. In order not to wear out the flash too much, don't write too often. 
 ===== 6. Signal K ===== ===== 6. Signal K =====
  
Line 391: Line 426:
   * [[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 1Opening the dashboard ===+Follow these steps to turn your GX into a NMEA to WiFi gateway within 5 minutes.
  
-Open a web browser, and go to the SignalK Dashboard by navigating to http://venus.local:3000.+These instructions assume that your GX device has already been set-up with Venus OS Large, and Signal K is enabled. 
 +  
 +=== Step 1Signal K Admin page ===
  
-Further documentation about that is ... (some link to signalk-node documentation?)+Open a web browser, and go to the Signal K admin page by navigating to http://venus.local:3000.
  
-=== Step 2Configure serial connections ===+{{ :venus-os:img_2580.jpeg |}}
  
-Use this to, for example, configure a USB-connected NMEA0183 connection in SignalKTo do so, go to the dashboard (http://0.0.0.0:3000), and there to Server -> Connections.+=== Step 2Set the admin password ===
  
-Make sure to not add a connection using any of the built-in serial ports (/dev/ttyO0, /dev/ttyO2, /dev/ttyO4, /dev/ttyO5). These are the VE.Bus- and VE.Direct ports on the Venus GX, and it is not necessary to configure them in SignalK. Data from any devices there connected is already available in SignalK, by means of the "Victron Venus Plugin"; see Dashboard -> Server -> Plugin Config.+Go to Security -> Users and create an admin user for Signal K and protect it with a secure password.
  
-Note that once configured in SignalK, for example a USB-serial port, that port is no longer normally available in Venus OS. For example, when plugging in a USB-GPS; and then adding a connection for its corresponding tty in the SignalK, makes for that GPS to be no longer be recognised and available in Venus OS.+{{ :venus-os:img_2579.png |}}
  
-=== Step 3. Configure can-bus connections ===+=== Step 3. Vessel information ===
  
-For the Venus GXSignalK comes pre-configured with a NMEA2000 listener for the VE.Can ports, its named "n2k-on-ve.can-socket", and uses the canboatjs.+Go to Settings and enter some basic information about your boat. 
 + 
 +{{ :venus-os:img_9926.png |}} 
 + 
 +=== Step 4. NMEA2000 Can-bus connection === 
 + 
 +For NMEA2000 networksits recommended to have all connected devices use isolated connections. Therefore, when connecting the an NMEA2000 network, we recommend using the Ekrano GX and the Cerbo MK2 GX. Connect to the port physically labelled “VE.Can 1”. 
 + 
 +Signal K is preconfigured to have its port operational for this. 
 + 
 +Here is how you can see the preconfigured connection in the Signal K Dashboard:
  
 ;#; ;#;
Line 420: Line 467:
 ;#; ;#;
  
- +Note that, to keep that operational, that port must remain 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 427: Line 473:
 ;#; ;#;
  
 +For more information on CAN-busses, see chapter 6.4.
 +
 +=== Step 5. Optional: Configure NMEA0183 serial connections ===
 +
 +Use this to, for example, configure a USB-connected NMEA0183 connection in SignalK. Go to Server -> Connections.
 +
 +Make sure to not add a connection using any of the built-in serial ports (/dev/ttyO0, /dev/ttyO2, /dev/ttyO4, /dev/ttyO5). These are the VE.Bus- and VE.Direct ports on the Venus GX, and it is not necessary to configure them in SignalK. Data from any devices there connected is already available in SignalK, via the "Victron Venus Plugin"; see Dashboard -> Server -> Plugin Config.
 +
 +Note that once configured in SignalK, for example a USB-serial port, that port is no longer normally available in Venus OS. For example, when plugging in a USB-GPS; and then adding a connection for its corresponding tty in the SignalK, makes for that GPS to be no longer be recognised and available in Venus OS.
 +
 +=== Step 6. Verify received data ===
 +
 +Go to the Databrowser to see the data now available to Signal K, and to tablets and nav. apps on   WiFi:
 +
 +{{ :venus-os:img_2578.png |}}
 +
 +=== Step 7. Configure your nav app ===
 +
 +Steps needed here will differ per app. The key required data is:
 +
 +  * Host/IP address: **venus.local**
 +  * Protocol: **TCP**
 +  * Port: **10110**
 + 
 +=== Done! ===
 +
 +Now you should have all your data such as position from the boat’s GPS, speed, wind data, as well as AIS targets in your favourite nav app. Like here in Navionics:
 +
 +{{ :venus-os:img_2581.jpeg?nolink |}}
 +
 +=== Where to go from here? Anchor alarms, trip recording, automatic log books and more ===
 +
 +  * Anchor alarm: https://demo.signalk.org/documentation/features/anchoralarm/anchoralarm.html
 +  * Automatic log book & trip recording: https://svrenaissance.com/starlink-and-victron-a-match-made-in-heaven-for-boaters/
 +==== 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 ===
  
-=== Step 4Adding Signalk Plugins or Webapps ===+^ Enclosure label ^ Interface ^ Notes ^ 
 +| VE.Can 1 | can0 | Isolated and default enabled in SignalK | 
 +| VE.Can 2 | can1 | Non-isolated |
  
-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+=== Ekrano GX ===
  
 +^ Enclosure label ^ Interface ^ Notes ^
 +| VE.Can 1 | vecan0 | Isolated |
 +| VE.Can 2 | vecan1 | Non-isolated |
 ==== 6.5 Signal K FAQ ==== ==== 6.5 Signal K FAQ ====
  
Line 562: Line 660:
 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 reset, as per the instructions in the GX user manuals. This includes downloading a file called venus-data.tgz.+Depending on what the issue is, there are a few things you can do
 + 
 +  - 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 detailsDisadvantage 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, make sure that the ''Keep only most recent data log files'' option is enabled. That feature is enabled by default, and can be found in the Signal K -> Server -> Settings section. 
 +  - A more detailed approach is logging into the SSH console, and checking for disk space: 
 + 
 +**Tips and tricks to login a diagnose disk space**
  
-A more detailed approach is logging in on SSH, and checking for disk spaceHere are a few useful commands.+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 616: Line 720:
  
   * [[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-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-20-signalk-reset.tgz|venus-data-20-signalk-reset.tgz]] - removes all files and directories from ''/data/conf/signalk/'', which lets you start over again with 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-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/''+  * [[https://www.victronenergy.com/upload/software/venus-factory-default/venus-data-20-node-red-reset.tgz|venus-data-20-node-red-reset.tgz]] - removes the files from ''/data/home/nodered/'', which lets you start with Node-RED from scratch.
  
 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. 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.1707494057.txt.gz · Last modified: 2024-02-09 16:54 by dfaber

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki