PDS2000
Version 4.2.4
March 2013
RESON B.V.
Stuttgartstraat 42- 44
3047 AS Rotterdam
The Netherlands
2 PDS2000 Documentation 3
2.1 Introduction ............................................................................................................. 3
2.2 Overview ................................................................................................................. 3
2.2.1 Anchor Handling ........................................................................................... 3
2.2.2 Bar Sweep..................................................................................................... 3
2.2.3 Boeilog .......................................................................................................... 4
2.2.3.1 Appendix Boeilog................................................................................. 4
2.2.4 Boraciet ......................................................................................................... 4
2.2.4.1 Addendum Boraciet ............................................................................. 4
2.2.5 Bottom Classification .................................................................................... 4
2.2.6 Bucket Dredging ........................................................................................... 5
2.2.7 Cable Lay ...................................................................................................... 5
2.2.8 Cutter Dredge ............................................................................................... 5
2.2.9 ES3 ............................................................................................................... 5
2.2.10 Excavator .................................................................................................... 5
2.2.11 Frequently Asked Questions ....................................................................... 6
2.2.12 HydroBat ..................................................................................................... 6
2.2.13 Interface Setup ............................................................................................ 6
2.2.14 Multibeam.................................................................................................... 6
2.2.15 Multibeam Calibration ................................................................................. 6
2.2.16 PDS2000 LiteView ...................................................................................... 7
2.2.17 PDS2000 User Manual ............................................................................... 7
2.2.18 Pipe Detection ............................................................................................. 7
2.2.19 Pipe Position Monitor .................................................................................. 7
2.2.20 Pipe Position Monitor J-Lay ........................................................................ 8
2.2.21 Rope Excavator .......................................................................................... 8
2.2.22 Slope Protection .......................................................................................... 8
2.2.23 Sonar Swath ............................................................................................... 8
2.2.24 Tide Application .......................................................................................... 9
2.2.25 Trailing Suction Hopper .............................................................................. 9
2.2.26 Trencher ...................................................................................................... 9
2.2.27 USBL ........................................................................................................... 9
3 Installation 11
3.1 Introduction ........................................................................................................... 11
3.1.1 Requirements .............................................................................................. 11
3.1.2 Memory Improvement ................................................................................. 12
3.2 Install PDS2000 .................................................................................................... 12
3.2.1 Start PDS2000 Installation .......................................................................... 12
4 Using PDS2000 47
4.1 Introduction .......................................................................................................... 47
4.2 Docking ................................................................................................................ 48
4.2.1 Dock Areas ................................................................................................. 49
4.3 Context Menus ..................................................................................................... 49
4.4 Navigation in a 3D View ....................................................................................... 50
4.4.1 Rotate the Data .......................................................................................... 50
4.4.2 Shift the Data .............................................................................................. 51
4.4.3 Zoom in/out in the Data .............................................................................. 51
4.4.4 Scale the Data ............................................................................................ 51
4.4.5 Center the Data .......................................................................................... 51
5 Starting PDS2000 53
5.1 Introduction .......................................................................................................... 53
5.1.1 Project......................................................................................................... 53
5.1.2 Application Type ......................................................................................... 53
5.1.3 Configuration .............................................................................................. 53
5.2 Project Structure .................................................................................................. 54
5.3 Projects Common Files ........................................................................................ 54
5.4 New Project Wizard .............................................................................................. 55
5.4.1 Project Configuration .................................................................................. 57
5.4.1.1 Description ........................................................................................ 57
5.4.1.2 Units .................................................................................................. 58
5.4.1.3 Coordinate System ........................................................................... 58
5.4.1.4 Formats ............................................................................................. 59
5.4.1.5 Log Files ............................................................................................ 59
5.4.1.6 File History ........................................................................................ 61
5.4.1.7 Disk Space ........................................................................................ 61
6 Coordinate System 71
6.1 Introduction ........................................................................................................... 71
6.2 Project Coordinate System ................................................................................... 72
6.3 Coordinate System Wizard ................................................................................... 73
6.3.1 New Coordinate System ............................................................................. 73
6.3.2 Select Coordinate System .......................................................................... 74
6.3.3 Ellipsoids ..................................................................................................... 75
6.3.4 Datum Transformation ................................................................................ 76
6.3.5 Select Datum Transformation ..................................................................... 77
6.3.6 Datum Transformation Parameters ............................................................ 78
6.3.7 Geoid Model ................................................................................................ 79
6.3.8 Unit .............................................................................................................. 81
6.3.9 Projection .................................................................................................... 82
6.3.10 Select Projection ....................................................................................... 83
6.3.11 Projection Parameters .............................................................................. 84
6.3.12 Post Correction ......................................................................................... 85
6.3.13 Save Coordinate System .......................................................................... 86
6.3.14 Coordinate System Overview ................................................................... 87
6.4 Edit Coordinate System ........................................................................................ 87
7 Vessel Configuration 91
7.1 Introduction ........................................................................................................... 91
7.2 Setup a Vessel Configuration ............................................................................... 91
7.2.1 New Vessel Configuration........................................................................... 92
7.3 Geometry .............................................................................................................. 93
7.3.1 Vessel Contour ........................................................................................... 95
7.3.1.1 Import Vessel Contours ..................................................................... 96
7.4 Equipment............................................................................................................. 96
7.4.1 Sub System ................................................................................................. 98
7.4.2 Navisound Graphical Trace ........................................................................ 99
7.4.3 Outputs...................................................................................................... 100
7.5 Computations ..................................................................................................... 101
7.5.1 Advanced Computations ........................................................................... 101
7.6 Data Sources ...................................................................................................... 103
7.7 Guidance ............................................................................................................ 104
7.8 Tools ................................................................................................................... 105
8 Guidance 131
8.1 Introduction ........................................................................................................ 131
8.2 Route .................................................................................................................. 132
8.2.1 Route Editor .............................................................................................. 133
8.2.2 ASCII Import Wizard ................................................................................. 136
8.3 Runlines ............................................................................................................. 138
8.3.1 Runlines Editor ......................................................................................... 139
8.4 Waypoints .......................................................................................................... 141
8.4.1 Waypoints Editor ...................................................................................... 142
8.5 Design Model ..................................................................................................... 143
8.5.1 3D Design Model Editor............................................................................ 144
8.6 Cutter Dredge ..................................................................................................... 146
8.7 Work Areas ........................................................................................................ 147
8.8 Restricted Areas ................................................................................................. 148
8.8.1 Restricted Areas Editor............................................................................. 148
9 Events 155
9.1 Introduction ......................................................................................................... 155
9.2 Events Mode ....................................................................................................... 155
9.2.1 Mode ......................................................................................................... 156
9.2.2 Conditions ................................................................................................. 156
9.2.3 Push Button .............................................................................................. 156
9.2.4 Event Definition ......................................................................................... 156
9.2.4.1 Separator Delimited ......................................................................... 158
9.2.4.2 Fixed Field ....................................................................................... 158
9.2.4.3 Field Selection ................................................................................. 159
9.3 Events Data Source ............................................................................................ 160
9.4 Events Numbering .............................................................................................. 161
11 Explorer 209
11.1 Introduction ...................................................................................................... 209
11.2 Context Menus ................................................................................................. 210
11.2.1 General Context Menu ........................................................................... 211
11.2.1.1 Backup Files Outside Project ........................................................ 211
11.2.2 File Group Context Menu ....................................................................... 213
11.2.3 File Context Menu .................................................................................. 213
11.3 Projects Common Database ............................................................................ 214
11.4 PDS2000 Database ......................................................................................... 215
11.4.1 Convert S-57 to C-Map........................................................................... 217
11.4.1.1 Updates ......................................................................................... 219
11.5 Project Database .............................................................................................. 219
11.5.1 Clipping Polygons ................................................................................... 224
11.5.1.1 Clipping Polygon Editor ................................................................. 225
11.5.2 Color Tables ........................................................................................... 226
11.5.2.1 Color Table Generator .................................................................. 226
11.5.2.2 Color Table for Bottom Classification ........................................... 230
11.5.2.3 Dredge Differential Color Table .................................................... 231
11.5.3 Contour Definitions ................................................................................. 231
11.5.3.1 Contour Definition Generator ........................................................ 232
12 Acquisition 251
12.1 Introduction ....................................................................................................... 251
12.2 Start Acquisition ................................................................................................ 251
12.2.1 Simulation ............................................................................................... 251
12.2.2 Realtime .................................................................................................. 251
12.3 Data Visualization ............................................................................................. 252
12.3.1 Layout ..................................................................................................... 252
12.4 Acquisition Menu Bar and Toolbar ................................................................... 254
12.4.1 Selecting Guidance ................................................................................. 259
12.4.1.1 Making Runlines or Routes Real Time .......................................... 260
12.5 Logging ............................................................................................................. 260
12.5.1 Check the Logging .................................................................................. 261
12.6 Shortcuts........................................................................................................... 262
12.6.1 F-Keys ..................................................................................................... 263
12.6.2 Attribute Actions ...................................................................................... 265
12.6.2.1 Attach to Button ............................................................................. 266
12.6.3 Manual Input Actions .............................................................................. 267
12.6.4 View Attribute Actions ............................................................................. 267
12.6.5 Shortcut Keys .......................................................................................... 270
12.7 Presentations .................................................................................................... 270
13 Views 271
13.1 Introduction ....................................................................................................... 271
13.2 3D View ............................................................................................................ 272
13.2.1 3D View – Online .................................................................................... 273
13.2.2 3D View – Online Dredge ....................................................................... 274
13.2.3 3D View – Toolbar and Context Menu .................................................... 275
13.2.4 3D View – Layers .................................................................................... 277
14 Replay 389
14.1 Introduction ...................................................................................................... 389
14.1.1 Controlling the Replayer ......................................................................... 389
14.1.2 External Replay Settings ........................................................................ 390
14.1.3 Saving Layout and Vessel Configuration ............................................... 391
14.1.4 Recomputation and Saving Results ....................................................... 391
15 Processing 393
15.1 Introduction ...................................................................................................... 393
15.2 Validating and Presenting Survey Results ....................................................... 393
16 Editing 395
16.1 Introduction ...................................................................................................... 395
16.1.1 Available Editors ..................................................................................... 395
20 Plot 547
20.1 Getting Started ................................................................................................. 547
20.1.1 Create a Plot Project .............................................................................. 547
20.1.2 Add Data Files ........................................................................................ 549
20.1.3 Place a Plan View ................................................................................... 549
20.1.4 Create a Plot ........................................................................................... 551
20.1.5 Place Panels ........................................................................................... 553
20.1.6 Add Layers ............................................................................................. 554
20.1.7 Print or Export a Plot .............................................................................. 554
20.2 How Plotting Works .......................................................................................... 555
20.2.1 Regeneration .......................................................................................... 555
20.2.2 Panel and Layer Order ........................................................................... 556
20.2.3 Overwrite Suppression ........................................................................... 556
20.2.4 Templates ............................................................................................... 557
20.2.5 Keywords ................................................................................................ 557
20.3 Available Panels ............................................................................................... 557
20.3.1 Plan Panel .............................................................................................. 558
20.3.2 North Arrow Panel .................................................................................. 559
20.3.3 Profile Panel ........................................................................................... 560
20.3.4 Profile Volume ........................................................................................ 561
20.3.5 Profile Series Panel ................................................................................ 564
20.3.6 Profile Cross Series Panel...................................................................... 565
20.3.7 Profile Info Panel .................................................................................... 566
20.3.8 Text Block Panel and Text Box .............................................................. 566
20.3.9 DXF Panel .............................................................................................. 567
20.3.10 Color Mapping Panel ............................................................................ 568
20.3.11 Image Panel ......................................................................................... 568
20.3.12 Key Map Panel ..................................................................................... 569
20.3.13 Scale Bar Panel .................................................................................... 569
20.4 Available Layers ............................................................................................... 570
20.4.1 Clipping Polygon Layer........................................................................... 571
20.4.2 CMap Layer ............................................................................................ 571
20.4.3 Dredge Track Layer ................................................................................ 572
20.4.4 DXF Layer .............................................................................................. 572
20.4.5 Events Layer ........................................................................................... 573
20.4.6 Event Markers Layer .............................................................................. 573
20.4.7 Geographic Grid Layer ........................................................................... 573
22 Export 613
22.1 Introduction ...................................................................................................... 613
22.1.1 Export Configuration File ........................................................................ 613
22.1.2 Export Type ............................................................................................ 614
22.2 Export Window ................................................................................................. 615
22.2.1 Excel and Comma Separated ................................................................ 615
22.2.2 Simrad EM Datagram ............................................................................. 617
22.2.3 Multibeam XYZ ....................................................................................... 618
22.2.4 XTF ......................................................................................................... 620
22.2.5 S7K ......................................................................................................... 622
22.2.6 SDS ........................................................................................................ 622
22.2.7 SZ ........................................................................................................... 623
22.2.8 Magnetometer DAT ................................................................................ 624
22.2.9 FAU......................................................................................................... 625
22.2.10 GSF ...................................................................................................... 625
22.3 Exporting .......................................................................................................... 625
1.1 PDS2000
PDS2000 is a software package for hydrographic survey and dredging
operations. It offers modules that cover the entire operation from
acquisition to an end product. The software runs on standard PC’s with
the Windows operating system. PDS2000 is available in different versions
tailored to specific operations.
The purpose of all the measurements is real time reading of data from
one or more sensors, make computations with the data, show the results
of the computations and simultaneously log the data. To be able to control
those processes a number of Views has been developed that will show
the reading, computations, results and logging processes. A view can
show the data either graphically or alpha-numerically.
Data needs to be checked after the measurements. PDS2000 gives
several options to remove anomalies and outliers, either manually or
automatically.
The final presentation of the cleaned data can be in the form of models,
tables, files, volumes, nautical charts and reports.
This manual is also available as a HTML Help file. Press F1 or select
Help > Help Topics to open the PDS2000 help files.
2.1 Introduction
This chapter will give an overview of all the manuals that will be delivered
with a PDS2000 version.
All these documents are accessible as PDF via the Start menu of
Windows at the location Start > Reson > PDS2000 Vx.x.x.x > PDS2000
Documentation. The documents can also be found in the folder
‘C:\Program Files\RESON\PDS2000 Vx.x.x.x\manuals’.
2.2 Overview
The manuals are listed not in order of importance but in alphabetic order.
For each manual a brief explanation will be given.
2.2.4 Boraciet
The Boraciet application is meant to monitor on the shore the work and
movements of the (dredging) vessel. To monitor this a GPRS link is made
between the vessel and on shore (called ‘wal server’). With this link it is
also possible to send data to the vessels. The ‘wal server’ is the central
place where the information of the different vessels comes together.
On shore the ‘wal server’ is connected by Ethernet with several PC’s
(called ‘wal clients’). On these ‘wal clients’ the activities of the vessels can
be monitored online. It is also possible to replay the activities of the
vessels on the ‘wal clients’.
The documentation is in Dutch.
For more information see the file Boraciet.pdf.
2.2.9 ES3
This document is made as an additional section in the ES3 User Manual
to explain the setup of PDS2000 for the Odom ES3.
The Odom ES3 and the other sensors (navigation, motion, heading and
sv probe) are interfaced to the RTA (Real Time Appliance) box. Therefore
in PDS2000 the setup of the clock synchronization and the interface to
the different sensors is different from the standard interfacing in
PDS2000.
For more information see the file ES3.pdf.
2.2.10 Excavator
The application type ‘Excavator’ is for a project where an excavator is
used for dredging.
A project with the application type ‘Excavator’ can contain one or two
vessels. For a one vessel project the vessel is the excavator and for a two
vessels project the vessels are the excavator and a pontoon on which the
excavator is located.
In this application manual the setup of an excavator project for a stand-
alone excavator and for an excavator on a pontoon will be discussed.
After the project is setup the separate tools of the excavator configuration
2.2.12 HydroBat
The HydroBat is a multibeam system where the data collection and the
control of the HydroBat will take place in PDS2000.
An explanation of the setup of the HydroBat in the equipment list will be
discussed and the special views for the HydroBat in the Acquisition will be
explained.
For more information see the file HydroBat.pdf.
2.2.14 Multibeam
The Multibeam Survey application in the PDS2000 software is an
application type for a survey with one or more multibeam systems.
In this manual the equipment, which is necessary for a multibeam survey,
will be discussed and also how to setup PDS2000 for this type of survey.
For more information see the file Multibeam.pdf.
2.2.26 Trencher
In PDS2000 the application ‘Trencher’ is made for the support of a cable
trencher. The cable will be trenched with a cable trencher and in this
application the knife depth will be calculated to determine the burial depth
of the cable.
In PDS2000 two vessels have to be setup, one is the survey vessel and
one is the trencher. The trencher will be positioned by a USBL positioning
system.
In this document will be explained which equipment on the trencher and
on the survey vessel, next to the standard equipment, have to be
selected. After the setup the calibration will be explained and some views
in the Acquisition will be discussed.
For more information see the file Trencher.pdf.
2.2.27 USBL
In this manual the USBL (Ultra Short BaseLine) as used in PDS2000 will
be explained.
The USBL equipment has to be setup in the Equipment list of PDS2000.
A USBL transceiver device and a USBL transponder device has to be
selected and setup.
Before a USBL survey can be started, a USBL calibration has to be done
to find the misalignment of the USBL transceiver. In this manual the
procedure for the USBL calibration will be explained.
For more information see the file USBL.pdf.
3.1 Introduction
This part of the manual describes the minimum requirements, how to
install PDS2000, C-Map charts and Tresco charts on a computer and how
to configure the computer for optimum use with PDS2000.
3.1.1 Requirements
The supported operating systems are for 32 bit and 64 bit:
MS Windows XP Professional Service Pack 3 or higher
MS Windows Vista
MS Windows 7
The system requirements for a desktop and laptop system are:
Minimal requirements:
CPU: modern Quad Core Processor
Monitor: single monitor system
Graphic card with OPENGL support and 1 Gb of memory; i.e.
NVidia Geforce GTX 4xx
4 Gb internal memory
1 x 500 Gb Hard disk
DVD Writer
Multi serial I/O card
Preferred requirements:
CPU: 8 Core Processor
Monitor: dual monitor system
Dual Graphic card with OPENGL support and 3+ Gb of memory,
i.e. NVidia GeForce GTX 6xx or ATI Radion HD 79xx
Having a 32 bit operating
system limits the amount of 8 Gb internal memory
usable internal memory to
Raid 0 Hard disk system for data storage: 1 Tb minimum
4 Gb.
DVD Writer
Multi serial I/O card
The requirements for the PC are depending on the application. A single-
Do this only once! It will be remembered by Windows the next time the
system is started.
When these steps are not performed the application can only use the
default maximum memory. So it is not necessary to apply these changes
but when done you get more memory for the applications.
The modification is only needed for 32 bit Windows operating systems. 64
Bit Windows operating systems don’t need to be modified. They already
are able to give the applications memory allocation bigger than 2 Gb.
b. Before the actual installation will start the user has to select the type of
setup.
From this new PDS2000 version onwards PDS2000 will only run with
the new version of the C-Map software. Click on to start with
the installation of the new C-Map software. If the user clicks on
no C-Map software will be installed and PDS2000 will not run
with C-Map anymore. Only when the user install later on the new C-
Map software PDS2000 will run again with C-Map.
See the chapter ‘Installing and Using C-Map’ on page 24 for a detailed
explanation of the C-Map installation.
f. Click on in the next page of the install wizard to start the
PDS2000 installation. Click on to finish the installation.
Installing PDS2000 will place the PDS2000 and the Dongle software
on the hard disk of the computer.
PDS2000 V.x.x.x.x
Where x.x.x.x is the installed version number. This folder contains the
programs and supporting files to run PDS2000.
General
Contains device drivers and more supporting files.
GeoidModels
Contains the files with the geoid models (see page 79) and X, Y
Figure 3-6 Device Manager window with the Moxa extender card
d. Set the Rx FIFO Trigger to 1. Check the option Set the change to all
the ports and click on .
This sets the timing for all ports to optimal, giving the shortest possible
delays.
Select in window Found New Hardware Wizard dialog the option Yes, this
time only and click on to continue with the wizard.
Figure 3-10 The About Control Center window where the PDS2000 dongle
can be updated
When the dongle update is available with the latest PDS2000 installation
select the ‘All Dongles.dk4’ file. This file contains the dates for all
PDS2000 released dongles as maintained by RESON.
When the user has received a separate patch for his dongle then browse
to the correct folder and select the dk4 file as received from RESON.
Click on to start the update of the dongle. When the update is
not successful contact your local agent or RESON B.V. and inform them
on the internal ID and the dongle s/n.
The Remote Presentation should have the same version number as the
PDS2000 version on the main computer!!
a. Select the folder ‘CMap’ on the CD-Rom of PDS2000, and start the file
‘Setup.exe’.
It is very important not to install the driver when Windows detects the
eToken driver and wants to install it.
Figure 3-17 C-Map Professional SDK Setup with installation of the eToken
dongle and the C-Map software
The eToken PRO (32k) Select when the old eToken dongle is used, select
does not work on MS when the new dongle is used.
Windows 7 64bits!!!!!
d. It is possible that after the installation of the eToken driver or after
Figure 3-19 C-Map Professional SDK Setup with installation of the C-Map
software
Figure 3-20 Welcome page of the C-Map Professional SDK Runtime Setup
wizard
The diagonal of the main computer screen used for PDS2000 has to
be set. This will be used to find the best display resolution. Click on
when the diagonal is not known.
Click on after the right screen diagonal is entered.
When the C-Map software is installed on a computer where no C-Map
software was installed before then the next dialog will be ‘l‘.
j. When old C-Map software with a license was active before the new
software is installed then the next dialog will ask what to do with the
license.
The users who are only using the S-57 converted charts in C-Map can
skip the items b – h and continue with item i on page 33.
Figure 3-31 C-Map Chart Manager with the Professional+ database set as
default
To use C-Map with the Select the right database at the top and choose one of the license
same eToken dongle on a actions.
different computer the
same license information Click on when the user wants to read the usr file with
has to be activated again. the license information. Select the file and click on in the
‘Select a license file’ dialog to read the license code(s) from the file.
For clients who are only using the converted S-57 files select as
database ‘Software Modules’ and use always
this database does not have a Zone defined in the usr file.
because
Figure 3-34 Add License Manually window to add the license code(s)
Select the right zone with the right area and enter the license code as
given in the email or from the usr file. Click on to activate
the license for the selected zone. Repeat this for each zone and/or
area that needs a license.
Figure 3-35 Licenses page of the C-Map Chart Manager with a license for
a zone.
k. C-Map with the right database is now installed and can be used in the
views of PDS2000.
a. Place the new DVD with the database in the DVD drive and click on
.
3.3.0.0. But before it will work in one of these ‘old’ versions, the file
‘CMGBase.dll’ located in the ‘PDS2000 Vx.x.x.x’ folder of the ‘old’ version
has to be deleted.
In some dedicated plan views in PDS2000, C-Map can be viewed as a
layer. Click on in the toolbar or select Layer Control in the context
menu to get the Layers window.
C-Map charts are digitized with a precision of 0.3 mm. This results in
chart accuracy on the display, which is given in the table above for the
largest scale of each scale level.
Display Detail
For the details of the C-Map chart the options are:
Full shows all the soundings, texts etc.
Standard takes most soundings away.
Base shows only the minimum amount of information on the C-Map
chart.
Show Light Info
The light information can be switched on or off.
Show Generic Text
The names of ports and areas can be switched on or off.
Show Other Text
Additional text such as names of features can be switched on or off.
Anti Cluttering
Switch override suppression (C-Map's anti-cluttering engine) on or off.
Show Chart Boundaries
The red chart boundaries in the display can be switched on or off.
Use C-Map Filters
C-Map filters are not user definable. Contact RESON B.V. in case
special requirements for C-Map filters are needed. This function
enables or disables the filters.
C-Map Filter Name
At the moment three filters are available:
- No Buoys
- No Buoys and Beacons
- No Buoys, Beacons and Piles
These filters remove the filtered items from the chart.
The option ‘Install Sentinel driver’ should be selected when the Tresco
charts are installed for the first time and no Sentinel driver is installed
yet.
The other three options are not needed for a proper installation of the
Navigis software.
Click on to continue.
The selected folder should be identical with the folder that is selected
for the Navigis software in Figure 3-44 on page 39.
Click on to continue with the installation.
Don’t select the option ‘Install Sentinel driver’ because the driver is
already installed during the installation of the Tresco Navigis software.
Click on to continue with the setup.
d. In the next page the installation of the kernel can be started.
The Tresco kernel needs to know the width of the screen to calculate
the scale to display the charts in the correct scale on the screen.
Click on after the right screen width is entered and the
installation will be finished. Click on to finish the installation of
the kernel.
When no detailed information on the Tresco chart is displayed it is
possible that the file TE.PMT, which has to be used in conjunction with
the dongle, is not installed on the right location. Check if the file is present
on the DVD, if not contact RESON BV or Tresco about this problem. If the
file is present copy the file to the folder ‘C:\Navichart\S57’.
Display Detail
For the details of the Tresco chart the options are:
Full shows all the soundings, texts etc.
Standard takes most soundings away.
Base shows only the minimum amount of information on the Tresco
chart.
Show Geographic Names
The geographic names can be switched on or off.
Show Names For Position Reporting
The labels for the position reporting can be switched on or off.
Show Buoys and Beacons
The buoys and beacons can be switched on or off. The light for the
buoys and beacons can be switched on or off with the option ’Show
Lights’.
Show Lights
The light and the labels can be switched on or off.
Show Light Descriptions
The labels for the lights can be switched on or off.
This option will only work when the option ‘Show Lights’ is on.
Show Full Length Sector Lights
The full length for some of the sector lights can be switched on or
off. Most of the lights don’t have a full length option.
This option will only work when the option ‘Show Lights’ is on.
Text Resolution
The size of the text on the charts can be defined in dpi.
Symbol Resolution
The size of the symbols on the charts can be defined in dpi.
4.1 Introduction
PDS2000 is designed with a Windows ‘Look and Feel’. On top of that
PDS2000 has some additional features.
Docked
The view is fixed in one of the dock areas (see below).
Floating
The view is docked but movable. Floating views can be located
outside the window.
MDI Child
‘Multiple Document Interface’ child. The view behaves like any other
view in a Windows application.
Docked to
When pressed, the choice is given to dock a view to any of the four
dock areas (see below).
As shown above, the client area has four dock areas: top, bottom, left and
right. Each dock area can have multiple views.
With the option Displays the Displays window can be opened in which
views can be added, modified or removed from the module. The option
Add Display is a quick method to add a new view to the module. Check
one of the existing views and this view will appear in the module. When a
5.1 Introduction
The Control Center should From the Control Center every module of PDS2000 can be started. But
always be running while before one of the modules is started a project, an application type and a
PDS2000 is used. configuration have to be created or selected. The Control Center does not
start when no project is available.
5.1.1 Project
A project can be an area to be surveyed, a harbor to be made, a river that
has to be dredged to a navigable depth, etc. It may require the
employment of one or more vessels (survey vessels, dredgers, work
ships, excavators) and each vessel can have a special task in the project.
A project has the information on the method of measuring and all the
information necessary to do the measurements.
PDS2000 stores all the details of a project in one folder.
5.1.3 Configuration
A configuration describes the way an application type is carried out. It
contains the used vessel(s), the layout used for the Acquisition and (if
present) Presentation(s), how events are used and alarms are managed.
Multiple configurations are possible for all application types.
Any object that carries sensors is defined as a vessel in PDS2000. Some
application types can handle multiple vessels, and each vessel can have
multiple sensors. This makes it necessary to have a set-up for each
vessel in an application type. The vessel set-up is called the Vessel
Configuration (see page 91).
Project 1 Project 2
Configuration Configuration
1.n x.n
Figure 5-1 Project structures
information from the vessel will be copied from the ‘Projects Common
Files’ map. The changes made in the vessel configuration will be copied
back the common information in the ‘Projects Common Files’ map.
See also the Project The common information contains the following items:
Common tab in the
Explorer (see page 214). Geometry information.
Vessel contours, vessel wireframes and 3D studio models.
Equipment setup.
These common information files are not stored in the project folder
anymore. For existing projects the files are not updated in the project
folder, but are stored in the ‘Projects Common Files’ map. For projects
created with the PDS2000 3.2.0.0 version or later the files are only
available in the ‘Projects Common Files’ map.
Figure 5-2 Select Project window with the option Run the New Project wizard
checked
On the first page a choice has to be made, start from scratch with an
empty project or use an existing project as template. When an existing
project is selected, all relevant files from the existing project are copied
into the new project. The logdata subfolders, grid models, CUBE models,
dtm XML files, logdata file sets and sound velocity profiles files are not
copied to the new project. The new project can then be checked and
changed with the wizard.
As this is a wizard, each dialog window has that will close the
current page and will open the next one. The last page will have .
It is recommended to step through all pages of the wizard. Click on
to stop the wizard at that page without writing the required files
into the project folder. So it is advisable not to click on but to
finish the wizard even without entering data in the pages. That way a
project is made and data can be entered at a later stage.
The Project Configuration With both choices in the previous page, the next page gives the Project
can be modified with Edit > Configuration window. When a project was copied the inputs fields
Project Configuration from contain data from the old project, when an empty project was started
the menu bar or with these fields contain default values.
from the toolbar in the
Control Center. In both cases it is advised to check each possible input and the
corresponding input fields. All possible inputs with their input fields are
detailed below.
5.4.1.1 Description
The project and all computations in the project use the selected units.
These units are only for display purposes; PDS2000 has its own internal
units for logging the data.
5.4.1.4 Formats
Check the items that have to be in the log file name. The order of the
items in the log file name can be changed by using or .
Select the item that has to be moved and use one of the buttons to move
the item upwards or downwards.
Between the different items in the log file name a separator is needed.
Selected for the option Separator the right separator (- _ . ,).
At the bottom the option Replace all dots in the log file name will replace
the dots with a dash (or an underscore when a dash is selected as
separator. This means that all the dots, also in the name of the runline,
will be replaced.
With the log file name will be reset to the default log file setting.
In the Acquisition it is possible to change the name of the log file name. If
the option is active in the Acquisition and a new logdata file is created the
user can specify a different log file name (see page 257).
Historical data can be stored in the ‘Backup’ folder in the project. For all
the file types that are checked in the list a copy is made when a new
logging file is opened. The copy will only be made if the file is changed
after the last backup.
Check the option Keep history of files for Replayer and Editing if the
backups have to be made. The backups are used in the Replayer (see
page 389) and in the Editing (see page 395) when a log data file is
opened. The log data file will use the available files from the backup to
show the information. For instance when the color table is changed after
the data is logged; the color table that was used during the logging will be
used if ‘Color Tables’ is checked for a backup.
To avoid that the backup folder will be overloaded with backups, a
maximum number of days can be set. If a backup is older it will be
removed from the backup folder.
Figure 5-11 Set when the oldest log data files have to be deleted
than because if the number of days is too high then it is possible that the
hard disk is full before the oldest log data files are deleted. A full hard disk
will stop the system.
It is very important to backup the old log data files before one of the
options becomes valid; otherwise the log data files are lost.
5.4.1.9 Options
This page will show options that can be important to display or compute
data.
Show multibeam beams with no bottom detection
In PDS2000 the beams that have no bottom detection get a 0 (zero)
for the beam Z. By default the zero beams will not be displayed in the
views of PDS2000. When the user wants to see the zero beams then
he can check this option.
Lat/Lon on Local Spheroid – Lat/Lon on Satellite Spheroid
The user can select by selecting one of these options which latitude
and longitude are displayed in PDS2000.
This page will show the settings for the GPS time parameters. At the
moment only one setting is available.
st Leap Seconds
From 1 of January 2013 The leap seconds for GPS receivers with a GPS time. The leap
the number of leap
seconds is 16.
seconds are used to correct the GPS time to UTC time.
The leap seconds as set here will be used through PDS2000.
Figure 5-15 Sonar Targets file selection and list with classifications
Select or create in this page the active sonar targets file which can be
used in the Acquisition, Presentations, Replay and Editing.
The sonar targets can be classified. The user can make his own list of
classifications which can be used to classify the sonar targets. It is always
possible to classify a sonar target with a classification that is not in the list.
For more information about the sonar targets see the Sonar Targets view
in the Chapter Views (see page 376).
Select or create in this page the active icon images file which can be used
at the moment only in the Acquisition, Presentations, and Replay.
For more information about the sonar targets see the option Add Icon
Image in the chapter Plan View – Toolbar and Context Menu on page
352.
From the list of application types, select the one that describes the project
the best. The type and number of possible sensors and computations that
By checking Run the configuration wizard the wizard goes over in a menu
where the configuration can be saved. When a name is given, click on
and the wizard will continue with the configuration name and the
vessels page (see below).
Is Run the configuration wizard not checked then by clicking on
the wizard will be finished and the configuration will not be saved. A new
configuration has to be made with the menu option Acquisition > New >
Configuration….
Remote
Vessels which are created on another location, that means for
instance on another ship, can be added or edited. This other ship can
be monitored by reading the data from that ship. To get a connection
with the other ship the Control Center on the remote vessel has to be
running.
Give the hostname or the IP-address of the remote vessel. The port
704 will be used to get the vessel configuration from the remote
vessel. Do not change this port number!!
During the acquisition the sensor data from the remote vessel can be
read, but because of the data load an update rate can be set. Check
the option Use limited data update rate and set the update rate (in the
example above on 5 seconds).
Click on to download the vessel configuration from the remote
vessel.
If the vessel configuration on the remote vessel is changed or the
update rate has to be changed, click on under ‘Remote’ to
download the new vessel configuration or modify the update rate.
5.4.5 Layout
The layouts page shows where the real time modules are displayed. The
module Control Center is by default on the local computer. The
acquisition server and presentations can be on the local computer or on
another computer in the network.
Click on to add new presentations to the list. Select one of the
modules and click on or just click on to go to the Layout
dialog.
If the layout is not running on the local computer (main PDS2000) but on
a remote computer, give the name of the remote computer or select with
the computer in the network.
The name of the layout can be selected. Click on to create a new
empty layout. This empty layout can be filled with views in the Acquisition
or Presentation. It is better not to use the same name for the layout in the
Acquisition and in the Presentation.
The UI (User Interface) profile is always the default. The user can defined
a UI profile where his own toolbar and ‘shortcut keys’ settings are saved.
Click on , give a new name for the profile and make the module
according the wishes of the user. A new UI profile starts always with the
default settings for the shortcuts and the toolbar.
5.4.6 Events
On this page the events can be defined. Three automatic eventing modes
In the real time mode are available, conditions can be set and an event string can be defined.
manually eventing is
possible with F6.
For more detailed information about events see chapter ‘Events’ on page
155.
On the alarms page real time alarms can be defined. The alarms are
related to the configuration and will be active for each vessel in the
configuration.
Vessel specific alarms can be set in the vessel configuration (see page
129).
When an alarm is added a Conditions window, similar to the one in the
Vessel Alarms on page 129, is opened. In this window the alarm can be
defined.
If the condition for an alarm is not known yet leave the alarms page
empty. When an alarm is required on a measurement it is easy to make a
condition in the Acquisition with Edit > Alarms (see page 254). That way,
alarms can be checked immediately.
Click on in the alarms page to close the wizard and once more on
in the ‘Wizard is Finished’ page.
6.1 Introduction
In PDS2000, a coordinate system database is available where for the
most common countries the standard coordinate systems are predefined.
It is also possible for the user to add new coordinate systems to the
database.
The active coordinate system has to be selected in the Project
Configuration (see page 58).
A new coordinate system can be created in the Project Configuration and
in the PDS2000 tab of the Explorer (see page 215). The new coordinate
systems will be stored in a separate database, where all the user defined
coordinate systems are available.
In the PDS2000 tab of the Explorer two different databases are available,
It is not possible to modify the pdsgeodatabase and the pdsusergeobase. The pdsgeodatabase is
the predefined coordinate the database with all the predefined coordinate systems and the
systems. pdsusergeobase is the database with all the user defined coordinate
systems.
In this chapter will be discussed how to select, to create and/or modify a
coordinate system through the Project Configuration. For creating and/or
modifying a coordinate system in the ‘Explorer – General’ the same
dialogs and windows will be used.
Select in the Control Center the menu item Edit > Project Configuration or
click on in the toolbar and select in the Project Configuration window
the option ‘Coordinate System’.
Figure 6-2 New Coordinate System page of the Coordinate System Wizard
Give a name for the new coordinate system and check the option Based
on existing coordinate system if an existing coordinate system has to be
used as a start for the new coordinate system.
Click on to go to the next page of the wizard.
If the option Based on existing coordinate system is checked the next
page is the Select Coordinate System page (see below) to select from the
list an existing coordinate system.
If the option is not checked the user can select a satellite and local
ellipsoid from the list in the Ellipsoids page (see page 75).
Figure 6-3 Select Coordinate System page of the Coordinate System Wizard
The base of an existing On this page the user can select one of the existing coordinate systems
coordinate system is as a base for the new coordinate system. All the coordinate systems as
always both ellipsoids. The defined in both databases (pdsgeodatabase and pdsusergeobase) are
other settings of the available in the list of coordinate systems.
system can be modified.
If an existing coordinate system is selected, click on to go to the
next page of the wizard. The next page will be the Datum Transformation
Parameters page (see page 78).
This page will be opened if the user create a new coordinate system that
is not based on an existing coordinate system.
It is not possible to create Click on to select a satellite ellipsoid and a local ellipsoid from the
a new ellipsoid. list of ellipsoids.
Figure 6-5 Select an ellipsoid from the list of available ellipsoids in PDS2000
On this page only the datum transformations that are possible between
the two selected ellipsoids of the new coordinate system will be available.
If one of the datum transformations is selected, click on to go to
the next page of the wizard. It will depend on the selected option in the
Datum Transformation page (see page 76) what the next page will be.
If the option Use existing datum transformation was checked the next
page will be the Geoid Model page (see page 79).
For the other options the Datum Transformation Parameters page (see
page 78) will be opened.
This page will be opened if in the Datum Transformation page (see page
76) the option New datum transformation is checked. If also the option
Based on existing datum transformation is checked, first the Select Datum
Transformation page (see page 77) is opened before the Datum
Transformation Parameters page will be opened.
Name
Specify a new name for the to be created new datum transformation.
Method
At the moment the only available method is the Bursa/Wolfe method.
Shift X, Y and Z
The translations in the X, Y and Z direction, to translate from the
satellite ellipsoid to the local ellipsoid.
Rotation X, Y and Z
The rotations around the X, Y and Z axis, to rotate from the satellite
ellipsoid to the local ellipsoid.
Scale factor (ppm)
The scale factor between the two ellipsoids in parts per million (ppm).
Prime meridian shift Greenwich (deg)
This option is not available for the Bursa/Wolfe method.
File name
This option is not available for the Bursa/Wolfe method.
Description
The user can enter a short description for the new datum
transformation.
If all the parameters are entered, click on to go to the next page
of the wizard. The next page will be the Geoid Model page (see below).
In this page a geoid model can be selected for the coordinate system.
The geoid model will correct the satellite ellipsoid height to a local height.
The methods available at the moment are:
Belgium hBG03/xyGridLb72
The latest geoid model for Belgium.
DeMin
An old geoid model for The Netherlands.
Denmark DVR90
The latest geoid model for Denmark.
EGM2008
The Earth Gravitational Model 2008 is a spherical harmonic model of
the earth’s gravitational potential.
Grid Model (Grid coordinates)
If this option is selected, a geoid model grid model can be selected
The geoid model grid model with grid projection coordinates (easting and northing).
has to be created in the grid
model editor (see page 524). Grid Model (Satellite coordinates)
If this option is selected, a geoid model grid model can be selected
with satellite ellipsoid coordinates (latitude and longitude in WGS’84).
Norway
For Norway the latest geoid model file is available: HREF2008a.
Null Model
A geoid model with a 0 (zero) correction. This model can be used to
get the GPS antenna height as a local height.
Select an unit that will be used for the projection parameters. Because
this unit is used for the projection it will become the system unit for the
project.
Click on to create a new unit type and the New Unit dialog will be
opened.
Name
Specify a clear name for the to be created unit type.
Meters per unit
Enter the number of meters per one new unit.
Name suffix
Give a suffix for the new unit type, like a ‘m’ for meters.
If the right unit is selected or create, click on to go to the next
page of the wizard. The next page will be the Projection page (see
below).
This page will be opened if in the Projection page (see page 82) the
option New projection is checked. If also the option Based on existing
projection is checked, first the Select Projection page (see page 83) is
opened before the Projection Parameters page will be opened.
Name
Specify a clear name for the to be created projection.
Unit
The unit that will be used cannot be changed on this page. If the unit
has to be changed click on to go back to the Unit page (see
page 81).
Method
In PDS2000 several projection methods are available.
Cassini-Soldner
Hotine Oblique Mercator (A)
Hotine Oblique Mercator (B)
Lambert 1 Parallel
Lambert 2 Parallel
Mercator
RD (is only valid with the unit Meters)
Transverse Mercator
Stereographic
Universal Transverse Mercator (is only valid with the unit
Meters)
The number of parameters on this page will depend on the projection
method that is selected. The values of the parameters False Easting and
False Northing have to be in the unit, which is mentioned on this page.
It is possible that a position calculated on the local grid not match with the
actual X, Y and Z for that point. With a post correction this point can be
moved so it match with the actual grid coordinates. This post correction is
only applied when a calculation is done from the local ellipsoid to the local
grid or vice versa.
On this page two ways to add a post correction are possible, manual or
with a model. The manual post correction is always a fixed shift in all the
X, Y and/or Z coordinates, while with post correction with a model for
each point a different shift can be used.
The models available at the moment are:
Belgium hBG03/xyGridLb72
The latest post correction model for Belgium.
Denmark DVR90
The latest post correction model for Denmark.
HARN
The latest correction model for the United States.
If HARN or OSTN02 is In theory is HARN a correction on the local latitude and longitude and
selected, PDS2000 will correct not on the grid coordinates, but in PDS2000 the only place for a post
the local ellipsoid coordinates correction is on the X and Y coordinates.
before the coordinates are
projected on the grid.
OSTN02
The latest post correction model for England, Scotland and Wales.
In theory is OSTN02 a correction on the local latitude and longitude
and not on the grid coordinates, but in PDS2000 the only place for a
post correction is on the X and Y coordinates.
Figure 6-16 Save Coordinate System page of the Coordinate System Wizard
On this page an overview is given of all the settings for the new
coordinate system.
Click on to check the new coordinate system by entering a
known point in the Geo Calculator (see page 194).
If the new coordinate system is accepted, click on to save the
coordinate system in the group as selected by the user. If one of the
settings in the overview is not right, click on to go back the
relevant page in the wizard to change the settings. It is also possible to
save the coordinate system and use the Edit option (see below) to
change the coordinate system.
Figure 6-18 Select Coordinate System window with only the user defined
coordinate systems
Figure 6-19 Edit Coordinate System window with an user defined coordinate
system
the datum transformation not, then when the coordinate system is saved
with the datum transformation is also changed in the coordinate
systems where the same name for the datum transformation is used.
There is also a relation between the selection of the projection and the
unit. Because the parameters of for instance the Easting and Northing in
the projection are specified in the unit that is selected for the coordinate
system.
7.1 Introduction
PDS2000 always needs a vessel configuration before the Acquisition can
be started. The vessel configuration will contain all the settings which are
necessary to do all the measurements.
Before a vessel configuration can be made a project has to be setup as
discussed in chapter ‘Starting PDS2000’ on page 53.
A new name for the vessel configuration has to be entered. The user can
choose to create a complete new vessel configuration or to use an
existing vessel configuration as template.
When the option Use existing vessel as template is checked, the user can
select from all the vessel configurations that are available in the Projects
Common Files map.
Click on to continue with the wizard. It can take a while before the
next page of the wizard will be opened. The reason is that PDS2000 first
check if the new vessel configuration name exists or not. If the name
already exists an error message will appear and the user can enter a
different name.
The next pages of the wizard will be explained with the separate tab
pages below.
The first page in the vessel configuration is the vessel geometry with the
vessel visualization, vessel draught, vessel turn radius, sea level, vertical
position and the offsets on the vessel.
Visualization mode 2D
Select as 2D vessel contour a vessel contour (made in PDS2000) or a
vessel Wireframe; after that select the file for the selected
A vessel wireframe is a 3D visualization.
drawing of the vessel and
can be used in the 3D
Click on to create a new vessel contour in PDS2000 or click
views in PDS2000. It is on to open the selected vessel contour. In both cases the
also possible to display the vessel contour editor will be opened (see page 95). For a survey
wireframe in the standard vessel usually only a top view is entered.
2D views. These Select the active shape (vessel contour) that will be displayed in the
wireframes should be 3D Acquisition.
DXF files.
Visualization mode 3D
Select as 3D vessel contour a vessel Wireframe or a 3D Studio file;
after that select the file for the selected visualization.
Vessel
Draught
The draught is the distance from the waterline to the deepest point
on the vessel and is always positive. It is used in computations
such as depth below keel.
-X +Y
Port Bow
CRP
X=0
Y=0
Z=0
-Y +X
Stern Starboard
-Z
Bottom
Figure 7-3 Vessel coordinate system
The options in the right top panel of the vessel contour editor are:
Name: Point(x)
Add the X and Y value for point(x) in the vessel coordinate system.
Type
Point. Select this type if point(x) is not a start of line or a start of
polygon.
Start of Line. Select this type if point(x) is the first point of the line. Until
a new start of line or start of polygon is selected all points after this
point will be part of the line.
Start of Polygon. Select this type if point(x) is the first point of the
polygon. Until a new start of line or start of polygon is selected all
points after this point will be part of the polygon. The polygon will be
solid.
The buttons and options on the right side in the editor are:
Add a new point to the contour. The added point comes always at the
end of the list.
Insert a new point above the location of the cursor in the list.
Select the view side of the vessel contour; top, bottom, left, right, front
and back.
,
Zoom Extents, Zoom In / Out.
Click on to save the vessel contour and to close the vessel
contour editor.
7.4 Equipment
Figure 7-7 Navisound Control Center to set the port(s) and check the
communication with the echo sounder
This view will be opened when in the Equipment one of the Navisound
Graphical Trace devices is selected and on or is
clicked.
is grayed out The user selects the required computations from the left window and adds
when a computation is not these with to the list of defined computations. By default the given
possible (anymore) for the computation name will be used and the properties of the selected
chosen application type. computation will be opened.
The properties of the added computations can be opened by selecting the
computation in the defined computations list and click on to
access the properties of that computation.
Multiple conditions can be set on any data source. If one of the conditions
is ‘true’ it will lower the rank of the source, provided automatic switch is
checked in the Data Sources page.
7.7 Guidance
Guidance is a method of assisting a vessel to sail along pre-defined
tracks or towards a pre-defined location or area. The guidance methods
are:
1. Route
2. Runlines
3. Waypoints
4. Design Model
5. Cutter Dredge
6. Work Areas
7. Restricted Areas
8. Vessel Placement
9. Dredge Instruction
10. Object Distance
The number of guidance methods that is available is depending on the
selected application type.
7.8 Tools
The Tools page is skipped in the vessel configuration wizard. If the vessel
configuration is opened outside the wizard always the interval logging tab
is available.
For several applications like (Rope) Excavator, Cutter, Trailing Suction
Hopper, Maggy Survey and Multibeam Survey extra tabs are added to the
Tool page.
The different tabs in the Tools Page are:
Anchor Definition (see below)
Crane Configuration (see page 107)
Cutter (see page 109)
Dredge Logging Settings (see page 110)
Interval Logging (see page 111)
Magnometer Dialog (see page 113)
Pipe Configuration (see page 114)
Production Parameters (see page 115)
Trip Registration (see page 116)
Figure 7-14 Tools page with the Anchor Definition page of the cutter dredge
application
In the Anchor Definition page the anchor definitions for the vessel
(pontoon) and the handling tugs can be specified.
Figure 7-15 Tools page with the Crane Configuration page of the excavator
application
Figure 7-16 Tools page with the Rope page of the rope excavator application
This Tools page is valid for the Rope Excavator application to setup the
crane configuration for a rope excavator with a backhoe.
On the three subpages the offsets for the boom, the rope and the tool
have to be entered. In the Acquisition the angles and/or offsets for the
boom and rope can be calibrated (see page 258).
For more information about this Tools page see the manual for the ‘Rope
Excavator’ application in the manuals folder of PDS2000.
This Tools page is valid for the Cutter Dredge application to setup the
cutter configuration.
For more information about the Cutter see the manual for the ‘Cutter
Dredge’ application in the manuals folder of PDS2000.
Figure 7-18 Tools page with the Dredge Logging Settings page of the
excavator application
This page is to setup the logging conditions for the grid model logging
with a (rope) excavator, cutter or hopper.
In the Logging page the grid model logging should be setup as explained
on page 119. Next to that setup the option Enable grid model logging
should be checked otherwise there is no grid model logging in the
Acquisition.
Figure 7-19 Tools page with the Interval Logging page of a cutter dredge
application
In the Logging page the interval logging format have to be checked before
an interval log file is created (see page 123).
Item to log
Double click on a field and the Select Data window will be opened. In
this window the item from one of the available computations can be
selected.
When an item is selected automatically the row is filled with the default
settings.
User name
Double click on a field and the text in the field can be modified.
This name will be visible in the Interval Logging view in the Acquisition.
Period
At the end of a period the actual value will be logged to the interval log
file.
By default the period is set on 00:01 (1 minute). Select the field and
the user can modify the period.
Reset
The reset is for the methods averaging and cumulating.
Yes. The calculation starts again when a new period starts.
No. The calculation continues after a new period is started.
In the Acquisition the interval logging can be monitored in the Raw Data
view and in the Interval Logging view (see page 302).
When in the Logging page the Interval Logging Format is checked (see
page 123) then the data will be logged in the file xxxx_Interval.log-
yyyymmdd.csv in the Logdata directory of the project, where xxxx is the
vessel name.
Figure 7-20 The Tools page with the Magnetometer Dialog page of the maggy
survey application
This Tools page is valid for the Maggy Survey application to setup the
offsets for a multi-channel magnetometer.
The number of channels that will setup by default will depend on the
magnetometer device driver that is selected in the Equipment.
Figure 7-21 Tools page with the Pipe Configuration page of the trailing suction
hopper application
This page is valid for the Trailing Suction Hopper application to setup the
pipe segments.
In the Pipe Configuration page the configuration for a suction tube with a
bend, an upper pipe, a lower pipe and a draghead (suction head) has to
be setup. When the trailing suction hopper has a starboard and port
suction tube two Pipe Configuration pages are available in the Tools
page.
For more information about this Tools page see the manual for the
‘Trailing Suction Hopper’ application in the manuals folder of PDS2000.
Figure 7-22 Tools page with the Production Parameters page of the trailing
suction hopper application for two bunkers
Figure 7-23 Tools page with the Trip Registration page of the trailing suction
hopper application
How the logging is done is defined in the Logging page. The dialog sets
the file formats, manages log space and sets the log conditions. The
layout of the Logging page depends on the selected application type and
on the selected logging formats.
On top of the page it is possible to change the log directory. Select an
existing directory or enter in the box a new log directory. This is same
option as in the Log Files page of the Project Configuration (see page 59).
Figure 7-25 Log File Index in the logging page for PDS2000 format
Index file after logging means that direct after the log file is closed an
index file of the log file is created. This will save time when the log file is
opened in for instance the Editing.
Figure 7-26 Backup log in the logging page for PDS2000 format
Backup log becomes available when the option Use backup log directory
is checked in the Project Configuration (see page 59). Check the option
Enable Backup log to log the PDS2000 logdata file also in the backup log
directory which is specified in the Project Configuration.
File name: Vessel name[application type]_runline name-date-time.PDS
The runline name is for a (rope) excavator application replaced by the
project name and for the dredge applications by the trip number.
This file name mentioned above is the default file name. With the option
user defined log file names in the Project Configuration a user-defined file
name can be defined (see page 59).
From PDS2000 version 3.6.0.0 onwards, the sonar image, side scan and
snippets data in the PDS2000 log file is compressed to reduce the size of
the log files. When this PDS2000 log file is opened in an earlier version
(3.5.0.x or older) the data of the sonar image, side scan or snippets
cannot be opened anymore!
From multibeam data all the pings will be logged in the PDS2000 format,
even the pings that are out of order. The pings with a bad time stamp will
only be logged when they are newer than the ping before and when they
meet the data rate criteria.
Select the grid model file name. If no file exists click on and give a
new file name. Select one or more data types and enter a cell size.
The grid model is filled with data from the added device in Data for grid
model logging.
File name: Name of the grid model.DTM
The tolerance is the minimum difference of the Z-value with the previous
Z-value. If the difference is more than the tolerance (e.g. 0.05 m) the data
point is added to the file.
The width of a sway is defined as 100%. By setting a minimum distance
(e.g. 10%) a point at every 10% of the width of the sway is added to the
file.
File name: Vessel name[application type]_runline name-date-time.XYZ
This is the same type of menu as for the PDS2000 Grid Model (see page
119).
File name: Name of the Grid Model.DTM
By setting the sampling rate the logging interval is defined (e.g. 30 sec).
File name: Vessel name[application type]_year_month_day.TRK
Figure 7-32 Grid model input for backscatter grid model logging
This is the same type of menu as for the PDS2000 Grid Model (see page
119) but with an extra layer for the backscatter data.
The old backscatter grid models (created with the Sidescan sonar format
in the PDS2000 versions before 3.4.0.0) can still be used for logging the
side scan sonar or snippets data). Only in these old grid models is no Z
Average available to show the data in a 3D view.
File name: Name of the Grid Model [Backscatter-Model].DTM
Check the option Reduce on nadir filter if not all the data has to be
logged. The data that is rejected by the nadir filter (see page 328) will not
be logged.
Figure 7-34 Backup log in the logging page for S7K format
Backup log becomes available when the option Use backup log directory
is checked in the Project Configuration (see page 59). Check the option
Enable Backup log to log the S7K file also in the backup log directory as
specified in the Project Configuration.
At the moment the following records, if available, will be logged:
1003 - Position
The position is the position of the vessel reference point.
The height is the height of the vessel reference point
relative to sea level when height source is ‘None’,
otherwise the height is relative to chart datum.
1008 - Depth
Depth of the vessel reference point relative to sea level.
1010 - 7K Sound Velocity Profile
1015 - Navigation
The position is the position of the vessel reference point.
The height is the height of the vessel reference point
relative to sea level when height source is ‘None’,
otherwise the height is relative to chart datum.
1016 - Attitude
7000 - 7K Volatile Sonar Settings
7004 - 7K Beam Geometry
7006 - 7K Bathymetry Data
The along track and across track values are related to the
vessel reference point and not to the sonar reference
point. The depths are relative sea level when the height
source is ‘None’, otherwise the depths are relative chart
datum.
7007 - 7K Backscatter Image Data (Side Scan Data)
7008 - 7K Beam Data (Snippets Data)
7009 - Vertical Depth
7027 - 7K Bathymetry Data new style
The along track and across track values are related to the
vessel reference point and not to the sonar reference
point. The depths are relative sea level when the height
source is ‘None’, otherwise the depths are relative chart
datum.
7028 - 7K Beam Data dB (Snippets Data)
The default and standard format is FAU 1 with the beam angle. There is
no difference in the file name between both formats.
File name: Date_time_1_vessel name_runline name.FAU
The number 1 mentioned the first multibeam system from the equipment
list. If more multibeam systems are logged simultaneously then the
second gets a 2, the third a 3, etc.
When the number of beams is changed during the logging the actual file
will be closed and a new FAU file will be created. In a FAU file the number
of beams is placed in the header of the file.
At the moment some fields in the header of the file are not filled in due to
varies reasons. The fields that are not filled are TimeOffset,
SensorValsEdited, SwathNtPosJump, MaxNonLinearity, Major, Minor,
Autoflags, RotRectValid and BB_Tilt. All these fields will have a value 0.
Figure 7-36 Uncorrected or fully corrected multibeam data selection for the
GSF logging
Select Uncorrected when the raw multibeam data has to be logged in the
GSF file. Select Fully Corrected when the corrected multibeam data has
to be logged in the GSF file. The corrected multibeam data in the GSF file
is computed according the multibeam xyz computation in the multibeam
device data.
File name: Date_time_1_vessel name_runline name.GSF
The number 1 mentioned the first multibeam system from the equipment
list. If more multibeam systems are logged simultaneously then the
second gets a 2, the third a 3, etc.
Below is a short explanation of the current implementation of GSF File
Logging in PDS2000:
The GSF logging is based on a modified version of the GSF 2.09
library provided by SAIC.
The logger uses CF_MBXYZREL PDS data blocks as a starting point.
Only fully computed results are stored in the GSF File.
Sonar specific data is only written for sonar models: 8101, 8111, 8124,
8125, 8150 and 8160.
Multi-head sonar data is logged into two separate GSF files.
Single beam sonar’s are not supported.
The following GSF types are written to the GSF file:
GSF header
GSF Processing Parameters
GSF Sensor Parameters
GSF Comment
GSF MB Ping
GSF Attitude
in place. The checks for that system are 1% on the system disk with a
minimum of 500 MB and 100 MB on the data disk.
The logging will stop when one of these two limits is reached. One
hour, 30 minutes and 15 minutes before these limits are reached a
message will be reported.
Minimum free disk space warning
Give the amount of disk space that should be kept free at all times, in
MB.
Allowed log space warning
The maximum space to be used by PDS2000 for logging purpose, in
MB.
The log space management system is not active when the minimum free
disk space and/or the allowed log space are zero.
PDS2000 will generate a warning signal when the limit for the minimum
free disk space or the allowed log space is reached and it will continue to
log the data.
A maximum size of the log file can be set. This means that when the file
exceeds the file size a new log file will be created.
Another option is by setting a time limit on logging in one file. If the time
limit is reached a new log file will be created.
On this page the simulation parameters can be set. The simulator is build-
in for training purposes.
Vessel position
Enter the grid position where the simulator will start.
Heading
The initial heading of the vessel.
Vru
Maximum values of the VRU simulator, Max. Heave in project units,
Max. Roll and Max. Pitch in degrees.
Depth
For each channel a depth value. Depth channel 1 is also used to
simulate a multibeam echo sounder.
Speed
Initial speed of the vessel. Depending on the chosen project units, in
knots or meters/second.
Simulate using runlines
Check Use Runlines to have the simulator running over the runlines.
Check Automatic Mode and the simulator will select the next runline
automatically.
Multibeam noise factor
Adds noise to the simulated multibeam swath, giving a more realistic
effect.
Figure 7-41 Alias page in the vessel configuration with an alias for NMEA
GGA
Aliases are used to give multiple sensors of the same type distinguished
names. E.g. when there are two GPS sensors both using the device
driver ‘Standard NMEA GGA’, these sensors will have the same name in
the program. To give those sensors aliases such as ‘GPS1’ and ‘GPS2’ it
is more clear to the user.
Aliases are used throughout PDS2000 wherever the device name comes
forward.
The alarms that can be set in this page are vessel specific or device
specific alarms and will be valid only for the vessel that is setup in this
vessel configuration.
Check the option Enable Alarm when the alarm has to be active.
Check the option Sound Alarm when the alarm should give a sound when
the alarm becomes valid. Each Severity (Low, Intermediate or High) gives
a different sound for the alarm.
With or a Condition dialog will be opened where the
selected condition can be modified or added. In this dialog an attribute
from the equipment or computation list can be selected and a condition
with a value for this attribute can be defined.
The vessel alarm file will be placed in the ‘Explorer - Project’ (see page
219), but cannot be edited through the explorer. It is only possible to
modify a vessel alarm file in the vessel configuration.
8.1 Introduction
Guidance is a method of assisting a vessel to sail along pre-defined
tracks, towards a pre-defined target or in/out pre-defined areas.
The number of guidance methods available in PDS2000 depends on the
application type that is selected. At the moment the different guidance
methods shown below are available through the different application
types:
1. Route (see page 132). A route is a sequence of points connected
with lines. The lines are straight lines between tangent points, or
circle segments when a center point is given. Routes are often used
in rivers and channels, but can also be used to follow a pipe or a
cable.
2. Runlines (see page 138). Runlines are straight lines or route wing
lines which can be grouped in blocks. A number of block methods are
available.
3. Waypoints (see page 141). A waypoint is a location towards the
vessel is moving.
4. Design Model (see page 143). A selection can be made between a
3D model and a grid model as guidance for dredging.
5. Cutter Dredge (see page 146). A work route for a cutter dredger.
6. Work Areas (see page 147). A work area is an area where the work
takes place. A work area can be a rectangle or a polygon area.
7. Restricted Areas (see page 148). A restricted area is an area where
it is not allowed to come or work. A restricted area can be a polygon
or an area on both sides of a route (e.g. a pipe or a cable route).
8. Vessel Placement (see page 149). A vessel placement is a location
with a heading towards the vessel is moving.
9. Dredge Instruction (see page 151). A dredge instruction gives the
dredge area with the depths for the dredger.
10. Object Distance (see page 152). Generate alarms when distance to
selected object become in alarm range.
Each method has its own definitions and computations and can have
many guidance files. In the Acquisition the user can change from
guidance file.
When a new route is created the user can select from three different
types of route; a generic route, a pipe route or a cable route. The generic
route is the standard route with Eastings and Northings. The pipe / cable
route has next to the Eastings and Northings also a Z-value or a depth.
This way a pipe / cable route can be used to show a pipe / cable with the
right depth.
The route editor can also A route is a number of points connected by lines. The route points can be
be opened in the Explorer - either tangent points (TG) or center points (CP). Tangent points can be
Project with the Track connected with a straight line or with a curve.
Guidance Routes option
(see in the ‘Project On the route page a route file can be selected and edited or a new file
Database’ on page 223). can be created. This opens automatically the route editor.
To check the fit of the curve against its adjacent tangent points. In
case a curve fit is not possible warnings are written in the ‘Status’ field
of the list.
From the menu bar some extra functions can be selected:
Route > Properties…
Figure 8-3 Route Properties for the standard route (left) and for the pipe /
cable route (right)
Start KP
Enter a Start KP for the (pipe / cable) route.
Pipe Diameter
Enter a pipe / cable diameter for the pipe / cable route.
KP calculation mode
Select the mode for the KP calculation, Grid distance or True
distance.
Grid distance. Calculate a distance between two tangent points on
the Easting – Northing plane.
True distance. Calculate a distance between two tangent points on
the local ellipsoid.
First curve turn
Select the direction of the first curve in the route, Clockwise or
Counter clockwise.
Manual KP handling
When a tangent point on the route is defined with a manual KP, this
option becomes valid.
in the import file is not a manual KP. Select then in the import wizard
‘KP’ for the KP column and ‘Man KP’ for the column with ‘1’.
Route > Export
An ASCII file with the route information will be created.
Figure 8-5 First page of the ASCII Import Wizard for a route
If an import configuration The ASCII file with the route information has to be selected. If the file is
file is used, click on selected the user can use an existing import configuration file or continue
to import the with the wizard to configure the import. If the user continues with the
ASCII file. wizard there is a possibility to save the import configuration file, so the
next time the configuration file can be used to import a route. Click on
to continue with the import wizard.
Figure 8-6 Second page of the ASCII Import Wizard for a route
Select the file type for the ASCII import file; the data in the file is delimited
with a character (like a comma, a tab, a space or user defined) or the data
is presented in fixed columns. Click on to go to the last page of
the import wizard.
On the last page of the import wizard the delimiter and the columns have
to be defined.
Delimiter
Select a character as delimiter between the data columns. The options
are comma, tab, space or custom. With custom a user defined
character can be added.
Extra
The extra option is used to skip the header lines of the ASCII import
file. First check the option before a number can be filled in.
Select Column Names
Click with the right mouse button on a column and select one of the
available field names for the selected column. On the right top side of
the page a column number will be added to the selected field name.
If the right delimiter is selected, the right number of header lines is
skipped and all the columns are selected, which are needed for the route,
click on to import the ASCII file.
If on the first page of the import wizard the options ‘Save configuration as’
is checked and a file name is given, the settings made on the second and
third page of the wizard will be saved in the import configuration file and
can be used the next time when an ASCII import for a route has to be
done.
The runlines editor can A runline can be a straight line or a route wing line. It is possible to have
also be opened in the several groups of runlines in a runlines file.
Explorer - Project with the
Runlines option (see in the On the runlines page a runlines file can be selected and edited or a new
‘Project Database’ on page file can be created. This will automatically open the runlines editor (see
222). page 139).
Lead-in Lines
When the option Show lead-in lines is checked, PDS2000 computes a
lead-in line from the current vessel position to the start point of the
next runline. The lead-in curve is based on the lead-in line length and
the ‘Vessel turn radius’ as set in the vessel geometry (see page 93).
The lead-in line length is the length of the straight line that is in line
with the next runline.
Check Use lead-in lines to compute off-line distances; distance to go
and traveled distances along the lead-in line.
Next line selection
In the next line selection the runline retrieval method needs to be set.
Normal. Each subsequent line is taken from the list with as start and
end of line the coordinates as defined in the runlines file.
Reverse. Each subsequent line is taken from the list with as start and
end of line the end and start coordinates.
Alternate. Each time a next line is selected from the list, the start and
end coordinates are alternately as normal or reversed. This allows
sailing line-by-line in a continuous way.
Enter or choose a number of lines to skip each time a next line is taken
automatically.
Check the option Automatic next line and click on to set a
condition to discard the current line and goes to the next runline in the
list. The condition editor is equal to the one described on page 104.
Online condition
This condition is used for logging purposes. Check the Offtrack limit
and give a value for the offtrack limit. When a vessel is further away
from the selected runline than the offtrack limit, logging stops if the
appropriate check marks are set in the ‘Condition Check’ in the
Logging page of the vessel configuration (see page 126).
For each runlines file one or more line types can be defined in this editor.
For blocks of lines the first line is entered and the computation of the
coordinates for the other lines is done automatically.
Click on under the ‘Full Name’ to create a new set of runlines.
Select from the Add Runline window a runline type to add. Each selection
gets a different line entry window on the bottom left-hand side of the
runlines editor.
Single line (rectangular)
Enter a line name, a line number and the start and end coordinates.
Single line (polar)
Enter a line name, a line number, the start coordinates and a line
length and bearing to the end coordinates.
Parallel lines (rectangular)
Enter a name for the runlines, the start and end coordinates for the
first line, a start number for the first line, the number of lines, the
number interval and the line spacing (= the distance between adjacent
lines).
Parallel lines (polar)
As above but instead of end coordinates for the first line a line length
and bearing to the end coordinates.
Grid
Enter a name for the runlines, choose an origin where the grid box
starts, the coordinates of the origin, the width and height of the grid
box and a rotation for the grid box.
Enter the start numbers, the number interval and the line spacing for in
the X and Y direction of the grid box.
Perpendicular lines
Creates a block of lines perpendicular to a centerline.
Enter a name for the runlines, for the centerline the start and end
8.4 Waypoints
The waypoints editor can Waypoints are target points or points of interest. Around a waypoint
also be opened in the tolerance circles can be drawn. In the Acquisition a wayline can be drawn
Explorer - Project with the from the current vessel position to a waypoint, indicating distance and
Waypoints option (see in bearing from the vessel to the waypoint.
the ‘Project Database’ on
page 224). On the waypoints page a waypoints file can be selected and edited or a
new file can be created. This will automatically open the waypoints editor.
Click on to add a new waypoint to the list. The details of the new
waypoint are displayed in the upper right corner of the waypoints editor.
Name
Enter a logical name for the waypoint. By default the name will be the
‘Waypoint’ with between brackets the date and time when it was
created.
Default tolerances can be set. For a new waypoint the user defined
tolerances in the top right corner are replaced by the default tolerances
set in here.
Options > Electronic Chart…
Select a PDS1000 electronic chart as background.
Options > Grid Properties…
Select the grid to be shown in the plan view: Grid Crosses, Solid Line
Grid, Dotted Line Grid or Scale Bar. The grid can be with or without a
grid annotation.
Options > Import from ASCII…
An ASCII Import Wizard will be started to guide the user through the
import settings. This import wizard is the same type of import wizard
as discussed on page 136. The ASCII file should contain at least a
waypoint name, the X and Y co-ordinate. The two tolerance circles are
optional.
Right clicking on the plan view window opens a context menu with the
zoom functions, which are also on the right side in the editor.
Z Shift
When checked, an offset to the Z-value of the design model will be
applied.
Z lower limit
When checked, the new Z-value for the design model.
Underdredge limit
The value is an offset perpendicular to the design model and is shown
in the different Profile – Realtime Design views just as an indication
(see ‘Profile – Realtime Design Antwerpen View’ on page 367). At the
moment no alarm is set or checks are done with this limit.
Overdredge limit
Same as for the ‘Underdredge Limit’.
After the check the errors are visible in the plan view of the editor. Zoom
in to one of the errors and click on the error to open a Fix window to solve
the error. After the error is fixed, click on again to check if the error
is gone. Continue to solve all the errors. Click on or to save
the model, this is only possible when there are no errors left. As
mentioned in the info box the non-flat and overlapping areas cannot be
fixed.
If an error is fixed but the result is not what the user wants then with
the modification made to the error can be undone.
The 3D model can be exported to a 3D-DXF file. When it is not possible
to solve all the errors in the model, like the non-flat and overlapping
areas, the only option is to export the data to a DXF file and try to solve
the errors outside PDS2000 e.g. in AutoCAD.
Right clicking on the plan view window opens a context menu with several
functions. The most of these functions are also in the toolbar.
Zoom functions ( )
Zoom In, Zoom Out, Zoom Window and Zoom Extents.
Pan ( )
Toggles the pan option on/off. When pan is active, keep the left mouse
button in and move the mouse to pan through the data.
The pan option can also be switched off by clicking on the right mouse
button.
The route editor can also A cutter dredger uses a work route as guidance. A work route is the same
be opened in the Explorer - as a route in ‘Route’ on page 132.
Project with the Track
Guidance Routes option Work route
(see in the ‘Project On the cutter dredge page a (work) route file can be selected and
Database’ on page 223). edited or a new file can be created. This opens automatically the route
editor (see page 133).
Work offset
An offset can be given to the work route. This offset route becomes
then the guidance route for the cutter dredger.
Swing limits
Angular swing limits
The maximum swing of the cutter to port and starboard side in
degrees.
Use also distance limits
Check this option to make it active.
A work area can be a dredge or dump area, and each area has a name
that can be descriptive and shown in the plan view.
With the option Only allow In the Acquisition one or more work areas can be selected and becomes
single area selected in the the active work area(s). A line is drawn from the current vessel position to
Acquisition only one work the active work area or the center of active work areas. That line stays on
area can be selected and the vessel’s tracking point while the vessel moves, guiding the vessel
will be active. toward the active work area.
The work areas editor can A work areas file can be selected or created with . Different work
also be opened in the areas can be kept together in one work areas file in the work areas editor.
Explorer - Project with the There is no limit to the number of areas in one file.
Work Areas option (see in
the ‘Project Database’ on Click on to create a new work area. Two work area types are
page 224). available:
Polygon Area
Select an existing clipping polygon from the project as work area.
Rectangular Area
Enter a name, the center coordinate, the width, the height and the
rotation of the work area.
Alternatively, work areas can be created by importing ASCII files, click on
and converts these files to work areas. The ASCII file should be a
comma separated file with the format <Name>, <Center X>, <Center Y>,
<Length>, <Width>, <Rotation>.
The placement points A vessel placement is a target location with a heading. In the Acquisition
editor can also be opened a line will be drawn from the current vessel position to a placement point,
in the Explorer - Project indicating distance and bearing from the vessel to the placement point.
with the Placement Points
option (see in the ‘Project On the vessel placement page a placement point file can be selected and
Database’ on page 222). edited or a new file can be created. This will automatically open the
placement points editor.
On the left side of the dredge instruction editor all the information can be
added or modified. This information will be shown directly in the plan view
on the right side.
This option is available for the (rope) excavator and grab crane dredge
applications will only work when 3D shapes of the crane are used.
Figure 8-25 Views in the Acquisition that have an alarm frame with text
9.1 Introduction
Before events can be viewed in the Messages – System Messages view
in the Acquisition, the event and the conditions to show the event have to
be defined. At the same time when an event is shown in the Messages –
System Messages view the information is logged in the PDS2000 log file.
The Events page can be opened in two different ways:
1. Through the New Project wizard. Select File > New Project… from the
menu bar of the Control Center to open the wizard (see page 68).
2. With Acquisition > Configure from the menu bar or with on the
toolbar of the Control Center the Configuration window will be opened.
Click on the tab Events to open the Events page.
On this page the eventing interval, the conditions and the event definition
have to be set.
The option Enable eventing has to be checked if the user wants events in
the Acquisition.
When the option Follow Logging Enable is checked the event logging is
started and stopped with the PDS2000 logging. This option overrules the
9.2.1 Mode
Select one of the three interval modes for the eventing:
Time
Set a time interval, e.g. 60 sec. Every 60 sec an event is generated.
Distance
Set a distance interval, e.g. 100 m. Every 100 m sailed an event is
generated.
Line
Set a line distance interval, e.g.100 m. Every 100 m sailed along a
runline, a route or a wayline an event is generated.
9.2.2 Conditions
Click on to define the conditions for the eventing.
In this example select for ‘Start character’ 23 for the X or 40 for the Y
and for ‘Field length’ in both cases 12 to add the two data items.
For the explanations of the other options in the fixed field see the ‘Field
Selection’ below.
Click on to select from the Select Data dialog the data item for the
relevant data source.
Set a start number for the first event number and set the number
increment to the next event numbers. If the counting of the event numbers
is decreasing, check the Count down checkbox.
10.1 Introduction
When PDS2000 is started always the Control Center will be opened.
From the Control Center all modules of the program can be started.
Before the Control Center of PDS2000 is started PDS2000 will do a check
Help Topics
It will open the Help file of PDS2000 which contains a copy of all the
PDS2000 manuals. The Help file can also be open with the F1-key.
Download PDS2000 Updates
The FTP site of PDS2000 will be opened to download the latest
version of PDS2000.
PDS2000 On The Web
The PDS2000 site on the RESON website will be opened.
PDS2000 On Twitter
The PDS2000 twitter site will be opened where the latest information
of PDS2000 is available.
View Release Notes
The release notes of PDS2000 will be opened in the default PDF
reader.
Send Feedback To RESON
Via email
The default email editor will be opened to send an email to the
helpdesk of PDS2000 (pds2000@reson.nl).
Via the web
The Support page on the RESON website will be opened.
Show Support Phone Numbers
The telephone numbers for the PDS2000 support in The Netherlands
and for the RESON support in Denmark and USA will be given.
External Clock Synchronization
Check this option to activate the clock synchronization.
With double click on in the taskbar the Clock Sync window will be
opened. This is the same window (Clock Sync – System messages) as
when on is clicked in the Clock Synchronization window (see
page 166). The only difference is that in the menu bar the option Edit is
added.
Click with the right button of the mouse on and a context menu is
opened with the options Show and Exit. With Show the same window as
with the double click on the icon is opened and with Exit will disappear
from the taskbar but the clock synchronization will not be inactivated.
10.5 Interfacing
On the Equipment page an IO port has to be set when a sensor is added
to the device list (see page 96). When in the Equipment page on
is clicked only the communication ports for that specific
device driver are available and not all possible interfaces can be selected.
In the Interfacing window which can be opened in the Control Center all
the different communication ports are available.
Select from the menu bar the option System > Interfacing or click on in
the toolbar to open the Interfacing window.
By default only the serial communication ports COM1 – 16 are displayed
in this window. If in the Equipment page for a specific device driver
another communication port is added then this new communication port
will be visible in the Interfacing window.
10.5.1.1 XSE
This type of communication port is only used for an Elac system. A
network port has to be entered and on the right side in the Interfacing
page an IP-address has to be entered for the XSE server.
10.5.1.2 Socket
This type of communication port is a network connection and can be used
for receiving and/or sending data through a network connection.
The ‘empty’ mentioned above in the table can also be replaced by ‘host IP
address’ when only the data from the host address has to be accepted.
10.5.1.3 Serial
This type of communication port is a serial connection, called COM port,
and can be used for all the sensors with a serial connection.
If more than one COM port has to be used, serial extender cards have to
be installed. See in the chapter ‘Installation’ on page 17 for more
information.
The Base Port Number is by default set on the right number (2020), do
not change this!!
Select the sensor type that matches with the selected device.
See for a detailed explanation the manual Interface Setup chapter Odom
ES3 (the file Interface Setup.pdf in the folder ‘manuals’).
10.5.1.5 RGL
The RGL communication port is a network connection and is specific for
the laser scan devices Riegl and Riegl Vline. The port cannot be selected
it will automatically selected when one of these laser scan types is
selected as device.
Host Address
The IP address is always from the Riegl laser scan.
10.5.1.6 R7KI
The R7KI communication port is a network connection and is specific for
the RESON SeaBat 7K systems. This communication port is identical with
the Socket port as described above.
Host Address
The host is always the 7K data server and, when it is running on the
same computer as PDS2000, the address is 127.0.0.1. If the 7K data
server is running on another computer then the address is the IP
address of the other computer.
Protocol
The protocol has to be UDP/IP.
This port can be used for all 7K drivers that need information from the 7K
data server, like the multibeam, the side scan sonar and the snippets, or
send information to the 7K data server, like the output to 7K.
10.5.1.8 OPC
The OPC communication port is a kind of network connection. The port
cannot be selected it will automatically selected when an OPC device is
selected.
Figure 10-13 OPC server has to be selected for the OPC communication
10.5.1.9 NCC
This type of communication port is needed for the Navisound echo
sounders. The port is a dummy port which is used in PDS2000 to
communicate with the Navisound. The actual port and settings are
defined in the Navisound Control Center (see page 99).
The NCC port is automatically created when a Navisound echo sounder is
selected in the Equipment. So it is not necessary to add a NCC port, but
when by accident the port is deleted while the Navisound is already
selected then the port can be added. It is not needed to define the baud
rate, etc. because this will be done in the Navisound Control Center.
There can be only one NCC port in the Interfacing available.
10.5.1.10 Edgetech
The Edgetech communication port is a network connection and is specific
for the Edgetech side scan sonar system. This communication port is
identical with the Socket port as described above, only the Local port and
the multicast are disabled.
10.6 Import
On several places in PDS2000 data files can be imported and converted
to information that can be used in PDS2000. The different import
possibilities will be discussed in the different modules of PDS2000.
The import in the Control Center is made to convert data files to PDS2000
log data files.
If the Select Tool dialog is
not visible, select File > Select from the menu bar the option Tools > Import or click on in the
New from the menu bar or toolbar to open the PDS2000 Import Utility. When the PDS2000 Import
click on in the toolbar Utility window is opened it will be an empty window with the Select Tool
to open the dialog. dialog on top of it.
Select in the Select Tool dialog the type of import for which a new import
configuration has to be created or select an existing import configuration.
An existing import configuration can also be opened with File > Open from
the menu bar or with from the toolbar.
If a new import configuration has to be created it is also possible to use
an existing import configuration file as a base. Check the option Copy
from existing config file and select the file that has to be used as a start.
At the end of the configuration the new import configuration can be saved
by clicking on in the toolbar or select File > Save As… from the menu
bar.
If there is already an import configuration that can be used with the import
files check the option Open existing and select the right import
configuration.
At the moment the PDS2000 Import Utility can import the following data:
Single Beam XYZ (see below)
XTF (see page 183)
S7K (see page 184)
SZ (see page 186)
Simrad EM3000 (see page 187)
This page will appear for all three formats. The number of columns on this
page depends on the selections in the pages before.
Click on to add a data file to the file selection. If in the runline
options page (see page 176) the option Pick runline from project is
checked and/or in the ASCII file options page (see page 176) the option
Timetag generation from start time and ping rate is checked, an Edit
Import File Settings window will be opened after the selection of the
file(s).
Import file
The added data file from the File Selection page.
Runline File
Select with an existing runline from the project.
This option will be shown if the option Pick runline from project in the
run line options page is checked (see page 176).
The next three fields will be shown if the options Timetag generation from
start time and ping rate in the ASCII file options page (see page 176) is
checked or the ASCII (X,Y,Z) data file with or without an ID is selected.
Start date
Click on next to the date and select in the calendar the right start
date.
Start time
Set the right start time of the first XYZ in the data file. Select the hours,
minutes or seconds with the mouse, type in the right value or use the
up and down arrows to change the numbers.
Ping rate (Hz)
Set the frequency for the XYZ data; how many times per second is the
XYZ data presented in the data file.
Click on in the Edit Import File Settings window to go back to the
file selection page. With in the file selection page, the Edit Import
File Settings window can be opened to check or modify the import file
settings. will only be active if a runline, date or time can be set.
If all the data files are added and the runline, date and time are set, click
on .
To click on behind one of the options will start the wizard for the right
settings of the selected option. It depends on the selection of the ASCII
data file and on the selections made in the pages before which parsing
options will be available on this page.
The different parsing options can be:
1. Parsing Of Date, Time, X, Y, Z for Channel 1 or Channel 2
2. Parsing Of X, Y, Z for Channel 1 or Channel 2
3. Parsing Of X1, Y1, X2, Y2 For Runline
Option 1 and 2 starts with the parsing of the XYZ data (see below). After
that option 1 will continue with the parsing of the date and time (see page
182) and option 2 will be finished. Option 3 is a separate parsing option
(see page 183).
If the parsing of one of the options is finish a checkmark ( ) will be
placed before the option. If all the parsing is done will become
active. Click on and the first page of the import utility will be
opened again.
On this page the settings for the XYZ data are set, so that on the next
page the right columns with XYZ data can be selected.
File
The filename displayed in the file box is the first file from the file
selection page. At the bottom, in ‘Preview Data’, the data of that file is
shown.
Original data type
Delimited. Check this option if the data is separated with a delimiter,
such as a comma, a tab or a space.
Fixed Width. Check this options if the data is aligned in columns with
spaces in between.
Skip lines
Check this option if the first line(s) of the data file(s) contains
information that is not runline data or XYZ data.
Give a number for the number of lines that have to be skipped.
Line ID
Give an ID for the lines that have to be extracted from the data file. If
an ID is given, the preview data will change and will only show the
lines in the data file with the given ID. In the example shown above,
the ID for the XYZ data is ‘EC’ and for the runline ‘RT’.
If all the settings are set, click on to go to the second page for
parsing XYZ data.
This page will appear when Delimited is checked on the first page of
parsing XYZ data. If Fixed Width is checked the page will be similar as
the page for parsing the date and time, only the sub items will be X, Y, Z
and optional date and time (see page 182).
On this page the delimiter and the columns have to be defined.
Delimiter
Select a character as delimiter between the data fields. The options
are comma, tab, space or custom. With custom a user defined
character can be added.
If in the ASCII file options Fields
page (see page 176) the If a column is selected in ‘Select Column Names’, a column number
option Timetag parsing is will be added to the selected field name.
checked, also the date and
the time column have to be Select column names
selected. Click with the right mouse button on a column and select one of the
available field names for the selected column.
If all the columns which are necessary for the import are selected, the
button will become active (only for parsing XYZ data). Click on
and go back to the first page of the import utility.
If the parsing contains a date and time, the ASCII Parsing Wizard will
continue with parsing date and time (see below).
The locations of the year, month and day in the date column are defined
with a start and end position in the column.
Double click in ‘Column For Field Name:’ on year, month or day and an
edit window will be opened.
Start Position
Set the start position of the item; in the example above the month
(here 02) starts at position 5.
Stop Position
Set the stop (end) position of the item; in the example above the
month (here 02) stops at position 6.
Factor
The multiplication factor should be 1.
Offset
An offset can be added to the selected item value to get the right
value. If for instance the year is presented in the data file as 05, then
with an offset of 2000 the year becomes 2005.
If the year, month and day are set, click on to go to the page for
parsing the time. This page works similar as the page for parsing the
date, only here are the items hour, minute, second and millisecond. If the
hour, minute and second is set (millisecond is optional) becomes
active.
Click on to select the XTF file for the import. It is possible to add
more XTF files before the import is started.
Check one of the options Import sidescan data, Import snippet data or
Import tide data if side scan data, snippets or tide data is available in the
XTF file(s) and have to be imported.
Click on to start the import of the XTF file(s).
Click on to select the S7K file for the import. It is possible to add
more S7K files before the import is started.
For bathymetry data at least the following records should be logged in the
S7K file:
For Position :1003; or 1015
10.6.3.1 Offsets
When in the S7K file(s) the record 7030 is missing, automatically an
offsets dialog will be opened. The offsets for the Position, Attitude,
Multibeam and Sealevel can be added manually or loaded from a file.
In the file all the items in the dialog should be mentioned with the terms as
displayed below in the text file.
Check the option Apply to all files when for all the S7K files in the import
the same offsets have to be applied.
Click on to select the ALL files for the import. It is possible to add
more ALL files before the import is started.
Check the option Apply imported sound velocity profile to PDS2000 file
when the imported sound velocity profile data from the ALL file has to be
applied to the created PDS2000 logdata file. When more ALL files have
the same sound velocity profile only one sound velocity profile file is
created in PDS2000.
Click on to start the import of the Simrad EM3000 file(s).
Survey data
A XYZ file have to be selected with . From this XYZ data file a grid
model will be generated and that grid model will replace the grid model
in the plot template.
The Name Prefix is automatically generated when the XYZ data file is
selected. The user can modified the prefix if he wants. The prefix
name will be used in the plot file and in the DXF file.
Check the option XYZ file contains Depths when the Z values in the
XYZ data file are depths. This is necessary because the depths in the
grid model are negative heights. So the Z values from the XYZ file get
a minus sign when the option is checked.
DTM
The generated grid model will Set the cell size for the grid model that have to be generated from the
be store with the name of the XYZ data file. The cell size doesn’t have to be the same as in the XYZ
XYZ file in the project. data file.
A Batch Plot setup file (BPP file) can be opened. This file contains all
the information to set all the items in the Batch Plot dialog.
Saves the setup and specify the name for the BPP file.
Prints the generated plot to the printer that is selected in the Print
Setup dialog.
Creates a plot file with the prefix name, date and time in the selected
plot project.
Creates a DXF file with the prefix name, date and time in the project
folder.
Closes the Batch Plot dialog without saving the setup in a BPP file.
Figure 10-33 Quick Profile Plot with a plot project and a plot template selected
In the tabs Filesets, DTM, Design and Text the right files for the profiles
plots can be selected and also the right text can be specified.
Under Select Runlines the runlines files or a set of runlines can be
selected which will be used to generate the profile plots.
10.8.1.1 Filesets
If in the profile panel of the plot template log data is specified as a layer
then with this tab the file set for the profile plots can be specified. Click on
to select an existing log data file set in the project for the
selected layer.
10.8.1.3 Design
If the setup with the file selections is saved, the saved setup can be
opened again. Before
selected.
is used the plot project has to be
If the setup with the file selection is finished, the setup will be saved
with the name of the plot template.
If the setup with the file selection is finished, the setup will be saved
with a name specified by the user.
For each runline that is selected in the Select Runlines box a preview
of the plot will be displayed. Click on in the preview file plot to
close the preview and continue with the preview of the next selected
runline. The preview can be stopped by closing the file plot preview
with .
For the selected runline in the General tab a preview of the plot will be
displayed. Click on or to close the preview.
For each runline that is selected in the Select Runlines box a profile
plot will be generated with the setting as specified in the different tab
pages. Each profile plot will be placed in the plot project as a separate
plot file with the name of the plot template and a sequence number.
After the plot files are generated they will be printed.
For each runline that is selected in the Select Runlines box a profile
plot will be generated with the setting as specified in the different tab
Before the DXF file can be created the plot files has to be generated
as discussed above in the option .
After the plot files are generated for each plot file a DXF file will be
created and will be placed in the plot project directory.
If a lot of DXF files has to be created, it can take a long time before the
creation of all the DXF files is finished. Move the cursor over the plot
icon ( ) in the taskbar and a display will tell the user how many tasks
(DXF files) still have to be processed. In the example below still 176
DXF files has to be created.
The Quick Profile Plot will be closed and the setup will not be saved.
The two default user accounts, Administrator and Basic Operator, do not
have a password yet. If the user wants a password to protect these two
accounts, select a user account and click on to open the User
dialog to add a password.
Enter the password in the field Password and repeat this in Retype
password. With the option Show password the actual text of the password
is displayed, if this option is unchecked only dots will be displayed (see
above).
At the moment are two access level present. With a new
access level can be added or an existing user level can be modified (see
below).
Figure 10-46 Manage user level access window with the two default access
levels, Administrator and Basic Operator.
In this window the menu options from the Control Center, the Acquisition
and the Presentation that can be switched on/off are displayed. The menu
options that are accessible in all different access levels are not displayed.
Check the option Make copy of access level if an existing access level
has to be used as base for the new one. If the option is unchecked all the
menu options in the new access level will be switched off (set on No).
Figure 10-48 Manage user level access window with new user level
Click on a Yes or No in the window and the selected menu item can be
changed. So is in the figure above the menu item Logging/Logging
Settings in the Acquisition changed to Yes.
Figure 10-49 New user account with the new user level
On the top right side in the application the user account can be changed.
Select the option and select one of the available user accounts. If for the
user account a password is added, then the user has to enter the
password before the selected user account becomes active.
10.11 Language
At the moment, next to the English language, the other languages that are
available in PDS2000 are Deutsch (German), Français (France), Italiana
(Italian), Nederlands (Dutch), Russian and Chinese.
If PDS2000 is running in a not English language it is possible that not all
items in a menu or in the text of the menus are in the right language. The
translation is made for a specific version of PDS2000, so if software
modification took place after that version the new items or text will be in
English.
Select from the menu bar of the Control Center the option Tools >
Options…and in the Language tab select a different language for
PDS2000.
Figure 10-52 Message to restart PDS2000 to made the new language active
Restart PDS2000 and the selected language will be the active language
for PDS2000.
The message is only a warning that the performance can be better if the
advice as mentioned in the message is followed.
When one of the checks failed the following text will be displayed.
Select the user general folder and automatically the selected folder will
become the folder used in the User General tab in the Explorer.
11.1 Introduction
PDS2000 uses different types of data files to store the relevant
information and settings. All these data files are accessible through the
Explorer.
It is also possible to use The Explorer is one of the windows that is available in the Control Center.
the context menu of the If the Explorer is not present in the Control Center, select View from the
Control Center to add or menu bar and check Explorer. To remove the window from the Control
remove the view. Center uncheck Explorer.
In the Explorer the information is divided in seven databases.
Projects Common
The settings and data files from the ‘Projects Common Files’ folder in
the PDS2000 Projects directory (see page 214).
PDS2000
General settings that can be used by all the applications and projects
in PDS2000 (see page 215).
Project
Project related settings and data files (see page 219).
Log Data
All available types of project related log data files (see page 244).
Multimedia
The multimedia files in PDS2000; the AVI, BMP, JPG and (Geo)TIFF
files (see page 246).
Report
The report files in PDS2000; CSV and PDF files (see page 248).
Sonar Targets
The sonar targets files with the GeoTIFF images of the targets (see
page 248).
Icon Images
The icon images files with the BMP and JPG images for the icons (see
page 248).
In the Explorer a directory structure is made with a separate folder for
It is possible to drag files each data type. The folders with in front of contain data files. Click on
and folders from for or double click on or the folder name to open the folder and make the
instance Windows Explorer data files accessible. With double click on one of the data files the specific
to the PDS2000 Explorer. editor for that data file will be opened. Notice that not all the data files
have their own editor.
At the moment for some data files a preview is available. Select a file and
on the right side in the Explorer, if possible, the data will be displayed. If
which contains the communication settings for COM and NET ports, and
the CustomActions[<module>].ini file, which contains actions defined
by the user.
When using the RESON 7k distribution module, the R7KDistribution.ini
file should be added to the backup.
Care must be taken when restoring project backups, since the backup
New File
For some files the New File A new file for the selected file group can be made and the editor of that
and/or the Add Files file group will be opened.
options are not active,
because there is no editor Add Files
available or it is not Add files to the selected file group. Files can be selected in a standard
possible to add files. dialog window. The file type is set to the file extension for the selected
file group.
Backup
A backup of the selected file group will be made. All the files in the file
group will be compressed to a ZIP file, which can be stored on any
location on the PC.
Refresh
Refresh the view in the Explorer.
Edit
For some files the Edit Will open the editor belonging to the selected file. In the editor the file
and/or the View options can be checked and/or modified.
are not active, because The editor can also be opened with a double click on the file.
there is no editor available
or it is not possible to view View
the file in Notepad. Will open the selected file in Notepad where the file can be checked
and/or modified. It is better to use the editor to modify the file.
Delete
Use the Ctrl key and the Delete the selected file(s) from the file group. It is possible to delete
Shift key to select multiple
files.
more files at the same time.
Also the ‘Delete’ key on the keyboard can be used to delete the files.
Rename
Change the name of the file.
Duplicate
Make a copy of the file. The copy will be placed in the same file group.
displayed. The message ‘No proper chart scale level available’ will be
displayed in the contour of the charts and the location of the charts is
hatched.
The file group context menu has other options than the standard
context menu:
Set as default database – With this option the selected database can
be set as default, which means that the selected database will be used
in the C-Map layers in PDS2000. It is also possible with the Chart
Manager from C-Map to set a default database.
Unregister database – The selected database will be unregistered
from the available databases in the Chart Manager.
C-MAP Filters
There are three C-Map filters available; for not showing the buoys, the
buoys and beacons and the buoys, beacons and piles in the C-Map
layer (see page 36).
Color Maps
The four different display modes (light conditions) which are available
in the Control Center, the Acquisition and the Presentation (see page
165).
Coordinate System Databases
A new coordinate system The different databases for the coordinate systems. The
that is created through pdsgeodatabase is the database with the coordinate systems as given
New File, will be stored in by PDS2000 and the pdsusergeobase is the database with the
the pdsusergeobase. coordinate systems made by the user. see page 71 for more
information about the coordinate system database.
Devices
The devices which are available in the Equipment page (see page 96).
Display Support Files
The files with setup information for different modules in PDS2000.
Dredge Status Configurations
The configuration files with dredge settings special made for Boraciet.
In these configuration files are defined which button are available in
the Manual Input – Dredge Status view (see page 304) and how the
flow will be displayed in the Dredge – SCADA view (see page 290).
These configuration files are only available for Boraciet application
types.
Formats
The formats as defined in the project configuration (see page 59).
PDS2000 Bitmap (BMP) Images
The BMP files as used in the views in PDS2000.
Presentation Definitions
The views which can be opened in the Control Center, in the
Acquisition and/or in the Presentation.
System Files
The system files as used by PDS2000.
Units
The units as defined in the project configuration (see page 58).
Wave Sounds (WAV)
The WAV files for the alerts sounds as specified in the Alert Sounds
page of the Project Configuration (see page 62).
Processing
Information will be displayed for each converted file.
For each file conversion a log file is generated with the conversion
information, warnings and errors. With this button the list with log files
becomes available.
11.4.1.1 Updates
The original file has When updates for the S-57 charts are available then the updates and the
extension 000, while the original S-57 file have to be converted at the same time. The update files
updates have 001, 002, need the original file to do the conversion to the C-Map database.
etc.
The original file cannot be the old original file that is converted before;
there should be a new one next to the update files. The new original file
knows how much update files are available and need them to make the
new database.
It is possible that the update is only a new original file. Then convert only
the new original file. Keep in mind that when the conversion is started the
folder with the existing database is replaced by a new database. So for an
update of some files all S-57 files have to be converted again to create a
new C-Map database.
database when the module is started. If modifications are made to the
files in the project database, the module have to be closed and started
again before the modifications are visible in the module.
The different file groups of the project database will be mentioned below.
The groups or the editors of that group that are not discussed in other
chapters of the manual will have a detailed explanation.
3D Models
The 3D models that can be used as a guidance in the project (see
page 143).
3D Objects
The 3D Objects file with the objects as added to the 3D Object
Manager in the Acquisition (see page 255). There will be only one 3D
Objects file per project.
Don’t rename the file otherwise the objects aren’t visible anymore in
the 3D view.
Alarms
The alarm files as created in the vessel configuration. These files can
only be edited in the tab Alarms of the vessel configuration (see page
129).
BSB Charts (KAP)
The raster (navigational) charts in BSB file format. The extension for
the BSB charts is KAP.
Import from DXF files is an extra option in the file group context menu
of the clipping polygon. A DXF file can be imported with the restriction
that the data in the DXF file contain only one polygon.
Export to DXF file is an extra option in the file context menu of the
clipping polygon. A clipping polygon file can be exported to a DXF file
and will be stored in the project.
It is possible to import multiple DXF files and also to export multiple
clipping polygons in one time. Each DXF file that is imported becomes
a clipping polygon file and each exported clipping polygon file
becomes a DXF file.
Color Tables
The color tables that can be used for the grid models, the 3D views, in
the plotting, etc (see page 226).
Configurations
The different configurations that are created in this project. The active
configuration can also be opened with Acquisition > Configuration from
the menu bar or with in the toolbar of the Control Center.
Import from DXF is an extra option in the file group context menu of
the runlines. From the DXF file only the lines that contain two points
(straight lines) can be converted to runlines. The lines have to be of
the linetype ‘Line’ One runlines file will be generated with all the lines
from the DXF file.
Figure 11-16 File group context menu of the Track Guidance Routes
Import from DXF is an extra option in the file group context menu of
the track guidance routes. From the DXF file only the polylines can be
converted to track guidance routes. For each polyline a separate track
guidance route will be generated.
User Interface Profiles
The UI Profiles which are used for the Control Center, the Acquisition
and the Presentation(s). These profiles contains the settings of the
toolbars used in the three windows. When the user changes one of the
toolbars it will be saved and the next time the new toolbar layout will
come up. Delete in the Explorer the UIP file of a window, if the user
wants to go back to the original (default) toolbar for that window.
User Maps
The user maps are files with user objects that can be created in the
plan views. The different user objects are lines, rectangles, circles,
polygons, text and symbols (see pagexxx).
User Presentation Defaults
There is only one file available, the file ‘EditorView’ and it contains all
the defaults for the editors. When in the context menu of a view the
option Save as Default is selected, the file ‘EditorView’ will be created
or updated.
Export Waypoints to Geo is an extra option in the file context menu of
the waypoints. The waypoints will be exported to an ASCII file
containing the waypoints with their geographical coordinates.
Work Areas
The created work areas that can be used as a guidance in the project
(see page 147).
added in the upper right corner of the editor. Click on to select the
coordinate type, grid or geographical coordinates. Click on to
insert a point above the selected point in the table and click on to
delete the selected point in the table.
In the menu bar some extra functions are available:
Options > Electronic Chart…
Select a PDS1000 electronic chart as background.
Options > Grid Properties
Select the grid to be shown in the view of the editor: Grid Crosses,
Solid Line Grid, Dotted Line Grid or a Scale Bar. The grid can be with
or without a grid annotation.
Options > Import from ASCII…
An ASCII import wizard will be started to guide the user through the
import settings. This import wizard is the same type of import wizard
as discussed on page 136. The ASCII file should contain the X and Y
coordinates of the clipping polygon.
Options > Import from DXF…
Select a DXF file with a polygon and the polygon will be imported in
the Clipping Polygon editor.
Figure 11-19 Color Table generator with a color table added (between 0 and -5)
to the existing color table
Add the values for the maximum and minimum range, select the number
of colors or the step size and click on to create a color table. With
a color table can be added to the existing color table.
If the option is selected the generator will use the whole color spectrum
to generates the colors. It will start with the selected color for the
maximum value and will stop with the color of the minimum value. With
the option only the two selected colors will be used to generate the
color table. The color starts with the selected color for the maximum value
and will stop with the color of the minimum value and for the intermediate
values the colors will run into one another.
With this option the whole spectrum will be used to go from the
color of the maximum value to the color of the minimum value.
Select one of the colors on the left side and click on . A Color
Table Entry dialog will be opened where the color and the minimum
value for the selected color can be changed. Click on to
confirm the change and a star will be placed in the edited color as an
indicator (see below).
Will show only the color table, there will be no buttons to generate a
color table.
Will show the Color Table generator again. This button appears when
is used to show only the color table.
In this color table only the colors and the text of the labels can be
modified. Click on if it is needed to reset the colors and text to the
default settings.
Double click on one of the colors and the Color Table Entry dialog will be
opened.
Figure 11-25 Color Table Entry for the bottom classification color table
For the values between the minimum and maximum value as displayed
on top of the dialog a different color can be selected and another text can
be entered.
It is not possible to modify the range and the steps for this type of color
table.
The dredge differential color table generator has three section; above
underdredge limit, below overdredge limit and between the two limits. For
each section the number of colors and maximum/minimum color can be
set. The edges between the section are defined by the underdredge limit
and overdredge limit.
In the Acquisition the underdredge limit and overdredge limit will be
automatically synchronized with the settings of the design model. So
when the limits for the design model are specified as 1 and -1 then the
limits in the color table will be changed from 0.5 to 1 and from -0.5 to -1.
The color scheme stays the same.
See the 3D View – Online Dredge on page 274 for an example of the
dredge differential color table.
If a new contour definition has to be generated, the left side will be empty.
Start then with or generate a contour definition with the option
or .
A contour line can be added to the list on the left side. A Contour
Properties window will be opened, where the settings for the line can
be set.
Add a value for the level and select a color for the contour line.
For the line style three options are available; a continuous, a dashed
or dotted line.
Give a line width for the contour line.
If a label with the depth value has to be plotted, check the option
Show labels.
Will edit the selected contour line. The Contour Properties window will
be opened (see above).
A color table will be used to generate the contours. Each value from
the color table becomes a contour line with the color from the color
table.
Create a new template. Give a name for the new template and add the
offsets and heights.
Click on to add a new exclude area to the list. Check the option
Polygon or Route and select the right clipping polygon or route with a
tolerance. The clipping polygon or route should exist in the project.
The selected template can be edit. The Add to Design Model window
will be opened (see above).
Before a design profile template can be added the right track guidance
route has to be selected. After that a template can be added with
. An Add to Design Model window will be opened where the
template can be selected.
The selected template can be edit. The Add to Design Model window
will be opened (see above).
When a new sound velocity profile is created the editor will be empty. The
table of the profile can be filled manually or an ASCII file with sound
velocity data can be imported with the option . Before this button is
opened to select the type of import the user has to select which part of the
data has to be imported; the upcast, the downcast or both.
The units for the four columns are not depending on the settings in the
project configuration (see page 58). The depth is always in meters, the
velocity is in m/s, the temperature is in °C and the salinity is in parts per
ton (ppt).
To add a SVP value to the table, fill in a depth value on the empty place
at the bottom of the depth column. When the next column is selected the
depth values will be automatically sorted.
A depth value can be deleted by selecting one of the values in a row and
click on . The whole row will be removed from the table. With