Differences

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

--- venus-os:extended [2020-06-17 00:11] – [Appendix A - Repartitioning Venus GX flash memory] mvader
+++ venus-os:extended [2020-09-12 09:42] – [6.2 Node-RED Dashboard/User Interface] mcorluka
@@ Line 38: / Line 38: @@
 ===== 3. Requirements =====
+==== 3.1 GX Device compatibility ====
 A compatible GX device:
@@ Line 49: / Line 51: @@
 Venus OS extended 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 ====
+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.
+Ofcourse, how intensive depends on what kind of flows (node-red) or how many messages & handling of them (SignalK) happens in the system.
+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.
+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.
+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 =====
@@ Line 241: / Line 257: @@
 Tbd. Actually a NMEA0183-network is probably something that doesnt exist: you can't have NMEA0183 in a network, its point to point.
+===== 6. Remote access via VRM =====
+==== 6.1 Node-RED flow editor and Signal K ====
+It it possible to access Node-RED flow editor and Signal K remotely via VRM - the interface and functionality is identical to access via LAN (ie. via **http://venus.local:1880** or **http://venus.local:3000**) .
+=== Step by step instructions ===
+  * **Step 1.** Log into/open the regular VRM 'dashboard' or 'advanced' page for the site
+{{ :venus-os:vrm_node_red_step_1.png?direct&600 |VRM Node-RED - Step 1}}
+  * **Step 2.** Modify the URL to include **/proxy/** after the site URL ID number (note that the last **/** is required)
+  As an example: **https://vrm.victronenergy.com/installation/12345/proxy/** where **12345** is the unique site URL ID
+{{ :venus-os:vrm_node_red_step_2.png?direct&600 |VRM Node-RED - Step 2}}
+  * **Step 3.** Click on the **Node-RED** or **Signal K** button in the Proxy relay screen; depending on location and the speed of internet connection, there may be a short delay while loading
+{{ :venus-os:vrm_node_red_step_3a.png?direct&600 |VRM Node-RED - Step 3a}}
+{{ :venus-os:vrm_node_red_step_3b.png?direct&600 |VRM Node-RED - Step 3b}}
+  * **Step 4.** The Node-RED flow editor or Signal K interface screen will appear
+{{ :venus-os:vrm_node_red_step_4.png?direct&600 |VRM Node-RED - Step 4}}
+==== 6.2 Node-RED Dashboard/User Interface ====
+It it also possible to access the Node-RED dashboard/User Interface remotely via VRM - the interface and functionality is identical to access via LAN (ie. via **http://venus.local:1880/ui**)
+=== Step by step instructions ===
+  * **Step 1.** Follow steps #1 to 4 in section 6.1 above in order to 'open' the remote connection
+  * **Step 2.** The 'new' proxy URL needs to be modified to include **/ui** after **.....victronenergy.com**
+  As an example: **https://12345-nodered.proxyrelay3.victronenergy.com/ui** where **12345** is the unique site URL ID
+{{ :venus-os:vrm_node_red_ui_step_2.png?direct&600 |VRM Node-RED UI - Step 2}}
+  * **Step 3.** The Node-RED dashboard/user interface screen will appear
+{{ :venus-os:vrm_node_red_ui_step_3.png?direct&600 |VRM Node-RED UI - Step 3}}
 ===== Appendix A - Repartitioning Venus GX flash memory =====