Synapsis Service Tool

RAnschütz Raytheon Anschütz GmbH
mçëíÑ~ÅÜ=NNSS=
a=J=OQNMM=háÉä=
dÉêã~åó=
qÉä=HQVJQ=PNJPM=NVJM=
c~ñ=HQVJQ=PNJPM=NVJUQM=
bã~áä=ë~äÉë]ê~óâáÉäKÅçã=
ïïïKê~óíÜÉçåJ~åëÅÜìÉíòKÅçã
SYNAPSIS
SERVICE TOOL
4169.DOC000302 Edition: Feb 2012

Weitergabe sowie Vervielfältigung dieser Unterlage, Verwertung Copying of this document, and giving it to others and the use or
und Mitteilung ihres Inhaltes nicht gestattet, soweit nicht communication of the contents thereof, is forbidden without express
ausdrücklich zugestanden. Zuwiderhandlungen verpflichten zu authority. Offenders are liable to the payment of damages.
Schadenersatz.
Sin nuestra expresa autorización, queda terminantemente prohibida
Toute communication ou reproduction de ce document, toute la reproducción total o parcial de este documento, así como su uso
exploitation ou communication de son contenu sont interdites, sauf indebido y/o su exhibición o comunicación a terceros. De los
autorisation expresse. Tout manquement à cette règle est illicite et infractores se exigirá el correspondiente resarcimiento de daños y
expose son auteur au versement de dommages et intérêts. perjuicios.
________________________________________________________________________________________________________________
Edition: Feb 2012 II 4169.DOC000302

R
Raytheon Anschütz GmbH
SYNAPSIS SERVICE TOOL Germany
SAFETY NOTES
x Warning!
Take care during maintenance and repair work: avoid
touching live electrical connections. The applicable safety
regulations such as VDE, BGV A3, OSHA 1919 and other
appropriate safety standards must be observed.
x The installation and initial commissioning may only be

performed by trained and qualified personnel.
x Maintenance and repair work may only be performed by

trained and qualified personnel with knowledge of the
national safety regulations for this type of equipment.
x Risk of equipment damage!

Parts may only be replaced when the supply voltage is
switched off.
_________________________________________________________________________________________________________________
Edition: Feb 2012 III 4169.DOC00030

Intentionally left blank
________________________________________________________________________________________________________________
Edition: Feb 2012 IV 4169.DOC000302

R
GENERAL INFORMATION
The present manual has been drawn up as a description and reference book. It will to
help answer questions and to solve problems in the quickest possible manner.
Before operating the equipment read and follow the instructions in this manual.
For this purpose refer to the table of contents and read the corresponding chapters
thoroughly.
If you have any further questions, please contact us on the following address:
RAYTHEON ANSCHÜTZ GMBH Tel. 0431 / 3019 - 0

Zeyestr. 16 - 24 Fax 0431 / 3019 - 291
24106 Kiel
Germany
All rights reserved. No part of this manual may be copied, neither mechanically,
electronically, magnetically, manually nor otherwise, or distributed, forwarded or
stored in a data bank without written permission of RAYTHEON ANSCHÜTZ GMBH.
Copyright:
RAYTHEON ANSCHÜTZ GMBH

Zeyestr. 16 - 24
24106 Kiel
Germany
Since errors can hardly be avoided in the documentation in spite of all efforts, we
should appreciate any remark and suggestion.
Subject to alterations.
_________________________________________________________________________________________________________________
Edition: Feb 2012 V 4169.DOC00030

RECORD OF AMENDMENTS
Item No. Amendment. Date of Short Name Signature

No. Amendment Description
________________________________________________________________________________________________________________
Edition: Feb 2012 VI 4169.DOC000302

R
TABLE OF CONTENTS
1 SYNAPSIS SERVICE TOOL ............................................................................................. 1
1.1 General Information ........................................................................................................... 1
2 OPERATION ..................................................................................................................... 3
2.1 Explanation of Symbols, Software Buttons and Functions ................................................ 3

2.1.1 Display Navigation ............................................................................................................. 4
2.2 Start-up the SYNAPSIS Service Tool ................................................................................ 5
2.2.1 Welcome Page .................................................................................................................. 6
2.2.1.1 User Rights ........................................................................................................................ 7
2.2.1.2 Configuration ..................................................................................................................... 7
2.2.1.3 Feedback Symbols ............................................................................................................ 8
2.3 Configuration Editor Page .................................................................................................. 9
2.3.1 Configuration Structure .................................................................................................... 10
2.3.1.1 Ship Parameters .............................................................................................................. 10
2.3.1.2 Synapsis Bridge ............................................................................................................... 11
2.3.1.3 Devices ............................................................................................................................ 12
2.3.1.4 Alerts................................................................................................................................ 13
2.4 Change Log Page ............................................................................................................ 14
2.5 Error Log Page ................................................................................................................ 15
2.6 Software Page ................................................................................................................. 16
2.7 Interface Data Page ......................................................................................................... 17
2.8 Misc Page ........................................................................................................................ 18
3 CONFIGURATION EXAMPLE FOR AN INTEGRATED

NAVIGATION SYSTEM (INS) ......................................................................................... 19
3.1 SYNAPSIS Radar New Installation .................................................................................. 19

3.1.1 Configure the Ship Parameters ....................................................................................... 19
3.1.2 Configure the Synapsis Bridge ........................................................................................ 21
3.1.3 Configure the Devices ..................................................................................................... 23
3.1.4 Configure the device Integration ...................................................................................... 25
3.1.5 Configure the CCRS ........................................................................................................ 27
3.1.6 Configure Alert Settings ................................................................................................... 29
3.1.7 Save the configuration ..................................................................................................... 30
3.1.8 Finishing the Configuration Process ................................................................................ 32
3.1.9 Restart all Applications of the INS ................................................................................... 33
3.1.10 Radar Configuration ......................................................................................................... 33
_________________________________________________________________________________________________________________
Edition: Feb 2012 VII 4169.DOC00030

