Yacht Devices YDEG-04 User manual

User Manual
Yacht Devices Engine Gateway YDEG-04
also covers models
YDEG-04N, YDEG-04R
Firmware version
1.31
2019

© 2019 Yacht Devices Ltd. Document YDEG04-011. May 21, 2019. Web: http://www.yachtd.com/
Yacht Devices Engine Gateway YDEG-04 is certied by the National Marine
Electronics Association.
NMEA 2000® is a registered trademark of the National Marine Electronics
Association. SeaTalk NG is a registered trademark of Raymarine UK Limited.
Garmin® is a registered trademark of Garmin Ltd. Volvo Penta® is a registered
trademark of Volvo Trademark Holding AB. BRP is a registered trademark
of Bombardier Recreational Products Inc.
Package Contents
Device 1 pc.
This Manual 1 pc.
Plug for Deutsch 6-pin connector 1 pc.
Stickers for MicroSD slot sealing 6 pc.

Contents
Introduction 4
Warranty and Technical Support 6
I. Product Specication 7
II. MicroSD Slot and Card’s Compatibility 9
III. Installation and Connection to NMEA 2000 Network 11
IV. Connection to Engine Network 12
IV.1 Connection to a Volvo Penta Engine 13
IV.1.1 Connection to EFI Engines (Gasoline, 2004-2005) 14
IV.1.2 Connection to EGC Engines (Gasoline, 2005 and Later) 15
IV.1.3 Connection to EDC III (EMS2), EDC IV (Diesel) 15
IV.1.4 Connection to EVC-A MC (EVC-MC, EVCmc) Engines (2004-2006, Diesel and Gasoline) 15
IV.1.5 Connection to EVC-A EC (EVC-EC, EVCec) Engines (2002-2005) 16
IV.1.6 Connection to Other EVC Versions and MDI (Engines from After 2005, EVC-B and Later) 17
IV.2 Connection to BRP Rotax Engines 20
IV.3 Connection to J1939 Engines 22
IV.4 Connection to SmartCraft Engines 23
V. Conguring the Device 25
VI. Display Engine and Transmission Status (Warnings) 42
VII. LED Signals 47
VIII. Firmware Updates 48
IX. Recording Data and Diagnostics of the Engine Interface 50
Appendix A. Troubleshooting 51
Appendix B. Bits for Engine and Transmission Status 53
Appendix C. NMEA 2000 and J1939 Messages Supported by the Device 55
Appendix D. Example of a Conguration File YDEG.TXT 59
Appendix E. Device Connectors 63
Appendix F. Adaptor for 8-pin EVC/Vodia Connector 65
Appendix G. Adaptor Cable for BRP Diagnostics Connector 66
Appendix H. SmartCraft Data Supported by the Device 67

— 4 —
Introduction
The Device is a gateway from VVolvo Penta (EVC all versions, MDI, EDC III, EMS2, EDC IV, EFI
with MEFI4B or later, EGC all versions), J1939 (including some Yanmar 4JH engines), SmartCraft
(Mercury, MerCuiser) and BRP CAN (Bombardier Recreational Products, for example BRP Rotax 1503
engine) networks (engine networks) to a NMEA 2000 marine digital network. With it, you can see engine
revolutions, temperature, working hours and other information on the screen of a chart plotter and other
display devices on an NMEA 2000 network.
The Gateway was initially developed specically for Volvo Penta engines with an EVC system, but
it can be used with engines of other manufacturers (adaptor cable may be required). On most vessels
with Volvo Penta or J1939 engines, the Device starts working upon installation, with no conguration
needed. Please, read the corresponding section of the manual before connecting.
We’re happy to point out that the Gateway has a wealth of diagnostics capabilities and settings. Because
of this, it can often be used on vessels where there are complications with similar equipment from various
manufacturers.
The YDEG-04 is compatible with a wide range of NMEA 2000 devices. Raymarine SeaTalk NG,
Simrad SimNet and Furuno CAN networks are branded versions of NMEA 2000 and differ only
in the type of connectors. In its devices, Garmin uses the NMEA 2000 Micro connector that
is compatible with the DeviceNet Micro connector. Our devices are supplied with different types
of NMEA 2000 connectors, making it possible to connect them to networks of different manufacturers
without any adapters. The Device model is shown on the case.
The model YDEG-04R has a connector similar to Raymarine SeaTalk NG Female. The model YDEG-04N
has a connector similar to NMEA 2000 Micro Male, DeviceNet Micro Male and Garmin NMEA 2000
Male (see Appendix E). To connect to other types of NMEA 2000 networks, a cable adapter is required
(it is not supplied with the Device and must be purchased separately).
The product with factory settings does not send data to engine networks, and it has a high-voltage
galvanic isolation between the NMEA 2000 and engine network. Installing the Device in accordance
with the manual should not have any effect on the work of the engine network. Power is supplied
by the NMEA 2000 network. The connector to the engine network supplies power only for isolated

