Yacht Devices YDEN-02 Series User manual

User Manual
NMEA 2000 Ethernet Gateway YDEN-02
also covers models
YDEN-02R, YDEN-02N
Firmware version
1.00
2019

© 2019 Yacht Devices Ltd. YDEN02-001, December 15, 2019.
Web: http://www.yachtd.com/
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.
Package Contents
Device 1 pc.
This Manual 1 pc.
Paperclip for reset 1 pc.
NMEA 2000 Drop Cable not supplied
Ethernet Cable not supplied
Note: Device can be connected to the network backbone directly, without
an NMEA 2000 drop cable.

Contents
Introduction 4
Warranty and Technical Support 5
I. Product Specication 6
II. Device Installation and Connection 8
III. Connecting to the Gateway 10
IV. Gateway Settings 16
1. Conguration of Application Protocols 17
2. NMEA Settings and Autopilot Control 20
3. NMEA 0183 and NMEA 2000 Message Filters 25
4. Other Settings 29
V. Reset of Settings and Hardware Reset 30
VI. LED Signals 32
VII. Recording of Diagnostics Data 35
VIII. Web Gauges of Administrative Web Site 38
IX. Data Logging and Cloud Services 40
X. Firmware Updates 44
APPENDIX A. Troubleshooting 45
APPENDIX B. NMEA 2000 Messages Supported by Device 47
APPENDIX C. Conversions Between NMEA 2000 and NMEA 0183 48

Introduction
The NMEA 2000 Ethernet Gateway (hereinafter Gateway or Device) connects
navigation PCs and laptops to NMEA 2000 over Ethernet, Garmin Marine Network,
Raymarine SeaTalk HS and RayNet, Furuno NavNet, or NMEA OneNet, and allows
bridging of NMEA 2000 networks. The Gateway is equipped with a standard Ethernet
RJ45 connector, and you may need a proprietary adapter to connect it with your vessel’s
network; direct connection to PC with standard computer cable is also supported.
The Device provides NMEA 0183 and NMEA 2000 data streams using TCP and/or
UDP protocols, and has a bi-directional converter between NMEA 0183 and NMEA
2000. This allows viewing of navigational data including AIS as well as managing
NMEA equipment including autopilot from virtually all marine software, e.g. OpenCPN
(NMEA 0183 only) and Expedition 10 (both NMEA 0183 and NMEA 2000 protocols
are supported). The Gateway has three data servers (TCP/UDP), which allows tailored
settings for different applications.
The Gateway has an internal web server, allowing it to be congured and updated
from a web browser. The Web Gauges page of the built-in web site allows managing
of digital switching equipment and real time viewing of vessel data using a web browser
on PC, laptop, tablet or smartphone that can replace instrument displays. No internet
connection or app installation is required.
The Device records vessel data to the internal memory, which can be downloaded
as a GPS track, spreadsheet or in XML format from the internal web server. These
data can also be automatically uploaded to the Yacht Device’s free Cloud Service,
to share your position and other data online, get your tracks or remotely monitor your
vessel from home.
We hope that you’ll like this tiny and low-power Device. Thank you for purchasing
our product and happy voyages!
— 4 —

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, the sales receipt may be requested
when applying for a warranty claim.
2. The Device warranty is terminated in case of violation of the instructions in this
Manual, case integrity breach, or repair or modication of the Device without
the 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/or replacement of the goods
and do not include the cost of equipment installation and conguration,
or shipping of the defective Device to the manufacturer.
5. Responsibility of the manufacturer in case of any damage as a consequence
of the Device’s 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. In the event of a failure, please refer to Appendix A before contacting technical
support.
9. The manufacturer accepts applications under warranty and provides technical
support only via e-mail or from authorized dealers.
10. The contact details of the manufacturer and a list of the authorized dealers
are published on the website: http://www.yachtd.com/.
— 5 —

I. Product Specification
Figure 1. Drawing of YDEN-02R and YDEN-02N models of Gateway
Our devices are supplied with different types of NMEA 2000 connectors. Models
containing R in the sufx of model name are equipped with NMEA 2000 connectors
and are compatible with Raymarine SeaTalk NG. Models containing N in the sufx
are equipped with NMEA 2000 Micro Male connectors.
To connect the Device to a Simrad SimNet network (with yellow connectors) you can
use an adaptor cable (SimNet Female — NMEA 2000 Micro Female, Navico part
number 24006199).
— 6 —