4 CONFIGURATION EXAMPLE FOR A STANDALONE
CONSOLE (RADAR, ECDIS, NAUTOCONNING, MFC) .................................................34
4.1 SYNAPSIS Radar New Installation...................................................................................34

4.1.1 Configure the Ship Parameters ........................................................................................34
4.1.2 Configure the Synapsis Bridge .........................................................................................36
4.1.3 Configure the Devices ......................................................................................................38
4.1.4 Configure the device Integration .......................................................................................40
4.1.5 Configure the CCRS .........................................................................................................42
4.1.6 Configure Alert Settings ....................................................................................................44
4.1.7 Save the configuration ......................................................................................................45
4.1.8 Finishing the Configuration Process .................................................................................47
4.1.9 Restart the in the Standalone Console .............................................................................48
4.1.10 Radar Configuration..........................................................................................................48
5 THE EGGSHELL ..............................................................................................................49
6 DISTURBED CONFIGURATION .....................................................................................51
7 TROUBLESHOOTING .....................................................................................................52
________________________________________________________________________________________________________________
Edition: Feb 2012 VIII 4169.DOC000302

R
TABLE OF FIGURES
Figure 2-1 Display information ....................................................................................................... 3

Figure 2-2 Display Navigation ....................................................................................................... 4
Figure 2-3 Eggshell - Utility Selections - ........................................................................................ 5
Figure 2-4 Welcome Page ............................................................................................................. 6
Figure 2-5 Welcome page with Feedback Symbol ........................................................................ 8
Figure 2-6 Configuration Editor ..................................................................................................... 9
Figure 2-7 Ship Parameters ........................................................................................................ 10
Figure 2-8 Synapsis Bridge ......................................................................................................... 11
Figure 2-9 Devices ...................................................................................................................... 12
Figure 2-10 Alerts .......................................................................................................................... 13
Figure 2-11 Change Log Page ...................................................................................................... 14
Figure 2-12 Error Log .................................................................................................................... 15
Figure 2-13 Software Page ............................................................................................................ 16
Figure 2-14 Interface Page ............................................................................................................ 17
Figure 2-15 Misc Page .................................................................................................................. 18
Figure 3-1 Configure the Ship Parameter .................................................................................... 20
Figure 3-2 Configure the Synapsis Bridge ................................................................................... 22
Figure 3-3 Configure the Devices ................................................................................................ 24
Figure 3-4 Configure the device Integration ................................................................................ 26
Figure 3-5 Configure the CCRS .................................................................................................. 28
Figure 3-6 Configure Alert Settings ............................................................................................. 29
Figure 3-7 Save the configuration ............................................................................................... 31
Figure 4-8 Exit Service Tool ........................................................................................................ 32
Figure 4-1 Configure the Ship Parameter .................................................................................... 35
Figure 4-2 Configure the Synapsis Bridge ................................................................................... 37
Figure 4-3 Configure the Devices ................................................................................................ 39
Figure 4-4 Configure the device Integration ................................................................................ 41
Figure 4-5 Configure the CCRS .................................................................................................. 43
Figure 4-6 Configure Alert Settings ............................................................................................. 44
Figure 4-7 Save the configuration ............................................................................................... 46
Figure 4-8 Exit Service Tool ........................................................................................................ 47
Figure 5-1 SYNAPSIS INS Eggshell ........................................................................................... 50
Figure 6-1 Disturbed Configuration ............................................................................................. 51
_________________________________________________________________________________________________________________
Edition: Feb 2012 IX 4169.DOC00030

Intentionally left blank
________________________________________________________________________________________________________________
Edition: Feb 2012 X 4169.DOC000302

R
LIST OF ABBREVIATIONS
Term Description
BGV Berufsgenossenschaftliche Vorschriften
BIP Bridge Integration Platform
CAM Central Alert Management
CCRS Consistent Common Reference System
CCRP Consistent Common Reference Point
CS Checksum
DGPS Differential Global Positioning System
DDU Data Distribution Unit
ECR Engine Control Room
ECDIS Electronic Chart Display and Information System
EUT Equipment Under Test
ENV Environment
FMEA Failure Mode and Effect Analysis
GPS Global Positioning System
HMI Human Machine Interface
IEC International Electro technical Commission
IMO International Maritime Organization
INS Integrated Navigation System
ISO International Organization for Standardization
MFC Multifunction Console
MFD Multifunction Display
MSC Marine Safety Committee
NDM Navigation Data Manager
NMEA National Marine Electronics Association
NMEA 0183 Standard protocol for data transfer
NCD Nauto Conning Display
NSC Navigation System Control
OPZ Operations Zentrale
PCB Printed Circuit Board
RAN Raytheon Anschütz
SC Status Converter
_________________________________________________________________________________________________________________
Edition: Feb 2012 XI 4169.DOC00030

Term Description
STBY Stand by
SOLAS Safety Of Life At Sea
UTC Universal Time Coordinated
VBW Dual Ground/Water Speed
VDE Verband der Elektrotechnik Elektronik Informationstechnik e. V.
________________________________________________________________________________________________________________
Edition: Feb 2012 XII 4169.DOC000302

R
1 SYNAPSIS Service Tool
Caution:
To apply this SYNAPSIS Service Tool is only allowed for well-trained Service
Personal.
1.1 General Information

