Differences

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

--- venus-os:large [2024-07-14 16:53] – [8.1 Disk space issues / data partition full] mvader
+++ venus-os:large [2024-08-04 16:01] (current) – [6.4 CAN-bus ports] mvader
@@ Line 427: / Line 427: @@
 ==== 6.3 First use & configuring ====
-=== Step 1. Opening 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 1. Signal 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 2. Configure serial connections ===
+{{ :venus-os:img_2580.jpeg |}}
-Use this to, for example, configure a USB-connected NMEA0183 connection in SignalK. To do so, go to the dashboard (http://0.0.0.0:3000), and there to Server -> Connections.
+=== Step 2. Set 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. Vessel information ===
+Go to Settings and enter some basic information about your boat.
+{{ :venus-os:img_9926.png |}}
+=== Step 4. NMEA2000 Can-bus connection ===
+For NMEA2000 networks, its 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”.
-=== Step 3. Configure can-bus connections ===
+Signal K is preconfigured to have its port operational for this.
-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:
+Here is how you can see the preconfigured connection in the Signal K Dashboard:
 ;#;
@@ Line 449: / Line 461: @@
 ;#;
-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 remain configured as a 250kbit VE.Can & NMEA2000 port in the Remote Console:
 ;#;
@@ Line 457: / Line 469: @@
 For more information on CAN-busses, see chapter 6.4.
-=== Step 4. Adding Signalk Plugins or Webapps ===
+=== Step 5. Optional: Configure NMEA0183 serial connections ===
-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
+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 ====
@@ Line 484: / Line 524: @@
 | 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 ====