OSD 5.4 User Manual

Miros OSD
User manual
Doc. No
PR-003/DD/008
Product
PR-003 - OSD Recovery
Classification
Open
Abstract:
The OSD 5.4 user manual contains information about how Miros OSD works, how to operate the
system and how to troubleshoot it.
Revision No.
Date
Prepared by
Checked by
Approved by
1
51 pages
2015-10-26
BSB
PJK
VSB
Description:
Updated for OSD-R version 5.4.
Blank page.
Miros OSD
TABLE OF CONTENTS
1
Foreword
6
1.1
Safety Instructions........................................................................................................... 6
1.2
Operational Warnings...................................................................................................... 6
2
2.1
Introduction
6
Abbreviations and definitions ........................................................................................... 7
2.1.1
Abbreviations ...................................................................................................... 7
2.2
Referenced publications .................................................................................................. 8
2.3
About this document........................................................................................................ 8
2.4
3
3.1
3.2
4
2.3.1
Intended audience ............................................................................................... 8
2.3.2
Navigating the manual ......................................................................................... 8
How to contact Miros AS ................................................................................................. 9
The OSD system
10
Hardware configuration ................................................................................................. 10
3.1.1
Marine radar...................................................................................................... 11
3.1.2
Integrated video digitizer.................................................................................... 11
3.1.3
OSD computer .................................................................................................. 11
3.1.4
Keyboard and pointing device............................................................................ 11
3.1.5
Display .............................................................................................................. 12
3.1.6
Interface unit ..................................................................................................... 12
3.1.7
Video digitizer.................................................................................................... 12
Software........................................................................................................................ 13
3.2.1
Operating system .............................................................................................. 13
3.2.2
OSD 5.4 system software .................................................................................. 13
Operating principles
14
4.1
Automatic detection by means of radar data processing ................................................ 14
4.2
Oil spill detection by means of infrared camera system .................................................. 16
5
Man-machine interface
18
5.1
General ......................................................................................................................... 18
5.2
Commanding tools ........................................................................................................ 18
5.3
User Interface concepts................................................................................................. 19
5.3.1
Menu bar ........................................................................................................... 20
5.3.2
Layouts ............................................................................................................. 20
Miros AS
Page 3 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.4
5.5
6
5.3.3
Layers and buttons ............................................................................................ 22
5.3.4
Other MMI functionality...................................................................................... 22
5.3.5
Timeouts and invalid data .................................................................................. 23
5.3.6
Position data ..................................................................................................... 23
Data presentation widgets ............................................................................................. 24
5.4.1
Numeric widget ................................................................................................. 24
5.4.2
Rose widget ...................................................................................................... 24
5.4.3
Heading widget ................................................................................................. 24
5.4.4
Rate of turn widget ............................................................................................ 25
5.4.5
Oil track widget.................................................................................................. 25
Application modules and floating views.......................................................................... 26
5.5.1
OSD module...................................................................................................... 26
5.5.2
AIS module ....................................................................................................... 27
5.5.3
Gimbal functions................................................................................................ 29
5.5.4
Radar module.................................................................................................... 31
5.5.5
Report Module................................................................................................... 31
5.5.6
Alarm module .................................................................................................... 32
5.5.7
About view ........................................................................................................ 32
Using OSD
34
6.1
System start-up ............................................................................................................. 34
6.2
Manually triggering the start-up sequence ..................................................................... 34
6.3
Locating a spill .............................................................................................................. 34
6.4
Data storage ................................................................................................................. 34
6.5
Third party data access ................................................................................................. 35
6.6
Check radar interface status .......................................................................................... 35
6.7
System restart ............................................................................................................... 36
7
7.1
6.7.1
OSD software restart ......................................................................................... 36
6.7.2
Video system restart .......................................................................................... 36
6.7.3
Graphical user interface restart.......................................................................... 36
6.7.4
Computer software restart ................................................................................. 36
6.7.5
Hardware restart................................................................................................ 37
6.7.6
Computer power cycle ....................................................................................... 37
Interpreting averaged BSI images and detections
The back scatter intensity (BSI) image with Oil .............................................................. 38
7.1.1
8
38
Situations where the information in a BSI image can be misleading ................... 40
System maintenance
Miros AS
42
Page 4 of 51
PR-003/DD/008, rev. 1
Miros OSD
8.1
OSD system .................................................................................................................. 42
8.2
The radar ...................................................................................................................... 42
9
Technical data
43
9.1
Radar ............................................................................................................................ 43
9.2
OSD performance data.................................................................................................. 43
9.3
9.2.1
System range .................................................................................................... 44
9.2.2
System resolution.............................................................................................. 44
Software........................................................................................................................ 45
10 Troubleshooting
46
10.1 Troubleshooting action list ............................................................................................. 46
10.2 Advanced trouble shooting ............................................................................................ 47
10.3 Support ......................................................................................................................... 48
11 Frequently asked questions
Miros AS
49
Page 5 of 51
PR-003/DD/008, rev. 1
Miros OSD
1
Foreword
1.1
Safety Instructions
RADIO FREQUENCY RADIATION HAZARD
The OSD radar antenna emits electromagnetic radio frequency (RF) energy that
can be harmful, particularly to human eyes. Never look directly into the radar
antenna aperture from a close distance while the radar is in operation, or
expose yourself to the transmitting radar antenna at a close distance. Consult
the radar Operator’s Manual for more information.
If the radar antenna unit is installed at a close distance to an area where people
reside, this may require halt of transmission within a certain sector of antenna
revolution. This is possible on nearly all X-band marine radars. Ask your radar
representative or dealer to provide this feature.
ELECTRICAL SHOCK HAZARD
Do not open the radar components or any of the OSD hardware components.
Only qualified personnel should work inside this equipment.
WARNING
Do not disassemble or modify the equipment. Fire, electrical shock or serious
injury can result.
1.2
Operational Warnings
ALIEN SOFTWARE
Do not install any software unrelated to OSD on the supplied computer. Doing
so may result in a malfunctioning OSD system.
2
Introduction
Miros OSD is designed to detect the presence of oil on water and to determine the outline of a
spill (position and area) and drift. This is achieved by processing sea clutter measured with Xband marine radar. Further, the system includes optional integration of infrared cameras for
inspection and verification of radar detections.
This User Manual contains guidelines for operation, maintenance and basic troubleshooting. It
also provides a brief system description, explains theory of operation and contains a “Frequently
Asked Questions” section.
Miros AS
Page 6 of 51
PR-003/DD/008, rev. 1
Miros OSD
2.1
Abbreviations and definitions
Abbreviations are used both when presenting OSD data on a display, and in the OSD
documentation.
2.1.1
Abbreviations
Table 1 is a lists of general abbreviations used in the OSD system.
Abbreviation
AIS
BSI
COG
deg
FTP
Meaning
Automatic Identification System
Back Scatter Intensity
Center of Gravity
Degrees
Det Norske Veritas
Germanischer Lloyd
File Transfer Protocol
GB
Gigabytes
DNV-GL
GPS
GUI
Hz
IP
IR
kW
Kilowatts
LAN
Local Area Network
LED
m
m/s
Light Emitting Diode
Metre
Metres per Second
MB
Megabytes
MMI
Man-Machine Interface
Nano-second
NMEA
National Marine Electronics
Association
OSD
PDF
PRF
RPM
s
Oil Spill Detection
Portable Document Format
Pulse Repetition Frequency
Revolutions Per Minute
Second
SOG
Speed over Ground
Std. Dev.
Miros AS
Global Positioning System
Graphical User Interface
Hertz
Internet Protocol
Infra Red
Kilobytes
SP
Radar echo amount
Unit of direction
Classification Society
Unit of file size and storage capacity
(1 GB = one billion bytes)
kB
ns
Remark
Service Pack
Standard Deviation
Sync
Synchronization
TCP
Transmission Control Protocol
Page 7 of 51
The visible part of a software system
Unit of Frequency
Unit of file size and storage capacity
(1 kB = one thousand bytes)
Unit of energy (1 kW = 1000 Watts)
System for sending data between
computers
Status indicator “lamp”
Unit of distance
Unit of speed
Unit of file size and storage capacity
(1 MB = one million bytes)
Typically display, keyboard and
pointing device (mouse, trackball)
Unit of time (1 ns = 10-9 seconds)
A combined electrical and data
specification for communication
between marine electronic devices
such as GPS, sonars, anemometer
(wind speed and direction),
gyrocompass and many other types of
instruments
Developed by Adobe Systems
Number of pulses per second
Unit of rotation speed
Unit of time
Vessel speed relative to earth, as
shown by GPS
Software upgrade.
Measure of variability or diversity used
in statistics
In this context also called Radar
Trigger
PR-003/DD/008, rev. 1
Miros OSD
TFT
UTC
VGA
Widget
XGA
Table 2.1:
2.2
Thin Film Transistor
Coordinated Universal Time
Video Graphics Array
A GUI widget is a GUI element
that displays an information
arrangement changeable by the
user, such as a window or a
text box
Extended Graphics Array
A type of LCD display
Replaces Greenwich Mean Time
Computer Display Standard
Computer Display Standard
General OSD system abbreviations.
Referenced publications
The following publications are referenced in this manual and offer more detailed information
about the OSD system:
[1] PR-003/DD/002, Miros OSD – Operating Principles.
[2] PR-003/DD/006, Miros OSD – Third Party Data Access.
All documents referred to in this manual can be found in the electronic documentation delivered
with all new OSD systems, unless stated otherwise.
2.3
2.3.1
About this document
Intended audience
This document describes the day-to-day operation of Miros OSD. It is aimed mainly at
operational users. Users who require more detailed information about the operating principles of
the OSD system and how to customize the system hardware and software are referred to the
reference publications.
It is assumed that the reader has basic knowledge about personal computers and MS Windows
operating systems.
2.3.2
Navigating the manual
For most users, it is not necessary to read the manual back-to-back. The following introduction
to the content and intentions of the various chapters can be used as a guideline for choosing
what to read and when:
Chapter 1 - Foreword
This chapter contains information about safety and proper use. Make sure that the safety
instructions and operational warnings are read and understood before the OSD equipment,
including the radar, is powered up and put into operation.
Chapter 2 - Introduction
This chapter contains important and useful information on navigating this document.
Chapter 3 - The OSD system
This chapter explains hardware and software building blocks in an OSD system. Read the
whole chapter once prior to start-up to get familiar with the system. Later on this chapter can be
addressed whenever needed.
Chapter 4 – Operating principles
Miros AS
Page 8 of 51
PR-003/DD/008, rev. 1
Miros OSD
This chapter is a brief overview of the fundamental principles behind OSD and how the system
works. Read it once before starting to use the system. The information gives a useful
background for better understanding and operation of Miros OSD.
Chapter 5 - Man-machine interface
This chapter contains the basic principles of how an operator interacts with the OSD system. It
describes the commanding tools such as keyboard and pointing device as well as the GUI.
Further, the chapter also describes the various data modules in the system and defines the kind
of information they make available to the operator. It is recommended that this chapter is read
together with chapter 6.
Chapter 6 - Using OSD
This chapter describes how to perform basic system operations. The chapter should be read in
full.
Chapter 7 – Interpreting BSI images
This chapter explains basic properties of the BSI image and provides critical information about
how to separate oil from false detection. This chapter can be read independent from the rest.
Chapter 8 – System maintenance
This chapter describes periodic maintenance.
Chapter 9 – Technical data
This chapter contains information about OSD performance.
Chapter 10 – Troubleshooting
This chapter contains a troubleshooting action list the user can consult when attempting to solve
error conditions.
Chapter 11 – Frequently asked questions
This chapter gives answers to radar and OSD system questions that are often asked.
2.4 How to contact Miros AS
Mail address:
Miros AS
P.O. Box 364
N-1372 Asker
Norway
Phone:
Telefax:
E-mail general:
E-mail service&
support:
+47 66 98 75 00
+47 66 90 41 70
[email protected]
[email protected]
[email protected]
Web:
www.miros.no
Miros AS
Page 9 of 51
PR-003/DD/008, rev. 1
Miros OSD
3
The OSD system
Miros OSD detects oil on water and oil drift by processing sea clutter measured with standard
marine X-band (3 cm) radar. The system can either be connected to a dedicated radar or
operate as a slave on an existing navigational radar.
Note:
3.1
The Miros OSD system will not, in any way, interfere with radar signals to the
navigation display when the system is operated as a slave on an existing
navigation radar. This means the Miros OSD system is well suited to be retrofitted
on a vessel.
Hardware configuration
The OSD system consists of the following hardware components:
·
·
·
·
·
·
·
·
·
·
Marine X-band radar (shared or dedicated).
EM-129 Integrated video digitizer (for digitizing radar video).
Windows computer (marine certified or rack mounted).
Display.
Keyboard.
Pointing device.
EM-124 Radar buffer amplifier (optional).
SM-134 OSD Interface unit (optional).
SM-098 Wind sensor (optional).
FLIR IR camera gimbals and associated SM-151 video digitizer (optional)
Figure 3.1: OSD system overview, including optional components.
Miros AS
Page 10 of 51
PR-003/DD/008, rev. 1
Miros OSD
GPS and gyro sensors are not part of the standard OSD system because these sensors are
typically available on vessels where access to such data is required.
3.1.1
Marine radar
Any X-band radar can in principle be used, but preferred models are:
·
·
Furuno FAR 2117/ 2127.
Sperry Marine VisionMaster.
Miros recommends radars with antenna size of 6 feet or greater, and antenna speed greater
than 20 RPM. The radar output to the OSD system should not be influenced by any signal
processing demands placed on the radar by other systems receiving signals from it. If the radar
signal output to the OSD system is affected by adjustments made on the radar operator
interface, processing in the radar should be turned off. That is, special filtering, gain control,
STC and other signal processing elements must be kept at a minimum, and if they exist, be
approved by Miros.
3.1.2
Integrated video digitizer
The EM-129 Integrated video digitizer is a component designed to digitise radar BSI images
from analogue radar signals. It comprises a custom radar interface board and a radar image
processing board.
Figure 3.2: EM-129, Integrated video digitizer.
3.1.3
OSD computer
OSD algorithms, user interface and other control software are typically run on a fanless
maritime computer, such as the SM-150. Other options, like a rack mounted computer, are
available. The computer takes input from system sensors on isolated serial ports and on
Ethernet. The computer needs a high capacity processor, typically Core i7.
Figure 3.3: The SM-150 standard computer. Front and rear view.
3.1.4
Keyboard and pointing device
User input is enabled with keyboard and a pointing device. The system is delivered with a
standard 104 key US keyboard and a trackball.
Miros AS
Page 11 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 3.4: Typical keyboard and trackball.
The keyboard is mainly required for system administration and configuration. Most of the time,
the keyboard can be stowed away because a pointing device alone will satisfy most
requirements for user input during normal operation. However, do not disconnect the keyboard.
3.1.5
Display
The OSD system comes delivered with either a standard flat screen display, or a marine
certified flat screen display. The latter is DNV approved for maritime use and can be rackmounted or fixed using tilt and rotating brackets.
3.1.6
Interface unit
The interface unit is used on installation sites where it is required that NMEA signals from wind,
gyro, AIS and GPS are terminated at a different location from where the OSD computer is
installed. Several of the computers supplied with Miros OSD are capable of direct connection to
NMEA signal cables.
The SM-134 Interface Unit consists of a 4-channel RS-422 serial to IP Interface, a LAN switch,
power supply and terminal blocks. It is powered by 100 - 240 VAC through a 6 A fuse/switch.
The four RS-422 Interfaces are typically used for:
·
·
·
·
Heading information, typically NMEA-0183 HDT sentence from a gyro.
Vessel track and time, typically NMEA-0183 VTG and ZDA from a GPS.
Wind speed and direction, typically NMEA-0183 MWV from a wind sensor.
OSD data output, Miros generic NMEA format.
Figure 3.5: Optional SM-134 interface unit.
3.1.7
Video digitizer
When optional FLIR IR camera gimbals are in use, the video signal is digitized in an SM-151
video digitizer. This unit is also capable of performing the tasks of the SM-135 interface unit.
Miros AS
Page 12 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 3.6: Optional SM-151 Video digitizer.
3.2
Software
Miros OSD consists of the following software:
·
·
·
3.2.1
Microsoft Windows Operating system.
OSD version 5.4 system software.
Auxiliary third party tools.
Operating system
Miros OSD is designed for MS Windows operating systems and is currently delivered with
Windows 7. For a complete list of supported operating systems, refer to chapter 9.
3.2.2
OSD 5.4 system software
The OSD system software comprises a number of software modules, each performing a specific
set of tasks. This manual does not provide a detailed description of all software components but
focuses mainly on an introduction to a selection of components that an end-user should know
about.
MirPresBridge - Data presentation is the graphical user interface for Miros OSD. How data is
displayed on screen is described in chapter 5.
MirAdm04 - Miros system manager monitors the OSD system status and manages OSD
software modules. MirAdm04 handles the following tasks:
·
·
·
·
Automatically start all OSD software modules on system start-up.
Maintain and display OSD system log files.
Monitor OSD computer system status.
Handle system events.
MirSip41 - Gimbal service connects cameras to the OSD software. MirSip41 handles the
following tasks:
·
·
Miros AS
Digitises video from gimbal mounted IR and low-light cameras.
Forwards control data to gimbals.
Page 13 of 51
PR-003/DD/008, rev. 1
Miros OSD
4
Operating principles
This chapter contains a brief overview of how the OSD system detects oil on water. Topics
covered include automatic detection by means of radar data processing and inspection and
verification of detections with an infrared camera system. Users who want a more detailed
introduction to these topics are referred to [1] “Miros OSD – Operating Principles”.
4.1
Automatic detection by means of radar data processing
Sea clutter refers to a portion of the radar echo that originates from the sea surface and is
caused by small, wind generated, surface ripples, aka. capillary waves. Sea clutter is scattered
radar pulses. Miros OSD algorithms analyse sea clutter because it contains information about
where there is oil. It is useful to understand what parameters affect the amount of sea clutter a
radar receiver measures, because sea clutter intensity has to be above a certain threshold
before oil spill detection and sea surface measurement is possible.
Sea clutter magnitude is a complex variable that depends on many parameters. Some
significant parameters are:
·
·
·
·
·
·
·
Wind speed
Wind direction
Sea state
Distance from target
Antenna height
Radar pulse mode
Radar transmitted energy
The angles Umin and Umax determine the systems operating range and is a function of radar
pulse mode, transmitted energy, antenna height and wind speed. Figure 4.1 illustrates the
backscatter intensity profile as a function of range with definition of Umin and Umax .
Figure 4.2 illustrates how sea clutter is presented as an averaged BSI image. Note the
difference in texture in one image compared with the other. This is due to different sea surface
roughness and wind conditions. The image on the left is captured during wind speeds of 8.3 m/s
while the one on the right is captured when there was no wind.
Figure 4.1: Surface area where OSD collects radar backscatter (between Umin and Umax).
Miros AS
Page 14 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 4.2: Typical illustration of sea clutter in averaged BSI images.
Oil on water smoothens out capillary waves, giving the sea surface a smooth appearance when
oil is present. This causes radar energy to be reflected away from the radar as opposed to
scattered, meaning there is less backscattered radar signal from areas covered with oil. Oil spill
detection with radar is a relative measurement and requires that there is sea clutter present
from unpolluted areas of sea. Therefore, the system will not operate when there is no wind. It
will also not operate when the entire field of view of the radar contains oil.
The system will not operate when there is too much wind. Breaking waves will disperse oil into
the water column and the contrast that once was between polluted and clean areas of the sea
disappears. This happens above a certain wind threshold. Experience from Oil on Water
exercises with oil emulsion releases, indicates wind speeds in the region of 10-14 m/s.
Oil detection is possible in short and medium pulse modes. Longer pulses contain more energy
and thereby increase operating range of the system, but it also has a blurring effect on the BSI
image that reduces system resolution.
Figure 4.3 illustrates what oil might look like in the sea clutter image produced by the processed
OSD radar image.
Figure 4.3: Sea clutter image with oil.
Miros AS
Page 15 of 51
PR-003/DD/008, rev. 1
Miros OSD
Images presented so far to illustrate examples of BSI images have a blank sector missing from
the full circle. This blank sector varies in size. It is referred to as a radar shadow and is caused
by physical obstructions that block the emitted radar pulse and echo. The radar shadow is not
included in the signal processing for automatic detection because of the signal degradation
caused by obstructing structures around the radar. Because data in the radar shadow is of no
value to oil spill detection, it is chosen to not display data from this sector.
Each vessel has different equipment installed in the vicinity of the radar, so the radar shadow
will not be the same on two vessels unless they have the same equipment installed in the same
location around the radar.
One should be aware that vessel motion affects the usable portion of the radar image, and the
area where oil spill detection is possible will depend on vessel motion. E.g. the blanking sector
grows when the vessel turns, shrinking the useable portion of the radar image. The size of the
useable portion of the radar image is therefore a function of the vessels turning rate.
4.2
Oil spill detection by means of infrared camera system
The use of infrared cameras is an optional feature that can be used to verify detections from the
processed radar images. A Miros OSD system can be used with up to two IR camera gimbals.
Each gimbal may also be equipped with a low-light camera.
When oil and water are at the same temperature, oil will emit less infrared energy than water.
This is due to differences in a physical property called emissivity. As a consequence, when you
look at an area of water polluted by oil, and the oil is at thermal equilibrium with the surrounding
water, then the oil will appear cooler than the water in an infrared image. Very thin oil layers will
not have any thermal contrast to water.
Unlike water, oil absorbs almost all light in the visible part of the electromagnetic spectrum. This
combined with the fact that the visible part of the spectrum is where most of the suns radiation is
concentrated, means that thick oil will heat up and become hotter than water. Thin oil will not do
so, mainly because it contains mostly volatile components of crude oil that are transparent to
light. This is referred to as differential heating. Not much sunlight is required to cause differential
heating of thick oil. Measurements done with overcast skies confirm that thick oil was heated so
that it appeared up to 5 Celsius warmer than the surrounding water.
As a result, during the day when the sun is out, when observing polluted areas of the sea with
an infrared camera, you will find the following:
·
·
·
You cannot see areas covered with thin oil.
Areas covered with medium thick oil will be cooler than water.
Areas covered with thick oil will be warmer than the surrounding water.
The following image provides an illustration of what you might observe. This image was taken
with a FLIR M-Series infrared camera system used on a vessel cleaning up oil in the Gulf of
Mexico after the Deep Water Horizon incident. In this image some white areas can be seen.
These are patches of thick oil that are hotter than the surrounding water. There are also some
smaller “black” areas, these are patches of thin oil that are at the same temperature as the
surrounding water. As is evident in this image, the contrast is greatest between water and thick
oil. So during the day, an infrared camera is an excellent tool for locating and focusing recovery
activities towards the thickest part of the oil.
Infrared imaging is a valuable add-on to radar-based oil spill detection. Using IR cameras and
interpreting IR images requires operator training.
Miros AS
Page 16 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 4.4: Patches of thin and thick oil in the Gulf of Mexico.
Miros AS
Page 17 of 51
PR-003/DD/008, rev. 1
Miros OSD
5
Man-machine interface
5.1
General
The man-machine interface (MMI) is the means by which the operator interacts with the Miros
OSD system. It consists of commanding tools and the graphical user interface (GUI).
MirPresBridge is the software module used for data visualization in Miros OSD systems. It is
designed for quick access to relevant information.
This section aims at explaining the different user interaction elements the interface provides.
The user interface presents and provides interaction with the following sources.
·
·
·
·
·
·
·
5.2
X-band radar oil spill detection algorithms
Wave extraction algorithms
Wind processing algorithms
Infrared camera system
AIS
GPS
Compass
Commanding tools
The operator controls the system with the following input devices:
·
·
Pointing device like a trackball or mouse.
Keyboard.
These tools are used to start/stop software modules, opening/closing windows and activating
various software module buttons.
Miros AS
Page 18 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.3
User Interface concepts
The user interface is built up with the following building block hierarchy:
·
·
·
·
Menu bar
Layouts
o
Main view
o
Side view
Floating views
Widgets
Layouts are listed as tabs in the menu bar and are activated by pressing a tab. Each layout
includes at least a main view and optionally a side view.
Floating views present information that is not inexplicably linked with a given task such as oil
spill detection. They contain data which is not mission critical and can be inspected
occasionally.
Miros AS
Page 19 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.3.1
Menu bar
The menu bar provides means for switching between enabled layouts and a menu for accessing
floating views which are not commonly shown. The menu bar also provides the means to
minimize and exit the MMI. The pull-down menu button displays:
·
·
·
·
About
Modules
o
o
o
o
Minimize
Quit
OSD
AIS
Radar
Report
Each floating view is described in more detail in sections below
5.3.2
Layouts
This section explains the following defined layouts.
·
·
·
OSD
Waves
Wind
The OSD layout is the main layout for Miros OSD. It includes information for oil spill detection
and tracking. It includes data layers such as processed radar image, oil spill detections and AIS.
A list of oil detections and their areas is provided. The OSD layout also includes navigational
information such as oil drift, surface currents, vessel heading and speed. When the infrared
video option is installed, video is also included in the OSD layout.
Figure 5.1
Miros AS
OSD layout (typical). The AIS window is a floating view that can be moved around.
Page 20 of 51
PR-003/DD/008, rev. 1
Miros OSD
The Waves layout presents critical wave parameters.
Figure 5.2
Waves layout with four important wave parameters.
The Wind layout provides instantaneous values of wind speed and direction with a time series.
Values are reduced to 10 m above sea level and they are averaged 2 and 10 minutes.
Figure 5.3
Miros AS
Wind layout. Orange graphics and text show 10 min. average wind speed while
blue graphics and text show 2 min averages.
Page 21 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.3.3
Layers and buttons
Layouts with presentation of geo-referenced data typically include layers that can be turned on
or off in the OSD layout. When a layer is shown, the background of the associated button has a
light colour. Layers will be presented in further detail below. Available layers are:
·
·
·
·
·
·
·
AIS – Automatic Identification System for vessels and buoys
SRI – Estimated OSD system range
OIL – Detected oil spills
BSI – Radar Back Scatter Intensity
Target – Position in centre of view of the IR camera
Own ship – Position, motion and history of own ship
Range rings and bearing – Grid elements
Some layers have pull-out menus for additional user interaction. To open and close the pull-out
menu, click the arrow in the layer’s associated button.
Figure 5.4
Layer buttons with OIL pull-out menu open.
The right-hand side of the main view also features directional buttons. These are:
·
·
5.3.4
GEO | SHIP – Choose whether the main view is locked to a geo-stationary position or
pans with the movement of the vessel.
HEAD | NORTH – Select vessel’s heading, vessel’s reverse heading or north as up on
the display.
Other MMI functionality
Additional MMI functionality is shown in this section. It is possible to hide and bring back the
entire side view. Elements (widgets) of the side view can be converted into floating views.
Closing such a floating view will bring it back into the side view.
The “Screenshot” button will save an image of the screen. The default save directory is
C:\Users\Miros\Pictures\Miros OSD.
Miros AS
Page 22 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.5
5.3.5
Other MMI elements
Timeouts and invalid data
The Miros OSD system relies on input from a multitude of sensors. Each data source is
monitored for timeouts and data validity. When a timeout occurs, a notice in bright yellow is
shown in the MMI. Any numerical value becoming invalid (due to timeouts or other reasons) is
replaced by the symbol “//”.
Figure 5.6
5.3.6
Timeouts notices. This particular view was captured by halting the underlying OSD
system and only running the GUI.
Position data
The bottom of the main view shows the location of the mouse pointer, to the left in georeferenced coordinates and to the right relative to the own ship. The relative view shows
distance in metres and an angle where 360° is straight ahead.
Figure 5.7
Miros AS
Position Data as shown in the main view.
Page 23 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.4
Data presentation widgets
The user interface has a collection of graphical presentation widgets that are used for data
presentation and illustration. This section provides an overview of each type of graphical widget
with information about how to interact with them when possible.
5.4.1
Numeric widget
Numeric widgets present the instantaneous value of a given parameter with descriptive
information of what is presented and a unit. Such widgets are used in the waves and wind
layouts. NB: Invalid numbers are replaced by the symbol “//”
Figure 5.8
5.4.2
Numeric widget presenting value of averaged wind speed reduced to 10 m above
sea level.
Rose widget
Rose widgets are used to present magnitude and direction of a vector such as wind speed, wind
direction and oil drift. There are two variations of the rose: one that indicates “coming from” and
one that indicates “going to”. The following figure illustrates both variations. Wind speed and
direction belong in the “coming from” category shown to the left. Sea current and oil drift belong
in the “going to” category shown on the right. Please note that north in the scale of the Rose
Widgets points the same way as in the Main View. This depends on the directional buttons
described above.
Figure 5.9
5.4.3
Left rose indicating “coming from” and right rose indication “going to”.
Heading widget
The Heading widget provides a numeric and graphical presentation appropriate to illustrate a
vessel’s heading.
Miros AS
Page 24 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.10 Heading widget.
5.4.4
Rate of turn widget
The rate of turn widget provides a numeric and graphical presentation appropriate to illustrate a
vessels rate of turn.
Figure 5.11 Rate of turn widget.
5.4.5
Oil track widget
The Oil track widget provides a list of recent oil detections with an identification number and spill
area. The following list provides a short functional description of available user interactions.
·
·
Miros AS
When a list entry is clicked, that entry is outlined in orange on the OIL layer in the
main view.
The status column shows whether the oil spill is selected by the user to be:
o Not evaluated – A new discovery in the OSD system, not yet evaluated by
the user.
o Confirmed – This is a verified oil spill.
o Rejected – This is verified to not be an oil spill. It will grayed out in the list
and the filled area is emptied.
Page 25 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.12 Oil track widget with three detections. Detection 117 is selected for status
evaluation and highlighted with orange in the OIL layer
5.5
Application modules and floating views
Naturally grouped functionalities are segregated and included in logically separated modules
that are enabled or disabled depending on system capabilities. All application modules can
operate in separate windows. The most common ones can also reside in the side view. The less
common ones are available through the menu bar. This way the user can select what
information to prioritise. The following application modules are defined:
·
·
·
·
·
·
OSD – Oil spill detection status, from menu bar.
AIS – Vessel locations, from menu bar.
Radar – Raw radar images, from menu bar.
Report – Report editor, from menu bar
Gimbal – IR video, from side view
Conning – Oil track list, rate of turn, heading, wind, oil drift and sea current widgets,
from side view
Figure 5.13 Sub menu listing installed application modules not featured on side view.
5.5.1
OSD module
The OSD module shows the time which has passed since the last updates of generated BSI
and oil detection data.
Miros AS
Page 26 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.14 BSI data is 1 second old, oil spill detection data is 13 seconds old.
5.5.2
AIS module
The AIS module provides vessel and buoy tracking when AIS input is available. The AIS floating
view will let the user set up which vessels to focus on. The AIS Target tab enables the user to
select an AIS target, pan the main view to it and redefine it as a boat or buoy. It also offers
vessel search by IMO number or vessel name.
The AIS Configuration tab of the AIS floating view lets the user instruct Miros OSD on how to
relate to lost AIS target timeouts. The lost target timeouts are defined by multiplying the
expected reporting intervals from vessels in different classes with a configurable factor. The
Target Settings periods are conveniently shared between the AIS configuration and the own
ship pull-out menu, and can be modified in either view. Changes made in one view immediately
take effect in the other. The lost target range scope is a setting for where to consider lost AIS
targets. Within this radius, lost AIS targets will trigger alarms which must be acknowledged.
Outside this radius, lost AIS targets will not trigger alarms.
When the AIS layer is enabled in the main view, icons representing individual vessels and
buoys will appear in a separate display layer. When the user clicks on an AIS target in the main
view, its properties will come up in a separate floating view. When enabled, historical AIS
positions and predicted future positions can also be shown.
Miros AS
Page 27 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.15 AIS targets: Selection of available vessels and buoys.
Figure 5.16 AIS configuration: How to set AIS timeouts and vectors.
Miros AS
Page 28 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.17 AIS and own ship configuration. “Velocity vector” toggles the display of estimated
motion for both AIS targets and own ship. “Past track” toggles own ship history.
“PAST POSN” toggles AIS target history. The “TIME INT” settings are the same as
in the AIS Configuration tab seen above.
Figure 5.18 AIS Target properties in main view
5.5.3
Gimbal functions
The gimbal module provides functionality to control infrared camera assemblies and store still
images and video. Up to two optional FLIR IR cameras provided by Miros are part of integrated
gimbal assemblies. When two gimbals are installed, the MMI lets the operator choose which
one to use.
The camera pointing target symbol indicates where the camera line-of-sight intersects the
ocean surface. This is used as an indication of where the cameras are pointing. It is possible to
move the camera pointing direction by clicking and dragging the pointing target. Wherever the
pointing target is dropped, in a projected view, the camera system will point to.
When used with two IR camera gimbals, the GUI lets the user select which gimbal to view and
control. Some available IR cameras supply both IR and low-light video. In this case the GUI is
capable of showing both video streams at the same time.
It is also possible to control the cameras via joysticks (JCU) provided by FLIR. Please refer to
the FLIR user manual on how to select camera outputs and IR palette colours. When two
Miros AS
Page 29 of 51
PR-003/DD/008, rev. 1
Miros OSD
gimbals are installed, the JCU does not follow the gimbal selection of the MMI. Instead, two
JCUs must be used, or the user must select gimbal on the JCU.
The video image can be turned into a floating view in order to make the image larger.
Underneath the video image are two buttons named “Record” and “Snapshot”. Clicking “Record”
starts and stops a video record process. Clicking “Snapshot” takes a snapshot of the current
camera image. Video and snapshot files are stored according to the MediaFolder setting in the
file gimbalsettings.ini. The default location is E:\Miros\gimbalmedia.
The computer which stores videos and snapshots is the same computer as handles the
incoming IR video from the IR camera gimbals. This is typically the same computer as runs the
Miros OSD display. In case you are using a more complex multi-computer setup, please contact
your local IT support to determine how to access stored videos and snapshots.
Figure 5.19 Camera pointing target symbol and the button which toggles its Main View layer.
Figure 5.20 Floating view of IR video from the gimbal module and FLIR camera.
Miros AS
Page 30 of 51
PR-003/DD/008, rev. 1
Miros OSD
5.5.4
Radar module
The radar module provides basic functionality to help debug problems that may occur and to
record unprocessed radar images. The Record button is used to toggle recording of raw radar
data. The default location for saved files is E:\Miros\HistFiles\DF047\event on the computer
which runs the Miros OSD system. This is typically the same computer as runs the GUI. In case
you are on a complex multi-computer OSD system, please consult with local IT support to
determine which computer stores the files.
Figure 5.21 Radar view.
5.5.5
Report Module
The report module provides functionality to write simple reports that include a summary and oil
spill data with contextual information about the environment and surrounding vessels. From the
report floating view the operator can manually edit text and save the report in rich text format
(.rtf). Oil spill, BSI, conning status, weather etc. are automatically added. An rtf editor is needed
to edit the report afterwards. In the report module the user chooses where to save the file. The
file is saved on the computer which runs the GUI.
Miros AS
Page 31 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.22 Report view.
5.5.6
Alarm module
The system can be delivered with an additional visible and audible alarm module. The module
can be configured to run a wav file from the computer/KVM system if an oil spill larger than a
predefined threshold is detected. There will also be a visible alert on the operator display where
the module is installed.
Figure 5.23
5.5.7
Alarm module.
About view
While not technically a module, the about view includes information on how to contact Miros
when something in a commissioned system is not as expected. The about view includes Miros
contact email, project number for traceability and site name.
Miros AS
Page 32 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 5.24 About view.
Miros AS
Page 33 of 51
PR-003/DD/008, rev. 1
Miros OSD
6
Using OSD
This chapter contains information about how system features are used and how certain basic
operations are performed.
6.1
System start-up
To start-up an OSD system, proceed as follows:
·
·
·
·
·
Make sure the OSD X-band marine radar is turned on
Turn on the EM-129 integrated video digitizer
Turn on the OSD display and computer
Wait for MirAdm04 to start and perform the start-up sequence
Wait for MirPresBridge (GUI program) to start up
Note: It can take up to 20 minutes before data appears on the display under normal
operating conditions with sufficient wind speeds (2 m/s and above) at the OSD measure
area.
If MirAdm04 does not start automatically, follow the instructions given under 6.2: “Manually
triggering the start-up sequence”.
6.2
Manually triggering the start-up sequence
When Miros OSD is commissioned, the system is configured to enter the OSD software start-up
sequence automatically. The automatic triggering of this sequence might fail or the sequence
might fail and need to be started manually.
MirAdm04 is the software module that manages all OSD radar data processing. MirAdm04
starts a set of modules, monitors their status and stops them. Launching MirAdm04 triggers the
start-up sequence. There is a shortcut to the MirAdm04 application on the Windows desktop
and in the Windows Start menu under a folder labelled “Miros OSD”. Click the MirAdm04
shortcut if it is not started by the system on boot.
In addition, the GUI MirPresBridge may have to be started from the Windows Start menu, and
the MirSip41 video module from the Services menu (see above).
6.3
Locating a spill
The systems primary goal is to help the operator locate where there is oil on water and provide
information to plan and carry out a recovery operation. Locating an oil spill can be done either
by evaluating an oil track or by inspecting and evaluating the averaged BSI image. Either way, it
is required that the operator is familiar with interpreting averaged BSI images. There is a certain
probability of false detections and the operator needs to know how to distinguish false from true
detections. Interpretation of BSI images is described in chapter 7.
Detected oil is shown in a binary presentation. When an automatic detection has been matched
with a good oil signature in the averaged BSI, then oil has been located with a high level of
confidence.
While detections indicate the current position of a potential spill, oil drift indicates where the spill
is likely to be headed, and the oil trace indicates where the oil has been. Estimated near-future
oil drift and past positions, as indicated in the trace, may differ due to reasons such as changing
tide, surface currents or wind.
6.4
Data storage
Miros OSD stores data in three data buffers:
Miros AS
Page 34 of 51
PR-003/DD/008, rev. 1
Miros OSD
·
·
·
Real time buffer
Time lapse buffer
Video and Snapshot dump buffer
The real time buffer is where un-processed real time data is stored. Un-processed real time data
can be post-processed and used to analyse unexpected behaviour/phenomena and to illustrate
the movement of an oil slick that is being tracked after an event has taken place. Storing data to
the real time buffer is user initiated by pressing the “Record” button in the radar view (see
chapter 5.5.4). Pressing “Record” again will stop recording. The real time buffer is configured to
hold 24 hours of real time data by default. When the buffer is full, data needs to be cleared
before new data can be recorded.
The time lapse data contains information snapshots taken at a given time interval, e.g. every 15
minutes over a given period. The time laps buffer mainly stores processed data. Information
stored in this buffer is intended for analysis of past events that might be used to develop best
practice routines or monitor that established routines are followed. Data storage in the time
lapse buffer is automatic and needs no operator intervention. By default data is stored every 15
minutes and is kept for 8 weeks. Data older than 8 weeks is then discarded when newer data is
stored.
The screen dump buffer is where all user-initiated screen dumps are stored. Video snapshots
and recordings are stored according to chapter 5.5.3.
6.5
Third party data access
The Miros OSD data processing computer uses MS Windows built in FTP server for remote
data access. Miros OSD systems are typically delivered on computers where the Windows FTP
server is installed, but disabled, and configured for login with the default system user that has
the username/password combination miros/miros. When enabled data is available on the root
path at the ftp login prompt.
In order to enable third party data access the FTP server has to be enabled. Depending on
security requirements for the network the Miros OSD computer is installed on, it might be
required to configure new users and passwords for the FTP server. For information about how
to enable and configure the Windows FTP server, please refer to the Windows documentation.
Please contact Miros support if you need additional help with accessing data from the Miros
OSD system.
6.6
Check radar interface status
If the radar is not functioning as expected by the interface unit, the system operation will be
affected. When the system is not working as expected the radar interface status needs to be
verified. Open (default) IP 192.168.1.2 in a web browser (Firefox, Internet Explorer etc.). If
installed, this will show the status of the Miros EM-129 radar digitiser interface unit.
There are eight status light indicators that each indicate three status levels. Green indicates
normal operation. Yellow indicates that something may be about to go wrong. Red indicates that
there is an error.
If any of the status indicators are red, note what the light is indicator for and report the fault to
your local Miros service representative.
Miros AS
Page 35 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 6.6: Radar status information
6.7
System restart
During the systems life span there might be situations that warrant a system restart to resolve
an undeterminable problem. There are multiple ways to perform a system restart and these are
described here.
6.7.1
·
·
·
6.7.2
·
·
6.7.3
·
6.7.4
·
·
·
Miros AS
OSD software restart
Shut down the OSD software by terminating MirAdm04 from its menu File → Exit.
Start MirAdm04 either from the desktop shortcut or from the Miros shortcut located in
the Miros folder in the Windows start menu.
Watch MirAdm04 perform the start-up sequence.
Video system restart
The video interface is controlled by a Windows service named MirSip41.
Windows start menu → type “Computer Management” → start the program → Leftclick “Services and Applications” → double-click “Services” → Select “MirSip41” →
right-click and choose “Restart”.
Graphical user interface restart
The MMI GUI is named “MirPresBridge”. The program may be closed and then
restarted from the Windows start menu without any effect on the underlying OSD
processing.
Computer software restart
Shut down the OSD software by terminating MirAdm04 with File → Exit.
Select computer “Restart” from the Windows start menu.
Wait for the computer to restart and watch MirAdm04 perform the start-up sequence.
Page 36 of 51
PR-003/DD/008, rev. 1
Miros OSD
6.7.5
Hardware restart
Note: Only perform a hardware reset if computer software restart fails.
·
·
6.7.6
Press the computer “Reset” button.
Wait for the computer to restart and watch MirAdm04 perform the start-up sequence.
Computer power cycle
If the system does not respond normally to a computer hardware reset, power cycling the
hardware might help:
·
·
·
·
Miros AS
Push the computer “Power” button and hold it until the computer shuts down.
Wait for a minimum of 30 seconds and push the “Power” button again until the
computer starts.
If needed, allow Windows to repair itself. Contact your local IT support first if this
operation fails.
Wait for the computer to start and watch MirAdm04 starting all the OSD software
modules.
Page 37 of 51
PR-003/DD/008, rev. 1
Miros OSD
7
Interpreting averaged BSI images and detections
To correctly interpret information in BSI images, basic knowledge of the operating principles is
required. Furthermore, ability to identify common sources of false detection is necessary. This
section will attempt to give an overview of system shortcomings and known situations that might
lead to false detections.
7.1
The back scatter intensity (BSI) image with Oil
The averaged BSI image is a grey scale image with 256 levels. Each pixel and its grey level
indicate the amount of energy backscattered from a small region of the sea surface. High levels
correspond to a high amount of backscattered energy and low levels correspond to a low
amount. In MirPresBridge the BSI images are currently presented using grades of cyan to
represent the grey scale. Hence, high levels of backscattered energy are represented with
bright cyan while areas with low levels are represented with dark cyan (black if the level is 0). As
described in section 1, the phenomenon that gives backscatter is scattering from wind
generated surface ripples. In areas with oil, these surface ripples disappear, and hence areas
with oil will occur as dark patches in the BSI images, see the examples in figure 7.1.
The BSI images in figure 7.1 A and figure 7.1 B show an oil slick detected from two different
vessels at the same time. The slick is crude oil, and has been floating freely for about 2.5 hours.
The wind conditions are marginal and hence the slick does not have ideal contrast. Notice that
contrast close to the vessel in Figure 7.1 B is quite good, but the contrast quickly degrades at
further distances. This is normal under conditions with marginal wind. In Figure 7.1 A there isn’t
any part of the slick with good contrast because the entire slick is viewed from a large distance.
The position of both vessels is indicated in the figures with arrows.
West of the vessel in figure 7.1 C there are two spills of 4.5m3 crude oil each, merging together.
They have been floating freely for about ten hours. A narrow bright stripe is seen going through
the spill. This is the trail the vessel left when it moved through the spill. Wind conditions are
quite good. Observe that contrast between oil and water is reduced further away from the
vessel. Because the wind conditions are favourable the reduction in contrast is not as severe as
it is in figure 7.1 B where wind is not as strong. Notice also the different levels of cyan inside the
oil slick. This lack of dampening uniformity has repeatedly been observed in spills that have
been floating freely for longer time periods but no correlation with oil thickness has been
documented. Northeast of the vessel in figure 7.1 C is a small spill. This is the same spill that is
illustrated in figure7.2 but around eight hours later.
The BSI image in figure 7.1 D illustrates remnants from a release of oil used in an oil boom test.
Here you should notice how the contrast between oil and water is good at a long range from the
vessel and contrast reduction is not significant over the entire range of the radar. This is the
case because the radar look direction to the oil is up wind. Up wind is the most favourable look
direction for oil spill detection with x-band radar.
Miros AS
Page 38 of 51
PR-003/DD/008, rev. 1
Miros OSD
A
B
C
D
Figure 7.1: Examples of back scatter intensity images. Oil is marked with red circles.
The BSI image in figure 7.2 shows a release of heavy fuel oil. The release is still on going and
the contrast is good. Observe that the upper part of the image has an area much brighter than
the rest of the image. This is caused by the fact that the Bragg scatter is largest in the upwind
direction. Hence the system has the largest operating range in the upwind-direction. The
operating range will be more dependent on the wind direction under marginal wind conditions
than under good wind conditions.
Miros AS
Page 39 of 51
PR-003/DD/008, rev. 1
Miros OSD
Figure 7.2: A release of heavy fuel oil
7.1.1
Situations where the information in a BSI image can be misleading
In some situations, the BSI image can have dark areas that might look like oil, but are not. Such
situations can arise from other phenomena that prevent the creation of surface capillary waves
or objects blocking the radar’s view of the sea surface. During testing of the system the
following situations have given ambiguous BSI images:
·
·
·
·
Wake from vessels (figure 7.3). Especially when a vessel turns and accelerates. Wake
from large vessels can be visible for up to 45 minutes after it was created.
Heavy seas, long swell, surface effects created by currents and algae may cause oillike features in BSI images.
Radar shadows caused by objects in the radar coverage area (figure 7.4). The
shadows will be larger for low antenna mounting heights.
Especially during low wind conditions, calm areas can create difficulties.
A vessel turns and accelerates
The wake is still visible after twelve minutes
Figure 7.3: Vessel wake
Miros AS
Page 40 of 51
PR-003/DD/008, rev. 1
Miros OSD
BSI image from ship closest to ship causing
shadow
BSI image from ship further away
Figure 7.4: Radar shadow
Situations like the ones shown in figure 7.3 and figure 7.4 are most often quite easy for an
operator to distinguish from real oil. For situations with wake, most often the vessel creating it
will also be visible in the BSI image. The contrast it gives will also gradually reduce with time.
Ships appear as bright spots.
Shadows are in most cases easy to recognize, since they appear as dark, straight lines that
radiate out from the centre of the averaged BSI image. The object causing a shadow will
typically also be visible as a bright spot in the end of the shadow closest to the vessel carrying
the radar. Be aware of situations where shadows are mixed with other phenomena, in which
case they can become harder to recognize.
Enabling the AIS layer and PAST POSN will make it easier to understand which BSI features
may be caused by moving vessels.
Miros AS
Page 41 of 51
PR-003/DD/008, rev. 1
Miros OSD
8
System maintenance
8.1
OSD system
The OSD system requires little maintenance. The only regular activity recommended is visual
inspection and cleaning of external surfaces.
Inspect the following components once a month, look for damage and clean using a soft, lint
free cloth and a mild detergent:
·
·
·
·
·
·
·
·
·
8.2
The OSD system computer.
The display, keyboard and pointing device.
The EM-129 integrated video digitizer.
The OSD radar antenna.
The EM-124 buffer amplifier (if present).
The SM-134 interface unit (if present).
The SM-151 video digitizer (if present).
The SM-098 wind sensor (if present).
FLIR IR cameras (if present).
The radar
For complete maintenance of the OSD radar please see the manufacturer’s documentation. An
authorized radar manufacturer representative must carry out all service and maintenance on the
radar system.
Because the OSD system requires higher radar performance than is necessary for navigation
purposes, the radar magnetron should be replaced at shorter intervals than recommended by
the radar manufacturer. This is especially important in areas with generally low wind speeds.
For this reason, radars used with OSD systems should have the magnetron replaced after a
transmit time of 4500 hours. If used continuously this corresponds to about twice a year.
Miros AS
Page 42 of 51
PR-003/DD/008, rev. 1
Miros OSD
9
Technical data
9.1
Radar
It is recommended that the X-band radar used in an OSD system complies with the following
characteristics to be suited as a signal source. The OSD system will NOT work if used with
long pulse radar. Wave and current measurements will only work with short pulse radar.
OSD X-band radar requirements
Antenna beam width:
1.3 degrees or less.
Antenna rotation speed:
20 - 60 RPM.
15 - 90 metres above mean sea level.
Antenna mounting height:
Pulse length:
Pulse repetition frequency:
Output power:
Radar signals:
Table 9.1:
9.2
Short pulse 50 - 80 ns. (Oil detection and drift.)
Medium pulse 250-300 ns. (Only oil detection.)
1000 Hz or higher. Depends on antenna RPM.
10 kW or more.
Raw video.
Sync.
Heading Marker.
Azimuth.
OSD X-band radar requirements
OSD performance data
The graphs presented here are based on certain assumptions and represent a best-case
scenario. System range and resolution are complex parameters that depend on several
variables. Graphs are only good at illustrating behaviour of a system property as a function of up
to 3 variables. System performance is affected by other variables than the following graphs
include and all will reduce performance when deviating from the assumed values.
The following performance graphs are based on the following assumptions:
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
Miros AS
Beam width is 0.9° (8 ft. antenna)
Antenna gain is 32 dB
Antenna speed is 24 RPM
Transmitted power is 25 kW
Receiver noise factor is 6 dB
System loss factor is 10 dB
PRF is 3000 Hz
Observation direction is up-wind
Short pulse is 70 ns
Medium pulse is 300 ns
Sampling rate is 31.25 MHz for short pulse
Sampling rate is 15.63 MHz for medium pulse
Azimuth sampling resolution is 0.6°
Polarization is horizontal
Antenna height is 25 m
Magnetron is in tip-top condition
Surface currents are consistent across the scanned area
Signal to noise ratio for oil detection is 20 dB
Page 43 of 51
PR-003/DD/008, rev. 1
Miros OSD
9.2.1
System range
Short Pulse
Medium Pulse
Operating range [m]
14000
12000
10000
8000
6000
4000
2000
0
0
2
4
6
8
10
12
14
16
Wind [m/s]
Figure 9.1: System range.
Figure 9.1 illustrates system range for automatic detection as a function of wind speed and
pulse mode. System range is very dependent on operating conditions. This is a best-case
illustration and should be used as a guideline only. Actual system range will be less than the
given graphs by an amount depending on your operating conditions.
9.2.2
System resolution
Short Pulse
Medium Pulse
Digitizer
Area [km2]
1
0,1
0,01
0,001
0,0001
0
2000
4000
6000
8000
Range [m]
10000
12000
14000
Figure 9.2: System resolution.
Figure 9.2 illustrates system resolution as a function of range. System resolution determines the
smallest detectable spill size under certain conditions. When a spill is less than the given
system resolution, then automatic detection will not function as expected. However, it might be
possible to find oil that is smaller than the given resolution by manually inspection.
Miros AS
Page 44 of 51
PR-003/DD/008, rev. 1
Miros OSD
System resolution is mainly limited by radar pulse characteristics or signal sampling properties.
The green portion of the graph in figure 9.2 indicates where the system resolution is determined
by radar video digitizer properties.
9.3
Software
OSD software
Operating system:
Application:
Table 9.2:
Miros AS
Windows 7 or Windows Server 2008 R2.
OSD System Software version 5.4
OSD software.
Page 45 of 51
PR-003/DD/008, rev. 1
Miros OSD
10 Troubleshooting
10.1 Troubleshooting action list
This chapter lists the most common reasons for trouble with the OSD system, and suggest an
action in an attempt to solve the problem. There may also be other reasons why the OSD
system behaves in a strange way, not listed here.
1. Undefined (“//”) data in the GUI
Possible reason
Wind is not strong enough to create
capillary waves on the sea surface,
resulting in no radar backscatter.
Heavy rain shower.
Windows operating system failure.
Action
There is really not much to do except wait for the wind
speed to increase. Wind speeds of 2 m/s and above
are usually sufficient.
Wait until the rain shower ends or passes.
Restart the OSD system computer.
2. “Timeout” in the GUI
Possible reason
The OSD radar is turned off.
The radar magnetron is about to wear
out. Maximum recommended Tx time
for an OSD radar magnetron is 4500
hours.
Heavy rain shower.
One or more OSD software modules
have recorded one or several errors.
Action
Turn the radar on.
Replace the radar magnetron.
The OSD radar antenna needs
maintenance.
One or more OSD hardware
components are without power.
One or more OSD hardware
components are malfunctioning.
Clocks are not synchronized.
Arrange radar antenna maintenance with radar
supplier representative.
Make sure that all OSD hardware components have
sufficient power.
Contact the local Miros OSD system supplier for repair
or replacement of defect hardware.
Open the NOW files folder and check that all relevant
NOW files are updated by looking at the storage time
stamp. Compare these time stamps with the OSD
computer system time. Change computer system time
or time zone if necessary. Use Zulu time.
Restart the OSD system computer.
Windows operating system failure.
Wait until the rain shower stops or passes.
Open MirAdm04 and check if any software module has
a red cross in front of its name. If yes, double-click on
the software module name for further investigation.
3. Data in the GUI display that is obviously wrong
Possible reason
Action
There is not enough wind
Wait until wind speed is greater than 2 m/s.
There is too much wind
Wait until wind speed is less than 10-14 m/s.
There are vessels or other obstacles
Wait until the obstacle is no longer in view. Reposition
that cause problems in the algorithms.
vessel relative to wind and obstacles.
4. One or more red crosses in front of software modules in the MirAdm04
window.
Possible reason
NMEA-data timeout. Missing external
data from a GPS, gyro or wind sensor.
OSD radar data timeout.
Miros AS
Action
Double-click on the software module name in the
MirAdm04 window for further investigation.
Check the actual sensor including cabling and
connections for error, and correct if possible.
Check radar status.
Connect to the EM-129 using the Firefox web browser
and check status. Correct any errors if possible.
Page 46 of 51
PR-003/DD/008, rev. 1
Miros OSD
5. One or more red lights in the EM-129 status page.
Possible reason
Action
The OSD radar is turned off.
Turn the radar on.
Low power.
Restart EM-129 using the power button.
DSP failure.
Restart EM-129 using the power button.
Processing failure.
Restart EM-129 using the power button.
Wrong OSD radar sync PRF.
Check radar status.
Set to correct mode (Short Pulse 50 - 80 ns) if
incorrect.
Check cabling and connections.
Increase EM-129 Sync PRF Tolerance if needed.
Wrong OSD radar azimuth count.
Check cabling and connections.
Check the radar and order service if required.
Wrong OSD radar heading PRI.
Check cabling and connections.
Check the radar and order service if required.
Increase EM-129 Heading PRI Tolerance if needed.
Video signal error.
Check cabling, connections and impedance jumper
setting.
Adjust EM-129 video gain and video offset.
6. Error messages at the display or in log files.
Possible reason
Action
The display shows error messages
Try to isolate the error and solve the problem.
generated by the Windows operating
Restart the computer.
system.
OSD history data cannot be stored.
Click on the MirAdm04 System Information tab and
check that there is sufficient disk space available.
Delete old data if necessary.
7. Nothing at all at the display (black screen).
Possible reason
Action
The display is switched off.
Turn the display on.
Wrong display input channel used.
Switch to correct display input channel from the display
menu.
The display brightness is dimmed all
Increase brightness.
the way down.
The display is broken.
Replace the display.
Windows operating system failure.
Restart the OSD system computer.
Table 9.1:
OSD troubleshooting action list.
10.2 Advanced trouble shooting
Miros OSD generate log files that contain information about system status together with status
messages that may help isolate the cause of system errors.
Log files are found under the folder c:\Miros\”Site-name”\Log, where “Site-name” is the name or
number of your system site.
Miros AS
Page 47 of 51
PR-003/DD/008, rev. 1
Miros OSD
10.3 Support
If the troubleshooting action list or log files do not help to solve a problem then contact your
local Miros representative for assistance. In order for one of our engineers to be able to help,
please provide information outlined below together with a description of the problem you need
help with:
· Any error messages on the OSD computer display.
· Any OSD software modules with a red cross in front of its name in the MirAdm04 window.
· Any EM-129 web browser status lights with red colour.
· Any repair or maintenance work carried out recently on the OSD radar.
· Radar status.
· IR camera status (if present).
· Local wind condition (wind speed and direction).
· Local weather condition (rain, snow, temperature, humidity, pressure).
· Any other findings that may help the OSD system supplier in providing quick and correct
support.
Miros AS
Page 48 of 51
PR-003/DD/008, rev. 1
Miros OSD
11 Frequently asked questions
This chapter lists a collection of frequently asked questions (FAQ) related to installation and
operation of the OSD system, and the answers to them.
1. Why does OSD show two slashes (“//”) instead of real data?
The most common reason for the two slashes (undefined data) in the OSD data display
is because the wind is not strong enough to create capillary waves on the sea surface,
resulting in no radar backscatter. Wind speeds of 2 m/s and above are usually
sufficient.
Other reasons can be that the OSD radar operates in the wrong mode, there is a
foreign obstacle like a ship or island in the OSD measure area, or there is a heavy rain
shower passing the OSD measure area.
2. Why does OSD show “Timeout” instead of real data?
There are several reasons why OSD can display “Timeout” in the data display. Most
common is that the radar is turned off or is set to a pulse mode other than short or
medium pulse.
Other reasons can be:
· A foreign obstacle like a ship or island in the OSD measure area.
· The radar magnetron is about to wear out. Maximum recommended Tx time for
a OSD radar magnetron is 4500 hours.
· Heavy rain shower in the OSD measure area.
· One or more OSD software modules have recorded one or several errors.
· One or more OSD hardware components are missing power.
· One or more OSD hardware components are broken.
· Time mismatch between the data storage time and local computer time.
· The OSD radar antenna needs maintenance.
· Windows operating system failure.
3. What are the radar requirements for a OSD system?
The requirements for a OSD radar are:
· Antenna beam width:
1.3 degrees or less (6 feet or more antenna
length).
· Antenna rotation speed:
20 - 60 RPM.
· Antenna mounting height: 15 - 90 metres above mean sea level.
· Pulse length:
Short pulse 50 - 80 ns. (Oil detection and oil drift.)
Medium pulse 150 - 300 ns. (Oil detection only.)
· Pulse repetition frequency: 1000 Hz or higher. Depends on antenna RPM.
· Output power:
12 kW or more.
· Radar signals:
Raw video, Sync, Heading Marker and Azimuth.
4. What kind of radars can OSD use?
OSD can, in principle, use any X-band marine navigation radar. Please see above for
radar requirements. Also contact your local Miros representative for further details.
5. How often should the radar magnetron be replaced?
OSD requires higher radar performance than is necessary for pure navigation
purposes, so the radar magnetron should be replaced at shorter intervals than
recommended by the radar manufacturer. Miros recommends the radar magnetron to
be replaced after 4500 hours of transmit time. If used continuously this corresponds to
about twice a year.
Miros AS
Page 49 of 51
PR-003/DD/008, rev. 1
Miros OSD
6. What is the radar safety distance?
This depends on the radar brand and make. The standard dedicated OSD radars, the
Furuno FAR-2117 and FAR-2127 have safety distances of:
FAR-2117: 0.10 m to 100 W/m2 and 3.00 m to 10 W/m2.
FAR-2127: 0.40 m to 100 W/m2 and 8.60 m to 10 W/m2.
7. Can the radar be used with OSD and for navigation at the same time?
When Miros OSD is connected to the main navigation radar for data input, the system
will not in any way affect normal radar operation. The two systems can therefore be
used at the same time. However, because radar settings used by the navigation display
will affect the signal used by OSD, you need to ensure the radar settings used for
navigation are compatible with that required by OSD. Oftentimes, navigation operators
will set the radar to long pulse. This disables the OSD system.
8. Why must OSD use the radar in short or medium pulse modes?
Oil spill detection requires a certain image resolution in order to detect oil and oil drift
measurement requires an even higher resolution. The system is not designed to
operate with pulse modes that have a pulse length longer than 300 ns.
9. What kind of maintenance is required for the OSD system?
The OSD system is almost maintenance free. The only regular activity recommended is
visual inspection and cleaning of external surfaces using a soft, lint free cloth and a
mild detergent.
The radar magnetron should be replaced after 4500 hours of transmit time, which
corresponds to twice a year if used continuously.
Please consult the radar manufacturer or local dealer for additional radar maintenance.
10. Does OSD work in heavy rain?
X-band radars are sensitive to rain. During conditions with heavy rain showers
reduction in system functionality is expected.
11. Can OSD operate in all kinds of weather?
Wind speed of 2 m/s and above is required to generate ripples on the sea surface
necessary to create radar backscatter. There is an upper wind speed limit at 10-14 m/s.
At high wind speeds oil will naturally disperse into the water column and the
mechanisms under which oil is detected are no longer applicable. Oil detection is also
affected by rain and will not operate during heavy downpours. Fog will however not
affect operation.
12. What is the maximum range for my OSD system?
Please refer to chapter 9.2.1.
13. Can a third party computer access OSD data?
Yes, information indicating areas with detected oil and surface current is accessible via
FTP. For more information please refer to chapter 6.5.
15. How much space is required to store OSD data?
Unprocessed radar image files typically contain around 500kB of data. Assuming a 24
RPM radar, the real time buffer set to 24 hours will use 17.3 GB of the systems storage
capacity.
Each snapshot in the time lapse buffer contains information equivalent to around 1 MB.
Assuming a snapshot interval of 15 minutes, the buffer set to 4 weeks will use 2.7 GB
of the system storage capacity.
Miros AS
Page 50 of 51
PR-003/DD/008, rev. 1
Miros OSD
16. What do the external lights on the EM-129 integrated radar video digitizer
indicate?
The EM-129 integrated radar video digitizer has six external status lights. Their
meanings are:
· PWR: Green light when EM-129 power is on, no light when power is off.
· SYS: Green light when EM-129 firmware is up and running OK.
· LAN: Green light when LAN activities to/from the EM-129.
· SYNC: Yellow light when the EM-129 receives radar sync pulses.
· AZ: Yellow light when the EM-129 receives radar azimuth pulses.
· HM: Yellow light when the EM-129 receives radar heading marker pulses.
Note that LAN activities, and reception of radar SYNC- and AZ pulses may happen so
fast that these lights seem to illuminate continuously.
17. What do the lights in the EM-129 status page indicate?
When in the EM-129 web interface, click on any of the status lights with the left mouse
button and a help text window will appear with a detailed explanation for each of the
seven status lights.
Miros AS
Page 51 of 51
PR-003/DD/008, rev. 1