The SYNAPSIS Service Tool is based on highly scalable and configurable service
oriented software architecture.
The SYNAPSIS Service Tool software is a composition of various services deployed

over;
x Standalone consoles only used for Radar or ECDIS or Nautoconning

x MFC with Radar-, ECDIS- or Nautoconning-Application
x Black Box version used as MFC or single applications
x All consoles (INS) of the bridge. Some of these services (e.g. device
integrations) may be installed once in the whole system, other services,
such as logging may run on each console, and further ones, like the
CCRS, may be executed only once throughout the system, although being
installed redundantly (on each console).
The configuration service is a service that is installed on each console redundantly,

while only a single instance will handle configuration request from other components
in the system at a time. All other instances have the rule of a configuration backup,
either for the system as a whole or for the hosting console if the network connection
fails.
The configuration of a SYNAPSIS Service Tool is hierarchically structured and has an

xml like appearance. Although the configuration needs not to be stored as xml - it
typically is. You might find a configuration in its xml format, but the configuration
should be edited via the service tool exclusively, as the system keeps track of revision
changes and checksums. Editing the configuration by hand is intended to break these
checks in order to prevent undesirable manipulation.
To understand the basic configuration access, you need to know, that the SYNAPSIS
Service Tool differentiates between two strategies of configuration access. Import and
Export are methods to read and write a configuration from/to the local file system (e.g.
a service notebook) while Load and Save are the corresponding actions to read or
write the configuration from/to a connected bridge system. In the last case, the bridge
system itself will synchronize and persisted the new configuration data.
_________________________________________________________________________________________________________________
Edition: Feb 2012 1 4169.DOC00030

SYNAPSIS SERVICE TOOL
Saving configuration changes via the service tool is transactional, that is either all of
your changes will be applied or none. Most changes to the configuration require you to
commit them, in order to prevent undesired changes. If you forget to commit a change,
the SYNAPSIS Service Tool will ask you how to proceed with your changes when you
change a configuration page.
A SYNAPSIS INS supports high grades of redundancy, i.e. redundant connection of

devices. For this reason SYNAPSIS differentiates between “Devices” and “Device
Integrations”. A “Device” is (in most cases) a physical sensor or a 3rd party system,
while a “Device Integration” should be understood as the connection/port to a
“Device”. In other words, a “Device Integration” is a service that integrates a device
into the SYNAPSIS INS. If you connect a new sensor to a SYNAPSIS INS, you will
have to configure the “Device” itself (provided data, deviances, mounting position,
etc.) and dependent on your connection topography one or more “Device Integrations”
(port, baud rate, etc.).
________________________________________________________________________________________________________________
4169.DOC00030 2 Editon: Feb 2012

R
2 Operation
2.1 Explanation of Symbols, Software Buttons and Functions
Using the trackball to place the Cursor.
Press the left button.
1x click for selecting, 2x click for executing.
The middle and right buttons have no function for the

SYNAPSIS Service Tool.
H1 H2 H3 H4
H5
Figure 2-1 Display information

_________________________________________________________________________________________________________________
Edition: Feb 2012 3 4169.DOC00030

Pos. Information
1 Service Tool selection buttons using a service tool selection side.
2 Service Tool Navigator display section. The design depends from the
selected service tool selection side (directory structure, information line,
select soft keys).
3 Detail view with setting options.
4 Selection tabs for changing the detail view.
5 Quick selection buttons.
2.1.1 Display Navigation

The Display handling and navigation is according to the WindowsTM typical operation
manner, for example see Figure 2-2.
HStep 1
HStep 3
HStep 2
Figure 2-2 Display Navigation
Step Information
1 Press on the (+) symbol to break down into the next subdirectory.
2 Select Service (Process) with a double click.
3 The detail view appears, again with a double click the detail view changes to
the Log File detail information.
________________________________________________________________________________________________________________
4169.DOC00030 4 Editon: Feb 2012

R
2.2 Start-up the SYNAPSIS Service Tool

The start-up for the SYNAPSIS Service Tool is found in the Eggshell. The Eggshell
design depends from the MFC configuration (see chapter 5).
Before you can start the Service Tool via the Eggshell all applications of this MFC has
to be closed by the EXIT function.
An USB keyboard has to be connected at the USB connector of the MFC.
The respective program has to be selected and started see Figure 2-3.
HStep 1
Figure 2-3 Eggshell - Utility Selections -
_________________________________________________________________________________________________________________
Edition: Feb 2012 5 4169.DOC00030

2.2.1 Welcome Page

On start-up the service tool will display the welcome page, which provides a login area
at its left side (see chapter 2.2.1.1).
After a successful login a load and save area at the right hand will become available.
According to the actual user rights and dependent on the availability of a connection to
a bridge system not all load and save operations may be enabled.
In details, the functionality to import a configuration is always available, while the load
functionality depends on the availability of a bridge system. The export is available as
soon as a configuration is loaded, while the save again requires the bridge system to
be connected.
H1
H2
H3
H4
H5
6
Figure 2-4 Welcome Page
________________________________________________________________________________________________________________
4169.DOC00030 6 Editon: Feb 2012

R
2.2.1.1 User Rights

There are three user rights with different access authorization possible:
Mariner User access
The Mariner user is allowed to:
x View and export error logs
x View the whole configuration
x Change logging behaviour and escalation times
Service User access
The Service user is allowed to use all capabilities of the service tool except some very
few capabilities to direct work on the configuration structure and the capability to set
start phases.
Developer User access
The Developer user is allowed to use all capabilities of the service tool.
2.2.1.2 Configuration
In this case there are two configurations possible.
The configuration for Standalone consoles or Black Box versions has to be done
completely from the service people (see chapter 4).
In association with an Integrated Bridge System (INS) it is important to load a

