Release Note

Schutzvermerk DIN 34 beachten / copyright reserved

Serial Interface to VDR Interface

Automation Products: MOS/MCS2200 & Alpha4

Document-No. 970.105.000-07
Date 28-09-2006

Automation Group/Navigation & Communication

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

Revision history

Ver-
sion Date Author Changed Short description of changes
1 2002-04-22 MSP First issue
2 2002-05-07 MSP More information.
Checksum included.
3 2002-11-18 MSP XDR, switch and event did not work in version
1. Fixed. New version and checksum
Minor textual improvements to this document.
4 2003-02-03 MSP Error in update interval routine. The initial value
was wrong and the calculation of the update time
after transmission was faulty.
New version and checksum.
5 2003-10-20 MSP The content is changed in order to be more clear
and understandable. The VDR with timestamp
on ALR sentences in described as well.
Limitations in the number of sentences are
included.
The number of data in one XDR sentence is
reduced from 5 to 4, but specifying 5 will still
work.
6 2006-01-04 MSP Firmware VDR without timestamp for Alpha4
included. Version 1 for Alpha4.
7 2006-09-28 MSP All New logo and header

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 2 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company
CLASSIFICATION AND APPROVAL

Classification: Confidential

DEFINITIONS

Internal after Review:

The document may be freely distributed internally within SAM, LM and established partners after
successful review/release.

Confidential for the Duration of the Development:

As for ‘Confidential’, but only for the duration of the development. Following the conclusion of
the development and sign-off by the authorised person, the document is automatically downgraded
to ‘Internal after Review’.

Confidential:

The document is for internal use within SAM and LM R&D, and shall not be used or disclosed to
other parties without the specific approval of the R&D manager.

AUTHORS:

Name Date Signature

Mads Staun Pallesen

APPROVAL:

Approved for release by:

Name Date Signature

Kjeld Dittmann

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 3 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

CONTENT.

1 Introduction.................................................................................................................................5
1.1 Purpose................................................................................................................................5
1.2 References...........................................................................................................................5
1.3 Terms. .................................................................................................................................5
1.4 Requirements ......................................................................................................................5
1.5 Design Considerations. .......................................................................................................6
1.5.1 The intension of the VDR ...........................................................................................6
1.5.2 Sentence Specification ................................................................................................6
1.5.3 Sentence Customization using Serial Objects.............................................................8
1.5.4 Relation between CT2100 Monitoring Channels ID’s and the sentence ID...............8
2 Physical Level.............................................................................................................................9
2.1 Supported Electrical Standards. ..........................................................................................9
2.1.1 EIA RS-232C. .............................................................................................................9
2.1.2 RS-422. .......................................................................................................................9
2.1.3 EIA RS-485...............................................................................................................10
2.2 Supported Line Setting. ....................................................................................................10
2.3 Supported Handshake Modes. ..........................................................................................10
2.4 Protocol Number...............................................................................................................11
2.5 Part number, ID Text and Checksum................................................................................11
2.5.1 MOS/MCS 2200 - VDR............................................................................................11
2.5.2 Alpha4 - VDR ...........................................................................................................11
2.5.3 MOS/MCS 2200 - VDR with Timestamp ................................................................11
2.6 Default Line Settings ........................................................................................................11
3 Limitations. ...............................................................................................................................12
3.1 Physical Location..............................................................................................................12
3.2 UMS2100 Release Dependency. ......................................................................................12
3.2.1 VDR without timestamp ...........................................................................................12
3.2.2 VDR with timestamp ................................................................................................12
3.3 Performance. .....................................................................................................................12
3.4 Supported protocol functions............................................................................................12
3.5 Total Number of Sentences...............................................................................................13
3.6 Supported Electrical Standard...........................................................................................13
4 Customizing the VDR interface................................................................................................14
4.1 General..............................................................................................................................14
4.2 ALR...................................................................................................................................15
4.2.1 How to include timestamp ........................................................................................15
4.3 RPM ..................................................................................................................................16
4.4 XDR ..................................................................................................................................17
4.5 Serial Objects. ...................................................................................................................18
4.6 Creating a serial object for communication line supervision time. ..................................18
4.7 Creating the Serial Objects. ..............................................................................................18
4.7.1 Common object parameters ......................................................................................18
4.7.2 ALR Object Parameters ............................................................................................19
4.7.3 XDR Object Parameters............................................................................................20
4.7.4 RPM Object Parameters............................................................................................21
SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg
Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 4 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

1 Introduction

1.1 Purpose.

The purpose of this document is to describe the limitations of the implemented protocol, and
to provide the necessary information for the customizing (CT2100).

1.2 References.

[IEC 61996] INTERNATIONAL STANDARD, IEC 61996, First edition 2000-07,

Maritime navigation and radiocommunications equipment and sys-
tems- Shipborne voyage data recorder (VDR) – Performance re-
quirements – Methods of testing and required test results.

[IEC 61162-1] IEC 61162-1, Second Edition, 2000-07, Maritime navigation and ra-
diocommunications equipment and systems - Digital interfaces. Part
1: Single talker and multiple listeners, Reference number IEC 61162-
1:2000(E).

[NMEA 0183] NMEA 0183, Standard For Interfacing Marine Electronic Devices,
version 2.20, January 1, 1997. Copyright © NMEA 1997.

1.3 Terms.

LM Lyngsø Marine
SAM STN Atlas Marine Electronics
VDR Voyage Data Recorder
CT2100 LM Customizing Tool for the UCS/UMS 2100 systems

1.4 Requirements

The requirements of the VDR interface as given by [IEC 61996] and [IEC 61162-1].
The requirements of the LM to VDR interface are specified in document 970.109.071.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 5 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

1.5 Design Considerations.

1.5.1 The intension of the VDR

According to [IEC 61996] Annex B, only a limited number of alarms are mandatory for the
VDR.
The VDR is NOT intended as an event logger for each and every alarm and/or value avail-
able in the alarm and control system.
It is also not the intension that the VDR protocol of the alarm and control system must act as
VDR interface for other systems such as e.g. fire systems or navigation systems. These sys-
tems must provide their own input to the VDR.
The alarm and control system can of cause have a few alarm telling that an alarm is present
in another system.

From a response time point of view it is also crucial that the minimum wait time of one sec-
ond between two sentences does not destroy the response time of an alarm/event, because a
large number of alarm/event are in queue for being transmitted.

Therefore: LIMIT THE NUMBER OF SENTENCES TO THE MANDATORY ONES!

If this for some reason cannot be done, then split the VDR interface into one with the manda-
tory alarms and one or more with the nice to have ones.

1.5.2 Sentence Specification

The following sentences can be specified and used in this interface

$xxALR,hhmmss.ss,xxx,A,A,c--c*hh<CR><LF> [IEC 61162-1]

$xxRPM,a,x,x.x,x.x,A*hh<CR><LF> [IEC 61162-1]

$xxXDR,a,x.x,a,c--c,...a,x.x,a,c--c*hh<CR><LF> [IEC 61162-1]

In order to make the serial interface protocol aware of which sentences to use and which data
to insert in the sentences the following must be specified:

Talker ID (ER, RC, SG, FD, FR, HD, HS, WD)

Sentence (ALR, RPM, XDR)
Sentence Dependent Data Structure

The talker ID is related to the source of data included in the sentence. For most data from a
LM system ER will be the selected talker ID.
The talker ID RC can be used for data from the propulsion remote control system, but the
talker ID is not yet a part of the [IEC 61162-1].

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 6 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company
If interfaces to other equipment are present the talker ID for these systems can be used to in-
dicate the source of the data.

1.5.2.1 ALR – Set Alarm State

This sentence is used to transmit an alarm condition and its acknowledge state.
The timestamp will be Null in the standard VDR interface. However in the VDR with time-
stamp the ALR sentence will include either the UTC or the LT time.

The following data must be available from the Gamma micro:

Alarm ID (0-999)
Alarm state (A=alarm=1, V=normal=0)
Acknowledge state (A=Acknowledged=0,V=Unacknowledged=1)

1.5.2.2 RPM – Revolutions

This sentence is used to transmit shaft or engine rpm and propeller pitch response values.
The values will be transmitted without comma.
The following data must be available from the Gamma micro:

Number of data (n)

1st Source ID (S=shaft, E=engine)
1st Engine/Shaft number (0 – 255)
1st Pitch included (0=No, 1=Yes)
.
.
.
nth Source ID
nth Engine/Shaft number
nth Pitch included

1.5.2.3 XDR – Transducer Measurements

This sentence is used to transmit transducer values. In addition to the mandatory contents of
the sentence the interface protocol must know the position of the comma in the values trans-
mitted.
The following data must be available from the Gamma micro:

Number of data (n)

1st Transducer Type (Null=0,C=1,A=2,D=3,…S=14)
1st Unit (Null=0, C=1,D=2,M=3,…U=12)
1st Transducer ID (001-255) (Null=0)
1st Value comma position
.
.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 7 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company
.
nth Transducer Type (Null=0,C=1,A=2,D=3,…S=14)
nth Unit (Null=0, C=1,D=2,M=3,…U=12)
nth Transducer ID (???) (Null=0)
nth Value comma position

1.5.3 Sentence Customization using Serial Objects

The number of serial objects is limited to 40 with 20 parameters in each object.

In order to make use of as many parameters as possible in each serial object it will be neces-
sary to pack information in the parameters fields when specifying some of the sentences.

1.5.4 Relation between CT2100 Monitoring Channels ID’s and the sentence ID

Since it is not possible to transfer the Monitoring Channel ID’s to the VDR protocol, a sheet
showing the relation between the Monitoring Channel ID and the sentence ID must be cre-
ated.
When a value/alarm is selected for the VDR, the related alarm/value should have the same
sentence ID.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 8 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

2 Physical Level.

2.1 Supported Electrical Standards.

Two basic forms of operation are available for transmission of digital data over
interconnecting lines. These are the single ended and differential techniques.

The single ended form uses a single conductor to carry the signal with the voltage referenced
to a single return conductor. The single ended form is the simplest way to send data, as it
requires only one signal line per circuit. This simplicity, however, is often counterbalanced
by the inability of this form to allow discrimination between a valid signal produced by the
driver, and the sum of the driver signal plus externally induced noise signals.
The differential circuit, a twisted pair transmission line and a differential line receiver offer a
solution to some of the problems inherent in the single ended form of operation. The driver
signal appears as a differential voltage to the line receiver, while the noise signal appears as a
common mode signal. The two signals, therefore, can be discriminated by a line receiver
with a sufficient common mode voltage operating range.
The Electronic Industries Association (EIA) has defined three specific standards for the
interface between computerised equipment.

2.1.1 EIA RS-232C.

The EIA RS-232-C electrical interface is a single ended, bipolar voltage, an unterminated
circuit. The EIA RS-232-C specification is for serial binary data interchange over short
distances. It is a protocol standard as well as an electrical standard, specifying hand shaking
signals and functions between terminal and communications equipment. As already noted,
single ended circuits are susceptible to all forms of electromagnetic interference. Noise and
cross talk susceptibility are proportional to length and bandwidth. Therefore the EIA RS-232-
C standard places restrictions on both. The distance is limited to 15 meters and bandwidth to
20 kbaud.
The single ended line standard EIA RS-232-C (CCITT V24/V28) is supported and recom-
mended where low data rates are required over shorter distance.

2.1.2 RS-422.

The EIA RS-422 is a differential, balanced voltage interface capable of significantly higher
data rates over longer distances. It can accommodate rates of 100 kbaud over a distance of
1200 meters. These performance improvements are derived from the advantages of a
balanced configuration that is isolated from ground noise current. It is also immune to
fluctuating voltage potentials between system ground reference and to common mode
electromagnetic interference.
The differential line standard EIA RS-422-A (CCITT V11 and X.27) is supported and
recommended where high data rates and/or the good noise rejection capability is required.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 9 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company
2.1.3 EIA RS-485

The EIA RS-485 specifications are almost identical to the RS-422 but with the exception that
RS-485 is used in Half Duplex applications.

2.2 Supported Line Setting.

The baud rate used on the transmission line:

a.) 19200
b.) 9600
c.) 4800
d.) 2400
e.) 1200
f.) 600
g.) 300
h.) 150

Supported combinations of:

a.) Bits per char.
b.) Parity.
c.) Number of stop bits.

Bits / char Parity Stop bits

7 None 2
7 Even 1
7 Even 2
7 Odd 1
7 Odd 2
8 None 1
8 None 2
8 Even 1
8 Odd 1

2.3 Supported Handshake Modes.

The handshake should be set to none in the CT2100.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 10 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

2.4 Protocol Number.

The protocol number for both VDR interface protocols is: 37

2.5 Part number, ID Text and Checksum.

2.5.1 MOS/MCS 2200 - VDR

Part Number EPROM + Firmware: 970.112.533

ID Text 970112533 VDR ALRXDR
(Can be seen in monitor mode)
Checksum (hexadecimal) E003
Fill value (hexadecimal) FF

2.5.2 Alpha4 - VDR

Part Number EPROM + Firmware: 810.000.175

ID Text 810000175-01 VDR Std
(Can be seen in monitor mode)
File name A4SIOCHK.BIN

2.5.3 MOS/MCS 2200 - VDR with Timestamp

Part Number EPROM + Firmware: 970.112.591

ID Text 970112591 VDR ALRXDR
(Can be seen in monitor mode)
Checksum (hexadecimal) 94CC
Fill value (hexadecimal) FF

2.6 Default Line Settings

The [IEC 62162-1] defines the following line settings:

Baud rate: 4800

Data bits: 8
Parity: N
Stop bits: 1

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 11 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

3 Limitations.

3.1 Physical Location.

The VDR protocol can be located in any outstation where the VDR data are available.

3.2 UMS2100 Release Dependency.

3.2.1 VDR without timestamp

The VDR protocol requires UMS2100 release 4.21 or higher.

3.2.2 VDR with timestamp

The VDR protocol requires UMS2100 release 4.72, 5.12 or 5.31 or newer.

3.3 Performance.

The VDR protocol follows the recommendation stated in [IEC61162-1] section 5.3.5 con-
cerning the transmission rate. There will be at least one second between two transmissions of
a sentence.
All sentences are resend after 10 minutes, some faster because of the requirement stated in
[IEC61162-1].
A sentence is send when its data changes.

3.4 Supported protocol functions.

The following sentences are supported:

1. ALR
2. RPM
3. XDR

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 12 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

3.5 Total Number of Sentences

The VDR protocol stores all sentences, change the data values of the sentences and transmits
them. It also keeps track of where the sentence are located in memory, which data are related
to it and when to transmit the sentence,
This information is stored in static allocated tables, the sentence and the control table.
Therefore a maximum number of sentences can be defined.

The control table size is 600 bytes.

ALR uses 6 bytes, XDR uses 11 bytes and RPM uses 7 bytes.
Number of ALR sentences: #ALR
Number of XDR sentences: #XDR
Number of RPM sentences: #RPM

Therefore the following formula can be used the determine if the protocol can hold the sen-
tences declared:
(#ALR*6+#XDR*11+#RPM*7)<600

3.6 Supported Electrical Standard.

The LM VDR protocol is able to support RS232, RS422 and RS485.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 13 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4 Customizing the VDR interface

4.1 General

The data used for the sentences must be based on data from monitoring channels or data that
has the same format and the data must be available in SLS-points.

The Modbus Output page of the CT2100 is used to specify which data must be transferred to
the VDR interface.

The contents of the analogue SLS-points ID_Mvalue and the ID_MGosSt can be used for all
three sentences.
In CT2100 versions below 5.11, the ID_MGosSt is only available if Displayed on Mimic
Diagram is checked in the Misc. Parameters page under Monitoring Channels. This option is
only available if a GOS is present. Therefore at least a dummy GOS must be present.
In CT2100 version 5.11 and newer, the ID_MGosSt is available if Coded Alarm State (Old
GOS State) is checked in the Misc. Parameters page under Monitoring Channels.

If you do not want to use the ID_MgosSt, a value with the same pattern of used bits must be
used instead. The ID_MGosSt value consists of 16 bits:
Bit no Name Use
0 -
1 -
2 -
3 -
4 -
5 -
6 Cut-out Not used
7 Sensor Fail Treated as an alarm in ALR. Data not valid. Null fields used in
XDR
8 Device Fail Data not valid. Null fields used in all sentences
9 Priority 4 Event Only used in XDR with type Switch
10 Priority 3 Alarm OR’ed.
11 Priority 2 Alarm 1 = Alarm
12 Priority 1 Alarm 0 = Normal. Only one of the bits is necessary.
13 Acknowledged 1 = Acknowledged, 0 = Unacknowledged
14 Simulated 1 = Simulated. Data not valid for VDR. Null fields used in all
sentences
15 -

The Serial Objects page of the CT2100 is used to specify which sentences must be used for
the VDR interface.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 14 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.2 ALR

This sentence is used to transmit an alarm to the VDR.

The sentence contains an alarm number (ID), the alarm state, the acknowledge state and text
describing the alarm.
The text cannot be transferred from the Gamma Micro and the field is therefore transmitted
as a null field (,*). The alarm number (alarm ID) is a 3-digit number with the range 0 – 999.

If the alarm is related to an analogue limit alarm, the XDR sentence can be used to show the
actual value. In that case the alarm ID of the ALR and XDR sentence must be the same.

The alarm state and acknowledge state are found in the ID_MGosSt value.

Example of an ALR sentence without timestamp:

$ERALR,,018,A,A,*5D
There is no descriptive text.

Example of an ALR sentence with timestamp (see section 4.2.1):

$ERALR,134557.00,018,A,A,*5D
There is no descriptive text.

4.2.1 How to include timestamp

Timestamp is supported in version 4.72, 5.12 & 5.31 and newer.

Create a Non Standard Control, Grafedit Project in the same PLC as the protocol.

It must contain the following msc-code:

UTC time used as timestamp:

pdef send_time
pt trigger
ESC 260, 0, 2 exit

pdef trigger
npt trigger
timud 5,5 exit

Local time used as timestamp:

pdef send_time
pt trigger
ESC 261, 0, 2 exit

pdef trigger
npt trigger
timud 5,5 exit

In version 5.31 and newer 260 is LIT_seri_out_UTC and 261 is LIT_seri_out_LT.

The time will be transferred to the VDR protocol every 1 second.
SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg
Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 15 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.3 RPM

This sentence is used to transmit the answerback values rpm and pitch to the VDR.
The sentence contains a one letter source ID (E=engine=1, S=shaft=2), an engine/shaft num-
ber (0-255), an rpm value, a pitch value and a data valid field.
Since there is only one data valid field, this field will indicate invalid data, if just one of the
values is invalid.
It is possible not to use the pitch value on fixed propeller engines.

The data valid state is found in the ID_MGosSt values.

If sensor fail occurs the values are still transmitted but the data valid field will indicate inva-
lid data.
If device fail occurs the related value will be transmitted as a null field (,,) and the data
valid field will indicate invalid data.

Example of a RPM sentence:

$ERRPM,E,112,-02523,-02523,V*55
Data are not valid.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 16 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.4 XDR

This sentence is used to transmit analogue transducer values or switch/valve states to the
VDR.

NOTE: One XDR sentence can contain 4 values/states.

This limit is included because otherwise the maximum sentence length of 79 charac-
ters is exceeded.

A data set consists of a one-letter transducer type, a transducer value/state, an engineering

unit and a transducer ID.
The types and units are fixed in [IEC 61162-1]. The transducer ID is a three-digit number (0-
999).
To be able to determine if the sensor and device fail, ID_MGosSt must be used.
If the value of ID_MGosSt contains sensor fail or device fail the value field will be null (,,
or ,*).

ID_Mvalue must be used as value, unless the value is binary. Then ID_MGosSt must be
used as value.
For binary values, remember to use transducer type ‘S’. If the event or an alarm bit is set the
value in the XDR sentence will be ‘1’, otherwise it will be ‘0’.

NOTE: A data value in a XDR sentence is always build upon two values. Either upon a
combination of ID_Mvalue and ID_MGosSt values or upon two identical ID_MGosSt val-
ues, if the value is binary.

Example of a XDR sentence:

$ERXDR,C,+0234.5,C,001,A,+0098.4,D,002,D,+00.040,M,003,F,+062.90,H,004*71

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 17 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.5 Serial Objects.

4.6 Creating a serial object for communication line supervision time.

There is no way to detect if the communication line has failed. This protocol is a talker protocol
without reply.

4.7 Creating the Serial Objects.

Basic Settings
Number of Data Fields in Object: 1
Object Specification: 0 – 39

4.7.1 Common object parameters

The common object parameters are the sentence specification and the talker ID.

Object Parameters
Object Pa- Value Description
rameters
Parameter 1: 2, 5 and 7 Sentence Specification
ALR 2 Set Alarm State
RPM 5 Revolutions
XDR 7 Transducer Measurements
Parameter 2: 3 – 10 Talker ID
ER 3 Engine Room Monitoring System
FD 4 Fire Door Controller / Monitoring Panel
FR 5 Fire Detection System
HD 6 Hull Door Controller / Monitoring Panel
HS 7 Hull Stress Monitoring System
RC 8 Propulsion Remote Control System
SG 9 Steering Gear / Steering Engine
WD 10 Watertight Door Controller / Monitoring Panel

ER is the talker ID used for alarm and monitoring systems. RC is used for propulsion remote con-
trol systems.
The talker ID identifies the origin of the message data.
It is only allowed to place alarms with the same talker ID in a serial object.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 18 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.7.2 ALR Object Parameters

Parameter 3: 1-8 Number of Alarms

Parameter 4: 0-1023 1st Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 5: 0-999 1st Alarm ID
Parameter 6: 0-1023 2nd Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 7: 0-999 2nd Alarm ID
Parameter 8: 0-1023 3rd Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 9: 0-999 3rd Alarm ID
Parameter 10: 0-1023 4th Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 11: 0-999 4th Alarm ID
Parameter 12: 0-1023 5th Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 13: 0-999 5th Alarm ID
Parameter 14: 0-1023 6th Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 15: 0-999 6th Alarm ID
Parameter 16: 0-1023 7th Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 17: 0-999 7th Alarm ID
Parameter 18: 0-1023 8th Modbus Output Address where the analogue value with the
monitoring channels states is stored. (_MGosSt)
Parameter 19: 0-999 8th Alarm ID

The alarm ID is a unique number within the complete set of ALR sentences used in a VDR inter-
face. Other sentences using IDs may use the same numbers.
The Modbus output address refers to the address on Modbus Output page in the CT2100.
The get the parameter value, 30000 are subtracted from the address. E.g. 30143 are 143.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 19 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

4.7.3 XDR Object Parameters

The XDR message consists of a number of measurement data. A worst-case calculation of the size
of the measurement data fields shows that one sentence can contain only 4 measurements, when
the sentence length must not exceed 79 characters. (The largest value will be –xxx.xx)
Parameter 3: 1 – 5 Number of measurement data
Parameter 4: 0 – 1023 Modbus Output start address where the first value with the
monitoring channels value is stored.
Parameter 5: 1 – 14 1st Transducer Type
C 1 Temperature C deg. C
A 2 Angular displacement D deg.
D 3 Linear displacement M meters
F 4 Frequency H hertz
N 5 Force N Newtons
P 6 Pressure P Pascals
R 7 Flow Rate l litres/s
T 8 Tachometer R rpm
H 9 Humidity P %
V 10 Volume M m3
U 11 Voltage V Volts
I 12 Current A Amperes
S 13 Switch or Valve Null none
G 14 Generic Null none
The unit are fixed for each transducer type.
Parameter 6: 0 – 4 1st Comma Position
Parameter 7: 0 – 999 1st Transducer ID (Value ID)
Parameter 8: 1 – 14 2nd Transducer Type
Parameter 9: 0 – 4 2nd Comma Position
Parameter 10: 0 – 999 2nd Transducer ID (Value ID)
Parameter 11: 1 – 14 3rd Transducer Type
Parameter 12: 0 – 4 3rd Comma Position
Parameter 13: 0 – 999 3rd Transducer ID (Value ID)
Parameter 14: 1 – 14 4th Transducer Type
Parameter 15: 0 – 4 4th Comma Position
Parameter 16: 0 – 999 4th Transducer ID (Value ID)
The Modbus Output start address refers to the address on Modbus Output page in the CT2100.
To get the parameter value, 30000 are subtracted from the address. E.g. 30143 are 143.
The first data for the sentence must be placed on the start address.
No vacant addresses are allowed within a block.
XDR data consist of a monitor channel value and its state or two states in case of a binary
value. This data set occupies two addresses. The value must be placed first, then the state,
then the next data set and so on.

The transducer ID is a unique number within the complete set of XDR sentences used in a VDR
interface. Other sentences using IDs may use the same numbers.
The transducer types and units are a fixed set within the IEC 61162-1.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 20 of 21
Release Note SAM Electronics GmbH
Serial Interface to VDR Interface Lyngsø Marine A/S
an L3 communication company

The comma position is the comma position within a value. Zero means no comma.

4.7.4 RPM Object Parameters

Parameter 3: 1–4 Number of RPM sentences

Parameter 4: 0 – 1023 1st Modbus Output start address. (Where the first analogue
value and state is stored.)
Parameter 5: 0–1 1st Pitch included (Must be No for fixed propeller)
0 No
1 Yes
Parameter 6: 1–2 1st Source ID
1 Engine
2 Shaft
Parameter 7: 0 – 255 1st Engine or Shaft Number
0 Single or on centre-line
Odd Starboard
Even Port
Parameter 8: 0 – 1023 2nd Modbus Output start address.
Parameter 9: 0–1 2nd Pitch Included
Parameter 10: 1–2 2nd Source ID
Parameter 11: 0 – 255 2nd Engine or Shaft Number
Parameter 12: 0 – 1023 3rd Modbus Output start address.
Parameter 13: 0–1 3rd Pitch included
Parameter 14: 1–2 3rd Source ID
Parameter 15: 0 – 255 3rd Engine or Shaft Number
Parameter 16: 0 – 1023 4th Modbus Output start address.
Parameter 17: 0–1 4th Pitch included
Parameter 18: 1–2 4th Source ID
Parameter 19: 0 – 255 4th Engine or Shaft Number

The Modbus output start address refers to the address on Modbus Output page in the CT2100. To
get the parameter value, 30000 are subtracted from the address. E.g. 30143 are 143.
The first data for the sentence must be placed on the start address.
No vacant addresses are allowed within a block.

Rpm and pitch data consist of a value and its state. These data sets occupy four addresses. If pitch
is not included only two addresses are used.
The rpm value must be placed first, then the state, then the pitch value and the state and then the
next data set and so on.

The Engine or Shaft number must be unique for each sentence. This number can be reused in
the ETL and the PRC sentences.

SAM Electronics GmbH • Behringstraße 120 • D-22763 Hamburg

Lyngsø Marine A/S • 2 / Lyngsø Allé • DK-2970 Hørsholm
970.105.000-07 28-09-2006 Page 21 of 21