Victron Energy

User Tools

Site Tools

You are here: Documentation » Victron GX product range » Venus OS Large image: Signal K and Node-RED
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-10-18 14:37] – [5.9. Node-RED FAQ] mvadervenus-os:large [2025-08-05 23:13] (current) – warwickchapman
Line 7: Line 7:
 **Node-RED** offers PLC like programming for connecting hardware devices, APIs and online services. It provides a browser-based editor that makes it easy to wire together flows. With it, one can for example program a functionality such as activating a relay based on a temperature measurement combined with time. Or make far more complex algorithms, tying relays, measurements, or other data available from Venus OS or elsewhere together. All without having to write real source code. Node-RED is also called Low-code programming for event-driven applications. **Node-RED** offers PLC like programming for connecting hardware devices, APIs and online services. It provides a browser-based editor that makes it easy to wire together flows. With it, one can for example program a functionality such as activating a relay based on a temperature measurement combined with time. Or make far more complex algorithms, tying relays, measurements, or other data available from Venus OS or elsewhere together. All without having to write real source code. Node-RED is also called Low-code programming for event-driven applications.
  
-Also Node-RED features a [[https://flows.nodered.org/node/node-red-dashboard|fully customisable dashboard]], viewable in a webbrowser - both locally but also remotely, via the VRM Servers.+Also Node-RED features a [[https://flows.nodered.org/node/node-red-dashboard|fully customisable dashboard]], viewable in a web browser - both locally but also remotely, via the VRM Servers.
  
-To get a good idea of its possibilities, see our [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows|example flows]].+To get a good idea of its possibilities, see the [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows|example flows]].
  
 **Signal K server** Signal K Server is a server application that runs on a central hub in a boat; in this case a Victron GX device. A few of its most used features are: **Signal K server** Signal K Server is a server application that runs on a central hub in a boat; in this case a Victron GX device. A few of its most used features are:
Line 26: Line 26:
 ===== 2. Where to find support ===== ===== 2. Where to find support =====
  
-There is and will be no official support on the functionalities of Venus OS large.+Victron maintains the integration of Node-RED and SignalK into Venus OS for GX-devices.  However, Victron does not provide support for systems which make use of these extended features to implement advanced solutions.
  