Device parameter Value Unit
Supply voltage (from NMEA 2000 network) 7..17 V
Current consumption (average) 48 mA
Load Equivalency Number 1 LEN
Ethernet physical layer 10/100 Base-T/TX —
Ethernet interface maximum speed 100 Mb/s
Ethernet galvanic isolation from NMEA 2000 1500 V
RMS
Internet protocol version IPv4 —
TCP connections from applications (max.) 9 —
UDP clients (applications or devices) Unlimited —
Device case length 54 mm
Weight 18 gr
Operating temperature range -20..55 °С
Yacht Devices Ltd declares that this product is compliant with the essential
requirements of EMC directive 2004/108/EC.
Dispose of this product in accordance with the WEEE Directive.
Do not dispose of electronic refuse with domestic or industrial waste.
— 7 —

II. Device Installation and Connection
The Device requires no maintenance. When deciding where to install the Device,
choose a dry mounting location. Do not place the Device where it can be ooded
by water or exposed to rain or water spray. Please note that you may need to observe
LED signals and/or press the Gateway’s hidden button during the conguration
procedure.
Interfaces of the Device can be connected in any order, a hot plug (when the Device
is powered) of Ethernet cables is allowed. The Device is powered from the NMEA 2000
interface, and we recommend connecting it rst.
1. Connecting to on NMEA 2000 network
The Device is directly connected to the NMEA 2000 network backbone without a drop
cable. To connect the Device to a Simrad SimNet network (with yellow connectors) you
can use an adaptor cable (SimNet Female — NMEA 2000 Micro Female, Navico part
number 24006199).
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 connector to secure and waterproof
it.
After turning on the NMEA 2000 network power supply, the status LED
— 8 —

on the Ethernet connector (green, shown on Figure 1 in Section I) will start ashing,
indicating that the Gateway is powered and functioning (see Section VI for details).
2. Connecting to Ethernet network
The Device supports direct connection to PC or can work over an Ethernet network
(10, 100 or 1000 Mb/s), Garmin Marine Network, Raymarine SeaTalk HS and RayNet,
Furuno NavNet, or NMEA OneNet.
To connect directly with a PC, a regular RJ45 Male-Male Cat 5e/6 cable is required.
The cable is not supplied with the Device, but can be purchased in any computer store.
The cable length can be up to 100 meters, and it must have at least 4 wires connected
(usually all 8 wires are connected in the cable).
The same cable is used to connect with a standard Ethernet hub or router,
or to a Garmin Marine Network. However, the vessel’s Ethernet network (usually used
to connect the chart plotter with radar or shnder) may have proprietary connectors.
All known manufacturers supply adaptor cables with a standard RJ45 connector,
for example:
• for Raymarine RayNet, use cables with part numbers A62360, A80151, A80159;
• for Raymarine SeaTalk HS use cables with part numbers E55049, E55050,
E55051.
After connection to the Ethernet network (or to a PC), the network LED (yellow)
of the Device will start ashing. This indicates network activity (including service
packets), and ashes every few seconds even if Gateway is not used by the PC
software. A constant signal of the LED means that the cable is not connected, damaged
or all network equipment is turned off. No signal of yellow LED means that
NMEA 2000 network is turned off (the Device is powered from NMEA 2000)
or indicates hardware problem (the Gateway must be replaced).
— 9 —

III. Connecting to the Gateway
Before continuing reading, make sure that the Device is connected to the Ethernet
network or to a PC and that the network status LED is ashing chaotically
(see Section II.2).
1. Ethernet and Internet Protocol (IP) basics
Each Ethernet device has a 6-digit physical address (MAC address). However,
for the application layer (web browser, TCP/UDP protocols), a 4-digit IP address
is required. All these addresses must be unique in the subnet. The IP address can be
xed (static IP address, stored in device settings) or obtained from the DHCP server in
the network when the device is powering on.
Along with the IP address, the device must also have a subnet mask and network
gateway address assigned to the interface, for example:
• IP address 192.168.4.3:
• Subnet mask: 255.255.255.0
• Network gateway: 192.168.4.1
With the settings above, the device knows that all devices with addresses starting
with 192.168.4.xxx are accessible through this network interface, and if it is the only
network interface of the device, it will send all packets to other subnets (for example,
to 10.1.1.1) to the network gateway for forwarding (the packet will be dropped
if the network gateway has no routing rules for the 10.x.x.x subnet).
Domain names (like www.yachtd.com) are resolved by an application to establish
the connection to IP address with the help of a DNS server (in the internet)
or with mDNS or Bonjour service (in the local network, multicast protocol).
— 10 —

