Вы находитесь на странице: 1из 82

Installer’s

Guide
Bridge Mate CyScan Installer’s Guide
Issue Date: 26th March 2010
Document No: 94-0085-4-MT

Marine Technologies, LLC


1111 Decker Drive
Mandeville
LA 70471
USA

Tel: +1 985 951 7771


Fax: +1 985 951 7701

Copyright © 2010. All Rights Reserved.


This document may not be used, sold, transferred, copied or reproduced in whole or in
Class 1 Laser Product
part in any manner or form or in or on any media to any person other than in accordance
Complies with EN 60825-1
with the terms of the Owner’s Agreement or otherwise without the prior written consent Complies with USA CFR 1040.10 & 1040.11
of the Owner. All brand or product names are trademarks or registered trademarks of their except for deviations pursuant to Laser Notice
respective companies or organisations. No 50 26 Jul 2001

CLASS 1
LASER PRODUCT

  2
Table of Contents
Introduction������������������������������������������������������������������������������������������ 5 Installing and Configuring CyScan Console���������������������������������������� 24
Welcome������������������������������������������������������������������������������������������������������������������� 6 Saving CyScan Console Configuration Settings������������������������������������������������������������� 25
System Overview������������������������������������������������������������������������������������������������������� 7 Installing the Console Software���������������������������������������������������������������������������������� 26
CyScan Sensor Part Names������������������������������������������������������������������������������������������ 8 Configuring the Day and Night View Colour Schemes����������������������������������������������������� 27
Serial Numbers & Software Versions��������������������������������������������������������������������������� 10 Typical Colour Scheme Configuration File Contents������������������������������������������������� 28
Product Label���������������������������������������������������������������������������������������������������� 10 The Colour Scheme Configuration File������������������������������������������������������������������� 31
Software Version Information������������������������������������������������������������������������������ 10 Creating a New Custom Colour Scheme���������������������������������������������������������������� 32
Sensor Information Display���������������������������������������������������������������������������������������� 11 Setting the Date and Time����������������������������������������������������������������������������������������� 33
Information Display Details��������������������������������������������������������������������������������� 11 Using the On-Screen Keyboard����������������������������������������������������������������������������������� 34
Service Access Mode������������������������������������������������������������������������������������������������� 35
Installing the Sensor Hardware����������������������������������������������������������� 12 Configuration Settings����������������������������������������������������������������������������������������������� 36
Where to Mount the Sensor��������������������������������������������������������������������������������������� 13
General Settings / Version Info���������������������������������������������������������������������������� 37
Sensor Mounting Locations���������������������������������������������������������������������������������� 13
Communications / Display Options����������������������������������������������������������������������� 38
Sensor Dimensions and Mounting Template������������������������������������������������������������������ 14
Vessel Parameters / File Transfer������������������������������������������������������������������������� 40
Console PC Dimensions��������������������������������������������������������������������������������������������� 15
Installing a Licence for Extended Operating Range ������������������������������������������������������� 41
Blanking Zones�������������������������������������������������������������������������������������������������������� 42
Installing the Cables���������������������������������������������������������������������������� 16
Initial Log File Creation��������������������������������������������������������������������������������������������� 43
Cable Specifications�������������������������������������������������������������������������������������������������� 17
UPS Specifications���������������������������������������������������������������������������������������������������� 18
Setting Up the Console Communications������������������������������������������� 44
CyScan Sensor Connections��������������������������������������������������������������������������������������� 19
Re-configuring a Serial Sensor for Ethernet Communications������������������������������������������ 45
To Connect a Cable to the CyScan Sensor������������������������������������������������������������� 19
Setting Up the Console Communications - Ethernet Mode���������������������������������������������� 46
Connecting the Power Cable�������������������������������������������������������������������������������� 19
Re-configuring an Ethernet Sensor for Serial Communications���������������������������������������� 47
Console and DP Feed Connections������������������������������������������������������������������������ 20
Setting Up the Console Communications - Serial Mode�������������������������������������������������� 48
CyScan Console PC Connections��������������������������������������������������������������������������������� 23

  3
Table of Contents (Continued)
Appendices������������������������������������������������������������������������������������������ 49
Target Types������������������������������������������������������������������������������������������������������������ 50 DP Message Monitor�������������������������������������������������������������������������������������������������� 57
Positioning and Mounting Targets�������������������������������������������������������������������������������� 51 Part Numbers����������������������������������������������������������������������������������������������������������� 58
Target Installation��������������������������������������������������������������������������������������������� 51 Standard Components���������������������������������������������������������������������������������������� 58
Positional Display Modes�������������������������������������������������������������������������������������������� 52 Optional Components����������������������������������������������������������������������������������������� 58
Range & Bearing������������������������������������������������������������������������������������������������ 52 Reflective Targets (Optional)������������������������������������������������������������������������������� 58
Bow and Starboard Axes (NMEA0183P)����������������������������������������������� 52 Installation Checklist������������������������������������������������������������������������������������������������� 59
Cable Routing Diagrams�������������������������������������������������������������������������������������������� 61
A and B Axes (A Pos and B Pos) (NMEA0183R)��������������������������������������� 52
Sensor Information Display - Error Messages��������������������������������������������������������������� 63
DP Message Types���������������������������������������������������������������������������������������������������� 53
Information Display Details��������������������������������������������������������������������������������� 63
NMEA0183R Format (0x0001)����������������������������������������������������������������������������� 53
Upgrading the Sensor Software Via the Console������������������������������������������������������������ 65
NMEA0183P Format (0x0002)����������������������������������������������������������������������������� 53
Upgrading the Sensor Software Directly����������������������������������������������������������������������� 66
ASCII17 Format (0x0004)����������������������������������������������������������������������������������� 54
Upgrade Messages��������������������������������������������������������������������������������������������� 67
MDL Standard (0x0008)������������������������������������������������������������������������������������� 54
Diagnostics�������������������������������������������������������������������������������������������������������������� 69
MDL Multi-Target (0x0040)��������������������������������������������������������������������������������� 54
The Diagnostics Menu���������������������������������������������������������������������������������������� 70
Nautronix Standard (0x0080)������������������������������������������������������������������������������ 54
Diagnostic Test Functions����������������������������������������������������������������������������������� 72
Artemis Mk IV (0x0010)������������������������������������������������������������������������������������� 54
Index���������������������������������������������������������������������������������������������������������������������� 74
Kongsberg Standard (0x0020)����������������������������������������������������������������������������� 54
Document History����������������������������������������������������������������������������������������������������� 81
Sensor Connectivity Configuration Utility��������������������������������������������������������������������� 55

  4
Introduction
This section provides an introduction and overview of the CyScan system.
It contains the following sections:
XX Welcome (page 6)
XX System Overview (page 7)
XX CyScan Sensor Part Names (page 8)
XX Serial Numbers & Software Versions (page 10)
XX Sensor Information Display (page 11)

  5
Welcome
Welcome to the CyScan Installer’s Guide. It explains how to mount and install the CyScan
system onto a vessel. For full instructions on how to use CyScan, please see the
CyScan Operator’s Guide (Doc № 94-0084-4).

  6
System Overview
CyScan is a high accuracy marine laser sensor. It provides positional information to a vessel’s The CyScan Console
DP system, allowing it to keep station relative to a target structure or another vessel. CyScan Console is a software application used to control and monitor the CyScan Sensor.
The CyScan system contains the following main parts: It is installed on a marine-specification PC running Microsoft WindowsTM, which is usually
XX CyScan Sensor mounted on the bridge near to the controls of the vessel’s DP system. It gives the DP
operator full control of the CyScan system and the data stream being fed to the DP system.
XX CyScan Console
The Ethernet version of CyScan Console can run on multiple terminals across a network, with
XX CyScan Targets one Master and multiple Slave terminals.

CyScan Sensor
The CyScan Sensor is a rotating laser scanner. It is mounted on the vessel’s superstructure;
typically on the wheel-house.
The CyScan Sensor is available in two versions - Serial or Ethernet. The Ethernet version of
the sensor can accommodate up to 3 connections to the DP system.

Power
CyScan Console

CyScan CyScan Targets


Sensor One or more retro-reflective CyScan targets are
mounted on the target platform or vessel. The
precise range and bearing of each target is used
to calculate the exact position of the CyScan
vessel relative to the target structure or vessel.
See Target Installation on page 51 for more
Console DP detail on CyScan targets.
PC System

The key elements of the CyScan system


CyScan Prism Cluster Target

  7
CyScan Sensor Part Names
The diagram below shows the key parts of the sensor unit and the various names that are
used throughout this guide:

Rotor Optical Window

Access Plate

Power

DP Feed

Console

Base Plate
Information Display Screen
  8
CyScan Sensor Part Names (Continued)

Power

DP Feed
Console
Alternative model with 5 cable glands.

  9
Serial Numbers & Software Versions
Serial numbers and Software Version Numbers are used to identify the hardware
configuration and product revision of each CyScan unit. They will be requested in the event of
an application service support call to the company.

Product Label Software Version Information


The Part Number and Serial Number can The Configuration page tab within the Property sheet provides version information about
be found on the product label fixed to the every software component within the Console application and the CyScan Sensor.
CyScan unit, see right. (See General Settings / Version Info on page 37).

CyScan Sensor
Product Label
Sensor Serial
Number

Software component
version information
CyScan Sensor
Part Number

CyScan Sensor
Serial Number

  10
Sensor Information Display
The Sensor Information Display shows the status of the sensor and it’s internal system throughout each period of operation.

Information Display Details


Below is a list of the messages that appear during normal startup and operation of the CyScan Sensor.
The messages are listed in the order they normally occur, when the system is left to startup and run
without the user pressing any buttons.

Display Screen Message Description


CTRLBOOT V1.04 Displays the current version of the boot loader (1.04 in this example)
Last POST code NN and continually updates ‘NN’ to show the last post code.
ETX booted OK The ETX has booted successfully and is starting the operating system.
NAVBOOT V1.60 The Navboot boot loader has started. The 2nd line indicates whether the
Serial Version sensor is configured for Serial or Ethernet communications (Serial in this example).
Press User BTN2 The system is waiting for the user to press User Push Button 2 if they
To Use USB Functions want to use the USB functions for upgrading etc.
USB is not selected Indicates that the USB options have not been selected (this message shows
when User Push Button 2 was not pressed at the previous stage).
Loading Navigator... The Navboot boot loader had finished and is now starting the application.
Starting application The application is starting.
Starting receiver... The receiver is starting.
Running The sensor and all its internal systems are now running normally. Sensor
Information
Display

  11
Installing the Sensor Hardware
This section contains the following pages:
XX Where to Mount the Sensor (page 13)
XX Sensor Dimensions and Mounting Template (page 14)
XX Console PC Dimensions (page 15)

  12
Where to Mount the Sensor
The CyScan system is designed for permanent or semi-permanent installation on-board a
vessel.
Sensor Mounting Locations
Often, a custom-fabricated plinth is used to provide the optimum height and location for
mounting the CyScan sensor.

A typical mounting position is above the wheelhouse for a vessel with On all types of vessel the sensor should be mounted:
a superstructure like that of on a platform supply vessel. XX With an unobstructed view in the expected direction of the target structure or vessel.
XX Well above sea level to prevent swamping or immersion.
XX On a flat, rigid, horizontal surface able to support 25.5kg and receive 4x M8 fixing bolts.
XX Allowing for easy access to the connector board and Sensor Information Display.
XX Clear of VHF emergency band antenna, S-band and X-band ship’s radars (as far away as
possible but at least 5m, in all directions, from any radar).
XX Clear of likely emissions from exhausts or other particulate sources to reduce the need
for cleaning the optical windows.

! Note: Exhaust emissions contain particulates


which will degrade the optics.
The sensor should be mounted with the Sensor Information Display (see page 11) facing
directly towards either the bow (default) or the stern; parallel to the vessel’s fore and aft
centre-line. Any deviation from the centre-line alignment must be corrected in the CyScan
Console software. (See Bearing Offset on page 40).

  13
Sensor Dimensions and Mounting Template
Sensor Clearance Mounting Template
The exact dimensions of the CyScan unit’s footprint are shown below. Mount the baseplate horizontally and aligned with the bow or stern as shown. By default
The additional information shown on the right will be useful when mounting the CyScan unit. each sensor is configured to have the access plate facing towards the bow. This orientation
Please refer to Document No: 94-0062-4 CyScan Mounting Template to view the information can be reversed if required to give easier access to the cables and access plate.

!
in larger format. WARNING:
If the CyScan sensor is mounted with the access plate facing towards the stern, the
BOW/STERN switch on the connector board (see page 19) must be set to STERN.

Allow a sensor height of 460mm


407 from the mounting plate, plus an

150
190
STERN (default) additional 30mm clearance to
4x 9 THRU
or remove the rotor from the shaft.
BOW

Allow 150mm
STERN (default) BOW (default)
or or clearance for
BOW STERN access to the

460
rotor screws.
15
360
405

300 705
0

0
15
0 15

Allow 150mm
clearance at either
85 300
7
side of the unit for use
of the lifting handles. 5
70

!
BOW (default)
47
80 or
327 Ensure a clear line Allow 300mm STERN
150

150
of sight to the clearance at the
Display Screen in access plate to
857 the access plate. manoeuvre internal
assemblies in/out.

All dimensions in mm
NOT TO SCALE

  14
Console PC Dimensions
The Console PC should ideally be mounted on the bridge,
near to the controls of the vessel’s DP system.

Drawings not to scale Dual-position


mounting brackets
can be attached to
283.3mm the bottom or the
268.3mm
246.6mm top of the unit.

R 5.0mm

R 2.0mm

60.5mm
*300 mm

PC front view
mm
mm
mm
mm
Dual-position mounting brackets can be
230.1
239.8
250.1
261.8
attached to the bottom or the top of the unit.
31.7 mm
22.0 mm
11.7 mm

