venus-os:large
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
venus-os:large [2023-12-21 10:42] – external edit 127.0.0.1 | venus-os:large [2024-06-24 21:08] – dfaber | ||
---|---|---|---|
Line 120: | Line 120: | ||
===== 5. Node-RED ===== | ===== 5. Node-RED ===== | ||
- | {{ : | + | {{: |
==== 5.1 Introduction ==== | ==== 5.1 Introduction ==== | ||
Line 129: | Line 129: | ||
A good tutorial on how to work with Node-RED is here: https:// | A good tutorial on how to work with Node-RED is here: https:// | ||
- | 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:// | [[https:// | ||
Line 142: | Line 144: | ||
The Node-RED editor can be accessed from your LAN at https:// | The Node-RED editor can be accessed from your LAN at https:// | ||
- | __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:// | 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:// | ||
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:// | ||
+ | |||
+ | ;#; | ||
+ | {{: | ||
+ | ;#; | ||
=== GX Device relays === | === GX Device relays === | ||
Line 197: | Line 206: | ||
=== SolarCharger MPPT Relay === | === SolarCharger MPPT Relay === | ||
- | Currently it is not possible | + | In order to switch |
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 controllable. Will be controllable in the future. | + | First set the relay to //manual control// using VictronConnect. Once that has been done, the relay can be controlled using Node-RED. |
=== Charger relays === | === Charger relays === | ||
Line 325: | Line 334: | ||
export NODE_EXTRA_CA_CERTS=/ | export NODE_EXTRA_CA_CERTS=/ | ||
+ | | ||
=== 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// | The input nodes send out a message on each value change. If the ‘//only changes// | ||
+ | === 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 ''/ | ||
+ | |||
+ | module.exports = { | ||
+ | /* Make sure that we also listen on port 1880 on all interfaces */ | ||
+ | | ||
+ | } | ||
+ | |||
+ | 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:// | ||
+ | |||
+ | module.exports = { | ||
+ | contextStorage: | ||
+ | default: { | ||
+ | module: " | ||
+ | config: { | ||
+ | flushInterval: | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | | ||
+ | With the above settings, context files will get created periodically in ''/ | ||
===== 6. Signal K ===== | ===== 6. Signal K ===== | ||
Line 381: | Line 420: | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
- | * [[http://slack-invite.signalk.org/|Signal K Slack]] - a real time chat group including a special Victron channel. | + | * [[https://discord.gg/uuZrwz4dCS |
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.4 First use & configuring ==== | + | ==== 6.3 First use & configuring ==== |
=== Step 1. Opening the dashboard === | === Step 1. Opening the dashboard === | ||
Line 404: | Line 443: | ||
=== 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 " | + | For the Venus GX, and Cerbo GX, SignalK comes pre-configured with a NMEA2000 listener for the VE.Can ports, its named " |
;#; | ;#; | ||
{{: | {{: | ||
;#; | ;#; | ||
- | |||
Note that, to keep that operational, | Note that, to keep that operational, | ||
Line 417: | Line 455: | ||
;#; | ;#; | ||
+ | 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 461: | ||
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:// | 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:// | ||
+ | ==== 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, | ||
+ | |||
+ | 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: | ||
==== 6.5 Signal K FAQ ==== | ==== 6.5 Signal K FAQ ==== | ||
Line 552: | Line 616: | ||
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:// | 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:// | ||
- | The easy solution | + | Depending on what the issue is, there are a few things you can do: |
- | A more detailed approach is logging in on SSH, and checking for disk space. Here are a 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; |
+ | - 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, | ||
+ | - A more detailed approach is logging in on SSH, and checking for disk space: | ||
+ | |||
+ | **Tips and tricks to login a diagnose disk space** | ||
+ | |||
+ | Require root access: https:// | ||
The '' | The '' | ||
Line 600: | Line 670: | ||
744 / | 744 / | ||
</ | </ | ||
+ | |||
+ | ==== 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:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | See [[https:// |
venus-os/large.txt · Last modified: 2024-08-04 16:01 by mvader