Bonjour and mDNS protocols are supported in Linux, Mac OS X and in Microsoft
Windows 10.
2. Connection to the Gateway
Usually, the Gateway can be accessed using a web browser by following addresses:
• http://192.168.4.1
• http://yden.local
The internal web site of the Ethernet Gateway should be opened. Use login «admin»
and password «admin» (without quotes) to enter the administrative web site. In case
of a wrong password, you can reset the Device settings to restore the default password
(see Section V).
It is possible that the connection will not be established due to network settings or you
will open some other device in a web browser instead of the Ethernet Gateway. Even
in case of a successful connection, we strongly recommend you to read this entire
Section to the end and change factory settings.
3. Ethernet modes of the Gateway
The Gateway offers several network modes:
• DHCP Client (dynamic IP address). In this mode, the Gateway automatically
receives an IP address and other network settings from the network router.
If your router has a web interface, you can enter the administrative web site
and check the addresses of connected devices to get know the assigned
IP address.
• DHCP Server. In this mode, the Gateway issues IP addresses to network
— 11 —

devices which are congured to obtain IP address automatically. The address
space is limited to four addresses (for four client devices), the rst client’s
address will be «next» to the the address of the Gateway; the other network
devices must be congured for static IP addresses. The factory setting
for Gateway’s address is 192.168.4.1.
• Static IP Address. In this mode, other network devices may also have static
IP addresses (stored in settings) or obtain addresses from the DHCP server
on the network.
• DHCP Magic. This is the factory setting of the Gateway. In this mode, it initially
tries to obtain the dynamic IP address (as in DHCP Client mode), and in case
of failure switches to DHCP Server mode. The process usually takes a few
seconds and the selected mode is indicated by status LED. The selected mode
is not saved to settings, and after reboot the sequence repeats.
The «DHCP Magic» mode should work well in case of direct connection with PC
(in rare cases, PCs are congured for a static IP address and an address conict
is possible). But if you have a network router with a DCHP server, it can assign random
address to the Gateway in «DHCP Magic» mode (if your router has a web interface,
you can log on and check the list of connected devices).
The current Ethernet mode of the Gateway is displayed every 8 seconds with status
(green) LED, see the Section VI for details.
4. Emergency mode of the Gateway
Use the supplied paperclip to press the hidden button (see Section V) during rst 10
seconds after powering on. The status LED (green) should issue the series of 3 ashes
(0.2, 0.4, 0.4 seconds with short intervals between). It means that Gateway is loaded
in emergency mode and using the address 192.168.4.1.
— 12 —

Figure 1. Internet protocol settings in Microsoft Windows
Open network connection properties on the PC («Internet Protocol Version 4
(TCP/IPv4)» on Microsoft Windows, see Figure 1) and set the IP address to 192.168.4.2
and subnet mask to 255.255.255.0, other settings can be ignored.
To avoid possible network conicts, it is recommended to connect the PC directly
to the Gateway with network cable.
— 13 —

If you still cannot open the Gateway’s web site from the PC, check the address
of the «Proxy Server» in a web browser (it must be switched off) and/or try another
web browser. See the next chapter for troubleshooting.
5. Troubleshooting of Ethernet connection
The following step-by-step guide will help you to troubleshoot the network connection:
a. Be sure that the network (yellow) LED of the Gateway is ashing chaotically
every few seconds. Otherwise, see the Section II.
b. Check the network mode of the Gateway by signals of status (green) LED,
see Section VI for details.
c. Reset gateway settings (or perform a hardware reset if you have installed
the beta version of the rmware), the Gateway will be switched to «DHCP
Magic» mode (see Section III.3).
d. Try to connect the PC directly to the Gateway (without network hub or router)
and try to access Gateway’s web server (see Section III.2).
e. Switch the Gateway to emergency mode and check settings of the PC and web
browser (see Section III.4).
f. Take a photo of your installation, internet settings of the PC, record a short video
with the LEDs ashing and apply to technical support or ask a local computer
specialist for help.
6. Recommended Ethernet settings
We recommend switching your Gateway from default «DHCP Magic» mode to «DHCP
Server» in case of direct connection with laptop or if you only have a passive network
hub that has no DHCP server. If you already have a DHCP server (network router
— 14 —

with DHCP server), switch the Gateway to «Static IP Address». In both cases,
the Gateway’s own IP address will be xed.
In case of an onboard PC (not a laptop, which can be taken away from the boat
for a while), you may prefer to congure a static IP address (use addresses differing
by at least 10 from Gateway’s address, for example to x.x.x.11 if the Gateway has
the address x.x.x.1).
If the IP address is different from the address on Device’s label, put the sticker
with the address on the Device or make a note in this manual.
— 15 —