configuration from another console or system or direct from the project department
(see Figure 2-4).
Pos. Information
1 Import the configuration from the file system (e.g. project department).
_________________________________________________________________________________________________________________
Edition: Feb 2012 7 4169.DOC00030

Pos. Information
2 Load the configuration from a connected SYNAPSIS INS.
3 Import the last configuration saved by a service user.
4 Export the configuration to the file system for saving the last version.
5 Save the configuration to a connected SYNAPSIS INS means the total

system works with the same configuration.
6 Unload the actual configuration.
2.2.1.3 Feedback Symbols

Two feedback symbols indicates the configuration process status.
Feedback Symbol
Figure 2-5 Welcome page with Feedback Symbol
A uncomplicated configuration process finished with a green feedback

symbol.
A disturbed configuration finished with a red symbol. A Tool Tip with a

process failure information appears when the cursor is placed about the
symbol see chapter 6.
________________________________________________________________________________________________________________
4169.DOC00030 8 Editon: Feb 2012

R
2.3 Configuration Editor Page

After pressing the Service Tool selection button Configuration Editor the Configuration
Editor page appears.
On the left side of this page you will find the Configuration Structure, an expandable
tree structure, which shall be used to navigate through the configuration. Depending
on the selected item the right of the page will display details to the selected
configuration part. Respecting the user rights, some input fields may be disabled.
A red lined path name indicates a modification in this path.
Figure 2-6 Configuration Editor
_________________________________________________________________________________________________________________
Edition: Feb 2012 9 4169.DOC00030

2.3.1 Configuration Structure
2.3.1.1 Ship Parameters

The ShipParameters section contains all physical ship parameters.
The tabs are used to change the Configuration Editor properties for the
ShipParameters.
x General Tab for displaying or editing the ship information (vessel name, call
sign, MMSI, ship&cargo).
x Dimensions Tab for displaying or editing the ship dimensions, common

reference point (CRP) and centre of rotation.
x Performance Tab for displaying or editing ship speed, draft and backup
coefficients.
Figure 2-7 Ship Parameters
________________________________________________________________________________________________________________
4169.DOC00030 10 Editon: Feb 2012

R
2.3.1.2 Synapsis Bridge

The Synapsis Bridge section contains all the MFC consoles that have been installed
with bridge or standalone environment.
The tabs are used to configurator or to change the SYNAPSIS Bridge properties for
the SYNAPSIS Bridge or standalone consoles.
x System Consoles Tab for displaying or editing the MFCs which are installed
in the SYNAPSIS INS or used as standalone consoles. Here you can add a
new Console or delete a selected Console. In this case the colour of the
SynapsisBridge path name changes to RED as modification indicator. A new
MFC is pre-configured; in this case you have to check the integrated devices
and the applications rights for the new MFC.
x Integrated Device Tab for displaying or editing the integrated devices. In this
case the Service Tool provides a list of all integrated devices used in the
SYNAPSIS INS or standalone console.
x Hosted Services Tab displays the internal process controlled device servicing.
In this case no additional manually configurations are necessary.
Figure 2-8 Synapsis Bridge
_________________________________________________________________________________________________________________
Edition: Feb 2012 11 4169.DOC00030

2.3.1.3 Devices
The Device section contains a structured list of all configured devices and default
Devices which settings apply if the corresponding settings are omitted for the specific
device.
Figure 2-9 Devices
________________________________________________________________________________________________________________
4169.DOC00030 12 Editon: Feb 2012

R
2.3.1.4 Alerts
The Alerts section holds a structured list of all alerts that may be occur in the
SYNAPSIS INS or standalone console and a Default Alert which settings apply if the
corresponding settings are omitted for the specific alert.
Figure 2-10 Alerts
_________________________________________________________________________________________________________________
Edition: Feb 2012 13 4169.DOC00030

2.4 Change Log Page

The Change Log Page displays a revision history of the loaded/imported configuration.
The Revision numbering and the Date will be done automatically.
Figure 2-11 Change Log Page
________________________________________________________________________________________________________________
4169.DOC00030 14 Editon: Feb 2012

R
2.5 Error Log Page

The Error Log Page displays on the left side an expandable tree structure, which
displays all running logging services and their actual log file lists. After selecting a
specific log file, its content will be displayed on the right side of the page. The page
provides a button to update the data manually and another button to export the
displayed log file into the file system.
Figure 2-12 Error Log
_________________________________________________________________________________________________________________
Edition: Feb 2012 15 4169.DOC00030

2.6 Software Page

The Software Page shows the loaded software packages and their revisions of all
connected consoles. The page provides a button to update the data.
Figure 2-13 Software Page
________________________________________________________________________________________________________________
4169.DOC00030 16 Editon: Feb 2012

R
2.7 Interface Data Page

The Interface Data Page shows the data telegrams (Rx and Tx) in the SYNAPSIS INS
or standalone console.
After selecting the Filter settings button a popup window appears. On the left side of
this window you will find a list of all configured ports within the bridge system. Each
port allows you to select/deselect the input and output direction to be monitored. On
the right side of the page, messages of all selected ports/directions will be displayed.
Outgoing (Tx) messages represent data after any computation directly before they are
handed to the port. Incoming (Rx) messages represent data directly after their receipt
and before any computation. In this case it is possible to change the filter mode. To do
this you can edit a character (e.g. $* or $GP*) into the new filter edit line. After
pressing the OK button and the reset button all data telegrams with this character are
listed on the right side.
Figure 2-14 Interface Page
_________________________________________________________________________________________________________________
Edition: Feb 2012 17 4169.DOC00030

