508XT V2 1 DCM Functional Vol2

XT
508
Functional Manual
Vol. 2 (DCM)
V2.1
Ref. 10048022 AA February 5, 2020

My Sercel > 2
My Sercel
For a complete library of Technical Documentation please visit the My Sercel
customer Extranet.
My Sercel provides the latest:
• User Manuals
• Software Updates
• Engineering Updates
• Maintenance Procedures
• E-mail notifications for the latest technical updates.
Figure 2-1 My Sercel Homepage
Click here to request a My Sercel account. http://customer.sercel.com or use the

following QR code
2
To contact Sercel
Europe North America
Nantes, France Houston, Texas, USA
Sales; Customer Support; Manufacturing & Repair Sales; Customer Support; Manufacturing & Repair
B.P. 30439, 16 rue de Bel Air Tel: +1 281 492 6688, Fax: +1 281 579 7505
44474 Carquefou Cedex Hot-Line: +1 281 492 6688
Tel: +33 2 40 30 11 81, Fax: +33 2 40 30 19 48 E-mail: sales.houston@sercel.com
Hot-Line: Land: +33 2 40 30 58 88 HOU_Customer.Support@sercel.com
Marine: +33 2 40 30 59 59 HOU_Training@sercel.com
Navigation: +33 2 40 30 69 87 HOU_Customer.Repair@sercel.com
E-mail: sales.nantes@sercel.com Tulsa, Oklahoma, USA
customersupport.land@sercel.com Tel: +1 918 834 9600, Fax: +1 918 838 8846
customersupport.marine@sercel.com E-mail: support@sercel-grc.com
customersupport.navigation@sercel.com sales@sercel-grc.com
repair.france@sercel.com
streamer.repair@sercel.com Middle East
www.sercel.com
Dubai, U. A. E.
St Gaudens, France Sales; Customer Support; Repair
Vibrator & VSP Customer Support; Tel: +971 4 8832142, Fax: +971 4 8832143
Vibrator Manufacturing & Repair Hot Line: +971 50 6451752
Streamer Manufacturing & Repair E-mail: dubai@sercel.com
Tel: +33 5 61 89 90 00, Fax: +33 5 61 89 90 33 repair.dubai@sercel.com
Hot Line: (Vib) +33 5 61 89 90 91
(VSP) +33 5 61 89 91 00
Far East
E-mail: customersupport.vib@sercel.com
customersupport.vsp@sercel.com Beijing, P. R. of China
Research & Development
Brest, France Tel: +86 106 43 76 710,
Sales; Customer Support E-mail: support.china@geo-mail.com
Tel: +33 2 98 05 29 05; Fax: +33 2 98 05 52 41 repair.china@geo-mail.com
E-mail: sales.nantes@sercel.com
Xushui, P. R. of China
Toulouse, France Manufacturing & Repair
Sales; Customer Support Tel: +86 312 8648355, Fax: +86 312 8648441
Tel: +33 5 61 34 80 74; Fax: +33 5 61 34 80 66 Singapore
E-mail: support@metrolog.com Streamer Manufacturing; Repair; Customer Support
sales.@metrolog.com Tel: +65 6 417 7000, Fax: +65 6 545 1418
info@metrolog.com
Russia
Moscow, Russia
Customer Support
Tel: +7 495 644 08 05, Fax: +7 495 644 08 04
E-mail: repair.cis@geo-mail.org
support.cis@geo-mail.org
Surgut, Russia
Customer Support; Repair
Tel: +7 3462 28 92 50
Regulatory Information >
Regulatory Information
European Union Statement
508 products meet the essential requirements of Directives RED 2014/53/UE (Radio), 2014/
30/UE (EMC), 2014/35/UE (Low Voltage) and 2011/65/UE (ROHS).
WARNING
The 508 products are class-A devices. In residential areas, the user may be requested to take
appropriate measures in the event of RF interference caused by these devices.
FCC US Statement
SERCEL products comply with U.S. FCC according to FCC CFR47 Part 15.
Operation is subject to the following two conditions:
(1) These devices may not cause harmful interference, and
(2) These devices must accept any interference received, including interference that may
cause undesired operation
Note Sercel products has been tested and found to comply with the limits for a Class A
digital device, pursuant to part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment
is operated in a commercial environment. This system generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio
communications. Operation of this system in a residential area is likely to cause
harmful interference in which case the user will be required to correct the
interference at his own expense.
IC Canadian Statement
SERCEL products comply with Industry Canada EMI Class A requirements according to
ICES-003 and RSS Gen.
Les produits SERCEL sont conformes aux exigences Classe A de l’Industrie Canada selon
les normes NMB-003 et CNR Gen.
Note These devices comply with Industry Canada’s licence-exempt RSSs. Operation
is subject to the following two conditions:
(1) These devices may not cause interference; and
(2) These devices must accept any interference, including interference that may
cause undesired operation of the device.
4
Regulatory Information > 4
China Regulation
508 Products comply with China ROHS 2.
5 February 5, 2020
License Agreement > 5
License Agreement
By downloading, installing, copying or otherwise using the present software and its
associated parts or items (« Software »), you, as licensee (“Licensee”) agree without
signature to the terms and conditions of the present software license agreement
(“Agreement”) issued by us (“Licensor) governed and judged by the French Laws and
French Courts in case of dispute resulting from its enforcement.
License.
The Software is copyrighted and licensed but not sold.
The license (“License”) is a non-exclusive, non-transferable, revocable license (with no right
to sub-licence) to use the object code version of the Software solely for the Licensee’s own
internal use for an indefinite period of time or during the term indicated by the Licensor, if
any.
The Licence allows copy for back up purposes only and does not authorise the Licensee or
anyone else to:
(a) Copy, reproduce, translate, adapt, vary, enhance or modify, merge, reverse engineer,
reverse assemble, decompile, or disassemble the Software or use the Software parts or items
separately;
(b) Remove from the Software any labels or notices (including copyright notices) as to the
Licensor’s ownership of the Software or any other intellectual property rights;
(c) Distribute, publish, transfer, licence, sublicense, sell, rent, lease, lend or make directly or
indirectly the Software or program documentation in whole or in part (including but not
limited to object code, source code and source program listings) available to other
organisations, entities or persons;
(d) Use or exploit the Software commercially or for the benefit of others;
(e) Create or attempt to create derivative works from the Software;
(f) Use the Software to violate the terms and conditions of any other software licensing
agreement between the Licensee and any third parties.
If Licensee is located in a country which requires a specific export licence or registration of
software licenses with government authorities, Licensee shall be responsible at its own cost
for meeting all requirement of such registration.
Import and Export.

Licensee is solely responsible for obtaining the necessary import licenses and any other
official authorizations and to carry out all customs formalities necessary and for paying all
associated costs, taxes and duties.
6
License Agreement >
Licensee acknowledges that Software and any related services and technology, including
technical information supplied by Licensor or contained in the Software or associated
documents (collectively “Items”), is or may be subject to export controls of any government
or community including but not limited to the U.S. government or E.U. Community (
collectively “Controls”). The export controls may ban or restrict or require licenses for the
export or re-export of Items from the United States or E.U. or any other countries. As a
consequence any delivery schedule and performance of any of Licensor’s obligation are
subject to the enforcement of any Controls and the obtaining of any licence if any, and
Licensor shall not be liable to Licensee for any damage and loss resulting thereof. The Parties
agree to provide each other with any reasonable assistance, in particular for the issue of any
document that may be required by relevant administration, to comply with the obligations of
this Agreement and the Controls and for this purpose the Licensee will complete the end user
statement submitted by the Licensor.
Warranty.
Licensor warrants that Software was developed with reasonable diligence and skill and that
it substantially conforms to published documentation.
Except as expressly provided above, Software is deemed to be accepted "AS IS", without any
further warranty of any kind, express or implied. The Licensor excludes, without limitation,
the warranties of merchantability, of fitness for a particular purpose and of non-
infringement. The Licensor does not warrant or assume responsibility for the accuracy or
completeness of any information, text, graphics, links or other items contained with the
Software.
Liability.
In no event shall the Licensor be liable for any claim or any damages including, without
limitation, direct, indirect, compensatory, special, incidental, punitive, exemplary or
consequential whether bodily, material or immaterial (such as, but not limited to loss of
profit or anticipated profits or revenues, loss of sales or data, contract, production, or
bargains, interruption of business, damage to goodwill or loss due to any delay) howsoever
caused including without limitation use or inability to use of the Software, breach of contract
(negligence included), breach of warranty, breach of duty (statutory duty included), tort or
otherwise even when Licensor has been advised of the possibility of such damages.
Confidentiality.
Licensee acknowledges and agrees that this Licence Agreement, any financial, business,
technical information, trade secret and Know How proprietary to the Licensor and contained
in the Software and/or in the documentation shall be deemed to be “Confidential
Information” and as such shall not be disclosed directly or indirectly by the Licensee to any
third party. Any breach of this provision by Licensee would cause Licensor to suffer
immediate and irreparable harm. In the event of such breach, Licensor shall have, in addition
7 February 5, 2020
License Agreement > 5
to any and all remedies at law, the right to an injunction, specific performance or other
equitable relief. Licensee’s obligation of confidentiality under this provision shall survive
expiry or termination of this Licence Agreement.
Intellectual property rights, patents and copyrights to Software.

Licensee acknowledges and agrees that all intellectual property rights and all Confidential
Information (whether existing or future) in and to the Software and in and to the associated
documentation belong or are licensed to Licensor and that Licensee only rights pertaining to
said intellectual property rights are these defined in this Licence Agreement. No title or
ownership of Software is transferred under this Agreement. Licensee shall take no action that
might impair any right, title or interest of Licensor as owner or as licensee in or to the
Software. Licensee shall not have any rights in or to any trademark or trade name owned by
Licensor with respect to the Software. Any breach of the provision here above of the present
provision by Licensee would cause Licensor to suffer immediate and irreparable harm. In the
event of such breach, Licensor shall have, in addition to any and all remedies at law, the right
to an injunction, specific performance or other equitable relief.
Termination.
The Licensor has the right to terminate this Agreement and Licensee's right to use this
Software upon any material breach by Licensee. The Licensee agrees to return to Licensor
or to destroy all copies of the Software upon termination of the License.
8
5
License Agreement >
(Page intentionally blank)

>
Revision history
Date of Manual Chapters or Description of revision or reason for

revision Version pages affected change
Jan. 2020 AA Initial document version.
10
>
My Sercel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1 Introduction
DCM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
508XT System Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 16
Terminology and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Working with DCM windows . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 Getting started
Opening a DCM user session. . . . . . . . . . . . . . . . . . . . . . . . . . . 22
DCM Graphic Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Using DCM with 508XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
XT-Pathfinder Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3 Data Completion Manager (DCM) Interface

DCM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
The Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Prospect Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Field Unit Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
View Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Noise Monitoring in Infrastructure Mode . . . . . . . . . . . . . . . . 123
Sensor Tilt Model creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Working with Stake IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Generate SPS-Out and Observer Reports . . . . . . . . . . . . . . . . 136
Archive/Restore prospect database . . . . . . . . . . . . . . . . . . . . . 143
DCM Trace Diagnostic Codes . . . . . . . . . . . . . . . . . . . . . . . . . 147
11 February 5, 2020
>
4 Position
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Position Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Field Units Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Settings Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Auto-assignment based on GPS positions and geometry correction
192
5 TraceView
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
The Menu Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6 Export
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Edit Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Actions Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
In queue view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Export Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7 SEG-D File Generator (SEG-D Gen)

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
SEG-D Gen tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Event Definition Text File format . . . . . . . . . . . . . . . . . . . . . . 259
Recorder Free Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
12
>
8 SEG-D Import Key Points

DCM compatibility with various revisions of the SEG-D format279
Importing Rev. 1 & 2.1 SEG-D files . . . . . . . . . . . . . . . . . . . . 280
Importing 508XT Rev. 3 SEG-D files . . . . . . . . . . . . . . . . . . . 281
Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1 . . . . . . . . . 283
9 Portable Field Terminal

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
PFT Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Creating a new WTU list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Collecting WTU Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Resuming a saved list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Toolbar and Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . 298
Transferring Files to the DCM server . . . . . . . . . . . . . . . . . . . 300
Transferring WTU List by USB drive . . . . . . . . . . . . . . . . . . . 304
10 Data Harvester
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Connecting to the DCM server . . . . . . . . . . . . . . . . . . . . . . . . 310
Harvesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Uploading data to the DCM server . . . . . . . . . . . . . . . . . . . . . 314
Field Monitor Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
File-based harvester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
WTU List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
WTU Topo View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Recommendations for maximum harvesting speed . . . . . . . . . 346
13 February 5, 2020
>
11 Glossary of abbreviations and acronyms

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
12 Index
14
Chapter
1 Introduction
This chapter includes the following sections:
• DCM Overview (page 16)

• 508XT System Documentation (page 16)
• Terminology and conventions (page 17)
• Working with DCM windows (page 20)
508XT Functional Manual

Introduction
DCM Overview > 1
DCM Overview
The Data Completion Manager (DCM) application, allows you to map WTU serial numbers
to line and station numbers, thus (when working with 508XT), for each incoming SEG-D file
with mute traces, DCM software knows which WTUs to obtain data from.
For each shot, the Completion view shows the harvesting status of each WTU graphically,
with different colours depending on whether or not the trace data is harvested.
After the server has replaced all mute traces in one shot with the seismic data from the
mapped WTUs, the complete SEG-D file can be generated in one click and exported to FTP
servers or disks.
508XT System Documentation

Documentation included with the 508XT system is available on the accompanying USB key
provided with your system (ref. 10040994) or on the My Sercel Extranet. If you do not have
a My Sercel account please click the following link to request access.
My Sercel account request
Documentation for the 508XT system consists of the following manuals:
• Installation Manual: provides an introduction to the 508XT system, installation
information, a few instructions for the operator to get started, and reference information
that will help you select a 508XT configuration tailored to your needs.
• Functional Manual Volume 1: describes the parameters displayed on the 508XT
system’s Graphic User Interface (GUI) and how to use each window.
• Functional Manual Volume 2 (DCM): describes the Data Completion Manager (DCM)
application.
• Data Format Manual: contains information on logged data and on interfaces
(description of Input/Output formats, including the SEGD format).
• Technical Manual: contains maintenance and repair information, including operating
instructions for using the system’s testers.
16
Introduction
Terminology and conventions >
Terminology and conventions

To use this manual, you need to be familiar with a number of terms that are described below.
Click
To press and release a mouse button quickly (left-hand button, unless otherwise specified).
Command button
A pushbutton that carries out a command (Add, Change, Delete, Reverse) with the
parameters displayed in the text boxes.
Dialogue box
A secondary window that provides or requests information within a main window.
Double-click
To press and release the left-hand mouse button twice in rapid succession without moving
the mouse.
Field Units/WTU
Throughout this document the terms Field Unit and WTU are used interchangeably. DCM
software uses the term Field Unit to refer to WTUs.
Icon
A small graphical image used to represent a window. Windows can be turned into icons or
minimized to save room or unclutter the workspace.
Index box
A text box (usually the first box from left to right) showing the identification number of a
row (or set of rows) to be generated in a list box or selected from a list box.
Infrasructure Mode
Infrastructure mode refers to Field Units connected via a MAN or a network of MANs.
List box
A box used to display a scrollable list of the rows edited under a text box.
Mouse buttons
The left-hand button is used to click, double-click, and select an item.
17 February 5, 2020
Introduction
Terminology and conventions > 1
The right-hand button causes a contextual menu to pop up, if any is available.
Point (to)
To move the mouse pointer on the screen until it rests on the item you want to select.
Scrollbar
A rectangular box, with a slider and direction arrow graphics in it, used to scroll the visible
area of a window pane or box. The slider indicates the relative position and size of the visible
area. The position is adjusted by dragging the slider or clicking the direction arrows.
Select
To point to an item in a menu, by dragging the mouse pointer until the item is highlighted,
and release the mouse button.
Text box
An entry box used to enter or display values and/or text for a parameter within a dialogue
box.
Toggle button
A push-button composed of a label preceded by a graphic (circle or square) with two
distinctive states that indicate the set and unset states of the button.
There are two special cases of toggle buttons.
• Radio button: used to select one option from a number of options. Each option is
represented by a radio button. Each button represents a mutually exclusive selection
(only one radio button can be set at a time).
Figure 1-1
18
Introduction
Terminology and conventions >
• Check button: used to set a number of options. Unlike a radio button, any number of
check buttons can be set at the same time.
Figure 1-2
19 February 5, 2020
Introduction
Working with DCM windows > Views 1
Working with DCM windows

Views
Selecting table rows

You can copy content from a table in a numeric view to a text editor or to a spreadsheet tool.
To select the tables cells to copy, do the following:
1. Click in the first row to select.
2. Press the Shift key.
3. Click in the last row to select. As a result, the selected rows are highlighted.
Copy and Paste

The Copy function allows you to copy content from a dialogue box or table cell.
1. Select the text, or table cells, or objects to copy:
2. Copy the selected content as follows:
- right-click on your mouse button.
- or Ctrl + C
3. The Copy or Copy with Headers option is displayed.
4. Selected text may be pasted in a valid table cell or text editor using the Ctrl + P
command or clicking on the right-mouse button and selecting Paste.
20
Chapter
2 Getting started
This chapter includes the following sections:
• Opening a DCM user session (page 22)

• DCM Graphic Interface (page 27)
• Using DCM with 508XT (page 33)
• XT-Pathfinder Network (page 39)

Getting started
Opening a DCM user session > 2
Opening a DCM user session

To open a user session:
1. Double-click on the DCM icon on your desktop.
Figure 2-1 DCM icon
2. The connection window is displayed.
Figure 2-2 DCM Server Connection Window
The DCM server IP address and Port are standard. You may choose to modify these in case
of a customized network configuration.
3. If you would like to customize the IP address of the DCM Server click
Figure 2-3 Customize IP address button
22
Getting started
Opening a DCM user session >
4. If the Customize IP Address button is selected, the Connection configuration screen

is displayed.
Figure 2-4 Connection configuration
5. Click the ‘Add’ button. A new Connection name is attributed. You may modify the
‘Label’ and ‘Host Name’ of the connection.
6. Click OK to apply.
Figure 2-5 Configuration settings
7. The connection to the DCM Server will begin.
Figure 2-6 DCM Server connection
23 February 5, 2020
Getting started
Opening a DCM user session > Starting/stopping the DCM server 2
8. The DCM interface is now connected.
Starting/stopping the DCM server

The DCM server is started automatically when you power up the server computer. If you
need to restart the DCM Server, you can use the commands ‘dcm stop’ then ‘dcm start’ in
a terminal window.
Figure 2-7 Stop DCM Server
Figure 2-8 Start DCM server
24
Getting started
Opening a DCM user session > Updating Software Patches
Updating Software Patches

To install a patch on the server computer you must open Sercel applications in the Linux
menu.
1. Stop the DCM server (command ‘dcm stop’ in a terminal window).
2. Open the DCM Patcher, a shortcut is available in Linux Menu ‘Applications >
Sercel > Data Completion Manager > Patcher’.
Figure 2-9
25 February 5, 2020
Getting started
Opening a DCM user session > 2
3. Select the Patches that you would like to install.
Figure 2-10 Start DCM Patch Installer
4. Click Install New Patches.
26
Getting started
DCM Graphic Interface >
DCM Graphic Interface

This section teaches a beginner how to customize a main window (also referred to as “client
window”) in just a few clicks. The first time you log on to a DCM server, each main window
in the Graphical User Interface is configured with a default layout.
Note Your customized window layout is automatically saved on your computer as you
close the client window, and recovered when you next open it.
In most main windows, it is for you to decide how many views to show and where to place
them. The GUI may also let you decide which information to view, and which type
(numerical/graphical) of view you want for this information. The intent of the procedure
below is to give you a glimpse of what you can do to customize each main window.
Customizing windows
1. Open the DCM window by clicking on this icon in the launcher bar:
Figure 2-11 DCM launch icon
2. Right-clicking anywhere on the toolbar allows you to choose which buttons you
would like to show or hide in the toolbar. (All options are also available from the
menu bar).
Right-click to
customize launcher
Figure 2-12
3. Clicking on the left-hand (dotted) border of the toolbar and holding down the mouse
button allows you to move and dock the toolbar to whichever border you like inside
the window. Moving it outside the window will undock the toolbar (to dock it again,
simply close it by clicking on the button in the upper right corner of the undocked
toolbar).
27 February 5, 2020
Getting started
DCM Graphic Interface > 2
4. The Window Resize buttons in the corners of a display pane let you
expand or collapse the pane vertically or horizontally.
5. The Thumbnail button allows you to collapse the selected window
to the Toolbar.
6. The ‘X’ allows you to close the dialog box.
7. Adjust the width of each display pane by dragging the vertical border to the left/
right. Likewise, to adjust its height by dragging the horizontal border upward/
downward.
8. To show the different views available, use either the Window menu item or tool bar
buttons. When you choose to add a view, the new view pane appears below the
currently selected pane.
9. To hide any view pane, click on the close button associated with its tab.
10. If the pane is not large enough for the whole view to fit in, you can resize the main
window and/or use the available scrollbars.
In graphical views, you can zoom in by pressing the left mouse button,
moving the mouse, then releasing the button. Use the zoom control
buttons to zoom out or go back to the whole view.
11. Double-clicking on the tab of any view pane either expands or collapses the view.
12. You can customize the layout of the main window by placing the different views
where you like them: with the mouse pointer resting on the tab of any view pane,
press the left mouse button, then move the mouse so as to drag the tab to where you
would like the view pane to appear.
Placing tabs side by side will cause the view panes to be cascaded.
Where views are cascaded, you bring any view to the front by simply
clicking on its tab.
28
Getting started
Cascaded
A C
Figure 2-13
Also, view panes can be tiled vertically and/or horizontally. With the
example shown in Figure 2-13, dragging the tab to (A) will split the
window vertically and place the view into the left-hand pane.
Dragging the tab to (B) will split the window horizontally and place
the view into the bottom pane. Dragging the tab to (C) will split the
window vertically and place the view into the right-hand pane (see
Figure 2-14).
29 February 5, 2020
Getting started
Figure 2-14 Tiled views
13. Double-clicking on the Square button in the lower right corner or each main window
enables or disables the automatic updating of the window.
The button is green if automatic updating is enabled, red otherwise. (The
Preferences on page 49 — setup menu in DCM allows you to adjust the
refresh rate). The blinking of the heartbeat-like indicator at the foot of the window is
indicative of the window being refreshed.
The Import ON/OFF button allows you put in hold the automatic Import of SEG-D
files (from 508XT or SegdGen) when required.
Refresh indicator
Import ON/OFF
Enable/disable
Automatic
Update
Figure 2-15
14. System messages appear in the “Status Mail” pane at the foot of the main window.
Whether you choose to show or hide that pane, the orientation of the Mail icon in the
toolbar will tell you if any message is present (the mail icon being raised is
indicative of one or more messages being present). To delete mail messages, right-
click in the Status Mail pane and select “Clear Status” from the menu that pops up.
30
Getting started
Customizing tables
1. To resize a column, simply drag its border to the desired width. Some columns,
however, have a minimum width that you are not allowed to override.
Drag and drop

column heading
Drag border
to resize
Figure 2-16
You can change the order of columns by clicking on a column heading in the table, then
dragging and dropping it where you would like it to appear (unless you are not allowed to
move that column).
2. To select the columns to be displayed,
right-click with the mouse on the
table header and select Columns. This
open a panel with all available
columns concerning the current table.
31 February 5, 2020
Getting started
3. You can use the Filters tab to isolate rows of interest. This can be very helpful if the
table has many rows.
Figure 2-17
• Click on the filter icon on the right side on the column header to enable a filter on this
column.
• Then select in the dropdown list, the rows you want to display.
• A filter icon indicated to the user the filtered columns.
4. You can save your table configuration by right-click on the table header > Preset >
Save and entering a name for it in the dialogue box that shows up. Subsequently,
you’ll simply have to select the desired type of table, using the “Load File” button,
and click Apply to recover your preferred arrangement of columns at your
convenience.
32
Getting started
Using DCM with 508XT >
Using DCM with 508XT

When using DCM in conjunction with the 508XT:
• The 508XT drives the acquisition by controlling the source(s) and TBs and taking the
shots.
• The 508XT generates SEG-Ds containing the cable traces recorded for the spread and
possibly additional mutes for further replacement with WTU traces.
The user has 2 different options for the completion of the shots with WTU traces:
- Either the original spread defined in the 508XT already contains the future WTU
traces declared as mutes (they act as placeholders for future replacement in
DCM).
- Or the spread defined in the 508XT only contains the cable traces and the WTU
traces are added later at import in DCM by using the DCM script override
function.
Option 1 above gives the advantage of defining only 1 set of SPS files for both systems
whereas option 2 avoids the hassle of defining mutes in the 508XT interface but also reduces
the size of the SEG-D file produced by the 508XT that will be imported into DCM.
• The 508XT must produce RAW and correlated/stacked files (if relevant) as they are all
needed by DCM when importing.
See. SEG-D Import Key Points (page 278).
508XT
After the standard 508XT wire line telemetry instruments are deployed (as usual), the 508XT
application controls shots and generates SEG-D files containing the traces from all the
channels described in the spread (“Wireless” channels are mute and the resulting traces in the
SEG-D files are dead).
The following two steps are essential:
1. In the 508XT Field view, one Auxiliary (FDU) channel at least is required in the
Layout setup, even if unused. Set all “wireless” channels to “Mute”.
33 February 5, 2020
Getting started
Using DCM with 508XT > 2
At least one Auxiliary FDU
Mute channels
Figure 2-18
2. In the Operation Process Type setup, ensure the “Raw Dump” option is setup.
DCM
Each SEG-D file generated by the 508XT is imported into the DCM application. Wireless
(dead) traces are replaced with the matching harvested WTU traces. The following steps are
essential:
1. Before the WTUs are deployed in the field, connect them to a computer running the
DCM software to ensure that they are configured with the correct recording
parameters and testing options for the survey. See Field Unit Parameters
(page 87).
34
Getting started
Figure 2-19 Field Unit parameters
2. Layout WTUs at the planned receiver points in “wireless” patches (see 508XT
Installation Manual), then use a PFT to scan the serial number of each WTU and
record the list of WTUs deployed in each Line. See Portable Field Terminal
(page 286).
35 February 5, 2020
Getting started
Figure 2-20 Scanning WTU serial numbers
3. Launch DCM (see Opening a DCM user session on page 22).

4. When the PFT comes within range of the recorder network, the PFT button at the
foot of the DCM window turns green. Click on the PFT button to load the list of
WTUs from the PFT.
Figure 2-21 Loading WTU list
5. In the “Assign Markers” window, click Apply. As a result, the imported WTU serial
numbers are mapped to Line and Point numbers in the Topo view.
36
Getting started
Change
Change Receiver
Line order order
Point numbers
Line numbers
Figure 2-22 Topo view
The receiver positions of the mute channels (and also the mandatory auxiliary
channel if unused) recorded in the SEG-D files imported into DCM are
automatically marked as WTUs. Note that “wireline” channels do not appear in
the DCM window.
If any changes or corrections to Stake ID mappings are required, use the Change
Markers command. See Working with Stake IDs (page 130).
Figure 2-23 Assign Markers dialogue
6. The incoming shots from the 508XT system automatically appear in the VP Table
view. The list of outstanding VPs is automatically loaded into the Data Harvester
when it is connected to the recorder local network.
37 February 5, 2020
Getting started
Figure 2-24
7. Use the Data Harvester to harvest outstanding traces. See Data Harvester
(page 306).
8. Connect the Data Harvester to the recorder local network to upload harvested data to
DCM. The matching dead traces in each outstanding VP are changed into WTU
traces.
9. In the DCM window, select the VPs to process (VPs with or without outstanding
traces) and then select Process VPs to generate SEG-D files for those VPs. Note that
there is no limitation to how many times you can process a VP.
10. Use the Export Parameters (page 224) window to set up record parameters.
Note that the process of recording complete SEG-D files is done on the computer to
which the harvested data is loaded.
38
Getting started
XT-Pathfinder Network >
XT-Pathfinder Network
The XT-Pathfinder network is an intelligent and dynamic network, self-adaptive to changes
in the spread.
The Pathfinder network provides continuous monitoring of all channels through a multi-hop
wireless transmission network.
Figure 2-25 XT-Pathfinder network
The XT-Pathfinder network performs three key functions, as explained below.
39 February 5, 2020
Getting started
XT-Pathfinder Network > 2
GPS Position
Upon power-up the WTU acquires GPS position and establishes its position on the XT-
Pathfinder network. The WTU then sends its position to the DCM.
This allows an operator to perform auto-assignment. See Auto-assignment based on
GPS positions and geometry correction (page 192)
Note GPS position acquisition is performed only once upon start-up.
Figure 2-26 GPS position acquisition
Real-Time Alerts
The XT-Pathfinder network provides real-time alerts in case of failure.
Figure 2-27 XT-Pathfinder network real-time monitoring
40
Getting started
Real-time alerts are provided for the following parameters:

• Battery level
• Sensor status
• Memory status
• GPS status
• Ambient noise
Continuous Monitoring
Each WTU-508 regularly monitors the following parameters:
• Battery level
• Sensor status
• Memory status
• GPS status
• Ambient noise
The intervals at which the WTU sends status data to the DCM is defined by the user. See
SoH Refresh Period (page 102).
Figure 2-28 Continuous monitoring
Theft Alarm
In case a WTU-508 is no longer detected on the field, an alert will be signalled on the DCM
alerting the operator of a possible theft.
41 February 5, 2020
2 Getting started
42
Chapter
3 Data Completion Manager

(DCM) Interface
This chapter gives the user a description of the DCM application.
• DCM Window (page 44)

• The Menu bar (page 47)
• General Parameters (page 73)
• Prospect Parameters (page 74)
• Field Unit Parameters (page 87)
• View Panels (page 108)
• Noise Monitoring in Infrastructure Mode (page 123)
• Sensor Tilt Model creation (page 124)
• Working with Stake IDs (page 130)
• Generate SPS-Out and Observer Reports (page 136)
• Archive/Restore prospect database (page 143)
• DCM Trace Diagnostic Codes (page 147)

Data Completion Manager (DCM) Interface
DCM Window > 3
DCM Window
To open the Data Completion Manager window, click on the DCM launcher icon on your
desktop:
Figure 3-1 DCM launcher
Figure 3-2 DCM window
44
DCM Window >
DCM Tool bars
1 2 3 4 5 6 7 8 9 11 12 13 14 15 16
Figure 3-3 Tool bar
1. Open TraceView application. See TraceView (page 204).

2. Open Export application. See Export (page 218)
3. Open Positioning application
4. Export TB list to file
5. Import QCs from file
6. Generate Reports
7. Show the VPs view
8. Show the Field Units view
9. Show the Gateways view
10. Empty
11. Show the Completion view
12. Show the Topo view
13. Show the Status Mails view
14. Show the Tasks view
15. Show the Health view
17 18 19 20 21 22 23
Figure 3-4 Status bar shortcut buttons
16. Import SEG-D files (on/off)

17. Auto-scroll (on/off)
18. New PFT files available
19. Display SEG-Ds with raw data in TraceView (on/off)
45 February 5, 2020
DCM Window > 3
20. Generate SEG-Ds with raw data (on/off)

21. Idle
22. Connected
46
The Menu bar > File menu
The Menu bar

This section describes the functions available within the different menu bars of the DCM
interface. In this section:
• File menu (page 47)
• Edit menu (page 48)
• Tools menu (page 53)
• Actions menu VP Table (page 55)
• Action menu Field Units (page 59)
• Window menu (page 68)
• Help menu (page 70)
File menu
The File menu contains the following commands.
Figure 3-5 File Menu
• Connect To - Allows you to disconnect from the DCM server.

• Clear Prospect - Allows you to clear ALL prospect data. Please note, all data will be
deleted and cannot be restored.
• Exit - Allows you to close the DCM application.
47 February 5, 2020
The Menu bar > Edit menu 3
Edit menu
The Edit menu contains the following commands.
Figure 3-6
Cut
The Cut command allows you to Cut a selected item to the clipboard.
Copy
The Copy command allows you to copy a selected item to the clipboard.
Paste
The Paste command allows you to paste the item on the clipboard.
Find
The Find command allows you to search for an item in the currently selected table. For
example, if you select the WTU table and then use the function Find, it will search the input
term in this table.
Figure 3-7 Find command
48
The Menu bar > Edit menu
Parameters
The Parameters window allows you to define the parameters of your operation. Select
Parameters... from the Edit menu.
Figure 3-8 Parameters Window
• See General Parameters (page 73)

• See Prospect Parameters (page 74)
• See Field Unit Parameters (page 87)
Preferences
The Preferences menu makes it possible to customize DCM GUI options on each local
DCM Client.
Note These are local Preferences settings, ignored by any other Client connected to
the same server.
49 February 5, 2020
General
Figure 3-9 General preferences
• Communication:
- Refresh Delays - sets the rate at which DCM views are updated with new
incoming data.
• QC:
- Maximum QC Age - any WTU with QC information older than the value
specified here will show faulty in views where WTUs are displayed.
• Processing:
- Generate Raw records: tick this option if you want to generate
SEG-D files with raw (unprocessed) data.
Note that although this is a processing option, it actually is a local preference,
meaning that if another client connected to the same server chooses a different
setting the SEG-D output will be different (one client will get RAW files while the
other won’t).
- Display Raw records: tick this option if you want to display
SEG-D files with raw data in TraceView.
• Views:
- Synchronize Scroll: if you tick this option, then selecting an item (table row,
column or cell) in one view will automatically scroll to the same item (Auto-
scroll) in all other views currently open. Note that the View menu also lets you
turn on/off Auto-scroll.
- Display Super Spread: if you tick this option, after selecting several VPs, it will
display a “superspead” (a spread union) from the selected VPs and display it in
the Topo view. The “superspead” encompasses all the spreads used for the selected
VPs.
- VPs selection mode manual: if you tick this option, the VPs selection mode will
be manual. Otherwise the VPs selection mode will be automatic.
50
The Menu bar > Edit menu
Appearance
Format
Select your preferred format for a Short Date, a Long Date and for Time.
Figure 3-10 Format preferences
Completion
Figure 3-11 Completion preferences
51 February 5, 2020
Select your preferred colour code to show traces that are Outstanding, Not in script (out of
live spread), Complete (harvested with no errors), Failed (harvested, but QC at fault), and
your preferred time format for shots.
Topo
Figure 3-12 Topo preferences
Select your preferred colour code to show a Stake, a WTU, an Error, the Spread area, a
trace with a QC result regarded as Normal, Warning, Critical, and a WTU with No QC
result.
52
The Menu bar > Tools menu
Tools menu
Figure 3-13 Tools Menu items
Open TraceView
Shortcut to the TraceView window. See TraceView (page 204).
Open Export
Shortcut to the Export window. See. Export (page 218).
Open Positioning
Shortcut to the Positioning window. See Position (page 150).
Export TB list / Import QCs

This gives you access to the file-based DH feature commands. For a detailed description of
this feature, go to the Data Harvester (page 306) section of this document.
Export TB list allows you to generate a file that contains a binary description of all the
known TBs and WTUs (incl. their topographic locations) to harvest. This file can be
uploaded into the data harvester as if the data harvester had been connected to the server to
get the new list of TBs and WTUs to harvest.
A file browser window lets you choose the location where to save the generated file.
The file name format is tbList-${DATE_YYYYMMDD}_${TIME_HHMMSS}-
${NB_MARKERS}markers-${NB_TBS}tbs-${NB_WTUS}WTU.dat.
Import QCs allows you to import a QC data file that has been generated by a data harvester
application.
This will update in DCM all the QCs of all the WTUs that have been harvested by the DH
that produced the file.
A file browser window lets you choose the file to import.
53 February 5, 2020
The Menu bar > Tools menu 3
Process Reports
The Reports dialog, allows you to specify the time range be used to generate the
corresponding reports for the events already processed:
• O bserver Reports
• SPS Reports
See details in section Generate SPS-Out and Observer Reports
(page 136)
Figure 3-14 Generate Reports
54
The Menu bar > Actions menu VP Table
Actions menu VP Table

The Actions menu is contextual. The commands specific to the VP Table view are shown and
described below (also available from the right-click popup menu).
Figure 3-15 VP table Actions menu
Processing
Process VPs
After selecting one or more VPs, use this command to generate SEG-D files from those
shots. You can select VPs that have outstanding traces, but in that case the resulting SEG-D
files are incomplete.
There is no limitation to how many times you can process a VP. You may want to process a
VP prematurely and reprocess it once and again in order to generate temporary SEG-Ds at
different harvesting stages. (The Process Count in the VP Table view indicates how many
times a VP has been processed).
55 February 5, 2020
The Menu bar > Actions menu VP Table 3
Preview VPs
Incomplete shots can be exported to a preview SEG-D file without having to permanently
process the data. This allows SEG-D files to be produced for analysis while still waiting for
outstanding data.
Previews can be generated as many times as required. Preview SEG-D files are placed in a
different folder than the final SEG-D files, so if export is set up this will mean these files will
not be exported.
Any outstanding channels will be marked as dead in the SEG-D trace header, though
TraceView will be still able to determine that these traces were outstanding. Other than these
small details, preview files are identical to the normal SEG-D format.
Delete VPs
Use this command when you want to delete processed VPs.
Update
Update markers in VPs
This command allows changes and corrections to Stake ID mappings (markers) to be applied
to shots that have already been taken, and even to processed SEG-D files. See Updating
Stake ID Mappings (page 132).
Figure 3-16 Update Marker Mapping
Update Process Types

