Sonar UI User Manual
Sonar UI User Manual
SeaBat Sonar UI
Version 1.4.12
October 2019
2 Quick Guide 3
2.1 Introduction ............................................................................................................. 3
2.2 Steps ....................................................................................................................... 3
3 General Information 5
3.1 Introduction ............................................................................................................. 5
3.2 Arranging the Panes ............................................................................................... 5
3.2.1 Panes ............................................................................................................ 5
3.2.1.1 Opening and hiding Panes .................................................................. 6
3.2.1.2 Docking ................................................................................................ 6
3.2.1.3 Floating ................................................................................................ 7
3.2.1.4 Tabs ................................................................................................... 11
3.2.1.5 Context Menu .................................................................................... 11
3.3 Sonar UI Toolbar .................................................................................................. 12
3.3.1 Application Settings Dialog ......................................................................... 12
3.3.1.1 Lay-out ............................................................................................... 12
3.3.1.2 Sonar System .................................................................................... 13
3.3.1.3 Sonar Network Connections .............................................................. 14
3.3.2 About Dialog ............................................................................................... 15
3.3.3 Licensed Features Dialog ........................................................................... 15
3.3.4 Help File ...................................................................................................... 16
3.3.5 Sonar Address ............................................................................................ 16
3.3.6 Service Mode .............................................................................................. 16
3.3.7 Operation Mode .......................................................................................... 16
3.3.8 Save JPG Screen Snapshot ....................................................................... 16
3.3.9 Start Record AVI ......................................................................................... 17
3.3.10 Start Record RDR ..................................................................................... 17
3.3.11 Start the Tracker ....................................................................................... 17
3.3.12 Pitch Stabilization ...................................................................................... 17
3.3.13 Roll Stabilization ....................................................................................... 18
3.3.14 1PPS ......................................................................................................... 18
3.4 Screen Toolbar and Context Menu ...................................................................... 18
5 Service 79
5.1 Introduction .......................................................................................................... 79
5.2 Diagram ................................................................................................................ 80
5.3 Information ........................................................................................................... 81
5.3.1 Status.......................................................................................................... 81
5.3.2 Details ......................................................................................................... 83
5.3.3 IO Module QC ............................................................................................. 85
2.1 Introduction
This chapter will give a brief explanation how to start the Sonar UI, what is
needed for using the Sonar and how to improve the performance after the
sonar is pinging.
The Sonar UI requires OpenGL version 3.30 or higher to function properly
(check the specification of the used video card).
2.2 Steps
a. Before the Sonar UI is started a valid license has to be installed in
the 7KControlCenter to have certain features available. When the
license is not yet installed, a valid license file can be dragged and
dropped at the 7k Control Center or at the Sonar UI. See the
Operation Manual of the sonar for more details.
The 7KcontrolCenter
Select in the 7KControlCenter the option New Sonar UI and click
on the Start button to open the Sonar UI.
It is essential the correct cable length is specified. A wrong
cable length can damage the system!
3.1 Introduction
To setup and operate the Sonar in the Sonar UI, use:
The Panes. (see the next section)
The Sonar UI Toolbar (see page 12 ).
The screen toolbar and a Context menu. (see page 18)
3.2.1 Panes
The settings panes on the right side are:
Display
Detection
Recording
Hardware
IO Module
Pipe
The three panes (control and messages) at the bottom are:
Main
Advanced
Messages
Playback
This section will explain how to open, dock, drag and hide the panes.
See the chapter Operation on page 21 for more information about the
functions of the different panes.
3.2.1.2 Docking
It is also possible to use 1. Click on the pin at the upper right corner of the pane to keep
the context menu of the
pane to switch between
the pane from auto-hiding. The pin will change to , the pane is
Auto Hide and Docking now in Docking mode (pinned) and will stay open even when
modes (see page 11). clicking outside the pane.
2. Click on to undock the pane.
When dragging a settings pane to the guide diamond on the right side of
the display then:
1 The settings pane will be placed on the right side of the display.
2 An opened bottom pane will be shifted to the left.
Figure 3-8 Re-dock bottom pane from the bottom guidance diamond and an
opened settings pane
3.3.1.1 Lay-out
Reset:
When the layout is disturbed, select the check box to reset the layout and
font size of the Sonar UI.
Font size:
It is possible to set the font size to Small, Medium, and Big.
This only applies to the font in the panes.
Color mode:
With the color mode the light conditions for the screen(s) are modified for
better viewing conditions on an individual basis. The four different color
modes are:
Normal
Standard light conditions.
Advanced
The roll stabilization is only The LED indicator will show the status of the roll stabilization. Be aware
available in the toolbar the status of the LED is an indication related to the last received ping.
when it is defined in the This means when the sonar does not ping the status of the LED is not
xml file. updated.
The different colors are:
Blue – When the Sonar UI is started the roll stabilization is not yet
initialized.
Grey – The roll stabilization is turned off.
Green – The roll stabilization is enabled and working.
Yellow/Orange – Warning level – The roll stabilization receives a
roll value that exceeds ±15°.
Red – Error level – Possible errors are : no attitude data received,
roll value exceeds ±35° or change rate > 10° per second.
3.3.14 1PPS
The LED indicator will indicate if the 1PPS is received or not. Be aware
the status of the LED is an indication related to the last received ping.
This means when the sonar does not ping the status of the LED is not
updated
The different colors are:
Blue – When the Sonar UI is started the 1PPS is not yet initialized.
Green – The 1PPS is working.
Yellow/Orange – Warning level – No 1PPS received for a couple of
seconds.
Red – Error level – No 1PPS received anymore.
4.1 Introduction
Depending of the sonar type the Sonar UI opens with a dialog box to
specify the transmit cable length.
It is essential the correct cable length is specified. A wrong
cable length can damage the system!
When the Sonar UI is started, it will open in the Operation mode with four
screens or the number of screens that were open when the Sonar UI was
closed before.
In this chapter the different panes and the four screens will be discussed.
The Main and Advanced panes (at the bottom of the Sonar UI) provide
sonar control and the various settings panes (at the right side of the SUI)
provide options for presenting the sonar data.
The different panes are:
Main (see below)
With the Main pane the operator controls the sonar and selects
what screens to view during operation.
Messages (see page 34)
The Messages pane displays the error message as they are
received in the Sonar UI.
Advanced (see page 27)
In the Advanced pane the operator can set advanced sonar
settings.
IO Module (see page 35)
In the IO Module the sensor data can be selected and interfaced
into the 7K system.
Detection (see page 39)
In the Detection pane operator sets the Absolute and Adaptive gate
settings for the bottom detection process.
Display (see page 45)
In the Display pane the operator can customize the visual
properties of the screens of the Operation.
4.2 Main
The Main pane is for general control of the sonar. The choice of
screens (Wedge, Sidescan/Helmsman, Water Column/Detect and
Snippets) allows the operator to customize the display layout in Operation
mode.
4.2.1 Range
The range setting allows the operator to select how far the Sonar will
‘see’.
Select the appropriate range scale to keep the image of the bottom
detection at or above the widest part of the sonar wedge
4.2.2 Power
The power setting allows the operator to increase or decrease the amount
of power (acoustic energy) that is transmitted into the water.
If the power is set to OFF, the system will not ping, but it will continue to
receive data provided that the (ping) rate is not set to 0. The sonar system
will act as a passive sonar by only receiving data. This is a feature that is
very useful for monitoring the ambient noise and interference from the
vessel itself.
4.2.3 Gain
The gain setting allows the operator to select the amount of receiver gain
that is applied to the returned sonar signal, in addition to the calculated
gain. The gain is applied throughout the range as a fixed gain value.
For a given power setting, a narrower pulse length will provide a higher
resolution at a shorter range. A wider pulse length will provide better
range but a lower resolution image.
In certain conditions, for example in turbid waters, the narrower pulse
length may not operate well. In such circumstances, the wider pulse
length may give better short-range performance. This may also be
achieved by changing from higher to lower frequency operation.
4.2.5 Gate
The operator is able to enable/disable the required gate mode(s). By
default they are disabled. When enabled, the Gate mode button is
highlighted.
Settings for the different gate modes are set in the Detection pane. (See
page 39)39
The recommended value is the maximum rate to ensure that the highest
possible ping rate, depending on the range setting, can always be
achieved
In some instances it may be beneficial to force a lower ping rate than the
normal rate associated with a particular range. Examples of this would be
instances when the vessel is moving at a very slow rate, and the operator
wants to reduce the quantity of data that is generated; or when the sonar
4.2.7 Tile
In the Tile – Screen box the different screens can be switched on/off. By
default all four the screens are on. When a screen is on the button is
highlighted.
Figure 4-10 Tile with Wedge, Water Column and snippets screen switched on
(button highlited) but Sidescan screen off (button greyed )
The Wedge and Water Column/Detect screens are always on the left
side of the SUI and the Sidescan/Helsman and Snippets always on the
right side. If only one of the two screens on one side is open, then that
screen will use the complete left or right side of the view.
The Water Column/Detect button has three functions: switching on the
Water Column screen, switching on the Detect screen or switching off
both.
The Sidescan/Helsman button has three functions: switching on the
Sidescan screen, switching on the Helsman screen or switching both off.
When a screen is disable, no historical data will be logged. This means
that a screen will start empty if it is enabled during operation.
the right sides of the Sonar UI. Double-click on the horizontal divider for
the left or right side and the other half of the horizontal divider will jump to
the same level.
4.3 Advanced
The Advanced pane is for the advanced settings of sonar transmit and
receive functions.
4.3.1.1 Equi-Angle
In equi-Angle mode the spacing between the beams is equiangular. The
beam center-center angular spacing is constant across the swath.
In areas of significant relief and in particular when surveying features
such as wrecks and vertical structures such as harbor walls, Equi-Angle
should be used in preference to Equi-distant (see also section ‘Equi-
distant’).
The default for Equi-Angle is the minimum number of beams for 100%
ensonification.
The number of beams can be set by the operator with the slider. This
allows the operator to be able to capture the highest detail using the
highest beam density needed. In very shallow water fewer beams can be
used to reduce data volumes.
4.3.1.2 Intermediate
Intermediate is made for a general purpose survey operations and
provides high-density soundings over the entire swath using the
maximum number of beams. The number of beams can be set with the
slider when the ‘Custom’ checkbox is ticked.
4.3.1.3 Equi-Distant
Equi-Distant gives equally spaced soundings across the entire swath
using the maximum number of beams.
The spacing between the beams is equidistant. With Equi-Distant the
spacing is modified to maintain an equal horizontal distance between
soundings on the seafloor assuming a flat bottom.
It is recommended that Equi-Distant be used for general survey
applications where the requirement to achieve a specific number of
sounding per cell in the across-track is critical, or where the seafloor is
generally flat.
In extreme conditions, using Equi-Distant over complex structures can
cause magnified artifacts due to the large overlap between beams
towards the edge of the sector. When the ‘custom’ checkbox is selected
the number of beams can be set with the slider
4.3.1.4 Flexmode
Flexmode gives a combination of a high density of beams on and around
the object location and a reduced density of soundings for the rest of the
swath.
Default settings
Total swath: 90°
High density sector: 45° centered
Altitude: 5m
DTM density: 0.1m
30%
Total swath
The low density spacing distance between the beams is defined by the
operator by setting the outside spacing with the slide bar (see below)
The high density spacing is set by the slides in the wedge. This slides
become visible in the wedge when the Flexmode is selected. Drag the
slides and the high density spacing changes.
Figure 4-18 Slides in the wedge to change the high density spacing
To achieve a correct beam The (horizontal) steering setting allows the operator to steer the swath
steering in equidistance electronically.
mode the sonar needs an
up-to-date online sound The achievable steering depends on the selected coverage angle (see
velocity measurement. Coverage angle on page 31).
The default button resets the steering to 0. (The coverage angle
will also reset.)
The extent of the steering is determined by the coverage angle selected.
The limitation is that the outer beam cannot be steered past 5° from the
5°
25°
60°
90°
85°
Figure 4-20 With a swath of 120° the maximum steering is ±25° (85°-(120°/2))
5°
30°
90°
55° 85°
Figure 4-21 With a swath of 60° the maximum steering is ±55° (85°-(60°/2))
4.3.4 Frequency
For a dual-frequency system, the frequency setting allows the operator to
switch the frequency on the fly without restarting the 7K Center. All sonar
controls will then be dedicated to the selected frequency.
4.3.7 Absorption
The absorption slider allows the operator to set the amount of loss that is
expected through the ambient water medium. The absorption loss is
proportional with the salinity of the water and the sound frequency: the
higher the salinity or frequency, the greater the loss. Also an increased
temperature will increase the absorption loss.
If the exact absorption loss value is not known, a value of 110dB/km for
salt water and 70dB/km for fresh water is recommended for a 400kHz
operation, and a value of 50dB/km for salt water and 20dB/km for fresh
water is recommended for a 200kHz operation.
This value is used in conjunction with the spreading loss coefficient (see
‘Spreading’) to compute the TVG (time varied gain) curve that is applied
to the returned signal (see Gain on page 24).
4.3.8 Spreading
The spreading allows the operator to enter the amount of cylindrical and
spherical spreading loss that is expected through the ambient water
medium. Spreading of sound through water may be the greatest
contributor to the loss of sound. As sound moves away from its source in
all directions, the acoustic pressures will decrease with the range.
This value is used in conjunction with the absorption loss value (see
above) to compute the TVG (time varied gain) curve that is applied to the
returned signal (see Gain on page 24).
In practical situations the transmission loss will lie between 20 and 40dB;
in other words, the spreading loss will neither be perfectly spherical nor
perfectly cylindrical. Finally, if the sonar operates very close to the seabed
or very close to objects in general, near-field effects may yield a
transmission loss less than 20dB.
If the exact spreading loss value is not known, an initial value of 30dB is
recommended.
4.3.11 Temperature
This parameter is only available for T50 sonars with the licensed
calibrated backscatter feature.
The T50 sonar uses the temperature together with the sound velocity and
frequency to calculate a more accurate absorption value. This absorption
value is used for the (licensed) calibrated backscatter feature.
Select the override checkbox to use the temperature as set by the slider.
4.4 Messages
In the Messages pane the operator can see the error messages related
to the sensor interfacing.
4.5 Playback
Select in the Playback pane s7k file to play back.
Press the Play button to start the replay.
Select from the toolbar the sonar address (see page 16) to connect again
with the sonar.
4.6 IO Module
In the IO Module pane the different sensors (such as the sound velocity
probe and the external clock) can be interfaced with the IO Module. The
data acquired by the IO Module is routed to the Sonar in real time to allow
for accurate time stamping and Beamforming.
.
Figure 4-35 Clicked in the ‘Driver Name’ field of the Attitude device to have the
attitude driver list available
In the I/O pane also the Input distribution (RRIO) is listed. This is not a
device as the other listed items are. The ‘Input distribution (Reson Remote
I/O)’ can be used when the operator wants to send one of the this different
device data to another system, like an acquisition computer,
Enter as Destination Address the IP Address or computer name followed
with ‘:’ and a port number; for instance: ‘10.4.1.28:1000’.
The port number is the base port and offset of the base port, depending of
the source of the message. Currently this is for:
VRU Base port (e.g. 2020)
Position System. Base port + 2 (e.g. 2022)
Compass Base. port + 4 (e.g. 2024)
Sound Velocity. Base port + 6 (e.g. 2026)
External Clock. Base port + 8 (e.g. 2028)
Pan and Tilt. Base port + 10 (e.g. 2030)
Do not use a port number between 6990 and 7000 as otherwise port
conflicts may occur with the 7kCenter.
4.6.2 Clock
To achieve correct time stamping of transmitted pulses it is necessary to
send time to the sonar processor. The Sonar uses the GPS PPS system
to achieve this. From the GPS receiver, the Sonar needs the TTL 1PPS
pulse and the qualifying time message (normally ZDA). The clock
synchronization must always be entered in the IO Module.
If the 1PPS is not detected during the sonar operation, the led indicator
in the toolbar changes from green to yellow/orange to red and in the
Service page in the Status tab the error is displayed. Set the associated
settings for the connected external clock device.
4.6.3 Attitude
Select the associated settings for the attitude sensor when connected to
the Sonar Processor.
Use the Hardware Pane (see Hardware on page 51) to setup the attitude
sensor used for the motion stabilization of the sonar.
4.6.4 Depth
Select the associated settings for the depth sensor when connected to the
Sonar processor.
4.6.5 Position
Select the associated settings for the GPS position sensor when
connected to the Sonar processor.
4.6.6 Heading
Select the associated settings for the heading sensor when connected to
the Sonar processor
Tracker
Coverage angle
Snippets
And Multi-detect mode
The minimum difference between the minimum and maximum gate value
is defined on 2m. When one of the gate values is set closer than 2m from
the other gate value, the other gate value will change to get a difference
of 2m again. This is also valid when one of the gate values is dragged in
the Wedge screen. (See Figure 4-40)
The minimum and maximum gate values can also manually be moved in
the Wedge screen by dragging them with the mouse.
When the maximum depth gate is out of range of the wedge and therefore
not displayed it is most easy to move the pointer at the outer nadir range
of the wedge, click (pointer becomes a double arrow) and drag it inside
the wedge. On this way the maximum depth gate is moved inside the
range of the wedge as illustrated in Figure 4-40.
Figure 4-40 Wedge with maximum depth gate not displayed. Pointer moved
to Nadir outer range of wedge and maximum depth gate dragged back into the
wedge.
In case a maximum gate is dragged outside of the wedge range the gate
will get the maximum value (for the depth gate 400m).
Figure 4-41 Depth gate with a depth gate tilt of 0° (left) and 15° (right)
The range gate will use the minimum and maximum range values as
entered. Only the bottom returns which are within these limits will be used
in the bottom detection process.
The minimum and maximum gate values can also manually be moved in
the Wedge screen by dragging them with the mouse as the depth gate.
(See Depth Gate)
The adaptive gate will use the minimum and maximum nadir depth values
as entered. It will search for the strongest bottom return from the nadir
beam based on the window size.
When the Follow seafloor checkbox is ticked and the minimum or
maximum nadir depth values approach the nadir search limits, the nadir
search gate will automatically center the nadir search on the detected
seafloor
The nadir search limits can manually be moved in the Wedge screen by
dragging them with the mouse.
The window size is used to define the gate limits around the detected
seafloor. The distance between the limits and the detected seafloor is the
percentage of the detected bottom depth value. The percentage is the
value as entered as window size. Increasing the window size will make
4.7.4 Tracker
The Tracker function is enabled or disabled in the Sonar UI toolbar. (See
page 12)
With the tracker the sonar can set based on the quality of the collected
data automatically the:
Range
Power, gain and absorption
Pulse length
Coverage Angle
By selecting the associated checkboxes it is defined which setting(s) is
set by the tracker.
Select the Coverage angle Enable checkbox to set the coverage angle of
the sonar automatically by the tracker.
Select the ‘fixed swath width’ checkbox, to maintain the swath width as
specified in the Swath width field independent if the depth or other
circumstances changes.
Select the ‘Limit coverage angle’ checkbox to limit the coverage angle to
the specified maximum.
4.7.5 Snippets
The snippets window is the number of samples on each site of the bottom
detection point. By default the snippet window is set to automatic.
Uncheck the checkbox and a number of samples could be set manually
(Minimum of 10 and maximum of 300).
Vernier parameters are only available from the detection pane when a
multi-ping forward looking sonar system (e.g. 7130) is used.
Three parameters are set:
Mode:
-Vernier
-Triple array Mag & Phase
The filter settings lets the operator choose whether a FIR (Finite
Impulse Response) low-pass filter is applied to the raw signal
prior to elevation computation by Vernier processing. For
bathymetry, a typical setting would be a rectangular filter of 19
taps. The longer the filter the smoother the output. For target
detection, a short filter or no filter is the preferred setting. The
Hanning filter favors the samples close to the center of the filter
window. For a given length it will have less effect than a
rectangular filter.
Filter length
Only the selected screen(s) as set in the main pane are displayed in the
display pane.
The Display pane contains settings for each screen. For the Wedge,
Water Column and Detect screen most of the settings are also available
in the context menus (see also Screens on page 65).
The Wedge, Water Column and Detect screen have in addition to the
general settings several “layer” settings with various features which can
The Active Sonar Targets Layer is only available if a forward looker sonar
is connected to the SUI.
In the Active Sonar Targets layer the user can set the trace color of the
contact, the symbol of the contact, the name of the operator, and the
classification.
The classification is a comma separated field. The user can add a
classification. The default classification list is loaded when all
classifications in the field are deleted.
A 7k 3001 record is sent from the 7kCenter and recorded in the 7k log file
(.s7k) if a contact is created. The specified operator name and
classification is included in the 3001 record and s7k log file.
See for more information about creating contacts chapter Sonar Contacts
on page 72.
The Contact History period is the time the contacts will vanish if there is
no navigation received in the 7k IO. Otherwise all the contacts remain
visible in the Wedge since the contacts do not move with the vessel
movement.
The sensor data can only be recorded when these sensors are interfaced
with the sonar system. This can be done in the IO Module. An alternative
is that the position, attitude and heading are send by Teledyne PDS to the
IO Module. Then only the external clock with 1PPS and the sound velocity
has to be interface in the IO Module.
The Status box lists the status of the Raw Data Recording with the current
file name, size of the recording file, records logged, the number of records
that are added to the recording file, and the percentage of free disk
space.
With increased range and/or ping rates, the recording files will become
quickly very large. It is best to monitor the file sizes and ensure that 10%
of the disk space is always left available for system operation. Therefore it
is advisable to record the data on a separate hard disk and not on C:\.
4.10 Hardware
In the Hardware the operator can setup the following:
Deck Mode
Motion Stabilization (see page 52)
PPS Configuration (see page 53)
Trigger Configuration (see page 54 )
Ping Settings (see page 54)
Bracket (see page 57)
Normalization details (see page 58)
Dual Head (see page 55)
Currently only the RESON T20-S has the Deck mode option.
Selecting deck mode will disable the electronics to avoid the electronics
will overheat while the data files are transferred from the system.
The roll and pitch stabilization is only available when it is defined in the
xml file of the sonar. It is possible that only the roll or pitch stabilization is
available in the hardware settings. This depends on the type of the sonar.
It is recommended that the motion sensor data update rate is at least
50Hz and preferably 100Hz. Baud rate and protocol details can be set in
the Motion Stabilization, but it should be ensured that the baud rate is
sufficient to allow the desired update rate. The motion sensor data for the
motion stabilization is read directly from the FPGA, so no port has to be
selected.
When the vessel rolls the swath is rotated and the projected swath on the
seafloor is laterally displaced.
This has the effect of reducing the usable swath width due to the
distortions on the edge.
With the input from a motion sensor (and roll stabilization enabled) to
steer each receive beam dynamically for every sample, the swath stays
vertical irrespective of vessel motion thereby maximizing swath.
The Trigger Configuration allows the operator to control the pulse length
and delay characteristics.
When the trigger input is enabled (Active) the ping will occur upon receipt
of the input trigger pulse. If the trigger pulse rate exceeds the sonar’s
actual maximum ping rate for that range setting, some trigger input pulses
may be dropped.
When the trigger input is disabled the sonar will return to ping at the rate
dictated by the settings in the main and advanced Control pane.
By default the trigger output is enable (Active). This means that a pulse
will be generated in conjunction with the sonar ping.
Figure 4-66 Example of trigger output with Delay = 0 and Pulse length = 1
The Delay allows the operator to specify how many milliseconds after the
sonar ping the output pulse will be sent.
The Pulse length allows the operator to change the pulse length of the
transmitted output signal.
When the checkbox ‘Entire RX duration’ is checked the trigger out is
enabled for the entire RX duration.
The 7K system which enables the connection becomes the ‘Master’ and
the other system automatically becomes the ‘Slave’.
When the system is in ‘Slave’ mode then the Tracker button is disabled.
The master and slave X, Z offset must be entered with respect to the
vessel reference point.
In normal mode the heads ping in turn (ping-pong mode). The maximum
ping rate is half of a single head system.
Optionally the heads can ping simultaneously at a high ping rate. This is
the Full Rate Dual Head mode (FRDH). In FRDH mode the ‘Master’
system trigger the ‘Slave’ system. For this purpose a trigger cable is
connected between both systems. This cable is connected between the
Master system Trigger Out port and the Slave system Trigger In port.
When the SUI runs on the ‘Master’ system then both sonar wedges
(master and slave) can be monitored in the Wedge screen (see page 70).
For an integrated dual head system are two sonar heads connected to a
single sonar processor.
The port and starboard X, Z offset must be entered with respect to the
vessel reference point.
In normal mode the heads ping in turn (ping-pong mode). The maximum
ping rate is half of a single head system.
Optionally the heads can ping simultaneously at full rate. This is the Full
Rate Dual Head mode (FRDH.
4.10.7 Bracket
Only for the custom configuration the operator can set the X, Y and Z
offsets.
When using the reversed bracket then the beams are reverted therby
normalizing the image and the generated data output again.
See also the Sonar Operate Manual for more bracket details.
4.10.8 Normalization
The pipe detection settings are set on the Pipe pane. (See section 4.11).
4.10.10 Cable
The cable length is used to adjust the transmitter TVR curve.
It is essential the correct cable length is specified. A wrong
cable length can damage the system!
4.11 Pipe
In the Pipe pane the operator can set the settings for the pipe detection
and tracking. The following section are available:
Pipe in sway detections (see page 61)
Pipe parts creation (see page 62)
Pipe route creation (see page 63)
Pipe steering (see page 63)
Five points environment (see page 64)
On top of the Pipe pane the pipe detection can be switched on/off by
checking or unchecking the Enable checkbox.
The pipe gating can be switched on/off by checking or unchecking the
Pipe gating checkbox.
The detections in a sway are done in a pipe window that goes from beam
to beam through the sway data. The pipe window is a window with the
width of the pipe diameter plus a margin that is placed over the ping to
find the best detection.
With the pipe detection parameters, beams will be discarded as noise and
from the beams in the sway that are not discarded the best detection will
become the pipe detection in the sway.
Pipe parts are pipe detections in a patch of 25 pings that will be joined
together as a possible part of the pipe.
The pipe segment length defines how many points will be outputted to
the pipe route. For each pipe segment one output point. E.g. when the
pipe segment length is set to 5meter, each 5 meter a point is output to
the pipe route.
When a pipe segment is the start, the end or next to a gap of the pipe
route an additional point will be added to the route.
When more pipes or pipe parts are detected the Sonar UI will take an
average of the pipe (parts) positions to calculate a steering angle. The
pipe with the best quality of detections will have a bigger weight in the
When horizontal steering is selected the Sonar UI will change the horizon
steering in the RESON Sonar 7k sonar when the Sonar UI calculates that
it is needed.
The Flex mode has to be When flex steering is selected the Sonar UI will change the angle of the
selected in the RESON center beam of the flex mode in the RESON Sonar 7k sonar when the
Sonar 7k, before the flex Sonar UI calculates that it is needed. The width of the flex mode and the
steering can work. settings of the flex mode will not be changed.
When the pipe is detected 5 point on and around the pipe will be
computed and outputted to generate a basic profile of the seafloor with
the pipe.
The five points are the top of pipe, the seafloor on both sides of the pipe
(as close as possible to the pipe) and the seafloor on both sides further
away from the pipe (maximum sample offset). The five point information is
output on each segment length. See section 4.11.3.1.
It is essential the correct offsets and head tilt parameters are defined in
the hardware pane.
4.12 Screens
It is possible in the Operation mode to display four different screens:
The wedge
The Detect or Water column
Sidescan
Snippets
The screens are switched on/off in the Main pane (see page 23).
With the toolbar quickly screen related parameters can be set by the
operator as also done in the Display pane.
Table 1 summarizes the toolbar buttons for the Wedge, Detect and Water
column screen.
Table 1: Toolbar buttons: Wedge, Detect, Water column screens
Zoom extent.
Beam selector.
Save a snapshot.
Table 2 summarizes the functions of the toolbar for the Snippets display.
Zoom extent.
Invert colors.
Save a snapshot.
Some of the context menu options are also available in the Display pane
(see page 45).
Figure 4-87 Wedge screen with beam data color mode on Quality
4.12.4.4 Contrast
At the lower left corner the current level for the contrast is indicated.
Define in the Display pane how the history is displayed in the Wedge by
setting:
History Length: the length of the history in pings.
Swath Shift: the direction of the history in the display.
Swath Spacing: the distance between the swaths.
Both sonar wedges can be displayed for sonars in dual head mode
4.12.4.6 Measurement
When pressing ‘M’ on the keyboard a distance measurement function
becomes active. Click in the wedge and drag the cursor to a point to
measure the distance between the two points.
Deactivate the measurement function by pressing ‘M’ again.
A sonar contact is created from the wedge context menu. Right click in
the Wedge to open the context menu and select:
Continuous contact mode
To create a contact each time you click in the wedge on the
objects of interests. Right click to disable the continuous contact
mode.
Create Sonar Contact
Click in the wedge on the object of interest to create the contact.
Delete All sonar Targets/Contacts
To delete all the sonar contacts. The contacts are also deleted if
the SUI is closed.
A contact can only be created in the Wedge not outside the Wedge.
If a contact is created then a dialog opens to enter a description of the
created contact. Enter a description and click Apply.
In the Active Sonar Targets Layer of the Display pane the sonar contact
attributes can be configured. In this layer the operator name can be
entered also. See chapter Display on page 45.
Classification
Change the classification of the contact. Classification types can
be added in the Display pane, the Active Sonar Targets layer.
Delete Sonar Contact
To delete the sonar contact.
Edit Sonar Contact
To edit the sonar description.
Set New Sonar Contact Position
Click in the wedge on the new location. The contact is moved to
this position.
The contacts are dynamically displayed in the Wedge if navigation data is
connected and setup in the 7k IO module.
Set in the Hardware pane the Offsets and the Head Mounting angles.
Measure the offset from the Vessel Reference point to the Sonar
Reference point.
The 7kcenter will send a 3001 Contact Output record each time a sonar
contact is created, contact information is edited or when the contact is
Figure 4-95 Water Column screen with the selected beam over a wreck
The beam can be selected with the from the toolbar in the Wedge
screen (see Table 1) or in the Display pane under Water Column (see
page 45).
The legend for the multibeam data color mode(Fixed, Quality, Detection
Process and Uncertainty) is shown in the lower right corner of the screen.
This legend (Data Layer) cannot be switched off in the Display.
The grid lines (Grid Layer) can be switched on/off in the Display pane
(see Figure 4-50).
4.12.7 Sidescan
The Sidescan screen shows an image of the seafloor which can be used
to locate and identify features and bottom conditions. Each sonar ping is
used to generate a line of data. Each line contains a series of amplitudes
representing the signal return versus time or range. When a series of
these lines is combined and displayed as the vessel moves along the
track, a two-dimensional image is formed, providing a detailed picture of
the bottom along either side of the vessel.
The sidescan data can be viewed on a waterfall display representing the
results of a peak-detect search through the left and right beams of the
swath.
By default the scaling of the data is set on Auto Scaling. Deactivate the
Auto button in the toolbar and the operator can manually set the
threshold, gain and TVG for the picture in the Sidescan screen.
The waterfall data is automatically adjusts to the ranges in the history.
provide a more detailed picture of the seafloor. This image can be used
together with bathymetry to identify features and to help ensure that the
survey does not miss any small but significant targets.
For integrated dual head systems only the side scan data of the port head
is showed.
4.12.8 Snippets
The Snippets screen shows the backscatter data in a waterfall display.
receiver
A single beam
Seafloor
4.12.9 Helmsman
The helmsman screen is used in combination with the pipe detection
functionality as navigation guidance for the operator (e.g. ROV pilot). It
displays the pipe detection and the pipe route relative to the the position
Figure 4-100 Helmsman screen with warning distance indication (In this
example when the distance exceeds 4 meters)
5.1 Introduction
The Service view in the Sonar UI monitors the status of the complete
sonar system; the temperature, voltage, communication status and other
parameters.
With the diagram of the sonar system together with the related BITE
(Built-In Test Environment) information, it is easy to check if each part of
the system is working fine. It is quickly apparent, for instance, if a
component, wire, or pin is the cause of an error or warning. A BITE
snapshot can be saved in HTML format.
The Service mode is selected in the Sonar UI Toolbar (see Service Mode
on page 16).
This chapter will explain how the user can go through the different options
to monitor the system or, if necessary, find the reason for the error.
5.3 Information
The available information of the sonar system is displayed on the right
side in the Service. The different types of information will be ordered
under several tabs:
5.3.1 Status
On the Status tab the errors or warning of the system are displayed.
When no error or warning occurs this page will be empty.
A message will be displayed on the Status tab for each part of the sonar
system in error.
5.3.2 Details
In the Details tab the BITE information of the selected component, wire, or
pin in the diagram will be displayed. Press Ctrl+B on the keyboard to
access more information for some items in the diagram.
At the top the name and unique ID of the selected component, wire, or pin
is given. Below this the available BITE information is displayed with the
actual value or status for each item. The accepted range for each item is
displayed between brackets.
When an error or warning occurs for one of these items a message will be
displayed on the Status tab (see 5.3.1 above). On the Details tab the
information is also updated as shown in Figure 5-5.
Errors and warnings occur when an item exceeds a specified minimum or
maximum level and/or exceeds a specified time limit.
The error status for each item has an internal error status which is
incremented when there is an error and decreased if not. When there are
many errors close to each other in time, the error status will increment
above 1 and the status goes to ‘Error’. After a while with few or no errors
the error status will crawl down and come below 1, the status goes back
to ‘Ok’. The tolerance to the errors and the time errors are remembered
are controlled by the ‘min’ and ‘max’. So for the error counters the min
and max are not just limits used for comparison.
This means that for example an error message occurs when the head
FPGA exceeds a certain temperature (level) but also when the PPS
pulses are not received (exceed a time limit).
When the error message is a time out it means that for a specific number
of seconds no information is received from the system.
The BITE file for all the information displayed in the Details page is made
for the Virtex6 hardware. Therefore the Virtex6 items in the Details page
will all be zero when Virtex2 hardware is used. The operator should
ignore the Virtex6 information when Virtex2 hardware is used.
5.3.3 IO Module QC
In the IO Module QC tab, the data from the different devices interfaced
and set up in the IO Module, are displayed.
For each device the data string is unpacked and the data is displayed as
it is received from the 7k center through the IO Module. See Figure 5-8.
The BITE LED on the Sonar UI Toolbar will also turn red. See Sonar UI
Toolbar on page 12.
The status of the message fields are indicated by symbols:
: All items ok
: No data in datablock. (Some device drivers expect a certain
data field while it is not outputted by the connected device. It is
still possible to use this driver as long the required data field is
available.)
: Invalid data; one or more items failed to unpack.
The status indication is with respect to the last received data block. This
means the field can still marked as ok while the status box indicates time
out. (As it was received previously correct.) See Figure 5-10.
The raw data as received from the IO Module is displayed. These are the
data strings of all the data that is received on the different ports. When in
the IO Module pane for the ‘Input Distribution’ an destination address is
6.1 Introduction
This section highlights the dual head configuration in the SUI when two
systems (sonar heads) are used. One system is designated as a Master
and the other as Slave system.
6.2 Setup
The sonars must be connected and interfaced as described in the
RESON user manual.
The Master and the Slave Processors must have, within their range, a
different IP number (E.g. 10.11.10.1 and 10.11.10.2)
There are two modes for a Dual head system a ‘ping pong mode’ (The
Sonars ping in turn) or Full Rate Dual Head mode (FRDH). (Sonars ping
in a maximum possible rate.) The full rate mode is an option.
For a Full Rate Dual Head configuration (FRDH) the processors must be
triggered. For this purpose a cable must be connected from the ‘Master’
processor trigger out socket to the trigger input socket of the ‘Slave’
processor.
For a Full Rate Dual Head configuration the transmit pulse type must set
in FM for both the Master and the Slave. For feature packs higher as
version 4 (FP4) the pulse mode will set automatically into FM mode when
full rate is selected.
The following table lists the steps to select FM as pulse type in the SUI. It
is only necessary to change the setting in the Master. The setting is
mirrored to the Slave.
Step Action
1 Select the Advanced pane
2 Set in the Transmit features the Pulse type to FM.
Step Action
1 Select the hardware pane .
2 Open the Dual Head branch (node).
3 In the properties:
a. Select the Dual head mode: Tick the checkbox for full
rate mode, untick the check box for normal ‘ping-
pong’ mode. In the normal mode the ping delay could
be set. This delay is inserted before the other head
pings to avoid interference with the slave head.
b. Click the arrow key for a drop down list, and select
the slave processor’s IP address. (A proper network
connection between the two processors is required
before the slave IP address is listed.)
c. Tick the ‘Connect’ checkbox. The master will be
connected with the Slave.
Enter the Master and Slave sonar offset with respect to the
vessel’s Centre Reference Point (CRP).
The offsets are from the sonars acoustic center to the CRP of
the vessel. On the moment of writing it is only for proper
indication of the wedge and therefore doesn’t need to be set
very accurate.
Two wedges appear at the master SUI. One for the Master and one for
the Slave sonar.
Hover with the cursor over the head for a Master/Slave indication text
box.
Both master and slave snippets data (when available) will be displayed
as well in the master snippets screen.
6.3 Control
As the Master dictates when the slave sonar will cycle, most functions in
the Slave Sonar are mirrored from the master, and therefore not possible
to change in the Slave.
Main Pane
All functions X
Advanced Pane
Beam mode X
Steering The steering value could be
changed at the slave. But as
soon the master steering
value is changed, this will set
the slave steering value with
the master setting.
Coverage The coverage value could be
changed at the slave. But as
soon the master coverage
value is changed, this will set
the slave steering value with
the master setting.
Max Rate X
Frequency X X
Pulse type X X
Absorption X
Spreading X
Sound velocity X
Detection Pane
Depth gate X
Range gate X
Adaptive gate X
Tracker X The Tracker mode is enabled
from the Master. The master
will control the Slave settings
except the power and gain;
these are controlled by the
slave. It is however not
possible to enable the tracker
conditions as power and gain
from the slave. This is done
by the master.
Coverage angle X
Multi-detect X
6.4 BITE
The BITE LED indicates the (Alarm) status both for the Master and Slave
system. A red BITE indicates an error in the Slave or in the Master. To
access and check the service menu for the Slave it is necessary to open
the Slave by the slave sonar address as discussed in the ‘Setup’ section
above. When in the Slave, access the service menu for fault finding the
Slave system.
7.1 Introduction
As described in the section ‘Recording’ on page 48 it is possible to store
selectable records created by a RESON multibeam: the Raw Data
Records (RDR). RDR is a feature of the 7K Control Center (not from the
SUI). Storage of records could be locally on the RESON processor, but
could also be on an external device as another computer, or a Network
Attached Storage (NAS) drive.
For some configurations, Windows settings needs to be configured (e.g.
file sharing, creating a workgroup etc.). For this document the necessary
Windows 7 operating system settings are described.
This document discusses the setup for RDR but is also applicable for AVI
recording.
7.2 Scenarios
For this document we define five scenarios:
For a common 7K Gx (where x is a generation number) processor:
RDR on a Gx processor.
RDR on an external (customer) computer.
RDR on a Network Attached Storage (NAS) drive.
For a T20 processor:
RDR on a connected computer in a local network (E.g.
workgroup).
RDR to a connected computer in a domain.
Local drive
Records and folder path could be set in the SUI Record page. See
section ‘SUI record and file path selection’ on page 109 for the procedure.
Storage
drive
Network
7KC
SUI
RDR Optional acc software
Optional
external
storage drive
7K Processor
2. Select the records to be logged and the shared folder in the SUI’s
recording pane. See section ‘SUI record and file path selection’
on page 109 for more details.
LAN1/ Storage
LAN2 drive
Network
7KC Acq software
RDR SUI (E.g. PDS) Optional
external
storage drive
T20 (PSP)
LAN1/ Storage
LAN2 drive
domain
4. Select the records to be logged and select the external computer’s created shared folder
in the SUI’s recording pane. See section ‘SUI record and file path selection’ on page 109
for more details.
It could be necessary to enable ‘Network discovery’ in the advanced sharing settings. See
section ‘file sharing’ on page 104 how to access the advanced sharing settings.
100 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
Step Action
2 Open the windows Control panel.
3 Open ‘System’
4 a. A overview is listed with the computer name and current
Workgroup(name).
b. Click ‘Change settings’ to modify.
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 101
Step Action
6 Tick the checkbox ‘workgroup’ and give the workgroup a
name. (Default Windows name is WORKGROUP, for the T20
PSP this is default RESON). The workgroup must be equal as
the other connected computers/processors.
Step Action
1
Open the windows start menu.
2 Open the windows Control panel
102 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
Step Action
4 Click ‘Change adapter settings’.
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 103
Step Action
8 a. Tick the checkbox ‘use the following IP address’.
b. Enter the IP address. (In this example 10.4.0.1).
c. Enter subnet mask 255.255.255.0
d. Click ‘OK’.
Step Action
1 Open Windows Explorer.
2 Make or create a new folder to be shared.
104 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
Step Action
3 Right click on this folder and click ‘Share with’ from the context
menu, followed by ‘Specific people.’
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 105
Step Action
5 Click ‘Add’.
6 Click the arrow to change the Permission Level from ‘Read’ into
‘Read/Write’.
106 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
Step Action
7 The folder is shared.
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 107
Step Action
2 Open the windows Control panel.
108 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
Step Action
Step Action
1 In the SUI, open the Recording pane.
2 Select the required records by ticking the checkbox(es)
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 109
Step Action
1 Open the SUI’s Application Setting Dialog box.
110 Appendix Raw Data Recording (RDR) SeaBat Sonar UI - User Manual
See Figure 7-12.
a. The file name.
b. And the file size is indicated in the SUI’s recording pane.
SeaBat Sonar UI - User Manual Appendix Raw Data Recording (RDR) 111
8 Appendix C – 3001 Contact
Output record
8.1 Introduction
The 7k 3001 – Contact output record is created by the 7kCenter if a sonar
contact is created / modified or deleted in the sonar UI.
Sonar Contacts can only be created if a forward looker sonar is
connected to the sonar UI
See for more information about the 7k format the document ‘DATA
FORMAT DEFINITION - 7k Data Format’.
SeaBat Sonar UI - User Manual Appendix C – 3001 Contact Output record 113
Name Size Description
Latitude f64 Latitude of contact in radians -π/2 to π /2, south
negative
Longitude f64 Longitude of contact in radians -π to π, west
negative
Azimuth f32 Optional azimuth of contact in radians
Contact length f32 Optional length of contact in meters
Contact width f32 Optional width of contact in meters
Classification utf * 128 Optional textual classification given by the operator
Description utf * 128 Optional textual description given by the operator
114 Appendix C – 3001 Contact Output record SeaBat Sonar UI - User Manual
9 Appendix Copyright
Information
9.1 Glew
The OpenGL Extension Wrangler Library
Copyright (C) 2002-2008, Milan Ikits <milan ikits[]ieee org>
Copyright (C) 2002-2008, Marcelo E. Magallon <mmagallo[]debian org>
Copyright (C) 2002, Lev Povalahev
All rights reserved.
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Materials.
THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
─E─
Index Equi-Angle - 27
Equiangular - 27
Equidistant - 28
Equi-distant - 28
External Clock - 35
─F─
Flex Steering - 64
Flexmode - 29
Floating - 7
─1─ FM - 32, 55
Frequency - 4, 31, 32
1PPS - 4, 18, 37, 50, 53
─G─
─7─
Gain - 4, 24
7KControlCenter - 3
Guide Diamonds - 7
─A─ ─H─
Absorption - 32, 33
Hardware - 51
Active Sonar Targets Layer - 47
Heading - 36, 49
Adaptive Gate - 41
helmsman - 77
Attitude - 36, 49
Help - 16
AVI File - 17, 51
Helsman - 26
AVI Recording - 17
Horizontal Steering - 30, 64
HTML File - 82
─B─
Backscatter - 49 ─I─
Beam Mode - 4, 27
Input distribution (RRIO - 36
Beamformer - 58
Intermediate - 28
Beamforming - 35
IO Module - 4, 22, 35, 36, 50, 56, 85
BITE - 16, 80
Bracket Configuration - 57
Brightness - 62 ─J─
JPG File - 16, 51
─C─
classification - 47 ─L─
Colinearity - 62 Layout - 12
Compressed water column - 49 Licensed Features - 16
constant spacing - 29
Context Menu - 11, 46, 68
Coverage Angle - 31 ─M─
CW - 32 Main - 22, 23
Main pane - 4
─D─ Maintain swath coverage’ - 29
multibeam data color mode - 47
Depth Gate - 39
Depth Gate Tilt - 41
Detect - 46, 75 ─N─
Detection - 39 Nadir Search Gate - 41
Diagram - 16, 80 Normalization - 58
─P─
Ping Rate - 25
Ping Settings - 55
Pipe Diameter - 61
Pipe pane - 60
Pipe Part - 63, 64
Pipe Window - 61
Pitch Stabilization - 17, 53
Position - 36, 49
Power - 4, 24
Pulse Length - 25
Pulse Type - 4, 32
─R─
Range - 4, 23
Range Gate - 41
Rate - 25
Recording - 23, 48
Remote desktop - 14
Reset - 12
Restore factory settings - 13
Roll Stabilization - 4, 18, 52
─S─
S7K File - 17, 36, 49
Salinity - 32
Service - 16
Side lobes - 58
Sidescan - 26, 75
Snapshot - 16
Snippets - 26, 49, 76
Sonar Address - 16
Sonar network connections - 14
Sound Velocity - 30, 33, 35, 49
Spreading - 32, 33
SVP Filter - 33
─T─
Teledyne PDS - 36
Toolbar - 12
Tracker - 17, 56
Trigger Configuration - 54
TVG - 24, 32, 33
─W─
Wake up - 14
Water Column - 26, 46, 74
Wedge - 26, 46, 70