Professional Documents
Culture Documents
SeaDarQ V 4 Installation and Maintenance Guide (Draft 4b)
SeaDarQ V 4 Installation and Maintenance Guide (Draft 4b)
SeaDarQ v 4
Oil Spill Detection
identification data
documentation title
SeaDarQ v 4 Installation and Maintenance Guide
documentation version
3.0 draft 4b DRAFT
publication date
08-jan-2015
software product
SeaDarQ
software product version
v 4.0
issuing organization
Nortek BV
1
DRAFT
Detailed Contents
I Introduction ........................................................................................................................6
1 Introduction ..........................................................................................................................6
1.1 Overview ............................................................................................................................................6
1.2 Purpose ..............................................................................................................................................6
1.3 Assumptions and scope ..................................................................................................................... 6
II Installation and configuration ...........................................................................................9
1 System overview ..................................................................................................................9
2 System components.......................................................................................................... 10
2.1 PC .................................................................................................................................................... 11
2.2 RNI ................................................................................................................................................... 12
3 Required / recommended tools ......................................................................................... 13
4 Physical Hardware installation .......................................................................................... 14
5 System cabling and connections ...................................................................................... 15
5.1 Introduction ...................................................................................................................................... 15
5.1.1 Overview ......................................................................................................................................... 15
5.1.2 Assumptions.................................................................................................................................... 15
5.1.3 Scope .............................................................................................................................................. 15
5.2 General description .......................................................................................................................... 15
5.3 PC and RNI ...................................................................................................................................... 17
5.4 Cabling requirements for a “generic” radar ...................................................................................... 19
5.4.1 Radar subsystem cabling ................................................................................................................ 19
5.4.2 Radar – RNI connection .................................................................................................................. 19
5.4.3 RNI – PC connection....................................................................................................................... 19
5.4.4 Wiring details “generic” radar .......................................................................................................... 20
5.5 Cabling requirements with a GEM radar .......................................................................................... 21
5.5.1 GEM subsystem cabling ................................................................................................................. 21
5.5.2 GEM radar – RNI cabling ................................................................................................................ 22
5.5.3 RNI – PC cabling............................................................................................................................. 22
5.5.4 GEM – PC cabling........................................................................................................................... 22
5.6 Cabling requirements with a Sperry radar ........................................................................................ 23
5.6.1 Sperry – RNI cabling ....................................................................................................................... 23
5.6.2 RNI – PC cabling............................................................................................................................. 24
5.6.3 SeaDarQ in slave configuration with a Sperry radar ....................................................................... 25
5.7 Cabling requirements with a Terma radar ........................................................................................ 26
5.7.1 Terma radar – RNI .......................................................................................................................... 26
5.7.2 RNI – PC cabling............................................................................................................................. 26
5.8 NMEA device connections to the RNI .............................................................................................. 28
6 RNI and Hardware configuration ....................................................................................... 29
6.1 Overview .......................................................................................................................................... 29
6.2 Device drivers .................................................................................................................................. 29
6.3 RNI Configurator .............................................................................................................................. 30
6.4 Radar type selection ........................................................................................................................ 30
6.5 GEM radar tuning procedure ............................................................................................................ 31
6.6 Sperry radar tuning procedure ......................................................................................................... 34
6.6.1 Sperry radar tuning procedure from within RNI Configurator .......................................................... 34
6.6.2 Sperry radar tuning procedure from within SeaDarQ 4 ................................................................... 35
6.7 RNI Configuration with SeaDarQ v 4.x ............................................................................................. 37
6.7.1 Settings in SeaDarQ ....................................................................................................................... 37
6.7.2 RNI signal level adjustment and Device Driver settings .................................................................. 37
6.7.3 NMEA Configuration ....................................................................................................................... 44
6.8 SeaDarQ software configuration ...................................................................................................... 46
6.8.1 general settings ............................................................................................................................... 46
6.9 Other issues ..................................................................................................................................... 46
6.9.1 GEM radar ...................................................................................................................................... 46
7 Software Update Installation ............................................................................................. 47
DRAFT
I Introduction
1 INTRODUCTION
1.1 Overview
This Technical Manual contains:
Installation and configuration
o System overview
o System components
o Required / recommended tools
o Physical Hardware installation
o System cabling and connections
o RNI and Hardware configuration
o Software configuration
Service and maintenance
o SeaDarQ PC and RNI
o Radar subsystem
Troubleshooting
o General approach
o Some symptoms and tests
o Troubleshooting styles
1.2 Purpose
The Purpose of this Installation and Maintenance Guide is to describe how to install and configure a SeaDarQ
Oil Spill Detection system. It focusses on the SeaDarQ PC and the SeaDarQ Radar NMEA Interface (RNI).
Table 1.1: SeaDarQ PC and RNI details (greyed-out items are not considered in this guide).
PC v4 motherboard X7DCAi
SeaDarQ 2.3.10 [ / X7DAE / X7DA8]
GaGe card CS 14200
ADDI-Data card APCI-1710
v5 motherboard X9DAi
SeaDarQ 4.0 GaGe card CS 1422 (Razor)
ADDI-Data card 1711
RNI rev 2E generic
rev 2E (b) special version for Sperry
(DIN5 power connector)
rev 4.0 special connectors for
Sperry, GEM/Terma
Table 1.3: Requirements for a generic radar, in order to connect it to a SeaDarQ system (PC & RNI)
aspect requirements remarks
video max range +5 V .. – 5 V minimum amplitude (top-top) about 0.5 V
trigger (sync) max range +15 V .. – 15 V minimum amplitude about 0.5 V
azimuth (ACP/bearing) max range +15 V .. – 15 V — " —; at least 60 to 90 pulses per rotation
north reset (ARP / heading) max range +15 V .. – 15 V —"—
radar pulse length short, 50 - 80 ns
PRF < 2000 Hz (1)
no clutter-suppression no clutter-suppression, or This is crucial !
clutter-suppression switched
off
rotation rate 24 to 48 rpm Faster is better; fast rotation is a must for the
hydrography application
This guide does not go into the details of installing the radar system; for instructions on installing the radar, see
the documentation from the radar manufacturer, or have it installed by radar manufacturer’s personnel.
A note about the RNI: a distinction should be made between RNI hardware versions and RNI firmware versions.
Hardware and firmware version determine compatibility of the RNI with versions of SeaDarQ. The following
table, Table 1.4, shows an overview.
Table 1.4: RNI hardware and firmware version compatibility versus SeaDarQ version number
SeaDarQ version
RNI hardware version RNI firmware version 2.x (– 2.11) 3.0 – 3.x 4.0 – 4.x
2E 2.1 + + –
3.0 3.5 – – +
4.0 (Radar Board) 4.0 – – +
The version 2E hardware can be upgraded to version 3.0 hardware by means of a replacement of the processor
board with a special “compatibility” processor board.
1
Higher radar Pulse Repetition Frequencies can be accommodated by reducing the PRF through the RNI, essentially
skipping some radar lines.
Figure 1.1 shows a schematic overview of the SeaDarQ Oil Spill Detection system and its components.
It consists of several components:
A radar system
itself typically consisting of:
o An antenna
o A turning unit (a.k.a masthead unit, scanner unit)
o A power and control unit
A SeaDarQ RNI unit (Radar – NMEA Interface)
A SeaDarQ PC, running the SeaDarQ Oil Spill Detection software
radar antenna
+
masthead / turning unit
radar power
and SeaDarQ RNI unit
control
SeaDarQ PC
Figure 1.1: Schematic overview of the SeaDarQ system and its components
The radar system is a third-party component. Installation instructions for the radar must be obtained from the
radar manufacturer.
The SeaDarQ RNI and PC are both 19" rack-mounted systems. Dimensions and other specifications are listed in
section II-2, System components.
The cabling and connection instructions, requirements, and details, are presented in section II-5, System cabling
and connections.
2 SYSTEM COMPONENTS
Figures 2.1 and 2.2 show front views of the SeaDarQ RNI and PC.
Section 2.1 gives the important specifications of the SeaDarQ PC, in terms of dimensions and weight.
Section 2.2 gives the important specifications of the SeaDarQ RNI.
For details of the radar system, consult the manufacturer’s documentation.
2.1 PC
The SeaDarQ PC has the following properties:
Dimensions: 4U 19” rackmount PC, 500 mm deep (excluding handles at front, approx. 50mm, and
room for cable connections at the back)
Weight: 22 kg
Power requirements: 650 W
Figure 2.3 shows an outline drawing of the front of the PC, with the most important dimensions in mm.
Figure 2.4 shows an outline drawing of the top of the PC, with the most important dimensions in mm.
483mm (19")
465mm
178mm (4U)
102mm
Figure 2.3: Outline drawing of the SeaDarQ PC (front view)
433mm
500mm
550mm
465mm
483mm
2.2 RNI
The SeaDarQ RNI has the following properties:
Dimensions: 1U 19” rackmount equipment, 500 mm deep (excluding knob at front, approx. 5mm;
including bracket at the back which allows cables to be tied down)
Weight: 6.5 kg
Power requirements: 100 W
Figure 2.5 shows an outline drawing of the front of the RNI, with the most important dimensions in mm.
Figure 2.6 shows an outline drawing of the top of the RNI, with the most important dimensions in mm.
44mm (1U)
483mm (19")
32mm
465mm
440mm
500mm
400mm
465mm
5mm
483mm (19")
Table 3.1: List of required and recommended tools and spares to bring for installation
Tools etc. Tools – useful extras
tool set (screwdrivers, both flat and multimeter
crosshead, pliers, cutters) oscilloscope (with probes, of course)
flashlight signal generator
screwdriver set RS-232 gender-changer ?
wire stripper mains plug-block
soldering iron mains extension lead
solder laptop
de-soldering braid RS-232 – RS422 converter
wires straight-through RS-232 cable
tape measure
coax wire stripper
coax crimper spare GaGe card
camera spare ADDI-Data card
(small) tie wraps
grounding eyelet (Sperry)
heat-shrink tubing
5.1.1 Overview
These sections describe the cabling and connections that are required to connect the sub-systems that make up a
SeaDarQ Oil Spill Detection system.
5.1.2 Assumptions
The description assumes that the system was ordered with information about the radar sub-system to be used, or
even with the radar sub-system as part of the order. In the latter case, the required cables are supplied with the
full system. Note that the cables to go from radar to RNI are considered part of the radar.
5.1.3 Scope
Generally speaking, the radar sub-system is a third-party self-contained system. For cabling details of the radar
sub-system, refer to the manufacturer’s instructions.
Only for a limited number of specific radar systems does this guide provide more detailed information:
The GEM radar (section II-5.5)
A Sperry radar (section II-5.6)
A Terma radar (section II-5.7)
radar
RNI
SeaDarQ ADDI-
PC Data GaGe
1711 1422
video in
trigger in
power USB
Figure 5.1: General overview of connections between radar, RNI, and PC.
The SeaDarQ Oil Spill Detection system also makes use of certain NMEA sources, in particular GPS and gyro.
NMEA connections are made to the RNI; connection details are provided in section II-5.8.
The SeaDarQ PC needs the following signals from the radar:
Video
Trigger
Azimuth change pulse (ACP, a.k.a. bearing)
Azimuth reset pulse (ARP, a.k.a. north reset or heading line)
The SeaDarQ RNI (Radar NMEA Interface) sits in between the radar signals and the PC acquisition cards. The
RNI provides adjustable signal conditioning for the incoming signals, allowing them to be converted to the input
ranges of the acquisition cards. Figure 5.1 sketches this general arrangement. Section II-5.4 describes the
connections that need to be made for this general situation.
To assist in troubleshooting, detailed schematics of various cables required in specific cases, are provided as an
addendum. For installation, these detailed cable schematics should not be necessary.
Some manufacturers use different names for ACP and ARP signals; table 5.1 lists some variations and
abbreviations.
Table 5.1: Alternative signal names for North Reset and Azimuth
North Reset NR ARP Azimuth Reset Pulse, Heading Marker,
Azimuth Reference Pulse Heading Line
Azimuth AZ ACP Azimuth Change Pulse Bearing
video in
ADDI Data
APCI 1711
Trigger in
GaGe Razor
CS 1422
Table 5.2: Description of the connectors on the back of the RNI unit
RNI socket label signal description
ARP in single-ended north reset signal from the radar system
ACP in single-ended azimuth signal from the radar system
trigger in trigger signal from the radar system
trigger out TTL trigger signal to the SeaDarQ PC (GaGe card trigger in)
video in video signal from the radar system
video through video out signal; not used
Figure 5.4: Connection schematic for PC, RNI and either GEM or Terma radar
radar
RNI
SeaDarQ
PC
video in
trigger in
the 9-pin “ACP, ARP out” connector on the back of the RNI. With the RNI rev 3.5, this connection and its
wiring details are the same for all radar brands and models. The cable is provided with the SeaDarQ system. As
an aid to possible troubleshooting, subsection II-5.4.4, “Wiring details “generic” radar”, figure 5.6 and
table 5.3, provide the wiring details for this cable.
For communication and control, the RNI and PC also need a standard USB cable connection (with a type A
connector on the PC side, and a type B connector on the RNI side). Always use the bottom USB connection of
the stack of 4 at the back of the PC, otherwise Windows will not recognize the RNI from the factory
configuration and tests, and will insist on reinstalling a device driver for it.
Figure 5.6: Wiring details for the general-case connection between SeaDarQ RNI unit and SeaDarQ PC
Table 5.3: Connection details for the SeaDarQ RNI unit, both to the radar (RNI in) and to the SeaDarQ PC (RNI
out)
DB-78 DB-78
connector PC DB-9 DB-9 connector PC
(ADDI-Data connector connector (ADDI-Data
signal card) RNI signal RNI card)
NR+ / ARP+ 2 7 ACP+ (AZ+) 1 60
NR– / ARP– 3 8 ACP– (AZ–) 2 61
AZ+ / ACP+ 60 1 ARP+ (NR+) 7 2
AZ– / ACP– 61 2 ARP– (NR–) 8 3
radar
GEM
ASU-43000 J01
J03 J05 J06 J07
J02
RNI
SeaDarQ
PC
video in
trigger in
Scanner Unit SU74-01 (SU74-02)”. The GEM Cable Running Sheet “TINPFS99111” gives signal-to-pin
assignments for the various connectors on their power supply unit, ASU-43000.
Connect the CB36 cable between the radar Scanner Unit SU74-06 and the power supply unit ASU-43000. For
details, see the GEM document “CB36 Cable Setting-up Procedure Side Scanner Unit SU74-01 (SU74-02)”.
Table 5.4: Video (and trigger) cables between GEM and RNI
signal ASU connector RNI connector cable
socket nr type socket type type
video J06 BNC video in BNC RG-59
trigger J05 BNC trigger in BNC RG-59
ACP
J03 DB-9 ACP, ARP in DB-9 serial
ARP
radar
(video)
RNI
SeaDarQ
PC
video in
trigger in
Table 5.5: Description of the 8-wire connection between Sperry radar and SeaDarQ RNI
pin nr signal description Sperry TSB number & wire colour wire colour
signal description (standard cable) (low smoke zero
halogen cable)
10 – N/C
9 – N/C
1 N/C 8 TX SART - white/brown black
2 N/C 7 TX SART + brown/white white
3 Trigger- 6 TX TRIG - white/green black
4 Trigger+ 5 TX TRIG + green/white green
5 DataIn- 4 TX DATA - white/orange black
6 DataIn+ 3 TX DATA + orange/white red
7 DataOut- 2 DU DATA - white/blue black
8 DataOut+ 1 DU DATA + blue/white blue
radar
mains power
slave Sperry
junction Vision
box Master
Display
(video)
RNI
SeaDarQ
PC
video in
trigger in
Figure 5.9: Subsystem components and connections with a Sperry radar system, with SeaDarQ in slave
configuration
Note that the tuning procedure for the Sperry radar as described in section 6.6 cannot be performed from within
SeaDarQ or the RNI Configurator software in this configuration, so Sperry personnel will have to perform it
from the Sperry console.
radar
RNI
SeaDarQ
PC
video in
trigger in
Figure 5.10: Subsystem components and connections with a Terma radar system
The Terma radar subsystem, like the GEM radar subsystem, provides the North Reset and Azimuth signals as
differential signals. The Terma radar system, too, makes the relevant signals available on a 9-pin Sub-D
connector. The wiring details, however, differ.
Any connections between the components that make up the Terma radar system, are to be made by Terma
personnel or qualified contractors.
Connect the Azimuth (ACP) and North Reset (ARP) signals by means of the special cable assembly, with a DB-
78 plug on one end to connect to the ADDI-Data 1711 card, and a DB-9 (M) plug on the other end to connect to
the 9-pin “ACP, ARP out” connector on the back of the RNI. With the RNI rev 3.5, this connection and its
wiring details are the same for all radar brands and models. The cable is provided with the SeaDarQ system. As
an aid to possible troubleshooting, subsection II-5.4.4, “Wiring details “generic” radar”, figure 5.6 and
table 5.3, provide the wiring details for this cable.
For communication and control, the RNI and PC also need a standard USB cable connection (with a type A
connector on the PC side, and a type B connector on the RNI side). Always use the bottom USB connection of
the stack of 4 at the back of the PC, otherwise Windows will not recognize the RNI from the factory
configuration and tests, and will insist on reinstalling a device driver for it.
Figure 5.11: Schematic of the RNI NMEA signal connections (view from top of RNI)
For wiring details of the NMEA devices to be connected, such as GPS and Gyro, consult the documentation of
those devices.
Note that the NMEA connections on the RNI can be configured in software for RS-232 or RS-422 type signals,
and can also be configured for different baud rates. The “RNI Configurator” software allows for adjustment of
these (and some other) configuration details; see appendix V-4 for details. Figure 5.12 shows a screenshot of a
NMEA port configuration tab in the RNI Configurator software.
Figure 6.1: Device Driver window for the ADDI- Figure 6.2: Device Driver window for the GaGe PCIe
Data 1711 PCI Angular Encoder card Razor CompuScope card (aka GaGe CS 1422)
Figure 6.3: RNI Configurator window (trigger tab, trigger mode manual)
AFC/MANUAL button to switch between automatic tuning (AFC) and for normal operation,
manual tuning select AFC
Figure 6.6: The Sperry BridgeMaster E radar controller tab in RNI Configurator
Figure 6.6 shows the Sperry BridgeMaster E radar controller tab in RNI Configurator, which contains all the
controls and indicators relevant for this task.
For details on the use of RNI Configurator, see appendix V-4. In particular, be aware that the RNI Configurator
program and the SeaDarQ 4 program itself can both control the radar via the RNI. However, they should not try
to control the radar at the same time, as this will lead to timing errors. So when performing this procedure from
within RNI Configurator, make sure that the SeaDarQ 4 program is not running.
After enabling radar control from RNI Configurator, switching on power to the radar, waiting for the radar to go
through the warm-up sequence, and starting transmitting, switch the Automatic Frequency Control (AFC) off (by
ticking the box). (Keep the Pulse length setting on Short.)
Start with the “Fine” slider in the center of its range
Gently move the “Coarse” slider to find the position where the video signal reaches maximum
amplitude, as indicated on the “Tune” indicator
Leaving the “Coarse” slider in its position of maximum tuning, gently move the “Fine” slider to further
maximize the video signal, as judged from the “Tune” indicator
When you have adjusted the “Coarse” and “Fine” sliders for maximum signal amplitude, switch AFC back on
(by un-ticking the box) and allow the automatic frequency control to further maximize the signal amplitude for a
second or 10.
After completing the adjustment procedure, make sure to store the settings in the RNI EEPROM (tab
“Miscellaneous”, button “Save Settings”).
If you subsequently want to start the SeaDarQ 4 program with RNI Configurator still running as well, make sure
to un-tick the box “Enable Radar Control”, in order to avoid conflicts and timing errors due to SeaDarQ and RNI
Configurator attempting to control the radar via the RNI at the same time.
Radar Control
panel
Figure 6.7: The Radar Control panel withing the SeaDarQ 4 main window
All controls and indicators relevant for this task are contained in the Radar Control panel, which is indicated in
figure 6.7. (This panel will only be present if the presence of a Sperry BridgeMaster E radar was detected.)
As mentioned elsewhere, make sure that SeaDarQ 4 and RNI Configurator
do not attempt to control the radar ate the same time, as this will lead to
clashes. If RNI Configurator is open at the same time as SeaDarQ 4, make
sure the box “Enable Radar Control” in RNI Configurator, on the Radar
Controller tab, is not ticked. It is preferable to not have RNI Configurator
running when running the SeaDarQ 4 main program.
To perform all of the tasks below, make sure SeaDarQ 4 has “Advanced
features” enabled (otherwise one of the adjustment sliders will not be
available).
Figure 6.8 (a) through (e) shows the on-screen controls in the Radar Control
panel, as they are changed through-out the procedure. (a) Power off
The procedure consists of the following steps:
From within SeaDarQ 4, switch on power to the radar
Wait for the radar to go through its warm-up sequence
When the warm-up sequence is finished, the radar will go into
stand-by mode; once this has happened, you can change it to
transmit mode
Change the AFC mode from “Automatic” to “Manual”
Start with the “Fine” slider in the center of its range
Gently move the “Coarse” slider to find the position where the
video signal reaches maximum amplitude, as indicated on the
“Tune” indicator (b) Power on, warming-up
Leaving the “Coarse” slider in its position of maximum tuning,
gently move the “Fine” slider to further maximize the video signal, Figure 6.8: On-screen controls
as judged from the “Tune” indicator in the Radar Control panel in
the SeaDarQ 4 program.
(c) Power on, warm-up completed, (d) Switched from Standby to (e) AFC switched from Automatic
in stand-by mode Transmit mode, AFC on Automatic to Manual
Figure 6.8: On-screen controls in the Radar Control panel in the SeaDarQ 4 program. (cont’d)
When you have adjusted the “Coarse” and “Fine” sliders for maximum signal amplitude, switch AFC back to
“Automatic” and allow the automatic frequency control to further maximize the signal amplitude for a second
or 10.
Note that the settings should be saved to the RNIs EEPROM, in order to survive a power-off of the RNI. This can
be done either through the RNI Configurator program (the button “Save Settings” on the “Miscellaneous” tab),
or via the RNI front panel (using the RNI front panel display and selection dial; see section V-4.5).
Values for the number of angular encoder pulses per rotation for known radar systems:
GEM: 4096
Terma: 4096
Sperry: 90 or sometimes 360 (check radar documentation)
ARP: tARP ms
ACP: fACP Hz
PRF: fPRF Hz
0V 0V
-1V
Figure 6.11: Illustration of the concept behind input offset, output offset, and gain
Be aware of the video polarity. Usually, it is necessary to tick the box “Invert video” in the “Processing
Parameters” screen (or in the GaGe CS14200 driver). Trying the procedure below with the wrong video polarity
will be very confusing, and in the end will have to be done again with the correct video polarity.
If the GaGe card is not connected, make sure to use a 50 Ω termination resistor on the oscilloscope channel.
If not using an oscilloscope, certain elements of SeaDarQ itself can be used in this adjustment process.
a. First of all, in SeaDarQ, switch on Configuration ► Enable Advanced Options; this will switch on the
“Tuning” option in the on-screen controls. Change “Tuning” from “Auto” (the default) to “Off”, and switch
off the automatic range correction (see section II-6.7.1)
b. Switch on the “Line” and “Histogram” windows of SeaDarQ (accessible via the “View” menu, or the two
leftmost buttons in the button bar).
c. Using RNI Configurator (with “Advanced” options enabled in the “View” menu), on the Video tab, first
adjust the “Output Offset” in order to map the 0 V radar video signal to the +1 V GaGe card input level. Do
this by setting the RNI video gain to 0%, and adjusting the “Output Offset” slider until the blue signal level
indication in the SeaDarQ “Line” (or “Range Correction Curve”) window shows only just at the 0 level.
d. Still using RNI Configurator, adjust the “Input Offset” slider on the Video tab in order to shift the “blank”
level of the radar video signal (i.e., its maximum voltage level) to 0 V.
This can be checked indirectly in SeaDarQ: when varying the gain in RNI Configurator, the base level (see
c.) should not move.
e. Finally, adjust the “Gain” slider until the RNI Video Output signal ranges to no more negative than -1 V.
If all adjustments have been made
correctly, the video signal in the
SeaDarQ “Line” window should
range from 0 to 100, without clipping
at either extreme. (A little clipping
near the radar is admissible, say
several tens of meters with the radar
range set to 3 km.)
Figure 6.18: Adjust input offset until gain adjustment no Figure 6.19: Signals after final adjustments
longer causes a base level shift
“Setup …”, tab “Processing Parameters”. In this screen, the trigger delay should be entered as the number of
nanoseconds between trigger edge and video signal start; the oscilloscope might give this number in
microseconds (1 μs = 10-6 s; 1 ns = 10-9 s).
b. This trigger delay time can also be calculated, by measuring the apparent radius rdelay of the disk on the
SeaDarQ radar image. The radar wave would travel this apparent distance at the speed of light (c) in a time
Δttrigger. (Actually, it would go there and back again, so we need a factor of 2.) So the trigger delay time
should be Δttrigger = 2* rdelay / c (where the speed of light c is 3*108 m/s). Note that SeaDarQ shows the
distance (and bearing) of the cursor in the status bar at the bottom of the image.
If the trigger delay time is correct, the disk in the middle of the SeaDarQ radar image should vanish.
An extra check is to look at the radar image of some nearby feature that should show up as a straight line. If the
delay time is correct, the radar image of this feature will also be a straight line; if not, the line will seem to bend
towards or away from the radar position.
Once the correct value for the delay
time has been established, fill in
this final value for the trigger delay
time in the driver for the GaGe card
(PCIe Razor CompuScope
Properties, under the Advanced
tab).
Once this value is filled in in the
driver, it should not be filled in
again in SeaDarQ’s Processing
Parameters screen; the value in the
Processing Parameters screen is
relative to the value in the driver,
and is only intended to experiment
with its value, as described.
Figure 6.22: Trigger delay value in the Device Driver window of the
GaGe data-acquisition card
Figure 6.25: RNI Configurator software with one of the NMEA tabs selected
2 RADAR SUBSYSTEM
2.1 Introduction
2.1.1 Overview
This section describes a number of aspects of service, inspection and maintenance of components of the
SeaDarQ (v 3) Oil Spill Detection system, in particular of the GEM radar system.
2.1.2 Purpose
The purpose of this section is to describe the most important service activities in sufficient detail that these
activities can be carried out by on-site technical personnel.
2.2.1 Moisture
If / when the scanner unit is opened, it is possible that moist air gets in. The moisture could at a later moment
condense on cold parts, e.g., when the unit cools down at night.
To prevent moisture and condensation, it is recommended to place a 100 g bag of silica gel inside the scanner
unsit.
During yearly inspection, this bag of silica gel should be checked and if necessary replaced.
2.2.4.1 Inspection
To inspect the motor brushes:
remove each brush in turn
check the brush for excessive wear (if it is shorter than x mm, it needs to be replaced)
after inspection, put the brush back into the motor housing (provided it has passed the check)
2.2.4.2 Replacement
Instead of putting the original motor brush back into the motor housing, put in a new one.
note
Access to all motor brushes is easier if the RTX plate assembly is unbolted and slid out.
2.2.5.1 Inspection
To inspect the motor drive belt:
check for wear
check the tensioning of the belt
2.2.5.2 Tensioning
To (re-) tension the drive belt:
loosen the bolt that keeps the tensioner in place (see fig)
by pushing on the tensioner by hand, put tension on the belt
re-fasten the bolt
2.2.5.3 Replacement
see GEM instructions
2.2.6 Magnetron
The magnetron has an expected total operational life-time of 4500 hours. Towards the end-of-life signal
degradation will occur.
2.2.6.1 Inspection
It is unlikely that visual inspection has any use whatsoever.
adjustment of magnetron current
with the radar in stand-by mode, measure the voltage over the magnetron wires (fig); only proceed with
the rest of the adjustment if the measured voltage is 6.3 V ( 0.1 V ?)
with the radar in operation, check the blinking rate of LED DL5 (on the high voltage side of the
scanner-unit). A frequency of 1 Hz indicates a correct magnetron current. A frequency lower than 1 Hz
indicates too low a magnetron current. A frequency higher than 1 Hz indicates too high a magnetron
current
adjust VR3 (by no more than 1/16th of a turn), clockwise to increase the magnetron current
2.2.6.2 Replacement
See GEM instructions
2.2.7 Motor
It may be easier or quicker to change out and replace the entire motor, allowing workshop refurbishment of the
original motor.
replacement
See GEM instructions
To remove the motor:
remove the drive belt from the pulley
disconnect the motor power connector (behind the motor)
undo the 4 bolts that keep the motor in place (for the bolts behind the motor, use a x mm pipe-wrench)
Putting a new motor in place, follow the reverse procedure.
2.3.1 Weekly
check exterior of the units
o for cleanliness
o for loose or missing hardware
inspect mechanical action of all switches
inspect external cables for cracks in insulation, cuts, frays, and deterioration, especially at connecting
and supporting points
tighten any loose connections
check interior
o for cleanliness
o for loose or missing hardware
check all wiring for cracks in insulation, cuts, frays, and deterioration, especially at connecting and
supporting points
Check for signs of overheating, usually indicated by:
o Discoloration
o Blistering
o Corrosion on contact surfaces
o Odours
If dust or dirt is found, remove it using a dust brush or vacuum cleaner
For any discrepancies found:
o Determine the cause
o Repair
If there is any evidence of water or salt inside the units:
o Determine where it came from
o Thoroughly check for damage to electronics
o Carefully remove any and all traces of water and/or salt deposits
2.3.3 Yearly
Grounding (console ?)
o Remove the power supply cord from the GEM ASU
o Connect a test-terminal to an un-painted part of the ship
o Connect a test-terminal to an un-painted console part (*)
o Using an Ohm-meter, verify that the resistance between the 2 terminals is less than 0.05 Ohm.
o If the test fails, check the ground connection and repeat the test
o Only re-connect the power supply after a positive test
Grounding
o Inspect ground connections for opens and corrosion
o Verify screws and nuts are tightened
o If there is corrosion:
Take out the power supply line
Replace screws/nuts fixing the ground strip
Clean ground contacts using a wire brush or emery cloth, to obtain a clean metallic
surface as a good conductor
After re-assembly and fixing, protect the earth connection with a silicone grease film
IV Troubleshooting
1 INTRODUCTION
This is a first collection of hints and guidelines to assist in case problems arise.
This section is of a highly technical and specialized nature. Users of this guide are assumed to be sufficiently
technically skilled, so many terms and procedures are not explained in exhaustive detail.
In the following sections, we provide information that we hope can help in the troubleshooting process:
Some technical background information about SeaDarQ
Certain symptoms, what they could mean (i.e., hypotheses to their cause), and what tests could confirm
this (testing the hypotheses)
Some tests, and how to interpret their results
A few more bits of advice found on the internet
In addition to that, refer to the first part of this Installation and Maintenance Guide, and to the SeaDarQ Oil Spill
Detection Reference Guide, for an understanding of the working of the system.
Disconnection of either the azimuth or the north reset signal should be noticeable in the driver details for the PCI
Angular Encoder. The “Settings” tab of the driver has tick-boxes “Pulse Overflow” and “Pulse Timeout”. Pulse
Overflow will show a tick-mark if the North Reset signal is not received for a (longish) time. Pulse Timeout will
show a tick-mark if the Azimuth signal is not received (this will show much sooner). Do note that these tick-
marks cannot be cleared or reset, other than by closing the driver window.
Correct processing of the trigger signal can be verified as follows:
A disconnected trigger in signal at the GaGe card results in a freezing of the SeaDarQ radar image
Another check of the trigger signal is to check the statistics in the “Radar Settings” window. In
particular, the number of lines reported there corresponds to the number of trigger pulses read in so far.
This number should steadily increase (with the trigger signal connected – it will stay at the last value if
trigger-in is disconnected).
This same “Radar Settings” window also reports trigger timeouts, which occur if no trigger signal is
received within the time specified as “Trigger time-out”. It is useful to set the trigger time-out to a short
time for checking purposes, say 5 seconds.
(In the “Radar Settings” window, select “Show statistics” in order to see these and similar numbers that can help
in diagnosing problems).
3.2.1 General
controller error messages
e.g. ARP error: self-explanatory
If errors like this are reported in the Radar Controller software, than they are not related to the RNI or SeaDarQ.
The Radar Controller software communicates with the ASU power supply and controller unit directly, over
RS232. If the ASU reports an error like this, there could be a problem with the CB36 cable.
On the other hand, be aware that during start of the system some of these errors may temporarily show – they
normally go away again after a minute or so.
cable
If needed to check an already radar-connected CB36 cable: use the cable itself as the “extended” probe-lead, and
short-circuit cable pairs on the 2x13 connector end, measuring on the mil-spec style connector. Use cable triples
if you need to determine one specific core. Have a short lead with pins that fit in the 2x13 style connectors for
the purpose.
power to the scanner unit
It is wise to check that all power connections in the CB36 cable actually are connected, and the same for the
ground connections. Power and ground are spread over multiple cores for current-carrying reasons.
ARP and ACP signals between radar and PC
If it is needed to check these signals on an oscilloscope, it may be necessary to use a specially constructed DB-9–
to–4xBNC cable. Such a cable could also connect one of each differential pairs to the RNI, as a temporary trick
to get at the numbers that the RNI provides for these signals if they are connected to the RNI.
List of things to check
(in large part based on a case aboard a specific Oil Spill Response Vessel, and therefor somewhat GEM-
specific)
[motivation in italics and between square brackets]:
When the antenna-rotation is switched on (via Radar Controller – transmit; after waiting for the system
warm-up sequence to finish), does the antenna try to turn briefly, or not at all ?
[If the antenna does try to turn briefly, and then stops, it could be that the motor does function, but that a
lack of angular encoder pulses, i.e. lack of the required feedback on the rotation speed, forces a motor
shutdown]
How does the antenna behave when the system is switched off: does it stay in its position, or does it move
with the ship or by the wind ?
[movement of the antenna by the wind , e.g., suggests a problem with the drive-belt]
Does the ASU-43000 provide the correct voltage to the motor (48 V, +/- 20%, 2A typical, 10A peak)
[a supply voltage that is too high continuously could eventually be bad for the motor – but mind you, 20%
allowed deviation comes down to 9.6 V]
Does the ASU-43000 provide the other supply voltage at the correct levels?
24 V +/- 10%, 3A typ., 4A peak
12V +/- 10%, 1.5A typ, 2A peak
-12V +/- 10%, 0.5A typ, 1A peak
[Possibly, a bad 12V or 24V supply could affect the angular encoder ?]
What can be gleaned from an inspection of the turning unit and antenna?
externally
internally
Points of interest:
damage to the antenna
damage to the motor housing
connectors and connections
motor
drive-belt
tensioning mechanism
rotary encoder
Controller Board ?
Different approach: what parts – and subsystems – are important or play a role in the antenna drive mechanism:
motor (with built-in planetary gear transmission)
motor power (48V)
o as supplied by ASU-43000
connection and cable to upmast
o round MIL-STD connector at the back of the ASU-43000
o orange plug-connectors inside the SU74-06
o cable end ferrules with which the cable parts are connected to the orange plugs
connection from Logic Controller board to motor controller board (internal to SU74-06)
control signals from ST82000 Controller Board
drive belt
+ tensioning roller
the rotary joint
the angular encoder
connection via the ST82000 controller board (details unknown)
the antenna itself
is the system operating within the environmental limits ?
Operating temperature -25 C tot +55 C
Relative humidity up to 90% at +40 C
There could be a problem with the electrical system on board the ship, in particular with earth. To check: Ohm-
meter (DMM) between PC ground and ship; between power supply ground (i.e., the ASU-43000) and ship,
between SU74-06 housing and ship ¬– all with the 220V plugs connected
(could be that ground in the plug or distribution box isn’t connected)
Put upmast 48V directly onto the motor, this will give an answer to the question if the problem really is with the
moror, or whether it is with the motor control board
DIP2
S3
Figure 3.1: Location of DIPSW S3 on the GEM ST82000 logic Figure 3.2: DIP2 on DIPSW S3; the
controller board arrow indicates the ON position
To switch on simulation of all signals through the ST800 program, after establishing communication with the
radar, select “Control”, “ACP”, “TestAcp”, “Enable”, and then “Control”, “State”, “Tx”.
After these commands, the Scanner Unit will put signals on the wires; figures 3.3 and 3.4 show oscilloscope
screen-shots of the trigger and video signals. Figures 3.5 and 3.6 show what the radar image looks like in
SeaDarQ. For figure 3.5 the maximum radar range was set to 1.535 km; the image will look slightly different
with other range settings. Figure 3.6 shows an enhancement of the radar image, as the normal radar image for
this simulated signal is difficult to see properly in this document, especially when printed.
Note that the oscilloscope images of figures 3.3 and 3.4 alternate, so the “live, unfrozen” signal on an
oscilloscope will appear as a combination image
Figure 3.3: Oscilloscope image showing the simulated Figure 3.4: Oscilloscope image showing the simulated
signals: trigger in (from radar: purple), trigger out signals: trigger (from RNI to PC; blue), video in (from
(from RNI to PC; blue), video in (from radar; yellow) radar; yellow) and video out (from RNI to PC; green)
and video out (from RNI to PC; green)
Using this test, it is possible to determine proper operation of all SeaDarQ components (PC, RNI), and proper
connections via the ASU-43000 and the CB36 cable, whatever the state of the motor, magnetron and modulator
in the Scanner Unit.
Figure 3.5: SeaDarQ radar image of the simulated GEM signals (maximum range set at 1.535 km)
Figure 3.6: Close-up of the simulated radar pattern (enhanced for better visibility)
4.1 Sources
http://serverfault.com/questions/8812/your-troubleshooting-rules-approach-to-troubleshooting
“Network Troubleshooting Tools” (J. Sloan; O’Reilly)
"The Practice of System and Network Administration" (T. Limoncelli; Addison-Wesley)
“Basic Troubleshooting Strategy” (B. Lonzo, presentation on SlideShare.net)
The following highlights are paraphrased from the "Debugging" chapter of "The Practice of System and
Network Administration":
Two things to know:
1. Know what the "fixed" version looks like.
2. Describe the problem at the right level.
Two strategies:
1. Additive: Keep adding components until the problem starts. The last thing you added is the problem.
2. Subtractive: Keep removing components until the problem goes away. The last thing you removed was
the problem:
Two bits of dumb luck:
1. […] The problem is being caused by the last change made to the system. (this works 99% of the
time... the problem is that 99% of the time you don't know what the last change actually was)
2. When all else fails, check for stupid things.
from some areas and towards others and to condense it down to points which are high probability problem
locations, then attack those. This comes back to the cause and effect point
look for places to carve the problem into a smaller one
relentlessly focus […] on narrowing down the scope of the problem.
Carve out chunks of "things it cannot be" as big as possible.
Understand the system
think basic - don't jump to the most complicated scenario because it's in your head, perform your basic
troubleshooting and let it lead you
start by checking the obvious. Is there an error message explaining what the problem is? Is everything connected
properly?
If the answer isn't obvious, line up some suspects and test those first. Only after you test the likely suspects
should you test the unlikely suspects. Then you can be as scientific as you want.
Another extract from Network Troubleshooting Tools:
(12.1: Generic troubleshooting)
1. Document
2. Collect information and identify symptoms
3. Define the problem
(This is not the same as identifying the symptoms but is the process of combining the symptoms
and making generalizations. You are looking for common elements that allow you to succinctly
describe the anomalous behavior of a system.
Your problem definition may go through several refinements.
It is natural to try to define the problem as quickly as possible, but you shouldn't be too tied to
your definition. Try to keep an open mind and be willing to redefine your problem as your
information changes.)
4. Identify systems or subsystems involved
5. Develop a testable hypothesis
(developing a set of tests is more important than having an exact definition of a problem […]
In general, you want tests that will reduce the size of the search space)
6. Select and apply tests
(Determining the optimal order for a set of tests is largely a judgment call. Clearly, the simple
tests that answer questions decisively are the best.)
7. Assess results
(As you perform tests, you will need to assess the results, refine your tests, and repeat the
process. You will want new tests that confirm your results. This is clearly an iterative process.)
8. Develop and assess solutions
(With many problems, there will be several possible solutions to consider. You should not
hastily implement a solution until you have thought out the consequences.)
9. Implement and evaluate your solution
(confirm the proper operation of your system)
One last word of warning. It is often tempting to seize on an overly complex explanation and
ignore simpler explanations. Frequently, problems really are complex, but not always. It is worth
asking yourself if there is a simpler solution. Often, this will save a tremendous amount of time.
V Appendices
1 PRE-INSTALLATION CHECK-LIST
SeaDarQ
Pre-Installation
Checklist
Radar signals
North Reset (Heading)
Level .......................................................... : TTL RS-422 _______ [V]1
Edge sensitivity .......................................... : Rising Falling
Termination................................................ : 50 75 1M
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Azimuth (Bearing)
Level .......................................................... : TTL RS-422 _______ [V]1
Edge sensitivity .......................................... : Rising Falling
Termination................................................ : 50 75 1M
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Trigger (Sync)
Level .......................................................... : TTL RS-422 _______ [V]1
Edge sensitivity .......................................... : Rising Falling
Termination................................................ : 50 75 1M
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Raw video2
Level (range) ............................................. : _______________ - ____________ [V]3
Termination................................................ : 50 75 1M
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Heading
Level .......................................................... : RS-232 RS-422 RS-485
Sentence ................................................... : $HEHDT
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Depth6
Level .......................................................... : RS-232 RS-422 RS-485
Sentence ................................................... : $SDDBT
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
Speed log6
Level .......................................................... : RS-232 RS-422 RS-485
Sentence ................................................... : $VWVHW
Connector and pin number ........................ : ________________________________
Mating connector type ............................... : ________________________________
5
Standard cable length is limited to 3m.
6
Depth and Speed are optional.
7
Cables from the NMEA devices to the SeaDarQ system are not in the scope of delivery.
8
Standard cable length is limited to 2m.
9
A stable power supply must be available, otherwise a UPS must be present.
Please draw a map with the locations of the SeaDarQ system, display, radar
processing unit and NMEA devices.
10
A minimum of three power outlets are required excluding radar.
11
A minimum free space of 5HE (222mm) x 700mm [w x d] is required with sufficient cooling for the system.
12
Specify the available space for the rack.
customer initials:
determine value
OK after reboot
set in driver
Description notes value
Site details
date
location
physical installation
position PC (rack-mounted ?)
position RNI (rack-mounted ?)
connect PC peripeherals
screen (VGA / DVI / …)
keyboard
mouse / trackball
power
SeaDarQ PC
screen
RNI
connections
radar RNI radar
RNI PC PC
video
trigger
azimuth
north reset
network / modem IP address
phone nr
check (Ultra-) VNC access VNC password
determine value
OK after reboot
set in driver
Description notes value
3 SEADARQ INSTALLER
Installation sequence:
1. Coastline Database.msi
2. SeaDarQInstaller_4.i.jjjj_x64.msi
Options:
Program Legend:
SeaDarQ Operational manual Always install
SeaDarQ AIS Module Optional, if applicable / ordered
SeaDarQ Geographic Snapshots ( ) Deprecated, no longer supported
SeaDarQ Drivers Do not install (development only)
Aptomar Support
( ) ChartWorX Support
Octopus Support
Radar Dump Support
GEM Radar Support
FTP Wave Client
Note that any change in the Device Driver for the GaGe card requires the Device Driver to be stopped and re-
started. Make sure that the SeaDarQ software is not running during this device driver restart !
4 RNI CONFIGURATOR
4.1 Introduction
This appendix describes the RNI Configurator software (version 4.0), that can be used to adjust settings on the
RNI.
Figure 4.1: The Device Manager window, showing the RNI NMEA Interface device driver (under NMEA
Devices)
Starting the RNI Configurator program starts with querying this device driver. If it isn’t loaded, this results in an
error message (figure 4.2), but after this error message, the program just loads (it gives no further indication that
no RNI is connected). If the RNI is powered up after the RNI Configurator program is already running,
communication between PC and RNI is not established; the (re-) appearance of the RNI NMEA Interface device
driver is not picked up after RNI Configurator is started. So the RNI Configurator program should always be
started after applying power to the RNI.
Note that there is no option to specify on which (mapped USB COM) port to look for the RNI; the program does
not scan any port, but communicates (or attempts to communicate) with the device driver.
Figure 4.2: The error message that appears if no RNI is connected (or powered) when the RNI Configurator
program is started
Another important aspect to be aware of, is that (especially with a Sperry radar) control of and communication
with the RNI now also happens in operational mode from within SeaDarQ 4.0 itself. Having both SeaDarQ and
RNI Configurator communicating with the RNI at the same time is bound to lead to unexpected results and
behaviour. As a general rule, only use RNI Configurator for first-time installation and configuration of the RNI
and radar. In day-to-day operations, only use control from within SeaDarQ itself.
Figure 4.3 shows the Sperry BridgeMaster E radar controller tab in full; figure 4.4 shows a slightly enlarged part
of it, for better legibility. Table 4.1 lists the various controls on this tab, with brief descriptions and, where
needed, some extra remarks, to explain what the controls do.
Please be aware that this radar controller tab is only applicable to the Sperry BridgeMaster series E radar. If no
Sperry BridgeMaster E is found, this tab will actually become totally blank.
(Note: a fair amount of this information and control is also available inside SeaDarQ 4; exceptions are the
configuration of the blanking sectors).
Figure 4.4: The Sperry BridgeMaster E radar controller tab, somewhat zoomed in
4.4.2 Video
Figure 4.5 shows the Video tab. Table 4.3 lists the items on the Video tab, with a short description of the
functionality of each item.
The Range Correction sections (Range Offset and Range Gain) are explained in separate sub-sections (sections
4.4.8 and 4.4.9).
+1V +1V
0V 0V
-1V
Figure 4.6: Illustration of the concept behind input offset, output offset, and gain
4.4.3 Trigger
The following figure, figure 4.7, shows the Trigger signal tab. Table 4.4 lists the items on the Trigger tab, with a
short description of the functionality of each item.
4.4.4 ACP
Figure 4.8 shows the ACP (Azimuth) tab. Table 4.5 lists the items on the ACP tab, with a short description of the
functionality of each item.
4.4.5 ARP
Figure 4.9 shows the ARP (North Reset) tab. Table 4.6 lists the items on the ARP tab, with a short description of
the functionality of each item.
4.4.6 NMEA
Figure 4.10 shows one of the NMEA Port tabs. Table 4.7 lists the items on the NMEA Port tab, with a short
description of the functionality of each item.
The tabs for the different NMEA Ports are all identical, the only difference between them is which NMEA Port
they apply to.
Table 4.8: NMEA signal connections for RS-232 and RS-422 on the RNI
RNI NMEA RS-232 RS-422
connection signal signal
pin nr
1 left TX A(-)
2 middle RX B(+)
3 right GND N/C
Figure 4.11: Schematic of the RNI NMEA signal connections for RS-422 (A-, B+) and RS-232 (view from top of
RNI)
NOTES:
1. Counter to what you might expect, enabling one of these filters means those messages (and only those
messages) are included. To disable a type of message on a NMEA port, toggle the button for that message
type to its de-selected, off state.
If filtering is disabled all together, all messages are included.
2. Wind speed and angle: relevant if the vessel (or stationary installation) that the SeaDarQ system is installed
on is equipped with a wind-sensor for wind-speed and –direction, which reports in NMEA format. Such a
system can feed wind information into SeaDarQ (via the RNI), allowing on-screen display of this
information.
Some options for the two-letter device codes (aka Talker ID) are:
GP GPS receiver
HE Heading – North seeking gyro
SD Depth sounder
AI AIS (typically used as !AIVDM, …)
The SeaDarQ device drivers expect certain combinations of two-character Talker ID and 3-character sentence or
message type: e.g., Heading HDT is expected to come from an HE device ($HEHDT). Sometimes a NMEA
device provides other information than expected based on its Talker ID; e.g., a differential GPS can also emit
heading sentences ($GPHDT). The SeaDarQ device drivers cannot handle such sentences. To remedy this, HE
and GP Talker ID substitution lets the RNI replace the original Talker ID with the one the SeaDarQ device
drivers expect based on the 3-character sentence or message type (so, e.g., $GPHDT is replaced by $HEHDT).
Note that this is only implemented for HDT (heading) and GLL (geographic location) sentence contents.
4.4.7 Miscellaneous
Figure 4.12 shows the Miscellaneous tab; figure 4.13 shows it again, slightly zoomed in for better legibility.
Table 4.10 lists the items on the Miscellaneous tab, with a short description of the functionality of each item.
Figure 4.14: Section of the Video tab that relates to the Range Correction Offset
Table 4.11: Items in the Range Correction Offset section of the Video tab
Item Description Remarks
Input Offset The base offset for the correction curve, to apply to the
video signal
Accepted range: 0 .. 10000 [mV]
Range This determines the curvature of the correction curve
Accepted range: 0 .. 1500 [m]
Reset range The range (distance from the radar) that corresponds to the
time of the next trigger signal
Accpeted range: 6 .. 74 [km]
Fine Tick-box to toggle the slider between coarse and fine
adjustments (when ticked, moving the slider changes the
setting by much smaller amounts) Each of the sliders has a tick-box
(Numerical This box shows the current setting for the quantity under and input box like this
input box) control of the slider (it is updated as the slider is moved). It
is also possible to type a value into the box
The idea behind the range correction is sketched in figure 4.15: the “envelope” of the actual video signal has a
certain distance-dependence, both in top-to-top levels of the video signal, and in the bottom level of the video
signal. Ideally, the bottom level would be zero, and the top-to-top level would be constant.
The range correction offset applies a correction curve to the video signal, such that the base level is translated to
zero. As the actual base level goes down (exponentially) over a single radar line, this base level correction varies
in a similar way.
(The second element, the decay in the video signal amplitude with distance, can be corrected through the Range
Gain section, described separately.)
video signal
offset
gain /
attenuation
offset
reset range
Figure 4.16: Sketch of the reset range for the range correction offset
Figure 4.17: Section of the Video tab that relates to the Range Correction Gain
Table 4.12: Items in the Range Correction Gain section of the Video tab
Item Description Remarks
Attenuation The base attenuation for the correction curve, to apply to the
video signal
Accepted range: 0 .. 200 [%]
Range This determines the curvature of the correction curve
Accepted range: 0 .. 1500 [m]
Reset range The range that corresponds to the time of the next trigger
signal
Accepted range: 6 .. 74 [km]
Fine Tick-box to toggle the slider between coarse and fine
adjustments (when ticked, moving the slider changes the
setting by much smaller amounts) Each of the sliders has a tick-box
(Numerical This box shows the current setting for the quantity under and input box like this
input box) control of the slider (it is updated as the slider is moved). It
is also possible to type a value into the box
The idea behind the range correction is sketched again in figure 4.18: the “envelope” of the actual video signal
has a certain distance-dependence, both in top-to-top levels of the video signal, and in the bottom level of the
video signal. Ideally, the bottom level would be zero, and the top-to-top level would be constant.
video signal
offset
gain /
attenuation
gain
reset range
Figure 4.19: Sketch of the reset range for the range correction gain (attenuation)
4.5.1 Introduction
The front of the RNI has a display panel and a selection dial. In principle, all RNI configuration settings can be
made either through the RNI Configurator program, or via the RNI front panel display and selection dial, with
only a very limited number of exceptions. Table 4.13 lists these exceptions.
Table 4.13: Configuration options exclusive to either RNI Configurator or the RNI front panel display
Option only via RNI Configurator only via front panel display
and selection dial
Sperry BridgeMaster E radar control —
Update firmware —
Restart RNI —
Save Settings to File —
Load Settings from File —
Radar type selection —
The top row of the display shows a series of icons that (generally speaking) corresponds to tabs in the RNI
Configurator program.
The second row on the display shows
the current menu level. When a sub-
menu is entered, the name of the sub-
menu is added to the rest of the line
(see figure 4.24 for an example). The
bottom row shows the name of the
currently selected menu or option. If
the currently selected menu has a sub-
menu, this is indicated by three dots Figure 4.24: RNI display showing a selection with a further sub-menu
following the name (figure 4.24 shows
an example). If the current selection is
an option with a value that can be
altered, the current value is shown at
the right-hand side of the row (see
figure 4.25 for an example).
By rotating the dial, you can move
between menus or options in the top
row; the current selection is indicated Figure 4.25: RNI display showing an option with a value that can be
by a surrounding rectangle.
altered
Clicking the dial enters the menu, sub-menu or option. Clicking an option with a value that can be altered,
selects that value (and highlights it). At this point, rotate the dial to change the value until the desired value is
shown. Click the dial to accept the value that is shown, and return to the menu.
All sub-menus have an option
“Back…” at the right, to return the
menu one level up (see figure 4.26).
The top-level or main menu has an
option “Exit…” instead, that when
selected exits the menu system and
returns to the normal status display.
Figure 4.26: Moving back a level on the RNI display
When the normal status display is shown, rotating the dial adjusts the brightness of the display.
The following sub-sections show and describe the various RNI front panel display menus, albeit briefly. The full
hierarchy of displays is not shown, as this would make this section unwieldy.
Where useful, annotations above the pictures of the RNI display indicate the function of the icons in the top row
of the display.
Main display
Warning
load from
EEPROM
EEPROM
defaults
NMEA
factory
save to
radar
Exit
► Menu
north reset
azimuth
trigger
video
back
► Menu ► Radar…
Connection
Note: RNI firmware version 3.5 only has “Other” (as it lacks the hardware for the specific radar options)
4.5.4 Video
► Menu ► Radar…
Video…
Overall offset
Range corr.
Range corr.
Input offset
termination
termination
offset …
Through
gain …
Input
Back
Gain
► Menu ► Radar ►
Video…
Input termination
The “Range Correction offset…” and “Range correction gain…” sub-menus lead to a similar screen, allowing
the following configuration options:
Range correction offset … options
sub-menu selection
Enabled Yes / No
Offset 0 … 10000 mV
Range 0 m … 1500 m
Reset range 6 km … 74 km
For a description of the idea behind range correction, see sections 4.4.8 (“Range Correction Offset”) and 4.4.9
(“Range Correction Gain”).
► Menu ► Radar…
Trigger…
Trigger mode
Input pull-up
Trigger level
termination
Dead time
direction
Input
Edge
Back
► Menu ► Radar ►
Trigger…
Input termination
Each sub-menu leads to an option to select a value for the relevant setting (without further sub-menus), as
detailed in table 4.14.
Table 4.14: Configuration options for Trigger, Azimuth and North Reset
Sub-menu selection options
Trigger Azimuth North Reset
Input termination 50 Ω / 75 Ω / 1 MΩ
Input pull-up Yes / No
Edge direction Rising / Falling
Trigger mode Auto / Manual
Trigger level –15000 mV … + 15000 mV
Dead time off … 25412 us off … 5236 ms
► Menu
NMEA
NMEA port 1
Substitute
(port 5)
port 2
port 3
port 4
Back
► Menu ► NMEA…
Port 1…
NMEA port 1
termination
termination
Loopback
Input bias
Baud-rate
Interface
Through
Filter…
Input
Back
► Menu ► NMEA… ►
Port 1…
Interface
Each sub-menu leads to an option to select a value for the relevant setting (without further sub-menus), with the
exception of the “Filter…” option, which does have a sub-menu of its own. The next table list the different
configuration options.
Sub-menu selection options
Interface RS-232 / RS-422
Loopback Yes / No
Input termination Yes / No
Through termination Yes / No
Input bias Yes / No
Baud-rate 600 bps 3600 bps 14.4 kbps 57.6 kbps
1200 bps 4800 bps 19.2 kbps 76.8 kbps
1800 bps 7200 bps 28.8 kbps 115.2 kbps
2400 bps 9600 bps 38.4 kbps 230.4 kbps
The “Filter…” sub-menu allows for the application of NMEA sentence filters to input NMEA message stream.
For more information on NMEA sentence filtering and the reason for its availability, see section 4.4.6.2.
Filter
Sub-menu selection options
Enabled Yes / No
HDT Cut / Pass
GLL Cut / Pass
GGA Cut / Pass
VHW Cut / Pass
DBT Cut / Pass
VDM / VDO Cut / Pass
Next to NMEA sentence filtering, NMEA Talker ID substitution can also be enabled from the RNI front panel
display. For an explanation of NMEA Talker ID substitution and the reason for its availability, see section
4.4.6.3
► Menu ► NMEA…
Substitute
The menu NMEA > Substitute controls the NMEA Talker ID susbstitution. It has no further sub-menus, but
when entered allows switching between the following options:
NMEA Substitute Off / HE / GP / HE & GP
load from
EEPROM
EEPROM
defaults
NMEA
factory
save to
radar
Exit
► Menu
“Save to eeprom” stores all current settings of the RNI into the on-board EEPROM. This ensures that after a
switch-off of the RNI, a subsequent switch-on has all current settings again.
Load from EEPROM
load from
EEPROM
EEPROM
defaults
NMEA
factory
save to
radar
Exit
► Menu
“Load from EEPROM” re-loads all settings for the RNI from the on-board EEPROM. This allows reverting to a
known configuration after experimenting with different settings, or temporarily changing settings.
Load factory defaults
load from
EEPROM
EEPROM
defaults
NMEA
factory
save to
radar
Exit
► Menu
“Load factory defaults” re-loads all settings for the RNI with factory defaults. Note that this does not affect the
settings in the on-board EEPROM, these latter are only changed after clicking “Save to EEPROM”.