ve.can:changing_nmea2000_instances
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ve.can:changing_nmea2000_instances [2016-12-15 06:53] – mvader | ve.can:changing_nmea2000_instances [2023-06-28 13:32] (current) – Update links sloges | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== 1. Introduction ===== | ===== 1. Introduction ===== | ||
- | Instances are used in an NMEA2000 | + | ==== 1.1 Purpose of NMEA 2000 instances ==== |
+ | Instances are used in an NMEA 2000 network to identify multiple similar products connected on the same network. | ||
- | There are two types of instances: device instances | + | 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/ |
- | Both the device instance and the data instance of a product can easily be changed with both Maretron N2Kview as well as and Actisense PC software. This does require a canbus adapter for your computer. | ||
- | For more detailed information, | + | ==== 1.2 Different types of instances ==== |
- | And the main [[ve.can: | + | There various types of instances, and for marine systems are two that matter: |
- | ===== 2. Changing | + | Details and differences of each type are explained in detail in the [[https:// |
+ | |||
+ | **WARNING**: | ||
+ | |||
+ | Note that its only rarely necessary to change either device or data instances like the Fluid-, Battery- and DC-instance. See next section. | ||
+ | |||
+ | ==== 1.3 Recommend instancing setup for main MFD brands | ||
+ | |||
+ | The only common use case we encounter in testing and support where it is necessary to change instances is with older Raymarine hardware & software: | ||
+ | |||
+ | * Raymarine i70: max number of tank levels is 5; fluid instance 0-4 and type must be fuel. | ||
+ | * Raymarine i70s: max number of tank levels is 5; fluid instance 0-4 and type must be fuel. | ||
+ | * Axiom MFDs: per Lighthouse version 4.1.75, a maximum of 16 tanks can be connected; fluid instance 0-15. | ||
+ | |||
+ | Further details per brand are in these documents: | ||
+ | |||
+ | * [[venus-os: | ||
+ | * [[venus-os: | ||
+ | * [[venus-os: | ||
+ | * [[venus-os: | ||
+ | |||
+ | ==== 1.4 Different methods for setting up instances ==== | ||
+ | |||
+ | As the NMEA2000 protocol prescribes commands to change an instance | ||
+ | |||
+ | Besides the here described methods there are more, for example some MFDs allow changing instances as well. | ||
+ | |||
+ | - GX Device: Device- instances only | ||
+ | - Actisense software + NGT-1 USB: Device- as well as data-instances | ||
+ | - Maretron software + USB adapter: Unknown | ||
+ | - Commandline of a [[venus-os: | ||
+ | |||
+ | Chapter 2, 3, 4, 5 and 6 explain these methods in detail. | ||
+ | |||
+ | ==== 1.5 Further reading on Victron and NMEA 2000 ==== | ||
+ | |||
+ | * [[ve.can: | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | ===== 2. GX Device: changing device instances ===== | ||
+ | |||
+ | The Settings -> Services -> VE.Can -> Devices menu shows a list of all devices on the N2K / VE.Can network: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | By clicking the right button, a detailed menu is shown: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ===== 3. Actisense: changing device instances | ||
+ | |||
+ | Note: make sure to use a recent Actisense driver. Otherwise the instance might not ‘stick’. | ||
+ | |||
+ | Requires the [[http:// | ||
+ | |||
+ | Changing a device instance: | ||
- Open Actisense NMEA Reader | - Open Actisense NMEA Reader | ||
Line 22: | Line 80: | ||
{{: | {{: | ||
- | ===== 3. Changing a data instance with Actisense ===== | + | ===== 4. Actisense: changing data instances |
- | Changing | + | Requires |
- | Changing a data instance: | + | Step by step instructions: |
- Open Actisense NMEA Reader | - Open Actisense NMEA Reader | ||
- Select data view (tab selection is at the bottom left) | - Select data view (tab selection is at the bottom left) | ||
- | - Right click the PGN: {{:ve.can: | + | - Right click on the PGN number. Note that this will only work on PGNs that allow changing their data instance (first screenshot below) |
- | - And change the value: {{: | + | - And change the value (second screenshot below) |
- | Notes for BMVs, Lynx Shunt and the Lynx Ion + Shunt: | + | Notes: |
- | + | * The Battery Instance and the DC instance are the same value within Victron products. Changing one of them, will also change the other one. | |
- | * The Battery Instance and the DC Detailed | + | |
* Since the BMV sends out two voltages, the main voltage and the aux- or starter-voltage, | * Since the BMV sends out two voltages, the main voltage and the aux- or starter-voltage, | ||
+ | * Changing the fluid level instance using Actisense has a bug. Probably due Actisense seeing it as 8 bit number; while in the definition it is a 4 bit number. Work around: using the GX, set the fluid type to Fuel (0), then using Actisense change the fluid instance to the desired value, and then using your GX, set the type back to the desired type. | ||
+ | |||
+ | {{: | ||
- | ===== 4. Changing Instance Using Maretron N2KAnalyzer ===== | + | {{:ve.can: |
- | Maretron understands that it is sometimes difficult to know whether a particular product uses device instance or if it uses data instance to uniquely identify itself on an NMEA 2000 network. For this reason, Maretron uses a term called " | ||
- | Open N2KAnalyzer and make sure that the " | ||
- | {{:ve.can: | + | ===== 5. Maretron N2KAnalyzer ===== |
- | Within the N2KAnalyzer main window, any cell with a white background can be edited by clicking in the cell and typing in the desired value. You can see from the following screen shot that a few parameters have a white background including Label and Installation Description #1. To change a devices instance, click in the Unique Instance | + | Maretron uses a term called "Unique Instance" where the N2KAnalyzer software tool automatically determines if a particular |
- | {{:ve.can: | + | WARNING: At Victron we do not understand what and how the Maretron software works with regards to this. We advise to use another tool, not Maretron, so that you know what you are doing, ie know what instance you are changing. |
+ | So far, we have not been able to use Maretron software to change a data instance. And changing the other instance, the device instance | ||
- | ===== 5. Changing the DeviceInstance | + | ===== 6. Changing the instances |
- | Instead of using Actisense or Maretron software, it is also possible to change the device | + | |
+ | ==== 6.1 Introduction | ||
+ | Instead of using Actisense or Maretron software, it is also possible to change the VE.Can aka N2K Device | ||
+ | |||
+ | Once logged into the shell, follow below instructions. More back ground information of the used commands such as dbus and dbus-spy is found by reading about root access document. | ||
+ | |||
+ | ==== 6.2 Warning: better use an Actisense! ==== | ||
+ | |||
+ | Note that the methods explained in this Chapter 6 are usually not recommended. Use an Actisense instead, see chapters 3 and 4 instead. | ||
+ | |||
+ | ==== 6.3 New method - changing a Device instance ==== | ||
+ | |||
+ | All devices available on the canbus are enumerated under the com.victronenergy.vecan service. And for all devices that support the necessary can-bus commands, the Device instance can be changed. All Victron products support changing their Device instance; and most or all non-Victron products as well. | ||
+ | |||
+ | < | ||
+ | # dbus -y com.victronenergy.vecan.can0 / GetValue | ||
+ | value = { | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | [and so forth] | ||
+ | </ | ||
+ | |||
+ | To change them, do a SetValue call to the DeviceInstace path like below. Or, perhaps easier, use the dbus-spy tool. | ||
+ | |||
+ | These lines read it, then changes it to 1, then reads it again: | ||
+ | < | ||
+ | root@ccgx: | ||
+ | value = 0 | ||
+ | root@ccgx: | ||
+ | retval = 0 | ||
+ | root@ccgx: | ||
+ | value = 1 | ||
+ | |||
+ | [note that numbers, like can0, and 00002CC005EB can ofcourse be different on your system]. | ||
+ | </ | ||
+ | |||
+ | ==== 6.4 New method - changing Data instance ==== | ||
+ | |||
+ | This applies only the NMEA2000-out feature. See links on top of page for what the NMEA2000 out feature is. | ||
+ | |||
+ | The data instances used for the NMEA2000 out feature are stored in local settings. Here is a snippet of the lines, taken by using the dbus-spy tool that also allows changing entries: | ||
+ | |||
+ | The Data instances are the " | ||
+ | < | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | Settings/ | ||
+ | </ | ||
+ | |||
+ | ==== 6.5 Old method ==== | ||
+ | |||
+ | (Only allows changing Device instances - not data instances as used in the NMEA2000-out function) | ||
- | Once logged into the shell, follow below instructions. Note that the example shown changes the device instance of a Skylla-i. The device instance of a VE.Can connected MultiPlus or Quattro can be changed as well. It will show as '' | ||
Step 1. List the devices: | Step 1. List the devices: | ||
Line 79: | Line 228: | ||
Device instance changed successful! | Device instance changed successful! | ||
- | ===== DISQUS ===== | + | |
- | ~~DISQUS~~ | + |
ve.can/changing_nmea2000_instances.1481781188.txt.gz · Last modified: 2016-12-15 06:53 by mvader