— 5 —
transceiver of the engine network. The Device is designed to work on 12V or 24V engine networks.
The devices is equipped with a slot for a MicroSD card which can be used to congure its settings (loading
a text le with the settings), updates for the Device rmware. The card can also serve to record the data
from the engine network for conguration and diagnosis of the Device.
We thank you for purchasing our Devices and wish you happy voyages!

— 6 —
Warranty and Technical Support
1. The Device warranty is valid for two years from the date of purchase. If a Device was purchased
in a retail store, when applying under a warranty case, the sale receipt may be requested.
2. The Device warranty is terminated in case of violating the instructions of this Manual, case integrity
breach, repair or modication of the Device without manufacturer’s written permission.
3. If a warranty request is accepted, the defective Device must be sent to the manufacturer.
4. The warranty liabilities include repair and replacement of the goods and do not include
the cost of equipment installation and conguration, as well as shipping the defective Device
to the manufacturer.
5. Responsibility of the manufacturer in case of any damage as a consequence of the Device operation
or installation is limited to the Device cost.
6. The manufacturer is not responsible for any errors and inaccuracies in guides and instructions
of other companies.
7. The Device requires no maintenance. The Device’s case is non-dismountable.
8. If the event of a failure, please refer to Appendix A. before contacting the technical support.
9. The manufacturer accepts applications under the warranty and provides technical support only
via e-mail or from authorized dealers.
10. Contact details of the manufacturer and a list of the authorized dealers are published on the website:
http://www.yachtd.com/.

— 7 —
I. Product Specification
Figure 1. Drawing of YDEG-04R model of Gateway
Our devices are supplied with different types of NMEA 2000 connectors. Models with sufx R
at the end of model name are equipped with NMEA 2000 connectors compatible with
Raymarine SeaTalk NG (as at the picture above). Models with sufx N are equipped with
NMEA 2000 Micro Male connectors (see Appendix E).

— 8 —
Device parameter Value Unit
Operating voltage (from an NMEA 2000 network) 10..16 V
Protection against reverse polarity Yes —
Average current consumption 38 mA
Load equivalency number 1 LEN
Operating temperature range -20..55 °С
Isolation between NMEA 2000 and engine network 2500 V
RMS
Supply voltage from engine network 10..30 V
Average current consumption (engine network) 13 mA
Engine cable length (to Deutsch male connector) 500 mm
Device’s case length (without connector) 54 mm
Weight without MicroSD card 75 g
Yacht Devices Ltd declares that this product is compliant with the essential requirements
of EMC directive 2014/30/EU.
Dispose of this product in accordance with the WEEE Directive. Do not mix electronic disposal with
domestic or industrial refuse.

— 9 —
II. MicroSD Slot and Card’s Compatibility
The Device has a slot for a MicroSD card that allows you to congure the Device (see Section V)
and update the rmware (see Section VIII).
Since the MicroSD slot is usually not in use when the Device is working, we recommend sealing it
with the sticker that is included with the Device or with a piece of tape to prevent water from entering
the Device through the slot.
The Device supports MicroSD memory cards of all sizes and classes. The MicroSD card must be formatted
on a personal computer before use in the Device. The Device supports the following le systems:
FAT (FAT12, FAT16, MS-DOS) and FAT32. It does not support exFAT, NTFS, or any other le systems.
Be careful when inserting the MicroSD card into the Device. The card is inserted with the label side toward
the LED and with the pin side toward the engine cable.
The Device slot has a ‘push-push’ mechanism that works on a spring and ensures proper card
xation. Improper loading or unloading (withdrawing your nger to quickly or not waiting
for the click) can result in the card being propelled out of the Device up to 5 meters. To avoid
possible eye injury, loss of or damage to the card, and other hazards, insert and remove the card
with caution.

— 10 —
Figure 1. Device with MicroSD card (pin side visible at left, label side at right)