After selecting one or more VPs in the VP Table, Update Process Types applies the settings
from the Process Types (page 77). This brings up a confirmation window. No
additional setting is required. You are notified of successful updating in the Status Mail
panel.
For example, you may want to do this after making changes to the Process Type setup. This
will apply the description of auxiliary traces to the selected VPs, depending on the filters
56
The Menu bar > Actions menu VP Table
specified in the Process Type setup: if any VP in the selected list matches the Process Type
filter settings, then the Aux descriptor for that Process Type overrides its former Aux
descriptor.
Update Sensor Codes

At the moment an SEG-D file is imported into DCM, the Sensor Code table
(page 84)specified in the Prospect parameters overrides the SEG-D sensor code and sensor
test limits recorded in the input file.
If you make any changes to the Sensor Code in the Prospect parameters, you can apply those
changes to VPs already imported and visible in the VP Table view. To do that, select the
desired VPs and choose Update Sensors.
Note that this does not affect the Point Code, so the number of channels at each receiver
point, for example, is unchanged (editable only when importing the SEG-D file).
Create Tilt Model

Use this command to create a model of the response of correctly planted geophones so that
the system can correctly identify geophone strings with incorrectly planted geophones. See
Sensor Tilt Model creation (page 124).
Add a comment
After selecting one or more VPs, this command allows you to enter a comment into the VP
table. Note that the comment is not recorded in the processed SEG-D files.
Figure 3-17 Add comment dialogue
Get super-spread
After selecting several VPs, using this command will extract a “superspead” (a spread union)
from the selected VPs and display it in the Topo view. The “superspead” encompasses all the
spreads used for the selected VPs.
Display VPs in TraceView

Using this command will allow you to visualise traces in TraceView.
57 February 5, 2020
The Menu bar > Actions menu VP Table 3
Copy
Copy
Use this command to copy the selected rows from the table (for example, you may want to
paste them into the Position window).
Copy with Headers

Use this command to copy the selected rows and the column headers from the table.
Save as file
Save Selection
Use this command to export the selected rows from the table to a CSV or .xls file so that they
can be saved and used whenever they are needed.
Save All
• Same as above, saving the entire table to a .CSV or .xls file.
Figure 3-18
58
The Menu bar > Action menu Field Units
Action menu Field Units

The Actions menu is contextual. The commands specific to the WTU Table view are shown
and described below (also available from the right-click popup menu).
Figure 3-19 WTU table Actions menu
59 February 5, 2020
The Menu bar > Action menu Field Units 3
Markers
Assign Markers
This command allows you to change allocation of stake IDs, build lines and add / remove
WTUs.
12 3 4 5
Figure 3-20 Assign Markers
1. Inserts a WTU/gap above the current cursor position in the table.

2. Deletes the selected WTUs from the list.
3. Resets the selected markers to the default value.
4. Shows the auto-calculate dialogue box.
5. Moves the selected rows up/down.
See also Working with Stake IDs (page 130).
60
Swap Topo Locations

This command allows you to swap the Stake ID assignments of two specific WTUs.
Figure 3-21 Swap topo Locations
Reset Markers
Use this command when you want to revert to the previous markers after loading a different
set of markers.
Open PFT files

WTU serial numbers are mapped to line and station numbers via Marker files.
Using a PFT to scan the WTU serial numbers, the WTU IDs and stake numbers can be
gathered in advance, loaded into the system and stored until required. To open such a file,
select Open PFT files.
Figure 3-22
The Location dropdown list allows you to can choose between PFT files recently loaded
(New Lists) or archived files (Archive).
61 February 5, 2020
Import Markers
A .CSV file can be created in advance and loaded to the system ready for use when the line
is to be shot. The file with the Stake IDs can be loaded to the server to save time building a
line from a paper list of numbers, and reduces the risk of entering a wrong ID.
userdcm
Figure 3-23 Import markers
Export Markers
You can use this command to save the stake ID mappings (markers) for all rows to a .CSV
file.
Export Selected Markers

After selecting one or more rows in the table, you can use this command to save the stake ID
mappings (markers) for the selected rows to a .CSV file.
62
Sleep
Send to sleep (WTU)
Figure 3-24 Send to Sleep dialogue
If WTUs are not being used in the live spread for a length of time, they can be sent to sleep
to conserve battery power. In rough terrain, where WTU retrieval or access is difficult,
sending the WTUs to sleep when not in use but connected to the network can save power and
reduce the times someone has to go to the WTU to change a battery. Also if the WTUs are
to be left out on the line overnight, this will save a considerable amount of battery power.
At the end of the sleep cycle, the WTU performs a full reboot including pre-configured start-
up tests.
The WTUs to which this command should apply must be selected in the WTU Table view
before selecting the menu option.
Gateway Set / Unset

Set / Unset Gateway allows you to define a WTU as a gateway for State of Health (SoH) data.
Using pathfinder technology WTUs will send SoH data to one or several gateway WTUs. A
Gateway WTU must be connected via Ethernet cable or via a MAN to the central system.
63 February 5, 2020
Note SoH is the acronym for ‘State of Health’. SoH refers to QC flags broadcast on
the XT-Pathfinder radio network.
Any WTU can be designated as a Gateway provided it is connected to the central system.
Storage Mode
Set Storage Mode

The ‘Set Storage Mode’ function allows you to charge the WTU battery to a certain level in
order to preserve life expectancy of the unit during prolonged storage periods.
BITs (Built in Tests)

Generate scheduled BIT VPs
Select the WTUs for which you want to generate SEG-D test files, then select Generate
Scheduled BITs VPs. This brings up the following dialogue box.
Figure 3-25 Generate Scheduled BIT VPs dialogue
Clicking OK causes the system to look for scheduled Built-In-Tests in the Field Unit
Parameters (page 87), and generate VPs for all scheduled BITs that were performed
over the time span specified in this dialogue box, for the selected WTUs. This will allow test
SEG-D files to be generated after the test data is harvested. See Scheduled Tests
(page 93)for details.
Run BITs
See Tests on request - Built in Tests (page 97).
64
System
Format Field Units

Field units may be formatted provided they are connected to the central system. Formatting
a field unit will erase all data from the internal memory.
Figure 3-26
Reboot Field Units

This function will reboot the WTU.
Figure 3-27
Remove Field Units

Use this command when you want to delete Field Units from the Field Units Table view.
Note that this is a local preference (unknown to the server, therefore not shared by different
clients running on different machines).
65 February 5, 2020
Add to Parameters Group

After selecting a set of WTUs, selecting this command brings up the WTU Parameters setup
dialogue and automatically pastes the selected WTUs into a new group. See Method 2:
Add to parameters group (page 106).
Figure 3-28 WTU Parameters set
Copy
• Copy: use this command to copy the selected rows from the table (for example, you may
want to paste them into the Position window).
• Copy with Headers: use this command to copy the selected rows and the column headers
from the table.
66
Save as file
Save Selection
Use this command to export the selected rows from the table to a .CSV file so that they can
be saved and used whenever they are needed.
Save All
• Same as above, saving the entire table to a .CSV file.
Figure 3-29
67 February 5, 2020
The Menu bar > Window menu 3
Window menu
Figure 3-30 Window menu
New window
Opens a new DCM window.
Show view
• VP Table view (page 108): shows details of each shot taken.
• Field Units Table view (page 112): shows WTUs organized in a list.
• Gateway Table View (page 117): displays a list of WTUs that have been designated
as Gateways.
• DH Table view (page 117): shows information about Data Harvester(s) connected
to the DCM server.
• Completion view (page 119): graphical display of the harvesting status of deployed
WTUs for each VP (WTUs are shown along the vertical axis and successive VPs are
show along the horizontal axis).
• Topo view (page 121): graphical display of WTUs mapped to Line numbers (along
the vertical axis) and Point numbers (along the horizontal axis). It also shows WTU test
results and noise monitoring QC, filtered with a color code to easily define each channel’s
condition.
68
The Menu bar > Window menu
• Status mail view: each event occurring in the field will send a message to the DCM
server and this will be displayed in the Status Mails view:
Figure 3-31 Status Mail view
• Task view: shows processes currently running such as processing of VPs, running
commanded tests, etc.
Figure 3-32 Task view
• Health view: shows statistics on the used disk space and memory space, and processor
activity.
Figure 3-33 Health View
Load Layout
This function allows you to load a previously saved layout.
Save Layout
This function allows you to save the current layout of your view panels.
69 February 5, 2020
The Menu bar > Help menu 3
Reset Layout
This function restores the default layout of view panels.
Themes
This option allows you to select from a list of color schemes for the user interface.
Help menu
Report bug or enhancement

This function allows you to provide Sercel with product bugs or suggestions for improving
the software.
Figure 3-34
This function allows you to report an ‘Enhancement’ or a ‘Bug’ and complete the text box
with details concerning your comment. Enter a text description and click OK. A report will
be created.
70
The Menu bar > Help menu
Figure 3-35
Enter License key

This function allows you to visualise and/or modify the license key.
71 February 5, 2020
The Menu bar > Help menu 3
About DCM
This allows you to visualise the Software, License and Server versions of DCM.
Figure 3-36 About DCM Window
72
General Parameters > Limits
General Parameters
Limits
The Limits setup window allows you to set allowable values for results from sensor tests to
be displayed in QC views. If the test limits are altered, they can be returned to the default
settings by clicking on the Restore Defaults buttons. These parameters will not be
transmitted to the WTUs (unlike WTU parameters).
Figure 3-37 General Limits
73 February 5, 2020
Prospect Parameters > Processing Mode 3
Prospect Parameters
The Parameters window allows you to define the parameters of your operation. Select
Parameters... from the Edit menu.
• Processing Mode (page 74)
• Firmware Update (page 76)
• Process Types (page 77)
• SEG-D Output (page 80)
• Script Override (page 81)
• Sensors (page 83)
• Advanced - QC Only Mode (page 85)
Processing Mode
The Auto-Processing feature allows SEG-D files to be automatically produced depending on
the option you select in this window.
Figure 3-38 Processing Mode Parameters
74
Prospect Parameters > Processing Mode
• Off: SEG-D files are not generated automatically. VPs must be processed manually to
generate SEG-D files.
• Process when VP completes: SEG-D files are automatically produced for VPs which do
not have any outstanding channels. As soon as all the data is retrieved for a VP, the SEG-
D file is generated automatically. This will only apply to VPs imported after this option
is enabled, and each VP is auto-processed only once.
• Force process after duration (s): after the last sweep in a VP is done, the SEG-D file for
that VP is automatically produced at the end of the specified time period, regardless of
whether there are outstanding channels or not. This will only apply to VPs imported after
this option is enabled, and each VP is auto-processed only once.
WARNING
You may want your system to be almost fully automated but this may cause disk
space to run out unless you take care to delete old VPs from the database (the system
will not automatically remove them).
If you select either of the auto-processing options, you can choose two more options:
• Process Type:
- Normal: an exportable SEG-D file is generated.
- Preview: a simple preview file is generated, meaning that no SEG-D file is
generated in the “normal” export folder, and this does not take up any FFID
number (remember when a VP is processed to produce an SEG-D, it takes up an
FFID file number and if you process a given VP more than once, the resulting
output SEG-Ds have the same FFID number but the file name suffix is
incremented, e. g. _001, _002, etc.).
The preview file is created in the /var/dump/.DCM/preview
folder and the file name is 0.ffid (the Tape Set is always 0).
• Process output mode in the case of a VP with Stacking (with or without Correlation):
- Only Dump: only the stacked (correlated) data is auto-processed.
- Dump and Raw: Raw data files are auto-processed too.
75 February 5, 2020
Prospect Parameters > Firmware Update 3
Firmware Update
You can enable or disable automatic WTU firmware updating.
Figure 3-39 Firmware Update Parameters
• If firmware updating is disabled and new WTU firmware is available, use this setup
window to enable updating, otherwise WTUs may not be compatible anymore, therefore
not visible to the system.
• If firmware updating is enabled and new firmware is available when a WTU connects to
the DCM server network (via a wireless or wired connection), the WTU automatically
receives new firmware. The firmware is downloaded to the WTU's flash memory. The
WTU must not be turned off during this LED sequence:
RED > AMBER > GREEN cycling on both LEDs with each colour being shown for 1 s.
The WTU will reboot automatically.
76
Prospect Parameters > Process Types
Process Types
Figure 3-40 Process Types Parameters
In incoming SEG-D files, the description of the auxiliary traces to record and traces to use
for correlation —if the type of processing is one with correlation— does not include anything
about wireless auxiliary traces.
The Process Types setup window (Figure 3-40) allows you to create DCM Aux trace
descriptors specifying which Aux WTU channel the wireless seismic channels are correlated
with.
You may want to create different DCM Aux trace descriptors:
• depending on the type of Aux WTU (because early-production WTUs and later-
production WTUs do not have the same filter specifications),
• depending on the Process Type in the incoming SEG-D file (this will associate the
appropriate DCM Aux descriptor with each incoming SEG-D file).
The purpose of creating different DCM Process Types is to discriminate between incoming
SEG-D files. Three filtering criteria can be used:
• The type of processing (incoming Process Type), which may be Impulsive, Impulsive
Stack, Vibro Stack, Correl After, Correl Before.
77 February 5, 2020
Prospect Parameters > Process Types 3
• The serial number of each Pilot used in the incoming Process Type that the new DCM
Aux descriptor is intended to match: for example, assuming it must be applied to all
Correl Before incoming process types for which the serial numbers of FDUs used as
correlation pilots are 123 and 456, then enter 123,456 into the Pilot Serials field.
• The Stacking fold specified for the incoming process type (1 or 2, or 4 etc.).
In order to apply the correct Aux descriptor to each incoming SEG-D, the system first tries
to apply the most discriminating filter and, if this fails, then it tries to apply the second most
discriminating one, etc.
Example
To create a new DCM Process Type, use the + top left button. Your list of DCM Process Types
should look like the one below, depending on how many different process types may be
encountered in incoming SEG-D files, and on the difficulty to describe them.
DCM Process Type No. * means “any”
Figure 3-41
In Process Type No. 1, a wildcard “*” is used to specify that it will match “any” incoming
SEG-D, meaning that it will be applied to all incoming SEG-Ds, unless they match Process
Type No. 2 which is more discriminating by picking out all “Correl Before” types with FDU
serial number 12123456 or 12895623 as correlation pilots.
After each incoming process type is identified, the system has to determine which additional
Aux descriptor to apply in order to append wireless Aux traces into the SEG-D file.
Figure 3-42
• The Auxiliaries table allows you to describe each Aux channel with the Serial Number
of the WTU used on this channel and a Label. A dropdown list box prompts the list of
WTUs known to the system (from WTU table).
78
Prospect Parameters > Process Types
• The Descriptors table allows you to describe the auxiliary traces that will appear in the
SEG-D, arranged sequentially as per this table. You can apply two types of processing to
the WTU traces and record the positive or negative region:
- Auto-correlation (e. g. aux1*aux1)
- Cross-correlation (e. g. aux1*aux2)
• A dropdown list box prompts the list of Aux trace labels created in the “Auxiliaries”
table.
Note You can create Aux traces from FDUs, by simply specifying the Serial Numbers
of those FDUs in the “Auxiliaries” table. As a result, you can use any
combination of new Aux labels to describe additional auto-correlation or cross-
correlation traces.
• The Correlation Pilots table specifies which Aux trace to use for correlation with
seismic traces, depending on the type of box (WTU or FDU). A dropdown list box
prompts the list of identified box types (identified from their Subunit type code in the
SEG-D file). For example, you may want WTU seismic traces to be correlated with
Aux1, early-production WTU traces with Aux2, FDU traces with Aux3, etc.
Note that you can use the up and down arrow buttons to rearrange the rows in tables, + or –
to create or delete a row, and this button to copy/paste a row.
How to use VE464 digital pilots for correlation

In place of a Serial Number in the “Auxiliaries” table, you can enter the column number of
a VE464 digital pilot (from the VE464 Basic Type) in order to use that VE464 reference
signal as an Aux channel.
Column Number to be used in place of

a Serial Number in the
“Auxiliaries” table.
Figure 3-43 VE464 Basic Type setup window
79 February 5, 2020
Prospect Parameters > SEG-D Output 3
Then the Aux label created for the VE464 signal can be used just like any other Aux trace in
the “Descriptors” table and the “Correlation Pilots” table. This makes it possible for WTU
traces to be correlated with that VE464 reference signal. Also, this makes it possible to
record the raw VE464 signal or any trace resulting from cross-correlating it with another
trace.
Updating DCM Process Types in VPs

The DCM Process Type settings are automatically applied to each and every new SEG-D file
imported into the DCM server. No operator action is required.
If you make any changes to the Process Type setup, you may want apply those changes to
SEG-Ds already imported. To do that, after selecting one or more VPs in the VP Table, right-
click and select Update Process Types. This applies the description of auxiliary traces to the
selected VPs, depending on the specified filters: if any VP in the selected list matches the
DCM Process Type filter settings, then the Aux descriptor for that Process Type overrides
the former Aux descriptor for that VP. This brings up a confirmation window. No additional
setting is required. You are notified of successful updating in the Status Mail panel.
SEG-D Output
You can choose the SEG-D format revision (1.0, 2.1 or 3.0) for output files. The output file
SEG-D format does not need to be the same as that of input files.
Also you can set the initial FFID (to be later incremented) of output SEG-D files for built-in
tests.
Figure 3-44 SEG-D Output Parameters
Note Refer to 508XT Data Format Manual for detailed description of SEG-D Format
Revision 1.0, 2.1 and 3.0.
80
Prospect Parameters > Script Override
Script Override
The Script Override function makes it possible to replace the spread described in the input
SEG-D file from the 508XT by a spread described in SPS files imported into DCM.
Figure 3-45 Script Override Parameters
The Source Point details (Source Point Line, Source Point Number, Source Point Index)
contained in the input SEG-D file will determine which spread to extract from the imported
SPS files. The spread description contained in the input SEG-D will be entirely replaced by
that from the SPS file.
Naturally you have to import the whole set of SPS files (SPS-S, -R and -X). Use the Browse
button to open the folder containing the SPS files to import, and select any of the three of
them (the system assumes that the other two are present in the same folder, with the same
name).
The following naming conventions should be respected for the three files:
${FILE_NAME}.(s|r|x)${ANY}, meaning that the file name extension should always begin
with S or R or X (lower or upper case), followed by any character string.
Below are three examples of allowable file names:
• mysps.s, mysps.r, mysps.x
• mysps.sps, mysps.rps, mysps.xps
81 February 5, 2020
Prospect Parameters > Script Override 3
• mysps.saaa, mysps.rbbb, mysps.xccc.

After the three SPS files are loaded, a summary of the retrieved information is displayed
(number or shots, number of receivers and Stake ID of the first receiver).
Figure 3-46 Information from loaded SPS
The Script Override function may be very helpful as it relieves you of the need to describe
mute traces in the 508XT (mute traces otherwise required as place-holders to be later
populated by traces from WTUs in DCM).
This function may also be especially helpful if you want to correct any spread script errors
(all the more as DCM makes it possible to replay already finalized SEG-Ds whenever you
like) or change the spread (add or remove traces) in any original SEG-D file.
It is alright to use the Script Override function even if FDUs are mixed with WTUs in the
spread: if the spread script loaded into DCM contains the same FDU receiver points as
described in the 508XT, the spread portion that uses FDUs will be replicated in DCM, FDU
traces will be preserved and still part of the VP in DCM.
Naturally, if those FDU receiver points are not present in the script, the corresponding FDU
traces do not appear in DCM. However, the seismic data from those FDUs is not lost! If any
FDU traces are lost as a result of a script error in DCM, you only need to import again the
82
Prospect Parameters > Sensors
SEG-D file and load a correct script to recover the missing FDU traces (the seismic data from
imported FDUs is preserved in the DCM database).
Note that if FDU locations in the script loaded into DCM are different from those contained
in the input SEG-D, they are updated with those from the script loaded in DCM. Likewise,
if sensor test limits are different, the limits specified in DCM override those from the input
SEG-D.
See below (Sensors) to create matching Point Code numbers and Sensor Code numbers.
Sensors
The sensor parameter setup is especially helpful for two purposes:
• If the Script Override (page 81) function is enabled, use this setup to create a Point
Code table containing Point Code numbers matching those loaded from the SPS files (for
each receiver point, the Point Code defines the number of channels at this receiver point,
and sets the sensor test limits to apply to each channel).
• The Sensor Code table makes it possible to update the sensor test limit settings for the
traces contained in the SEG-D file imported from the 508XT. Typically, this is used to set
the test limits of WTU traces, but unless FDU traces have distinct Sensor Code numbers,
they too may be affected.
Point Code table, with Script Override enabled

The Script Override (page 81) function allows the spread script from SPS files loaded
into DCM to replace the spread description contained in the input SEG-D file. For this to
work, the SPS files should contain a Point Code for each receiver (in SPS-R), and you must
create matching Point Code numbers in the Point Code table (Figure 3-47), so that the
appropriate number of channels and sensor test limits can be applied to each receiver point
in the VP built from the input SEG-D and SPS loaded into DCM.
Figure 3-47 Point Code table
83 February 5, 2020
Prospect Parameters > Sensors 3
Naturally, if the SPS-R file you have loaded does not contain any Point Code, a default rule
is used: the Point Code number is assumed to be 0. This means that in that case, you must
create Point Code #0 in the Point Code table, otherwise the SPS file will be discarded (its
spread description will not be applied).
IMPORTANT
If the Point Code specified in the SPS file is not present in the Point Code table in
DCM, the Script Override function will not change anything (the input SEG-D will
keep its original spread and sensor test limits).
Note that only the ID number of the Point Code is used as an identifier in DCM. For example,
if a Point Code is identified as “p3” in the SPS-R file, then the system will search for Point
Code number “3” (not “p3”) in the Point Code table.
In the Point Code table, only the ID number of the Sensor Code is used to describe the Point
Code. For example, enter 1+2+3 rather than s1+s2+s3.
For example, assigning a Point Code defined as Sensor Code 1 (Figure 3-47) to a receiver
point will apply Sensor Code 1 to the first channel at this receiver point
Sensor Code table
Figure 3-48 Sensor Code table
If you do not enable the Script Override (page 81) function, you can still override the
sensor test limits for the traces contained in the input
SEG-D file.
For example, assuming point codes and sensor types are created in the 508XT to apply
Sensor type “s1” to some receiver points and “s2” to others, when an SEG-D file is imported
into DCM, the sensor test limits from the input SEG-D are replaced by those defined for
Sensor Codes “1” and “2” respectively in the above Sensor Code table (Figure 3-48).
It is important to note that you must drop the letter “s” used in the 508XT to identify a Sensor
Code: only the ID number from the “Id” column in the Sensor Code table is used.
84
Prospect Parameters > Advanced - QC Only Mode
This is especially helpful if mute traces are defined in the 508XT as placeholders for WTUs.
As the Trace Headers for mute traces are cleared in the input SEG-D, sensor test limits for
those traces are lost. The sensor codes created in the Sensor Code table allow you to update
the sensor test limits for the WTU traces.
Note For mute traces, the sensor type recorded in the Trace Header in the input SEG-D
from the 508XT is always “s1”. Therefore, to update the sensor test limits for
WTU (formerly mute) traces in the SEG-D, you must create Sensor Code “1”
with the appropriate limit settings in the Sensor Code table.
WARNING
FDU traces too are updated with the sensor code (especially test limits) from the
above Sensor Code table (Figure 3-48)
For example, assuming you create Sensor Code 1 with its associated limit settings
in DCM and the input SEG-D from the 508XT has FDUs that use sensor type s1,
then the test limit settings for those FDU traces will be replaced by those specified
in DCM!
Ideally, in order to prevent any unintended changes to FDU test limits, FDU traces
and WTU traces should have distinct Sensor Code numbers.
Important note: Exactly the same rules and logic apply as far as sensors and point codes are
concerned when the DCM input is made of revision 3.0 SEG-Ds imported from the 508XT.
The sensors and sensor limits can be redefined or used the same way as with the 508XT
inputs.
Advanced - QC Only Mode

The DCM system offers the option to only retrieve the QCs of infrastructure connected
WTUs.
When this mode is enabled for the prospect, the DCM system never requests seismic data
from the connected WTUs, but only their QCs.
Figure 3-49 Advanced Prospect Parameters - QC Only
85 February 5, 2020
Prospect Parameters > SoH Radio 3
One advantage of this mode is to prevent the infrastructure network (e.g. single MAN’s
access point or multiple MAN in a Mesh network) to be overloaded with too much data
traffic and to maintain the stability of the network as much as possible to retrieve the QCs
from WTUs at different locations in the spread.
This could be especially useful when used in conjunction with the WTU noise monitoring
feature as WTUs connected to the central system through such a network would report their
noise monitoring RMS QCs at regular intervals (normally every 5s – though it is subject to
the network latency) and thus this would help allowing the noise monitoring of some
sections of the spread in near-real time (refer to section Noise Monitoring in
Infrastructure Mode (page 123) for more details about the WTU noise monitoring
function).
SoH Radio
This parameter allows you to specify which regulatory domain the radio will operate in:
• CE radio domain - regulates radio communication in the European union
• FCC radio domain - regulates radio communication in the United States
Figure 3-50 SoH Radio parameters
86
Field Unit Parameters > Overview of programmable WTU parameters
Field Unit Parameters

In this section:
• Overview of programmable WTU parameters (page 87)
• Tilt Model (page 90)
• Acquisition Parameters (page 90)
• Limits (page 92)
• Scheduled Tests (page 93)
• Working hours (page 98)
• Wifi Settings (page 100)
• Pathfinder Settings (page 101)
• GNSS (page 103)
• Creating WTU parameter groups (page 103)
• Loading parameters to WTUs (page 107)
Overview of programmable WTU parameters

IMPORTANT
Before field deployment ensure the parameters of each WTU are synchronised with
the parameters defined in the DCM interface. This can be done via a MAN
(recommended) or by connecting each WTU directly to the DCM server.
The WTU parameters window allows you to set the parameters to be transmitted to the
WTUs.
Select Parameters from the Edit menu.
Table 3-1 provides a complete list of all the programmable WTU parameters along with
a list of where these are set in the DCM window.
Before deployment all these parameters should be correctly set in DCM and then all WTUs
connected to the DCM server network or a PC hosting standalone DCM software. The WTU
will store these parameters in Flash memory.
These parameters are automatically sent by the server so any WTU that reads “Connected”
for over 10 seconds will have been updated with the parameters.
Table 3-1 WTU Parameters Overview
Parameter location in DCM Parameters window Description

Field Unit > Tilt Model > Model Date page 90
87 February 5, 2020
Field Unit Parameters > 3
Table 3-1 WTU Parameters Overview (Continued)

Groups > Default > Acquisition > Sample Period
Groups > Default > Acquisition > Preamp Gain
page 90
Groups > Default > Acquisition > Filter Type
Groups > Default > Acquisition > Lowcut Value
Groups > Default > Limits > Sensor Resistance > Minimum
Groups > Default > Limits > Sensor Resistance > Maximum
Groups > Default > Limits > Geophone Sensor Tilt > Maximum
Groups > Default > Limits > Noise Alarm > Analog page 92
Groups > Default > Limits > SoH Thresholds > Internal Battery’s
Remaining Charge Threshold
Groups > Default > Limits > SoH Thresholds > External Battery’s Voltage
Threshold
Groups > Default > Scheduled Tests > Tests to run
page 93
Groups > Default > Scheduled Tests > Time to run tests
Groups > Default > Working Hours > Enable Working Hours
Groups > Default > Working Hours > Wake Time
Groups > Default > Working Hours > Sleep Time page 98
Groups > Default > Working Hours > Enable Start Date
Groups > Default > Working Hours > Start Date
Groups > Default > Wifi Settings > Encryption Mode
Groups > Default > Wifi Settings > Encryption Key
page 100
Groups > Default > Wifi Settings > Custom SSID
Groups > Default > Wifi Settings > Channels
Groups > Default > Pathfinder > Pathfinder ON / OFF
Groups > Default > Pathfinder > SoH Refresh Period
page 101
Groups > Default > Pathfinder > Wireless Channel
Groups > Default > Pathfinder > Crew ID
88
Field Unit Parameters >
Table 3-1 WTU Parameters Overview (Continued)

Groups > Default > GNSS > GNSS Type
page 103
Groups > Default > GNSS > GPS mode
Note Any parameter NOT listed here can be changed at any time without having to
reprogram the WTU.
89 February 5, 2020
Field Unit Parameters > Tilt Model 3
Tilt Model
Figure 3-51 WTU parameters — Tilt Model setup
This setup brings up the dialogue for loading the sensor pulse response model used to
perform the Sensor Tilt Test.
For information on creating the model and determining the correct Maximum tilt deviation
limit, see Sensor Tilt Model creation (page 124).
Acquisition Parameters
Figure 3-52 WTU parameters — Acquisition Parameters setup
This is where the basic recording parameters are configured.

The Acquisition Parameters are set depending on which configuration is needed. You must
set:
90
Field Unit Parameters > Acquisition Parameters
• the Sample Period (0.5, 1, 2, 4 ms);

• the Preamp Gain (0 or 12 dB);
• the Filter Type (type of high-cut filter for WTU channels).
- Linear phase: This type of filter is ideal as far as phase considerations are
concerned, as all the frequencies are delayed by the same amount. That delay is
set to zero in the system. In return, this kind of filter has a pulse response with
leading ringing (“precursors”) as well as lagging ringing (actually, the pulse
response is symmetrical with respect to time 0).
- Minimum phase: The minimum phase type is causal, i.e. its pulse response, much
like analog filters, starts at time 0, peaks and then rings (no ringing prior to the
peak).The delay, however, somewhat depends on the input frequency.
WARNING
Extreme care should be taken when setting the Acquisition parameters to ensure they are set
at the correct values for each prospect.
Note that the acquisition parameters can only be configured in a WTU when it is
connected to the DCM server, therefore it is essential that all WTUs are configured
before being deployed in the field.
• the Lowcut Value of the Lowcut filter (None (no lowcut filter applied), 0.15625
(recommended), 0.3125, 0.625, 1.25, 2.50 Hz): a filter that transmits frequency above the
selected Lowcut value.
91 February 5, 2020
Field Unit Parameters > Limits 3
Limits
Figure 3-53 WTU parameters — Limits setup
This window allows the operator to:

• Enable/disable, and set limits for sensor tests:
• Sensor resistance
• Geophone sensor tilt
By default, the same settings are used as those defined in General Limits for all sensors. If,
however, you would like to copy only certain settings, you can click on Copy from General
parameters to use the same settings as selected in Noise Monitoring in Infrastructure
Mode (page 123) for QC views in DCM.
Note that WTUs will measure any field resistance above 4kΩ at 0dB gain, and 1kΩ at 12dB
gain as “open-circuit”.
If the test limits are altered, they can be returned to the default settings by clicking on the
Restore Defaults button.
92
Field Unit Parameters > Scheduled Tests
• Set the threshold for the ambient noise alarm.

The value set here is the Noise Threshold value used by the WTU ambient noise
monitoring algorithm. If a high level of ambient noise is detected, a noise alert will be
transmitted by the WTU on the Pathfinder network.
• Set thresholds for SoH alarms to be reported via the Pathfinder network
• Internal battery remaining charge
The WTU monitors the charge remaining in the internal battery,
and when it drops below the threshold value set here, an alarm is
transmitted over the Pathfinder network. This alarm condition will
be cleared if the battery is charged.
• External battery voltage
The WTU monitors the voltage input by an external battery as an
indicator of the state of charge of the battery. When the voltage
measured drops below the threshold values set here, an alarm is
transmitted over the Pathfinder network. This alarm condition will
be cleared if the battery is changed for one with a higher voltage.
Scheduled Tests
The Scheduled Tests setup allows the operator to select Built-In Tests — Instrument and/or
Sensor tests — that are to be run at scheduled times.
Select Parameters from the Edit menu, open a Group folder (e. g. the Default group) and
click on the Scheduled Tests tab.
93 February 5, 2020
Figure 3-54 WTU parameters — Scheduled Tests setup
This dialogue allows the operator to select tests — Instrument and/or Sensor tests — that are
to be run at scheduled times. The tick boxes in the Tests to Run area select which tests are
to be run.
In the Times to Run Tests area, appropriate times must be entered to determine when the
WTUs will run the tests (periods of time for which no shot is due to be launched).
Note The scheduled times values must be passed from the DCM server to the WTUs,
therefore the test scheduled must be determined and entered before the WTUs
are connected to the DCM server network for configuration.
Note The times used must be within the WTUs Working Hours. Any tests scheduled
outside of Working Hours will not be run. See Working hours (page 98).
IMPORTANT
It is important to be sure no source is launched while the WTUs are performing one
or more tests.
Click Apply and OK.
94
Two minutes before scheduled BITs are due to start the DCM window will display the
Scheduled BITs alert dialogue.
Figure 3-55
No acquisitions should be initiated while this dialogue is visible. The dialogue will
automatically close when it is safe to restart production.
Note that for the alert dialogue to display at the correct time, the server PC time, time zone
and daylight savings settings must be correct.
To generate SEG-D test files:
1. In the WTU Table view, select the WTUs for which you want to generate SEG-D test
files.
2. Select Generate Scheduled BIT VPs from the right-click (Actions) menu to
generate VP entries for the selected WTUs.
3. In the dialogue box that shows up, set the desired time span for the scheduled BIT
tests. This creates a VP row, in the “VP Table” view, for each scheduled BIT test
performed over the time span you specified (this will allow the raw data from the
scheduled BIT tests to be harvested and recorded to SEG-D files).
95 February 5, 2020
Outsanding
BIT VPs
Figure 3-56 Waiting for test results
Until the scheduled tests are performed and the raw data harvested, the outstanding BIT VPs
show in orange in the Completion view.
WTU test results are colour-coded in the Completion view (page 119) to easily define
each channel’s condition.
Test results also show in the Completion view (page 119) where they can be displayed
and saved in a variety of ways.
96
Tests on request - Built in Tests

In addition to any scheduled tests, you can launch tests at any moment on WTUs connected
to the central unit (in infrastructure mode), by selecting one or more of those WTUs in the
WTU table view, and selecting Run BITs from the right-click popup menu. This brings up
the following window allowing you to choose the tests to run and whether you want to
generate VPs for the selected tests.
Figure 3-57
The WTU almost immediately goes to the BIT mode, stops acquisitions and performs the
requested tests. A task is created in the Tasks view, with a bar showing the progress of the
tests. No acquisitions should be initiated until the tests are complete.
The test results (QCs) are updated in the WTU table.
For each WTU to test, the system uses the parameter settings from the Parameter Group the
WTU belongs to.
If you choose “Generate VPs”, one SEG-D file is created for each test selected, containing
the results from all selected WTUs attached to the same Parameter Group. Also, if not all of
the selected WTUs use the same Parameter Group, then one SEG-D is created for each
Parameter Group. There will be as many SEG-Ds as there are Parameter Groups involved for
each type of test.
Only WTUs that have been assigned to a receiver position can be present in test SEG-Ds.
97 February 5, 2020
Field Unit Parameters > Working hours 3
Working hours
Figure 3-58 WTU parameters — Working Hours setup
The Working Hours setup allows the operator to select the days and hours during which
WTUs operating in Autonomous mode will acquire data. Outside of these working hours, the
WTUs will enter sleep mode to conserve battery and will not acquire data. When asleep, they
cannot be awakened except by power-cycling. Note that the working hours can only be
configured in an WTU when it is connected to the DCM server, therefore it is essential that
all WTUs are configured with working hours before being deployed in the field.
In Infrastructure Mode the WTUs will remain “alive” and ignore any work hour settings as
long as they remain connected to the DCM server network or a Data Harvester. Once
disconnected, the WTU will allow a grace period of approximately 4 minutes to allow
reconnection to the DCM server or Data Harvester, after which it will apply any working
hours rules. This allows the Observer or harvesting personnel to extend the working day if
necessary.
To set up the working hours, you define a typical week by ticking the days that you want the
Wake Up time and Sleep time to apply to. On the days that you leave unticked, the WTU will
be Off.
98
Field Unit Parameters > Working hours
However, remember that you primarily set up a Wake Up time. For example, assuming the
Wake Up time is 20:00 and the Sleep Time is 08:00 from Monday to Saturday, the WTU
being Off on a Sunday, this means the WTU will wake up at 20:00 in the evening on a
Saturday and will not go to sleep until 08:00 in the morning on Sunday, then remain OFF
until the Monday evening, only waking up at 20:00.
Also, extra care is required if the D(aylight) S(aving) T(ime) is going to change during the
course of the survey. For example, assuming the Wake Up time is set to 08:00, France local
summer time, that is 06:00 UTC, when the time switches to the winter period the local time
08:00 becomes 07:00 UTC whereas the WTU is still set to wake up at
06:00 UTC. To avoid the need to update the WTU parameters, you may have to consider
setting a longer daily working period from the outset.
Setting work hours takes immediate effect once the WTU has attained GPS Lock. Setting a
start date will send the WTU to sleep until that date. The WTU will awake at the time
specified within the work hours setting. After the start date the WTUs will be powered on
and acquire during the work hours set.
If the WTUs are required to operate in 24 Hours continuous operation from a specified start
date, Enable the Start Date, and ensure Working Hours are Deselected.
The initial start date allows the deployment of the WTUs in the field to take place without
the WTU being powered up and consuming battery power. This is useful at the initial layout
on a prospect.
Note The WTUs working hours time is set in UTC, so in order for the conversion to be
correct, you must ensure that the local Time Zone is set correctly on the server
computer (and also on client computers if any).
The DCM application must be shut down before you make any changes to the system time
or time zone.
99 February 5, 2020
Field Unit Parameters > Wifi Settings 3
Wifi Settings
WTUs use the Wifi network to communicate with MAN Antennas, or with a Data Harvester.
This section allows you to modify the Wifi settings for WTU groups.
Encryption
Select the type of:
Encryption Mode used to secure your WTU network.
• None
• WEP64
• WPA2
Enter an Encryption Key, a random string used to protect your data.
Custom SSID
WTUs have an optional programmable SSID.
• The programmable SSID is used in addition to the default SSID, it never replaces it.
• If the programmable SSID is set, the WTU uses it in addition to the default SSID for
normal WLAN connections.If the programmable SSID is set in anti-theft mode, the WTU
will prefix it with "LJ" for the anti-theft (also known as lojack) WLAN scan and use it
with the default. So anti-theft awake WTUs will accept access points with the default
"VibtechLJBSS" and "LJ<programmableSSID>".
This allows insulating possible adjacent crews but may also be used to create independent
radio networks being accessed by dedicated access points to optimize radio performances,
100
Field Unit Parameters > Pathfinder Settings
without preventing rental firms from being able to wirelessly connect to WTUs once returned
by customers (default known SSID always available).
WARNING
Obviously if a custom SSID is used, all access points used to talk to WTUs must be
updated to broadcast the same custom SSID.
See sections Setting the Tablet PC access point's SSID, in 508XT Installation
Manual, Chapter 9. to know how to program DCM’s usual access points SSIDs.
Channel
This option allows you to specify the channel set via which the WTU group will be
communicating with the Access Point on the 2.4GHz band.
Pathfinder Settings
The XT-Pathfinder network is the wireless 2.4GHz frequency used by WTUs to
communicate with each other.
WARNING
When using other radio equipment such as a Wifi Acess Point, Sercel strongly
recommends to use a different channel than the Pathfinder Wireless channel.
This section allows you to specify the specific settings concerning the Pathfinder network.
101 February 5, 2020

