ve.can:nmea-2000:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ve.can:nmea-2000:start [2020-01-06 22:58] – [1. Introduction] mvader | ve.can:nmea-2000:start [2025-07-19 07:29] (current) – [3.2 NMEA 2000 instances] mvader | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
===== 1. Introduction ===== | ===== 1. Introduction ===== | ||
- | This document explains how to integrate a Victron system onto a Marine MFD, such as from Garmin, Raymarine Navico and other brands. | + | ==== 1.1 Summary ==== |
- | This are multiple ways to do such an integration; | + | This guide provides |
- | For all new installations, we recommend to use one of our [[venus-os:start|GX Products]]. It acts as a hub, collecting information from connected equipment | + | * **MFD (Chart Plotter) Monitoring**: |
+ | * **Tank Level Monitoring**: Seamlessly integrate tank level data between the NMEA 2000 network, Victron | ||
+ | * **NMEA2000-out feature**: Share tank data, as well as other data such as Battery, DC & AC system data from GX devices | ||
+ | * **GPS Integration**: | ||
+ | * **Advanced features powered by Signal K**: Includes wireless AIS, anchor alarms, and automatic trip logging. | ||
- | A GX Device can connected to a Marine MFD in two ways. One is by connecting it to the NMEA2000 network, N2K. N2K is is a plug-and-play communications standard used for connecting marine sensors and display units within ships and boats. | + | This document serves as a high-level overview with links to relevant manuals |
- | Victron Energy is a member of the NMEA 2000 organisation, | + | ==== 1.2 MFD Integration ==== |
- | For brevity, this document will refer to NMEA 2000 as N2K. | + | Integration with MFDs depends on customer requirements and equipment used. A GX device (e.g., Cerbo GX or Ekrano GX) is typically involved, with two main options: |
- | ===== 1. How to connect to a NMEA 2000 network | + | - **NMEA 2000 Integration**: |
+ | - **HTML5 App Integration**: | ||
- | ==== 1.1 Multis, MultiPlusses and Quattros ==== | + | **Comparison of Options:** |
- | Use the [[https:// | + | |
- | === Combining with a Color Control GX === | + | - **NMEA 2000**: Offers customizable data pages on the MFD but requires more configuration. |
- | Monitoring and controlling these products from both to a N2K network and a Color Control GX is possible. In that case, do not connect | + | - **HTML5 App**: Plug-and-play with an auto-configured system overview but less customizable. |
- | Schematic diagram of combining a CCGX with NMEA 2000: | + | **Illustration**: |
- | {{ : | + | |
- | In above example, there needs to be a fuse in the [[https://nocache.victronenergy.com/ | + | {{ :ve.can:nmea-2000: |
- | === Limitations === | + | * Right bar: NMEA 2000 data. |
+ | * Bottom: HTML5 App integration. | ||
- | When the Multis/ | + | === Further reading by brand === |
- | * Incompatible with Hub-4 and ESS Assistant, for Energy Storage Systems | + | * [[https:// |
- | * Listing the VE.Bus installed Assistants on the CCGX / VRM Portal does not work | + | * [[https:// |
- | * Alarm information per phase does not work (generic alarm information still works) | + | * [[https:// |
- | * Forwarding charge-current information of MPPTs to the VE.Bus system does not work. Solution: always install a BMV, which is needed anyway in a Marine installation. | + | * [[https:// |
- | Setting On/ | + | ==== 1.3 Tank monitoring |
- | ==== 1.2 BMV Battery Monitors | + | |
- | Use the [[https:// | + | |
- | Combining this with a CCGX on the same network is possible. Connect the CCGX to the N2K network | + | The Victron GX devices offer a user-friendly **Tank Level Page** |
- | {{ : | + | |
+ | **Key Features:** | ||
+ | * Monitor tank levels on the GX device and VRM Portal. | ||
+ | * Access NMEA 2000 tank data or share GX tank data with NMEA 2000. | ||
+ | * Customize tank naming, shapes, and damping for accurate readings. | ||
+ | * Expand capabilities with the [[https:// | ||
- | ==== 1.3 VE.Can products (Skylla-i, Skylla-IP44, | + | **Visual Examples:** |
- | Since the Victron VE.Can communication protocol | + | {{ : |
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ** Video that demonstrates | ||
+ | |||
+ | | ||
+ | |||
+ | |||
+ | === Further details === | ||
+ | * **Resistive tank level inputs built-in to the Cerbo GX and Ekrano GX:** See [[https:// | ||
+ | * **Reading data from NMEA 2000 Tank senders into the GX Device and VRM Portal:** The GX device can read tank level data from compatible sensors on the NMEA 2000 network. This information | ||
+ | * **Transmitting GX tank levels to the NMEA 2000 network:** For vessels with advanced monitoring setups, the GX device | ||
+ | |||
+ | ==== 1.4 NMEA2000-out feature ==== | ||
+ | |||
+ | Victron Energy GX devices feature an NMEA 2000-out function: when enabled, the GX device acts as a bridge: it makes the data of all connected | ||
+ | |||
+ | Using that feature, and having the GX device connected | ||
+ | |||
+ | |||
+ | ==== 1.5 Advanced features powered by Signal K ==== | ||
+ | |||
+ | Signal K unlocks powerful features: | ||
+ | * **Wireless AIS & Navigation Data**: Share NMEA 2000 data via WiFi for apps like Navionics. | ||
+ | * **Anchor Alarm**: Reliable and easy-to-use alarm. | ||
+ | * **Automatic Logbook**: Track journeys effortlessly. | ||
+ | |||
+ | More details: | ||
+ | - [[https:// | ||
+ | - [[https:// | ||
+ | |||
+ | ==== 1.5 Modbus-TCP, mostly for SCADA systems ==== | ||
+ | |||
+ | Ideal for larger vessels, the GX built-in Modbus-TCP server enables SCADA system integration. For more details, see the [[https:// | ||
+ | |||
+ | ===== 2. Integration details by Victron product ===== | ||
+ | |||
+ | ==== 2.1 Systems with a GX Device ==== | ||
+ | |||
+ | For most installations and integrations, | ||
+ | |||
+ | ==== 2.2 Other products featuring a VE.Can port ==== | ||
+ | |||
+ | All Victron products that feature a VE.Can port can be directly connected to the NMEA 2000 network, using the [[https:// | ||
* Skylla-i 24V Battery Chargers | * Skylla-i 24V Battery Chargers | ||
- | * Skylla | + | * Skylla |
- | * Lynx Shunt Battery | + | * Lynx Shunt VE.Can |
- | * Lynx Ion + Shunt all models | + | * Lynx Smart BMS |
* SmartSolar MPPT Solar Chargers with VE.Can communications port | * SmartSolar MPPT Solar Chargers with VE.Can communications port | ||
- | {{ : | + | * Multi RS |
+ | * Inverter RS | ||
- | ===== 2. MFD integration ===== | + | {{ :ve.can: |
- | Using the NMEA 2000 protocol, Victron equipment can be integrated in many multi function displays. Such as the ones from Maretron, Raymarine, Garmin | + | ==== 2.3 VE.Bus |
- | Note: working on a very large yacht featuring custom Scada and PLC networks? Consider integrating the Victron system with [[ccgx:modbustcp_faq|ModbusTCP]] instead of NMEA 2000. | + | * [[https:// |
+ | * [[https:// | ||
- | ==== 2.1 Raymarine & EmpirBus ==== | + | Note that the use of both those interfaces is deprecated. Use a GX device instead. |
- | Integration onto Raymarine MFDs is always done with an [[http:// | + | ===== 3. NMEA 2000 Details ===== |
- | In the [[http:// | + | ==== 3.1 PGN Lists ==== |
- | Next, use the [[http://www.trigentic.com/#empirbus-graphic|EmpirBus Graphical tool]] to design the pages for on the Raymarine MFDs. | + | Refer to our [[https://www.victronenergy.com/upload/ |
- | The EmpirBus system requires the data instance of battery status and dc detailed status to be unique when using multiple sources. ([[ve.can: | + | ==== 3.2 NMEA 2000 instances |
- | {{ : | + | |
- | ==== 2.2 Maretron | + | |
- | All data sent out by Victron devices can be picked up by the Maretron MFDs & software. See the [[http:// | + | Instances are used in an NMEA 2000 network to identify multiple similar products connected to the same network. |
- | ===== 3. PGN overview | + | As an example, take a system with two battery monitors (one for the main battery bank, and another for the hydraulic-thruster bank) and also a Quattro inverter/ |
+ | |||
+ | There are various types of instances, and for marine systems are two that matter: the Device instance and the Data instance. The Data instance goes by various different names, like Fluid instance, Battery instance and DC instance. | ||
+ | |||
+ | NMEA 2000 defines three different instances: | ||
+ | |||
+ | * Data instances (Battery instance, Fluid instance, and similar) | ||
+ | * Device instance | ||
+ | * System instance | ||
+ | |||
+ | === When is manual configuration of instances needed? === | ||
+ | |||
+ | * For **Garmin, Furuno, Maretron and Navico (B&G, Lowrance, Simrad) systems**: no configuration needed. Required fields can be configured and selected on the MFD, usually by pressing and holding on a data field in the data bar until the selection pane comes up. | ||
+ | * For **Raymarine**, | ||
+ | |||
+ | === Further reading on NMEA 2000 instances === | ||
+ | |||
+ | * [[https:// | ||
+ | * [[ve.can: | ||
+ | ==== 3.3 Terminators and network layout | ||
+ | |||
+ | A NMEA 2000 CAN-bus network needs to be laid out as in a backbone configuration, | ||
+ | |||
+ | * Use the NMEA 2000 cable as the backbone. | ||
+ | * Run a separate drop cable separately to each Victron device [[https:// | ||
+ | * Only terminate the NMEA 2000 backbone. Do not install a terminator in any of the VE.Can ports on the Victron products. | ||
+ | |||
+ | Or: | ||
+ | |||
+ | * Have the NMEA 2000 network on one side, with one terminator. On the other end, change to the Victron network, with also one (Victron) terminator at the end. | ||
+ | |||
+ | The first option is more aligned with the official NMEA 2000 method. But, in case of multiple Victron products that need to be connected to the NMEA 2000 network, will require more wire runs and definitively more NMEA 2000 to VE.Can conversion cables. | ||
+ | ==== 3.4 DC Voltage compatibility ==== | ||
+ | |||
+ | The Victron VE.Can network accepts 9 to 70VDC. | ||
+ | |||
+ | The NMEA-2000 network used to be 9 to 16VDC, which is, or will be, expanded to also include 24V. Which means that some NMEA-2000 devices are 9 to 16VDC, some are 9 to 30VDC, and some allow higher voltages. | ||
+ | |||
+ | Also, the Victron VE.Can network will (in most cases) be powered with battery voltage. So for a 48V system, the voltage on the VE.Can network **exceeds** the NMEA-2000 accepted voltage levels. | ||
+ | |||
+ | Therefore, it is important to **not** connect those power cables. | ||
+ | |||
+ | The Victron cable used to connect both networks together, the [[https:// | ||
- | Refer to our [[https:// | ||
- | ===== 4. FAQ ===== | ||
- | Note that there are many more generic frequently asked questions answered in the [[https:// | + | ==== 3.5 Galvanic isolation ==== |
- | === Q1: What about instances? Device instances, data instances? === | + | When connecting a GX to an NMEA 2000 network, it is recommend to do so using a galvanically isolated CAN-Bus port. |
- | See [[ve.can:changing_nmea2000_instances|]] for details on that. | + | This is especially the case when your NMEA backbone and GX are powered from separate power sources or do not share a common ground. These are the two most popular models that feature such galvanically isolated port: |
- | === Q2: Can MPPT Solar Chargers with a VE.Direct | + | * Cerbo GX MK2 (launched in 2024 as a successor to the Cerbo GX which did not feature an isolated |
+ | * Ekrano GX | ||
- | No, they cannot be connected. Even though the [[https:// | + | On both above products, VE.Can port 1 has galvanic isolation. VE.Can port 2 does not. |
- | Similarly, also a GX Device does not (yet) transmit data from connected Solar Chargers on its NMEA2000-out port. | + | For a full list of which ports feature isolation, see [[https:// |
+ | ==== 3.6 Further reading on Victron and NMEA 2000 ==== | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
- | === Q3: What about terminators and network layout? === | ||
- | A N2K CAN bus network needs to be laid out as in backbone configuration, | + | ===== 4. Maretron ===== |
- | * Use the NMEA2000 cable as the backbone. | + | All data sent out by Victron devices on the NMEA 2000 network can be picked up by the Maretron MFDs & software. See the [[http://www.maretron.com/products/N2KView.php|Maretron N2KView® vessel monitoring and control software]]. |
- | * Run a separate drop cable separately to each Victron device. The drop cable will be one of these three products: | + | |
- | * [[https://www.victronenergy.com/accessories/ve-bus-to-nmea2000-interface|VE.Bus to NMEA 2000 interface]] | + | |
- | * [[https:// | + | |
- | * [[https:// | + | |
- | * Only terminate the NMEA 2000 backbone, do not terminate on the VE.Can side. | + | |
- | === Q4: What PGNs does the Color Control GX transmit on N2K? === | + | ===== 5. FAQ ===== |
- | Nothing. At the moment the CCGX only reads data from the NMEA 2000 network. The data it can read is: | + | === Q1: Can or must both Ethernet and and NMEA 2000 connection be made between Victron GX and MFD? === |
- | * Victron Inverter/ | + | Both can be made at the same time. |
- | * Victron Battery monitor data | + | |
- | * Victron BMS data | + | |
- | * Victron Tank sender data as well as tank sender data from other manufacturers. See chapter 1.4.7 in the [[ccgx: | + | |
- | === Q5: Can integration onto Raymarine displays also be done without Empirbus NXT? === | + | Ethernet is needed to get the MFD App, as explained above. |
- | Yes, see [[https:// | + | And an NMEA 2000 connection is needed to get data to show in other fields |
- | === Q6: What about Maretron and other brand tank sensors on the Ccgx? === | + | See annotated screenshot above for which is what. |
- | See chapter 1.4.7 in the [[ccgx: | ||
- | ===== DISQUS ===== | ||
- | ~~DISQUS~~ |
ve.can/nmea-2000/start.1578347914.txt.gz · Last modified: by mvader