IV. Gateway Settings
To congure the Gateway, open the administrative web site with a web browser
(see Section III.2).
Open the «Administration» link from the navigation menu at left (in the mobile
version, the menu is accessible by clicking on the icon in the top left corner), and change
the password to the administrative web site. You can record the password in this
manual.
The next important thing is to open the «Ethernet Settings» page and check
the network mode (see Section III.6). The «DNS Server Address» setting is propagated
to clients in DHCP Server mode, and used by the Gateway to access Cloud Service
(see Section IX) in all modes except DHCP Client (in this mode, the DNS address
is obtained from network DHCP server is used).
On this page you can also check or change the MAC address (physical Ethernet
address, usually it is not required) and domain name (yden.local by default).
The Gateway may not be accessible by the domain name if the PC has no Bonjour
or mDNS service running (available in Linux, Mac OS X and Microsoft Windows 10).
We strongly recommend that you check and modify default settings
after installation. Network users can take control of autopilot and other
important ship systems. If your network has external access, be sure
that the administrative web site and data servers are not accessible
from outside.
— 16 —

1. Configuration of Application Protocols
Figure 1. Settings of OpenCPN application
Most marine applications support both TCP and UDP network protocols. TCP
is a connection-oriented protocol. This means that the receiver must conrm
reception of data before it gets the next packet of data, otherwise the sender repeats
the transmission after a timeout. So, the second TCP connection doubles the network
trafc and CPU load, despite the fact that both clients receive the same data.
— 17 —

UDP is a connectionless protocol; any number of clients can listen to data broadcasted
from a specied port without any additional load on the server and without increasing
the actual network trafc. We recommend using UDP protocol where possible, because
the resources of the Device’s CPU are limited.
The Gateway supports NMEA 2000 (RAW) and NMEA 0183 data protocols.
The Gateway contains a bi-directional converter between NMEA 0183
and NMEA 2000 (see Appendix C) and has a exible system of message lters
(see Section IV.3). The NMEA 2000 (RAW) protocol is supported in Expedition 10
and CAN Log Viewer (see Section VII.2). The RAW protocol is very simple, open
and supported by our other gateways and routers (see the Appendix E of NMEA 2000
Wi-Fi Gateway YDWG-02 manual for technical details).
On the «NMEA Server» page you can set up to three server ports (see Figure 2).
If TCP network protocol is selected, up to three connections (from three different
applications on one device, or from three devices with one marine application running
on each) are allowed at the same time. So three servers allow nine connections
in total.
In the case of using UDP protocol, the number of devices or applications used
on the data port is not limited. We recommend using UDP protocol when possible.
Servers can be congured as bi-direction, read-only («From NMEA 2000»)
or write-only («To NMEA 2000»). We recommend conguring data ports
as read-only if possible, to prevent network ooding from incorrectly congured
applications.
Server #1 serves Web Gauges (see Section VIII) in addition to connected clients;
Web Gauges will not work when this server is congured to NMEA 2000 protocol
or turned off.
— 18 —

Figure 2. Gateway server settings
— 19 —

Server #3 also supports the «Debug» and «Memory» data protocols. The «Debug»
protocol is designed to diagnose hardware or software issues and described in Section
VII. The «Memory» protocol allows export of the vessel’s data from an internal
memory to GPX (tracks), CSV (spreadsheets) or XML formats; see Section IX
for details.
With the factory settings, Gateway has Server #1 enabled and pre-congured use
of TCP port 1456 and the NMEA 0183 data protocol. To connect your application
to the Gateway with factory settings:
• set the IP address 192.168.4.1 in the application settings;
• specify the TCP protocol and port 1456 in the application settings.
To use the Gateway with a Navionics Boating App, no settings are required in the app,
but some changes are required in the Gateway conguration:
• congure one of the Gateway servers to use UDP port 2000 and NMEA 0183
data protocol;
• be sure that Gateway web server is accessible from your mobile device;
• be sure that your router forwards UDP packets between Ethernet and Wi-Fi
networks.
2. NMEA Settings and Autopilot Control
On the «NMEA Settings» page you can congure control of NMEA 2000 (SeaTalk NG)
autopilots, and tune conversion between NMEA 0183 and NMEA 2000 protocols.
— 20 —