Configuring The EMU-1 with more than 1 Engine

A single EMU-1 can be used to monitor up to two engines, so long as they both share the same power supply.  For installations where this is not the case, a dedicated EMU-1 will be needed for each engine.  This article will explain how to set up your EMU-1 when using a single unit for two engines or multiple EMU-1 on the same NMEA 2000 network.

To check whether your engines sensors are compatible with the EMU-1, read this article.

Getting Started

An Actisense NMEA 2000 to PC Gateway (NGT-1/NGX-1) and our freely available Toolkit software are needed to configure your EMU-1.  Please make sure you have these available before starting the configuration process. 

This article explains why the Maretron USB100 can’t be used instead of the NGT-1.

Installation and Launching the Application

1. Install your NGT/NGX-1 and EMU-1 on the same, correctly terminated, NMEA 2000 network.  Download our free PDF guide for how to correctly install an NMEA 2000 network if you are not sure how to do this.
2. Plug your NGT/NGX-1 in to a PC/laptop with Toolkit installed.  If using the USB variant of the NGT/NGX-1, ensure the USB drivers have downloaded and installed successfully.
3. Ensure that no other software application is using the NGT/NGX-1 COM port.  The best way to do this is close all software applications.
4. Start Toolkit
5. Select the NGT/NGX-1 from the COM port selection drop down menu
6. Select the correct baud rate.  
7. Click ‘new config’ in the ribbon menu at the top of the Toolkit window.

The EMU-1 configuration tool will open in the centre of the Toolkit Window and you can now begin applying settings.

The problem with more than one engine

The EMU-1 will transmit standard NMEA 2000 messages, known as Parameter Group Numbers (PGNs).  For example; Engine Parameters, Dynamic (PGN 127489) contains the information for pressure and temperature parameters (among many others), and Engine Parameters, Rapid Update (PGN 127488) contains the information for RPM.

When there is more than one source of this kind of information, the data needs to be separated so that the receiving device (an MFD for example) knows that there is more than one and how it should be displayed.  To do this, the data instance needs to be changed.

NOTE: The data instance needs to be changed, not the device or system instance shown in Toolkits ‘Properties’ window when a device is selected in any of the device lists.

The data instance can be changed using the column highlighted in the screen shot below.  Most data receiving devices default to instance zero for port and instance 1 for starboard.  This can be usually be changed (depending on the manufacturer) but we recommend keeping to this convention when configuring your EMU-1 to avoid any unnecessary steps or complications.

[img]

Configuring a single EMU-1 with two engines

As mentioned above, if using a single EMU-1 for two engines, they must both share the same power supply.  The EMU-1 must be powered from the same supply as the gauges it is monitoring. 

When configuring your EMU-1, you will need to remember which gauge, alarm and tach inputs come from which engine.  Leave any inputs from the port engine at instance 0.  Change any inputs from the Starboard engine to instance 1.  Most NMEA 2000 displays default to using these settings when they decide how to display your engine data, which is why these are the settings we recommend.

If you have a different set up to the more conventional port and starboard, it is up to you how you assign instances.  Be sure to remember which one is which as this becomes important when setting up your NMEA 2000 display later.

Configuring Multiple EMU-1’s

1. Make a note of the serial numbers for each EMU-1 and which engine they are connected to.
2. Click ‘New config’
3. Apply your settings, keeping all instances at 0
4. Click ‘send to device’
5. Select the EMU-1 with the serial number connected to your port engine.
6. Give your configuration a memorable name
7. Click OK.
8. Repeat for the Starboard engine, using instance 1 instead of 0.  Remember to select the serial number for your starboard engine when sending to device.

As above: Most NMEA 2000 displays default to using these settings when they decide how to display your engine data, which is why these are the settings we recommend.

If you have a different set up to the more conventional port and starboard, it is up to you how you assign instances.  Be sure to remember which one is which as this becomes important when setting up your NMEA 2000 display later.

For more information on NMEA 2000 and how it works, please download our free guide to NMEA 2000 networking here: https://actisense.com/complete-guide-to-building-an-nmea-2000-network/