Field Unit Parameters > Pathfinder Settings 3
Figure 3-59 Pathfinder settings tab
Pathfinder On / Off
This parameter allows you to turn the Pathfinder Radio On / Off. When the Pathfinder radio
is Off the power consumption will be reduced.
SoH Refresh Period

This option allows you to define the amount of time between SoH (state of health) updates
for the WTU’s. See also, Continuous Monitoring (page 41).
You may choose between intervals of:
• 15 min.
• 30 min.
• 45 min.
• 60 min.
Note Note that a shorter refresh period means that there is an increased power
consumption on the WTUs.
102
Field Unit Parameters > GNSS
Pathfinder Wireless Channel

The Pathfinder Wireless Channel indicates the channel via which the Pathfinder network
communicates.
Pathfinder Crew ID
The Pathfinder Crew ID is used to limit the interferences and connections between Sercel
equipment using the Pathfinder network. In order to prevent two groups of WTUs from
communicating with each other, select different configurations for each group.
GNSS
The GNSS tab indicates the GPS parameters.
GPS Mode
GPS mode means that a WTU can change the way it uses GPS, in order
to reduce power consumption.
• Stationary: the WTU remains stationary and its GPS module is always active (mainly
intended to be used when GPS coverage is poor).
• Low power: the WTU remains stationary and its GPS module is set to duty cycle to
reduce the power consumption of the WTU.
• Mobile: the WTU is moved around while recording (for example if it is used as an
auxiliary channel in a vibrator).
GNSS Type
This option allows you to select the Global Navigation Satellite System used to program the
timing of the WTUs. The following options are available.
• GPS Only
• GLONASS Only
• GPS and GLONASS
Creating WTU parameter groups

There is a default WTU parameter Group which can neither be deleted nor renamed.
You may want to create more “WTU parameter groups” if not all of the WTUs have the same
settings for all parameters (for example some WTUs may need to have different Scheduled
tests). Note that all, however, will have the same Tilt Model.
Right-clicking on a group (other than the Default group) allows you to rename or delete it.

Field Unit Parameters > Creating WTU parameter groups 3
There are two ways to create a new group: either select an existing group and choose
Duplicate from the right-click menu, or (quicker) select a set of WTUs in the WTU table
view and use the New parameter group command.
Method 1: Duplicate
1. Select any group in the list (for example the Default group if you are creating the 1st
new one).
2. Right-click on it and choose Duplicate... This brings up a popup window allowing
you to type a name for the new group (any alphanumeric character is allowed).
Figure 3-60
3. Click OK. The new group appears in the list of groups. If you click on it, the
parameter window has one more tab (WTUs) than with the Default group.
4. At this stage, the list of WTUs in the WTUs tab is empty. Clicking on the + button in
the upper left corner brings up a popup window that prompts the list of mapped
WTUs so that you can select those you want to be part of the group you are creating.
Click OK.
Note that those WTUs which are not part of any custom group show in the Default
group.
104
Field Unit Parameters > Creating WTU parameter groups
Figure 3-61
5. Set the specific parameters in the other tabs for the group. A star (*) in the left-hand
pane means that the parameter settings are different from the default group.
Star denoting
Figure 3-62

Field Unit Parameters > Creating WTU parameter groups 3
Method 2: Add to parameters group

There is a quicker way to create the list of WTUs:
1. Select the desired WTUs in the WTU Table view, then choose Add to parameters
group from the Actions menu (or the right-click popup menu). This brings up a
popup window allowing you to type a name for the new group or to select a nn
existing group.
Figure 3-63
2. Click OK. This automatically pastes the selected WTUs into the new group and
selects the WTUs tab in the parameter window. All parameters in the other tabs have
default settings. Select each tab and change settings as required.
Note that each WTU can be part of only one group, so if any WTU in your selection is
already part of another group, it is highlighted (red) in the WTUs tab. This does not prevent
you from creating the new group (by clicking OK or Apply) but the group will not include
the conflicting WTUs.
106
Field Unit Parameters > Loading parameters to WTUs
Loading parameters to WTUs

Before the WTUs are deployed in the field, it is essential that they are connected to a
computer running the DCM software to ensure that they are configured with the correct
recording parameters (especially the Sample interval, Pre-amplifier gain, Working hours)
and testing options for the survey.
This also ensures that the WTUs are programmed with the latest firmware version available.
Extreme care should be taken when setting the Acquisition parameters to ensure they are set
at the correct values for each prospect.
1. In the DCM window, select Parameters from the Edit menu to set the acquisition
parameters.
2. Click Apply.
3. Connect the WTUs to the DCM server (via a MAN, a Wifi access point or via
Ethernet connection) in order to synchronize the DCM parameters with WTU’s.
DCM software can also be installed as a standalone server computer at a staging
area. If both are used it is essential that they are set up with the same acquisition
parameters.
Figure 3-64 DCM server loading parameters to WTU

View Panels > VP Table view 3
View Panels
In this section:
• VP Table view (page 108)
• Field Units Table view (page 112)
• DH Table view (page 117)
• Completion view (page 119)
• Topo view (page 121)
VP Table view
This VPs view panel shows details of each shot taken (impulsive acquisition, vibroseis
acquisition, instrument and sensor tests).
Figure 3-65 VP Table View
108
View Panels > VP Table view
VP Attributes
• VP ID: identification number for the VP
• VP Type: type of VP (impulsive, vibroseis, test)
• Shot Number: shot number
• Parameters Status: indicate if VP’ parameters are up-to-date with current WTU
acquisition parameters
• Timebreak: the local time when the VP was created (fired)
• Numerical TB: the GPS time when the VP was created (fired)
• FFID: file id number
• Sweeps Received: VP progress state (percentage of acquisitions received for this VP)
• Processed count: indicates how many times the VP has been processed (using the
Process VPs command in DCM)
• Outstanding WTUs (field units): indicates how many WTUs are still outstanding for
this VP
• Failed WTUs (field units): indicates how many WTUs have failed this VP
• Muted Channels: indicates how many mute channels are associated with this VP
• Source Point Line: Source Point Line number
• Source Point Number: Source Point number
• Source Point Index: Source Point Index
• Comment: textual comment associated with this VP
• Sample period: sample rate used the channels recorded for this VP
• Pre-amp Gain: gain used for the channels recorded for this VP
• Filter Type: type of filter used for the channels recorded for this VP
• Swath ID: Swath identifier for this VP
VP Table Actions
The right-click popup menu available from any row in this table (same as the Actions menu)
allows you to:
• Process VPs (page 55)
• Preview VPs (page 56)
• Delete VPs (page 56)
• Update markers in VPs (page 56)
• Update Process Types (page 56)
• Update Sensor Codes (page 57)

View Panels > VP Table view 3
• Add a comment (page 57)

• Create Tilt Model (page 57)
• Get super-spread (page 57)
• Display VPs in TraceView (page 57)
• Copy (page 58)
• Save as file (page 58)
Figure 3-66 VP table context menu
110
View Panels > VP Table view
Customize VP Table
Display of VP table view is customizable by right-clicking with the mouse on the table
header and selecting the desired item.
Columns
Choose which VP attributes you want to display.
Presets and Filter

Use Presets to save customized columns configuration. Use Filter function to show/hide
columns in the table.
See Actions menu VP Table on page 55

View Panels > Field Units Table view 3
Field Units Table view

This view panel shows the WTUs (field units) organised in a list. The WTU Table view gives
all the details an operator needs for each WTU that has connected to the server.
Figure 3-67 WTU table view
Field Units Attributes

• ID: the serial number of the WTU
• State: the current state of the WTU (Ethernet connection)
• Auxiliary: True/False, see Process Types (page 77) to define a WTU as an
auxiliary channel
• GateWay: True/False, indicates if the selected WTU has been designated as a Gateway.
• SoH Sensor: Red/Green. Indicates if Sensor resistance is outside test limits. Red (Fail)
Green (Pass)
• SoH Field Unit: Red/Green. Indicates if Sensor built-in-test statuses are OK. Red (Fail)
Green (Pass).
• SoH Time Synchro: Red/Green. Indicates if the GPS lock and radio sync statuses are
OK. Red (Fail) Green (Pass).
• SoH Memory: Red/Green. Indicates if memory is full. Red (Full) Green (OK).
• SoH Battery: Red/Green. Indicates if the internal and external batteries are OK. Red
(Fail) Green (Pass).
• SoH Noise Alarm: Red/Green. Indicates if the noise level is above the programmed
threshold.
112
View Panels > Field Units Table view
• SoH Age: The time elapsed since the last SoH data update from the field unit.
• Topo-Location Line: Stake ID marker line defined for the WTU
• Topo-Location Point: Stake ID marker station defined for the WTU
• QC Age: the time elapsed since the last QC data was updated from the selected field unit.
• Battery: battery status (Internal or External)
• Int Batt Volts: the WTU’s internal battery voltage reading (V)
• Ext Batt Volts: the WTU’s external battery voltage reading (V)
• Int Batt %: the WTU’s internal battery capacity in percentage of full capacity.
• Batt Charge: the WTU’s internal battery charge status (mA)
• RSSI: Radio Signal Strength Indicator (dBm) if the WTU is connected to the Central
Unit through WiFi
• Parameters status: indicates if the WTU’s parameters are up-to-date with the current
prospect parameters.
• Parameters group: group of parameters the WTU belongs to, see Creating WTU
parameter groups (page 103)
• Field Unit Type: type of field unit.
• GPS Quality: GPS signal quality
• GPS Status: GPS status. Locked / Unlocked
• Outstanding VPs: indicates how many outstanding VPs are associated with the WTU
• Oldest Outstanding VPs: indicates the date of the oldest outstanding VPs associated with
the WTU
• Noise Monitoring Ch. 1: the noise RMS value in mV computed over the last second (1s)
of acquisition (refer to section Noise Monitoring in Infrastructure Mode
(page 123) for more details about this QC value).
• GPS module: the type of GPS module in the WTU
• Position: GPS position of the WTU
• QC Age: the time elapsed since the QC data from the WTU was last updated
• QC Time: the time when a QC data update was last received from the WTU
• Instr Noise Ch. 1: Instrument noise (nV) on channel 1
• Instr Distortion Ch. 1: Instrument distortion (dB) on channel 1.
• Instr Gain Ch. 1: Instrument Measured Gain/Theoretical Gain ratio (%) on channel 1
• Instr Phase Ch. 1: Instrument Phase error (ms) on channel 1
• Sensor Noise Ch. 1: sensor noise (µV or µm/s²) on channel 1
• Sensor Resistance Ch. 1: sensor resistance (Ω) on channel 1

• Sensor Tilt Ch. 1: sensor tilt (% or degrees) on channel 1.

• GPs Lock Time: time of first GPS lock (seconds)
• Firmware Version: WTU firmware version
• Sensor Firmware Version: firmware version of the WTU sensor
• GPS Firmware Version: firmware version of the WTU GPS
• QS1 Firmware Version: firmware version of the field unit QS1.
• MAN: the serial number of the MAN to which the particular WTU is connected.
114
View Panels > Field Units Table view
WTU Table Actions

The right-click popup menu available from any row in this table (same as the Actions menu)
allows you to:
• Assign Markers (page 60)
• Swap Topo Locations (page 61)
• Reset Markers (page 61)
• Open PFT files (page 61)
• Import Markers (page 62)
• Export Markers (page 62)
• Export Selected Markers (page 62)
• Send to sleep (WTU) (page 63)
• Gateway Set / Unset (page 63)
• Generate scheduled BIT VPs (page 64)
• Run BITs (page 64)
• Format Field Units (page 65)
• Reboot Field Units (page 65)
• Remove Field Units (page 65)
• Add to Parameters Group (page 66)
Customize WTU table

Display of the WTU table view is customizable by right-clicking with the mouse on the table
Presets and Filter

Use Presets to save customized columns configuration. Use Filter function to show/hide
columns in the table.
See Customizing tables (page 31).

Columns
Choose which WTU attributes you want to display
Figure 3-68 Columns List
116
View Panels > Gateway Table View
Gateway Table View
Figure 3-69 Gateway table
This view shows the WTUs (field units) that have been designated as Gateways organised in
a list.
The WTU Table view gives all the details an operator needs for each WTU that has connected
to the server.
DH Table view
This view panel gives the operator all the information needed for a Data Harvester that have
been connected to the DCM server.
Figure 3-70 Data Harvester Table view
• DH ID: the serial number of the Data Harvester.

• Network: network connected/disconnected indicator
• Last Connect: the time when the Data Harvester was last connected, to be notified of
outstanding TBs.
• State: status of the Data Harvester connection.
• Progress: progress through the current connection state (0-100).
• Timebreak: the GPS timestamp until which the Data Harvester has been requested to
harvest outstanding TBs.
• Data: Total amount of data (KB) uploaded from the DH to the DCM server during the last
connection.
• Data time: Time of last data upload.
• Field Units: total number of WTUs for which the Data Harvester had got data when it
last connected.

View Panels > DH Table view 3
Customize DH Table
Display of DH table view is customizable by right-clicking with the mouse on the table
Columns
Choose which VP attributes you want to display.
Figure 3-71
Presets and Filter

Use Presets to save customized columns configuration.
Use Filter function to show/hide columns in the table.
See Chapter 2 Getting Started > Customizing tables (page 31)
118
View Panels > Completion view
Completion view
For each shot, the Completion view shows the harvesting status of each WTU graphically,
with different colours depending on whether the trace data is outstanding or has been
harvested from the WTU.
Sum VPs, Sum WTUs
Show/Hide outstanding/field traces
Zoom
Control
Figure 3-72 Completion view

View Panels > Completion view 3
Colour code
The Edit > Preferences menu (see Preferences (page 49)) allows you to select your
preferred colour code to show:
• Outstanding traces
• Traces harvested, with no errors
• Traces harvested, but with errors (dead traces)
• Traces out of live spread
Zoom controls
You can use + and – zoom icons to zoom in/out.
Sum VPs and Sum WTUs (collapse/expand) controls

In the “Completion” view, cells can be collapsed for better legibility (showing more VPs and
WTUs, but fewer details) or expanded.
• By default, both the vertical (Sum the VPs) and the horizontal (Sum the WTUs)
collapsing controls are enabled. You will see more VPs and WTUs (but fewer details).
- This means that if there are too many details to display, one cell will stand for the
data from several rows (e. g. 4 VPs with the same information to display) and
several columns (e. g. 4 WTUs with the same information to display).
- If only failed traces are viewed ( ) and a single one of the WTUs (traces) in
any of the VPs which are collapsed into one cell is faulty (Failed), the cell shows
faulty.
• If you only enable “Sum the VPs”, one cell may stand for several rows, for example 4
VPs, but these 4 VPs (one row) will have one distinct cell for each WTU.
• Conversely, if you only enable “Sum the WTUs”, one cell may stand for several columns,
for example 4 WTUs, but these 4 WTUs (one column) will have one distinct cell for each
VP.
• If neither “Sum the VPs” nor “Sum the WTUs” is enabled, no cell is collapsed on either
axis. You will see fewer VPs and fewer WTUs (but greater detail).
120
View Panels > Topo view
Topo view
This graphical view shows WTUs mapped to Line numbers (along the vertical axis) and
Point numbers (along the horizontal axis). It also shows WTU test results and noise
monitoring QC, filtered with a colour code to easily define each channel’s condition.
Figure 3-73 Topo view
Zoom controls
You can use + and – zoom icons to zoom in/out.
QC Attribute
This drop-down menu allows to choose which QC data from field equipment you want to
display in the Topo view.
• BIT Results: a filter option lets you choose the test type to view (Sensor Resistance,
Sensor Tilt, etc.).
• Internal battery charge: (remaining capacity in mAh)
• Internal battery: voltage measured for the internal battery (V)
• Internal battery: voltage measured for the external battery (V)
• Oldest outstanding VP: (remaining capacity in mAh)
• QC Age: the time elapsed since the QC data from the WTU was last updated)
• RSSI: radio signal strength indicator (dBm) for WTUs connected to the central unit
• Noise monitoring: latest noise QC RMS value (mV) received for the WTU, see Noise
Monitoring in Infrastructure Mode (page 123).
For some QC attribute, Critical and Warning threshold can be user-defined.
The Edit > Preferences menu lets you select your preferred color for WTUs that override
the “Critical” alert threshold, and those which override the “Warning” threshold. For those
WTUs below both alert thresholds, the “Normal” color option is used.

View Panels > Topo view 3
Figure 3-74 Internal or External Battery voltage alert levels
Figure 3-75 Internal Battery Charge alert levels
Figure 3-76 Noise Monitoring Alert Level
field units
Figure 3-77 RSSI alert levels
122
Noise Monitoring in Infrastructure Mode > Topo view
Noise Monitoring in Infrastructure Mode

WTUs connected in infrastructure mode to the central unit i.e. connected via a MAN or via
an infrastructure network of MANs report their noise monitoring RMS value in Volt every
5s.
The RMS value is computed over the last second (1s) of acquisition at the moment the WTU
receives the get QC message from the central system (so every 5s as 5s is the update
frequency of the QCs for connected WTUs).
The RMS value is computed from the samples LSB values recorded by the WTU - offset
removed - and converted into Volt using the gain factor.
The noise monitoring RMS value in the central unit is not persisted i.e. as soon as a WTU
disconnects, its RMS value is blanked as it is essentially useful as a “real-time” QC.
The user can specify a noise monitoring threshold in the topo view by selecting the Noise
Monitoring QC and setting a critical value in mV.
When the noise monitoring RMS value returned by the WTU reaches or exceeds the
threshold, the cell representing the WTU in the topo view turns red and at the same time, the
Noise Monitoring Ch. 1 cell’s background for this WTU in the WTU table turns red as well.
Figure 3-78 Noise Monitoring Critical Threshold in topo view
Figure 3-79 Noise Monitoring RMS value for channel in WTU Table
The noise monitoring RMS value in Volt is computed and reported by the WTU for its first
channel only.

Sensor Tilt Model creation > Overview 3
Sensor Tilt Model creation

In this section:
• Overview (page 124)
• Preparation (page 124)
• Acquire and save the model sensor response (page 125)
• Load the sensor response model (page 128)
• Optimising the Sensor Tilt threshold limits (page 128)
Overview
In order for the DCM system to be able to correctly identify geophone strings and WTUs
with incorrectly planted sensors — using the Sensor Tilt test — a model of the response of
correctly planted sensors, in the configuration to be used in the survey, must first of all be
created.
This section describes how to create the sensor response model and how to apply it.
Preparation
Prior to building a Sensor Tilt Model it is important that the sensor Parameters are set
correctly (see General Parameters (page 73)). The Sensor Resistance parameter must
be set to match the sensor configuration used before attempting to create the model as this
will fail if the measured parameter is outside of the limits set there.
A minimum of 10 WTUs with representative geophone strings connected should be
deployed within range of the MAN. Great care should be taken to ensure that all the sensors
are planted correctly.
124
Sensor Tilt Model creation > Acquire and save the model sensor response
Acquire and save the model sensor response

1. Select WTU Parameters from the Edit menu to open the “WTU Parameters”
window.
2. Click on the Scheduled Tests tab.
Figure 3-80 Scheduled Tilt test
3. In the “Tests to Run” list, tick the Sensor Tilt option.

4. In the “Times to Run Tests” area, select the appropriate time to run a Tilt test: this
must be within the WTUs Working Hours, and you must make sure no source is due
to be launched during the test.
5. Click Apply and OK.
6. In the “WTU Table” view, select the planned WTUs for the Tilt test (WTUs with
correctly planted sensors), and select Generate Scheduled BIT VPs. This creates a
VP entry, in the “VP Table” view, for each Tilt test that was performed over the time
span you specify in the dialogue box that shows up.

Sensor Tilt Model creation > Acquire and save the model sensor response 3
Figure 3-81 Generate scheduled BIT VPs
- Click OK.
Field Units
Figure 3-82 Waiting for Tilt test results
7. After the Tilt test is performed as scheduled and the acquired raw data is transferred
to the server via the MAN, the harvesting status of the tested WTUs should change
from orange to green.
8. In the “VP Table” view, select the Sensor Tilt VPs created in step 6, and select
Create Tilt Model from the right-click popup menu.
126
Sensor Tilt Model creation > Acquire and save the model sensor response
Figure 3-83 Creating the Tilt Model
This brings up a dialogue box that allows you to save the response
acquisition model to a named file in an appropriate folder.
Note Alternative option to create the Tilt Model is to select the WTU, right-click and
use the function Run BITs. Then select Sensor Tilt and Tick the checkbox
Generate VPs
Figure 3-84 Run Sensor Tilt Test

Sensor Tilt Model creation > Load the sensor response model 3
Load the sensor response model

After the sensor response model has been created and saved, it must be loaded by the server,
to be used as the reference model in the Sensor Tilt tests.
This is done with the Tilt Model (page 90) tab in the Field Unit parameters setup.
Figure 3-85 Field unit parameters — Tilt Model tab
Click Load Model to browse to the location of the sensor response model (a *.mdl file).
Select the desired *.mdl file and click Open to load the sensor response model file.
Click Apply and then OK.
Figure 3-86 Set Tilt Model
Optimising the Sensor Tilt threshold limits

When the Sensor Tilt test is performed by the system, the actual response of each set of
sensors is compared with the model response acquired, stored and loaded as described above.
This analysis produces a difference figure scaled in %, that is then compared with the Sensor
128
Sensor Tilt Model creation > Optimising the Sensor Tilt threshold limits
Tilt threshold set in the General Parameters (page 73) tab to determine whether the
test has passed or failed.
In order that the Sensor Tilt test produces the most accurate results, care must be taken to
select an optimum value for the Sensor Test threshold and a method for doing this is outlined
below for WTUs with geophone strings.
1. Lay out 10 WTUs with representative geophone strings attached. The WTUs should
have a wireless connection to a DCM server network through a MAN.
2. Ensure that all geophones are correctly planted.
3. Run the Sensor Tilt test and record the returned value of Sensor Tilt for each WTU.
Figure 3-87 Sensor Tilt Result
4. On half of the tested geophone strings, tilt one of the geophones to an angle that
would be deemed unacceptable, at least one of these being 90ο (i.e. geophone laid
flat on ground). On the other half of the tested geophone strings, tilt one of the
geophone to an angle that would be deemed acceptable, bearing in mind the
geophone manufacturer’s specification for tilt performance.
5. Run the Sensor Tilt test again and note the values for Sensor Tilt returned by both
groups of geophone strings. Select a value of Sensor Tilt that lies between that
returned by WTUs with sensors tilted out of tolerance, and that returned by WTUs
with sensors whose tilt is within tolerance. Enter this value as the Geophone
threshold setting in the General Parameters (page 73) > Sensor Tilt field.
6. Run the Sensor Tilt test once more and note the WTUs that are reported as having
failed this test. These should match with the WTUs that are connected to geophone
strings having a geophone tilted out of tolerance. Note the WTUs that are reported as
having passed the test. These should match with the WTUs that are connected to
geophone strings having a geophone tilted within tolerance.
7. Replant all of the geophones that are tilted out of tolerance and ensure that their tilt
angle is within the manufacturers tolerance before running the Sensor Tilt test once
more. This time ensure that all the WTUs are reported as having passed the Sensor
Tilt test.

Working with Stake IDs > About Stake ID mapping 3
Working with Stake IDs

In this section:
• About Stake ID mapping (page 130)
• Assigning field units to topographic locations and correcting geometry
errors in Positioning (page 130)
• Checking for duplicate stakes (page 132)
• Updating Stake ID Mappings (page 132)
About Stake ID mapping

In DCM software “Stake ID mapping” is the mapping of WTU serial numbers to Line and
Station numbers. This association is how the server knows which WTU to obtain data from
for each shot or VP.
Under ideal circumstances the mappings would be set from the DCM window prior to
shooting by upload of a WTU list from a PFT, or by entering the numbers manually. Every
time a shot is taken the current mappings (as shown in the Topo view) would be applied to
the new shot. If the mappings are changed in the WTU Table view then the new mappings
would be used for the next shot, but would not affect previous shots.
Under field conditions the following situations can occur:
1. A delay in getting the Stake ID mappings from the layout crew would mean that the
Observer would have to waste time waiting for the mappings to arrive before starting
shooting. This could seriously impact production.
2. A mistake may have been made in the mappings. Each individual mistake can mean
incorrect trace order in the SEG-D file, or a dead channel.
3. Field crew may have had to replace a WTU but have been unable to give the
Observer details of the new Stake ID mapping for several hours, and in the meantime
more shots have been taken. In this case the new WTU has recorded data for these
shots, but the server will only get data from the new WTU from the point the
Observer was able to enter the new mapping — leading to dead channels in shots
where in actual fact the data was available.
The “Change Markers” feature in DCM and the “Aided-assignment” function in Position
allow these sorts of problems to be solved.
Assigning field units to topographic locations and correcting

geometry errors in Positioning
The “Change Markers” feature in DCM and the “Aided-assignment” function in Positioning
allow changes and corrections to Stake ID mappings to be applied to shots that have already
been taken, and even to finalised SEG-D files.
130
Working with Stake IDs > Assigning field units to topographic locations and correcting geometry errors in
Positioning
In addition to making corrections to the current or a past Stake ID mapping, these features
(especially the “Aided-assignment” function) can also be used to create a new Stake ID
mapping from scratch.
Judicious use of those features means higher production (because shooting can start earlier),
and elimination of dead channels due to the above causes.
• See Assigning field units to topographic locations and correcting geometry
errors in Positioning (page 130) and Updating Stake ID Mappings
(page 132)
• “Aided assignment” is described in the chapter dedicated to Position: see Auto-
assignment based on GPS positions and geometry correction (page 192).

Working with Stake IDs > Checking for duplicate stakes 3
Checking for duplicate stakes

It is possible the changes may have resulted in duplicate WTUs for the same stake. Have a
look through the WTU Table view looking for Stake IDs highlighted red. If you find any you
have to assume that your new assignment is correct, so consult your list of changes, and clear
the Stake ID for the old WTU.
Now your list is correct, you need to apply it to shot files. Refer to Updating Stake ID
Mappings (page 132) below.
Updating Stake ID Mappings

Let us assume that this is the first days shooting and there has been a problem getting the
Stake ID assignment information to the Observer. However, the field crew have checked the
WTUs and they are all good to go, and the shooting teams are in place waiting.
Rather than waste valuable time waiting for the Stake IDs to arrive we can start shooting now,
even though we don't have stakes assigned to any of our WTUs, but we will have to update
the mapping at some point after the Stake ID assignment information has been loaded to the
server. Then if a Data Harvester is plugged in, we will be able to harvest data from the WTUs
for all shots as normal.
To update the Stake ID mapping for one or more shots, select the shots in the VP Table view.
Then right-click on them and select Update markers in VPs. The following dialogue
appears, providing different ways of updating stake ID mappings.
Figure 3-88 Change Markers dialogue
Update to current marker model

If you choose the Update to current marker model option, clicking OK applies the current
stake ID mapping (as shown in the Topo view) to the shots that were selected in the VP Table
view.
Update to one VP’s marker model

This option brings up a window prompting the list of VPs (same as the VP Table view).
132
Working with Stake IDs > Updating Stake ID Mappings
Figure 3-89
Select which VP you want to copy markers from. Clicking OK applies the stake ID mapping
from this VP to the VPs that were selected in the VP Table view.
Expert mode to update markers

When performing historical edits it is often the case that the current Stake ID assignments
have changed and it is undesirable to load in old Stake IDs into DCM just for the purpose of
an edit. In this case, manually entering the changes in the table is the best way to proceed.
Figure 3-90
• Line Number — Mandatory. The line number of the Stake.

• Point Number — Mandatory. The station number of the Stake.
• From WTU — Optional. The serial number of the existing WTU assigned to the Stake.
- Choosing “Any” means “Match any WTU”.
- Entering 0 means “Match any unassigned WTU”.
- Entering a serial number means “Match only this specific WTU”.

Working with Stake IDs > Updating Stake ID Mappings 3
In most cases it is best to choose “Any”. If a number is entered here the mapping
will only be updated in each particular shot if the existing WTU matches.
• To WTU — Mandatory. The serial number of the WTU that is to be assigned to this
Stake. Entering 0 means there is no WTU at this Stake (and the channel will be marked
as failed).
• From Channel - Mandatory. The source channel of the Marker changes.
• To Channel- Mandatory. The destination channel of the topo location.
When numbers are input to this table, the background colour of the row indicates whether
the entries are complete. A red background colour means there are missing mandatory
entries.
In the case where different selected VPs have different WTU IDs assigned to the same Line
and Station, the “From WTU” should be set to “Any”.
Clicking OK causes the VPs that were selected to be updated by applying the changes listed.
Note It is possible to copy and paste tab separated data (e.g. from Open Office Calc
spreadsheets) to and from the Expert mode to update markers table.
Check the history of marker updates
Figure 3-91
The Check the history of marker updates option shows a complete history of all changes
applied. Details of an individual change can be displayed by clicking the View change
details button.
134
Working with Stake IDs > Updating Stake ID Mappings
Figure 3-92
The last update to be performed can by undone by clicking the Undo last update button.
Note Once an Undo has been performed, there is no way to automatically “re-do” it,
and the details of the change are deleted.
Tips and Tricks

• Apply any updates before updating the Data Harvesters with the new list to harvest.
• In general,
- If the changes you want to make apply to the current WTU list, make the changes
to the WTU list then select the relevant previous VPs immediately and select
Update markers in VPs > Update to current marker model.
- If they do not apply to the current WTU list, use the the Expert mode to update
markers table to enter the details at an opportune time.
• If data has been gathered for a particular WTU in a shot, then that WTU is swapped out
of the shot, the data remains in the temporary file but is ignored. A list of extraneous data
(if any) in a temporary file can be found by opening the VP in TraceView and selecting
File > Properties > Other Details. If the mappings are updated again and the original
WTU reinstated the data will automatically appear, meaning there is no need to re-
harvest. Finalising files to SEG-D removes extraneous data.

Generate SPS-Out and Observer Reports > Report Generation 3
Generate SPS-Out and Observer Reports

In this section:
• Report Generation (page 136)
• File Format (page 137)
• Example of RAW Observer Report (JSON format) (page 139)
Report Generation
1. Open “Generate Reports” dialogue by clicking the icon in DCM.
Generate Reports
Figure 3-93 Generate Reports dialogue
2. Choose the Time Range to ask for the corresponding reports

3. Select the Type of Reports (Observer Reports, SPS Reports or both).
136
Generate SPS-Out and Observer Reports > File Format
4. Select option “Split by date” to create one set of reports for each julian day,
otherwise each report file generated will contains all shots reports for the entire
requested period.
5. Select the Destination folder to save the reports and Click OK
6. When report generation is done, destination folder is opened in the file explorer. Two
Observer reports (RAW JSON and Excel-compatible) and three SPS reports (R, S
and X) are generated per swath per range of dates.
userdcm
userdcm
• If option “Split by date” was selected, one set of reports per julian day is created.
• Fo r Observer output, all the generated SEG-D files will be taken into account (RAW and
DUMP processed SEG-D files).
• Fo r SPS output, only the DUMP SEG-D files processed will be taken into account (no
way to distinguish RAW/DUMP entries in SPS format).
File Format
Each report generated will be named as:
<date>_<time>_<swathName>_<reportType>.<reportExtension>
Table 3-2
Server local start date of the report (YYYYMMDD format) i.e.
date date of the first shot in the report (same as date from GH1 in
SEG-D headers)
Server local start time of the report (HHMMSS format) i.e.
time time of the first shot in the report (same as time from GH1 in
SEG-D headers)

Generate SPS-Out and Observer Reports > File Format 3
Table 3-2
swathName Swath name of the shots in the report
Type of the report
reportType - Observer
- SPS
Extension of the report related to its type:
- .json for Observer RAW JSON
- .xml for Observer XML Excel compatible
reportExtension
- .r for SPS R
- .s for SPS S
- .x for SPS X
The RAW format of Observer report will correspond to a standard JSON format whereas the
XML format (Excel compatible) of Observer report will correspond to an XML file
Microsoft office schema.
The SPS (R, S and X) format will correspond to SPS specifications revision 2.1 (refer to
Sercel SPS standard 2.1).
138
Generate SPS-Out and Observer Reports > Example of RAW Observer Report (JSON format)
Example of RAW Observer Report (JSON format)