— 11 —
III. Installation and Connection to NMEA 2000 Network
The Device requires no maintenance. When deciding where to install the Device, choose a dry mounting
location. Avoid places where the Device can be ooded with water, this can damage it.
The Device is directly connected to the network backbone without a drop cable. Before connecting
the Device, turn off the bus power supply. Refer to the manufacturer’s documentation if you have
any questions regarding the use of connectors:
• SeaTalk NG Reference Manual (81300-1) for Raymarine networks
• Technical Reference for Garmin NMEA 2000 Products (190-00891-00) for Garmin networks
After connecting the Device, close the lock on the connection to ensure its water resistance and reliability.
The Device has an LED which ashes red or green. After turning the power in the NMEA 2000 network
on, the Device’s LED will give a series of 2 ashes 5 seconds apart. If this does not happen, see Appendix A.
If your boat has no NMEA 2000 network installed, you should establish a basic NMEA 2000
network rst. You cannot simply connect the Gateway to a NMEA 2000 port of your chart
plotter. Many manufacturers offer a “Starter Kit” which contains all that is necessary to
establish a basic network and connect two devices:
• for Raymarine SeaTalk NG, see Raymarine part number T70134;
• for NMEA 2000, see Garmin part number 010-11442-00.

— 12 —
IV. Connection to Engine Network
Read and become fully familiar with the contents of this section. Never connect the Device
to the connector that ‘just looks right’ until you are sure about its wiring. If you have any doubts,
ask a specialist.
Modern engine networks may seem very complicated and may have many similar connectors with
different wiring and different purposes. Some engines, which only differ by one character in the
model name, may have a vastly different electronics and different wiring. Be sure that you are using
the appropriate manual. Usually, a manual lists the colors of wires, and you may check a connector
by the color of the incoming wires.
Never disconnect or connect any connectors when the circuit breaker is ON. The entire installation process
must be performed with no power coming into the engine network and with the engines disconnected
at the circuit breaker.
The Device uses two data lines called «CAN HIGH» and «CAN LOW», and two power supply lines:
VCC (positive) and GND (negative, ground), see Appendix E. We strongly recommend checking
the engine connector wiring in the engine’s manual, and verifying your engine connector wiring with
a simple multimeter to be sure that you nd the right connector:
• turn OFF the circuit breaker and check resistance between the CAN HIGH and CAN LOW pins,
it must be 60 – 120 Ohm;
• turn on the circuit breaker (for some models ignition also should be on) and check voltage on the
VCC and GND pins (be careful not to short-circuit anything) of the connector, it must be 12 –24 V.

— 13 —
IV.1 Connection to a Volvo Penta Engine
The Device is compatible with all versions of Volvo Penta EVC, including the rst version EVC-A
(also known as EVC-MC or EVC-EC); engines with MDI (Mechanical Diesel Interface, D1 and D2 series);
with engines equipped with EDC III (EMS2) and EDC IV systems; with gasoline engines equipped with
EFI system (MEFI4B or MEFI5 controllers are supported, with or without EVC system installed); with
gasoline engines equipped with Volvo Penta EGC (with or without EVC system installed).
The Gateway is compatible with most of engines manufactured since 2004 and even with some engines
manufactured before 2000. Most modern engines (manufactured since 2006) are equipped with different
versions of EVC-B, EVC-C, EVC-D, or EVC-E. If any of these versions are tted on your boat, (regardless
if diesel or gasoline engine) please refer section IV.1.6 for installation details. Please also see IV.1.6
for engines with MDI (Mechanical Diesel Interface), which are used in the popular D1 and D2 series
of engines (for example, D2-40F).
For Volvo Penta KAD and TAMD engines (EDC I and EDC II), and for engines with J1708/J1587 interface,
please, use another our product, J1708 Engine Gateway YDES-04 (see www.yachtd.com for details).
Do not connect the Device to any connectors labeled “Panel”, “Diagnostics”, “Datalink”, “Aux”
or “Senders”. If you have any doubts, ask a specialist.
When connected to both the NMEA 2000 and the engine network, the Device should give a signal indicating
data in the engine network (see Section VII) immediately after the ignition is turned on.
The plug supplied with the Device is not a terminator of a CAN bus. It connects two CAN buses
on the 6-pin connector (see Appendix E).

