User's Manual
Table Of Contents
- GENERAL
- 1 About these Operating Instructions
- 2 Safety Precautions
- 3 NACOS Platinum System Description
- 4 Multi Function Display
- 5 NACOS Platinum Graphical User Interface
- QUICK START GUIDE
- MAIN APPLICATIONS
- RADAR
- 1 General Information
- 1.1 RADAR Safety
- 1.2 Current IHO Standards / Regulatory Approvals
- 1.3 System Structure and Installation
- 1.4 Basics / Evaluation of the RADAR Video
- 1.4.1 Basics of the Evaluation of RADAR Video in Platinum Series
- 1.4.2 Achievable RADAR Range
- 1.4.3 Distortions of the RADAR Video
- 1.4.4 Undesirable Echo Displays and Effects
- 1.4.5 RADAR Setting for the Display of Racon Codes
- 1.4.6 RADAR Settings for Target Enhancer Detection
- 1.4.7 RADAR Setting for SART Detection (X-Band only)
- 1.4.8 Transmission formats
- 1.5 Basic setting of the RADAR Video
- 1.6 RADAR Accuracy
- 2 The RADAR Keyboard
- 3 An Overview of the Screen
- 4 RADAR Application Area
- 5 RADAR Sidebar - Permanent Area
- 6 RADAR Sidebar - Non-Permanent Area
- 7 Target Handling
- 7.1 Overview
- 7.2 Manual Target Acquisition
- 7.3 Manual Target Selection
- 7.4 Automatic Target Acquisition
- 7.5 Settings for Dangerous Targets
- 7.6 Settings for Acquisition/Guard Zones
- 7.7 Target Fusion
- 7.8 Deletion and Loss of Targets
- 7.9 Critical Target
- 7.10 Target List
- 7.11 Target Display
- 7.12 Trial Manoeuvre
- 7.13 Reference Target Tracking
- 7.14 ARPA Training
- 7.15 ARPA Malfunctions
- 7.16 AIS Malfunctions
- 8 User Symbols
- 9 CHARTRADAR (optional)
- 9.1 Overview
- 9.2 Basic Adjustments
- 9.3 Selecting the Objects to be Displayed in the Vector Chart
- 9.3.1 Overview
- 9.3.2 Categories of Display Groups
- 9.3.3 Select a Category
- 9.3.4 Select the Primary Chart Information Set (PCIS)
- 9.3.5 Indication of Category in the Status Line
- 9.3.6 Defining the Symbol Presentation
- 9.3.7 Setting the Display of Text Labels
- 9.3.8 Switch on Additional Information
- 9.3.9 Switch on Conditionally Displayed Features
- 9.4 CHARTRADAR Application Area
- 9.5 Application Area Context Menu
- 9.6 Setting the Depths Lines to be Displayed in the Vector Chart
- 9.7 Setting the Own Ship’s Draft
- 9.8 Activating the Chart Monitoring
- 9.9 Setting the Look-Ahead Sector
- 9.10 Chart Maintenance
- 9.11 Main Differences between CHARTRADAR and Full ECDISPILOT
- 1 General Information
- VOYAGE PLANNING AND MONITORING
- 1 Voyage Planning
- 1.1 Generation of Routes
- 1.1.1 General Information about Pre-planned Tracks
- 1.1.2 Generation, Handling and Administration of the Routes
- 1.1.3 Route Display Settings
- 1.1.4 Route Editing - Graphical
- 1.1.5 Route Editing - Text Mode
- 1.1.6 Details of the Waypoint Data
- 1.1.7 Checking of Routes
- 1.1.8 Completing the Generation of the Route
- 1.1.9 Import / Export Routes
- 1.1 Generation of Routes
- 2 Chart and Route Monitoring
- 1 Voyage Planning
- CONNING
- SENSORS
- OPTIONAL APPLICATIONS
- MAINTENANCE
- 1 Performance Monitor
- 2 Data Maintenance of the Electronic Charts
- 2.1 General
- 2.2 Starting Chart Maintenance
- 2.3 Chart Maintenance Application Area
- 2.4 Update of Charts from Media
- 2.5 Messages during Chart Update
- 2.6 Display Charts which are on a Media or a MFD (workstation)
- 2.7 Maintenance of Charts on your MFD (workstation)
- 2.8 Display Expander
- 2.9 Backup/Restore of Map Data
- 3 Manual ENC Update Editor
- 4 Hardware Maintenance
- 5 SW Version and Updates
- ALARMS
- LISTS AND INDEXES
- DOCUMENT HISTORY
ED 3100 G 140 / 04 (2011-11)
Operating Instructions
V-2 Alarm Management
V Alarms.fm / 10.11.11
V-35
NACOS Platinum
2.2.8 Machinery Alarms
System Alarms
Besides the alerts delivered by the different applications running on the MFD or which are received from
the connected equipment, sub-systems and sensors, there is a list of alarms, warnings and indications
which can additionally be issued by the integrated system and displayed on any MFD.
These alerts are not connected to any application but to a system monitoring process running partly on
each MFD and on the Data Processing Unit.
The possible systems alarms are very much depending on the installed system structure and components
available on board and they are therefore part of the configuration database created for your ship.
The following list of alarms can therefore only be an example, covering the most probable alarms which
can be expected on small systems as shown in Figure I / 2 (an IMO RADAR Set with 2 RADARs) or larger
systems as shown in Figure I / 4 (a system for large ships).
Master DPU: Status of DPU 2
The DPU or DCU which is currently running as the master has detected a problem with the secondary
DPU.
Master DPU: Status of MFD (1 … N)
The DPU or DCU which is currently running as the master has detected a problem with one of the
installed MFDs. (1 … N) is indicating the range of identification number of the MFDs.
DPU 1: SIO card 1 Channel (n)
The DPU or DCU has detected a problem with one of the installed serial I/O cards.
(n) is indicating the channel number on the SIO.
DPU 1: SIO card 2 Channel (n)
The DPU or DCU has detected a problem with one of the installed serial I/O cards.
(n) is indicating the channel number on the SIO.
DPU 1: SIO on CPU Board
The DPU or DCU has detected a problem with the on-board serial I/O channel.
Module 01C2C001 (SIO 2010) err
The serial I/O module with the identification 01C2C001 is reporting an internal error.
Note:
As soon as you add a Monitoring and Control System (MCS) as part of the NACOS Platinum, the number
of integrated and ship dependent monitoring and alarm functions will be increased significantly. In this
case refer also to the Commissioning Protocol which includes the complete list of alarms for the system
installed on your ship. This document should also be available in printed form in the ship's files.
The alarm priority of these alarms is generally defined by the system configuration which is only acces-
sible by the so called Integration Manager, an offline tool for the manufacturer's commissioning and
service organisation. The output of this tool is a database which is loaded into the system (the MFDs and
the DPUs) after the database has been adapted to the system structure and its interfaces.