2.8 Misc Page

The Miscellaneous Page displays Meta data information from the SYNAPSIS INS or
standalone console. On the left side of this page you will find display options and tool
settings while the right side displays tool information, such as the loaded plug-in and
meta configuration file path.
Figure 2-15 Misc Page
________________________________________________________________________________________________________________
4169.DOC00030 18 Editon: Feb 2012

R
3 Configuration Example for an Integrated Navigation System (INS)

In the following chapters we explain a typical configuration for an Integrated
Navigation System (INS) equipped with multiple MFCs.
Precondition:
x You know the Password

x Login as SERVICE user
x Service On Screen Keyboard or Plug-in a USB Keyboard
x You know the ship specifics data (Common Reference Point CRP)
x USB Stick to export the configuration
3.1 SYNAPSIS Radar New Installation

Precondition:
The hardware installation was finished, switch on the console. The Eggshell appears.
3.1.1 Configure the Ship Parameters

Procedure: Configure General, Dimension and Performance (see Figure 4-1).
Step1. Select the On-Screen Keyboard.
Step2. Select Service Tool.
Step3. Login as Service user.
Step4. Select Import, import the empty configuration template

SYNAPSIS_template.xml.
Step5. Select Configuration Editor.
Step6. Select ShipParameter in the expandable tree structure.
Step7. .Edit the ShipParameter General and commit the allocations , Dimensions
and commit the allocations, Performance commit the allocations.
_________________________________________________________________________________________________________________
Edition: Feb 2012 19 4169.DOC00030

HStep 1
HStep 2
HStep 4
HStep 3 HStep 4
Step 5
HStep 7
HStep 6
Figure 3-1 Configure the Ship Parameter
________________________________________________________________________________________________________________
4169.DOC00030 20 Editon: Feb 2012

R
3.1.2 Configure the Synapsis Bridge

Procedure: Tell the system that it consists of N consoles hosting Y applications (see
Figure 4-2).
Step1. Select the Synapsis Bridge node in the Configuration Navigator.
Step2. Select System Consoles. (You should see an empty list of all configured
consoles and their functionalities).
Step3. Press the + console button to add a new console. (A new console should
have been added).
Step4. Select the new console item in the list with a double click. The console
configuration appears. Uncheck the undesired functionalities (ECDIS and
Conning). The Service functionality is pre-configured, this configuration should
be uncheck in special console constellations only. Select whether the operator
has a proper lookout from the console.
Step5. Select the User Interface tab. Configure the user interface and the display
interface.
Step6. Press the commit button (flashing yellow) to save the configuration.
Step7. Repeat procedure Step1 to Step6 for all N consoles of the INS.
_________________________________________________________________________________________________________________
Edition: Feb 2012 21 4169.DOC00030

Step 1
Step 3
Step 2
Step 4
Step 5
HStep 6
Figure 3-2 Configure the Synapsis Bridge
________________________________________________________________________________________________________________
4169.DOC00030 22 Editon: Feb 2012

R
3.1.3 Configure the Devices

Procedure: Tell the system which external devices exist (see Figure 4-3).
Step1. Select the Devices node in the Configuration Navigator.
Step2. Press x device button to add physical devices that shall be connected to
the console. A dialog window should have opened. Press on the spinner for
open the device type list. Select the device type and press the Ok button. The
configuration page appears.
Step3. Edit the device parameters General, Device Data, NMEA Interface, CAN
Interface. General is normally used for the mounting position of the device.
Device Data no configuration is necessary. NMEA Interface, no configuration is
necessary, for specifying the received or sent NMEA telegram press the +
button and specify the talker and /or the sentence. CAN Interface, no
configuration is necessary.
_________________________________________________________________________________________________________________
Edition: Feb 2012 23 4169.DOC00030

HStep 1
HStep 2
HStep 3
HStep 4
Figure 3-3 Configure the Devices
________________________________________________________________________________________________________________
4169.DOC00030 24 Editon: Feb 2012

R
3.1.4 Configure the device Integration

Procedure: Tell the system how to connect/integrate the external devices (see Figure
4-4).
Step2. Select Integrated Devices tab. (You should see an empty list of all
configured device integrations).
Step3. Press the + integration button to add a new device integration. (A dialog
window appears).
Step4. Select the console and the device you want to connect to this console (for
example MFC2 and AIS1).
Step5. Select the interface type (Serial/Ethernet) and apply the required interface
settings. The settings for start-up, role arbitration, device(s), and direction are
pre-set to standard settings. Press the commit button before leaving the page.
Step6. For integrating another device press the System button and repeat the
procedure Step3 to Step5.
_________________________________________________________________________________________________________________
Edition: Feb 2012 25 4169.DOC00030

HStep 1 HStep 2
HStep 3 Step 4
Step 5
HStep 6 HStep 7
HStep 3 to Step 5
Figure 3-4 Configure the device Integration
________________________________________________________________________________________________________________
4169.DOC00030 26 Editon: Feb 2012

R
3.1.5 Configure the CCRS

Procedure: Tell the system how to select/degrade sensor data (see Figure 4-5).
Step1. Select the Synapsis Bridge / General / Application / CCRS path in the
Configuration Navigator.
If your previous configurations resulted in relevant changes to the CCRS data