60.5mm
* Allow an additional 45mm space at the front
and 65mm at the rear for the connectors. PC plan view PC rear view

  15
Installing the Cables
This section contains the following pages:
XX Cable Specifications (page 17)
XX UPS Specifications (page 18)
XX CyScan Sensor Connections (page 19)
XX CyScan Console PC Connections (page 23)

  16
Cable Specifications
The CyScan system is usually supplied without the cables that are necessary to connect the
sensor to the DP system and to the PC control console. Cables must be supplied and fitted
by the installer to match the particular requirements for each vessel. All cables should be
properly secured.
The cable glands will fit cables from 7-13mm diameter.

! Note: Data cables should not be run next to power


cables to avoid signal interference problems.

Use Description Manufacturer Part Numbers


(40m lengths)

Signal Wiring to DP System


Minimum 5-core shielded data cable, 33-0122-3
twisted pair. Olflex Classic 135 CH xG 0.5 All cables should be
Signal Wiring to Console armoured, external
marine standard
Ethernet connection to including UV and
User Console PC Standard CAT 5e screened cable chemical resistance,
33-0124-3
(and optional Ethernet (maximum length 90m). 500V rated voltage,
link to DP System) Diameter 7-13mm
and operate between
33-0121-3 -40°C to +80°C.
Power Cable 3 core cable.
Olflex Classic 400 CP 3G 1.0

x is number of cores including Ground with each core 0.5mm2 (minimum 5-core specifies 4 signal cores and 1 ground core).

! Note: Refer to the cable routing diagrams


on page 61 to determine which cables you require.

  17
UPS Specifications
The main power supply to the CyScan Sensor and console must come directly from a UPS
(Un-interruptible Power Supply), which will also act as the power disconnection point.
The CyScan system comprises the following components and the UPS system used must meet
these minimum specifications:

CyScan
XX The UPS must be Marine Type Approved
XX Output Power = 3W / 35 dBm
XX Input Power = 45W
XX Voltage Range = 85-264 Vac
XX Peak Current draw at 110V = 1.14A RMS
XX Nominal Current draw at 110V = 0.68A RMS
XX Peak Current draw at 240V = 0.52A RMS
XX Nominal Current draw at 240V = 0.4A RMS

Marine PC
XX Voltage Range = 100-240Vac
XX Frequency Range = 50-60Hz
XX Peak Current draw = 0.4A RMS
The CyScan UPS should be able to run on back-up power for at least the same duration as
that specified for the DP System UPS.
The power cable to the CyScan Sensor must be rated to withstand the maximum current
output of the UPS.

! Note: The specifications given above apply when


the UPS is connected to a CyScan system only.

  18
CyScan Sensor Connections

To Connect a Cable to the CyScan Sensor Cable ties Power terminals on connector board
1. Remove the 4 screws from the access plate and remove the plate from the sensor unit to
expose the connector board. (See CyScan Sensor Part Names on page 8).
2. Remove the screw head from the appropriate watertight cable gland. See CyScan Sensor Live
Part Names on page 8 to identify the correct cable gland.
3. Feed the cable through the screw head and gland.
Earth
4. Connect the cable to the correct socket/terminal on the sensor connector board.
5. When all the connections have been made, replace the access plate and tighten all of the Terminal block with cable cores connected
cable glands to ensure a watertight seal. Neutral

Connecting the Power Cable


Having fed the cable through the watertight cable gland, use the key provided to open the
ferrite and pass the cable through the centre of the ferrite. Close the ferrite securely and
ensure it is firmly attached to the inside of the CyScan casing to prevent excessive movement.
Then strip 10mm of insulation from the end of
each of the three cores and connect them to
the appropriate terminals as labelled on the
Watertight Ferrite BOW/STERN switch
terminal block (see below).
cable gland and key see page 14 for details
Ferrite Key When you have connected the cores to the
terminal block, use two cable ties to secure
the terminal block and cable together before
plugging the terminal block securely in to the
socket on connector board as shown on the
right.

Ferrite secured around cable


To Connect Cables to
Power/Serial Plugs: 
..Hook lever-tool into
slot above connector-
hole in plug.

33Whilst holding down
lever, insert cable end
into connector-hole.
$$Release and remove
the lever-tool.
Base of CyScan with the access plate removed to expose the connector board
  19
Console and DP Feed Connections
The console and DP feed connections will vary depending on whether the sensor unit
is configured for connection via an Ethernet connection (an Ethernet Sensor) or a serial
connection (a Serial Sensor).

To Connect an Ethernet Sensor to the Console and the DP Feed:

! Note: The console network must be a


separate network from the DP network.
A network switch will be required if more than one Console is to be connected to the
sensor when running on a self-contained network. We recommend using a NetGear
Ethernet switch such as the FS105. Similar alternatives may be suitable but have not
been tested for compatibility. The Ethernet sockets are Auto/MDI/X capable. †Contact your DP supplier if
  alternative settings are required. Console Network Protocols:
DP Network Protocols: Master: TCP/IP
For a sensor connected to a single console a crossover Ethernet cable is sufficient. UDP unicast Slave: UDP multicast
See CyScan Console PC Connections on page 23 for details about the Console ports. UDP client 192.168.1.11
Default Ethernet Settings: †

Default DP Ethernet Settings: IP Address: 192.168.0.86
IP Address: 192.168.1.86 Subnet Mask: 255.255.255.0
Subnet Mask: 255.255.255.0 Multicast Group: 0

Mains Power
85–264V AC Fuses Power LED
45–65Hz 45W Power
Serial 1
Ferrite Bead

VFD Screen

Ethernet Link
to Vessel’s
DP System Ethernet 1

Stern
Serial 0

Ethernet 0 Bow Service Connections


Ethernet Link to
Serial ports 0 & 1 can be used as optional DP feed outputs. Marine PC
This can be configured using ‘connect.ini’,
see Sensor Connectivity Configuration Utility on page 55.
  20
To Connect an Ethernet Sensor with Ethernet to the Console and Serial to the DP Feed:
Connect Ethernet Port 0 to the Console PC and Serial Port 1 to the DP system.
Configure the serial connections as shown below:

To Connect Cables to
Power/Serial Plugs:  1  RX-
RS422 Link
Serial 1 9600 baud
..Hook lever-tool into 2  RX+
8 bits
slot above connector- 3  TX-
hole in plug. 1 stop bit
4  TX+
No parity
5  GND
33Whilst holding down  6  Test
lever, insert cable end
into connector-hole. DP 7  GND *+24V output on pin 8 of
Feed 8  +24V * both serial ports can be
used to power a 100mA
$$Release and remove
the lever-tool. data converter, if required.

Mains Power
85–264V AC Fuses Power LED
45–65Hz 45W Power

Ferrite Bead Serial 1

VFD Screen

RS422 Link
†Contact your DP supplier if Console Network Protocols:
Master: TCP/IP
to Vessel’s
Ethernet 1
  alternative settings are required. DP System
Slave: UDP multicast

Default Ethernet Settings:
IP Address: 192.168.0.86 Stern
Serial 0
Subnet Mask: 255.255.255.0
Multicast Group: 0 Ethernet 0 Bow Service Connections
Ethernet Link to
Marine PC

  21
To Connect a Serial Sensor to the Console and the DP Feed:
Connect Serial Port 0 to the Console PC and Serial Port 1 to the DP system.
Configure the serial connections as shown below:

To Connect Cables to
Power/Serial Plugs:  RS422 Link
1  RX-
..Hook lever-tool into Serial 1 2  RX+
9600 baud
slot above connector- 8 bits
3  TX-
hole in plug. 1 stop bit
4  TX+
No parity
33Whilst holding down 5  GND
lever, insert cable end
 6  Test
into connector-hole. DP 7  GND *+24V output on pin 8 of
$$Release and remove Feed 8  +24V * both serial ports can be
used to power a 100mA
the lever-tool. data converter, if required.

Mains Power
85–264V AC Fuses Power LED
45–65Hz 45W Power

Ferrite Bead

RS422 Link Serial 1


VFD Screen
38400 baud
8 bits 1  RX-
1 stop bit 2  RX+
RS422 Link
No parity 3  TX-
to Vessel’s
4  TX+
DP System Ethernet 1
5  GND
6  Test
1 2 3 4 5 7  GND Serial 0
6 7 8 9
8  +24V * Stern

Ethernet 0 Bow Service Connections


Marine PC CyScan RS422 Link to
Com1/Com2 Serial 0 Marine PC

  22
CyScan Console PC Connections

Connect an Ethernet sensor to the Console PC using any of the Ethernet


ports (LAN 1, 2 or 3). (LAN 1 & 2 are preferred. LAN 3 operates with a
maximum cable length of 50m and is generally reserved for diagnostics).

Connect a Serial sensor to the Console PC using either of the COM ports.
(COM1 is the default).

Front View

Rear View

Front and Rear View of Marine PC (Part No: 20-0098-1A)

  23
Installing and Configuring CyScan Console
This section contains the following pages:
XX Saving CyScan Console Configuration Settings (page 25)
XX Installing the Console Software (page 26)
XX Configuring the Day and Night View Colour Schemes (page 27)
XX Setting the Date and Time (page 33)
XX Using the On-Screen Keyboard (page 34)
XX Service Access Mode (page 35)
XX Configuration Settings (page 36)
ƒƒ General Settings / Version Info (page 37)
ƒƒ Communications / Display Options (page 38)
ƒƒ Vessel Parameters / File Transfer (page 40)
XX Installing a Licence for Extended Operating Range (page 41)
XX Blanking Zones (page 42)
XX Initial Log File Creation (page 43)

  24
Saving CyScan Console Configuration Settings
The configuration settings for the CyScan Console, which were previously stored in the
system registry, are now stored in the ‘c4config.ini’ file.
The ‘c4config.ini’ is normally located in the installation directory for the CyScan Console
application. The default location is:
C:\Program Files\CyScan4\c4config.ini

!
IMPORTANT: Indiscriminate adjustment of parameter settings can adversely affect the
operation of CyScan. DO NOT edit the settings unless directed to do so by a qualified
technician.

  25
Installing the Console Software
This section explains how to install CyScan Console software onto a Marine PC. If the PC has
been supplied by the manufacturer, it may have been shipped with CyScan Console already
installed. However, it may be necessary to upgrade the Console software with a newer
version.

! Note: Before installing a newer version of CyScan Console, ensure that all previous
versions have been uninstalled.

To Uninstall CyScan Console:


1. Click on Start > All Programs> CyScan User Console x.xx>Uninstall.
2. Click Next when the wizard appears.
Welcome
3. Make sure the path in the ‘Uninstalling from:’ field is correct. Screen
4. Click on the Uninstall button.

! Note: If the installation directory has already been deleted manually the ‘uninstall.
exe’ file will be missing. In this case you just need to delete the ‘CyScan User Console
x.xx’ folder from Start>All Programs and then delete the desktop shortcut.

! Versions of CyScan Console earlier than v4.30 will need to be removed using the
‘Programs and Features’ facility from the Control Panel.

To Install CyScan Console: Choose


5. Copy the CyScan Console.msi file, from the USB memory stick or CD on which it was Install
supplied, onto the PC’s hard disk. Location
Screen
6. Double-click on the CyScan Console.msi file.
The Welcome screen is displayed.
7. Click on the Next button.
8. Select either Serial or Ethernet as appropriate and click on the Next button.
9. Select either the serial port or the Multicast Group, as appropriate for the option chosen
in step 7, then click on the Next button.
The Choose Install Location screen is displayed.
10. Click on the Next button to install Console in the default directory
(C:\Program Files\CyScan4).
Installation
11. Click OK when prompted to do so.
Complete
12. Click on the Finish button to finish the install. Screen
  26
Configuring the Day and Night View Colour Schemes
To provide maximum visibility during daytime operation and minimal glare during night shifts,
CyScan User Console offers two display modes: ‘Day View’ and ‘Night View’. There is one
colour scheme available for Day View, “grey”, and a choice of two colour schemes available
for Night View, “green” or “orange”.

Day View “grey” Night View “green”


colour scheme with colour scheme with
default parameters. default parameters.

The colour scheme configuration file, ‘c4colour.ini’, controls all the parameters relating to
the day and night view colour schemes. This file is located in the CyScan Console installation
directory.
The default path for the installation directory is:
C:\Program Files\CyScan User Console

! Note: If the ‘c4colour.ini’ file is missing it will be created the first time the Console
application is run. The values contained within the ‘c4colour.ini’ file will then
override any internally held defaults. The Console will read data from the ‘c4colour.ini’
file but will never write to the file.
The default view (Day View or Night View in either “green” or “orange”) can be set within the
‘c4colour.ini’ file.
Each of the three colour schemes has default parameters, but these can be customised by
editing the appropriate parameters within the ‘c4colour.ini’ file. Alternative Night View
“orange” colour scheme
with default parameters.
  27