— 14 —
IV.1.1 Connection to EFI Engines (Gasoline, 2004-2005)
Only engines equipped with an MEFI4B controller and later are supported (for example, 8.1 Gi-E,
8.1 OSi-A, 8.1 Gi-EF, 8.1 GXi-D, 8.1 GXi-E and many other). An adaptor cable for the Marine
Data Link Connector is required (available in accessories on the ordering page). The cable has both male
and female connectors (Y-connector), so you can use diagnostics equipment with the Gateway connected.
Figure 1. Marine Data Link Connector (with dust cap removed)
Note that ten wires must be connected to the Marine Data Link Connector from the engine side. Otherwise,
it means that your engine is equipped with an older MEFI version (MEFI3, MEFI4) which is not compatible
with the Device.
To get engine tilt/trim data, please, set MEFI4B setting to ON (see V.36). To calibrate tilt/trim settings,
see V.37-39.
Note: you can use the supplied 6-pin plug as a dust cap for the unused Device connector.

— 15 —
IV.1.2 Connection to EGC Engines (Gasoline, 2005 and Later)
Note: If an EVC system is tted, see the EVC section details.
The Device is compatible with all EGC engines (8.1Gi-H, 8.1GXi-G, 8.1OSi-D and many other).
Device is connecting to EVC/Vodia 8-pin Deutsch connector with adaptor cable (see Appendix F, available
in accessories at ordering page). The cable has male and female connectors both (Y-connector), so you can
use diagnostics equipment with Gateway connected.
Note: you can use supplied 6-pin plug as a dust cap for the free Device connector.
IV.1.3 Connection to EDC III (EMS2), EDC IV (Diesel)
Note: If an EVC system is tted, see the EVC section details.
To connect with EDC III (EMS2) engines, an EVC/Vodia 8-pin adaptor cable (see Appendix F, available
in accessories on the ordering page) is required. The adaptor cable must be connected to the engine’s 8-pin
Deutsch connector, or in line (cable has a built-in Y-connector) between the ECU (Engine Control Unit)
and the CIU (Control Interface Unit).
The Gateway is compatible with EDC IV engines, but the wiring may differ depending
on the instruments installed. A 6-pin Deutsch Vodia connector usually has four wires (power and J1708) only
and cannot be used for a Gateway connection. Please refer your installation diagram and follow
the instructions from section IV.3.
For EDC I and EDC II engines, please, use another our product, J1708 Engine Gateway YDES-04 (see
www.yachtd.com for details).
IV.1.4 Connection to EVC-A MC (EVC-MC, EVCmc) Engines (2004-2006,
Diesel and Gasoline)
Unlike other EVC engines, EVC-A MC (used in the D3-160A-A engine and some others engines) use
the Volcano protocol which is physically compatible with the J1939 protocol, but differs at the software

— 16 —
level. Engine revolutions, coolant temperature, boost pressure, battery voltage and engine hours
are supported. The Engine Gateway must be connected in series with the engine
and Helm Interface Unit (HIU).
Connections can be made with a «EVC-A MC 12-pin C5:ENGINE» adaptor cable (available in accessories
on the ordering page). This cable contains a Y-connector, and must be connected between the C5:ENGINE
(grey) connector of HIU (Helm Interface Unit) and the engine cable.
Connection can also be made using an EVC/Vodia 8-pin adaptor cable (see Appendix F, available
in accessories on the ordering page). The Y-connector of this cable must be connected between
the ECU (Engine Control Unit) and the cable to the HIU. Note that this connection point may
be located far from the NMEA 2000 backbone, and an additional NMEA 2000 drop cable
may be required.
The multisensor interface is a different CAN network on this ECU, and to get multisensor data
(water temperature, depth and speed), an additional Gateway with an «EVC-A Multisensor» adaptor
cable (available in accessories on the ordering page) is required. The Y-connector of this adaptor cable
must be connected between the C4:MULTISENSOR (yellow) connector of the HIU and the multisensor
cable.
Note: you can use the supplied 6-pin plug as a dust cap for the unused Device connector.
To activate support of Volcano protocol (required on Gateways connected to both a C5:ENGINE and
a C4:MULTISENSOR), the setting VOLCANO=ON must be set (see V.21).
Water temperature, depth and speed can be calibrated with settings V.22-V.24.
IV.1.5 Connection to EVC-A EC (EVC-EC, EVCec) Engines (2002-2005)
This type of EVC system used on D4 and D6 engines was manufactured from 2002-2005 (for example,
D4-210A-A). An adaptor cable, «EVC-A EC 12-pin X5:MULTILINK» is required (available in accessories
on the ordering page). The Y-connector of this cable must be connected between the X5:MULTILINK port
of the HCU (Helm Control Unit) and the sync cable.