selection table, the commit button will be enabled from the start.
If your console integrates data redundantly (e.g. two position sources), you may
change priorities or exclude data sources on this page manually. Normally the
recommended way is to stay with the defaults as the CCRS will re-sort device
priorities in automatic mode anyway and the applications (Radar, ECDIS,
Conning) allow selection in manual mode.
Step2. If you want to change the CCRS defaults, double click on the data item
line of interest. A dialog window appears. Following task are possible, check in
or check out the sensor used for the data item and the selection mode.
_________________________________________________________________________________________________________________
Edition: Feb 2012 27 4169.DOC00030

HStep 1
Step 2
Step 3
Figure 3-5 Configure the CCRS
________________________________________________________________________________________________________________
4169.DOC00030 28 Editon: Feb 2012

R
3.1.6 Configure Alert Settings

Procedure: You may but you do not need to customize alert settings (see Figure 4-6).
Step1. Select the Alert node in the Configuration Navigator. It is recommended

to omit this step.
Step2. Double click on the desired alert item in the alert list. A dialog window
appears. Change the timeouts (alarm escalation timeout and mute duration).
Press the commit button before leaving the page.
HStep 1
HStep 2
Figure 3-6 Configure Alert Settings
_________________________________________________________________________________________________________________
Edition: Feb 2012 29 4169.DOC00030

3.1.7 Save the configuration

Procedure: Save the configuration (see Figure 4-7)
Step1. Select the Welcome button.
Step2. Press the Save button to store the configuration or to store the changes
right into the Integrated Navigation System (The INS itself will take care to
distribute and synchronize the configuration over all consoles).
Step3. Press the Export button to store the configuration or to store the changes
into an external file system such a USB stick.
Step4. After Step2 or Step3 was selected a popup window appears. In this case
the user can be commentate the new configuration in a short helpful way. These
comment appears on the Change Log page labelled with a new Revision number
and a time stamp.
________________________________________________________________________________________________________________
4169.DOC00030 30 Editon: Feb 2012

R
HStep 1
HStep 3
HStep 2
HStep 4
Figure 3-7 Save the configuration
_________________________________________________________________________________________________________________
Edition: Feb 2012 31 4169.DOC00030

3.1.8 Finishing the Configuration Process

After doing and saving the new configuration close the ServiceTool. For finishing the
configuration process you have to select the Restart BIP in the Utility Selections.
Procedure: Finishing the Configuration Process (see Figure 4-8).
Step1. Exit the ServiceTool.
Step2. Select Restart BIP.
HStep 1
HStep 1
HStep 2
Figure 3-8 Exit Service Tool
________________________________________________________________________________________________________________
4169.DOC00030 32 Editon: Feb 2012

R
3.1.9 Restart all Applications of the INS

After any configuration modifications took place, all applications in the INS have to be
restarted to apply the changes.
Step1. Exit; RADAR, ECDIS, NAUTOCONNING.
Step3. Select the MFC button for loading up the applications.
3.1.10 Radar Configuration

Every RADAR application must be configure with the RADAR Configuration Tool for
itself.
See SYNAPSIS Radar Service and Installation Manual Doc. No. 4166DOC020302
chapter 3.2..
_________________________________________________________________________________________________________________
Edition: Feb 2012 33 4169.DOC00030

4 Configuration Example for a Standalone Console (RADAR, ECDIS,

Nautoconning, MFC)
In the following chapters we explain a typical configuration for a standalone console
(or black box version) equipped with a RADAR application.
Precondition:
x You know the Password

x Login as SERVICE user
x Service On Screen Keyboard or Plug-in a USB Keyboard
x You know the ship specifics data (Common Reference Point CRP)
x For the sensor configuration see wiring diagram 950-014.HP025 (placed in the
Radar Service Manual)
x USB Stick to export the configuration
4.1 SYNAPSIS Radar New Installation

Precondition:
The hardware installation was finished, switch on the console. The Eggshell appears.
4.1.1 Configure the Ship Parameters

Procedure: Configure General, Dimension and Performance (see Figure 4-1).
Step1. Select the On-Screen Keyboard.
Step2. Select Service Tool.
Step3. Login as Service user.
Step4. Select Import, import the empty configuration template

SYNAPSIS_template.xml.
Step5. Select Configuration Editor.
Step6. Select ShipParameter in the expandable tree structure.
Step7. .Edit the ShipParameter General and commit the allocations , Dimensions
and commit the allocations, Performance commit the allocations.
________________________________________________________________________________________________________________
4169.DOC00030 34 Editon: Feb 2012

R
Step 1
HStep 2
HStep 4
HStep 3 HStep 4
HStep 5
HStep 7
HStep 6
Figure 4-1 Configure the Ship Parameter
_________________________________________________________________________________________________________________
Edition: Feb 2012 35 4169.DOC00030

4.1.2 Configure the Synapsis Bridge

Procedure: Tell the system that it consists of a single console hosting a radar application
(see Figure 4-2).
Step2. Select System Consoles (You should see an empty list of all configured
consoles and their functionalities).
Step3. Press the + console button to add a new console (A new console should
have been added).
Step4. Select the new console item in the list with a double click. The console
configuration appears. Uncheck the undesired functionalities (ECDIS and
Conning). The Service functionality is pre-configured, this configuration should
be uncheck in special console constellations only. Select whether the operator
has a proper lookout from the console.
Step5. Select the User Interface tab. Configure the user interface and the display
interface.
________________________________________________________________________________________________________________
4169.DOC00030 36 Editon: Feb 2012

R
HStep 1
HStep 3
HStep 2
HStep 4
HStep 5
Step 6
Figure 4-2 Configure the Synapsis Bridge
_________________________________________________________________________________________________________________
Edition: Feb 2012 37 4169.DOC00030

4.1.3 Configure the Devices

