Yacht Devices YDNB-07N User manual

User Manual
Yacht Devices NMEA 2000 Bridge YDNB-07
also covers models
YDNB-07N, YDNB-07R
Firmware version
1.07
2018

© 2018 Yacht Devices Ltd. Document YDNB07-003. April 23, 2018. 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.

Contents
Introduction 4
Warranty and Technical Support 6
I. Product Specication 7
II. Installation and Connection to NMEA 2000 Networks 9
III. LED Signals 11
IV. MicroSD Slot and Card’s Compatibility 12
V. Loading of Programs into the Device 14
VI. Structure and Basic Syntax of the Program 15
VII. Description of the Settings 17
VIII. Software Filters 21
IX. Optimization and Performance 30
X. Debugging of the Program 34
XI. Firmware Updates 36
Index 38
Appendix A. Troubleshooting 39
Appendix B. List of NMEA 2000 Messages of the Device 41
Appendix C. Device Connectors 42
Package Contents
Device 1 pc.
This Manual 1 pc.
Stickers for MicroSD slot sealing 6 pc.

— 4 —
Introduction
Yacht Devices NMEA Bridge unies two physical NMEA 2000 networks into a single logical network,
smoothly exchanging messages between them. The Device also supports ltering and processing
of transmitted messages.
This can accomplish the following tasks:
1. Bypass the physical limits of NMEA 2000 networks concerning length of networks
(100 meters for regular cable and 250 meters for heavy or mid-type cable) and concerning
the maximum number (50) of physical devices attached to the network. On a network with
address capacity of 252, multiple bridges can be engaged to expand to around 250 physical devices.
2. Isolate devices from each other. Using the simple lter, you can block transmission of all
or of selected messages from a given device in a separate subnet.
3. Ensure proper functioning of equipment. Correct the transducer offset of the depth sounder,
or “delete” invalid data in messages from equipment that is only partially operational using
a 2- or 3-line script.
4. To ensure compatibility of equipment from different generations. You can create
and send any type of NMEA 2000 message using data from other messages in the network.
5. Diagnose malfunctions in the NMEA 2000 network. The Device can record network
messages and debug data from custom programs on a MicroSD card in a text le. You can view
the data in a standard text editor on a smartphone or tablet with a MicroSD slot, there is no need
for a computer. You can even create and edit programs for the Device right on your phone!
6. Safely connect devices that do not meet NMEA 2000 standards. One of the CAN-interfaces
on the device has high-voltage galvanic isolation and can operate at a higher supply voltage.
7. Create gateways for networks based on CAN protocol operating at a speed from 50 kbps
to 1000 kbps. The programming language of the device is not designed for full-edged applications,
but one can create, for example, a gateway from a J1939 network to NMEA 2000.

— 5 —
Programming the device requires knowledge of NMEA 2000. Copy of NMEA 2000 standard can be
purchased from the National Marine Electronics Association: http://www.nmea.org.
Yacht Devices would like to note that a NMEA 2000 network might contain important
devices such as a deep sounder, magnetic compass and autopilot. Failure or incorrect
operation of these devices can result in serious accidents and fatalities. When
programming the Device, you must be fully aware of all the implications. Before
making a sea-going trial, conduct mandatory training for the vessel’s crew.

— 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 YDNB-07R model of Bridge
Our devices are supplied with different types of NMEA 2000 connectors. Models with the 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 the sufx N are equipped with NMEA 2000 Micro Male connectors
(see Appendix C).

— 8 —
Device parameter Value Unit
Operating voltage, from CAN1 interface 9..16 V
Average current consumption, CAN1 38 mA
Load equivalency number, CAN1 1 LEN
Supply voltage of CAN2 interface 9..30 V
Average current consumption at CAN2 13 mA
Load equivalency number, CAN2 1 LEN
Isolation between CAN1 and CAN2 2500 V
RMS
Protection against reverse polarity Yes —
Operating temperature range -20..55 °С
Cable length 500 mm
Device’s case length (without connector) 54/40 mm
Weight without MicroSD card 52 g
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 mix electronic disposal
with domestic or industrial refuse.

— 9 —
II. Installation and Connection to NMEA 2000 Networks
Never connect both connectors of the Device to the same NMEA 2000 network.
This can ood the network with innite forwarding of messages and cause a temporary
inoperability of the 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 water resistance and reliability.
The microcontroller of the Device is powered by the CAN1 interface. The Device will
not work until the NMEA 2000 network on the CAN1 interface is not powered up. If you want
to start up the Device for familiarization purposes, the CAN2 interface can be left unconnected
from the NMEA 2000 network.
The Device has a 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.

— 10 —
Figure 2. Scheme of a typical installation
Please remember that a NMEA 2000 network requires a separate power supply and a terminator
on each side. If the Device is inset, dividing an existing NMEA 2000 network into two parts, you have to add
a terminator to each of the segments and power the second segment with a 12V power supply.
More information on this topic is available in the above listed documents from Raymarine and Garmin.