Typical Colour Scheme Configuration File Contents
The following example shows the contents of a typical ‘c4colour.ini’ file and includes the
default values for all three colour schemes:
[startup] COLOUR_GenericBackground=0xd8e9ec
default=registry COLOUR_GenericForeground=0x8b0000
day=day_standard COLOUR_ScannerBackground=0xe16941
night=night_green COLOUR_ScannerForeground=0x00a5ff
[custom] COLOUR_ScannerText=0x00a5ff
DayBannerPath= COLOUR_QualityHigh=0x00c000
NightBannerPath= COLOUR_QualityMed=0x0080ff
COLOUR_QualityLow=0x0000ff
[day_standard]
COLOUR_ScannerRefln=0x00ffff
SYSCOLOR_3DDKSHADOW=0x404040
COLOUR_ScannerReflnOutline=000000
SYSCOLOR_3DFACE=0xd8e9ec
COLOUR_ScannerReflnSelected=0x0000ff
SYSCOLOR_3DHILIGHT=0xffffff
BRUSH_ScannerBackground=0xe16941
SYSCOLOR_3DLIGHT=0xd8e9ec
BRUSH_ScannerSurveyPoint=0x9314ff
SYSCOLOR_3DSHADOW=0x808080
BRUSH_GenericBackground=0xd8e9ec
SYSCOLOR_ACTIVEBORDER=0xd8e9ec
BRUSH_ScannerReflnBad=0x0000ff
SYSCOLOR_ACTIVECAPTION=0x6a240a
BRUSH_ScannerTargetGood=0x00ffff
SYSCOLOR_APPWORKSPACE=0x808080
BRUSH_ScannerTargetBad=0x0000ff
SYSCOLOR_BACKGROUND=0xa56e3a
BRUSH_ScannerVesselBackground=0xa9a9a9
SYSCOLOR_BTNTEXT=000000
BRUSH_ScannerVesselCyScanBackground=0x0000ff
SYSCOLOR_CAPTIONTEXT=0xffffff
BRUSH_BlankingZoneBackground=0xd8e9ec
SYSCOLOR_GRAYTEXT=0x808080
BRUSH_CompassNeedle=0x0000ff
SYSCOLOR_HIGHLIGHT=0x6a240a
BRUSH_ScannerVesselForeground=000000
SYSCOLOR_HIGHLIGHTTEXT=0xffffff
PEN_ScannerBackground=0xe16941
SYSCOLOR_INACTIVEBORDER=0xd8e9ec
PEN_ScannerSurveyPoint=0x9314ff
SYSCOLOR_INACTIVECAPTION=0x808080
PEN_GenericForeground=0x8b0000
SYSCOLOR_INACTIVECAPTIONTEXT=0xd8e9ec
PEN_ScannerReflnBad=0x0000ff
SYSCOLOR_INFOBK=0xe1ffff
PEN_ScannerTargetGood=0x00ffff
SYSCOLOR_INFOTEXT=000000
PEN_ScannerTargetBad=0x0000ff
SYSCOLOR_MENU=0xd8e9ec
PEN_ScannerVesselForeground=000000
SYSCOLOR_MENUTEXT=000000
PEN_ScannerVesselCyScanForeground=0x0000ff
SYSCOLOR_SCROLLBAR=0xd8e9ec
PEN_BlankingZoneForeground=0xd8e9ec
SYSCOLOR_WINDOW=0xffffff
PEN_ScannerForeground=0x00a5ff
SYSCOLOR_WINDOWFRAME=000000
PEN_ScannerHeadingAxis=000000
SYSCOLOR_WINDOWTEXT=000000
SYSCOLOR_GRADIENTACTIVECAPTION=0xf0caa6
SYSCOLOR_GRADIENTINACTIVECAPTION=0xc0c0c0
SYSCOLOR_HOTLIGHT=0x808080
SYSCOLOR_MENUHILIGHT=0xc56a31

  28
Typical Colour Scheme Configuration File Contents (Continued)

[night_green] COLOUR_ScannerRefln=0x00ffff
SYSCOLOR_3DDKSHADOW=0x404040 COLOUR_ScannerReflnOutline=000000
SYSCOLOR_3DFACE=000000 COLOUR_ScannerReflnSelected=0x0000ff
SYSCOLOR_3DHILIGHT=0x40ff40 BRUSH_ScannerBackground=0x142814
SYSCOLOR_3DLIGHT=0x008000 BRUSH_ScannerSurveyPoint=0x9314ff
SYSCOLOR_3DSHADOW=0x005500 BRUSH_GenericBackground=000000
SYSCOLOR_ACTIVEBORDER=0x008000 BRUSH_ScannerReflnBad=0x0000ff
SYSCOLOR_ACTIVECAPTION=0x005500 BRUSH_ScannerTargetGood=0x00ffff
SYSCOLOR_APPWORKSPACE=0x005500 BRUSH_ScannerTargetBad=0x0000ff
SYSCOLOR_BACKGROUND=000000 BRUSH_ScannerVesselBackground=0x1f1f1f
SYSCOLOR_BTNTEXT=0x00c000 BRUSH_ScannerVesselCyScanBackground=0x0000ff
SYSCOLOR_CAPTIONTEXT=0x008000 BRUSH_BlankingZoneBackground=000000
SYSCOLOR_GRAYTEXT=0x005500 BRUSH_CompassNeedle=0xaab220
SYSCOLOR_HIGHLIGHT=0x40ff40 BRUSH_ScannerVesselForeground=0x4f4f4f
SYSCOLOR_HIGHLIGHTTEXT=0x008000 PEN_ScannerBackground=0x142814
SYSCOLOR_INACTIVEBORDER=0x008000 PEN_ScannerSurveyPoint=0x9314ff
SYSCOLOR_INACTIVECAPTION=0x005500 PEN_GenericForeground=0x228b22
SYSCOLOR_INACTIVECAPTIONTEXT=0x008000 PEN_ScannerReflnBad=0x0000ff
SYSCOLOR_INFOBK=0x40ff40 PEN_ScannerTargetGood=0x00ffff
SYSCOLOR_INFOTEXT=0x008000 PEN_ScannerTargetBad=0x0000ff
SYSCOLOR_MENU=000000 PEN_ScannerVesselForeground=0x4f4f4f
SYSCOLOR_MENUTEXT=0x008000 PEN_ScannerVesselCyScanForeground=0x0000ff
SYSCOLOR_SCROLLBAR=0x40ff40 PEN_BlankingZoneForeground=000000
SYSCOLOR_WINDOW=000000 PEN_ScannerForeground=0x228b22
SYSCOLOR_WINDOWFRAME=0x008000 PEN_ScannerHeadingAxis=0xd3d3d3
SYSCOLOR_WINDOWTEXT=0x40ff40
SYSCOLOR_GRADIENTACTIVECAPTION=0x00ff00
SYSCOLOR_GRADIENTINACTIVECAPTION=0x005500
SYSCOLOR_HOTLIGHT=0x800000
SYSCOLOR_MENUHILIGHT=0x141414
COLOUR_GenericBackground=000000
COLOUR_GenericForeground=0x228b22
COLOUR_ScannerBackground=0x142814
COLOUR_ScannerForeground=0x228b22
COLOUR_ScannerText=0xa4a4a4
COLOUR_QualityHigh=0x00c000
COLOUR_QualityMed=0x0080ff
COLOUR_QualityLow=0x0000ff

  29
Typical Colour Scheme Configuration File Contents (Continued)

[night_orange] COLOUR_ScannerReflnOutline=000000
SYSCOLOR_3DDKSHADOW=0x00233f COLOUR_ScannerReflnSelected=0x0000ff
SYSCOLOR_3DFACE=000000 BRUSH_ScannerBackground=0x002346
SYSCOLOR_3DHILIGHT=0x008cff BRUSH_ScannerSurveyPoint=0x9314ff
SYSCOLOR_3DLIGHT=000000 BRUSH_GenericBackground=000000
SYSCOLOR_3DSHADOW=0x00233f BRUSH_ScannerReflnBad=0x0000ff
SYSCOLOR_ACTIVEBORDER=000000 BRUSH_ScannerTargetGood=0x00ffff
SYSCOLOR_ACTIVECAPTION=0x00233f BRUSH_ScannerTargetBad=0x0000ff
SYSCOLOR_APPWORKSPACE=0x00233f BRUSH_ScannerVesselBackground=0x1f1f1f
SYSCOLOR_BACKGROUND=000000 BRUSH_ScannerVesselCyScanBackground=0x0000ff
SYSCOLOR_BTNTEXT=0x00467f BRUSH_BlankingZoneBackground=000000
SYSCOLOR_CAPTIONTEXT=000000 BRUSH_CompassNeedle=0xaab220
SYSCOLOR_GRAYTEXT=0x00467f BRUSH_ScannerVesselForeground=0x4f4f4f
SYSCOLOR_HIGHLIGHT=0x00233f PEN_ScannerBackground=0x002346
SYSCOLOR_HIGHLIGHTTEXT=0x008cff PEN_ScannerSurveyPoint=0x9314ff
SYSCOLOR_INACTIVEBORDER=000000 PEN_GenericForeground=0x008cff
SYSCOLOR_INACTIVECAPTION=0x00233f PEN_ScannerReflnBad=0x0000ff
SYSCOLOR_INACTIVECAPTIONTEXT=000000 PEN_ScannerTargetGood=0x00ffff
SYSCOLOR_INFOBK=0x008cff PEN_ScannerTargetBad=0x0000ff
SYSCOLOR_INFOTEXT=000000 PEN_ScannerVesselForeground=0x4f4f4f
SYSCOLOR_MENU=000000 PEN_ScannerVesselCyScanForeground=0x0000ff
SYSCOLOR_MENUTEXT=0x00467f PEN_BlankingZoneForeground=000000
SYSCOLOR_SCROLLBAR=000000 PEN_ScannerForeground=0x008cff
SYSCOLOR_WINDOW=000000 PEN_ScannerHeadingAxis=0xd3d3d3
SYSCOLOR_WINDOWFRAME=000000
SYSCOLOR_WINDOWTEXT=0x008cff
SYSCOLOR_GRADIENTACTIVECAPTION=0x008cff
SYSCOLOR_GRADIENTINACTIVECAPTION=0x00233f
SYSCOLOR_HOTLIGHT=0x800000
SYSCOLOR_MENUHILIGHT=0x141414
COLOUR_GenericBackground=000000
COLOUR_GenericForeground=0x008cff
COLOUR_ScannerBackground=0x002346
COLOUR_ScannerForeground=0x008cff
COLOUR_ScannerText=0x008cff
COLOUR_QualityHigh=0x00c000
COLOUR_QualityMed=0x0080ff
COLOUR_QualityLow=0x0000ff
COLOUR_ScannerRefln=0x00ffff

  30
The Colour Scheme Configuration File
The [startup] section of the ‘c4colour.ini’ file has three entries and these determine Colour values are specified as 24-bit RGB values in hexadecimal format with the following
which colour scheme is selected when the CyScan Console application is started up and byte order:
which day and night colour schemes are used. colour = 0xBBGGRR
Where BB is the 8-bit blue, GG the 8-bit green and RR the 8-bit red value.
[startup]
default=registry
day=day_standard The [custom] section of the ‘c4colour.ini’ file allows for customisation of the individual
night=night_green system, brush and pen colours and also for the use of custom branding banners.
The default day and night banners pictured below can be replaced with OEM supplied images
The ‘default’ key determines which colour scheme is applied when the CyScan Console by specifying the absolute or relative paths to the image files, for example:
application is first started up. When this key is set to ‘registry’ the Console displays the
most recently used colour scheme, as stored in the ‘c4config.ini’ file (see Saving CyScan [custom]
Console Configuration Settings on page 25). Setting the ‘default’ key to either ‘day’ or DayBannerPath=.\custom_day_logo.bmp
‘night’ will command the Console to start every time in either Day View or Night View NightBannerPath=.\custom_night_logo.bmp
respectively.
The ‘day’ key determines which colour scheme is applied for Day View. This will usually be set
The image files must be Windows BMP bitmap files of size 411 x 77 pixels.
to ‘day_standard’ to apply the “grey” colour scheme as this is the only pre-defined day
scheme available.
Default Day View Banner
The ‘night’ key determines which colour scheme is applied for Night View and will usually be
set to either ‘night_green’ to apply the “green” colour scheme or ‘night_orange’ to
apply the “orange” colour scheme.
The corresponding colour scheme sections, e.g. [day_standard], define the actual
system colours, pens, brushes and generic colours used. Each value is listed explicitly with a
prefix, SYSCOLOR_..., COLOUR_..., BRUSH_... or PEN_..., to indicate which component of the Default Night View Banner
user interface it relates to. Each of the values can be edited to customise the colour scheme
as required.

[day_standard]
SYSCOLOR_3DDKSHADOW=0x404040
...
COLOUR_GenericBackground=0xd8e9ec
...
BRUSH_ScannerBackground=0xe16941
...
PEN_ScannerBackground=0xe16941

  31
Creating a New Custom Colour Scheme
If required, you can define a complete custom day or night colour scheme by adding the
details to the end of the ‘c4colour.ini’ file, rather than editing the details for one of the
existing colour schemes.
1. Give the scheme a name, e.g [day_custom] then define all the colours as required:

[day_custom]
SYSCOLOR_3DDKSHADOW=0x404040
...
COLOUR_GenericBackground=0xd8e9ec
...
BRUSH_ScannerBackground=0xe16941
...
PEN_ScannerBackground=0xe16941

Refer to the example shown in Typical Colour Scheme Configuration File Contents on
page 28 to see the full list of colours to define.
2. Once you have defined your new scheme you need to set either the ‘day’ or ‘night’ key in
the [startup] section according to your requirements. For example:

[startup]
default=registry
day=day_custom
night=night_green

In the example above the new custom colour scheme [day_custom] will be used for
Day View.

  32
Setting the Date and Time
To Set the System Date and Time:
1. Double-click on the time displayed on the Status Bar at the bottom of the screen.
2. The Date and Time Properties window is opened.
3. Set the correct date and time and click on the OK button.

  33
Using the On-Screen Keyboard
In order to accommodate systems without keyboards, CyScan Console provides an on-screen
keyboard option. This enables text input using only a mouse pointer. You can activate the
on-screen keyboard wherever you see this icon:
If the icon is greyed out then the on-screen keyboard feature is disabled.

!
Note: By default, the on-screen keyboard feature is disabled as CyScan is usually
installed on systems with keyboards. (See ‘To enable the on-screen keyboard’
below).

To use the on-screen keyboard:


1. Click on the icon to display the on-screen keyboard.
2. Select an item within the CyScan Console that requires text entry or editing.
3. Click on the required keys on the on-screen keyboard using your mouse.

To enable the on-screen keyboard:


1. Enter Service Access Mode (see page 35).
2. Click on the Sensor Operations button.
3. Click on CyScan Configuration.
The Configuration Tab is opened.
4. Click on the down arrow of the Select Configuration Category box and select the
Communications / Display Options entry.
5. Tick the Enable On-Screen Keyboard option.
6. Click on the Apply button.

  34
Service Access Mode
Several parameters within CyScan Console can seriously affect system operation if they are 3. Click on the Service Access button in the lower right corner of the About tab.
set incorrectly. These critical settings can only be changed in Service Access Mode. A dialog will be opened, displaying a Service request code:

!
IMPORTANT: Indiscriminate adjustment of parameter settings can adversely affect the
operation of CyScan. DO NOT edit the settings unless directed to do so by a qualified
technician.
Service Access Mode can be entered either by plugging an engineer’s USB key into any
available USB port on the console computer before starting the application, or by obtaining
a temporary service access code as described below. If using a USB key it is recommended
that when the settings are complete, the application is restarted without the key in order to
return to normal user mode.

To obtain and use a temporary service access code:


1. Click on the Sensor Operations button.
2. Select the About CyScan option.
The About Tab is displayed:

4. Send the service request code to an authorised customer service representative.

!
Note: The service request code is constructed as two groups of six upper case
letters [A-Z] separated by a plus sign (+). There are never any numerals in a service
request code.
5. A corresponding Service access code will be supplied to you. This code is nontransferable
and will operate only with current Console system for a limited period.

! Note: The service access code is a


12 digit hexadecimal number [0-9, A-F].
6. Enter the received code into the Service access code field and click on the OK button.
Service access will be granted on the system for a maximum period of 12 hours.
However, the system will automatically exit Service Access mode after 20 minutes.
To restart Service Access mode within the 12-hour grace period, click on the
Service Access button on the About tab.

  35
Configuration Settings

Opening the Configuration Tab Configuration Options


The Configuration Tab is used to set up the Console software. To access all of the Configuration options are arranged in three categories:
configuration settings you must use an Engineer’s USB key, or obtain a temporary service XX General Settings / Version Info (see page 37).
access code. (See Service Access Mode on page 35).
XX Communications / Display Options (see page 38) (Service Access Mode Only).

To Open the Configuration Tab: XX Vessel Parameters / File Transfer (see page 40) (Service Access Mode Only).

1. Click on the Sensor Operations button.


To Access Additional Configuration Categories:
2. Click on CyScan Configuration.
XX Click on the Select Configuration Category
The Configuration tab is displayed: drop-down arrow and select the required option.

  36
General Settings / Version Info Display Options
The General Settings/Version Info screen is used to set the DP Feed Format and basic display The following default settings can overridden from the Display Options menu. However, the
options. It also displays detailed software version information for the Sensor and the Console display will change back to the default settings when the CyScan Console is restarted.
software.
Range & Bearing Only
To Access the General Settings/Version Info Screen: Tick the Range and Bearing Only checkbox to display range and bearing information while
1. Click on the Sensor Operations button. navigating. (See Positional Display Modes on page 52). This option has no effect on the
message strings sent to the DP system.
2. Click on CyScan Configuration.
The Configuration tab is displayed:
Day View/Night View
To provide maximum visibility during daytime operation and minimal glare during night shifts,
CyScan User Console offers two display modes: ‘Day View’ and ‘Night View’.
To change the view option, click on the drop-down arrow and select either
Day View or Night View.

!
Note: The default view, and the default colour schemes for the Day and Night
views, are set in the ‘c4colour.ini’ configuration file (see Configuring the Day and
Night View Colour Schemes on page 27).

Example Night View


DP Feed Format & Message String
The DP Feed Format & Message String must be configured to match the vessel’s DP system. Example Day View
(see DP Message Types on page 53).

To Set the DP Feed Format


1. Enter Service Access Mode (see page 35) using either an Engineer’s USB key or a
temporary service access code.
2. Click on the DP Feed Format & Message String drop-down arrow and select the required
feed format.
3. Click on the Apply button.

  37
Communications / Display Options Console Options
The Communications/Display Options screen is used to configure the console display, data The Console Options are used to set the orientation of the vessel outline on the console
logging options and DP feed behaviour. display, and to enable/disable the on-screen keyboard.

To Set the Communications / Display Options: Bow Orientation


1. Enter Service Access Mode (see page 35) using either an Engineer’s USB key or a The Bow Orientation option is used to rotate the blue circular sensor display area so that it
temporary service access code. matches the orientation of the DP system display. The whole display including any blanking
zone is rotated so that the relative range and bearing to any targets remains constant. This
2. Click on the Sensor Operations button. option does not affect the data that is sent to the DP System.
3. Click on CyScan Configuration. The required orientation usually depends on the direction in which the system is used. For
The Configuration tab is displayed: example, if CyScan is used while facing aft looking out over the stern, the display should be
set up with the vessel bows pointing downwards. See page 14 for important information!
4. Click on the Select Configuration Category drop-down arrow and select
Communications / Display Options. XX Click on the drop-down arrow and select the required orientation for the vessel’s bows
(Top, Bottom, Left or Right).
5. Select the required options and click on the Apply button.
On-Screen Keyboard
Tick the Enable On-Screen Keyboard option to display the on-screen keyboard.
(See Using the On-Screen Keyboard on page 34).

Datalog Options
The Datalog Options are used to turn logging on or off, and to set the log file storage location.
XX Select Disable to switch off system logging (NOT Recommended).
XX Select Enable to write log files to C:\Program Files\CyScan User Console.
XX Select Custom to specify another log file storage location, and enter a valid file path.

  38
DP Feed Behaviour
The DP Feed Behaviour options control the data sent to the DP system if a target is lost:

!
The DP Feed Behaviour settings must be set correctly for the vessel’s DP system.
Incorrect settings can cause serious problems. Refer to the vessel’s DP system supplier
for the precise configuration.

The following behaviour applies while navigating: The following behaviour applies when no navigation is in progress:
For a DP Feed format that does not contain status flags: For a DP Feed format that does not contain status flags:
DP Feed Allow Refresh DP Feed Allow Refresh
Always Timer and Output if Target is Lost Always Timer and Output if Target is Lost
Enabled Zero Strings Enabled Zero Strings
  Null data (gaps in data string)   Null data (gaps in data string)
  Null data (gaps in data string)   Null data (gaps in data string)
  Stale Data (with zeroed ID field if applicable)   Zero data (coordinates are set to zero)
  Stale Data (with zeroed ID field if applicable)   Null data (gaps in data string)

For a DP Feed format that does contain status flags,


for Single-Target Navigation: For a DP Feed format that does contain status flags:
DP Feed Allow Refresh DP Feed Allow Refresh
Always Timer and Output if Target is Lost Always Timer and Output if Target is Lost
Enabled Zero Strings Enabled Zero Strings
  Flag indicates stale data; data is stale for 10sec then zero   Null data (gaps in data string)
  Flag indicates stale data; data is stale for 10sec then zero   Zero data (flag indicates void data)
  Flag indicates stale data; data is stale for 10sec then zero   Zero data (flag indicates void data)
  Flag indicates stale data; data is stale for 10sec then zero   Null data (gaps in data string)

for Multi-Target Navigation:


DP Feed Allow Refresh
Always Timer and Output if Target is Lost
Enabled Zero Strings
  Flag indicates stale data; data is stale indefinitely
  Flag indicates stale data; data is stale indefinitely
  Flag indicates stale data; data is stale indefinitely
  Flag indicates stale data; data is stale indefinitely DP Feed Behaviour
Check Boxes

  39
Vessel Parameters / File Transfer Bow and Starboard Offsets
The Vessel Parameters screen is used to enter the vessel’s name and to set the position and
bearing of the scanner in relation to the vessel’s centre-line. This screen is also used for
Bow Offset
loading range licences see Installing a Licence for Extended Operating Range on page 41.

To Set Up the Vessel’s Parameters:


1. Enter Service Access Mode (see page 35) using either an Engineer’s USB key or a
temporary service access code.
2. Click on the Sensor Operations button.
Starboard Offset
3. Click on CyScan Configuration.
The Configuration tab is displayed.
4. Click on the Select Configuration Category drop-down arrow and select
Vessel Parameters / File Transfer.
5. Enter the required vessel Bearing Offset
parameter values and click on the The CyScan Sensor should be aligned as closely as possible with the vessel’s centre-line, so
Apply button. the Bearing Offset should only need to be a few degrees at most.
ƒƒ Name—Enter the vessel’s name. (See Where to Mount the Sensor on page 13).
It will appear at the top of the
main console screen.
ƒƒ Length and Breadth—Enter the
length and width (beam) of the Sensor pointing to Port. Sensor pointing to Starboard.
vessel in metres. Enter a positive Enter a negative
Bearing Offset Angle. Bearing Offset Angle.
ƒƒ Bow Offset—Enter the distance + -
between the CyScan Sensor and
the vessel’s bow in metres.
ƒƒ Starboard Offset—Enter the
distance between the CyScan
Sensor and the vessel’s side in
metres.
ƒƒ Bearing Offset—If the CyScan
Sensor is exactly parallel to the
vessel’s centre-line running from bow to stern, enter a Bearing Offset of 0°.
If the sensor is pointing slightly to Port in relation to the vessel’s centre-line, enter a
positive bearing offset in degrees, e.g. 2°.
If the sensor is pointing slightly to Starboard in relation to the vessel’s centre-line,
enter a negative bearing offset in degrees, e.g. -2°.

  40
Installing a Licence for Extended Operating Range
A standard CyScan unit will operate with a range of 1250m and does not require any form
of range licence. The range can be extended as shown below by installing an appropriate
licence:
XX Long range = 2500m
XX Extended long range = 3250m

To Install a Range Licence:


1. Load the Vessel Parameters/File Transfer screen (see Vessel Parameters / File Transfer
on page 40.
2. Click the Load button (see right).
3. Browse and select the required ‘.ctf. file, then click Open.
4. Click Yes on the warning message if you are sure you have selected the correct file.
A message will appear confirming that the licence has been loaded and identifying the
new range (either 2500m or 3250m).
5. Click Yes to apply the licence key.
Load/Remove
buttons

To Remove a Range Licence:


1. Load the Vessel Parameters/File Transfer screen (see Vessel Parameters / File Transfer
on page 40.
2. Click on the Remove button (see right).
3. Click Yes on the warning dialog if you are sure you want to proceed.
A message will appear confirming that the licence has been removed and the system will
now operate at the standard range.

  41
Blanking Zones
A Blanking Zone can be used to mask the segment of the scan rotation that is obscured by
the vessel’s superstructure.

! Note: Changing the blanking zone whilst navigating


will interrupt the data sent to the DP system.

To Create a Blanking Zone


1. Enter Service Access Mode (see page 24) using either an Engineer’s USB key or a
temporary service access code.
2. Click on the Sensor Operations button.
3. Click on Set Blanking Zone > Manually.
4. Click on the first segment of the blanking zone. (See right).
5. Release the mouse button.
6. Move the mouse in an anti-clockwise direction around the display circle.
(When you hover over a segment it will turn grey, showing that it will
become part of the blanking zone). La
t st
en S
7. Click on the last segment of the blanking zone. m eg
S eg m
en
8. Click on the Apply button to confirm the changes. st t
Fir
Click Click
and mouse.
To Show or Hide the Blanking Zone  release
1. Click on the Display Options button. mouse.

2. Click on Show Blanking Zone.
If this option is ticked, the blanking zone (if set) will be displayed.

!
Note: When selecting the start and stop segments for the blanking zone,
you must always work in an anti-clockwise direction.

  42
Initial Log File Creation
When a new CyScan system is first commissioned, a log file should be created as a base
reference for the system. A copy of the initial log file should be sent to your DP supplier.
Ideally, the initial log file should be created by navigating against a CyScan Target for at least
10 minutes. If this is not possible, start logging manually (see below) for 10 minutes.
When the logging period has been completed, follow the steps below to copy and send the
log file to your DP supplier:
1. Go to C:\Program Files\CyScan User Console and locate the sub-folder that matches the
start and end times of the logged period.
2. Right-click on the sub-folder and left-click on Send To > Compressed (zipped) Folder.
3. E-mail the compressed Zip file to your DP supplier.

System Logging Options


During navigation, the system automatically generates a set of operation logs. Logging can
also be started manually, when the system is not navigating (see below).
By default, logs are written to the C:\Program Files\CyScan User Console directory, unless a
custom file-path has been entered in the Communications / Display Options screen
(see page 38). Sub-folders within this directory are named according to the time period that
they cover.

Starting and Stopping Manual Logging

! Note: During manual logging, the CyScan button is disabled.


You must stop logging before you can exit the system.
To start (and stop) manual logging, either press the
Alt + L keys together, or use the menu option:
1. Click on the Sensor Operations button.
2. Click on Datalogs > Log data now.
If the Log data now option is ticked, logging is in progress:

  43
Setting Up the Console Communications
This section contains the following pages:
XX Re-configuring a Serial Sensor for Ethernet Communications (page 45)
XX Setting Up the Console Communications - Ethernet Mode (page 46)
XX Re-configuring an Ethernet Sensor for Serial Communications (page 47)
XX Setting Up the Console Communications - Serial Mode (page 48)

  44
Re-configuring a Serial Sensor for Ethernet Communications
Each CyScan sensor will be pre-configured for either Serial or Ethernet communications
before it is shipped.

!
WARNING:
Make sure you know the current configuration of your sensor before proceeding
(see page 11 for details on how to determine this). Do not continue if unsure.

To re-configure a Serial sensor to Ethernet communications mode you will need to obtain a
copy of the ConnCfg utility (ConnCfg.exe). You will also need a USB upgrade key.

! Note: The console network must be a separate


network from the DP network.

To Re-configure a Serial Sensor to Ethernet Mode: Default Settings:


If your sensor is already configured for Ethernet communications, go straight to Setting The default factory settings for an Ethernet configured CyScan sensor are as follows:
Up the Console Communications for an Ethernet Configured Sensor: on page 46.
Otherwise you can re-configure the sensor as follows: DP Network Protocols:

1. Obtain the parameters for the Console network (Sensor IP address, Sensor multicast ƒƒ UDP Unicast
group number, Network netmask, Gateway), the DP server network (DP server IP ƒƒ UDP client 192.168.1.11
address, Network netmask, Gateway) and the DP message Clients IP addresses (these
must be on the same network as the DP server). Default DP Ethernet Settings:
ƒƒ IP Address: 192.168.1.86
2. Use the ConnCfg utility to generate a connect.ini file for the sensor (See Sensor
Connectivity Configuration Utility on page 55). ƒƒ Subnet Mask: 255.255.255.0

3. Copy the connect.ini file into the Upgrade folder on an upgrade USB memory stick.
Ensure this folder also contains Ethernet versions of NavBoot.exe and NavApp.exe. Console Network Protocols:
ƒƒ Master: TCP/IP
4. Use the upgrade USB memory stick to upgrade these files. (See Upgrading the Sensor
ƒƒ Slave: UDP Multicast
Software Directly on page 66).
Default Ethernet Settings:
5. After a successful upgrade, power down the sensor and connect it to the network as
described in To Connect an Ethernet Sensor to the Console and the DP Feed: (see page ƒƒ IP Address: 192.168.0.86
20). ƒƒ Subnet Mask: 255.255.255.0
6. Go to Setting Up the Console Communications for an Ethernet Configured Sensor: on ƒƒ Multicast Group: 0
page 46 and complete all the steps in that section.

  45
Setting Up the Console Communications - Ethernet Mode
Setting Up the Console Communications for an Ethernet Configured Sensor:
If your sensor is currently configured for Serial communications but you need to run it
with Ethernet communications, complete all the steps in Re-configuring a Serial Sensor
for Ethernet Communications (see page 45) first.
1. Ensure the network parameters are set up correctly on the Console PC. (Contact the
network administrator if necessary to ensure that the parameters are correct). ! See Re-configuring a Serial Sensor for Ethernet Communications
on page 45 for the default network settings.
2. Power up the sensor.
3. Once the sensor is running, use the PC that you set up in step 1 to ping the sensor with
the sensor IP address as configured in the ‘connect.ini’ file. If you are using an internal
Intranet, such as a company-wide network, you can use any PC on this Intranet to verify
that the sensor can be pinged.
4. Uninstall all previous installations of the CyScan Console software from the Console PC
you set up in step 1.
5. Install the latest CyScan Console software on the PC you set up in step 1, selecting
Helpful Points/Troubleshooting
Ethernet rather than Serial when prompted to choose. Set the Multicast Group to match
what was set in the ‘connect.ini’ file. See Installing and Configuring CyScan Console 1. Reserved IP addresses must be used if the system is running on a self-contained network.
(page 24). The sensor uses a static address and DCHP is not supported. Make sure the correct
6. Run the Console software on the PC and verify whether the multicast channel can network parameters have been used to generate ‘connect.ini’.
communicate with the sensor (the status indicator in the status bar on the Console 2. The Console PC must be on the same self-contained network as the sensor. The network
display will be green, rather than red, if communication is OK). parameters for the Console PC must be configured correctly in order for communications
7. If the status indicator in the status bar of the Console display remains red after 15 to work between the sensor and the Console PC. This normally involves setting up a
seconds, click the CyScan button on the Console to launch the Control dialog. correct static IP address, a network netmask (normally 255.255.255.0) and a gateway IP.

8. Select Reset Communication from the drop-down list and verify whether communication 3. The Console PC and the sensor must both have the same multicast group number.
is OK (the status indicator will turn green). When a CyScan Console runs first time on the network, the console may have a different
multicast group number to the sensor in use. Follow steps 4-9 above to configure a
9. If the status indicator remains red after completing steps 1-8, check all connections and multicast group for the Console.
the sensor configuration parameters etc. and retry, or contact your local service engineer
for assistance. 4. A Console PC automatically retrieves the correct sensor IP once the correct multicast
group has been configured.
10. Repeat steps 1 and 4-9 for any additional Console PCs.
5. A Console PC always starts in slave mode by default. You can switch between working
as a slave Console and a master by clicking the CyScan button, and selecting relevant
commands from the control dialog.

  46
Re-configuring an Ethernet Sensor for Serial Communications
Each CyScan sensor will be pre-configured for either Serial or Ethernet communications
before it is shipped.

!
WARNING:
Make sure you know the current configuration of your sensor before proceeding
(see page 11 for details on how to determine this). Do not continue if unsure.

You will need a USB upgrade key to complete the following process:

To Re-configure an Ethernet Sensor to Serial Mode:


1. Copy Serial versions of NavBoot.exe and NavApp.exe into the Upgrade folder on an
upgrade USB memory stick.
2. Use the upgrade USB memory stick to upgrade the NavBoot.exe and NavApp.exe files
(see Upgrading the Sensor Software Directly on page 66).
3. After a successful upgrade, power down the sensor and connect it to the Console PC as
described in To Connect a Serial Sensor to the Console and the DP Feed: (see page 22).

4. Go to Setting Up the Console Communications for a Serial Configured Sensor: on page Information Display
48 and complete all the steps in that section.

VGA USB1 USB2 User Push Button 2

  47
Setting Up the Console Communications - Serial Mode
Setting Up the Console Communications for a Serial Configured Sensor:
If your sensor is currently configured for Ethernet communications but you need to run it
with serial communications, complete steps 1-3 in Re-configuring an Ethernet Sensor for
Serial Communications (see page 47) first.
1. Uninstall all previous installations of the CyScan Console software from the Console PC.
2. Install the latest CyScan Console software on the Console PC, selecting Serial rather than
Ethernet when prompted to choose. Set the Serial Port to match the serial port that
is being used to connect the Console PC to the sensor. See Installing and Configuring
CyScan Console (page 24).

3. Connect the sensor to the Console PC as described in To Connect a Serial Sensor to the
Console and the DP Feed: (see page 22), if not already connected.

4. Power up the sensor.


5. Run the Console software on the PC and verify that the Console can communicate with
the sensor (the status indicator in the status bar on the Console display will be green,
rather than red, if communication is OK).
6. If the status indicator in the status bar of the Console display remains red after 15
seconds, click the CyScan button on the Console to launch the Control dialog.

7. Select Reset Communication from the drop-down list and verify whether communication
is OK (the status indicator will turn green).

8. If the status indicator remains red after completing steps 1-8, check all connections and
retry or contact your local service engineer for assistance.

  48
Appendices
This section contains the following pages:
XX Target Types (page 50)
XX Positioning and Mounting Targets (page 51)
XX Positional Display Modes (page 52)
XX DP Message Types (page 53)
XX Sensor Connectivity Configuration Utility (page 55)
XX DP Message Monitor (page 57)
XX Part Numbers (page 58)
XX Installation Checklist (page 59)
XX Cable Routing Diagrams (page 61)
XX Sensor Information Display - Error Messages (page 63)
XX Upgrading the Sensor Software Via the Console (page 65)
XX Upgrading the Sensor Software Directly (page 66)
XX Diagnostics (page 69)
XX Index (page 74)

  49
Target Types
CyScan can operate successfully with flat or cylindrical targets. These are available from your
CyScan agent and are shown below:

Flat Targets Cylindrical Targets Prism Targets


Flat targets are generally attached to rigid structures such Cylindrical targets can be used up to Prism cluster with 8 x 6cm elements
as metal stanchions using steel bands. approximately 300 metres. They can be hung over for extended range operations. Varible
2 metre tall flat targets can typically be seen at up to the side of the structure/vessel and secured at configurations allow for optimisation of the
400 metres in ideal conditions. Shorter 1 metre tall flat either end. visible reflection, visible reflection level or
targets are visible at up to 250 metres when viewed Part number: 20-0078-0-B reflected power.
straight on. (2m cylindrical reflector) Part number: 20-0075-1-A
Part number: 20-0031-0
(2m x 350mm flat reflector including stainless steel
bands)

  50
Positioning and Mounting Targets

Target Installation
Key to the operation of the CyScan system is the correct installation of targets. Please follow
the guidelines given below when installing targets on the structure/vessel.
Once the targets are installed, their relative positions can be automatically surveyed by the
system.

Installation Tips Optimum Spacing for Multiple Targets


XX Targets should be placed in positions where the sensor can see them while the vessel is XX Targets should be positioned with unequal spacing between them – this helps the system
within the expected working area. Consider vertical position as well as horizontal. to distinguish between specific targets. For example, with a typical mooring distance of
XX Flat targets should not be placed too far along the structure/vessel from the expected 40-80m using three targets, suitable spacings between the targets would be 10m and
working area as this can reduce the viewing angle for close operations. 20m – giving a total spread of 30m.

XX The sensor beam should not strike a flat target at an angle of more than 45 degrees to


the target surface.
XX Cylindrical targets can be viewed from any angle equally well.  Targets are asymmetrically spaced,
thus making it easier for the CyScan system
to assess which reflection corresponds to a
particular target.

VI
ANEWAB
45 o
GLE LE 45 o
0 VI
ANEWAB
XX Targets should be placed no closer than 5m together. Ideally they should be placed 10m
or more apart.
GLE LE

û û Targets are too close together and have


even spacings. This makes it more difficult
for the CyScan system to differentiate
them.

  51
Positional Display Modes
The relative positions of the RadaScan vessel and single or multiple targets can be expressed
either as Range and Bearing values, or in terms of the rectangular coordinate frame
Bow and Starboard Axes (NMEA0183P)
appropriate to the selected type of navigation (single or multi-target) and DP feed messages. In this mode the position of the sensor vessel is expressed in metres from the target along
Bow and Starboard axes which have their origin at the primary (or only) target.
Coordinate frame axes are only displayed if the DP feed is set to either NMEA0183P or
NMEA0183R. The display can be overridden to display Range and Bearing data, if required. The axes are parallel with the vessel’s own axes.
This mode is available for single target navigation, and for multi-target navigation where the
DP Mode Navigation Type Coordinate Frame Axes
DP feed messages are of type NMEA0183P (primary).
NMEA0183P (Primary) Single Target Bow and Starboard Axes
Multi-Target
NMEA0183R (Raw) Single Target Bow and Starboard Axes
Multi-Target A and B Axes
All other DP formats display Range and Bearing data only.
To change the positional display mode:
The default mode is set in the General Settings / Version Info tab (see page 37) but this
setting can be overridden from the Display Options menu:

! Note: Selecting either option has no effect on


the message strings sent to the DP system.
1. Click on the Display Options button. A and B Axes (A Pos and B Pos) (NMEA0183R)
2. Click on Display Options > Range & Bearing Only. In this mode the position of the sensor vessel is expressed in metres from the target along A
If the Range & Bearing option is ticked, range and bearing will be displayed. If the option and B axes which have their origin at the primary target.
is un-ticked, either Bow and Starboard or A and B axes information will be displayed, The axes are initially aligned with the multi-target group, with the A axis passing through the
depending on the type of DP feed messages that are being sent to the DP system. secondary target. However, if the multi-target group is subsequently aligned, the axes are
rotated such that the A axis remains as the baseline for the vessel heading.
Range & Bearing This mode is only available for multi-target navigation where the DP feed messages are of
Range and Bearing mode displays the distance and the bearing of the target from the sensor type NMEA0183R (raw).
vessel.

  52
DP Message Types

NMEA0183R Format (0x0001) NMEA0183P Format (0x0002)


A 42-character string: A 42 character string:
$RLS,±AAA.AA,±BBB.BB,S1,XXX.XXX,S2,HHHH*CC<CR><LF> $RLS,±AAA.AA,±BBB.BB,S1,XXX.XXX,S2,HHHH*CC<CR><LF>
Where: Where:
XX $RLS message header XX $RLS message header
XX AAA.AA resolved raw position in A axis [metres] XX AAA.AA resolved primary position in A axis [metres]
XX BBB.BB resolved raw position in B axis [metres] XX BBB.BB resolved primary position in B axis [metres]
XX S1 status of position data in A and B axis, A - available; V - void XX S1 status of position data in A and B axis, A - available; V - void
XX XXX.XXX resolved bearing of vessel with respect to A axis [degrees] XX XXX.XXX resolved bearing of vessel with respect to A axis [degrees]
XX S2 status of bearing data, A - available; V - void XX S2 status of bearing data, A - available; V - void
XX HHHH status word in hexadecimal. Up to 16 bits defined in a separate specifications XX HHHH status word in hexadecimal. Up to 16 bits defined in a separate specifications
document document.
XX CC computed checksum in hex XX CC computed checksum in hex
XX <CR> Carriage return (ASCII 0D hex) XX <CR> Carriage return (ASCII 0D hex)
XX <LF> Line feed (ASCII 0A hex) XX <LF> Line feed (ASCII 0A hex)

!
Note: When the targets are installed on a fixed platform and their co-ordinates are
entered in Northings and Eastings, AAA.AA and BBB.BB will also be in Northings
and Eastings and XXX.XXX will be true vessel heading.

  53
DP Message Types (Continued)

ASCII17 Format (0x0004) Nautronix Standard (0x0080)


A 17 character string delimited only by <CR> and <LF> with bearing measured bow clockwise. A 14 character string delimited only by <CR> and <LF> with bearing measured bow clockwise.
Character Index Description Format Character Index Description Format
0-5 Range (metres x 10) nnnnnn6 Space (0x20h) X7-12 Bearing (degrees x 1000) nnnnnn13 0-1 ID nn2-6 Bearing (degrees x 100) nnnnn7-11 Range (m x 10)) nnnnn12 carriage return
Space (0x20h) X14 Status Flag (0 = invalid, 1 = valid) N15 carriage return (0x0Dh) X16 (0x0Dh) X13 line feed (0x0Ah) X

MDL Standard (0x0008) Artemis Mk IV (0x0010)


A 19 character string delimited only by <CR> and <LF> with bearing measured bow clockwise. A 17 character string delimited only by <CR> and <LF> with bearing measured bow clockwise.
Character Index Description Format Character Index Description Format
0-1 ID nn2 Space (0x20h) X3-9 Range (m) nnnn.nn10 Space (0x20h) X11-16 Bearing (degrees) 0-5 Range (metres x 10) nnnnnn6 Space (0x20h) X7-12 Bearing (degrees x 1000) nnnnnn13
nnn.nn17 carriage return (0x0Dh) X18 line feed (0x0Ah) X Space (0x20h) X14 ID (always 1) N15 carriage return (0x0Dh) X16 line feed (0x0Ah) X

MDL Multi-Target (0x0040) Kongsberg Standard (0x0020)


A 22 character string delimited only by <CR> and <LF> with bearing measured bow clockwise. A 9 character string in BCD format.
Character Index Description Format Character Index Description Format
0-1 ID nn2 Space (0x20h) X3-9 Range (m) nnnn.nn10 Space (0x20h) X11-16 Bearing (degrees) 0-2 Bearing (degrees x 100) in BCD ddd3-5 Range (metres x 10) in BCD ddd6 Zero (0x00h) X7
nnn.nn17 Space (0x20h) X18-19 NMEA style checksum in hex CC20 carriage return (0x0Dh) Zero (0x00h) X8 Delimiter (0xFFh) X
X21 line feed (0x0Ah) X

  54
Sensor Connectivity Configuration Utility
The ConnCfg utility (‘ConnCfg.exe’) can be obtained from your DP supplier and can be run by
launching the ‘ConnCfg.exe’ file.
The ConnCfg utility is used to generate a ‘connect.ini’ file, or to change an existing one.
The ‘connect.ini’ file is used to reconfigure a CyScan sensor from serial to Ethernet
communications mode.
Once generated the ‘connect.ini’ file can be copied into the sensor root disk so that the
sensor can be “seen” as a node on a user-selected network with a set of configured
parameters.

!
Note: The ‘connect.ini’ file itself covers more configurable parameters than are
provided by the ConnCfg utility. The parameters are not opened for configuration by
this utility but are generated automatically when an ini file is generated.

Before using this utility you will need to know the network parameters for the network
you will connect the sensor to, and you will need to determine whether port COM1 on the
sensor (normally used to communicate with a serial console) will be used as an additional DP
message transmitter.

ConnCfg Utility Main Window


New Node IP Field

continued...

  55
Sensor Connectivity Configuration Utility (Continued)
To Generate a New ‘connect.ini’ File: Contents of a Typical ‘connect.ini’ file
1. In the Ether0 section enter the IP Address, Gateway and Netmask for the Ethernet 0 Below is an example of a typical ‘connect.ini’ file. The content shown below corresponds to
port, which is used for communication with the Console. the data shown in the image on page 55. In each section the parameters are listed in the
order they are generated by the ConnCfg utility. Some values are not user configurable with
! Note: As you type in the IP Address field, the utility will make a best guess for the
Ether0 Gateway field and will enter the IP address into this field automatically.
the ConnCfg utility, but you can also use a text editing utility, such as Notepad, to edit the ini
file directly.
2. Use the arrows on the Multicast Group field to enter the correct number for this case. [System]
3. In the Ether1 section enter the IP Address, Gateway and Netmask for the Ethernet 1 NumberOfEtherPort = 2
port, which is used as the DP server address. MaxDPFeedReceivers = 5

!
Console = “ether0”
Note: As you type in the IP Address field, the utility will make a best guess for the
DPFeed1 = “ether1”
Ether1 Gateway field and will enter the IP address into this field automatically.
DPFeed2 = “serial2”
The utility will also make a best guess for the new node IP field in the DP Clients
DPFeed3 = “unknown”
section and will enter this IP address automatically too.
[ether0]
4. Enter a DP client’s address in the New Node IP field then click the Add to List button to
IPAddress = “192.168.3.3”
add the address to the DP Clients List box.
Netmask = “255.255.255.0”
ƒƒ Repeat to add more IP addresses to the DP Clients List box - up to a maximum of 5. Gateway = “192.168.3.1
ƒƒ Select an address in the DP Clients List and click Remove to remove it from the list. MulticastGrp = 0
ƒƒ Click Remove All to remove all the addresses from the DP Clients List. [ether1
IPAddress = “192.168.6.6”
5. If you want to use the COM1 port as an additional DP transmitter (only applicable when Netmask = “255.255.255.0”
using a CyScan sensor configured to Ethernet mode) check the Use COM1 Gateway = “192.168.6.1”
( Serial Port 0 ) for DP feed checkbox. MulticastGrp = 0
6. When you are sure you have entered everything correctly, click the Save As button and [ether2]
choose an appropriate location and filename when prompted (the filename must be IPAddress = “0.0.0.0”
‘connect.ini’ when the file is copied into the sensor root disk). Netmask = “255.255.255.0”
Gateway = “”
MulticastGrp = 0
To Edit an Existing ‘connect.ini’ File: [Bootloader]
MulticastPort = 7701
1. Open the file to be edited by clicking the View File button and locating/selecting the file
MulticastAddress = “239.255.3.15”
using the File Open Dialog.
[EtherDPFeedClients]
2. Edit the fields as required. See To Generate a New ‘connect.ini’ File: for details on
DPFeedIPAddress0 = “192.167.6.200”
editing each field.
DPFeedIPAddress1 = “192.167.6.201”
3. Click the Save button to save the file with its original filename, or click Save As and enter DPFeedIPAddress2 = “0.0.0.0”
a new filename when prompted (the filename must be ‘connect.ini’ when the file is DPFeedIPAddress3 = “0.0.0.0”
copied into the sensor root disk). DPFeedIPAddress4 = “0.0.0.0”

  56
DP Message Monitor
A DP message monitor (‘DPMessageMonitor.exe’) is available for CyScan Console v4.20 and The Message Server IP field shows the DP message server’s IP address, but this is only active
can be obtained from your DP supplier. This test utility monitors DP messages on the sensor’s when DP messages are received.
DP message network and can be used to verify that the connection is properly configured. The Monitored UDP Port field shows the server UDP port for sending DP messages.
This utility can be run by launching the ‘DPMessageMonitor.exe’ file. Do not change this.

DP Monitor Utility To Monitor a DP Message:


The utility can be used to monitor the DP messages transmitted from the sensor’s DP 1. Configure the PC with the correct network parameters and make sure the PC is on
message server. The utility uses User Datagram Protocol (UDP) and, in order to monitor the the same network as the sensor’s UDP server (sensor’s eth1, see Sensor Connectivity
messages, needs to be configured as a UDP client to the sensor server. The address for its Configuration Utilityon page 55).
host should already have been added to the client list (see Sensor Connectivity Configuration

!
Utility on page 55). Note: The IP address used for the PC must already have been added to the DP
Server’s Client List using the ConnCfg utility (See Sensor Connectivity Configuration
DP Monitor Layout Utility on page 55).
The image below shows the screen layout of the DP Message Monitor: 2. Click the Start button to begin monitoring the DP messages. The DP messages will appear
in the middle list box.
3. You can use the Clear button to clear the list box to accommodate new messages.

The Local IP field shows the IP address of the local host PC, where the DP monitor is running.
The IP address will already have been added to the DP server’s client list using the ConnCfg
utility (see Sensor Connectivity Configuration Utility on page 55).

  57
Part Numbers

Standard Components Reflective Targets (Optional)


Component Part Number Component Part Number
Mounting Template 94-0062-4-A Flat 2m x 350cm 20-0031-0
Cable Routing Diagram 94-0114-4/94-0117-4 Cylindrical 1.9m Ø 200mm 20-0078-0
Operator’s Guide 94-0084-4 Glass prism cluster with 8 x 20-0075-1
Installer’s Guide 94-0085-4 6cm elements
DC4 98-0025-4-A
Dispenser Needle (for DC4) 98-0026-4-A
Dispensing Syringe (for DC4) 98-0024-4-A

Optional Components
Component Part Number
Marine PC 20-0098-1-A
Monitor, Bracket & Cables Various
Keyboard 38-0038-4-A
Mouse 38-0037-4-A
Ethernet Laptop 38-0062-1-A
Power Cable (40m) 33-0121-3
Data Cable (40m) 33-0122-3
Ethernet Cable (40m) 33-0124-3
Ethernet Connector Plug 80-0091-4

  58
Installation Checklist

CYScan Sensor Serial No.


Console PC Serial Serial No.
Shipping Line
Vessel Name
Installer

Mechanical Installation Console Configuration


Check Requirement  Check Requirement 
Sensor The Sensor is mounted securely with 4 bolts. Communications The Console is communicating with the sensor correctly.
The Sensor’s connector board is facing towards the bow or the stern Settings
and the sensor orientation switch is set accordingly. Console Date and The CyScan Console PC’s Date and Time are set correctly.
The Sensor has a clear line of sight in the direction of the target. Time
Cables The cables are installed away from power cables. General Settings/ The DP Feed Format & Message String is set correctly for the
Version Info vessel’s DP system.
The cables are properly secured.
The Sensor’s serial number is shown correctly.
Console PC The Console PC is mounted securely in an optimum location.
The Sensor and Console software version details are correct.
Communications/ The DP Feed Behaviour is set correctly for the vessel’s DP system.
Sensor Connections Display Options The Bow Orientation is set correctly.
Check Requirement 
If the Console PC does not have a physical keyboard,
Power The Sensor’s power inlet is connected correctly to the vessel’s UPS. the on-screen keyboard is enabled.
Power supply is within the range of 85-264VAC 45-63Hz Logging is enabled.
DP Feed The Sensor is connected correctly to the DP system using the Vessel Parameters The Vessel Dimensions have been entered correctly.
approved cables and connectors.
The Bow and Starboard Offsets have been set correctly.
CyScan The Sensor is connected correctly to the CyScan Console PC using the
The Bearing Offset has been set correctly.
Console approved cables and connectors.
Blanking Zone A blanking zone has been set to cover any superstructure in close
proximity to the sensor.
Changes to Sensor Software Exit Service Access The Engineer’s USB key has been removed and the system has
Check Requirement  Mode been restarted.
Sensor Software All required updates or changes made to the Sensor Software have
been completed.

  59
Installation Checklist (Continued)
Connection Tests System Interference Tests
Check Requirement  Check Requirement 
Sensor­–Console The connection between the Sensor and the Console is OK. Vessel Radio Whilst CyScan is navigating against a target, switch on the vessel’s
Connection radios systems.
Sensor­–DP The DP system can receive a message string from the Sensor. Ensure that CyScan does not suffer any loss of signal quality.
Connection Ensure that the vessel’s radio systems are not adversely affected by
Cyscan.
Functional Tests
Training
Check Requirement 
System is 1 or 2 targets can be identified by the Sensor. Check Requirement 
Operational Basic Operation The crew understand the basic operation of the system.
Bearing Offset Place a target at the stern, in-line with and facing the sensor. Check The crew understand the need to switch on the system early.
the target’s bearing on the RadaScan Console display to verify any The crew understand the importance of the correct positioning of
bearing offset. targets.
Range Test The system is able to locate a target at a distance no less than 150 The crew understand the need to suspend the system after use.
metres.
The crew understand the need to power cycle the entire system
DP System Test CyScan’s DP Feed Message String is accepted by the DP System. (Console PC and Sensor) regularly (at least once a month).
The DP weighting against other available reference systems is within Operator’s The crew know how to access the Operator’s Guide.
acceptable levels. Guide

Initial Log File


Check Requirement 
System Log Files A set of initial system log files have been created.
The log files have been e-mailed to your DP supplier.

  60
Cable Routing Diagrams
Ethernet Communications

DP Instrument Room Bridge Mast Link Cable


Overhead Monitor Binnacle (Aft)
CyScan Console
DP Feed
Power
CyScan
Monitor

CyScan
Sensor
Monitor Cable

Central DP Console (Aft)

Marine PC

60.5mm
16A Marine PC Power Cable

Monitor Power Cable

DP System UPS
Emergency Breaker Box Note: The Ethernet cable connecting
Ethernet the CyScan Sensor to the Marine PC
5A
should not exceed 90 metres in length.
Ethernet Cable
Please contact your DP supplier if
P/N 33-0124-3 (40m)
longer distances are required.

5A
Sensor Power
DP System UPS Power Cable
P/N 33-0121-3 (40m)
Interface Cabinet

RS-422 Data
Data Cable
P/N 33-0122-3 (40m)

  61
Cable Routing Diagrams (Continued)
Serial Communications

DP Instrument Room Bridge Mast Link Cable


Overhead Monitor Binnacle (Aft) CyScan Console
DP Feed
CyScan Power
Monitor

CyScan
Sensor
Monitor Cable

Central DP Console (Aft)

Marine PC

60.5mm
16A Marine PC Power Cable

Monitor Power Cable RS-422 Data


Data Cable
P/N 33-0122-3 (40m) Note: COM1 is the default COM port on
the Marine PC, but it can be reconfigured
for COM2 if necessary.
DP System UPS
Emergency Breaker Box
5A

5A
Sensor Power
DP System UPS Power Cable
P/N 33-0121-3 (40m)
Interface Cabinet

RS-422 Data
Data Cable
P/N 33-0122-3 (40m)

  62
Sensor Information Display - Error Messages
The Sensor Information Display shows the status of the sensor and it’s internal system throughout each period of operation.

Information Display Details


Below is a list of the messages that may appear if a problem occurs during operation, with descriptions of their meaning:

Display Screen Message Description


Boot fail, resetting Start up failed and a retry is about to commence.
Checking components Checking the system components. Sensor
CTRLAPP not found The controller application has not been programmed (software is missing). Information
CTRLBOOT V1.02 This message is displayed when the system begins booting. Display
CyScan Boot Failed Start up failed repeatedly. Power cycle the system to retry the start up.
power cycle to retry
Diagnostic exit The system has exited the diagnostic mode and is waiting for the sensor to
Waiting for reboot reboot.
Download timed out The link between the system and boot loader has failed.
Err writing sw event There was an error writing a period software event to the system.
ETX booted OK All the power-on tests have been passed.
ETX in BIOS SETUP ETX is in BIOS setup screens or test.
ETX Missing OS/Disk The sensor firmware is missing or corrupted.
Failed Programming failed.
Failed to initialise Receiver The receiver failed to start correctly.
Failed to start rotor The rotor motor could not be started.
Failed to suspend rotor The rotor could not be suspended.
Going to running Preparing to suspend the sensor.
Going to suspend Preparing to suspend the sensor.
Last POST code nn The power-on test ‘nn’ is being performed.
Low Temperature The sensor’s temperature is currently below the normal operating temperature and it has entered an automatic warm-up state. This state
Warming up system prevents the rotor from turning until the system reaches a safe operating temperature.
-NN°C please wait... The system is warming up and the temperature has reached NN degrees °C.
Power Fail A low voltage supply has been detected.
Program failed CRC CtrlApp application failed its CRC check when loading.
Programming CtrlApp Programming has been started.

  63
Sensor Information Display - Error Messages (Continued)

Information Display Details (Continued)


Below is a list of the messages that may appear if a problem occurs during operation, with descriptions of their meaning:

Display Screen Message Description


Programming complete Programming of the CtrlApp was successful.
Receiver Fatal Error The receiver has generated a fatal alarm and cannot start.
Resetting The boot loader has issued a reset.
Running The sensor is in the normal running state.
Starting application The main sensor is starting.
Starting motor The rotor motor is about to start.
Starting receiver The receiver is about to start.
Suspended The sensor is suspended.
Updating Blanking Zn A new blanking zone has been sent to the receiver, which is updating accordingly.
Updating receiver New parameters have been sent to the receiver, which is updating accordingly.
Waiting for command Boot loader is waiting for commands.
Writing page nn Boot loader is writing internal flash page nn.

  64
Upgrading the Sensor Software Via the Console
Where possible any upgrades to the sensor software should be done via the Console.
The following files can be upgraded this way:

XX NAVAPP.EXE
XX NAVMON.BIN
XX CTRLAPP.HEX
XX RECAPP.HEX

! For receiver upgrading CTRLAPP.HEX must


already be present on the sensor.

To Upgrade the Sensor Software via the Console:


1. Start the Console in Service Access mode (see Service Access Mode on page 35).
2. Select the required option from the drop-down list:
ƒƒ Upgrade Navigator Executable (NAVAPP.EXE)
ƒƒ Upload Operating System Kernel (NAVMON.BIN)
ƒƒ Upload MKIV Controller Image (CTRLAPP.HEX)
ƒƒ Upload MKIV Receiver Image (RECAPP.HEX)
then click on OK.
3. Follow any on-screen instructions to complete the transfer of the selected file.

! If you need to upgrade more than one component, don’t reboot the sensor when
prompted, just upgrade the next component as required.
4. After the final component has been transferred, select Reboot and then select the option
to load the upgrade tool if you wish to observe the process.

  65
Upgrading the Sensor Software Directly
If it is not possible to use the Console you can upgrade the sensor software directly.
Each CyScan sensor has a ‘main’ ETX flash drive (the rootdisk), which runs the main Navigator
application, plus an additional secondary disk. When the system is running all data is written
to the secondary disk, allowing the main disk to run without interruption.
If the secondary disk is missing or fails for any reason, the automatic upgrade process will be Information Display
disabled. In this case, upgrades can only be carried out by using a DOS bootable USB upgrade
key. This ensures the system is still fully recoverable if an error occurs during the upgrade
process.

To Manually Upgrade the Sensor Software:


The manual upgrade process will not complete if a secondary disk is detected. If the sensor
has a working secondary disk present you should use the automatic upgrade process.
Before you begin the upgrade process you will need to ensure all the upgrade files are saved VGA USB1 USB2 User Push Button 2
into a subdirectory named ‘upgrade’ in the root directory of the DOS bootable USB upgrade
key. You will also need a monitor and keyboard.

! Note: During a manual upgrade the USB upgrade key will be


referred to as drive ‘C:’ and the main rootdisk will be drive ‘D:’
To Automatically Upgrade the Sensor Software:
Before you begin the upgrade process you will need to ensure all the upgrade files are saved
1. Power down the sensor and remove the access plate. Connect a keyboard to USB2 and a into a subdirectory named ‘upgrade’ in the root directory of a USB upgrade key.
monitor to the VGA port. Connect the USB upgrade key to USB1. 1. Power cycle the sensor and press User Push Button 2 when the following message
2. Power up the sensor. appears on the Information Display:
3. When the system has booted into DOS (view the monitor to verify this) press ‘Enter’ Press User BTN2
twice on the keyboard to skip the date and time updates. To Use USB Functions

4. When the ‘C:\>’ prompt appears, create a directory named ‘upgradem’ on the sensor’s 2. Insert the USB upgrade key into USB1 when prompted to do so.
rootdisk by entering the following syntax: C:\>mkdir D:\upgradem 3. Once the ‘upgrade’ directory has been found on the USB key, the Information Display
5. Copy the upgrade files from the ‘upgrade’ directory on the USB key into the ‘upgradem’ will cycle through the filenames of each of the upgrade files in turn, giving you the
directory on the sensor’s rootdisk by entering the following syntax: opportunity to press User Push Button 2 to confirm each file you need to upgrade.
C:\>copy upgrade\*.* D:\upgradem 4. The system will then copy all the files that were ‘confirmed’ in step 3 from the USB
6. Delete the ‘bootload.ini’ file from the sensor’s rootdisk by entering the following syntax: upgrade key onto the sensor’s secondary disk. Progress will be shown on the
C:\>del D:\bootload.ini Information Display.

7. Remove the USB upgrade key and power cycle the sensor. 5. The upgrade will then begin and the system will transfer all the required files from
The sensor will restart and, following some initial messages, the Information Display will the sensor’s secondary disk onto the main rootdisk. Progress will be shown on the
read ‘ini file created’ before progressing on to ‘UPG from Rootdisk’ as the Information Display.
upgrade begins. Further messages will indicate the progress of the update and more 6. When the upgrade is complete the Information Display will prompt you to remove the
detailed updates will be shown on the monitor. USB key. When the key has been removed the sensor will restart and go into normal
8. When the upgrade is complete the sensor will restart and go into normal running mode. running mode.

  66
Upgrade Messages
Below is an alphabetical list of the messages that may appear on the Information Display during a direct manual or automatic upgrade of the sensor software,
with descriptions of their meaning:

Display Screen Message Description


BKUP Dir Created A backup directory has been created on the 2nd disk.
Copy USB file error There was an error while trying to copy the file from USB key to disk.
Error in USB selection An error has occurred.
Failed Create BK Dir The creation of a backup directory in the 2nd disk has failed.
Failed Create UPG Dir The creation of the upgrade directory in the 2nd disk had failed.
Failed cret ini file The creation of an upgrade ini file has failed.
Failed to detect USB The USB key that was inserted can not be detected.
Press User BTN 2 Press User Push Button 2 now if you want to use a USB key to upgrade the system.
For USB Upgrade
Ini file created An upgrade ini file was created.
Loading Navigator... The main navigator application is now being started.
NAVBOOT Vx.yz Navboot (version x.yz) has started. (Navboot controls the upgrade process).
No 2nd Disk detected The second disk used for logging alarms, backing up and logging has not been fitted or cannot be detected.
No UPG files on USB No suitable upgrade files were found in the ‘upgrade’ directory on the USB key.
No USB file accepted You have not confirmed any of the files on the USB key to be upgraded.
Please remove USB!! The upgrade is complete and you should now remove the USB key so that the system can reboot.
Pls insert USB Insert the USB key and wait for it to be detected.
Then wait
Ready to confirm Get ready to confirm which files should be upgraded by pressing User Push Button 2 as they are displayed.
Use user input BTN2
Rebooting... The sensor is about to restart.
Start upgrading The transfer of the upgrade files to the sensor rootdisk is about to start.
UPG DIR Created The temporary ‘upgrade’ directory on the 2nd disk has been created.
UPG error occurred An error has occurred while upgrading to one of the system components.
UPG from Rootdisk A manual upgrade from the root disk is in progress.
Upgrade abandoned The upgrade process has been stopped because the same component has failed to upgrade a number of times.
Please remove USB!!
Upgrade DIR found An ‘upgrade’ folder has been found on the USB key.

  67
Upgrade Messages (Continued)
Below is an alphabetical list of the messages that may appear on the Information Display during a direct manual or automatic upgrade of the sensor software,
with descriptions of their meaning:

Display Screen Message Description


Upgrade DIR not found No ‘upgrade’ folder could be found on the USB key.
Upload failed The file failed to upload correctly.
USB Upd not selected You have not chosen to upgrade via USB.
USB upg not allowed When no 2nd disk is present the USB upgrade cannot be done automatically from USB key - it must be done manually.
USBx is detected A USB Key has been detected with drive letter shown in x.
Writing revision error Navboot could not write its version information to disk.

  68
Diagnostics
The sensor connector board includes two user push buttons, which can be used in
conjunction with the Information Display to access a set of test functions for diagnostics.

!
Note: The diagnostic tests can be run during normal operation of the sensor. This can
be useful for viewing live data but should be carried out with caution as some tests can
interfere with the normal operation of the unit.

Information Display To Access the Diagnostic Menu:


The diagnostic menu can be accessed by power cycling the system and holding down
User Push Button 2 User Push Button 1 while the system restarts, until the diagnostic menu is displayed.
The top line of the Information Display will show the selected menu, and the second line
will cycle through the available options (tests or sub-menu options) as User Push Button 1 is
pressed. See The Diagnostics Menu on page 70for a breakdown of the diagnostic menu.
User Push Button 1

!
Sensor Connector Board Note: During normal operation of the sensor the Navigator will write messages to
the Information Display and these will overwrite the diagnostic information. You can
re-display the diagnostic menu by pressing User Push Button 2.

To Select an Option from the Diagnostic Menu:


Pressing User Push Button 2 will activate the option that is displayed on the second line of
Line 1 displays the current Menu. the Information Display. This will therefore either run the selected test or descend into a
further sub-menu, according to the option that was activated.

!
Line 2 displays the current Option Note: Some tests will simply display live information but others, such as the motor test,
will start when User Push Button 2 is pressed and will stop when the same button is
pressed again.
Information Display See Diagnostic Test Functions on page 72 for details of the test functions available.

  69
The Diagnostics Menu
Legend
User Push Button 1 User Push Button 2

Diagnostics Diagnostics Diagnostics Diagnostics Diagnostics


Encoder Inputs Outputs VRU IDs
See page 71.

Encoder Inputs Outputs VRU IDs


Count Control Inputs Receiver Power Scaled Bk

IDs
Encoder Inputs Outputs VRU Cn
Fault Hardware code ETX Reset Raw

IDs
Encoder Inputs Outputs VRU View En
Position Spare1 Loopback View X Tilt

IDs
Encoder Inputs Outputs VRU Y Tilt Ct
Exit ISO_5V Gyro Test 1 Exit Rolls
Pitch
Yaw IDs
X Acc BkCnEnCt
Exit Encoder Inputs Outputs Exit VRU Y Acc
Return to Diagnostics Heater Gyro Test 2 Return to Diagnostics Z Acc
IDs
Exit
Inputs Outputs View
Serial 0 Exit Exit
Exit IDs
Return to Diagnostics
Inputs Exit Outputs Exit View
Serial 1 Return to Diagnostics Return to VRU

Inputs
Exit

Exit Inputs
Return to Diagnostics

  70
The Diagnostics Menu (Continued)
Diagnostics Diagnostics Diagnostics Diagnostics Diagnostics Diagnostics
System History Calibration Com1&2 Loopback Ethernet Exit
Continued from
page 70.
System History Calibration The loopback will Ethernet
Exit Diagnostics
S/N Total Events Zero Yaw timeout after 2 minutes CS:
and
return to Diagnostics.

System History Calibration Ethernet


Ctrl Temp Clear Exit DP:

System History Exit Calibration Ethernet


Rec Temp Exit Return to Diagnostics
MGrp:

System Exit Outputs Ethernet


EtxAmb Temp Return to Diagnostics
Exit

System Exit Ethernet


EtxCPU Temp Return to Diagnostics Diagnostics
Clear
Motor
Press B2 to clear

System Info
CtrlBoot Info Version Motor
Clear
Low
Exit

System Info
CtrlApp Info Cmp Date Exit Clear
Motor
Return to History High

System Info
RecBoot Info Cmp Time Motor
Exit

System Info
Exit Motor
RecApp Info Exit Return to Diagnostics

System Exit Info


NavBoot Info Return to System

System
NavApp Info

System
Legend
Exit
User Push Button 1 User Push Button 2

Exit System Only available when the receiver is operational and the navigator is available.
Return to Diagnostics
Only available when the navigator is operational.

  71
Diagnostic Test Functions

Table 1
Test Function Description Test Function Description
Encoder Yaw Displays either the Valid or Alarm status and the yaw value.
Count Displays the encoder count when the marker was received. Tm is the X Acc Displays either the Valid or Alarm status and the X accelerometer value.
time between markers. Y Acc Displays either the Valid or Alarm status and the Y accelerometer value.
Faults Displays the number of marker faults (when the encoder count is not Z Acc Displays either the Valid or Alarm status and the Z accelerometer value.
equal to 512). Tm is the time between markers.
IDs
Position Displays the current encoder count.
Bk Displays the backplane board 8 digit ID code.
Inputs
Cn Displays the connector board ID.
Control Inputs Displays the bit pattern of the control input connected to the controller.
En Displays the encoder ID.
Hardware code Displays the hardware revision of the connector board.
Ct Displays the controller (connector board) ID.
Spare1 Displays the value on the spare input (either H or L).
BkCnEnCt Displays the input states of the ID chips io pins.
ISO_5V Displays the state of the isolated 5V on the connector board (OK or FAIL).
System
Heater Displays the state of the heater output.
S/N Displays the serial number of the unit, stored in the system memory.
Serial 0 Displays the configuration of serial port 0, either RS232 or RS422.
Ctrl Temp Displays the temperature measured at the controller.
Serial 1 Displays the configuration of serial port 1, either RS232 or RS422.
Rec Temp Displays the temperature measured at the receiver board.
Outputs Displays the current state of the output and toggles it when User Push
Button 2 is pressed. EtxAmb Temp Displays the temperature measured at the ETX board.

Receiver Power Turns the power to the receiver on or off. EtxCPU Temp Displays the temperature of the ETX CPU.

ETX Reset Allows the ETX to be reset. See Table 2 on page 73 for details on the remaining system menu options...

Loopback Loopback on the connector board. History

Gyro Test 1 Toggles the gyro self test line 1. Total Events Displays the total number of recorded system events.

Gyro Test 2 Toggles the gyro self test line 2. Clear Sub-menu to clear service history.

VRU History>Clear Pressing User Push Button 2 will clear all service history events.

Scaled Turns the VRU scaled mode on or off. Calibration

Raw Turns the VRU raw mode on or off. Zero Yaw Performs an auto zero on the Yaw sensor.

View Sub-menu. Com1&2 This test links the two serial ports (com 1&2) together so an external
Loopback program can be used to perform a loopback test. Once started the
VRU>View loopback will timeout after 2 minutes and return to Diagnostics.
X Tilt Displays either the Valid or Alarm status and the X tilt value. Ethernet
Y Tilt Displays either the Valid or Alarm status and the Y tilt value. CS: Displays the IP address of the sensor for the console link.
Roll Displays either the Valid or Alarm status and the roll value. DP: Displays the IP address of the sensor for the DP link.
Pitch Displays either the Valid or Alarm status and the pitch value. MGrp: Displays the group that the console is using for Multicast.

  72
Diagnostic Test Functions (Continued)

Table 1 (Continued)
Test Function Description
Motor
Low Runs the motor at 60rpm until User Push Button 2 is pressed.
High Runs the motor at 120rpm until User Push Button 2 is pressed.
Exit Pressing User Push Button 2 will exit the diagnostic menu.

Table 2
Test Function Description
System (Continued from Table 1)
CtrlBoot Info Refer to Table 3 below.
CtrlApp Info Refer to Table 3 below.
RecBoot Info Refer to Table 3 below.
RecApp Info Refer to Table 3 below.
NavBoot Info Refer to Table 3 below.
NavApp Info Refer to Table 3 below.

Table 3
Test Function Description
Info
Version Software version of the component selected on the System menu.
Cmp Date Displays the date the software compiled.
Cmp Time Displays the time the software was compiled.

  73
Index
A
A and B Axes 52
Access Plate 8
Additional Configuration Categories 36
A Pos and B Pos 52
Armoured Cable 17
Artemis Mk IV 54
ASCII17 54

B
Banner
Day View 31
Night View 31
Base Plate 8
Bearing Offset 40
BKUP Dir Created 67
Blanking Zone
Create 42
Show/Hide 42
Blanking Zones 42
‘Boot fail, resetting’ 63
Bow and Starboard Axes 52
Bow and Starboard Offsets 40
Bow Orientation 38
BRUSH_ 31

  74
Index (Continued)
C
c4colour.ini 27 Tab 36 Custom Colour Scheme 32
Opening 36
c4config.ini 25, 31 Cylindrical Targets 50
Utility
Cable 17 ConnCfg 55 CyScan
Connections 19 Sensor Connectivity 55 Button 43, 46, 48
Glands 9 ConnCfg Utility 45, 55 Console 7
Routing Diagrams 61 Installing 26
Main Window 55
Specifications 17 Uninstalling 26
connect.ini 45 Sensor 7
Calibration 72
connect.ini File 45, 55 Sensor Part Names 8
Exit 71
Edit Existing 56 Targets 7
Zero Yaw 71
Generate New 56 ‘CyScan Boot Failed power cycle to retry’ 63
‘Checking components’ 63 Typical Contents 56
Checklist Connections
Console Configuration 59 Console PC 23
Functional Tests 60 DP Feed 20
Initial Log File 60 Ethernet Sensor 20, 21
Installation 59 Power 19
Mechanical Installation 59 Sensor 19
Sensor Connections 59 Serial Sensor 22
Sensor Software Updates 59
Connection Tests 60
System Interference Tests 60
Training 60 Console 8, 9
Network 45
Cmp Date 73
Options 38
Cmp Time 73 Software 26
COLOUR_ 31 Installing/Uninstalling 26
Colour Scheme Configuration File 31 Console PC
Colour Schemes 27 Connections 23
Com1&2 Loopback 72 Dimensions 15

Communications / Display Options 38 Coordinate Frame Axes 52


Communications (Ethernet Sensor) 46 Copy USB file error 67
Helpful points 46 CS: 72
Troubleshooting 46 CtrlApp Info 73
Communications (Serial Sensor) 48 ‘CTRLAPP not found’ 63
Configuration CtrlBoot Info 73
Categories 36 ‘CTRLBOOT V1.02’ 63
Options 36 CTRLBOOT V1.04 11
Settings 36
custom 28, 31
  75
Index (Continued)
D
Data Cable 17 DP: 72 Ether1 56
Datalog Options 38 DP Clients List 56 Ethernet 72
Date and Time 33 Remove 56 Connection 17
day 28 Remove All 56 CS: 71
DP Feed 8, 9, 20 DP: 71
DayBannerPath 28
Behaviour 39 Exit 71
day_standard 28 Link 17
Connections 20
Day View 27, 37 Format MGRP: 71
DCHP 46 Setting 37 Ethernet Sensor
default 28, 31 Format & Message String 37 Communications 46
Default Network Settings 45 DP Message Connections 20, 21
Diagnostic exit 63 To Monitor 57 ‘ETX booted OK’ 63
Types 53 ETX booted OK 11
Diagnostics 69
Accessing 69 DP Monitor ETX in BIOS SETUP 63
Calibration 71 Layout 57
‘ETX Missing OS/Disk’ 63
Com1&2 Loopback 71 Utility 57
Exit (diagnostic menu) 73
Encoder 70 DP Server
Ethernet 71 IP Address 45 F
Exit 71 Network 45
History 71 Failed 63
IDs 70
E Failed Create BK Dir 67
Inputs 70 E-mail 2 Failed Create UPG Dir 67
Menu 70 Failed cret ini file 67
Encoder 72
Motor 71
Count 70, 72 Failed to detect USB 67
Outputs 70
Exit 70 ‘Failed to initialise Receiver’ 63
Selecting Options 69
Fault 70 ‘Failed to start rotor’ 63
System 71
Faults 72
VRU 70 ‘Failed to suspend rotor’ 63
Position 70, 72
Diagnostic Test Functions 72 Fax Number 2
Error in USB selection 67
Display Ferrite 19
‘Err writing sw event’ 63
Options 37 Flat Targets 50
Button 42, 52 Ether0 56
Menu 52
Screen 8
Download timed out 63
DP 52

  76
Index (Continued)
G M
Gateway 45, 56 Inputs 72 Manual Logging
General Settings / Version Info 37 Control Inputs 70, 72 Starting/Stopping 43
‘Going to running’ 63 Exit 70 Marine PC 23
Hardware Code 70, 72 MDL
‘Going to suspend’ 63
Heater 70, 72 Multi-Target 54
H ISO_5V 70, 72 Standard 54
Serial 0 70
Message Server IP 57
History 72 Serial 1 70
Clear 71, 72 Spare 1 70, 72 MGRP: 72
Exit 71 Installing Monitored UDP Port 57
Total Events 71, 72 CyScan Console 26 Motor 73
History>Clear IP Address 56 Exit 71
Exit 71 DP Server 45 High 71, 73
Press B2 to clear 71, 72 Low 71, 73
K Mounting
I Locations 13
Kongsberg Template 14
IDs 72 Standard 54
Msi File 26
Bk 70, 72
BkCnEnCt 70, 72 L Multicast Group 56
Cn 70, 72
Ct 70, 72 ‘Last POST code nn’ 63
En 70, 72 Last POST code NN 11
Exit 70 Loading Navigator... 11, 67
Info 73 Local IP 57
Cmp Date 71 Log File 43
Cmp Time 71 Creation 43
Exit 71 ‘Low Temperature’ 63
Version 71
Information Display 8, 69
Ini file created 67

  77
Index (Continued)
N P R
Nautronix Part Numbers 10, 58 Range & Bearing Only 37, 52
Standard 54 Cables 17 Range Licence 41
NavApp 73 Cylindrical Target 50 Ready to confirm 67
NavBoot 73 Flat Target 50
Rebooting... 67
Prism Target 50
NAVBOOT V1.60 11 RecApp 73
PEN_ 31
NAVBOOT Vx.yz 67 RecBoot 73
Please remove USB!! 67
Netmask 45, 56 ‘Receiver Fatal Error’ 64
Pls insert USB 67
New Node IP 55 Reflective Targets 58
Positional Display Mode 52
night 28 registry 28, 31
Change 52
NightBannerPath 28 Reserved IP Addresses 46
Power 8, 9
night_green 29 Cable 17 Reset Communication 46, 48
night_orange 30 Connections 19 Resetting 64
Night View 27, 37 ‘power cycle to retry’ 63 Rotor 8
NMEA0183P 52, 53 ‘Power Fail’ 63 ‘Running’ 64
NMEA0183R 52, 53 Press User BTN 2 67 Running 11
No 2nd Disk detected 67 Press User BTN2 To Use USB Functions 11
No UPG files on USB 67 Prism
No USB file accepted 67 Targets 50
Product Label 10
O
Program failed CRC 63
On-Screen Keyboard 34, 38 Programming 63
Optical Window 8 Programming complete 64
Optional Components 58
Outputs 72
ETX Reset 70, 72
Exit 70
Gyro Test 1 70, 72
Gyro Test 2 70, 72
Loopback 70, 72
Receiver Power 70, 72

  78
Index (Continued)
S U
Sensor startup 28, 31 UDP 57
Clearance 14 Start upgrading 67 Uninstalling
Connections 19 ‘Suspended’ 64 CyScan Console 26
Connectivity SYSCOLOR_ 31 ‘Updating Blanking Zn’ 64
Configuration Utility 55
Connector Board 69 System 72, 73 ‘Updating receiver’ 64
Dimensions 14 CtrlApp Info 71 UPG DIR Created 67
IP Address 45 CtrlBoot Info 71 UPG error occurred 67
Multicast Group Number 45 Ctrl Temp 71, 72
UPG from Rootdisk 67
Part Names 8 EtxAmb Temp 71, 72
EtxCPU Temp 71, 72 Upgrade
Upgrade 65, 66 Sensor 66
Exit 71
Sensor Information Display 11 Upgrade abandoned 67
NavApp Info 71
Error Messages 63
NavBoot Info 71 Upgrade DIR found 67
Sensor Operations RecApp Info 71 Upgrade DIR not found 68
Button 34, 35, 36, 37, 38, 40, 42, 43 RecBoot Info 71 Upload failed 68
Sensor Software Upgrade Rec Temp 71, 72
Automatic 66 UPS Specifications 18
S/N 71, 72
Manual 66 USB is not selected 11
System Logging 43
Serial 72 USB Upd not selected 68
Serial 0 20, 72 T USB upg not allowed 68
Serial 1 20 USBx is detected 68
Target
Serial Numbers 10 Cylindrical 50
User Datagram Protocol 57
Serial Sensor Flat 50 User Push Button 1 69
Connections 22 Positioning and Mounting 51 User Push Button 2 69
Serial Version 11 Prism 50 UV 17
Service Access 35 Types 50
Code 35 Telephone Number 2
Shielded 17 Troubleshooting
Signal Wiring 17 Communications, Ethernet 46
Software Versions 10
Standard Components 58
‘Starting application’ 64
Starting application 11
‘Starting motor’ 64
‘Starting receiver’ 64
Starting receiver... 11
  79
Index (Continued)
V
Version 73
Vessel Parameters / File Transfer 40
VRU 72
Exit 70
Raw 70, 72
Scaled 70, 72
View 70, 72
VRU>View 72
Exit 70
Pitch 70, 72
Roll 70, 72
X Acc 70, 72
X Tilt 70, 72
Y Acc 70, 72
Yaw 70, 72
Y Tilt 70, 72
Z Acc 70, 72

W
Waiting for command 64
‘Warming up system’ 63
Writing page nn 64
Writing revision error 68

Z
Zero Yaw 72

  80
Document History

Document Number Changes Issue Date


94-0085-4 First release 26th March 2010

  81