Procedure: Tell the system which external devices exist (see Figure 4-3).
Step1. Select the Devices node in the Configuration Navigator.
Step2. Press x device button to add physical devices that shall be connected to
the console. A dialog window should have opened. Press on the spinner for
open the device type list. Select the device type and press the Ok button. The
configuration page appears.
Step3. Edit the device parameters General, Device Data, NMEA Interface, CAN
Interface. General is normally used for the mounting position of the device.
Device Data no configuration is necessary. NMEA Interface, no configuration is
necessary, for specifying the received or sent NMEA telegram press the +
button and specify the talker and /or the sentence. CAN Interface, no
configuration is necessary.
________________________________________________________________________________________________________________
4169.DOC00030 38 Editon: Feb 2012

R
HStep 1
HStep 2
HStep 3
HStep 4
Figure 4-3 Configure the Devices
_________________________________________________________________________________________________________________
Edition: Feb 2012 39 4169.DOC00030

4.1.4 Configure the device Integration

Procedure: Tell the system how to connect/integrate the external devices (see Figure
4-4).
Step2. Select Integrated Devices tab. (You should see an empty list of all
configured consoles and their functionalities).
Step3. Press the + integration button to add a new device integration. (A dialog
window appears).
Step4. Select the device you want to connect to this console (for example AIS1).
Step5. Select the interface type (Serial/Ethernet) and apply the required interface
settings. The settings for start-up, role arbitration, device(s), and direction are
pre-set to standard settings. Press the commit button before leaving the page.
Step6. For selecting another device press the System button and repeat the
procedure Step3 to Step5.
________________________________________________________________________________________________________________
4169.DOC00030 40 Editon: Feb 2012

R
HStep 1 HStep 2
HStep 3 HStep 4
HStep 5
HStep 6 HStep 7
HStep 3 to Step 5
Figure 4-4 Configure the device Integration
_________________________________________________________________________________________________________________
Edition: Feb 2012 41 4169.DOC00030

4.1.5 Configure the CCRS

Procedure: Tell the system how to select/degrade sensor data (see Figure 4-5).
Step1. Select the Synapsis Bridge / General / Application / CCRS path in the
Configuration Navigator.
If your previous configurations resulted in relevant changes to the CCRS data

selection table, the commit button will be enabled from the start.
If your console integrates data redundantly (e.g. two position sources), you may
change priorities or exclude data sources on this page manually. Normally the
recommended way is to stay with the defaults as the CCRS will re-sort device
priorities in automatic mode anyway and the applications (Radar, ECDIS,
Conning) allow selection in manual mode.
Step2. If you want to change the CCRS defaults, double click on the data item
line of interest. A dialog window appears. Following task are possible, check in
or check out the sensor used for the data item and the selection mode.
________________________________________________________________________________________________________________
4169.DOC00030 42 Editon: Feb 2012

R
HStep 1
HStep 2
HStep 3
Figure 4-5 Configure the CCRS
_________________________________________________________________________________________________________________
Edition: Feb 2012 43 4169.DOC00030

4.1.6 Configure Alert Settings

Procedure: You may but you do not need to customize alert settings (see Figure 4-6).
Step1. Select the Alert node in the Configuration Navigator. It is recommended

to omit this step.
Step2. Double click on the desired alert item in the alert list. A dialog window
appears. Change the timeouts (alarm escalation timeout and mute duration).
Press the commit button before leaving the page.
HStep 1
HStep 2
Figure 4-6 Configure Alert Settings
________________________________________________________________________________________________________________
4169.DOC00030 44 Editon: Feb 2012

R
4.1.7 Save the configuration

Procedure: Save the configuration (see Figure 4-7).
Step1. Select the Welcome button.
Step2. Press the Save button to store the configuration or to store the changes
right into the console.
Step3. Press the Export button to store the configuration or to store the changes
into an external file system such a USB stick.
Step4. After Step2 or Step3 was selected a popup window appears. In this case
the user can be commentate the new configuration in a short helpful way. These
comment appears on the Change Log page labelled with a new Revision number
and a time stamp.
_________________________________________________________________________________________________________________
Edition: Feb 2012 45 4169.DOC00030

HStep 1
HStep 3
HStep 2
HStep 4
Figure 4-7 Save the configuration
________________________________________________________________________________________________________________
4169.DOC00030 46 Editon: Feb 2012

R
4.1.8 Finishing the Configuration Process

After doing and saving the new configuration close the ServiceTool. For finishing the
configuration process you have to select the Restart BIP in the Utility Selections.
Procedure: Finishing the Configuration Process (see Figure 4-8).
Step1. Exit the ServiceTool.
HStep 1
HStep 1
Step 2
Figure 4-8 Exit Service Tool
_________________________________________________________________________________________________________________
Edition: Feb 2012 47 4169.DOC00030

4.1.9 Restart the in the Standalone Console

After any configuration modifications took place, all applications of the standalone
console have to be restarted to apply the changes.
Step1. Exit; RADAR, ECDIS, NAUTOCONNING.
Step3. Select the MFC button for loading up the applications.
4.1.10 Radar Configuration

The RADAR application must be configure with the RADAR Configuration Tool for itself.
See SYNAPSIS Radar Service and Installation Manual Doc. No. 4166DOC020302
chapter 3.2..
________________________________________________________________________________________________________________
4169.DOC00030 48 Editon: Feb 2012

R
5 The Eggshell
The Eggshell is used as utility tool verified for the SYNAPSIS Service Tool. The
Eggshell design depends from the MFC configuration. MFC used with Radar, ECDIS,
Nautoconning or only Radar, ECDIS or ECDIS, Nautoconning. Basically the
SYNAPSIS INS relevant Utility Selections are consistent (see Figure 5-1).
The Eggshell is a helpfully tool for trained service people only with
following services;
x Operator System Shutdown, is used to shutdown this MFC. If the MFC