— 11 —
III. LED Signals
1. Signal with period of 5 seconds, two ashes of the LED. The rst ash indicates the condition
of the CAN1 interface network. The signal is green if within the last period (5 seconds) has been data
received from the network or successfully sent, red if not. The second ash indicates
the condition of the CAN2 interface network.
The Device can be congured to receive only a limited set of NMEA 2000 messages
(see SectionVII.3), the remaining messages are ltered at the hardware level. In this regard,
some NMEA 2000 networks can indicate a red light much of the time, even when
the network is functioning normally. In this case, to check the connection, turn one device that
is on the network (e.g. the chart plotter) off and on again. The status of the network will be displayed
with green ashes for some time as the device is powering up and connecting.
2. Three ashes (colors may vary), one time after inserting the MicroSD card into
the Device. See Section V.
3. Long ash (3-second), red or green. Diagnostics mode started / nished, see Section X.
4. Five green ashes when NMEA 2000 network is turned on. The Device has the MicroSD
inserted with a rmware update, the rmware is updated (see Section XI).

— 12 —
IV. 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 XI).
Figure 1. Device with MicroSD card (pin side visible at left, label side at right)
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 too 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.

— 13 —
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 capacities 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 into the Device. The card is inserted with the label side toward
the LED and with the pin side toward the cable.

— 14 —
V. Loading of Programs into the Device
Place YDNB.CFG le with the program to the root directory of a MicroSD card with a FAT or FAT32
le system. Insert the MicroSD card into the Device. After a few seconds, you should see the LED ash
three times:
1. Three red ashes mean that the memory card cannot be read.
2. A green followed by two red ashes means that the YDNB.CFG le cannot be found
on the memory card and the current Device conguration was saved to the YDNBSAVE.CFG le.
3. A red followed by a green and another red ash means, that the YDNB.CFG le contains
errors and was not accepted by the Device. The text le YDNBERR.TXT was created in the root
directory of the memory card, comprising an error log.
4. Three green ashes mean that the le has successfully been loaded into the Device. The text
le YDNBSAVE.CFG was created in the root directory of the memory card, comprising the current
program and the used settings.
The Device performs compilation of the program text into bytecode. Before the Device saves a program
in the YDNBSAVE.CFG le, it decompiles the bytecode to text. This is why the contents of the YDNB.CFG
and YDNBSAVE.CFG les can differ from each other.
The YDNB.CFG le must contain at least one interpretable line of code (a setting, lter etc.) without errors,
to be loaded into the Device.
To modify the current program, insert a memory card into the Device that does not contain a YDNB.CFG
le. The LED of the Device will ash green, red, red. This means that a YDNBSAVE.CFG le, comprising
the current program, was saved onto the memory card. This program can be modied, saved as YDNB.CFG,
and loaded back into the Device.

— 15 —
VI. Structure and Basic Syntax of the Program
The program denes algorithms and rules for the processing and forwarding of NMEA 2000 messages that
the Device receives via the CAN1 and CAN2 interfaces.
The program consists of settings, subprograms of lters, and comments. The settings and lters
are described in detail in the later sections of this Manual.
Comments in the program are added after the # symbol. Comments can be situated at the beginning
of a line as well as after interpretable program text.
Settings can be set anywhere in the program, except for inside subprograms of lters. Nevertheless,
we recommend declaring settings before lters.
Example 1.
# Example N1
FW_CAN1_TO_CAN2=ON # Allow forwarding of all mismatched messages
FW_CAN2_TO_CAN1=OFF # Setting for other direction
match(CAN2,0x01FD0600,0x01FFFF00) # 1st lter
{
# Empty subprogram, matched messages will be dropped
}
match(CAN2,0x00000010,0x000000FF) # 2st lter
{
send(CAN1) # Forward of matched message to CAN1 interface
}
match(CAN1,0x00000020,0x000000FF) # 3nd lter (for CAN1)
{
# No send(), matched messages will be dropped
}
# End of program

— 16 —
A lter consists of a header, which begins with the keyword match(), and contains the data for the matching
of a message, as well as a processing subprogram entered in the specially created programming language.
The order of the lters is important because the Device matches received messages with the lters,
in the order they are specied in the program. In case of a match, the message is sent to the processing
subprogram of the lter, which will then be responsible for forwarding or blocking the message. The message
will not be compared with the next lter.
In case there is no match with any of the lters, the Device follows the settings. If message forwarding
is enabled for the interface (by default, yes), the given message will be sent to the other CAN interface.
If disabled, the message will be discarded.
The program in example 1 comprises two settings and three lters. The Device will forward every message
it gets from the CAN1 interface to the CAN2 interface, except for messages sent by the device with address
0x20. But only messages with the address 0x10 will be forwarded from the CAN2 to the CAN1 interface,
with the exception of messages with PGN 0x1FD06.
Looking ahead, we explain the operation of this program. When receiving a message from
the CAN2 interface, it coincides with the rst lter of the program when its PGN is equal to 0x1FD06.
The processing subprogram of the rst lter is empty, so the message will not be forwarded and
the processing of the message is completed.
In case there is no match with the rst lter, comparison with the second lter will be executed. It is successful
if a device with the address 0x10 at the CAN2 network sent the message. The processing subprogram
of this lter consists of only a call of the send() function, which initiates the forwarding of the message.
If the messages received from the CAN2 interface do not coincide with the rst two lters (the third
lter only affects messages received from the CAN1 interface), the messages will be blocked according
to the FW_CAN2_TO_CAN1 setting.