-For support, turn to the [[https://community.victronenergy.com/c/modifications/5 |Modifications Space on Victron Community]]. Another good resource is [[https://community.victronenergy.com/tag/node-red|all posts tagged as Node-RED]].+**Node-RED support** 
 +The Victron Community is a good place to ask questions and get answers: 
 +  * [[https://community.victronenergy.com/c/modifications/5 |Modifications Space on Victron Community]] 
 +  * [[https://community.victronenergy.com/tag/node-red|All posts tagged as Node-RED]]
  
 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. 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.+**Signal K community** 
 +For support on Signal K, the largest crowd of helpful people can be found in the Signal K Discord & Signal K GitHub discussions forum. Both are best found here: https://signalk.org/community/ 
 ===== 3. Requirements ===== ===== 3. Requirements =====
  
Line 38: Line 43:
  
 The compatible GX devices are: The compatible GX devices are:
- +  * Ekrano GX (fastest processor) 
-  * Ekrano GX +  * Cerbo GX (second-fastest processor)
-  * Cerbo GX+
   * Cerbo-S GX   * Cerbo-S GX
-  * Venus GX+  * Venus GX (slowest processor)
   * Octo GX   * Octo GX
-  * MultiPlus-II GX +  * MultiPlus-II GX (fastest processor) 
-  * EasySolar-II GX+  * EasySolar-II GX (fastest processor)
  
 +The Color Control GX (CCGX) and the CanVU GX are not able to run Venus OS Large.
  
-The Color Control GX (CCGX) as well as the CanVU GX are unfortunately not able to run Venus OS Large.+Venus OS large is also available for certain RaspberryPi models. Installation files below, and installation & other RaspberryPi specific instructions [[https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image|here]].
  
-Venus OS large is also available for certain RaspberryPi models. Installation files below, and installation & other raspberrypi specific instructions [[https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image|here]].+==== 3.2 CPU & memory resources ====
  
-==== 3.2 CPU & Memory resources ====+Both Signal K as well as Node-RED are resource intensive software applications relative to the CPU and memory of most GX devices.
  
-Both SignalK as well as Node-RED are rather resource intensive software applications to run on the GX Device. From a CPU usage point of view as well as RAM memory.+The level of intensity largely depends on the system's specific configuration - whether it's the type of flows in Node-RED or the volume and processing requirements of messages in Signal K.
  
-Ofcourse, how intensive depends on what kind of flows (node-red) or how many messages & handling of them (SignalK) happens in the system.+**WARNING: Venus GX** 
 +The Venus GX is the slowest GX-device still supported by Victron. Running both Signal K and Node-RED at the same time will very likely overload the device and may result it in becoming unstable.
  
-From a GX device point of view, from the support models the Venus GX is the one with the least resources. Running both SignalK and Node-RED at the same time will be "pushing it" to say it simply. The Cerbo GX is already much faster, as it has a dual core CPU as well as much more RAM. More details about CPU & RAM differences are in this document: https://github.com/victronenergy/venus/wiki/machines.+If a GX-device runs out of memory or the load on the CPU becomes too high, the device will eventually reboot which may render a system unstable. 
 + 
 +More details about CPU & RAM differences is available [[https://www.victronenergy.com/live/venus-os:start|here]].
  
-When running out of RAM or CPU, the device will slow down. And eventually also reboot by itself due to the watchdog. 
  
 ===== 3. How to install and update ===== ===== 3. How to install and update =====
Line 75: Line 82:
 Note, when installing on a RaspberryPi, do make sure to familiarise with [[https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image|the Venus OS for raspberrypi documentation]] as well. Note, when installing on a RaspberryPi, do make sure to familiarise with [[https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-image|the Venus OS for raspberrypi documentation]] as well.
  
-=== Step 2. Update to the latest firmware version (v2.90 or later) ===+=== Step 2. Update to the latest firmware version ===
  
-See Settings -> Firmware -> Online updates. For more information, refer to the user the manual of your GX device.+See Settings -> General -> Firmware -> Online updates (previously, Settings -> Firmware -> Online updates). For more information, refer to the user the manual of your GX device.
  
 === Step 3. Set the image type Venus OS Large === === Step 3. Set the image type Venus OS Large ===
  
-Go to Settings -> Firmware -> Online updates -> Image type:+In the Online updates menu: 
 +{{ :venus-os:venus-os_image_type_selector_v2.png?nolink&500 |}}
  
-{{ :venus-os:image_type_selector.png?nolink&500 |}}+Set the Image type to 'Large', navigate one level back in the menu and check for a new version and install that.
  
-Now, change the Image type to Large. Then go one menu up, and Check for a new version and install that.+The firmware will take some time to download depending on the speed of your Internet connection, after which the GX-device will reboot for the installation which typically takes about 2 minutes.
  
-=== Step 3. Verify and enable ===+=== Step 4. Verify and enable ===
  
-  - Verify that the image was successfully installed: go to the Settings menu, and check that the Venus OS Large menu is available. +  - Verify that the image was successfully installed: go to the Settings menu, and check that under the integrations for availability. 
-  - Enable either Signal K or Node-RED. Note that though its possible to enable both, doing that on a Venus GX is "pushing it", the system might become slow. This is less of a problem on a Cerbo GX, as it has more resources (faster CPU). Installer access level is required to enable/disable these settings.+  - Enable either Signal K or Node-RED. Installer access level is required to enable/disable these settings. 
 + 
 +Visible once successfully installed, the integration settings: 
 +{{ :venus-os:venus_os_large_menu_v2.png?nolink&500 |}}
  
-Visible once successfully installed, the Venus OS Large menu: 
-{{ :venus-os:venus_os_large_menu.png?nolink&500 |}} 
  
 === How to update === === How to update ===
  
-Both online and offline update methods can be used. The Image type setting, see the How to install chapter, defines what image type is being updated. See the GX manual for more details.+Both online and offline update methods can be used. The Image type setting, see the How to install chapter, defines what image type is being updated. See the manual of your GX-device for more details. 
 ===== 4. Accessing Node-RED and Signal K ====== ===== 4. Accessing Node-RED and Signal K ======
  
-After installing and then enabling either one or both of the features, they need to be configured through a website in your browser.+After installing and enabling Node-RED or Signal K, they need to be configured through a website in your browser.
  
-To access the Node-RED flow editor, type https://venus.local:1881/. Note that it might be necessary to replace venus.local by an IP address, for example like this: https://192.168.178.224:1881/. It is normal for the browser to show a security warning. Proceed according to browsers instructions. +To access the Node-RED flow editor, type https://venus.local:1881. Note that it might be necessary to replace venus.local with an IP address on your LAN, for example: https://192.168.178.224:1881. The web browser will show a security warning (from using HTTPS on a local IP address), which must be accepted.
- +
-See [[https://www.victronenergy.com/media/pg/Cerbo_GX/en/accessing-the-gx-device.html#UUID-a007e0de-85f1-a53f-550b-25f0ed46ac1f|the Remote Console on LAN chapter on our GX manual]] for how to find the IP address. +
- +
-To access the Signal K admin panel, type http://venus.local:3000/. Just like Node-RED above, note that it might be necessary to replace venus.local in that URL by an IP address. For example like this: http://192.168.178.224:3000/ +
- +
-These two screenshots show what you will see after successfully accessing the pages:+
  
 === Node-RED flow editor === === Node-RED flow editor ===
  
 {{ :venus-os:node-red_flow_editor.png?nolink |}} {{ :venus-os:node-red_flow_editor.png?nolink |}}
 +
 +To access the Signal K admin panel, type http://venus.local:3000. Just like Node-RED above, note that it might be necessary to replace venus.local in that URL by an IP address. For example: http://192.168.178.224:3000/
  
 === Signal K admin panel === === Signal K admin panel ===
  
 {{ :venus-os:signal_k_admin_panel.png?nolink |}} {{ :venus-os:signal_k_admin_panel.png?nolink |}}
 +
 +See [[https://www.victronenergy.com/media/pg/Cerbo_GX/en/accessing-the-gx-device.html#UUID-a007e0de-85f1-a53f-550b-25f0ed46ac1f|the Remote Console on LAN chapter on our GX manual]] for how to find the IP address on the GX-device.
  
 ===== 5. Node-RED ===== ===== 5. Node-RED =====
  
-{{:venus-os:node-palette.png?direct&nolink |}}+{{ https://raw.githubusercontent.com/victronenergy/node-red-contrib-victron/master/docs/images/node-palette.png?nolink |}} 
 ==== 5.1 Introduction ==== ==== 5.1 Introduction ====
  
 Node-RED is a tool for connecting hardware devices, APIs and online services in new and interesting ways. It provides a browser-based editor that makes it easy to wire together flows. With it, one can for example program a functionality such as activating a relay based on a temperature measurement. Or make far more complex algorithms, tying relays, measurements, or other data available from Venus OS or elsewhere together. All without having to write real source code, as Node-RED calls Low-code programming for event-driven applications. Node-RED is a tool for connecting hardware devices, APIs and online services in new and interesting ways. It provides a browser-based editor that makes it easy to wire together flows. With it, one can for example program a functionality such as activating a relay based on a temperature measurement. Or make far more complex algorithms, tying relays, measurements, or other data available from Venus OS or elsewhere together. All without having to write real source code, as Node-RED calls Low-code programming for event-driven applications.
  
-Also Node-RED features a [[https://flows.nodered.org/node/node-red-dashboard|fully customisable dashboard]], viewable in a webbrowser - both locally but also remotely, via the VRM Servers.+Also Node-RED features a [[https://flows.nodered.org/node/node-red-dashboard|fully customisable dashboard]], viewable in a web browser - both locally but also remotely, via the VRM Servers.
  
 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".
Line 150: Line 159:
 For developers: source code for the node-red-contrib-victron modules is [[https://github.com/victronenergy/node-red-contrib-victron/|here]], and note that updating is not possible from either the Node-RED editor as the commandline. The recommended way to get to the new node-red-contrib-victron version is to await a new Venus OS large build.  For developers: source code for the node-red-contrib-victron modules is [[https://github.com/victronenergy/node-red-contrib-victron/|here]], and note that updating is not possible from either the Node-RED editor as the commandline. The recommended way to get to the new node-red-contrib-victron version is to await a new Venus OS large build. 
  
 +==== 5.4 Examples ====
  
-==== 5.2 Back-up and restore ====+Our most up to date library of examples can be accessed from within Node-RED. See the main menu (accessible from the top right), and then click Import. Or ctrl-i. 
 + 
 +{{ :venus-os:examples_node-red.png?direct |}} 
 + 
 +To see the examples when you don't have access to a Node-RED installation and flow-editor, see their copy here: https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows. 
 + 
 +==== 5.5 Back-up and restore ====
  
 Just as with other software it is important to keep your Node-RED flows save and secure. We advise you to periodically backup your flows using the palette manager "//Export -> all flows//" option to download the ''flows.json'' file to your PC.  Just as with other software it is important to keep your Node-RED flows save and secure. We advise you to periodically backup your flows using the palette manager "//Export -> all flows//" option to download the ''flows.json'' file to your PC. 
Line 161: Line 177:
 Do note that the above instruction only makes a backup of your flows, not of the Node-RED configuration. The configuration is stored in ''.config.*.json'' files under ''/data/home/nodered/.node-red/''.  Do note that the above instruction only makes a backup of your flows, not of the Node-RED configuration. The configuration is stored in ''.config.*.json'' files under ''/data/home/nodered/.node-red/''. 
  
-==== 5.3 Installing extra nodes ====+==== 5.6 Installing extra nodes ====
  
 Node-RED comes with a core set of useful nodes, but there are many more available from both the Node-RED project as well as the wider community. Node-RED comes with a core set of useful nodes, but there are many more available from both the Node-RED project as well as the wider community.
Line 183: Line 199:
 Make sure that there is always 30MB of free space remaining on the data partition. One of the [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows#monitor-disk-usage | example flows]] shows how to check the free space using a Node-RED dashboard .  Make sure that there is always 30MB of free space remaining on the data partition. One of the [[https://github.com/victronenergy/node-red-contrib-victron/wiki/Example-Flows#monitor-disk-usage | example flows]] shows how to check the free space using a Node-RED dashboard . 
  
-==== 5.4 Controlling relays ====+==== 5.7 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]]. 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]].
Line 218: Line 234:
 === Charger relays === === Charger relays ===
 The only charger which has a relay that is controllable is the Smart IP43 Charger. To use that for remote control, set its mode, using the VictronConnect app, to be remote controllable. Note that its use is limited: the relay is only powered (and thus only controllable) when the charger is switched on. It doesn't work when it's turned off with AC connected. This limitation applies to the 230V models as well as the later 120V/240V models. The only charger which has a relay that is controllable is the Smart IP43 Charger. To use that for remote control, set its mode, using the VictronConnect app, to be remote controllable. Note that its use is limited: the relay is only powered (and thus only controllable) when the charger is switched on. It doesn't work when it's turned off with AC connected. This limitation applies to the 230V models as well as the later 120V/240V models.
-==== 5.5 Node-RED Dashboard ====+==== 5.8 Node-RED Dashboard ====
  
 Besides the flow and automation functionally, Node-RED also offers a fully customisable dashboard. Including graphs, indicators as well as controls such as switches and sliders. Besides the flow and automation functionally, Node-RED also offers a fully customisable dashboard. Including graphs, indicators as well as controls such as switches and sliders.
Line 231: Line 247:
 {{ :venus-os:vrm_node_red_ui_step_3.png?direct&600 |VRM Node-RED UI - Step 3}} {{ :venus-os:vrm_node_red_ui_step_3.png?direct&600 |VRM Node-RED UI - Step 3}}
  
-==== 5.6 Configuration files ====+==== 5.9 Configuration files ====
  
 WARNING: the vast majority of systems using Node-RED will not, and should not (!), have to modify any of the files here described. Venus OS itself, including Venus OS large and Node-RED, is made such that its not necessary to dive into the command line. WARNING: the vast majority of systems using Node-RED will not, and should not (!), have to modify any of the files here described. Venus OS itself, including Venus OS large and Node-RED, is made such that its not necessary to dive into the command line.
Line 250: Line 266:
 For more information on such Node-RED configuration customisations, see https://nodered.org/docs/user-guide/runtime/configuration. For more information on such Node-RED configuration customisations, see https://nodered.org/docs/user-guide/runtime/configuration.
  
-==== 5.7. Ready-to-use solutions ====+==== 5.10 Ready-to-use solutions ====
  
 Node-RED can also be used for doing more advanced tasks. Some examples of ready-to-use solutions are: Node-RED can also be used for doing more advanced tasks. Some examples of ready-to-use solutions are:
Line 256: Line 272:
   * [[https://flows.nodered.org/node/node-red-contrib-eskomsepush|EskomSePush]] - use Node-RED for charging the batteries before the next load shedding happens (for South African users)   * [[https://flows.nodered.org/node/node-red-contrib-eskomsepush|EskomSePush]] - use Node-RED for charging the batteries before the next load shedding happens (for South African users)
  
-==== 5.8. Using data from VRM  ====+==== 5.11 Using data from VRM  ====
  
 For some flows it can be useful to retrieve data from the VRM Portal Database. For example to retrieve de Solar irradiation or yield forecasts. For some flows it can be useful to retrieve data from the VRM Portal Database. For example to retrieve de Solar irradiation or yield forecasts.
Line 281: Line 297:
 The [[https://flows.nodered.org/node/victron-vrm-api|Victron VRM API node]] makes it easy to use the VRM API from a Node-RED flow. Alternatively take a look at above mentioned Dynamic-ESS flow. The [[https://flows.nodered.org/node/victron-vrm-api|Victron VRM API node]] makes it easy to use the VRM API from a Node-RED flow. Alternatively take a look at above mentioned Dynamic-ESS flow.
  
-==== 5.9. Node-RED FAQ ====+==== 5.12 Node-RED FAQ ====
  
 === Q1: Write/read file gives "Error: EACCESS: permission denied' === === Q1: Write/read file gives "Error: EACCESS: permission denied' ===
Line 358: Line 374:
 === Q11: Is there a way to have the context survive reboots? === === 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 +By default the context is stored in RAM memory of the GX device only. When the GX device reboots or loses lower, the context information is lost.
-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: 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:
Line 374: Line 389:
   }   }
      
-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. +With the above settings, context files will get created periodically in ''/data/home/nodered/.nodered/context/''. In order not to wear out the flash memory too much, don't write too often. 
 ===== 6. Signal K ===== ===== 6. Signal K =====
  
Line 522: Line 537:
  
 ^ Enclosure label ^ Interface ^ Notes ^ ^ Enclosure label ^ Interface ^ Notes ^
-| VE.Can 1 | can0 | Isolated and default enabled in SignalK | +| VE.Can 1 | vecan0 | Isolated and default enabled in SignalK | 
-| VE.Can 2 | can1 | Non-isolated |+| VE.Can 2 | vecan1 | Non-isolated |
  
 === Ekrano GX === === Ekrano GX ===
  
 ^ Enclosure label ^ Interface ^ Notes ^ ^ Enclosure label ^ Interface ^ Notes ^
-| VE.Can 1 | vecan0 | Isolated |+| VE.Can 1 | vecan0 | Isolated and default enabled in SignalK |
 | VE.Can 2 | vecan1 | Non-isolated | | VE.Can 2 | vecan1 | Non-isolated |
 ==== 6.5 Signal K FAQ ==== ==== 6.5 Signal K FAQ ====
Line 651: Line 666:
 ==== 8.1 Disk space issues / data partition full ==== ==== 8.1 Disk space issues / data partition full ====
  
-Using both Signal K Server, as well as Node-RED, it is quite easy to completely fill up the data partition. Which can cause all sorts of issues, like:+Using both Signal K Server, as well as Node-RED, it is possible to completely fill up the data partition. 
 + 
 +The GX device will issue a warning, #46 Data partition full, as soon as the free space of the data partition is below 5%. 
 + 
 +To see the exact free space, go to Settings -> General -> Modifications. 
 + 
 +Having the data partition full will lead to unexpected results. The system is not built to be resilient for that. Some examples:
  
   - Venus OS itself no longer working correctly,   - Venus OS itself no longer working correctly,
Line 657: Line 678:
   - Node-RED refuses to start,   - Node-RED refuses to start,
   - and similar.   - and similar.
- 
-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]]. 
  
 Depending on what the issue is, there are a few things you can do: 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 details. Disadvantage is that you'll need to reconfigure the GX.+  - Remove all Node-RED flows and installed node palettes. See next chapter on how to do that.
   - 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.   - 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.
 +  - 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.
   - A more detailed approach is logging into the SSH console, and checking for disk space:   - A more detailed approach is logging into the SSH console, and checking for disk space:
  
Line 721: Line 741:
   * [[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]] - 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-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 only the SignalK log files
   * [[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.   * [[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.1729255068.txt.gz · Last modified: by mvader
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki