Operation

Report

Dettifoss
IMO 9822853

Operation Copenhagen
Attendance period: 2020-07-27 - 2020-07-29
 Report
Name of Vessel: Dettifoss IMO No: 9822853
Name of Yard: GUANGZHOU WENCHONG SY Hull No: H5647
Engine Type: 7G60ME-C9.5-EGRBP Sea Trial: 2019-06
Engine Builder: CMD Engine No: CE0590
A
Job Order No: 3-05727-4-01 Run.hours: 1486
External Workforce: Yes No Workshop:
Place: Århus - Aalborg Service Center: Copenhagen
Period: 2020-07-27 - 2020-07-29 ECS Version: 1609-6.4
Visit by / [Author]: Philip Hughes, PLH/EEEO9 ERCS Version: 1803-1.8
Copy to dept and/or person (init.):
Owner/Manager: Eimskip Island ehf
Requested by: MAN ES-CPH, Jesper Arvidsson, Dept. EEEO8
Reason: Data Acqusition from OSU and EMS (PMS v5)
Summary and Conclusion:
Extent of work:
 Network Layout prepared for data acquisition from OSU 1&2 on engine LAN.
 Data connection to EMS setup over serial line (see sketch attached).
 Network extended in ECR by use of unmanaged switch (Pos 2c).
 Network extended in ER – PMI DAU cabinet – by use of M12 switch (unmanaged, Pos 2d).
 Ship LAN extended by unmanaged switch (pos 2e) in ECR.
 Custom CoCoS was setup to acquisition process values from 2 OSUs and from EMS PMS v5.

Conclusion:
Data acquisition to OSU controllers and EMS set up successfully. Data stored locally on measurement
Laptop onboard.

Recommendation:
MAN recommends to replace the EMS-MOP with new, and enroll M/V Dettifoss in MAN CEON Data Cloud
free of charge, enabling easier/better sharing of data with EimSkip.

EEO/PLH/MER/22821-2020
2020-08-13

Philip Hughes
Setting up custom CoCoS:
CoCoS was setup to sample OSU1 and OSU2 running parameters from modbus_tcp.

// DA_tcp_OSU_n ; db
//Opv ;Idx;mb; Reg ; //Remark
CO_exhgas_nox_wago ;0 ;1 ; 1000; //[A]: NOx Reading
CO_exhgas_o2_wago ;0 ;1 ; 1001; //[B]: O2 Reading
BO_nox_sensor_OK ;0 ;1 ; 1002; //[C]: NOx Sensor OK (1/0 = OK/Bad)
BO_nox_canbus_OK ;0 ;1 ; 1003; //[D]: Canbus to Sensor OK (1/0 = OK/NOK)
BO_sensor_heatelm_OK ;0 ;1 ; 1004; //[E]: Sensor Heater Element OK (1/0 = OK/NOK)
BO_sns_htelm_intrng_OK;0 ;1 ; 1005; //[F]: Sensor Heater Element Inside Temperature Rangee OK
BO_nox_sns_CommAlrm ;0 ;1 ; 1006; //[G]: NOx Sensor Common Alarm (1/0 = OK/Raised)
NU_byte4 ;0 ;1 ; 1007; //[H]: Status Byte 4: (Sensor OK = 85d)
NU_byte5 ;0 ;1 ; 1008; //[I]: Status Byte 5: (Sensor OK = 159d)

Two sensors per OSU = 4 sensors in all indexed from 0 – 3. 4x9 = 36 values in total.

For synchronising OSU values into engine data stream, CoCoS was also setup to acquisition of
below values from EMS (PMS v5).

PMS modbus
Register Value
30014 Average mean indicated pressure
30029 Average maximum cylinder pressure
30044 Average cylinder compr. pressure
30045 Pmax setpoint
30046 Pcomp setpoint
30047 Pcomp/Pscav setpoint
30054 ECS, scavenge air receiver pressure
30055 ECS speed setpoint
30056 ECS, engine speed
30057 ECS, estimated engine load
30058 PMI, estimated engine load
30059 Active engine running mode
30123 T/C speed (filtered)
30229 FO Index
180 Ambient Pressure, 8802
181 Compressor Inlet Temperature, 8818
244 Compressor Inlet Humidity, 8819
30263 O2 concentration set point
30264 Actual O2 concentration
30265 EGR cooler inlet temperature
30266 EGR WMC outlet temperature
30267 Pressure EGR blower inlet
30268 Gas differential pressure EGR cooler
30269 Gas differential pressure EGR unit
30270 EGR Blower dp, EGR Blower 1
30271 EGR Blower dp, EGR Blower 2
30272 EGR Blower speed, EGR Blower 1
30274 EGR Blower 1 speed setpoint
30276 EGR Blower throttle valve differential pressure, BTV 1
30278 EGR Blower throttle valve position, BTV 1
30280 EGR Blower throttle valve 1 position setpoint
30282 EGR Cylinder bypass valve position
30283 EGR Cylinder bypass valve setpoint
30284 EGR Blower throttle valve outlet temperature
30285 EGR Process water actual pH, Sensor 1
30286 EGR Process water actual pH, Sensor 2
30287 EGR Process water pH setpoint
 5/11

Setting up data sampling on engine LAN:

Network Connection to PMI DAU (cable a in network sketch) was used to extent the engine LAN
in the ECR using an unmanaged RJ45 ethernet switch (pos 2c) and in the E/R with an
unmanaged M12 ethernet switch (pos 2d).

Extension of Engine LAN in ECR (port 4) - 2c Extension of Engine LAN in E/R – 2d.
5port switch below MGuard M12 switch in DAU cabinet

Network sketch (photo in page 7):

 6/11

24v supply to un-managed switch (Pos 2c) and to ADAM4572 (pos a2) was taken from the
managed switch supply (pos 2). 220v supply to measument laptop (pos 10) was taken from
inside the console.

EGR OSU 1&2: After powering up the OSU WAGO PLCs,

no connection could be established from the engine network.
The network plug (pos 4d - adjacent) was found failing and
replaced. With an Ethernet connection established, both
PLC’s were found to have the same default IP address from
the initial SW setup, = IP: 172.17.17.105.

Connecting the PLC’s one at a the time, and logging on to

the PLC admin page (with IE), the IP setup was changed to:

OSU #1: IP 172.17.17.101 SubN: 255.255.255.0

OSU #2: IP 172.17.17.102 DefGW: 172.17.17.1

Logon to
wago admin
web page
and setup of
fixed IP on
engine LAN.
 7/11

OSU O2 values on custom CoCoS. Connection testing by ‘Breathaliser’. The difference in return
to the 21% O2 pattern is due to mechanical routing and dissipation of the exhaust gas after the
probes.

Modbus connection to EMS;

EMS’ Private Modbus Server ‘PMS’ was enabled on the EMS by loading the license key from
MAN. PMS serves modbus_tcp requests using slave ID 3 and Function Code 04. CoCoS on the
other hand uses modbus_tcp with FC 03, but has a serial modbus_RTU master requesting with
FC 04. So CoCoS was setup to use serial modbus (RTU) with FC04 (da_mbus_fc4.dll) but
through a USB serial converter (ADAM4561) and a modbus_tcp gateway (ADAM4572) according
to the sketch below.

The 4572 modbus tcp gateway had to be ‘inverted’ to work as a modbus master. Normal working
mode is to strip modbus_tcp frames of their IP and ‘forward’ the modbus frame on the serial port).

0) ADAM4561 driver provides laptop a COM port (named ‘COM2’ with device manager)
then:
1) CoCoS (da_mbus_fc4_pms5.dll) issues a modbus_rtu master request on COM2
2) ADAM4561 converts to a modbus rtu master request transmitted on RS485 terminals
3) ADAM4572 Receives modbus_rtu request on RS485 terminals
4) ADAM4572 ‘repackages’ the modbus request in an IP frame and forwards it on Engine
LAN. The incoming modbus request has no IP target (since it is serial modbus).
ADAM4572 has to be setup in ‘Master Mode’ and the slave IP – the EMS-MOP - must be
configured in the Gateway – ref photo below.
5) EMS’ PMS interface replies the modbus_tcp request to 172.17.17.7 and the process is
reversed.
 8/11

Setup of
ADAM4572:

Succesful
data
acquisition
from OSU #1
& #2, and
from EMS.

Engine LAN overview complete (ref. sketch page 4):

Custom CoCoS laptop was placed on top of

the AMS console. Power supply from 220v
outlet inside
 9/11

the console.

CoCoS will AutoOpen on startup.

The engine has to be opened manually_
system -> open engine ->
‘CE0590A – OSU..’)

Empty CoCoS on start up.

Connection to Ship Internet:

The WAN side of the MGuard was connected to the ship’s Network through the network plug
‘LAN 10-21’ located at the end of the AMS console at the CCTV terminal. A 10m red LAN cable
(f) was pulled to the new office type unmanaged switch (2e), inserted between the CCTV terminal
and Ship LAN.
 10/11

MGuard VPN Firewall. Connection to Extending the Ship LAN by unmanaged switch 2e.
MAN Online Service portal for Remote Cable q: original connection to Ship LAN 10-21 socket
Attendance through cable f and Ship Spare LAN cable left for mounting 2e under the desk.
LAN.

The MGuard WAN IP was set by logging on the the MGuards Web Admin page from the EMS-
MOP using Internet Explorer. It was set Fixed IP address: 10.5.71.14 Default Gatway: 10.5.71.1
according to the agreement with Subnet mask: 255.255.255.0 DNS: 10.5.71.10 (not used)
EimSkip.

Note:
When connected to MAN’s servers, the ‘Info’ LED will be Constantly Lit.
If/when not connected, the Info LED will Blink.

Note: Cable f goes through an existing

(‘sharp’) hole in the AMS console.

Set fixed IP on MGuard WAN from EMS-MOP

MAN recommends the Chief/Electrician to reroute this cable through a new hole and along the
floor, or to smoothen the hole using a cable rubber of sorts.

Remote Attendance/Troubleshooting Assistance:

 11/11

Named ‘OSU_laptop’ the custom CoCoS PC was added to MAN’s Online Service Portal for
remote connection.

Remote connection to the

ECS, ERCS, EMS and
Custom Laptop is possible as
long as the red cable f is
connection.

Disconnecting cable f will not

raise alarms anywhere.

Only Authorised MAN users

from within MAN’s network
can access M/V Dettifoss.

We recommend to enroll EimSkip in the MAN CEON data Cloud (https://manceon.io).

This will open Data Access for EimSkip, as
well as enabling continuous monitoring.

It will require:
a) a new EMS-MOP (supplied Free of Charge
for this vessel).
b) Update MGuard WAN port settings on the
Ship LAN – ref. the attached
“Connectivity_checklist_PSA_mGuard.pdf”
c) Accepted EULA (MAN is allowed to log
EimSkip’s engine data).