— 17 —
VII. Description of the Settings
Note that a vertical bar (pipe) is used in the descriptions below to separate alternative setting values.
ON|OFF means, that the setting can have to different values — ON or OFF.
1. Forwarding of messages
FW_CAN1_TO_CAN2=ON|OFF
FW_CAN2_TO_CAN1=ON|OFF
Enables or disables the automatic forwarding of messages that do not coincide with lters between the CAN1
and CAN2 interfaces, see example 1 at page 15.
2. Assembly of NMEA 2000 fast messages
PGNS_TO_ASSEMBLY=x
x — from one to ve PGN, entered as decimal or hexadecimal values, separated by commas.
NMEA 2000 messages with a length from 9 to 223 byte, are transmitted in a series of standard CAN messages
with a length from 1 to 8 byte (see „3.1 Fast-packet messages“ in the NMEA 2000 standard documentation).
The Device can pre-assemble NMEA 2000 fast messages from series of CAN messages and transmit them
to the program in an assembled state. In this parameter, you can select up to ve messages types
for assembly, using PGN. Messages not completely assembled will be discarded.
When such a message is send, it is dissembled into a series of CAN messages and put into a sending queue.
It is recommended not to use the assembly of NMEA 2000 messages when possible, but to process them
at the level of CAN messages, as this will signicantly reduce the sending delay in the Device (see Section IX).

— 18 —
3. Hardware lters
CAN1_HARDWARE_FILTER_y=f,m
CAN2_HARDWARE_FILTER_y=f,m
y — number of the hardware lter, decimal number from 1 to 7;
f — lter value, decimal or hexadecimal number (29 signicant bits);
m — lter mask, decimal or hexadecimal number (29 signicant bits).
The Device can lter messages from the CAN1 and CAN2 interface at hardware level, which in some cases
can reduce the load on the microprocessor by a factor of up to a 100. The message selection is carried
out through the standard 29-bit identier of CAN messages, which contain the message priority, PGN,
the sender’s address and (in some cases) the recipient’s address.
Messages are only passed to the program if they match one of the hardware lters. It is possible
to set up to 7 custom hardware lters for each interface, with numbers from 1 to 7.
Additionally, the Device has a set system hardware lter for each interface with the number 0,
which cannot be modied by the user:
CAN1_HARDWARE_FILTER_0=0x00E80000, 0x01F90000
CAN2_HARDWARE_FILTER_0=0x00E80000, 0x01F90000
The lter (rst parameter) sets bits for the comparison with the message identier and
the mask (second parameter) indicates the bits whose comparison result is signicant.
Thus, the system hardware lter passes only messages with the following PGNs:
0xE800 (ISO Acknowledgement), 0xEA00 (ISO Request), 0xEC00 (ISO Transport protocol),
0xEE00 (ISO Address Claim).
If no custom hardware lter for the interface is dened in the program, a lter that accept all messages
will be automatically added for the given interface:
CAN1_HARDWARE_FILTER_1=0,0
So if no custom hardware lter is set in the program, all messages will be passed to the program.

— 19 —
4. NMEA 2000 instance
DEVICE_INSTANCE=x
SYSTEM_INSTANCE=y
x — number from 0 to 255, y - number from 0 to 15.
These settings allow you to program the device and system instances of the Device, used in
the Device information (NAME) and transmitted in the ISO Address Claim message.
The default value of both settings is 0. These settings will not be saved to the YDNBSAVE.CFG le if they
have the default values.
5. Message slots initialization
SLOTx=aabbccdd…
or
SLOTx=aa bb cc dd….
x — number of slot, 1 – 3;
aabbccdd — sequence of bytes (1 – 229), hexadecimal values.
These settings are used to initialize slots when the Device is powered up (or when a new program is
loaded from the MicroSD card). Data from slots may be loaded to the current message buffer using the
load() function (see VIII.8). The buffer’s format is described in VIII.2. You can overwrite slot content
in the program lters.
Example of non-addressed ISO Request of ISO Address Claim:
SLOT1= 00FFEA18 FF 03 00EE00

— 20 —
6. Speed of the CAN2 interface
CAN2_SPEED=x
x - the speed in kbps, factory setting is 250, allowed values are 50, 125, 250, 500 and 1000.
The speed of the CAN2 interface can be set within a range from 50 to 1000 kbps (NMEA 2000
has 250 kbps speed). This allows interfacing with various CAN networks. The speed of the CAN1 interface
cannot be changed, it has xed speed of 250 kbps.