"Obs_Report_Result": {
"Observer_Report": {
"Line Report": {
"Total number of traces": "44",

"Number of Auxes": "0",
"Number of Seis traces": "44",
"Number of dead Seis traces": "0",
"Number of live Seis traces": "44",
"Spread first line": "N\/A",
"Spread first number": "N\/A",
"Spread number": "N\/A",
"Spread type": "N\/A",
"Internal time break": "0",
"Acquisition error description": "N\/A",
"Filter type": "0.8FN Lin Phase",
"Dead Seis": "",
"Live Seis": "1:3-1 (1-2)\n1:2-4 (3-4)\n1:5-44
(5-44)"
},
"Shot Report": {
"Sample rate": "2000",

Generate SPS-Out and Observer Reports > Example of RAW Observer Report (JSON format) 3
"Source line number": "1.00",

"Source point number": "7831.00",
"Source point index": "1",
"Source Set Number": "0",
"Source Easting": "0.00",
"Source Northing": "0.00",
"Source Elevation": "0.00",
"COG Easting": "N\/A",
"COG Northing": "N\/A",
"COG Elevation": "N\/A",
"Acquisition length": "60002",
"Number of samples": "30001",
"Type of source": "impulsive",
"Shot number": "1864552994",
"TB window": "0",
"Shot date time": "20160727 16:00:00",
"Uphole time": "0",
"Blaster id": "0",
"Blaster status": "0",
"Record length": "60002",
"Pilot length": "0",
"Sweep length": "0",
"Swath name": "sw1",
"Operating mode": "normal",
"Swath Id": "1",
"Observer comments": ""
},
140
Generate SPS-Out and Observer Reports > Example of RAW Observer Report (JSON format)
"Noise Report": {
"Noise elimination type": "none",

"Low trace percentage": "N\/A",
"Low trace value": "N\/A",
"Number of windows": "0"
},
"Process Report": {
"Type of process": "Raw Data",

"Autocorrelation peak time": "N\/A",
"Correlation Pilot No.": "0",
"Acquisition number": "N\/A",
"Max of max Aux": "N\/A",
"Max of max Seis": "N\/A",
"Dump stacking fold": "1",
"GPS time of acquisition TB":
"1153670417000000",
"Max time values": "N\/A"
},
"Record Report": {
"File number": "8831",

"Record type": "normal",
"Test record type": "normal",

Generate SPS-Out and Observer Reports > Example of RAW Observer Report (JSON format) 3
"Type of dump": "normal",

"Processing time": "1156768624497000"
},
"Others": {
"Software version": "3.1.0.0 ",
"User text": ""
}
}
142
Archive/Restore prospect database > Example of RAW Observer Report (JSON format)
Archive/Restore prospect database

A tool called “Archive” allows you to archive the whole content of the DCM database
(optionally included seismic data). This could be useful in case of server crash to restore the
state of your prospect and not losing some data.
Figure 3-94

Archive/Restore prospect database > Archive Prospect Database 3
Archive Prospect Database

1. Open Archive using the shortcut located in Applications > Sercel > Data Completion
Manager > Archive.
Figure 3-95
2. Select the backup directory to save the database (preferably on an external drive).
There are two additional options:
• With seismic data (need more space)
144
Archive/Restore prospect database > Archive Prospect Database
• With checksum (slower but safer, this option is used to detect

errors which may have been introduced during transmission or
storage of the data)
Figure 3-96
3. Click Backup. You can see the progress bar during the backup. When it’s done,
details field gives you statistics about number of files transferred, total amount of
data and throughput.

Archive/Restore prospect database > Restore Prospect Database 3
Restore Prospect Database

1. Open Archive using the shortcut located in Applications > Sercel > Data
Completion Manager > Archive.
Note Ensure that you Stop the DCM server before attempting to restore the database.
2. Select backup directory and Click “Restore”. A popup window appears to warn the
user that this action will replace the existing prospect data (including seismic) with
the content of the backup.
Figure 3-97
3. Type “delete and restore” in the appropriate field to confirm the restoration and
click OK.
Figure 3-98
146
DCM Trace Diagnostic Codes > Overview
DCM Trace Diagnostic Codes

Overview
To aid fault finding and QC, the DCM system is capable of reporting detailed diagnostic
information for the reason a trace has been marked dead in the acquisition files. This
information can be viewed in the TraceViewer software “TraceView” tool.
There are two categories of diagnostic codes, Absolute and Historic.
Absolute codes
Absolute codes are returned in situations where it is possible to absolutely determine the
reason no data was transcribed for the time in question.

DCM Trace Diagnostic Codes > Historic codes 3
Table 3-3 Absolute codes
Code Description
OK The data was successfully retrieved.

No WTU
There is no WTU assigned to the Line and Station for this channel.
assigned
Muted/Forced During a manual set of BITs the WTU disconnected from the recorder
BIT and so was excluded from the remainder of the tests in the test script.
The data requested was for a time before the earliest data available in
Data Rollover
the WTUs flash memory.
The WTU does have data for the time of the shot, but the data was
Parameter recorded with different acquisition parameters (so the WTU was
Mismatch recording with a different sample rate/gain, or possibly was generating
BIT data).
The shot has not been transcribed to SEG-D yet, and the system is still
Outstanding
waiting for data from the WTU.
Forced While the data was still outstanding the observer has manually
Complete completed the trace by marking it as dead.
The data packed received from the WTU was corrupt. Could be seen if
Protocol the DCM server and WTU were running incompatible versions of
software.
Invalid The WTU was unable to return data for the channel specified. Typically
Channel seen if a 1 Channel WTU was marked where 3C data was expected.
Historic codes
The WTU saves samples to files in flash memory on a regular basis. When saving the file the
WTU will also include the reason it is saving the file. Under normal situations the reason the
WTU is saving a file is that it is flushing the data held in RAM to permanent storage, but
there are various situations when the WTU flushes the RAM to permanent storage for other
reasons.
In the case where it was not possible for the WTU to supply data for a given time the WTU
will search back through its flash memory to find the last sample file that was saved, and read
the code which determines why it last stopped recording.
When analysing these codes it is important to remember that they are the reason that the
WTU last stopped recording prior to (or during) the time of the shot, so the code may not
indicate the exact state of the WTU at the time of the event. For example, if the code reported
is “Stopped (State Sleep)” but the WTU was expected to be awake for the shot, one
148
DCM Trace Diagnostic Codes > Historic codes
possibility could be that the WTU went to sleep, woke up correctly, but was unable to gain
initial GPS lock. In this case until the WTU gains GPS lock it will not be able to create files
as it does not know what the current time is.
Table 3-4 Historic codes
Code Description
Stopped(GPS Lock Lost) The WTU stopped sampling because GPS lock was lost.
The WTU detected its timing was out of tolerance and
Stopped(Timing Resync)
stopped sampling to resynchronise.
Stopped(Parameter The WTU stopped sampling as it received a command
Change) from the recorder to change acquisition parameters.
The WTU stopped sampling as it was commanded into an
Stopped(State Idle)
Idle state by the recorder.
The WTU stopped sampling as it was commanded into a
Stopped(State Standby) Standby state by the recorder (can be seen when
transitioning to and from other states).
Stopped(State Sleep) The WTU stopped sampling as it is about to go to sleep.
The WTU stopped sampling seismic data as it is about to
Stopped(State Test)
perform one or more BITs.
Stopped(State Firmware) The WTU stopped sampling to perform a firmware update.
The WTU has detected an internal condition that requires
Stopped(Reset acquisition)
sampling to be restarted.
The WTU saved samples to continue sampling with
Stopped(State Acquire) different acquisition parameters. This code is here for
completeness, and should not occur.
The WTU does not have the data, and the stop reason
reported in the last file to be saved to the WTUs flash was
a normal flush from RAM, meaning the WTU unexpectedly
Data Not Recorded
stopped recording shortly after. The most common
reasons for this would be if the WTU was turned off by
removing the dongle, or if the battery ran out.
No BIT result There was a failure running the BIT test.
No Sensor attached WTU not attached, or sensor board failure.
The WTU was asked to perform a BIT that it does not
Unsupported BIT
support.

Chapter
4 Position
This chapter gives the user a description of the Position window.

• Position Interface (page 152)
• View menu (page 167)
• Field Units Menu (page 173)
• Settings Menu (page 184)
• Auto-assignment based on GPS positions and geometry
correction (page 192)

Position
Overview >
Overview
The Position application provides a graphic view of WTU’s on the field once they have
acquired GPS position.
This application allows you to automatically or manually assign WTU’s to Stake IDs, change
the order of WTU’s, find WTU’s, and quickly identify problems with field units.

Position
Position Interface > Main Window 4
Position Interface
To open the Position application main window, click on the Tools menu in Data Completion
Manager then select Open Position or click on Position Icon.
Open Position
Application
Main Window
Figure 4-1 Position window
152
Position
Position Interface > Main Window
Pointing tools
The pointing tools available from the Position toolbar affect the way the cursor interacts with
the map.
Figure 4-2 Position pointing tools
Select
With this tool you can click on a WTU or a receiver Line to select it. You can also draw a
selection rectangle around a group of WTUs to select them. Holding the “Ctrl” key while
clicking on a WTU adds that WTU to the current selection.
Clicking on an empty map area clears the current selection.
Selected WTUs show in a different colour and, if they are assigned to a receiver loaded in
Position, a line is drawn between the WTU and its receiver.
Selected lines are drawn with a thick yellow line.
The mouse wheel allows zooming in/out inside the map view.
Pan
With this tool you can move the map by clicking and dragging it. The mouse wheel allows
zooming in/out inside the map view.
Zoom
With this tool you can zoom on an area of interest by drawing a rectangle around the desired
area. The map is then resized so that the selected rectangle fits to the window pane. The
mouse wheel allows zooming in/out inside the map view.

Position
Center Map on Recorder

Clicking this icon allows you to centre the map on the recorder in field.
Finding a Field Unit on the map

An input field in the Position toolbar makes it possible to enter a WTU identifier. If you click
the Find Field Unit button and the WTU is present on the map, then the map is centred on
this WTU and the WTU is selected.
Figure 4-3 Find WTU button and input field.
154
Position
Time Filter
The Time Filter function (if selected), allows you to filter the display of field units by time.
Only field units that are more recent than the indicated time will be displayed. If the Time
filter is not selected, all known field units will be displayed.
Time may be indicated as local time (time indicated by your machine) or UTC.
Figure 4-4 Time filter
In order for field units to be identified (after the indicated date), at least one of the following
conditions must be true:
• QC for the field unit(s) has been received after the indicated date
• SOH for field unit(s) has been received after the indicated date
Field units that have been identified can be used with the assignment function and SOH
information is available.
Field units that have not been identified cannot be assigned and SOH information is not
available.
WTU Color Status

WTUs are displayed on the map as a circle with a colour reflecting its status, to be interpreted
as follows:
Grey circle: the WTU is not assigned to any receiver or is assigned to a receiver that
is not loaded into Position (see Load Receivers on page 158).
Green circle: the WTU is assigned to a receiver loaded into Position and no problem
has been detected on this WTU (see Warnings Table on page 183 to see which
problems may be detected).
• a Gateway WTU is indicated by a larger dotted circle surrounding
the green circle.
Figure 4-5 Gateway WTU

Position
Red circle: a problem has been detected on this WTU (see Warnings Table on
page 183 to see which problems may be detected).
Figure 4-6 Position WTU colors status
156
Position
WTU association
When a WTU is selected, the receiver point to which it is mapped is displayed as a segment
joining the WTU icon and the receiver point.
In the example below WTU 1569 is associated with receiver point 111 on line 170.
Figure 4-7 WTU association
When a WTU is selected on the map, its instrument ID is displayed above the WTU icon.

Position
File Menu > Load Receivers 4
File Menu
Figure 4-8 File Menu
In this section:
• Load Receivers (page 158)
• Add Image (page 161)
• Add Vector (page 166)
• Add Vector Directory (page 166)
• Export Settings (page 166)
Load Receivers
Selecting Load receivers… from the File menu allows you to load the prospect’s receiver
positions into Position in order to perform automatic or manual stake assignment, or to check
the GPS positions collected from harvested WTUs against the theoretical locations of
receiver points.
Prior to loading any receivers, you must select the appropriate projection for the prospect (see
Projection management (page 187)).
158
Position
File Menu > Load Receivers
If no projection is selected, an error message is displayed, otherwise the “Load a receivers

file” window appears:
Figure 4-9 Load a receivers file
Click Browse button and select the file you want to load to Position.
File format
This field is used to choose the receiver file format:
• SPS-R if the receiver file is an SPS file. Both SPS Rev 1.0 and 2.1 are supported and
automatically recognized.
• CSV if the receiver file is a CSV file, with the following content:
• ASCII file with fields separated by commas.
• The first line is considered as data (no header).
• A data line should have the following fields: receiver line number,
receiver point number, receiver Easting, receiver Northing.
File linear units

This drop-down list allows you to choose the unit used to express Easting and Northing in
the file. By default, this unit is the same as selected in the projection setup.
The receivers appear on the map as yellow flags linked with yellow lines if they belong to the
same receiver Line.

Position
File Menu > Load Receivers 4
The Line number is written next to the first receiver in the Line.
Figure 4-10 Receiver Line
Receiver Lines can be selected by clicking on them with the Select pointing tool (see
Pointing tools (page 153)).
When a receiver Line is selected, it is displayed with increased thickness. A line is drawn
between the receivers in that Line and the WTU assigned to those receivers.
160
Position
File Menu > Add Image
Add Image
The map display can be used to display images. The images must be “geo-referenced” i.e.
contain embedded geographical information (e.g. GeoTiff).
To import an image select File >Add Image… and select an image file from the file open
dialogue. If successful the Layers dock window will show the loaded image layer
(Sercel_uPos.tif in the example below).
Figure 4-11 Add image background
Supported Formats
The GDAL library used has support for the following formats: Currently only geo-referenced
images like GeoTIFFs are supported. i.e.
Images that contain the information to position and warp the image data onto a map.
• VRT (rw+): Virtual Raster
• GTiff (rw+): GeoTIFF
• NITF (rw+): National Imagery Transmission Format
• RPFTOC (ro): Raster Product Format TOC format
• HFA (rw+): Erdas Imagine Images (.img)
• SAR_CEOS (ro): CEOS SAR Image
• CEOS (ro): CEOS Image
• JAXAPALSAR (ro): JAXA PALSAR Product Reader (Level 1.1/1.5)

Position
File Menu > Add Image 4
• GFF (ro): Ground-based SAR Applications Testbed File Format (.gff)

• ELAS (rw+): ELAS
• AIG (ro): Arc/Info Binary Grid
• AAIGrid (rw): Arc/Info ASCII Grid
• SDTS (ro): SDTS Raster
• DTED (rw): DTED Elevation Raster
• PNG (rw): Portable Network Graphics
• JPEG (rw): JPEG JFIF
• MEM (rw+): In Memory Raster
• JDEM (ro): Japanese DEM (.mem)
• GIF (rw): Graphics Interchange Format (.gif)
• ESAT (ro): Envisat Image Format
• BSB (ro): Maptech BSB Nautical Charts
• XPM (rw): X11 PixMap Format
• BMP (rw+): MS Windows Device Independent Bitmap
• DIMAP (ro): SPOT DIMAP
• AirSAR (ro): AirSAR Polarimetric Image
• RS2 (ro): RadarSat 2 XML Product
• PCIDSK (rw+): PCIDSK Database File
• PCRaster (rw): PCRaster Raster File
• ILWIS (rw+): ILWIS Raster Map
• SGI (rw+): SGI Image File Format 1.0
• SRTMHGT (rw): SRTMHGT File Format
• Leveller (rw+): Leveller heightfield
• Terragen (rw+): Terragen heightfield
• ISIS3 (ro): USGS Astrogeology ISIS cube (Version 3)
• ISIS2 (ro): USGS Astrogeology ISIS cube (Version 2)
• PDS (ro): NASA Planetary Data System
• ERS (rw+): ERMapper .ers Labelled
• L1B (ro): NOAA Polar Orbiter Level 1b Data Set
• FIT (rw): FIT Image
• GRIB (ro): GRIdded Binary (.grb)
162
Position
• RMF (rw+): Raster Matrix Format

• MSGN (ro): EUMETSAT Archive native (.nat)
• RST (rw+): Idrisi Raster A.1
• INGR (rw+): Intergraph Raster
• GSAG (rw): Golden Software ASCII Grid (.grd)
• GSBG (rw+): Golden Software Binary Grid (.grd)
• GS7BG (ro): Golden Software 7 Binary Grid (.grd)
• COSAR (ro): COSAR Annotated Binary Matrix (TerraSAR-X)
• TSX (ro): TerraSAR-X Product
• COASP (ro): DRDC COASP SAR Processor Raster
• PNM (rw+): Portable Pixmap Format (netpbm)
• DOQ1 (ro): USGS DOQ (Old Style)
• DOQ2 (ro): USGS DOQ (New Style)
• ENVI (rw+): ENVI .hdr Labelled
• EHdr (rw+): ESRI .hdr Labelled
• GenBin (ro): Generic Binary (.hdr Labelled)
• PAux (rw+): PCI .aux Labelled
• MFF (rw+): Vexcel MFF Raster
• MFF2 (rw+): Vexcel MFF (HKV) raster
• FujiBAS (ro): Fuji BAS Scanner
• Image GSC (ro): GSC Geogrid
• GSC (ro): GSC Geogrid
• CPG (ro): Convair PolGASP
• IDA (rw+): Image Data and Analysis
• NDF (ro): NLAPS Data Format
• EIR (ro): Erdas Imagine Raw
• DIPEx (ro): DIPEx
• LCP (ro): FARSITE v.4 Landscape File (.lcp)
• RIK (ro): Swedish Grid RIK (.rik)
• USGSDEM (rw): USGS Optional ASCII DEM (and CDED)
• GXF (ro): GeoSoft Grid Exchange Format
• ADRG (rw+): ARC Digitized Raster Graphics

Position
File Menu > Add Image 4
• BLX (rw): Magellan topo (.blx)

• FAST (ro): EOSAT FAST Format
• BT (rw+): VTP .bt (Binary Terrain) 1.3 Format
• CPG (ro): Convair PolGASP
• IDA (rw+): Image Data and Analysis
• NDF (ro): NLAPS Data Format
• LAN (ro) Erdas .LAN/.GIS
164
Position
Add Image (non-georeferenced)

If you try to import a non-georeferenced image, Position will reject it and propose a tool
called “GeoRef” in order to add manually known positions to the file
Click Launch georef… to open the image in Georef.
Figure 4-12 Launch Georef
Then use the Add Point button and enter Latitude and Longitude coordinates to
manually define a known position on the image. At least 4 positions need to be defined to
correctly geo-reference the image. The easiest way is to define the 4 corners of the image.
Figure 4-13 Add point in Georef

Position
File Menu > Add Vector 4
When known positions are defined, use the function File > Save Georeferenced to save the
image in geotiff format. Now you can import it to the Position window.
Add Vector
This function allows you to import vector graphics.
Add Vector Directory

This function allows you to import all vector graphics from a directory.
Export Settings
This function allows you to export geographic settings in a file format. This file can then be
imported into Field Monitor in order to display a background map and SPS receivers.
166
Position
View menu > Zoom menu
View menu
Figure 4-14 View Menu
In this section:
• Zoom menu (page 167)
• Rotation (page 168)
• Layers (page 169)
• Warnings (page 171)
• Gateways (page 172)
• Position Toolbar (page 170)
Zoom menu
Zoom In
Zoom in the display.
Zoom Out
Zoom out the display.
Fit to window
Fits the view to the window’s size.

Position
View menu > Rotation 4
Rotation
Toggles viewing on the left-hand side of the Position window the Rotation control toolbar.
Use the dial in the Rotation box to rotate the display. The rotation dial is based on the North
position if pointed upwards (as in the image below).
Figure 4-15 Rotation dial
168
Position
View menu > Layers
Layers
The map display shows layers of information. These layers are represented in the Layers
dock window as a list. Layer setup is saved and restored when the application is restarted. The
Layers dock window allows the following control of a layer.
Figure 4-16 Layer Controls
Show/Hide a Layer
Show or hide a layer by setting/clearing its checkbox in the Layers dock window
Zoom to Layer Extent

Select the Zoom to Layer Extent command from a layers right-click menu and the map will
try to pan and zoom to show the full layer in the map screen. e.g. For the WTU layer this will
try to zoom out and pan so that all WTUs are shown on screen.
Reproject Layer to Grid

Select this right-click menu option to attempt to warp the selected layer to the currently used
X/Y grid.
Use UTM Projection from Layer

The map initially has no XY transform to convert GPS lat/long positions to map/screen x,y
coordinates. As soon as any position information is loaded (WTU sending GPS position or
loading an image layer with geo-reference data) the map tries to select and create a transform
to x,y coordinates
If the position source is a grid x,y projection (e.g. an geo-referenced image with a projection
defined) then this will be used otherwise the nearest UTM grid will be selected automatically
instead. If you have layers where the positions differ by large amounts (e.g. by loading in an
image layer of an area a long way away from positions the WTUs are sending) then the
automatically chosen transform may fail for some of the layers. If this happens the failed
layer will be shown with a warning background colour.

Position
View menu > Position Toolbar 4
The Use UTM Projection from Layer right-click menu command allows you to select the
best grid transform for the selected layers and then apply this transform to all the other layers.
Remove
The Remove command is only available for some layers. It will remove the selected layer
from the layer list on the map.
Position Toolbar
This toggles viewing of the Position Toolbar.
Figure 4-17 Position Toolbar
Dock all views

This option manipulates the panes, docking them when left-clicked.
170
Position
View menu > Warnings
Warnings
Toggles viewing on the left-hand side of the Position window the Warnings table.
The Warnings table identifies potential problems wit the field units. The tick boxes on the
left make it possible to choose which types of automatic checks to do.
.
Figure 4-18 Warnings table (Position)
Figure 4-19
See Auto-assignment based on GPS positions and geometry correction

(page 192) for details.

Position
View menu > Gateways 4
Gateways
This toggles viewing on the left-side of the screen the Gateways window.
Gateway units recover State of Health (SOH) data from neighbouring field units. See State
of Health (SoH) Warnings (page 203) for more information.
The gateways window displays a list and details of all boxes that are or have previously been
designated as ‘Gateway’ field units.
The ‘Nb. of field units’ field indicates how many field units are currently transmitting data
via this gateway.
Figure 4-20 Gateways window
172
Position
Field Units Menu > Change Stake ID’s (manually)
Field Units Menu

In this section:
• Change Stake ID’s (manually) (page 173)
• Automatic Stake ID assignment (page 174)
• Copy Field Units (page 180)
• Select VP’s (page 181)
Figure 4-21 Field Units Menu
Change Stake ID’s (manually)

DCM software allows you to manually change/assign Stake IDs for field units once these
have acquired GPS lock position.
In the example below, some field units have been assigned e.g. 1624, 1475, 1598, etc. While
others have not been assigned, e.g. 1483, 1632, 1468, etc.
Field Units
Not Assigned
Figure 4-22 Field Units unassigned

Position
Field Units Menu > Automatic Stake ID assignment 4
1. Enter the Line and Point Number of the VP to which you would like to assign the
field unit.
Figure 4-23 Field Unit Manual Assignment
2. Click OK.
Automatic Stake ID assignment

Automatic assignment will automatically map a field unit to its closest available VP (line and
point number).
To assign/change stake IDs:
1. Use the dial in the Rotation box to rotate the display so that the line you wish to
number is horizontal on the screen with the lowest numbered station to the left.
2. Select Field Units by dragging a selection box around them using the mouse.
3. Select Field Units > Change Stake Ids.
174
Position
Field Units Menu > Automatic Stake ID assignment
The Stake ID table will display the WTUs with their order dependent
on their X position in the graphical display.
Figure 4-24 Stake Id’s Unassigned
4. Click Calculate. The system will automatically assign the Stake IDs to the nearest
VP.

Position
Figure 4-25 Stake ID’s after Automatic Assignment
WARNING
This can lead to duplicate associations if the offsets are not set appropriately to the
line geometry. The window will highlight Field Units with duplicate associations.
Fill Gaps
The Fill Gaps function will try to fill gaps between assigned field units.
If two consecutive field units have a gap in their channel assignment, (i.e. the point increment
does not match the Field Unit Increment, PointNb value), new lines will be created
between them to hold missing WTUs.
The field unit of these new lines will be assigned to the preceding Line/Point plus the Field
Unit Increment, PointNb. After the field unit is assigned to the guessed receiver.
176
Position
Example: There is a gap of 9 receivers between field units 1427 and 1634, see Figure 4-26.
Figure 4-26 Gap between Receivers

Position
The Fill Gaps function will create 9 field units between these two field units, see Figure 4-
27. You will have to fill the field unit ID with any known field unit positioned on this
location
Figure 4-27 Gaps between Receivers Filled
178
Position
Field Unit order buttons

The selected WTUs appear in the table in the order they were selected in the view, it is not
guaranteed that they appear in the strict line order.
These buttons allow you to sort the WTUs in the table, the way they are geographically
sorted on the map, along the linear extrapolation of selected WTUs positions. This linear
extrapolation is represented by an arrow on the Field Unit order buttons.
Example: the WTUs are sorted along their linear extrapolation, south to north:
Figure 4-28

Position
Field Units Menu > Copy Field Units 4
Example: the field units are sorted along their linear extrapolation, north to south:
Figure 4-29 Field Unit Order
Copy Field Units

The Copy Field Units function copies a selection of field units in the Position view to the
clipboard.
The selected field units can then be pasted to a text editor or a table.
Figure 4-30 Example copy boxes (left) displayed in text editor (right)
180
Position
Field Units Menu > Select VP’s
Select VP’s
Loading in the stakes and Field Unit positions to Position

The GPS position of the Field Unit at the time a shot was taken is harvested along with the
seismic data and stored in the DCM server database. This position can be loaded from the
server database along with the Stake ID mappings for the shot and displayed in the Position
window. It is then possible to use this position to automatically check for geometry errors
and prompt the necessary corrections.
The checks and corrections can be done on one or more VPs — typically a day’s worth of
VPs should be selected.
Note It may be advisable to save off the current markers to a safe location. (In the
DCM window, select Markers > Export markers).
1. Open the Position window.
2. From the WTU menu, choose Select VPs. This opens the Select VPs dialogue box
which allows you to load either the current stake ID mapping (as shown in the Topo
view), or an older stake ID mapping from one or more past VPs.
Figure 4-31 Select VPs
- Check current Positions and Markers: this option imports the most recent
WTU positions based on the QC information and the latest stake ID mapping
loaded to the server.

Position
Field Units Menu > Potential Assignment Problems 4
- Check VP positions and Markers: with this option, two list boxes are prompted,
containing the whole list of VPs so that you can select which VPs to extract WTU
GPS positions from and which VPs to get stake ID mapping from. For example,
you may want to use this option to look for WTU changes throughout the day.
3. Select the appropriate option, depending on what you want to check, and then click
OK. This loads the corresponding WTU GPS positions and stake ID mapping to
Position.
As soon as the GPS positions of WTUs and the VP markers are loaded, the system
automatically performs a number of checks in order to prompt the best possible geometry
corrections.
Potential Assignment Problems

A number of automatic checks on Field Units are performed, based on the Field Unit positions
and the receiver point each Field Unit is assigned to. Every Field Unit on which a problem is
detected shows as a red circle on the map.
In addition, all WTUs with a problem show in a table available by selecting Warnings from
the View menu.
The table contains one line for each WTU revealing a problem, and four columns:
• Sensor: the serial number of the WTU revealing a problem.
• Line: the Line number to which this WTU is assigned (blank if this WTU is not assigned
to any receiver point).
• Station: the receiver point to which this WTU is assigned (blank if this WTU is not
assigned to any receiver point).
182
Position
Field Units Menu > Potential Assignment Problems
• Warning: the description of the problem.
Figure 4-32 Warnings Table
The tick boxes on the left make it possible to choose which types of automatic checks to do
Position Warnings (Wrong line order, Far from prospect, etc.) or State of Health Warnings
(Sensor Error, Low battery, etc.). You may want to disable one or more types of checks in
case of intricate survey configuration. The changes are immediately visible in the problem
table and in the graphic view.
Each table row can be clicked to select a WTU with a problem and center the map on it. The
selected WTU is highlighted.
For a description of the different problems that can be detected, see Automatic checking
of WTU assignment to receiver points (page 197).

Position
Settings Menu > Position Window Options 4
Settings Menu
In this section:
• Position Window Options (page 184)
• Projection management (page 187)
• Channels Management (page 191)
Position Window Options
Figure 4-33 Position Window Options
• Association distance: this field indicates the distance at which assignment is

automatically applied. Any WTU located within the indicated distance will be assigned
to the corresponding receiver point. The distance is expressed in the units chosen in the
projection setup (see Projection management on page 187).
184
Position
Settings Menu > Position Window Options
• Association distance alarm: this indicates the threshold at which a WTU is considered
too far from a receiver point.
• GPS position display format: this format affects the cursor GPS position displayed at
the bottom right in the Position window. It also affects the GPS coordinates displayed in
the Warnings Table (page 183). The two possible options are:
- GPS position displayed in degrees/minutes/seconds/hundredth of a second.
- GPS position displayed in decimal degrees.
Following options are used to facilitate the display of elements on the position view:
• Field Unit display angle: angle to display the field unit IDs on the Position view.
• Receiver ID display angle: angle to display the Receivers Points on the Position View.
See an example below with Receiver ID display angle set to 45°.
Figure 4-34 Position View Display Receiver IDs

Position
Settings Menu > Position Window Options 4
• Association Shape: shape of association display for WTUs associated to receivers

points. If the associations are difficult to see because they overlay each other or they
overlap the lines representation, they can be curved in the Options window
Figure 4-35 Position View Line Shape Association
186
Position
Settings Menu > Projection management
Figure 4-36 Position View Arc Shape Association
Projection management
By default, Position chooses a UTM projection to display GPS positions on the screen.
However, that projection is not suitable if the prospect uses a different coordinate system, as
is the case most of the time.
Selecting Set projection… from the Settings menu brings up a setup window that allows
you to choose the suitable coordinate system for the prospect.

Position
Settings Menu > Projection management 4
Figure 4-37 Projection Management
In the Projection management window, each of the most commonly used coordinate systems
is identified with an EPSG Code and a Projection name. To find a projection name or EPSG
code, type it into the Filter field.
Selecting a coordinate system automatically sets the default parameters. Choose the same
system as used for staking in the prospect so that the projection of WTU positions can use
the same reference as in the SPS files.
The Manual Edit tab shows the Ellipsoid parameters, Projection type and Projection
parameters of the projection currently selected and makes it possible to edit them so that they
can match those of the prospect. An error message appears, and your changes are discarded,
if any parameter is wrong when you click OK.
188
Position
Settings Menu > Projection management
Figure 4-38 Editable parameters for Lambert projection
• The Ellipsoid parameters section allows you to change the Ellipsoid description, the
Spheroid parameters or the Datum shifts.
• The Projection type list allows you to change the projection type of the coordinate
system.
• The Projection parameters section allows you to change the projection parameters of
the coordinate system. Depending on the projection type selected, some parameters may
or may not be editable.
You can copy and paste a textual description of the projection into the Text Import tab.

Position
Settings Menu > Projection management 4
Figure 4-39 WKT text string for the selected Lambert projection
The Test section allows you to check the projection parameters against a known GPS
reference position if one is available. Enter the GPS coordinates in the Latitude and
Longitude fields and then click the Project button. The projected coordinates are computed
and displayed in the x and y fields. The coordinates should match the expected reference
position in the coordinate system of the prospect.
190
Position
Settings Menu > Channels Management
Channels Management
This function is for future product enhancement. Please ensure that you are working in One
Channel mode.
Figure 4-40 Channel Management

Position
Auto-assignment based on GPS positions and geometry correction > Auto-assignment of WTUs to receiver 4
points
Auto-assignment based on GPS positions and geometry

correction
In this section:
• Auto-assignment of WTUs to receiver points (page 192)
• Manual assignment of Field Units to receiver points (page 196)
• Automatic checking of WTU assignment to receiver points (page 197)
WARNING
To assist you in making sure WTUs are assigned to the correct receiver points, the auto-
assignment function uses the straight GPS positions from the GPS module in the WTU rather
than any differential positions. However, the WTU is able to use Satellite-Based
Augmentation Systems (SBAS), e. g. EGNOS in Europe or WAAS in North America, in
order to make corrections and achieve positioning accuracy at the metre level, which is
suitable for most trace intervals currently used.
The aided-assignment function was tested in open areas with good GPS signals and also on
data from customers in Europe and North America, with quite convincing results. However,
in areas not covered by SBAS systems or more generally with poor GPS coverage, the
positioning accuracy may be variable, which may impair the ability of the auto-assignment
function to grab the correct receiver points.
The auto-assignment function is only provided as an assistant in assigning WTUs to
topo locations and making corrections to the existing WTU assignment, and at all
times the final decision rests with the observer.
In Position, WTUs can be assigned to receiver points automatically or manually. See:
• Auto-assignment of WTUs to receiver points (page 192). The auto-
assignment function is not totally automatic since it will always bring up the “Assign
Stake IDs” dialogue so that you can confirm or cancel it (see Automatic Stake ID
assignment on page 174).
• Manual assignment of Field Units to receiver points (page 196).
Auto-assignment of WTUs to receiver points

A prerequisite for the use of auto-assignment is that the relevant SPS files, containing the
theoretical locations of receiver points have been loaded into Position (see Load
Receivers on page 158).
Position will use these theoretical receiver point locations to suggest which receiver point is
closest to each WTU, but in order to do this, it also requires the GPS position of each WTU.
It can receive these GPS positions by one of the following two methods.
192
Position
Auto-assignment based on GPS positions and geometry correction > Auto-assignment of WTUs to receiver
points
WTU GPS position by XT-Pathfinder

The XT-Pathfinder network is a wireless radio network using the 2.4GHz frequency band.
Through the Pathfinder network, WTUs transmit GPS data from to neighbouring WTUs and
eventually to a gateway WTU.
If the WTUs have been configured with XT-Pathfinder enabled, then, on power up and once
the XT-Pathfinder network has been established, each WTU will transmit its position
through the network to the DCM, and can then have an association suggested by Position.
Figure 4-41 GPS position transmitted by XT-Pathfinder
WTU GPS position by Harvesting

In the situation where the WTUs have been configured without Pathfinder enabled, or if the
ground conditions are such that a Pathfinder network cannot be established, then it is possible
to gather the WTU GPS positions by harvesting each of the affected WTUs.
Auto-assignment can be done either on a set of selected WTUs or on a selected receiver Line.
Two buttons are available from the toolbar that make it possible to assign WTUs to receiver
points automatically:
Auto-assign button Confirm button

Figure 4-42 Auto-assignment buttons

Position
Auto-assignment based on GPS positions and geometry correction > Auto-assignment of WTUs to receiver 4
points
For selected WTUs

1. Select a group of WTUs with the Select tool (see Pointing tools on page 153).
2. Click the Auto assign button. Position will suggest an assignment to the closest
receiver point for each selected WTU. The suggested assignment shows on the map
as a cyan line linking the WTU with the closest receiver. The chosen receiver is the
closest one whose distance from the WTU is less than the maximum distance
specified in the Position Window Options (page 184) setup.
3. If this suggestion is correct, click the Confirm button. The suggested assignment is
presented in a table showing the current assignment and the suggested one. If this is
suitable click OK, otherwise click Cancel.
If you choose to confirm, the assignment is sent to the server.
194
Position
Auto-assignment based on GPS positions and geometry correction > Auto-assignment of WTUs to receiver
points
For a selected line

1. Select a line by clicking on it with the Select tool (see Pointing tools on
page 153).
2. Click the Auto assign button. For every WTU, Position will suggest to assign each
WTU to the closest receiver point in the selected Line whose distance from the WTU
is less than the maximum distance specified in the Position Window Options
(page 184) menu. The suggested assignment shows on the map as a cyan line
linking the WTU with the closest receiver point.
3. If this suggestion is correct, click the Confirm button. The suggested assignment is
presented in a table showing the current assignment and the suggested one. If this is
suitable click OK, otherwise click Cancel.
Figure 4-43 Example of aided-assignment on a receiver line

Position
Auto-assignment based on GPS positions and geometry correction > Manual assignment of Field Units to 4
receiver points
Manual assignment of Field Units to receiver points

Field Units can graphically and manually be assigned to receiver points loaded into Position.
This requires that you have loaded SPS files (see Load Receivers on page 158). No
automatic grabbing algorithm is used.
1. Select a group of WTUs with the Select tool (see Pointing tools on page 153).
2. Click on a WTU in the selection and drag it to the receiver point you want to assign
the WTU to. The WTU position pattern is preserved for the assignment, meaning
that if the receivers match the position pattern of the selected WTUs, then all the
selected WTUs will be assigned to the matching receivers.
3. Once the WTUs are assigned to the receiver points, release the mouse button and
click the Confirm button.
4. The suggested assignment is presented in a table in the “Assign Stake IDs” dialogue
in Position, showing the current assignment and the one done manually (see
Change Stake ID’s (manually) on page 173). If this is suitable click OK,
otherwise click Cancel.
196
Position
Auto-assignment based on GPS positions and geometry correction > Automatic checking of WTU assign-
ment to receiver points
Automatic checking of WTU assignment to receiver points

After Automatic checks against input SPS files (page 197), a number of
automatic checks on WTUs are performed, based on the WTU positions and the receiver
point each WTU is assigned to. Every WTU on which a problem is detected shows as a red
square on the map in Position. In some cases it is worth having the prospect map to double-
check.
As a result of that automated checking, all WTUs revealing a problem show in a table
available by selecting Warnings from the View menu in Position. Note that the tick boxes
on the left make it possible to choose which types of automatic checks to do (Wrong line
order, Far from prospect, etc.). You may want to disable one or more types of checks in case
of intricate survey configuration. The changes are immediately visible in the problem table
and in the graphic view.
Figure 4-44 Position Warnings table
There are two types of automatic checks, depending on whether or not you have loaded SPS
files into Position (see Load Receivers on page 158), hence two precision levels:
• Automatic checks against input SPS files (page 197): with SPS files loaded,
the GPS positions collected from harvested WTUs can be compared against the
theoretical locations of receiver points from the SPS files.
• Automatic checks with no SPS input (page 200): less reliable since theoretical
receiver locations are not known to Position.
Automatic checks against input SPS files
Wrong line order — (loaded receivers)

Two WTUs associated with loaded receivers can be reported as having a wrong Line number
order. This means that their GPS positions do not match any receiver points in the Lines (for
example, their positions may have been swapped).

Position
Auto-assignment based on GPS positions and geometry correction > Automatic checking of WTU assign- 4
This problem may be indicative of a WTU assigned to a wrong receiver point, or WTU
marking performed in reverse Line number order with the PFT.
The example below describes this situation. The WTUs assigned to receiver points 190:110
and 190:109 have been “swapped” (the vector direction between those receiver points is
inverted compared to the vector direction between the two WTUs). The problem is reported
with two rows in the Warnings table: one for each WTU revealing a wrong Line number
order.
Figure 4-45 Wrong Line order
The message in the Warnings table reads “Wrong line order with XXX” where XXX is the
identifier of the WTU that reveals a problem associated with the previous or next receiver
point.
The following mathematical checks are performed:
For each receiver which has a WTU assigned to it in the Line, in increasing point order:
• Rec1 is a Receiver Point, Rec2 is the next Receiver Point, in increasing Receiver Point
order.
• WTU1 is the WTU assigned to Rec1, WTU2 is the WTU assigned to Rec2.
• Compute U, the vector linking Rec1 and Rec2.
• Compute V, the vector linking WTU1 and WTU2.
• If the scalar product U.V is negative, WTU1 and WTU2 are reported in “Wrong line
order”.
GPS position is far from associated receiver

The GPS position of this WTU is far from the theoretical receiver point it is assigned to. This
may be indicative of a misplaced WTU, or QC age too old.
198
Position
This problem is detected only on WTUs assigned to receiver points loaded into Position. It
is raised if the distance between the WTU position and its theoretical receiver point exceeds
a critical value. To set that maximum distance, select Options… from the Settings menu.
The message in the Warnings table reads: “GPS position is XXX away from associated
receiver”. XXX depends on the maximum distance specified in the Options setup.
For example, in Figure 4-46 below, WTU 1427 is 67 metres away from its associated
receiver point (170:107). This is more than the maximum distance specified in Options setup
(15 metres). The WTU is displayed in the Warnings table. If you click on its row in the table,
the WTU shows in red at the centre of the map and is selected. A straight line is drawn
between the WTU and its associated receiver point.
Figure 4-46 WTU far from associated receiver

Position
Automatic checks with no SPS input
GPS position is far from prospect

The GPS position of this WTU is far from the average position of all the WTUs known to
Position. This may be indicative of an invalid GPS position.
This problem can be detected on any WTU, with or without any assigned receiver. Only the
GPS position is used to perform this check.
The message in the Warnings table reads: “GPS position far from prospect”, followed by the
WTU GPS coordinates.
The following mathematical checks are performed:
• Compute the average AX and AY of the WTU positions.
• Compute the standard deviation SX and SY of WTU positions from AX and AY.
• Any WTU whose X position is > 3*SX or Y position is > 3*SY is reported as “far from
prospect”. The purpose of this test is to find aberrant positions, based on the relative
positions of WTUs and on the 3-sigma rule (normally applicable in the case of a Gaussian
distribution). Although in the case of a seismic prospect a Gaussian distribution is not
relevant, field trials revealed that the 3-sigma rule makes it possible to discard a
reasonable amount of erroneous points (in a Gaussian distribution, 99.xxx% of
observations are within ±3 standard deviations, and any observation that does not lie
within three standard deviations is regarded as aberrant).
Wrong line order — WTUs assigned to receivers not loaded

This alert is raised if the GPS positions of the WTUs in a same Line do not progress in the
same direction, as in Figure 4-47 below.
Figure 4-47 Wrong Line order
In this example, the position of the WTU assigned to receiver point 116:153 does not
progress in the expected Line order (the position goes “backwards” relative to the others).
This kind of configuration is reported in the Warnings table.
This type of check is only performed on WTUs that are assigned to receivers which have not
been loaded into Position. Only the GPS positions of harvested WTUs are known (theoretical
receiver positions are not known). Checks with loaded receivers (Automatic checks
200
Position
against input SPS files on page 197) are more reliable since Position knows the
receiver positions.
This problem may be indicative of a wrong WTU position or a WTU assigned to the wrong
receiver on the Line.
The message in the Warnings table reads: “Wrong line order with XXX and YYY.” where XXX
and YYY are the identifiers of the two preceding WTUs in the Line.
The following mathematical checks are performed, for each WTU assigned to the same Line,
in increasing Receiver Point order:
• WTU1 is a WTU, WTU2 is the next one in increasing Receiver Point order, WTU3 is the
next one.
• Compute U, the vector linking WTU1 and WTU2.
• Compute V, the vector linking WTU2 and WTU3.
• If the scalar product U.V is negative, WTU3 is reported in “Wrong line order”.
Double Association
If two WTUs are assigned to the same Receiver Point, two rows are present in the Warnings
table, one for each WTU assigned to that Receiver Point.
If you click on any of these rows in the Warnings table, the map is resized to show the two
WTUs and the common receiver point. The WTU corresponding to the clicked row is
selected.

Position
Figure 4-48 Double association
This check is performed on WTUs assigned to receiver points, regardless of whether or not
those receiver points are loaded into Position. Only the stake ID mapping is used for that test.
The message in the Warnings table reads: “Associated to the same receiver than WTU XXX”
where XXX is the identifier of the other WTU assigned to the common receiver point.
202
Position
Auto-assignment based on GPS positions and geometry correction > State of Health (SoH) Warnings
State of Health (SoH) Warnings
Figure 4-49 SoH Warnings
• Sensor Error: Indicates error if the sensor resistance and tilt statuses and packet error
rate.
• Field Unit Error: Indicates if there is an error concerning the built-in-tests.
• Low Battery: Indicates error concerning the internal and external batteries.
• Low Memory: Indicates error if the memory is full.
• GPS Time Lock: Indicates if there is an error concerning the GPS lock and radio sync
statuses.
• Noise: Indicates if the noise level is above the programmed threshold.
• Outdated: Indicates if the time elapsed since the last SoH Data has surpassed the time
limits.

Chapter
5 TraceView
This chapter gives the user a description of the TraceView

Application

• The Menu Bar (page 206)
• Options Menu (page 210)
• Notes (page 216)

TraceView
Overview >
Overview
The TraceView application lets you visualize data gathered by the DCM system and can be
run either as a standalone application or together with the DCM server network.
When run with the DCM server in acquisition mode, TraceView will automatically update
the trace display with the latest generated SEG-D file. SEG-D format 1.0, 2.1 and 3.0 are
supported by TraceView.
Figure 5-1 TraceView
Note TraceView provides also the ability to plot data using a Isys V12 plotter
configured as a printer. See 508XT Installation Manual for the detailed
procedure to install the specific driver and configure the plotter.

TraceView
The Menu Bar > File 5
The Menu Bar

This section describes the menus and their usage. The menu options are accessed by left-
clicking on the main menu items on the menu bar to access the drop-down menus.
In this section:
• File (page 206)
• View (page 207)
• Help (page 209)
File
Open
Select to open a SEG-Y or SEG-D compliant file containing acquisition data. TraceView will
open files generated by the DCM system, and other SEG-Y revision 0 or SEG-D revision 1,
2.1 or 3.0 acquisition files.
Shortcut: ctrl+o.
Open next
Select to open the next SEG-Y or SEG-D file in the folder. Files are sorted alphanumerically.
Shortcut: ctrl+PgDn.
Open previous
Select to open the previous SEG-Y or SEG-D file in the folder. Files are sorted
alphanumerically.
Shortcut: ctrl+PgUp.
Print
Selecting this option will cause the traces to be printed according to the settings in the
TraceView Print dialog (see TraceView Print (page 213)).
Shortcut: ctrl+p.
Print page
Selecting this option will cause the traces to be printed as shown on the TraceViewer display.
Shortcut ctrl+Shift+P.
Properties
This option shows the properties of the SEG-Y or SEG-D file currently loaded including the
text header values.
206
TraceView
The Menu Bar > View
Shortcut: ctrl+r.
Exit
Closes the application
Shortcut: ctrl+q.
View
TraceView
Selecting this option causes TraceView to display the acquisition data as signal traces.
Shortcut: F9.
When in TraceView, the further items on the drop-down menu are as follows:
Zoom in
Increases the zoom level on the view.
Shortcut: ctrl++
The mouse can also be used to zoom in. Move mouse cursor to desired point on the record;
left click, and hold; drag mouse diagonally downwards (left or right) highlighting a specific
area; then release mouse button. TraceView will zoom in to this highlighted area. Repeat if
necessary.
Zoom out
Decreases the zoom level on the view.
Shortcut: ctrl+-.
The mouse can also be used to zoom out. Position mouse cursor anywhere within a
TraceView record; left click and hold; drag mouse diagonally upwards (left or right); release
mouse button. TraceView will reset the zoom back to the original settings.
Reset zoom
Resets the zoom back to the default level
Shortcut: 0.
Options
Opens the Options dialog to change the way the seismic traces are displayed. See Options
Menu (page 210).
Shortcut: ctrl+t.

TraceView
The Menu Bar > View 5
Toolbars
Currently no function in the TraceView.
Spectrum view
Selecting this option causes TraceView to display the acquisition data in form of a spectral
view where the individual channels are overlaid upon each other.
Shortcut: F10.
When in Spectrum view, the further items on the drop-down menu are as follows:
Zoom in
Increases the zoom level on the view.
Shortcut: ctrl++.
Zoom out
Decreases the zoom level on the view.
Shortcut: ctrl+-.
Reset zoom
Resets the zoom back to the default level
Shortcut: 0.
Next Page
Moves the spectral display to the next page of channels. See Options Menu (page 210)
for the definition of channel pages
Shortcut: PgUp.
Previous Page
Moves the spectral display to the previous page of channels.See Options Menu
(page 210) for the definition of channel pages
Shortcut: PgDn.
Next Channel
Select to highlight the spectrum of the next consecutive seismic channel to the one currently
highlighted.
Shortcut: right arrow.
208
TraceView
The Menu Bar > Help
Previous Channel
Select to highlight the spectrum of the previous consecutive seismic channel to the one
currently highlighted.
Shortcut: left arrow.
Options
Opens the Options dialog to change the way the spectral traces are displayed. See Options
Menu (page 210).
Shortcut: ctrl+t.
Toolbars
Opens a further dialog to enable or disable spectral view paging, and spectral view
highlighting.
Help
About
Opens a dialog window showing TraceView application information.

TraceView
Options Menu > 5
Options Menu
The Options dialogue is opened in either TraceView or Spectrum view using the View;
Options menu options, and is used to configure the following:
• How seismic traces are displayed in TraceView.
• How seismic traces are printed if the Print menu option is used.
• How the spectrum of seismic data are presented in Spectrum View.
There are three pages on the Options dialogue, one for each of the groups of settings listed
above, and navigation between them is achieved by selecting the appropriate page tab.
• TraceView page (page 210)
• TraceView Print (page 213)
• Spectrum View (page 215)
TraceView page
Figure 5-2 Options dialog - TraceView page
210
TraceView
Options Menu > TraceView page
X Spacing
The distance in pixels between the centre line of each trace.
Scale
A scaling factor that is applied to the samples in each trace. A value greater than 100% will
cause adjacent traces to overlap.
Trace clip
Maximum positive or negative trace width defined as multiples of X Spacing.
Fill Type
Trace drawing options. The Wiggle Trace option draws a line between sample points. The
Variable Area option colours in areas to the right of the centre line. The Variable Area Wiggle
Trace option draws the line and the fill-in areas.
X Axis Labels
X Axis Labelling Options. TraceView can either display Receiver Line and Station numbers
above the X Axis or Channel numbers.
Trace Order
Enables or disables the tool tip that shows information on the trace and sample under the
mouse pointer.
• SEG-D file order
Traces are ordered using the default order of the SEG-D file
• Original SPS order
Traces are ordered using the "Index within acquisition" field of "Sercel Trace Identification"
block
• Topology order
Traces are ordered by topology
For topology order, in shot domain, the following criteria are used to distinguish traces:
1. Receiver topology (line, point and index), from "Trace Header Extension #1"
2. Group index, from "Trace Header Extension #1"
3. Sensor SEG-D code, from "Trace Header Extension #1"
4. Channel number, from "SERCEL Trace Identification Block"
5. Default trace order in the SEG-D file

TraceView
Options Menu > TraceView page 5
Show Value Tool Tip

Enables or disables the tool tip that shows information on the trace and sample under the
mouse pointer.
Gain Type
Selects the gain algorithm to be applied to the samples in each trace. These are described as:
• Equalised Gain.
The peak values of each trace are scaled up to the trace width.
• Automatic Gain Control (AGC).
Samples are RMS normalised within a rolling window. AGC Window Size defines the size
of this window in milliseconds.
• Fixed Gain.
All samples are scaled relative to the Trace Limit (mV) that represents that offset from the
zero point to the edge of the trace. All traces are scaled by the same amount.
212
TraceView
Options Menu > TraceView Print
TraceView Print
Figure 5-3 Options dialog - TraceView Print
This group of options allow you to configure which traces and samples are printed.
Print All Traces

All traces will be printed on one continuous plot. The time range will be the complete listen
time.
Print range of traces or samples

Selecting this option will allow you to define a range of channels and/or samples to print.

TraceView
Options Menu > TraceView Print 5
Headings
A header is printed at the start of every print which displays information regarding the
acquisition. It is possible to customise two text fields in the header.
Title
The Title is displayed in the top left of the header in large sized text.
Subtitle
The Subtitle is displayed in the top left of the header, just below the Title and in slightly
smaller sized text.
Trace Spacing
This option lets you define the actual space between traces on the plot. Values can be entered
in either mm or inches. Changing the units will automatically convert the spacing to the new
units.
Printer
Select the printer to be used.
“Sercel-V12” appears in the list of available printers if you have installed the specific driver
for Isys V12 Plotter. See 508XT Installation manual for detailed instructions.
214
TraceView
Options Menu > Spectrum View
Spectrum View
Figure 5-4 Options dialog - Spectrum View
Channels Per Page

The number of channels that will be displayed, per page, on the spectrum view.
Y Minimum
Sets the minimum value (in decibels) that will be displayed on the y axis.
Show Spectrum Harmonics

Spectrum Harmonics are vertical lines that follow the mouse pointer as it is moved across the
spectrum view. A vertical line is drawn at the mouse position, and at frequency values that
are multiples of the mouse position.
Use the check box to enable and disable the display of Spectrum Harmonics.

TraceView
Options Menu > Notes 5
Show Value Tool Tip

Enables or disables the tool tip that shows the frequency and magnitude of the current mouse
position.
Windowing Algorithm
TraceView provides a number of standard windowing algorithms that can be applied to the
raw sample data before the Fast Fourier Transform is applied to translate the sample data into
the frequency domain.
The following algorithms can be applied:
• Rectangle - no windowing algorithm is applied, raw data is used.
• Bartlett.
• Blackman Harris.
• Blackman Harris 70dB.
• Blackman Harris 7 Term.
• Hamming.
• Hanning.
Notes
For Microseismic files TraceView will calculate and remove the DC offset, for display
purposes only. SEG-D files will not be affected.
DC offset removal can be disabled by adding the command line parameter --noDcRemoval
to the TraceView shortcut.
216
5 TraceView
Options Menu >
217
Chapter
6 Export
This chapter describes the Export window.

It includes the following sections:

• Edit Menu (page 222)
• Actions Menu (page 227)
• In queue view (page 235)
• Export Results (page 239)

Export
Overview >
Overview
The DCM system automatically saves its shot files to a SEG-D repository on its server
computer’s disk (In queue). The Export main window is dedicated to the process of
exporting them from the SEG-D repository to your archiving media: disks drives (NAS),
FTP repositories or Local folders (on Server).
A file is not deleted from the SEG-D repository until its has been exported successfully. The
activity of each type of medium is logged in a separate view (LOCAL, NAS, FTP).
To open the Export main window, click on the Tools menu in Data Completion Manager then
select the Open Export Application button or select Tools --> Open Export.
Open Export
Figure 6-1 Export window interface

Export
Overview > Export Controls 6
Export Controls
Exporting to devices can be activated / de-activated using the Export ON / OFF buttons on
the action bar on the lower right hand side of the Interface.
Figure 6-2 Export ON / OFF
Exporting to Devices
If Export is ON any SEG-D files that are In queue will be exported to the selected devices.
Otherwise the SEG-D files will remain in stand-by until Export is enabled.
The available export devices are prompted in the “Export Options Available Devices” box.
• A removable disk (NAS) is ready if it is “mounted”.
• An FTP server is ready if connection to it is successful.
• A Local drive is available if it is defined.
Figure 6-3 Export Options
220
Export
Overview > Device Control Board
Device Control Board

The Device Control Board shows the status of each device to which the shot files can be
exported.
An indicator light is associated with each export device to indicate its current state:
• Red: device not mounted (NAS connection) or not accessible (FTP connection, Local).
The indicator turns red if the removable disk is unmounted or the FTP/Local connection
is closed:
- manually by the operator,
- or automatically, because of a problem on the network.
• Orange: device mounted (NAS connection) or accessible (FTP connection or Local).
Green: device mounted (NAS connection) or accessible (FTP connection or Local), and
writing to that device is in progress or enabled.
Figure 6-4 Device Control Board
The Device Control Board is also used for local controls of mounting/unmounting NAS
disks, making an FTP connection, and for Local storage.

Export
Edit Menu > Disk Record Setup 6
Edit Menu
Figure 6-5 Edit Menu
Disk Record Setup

The Disk Record Setup window lets you choose the way the system will store SEG-D files in
your export device.
Figure 6-6 Disk Record Setup
222
Export
Edit Menu > Disk Record Setup
The files can be arranged in three different manners:

• Flat: all files are saved to the same directory. Production files are directly saved to /
<remotedir>/ and test files to /<remotedir>/test.
• Swath Name: a distinct subdirectory for each swath. Production files are recorded to /
<remotedir>/<swath>/<groupname<index>>. Test files are recorded to /<remotedir>/
test.
Use this option to prevent different swaths from being recorded on the same export set
and therefore mixed.
• Swath Name and Julian Day: same as with the “Swath name” option, but for each
swath, a subdirectory is created for each julian day. Production files are recorded to /
<remotedir>/<swath>/<julian>/<groupname<index>>. Test files are recorded to /
<remotedir>/test.

Export
Edit Menu > Export Parameters 6
Export Parameters
Figure 6-7 Export Sets Management
Export Sets
If you are shooting multiple swaths, you may want to create a distinct Tape Set (a set of tape
numbers) for each swath. This allows exporting the different swaths to distinct directories on
NAS disks.
The “Name” field contains the identification number of each Export Set. Each Export Set
consists of the Index numbers ranging from the value specified in the associated “1st Index”
field to that specified in the “Last Index” field.
The Swathes setup allows you to select which Export Set to associate with which swath.
Name
(16 ASCII characters max.). Used to enter a user-friendly name for the export set.
Group Name
Export set identifier.
224
Export
Edit Menu > Export Parameters
1st (First) Index

Specify the lowest index number in the Export set.
Last Index
Specify the highest index number in the Export set.
Current Index
(Allowable range: 0 to 9999).
Files Count
(Allowable range: 1 to 100000). Allows you to specify the number of SEG-D files recorded
for each Index.
First index, last index and file count fields determine how many SEG-D files can be recorded
using this export set. Be sure the size is consistent with the amount of production files
expected and the number of files per index. If you generate more files than planned in the
Index Set, export will stop and a warning message will be displayed in the Status Mail view.

Export
Edit Menu > Preferences 6
Preferences
Figure 6-8
The Preferences menu makes it possible to customize Export interface on each DCM Client.
General --> Communication

• Refresh delay: sets the rate at which Export views are updated with new incoming data.
Appearance --> Format

• Select your preferred format for a Short Date, a Long Date and for Time.
226
Export
Actions Menu > Add a New Export Device
Actions Menu
Figure 6-9 Actions menu
Add a New Export Device

The Export interface allows you to create one or several export device types. The supported
export device types include:
• NAS disks
• FTP repositories
• LOCAL folders

Export
Actions Menu > Add a New Export Device 6
1. In the Actions menu, select Add a New Export Device. The New Device Creation
screen is displayed. Click on the export device you want to add.
Figure 6-10
228
Export
Add a NAS Export Device
Figure 6-11
After connecting an external disk, to Add a new NAS export device,

1. Enter the Device name.
2. Enter the IP address of the disk on the local network.
The following IP addresses are allowed:
• 172.27.128.41
• 172.27.128.42
• 172.27.128.43
• 172.27.128.44
3. Enter the directory path to which to save your SEG-D files on the disk.
4. Select the Transfer Mode (UDP or TCP).

Export
5. Specify the dick monitoring options for the NAS device.

6. Click on the OK button.
7. Click the Mount button to activate the NAS device.
The Mount (Unmount) button attaches (detaches) the specified remote directory to (from)
the file hierarchy of the server computer at a mount point automatically determined by the
system.
Note Prior to removing a disk, click on the associated Unmount button. Disks cannot
be unmounted while a file is being written.
Local network (172.27.128.x.)
Observer NAS
server
DCM server 172.27.128.41

GUI
172.27.128.100
172.27.128.2
Figure 6-12
Edit a NAS Device

The NAS devices are removable but cannot be unmounted while a file is being written.
Use the Edit Device window to enter/edit the IP address and directory of your NAS device.
Click on the NAS device type to open the window.
This setup window allows you to specify the IP address of each external disk attached to the
system, and the directory to which to save your SEG-D files.
You may also modify the disk monitoring options concerning available disk space.
230
Export
Add an FTP export Device
Figure 6-13
The FTP Server details can be opened by double-clicking on the FTP device type of the
Device control board.
1. Select FTP from the Create New Device dialog.
2. In the IP Address field, specify the IP address for the machine on which FTP server
software (e. g. FileZilla supplied) is running.
3. In the Remote directory field, enter the name of the directory to which the records
will be saved on the FTP server machine.
4. In the User and Password fields, enter the user name and password (the user
account) that the FTP user will use to connect to the FTP server. This assumes that
the same user account is created on the FTP server machine
5. Click on the OK button.

Export
6. Click the Connect button to activate the FTP connection.
(172.27.128.x)
DCM Server
FileZilla
Figure 6-14
Add a LOCAL export folder
Figure 6-15
1. Select LOCAL from the Create New Device.

2. In the Device name field, enter a user-friendly name for the device.
3. In the Remote directory field, enter the name of the folder to which the records will
be saved on the local machine.
232
Export
Actions Menu > Clear Export Results
4. Click the OK button.

5. Click Connect button
Clear Export Results

This command allows you to clear all exported results.
Copy SEG-D files

The Copy SEG-D files to function allows you to copy an SEG-D file from a NAS disk to
another disk or to a NAS drive.
Note This function is available for files that have already been exported.
1. In the Actions menu, select Copy SEG-D files...
Figure 6-16

Export
Actions Menu > Copy SEG-D files 6
2. The Copy SEG-D files options dialog is displayed.
Figure 6-17
If any NAS disk is “mounted” and/or any FTP or local disk is connected, it appears in the
“Destination Devices” list box.
3. Choose the device from which to read by clicking on it in the Source Devices list
box, and then move it to the Destination Devices list box by double-clicking.
4. Use the Browse button to open the folder containing the file you want to copy and
select it.
The record number of the file you are reading is displayed in the relevant activity log view.
234
Export
In queue view > Copy SEG-D files
In queue view
The In queue view lists SEG-D files that have been processed but not yet exported. Files
remain in this state until the Export On is enabled.
Figure 6-18 In queue view
Right-Click on a line in the In queue view allows the following actions:

• Display SEG-D files in TraceView (page 236)
• Copy SEG-D files to (page 237)
• Delete SEG-D files (page 238)
• Download SEG-D files (page 238)
Figure 6-19 In queu action menu

Export
In queue view > Display SEG-D files in TraceView 6
Display SEG-D files in TraceView

The Display SEG-D files in TraceView function allows you open the TraceView application
on the client computer and open a temporary copy of the SEG-D file that has not yet been
exported yet.
Figure 6-20 Display SEG-D in TraceView
236
Export
In queue view > Copy SEG-D files to
Copy SEG-D files to

The Copy SEG-D files to function allows you to copy a SEG-D file that has not yet been
exported to a local disk. This function is only available for SEG-D files In queue.
1. In the In queue section, select one or several lines, then right-click to display the
contextual action menu.
2. Select Copy SEG-D files to...
3. The Copy SEG-D files options dialog is displayed.
Figure 6-21 Copy SEG-D files to
4. Select the Source and Destination device.

5. Use the Browse button and select the one or several SEG-D files with CTRL key and
click Open.
6. Click Copy.

Export
In queue view > Delete SEG-D files 6
Delete SEG-D files

This function will delete the selected SEG-D files from the queue list. To be used carefully
as you can delete seismic data from server disk.
Download SEG-D files

The Download SEG-D files option allows you to download selected files that are processed
but not yet Exported to a local disk or (USB device storage).
Figure 6-22 Download SEG-D files
1. In the In queue section, right click on the SEG-D file to copy.

2. Select Download SEG-D files.
3. Use the Browse button to indicate the destination folder.
4. Click Download.
238
Export
Export Results > Download SEG-D files
Export Results
The Export Results tab allows you to open a separate view for each type of export target
(NAS, FTP, LOCAL), showing a table in which the activity of the export results are logged.
Figure 6-23 Local Export Results View
Figure 6-24 FTP Export Results View
For details on how you can arrange the views and toolbars as you would like them, see the
Customizing windows on page 27 section. You can move and resize columns in tables
by right-clicking in any column heading and selecting Customize (see Figure 2-12).
Export File Name

Indicates the name of the exported SEG-D file.

Export
Export Results > Download SEG-D files 6
Swath Id
Identification number of the swath (parameter from the Operation window).
Device Name
Name of the Device assigned by the Export process to the export target.
File Number
Identification number of each SEG-D file written to the Removable disk, FTP server, or
Local folder.
Remote Folder
Directory to which SEG-D files are exported.
Export Duration Time

Date and Time when the SEG-D file has been exported to the export device (NAS disk, FTP
server or Local folder).
Size
Size (in MiB) of the exported SEG-D file.
Throughput
Throughput (MiB/s) to write the file on the export device.
Export Error
Indicates whether or not the SEG-D file was recorded successfully.
Export Error Message

If an error occurred when recording the SEG-D file, this field contains the error message
generated by the export device.
240
6 Export
Export Results > Download SEG-D files
241
Chapter
7 SEG-D File Generator

(SEG-D Gen)
This chapter includes the following information,

• Quick Start (page 244)
• SEG-D Gen tool (page 249)
• Event Definition Text File format (page 259)
• Example of event definition text file (page 264)
• Recorder Free Mode (page 265)

SEG-D File Generator (SEG-D Gen)
Overview >
Overview
The Standalone DCM server configuration does not require a 508XT. Instead it relies on the
SegdGen tool to manage shots. This way of managing shots is typically suitable for:
• Microseismic surveys, and more generally for any shooting mode where the sources are
not controlled by the seismic acquisition system (independent source shooting) — the
seismic data is retrieved on the basis of the Time Breaks recorded by the source
controllers. See Recorder free Impulsive Operations (page 266)
SegdGen makes it possible to choose from the following three options to create shot files:
• Time range: DCM creates continuous events, starting from the specified Start Time. The
timebreak for each new event is determined from the Record Length specified in the
Acquisition Parameters tab. Events stop being created when the timebreak hits the
specified End Time.
• Real Time: same as Time Range, with events triggered by the system clock.
• Text File: DCM creates events from a text file containing shot parameters. See Event
Definition Text File format (page 259)
• Boombox File: DCM creates events from Boom Box® shooting system output file.
In the most basic case all that is required to be defined in the text file is a GPS timebreak.
Further optional fields can be added to the text file to define options like the source point,
stacking, correlation and noise edition. The text file can define multiple events.

Quick Start > 7
Quick Start
1. Install DCM Client software on a Linux computer (this installs SegdGen on the
computer).
Note SegdGen should preferably be run on the Linux machine hosting the DCM
Server so that the SEG-D files it produces can be automatically imported into
the server from the
/var/dump/.dcm/import folder.
2. Launch the SegdGen tool, located in this folder:
/export/home/userdcm/Sercel/dcm/native/linuxV2_6_32A64
3. Choose the appropriate Generation Type option:
• Time Range (page 250) or Real Time (page 250): set the
Start time and End time. You can keep the Start µs field to the
default value (0) or enter the micro-second part of the TB time if
required.
• Text File: select the text file to load (to create a text file, see
Event Definition Text File format (page 259).
• Boom Box File: select the file to load (see Recorder free
Impulsive Operations (page 266)
244
Quick Start >
Figure 7-1 Event definition file example
• The text file typically includes the GPS TIMESTAMP and PROCESS TYPE fields, and
SRC LINE / SRC STATION number fields (corresponding to SPL / SPN in an SPS Source
file). In the above example, we have three Impulsive Stack shots (source line 501, source
points149, 150 and 151), with 8 acquisitions per shot.

Quick Start > 7
Figure 7-2 Loading an event definition text file
• The Headers tab is automatically populated with information from

eventDefinitionFile.txt file you are loading.
• The output path should be: /var/dump/.dcm/import. (To populate the VP Table view, the
system will look for SEG-D files in this folder).
4. Click on the Spread tab. Select From SPS from the Spread Setup button, and choose
the corresponding sps.s file.
• Note that three SPS files (r, s, x) must be present in the same folder (with .r, .s, .x as
extensions). Both SPS v1.0 and SPS v2.1 standards are supported.
• Do not tick the Generate test data option.
246
Quick Start >
Figure 7-3
• Note that fields not defined in the text file use the appropriate setting from the
Acquisition Parameters and Spread tabs.
5. Back to the Generation tab, click Start. The system sorts the event definitions by
timebreak, creates events based on the definitions, and searches for the
corresponding spread in the SPS file.
In the example below, the active spread has 476 channels.

Quick Start > 7
Figure 7-4
6. The VP Table view in DCM has one row for each shot, populated with the
Timebreak, the total number of acquisitions (sweeps 1/1 in this example), the Source
Line and Source Point Numbers.
Figure 7-5
7. Data can now be harvested as normal (go to On Line with Export to produce the
final SEG-D files).
248
SEG-D Gen tool > SEG-D Generation Tool window
SEG-D Gen tool

In this section:
• SEG-D Generation Tool window (page 249)
• Generation tab (page 249)
• Acquisition parameters tab (page 252)
• Spread tab (page 254)
• Headers tab (page 257)
SEG-D Generation Tool window

To launch the SEG-D Gen tool, double-click on the segdgen file located in this folder: /
export/home/userdcm/Sercel/dcm1.0/native/linuxV2_6_32A64
Generation tab
Figure 7-6

SEG-D Gen tool > Generation tab 7
Time Range
Shot files will be generated starting from the specified Start time (and Start µs).
• The timebreak for each new event is determined from the Record
Length specified in the Acquisition Parameters tab. Events will
stop being created when the timebreak hits the specified End time.
• Clicking Start generates the shot files immediately. Note that the
Shortcuts buttons make it possible to step through the calendar (±
1 year, day, hour, minute, second, etc).
Real Time
Events are triggered by the system clock.
• If the system clock time is earlier than the specified Start time,
then the first event will not be created until the system time hits the
Start time.
• If the current system clock time lies somewhere between the
specified Start time and End time, all events from the Start time to
the current system time are immediately created (same as Time
Range).
• Then new events are created when the system time hits the time-
break time determined from the Record Length.
• Events will stop being created when the system time hits the
specified End time.
250
SEG-D Gen tool > Generation tab
SPS input in Time Range and Real Time modes

The Time Range and Real Time modes are intended for continuous acquisition, which does
not need any source, typically in Microseismic operations. Still, in these modes, SEGDGEN
does not keep you from using input SPS files with source point entries in them. SEGDGEN
works differently depending on whether the input SPS-S file has only one or multiple source
points:
• If a single source point is specified in the input SPS files (a single
entry in SPS-S), this source point is repeated for each event
generated (same Source Point Line, Source Point Number, Source
Point Index for each event, and these fields cannot be edited in
SEGDGEN in these modes).
• If two or more source points are described in the SPS-S file,
SEGDGEN generates an event for each of them and stops when it
reaches the end of the list, even if the requested time range and
Acquisition Length would allow more events to be generated.
Text File
Shot files will be generated based on definitions from an event definition text file.
Figure 7-7
• Text File: select the text file containing the shot parameters (the event definition text file
to use to create SEG-D files from).To create a text file, see Event Definition Text File
format (page 259)). Fields not specified in the event definition file will be populated as
specified in the Acquisition Parameters and Headers tabs.
• Select the Output Path (/var/dump/.dcm/import).

SEG-D Gen tool > Acquisition parameters tab 7
• Clicking Start generates the events (shot files) described in the text file (one event for
each text line).
Output Path
The folder where to create the SEG-D files. For the VP Table view to be populated, the SEG-
D files must be saved to this folder: /var/dump/.dcm/import.
Note that in case of naming conflict, no file will be generated.
Boombox File
Shot files will be generated based on Boom Box® shooting system output file.
Acquisition parameters tab
Figure 7-8
Sample Period
(500, 1000, 2000, 4000 µs). The sampling interval to be used on all channels.
Gain
The channel preamplifier gain (0, 12 dB).
Filter
(Linear/Minimum). Each acquisition channel has a built-in Digital Signal Processor that
performs high-cut filtering, depending on this filter option.
The available filters have a –3 dB point at 0.8 times the Nyquist Frequency (the Nyquist
Frequency is half the sampling frequency), i.e. 0.4 times the sampling frequency:
- 100 Hz @ 4-ms.
252
SEG-D Gen tool > Acquisition parameters tab
- 200 Hz @ 2-ms.
- 400 Hz @ 1-ms.
- 800 Hz @ 0.5-ms.
- 1600 Hz @ 0.25-ms.
They feature a slope of about 370 dB/octave. The pulse response ringing, however, decays
slowly.
The attenuation is at least 120 dB for all frequencies above the Nyquist Frequency,
preventing any aliasing effect.
The DCM system allows the user to choose between:
- linear-phase type or
- minimum-phase type.
The amplitude spectrum does not depend much on the type of filter (linear or minimum
phase), unlike the phase spectrum.
• Linear Phase: this type of filter is ideal as far as phase considerations are concerned, as
all the frequencies are delayed by the same amount. That delay is set to zero in the DCM.
In return, this kind of filter has a pulse response with leading ringing (“precursors”) as
well as lagging ringing (actually, the pulse response is symmetrical with respect to time
0).
• Minimum Phase: the minimum phase type is causal, i.e. its pulse response, much like
analog filters, starts at time 0, peaks and then rings (no ringing prior to the peak).
The delay, however, somewhat depends on the input frequency.
Record Length
The length of time (seconds) that the data is recorded for each shot.
Microseismic
This option is intended for a permanent acquisition from a fixed spread. The continuous
acquisition consists of consecutive shots with zero dead-time. No sample is lost between the
last sample in a shot and the first sample in the next one. The File Number is incremented for
each shot. The Point Index and Shot Number are not incremented.

SEG-D Gen tool > Spread tab 7
Spread tab
Figure 7-9
Spread Setup
• Single static line: you specify a Number of Seismic channels, and then every SEG-D
file will have this number of seismic channels. The channels will all be on Line 1, and
their point numbers will start from 1.
• From SPS: the spread is based on SPS Source, Receiver and Relation files provided. The
corresponding spread is used according to the Source Line and Source Station of each
SEG-D file generated.
Use the browse button (...) to select an SPS Source file. Three SPS files (r, s, x) must be
present in the same folder (with .r, .s, .x as extensions).
254
SEG-D Gen tool > Spread tab
Number auxiliaries
The number of auxiliary channels to add to the SEG-D files. Note that in case of dump files
for correlation process types, an additional auxiliary channel which the autocorrelation of the
correlation pilot will be automatically added to the dump file. In this case the raw files will
have N aux channels, and the dump file will have N+1.
Number of receivers
The number of seismic channels.
Sensor Code
The electrical characteristics of sensors are not necessarily the same across the entire spread.
Use this table to create a Sensor code ID for each type of sensor and apply the appropriate
resistance, tilt (pulse response) and noise test limits to each Sensor Code ID.
Figure 7-10
Point Code
This table is used to create the required Point Codes. At each receiver point, the Point Code
ID # is an attribute that determines how many channels are expected at this receiver point
and which type of sensor to use for each channel (i. e the sensor test limits to apply).
For example, assigning a Point Code defined as Sensor Code 1+2+3 (Figure 7-10) to a
receiver point will apply Sensor Code 1 to the first channel at this receiver point, Sensor
Code 2 to the second channel, and Sensor Code 3 to the third channel.
• SPS mode: if the Spread Setup option is set to From SPS, then the Point Code specified
in the SPS files determines which Point Code to use from the table, which itself
determines the number of channels at each receiver point, the sensor SEG-D code and the
sensor test limits in the SEG-D file generated by SEGDGEN. Naturally, you must make

SEG-D Gen tool > Spread tab 7
sure to create the appropriate Point Code ID in the table to match the Point Code from the
SPS files.
• Forced point code option:
- If the Spread Setup option is set to Single static line, the Forced point code
button allows you to specify which Point Code to pick up in the table to determine
the number of channels at each receiver point, the sensor SEG-D code and the
sensor test limits in the SEG-D file generated by SEGDGEN.
- If the Spread Setup option is set to From SPS, the Forced point code button
allows you to override the Point Code specified in the SPS file, or specify one if
none is found in the SPS files (not recommended — see SPS mode above).
• Text file import mode:
- If you select a Point Code from the table with the Forced point code button, it is
used to determine the number of channels at each receiver point, the sensor SEG-
D code and the sensor test limits in the SEG-D file generated by SEGDGEN,
regardless of whether From SPS or Single static line is selected.
- Otherwise, use the From SPS option (SPS mode): the Point Code specified in the
SPS files determines which Point Code to use from the table, which itself
determines the number of channels at each receiver point, the sensor SEG-D code
and the sensor test limits in the SEG-D file generated by SEGDGEN.
Generate test data

For testing purpose only — not for production use! Normally the channels are muted.
Selecting this option will generated synthetic data and instrument serial numbers.
256
SEG-D Gen tool > Headers tab
Headers tab
Figure 7-11
SEG-D revision number

SEGDGEN can generate SEG-D Rev 1, SEG-D Rev 2.1 or SEG-D Rev 3.0 files.
Start FFID
The FFID for the first shot file to generate. FFIDs are then automatically incremented by 1
for each new file generated.
After a file is generated, this field will automatically update to be the next FFID in sequence.
Source Line
The Source Line Number for the first file to generate.
Source Point Number

The Source Point Number for the first file to generate. The Point Number can be incremented
by a configurable amount (the Source Point Increment) for each new file generated.
After a file is generated, this field will automatically update to be the next Source Point
Number in sequence.
Source Point Increment

The increment to apply to the Source Point Number after each new file is generated. Set to 0
to have the same Source Point Number in all files.

SEG-D Gen tool > Headers tab 7
External Header
SEG-D GEN can generate an External Header in the output SEG-D file.
You can choose the size (1 kB or 64 kB), and type the text that you want to be recorded in
the External Header.
258
Event Definition Text File format > Headers tab
Event Definition Text File format

The event definition text file is a standard ASCII file in CSV (comma separated variable)
format. Most of the field definitions have the same description and values as the
corresponding fields in the SEG-D format.
To create the text file, use the following guidelines:
• Lines beginning with # are ignored, as are completely blank lines.
• The first non-ignored line of the file should list the field names to set (headers). In the
Example of event definition text file (page 264) the “DESCRIPTION” field is
ignored by the SEGDGEN tool, and is just present for clarity. The field names can be in
any order.
• The following lines should be the field values, with one line defining one event. The field
values should be in the same order as defined by the field names on the first line.
• There is only one required field — the GPS time-break. Subsequent fields allow more
and more control over the details of the event to create. Fields not defined in the text file
will use the appropriate setting from the SEG-D Generator tool (Acquisition
Parameters and Spread tabs), and from the server where available.
• Files are produced in the order that they are listed in the text file.
• For Stack/Correlation process types, a separate dump file must be specified (and the
dump should have the same GPS TIMESTAMP as the first sweep.
• The TYPE OF DUMP field must be set to 1 for the raw files, and 0 for the final dump.
• The file should be saved with a .txt or .csv file extension.
The field definitions below are split into the following categories:
1. Required — Required fields (GPS Time stamp).
2. File and shot identification — FFID, source line/station etc.
3. Source identification — Source ID/Type.
4. Acquisition parameters — Sample Rate, Gain, Record Length, Process Type etc.
5. Stacking — acquisition number, fold etc.
6. Correlation — correlation pilot, autocorrelation peak, etc.
7. Noise Editing — Type, parameters.
8. Miscellaneous.

Event Definition Text File format > Headers tab 7
Table 7-1 Required Fields
Field Name Description Example

GPS time of acquisition Time Break,
GPS expressed as as the number of
903892995601234
TIMESTAMP microseconds since January 6, 1980 a t0:00
a.m. UTC.
Table 7-2 File and shot identification

FFID File Number for the SEG-D file. 1234
SWATH ID Numeric swath identifier. 1
SRC LINE Source Point Line Number. 10
SRC STATION Source Point Station Number. 67
SRC POINT_INDEX Source Point Index (1-9). 1
Table 7-3 Source identification

SOURCE ID Numeric source identification number. 1
SOURCE TYPE 0 = no source, 1 = Impulsive, 2 = Vibro 1
260
Table 7-4 Acquisition parameters

GAIN Gain in dB (0, 12, 24, 36). 24
Sample period in microseconds (500, 1000, 2000,
SAMPLE PERIOD 2000
4000).
ACQ LENGTH Acquisition length in milliseconds. 10000
RECORD LENGTH Record length in milliseconds. 5000
PILOT LENGTH Pilot length in milliseconds. 5000
SWEEP LENGTH Sweep length in milliseconds. 5000
LISTEN TIME Listen time in milliseconds. 5000
1 = No operation (raw data), 2 = Stack, 3 =
PROCESS TYPE 1
Correlation After stack, 4 = Correlation before stack.
OPERATING MODE 1 = Standard, 2 = Microseismic. 1
Table 7-5 Stacking
Exampl
Field Name Description
e
STACKING FOLD Stacking fold (1-32). 4
Acquisition number within the stack
ACQ NUMBER 3
(1-32).
Should be 1 for final acq in stack.
STACK IS DUMPED 0
0=No, 1=Yes.
Table 7-6 Correlation
Exampl
e
Autocorrelation peak time in
AUTOCORREL PEAK 1000
milliseconds.

Event Definition Text File format > Headers tab 7
Table 7-6 Correlation
Exampl
e
Raw Auxiliary trace number to use as
CORREL TRACE NUMBER the correlation pilot. Must always be set 1
to 1.
Note For text file import, the correlation pilot must always be 1 (i.e. the first aux
channel. The system will automatically add the autocorrelation of aux1 to the
final dumps).
262
Table 7-7 Noise Editing
Exampl
e
Noise elimination type. 1=Off,
NE TYPE 2=Diversity Stack, 3=Historic, 2
4=Enhanced Diversity Stack.
NE LOW TRACE PERCENT Noisy trace percentage (0 to 100%). 3
NE LOW TRACE VALUE Low trace value (0 to 132 dB). 12
Number or windows (Div) / Window
NE WINDOW 1
length (Enhanced Div).
Historic editing type/Overlap.
NE HISTORIC EDITING TYPE 1
1=Zeroing, 2=Clipping.
NE NOISY TRACE PERCENT Noisy trace percentage (0 to 100%). 5
NE HISTORIC RANGE Historic Range (0-36 dB). 12
NE HISTORIC TAPER LENGTH Historic taper length 2's exponent (0-8). 0
NE THRESHOLD HOLDVAR Threshold Hold/Var. 1=Hold, 2=Var. 1
Historic threshold Init value (0 to 132
NE HISTORIC THRESHOLD INIT 12
dB).
NE HISTORIC ZEROING LENGTH Historic zeroing length (1 to 500 ms). 20
Table 7-8 Misc.

Produce a RAW dump for this acquisition.
RAW DUMP 0
0=No RAW dump, 1=Produce RAW dump
TYPE OF DUMP 0= Final dump, 1= RAW file 0
EXT HEADER SIZE 1024 of 65536 (standing for 1 kB or 64 kB). 1024
Contains the text to record in the External Header
(Warning: any comma in the imported text file is
See below
EXT HEADER TEXT interpreted as a separator between fields, so in
(*)
order to prevent any conflict, use «,» in
place of any comma in the External Header text).

Event Definition Text File format > Example of event definition text file 7
Table 7-8 Misc.

UPHOLE TIME 0
BLASTER ID 0
BLASTER STATUS 0
(*) External Header text sample:
#Impulsive with external headers "Sercel, Impulsive"
SP 1:7 Impulsive
,903893100000000,1,7,1801,5000,1,1,1,5000,0,0,0,0,1,0,0,0,1
024,Sercel, Impulsive
Example of event definition text file

An example of an event definition text file is available in the Sercel SEG-D Gen application.
Figure 7-12 SEG-D Gen application
Once the SEG-D gen application is opened. Click ‘Help’ then ‘Example Text File’.
Figure 7-13 Example Text file Generation
264
Recorder Free Mode > General Concept
Recorder Free Mode

In this section:
• General Concept (page 265)
• Recorder free Impulsive Operations (page 266)
• Recorder-free Vibroseis Operations (page 270)
General Concept
“Recorder free mode” makes reference to a field operating mode where the sources are run
independently from the recording unit (at least independently from the DCM central system
software).
The advantage of this mode is to free the DCM system from being paired with a source
controlling system and acquisition sequencer - e.g. 508XT+ VE464 system – and to be run
independently from the field operation as well as being dedicated to what it’s been designed
for (and good at): managing the off-loading of the data and producing final SEG-D outputs
at the end of the completion process.
Moreover DCM offers the expected flexibility that is expected by such a production mode:
• (Re)harvest the data at any time (autonomous field units keep the data locally stored for
very long period of time)
• Replay VPs/SPs multiple times if required to recover from various kind of issues like
wrong spread definition, wrong process type definition, wrong definition of markers, …
• Cut-off data differently by generating new TBs/events and especially from delayed
source information (which is the concept of independent sources that is the object of this
document)

Recorder Free Mode > Recorder free Impulsive Operations 7
Recorder free Impulsive Operations
Figure 7-14
WARNING
On first implementation, “Recorder free” mode with Impulsive Operation is only
available using a Boom Box® shooting system.
1. Shots are taken independently from field operation with a GPS-synced Boom
Box® shot controller system.
During this time, WTUs are recording continuous data in autonomous mode.
2. When shooting is done, the Boom Box® outputs “Shot Descriptor files”
containing TB GPS Time + Other Information.
266
Recorder Free Mode > Recorder free Impulsive Operations
Hereafter is an example of a boom box file (wavelet information is not available for clarity):
Crew,Unit,ID,Line,Station,Time,Status,First Pick(ms),CTB(us),Uphole
Shift(ms),Cap res(ohm),Geo res(ohm),Battery(V),Lat(deg N),Lon(deg
E),Alt(m),Wavelet(Base64)
1,1,105602,1132,5422,2015-06-30
15:40:10.000000,225,0.5,8.0,0,8,0,11.8,41.778365,1.610483,883.8,
1,1,105601,1132,5423,2015-06-30
15:37:40.000000,225,0.5,8.0,0,9,0,12.1,41.777850,1.610311,903.6,
1,1,105600,1132,5424,2015-06-30
15:35:40.000000,225,3.5,8.0,0,8,0,11.9,41.777891,1.609913,914.5,
1,1,105599,1132,5425,2015-06-30
15:33:40.000000,225,0.5,8.0,0,8,0,11.9,41.777567,1.609641,919.4,
1,1,105598,1132,5426,2015-06-30
15:31:40.000000,225,0.5,8.0,0,9,0,11.9,41.778061,1.609054,925.7,
1,1,105597,1132,5427,2015-06-30
15:29:40.000000,225,3.5,8.0,0,8,0,11.9,41.777917,1.608753,923.5,
1,1,105596,1132,5428,2015-06-30
15:27:40.000000,225,3.5,8.0,0,8,0,12.1,41.777863,1.608389,921.4,
1,1,105595,1132,5429,2015-06-30
15:26:10.000000,225,0.5,8.0,0,9,0,12.1,41.777752,1.608070,918.8,
1,1,105594,1132,5430,2015-06-30
15:24:40.000000,225,0.5,8.0,0,8,0,12.1,41.777569,1.607785,913.7,
1,1,105593,1132,5431,2015-06-30
15:23:10.000000,225,0.5,8.0,0,9,0,11.9,41.777744,1.607311,918.3,
1,1,105592,1114,5431,2015-06-30
15:11:40.000000,225,2.0,8.0,0,9,0,12.1,41.772619,1.609529,820.7,
1,1,105591,1114,5430,2015-06-30
15:09:10.000000,225,0.5,8.0,0,8,0,12.1,41.772561,1.609940,822.3,
1,1,105590,1114,5429,2015-06-30
15:06:40.000000,225,0.0,8.0,0,8,0,12.1,41.772692,1.610277,823.6,
1,1,105589,1114,5428,2015-06-30
15:05:10.000000,225,0.5,8.0,0,8,0,12.1,41.772894,1.610594,820.9,

Recorder Free Mode > Recorder free Impulsive Operations 7
1,1,105588,1114,5427,2015-06-30
14:55:40.000000,225,0.5,8.0,0,8,0,12.2,41.774093,1.610475,820.5,
1,1,105587,1114,5426,2015-06-30
14:54:10.000000,225,0.5,8.0,0,9,0,12.2,41.773988,1.610844,819.6,
1,1,105586,1114,5425,2015-06-30
14:52:40.000000,225,0.5,8.0,0,9,0,12.2,41.773896,1.611270,819.5,
1,1,105585,1114,5424,2015-06-30
14:51:10.000000,225,0.5,8.0,0,9,0,12.3,41.773835,1.611670,823.6,
1,1,105584,1114,5423,2015-06-30
14:49:40.000000,225,3.5,8.0,0,9,0,12.3,41.773602,1.612125,824.5,
Crew :
Unit
ID : Fields used by the

Line: Source Line Number system to create the
corresponding events.
Station: Source Point Number
Time: UTC time with format: "yyyy-MM-dd HH:mm:ss.zzzzzz"
Status:
First Pick (ms):
CTB (us):
Uphole Shift (ms):
Cap res (ohm):
Geo res (ohm):
Battery (V):
Lat (deg N):
268
Recorder Free Mode > Recorder free Impulsive Operations
Long (deg E):
Alt (m)
Wavelet(Base64)
3. Open SegdGen, choose Generation Type “Boom Box File” and select the .csv files
outputted from the Boom Boxs® shooting system. Click Start to launch the
generation of events.
• One SEG-D file is generated for each valid entry over all selected files.
• For every input Boom Box file, the user is warned when source line or station 0 is found,
without stopping SEG-D file generation (warning message). In that case, line entry is
skipped.
• SEG-D file generation stops as soon as controller IDs (column “ID” in Boom Box files)
in a file are not sequential (error message). Note that IDs must be not sequential from one
file to another

Recorder Free Mode > Recorder-free Vibroseis Operations 7
4. DCM system imports the SEG-D files generated by SegdGen and creates the
corresponding events in DCM.
5. Use the DataHarvester to get the Timebreaks list. Harvest and upload the data
normally.
Recorder-free Vibroseis Operations

In vibroseis, we will use the same principles & tools i.e. based on SegdGen. We extract shots
information from the source controlling system and we feed SegdGen with the shots details
to produce SEGDs files imported into DCM.
Figure 7-15
• GPS Timebreaks from the Vibroseis system are used to create the events in SegdGen.
• To be able to do the correlation part, a pilot trace to be added into the SEG-D files
produced by SegdGen must be provided.
Supported pilot trace input formats

Event definition text file format now supports the import of a pilot reference file.
Following formats are supported:
• CSV file
• SEG-D file format V1.0 / V2.1/ V3.0
• VE464 custom file
GPS TIMESTAMP, CSV FILENAME, SEGD FILENAME, SEGD TRACE

NUMBER,VE464 FILENAME,
903894994601234,file.csv,file.SEG-D, 1, file.custom
270
Recorder Free Mode > Recorder-free Vibroseis Operations
If we add multi same type files input (5 max), we can add these columns:
CSV FILENAME 2,SEGD FILENAME 2, SEGD TRACE NUMBER 2,VE464

FILENAME 2,
file2.csv,file2.SEG-D, 2,
file2.custom
…
CSV FILENAME 5,SEGD FILENAME 5, SEGD TRACE NUMBER 5,VE464

FILENAME 5
file5.csv,file5.SEG-D, 5,
file5.custom
CSV file format

We consider CSV sampling rate equal to matching parameters. We support only one column
right now and we do not have to define column index for csv.
It is also concern of user to set adapted amplitude (+/-1V is preferred value), no check during
decoding to be more flexible.
Csv separator is comma (‘,’).
Standard SEG-D file format

Standard SEG-D files format V1.0, V2.1 or V3.0 containing pilot trace recorded as auxiliary
channel can be used to specify in SegdGen which pilot to use.
We consider SEG-D sampling rate equal to matching parameters.
VE464 custom file (ASCII samples file format)

The supported ASCII format is based on the “custom sweep” format of the Sercel VE464
system - see VE464 user’s manual section VE464 file formats > Custom Sweep file.
An example is provided in the VE464 documentation:
#IDENTIFIER filename
#COMMENT linear 10s 15-50Hz (optional comment)
0.0000001 TRUE # start taper, QC inhibited

0.0000002 TRUE
- 0.0000001 TRUE
- 0.0000004 TRUE
...
0.99567 FALSE
...
0.0000001 TRUE # end taper, QC inhibited
Figure 7-16 VE464 CustomSweep example
How to use Recorder free mode in Vibroseis

1. Write the event definition text file with support of import pilot sweep (see previous
section Supported pilot trace input formats (page 270)).
Hereafter, an event definition text file example describing one VP with 2 stacks,
correl before, using the file “pilot.SEG-D” as reference for the correlation
272
DESCRIPTION,GPS TIMESTAMP,SRC LINE,SRC STATION,FFID,ACQ

LENGTH,PROCESS TYPE,STACKING FOLD,ACQ NUMBER,RECORD
LENGTH,SWEEP LENGTH,AUTOCORREL PEAK,CORREL TRACE NUMBER,TYPE
OF DUMP,SOURCE TYPE,SEGD FILENAME
RAW1,1150706241000000,1,6,1108,30000,1,2,1,15000,10000,1000
,1,1,2,pilot.SEG-D
RAW2,1150706251000000,1,6,1109,30000,1,2,2,15000,10000,1000
,1,1,2,pilot.SEG-D
DUMP,1150706241000000,1,6,1110,30000,4,2,2,15000,10000,1000
,1,0,2,pilot.SEG-D
2. In SegdGen > Generation tab, choose generation type “Text file” and select the
event definition text file.

3. In SegdGen > Spread tab, Nb of auxiliaries should be 1.
4. Optionally, you can input the SPS files define the Spread in SegdGen.
5. In DCM > Process Type, nothing should be defined.
274
6. Start the generation of events.
SegdGen adds the pilot trace in the SEG-D files generated.

7. Events are
created in DCM
with the
imported pilot
trace in Aux1
with Topo Id
(0,1). Other
channels are
outstanding data
for WTUs.
Pilot trace
Imported in
SegdGen
from file
Outstanding
WTU channels
8. Now harvest the

Oustanding
WTUs normally
and upload the
data.
9. Process the
events completed. DCM server will add the autocorrelation of the pilot automatically
during processing.
So correlated DUMP file will have two auxiliary channels:
• Aux1 (topo 0,1) for pilot
• Aux2 (topo 0,2) for autocorrelation
276
7 SEG-D File Generator (SEG-D Gen)
277
Chapter
8
and Restrictions
SEG-D Import Key Points
This chapter includes the follwong information,
• DCM compatibility with various revisions of the SEG-D

format (page 279)
• Importing Rev. 1 & 2.1 SEG-D files (page 280)
• Importing 508XT Rev. 3 SEG-D files (page 281)
• Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1
(page 283)

DCM compatibility with various revisions of the SEG-D format >
DCM compatibility with various revisions of the SEG-D for-

mat
DCM is able to import:
• Sercel SEG-D revision 1.0
• Sercel SEG-D revision 2.1
• Sercel SEG-D revision 3.0 (shot domain)
DCM is able to output:

• Sercel DCM SEG-D revision 1.0
• Sercel DCM SEG-D revision 2.1
• Sercel DCM SEG-D revision 3.0 (shot domain)
DCM is able to convert:

• Sercel 508XT SEG-D revision 3.0 (shot domain) into Sercel DCM SEG-D revision 1.0
or 2.1
• Sercel 508XT SEG-D revision 1.0 or 2.1 into Sercel DCM SEG-D revision 3.0 (shot
domain)

Importing Rev. 1 & 2.1 SEG-D files > Importing files for a VP that defines different numerical pilots for every 8
sweep
Importing Rev. 1 & 2.1 SEG-D files

In this section, we aim at providing details on SEG-D import and especially putting the focus
on key points and restrictions.
Importing files for a VP that defines different numerical pilots for every
sweep
The DCM system has some restrictions when working in conjunction with a 508XT+VE464
in the very particular case of using different numerical pilots for every sweep in a VP in
slip-sweep mode.
The table below makes a summary of the cases where you have to be careful on how to record
your pilots so that they can be properly used for the correlation in DCM.
280
Importing 508XT Rev. 3 SEG-D files > Importing files for a VP that defines different numerical pilots for
every sweep
Importing 508XT Rev. 3 SEG-D files

The SEG-D files produced by the 508XT are revision 3.0 only. Please refer to the 508XT
documentation for details on the Sercel 508XT SEG-D revision 3.0 format.
Basically there is no change in the principles and importing sequence in DCM.
Required 508XT customization or settings

• As with the 508XT, the RAW and stacked/correlated files must be imported into DCM
for every shot/VP i.e. the RAW option must be ticked in the 508XT.
• You can choose to remove low frequencies of the data using either a Low Cut Filter or a
DC Offset removal:
• If you select a Low Cut Filter in 508XT, we recommend you
select the same Low Cut Filter in DCM (see Acquisition
Parameters (page 90)).
• If you select DC Offset Removal in 508XT, you must also apply
DC Offset Removal in DCM (see Acquisition Parameters
(page 90)). In this case, ensure you select None as the Low Cut
Filter value.
• In cases where you use SEGD-Gen with DCM.
- If you enable a Low Cut Filter value in WTU Acquisition Parameters (see
Acquisition Parameters (page 90)), ensure you Enable the microseismic
option in SEGD-Gen (see Microseismic (page 253)). This instructs DCM
NOT to Remove DC Offset. It is not needed as the Low Cut Filter in the WTU
already removes low frequencies.
- To Remove DC Offset, ensure you Disable the microseimic option in SEGD-
Gen. In this case, the DCM central unit software removes the offset from all the
traces, including cable traces & auxiliaries (as with the 508XT, DCM reprocesses
the cable traces when generating the final file with the wireless traces).
- If you do not want to remove DC offset or apply any Low cut filter, e.g. in passive
monitoring where consecutive SEG-D levels must not be altered, the
Microseismic option must be enabled.
• The RAW pilot trace must always be recorded in the dump (final) file i.e. always add this
trace (not only its auto-correlation) in the 508 process type definition.
This will guarantee that the reference trace number used for the correlation is filed in the
seismic trace headers.

Importing 508XT Rev. 3 SEG-D files > Importing files for a VP that defines different numerical pilots for 8
every sweep
Import restrictions
• DCM currently does not support importing 508XT SEG-D files using a digital pilot to
correlate the seismic traces with.
• DCM currently does not support importing micro-seismic 508XT SEG-D files.
282
Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1 > Importing files for a VP that defines different numerical
pilots for every sweep
Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1

The conversion to SEG-D 1.0/2.1 has been made so that there is no functional change
compared to a rev1.0/2.1 SEG-D that DCM produces from the import of a 1.0/2.1 SEG-D.
However, because the revision 3.0 of the SEG-D standard is far richer compared to the rev1.0/
2.1, some specific rev3 fields may have not been reported into rev 1.0/2.1 fields.
In the opposite, non-existent rev 1.0/2.1 fields in rev 3.0 couldn’t be “re- invented” in the final
rev 1.0/2.1 files converted by DCM (the spread type is an example).
Conversion Caveats
Making an exhaustive list of every single 3.0 field with its 1.0/2.1 translation or absence of
translation would be of low interest. The choice has been made in this section to focus on the
restrictions or interpretation subtleties that the DCM software makes when importing
revision 3.0 SEG-D and outputting an equivalent revision 1.0/2.1 with wireless traces added.
Timebreak and skew

• As with the 508XT, DCM uses the source GPS time break as the shot TB (Additional
Source Info Block in SEG-D rev3)
• The first timing word is computed and recorded as usual: if the source is not GPS-synced
and if the source time break falls out of a sampling rate boundary, a first timing word
value is recorded.
Note In SEG-D rev3, the GH#1 date-time of the shot is UTC time whereas it was local
time in SEG-D rev1.0/2.1. DCM keeps the original UTC time recorded in GH#1
in the final file. The shift between UTC and local times is visible in DCM in
the VP table as DCM used to display the shot time converted into local time in
the VP table for obvious practical reasons (note that DCM uses the server’s local
time information).
• Acquisition length, record length and listen time adjusted to cope with the N+1
samples per trace that Sercel rev1.0/2.1 SEG-Ds used to contain
- In Sercel SEG-D rev 1.0/2.1, the number of samples recorded for every trace is the
acquisition length divided by the sampling rate + 1 more sample
- In Sercel SEG-D rev 3, the number of samples recorded for every trace doesn’t contain
the additional sample anymore
- To cope with that in DCM converted SEG-Ds, the acquisition length, record length and
listen time are adjusted i.e. the length of 1 sample is deduced from those fields values
- The final number of samples remain exactly the same as the original 508XT imported
file.

Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1 > Importing files for a VP that defines different numerical 8
Note #1
That could be an issue with software tools reading SEG-D files in the particular cases of the
1ms or 500us sampling rates. In these 2 particular cases indeed, the channel set end time
(file header block > scan type header, byte 5-6) ends up with a value that is not a multiple of
2ms as expected. This could be an issue for readers that use the channel set end time to
compute the number of samples per trace/size in bytes of a trace as the computed value
may defer with the number of samples per trace recorded in the extended header.
Example of adjusted lengths/times

508XT generated file @1ms sampling rate, 3,000 samples per trace, acquisition length and
record length/listen time set to 3,000ms
Once processed in DCM and converted into SEG-D 1.0/2.1, the number of samples per trace
remains 3,000 but both acquisition length and record length/listen time are set to 2,999 to be
compatible with the +1 sample. The channel set end time is also set to 2,999 which is not a
multiple of 2ms.
• Shot number
• In SEG-D rev 1.0/2.1 the shot number recorded in the extended
header was the VP number in the 508XT operation table
• In SEG-D rev 3.0, the 508XT uses a unique identifier to uniquely
identify every VP. That greatly simplifies the import process in
DCM. It is this VP UUID that is now reported in the VP table in
Completion view. Note that it is truncated to exactly match what is
recorded in the final file in the extended header (bytes 37-40) as
this field can only hold a 4 bytes number (the UUID is a 16 bytes
number).
284
8 SEG-D Import Key Points
Converting from Rev. 3.0 SEG-D to rev 1.0 or 2.1 > Importing files for a VP that defines different numerical
285
Chapter
This chapter gives the user a description of the DCM Portable Field
Terminal (PFT) Application.

• PFT Settings (page 288)
• Creating a new WTU list (page 289)
• Collecting WTU Identifiers (page 291)
• Resuming a saved list (page 297)
• Toolbar and Status Indicators (page 298)
• Transferring Files to the DCM server (page 300)
• Transferring WTU List by USB drive (page 304)

Portable Field Terminal
Overview >
Overview
The Portable Field Terminal (PFT) application runs on a rugged handheld mobile device.
The main function of the PFT is to allow the field crew to assign WTU serial numbers to
stakes in the field. The PFT uses a built-in RFID sensor (on the back of the device) to scan
WTU serial numbers.
The PFT application creates a list of WTU serial numbers with the Line and Point number
for each WTU. On completion of a list, the list is automatically transferred wirelessly to the
DCM server where it can be imported into the Data Completion Manager window.
Figure 9-1 PFT handheld device
Press and hold the power button to switch on the handheld device. The PFT application will
start automatically after a few moments.

PFT Settings > 9
PFT Settings
Figure 9-2
Check the Wake-up Field Units while scanning check box if you would like to activate field
units that are in sleep mode during scanning.
A PFT will stay awake for approximately 15 minutes before returning to its sleeping state.
288
Creating a new WTU list >
Creating a new WTU list

The PFT can create lists of WTU serial numbers that are numbered by Line and Point, or
named lists. It also records the type of WTU.
• Numbered lists are used to record the position of WTUs on lines.
• Inventory lists are used to create inventories of WTUs in base camp or elsewhere.
Creating a numbered list

1. To create a Numbered list, click the Numbered list button on the start screen.
Figure 9-3
2. Enter the Line and Point number of the first WTU to be scanned, and the number
increment (typically one) between neighboring stakes.
3. Finally tell the PFT in which direction the line will be scanned. Select Low To High
if you will be started with the lowest numbered stake and scanning up the line, or
High to Low if you are scanning down the line.
4. Click Next to continue.

Creating a new WTU list > 9
Figure 9-4
5. By default, numbered lists are named after the Line/Point number of the first stake.
This is the name that will be displayed in the DCM window when the list is
imported. It is important that this name is meaningful to the person operating the
DCM window as it will be used to select the correct WTU list for each line.
- If you are happy with this name, click Next.
- If not, use the on-screen keyboard to enter a different name. Click the keyboard
icon at the bottom of the screen to open the on-screen keyboard. Enter the new
name and click the keyboard icon again to hide the on-screen keyboard. Click
Next to continue.
Creating an Inventory list

As above, but click the Inventory list… on the start screen and the PFT will go straight to
the list naming screen.
290
Collecting WTU Identifiers >
Collecting WTU Identifiers
Scanning WTU serial numbers

The PFT uses a scanner mounted at the rear of the hand-held device to read RFID chips on
the side of the WTU.
WTU serial numbers are collected on the PFT WTU list page.
Figure 9-5
The top of the screen shows the current list name. Make sure this name is appropriate for the
WTUs being scanned.
To scan a WTU, click the Scan button or the left application soft key (see Figure 9-1 on
page 287) to begin scanning, and hold the top of the PFT device next to the large barcode
label on the WTU.
The PFT scans for RFIDs once a second. Each scan is accompanied by an audible beep.
When a WTU's RFID chip is successfully read the PFT records the serial number in the WTU
list and plays an audible ping noise.
Note If a WTU is scanned twice in quick succession its serial number is only recorded
once (to avoid accidental re-scans) and an audible warning is played.
If this is a numbered list the WTU is automatically assigned the next Point number in
sequence on the current line. Make sure these numbers match the real-world stake location
of the WTU.
The Type field reads the type of WTU: “1C” for WTU
When you have finished scanning WTUs on a line click the Done button to save the list.

Collecting WTU Identifiers > 9
Manually entering a WTU serial number

If a WTU fails to scan, its serial number can be entered manually from the WTU list page.
Figure 9-6
1. Click the Add button. A new page will appear.

2. Use the numeric key pad to enter the WTU serial number.
3. Click OK to return to the WTU list page.
From this page you can also modify the Line and Point number associated with a WTU. To
do so, click the appropriate entry box and enter a new value.
Note If you change the Line or Point number whilst recording a numbered list, then
subsequent WTUs will be assigned the new Line number, and a Point number
based on the new value and the Point increment.
292
Recording stakes without a WTU (numbered lists)
Figure 9-7
To keep the numbering of WTUs correct, it is very important to record stake positions where
there is no WTU. This typically happens when an obstruction (such as a river or road)
prevents WTUs and sensors being deployed at a stake.
The simplest way to do this is to record a gap where an individual WTU is missing. To do
this,
1. Click Add.
2. Leave the Serial number field blank to tell the PFT that there is no WTU at this Line
and Point position.
3. Click OK.

Figure 9-8
4. For larger gaps, scan the first WTU after the gap. The WTU will appear in the table
with the wrong Line and Point number.
5. Double-click the WTU entry to modify the WTU entry.
294
Figure 9-9
6. Change the Point number and click OK.

7. Click Done.
Figure 9-10

Removing an entry
Figure 9-11
Click the Delete button to remove the last entry from the WTU list.
Click Done to confirm the deletion.
296
Resuming a saved list >
Resuming a saved list

Automatic Resumption of List after sleep or power off
The PFT will automatic resume a list if collection is interrupted by the device going to sleep
or if it is powered off.
On waking up, the PFT application immediately returns to the WTU list page with the same
entries as before.
Manual Resumption of a Saved List

The user can also choose to re-open and resume a saved list.
To do this, click the Resume a saved list… button on the Start page.
Figure 9-12
Note Once a list has been transferred to the recorder it is automatically removed from
the PFT device to avoid duplicate lists. Once a list has been transferred it cannot
be resumed.
The table at the top shows all WTU lists on that device. Click on the table to select a file and
view a summary of what it contains.
Click Next to re-open the file.

Toolbar and Status Indicators > 9
Toolbar and Status Indicators

Status indicators are located on the toolbar at the bottom of the PFT display.
Virtual keyboard
Files that have not yet been Battery indicator

transferred to DCM server
Figure 9-13
Scanner button/status indicator

The scanner button/status indicator is located at the left hand side of the PFT toolbar. It is
shown on the toolbar in the WTU list page.
The text on the button changes to indicate the status of the RFID scanner.
To activate the button simply click on the text or press the left application soft key (see
Figure 9-1 on page 287).
• Status “Scan” — scanner is not currently active. Click the button to start scanning (once
per second).
• Status “Stop Scan” — scanner is currently active (scanning once a second). Click the
button to stop scanning.
• Status “Scanner Error” — indicates a problem with the RFID scanner or its driver.
- Click the button to reinitialize the RFID scanner. This is often enough to resolve
a problem with the scanner.
- Remove the expansion cap on the top of the device and check that the RFID
scanner is seated correctly. Click the button to reinitialize the scanner.
On-screen keyboard button

Located in the middle of the PFT toolbar.
This button is used to show and hide the on-screen keyboard.
Battery Indicator
Shows how much charge is left in the device's internal battery.
Connection Status
The connection status icon is at the right hand side of the PFT toolbar.
298
Toolbar and Status Indicators >
It shows whether the PFT is able to connect to the DCM server.
Table 9-1
The PFT is able to connect to the DCM server. If the arrows are moving,
then the PFT is actively transferring files to or from the server.
The PFT is unable to connect to the DCM server.

Transferring Files to the DCM server > 9
Transferring Files to the DCM server

Completed WTU lists are automatically transferred to the DCM server whenever the PFT
comes within range of a MAN.
If the DCM window is open, the user is notified that new PFT files are available to be
imported. The PFT symbol turns green in colour.
Figure 9-14
When files are ready to be imported, the PFT button on the toolbar of the DCM window is
enabled.
Click the PFT button to start importing lists. The “PFT Lists” window will appear. The
Location dropdown list button makes it possible to browse through New Lists or the Archive
folder containing lists previously saved. You may want to open a list to apply its markers
and/or to save it to the Archive folder.
Field Units
Figure 9-15 PFT Lists window
The “PFT Lists” window shows a summary of all the lists that have been received from PFT.
The summary includes the date and time that the list was created, which PFT generated the
list, and how many WTUs the list contains.
It also shows the list Description. This is the name given to the list when it was first created
by the PFT operator.
300
Transferring Files to the DCM server >
Assigning markers
To import a marker list, select it from the New Lists or Archive location and then click
Open. This brings up the “Assign Markers” window.
Figure 9-16
To accept the WTU IDs and Line and Point numbers recorded by the PFT, just click Apply.
(Note that this automatically removes the list from the New Lists and saves it to the Archive
location, so that you can find it in the archive and open it again at a later date if required).
The WTU IDs, Line numbers and Point numbers will now appear in the Completion
window’s “Stakes” view and “WTU list” view.

Transferring Files to the DCM server > 9
Point numbers
Line numbers
Figure 9-17
PFT list archive

Applying the markers from a new list automatically saves the list to the Archive location.
You may not want to assign the markers from a new list and still want to archive it, for
example because you suspect a problem in that list or because you simply want to unclutter
the New Lists folder but apply the markers at a later date. In that case, select the list from the
New Lists folder and click on the Archive button.
Figure 9-18 PFT Lists window
If for any reason you need to apply the markers from an archived list, select it from the
Archive location and click Open.
302
Transferring Files to the DCM server >
Figure 9-19
This brings up the Assign Markers dialogue box. Click Apply (see Assigning markers
on page 301).

Transferring WTU List by USB drive > 9
Transferring WTU List by USB drive

A USB drive can also be used to transfer WTU lists to the DCM server if wireless networking
is unavailable.
1. Exit the PFT by creating a named WTU list with the name pft quit (include the
space).
2. Tap the Start button followed by Programs, followed by File Explorer:
Figure 9-20
3. Browse to My Device > Program Files > PFT > PFT Lists.
4. Select all files in this directory.
5. Go to Menu > Edit > Copy.
6. Browse to Hard Disk (the USB drive).
7. Go to Menu > Edit > Paste.
8. Remove the USB drive and insert it into the DCM server.
9. Copy the WTU list files from the USB drive to
/export/home/userdcm/PFTLists on the DCM server.
304
Transferring WTU List by USB drive >
305
Chapter
10 Data Harvester
This chapter gives the user a description of the Reaper and Field
Monitor applications which run on the Data Harvester tablet PC.

• Connecting to the DCM server (page 310)
• Harvesting (page 312)
• Uploading data to the DCM server (page 314)
• Field Monitor Application (page 315)
• File-based harvester (page 320)
• Main window (page 322)
• WTU List (page 324)
• WTU Topo View (page 328)
• Settings (page 332)
• Troubleshooting (page 336)
• Recommendations for maximum harvesting speed
(page 346)

Data Harvester
Overview >
Overview
Figure 10-1 Data Harvester - Tablet PC platform
The Data Harvester (DH) portable tablet PC runs the Reaper application and the Field
Monitor application.

Data Harvester
Overview > 10
The Reaper application is used to retrieve status information and seismic data from Wireless
Transmission Units (WTUs) that are operating in Autonomous mode.
Figure 10-2 Reaper application main window
308
Data Harvester
Overview >
The Field Monitor application is used to recover State of Health (SoH) data from WTUs.
Figure 10-3 Field Monitor application main window
The DH is designed to be very simple to use and requires next to no user input to operate.
Whenever a wireless or wired connection to a WTU is made, it automatically starts
uploading data from the WTU’s internal memory. Similarly, whenever the DH is connected
to the DCM server’s local network, it automatically starts to transfer the harvested data to the
server.
A detailed software installation procedure is described in the 508XT Installation Manual.

Data Harvester
Connecting to the DCM server > 10
Connecting to the DCM server
Connecting the Data Harvester to the DCM server

Before harvesting any WTU data, the DH should be connected to the DCM server to get the
latest list of WTUs to harvest. This is done by connecting the tablet PC to the Ethernet switch
port on the DCM local network. As soon as the DH detects the connection, it automatically
retrieves a list of WTUs that need to be harvested. For each WTU, the current line and station
position of the WTU is shown.
WTU’s need to be
harvested
Figure 10-4 DH window showing WTU list
The WTU List Table (above) shows the number of WTUs that need to be harvested, the serial
number of the WTUs and the field location.
310
Data Harvester
Connecting to the DCM server >
Disconnecting the Data Harvester from the DCM server

Disconnect the Tablet PC from the local network’s Ethernet switch port.
To conserve the tablet PCs battery, the tablet PC can be switched off once it is disconnected
from the network. The DH automatically backs up its list of WTUs to be harvested. The list
is automatically restored when the DH is restarted.

Data Harvester
Harvesting > 10
Harvesting
Harvesting the First WTU
If the table PC was switched Off, switch it On now.
The DH can connect to a WTU using its built-in access point, a MAN (not recommended),
or a WTU Ethernet cable. When using a MAN, make sure the power is turned down, so that
only the closest WTUs can connect. If distant (up to 6) WTUs connect, the data harvesting
process will be slower and more battery power will be used.
WTU’s currently
harvested
Figure 10-5 DH Window showing harvesting progress
As soon as the DH connects to a WTU, it will automatically begin harvesting its stored data.
The WTU will appear in the list of harvested WTUs (see above).
The Serial Number and Topo location of the WTU currently being harvested shows in the
Slots panel. Wait until the progress bar is complete. Clicking on the slot takes you to that
WTU in the List view or Topo view and shows its harvesting details.
Note Do not disconnect the WTU until it has transferred all its data (watch the
progress bar in the Slots panel).
312
Data Harvester
Harvesting >
The stronger the signal strength the quicker a WTU

will be harvested. Moving closer to a WTU with weak
signal strength (red status) will speed up harvesting.
Harvesting the remaining WTUs
To harvest the remaining WTUs, approach each one in turn and connect to it via the WTU
Ethernet cable or through a wireless access point.
At each WTU, wait for the progress bar to be complete before proceeding to the next WTU.
Note Each DH Access Point makes it possible to harvest two WTUs (max.)
simultaneously.

Data Harvester
Uploading data to the DCM server > 10
Uploading data to the DCM server

When you are finished harvesting WTUs, return to the DCM server and connect the DH
tablet PC to the Ethernet switch port.
The DH automatically begins uploading the data to the server. Depending on how many
WTUs have been harvested and how much data is to be transferred, this may take a while (in
some cases more than an hour).
Upload data in
progress
Figure 10-6
The Slots panel shows how much data has been transferred, and how much remains.
Once all the data has been uploaded, the progress bar is complete in the Slots panel. The
WTU list will update to show the new list of WTUs to be harvested. The DH is now ready
to begin harvesting again.
314
Data Harvester
Field Monitor Application > Setting a Gateway
Field Monitor Application

The Field Monitor application is used to recover SoH (State of Health) data from WTUs.
A WTU must be connected with cable to the DH or through Wifi. Then a gateway can be
defined in order to recover SoH data from surrounding WTU’s.
Figure 10-7
Setting a Gateway
Setting a Gateway WTU allows you to recover SoH data from WTU field units. Once a
gateway WTU has been defined, all surrounding WTU’s will transmit their SoH information
to the gateway.
To define a Gateway:
1. Connect the Data Harvester via cable or using Wifi to a WTU.
2. Open the Field Monitor application and select Gateway see Figure 10-7.

Data Harvester
Field Monitor Application > Setting a Gateway 10
3. A list of the available WTUs is displayed. Select the WTU that you would like to
define as the Gateway.
4. Select Set the Gateway. Click Set to confirm.
316
Data Harvester
Field Monitor Application > Setting a Gateway
5. The Gateway confirmation screen is displayed.

Data Harvester
Field Monitor Application > Monitoring Field Units 10
Monitoring Field Units

The Field Monitor application allows you to monitor the state of field units.
Figure 10-8
Elements which are green in colour indicate that they are within defined limits.
Elements which are red in colour indicate that they are outside defined limits.
Elements which are grey in colour indicate that data for the field units has not been received.
318
Data Harvester
Field Monitor Application > Mapping Field Units
Mapping Field Units

The Field Monitor allows you to visualize the location of connected field units on a
topographical map.
Figure 10-9
Loading settings
You can load settings exported from the Position application into Field Monitor. The settings
provide the current marker assignment, the SPS-R and the background map.

Data Harvester
File-based harvester > Mapping Field Units 10
File-based harvester
The Reaper application offers a “disconnected” mode which can be especially useful in
difficult field conditions where the data harvester tablets are not brought back very often to
the recorder to upload QCs and data QCs and to download their TB lists.
With this mode it is possible to:
• Import a list of TBs generated at the recorder in a file into the data harvester.
• Export QCs harvested by the data harvester into a file that can be uploaded afterwards at
the recorder into the server application.
This allows the data harvester to get the meta information it needs (list of WTUs with their
topographic locations and TBs) to harvest the field units and vice versa to supply the central
unit with the QC information harvested from the field with no need to physically connect the
tablet to the central unit in the recorder.
Note that any TB list file generated by the central unit software contains the whole list of
TBs/WTUs that the central unit software knows there is outstanding data for.
In return, any QC file generated by any data harvester contains the QCs of all the WTUs the
data harvester has been able to talk to.
Note
1. This mode does not allow the transfer of harvested seismic data for obvious
reasons relative to the volume of data transfer through files it would imply.
2. It is important that the clock of the tablet running the DH, the clock of the central
unit server and the clock of the machine running the clients (if relevant) are properly
synchronized so that the QC age computation is correct.
An advantage of the file-based DH feature is the possibility of using standard data networks
to transfer by email TB list and QC files between phones or connected devices.
Typical steps for using the file-based DH feature to exchange TB lists and QCs via 3G for
instance:
1. From the central unit software, use the “Export TB list” function to export the TB
list file into a local folder
2. Transfer this file to the local storage of a USB-connected phone.

3. Send the TB list file via e-mail from the phone.
320
Data Harvester
File-based harvester > Mapping Field Units
4. At the other end, USB-connect the phone that received the e-mail to the data
harvester tablet.
5. Extract the received file and use the “Import TB list” command in the data harvester
to import the list
Figure 10-10
6. Harvest WTUs…
7. In the opposite way, the same principles can be applied to return the harvested QCs
to the central unit software.

Data Harvester
Main window > 10
Main window
Figure 10-11 Main menu page
The main page has four menus:

• Field Unit List: shows the list of WTUs to harvest.
• Topo View: graphical view of the list of WTUs to harvest.
• Troubleshoot: allows you to choose a WTU to run sensor tests. Also makes it possible
to run a Harvest Health test.
• Settings: sets various options (harvesting trace data or QC only, display options).
• Quit: closes the Reaper window.
Device Status
• Battery: shows the state of the table PCs internal battery, and an estimate of time
remaining.
• Disk usage: shows the amount of space left in the tablet PCs internal hard disk. If the
display turns red, immediately return the DH to the DCM server to upload the harvested
data.
Harvesting Status
• Speed: shows the data rate when harvesting is in progress.
322
Data Harvester
Main window >
Connections Status
• Harvester: green if the harvester is up and running.
• Server: green if data is being transferred to/from the server, otherwise red. Do not
disconnect the DH from the local network until the indicator is red.

Data Harvester
WTU List > 10
WTU List
The WTU list table shows a list of all the WTUs that need to be harvested. It also shows
status information for WTUs that have connected, by displaying warning icons (for Sensor
tests, GPS quality, and Battery voltage and optionally Instrument tests) on the right-hand
border.
Green if
connected
Wipe up/down to
scroll through the
list
Warning
Tap to icons
show
details
Back to Shortcuts
main (Modify/
menu Clear Line
page Find WTU filter, etc.)
Figure 10-12 WTU list page
Warning icons only appear in case of errors. To set alert options and thresholds, select
Settings from the main menu page, then Display. See Display settings (page 333).
With no filters, the whole WTU list is displayed (wipe up/down to scroll through the list).
The shortcuts available from the button in the lower-right corner allow you to set or clear
filters.
324
Data Harvester
WTU List >
Banner
Figure 10-13
• WTU list: displays a count of the number of WTUs that have been harvested.
• To be harvested X of Y: shows the total number of WTUs remain to be harvested and
how many WTUs have been successfully harvested.
• QC X of Y: shows how many WTUs have uploaded QC status information to the Data
Harvester (GPS, battery voltage, etc). This will differ from the harvested count, as WTUs
without outstanding data will not be data harvested, but will send their QC information
to the Data Harvester.
The button in the bottom-right corner opens the filter setup page.
Line Filter
A Line Filter can be used to prevent the DH connecting to WTUs that are on the wrong line.
To set a line filter, tap on the Change button to open the “Line Filter” selection window. If
the WTU list contains Line and Receiver Numbers, the list of lines is prompted (otherwise
only “None” is prompted).
Tap to choose the line or lines to be harvested and choose OK.
Figure 10-14
The line filter is useful during wireless harvesting — it prevents the DH from connecting to
adjacent lines that may be far away and have a low bandwidth connection.
To disable the line filtering, select Clear line filter from the lower-right button.

Data Harvester
WTU List > 10
Error only filter

The Error only filter option makes it possible to show fewer WTUs — i. e. only those for
which a display alarm (Battery/GPS/Sensor test/Optionally Instrument test) is raised — or
all WTUs in the list.
Find
Clicking the find button brings up a dialogue box that lets you enter the location or serial
number of a WTU (depending on whether you choose “By WTU location” or “By WTU
ID”). Clicking OK takes you to the specified WTU in the list view.
By Field Unit Location
By Field Unit ID
Figure 10-15
326
Data Harvester
WTU List >
File-based DH functions
The file-based DH functions are available from the WTU list from the lower-right button
• Export QCs
Export QCs allows you to export a file that contains a binary description of the harvested
QCs that can be uploaded into the central unit software. A file browser window opens to let
you choose the device/directory where to save the QC file.
The file name format is qcData-${DATE_YYYYMMDD}_${TIME_HHMMSS}-
dh${DH_ID}-${NB_WTUS}WTU.dat.
• Import TB list
Import TB list allows you to import into the data harvester a WTU + TB list to harvest (this
list is generated from the central unit software).
A file browser window lets you choose the file to import.
Note Importing a new TB list has the same effect as downloading it in the usual
connected mode i.e. the previous list is fully replaced with the new one
(obviously the harvested seismic data are kept until uploaded to the server).

Data Harvester
WTU Topo View > 10
WTU Topo View

This graphical view shows the WTUs to harvest, mapped to Line numbers (along the vertical
axis) and Point numbers (along the horizontal axis).
Note that this view only shows those WTUs which have outstanding data and whose Topo
location is known to the server. The Data Harvester may find more WTUs and display them
in its WTU list page, but because they are not present in the list provided by the server, their
location is unknown, therefore they will not show in the WTU Topo view.
Figure 10-16 WTU Topo view — Harvesting status
The “Harvesting view” option shows the WTU’s harvesting status:

• Orange: the WTU has outstanding data.
• Green: no outstanding data in the WTU.
Figure 10-17 Topo view — QC status
The “QC view” option shows a summary of the WTU’s QC indicators:

• Green: all QC (battery/GPS/sensor tests/optionally instrument tests) indicators are OK
• Red: One or more QC (battery/GPS/sensor tests/optionally instrument tests) indicators
not OK,
328
Data Harvester
WTU Topo View >
• Grey: WTU not found yet (N/A).
Figure 10-18 Topo View - Noise Monitoring Status
The “Noise view” option shows the WTU’s noise monitoring RMS QC indicators:
• Green: the noise monitoring RMS value reported by the WTU is below the threshold
defined in the display settings.
• Red: the noise monitoring RMS value reported by the WTU equals or is above the
threshold defined in the display settings.
• Grey: the noise monitoring RMS value is unknown for the WTU at that topographic
location (WTU not “seen” yet) or the RMS value is outdated considering the noise
monitoring age threshold defined in Reaper’s display settings, page 333.
Note concerning the noise monitoring RMS value Computation:
The RMS value is computed from the samples LSB values recorded by the WTU - offset
removed - and converted into Volt using the gain factor.
The RMS value is computed over the last second (1s) of acquisition at the moment the WTU
receives the get QC message from the harvester.
Considering the way the data harvester works, it is important to notice that:
• A WTU returns its noise monitoring RMS value to the harvester every time it connects
to provide its QCs i.e. every 30s if the harvester stays in range. The noise monitoring
value being a QC, it would be updated every 30s for a harvester staying in range of a
WTU.
• In the particular case of a WTU being harvested (staying connected to the harvester), its
QCs (and its noise monitoring value) would be reported every 5s while connected.
Note that the noise monitoring RMS value is not persisted and so not uploaded to the central
unit when the harvester uploads its QCs and data to the central system as this QC is
essentially a “real-time” QC.
Also note that for WTU, the noise monitoring RMS value is computed and returned by the
WTU only for the channel #1.

Data Harvester
WTU Topo View > 10
You can use + and – zoom buttons to zoom in/out. Note that the purpose of these buttons is
not to expand/collapse cells so that they can show more or fewer details, but to let the view
fit the spread size.
Clicking on a WTU in the graphical view brings up a panel showing detailed properties and
allowing troubleshooting.
Click to show
details
Figure 10-19
File-based Data Harvester options are available via the lower-right button similar to
the WTU list functions.
Clicking the find button brings up a dialogue box that lets you enter the location or serial
number of a WTU (depending on whether you choose “By WTU location” or “By WTU
ID”). Clicking OK automatically selects the specified WTU in the graphical view.
330
Data Harvester
WTU Topo View >
By Field Unit Location
By Field Unit ID
Figure 10-20

Data Harvester
Settings > 10
Settings
Device
Figure 10-21 Device settings
This setup page allows you to set status options and alert thresholds for the Data Harvester
Tablet PC.
• Critical battery level (%): the indicator will turn orange if the battery voltage drops
below this threshold.
• Warning battery level (%): the indicator will turn red if the battery voltage drops below
this threshold.
• Battery level display: the available battery life can be displayed as a Time or %.
• Critical disk usage (%): the indicator will turn orange if the used disk space exceeds this
threshold.
• Warning disk usage (%): the indicator will turn red if the used disk space exceeds this
threshold.
332
Data Harvester
Settings >
Figure 10-22
Display settings
Figure 10-23 Reaper Display settings
This setup page allows you to set display options and alert thresholds.

Data Harvester
Settings > 10
• Warn on Battery: determines which battery (internal or external) is monitored for low
voltage.
• Low Battery: the minimum voltage of the WTUs battery (internal or external, depending
on the Warn on Battery setting). This causes a “Low battery” warning icon to appear if
the voltage drops below this threshold. A low voltage indicates that the WTUs external
battery needs recharging.
• Low Resistance: the minimum resistance result value for the sensor Resistance test. This
causes a “Sensor test” warning icon to appear if the resistance is below this threshold.
• High Resistance: the maximum resistance result value for the sensor Resistance test. This
causes a “Sensor test” warning icon to appear if the resistance exceeds this threshold.
• High Tilt: the maximum tilt result value for the sensor Tilt test. This causes a “Sensor
test” warning icon to appear if the tilt value exceeds this threshold.
• Noise Monitoring Threshold: the threshold in mV above which the noisy flag is raised.
• Noise Monitoring Age Threshold: the threshold in minutes above which the noise
monitoring information is considered outdated/irrelevant.
• Low GPS Quality: the minimum GPS signal quality level. This causes a “GPS” warning
icon to appear if the signal quality is below this threshold.
• Show instrument test errors: when set, instrument test errors - i.e. instrument noise,
instrument distortion, instrument gain, instrument phase, and instrument gravity (digital
WTUs only) - are taken into account when QC information is displayed:
In the WTU list, a dedicated instrument tests warning icon is displayed if at least one of
the instrument tests above has failed during the last BITs sequence
In the WTU topo view, instrument tests results are taken into account in the
“computation” of the status of the cell i.e. if at least one of the instrument tests above has
failed during the last BITs sequence, the cell is marked as failed (obviously it is also
marked as failed if one of the other QCs monitored - i.e. sensors tests, GPS and battery –
has failed).
This setting is disabled by default i.e. instrument tests results are not considered when
displaying QCs information.
• Inverted theme: sets the background colour (black/white).
334
Data Harvester
Settings >
Harvesting
Figure 10-24 Harvesting settings
Select this option if you want to harvest QC data only (helpful if there is no outstanding data).

Data Harvester
Troubleshooting > Sensor tests 10
Troubleshooting
In this section:
• Sensor tests (page 336)
• Harvest Health (page 338)
Sensor tests
With the Data Harvester connected to a WTU, you can use the Troubleshooting menu to run
sensor tests.
WARNING
This will stop the WTU recording seismic data during the sensor tests. Tests are
normally run when the WTU powers-up or on a Scheduled Test run (see BITs (Built
in Tests) on page 64).
Figure 10-25
1. Select Choose WTU to select the WTU you want to test.
336
Data Harvester
Troubleshooting > Sensor tests
Choose Field Unit

1425
Figure 10-26
2. In the dialogue box that appears, tap on Run tests to launch the sensor tests.
Figure 10-27
Test results are displayed:

Data Harvester
Troubleshooting > Harvest Health 10
Figure 10-28
• External Battery and Internal Battery: the voltage of the WTUs external/internal
battery. A low voltage indicates that the WTUs external battery needs recharging.
• GPS: indicates whether the WTU is GPS Locked, or Unlocked. A WTU requires GPS
lock for timing before it can begin acquiring.
• Resistance: the result of the last sensor Resistance test.
• Tilt: the result of the last sensor Tilt test.
• Noise: the noise monitoring RMS value in mV computed over the last second of
acquisition.
Harvest Health
This function retrieves all past quality and state-of-health data from a selected WTU and
makes it possible to save it to a .CSV file.
The Harvest Heath function extracts health data stored in each seismic data file in the WTU.
This allows the user to examine the changes in these health values over time (e.g. watch the
decay of the external battery voltage).
The files in the WTU capture these health values when the file is saved, so for instance hold
the GPS position, quality and the battery levels measured by the WTU at the time the file was
saved.
338
Data Harvester
Troubleshooting > Harvest Health
Operation
Troubleshoot a WTU and once the WTU is connected, select Harvest Health from the
Troubleshoot page. The progress of the health harvesting is visible on the screen.
Data Files
The data files produced are stored to your Windows data directory:
My Documents\reaper\health\<current date>\<WTU>.csv
• <current date> is the date when the file was created in ISO 8601 format (YYYY-MM-
DD).
• <WTU> is the serial number of the WTU for the file.
The file format is text in comma separated columns suitable for importing to a spreadsheet
application such as Microsoft Excel.

Data Harvester
Data Columns
The data files contain the following fields:
Column Description
The time of the first sample in the file. The time is in
GPS Time (µs) microseconds since the GPS datum (UTC 00:00:00,
January 6th, 1980).
The time of the first sample in the file converted to the
Reaper Tablet’s local time zone (yyyy-MM-dd hh:mm:ss)
Local Time e.g. “2013-05-20 08:25:13” for 8:25a.m. on the 20th of
May 2013. The Reaper Tablet’s time-zone should be set
correctly if you want to make use of this data.
The sub-second time of the first sample in the file. As the
Local Time column only shows time to whole seconds the
Fractional Time remaining microseconds are shown here. E.g. if the first
(µs) sample was really at “2013-05-20 08:25:13.095” then
Local Time shows “2013-05-20 08:25:13” and Fractional
Time shows “95000”.
340
Data Harvester
The time in microseconds between the last sample

present in this file and the next file stored in the WTU.
Time to next file When the WTU is recording normally this should always
(µs) be zero. There will be gaps between the files when the
WTU powers off, sleeps for working hours and runs
scheduled BITs.
Number of The number of samples contained in this file (240,000 is
Samples the size of a full file — scheduled BIT files are smaller).
This field contains a value that indicates why the file was
saved to the WTU flash. If the Stop Reason is not
END_GOOD then it is the reason the acquisition was
stopped by the WTU.
When looking at these stop reasons it is important to
remember they do not identify why the WTU is not
recording during the gap between files itself, just why the
WTU stopped initially.
Stop Reason For example a WTU can stop recording due to
GPS_LOCK_LOST but before starting again run out of
battery power and be off for two days before the external
battery is replaced. In this case the only thing recorded in
the health file is the GPS_LOCK_LOST event, not the real
issue of running out of battery power.
These codes are subject to change in future WTU
versions — extending this set by adding new codes
should be expected.
Stop Reason Value Description
Normal file save. The file was full. No issue and acquisition
GOOD 0
is continuing.
RESET_ACQ 2 Issue with the WTU sensor, acquisition is being restarted.
GPS timing lock has been lost. Acquisition is stopping until
GPS_LOST 3
the WTU regains GPS lock.
A gap in the timestamp of samples produced by the sensor
TIME_JUMP 4 has been detected. Acquisition continues after this gap in
time.

Data Harvester
The acquisition parameters (sample rate, gain, filter etc.)

PARAM_CHANGE 5 have been changed so acquisition has been stopped to
restart with the new parameters.
The WTU has been moved to idle state (should not be
STATE_IDLE 6
seen).
The WTU has been moved to standby state (should not be
STATE_STANDBY 7
seen).
The WTU is going to sleep (normally triggered by the
STATE_SLEEP 8
working hours setting).
The WTU is stopping acquiring seismic data in order to run
STATE_BIT 9 a BIT. Normally triggered by scheduled BITs. Once the
BITs have completed, the WTU should restart acquiring.
STATE_ACQUIRE 10 The WTU has entered acquire state (should not be seen).
The WTU is being sent new firmware so stops the
STATE_FIRMWARE 11 acquisition to receive and store the firmware. The firmware
update process ends with a WTU reboot.
UNKNOWN 15 The WTU has stopped recording for an unknown reason.
The WTU stopped recording this file as the BIT was
BIT_COMPLETE 19
complete — the file will be a BIT samples file.
The WTU was unable to open and read from this file. The
FILE_FAIL 20
file is probably corrupt in the flash in the WTU.
Column Description
The total time in seconds of the current boot of the WTU.
Uptime (s)
Power-offs, sleeps and resets will reset this timer.
Code for the type of power-on that caused the WTU to
Reset Code boot. These codes are internal and useful for Sercel staff
to diagnose faults in the WTUs.
Code for the type of power-on that caused the WTU to
Reset Data boot. These codes are internal and useful for Sercel staff
to diagnose faults in the WTUs.
Memory Free (B) Total amount of free memory in the WTU in bytes.
Internal Voltage
The voltage reading for the internal battery in millivolts.
(mV)
Internal Charge The charge estimate for the internal battery in milliamp-
(mAh) hours.
342
Data Harvester
The current being supplied by the internal battery in

Internal Current
milliamps. This can be used to establish when the internal
(mA)
battery is being charged or discharged.
Internal The temperature reading from the internal battery in
Temperature (°C) degrees centigrade.
External Voltage
The external battery voltage reading.
(mV)
Board Temperature The temperature reading for the WTU main processor
(°C) board in degrees centigrade.
The type of acquisition being recorded. These codes are
Acq Type
subject to change in future WTU versions.
Acq Type Value Description
SEISMIC 0 Normal seismic acquisition.
INSTR_IMPULSE 1 Instrument impulse response test.
INSTR_CMRR 2 Instrument common-mode rejection ratio
test.
INSTR_NOISE 3 Instrument noise test.
INSTR_DISTORTION 4 Instrument distortion test.
FIELD_NOISE 5 Field noise/offset test.
FIELD_OFFSET 6 Field noise/offset test.
FIELD_IMPULSE 7 Field impulse response test.
FIELD_CMRR 9 Field common-mode rejection ratio test.
FIELD_RESISTANCE 10 Field resistance test.
FIELD_DISTORTION 11 Field distortion test.
FIELD_TILT 12 Field tilt test.
INSTR_GAIN_PHASE 13 Instrument gain and phase test.
INSTR_GRAVITY 19 Instrument gravity test.
INSTR_CROSSTALK 21 Instrument crosstalk test.
FIELD_CROSSTALK 22 Field crosstalk test.
Column Description
Period (µs) The sample period being recorded.
Gain (dB) The gain setting being used.

Data Harvester
The filter type in use.
Filter Value Description

Filter
LINEAR 0 Linear phase filter.
MINIMUM 1 Minimum phase filter.
The subunit type for the sensor in DCM SEG-D format.
Subunit Type Subunit Type Value Description

WTU 38 WTU with Sercel sensor.
Number of
The number of channels the WTU has (1 or 3).
Channels
The settings key being used by the WTU. The key
changes when any of the WTU parameters are changed
Settings Key
(acquisition, working hours, scheduled BITs, GPS mode
etc.).
Indicates if the GPS has a position fix.
GPS Lock Value Description

GPS Lock NO_FIX 0 The position is not currently fixed
and may be unreliable.
FIX 1 The GPS module is reporting a
position fix.
GPS Quality (%) The WTU estimate of GPS quality in percent.

The GPS latitude in decimal degrees reported by the GPS
Latitude (°)
module.
The GPS longitude in decimal degrees reported by the
Longitude (°)
GPS module.
344
Data Harvester
Horizontal The horizontal accuracy estimate reported by the GPS

Accuracy (mm) module in millimetres.
Height (mm) The height above mean sea level (WGS84) in millimetres.
The GPS module used in the WTU.
GPS Model Value Description
MLEA_LIGHT 5 The WTU contains a MLEA light module.

GPS Model
MLEA 3 The WTU contains a MLEA module.
TM1 2 The WTU contains a TM1 module.
Column Description
[MLEA/MLEA_LIGHT] Count of times GPS antenna gain has
GPS AGC High become larger than reasonable for a working antenna (more
than 3 is shown as a fault in Completion).
[MLEA/MLEA_LIGHT] Module internal - Noise level as
GPS Noise/ms
measured by the GPS core.
[MLEA/MLEA_LIGHT] Module internal - AGC monitor (counts
GPS AGC count
SIGHI xor SIGLO, range 0 to 8191).
[MLEA/MLEA_LIGHT] Module internal - Status of GPS antenna
GPS Ant Status supervisor. (INIT=0, DONTKNOW=1, OK=2, SHORT=3,
OPEN=4).
[MLEA/MLEA_LIGHT] Module internal – Jamming indicator
GPS Jam Ind
(0 = no jamming, 255 = strong jamming).
GPS AGC Fault 0 if GPS AGC is OK, 1 if GPS AGC count is too high (above 3).
Number of Satellites Number of satellites being tracked by the GPS module.
GPS satellite ID being tracked in channel n (only valid if n is less
Svid[n]
than Number of Satellites)
GPS satellite carrier-to-noise ratio (dB-Hz) for channel n (only
Carrier to Noise[n]
valid if n is less than Number of Satellites)

Data Harvester
Recommendations for maximum harvesting speed > 10
Recommendations for maximum harvesting speed

Below are recommendations that will help achieve the maximum harvesting data rate:
• DHs and MANs at close range should be set to use different channels:
- WTUs can communicate on channels 1, 3, 5, 7, 9, 11.
- By default, all Tablet PCs are configured to use channel 1. Use a mix of channels
if harvesters are likely to be in close proximity.
- MANs can be configured to use channels 1, 5, and 9 or 3, 7 and 11. If MANs are
being used as fixed infrastructure, use different channel sets for adjacent MANs.
- If MANs are being used for harvesting, use one channel set for MANs, and the
other channels for Tablet PCs without MANs.
• If a MAN is being used with a Tablet PC, disable the internal Access Point to avoid it
interfering with the MAN.
• The MAN's inline amplifiers will increase the range of a MAN, but can reduce harvesting
speed if a distant WTU connects and starts harvesting. It may be better to have a shorter
range and move closer to the WTU before harvesting it.
• Power off any unused access point (MAN, Data Harvester).
• Set DH AP mode of operation to 11B/G Mixed mode (see 508XT V2.0 Installation
Manual).
• If tablet PCs are being used to harvest adjacent lines, space the harvesting teams out along
the lines to reduce interference, or harvest alternate lines.
• DH standing closer to the WTUs gives best harvesting rate figures.
• When WTUs are partially obscured due to terrain or high grass, changing the height of
the DH gives improvements (DH just above head height).
• By default the data harvester can harvest up to 2 WTUs at a time. This delivers best
performance in most cases and shouldn't be changed unless real harvesting
slowness is experienced (contact Sercel Customer Support for help).
• It is recommended to keep WTUs at least 2 m apart from one another (for example in case
of “batch harvesting”). Failure to respect this minimum spacing may give rise to
interferences and cause the WTUs to repeatedly disconnect/reconnect, slowing down the
harvesting data rate.
346
10 Data Harvester
Recommendations for maximum harvesting speed >
347
Chapter
11 Glossary of abbreviations
and acronyms

Glossary of abbreviations and acronyms
Glossary >
Glossary
A
AC Alternating Current.
Acq. An abbreviation for Acquisition.
ADC Analog-to-Digital Converter.
ADS-TA Ancillary Data Standard for Trace Attributes data. Used to exchange
trace and shot domain attributes, in conjunction with ADS-TE
records.
ADS-TE Ancillary Data Standard for Trace Edit data. Used in conjunction with
ADS-TA records, to track trace exclusion information for a seismic
data volume.
AGC Automatic Gain Control.
AIB Auxiliary Interface Box. Used to connect analog pilot signals from a
DPG to FDUs used as auxiliary channels.
AP Access Point (wireless communications).
API American Petroleum Institute.
APS Attribute Processing Support format. A standard for exporting shot

point attributes for source Quality Control tools.
ASCII American Standard Code for Information Interchange.
Aux. An abbreviation for Auxiliary.
Avg. An abbreviation for Average.
AWD Accelerated Weight Drop.
AWG American Wire Gauge.

Glossary > 11
B
Bacc. An abbreviation for Base plate Acceleration (vibrator).
BCD Binary-Coded Decimal.
BOB Break Out Box.
BOT Beginning Of Tape.
Bvel. An abbreviation for Base plate Velocity (vibrator).
C
CD Compact Disk.
CD490E Sercel-packaged 3490E cartridge drive.
CD590 Sercel-packaged 3590 cartridge drive.
CDP Common Depth Point. The situation where the same portion of
subsurface produces reflections at different offset distances on
several profiles.
Chan. An abbreviation for Channel.
CMP Common Mid-Point.
CMRR Common-Mode Rejection Ratio. Expresses the ability of a device to

reject the effect of a voltage that is applied simultaneously to both
input terminals.
COG Centre Of Gravity.
Config. An abbreviation for Configuration.
Coord. An abbreviation for Coordinates.
Correl. An abbreviation for Correlation.
350
Glossary >
CR Carriage Return.
CRC Cyclic Redundancy Code. An error correction code used to catch

errors in the data.
CTB Confirmed Time Break.
Ctrl. Abbreviation for Control.
D
DAC Digital-to-Analog Converter.
dB Decibel.
DC Direct Current.
DCM Data Completion Manager. Sercel’s seismic network software based

on a client/server architecture. Totally controls the spread and the
operations, and also performs all the requested computations (stacks,
correlations) before recording data onto tapes or disks.
DFT Discrete Fourier Transform.
DGPS Differential GPS. The DGPS technique uses a fixed ground-based

reference station to broadcast the difference between the position
indicated by the satellite system and the known fixed position. The
base station broadcasts the difference between the measured satellite
pseudoranges and actual (internally computed) pseudoranges, so that
receiver stations can correct their pseudoranges by the same amount.
DH Data Harvester.
DHCP Dynamic Host Configuration Protocol (protocol for automating the

configuration of computers that use TCP/IP)
DIP Dual Inline Package.

Glossary > 11
DMZ Demilitarized Zone (PCs directly connected online).
DPG Digital Pilot Generator (VE432/VE464). A control unit for the

vibrator electronics (DSD). Connects to the LCI-428.
DPR Dual Port RAM.
DQPSK Differential Quadrature Phase Shift Keying (transmission encoding).
DSCSI Differential SCSI. See SCSI.
DSD Digital Servo Drive (VE432/VE464). Performs real-time control of

the energy imparted into the earth by a vibrator. Communicates with
a DPG via a radio link.
DSP Digital Signal Processor.
DSU Digital Sensor Unit. An integrated package including station

electronics and three digital accelerometers based on the MEMS
technology.
DTS Data Transfer Sequence.
DVD Digital Versatile Disc.
DXF (1) Drawing Interchange Format (2) Data Exchange Format (3)
AutoCAD File (file extension).
E
EEPROM Electrically Erasable Programmable Read-Only Memory.
EOF End Of File.
EOM End Of Media.
EOT End Of Tape.
352
Glossary >
ESD Electrostatic Discharge.
eSQC-Pro Seismic Quality Control software.
Explo. An abbreviation for Explosive.
F
FC Fibre Channel.
FDU Field Digitizing Unit. An analog-to-digital converter for a seismic or

auxiliary channel. Includes a digitally controlled test signal
generator.
FFT Fast Fourier Transform. A Fourier Transform method for calculating

the frequency spectrum, in both magnitude and angle, for any
function of time.
Flt. An abbreviation for Fleet.
FM4 Hermaphrodite connector (4-pin, male and female).
FO Firing Order sent to a source controller.
FPS File Per Source (file including vibrator attributes plus SEG-D file
number)
Freq An abbreviation for Frequency.
FT FT analysis: Frequency vs Time representation of the amplitude of a

signal. Alternately, an abbreviation for Fourier Transform.
FTP File Transfer Protocol.
G
GIS Geographical Information System.

Glossary > 11
GMT Greenwich Mean Time.
GPS Global Positioning System. A satellite-based global navigation

system that consists of a constellation of 24 satellites orbiting the
Earth, several in-orbit spares, and a ground-based control segment.
The GPS is owned and operated by the U.S. Department of Defense
but is available for general use around the world. The satellites
transmit signals that are used for extremely accurate three-
dimensional (latitude, longitude, and elevation) global navigation
(position determination), and for the dissemination of precise time.
GPS-derived position determination is based on the arrival times, at
an appropriate receiver, of precisely timed signals from the satellites
that are above the user's radio horizon. The location accuracy is
anywhere from 100 to 10 metres for most equipment. Accuracy can
be pinpointed to within one meter with special military-approved
equipment.
GUI Graphical User Interface.
H
HC High Cut (RF filtering).
HDOP Horizontal Dilution Of Precision (GPS).
Hex. An abbreviation for Hexadecimal.
HFVS High Fidelity Vibratory Seismic. A method for improving the fidelity
of data acquired with a vibratory source. Involves the measurement
and recording of suitable motions from each vibrator so that these
actual motions can be used to separate simultaneous sources and
process the data.
HV High Voltage.
HVD High Voltage Differential (SCSI interface).
354
Glossary >
I
ID (1) Identification, identity. (2) Inner Diametre.
Ident. An abbreviation for Indentity.
Incr. An abbreviation for Increment
Info. An abbreviation for Information
Init. An abbreviation for (1) Initialize (2) Initialization.
Instr. An abbreviation for Instrument.
IP Internet Protocol.
ITB Internal Time Break.
K
kN 1000 Newton.
L
LAN Local Area Network. A data communications system that (a) lies
within a limited spatial area, (b) has a specific user group, (c) has a
specific topology, and (d) is not a public switched
telecommunications network, but may be connected to one.
Lat. An abbreviation for Latitude.
LC Low Cut (RF filtering).
LCD Liquid Crystal Display.
LCI-428 Line Controller Interface (428XL control module that can handle up
to 10 000 channels in real-time at 2 ms sampling rate).

Glossary > 11
LED Light Emitting Diode.
LF Line Feed.
Long. An abbreviation for Longitude.
LVD Low Voltage Differential (SCSI interface).
M
Macc. An abbreviation for Mass Acceleration (vibrator).
MAN Mesh Area Network
Max. Abbreviation for Maximum.
MB Megabyte.
Mbps Megabits Per Second.
MDR Mirage Data Recorder.
MEMS Micro-machined Electro-Mechanical Sensor.
MGA Multipurpose Geophone Analyzer.
Min. An abbreviation for (1) Minimum (2) Minute.
Misc. An abbreviation for Miscellaneous.
MRU Mobile Receiver Unit. A radiopositioning transceiver used for

service vehicle tracking.
Mvel. An abbreviation for Mass Velocity (vibrator).
356
Glossary >
N
NA Not Available.
NAN Not A Number.
NAS Network Attached Storage system
NB An abbreviation for “Number”.
NC Not Connected.
NCS Network Control Sequence
NFS Network File System.
NMEA National Marine Electronics Association.
NMO Normal Move-Out. The variation of reflection arrival time because of

variation in the shotpoint to geophone distance (offset) which causes
an increase of the length of the reflection travel path.
Num. An abbreviation for (1) Number (2) Numerical.
O
Obs. An abbreviation for Observer.
OD Outer diametre.
OS Operating System. Software designed to control the hardware of a

specific data-processing system in order to allow users and
application programs to make use of it.
OVC Open Vibrator Controller.

Glossary > 11
P
PB Play Back.
PC Personal Computer
PCB Printed Circuit Board.
PDA Personal Digital Assistant (palmtop computer).
PDF Portable Document Format
PFT Portable Field Terminal.
PN Part Number.
POSC Petroleum Open Standards Consortium.
PPM Parts Per Million.
PPS Pulses Per Second
PRM Processing Module in a DCM system. Software running on the server

computer, for formatting the data to and from the recording media, to
the plotters and eSQC-Pro, and for noise editing, correlation and
stacking.
Proc An abbreviation for (1) Processing (2) Process (3) Processor.
PWB Printed Wiring Board.
Q
QC Quality Control.
QPSK Quadrature Phase Shift Keying (transmission encoding).
358
Glossary >
R
RAID Redundant Array of Independent Disks.
RAM Random-Access Memory.
Rcv. An abbreviation for Receiver.
RDM Removable Disk Module.
Rdy. An abbreviation for Ready.
Rec. An abbreviation for (1) Record (2) Recorder.
Ref. An abbreviation for Reference.
RF Radio Frequency.
RFID Radio Frequency Identification.
RJ45 Registered Jack - 45 (8 wire connector used in networking).
RMS Root-Mean-Square. The square root of the average of the squares of

a series of related values (for a sine wave, 0.707 times the peak
value).
RP Receiver Position.
RSSI Received Signal Strength Indicator.
RTK Real-Time Kinematic (GPS). The RTK technique allows centimetric

accuracy to be achieved.
Rtv. An abbreviation for (1) Retrieve (2) Retrieval.
RVT Removable Virtual Tape.
Rx. An abbreviation for Receive.

Glossary > 11
S
SCSI Small Computer Systems Interface. SCSI is a system level interface
and as such it uses high level commands, and logical block
addressing. This considerably simplifies the task of the device driver
and saves CPU time on every single I/O. Moreover, because the SCSI
device does operations like “rewind the tape” or “format this disk”
without host intervention, the host saves even more CPU time.
SD or SDev. Standard Deviation.
SE Single-End.
SEG Society of Exploration Geophysicists. The SEG promotes the science

of geophysics and the education of exploration geophysicists.
SEG-D One of the formats developed by the SEG for recording seismic data,
used in processing and interpretation software to determine how the
tape should be read.
Seq. An abbreviation for Sequence.
SGA Signal Graphic Analyzer. Software used to analyse radio or wireline-

similarity signals acquired on Sercel systems. Allows the user to
monitor the phase, distortion or force of the vibrator source signal (on
auxiliary traces) in real time.
SGT Sercel Geophone Tester.
Simult. An abbreviation for Simultaneous.
SMT Surface-Mount Technology.
SN Serial Number.
SNR Signal-to-Noise Ratio.
SP Shot Point.
SPL Source Point Line.
360
Glossary >
SPN Source Point Number.
SPS SHELL Processing Support format. A standard for the transfer of

positioning and geophysical support data from land field crews to
seismic processing centres.
SR Sample Rate. The sampling interval in a seismic acquisition.
Stat. An abbreviation for Statistics.
SWR Standing Wave Ratio. The ratio of the maximum to the minimum
amplitudes of corresponding components of a field, voltage or
current along a transmission line or waveguide in the direction of
propagation and at a given frequency. Alternately, the reciprocal of
this ratio.
T
TB Time Break. A time mark indicating the shot instant or the time at
which the seismic wave was generated.
TBP Tape By-Pass.
TCP Transmission Control Protocol (with Internet Protocol, the main

protocol of the Internet).
TCXO Temperature-Controlled Crystal Oscillator.
TDM Time-Division Multiplex.
TDMA Time Division Multiple Access.
TE Transmit Error.
Topo. An abbreviation for Topographical.
Tx. An abbreviation for Transmit.

Glossary > 11
U
UH Up-Hole. (1) Uphole geophone: a geophone placed a few feet from a
shothole to detect the Uphole time. (2) Uphole time: the time for the
first wave from an explosion to reach the surface at or near the
shotpoint.
UL Sercel Ultra-Link product line.
UPS Uninterruptible Power Supply.
URL Uniform Resource Locator (world wide web address).
USB Universal Serial Bus.
UTC Universal Time Coordinated. Greenwich Mean Time updated with

leap seconds each year to compensate for changes in the rotation of
the earth.
Util. An abbreviation for Utility.
V
Var. An abbreviation for Variable.
VE464 Vibrator Electronics, consisting of a control unit (DPG) connecting

to the LCI-428 control module, and a vibrator control unit (DSD)
installed in each vibrator truck.
VHF Very High Frequency (frequency in the band from 30 to 300 MHz
corresponding to a metric wave between 10 and 1 m).
Vib. An abbreviation for Vibrator.
VLSI Very Large-Scale Integration.
362
Glossary >
VP Vibrator Point. The Shot Point when a vibratory source is used.
VQC88 A standalone field system used for vibrator maintenance or trouble-

shooting, capable of acquiring 7 analog channels (including two
independent accelerometer sensors).
VSR Vibrator Signal Recording. A function used to record actual vibrator

motions from each vibrator.
VSWR Voltage Standing Wave Ratio. The ratio of the electronic field or
voltage at a voltage minimum to that at the adjacent maximum in a
stationary-wave system, as in a coaxial cable.
W
WGS84 World Geodetic System 1984.
WLAN Wireless Local Area Network.
WTU Wireless Transmission Unit
WZ WZ velocity: the propagation velocity of the shot wave in the ground.
X
Xdump. Extra Dump.
Xmit. An abbreviation for Transmit or Transmitter.
Xtalk. An abbreviation for Crosstalk. The signal picked up by an acquisition

channel because of undesired coupling to another channel.

Index
> 12
12
Alias filter
· Frequency at - 3dB point (SEGD)
Index DFM: 119
· Slope (SEGD) DFM: 120
Angle from skew (SPS) DFM: 10,
DFM: 20, DFM: 50, DFM: 61
508XT manuals Archive
IM = Installation Manual · PFT lists FM2: 288
Array
FM1 = Functional Manual Vol. 1 · Forming (SEGD) DFM: 121
Arrays, sub, number of DFM: 25,
FM2 = Functional Manual Vol. 2
DFM: 66
DFM = Data Format Manual Assembly
· Location (SEGD) DFM: 142
A · Serial number (SEGD) DFM: 142
· Type (SEGD) DFM: 142
Abbreviations FM2: 334
Assign Markers
Absolute · from PFT list FM2: 287
· Spread, tests FM1: 87
Assigning boxes to stakes FM2: 178
Acquisition
Auto
· Error description (SEGD)
· Export FM2: 216
DFM: 128
· Length (SEGD) DFM: 122
Auto-assignment FM2: 178
· Number (SEGD) DFM: 127 Auto-check
· parameters FM2: 76 · GPS and SPS FM2: 183
Acquisition type tables (SEGD) · GPS, no SPS FM2: 186
· WTU assignment to RP
DFM: 127
FM2: 183
Additional
Autocorrelation peak time (SEGD)
· blocks (SEGD general header)
DFM: 113 DFM: 127
AGC FM1: 433 Automation
· Continuous, shooting FM1: 181
Aided assignment FM2: 116
· Discontinuous, shooting
Air FM1: 181
· gun (SPS) DFM: 14, DFM: 54 · Manual, shooting FM1: 181
· pressure psi (SPS) DFM: 25,
Auto-processing FM2: 60
DFM: 66
364
Index
>
Aux · error (SEGD) DFM: 140

· Channel contents (SPS) · high limit (SEGD) DFM: 140
DFM: 11, DFM: 22, · low limit (SEGD) DFM: 140
DFM: 51, DFM: 63 · value (SEGD) DFM: 140
· Traces, number of DFM: 122 Channel
Auxiliary · data error overscaling (SEGD)
· channels, deploying IM: 300 DFM: 146
· edited status (SEGD) DFM: 146
· filter (SEGD) DFM: 145
B · gain control method (SEGD)
Base scan interval (SEGD) DFM: 119
DFM: 114 · gain scale (SEGD) DFM: 145
Beginner FM2: 13 · increment (SPS) DFM: 16,
BIT DFM: 29, DFM: 57,
· generate VPs FM2: 50 DFM: 70
Blaster · number (SEGD) DFM: 142
· id (SEGD) DFM: 124 · process (SEGD) DFM: 147
· status (SEGD) DFM: 125 · sample to mV conversion factor
Blocking (SEGD) DFM: 146
· trace FM2: 212 · Set End Time (SEGD) DFM: 118
Blocks in General Trailer · Set Number (SEGD) DFM: 133
DFM: 116 · set number (SEGD) DFM: 118
· Set Starting Time (SEGD)
Browser
DFM: 118
· settings FM1: 6
· set, number of channels in
Button FM2: 3 DFM: 118
Bypass · sets per record DFM: 114
· file exports FM2: 225 · type (SEGD) DFM: 143
Bytes per scan (SEGD) DFM: 114 · type id (SEGD) DFM: 147
· Type Identification (SEGD)
C DFM: 119
Channels, number of (SPS)
Cable
· length, Line IM: 299
DFM: 11, DFM: 21, DFM: 51,
· Line cable length IM: 299 DFM: 62
Calendar FM2: 84 Charge
Capacitance · Depth DFM: 24, DFM: 66

Index
> 12
· Length DFM: 24, DFM: 66 DFM: 145

Circular bearing of H256 (SPS) · unit type (SEGD) DFM: 145
DFM: 10, DFM: 20, DFM: 50, Conversion
DFM: 60 · sample to mV DFM: 146
Cleaning Coord. status final/prov (SPS)
· boxes IM: 290 DFM: 14, DFM: 25, DFM: 54,
· plugs IM: 290 DFM: 66
Click FM2: 3 Coordinate location (SPS) DFM: 9,
Client DFM: 18, DFM: 49, DFM: 59
· main window FM2: 13 Copy
· SPS DFM: 9, DFM: 18, · and Paste FM2: 6
DFM: 49, DFM: 58 · function (Export window)
Clock FM2: 223
· time w.r.t. GMT (SPS) DFM: 9, Core FM1: 618
DFM: 18, DFM: 49, Correlator, noise supp (SPS)
DFM: 59 DFM: 13, DFM: 24, DFM: 53,
CMRR DFM: 65
· geophone string FM1: 624 Corrosion IM: 305
Colour code FM2: 106 Crew
Comment · name, Comment (SPS) DFM: 11,
· VP table FM2: 43 DFM: 21, DFM: 51,
Comments DFM: 62
· SEGD DFM: 131 Cut off
Common mode · error (SEGD) DFM: 140
· rejection ratio, geophones · high limits (SEGD) DFM: 140
FM1: 624 · low limit (SEGD) DFM: 140
Connection · value (SEGD) DFM: 140
· opening a session FM1: 3 CX-508 Concentrator IM: 9
Continuous
· shooting FM1: 181
Continuous monitoring FM2: 27
D
Control Damp coeff, natural freq. (SPS)
· type (SPS) DFM: 13, DFM: 24, DFM: 12, DFM: 52
DFM: 53, DFM: 65 Damping coeff, natural freq (SPS)
· unit serial number (SEGD) DFM: 23, DFM: 64
366
Index
>
Data · Channels (tests) FM1: 87

· Bypass FM2: 225 · of grid units (SPS) DFM: 9,
· record sorting order (SPS) DFM: 19, DFM: 49,
DFM: 7, DFM: 46 DFM: 60
Data Harvester · of survey area (SPS) DFM: 9,
· connecting FM2: 296 DFM: 17, DFM: 49,
· disconnecting FM2: 297 DFM: 58
· harvesting FM2: 298 Desktop FM1: 7
· software, installing IM: 344 Destination Devices FM2: 220
· uploading data FM2: 300 Diagnostic codes FM2: 133
· user guide FM2: 292 Dialog box FM2: 3
Date Digital
· of survey (SPS) DFM: 9, · Sensor Unit, deploying IM: 295,
DFM: 18, DFM: 49, IM: 484
DFM: 58 Discontinuous
· SEGD DFM: 128 · shooting FM1: 181
Day Double-click FM2: 3
· of year (SPS) DFM: 15, DSU
DFM: 27, DFM: 55, · Deploying IM: 295, IM: 484
DFM: 68 DSU1-508 IM: 8
DCM Dump FM2: 61
· Launch FM2: 13 Dump stacking fold (SEGD)
· Patcher FM2: 11
DFM: 127
· Server
Start/Stop FM2: 10
Duplicate
· stakes FM2: 118
Dead seis traces, number of
DFM: 122
Deploying E
· field equipment IM: 288, Ethernet
IM: 481 · port, identifying IM: 30
Depth Event
· charge DFM: 24, DFM: 66 · definition text file FM2: 245
· towing DFM: 25, DFM: 66 Expanded file number (SEGD)
Descale Multiplier (SEGD) DFM: 116, DFM: 117
DFM: 118 Explosive (SPS) DFM: 14,
Description

Index
> 12
DFM: 54 · unit type (SEGD) DFM: 143

Exponent, subscans DFM: 119 FDU-508 IM: 7
Export · functions IM: 7
· Auto/Manual FM2: 216 Fibre Optics
· client window FM2: 204 · TFOI, connecting IM: 298,
· markers FM2: 48 IM: 489
Export window FM2: 204 Field
Extended · computer system(s) (SPS)
· channel set number (SEGD) DFM: 9, DFM: 18,
DFM: 121, DFM: 133 DFM: 49, DFM: 59
· Channel Sets/Scan Types (SEGD) · record increment (SPS) DFM: 16,
DFM: 116 DFM: 29, DFM: 56,
· file number (SEGD) DFM: 133 DFM: 70
· header (SEGD) DFM: 122 · record number (SPS) DFM: 16,
· header blocks (SEGD) DFM: 116 DFM: 29, DFM: 56,
· header flag (SEGD) DFM: 121 DFM: 70
· header length (SEGD) DFM: 114 · tape number (SPS) DFM: 16,
· receiver line number (SEGD) DFM: 29, DFM: 56,
DFM: 135 DFM: 70
· receiver point number (SEGD) File
DFM: 136 · count (SEGD) DFM: 128
· Record Length (SEGD) · Header block (SEGD) DFM: 113
DFM: 116 · number (SEGD) DFM: 113,
Extender DFM: 133
· TFOI, connecting IM: 298, Files
IM: 489 · per tape FM2: 211
External · per tape (SEGD) DFM: 128
· header (SEGD) DFM: 131 Filter
· header blocks (SEGD) DFM: 116 · alias Hz, dB pnt, slope (SPS)
· header length (SEGD) DFM: 115 DFM: 11, DFM: 21,
DFM: 51, DFM: 62
· low Hz, dB pnt, slope (SPS)
F DFM: 11, DFM: 21,
Factor to metre (SPS) DFM: 9, DFM: 51, DFM: 62
DFM: 19, DFM: 49, DFM: 60 · notch Hz, -3 dB points (SPS)
FDU DFM: 11, DFM: 51
368
Index
>
· notch Hz, -3dB points (SPS) DFM: 113

DFM: 21, DFM: 62 · Header block 2 (SEGD)
· type FM1: 76 DFM: 116
· type (SEGD) DFM: 128 · Header block 3 (SEGD)
Filtering DFM: 117
· seismic trace display FM1: 431 · Header Block Number (SEGD)
Firmware update FM2: 62 DFM: 116, DFM: 117
First · Trailer blocks, number of
· Notch Frequency (SEGD) DFM: 116
DFM: 121 Geodetic datum
· Timing Word (SEGD) DFM: 133 · parameters (SPS) DFM: 9,
Floppy disk DFM: 19, DFM: 49,
· specifications (SPS) DFM: 7, DFM: 59
DFM: 8, DFM: 46, · spheroid (SPS) DFM: 9,
DFM: 48 DFM: 18, DFM: 49,
Format DFM: 59
· code (SEGD) DFM: 113 Geophone
· SEGD, Rev 2.1 DFM: 151 · arrangement FM1: 625
· SPS, initial DFM: 1 · number per trace FM1: 623
· SPS, Rev. 2.1 DFM: 41 · parallel FM1: 623
· version num. (SPS) DFM: 9, · series FM1: 623
DFM: 17, DFM: 49, · strings FM1: 623
DFM: 58 Geophysical contractor (SPS)
Frequency DFM: 9, DFM: 18, DFM: 49,
· Nyquist FM1: 77, FM2: 238 DFM: 58
From channel (SPS) DFM: 16, Getting started FM2: 7
DFM: 29, DFM: 57, DFM: 70 · 508XT GUI FM1: 1
From receiver (SPS) DFM: 17, GPS
DFM: 29, DFM: 57, DFM: 70 · correcting geometry errors
Geometry
correcting with GPS posi-
G tions FM2: 178
Gain · correcting Stake ID errors
· geophone string FM1: 624 FM2: 116
General GPS position FM2: 26
· Header block 1 (SEGD) Grid

Index
> 12
· coord. at origin (SPS) DFM: 10,

DFM: 20, DFM: 50,
I
DFM: 60 Icon FM2: 3
· origin (SPS) DFM: 10, Impedance
DFM: 20, DFM: 60 · geophone string FM1: 624
Group Import
· geophone string FM1: 627 · administration window FM1: 618
Guest · markers from CSV FM2: 48
· privileges FM1: 616 · WTU list from PFT FM2: 286
Index
· box FM2: 3
H Install
Hardware · administration window FM1: 618
· installing IM: 25 Installing
Harvest Multiple Autonomous CX- · Data Harvester software IM: 344
508 FM1: 105 · hardware IM: 25
Harvesting FM2: 298 · PFT software IM: 264
· recommendations FM2: 332 Instrument
Harvesting CX-508 FM1: 643 · Code (I) tables (SPS) DFM: 11,
Header record DFM: 51
· description (SPS) DFM: 17, · Code (SPS) DFM: 16, DFM: 29,
DFM: 58 DFM: 56, DFM: 70
· specification (SPS) DFM: 8, Internal
DFM: 48 · time break (SEGD) DFM: 126
Help
· language FM1: 6 J
Historic
· editing type (SEGD) DFM: 126 Julian day (SEGD) DFM: 113
· range (SEGD) DFM: 126
· taper length (SEGD) DFM: 126 L
· threshold Init value (SEGD)
Language
DFM: 126
· help FM1: 6
· zeroing length (SEGD)
DFM: 126 Lat. Long
· initial line (SPS) DFM: 10,
Hour of day (SEGD) DFM: 113
DFM: 20, DFM: 50,
370
Index
>
DFM: 60 · user FM1: 4

· scale factor (SPS) DFM: 10, Log in
DFM: 20, DFM: 50, · connecting to server FM1: 4
DFM: 60 · name FM1: 5
Lat. of standard parallel(s) (SPS) Long. of central meridian (SPS)
DFM: 9, DFM: 19, DFM: 49, DFM: 10, DFM: 19, DFM: 50,
DFM: 60 DFM: 60
Launcher Low
· bar, customizing FM1: 9 · stacks, number of DFM: 147
· icons FM1: 8, FM2: 31 · Trace Percentage (SEGD)
Leakage DFM: 126
· error (SEGD) DFM: 141 · Trace Value (SEGD) DFM: 126
· limit (SEGD) DFM: 141 Low-cut
· value (SEGD) DFM: 141 · Filter frequency (SEGD)
Length DFM: 120
· record (SEGD) DFM: 127 · Filter slope (SEGD) DFM: 120
Limits
· WTU parameters FM2: 78
Line
M
· name (SPS) DFM: 15, DFM: 16, Management
DFM: 26, DFM: 29, · sessions FM1: 617
DFM: 55, DFM: 56, Manual
DFM: 67, DFM: 70 · Export FM2: 216
· number format (SPS) DFM: 10, · shooting FM1: 181
DFM: 20, DFM: 50, Manual assignment FM2: 182
DFM: 61 Manufacturer’s
· sequence number, SPS DFM: 49, · code (SEGD) DFM: 114
DFM: 58 · serial nb (SEGD) DFM: 114
Linear Map grid
· Phase FM1: 83, FM2: 238, · easting (SPS) DFM: 15,
FM2: 239 DFM: 27, DFM: 55,
List DFM: 68
· box FM2: 3 · northing (SPS) DFM: 15,
Live seis traces, number of DFM: 27, DFM: 55,
DFM: 122 DFM: 68
Local Markers

Index
> 12
· assigning, PFT list FM2: 287 · seismic data setup FM1: 433
· history FM2: 120 Normalization
· import from CSV FM2: 48 · seismic traces FM1: 433
Max Notch
· of max, Aux (SEGD) DFM: 127 · frequency (SEGD) DFM: 121
· of max, Seis (SEGD) DFM: 127 Number of
MEMS IM: 8 · Auxes (SEGD) DFM: 122
Minimum · blocks of General Trailer (SEGD)
· Phase FM1: 77, FM2: 238, DFM: 116
FM2: 239 · channel sets per record (SEGD)
Minute of day (SEGD) DFM: 113 DFM: 114
Mouse · channels (SPS) DFM: 11,
· Buttons FM2: 3 DFM: 21, DFM: 51,
Multi-component DFM: 62
· recording (SPS) DFM: 11, · channels in this channel set
DFM: 22, DFM: 51, (SEGD) DFM: 118
DFM: 63 · dead Seis traces (SEGD)
DFM: 122
· geophones per trace FM1: 623
N · live Seis traces (SEGD)
Name DFM: 122
· Log in FM1: 5 · sample skew 32 byte extensions
NAS4000 (SEGD) DFM: 114
· shock-mount parts IM: 223 · samples in trace (SEGD)
No. sub arrays, nom depth (SPS) DFM: 122
DFM: 25, DFM: 66 · samples per trace DFM: 131
Noise · samples per trace (SEGD)
· elimination type (SEGD) DFM: 134
DFM: 126 · Seis traces (SEGD) DFM: 122
Noisy · stacks low (SEGD) DFM: 147
· stacks noisy (SEGD) DFM: 147
· stacks, number of DFM: 147
· subscans exponent (SEGD)
· trace percentage (SEGD)
DFM: 126 DFM: 119
· traces (SEGD) DFM: 122
Nominal towing depth DFM: 25,
· windows (SEGD) DFM: 126
DFM: 66
Nunits, len, width (SPS) DFM: 12,
None
372
Index
>
DFM: 13, DFM: 23, DFM: 24, IM: 194, IM: 394, FM1: 500
DFM: 52, DFM: 53, DFM: 64, Permission FM1: 616
DFM: 65 PFT
Nyquist FM1: 77, FM2: 238 · software, installing IM: 264
PFT lists
· archive FM2: 288
O · Assigning markers FM2: 287
Observer Phase
· privileges FM1: 616 · angle (SEGD) DFM: 117
Offset · Control (SEGD) DFM: 117
· to coord. location (SPS) DFM: 9, · Linear FM1: 83, FM2: 238,
DFM: 18, DFM: 49, FM2: 239
DFM: 59 · Minimum FM1: 77, FM2: 238,
Open FM2: 239
· session FM1: 3, FM2: 8 Pilot length (SEGD) DFM: 127
Operation window FM1: 613 Ping IM: 30
Optical Fibre Plug
· TFOI, connecting IM: 298, · cleaning IM: 290
IM: 489 Point (to) FM2: 4
Organization Point Code
· code DFM: 286 · SPS DFM: 15, DFM: 26,
Outstanding DFM: 55, DFM: 67
· VP FM2: 99 Point Depth (SPS) DFM: 15,
DFM: 26, DFM: 55, DFM: 67
P Point Index
· SPS DFM: 15, DFM: 16,
Parallel
DFM: 26, DFM: 29,
· geophone FM1: 623
DFM: 55, DFM: 56,
Parameters DFM: 67, DFM: 70
· acquisition FM2: 76
Point number
· loading to WTU FM2: 93
· SPS DFM: 15, DFM: 16,
Password DFM: 26, DFM: 29,
· expiry date FM1: 616 DFM: 55, DFM: 56,
· opening a session FM1: 5 DFM: 67, DFM: 70
Paste FM2: 6 Point record
Peripherals IM: 133, IM: 182,

Index
> 12
· description (SPS) DFM: 26,

DFM: 67
Q
· specification (SPS) DFM: 15, QC
DFM: 55 · age FM2: 99
Polarity · age, max. FM2: 36
· SEGD DFM: 114 · Time FM2: 99
Pos. proc. contractor (SPS) DFM: 9, Quadrant bearing of H256 (SPS)
DFM: 18, DFM: 49, DFM: 59 DFM: 10, DFM: 20, DFM: 50,
POSC DFM: 286 DFM: 61
Positioning Quality Control
· contractor (SPS) DFM: 9, · check records (SPS) DFM: 14,
DFM: 18, DFM: 49, DFM: 54
DFM: 58 QuietSeis IM: 2
Post-plot date of issue (SPS)
DFM: 9, DFM: 18, DFM: 49, R
DFM: 58 R,S,X file quality control (SPS)
Power DFM: 14, DFM: 54
· requirements IM: 31
Rate
P-P bar/m,prim/bubble (SPS) · refresh FM2: 16
DFM: 25, DFM: 66 · sample FM1: 76
Prestack within field units (SEGD) Raw SEG-D FM2: 36
DFM: 126 Real-time alerts FM2: 26
Printer IM: 196 Reaper window FM2: 308
Privileges FM1: 616 Receiver
Process · code (Rx) tables (SPS) DFM: 12,
· Type, SEGD DFM: 127 DFM: 52
· VPs FM2: 41 · index (SPS) DFM: 17,
Project code and description (SPS) DFM: 30, DFM: 57,
DFM: 10, DFM: 20, DFM: 50, DFM: 71
DFM: 61 · line number (SEGD) DFM: 134
Projection · point easting (SEGD) DFM: 137
· type (SPS) DFM: 9, DFM: 19, · point elevation (SEGD)
DFM: 49, DFM: 60 DFM: 137
· zone (SPS) DFM: 9, DFM: 19, · point index (SEGD) DFM: 134
DFM: 49, DFM: 60 · point northing (SEGD)
374
Index
>
DFM: 137 · int. Record Len. (SPS) DFM: 11,

· point number (SEGD) DFM: 134 DFM: 51
Record · int., Record Length (SPS)
· identification (SPS) DFM: 15, DFM: 21, DFM: 62
DFM: 16, DFM: 55, · Rate FM1: 76
DFM: 56 · skew extensions, number of
· length (SEGD) DFM: 127 DFM: 114
· type (SEGD) DFM: 114 · skew, SEGD DFM: 133
Record length · to mV conversion factor
· SEGD DFM: 114 DFM: 146
Refraction Sample Rate
· delay, SEGD DFM: 126 · SEGD DFM: 122
Refresh Samples
· rate FM2: 16 · in trace, number of DFM: 122
Relation record · per trace, number of DFM: 131,
· description (SPS) DFM: 29, DFM: 134
DFM: 70 Scale
· specification (SPS) DFM: 16, · factor (SPS) DFM: 10,
DFM: 56 DFM: 20, DFM: 50,
Remote DFM: 60
· user FM1: 4 Scan Type
Remote Connection FM1: 4 · Header (SEGD) DFM: 118
Resistance · Number (SEGD) DFM: 133
· error (SEGD) DFM: 139 · per record (SEGD) DFM: 114
· high limit (SEGD) DFM: 139 Scheduled
· low limit (SEGD) DFM: 139 · BIT VPs, generate FM2: 50
· value (SEGD) DFM: 139 · tests FM2: 79
Revision Number (SEGD) SCI-508 IM: 19
DFM: 116 Scrollbar FM2: 4
RMS normalization FM1: 433 Second
Role FM1: 616 · Notch Frequency (SEGD)
RSSI FM2: 99 DFM: 121
· of minute (SEGD) DFM: 113
SEGD
S · format, Rev 2.1 DFM: 151
Sample · Trace Blocking FM2: 212

Index
> 12
Seis traces, number of DFM: 122 Setup

Seismic · AGC FM1: 433
· datum (SPS) DFM: 15, · Filtering, seismic trace display
DFM: 26, DFM: 55, FM1: 431
DFM: 67 · Normalization, seismic traces
· instrument header records (SPS) FM1: 433
DFM: 21, DFM: 62 · Time, exponential FM1: 433
· receiver header records (SPS) SH geophone IM: 294
DFM: 23, DFM: 64 Shock-mount
· source header records (SPS) · NAS4000 IM: 223
DFM: 23, DFM: 65 Shooting
Select FM2: 4 · system, connecting IM: 41
Selecting Shot
· table cells FM2: 6 · Depth, charge len. (SPS)
Senior DFM: 14, DFM: 54
· Observer, privileges FM1: 616 · depth, charge len. (SPS)
Sensor DFM: 24, DFM: 66
· sensitivity (SEGD) DFM: 144 · number (SEGD) DFM: 122
Sensor Type Size
· Number (sensor tests) DFM: 137 · vert. stk fold (SPS) DFM: 13,
· SEGD code DFM: 136 DFM: 53
Sequence Size, vert. stk fold (SPS) DFM: 24,
· Line, SPS DFM: 49, DFM: 58 DFM: 65
Series Skew, sample, number of extensions
· geophones FM1: 623 DFM: 114
Server Sleep
· log on to FM1: 4 · time, WTU FM2: 85
· start/stop FM2: 10 · WTU FM2: 49
Session Slip-sweep
· manager FM1: 617 · mode used (SEGD) DFM: 128
· opening FM1: 3, FM2: 8 Software
Sets, channel DFM: 114 · version (SEGD) DFM: 128
Settings SoH FM2: 49
· browser FM1: 6 Soil, drill method (SPS) DFM: 14,
· help FM1: 6 DFM: 25, DFM: 54, DFM: 66
376
Index
>
Source Stake ID mapping

· aux nb (SEGD) DFM: 127 · Aided assignenment FM2: 178
· code (Sx) tables (SPS) DFM: 13, · Auto-assignment FM2: 178
DFM: 53 · Manual assignment FM2: 182
· easting (SEGD) DFM: 128 Starting
· elevation (SEGD) DFM: 128 · DCM server FM2: 10
· Line Number (SEGD) DFM: 117 State of Health FM2: 49, FM2: 158
· northing (SEGD) DFM: 128 Static correction (SPS) DFM: 15,
· Point Index (SEGD) DFM: 117 DFM: 26, DFM: 55, DFM: 67
· Point Number (SEGD) DFM: 117 Stopping
· Set Number (SEGD) DFM: 117 · DCM server FM2: 10
Source Devices FM2: 220 Streamer cable number (SEGD)
Spacing DFM: 121
· IM: 299 String
· FDU IM: 299 · gain, geophone FM1: 624
· FDU-508 · group, geophone FM1: 627
Spacing IM: 299 · impedance, geophone FM1: 624
Spread · wiring, geophones FM1: 627
· number (SEGD) DFM: 123 Subarrays, number of DFM: 25,
· type (SEGD) DFM: 123
DFM: 66
SPS
Subscan exponent DFM: 119
· format, initial DFM: 1,
DFM: 274 Sum VP/WTU FM2: 106
· Rev. 2.1 DFM: 41 Super-spread FM2: 43
· Sercel (over 10000 traces) Surface
DFM: 38 · elevation, SPS DFM: 15,
Stacking Fold DFM: 55
· SEGD DFM: 127 Surface elevation
Stacks, number of · SPS DFM: 27, DFM: 68
· Low DFM: 147 Swath
· Noisy DFM: 147 · first line (SEGD) DFM: 123
Stake ID FM2: 116 · first number (SEGD) DFM: 123
· correcting with GPS position Sweep
FM2: 116 · freq start, end (SPS) DFM: 13,
· loading to Position FM2: 167 DFM: 53
· updating FM2: 118 · frequency start,end (SPS)

Index
> 12
DFM: 24, DFM: 65 · event definition FM2: 245

· length (SEGD) DFM: 127 TFOI
· type, length (SPS) DFM: 13, · connecting IM: 298, IM: 489
DFM: 24, DFM: 53, TFOI-508 IM: 10
DFM: 65 Theft Alarm
· WTU FM2: 27
T Third Notch Frequency (SEGD)
DFM: 121
Table
· how to select FM2: 6
Threshold
· Hold/Var (SEGD) DFM: 126
Tape
· type tables (SEGD) DFM: 127
· drive IM: 23
· Label FM2: 210
Tilt
· error (SEGD) DFM: 139
· label (SEGD) DFM: 127
· limit (SEGD) DFM: 139
· number of files FM2: 211
· value (SEGD) DFM: 139
· number, SEGD DFM: 128
· type, format, density (SPS) Tilt Model
DFM: 11, DFM: 21, · create FM2: 43, FM2: 110
DFM: 51, DFM: 62 · WTU parameters, load FM2: 76
Tape/disk identifier (SPS) DFM: 9, Time
DFM: 18, DFM: 49, DFM: 58 · delay, FTB-SOD (SPS) DFM: 11,
DFM: 21, DFM: 51,
Taper
DFM: 62
· length start, end (SPS) DFM: 13,
· exponential, trace display
DFM: 24, DFM: 53,
FM1: 433
DFM: 65
· SPS DFM: 15, DFM: 27,
TB DFM: 55, DFM: 68
· window, SEGD DFM: 122
Time break
Tb to T0 time (SEGD) DFM: 126 · SEGD DFM: 123
Test · window, SEGD DFM: 133
· Record, type (SEGD) DFM: 123 To channel (SPS) DFM: 16,
· Spread FM1: 87
DFM: 29, DFM: 57, DFM: 70
Tests
To receiver (SPS) DFM: 17,
· on request FM2: 83
DFM: 29, DFM: 57, DFM: 71
Text
· box FM2: 4
Toggle
· button FM2: 4
Text file
378
Index
>
Topo view · Live seis DFM: 122

· Complete window FM2: 107 · Seismic DFM: 122
· Data Harvester FM2: 314 Trailer, general DFM: 116
Total number of traces (SEGD) Type
DFM: 122 · Model, Polarity (SPS) DFM: 11,
Towing depth DFM: 25, DFM: 66 DFM: 12, DFM: 13,
Trace DFM: 21, DFM: 23,
· blocking FM2: 212 DFM: 24, DFM: 51,
· data block DFM: 131 DFM: 52, DFM: 53,
· edit (SEGD) DFM: 133 DFM: 62, DFM: 64,
· Number (SEGD) DFM: 133 DFM: 65
· number of samples in DFM: 122 · of process (SEGD) DFM: 127
Trace Header · of source (SEGD) DFM: 122
· Extension (SEGD) DFM: 133
· Extension Block 1 (SEGD) U
DFM: 134
· Extension block 2 (SEGD)
Unit
· serial number (SEGD) DFM: 142
DFM: 137
· type (SEGD) DFM: 142
· Extension block 3 (SEGD)
DFM: 139 Units
· Extension block 4 (SEGD) · spacing X, Y (SPS) DFM: 12,
DFM: 140 DFM: 13, DFM: 23,
· Extension block 5 (SEGD) DFM: 24, DFM: 52,
DFM: 141 DFM: 53, DFM: 64,
· Extension block 6 (SEGD) DFM: 65
DFM: 142 Updating
· Extension block 7 (SEGD) · stake ID FM2: 118
DFM: 145 Uphole
· Extensions (SEGD) DFM: 121, · time (SEGD) DFM: 123
DFM: 134 · time (SPS) DFM: 15, DFM: 26,
· SEGD DFM: 133 DFM: 55, DFM: 67
Traces URL
· total number of DFM: 122 · opening a session FM1: 4
Traces, number of
· Aux DFM: 122
· Dead seis DFM: 122

Index
> 12
V WTU
· parameters, loading FM2: 93
VE464 · position, load to Position
· connecting IM: 38 FM2: 167
Vertical WTU assignment
· datum description (SPS) DFM: 9, · Automatic checks FM2: 183
DFM: 19, DFM: 49, WTU list
DFM: 60 · import from PFT FM2: 286
· Stack (SEGD) DFM: 121 WTU parameters
Vibrator · group, create FM2: 89
· type (SEGD) DFM: 117 · summary FM2: 73
Vibroseis (SPS) DFM: 13,
DFM: 53
View Y
· Topo, Complete window Year (SEGD) DFM: 113
FM2: 107
· Topo, Data Harvester FM2: 314
VP
· Process FM2: 41
W
Wake up
· time, WTU FM2: 85
Water
· depth (SPS) DFM: 15,
DFM: 26, DFM: 55,
DFM: 67
· gun (SPS) DFM: 14, DFM: 54
Weathering thickness (SPS)
DFM: 14, DFM: 25, DFM: 54,
DFM: 66
Weekly calendar FM2: 84
Window
· TB DFM: 122
Working hours FM2: 84
380

508XT V2 1 DCM Functional Vol2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

508XT V2 1 DCM Functional Vol2

Uploaded by

Copyright:

Available Formats

XT

Ref. 10048022 AA February 5, 2020

Figure 2-1 My Sercel Homepage

Click here to request a My Sercel account. http://customer.sercel.com or use the

Import and Export.

Intellectual property rights, patents and copyrights to Software.

(Page intentionally blank)

Date of Manual Chapters or Description of revision or reason for

3 Data Completion Manager (DCM) Interface

7 SEG-D File Generator (SEG-D Gen)

8 SEG-D Import Key Points

9 Portable Field Terminal

11 Glossary of abbreviations and acronyms

This chapter includes the following sections:

• DCM Overview (page 16)

508XT Functional Manual

508XT System Documentation

Terminology and conventions

Working with DCM windows

Selecting table rows

Copy and Paste

This chapter includes the following sections:

• Opening a DCM user session (page 22)

508XT Functional Manual

Opening a DCM user session

Figure 2-1 DCM icon

2. The connection window is displayed.

Figure 2-2 DCM Server Connection Window

Figure 2-3 Customize IP address button

4. If the Customize IP Address button is selected, the Connection configuration screen

Figure 2-4 Connection configuration

Figure 2-5 Configuration settings

7. The connection to the DCM Server will begin.

Figure 2-6 DCM Server connection

8. The DCM interface is now connected.

Starting/stopping the DCM server

Figure 2-7 Stop DCM Server

Figure 2-8 Start DCM server

Updating Software Patches

3. Select the Patches that you would like to install.

Figure 2-10 Start DCM Patch Installer

4. Click Install New Patches.

DCM Graphic Interface

Figure 2-11 DCM launch icon

Figure 2-14 Tiled views

Drag and drop

• A filter icon indicated to the user the filtered columns.

Using DCM with 508XT

At least one Auxiliary FDU

Figure 2-19 Field Unit parameters

Figure 2-20 Scanning WTU serial numbers

3. Launch DCM (see Opening a DCM user session on page 22).

Figure 2-21 Loading WTU list

Figure 2-22 Topo view

Figure 2-23 Assign Markers dialogue

Figure 2-25 XT-Pathfinder network

The XT-Pathfinder network performs three key functions, as explained below.

Figure 2-26 GPS position acquisition

Figure 2-27 XT-Pathfinder network real-time monitoring

Real-time alerts are provided for the following parameters:

Figure 2-28 Continuous monitoring

(Page intentionally blank)

3 Data Completion Manager