Nucleo GX Manual Address Claim procedure (ACL): a mechanism, specified by J1939 and used in NMEA 2000 by devices on the network to negotiate and assign each device on the network a unique network addresses. It is a number from 0 to 252. There are three special network addresses defined: 1. 0xFD (253) - Reserved 2. 0xFE (254) - Unable to claim address - for example when all others are in use 3. 0xFF (255) - The broadcast address 15.8.2. NMEA 2000 Virtual-devices When the NMEA2000-out feature is enabled, the GX device acts as a bridge: it will make each Battery monitor, Inverter/charger or other device that is connected available individually on the CAN-bus.
Individually, as in each with its own network address, its own Device instance, function codes, and so forth. For example, a GX device with two BMVs connected on a VE.Direct port and an inverter/charger connected using VE.Bus, will make the following data available on the CAN-bus: Address Class Function Description 0xE1 130 (Display) 120 (Display) The GX device itself 0x03 35 (Electrical generation) 170 (Battery) The 1st BMV 0xE4 35 (Electrical generation) 170 (Battery) The 2nd BMV 0xD3 35 (Electrical generation) 153 The inverter/charger (AC-output) 0xD6 35 (Electrical generation) 154 The inverter/charger (AC-input) 15.8.3.
NMEA 2000 Classes and Functions As per NMEA 2000 specification, these define the types of senders and devices connected to the CAN-bus. Classes are the main categories and functions specify it to a further detail. 15.8.4. NMEA 2000 Instances Instances are used in an NMEA 2000 network to identify multiple similar products connected to 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) and also a Quattro inverter/charger. All three of those devices will send their battery voltage measurements out on the N2K network.
For the displays to show these values at the right place, they need to know which voltage belongs to what battery. That is what instances are for. 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: 1. Data instance 2. Device instance 3. System instance For all battery monitors and other devices that the GX device makes available on the CAN-bus, each of the above types of instances is available and can be individually configured.
Per Virtual-device, there is one Device instance and one System instance. And depending on the type of Virtual-device, there are one or multiple Data instances. For example, for a BMV-712 there are two Data instances, one DC Instance for the main battery and another one for the Starter battery voltage. How to configure the instances depends on the equipment and software that is used to read them from the CAN-bus. Examples of equipment and software meant here are MFDs such as from Garmin, Raymarine, Furuno or Navico; as well as more software-oriented solutions from for example Actisense and Maretron.
Most of those solutions identify parameters and products by requiring unique Device instances, or using the PGN 60928 NAME Unique Identity Numbers and do not rely on the Data instances to be globally unique. However, there is one exception: Raymarine MFDs may need to change the Data instance to display data properly, depending on the Lighthouse firmware version. For more information, please see the Raymarine-specific NMEA 2000 chapter. Page 145 Marine MFD integration by NMEA 2000