MWD Ops

g GE Energy
GE Tensor
MWD Operations Manual
SERIAL NUMBER:
Client Company:
THIS MANUAL CONTAINS PROPRIETARY

INFORMATION THAT MAY NOT BE
DISCLOSED TO OTHERS, REPRODUCED
OR USED WITHOUT WRITTEN
AUTHORITY FROM
GE ENERGY
1840 ROYSTON LANE
ROUND ROCK, TEXAS 78664
This document is an unpublished work. Copyright 1994, 2003 (Revised) GE Energy. All rights reserved. “This
document and all information and expression contained herein are the property of GE Energy and is provided to the
recipient in confidence on a ‘need to know’ basis. Your use of this document is strictly limited to a legitimate business
purpose requiring the information contained herein. Your use of this document constitutes acceptance of these terms.”
g GE Energy
This document is an unpublished work. Copyright 1994, 2003 (Revised) GE Energy. All rights reserved. “This
document and all information and expression contained herein are the property of GE Energy and is provided to the
recipient in confidence on a ‘need to know’ basis. Your use of this document is strictly limited to a legitimate business
purpose requiring the information contained herein. Your use of this document constitutes acceptance of these terms.”
g GE Power Systems
1840 Royston Lane

Round Rock, Texas 78664
(512) 251-4131
(512) 252-6150 (FAX)
MWD Operations Manual
01 Variable Units Definition Utility

02 qMWDCnfg™ Tensor MWD Software System Configuration Utility
03 Tensor MWD Toolface Offset Procedure
04 Tensor MWD qMWDW32™ Real Time System Interface
05 Tensor MWD Driller’s Remote Terminal Rig Floor Display
06 Tensor MWD qW32 Server qTalk Procedures
07 Tensor MWD qProg/11 System Utilities
08 Tensor MWD qDirK_IOTM System Utility
09 Supporting Documents
a MWD Assembly Drawing
b Poppet Orifice Setting
c Surface System Setup
d Tensor MWD Flow Simulation Setup Diagram
e MWD Surface Gear
f MWD DPT Tracking Surface Gear
g Magnetic Spacing Chart
h MWD (1.875” OD) Fluid Velocity Chart
i SAI
j MWD Failure Troubleshooting
k MWD Failure Troubleshooting
i MWD Failure Troubleshooting Procedure
ii No Pulse Flowchart
iii Pulse but Data not Decoded Flowchart
iv Remove Tool from Drillstring Flowchart
v Pumps and Hydraulic Check Procedure (GEHYD00001
vi Remove Tool from Drillstring Procedure (GEPOH0001)
vii Resynchronization Procedure (GERHY0001)
viii Work Drill String Procedure (GEWDS0001)
ix Transducer Procedure (GEXDR001)
12 Tensor MWD Battery Manual
13 Memory_IO Utility Program Tensor MWD Memory Input & Output Program
14 Tensor MWD MWDRoll32 System Utility
g GE Power Systems
Notes:
g GE Power Systems
Variable Units Definition Utility
This document is an unpublished work. Copyright 1994, 2002 (Revised) GE Power Systems.
All rights reserved. “This document and all information and expression contained herein are the
property of GE Power Systems and is provided to the recipient in confidence on a “need to
know” basis. Your use of this document is strictly limited to a legitimate business purpose
requiring the information contained therein. Your use of this document constitutes acceptance of
these terms.”
N otes
Notes
2
Section 01
Version 2.00; February, 2002 VuDu
qVarUnit Variable Unit Definition Utility
General Operation
The Variable Units Definition Utility defines the units to be used

by Tensor MWD and Tensor Steering Tool applications. The units’
definition is stored in the system registry.
The utility allows the operator to perform the following actions:
· Select a predefined units definition.

· Modify a selected units definition.
· Save a selected units definition to a file.
· Load a units definition from a file.
· Broadcast a units' definition on the qBus (where applicable)
3
Section 01
When the variable units utility is first started it will display the
current units definition stored in the system registry. The
appropriate button at the top of the screen will be automatically
selected. The user may change any of the individual displayed
units by clicking on a dropdown box and selecting the desired
units. Additionally, units’ definitions may be loaded from a file by
clicking the button labeled Read File or by clicking one of the
preset buttons labeled Imperial, Metric, Custom, or Default.
When the desired units are displayed on the screen, the user may
save them in the system registry by clicking the Apply button.
Additionally, if qMIX-based MWD software is being used, a button
labeled Broadcast will be displayed. Clicking the Broadcast button
will cause the units definition to be broadcast to other applications
on the qBus. This button will not be displayed when it is
inapplicable. Note: the unit changes will not affect any qMWD/32
running applications when the changes are made or broadcast. The
qMWD/32 applications must be exited and restarted to allow the
application to access the settings in the registry and display the
proper units.
The displayed units definition may be saved to a file for use on

another computer by clicking the WriteFile button.
4
Section 01
Predefined Units Sets
Metric
Imperial
Default
Custom
Imperial
The predefined Imperial Set is selected by clicking the

button labeled Imperial at the top of the screen. The screen
will be updated to show the Imperial units.
Metric
The predefined Metric Set is selected by clicking the button

labeled Metric at the top of the screen. The screen will be
updated to show the Metric units.
Default
The predefined default set is selected by clicking the button

labeled Default at the top of the screen. The screen will be
updated to show the combination Imperial/Metric units that
have been in use since the inception of the qMWD program.
Custom
This option allows the operator to design an Imperial or

Metric Set to suit the location. Not all measurements use
the same Metric or Imperial units.
The predefined default set of units is the standard set of units for
qMWD™ that the system has been employing prior to the inception
of the VUDU.
5
Section 01
Command Buttons
Default
Clicking the Default button will always cause the units to report to
the default set.
To customize the selected units definition, click on the dropdown

box for a physical quantity and select one of the units listed.
Alternatively, you may load the units’ definition from a file.
Read File
Clicking the Read File button will display a dialog box prompting
you to select a file containing the units’ definition. Only files with
an extension of .VUD will be displayed. After reading the file, the
units displayed will be updated accordingly. Note that reading a
units definition file only changes the units displayed. The new
units will not be used unless the Apply button is clicked to save the
new units definition in the system registry.
Apply
Clicking the Apply button will cause the currently displayed units
definition to be stored in the system registry.
Broadcast
Clicking the Broadcast button will cause the currently displayed

units definition to be broadcast on the qBus. This button will only
be displayed when it is applicable.
6
Section 01
Write File
Clicking the Write File button will display a dialog box prompting
you to enter a filename for storing the current units definition.
This file will be stored with an extension of .VUD by default. The
resulting file may be transported to another computer and read with
the Read File button in order to configure more than one computer
with the same units definition.
Exit
Clicking the Exit button will allow you to exit the variable units
definition utility. If you have made changes to the selected units
without saving them or broadcasting them, where applicable, you
will be prompted to do so.
Note: All qMWD/32 applications running when the units are

changed will have to be exited and restarted to affect the changes in
the display units in the applications. The application must read the
settings in the registry when the application is started.
7
Section 01
Units Options and Selections
Length Newtons [N]

Centimeters [cm] Pounds [lb]
Feet [ft]
Inches [in] Energy, Work, Heat
Meters [m] Foot-Pounds [ft-lb]
Millimeters [mm] Joules [J]
Kilojoules [kJ]
Area Meter-Newtons [m-N]
Square Centimeters
[sq cm] Torque
Square Feet [sq ft] Dekanewton-Meters
Square Inches [sq in] [daN-m]
Square Meters [sq m] Kilonewton-Meters [kN-m]
Square Millimeters [sq mm] Newton-Meters [N-m]
Pound-Feet [lb-ft]
Volume
Barrels [bbl] Pressure
Cubic Centimeters [cc] Bars [bar]
Cubic Feet [cu ft] Kilopascals [kPa]
Cubic Meters [cu m] Pounds/Square Inch [PSI]
Gallons [gal]
Liters [l] Weight Density
Kilogram-Force/Cubic
Velocity Meter [kgf/cu]
Feet/Hour [ft/h] Kilogram-Force/Liter [kgf/l]
Kilometers/Hour [km/h] Pounds/Cubic Foot
Meters/Hour [m/h] [lb/cu ft]
Meters/Second [m/sec] Pounds/Gallon [lb/gal]
Plane Angle Electrical Resistivity

Degrees [deg] Ohm-Meter [ohm-m]
Angular Velocity Magnetic Induction

Revolutions/Minute [rpm] Gauss [Gauss]
Milligauss [mGauss]
Force Nanoteslas [nT]
Dekanewtons [daN] Webers/Square Meter [T]
Kilodekanewtons [kdN]
Kilograms-Force [kgf] Temperature
Kilonewtons [kN] Celsius [degC]
Kilopounds [klb] Fahrenheit [degF]
8
Section 01
Gravity
G’s [g]
Meters/Second/Second
[m/s/s] Electrical Conductivity
Milli-G [mg] Mhos/Meter [mho/m]
Millimhos/Meter [mmho/m]
Volume Rate Siemens/Meter [S/m]
Barrels/Minute [bbl/min]
Cubic Meters/Minute Inverse Linear Velocity
[cu m/min] Minutes/Foot [min/ft]
Gallons/Minute [gpm] Minutes/Meter [min/m]
Liters/Minute [l/min]
9
Section 01
N
NOOTTEES
S
10
Section 01
g GE Power Systems
qMWDCnfg 
Tensor MWD Software
SYSTEM CONFIGURATION UTILITY
This document is an unpublished work. Copyright 1994, 2002 (Revised) GE Power Systems. All
rights reserved. “This document and all information and expression contained herein are the property
of GE Power Systems and is provided to the recipient in confidence on a “need to know” basis. Your
use of this document is strictly limited to a legitimate business purpose requiring the information
contained therein. Your use of this document constitutes acceptance of these terms.”
NOTES
2
Section 02
Version 2.00; 01 February, 2001 CNFG
Table of Contents
TABLE OF CONTENTS ....................................................................................... 3
NOTICE................................................................................................................ 4
TITLE PAGE......................................................................................................... 5
Selecting a *.MWD File ............................................................................ 7
Configuration *.MWD File Control.......................................................... 7
A) ACCESS LEVELS,............................................................................................ 7
B) ACCESS CODES ............................................................................................. 7
C) AVAILABLE STORAGE MEDIUMS ...................................................................... 7
GETTING STARTED............................................................................................ 9
Setup Parameters Edit Screen................................................................ 10
Receiver Link Address & Transmitter Link Address ..................................... 10
Select Access Levels................................................................................ 13
Changing the Access Levels ................................................................... 14
Setup......................................................................................................... 17
Load .......................................................................................................... 18
Telemetry Controls Menu, Figure 1: ...................................................... 24
Special Telemetry Controls: ................................................................... 30
qMWD™ Coding, Detection and Decoding Processes ................................. 32
Mode Control Settings ............................................................................ 35
Survey Sequence Definitions ................................................................. 38
Toolface/Logging (T/L) Sequence Definitions ....................................... 39
Directional Data Variables....................................................................... 40
Telemetry Warnings ................................................................................ 43
Formation Data Variables ....................................................................... 44
Data Word Update Times ....................................................................... 45
Survey Duration Comparison Chart....................................................... 47
Job Site Environment Settings:.............................................................. 50
Directional Processing Controls: ............................................................ 53
Type 1 Computation: ............................................................................... 56
Type 2 Computation: ............................................................................... 56
Gamma/Battery Processing Controls:.................................................... 58
Pumps/Flow Evaluation Controls: .......................................................... 62
Mechanical Flow Switch Settings .................................................................. 64
InvF: “OFF” ...................................................................................................... 64
Electronic Flow Switch (EFS) ......................................................................... 64
Use InvF: “OFF” .............................................................................................. 64
Surface Receiver Controls:...................................................................... 65
Synch. Detection k-factors: .................................................................... 66
Depth Tracking Controls: ........................................................................ 67
Depth Tracking System for GE Power Systems Tensor MWD ............ 73
Changing the Hook-Position Scale Factor… ......................................... 79
Mud Flow/Rotary Drive/Generic Sensor Controls:................................ 85
Turbine Controls ...................................................................................... 88
Down Link Controls and Procedures:..................................................... 90
3
Section 02
NOTICE TO ALL qMWD/W32™ USERS!!
It is of the utmost importance for all users of this software package to

have a working knowledge of the latest versions of the Microsoft
Windows 95® & Microsoft Windows 98®, Microsoft Windows NT®,
Microsoft Windows 2000 & XP software platforms. The mechanics of
the qMWD/W32™ program were designed with this requirement in
mind.
Should a client require a uniform systematic approach for their

operations, a member of the client’s staff shall be trained to a level of
expertise capable to set the limits on the operational procedures of the
program.
GE Power Systems provides the software instruction to the user

involving the TOTAL CAPABILITIES of the program. QDT can present a
customized instructional format on a limited basis with advanced
notice. Each client must set their own requirements and limits and
must use the devices included in the software to tailor the format for
their particular use. Should a client require special adjustments to the
program, they must discuss these requirements with the management
of GE Power Systems, Round Rock, Texas. Advice shall be provided
to the client who desires and requires such needs during or after the
training schedule.
Experience has proven that managers of companies employing the

QDT MWD system must exert comprehensive control on the use of
the qMWDCnfg Program. For this reason, the Access Levels and
Access Codes are mentioned in the first part of this chapter. A lack of
control can lead to errors of operation developed in the field
environment and being passed on from one operator to another.
These errors can very possibly compound as the process evolves. It
is STRONGLY ADVISED and HIGHLY RECOMMENDED by GE
Power Systems that someone in the organization be assigned the
position of Systems Analysts and executes the duties of insuring and
maintaining the integrity of ALL releases operating in the field.
4
Section 02
Title Page
Initially, upon starting the program, the Title Page will appear. At
this point, the operator should depress the Enter Key or mouse
click on the Continue button. This will give the user access to the
necessary level to configure a file to define the operating variables.
Access Codes to the System Engineer level can be obtained from
GE Power Systems Technical Support.
5
Section 02
Configuration File Specification: Forced Setup
The program is intended to start in the forced startup routine.
The user is required to select a particular *.MWD configuration
file from the storage medium provided. The files are resident
in the default file folder –
C:\ProgramFiles\AlliedSignal,Inc\Software for Drilling
Applications\qMWDW32.
The user can design the system to search a particular drive or

storage medium to access the desired or prescribed *.MWD
configuration file.
Example: C:\JobNumber\ConfigFiles\DirOnly.MWD
or C:\JobNumber\ConfigFiles\GamDir.MWD
After selecting a particular *.MWD configuration file, the previous

Title Page will be displayed and the user can press Enter to
Continue.
6
Section 02
Selecting a *.MWD File
To select a particular file, simply double click on the desired file.

The file will be highlighted and opened into the qMWDCnfg
program. The program will then proceed to the Main Menu Screen.
Accessing the menu items will allow the operator to view all of the
variables allowed by the access Level appropriate to his Capability
Code.
Configuration *.MWD File Control
Experience has proven that managers of companies employing the

GE Power Systems Tensor MWD must exert comprehensive
control on the use of the qMWDCnfg Program. For this reason, the
Access Levels and Access Codes were mentioned in the first part
of this chapter. A lack of control can lead to errors of operation
developed in the field environment and being passed on from one
operator to another. These errors can very possibly compound as
the process evolves. It is STRONGLY ADVISED and HIGHLY
RECOMMENDED by GE Power Systems that someone in the
organization be assigned the position of Systems Analysts and
executes the duties of insuring and maintaining the integrity of ALL
releases operating in the field. This person should track all
configurations employed by the operators, and alleviate the
possibly of incorrect and inaccurate operating procedures, in
regards to the qMWDCnfg Program.
The program has numerous features available for insuring limited

access to the variables to the qMWDCnfg program in the field-
operating environment.
They are the

a) Access Levels,
b) Access Codes
c) The available storage mediums using controlled access
procedures.
These features can be located in the Setup procedures of the

program. Consult your manual or the GE Power System Technical
Support to assist in this setup.
(512) 252-6130.
7
Section 02
Introduction to qMWDCnfg TM
This program allows the operator to design program configurations

for the MWD probe and surface system that will meet the
requirements necessary to operate the MWD system successfully
in any environment suitable for MWD operation. This portion of the
manual will deal with every menu selection and detail the meanings
and definitions of each menu selection and number values listed.
Example screens are displayed and each entry is defined and
explained as to which entries shall be altered and what values
should not be altered.
The operator’s PC is only the system that contains the programs

necessary to configure the downhole probe and surface system. It
is NOT the primary operating system. The primary operating
system is contained in the Driller’s Remote Terminal. After storing
a configuration to the probe and the surface systems successively,
the PC may be used to monitor the MWD system and to store the
data measured and transmitted to the surface. The firmware and
configuration file variables stored to the multi-processors in the
transmitter (Node 20) and the surface receiver (Nodes 05 and 09)
are written into a non-volatile memory. Therefore, when power is
removed from the processors, the configuration last stored to the
system will be resident and remain there, until the ‘store to’
command is performed again for that particular multi-processor.
Access to the qMWDCnfg program can be controlled by setting the

Access Levels of the desired variables to the particular levels
available in the program. The levels can be set to allow total and
complete access by anyone starting the program. Alternatively, by
carefully setting the Access Levels, entry into the program can be
controlled by assigning specific Access Codes to the particular
levels of operator training. This protects the integrity of the
configuration designs used by a particular GE Power Systems
Tensor MWD user. The more advanced and highly trained
operators should be allowed more in depth access to the program.
This is to allow alterations necessary for smoother and more
flexible configuration design.
8
Section 02
Getting Started
After entering the correct Access Code, the following Main Menu
screen will be displayed. For the initial default setup, the Access
Code is any number. This allows any operator limited access to
the variables available for configuring the MWD system. This
screen allows access to the variables and settings required for
configuring the MWD system properly. Remember that access to
the program is determined by the Capability Level assigned to
particular Access Codes. Refer to Setup for instructions to design
the desired setup.
To be able to total access to the configuration system, please call

GE Power Systems Customer Support and request the code for
total access. The code for total access will be given only to the
Systems Analyst or MWD manager.
9
Section 02
Setup Parameters Edit Screen
The Setup Parameters Edit Screen is designed to allow the

Systems Analyst the ability to adjust the operating parameters of
the program to read, load and write the *.MWD configuration files to
particular file folders. It will also enable auto verification of the load
process, enable the particular load routine for accessing the *.MWD
configuration files on boot-up, and enable depth tracking.
Receiver Link Address & Transmitter Link Address

THE FIRST THREE VARIABLES MUST REMAIN AS THEY ARE, AND NEVER
CHANGE. Future releases will not allow any alteration to these
values. The receiver link address and the transmitter link address
must always remain as given. Node address conventions are
required for the proper operation of the system.
(MPRx) Receiver Link Address: 05 (MUST ALWAYS BE 5)

(MPTx) Transmitter Link Address: 20 (MUST ALWAYS BE 20)
Turbine Controls/Recorder Link Address: 29 (MUST ALWAYS BE 29)
10
Section 02
Default Configuration Read/Write/, for W32 operating systems:
The File Paths are loaded to the system in this format from the
original installation of the program. If the systems analyst desires
to alter this path, then the path will be entered here. Example:
A:\File Folder Name\ or C:\JobNumber\CnfgFileName.MWD.
Note, when a file is being accessed, for loading to the program, the
path can be selected from the dialog by selecting the drive and the
file folders desired. The operator must know the path used to
locate these files or can use Find to locate any and all *.MWD files.
Filter for Config. File Directories: This string describes a filter

that is used when obtaining File Directories of Config. files. A file
name must be given, when loading or storing files from or to Disk.
In the given example, it will be all of the files in the “\qMWDW32\”
subfolder of the Program Files file folder, listed by any name, but
ending with the Extension “.MWD”. The asterisks “*” denotes a wild
card and instructs the program to select all files in that folder ending
with the extension of MWD.
Auto Verify, Label: AVer, Select an Option: When enabled, this

switch causes data that is stored to the processors to be read back
and verified. If any errors are found, they are displayed on the
screen. It is advisable to keep this switch enabled.
Configuration File Name, Label: CfgF, Edit String: This is the

name of the configuration file to be loaded when the program is
booted, when the Configuration Load Option is “Fixed” or “Last”. It
is also the name of the configuration file currently loaded in to the
configuration program.
Configuration Load Option Switch, CfgL, Select an Option:

This gives the operator the option to select the method in which
specific configuration programs will be selected to be loaded into
the program upon booting the configuration program.
1. “Fixed” - The file named in the ‘Configuration File Name’

above. If there were but one configuration being used by the
operation, then this option would limit the operators to using
the one configuration.
2. “Last” - The last file ACCESSED, either READ IN or

WRITTEN OUT. NOTE: It is possible that it is not the last
file that was necessarily stored to the probe or receiver, so
this option should be selected with great caution.
11
Section 02
3. “Forced” - This switch forces the user to select a
file from the configuration file menu before the
program is booted. This switch is suggested to be the
most reliable to prevent an operator from loading the
improper data by mistake.
NOTE: If the “Last” or “Fixed” options are selected and the

configuration file does not exist, qMWDCnfg first looks for the
default file “qMWDCnfg.MWD” and loads it if it exists. Otherwise, a
warning message is displayed on the screen and hard coded
default values are loaded.
Serial/ Release Number, Label: SrlN, Edit String: This is a

unique number that helps to identify the software versions being
used. This is necessary information when calling in for support.
Copy the version release number from the disks used to load the
software on the PC.
Depth Tracking Controls, Label DTE, Select an Option: This

variable enables/disables viewing, editing, and
uploading/downloading of control variables specific to Depth
tracking. If the PC is NOT connected to a Remote terminal with
Depth Tracking firmware and sensors, then this option should be
set to ‘DISABLE’. If the system is connected to a working depth
tracking surface gear, then this option can be set to ‘ENABLE’,
without causing any operating problems. The program will activate
the Depth Tracking parameters without reentering the capability
code.
Turbine Controls, Label TuEn, Select an Option: This variable

enables/Disables viewing, editing, and uploading/downloading of
control variables specific to the Turbine Control and Recorder node.
If the PC is not connected to a downhole System with a turbine,
then this option should be set to “Disable”. If the PC is connected
to a working turbine node, then this option should be set to
“Enable”.
12
Section 02
Select Access Levels
The second option under the Setup label in the drag-down menu is
the Variable Access Specification Screen. Click on the Access Level
label to display window showing Variable Access Levels for each of
the variables available. The variable displayed indicates the access
level that an operator must use to be able to either read the contents
or write (change) the contents of the variable. Every variable
displayed in the qMWDCnfg program is displayed in this screen by
scrolling down the page.
13
Section 02
Changing the Access Levels
To change the level of the read/write options, the operator needs to

double click on the variable to be changed. This will display the
pop-up screen to edit the particular variable highlighted. Select the
desired level that will insure the proper operator access to the
program. Select OK when finished for each variable. Continue the
process for each variable.
It is recommended that for the variables always requiring viewing

(Read) by the operator, to be set to a value of zero (0). This will
give the operator access to these variables for viewing, regardless
of the Access Code entered. Not all variables, obviously, will
require changing (Write), and will not correspond to the variables
that necessarily requiring viewing. However, for those particular
variables that will require operator input on the job, the write Access
Level should also be put at zero (0). Again, regardless of the
Access Code entered, he will have access to these variables. This
will simplify the need for various Access Codes to particular
operators. Assistance in setting up this system is available from
GE Power Systems Technical Services Specialist.
14
Section 02
Capability Codes
These changes in the Access Levels and the Capability Codes will
give a modicum of protection from operators accessing variables
that can only impair the system operations. Maintaining the
Capability Code of 11, but placing it in the General user-Default
level, will still give the general user access to the variables he
needs to perform his job. However, this is not entirely necessary,
since the default value will accept practically any number (except
the ones used for other levels) to access the default variables.
These changes will be transparent to the operator. The change of
the Capability Code for Level 11 – System Engineer, to the value of
xx will still maintain a level of access for the technician at that level.
It is recommended that the System Engineer select a number that
will be easy to remember in the range of –32768 and 32767.
15
Section 02
File
Clicking on the header label File will reveal a drop down menu
allowing you to:
Open...
This command will display the Load from Disk splash to load a
configuration file (*.MWD) from the hard drive initially. As is the
practice with Win 95, you are allowed to select a different file
medium, if so desired. It does not access the Load/Store options
for Loading from the MPTx or the MPRx.
Save as…
This command will display the Store to Disk splash to store a
configuration file (*.MWD) from the hard drive initially. As is the
practice with Win 95, you are allowed to select a different file
medium, if so desired. It does not access the Load/Store options
for Storing to the MPTx or the MPRx.
Print…
This command will automatically send the *.MWD file displayed on
the PC to the printer in the normal print format. It will also name the
source of the file displayed, unless altered by an entry in the file.
Exit…
This command will exit the qMWD 32 PC program.
View
Clicking on the header label View will reveal a drop down menu
allowing you to:
Status Bar…
Toggle the view of the Status Bar. The Status Bar will assist you in
describing functions that are highlighted.
16
Section 02
Setup
Clicking on the header label Setup will reveal a drop down menu
allowing you to:
Operating Parameters… Clicking on the sub menu,

Operating Parameters, will give you access to the Setup
Parameters Edit Screen.
Access Levels… Clicking on the sub menu, Access

Levels, will give you access to the Variable Access
Specification screen.
Capability Codes… Clicking on the sub menu,

Capability Codes, will give you access to the Capability Code
Specification screen.
Save Current Setup… Clicking on the sub menu, Save

Current Setup, will save the qMWDCnfg Setup parameters
to a file.
17
Section 02
Load
Clicking on the header label, Load, will reveal a drop down menu
allowing you to manipulate configuration files for loading data. The
files can be loaded from several mediums to and from the surface
receiver, the downhole probe and/or the turbine processor, if such a
module is used.
Load from…
Disk
Clicking on the Disk label will reveal a Load from Disk window that
will allow the operator access to all storage mediums available on
the PC.
18
Section 02
Transmitter – Clicking on the Transmitter label will reveal the
Win95 warning dialog box.
Receiver – Clicking on the Receiver label will reveal the Win95

warning dialog box.
19
Section 02
Store
Clicking on the header label Store will reveal a drop down menu
allowing you to:
Disk – Clicking on the Disk label will reveal a Store to Disk window
that will allow the operator access to all storage mediums available
on the PC.
20
Section 02
Receiver and Transmitter – Clicking on both of these options will
reveal the Windows warning dialog box. Note, the system will
begin storing to the receiver then automatically continue to start
storing to the transmitter.
Receiver – Clicking on this menu option will reveal the Windows

dialog box.
Transmitter – Clicking on the Transmitter label will reveal the

Windows warning dialog box.
21
Section 02
Load and Go
Clicking on the header label Load and Go will reveal a drop down
menu allowing you to:
Select a configuration file, load the file to the PC and then store that
configuration file, without viewing it, to the Rx and Tx.
Receiver and Transmitter – The system will first store the

configuration file to the receiver and then continue to the
transmitter.
22
Section 02
Transmitter – The system will store the configuration file only to
the transmitter.
Receiver – The system will store the configuration file only to the
receiver.
23
Section 02
Telemetry Controls Menu, Figure 1:
These controls allow observation and editing of the variables that

define the basic format of the telemetry envelope and are used by
the down link communications process in both the downhole
transmitter and surface receiver. They also define the controls for
setting the change over inclination for transmitting gravity or
magnetic toolface data values.
24
Section 02
Receive Delay Time (RxDT), Units: Seconds, Limits: 10 to 120:
This variable determines the receiver delay time control that
specifies the delay required from Pumps On detection until the
receiver begins detecting signals or looking for synch. This delay
should be set long enough to allow the pumps adequate time to
attain the required strokes per minute and for the standpipe
pressure to become steady. This will avoid an errant “synch” on
any pump noise or stand pipe fluctuations. In addition, the operator
should insure that there is NO LESS than a 5-second differential
between the RxDT and the TxDT. (i.e. RxDT is 5 seconds LESS
THAN TxDT. This variable selection will improve with the
experience of the operator. NOTE: if the receive delay time is short
in comparison to the down link time period (DLTP) and a Downlink
command interpretation is pending, the RxDT will automatically and
appropriately be extended.
Transmit Delay Time (TxDT), Units: Seconds, Limits: 15 to 120:

This variable determines the transmit delay time control that
specifies the delay required from Flow On detection until the
downhole tool telemetry transmissions commence. It is suggested
that at the beginning of all jobs, this variable should be set to no
less than 60 seconds, to allow the pumps the time to reach the
required SPM and for the SPP to become steady. As before, this
variable can be adjusted with more experience by the operator.
Again, refer to the RxDT for the proper time differential. It should
be set to NO LESS than 5 seconds LATER than the Receive Delay
Time (RxDT) variable. If the TxDT is short in comparison to the
DownLink time, (DLTP) and a DownLink command interpretation is
pending, then the TxDT will automatically and appropriately be
extended.
If the RxDT and TxDT variables are set too close together, or if the
TxDT is set for a delay time of longer than the RxDT, the following
dialog box will be displayed.
25
Section 02
Synch Window Factor (SyWF), Units: Decimal Minutes, Limits:
1.25 to 100.00 and 0: This is the period of time, relative to when the
RxDT period has expired, that defines when the receiver will indicate
that it has missed synch. That is, IF a synch word has not been
detected. The length of the Synch word is a function of the Pulse
Width (3X PW for the Alert Pulse) and the number of singlewide pulse
symbols (Synch Pulses) in the word. The Synch Window Factor
defines the window Period as a multiple of Synch Word Periods to
compute the Synch Window Period. The receiver compensates for all
detection latencies and the value of TxDT-RxDT. A value of zero (0)
indicates an Infinite Synch Window for the duration of "Pumps
On" and is the suggested preference, unless the operator prefers to
limit the receivers search for a synch.
Number of Synch Pulses (NSyP), Units: Pulses, Limits: 3 to 8:

This variable defines the number of singlewide pulses in a synch
word. A Synch Word consists of a Triple Wide (3X) pulse followed
by 3 to 8 singlewide (1X) pulses, as defined by this variable. Each
pulse in the Synch Word is separated by a gap, equivalent in time,
to two (2) “1X” pulse widths. The minimum number of pulses
required is three. Under adverse noise conditions, increasing the
number of singlewide synch pulses will reduce the noise effects and
improve the accuracy of the initial synchronization timing. The
synchronization accuracy is continuously improved with each data
pulse received. As any inaccuracies in the “initial estimate” of
synch timing are removed, Word Quality Factors, “WdQF”, and
Average Word Quality Factors, “AvQF”, will improve with time.
Survey Header Size (SHSz), Units: Bits, Limits: 3 to 8 and 0:

This variable defines the number of bits in a survey header. It is
recommended to use the minimum value of three. Setting the
value to zero (0) defines that no Survey Header will be transmitted.
The survey header is the method used by the system to distinguish
the two types of data being sent.
Toolface/Logging Header Size (THSz), Units: Bits, Limits: 3 to

8 and 0: this variable defines the number of bits in the
Toolface/Logging Header. It is recommended to use the minimum
value of three. Setting the value to zero (0) defines that no
Toolface/Logging header will be transmitted.
26
Section 02
Type of Header Check Bit (s) (HdCk), Select an Option: The
“HdCk” variable defines the type of check bits, if any, which are to
be appended to both the Survey and Toolface/Logging Header
words. “Parity” requires a single additional bit per header word.
“ECC” appends an “Error Correction Code” to the headers
consisting of two Bits for headers with 3 to 7 bits and three bits for
headers with eight bits. In a noisy surface environment, it is
important to place check bits on the headers. Should the HdCk not
be recognized, then all of the data following the header will be
meaningless (un-decodable). It is a small price to pay in time to
insure that the data at least has a good chance to be identified.
Down Link Commands (DwnL): This switch ENABLES or

DISABLES the Down Link capabilities of the MWD system. If the
operator is not versed in the use of the DownLink commands, or
has not performed the service, then he should always switch the
system to the DISABLED mode. Practice with the simulator or a
flow loop is highly recommended before attempting the practice in
the field. Refer to the Down Linking Commands at the end of the
chapter.
Command Time Period (DLTP), Units: Seconds, Limits: 15 to

120: This selection is not operable if DwnL is DISABLED. This
variable defines the maximum length of a DOWN LINK pulse
(PUMPS UP) and the maximum length of the FLOW OFF (PUMPS
OFF) command value intervals or windows. COMMANDS are
determined by the number of DOWN LINK pulses, spaced apart by
equal PUMP DOWN intervals. NOTE: the last FLOW OFF
INTERVAL between the LAST DOWN LINK pulse and the next
PUMPS UP to continue operations determines the VALUE of the
command (N x DLTP). This FLOW OFF period is usually longer
than the value of DLTP. The COMMAND Value requires a NO
FLOW period of N x DLTP with a tolerance of ±0.5 x DLTP. For
example, if a Mode Number change, from Mode 1 to Mode 4, was
required, then the Command Number would be 2, consisting of 2
Pumps Up with 1 (one) equal (in Time) Pumps Down, with a
Command Value of 4, with a DLTP = 60 seconds. Then the timing
sequence, to effect the change would be: Pumps Up of a time >
FEvt but < DLTP, i.e. for approximately 40 seconds to allow for flow
and pressure to steady and to insure adequate time for rig
inadequacies. Pumps Off for the same amount of time and on
again for the same amount of time. Then leave pumps down for a
Command Value of 240 seconds, ± 30 seconds, or bring the pumps
27
Section 02
up anywhere after 210 seconds (3 minutes & 30 seconds) but
before 270 seconds (4 minutes & 30 seconds). This would effect
the change in both the MWD tool and the DRT.
Command Set (DLTy): This control variable defines the types of

commands enabled for DownLink transmission. This control
effectively redefines the DownLink command numbers and values.
If DwnL is DISABLED the setting for this variable is not activated. If
the operator intends to use the DownLink commands, then this
variable should be set to the type of command desired for the
operation.
Mode Number (ModN): This switch will allow the operator to

change to any of the four different modes of operation. In
this case, each mode defines the Pulse Width, Survey and
T/L Sequence Numbers, Acquisition Time, and T/L Transmit
Time. NOTE: the operator is limited to changing only the
Modes, not the individual settings in each mode. Therefore,
the operator should pay extra special attention to the design
and selection of the modes that he plans to institute in the
program before the tool is programmed for downhole
operation.
Rate/Sequence: This switch will allow the operator more
flexibility in changing the operation of the tool. There are
three options that will allow the operator to change: (A) Only
the pulse width, (B) Only the T/L sequence, or (C) Only the
survey sequence number. The operator can change all
three by stepping through the change procedures and
commanding the MWD tool/surface, sensors to change each
particular phase to fine tune the operation. It must be noted,
however, that this procedure will take an excessive amount
of time. It is highly recommended NOT to use this option
due to use of the EFS that may cause a DownLink command
to the tool while tripping into the hole. Due to the numerous
options available it would be too time consuming to downlink
all three options to get back to where the tool was originally
set when tripped into the hole.
28
Section 02
Inclination Threshold (IncT), Units: Angle Degrees, Limits: 0.0°
to 45.0°: This control defines the inclination threshold for selecting
either gravity or magnetic toolface values for use in the Auto
Toolface Angle (aTFA) or Auto Pseudo Toolface Angle (pTFA).
Note the tool will not switch unless it measures an inclination equal
to or greater than this variable. This variable should be discussed
with the directional driller on location prior to configuring the tool,
since many of them have their preference to when to make the
switch. If there is an increased chance of magnetic interference,
due to the tool being in the casing at kickoff or near by wells on an
offshore platform, then the IncT can be set to 1.0° or less. The
gravity toolface is not affected by magnetic interference and will be
accurate to ±20°, until the inclination reaches 2.0° in which case the
toolface will be accurate to ± 10°. This practice should be used
only when the direction of the hole or casing is known and a gravity
Toolface can be used with confidence. This practice has been field
tested with success.
Evaluation Mode (EvIM): Selecting an option will give you the

choice of the tool evaluating the inclination only in Survey Data
Sequences or during both the Survey and the Toolface/Logging
Sequences. It is strongly suggested that the operator select the
“Survey” option to insure that the tool will not switch back and forth
while on bottom drilling. Noise and vibration will affect the
inclination measurement while drilling. By selecting the “Survey”,
position the tool will continue to send only Magnetic Toolfaces until
after a survey is taken and the inclination measured is greater than
the threshold limit selected, and then it will transmit Gravity
toolface. The opposite will occur when the threshold is crossed
from the ‘greater than the threshold value’, to the ‘lesser than the
threshold value’, but only after a survey is measured. The MWD
operator should be aware of this value and be alert to the position
of the well and inform the directional driller and the driller of the
impending changes that will occur when the threshold is crossed in
its respective directions.
29
Section 02
Special Telemetry Controls:
This screen allows the observation and editing of parameters that

define the type of synch word generated by the pulser and that define
the electrical input pulse widths that relate to the 10 selectable
hydraulic output pulses. Please note that the PWin parameters
relate ONLY to non-GE Power Systems Tensor MWD
manufactured pulsers.
Synch Word Type/Format (SyTy), Label: SyTy Select an Option:
This variable defines the type of synch word as generated by the
pulser.
The default “3111” value defines a triple-wide pulse followed by

3 to 8 single wide pulses, defined by NSyP, as the standard
synch sequence. This is the standard pulser synch sequence
employed by the QDT pulser.
30
Section 02
The “1111” value defines a singlewide pulse followed by three
to 8 singlewide pulses as an optional sequence. Selecting this
option may be necessary if you are using a non-standard pulser
that is UNABLE to generate a triple-wide pulse. It has been
proven in field use, that should noise be a factor to cause the
triple-wide pulse not to be decoded, then this sequence could
remedy the problem. Refer below.
Note for ALL GE Power Systems Tensor MWD clients.
Selecting the “1111” option will not reduce the time necessary
for achieving Synch. The standard “3111” synch type, using the
standard triple-wide pulse followed by 3 single pulses, will utilize
28 time slots, compared to 32 time slots utilized by “1111” synch
type. It has been found that in severe noise environments,
where the triple wide pulse signal-to-noise ratio is very small,
the single wide alert pulse (1111) allows improved recognition of
the alert pulse. The PWin values also have to be matched for
proper operation with the GE Power Systems Tensor MWD.
Pulser Drive Signal Widths (PWin): 0.250, 0.375, 0.500, 0.600,

0.800, 1.000, 1.200, 1.500, 2.000, and 3.000. Label: PWin, Units:
Seconds, Limits: 0.050 to 0.250: These variables define the
length of the electrical input signals to the pulser that correspond to
the 10 different output pulse lengths that are defined in the right
hand column. Refer to Engineers Reference Manual for more
information.
Note for ALL GE Power Systems Tensor MWD clients: DO NOT

CHANGE THE PWin VALUES! Option these variables out, using the
Capability Codes and the Access Levels at least to a view only level.
31
Section 02
qMWD™ Coding, Detection and Decoding Processes
1. Background
A large number of different coding schemes have been used for
encoding MWD mud pulse signals. A paper by Steve Monroe (SPE
20326,1990) discusses the relative advantages and disadvantages of
many of these methods, especially with regard to their “Data Rate”
(data bits per second), “Pulse Rate” (pulses per data byte), and
“Signal Efficiency” (data bits per pulse). The method that GE Power
Systems uses is not discussed in Steve Monroe’s paper but has a
name similar to one described in the paper. We call our coding
method “M-ary Coding”. We have chosen this method for its
reasonable combination of good data rate, and good signal efficiency,
as well as some desirable characteristics related to having to detect
only a single pulse in the presence of noise.
2. “M-ary Coding”
The GE Power Systems Tensor MWD coding method involves
breaking up any data word into combinations of two (2) and three (3)
bit symbols, each encoded by locating a single pulse in one-of-four or
one-of-eight possible time slots. An example for the case of an 8-bit
word encoding a value of 221 is shown below:
Word Value: 221; Maximum Value: 255;

Digital Value: 128 64|32 16 8 |4 2 1
1 1 | 0 1 1 |1 0 1
This encodes in “M-ary” as 3,3,5 where the first 3 comes from the
symbol containing 11, the two most significant bits of the digital word,
then 3 from the next symbol, 011, and the final 5 from the 3 bit
symbol, 101. Visually this can be shown as:
| | | | | | | | | | | | | | | | | | | | | | | | | | |
3 PP2107 6 5 4 3 PP21076 5 P P43 2 1 0
START OF DATA WORD END
where the pulses are transmitted most significant first.
In the above example we have chosen to use the time slots (time
resolution-intervals) equal to one half the pulse width, and have
allowed for a full pulse width (two-slot) pulse-interference-gap (PIG) or
recovery time after each pulse. These choices were mainly based on
earlier modeling and experimental work (Marsh, Fraser and Holt: SPE
17787, 1988). One important feature of this method is that we have to
find only the best single pulse in a window containing four or eight
possible locations for the pulse. This feature increases the
32
Section 02
robustness of the detection process at the expense of data rate and
signal efficiency.
3. Synchronization of the Detection and Decoding Processes

with the Transmitted Signals.
The GE Power Systems Tensor MWD uses a triple wide pulse
followed by three to eight singlewide pulses to provide a method of
synchronizing the surface equipment to the transmitted data
sequences. The surface receiver equipment functions by looking for
one received pulse, matched to the shape of the triple-wide pulse,
followed by establishing a time base derived from the received
positions in time of the three or more single-wide pulses. The receiver
also utilizes a tracking loop that removes clock drift, by slowly
adjusting the surface timing based on the average location in time of
the received pulses.
4. Pulse Detection
The GE Power Systems Tensor MWD surface receiver uses the
cascade of a simple front-end analog-roofing filter, followed by a steep
cut off tunable low pass filter, followed by a matched filter executed in
software. This methodology is discussed in the paper by Marsh, et.
al., mentioned above. The matched filter has been shown to be the
optimum filter for detecting signals corrupted by additive white
Gaussian noise under a wide variety of criteria. Use of the matched
filter has proven effective in many different MWD systems over the
years. The GE Power Systems Tensor MWD software has the ability
to shift the tunable filter edge during operation to help reduce the
effect of inband interference. For those cases where the
noise/interference is concentrated in the upper portion of the
passband, manually lowering the “low pass” cutoff frequency will
reduce the noise/interference faster than it reduces the signal. This
can result in enhanced signal detection quality. The results of the
pulse detection process are the location in time of the centroid of the
“best” pulse located in the allowed time window, its amplitude and
other characteristics. In case multiple pulses are detected in the
allowed symbol window, an evaluation process is started which may
enable the correct pulse to be selected. A description of this process
contained in the qMWD Engineer’s Reference Manual, (Green Book)
Section 2.4.5.2.
33
Section 02
5. Decoding Process
After each pulse is detected, the value of the symbol corresponding to
its location is determined. When all the expected pulses making up a
data word have been received, the decoded value is reported to the
receiver display and logging functions. The receiver display maintains
files containing all decoded data words, pulse data buffers (contains
the characteristics of all detected and suspect detected pulses), and
pulse waveform records, (contains a stripchart vs. time of the output of
the matched filter process).
6. Parity Check and Error Correction Code

Each data word and header (if used) can be encoded with parity or
error correction code symbols added to the data. The parity check will
detect a single one-slot pulse position error contained in the detected
data word. The error correction code will detect a single two-slot
pulse position error, and correct a single one-slot pulse position error.
The single slot error in pulse location is the most likely form of error
source to be expected in the received signal.
7. Other System Capabilities

The GE Power Systems Tensor MWD Engineer’s Reference Manual
describes in detail many system attributes. Such as the ability to
detect either, positive or negative pressure pulses, with the wide
variety of available formats for data words. DownLinking provides the
ability to change almost any parameter of the tool while downhole, by
using a series of timed flow off and on sequences. The system has
been used to successfully encode and decode several other
proprietary signal formats.
GE Power Systems – QSI-TN93379 12 October 1993
34
Section 02
Mode Control Settings
These settings work in conjunction with the two following menu

definitions. These settings must carefully be selected to properly
program the downhole probe and the surface system. The proper
Mode Number must be selected to set the pulse width, survey
sequence, Toolface sequence, acquisition times and transmit times
for the Toolface.
Mode Number (ModN): This mode should be carefully selected to

match the transmission mode desired for the operation that will be
run. The mode number variable determines one of four (or more)
modes of operation based on the control variables contained in the
numbered mode blocks “Mod1” through “Mod4”. “ModN” identifies
the numbered mode block to be used.
Pulse Width PwN: (PW1, PW2, PW3, PW4), Units: Seconds,

Limits: (1) 0.250, (2) 0.375, (3) 0.500, (4) 0.600, (5) 0.800,
(6) 1.000, (7) 1.200, (8) 1.500, (9) 2.000, (10) 3.000. The Pulse
Width control variable determines the length of a single-wide (1x)
pulse. The time required to transmit a number of data bits is
directly proportional to the pulse width. There are 10 standard
pulse width options ranging from 0.25 to 3.0 seconds.
35
Section 02
Survey Sequence Numbers SSNN: (SSN1, SSN2, SSN3, SSN4),
Units: Select Option, Limits: 1, 2, 3, 4. The survey sequence
number control variable in the numbered mode control blocks,
defines the survey data sequence string number used, which
determines the data order and content of the survey sequence.
Options:
-1 (end user specified default sequence),
0 (indicates no data),
1 (indicates SSq1),
2 (indicates SSq2),
3 (indicates SSq3),
4 (indicates SSq4).
Toolface/Logging Sequence Numbers TSNN (TSN1, TSN2,

TSN3, and TSN4): The Toolface/logging sequence number control
variables in the numbered mode control blocks define the T/L data
sequence string number used. The T/L data sequence string
determines the data order and content of the T/L sequence.
Options:
-1 (end user specified default sequence),
0 (indicates no data),
1 (indicates TSq1),
2 (indicates TSq2),
3 (indicates TSq3),
4 (indicates TSq4).
36
Section 02
Toolface Data Acquisition Timing Controls, AqTN (AqT1, AqT2,
AqT3, and AqT4): Units are in seconds. The numbered T/L data
acquisition timing control variables located in each number mode
control block, defines the nominal period allowed to acquire
Toolface/logging data variables. It defines the time when the data
acquisition processes in the transmitter will be executed prior to the
data being required for transmission. The processor adds an
additional 2 to 3 seconds to allow for processing and encoding
time. This subject is discussed in detail in the operational overview
section of the manual. This control does not effect the operation of
the surface receiver. It is recommended that these values remain
at 10 seconds.
T/L Transmission Time Limit Controls, TLTN (TLT1, TLT2,

TLT3, and TLT4): Units are in minutes. The T/L transmission time
limit variables in the numbered mode blocks limit the transmission
time for Toolface/Logging Sequence Data, when set to a non-zero
value. When set to zero, transmissions are continuous until a
pumps off detection occurs. The operator may want the tool to stop
transmitting TLTN data at some time after the initiation of
transmitting T/L data, such as when sliding and rotating a single or
stand. If no T/L data is required, then the tool can be shutdown,
after a prescribed amount of time. Since telemetry is never
terminated in the middle of a word or data set, actual T/L telemetry
periods may be somewhat longer than specified. This variable is
very useful but can be a problem if used incorrectly.
37
Section 02
Survey Sequence Definitions
Allows observation and editing of the survey sequence definition

strings that primarily determine the data content of the transmitted
survey sequences.
Survey Sequence Definition Strings, SSqN (SSq1, SSq2, SSq3,

SSq4): Units: Select Option, Limits: 1, 2, 3, 4: The survey
sequence definition strings primarily determine the data content of
the transmitted survey sequences. More Information in “Telemetry
Sequence String Formats” in the qMWD Engineer’s Reference
Manual, Chapter 5.4.6, listed under DATA VARIABLES.
38
Section 02
Toolface/Logging (T/L) Sequence Definitions
Allows observation and editing of the T/L sequence definition

strings that primarily determine the data content of the transmitted
T/L sequences.
Toolface/Logging Sequence Definition Strings, TSqN (TSq1,

TSq2, TSq3, TSq4): Units: Select an Option, Limits: 1, 2, 3, 4: The
Toolface/Logging sequence definition strings primarily determine the
data content of the transmitted Toolface/Logging sequences. More
Information in “Telemetry Sequence String Formats” in the QSI
Engineer’s Manual, Chapter 5.4.6, listed under DATA VARIABLES.
NOTE: The semicolon (;) punctuation mark is used to separate

data sets within the sequence to distinguish data measured
individually or as a data set. I.E. ----…aTFA:6:P;gama:8:P… will
measure the two values individually and transmit as prescribed.
The data set, ….aTFA:6:P gama:8:P…. programs the system to
measure both values at the same time and then transmit as
prescribed. Data points that require a particular time stamp to
relate to a specific depth require the semicolon (;) separation. Note
the values of toolface and temperature do not require a specific
time stamp relating to depth; therefore, the semicolon is not
required.
39
Section 02
Directional Data Variables
Inclination, “Inc”, defines the gravity inclination variable, Inc:12:P,

Units: Decimal Degrees, Limit: Fixed at 0.0 to 180.0. Use a 12-byte
word with parity. Less than 12 bytes will not afford reliable
resolution of the data value. More than 12 bytes will provide data
resolution beyond the capacity of the sensor capabilities and waste
transmission time.
Azimuth, “Azm”, defines the magnetic azimuth variable, Azm:12:P,

Units Decimal Degrees, Limit: 0.00 to 359.99. Use a 12-byte word
with parity. Less than 12 bytes will not afford reliable resolution of
the data value. More than 12 bytes will provide data resolution
beyond the capacity of the sensor capabilities and waste
transmission time.
Auto Toolface Angle, “aTFA”, defines the auto toolface angle

which may be set to the mTFA or gTFA value depending on the
requirements specified in the auto toolface angle control block,
“aTFC”. This variable is provided as a telemetry mechanism to
switch the toolface type as a function of the inclination value.
aTFA:6:P, Units: Decimal Degrees, Limit: 0 to 359.99. Use a 6-
byte word to decode a toolface angle with a resolution of ±3.5°.
Total Gravity, “Grav”, defines the measured gravity value,

Grav:12:P, Units: G’s, Limit: 0.000 to 2.000.
Grav=SQRT(Ax^2+Ay^2+Az^2). All QDT products employ tri-
axially-oriented accelerometers. Less than 12 bytes will not afford
reliable resolution of the data value. More than 12 bytes will
provide data resolution beyond the capacity of the sensor
capabilities and waste transmission time.
Dip Angle, “DipA”, is the measured magnetic dip angle, Dip:12:P,

Units: Decimal Degrees, Limit: -90.0 to 90.0 limited.
DipA=ATAN2(Mv/(SQRT(Mx^2+My^2+Mz^2-(-Mx*Ax-
My*Ay+Mz*Az)^2)))
Less than 12 bytes will not afford reliable resolution of the data
value. More than 12 bytes will provide data resolution beyond the
capacity of the sensor capabilities and waste transmission time.
40
Section 02
Total Magnetic Field, “MagF”, defines the measured total
magnetic field variable, MagF:12:P, Units: Gauss, Limits: 0.000 to
1.000 limited. MagF=SQRT (Mx^2+My^2+Mz^2). Less than 12
bytes will not afford reliable resolution of the data value. More than
12 bytes will provide data resolution beyond the capacity of the
sensors and waste transmission time.
Temperature, “Temp”, defines the directional sensor temperature

variable, Temp:8:p, Units: Degrees Centigrade, Limit: -50 to 205,
°C.
Average Battery Voltage, “BatV”, defines the average battery

voltage as averaged over and computed every “BEvT” seconds at
20 samples/second. BatV:8:P, Units: Volts DC, Limits: 0.0 to 51.1
VDC.
Magnetometer X Axis, “Mx”, defines the magnetometer X axis

corrected and scaled data. Mx:10:P, Units: Gauss, Limit: -1 to 1.
Magnetometer Y Axis, “My”, defines the magnetometer Y axis

corrected and scaled data. My:10:P, Units: Gauss, Limit: -1 to 1.
Magnetometer Z Axis, “Mz”, defines the magnetometer Z axis

corrected and scaled data. Mz:10:P, Units: Gauss, Limit: -1 to 1.
Accelerometer X Axis, “Ax”, defines the accelerometer X axis

corrected and scaled Data. Ax:12:P, Units: G’s, Limit: -1.66 to
1.66.
Accelerometer Y Axis, “Ay”, defines the accelerometer Y axis

corrected and scaled Data. Ay:12:P, Units: G’s, Limit: -1.66 to
1.66.
Accelerometer Z Axis, “Az”, defines the accelerometer Z axis

corrected and scaled Data. Az:12:P, Units: G’s, Limit: -1.66 to
1.66.
41
Section 02
Data Value Resolution Formula
To assist clients in determining the resolution of a transmitted

value, from the above listed values, this algorithm is supplied:
V= 1 (M)
Y
2
V => Minimum resolved value
Y => number of bits used in transmission of word value.
M => max value of word being transmitted.
i.e., Inc max value is 180°.
Example: inc:12:P => 1 (180) => 0.044
12
2
This result indicates that the value of the inclination displayed was
resolved to 0.044°.
For the azimuth => 1 (360) => 0.087 azm:12:P

212
42
Section 02
Telemetry Warnings
Low Battery Voltage Warning, “BatW”, indicates that the battery

voltage is below the value specified by “BThr”. “False” indicates
that BatV≥BThr. “True” indicates that BatV≤BThr.
High Temperature Warning, “TmpW”, defines the high

temperature warning flag. This flag is set when Temp≥TmpT.
Magnetic Anomaly Warning, “MagW”, defines the magnetic

anomaly warning flag. The state is determined by the directional
process, based on the measured dip angle, magnetic field values
and the magnetic anomaly control in the MagC block.
Dip Angle Anomaly Warning, “DipW”, defines the dip angle

process, based on the measured magnetic dip angle. False if
dDip≤DipT and True if dDip≥DipT.
Total Gravity Anomaly Warning, “GrvW”, defines the total gravity

process, based on the measured total gravity vector. False if
dGrv≤GrvT and True if dGrv≥GrvT.
43
Section 02
Formation Data Variables
Gamma Count Rate, “Gama”, defines the measured gamma count

rate in counts/second as measured over a count-sampling period
and optionally factored by the “Gsf” scale factor. Please refer to the
Gamma Acquisition Controls Section for further information on
sampling periods. Gama:8:P. Units: Counts/second (optionally
factored). Limits: 0.00 to 255.00.
Data Sets
Data sets are defined by the variables used the Survey and
Toolface/Logging Sequences. A row of data variables separated by a
space only, will be acquired at the same time and lined up for
transmission sequentially. Data variables separated by a semicolon
(;) or a comma (,) will be acquired prior to the requirement for
transmission. Therefore, all of the data transmitted for a survey was
acquired at the same time from the measurements of the directional
sensors. However, the data from the tool needed for transmission
during the Toolface/Logging sequence, at times, does not need to be
acquired at the same time. In fact, most data variables should be
acquired separately, or as needed.
Example of a T/L Sequence:

12{aTFA:6:P;Gama:8:P} aTFA:6:P Temp:8:P
The toolface angle and the gamma measurement will be
acquired separately, with the toolface acquired first, and the
gamma acquired during the transmission sequence of the
toolface. This will be repeated 12 times, then the sensors will
be powered and a toolface value, as well as the temperature
value will be calculated. Then both words will be transmitted,
without the sensors having to be powered to acquire the
second value, which is the temperature.
If time/depth stamps are an important mark, when storing the

data, then this procedure should be followed. The type of data
required for transmission is the determining factor, as whether
or not to strictly adhere to this procedure.
44
Section 02
Data Word Update Times
Real-time Data Word Updates are dependent upon Pulse Length and
the Number of Bits per Word. The following chart of Empirical Data
will indicate the time required for Data Word updates for three different
word lengths per pulse length. The resolution of the Data Word value
transmitted is dependent on the number of bits per Word.
It can be seen that as the pulse width lengthens the data bits per word
become extremely important. A decision to sacrifice resolution for a
faster update is crucial, and the course of action must be determined.
Obviously, a 12-bit word is almost twice as long as a 6-bit word, but a
12-bit word is NOT twice as accurate as a 6-bit word. For example,
the resolutions for each of the different length Toolface data words
are: 1) 12 bits = 0.1°, 2) 8 bits = 1.5°, 3) 6 bits = 5.5°. The accuracy is
dependent on the values of the least significant bits. This will
obviously affect the accuracy of the gTFA measurements, somewhat,
but not as adversely as the time necessary to transmit the data. The
decision is up to the operator and the end user of the data. It can be
concluded that the difference in resolution and the resultant accuracy
of the Toolface data word is minimal for the decreased Toolface
update time.
The resolution of Survey Data Words and Logging Data words is of

utmost importance. That is why it is so important to insure that the
required number of bits is used to transmit the Data Word.
45
Section 02
Data Word Transmission Times
Pulse Width Bits/Word Update

Time
A. 0.25 6 4 seconds
8 5 seconds
12 7 seconds
B. 0.325 6 5 seconds
8 6 seconds
12 9 seconds
C. 0.5 6 7 seconds
8 9 seconds
12 13 seconds
D. 0.6 6 8 seconds
8 10 seconds
12 16 seconds
E. 0.8 6 11 seconds
8 14 seconds
12 21 seconds
F. 1.0 6 14 seconds
8 18 seconds
12 26 seconds
G. 1.2 6 17 seconds
8 22 seconds
12 31 seconds
H. 1.5 6 21 seconds
8 27 seconds
12 39 seconds
I. 2.0 6 28 seconds
8 36 seconds
12 52 seconds
J. 3.0 6 42 seconds
8 54 seconds
12 78 seconds
46
Section 02
Survey Time Comparison Chart
The following two pages illustrate, with empirical data obtained from
the Flow Simulation Test Fixture, the potential times elapsed for
different types of survey configurations and Toolface/logging
configurations.
Category A configuration:
Inc:12:P Azm:12:P aTFA:6:P DipA:12:P MagF:12:P Temp:8:P
BatV:8:P Grav:12:P
Category B configuration:Inc:12:P Azm:12:P aTFA:6:P

TmpW+BatW+MagW:P
Toolface/Logging Sequence: aTFA:6:P XX {Gama:8:P}

(XX denotes the number of repetitions before starting the string over)
Category A
Pulse Width 1.0 sec 1.5 sec. 2.0 sec.
Parameter
60 sec TxDT Elapsed Time Elapsed Time Elapsed Time
Synch: 1:14 1:22 1:27
Inclination: 1:48 2:14 2:37
Azimuth: 2:15 2:52 3:28
Static Toolface: 2:28 3:13 3:55
Dip Angle: 2:55 3:52 4:47
Total Mag Field: 3:20 4:30 5:36
Tool Temperature: 3:37 4:56 6:11
Battery Volts: 3:55 5:24 6:46
Total Gravity: 4:21 6:01 7:36
Dynamic Toolface: 4:42 6:33 8:20
1st Gamma: 5:00 6:58 8:54
Gamma Update Rate: ±18 ±27 ±36

3.33 g/min 2.22 g/min 1.66 g/min
Gamma Pts. / Foot

@ 70 Ft. / Hr. ROP 2.86 1.9 1.66
Gamma Pts. / Foot

@ 30 Ft. / Hr. ROP 6.66 4.44 3.33
47
Section 02
Category B
Pulse Width 1.0 sec 1.5 sec. 2.0 sec.
Parameter
60 sec TxDT Elapsed Time Elapsed Time Elapsed Time
Synch: 1:14 1:22 1:27
Inclination: 1:48 2:14 2:37
Azimuth: 2:15 2:52 3:28
Static Toolface: 2:28 3:13 3:55
Warnings for
Dip Angle+Mag Field+
Temperature+
Battery Voltage: 2:37 3:27 4:11
Dynamic Toolface: 2:59 3:57 4:54
1st Gamma: 3:18 4:25 5:29
Gamma Update Rate: ±18 ±27 ±36

3.33 G/min 2.22 G/min 1.66 G/min
Gamma Pts. / Foot

@ 70 Ft. / Hr. ROP 2.86 1.9 1.43
Gamma Pts. / Foot

@ 30 Ft. / Hr. ROP 6.66 4.44 3.33
Please note that the data used in these examples was compiled
from a Simulated Flow Lab Test Fixture. The times presented may
vary from ±3.5 seconds using the same configurations.
Note: the data presented in the previous two pages are just
examples that can be used for comparison to determine potential
time elapsed for different configurations. They are not meant to
represent any actual configurations recommended by GE Power
Systems or its subsidiaries or any of its employees. It is strongly
recommended by GE Power Systems that each client investigate
the configuration that is best suited for the well environment and the
client’s needs.
48
Section 02
Accuracy of Directional Sensors Manufactured by GE Power
Systems, Austin, Texas
The orientation modules manufactured by GE Power Systems, tri-axial

magnetometers and accelerometers mounted into a common chassis, are
high-performance instruments in terms of linearity, and stability after
exposure to the downhole environment and calibration accuracy. The
significance is that when their responses are properly processed and
when they are operated in the field using "good practice", the navigational
information- azimuth, inclination and toolface -is as credible and accurate
as is available today. This is true of the instruments used in the GE
Power Systems Tensor MWD System, the GE Power Systems Tensor
Steering Tool System and the GE Power Systems Tensor CHAMP/EMS
tool. GE Power Systems also supplies similar directional instruments to a
number of oil service companies.
The directional sensors typically perform as follows:
Magnetometers: residual output error after compensation:
less than 1 milligauss
Inclinometer: residual output error after compensation:
less than 0.6 milligee
Typically, an isolated magnetic directional probe in free space (including

fully calibrated sensor package and microprocessor with operating
thermal model) will produce accuracies as follows:
Lateral displacement error: +/- 2.6 feet per 1000 feet, or a conical
uncertainty of 0.15° maximum. This translates to azimuth errors related
to inclination as follows:
+/- 1.7° at an inclination (off vertical) of 5°
+/- 0.3° at the inclination of 30°
+/- 0.15° when horizontal. The inclination error is less than 0.1°.
To realize the full accuracy available from the analog directional

instrument, the data handling system must properly digitize the sensor
outputs, thermal model compensation must be programmed correctly and
sufficient resolution must used to transmit the final data.
"Good practice" in directional surveying with magnetic instruments refers

to the care, which needs to be taken in making sure that the instrument
assembly is well aligned with the drilling assembly. In addition, that
adequate non-magnetic material is used to space the instrument far
enough away, from the mud-motor and any magnetic collars/subs, to
prevent influence on the magnetic sensor measurements. As much as
possible, care must be taken that, when a definitive survey is attempted,
that the instrument be stationary.
Lack of "good practice" will obviously affect survey accuracy.
49
Section 02
Job Site Environment Settings:
This window allows observation and editing of the variables that

define Earth’s magnetic characteristics applicable at the drilling site.
The nominal values and tolerances on the total magnetic field and
dip angle determine the specifications for determining a magnetic
anomaly. The magnetic declination value is added to the measured
(magnetic) azimuth to arrive at true azimuth or added to magnetic
toolface angles to arrive at toolface angles relative to true North.
Values may be entered manually, or they may be selected from a
database of site locations. Access to the database for adding or
deleting entries is also provided.
Site Location (LOC): The site location is used as a reference to

access the Site Environment Settings database. The database of
information is kept in the file ‘Site_DB.DAT’. Each entry must be
unique. Entries are not case sensitive. Only the characters A-Z
and 0-9 are considered when determining uniqueness.
A right button click on the mouse will reveal a small menu box. The
menu box will allow the operator to view the Site_DB.DAT file or
save the current site to that data base file or delete the current site
from that data base file. This option will be activated at anytime the
window is open. Use it to store numerous site values.
Nominal Dip Angle (NDip), Units: Angle Degrees, Limits: -

90.00° to 90.00°: Defines the nominal magnetic dip angle (NDip) at
the drilling site.
50
Section 02
Dip Angle Tolerance (DipT), Units: Angle Degrees, Limits: 0.92°
to 10.00°: Defines the magnetic dip angle tolerance. When using
“MagW” in the Survey or Toolface/Logging Sequence, if the Dip
Angle measured is greater or less than the “NDip” value by a
quantity greater than “DipT”, then a “True” warning is transmitted
by the tool. If the Dip Angle measured is greater or less than the
“NDip” value by a quantity less than the “DipT”, then a “False”
warning is transmitted by the tool.
Nominal Magnetic Field (NMag), Units: Gauss, Limits: 0.200 to

0.900: defines the nominal total magnetic field ('NMag') at the
drilling site.
Magnetic Field Tolerance (MagT), Units: Gauss, Limits: 0.010

to 0.200: Defines the total magnetic field tolerance. When using
“MagW” in the Survey or Toolface/Logging Sequence, if the
Nominal Magnetic Field measured is greater or less than the
“NMag” value by a quantity greater than “MagT”, a “True” warning
is transmitted by the tool. If the Dip Angle measured is greater or
less than the “NMag” value by a quantity less than the “MagT”,
then a “False” warning is transmitted by the tool.
Magnetic Declination (MDec), Units: Angle Degrees, Limits: -

180.00° to 180.00°: Defines the magnetic declination at the drilling
site. This value is used for the computation of the True Azimuth
and True Magnetic Toolface angles.
Delta Mag. x-y Field Tol. (MxyT), Units: Gauss, Limits: 0.010 to
0.200: The MxyT control variable defines the allowed tolerance on
the difference in magnetometer x-y fields (“dMxy”) as measured
during a survey data acquisition (“SMxy”). The x-y field value is
measured during a Toolface/logging acquisition (“TMxy”). When
the magnitude of “dMxy” exceeds this value, the “MxyW” warning
flag is set.
Nominal Gravity Magnitude, (NGrv), Units: Gs, Limits: 0.000 to

2.00: “NGrv” defines the nominal gravity magnitude at the drilling
site. It measures movement of the accelerometer orientation when
the accelerometer is energized. An acceptable measurement
should be between 1.005 and 0.995.
51
Section 02
Gravity Magnitude Tolerance, (GrvT), Units: Gs, Limits: 0.000
to 1.000: “GrvT” defines the gravity magnitude field tolerance.
When using “GrvW” in the Survey or Toolface/Logging Sequence, if
the Nominal Gravity Magnitude measured is greater or less than
the “NGrv” value by a quantity greater than “GrvT”, a “True”
warning is transmitted by the tool. If the Nominal Gravity
Magnitude measured is greater or less than the “NGrv” value by a
quantity less than the “GrvT”, then a “False” warning is transmitted
by the tool.
Magnetic Data Information Site on the Web.
www.ngdc.noaa.gov/seg/potfld/geomag.html
The magnetic declination and other magnetic data can be found on

the Internet at the site for the National Geophysical Data Center of
NOAA. Go to the above address, and under the heading ‘Models and
Software’ is listed Geomag Declination On-line. This link will take you
to a page for calculating the MDec and other magnetic characteristics
of any spot around the world defined by longitude and latitude.
52
Section 02
Directional Processing Controls:
These controls allow the operator to edit and observe the variables
relating to the DownHole Directional processor. The corrections for
RTTF and TTTF have been altered to a one step option, called the
“Correct for Magnetic TFA Declination”. This option now only
allows the selection of one of three methods of adding the Mag Dec
correction to the Magnetic Toolface.
High Temperature Threshold (TmpT), Units, Degrees Celsius or

Fahrenheit, Limits: 0 to 200 °C or 32 to 392 °F: This variable
defines the high temperature threshold above which the high
temperature warning flag (“TmpW”) is set true. The high temperature
condition is always evaluated and does not have a disabling switch.
The standard setting for QDT MWD probes is 125° C (257° F). The
display can be adjusted for Celsius or Fahrenheit by using the
Variable Units Display Routine. Note: THE RANGE OF THE
TEMPERATURE THRESHOLD, AS DEFINED AND ALLOWED BY THIS PROGRAM,
IS NOT INTENDED TO AND DOES NOT SPECIFY A TEMPERATURE RATING FOR
THE DOWNHOLE DIRECTIONAL PROCESSING HARDWARE. REFER TO THE
HARDWARE SPECIFICATIONS FOR TEMPERATURE OPERATING LIMITS.
53
Section 02
Correct for Magnetic TFA Declination (CmTF), Select an
Option: The "CmTF" control variable enables or disables the
addition of (correction for) the magnetic declination value, MDec, to
magnetic toolface angles for true magnetic toolface values. This
control maps to the "TmTF" control in the surface receiver and the
downhole tool. When set to “DownHole”, TmTF is set to “On” in the
DownHole Tool. Similarly, when set to “Surface”, TmTF is set to
“On” in the Surface Receiver. Alternatively, the operator can
choose to turn off correction in both the DownHole Tool and the
Surface Receiver by setting CmTF to “Off”.
Sensor Power Control (DSPC), Select an Option: This control

specifies whether the directional processor is allowed to control the
sensor power. I.E.: when ENABLED, the sensors are powered only
during data acquisition processes, and when DISABLED, the
sensors are powered continuously. A delay of “DWuT” (warm-up
time in seconds) is always required from power on before data
sampling commences. This control should ALWAYS be set to
ENABLED.
Survey Acquisition Mode (SuAM), Select an Option: The survey

acquisition mode defines whether survey data is acquired following
a FLOW ON detection or a FLOW OFF detection. GE Power
Systems recommends all surveys be measured in a flow off
condition with battery backup. Refer to “SuDT”. This control maps
to the DownHole Probe.
Survey Acquisition Delay Time (SuDT), Units: Seconds, Limits:

5.00 to 60.00: The survey delay time specifies the delay time from
either the FLOW or NO FLOW epoch, as defined by the “SuAM”
variable, before a survey data acquisition process occurs. This
control maps to the DownHole Probe and standard time is 25
seconds, but can be adjusted with more experience.
Survey Sampling Rate (SuSR), Units: Hz, Limits: 20 to 256: The

survey sampling rate control specifies the sampling rate, in data
sets/second, for survey data acquisitions. This rate is also used for
acquisitions resulting from the zero toolface offset command and
the acquire survey data command. This variable is always used in
conjunction with “SuST” (below) that determines the number of
samples averaged for data computations.
54
Section 02
Survey Sampling Time (SuST), Units: Seconds, Limits: 0.05 to
30.00: This variable controls the sampling time, in seconds, for
survey data acquisitions. This period is also used for acquisitions
resulting from the zero toolface offset command (“ZTFA!”) and the
acquire survey data command (“AcqS!”). It is always used in
conjunction with “SuSR” which determines the number of samples
averaged for survey data computations. Clients employing MWD
systems with turbine powered systems and no battery backup will
have to increase the sampling time to accommodate for excessive
vibrations experienced during the survey caused by flow and mud
motor operations.
Steering Sampling Rate (StSR), Units: Hz, Limits: 20 to 256:

This control specifies the sampling rate, in data sets/second, for
steering (T/L) data acquisitions. This rate is also used for
acquisitions resulting from the ”acquire” steering data command
(AcqD). This variable is always used in conjunction with “StST”
which determines the number of samples averaged for steering
data computations.
Steering Sampling Time (StST), Units: seconds, Limits: 0.05 to

30.00: This control specifies the sampling time, in seconds, for
steering (“T/L”) data acquisitions. This period is also used for
acquisitions resulting from the "Acquire Steering Data" command
(“AcqD!”). This variable is always used in conjunction with “StSR”
which determines the number of samples averaged for data
computations.
55
Section 02
Magnetic Toolface Calculation Type (mTTy), Select an Option:
There are two different computations for the magnetic toolface
angle. The numeric control variable “mTTy” may be set to either 1
or 2 to select type 1 or type 2 computations.
Type 1 Computation:
mTFA = ATAN2 (Mx / My) -(+) TFO + MDec
Type 2 Computation:
mTFA = ATAN2 ((Grav*Mx+Ax*Mz) / (Grav*My+Ay*Mz)) -(+)

TFO + MDec
Toolface Offset ("TFO"). Where "TFO" is the value of the toolface

offset that is normally subtracted in toolface angle computations.
However, a customization provision allows for the addition of the TFO
value for offset corrections.
gTFA = ATAN2(Ax/Ay) -(+) TFO

mTFA = ATAN2(Mx/My) -(+) TFO + MDec
Auto Data Acquisition Control (DiAA), Select an Option: This

control switch allows putting the directional data acquisition process
in automatic data mode for Test Purposes. This volatile switch
control is automatically disabled when power is cycled to the tool or
after the first data acquisition process following a flow sense
change. It determines whether the directional processor operates
continuously, only on command, i.e. Flow On, or Flow Off. If “ON”
the processor updates survey data defined by “SuSR and “SuST”
control settings on a continuous basis. When the control is “OFF”,
the processor updates only when commanded. This control should
ALWAYS SET TO “OFF”.
Auto Broadcast Mode (DiAF), Select an Option: This control when

“ON” causes the directional process to automatically output a data
string on the multi-point communications bus at the completion of
each commanded or automatic data acquisition cycle. This is an
internal communication command in the downhole probe and
SHOULD ALWAYS SET TO “ON”. The content and format is defined
by the “DFmt” string below.
56
Section 02
Auto Broadcast String (DFmt): This string determines the content
of the output from the directional processor when the DiAF auto
formatting switch is set to “ON”. This is an ASCII string whose
format is “qMIX” text compatible and is generally limited to inquiry
statements. The string should read:
Azm?;Inc?;mTFA?;gTFA?;Temp?;MagF?;DipA?
Alternatively, whatever the operator wishes to read in that string.

The operator should use what is given and there is no need to alter
the example, unless the system needs to be tested on the bench.
When performing a roll test using the MWDRoll program, the DFmt
is rewritten to display the required to perform the roll test. It is then
rewritten to the DFmt that was resident when the tool was queried
prior to the start of the roll test.
57
Section 02
Gamma/Battery Processing Controls:
The gamma acquisition controls define the gamma data acquisition

modes and data processing management. The Battery Monitor
process monitors the average battery voltage and can enable the
optional secondary battery pack when low voltage condition (below
battery threshold) is detected.
Sensor Power Control (GSPC), Select an Option: The Gamma

Sensor Power Control Switch enables or disables the processor to
control the sensor power. When “ENABLED”, the sensor is
powered ONLY during flow conditions. During No Flow conditions,
the sensor will respond to external data acquisition commands in a
“singleshot” mode of data acquisition, which is intended for testing
procedures. When “DISABLED”, the sensor is powered
continuously and acquires data continuously after power is applied
to the gamma sensor. When using battery power as the single
source, it is recommended to "Enable" this switch.
Sensor Warm-up Time (GWuT), Units: Seconds, Limits: 0.1 to

10.0: The Gamma Sensor Warm-up Time control specifies the
delay required after energizing the sensor before data acquisition
may commence and should be set to 1.0.
58
Section 02
Minimum Sampling Time (GMin), Units: Seconds, Limits: 1 to
60: The minimum gamma sampling time control specifies the
minimum gamma count sampling time. A gamma rate computation
will never be based on a sampling time less than specified.
Acquisition commands received prior to this time will be responded
to in auto formatting mode with the most recent gamma data. If a
gamma computation has not occurred since sensor power up, it will
process data when sampling has occurred for the specified “GMin”
period. It is recommended that this variable be set to one.
Maximum Sampling Time (GMax), Units: Seconds, Limits: 60 to

3000: This control specifies the maximum gamma count sampling
time. A gamma rate computation will never be based on a sam-
pling time greater that specified. If the gamma process is in
commanded acquisition mode, it will automatically acquire data
when the sampling period has reached “GMax” seconds. As an
example: Should the gamma command in the T/L Sequence be
preceded by the carat, ^, the sensor will measure Gamma at
pumps up and then not obtain another reading until 3000 seconds
later under continuous pumps up condition for that period of time or
at the next pumps up. Therefore, the same gamma reading will be
sent. DO NOT precede the Gamma command by the carat, ^. It
is recommended to place the GMax variable at 60.
The Gamma Rate Scale Factor: The process of computing the

“Gama” rate variable may be factored by a user specified number
used as a multiplier on the counts/second result. This value must
be set to 1.0000, unless the user has a specific requirement. The
variable will scale the gamma count/second for different collar
sizes, hole I.D. and mud weight. These scale factors are currently
being left to the MWD customer to determine. Refer to QSI for
more information regarding this scaling factor.
Scale Factors calculated for following collar sizes, (in inches)
O.D. I.D. Factor O.D. I.D. Factor

4.75 x 2.61 > 2.35 8.00 x 4.00 > 6.0
6.25 x 3.25 > 3.5 8.00 x 3.25 > 6.3
6.50 x 3.25 > 4.15 9.00 x 4.00 > 8.0
6.75 x 3.25 > 4.25
59
Section 02
Auto Acquisition Mode (GaAA), Select an Option: This control
switch determines whether the gamma process operates in the
auto acquisition mode or only acquires data on command. When
the switch is set, gamma data is acquired continuously and
automatically, using the sampling period as specified by the “GUpT”
control. Otherwise, data is only acquired when requested from the
MPTx processor or by the “AcqG” command. The “AcqG”
command originates from the T/L Sequence, by the sequence
Gama:8:P. In auto acquisition mode, data processing only stops
during a Flow Off condition and if the “GSPC” control is disabled.
This control only effects the gamma computations. Whenever the
sensor is on, counts are being acquired. Always select the “OFF”
option for the downhole operations. Clients employing the memory
module in the survey electronics module will be instructed to leave
this switch in the "On" position.
Auto Acquisition Update Time (GUpT), Units: Seconds, Limits:

1 to 3000: This variable determines the period for sampling gamma
counts and computing the “Gama” rate variable when the gamma
process is in auto acquisition mode (refer to “GaAA”).
Auto Broadcast Mode (GaAF), Select an Option: This switch,

when set, causes the gamma process to automatically output a
data string (“GFmt”) on the multi-point communications bus at the
completion of each data acquisition cycle. The output string
content and format is defined by the “GFmt” string. It should be set
to “ON” for downhole operations.
Auto Broadcast String (GFmt), Edit String, Gama?;GaTT?: This

string determines the content of the output from the gamma
process when the “GaAF” auto-formatting switch is "Enabled". This
is an ASCII string, the format of which is “qMIX” text compatible and
is generally limited to inquiry statements.
It is STRONGLY recommended that all operators refer to the

“qMWD Engineer’s Reference Manual Volume I, Chapter 4.5 for
more information regarding Gamma operation.
The battery monitor process monitors the battery voltage and can
enable an optional secondary battery pack when a low voltage
condition is detected. All of the controls for this process are
contained in the “BatC” control block.
60
Section 02
Voltage Update/Averaging Time (BEvT): Battery Evaluation Time
is the control that specifies the number of seconds the battery
process AVERAGES the battery input voltage reading for the
purpose of data computations and evaluations. This control is
limited from 1 to 240 seconds but should be set to a value of 10.
Low Battery Voltage (BThr): The Low Battery Threshold Voltage

defines the threshold, below which the battery is CONSIDERED
low. This value should always be set to 21.0 VDC to set a warning
when using one battery and provide a switch when using two
batteries.
This will alert the operator that the battery is low. When using a
double battery stack, when the average is below this value, then
the system will switch to the second battery pack and set the
secondary battery ON flag (“Bat2”). The variable should be set to
21.0 volts when using the double battery stack.
61
Section 02
Pumps/Flow Evaluation Controls:
These controls allow the operator to observe and/or edit the variables
used by the pump monitoring process for evaluating pump on/off
conditions and scaling the pressure transducer in the Surface System.
The term “pumps” is used for variables in the Surface System. They also
allow the operator to observe and/or edit the variables used by the flow
monitor process for determining flow ON/OFF conditions. The term “flow”
is used for the variables in the Transmitter Processor.
Pumps-On-Threshold (PmpT): This variable defines the input pressure

value at and above which pumps are to be considered on. Ideally, the
set point would correspond to the pressure at a flow rate that also
causes the downhole tool flow sensing mechanism to switch. This will
minimize any timing discrepancies between the transmitter and receiver
relative to synch transmission and detection. This variable is measured
in PSI at the transducer and is limited from 50 to 2000 PSI. Note: A
surface test of the tool with an open ended BHA will result in a maximum
pressure of about 400 to 600 PSI, therefore, the setting should be at its
lowest of 50 PSI. When the tool is placed downhole, the setting should
be set to a value of 500 to 800 PSI. This variable is accessible in the
Basic Receiver Controls in the qMWD_PC monitoring program and is the
only variable changeable in a ‘Pumps On’ environment. This will allow
the operator to turn the DRT On/Off by lowering/raising the value should
that procedure be required.
62
Section 02
Pumps On/Off Evaluation Time (PEvT): This variable is functionally
identical to “FEvT”. It determines how long the pumps input must
indicate a state change before the system will respond to the change.
The value reported to the system for the elapsed time in pumps on or
pumps off state includes the pumps evaluation time. Therefore, all
timing relative to pumps change epochs is relative to when the change
was first detected. The recommended time for both “PEvT” and
“FEvt” is 7 seconds.
Pressure Transducer Rating (PTfs): This variable defines the

nominal pressure value for the pressure transducer full-scale output,
i.e. this value is used to calculate the PSI equivalent of the millivolt
readings of the transducer. This value should be 5000 but is
adjustable, depending upon the type of standpipe transducer
employed.
Pressure Transducer Offset (PTO): This correction value is used to

correct the pressure transducer and related receiver electronics for
offset conditions. The offset value is entered in PSI, but is scaled and
stored internally in A/D counts. Therefore, the value read will
automatically change when the pressure transducer full-scale
definition, “PTfs”, is changed. The PTO value is subtracted from the
raw pressure measurement for correction. This value is usually set at
0 PSI, but in low-pressure flow loop conditions; a negative value may
have to be entered to compensate for the inadequacies of the
transducers at pressures less than 75 PSI.
Pressure Transducer Gain (PTG): This correction (multiplier) factor

is used to correct the pressure transducer and related receiver
electronics for scaling errors. This variable is used as a multiplier on
the pressure transducer measurements at the A/D conversion level.
Unless otherwise instructed it should always be set to 1.000.
63
Section 02
Flow On/Off Evaluation Time (FEvt): The flow evaluation time
control determines how long the flow input must indicate a state
change before the system will respond to the change. The value
reported to the system for the elapsed time in a flow or no flow state
includes the flow evaluation time. Therefore, all timing relative to flow
change epochs is relative to when the change was detected (not when
the flow state change is reported). This variable should match the
“PEvT” variable above. In certain cases, when using a pulse width of
2.0 or 3.0 seconds, it is recommended that this variable always be set
to 10 seconds, to insure that flow switches activated and deactivated
by pulses, will not interpret the Alert Pulse as a Flow Off condition.
Invert Flow Sense (InvF): THIS CONTROL SWITCH SHOULD ALWAYS BE

IN THE OFF POSITION, FOR ALL MWD TOOLS SENT DOWNHOLE.
Mechanical Flow Switch Settings

InvF: “OFF”
When using the original flow switch designed in the QDT MWD, the
InvF should be set to the “OFF” position. The total tool (with the
exception of the flow switch) can be tested by performing the Dry
Pulse Test procedure.
Electronic Flow Switch (EFS)

Use InvF: “OFF”
In January of 1998, GE Power Systems, Round Rock, Texas,
incorporated the EFS for use in the QDT MWD pulsers. This
system is an accelerometer activated flow switch, which is very
sensitive to vibrations in the environment. To avoid any confusion
in the programming of the system, the engineers designed the
system to operate in the same orientation as the original flow
switch, with regards to the InvF.
The incorporation of the EFS has simplified the operation and

testing procedures prior to sending the probe into the downhole
environment and increased the reliability of the QDT MWD. After
configuring the tool, the operator simply has to apply soft vibration
to the probe at any location for the required TxDT time-period to
witness the actuation of the servo-poppet. Simply rattling an object
such as a ribbed handled screwdriver across any portion of the
MWD tool will induce sufficient vibration to the EFS to activate the
tool. Apply the vibration to the tool for a time-period greater than
the TxDT setting and the tool will pulse.
64
Section 02
Surface Receiver Controls:
These variables allow the operator to edit the coefficients and

thresholds used in the detection of pulses, synch tracking and other
related tracking processes. The Low/High Pulse Amplitude Limits are
the only variables necessary for field operator access. These are
accessible via the qMWD_PC program.
Low/High Pulse Amplitude Limits, Units: PSI, LoPL, Limits: 3

to 300: HiPL, Limits: 20 to 2000: These variables specify the
acceptable, inclusive range of pulse amplitudes. Pulses detected
outside of the defined range will not be reported or processed. The
ratio of HiPL: LoPL CAN exceed the 10:1 ratio, or be less than that
ratio. Normally, these values are set based on the pulser
characteristics and should normally not require field modification;
65
Section 02
however, experience will allow the operator to forecast a
satisfactory range. NOTE: these variables are accessible in the
qMWD_PC program via Basic Receiver Controls, for real time
adjustment. Take into account that this DOES NOT alter the
settings in the Configuration File originally loaded to the DRT, if the
file is to be reloaded for one reason or another.
Average Quality and Confidence Factors, (AvQn and AvCn),

Units: Number of Words, Limits: 10 to 32: These values define the
size of the average quality and confidence factor “sliding window”
averaging filters. Take note of the minimum value of 10 and do not
enter a number less than that. To view the Quality and Confidence of
the most recent word, refer to Alt-6, Pulse Data Buffers Screen, in
qMWD_PC program.
Pulser Type (PTyp): The qMWD surface system can operate with
either a positive or negative pulser system. However, the QDT MWD
system is POSITIVE, and this control MUST BE SET AT ALL TIMES
TO POSITIVE.
Synch. Detection k-factors:

THESE VALUES MUST NOT BE CHANGED!!
Tampering with these values could render the decoding process
inoperable with the change of only one numeral or decimal.
Please DO NOT ALTER THESE VARIABLES!!!! The variables
should read the following values unless otherwise dictated by
GE Power Systems or your Systems Analyst:
SDk1 = 1.0977
SDk2 = 0.75000
SDk3 = 0.1992
SDk4 = 1.7500
STk1 = 0.150000E+00
STk2 = 0.130000E-04
AvAk = 0.1000
PAf1 = 12.0
PAf2 = 8.0
66
Section 02
Depth Tracking Controls:
This screen allows the operator to view and edit control parameters
related to Depth Tracking. Depth Tracking may be switched from
the Automatic Mode, or the Manual Mode, or it can be entirely
disabled, depending upon the job requirements. These variables
map to the Surface Receiver Processor (MPRx), Node 05.
Numerous variables displayed in this screen are available for
adjustment in the Basic Receiver Controls Menu, accessed in the
drag down menu, of the qMWD_PC MWD Monitoring Program.
NOTE: when not using a Heave Compensator, set all Heave
values and Secondary Heave Values to zero (0).
67
Section 02
Depth Tracking Mode, (DTMo), Select an Option: This option
allows the operator to select either the Manual or Automatic mode of
Depth Tracking, or to disable it altogether. “Manual” depth tracking
requires the use of the “Bttm!” and “Slps!” commands to effect control
of depth tracking. “Automatic” depth tracking is just that - It enables
Auto depth tracking. This mode allows limited use of “Bttm!” and
“Slps!” commands. “Off” will disable the system.
On Bottom Detection Method, (OBDM), Select an Option: This

parameter determines the On Bottom/Off Bottom conditions after
coming out of the slips. The Hook Load Based method determines
On Bottom when the Weight on Bit (WOBs) parameter reaches 30
percent of the Minimum Weight on bit (MnWB). It does not mean
that when the hook load sensor is being employed that this
method be used! This method is effective with vertical wells running
a high Weight On Bit (i.e. 25+ Kips). The Depth Based method
determines On Bottom when the Bit Depth (BDep) data variable
becomes equal to the Measured Depth (MDep). This method is more
effective for low Weight on Bit conditions, with a stabilized BHA and
horizontal wells. It is the Recommended Method, ALWAYS.
Hook Load Sensor Full Scale, (HLfs), Units: Klbs, Limits: 256 to
2048: Defines the full-scale value of the hook load sensor input, with
the default set at 1000. Refer to qMWDTM Depth Tracking Engineers
Ref. Manual, ¶3.1.3.
Hook Load Sensor Offset, (HLo), Units: Klbs, Limits: -1024 to

1024: Hook Load Offset is provided to compensate for the difference
between the weight detected by the hook load instrumentation, and
the actual weight of only the drill string, minus the block and kelly
assembly. The “Zero Hookload”, (ZHL!), command in the drag down
menu is used for setting the hook load offset. Refer to qMWDTM
Depth Tracking Engineers Ref. Manual, ¶3.1.4.
Hook Load Averaging Number, (HLn), Units: 0.1 seconds, Limits:

1 to 10: This variable defines the sensor input averaging period in
units of 0.1 second. This number does not affect the update period,
which is fixed at 0.1 second. Actual limits: (0.1 - 1.0). Refer to
qMWDTM Depth Tracking Engineers Ref. Manual, ¶3.1.5.
68
Section 02
In-Slips Hook Load Threshold, (ISHL), Units: Klbs, Limits: 1 to
100: This variable defines the hook load weight threshold for switching
the system from the “Out-of-Slips” state to the “In-Slips” state and
vice-a-versa. Once in the Drilling Mode (after tagging bottom), this
threshold becomes significant only if the difference between the value
of the Measured Depth and the value of the Bit Depth is greater than
the value of the Minimum In-Slips Travel Distance. I.E. MDep - BDep
> ISTD. See also Minimum String Weight.
In-Slips Travel Distance, (ISTD), Units: Feet, Limits: 1 to 100:

This parameter defines the minimum amount of hook travel
upwards required to be able to return the system to the In-Slips
state, measured from the bottom of the hole. This parameter is
used to prevent the system from inadvertently entering the “In-
Slips” state when the measured hook load value is lower than the
In-Slips Hook Load Threshold (ISHL), due to light drill string weights
encountered during horizontal and shallow depth drilling. This
value may have to be adjusted when setting the Kelly back; if the
Kelly shuck is lower than this value, to prevent inadvertent logging
of footage.
Off Bottom Travel Distance, (OBTD), Units: Feet, Limits: 0.0 to

25.0: Defines the maximum allowable divergence of Bit Depth
(BDep) from Measured Depth (MDep) before an “Off Bottom”
condition is detected after initial “On Bottom” conditions are
satisfied. This buffer variable prevents the system alternating
to/from “On Bottom” to/from “Off Bottom”, when conditions created
by inadequately compensated floating drilling rigs, cause the depth
tracking to “pull” the bit off bottom.
String Weight Threshold, (StWt), Units: Klbs, Limits: 25 to

2048: This parameter defines the hook load weight threshold for
switching from the “In-Slips” state top the “Out-of-Slips” state.
There should be enough difference between the Minimum String
Weight value and the “In-Slips Hook Load Threshold” to prevent
system oscillation between the “In-Slips” and “Out-of-Slips states.
69
Section 02
Minimum Weight-on-Bit, (MnWB), Units: Klbs, Limits: 20 to
255: Minimum Drilling Weight-on-Bit Threshold is used to determine
On-Bottom and Off-Bottom conditions. AFTER coming out of the
slips, the first On-Bottom condition establishes the bit depth when
the Weight -on-Bit data parameter (WOBs) reaches 30% of the
specified MnWB value. Subsequent “Off-Bottom conditions are
reported if the bit depth has diverged from the measured depth by
an amount greater than the “Off Bottom Travel Distance. This
parameter is used when the On Bottom Detection Method (OBDM)
used is ‘Hook Load Based’.
Hook Position Scale Factor, (HPsf), Units: Feet, Limits: 0.0500 to

0.5000: Hook Position Scale Factor is used to convert the Geolograph
Wheel sensor output counts to feet. The operation of the Geolograph
Wheel is often dependent upon the wheel itself and the environment
in which it is used. (I.E. it is affected by the line tension, the weather,
and ultimately the manufacturing differences.) The Geolograph wheel
sends two signals (four edges) per revolution, is thus hardware
dependent, and MUST be set accordingly. The operator should track
at least three joints of drill pipe at the beginning of the operation and
follow the formula listed below to calculate the proper scale factor.
This parameter is a hardware dependent number and must be set
accordingly. Refer to qMWDTM Depth Tracking Engineers Ref.
Manual, ¶3.1.11.
Instrument Measured Length = Measured depth tracked by

the system, with the current HPsf value, over the specified
number of joints of drill pipe.
Driller’s Pipe Tally = Tallied pipe length over the same

specified number of joints.
HPsf Adjustment Formula
Current HPsf Value = X
Instrument Measured Depth Driller’s Pipe Tally
Solve for X and adjust HPsf to new value that is more accurate.
Monitor accuracy by noting depth tracking depth and that of the
Driller’s depth over several joints and adjust accordingly.
70
Section 02
Pipe Length, (PLen), Units: Feet, Limits: 10.0 to 999.9: When an
“On-Bottom” condition is detected for the first time after coming out
of the slips, the Hook Position is forced to the operator specified
PLen value by setting the internal Geolograph Wheel counter to a
count that is equivalent to the PLen value. This value is used to
indicate to the operator when drilling is about to stop and another
pipe stand added. The accuracy and performance of the depth
tracking system does not depend on the absolute value of this
parameter. This value will not affect depth tracking and exists
primarily for operator reference. You will notice some jumps in this
number when connections are made; the final determinant of
accuracy is the measured depth at each Kelly down position and
over a length of numerous joints of drill pipe. Refer to qMWDTM
Depth Tracking Engineers Ref. Manual, ¶3.1.12.
Heave Compensation Full Scale, (HCfs), Units: Feet, Limits: -99

to 99: This parameter defines the maximum heave distance when
the Heave Compensation Sensor is at full scale. When not using a
Heave Sensor, set this variable to zero (0).
Heave Compensation Offset, (HCo), Units: Feet, Limits: -99 to

99: This parameter defines the sensor offset that is subtracted from
the scaled heave value for output. When not using a Heave
Sensor, set this variable to zero (0).
Heave Comp. Averaging Number, (HCn), Units: 0.1 Second,

Limits: 0 to 10: This parameter defines the time over which the
optional Heave Comp. Sensor measurements are averaged, for
Non-Floating or Non-Compensated rigs, this value (HCn) or the
Heave Compensation Sensor full-scale (HCfs) value, should be set
to zero (0).
Secondary Compensation Full Scale, (C2fs), Units: Feet,

Limits: -99 to 99: This parameter defines the full-scale value of the
Secondary compensation Sensor full-scale output. When not using
a Heave Sensor, set this variable to zero (0).
Secondary Compensation Offset, (C2o), Units: Feet, Limits: -99

to 99: C2o defines the sensor offset that is subtracted from the
scaled sensor value for the output. When not using a Heave
Sensor, set this variable to zero (0).
71
Section 02
Secondary Compensation Averaging Number, (C2n), Units:
Feet, Limits: 0 to 10: C2n defines the averaging period for the
optional Secondary Compensation Sensor. This does not affect the
update period, which is fixed at 0.1 second. For land and non-
compensated rigs, where Secondary Compensation would not be
used, this value or the Secondary Compensation Sensor full-scale
value should be set to 0.
Sensor Drive Level Averaging Number, (SDn), Units: 0.1

second, Limits: 0 to 20: This variable defines the period over
which sensor inputs are averaged. This number does not affect the
sensor update period, which is fixed at 0.1 second. Actual limits =
0.0 to 2.0 seconds.
Constant Time ROP Averaging Number, (ROPn), Units:

Minutes, Limits: 1 to 6: This variable specifies a fixed period of
time, by defining the averaging number, that determines the
averaging period in units of minutes. The update time remains
fixed at 1 minute. Refer to qMWDTM Depth Tracking Engineers Ref.
Manual, ¶3.1.18.
Constant Distance ROP Averaging Number, (ROPd), Units: 0.5

Feet, Limits: 1 to 20: This variable specifies a fixed length of
MDep, by defining the averaging number, used to determine the
ROP by measuring the time required to penetrate the specified
length of MDep. The update is not affected and remains at 0.5-foot
intervals. Actual limits: 0.5 to 10.0 feet. Refer to qMWDTM Depth
Tracking Engineers Ref. Manual, ¶3.1.19.
Depth Tracking Data Update Time, (DTUT), units: Seconds,

Limits: 1 to 100: Defines the time between updates from the
receiver for Depth Tracking Data. Sensor update is fixed at 0.1
seconds. Each update from the receiver creates a record in the file
setup in the qMWD_PC program, and can eventually create a very
large file. Therefore, longer update times from the receiver may be
appropriate for slow ROP and shorter update times for higher ROP.
An update time of 2-4 seconds is a good average to start with, but
large files will be created regardless, over the course of a job.
Refer to the File Management section in qMWD_PC program for
instructions on efficient ways to store data.
Refer to Depth Tracking section for details on setting up Surface

System for Depth Tracking.
72
Section 02
Depth Tracking System for GE Power Systems Tensor MWD
Objectives: The objectives of this technical note are to clarify

some of the basics of the QDT-qMWD™ Depth Tracking
System. The reader is encouraged to review the qMWD™
Depth-Tracking Engineer's Reference Manual.
Summary: The major points made by this document, with

regards to the "MPRx-D3 V01.60" Depth-Tracking Firmware
are summarized as follows:
1. Simply stated, the Depth-Tracking System - a.k.a.

"DTS" - is a relative measurement system that
measures the difference between the bottom of the hole
and the bit in units of "depth-counts".
2. The operator is required to initialize the system by

entering an absolute value of Measured Depth, which
defines the current length of the borehole in feet.
3. The depth-tracking system internally keeps all length

variables in units of depth-counts. Units of depth-counts
are converted to units of feet by the operator-specified
value of the Hook Position Scale Factor – "HPsf" –
nominally, 0.1 feet-per-depth count with a standard QDT
Geolograph wheel.
4. Changes to the Hook Position Scale factor – "HPsf" –

may be made at any point in the drilling cycle with
predictable and appropriate results.
5. The Reported Measured Depth – "MDep" – is only

affected by a change in HPsf to the extent of the amount
of hole drilled since initially tagging bottom from being in-
slips last or manually setting "MDep" – whichever
occurred last. If drilling ahead has not occurred since
either of these events, the reported measured depth, in
feet, will not change.
73
Section 02
6. Again, the Depth-Tracking System is a relative
measurement system that measures the difference
between the bottom of the hole and the bit location along
the borehole in units of "depth-counts". Therefore,
manually entering a new Measured Depth value or
changing "HPsf" will effect changes to the Reported Bit
Depth, in feet, while retaining the measured difference in
depth-counts.
7. The reported depths increase in a positive direction when

drilling ahead.
8. The Hook Position – "HP" – is initialized to the specified

Pipe Length – "PLen" – when initially tagging bottom after
coming out of the slips. The reported hook position will
decrease while drilling ahead and will be nominally zero
when the Kelly is drilled down to the stop position. The
use or accuracy of PLen or HP does not affect the
accuracy of the reported depths.
9. When not in use, the "Heave" and/or "Secondary"

compensation measurement inputs must be disabled
when configuring the DTS with the qMWDCnfg/W32TM
program. Failure to do so will introduce random noise
into the DTS measurements.
10. With the advent of the Variable Units Definition Utility

(qMWD V01.20), depth-tracking units presented to the
user on the PC may be in units other than feet. However,
the receiver always communicates in length-units of feet
and unit conversions occur in the PC.
74
Section 02
General Description:
The qMWD™ Depth-Tracking System, a.k.a. the "DTS", is a
relative measurement system. It cannot determine absolute
values of depth - it can only measure changes in depth. Given
a calibrated depth measurement input signal, the DTS can
accurately measure changes in depth. Given that the operator
has provided an initial and accurate measured-depth value, it
will supply reported depths in absolute values of depth from
the surface.
There are two primary depth values provided by the Depth

Tracking System.
• Measured Depth - "MDep" - is the conventional term used

by drillers to describe what is actually the length of the
borehole. (Refer to TVD or True Vertical Depth) Measured
Depth, by convention, is always a positive number
downwards relative to the earth's surface. Measured Depth
must be properly initialized by the operator to ensure that
the Reported Measured Depth is accurate. Typically, this
information is provided to the DTS operator by the driller.
• Bit Depth - is the location of the bit along the length of the
borehole relative to the surface.
The measurement-input signal allows the DTS to count

changes to the bit depth. The DTS actually requires two
count-input signals that are in quadrature phase. The 90-
degree-out-of-phase attribute of these signals allows the DTS
to also determine the direction that the bit is moving. The units
of distance used internally by the measurement system are
referred to as depth-counts. The depths as reported by the
DTS to other qMWD™ surface-system components, such as a
PC, are always in units of feet. Conversions from feet to other
units of length are performed locally in the PC - not by the
surface receiver/DTS. The conversion from depth-counts to
feet is based on the Hook-Position Scale Factor - "HPsf",
which is in units of feet per depth-count. The standard QDT
depth-tracking wheel is nominally 0.40 feet per revolution and
0.10 feet per count. The diameter and type of cable used will
affect the actual value of HPsf. The MWD operator may
75
Section 02
calibrate the depth encoder and enter a calibrated Hook-
Position Scale Factor (HPsf) value from either the
qMWD/W32TM Configuration Program (Depth-Tracking
Controls Menu) in qMWDCnfg/W32™ or the qMWD/W32™
Real-Time System Interface Program (System Configuration
Dialog window) in qMWDPC/W32™. In general, the
experience has been that an HPsf value in the order of 0.107
to 0.108 feet per depth-count is appropriate on many rigs.
AGAIN, the reported Bit Depth and Measured Depth are

measurements along the length of the borehole and are
positive values relative to the surface. The operator provides
an initial Measured Depth in feet, which is converted to depth-
counts using the calibrated value of Hook-Position Scale
Factor - "HPsf". The operator, using the qMWDPC/W32™
Program, may also input a value of Bit Depth - "BDep" (a.k.a.
"Dpth)". However, when first tagging bottom with the bit after
coming-out-of-slips, the Bit Depth value is automatically forced
to the value of the Measured Depth. Changes in the Bit Depth
are then measured relative to this initial on-bottom depth
value. Simultaneously, the Hook Position value - "HP" - is
preset to the value specified by the operator for the nominal
Pipe Length - "PLen".
The Hook Position value will decrease with increased bit

depth. The intent is that when a nominal length of pipe, or a
nominal stand of pipe, is drilled to the Kelly Down position, the
Hook Position will be approximately zero. In addition, as bit
depth increases from the initial on-bottom depth value in a
positive direction, the Measured Depth increases. When the
bit is pulled off-bottom, the bit-depth decreases, the hook
position increases and the measured depth is unchanged. As
the bit moves back towards bottom, the bit depth increases
and the hook position decreases. The measured depth will
remain unchanged while the bit depth is less than the bit
depth. The measured-depth will only increase when the bit-
depth indicates that additional length of borehole has been
drilled. The initial on-bottom depth value is not affected by
pulling off-bottom and tagging bottom a second and
subsequent times, until an in-slips condition occurs. NOTE
that the accuracy of Pipe Length does not, in any way, affect
76
Section 02
the accuracy of the reported Bit or Measured Depths - the
Hook Position value is only provided for convenience and
might be used to judge the time remaining to drill down the
current length of pipe.
Bit "In-Slips" State: While the DTS is in the "in-slips" state

the hook position will automatically change, but the bit depth
and measured depth will not automatically change. An in-slips
condition is determined or effected as follows:
• Manual Mode: This mode is put into effect by issuing an
"In-Slips" command ("Slips!"), which can be accomplished
from the "Depth Tracking Commands" pull-down window in
qMWDPC/W32TM.
• Automatic Mode: When the reported Bit-Depth is more
than the specified In-Slips Travel Distance Threshold -
"ISTD" - from the measured depth and the reported Hook
Load - "HL" - is below the specified In-Slips Hook Load
Threshold - "ISHL".
Bit "Out-of-Slips" State: In-slips to out-of-slips state change

is only part of the automatic depth-tracking mode. The state
change is automatically detected when the reported Hook
Load - "HL" - is above the specified Minimum String Weight -
"StWt". When this state change is detected the DTS attempts
to measure Off-Bottom Hook Load - "OBHL". The value of
"OBHL" is necessary to derive the Weight-On-Bit - "WOBs",
which, in turn, is required to automatically detect an on-bottom
condition in the automatic, hook-load-based, on-bottom
detection method. In addition, the reported bit-depth begins
tracking the changes to the hook position.
77
Section 02
Bit "On-Bottom" State: When an on-bottom condition is first
detected after being in-slips, the bit depth is set to the
measured depth and the hook position is set to the specified
pipe/stand length. An on-bottom condition is determined or
effected as follows:
• Manual Mode: By issuing a "Bttm" command from the

"Depth Tracking Commands" pull-down window in
qMWDPC/W32TM.
• Automatic "Depth-Based" Mode: When the reported Bit-
Depth is equal to the measured depth and the pumps are
on.
• Automatic "Hook Load-Based" Mode: When the
reported Weight-on-Bit - "WOBs" - exceeds the specified
Minimum Weight-On-Bit - "MnWB" and the pumps are on.
The indicated Weight-on-Bit is computed as the measured
or specified Off-Bottom Hook Load - "OBHL" - less the
current Hook Load measurement - "HL".
78
Section 02
Changing the Hook-Position Scale Factor…
Ideally, as in virtually any instrumentation system, any changes to

the DTS control and calibration parameters should be made while
the system is in a static state. In this case, an "in-slips" state is the
appropriate static condition. Conversely, on-bottom and drilling
ahead would be the least ideal condition to make changes to the
DTS control and calibration parameters. However, it has been
stated that it is not always possible to effect the necessary changes
to the DTS parameters within the time available while in-slips.
Effective with version V01.60 of the surface receiver, making
changes to the Hook Position Scale Factor - "HPsf" - during any
drilling state are possible.
The DTS assumes that the most recent of either an operator-

entered value of Measured Depth or the initial on-bottom measured
depth, in units of feet, is correct. This assumption is based on the
premise that if the measured depth reported by the DTS does not
agree with the driller's tally, then the DTS operator will manually
enter/correct the measured depth while in-slips or before tagging
bottom. However, it may not be possible to calculate and effect a
correction to the HPsf until after the string is out-of-slips, possibly
on-bottom, and possibly drilling ahead.
The affects on the reported hook position and various depth

parameters are as follows:
Hook Position: Is modified by the change in depth-counts per

pipe length. If the bit has tagged bottom, but drilling has not
commenced, the reported Hook Position, in feet, will not be affected
by a change in the HPsf value. If on-bottom and drilling ahead, the
new value of "HP" will properly reflect the correct number of feet
remaining to be drilled down based in the number of depth-counts
drilled down and the new number of depth-counts per length of
pipe. In all other drilling states, the value of "HP" is
inconsequential.
Measured Depth: The reported value of MDep, in feet, is only

modified based on the number of depth-counts that MDep has
changed, since an initial-on-bottom-measured-depth was set or the
most recent occurrence of a manually entered MDep. The
assumption is that if the system is on-bottom and drilling ahead, the
depth-count changes in MDep since drilling commenced or since
MDep was specified, are correct – then that is what is measured.
79
Section 02
Then the number of feet those new counts represent, according to
the new HPsf definition, should change. If MDep was manually
entered or the bit has initially tagged bottom, but drilling has not
commenced, the reported MDep will not be affected because of a
change in HPsf. NOTE: When correcting the HPsf value, it is
recommended that the operators enter a new MDep value first,
preferably while in-slips or before tagging bottom, and then enter
the new HPsf.
Bit Depth: Is modified to keep the difference between MDep and

BDep constant in units of depth-counts - this is what the system
measures and is logically assumed to be correct. Therefore, if the
reported bit depth indicates the bit is off-bottom, the reported bit-
depth, in feet, will be affected by a change in HPsf. Also, note that
whenever MDep is modified by the operator, that BDep is also
automatically modified to keep the difference between MDep and
BDep constant in units of both depth-counts and feet - again. This
is what the system measures.
80
Section 02
Miscellaneous Depth Parameters: As previously stated, all depth
parameters are internally processed or computed in units of depth-
counts based on HPsf in feet-per-count. Therefore, whenever HPsf
is modified, there are several parameters that must be rescaled in
depth-counts to effect the same values reported in feet. The
following is a list of such parameters, which are input and/or output
by the receiver/DTS…
"SDep" - Survey Depth Tag
"WDep" - Word Depth Tag
"TVD" - True Vertical Depth (not used at this time)
"MSDT" - Manually-Entered Survey Depth Tag
"Heav" - Optional Heave Compensation Sensor
"DC2" - Optional Secondary Compensation Sensor
Heave and Secondary Depth Compensation inputs:
The DTS provides two sensor inputs for use on offshore platforms.
These inputs compensate for rig-heave.
Rig Heave sensor. This is a pull-wire sensor that measures the

vertical motion between the drilling rig structure and a point that is
fixed relative to the seabed (i.e. to the Earth). The sensor itself is
usually mounted to the rig structure near one of the several heave
compensators. The line is attached to a point moving relative to the
seabed such as the moving sheave of one of the guideline
tensioners. These often have a mechanical advantage of 4, so a
sensor with a 12-foot line movement will translate into a vertical
measurement range of 48 feet. This sensor should be used for rig
heave compensation without the secondary compensation sensor
(below) when the Geolograph line is connected in the normal way
to the moving traveling block/swivel/kelly.
Secondary Compensation Sensor. In the event that the
Geolograph line is connected to the FIXED block, then an additional
measurement is necessary to add in the effect of the block
separation. This additional measurement is the Secondary
Compensation sensor. The sensor is mounted on the fixed block
and the line is attached to the moving block.
81
Section 02
Depth Tracking on Land or Fixed Platforms Offshore
When not in use, either or both depth compensation

measurements must be disabled when configuring the DTS
with the qMWDCnfg/W32TM program. Failure to do so will
introduce random and undesirable noise into the DTS
measurements.
Caution: When the Heave Sensor Input is not

used/connected, the "Heave Compensation Averaging
Number" MUST be set to 0 to disable the input and prevent a
floating/un-terminated input from introducing noise into the
depth-tracking system measurements.
Caution: When the Secondary Compensation Sensor Input is

not used/connected, the "Secondary Compensation Averaging
Number" MUST be set to 0 to disable the input and prevent a
floating/un-terminated input from introducing noise into the
depth-tracking system measurements.
When a compensation-input is enabled, changes to the input

are added to the bit depth. Changes are relative to either
coming out-of-slips or the initial on-bottom event after being in-
slips. A positive heave-input change will tend to decrease the
bit depth to compensate for the increased, heave-induced,
depth-count measurements.
82
Section 02
Getting Started to Run Depth Tracking
Run the Variable Units program, to convert the value of the

variables to either Imperial or Metric display.
Note: Acquire necessary data values

a. Measured Depth – Driller’s measured depth of the hole.
b. Bit Depth – Driller’s total length of drill string (BHA and Drill
Pipe) measured from topmost joint of drill pipe, located at one
foot above the rotary table. Note: If using a Top-Drive system,
the topmost joint of drill pipe would be the top of the last stand
completely drilled down.
c. Pipe Length – The nominal length of an average length of
drill pipe, usually 30.0 to 30.5 feet. If the system is using a Top
Drive, then PLen will be 90.0 to 93.0 feet.
d. Insure that Hook Position Scale Factor (HPsf) is set to
0.1070 or 0.1080.
e. Insure that the In-Slips Travel distance Threshold (ISTD) is
set at 21 feet.
f. Insure that the In-Slips Hook Load Threshold (ISHL) is set to
a value greater than the weight of the block and kelly. 16-24 K
is a good value to use.
g. Insure that the Minimum String Weight (StWt) is set to a
value at least 16K greater than the ISHL. This will keep the
system from fluctuating in and out of slips while making a
connection.
Sensor Calibration
a. With the drill string in the slips, have the driller hold the block
and kelly assembly stationary and Zero the Hook Load. The
command is located in the “Depth Tracking Commands” pull-
down window in the qMWDPC/W32™ program. This will take
the measured weight of the block and kelly and essentially use
the value as a zero (0) weight value.
b. Have the driller connect the kelly to the drill string and pick up
the drill string out of the slips. With the system held steady, let
the drill string remain motionless for approximately 15 seconds.
The program will calculate the Off Bottom Hook Load (OBHL).
c. Insure that the value of the HPsf is entered as 0.107 or 0.108.
Note: the PLen does not affect the values of the HPsf and the
MDep and BDep.
83
Section 02
Initial Calibration of the “On-Bottom” State of the Drill String
This procedure takes cooperation between the MWD operator and

the driller. It is advised to have two operators on tour to do this
initially, with one operator on the PC and the other operator on the
floor with the driller for easier communication.
a. Set the value of the Bit Depth (BDep) to a number that is
shallower than the actual bit depth reported by the driller.
Recommend using a value approximately one joint length less
or approximately 30 feet.
b. Have the driller ease the drill string down slowly until he tags
bottom and stop.
c. At this point Select the “On Bottom” command under the Depth
Tracking Commands under the drag down menu in
qMWDPC/W32 program. This will place the Bit Depth (BDep)
equal to the Measured Depth (MDep). Note: The Hook Position
will reflect the value of the Pipe Length (PLen) value. As stated
above, this will not affect the accuracy of the depth tracking.
The value will be reset on the next connection.
84
Section 02
Mud Flow/Rotary Drive/Generic Sensor Controls:
This selection allows viewing and editing of MudFlow Control

variables, rotary Drive variables, and Generic Sensor variables.
Mud Flow Processing Controls
Pump 1 Displacement Factor, (PDf1), Units: Gallons, Limits: 0.00

to 99.99: Pump Displacement Factors define the mud flow rate per
stroke and are used to derive values GPM1, GPM2, and GPM from
SPM1 and SPM2.
Pump 2 Displacement Factor, (PDf2), Units: Gallons, Limits: 0.00

to 99.99: Pump Displacement Factors define the mud flow rate per
stroke and are used to derive values GPM1, GPM2, and GPM from
SPM1 and SPM2.
85
Section 02
Pump Strokes Averaging Number, (SPMn), Units: Strokes, Limits:
1 to 10: This parameter defines the number of strokes over which the
time between strokes is averaged. This average value is then
inverted to yield the pump stroke rate measurements (SPM1 and
SPM2) in units of strokes per minute.
Pump Flow Data Update Time, (PFUT), Units: Seconds, Limits: 0

to 100: Defines the time between updates from the receiver for Pump
Flow Data.
Rotary Drive Processing Controls
Rotary Drive Ratio, (RPMk), Limits: 0.10 to 99.99: This is the

ratio/reduction between the measured shaft speed and the Kelly
bushing Speed (RPM).
Rotary Speed Averaging Number, (RPMn), Units: Seconds,

Limits: 1 to 10: This defines the averaging period of the speed
sensor measurements. This number does not affect the update
period, which is fixed at 1 second.
Generic Processing Controls
Generic Sensor 1 Full Scale, (G1fs), Limits: 0.1175e-37 to

3.403e+38: Defines the full-scale value magnitude from the generic
sensor GS1.
Generic Sensor 1 Offset, (G1o), Limits: 0.1175e-37 to 3.403e+38:

Defines the offset correction value which is subtracted from the scaled
value of generic sensor GS1.
Generic Sensor 1 Averaging Number, (G1n), Units: 0.1 Second,

Limits: 1 to 10: Defines the time over which generic sensor GS1
readings are averaged. This number does not affect the update
period, which is fixed at 0.1 second.
Generic Sensor 2 Full Scale, (G2fs), Limits: 0.1175e-37 to 3.403e+38:
Defines the full-scale value magnitude from the generic sensor GS2.

86
Section 02
Generic Sensor 3 Full Scale, (G3fs), Limits: 0.1175e-37 to

3.403e+38: Defines the full-scale value magnitude from the generic
sensor GS3.


Generic Sensor Data Update Time, (GSUT), Units: Seconds,

Limits: 0 to 100: Defines the time between updates from the receiver
for Generic Sensor Data.
87
Section 02
Turbine Controls
Turbine Voltage-On Threshold (TuVT), Units: Volts, Limits: 0.00

to 40.0. This control specifies the voltage threshold over which the
TVOk bit will be set in the turbine status register (TuSR) as long as an
over-voltage condition does not also exist.
Turbine Current-On Threshold (TuAT), Units: Amps, Limits: 0.000

to 2.000. This control specifies the current threshold over which the
TAOk bit will be set in the turbine status register (TuSR).
Turbine Over-Voltage Threshold (TOVT), Units: Volts, Limits: 0.0

to 50.0. This control specifies the voltage threshold over which the
TSOV bit will be set in the turbine status register (TuSR).
Turbine Over-Voltage Reset Delay (OVRD), Units: Seconds,

Limits: 2 to 60. This control specifies the time delay in seconds
between detection of an over-voltage condition and an attempted
reset of the over-voltage condition.
Turbine Over-Voltage Reset Attempts (OVRn), Limits: 2 to 20.

This control specifies the maximum number of over-voltage reset
attempts within a specified time interval of OVRi seconds. If the
number of resets occurring within this OVRi time interval reaches the
OVRn limit, then the regulator will be disabled until the operator
intervenes with a Reset Over-Voltage Detection Command (ROVD!)
or the Turbine processor is reset.
88
Section 02
Over-Voltage Reset Time Interval (OVRi), Units: Seconds, Limits:
10 – 3600. This control specifies the maximum number of over-
voltage reset attempts within a specified time interval of OVRi
seconds. If the number of resets occurring within this OVRi time
interval reaches the OVRn limit, then the regulator will be disabled
until the operator intervenes with a Reset Over-Voltage Detection
Command (ROVD!) or the Turbine processor is reset.
Turbine Flow-True Speed (TFTS), Units: Revolutions per Minute

(Rpm’s), Limits: 0 – 65,535. This control specifies the minimum
turbine RPM for which turbine flow is determined to be “On”. The use
of this threshold in combination with Turbine Flow-False Speed
Threshold (TFFS) provides for hysteresis between the flow-on-off
state changes. A minimum of 20% is recommended, which can be
achieved by
TFFS = TFTS x 0.8
Turbine Flow-False Speed (TFFS), Units: Revolutions per Minute

(Rpm’s), Limits: 0-65,535. This control specifies the maximum
turbine RPM for which turbine flow is determined to be “Off”. The use
of this threshold in combination with Turbine Flow-True Speed
Threshold (TFTS) provides for hysteresis between the flow-on-off
state changes. A minimum of 20% is recommended, which can be
achieved by
TFFS = TFTS x 0.8
Turbine High Temperature Threshold (THTT), Units: Fahrenheit,

Limits: 32 to 392. This control specifies the temperature threshold
over which the High Temperature Warning flag (ThiT) is set. Note:
The Variable Units Display Utility will display the units desired.
89
Section 02
DOWNLINK CONTROL PARAMETERS
90
Section 02
Down Link Controls and Procedures:
Down Link Commands (DwnL): This switch ENABLES or

DISABLES the Down Link capabilities of the MWD system. If the
operator is not versed in the use of the DownLink commands, or has
not performed the service, then he should always switch the system to
the DISABLED mode.
Command Time Period (DLTP): This selection is not operable if

DwnL is DISABLED. This variable defines the maximum length of a
DOWN LINK pulse (PUMPS UP) and the maximum length of the
FLOW OFF (PUMPS OFF) command value intervals or windows.
COMMANDS are determined by the number of DOWN LINK pulses,
spaced apart by equal PUMP DOWN intervals. NOTE: the last
FLOW OFF INTERVAL between the LAST DOWN LINK pulse and the
PUMPS UP command to continue operations, determines the VALUE
of the command (N x DLTP). This FLOW OFF period is usually longer
than the value of DLTP.
Note: A 60 second recommended DLTP dictates that if the

pumps are up/down for a period of time greater than 60 seconds,
then the command is not initiated.
Command Set (DLTy), Mode Number or Rate Sequence: This

control variable defines the types of commands enabled for Downlink
transmission. This control effectively redefines the Downlink
command numbers and values. If DwnL is DISABLED the setting for
this variable is not activated. If the operator intends to use the
DOWNLINK commands, then this variable should be set to the type of
command desired for the operation, either Mode Number or Rate
Sequence.
Mode Number (ModN): This switch will allow the operator to change
to any of the four different modes of operation. In this case, each
mode defines the Pulse Width, Survey and T/L Sequence Numbers,
Acquisition Time, and T/L Transmit Time. NOTE: the operator is
limited to changing only the Modes, not the individual settings in each
mode. Therefore, the operator should pay special attention to the
design and selection of the modes that he plans to institute in the
program before the tool is programmed for downhole operation.
RECOMMENDED OPERATION.
91
Section 02
Rate/Sequence: This switch will allow the operator more flexibility in
changing the operation of the tool. There are three options that will
allow the operator to change: (A) Only the pulse width, (B) Only the
T/L sequence, or (C) Only the survey sequence number. The
operator can change all three by stepping through the change
procedures and commanding the MWD tool/surface sensors to
change each particular phase to fine tune the operation. It must be
noted, however, that this procedure will take a lot of time.
To change the MODE NUMBER only use the Command Number 2 to

specify a mode number change. NOTE: this is only if the Mode
Number switch is selected. Then use the corresponding Command
Value to select the desired MODE NUMBER. There are four different
Mode Number Options to select from with each having a particular
command value.
92
Section 02
Mode Number Change Command Table
Mode Number
Command Data
Value (N) Sequence Change
1 Mode Number #1 (Mod1)

93
Section 02
Mode Number Down Link Command Sequence Diagram
Using a command time value of 60 seconds will designate one-minute intervals to obtain the desired mode number.
Any action taken, pumps up or pumps down, within a particular window, will satisfy the command for that particular window and will
immediately start the process for the next window. Any lack of action (surpassing a Command Number window) in the Command
Number will render the DownLink procedure invalid. Surpassing the Command Value (pumps down) beyond the last window will not
execute the DownLink procedure.
Command Number Command Value
Pumps Pumps Pumps Mode Mode Mod Mode

Up 1 Down 1 Up 2 1 2 3 4
Wait 2 min. and bring pumps up at

Pumps Down 2 (30 seconds) required time to attain desired Mode
½ Command Time Period of
60 seconds. Number change.
Using a 60 second Command Time Period: It is recommended that after the Pumps Up 1 command, initiate Pumps Down 1 command at 35 seconds,
let pumps stay down and then initiate Pumps Up 2 command at 35 seconds. Let pumps run for 35 seconds and then initiate Pumps Down 1
command. Then wait the required amount of time for initiating mode number change. 1 minute = Mode 1, 2 minutes = Mode 2, 3 minutes = Mode
3, 4 minutes = Mode 4, provided the Command Time Period = 60 seconds.
A 35-second pump up/down interval is recommended to prevent the command from exceeding the 60-second time limit. Most rigs are somewhat
sluggish in their response and thus require some tolerance in the time allowed. A 60-second DLTP also allows for a simpler calculation of the time
requirements to initiate the change. A 2-minute pump down command value, after the satisfying command number, to the pumps up maneuver will
place the system in Mode 2.
Note: the pumps do not have to be brought up to the maximum rate. The required rate is only that which is enough to activate the tool and attain a
standpipe pressure greater than the pumps on threshold.
Rate Sequence Option
PULSE WIDTH
To change the pulse width only use the Command Number 2 to specify a rate change. NOTE: this is
only if the Rate/Sequence variable is selected. Then use the corresponding Command Value to
select the desired Pulse Width. There are 10 different pulse widths to select from with each having a
particular Command Value.
Pulse Width Pulse Width

Command Value (N) (seconds)
1 0.250
2 0.375
3 0.500
4 0.600
5 0.800
6 1.000
7 1.200
8 1.500
9 2.000
10 3.000
Rate/Sequence Option
PULSE WIDTH DOWN LINK COMMANDS

Any action taken, pumps up or pumps down, within a particular window, will satisfy the command for that particular window and
will immediately start the process for the next window. Any lack of action (surpassing a Command Number window) in the
Command Number will render the DownLink procedure invalid. Surpassing the Command Value (pumps down) beyond the
last window will not execute the DownLink procedure.
Pumps Pumps Pumps 0.250 0.325 0.500 0.600 0.800 1.000 1.200 1.500 2.000
Up 1 Down 2 Up 2
Pumps Down 2 (30 seconds)

½ Command Time Period of Wait and bring pumps up at required time to attain desired Pulse Width change.
60 seconds
READ RECOMMENDATIONS!!!!!!
Using a 60-second Command Time Period: After the initial Pumps Up 1 command, it is recommended to initiate the Pumps Down 1
command at 35 seconds. Allow the pumps to stay down for 35 seconds and then initiate Pumps Up 2 command. Let pumps run for 35
seconds and then shut them down. Then wait the required amount of time for initiating mode number change. 1 min = 0.25sec, 2 min =
0.375sec, 3 min = 0.50sec, 4 min = 0.60sec, 5 min=0.8sec, 6 min=1.00sec, 7 min.=1.2 sec, 8 min.=1.5sec, 9 min=2.00sec, 10 min=3.0sec
pulse. Each minute after the Pumps Down 2 command will place the DownLink Command in the middle of the window.
Note: the pumps do not have to be brought up to the maximum rate. The required rate is only that which is enough to activate the tool and
attain a standpipe pressure greater than the pumps on threshold.
96
Section 02
Rate Sequence Option
TOOL FACE/LOGGING SEQUENCE
To change the T/L Sequence only use the Command Number 3 to specify a sequence change.
NOTE: this is only if the Rate/Sequence variable is selected. Then use the corresponding Command
Value to select the desired T/L Sequence. There are four different T/L Sequences to select from with
Toolface/Logging Sequence Number Change Command Table

each having a particular Command Value.
T/L Sequence Data Sequence

Command Value (N) Change
1 T/L Seq #1 (“TSq1”)

2 T/L Seq #2 (“TSq2”)
3 T/L Seq #3 (“TSq3”)
4 T/L Seq #4 (“TSq4”)
RATE/SEQUENCE OPTION
Toolface/Logging Sequence
Any action taken, pumps up or pumps down, within a particular window, will satisfy the command for that particular window and will
immediately start the process for the next window. Any lack of action (surpassing a Command Number window) in the Command
Number will render the DownLink procedure invalid. Surpassing the Command Value (pumps down) beyond the last window will not
execute the DownLink procedure.
Pumps Pumps Pumps Pumps Pumps T/L T/L T/L T/L

Up 1 Down 1 Up 2 Down 2 Up 3 1 2 3 4
Pumps Down 3 (30 seconds) Wait 3 min. and bring pumps up at required time to attain
½ Command Time Period desired ToolFace/Logging Sequence change.
READ THE RECOMMENDED INSTRUCTIONS!!!!!!

Using a 60 second Command Time Period: It is recommended that after the Pumps Up 1 command, to initiate Pumps Down 1 command at 35
seconds, and let pumps stay down for 35 seconds and then initiate the Pumps Up 2 command. Let pumps run for 35 seconds and then initiate
the Pumps Down 2 command. Wait 35 seconds and initiate the Pumps Up 3 command. Wait 35 seconds and initiate the Pumps Down 3
command. Then wait the required amount of time for initiating mode number change. 1 minute = TSq1, 2 minutes = TSq2, 3 minutes = TSq3, 4
minutes = TSq4. Each minute after the Pumps Down 3 command will place the DownLink Command in the middle of the window. Note: the
pumps do not have to be brought up to the maximum rate. The required rate is only that which is enough to activate the tool and attain a
standpipe pressure greater than the pumps on threshold.
98
Section 02
SURVEY SEQUENCE:
To change the Survey Sequence only use the Command Number 4 to specify a sequence change.
NOTE: this is only if the Rate/Sequence variable is selected. Then use the corresponding Command
Value to select the desired Survey Sequence. There are four different Survey Sequences to select
from with each having a particular Command Value.
Survey Sequence Number Change Command Table
Survey Sequence Data Sequence

Command Value (N) Change
1 Survey Seq #1 (“SSq1”)

Any action taken, pumps up or pumps down, within a particular window, will satisfy the command for
that particular window and will immediately start the process for the next window. Any lack of action in
a window (surpassing the time window) in the Command Number will render the command number
invalid. Surpassing the Command Value (pumps down) beyond the last window will not execute a
command.
Survey Sequence
Any action taken, pumps up or pumps down, within a particular window, will satisfy the command for that particular window
and will immediately start the process for the next window. Any lack of action (surpassing a Command Number window) in
the Command Number will render the DownLink procedure invalid. Surpassing the Command Value (pumps down)
beyond the last window will not execute the DownLink procedure.
Pumps Pumps Pumps Pumps Pumps Pumps Pumps Surv Surv Surv Surv
Up 1 Down 1 Up 2 Down 2 Up 3 Down 3 Up 4 1 2 3 4
Wait 2 min and bring pumps up at required time to

Pumps Down 4 (30 second)
½ Command Time Period of attain desired Survey Sequence change.
60 seconds
READ RECOMMENDATIONS!!!!!
Using a 60-second Command Time Period: It is recommended that 35 seconds after the Pumps Up 1 command to initiate
the Pumps Down 1 command. Repeat the pump up/down commands three more times, for a total of 4 commands. Then
wait the required amount of time for initiating mode number change. 1 minute = SSq1, 2 minutes = SSq2, 3 minutes =
SSq3, 4 minutes = SSq4, provided the Command Time Period = 60 seconds.
Note: the pumps do not have to be brought up to the maximum rate. The required rate is only that which is enough to
activate the tool and attain a standpipe pressure greater than the pumps on threshold.
100
Section 02
EXAMPLE: Mode Number Change Using DownLinking
This procedure will change the Survey Sequence, T/L Sequence, and
the Pulse Length. Assume the operator desires to change from the
initial operating Mode 1 to Mode 3. The command for Mode Switching
is two Down Link Commands (Only if Mode Number in DLTy is
selected). Apply a Command Time Period (DLTP) of 60 seconds.
1. Bring the pumps up to a SPP above the “Flow On Threshold” for a
period of time longer than the Flow Evaluation Time (FEvT). Do not
exceed the 60-second window with the pumps up.
2. Shut the pumps down and leave the pumps down for the same
period of time, > 5 seconds, but < 60 seconds.
3. Bring the pumps up again to the same SPM/SPP for the same
period of time.
4. Bring the pumps down. This satisfies the command of two Down
Link pulses and commands the tool and surface gear to change
Modes. Leave the pumps down for the period of time of N x DLTP, in
this case N = 3. NOTE: that there are four options for the system’s
modes of operation. Therefore, to change from ANY mode to the
desired mode, in this case Mode 3, the operator simply leaves the
pumps down for a period of time > 150 seconds, but < 210 seconds.
The system is sloppy for a reason, and will recognize any command
within the range of +/- 0.5 x DLTP.
5. When the pumps are brought up to resume drilling or surveying,
both the tool and the surface gear will have changed to Mode 3. The
tool may take a minute longer before it begins the Synch Pulse
transmission, due to the change of the mod of operation. It is VERY
IMPORTANT that a copy of the PROGRAM CONFIGURATION, which
should be saved and printed for each run, is referred to for
confirmation of this change.
6. NOTE: A change in the DLTy will change the timing. It is
STRONGLY advised that the operator consider this when performing
any down link procedures, and make the appropriate adjustments.
7. Down Linking is a very important maneuver and should be
designed and performed with great care and attention. It is
recommended that the operator be on the rig floor during the
procedure and take the time to explain the procedure to other parties
involved in the operation, such as the driller, the directional driller and
the operator’s representative.
101
Section 02
A E
Access Level · 13 EFS · 3, 28, 64
Automatic "Depth-Based" · 78 Electronic Flow Switch · 3, 64
B F
Battery Voltage Formation Data Variables · 3, 44

Low Battery Threshold · 61 Data Sets · 44
Bit Depth · 68, 69, 74, 75, 76, 80, 83,

84 G
Gamma Rate Scale Factor · 59
C
Gamma/Battery
Capability Codes · 15 Processing Controls · 3,
Command Time Period · 27, 91, 94, 96, 58
98, 100, 101 Gravity · 51
Compensation · 71, 72, 81, 82
Configuration File
Forced Startup
*.MWD · 6
H
Heave · 67, 71, 74, 81, 82
Hook Load Sensor · 68
D Hook Position Scale Factor · 70, 73, 79,
83
Data Update Time · 72, 86, 87
Data Value Resolution · 42
Decoding Process · 32 I
M-ary Coding · 32
Depth Parameters · 81 Inclination Threshold · 29
Depth Tracking · 3, 12, 67, 68, 70, 71, 72, In-Slips · 69, 77, 83
73, 75, 77, 78, 82, 83 Invert Flow Sense · 64
Depth Tracking Controls ·
3, 12, 67
Directional Data Variables J
Magnetometer · 41
Directional Data Variables · 40 Job Site Environment · 50
Accelerometer · 41 Dip Angle · 43, 47, 48, 50, 51
Azimuth · 40 Gravity · 29, 51, 52
Dip Angle · 40 Magnetic Declination · 51
Inclination · 40 Magnetic Field · 41, 51
Total Gravity · 40, 47 Site Location · 50
Directional Processing
Controls · 53 L
Magnetic TFA Declination · 53, 54
Temperature Threshold · 53, 89 Labels
Toolface Calculation Type · 56 AqTN · 37
Directional Sensors · 49 aTFA · 29, 39, 40, 44, 47
Down Link · 3, 27, 91, 94, 101 AVer · 11
Ax · 40, 41, 56
102
Section 02
Ay · 40, 41, 56
Az · 40, 41
O
Azm · 40, 47, 57
BatV · 41, 43, 47 On Bottom · 68, 69, 70, 84
BatW · 43, 47 On-Bottom · 70, 71, 78, 84
CfgF · 11
DipA · 40, 47, 57
DLTP · 25, 27, 91, 94, 101 P
DLTy · 28, 91, 101
DTE · 12
Pipe Length · 71, 74, 76, 77, 83, 84
DwnL · 27, 28, 91
Pulse Amplitude Limits · 65
EvIM · 29
Pulse Width PwN · 35
Grav · 40, 47, 56
Pulser Type · 66
HdCk · 27
Inc · 1, 6, 40, 42, 47, 57 Pumps/Flow Evaluation
IncT · 29
MagF · 41, 47, 57
Controls · 62
ModN · 28, 35, 91 Pumps-On-Threshold · 62
Mx · 40, 41, 56
My · 40, 41, 56
Mz · 40, 41, 56 Q
NSyP · 26, 30
PWin · 30, 31 qMWDCnfg
PwN · 35 Auto Verify · 11
RxDT · 25, 26 Getting Started · 9
SHSz · 26 Introduction · 8
SrlN · 12 Link Adress · 10
SSNN · 36 Set-up Parameters · 10
SSqN · 38 Quality and Confidence Factors · 66
SyTy · 30
SyWF · 26
Temp · 41, 43, 44, 47, 57 R
THSz · 26
TLTN · 37
Rate/Sequence · 28, 92, 95, 96, 97, 99
TSNN · 36
Receiver · 19
TSqN · 39
ROP · 47, 48, 72
TuEn · 12
TxDT · 25, 26, 47, 48, 64
Load · 18
Load and Go · 22 S
Load from · 18
Sensor Calibration · 83
Special Telemetry Controls
M Pulser Drive Signal Widths · 31
PWin · 30
Synch Word Type · 30
Magnetic Data Information Site · 52
Store · 20
Magnetic Data Web Site
String Weight · 69, 77, 83
http
//www.ngdc.noaa.gov/seg/potfld/geo Surface Receiver
mag.html · 52
Magnetic Field · 51
Controls · 3, 65
Low/High Pulse Amplitude Limits · 65
Measured Depth · 68, 69, 70, 73, Survey Sequence · 3, 36, 38, 99, 100, 101
74, 75, 76, 79, 83, 84 Survey Time · 47
Mode Control Settings · 35
Mode Number · 27, 28, 35, 91, 92, 93, 94,
101 T
T/L Transmission Time Limit Controls ·
103
Section 02
37
Telemetry Controls Menu · 24
V
Header Size · 26
Receive Delay Time · 25 Voltage · 41, 43, 48, 61, 88, 89
Synch Pulses · 26
Synch Window Factor · 26
Transmit Delay Time · 25 W
Telemetry Warnings · 43
Toolface/Logging Sequence · 36, 37, 39, Weight-on-Bit · 70, 78
47, 51, 52, 97, 98
Transmitter · 19
Word Transmission Times ·
Turbine · 3, 10, 12, 88, 89 46
Turbine Controls · 12, 88 Word Update Times · 45
104
Section 02
NOTES
105
Section 02
NOTES
106
Section 02
g GE Power Systems
Tensor MWD
TOOLFACE OFFSET
PROCEDURE
rights reserved. “This document and all information and expression contained herein are the
property of GE Power Systems and is provided to the recipient in confidence on a “need to know”
basis. Your use of this document is strictly limited to a legitimate business purpose requiring the
information contained therein. Your use of this document constitutes acceptance of these terms.”
Notes
2
Version 2.00; February, 2002 TFO Procedure
Toolface Offset Procedure
The Toolface Offset Procedure is a separate program routine. It will
automatically start when the Configuration Routine is exited or the
operator can initiate the program independently. Please note that there are
very few differences from the DOS Toolface Offset Procedure, except for
the fact that the system is now in a Windows format.
This routine, when entered into, will communicate with the survey
electronics (MPTx Node 20) and/or the surface gear (MPRx Node 05) by
actively accessing the processors of each system. In the case of the MPTx
Node 20, the processor and the sensors are actually powered and
operating. You will notice the data updates on the screen, so, be aware of
any changes made and the results of those changes.
This program allows the operator to set the values for the Instrumentation
Mounting Offset (IMO) in the DownHole Tool, and the Drill Assembly
Offset (DAO) in the Driller’s Remote Terminal.
WARNING
If you disconnect the Transmitter before quitting this
screen normally, you will leave the Auto-Acquisition
(DiAA) mode "On" in the downhole tool, which will
consume battery power.
When this program is started, the system looks for the downhole tool
(LnkA 20) and the surface receiver (LnkA 05) to execute the sub routine.
3
If either of the systems is not on line then the program will time out and
informs the operator which address is not connected. This can take about
30 seconds.
Abort will end the program.
Retry will instruct the program to make another attempt to connect to both
of the processors.
Ignore will instruct the program to ignore the processor it could not
connect and continue with the connection and process already established.
Normal Field Procedure
When the operator is in the field, the procedure will dictate that the
DownHole Tool be corrected first, after the tool is built up. It is
possible that the Driller’s Remote Terminal will not be connected
and the first screen will be displayed. The operator will then
perform the Zero the Gravity Toolface procedure.
When the MWD Collar to Mud Motor offset (DAO) is measured,

in the event that a Universal Bottom Hole Orientation (UBHO) sub
is not used, then the operator will be required to enter the DAO
into the Driller’s Remote Terminal (DRT), Node 05. This
procedure is described below in the following pages.
4
If both processors are connected to the system, then the following screen
will be displayed.
The program will activate the transmitter processor (Node 20) and sensors
and display the IMO (Internal Mounting Offset) of the downhole tool, and
the DAO (Driller’s Assembly Offset) stored in the Driller’s Remote
Terminal. Both of these values will be displayed on the screen.
Note: If both systems are connected and powered and the routine times
out, the following screen will be displayed. The operator must
then check the system for a break in the connection.
If only one system is connected, one of the previous messages requesting

action to Abort, Retry, or Ignore will be displayed.
When the program is in operation, the values are continually being

updated (Number Of Updates) at a rate equal to the Steering Sampling
5
Rate (StSR) from the DownHole Tool. This causes the screen to pause on
occasion.
WARNING:
If you disconnect the Transmitter (DownHole Tool) before

quitting this screen normally, you will leave the data Auto-
acquisition (DiAA) mode “ON” in the DownHole Tool, which
will consume battery power. Power must be removed from the
DownHole Tool processor to reset the processor and turn the
Auto-Acquisition (DiAA) mode “Off”.
6
Zero the Gravity Toolface Angle (gTFA): This option will automatically
set the gTFA value in the DownHole Tool to the value of 0° (zero
degrees), by adding the correction measured relative to the current
position of the Survey Electronics Module.
Pressing Enter will activate the procedure and follow the instructions or
press Enter again.
7
Allow the system to perform the task. This procedure will take several
updates before displaying the result. BE PATIENT. Note: the value of
the Instrumentation Mounting Offset (IMO), does not have to be zero to
perform the procedure. The system will automatically correct for any
value previously set in the DownHole Tool.
WARNING:
The operator should insure that the complete MWD tool is
assembled (all connections must be made up to the proper
torque) and ready to be run downhole. Insure that the
orientation key slot is in a straight up position. (The use of a
small carpenter’s level laid across the keyway slot will
determine a precise high side position.)
The system determines the manufactured ‘Normal’ gravity toolface of the

instrument. Then it calculates the offset of that position, in relation to the
position of the Gravity Toolface of the tool with the key-slot up. It then
assigns that value as the internal correction to all subsequent Toolface
readings. This correction value is then transmitted to the DownHole Tool
and stored in the MPTx (Node 20). Within the next few screen updates,
you should see the gTFA value change to 0°. The Instrumentation
Mounting Offset (IMO) now reflects the calculated offset of the
DownHole Tool to the key-slot of the pulser. Do Not disconnect the
programming cable from the tool until you have exited this program,
otherwise the DiAA switch will remain in the “ON” position and keep the
sensors powered. The batteries must then be disconnected from the tool to
reset the processor.
8
Edit the Instrumentation Mounting Offset (IMO): This switch allows
the operator to manually set the IMO value to any setting from 0° - 360°.
This option is available to allow the operator to set the internal correction
(IMO) of the tool to 0° (zero degrees) prior to running the MWD Roll
program.
Double click on the highlighted option, ‘Edit the Instrumentation

Mounting Offset’, and enter the desired IMO value and press Enter.
9
Set the Drill Assembly Offset (DAO): This switch allows the operator to
manually set the DAO value in the Surface Receiver. This value will be
displayed on the Compass Rose (Screen 0) in the qMWD_PC program,
used to monitor the transmitted data. For the clients using an orienting
mule shoe device, (UBHO), this value should be set and left at 0° (zero).
Please note any value other than 0.000° will result in the value of the DAO
in the qMWD program being displayed in the warning color yellow.
If the tool has already been programmed and the IMO calculated and set,
and the tool is properly disconnected from the system, then the operator
will get the warning window indicating that the system could not connect
to the DownHole Tool. This is normal and should be expected. Press
Ignore and continue.
The following window will be displayed, indicating that the system is now
communicating with the Driller’s Remote Terminal (Node 05). Press
Enter or double click on the highlight and continue.
The following screen will be displayed, that will allow the operator to
enter the proper Driller’s Assembly Offset (DAO).
10
In the example provided, the value of 90° was entered into the previous
window and entered. The following window will be displayed indicating
the value of the DAO stored into the Driller’s Remote Terminal (Node
05). Double click on the Close button and the system will exit the
program.
11
Toolface Offset Procedure READ!
1: With the tool assembled, to contain at least the survey electronics
module and the pulser module, connect the programming cable to
the programming plug and connect to the uphole end of the MWD
tool. Set the tool on V-blocks in a near horizontal position and
orient the muleshoe key slot so it faces UP.
2: Double click on the TFO Procedure Icon to start the Tool Face
Offset Procedure.
3: With both the downhole tool and the remote terminal connected to
the system, the program should quickly address both systems. If
either of the two modules is not connected, the routine will look
for the absent node and then enter into the routine with a warning
screen. The Warning Screen will identify which of the systems it
could not locate and ask the operator if he would like to Abort,
Retry or Ignore. Depending on which routine the operator wishes
to follow, select the appropriate option.
4: If the operator wishes to ‘Zero the Gravity Toolface Angle’, once

the tool is located, then the operator can select the appropriate
option and continue to the screen that will allow this procedure.
5: DOUBLE CHECK TO INSURE THAT THE KEYWAY IS

LOCATED IN THE UP POSITION. This procedure is performed
specifically in the DownHole Tool (Node 20). Select the first
command to Zero the Gravity Toolface Angle. Notice the number
in the second line, Gravity Toolface Angle, which is below the
update line, will change to zero. Simultaneously, the value of the
Instrumentation Mounting Offset will be changed from its previous
value to the previous value of the Gravity Toolface Angle. Also,
that the value of that space will be added to the Total Toolface
Correction.
At this point, if the operator knows the DAO (Driller’s Assembly Offset),
then enter this value into the system. The DAO value maps to the surface
gears Remote Terminal.
6: Quit this routine. IT IS IMPORTANT TO QUIT THE ROUTINE

BEFORE DISCONNECTING THE PROGRAMMING CABLE.
OTHERWISE, THE DiAA LABEL WILL REMAIN ON AND
THE TOOL SENSORS WILL WORK CONTINUOUSLY. If the
batteries are connected to the tool and the connection is broken
before quitting the routine, the batteries will have to be
12
disconnected from the electronics to reset the tool. All corrections
and configuration files will remain stored in the processor, but the
TFO correction routine should be run again if any connections are
broken and/or re-torqued. The offset may be different.
DO NOT MAKE ANY ASSUMPTIONS.
7: Disconnect the programming cable and assemble the spear-point

on the top of the downhole tool.
13
Measuring and Calculating the DAO, (Driller’s Assembly
Offset)
8:When the MWD Collar is torqued to the bent sub/bent housing mud
motor make this measurement with a tape measure:
Looking ⇓ DOWNHOLE, measure the angle

FROM
The SCRIBE LINE of the Mud Motor/Bent

housing/Bent sub
CLOCKWISE TO
the ORIENTATION BOLT of the MWD
Collar.
MWD Orientation
Bolt
Mud Motor Scribe

Line
9. Measure the drill collar circumference with the tape measure.

10. Divide the Offset measurement by the Circumference
Measurement.
11. Multiply the result by 360° and the product is the TFO in degrees.
12. This value should then be recorded in the DAO value of the TFO
Procedure. The DAO value will appear on the screen in the qMWDPC
program routine.
NOTE: For those clients using a UBHO, the DAO should

always set to zero.
14
Measuring the Driller’s Assembly Offset
DOWNHOLE
MWD TOOL
Orientation Bolt
MUD MOTOR Scribe Line
DOWNHOLE
MWD
Orientation Bolt
MUD MOTOR Scribe Line
15
NOTES
16
g GE Power Systems
Tensor MWD
qMWDW32™
Real Time System Interface
TABLE OF CONTENTS
qMWDW32 REAL TIME SYSTEM INTERFACE ............................................................4
BROADCAST UNITS TO SYSTEM. .....................................................................5
GETTING STARTED..............................................................................................6
qBus COMMUNICATIONS...................................................................................7
CONNECT TO THE ARCHIVE DATABASE ..........................................................9

GENERAL............................................................................................................10
Run Description...........................................................................................10
Well Name ...................................................................................................10
API Number. ................................................................................................10
NEW ..................................................................................................................11
SURVEY OPTIONS ...............................................................................................12
SENSOR OFFSETS ...............................................................................................13
TIE-INS...............................................................................................................14
DATA LIMITS ......................................................................................................15
SURVEYS............................................................................................................16
SURVEY DATA CALCULATIONS ............................................................................17
Insert New Survey.......................................................................................19
qMWDPC DISPLAY SCREEN .............................................................................20
SYSTEM SETUP ..................................................................................................21
Depth Tracking ............................................................................................21
SYSTEM COMMANDS ..........................................................................................22
Depth Tracking Controls.............................................................................22
Depth Tracking Mode (DTMo) ...................................................................23
On Bottom Detection Method (OBDM) .....................................................23
In-Slips Hook Load (ISHL) ..........................................................................23
Minimum In-Slips Travel Distance (ISTD).................................................23
Minimum String Weight Threshold (StWt) ..............................................24
Off Bottom Travel Distance (OBTD) ..........................................................24
Minimum String Weight Threshold (StWt) ..............................................24
Minimum Drilling Weight-on-Bit Threshold (MnWB)..............................24
Pipe Length (PLen) ......................................................................................24
Constant Time Rate-of-Penetration Averaging Number (ROPn) ............25
Constant Distance Rate-of-Penetration Averaging Number (ROPd) ......25
Pump Displacement Factors 1 and 2.........................................................25
Off-Bottom Hook Load (OBHL) ..................................................................25
BASIC RECEIVER CONTROLS ...........................................................................26
Receive Delay Time ("RxDT").....................................................................26
Synch Timing Window Factor ("SyWF")...................................................27
Pumps-On Threshold ("PmpT") .................................................................27
Pulse Amplitude Limits ("LoPL" and "HiPL") ............................................27
Driller’s Remote Serial Number.................................................................27
Set System Time .........................................................................................28
Printing Controls .........................................................................................28
TFA Print Timestamp ..................................................................................29
Section 04
Version 02.00; February 2002; qMWDPCW32
2
TIME ONLY: EACH LINE IS PRECEDED BY "TFA’S AT HH: MM:SS = " .. 29
DATE,TIME: .................................................................................................... 29
MINIMUM: .................................................................................................... 29
PRINTED TOOLFACES PER LINE ...................................................................... 29
AUTO PRINT SURVEY DATA ............................................................................ 29

Survey Data Filter ....................................................................................... 29
TELEMETRY DATA MONITOR WINDOW......................................................... 31
Telemetry Data............................................................................................ 36
Gravity.......................................................................................................... 37
DAO .............................................................................................................. 37
Depth Tracking Data ................................................................................... 37
TELEMETRY DATA WINDOW SETUP 39
Telemetry Monitor Setup ........................................................................... 39
Toolface Display Offset .............................................................................. 39
New Toolface Data Outside ....................................................................... 40
Toolface Display Scale ............................................................................... 40
Telemetry Monitor Window Colors........................................................... 40
Alarm Settings............................................................................................. 41
PULSE WAVEFORM DATA WINDOW 43
Browsing Pulse Waveform Display........................................................... 44
TELEMETRY DATA WORDS 45
Data Word Setup......................................................................................... 47
Survey Sensor Bit Depth Offset................................................................. 49
Manually Set Survey Depth ....................................................................... 51
Survey Data Blocks Setup.......................................................................... 51
PULSE DATA BUFFER WINDOW 52
Pulse Data Buffer Features......................................................................... 53
Browsing ..................................................................................................... 54
Pulse Data Buffer Setup ............................................................................. 55
Pulse Data Buffer Log File .......................................................................... 55
GAMMA DATA 56
Gamma Data Setup .................................................................................... 57
Gamma Data Log File ................................................................................. 57
Logging On/Off............................................................................................ 58
Log Status Window .................................................................................... 60
Disk Evaluation Period................................................................................ 61
DEPTH TRACKING DATA WINDOW 62
Depth Tracking Setup ................................................................................. 63
Depth Tracking Commands ....................................................................... 64
Set OBHL...................................................................................................... 65
Set Depth or Change Depth ....................................................................... 66
Set-Up Depth Tracking ............................................................................... 68
First Method ................................................................................................ 68
Second Method........................................................................................... 68
Section 04
3
TENSOR W32 Real Time System Interface
Welcome to the WIN95 version of TENSOR MWD software, called TENSOR
W32 Real Time System Interface. The DOS version will no longer be
supported for upgrades or changes to accommodate clients who wish to stay
with that particular version. Clients are urged to operate under the WIN95
version, TENSORW32, since all PC’s being marketed are Pentium processors
containing the WIN95 / WIN98 / WIN2000 or Windows NT platforms. This new
system has been designed to accommodate and operate under Win98 and
Windows NT.
Operators shall be required to have a complete working

knowledge of whichever Windows platform is being used, to
be able to operate the program properly in the qMWD
software routines.
With the inception of the TENSORW32 software, problems previously

encountered with running a DOS system under a Windows platform, or
problems with PC compatibility, will be eliminated. The new TENSORW32
operating system requires the use of a system interface or gateway node
device (qNIC) to facilitate the communication functions between the PC and the
qMIX™ protocol. The absence of the interface results in the software
becoming inoperative.
No PC containing the TENSORW32 software will be able to communicate with

the TENSOR MWD system using the old qBus cables. However, the
remaining DOS routines will require the use of the qBus cables to communicate
with the system. Each system should continue to keep an original qBus
(RS232) cable. The programs are currently being rewritten to operate in the
Windows environments.
The qMWDW32 software has been designed to operate with a storage option
for retaining data in an Archive Database in the Access *.mdb form. This file
was created to store formation, depth and survey data for use in LogView, but
can be used for storage of data for survey calculation purposes.
Section 04
4
ATTENTION!!
PRIOR TO STARTING
Real Time System Interface™

Tensor MWD Software
INSURE THAT THE
VARIABLE UNITS DEFINITION UTILITY™

Tensor MWD Software
PROGRAM IS RUN.
SELECT THE PROPER UNITS FOR THE WELL LOCATION AND

BROADCAST TO THE SYSTEM.
REFER TO SECTION 01 FOR VUDU™ INSTRUCTIONS
Section 04
5
Getting Started
qMWD_PC
Double-click on the qMWD_PC Icon on the desktop and the Title Page
will display on the screen.
Click on the ‘Continue’ button or press Enter ↵.
Section 04
6
qBus Communications
Should the qBus network not be communicating, the following dialog box will
be displayed. Selecting No will allow the program to continue to start without
being connected to the qBus system. Selecting Yes will cause the qServer to
attempt another connection with the Remote Terminal.
If all of the connections are continuous and communications are established,

then the following dialog will be displayed if the DRT is powered and the time
does not agree with the time of the PC. Check the PC for the correct time and
adjust it to match the local time zone of the operation, and then set the MWD
system to the PC time.
Selecting Yes will transmit the PC time to the MPRx processor (Node 05).
When the power to the MPRx be interrupted at anytime during the operation
and restarted, this dialog will be displayed. Selecting Yes will resynchronize
the DRT with the PC.
Section 04
7
The following reminder will be displayed to insure that the operator will
remember to create or connect to an Archive Database if data is being
stored to the database file. Click OK to continue through the program start
and set up the parameters of the Archive Database or restart logging to the
database.
Prior to connecting to and setting up the Archive Database, insure that the
depth settings – Measured Depth and Bit Depth – are set to values that will
not adversely affect the LogView data. For instance, if the bottom of the
well is a casing shoe, then input the casing depth or the top of the cement
as the measured depth and the bit depth at some value shallower. This
will prevent erroneous shallow depths from being stored into the Archive
Database. Calibrate all of the sensors in use, such as the Depth Encoder,
by checking the HPsf, to insure it is at a reasonable value. Calibrate the
hookload sensor, so that it will allow the system to make connections.
To prevent any power outages to the DRT during operation, every

operator is advised to obtain and maintain a high quality Un-interruptible
Power Supply (UPS) system. This not only insures continuous power to
the DRT, but also provides clean power to the system.
Section 04
8
Connect to the Archive Database
Select File from the drag down menu and select Database ► Select
Database.
This will place you into the following dialog box:
Select Connect to select a database. The operator will be guided through

Windows routine to select a database previously used. If the database
should require updating or editing then get into the Edit Job Settings to
change runs, or edit other parameters in the Archive Database.
Section 04
9
General
Required Data Entries are the Run Description, Well Name, and the
API Number. These three items must be entered accurately because they
cannot be edited after the Archive Database is created. Insure that the data
is accurate. Any sort of job identification number can be inserted into the
API number slot, if there is no API number available.
Run Description – this value can be used to describe the run

environment, such as Kickoff, Angle Build, Tangent, Angle Drop,
Sidetrack or such. This will aid in the description of the particular type of
BHA being used.
Well Name – this entry should be an exact name of the well as officially
denoted on all well site communication.
API Number – this entry should be the API number designated. In other
areas, such as Canada, it will be a number such as the Land Section
Description or LSD.
In essence, any character entered into these spaces will suffice, but for
accuracy, it should be entered with the correct name and or value.
Section 04
10
New
The instructions “Press New to start a new Run’, indicate that this button
must be selected when a new run is begun. A Run is described as anytime
an MWD tool is tripped into the hole below the rotary table. This can be
the first time it is run into the hole for Run 1. When the MWD tool is
subsequently tripped out of the hole, which would be then end of Run 1.
Regardless of the reason for tripping the tool out of the hole, should it be
for a bit change, BHA change, or MWD failure, the particular run is
complete and a New Run should be selected. The program will
automatically enumerate the runs in sequential order. The reason for this
is there is a high probability that the BHA may change and therefore the
Sensor Offsets may differ from the previous run. When LogView is used
to plot formation evaluation data, the offsets are used to calculate sensor
depths on a run-by-run basis. Therefore, it is essential that the Archive
Database be created to match the MWD runs. The sensor-offset data is
not a time sensitive entry; it is a run sensitive data entry.
The data from the previous Run will be copied into the New Run screens
and can be edited at any time. Note that the Tie-In survey data is the last
accepted survey in the survey file. It can be edited to contain any survey
data that the operator requires, but by default, it will select the last
accepted survey of the previous run.
GO TO ‘Survey Options’ on the TAB SELECTIONS at the top of the

box.
Section 04
11
Survey Options
Currently there are only two selections for survey calculation types. The
two options provided, Average Angle and Minimum Curvature are the
most commonly used and should give the most options.
GO TO ‘Sensor Offsets’ on the TAB SELECTIONS at the top of the

box.
Section 04
12
Sensor Offsets
Enter the correct sensor offset values for the Survey sensor and the
Gamma sensor. The above example is in feet. The values should be
entered in with a positive (+) value. Refer to Variable Units Definition
Utility.
GO TO ‘Tie-Ins’ on the TAB SELECTIONS at the top of the box.
Section 04
13
Tie-Ins
This data is very important and MUST be entered correctly! For Run 1,
this is the last survey from the survey record of any hole drilled prior to
the MWD being utilized on the well. In other words, this survey is the last
recorded survey ABOVE (Shallower Than) the next expected MWD
survey measured.
Note: On the start of a New Run, the data from the last accepted survey
will be used for the Tie-In. That Tie-In data for the next run can be edited
should the operator require a survey other than the last MWD measured
survey. Please note that accuracy is most important.
Section 04
14
Data Limits
Data Limits can be accessed from the Setup label in the drag down menu.
Select Data Limits and carefully select the following limits.
Depth Update Interval

This limiter will prevent a depth record from being created unless the
depth has increased by whatever limit is selected. The above limit
example is in feet.
Limit Depth
This limiter will prevent erroneous depths that may be entered from being
stored to the database.
Limit Gamma
This will prevent any erroneous gamma values, which may result from a
miss-decode, being stored to the database. It is very similar to the Wild
Data filter in LogView. The data will still be in the file, but it will be
marked ‘bad’.
Note that these options can be activated or deactivated at the operator’s

discretion. They will be grayed out if they are de-activated.
Section 04
15
Surveys
Surveys are now capable of being stored into the Archive Database.
When the archive database is connected and logging to the database is on,
then all measured surveys will be stored in the Survey File in the Archive
Database.
The above dialog box will be displayed after the transmission of the
survey is complete, prompting the operator to accept or reject the survey
data. The depth of the survey is displayed, but cannot be changed in this
dialog box. Regardless if the survey data is accepted or rejected, the
survey will be stored in the survey file. The operator has the option to
review the survey file and make amendments to the data at his discretion.
Survey integrity is of utmost importance, so operators are advised to
adhere to the highest standards when editing survey data.
Section 04
16
Survey Data Calculations
Survey Data Calculations are accessible from the File menu. This display
is intended to allow the operator near real-time viewing and unlimited
editing of survey data and calculation results, without having the need for
a secondary survey calculation routine.
Operators may view the survey data, edit the survey depth, mark a bad
shot, force a new survey calculation based on previous edits, and print the
Survey Data table.
Any new additions or insertions will automatically be recalculated. If a

previously accepted survey is marked ‘bad’, then a recalculation occurs
and the data is re-presented.
The following parameters are presented to the operator:
Bad – This is an editable field. When checked by the operator it marks

that particular survey as a bad shot, and it is not used in the survey
calculations. The condition of Bad can be reversed at any time the
operator desires.
Survey Depth – The depth at which the survey was taken. This includes
any sensor depth offsets defined by the operator. This is an editable field
in the survey display.
Section 04
17
Inclination – This is the measured angle of deviation of the well bore
from the vertical. This is an editable field in the survey display.
Azimuth – The direction of a course measured in a clockwise direction

from North = 0° to 360°. This is an editable field in the survey display.
TVD - The vertical depth of a deviated well bore calculated from the
surface elevation. This is an editable field in the survey display.
Dogleg Severity – The rate at which the well is changing orientation. If

the length units are in feet, the rate is in degrees per 100 feet (°/100 ft.). If
length units are meters, the rate is in degrees per 30 meters (°/m).
North Coordinate – The total horizontal displacement with respect to a

specified tie-in in the north direction. A negative number denotes a
Southerly displacement.
East Coordinate – The total horizontal displacement with respect to some

specified tie-in in the east direction. A negative number denotes a
Westerly displacement.
Vertical Section – The projections of the well bore into a vertical plane,
parallel to a specified azimuth (vertical section azimuth) and scaled to the
True Vertical Depth. It is calculated with respect to a specified origin.
Survey Source – This column designates the type of survey source. If the
data – Measured Depth, Inclination, and Azimuth – are measured by the
MWD and not altered, then it is designated as MWD. Any alterations to
the data will change the designation to User to indicate a change was made
to the original data.
Run – This column indicates which run the survey data was recorded
during which run.
Survey Time – This column records a time stamp indicating the time and
date that the survey was registered.
Section 04
18
Calculate TVD from MD Option
An operator can convert any measured depth value in the course of the
well to a True Vertical Depth value using the Convert MD to TVD option.
By entering the desired Measured Depth and clicking on Convert, a True

Vertical Depth will be calculated and visa versa.
Insert New Survey
An operator can insert a new or corrected survey into the file at any
selected depth. The operator is allowed to enter a new Measured Depth,
Inclination, and Azimuth. Selecting OK will insert the survey at the
appropriate position and recalculate the data, including the new survey.
The Set TVD will allow the operator to insert a TVD value at this point, if
the survey is measured and calculated from another source.
Section 04
19
qMWD_PC Display Screen
Behind the Set System Time will be the qMWD_PC display screen. Note:
Upon loading the software for the first time, the windows will be
displayed in WindowsXX cascade mode. The operator must select and
size the desired windows to display the required data for the job. The
following display is only a recommendation. The system is operating in
the multi-tasking WindowsXX platform that allows the operator to select
individual screens for display and define the sizes desired.
As mentioned before, this display is only a suggested option. Each

individual screen will be described and the options discussed in the
following pages.
Section 04
20
System Setup
The System setup parameters affect the general operation of the entire
qMWD/PC software package. The qMWD_PC program saves all setup
changes to the registry upon exit.
The following selections are available:
Depth Tracking
Depth Tracking Check Box
This check box is intended to indicate that the qMWD_PC program is

aware that it is attached to a qMWD system that has depth tracking
enabled. This is not 'check-able' by the operator - the program queries the
system at startup. To change the status of this box the operator must
access Depth Tracking Controls through the System Setup window and
select the appropriate choice for Depth Tracking Mode
Standard Pipe Length
This value specifies a standard length in feet for adjusting the Current Bit
Depth value by selecting the 'Add/Subtract Standard Pipe Length' buttons.
Section 04
21
Depth Prompt Mode
When the ‘Flow off’ option is selected – the program will prompt the
operator for depth, when the pumps have been turned off. The ‘Flow on’
option is simply the reverse - the operator is prompted for depth when the
pumps are turned on. ‘Disable’ eliminates all automatic depth prompting.
System Commands
Depth Tracking Controls
Allows viewing, editing, and uploading/downloading of the following

control variables specific to Depth Tracking:
Section 04
22
Depth Tracking Mode (DTMo)
This option allows the operator to select either the Manual or Automatic
mode of Depth Tracking, or to disable it altogether. "Manual" depth
tracking requires the use of the "Bttm!" and "Slps!" commands to effect
control of depth tracking. "Automatic" depth tracking does what it sounds
like - enables automatic depth tracking. This mode also allows limited use
of "Bttm!" and "Slps!" commands.
On Bottom Detection Method (OBDM)
Defines the method used for determining On Bottom conditions after

coming out of slips.
Hook Load Based: This method determines an On Bottom

condition when the Weight On Bit (WOBs) parameter reaches 30
percent of the Minimum Weight On Bit (MnWB). This method is
effective with vertical wells running a high weight on bit (i.e. 20+
Kips). Do not use in deviated well bores.
Depth Based: This method determines On Bottom condition when

the Bit Depth (BDep) data variable becomes equal to the Measured
Depth (MDep). This method is more effective for low weight on
bit conditions and horizontal wells.
In-Slips Hook Load (ISHL)
In-Slips Hook Load Threshold defines the hook load weight threshold for
switching from the "Out-of-Slips" state to the "In-Slips" state. Once in
drilling mode, (after touching bottom) this threshold is only applicable if
the bit is at least Minimum In-Slips Travel Distance from the bottom. See
also Minimum String Weight.
Minimum In-Slips Travel Distance (ISTD)
This parameter defines the minimum amount of hook travel required to

return the string to the slips as measured from the bottom of the hole. This
is used to prevent the system from inadvertently entering the "In-Slips"
state when the measured hook load value is low due to light drill string
weights or horizontal drilling.
Section 04
23
Minimum String Weight Threshold (StWt)
This parameter defines the hook load weight threshold for switching from
the "In-Slips" state to the "Out-of-Slips" state. There should be enough
difference between the Minimum String Weight value and the In-Slips
Hook Load Threshold to prevent system oscillation between the "In-Slips"
and "Out-of-Slips" states.
Off Bottom Travel Distance (OBTD)
Defines the maximum allowable divergence of Bit Depth (BDep) from

Measured Depth (MDep) before an Off Bottom condition is detected after
initial On Bottom conditions are satisfied.
Minimum String Weight Threshold (StWt)
This parameter defines the hook load weight threshold for switching from
the "In-Slips" state to the "Out-of-Slips" state. There should be enough
difference between the Minimum String Weight value and the In-Slips
Hook Load Threshold to prevent system oscillation between the "In-Slips"
and "Out-of-Slips" states.
Minimum Drilling Weight-on-Bit Threshold (MnWB)
Minimum Drilling Weight-on-Bit Threshold is used to determine On-

Bottom and Off-Bottom conditions if the On Bottom Detection Method
parameter is set to "Hook Load Based". After coming out of the slips, the
first On-Bottom condition establishes the bit depth when the Weight-on-
Bit data parameter (WOBs) reaches 30 percent of the specified MnWB
value. Subsequent "Off-Bottom" conditions are reported if the bit depth
has diverged from the depth of the hole and the indicated WOBs value
drops below 30 percent of the MnWB value.
Pipe Length (PLen)
When an "On-Bottom" condition is detected for the first time, after

coming out of the slips, the Hook Position is forced to the operator
specified PLen value. This is done by setting the internal Geolograph
Wheel counter to a count that is equivalent to the PLen value.
Depth Tracking Data Update Time (DTUT)
This variable defines the time between updates from the receiver for
Depth Tracking Data.
Section 04
24
Constant Time Rate-of-Penetration Averaging Number (ROPn)
Constant Time Measured Rate-of-Penetration is determined by measuring

the change in Measured Depth (MDep) over a fixed time-period specified
by ROPn. This ROPn number does not affect the update period, which is
fixed at 0.1 second.
Constant Distance Rate-of-Penetration Averaging Number (ROPd)
Constant Distance Measured Rate-of-Penetration is determined by

measuring the time to penetrate a specified, but otherwise fixed, length of
Measured Depth (MDep).
Pump Displacement Factors 1 and 2
The Pump Displacement Factors define the mudflow rate per stroke and
are used to derive the data values. 1. GPM1 = (pump 1 gallons per
minute). 2. GPM2 = (pump 2 gallons per minute). 3. GPM = (GPM1 +
GPM2). The values for GPM1 and GPM2 and GPM are derived from the
values measured by SPM1 (pump 1 strokes per minute) and SPM2 (pump
2 strokes per minute).
Off-Bottom Hook Load (OBHL)
Off-Bottom Hook Load is used to automatically establish an "On-Bottom"

condition and to compute Weight-on-Bit. If the Depth Tracking Mode
(DTMo) is in "Manual" mode, then the operator must enter this value
manually. If DTMo is in "Automatic" mode, then OBHL is automatically
established within the first several seconds after coming out of slips. The
algorithm assumes that at least 20 seconds is available before hook motion
begins to indicate travel back to the bottom. During this period, it is
assumed that slips are removed from the rig floor and pumps are turned on
and stabilized for flow.
Section 04
25
Basic Receiver Controls
Selecting this option allows the operator to view and change certain
control parameters in the receiver. The parameters displayed include:
· Receive Delay Time

· Synch Timing Window Factor
· Pumps-On Threshold
· Low Pulse Amplitude Limit
· High Pulse Amplitude Limit
These control parameters are downloaded from the surface receiver when
this option is selected.
Receive Delay Time ("RxDT")
The receiver delay time control specifies the delay required from
pumps/flow on detection until the receiver will attempt detecting signals.
This delay should be set long enough to allow the standpipe pressure to
stabilize. The value should be at least 5 to 10 seconds less than the
transmit delay time "TxDT”. Refer to Section 01 in qMWDCnfg.
If the receive delay time is short in comparison to the downlink time

period "DLTP" and a downlink command interpretation is pending, the
receive time delay is automatically and appropriately extended.
Section 04
26
Synch Timing Window Factor ("SyWF")
The synch window is a period of time, relative to when the "RxDT" period
expired, that defines when the receiver will indicate that it has missed
synch, if a synch word has not been detected.
The length of a synch word, in time, is a function of the pulse width and
number of singlewide pulse symbols in the word. The synch window
factor defines the window period as a multiple of synch word periods. In
computing the synch window period, the receiver compensates for all
detection latencies and the value of TxDT-RxDT.
A value of zero (0) indicates an infinite synch window (as long as pumps
are on).
Pumps-On Threshold ("PmpT")
This variable defines the input pressure value at and above which pumps
are to be considered on.
Ideally, the set point would correspond to the pressure at a flow rate,
which also causes the downhole tool flow sensing mechanism to switch.
This will minimize any timing discrepancies between the transmitter and
receiver relative to synch transmission and detection.
Pulse Amplitude Limits ("LoPL" and "HiPL")
These values specify the acceptable, inclusive range of pulse amplitudes.

Pulses detected outside of the defined range will not be reported or
processed. The ratio of HiPL: LoPL should not exceed 10:1. Note: this is
not a hard rule, since the ratio can be exceeded by a 20% margin, without
affecting the decoding characteristics. Normally, these values are set
based on the pulser characteristics and would normally not require field
modification, but in some circumstances, the system needs adjustment to
avoid adverse noise conditions.
Driller’s Remote Serial Number
This is the serial number of the Surface Receiver. It is not editable, and is
for reference only.
Section 04
27
Set System Time
Selecting this item sets the qMWD 'Time' variable to the current time of
the PC clock. The 'Time' is then also broadcast over the qBus to all
modules.
This action is identical to selecting "Yes" for the "Set System Time"
dialog box that appears when starting the program.
Printing Controls
Number of Characters in Print Line (Printer Page Columns)
The operator may specify the number of columns per page for text
printouts.
Print Toolface Angles
When set to "On", Toolface Angles are printed in real time as they are
received from the Surface Receiver. The number of Toolface Angles per
printed line is set by Printed Toolfaces Per Line. When pumps are turned
"Off", any TFA's that have been received, but not printed, are printed.
Section 04
28
TFA Print Timestamp
This specifies the type of timestamp that starts each line of the printed
Toolface Angles. Options are:
TIME ONLY: each line is preceded by "TFA’s at hh:mm:ss = "
DATE, TIME: each line is preceded by "TFA's at dd-mmm-

yy, hh:mm:ss = "
MINIMUM: each line is preceded by "TF@hh:mm "
Printed Toolfaces Per Line
This specifies the number of Toolfaces per line to be printed. Up to ten

(10) TFA’s may be printed on a line. It is important to note that
qMWD_PC will only print those TFA’s for which there is room. If, for
some reason, there is only enough room for 'Toolfaces Per Line'-1 TFA’s,
then the last TFA will be printed on the next line.
Auto Print Survey Data
This switch, when checked, enables formatted printing of all telemetered

survey variables that were successfully decoded by the surface receiver.
Each survey printout will contain a header that includes survey time, date,
and depth.
Survey Data Filter
This switch, when set to ALL in conjunction with the variable Auto Print
Survey Data will enable printing of all telemetered and derived survey
data variables.
When set to "Telemetered ONLY", only telemetered variables are printed

in the survey printout. Variables derived from "raw" sensor values are not
printed.
Hook Position Scale Factor (HPsf)
Hook Position Scale Factor is used to convert the Depth Encoder Wheel
sensor output counts to distance. The Depth Encoder wheel typically
sends two signals (four edges) per revolution. This parameter is hardware
dependent and MUST be set accordingly.
Section 04
29
Event Logging
This parameter has been moved to qTalk, and is accessible by invoking

Alt-L. The event log is named “MWDEvent.Log”, and it resides in the
root directory of the current disk drive. Note that this file is common to all
qMWD/W32 programs. It is perfectly acceptable to have more than one
program writing events - different programs will not overwrite events
from other programs. The format of an event file record is as follows:
program ddmmmyy hh:mm:ss - event string
Events may contain multiple lines. Extra lines are indented.
Section 04
30
Telemetry Data Monitor Window
The Telemetry Data Window is a combination of two separate window

‘panes’. These panes can be adjusted to the operators preferred settings
for appropriate display. Other added features of the Telemetry Data
Window are discussed below.
Section 04
31
Telemetry Data Monitor Window Features
The Telemetry Data Monitor window contains all of the familiar
features of the previous software versions and many new enhanced
features because of the Windows™ operating platform. The
features are described below and all operators are encouraged to
read this section and take advantage of the features as they pertain
to their job applications.
Telemetry Data Target Rose
The Target Rose display gives the operator a numerical and

graphical display of the inclination, azimuth, and toolface angles
with time-stamps to indicate when the data was sent.
Inclination
The inclination numerical value is displayed in the lower left-

hand corner of the display and can be color coded with the
graphical display or displayed in black.
Azimuth
The azimuth numerical value is displayed in the lower right-

hand corner of the display and can be color-coded with the
graphical display or displayed in black.
ToolFace
The toolface numerical value is displayed in the middle of

the target rose. It can also be color coded with the graphical
display or displayed in black. One unique feature of the
toolface display is that the Magnetic Toolface angles are
always displayed in red. The Gravity Toolface angles are
displayed in the default colors or operator selected colors. It
is advisable that the color red not be chosen for the standard
color, since the system uses red for the Magnetic Toolface
angle. Another option featured in the Toolface Display
Setup is the option to have the scale change automatically to
display a magnetic toolface angle or a gravity toolface angle.
Section 04
32
Pump State
The Pump State indicates ON or OFF depending whether or not the

Pump PSI is above or below the pump on/off threshold and has
satisfied the Pump Evaluation Time (PevT).
Down Time
Down Time indicates the amount of time since the Pump PSI
was below the pump on/off threshold listed in HH:MM:SS
format.
Up Time
Up Time indicates the amount of time since the Pump PSI

was above the pump on/off threshold listed in HH:MM:SS
format.
Pump PSI
This label indicates the pressure on the standpipe,

measured by the transducer in pounds per square inch.
Telemetry Status
The telemetry status states the position of the processor in

the decoding process.
Pumps On, Synch Delay – This is the position of the

processor immediately after the Pump PSI exceeds the
Pumps on/off threshold and the PevT variable has been
satisfied.
Pumps On, Expect Sync – This is the position of the

processor immediately after the Receiver Delay Time
(RxDT) variable is satisfied. The processor will stay in this
position until it detects an Alert Pulse and the required
number of synch pulses.
Expect Survey Header – This is the position of the

processor immediately after the processor has established
synchronization with the tool pulse routine.
Section 04
33
Expect Survey Data – This is the position of the processor
immediately after the processor has successfully detected
and decoded the survey header sequence.
Section 04
34
Expect T/L Header – This is the position of the processor
immediately after decoding the survey sequence in
preparation to receive toolface/-logging data. This heading
is displayed in the event the downhole probe does not have
a stored survey to transmit and the probe transmits a T/L
Header pulse, instead.
Expect T/L Data – This is the status of the processor

immediately after successfully decoding the toolface/logging
header and until a pump off event is detected.
Pumps Off – this is the position of the processor immediately

after detecting a pumps off event.
Quality
The Quality is a percent (%) value calculated by an algorithm that

will compare the arrival position of the pulses, of a completely
transmitted word, to the expected position of the pulses. This is all
based upon the timing sequence established by the synch pulses.
Confidence
Confidence is a percentage (%) value indicating that extraneous

pulses created by drilling noise were detected and analyzed as
possible data pulses. Consequently, the word decoded may be in
error and will require analysis by the operator. The operator should
check the Low Pulse Level (LoPL) to insure that it is above any
drilling noise being detected by the transducer at the standpipe. If
this does not solve the problem, the operator should consider
changing the Pulse Width (PwN) to one that will remove the pulse
train from the frequency of the noise being encountered. Refer to ¶
2.4.5.2 of the qMWD Engineer’s Reference Manual Volume 1 for a
detailed explanation of the Confidence Levels.
Note: If the Surface system locks onto a false synch routine, both
the Quality and the Confidence will degrade rapidly and no data will
be displayed.
Section 04
35
% Decode
Percent Decode is a routine that calculates the percentage of

words decoded compared to the number of words transmitted.
Please note that decoded words with low confidence values will be
included as decoded words.
Pulse Amplitude
Pulse Amplitude is the calculated value of a pulse above the mean

PSI base line as determined by the surface receive processor. The
displayed pulse value is highly filtered. Therefore, it may not
accurately indicate the perceived pulse height on the standpipe
pressure gauge.
Telemetry Data
The Telemetry Data are the values of the specific words transmitted
by the downhole probe. No value for the variables will be displayed
if the specific word is not entered into the Survey Sequence or the
T/L Sequence. These values are considered survey quality words
and support the accuracy of the measured survey.
Dip Angle
This position displays the Dip Angle in degrees transmitted by the

downhole probe.
Mag Field
Displays the Total Magnetic Field transmitted by the downhole

probe.
Temperature
This variable displays the Tool Temperature in °C, transmitted by

the downhole probe. Refer to the Variable Units Display Utility to
change the display to °F.
Battery
The Battery voltage is displayed in VDC, transmitted by the

downhole probe.
Section 04
36
Gravity
The Total Gravity value or warning as transmitted by the downhole

probe is displayed.
DAO
Displays the Driller’s Assembly Offset in angle degrees, as stored

in the Surface Receiver processor. Any value other than 0.000 will
be displayed in the color yellow. Otherwise, the value is displayed
in the color black.
Depth Tracking Data
This is an abbreviated display of the Depth Tracking Data window

available to the operator. It can display the following data values.
Mode
The data displayed is dependent upon the mode of operation

selected. If depth tracking is disabled, a state of Off will be
displayed. If Manual depth tracking is enabled, all of the variables
available will be displayed. This state requires manual activation of
the In-Slips and On-bottom commands. If Automatic depth tracking
is enabled, all of the variables available will be displayed. This
state requires no manipulation of the commands following the
calibration of the system.
Bit Depth
In the Automatic depth-tracking mode, the system will actively track

the position of the bit.
Measured Depth
In all modes, the measured depth is the depth of the hole.
TVD
When the Archive Database is activated and surveys are measured
and accepted and calculated, then the projected TVD is calculated
and displayed. It is an option that can be toggled on or off using
the drag down menu Depth - Display TVD.
Section 04
37
Hook Load
This variable displays the measured weight of the drill string, minus
the Traveling Block and the Kelly.
WOB
Weight On Bit is calculated from the difference of what the OBHL

value is set to and the hook load. There is an 8K resolution, so
light bit weights will not be too exact.
Hook Position
This variable indicates the position of the Kelly in relation to the drill
floor. It will reset to the Pipe Length (PLen) after a connection is
made or if the On-Bottom command is issued.
ROP
The calculated Rate of Penetration (ROP) is displayed. Refer to

the different ROP calculation results in the Depth Tracking Setup.
ROP Age
This displays the elapsed time in minutes since the last ROP
update. This value will indicate to the operator if an adjustment
should be made in the update times of ROP calculation method.
All of the variables displayed in this window are for convenience

purposes. All of these values are available in other windows should
a more detailed analysis of the data be required.
Section 04
38
Telemetry Data Window Setup
The Telemetry Data Window setup can be accessed two different

ways. Click on the Setup option in the drag-down menu across the
top of the screen. Then select the Telemetry Monitor Setup option
to display the following screen, or right click with the mouse arrow
on the Toolface Display and get the same screen.
Telemetry Monitor Setup
This window appears as an option on the Setup pull-down menu

when the main highlighted window is the Telemetry Monitor.
The setup variables for the Telemetry Monitor window include:
Toolface Display Offset
This value sets an angular offset (rotation) for the toolface data plot.
The plot coordinates and plotted values may be shifted a full 360
degrees, allowing the operator to select a "target" direction for the
top of the dial display. USE THIS OPTION WITH CAUTION AND
GUARD AGAINST UNINTENDED USE.
Section 04
39
New Toolface Data Outside
When set to "On", the newest toolface value is appears on the

outside of the circle plot. When set to "Off", the newest toolface
value appears on the inside of the circle plot. Please note that the
newest toolface value will be a solid color and the historical toolface
values will be a faded shade of the same color.
Toolface Display Scale
The operator may select from the following options for displaying of
toolface values:
➲ 0 to 360
➲ -180 to 180
➲ Automatic switching between 0 to 360 for magnetic

toolface angles and -180 to 180 for gravity toolface
angles.
Telemetry Monitor Window Colors
➲ Compass Rose Color - Color of circular grid rings
➲ Toolface Color - Color of Toolface graphics and text
➲ Inclination Color - Color of Inclination graphics and

text
➲ Azimuth Color - Color of Azimuth graphics and text
For each setup color item on the window, the foreground color of
the specified parameter may be set.
Section 04
40
Alarm Settings
A right button click on the Survey Data Display windowpane will

reveal the options for the Alarm Settings.
Alarm Settings allow the operator to define the tolerances for

the data parameters. Dip Angle, Magnetic Field and Gravity
have an operator defined nominal value, and a tolerance.
As long as the telemetered value of each of these
parameters is within the nominal value, plus or minus the
tolerance, no warning is issued. If it is beyond tolerance,
then the value is printed to the window in red. The High
Temperature Threshold defines the temperature above,
which a warning is issued. Low Battery Voltage defines a
voltage below, which a warning is issued.
With the exception of Low Battery Voltage, all of these

parameters are read in from the Surface Receiver at
runtime. Should qMWD_PC be restarted, the values are
read again from the Receiver (they are not saved).
Section 04
41
These alarm settings are secondary warning features, in
addition to the warning features set in the Site Environment
Settings in the Configuration System Utility. The warnings in
this window are set by a comparison of the total word value
transmitted, with the settings in the window. On the
contrary, the warnings in the Configuration System Utility are
set by a comparison of the words in the tool, prior to
transmission.
Section 04
42
Pulse Waveform Data Window
This window appears as an option on the Window pull-down menu.
It shows a plot of the pressure pulse waveform output from the

matched digital filter in the receiver. Each horizontal bar represents
512 samples of the pressure signal. The data below the pulse
display indicates the Pulse Amplitude in PSI, the Pump Pressure in
PSI, the Pulse Width in seconds, the LoPL and HiPL in PSI and the
Filter Band Width as it relates to the pulse width. The values on the
left side of the window indicate the relative pulse height and the
values on the right side are the date/time stamp of the trailing
pulses displayed. These values can and should be stored to a file
for future reference, should any problems occur on the job.
Right clicking on the Pulse Waveform Data window will bring up a

shortcut menu for access to the Pulse Waveform Data Setup dialog
box.
Section 04
43
Browsing Pulse Waveform Display
Browsing can be enabled by selecting the Browse Log function
from the Log pull-down menu. This is a toggle - to turn off

browsing, again select the Browse Log function from the Log pull-
down menu. When browsing, navigation buttons appear on the
right hand side of the window. Use these buttons to move
throughout the file.
The pulses will always appear the same regardless of the pulse
width. The speed of pulse trace as it progresses across the screen
is the only indication of the pulse rate. The saddle pulse
appearance is the result of a 3X pulse analyzed by a 1X filter, with
X being the PwN.
Section 04
44
Telemetry Data Words
In the active display, it shows the time/date stamp, depth, and value
for each data word decoded by the receiver. The new values
overwrite any previous value of the same variable and a highlight
bar indicates the most recent value received. The character at the
beginning of each line indicates whether the value was received
during survey (S) or logging (L). The time tag appears in hh:mm:ss
ddmmmyy format.
Browsing the Log File
This option appears on the Log Pull-down Menu or by right clicking

on the window. All new values are listed in the order received
indicated by the time tag in a yymmddhhmmss format. Browse will
load the current log file for viewing. The file may be scrolled
through using the cursor keys or mouse movements. Logging is
not disabled when browsing a log.
Section 04
45
Browsing ASCII text data such as Telemetry Data Words, Survey
Data, or Depth Tracking Data is performed by the Browse ASCII
Data feature. To browse ASCII data the ASCII data is loaded into a
scrolling window. Operators may browse by moving the sliders.
This viewer can be used to look at any qMWD_PC generated ASCII
data file, including gamma and resistivity files. To turn off browsing,
click on the 'OK' button at the bottom of the window.
Section 04
46
Data Word Setup
Data Word Log File

This entry allows the operator to view and specify the log file name.
To change the current entry the operator must click on the
“Change” button to bring up a standard file selection dialog box.
Operators are strongly urged to implement a file naming system
that will be a standard for their operations. A system was designed
into the program to assist in creating order in this process;
however, operators can adopt their own methods.
Logging At Startup
When set to "On", logging for Telemetry Data Words will be
automatically enabled at startup. When set to "Off", logging will not
be automatically enabled at startup, but may be turned on using the
Log pull-down menu. If the is set to the ‘On’ setting and the storage
medium is not found for the file named for logging the data, and
error will appear at the startup of the program. This is just an
indicator that the medium is not available and should be remedied
in the course of the program running.
Logging On/Off
When set to “On” logging will be turned on for the specified log file
after exiting the setup window. Similarly when turned “Off” logging
will be turned off upon exiting the setup window. Turning Logging
On/Off may also be done by selecting the appropriate choice from
the “Logging” pull-down menu, or by right clicking on the data
window of interest and selecting “Logging On” or “Logging Off”.

It displays the contents of each completed Survey Block.
The Survey Block consists of the qMWD 'SuSD' variable. It is

solicited from the receiver whenever the Survey Status Register
indicates that a new complete survey has been received.
Note that if the receiver already has a valid survey in memory when
the qMWD/PC program is started, it will be considered as a "new"
Survey Data Block. This means that the same Survey Data Block
may be logged repeatedly if the program is started repeatedly with
no new surveys received.
Section 04
47
The window displays the survey with the SDep variable and all of
the survey received and decoded by the receiver. The SDep
contains the survey-offset value calculated from the BDep at the
time the survey was decoded or BDep was entered before the
system detected synch.
Section 04
48
Survey Data Window

It displays the contents of each completed Survey Block. The
survey block consists of the qMWD SuSD variables. It is solicited
from the receiver whenever the Survey Status Register indicates
that a new complete survey has been received. Note that if the
receiver already has a valid survey in memory when the qMWD/PC
program is started, it will be considered as a new Survey Data
Block. This means that the same Survey Data Block may be
logged repeatedly if the program is started repeatedly with no new
surveys received.
Right clicking on this window will bring up a shortcut menu for

access to the Survey data Setup dialog box.
Section 04
49
Survey Sensor Bit Depth Offset
This denotes the distance between the directional sensors (survey

sensor) and the bit. When setting the Survey Depth in the receiver,
this value is subtracted from the Survey Bit Depth as entered in the
“Set Survey Depth” window before being stored to the receiver.
This offset is applied to data logged to the Survey Data Table of the
LogView database.
NOTE: The Survey Sensor Bit Depth Offset is set in the Edit
Settings in the Archive Database. Changes should not be made in
this dialog box if data is being stored to the Archive Database.
Section 04
50
Manually Set Survey Depth
This option allows the operator to manually set the Survey Depth.
Once set, the next telemetered survey will be depth stamped with
this depth. Note that this Survey Depth denotes the Bit Depth
minus the Survey Sensor Offset at the time the survey is taken.
Survey Data Blocks Setup
Right clicking on this window will bring up a shortcut menu for

access to the Survey Data Setup dialog box.
Survey Data Log File

Logging At Startup
When set to "On", logging for Survey Data will be automatically
enabled at startup. When set to "Off", logging will not be
automatically enabled at startup, but may be turned on using the
Log pull-down menu.
Logging On/Off
window of interest and selecting “Logging On” or “Logging Off.”
Section 04
51
Pulse Data Buffer Window

It shows the current Pulse Data Buffer, with engineering data for
the last received word. Pulse Data Buffers are intended for
engineering diagnostic purposes, but can be useful to the operator.
The operator is advised to record the Pulse Data Buffer records in a
file to assist in post well analysis, if pulse detection was a problem
at anytime during the job.
Section 04
52
Pulse Data Buffer Features
Record Number: Designates record number during

browsing
Time Tag: hh:mm:ss dd mmm ‘yy
Flags: Survey or Toolface Data
Survey Data, Parity Type of data decoded
Quality: Quality of pulse position and detection
Confidence: Confidence in word detection
Previous Average Amp: Amplitude of previous word
Average Pulse Amp: Amplitude of current word
Worded Decoded: Hex Value of current word
Sequence Number: Identifies Survey or T/L Seq. used.
SySR: Synced Identifies whether system is synched.
SuSR: Received Survey Indicates a survey was decoded
TLSR: Received Word Indicates if a T/L word was decoded.
Number of Symbols 3 Number of pulses detected
Num 2-Bit Symbols 0 Number of 2-bit symbols
detected.
Word Number of Bits: 9 Number of bits assigned to word.
2nd Pls. dcd: Refer to P2 bars below. Secondary
pls’s.
Interval Mod’d None
Bad Symbols: None
Average Interval Error: 0.0195
Interval Error Mag: 0.0352
Word Number: 18 Order of word in Sequence
Symbol Mod’d: None
The window allows the operator to identify the position of the

system in the decoding sequence by observing the word number.
This window also indicates the quality and confidence on a per
word basis, instead of over a 10-word average. If drilling or pump
noise is a problem, causing the confidence to deteriorate, then the
operator can study the two pulse bars on the bottom of the screen.
This will help to determine if the noise pulses are large enough to
create doubt in the decoding process. The accepted pulses will be
highlighted in green. At times, depending upon the location of the
noise pulse, the secondary pulse, P2, will be a valid pulse and will
be accepted if it is calculated to be the more correct pulse of the
two appearing in the window.
Section 04
53
Browsing
Browsing can be enabled by selecting the browse log function from

the Log pull-down menu. This is a toggle – to turn off browsing,
again select the Browse Log function from the Log pull-down menu.
When browsing, navigation buttons appear on the right hand side of
the window. Use these buttons to navigate throughout the file.
Section 04
54
Pulse Data Buffer Setup
Right clicking on the Pulse Data Buffers window will bring up a

shortcut menu for access to the Pulse Data Buffer Setup dialog
box.
Pulse Data Buffer Log File
"Change" button to bring up a standard file selection dialog box.
Logging At Startup
When set to "On", logging for Pulse Data Buffers will be

Log pull-down menu.
Logging On/Off
When set to "On" logging will be turned on for the specified log file
after exiting the setup window. Similarly when turned "Off" logging
the "Logging" pull-down menu, or by right clicking on the data
window of interest and selecting "Logging On" or "Logging Off.”
Section 04
55
Gamma Data
This window appears as an option on the Window pull-down menu

and it shows gamma data on a linear plot.
Gamma data may be plotted vs. either time (as shown above) or
depth. When plotting vs. depth the depth scale may be adjusted in
the Gamma Data Setup dialog.
Right clicking on the Gamma Data window will bring up a shortcut

menu for access to the Gamma Data Setup dialog box.
Section 04
56
Gamma Data Setup
The setup variables for the Gamma Data window include:
Gamma Data Log File
Logging At Startup
When set to "On", logging for Gamma Data will be automatically

enabled at startup. When set to "Off", logging will not be
automatically enabled at startup, but may be turned on using the
Log pull-down menu.
Section 04
57
Logging On/Off
Plot Method
When set to “Depth Based” plots Gamma vs. depth. This method is
typically used with the depth tracking system enabled. Only data
points with a corresponding depth that is greater than the previous
points depth will be plotted, although all data will be logged
regardless of depth values. When set to “Time Based” plots
Gamma vs. time. This method is typically used with the depth
tracking system disabled.
Clear Gamma Plot
Clears the gamma data used for plotting from memory and clears
the plot. It must be noted that this does not erase any data log files
should they exist.
Scroll Down When New Data is Received
When checked automatically scrolls down to the bottom of the

window in order to display the latest data point when that data point
is received. The operator may want to uncheck this item if he
wishes to browse earlier plotted data.
Load in Last Data Log File at Startup
When checked, automatically loads, at startup, the last gamma

data file that was logged. Care should be used when checking this
option as large log files may take a very long time to load.
Gamma Bit Depth Offset
This denotes the distance between the bit and the gamma sensor
(in feet). This value is subtracted from the bit depth value, and this
new value is logged with the gamma data point. Note: This offset is
set in the Settings portion of the Archive Database and should be
changed only there.
Section 04
58
Grid Depth Resolution
This denotes the distance between two horizontal gradients in the

Gamma plot. The drop down list offers options, however;
alternatively, the operator can enter his own distance options. This
item is only relevant when the Plot Method is set to “Depth Based.”
Section 04
59
Log Status Window
This window appears as an option on the Window pull-down menu

and summarizes the status for all of the qMWD/PC log files.
For each main window with logging capability, the file name and
recent statistics are shown.
The statistics for all files are re-initialized whenever pumps are
turned on. The statistics for an individual file are also re-initialized
whenever logging is turned on or off for the corresponding main
window.
DO NOT log the Log Status data to floppy disks as floppies tend to
fill very quickly and may cause a fault in the program.
Log File Setup
Double clicking on a log status line will bring up the setup dialog
box relating to that log file. All individual Log files can be accessed
from this dialog. Logging may be turned on or off, and the name
and location of the log file may be selected.
Section 04
60
Log Status Setup
Right clicking on the Log Status window will bring up a shortcut

menu for access to the Log Status Setup dialog box. The setup
variables for the Logging Status window include:
Disk Evaluation Period
It specifies (in seconds) how often the disk consumption of all of the
log files should be computed.
Disk Warning Triggers

The 5 values may be set to indicate the times (in minutes) at which
warnings should appear before the anticipated end of disk space is
reached.
Section 04
61
Depth Tracking Data Window
It shows the Depth Tracking Data Block (DTD), Pump Flow Data
(PFD) and Generic Sensor Data (GSD) blocks as they are
broadcast from the Surface Receiver. Only the most recent blocks
received are displayed, and each block is independent from the
other blocks.
Each Data block can have logging turned On/Off independently,

and can be browsed independently.
Section 04
62
Depth Tracking Setup
Right clicking on the Depth Tracking Data window will bring up a

shortcut menu for access to the Depth Tracking Data Setup dialog
box.
The setup variables for the Depth Tracking Data window include:
Data Log File
Logging At Startup
When set to "On", logging for Depth Tracking related Data would be
Log pull-down menu.
Logging On/Off
Section 04
63
Depth Tracking Commands
On Bottom – This command will force the bit depth and the
measured depth to be equal and depth will be added as the depth
encoder is moved in an increasing direction.
In Slips – This command will manually force the system to place

the drill string in the In Slips position. Depth Tracking ceases and
no depth tracking will be logged or measured.
Zero the Hook Load – This command will measure the hook and
place that value in the system as an offset in the program. This
should be done only when the system is measuring the block and
Kelly, alone. This measurement is designed to eliminate the weight
of the block and Kelly to more accurately measure the drill string
and allow the system to measure and make connections.
Section 04
64
Set OBHL
This command will allow the user to check the current Off Bottom
Hookload value and then set a new value if necessary.
To view and/or change this variable, press the Set OBHL button.
The current value of the OBHL will then be displayed in a dialog
box. To change the OBHL, enter the desired value and press the
Send button. The program will then send the new OBHL to the
receiver. The display for the OBHL will be blanked, and the new
value will be read back from the remote terminal and displayed.
NOTE: The Off Bottom Hook Load is used to automatically

establish an ‘On-Bottom condition and to compute the Weight-On-
Bit (WOB). If the Depth Tracking Mode (DTMo) is in the ‘Manual’
mode, then the operator must enter this value manually. If the
DTMo is in the ‘Automatic’ mode, then the OBHL is automatically
established within the first several seconds after coming out of
Slips. The algorithm assumes that at least 20 seconds is available
before the hook motion begins to indicate the bit motion back to
bottom. During this period, it is assumed that slips are removed
from the rig floor and the pumps are started and flow is stabilized.
Care should be taken when using these commands, because either

one can adversely affect the operation of the depth tracking system
Section 04
65
Set Depth or Change Depth
Depth can be changed in two different ways. Under the depth label
in the menu, pull down the depth menu and you will see two
different depth windows.
Bit Depth – The Bit Depth can be changed to match the desired
depth required. If the bit depth is deeper than the Measured Depth,
then the Measured Depth will be changed to reflect that of the bit
depth. Use caution when executing this command.
Measured Depth – This entry can be changed to reflect the

desired depth required. The operator can apply this depth if a Rate
of Penetration required monitoring during a reaming run. This entry
can be deeper than the Bit Depth, if the operator so chooses.
Transmit Depths – This command is used if the operator enters

only one value, in either the Bit Depth or the Measured Depth and
would like both depths to be changed simultaneously. Otherwise,
only the individual depths entered will be changed.
Section 04
66
The operator can enter the correct Measured Depth to match that
of the hole and can then enter a Bit Depth shallower. When the
driller reaches bottom with the bit and begins drilling, then the
operator can then initiate the On Bottom command and the depth
tracking system will begin operating accurately.
Monitoring Hook Position Scale Factor (HPsf): Using the

formula described below, the operator should compare the
measurement of the Depth Encoder per joint with the Pipe Tally
gathered from the driller. Input the data into the formula and make
the appropriate adjustments from the Depth Tracking Controls
selection. DO NOT MAKE ADJUSTMENTS TO THE HOOK
POSITION SCALE FACTOR (HPsf) WHILE THE WHEEL IS IN
MOTION. THE WHEEL MUST BE STATIONARY, OR ERRORS
WILL OCCUR IN THE DEPTH TRACKING PROCESS.
Section 04
67
Set-Up Depth Tracking
(Re-) Calibrate Depth Encoder Wheel

There are two methods to calibrate the depth encoder wheel.
First Method
Mark the kelly or some part of the BHA and note the Hook Position
in the TENSOR program.
Have the driller move the pipe up or down a pre-measured
distance.
Compare the distance measured by the depth encoder and the pre-
measured distance on the BHA.
Use the formula below to adjust the HPsf value to calibrate the
depth encoder.
X (new HPsf) = Y (existing HPsf)

BHA distance Depth Encoder
distance
Solve for X, which is the encoder variable that will be used to

calibrate the HPsf to provide proper measurements relative to the
movement of the Kelly.
Second Method
Using the existing Hook Position Scale Factor (HPsf) value, allow
the driller to drill one or more joints of pipe and note the distance
measured by the depth tracking system. Example: 1st joint drilled,
measured 28.56’ on the depth tracking system, and the driller
strapped the joint to be 29.78’. The existing HPsf = 0.1003
X (new HPsf) = 0.103

29.78 ft. 28.56 ft.
Solving for: X = 3.0673 ÷ 28.56 => .107
Access System Setup and Depth Tracking Controls and with Depth
Tracking activated to Manual or Automatic, change the HPsf to the
new value. Insure that the Depth Encoder wheel is not in motion.
Section 04
68
INDEX
%
% Decode .......................................................................................................................36
(
(HPsf)..........................................................................................................................30, 67
A
Alarm Settings ................................................................................................................41
Archive Database .........................................................................................10
Connect.........................................................................................................................10
Archive DataBase
API Number..................................................................................................................11
Required Data Entries...................................................................................................11
Run Description ............................................................................................................11
Well Name ....................................................................................................................11
ATTENTION!! ............................................................................................6
Automatic Depth Tracking ............................................................................................22
Azimuth .....................................................................................................................19, 33
B
Bad ...................................................................................................................................18
Basic Receiver Controls .........................................................................27
Battery ............................................................................................................................36
Bit Depth....................................................................................................................37, 66
Browsing Pulse Waveform Display .............................................................................44
Browsing the Log File....................................................................................................45
C
Calculate TVD from MD Option..............................................................20

Calibrate Depth Encoder Wheel ..................................................................................68
Change Depth ................................................................................................................66
Confidence ....................................................................................................................35
Constant Distance Rate-of-Penetration Averaging Number (ROPd)................................26
Constant Time Rate-of-Penetration Averaging Number (ROPn) .....................................26
D
DAO .................................................................................................................................37
Data Limits ..............................................................................................................16
Data Word Log File........................................................................................................47
Data Word Setup............................................................................................................47
Depth Prompt Mode .........................................................................................................23
Depth Tracking .................................................................................................................22
Depth Tracking Controls ..............................................................................................23
Depth Tracking Commands..........................................................................................64
Depth Tracking Data......................................................................................................37
Depth Tracking Data Update Time (DTUT) ................................................................25
Depth Tracking Data Window ......................................................................................62
Depth Tracking Mode (DTMo) ........................................................................................24
Section 04
69
Depth Tracking Setup....................................................................................................63
Depth Update Interval....................................................................................................16
Dip Angle .......................................................................................................................36
Disk Evaluation Period ..................................................................................................61
Dogleg Severity ...............................................................................................................19
Down Time.....................................................................................................................34
Driller’s Remote Serial Number .......................................................................................28
E
East Coordinate ..............................................................................................................19
Event Logging ..................................................................................................................31
G
Gamma Bit Depth Offset...............................................................................................58
Gamma Data ..................................................................................................................56
Gamma Data Log File ...................................................................................................57
Gamma Data Setup.......................................................................................................57
Gamma Plot....................................................................................................................58
General .......................................................................................................................11
Getting Started .................................................................................................7
Gravity .............................................................................................................................37
Grid Depth Resolution...................................................................................................59
H
Hook Load.......................................................................................................................38
Hook Position .................................................................................................................38
Hook Position Scale Factor (HPsf).............................................................................30, 67
I
In Slips............................................................................................................................64
Inclination .................................................................................................................18, 33
Insert New Survey.............................................................................................20
In-Slips Hook Load (ISHL) ..............................................................................................24
L
Limit Depth .....................................................................................................................16
Limit Gamma..................................................................................................................16
Log File Setup ................................................................................................................60
Log Status Window........................................................................................................60
Logging At Startup .............................................................................................47, 55, 57
Logging On/Off ...................................................................................................47, 55, 58
M
Mag Field........................................................................................................................36
Manually Set Survey Depth..........................................................................................51
Measured Depth.......................................................................................................37, 66
Minimum Drilling Weight-on-Bit Threshold (MnWB)....................................................25
Minimum In-Slips Travel Distance (ISTD)......................................................................24
Minimum String Weight Threshold (StWt)......................................................................25
Mode................................................................................................................................37
N
New ...............................................................................................................................12
Section 04
2
New Toolface Data Outside..........................................................................................40
North Coordinate............................................................................................................19
O
Off Bottom Travel Distance (OBTD) ...............................................................................25
Off-Bottom Hook Load (OBHL) ......................................................................................26
On Bottom .......................................................................................................................64
On Bottom Detection Method (OBDM) ...........................................................................24
P
Pipe Length (PLen)...........................................................................................................25
Plot Method.....................................................................................................................58
Print Survey Data ...........................................................................................................30
Print Toolface Angles .....................................................................................................29
Printing Controls...............................................................................................................29
Pulse Amplitude .............................................................................................................36
Pulse Amplitude Limits ("LoPL" and "HiPL").................................................................28
Pulse Data Buffer Features ..........................................................................................53
Pulse Data Buffer Log File............................................................................................55
Pulse Data Buffer Setup................................................................................................55
Pulse Data Buffer Window............................................................................................52
Pulse Waveform Data Window ....................................................................................43
Pump PSI ........................................................................................................................34
Pump State ....................................................................................................................34
Pumps-On Threshold ("PmpT") .......................................................................................28
Q
qBus Communications ..............................................................................8

qMWDPC Display Screen ........................................................................21
Quality..............................................................................................................................35
R
Receive Delay Time ("RxDT").........................................................................................27
ROP .................................................................................................................................38
ROP Age .........................................................................................................................38
Run...................................................................................................................................19
S
Sensor Offsets.......................................................................................................14
Set Depth ........................................................................................................................66
Set OBHL ........................................................................................................................65
Set System Time ...............................................................................................................29
Set-Up Depth Tracking..................................................................................................68
Standard Pipe Length.....................................................................................................22
Survey Data Blocks Setup ............................................................................................51
Survey Data Calculations .............................................................................18
Survey Data Filter.............................................................................................................30
Survey Data Window .....................................................................................................49
Survey Depth...................................................................................................................18
Survey Options .....................................................................................................13
Survey Sensor Bit Depth Offset ...................................................................................50
Survey Source..................................................................................................................19
Section 04
3
Survey Time ....................................................................................................................19
Surveys .......................................................................................................................17
Synch Timing Window Factor ("SyWF").........................................................................28
System Commands ...........................................................................................23
System Setup ........................................................................................................22
T
TAB SELECTIONS ...........................................................................................12, 13, 14
Target Rose ...................................................................................................................33
Telemetry Data...............................................................................................................36
Telemetry Data Monitor Window ...............................................32
Telemetry Data Window Setup ....................................................................................39
Telemetry Data Words ..................................................................................................45
Telemetry Monitor Setup ..............................................................................................39
Telemetry Monitor Window Colors ..............................................................................40
Telemetry Status ............................................................................................................34
Temperature..................................................................................................................36
TFA Print Timestamp.......................................................................................................30
Tie-Ins .........................................................................................................................15
ToolFace.........................................................................................................................33
Toolface Display Offset .................................................................................................39
Toolface Display Scale..................................................................................................40
Transmit Depths...........................................................................................................66
TVD............................................................................................................................19, 37
U
Up Time ...........................................................................................................................34
V
VARIABLE UNITS DEFINITION UTILITY™...........6

Vertical Section ...............................................................................................................19
W
Window Colors ...............................................................................................................40
Windows 95/98....................................................................................................................5
WOB ................................................................................................................................38
Z
Zero the Hook Load.....................................................................................................64
Section 04
4
g GE Power Systems
Tensor MWD
DRILLER’S REMOTE TERMINAL
RIG FLOOR DISPLAY
2
Section 05
Version 2.00; February, 2002 DRT Ops
REMOTE TERMINAL OPERATION
The Driller's Remote Terminal Display is a lightweight, compact, low power,

and intrinsically safe system that is capable of containing a surface qMWD
receiver processor and electronics for simple system configurations. The unit
is loaded from programs resident in the PC and performs all of the decoding
and processing of the data received from the downhole probe processor. The
unit weighs 15 pounds. A description of the operational methods is detailed
below.
Power Up
The Driller's Remote Terminal Display is powered when the system is

plugged into the Safe Area Power Supply unit connected to a 110 VAC
source. The power supply can be attached to a 220 VAC source and will
automatically adapt to that power rating.
Key Pad Operation
The display includes a keypad with 16 colored and engraved keys. The
keypad is organized in a 4 X 4 key matrix and is used to control the display
contrast and set or view operator selectable controls. NOTE: Some of the
operations of the keypad that will be discussed in this section are subject to
change in future versions.
1. The two CONT keys at the upper left corner of the keypad are
used to adjust the contrast of the display. Pressing the top key
increases the display contrast while the lower key reduces the
contrast. A built in temperature sensor allows automatic
compensation of contrast changes that occur because of temperature
changes.
2. The SHFT key allows the operator to enter the red filled, engraved
characters on the white keys. This is always pressed immediately
preceding the desired character key. When pressed, a 1 will appear in
the inverse video cursor box in the lower left-hand portion of the
screen display.
3. The SHFT key allows the operator to select functions, which are
identified by the green filled, engraved, mnemonics on the white
keys. This key is always pressed immediately preceding the desired
character key. When pressed, a 2 will appear in the inverse video
cursor box in the lower left-hand portion of the screen display.
3
Section 05
4. The Non-Shifted characters in the 'data entry mode' are the digits
0 through 9.
5. The Shifted characters in the data entry mode are A through F, N,

Y, minus sign [-], comma [,], colon [:], and decimal point [.].
6. The DEL key in the data entry mode removes the last character
entered from the data entry line at the bottom of the menu. This key
is sometimes used to clear inverse video warning conditions such as
in the case of the Gamma and Resistivity pictures.
7. The ENTR key is used to cancel entry. The characters in the data
entry line of the menu are then processed. If all data has been
removed from the entry line, the ENTR key will cause the previous
menu to be displayed.
8. The UP and DOWN and the LEFT and RGHT and the ESC keys
will most likely be used to move a cursor and exit from a menu
display in future software versions.
4
Section 05
Menu/Control Options - Screen #1 (Depress Key 1)
All display control options that may be set by the operator from the display
keypad are controlled from this screen. The display menu options are quite
self-explanatory. This screen can be accessed from any other screen by
depressing Key 1 on the keypad. The control options can be selected by
depressing the appropriate option number. After choosing a particular
control option depress ENTER to view the options. The selections will then
be displayed. Choose an option or input a value and depress ENTER. Then
depress ENTER once more to return to the previous menu. Below is a brief
description of each of the options, their uses, and limits.
1. Pulse Polarity
This option defines the vertical scaling on the pulse waveform display.
This option is selected externally by setting the ASCII "PuTy" variable.
Display External Description

Option # Value
0 "Negative" Used with negative pulse systems;

all positive filter values are clipped.
1 "Positive" Used with positive pulse systems; all

negative filter values are clipped.
2 "Bipolar" Provided for engineering purposes

No clipping.
Depress the appropriate number to select the pulse display required

and depress ENTER. Depress ENTER one more time to return to
the previously displayed screen. Note: This is a 'display only'
option and will not affect the decoding process. The GE Power
Systems Tensor MWD is a positive pulse system and selection 1
should be optioned for the pulse polarity display.
5
Section 05
2. Pulse Display
This option affects the method of the pulse waveform display as it

progresses across the screen. This option is only for the operator's
customizing preferences.
Display External Description

Option # Value
0 "Piece" Displays the pulse wave form across

the screen with new data appearing from the right
1 "Scope" Displays the pulse waveform across

the screen with new data appearing from the left.
3. Pulse Amplitude Scale Mode Options
The pulse scale option allows the user to select either "Fixed" or
"Auto" scaling modes of operation for the vertical pulse amplitude
scale in the pulse waveform display.
4. Pulse Amplitude Range Options
This option allows the operator to define the pulse amplitude range
for the pulse waveform when using the 'Fixed' scale mode. This
variable also defines the initial auto scale setting in the 'Auto' scale
mode.
The scale options are: 10, 20, 40, 80, 160, 320, and 640 PSI.
5. Toolface Angle Display
This option allows the operator to select the digital toolface value
to be displayed a 0° to 359° for Magnetic ToolFace Angle display
or -180° (Left) to 179° (Right) for Gravity (HighSide) ToolFace
Angle Display. This is not an automatic function as it is on the
PC, so the operator will have to option this selection to make the
changes as desired or needed.
6
Section 05
6. Toolface Heading Offset
This option allows the operator to enter a 'Desired Toolface

Heading', which in effect, rotates the compass so that the desired
heading is at the top of the graphic display. In this case, the digital
value is the deviation from the desired heading. The limits are
from 0° to 360°.
THIS IS A FEATURE THAT WE STRONGLY ADVISE N O T
USING, AS IT CAN PRESENT INCORRECT DISPLAYS OF
DATA TO THE UNTRAINED USER!
7. Toolface Direction
This option allows the operator to select the latest toolface marker
on the compass face to update in a direction either
"Outer-to-Inner" or "Inner-to-Outer.” This is another
customization feature available to the operator.
8. Time Display
This option allows the operator to select the time display on the
Toolface display screen and determine the size of the display.
9. Gamma Trip Point (Limits 0 to 300 API)
This value is displayed at the bottom of the Gamma Log display.

When the most recent gamma value exceeds the gamma trip point,
the gamma display will automatically enter the inverse video mode
to provide the operator with a very visible and obvious
notification.
10. # of Gamma Data Points (Limits 10 to 80)
This option allows the operator to select the number of gamma points
to be displayed on the screen at one time. This is a scaling method.
11. Gamma Data
This option allows the operator to select whether to display the data
with the most recent value either at the top or at the bottom.
7
Section 05
12. Gamma Scaling
This allows the operator to select the scaling range of the log to be
fixed by a specified minimum and maximum or to be auto ranging.
13. Gamma Max Scale (If fixed) (Limits 20 to 300 API)
This allows the operator to fix the upper end (Maximum) width of the
gamma scale on the log.
14. Gamma Min Scale (If fixed) (Limits 0 to 280 API)
This allows the operator to fix the lower end (Minimum) width of the
gamma scale on the log.
15. Resistivity Trip Point (Limits 0.00 to 9999.00)
This value is displayed at the bottom of the Resistivity Log display.

When the most recent resistivity value exceeds the resistivity trip
point, the Resistivity Display will automatically enter the inverse
video mode to provide the operator with a very visible and obvious
notification.
16. # of Resistivity Data Points (Limit 10 to 80)
This option allows the operator to select the number of resistivity

points to be displayed on the screen at one time. This is a scaling
method.
17. Resistivity Data
This option allows the operator to select whether to display the data
with the most recent value either at the top or at the bottom.
8
Section 05
Azimuth, Inclination, and Toolface Displays - Screen 2
This Screen Option has six (6) display options –

01, 02, 03, 04, 05, & 06.
When the remote terminal display is powered up, it will begin in

Screen 2, or in the last screen option (01 through 06) that was
displayed when the RT was powered down. All six screen options
display the same general data such as Azimuth, Inclination, and
Toolface. There will be a digital display for the most recent
Azimuth value, which is presented to a resolution of 0.1°. And a
digital display for the most recent Inclination value, which is
presented to a resolution of 0.1°. A graphic display of Historical
Toolface readings displays the five most recent values on a
compass rose display. The center of the compass displays the most
recent Toolface Angle in digital form and also indicates the type of
toolface being displayed as either magnetic or gravity. The
operator may select the digital toolface value to be displayed as 0°
to 359° for Magnetic Toolfaces or 0° to -180° (left) and 0° to
+180° (right) for Gravity (HighSide) Toolface display as explained
above in screen 1, selection 5. The update direction for the
Toolface indicator may be selected as 'Outer-to-Inner' or
'Inner-to-Outer' for the position of the latest toolface.
9
Section 05
The differences in the displays for Screen 2 are acquired by
depressing the following buttons in the indicated sequence:
01 Directional data Only w/ pulse trace on lower

section.
02 Directional data Plus Gamma w/pulse trace on

lower section.
03 Directional data Plus Gamma/Resistivity w/ pulse

trace on lower section.
04 Directional data Only w/ Message Lines on lower

section.
05 Directional data Plus Gamma w/ Message Lines on

lower section
06 Directional data Plus Gamma/Resistivity w/ Message

Lines on lower section
07 DownLink Control Menus
10
Section 05
Receiver Status and Graphic Pulse Display - Screen 3
The information on the display screen provides receiver status

information in digital and annotated form to include: pump
pressure (SPP), average pulse amplitude, (not available when both
gamma and resistivity data are being displayed) and the receiver
decoding status. The oscilloscope pulse waveform displays the
pulse after both analog and digital filtering with the most recent
pulses on the right of the screen. The length of the display will
vary depending on whether the resistivity and/or gamma data
displays are selected. However, the horizontal time scale
automatically adjusts to the data rate (pulse width). Depending on
the available display width, the display will typically contain 7 to
11 pulse waveforms.
The vertical scale mode is operator selectable as fixed or auto

scaling. In the fixed scale mode, the operator may define the scale.
The amplitude scale options range from 10 to 640 PSI in both the
auto and fixed scale modes. When the receiver indicates that the
pump pressure is below the defined pumps-on-threshold, the pulse
waveform is replaced with the words "PUMPS OFF" in large, bold
24 x 32 pixel characters.
11
Section 05
Gamma/Resistivity Data Display - Screen 4
This display screen includes a graphic representation of Gamma

data on the left side of the screen and Resistivity data on the right.
The operator may select from 10 to 80 data points to be displayed
for each screen independently from each other as described above
in section A. The display is a strip chart type format, with the data
points displayed vertically with the most recent value either at the
top or at the bottom as specified by the operator. The display can
accept Gamma data in the range of 0 to 300 API units and
Resistivity data, on a logarithmic scale, that allows the data to be
displayed in a range from 0.01 to 99992 ohmmeters in six decades.
For the resistivity, only two decades are displayed and the
processor automatically adjusts the scaling according to the most
recent resistivity value. For Gamma the display window may be
100 API, 200 API, or 300 API units wide on the horizontal scale
with auto-scaling capability. The operator may enter a Gamma
Trip Point and/or a Resistivity Trip Point as described above in
section A.
Transmitted Data Display - Screen 5
This screen displays the data from the downhole tool as they are
decoded. The quality of the signal is averaged and displayed along
with the confidence of the decoded value.
Recorded Survey Data Display - Screen 6
This screen displays the record of all surveys transmitted by the

downhole tool chronologically.
12
Section 05
DRT DownLink Prompt Utility
Screen 7
Overview
The downlink utility is a menu driven application that leads the user
through the steps necessary to downlink either Mode or
Rate/Sequence Information from the surface to the downhole tool.
The application is divided into two basic sections. In the first section,
the user is presented with available downlink options, and allowed to
choose which particular option(s) they wish to change. The second
section leads the user through the pump timing sequences required to
communicate the selected options to the receiver and downhole tool.
Due to the nature of the communication medium, the DownLinking is

not an exact science. Inherently, the receiver and the downhole tool
have differences in how they interpret pressure pulses. The
application can, and does, query the receiver as to the configuration it
thinks is in effect, and in most cases, but not always, this will match
the configuration of the downhole too. Final determination of the
validity of the downlink requires the user to examine the data sets
uplinked from the downhole tool to determine if the tool was
configured correctly.
13
Section 05
Keypad Usage and Startup
To start the utility, press the “7” Key from any of the DRT displays
with the exception of the menu screen – Screen #1.
To select an item, enter the number to its left, followed by the

“ENTR” Key.
To ‘backspace’ over an entry, use the “DEL” key.
Attempting to execute a downlink before selecting a valid mode or

variable will result in an error.
An “ESC” key sequence is available to abort execution after the

downlink has started.
SHFT (Green “SHFT’ Key), followed by the ESC key, will prompt
the user through an exit of the downlink.
NOTE: When using the shift key, depress the shift key,
followed by the next key. Do NOT depress both keys
simultaneously.
Mode Operation
Mode DownLinks have the simplest interface; the application will

present the user with two selection screens, and then prompt the user
through the downlink sequence.
The initial screen is a list of the four available modes, and a synopsis
of the variables constituting that mode. Select the desired mode by
entering the number to the left of the selection followed by the
“ENTR’ Key. If the selection is valid, the screen will cycle to the
mode confirmation screen.
The mode confirmation screen will present the user with a detailed
listing of the variables involved with the selected mode, and provide
the option of continuing with the downlink or returning to the
previous menu.
14
Section 05
Rate/Sequence Operation
Rate/Sequence operation allows the user to downlink individual

variables. There are five screens available.
• The initial screen is a list of all three variables that may be

selected, and Exit option, and a selection that will display the
current configuration.
• Each available variable (three) has an option screen associated

with it. They are:
• Survey Sequence Number
• Toolface Sequence Number
• Pulse Width Option Number
The screen associated with each variable will display a list of all
available options for the item selected, and an exit option.
• A confirmation screen that displays the variable selected, and

allows the user to either continue with the downlink, or return to
the previous menu.
To operate, select the variable to be changed by entering its number on the

keypad followed by the “ENTR” key. The screen will display a list of all of
the available values. Enter the number of the desired value, followed by the
“ENTR” key. The screen will cycle to a confirmation screen displaying the
item selected. Select “Execute DownLink” and the display will cycle to the
downlink execution portion of the application. Select “Previous menu” to
return to the startup screen.
15
Section 05
DownLink Execution
Regardless of whether the system is in Mode or Rate/Sequence, downlink

execution is the same. The downlink screen is divided into three basic
sections.
• Top – Operator instruction and countdown timer.

• Middle – Pump pressure and up/down time.
• Bottom – Sequence synopsis and status.
The top area of the screen is the user prompt area and countdown timer. As
the downlink proceeds, this section is used to tell the user what is to be done,
and how much time remains.
The middle section of the screen provides Pump pressure, total uptime, or
downtime depending on the current location in the sequence.
The bottom section of the screen provides a synopsis of what the process will
be for the complete downlink, and indicates the current location in the
downlink sequence.
Regardless of the variable being downlinked, every downlink will consist of:
1. Two or more Command Pulses (Pumps On) that define the parameter
being modified,
2. An option/value interval (Pumps Off) that defines the option/value being
set for the parameter, and
3. A terminating Pumps On.
During the downlink, the user will be prompted to turn pumps on and pumps
off. If during the sequence, the pump timing violates the minimum or
maximum timing parameters, an abort cycle will be automatically invoked.
When the sequence has completed successfully, the screen will display a
message that the downlink has completed, and display a message to that
effect with a list of the current configuration from the receiver. Enter SHFT,
ESC, and the display will return to the screen that was active prior to starting
the utility.
16
Section 05
DownLink Exits
There are two ways to abort a downlink sequence after the sequence has
begun execution.
• Automatic
• User Requested
Regardless of how it is invoked, the abort cycle functions the same as the
normal downlink process. The primary difference is that if a pump timing
violation occurs during the abort sequence, the state of the downhole tool and
the receiver will be unknown.
Auto Abort
An auto-abort cycle is invoked when the application detects a violation of the

pump timing parameters. When the violation is detected, the display will
cycle to the abort screen(s). The display will prompt for pumps on / pumps
off cycles to cleanly abort the downlink. When the downlink abort has
successfully completed, the display will return to the original downlink
screen.
Manual Abort
Manual abort may be invoked during the command pulses or during the
option interval. To start a manual abort, depress the SHFT key, followed by
the ESC key (Do NOT depress SHFT and ESC at the same time). The
precise functionality of the ESC sequence is determined by the current state
of the downlink process.
If the downlink has not yet started, control is returned to the confirmation
screen.
If the downlink sequence has begun, the ESC sequence will cycle the user
into the abort-downlink-sequence screen(s).
If the DRT is currently in an abort sequence, the application will restart.
17
Section 05
General Operation
When the abort key sequence has been recognized, a message box will be
displayed on the top of the screen. Continue to follow the operating
instructions displayed on the display. When the application can cleanly
interrupt the downlink sequence, it will automatically cycle into the abort
sequence. When the abort sequence begins, follow the instructions for
pumps on / pumps off. Then the abort sequence is complete, a message
indicating successful completion will be displayed.
18
Section 05
19
Section 05
NOTES
20
Section 05
g GE Power Systems
Tensor MWD
qW32 Server
qTalk Procedures
qTALK NOTICE TO ALL qMWD™ USERS
qTalk is still an available DOS system program. It is required to be able to operate
the BootLoad program and load the firmware to the individual processors, 05, 09, 20,
21, and 27. The same commands are still available and still apply. At the end of this
section, you will find the directions for operating the DOS version of the qTalk
program. Following is a description of the new W32 qServer system that operates
via the Network Interface Device attached to the qBus cable, commonly called the
qNIC or dongle. Software updates may also come available for the qNIC and the
load instructions are the same for this device when necessary, but only of the –02A
modules.
2
Section 06
Version 2.00; February, 2002 06WINqTalK_GE.doc
INTRODUCTION
qTalk System Utilities is the program used to communicate with the

various nodes on the qTalk for Win95 version, now contained in the
qW32 Server program.
To access the qW32 Server, simply place the mouse arrow on the q W32
Server Icon located on the Task Bar and click once. The following
window will appear.
By simply clicking on the qTalk button or pressing the q key the

following window will appear.
The Win32 qTalk display is entirely different from the previous DOS
version, and is more versatile.
3
Section 06
qTalk/W32 Window
qTalk/W32 is a limited version of qTalk for 32 bit windows.
There are three large main windows in qTalk and one small, single line
window above the three main windows. The Message contents widow
allows the operator to choose from numerous hard coded messages to
transmit to the systems or enter ones of his own choosing from the
mnemonics list at the end of this chapter. The topmost window,
Received Messages is for all messages sent and received in a constantly
scrolling fashion. The screen can be paused with the toggle switch for
closer examination. The middle window, Sent Messages, is for
recording all messages sent by the PC either from the program,
QDTW32 or those issued by the operator via the Message Contents
window. The lower window, Responses, records all responses from the
respective nodes that respond to any queries sent from the PC. As long
as the qServer is booted these messages and responses will be saved in
the scrolling fashion.
4
Section 06
Should the operator prefer to send a query or command to a particular,
then the destination label or destination address can be selected to direct
the query or command to that particular node address. Most commands
can be performed with the ‘wild card’ ## selection and the ____ open
label.
The Pause button pauses scrolling of message. This makes it easier to

inspect previous messages.
The Clear Display button clears the main message windows.
The Exit button quits qTalk/W32.
Other commands:
Logging qTalk/W32 Messages to a File
Playing Back a qTalk Log File
Changing the BAUD Rate
Checking Node Status
5
Section 06
Node Status Window
This screen identifies all on-line nodes on the qBus and displays any
warnings or faults that each node might have. This is equivalent to
sending the message:
\____##/?\qdfr? qdwr?
Instead of showing the fault and warning register values, however, a

brief description relating to each warning or fault bit set in the registers
is displayed.
6
Section 06
Changing the BAUD Rate
To change the baud rate, start qTalk and then hold down the <Alt> key
and type the letter ‘b’. This brings up the qW32Srvr BAUD Rate dialog
box. Select one of the BAUD rates, or type your own, and click on
‘OK’.
Clear the Status Message Window
Clicking on this button clears all warning and error messages in

the Status window of the main qW32Srvr dialog.
7
Section 06
Logging qTalk/W32 Messages to a File
To start logging to disk, type <Alt-L> while running the qTalk/W32

window. The default qTalk log file name is qW32Talk.Log. To turn
logging off, type <Alt-L> again. Care should be taken in generating a
qTalk log, as these logs tend to grow large very rapidly. Notice the
Logging windowpane next to the Sent Messages display.
Playing Back a qTalk Log File
To play back a qTalk/W32 log file, type <Alt-D> from the qTalk
window and select the desired log file to play back. The default qTalk
log file name is qW32Talk.Log. This will send all messages logged to
all qMWD/W32 client programs at a steady rate. Typing <Alt-D> again
turns off the playback feature.
8
Section 06
COM Port
The port used to communicate with the qBus nodes can be used by
clicking on the system menu icon at the top left corner of the qW32Srvr
server (the gray and black Q icon) and then selecting the menu item
COM Port. You must know the COM port that is going to be used for
communicating with qBus nodes before you make the change. In the
case of notebook or laptop computers, a PCMCIA card is generally used
for this purpose. Use the Win95 Device manager to determine which port
has been assigned for this card (see Win95 documentation for how to
find this out).
The qW32Srvr will default to COM1 when run the first time after the
initial installation of qMWDW32. If it becomes necessary to change the
COM port, the new COM port will be saved in the system registry and
will be used each time the qW32Srvr is run.
Insure the Com port change is required. If the system is

operating properly, do not change the Com Port unless otherwise
directed.
9
Section 06
Stopping the qW32Srvr
Clicking on the STOP MWD System button allows the server to exit, or
quit running. During normal operation, it should not be necessary for the
operator to do this manually. The server keeps a list of running
qMWD/W32 programs. When the last one exits, the server exits as well.
10
Section 06
qTalk DOS
INTRODUCTION
qTalk System Utilities is the program used to communicate with the

various nodes on the network that make up the QDT MWD system. This
program can be partially entered into via the qBus Monitor (Alt-7) in
the qMWD_PC program. When the operator needs to talk directly to the
MWD probe to troubleshoot the probe or any other node on the system,
then this program should be used. Familiarity and practice with this
program, using the manuals provided by QSI will assist the operator
greatly in mastering this process. A mnemonic list of definitions is
contained in the manual to assist the operator in selecting the proper
labels to query the nodes.
Multipoint Mode
qTalk Multipoint mode allows the PC to function like a standard qMIX

device on the bus, as either the master node or a slave node. A
background 'host' process handles communications interrupts, parsing
and, formatting of messages. It uses its own link label (LnkL) and link
address (LnkA) for communicating with other Multipoint nodes. The PC
keyboard and screen act either as a passive bus monitor or as an
interactive, point-to-point port (with a unique link label) for
communicating with the host process.
Normal Operation and Colors
During normal Multipoint operation, the qTalk display

monitors all bus activity, with incoming characters in
Yellow and outgoing characters in Lt. Blue. The
operating mode for qTalk is displayed near the top-right
corner of the screen as a Lt. Blue character indicating one
of four states:
M - Master Mode, S - Slave Mode, I - Idle Mode, C -
Chat Mode
If there is no communication occurring with other
devices, the letter displayed in a lower case. Notice
change when qBus cable is disconnected.
11
Section 06
For an active qMIX bus, the master will be sending calling and polling
sequences to the slave nodes. If qTalK's link address is being polled, it
will be responding with Lt. Blue EOT characters. If qTalk itself is
master, it will be sending the calling and polling sequences in blue, while
any slave responses will be in yellow. In either master or slave modes,
messages going to or from the PC node are handled automatically by
qTalk.
Note that the display on some PC's may not scroll fast enough to keep up
with the qMIX calling and polling sequences at 9600 Baud. If a display
lag develops, the qTalk buffer will hold up to 8192 delayed characters,
after which the message: (break) will appear in red to indicate that a
section of data has been dropped in order to catch up. Using F5-CrLf or
F7-Filt can reduce lag in the display. (Cr. -Carriage Return, Lf- Line
Feed). The break message will also appear when a break sequence is
received on the serial communications line. A repeated string of breaks
usually indicates operation at an incorrect baud rate. Other warning
messages that appear in red indicate problems with the printer or with a
disk file. In host mode, normal interactive dialog occurs in green, while
red indicates an error response.
12
Section 06
Host Mode
In addition to simply monitoring the Multipoint bus activity, the user

may send and receive messages by routing them onto the bus through the
qTalk "Host" mode. In Host mode, the PC keyboard and screen are
treated as a point-to-point port which has the label 'Talk' and uses the
address defined in the qMIX 'LnkA' control variable. I.E., the LnkA is
the number assigned to the PC using the 'Node Address' conventions
described in the Help in qMWD_PC program. The Multipoint port on
the serial bus continues to operate as normal.
You can enter the Host mode in qTalk by pressing the F4 key or ESC.
This is only in qTalk, not in qBus Monitor. In qBus Monitor, you can
use only the F4 key for this procedure. The communication display is
halted and the process presents a ">" prompt character to solicit
messages from the user. Communications are still present, but the
display does not present them on the screen. Only the nodes that have
information relating to the request of the user will respond, displaying
their source routing information preceding the message. You can exit
the Host mode by pressing the 'F4' key or by typing '\M'. This will
reestablish the display showing bus activity.
Once the operator is in the host mode, the qTalk program can be used to
investigate many aspects and conditions on the bus. Practice and
familiarity are imperative for an operator to become proficient with this
system. There numerous routines to enter a command line that can be
used for interrogating the surface system and downhole when it is
connected to the system. Following are a couple of methods used to call
up the command line.
Typed Displayed Purpose

Command Line - \↑\ \____##/?\ Inquiry to all
nodes
\05\ \____05/?\
Inquiry to node 05 (any node address number can be used to specifically
target that particular node)
Following any of these command lines, the operator can enter a label that
relates to a specific function in that particular node. Alternatively, he
can enter a label that relates to all nodes. If a particular node does not
respond to an inquiry, then that particular node probably does not use
that particular command or function related to that label.
13
Section 06
Scrolling Previous Commands - The program is written to allow the
operator to recall up to 10 previously invoked commands by depressing
the up arrow (↑) to go backwards or the down arrow (↓) to go forward.
A particular label can be altered or changed to assist the operator in

performing functions for trouble shooting or testing. To be able to do
this, the operator must enter a command code of 10. The capability level
can be checked by entering the label CLev after the command line,
followed by a ?. To change the level, follow the instructions below.
Please be very careful when performing this function and take care not to
alter labels indiscriminately.
Command Code - CCod 10 will allow the

operator to enter commands and change label
values and switch positions. This command can be
entered after the command line followed by an
exclamation point (!). >\ ##/?\CCod 10!
Extreme Care must be taken when in this
operating mode!
14
Section 06
Soft Keys - The soft keys on the right side of the
screen allow the operator to manipulate the operation of
qTalk. However, some of the keys need not be used for
normal operation. (Note difference of display in qTalk2
and qBus Monitor). For normal operation, the operator
needs to use only:
F4 - Host. This key stops the scrolling of the display to

allow the operator to perform the desired commands.
Toggling the switch will alternate the command.
F7 - Filter. This key eliminates the unanswered link

addresses that are polled. Only the nodes that are active
in qMIX will be displayed.
F8 - Pause. This key stops the scrolling of the data to

allow the operator to view data.
SF1 - Exit. This allows the operator to exit the program.
SF4 - VChk. This command performs a system check on

all of the nodes attached to the system.
SF5 - qDFR. This command performs a system check on

all of the nodes attached to the system.
Note: SF4 and SF5 commands are the same routines performed
on the system in the Node Status screen in the qMWD_PC
program.
SF9 - Term. This command places the system into the

Terminal Mode. Only operators with extensive training
in the operation of qTalk should enter this routine.
Lists of qTalk variables and mnemonics are available in the QDT

Training Manual and the qMWD Engineer's Reference Manual Vol. 2,
Appendices B2 and V. Using these labels in the inquiry mode will foster
great familiarity and confidence in an operator's routine.
15
Section 06
Terminal Mode
The terminal mode of the program qTalk is used only for extensive
troubleshooting or for loading the QSI software to the system. It should
only be used by trained personnel, as should the procedures for loading
the QSI software.
The terminal mode of qTalk is obviously different from the Multipoint

mode in display, due to the lack of color and the menu options. Note:
toggling F10 will switch from the two available menus. They should
read as follows:
Menu 1
F1-Exit F3-Auto LF(Off) F5-Print(Off) F7-Data Bits(8)
F9-Parity(None)
F2-Remote F4-Echo(Off) F6-Baud(9600) F8-Stop Bits(1)
F10-Next Menu
Menu 2
F1-Exit F3-Display (All) F5-Idle! F7-Chat! F9-
Go to Multipoint
F2-Remote F4-EOL Chr(Cr) F6-qMIX! F8-Errors( ) F10-
Next Menu
Following are the toggle options of the soft-keys as they are displayed at
startup and with the options in parentheses. The default options are in
bold type.
16
Section 06
Menu 1 Menu 2
F1 - Exit. This will exit F1 - Exit. this will exit out of
out of the qTalk program. the qTalk program.
F2 - Remote Local F2 - Remote Local
F3 - Auto LF(Off) (On) F3 - Display (All) (I&D) (Dat)
F4 - Echo (Off) (On) (Hex)
F5 - Print (Off) (On) F4 - EOL Chr (Cr) (ETX)
F6 - Baud(600) (1200) ( 2400)( (EOT)
4800) (9600)-(19200) (38400) F5 - Idle! - This will stop the
(115k2) qMIX program to allow the
F7 - Data Bits(8) (7) (6) (5) operator to access a Node
F8 - Stop Bits(1) (2) F6 - qMIX - This will restart the
F9 - Parity(None) (Even) qMIX program after it was
(Mark) (Spce) (Odd) idled.
F10- Toggles the Next Menu F7 - Chat! - This will allow the
operator to select a particular
node to communicate with
F8 - Errors( )
F9 - Go Multipoint - Allows the
operator to re-access the
Multipoint program.
F10- Toggles the Next Menu
17
Section 06
WARNING: After establishing communications with a particular node,
the operator MUST reestablish qMIX communication by selecting the
qMIX softkey (F6), before exiting the qTalk program, otherwise the
node will be idle and may appear non functional. Cycling the power to
the system should cold boot the system for all of the nodes and
reestablish qMIX operations. Care should be taken to know what labels
were changed, if any, and which ones should be changed back to their
original value or setting. You will note that while performing the
configuration routine, the program changes the labels listed in the
configuration, only. The process can be observed with the use of two
PC's connected to the qBus outlets on the SASB, with one PC in qTalk
or qBus monitor.
Every operating company is urged to allow one individual access to

these procedures, for the purpose of upgrading the firmware of the
systems, and each operator should have minimal training to become
familiar with qTalk to enhance their troubleshooting capabilities.
18
Section 06
Commonly Used mNemonic Labels
A
AcqD! Acquire Directional Steering (T/L) Data Command
AcqS! Acquire Directional Survey Data Command
AcqG! Acquire Gamma Data Command
Ax Accelerometer X axis corrected & scaled Data
Ay Accelerometer Y axis corrected & scaled Data
Az Accelerometer Z axis corrected & scaled Data
Azm Directional Sensor Azimuth Data (refer to TAzm)
B
Bat2 Auxiliary Battery Switch Control/State
BatD Battery Data Block
BatV Battery Voltage
BHiV Battery High Voltage Measurement
BLoV Battery Low Voltage Measurement
BThr Low Battery Voltage Threshold
C
CCod Capability Code Number
D
DipA Dip Angle
DLC Downlink Controls Parameter Block
DLTP Downlink Time Period
DSns Directional Sensor Information Block
19
Section 06
G
Gama Gamma Data Value
GamD Gamma Data Block
GamD Gamma Data Block
Grav Gravity Data
gTFA Gravity Toolface Angle
I
Inc Inclination Data
InvF Inverted Flow Switch
L
LnkA qMIXTM Link (node) Address
LnkL qMIXTM Link (node) Label
LnkM qMIXTM Link Mode (following a Reset)
Loc Job Site Location Information Block
LoPL Receiver Low Pulse Amplitude Limit (editing control)
M
MagD Magnetic Data Block
MagF Total Magnetic Field
MDec Magnetic Declination
Mod1 Telemetry Controls Parameter Block for Mode #1
ModC Main Telemetry Mode Controls Parameter Block
ModN Telemetry Mode Number at power on
20
Section 06
P
PLen Pipe Length
PlsC Pulse Controls Parameter Block
PlsW Pulse Width in effect
PmpD Pump Data Block
Pmps Pumps Status - On/Off
PmpP Pump Pressure
PmpT Pumps-On Threshold
PTO Pressure Transducer Offset correction
PW1 Pulse Width for Telemetry Mode #1
Q
qDCR qMIXTM Device Control Register
qDFR qMIXTM Device Fault Register
qDSR qMIXTM Device Status Register
qDWR qMIXTM Device Warning Register
qLNM qBus Host-Mode Log Name, XXXXXXXX.QBM
qLPA qBus Host-Mode Log Path, *.QBM
qMem qMIXTM Memory I/O Function (diagnostic)
qMIX! Go To Normal qMIXTM Mode Command
qSCR qMIXTM System Control Register
qSFR qMIXTM System Fault Register
qSSR qMIXTM System Status Register
qSW qMIXTM Software Version String (refer to Ver)
R
ROPd Constant Distance ROP Averaging Number
ROPn Constant Time ROP Averaging Number
RTOC Receiver Toolface Offset Computation Control
RTTF Receiver Toolface Offset Computation Control
21
Section 06
S
SFlw Simulated Flow control (test & diagnostic)
Site Job Site Information Data Block
SN Processor Hardware Serial Number
SSN1 Survey Sequence Number for Telemetry Mode #1
SSq1 Survey Sequence Definition String #1
StWt String Weight Threshold
SuDT Directional Survey Delay Time
SuWd Survey Word Data Block
T
TFO Toolface Offset
TFS Toolface display type Switch (in qDRT)
Time Date and Time Stamp (YYMMDDHHMMSS)
TLWd Toolface/Logging Word Data Block
TmpT High Temperature Threshold
TSN1 Toolface/Logging Sequence Number for Telemetry
Mode #1
Mode #2
Mode #3
Mode #4
TSq1 Toolface/Logging Sequence Definition String #1
TVD True Vertical Depth
TxDT Telemetry Transmit Delay Time from flow on
22
Section 06
V
VChk() Non-Volatile Variable Check Function (diagnostic)
Ver() Software/Firmware Version Function (information)
Z
ZazD! Clear azimuth data display command (in qDRT)
Zdia! Zero the Diagnostics Data Block Command
ZGaD! Clear gamma data display command (in qDRT)
ZInD! Clear inclination display command (in qDRT)
ZMbD! Clear message box command (in qDRT)
ZReD! Clear resistivity data display command (in qDRT)
ZTFD! Clear toolface data display command (in qDRT)
23
Section 06
NOTES
24
Section 06
g GE Power Systems
Tensor MWD
qProg/11
SYSTEM UTILITIES
This document is an unpublished work. Copyright 2001 GE Power Systems. All rights reserved. “This
document and all information and expression contained herein are the property of GE Power Systems
and is provided to the recipient in confidence on a “need to know” basis. Your use of this document is
strictly limited to a legitimate business purpose requiring the information contained therein. Your use of
this document constitutes acceptance of these terms.”
qProg/11TM System Utilities
Programming M68HC11 Processors
GE Power Systems requires that a license be obtained for the

installation and use of the qProg/11TM M68HC11 Programming
Utility. Licenses may be obtained from:
GE Power Systems
1840 Royston Lane
Round Rock, TEXAS
78664-9555
GE Power Systems reserves the right to make changes without
notice, in the software described or contained herein in order to
improve design and /or performance. GE Power Systems assumes
no responsibility or liability for the use of this software and makes
no representation or warranty that this software is free from patent
or copyright infringement.
"qProg/11" is a trademark of GE Power Systems
1. Introduction to qProg/11
The qProg/11 program is a general purpose utility used to program

application software/firmware into the EEProm of 68HC11
microcontroller based processor boards.
qProg/11 adapts easily to new target hardware simply by defining

the target specifications. When qProg11 is executed to program a
target it first locates the target specification which defines the files,
baud rates, memory configurations, and other information required
to program the target.
The standard sequence used is as follows:
- Load the application software/firmware from disk.
- Download the 1st stage bootloader and receive back
acknowledge character when it begins to execute.
- Download the 2nd stage bootloader and receive back
acknowledge character when it begins to execute.
- Download the application software/firmware.
Variations of the above sequence are possible based on the

command line used to invoke qProg/11. For example, a page zero
RAM program can be loaded into the 68HC11 and executed using
the command line options /BO, /B1, and /B2. See the section
below on the command line for more information.
2
Section 07, Version 2.00; March, 2002 Win_qProg_GE
Before using qProg/11 with a new processor board, the processor
board must be defined by creating a target ID and specification.
See the section on configuration for specific information.
2. Installation of qProg/11 Program
qProg/11 is customarily installed on a hard disk drive in the

c:\BootLoad directory and is by default set up to run in this
directory. qProg/11 can be installed in any directory, however
certain path data and batch files may require minor modifications.
Copy the distribution files to the hard disk as follows (assuming the
source disk is inserted in drive 'b', and the destination is the
c:\bootload directory):
md c:\bootload (if directory does not exist)

xcopy b: c:\bootload /v/s
If installed in a directory named in the DOS PATH statement, the

program can be executed from anywhere on the disk. If not
installed in such a directory, the full path to qProg11.exe or batch
files can be used to invoke the program.
3
3. Configuration
qProg/11 is designed to easily adapt to new and varied hardware.

This is accomplished through the use of an ASCII data file named
qPrg11ID.dat. qPrg11ID.dat is a standard ASCII file, which provides
all the information about the targets to be programmed. The file is
divided into two sections. The first section consists of a list of target
identification data structures, each identified by a unique target ID.
The format of the structure is as follows:
- "Target ID" 1 to 16 characters.

- Target crystal frequency(Hz): determines baud rate for
1st stage.
- "[path]1st stage bootloader program" (.s19 file).
- "[path]2nd stage bootloader program" (.s19 file) or null if
2nd stage not needed.
- Baud rate for 2nd stage or zero.
- "[path]default program to load" (.s19 file) or null.
- Baud rate to load program or zero if same as baud for
last stage.
- "Memory Specification ID for target" see format
documentation below.
- "[path]HC11 Config. Reg. programming file" (.s19 file) or
null.
- Default configuration register value for the /PC command
line option.
The second section of the qPrg11ID.dat file is a list of memory

specification data structures. The memory specifications are
referenced through the "Memory Specification ID for target" field in
the target identification data structure (defined above). Multiple
Targets can use the same memory specification data structure.
The format of this structure is as follows:
- "Memory specification ID for target" referenced by the

target ID structure.
- Number of pages (0x01 if not a paged memory).
- Page size (in bytes)
- Low inclusive address of the memory.
- High inclusive address of the memory.
- Number of check characters or 0
- Check character type or 0 (1 for checksum)
- Address of 1st check character.
- Disable/Enable character by default (0 or 1)
- Fill character value
4
The qPrg11ID.dat file can be edited using any ASCII type editor.
Target ID's are modified or new targets added by simply making
modifications or additions to the target ID and Memory specification
lists. See the qPrg11ID.dat file itself for more information on the file
format, list termination, etc. The file must reside in the same
directory as the qProg11.exe file.
When defining a new target, it may be necessary to create new

versions of the 1st and 2nd stage bootloaders as well as the HC11
config. register programming file. As an aid, the following source
files are provided and can be used as templates for the new files:
Boot11_1.asm -Example 1st stage bootloader

BT80-2_2.asm -Example 2nd stage bootloader
Cnfg$XX.asm -Example HC11 Cnfg. Register
programmer
4. Command Line
The following command line is used to execute the qProg/11 utility:
qProg11 target_id filename.ext /s1/s2/..../sn
where:
(i) "target_id is the target identification string and may be up to
16 alphanumeric characters. The target ID is primarily used
to define the names of the bootloader files and the memory
configuration for the target processor.
(ii) "filename.ext" identifies the source file to be transferred to

the target processor and may be preceded by a path
designation. This file specification may be omitted if it is
specified in the target specification, or if the /BO option
switch is used.
(iii) /s1, /s2 and /sn designate option switch settings and are only
required to change the default settings. A list of available
options can be obtained directly from qProg/11 by entering
'qProg11' by itself on the command line. the options
available are:
/1
/2 The Port select switches. Selects the desired serial
communications port to be used.
/C
/NC The Checksum enable and Checksum disable
5
switches. The Checksum enable switch is the default
and indicates qProg/11 should write checksums. The
type of checksum and destination address are
individually specified for each device in the target
processor.
/F
/NF The Fill and No Fill switches. When No Fill is used,
only the bytes defined by the .s19 file are
programmed. The default is individually specified for
each target. Fill will cause all bytes in a memory or
memory page which are not defined in the source file
to be filled with the character specified for the target.
/G
/NG The Go and No Go switches. No Go is the default.
When Go is used the program will proceed
automatically without operator prompts. The
processor should be in the proper mode before
executing the command line. Go is used often once
the programming procedure has been defined.
/O
/NO The Overlay and No Overlay switches. No Overlay is
the default. The Overlay switch enables overlays.
That is, qProg/11 will not generate errors if the same
address is written more than once. qProg/11
assumes that if the same address is written more than
once that the bootloader is controlling paging.
/P
/NP The Paging enable and Paging disable switches. The
Paging enable is the default and indicates the file
(filename.exe specified on the command line)
contains code which is to be written to multiple pages
at the same bus address. The file should also contain
the appropriate page control bytes. Page control
bytes are defined as a single byte with the base
address of a device as its destination. The value of
the byte indicates the new page for the following
bytes to be programmed.
/V
/NV The Verify enable and Verify disable switches. The
Verify enable switch is the default and causes
qProg/11 to display a verification window to allow
verification for the programming configuration. When
6
neither the /V nor the /NV switches are used, the /G
switch automatically disables verification (an
exception to the default).
/Q The Quiet Mode switch. The switch indicates that no

prompts should be output to the display and that only
one error output is possible.
/NB The No Boot switch. This prevents the program from

attempting the transfer the bootloader programs to the
target processor. It is only used when the bootloader
programs have already been transferred and are
running. This switch causes qProg/11 to proceed
directly to programming the file (filename.exe)
specified on the command line. This option is
typically used when programming a processor with
multiple files, and prevents the need to repeatedly
reset the processor in boot mode.
/BO The Boot Only switch. This option is used when it is

desired to load only the bootloader. qProg/11 will
terminate after the last boot stage is loaded (after the
1st stage if the 2nd stage is not specified).
/PC:[XX]
The Program Config. switch. This option is used to
program the 68HC11 configuration register. The
processor must be in the Bootstrap mode (See the
section entitled 'Invoking Boot Mode'). If only /PC is
typed, the default value specified for the target is
programmed. If /PC:XX is used, the hex value XX is
programmed.
/B1:[path]filename[.ext]
The 1st stage bootloader override switch. This switch
causes qProg/11 to replace the default 1st stage
bootloader with the file specified. the file must be an
'.s19' type file.
/B2:[path]filename[.ext]
The 2nd stage bootloader override switch. This
switch causes qProg/11 to replace the default 2nd
stage bootloader with the file specified. The file must
be an '.S19' type file.
/D:[path]filename[.ext]
Specifies a diagnostic output file path name.
7
All switches allowed with the program may be entered on the
command line and will be passed to the program. Spaces are not
allowed in the option switch portion of the run string!
When qProg/11 runs, the terminal will display the following
sequences:
(i) The source file is read while displaying the progress,

number of lines read, number of bytes read and
number of memory pages to be programmed.
(ii) Unless the operator is used the Go or No Verify

switches, the operator may then verify the
programming information by viewing the status
windows on each memory. At this point, entering "G",
for Go, causes the program to enter the bootloader
stage.
(iii) Provided the operator did not enter the No Boot

switch, the program will begin transferring the next 2
stages of the bootloading processes. Unless the
operator entered the Go switch, the program will
instruct the operator to reset the target processor and
enter "C", for Continue, when the processor has been
reset. If the process fails to get the expected
response after loading the first stage bootloader, it will
stop and ask the operator for instructions (Abort,
Ignore or Retry). If the second stage fails to load or
respond as expected, the program will abort.
(iv) Once the boot loading process is complete, the
program begins transferring the contents of the
source .s19 file and displays the programming
progress for each memory or memory page being
programmed. Generally, the data transfers occur at
38.4K baud and transfer 32 data bytes per exchange
in a single binary string. The programming rate will
vary depending on the types of EEPROM's being
programmed. However, typical programming rates for
Atmel and Xicor 28Cxxx devices will be about 1K data
bytes/second.
8
5. Invoking Boot Mode
The M68HC11 is programmed using the serial communications

interface and a multiple-stage boot loader process. The M68HC11
processor has an internal bootloader program (68HC11 bootstrap
mode) which may be invoked when reset (power on reset or
external reset) with the 68HC11 MODA and MODB inputs pulled
low. The MODA and MODB inputs are usually accessed via test
points or through lines brought out through a connector. This
program loads the next stage boot loader program (1st stage
bootloader) to the 256 byte, internal, 68HC11 RAM. It, in turn,
loads the larger programming process (2nd stage bootloader) to the
larger external RAM. These programs are loaded by the
"qProg/11"PC program.
Once the 2nd stage bootloader is loaded and running in RAM, there
is no need to start over by resetting the 68HC11 in bootstrap mode.
Subsequent programs can programmed by re-executing qProg/11
using the /nb command line option. qProg/11 will then skip directly
to the programming step by communicating with the 2nd stage
bootloader already loaded.
6. Recovering From Problems

Problems may occur during programming, which may lead to a
confusing situation. The following points may be helpful in the
event a programming problem does occur.
(i) When qProg/11 terminates, a message will normally be

displayed indicating the condition at the time of termination. When
programming is successful, this message will say "Programming
Complete". If an error occurred, the error message will be
displayed. An error number will also be displayed. The error
number definitions are as follows:
Serial communication function I/O error return codes. The error

codes from -1000 through -1099 are reserved for the "qSIO" error
codes.
"qSIORx" codes start at -1000>>>>
-1000 General or undefined Rx error
-1001 Character time-out during Rx
-1002 Receiver over run error
-1003 Receiver framing error
-1004 Receiver parity error
-1005 Received break error
-1006 Rx FIFO overflow
-1007 Time-out waiting for data reply
9
"qSIOTx" codes start at -1030>>>>
-1030 General or undefined Rx error
-1031 Character time-out on data transmit
-1032 Receiver over run error during Tx
-1033 Receiver framing error during Tx
-1034 Receiver parity error during Tx
-1035 Received break error during Tx
-1036 Tx FIFO underflow
"qSIO" miscellaneous codes start at -1080>>>>
-1080 Error on data transfer verification
File I/O error return codes. The error codes from -1100
through -1199 are reserved for the "qFIO' error codes.
Open error codes start at -1100>>>>

-1100 General or undefined file error
-1101 DOS did not open a file for read
-1102 DOS did not open a file for write
-1103 DOS did not open a file for append
-1104 DOS did not/could not open an existing file for
Read/Write
-1105 /*DOS did not open a new or destroy existing
file for Read/Write
-1106 /*DOS did not/could not open an existing or
new file for Read/Write
Read file error codes start at -1120>>>>

-1120 /*General or undefined read error */
Write file error codes start at -1140>>>>

-1140 General or undefined write error
Miscellaneous file error codes start at -1160>>>>

-1160 Operator disallowed writing to an existing file
10
Terminal I/O error return codes. The error codes from -1200
through -1299 are reserved for the "qFIO" input error codes.
The error codes from -1300 through -1399 are reserved for
the "qFIO" output error codes.
Terminal input error codes start at -1200>>>>

-1200 General or undefined input error
-1201 An input string exceed the max size that could
be processed
Terminal output error codes start at -1300>>>>

-1300 General or undefined input error
qProg/11 specific error codes.

qProg/11 specific error codes start at -20001>>>>
-20001 Memory allocation error.
-20002 Source file read error.
-20003 Source file record format error.
-20004 Source file character count error.
-20005 Source file character error.
-20006 Source file checksum error.
-20007 Missing memory definition error.
-20008 All pages full error.
-20009 Page boundary error.
-20010 Data overlay error.
-20011 Switch string format error.
-20012 Switch type error.
-20013 Missing file name error.
-20014 File open error.
-20015 Run string error.
-20016 Data acknowledge error.
-20017 Bootload error.
-20018 Check character type error.
-20019 Target ID match error.
-20020 Operator abort.
-20021 Page number error.
-20022 Device overlap error.
-20023 Data in page byte error.
(ii) If you forget to enter the No Boot switch when loading

more than one file, the program will stop and request
operator direction. Abort the program and try again
using the /nb switch. In most cases, this will work.
However, since the first stage boot loader program is
most likely transferred at a different baud rate than
program files, there is no guarantee.
11
(iii) If problems persists, please call GE Power Systems
and ask for assistance from Technical Services.
Please do so from the PC being used to program the
target processor(s), so that we may talk you through
the problem.
g GE Power Systems
Kenneth W. Braud
Customer Technical Service – Tensor Systems
Reuter-Stokes
1840 Royston Lane
Round Rock, TEXAS
(512) 251-4131 (512) 251-7396
(512) 845-6808 Cell
12
qProg/11 TM
Compatibility Notice
qProg/11TM is designed to be a general purpose PC utility program
for loading programs into Motorola M68HC11 MCU-based
equipment such as the qMWDTM receiver, remote terminal and the
downhole transmitter. however, with the large number of PC's
available, there are several minor variations in the electronics used
in the construction of the various PC's. Though it is the general
practice of GE Power Systems to test programs on several different
brands and models of computers GE Power Systems cannot
guarantee that qProg/11TM, or any other programs, will be 100%
compatible with all brands of PC's. Any questions concerning the
compatibility of the software with any PC brand being considered
should be directed to GE Power Systems, 1840 Royston Lane,
Round Rock, TEXAS 78664-9555. (512) 251-4131.
13
QDT - qMWDTM V01.XX
Quick-Start Instructions
Installing qMWD/PCTM Programs & Files
For clients using the Windows 95/98 Windows NT versions of the

QDT MWD software, just insert the CD containing the software in to
the CD port of the PC and follow the highlighted prompts to
properly install the programs. The qProg11 programs will be
located on the C:\ drive. To operate the qProg11 programs, boot
the PC in the DOS mode using the F8 soft key to prevent Windows
from starting and go to the Prompt Only mode. For users with
Windows 98 and Windows NT, just Reboot the system in the DOS
mode for the features to operate.
For clients still using DOS 6.22, follow the instructions for loading
the programs to the PC in the DOS mode using the supplied floppy
disks.
• Insert the "qMWD/PC Disk 1 of 2 Diskette" into drive A: (or

B:).
• Type a:install a: c: <Enter>. The directory

qMWD\qMWD_PC will be created on the C: drive, if it does
not already exist. The qMWD/PCTM programs and files will
be loaded into this directory. If the directory already exists,
then a backup directory will be created to save the old
programs.
• After the files are loaded from Disk 1 of 2, the installation

procedure will prompt you to install the second of the two
qMWD/PC diskettes. The qMWDCnfgTM and qDirK_IOTM
programs and files will also be loaded into the
c:\qMWD\QmWD_PC directory (all PC programs are now
normally loaded on a single directory.
Run these programs through the qMWD_PC, qMWDCnfg and the

qDirK_IO batch files while in the qMWD\qMWD_PC directory.
These batch files must be entered completely as displayed to
insure that the batch file is executed correctly. There some Menu
programs that will activate complete utilization of the batch files.
REMEMBER, these routines cannot be activated through windows,
yet.
14
Installing qProg/11TM
• Insert the qProg/11 Diskette into drive A:.

• Unless it already exists, create a c:\Bootload directory on
the c: drive by typing cd\<Enter> md bootload <Enter>.
• Switch to the c:\Bootload directory by typing cd bootload
<Enter>.
Copy the contents of the qProg/11 Diskette by typing
xcopy a:/v.
Installing qMWD/11TM
Insert the qMWD/11 Diskette into drive A:.
Type a:install a: c: <Enter> The files containing the programs for

the transmitter processor, receiver processor and the DRT
processor will be stored in the directory qMWD. These files will be
needed for accessing the required program files used by the three
processors in the QDT MWD system.
15
Updating Embedded qMWDTM Firmware Programs
AlliedSignal Tensor recommends that the firmware programs in all
qMWD™ hardware such as receivers, displays and the down-hole
tool be upgraded to versions in effect with the qMWD™ V01.60a
release. NOTE: ONLY “qMPTx-2R” program is V01.60a, all other
firmware programs are as released with the qMWD/11 V01.60
distributions and are identified as V01.60 in their application I.D.
strings.
If you are ever unsure as to whether or not the qMWD™ equipment

is loaded with the latest firmware, use the Ver() function to identify
the firmware versions using the qTalk/PC™ (refer to Appendix Q in
the qMWD manual). Appendix P in the qMWD ™ Engineer’s
Reference Manual provides complete instructions for programming
the MC68HC11 based systems used in the qMWD™ hardware.
The following presumes an understanding of those procedures.
NOTE: The qTalk/PC and qProg/11 programs required to upgrade

embedded firmware programs will ONLY function properly when
operating from the DOS-Only mode. From Windows95: Select
“Shut Down”, click on “Restart the Computer”, click on “Yes”, wait
for the beep and “Starting Windows” indication, Press the “F8” key
within 1 second from the beep, select “Command Prompt Only” and
press the “Enter” key.
This will boot the DOS system with out starting the Windows
system. Note this will not work on Windows 98 or Windows NT or
Windows 2000.
CAUTION: The “HLOC” and “HLSC” control parameter values are

determined and set in the qMPRx-D3 program at the factory for
DRT units ordered with (and licensed for) Depth-Tracking
capability. Please, if upgrading from Versions PRIOR V01.40, be
sure to record these values before proceeding with the upgrade
procedure and re-enter them at the conclusion of the procedure. IF
LOST, please contact AlliedSignal Tensor, ask for
repair/maintenance, and request the values of these parameters.
Please have the unit serial number readily available. These steps
are not required for updating systems containing V01.40 or later.
16
Connecting the System Hardware Components
Setup the system as you normally would with the Driller's Remote
Terminal (DRT) configured to the Safe Area Supply Box (SASB),
the Survey Electronics module configured to the Programming
Cable. Connect a PC containing the correct version of qMWD
software to the qBus cable. In this situation the downhole tool
(MPTx), the DRT with the integral qMWD receiver (MPRX) are all
connected to the system and can be communicated with through
qTalk. If you are using a Flow Simulation Box, insure that the
simulated flow control is set to Flow Off.
Loading Software To The qMWD Receiver (MPRx Node 05)
Switch to the C:\qMWD\qMPRx-D3 directory. The data in this file

will be loaded into the processor used for the decoding routines in
the qMWD receiver.
Run qTalk by typing qTalk2 (If the string c:\ qTalk is in your Path in
the Autoexec.bat file, it will boot automatically). Press F4 to invoke
the Host Mode. Press Shift+F5 to interrogate all nodes on the
network. Be sure that at least node MPRx05, responds.
For Versions BEFORE V01.40, record the variables “HLOC” and
“HLSC”. Query the labels and via qTalk and reenter the values
after upgrading the software version.
17
Invoking the Boot! Mode for the qMWD Receiver (MPRx05).
Follow these instructions implicitly!
Run qTalk - qTalk2 (c:\qTalk should be in the path. If it is not go

to the qTalk directory, C:\qTalk\ and type qtalk2.)
Switch To Terminal Mode - Shift+F9
Set the Baud Rate to 9600 - F6 Baud softkey
Switch to Second Menu - F10 Next Menu
Idle the qBus - F5 - Idle! (Depress rapidly 3-4 times, minimum.)
Invoke the Chat Mode - F7 - Chat! At the prompt, enter the Link
address 05. The node selected will return a command prompt.
Invoke Boot Mode - type CCod 11 Boot! <Enter>. If successful,
then the target processor will NOT return a prompt.
Exit qTalk - F1- DO NOT PRESS ANY OTHER KEYS!! Insure
that you are in the directory C:\qMWD\qMPRx-D3, then proceed
to the next step in the instructions.
Load the qMIX/11™ Operating Parameters, Receiver Operating
Parameters, and the qMWD™ Receiver Program – type ProgAll <Enter>
Turn the System Power Off and then On Again
18
Loading Software To The qMWD Driller's Remote
Terminal (DRT Node 09)
Switch to the C:\qMWD\qDRT-3 directory. The data in this file will

be loaded into the processor used for the displaying the various
routines used in the qMWD Driller's Remote Terminal.
Run qTalk by typing qTalk2 (c:\qTalk should b in your path). Press

F4 to invoke the Host Mode. Press Shift+F5 to interrogate all
nodes on the network. Be sure that all of the nodes MPRx05,
MPTx20, and DRT 09 respond. Should one of the nodes not
respond, check all of the connections, and repeat this step.
Invoke the Boot! Mode for the qMWD

Display Processor (DRTx09).
Run qTalk c:\qTalk should be in the path. If it is not go to the qTalk

directory, C:\qTalk\ and type qtalk2.)
Idle the qBus - F5 - Idle! (Depress rapidly 3-4 times.)
Invoke the Chat Mode - F7 - Chat! At the prompt enter the Link
Exit qTalk - F1 DO NOT PRESS ANY OTHER KEYS!! Insure that
you are in the directory C:\qMWD\qDRT-3, then proceed to the next
step in the instructions.
Parameters, and the qMWD™ Receiver Program – type ProgAll
<Enter>
19
Loading Software To The qMWD Transmitter
(MPTx Node 20)
Switch to the C:\qMWD\qMPTx directory. The data in this file will

be loaded into the processor used for the encoding routines in the
qMWD transmitter.

MPTx20 and DRT 09 respond, if they are connected. Should one
of the nodes not respond, check all of the connections and repeat
this step. Note, not all nodes have to be connected to load the
firmware to the targeted node.

Transmitter (MPTx20).

Exit qTalk - F1 DO NOT PRESS ANY OTHER KEYS!!

Insure that you are in the directory C:\qMWD\qMPTx, for the
standard QPN 100080-02 module.
C:\qMWD\qMPTx-2 directory for the new “Mark-2” QPN 100640-01

module.
C:\qMWD\qMPTx-2R directory for the new “Mark-2” QPN 100640-

02 module with recorder memory.
Then proceed to the next step in the instructions.
20
For all Software Versions PRIOR to V01.30
DO N OT USE THE ProgAll BATCH FILE COMMAND FOR
NOT
LOADING THESE FILES TO THE DOWNHOLE TOOL! IT WILL
RESET THE CALIBRATION FACTORS TO DEFAULT VALUES.
CONTINUE WITH THE STEPS BELOW, AS INSTRUCTED.
Load the qMIX/11TM Operating Parameters - type ProgqCtl

<Enter> and follow the instructions.
Select GO,
Then Continue
Load the qMWDTM Transmitter Operating Parameters - type
Progeep<Space>/nb <Enter>. and follow the program instructions
(/nb means no boot). (Note there is a <Space> between Progeep
and /nb.)
Select GO
Load the qMWDTM Transmitter Program - type -
Prog<Space>/nb <Enter> and follow the program instructions.
(Note there is a <Space> between Prog and /nb.)
Select GO.
For all Software Versions V01.30 and later:

<Enter>
Run qTalk by typing qTalk2.
Invoke the Host Mode - F4
Verify No Errors in qDFR and qDWR - Press Shift+F-5. This

procedure will interrogate all nodes on the network for the qMIX
register values. All values for qDFR and qDWR should be returned
as a $0000 hex value.
Check for Control Parameter Value Errors - Press Shift+F-4.

This procedure will cause all nodes to check for valid operating
parameters using the VChk() function (refer to Appendix I). All
nodes should return VChk(All Okay)
NOTE: DO NOT cycle the power or reset the processor as the

“onscreen” directions in the qProg/11 program may instruct
you when using this bootloader method!!!!
21
Loading Software To The Turbine Assembly(Node 27)
Switch to the C:\qMWD\qTCR directory. The data in this file will be

loaded into the processor used for the displaying the various
routines used in the qMWD Turbine Module.

MPTx20, DRT 09 and qTCR27 respond, if they are connected.
Should one of the nodes not respond, check all of the connections
and repeat this step.

Turbine Module (qTCR 27).

Exit qTalk - F1 DO NOT PRESS ANY OTHER KEYS!! Insure that
you are in the directory C:\qMWD\qTCR, then proceed to the next
step in the instructions.
<Enter>
22
g GE Power Systems
Tensor MWD
qDirK_IOTM
SYSTEM UTILITY
This document is an unpublished work. Copyright 1994, 2002 (Revised) GE Power Systems. All rights
reserved. “This document and all information and expression contained herein are the property of GE Power
Systems and is provided to the recipient in confidence on a “need to know” basis. Your use of this document is
strictly limited to a legitimate business purpose requiring the information contained therein. Your use of this
document constitutes acceptance of these terms.”
NOTES
2
Section 08
Version 2.00, February, 2002 08WinQDIRK_GE.DOC
INTRODUCTION
qDirK_IO System Utilities, from now on referred to as qDirK, is the program

used to install the sensor coefficients of the GE Power Systems orientation
module into the GE POWER SYSTEMS processor module used in the
TENSOR MWD probe. The program is a very simple and friendly utility
system to master and use. However, it is EXTREMELY important for the
operator to remember a few CRITICAL features about the methods employed
by GE Power Systems in the design and implementation of downhole tools
and software.
NOTE: AT NO TIME SHOULD ANY DATA BE ALTERED. THE FILES,

PATHS AND STORAGE METHODS WERE DEVISED BY GE Power
Systems FOR COMPATIBILITY TO INSURE VERIFICATION FOR
REPORTING ACCURACY.
The orientation module in the downhole electronics system contains the

accelerometers and magnetometers that are used to measure the tool
orientation. Each set of sensors used in each module must be calibrated to
exact specifications to achieve accuracy and consistency in all
measurements. The coefficients obtained in the calibration process are
unique to that set of sensors and thus each set of sensors constitutes a
unique system that is unlike any other set of sensors in any other module.
Every time an orientation module is calibrated or recalibrated, a record of the
coefficients is made and kept on file for that particular set of sensors.
The GE POWER SYSTEMS orientation module in the directional module,

contains the processor and the power supply module. This system is used to
contain the downhole software programs, in conjunction with the orientation
module, processes all measurements, and dictates the transmission
procedure. The coefficients for the orientation module are resident in the
processor in the module when the two modules are coupled to make a tool.
3
Section 08
Consequently, each directional module, comprised of the orientation module
and the processor/triple power supply module, constitutes a unique system.
You cannot mix-match systems without reprogramming the new system with
the unique set of coefficients. It is recommended that only a highly trained
technician or engineer perform these procedures. Whenever this function is
performed, then this program must be employed to match the two modules.
IT IS ADVISED THAT EACH CLIENT MAKE A BACK UP FLOPPY DISK OF

THE COEFFICIENT DATA. EACH PROBE IS SHIPPED FROM GE POWER
SYSTEMS WITH A FLOPPY DISK INCLUDED. MAKE A COPY OF IT!
STORE THIS DATA IN A SAFE PLACE. WHEN A TOOL IS RETURNED TO
GE POWER SYSTEMS , DESTROY THAT FLOPPY WITH THE OLD
COEFFICIENT DATA TO AVOID EVER CONFUSING IT WITH THE NEW
DISK THAT WILL BE SENT BACK WITH THE RE-CALIBRATED
DIRECTIONAL MODULE AND TO AVOID THE POSSIBILITY OF LOADING
IT INTO THE RE-CALIBRATED DIRECTIONAL MODULE.
Booting the system
Double click on the qDirk icon. This will get the operator into the title page.
This system operates very similar to the Load/Store screen in the qMWDCnfg
file system. A default file is loaded into the file. In this case, the values are
all null. The operator must load from the disk or the processor to obtain any
non-null values. Loading values from the disk will allow the operator to
observe and evaluate data files for particular sensor modules. Loading the
values from the processor will allow the operator to observe and evaluate the
file stored in a downhole processor.
Storing data to disk or to processor will input data to a particular file or

processor. THERE ARE NO ACCESS LIMITATIONS TO THIS PROGRAM!!
Therefore, operators should be EXTREMELY careful when accessing this
program. EXTREME CAUTION is warranted to insure that files are not
copied over or loaded to the wrong processor. As mentioned before the
coefficients are unique to the particular sensor packages coupled with the
particular processor packages. Loading the wrong coefficients into the wrong
processor will render the survey package USELESS. So please use
EXTREME CAUTION when using this program.
Edit Coefficient Information selection will allow the operator to access the
three screens that display the coefficient values. The General coefficient
Information Edit Screen displays the Manufacturer, Part, and Serial Number,
with the date of calibration and other specific data. This data and the data in
the Accelerometer and Magnetometer Coefficient Edit Screens is acquired,
4
Section 08
calculated, and entered in the Calibration Lab in Austin, Texas. THIS DATA
SHOULD NEVER BE ALTERED. Whenever a system is returned to GE
Power Systems for repair or maintenance, the calibration is checked
electronically for compatibility with the latest calibration results for that
particular module. Any alterations to the values are readily obvious.
The Setup Parameters Edit Screen allows the operator to check the file
reading and storage process. If the technician is having difficulty storing or
accessing data, then this screen will allow him to verify the link address and
read/store file paths. Only a technician adequately versed in Windows
should attempt to alter the file paths, and only if they have been corrupted.
Use the displays in this section to verify compatibility. The file names are
created by GE Power Systems and should NEVER be altered. This will
render the calibration file system to become incompatible with the clients
system and not allow any coefficient data to be verified for accuracy.
5
Section 08
Notes
6
Section 08
g GE Power Systems
1840 Royston Lane

(512) 251-4131
(512) 252-6150 (FAX)
MWD Operation Manual
Section 9
Supporting Documentation
MWD Assembly Drawing

Poppet Orifice Setting
Surface System Setup
Tensor MWD Flow Simulation Setup Diagram
MWD Surface Gear
MWD DPT Tracking Surface Gear
Magnetic Spacing Chart
MWD (1.875” OD) Fluid Velocity Chart
SAI
MWD Failure Troubleshooting
MWD Failure Troubleshooting Procedure
No Pulse Flowchart
Pulse but Data not Decoded Flowchart
Remove Tool from Drillstring Flowchart
Pumps and Hydraulic Check Procedure (GEHYD00001)
Remove Tool from Drillstring Procedure (GEPOH0001)
Resynchronization Procedure (GERHY0001)
Work Drill String Procedure (GEWDS0001)
Transducer Procedure (GEXDR001)
g GE Power Systems
Magnetometer location used for Survey Sensor to Bit distance
measurements. 1.60 ft from DownHole End of module.
Pulser Battery 1 Dir. Mod.
Pulser Battery 1 Dir. Mod. Battery 2
Pulser Dir. Mod. Battery 2 Battery 1
981524 Jumper Connector

Replaces Battery 1
Pulser Dir. Mod. Battery 2 Note: Do Not use when using
two batteries.
Pulser Gamma Dir. Mod. Battery 2
Pulser Gamma Dir. Mod. Battery 2 Battery 1
Pulser Dir. Mod. Gamma Battery 2 Battery 1
Gamma Sensor location used for

Gamma Sensor to Bit distance
Pulser Gamma Battery 1 Dir. Mod. measurements. 1.60 ft. from DownHole
End of module.
Poppet Tip Location is EQUAL to the Orientation Bolt

Location on Landing Sub / Mule Shoe Sub.
Tensor MWD Module Position Chart

The Battery Module directly BELOW the Directional Module is ALWAYS Battery 1. The Battery Module directly ABOVE Directional Module is ALWAYS Battery 2.
The Jumper Connector (981524) connects Bus 2 & 3 to send power to the Directional Module – care should be taken when making the connection. These illustrations of module
positions are options. Users must consider magnetic interference and other factors when determining module positions. Measure all Sensor to Bit distances from Poppet Tip
to positions indicated on illustration. These offsets will reference from the Orientation Bolt(s) on the Landing Sub / Mule Shoe Sub.
Page 1
Section 09;Version 2.00; 2February, 2002
Pulser Battery I
Pulser Battery I
Pulser Battery I Directional Module
Tensor MWD ASSEMBLY/BUILD PROCEDURE

The UpHole end of a connected intermodule (centralizer) has exposed pins, which can cause failures if shorted to each other. Therefore,
always install the intermodule (centralizer) into the BOTTOM of the unit above (UpHole), before stabbing it into the unit below (DownHole) it.
See sequence illustrated above. Use this procedure for the expanded module probes also.
Page 2
Section 09;Version 2.00; 2February, 2002
Poppet Orifice Settings
4 3/4" & 6 1/2" Mule Shoe Poppet/Orifice Configurations

Main
Orifice Poppet Flow Area
I.D. Part No. End O.D. Part No. [in2] Flow Ranges [GPM]
1.28 981068 1.122 981140 0.297 Below 250
1.28 1.086 981213 0.360 200-375
1.28 1.040 981214 0.437 300-500
1.35 981067 1.122 981140 0.443 225-475

1.35 1.086 981213 0.505 350-550
1.35 1.040 981214 0.582 475-600
1.40 981066 1.122 981140 0.550 350-575

1.40 1.086 981213 0.612 450-650
1.40 1.040 981214 0.690 475-700
1.50 981051 1.122 981140 0.778 475-750

1.50 1.086 981213 0.840 500-800
1.50 1.040 981214 0.918 Over 700
1.55 981059 1.122 981140 0.898

1.55 1.086 981213 0.961
1.55 1.040 981214 1.037
1.60 981060 1.122 981140 1.022

1.60 1.086 981213 1.084
1.60 1.040 981214 1.161
3 1/2 " Mule Shoe Poppet/Orifice Configurations

Main
Orifice Poppet Flow Area
I.D. Part No. End O.D. Part No. [in2] Flow Ranges [GPM]
1.20 981967 1.122 981140 0.1423 50-100
1.20 1.086 981213 0.2047 75-120
1.20 1.040 981214 0.2815 100-150
1.23 981966 1.122 981140 0.1995 60-110

1.23 1.086 981213 0.2619 80-120
1.23 1.040 981214 0.3387
1.25 981961 1.122 981140 0.2383 80-130

1.25 1.086 981213 0.3007
1.25 1.040 981214 0.3775
NOTE: All power must originate from the same outlet.
Monitor
Pwr This will insure a common ground connection for the system.
Strip
UPS Hazardous
Printer
Refer to QSI drawing SY-100522-01
SAFE Area
AREA
Pwr
Strip
Personal
Computer
DRT
UPS 384022
250FT.
384023/100FT. 384023/100FT.
A/C (MAIN.)
(Optional) (Optional)
Source
Pwr
Strip SASB Cable SASB Cable R/T Ends-->
SH SH SH
<-- Ends
384023/100FT. 384023/100FT. 384022

(Optional) (Optional) 250FT. Transducer
(MAIN.) Cable
Earth
Ground
xducr
SH = Indicates Shield is terminated at connector

A UPS MUST be used at all times for the SASB power!
NOTE: RT End of 384022 is
The use of two UPS’s is an option, not a requirement, one will suffice.
not connected to the Shield.
Version 2.00; February, 2002

DRT Pressure Sensor
Connected to Rig StandPipe for mud pulse detection.
0 - 10K PSI range, 4 - 20 mAmp
Node 05
R/T
TO SASB END
Node 09 DOWNHole Direction
Hook Load
Connected to hydraulic system to measure
Cable
hookload from dead-line. Located at the dead-
384022
250’
line anchor, drillers panel, or GeolographTM
Required recorder. 0 -2K PSI range.
Depth Encoder Anchor Point

To be attached to the Geolograph Line that is to rig
connected to the Kelly to measure drilling
activity.
Junction Box Assembly
Version 1.00; 01 February, 2001

Hydraulic
Quick
Disconnects
0-2000 PSI, 4-20 mA rated

Druck Hookload
transducer
Place in-line with hydraulic hose connecting deadline anchor to hook- Hydraulic
load indicator on driller’s panel. These hoses can be located at the Quick
anchor, or at the Geolograph recorder or in the driller’s panel. Consult Disconnect
with rig personnel before attaching this device.
Anchor Point to Rig
(Can use extension)
Downhole Direction
Attach to Geolograph Line threaded as shown

around the idler pulleys at the top and the bottom
and around the main measuring wheel. The wing-nuts
on the idler pulleys can be loosened to allow the
guide plate to be rotated allowing the cable to be
threaded around the pulleys. Insure that the sensor
is securely anchored to the rig structure at the securing
points to keep the sensor in place and prevent it from
Comm. riding up and down as the line feeds through.
Cable
Anchor Point to Rig

(Can use extension)
Apply Teflon tape to all 2”NPT threaded connections
connect nipple to standpipe and connect receiver
section of Hammer Union to nipple. Inspect for o-ring
and slide blue hammer union section over transducer
and place in the receiver section of the hammer union.
thread the blue section to the receiver section until
snug and hammer tighten onto receiver section of hammer
union.
2”NPT thread welded

Connection (female)
15-2 Hammer Union
Standpipe
Mud Flow
2”NPT thread heavy

wall Nipple (15K PSI)
male-male
Ground
Tensor MWD Flow Simulation Setup Diagram
Node 09
DRT
S.A.P.S
S.A.P.S
384023 Cable P/N

Node 05
qNIC
Directional Module
Tool qBus Flow
Windows PC
Power
QDT MWD
Flow
Simulator
Node(s) 20
(& 21w/DGS)
Version 2.00; February, 2002

8 7 6 5 4 3 2 1
REVISIONS
SAFE AREA HAZARDOUS AREA ZONE REV
A
DESCRIPTION
INITIAL RELEASE
DATE
(ECN950012) 27MAR95
APPRVD
HSM
POWER B
C
384027 WAS 384009
ADDED QPNs
(ECN960011) 23FEB96
(ECN960056) 18NOV96
HSM
HSM
D REVISIONS (ECN970024) 09JUL97 HSM
P/N 384016
D P/N 384021 D
REMOTE
TERMINAL
OFF | ON
POWER
90-250 VAC, 45-65 HZ
ENSURE THAT
GROUNDING STUD
IS SECURELY
BONDED TO RIG
SH
STRUCTURE
CONTAINS
INTRINSICALLY SAFE
CIRCUITS SH
SH
REMOTE TERMINAL
TOOL
PROGRAMMING
qBUS qBUS
CONNECT TO SAFE AREA EQUIPMENT ONLY SH
SH SH
SAFE AREA POWER SUPPLY
PRESSURE
TRANSMITTER
SH SH
C P/N 384023 P/N 384022 P/N 384024 C
P/N 384017
SH SH
P/N 384023 P/N 384022
P/N 384008
PC
P/N 384025
B B
SH INDICATES THAT THE SHIELD IS

TERMINATED AT THIS POINT.
P/N 384008
CARE SHOULD BE TAKEN IN THE

PC ORIENTATION OF CABLE P/N
384022
CABLE, PROGRAM,
qMWD, TOP
P/N 983130
P/N 384027 MINIMUM UNLESSOTHERWISESPECIFIED, CONTRACTNO.

DIMENSIONSAREININCHES.
Tensor MWD ELECTRONICS ASSEMBLY A

TOLERANCESARE:
A APPROVALS DATE
DRAWN
HSM 23MAR95 MWD SURFACE SYSTEM
MATERIAL CHECKED CABLING DIAGRAM
Tensor MWD ELECTRONICS CARTRIDGE
FINISH ISSUED SIZEFSCM.NO.DWG.NO.
SY-100521-01 D
COPYRIGHT(C) 1995-2002 GE Power Systems ALL RIGHTS RESERVED DONOTSCALEDRAWING SCALE SHEET
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
REVISIONS
SAFE AREA HAZARDOUS AREA ZONE REV
A
DESCRIPTION
INITIAL RELEASE
DATE
(ECN950012) 27MAR95
APPRVD
HSM
POWER B
C
CHANGED CABLES
ADDED QPNs
(ECN960011) 23FEB96
(ECN960056) 18NOV96
HSM
HSM
D REVISIONS (ECN970024) 09JUL97 HSM
P/N 384029
D P/N 384021 MUD PRESSURE TRANSMITTER D
P/N 384031
REMOTE
TERMINAL
OFF | ON
POWER
90-250 VAC, 45-65 HZ
ENSURE THAT
GROUNDING STUD
IS SECURELY
BONDED TO RIG OR
SH
STRUCTURE
CONTAINS
INTRINSICALLY SAFE
CIRCUITS
SH
REMOTE TERMINAL
TOOL
PROGRAMMING
XO CABLE MUD PRESSURE TRANSMITTER
P/N 384017
qBUS qBUS
CONNECT TO SAFE AREA EQUIPMENT ONLY
P/N 384037
SH
SAFE AREA POWER SUPPLY
HOOK LOAD TRANSMITTER

P/N 384032
SH SH
C P/N 384022 C
P/N 384023
P/N 384036
DEPTH ENCODER
P/N 384023 P/N 384022
QDT P/N 384036

P/N 384033
SH SH
P/N TBD
PC
P/N 384008 RIG HEAVE
P/N 384025
SENSOR
JUNCTION BOX
P/N 384035
B B
P/N 384034
PC SECONDARY COMPENSATION
P/N 384008 POWERINPUT
90-250 VAC, 45-65 Hz PUMP STROKES #1
PUMP STROKES #2
GENERIC SENSOR #1
GENERIC SENSOR #2
P/N 384039
PC
GENERIC SENSOR #3
CABLE, PROGRAM,
P/N 384008
QUANTUM SOLUTIONS, INC.
SANTA CLARA, CALIFORNIA
qBUS EXPANSIONBOX
QPN 100500-01
MADE IN U.S.A.
ALLSENSOR CABLE SHIELDS ARE CARRIED THROUGH CORES. ALL
CONNECTOR SHELLS USED IN SENSOR WIRING ARE FLOATING.
qMWD, TOP
P/N 384027 MINIMUM CONTRACTNO.
SH INDICATES THAT THE SHIELD IS

UNLESSOTHERWISESPECIFIED,
DIMENSIONSAREININCHES. QUANTUMSOLUTIONS,INC.
A
TOLERANCESARE:
SANTACLARA,CALIFORNIA
A MWD ELECTRONICS ASSEMBLY TERMINATED AT THIS POINT. APPROVALS DATE
MWD SURFACE SYSTEM
CARE SHOULD BE TAKEN IN THE DRAWN
HSM 23MAR95 CABLING DIAGRAM
MWD ELECTRONICS CARTRIDGE ORIENTATION OF CABLE P/N MATERIAL CHECKED
WITH DEPTH TRACKING
384022 FINISH ISSUED SIZEFSCM.NO.DWG.NO.
SY-100522-01 D
COPYRIGHT(C) 1995-2002 GEPower Systems ALL RIGHTS RESERVED DONOTSCALEDRAWING SCALE SHEET
8 7 6 5 4 3 2 1
g Power Systems
Magnetic Spacing Chart
Angular Difference From Magnetic North or South
5° 10° 15° 20° 25° 30° 35° 40° 45° 50° 55° 60° 65° 70° 75° 80° 85° 90°
Above Sensor 4 6 8 9 10 10 11 12 12 13 13 14 14 14 14 15 15 15
5° 5°
Below Sensor 3 4 4 5 6 7 7 7 8 8 8 9 9 9 10 10 10 11
6 9 11 12 13 15 16 17 17 18 19 19 20 20 20 21 21 21
10° 10°
4 5 6 8 9 9 10 10 11 12 12 12 12 13 13 13 13 13
8 11 13 15 16 18 19 20 21 22 23 23 24 24 25 25 25 25
15° 15°
4 6 8 9 11 11 12 13 14 14 14 15 15 15 16 16 16 16
9 12 15 17 19 21 22 23 24 25 26 27 28 28 29 29 29 29
20° 20°
I 5 8 9 11 12 12 14 15 16 16 17 17 17 17 17 18 18 18 I
N 10 13 16 19 21 23 24 26 27 28 29 30 31 31 32 32 32 32 N
25° 25°
C 6 9 11 12 13 14 16 16 17 18 19 19 19 20 20 20 20 21 C
L 10 15 18 21 23 25 27 28 29 31 32 33 33 34 34 35 35 35 L
30° 30°
I 7 9 11 12 14 15 16 18 19 19 20 20 21 21 22 22 22 22 I
N 11 16 19 22 24 27 28 30 32 33 34 35 36 36 37 37 37 37 N
35° 35°
A 7 10 12 14 16 16 18 19 20 21 21 22 22 23 23 24 24 25 A
T 12 17 20 23 26 28 30 32 33 35 36 37 38 39 39 39 40 40 T
I 40° 40° I
7 10 13 15 16 18 19 20 22 22 23 23 24 24 25 25 25 26
O 12 17 21 24 27 29 32 33 35 37 38 39 40 40 41 41 42 42 O
45° 45°
N 8 11 14 16 17 19 20 22 22 23 24 24 25 26 26 26 26 27 N
13 18 22 25 28 31 33 35 37 38 39 40 41 42 43 43 43 44
50° 50°
O 8 12 14 16 18 19 21 22 23 24 25 26 26 27 27 27 28 28 O
F 13 19 23 26 29 32 34 36 38 39 41 42 43 44 44 45 45 45 F
55° 55°
9 12 14 17 19 20 21 23 24 25 25 26 27 27 28 28 28 29
W 14 19 23 27 30 33 35 37 39 40 42 43 44 45 45 46 46 46 W
60° 60°
E 9 12 15 17 19 20 22 23 24 26 26 27 28 28 29 29 29 30 E
L 14 20 24 28 31 33 36 38 40 41 43 44 45 46 46 47 47 48 L
65° 65°
L 9 12 15 17 19 21 22 24 25 26 27 28 28 29 29 29 30 30 L
14 20 24 28 31 34 36 39 40 42 44 45 46 47 47 48 48 48
70° 70°
B 9 13 16 18 20 21 23 24 26 27 27 28 29 29 30 30 30 31 B
O 14 20 25 29 32 34 37 39 41 43 44 45 46 47 48 48 49 49 O
75° 75°
R 9 13 16 18 20 22 23 25 26 27 28 29 30 30 30 30 31 31 R
E 15 21 25 29 32 35 37 39 41 43 45 46 47 48 48 49 49 49 E
80° 80°
9 13 16 18 20 22 24 25 27 27 28 29 29 30 31 31 31 31
15 21 25 29 32 35 37 40 42 43 45 46 47 48 49 49 49 50
85° 85°
9 13 16 18 20 22 24 25 26 28 28 29 30 30 31 31 31 31
Above Sensor 15 21 25 29 32 35 38 40 42 43 44 46 47 48 49 49 50 51
90° 90°
Below Sensor 9 13 16 18 21 22 24 25 26 28 28 29 30 30 31 31 32 32
5° 10° 15° 20° 25° 30° 35° 40° 45° 50° 55° 60° 65° 70° 75° 80° 85° 90°
Angular Difference From Magnetic North or South
Top number (shaded) in each row is required footage of non- magnetic material above directional sensors. Lower number (unshaded)
in each row is footage below sensor positon.
50
MWD (1.875" OD) Fluid Velocity Chart - 40 ft/sec MAX
ID=2.25" ID=2.50" ID=2.75" ID=3.00" ID=3.25" ID=3.50" ID=3.75" ID=4.00"
40
Velocity in Feet/Second
30
20
10
0
50
0
00
50
00
50
00
10
15
20
25
30
35
40
45
50
55
60
65
70
75
80
85
90
95
10
10
11
11
12
Gallons/Minute
Fluid Velosity Chart GE Power Systems Confidential Page 1

g GE Energy
Technical Notice 83 Page 1 of 1

MWD Failure Troubleshooting
Procedures
The steps below are for a reference for MWD field troubleshooting. Remain calm
and use proper judgment while resolving a failure. Maintain contact with your
MWD department managers/coordinators and directional driller for assistance
while trying to troubleshoot.
Operator experience is the most valuable tool when troubleshooting complex

systems. The following material, informed by experience and general best
practices, supplements knowledge the operator may already posses.
The first series of troubleshooting materials concentrates on the most commonly

experienced problems with the Tensor MWD system. It is broken down into two
scenarios.
Scenario 1 deals with a situation in which no pulses are present.
Scenario 2 covers a situation in which pulses are present but cannot be

decoded.
Troubleshooting takes place in four areas labeled Area A through D.
Area A: Troubleshooting procedures that the operator can accomplish inside the
unit.
Area B: Procedures that must be accomplished outside the unit either on the
drill floor, mud pits or around the pumps.
Area C: This Area encompasses any actions that involve the down hole tool
such as working the drill string or cycling the pumps.
Area D: Procedures at this Area are those performed while the Bottom Hole
Assembly and / or the tool are at the surface.
Follow the listed procedures in the order in which they are presented. If pulsing
returns to normal, discontinue troubleshooting and try to determine if the problem
is intermittent, aberrant or symptomatic of another system failing.
CONFIDENTIAL Page 1 of 5
MWD Scenario 1: No Pulse
1.1. Determine if pulse is updating on the qMWD-PC Pulse Waveform

data Window. Check to make sure that the computer has not
locked up if the screen is not updating.
1.2. Is qMWDPC showing standpipe pressure on the screen? Make

sure that the program or the computer has not locked up if the
standpipe pressure is not showing on the qMWDPC program
display.
1.3. Ensure that down hole temperature has not exceeded operating
limits of the MWD. Normal operating limit is 150° C with High
Temperature tools capable of performing to 175° C. Remove the
tool from the drill string if normal operating limits are violated.
1.4. Ensure down hole tool vibration has not exceeded operating limits
of the MWD. Remove the tool from the drill string if normal
operating limits are violated.
1.5. Determine if it is possible to see pulses on the standpipe pressure

gauge. Pressure fluctuations at the same time period of the pulse
window indicate that the tool is pulsing. If the pressure does not
fluctuate, the tool may have stopped pulsing due to operating
conditions.
1.6. If pulses are still absent vary pump rate in attempt to recover
pulses. Be sure to try flow rates with one pump only, two pumps,
and the pump not in use when the tool failed.
1.7. Pumps and Hydraulic Check Procedure (GEHYD00001)
1.7.1. Is the mud aerated?
1.7.2. Is there a high level of solids?
1.7.3. Is the suction screen or pipe screen plugged?
1.7.4. Is LCM being mixed properly?
1.7.5. Is the mixing pump turned on?
1.7.6. Is there air or foam apparent in the mud tanks?
1.7.7. Is pulsation dampener pressure set to 1/3 of standpipe
pressure?
1.8. Circulate off bottom and pump a sweep with a water pill or high
viscosity pill if possible in order to remove solids that may be
plugging off the MWD.
1.9. Work Drill String Procedure (GEWDS0001)
If it is possible that the MWD tool has become unseated out of the
Muleshoe, pick off bottom (with pumps off) enough so that the drill
string can be run in quickly and then stopped suddenly without
hitting bottom at the same time you can also rotate the drill string.
Turn the pumps on to see if the tool has seated properly and pulses
are regained. You may need to repeat this process a few times to
successfully seat.
1.10. Resynchronization Procedure (GERSY0001)
Try to resynchronize the tool with the surface system.
1.11. Remove Tool From Drillstring. (GEPOH0001)
If you must trip out of the hole be sure to check for any signs of
washout during the trip.
Once on surface, completely inspect Muleshoe and float valve for

normal condition and operation. Replace if necessary. Check that
the Signal Shaft is free and operates smoothly.
Check that there is enough clearance below the MWD Muleshoe to

allow laminar flow. Typically, 3 feet of unobstructed flow should be
below the Muleshoe.
Perform shallow hole test. If successful continue in hole to bottom.
MWD Scenario 2: Pulse Is Present Data Not Decoded
2.1. Determine if pulse is updating on the qMWD-PC Pulse Waveform
Window.
2.2. If the problem persists check the following items.
2.3. Check that the quality and confidence levels are good. Generally,
they should be greater than 70% for Quality and 80% for
Confidence.
2.4. Make sure that the HiPL and LoPL (High Pulse threshold and Low
Pulse Threshold) values are correct. The best practice is to set the
LoPL value above the noise. HiPL should be set higher than the
pulse can possibly attain but lower than a torque wave created by
stalling the mud motor.
2.5. Make sure that the Fbwf (Final Band Width Filter) filter is set
properly. It should be set to a minimum and maximum of 60% at
the high or low end of the pulse window.
2.6. Is down link enabled?
2.7. If down link is enabled perform the Mode Switch Tool and Receiver
Procedure (GE Tensor Operations Manual, PN 9810004, “Downlink
Controls and Procedures)”.
Down link tool to the same mode as the surface receiver if unable
to decode pulses.
If you are getting small pulses and cannot increase the flow rate,
down link the tool to a wider pulse width.
2.8. Cycle power to the receiver. If the problem persists then continue
troubleshooting.
2.9. Change out the Safe Area Interface or Safe Area Power Supply.
2.10. If data still cannot be decoded inspect and clean cable

connections.
2.11. Inspect cables for damage. Replace if necessary.
2.12. Check the Transducer Procedure (GEXDR0001)
2.13. Perform Pumps and Hydraulics system check (GEHYD0001)
2.14. Remove tool from drillstring. (GEPOH0001)
If you must trip out of the hole be sure to check for any signs of
washout during the trip.
Once on surface, completely inspect Muleshoe and float valve for

normal condition and operation. Replace if necessary. Check that
the Signal Shaft is free and operates smoothly.
Check that there is enough clearance below the MWD Muleshoe to

allow laminar flow. Typically, 3 feet of unobstructed flow should be
below the Muleshoe.
Perform shallow hole test. If successful continue in hole to bottom.
g GE Power Systems
1840 Royston Lane

(512) 251-4131
(512) 252-6150 (FAX)
g GE Power Systems
g GE Power Systems
1840 Royston Lane

(512) 251-4131
(512) 252-6150 (FAX)
Procedure GEHYD0001
Procedure to Inspect the Hydraulic System
If any parameter is incorrect notify the person in charge. Do not hesitate to

recommend a change of procedure, process or quality if necessary.
1. Is Standpipe pressure consistent? If not there are a number of things

that can cause the pressure to be inconsistent. Consider the following
as possible reasons why the pressure is not constant.
2. Air or foam in the mud system. Introduction of air into the mud system
will distort pulses to the point that they become undetectable. Check
the mud pits for foaming or bubbling. If present inform the person in
charge.
3. Check pipe screens for solids. Pipe screens, as well as in line screens
for the pumps, when packed with solids will distort pulses or even
prevent pulses from appearing on the standpipe or Pulse Waveform
data screen. Make sure that these screens are clean and free of
debris.
4. Pulsation dampers set to the wrong setting will cause pulses to
become distorted or make pulses disappear. Normal setting for
pulsation dampers is one third of system pressure. Make sure the
pulsation dampers are set correctly.
5. During the drilling process monitor the procedures and quantities with
which Lost Circulation Material (LCM) is mixed. The LCM should be
well mixed in the system and does not exceed GE Tensor
recommendations. (Refer to Tensor MWD Operating Specifications).
The mixing pump should be on and all material mixed thoroughly.
Procedure GERSY0001
Procedure to Resynchronize the down hole tool with the surface receiver
The procedure listed below is only one method of obtaining a resynchronization

between the down hole tool and the surface receiver. It is, however, the most
certain method.
1. Remove the drill string from bottom

2. Shut down the mud pumps.
3. Wait at least one minute without moving the drill string.
4. Rapidly bring up the mud pumps until correct operating pressure is
obtained.
5. Check for synchronization pulses for at least five (5) minutes.
6. If synchronization pulses are absent as well as other pulses, continue
trouble shooting with Trouble Shooting Chart Scenario A, Level 3.
7. If pulses are present but it is impossible to decode data, continue
trouble shooting with Trouble Shooting Chart Scenario B.
Procedure GEWDS0001
Procedure to Work the Drill String
Working the drill string as recommended should only be carried out in

consultation with the person in charge. Be absolutely certain to follow all
necessary precautions to prevent the drill string from abruptly returning to
bottom.
1. Pick up off bottom 7- 10 meters (20 – 30 feet).

2. Open Kill line
3. Vigorously work pipe up and down. Do not allow the bit to collide with
the bottom of the hole.
A. If pulses are absent: check the Pulse Waveform data screen while
working the pipe. Moving the drill string should create pseudo pulses on the
Pulse Waveform data screen. If pseudo pulses appear the transducer and
transducer cable should be good. If normal pulsing does not return continue
to B.
B. Tool may be unseated: Perform steps 1 – 3 above.
4. Rotate at a minimum of 60 RPM

5. Return to step 1 and repeat this procedure several times.
6. Rapidly bring up the pumps and check for a pulse for at least five
minutes.
C. Pulses are still absent: return to the troubleshooting chart.

Procedure GEXDR0001
Procedure to check the Pressure Transducer
Checking the pressure transducer on the standpipe is an important

troubleshooting procedure, because it is the primary means by which the
mechanical pressure pulse is transformed into an electrical signal.
1. Remove pressure transducer from standpipe

2. Check to determine if the diaphragm is damaged.
Check the
diaphragm for
damage. If it is cut
or dented change
out the transducer
3. Make sure that the diaphragm area is clear of debris such as mud,
LCM and, in cold climates, ice. Also check the area inside the
transducer mounting area on the standpipe and make sure this area is
also free of debris. If debris is present, thoroughly clean the area.
4. Replace the standpipe pressure transducer and bring the pumps up to
normal operating range.
5. If a pressure signal is now present on the Driller’s Remote Terminal or
the Pulse Waveform data screen, make sure that the pulses are being
detected. If not, continue trouble shooting on Trouble Shooting Chart
Scenario B.
6. If pulses are not present continue trouble shooting on Trouble Shooting
Chart Scenario A.
g GE Power Systems
Notes:
g GE Power Systems
Tensor MWD
Battery Manual
GE Power Systems supplies this manual for information and
insight to our clients on safe handling and transportation of
Lithium battery products. This manual contains information
supplied by battery and battery pack manufacturers and
suppliers. The information contained within is easily obtained
via the Internet or by contacting the Battery Suppliers listed in
the front of the manual.
GE Power Systems obtained permission from the companies

listed in this manual to print the data from the Internet and
place in this manual for our clients’ convenience. The manual
is not intended as an advertisement for the vendors and
suppliers mentioned herein, but to give basic information on
Lithium batteries.
Tensor MWD clients are urged to acquire as much information

from the manufacturers pertaining to the Lithium batteries and
battery packs employed in their fleet of MWD systems.
http://www.spectrumbatteries.com/supp2.htm
http://www.spectrumbatteries.com/Prod_in/chart.htm
http://www.batteryeng.com/safety.htm
http://www.spectrumbatteries.com/Prod_in/passivation_information.htm
http://www.batteryeng.com/func_perf.htm
2 Section 10
Version 2.00; February, 2002; BattM
PLEASE NOTE AND READ – THE ABOVE HYPERLINKS.
These hyperlinks can be used to access more detailed data

about battery manufacturers and battery pack assembly
companies. We encourage clients to gain as much information
regarding batteries and the handling procedures as possible.
Battery Engineering and Electrochem are now the same

company, but the web sites do still work. Electrochem has
purchased Battery Engineering.
This manual was assembled using the Yardney safety

instructions from the Website. Yardney no longer
manufactures Lithium Thionyl battery s. They did however
supply this common data for Lithium battery safety prior to
divesting the lithium battery manufacturing process. It was
edited for format only to make it more readable and
understandable. Please read and follow all safety precautions
in the manual. Refer to the above Websites for information on
battery power and depletion tables and calculators.
Section 10 3
SAFE STORAGE AND HANDLING
In most cases, improper handling and storage,
resulting in such problems as overheating and
short-circuiting cause damage to batteries. The
common safety practices have been outlined below;
safety precautions to take with regard to all aspects
of battery storage and handling.
Storage
1. Shelf
Batteries should be stored in their original shipping boxes, if
possible, to keep them isolated from each other, preventing
external short circuits. Do not store batteries loosely, and do not
place batteries on metal surfaces.
2. Temperatures and Environment

Batteries should be stored in a cool, dry, well-ventilated area with
an optimal storage temperature range of 0-25 C. If prolonged
storage is anticipated, batteries should be protected against
excessive humidity. This will prevent moisture from forming an
electrical pathway between the feed-through terminal and battery
cover, which can lead to severe galvanic corrosion of the feed-
through pin, thus compromising the hermeticity of the battery.
3. Hazard Consideration
Lithium battery storage areas should be clearly marked and
provided with “Lith-X” fire extinguishing material. Batteries might
burst if subjected to excessive heating. In case of fire, only “Lith-
X” fire extinguisher should be used, as water will cause exposed
lithium to ignite. Signs should clearly state - WATER IS NOT TO
BE USED IN CASE OF FIRE.
4 Section 10
INCOMING INSPECTION
The proposed flow of batteries throughout the facility should be

thoroughly reviewed by plant safety personnel to identify and
eliminate potential sources of electrical and physical damage to
the batteries. Conditions that can short circuit, recharge, over-
discharge, puncture, crush, or overheat the batteries must be
avoided, and all personnel involved in the handling should be
properly trained.
1. Testing
Physical dimensioning should be performed with all-plastic
calipers, and no electrical tests other than open circuit voltage
checks should be performed without first consulting the battery
manufacturer. Short circuit and load tests can degrade battery
performance. If batteries are to be tested at elevated
temperatures, the test chambers must have over-temperature
protection.
Note: Abuse testing should not be performed

without first consulting the battery
manufacturer.
Section 10 5
SAFE TRANSPORTATION
All lithium/thionyl chloride batteries with a lithium content of

greater than 0.5 grams are restricted and they are subject to
DOT (49 CFR 172.101) and International Air Transport
Association (IATA) shipping regulations. Those batteries that
contain less than 0.5 grams of lithium are unrestricted, and they
can be shipped by any means (ref. U.S. DOT 173.185(I) and
IATA section 4.5.A45). Because the shipping regulations are
very complex, shippers of lithium batteries are urged to obtain
copies of the 49 CFR (DOT regulations) and IATA regulations.
These regulations also explain how the paperwork is to be filled
out. This brochure will not attempt to explain paperwork because
every carrier has different requirements.
1. U.S. DOT
The proper shipping name is LITHIUM BATTERY, 9 (UN3090),

PG II. The Regulations State that the batteries must be
separated to prevent external short circuits, and they must be
packed in inner fiberboard containers (no more than 500 grams
of lithium per inner container). The inner containers can then be
packed with at least one inch of non-combustible packing
material (such as vermiculite) separating each inner package in
4G fiberboard boxes, 1A2 or 1B2 steel drums, 1G fiber drums, or
4C1, 4C2, 4D, 4F wooden boxes.
Motor freight, rail freight, water, or Cargo Aircraft can ship the
batteries only. Restricted batteries cannot be carried aboard
passenger-carrying aircraft. Boxes must be labeled
MISANEOUS (CLASS 9). If the batteries are to be shipped by
air, then the package has to have a CARGO AIRCRAFT ONLY
label, also known as DANGER LABEL attached. Boxes must be
marked with the proper shipping name and the UN number near
the shipping labels.
6 Section 10
2. INTERNATIONAL AIR TRANSPORT ASSOCIATION (IATA)
IATA regulations are very similar to the DOT regulations

except for paperwork and packaging. Packaging for IATA
shipments has to be performance tested before the
packages are used for shipping. These packages have to be
marked with a United Nations Marking Symbol (section 6.0 of
IATA shipping regulations).
Section 10 7
SAFE DISPOSAL
Lithium/thionyl chloride batteries must be disposed of

properly in accordance with 40 CFR PARTS 261 & 262.
Lithium batteries for disposal are classified as Waste
Lithium Batteries, 9, UN3090, II for shipping purposes,
and they have an EPA waste disposal code of D003 and
D001.
The products of lithium/thionyl chloride battery

deactivation are not toxic (non-hazardous), once
neutralized. Lithium/thionyl chloride batteries should be
disposed of by an EPA permitted treatment, storage, and
disposal facility. Because each state and country have
different disposal regulations, contact your local
environmental agency for instructions on how to properly
manage and dispose of waste lithium batteries.
EMERGENCY CONDITIONS
Because of the high energy density inherent in
lithium/thionyl chloride batteries, the potential for
hazardous situations does exist. Most hazards are
due to internal or external heating of a hermetically
sealed battery. Overheating causes liquid
electrolyte to expand, increasing hydrostatic
pressure inside the can. This might cause the
battery to burst. Further heating can cause the
lithium anode to melt, which, in turn, will react
spontaneously with the electrolyte and bring about a
violent reaction of the battery.
8 Section 10
CAUSES OF HAZARDOUS CONDITIONS - ELECTRICAL AND
PHYSICAL
Hazardous electrical conditions include recharging, short-

circuiting, and forced discharging (voltage reversal).
Hazardous physical conditions include external heating due

to uncontrolled storage, incineration, and physical
destruction of the battery case via crushing, puncturing, and
disassembly. Excessive heating can cause violent behavior
with any type of battery. Physical destruction can result in
leakage of toxic and highly corrosive electrolyte.
Section 10 9
EMERGENCY PROCEDURES
OSHA Safety Regulations must be followed, at all

times, the OSHA regulatory references are found in
29 CFR PART 1910. In the unlikely event of violent
battery behavior, the area should be evacuated
immediately. Unless they are wearing personal
protection devices, all workers should stay away
from the area for at least 15 minutes rather than
trying to correct the situation. Burning or fuming
batteries should be left isolated until expert handling
can correct the condition. Lithium fires should
never be extinguished with equipment other than
that which is designed for lithium fires (i.e., “Lith-X”).
In case of leakage, leaking batteries should be

isolated from all personnel and equipment. Since
electrolyte can be neutralized with common baking soda,
leaking batteries should be placed in sealed plastic bags
containing baking soda. The bags should be placed in a
sealed and labeled drum. Vermiculite should be used to
cushion the batteries.
Note: Personal protective equipment should always

be used around leaking batteries
10 Section 10
SAFETY EQUIPMENT AND MATERIALS
Common personal protective equipment and material that should

be available in the event of a lithium thionyl chloride battery
being involved in an incident such as a crush, puncture, or fire is
as follows:
Rubber Gloves Fisher Scientific #11-394-23A or equal
Rubber Boots Uniroyal Steel Shank Rubber Boot or
equal
Respirator MSA 4571000 Al Front Mounted Gas Mask
Complete with Canister #84494 GMB
Acid Gasses and Carrying Case #84494
Acid Gas Canister or equal
Lab Apron Lab Safety Supply #R3003 or equal
Neutralization Materials 10 lbs. Industrial Grade Sodium
Bicarbonate (Baking Soda or Soda Ash)
Extinguishing Materials 45 lbs., Lith-X Graphite Powder for
extinguishing Class D fires
Section 10 11
LITHIUM BATTERY SAFETY MANUAL
APPENDIX: HANDLING OF LITHIUM THIONYL CHLORIDE

BATTERIES UNDER ABNORMAL CONDITIONS.
The following paragraphs will discuss the safe handling of
Lithium Thionyl Chloride (LTC) batteries under the abnormal
hazardous conditions of:
1. Leaking or venting batteries,
2. Hot batteries,
3. Exploding batteries,
4. Lithium fires.
Personnel Protective Equipment Required:
Safety Glasses, Rubber Gloves, Helmet with full face
shield, Flak Jacket with gloves, Riot Shield, Respirator
with canisters for Acid Gases or full-face respirator with
acid gas cartridges.
Other Equipment Required:
Infrared Temperature Probe, Sodium Carbonate (Soda
Lime) or Sodium Bicarbonate (Baking Soda), Vermiculite,
Fire Extinguisher containing Lith-X Graphite powder,
extended Non-conductive pliers or tongs, Thermal
resistant gloves (welding gloves).
PROCEDURE FOR LEAKING OR VENTED BATTERIES
Leaking or vented batteries should be isolated from personnel and

equipment. If possible, the area should be vented to the outside.
Prior to handling, the temperature of the batteries should be checked
with a remote-sensing device such as an infrared temperature probe.
If the batteries are at ambient temperature, they should be handled
with rubber gloves or non-conductive pliers or tongs and placed in
plastic bags containing Sodium Carbonate. Spilled electrolyte should
be absorbed with Sodium Carbonate and placed in plastic bags. All
bags should be placed in a sealed and labeled drum with Vermiculite
or other non-flammable cushioning material such as sand or Sodium
Carbonate to cushion the batteries. These materials should be
disposed as previously discussed under Safe Disposal in the Lithium
Battery Safety Manual.
12 Section 10
PROCEDURE FOR HOT BATTERIES
As soon as a hot battery is detected, all personnel should be

evacuated from the area. The temperature of the battery
should be monitored with a remote-sensing device such as an
infrared temperature probe. The area should remain evacuated
until the battery has cooled to ambient temperature. When the
battery has returned to ambient temperature, it can be handled
by an operator wearing protective equipment (face shield, flak
jacket and gloves) with non-conductive pliers or tongs. The
batteries should be placed in plastic bags containing Sodium
Carbonate and then placed in labeled drums containing
Vermiculite or other non-flammable cushioning material such as
sand or Sodium Carbonate. These materials should be
disposed of as previously discussed under Safe Disposal in
the Lithium Battery Safety Manual.
OR
If liquid nitrogen is available, the battery should be placed in liquid
nitrogen/or dry ice with a pair of tongs. Once frozen, the battery
must be dissected and the components neutralized in a soda ash
water bath. Unused or partially used Lithium must be set aside to
hydrolyze.
If the battery is thawed and not dissected, the battery will return to its
original state of being hot (short-circuited) and may explode.
If the battery vents or explodes, it should be handled with the
procedure for vented or exploding batteries.
PROCEDURE FOR EXPLODING BATTERIES
If a battery explodes, all personnel should be evacuated from the

area. The area should be vented to the outside until the pungent odor
is no longer detectable. If the expelled material is on fire, it should be
treated as described below in the procedure for a Lithium fire. After
the residue has cooled, it can be absorbed with Sodium Carbonate
and placed in plastic bags. All bags should be placed in a sealed and
labeled drum with Vermiculite or other non-flammable cushioning
material such as sand or Sodium Carbonate to cushion the s. These
materials should be disposed as previously described under Safe
Disposal in the Lithium Battery Safety Manual.
Section 10 13
PROCEDURE FOR A LITHIUM FIRE
Evacuate the premises. Personnel should avoid breathing the smoke

from a lithium fire, as it may be corrosive. Trained personnel wearing
self-contained breathing apparatus or a respirator with acid gas
cartridges should use Lith-X fire extinguishers to fight the fire. When
the fire is extinguished and the residue cooled, it can be absorbed with
Sodium Carbonate and placed in plastic bags. All bags should be
placed in a sealed and labeled drum with Vermiculite or other non-
flammable cushioning material such as sand or Sodium Carbonate to
cushion the s. These materials should be disposed as previously
described under Safe Disposal in the Lithium Battery Safety Manual.
14 Section 10
LITHIUM BATTERY SAFETY
With proper use and handling, lithium batteries have demonstrated

an extensive safety record.
The success and wide use of lithium batteries is partially because
they contain more energy per unit weight than conventional
batteries. However, the same properties, which result in a high
energy density also, contribute to potential hazards if the energy is
released at a fast and uncontrolled rate. In recognition of the high-
energy content of lithium systems, safety has been incorporated
into the design and manufacture of all batteries. However, abuse
or mishandling of lithium batteries can still result in hazardous
conditions. The information provided here is intended to give users
some guidelines to safe handling and use of lithium batteries.
Section 10 15
Abuse
In general, the conditions that cause damage to batteries and
jeopardize safety are summarized on the label of each. These
conditions include:
• Short Circuit
• Charging
• Forced Over-discharge
• Excessive heating or incineration
• Crush, puncture, or disassembly
Very rough handling or high shock and vibration could result in
damage.
NOT DESIGNED FOR CHARGING OR RECHARGING

PRODUCT NAME: Lithium Oxyhalide Primary Battery (MWD)
CHEMISTRY SYSTEM: Lithium/Thionyl Chloride
CHEMICAL FORMULAS: Li/ SOCI2
TOXIC, CAUSTIC OR IRRITANT CONTENT
Important Note: The battery container should not be opened or incinerated since
the following ingredients contained within could be harmful under some
circumstances if exposed.
In case of accidental ingestion of a cell or its contents, obtain prompt medical
advice.
MATERIALS
Lithium is included in this section due to its vigorous reaction with water forming a
caustic hydroxide.
Lithium (Li) (CAS # 7439-93-2)
Thionyl Chloride (SOCI2) (CAS # 7719-09-7)
STORAGE AND DISPOSAL TIPS

STORAGE: Store in a cool place but prevent condensation on the batteries. Elevated
temperatures can result in shortened battery life.
FIRE: If batteries are directly involved in a fire, DO NOT USE WATER, CO2, DRY
CHEMICAL OR HALOGEN EXTINGUISHERS. A Lith-X (graphite base) fire
extinguisher or material is the only recommended extinguishing media for fires
involving lithium metal or batteries. If a fire is in an adjacent area, and batteries are
packed in their original containers, the fire can be fought based on fueling material,
e.g., paper, and plastic products. Avoid fume inhalation.
DISPOSAL: DO NOT INCINERATE or subject batteries to temperatures in excess of

212°F (100°C). Such abuse can result in loss of seal, leakage, and/or explosion.
Dispose of in accordance with appropriate Federal, State, and Local regulations.
16 Section 10
HANDLING AND USE PRECAUTIONS
MECHANICAL CONTAINMENT: Encapsulation (some potting) will not allow for

expansion. Such enclosure can result in high-pressure explosion from heating due to
inadvertent charging or high temperature environments (i.e., in excess of 100°C).
SHORT-CIRCUIT: Batteries should always be packaged and transported in such a
manner as to prevent direct contact with each other. Short-circuiting will cause heat
and reduce capacity. Jewelry, such as rings and bracelets, should be removed or
insulated before handling the batteries to prevent inadvertent short-circuiting through
contact with the battery terminals. Burns to the skin may result from the heat
generated by a short- circuit.
CHARGING: These batteries are not designed to be charged or recharged. To do so
may cause the batteries to leak or explode.
OTHER: If soldering or welding to the terminals or case of the battery is required,
exercise proper precautions to prevent damage to the battery which may result in
loss of capacity, seal, leakage, and/or explosion. DO NOT SOLDER to the case.
Batteries should not be subjected to excessive mechanical shock & vibration.
Section 10 17
HANDLING AND INSPECTION GUIDELINES
The most frequent forms of abuse can easily be identified and
controlled in the workplace. All spirally, wound batteries are internally
protected against the hazards associated with short circuits. This is
accomplished by incorporating a fast acting fuse under the terminal cap.
It is our experience that inadvertent short circuits (resulting in open
fuses) are the largest single cause of field failures. Batteries with open
fuses (characterized by zero voltage) should be disposed of or returned
to the manufacturer for rework. Never attempt to remove the terminal
cap or replace the internal fuse.
Problems associated with shorting as well as other hazardous
conditions can be greatly reduced by observing the following
guidelines:
• Cover all metal work surfaces with an insulating material.
• The work area should be clean and free of sharp objects that
could puncture the insulating sleeve on the battery.
• Never remove the shrink-wrap from a battery pack.
• All persons handling batteries should remove jewelry items such
as rings, wristwatches, pendants, etc. that could be exposed to the
battery terminals.
• If batteries are removed from their original packages for
inspection, they should be neatly arranged to preclude shorting.
• Individual cells should be transported in plastic trays set on
pushcarts. This will reduce the chances of the batteries being
dropped on the floor, causing physical damage.
• All inspection tools (calipers, rulers, etc.) should be made from
non-conductive materials, or covered with a non-conductive tape.
• Batteries should be inspected for physical damage. Batteries
with dented cases or terminal caps should be inspected for
electrolyte leakage. If any is noted, the battery should be disposed
of in the proper manner.
18 Section 10
STORAGE
Batteries should be stored in their original containers. Store

batteries in a well ventilated, cool, dry area. Store batteries in an
isolated area, away from combustible materials. Never stack heavy
objects on top of boxes containing lithium batteries to preclude
crushing or puncturing the case.
HANDLING DURING PRODUCT ASSEMBLY
• All personnel handling batteries should wear appropriate

protective equipment such as safety glasses.
• Do not solder wires or tabs directly to the battery. Only solder to
the leads welded to the battery by the manufacturer.
• Never touch a battery case directly with a hot soldering iron.
Heat sinks should be used when soldering to the tabs, and contact
with the solder tabs should be limited to a few seconds.
• Batteries should not be forced into (or out of) battery holders or
housings. This could deform the battery pack causing an internal
short circuit, or fracturing the glass to metal hermetic seal.
• All ovens or environmental chambers used for testing batteries
should be equipped with an over-temperature controller to protect
against excessive heat.
• Do not connect batteries of different chemistries together.
• Do not connect batteries of different size together.
• Do not connect old and new batteries together.
• Consult manufacturer before encapsulating batteries during
discharge. Batteries may exceed their maximum rated temperature
if insulated.
Section 10 19
g GE Power Systems
Notes:
g GE Power Systems
MEMORY_IO UTILITY PROGRAM

TENSOR MWD
MEMORY INPUT & OUTPUT PROGRAM
This document is an unpublished work. Copyright 1994, 2001 (Revised) GE Power Systems. All rights
reserved. “This document and all information and expression contained herein are the property of GE Power
Systems and is provided to the recipient in confidence on a “need to know” basis. Your use of this document
is strictly limited to a legitimate business purpose requiring the information contained therein. Your use of
this document constitutes acceptance of these terms.”
Requirements
The program utility Memory_IO™ was developed to provide the operator

with a menu-oriented set of functions to initialize and configure the
memory recorder files and to transfer data from the files. Translation of
the data to any ASCII alphanumeric format requires the availability of an
interpreter function (View_Raw) for the specific file type. Higher level
processing of the recorded data, including plotting, is neither within the
scope of this manual or intent of the recorder software.
This program has been designed to have the function similar to other
Microsoft Windows™-based configuration PC programs developed by GE
Power Systems.
This manual will assist the operator to maneuver through the program,
configure data storage in the recorder boards, and retrieve the data from
the recorder boards.
2
Section 11, Version 2.00; February, 2002 11W32MemoryIO_GE.doc
Table of Contents
REQUIREMENTS............................................................................................................................2
TABLE OF CONTENTS..................................................................................................................3
LOG-ON ...........................................................................................................................................5
DIRECTORY AND FILE OPERATIONS SCREEN.......................................................................6
DIRECTORY AND FILE OPERATION .........................................................................................7
THE NODE DATA WINDOW ........................................................................................................8
FILE VIEW WINDOW ....................................................................................................................9
MOUSE OPERATIONS ON A RECORDER LABEL ..................................................................10
DRIVE VIEW WINDOW ..............................................................................................................11
FILE MENU COMMANDS ...........................................................................................................12
COPY..............................................................................................................................................12
COPY ALL FILES..........................................................................................................................13
COPY ALL NODES.......................................................................................................................13
LAST TRANSFER REPORT .........................................................................................................13
VIEW RAW FILE ..........................................................................................................................13
ERASE FILE ..................................................................................................................................13
ERASE ALL FILES........................................................................................................................14
CONFIGURATIONS......................................................................................................................14
MASTER RECORDING CONTROLS CONFIGURATION WINDOWS ...................................................14
REFRESH ALL NODES ................................................................................................................15
REFRESH NODE ...........................................................................................................................15
REFRESH A RECORDER FILE....................................................................................................15
OPEN FILE.....................................................................................................................................15
OPEN ALL FILES..........................................................................................................................15
CLOSE FILE ..................................................................................................................................16
CLOSE ALL FILE..........................................................................................................................16
3
FILE PROPERTIES ....................................................................................................................... 16
BRIEF: FILE STATUS REPORT ..................................................................................................... 16
FULL: FILE DETAIL REPORT ....................................................................................................... 17
FILE SYSTEM STATUS REPORT.................................................................................................... 17
SOFTWARE VERSION................................................................................................................... 17
EXIT............................................................................................................................................... 17
DRIVE VIEW WINDOW .............................................................................................................. 18
RECORDER FILE DEFINITIONS................................................................................................ 18

“ATFA” FILE RECORD FORMAT & CONFIGURATION.................................................................. 18
“AVAR” FILE RECORD FORMAT & CONFIGURATION .................................................................. 19
“BATT” FILE RECORD FORMAT & CONFIGURATION................................................................... 19
“CDIR” FILE RECORD FORMAT & CONFIGURATION ................................................................... 19
“CIRC” FILE RECORD FORMAT & CONFIGURATION ................................................................... 19
“DIRD” FILE RECORD FORMAT & CONFIGURATION .................................................................. 20
“DVAR” FILE RECORD FORMAT & CONFIGURATION ................................................................. 20
“EVNT” FILE RECORD FORMAT & CONFIGURATION .................................................................. 20
“GAMA” FILE RECORD FORMAT & CONFIGURATION ................................................................. 21
“GAMR” FILE RECORD FORMAT & CONFIGURATION ................................................................. 21
“GVD4 & “GVD8” FILE RECORD FORMAT & CONFIGURATION ............................................... 22
“PLSR” FILE RECORD FORMAT & CONFIGURATION .................................................................... 22
“QCOP” FILE RECORD FORMAT & CONFIGURATION ................................................................. 23
“SUD” FILE RECORD FORMAT & CONFIGURATION .................................................................... 23
“TCH4” FILE RECORD FORMAT & CONFIGURATION .................................................................. 23
“TEMP” FILE RECORD FORMAT & CONFIGURATION ................................................................... 23
“TREV” FILE RECORD FORMAT & CONFIGURATION .................................................................. 24
“TTMP” FILE RECORD FORMAT & CONFIGURATION .................................................................. 24
“UDIR” FILE RECORD FORMAT & CONFIGURATION .................................................................. 24
“XD20”, “XD36” & “XVLR” FILE RECORD FORMATS............................................................... 24
SET UP........................................................................................................................................... 26
RAW AND DATA WRITE FILE PATH ............................................................................................ 26
DEFAULT (JOB) INFORMATION INPUT READ FILE PATH (JIPA)................................................... 26
FILE EXTENSION FOR RAW FILE DIRECTORIES (REXT) ............................................................... 26
DEFAULT USER INFORMATION SECTION FILE (QTNM) .............................................................. 27
FILE-COPY BAUD RATE (FCBR) ................................................................................................ 27
NIC-PC BAUD RATE (NPBR) .................................................................................................... 27
SKIP COPY-RANGE WINDOW (CROP) ........................................................................................ 27
SKIP COPY FILE TO PATH WINDOW (SCFP) ............................................................................... 27
SKIP [JOB] INFORMATION SECTION PROCESS DURING RECORDER FILE COPY (QTOP) .............. 27
SKIP SPECIFY MAXIMUM FILE SIZE (SFSO) ............................................................................... 27
DISABLE SET-SYSTEM TIME WINDOW (STWO)......................................................................... 29
COMMANDS................................................................................................................................. 29
SET SYSTEM/QMIX TIME ........................................................................................................... 29
FORMAT FILE MEMORY .............................................................................................................. 29
4
Log-On
The Log-On screen is the program title screen and allows the operator to
enter 1 to 11 capability codes that define the user’s capability level. The
default level is 11. It is the client’s responsibility to determine the level of
access allowed the operator in the field. Any operators familiar with the
qMWDCnfg Program Utility will be knowledgeable of the Capability Level
and Access Codes.
The following window will display to indicate the baud rate of the data
communication. This is just a statement to indicate what the speed of the
data transfer will be if an older qNIC is used that does not have the
upgraded firmware contained in it. Most users will not see this warning.
5
Directory and File Operations Screen
When connected only to the MPTx (Node 20), the main menu screen will
appear as indicated above. Clients connecting to a probe containing the
turbine processor, in the regulator portion of the turbine assembly, will
notice the address label in the Drive View Window (left portion of the
window), to indicate the presence of that particular microprocessor,
TCR29.
When connecting to a Recorder Board that has been powered down, the
following window will appear (at the operators discretion), requesting to
transmit the current PC time to the MPTx. The command to Set the
System Time is also available under the Commands drag-down menu.
6
Directory and File Operation
The purpose of the Directory and File Operation window is to allow the
operator access to all memory files in the system and perform various file
operations including copy, erase, open and close operations. On copying,
the recorder file data will be saved to an output file referred to as the “Raw
Data File” that has by convention, a PC file extension of “.RAW”. This

extension may be modified in the program Setup options.
The window is divided into three windowpanes, the Node Data Window,
the File View Window and the Drive View Window.
7
The Node Data Window
The Selected Node Data will be updated approximately every two

seconds. The PC time and date will be updated every second.
The Selected Node Data includes the selected node's label and ID
number, date and time, qMIX fault and warning registers (qDFR & qDWR),
the File System Status register (FSSR) and the File System Control
Register (FSCR). In addition, registers unique to the application MAY be
displayed.
All registers can be expanded in detail by double-clicking the mouse on

the particular register field.
Any register data that indicates fault or warning conditions will be

displayed on a red background. If communications between the PC and
the selected node is lost, ALL of the selected node's data fields, including
the node's 'Name' field, will be displayed on a red background. If this
situation occurs, the readings displayed in the selected node's data fields
will be the last data received from the selected node before the
communication breakdown occurred.
This window also includes a 'Refresh' button, which will remove all of the
current data and re-poll new data from all of the nodes on the Q-Bus.
8
File View Window
This window displays the following information for each recorder file on the
selected node.
NodeID - Recorder labels and address. (On the heading of the first
column.)
Label - Memory File label.
Status - Indicates the selected file is Open or Closed.
Recorder Bytes - Size of current data file in bytes.
Recorder Records - Size of current data file in number of records. (*)
Allocated Bytes - The total size of the file in bytes
Copied - Indicates whether the selected file has been copied to PC.
Time Of Status - the actual PC time when the status was received from
the recorder.
(*) It does not reflect the actual physical size of the file type of variable
length record files.
9
Mouse Operations on a Recorder Label
Left-Click on a recorder file label to select and highlight a recorder file.
Double-click on a recorder file label to bring up a detailed status report of

a recorder file.
Right-Click on a recorder file label to bring up Operation Options Menu. A

similar menu, the File Menu Commands, can be accessed from the File
option on the drag-down menu.
10
Drive View Window
This is a tree-type structure view of all the recorders

available on the Q-Bus.
Mouse operations on a Node
Left-Click on a node label to select and highlight a

node.
Double-click on a node label to expand or collapse
individual nodes.
Right-Click on a node label to bring up a status
report of a recorder node.
Mouse operations on a Recorder File
Left-Click on a recorder file label to select and

highlight a recorder file.
Right-Click on a recorder file label to bring up a
status report of a recorder if
11
File Menu Commands
This menu can be accessed from the File

drag-down menu of the Directory and File
Operation Menu.
Copy
Copy File allows copying a portion or the

entire file from the source node to a
specified disk PC file. A prompt for the
path and name of the file is displayed. If
the file exists, a warning is displayed.
During the copy process, there will be a
dynamic window showing the file transfer
progress. If the process fails for any
reason, the number of blocks that have
been copied successfully will be displayed.
The following additional information will be

stored in each file: - Memory I/O &
Configuration program version string.
- The path and name of the disk file itself.

- Time&Date, the raw file copied from the recorder.
- Recorder version string.
- Recorder Node I.D.
- Recorder file name.
- Recorder file status.
- Recorder Control Block Data.
- The Starting and the Ending Block Number, and the block size.
12
Copy All Files
Copy All Files allows copying all the files in the selected node
automatically from the source node to a specified disk PC file. During the
copy process, there will be two dynamic windows, one showing the file
transfer progress and the second one showing the history of the process
and the result of operation on each recorder file
Copy All Nodes
Copy All Nodes allows copying all the files in the selected node
automatically from the source nodes to a specified disk PC file. During the
copy process, there will be two dynamic windows, one showing the file
transfer progress and the second one showing the history of the process
and the result of operation on each recorder file.
Last Transfer Report
This option brings up a report of the file transfer statistics for the last file
transfer of the selected recorder file.
View Raw File
The Raw Data File Viewer (View_Raw) interprets and translates the DATA
SECTION of a selected raw data file into a readable form. This interpreter
provides viewing and printing of Raw Data File.
Erase File
This option allows the operator to erase the selected file. If the file was
not successfully copied, the operator will be so advised in a pop-up
window and provided with the opportunity to either Cancel or Continue. In
any case, the operator will have one more opportunities to abort the
operation before the erase command is issued. The erase operation
leaves the file open for recording purposes. The Erase File operation is
effectively a close-file operation immediately followed by an open-file
operation.
13
Erase All Files
This option allows the operator to erase all the open files in the selected
memory node. If the Copied Status does not indicate that all the files were
(successfully) copied, the operator will be so advised in a pop-up window
and provided with the opportunity to either Cancel or Continue. In any
case, the operator will have one more opportunities to abort the operation
before the command is issued. This operation leaves all files open. The
Erase All Files operation is effectively a close-file operation immediately
followed by an open-file operation.
Configurations
This consists of two different types of Configurations, the Master Controls,

and the File Controls.
Master Recording Controls Configuration Windows
This option will bring up a window that provides the capability to

configure the Master Recorder Controls of the selected NODE.
A separate executable program will be launch by this program

when this option is selected. The executable file naming
conventions is "xxxCnfg.exe", where "xxxx" is the 2,3 or 4-character
label of the selected NODE.
File Recording Controls Configuration Windows
This option will bring up a window that provides the capability to

configure the File Recorder Controls of the selected FILE.
A separate executable program will be launch by this program

when this option is selected. The executable file naming
conventions is "xxxCnfg.exe", where "xxxx" is the 2,3 or 4-character
label of the selected FILE.
14
Refresh All Nodes
This switch re-acquires the file directory information from all nodes. Each
node with recording capability will respond with a list of all predefined files.
Once the list of files has been created, the program requests status
information on each file in the list. This information is then used to re-
create the information displayed on the all the windows
Refresh Node
This switch re-acquires all the files of the currently selected node. This
information is then used to re-create the information displayed on the File
View window. A "NO DATA" indication in the "Status" column indicates
the node identified the file name, but failed to provide the detailed status
information as requested by the PC.
Refresh A Recorder File
This switch re-acquires a file of the currently selected node. This

information is then used to re-create the information displayed on the File
View window. A "NO DATA" indication in the "Status" column indicates
the node identified the file name, but failed to provide the detailed status
information as requested by the PC.
Open File
This option opens a predefined file by allocating memory to the file.

For fixed-length record and variable-length record files, this option will
cause a pop-window to appear that will allow the operator to specify the
MAXIMUM amount of memory to be allocated in 'Memory Blocks'. A
single memory block is allocated to a file when initially opened. For
accumulation-type files, memory allocations are fixed - they are NOT
dynamic.
Open All Files
The option opens all files that are closed - all files not already opened.
This option does not allow the operator to specify any file
options/attributes - such as the maximum file size.
15
Close File
This option allows the operator to close the selected file. If the file was not
successfully copied, the operator would be so advised in a pop-up window
case, the operator will have one more opportunity to abort the operation
before the command is issued. The close-file operation reallocates the file
memory blocks and disables the file for recording purposes.
Close All File
This option allows the operator to close all of the open files in the selected
memory node. If the Copied Status does not indicate that all the files were
(successfully) copied, the operator will be so advised in a pop-up window
case, the operator will have one more opportunities to abort the operation
before the command is issued. The close operation disables the file for
recording purposes.
File Properties
This option consist of three different types of reports:
• Brief
• Full
• File System
• Software Version
Brief: File Status Report
This option will generate a status report of the selected file. The
report contains the following information:
- Current Block Number.

- Current Record Entry/Index (For Sequential Files).
- Number of Bytes per Record.
- Current File Record Number.
- Total number of Output Blocks allocated.
- Number of Records per Output Block.
- Current File Block Number.
- Fault Indicators (General, Definition or File Control).
- File-Overflow Indicator (Accumulation- and Histogram-type Files.)
- File-Full Indicator.
16
Full: File Detail Report
-This option will generate a detailed file status report of the file.
File System: File System Status Report
-This option will generate a file system status report of the node.
Software Version: Software Version
-This option will generate a window with the software version string
of the selected node.
File System Status Report
This option will generate a file system status report of the node.
Software Version
This option will generate a window with the software version string
of the selected node.
Exit
Use this command to end your Memory_IO session.
17
Drive View Window
The Drive View Window displays all of the various recorders available on
the Q-Bus. Below are the descriptions of each of the file definitions.
Recorder File Definitions
“aTFA” File Record Format & Configuration
The “auto-ToolFace Angle” recorder identified as “aTFA”

automatically records toolface data during flow-on conditions. This
file is primarily provided for test and diagnostic purposes. As many
as 16 data points are stored in a single 53-byte, fixed-length record,
which is headed with the 4-byte packed time tag.
There are no recorder configuration parameters that directly affect

or control data recordings in this file. If gamma recording stops
mid-record due to a power-off, reset, or flow-off condition, or if the
toolface-type changes, then the record is closed and a new record
is opened, when the next data point is available. A
short/incomplete record is indicated when any of the remaining
“dTime” bytes are 0.
18
“AVar” File Record format & Configuration
The Accelerometer-Variance-Data Recorder – “AVar” consists of

20-byte fixed-length records, which records the 4-byte packed
directional time tag and the variance on each of the three (3) 12-bit
accelerometer A-to-D channels (VAx, VAy & VAz) and the derived
value of Grav. All data is recorded as 4-byte floating-point values.
“AVar” Recording Mode – AVRM

A single Recording Mode parameter – “AVRM” – allows recording
“All” directional data updates or “SurveyONLY” data updates.
“Batt” File Record Format & Configuration
The Battery Voltage recorder identified as “Batt” records high and

low battery voltage measurements at fixed 0.1 – hour intervals.
Data is acquired according to the “BatC” controls as defined for the
downhole tool and typically set/configured using the DOS
qMWDCnfg or Windows qMWDCnfg/W32™ programs. As many
as 10 data points are stored in a single 24-byte, fixed-length record
which is headed by the 4-byte packed time tag. There are no
recorder configuration parameters that directly affect or control data
recordings in this file.
“CDir” File Record Format & Configuration
The Corrected-Directional Sensor Data Recorder File – CDir –

consists of 36-byte fixed – length records, which records the 4-byte
packed directional time tag, and the 8 corrected 12-byte A-to-D
channels (Mx, My, Mz, Ax, Ay, Az, Temp & Ch7). All sensor data is
recorded as 4-byte floating-point values.
“CDir” Recording Mode – CDRM
A single Recording Mode parameter – CDRM – allows

recording “All” directional data updates or “SurveyONLY”
data updates.
“CirC” File Record Format & Configuration
The qMWD™ “Circulation – Time Recorder” – “CirC” –

accumulates the total Flow-On time. Accumulated times are
recorded in units of 240 seconds. The “CirC” recorder occupies
256 bytes of type-1 (28c256 EEPROM) memory. The maximum
range is 232 seconds (49,710 days).
19
“DirD” File Record Format & Configuration
The Directional Data Recorder – “DirD” _ consists of 38-byte fixed-

length records, which record the 4-byte packed directional time tag,
Inc, Azm, MagF, DipA, Temp, gTFA, mTFA, Grav, the 1-byte
Directional Flag register – DiFR and the currently-unused sensor
fault byte. All borehole information is recorded as 4-byte floating-
point values.
“DirD” Recording mode – “DDRM”
A single Recording Mode parameter – “DDRM” allows

data updates.
“DVar” File Record Format & Configuration
The Directional Sensor Variance Data recorder – “DVar” – consists

of 48-byte fixed-length records, which record the 4-byte packed
directional time tag, the variance on each of the 8 12-bit A-to-D
channels, - VMx, VMy, VMz, VAx, VAy, VAz, VTmp & VCh7, and
the derived values of MagF, DipA & Grav. All data is recorded as
4-byte floating-point values.
“DVar” Recording Mode – “DVRM”
A single Recording Mode parameter – “DVRM” allows

data updates.
“Evnt” File Record Format & Configuration
The Event File contains variable-length records that are used to log
application and system-type events – primarily for diagnostic
purpose. Examples of events logged are various types of resets,
control block configurations, flow-state change events, etc.
20
“Gama” File Record Format & Configuration
The Gamma recorder identified as “Gama” records gamma data

that is acquired according to the “GamC” controls as defined for the
real-time telemetry process and typically set/configured using the
DOS qMWDCnfg or Windows qMWDCnfg/W32™ programs. As
many as 16 data points are stored in a single 36-byte, fixed-length
record is headed with the 4-byte packed time tag. The recorded
gamma value – “Gama” – is scaled by the gamma scale factor –
“Gsf”. Also, refer to the “GamR’ recorder, which allows recording at
fixed intervals independent of the telemetry process. There are no
recorder configuration parameters that directly affect or control data
recordings in this file.
“GamR” File Record Format & Configuration
The Gamma Recorder identified as “GamR”, unlike the “Gama” file,

is real-time telemetry-independent to allow recording at fixed
intervals. A single 8-byte, fixed-length record is headed with the 4-
byte packed time tag. The recorded gamma value – “GamR” – is
scaled by the gamma scale factor – “Gsf”, as is the “Gama” data
value.
“GamR” Recording Controls – “GRC”
The operation of the recorder is affected by the controls in

the “GRC” block.
“GaRI” defines the Gamma Recording Interval for timed-

automatic recording modes from 2 to 3000 minutes.
“GaRM” defines the Gamma Recording Mode, which has

several options:
• “Off” – will disable internal recording.
• “NoFlowAuto” will effect recordings at the specified “GaRI”
interval while flow is off.
• “FlowAuto” will effect recordings at the specified “GaRI”
interval while flow is on.
• “TimedAuto” will effect recordings at the specified “GaRI”
interval regardless of the Flow State.
• Monitor” will effect recordings whenever the “Gama” variable
is updates – conventionally for telemetry. This would
effectively allow recording the “Gama” values in the “GamR”
file format, which has a wider range that the single-byte
“Gama’ file format.
21
“Graf” – is the typical data Auto-Formatting Switch used in
conjunction with the Recorded data Format String – “GRFo” –
for the recorded gamma data acquisition process. This is
typically used for bench testing. The standard qMIX™ switch
options are “On” and “Off”.
Since the “GamR” is an independent data acquisition process, a

format string – “GRFo” and an auto-format switch – “GRAF” –
have been provided for testing purposes.
“GVD4 & “GVD8” File Record Format & Configuration
Two Generic-Variables-Data recorders are provided with the intent

that the operator would, by convention, select/Open only one of the
two for recording. The two files share common set of
configuration/control parameters.
“GVD4” – The 20-byte, fixed-length record “GVD4” file is

used to record generic variables “GV0” through “GV3”. The
record structure is headed with the 4-byte packed time tag.
“GVD8” – The 36-byte, fixed length record “GVD8” file is

used to record all 8 generic variables “GV0” through “GV7”.
The record structure is headed with the 4-byte packed time
tag.
“Plsr” File record Format & Configuration
The qMWD™ Pulser Operations Recorder – “Plsr” accumulates

pulser operations.
• The number of pulser operations is normally recorded at 10th
hour intervals as long as the number of operations is greater
than 20.
• If the number of unrecorded operations exceeds 240, then
240 operations are immediately recorded.
The “Plsr” recorder occupies 256 bytes of type-1 (28c256

EEPROM) memory. The maximum range is 232 operations (4 X
109)
22
“qCOP” File Record Format & Configuration
The qCOP File is a special event file containing variable length

records that log system-type events for diagnostic purposes. The
primary function of the logic associated with this file is to monitor
system resources to detect fatal anomalies, record the anomaly,
and effect a reset of the processor.
“SuD” File Record Format & Configuration
The standard Survey Data Recorder – SuD, consists of 17-byte

fixed length records, which records the 4-byte packed directional
time tag, Inc, Azm, MagF, DipA, Temp, gTFA and mTFA. All
borehole information is recorded as 2-byte fixed-point values. A
survey data record is written automatically each time that the
directional data-acquisition process indicates a new survey data set
is ready. There are no recorder configuration parameters that
directly affect or control data recordings in this file.
“TCh4” File Record Format & Configuration
The Turbine Analog Channel #4 Data File – TCh4 is provided in the

event that the now-undefined analog channel #4 data is utilized in
the future. Then open, a fixed length, 16-byte data record will be
recorded at the end of each “TuRI” data averaging and recording
interval.
High and Low values are maximum and minimum 1-second

averaged values during the TuRI period.
High and Low Peak values are maximum and minimum single-
sample values during the TuRI period.
“Temp” File record Format & Configuration
The qMWD™ Time Temperature Histogram Recorder – Temp,

records the time within multiple 10°C accumulators that span the
range from –50°C to +180°C (inclusive).
There are 26 4-byte accumulators:

• 1 accumulator for all readings < -50°C
• 23 10 – C° accumulators that span the range from –50°C to
+180° C.
• 1 accumulator for all reading > +180° C.
23
• 1 accumulator for periods at an unknown temperature.
The maximum range is 232 0.1 hour (17 X 106 days).
The “Temp” recorder occupies 768 bytes of type-1 (28c256
EEPROM) memory.
“TRev” File Record Format & Configuration
The Turbine Revolutions Accumulation File – TRev, is provided for

diagnostic information or possibly for use to schedule normal
maintenance. It accumulates in units of thousands of revolutions.
“TTmp” File Record Format & Configuration
The Turbine Time Temperature Histogram Recorder – TTmp,

records the time within multiple 10 C° temperature bands to a
resolution of 0.1 hours.
There are 26 4-byte accumulators:

• 1 accumulator for all readings < -50°C
• 23 10 – C° accumulators that span the range from –50°C
to +180° C.
• 1 accumulator for all reading > +180° C.
• 1 accumulator for periods at an unknown temperature.
The maximum range is 232 0.1 hour (17 X 106 days).
The “Temp” recorder occupies 768 bytes of type-1 (28c256
EEPROM) memory.
“UDir” File Record Format & Configuration
The Uncorrected Directional Sensor Data Recorder – UDir,

consists of 36 byte fixed length records, which records the 4-byte
packed directional time tag, and the 8 Uncorrected but scaled 12 bit
A-to-D channels (UMx, UMy, UMz, UAx, UAy, UAz, UTmp & Uch7).
All sensor data is recorded as 4-byte floating-point values.
“xD20”, “xD36” & “xVLR” File Record Formats
Three General Purpose Files may be used by the end-user to

record data, in any format, over the Q-BUS as provided by the
qMIX-syntactical Recorder Write-Record Function. Two general
purpose, fixed length record data files and a single, variable length
record data file are available. In all cases, and inherent by the
24
design definition, the MemoryIO/32 program only provides file
viewing in hexadecimal formats.
25
Set Up
Raw and Data Write File Path
This string describes the path to which raw and Data files are
stored to disk. A leading \\ can be used to specify a path beginning
from the root directory. If no path is specified, the current directory
is searched. This path may also be edited when actually storing a
file.
Default (Job) Information Input Read File Path (JIPa)
This string describes the path to which (Job) Information Input files
are loaded from disk. A leading \ can be used to specify a path
beginning from the root directory. If no path is specified, the current
directory is searched.
File Extension for Raw File Directories (Rext)
This string describes a file extension that is used when storing Raw
files to disk. Enter a maximum of three characters for the
extension. The period ('.') can be omitted.
26
Default User Information Section File (QTNm)
This string defines a file on the 'RAW and Data Write Path' and
forces the recorder Copy File process to copy the content of this file
to the User Information Section of the RAW file.
NOTE: This option string will be disabled and ignored by the

program under the following conditions:
1) Skip Job Information Section Process is Enabled.

2) The string is empty.
File-Copy Baud Rate (FCBR)
This is the baud rate when downloading files from the recorder.
The options are 38400, 19200, 9600, and 4800.
NIC-PC Baud Rate (NPBR)
This is the baud rate for the NIC-PC point-to-point serial

communications link. The options are 38400, 19200, and 9600.
Skip Copy-Range Window (CROp)
This option allows the operator to skip the Copy-Range Window

during the Copy File process. Select 'Yes' to enable this option or
'NO' to disable this option.
Skip Copy File to Path Window (SCFP)
This option allows the operator to skip the Copy File to Path
Window process during Copy File process. Select 'YES' to enable
this option or 'NO' to disable this option.
Skip [Job] Information Section Process During Recorder File

Copy (QTOp)
This option allows the operator to skip the Information Section entry
process during Copy File process. Select 'YES' to enable this
option or 'NO' to disable this option.
Skip Specify Maximum File Size (SFSO)
27
This option allows the operator to skip the Specify Maximum File
Size Window during Open File process. Select 'Yes' to enable this
option or 'NO' to disable this option.
28
Disable Set-System Time Window (STWO)
This option allows the operator to disable the Set-System Time

Window.
Commands
Set System/qMIX Time
Selecting this item sets the qMIX "Time" variable of the PC program
to the current time of the PC clock. The "Time" is then broadcast
over the communications network to all modules/nodes.
Format File Memory
This command will cause the file memory to be reformatted. This

command may only be invoked when the file system is disabled
and no other memory related processes are active - such as a
memory test or memory block erasures.
It will:
• Close all open files,
• Erase all good file-system blocks - blocks that are not bad.
• Process all bad file chains to recover any lost memory blocks.
• NOT Delete/erase any bad file information.
29
A G
Allocated Bytes .......................................... 8 Gama......................................................... 22
aTFA......................................................... 18 GaRI.......................................................... 22
AVar ......................................................... 19 GaRM ....................................................... 22
Graf ........................................................... 24
B
GRC .......................................................... 22
baud rate ..................................................... 4 GVD4........................................................ 24
Baud Rate ................................................. 29 GVD8........................................................ 24
C L
Capability Level ......................................... 4 Label ........................................................... 8
CirC .......................................................... 19 Labels
Close All File............................................ 16 aTFA .................................................... 18
Close File.................................................. 16 AVar..................................................... 19
Configurations .......................................... 13 Batt....................................................... 19
Copied ........................................................ 8 CDir...................................................... 19
Copy ......................................................... 11 CirC...................................................... 19
Copy All ................................................... 12 DDRM.................................................. 21
Copy File to Path ...................................... 29 DirD ..................................................... 21
Copy-Range Window ............................... 29 DVar..................................................... 21
DVRM.................................................. 21
D Evnt ...................................................... 21
Data Write File Path ................................. 28 Gama .................................................... 22
DDRM ...................................................... 21 GaRI..................................................... 22
DirD.......................................................... 21 GaRM................................................... 22
Directory................................................. 5, 6 Graf ...................................................... 24
Drive View ..................................... 6, 10, 18 GRC ..................................................... 22
DVar ......................................................... 21 GVD4................................................... 24
DVRM ...................................................... 21 GVD8................................................... 24
qCOP.................................................... 25
E SuD ...................................................... 25
Erase All Files .......................................... 13 TCh4 .................................................... 25
Erase File .................................................. 12 Temp .................................................... 25
Evnt .......................................................... 21 TRev..................................................... 26
Exit ........................................................... 17 TTmp.................................................... 26
UDir ..................................................... 26
F xD20..................................................... 27
fault............................................................. 7 xD36..................................................... 27
File Definitions ......................................... 18 xVLR.................................................... 27
File Detail Report ..................................... 17 Log-On........................................................ 4
File Extension........................................... 28 Capability Level..................................... 4
File Menu.................................................. 11 M
File Operation............................................. 6
File Operations ........................................... 5 Master Recording Controls ....................... 13
File Properties........................................... 16 Maximum File Size................................... 30
File Recording Controls............................ 13 Mouse Operation......................................... 9
File Status ................................................. 16 N
File System Status Report......................... 17
File View .................................................... 8 NIC-PC Baud Rate.................................... 29
Format File Memory................................. 31 Node Data ................................................... 7
FSSR........................................................... 7
30
O Software Version.......................................17
Status ...........................................................8
Open All Files ...........................................15
Status Report .............................................17
Open File...................................................15
SuD............................................................25
P
T
Plsr ............................................................24
Table of Contents ........................................3
Q TCh4..........................................................25
Temp .........................................................25
qCOP.........................................................25 Transfer Report .........................................12
qDFR...........................................................7 TRev..........................................................26
qDWR .........................................................7 TTmp.........................................................26
R U
Read File Path ...........................................28
UDir ..........................................................26
Recorder Bytes............................................8 User Information Section ..........................29
Recorder Records........................................8
Refresh A Recorder File ...........................15 V
Refresh All ................................................15
View Raw..................................................12
Refresh Node ............................................15
Requirements ..............................................2 W
S warning conditions ......................................7
Set System/qMIX Time ............................31 X
Set Up .......................................................28
xD20..........................................................27
Data Write File Path.............................28
xD36..........................................................27
Read File Path ......................................28
xVLR.........................................................27
Set-System Time .......................................31
31
NOTES
32
g GE Power Systems
Tensor MWD
MWDRoll32
System Utility
NOTES
2
Section 12; Version 2.00; February, 2002; 12WinMWDRoll32_GE.doc
Overview
MWDRoll32 is a standalone piece of software used to verify correct operation of
Measurement-While-Drilling (MWD) tools manufactured by GE Power Systems .
Using MWDRoll32 entails performing various tests, both logical and physical, prior to
the use of MWD tools. MWDRoll32 diagnostics reports from a correctly functioning
tool will fall within the guidelines for satisfactory operation, while a non/mal-
functioning tool will fail to reach these guidelines. Given the software’s limited
demands on the client’s computer system, MWDRoll32 will not require new or
powerful machines to run.
Hardware Requirements:
• A PC compatible computer.
• qNIC cable.
• Safe Area Power Supply (SAPS).
• Tool Programming cable.
Hardware Setup:
• Connect on end of the qNIC cable to an available qBUS port on the SAPS.
• Connect the other end of the qNIC cable to an available COM port on the
computer.
• Connect the tool programming cable to the SAPS and the MWD tool.
Software Requirements:
• Microsoft Windows 95/98 or NT 4.0.
Minimum Windows Settings:

• Screen resolution of 640x480 pixels.
• Video color depth of 8 bits (256 colors).
Recommended Windows Settings:

• Screen resolution of 1024x768 pixels.
• Video color depth of 16 bits (65536 colors) or more.
3
MWDRoll32 is an entirely new program. It encompasses almost all the functionality
of the older MWDRoll, for the benefit of previous users, with the new features are
described below.
• O/S platform upgrade from MS-DOS to Windows 95/98/NT.

• New UI presenting a graphical/alphanumerical display.
• MWD tool communication now handled via qW32Server application.
• New “Remote” data acquisition mode.
• No need to save data, it is all automatically saved into a database.
• Added header/data editing.
• New print previewing feature.
• Printed reports now present information in more comprehensive fashion.
• New feature allows opening, editing, and updating previous roll tests.
• Added help and user manual.
• Multilanguage support.
4
Main Display
The main display is the only window that gives the user information about the MWD
tool’s status. This display was designed to give the user all relevant information
about the current roll test and the MWD tool. When MWDRoll32 is started, you will
notice that the display consists of six subsections, each designed to give the user
particular information.
The six subsections are as follows:

• Guidance Rose: Designed as an alternative to the alphanumeric
displays, this display gives a graphical view of the three-dimensional
orientation of the MWD tool.
• Sensor Derived Data: This display gives the user real-time critical
information that would be difficult to calculate manually.
• Sensor Acquired Data: Some of the corrected sensor values of the
MWD tool are displayed in this display.
• Header Information: Information about the current roll test is displayed
in this section.
• Miscellaneous Notes: Any notes entered via the header information
dialogs are displayed in this section.
• User Instructions / Feedback: This constant up-to-date section
provides the user with useful information about what state MWDRoll32 is
in and what operations are allowed. There are also two buttons that allow
manual acquisition of data.
5
Guidance Rose Display
The Guidance Rose was designed to give the user a more intuitive and easy to read
perspective on the MWD tool’s orientation in space. When MWDRoll32 has
established communication with the tool, this display will be active.
While not acquiring data, the display will resemble one of these:
The image to the left is displayed when no tool is attached or communication is not
established with the tool. The “ghosted” display indicates that nothing needs to be
displayed.
The image to the right is displayed when a tool is attached and communication has
been established. In the display, you will find three essential pieces of information:
Inclination:
On the left of the display there is a vertical semicircle. Within the semicircle, there are
two colors – yellow and green. The inclination is indicated by the intersection of the
two colors. More specifically, in the picture above, the inclination is at roughly 90°. If
the tool is oriented upwards, the yellow arc will span 180° to the top. If the tool is
orientated downwards, the green arc will span 180° to the bottom.
Azimuth:
The blue arc in the outermost circle indicates the azimuth. It always starts from the
top (0°) and wraps clockwise around to the current azimuth angle. In the above
picture, the azimuth is approximately 97°.
High Side:
The red line in the inner circle indicates the high side. When the tool is rotated, this
line will move and constantly display the MWD tool’s roll angle. In the above picture,
the high side is approximately 253°.
When acquiring data, the display will differ somewhat:
6
In this mode, the rose will act the same but will have five extra visible items. These
extra items are designed to give the user a clearer picture of what is going on during
data acquisition.
The most prominent new item is the green pie section. This pie section indicates the
recommended high side for the current data shot. During a roll test, the pie section
will rotate through 8 ordinal positions spaced evenly at 45° intervals. It will be the
user’s duty to align the high side (red line) indicator within the green pie section.
The other four items are located in the four corners of the rose display. They are
designed to give the user feedback on what MWDRoll32 believes is the correct
position to acquire data for. The top left item indicates whether the inclination is right.
The top right item indicates whether the azimuth is right. The lower right item
indicates whether the high side is right. Finally, the lower left item indicates whether
the tool is stable or unstable.
In the picture above, the user is attempting to take the first shot in the East
orientation. From the leftmost picture, we can tell that the tool is not ready to acquire
data. While the inclination is correct and the tool is stable, the azimuth and high side
are incorrect. The user then rotates the tool towards the east orientation. The blue
azimuth arc rotates to indicate east and the azimuth item in the top right of the
display indicates OK. Then, the user rotates the tool until the high side lies within the
green pie section. Then, the high side item in the lower right of the display indicates
OK. Now that all items are displaying in green, it is recommended that data be
acquired. To do so, click on the “Acquire” button.
7
Sensor Displays
In the main display, you will find the Sensor Acquired Data and the Sensor Derived
Data views. In an attempt to provide all relevant information to the user in just one
window, these displays were created. The Sensor Acquired Data display shows
critical sensor values while the Sensor Derived Data shows information calculated
from the acquired data.
Sensor Acquired Data:

• Accelerometer X, Y, & Z: Corrected gravity values from the MWD tool’s
accelerometer sensor are displayed here.
• Magnetometer X, Y, & Z: Corrected magnetic field values from the
MWD tool’s magnetometer sensor are displayed here.
• Battery: The battery power, in volts, is displayed here.
• Temperature: The tool’s temperature in degrees Celsius is displayed
here.
Sensor Derived Data:

• Total Acceleration: The overall acceleration due to gravity is displayed
here.
• Total Magnetic Field: The overall magnetic field is displayed here.
• Dip Angle: The angle formed between the tool and the earth’s surface is
displayed here.
• High Side: The angle calculated from the gravitational tool-face is
displayed here.
• Azimuth Angle: The horizontal angle of the tool.
• Inclination Angle: The angle with respect to vertical.
• Magnetic Tool-Face: The angle calculated from the magnetic tool-face
is displayed here.
• Timeout/Update: The number to the left of the slash (/) indicates the
time before communication will timeout. The number to the right of the
slash indicates the last refresh interval.
8
Header Information and Miscellaneous Notes Display
The header information and notes displays present the user with information
pertaining to the started or opened roll test.
Header Information Display:

Under the sensor displays, you will find the header information display. This simple
display shows the information entered in the Header Information dialog. Once
again, this information is displayed to present all relevant information to the user.
Miscellaneous Notes Display:

To the left of the header information display, you will find the Miscellaneous Notes
dialog. The text displayed in this display is identical to the text entered in the Header
Information dialog.
9
User Instructions / Feedback Display
The bottommost display gives the user information about the current status of
MWDRoll32. At all times, the user can check this display to see what is happening
and what can be done.
The two buttons to the right are used when acquiring data in Interactive mode. When
in this mode, the display will indicate the required orientation and the number of data
shots to perform. The user will use the Guidance Rose or Sensor Derived Data
display to determine whether a data shot can be made. If so, the Acquire button will
save the data and proceed to the next shot. On the other hand, the user might not
want to take the shot and can use the Skip button.
10
Starting a New Roll Test
When MWDRoll32 is started, by default, no roll test is started or opened. In this state,
the only functionality provided is the actual display of MWD sensor data. An
experienced user might be able to determine whether the tool has a problem simply
by visual inspection of the data. However, it is very likely that visual inspection alone
is enough – thus the need for performing roll tests.
The Process:
Starting a new roll test involves three basic steps. First, click on the Start New Roll
Test… item from the File menu. The Header Information dialog will appear. Enter
all information and click OK. Then, the Roll Test Options dialog will appear. After
selecting the desired options, click on the OK button.
MWDRoll32 will be put into data acquisition mode. Depending on what options were
selected, data will be acquired in Interactive or Remote mode. For more information
on how to acquire data, see the Acquiring Data help.
Tool Orientation
It is extremely important that the operator follow the tool orientation instructions
displayed in the User Instructions/Feedback window. The design of the Roll Test is
to gather data at prescribed positions as determined by GE Power Systems . The
data gathered and derived from the sensors in the predetermined positions is
analyzed with respect to the tool being in those positions. Data gathered out of
position will skew the results and give a false indication that the tool is out of
calibration. Please follow the instructions for the Roll Test explicitly so that an
accurate test can be performed.
11
N
North
Orientation
East
Orientation
Take shots in the eight (8) ordinal position for
each of the three horizontal orientations. Follow
the instructions for performing a Roll Test. Take
two (2) shots in the vertical position. Note the
position of the sensors relative to the position
changes during the roll test. The results of the roll
test are based on the tool being rotated through the
prescribed positions.
Vertical
Orientation
South
Orientation
12
Continuing a Previous Roll Test
Once a roll test has been completed, it is possible to re-open it and perform certain
tasks. For example, it is possible to open a previous test and re-print the report. Also,
any changes can be made to the header, and more data can be acquired.
The Process:
To open a previous test, click on the Open Previous Roll Test... item from the File
menu. Select the test that you wish to re-acquire data for and click the OK button.
Now that a roll test is open, you may start acquiring data. To do so, select the Start
Data Acquisition… item from the File menu. The Roll Test Options dialog will
appear and after selecting the desired options, click on the OK button.
MWDRoll32 will be put into data acquisition mode. Depending on what options were
selected, data will be acquired in Interactive or Remote mode. For more information
on how to acquire data, see the Acquiring Data help.
13
Opening a Roll Test
Once a roll test has been completed, it is possible to open it and perform certain
tasks. MWDRoll32 allows the user to perform all possible tasks on an opened test –
just like a new test. For example, if a user performed a roll test, printed it, and later
determined that there was some bad data, they might want to re-open the test and
take more data shots.
Starting the dialog:

If at least one roll test has been performed, you will be allowed to open this dialog. To
do so, select the Open Previous Roll Test… item from the File menu and the dialog
will appear.
In the Test Identifier section, a unique number assigned to each test performed will
be displayed. By default, the latest test will be highlighted but the user can choose
any of them. By selecting a test, Header Information and the Miscellaneous Notes
for that test will be displayed. Once content with the selection, the user can click OK
to open the test.
Note: One reason for entering all header information and some descriptive notes
when a test is started is that it makes it easier to discern between tests later.
14
Editing Header Information
There are exactly two instances when the user will need to edit a test header. First, if
a new roll test is started (see Starting a New Roll Test), the dialog below will appear
and prompt the user for information. Second, if a roll test has been opened or is
active, and the user wants to edit the header to update it.
Starting the Dialog:

Once a roll test is open (see Opening a Roll Test), the header may be edited. To do
so, select the Header Information… item from the Edit menu and the dialog below
will appear.
While it is not required to enter all possible fields, it is highly recommended.

Identification of the test will be very difficult if insufficient data is entered.
Note: The Unique ID Number, Tool Serial Number, and Start Data & Time are all
read-only. MWDRoll32 will enter these fields automatically.
15
Editing Test Data
Unfortunately, roll tests do not always work exactly as expected. Bad data due to
magnetic interference, human misalignment, or any other source could plague a
perfectly good tool’s roll test. This eventuality can be handled by flagging bad test
data.

If a test is opened or in progress, you may use the data editing feature by clicking on
Data Sets… from the Edit menu. A window will appear within which each row
constitutes a data shot. Within that row, several pieces of data are listed and
correspond to a column.
Data-Set Columns (Units):

• Shot #: The incremental number corresponding to the data shot.
• Orientation: The orientation that the shot was taken in. (N, S, E, V, U)
• Bad: A check box that allows the user to discard the data shot. (True/False)
• Gx, Gy, Gz: The MWD accelerometer sensor’s X, Y, and Z-axis value. (G)
• G Tot: The total acceleration calculated by the accelerometer values. (G)
• Hx, Hy, Hz: The MWD magnetometer sensor’s X, Y, and Z-axis value.
(Gauss)
• H Tot: The total magnetic field calculated by the magnetometer values.
(Gauss)
• Azm: The azimuth angle of the tool. (°)
• Inc: The inclination of the tool. (°)
• mTFA: The magnetic tool-face angle. (°)
• gTFA: The gravitational tool-face (High-side) angle. (°)
• DipA: The dip angle with respect to the earth’s magnetic field. (°)
Removing Bad Data:

As a user, your duty will be to identify the data set or sets that have bad data. Once
identified, place a checkmark in the Bad field of the data set. The data is now marked
as bad. Although the data will be marked bad until unmarked, it is not deleted. It will
remain part of the acquired data and will be visible on printed reports. Even though
16
bad data is not deleted, it will not be used in any calculations and can be safely
ignored.
17
Roll Test Options
Data acquisition can be initiated in only two ways. First, if the user wishes to start a
new test, they will be guided through a sequence that will automatically bring up the
dialog below and start data acquisition. Otherwise, if the user has an opened roll test
open, they must manually choose to start acquiring data.

Once a roll test has been opened and is active, the user can choose to start
acquiring data. To do so, select the Start Data Acquisition… item from the File
menu. The dialog below will appear.
Test Operating Mode:

First, the user will need to determine which operating mode they will be using. If a
test is being conducted with the computer close by, Interactive mode will allow the
user to manually acquire data when they are ready. Otherwise, if the computer is
beyond practical distance, using Remote mode will allow data to be acquired
automatically at timed intervals.
Interactive Mode Options:

If the user selects Interactive mode, the interactive mode options must be set. By
default, manual data acquisition will be selected. This means that when data is to be
acquired, the user must use the Acquire and Skip buttons. If automatic data
acquisition is selected, MWDRoll32 will acquire data automatically when the tool is in
the correct position.
Remote Mode Options:

If the user selects Remote mode, the remote mode options must be set. To give the
user time to proceed to the MWD tool’s location before testing actually starts, enter
the time (in seconds) needed in the Hold-Off field. Then, set the time (in seconds)
between each data acquisition in the Interval field.
18
Note: The Interval field specifies the time between each data acquisition.
When the orientation changes, the user will not have any extra time to move
the tool.
19
Orientations:
By default, data will be acquired for all four orientations. The user can, if they wish to,
choose which orientations to use. Frequently, if a data shot is discovered to be bad
after a roll test is completed, the user will want to re-acquire data for that orientation
only.
Starting the test:

Once all options in this dialog have been set, the user may start the test by clicking
on the OK button. To find out how to acquire data, see the Acquiring Data help.
20
Acquiring Data
Once a roll test has been started (see Starting a New Roll Test), the process of data
acquisition will be initiated. Depending on whether the user selected to operate in
Interactive or Remote mode, data will be acquired in very different ways.
Interactive Mode Data Acquisition:
Step 1: For this step, the user will position the tool in the orientation specified
in the User Instructions / Feedback display. To do this, place the MWD tool
flat (set inclination to 90°) and set the azimuth to reflect the orientation:
• For North, set the azimuth to 0°

• For East, set the azimuth to 90°
• For South, set the azimuth to 180°
• For Vertical, the azimuth value is ignored.
Step 2: Before a data shot can be acquired, use the Guidance Rose display
to rotate the tool until the red high side marker is within the green marker.
This indicates that the tool is within accepted limits for accuracy. Clicking on
the Acquire button will save the data shot and clicking on the Skip button
will discard the data shot. Once either button has been pressed, the green
marker will move and the user will repeat this step until the marker is back in
the original position.
Step 3: Once the green marker has rotated in a complete circle and back to
the original position, the User Instructions / Feedback display will indicate
what to do next. If there is still more orientations left, proceed with step 1.
Otherwise, the test has been completed.
Remote Mode Data Acquisition:
Once the user clicks the OK button from the Roll Test Options dialog, the
data acquisition process will start immediately. Synchronize your watch to
when the OK button is pressed.
Step 1: Proceed to the MWD tool’s location and position it in the first
orientation specified in the Roll Test Options dialog. Next, wait for the Hold-
Off time to elapse.
Step 2: Now, MWDRoll32 will acquire data at the rate specified in the Roll
Test Options dialog. It will be the user’s task to rotate the tool by 45°
between intervals and wait for the data shot to be recorded.
Step 3: Once all data shots have been completed for the current orientation,
the user must determine whether there is another orientation left or whether
the test is over. If there is another orientation, position the tool for that
orientation and continue with step 2. Otherwise, the test has been completed.
Note that positioning the tool for a new orientation must be completed within
the interval time.
21
Printing and Exporting Reports
Once a roll test has been completed, the user might want to print or export a report.
Although all data will be saved, it is highly recommended that a report be printed for
every roll test.

To view a preview of the test report, click on the Print/Export Report… item from the
File menu. A window containing a preview pane and print control buttons will appear.
Exporting:
If you wish to export the report, click on the icon with an envelope picture. You will be
prompted to enter the format and destination of the export. If you wish to export to
another file format, you will be prompted to enter the path and filename for the new
file. If you are done performing printing and exporting tasks, click the X button to
close the window.
Printing:
If you wish to print the report, verify that the data is correct by using the print control
buttons to zoom, switch pages, etc. Once you are ready to print, click the icon with
the printer picture. A window with print options will appear. When ready, click OK and
the report will be spooled to the printer. If you are done performing printing and
exporting tasks, click the X button to close the window.
22
Troubleshooting
Known Issues:
There are certain known issues that may cause problems under relatively infrequent
circumstances. This section will highlight them.
Error Messages:
• The Jet VBA file vbajet.dll or vbajet32.dll failed to initialize when

called. Try re-installing the application that returned the error: This
error is due to a problem registering the DAO file ddao350.dll. To correct
this problem, click on the Windows Start button, choose the “Run” item,
and enter “regsvr32 ddao350.dll”. Click OK and re-start MWDRoll32.
Appearance Problems:
• MWDRoll32’s main displays look discolored, odd, or indistinguishable:

This is probably due to bad color settings. From your Start button, click on
Control Panel from the Settings menu. Next, click on the Display icon. A
window should appear with several tabs at the top. Click on the Settings tab.
The Color Palette item should be set to at least 256 colors or 8 bit. Ideally, it
should be at 65536 Colors, 16 Bit, or High Color.
• MWDRoll32 doesn’t fit within my Windows desktop and I can’t see

some items: This problem is due to the resolution of the video adapter.
From your Start button, click on Control Panel from the Settings menu. Next,
click on the Display icon. A window should appear with several tabs at the
top. Click on the Settings tab. The desktop area should be at least 640 x 480.
Ideally it should be at 1024 x 768.
• After I print, the print preview pane displays oddly: Once a report has
been sent to the printer, MWDRoll32 will be unable to refresh the print
preview screen. To view it again, click on the Close button and re-click on
the Print/Export Report… item from the File menu.
Bug Reporting:
If you find a problem that seems likely to be a bug, first make sure you can reproduce
the problem. Then email the following list of details to mike.spalding@ps.ge.com or
kenneth.braud@ps.ge.com
• Your name and email address for correspondence.

• Description of bug including any relevant information.
• Steps needed to reproduce the problem.
• Details of the computer system running MWDRoll32.
• Any additional information.
Please be sure to submit the email with as many details as possible.
23
Magnetic Declination and other Magnetic Information
The declination and other magnetic information can be found on the Internet at the
site for National Geophysical Data Center of NOAA. The address is
www.ngdc.noaa.gov/seg/potfld/geomag.html, and under the heading Models and
Software is listed Magnetic Declination On-line. The latitude and longitude must be
entered to obtain the information and the declination will be calculated from the
model. The option to use the Zip Code for U.S. areas is an option to get the Latitude
and Longitude. There are two sites listed on the page, U.S. Gazetteer and the Getty
Thesaurus that will assist you in finding the correct Longitude and Latitude if the zip
code is not useful or unknown.
The results will be give in this following format:

Model: IGRF2000
Latitude: 30.44 deg
Longitude: -97.63 deg
Elevation: 0.00 km
Date of Interest: 2/19/2002
D I H X Y Z F
(deg) (deg) (nt) (nt) (nt) (nt) (nt)
5d 39m 59d 49m 24715 24595 2435 42502 49166
dD dI dH dX dY dZ dF
(min/yr)(min/yr) (nT/yr) (nT/yr) (nT/yr) (nT/yr) (nT/yr)
-5 -0 -38 -34 -43 -75 -84
D = Magnetic Declination in Degrees and minutes (divide value m by 60 to convert to

decimal degrees) 5d 39m = 5.65°
I = Magnetic Inclination or Dip Angle in Degrees and minutes.
F = Total Magnetic Field in nanoteslers. Divide by 1000 to convert to Gauss.
The lower line of values indicates the change per year of the values and the direction
of the change, either + or -.
24

MWD Ops

Uploaded by

Copyright:

Available Formats

You might also like

MWD Ops

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

MWD Ops

Uploaded by

Copyright:

Available Formats

g GE Energy

THIS MANUAL CONTAINS PROPRIETARY

1840 Royston Lane

MWD Operations Manual

01 Variable Units Definition Utility

Variable Units Definition Utility

The Variable Units Definition Utility defines the units to be used

The utility allows the operator to perform the following actions:

· Select a predefined units definition.

The displayed units definition may be saved to a file for use on

The predefined Imperial Set is selected by clicking the

The predefined Metric Set is selected by clicking the button

The predefined default set is selected by clicking the button

This option allows the operator to design an Imperial or

To customize the selected units definition, click on the dropdown

Clicking the Broadcast button will cause the currently displayed

Note: All qMWD/32 applications running when the units are

Length Newtons [N]

Plane Angle Electrical Resistivity

Angular Velocity Magnetic Induction

TABLE OF CONTENTS ....................................................................................... 3

It is of the utmost importance for all users of this software package to

Should a client require a uniform systematic approach for their

GE Power Systems provides the software instruction to the user

Experience has proven that managers of companies employing the

The user can design the system to search a particular drive or

After selecting a particular *.MWD configuration file, the previous

To select a particular file, simply double click on the desired file.

Configuration *.MWD File Control

Experience has proven that managers of companies employing the

The program has numerous features available for insuring limited

They are the

These features can be located in the Setup procedures of the

This program allows the operator to design program configurations

The operator’s PC is only the system that contains the programs

Access to the qMWDCnfg program can be controlled by setting the

To be able to total access to the configuration system, please call

The Setup Parameters Edit Screen is designed to allow the

Receiver Link Address & Transmitter Link Address

(MPRx) Receiver Link Address: 05 (MUST ALWAYS BE 5)

Filter for Config. File Directories: This string describes a filter

Auto Verify, Label: AVer, Select an Option: When enabled, this

Configuration File Name, Label: CfgF, Edit String: This is the

Configuration Load Option Switch, CfgL, Select an Option:

1. “Fixed” - The file named in the ‘Configuration File Name’

2. “Last” - The last file ACCESSED, either READ IN or

NOTE: If the “Last” or “Fixed” options are selected and the

Serial/ Release Number, Label: SrlN, Edit String: This is a

Depth Tracking Controls, Label DTE, Select an Option: This

Turbine Controls, Label TuEn, Select an Option: This variable

To change the level of the read/write options, the operator needs to

It is recommended that for the variables always requiring viewing

Operating Parameters… Clicking on the sub menu,

Access Levels… Clicking on the sub menu, Access

Capability Codes… Clicking on the sub menu,

Save Current Setup… Clicking on the sub menu, Save

Receiver – Clicking on the Receiver label will reveal the Win95

Receiver – Clicking on this menu option will reveal the Windows