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 [2021-03-15 17:31] – [1.1 Summary] mvader | ve.can:nmea-2000:start [2022-03-16 12:19] (current) – [3.4 DC Voltage compatibility] stefanie | ||
---|---|---|---|
Line 4: | Line 4: | ||
==== 1.1 Summary ==== | ==== 1.1 Summary ==== | ||
- | This technical | + | This document explains how to integrate a Victron system onto a marine |
- | There are multiple options, and how to best integrate depends on the customer requirements, | + | There are multiple options, and how to best integrate depends on the customer requirements, |
Make sure to closely read this full document to find the best method for your type of system. | Make sure to closely read this full document to find the best method for your type of system. | ||
- | {{: | + | {{: |
==== 1.2 What is NMEA 2000? ==== | ==== 1.2 What is NMEA 2000? ==== | ||
- | NMEA2000 | + | NMEA 2000 is a communications standard used for connecting marine sensors and display units within ships and boats. |
Victron Energy is a member of the NMEA 2000 organisation, | Victron Energy is a member of the NMEA 2000 organisation, | ||
Line 19: | Line 19: | ||
==== 1.3 What is the MFD HTML5 App? ==== | ==== 1.3 What is the MFD HTML5 App? ==== | ||
- | The MFD HTML5 App is a very simple to install and setup integration into all main marine MFD brands, including Raymarine, Garmin, Navico and Furuno. Truly plug-and-play: | + | The MFD HTML5 App is a simple to install and setup integration into all main marine MFD brands, including Raymarine, Garmin, Navico and Furuno. Truly plug-and-play: |
==== 1.4 Other integration options ==== | ==== 1.4 Other integration options ==== | ||
Line 26: | Line 26: | ||
First of all Modbus-TCP. Typically used on larger vessels, Modbus-TCP is a protocol commonly used for (custom) designed SCADA systems. The Victron GX devices all support the Modbus-TCP protocol. More information in the [[ccgx: | First of all Modbus-TCP. Typically used on larger vessels, Modbus-TCP is a protocol commonly used for (custom) designed SCADA systems. The Victron GX devices all support the Modbus-TCP protocol. More information in the [[ccgx: | ||
- | The other alternative is SignalK. More information about that in the [[venus-os: | + | The other alternative is SignalK. More information about that in the [[venus-os: |
===== 2. Integration details ===== | ===== 2. Integration details ===== | ||
Line 34: | Line 34: | ||
For most installations and integrations, | For most installations and integrations, | ||
- | There are two ways to connect a GX Device to a MFD: | + | The GX devices offer both above introduced integration options: NMEA2000 as well as the Victron HTML5 App. |
- | - the (simpler) plug and play like method uses an Ethernet connection, which enables the MFD HTML5 App. Available | + | The HTML5 integration is available |
- | - in an the NMEA2000 network. See the [[https:// | + | |
- | Both connections | + | When connected to the onboard NMEA2000 network, the GX Device |
- | The MFD HTML5 App is the simplest | + | Both the NMEA2000 and HTML5 App/ |
+ | |||
+ | Each has its advantages and disadvantages, | ||
+ | |||
+ | The MFD HTML5 App is the simpler one to setup as its plug and play. It presents an easy to use system overview without requiring any configuration. The system overview shown will automatically adapt to the type of Victron system installed. The (only) available configuration is defining the batteries as well as giving them names. | ||
The NMEA 2000 integration is more complex, and allows more customisation on the MFD: the data will show up in the data-tree of the MFD, and most MFDs then allow the user to configure various pages and combinations of information. | The NMEA 2000 integration is more complex, and allows more customisation on the MFD: the data will show up in the data-tree of the MFD, and most MFDs then allow the user to configure various pages and combinations of information. | ||
- | Note that, besides making information available on NMEA 2000, a GX Device can also read tank level data from NMEA 2000. More information in [[https:// | + | As mentioned above, a GX Device can also read tank level data from NMEA 2000. More information in the [[https:// |
==== 2.2 Products with a VE.Can port ==== | ==== 2.2 Products with a VE.Can port ==== | ||
- | Some of our products feature a VE.Can port; which can be directly connected to the NMEA 2000 network. No electronic converter is necessary. The conversion cable required is the [[https:// | + | All Victron |
- | These products include our Skylla-i | + | * Skylla-i |
+ | * Skylla IP65 Battery Chargers | ||
+ | * Lynx Shunt VE.Can | ||
+ | * Lynx Smart BMS | ||
+ | * SmartSolar MPPT Solar Chargers with VE.Can communications port | ||
- | ==== 2.3 Tank monitoring ==== | + | {{ :ve.can: |
- | When discussing integration of tank level data, there are two topics to separate: one is to have tank levels measured by a Victron tank level adapter sent out to the NMEA2000 network, to display on an MFD for example. | + | ==== 2.3 Tank monitoring integration ==== |
- | And the other is for Victron monitoring systems to read tank level data available on the NMEA2000 network | + | The GX devices can measure |
- | Both are possible. | + | Below sections explain the details of each integration type. |
=== Integration A) GX Device to MFD and NMEA2000 === | === Integration A) GX Device to MFD and NMEA2000 === | ||
Line 65: | Line 72: | ||
Some of Victron GX monitoring products feature built-in tank level inputs. For example the [[https:// | Some of Victron GX monitoring products feature built-in tank level inputs. For example the [[https:// | ||
- | Besides the built-in tank level inputs, all GX devices can also have their number and types of tank level inputs expanded by adding one or multiple [[https:// | + | Also, all GX devices can also have their number and types of tank level inputs expanded by adding one or multiple [[https:// |
All tank level inputs feature customisable naming, setting a type (fresh water, fuel, black water and more), configurable filtering and damping settings as well as setting up a custom tank shape for non-square tanks. | All tank level inputs feature customisable naming, setting a type (fresh water, fuel, black water and more), configurable filtering and damping settings as well as setting up a custom tank shape for non-square tanks. | ||
- | The GX Device can transmitted to the resulting tank levels to the NMEA2000 network. See the [[https:// | + | The GX Device can transmit |
=== Integration B) NMEA2000 to GX Device and VRM Portal === | === Integration B) NMEA2000 to GX Device and VRM Portal === | ||
Line 79: | Line 86: | ||
Compatible tank senders are listed in the [[https:// | Compatible tank senders are listed in the [[https:// | ||
- | TODO ADD SCREENSHOTS | + | {{ : |
- | ==== 2.4 Using our converter interfaces (DEPRECATED!) ==== | + | //Above picture: GX Touch 50, showing multiple tank levels. Coming from either the NMEA2000 network, directly connected resistive tank senders or via the GX Tank 140 accessory.// |
+ | |||
+ | //Below screenshot shows a similar system, but then on the [[https:// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== 2.4 NMEA 2000 GPS integration ==== | ||
+ | |||
+ | Our GX devices can read location, altitude, speed and course from the NMEA2000 network. For details, see the GX manual. | ||
+ | |||
+ | Note the other way around does not work. A GX Device which has a USB GPS installed does not emit GPS data out onto the NMEA2000 network as part of the NMEA2000-out function. | ||
+ | |||
+ | ==== 2.5 Using our converter interfaces (DEPRECATED!) ==== | ||
* [[https:// | * [[https:// | ||
Line 88: | Line 107: | ||
Note that the use of both those interfaces is deprecated. Use a GX device instead. | Note that the use of both those interfaces is deprecated. Use a GX device instead. | ||
+ | ===== 3. NMEA2000 Details ===== | ||
+ | ==== 3.1 PGN Lists ==== | ||
+ | Refer to our [[https:// | ||
+ | ==== 3.2 NMEA 2000 instancing ==== | ||
- | ===== 3. Varia ===== | + | NMEA 2000 Instances are used to identify multiple similar products connected on the same network. |
+ | There are several types of instances, the most important ones being the **Device instance** as well as the **Data instances**. | ||
- | ==== 3.1 VE.Can products (Skylla-i, Skylla-IP44, Lynx Shunt, Lynx Ion+Shunt and more) ==== | + | More information about instances is in [[https:// |
- | Since the Victron VE.Can communication protocol is based on N2K, the following products can all be connected directly to a N2K network. The only thing necessary is a plug converter: the [[https:// | + | === What settings need to be made? For example instances? === |
- | * Skylla-i 24V Battery Chargers | + | That is a commonly asked question. The answer depends on the used brand of MFD: |
- | * Skylla IP44 Battery Chargers | + | |
- | * Lynx Shunt Battery Monitors | + | |
- | * Lynx Ion + Shunt all models | + | |
- | * SmartSolar MPPT Solar Chargers with VE.Can communications port | + | |
- | {{ :ve.can: | + | |
+ | For **Garmin, Furuno, Maretron and Navico (B&G, Lowrance, Simrad) systems**: none. No instances, also not data instances such as the DC Detailed instance, need to be changed. It all works out of the box, other than configuring what field to show where on the MFD. | ||
+ | For **Raymarine**, | ||
- | ==== 3.2 Raymarine & EmpirBus | + | ==== 3.3 Terminators and network layout |
- | Besides | + | A N2K CAN-bus network needs to be laid out as in a backbone configuration, |
- | In the [[http://www.empirbus.com/clickOnce/EmpirBusStudio-Demo/|EmpirBus Studio software]] you will find dedicated Victron building blocks than can be drawn onto the diagram. | + | * Use the NMEA 2000 cable as the backbone. |
+ | * Run a separate drop cable separately to each Victron device | ||
+ | * Only terminate | ||
- | Next, use the [[http:// | + | Or: |
- | The EmpirBus system requires | + | * Have the N2K network on one side, with one terminator. On the other end, change |
+ | The first option is more aligned with the official N2K method. But, in case of multiple Victron products that need to be connected to the N2K network, will require more wire runs and definitively more NMEA2000 to VE.Can conversion cables. | ||
+ | ==== 3.4 DC Voltage compatibility ==== | ||
- | ==== 3.3 Maretron ==== | + | The Victron VE.Can network accepts 9 to 70VDC. |
- | All data sent out by Victron devices can be picked up by the Maretron MFDs & software. See the [[http:// | + | 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, |
- | ===== 4. NMEA2000 PGN overview ===== | + | 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. |
- | Refer to our [[https:// | + | Therefore, it is important |
- | ===== 5. FAQ ===== | + | The Victron cable used to connect both networks together, the [[https:// |
- | Note that there are many more generic frequently asked questions answered in the [[https:// | + | ==== 3.5 Further reading on Victron |
- | ==== Q1: What about instances? Device instances, data instances? ==== | + | * [[https:// |
+ | * [[https:// | ||
+ | * [[https:// | ||
- | See [[ve.can: | + | ===== 4. Varia ===== |
- | ==== Q2: What about terminators and network layout? | + | ==== 4.1 Raymarine & EmpirBus |
- | A N2K CAN bus network needs to be laid out as in a backbone configuration, | + | Besides |
- | * Use the NMEA 2000 cable as the backbone. | + | In the [[https:// |
- | * Run a separate drop cable separately to each Victron device. The drop cable will be one of these three products: | + | |
- | * [[https:// | + | Next, use the [[http://www.empirbus.com/#empirbus-graphic|EmpirBus Graphical tool]] to design the pages for on the Raymarine MFDs. |
- | | + | |
- | | + | The EmpirBus system requires the data instance of battery status and dc detailed status to be unique when using multiple sources. ([[ve.can: |
- | * Only terminate the NMEA 2000 backbone, do not terminate on the VE.Can side. | + | |
+ | ==== 4.2 Maretron ==== | ||
+ | |||
+ | All data sent out by Victron devices on the N2K 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]]. | ||
+ | |||
+ | ===== 5. FAQ ===== | ||
+ | |||
+ | === Q1: Can/must both Ethernet and and N2K connection be made between Victron GX and MFD? === | ||
+ | |||
+ | Both can be made at the same time. | ||
- | ==== Q3: What PGNs does a GX Device transmit on N2K? ==== | + | Ethernet is needed to get the MFD App, as explained above. |
- | See the [[https:// | + | And an N2K connection is needed to get data to show in other fields on the MFD. |
- | ==== Q4: Can integration onto Raymarine displays also be done without Empirbus NXT? ==== | + | See annotated screenshot above for which is what. |
- | Yes, see [[https:// |
ve.can/nmea-2000/start.1615825915.txt.gz · Last modified: 2021-03-15 17:31 by mvader