— 17 —
One Gateway is enough for a twin-engine installation.
Note: you can use the supplied 6-pin plug as a dust cap for the unused Device connector.
IV.1.6 Connection to Other EVC Versions and MDI (Engines from
After 2005, EVC-B and Later)
This connection can be made at the following points (please, read also the details below):
• If the system has an EVC tachometer (with a needle gauge and a small LCD display) connected
by a 6-pin Deutsch connector (see Fig. 2 on the next page), the best option is to connect the Gateway
in-line with a tachometer (no extra cables are required, the Gateway is equipped with a 6-pin
Y-connector);
• If the system has an HCU (Helm Control Unit) with a 6-pin «Multilink» connector (usually
the connector and/or the cable label are yellow), the Gateway can be connected to this port (in line
with the existing cable);
• If the system has a Multilink Hub (casing usually made completely of yellow plastic,
6-pin connectors), the Gateway can be connected to any port of the hub.
If the engines are connected to a single network (joined with a sync cable), one Device is adequate
for transferring data from all engines to the NMEA 2000 network. The Device supports up to 8 engines
on a network. If the engines are not united on a single network, a separate Device will be needed
for each one.
The basic test is to switch the cables of the EVC tachometers. If the port tachometer shows data of
the starboard engine, it means that you need a dedicated Gateway for each engine (it is less expensive than
installing a sync cable). If the port tachometer still shows port engine data, then one Gateway is enough.
The Device has a built-in Y-connector, and to connect the Device before the EVC tachometer, you only
need to disconnect the tachometer cable, connect it to the Device, and connect the cable from the Device
to the tachometer. If the engines are united on a network and there are multiple tachometers,
you can choose any of them, whichever is most convenient.
Note that if you are installing the Gateway in the place of a broken EVC tachometer, the plug supplied with

— 18 —
the Device must be installed in the unused connector of Device. This plug connects the two CAN interfaces
(CAN1 and CAN2, see Appendix E). The engine controller sends data on the CAN1 interface and monitors
the echo on CAN2. CAN1 and CAN2 are joined in EVC tachometer. If the tachometer is not installed and
the plug is not set, the engine controller will see no echo at CAN2 and will stop data transmission.
Figure 2. Volvo Penta engine with MDI and EVC tachometer
In case of connection to a free «Multilink» port of the HCU (not in series with any of the existing Multilink
connections), setting of supplied plug is required. In case of connection to the free port of a Multilink
hub, the plug is required only if no other EVC equipment is connected to the hub (if you are unsure,
you can initially connect Device without the plug, and install the plug in case of failure).
Note that the plug (Deutsch connector of male type) cannot be installed if you are connecting the Gateway

— 19 —
to the HCU or a hub without an EVC cable, because the required Device connector (female) will be inserted
in the HCU/hub. In this case you can contact us before ordering, and we’ll supply you with a female type
plug instead of the male type free of charge. You can also join the pins of the female Device connector
yourself (CAN1 HIGH with CAN2 HIGH, CAN1 LOW with CAN2 LOW, see Appendix E). This situation
is very rare in practice.

— 20 —
IV.2 Connection to BRP Rotax Engines
BRP CAN protocol differs from J1939 and Volvo Penta EVC protocols and requires conguration
of the Device. BRP CAN diagnostics connector wiring is also differ from the Device’s engine
connector wiring; you should change the pins in the connector or use an adaptor cable.
The Device supports up to two BRP engines on a network. The following data are supported:
• engine speed;
• engine hours;
• engine temperature;
• boost pressure;
• keyswitch battery voltage;
• fuel rate;
• fuel tank level;
• engine warnings transmitted in J1939 messages with PGN 65226; native engine warnings
(see Table 3 in VI.3)
To activate BRP CAN protocol support for most engines, you should add the following lines
to the conguration le (see V.19 and V.20 for details):
BRP_ROTAX=ON
ENGINE_CAN_SPEED=500
Please note that the Device must be rebooted before the new CAN bus speed comes into effect. Most
BRP engines have 500 kbps CAN speed, but some models use 250 kbps. If you do not get any data, try
to set 250 in the second parameter. If get RPM and engine hours, but no fuel rate and oil pressure, set
the HANDSHAKE value to BRP_ROTAX setting.
Usually, that is all that you need to do to change in the default settings.
Engines in a BRP CAN network have no J1939 addresses, but addresses are used in the Device’s