Instances are used in an NMEA2000 network to identify multiple similar products connected on the same network. As an example, take a system with two battery monitors, one for the main battery bank, and another for the hydraulic-thruster bank. All the displays in the network need to be able to address both of them separately.

There are two types of instances: device instances and data instances. And depending on the make and model of the displays being used (Garmin, Maretron, Raymarine, etcetera), you need to change one of them or both. This page explains how to change these instances.

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, see also the FAQ in our Data communication whitepaper.

And the main NMEA2000 integration guide.

1. Open Actisense NMEA Reader
2. Select the network view (tab selection is at the bottom left)
3. Select the product whose device instance you want to change
4. Select the properties tab at the bottom right and change the device instance

Changing the data instance is possible with Actisense NMEA Reader PC software, version v1.517 and later. Download the latest version from their website. Look for the setup.exe on that page. Besides the PC software you also need the interface to hook the nmea2000 network up to your PC: the Actisense NGT-1: http://www.actisense.com/products/nmea-2000/ngt1.html

Changing a data instance:

1. Open Actisense NMEA Reader
2. Select data view (tab selection is at the bottom left)
3. Right click the PGN:
4. And change the value:

Notes for BMVs, Lynx Shunt and the Lynx Ion + Shunt:

• The Battery Instance and the DC Detailed instance are the same value. Changing one of them, will also change the other one.
• Since the BMV sends out two voltages, the main voltage and the aux- or starter-voltage, it comes preconfigured with two battery instances: 0 and 1. When you want to change that to 1 and 2, change the 1 into 2 first, and then the 0 into 1, as they cannot be the same.

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 “Unique Instance” where the N2KAnalyzer software tool automatically determines if a particular device uses device or data instances.

Open N2KAnalyzer and make sure that the “Unique Instance” column is turned on (i.e. checked) using the Setup>Columns menu item.

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 cell for the device you want to change and type the new number followed by a carriage return. If the particular products accepts the instance change, you will see the new instance number reflected in the cell. You can also use a tool within N2KAnalyzer to check that all products on the network are uniquely instanced. Use the Analyze>Instancing menu to verify correct overall system instancing.

Instead of using Actisense or Maretron software, it is also possible to change the device instance from the Color Control shell. To get root access, follow these instructions: CCGX: Root Access

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 com.victronenergy.vebus.socketcan_can0_di0_xxxx.

Step 1. List the devices:

root@ccgx:~# dbus -y
com.victronenergy.bms.socketcan_can0_di0_uc10
com.victronenergy.charger.socketcan_can0_di1_uc12983

It shows a Skylla-i (the charger). di1 in the name means that it is currently on DeviceInstance 1.

Step 2. Change it, for example, to 4:

root@ccgx:~# dbus -y com.victronenergy.charger.socketcan_can0_di0_uc12983 /DeviceInstance SetValue %4
retval = 0

Step 3. Wait a few seconds, and double check:

root@ccgx:~# dbus -y
com.victronenergy.bms.socketcan_can0_di0_uc10
com.victronenergy.charger.socketcan_can0_di4_uc12983

Device instance changed successful!