configuration was changed or updated a System Shutdown has to be done.
x Other Logins.
x Service Switch to Admin + password, after entering the password the service
people is logged in as Administrator.
x Service On Screen Keyboard, in this case an On Screen Keyboard appears on

the display.
x Restart BIP, the BIP process from this MFC will be restarted.
x View Framework Licenses, displays the user rights supporting software.
x Operator Change Date/Time, is used after first installation or when the ships
time system is defective for longer as 4 days.
x Service Tool, access the SYNAPSIS INS Service Tool.
x MFC button, after pressing this button the MFC applications loaded up. The
MFC displays an application. The progression can be defined.
_________________________________________________________________________________________________________________
Edition: Feb 2012 49 4169.DOC00030

MFC configuration with

SYNAPSIS specific
ECDIS and Nautoconning
MFC configuration with

SYNAPSIS specific Radar, ECDIS and
Nautoconning
Radar specific
Figure 5-1 SYNAPSIS INS Eggshell
________________________________________________________________________________________________________________
4169.DOC00030 50 Editon: Feb 2012

R
6 Disturbed Configuration
A disturbed configuration process is marked with red Feedback Symbol on the
Welcome Page see (Figure 6-1).
Procedure: Disturbed Configuration
Step1. Write down the Tool Tip information e.g. “Config request timed out”.
Step2. Exit the Service Tool.
Step3. Start the Service Tool again.
Step4. Repeat the configuration job (e.g. Import).
If this process finished again with the disturbed symbol please inform
Raytheon Anschütz about the Tool Tip information.
Config request timed out
Figure 6-1 Disturbed Configuration
_________________________________________________________________________________________________________________
Edition: Feb 2012 51 4169.DOC00030

7 Troubleshooting
Problem: No sensor data available in the applications.
False or missing information in the CCRS selection tables might result in empty
sensor lists or missing sensor data, although a sensor is connected. Check (and
commit) the CCRS configuration (see Figure 4-5).
________________________________________________________________________________________________________________
4169.DOC00030 52 Editon: Feb 2012

Synapsis Service Tool

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Synapsis Service Tool

Uploaded by

Copyright:

Available Formats

RAnschütz Raytheon Anschütz GmbH

4169.DOC000302 Edition: Feb 2012

Edition: Feb 2012 II 4169.DOC000302

x The installation and initial commissioning may only be

x Maintenance and repair work may only be performed by

x Risk of equipment damage!

Edition: Feb 2012 III 4169.DOC00030

Edition: Feb 2012 IV 4169.DOC000302

RAYTHEON ANSCHÜTZ GMBH Tel. 0431 / 3019 - 0

RAYTHEON ANSCHÜTZ GMBH

Edition: Feb 2012 V 4169.DOC00030

Item No. Amendment. Date of Short Name Signature

Edition: Feb 2012 VI 4169.DOC000302

1 SYNAPSIS SERVICE TOOL ............................................................................................. 1

1.1 General Information ........................................................................................................... 1

2.1 Explanation of Symbols, Software Buttons and Functions ................................................ 3

3 CONFIGURATION EXAMPLE FOR AN INTEGRATED

3.1 SYNAPSIS Radar New Installation .................................................................................. 19

Edition: Feb 2012 VII 4169.DOC00030

4.1 SYNAPSIS Radar New Installation...................................................................................34

5 THE EGGSHELL ..............................................................................................................49

6 DISTURBED CONFIGURATION .....................................................................................51

Edition: Feb 2012 VIII 4169.DOC000302

Figure 2-1 Display information ....................................................................................................... 3

Edition: Feb 2012 IX 4169.DOC00030

Edition: Feb 2012 X 4169.DOC000302

Edition: Feb 2012 XI 4169.DOC00030

Edition: Feb 2012 XII 4169.DOC000302

1 SYNAPSIS Service Tool

1.1 General Information

The SYNAPSIS Service Tool software is a composition of various services deployed

x Standalone consoles only used for Radar or ECDIS or Nautoconning

The configuration service is a service that is installed on each console redundantly,

The configuration of a SYNAPSIS Service Tool is hierarchically structured and has an

Edition: Feb 2012 1 4169.DOC00030

A SYNAPSIS INS supports high grades of redundancy, i.e. redundant connection of

4169.DOC00030 2 Editon: Feb 2012

2.1 Explanation of Symbols, Software Buttons and Functions

Using the trackball to place the Cursor.

Press the left button.

1x click for selecting, 2x click for executing.

The middle and right buttons have no function for the

Figure 2-1 Display information

Edition: Feb 2012 3 4169.DOC00030

1 Service Tool selection buttons using a service tool selection side.

3 Detail view with setting options.

4 Selection tabs for changing the detail view.

5 Quick selection buttons.

2.1.1 Display Navigation

Figure 2-2 Display Navigation

2 Select Service (Process) with a double click.

4169.DOC00030 4 Editon: Feb 2012

2.2 Start-up the SYNAPSIS Service Tool

An USB keyboard has to be connected at the USB connector of the MFC.

Figure 2-3 Eggshell - Utility Selections -

Edition: Feb 2012 5 4169.DOC00030

2.2.1 Welcome Page

Figure 2-4 Welcome Page

4169.DOC00030 6 Editon: Feb 2012

2.2.1.1 User Rights

Mariner User access

The Mariner user is allowed to:

x View and export error logs

x View the whole configuration