User’s Guide

  

    



Technical Communications Group

P.O. Box 670968
Houston, TX 77267-0968
USA
713-625-4694
This manual is provided without any warranty of any kind,
either expressed or implied. The information in this document
is believed to be accurate. However, Baker Hughes INTEQ
will not be liable for any damages, whether direct or indirect,
which result from the use of any information contained
herein.

© 1998 Baker Hughes Incorporated. All rights reserved.


 



Chapter 1


 
Preparation & Installation Procedures . . . . . . . . . . . . . . . . . . 1-1
TMI P133 System Installation Problems . . . . . . . . . . . . . . 1-5
Hard Drive Will Not Boot After Image Cloning . . . . . 1-5
Sound Blaster Configuration . . . . . . . . . . . . . . . . . . . . . . 1-6
Monitor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Manually Ghosting MSS Images (Non-Field Systems) . . . 1-7
MSS Image Configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Re-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Converting to a Single Computer System . . . . . . . . . . . . . 1-8
Possible Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
DCI and TMI Peripheral Card Layout . . . . . . . . . . . 1-10
Trenton PII-333 MHz CPU BIOS Configuration . . . . 1-12
Trenton PII-333 MHz CPU SCSI BIOS Configuration 1-15
TMI P133 BIOS Configuration . . . . . . . . . . . . . . . . 1-16
TMI P133 SCSI BIOS Configuration . . . . . . . . . . . . 1-18
Upgrading a TMI P133 Configuration . . . . . . . . . . . . . . 1-19
Hardware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Update CMOS Configuration . . . . . . . . . . . . . . . . . 1-20
Update SCSI BIOS Configuration . . . . . . . . . . . . . . 1-20
3COM 3C509B Configuration . . . . . . . . . . . . . . . . . 1-21
Downloading OPTO22 Software (HAZARA) . . . . . . . . . . . . 1-22
Physical Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Download the Opto 22 Kernel & Strategy via ARCnet 1-22
Downloading the Kernel . . . . . . . . . . . . . . . . . . 1-25
Downloading the Strategy . . . . . . . . . . . . . . . . . 1-26
Save the Strategy to Flash (EPROM) . . . . . . . . . 1-27
Download the Kernel & Strategy via Serial Cable . . 1-29
Known Issues & Miscellaneous Comments . . . . . . . . 1-31
Checking System Communications . . . . . . . . . . . . . . . . . . . 1-33
Test Ethernet Communications . . . . . . . . . . . . . . . . . . . 1-33
Physical Indications . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Software Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Interconnection of MSS Systems . . . . . . . . . . . . . . . 1-35

  ! 



 
      

 

  



Check DSeries Interconnection . . . . . . . . . . . . . . . . 1-35

ARCnet Communications & SARA/HAZARA, (M4RTU) 1-35
Checking Sensor Channels . . . . . . . . . . . . . . . . . . . . . . 1-36
Channel A & B Communications in MWD PowerComms 1-38
Good Communication . . . . . . . . . . . . . . . . . . . . . . . 1-39
No Communication . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Partial Communication . . . . . . . . . . . . . . . . . . . . . . 1-40
Network Troubleshooting & General Information . . . . . . 1-43
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Coaxial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Twisted Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45
ARCnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-45
Other Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46
Network Interface Cards . . . . . . . . . . . . . . . . . . . . . 1-46
Media Converters . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Fiber Optic Hub (Concentrator) . . . . . . . . . . . . . . . 1-49
Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Changing Network Names and Addresses . . . . . . . . . . . . 1-54
Windows 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
ARCnet Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

Chapter 2

 
MSS Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Computer Naming Conventions . . . . . . . . . . . . . . . . . 2-1
Main INTEQ Directory Structure . . . . . . . . . . . . . . . . 2-2
RES Subdirectory Structure . . . . . . . . . . . . . . . . . . . . 2-3
Bin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Ctl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
symb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Tmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

 "# $!%& '()*

 


 
    

 

  


System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
MSS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Message Server/Common Data Area . . . . . . . . . . . . 2-11
Interprocess Communication . . . . . . . . . . . . . . . 2-11
Common Data Area Access . . . . . . . . . . . . . . . . 2-11
Units Conversion System . . . . . . . . . . . . . . . . . . . . . 2-13
Conversion ID . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Units Conversion Files . . . . . . . . . . . . . . . . . . . 2-15
Depth Tracking System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Depth System States . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
No Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Drilling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Reaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Off Bottom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
In Slips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
MSS Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
DSeries Data Backup . . . . . . . . . . . . . . . . . . . . . . . 2-22
General Notes & Hints . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Chapter 3
 
Setup & Monitor (MSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Database/Location Setup . . . . . . . . . . . . . . . . . . . . . 3-2
Starting a New Field, Facility or Well . . . . . . . . . . . . 3-3
Starting a New Hole . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Field Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Facility Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Well Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Hole Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Location Properties . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Rig Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Pump Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Base System Units Specification . . . . . . . . . . . . . . . 3-11
Service Level Setup . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
MWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

  ! 



 
     

 

  



Surface Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

DAQ/COMMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Processes Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
MWD Tool Configuration Setup . . . . . . . . . . . . . . . . 3-18
Survey Reference Setup . . . . . . . . . . . . . . . . . . . . . . 3-21
Survey Reference Data Window . . . . . . . . . . . . . . . . 3-23
BGGM Calculations Window . . . . . . . . . . . . . . . . . . 3-24
Sag Calculations Window . . . . . . . . . . . . . . . . . . . . 3-25
SUCOP Reference Data Window . . . . . . . . . . . . . . . 3-28
Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30
Main Window Setup Information . . . . . . . . . . . . . . . . . . 3-32
Annulus Properties . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Drillstring Properties . . . . . . . . . . . . . . . . . . . . . . . 3-33
Units Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Log Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36
MSS Message Server (MsgSvr) . . . . . . . . . . . . . . . . . . . . . . 3-37
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37
Message Server Files . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Message Server Displays . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Configuring the Message Server . . . . . . . . . . . . . . . . . . 3-42
Configuring Client Computers . . . . . . . . . . . . . . . . . . . . 3-50
Other Message Server Properties . . . . . . . . . . . . . . . . . . 3-50
Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Network Options . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Log Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Performance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
CDAFeed Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Common Data Area Setup (CDASetup) . . . . . . . . . . . . . . . . 3-54
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54
CDA Table Description . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-58
Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Changing Units Conversions . . . . . . . . . . . . . . . . . . . . . 3-60
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
MWD Detect/Decode (MWDecode) . . . . . . . . . . . . . . . . . . . 3-62
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-62

 "# $!%& '()*

 


 
    

 

  


Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
NRZ (Non-Combinatorial) Start-up Windows . . . . . . 3-66
MWD Graphics (MWDGraph) . . . . . . . . . . . . . . . . . . . . . . 3-80
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
AutoTrak Control (ATCtl) . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Transmitting Downlinks . . . . . . . . . . . . . . . . . . . . . 3-93
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Start-up Options . . . . . . . . . . . . . . . . . . . . . . . . 3-94
AutoTrak Display (ATDisp) . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Survey Processing (SvyPrc) . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
MagCorr Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
ASurvey Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
SUCOP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Using SvyPrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Current View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105
Quality Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
INTEQ_RTS - SUCOP Interface Driver . . . . . . . . . . . . . . . 3-109
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
Survey Editing & Printing (SvyEdit) . . . . . . . . . . . . . . . . . 3-111
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Importing & Exporting Surveys . . . . . . . . . . . . . . . . . . 3-112
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-112
Creating a Survey Report . . . . . . . . . . . . . . . . . . . . . . 3-114
Remote Driller’s Dial (RDD) . . . . . . . . . . . . . . . . . . . . . . 3-118
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
Parameters Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119
Serial Port Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Starting & Stopping Processing (Transmission) . . . . . . 3-121

  !



 
     

 

  



Testing the Driller's Dial . . . . . . . . . . . . . . . . . . . . . . . 3-122

Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . 3-123
Real time Processing (RtProc) . . . . . . . . . . . . . . . . . . . . . . 3-124
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-124
CDA Item Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
Saving the Configuration . . . . . . . . . . . . . . . . . . . . 3-128
Loading a Saved Configuration . . . . . . . . . . . . . . . 3-129
Depth Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Depth Tracking Control Page . . . . . . . . . . . . . . . . 3-131
Depth Tracking Setpoints Page . . . . . . . . . . . . . . . 3-131
Depth Tracking Resets Page . . . . . . . . . . . . . . . . . 3-132
Depth Tracking Tide Page . . . . . . . . . . . . . . . . . . . 3-134
Depth Tracking Heave Page . . . . . . . . . . . . . . . . . 3-135
MWD Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135
Starting & Stopping MWD Processing . . . . . . . . . . 3-136
Online Hydraulics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Entering Setup Data & Starting Online Hydraulics . 3-137
Hydraulics Control Page . . . . . . . . . . . . . . . . . . . . 3-137
Hydraulics Resets Page . . . . . . . . . . . . . . . . . . . . . 3-138
Hydraulics Rheology Page . . . . . . . . . . . . . . . . . . 3-139
Hydraulics Cuttings Page . . . . . . . . . . . . . . . . . . . 3-141
Specifying the Relog Number . . . . . . . . . . . . . . . . . . . 3-141
Calculating Bottom-Hole Resisivities . . . . . . . . . . . . . . 3-142
Changing Units Conversions . . . . . . . . . . . . . . . . . . . . 3-143
Viewing the Error Log . . . . . . . . . . . . . . . . . . . . . . . . 3-144
Viewing the Depth Track & MWD Logs . . . . . . . . . . . 3-145
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . 3-146
Data Logger (Dlogger) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-147
Configuring Record Types
(Database Tables) . . . . . . . . . . . . . . . . . . . . . . . 3-149
Undoing Changes . . . . . . . . . . . . . . . . . . . . . . . . . 3-153
Saving the Configuration . . . . . . . . . . . . . . . . . . . . 3-153
Starting Data Logger Recording . . . . . . . . . . . . . . . . . . 3-153
Updating the Configuration While Recording . . . . . . . . 3-154
Stopping Data Logger Recording . . . . . . . . . . . . . . . . . 3-154
Changing Units Conversions . . . . . . . . . . . . . . . . . . . . 3-154
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . 3-156

 "# $!%& '()*

 


 
    

 

  


Online Torque & Drag (Ontad) . . . . . . . . . . . . . . . . . . . . . 3-157
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157
Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-158
Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-164
General Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-164
Calculation Setup . . . . . . . . . . . . . . . . . . . . . . . . . 3-166
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-178
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-178
Running the Program . . . . . . . . . . . . . . . . . . . . . . 3-179
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-180
Buckling Information . . . . . . . . . . . . . . . . . . . . . . 3-185
WOB Reserve Until Buckling Occurs . . . . . . . . 3-185
Control Files/Database/CDA . . . . . . . . . . . . . . . . 3-187
Online Help Utilities . . . . . . . . . . . . . . . . . . . . . . . 3-188
Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-188
Buckling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-188
Stiff/Soft String Model . . . . . . . . . . . . . . . . . . . . . . 3-189
Reading the Opto System (ReadOpto) . . . . . . . . . . . . . . . . 3-193
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-194
Reading the P&F System (ReadPF) . . . . . . . . . . . . . . . . . . 3-197
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-197
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-197
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-198
Reading the Pump Stroke Gauge (ReadSpm) . . . . . . . . . . . 3-201
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-201
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-201
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-202
Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-202
Flow Calculation Option . . . . . . . . . . . . . . . . . . . . 3-204
Decode Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-204
RigLink Real Time Plot (RLPlot) . . . . . . . . . . . . . . . . . . . 3-205
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-205
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-205
RLPlot Files (*.rlp) . . . . . . . . . . . . . . . . . . . . . . . . 3-206
Label Applet . . . . . . . . . . . . . . . . . . . . . . . . . . 3-207
Number Value Applet . . . . . . . . . . . . . . . . . . . 3-207
Well Activity Applet . . . . . . . . . . . . . . . . . . . . 3-208

  ! 



 
     

 

  



Steering Rose Applet . . . . . . . . . . . . . . . . . . . . 3-209

Formation Evaluation Log Applet . . . . . . . . . . 3-212
FEEdit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-213
Rig Display (RigDisp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-222
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-222
Choosing a Format for Display . . . . . . . . . . . . . . . . . . 3-223
Using the Open Command . . . . . . . . . . . . . . . . . . . 3-223
Using the List Command . . . . . . . . . . . . . . . . . . . . 3-224
Changing the Scale Range of a Trace Component . . . . . 3-225
Getting Information about a Lights Component . . . . . . . 3-226
Changing Units Conversions . . . . . . . . . . . . . . . . . . . . 3-226
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . 3-227
CDA Feed/RigLink Server . . . . . . . . . . . . . . . . . . . . . . . . 3-228
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-228
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-228
RigLink Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233
WITS Data Communications (WITS) . . . . . . . . . . . . . . . . . 3-237
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-237
Properties Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-238
Global Properties . . . . . . . . . . . . . . . . . . . . . . . . . 3-238
Port Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-240
Communications Configuration . . . . . . . . . . . . . . . . . . 3-242
Trigger Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-243
Record Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-245
Setting Up & Starting WITS Transmission . . . . . . . . . . 3-247
Ending WITS Transmission . . . . . . . . . . . . . . . . . . . . . 3-248
Example Transmission Formats . . . . . . . . . . . . . . . . . . 3-248
Mobil MWD Communications (MOBM) . . . . . . . . . . . . . . 3-253
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-253
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-255
Transmission Parameters . . . . . . . . . . . . . . . . . . . 3-255
CDA Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-257
Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-258
Menus & Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259
Transfer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259
Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-259
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-260

 "# $!%& '()*

 


 
    

 

  


Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
Last Data Packet . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
Message File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-261
Database Editor (DbEdit) . . . . . . . . . . . . . . . . . . . . . . . . . 3-264
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-264
Performing Individual Record-Based Editing of Table . 3-266
Copying & Printing the Spreadsheet Contents . . . . 3-270
Editing Attribute Values . . . . . . . . . . . . . . . . . . . . . . . 3-270
Individual Value . . . . . . . . . . . . . . . . . . . . . . . . . . 3-270
Block of Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-270
Protected Attributes . . . . . . . . . . . . . . . . . . . . . . . 3-271
Adjusting the Spreadsheet Display . . . . . . . . . . . . . . . . 3-271
Modifying the Deleted/Undeleted Status of Records . . . 3-272
Inserting a Record . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-273
Special Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-275
Time Depth Adjust . . . . . . . . . . . . . . . . . . . . . . . . 3-276
Mass Delete/Undelete . . . . . . . . . . . . . . . . . . . . . . 3-277
Mass Identifier Change (MWD tables) . . . . . . . . . . 3-279
Reprocess MWD . . . . . . . . . . . . . . . . . . . . . . . . . . 3-280
Recalculate MWD . . . . . . . . . . . . . . . . . . . . . . . . . 3-281
Write DSeries Files . . . . . . . . . . . . . . . . . . . . . . . . 3-282
Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . 3-285
Backup/Restore/Delete Utility (BackRest) . . . . . . . . . . . . . 3-286
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-286
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-287
Tree Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-288
Selecting a Tree Node . . . . . . . . . . . . . . . . . . . 3-288
Selecting Data Types . . . . . . . . . . . . . . . . . . . 3-289
Selecting an Operation . . . . . . . . . . . . . . . . . . 3-289
Processing Operations . . . . . . . . . . . . . . . . . . . . . . . . 3-289
Backup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-289
Restore Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-292
Delete Database Data . . . . . . . . . . . . . . . . . . . . . . 3-294
Delete Disk Data . . . . . . . . . . . . . . . . . . . . . . . . . 3-295
Backup & Restore Scripts . . . . . . . . . . . . . . . . . . . . . . . . . 3-296
MSS Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-296
DSeries Data Backup . . . . . . . . . . . . . . . . . . . . . . 3-297
Output to HPUTIL Files from MSS Database (MPSetup) . . 3-298

  ! +



 
     

 

  



Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-298
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-299
Data Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-301
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-302
Plot Driver (PDriver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-303
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-303
Template Options . . . . . . . . . . . . . . . . . . . . . . . . . 3-304
Headers & Trailers . . . . . . . . . . . . . . . . . . . . . . . . 3-307
Plot Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-308
Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-309
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-310
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-310
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-311
Tasks Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 3-312
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 3-329
How To... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-333
Configure a Veritas Thermal Plotter . . . . . . . . . . . 3-333
Select Curves for Plot . . . . . . . . . . . . . . . . . . . . . . 3-333
Select Header & Trailer Pages . . . . . . . . . . . . . . . 3-333
Plot Curves in Different Units . . . . . . . . . . . . . . . . 3-333
Edit Contents of Remarks Page . . . . . . . . . . . . . . . 3-334
Change Log Plot Headers . . . . . . . . . . . . . . . . . . . 3-335

Chapter 4
 

Message Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Digital Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Procedural Considerations . . . . . . . . . . . . . . . . . . . . 4-3
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Block Height - Resetting Digital Counters . . . . . . 4-6
RPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Analog Sensor Calibration . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Procedural Considerations . . . . . . . . . . . . . . . . . . . . 4-7
Block Separation . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Hookload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

+ "# $!%& '()*

 


 
    

 

  


SPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Torque . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Create Tool Run in DSeries . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Well & Hole Set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
MWDecode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Start Depth Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Start MWD Processing . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
MSS Hydraulics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Start-up (Summary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Chapter 5
 
Quick Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
MSS Hydraulics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Calibration Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Resetting Block Height SARA/HAZARA . . . . . . . . . . . . 5-4
Resetting Block Height P&F . . . . . . . . . . . . . . . . . . . . . . 5-4
Start New Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Start a Sidetrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Create a Relog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Calculating Bottom Hole Resistivity . . . . . . . . . . . . . . . . . . . 5-9
Calculating Potassium Concentration . . . . . . . . . . . . . . . 5-10
Changing Units Conversion . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Assigning Alternate Equipment . . . . . . . . . . . . . . . . . . . . . . 5-11
Checking the Various Online Message Logs . . . . . . . . . . . . . 5-11
Entering a Tie-On Survey . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Posting a Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Editing a Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Creating a Survey Report . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Creating a Daily Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Creating a Real-Time Plot . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
RigLink Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Transferring Data to DSeries . . . . . . . . . . . . . . . . . . . . . . . . 5-19
DbEdit Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
MPSetup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Backup Individual Runs . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Final Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

  ! +



 
     
  1



Chapter 1 covers procedures for

installing and downloading software to
an MSS system.

 
  
To install an MSS system, you will need the following
disks:
• MSS installation floppy disk.
• MSS CD-ROM (this is a two disk set)
1. Place the first CD-ROM in the CD-ROM drive of the
PC and boot from the MSS installation floppy disk.
This disk will load all the necessary drivers and run
an installation script on the CD-ROM.
You are prompted to select the type of computer that
MSS is being installed on, enter the appropriate
number and press [RETURN] to continue.
1. DCI and TMI systems
2. Toshiba Satellite 220CDS and Tecra
530CDT
3. Azonics Propanel
4. DOS prompt No drivers
5. DOS prompt Test Mode DCI and TMI
Systems
2. After loading drivers and running the install script
from the CD-ROM, the cloning operation begins.

  ! ,



 
     Confidential

 
 


3. On the DCI systems, because of a bug in the Ghost

cloning program on SCSI hard drives, we have to run
it in “slow mode”. As a result the early part of the
cloning appears to do nothing for 5-10 minutes, it is
in fact inspecting the hard drive, once this is
complete the cloning process will begin.
4. Part way though the cloning operation you will be
prompted to Insert next media and press enter to
continue. Replace the CD-ROM with the second
CD-ROM. Tab to the FileName? button and press
[ENTER]. Scroll down to select the MSS.001 file
and press [ENTER], cloning will then continue.
5. At the end of the cloning operation, remove the
floppy drive and reboot the computer from the hard
drive.
6. If this is a TMI P133 System, refer to the section,
“Installation Problems” later in this chapter.
7. The system will halt at a menu showing three
options:
Windows NT Workstation Version 4.00
Windows NT Workstation Version 4.00
[VGA Mode]
Microsoft Windows
Select Microsoft Windows and press [RETURN] to
continue the boot.
8. Eventually you will see the Enter Network Password
Screen. Login as admin with a password of
mssadmin.
9. You will be faced with three scenarios at this point:
• The Audio card is the same model as used to build
the images, see steps 10-12.
• The Audio card is a different model to that in the
images, but is supported by the same drivers, see
steps 12-19.

,- "# $!%& '()*

Confidential


 
    

 
 


• The Audio is an unsupported model. Consult with

local technical support if this happens are there a
several methods that may be required to solve this
scenario.
10. You will see several dialogs stating New Hardware
Found for the Creative Sound Blaster Audio Card.
Drivers will be installed automatically (provided that
this a supported model), when installing the joystick
driver the user will be informed of a version
conflict.
11. Select Yes to keep the version installed on the
computer. More New Hardware Found dialog’s
will appear to complete the driver installation.
12. The Windows 95 configuration is completed, select

 

     to
reboot the system.
13. Ensure the resource assignments for the sound card
are correct. Right click on the My Computer icon
on the desktop and select Properties.
14. Select Device Manager tab.
15. Open the Sound, video and game controllers node
and select the Creative AWE64 16-bit Audio item,
then click Properties.
16. Move to the Resources tab. Uncheck the Use
automatic settings box. Change the value assigned
to the Settings based on entry to Basic Configuration
0001, if this is not already set correctly.
17. For each resource type in the list on this page, set the
values as follows:
Interrupt Request 10
Direct Memory Access 3
Direct Memory Access 7
Input/Output Range 0220-022F
Input/Output Range 0300-0301
Input/Output Range 0380-038B

  ! ,.



 
     Confidential

 
 


The settings are changed by selecting the resource

type, then clicking the Change Setting button. In
the Edit Interrupt Request dialog assign the correct
value and press OK. When all values are correct
press OK to return to the device manager window
and then OK again to exit the configuration. Reboot
when prompted.
18. Return to the Device Manager window after the
reboot. Check the values for the Creative AWE64
16-bit Audio, by looking at the same screen.
19. Check the resource assignments for the Creative
AWE64 Wavetable MIDI device and the Creative
Gameport Joystick device. The resources are as
follows:
Creative AWE64 Wavetable MIDI
Basic Configuration 0000
Input/Output Range 0220-022F
Input/Output Range 0220-022F
Input/Output Range 0220-022F
Creative Gameport Joystick Basic Configuration
0000
Input/Output Range 0200-0207
Change the values to these if necessary using the
same method as outlined in steps 15-17.

,/ "# $!%& '()*

Confidential


 
    

 
 



!""

  # 

 
 

On the TMI P133 training systems, a bug in the current
version of the ghost program manifests itself after the
cloning process is complete and the system is being
rebooted on the newly cloned hard drive. The system will
not boot from the hard drive, because Ghost has incorrectly
reconstructed the boot sector. The work around, if
necessary, is as follows:
1. Boot from the MSS Installation Floppy Disk. At the
boot menu, select option 4 DOS prompt No
drivers.
2. At the DOS prompt, run the command: fdisk /mbr
3. To complete the process you will need a copy of
Partition Magic version 3.xx (you will have to obtain
this locally). Run pqmagic.exe
4. Ensure that the C: partition has the focus, then select
the resize menu option.
5. Make a note of the starting cluster size in the Resize
Partition dialog. This will be 16 K on the TMI P133
system.
6. Give the partition a new size that is less than the
original, by a nominal amount, say 5 MB less.
7. Reset the Cluster size back to its original value,
this is very important. If this is not done, Partition
Magic will by default convert the filesystem to
FAT32 and Windows NT will not be accessible.
Press OK to complete the process.
8. Repeat the resizing operation (steps 5-7) on the C:
partition, but this time increase the size so there is no
free space after the partition.
9. Exit Partition Magic.
10. Reboot the system.

  ! ,0



 
     Confidential

 
 


The system installation can then continue as normal.

 $  

The drivers for the Audio system are only installed under
Windows 95. They are not installed under Windows NT
because Windows NT does not handle Plug and Play ISA
devices in a manner that can be cloned. Also we do not
want you running multimedia applications on the system
during real-time acquisition and processing. Currently no
MSS software makes use audio card’s features.

 
The system is configured for a monitor that supports 1024
x 768 pixels and 65,536 colors at a refresh rate of 75 Hz.
Should the monitor that is supplied locally not fit this
specification, on booting into Windows 95, no display may
be seen when you would expect the Password Entry
Screen, or the system may hang or the screen may be
completely unreadable. Windows NT will change to VGA
mode automatically.
1. The display is readable when in Windows 95/NT or
is in VGA mode in Window NT, then proceed to
Step 3.
2. If the system hangs or is completely unreadable, you
must restart the system. On the selecting “Microsoft
Windows” at the boot prompt, immediately press
[F8] to bring up a Windows boot selection menu.
Choose Safe Mode.
3. Right click on the background screen and select the
Properties option on the context menu. Go to the
Settings page and click Advanced Properties. Select
the Monitor page and select Change. When presented
with a list of devices, select the Show All button and
select your monitor from the list. If your monitor is
not on the list just cancel all the way out. After
selecting the monitor, click OK. Back at the

,1 "# $!%& '()*

Confidential


 
    

 
 


Advanced Properties dialog click Apply. Change to

the Adapter page and change the refresh rate to 75
Hz and click Apply. When warned about changing
the refresh rate, select the default answer on the
dialogs after the screen refreshes select Yes if the
screen is viewable or No if it was not. Exit from the
display setup screens by selecting OK as
appropriate.
The PC is now configured and ready to use.

  %


 &' 

(
The following rules apply to selecting appropriate sizes:
1. The new size for Partition 1 should not be larger than
the old size of 1992 MB.
2. The new size for Partition 2 should be set to take up
all additional space on the drive. For example the
new total drive size is 6000, with Partition 1 set to
1992, then Partition 2 would be set to (6000 - 1992)
4008 MB.

Note: Under no circumstances should the free

space on the new drive sum to a negative
number.

 
The image is laid out such that Partition 1, drive c:, has
Windows 95 on it for use as an MSS client system whose
role is to run DSeries/HPUTILs, perform tool
configuration, plot production and provide supplemental
graphs output. This computer is assigned the name 2of3
and an IP address of 147.108.0.222.
Partition 2 on the image, drive d:, has Windows NT on it
for use as the MSS server system whose primary role is in
real-time tool communication and monitoring and data

  ! ,



 
     Confidential

 
 


storage. This system is assigned the name 1of3 and an IP

address of 147.108.0.221.
In a typical field configuration there will be two PC
systems, on booted in Windows NT and one booted in
Windows 95. Therefore, no system renaming is necessary
by default.

)
 
1. Before re-installing on a possibly corrupt file system
make backups from HPUTIL/DSeries and of the
MSS data via the menu entry Save MSS Data to Zip.
It is preferable if the backup occurs while the MSS
database is not in use (i.e., while MSS applications
are not running).

Note: Backing up the MSS data while the database

is in use could cause data loss and/or poor
system performance over this time period.

2. Perform an installation as noted in the previous

section.
3. After rebooting the installed system, restore the
HPUTIL/DSeries data from backup, and the MSS
data using the Restore MSS Data from Zip menu
option.

  
  


In the event that one of the computers fails, run the system
in Windows NT. Reboot into Windows 95 when you have
to perform tasks, that can only be done under Windows 95
in DSeries/HPUTILs, until a replacement arrives.

, "# $!%& '()*

Confidential


 
    

 
 


#  # 
Zip Drive or CD-ROM Malfunctions
In the event that one of these devices fails, you can use the
equivalent drive from the other system as a resource.
In Windows Explorer, select Network
Neighborhood\xxx\yyy and right click to bring up the
context menu and select the Map Network Drive option
(where xxx is the other computer’s name and yyy is the
shared drive). In the following dialog set the drive letter to
an unused value, and optionally set the reconnect on logon
checkbox. In Windows NT, there will also be a connect As
entry, which you can leave empty.
The relationship of shared drives to physical drives is by
default as shown in the Table 1-1.

Table 1-1 Defaults

Windows 95 Windows 95 Windows NT Windows NT

Share Share
Drive A --- Drive A ---
Drive C C Drive C C
--- Drive D D
Zip Drive D Zip Drive ZIP
CD-ROM CDROM CD-ROM CDROM
Drive

Data Exceeds the Size of the Zip Drive

Manually backup each of the selectable components from
the backup scripts “Save MSS Data to Zip” and “Restore
MSS data from Zip”. If the size of an individual file
exceeds to the capacity of the Zip Disk you will need to
contact your local technical support group.

  ! ,



 
     Confidential

 
 


After a New Installation the System Automatically

Reconfigures Devices
This can happen if the adapter cards are not in the correct
locations in the PC, the cards are not jumpered correctly,
the PC BIOS or SCSI BIOS is not correctly configured, or
the chip set versions on the cards are different to those in
the master machine.
System locks up and I have to power cycle
The version of Windows 95 installed on these systems will
usually detect if windows was incorrectly shutdown and
will run the scandisk program during boot-up to check and
fix any problems. If it finds problems this is usually
because files were in use when the system locked up and
were not closed properly. In some cases, portions of these
files will be lost. Scandisk will try to save these lost files
follow its instructions. It will write these lost files into the
c:\ directory, you should look at the contents of these files
to try to see if you can identify their origin. Usually, this
process is not a problem as it can also identify parts of files
that were no longer in use. However, in some cases this
might leave you with a non-functioning system, so be
prepared to have to restore the data; e.g., from backups.

 
There are currently two system configurations supported:
• DCI system, with a Trenton CPU on a Trenton
backplane, for field systems.
• TMI system, with a TMI P133 CPU on a TMI
backplane, for training systems only.


!"
The following summarizes the adapter card layout in the
two system configurations. These cards must be in these
slots to ensure correct operation, cards not mentioned here,
such as the filter card have set positions but these are not

,
"# $!%& '()*
Confidential


 
    

 
 


critical to the systems operation. See Table 1-2.

Table 1-2 Card Layout

DCI System, Trenton

TMI System, TMI Backplane
Backplane
Slot # Card
Slot # Card

1
2 13
3 12
4 11
5 Creative Labs 10 Creative Labs
6 9 ARCnet
7 8
8 ARCNET CPU
9 Parallel/Serial
Fan Out
10 CPU
11 1
12 NIDAQ 2 Comtrol
13 Comtrol Serial S1
Fan Out
S2
S3 NIDAQ
S4

  ! ,



 
     Confidential

 
 


#$$$%&
'( 

AMI BIOS version 1.15.
The CMOS configuration program is accessed during boot
by pressing the [Del] key.
Standard
CMOS Setup Floppy Drive A 1.44 MB 31/2
Floppy Drive B Not Installed
Primary Master Not Installed
Secondary Slave Not Installed
Secondary Master Not Installed
Secondary Slave Not Installed
Boot sector
Virus Detection Disabled
Advanced
CMOS Setup Quick Boot Disabled
1st Boot Device Floppy
2nd Boot Device Disabled
3rd Boot Device Disabled
Try Other Boot Devices Yes
Initial Display Mode BIOS
Display Mode At
Add-on ROM Init Force BIO
Floppy Access Control Read-Write
Hard Disk Access Control Read-Write
S.M.A.R.T For Hard Disks Enabled
Bootup Num-Lock On
PS/2 Mouse Support Enabled
Primary Display VGA/EGA
Password Check Setup
Boot to OS/2 No
L1/L2 Cache WriteBack
System BIOS Cacheable Enabled
Cache BUS ECC N/A
C000, 16k, shadow Disabled
C400, 16k, shadow Disabled
C800, 16k, shadow Disabled
CC00, 16k, shadow Disabled
D000, 16k, shadow Disabled
C400, 16k, shadow Disabled
C800, 16k, shadow Disabled
DC00, 16k, shadow Disabled
Advanced
Chipset Setup USB Function Enabled
USB KB/Mouse Legacy Support Enabled
EDO DRAM Speed Auto
EDO Read Burst Timing x333
EDO Write Burst Timing x333

,- "# $!%& '()*

Confidential


 
    

 
 


EDO RAS Precharge 4 clks

EDO RAS to CAS 3 clks
MA Wait State Slow
SDRAM Timing Latency Auto
RAS to CAS 3 Clks
RAS Precharge 3 Clks
VGA Frame Buffer USWC Enabled
PCI Frame Buffer USWC Enabled
DRAM Integrity Mode Non ECC
Fixed Memory Hole Disabled
TypeF DMA Buffer Control1 Disabled
TypeF DMA Buffer Control2 Disabled
DMA-0 Type Normal ISA
DMA-1 Type Normal ISA
DMA-2 Type Normal ISA
DMA-3 Type Normal ISA
DMA-4 Type Normal ISA
DMA-5 Type Normal ISA
DMA-6 Type Normal ISA
DMA-7 Type Normal ISA
AGP Aperture Size 64 MB
System Type Auto
USWC Write I/O POST Auto
PAC Bus SERR# Enabled
AGP Common SERR# Enabled
AGP System Error Forwarding Enabled
AGP Parity Error Response Enabled
IRQ 12 Mouse
PIIX4 SERR# Enabled
USB Passive Release Enable Enabled
PIIX4 Passive Enabled
PIIX4 Delayed transaction Enabled
Master Lat. Timer 40H
MTT 20H

  ! ,.



 
     Confidential

 
 


Power
Management
Setup ACPI Aware OS No
Power Management/APM Disabled
Power Button Function On/Off
Instant On Support Disabled
Green PC Monitor Power State Stand By
Video Power Down Mode Disabled
Hard Disk Power Down Mode Disabled
Hard Disk Time Out(minute) Disabled
Standby/Suspend Timer Unit 4 min
Standby Time Out Disabled
Suspend Time Out Disabled
Slow Clock Ratio 50-62.5%
Display Activity Ignore
Device 6 (Serial Port 1) Ignore
Device 7 (Serial Port 2) Ignore
Device 8 (Parallel Port) Ignore
Device 5 (Floppy Disk) Ignore
Device 0 (Primary master IDE) Ignore
Device 1 (Primary slave IDE) Ignore
Device 2 (Secondary master IDE) Ignore
Device 3 (Secondary slave IDE) Ignore
PCI/Plug
and Play Setup On Board LAN Enabled
On Board Video Ènabled
On Board SCSI Enabled
Plug and Play Aware O/S No
PCI Latency Timer (PCI Clocks) 64
PCI VGA Palette Snoop Disabled
PCI IDE Bus Master Enabled
OffBoard PCI IDE Card Auto
OffBoard PCI IDE Primary IRQ Disabled
OffBoard PCI IDE Secondary IRQ Disabled
DMA Channel 0 PnP
DMA Channel 1 PnP
DMA Channel 2 PnP
DMA Channel 3 PnP
DMA Channel 4 PnP
DMA Channel 5 PnP
DMA Channel 6 PnP
DMA Channel 7 PnP
IRQ5 PCI/PnP
IRQ9 PCI/PnP
IRQ10 PCI/PnP
IRQ11 PCI/PnP
IRQ15 PCI/PnP
Reserved Memory Size Disabled
Reserved Memory Address C000

,/ "# $!%& '()*

Confidential


 
    

 
 


Peripheral Setup OnBoard FDC Enabled

OnBoard Serial Port1 3F8h
OnBoard Serial Port2 2F8h
Receiver Polarity Non-Inverted
Transmitter Polarity Non-Inverted
OnBoard Parallel Port 378
Parallel Port Mode ECP
EPP Version N/A
Parallel Port IRQ 7
Parallel Port DMA Channel 3
OnBoard IDE Disabled

#$$$%&((
'(

 
Adaptec AIC 7880 SCSI BIOS version 1.26.
The Adaptec BIOS is not accessible during boot-up (unlike
the TMI systems). You must boot into DOS from the install
disk using the DOS prompt No drivers option and run the
cfg7880 program. Alternatively reboot windows into
DOS, from the  

 menu.
SCSI Bus Interface
Definitions
Host Adapter SCSI ID 7
SCSI Parity Checking Enabled
HOST Adapter SCSI Termination Low ON/High On
Boot Device Options
Boot Target ID 0
Boot LUN Number 0
Boot Device Options
0 1 2 3 4 5 6 7
Initiate Sync yes yes yes yes yes yes yes yes
Maximum Sync Rate 40.0 40.0 40.0 40.0 40.0 40.0 40.0 40.0
Enable Disconnection yes yes yes yes yes yes yes yes
Initiate Wide Negotiation yes yes yes no yes no yes yes
Send Start Unit Command no no no no no no no no
Include in BIOS Scan yes yes yes no no no no no
8 9 10 11 12 13 14 15

Initiate Sync yes yes yes yes yes yes yes yes
Maximum Sync Rate 40.0 40.0 40.0 40.0 40.0 40.0 40.0 40.0
Enable Disconnection yes yes yes yes yes yes yes yes
Initiate Wide Negotiation yes yes yes yes yes yes yes yes
Send Start Unit Command no no no no no no no no
Include in BIOS Scan no no no no no no no no

  ! ,0



 
     Confidential

 
 


Advanced Configuration Options

Plug and Play SCAM Support Disabled
Reset SCSI Bus at IC Initialization Enabled
Host Adapter BIOS Enabled
Support Removable Disks Boot Only
Extended BIOS Translation Enabled
Display CTRL A Enabled
Multiple LUN Support Enabled
BIOS Support for Bootable CD-ROM Enabled
BIOS support for INT 13 extensions Enabled
Support for Ultra SCSI Speed Enabled

The maximum sync rate can only be set to 40 after the

Support for Ultra SCSI Speed is enabled.

)$$
'( 

TMI BIOS version 4.05a.2.1k. This is not the version used
in the MSS-II systems. The version used in the MSS-II
configuration will not work with MSS-III, without being
upgraded.
Basic Options
Floppy Disks Onboard Floppy Controller Enabled
Drive A Type 3-1/2 Inch 1.44 MB
Drive B Type Not Installed
Floppy Seek During Post Disabled
Fixed Disks IDE Controller Setup Primary(1F0-1F7)
Auto Detect IDE Drives Enabled
Large Disk DOS Compatible Enabled
Keyboard Typematic Sound Disabled
Keyboard Typematic Delay 250ms
Keyboard Typematic Rate 30 chars/sec
Shadow RAM Shadow Select Address C000:0
Shadow Select Length 32K
Shadow Select Status SHADOW
Shadow Select Address C800
Shadow Select Length 2k
Shadow Select Status ROM
Shadow Select Address E000:0
Shadow Select Length 64K
Shadow Select Status SHADOW
Shadow Select Address F000:0
Shadow Select Length 64K
Shadow Select Status SHADOW

,1 "# $!%& '()*

Confidential


 
    

 
 


Boot Options 101 Keyboard Numlock at Boot Enabled

Set Boot Drive Sequence Diskette drive, hard drive
CD-ROM drive
Report POST Errors Enabled
Report Option ROM Errors Enabled
Show F2 Message For Setup Enabled
Quiet Boot Enable/Disable Disabled
Password Edit Password Options Disabled
Advanced Options
Serial Ports 16550 Compatible UART 1 03F8h/IRQ4
16550 Compatible UART 2 02F8h/IRQ3
Parallel Ports Select Parallel Port Address 0378h IRQ7
Parallel Port Mode ECP Mode
Parallel Port DMA DMA Channel 1
Redirection Serial Redirection Destination Disabled
Memory Cache External Cache Enabled
Advanced ChipsetDRAM Speed 70ns
DMA Alias Disabled
ECC/Parity Config Parity
Memory Gap Block Size Disabled
IO Recovery 8 Bit I/O Recovery time 4.5 SYSCLK
16 Bit I/O Recovery time 4.5 SYSCLK
ISA Guaranteed Access Time Disabled
Delayed Transactions Enabled
Bus Speed Set ISA Bus Speed 8.25 Mhz
Miscellaneous Speaker Config Enabled
Watchdog Timer Delay 1.2sec
Allocate USB Resources Disabled
PS/2 Mouse PS/2Mouse Config Disabled
PCI Options
IRQ Setup PCI IRQ Line 1 IRQ9
PCI IRQ Line 2 IRQ12
PCI IRQ Line 3 IRQ15
PCI IRQ Line 4 Disabled
PCI Devices Nothing to configure
PCI Performance Delay for PCI Config Disabled
PCI Latency for Bus 0 Device 13
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 14
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 15
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 16
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 17
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 18
Minimum Guaranteed PCI clocksAuto
PCI Latency for Bus 0 Device 19

  ! ,



 
     Confidential

 
 


Minimum Guaranteed PCI clocksAuto

PCI Latency for Bus 0 Device 20
Minimum Guaranteed PCI clocksAuto
PCI Cache Line Size
Number of 32 bit words per line Auto
Onboard SCSI Onboard PCI SCSI Enabled

)$$((
'( 

Adaptec AIC 7870 BIOS version 1.2, accessed by pressing
[CTRL][A] during boot-up when prompted.
SCSI Bus Interface Definitions
Host Adapter SCSI ID 7
SCSI Parity Checking Enabled
HOST Adapter SCSI Termination Low ON/High ON
Boot Device options
Boot target ID 0
Boot Lun Number 0
Boot Device
Configuration 0 1 2 3 4 5 6 7
Initiate Sync Negotiation yes yes yes yes yes yes yes yes
Maximum Sync Transfer
Rate 20.0 20.0 20.0 20.0 20.0 20.0 20.0 20.0
Enable Disconnection yes yes yes yes yes yes yes yes
Initiate Wide Negotiation yes yes yes yes yes yes yes yes
Send Start Unit Command no no no no no no no no

SCSI Device ID #8 #9 #10 #11 #12 #13 #14 #15

Initiate Sync Negotiation yes yes yes yes yes yes yes yes
Maximum Syn
Transfer Rate 20.0 20.0 20.0 20.0 20.0 20.0 20.0 20.0
Enable Disconnection yes yes yes yes yes yes yes yes
Initiate Wide Negotiation yes yes yes yes yes yes yes yes
Send Start Unit Command No No No No No No No No
Advanced Configuration Options
Host Adapter BIOS (Configuration Utility reserves BIOS space Disabled
Support Removable Disks Under BIOS as Fixed Disks Disabled
Extended BIOS Translation for DOS Drives > 1 GByte Enabled
Display <CTRL A> Message during BIOS initialization Enabled
Multiple LUN support Disabled
BIOS Support for More than 2 drives Enabled

, "# $!%& '()*

Confidential


 
    

 
 


*  
!"" 

*& 
1. Upgrade Memory to 160 MB, by replacing the
lowest two SIMM’s with the new 64 MB SIMM’s.
Leave the upper two slots filled with the pre-existing
16 MB SIMMs.
2. To accommodate the MSS configuration changes,
the peripheral boards in the computer must be
rearranged to match the layout previously described
for TMI P133.
3. Install the IDE hard drive upgrade if required. A
minimum 2.5 GB hard drive is required.

+*& 
Update TMP P133 Flash BIOS.
In the MSS-II configuration the BIOS version was
v4.05a.1.2d, this will be upgraded to v4.05a.2.1k. The
update procedure is as follows:
1. Reboot on the TMI Upgrade Floppy Disk and select
option 2 Load Flash BIOS Update to BIOS Version
4.05a.2.1k. Proceed to the point where you are
prompted to press [ENTER] to flash the new BIOS
onto the CPU.
2. Change switch #3 on the DIP switch block to the
CLOSED (ON) position.
3. Proceed to flash this BIOS image onto the CPU card.
4. Allow the CPU to reboot.
5. You will see a message indicating that default
configuration loaded. Press the [F2] key during the
memory test to enter the CMOS setup routine.
6. Once in the CMOS setup routine, place Switch #3
back to the default OPEN (OFF) position.

  ! ,



 
     Confidential

 
 


7. Press [ESC] from the CMOS setup program to save

and reboot the CPU with your CMOS configuration.

& '( 

To make the CMOS settings consistent between systems, a
CMOS image is written back from floppy disk to CMOS,
the CMOS image will only work with BIOS version
4.05a.2.1k. The update procedure is as follows:
1. After completing step 7 of the Flash BIOS Update,
the system will reboot on the TMI Upgrade Floppy
Disk.
2. Select option 1 Load CMOS Configuration for BIOS
Version 4.05a.2.1k.
3. After the CMOS is updated, remove the TMI
Upgrade Floppy Disk.
4. Press any key to reboot from the hard disk with this
new CMOS configuration.

& ((
'( 

1. After completing step 4 of the CMOS Configuration
Update, and the system is rebooting simultaneously
press the [CTRL][A] keys, when the “Adaptec AIC-
7870 BIOS V1.2 for the P5000HX” text appears on
the screen. This will let you enter the SCSI BIOS
configuration routine.
2. Enter the “Configure/View Host adapter Settings”
menu.
3. Press [F6] to set default settings.
4. Enter the “Advanced Configuration Options” menu.
5. Change the option Support Removable Disks under
BIOS as fixed Disks to disabled.
6. Press [ESC] twice. When prompted, save the
changes.

,-
"# $!%& '()*
Confidential


 
    

 
 


7. Place the TMI Upgrade Floppy Disk in the floppy

drive.
8. Press [ESC], answer yes to exit and press any key to
reboot.

$'$,-.
 
The IRQ and I/O addresses used by the card have changed
from those used in MSS-II, details are given elsewhere in
this chapter. The update procedure is as follows:
1. After completing step 8 of the SCSI BIOS
configuration, the system will reboot on the TMI
Upgrade Floppy Disk. Select option 3 Load 3COM
Configuration.
2. After the automatic changes are complete, remove
the TMI Upgrade Floppy Disk and press any key to
reboot from the hard disk.
The upgrade is complete.

  ! ,-



 
     Confidential

 
 


+  ,,
 &-.)(

Communication between the MSS computer and the
HAZARA can be either via RS-232 serial cable or ARCnet
fiber optic cable. It is expected that only ARCnet
communication should be necessary. The preparation of
the HAZARA requires the OPTO22 kernel (the M4RTU
operating software) and the MSS Strategy (programmed
flow chart for data acquisition) to be downloaded.
Normally this will only ever be done at the Customer
Service Center (CSC). However, in the unlikely event that
the kernel or strategy become corrupt, this operation may
have to be performed at the wellsite.

 

All fiber optic connections are keyed. Always make sure
that the key and spline are aligned and never force a
connector on. Always make sure that all fiber optic
connections are clean and dry, cleaning with isopropyl
alcohol if necessary. Always replace dust covers to
disconnected fiber connectors.
HAZARA
Make sure that the fiber optic Transmit (TX) and Receive
(RX) connections in the HAZARA are connected to the
correct TX and RX ports on the M4RTU.
TMI
Connect the other end of the fiber cable from the HAZARA
(via the fiber spool and junction boxes) directly into the
ARCnet card, TX on top and RX on bottom.

*
' //01( "
2
Turn off the power and the purge air supply to the
HAZARA and open the door. Remove the black cover to
the M4RTU unit, exposing the jumpers. Configure the
jumpers, if the jumpers are currently set for standard
,-- "# $!%& '()*
Confidential


 
    

 
 


operation this only involves placement of the E/R jumper

to the On position and the X1 to the Off position. The
jumper setting configuration for downloading via ARCnet
is shown in Table 1-3 note positions of E/R and X1):

  ! ,-.



 
     Confidential
 ,-/

 

Table 1-3 Jumper Settings for Downloading Strategy via ARCnet

E/R Aut X0 X1 H0 H1 0 1 2 3 0 1 2 3 4 5 6 7
o

off off on off on off off on on on on off off off off off off off
Confidential



 
    
"# $!%& '()*

 



 
 


Turn the HAZARA power on. If power is applied using the

purge bypass key, ensure all necessary hot work permits
and wellsite precautions are satisfied.

* 
0
On the MSS, run the OptoTerm program:

  
  
  

Highlight the HAZARA_ARCNET entry.
Start the download flash files option:
  

  
The Download File pop up appears.
If necessary, move to the correct directory. The required
directory is c:\Opto22\OptoKrnl.


Select All Controllers.
Files of type:
Select the file:
o41rtuB2.2g
Or the latest file found on the INTEQ: Surface Signal
Processing Bulletin board in the message MSS: Latest
Kernel for SARA or HAZARA.
Open the file:

Acknowledge:

The Flash Download File window appears. The progress
of the load file, controller initialization and controller
programming events, is displayed. Ignore the “Error Code
4192, Forth Dictionary is incomplete” message if it pops
up at the end of the Kernel download.

  ! ,-0



 
     Confidential

 
 


Turn off the power to the unit and install jumper at X1

before powering up to load the strategy.
Exit the OptoTerm window:
  
* 
( "
On the PC run the OptoControl program:

  
  
  



Open the strategy file:
  

Go to the directory c:\inteq\res\ctl\sara.
Look in:
Select the correct Strategy file.
sara.cdb
Open the strategy file.
Open
The strategy is opened and is displayed in the OptoControl
window. Open the Configure Controllers window:

!"


The Configure Controllers window appears.
Select (highlight) the HAZARA_ARCNET entry. Set
HAZARA_ARCNET controller as Active:

 #$%
Acknowledge:
OK
Download the strategy:
&
  '
The Controllers memory is cleared and a prompt is

,-1 "# $!%& '()*

Confidential


 
    

 
 


displayed asking if you want to continue downloading the

strategy:
Acknowledge:
(
The strategy is downloaded to the M4RTU.

(
( "+
32'4
The strategy now needs writing to M4RTU EPROM to
allow flash reload of the strategy after power downs. From
the OptoControl Window:
Write the strategy to flash:


 
%
 

After the strategy is written to EPROM, a message is
displayed indicating a successful store in Flash EPROM.
Acknowledge the prompt and exit the OptoControl
Window.
Acknowledge:

Exit the OptoControl window:
  
The final step is to return the M4RTU jumpers to settings
to the normal operation positions.
Turn the HAZARA power off and place the E/R jumper to
the Off position and the X1 to the On position.
The position of the jumpers for normal operation should be
as shown in Table 1-4.

  ! ,-



 
     Confidential
 ,-

 

Table 1-4 Jumper Settings for Normal Operation via ARCnet

E/R Auto X0 X1 H0 H1 0 1 2 3 0 1 2 3 4 5 6 7

off on on on on off off on on on on off off off off off off off
Confidential



 
    
"# $!%& '()*

 



 
 


Replace the black cover to the M4RTU.

Close up the HAZARA and turn On the power and the
purge air supply.

*
01( "(5
Download of kernel and strategy via serial cable should
never be required, but is included for completeness. The
procedure is similar to the strategy and flash downloading
via ARCnet cable, with the following exceptions.
The physical connection is via a special serial cable. This
has a pluggable 7 pole terminal strip, (P/N 67536-007) at
one end and a female DB-9 serial connector at the other.
See Figure 1-1.

To Comm. Port To Comm. Port

or M4RTU or TMI

DB-9
Pluggable 7 Pole
Terminal Strip

    


 
 

 

Connect the pluggable 7 pole terminal strip to COM port 0

on the end of the M4RTU and the DB-9 connector to COM
port 1 on the PC (DB-9 connector on CPU board).
Configure the jumpers for serial download, positions as
follows (note the E/R, X1 and H1 positions). See
Table 1-6.

  ! ,-



 
     Confidential
 ,.

 

Table 1-6 Jumper Settings for Serial Download

E/R Auto X0 X1 H0 H1 0 1 2 3 0 1 2 3 4 5 6 7

off off on off on on off on on on on off off off off off off off
Confidential



 
    
"# $!%& '()*

 



 
 


In the OptoTerm program, select HAZARA_SERIAL

prior to downloading the kernel with the Download Flash
Files option.
In the OptoControl program, select and set
HAZARA_SERIAL as the active controller prior to
downloading the Strategy.

0*16

Reversing of ST connectors:
Some, (very few), early release cabin junction boxes had
the TX and RX labelling reversed. There is also the
possibility that the ST connections in the HAZARA may
have inadvertently been connected in reverse. If
everything is powered up and it appears that the
connections are correct, and the green LED on the PC
ARCnet card is not illuminated, try reversing the ST
connections on the ARCnet card.
Strategy file (sara.cdb) fails to be loaded into OptoControl:
The strategy file may fail to load into OptoControl,
prompting with a message that the strategy is already open.
This is the result of a previous abnormal termination of the
program. When a strategy is opened, two files, sara.$cdb
and sara.locCDB are written in the c:\Inteq\Res\ctl\sara
directory. On normal termination of the program they are
removed, with abnormal termination they may not be. To
overcome the problem use Windows Explorer to delete the
sara.locCDB file.
Jumper Removal and Significance:
The following gives a summary of the jumper
configuration. The settings indicated in bold are the default
settings for normal operation of the M4RTU with MSS.
• The E/R jumper controls whether the unit will run
from RAM (In) or from EEPROM (Out).

  ! ,.



 
     Confidential

 
 


• The Auto jumper controls whether Auto-boot is

enabled (In) or disabled (Out).
• The X0 jumper controls whether the unit runs in
Binary (In) or ASCII (Out) mode.
• The X1 jumper controls whether the unit will boot
to kernel (In) or to loader (Out).
• The H0 and H1 control whether communication will
be through COM0 (H0 In, H1 In) or via ARCnet
(H0 In, H1 Out).
• The block of jumpers 0 through 3 are used to set the
serial baud rate. The speed employed in the above
procedure is 115200.
The block of jumpers 0 through 7 are used to set the
ARCnet address. Each jumper represents a bit. The address
is set by adding all the bits together (e.g., an address of 255
would be represented by having all eight jumpers on).
Bit In 0 1 2 3 4 5 6 7
1 2 4 8 16 32 64 128
Each ARCnet node must have a unique address. The MSS
standard default for the HAZARA address is 1 (i.e., jumper
in position 0 On, 1-7 Out). The address on the ARCnet
card is similarly set using the dip switches 1 through 8
(accessible from the rear of the PC). The standard address
of the ARCnet card is 3; i.e., switch 1-6 Closed
(to the right), switch 7 & 8 Open (to the left).
To avoid loss of jumpers after removal, replace the jumper
onto a single pin of the pair from which it was removed.
Serial Controller Configuration:
Serial controllers may only be configured for COM Port 1
or 2 on the TMI COM ports 3 through 10 (i.e., the Rocket
Port COM ports) cannot be used.

,.- "# $!%& '()*

Confidential


 
    

 
 


/
 

After a unit is rigged up there are a number of procedures
that should be performed to check communication
between all the components of the MSS system. The
following section assumes that all components are
installed and powered up.

 0 


"66
Table 1-3 summarizes the normal operating states of the
various indicator LEDs.

Table 1-3 Normal LED Indicators Status

LED Normal State

3Com Hub Status (top) On, Green, optical idle received

(normally just the ProPanel
ADAM segment)
Status Off, (the port has not been
(bottom) partitioned)
AUI Off, (the segment has not been
partitioned)
Packet Intermittent Yellow flash
whenever a data packet is
received by the Hub
Collision Off, very occasional yellow
flashing is acceptable indicating
a data packet collision
Power On Green indicating the unit
has power applied

  ! ,..



 
     Confidential

 
 


Table 1-3 Normal LED Indicators Status

LED Normal State

ARCnet Receive (left) On, Green

Card
Right Flickering On, Red

(*
6
Use the ping command to establish that there is a TCP/IP
connection between the various computers on your
network.
On the system, open a DOS command shell:

  
 
 

for (Windows NT).

  
  &
)


for (Windows 95).
Ping echo of the other machines on your network, a
response similar to that below indicates a good connection:
D:\>ping sd1of3
Pinging 2of3 [147.108.0.222] with 32
bytes of data:
Reply from 147.108.0.222: bytes=32
time<10ms TTL=128
Reply from 147.108.0.222: bytes=32
time<10ms TTL=128
Reply from 147.108.0.222: bytes=32
time<10ms TTL=128
Reply from 147.108.0.222: bytes=32
time<10ms TTL=128
A response like this, indicates a problem:
D:\>ping sd1of3
Pinging 2of3 [147.108.0.222] with 32 bytes of data:
Request timed out.
Request timed out.

,./ "# $!%& '()*

Confidential


 
    

 
 


Request timed out.

Request timed out.
This establish proof of a connection in a single direction
only. The process should be repeated from each computer
to every other computer involved in the network. This will
help establish that the correct IP address have been
assigned to the network adapter and have been entered into
the hosts file correctly.

66((("
By default the MSS system running under Windows NT
will map the C: drive from the MSS client system running
under Windows 95 to the L: drive.
The MSS system running under Windows 95 will map the
C: drive from the MSS client system running under
Windows NT to the M: drive and the D: drive to the N:
drive.


6(66
Run DSeries on the offline system and enter some
Drillstring components and Bottom Hole Assembles
information, save and exit. Run DSeries on the online
system and verify the previously entered data.

)  
)1

-.)2 & 3)*(
It is necessary to check the ARCnet communications with
both PC systems. This is to ensure that in the event of any
subsequent failure, the backup system will function
correctly. First connect the ARCnet ST connectors to the
ARCnet card on the offline system, after the test return the
fiber optic connectors to the online system and repeat the
test.
Start the ReadOpto program.

  
  *+, &

-
   

  ! ,.0



 
     Confidential

 
 


The Status: line at the bottom of the screen should briefly

display the message:
Trying to open comms port,
please wait…
At this point the RTU Temperature: display line should
indicate the correct temperature. Note that this is the
internal temperature of the M4RTU and as such can be
expected to vary from the ambient air temperature.

/
  
It is assumed that this check is being performed prior to rig
up and that the HAZARA unit is close enough to the
computers to allow manual sensor activation within
viewing distance of the computer screen. Note that at this
point, since calibration is unknown, when checking the
analog channels you may not see much variation in the
sensor converted units values, so look for changes in the
voltages on each channel.
Connect the sensors via LEMO connectors to the
HAZARA unit and start the ReadOpto program.

  
  *+, &

-
   

Block Height and Rig Heave Digital Channels:

Rotate the sensors first in one direction, and after a few
seconds in the opposite direction. The Counts should be
seen to increase and decrease in the 
$. -/ and
&


/ data fields.
RPM Digital Channel:
Holding the RPM sensor away from any close proximity to
metal, repeatedly swipe a metal object such as a crescent
wrench to and fro, close to the target face of the sensor. The
&/ data field should display an RPM value. After you
stop, the RPM value should return to zero.

,.1 "# $!%& '()*

Confidential


 
    

 
 


Encoder Calibration Switch Digital Channel:

Open the ReadOpto, Digital Sensor Calibration window
and select the Start Calibrating button:
 

!
  
'
"
 '
Click the two way calibration switch a few times in each
direction. A new line should appear in the calibration table
for each click of the switch. Note the character code in the
(2 column of the window. LC should appear for Layer
Change switch clicks and HT should appear for Height
switch clicks. Select the OK button to exit the calibration
window.
Hookload Analog Channel:
Place a metal rod through the hookload sensor and tighten
down the clamp. The -

.
 / data field voltage should
be seen to vary.
Spare (Standpipe Pressure) Analog Channel:
The Spare analog channel is the channel assigned to
Standpipe Pressure on the discontinued SARA
configuration of the OPTO22 unit. Connect the pressure
transducer to this channel. Using the tip of your finger or a
soft blunt instrument press the pressure diaphragm, (take
care not to damage the diaphragm). The
 
/ data field voltage should be seen to vary.
Torque Analog Channel:
Take a magnet and swipe it around the inside of the torque
sensor. A small voltage variation should be seen in the

0/ data field. Exercise common sense when
handling magnets inside the unit and make sure that you
keep them well away from any magnetic media such as
floppy or Zip disks.

  ! ,.



 
     Confidential

 
 


   $   4+


This set of tests is to be performed under Windows 95.
1. Connect the Cables from the computer COM ports to
Channel A and B connectors on the Module. Connect
the Module to the Pod.

Note: Use only the specific Black PowerComms 12

pin LEMO cable.

DO NOT use Sensor 12 pin LEMO cables since there

are critical differences between the wiring of the
two.
2. Connect the Power cable to the Module.

&' 7
DO NOT connect the Pod to the MWD tool until the
Pod has been powered up and gone through its self
test cycle. With some tool configurations, an error
condition will be generated by the Pod if it is
connected before power up.

3. Turn on the main power switch on the PowerComms

Module.

  
  *+, &

-
  &1



Once the main window appears, click on the green plug
short cut button, or:


  

$

This will activate the Pod/Tool Communication window.
Click on the Call Pod button in the lower left hand corner.
This action will check the communication between the
computer and the MWD PowerComms Module and Pod.

,. "# $!%& '()*

Confidential


 
    

 
 


86
When this procedure is complete, the following message
will appear in the main MWD PowerComms window:
COMM 1 initialized
PowerComms channels A and B set
to 8 bit mode
MWDCom line set to 38400 baud
DOS line set to 38400 baud
COMM 2 initialized
COMM 2 (CHAN B) <-- MwdCom
COMM 1 (CHAN A) <-- DOS
When this message is displayed, the MWD PowerComms
hardware and software are properly assembled and
configured. If the following message is displayed:
COMM 1 initialized
PowerComms channels A and B set
to 8 bit mode
MWDCom line set to 38400 baud
DOS line set to 38400 baud
COMM 2 initialized
COMM 1 (CHAN B) <-- MwdCom
COMM 2 (CHAN A) <-- DOS
This simply means that COMM 1 and COMM 2 are
reversed. This will not in any way effect the ability of
MWD PowerComms to communicate with the tool.
However, if it is desired to correctly configure the system,
either switch the cables from COMM 1 and COMM 2 or
switch the cables from channel A and channel B.

6
If the following message is displayed:
COMM 1 initialized
No PowerComms communication on COMM 1
COMM 1 closed
COMM 2 initialized
No PowerComms communication on COMM 2
COMM 2 closed
Neither COMM 1 nor COMM 2 is available
Connection ABORTED.

  ! ,.



 
     Confidential

 
 


There is a communication error. This message is followed

by a Warning box stating:
PowerComms communication error.
Communication ABORTED.
Click OK to dismiss box. Obviously, there is a problem in
the hardware setup in the MWD PowerComms. The
following troubleshooting steps should be followed:
1. Is the power light on?
2. Is the power switch flipped in the on (up) position?
3. Is the 4 pin Bendix Power Cable secured into the AC
Input 120 V/240 V receptacle?
4. Is the 4 pin Bendix power cable plugged into a live
120 V or 240 V socket?
5. Are the 7 pin LEMO to DB 9 cables in their
appropriate location? (i.e., Channel A to COMM 1
and Channel B to COMM 2).
6. Is the 12 pin LEMO Module to Pod cable properly
connected from the Module to the Pod?
7. Is a LED error message flashing on the Pod’s pulse
or flow lights?
Once the previous steps have been followed, attempt
communication with the Pod by clicking on the Call Pod
button, located in the lower left hand corner of the Pod/
Tool Communication window.

6
If COMM 1 and Channel A are connected without COMM
2 and Channel B connected, the following message will
appear:
COMM 1 initialized
PowerComms channels A and B set to 8-
bit mode
MWdCom line set to 38400 baud
DOS line set to 38400 baud

,/
"# $!%& '()*
Confidential


 
    

 
 


COMM 2 initialized
PowerComms communication on COMM 1
(CHAN A) only
“MWDCom” will not be available while
using DOS functions.
Although single line communication will work, it is
suggested to establish dual-line communication. To
correct this problem, connect the 7 pin LEMO connection
to Channel B and the DB 9 connection to COMM 2.
If COMM 2 and Channel A are connected without COMM
1 and Channel B connected, the following message will
appear:
COMM 1 initialized
No PowerComms communication on COMM 1
COMM 1 closed
COMM 2 initialized
PowerComms channels A and B set to 8-
bit mode
MWDCom line set to 38400 baud
DOS line set to 38400 baud
PowerComms communication on COMM 2
(CHAN A) only
“MWDCom” will not be available while
using DOS
functions.
Although single line communication will work, it is
suggested to establish dual line communication. To correct
this problem, connect the 7 pin LEMO connection from
Channel A to Channel B and connect another 7 pin LEMO
connection from Channel A and the DB 9 connection to
COMM 1.
If COMM 1 and Channel B are connected without COMM
2 and Channel A connected, the following message will
appear:
COMM 1 initialized
PowerComms channels A and B set to 8-
bit mode
MWDCom line set to 38400 baud
DOS line set to 38400 baud
COMM 2 initialized

  ! ,/



 
     Confidential

 
 


A Warning box will then appear:

Only single line PowerComms
communication can be established. You
may have a loose connection, bad
cable, or a bad port on COMM 2.
If you want to proceed in single line mode, you must switch
the COMM 1 cable to “Host Port A” on the PowerComms
unit.
Click OK to dismiss the box. Another Warning box
appears:
PowerComms communication error.
Connection ABORTED.
Click OK to dismiss the box. If it is desired to remain in
single line mode, simply switch the 7 pin LEMO
connection from Channel B to Channel A. Or, preferably,
switch the 7 pin LEMO connection from Channel B to
Channel A and connect another 7 pin LEMO connection
from Channel B and the DB 9 connection to COMM 2.
Finally, if COMM 2 and Channel B are connected without
COMM 1 and Channel A connected, the following
message will appear:
COMM 1 initialized
No PowerComms communication on COMM 1
COMM 1 closed
COMM 2 initialized
PowerComms channels A and B set to 8-
bit mode
MWDCom line set to 38400 baud
DOS line set to 38400 baud
A Warning box will then appear:
Only single line PowerComms
communication can be
established. You may have a loose
connection, bad
cable, or a bad port on COMM 1.
If you wish to proceed in single-line
mode, you must

,/- "# $!%& '()*

Confidential


 
    

 
 


switch the COMM 2 cable to “Host Port

A” on the
PowerComms unit.
Click OK to dismiss the box. Another warning box
appears:
PowerComms communication error.
Connection ABORTED.
Click OK to dismiss the box. If it is desired to remain in
single line mode, simply switch the 7 pin LEMO
connection from Channel B to Channel A. Or, preferably,
switch the 7 pin LEMO connection from Channel B to
Channel A and connect another 7 pin LEMO connection
from Channel B and the DB 9 connection to COMM 2.

'/ #   %





Ethernet is a network system that uses Bus (coaxial cable
medium) or star (twisted pair or fiber optic medium)
topologies. It was developed by Xerox and is largely
accepted and endorsed by most computer vendors.

95
Coaxial Ethernet is called 10BASE2, referring to 10 Mbps
(speed), BASEband (transmission) 185 meters (maximum
length), although it should be noted that the actual
maximum length is only 185 meters. Connectors used with
10Base2 cabling are BNC.
The Ethernet Bus must be made up of, in effect, one
continuous cable, terminated at each end with a 50 Ohm
terminator. The Bus is actually made up of a number of
cables connected together with BNC “T” connectors,
which allow devices to be connected to the bus. Wherever
possible, attach the computers NIC or transceiver directly
to the “T”. A short piece of RG58 coaxial cable can be used

  ! ,/.



 
     Confidential

 
 


to link between the “T” and the NIC/transceiver as long as

it does not exceed 18 inches in length.

&' 7
DO NOT use RG59 cable or 75 Ohm terminators,
which are typically used for video signals. They
may appear to work but will result in a degradation
of the network reliability and efficiency.

To check for suspected faults in the physical medium, try

systematically isolating sections of the Bus, by
disconnecting and terminating at that point, and then
verifying if the fault still exists.
You can check that the terminator is OK by measuring the
resistance between the center pin and the outer casing. The
resistance should be about 50 Ohm.
Note that as soon as you remove a terminator or break the
bus the entire network segment will be down and
communication with all hosts lost. There should be no
problem doing a quick disconnect for a few second; e.g.,
long enough to change out a terminator or insert another
section of cable.

*
Twisted pair Ethernet is called 10BaseT, referring to 10
Mbps (speed), BASEband (transmission) Twisted pair
cable. The maximum recommended segment length is 100
meters. Connectors used with 10BaseT cabling are RJ-45.
The cable type is also referred to as UTP derived from
Unshielded Twisted Pair.
The network is made up of one or more hubs
(concentrators), with twisted pair segments running to each
network connection in a Star arrangement. Note that
unshielded twisted pair cable has strict specification of at

,// "# $!%& '()*

Confidential


 
    

 
 


least 2 twists per foot. This is to prevent crosstalk (signal

echoing) between the conductors.

Note: DO NOT use other 8 wire cables with RJ-45

connectors such as those made up for serial
communication. Although they may appear
to work, in actual fact they will result in a
degradation of the network reliability and
efficiency.

To support 10BaseT connections requires a minimum of

category 3 twisted pair cabling, to support 100BaseT
connections requires a minimum of category 5 cabling.

+5' 65
Fiber Optic Ethernet is called 10BaseFL, referring to 10
Mbps (speed), BASEband (transmission) Fiber optic
Link. The maximum recommended segment length is 2
kilometers. The fiber cables are terminated with ST type,
bayonet connectors. The network is made up of one or
more hubs (concentrators), with a pair of fiber optic cables
(transmit and receive), running to each network
connection.
Fiber optic cabling is based on a continuous strand of very
fine glass which uses light to carry information. Fiber optic
medium is able to carry very high levels of data for great
distances. It is completely free of EMI/RFI interference.
Fiber optic cable is also a more secure medium, being
immune to electronic eavesdropping.

)
ARCnet uses Bus (co-ax cable medium) or star (fiber optic
cable medium) topologies. It is a proprietary network
system designed by Datapoint Corporation. ARCnet uses
Token Bus techniques. A Token is special data message
that is sequentially passed around a network and represents
permission to send data. ARCnet transmission speed is 2.5

  ! ,/0



 
     Confidential

 
 


Mbps (somewhat slow by networking standards). Token

bus is regarded as being particularly suitable for the
industrial environment.
MSS utilizes fiber optic cabling for ARCnet
communications. The cable runs, in effect, directly
between the two ARCnet nodes (M4RTU in the HAZARA
unit and ARCnet card in the TMI computer). ST bayonet
connectors are used to connect to the nodes. The use of
fiber optic cable allows a long distance (up to 2 km)
between nodes. Fiber optic medium is also completely free
from EMI/RFI interference.

 -

*6
The standard Network Interface Card (NIC) used with the
systems based on the Trenton CPU board, is the onboard
DEC 21143 NIC. This only has a twisted pair, RJ-45
connection. It supports 10BT and 100BT connections, but
the software images are set for the lowest common
connections, 10BaseT. There is no configuration program
for the DEC 21143 NIC, unlike the previous 3C509B
cards, this is a true Plug and Play interface.
In the TMI P133 systems the 3Com 3C509B combo card is
used, as was also present in the MSS-II configuration of the
TMI, but its configuration is different. This card does not
correctly support Plug and Play, and this feature must be
disabled for Windows 95/NT to run correctly.

,/1 "# $!%& '()*

Confidential


 
    

 
 


Table 1-4 Network Interface Card

MSS-III MSS-II

I/O Base Address 240 200

IRQ 15 10
Boot PROM Disabled Disabled
Transceiver Type Auto Detect Auto Detect
Network Driver Windows or OS/2 Windows or OS/2
Optimization Client Client
Maximum Modem Disabled Disabled
Speed
Plug and Play Disabled Disabled
Capability
Maximum Interrupt 500 ms 500 ms
Time
I/O Synchronous Disabled Disabled
Ready Capability

The configuration can be set by:

Boot from the installation floppy disk
At the prompt select option 4, DOS
prompt No drivers
cd 3com
mss3
or
Boot from the installation floppy disk
At the prompt select option 4, DOS
prompt No drivers
cd 3com
3c5x9cfg
view and set the parameters manually

  ! ,/



 
     Confidential

 
 


If the onboard DEC 21143 NIC fails, this will require a

replacement PC. There are no specific diagnostics tests that
can be run on the network interface other than the ping tests
described elsewhere in this chapter.
In the case of the 3COM card, the user could reconfigure
the card to use a specific port (AUI, RJ-45, Coax) in effect
overriding the cards automatic selection of a port. The
3c5x9cfg program allows for tests of the card,
independently of the Windows operating system. The tests
are outlined in the Verification & Validation notes.


A media converter is used in the MSS configuration. It is
located inside the Azonics ProPanel. It converts the ST
connection fiber optic signal to RJ-45 connection 10BaseT
signal which is then routed into the NIC RJ45 port. The
Media converter requires an external power supply. In the
ProPanel, this is obtained from the Azonics 12 volt power
supply.

6
A transceiver is a device that transmits and receives the
data packets to and from the network and the network
medium. Most network cards will have onboard
transceivers and each system includes transceivers. It may
be preferable to use the externals as defaults to save the
NIC from damage. In these instances the device will have
a DB-15 AUI (Attachment Unit Interface) network port.
The transceiver connects to the AUI port. The connection
from transceiver to network medium will be either RJ-45,
BNC, or ST.
On some transceivers there may be an SQE Test switch or
jumper. This should ALWAYS be in the OFF position.
There are too many different types of transceivers to list all
the possible status LED conditions. On many transceivers
there will be a Link LED, which should be on (usually

,/ "# $!%& '()*

Confidential


 
    

 
 


green) if the network connection is good. The best way to

check if a transceiver is causing a problem is to swap it out
with a known good transceiver. Some devices have ports
for both transceiver (AUI port) and direct connections
(BNC and/or RJ45). In this case you can try removing the
transceiver completely and connect directly to the NIC’s
BNC connector. The NIC will have to be reconfigured to
use this port (see Checking NIC’s above).

+5' 65364
A 3Com Fiber Optic Hub is included in the MSS
HAZARA kit. This hub has 6 pairs of fiber optic ST
bayonet connectors and 1 AUI port. The primary function
is to connect the 10BaseFL segment of the Ethernet
network to the unit segment of the network. The unit
segment will generally be 10Base2, although on some
locations it may be a clients own installed 10BaseT
segment. The hub requires no configuration other than
simply making all the physical connections.
Segment Partitioning:
The 3Com hub provides automatic segment partitioning.
This is a mechanism that isolates segments that generate
excessive errors, thereby maintaining the integrity of the
rest of the network. Conditions that will cause segment
partitioning are as follows:
• Detection of 64 consecutive collisions on a
segment: A collision is when two data packets are
sent to the network at the same time. A low level of
data collisions is to be expected. This is because
Ethernet uses Carrier Sense Multiple Access with
Collision Detect (CSMA/CD) protocol. Before a
device sends a data packet to the network, it checks
to see if any other station is active (carrier sense). If
yes, it waits until the cable is free before sending the
packet. If two devices send a packet at exactly the
same time, a collision will occur. In this case,
transmission is immediately halted and after a

  ! ,/



 
     Confidential

 
 


small, randomly generated time interval, then

transmission is restarted.
• Incorrectly terminated coaxial segment: If the AUI
segment of network is connected to an incorrectly
terminated coaxial bus, then that segment may be
partitioned. A typical MSS installation will have a
coaxial segment attached to the AUI port. This
segment must be made up of a single Bus
(backbone), terminated at each of the two ends with
a 50 W terminator.
• A transceiver is connected with SQE Test enabled:
Some transceivers have SQE test capability built in.
This is turned on by either a switch or jumper. SQE
test should NEVER be enabled on any transceiver.
Status LEDs:
There are two rows of status LEDs, one pair for each of the
six fiber optic segments. The top row are green and the
lower row are red. Under normal operation the top LED
should be on for any active connection. If any of the bottom
row of LEDs comes on, it means that segment has been
partitioned.
AUI LED:
The AUI LED is red and should not normally be on. If it
does come on it means that the AUI segment has been
partitioned.
Packet LED:
The packet LED will flash yellow whenever a packet is
received from any of the network ports. If the LED does
not flash, then no packets are being received by the hub.
Collision LED:
The collision LED flashes any time a packet collision is
detected on any of the segments connected to the hub.

,0
"# $!%& '()*
Confidential


 
    

 
 


Power LED:
The power LED is green and will be on whenever a correct
power supply is supplied to the unit.
Table 1-5 shows the various error conditions of the status
LEDs on the 3Com Hub and indicates the corrective
actions that should be performed to try and remedy the
error condition.

Table 1-5 3Com Hub Status LED Error Conditions

Error
LED Corrective Action
State

Status (top) Off • Check Tx and Rx connections

are not reversed (try reversing
them).
• Try connecting to a different
port on the 3Com hub.
• Try connecting via a different
channel (drill floor and unit
fiber boxes.
• Cycle the power and reboot the
connected computer (usually
ProPanel).
Status On, red • Segment has become parti-
(bottom) tioned. Try another port on the
hub.
• Cycle power on the connected
computer
(usually the ProPanel).
• Replace media converter on
connected computer
(usually the ProPanel).
• Replace NIC on connected
computer
(usually the ProPanel).

  ! ,0



 
     Confidential

 
 


Table 1-5 3Com Hub Status LED Error Conditions

Error
LED Corrective Action
State

AUI On, red • AUI segment has become parti-

tioned, check segment physical
aspects, all connections are
good and there is no damage to
the cable (normally co-ax).
• Check 50 Ohm terminators (one
at each end only), ohm out from
center pin to outside casing
resistance should be approxi-
mately 50 Ohm.
• Check transceiver firmly seated
and latched to AUI port.
• Replace transceiver if suspect.
Packet Off, Flashes • This means no data packets are
Collision yellow being received by the hub (no
direct action).
• Occasional collisions can be
expected and are acceptable.
• If collisions are very frequent,
suspect a bad NIC. Systemati-
cally remove each host and see
if the problem goes away. If it
does not, replace NIC and or
transceiver attached to that
computer.
Power Off, red • Check that the power chord is
securely plugged in, and check
any breakers.
• Check the fuse in the 3Com
hub.

,0- "# $!%& '()*

Confidential


 
    

 
 


'/ 


Ethernet communication uses the TCP/IP (Transfer
Control Protocol/Internet Protocol) suite of
communications protocols. To avoid communication
errors, each node on the network must be uniquely
identified. This is achieved using the IP address. IP
addresses are in the form xxx.xxx.xxx.xxx where xxx
represents a number between 0 and 255. Individual
networks are all assigned a unique network address, which
forms a part of the IP address. In the case of INTEQ, this
is 147.108.0.0, in other words, all INTEQ IP addresses will
start with 147.108 unless connected to a client’s network.
Since numeric addresses are difficult to remember, the
TCP/IP system incorporates a host name to IP address
database. This database is in the form of a simple ASCII
configuration file called “hosts”. It allows for the mapping
of an alphanumeric name to an IP address. The location of
this file in Windows 95 is c:\windows\host, and on
Windows NT is d:\winnt\system32\drivers\etc\hosts.
To simplify installation and operation, a standard hosts file
is used on all MSS computers, Table 1-6 illustrates their
contents:

Table 1-6 Host File

127.0.01 Loopback
147.108.0.221 1of3
147.108.0222 2of3
147.108.0.223 3of3

It is important to realize that it is generally acceptable to

use the standard addresses in the field, since in most cases
the INTEQ installation will form its own isolated mini
network. However, if the computers are connected to

  ! ,0.



 
     Confidential

 
 


another INTEQ LAN (Local Area Network) such as in the

CSC or local office, the IP addresses will have to be
changed. This is to avoid two computers with the same IP
address being on the same network, which would result in
network errors and a failure to communicate correctly
between hosts. In this case it will be necessary to contact
your local network administrator to get IP address
assignments.

 '/ '  

*.,
1. You should first change the IP address/names
assigned in the c:\windows\hosts file to match those
that will be entered in the Network configuration
screens. Unmap any mapped drives.
2. Right click on the Network Neighborhood icon on
the desktop and select Properties.
3. Select the Identification tab on the Network dialog
and set the new value for the Computer Name.
4. Select the Configuration tab on the Network dialog.
In the list of components, select the  2* 

$
 $
 33452 ' 362
366' 

 entry and then
click Properties.
5. On the TCP/IP properties sheet, on the IP Address
tab assign the IP address and subnet mask. Select
OK. You may need to assign values to others tabs on
the TCP/IP properties sheet, ask local technical
support for help on this.
6. On the Network dialog, select OK.
7. When prompted Reboot the system.
8. Re-map the shared drives that were disconnected in
step 2. In Windows Explorer, select Network
Neighborhood\xxx\yyy and right click to bring up

,0/ "# $!%& '()*

Confidential


 
    

 
 


the context menu and select the Map Network Drive

option (where xxx is the other computer’s name and
yyy is the shared drive). In the following dialog set
the drive letter to an unused value, and optionally set
the reconnect on logon check box. In Windows NT,
there will also be a connect As entry, which you can
leave empty.

* 
1. You should first change the IP address/names
assigned in the d:\winnt\system32\drivers\etc\hosts
file to match those that will be entered in the
Network configuration screens.
2. Unmap any mapped drives. In Windows Explorer
right click on the drive, for example drive L:, and
select Disconnect. Make a note of the mapping you
will need to reconnect these later.
3. Right Click on the Network icon on the desktop and
select Properties.
4. Enter the new value for * !$
  

 + and select OK. If necessary
also change the work group or DOMAIN entries.
5. Go to 

$
   2* 

$
 

  * # 3 and enter the new
values for the IP Address and subnet mask and
default gateways, and click OK. You may be
required to change other entries within the TCP/IP
Properties screen, ask local technical support for
help on this.
6. Click OK on the Network dialog. Depending on the
extent of the configuration changes you may or may
not be asked to reboot the computer, if prompted do
this. If not prompted to reboot it is still advised to
reboot the system yourself.
7. Select
   and enter the following
command to run.

  ! ,00



 
     Confidential

 
 


%SystemRoot%\system32\musrmgr.exe
8. In the User Manager program, select the IUSR_1OF3
user on the list.
9. In the User Manager program, select 7 
.
10. In the rename dialog, change the name to
IUSR_XXXX, where XXXX is the new name of the
computer.
11. Select OK.
12. In the User Manager program, select the
IWAM_1OF3 user on the list.
13. In the User Manager program, select 7 
.
14. In the rename dialog, change the name to
IWAM_XXXX, where XXXX is the new name of
the computer.
15. Select OK.
16. Exit the User Manager.
17. Select
   and enter the following
command to run.
%SystemRoot%\system32\mmc.exe%SystemRo
ot%\System32\inetsrv\iis.msc
18. In the Microsoft Management Console, select the
Internet Information Server node in the tree-view on
the left portion of the screen, and right click and
select Connect.
19. Assign to the Computer Name entry, the new name
of this computer.
20. Click OK.
21. The Internet Information Server should now have a
tree-view that includes a Default Web Site and
Default FTP Site.

,01 "# $!%& '()*

Confidential


 
    

 
 


22. Select the Default Web Site and right click and select
Properties.
23. Go to the $

$      
#
 #

 #$$  7 and
set this to the IUSR_XXXX account you just
renamed.
24. Select OK to close all the dialog boxes.
25. In the Microsoft Management Console, select the
Default FTP Site, and right click and select Stop.
26. Select the Default FTP Site, and right click and
select Properties.
27. Set the value of
$ #$$
  7
to the IUSR_XXXX account you just renamed.
28. Select OK to close all the dialog boxes.
29. In the Microsoft Management Console, Select the
Default FTP Site, and right click and select Start.
30. Exit the Microsoft Management Console.
31. Start Notepad.exe and load a copy of the file
c:\tools\convert.reg for editing. It will look will look
this:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\INetStp]
"AnonymousUser"="IUSR_1OF3"
[HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\Al
ertManager\Recipients]
"Recipient0"="Type:\"Network Message\"
Priority Level:\"1\"
Recipient:\"1OF3\" "
32. Change the references to 1OF3 to the new name of
this computer and save the file.
33. In Windows Explorer Select c:tools\convert.reg file
and right click and select Merge.

  ! ,0



 
     Confidential

 
 


34. Re-map the shared drives that were disconnected in

step 2. In Windows Explorer, select Network
Neighborhood\xxx\yyy and right click to bring up
the context menu and select the Map Network Drive
option (where xxx is the other computer’s name and
yyy is the shared drive). In the following dialog set
the drive letter to an unused value, and optionally set
the reconnect on logon check box. In Windows NT,
there will also be a connect As entry, which you can
leave empty.

2
As with the Ethernet IP addresses, each node on an ARCnet
network must be assigned a unique address. In the MSS
implementation, a point to point topology is used. This
means that only two ARCnet nodes will be directly
connected (the M4RTU in HAZARA and the ARCnet card
in the computer). Ensure that these two nodes have unique
addresses in the range of 0 through 255.
The standard ARCnet addresses for MSS and jumper/
switch configurations are illustrated in Table 1-7 & Table
1-8.

,0 "# $!%& '()*

Confidential


 
    



 
    
  !

 

Table 1-7 ARCnet Card Computer Address Configuration

Device Address Dip Switch Position

1 2 3 4 5 6 7 8
ARCnet 3 Closed Closed Closed Closed Closed Closed Open Open
Card
Confidential

Table 1-8 M4RTU (HAZARA) ARCnet Address Configuration

Device Address Jumper Position

 


1 2 3 4 5 6 7 8
HAZARA 1 On Off Off Off Off Off Off Off
(M4RTU)
,0

 
 


•Notes•

,1
"# $!%& '()*
Confidential


 
    
  2


Chapter 2 covers an overview of the MSS

directory structure and the depth tracking
system.

+


   

With the release of MSS III, pulse detection and decoding
are performed on the Windows NT platform, (making the
OS-9000 ADAM computer of MSS I & II obsolete). The
naming convention of previous systems is no longer
appropriate. Since MSS III and MSS IV software were
developed with a time overlap it was decided that a naming
convention was required that would encompass all
subsequent MSS releases. So, a simple numeric naming
convention was derived.
The two main MSS computers are named 1of3 and 2of3,
where the first number in each name indicates the
computer identifier and the second number indicates the
MSS phase. Table 2-1 explains the naming convention.

  ! -,



 
     Confidential

 
 

Table 2-1 Computer Descriptions

Computer Description

1of3 Real time computer (Windows NT) of MSS-III

2of3 Offline computer (Windows 95) of MSS-III
3of3 Remote computer (Windows 95) of MSS-III
4of3 Second remote computer (Windows 95) of
MSS-III
1of4 Real time computer (Windows NT) of MSS-IV
2of4 Offline computer (Windows 95) of MSS-IV

For MSS III, some of the legacy 16 bit software, 1of3 will
always be booted up in Windows NT and 2of3 will always
be booted up in Windows 95. The two computers are
identical, so either can be booted up in Windows 95 or NT.
Whichever one is booted up in NT will boot as 1of3 and the
other computer is booted up in Windows 95 will be 2of3.
If the you attempt to boot both in the same operating
system, and on the same network, the system will detect a
duplicate computer name/IP address causing abort loading
of the network service software.

 6"(6
The main INTEQ directory structure is as follows:
C:\Inteq_
|_ \Res MSS Software/Files
|_ \RigLink RigLink Internet Browser Software/Files
|_ \RigLinkServer RigLink Server Software/Files

The MSS III software is always installed on drive C: (the

Windows 95 FAT partition), regardless of whether the
computer is booted in NT (1of3) or Windows 95 (2of3,
3of3 etc.). All INTEQ software is loaded into the root

-,- "# $!%& '()*

Confidential


 
    

 
 

directory C:\Inteq. There are two main INTEQ products

installed, MSS and RigLink. Since these are distinct
packages they are installed in separate directories. MSS is
based on the RES database structure and is thus installed
under C:\Inteq\Res. RigLink comprise two services,
Server and Client. The server software is installed in the
c:\inteq\RigLink\Server. All the required files for the client
server are installed in c:\inteq\RiglLink.

2((56"(6
The Res directory has seven subdirectories for
applications, control files, miscellaneous user documents,
database, symbols and logo files, and miscellaneous
temporary files.
C:\Inteq\Res_
|_ \Bin
|_ \Ctl
|_ \Data
|_ \Database
|_ Documents
|_ \symb
|_ Tmp


The bin (binary) directory contains all the compiled and
batch script executable files. The
  
 
&

menu shortcuts all point to these executable files. If
you add a shortcut to the Desktop it should point to one of
the files in this directory.
The Directory also has one subdirectory called System.
This contains all the compiled .dll (dynamic link library)
files and .hlp (help) files that are INTEQ specific. You
should not need to do anything with this directory.


The Ctl (Control) directory contains all the control or
configuration files, which are commonly flat ASCII files

  ! -,.



 
     Confidential

 
 

that can be viewed using a text editor. Under normal

circumstances these files Should Not be edited. Reference
is made here in case of an emergency situation whereby
you may be instructed by Technical Support to modify one
or more of the files. There are five filename extensions
commonly used within MSS to identify particular types of
files, namely .cfg (configuration), .ctl (control), .cvt
(conversion), .dat (data), and .log (log). The function of
each file is outlined in Table 2-2.

Table 2-2 Configuration Files

Extension Description of File Type

.cfg Files that contain configuration data that changes;

usually selected or entered by you from within an
application setup or properties option.
.ctl Files that contain predetermined control data that
determine how an application will act or deal with
specific data or input. These files are fixed at the
time of release and should NOT be changed.
.dat Files that contain specific data used by an
application. This data may be predetermined data
or change as a result of your input from within an
application.
.log Files that are a log of messages such as error logs
or depth tracking logs that are written to an
viewable from the applications.

The Ctl directory also contains a series of subdirectories

with application specific control files.

-,/ "# $!%& '()*

Confidential


 
    

 
 

C:\Inteq\Res\Ctl_
|_ \Mobil
|_ \Mobm
|_ \Mwd_
|_ \Res
|_ \Uft
|_ \Rigdisp
|_ \rplot
|_ \sara
|_ \Wits

See Table 2-3 for a brief description of each control file.

Table 2-3 Control Files

Directory Description of File Type

\Mobil Contains configuration files for the Mobil SLS

data communications program.
\Mobm Contains configuration files for the Mobil MWD
data communications program.
\Mwd Contains files that determine how specific MWD
data words will be handled by the RtProc
application.
\Mwd\Res Contains correction curve data and data files used
for correcting and compensating MWD values for
different tool sizes and bore hole diameters.
\Mwd\Uft Contains all the UFT telemetry formats and
associated files.
\Rigdisp Contains all the RigDisp display format files
(files with .rdf file extensions).
\RLPlot Contains all the format files required for RLPlot.
\sara Contains all the configuration, strategy and
controls needed for configuring the M4RTU
processor in the SARA and HAZARA units.

  ! -,0



 
     Confidential

 
 

Table 2-3 Control Files

Directory Description of File Type

\Wits Contains the WITS application setup configuration

file.


This directory contains a series of subdirectories used for
data files created as output or export from specific
applications, usually as flat ASCII files.
C:\Inteq\Res\Data_
|_ \Backup_runs
|_ \Mobil
|_ \Mobm

Table 2-4 gives a brief description of the file contained in

each data directory.

Table 2-4 Data Directory

Directory Description of File Type

\Backup_runs Contains files exported from the RES database

by the BackRest application.
\Mobil Contains data files output by the Mobil SLS
data communications program.
\Mobm Contains data files output by the Mobil data
communications program.

5
This directory contains a series of subdirectories that
contain the RES database file and all the files necessary to
build and update the database structure and catalog data.

-,1 "# $!%& '()*

Confidential


 
    

 
 

C:\Inteq\Res\Database_
|_ \Acess
|_ \Defaults
|_ \Install

Table 2-5 gives a brief description of the file contained

database directory.

Table 2-5 Database Directory

Directory Description of File Type

\Access Contains the RES database file and a copy of the

database file with default entries only.
\Defaults Contains all the necessary files to build the RES
database and populate it with catalog data from a
new Access database.
\Mobm Contains files used to update a database structure.

6
This directory contains a miscellaneous documents for
wellsite reporting, as supplied by Operations for inclusion
on the MSS CD.

"5
This directory contains all the symbol files, such as
lithology and engineering symbols, also company logo
files used in generating various plots and reports.


This directory is for any miscellaneous temporary files.

  ! -,



 
     Confidential

 
 



((5
The MSS database (RES) is a based on the relational model
used in DrillByte and RES. Figure 2-1 shows the portion of
the model most used by the current MSS version.
The database holds both parameter (essentially static) and
sequential (dynamic) data. For the most part, the parameter
tables are populated through use of the MSS setup/monitor
program. In that program you can specify the Field,
Facility, Well and finally the Hole that is being drilled
(FIELD, FACILITY, WELL and HOLE tables).
For the field, facility and well, you can also specify
detailed information about their geographic location
(LOCATE table).
In order to get a definitive path from the surface to a
downhole location, especially where there are sidetracks,
the PATH_DESC and PATH tables are used. Each well
can have multiple PATH_DESC records. There is always
at least one PATH_DESC record for a well and a new
record is inserted every time that a sidetrack hole is started.
Since a well path can consist of more than one hole, and a
hole can exist in more than one well path, the PATH table
serves as a “join” table between PATH_DESC and PATH.
Survey reference and Sag data are stored in the
SURVEY_REF and SURVEY_SAG tables. The Operator
(Client oil company), Rig and Pump information are stored
in the OPERATOR, RIG and PUMPDETAILS tables
respectively.

-, "# $!%& '()*

Confidential


 
    

 
 
  
 !
  ! -,



 
     Confidential

 
 

For online hydraulics and torque & drag, information about

the annulus and drillstring is required. The MSS setup/
monitor program lets you setup the annulus information
which is stored in the ANNULUS and ANN_SECT tables.
There is an ANN_SECT record for each annular section.
Similarly, drillstring information is saved in the
TUBULAR_RUN and TUBULAR_ELEM tables. There is
a TUBULAR_ELEM record for each section (element
type) of the drillstring. You can enter more detailed
drillstring information for each tubular element. These are
stored in tables such as BIT, DRILLPIPE,
DRILLCOLLAR, etc., depending on the element type. The
BIT, HOLE_OPENER and UNDERREAMER tables also
have further relationships with the BIT_JETS table, with
one record for each jet used in these elements.
Sequential real time data is stored to the database, usually
on a time or depth basis. For example, GENTIME (general
time) data are stored on a regular time basis, while
DRILLDEPTH (drilling depth-based) data are stored at
equal increments of hole depth. There are two programs
which store this data: RtProc can be configured to store
GENTIME and DRILLDEPTH data records. Dlogger can
be configured to record any type of non-MWD sequential
data.
In the MWD area of sequential data, MWD_TIME
contains a record every 15 seconds that depth tracking is
on. These records serve as a depth-time array which can be
later used for depth-tagging the MWD tool memory data.
As MWD data are pulsed from the tool, the raw datawords
are stored in the RAW_MWD_GENERIC table. The
results of MWD processing of the raw data are stored in the
MWD_GENERIC table.
The results of survey processing (by SvyPrc) are stored
into SURVEY_RAW. Posted surveys (from SvyPrc) are
stored in the SURVEY table.

-,
"# $!%& '()*
Confidential


 
    

 
 

 (:
The Message Server is a program that serves two purposes:
• Interprocess communication
• Common Data Area access

 66

Message Server is used to pass messages between MSS
applications. This allows an application to inform others of
a change that has been made (for example: changes a units
conversion, posted a survey, changed the drillstring
configuration) or allows an application to request
information from the system (for example: the current
drillstring identifier).
The Message Server (MsgSvr) should be the first MSS
application started. As other applications are executed they
register with the Message Server indicating which
message types they are interested in receiving. As
messages are generated, Message Server looks at its list of
registered programs and directs the message to those who
have specified interest in that message type.
Valid MSS Message Types are stored in a configuration
file (MsgTypes.cfg) in the INTEQ ctl folder. This file
should not be moved or changed.
Various settings of the Message Server are stored in the
Msg.cfg file of the ctl folder. This file should not be moved
from that location. It should not normally be directly edited
either. Changes to the Message Server settings should be
done through the program itself.

66
The Common Data Area (CDA) is an area of shared
memory that holds real-time data values which are
available to any MSS application running on the computer.
The Message Server controls access to the CDA. Normally
there is only one CDA under Message Server control but

  ! -,



 
     Confidential

 
 

there may be more (for example: the case of a Data Center

connected to multiple rigsites).
When Message Server starts up it reads the local.def file in
the INTEQ ctl folder and uses this to build the CDA. Here
is an extract from the file:
# CDA definition file format 1.0
#
# data types: byte, int16, int32, float, double, string
#
# defining arrays: {type}[{size}]
# ex: byte[20]
#
# 'string' is a special case of 'byte', differing in conversions
# (byte is treated as a 8-bit integer value)
# ex:
# byte[20] “200” -> double 2.0
# string[20] “200” -> double 200.0
# int32 65 -> byte[20] “A”
# int32 65 -> string[20] “65”
#
# type,mnemonic,alternate, conversion id, status, group id, description
double,TIME,NONE,ZO,1,1,Time
double,WELL_ID,NONE,ID,1,1025,Well Identifier
double,PATH_ID,NONE,ID,1,1025,Path Identifier
double,HOLE_ID,NONE,ID,1,1025,Hole Identifier
double,ANNULUS_ID,NONE,ID,1,1025,Annulus Identifier
double,TUBRUN_ID,NONE,ID,1,1025,Tubular (BHA) Identifier
double,RIG_ID,NONE,ID,1,1025,Rig Identifier
double,TOOLRUN,NONE,D0,1,1025,MWD Toolrun
double,DEPTH,NONE,LD,1,1025,Depth
double,VDEPTH,NONE,LD,1,1025,Vertical Depth
double,BITDEP,NONE,LD,1,1,Bit Depth
double,VBITDEP,NONE,LD,1,1,Vertical Bit Depth
double,BLOCKUCOMP,NONE,LD,1,1,Topdrive Position Uncomp
double,BLOCKCOMP,NONE,LD,1,1,Block/Topdrive Position Comp
double,RIGHEAVE,NONE,LD,1,1,Rig Heave
double,BLOCKSEP,NONE,LD,1,1,Block Separation
double,DELTABLOCKHT,NONE,LD,1,1,Change in Block Height
double,BITVELOCITY,NONE,RP,1,1,Bit Velocity
double,ROP,NONE,RP,1,1025,Instantaneous ROP

The lines beginning with # are comments only. Following

that are the actual CDA item specifications, starting at:
double,TIME,NONE,ZO,1,1,Time

-,- "# $!%& '()*

Confidential


 
    

 
 

The first column specifies the type of data storage for the
item. This is usually “double”, meaning a double float
value. The second column gives the mnemonic used to
identify the item. The third column gives an alternate item
mnemonic (the value for the alternate is used rather than
from this item). The fourth column gives the Units
Conversion ID. Next comes the Status column
(0 for Off, 1 for On). The sixth column contains a number
which represents the groups that the item belongs to
(See CDASetup in Chapter 3 for an explanation). Finally
there is a description of the item.
The CDASetup program is used to view and configure the
CDA items and rewrites the local.def file accordingly.
Message Server periodically saves the data content of the
CDA to a file named local.rtd in the ctl folder. This is
reloaded whenever Message Server is restarted in order to
display the most recent data for CDA items. On occasion
this file may become corrupted and cause problems upon
restart. If this occurs, delete it and Message Server will
create a new one. This would also be necessary if the
local.def file is changed in terms of number or order of
items.

&("

All data values stored internally by MSS (in memory or in
the database) are in S.I. metric units. The term “SI” is an
abbreviation for 'Le Systeme International d'Unites or The
International System of Units. However, these are not
usually the units that users want to see the data displayed
in. For that reason, MSS employs a Units Conversion
System which lets you specify the types of units you want
to see for each measurement type and then takes care of
doing all the conversion between the outside world and the
internal values.

  ! -,.



 
     Confidential

 
 


Each measurement type (length, mud density, torque, etc.)
is assigned a unique two-letter conversion identifier
(conversion ID). For example, length and depth
measurements are assigned a conversion ID of “LD”, while
mud density measurements are assigned a conversion ID or
“MD”. All items in the Common Data Area or database
that are measured in terms of length or depth (such as
DEPTH, BITDEP, etc.) are assigned “LD” as their
conversion ID, while items measured in terms of mud
density (MWIN, ECD, etc.) are assigned a conversion ID
or “MD”.
The available conversion factors for each conversion ID
used in the MSS system are stored in a configuration file
(c_avail.dat) in the INTEQ ctl folder. Here is a portion of
the file:
,LD,m, 1,2,
,LD,ft, 3.280839895,2,
,LF,N, 1,0,
,LF,kN, 0.001,2,
,LF,kdaN, 0.0001,2,
,LF,kdyne, 100,2,
,LF,klbf, 0.000224808924,2,
,LF,lbf, 0.224808924,1,
,LF,kgf, 0.101971621,1,
,LF,tonnes, 0.000101971621,2,
Each line specifies the two-letter identifier, the units label,
the conversion factor (to S.I. units) and the number of
decimal places to use when a value is output.
The configuration file convdesc.dat in the ctl folder) gives
a description of each two-letter identifier. For example:
,LD,Length or Depth,
,LF,Load or Force,

-,/ "# $!%& '()*

Confidential


 
    

 
 

&+

The conversion factor file used by MSS is system.cvt
(in the ctl folder). You can configure the contents of this
file using the standard Units Conversion dialog accessible
from most MSS applications. See Figure 2-2.

  




Normally you would leave the Units Set as System Set

(for system.cvt). The Conversion Type list contains the
conversion identifiers available in the system. This list can
be ordered by ID or description. Select the identifier you
want to change and the Units list below changes to reflect
the available conversion labels and factors for that
identifier. Select a new conversion if you wish and press
Apply or OK. This immediately applies the conversion and
a UNITSCHG message is sent to the rest of the MSS
system. If other applications are registered to accept that
message (most are) and are displaying data using that

  ! -,0



 
     Confidential

 
 

conversion identifier, their displays are updated to reflect

the change. The system.cvt file is updated accordingly.
On a new job, it would be very time consuming to change
a metric system.cvt to FPS or vice versa. So, to make this
task easier, there are two configuration files (def_f.cvt and
def_m.cvt) which contain default setups of conversion
factors for a typical FPS and metric job. These serve as
starting points for a mostly FPS or metric setup which can
then be modified to suit the particular job.
This is accomplished in the MSS setup/monitor program.
On the first start-up Wizard screen there is a button, labeled
Units, which displays the window as shown in Figure 2-3.

 "  #
 $

Here you can choose to reset the system.cvt file to the

contents of one of the default files. Be careful about doing
this if you have already made modifications to the System
Set, however, since this action overwrites the current
system.cvt file.

-,1 "# $!%& '()*

Confidential


 
    

 
 

+ /


+



The depth tracking process loop is repeated once a second
whenever Depth Tracking is started. Each second, the
system checks for depth resets and setpoint changes as well
as changes of state caused by certain rig actions
(i.e., turning the pumps on or pulling the slips).
See Figure 2-4, Figure 2-5.
The system adjusts the bit depth up or down according to
the change in block height compared to the previous
cycle’s block height.
During each cycle, if the current block height is less than
or equal to the previous BH_MIN, the system will be in
“Drilling”, provided certain other criteria are met. If the
system is “Drilling”, the hole depth will be incremented by
the change in block height compared to BH_MIN
difference and the current block height will be saved as the
new BH_MIN for use in the next cycle.
BH_MIN is the minimum block height from the previous
cycle. BH_MIN is measured and stored in the background;
the user does not see the value and cannot change it. If the
current block height is equal to or below the BH_MIN, the
system will drill by the amount of change. If the current
block height is greater than the BH_MIN, the system will
go to “Reaming” or “Off Bottom”, depending on whether
the pumps are on or off.


The system will be in this state after Depth Tracking is
started. The system will remain in this state until the slips
are pulled the first time. The system will then go into either
“Off Bottom” or “Drilling”, depending on the bit depth
relative to the total depth and whether or not pumps are on
or off. The system will not go into “Reaming” from “No
Monitor”. If the pumps are on and the bit depth is less than

  ! -,



 
     Confidential

 
 

the total depth the system will be “Off Bottom”. Also, if the
pumps are off and the bit is on bottom the system will be
“Off Bottom”. The system will remain in “Off Bottom”
until the pumps are on and the bit depth is greater than or
equal to the total depth. Because the system will not have a
BH_MIN when it is first started it will not go into
“Reaming” until the system has been into “Drilling”. If the
pumps are on and the bit depth is greater than or equal to
the total depth the system will be in “Drilling”. The system
will remain in “Drilling” until the bit is lifted off bottom.


The criteria for “Drilling” are out of slips, pumps on, and
block height less than or equal to the previous BH_MIN.
The system will change out of “Drilling” if either the
pumps are turned off or when the block height is greater
than the previous minimum block height. In the former
case the system will go into “Off Bottom” and in the latter
case the system will go into “Reaming”. See Figure 2-4 and
Figure 2-5.

-, "# $!%& '()*

Confidential


 
    



 
    
  !

 

 % &'& $(
)*

  +)
Note: Initially, DT will remain in “No Note: This cycle is repeated once a
Monitor” until BH>BH_IN_SLIPS.DT Start Depth second.
then go to “Off Bottom”, not “Reaming” Tracking
until the system has been to “Drilling” BH_MIN is the minimum block height
and established a BH_MIN.
on the previous “Drilling” cycle. If the
Until in “Drilling” the first time, DT uses
other criteria are met and the blocks are
bit depth >= hole depth to determine No Monitor
“Drilling Status”. below BH_MIN, the system will be
“Drilling”.
N (Initially)
Hookload>IN In Slips
Slips Setpoint?
Y N
Y
Pump N Block Height
Confidential

Off Bottom Pressure>Circ. Passed Below

Setpoint? Low Block? N
N
Set Slips Y Y
And Pump Off
Bit Depth>= Block Height
Total Depth? Passed Above
N (Initially) Y High Block? N
Y

Block

 
Reaming Height<=BH_MIN+
N Jitter?
Y

Drilling Connection
-,
 -,-

 

 , &'& $(
)*

  +)
Start Depth
Tracking
Pump ON and Bit
Depth>=Total Depth
No Monitor Drilling
Pump
OFF BH>BH_MIN+Jitter
Pump OFF and
Bit Depth
>=Total Depth Pump ON with
or Pump ON and Bit Depth>=
Bit Depth<Total Total Depth
Depth BH<=BH_MIN + Jitter
Confidential

Pump ON or Pull Slips Pump OFF or Set Slips

with Pump ON with Pump ON
Off Bottom Reaming
Set Slips
and Pump Off
Pull Slips with Pull Slips
Pump OFF with Pump ON



 
    
"# $!%& '()*

In Slips

 
Notes: The boxes with the borders Pay attention to the and/
are the Depth System states. The BH Passed
or part of the comments.
comments along the arrows show Low Block\and
They indicate that two
the action(s) that will cause a BH>High Block
actions must occur or that
change of state Pull Slips and several actions will cause
Pull Slips and
BH<=BH_MIN Pump ON a change of state.
To use this diagram, pick the
current system state and then
find the action that occurred. Connection
Follow the arrow to the new
state.

 
 

2
The criteria for this state are out of slips, pumps on, and
block height less than or equal to the previous BH_MIN.
The only criteria different than those required for
“Drilling” state is the current block position relative to the
BH_MIN. The system will change from “Reaming” if the
pumps are turned off or the block height is less than or
equal to BH_MIN. In the former case, the system will go
into “Off Bottom” and in the later case the system will go
into “Drilling”.

'

“Off Bottom” is kind of a catch all state. Normally, the
criteria for “Off Bottom” are out of slips, pump off, and
block height greater than the previous minimum block
height. There are some cases where the system will go into
“Off Bottom” outside of these criteria. Some examples are:
When in “Drilling” and pump pressure is lost, When in
“Reaming” and slips are set with the pumps still on, When
“In Slips” and the pumps are turned on. Basically, the
system will go to “Off Bottom” if no other state applies.

( 
This state can only be reached from “Off Bottom”. The
criteria for “In Slips” are hookload less than the in slips
setpoint and pumps off. If the slips are set with the pumps
still on the system will remain in “Off Bottom” until the
pumps are off. Once the system is “In Slips”, it can go into
“Off Bottom” by pulling the slips or into “Connection” if
the block height has passed the Low Block and High Block
setpoints.

6
This state can only be reached from “In Slips”. The criteria
for “Connection” are in slips, pumps off, the block has
passed below the Low Block setpoint, and the block has
passed above the High Block setpoint. When the slips are

  ! -,-



 
     Confidential

 
 

pulled, the system measures the connection length by

subtracting the block height when the slips were first set
from the block height when the slips were pulled. This
connection length is added to the last BH_MIN to get a new
BH_MIN. The system will not leave “Connection” until
the slips are pulled and the pumps are on. The system will
then go into “Reaming” if everything is normal. If the
current block height is below the new BH_MIN the system
will go into “Off Bottom”. This is a way of preventing the
system from drilling and of letting you know that
something is wrong.

+ $/
The following is the MSS data that should be backed up:
• c:\inteq\res\database\access\res.mdb
• c:\inteq\res\data directory and all subdirectories
• files in the c:\inteq\res\ctl directory with the
following extensions .ucs .mps .ini .cvt .cda
• c:\my documents directory and all subdirectories
• Registry below the node
HKEY_CURRENT_USER\Software\INTEQ-RES
Saving and restoring MSS data is performed via the Save
MSS Data to Zip and Restore MSS Data from Zip menu
shortcuts that link to c:\inteq\res\archive.bat file.

(
6
HPUTIL offers a “Get Data” option from its main screen
that allows you to save all the files referenced in the
c:\hputil\exe\gdpf.lst file for the given job number. Data
may be saved to a Zip drive, floppy drive, or hard disk. The
c:\hputil\exe\gdpf.lst file needs to be modified to match
local file naming conventions. Restores selects from a table
of all the “archives” that can be listed on the source media.
Floppies have no selection, hard disk, Zip drive, and
networks can have multiple “archives” and a selection is

-,-- "# $!%& '()*

Confidential


 
    

 
 

required. On restore, NO files are overwritten unless the

user confirms the overwrite.
The DSeries menu offers an alternative run-by-run data
backup/restore option, with similar target drive options.
How often do I backup the data?
As a starting point, it is suggested that you keep a backup
on three different disks and to rotate through these each
time you make a backup. This strategy helps prevent the
situation where a problem is not recognized immediately,
resulting in the problem being included in the backup.
A backup should be made at least every 12-24 hours. Local
procedures may require a different time interval.

% '  -
• Accurate block height is crucial. Both bit depth and
hole depth depend on block height. Correcting your
hole and bit depth every kelly down are not
substitutes for a good calibration.
• Hole depth is not derived from bit depth in this
system. In other words, the hole depth is not equal
to the deepest bit depth seen. The hole depth is not
directly affected by changes in bit depth, even when
on bottom. Both bit depth and hole depth are
changed in two different sub-routines by comparing
current block height to two different, independent
values – previous block height and BH_MIN.
• The bit depth that is in the system on start-up is only
the starting point. The bit depth is incremented by
the change in block height compared to the previous
block height. If your block height calibration is not
very good, the bit depth will not track accurately.
• The hole depth that is in the system on start-up is a
starting point and is incremented by the change in
block height compared to BH_MIN. Again, if your

  ! -,-.



 
     Confidential

 
 

block height calibration is not good, the hole depth

will not update correctly.
• After calibrating all the sensors, you can put in the
bit depth and hole depth at any time. The system
should track the bit depth while tripping and be on
bottom at the correct place.
• In spite of statements above, the hole depth, bit
depth, and BH_MIN are interrelated to the extent
that changing one does cause the others to be
recalculated in certain instances. If the bit depth is
reset shallower while in “Drilling”, for instance, a
new BH_MIN and off bottom distance are
calculated to keep everything working. The system
will go into “Reaming” in this situation. The hole
depth can also be reset to a deeper value while in
“Reaming”, “Off Bottom”, or “Drilling”. This will
cause the recalculation of BH_MIN and off bottom
distance.
• There are safe guards built into the system to
prevent illogical situations from happening. These
include bit depth being reset to deeper than hole
depth and off bottom distance being reset to a
negative value.
• The in slips setpoint is important to connections in
that the value must be above the true in slips
hookload but also well below the actual out of slips
value. Adjusting this value up or down will slightly
change the measured length of the single. A typical
value would be 10 klb above the actual in slips
value.
• Only use “Assumed ROP” when there is no block
height sensor. If you enable Assumed ROP when
there is a working block height sensor the system
will produce incorrect values.
• A normal sequence would be: “Connection”,
“Reaming” (when pumps are on), “Drilling” (when
BH<=BH_MIN), “Reaming” (when
-,-/ "# $!%& '()*
Confidential


 
    

 
 

BH>BH_MIN), “Off Bottom” (when pumps are

off), “In Slips” (when slips are set), “Connection”
(when blocks pass the high block setpoint),...
• Another normal sequence could be (note the
comments): “Connection”, “Reaming” (when
pumps are on), “Drilling” (when BH<=BH_MIN),
“Reaming” (when BH>BH_MIN), “Off Bottom”
(when slips are set), “In Slips” (when pumps are
off), “Connection” (when blocks pass the high
block setpoint),… The sequence is the same but the
actions are slightly different.
• When you trip out of hole the system should track
the bit depth accurately, at least until you reach the
BHA. If you will be doing re-logs on the way out of
the hole you can simply leave the system alone. If
you are not doing any re-logs on the trip out you can
End Depth Tracking. If you End Depth Tracking
you will have to repeat the previous step when you
trip back in hole.

  ! -,-0



 
     Confidential

 
 

•Notes•

-,-1 "# $!%& '()*

Confidential


 
    
  3



Chapter 3 covers the various applications

used within the MSS system.

   &

(


The MSS program is used to:
• enter system parameters such as well, hole, etc.
• enter survey reference parameters
• monitor real-time applications and restart them if
necessary
MSS should be the first application started in the system
(with the possible exception of the MsgServer). If the
MsgServer is not already running, MSS starts it
automatically.


MSS starts by displaying a “splash screen” which gives
program information and status messages as the program
connects to the database and loads in current parameters.
See Figure 3-1.

  ! .,



 
     Confidential

 
-$$)


 " ! $( )

You are then led through a series of windows in order to set

up the parameters required for the MSS real time
applications to function properly:
• Database/Location setup
• Service Level setup
• Processes setup
• MWD Tool Configuration setup
• Survey Reference setup

5:!6(
The first window displayed after the splash screen is the
Database/Location setup. This is where you specify the
Client, Field, Facility, Well, and Hole properties for the
job. See Figure 3-2.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 " ! .  +)

$

The Field, Facility, Well and Hole fields are text fields
with accompanying drop-down choice lists. Click on the
arrow to the right of the text field to get a list of available
choices for each category. A “cascading” effect occurs if
you change a category choice. For example, changing the
Field will also change the Facility, Well and Hole.
Changing the Well also changes the Hole, etc.
At the top right of the window is a button (Units…) which,
when pressed, displays a window in which you can set up
the base conversion units for the job.
If all information in this window is correct, press Next to
move on to the next setup window (Service Level). Press
Cancel to quit the program.

(  *+;+6"

To enter a NEW value for a category, highlight the existing
text string and type in the new value. For example, to enter
a new WELL, highlight the text in the Well field and type

  ! .,.



 
     Confidential

 
-$$)


in a new well name. When the field is deactivated

(by clicking outside it with the mouse, tabbing to another
control, etc.), the change is accepted and a new WELL is
created. In addition, new PATH and HOLE records are
also created, using default names which are then displayed
in the text boxes in the window.

Note: You should only type directly into the text

boxes if you want to create a new record for
a category. If all you want to do is change
the name, press the Details button to the
right of the category and change the name in
the window that is displayed.

(  *

If a new hole is created (by typing directly into the Hole
text field) the program requires some extra information. To
gather this information, the following window is displayed
when the text box is deactivated (clicking outside it with
the mouse, tabbing to another control, etc.). See Figure 3-3.

 "" ! . )* / $))

The default name for the first path in the well is “Original
Path”. When a new hole is created, you have the
opportunity to name the new path (or you can simply leave
it with the default name of Sidetrack #n (where n is the next

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


sidetrack number). You must specify which path the new

hole is being sidetracked from, also the measured depth of
the kick off. The relationship between Holes and Paths is
illustrated in Figure 3-4.

 "% /  0( 

A path is a collection of holes, or a collection of sections

of holes.

  ! .,0



 
     Confidential

 
-$$)


+ 
Pressing the Details button to the right of the Field category
displays the Field Properties window. See Figure 3-5.

 ", ! .  0$

To change the Field Name, highlight it and enter a new

value.
From the Field Properties window, it is possible to call up
the Location Properties window to enter Field-specific
location information (refer to the Location Properties
section below).

Note: In this and all entry windows, an Asterisk (*)

next to a field label signifies that an entry is
required.

+6" 
Pressing the Details button to the right of the Facility
category displays the Facility Properties window.
See Figure 3-6.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


 "1 ! . ) 0$

To change the Facility Name or Water Depth, highlight the

current value and enter a new one. The water depth should
be 0 if the well is onshore.
From the Facility Properties window it is possible to call
up the Location Properties window to enter Facility-
specific location information.

 
Pressing the Details button to the right of the Well category
displays the Well Properties window. See Figure 3-7.

 "2 ! . 3 0$

It is possible to rename the Well, both a long name (up to

64 characters) and short name (up to 16 characters), and to

  ! .,



 
     Confidential

 
-$$)


enter the Lease name and Job Number. To do so, highlight

the current value and type a new value into the text fields.
From the Well Properties window it is possible to call up
the Location Properties window to enter Well-specific
location information.
The Rig Properties window can also be accessed by
pressing the Rig button.

 
Pressing the Details button to the right of the Hole category
displays the Hole Properties window. See Figure 3-8.

 "4 ! . / 0$

It is possible to rename the Hole and to enter the starting

depth (unless it is the first hole when the starting depth is
always 0 and the box is read-only). To do so, simply
highlight and change the values in the text fields.

Note: The Hole Properties window can be

accessed from either the Setup Wizard or
later from the application's Parameters
menu. In the latter case, it is possible to
open or create Annulus and Drillstring
(Tubular) records associated with the hole.
., "# $!%& '()*
Confidential


 
    

 
-$$)


!6 
Pressing the Location button on the Field, Facility or Well
Properties windows displays the Location Properties
window. See Figure 3-9.

 "5 ! . +)

0$  &+

The type of location data (FIELD, FACILITY or WELL)

is identified in the window title bar. You can enter values
in the text fields as needed for the particular reporting
requirements of the job.
When the Location Properties window is called from the
Facility or Well Properties window, an extra button
appears in the top right of the window. See Figure 3-10.

  ! .,



 
     Confidential

 
-$$)


 "6 ! . +)

0$ 3
 78

This allows the population of text fields from the “parent”

record. That is, Facility Location information populated
from Field Location information, Well Location
information from Facility Location information, etc.

2  
Pressing the Rig button on the Well Properties window
displays the Rig Properties window. See Figure 3-11.

 " ! .  0$

You can enter the names of the Contractor and Rig; also
Datum information.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


  

Pressing the Pumps button on the Rig Properties window
displays the Pump Properties window. See Figure 3-12.

 " ! . 0$ $

You can enter pump information by simply typing directly

into the fields of the table (or making choices from drop
down lists for Status and Type). The Capacity value is
calculated automatically from other entered information.
To delete a pump from the table, place the cursor in the row
to be removed and press the Delete Selected Row button.

("&( 66

Pressing the Units button on the Database/Location setup
window displays the “Initial System Units Setup” window.
See Figure 3-13.

  ! .,



 
     Confidential

 
-$$)


 "" ! . 
  #
 $

The system-wide units conversion set is stored in the file

system.cvt in the INTEQ ctl folder. Two other files,
def_f.cvt and def_m.cvt, contain default base FPS and
Metric units sets, respectively. Select the desired base units
using the radio buttons and press OK. The conversion
information from the specified file is copied into
system.cvt.

Note: This will over-write any conversion

configurations that have been entered into
the current system set and should therefore
usually only be done at the start of a job.

The standard units conversion window is displayed for

further configuration of individual units conversions.
See Figure 3-14.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "% ) 





By pressing OK in this window sends a UNITSCHG

message to the system. Any other applications which
handle this units change message (most MSS applications)
will update their displays accordingly.

(6!(
The Service Level setup window allows you to specify
what type of job is to be performed with MSS. The result
of the Service Level setup is the inclusion of specific
applications in the set that MSS will automatically start
and then monitor (once the setup sequence is complete).
See Figure 3-15.

  ! .,.



 
     Confidential

 
-$$)


 ", ! . ) +

There are three sections on the window: MWD, Surface

Logging, and DAQ/COMMS. These sections are discussed
as follows.


Check or uncheck the MWD “ON” box to specify if MWD
will be used on the job. If the box is unchecked, all other
categories in the MWD section are disabled.
Next, choose either Directional Only or Formation
Evaluation. If Directional Only, the FE categories on the
right side of the section are disabled. If Formation
Evaluation is selected, they are enabled.

Note: The selection of Formation Evaluation

causes the Surface Logging “ON” box to be
checked and disabled. This is because FE
requires the MWD Processing and Depth
Tracking functions of the real-time

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


processing application, RtProc, which is the

main application associated with Surface
Logging as well as FE. If Directional Only
is selected, the Surface Logging “ON” box
is enabled to allow you to choose it or not,
depending on requirements.

The FE subcategories currently available are MDP/CoPilot

and AutoTrak which require particular online programs to
be run.

(6! 
Check or uncheck the Surface Logging “ON” box to
specify whether Surface Logging is be used on the job. If
the box is unchecked, all other categories in the Surface
Logging section are disabled.

Note: The “ON” box will be checked and disabled

automatically if MWD is “ON” and
Formation Evaluation is selected in the
MWD section.

Options in the Surface Logging section are Dlogger (data

logging to the database) and Online Torque and Drag.

:'(
You can specify any combination of data acquisition and
communications applications to be started and monitored
by MSS.
Currently available DAQ choices are Opto (for the SARA
and HAZARA data acquisition systems) and ReadPF
(for the Pepperl & Fuchs system).
Currently available COMMS choices are WITS (Wellsite
Information Transfer Specification format) and Mobil
MWD (Mobil Data Center MWD format).
If all information in this window is correct, press Next to

  ! .,0



 
     Confidential

 
-$$)


move on to the next setup window (Processes). Press

Cancel to quit the program.

6(
The Processes setup window displays a table containing
the set of applications that the MSS program will
automatically start and monitor (as well as automatically
restart if so designated). See Figure 3-16.

 "1 ! . 0)

The application set is made of entries resulting from the

Service Level set up on the previous window, and the last
set saved (to the file userproc.cfg in the INTEQ ctl folder).
The set is saved to userproc.cfg when the Processes setup
window is exited.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


The userproc.cfg file has the following format:

MWDPrc,1
SvPrc,0
PuRead,1
RtProc,0
Dlogger,1
PFRead,1
WITS,1
where the first column is the application name and the
second column is the “restart flag” (1 to restart, 0
otherwise).
The program combines the Service Level-required
applications with the contents of this file to arrive at the
contents of the Processes table.
You can modify the table as required. Processes can be
added by choosing from the drop down list which is
displayed when the arrow at the right edge of the first
column is pressed. This drop down choice list is built from
the proc.cfg file in the INTEQ ctl folder. Processes may be
removed from the table by choosing the blank entry in the
drop down list. Finally, you can check or uncheck the
boxes in the second column to specify whether programs
should be automatically restarted if MSS recognizes that
they have terminated.
Press Next to move on to the next setup window if all
information is correct.
The next window depends on the specified Service Level.
If MWD is “ON”, the next window is the MWD Tool
Configuration. Otherwise it is the Setup Summary
window.
Press Cancel to quit the program.

  ! .,



 
     Confidential

 
-$$)


 (
The MWD Tool Configuration setup window displays
information about the current MWD Tool. See Figure 3-17.

 "2 ! .
 



Tool configuration and calibration information is entered

using DSeries which writes a file named mss2.fil in the
INTEQ hputil folder. MSS displays data from this file,
including the tool configuration in a “tree” representation.
Ensure that the run number and scribeline values are
correct. If they are not, either enter the correct information
in DSeries and re-write mss2.fil, or locate the correct
mss2.fil. The path of the current mss2.fil file is displayed.
To select another, press the Browse button to display the
standard file navigation window. See Figure 3-18.

., "# $!%& '()*

Confidential


 
    

 
-$$)


 "4 $

Once the correct mss2.fil file is found, press Open. The

location of the mss2.fil file is written to the text field in the
Tool Configuration window.
To view more detailed information about the MWD tool,
press the Configuration button. This displays the MWD
Calibration window. See Figure 3-19.

  ! .,



 
     Confidential

 
-$$)


 "5 ! .
 


 

Once again the MWD tool is represented by a “tree”

diagram, with nodes for each sensor in the tool, also nodes
for mud resistivity and density - potassium content.
Click on a node to display calibration information. For
example, if the Directional sensor node is clicked,
directional calibration information is displayed.
See Figure 3-20.

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


 "6 ! .
 



On the MWD Tool Configuration setup window, press

Next to move on to the next setup window
(Survey Reference). Press Cancel to quit the program.

("26(
The Survey Reference window is used to view/enter
information used in survey processing. See Figure 3-21.

  ! .,-



 
     Confidential

 
-$$)


 " ! .  $

Some text fields are read-only since their contents are not
manually-entered in this window. For example, the
scribeline value is read from the mss2.fil file. Similarly, the
Azimuth Reference, Declination and Grid values are set
from changes made in the Reference window, accessed by
pressing the Reference button.
The nominal Magnetic Field, Dip and Gravity values can
be manually entered here but are usually be calculated in
the BGGM window, accessed by pressing the BGGM
button.
The Magnetic Correction Type can be set to Magcorr or
None.
The Sag filename specifies the name of a file in the INTEQ
data folder (the actual filename has a .res extension). This
file contains actual and correction inclination values and is
created from within the Sag calculation window, accessed
by pressing the Sag button.

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


SUCOP setup data (including whether SUCOP is used at

all) can be accessed by pressing the SUCOP button.
If all information in this window is correct, press Next to
move on to the next setup window (Setup Summary). Press
Cancel to quit the program.

("26*
This window allows you to specify the Reference North
and declination data, and also starting well coordinates and
survey calculated method. See Figure 3-22.

 "  

) 

After entering the required data, press OK to save the

information.

  ! .,-.



 
     Confidential

 
-$$)


886*
See Figure 3-23.

 "" 9::! )



Enter the correct longitude and latitude. The date is

automatically inserted. If offshore, the elevation should be
0. If onshore, it should be above mean sea level.
Once these data values have been entered, press Apply to
perform the calculation. The results are displayed in the
table. Press OK to transfer the Gravity, Declination, Dip
and Magnetic Field values to the setup window.

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)


( 6*
See Figure 3-24.

 "%  )

Choose a Project Name (which will be used in the file

name) and enter stabilizer information into the table. Add
mud density, bit-to-sensor distance and the inclination
range over which the calculations should be performed.
Press Apply to perform the calculation. The results are
displayed in pop up window. See Figure 3-25.

  ! .,-0



 
     Confidential

 
-$$)


 ",  )



The resulting Sag file (in this example sag6.res written to

the INTEQ data folder) has the following format:

.,-1 "# $!%& '()*

Confidential


 
    

 
-$$)


!********* Baker Hughes INTEQ --- SAG correction program v. 1.1

*********
!
! Gauge [in] OD [in] ID [in] Length [ft]
! Bit : 8.000 Tubular 1 : 7.000 4.000 98.43
! Stabilizer 1 : 7.000 Tubular 2 : 4.000 3.000 196.85
! Stabilizer 2 : 6.000 Tubular 3 : 4.000 3.000 98.43
! Stabilizer 3 : 0.000 Tubular 4 : 0.000 0.000 0.00
! Stabilizer 4 : 0.000 Tubular 5 : 0.000 0.000 0.00
! Stabilizer 5 : 0.000 Tubular 6 : 0.000 0.000 0.00
! Stabilizer 6 : 0.000 Tubular 7 : 0.000 0.000 0.00
! Mud Weight : 11.00 ppg Bit to Sensor : 50.00 ft
!
! Incl. range from 5.00 deg to 90.00 deg in increments of 5.00
deg
!
$$SAG_TABLE
!
! Inclination [deg]
! actual correction
! ------------------
0.00, +0.00
5.00, +0.00
10.00, -0.00
15.00, -0.00
20.00, -0.00
25.00, -0.00
30.00, -0.00
35.00, -0.00
40.00, -0.00
45.00, -0.00
50.00, -0.00
55.00, -0.00
60.00, -0.00
65.00, -0.00
70.00, -0.00
75.00, -0.00
80.00, -0.00
85.00, -0.00
90.00, -0.00
95.00, -0.00
$$END

Press OK to dismiss the results window. The name of the

file is written back to the setup window.

  ! .,-



 
     Confidential

 
-$$)


(&'26*
See Figure 3-26.

 "1 # 0 

)  3


The check box at the top of the window indicates whether

SUCOP is to be used. If it is unchecked, no further data
entry is required. If it is checked (i.e., using SUCOP), the
text fields should be examined for correctness. The read-
only reference data at the top comes from the Survey
Reference window. The read-only Tie-In data in the
middle is read from the last tie-in survey in the database for
this hole. Finally, the lower section, the only one that you

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


can edit, contains tolerance information used by SUCOP.

The default values should usually be used.
Press OK to accept the information and return to the setup
window.

( ("
The final window in the setup sequence provides a
summary of some of the information entered in previous
windows. See Figure 3-27.

 "2 ! . 

The client and location information is shown at the top,

followed by MWD tool information (if MWD Service
Level is ON) and finally the Processes for starting and
monitoring.
Use the Back button to return to previous screens if
corrections are necessary.
Press Cancel to quit the application.
Press OK to accept the information. This is the point where
any new entered information is written to the database.

  ! .,-



 
     Confidential

 
-$$)


The designated programs are started and the main MSS

window is displayed.


The main MSS window provides a visual status of the
monitored programs and access to various setup windows
through menu or toolbar choices. See Figure 3-28.

 "4 ! 

 !



To the left of each application name is a box containing a

red cross (not running) or a green check mark (running). If
a program terminates, the system sends a “disconnected”
message to MSS. This causes the status to be changed to
“not running”. If the process is scheduled for restarting,
this is now done. MSS will attempt to restart an application
up to three times before giving up and writing a message to
the Error Log. If the process starts up OK, the system sends
MSS a “connected” message and the status is changed to
“running”.
If MSS is iconized (minimized) when status messages are
received, it restores itself to its original window size so that
the status of monitored applications can be seen.
The Error Log status is always shown as the first item on
the display. Viewing the Error Log (from the View menu)
will change the status to green. When a new error is written
to the log the status changes to red.

.,.
"# $!%& '()*
Confidential


 
    

 
-$$)


The shape of the MSS main window can be changed if

required to position it differently on the screen. For
example, it can be made long and narrow. See Figure 3-29.

 "5 ! 

 !



Or vertical as shown in Figure 3-30.

 ""6 ! 

 !



  ! .,.



 
     Confidential

 
-$$)


 4


Many of the same setup windows used in the Wizard part
of the program are accessible from menu items or
equivalent toolbar buttons. This is the case for the Tool
menu (Configuration), Survey menu (Setup), Parameters
menu (Field, Facility, Well, Hole and Rig Properties), and
Processes menu (Configuration).
One difference is the Hole Properties window from the
Parameters menu where it is now also possible to specify
the annulus and drillstring. See Figure 3-31.

 "" ! . / 0$

Note: These functions can also be accessed from

the Parameters menu directly.

The current annulus and drillstring identifiers are shown.

Use the Open or New buttons to access the current Annulus
or Drillstring, or to create a new one.

 

You can open the current annulus (for viewing or editing)
by pressing the Open button, or create a new one by
pressing the New button. See Figure 3-32.

.,.- "# $!%& '()*

Confidential


 
    

 
-$$)


 "" & -



The annulus information is entered into the table. Press OK

or Save to write the edited or new annulus to the database.

  

You can open the current drillstring (for viewing or
editing) by pressing the Open button, or create a new one
by pressing the New button. See Figure 3-33.

  ! .,..



 
     Confidential

 
-$$)


 """ &
 

The drillstring information is entered into the table. Press

OK or Save to write the edited or new drillstring to the
database.

&

You can change any of the system units conversions by
selecting the Configuration item from the Units menu (or
its toolbar equivalent). This displays the standard system
conversion units window. See Figure 3-34.

.,./ "# $!%& '()*

Confidential


 
    

 
-$$)


 ""% ) 





Pressing OK in this window sends a UNITSCHG message

to the system. Any other applications which handle this
message (most MSS applications) will update their
displays accordingly.

! ! 
You can view the Error Log, MWD Log, and Depth Track
Log by selecting the appropriate item in the View menu (or
by pressing the equivalent button in the toolbar).
The Error log contains errors generated by all applications
running on the system. The file is named error.log and is
located in the INTEQ ctl folder.
The MWD log contains information generated by the
MWD processing thread of RtProc. The file is named

  ! .,.0



 
     Confidential

 
-$$)


mwd.log and is located in the INTEQ data folder.

The Depth Track log contains information generated by the
Depth Track processing thread of RtProc. The file is named
dtrak.log and is located in the INTEQ ctl folder.


Online help can be accessed by selecting Help Topics from
the Help menu.
Application version information can be found by choosing
“About MSS” from the Help menu.

.,.1 "# $!%& '()*

Confidential


 
    

 
-$$)



 & 
(


The Message Server is used for communication between
MSS applications across processes, computers, and/or
networks. It also controls the Common Data Area (CDA)
where real time data are stored for easy access by all
applications.
Inter-application communication is accomplished by using
messages. All messages are currently of a broadcast type -
- meaning that an application sending out a message does
not specify a destination. Client applications tell the
Message Server what message types they are interested in,
and the Message Server will send them any broadcasts of
those types. As an example, if an application needs to
know when the drillstring changes, it registers this fact
with the Message Server at start-up. If the Message Server
receives a “drillstring changed” message it forwards it to
that application. Messages may be flags indicating that
some event has occurred, or they may contain data.
See Figure 3-35.

  ! .,.



 
     Confidential

 
-$$)


 "", !  !   0



Message types are defined as having two levels: a type and

a subtype. The type is a general grouping (e.g., MWD).
While a subtype is a specific message of that type
(e.g., DATAWORD). The type class and subtype together
define a unique message type. An example is
“MWD:DATAWORD” messages which are sent for raw
or calculated mnemonics. Such a message might be a dip
value, a depth value, or a raw magnetometer reading.
Also the broadcast/register scenario described above,
applications may also make REQUESTS for information.
For example, if an application wants to know the current
online hole, it can make a request for that information. If
another application has informed Message Server that it
can respond to such a request, it is routed to that application
which then responds with the requested information.

.,. "# $!%& '()*

Confidential


 
    

 
-$$)



  
Messages are defined in the control file MsgTypes.cfg in
the INTEQ ctl folder. This file should not be changed or
moved from that location.
Message Server configuration information is stored in
another file in the ctl folder, Msg.cfg. The values stored in
this file are entered using windows accessible through the
Properties item of the MsgSvr Settings menu.


 + 
You can configure Message Server to display a number of
sub-windows simultaneously. You can then arrange these
sub-windows within the main window. The following are
available from the View menu:
Client List
This window displays the client applications currently
connected to the Message Server. See Figure 3-36.

 ""1 

 +

Each row of the list gives the location (computer IP

address), name of the application, messages that the
application has registered interest in, and time of the last
message received.

  ! .,.



 
     Confidential

 
-$$)


Message Spy List

This window displays messages as they are passed through
the Message Server. See Figure 3-37.

 ""2 ! $

Each row shows the ID of the sender of the message, how

many applications have registered to receive that message,
the message type and size, and when the message was
received by the Message Server.
Message Log
This window displays the contents of the Message Log.
See Figure 3-38.

.,/
"# $!%& '()*
Confidential


 
    

 
-$$)


 ""4 ! +

Trace Log
This window displays the contents of the Trace Log.
See Figure 3-39.

 ""5
) +

  ! .,/



 
     Confidential

 
-$$)


Performance
This window displays information pertaining to the
performance of the Message Server. See Figure 3-40.

 "%6 0

)

CDAView
This is not yet implemented - this functionality is currently
in the CDASetup application.

  


Before trying to configure the Message Server application,
take a moment and note what computers need to be able to
access the server. Make a list of every computer that runs
any Message Server client applications. Record the IP
address of each client computer. For example, see
Figure 3-41

.,/- "# $!%& '()*

Confidential


 
    

 
-$$)


SERVERS CLIENTS

PC 1 PC 1
147.108.0.221 147.108.0.221

PC 2
147.108.0.222

PC 3
147.108.0.223

 "% ! 

Note that the server machine should also appear in the

client list. This is because any computer you wish to
connect to the Message Server must have an entry in the
client list.
The following setup needs to be done on each computer,
but first start on the server machine. Select the Properties
item from the Settings menu. See Figure 3-42.

  ! .,/.



 
     Confidential

 
-$$)


 "% !   

 +

A tabbed configuration window titled MsgSvr Properties

will appear. See Figure 3-43.

 "%" 

 0

.,// "# $!%& '()*

Confidential


 
    

 
-$$)


The first tab of this dialog, Clients, is displayed. This is

where you should enter the clients list you recorded earlier.
Again, any computer that needs to access the server should
be included in this list.
Before any client application is allowed to connect to the
Message Server, the IP of the computer it is running on is
checked against this list. Any client trying to connect from
a computer not in this list will be refused.
Note the three buttons above the list box. They are labeled
List, Any, and Local. Click on the List button if it is not
selected already. This allows you to enter items into the list
box. To enter a client computer, type its IP in the edit box
at the bottom and press Add. To remove a client from the
list, select it in the list and press Delete. The Any tab
allows any computer on the network to connect to the
Message Server on this computer. The Local tab allows
only clients on the local computer to connect. The best and
most secure practice is to choose List and enter the IP of
each client specifically.
Select the Servers tab. See Figure 3-44.

  ! .,/0



 
     Confidential

 
-$$)


 "%%  0

The Servers page functions exactly like the Clients page.

On this page, select the List button and enter the IP of the
server machine.
Select the CDAs tab. See Figure 3-45.

.,/1 "# $!%& '()*

Confidential


 
    

 
-$$)


 "%, - 0

Enter a name for the primary CDA in the Local CDA

Name field. This is usually a short form of the well name,
such as Rig81, or Gulf15. The Additional CDAs list
would only be used if there were multiple CDAs on the
server. For example, this might be the case in a data center.
Select the Keys tab. See Figure 3-46.

  ! .,/



 
     Confidential

 
-$$)


 "%1  0

In the Local Keys group box, click Add. See Figure 3-47.

 "%2 ; - -)) 

A small window pops up. Enter a text string in the Key

field. This is the password client computers must use to
connect to the data on this server. Example: “Rig81 key
abcdef12345” Now enter a name for this key in the
Description field. Example: “Key for Rig 81”. Click OK.
A Yes-No prompt will appear, asking if you want to copy
this key to the Remote Key list. See Figure 3-48.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "%4 $    +<

Click Yes. See Figure 3-49.

 "%5  0

There should now be an entry for your key in both the top
and bottom list boxes. The Local Keys list is the
permission list the Message Server will check incoming
clients against. The Remote Keys list is what a client
application will use to try to connect to a server.
For most purposes, you are done configuring this
computer. Click OK at the bottom of the Properties
window.
  ! .,/



 
     Confidential

 
-$$)


   
You now need to configure the client computers. Run the
Message Server on each one, following the same steps you
followed for the server machine. Make sure the key text is
the same on every computer. Once you are finished
configuring a client computer, close the Message Server
application. It should be the only time you need to run
Message Server on that computer.

 
 

Properties other than client and server access can be set on
the remaining tab pages of the Properties window:

' 5

See Figure 3-50.

 ",6 $
 0

The Options page allows you to configure the following

parameters:

.,0
"# $!%& '()*
Confidential


 
    

 
-$$)


*' 
• Allow SMC
Permits shared memory connection. This should be
ON.
• Shared Memory CDA
Permits shared memory CDA connection. This
should be ON.
• Key Check for CDA
Indicates whether key checking should be carried
out to allow access to the CDA

! ' 
• Message Logging
Log messages to a file. This should be OFF.
• Error Logging
Generates a log file of any errors encountered
• Debug Level
Indicates the level of debugging (generally 0 or 1)
to report in the logs.

  ! .,0



 
     Confidential

 
-$$)


65
See Figure 3-51.

 ", 0

) 0

The Performance page allows the setting of a number of

parameters which affect the performance of the Message
Server. You should not normally change any of these
parameters unless specifically instructed to do so.

.,0- "# $!%& '()*

Confidential


 
    

 
-$$)


+5
See Figure 3-52.

 ", !  0$

The CDAFeed tab allows you to specify which CDAFeed

client applications are allowed to connect to this Message
Server. The choices are:
• Any - CDAFeed programs can connect to this
Message Server from any computer.
• List - CDAFeed programs running on computers
whose IP addresses appear in the list can connect to
this Message Server.

  ! .,0.



 
     Confidential

 
-$$)


 + 
 &+
(


The CDASetup program is used to view and/or configure
the Common Data Area (CDA). The CDA is an area of
shared memory where all real time parameter data values
are stored for easy access by applications in the MSS
system. It contains data from the MWD tool (both raw and
processed), surface sensor data, and computed and derived
data such as depth, vertical depth, rate of penetration, etc.
As such, the CDA is the heart of the online system and the
CDASetup program allows you to observe its state at any
time.
The configuration of the CDA is stored in a file named
local.def in the INTEQ ctl folder. At start-up this file is
loaded into memory. If it is missing, the program will fail
to start. The last set of data values of the CDA is stored in
a file named local.rtd in the INTEQ ctl folder. This file is
accessed as start-up to load in this last set of data. If you
have a problem starting the program it could be that this file
has become corrupt. Delete it and the program will create
another.
Among the ways that you can interact with the CDA
through the program are:
• turning items on and off
• assigning one item to another
• manually entering the value for an item
When started, the following main window is displayed as
shown in Figure 3-53.
The window is made up of several distinct areas:
A The menu bar. All program functions are accessible
through the menu bar.
B The toolbar. The buttons are shortcuts to menu
items. Hold the cursor over a button momentarily to

.,0/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "," - $ !

3


get a brief description.

C The controls area.
D The CDA table display.
E Status bar where application messages are
displayed.
To quit the application, choose Exit from the File menu or
click the close box in the top right of the main window.
Select a group and press OK. On the main window, if a
group is being displayed, the group name is shown above
the table. If the entire CDA is being shown, no group name
appears. Select a group and press OK.
To search for a CDA item, type the starting characters of
its mnemonic into the Find box. The CDA table view
scrolls to items whose mnemonic matches those starting
characters.
The table displayed in the main window may be the whole
CDA or a subset (Group) of it. To select a different Group

  ! .,00



 
     Confidential

 
-$$)


(or the whole CDA), choose Groups from the Options

menu to display the following window shown in
Figure 3-54.

 ",%  $. ' :$

+ #  +

The CDA data items are displayed in a tabular form, each
row of the table representing a CDA item and each column
representing an attribute of an item. The columns
(attributes) are:
Mnemonic
The identifier for a CDA item.
On
Indicates whether the item is currently ON (new values are
displayed as they are made available) or OFF (no
automatic update of the value). You may need to turn an
item OFF and enter a default value if a sensor fails and
must be repaired. Check the box to turn the item ON.
Uncheck it to turn the item OFF.

.,01 "# $!%& '()*

Confidential


 
    

 
-$$)


Note: Changing the Configuration of a CDA item

is only possible when in Edit Mode. You can
switch from Update mode to Edit mode (and
vice versa) by pressing the “Turn Update
Off” button at the top of the Main Window.

Value
This column displays the current value for the CDA item.
This may be a raw sensor reading or the result of a
computation by one of the MSS applications, or it may be
an operator-entered value. Internally, all data values in the
CDA are in S.I. metric. You can choose to view the values
in other units (using the Units Conversion configuration
item from the Options menu).
Units
The conversion units label for the value column.
Last Change
The time that the value column last changed. This gives an
indication if new values are being received into the CDA
for the item.
CID
The conversion identifier for the CDA item.
Alternate
Indicates whether an alternate CDA item has been
assigned to the item. This might be necessary if a sensor
fails and you want to use the value from another sensor in
its place (rather than using a fixed, manually-entered
value). The item is first turned OFF and the alternate CDA
mnemonic is then entered into the Alternate column. To
remove the alternate assignment, simply remove the
mnemonic from the column.

  ! .,0



 
     Confidential

 
-$$)



The program operates in one of two modes: UPDATE
mode or EDIT mode. The current mode is indicated in the
status bar (lower right of the main window).

& 
This mode allows you to view the current values in the
CDA. If the program is currently in Edit mode, you can
place it in Update mode by pressing the “Turn Update On”
button (the label changes to “Turn Update Off”).
In Update Mode, CDA items are refreshed at the rate you
specify in the Interval box at the top of the window. For
example, if you specify 5 in the interval box, the values are
updated every 5 seconds. Five seconds is the default update
rate and should be a good value under most circumstances.
Entering a smaller number (faster updates) may affect the
responsiveness of the computer.


This mode allows you to modify the configuration of the
CDA. If the program is currently in Update mode, you can
place it in Edit mode by pressing the “Turn Update Off”
button (the label changes to “Turn Update On”). The CDA
item values do not change automatically when in the Edit
mode.
The changes that you can make while in the Edit mode are:
• Turn an item off or on
• Enter a fixed value for an item
• Assign an alternate item
• Change the units conversion type for an item
• Change an item mnemonic
• Change the Group membership of and item

.,0 "# $!%& '()*

Confidential


 
    

 
-$$)


Turning an item OFF/ON

The ON check box next to the mnemonic indicates whether
an item is on or not. A check mark appears if it is currently
ON. If ON, you can turn an item OFF by clicking on the
box to remove the check mark. If OFF, click on the box -
the check mark appears to indicate that the item is ON.

Note: It is only possible to manually enter a value

for an item when its status is OFF.

Entering a fixed value for an item

If the item is ON, first turn it OFF by clicking in the “ON”
checkbox. Then, click in the Value column and enter the
new value.
Assign an alternate item
Instead of a fixed value for an item, it is sometimes useful
to have another item’s value used instead. This is
accomplished by assigning an Alternate item. Click in the
Alternate column and type in the name of the Alternate
item. Programs that get a data value from a CDA item with
an Alternate assigned actually get the value of the
Alternate.
Change the units conversion type for an item
Click on the CID column and type in the two-letter
conversion identifier for the CDA item in question. Click
outside the column (or tab from it) and the new conversion
is immediately employed.
Change an item mnemonic
Click in the Mnemonic column of the item to change, then
type in the new name.
Change the Group membership of an item
CDA items can be assigned to various Groups. This can be
useful in restricting the list that is displayed in the main
window to a subset of the CDA. To view or change the

  ! .,0



 
     Confidential

 
-$$)


current Group membership of an item, right-click on its

Mnemonic. See Figure 3-55.

 ",,  $.  :$

The current groups to which the item belongs to are shown

with a check mark in the box next to the group name.
Modify the settings as required and then press OK to save
the changes.

 * 
The current system units conversions can be viewed/
changed by choosing Units Conversions from the Options
menu. See Figure 3-56.
Choose the units type to be modified from the list. The
available conversions are shown in the box labeled
“Units”. Choose the conversion you want to use for that
type. Repeat this procedure for other types if required.
Press OK to save the changes.

.,1
"# $!%& '()*
Confidential


 
    

 
-$$)


 ",1 ) 





Note: Changes to the system conversion table are

broadcast to other applications which will
change their displays accordingly if they are
set up to handle the message.

   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

  ! .,1



 
     Confidential

 
-$$)


4+ +1+ & 4+(


MWDecode is the MWD mud pulse telemetry (MPT)
processing application for all SWWP based systems. It is
used to both detect and decode MWD pulsed data. Pump
pressure data is first read from the data acquisition board
and then filtered to extract the transmitted MWD pulses.
The resulting pulses are decoded based on the transmission
scheme and data rate to produce a bit stream. The bit
stream is then parsed based on the currently selected UFT
telemetry format to produce the dataword values. These
values are displayed in a scrolling list in the MWDecode
parse window and distributed to other processes via the
Message Server application.

Note: MWDecode does not support ILS DAS

encoding schemes.


When MWDecode is first started, you will see the
Setup window shown in Figure 3-57.

 ",2 !3). $

.,1- "# $!%& '()*

Confidential


 
    

 
-$$)


The Tool Family pick list is generated from the list of UFT
Telemetry files which is contained in the MASTER.UFT
file that MWDecode is configured to use. Initially,
MWDecode will look in the INTEQ ctl\mwd\uft directory
for the MASTER.UFT file. If you want to configure
MWDecode to use another MASTER.UFT file, then
clicking on the “Find MASTER.UFT file” button will
display the following window in which the normal
Explorer type controls can be used to locate the new
MASTER.UFT file. See Figure 3-58.

 ",4 $

Note: If the current MASTER.UFT is modified or a

different MASTER.UFT file needs to be
selected after MWDecode is already
running, MWDecode must be shut down and
restarted in order for the changes to be
recognized or the new MASTER.UFT file to
be selected.

For MWDecode, the total number of words the parser can

process has been increased to 64. However, it appears that
the FID may count as 1 word, resulting in a maximum of

  ! .,1.



 
     Confidential

 
-$$)


63 words following the FID. In conjunction with this, you

should also be aware that the SWWP and SWWP/DAS are
limited to 20,480 bytes of storage for the UFT format
tables, which includes both the telemetry and recorder
format files. Only those FIDs, along with the current
recorder format, are downloaded to the SWWP and
SWWP/DAS during the SUITing process. Therefore,
anyone designing UFT files along with SUIT configuration
files, needs to ensure that the size of the selected FIDs
along with the selected recorder format (both are specified
in SUIT) do not exceed the 20,480 byte limit of the
downhole systems. If the UFT format table limit is
exceeded, SUIT will report an error when the SWWP is
programmed and the programming process will be aborted.
The user-configurable field “Standpipe Sensor Full” is
used to properly convert the amperage or voltage signal fed
into MWDecode into the corresponding pressure. Usually
this field will either be 5,000 or 10,000 psi (344.74 or
689.48 bar) dependent upon the type of transducer being
used.
The user-configurable field “Pump-On Threshold” is most
importantly used to signal the start of the “Sync Delay”
when using Combinatorial encoding. This field is also used
to determine the pressure level at which the Pumps On/Off
indicator (located in the lower right corner of the main
MWDecode window) toggles states. For NRZ decoding,
this field is only used to toggle the Pumps On/Off indicator.
A typical value for this field will be 200 psi (13.79 bar).
The “Pumps-On Threshold” value in MWDecode can be a
different value than the “Pump Press Cutoff” value set in
RtProc. The circulating time and the pumps on/off
indicator in the RtProc window are calculated from the
“Pump Press Cutoff” value in RtProc. Therefore, in order
to “keep things in order”, it is recommended that you
always set the RtProc “Pump Press Cutoff” field to the
same value used for the MWDecode “Pumps-On
Threshold” field. In this manner, if both the MWDecode
and RtProc windows are being viewed, the pumps on/off

.,1/ "# $!%& '()*

Confidential


 
    

 
-$$)

indicators will reflect identical states at all times.
Since MWDecode is capable of decoding two base level
encoding schemes: NRZ (Miller, Split-Phase, and
Bi-Phase) and RZ (Combinatorial), you are presented with
the following “MWDecode: Transmission Type” window
in which the base level encoding scheme is chosen.
See Figure 3-59.

 ",5 !3).




$

NRZ stands for Non-Return to Zero. NRZ encoding

schemes use pulser movement definitions that allow for
the pulser to be extended and retracted for variable
amounts of time. This means that pulse widths of NRZ
codes will not be constant for a given data rate. Examples
of NRZ encoding schemes are: Miller, Split-Phase, and Bi-
Phase.
RZ stands for Return to Zero. RZ encoding schemes use
pulser movement definitions that allow for the pulser to
only be extended for a predetermined amount of time. This
means that the pulse widths of RZ codes will be constant
for a given data rate. An example of an RZ encoding
scheme is: Combinatorial.

  ! .,10



 
     Confidential

 
-$$)


2<3 #54(# *

Selecting the Non-Combinatorial option results in the
following shown in Figure 3-60.

 "16 ;
 
  


In this window, you must make selections for

Transmission format, Bandpass type, Transmission Rate,
Notch Filter, Equalizer Filter, Filter Threshold, and if using
Split-Phase, the Signal Polarity. All these selections are
identical to existing systems, except for the Polyphase
Bandpass filter.
The polyphase filter efficiently implements a low
distortion “brickwall” bandpass filter. If problems with
decoding are encountered while using the Generic
Bandpass filter, then the polyphase filter should be chosen.
It is best used when a noise source (such as the pumps) is
close to the passband of the pulse signal, or if noise is
suspected (such as drilling noise) of attenuating one of the
pulse frequencies. Essentially, the passband is made
slightly wider by the polyphase bandpass -- allowing more
3rd harmonic signal -- while the noise rejection properties
are slightly better, and the signal distortion is lower.
.,11 "# $!%& '()*
Confidential


 
    

 
-$$)


Another point to mention is that MWDecode is not as

limited in filter selections as previous decoding systems.
Any Notch filter can be applied together with any
Equalizer filter. However, you should be aware that the
MPT signal processing may be adversely affected by some
filter combinations.
Refer to the “MWD Decoding Handbook” for
explanations and help on selecting specific filters.

Note: The threshold setting can also be set using

the MWDGraph application and double
clicking in the Filtered Data graph.

After completing the Settings window, you will see

the Settings Summary window shown in Figure 3-61.

 "1 
 

After selecting OK, you will see RZ (Combinatorial)

Start-up windows as shown in Figure 3-62.

  ! .,1



 
     Confidential

 
-$$)


 "1




$

After selecting “Combinatorial” for the transmission

type, you will see following window shown in
Figure 3-63.

 "1" 

  


In this window, you must select the Pulse Width from the
pick list.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


Note: At this time, do not use 0.75 second pulse

width with collar or probe based systems.
Also, it is recommended that a 0.5 second
pulse width only be attempted with collar
based systems.

There are three other user-configurable fields: “Sync

Window”, “Sync Delay”, and “Minimum Pulse Height”.
The Sync Window value is used to specify the time period
that MWDecode will attempt to identify the Sync Pulses
transmitted from the downhole tool. The recommended
settings for the Sync Window vary depending on the
current pulse width. Recommend settings are:
0.50 second - 6 second window
0.75 second - 10 second window
1.0 second - 12 second window
1.5 seconds - 18 second window
2.0 seconds - 24 second window
3.0 seconds - 36 second window
These values are recommendations only and the actual
values that should be used are best determined under actual
rigsite conditions.
The Sync Delay value is used to help specify the time
period that MWDecode will wait after detecting “Pumps
On” before it starts trying to identify Sync Pulses. Used in
conjunction with the Sync Window, MWDecode will
delay for the time period of [Sync Delay - ½ * Sync
Window] before attempting to identify the Sync Pulses.
MWDecode will stop attempting to identify the sync
pulses after a time of [Sync Delay + ½ * Sync Window].
The Sync Delay value will depend upon the current
downhole system and the values that are programmed into
that system. Some recommended Sync Delay times are
shown below (Initial Valve Off Time value is included in
the SUIT report for the tool):
• Collar and Navi185 based systems:

  ! .,1



 
     Confidential

 
-$$)


Sync Delay = Initial Valve Off Time + 15 seconds

• SWWP/DAS410/500 with Flow Switch:
Sync Delay = Initial Valve Off Time + 30 seconds
• SWWP/DAS500 with Vibration detection:
Sync Delay = Initial Valve Off Time + 15 seconds
These values are recommendations only and the actual
values that should be used are best determined by you
under actual rigsite conditions.
The Minimum Pulse Height value is used during the
sync’ing process. The system ignores all pulses below this
value and will only evaluate pulses that are larger than this
to determine if they fit the sync pulse pattern. It is to your
advantage to set this value as low as possible, but still
slightly above the average noise level. At this time the
value must be input as PSI regardless of the currently
selected pressure units.

Note: Even though the Sync Delay, Sync Window,

and Minimum Pulse Height parameters can
be setup, it is recommended to only use the
“Force Resync” option outlined later.

The last selectable field in this window is “Decode

Method”. The two choices are Correlate and Peak Detect.
Correlate stands for correlation detection. This method of
decoding is much like pattern matching. It uses both pulse
width and the gap before and after the pulse to determine if
a pulse is actually a pulse. The pulse widths and timing
gaps are distinctive for each data rate.
Peak Detection simply looks for the existence of a peak
(maximum point) within a slot. For example, if a word
consists of 3 pulses in 17 slots, the 3 largest peaks will be
found in the 17 slots. These 3 peaks will then try to be
matched to valid patterns.
For both methods, once the required number of pulses are

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


found for a given word, the pulse pattern will try to be

matched with valid patterns. If a valid pattern is found, the
word is deemed to be “Good”. If the pulse pattern cannot
be matched to any valid pattern, the end of the bit stream is
tagged with “UU” and the word is given a status of “Bad”.

Note: At this time, only Correlate should be

selected. Test results with the Peak
Detection method have not compared as
well to the Correlation method. However, if
all else fails, Peak Detection can be
attempted.

After completing the Settings window, you will see the

window in Figure 3-64.

 "1% 
 

Main MWDecode Window

Once in the main MWDecode window, you can view
the parsed MPT data as well as other messages
(Pumps On & Pumps Off). The NRZ MWDecode
main window is shown in Figure 3-65.

  ! .,



 
     Confidential

 
-$$)


 "1, !3)

The MWDecode main window contains the following

items: Menu, Toolbar icons, Resync on Preamble/Force
Resync button, Pump Pressure display, Raw and Filtered
recording check boxes, parse window, pumps on/off
indicator, and rotating/non-rotating FID indicator.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


Menu Items
See Figure 3-66.

 "11 

Selecting    will end the MWDecode application.

Selecting
  8 will display a combination
Non-Combinatorial and Combinatorial Filter Setting
window. See Figure 3-67.

 "12 


Only the current base level encoding filter selections will

be available.

Note: To switch between NRZ decoding and

combinatorial decoding, MWDecode must
be shutdown and restarted.

Note: The threshold setting can also be set using

the MWDGraph application and by double-
clicking in the Filtered Data graph.

  ! .,.



 
     Confidential

 
-$$)


An example of the NRZ filters window is shown in

Figure 3-68.

 "14 ) 

When you select
 

%
 will display
the MSS standard unit conversion window.
Selecting
   will display the Data
Output window. This is used to configure the chart
recorder/DAT recorder output. See Figure 3-69.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "15  $

Selecting 9 
$ will bring up the

“MWDecode: Statistics” window. The decoding statistics
will only be reset when you choose to reset them.
Restarting MWDecode or the MSS computer will not reset
the statistics. An example of this window is shown in
Figure 3-70.

  ! .,0



 
     Confidential

 
-$$)


 "26 )

When you select 9  8$ this will start the

MWDGraph application.
Selecting 9  8 will toggle the spreadsheet grid On
and Off in the MWDecode parse window.
MWDecode Toolbar Icons
See Figure 3-71.

 "2
 )



Listed from left-to-right, icons are available in the main

MWDecode window for the following menu items:
• Settings - Filters
• View - Statistics
• View - Graphics
• Settings - Conversions
• View - Grid

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


Resync on Preamble/Force Resync Button

This button is labeled differently depending on whether
MWDecode is configured for NRZ or Combinatorial
decoding. If NRZ decoding is selected, the button will be
labeled “Resync on Preamble”. Pressing this button will
cause the parser to stop decoding the current signal and to
search for a valid Preamble pattern to resync. If the parser
finds a preamble pattern, it will then look for a Marker bit
and attempt to decode as normal. Note that a preamble
pattern may be detected in the midst of data pulses causing
incorrect syncing. That is, a valve off is not required in
order for the parser to start decoding again. See
Figure 3-72.

 "2 
) 9


If Combinatorial decoding is selected, the button will be

labeled “Force Resync”. Pressing this button will cause the
parser to stop decoding and to search for valid sync pulses
within the last [½ * Sync Window length] seconds of
filtered data. This would normally be used when the
downhole conditions (e.g., mud motor stall) cause the
MWD tool to reset. In this instance, the pump pressure
would not have fallen below the pump off limit, so the
surface system would keep trying to decode while the
downhole tool is going through the start-up routine. When
you identify the sync pulses on the filtered data graph,
press this button to attempt to re-sync the downhole and
surface systems.
Pump Pressure Display
This shows the current pump pressure measurement.

  ! .,



 
     Confidential

 
-$$)


Raw and Filtered Recording

Checking either of these boxes causes the selected signal to
be recorded to disk. Checking the Raw signal box will
create a file with the naming convention of:
\mmmddyyyyhhmmss.raw (in the INTEQ directory)
Checking the Filtered signal box will create a file with the
naming convention of:
\mmmddyyyyhhmmss.fil (in the INTEQ directory)
If decoding problems occur, you can select to record the
incoming signal for later playback and analysis. At present,
no playback function is available. If recordings are made,
you should provide very good documentation (minimum
required: tool type, data rate, encode type, UFT files used
(.TEL and 77249UD), and FID survey sequences), such
that when playback functions are developed, the data can
be properly interpreted.
Parse Window
The parse window is where the parse datawords appear.
The time stamp, bit pattern, value, units, and quality flag
are shown for the datawords.
The information displayed in the parse window is passed to
the Message Server so that other applications (like RtProc,
SvyPrc, and RDD) have access to this data. However, any
datum that is tagged as “Bad” quality will not be passed to
the Message Server. Normally, the data line appearing in
the Parse window will be black in color, however, if the
quality of the word is deemed “Bad”, the line will be
colored red.

Note: No calculations are performed in the parse

window. This means that toolfaces will not
have the scribeline factor added, azimuths
will not have grid corrections applied,
inclinations will not have Sag corrections
applied, GZMX will not be calculated into

., "# $!%& '()*

Confidential


 
    

 
-$$)


an inclination, etc. The corrected values for

the above parameters, will only appear in
the RtProc, SvyPrc, and RDD applications.
It is very important that you not report the
values seen in the parse window to other rig
personnel since important correction
factors may be missing.

Pumps On/Off Indicator and Rotating/Non-rotating FID

Indicator
The pumps on/off indicator is located in the lower right
hand corner of the MWDecode application window. A
status of On is characterized by a green background with a
black foreground. A status of Off is characterized by a red
background with a white foreground. The MWDecode
“Pump-On Threshold” value is used to determine the state
of this indicator.
The rotating/non-rotating FID indicator is located just to
the right of the pumps on/off indicator. When a rotating
FID is decoded, the indicator colors are a green
background with a black foreground. When a non-rotating
FID is decoded, the indicator colors are a red background
with a white foreground.
MWDData.log
This is not directly accessible from MWDecode, but you
should be aware that all data shown in the parsed data
window are stored into the following ASCII text file:
\MwdData.log (in the INTEQ ctl\mwd directory)
The size of MwdData.log is limited to 524,288 bytes.
When it reaches this size, one quarter of the oldest data is
deleted to make room for new data. This file can be viewed
with any text editor application.

  ! .,



 
     Confidential

 
-$$)


4+ % & 4+%(


MWDGraph is the application used for displaying the raw
and filtered MPT time domain traces. It will also display
frequency domain traces of the MPT signal. MWDGraph is
used in conjunction with MWDecode, and MWDGraph
receives data directly from MWDecode, such that if
MWDecode is not running, MWDGraph will not update.


There are no start-up windows associated with
MWDGraph. It is started directly from MWDecode by
selecting the icon or by using the menu choice.
The MWDGraph window can display up to four MPT
graphs in any combination. The choices are: Raw Data,
Filtered Data, Raw FFT Data, and Filtered FFT Data.

Note: FFT stands for Fast Fourier Transform.

This process converts the time domain MPT
signal to a frequency domain signal.

Note: When using NRZ encoding, vertical lines

will appear on the FFT graphs indicating
the frequencies of the MPT signal. Also, a
shaded background will define the range of
the current Generic Bandpass filter.

An example NRZ MWDGraph window is shown

Figure 3-73.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


 "2" !3:$( 3



Using the Raw FFT Data graph: A quick lesson.

By using the Frequencies.txt file, it is seen that the
frequencies for 2xSP (what is currently selected) are 0.2
and 0.4 Hz. These frequencies agree with the vertical lines
shown in the FFT graph. By examining the FFT graph, it is
seen that the low frequency is close to the expected 0.2 Hz
and appears at approximately 0.19 Hz. Looking further, a
peak at about 0.31 Hz is also seen. Since this is not a
frequency of 2xSP, it can be assumed that this peak is due
to noise. You should select the Tuneable Notch filter and
set the frequency to 0.31 Hz. This will knock out the noise
peak which is occurring within the current passband of the
MPT signal.

  ! .,



 
     Confidential

 
-$$)


Note: Refer to the “MWD Decoding Handbook”

for further information.

The MWDGraph window contains the following: Menu,

Toolbar icons, Graphs, and a Running/Paused indicator.
Menu Items
For the File Menu, see Figure 3-74.

 "2%  !



Select    to send a current snapshot of the

MWDGraph window to the printer.
Select   
 for a standard window setup
routine for configuring the printer.
Select    to end the MWDGraph application.
For the View Menu, see Figure 3-75.

 "2, ' !



Select 9  !0$: to view a file that lists the

frequencies of the MPT signal and the associated ranges
for the passband filters. For a partial example, see
Figure 3-76.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "21 =

) +


For the Settings menu, see Figure 3-77.

 "22 
 !


 
$ will bring up the “MWDGraph: Set

Scales” window. In this window, you can select whether to
autoscale the Y axis or reverse the time scale. The X axis
scale limits are also entered in this window, along with the
Y axis scale limits (only used when Auto Y Scale is set to
“No”). You should be aware that when autoscale is turned
on, if a large pressure pulse is measured, or starting from a
pumps off situation, the MPT pulses may appear to be
reduced in size and in some cases may be difficult to
identify until the large pressure differences have “scrolled”
off the graph. Reversing the time scale may be useful when

  ! .,.



 
     Confidential

 
-$$)


using combinatorial to help identify the sync delay. An

example Scales window is shown in Figure 3-78.

 "24  )

When you select
 
$ 

 will display
the “MWDGraph: Select Plots” window. In this window
you can configure which plots will be displayed in the main
window. An example of this window is shown in
Figure 3-79.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "25 ) 0

Select
   and this is a toggle option that
will alternately pause and restart the MWDGraph display.
While paused, you can more easily analyze the
MWDGraph display. When paused, the Running/Paused
indicator in the lower left corner will turn red with a white
outline. When running, the Running/Paused indicator will
turn green with a black outline.
MWDGraph Toolbar Icons
See Figure 3-80.

 "46
 )



Listed from left-to-right, Toolbar icons are available in the

MWDGraph window for the following menu items:
• File - Print
• View - Pause
• View - Frequencies.txt

  ! .,0



 
     Confidential

 
-$$)


• Settings - Scales
• Settings - Conversions
When MWDGraph is first started, you should first select,
Settings - Select Plots and choose which plots to view. As
a default, MWDGraph will start up with the Raw Data and
Filtered Data graphs displayed. After choosing which plots
to display, select Settings - Scales and configure as desired.
Operational Notes for using MWDGraph: NRZ
Encoding
Some features of MWDGraph to use in the field in case of
decoding problems are:
• Double-clicking in the Filtered Data graph will
adjust the threshold to the current position of the
mouse pointer.
• Use the Raw Data trace to identify Valve Off’s. If
sufficient noise exists in the signal, such that
identifying the Valve Off is difficult, it has proven
to be much easier to identify the Valve Off in the
Raw Data trace than in the Filtered Data trace.
• Use the Raw Data trace to determine pulse heights.
Since the Raw Data trace does not revolve around a
zero axis (as does the Filtered Data), the size of the
pulse can be measured directly off the Raw Data
trace. Use the mouse pointer and read off the X, Y
coordinates listed in the upper left corner of each
graph.
• Use the FFT traces to help identify noise in the
system. Because the Filtered FFT Data takes
approximately 10 minutes to calculate frequencies,
it will probably prove more effective for you to use
the Raw FFT Data trace to identify noise. The
optimum time to identify noise in the system is after
the Valve Off and during the Preamble just prior to
the Marker Bit. At this time, the only frequency that
should be visible in the system is the low frequency

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


of the MPT signal. This will be indicated by the

left-most vertical bar in the Raw and Filtered FFT
Data traces. If other noise is in the system, you
should determine if it is outside the range of the
Bandpass filter (outside the shaded background). If
it is outside this range, then no action is probably
needed as the Bandpass filter will filter out the
noise. If the noise is determined to be within the
Bandpass filter, you should determine the exact
frequency of the noise and apply the Tuneable
Notch Filter at this frequency.

Note: During testing it was discovered that a

frequency viewed on the Raw Data traces
was shifted slightly lower in frequency when
viewed on the Filtered Data traces. For this
reason, the Tuneable Notch filter may need
to be set slightly lower than the frequency
seen on the Raw FFT trace. For example, a
1 Hz signal on the Raw Data appears as
0.985 Hz on the Filtered Data. A 0.75 Hz
signal on the Raw Data appears as 0.74 Hz
on the Filtered Data. A 0.46 Hz signal on
the Raw Data appears as 0.455 Hz on the
Filtered Data. You may have to slightly vary
the frequency of the Tuneable Notch filter
until an optimum setting is found.

Operational Notes for using MWDGraph:

Combinatorial Encoding
Due to the fact that the filtering selection for combinatorial
encoding is not adjustable, the main use of MWDGraph is
to aid in visually identifying the Sync Pulses. Once the
sync pulses are identified (wait until they appear on the
Filtered Data graph), click on the “Force Resync” button
located in the MWDecode application.

Note: Do not click too early. Both sync pulses

must be clearly visible in the Filtered

  ! .,



 
     Confidential

 
-$$)


Data graph. If the button is clicked too

early, simply click it again at the proper
time. Clicking this button will cause the
parser to stop decoding and to search for
valid sync pulses within the last [½ * Sync
Window length] seconds of filtered data. See
Figure 3-81 that reflects the proper time to
click the “Force Resync” button.

 "4 ) 

)

Using the ROD (Rigsite Optical Decoder) with

Combinatorial
As opposed to NRZ decoding with the ROD (which
requires no special steps), you should be aware of a few
items in order to decode combinatorial data with the ROD.
When using the ROD, the Sync Window, Sync Delay, and
Minimum Pulse Height values cannot be used to detect the
sync pulses. The reason for this, is that the ROD cannot
produce the step change needed to recognize a Pumps On
transition. The ROD only outputs two levels, high and low.
Therefore, the first step is to lower the “Pump-On

., "# $!%& '()*

Confidential


 
    

 
-$$)


Threshold” parameter in MWDecode. The value should be

set to around 10 psi (0.69 bar), such that MWDecode
reflects a Pumps On state when the ROD is connected.
After connecting the ROD and attaching it to the POD,
simulate or start the flow process in order to make the tool
pulse. Once the sync pulses are seen in the Filtered Data
graph, click on the Force Resync button and decoding will
commence. Do not be concerned that MWDecode is
attempting to decode prior to the tool actually pulsing. This
is part of the process in order to decode combinatorial with
the ROD.
Another alternative method for decoding using the ROD:
1. Go to Settings - General, make sure “Pump On
Threshold” is about 200-500 psi such that the current
status of the pump is off.
2. Set sync delay and sync window correctly according
to how the tool is SUITed.
3. Go to Settings - General and set “Pump On
Threshold” to 5-10 psi and standby.
4. Use MWDComm, power the tool up and press the
OK button in the Settings - General window when
you see a big pulse on Filtered Data in MWDGraph;
if the tool is being powered by a battery, press the
OK button in Settings - General window when the
tap test is started. This will force MWDecode to
recognize pump on and start the process of searching
for sync pulses.
Miscellaneous Tips for MWDGraph
1. For all graphs, moving the mouse pointer over the
graph area will display the X, Y coordinates in the
upper left corner of the current graph.
2. Except in the Filtered Data graph when using NRZ
encoding, left clicking and dragging will produce a
“zoom in” box, such that the area outlined will be
zoomed in on.

  ! .,



 
     Confidential

 
-$$)


3. On all graphs, right clicking will produce a pop up

shown in Figure 3-82.

 "4 0$ #$ 9>

Do not use the “Mark Data Points” or

“Customization Dialog” option. All others should be
harmless to use, and some may actually prove to be
useful, such as Grid Lines. Also, if a graph has been
zoomed in, the Undo Zoom option will become
active. Use this option to return to the normal
viewing level.
4. It may be helpful to use the Pause button in
conjunction with some of these options.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


/  & (


The AutoTrak Control program (ATCtl) is used to send
commands to the AutoTrak BHA, as well as evaluating
command confirmations and tracking Bypass Actuator
(BPA) usage. All of this information is stored to the
database and can be retrieved with ATCtl and AtDisp.
Communicating with the AutoTrak tool is achieved by
flow rate modulation (referred to as downlinking). This
modulation is achieved by diverting a portion of the mud
flow, 10% - 20%, from the standpipe back to the most
convenient place in the return system using a BPA. This
BPA is controlled by ATCtl via a Bypass Controller
(BPC).
The ATCtl program must run on the computer connected
with the Bypass Controller (BPC) via a serial port, but can
also be run (as a second copy) on a remote computer.
These two computers must then be connected via MsgSvr.
The computer connected to the BPC must also be
connected to the database.


When started, the following main window is displayed, as
shown in Figure 3-83.

  ! .,



 
     Confidential

 
-$$)


 "4" -
* 



On the left side of window is the Downlink Control panel

where you can send new downlinks. On the right side of the
window you can view previous downlink and confirmation
data; also the current Downlink Controller (DLC) status.
Use the tabs to switch between the data.
Selecting Pulse Pop up from the View menu displays a
window showing the pulse sequence of the currently
selected downlink. The BPA open and close times allow
(in case of a BPC or BPA failure) to manually switch the
pump rate to send a downlink. See Figure 3-84.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "4% 


* 0

 *

On the left side of main window, select the downlink
command, the parameters to go with that command, and
the pulse time.
Press the Transmit button to send the downlink.
Confirm the downlink. If the downlink is sent correctly to
the BPC, the status line shows the expected transmission
time remaining. Otherwise, an error message will appear
on both the Downlink Control and the Downlinks tab field.
Pressing the “Abort” Button interrupts the downlink.

  ! .,.



 
     Confidential

 
-$$)


5

If the Transmit downlink display is empty and the button is
labeled Check BPC, an error message is displayed in the
status line. This is usually because the BPC is not correctly
connected. Using this error message you can locate the
problem and then (after correcting it) check if everything is
OK by pressing Check BPC.

(# ' 

ATCtl can be started with the following options:



do not connect to a BPC (if you want to run ATCtl on

multiple computers at the same time)
Only one version of ATCtl can be connected to a BPC, all
others will automatically switch to remote mode and state
“Remote BPC” on the lower right side.
-simulate
simulates a BPC and can be used to test the system when
no BPC is available.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


/ +  &+(


ATDisp is used to view old downlinks and to visualize the
drilling process.


The default screen at start-up is the Rose-view. Using the
tabs you can switch between the different views, such as
the downlink and confirmation search and the downlink
and dataword lists.
The Rose-view displays the three ribs (with rib 1 in
magenta) and the Dogleg Severity (DLS) between the last
two posted surveys in blue (with both DLS and direction to
show which direction the tools is drilling).
If the tool is in steering mode, the Rose-view additionally
shows the resulting force in red and the rib-forces in green.
See Figure 3-85.

  ! .,0



 
     Confidential

 
-$$)


 "4, -
* $

The Downlink List keeps a log of the downlinks send

since ATDisp was started.
The Downlink Search and the Confirmation Search
allow you to search the database for old downlinks and
downlink confirmations. The downlinks can be searched
by measured depth, time or by scrolling with the up/down
buttons for either time or depth. Checking the “Show
Current Data” box shows the last downlink /confirmation.
See Figure 3-86.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


 "41 


* )(

The Datawords tab shows a list of the last (maximum

2000) datawords received from the BHA and can be stored
to file using the  
% 
 ; #.
The PP displays the time based standpipe pressure chart of
the last downlink (+10 seconds before and 20 seconds
afterwards) for evaluation and printing (by right-clicking it
with the mouse and selecting export menu). The bits are
separated by a dotted line. Also, BPA activations are
shown in gray. The chart is automatically scaled but
zooming is possible using the mouse. See Figure 3-87.

  ! .,



 
     Confidential

 
-$$)


 "42 00 0

ATDisp can be started with the following option:



Do not connect to the database but connect to ATCtl via

MsgSvr and receive all database information from ATCtl.
By default ATDisp tries to connect to the database itself.

., "# $!%& '()*

Confidential


 
    

 
-$$)


  &
(


Survey Processing in MSS involves a number of
applications working together. Central to the whole
process is the Message Server as can be seen in
Figure 3-88.

 "44 ! 

MSS
Entry of database setup information such as well and hole,
as well as survey reference information such as
Declination and Grid Offset. BGGM and Sag calculations
can be run from within this application. This information
is stored into the database for retrieval by other
applications that need it (such as SvyProc and SvyEdit).
MWDecode
This is the real-time mud pulse detector/decoder which

  ! .,



 
     Confidential

 
-$$)


translates mud pulse telemetry data into chunks of

information called DATAWORDS containing, among
other things, the mnemonic and value of a piece of
telemetered data. The datawords are made available to the
system by forwarding them as messages to the Message
Server.
SvyPrc
This is the survey processing application. It registers with
the Message Server to receive dataword messages (from
MWDecode) and SUCOP results messages (from
INTEQ_RTS). SvyPrc takes the base datawords and
processes them into corrected data words which are then
sent back to the Message Server. SvyPrc records base, raw
and corrected survey information to the database
(SURVEY_RAW table). You can choose to POST surveys
from within SvyProc and these are written to the SURVEY
table in the database.
SUCOP & INTEQ_RTS
If SUCOP is present, a special SUCOP data message,
containing base survey values, is sent out from SvyPrc and
picked up by the INTEQ_RTS program running on the
SUCOP computer. INTEQ_RTS, in turn, copies the data
into the SUCOP program and gets a set of results which it
sends back to the Message Server.
RDD
The RDD program takes dataword messages (and SUCOP
results messages if applicable) from the Message Server
and formats and transmits a string of characters to the
Remote Driller's Dial, updating it with the latest directional
information.
SvyEdit
The Survey Editor can be used to information in the
SURVEY table of the database.
The SvyPrc application is used for the real time processing

.,

"# $!%& '()*

Confidential


 
    

 
-$$)


of directional data pulsed by the MWD tool. It should

therefore be running whenever the tool is in the hole and
sending data to the surface.
SvyPrc takes the raw datawords transmitted by the tool and
builds complete surveys. When a complete survey has
been taken, it is made available for posting.

 
There are three modes of operation: MagCorr, ASurvey,
and SUCOP.

 
In this mode, calculations are run after a complete set of G
and H values have been read. Values taken directly from
the tool are called “raw” values. SvyPrc compensates for
scribeline, magnetic declination, and grid offsets. These
values are the “base” values. SvyPrc then takes the ‘base’
values and runs them through a magnetic correction
algorithm (Baker Hughes INTEQ’s MagCorr #1
algorithm), resulting in the final, “corrected” values.

("
In ASurvey mode, calculations are run after three “raw”
values are received: inclination, azimuth, and either the
magnetic or highside toolface. These values are corrected
for scribeline, magnetic declination, and grid offsets.
These “base” values are stored as is – there are no magnetic
corrections done for ASurveys. See Figure 3-89.

  ! .,




 
     Confidential

 
-$$)


 "45 ! ?-  0)



(&'
SUCOP is a special case. This mode requires that the
SUCOP program (version 2.5 or above) be running on a
computer networked to the computer where SvyPrc is
running. Likewise, the INTEQ_RTS SUCOP interface
driver must be running on the same computer as SUCOP.
When a complete set of G and H values are received by
SvyPrc, they are passed on to SUCOP through the Message
Server and INTEQ_RTS driver. SUCOP processes these
“raw” values and returns the “corrected” values. See
Figure 3-90.

 "56 # 0 0)



.,
- "# $!%& '()*
Confidential


 
    

 
-$$)


*


=*
When SvyPrc starts-up, the Current view is displayed.
This view can also be reached by pressing the C toolbar
button, or selecting the 9   9 menu item.
This display shows the survey that is currently being
transferred in the top section of the window. The bottom
section is a list of all completed but unposted surveys in the
system. This list is sorted with the latest survey on top.
See Figure 3-91.

 "5 

 '

From left to right and top to bottom, the items on the top
section of the Current View are:
ACOR Total correction for grid and declination
FCOR Total correction for scribeline and internal
tool offset
Sag Corr. Sag correction applied

  ! .,
.



 
     Confidential

 
-$$)


Nominal GT Nominal gravitational field strength

Nominal HT Nominal magnetic field strength
Nominal Dip Nominal dip angle
GXBX Transmitted X-axis accelerometer
reading
GYBX Transmitted Y-axis accelerometer
reading
GZBX Transmitted Z-axis accelerometer
reading
HXBX Transmitted X-axis magnetometer
reading
HYBX Transmitted Y-axis magnetometer
reading
HZBX Transmitted Z-axis magnetometer
reading
DHZ Change in Z-axis magnetometer
reading
DHXY Change in HXY
TCDX Transmitted temperature reading
GT Calculated total gravitational field
strength
HT Calculated total magnetic field
strength
DIP Calculated dip angle
AZI Raw and corrected azimuth
INC Raw and corrected inclination
HTF Raw and corrected highside
toolface
MTF Raw and corrected magnetic
toolface
IMCX Near bit inclination

.,
/ "# $!%& '()*
Confidential


 
    

 
-$$)


=*
There are four data views besides the default Current
view. These all display historical survey data.
• ASurvey view (A on the toolbar) displays only
ASurveys surveys.
• DRAW view (D) displays DRAW surveys.
• SUCOP view (S) displays surveys received from
the SUCOP application.
• Posted view (P) displays all surveys of any type that
have been marked as posted.
Note that the list is sorted with the latest surveys on top.
Any posted surveys will be displayed in bold
(except on the Posted view). See Figure 3-92.

 "5  '

  ! .,
0



 
     Confidential

 
-$$)


Abbreviations used in the survey lists are:

Time Time the survey was taken
MD Measured depth
Azim Azimuth
Incl Inclination
Dip Calculated dip angle
HT Calculated total magnetic field strength
GT Calculated total gravitational field strength
Gxy Calculated GXY
Hxy Calculated HXY
Gx Transmitted X-axis accelerometer reading
Gy Transmitted Y-axis accelerometer reading
Gz Transmitted Z-axis accelerometer reading
Hx Transmitted X-axis magnetometer reading
Hy Transmitted Y-axis magnetometer reading
Hz Transmitted Z-axis magnetometer reading
Solution MagCorr solution used (0 or 1)
SagCorr Sag correction applied
MagCorr MagCorr algorithm used (0 or 1)
Posted Survey posted flag

"!
Once a current survey is filled in on the Current view, you
may want to check additional quality values for that
survey. A separate dialog, the “Survey Quality Value
Limits” dialog, shows this information. This is accessible
from the toolbar button Q, or the 9  , ;
menu item. See Figure 3-93.

.,
1 "# $!%& '()*
Confidential


 
    

 
-$$)


 "5"  @ ' +

In order to modify the range in which a value is considered

good, click the Modify Limits button. This enables the
Limits fields and allows you to change these ranges. Once
you are finished, press Save to accept your changes, or
Cancel to abort. See Figure 3-94.

 "5%  @ ' +

Pressing the Set Defaults button will reset the quality

ranges to their initial settings.

  ! .,




 
     Confidential

 
-$$)


The following color coding and marking is used for fields

on the Current display:
Value color coding:
White background Good value
Red background Bad/out of range value
Blue background Recalculated value
Green background Corrected value
Value markers:
“*” Value out of range
“e” Bad value
“r” Recalculated value
“c” Corrected value

.,
 "# $!%& '()*
Confidential


 
    

 
-$$)


'056)

*
 +


INTEQ_RTS is the MSS interface driver for SUCOP. In
SUCOP mode, raw surveys are sent by SvyPrc to SUCOP
through this driver for processing. Corrected surveys are
sent back from SUCOP through INTEQ_RTS to SvyPrc.


There is very little configuring to do for INTEQ_RTS. See
Figure 3-95.

 "5,  



The Server Name field should contain the name or IP

address of the MSS computer running Message Server
(and usually also the SvyPrc program). This is where the
INTEQ_RTS driver will look when connecting to the MSS
network.
If you are using SUCOP 2.5 or later, check the “Use
Extended Results Data” option field. This option allows
the driver to retrieve more detailed survey information
using improvements in the SUCOP RTS 1.1 specification.

 
After you have installed SUCOP, copy the

  ! .,




 
     Confidential

 
-$$)


INTEQRTS.EXE file into your SUCOP directory. Open

the SUCOP.INI file (in your windows directory) and look
for a section labeled “[RealTimeSystem]”. You should see
something like this:
[RealTimeSystem]
; Shell Real Time System Driver (for
the serial port)
driver=siepdrv.exe
Change the “driver=” line to:
[RealTimeSystem]
; Shell Real Time System Driver (for
the MSS
system)
driver=InteqRTS.exe
Restart SUCOP and test the 
   


 menu option. It should open a dialog
similar to the one above.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


 0   &
0(


The SvyEdit program is used for editing and printing
posted surveys and entering tie-on information. Reference
data can also be edited here. Reports and graphical plots
can also be produced from the stored survey information.


At start-up the well and path should be selected by
choosing Open from the File menu. This loads the posted
surveys for that well and path. See Figure 3-96.

 "51  & 3



Editing is achieved by changing either MD (survey depth),

Inc (inclination), or Azi (azimuth). All other parameters
are calculated. Tie-on information is entered by selecting a
row on the spreadsheet and right clicking and selecting the
Insert Tie-on option. When this occurs the TVD, NS, EW,
and Vertical section fields become editable to allow for

  ! .,



 
     Confidential

 
-$$)


entry of tie-on information.

  07

It is possible to import surveys from an outside source.
Choosing the Import option under the File menu presents
the following screen. See Figure 3-97.

 "52 $   3



Surveys can be imported from ASCII files or from

EC*Trak file. Surveys can also be exported to ASCII files
by choosing the Export option under the File menu. See
Figure 3-98.
If the Format for Print option is selected, the output file
includes header information. If the option is not selected, a
space separated listing of the surveys is exported.

* 
There are two utilities available from the survey program.
The first is for performing BGGM calculations which
calculates declination, dip, and magnetic field based on

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "54 &>$   3



latitude and longitude. See Figure 3-99.

 "55 9::! )

 3


The second utility performs Sag calculations based on

stabilizer position. This data can be picked up by the real-

  ! .,.



 
     Confidential

 
-$$)


time processing routine for inclusion with inclination

measurements. See Figure 3-100.

 "66  )

3


Pressing the Apply button produces the window shown in

Figure 3-101. Press OK to save the Sag data.

 
 )

Start SvyEdit to display the main window. See
Figure 3-102.
The printing options are located under the File menu. See
Figure 3-103.
Under Print Setup the following is found. See
Figure 3-104.
This allows you to select various options for the printout.
The Final Copy option results in the words FINAL COPY
being printed in the survey header. If unchecked, a FIELD
COPY ONLY is printed. The Use 2 Decimal places option

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "6  )

 3


 "6  & 3



  ! .,0



 
     Confidential

 
-$$)


 "6"
 !


 "6% 0

 $ 3


results in the azimuth and/or inclination to be printed with

two decimal places. If unchecked they are printed with one
decimal place. The Print Plane Vsect option, if unchecked,
results in the overall vertical section being printed. If
checked, the incremental vertical section will be printed.
To print the surveys select the print option under the file
menu. See Figure 3-105.
Select the appropriate printer and press OK.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


 "6, 0

 3


  ! .,



 
     Confidential

 
-$$)


) + 8 + &)++(


RDD is used to update the Remote Driller's Dial, normally
located on the drill floor, with real-time directional
information. The MWDecode and SvyPrc programs send
DATAWORD messages with this data to the Message
Server which, in turn, routes them to the RDD. Optionally
results data from the SUCOP program may also be
displayed.
The program can also be used to test communications with
the Dial by sending known patterns of data.
When started, the main window is displayed as shown in
Figure 3-106.

 "61 .    #$

The text fields in the upper part of the window display the
latest values for various directional data words. The text
field in the lower half of the window displays the last
message string sent to the Dial. The time of the last
transmission is also shown.
When the program starts it may start transmitting
., "# $!%& '()*
Confidential


 
    

 
-$$)


automatically. This is an option set in the Parameters

window accessible from the Settings menu. If automatic
transmission is not turned on, you must start processing by
selecting Run from the Process menu (or press the
equivalent toolbar button).
To stop transmitting to the Dial, choose Run from the
Process menu (or press the toolbar button).
To test the Dial, choose Test from the Process menu.
To quit the application, choose Exit from the File menu or
click the close box in the top right of the main window.



To configure the various parameters used by the program,
choose Serial Port & Parameters from the Settings menu.
See Figure 3-107.

 "62  

0$

If not already selected, click on the Parameters tab to

display the Parameters settings.

  ! .,



 
     Confidential

 
-$$)


Use SUCOP
Check this box if you want to display results data from the
SUCOP program.
Toolface
Choose whether to display Gravity Toolface, Magnetic
Toolface, or Auto (the program decides based on the data).
Magnetic Corr. Type
Choose the magnetic correction type being used, if any.
Automatically begin processing at start up
Check this box if you want RDD to automatically begin
transmitting data to the Dial at start-up, using the last saved
configuration.
Press Apply to save changes. If you press OK, changes are
saved and the window is also dismissed. Press Cancel to
keep the old settings.

 


To configure the serial port used by the program, choose
Serial Port & Parameters from the Settings menu. The
following window is shown in Figure 3-108.

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


 "64  

0$

Choose the port to be used for communicating with the

Driller's Dial. The port settings are fixed at 1200 baud, 8
data bits, 1 stop bit, and no parity.

 
 

&(
To start processing, choose Run from the Process menu. A
check mark appears next to the menu item letting you
know that the program is now in processing mode. The
equivalent toolbar button is also depressed. As new data
words are made available they are displayed in the main
window and periodically a message string is sent to the
Dial. The time and contents of the transmitted message are
shown in the main window.
To stop processing, choose Run from the Process menu.
The check mark disappears and the toolbar button pops up.
New data words are still displayed in the main window but
none are sent to the Dial.

  ! .,-



 
     Confidential

 
-$$)


  + 9 +

It is possible to test communications with the Driller's Dial
by sending it a known set of data and checking for the
correct response. Testing is only possible when processing
has been stopped. Choose Test from the Process menu to
display this window in Figure 3-109.

 "65 .


Select the type of test to perform from the drop-down list.

Press Run to start transmitting the test data to the Dial.
Press the Stop button to end the test (or press Close to end
the test, and close the window).
The following tests are available:
Eights
Toolface = 90 degrees Right
Toolface type = M
Azimuth = 888.8
Inclination = 888.8

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


Incremental
1. 360 degree Toolface incremental step (each step is
36 degrees).
2. Toggle between M and G toolface types.
3. Azimuth and Inclination scrolling increment (000.0,
111.1, to 999.9).
Toolface 150 Right
Toolface = 150 degrees Right
Toolface type = M
Azimuth = 123.4
Inclination = 032.1
Toolface 175 Right
Toolface = 175 degrees Right
Toolface type = G
Azimuth = 123.4
Inclination = 032.1
Zeroes
Toolface = 0 degrees
Toolface type = M
Azimuth = 000.0
Inclination = 000.0

   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

  ! .,-.



 
     Confidential

 
-$$)


)   &)(


RtProc should be run on all jobs that are not “directional-
only”, specifically to provide depth values and online FE-
MWD processing.
The program is used to:
• perform Formation-Evaluation MWD processing
• perform Depth Tracking
• perform online Hydraulics
• display online MWD and Surface data
• display user-configurable CDA values
• set the MWD Relog Number
• calculate bottom-hole resistivities
• view the system Error, Depth Tracking and MWD
logs
When started, the main window appears as shown in
Figure 3-110.

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "6  0)



The title (caption) bar of the window displays current

Well, Hole, Tool run, and Relog Number information. The
window is made up a several distinct areas:
A. The menu bar. All program functions are accessibly
through the menu bar.
B. The toolbar. The buttons are shortcuts to menu
items. Hold the cursor over a button momentarily to
get a brief description.
C. Common Data Area (CDA) values - fixed items. The
first column of CDA values is fixed and you cannot
change this.
D. Common Data Area (CDA) values - user-
configurable items. Each item consists of a button on
which is displayed the item name and a text field in
which is displayed the item's value. If units are
associated with the item, the unit string follows the
text field. To configure an item, press the button to
display the CDA selection dialog.

  ! .,-0



 
     Confidential

 
-$$)


E. The main data display consisting of a scrolling list of

data records, updated each time a new MWD
dataword is processed or when a surface
(DRILLDEPTH) record is written to the database.
You can click on a row to effectively
“delete” or “undelete” the associated record. A pop
up window asks if you want to zap or unzap the
record.
F. The status bar. This is used to display application
messages and also the location of several
indicators which show the current rig activity,
pumping and rotating status, and current state of
MWD Processing, Depth Tracking, and Online
Hydraulics. These last three display a green “traffic
light” when they are running and a red cross when
they are not. The final status indicator turns red
when error messages are written to the system Error
Log. It is otherwise green.
To quit the application, choose Exit from the File menu or
click the close box in the top right of the main window. A
Warning box is displayed to ask if you really intend to quit
the application.

Note: The system Message Server (MsgSvr) should

be running before RtProc is started. If it is
not, RtProc, which reads and writes to the
CDA controlled by the message server, will
take a long time to display its main window.
If you realize that this is the case, you can
start MsgSvr after RtProc and this should
speed up the appearance of RtProc's main
window and everything should run normally
thereafter.

.,-1 "# $!%& '()*

Confidential


 
    

 
-$$)


+
 + 
Up to 28 CDA items may be monitored with RtProc. Seven
are fixed items (Measured Depth, Bit Depth, Vertical
Depth, Block Position, Rate of Penetration, Hookload and
Weight On Bit). The remaining items are user-
configurable.

 
To configure an item, click on one of the buttons to the left
of a text field. This displays the following Available
Display Items window in Figure 3-111.

 " 0). - $ 

This window displays items from either the CDA or the

MWD Control file. The current source can be deduced by
which of the two source buttons at the top of the window
is depressed. If you want a list from the other source,
simply press that button. The order of items in the list can
be either by their position in the source CDA/file, or sorted
alphabetically. The Sort By button at the top right of the
window can be used to change the ordering if desired.

  ! .,-



 
     Confidential

 
-$$)


Either select an item in the list and press OK, or double-

click an item. The advantage to using the double-click
method is that the window stays open, allowing you to
choose others items on the main window and setting the
CDA source without having to continually display and
dismiss the Available Display Items dialog.
To clear an item from the main window, follow the same
procedure but choose the “Clear Item” entry in the list
(always at the top regardless of ordering).
The configuration is stored into the system registry and is
automatically loaded the next time that RtProc is started.

( 
 
Once you have configured the CDA display area the way
you want it, you should save that configuration to disk for
future use, especially if you wish to have different
configurations for use with different MWD tools, rig
activities, etc.
To save the current configuration, choose the Save Mnem
Setup item of the File menu. This displays the standard
Save File dialog shown in Figure 3-112.

 "  -

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


By default the dialog opens in the INTEQ ctl folder and

files with the .ucs extension are shown (as well as any sub
folders of ctl). A default file name (NewSetup) is inserted
into the Filename entry box. You can keep this and just
press Save, enter a new name (no need for .ucs) and press
Save, or choose an existing .ucs file to save into and press
Save. If you choose an existing file a warning is issued that
this action will cause the file to be overwritten.

! ( 

To load a CDA Display Item configuration that has been
previously saved, choose the Load Mnem Setup item of
the File menu. This displays the standard Load File dialog
shown in Figure 3-113.

 "" $

By default the dialog opens in the INTEQ ctl folder and

files with the .ucs extension are shown (as well as any sub
folders of ctl). You can enter a name (no need for .ucs) and
press Open, select an existing .ucs file and press Open, or
double click on an existing .ucs file If you choose a file that
does not exist, a message is written to the Error Log
explaining the problem.

  ! .,-



 
     Confidential

 
-$$)


+ /
Depth Tracking is usually the first of the three online
processing functions that is started (in order to provide
depth information to both the MWD and Hydraulics
processes). Depth Tracking runs as a background task in
RtProc. The results of the process are written to the CDA
and to the database (MWDTIME depth-time records,
DRILLDEPTH depth-keyed data, and GENTIME time-
keyed data).
Choose Depth Tracking from the Processes menu (or click
the equivalent toolbar button). This displays the following
tabbed window shown in Figure 3-114.

 "% 0). 

 0

There are five “tabs” on the window: Control, Setpoints,

Resets, Tide, and Heave. The first time the program is run
the selected tab will be Control. However, the program
remembers the last page viewed and opens the window at
that tab the next time it is displayed.

.,.
"# $!%& '()*
Confidential


 
    

 
-$$)


• Control: used to specify starting depth and other

information and to Start and Stop depth tracking.
Also used to specify whether tripping.
• Setpoints: used to specify a number of setpoints
used in the depth tracking logic
• Resets: used to reset various items calculated by the
depth tracking process, including depths, ROP, and
WOB.
• Tide: used to specify whether tidal correction is to
be used, and to enter tidal information.
• Heave: used to specify if heave correction is to be
used, and to enter data used in the heave correction.

 
6  
Use this page to enter starting information and to start
Depth Tracking (by pressing the Start Depth Tracking
button). The label of the button changes to End Depth
Tracking and the DT indicator in the status bar turns green.
The starting data text boxes are also disabled once depth
tracking has been started.
If the Stop Depth Tracking button is pressed, the label is
changed back, the DT indicator in the status bar turns red
and the starting data text boxes are re-enabled.
Use the radio buttons in the top right of the page to indicate
whether depth tracking is occurring while tripping in,
tripping out or not tripping (i.e., drilling).

 
6 (  
Choosing the Setpoints tab displays the following page as
shown in Figure 3-115.

  ! .,.



 
     Confidential

 
-$$)


 ", 0). $

 0

Refer to the Depth Tracking Logic section to see how these

setpoints affect processing. The Recording Depth and
Recording Time are not related to depth tracking logic but
specify how often to record DRILLDEPTH and
GENTIME surface data (respectively). Entering a value of
0 turns off recording of that table to the database.
The Set To Defaults button can be used to return the
setpoints values to a default set to serve as a starting point
for new setpoint entries.

 
6 2 
Choosing the Resets tab displays the following page shown
in Figure 3-116.

.,.- "# $!%& '()*

Confidential


 
    

 
-$$)


 "1 0).  0

The items on this page are only enabled when Depth

Tracking has been started. It can be used to reset calculated
depths, rate of penetration and weight on bit. There is an
interaction between the M.Depth, Bit M.Depth and Off
Btm Dist fields. For example, entering a value for Off Btm
Dist (Off Bottom Distance) calculates Bit M.Depth using
it and M.Depth. Pressing the On Bottom button forces Bit
M.Depth to the M.Depth value and sets Off Btm Dist to 0.
The Reset check boxes are set automatically when changes
are made to the associated text fields, but can also be
manually set or cleared. These Reset flags are
communicated to the background depth tracking process
which updates itself with the new information.
The Assumed ROP check box should only be used in the
extreme situation of losing data acquisition from the block
position sensor. Enter a value for ROP and check the
Assumed ROP box to force a calculation of Block Position
over time based on that ROP. This serves as an emergency

  ! .,..



 
     Confidential

 
-$$)

measure until the data acquisition problem can be
corrected.
The String Weight reset and associated AutoCalc OFF
check box allows you to turn off the default calculation of
the string weight from the hookload readings. Check the
AutoCalc OFF box and enter a value into the string weight
field. This affects the WOB which is calculated from string
weight and hookload.

 
6  
Choosing the Tide tab displays the following page shown
in Figure 3-117.

 "2 0).
 0

Here you can specify if tidal corrections should be factored

into the depth track processing. If so, you must enter tidal
information including times and tidal variation from mean
sea level.

.,./ "# $!%& '()*

Confidential


 
    

 
-$$)


 
6  
Choosing the Heave tab displays the following page shown
in Figure 3-118.

 "4 0). / 0

Here you can specify if heave smoothing is to be applied to

the block position acquired from the sensor. If it is, the
heave setpoint values used in the computation should be
checked for correct values. The Set To Defaults button will
fill in the text boxes with reasonable values that should be
good in most circumstances.

4+ 
RtProc performs all FE-MWD processing as a background
task. It accepts MWD DATAWORD messages from the
MWDecode application and applies corrections and
calibration information to the raw values. The raw and
corrected values are written the MWD_RAW_GENERIC
and MWD_GENERIC database tables respectively. The
values are also written to the CDA and displayed in the

  ! .,.0



 
     Confidential

 
-$$)


scrolling list in the RtProc main window.

The MWD indicator in the status bar is green when MWD
Processing has been started and red otherwise.

( 1(  6

Choose MWD Processing from the Processes menu. Refer
to Figure 3-119.

 "5 0). !3 0)

 $

The current status is displayed. The label of the left hand

button changes depending on the status. If MWD
processing is stopped, the label reads Start. Otherwise it
reads Stop. Use this button to start and stop processing.

  - 
Online hydraulics is a background task of RtProc. Real-
time values of mud weights, flow, etc. are read from the
CDA and, along with user-entered information, used in
calculations to produce values for ECD, Annular
Velocities, Pressure Losses etc. These values are written to
the CDA.
The HYD indicator in the status bar is green when Online
Hydraulics has been started and red otherwise.

.,.1 "# $!%& '()*

Confidential


 
    

 
-$$)


 ( 1( '

"6
Choose Hydraulics from the Processes menu to display the
following tabbed window in Figure 3-120.

 "6 0). /) 



There are four pages associated with the Hydraulics

window:
• Control: used to enter various setup data and to start
and stop processing
• Resets: used to reset various computed values
• Rheology: used to enter and calculate items such as
PV, YP, k, n etc.
• Cuttings: used to enter cuttings variables such as
size and density, used in slip velocity calculations.

"6 
This is always the selected page when the Hydraulics
window is displayed. The identifiers of the current
Annulus and Drillstring are displayed. If these are
incorrect (or if Annulus is blank or Drillstring number is
0), use the MSS configuration program to re-specify them.

  ! .,.



 
     Confidential

 
-$$)


The large button towards the base of the page is alternately

labeled Start Hydraulics or Stop Hydraulics depending on
the current status. You must press this button to stop or
start online hydraulics processing.

"62 

Choosing the Resets tab displays the page shown in
Figure 3-121.

 " 0). /) 

Use this page to reset items such as total volume pumped,

cumulative circulating time, and individual pump strokes.
Circulation events can be cleared and started from this
page. Choose the event to be started from the drop down
list.
You can also reset Mud Packets here. In the Online
Hydraulics processing model, the hole is comprised of a
specific set of Mud Packets (packets of drilling fluid of
equal volume). As circulation proceeds and drilling fluid is
pumped into the well, new packets are created while old
ones exit the annulus at the surface. These packets are
tracked around the well in order to monitor lagged
differences in such variables as mud weight, mud
temperature and mud resistivity. Similarly, as a packet

.,. "# $!%& '()*

Confidential


 
    

 
-$$)


passes the bit, the depths and amount of hole cut are saved
into the packet and used in Returns Depth and cuttings
loading calculations.
When Online Hydraulics is running, it is possible to view
the attributes of each monitored mud packet by selecting
Mud Packets from the View menu. See Figure 3-122.

 " 0). ! 0)* 



You can specify how often the information is updated and

also what to view for each packet (volume, cuttings length,
weight, temperature, resistivity, and depth).

"62
 " 
Choose the Rheology tab to display this page shown in
Figure 3-123.

  ! .,.



 
     Confidential

 
-$$)


 "" 0). /) (

Here you choose which Hydraulics Model to use in

processing (Bingham or Power Law) and derive PV, YP, k,
n and Viscometer readings from one another.
First check two boxes in both the Use In Ann and Use In
Pipe columns. Then, knowing either Viscometer readings
or PV and YP (for both annulus and pipe), it is possible to
derive the other values.
Viscometer values known
Enter viscometer readings against the appropriate RPM
speeds. Then press the “Calc PV,YP, k & n” buttons.
The Annulus and Pipe PV and YP values are calculated, as
are k and n values.
PV and YP known
Enter PV and YP for annulus and Pipe. Press the “Calc Ann
k, n & Vis” button and the “Calc Pipe k, n & Vis” buttons
to calculate k and n values, and to back-calculate
viscometer readings.

.,/
"# $!%& '()*
Confidential


 
    

 
-$$)


"6  

Choose the Cuttings tab to display the page shown in
Figure 3-124.

 "% 0). /) 



This page allows you to specify cuttings density, diameter,

thickness and shape. This information is used in the slip
velocity calculation.

  )  '#

The Relog Number is used as a key variable in identifying
recorded data. It is therefore essential that the Relog
Number be set correctly.
When drilling new hole the Relog Number is always 0.
However, if a section of hole is to be re-logged, the Relog
Number should be incremented. The first time a section is
re-logged, the Relog Number is 1; the second time, the
Relog Number is 2, etc.
Changing the Relog Number is done manually using the
window displayed when Relog Number is selected from
the MWD menu shown in Figure 3-125.

  ! .,/



 
     Confidential

 
-$$)


 ", 0).  ;

When a relog is going to take place, increment the relog

number to the appropriate value. Prior to drilling new hole
again, return it to a value of 0.

   $-  )

It is possible to calculate bottom-hole resistivities from
surface values and bottom-hole temperature by choosing
Calculate BH Res from the MWD menu shown in
Figure 3-126.

.,/- "# $!%& '()*

Confidential


 
    

 
-$$)


 "1 0). ) 9 / 

You can calculate bottom-hole Rm from either Surface Rm

or Surface Chlorides. Enter the depth, surface information
and bottom-hole temperature and then press the “Calculate
BH Rm/Rmf” button. The results are displayed in the
bottom two (read-only) text boxes.

 * 
The current system units conversions can be viewed/
changed by choosing Configuration from the Units menu.
See Figure 3-127.

  ! .,/.



 
     Confidential

 
-$$)


 "2 ) 




Choose the units type to be modified from the list. The

available conversions are shown in the box labeled
“Units”. Choose the conversion you want to use for that
type. Repeat this procedure for other types if required.
Press OK to save the changes.

Note: Changes to the system conversion table are

broadcast to other applications which will
change their displays accordingly if they are
set up to handle the message.

:  0 ;

The system Error Log (error.log in the INTEQ ctl folder)
contains messages from all INTEQ applications. An
indicator in the status bar, labeled Err, shows the status of
.,// "# $!%& '()*
Confidential


 
    

 
-$$)


the Error Log. If a new error message is written to the log,

by RtProc or an other application, the indicator turns red.
Either click on it or choose Error Log from the View menu
to pop up the Error Log listing. See Figure 3-128.

 "4 & +

You can sort the list either ascending or descending on

time and you can choose to only view messages generated
by a certain application.
When you close this window, the Err indicator changes to
green until the next error message is generated.

:  + /  4+ ;

From the View menu it is also possible to display the
contents of the Depth Track log (dtrak.log in the INTEQ
ctl folder) and MWD log (mwd.log in the INTEQ data
folder) by choosing Depth Track Log and MWD Log

  ! .,/0



 
     Confidential

 
-$$)


respectively from the View menu. Both display the

information shown in Figure 3-129.

 "5 0). + +



Press Close when you have finished viewing the log.

   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

.,/1 "# $!%& '()*

Confidential


 
    

 
-$$)


+ ; &+ (


Dlogger is the data logger program used to record “real-
time” data to the database. The source of the data is the
Common Data Area (CDA) and you can configure the
program in terms of which CDA items values to store into
which database tables, how often and under what rig
conditions.
The program consists of a front-end user interface for
record configuration and a background process that does
the actual recording, as well as other data manipulation
such as averaging. You can start the background process
manually or it can be set up to run automatically when the
program is started (using the last saved configuration).
In summary, the program is used to:
• configure the records to be written to the database
• specify the frequency of recording, also the valid rig
conditions for recording
• perform averaging and calculate minimum and
maximum data values
• record data records

Note: The message server program (MsgSvr)

should be running before starting Dlogger
since it controls the CDA. Similarly, the
RtProc program's depth tracking processing
should also be running in order to provide
depth values.

When started, the following main window is displayed.

See Figure 3-130.

  ! .,/



 
     Confidential

 
-$$)


 ""6  + 



 )


The window is made up a several distinct areas:

A The menu bar. All program functions are accessibly
through the menu bar.
B The toolbar. The buttons are shortcuts to menu
items. Hold the cursor over a button momentarily to
get a brief description.
C The record type to be configured, select from a drop-
down list.
D Attributes of the selected record type along with
their current data source (CDA item) and type
(raw, average, minimum, maximum)
E Triggers for the selected record type. Up to three
triggers can be assigned.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


A trigger consists of four components: CDA item,

interval change type (fixed, percentage,
incremental), interval value and valid rig activity.
F Valid Rig Activity selection. Use the check boxes to
mark all valid conditions for recording.
G The data logger message area where messages about
recording are displayed
H The status bar used to display application
messages.
To quit the application, choose Exit from the File menu or
click the close box in the top right of the main window. A
Warning box is displayed to ask if you really intend to quit
the application.

 ) 

&+# # (
Dlogger configuration information is stored into the
DLOGCONFIG and DLOGTRIGGER tables of the
database. The last configuration stored in these tables is
loaded when the program starts-up. You can then make
any modifications required.
• Select records to be recorded.
There are two ways to turn records “ON” or “OFF”. Either
choose Table Status from the Configuration menu or right-
click anywhere on the gray background of the main
window. The Table Status Control window is displayed in
Figure 3-131.

  ! .,/



 
     Confidential

 
-$$)


 ""  +.
  



A check box to the left of the table (record type) name

shows its current status. A checked box indicates the record
is turned ON while an empty box indicates it is OFF. Click
on the check box to change a record's status as required.
Once all changes have been made, press OK to save them
and dismiss the pop up window.
• Select the record type to be configured
The available record types appear in the drop-down list.
Select the type to configure from this list.

Note: Several database tables are written to by

other online programs. For example, RtProc
writes the following: MWD_TIME,
DRILLDEPTH, GENTIME,
MWD_RAW_GENERIC, MWD_GENERIC.
SvyPrc writes these: SURVEY_RAW,
SURVEY.

When the record type is changed, the attribute list also

.,0
"# $!%& '()*
Confidential


 
    

 
-$$)


changes.
• Configure record attributes.
To configure a record attribute, double-click the
appropriate row. This displays the following window as
shown in Figure 3-132.

 ""  +. - !


)

The top box shows the currently selected CDA source for
the record attribute. Similarly, the current Data Type is
shown in the series of radio buttons beneath the list of
available CDA items. As required, select a new CDA item
source from the list and/or change the Data Type. Then
press OK to save the changes and dismiss the window. The
selected row is updated with the new configuration. Repeat
this for any other attributes that need modification.

Note: Double-clicking a CDA item immediately

dismisses the pop up window and updates
the selected row in the attribute list.

  ! .,0



 
     Confidential

 
-$$)


• Configure record triggers

Double-click on the CDA Item name (or “Unassigned”
label) next to one of the three numbered triggers. This
displays the following window in Figure 3-133.

 """  +. - !


)

This represents the CDA item whose change in value

triggers recording to the currently selected record type.
Select an item from the list, or choose “Unassigned”. Then
press OK to save the changes and dismiss the window. The
selected trigger mnemonic is updated. Repeat this for other
triggers that need changing.

Note: Double-clicking a CDA item immediately

dismisses the pop up window and updates
the selected trigger.

Next, choose the interval change type and the interval

value:

.,0- "# $!%& '()*

Confidential


 
    

 
-$$)


• Fixed: any positive or negative absolute change in

the value of the trigger mnemonic of the specified
Interval amount triggers a new record (compared
with the last value read for the item)
• Percentage: any positive or negative percentage
change in the value of the trigger mnemonic of the
specified Interval amount triggers a new record
(compared with the last value read for the item)
• Incremental: any positive change in the value of
the trigger mnemonic of the specified Interval
amount triggers a new record (compared with the
last value read for the item)
Finally, choose the rig conditions when recording of the
currently selected record is valid. Check as many of the
activities as required or check Always to record no matter
what the activity. Clearing all boxes effectively turns the
record OFF.

& 
 
If, for whatever reason, you want to revert to the
configuration in the database and lose any changes you
have made since start-up, choose Undo Changes from the
Configuration menu.

( 
 
Once you have configured the record(s) the way you want
them, save the configuration by choosing Save Changes
from the Configuration menu. This saves the changes to
the DLOGCONFIG and DLOGTRIGGER tables of the
database.

 + ; )

Choose Start/Stop Dlogger from the Dlogger menu to
start the background recording process. A message is
displayed on the scrolling message area to indicate that
recording has started. For example:

  ! .,0.



 
     Confidential

 
-$$)


Recording Started: June 16, 1998

08:21:22 AM
A check mark next to the menu item and the depressed state
of the toolbar button indicate that recording has been
started.
As database records are written, messages appear in the
scrolling list. Check that the records that you have turned
ON are recording at the intervals you expect. If not, check
the status and triggers of the record in question.

*   4 

)
If changes are needed in the configuration once recording
has been started, make them as described in the previous
section, save them, and then choose Apply Changes from
the Dlogger menu. This causes a stop and then restart of
the background processing during which the saved
configuration is loaded.

 + ; )

To halt recording, choose Start/Stop Dlogger from the
Dlogger menu. The background process halts and a
message is written to the screen:
Recording Stopped: June 16, 1998
09:21:22 AM
The check mark is removed from the menu item and the
toolbar button returns to its non-depressed state.

 * 
The current system units conversions can be viewed/
changed by choosing Units Conversions from the Options
menu. See Figure 3-134.

.,0/ "# $!%& '()*

Confidential


 
    

 
-$$)


 ""% ) 





Choose the units type to be modified from the list. The

available conversions are shown in the box labeled
“Units”. Choose the conversion you want to use for that
type. Repeat this procedure for other types if required.
Press OK to save the changes.
All data recorded to the database are in S.I. units regardless
of the Units Conversions configuration.

Note: Changes to the system conversion table are

broadcast to other applications which will
change their displays accordingly if they are
set up to handle the message.

  ! .,00



 
     Confidential

 
-$$)


   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

.,01 "# $!%& '()*

Confidential


 
    

 
-$$)


  <  + &(


Online Torque & Drag is the real time version of the well
planning Torque & Drag used in RES, EC*Trak and
DEAPTEQ (BHI Model).
Online T&D is designed to give the Directional Driller,
Driller and Tool Pusher real time information on subjects
such as the friction factor trend, WOB reserve until
buckling, buckling information, fatigue, and yielding
information.
From this information you can extract several downhole
conditions or changes in conditions that should help you
make decisions on how to proceed. You should be able to
detect much earlier when there is a change in mud
lubricity, hole cleaning problems or stuck pipe.
Online T&D basically calculates a force equilibrium over
the drillstring and calculates the forces on and within the
drillstring. The forces on the drillstring include friction
from the borehole. This is dependent on the normal force
and on the friction factor. Friction is only present when the
drillstring moves.
There are two fundamentally different methods of
calculating the friction factor within this program.
First, there is the Incremental FF method. The
incremental FF algorithm calculates a FF for the drillstring
to the depth where the FF log starts and from there on it
calculates a FF for incremental steps until a new sensor
signal has been recorded or you start a new calculation.
This assumes that the FF in the preceding element(s) stays
constant. In this way you can immediately see at what bit
depth the friction increased. A disadvantage is that any FF
changes in other parts of the well are attributed to the last
element and therefore a FF change does not express at
what part of the drillstring the increased FF is originating
from. To make the general tendencies clearer, the changes

  ! .,0



 
     Confidential

 
-$$)


in the incremental FF can be averaged over specified

lengths. (Experience shows that averaging over 25 meters
is sufficient.)
The second method is the Well FF method. In this
algorithm the FF is always calculated over the complete
wellbore. The FF changes here are really small as they are
averaged over the complete drillstring, but give realistic FF
values representing the complete drillstring wellbore
interaction.
Ontad uses either downhole information supplied by an
MDP sub or CoPilot tool, using downhole TOB and WOB,
and surface data or just surface data. When downhole
information is available the FF calculation can be
incremental or for the complete well. With just surface
data, measurements are performed during off bottom
rotation, slack off or pick up and a FF calculation should be
done for the complete well.
The software is applicable for conventional drilling and
coiled tubing (reeled system).


At start-up, the program loads data from the Windows
registry and database and displays the main window shown
in Figure 3-135.

.,0 "# $!%& '()*

Confidential


 
    

 
-$$)


 "", 
 !
3


Some important parts of the window are:

Menus & Toolbar
These allow you to access setup windows as well as the
MSS drillstring, annulus, and survey editors.
Plot type choice
A row of radio buttons above the main graphical display
area allows you to select the graph to be plotted:
1. Friction Factor trend
2. Drillstring in the well with colored buckling
information
3. WOB Reserve until buckling occurs
4. Axial Analysis with rotation

  ! .,0



 
     Confidential

 
-$$)


Status fields
These fields display the values of the CDA mnemonics
specified in
  # &
$.
The averaging time and the mnemonic for the Averaged
Torque and the Averaged HKLD value must be setup in

 


.
The Averaged HKLD is always the averaged raw HKLD.
If the “Indicated HKLD” option is checked (in the General
setup window), the correction is performed internally.
Safety Factors
The Min. Fatigue and Min. Yield Safety Factors are
presented here. See the Theory section for further details.
Calculate
The Calculate action from the Calculate Menu is used to
start a new calculation manually.
If the Reset Friction Factor Menu is pressed the complete
friction factor set is deleted and a new friction factor for the
well is calculated. The former Results are still stored in the
BakerFF.log but can not be reloaded again. If you want to
reload the former FF then you have to backup BakerFF.ctl
file and copy the file back if needed. See the Results
Friction Factors chapter for more information.

.,1
"# $!%& '()*
Confidential


 
    

 
-$$)


Graphical Displays
Friction Factor (see Figure 3-136).

 ""1 )

)

This presents friction factors versus measured depth for the

well.
The absolute value for the friction factor is not that
important. The important thing is the trend. In the
  $
 $
 menu you can specify which
friction factors should be shown here:
1. Raw incremental FFs
2. Averaged incremental FFs
3. Well FFs
The FF trend indicates hole cleaning, stuck pipe, and mud
lubricity problems.
See below for more information on the incremental and
well friction factors.

  ! .,1



 
     Confidential

 
-$$)


Buckling (see Figure 3-137).

 ""2 9)*



The drillstring is shown along the well path. Green

indicates no buckling. Yellow parts of the string are
buckled sinusoidal and the red parts are buckled helical.
Drilling with helical buckled drillstring sections should be
avoided.

.,1- "# $!%& '()*

Confidential


 
    

 
-$$)


WOB Reserve (see Figure 3-138).

Helical Buckling Starts

 ""4 39 

In this graphic the corresponding WOBs for a given HKLD

are presented. For this calculation the calculated friction
factors are used. It can be seen that a decreased HKLD
(less tension at surface) does not lead to much higher
WOB. This is caused by the fact that the drillstring is
buckled helically and in the extreme case no WOB
increase is realized because the drillstring is locked up.
You can see in this graphic how far the HKLD can be
decreased before helical buckling starts.

  ! .,1.



 
     Confidential

 
-$$)


Axial Analysis with Rotation (see Figure 3-139).

 ""5 -> -

 ( 

In this graphic, the difference between the HKLD and the

downhole WOB is presented.
This plot should be observed if you are drilling with
rotation and thus the rotational friction factors are
calculated.
Because almost no drag is applied while drilling with
rotation, an axial friction factor analysis can be executed
with this option.

 

8(
Selecting General from the Setup menu displays the
following window shown in Figure 3-140.

.,1/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "%6 :
 $

Data Acquisition Interval

Specify how often the CDA should be read.
Drill Floor Height
Enter the height of the drill floor if Measured Depth is not
referenced at the drill floor.
Calculation Start
Event Dependent: The calculation starts automatically if
the CDA is updated with new sensor data and the time
averaging interval has ended.
User Dependent: The calculation must be started by
choosing the “Calculate” menu item.
Distance MDP Sub - Bit
If an MDP or CoPilot sub is used, enter the distance
between the sub and the bit.

  ! .,10



 
     Confidential

 
-$$)


FF Plot Start Depth

Enter the Start Depth for the y-axis of the FF plot.
Indicated Hookloads Calculation
Checking this option enables a conversion of measured
surface loads to real hookload data, as it is observed on a
deadline-type weight indicator, through user-selectable
application of a correction algorithm for Traveling
Assembly Weight and Strung Line Friction in both
traveling and crown block assemblies.
Only Incremental Frict. Fact. Calculation
If this option is checked, the calculation algorithm
calculates only incremental and not well friction factors. If
it is disabled, both incremental and well friction factors are
calculated. The default should be unchecked.
Incremental Friction Factors are only valid for a small
interval. Well Friction Factors are valid for the complete
well.
Due to sensor resolution restrictions it is usually the case
that incremental friction factors are not calculated as often
as well friction factors.

6(
Selecting Calculation from the Setup menu displays the
window shown in Figure 3-141.

.,11 "# $!%& '()*

Confidential


 
    

 
-$$)


 "% )

$

Buckling Model
The application supports two Buckling Criterion’s, the
Conservative (Unloading) and Extended (Loading)
approach.
It is advised that the Conservative approach is used to
model buckling of the tubing in order to recognize at an
early state that tubular buckling might be a problem.
In case buckling has been recognized for the simulation,
the Extended approach should be checked in a next step as
well. When the Extended criterion does not indicate
buckling.
For a Conservative approach, the critical compressive load
for sinusoidal buckling in straight wellbore sections is
calculated using the formula developed by Dawson and
Paslay, which is widely used and accepted throughout the

  ! .,1



 
     Confidential

 
-$$)


industry. In case of curved wellbore sections, the effect of

curvature on buckling resistance is considered for as well.
In the case of vertical wells, the basic work on tubing
buckling by Lubinski is used. The conservative approach
models unloading of tubulars and combines equations for
helical buckling as published by Chen, Lin & Cheatham,
Lubinski and He & Kyllingstad.
The Extended buckling criterion models buckling more
accurately when loading a tubular drillstring than the
Conservative approach. For the Extended buckling
criterion, a set of equations for both, sinusoidal and helical
buckling, as provided by Juvkam-Wold and Wu are used.
Rig Operation
Select the rig operation in which you want to perform the
calculation:
Pick Up
The friction factors are calculated with the measured
Surface Loads, RPM, ROP, WOB, and TOB assumed to be
zero and a top movement direction.
Slack Off
The friction factors are calculated with the measured
Surface Loads, RPM, ROP, WOB, and TOB assumed to be
zero and a down movement direction.
Rotation off Bottom
The friction factors are calculated with the measured
Surface Loads, WOB, and TOB assumed to be zero and a
no axial movement.
Drilling
The friction factors are calculated with the measured
Surface Loads, RPM, ROP, and the measured WOB and
TOB.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


Friction Factor Averaging Interval

The incremental friction factors are averaged over this
length interval.
Calculation Method
The application has two methods of calculating a friction
factor:
Force Method and Torque Method
With the Force Method a sliding friction factor is
calculated. With the Torque Method, a rotational friction
factor is calculated.
If you want to calculate only sliding friction factors, use
the Force Method. If you want only rotational friction
factors, use the Torque Method.
The sliding friction factors can only be calculated if the
drillstring is not rotating. The rotational friction factors can
only be calculated if the drillstring is rotated. The internal
algorithm uses the averaged HKLD and the WOB for the
sliding friction factor iteration. The averaged Surface
Torque and TOB is used for the rotational friction factor
iteration.
Normally the sliding friction factors are a little bit higher
than the rotational friction factors.
If you choose the “Automatic” option dependent on the
RPM value, the “Force Method” or the “Torque Method”
is selected automatically.
Troubleshooting: If the rig operation is changing often
between rotating and non-rotating and incremental friction
factors are evaluated and no conversion for friction factors
are calculated, you have to Reset the Friction Factors
(Calculate menu). The new trend should then be observed.
M.Depth versus Friction Factor Table
Within the Friction Factor input section, Friction Factors
along the well path can be provided. The well path can be

  ! .,1



 
     Confidential

 
-$$)


divided in multiple sections with different Friction Factors

applied.
This option can be used if the friction factor (e.g., for the
casing) is known.
Mud Weights Setup
Selecting Mud Weights from the Setup menu displays the
window in Figure 3-142.

 "% ! 3( $

The two tables display the Interval-specified variable-

density static fluid-profile descriptions for both
“drillstring” bore and annulus and permit evaluation of
rotation or reciprocation loads during liner or casing
cementing operations, as well as the use of “buoyancy-
assist” techniques for running casing or liners in wells with
high displacement/TVD ratios (i.e., extended-reach wells).
Use Online Mud Weights
Check this option to enable a direct use of mud weights
from the CDA. If the mud weights are changed the
calculation algorithms automatically use the CDA values.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


Inner Fluid Density

Choose the CDA mnemonic used for the inner fluid
density.
Outer Fluid Density
Choose the CDA mnemonic used for the outer fluid
density.
HKLD Setup
Selecting HKLD from the Setup menu displays the
following window shown in Figure 3-143.

 "%" 
) /* $

Block Weight
The Traveling Assembly Weight or block weight needs to
be provided to enable the algorithms to perform a
conversion of the measured surface loads to real hookload
data, as it is observed on a deadline-type weight indicator.

  ! .,



 
     Confidential

 
-$$)


Correction Method
The default checked option should be “Theory”.
Strung Line Friction/Sheave Efficiency
The Number of Strung Lines need to be provided to enable
the algorithms to perform a conversion of measured
surface loads to real hook-load data, as it is observed on a
deadline-type weight indicator by allowing for frictional
losses in the hoisting system.
An efficiency of 97% is assumed per strung line. A typical
rig setup includes 10 strung lines; more modern rigs may
have 12, some even 16 lines.
Percentage
Pick Up Percentage/ Drilling/ Slack Off Percentage
Enter the percentage value for moving the string down and
up. The evaluation of default percentage values is an
ongoing project. Until now no statement can be given.
CDA Mnemonics Setup
Selecting CDA Mnemonics from the Setup menu
displays the following window. See Figure 3-144.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "%% - $

In the CDA Setup window, you select which CDA

mnemonics are to be used for the required program
sensors. The available mnemonics for each sensor depend
upon the conversion factors.
For the Avg. HKLD and Avg. Surface Torque two special
items should be selected in the CDA: HKLD_TD and
TORQUE_TD. The raw HKLD and Surface Torque data
are chosen in the “Sensor Setup” pop up.
Surface Sensor Setup
Selecting Surface Sensor from the Setup menu displays the
following window shown in Figure 3-145.

  ! .,.



 
     Confidential

 
-$$)


 "%, 
 $

HKLD Averaging
Choose the CDA mnemonic for the raw HKLD and for the
HKLD Target. The raw HKLD is averaged over the
specified Averaging Interval and is written to the HKLD
Target value.
The default value of 30 seconds for the Averaging Interval
is for a data acquisition interval of 1 second. Thus 30
values are averaged.
The averaging interval is a multiple of the Data acquisition
interval.
Surface Torque Averaging
Choose the CDA mnemonic for the raw Surface Torque
and for the Surface Torque Target. The raw Surface Torque
is averaged over the specified Averaging Interval and is

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


written to the Surface Torque Target value.

The default value of 30 seconds for the Averaging Interval
is for a data acquisition interval of 1 second. Thus 30
values are averaged.
The averaging interval is a multiple of the Data acquisition
interval.
Units Setup
Selecting Units from the Setup menu displays the window
shown in Figure 3-146.

 "%1 ) 





The Engineering Units can be changed at any time by

selecting the Unit Conversions utility from the Setup
menu.
The Engineering Units used in Ontad and associated
editors are:

  ! .,0



 
     Confidential

 
-$$)


(AN) Angle … Inclination and Azimuth

(DI) Diameter … Diameter
(DL) Dogleg … Dogleg, Build, Turn
(EM) Elastic Moduli … Elastic Moduli
(FD)

Note: The unit conversion FD Fluid Density is not

used. Please check for MD Mud Density.

(LD) Length or Depth … measured depth, TVD, N-S, E-

W
(LF) Load or Force … WOB, HKLD
(MD) Mud Density … Reference Mud Density
(MS) Mass … Motor Weight
(RM) Rev/Unit Time … min/max Operating Speed
(RP) Rate of Penetration… Axial Velocity
(SC) Time in seconds … data acquisition time
(SR) Stress … Yield and Tensile Strength
… Endurance Limit
… max ___ Stresses
… Stress distribution
(SW) String Weight … actual and nom. Linear weight
(TQ) Torque … TOB
Results Menu
Friction Factors
Selecting the Friction Factors option from the Results
Menu displays the window shown in Figure 3-147.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


 "%2 )

)
Loads & Torques
Selecting the Loads and Torques option from the Results
menu will display the window in Figure 3-148.

 "%4 + 


=

  ! .,



 
     Confidential

 
-$$)


The internal Axial Force, Torque, and distributed Normal

Loads along the well path are presented.
The Axial Force at surface is the corrected averaged
HKLD. The axial Force at the bottom is the WOB.
The Torque at the surface is the averaged Surface Torque.
The Torque at the bottom is the TOB.



8 (
The following steps must be performed to start the MSS
Online Torque & Drag program:
1. Start the MsgServer (if not already running).
2. Start MSS and select a well/path and create an online
annulus, tubular and survey.
3. Start Ontad.
4. Go through the Ontad Setup menu and define all
input values.
5. Wait until a new sensible sensor data set is available,
and press “Reset Friction Factors”.
6. Check the friction factor in the Results pop up.
7. Repeat steps 5 and 6 several times to see if the
friction factors are the same and so the sensors are
calibrated correctly.
8. If the friction factor is not in the range between 0.1
and 0.5 and the sensor values are sensible, check the
Indicated HKLD’s setup and “calibrate” the
corrected HKLD by changing the sheave efficiency
or the block weight.
9. Repeat steps 5 through 7.
10. If rotational FF are calculated with the Torque
method (RPM > 0) you have to check if the
calculated HKLD and the corrected HKLD are
., "# $!%& '()*
Confidential


 
    

 
-$$)


identical. The corrected HKLD is stored in the

BakerFF.ctl file and the calculated HKLD is
presented in Results - Loads and Torque (axial load
at surface).
11. If they are not the same, change the Indicated
HKLD’s setup and “calibrate” the corrected HKLD
by changing the sheave efficiency or the block
weight. The corrected HKLD and the calculated
HKLD must be the same (as much as possible).
12. Repeat steps 5 through 11.
13. If the program has been started in the correct way it
will run automatically for the complete job.

2 
 
There are two ways for the program to start calculating:
User dependent
You have to press the “Calculate” menu to start a new
calculation.
Event dependent
You choose “Event Dependent” in the General Setup for
“Calculation Start”.
The program starts a new calculation automatically if the
following conditions are fulfilled:
• Drilling
• Force Method - new WOB and HKLD and the
averaging interval has been run through
• Torque Method - new TOB and Surface Torque and
the averaging interval has been run through
• Rotation off Bottom - new HKLD and Surface
Torque and the averaging interval has been run
through

  ! .,



 
     Confidential

 
-$$)


• Pick Up - new HKLD and Torque and the averaging

interval has been run through
• Slack Off - new HKLD and Torque and the
averaging interval has been run through

2
Friction Factors
The application has two means of calculating the friction
factor:
1. Only incremental friction factor calculation
2. Incremental and well friction factor calculation
If the Only Incremental Friction Factor:
Calculation option is checked the calculation algorithm
calculates only incremental and not well friction factors. If
it is disabled both incremental and well friction factors are
calculated. The default should be a disabled checkbox.
Incremental Friction Factors are only valid for a small
interval, while Well Friction Factors are valid for the
complete well.
Since the incremental Friction Factors are stored for an
interval and assumed to be constant, a friction increase in
the upper sections results in a higher new calculated
friction factor. Friction changes over a long upper interval
result in a much higher calculated friction factor for the last
interval. If the problem causing this higher friction (stuck
pipe, hole cleaning problems, etc.) disappears, the
calculated friction factor for the last interval drops rapidly
to near. zero. If this happens the “Reset Friction Factor”
menu option can be pressed to reset all friction factors and
start to observe a new friction factor trend.
Due to sensor resolution restrictions, it is normal that
Incremental friction factors are calculated less often than
Well friction factors.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


If the calculated friction factors are less than zero or bigger

than 2.0, the calculation is aborted and an error message is
written to the error.log file.
The friction factor trend must be evaluated to identify
drilling performance problems.
The following features can be examined by observing the
friction factor trend:
Mud Lubricity: The friction factors are evaluated to
determine the effectiveness of mud additives.
Hole cleaning: The effectiveness of cuttings removal from
the wellbore will be estimated with the online calculated
friction factors as an early indication of drillstring
becoming stuck in the borehole.
Sticking Pipe: The calculated friction factors identify
when the drillstring is becoming stuck, or BHA
components hanging on ledges enabling the driller to take
remedial action.
Below are some examples on case histories:
Case History 1:
• Increased Friction Factor validated by a lower ROP.
• Most probably caused by hole cleaning problems.

  ! .,



 
     Confidential

 
-$$)


• Friction Factor calculation performed with surface

data only (rotation off bottom). See Figure 3-149.

 "%5  / 

Case History 2:
• Friction Factor fluctuations for incremental steps
and well Friction Factors.
• Correlation to RPM charts show sharp decrease in
Friction Factor after string rotation
• In addition to string rotation there was off bottom
rotation and circulation at 1,870 m and 2,040 m
MD.
• Friction Factor increases when drilling in sliding
mode.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


• Friction Factor increases when drilling in sliding

mode. See Figure 3-150.

 ",6  / 

Case History 3:
In order to be able to see real tendency changes we have to
average the incremental FF.
From top down we see averaging over 10, 20, and 30
meters.
Only in the last graphic does it become clear that
something is changing after 3,700 meters MD. See
Figure 3-151.

  ! .,.



 
     Confidential

 
-$$)


 ",  / "

Case History 4:
• Mud change leading to higher Friction Factors.
• To stop losses, additives were added to the mud
starting at 3,700 m MD in order to build a sealing
mud cake. See Figure 3-152.

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 ",  / %

6 
The Ontad program shows you in a colored display which
parts of the drillstring are buckled and in which way
(not buckled, sinusoidal buckled, helical buckled).

'
2&
6 '66

If the WOB reserve check box in the main plot window is
enabled, the relation between the HKLD and the WOB is
graphical presented.
If you are drilling without rotation, the minimum HKLD
can be seen in the graphic until lock up occurs. If you are
drilling with rotation, realistically no lock up can occur.
Min. Fatigue and Min. Yield Safety Factors
The minimum Yield and Fatigue Safety Factors are
reported in the main window.
Yield Safety Factor
The Yield Safety Factor is defined by the ratio of the Yield
Strength (material property specified in the Tubular
Editor) and the Equivalent or Combined Stress. A Yield

  ! .,0



 
     Confidential

 
-$$)


Safety Factor of 1.0 essentially means that no stress reserve

is available anymore. A minimum acceptable Yield Safety
Factor is recommended as 1.3. Any accepted value less
than 1.3 requires very careful operation; therefore, a strike
limitation of e.g., WOB would be required when accepting
such a scenario.
Fatigue Safety Factor
The Fatigue Safety Factor calculation is based on the
Endurance Limit provided in the Tubular Editor. The
Fatigue Safety Factor definition is based on the assumption
of 106 rotations. The Endurance Limit provided is defined
as the alternating stress level a tubular can withstand when
rotating 106 times and no fatigue occurs. When rotating 106
times with an alternating stress level equivalent to the
Endurance Level, no fatigue will occur; when rotating (106
+ 1) times with the same stress level, fatigue will occur.
This transition is defined with a Fatigue Safety Factor of
1.0.

Note: A very common problem where fatigue

problems are indicated by the T&D
application is when rotating a drill pipe
through a very large, single spot dogleg. In
this case, a Fatigue Safety Factor less than
1.0 occurs just at one position, the position
of the large dogleg. Such a scenario may be
accepted when ensuring that the same joint
or stand of drill pipe does not get rotated all
the time at the same depth. You need to
avoid the 106 rotations. Attention: Intensive
Back reaming expected!

Note: In case a series of Fatigue Safety Factors

less than 1.0 are indicated, in high curvature
wellbore sections, slide drilling should be
considered.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


+:5:

There are two control files existing:
• BakerFF.log
This file contains a friction factor log of all
calculated friction factors and the corresponding
sensor data during the job and is updated whenever
you restart the program.
• BakerFF.ctl
This file contains the currently used friction factors.
It will be updated every time a new calculation has
been performed.
The following layout is used in both ctl files:
Measured Depth, Bit depth, Surf. WOB, Incremental
Friction Factor, Well Friction Factor, corrected HKLD,
Torque, WOB, TOB, ROP, RPM, Rig status, Min. Yield
Factor, Min. Fatigue Factor, HKLD WOB Difference.
There are 5 Ontad database tables in the MSS/RES
database:
• ONTD_CALC - calculation setup table of interface
settings
• ONTD_FRICTION - input friction factor table
• ONTD_INNERMUD - input inner mud table
• ONTD_OUTERMUD - input outer mud table
• ONTD_RESULTS - friction factor results table
(raw incremental FF or aver. Incremental FF or well
friction factors, dependent on the interface results
setup)
In the CDA the last calculated well friction factor and the
last calculated incremental friction factor can be found in
FRICT_WELL and FRICT_INCREM.

  ! .,



 
     Confidential

 
-$$)


' &
The online Torque & Drag application has built-in online
help. You can press the F1 button or use the right mouse
button “What’s this?” to activate the context sensitive help.
It is also possible to search for keywords and get further
information under the Help menu.



6
The Buckling Criterion options available are either
Conservative (unloading) or Extended (loading).
It is recommended that the Conservative approach is used
to model buckling of the tubing in order to recognize at an
early state that tubular buckling might be a problem.
In the case where buckling has been recognized for the
simulation, the Extended approach should be checked in a
next step as well. When the Extended criterion does not
indicate buckling, operating parameters such as maximum
WOB need to be limited.
For a Conservative approach, the critical compressive load
for sinusoidal buckling in straight wellbore sections is
calculated using the formula developed by Dawson and
Paslay, which is widely used and accepted throughout the
industry. In case of curved wellbore sections, the effect of
curvature onto buckling resistance is considered for as
well. In the case of vertical wells, the basic work on tubing
buckling by Lubinski is used. The conservative approach
models unloading of tubulars and combines equations for
helical buckling as published by Chen, Lin & Cheatham,
Lubinski and He & Kyllingstad.
The Extended buckling criterion models buckling more
accurately when loading a tubular string than the
Conservative approach. For the Extended buckling
criterion, a set of equations for both, sinusoidal and helical
buckling, as provided by Juvkam-Wold and Wu is used.
., "# $!%& '()*
Confidential


 
    

 
-$$)


(:(( 
The online Torque & Drag software uses a Stiff String
Model while other oilfield drillstring simulation programs
commonly use the Soft String model. The Soft string
model does not apply for the bending resistance of tubular
strings in highly curved wellbore sections while the Stiff
String model does.
However, the results obtained in wellbores with dogleg
severity’s less than approximately 10 [deg/100 ft.] are very
similar to those determined with a Stiff String model.
For applications with borehole curvature larger than 10
[deg/100 ft.], it is strongly recommended that the Stiff
String model be used.
How are the friction factors calculated? See Figure 3-153.

 "," -( 

With the measured HKLD1, Surface Torque1, DWOB1,

DTOB1, RPM1 and the calculated ROP1, the friction
factor is calculated. The calculation starts at the bottom
with DWOB1 or the DTOB1 (depending on whether RPM

  ! .,



 
     Confidential

 
-$$)


is greater or smaller than 0) and an assumed friction factor

of 0.3. The drillstring is divided in 30 feet elements and the
cutting forces are calculated at each node. The procedure is
repeated until the surface is reached. If the calculated
HKLD or the Torque matches the measured one the correct
friction factor is found. If not the friction factor is iterated
as long until the Surface load matches the calculated
surface load. Refer to Figure 3-153.
While drilling with rotation the “Torque” method must be
used. While drilling without rotation the “Force” method
must be used. It is clear that while drilling without rotation
the “Torque” can not be used because no Surface Torque is
applied. The losses in rotational direction and axial
direction (Torque and Drag) are divided while drilling with
rotation in the relation of the absolute velocities. Because
while drilling with e.g., 90 RPM and 15 m/h ROP the
velocity in rotational direction is much greater than the
axial velocity. Almost no axial drag is applied while
drilling with rotation. Thus the “Torque” method must be
used.

Note: If the RPM in any operation mode (drilling,

pick up, slack off, rotation of bottom) is
greater than zero then the “Torque” method
must be used.

If you select the automatic option, the program decides

automatically which option must be used.
If the next interval is drilled and the Incremental friction
factor calculation method is used, the last friction factor
which was stored for the last interval is used and a new
friction factor only valid for the just drilled interval is
calculated.
If the Well friction factor method is used, a new friction
factor for the complete well is calculated with every new
data set in the CDA. See Figure 3-154.

.,
"# $!%& '()*
Confidential


 
    

 
-$$)


 ",% -( 

Stress Analysis
The Ontad program performs a complete (torsional,
bending, axial) stress analysis. The only values presented
to you are the Min. Yield and Fatigue Safety factors in the
drillstring.
Yield Safety Factor
The Yield Safety Factor is defined by the ratio of the Yield
Strength (material property specified in the Tubular
Editor) and the Equivalent or Combined Stress. A Yield
Safety Factor of 1.0 essential defines that no stress reserve
is available anymore. A minimum acceptable Yield Safety
Factor is recommended with 1.3. Any accepted value less
than 1.3 requires very careful operation; therefore, a strike
limitation of e.g., WOB would be required when accepting
such a scenario.
Fatigue Safety Factor
The Fatigue Safety Factor calculation is based on the
Endurance Limit provided in the Tubular Editor. The

  ! .,



 
     Confidential

 
-$$)


Fatigue Safety Factor definition is based on the assumption

of 106 rotations. The Endurance Limit provided is defined
as the alternating stress level a tubular can withstand when
rotating 106 times and no fatigue occurs. When rotating 106
times with an alternating stress level equivalent to the
Endurance Level, no fatigue will occur; when rotating
(106 + 1) times with the same stress level, fatigue will
occur. This transition is defined with a Fatigue Safety
Factor of 1.0.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


)  
 &)(


The ReadOpto program is designed to read data from
either the HAZARA or SARA data acquisition system
over the ARCnet. It is designed to read four analog signals
and three digital signals. The analog signals that may be
acquired and stored to the CDA are block separation,
hookload, standpipe pressure, and torque. The digital
signals are block height, motion compensation, and rpm.


At program start-up, an attempt is made to communicate
with the Opto system. Current sensor values (or errors) are
displayed on the main window. See Figure 3-155.

 ",, $ 3



  ! .,.



 
     Confidential

 
-$$)



The communication link to the controller can be
configured by selecting Controller from the Configure
menu. See Figure 3-156.

 ",1 
 

3


This allows you to choose either ARCnet or serial line. For

normal operation the ARCnet should be selected.
Calibration of surface sensors is also accessed from the
Configuration menu. It is separated into analog and digital
sensor calibration. The analog screen is shown in
Figure 3-157.
The available sensors are Block Separation, Hookload,
Pump Pressure, and Torque. All are two point calibrations
that can set automatically or manually entered. The digital
calibration screen is shown Figure 3-158.
Block height and motion compensation count values are
automatically entered by pressing the calibration button on
the block height calibration cable attached to HAZARA or
SARA. The heights corresponding to the count values can

.,/ "# $!%& '()*

Confidential


 
    

 
-$$)


 ",2 -
 
 
3


 ",4  

 
3


  ! .,0



 
     Confidential

 
-$$)


then be manually entered. The RPM value may be adjusted

if it senses more than one count per revolution.
In the event of power loss to HAZARA or SARA, it is
necessary to reset the digital counters. This is
accomplished from the Reset Digital Counters screen
accessed from the Configuration menu as shown in
Figure 3-159.

 ",5   

 3


Simply type in the current block height and the counts will
be adjusted accordingly.

.,1 "# $!%& '()*

Confidential


 
    

 
-$$)


)  
 &)(


The ReadPF program is used to read a serial data stream
from the Pepperl & Fuchs data acquisition system. The
P&F system sends values for block position and hookload
in a continuous WITS Level 0 ASCII stream to one of the
serial ports of the MSS computer. ReadPF reads the serial
port, decodes the data stream and stores the data values
into the Common Data Area (CDA).


At program start-up, the current values for serial port and
parameter configuration are read from the Windows
Registry, the port is opened and decoding of the incoming
data stream commences immediately.
If this is the first time that the program has been run and
there are no current settings, a default configuration is
used.
The main window displays the values for block position
and hookload as they are read from the serial port.
See Figure 3-160.

 "16 !

3
 $

  ! .,



 
     Confidential

 
-$$)



The user-configurable parameters are the serial port and its
settings, target the CDA items, the units in which the
incoming data values are being sent and the units that are
being displayed in the main window.
Choose Properties from the Configure menu. This pops up
a tabbed window. For serial port settings, choose the Serial
Port tab. See Figure 3-161.

 "1  0 3



The port being used for the P&F data stream is selected by
choosing from the drop down list attached to the Port field.
The settings for that port can be changed using drop down
lists attached to the baud rate, data bits, stop bits and parity
fields. The usual settings are 9600 bits per second baud
rate, 8 data bits, 1 stop bit and no parity. The available
serial ports on the system are loaded from a file
(serports.cfg) located in the INTEQ ctl directory. Press
Apply or OK to save the selection.
The data values from the P&F system may be in one of two

., "# $!%& '()*

Confidential


 
    

 
-$$)


units for each of the variables. Block position may be sent

in feet or meters while hookload may be sent in kilo-
pounds or kilograms. It is essential that the program
settings match the units being sent so that proper decoding
can take place. To view or change the data stream unit
settings, choose the Parameters tab. See Figure 3-162.

 "1 0 3



The WITS Item codes are fixed. You can change the
Target CDA Item field by highlighting it and typing in a
new mnemonic. The Source Units field can be changed by
choosing from the Units drop down list. Press Apply or OK
to save the selection.
The main window display units may be changed by
choosing the Units Conversion item from the Configure
menu. This displays the standard units conversion setup
window. You can change the units for block position
(conversion identifier LD) or hookload (conversion
identifier LF) as needed.
The settings are saved in the Windows registry and are
reloaded automatically by the program whenever it starts

  ! .,



 
     Confidential

 
-$$)


up. Setup is not required once the program has been

initially configured. It starts up and automatically opens
the serial port and starts decoding the data stream, placing
the new values into the CDA.
The only way to stop decoding the data stream is to exit the
application.

Note: It is possible to view any decoding errors by

either making the display window bigger (by
dragging from its bottom right corner) or by
hiding the toolbar (View menu). An extra
line becomes visible on the main window
giving a count of errors encountered.
Decoding errors usually means a problem in
the serial line. See Figure 3-163.

 "1" !

3
 (
 & +


.,-

"# $!%& '()*

Confidential


 
    

 
-$$)


)  
/ % &)
(


The ReadSpm program is used to read a serial data stream
from up to two TOTCO™ SPM Gauges. ReadSpm reads
one or two serial ports, decodes the data stream(s) and
stores strokes per minute values for up to four mud pumps
into the Common Data Area (CDA). It can also be
configured to calculate mud flow from the strokes per
minute readings.


At program start-up, the current values for serial ports are
read from the Windows registry, the ports are opened and
decoding of the incoming data stream commences
immediately.
If this is the first time that the program has been run and
there are no current settings, a default configuration is
used.
The main window displays the values for individual pump
strokes per minute as well as a total value. See
Figure 3-164.

  ! .,-




 
     Confidential

 
-$$)


 "1%  0!

For each pump, its current SPM and flow value are shown.
The SPM value comes from the gauge while the flow value
may either be read from the CDA (if “Update CDA
FLOWIN” option is OFF) or calculated by the program
(if “Update CDA FLOWIN” option is ON). The status
following the flow values indicates the current
configuration of the rig pumps as specified in the MSS
setup program. Pumps can be configured to be ON, OFF,
BOOSTER, or UNUSED (not present).



(
The only user-configurable parameters are the serial ports
connected to the TOTCO™ gauges.
To view or change the serial port settings, choose Serial
Ports… from the Configure menu. This displays the
following window as shown in Figure 3-165.

.,-
- "# $!%& '()*
Confidential


 
    

 
-$$)


 "1,  0!.  0

You can specify the serial port connected to one or two

gauges. Each gauge provides strokes per minute data for
up to two pumps. Select a port (or switch to OFF) for each
gauge. The port settings are fixed at 2400 bps baud rate, 8
data bits, 1 stop bit and no parity.
Press OK to save the settings. If the port configuration is
changed the connections to the gauges are closed and then
re-opened according to the new configuration.
The settings are saved in the Windows registry and are
reloaded automatically by the program whenever it starts
up. There is no user setup required once the program has
been initially configured. It starts up and automatically
opens the serial ports and starts decoding the data streams,
placing the new values into the CDA.
The only way to stop decoding the data stream is to switch
the ports to OFF or exit the application.

  ! .,-
.



 
     Confidential

 
-$$)


+*6' 
There is an option for ReadSpm to calculate the mud flow
from pump SPM readings and update the corresponding
CDA item. This option is only available if Online
Hydraulics is not being run in RtProc.
If unavailable, the menu item “Update CDA FLOWIN”.
and its toolbar equivalent, are disabled, in which case the
mud flow values displayed on the main window are read
from the CDA rather than being calculated by ReadSpm.
If the “Update CDA FLOWIN” option is selected,
ReadSpm calculates individual pump flow values as well
as a total flow value and updates the CDA with these
values.

+ 0
It is possible to view any decoding errors by either making
the display window bigger (by dragging from the bottom
right corner) or by hiding the toolbar (View menu). Extra
lines becomes visible on the main window giving a count
of decoding and checksum errors encountered. Decoding
errors usually means a problem in the serial line. See
Figure 3-166.

 "11  0!

.,-
/ "# $!%& '()*
Confidential


 
    

 
-$$)


);/ )    &); (


The RLPlot (RigLink Real Time Plot) program is the real-
time plotting package available with MSS. It utilizes
portions of code developed for RigLink. It actually plots
data from the RigLink Server application. This application
should be run on the offline computer.


At start-up, the following main window is displayed as
shown in Figure 3-167.

 "12 +0 $

Server: Computer running the RigLink Server.

Well: *signifies any well.
Buffer Ref: Depth or Time - References for retrieving
buffered data
Buffer Size: Amount of data in meters or seconds to pull
from the data buffers.
Format File: A file in inteq\res\ctl\rlplot that describes
the plot format.

  ! .,-
0



 
     Confidential

 
-$$)


User Name: A user that has permission to access

the RigLink Server.
See Figure 3-168.

 "14 +0

2!+3>? 4
These files have the extension .rlp and contain three
sections. The top section specifies the total width and
height of display in pixels:
# Application total width and height
#
Width = 800
Height = 750
The second section sets some general parameters for the
appearance of various applets which may be used on the
display. The applets currently available are labels, numeric
values, well activity, steering rose, and log formats.

.,-
1 "# $!%& '()*
Confidential


 
    

 
-$$)


The amount of blank space around the edges of the plot are
specified by:
#
TopPad=5
Left Pad=5
RightPad=5
BottomPad=5
#

!5 
The label applet is for displaying text anywhere on the
canvas. The following gives default values for the
appearance of the text. Any of the default values can be
overwritten by specifying another value when actually
positioning the applet.
#
# Labels
#
LBL_Width=125 Width
LBL_Height=30 Height
LBL_BC=white Background Color
LBL_FC-black Foreground Color
LBL_FontS=9 Font Size
LBL_FontStyle=PLAINFont Style
LBL_Font=Dialog Font Name
LBL_Align=Center Alignment of the text
inside the label
LBL_3D-true Three Dimensional Effect
#

5= 
The number value applet displays a CDA mnemonic and
its value (DEPTH = 10000 ft). The following gives default
values for the appearance of CDA value. Any of the default
values can be overwritten by specifying another value
when actually positioning the applet.

  ! .,-




 
     Confidential

 
-$$)


#
# Num Val control
#
NV_Width=130Width
NV_Height=30Height
NV_BC=whiteBackground Color
NV_FC=blackForeground Color
NV_FontS=9Font Size
NV_Config=trueAllow user to change
mnemonics
NV_PREC=2Numeric precision
NV_ShowMnm=trueDisplay the mnemonic
NV_3D=trueThree Dimensional Effect
NV_FontStyle=PLAINFont Style
NV_Font=DialogFont Name
#

6" 
The well activity applet is for displaying a text string of the
current rig activity based on rig status or WITS status from
the CDA.
#
# Well Activity control
#
#
WA_Width=160
WA_Height=20
WA_File=/inteq/res/ctl/rlplot/
WellActivity.wac
#
The WellActivity.wac is for specifying colors and text
strings for the various activities. The following is an
example entry from this file:
#Well Activity Properties List
#Sat Jul 26 16:21:53 Central Daylight
Time 1997
RIGSTAT=RIGSTAT
WITSSTAT=WITSSTAT
BG=white
FG=black
Font=Helvetica
Fontstyle=BOLD

.,-
 "# $!%& '()*
Confidential


 
    

 
-$$)


3D=yes
FontSize=18
#
WitsVal0=0
WitsString0=Undefined
WitsBG0=gray
WitsFG0=black
#
WitsVal1=1
WitsString1=Rig Up
WitsBG1=white
WitsFG1=black
#

( 2 

The steering rose applet is for placing a steering rose
anywhere on the display.
#
# Steering Rose control
#
#
SR_Width=200
SR_Height=200
SR_File=/inteq/res/ctl/rlplot/
sr_setup.str
#
#
The sr_setup.str specifies the appearance of the steering
rose. Below are the contents of that file.
#Steering Rose Properties List
#
# 3D Flag (true or false)
#
3d=true
#
# Display HTFX and/or MTFX (true or
false)
#
ShowHTFX=true
ShowMTFX=true
#
# No of previous meas to display
#

  ! .,-




 
     Confidential

 
-$$)


HistoryList=5
#
# background and foreground colors
# black, blue, cyan, dark gray, gray,
green,
light Gray, magenta, orange, pink,
red, white, yellow
#
BackgroundColor=white
ForegroundColor=black
#
# Grid Color
# black, blue, cyan, darkGray, gray,
green,
lightGray, magenta, orange, pink, red,
white, yellow
#
GridColor=lightgray
CircleColor=black
#
# Tick Marks (true or false)
#
LongTickMarks=true
#
# HTFX and MTFX Colors
# black, blue, cyan, darkGray, gray,
green,
lightGray, magenta, orange, pink, red,
white, yellow
#
HTFXColor=red
MTFXColor=blue
#
Data to display
#
Mnemonic1=AZNX
Mnemonic2=INNX
Mnemonic3=IMCX
Mnemonic4=HTFX;MTFX
#
# Data units (deg or rad)
#
DisplayUnits=deg
TransUnits=rad
#
# Tick Mark Increment (degrees)

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


#
TickIncrement=30
#
# HTFX symbol
#
HTFXSymbol=Circle
#
# MTFX symbol
#
MTFXSymbol=Rect
#
# Padding to use (determine the size
of the font in
drawing the grid labels)
#
XPad=40
YPad=20
#
# Grid Label Font Size
#
FontSize=14
#
# Font Style (BOLD, ITALIC, PLAIN)
#
FontStyle=BOLD
#
# Font Name (Courier, Dialog,
Helvetica,
TimesRoman,Symbol)
#
Font=Helvetica
#
# HTFX and MTFX Mnemonic names
#
HTFXMnm=HTFX
MTFXMnm=MTFX

  ! .,-



 
     Confidential

 
-$$)


+!  
The formation evaluation log applet places a plot on the
display.
#
# FELog Control
#
#
FE_Width=480
FE_Height=480
#
#
The third section is for actually positioning the various
applets on the canvas.
# Controls to add to the form
#
The following places a number value applet 75 pixels from
the left edge and 80 pixels down from the top which will
display DEPTH from the CDA.
#
NV_X1=75
NV_Y1=80
NV_Mnm1=DEPTH
#
The following positions a well activity applet 320 pixels
from the left edge and 50 pixels down from the top that
displays the well activity.
#
WA_X1=320
WA_Y1=50
#
The following places a steering rose applet 200 x 200 in
size 40 pixels from the left edge and 360 pixels down.
#
SR_X1=40
SR_Y1=360
SR_Width1=200
SR_Height1=200
SR_File1=/inteq/res/ctl/rlplot/

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


sr_setup.str
#
The following places the text string “Test Message
Number 1” 410 pixels from the left edge and 510 pixels
down. It also exhibits how default values are overwritten.
#
LBL_X1=410
LBL_Y1=510
LBL_Msg1=Test Message Number 1
LBL_Width1=300
LBL_Height1=50
LBL_BC1=lightGray
LBL_FC1=red
LBL_FontS1=16
LBL_FontStyle1=BOLD
#
The following places a 480 x 480 plot (dddepth.fmt) 280
pixels from the left edge and 80 pixels down.
#
FE_X1=280
FE_Y1=80
FE_Width1=480
FE_Height1=480
FE_File1=/inteq/res/ctl/rlplot/
dddepth.fmt
#

00

 > 
 > *+, ;.
% >  

  ! .,-.



 
     Confidential

 
-$$)


See Figure 3-169.

 "15 &+ &

A default template will appear. To edit this template,

double-click anywhere on the canvas and a window will
appear as shown in Figure 3-170.

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "26 & &+ 

This window is used for editing Global parameters. The

background, grid, and border colors may be changed to any
of the following. See Figure 3-171.

 "2 

  ! .,-0



 
     Confidential

 
-$$)


Plot Key Type: Choice between Depth or Time

based plot.
Plot Span: Amount of data per page.
Major Grid: Distance between horizontal lines
with data labels.
Minor Grid: Distance between horizontal lines
without data labels.
Pen Up Interval: Data points that are farther apart
than this distance will not be
connected
Data Buffer Size: Maximum number of points to keep
in memory for zoom and scroll.
Allow Reversed Plots:This option allows for plotting off
bottom data.
Font size, name, and style may also be specified.
Selecting a track produces the following in Figure 3-172.

 "2 & &+ 

.,-1 "# $!%& '()*

Confidential


 
    

 
-$$)


Track left and right positions may be specified using

fractional numbers with 0 being the left side of the plot and
1 being the right side of the plot.
Visible: Turns on and off track grids and
borders.
Scale Minimum: Minimum value plotted.
Scale Maximum: Maximum value plotted.
Major Grid: Thick vertical lines.
Minor Grid: Thin vertical lines.
Linear/Log Scale: Selecting whether the scale is linear
or logarithmic.
Normal/Reversed
Scale: Normal increases to right.
Add font, size and style can be used to change the fonts in
that track.
Add Parameter: Adds a parameter to the track which
defaults to ROP
Expanding the track and selecting one of the parameters
produces the window shown in Figure 3-173

  ! .,-



 
     Confidential

 
-$$)


 "2" & &+ 

Data Buffer Name: Not used at this time.

Parameter Mnemonic: Type in a mnemonic or
select the button for a list,
see Figure 3-174.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


 "2% !

) +

The choice box allows for the selection of which type of

data to plot. See Figure 3-175.

 "2, () 9>

Key Mnemonic: Mnemonic to depth tag the data. All

MWD data is handled
automatically.
Title: The text appears in the track
heading. Multiple words should be
joined with an underscore; i.e.,

  ! .,-



 
     Confidential

 
-$$)

Gamma_Ray.
Parameter
Type: Select from the following.
See Figure 3-176.

 "21 0
$

Line
Thickness: Changes line thickness. Larger numbers
are thicker lines.
Color: Select the color of the parameter.
Density
Tics: Specify the location of data density
indicators (see Figure 3-177).

 "22 

)

Fill Type: Allows filling from the parameter to the

baseline (see Figure 3-178).

 "24 
$

.,--
"# $!%& '()*
Confidential


 
    

 
-$$)


Clip to Track: Determines if the data range is

confined to the track or may be
plotted outside the track.
Add Scale: Used to specify an individual
parameter scale.
Add Font: Used to specify an individual
parameter font.
File manipulation is accomplished with the selections at
the bottom of the editing screen. See Figure 3-179.

 "25 &

 )


Load: Loads an existing format.

Save: Saves the current format.
Save As: Renames the current format.

  ! .,--



 
     Confidential

 
-$$)


) +  &)+(


RigDisp is a general purpose display program that reads
data values from the Common Data Area (CDA) and
displays them in a window according to a user-defined
format. RigDisp formats are stored on disk as ASCII-
format .rdf files. A display format may consist of a mixture
of alphanumeric and graphical elements arranged on the
screen according to the users requirements.
When started, the following main window is displayed
(though the format may be different from that shown).
See Figure 3-180.

 "46 0 )  

(  $

The window is made up a several distinct areas:

• The menu bar. All program functions are accessibly
through the menu bar.
• The main display area.
• The status bar where application messages are
displayed

.,--- "# $!%& '()*

Confidential


 
    

 
-$$)


To quit the application, choose Exit from the File menu or

click the close box in the top right of the main window.
The display format loaded at start-up is the last one used
or, if this is the first time that the program is used on a job,
a default format is loaded.

    + 

You can select the format for display in two ways:
• using the Open command from the File menu
• using the List command from the File menu

& 
' 
Choose Open from the File menu to display the standard
file open window shown in Figure 3-181.

 "4 $

The default starting location is rigdisp, a sub-folder of the

INTEQ ctl directory. RigDisp formats are usually stored in
that folder. Select a format, and press the Open button. The
format is loaded and the RigDisp main window changes
accordingly.

  ! .,--.



 
     Confidential

 
-$$)


& 
!
Choose List from the File menu to display the following in
Figure 3-182.

 "4 $. -A 

The window displays a list of formats to choose from. This

list is built from the rigdisp.lst file in the INTEQ
ctl\rigdisp folder.
It is also possible to display the format list by pressing the
F2 key. If this file is not present, the following Warning is
displayed. See Figure 3-183.

 "4" $  ;  + 3




Check the existence of the list file and that it contains valid
format names.
.,--/ "# $!%& '()*
Confidential


 
    

 
-$$)

Note: If the “rigdisp.lst” file is changed, RigDisp
must be restarted to recognize the changes
since the file is only read once at start-up.

 
  )   


A Trace component displays data in a graphical form
rather than alphanumeric. For example, see Figure 3-184.

 "4%
) $


 &>$

Clicking with the left mouse button on a Trace component

displays the window shown in Figure 3-185.

 "4,
) !

 !>

The Trace field is a drop-down list of parameters included

in the Trace. Select the parameter to configure then enter
the required minimum and maximum scale values. Repeat
for other parameters if required, then press OK to save the
changes.

  ! .,--0



 
     Confidential

 
-$$)


%
 #  ;

A Lights component is used to graphically display a piece
of data. Typically the graphic changes depending on the
value of the underlying parameter value. An example
Lights component is shown in Figure 3-186.

 "41 +( $


 &>$

Clicking with the left mouse button on a Lights component

displays information about its settings. See Figure 3-187.

 "42 $. ! +( 3

 * 
The current system units conversions can be viewed/
changed by choosing Units Conversions from the

.,--1 "# $!%& '()*

Confidential


 
    

 
-$$)


Configure menu. See Figure 3-188.

 "44 ) 





Choose the units type to be modified from the list. The

available conversions are shown in the box labeled
“Units”. Choose the conversion you want to use for that
type. Repeat this procedure for other types if required.
Press OK to save the changes.

Note: Changes to the system conversion table are

broadcast to other applications which will
change their displays accordingly if they are
set up to handle the message.

   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

  ! .,--



 
     Confidential

 
-$$)


+ 1);/



The CDAFeed program is used to transfer data from the
MSS Common Data Area (CDA) to one or more RigLink
servers. The RigLink server is used to transfer the data to
applets running on Web pages or to the RLPlot display
application running on MSS.

Note: A program called CDAFeed is also part of

the DrillByte system and is also used to
connect to a RigLink server, also transfer
data back and forth between MSS and
DrillByte Common Data Areas.


When first started, the main window is displayed. If this is
the first time that the program has been run, there will be
no entries in the “RigLink server connections” list. See
Figure 3-189.

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


 "45 -

To specify a new connection, choose Properties… from

the Settings menu (or press the Properties toolbar button).
The following tabbed window is displayed as shown in
Figure 3-190.

  ! .,--



 
     Confidential

 
-$$)


 "56 - 0$

RigLink Servers tab

Enter the Well Name that will be used on RigLink output
screens to identify the data from this well.
Choose Add to add a new server to the list, Edit to edit an
existing entry, or Delete to remove an entry from the list.
If Add or Edit is selected, the following entry screen
appears as shown in Figure 3-191.

 "5 +

*  &


.,-.
"# $!%& '()*
Confidential


 
    

 
-$$)


Enter the IP address of the RigLink server and specify the

amount of buffered data to retransmit in case of a
disconnection. Press OK to save the entry and have it
inserted (or updated) in the server list.
CDA Items tab (see Figure 3-192).

 "5 - 

This page is used to specify which CDA items are sent and
when they are sent. Selecting Add or Edit displays the
following dialog shown in Figure 3-193.

 "5" -  &



  ! .,-.



 
     Confidential

 
-$$)


Specify the required item in the CDA Mnemonic field by

choosing from a drop-down list of all items in the CDA.
Next, specify when to transmit the item. See
Figure 3-194.

 "5% -  &



Data values may be sent on a time and/or depth basis or

when the item is updated (On Update) or changed (On
Changed) in the CDA. Typically surface measurements
will be sent on a time or depth basis and MWD data will be
sent “On Update”. Press OK to insert into (or update) the
list of CDA items on the Properties CDA Items tab.
When the RigLink server(s) and CDA items have been
specified, press OK to dismiss the Properties window.
The new server connection should be displayed in the list.
See Figure 3-195.

.,-.- "# $!%& '()*

Confidential


 
    

 
-$$)


 "5, -

);/

The RigLink Server can be run on a computer running
either Windows NT or Windows 95. It is, however,
recommended that it be run as a “service” on Windows-NT
when providing RigLink to clients. The RigLink Server is
also used to provide real time plots at the wellsite and it can
be run from the start menu.

  
  *+, ;.
% 
;.
%
This will display the following window shown in
Figure 3-196.

  ! .,-..



 
     Confidential

 
-$$)


 "51 +

* 

The RigLink Properties window is used primarily to make

sure the Root Directory and the Web Directory paths are
correct, and to set buffer sizes. To access the RigLink
Properties window, select Properties from the Misc. menu.
See Figure 3-197.

.,-./ "# $!%& '()*

Confidential


 
    

 
-$$)


 "52 +

* 0$

Table 3-1 RigLink Properties

Field Description

Root Directory Shows the directory where the

RigLink server is installed
Web Directory Shows the directory where the
Web Server is installed
Bin Directory Non-editable field
CTL Directory Non-editable field
Image Directory Non-editable field

  ! .,-.0



 
     Confidential

 
-$$)


Table 3-1 RigLink Properties

Field Description

Buffer Size Show how many messages get

saved into memory before
being saved to hard disk. 1000
is the recommended setting
Trans Size Shows the size of the chunk of
data that comes in at one time.
1000 is the recommended
setting
Garbage Collect Every Non-editable field
Ignored Buffered Data Filters out unwanted incoming
Starting With data
Ignored Buffered Data Ending Filters out unwanted incoming
With data
Ignored Buffered Data Filters out unwanted incoming
Mnemonics data

.,-.1 "# $!%& '()*

Confidential


 
    

 
-$$)


4

+  &4

(


WITS is an application that is used to perform data
transfer between two or more computer systems, using the
WITS transmission format. This initial version of WITS
permits sending and receiving at WITS Level 0 (ASCII)
and Level 1 (binary). Up to four serial ports may be used
for simultaneous communications. It is also possible to
send data between two WITS programs via the Message
Server.
At start-up, the following main window is displayed. See
Figure 3-198.

 "54 3
!

3
 7 !8

The main window consists of a series of menus with

associated toolbar, a control area which contains a list of
available WITS ports and a means of choosing between a
Data and a Summary display, and an area for displaying
the data or summary information.

  ! .,-.



 
     Confidential

 
-$$)

At the base of the main window is a status bar with two
indicators. The left indicator (XFER) turns green when you
have started data transfer. Otherwise it is red. The right
indicator (ERR) turns red when an error message has been
written to the error log file. The left side of the status bar is
used for application messages. See Figure 3-199.

 "55 3
!

3
 7  !8



Choose Properties for the Settings dialog menu to display.
The Properties tabbed window consisting of: Global, Port,
and Record tabs.

85 
This page is used to set up information common to all
ports. See Figure 3-200.

.,-. "# $!%& '()*

Confidential


 
    

 
-$$)


 "66 3
: 0

Well ID is a unique string identifying the current well. It

must be no more than 12 characters long.
Sidetrack No. identifies the current sidetrack hole number
for the well.
Local ID is a unique number used to identify a WITS
computer in a network of computers. This number is
normally assigned by a Data Center to identify data
coming from different rigs.
The Data Center is normally 0 by default. Use a value of
9999 unless otherwise directed.
Units identifies the system of units that the data are
transmitted in, either FPS, or Metric.

  ! .,-.



 
     Confidential

 
-$$)


The system of units must not be changed once transmission

is underway.
Automatic transfer check box is used to specify if transfer
to enabled ports should begin automatically at program
start-up rather than waiting for you to manually start
transmissions.

 
This page is used to create WITS ports for transmission and
specify properties specific to each port, such as
communications parameters. See Figure 3-201.

 "6 

)
 0$

The first two ports (Ports 0 and 1) are displayed. Other

ports can be accessed using the horizontal scroll bar. Each

.,-/
"# $!%& '()*
Confidential


 
    

 
-$$)


port can be configured with the following parameters:

Description is a string used to identify the port.
On/Off allows you to enable/disable a port. No
transmission/reception of data occurs on a disabled port.
Mode determines if a port is a Sender, a Receiver, or Both.
Level determines the WITS Level that the port recognizes.
Currently, this may be Level 0 (ASCII) or Level 1
(Binary).
Store To CDA specifies whether to store incoming data to
the CDA.
Store To Database specifies whether to store incoming
data to the Database (Level 1 only).
Hole identifies the hole for database storage/retrieval.
Remote ID is the identifier of the remote system
(i.e., matches the Local ID of the remote system).
Master Remote indicates whether the Remote ID
indicated in the field above is the master remote computer.
This is for use in Level 2 and above and when transmission
is occurring to multiple receivers. Since only one of those
is allowed to control the triggering rates, etc., that receiver
has to be identified to the program. (Not Currently Used).
Phone is the phone number of the remote system
(Not Currently Used).
Inter Record Interval is the minimum time (in seconds)
to wait between transmitted records. This is normally 0
(no wait between records).
HI Interval specifies how often to send HI messages to the
remote system at Level 2 and above. (Not Currently Used).
Two buttons at the base of the window allow you to setup
up the communication port parameters (COMM CONFIG)
and triggering information for Level 0 transmissions
(TRIGGERS).

  ! .,-/



 
     Confidential

 
-$$)


See the Communications Configuration and Trigger

Configuration sections below for more information.

 

You can choose the port to be used for transmission as well
as the communications settings for that port. See
Figure 3-202.

 "6  



The port may be a serial (COM) port, in which case the

Baud Rate, Data Bits, Stop Bits, and Parity must be set, or
MsgSvr, in which case these parameters are not used and
the controls are disabled. See Figure 3-203.

.,-/- "# $!%& '()*

Confidential


 
    

 
-$$)


 "6"  



Note: If MsgSvr is selected, data are transmitted

in the form of messages to the MsgSvr where
they are routed to any other WITS program
that has registered interest in such
messages. In this way it is possible to
transmit WITS data via the network rather
using traditional serial connections.

 
This allows you to specify up to three trigger parameters
and intervals for each WITS record. These triggers are
only used to determine triggering intervals for Level 0
transmissions. (Level 1 transmissions occur when WITS
records are written to the database by Dlogger).
Pressing the TRIGGERS… button on the Ports setup
window displays the following Port Record Configuration
window. See Figure 3-204.

  ! .,-/.



 
     Confidential

 
-$$)


 "6%
 



Columns 1 and 2 of the table identify the WITS record

number and description. There are three pairs of columns,
a pair for each possible trigger - time, depth and event.
Only the time trigger is initially displayed. Use the
horizontal scrollbar to access the other triggers.
Only records with triggers are transmitted. To remove a
trigger from a record, clear the trigger mnemonic and
value. Clearing all triggers for a record stops if from being
transmitted even if Enabled in the Port Configuration.
To choose a Trigger mnemonic, simply type it into the field
or right click on the field to display the CDA Source
selection window. See Figure 3-205.

.,-// "# $!%& '()*

Confidential


 
    

 
-$$)


 "6, - )

Select the CDA item to be used as the trigger and press

OK. You can sort the list according to position in the CDA
or name by pressing the buttons at the top of the window.

) 
This property window is used to specify whether a record
is ON (available for sending or receiving) and to specify
record item configuration, i.e., source CDA items for
“sender” ports and target CDA items for “receiver” ports.
For a “sender” port, CDA items are only applicable for
Level 0 transmissions. For a “receiver” port they are valid
for all levels.
When the Records tab is selected, the following property
page is displayed. See Figure 3-206.

  ! .,-/0



 
     Confidential

 
-$$)


 "61 

)
 0$

In the RECORDS section you can turn a record ON or OFF

by checking the box next to its name. If a record is OFF it
will not be sent at any level and will be ignored if received.
In the ITEMS section, you assign a CDA item to WITS
Record Items for the currently selected Record (in the
RECORDS section).

Note: This configuration is only valid for WITS

records that are generated automatically (as
opposed to manually by you). The records
that are valid for CDA assignment are: 1,
2,3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17 and
18, as well as records 50 through 80 (special

.,-/1 "# $!%& '()*

Confidential


 
    

 
-$$)


INTEQ MWD records that are not part of

the WITS standard and only used when the
sending and receiving party have agreed on
their use).

To assign a CDA mnemonic, simply type it in or right click

in the field to pop up the CDA Source selection window
(see Trigger Configuration section).

 * 
 4


1. Set up the Global properties (with values supplied by
the Data Center) or using defaults.
2. Select the Ports tab and fill in the configuration for
Port 0. If other ports are to be used, scroll
horizontally (if necessary) to display the required
port columns and fill in those too. Up to four ports
can be configured. For each WITS port, press the
Comm Config… button to specify the
communications port parameters for that WITS port.
For Level 0 ports with a mode of Sender or Both,
press the Triggers… button and specify the
transmission triggers of required records.
3. Select the Records tab and turn ON the required
Record types. If a Level 0 sender, or a receiver at any
level where storage to the CDA is required, assign
CDA mnemonics to WITS Items as required.
4. Choose Save Configuration from the Configure
menu to store the new configuration to disk.
5. When ready, choose Transfer Data from the Transfer
Menu.
After a short delay the XFER status bar indicator
should turn green.
6. If an error occurs the ERR status indicator turn red.
The error log can be view by choosing the Error Log
menu item from the View menu or pressing the Error
Log toolbar button.

  ! .,-/



 
     Confidential

 
-$$)


0 4


1. To stop communications on a specific port, make it
Disabled in the Port Configuration window. This
immediately changes the ports status. You can also
stop a record from transmitting at Level 0 by
removing its triggers or setting them to 0. Save
configuration if desired so that the port is disabled
when the program is restarted.
2. To stop all communication, choose Transfer Data
again from the Transfer Menu.
The XFER status bar indicator should turn red.

07   

Level 0 Sender (see Figure 3-207)

 "62 3
 

)
 7+ 6 

$

A port set up to send at Level 0 gets its data from the CDA

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)

based on the Record/Item setup (from the Records
property page). If a WITS item does not have a CDA
source, it is not sent. Only records specified as ON are sent.
The triggering interval for each record is specified using
the Triggers configuration dialog available from the Port
setup property sheet.
On the main window, select the Port for display from the
drop down list. Only the Data type display is available at
Level 0.
The data display consists of three columns of information.
The first column contains the ASCII string sent by the
program. This consists of a four digit identifier followed
by the data value. The second column displays the CDA
source for the WITS item. The third column shows the data
value alone.
Level 0 Receiver (see Figure 3-208)

 "64 3
 

)
 7+ 6 )
$8

A port set up to receive at Level 0 decodes an ASCII data

  ! .,-/



 
     Confidential

 
-$$)

stream and stores the data values to the CDA based on the
Record/Item setup (from the Records property sheet). If a
WITS item does not have a CDA target, it is not stored.
Only items in records specified as ON are stored.
On the main window, select the Port for display from the
drop down list. Only the Data type display is available at
Level 0.
The data display consists of three columns of information.
The first column contains the ASCII string sent by the
program. This consists of a four digit identifier followed by
the data value. The second column displays the CDA target
for the WITS item. The third column shows the data value
alone.
Data sets are separated on the display by a dashed line.
Level 1 Receiver (see Figure 3-209)

 "65 3
 

)
 7+  )
$ 78

A port set up to receive at Level 1 decodes a binary data

stream from the serial port. The decoded data values can be

.,-0
"# $!%& '()*
Confidential


 
    

 
-$$)


stored into the CDA, the Database, or both. The CDA

target items are specified in the Record/Item setup (from
the Records property sheet). If a WITS item does not have
a CDA target, it is not stored to the CDA. Only records
specified as ON are fully decoded. If data is stored to the
database, Record 1 data is stored to WITS_01 table,
Record 2 data is stored to WITS_02 table, etc.
On the main window, select the Port for display from the
drop down list. Both the Data and Summary type displays
are available.
The Data display consists of two header lines for each
record received, followed by the remaining record data
displayed in three columns. The first header line displays
the Record Identifier, the Record Sequence Identifier
(SQID), the overall sequence identifier (PRTSN) and the
Record Date and Time. The second header line displays
the rig status at the time the record was produced. The Data
lines consist of Mnemonic/Value pairs.
Summary Display (see Figure 3-210).

  ! .,-0



 
     Confidential

 
-$$)


 "6 3
 

)
7+  )
$ 78

When the Summary type display is selected, the following

additional screen objects are activated:
Activity: The current rig activity (from the latest record
received).
Last PRTSN: The Physical Record Trailer Sequence
Number (overall sequence number) from the last received
record.
Last Receive Time: The time in the last record received.
The Summary display consists of four columns of
information. The first column is the WITS Record number.
The second column is the WITS Record Description. The
third column contains the sequence number from the last
received record of that type. The fourth column contains
the date and time of the last record received of that type.

.,-0- "# $!%& '()*

Confidential


 
    

 
-$$)


# 4+  & $ (


MOBM is an application that reads data from the Common
Data Area (CDA) and transmits them in a Mobil-
proprietary ASCII format to the Mobil Drilling Operations
Center (DOC).
At start-up, the following main window is displayed as
shown in Figure 3-211.

 " ! !3  

)


This window displays the data required for Mobil MWD

data transmission. At the top of the window, current time
and rig activity are displayed. To the left of the status is a
field named Well ID which displays the identifier for the
site. This number is assigned by the DOC. To the right of
the time field is the Current Time Interval field which
displays the current time triggering interval. While this
interval has a default value at start-up, it is generally
controlled remotely by the DOC through messages sent to

  ! .,-0.



 
     Confidential

 
-$$)


the program via the communications link. This allows the

DOC operator to increase or decrease the frequency of
transmission depending on the drilling situation.
The middle part of the screen displays five groupings of
data items. These groupings correspond to the five “data
lines” making up the Mobil MWD data format. It should be
noted that, while these fields represent the data items used
in the transmission, they do not necessarily exactly match
values read from the CDA, due to averaging, etc.
Additionally, they may not match exactly what is sent to
the DOC because the program overrides invalid data, etc.
prior to transmission. These fields should only be used for
monitoring the data items. The actual data sent to the DOC
may be viewed in the Last Data Packet pop up window, or
historically in a window displaying the data file, updated at
each transmission.
At the base of the window is an area for messages,
specifically the date/time of the last transmission and the
last message received from the DOC. All messages to and
from the program are written to the message file and can be
viewed in a pop up window.
Three indicator boxes are located at the right end of the
status bar at the base of the window.
The left hand indicator displays the word XFER and is
GREEN when transmission has been started, or RED if
transmission has not yet been started (or has been stopped).
The middle indicator displays the word LINK and is
GREEN if the program believes that the communications
link is good (based on periodic messages being sent from
the DOC), or RED if it appears that the link has been lost.
The right hand indicator displays the word ERR and is
GREEN when no errors have occurred (and been written to
the system Error Log) by this program. Viewing the Error
Log will reset the indicator and turn it back to GREEN.

.,-0/ "# $!%& '()*

Confidential


 
    

 
-$$)



Choose Properties from the Settings menu to display a
tabbed window that allows you to change the programs
configuration.

Note: Changes to the configuration can only be

performed when transmission has been
stopped. The new settings take effect when
the transmission is restarted.


Selecting this tab displays the following entry window for
specification of transmission-related parameters.
See Figure 3-212.

 " 

0$

Well ID: is the site identifier specified by the DOC. It is an

integer number between 1 and 999.
Depth Interval: is the depth triggering interval expressed

  ! .,-00



 
     Confidential

 
-$$)


in feet. Its default is 1 and should not be changed unless

requested by the DOC. Transmissions are made when the
measured depth of the hole advances by this amount.
Short Time Interval: is a time triggering interval for
transmissions to the DOC. This is 60 seconds by default.
Long Time Interval: is a time triggering interval for
transmissions to the DOC. This 300 seconds by default.

Note: The actual current time interval used

depends on a number of factors including
rig activity. The DOC can change the actual
time triggering interval remotely. The short
and long time triggering intervals are used
as “fallback” or default values.

Maximum Wait: is the maximum amount of time (in

seconds) that the application waits for a “I Am Here”
message from the DOC before deciding that the
communications line is down and issuing a message to you.
Data File Name: is the name of the file on disk where
copies of the transmitted data are written. This file is in the
c:\inteq\res\data\mobm directory. Changing the file name
will start a new file on disk, leaving the old one available
for viewing, archiving, etc. The DOC requires that data that
were not transmitted (perhaps because the communications
line was down) be available for forwarding to the DOC
when requested.
Message File Name: is the name of the file on disk where
copies of the messages to and from the program are written.
This file is in the INTEQ\data\mobm directory. Changing
the file name will start a new file on disk, leaving the old
one available for viewing, archiving, etc.
The Automatic transfer checkbox that allows you to
specify if transfer should begin automatically at program
start-up rather than waiting for you to manually start
transmission.

.,-01 "# $!%& '()*

Confidential


 
    

 
-$$)


Note: Configuration changes are only saved to

disk when Save is selected from the Settings
menu.

(6
Selecting this tab displays the following window used to
view and/or modify the assignment of the source CDA
Items with Mobil transmission format items. See
Figure 3-213.

 "" 

0$

Pressing the “Use Default Set” button causes the table to

be updated to a set of default pairings.
You cannot modify the first column but can change the
CDA Source Item for any of the Mobil items in the table.

Note: The configuration changes are only saved to

disk when Save is selected from the Settings
menu.

  ! .,-0



 
     Confidential

 
-$$)


(
Selecting this tab displays the following window which is
used to view and/or modify the configuration of the
communications serial port. See Figure 3-214.

 "% 

0$

The serial port names available in the Port list are read from
the control file serports.cfg in the INTEQ ctl folder. The
initial parameters associated with each port are also read
from this file. Changes made to the settings are not saved
back to that file but are saved to the Registry when Save
Configuration is chosen from the Settings menu.

.,-0 "# $!%& '()*

Confidential


 
    

 
-$$)


   #

+
Exit
Exit the program.


Transfer Data
Starts and stops transmission to the Mobil Drilling
Operations Center.

( 
Properties...
Set up Transmission, CDA Source, and Serial Port
properties.
Load
Loads the current configuration from disk. The
transmission and serial port configuration information is
stored in the Windows Registry while the CDA Source
configuration is stored in the file mobmcda.cfg in the
INTEQ\ctl\mobm directory.
Save
Saves the current configuration to disk. The transmission
and serial port configuration information is stored in the
Windows Registry while the CDA Source configuration is
stored in the file mobmcda.cfg in the INTEQ\ctl\mobm
directory.

  ! .,-0



 
     Confidential

 
-$$)


=*
Last Data Packet
Pops up a window displaying the last data packet
transmitted to the DOC and/or written to the data file.
Data File
Pops up a window displaying the contents of the
transmitted data file (in INTEQ\data\mobm).
Message File
Pops up a window displaying the contents of the
transmitted message file (in INTEQ\data\mobm).
Error Log
Pops up a window displaying the Error Log file (Error.log
in $RES_HOME\ctl).
Toolbar
Display or hide the program toolbar.
Status Bar
Display/hide the program status bar.

 
Help Topics
Access Windows Help about the program.
About Mobm
Displays version information about the program.
Context Sensitive Help
An extra toolbar button is used for context sensitive help.
Click on this button and the cursor changes into a question
mark. Click on the screen item that you require help about
and the Help window opens up with the information about
that item. The cursor then changes back to its regular form.

.,-1
"# $!%& '()*
Confidential


 
    

 
-$$)


Operation
Transmission is started/stopped using the Transfer Data
from the Transfer menu.

:

!6
This displays a window containing the last transmitted data
packet. See Figure 3-215.

 ", +  0)* $

This window is updated automatically as packets are

generated and transmitted to the DOC and/or written to the
data file. There is a 5 second loop checking the data,
however, and therefore there may be a small lag between
the generation of the packet and its display in this window.

+
This displays the contents of the transmitted data file.
See Figure 3-216.
This serves as a historical record of data transmissions.
There is no automatic update of the display as new packets
are generated. Pressing Refresh updates the window to
reflect the current status of the file. Pressing Close
removes the window from the screen.

 +
This displays the contents of the message file.

  ! .,-1



 
     Confidential

 
-$$)


 "1 !3   +



See Figure 3-217.

 "2 !3 !  +



Messages sent from the DOC, as well as messages

generated by the program, are appended to this file. DOC
messages are in blue, all others are in black. There is no
automatic update of the display as new packets are

.,-1- "# $!%& '()*

Confidential


 
    

 
-$$)


generated. Pressing “Refresh” updates the window to

reflect the current status of the file. Pressing Close
removes the window from the screen.

  ! .,-1.



 
     Confidential

 
-$$)


+# 0 &+#0(


DbEdit is the database editing program. It can be used to
edit an individual database record or to perform mass
changes to a database table.
The program is used to:
• modify individual attribute values of a database
record
• adjust the depth-time relationship and apply the
changes to multiple tables
• perform a mass “delete/undelete” of database
records
• perform a mass change of record identifiers
• recalculate MWD data following changes in
correction data
• reprocess MWD data from the raw source
• write out files for use by DSeries in plotting and
processing memory data
When started, the following main window is displayed. See
Figure 3-218.
The window is made up of several distinct areas:
A The menu bar. All program functions are accessible
through the menu bar
B The toolbar. The buttons are shortcuts to menu
items. Hold the cursor over a button momentarily to
get a brief description
C The selected well/hole for editing
D The Data Type (MWD, AutoTrak, Surface, or
Param)
E The table (record type) name to edit

.,-1/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "4  &

 !
3


F The range selector for loading data for the currently

selected table
G Block Attribute Value. Only enabled when a block
of attribute values is selected in the spreadsheet
H Action controls (Load, Save, Insert records, change
“Delete/Undelete” Status of records)
I Spreadsheet table into which data records are loaded
for editing
J Status bar where application messages are displayed
To quit the application, choose Exit from the File menu or
click the close box in the top right of the main window. A
Warning box is displayed to ask if you really intend to quit
the application.

  ! .,-10



 
     Confidential

 
-$$)



 )$
0  # 
Several pieces of information are required before loading
data for record-based editing:
• the well/hole
• the database table
• the table attributes
• the range of data
1. Select the Well/Hole
This is done by choosing the appropriate well/hole
combination from the drop-down list at the top of the
screen.
2. Select the table (record type) to be configured.
First choose the type of database table using the Data
Type selector. The list of available tables in the
Table selector changes according to the Type
selected. In the case of AutoTrak, Surface and Param
types, the Table list contains actual database table
names. The MWD type is different in that all data is
in the MWD_GENERIC table and the Table list
actually contains a Sensor-type breakdown.
3. Select the attributes for loading.
This can be skipped if you want to load all the
attributes of a table. However, to only load a subset
of table attributes, press the A button to the right of
the Table choice box. This pops up a window
containing a list of attributes for the table.
See Figure 3-219.

.,-11 "# $!%& '()*

Confidential


 
    

 
-$$)


 "5 &. - $

You can select which attributes you want to load

from the list by clicking and highlighting them.
Click again to deselect an attribute. The buttons at
the top of the list can be used to quickly select or
deselect all attributes. When you have selected the
attributes you want to load, press OK to dismiss the
window.

Note: Key attributes that are not selected will still

be loaded since they are required to be able
to save the records back to the database.

The attribute configuration can be saved to a file in

the INTEQ ctl folder. Choose Table Attributes,

  ! .,-1



 
     Confidential

 
-$$)


Save from the Options menu to display the standard

file save dialog. See Figure 3-220.

 "6  -

DbEdit uses the .des extension to identify attribute

setup files. You can use the default.des file or enter
a new name (there is no need to add the .res
extension when you enter a new name). Press Save
to save the file to disk. You can reload an attribute
setup file from disk using the Table Attributes,
Load command from the Options menu.
4. Choose the range of data to load.
Choose one of the key items (depth, time, or run) and
then enter the “from” and “to” values to set the
range.

Note: The Run choice is only available for MWD

data type.

5. Load the data.

Press the Load button to load in data records from the
selected table for the chosen range. The data records

.,-1 "# $!%& '()*

Confidential


 
    

 
-$$)


are inserted into the spreadsheet.

See Figure 3-221.

 " & $(

A color scheme is used for “real-time data” type

records, based on the act_code (activity code) field.
Default colors are:
Black Drilling
Red Reaming, Circulating
Cyan In Slips
Green Off Bottom
Blue Tripping
Gray Other
The units displayed in the spreadsheet can be
modified by choosing Units Conversions from the
Options menu.

  ! .,-1



 
     Confidential

 
-$$)


Note: A change made to a units conversion will

also be reflected in any other application
displaying that type of conversion.

 " 1 
( 

Right-clicking on the spreadsheet displays a menu from
which you can choose to copy or print the currently
selected block of cells. If Copy is selected, the cell contents
are copied to the Windows clipboard, from which they can
be pasted into another application (for example, Excel or
Notepad).

0 # : 

=
Edit an attribute's value by selecting a cell and typing in the
new value.

Note: If an attribute value is changed, the

“edit_flag” attribute value, if applicable, is
incremented to note the fact that an edit has
taken place. The first edit changes the value
from 0 to 2. The increment is by one
thereafter.

6=
If you select a block of cells in the same column, the Block
Attr Value box in the top part of the window becomes
enabled. You can type a value into the box and this replaces
the values in all the cells of the selected block when focus
leaves the box (mouse click on another part of the window
or tabbing out of the control).
Alternatively, if you place one of four “operator”
characters before the number in the Block Attr Value box,
DbEdit performs a calculation on each cell in the selected
block:

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


+: add the entered number to cell’s value

-: subtract the entered number from the cell
value
*: multiply the entered number and the cell’s
value
/: divide the cell’s value by the entered
number

65
Key attributes of a record are protected from editing by
making the column read-only. This applies to most
attributes ending with “_id” since they usually represent an
identifier. If you double-click on a cell and the value does
not become highlighted for editing, you know that it is a
protected attribute.

= 
 + 

It is possible to adjust the display of the columns in the
spreadsheet in several ways:
Adjust column widths manually
Move the cursor over the divider between columns in the
spreadsheet header. It changes its appearance and allows
you to drag the divider to the left or right, changing the
column width.
Minimize column widths automatically
Select a column by clicking in its header (or select several
columns by clicking a dragging) then choose Column
Widths from the Options menu. This shrinks the width of
the selected column(s) to a minimum. Re-selecting a
minimized column and using the command a second time
returns it to its original width.
Freeze columns
When there are more attributes loaded than can fit on the
visible portion of the spreadsheet, a horizontal scrollbar
allows you to scroll the sheet to see them. If you want to
  ! .,-



 
     Confidential

 
-$$)


keep some left-hand columns on the screen (for example

depth or time) for reference, you can freeze them in place
so that they are not scrolled. To do this, select the right-
most column you want to remain visible and select Freeze
Columns from the Options menu. To “un-freeze”
columns, choose the command again. If columns are
currently frozen, a check mark appears next to the menu
item and the equivalent toolbar button is depressed.
Clear the spreadsheet
You can quickly clear the whole spreadsheet by choosing
Clear Sheet from the Options menu.

  + 1* 
 

)
The record status of most real time database records is
stored in the “edit_flag” attribute. This value is 0 for a
newly added record. Any edits to the record cause the
edit_flag value to be incremented. If the record is marked
as “deleted”, its edit_flag value is set to negative That is,
the record is not really deleted, just marked as such. It is
therefore possible to reverse the deletion by changing the
edit_flag back to a positive value.
Changing the status of an individual record, or group of
records, is done by selecting the record(s) and pressing the
Status button above the spreadsheet. This pops up the
Record Status window as shown in Figure 3-222.

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


 " &. ) 

The From and To fields show the rows from the

spreadsheet that will be affected by the change. You can
change these if you want. Press ALL to select all the rows
in the spreadsheet.
Below the From and To boxes you can choose the action to
perform on those rows. The default choice is based on the
edit_flag status of the first record in the block. If it is
already deleted, then Undelete Rows is selected. If it is not
deleted, then Delete Rows is selected. Of course, you can
change this if you wish.
Press OK to start the process and dismiss the window. The
edit_flag column of the selected rows will have been
updated with the new status.

Note: The deleted status of a record with edit_flag

0 becomes -1. If it is then undeleted it
becomes 0 again, not 1.

  )
You can insert a new record (or number of records) by

  ! .,-.



 
     Confidential

 
-$$)


pressing the Insert button above the spreadsheet.

However, records can only be inserted into a table if you
have already loaded records for that table with all
attributes selected. If only a subset of attributes are
selected and loaded, the Insert button remains disabled.
After loading records for a table, press Insert to display the
window shown in Figure 3-223.

 "" &. 

 )

Enter how many records you want to insert, then specify

the starting and ending Time and Depth for the new
records. The program will interpolate within the specified
range to arrive at a time and depth for each record. Press
Apply to do this interpolation. The small spreadsheet is
populated with the results. See Figure 3-224.

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)


 "% &. 

 )

If everything looks OK, press Insert to place the new

records into the main window's spreadsheet. They are
added below the currently selected row, or at the end of the
records if no row is currently selected.

 
In addition to the editing of individual database records,
the DbEdit program can be used to perform large-scale
changes to the database, including a complete re-process of
pulsed MWD data.
These operations can be accessed from the Special menu
and include:
• Time-Depth Adjust
• Mass Delete/Undelete
• Mass Identifier Change

  ! .,-0



 
     Confidential

 
-$$)


• Reprocess MWD Data

• Recalculate MWD Data
• Write DSeries Files

 
@
The key database table for keeping time-depth
relationships is MWD_TIME. Records are written to this
table by the Depth Tracking process of RtProc at a rate of
once every 15 seconds. The contents of this table are
written to the DSeries “spool” file for use in depth-tagging
the tool memory data. It is therefore essential that this
relationship be as accurate as possible. Sometimes it
becomes necessary to correct the depths for a specific
range of times. This action makes that simple to do and, at
the same time, allows the automatic update of other
database tables with the corrected depths.
When this action is selected the following window is
displayed as shown in Figure 3-225.

 ", &. $( -B



Enter the starting and ending time for the range to be

edited. The original start and end depths from
.,-1 "# $!%& '()*
Confidential


 
    

 
-$$)


MWD_TIME are read from the database and displayed in

read-only boxes below the times.
The correction can be either a straight shift or may involve
some stretching or squeezing of depths in the range. You
can specify that the depths in other tables be corrected by
selecting which tables to update and checking the
appropriate box.
For a straight shift, check the Shift Only box and enter in
the amount to shift (a negative value is valid). When Apply
is pressed, all depths within the specified time range are
adjusted up or down depending on the shift amount.
For stretching/squeezing, enter the correct start and end
depths for the time range and press Apply. The program
computes the new depths for the intermediate records in
the range, based on the starting and ending points and the
number of records in the range.
The cursor changes to an hourglass shape while processing
is taking place and the window is made “busy”. When the
processing is complete, the cursor resumes its normal
shape. Press Done to dismiss the window.

:&
The deleted/undeleted status of database real time records
depends on the “edit_flag” attribute. If the value of
edit_flag is 0, the record has not been edited since it was
inserted into the database. Any edits on the record
increment the edit_flag value by 1 (except for the first edit
which sets the edit flag to 2). Deleted or undeleted status is
indicated by the “sign” of the edit_flag value. A positive
value indicates undeleted while a negative value indicates
deleted. Since a “deleted” record is simply marked and is
never really removed from the database it is quite simple
to “undelete” it again by adjusting the edit_flag value.
The rules for deleting are:
• If the edit-flag value is 0, deleting makes it -1

  ! .,-



 
     Confidential

 
-$$)


• If the edit flag value is 2, 3, 4, etc., deleting makes it

-2, -3, -4, etc.
• If the edit flag is negative, deleting has no affect.
The rules for undeleting are:
• If the edit-flag value is 0 or greater, undeleting has
no effect.
• If the edit flag value is -2, -3, -4, etc., undeleting
makes it 2, 3, 4, etc.
• If the edit flag is -1, undeleting makes it 0.
To perform a mass delete/undelete, choose Mass Delete/
Undelete from the Special menu to display the window
shown in Figure 3-226.

 "1 ! ?#



Specify the time range over which the change should be

applied. The corresponding depths for these times are read
from the database and displayed.
Choose which database tables should be affected by the
change.
Press Delete or Undelete to start processing.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


The cursor changes to an hourglass shape while processing

is taking place and the window is made “busy”. When the
processing is complete, the cursor resumes its normal
shape. Press Done to dismiss the window.


 354
You can make mass changes to certain identifiers within
MWD records. These are Tool Run Number, Relog
Number and Activity Code.
To perform this action, choose Mass Identifier Change
from the Special menu. The following window is
displayed in Figure 3-227.

 "2 ! 

 (


Choose which Identifier to change from the three radio

buttons and enter the correct value to be inserted into
database records for the range specified in the Start Time
and End Time boxes. The corresponding start and end
depths are read from the database and displayed. Also
specify which tables should be updated with the change.
Press Apply to start processing. The cursor changes to an
  ! .,-



 
     Confidential

 
-$$)


hourglass shape while processing is taking place and the

window is made “busy”. When the processing is complete,
the cursor resumes its normal shape. Press Done to dismiss
the window.

2 6
This involves reading in the records from
MWD_RAW_GENERIC as if they are being re-
transmitted by the tool and performing full processing
using current calibration information. This is needed if
sensor offsets have changed in the calibration file.

Note: Recalculate MWD can be used if sensor

offsets have not changed.

When you choose Reprocess MWD from the Special

menu, the standard file open dialog is displayed so that you
can choose the correct mss2.fil calibration file.
See Figure 3-228.

 "4 $

Navigate to the correct mss2.fil, and press Open. The path

to the file is copied to the window shown in Figure 3-229.

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


 "5 &. !3 $)

The text fields are read-only. A Browse button returns you

to the file open dialog if the file name or run number is
incorrect.
Press Reprocess. The cursor changes to an hourglass shape
while processing is taking place and the window is made
“busy”. A progress box gives an indication of the status of
processing. When complete, the cursor resumes its normal
shape. Press Done to dismiss the window.

266
It is possible to recalculate corrected MWD data in the
MWD_GENERIC table when updated calibration
information is made available.

Note: If sensor offset changes are involved, you

must run the Reprocess MWD command to
reprocess MWD data from the
MWD_RAW_GENERIC table and replace
the data in MWD_GENERIC. This is
because the Recalculate MWD action makes
no changes to the depths in the records.

  ! .,-



 
     Confidential

 
-$$)


When you choose Recalculate MWD from the Special

menu the following window is displayed in Figure 3-230.

 ""6 &. )) !3 

Enter or browse for the correct mss2.fil calibration file.

Enter the starting and ending time range for the
recalculation. The corresponding depths are loaded from
the database and displayed. Select the MWD sensor type(s)
to be recalculated.
Press Recalculate. The cursor changes to an hourglass
shape while processing is taking place and the window is
made “busy”. When the processing is complete, the cursor
resumes its normal shape. Press Done to dismiss the
window.

(+
DbEdit is able to write out three files to the INTEQ hputil
folder for use by DSeries programs. These are the spool
(time-depth), tvddata (survey) and binary (mwd and
surface data) files.
Choose Write DSeries Files from the Special menu. The
first time that the program is run the following window is

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)

displayed to specify the location of the HPUTIL folder.
Enter a new path if it is incorrect. You can check the “Don't
ask me again” box to prevent this window from appearing
every time you run Write DSeries Files. If you want to
reset the HPUTIL path thereafter, call up this window from
the File menu. See Figure 3-231.

 "" &. /0#
+ ) +)

After pressing OK (or Cancel), the following is displayed

as shown in Figure 3-232.

  ! .,-.



 
     Confidential

 
-$$)


 ""    

 )

This window allows you to specify the type and range of

data you want to transfer from the database to DSeries files.
The last data transferred is shown at the top of the window.
Choose a Run Number for transfer. The start and end times
for the run are updated from the database. Adjust the start
and end times for the range of data you wish to transfer.
The corresponding depths are read from the database and
displayed.
Next, choose the type of data you want to transfer: MWD
and Surface Data, Time-Depth data, and/or Survey data. If
survey data is selected, also specify the Path that the
surveys should correspond to.

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)

If you want to append to the MWD/Surface data file
(binary) check the Append box. It is not currently possible
to append to the spool or tvddata files.
Finally, press OK to start the data transfer. Progress
windows pop up for each of the data types selected. See
Figure 3-233.

 """ 3  
$( 

When the transfer is complete, the progress windows

disappear automatically.

   - 
General online help can be displayed by choosing Help
Topics from the Help menu.

  ! .,-0



 
     Confidential

 
-$$)


$/1)1+  *  &$/)(


The BackRest program is used to backup data from the
database, restore backed up data to the database, or
permanently remove data from the database or directories
on disk. The disk where backed up data directories reside
is typically the hard disk but may also be a Zip disk or other
removable medium.
The database tables that may be backed up and restored
are:
MWD_GENERIC RAW_MWD_GENERIC MWD_TIME
SURVEY WELL PATH_DESC
PATH HOLE HOLE_DATA
OPERATOR LOCATE DRILLDEPTH
RIG PUMP_DETAILS HYDRAULICS
SURVEY_REF SURVEY_RAW GENTIME

The operations that may be performed on the data are:

• Backup from database to disk
• Restore from disk to database
• Delete from database
• Delete from disk
These operations may be performed on a RUN, HOLE
SECTION, or WELL basis. You can choose the starting
point by selecting a node in either the database tree control
or the disk tree control.
• If a WELL node is selected, the operation
includes all holes in that WELL.

Note: Data other than MWD_GENERIC and

RAW_MWD_GENERIC may only be
operated on at the WELL level.

• If a HOLE node is selected, MWD data for all

runs in that hole are affected by the operation.
.,-1 "# $!%& '()*
Confidential


 
    

 
-$$)


• If a RUN node is selected, only MWD data for

that run are affected.


At start-up, the program connects to the database and reads
information about wells, holes and MWD runs into
memory. It also checks the backup base directory using the
directory name stored in the Windows registry or the
default of INTEQ\data\backup_runs and loads in folder/
file names that it finds there. With this information, two
tree controls are populated to give you a graphical
representation of the data stored in the database and on
disk. The main window is then displayed as shown in
Figure 3-234.

 ""% !

3


  ! .,-



 
     Confidential

 
-$$)


The window consists of:

• “tree controls”
- Database Tree
- Disk Tree
• operation buttons
- Backup
- Restore
- Delete from Database
- Delete from Disk
• data type check boxes
- MWD data
- Spool (time-depth) data
- Surface (drilling) data
- Survey data


The database tree control displays the wells, holes, and
MWD runs currently in the database.
The disk tree control displays the files and folders
containing “backed-up” data on disk. Each well has its own
folder, as does each hole within a well. A well is identified
by having the prefix WELL – in front of the name while a
hole folder is identified by having the prefix HOLE – in
front of the name. The names on disk have underscore
characters replacing any spaces in the actual names. The
well folders are placed in a base directory (either the
default directory or one specified using the Backup
Directory item of the Options menu.

(6  

Before performing one of the data processing operations,
you must select a node in either the database tree control or
the disk tree control.

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


• Selecting a WELL node means that any operation

will affect the well and all holes and runs in that
well.
• Selecting a HOLE node means that any operation
will affect the hole and any runs in that hole.
• Selecting a RUN node means that any operation
will affect data in that run only.

(6 " 
You can choose the type of data that will be affected by the
operation by checking/unchecking the boxes located
between the tree controls.
By default, if a well node is selected, all boxes are made
enabled and checked. You can change this selection by
unchecking boxes for data that are not required in the
upcoming operation.
This means that, if spool, surface or survey data are to be
acted on, a well node must be selected.
If a hole or run node is selected, all check boxes are made
inactive since you cannot choose the data type at these
levels. The MWD box is always checked.

(6 ' 

If you select a node in the database tree control, the
Backup and Delete from Database buttons are enabled
while the Restore and Delete from Disk buttons are
disabled. The reverse is true if you select a node in the disk
tree control.

 

6 
Pressing the Backup button starts the backup process.
What actually takes place depends on the node and the data

  ! .,-



 
     Confidential

 
-$$)


types selected:
If a Well node is selected…
The program creates a target folder under the base
directory with a name constructed from the well number
(short name) in the form WELL-xxxxxxx with any spaces
replaced by underscore characters. Several files are written
immediately to the new directory:
• wellinfo.dat : well record
• pdinfo.dat : path description records
• pathinfo.dat : path records
• locinfo.dat : well location record
• operinfo.dat : operator record
All of these files are comma-delimited ASCII files.

Note: It is recommended that WordPad be used to

view data files rather than NotePad.

For each hole record in the well, the program creates a

folder with a name constructed from the hole name in the
form HOLE-xxxxxxx with any spaces replaced by
underscore characters. Into this folder is written:
• holeinfo.dat : hole record
For each run in the hole, two files are written:
• RUN_#.dat (with # replaced by the actual MWD run
number) containing MWD_GENERIC records
• rawrun_#.dat (with # replaced by the actual MWD
run number) containing RAW_MWD_GENERIC
records
In addition:
• If the SPOOL data box is checked, a file named
spool.dat is written to the WELL folder with data
from the MWD_TIME database table.

.,-
"# $!%& '()*
Confidential


 
    

 
-$$)


• If the SURFACE data box is checked, a file named

surface.dat is written to the WELL folder with data
from the DRILLDEPTH database table.
• If the SURVEY data box is checked, a file named
survey.dat is written to the WELL folder with data
from the SURVEY database table.
If a Hole node is selected…
The program creates a target folder under the
corresponding WELL folder with a name constructed from
the hole name in the form HOLE-xxxxxxx with any spaces
replaced by underscore characters. Into this folder is
written:
• holeinfo.dat: hole record
For each run in the hole, two files are written:
• RUN_#.dat (with # replaced by the actual MWD
run number) containing MWD_GENERIC records
• rawrun_#.dat (with # replaced by the actual MWD
run number) containing RAW_MWD_GENERIC
records

Note: If the WELL folder corresponding to the

hole does not exist on disk, it is created.

If a Run node is selected:

Two files are written to the corresponding HOLE folder:
• RUN_#.dat (with # replaced by the actual MWD
run number) containing MWD_GENERIC records
• rawrun_#.dat (with # replaced by the actual MWD
run number) containing RAW_MWD_GENERIC
records

Note: If the WELL and HOLE folders

corresponding to the run do not exist on
disk, they are created.

  ! .,-



 
     Confidential

 
-$$)


During the backup (and restore) operations, a progress bar

is displayed, along with messages, to keep you informed as
to the status of the operation. See Figure 3-235.

 "", 9)*  3



2
Pressing the Restore button starts the restore process. What
actually takes place depends on the node and data types
selected:
If a Well node is selected…
The program creates a WELL record in the database,
populated with data from the wellinfo.dat file.
The program also creates new records in the
PATH_DESC, PATH, LOCATE and OPERATOR tables,
populating them with data from the pdinfo.dat,
pathinfo.dat, locinfo.dat and operinfo.dat files, read from
the WELL folder.
For each hole folder in the well folder, the program creates

.,-- "# $!%& '()*

Confidential


 
    

 
-$$)


a database record in the HOLE table and populates it with

data from the holeinfo.dat file. A HOLE_DATA record is
also created corresponding to the new hole record.
For each run in the hole, the RUN_#.dat file is read and
new records are written to the MWD_GENERIC table.
Then the rawrun_#.dat file is read and records are written
to the RAW_MWD_GENERIC table.
In addition:
• If the SPOOL data box is checked, the spool.dat file
is read and records are written to the MWD_TIME
database table.
• If the SURFACE data box is checked, the
surface.dat file is read and records are written to the
DRILLDEPTH database table.
• If the SURVEY data box is checked, the survey.dat
file is read and records are written to the SURVEY
database table.
If a Hole node is selected…
The program creates a HOLE record in the database,
populated with data from the holeinfo.dat file.
A HOLE_DATA record is also created corresponding to
the new hole record.
For each run in the hole, the RUN_#.dat file is read and
new records are written to the MWD_GENERIC table.
Then the rawrun_#.dat file is read and records are written
to the RAW_MWD_GENERIC table.

Note: If the WELL record corresponding to the

HOLE does not exist in the database, it is
created.

If a Run node is selected…

The RUN_#.dat file for the run is read and new records are
written to the MWD_GENERIC table. Then the

  ! .,-.



 
     Confidential

 
-$$)


rawrun_#.dat file for the run is read and records are written
to the RAW_MWD_GENERIC table.

Note: If the WELL and HOLE records

corresponding to the run do not exist in the
database, they are created.

5
Pressing the Delete from Database button starts the delete
process. This is a potentially dangerous action and you
should be absolutely certain that the data are backed up to
disk before proceeding.

&' 7
Failure to do this will result in a permanent loss of
data!

What actually takes place depends on the node and data

types selected:
If a Well node is selected:
The program deletes the specified WELL record from the
database. This triggers the automatic deletion of
EVERYTHING IN THE WELL. When complete the well
node and any hole and run nodes associated with it are
removed from the database tree.
If a Hole node is selected…
The program deletes the specified HOLE record from the
database. This triggers the automatic deletion of
EVERYTHING IN THE HOLE. When complete the hole
node and any run nodes associated with it are removed
from the database tree.
If a Run node is selected…
The program deletes records in the MWD_GENERIC and

.,-/ "# $!%& '()*

Confidential


 
    

 
-$$)


RAW_MWD_GENERIC tables corresponding to the

specified hole and run number. When complete the
affected run node is removed from the database tree.


Pressing the Delete from Disk button starts the delete
process. This is a potentially dangerous action and you
should be absolutely certain that the data are either in the
database or backed up to a removable Zip disk before
proceeding.

&' 7
Failure to do this will result in a permanent loss of
data!

What actually takes place depends on the node and data

types selected:
If a Well node is selected:
The program deletes the specified WELL folder and all
contained files and folders. When complete the well node
and any hole and run nodes associated with it are removed
from the disk tree.
If a Hole node is selected:
The program deletes the specified HOLE folder and all
contained files. When complete the hole node and any run
nodes associated with it are removed from the disk tree.
If a Run node is selected:
The program deletes RUN_#.dat and rawrun_#.dat files
from the HOLE folder corresponding to the specified hole
and run number. When complete the run node is removed
from the disk tree.

  ! .,-0



 
     Confidential

 
-$$)


$/  )


+ $/
The following is the MSS data that should be backed up:
• c:\inteq\res\database\access\res.mdb
• c:\inteq\res\data directory and all subdirectories
• files in the c:\inteq\res\ctl directory with the
following extensions .ucs .mps .ini .cvt .cda
• c:\my documents directory and all subdirectories
• Registry below the node
HKEY_CURRENT_USER\Software\INTEQ-RES
Saving and restoring MSS data is performed via the Save
MSS Data to Zip and Restore MSS Data from Zip menu
shortcuts that link to c:\inteq\res\archive.bat file.
See Figure 3-236.

 ""1 -)( )$ )

The data are backed up in zipped format as individual files

corresponding to each of the individual components
selectable by the “Save MS Data to Zip” and “Restore MSS
data from Zip” menu options. When data are restored you
.,-1 "# $!%& '()*
Confidential


 
    

 
-$$)


will be prompted to confirm any overwrites.

(
6
HPUTIL offers a “Get Data” option from its Main Screen
that allows you to save all the files referenced in the
c:\hputil\exe\gdpf.lst file for the given job number. Data
may be saved to a Zip disk, floppy disk, or hard disk. The
c:\hputil\exe\gdpf.lst file needs to be modified to match
local file naming conventions. Restore selects from a table
of all the “archives” that can be listed on the source media.
Floppies have no selection, hard disk, Zip disk, and
networks can have multiple “archives” and a selection is
required. On restore, NO files are overwritten unless you
confirm the overwrite.
The DSeries menu offers an alternative run-by-run data
backup/restore option, with similar target drive options.

  ! .,-



 
     Confidential

 
-$$)


  -*
;   

+#
& 
(


Data from the database are required in disk files for
processing on the offline system. This offline processing
includes depth-tagging of MWD tool memory data and
plotting logs using the MPLOT program. The files that are
needed are:
• spool .dat containing time-depth data (from the
MWD_TIME database table)
• tvddata.dat containing survey data from the
SURVEY database table
• binary.dat containing MWD and surface data from
the MWD_GENERIC, DRILLDEPTH, and
GENTIME database tables
While MPSetup is able to write out the spool and tvddata
files directly from the database to the target files in the
HPUTIL directory on the shared hard disk drive, it is used
primarily to build “configurations” that can be used to
create the binary file used by MPLOT for drawing logs.
A configuration consists of a number of sections that
specify:
(a) the range of data to be used, including the hole
identifier, run number, relog number and starting and
ending times, and
(b) the type of data to be used; i.e., categories such as
Gamma, Neutron, Surface Data, etc.
Thus, the configuration allows you to specify exactly
which sections are to be used in MPLOT logs, especially
where relogs have been made over the same depth range.
Once built, the configuration can be saved to a file on the
hard disk and reloaded for use at a later time. After

.,- "# $!%& '()*

Confidential


 
    

 
-$$)


reloading, you can choose to edit or remove existing

sections, add new sections, or simply use the configuration
to write out the binary file.
Configuration files are typically stored in the INTEQ ctl
directory and have the extension “mps”.
The program requires that certain files already exist on the
hard disk:
mwd_rtp.ctl in the INTEQ ctl directory
mserdb.fil in the HPUTIL directory
The following output files are written to the HPUTIL
directory:
binary.fil database file
binary.idx index file
binary.tdx index file


Upon start-up, the main MPSetup window is displayed.
See Figure 3-237.
If a current configuration exists (the name is stored in the
Windows registry), it is reloaded into the table. The current
section is displayed in RED and data associated with the
section are displayed in the text fields and controls below
the table.
Above the section table there are two text fields displaying
the configuration name and the well identifier. You can
choose from the drop down list of available wells. A
configuration is given a name when it is saved for the first
time.
At this point you can:
• modify an existing section by selecting the row in
the table, making changes to the section data and
then pressing the Update Row button.

  ! .,-



 
     Confidential

 
-$$)


 ""2 !0 $  !

3


• delete an existing section by selecting the row and

pressing the Delete Row button.
• insert a new section by choosing the hole, run, relog
and curve data in the lower part of the screen and
then pressing one of the Insert buttons to place the
new section at the top or bottom, or above or below
the currently selected row.
The hole identifier is selected from the drop down list of
existing holes. If the hole is changed, the run number list is
changed accordingly. Choosing a new run number will
likewise change the relog number list. When the hole, run
and relog numbers have been selected, the time range is
displayed along with the corresponding measured depth
range. If a different time range is required (less than the
displayed range), change the start and end times
accordingly. The corresponding depths are displayed for
the new times. The data categories available in that range
are displayed in the list to the right. You choose which of

.,.

"# $!%& '()*

Confidential


 
    

 
-$$)


these categories should be used in the section.

Once the configuration is set up as needed it is saved to the
hard disk by choosing Save from the File menu.
A saved configuration can be reloaded using the Open
command from the File menu.
A brand new configuration can be started using New from
the File menu.

+ 
You can choose the type of datafile to write from the
Process menu. Before doing so, it may be worth checking
the current setting of the HPUTIL directory location since
the program requires certain control files in this directory
and the new data files are output to this directory. Choose
the Settings item from the Options menu.
See Figure 3-238.

 ""4 
 3


You can change the location of HPUTIL by typing directly

into the entry box.
In the Process menu there are three data output items:
• Write MWD/Surface data: to write the MPLOT
binary files (based on the configuration)
• Write Time-Depth data: to write the spool file
(all MWD_TIME data in the well)

  ! .,.




 
     Confidential

 
-$$)


• Write Survey data: to write the tvddata file

(all survey records in the well)
The progress of the output is displayed on a pop up
window. See Figure 3-239.

 ""5 $ 0 3



If you press the Cancel button, output is halted at the end

of the current section.


The only other option in the program is the choice of units
conversions. These are for the display only as the values
written to the data files are always in S.I. metric units.
Choose Units Conversions from the Options menu to pop
up the standard window that allows you to specify the
conversion used for each identifier. Save the setup and
close the configuration window and the new settings are
used immediately.

.,.
- "# $!%& '()*
Confidential


 
    

 
-$$)


  + &+(


The Plot Driver application (PDriver) provides two
important pieces of functionality. First, it is used to extract
archived curve data from INTEQ data stores and directly
load the RIS-Info plotting program without having to go
through any manual import methods. Secondly, it provides
data entry screens for the editing of the log plot headers
and trailers.
On application start-up, the previous settings and
configuration options are loaded from the Windows
registry. If this is the first time the application is run,
default settings are used.
There is no need to manually start the RIS-Info software
package. Whenever the PDriver application determines
that it needs to communicate with RIS-Info it checks
whether or not the application is already running and if
necessary starts it.
Upon start-up, the PDriver program displays the following
main window shown in Figure 3-240.

  ! .,.
.



 
     Confidential

 
-$$)


 "%6 0

 ' 

See Figure 3-241.

 "%
$ $



Template Name
This is a read-only field containing a list of plot templates
located in the RIS-Info plot sub-directory. This is the plot

.,.
/ "# $!%& '()*
Confidential


 
    

 
-$$)


template that RIS-Info will render the log data onto. The
curve data that gets extracted from the INTEQ data stores
is determined by the mnemonics used in the selected plot
template.
Plot Type
This is used to select the desired plot type. A choice
between plotting keys Measured Depth, True Vertical
Depth, and Time is allowed. Your choice determines the
type of view displayed by RIS-Info.
After RIS-Info draws the plot, the plot type can be changed
from within RIS-Info by changing the setting on the Range
of Interest… dialog. Data for all three vertical plotting
keys is sent to RIS-Info, but only one is used in the active
plot.

Note: Changes made to the plot type within RIS-

Info will not change the plot caption on the
log header.

See also: Tasks Menu: Change the log plot headers without
resending the curve data.
Scale
Designates the plot scale factor that RIS-Info will be
instructed to use. If the current setting is blank or needs to
be changed, select the Change… button to the right. A list
box containing the available scales for the current plot type
is displayed. Custom scale factors can also be created. To
make your custom scale factor persistent, add a custom
scale factor within RIS-Info.

Note: Changes made to the scale factor within

RIS-Info will not change the scale caption
on the log header.

See also: Tasks Menu: Change the log plot headers without
resending the curve data.

  ! .,.
0



 
     Confidential

 
-$$)


Scale Factor
The Scale Factor can be changed by pressing the Change…
button located on the main application window. This pops
up a window as shown in Figure 3-242.

 "% - ) )

Select the desired scale factor from the list or choose the
Custom... button which will display the window shown in
Figure 3-243.

 "%"  ) )

Data Source Object Tree

See Figure 3-244.

.,.
1 "# $!%& '()*
Confidential


 
    

 
-$$)


 "%% B)


Use the data source tree view to select the facility, well,
path, and hole to obtain curve information.

Note: In the current system, data to be plotted is

extracted from the binary.fil file of the
HPUTIL directory. Therefore, the data
source tree selection is mainly used to get
header-related data and to specify the
PATH which is used in vertical depth
calculations.

1
See Figure 3-245.

 "%, / 


Use this control to specify the type of log headers and

  ! .,.




 
     Confidential

 
-$$)


trailers to create for the plot. Specific pages to attach to the

log plot can be selected through the Headers & Trailers
options property page.
None
Selecting this button indicates that no header or trailer
pages will be generated for the current plot.
Abbrev
Selecting this button will cause the MINI header output to
be generated. The contents of the MINI header can be
configured through the Headers & Trailers options
property page.

Note: The MINI and FULL log headers can be

independently configured from the options
property page.

Full
Selecting this button will cause the FULL header output to
be generated. The contents of the FULL header can be
configured through the Headers & Trailers options
property page.

Note: The MINI and FULL log headers can be

independently configured from the options
property page.

2 
This control is used to specify the range of data to be
plotted. See Figure 3-246.

.,.
 "# $!%& '()*
Confidential


 
    

 
-$$)


 "%1 0 



From
Starting depth or time, used to set the range of interest in
RIS-Info.
To
Ending depth or time, used to set the range of interest in
RIS-Info.
See Also: RIS-Info Options Property Page.

6

See Figure 3-247.

 "%2 -)
9


Start Plot
Pressing this button opens/creates the RIS-Info project,
opens/creates the RIS-Info Well, loads the plot template,
starts the curve data extraction process, generates the log
header and trailer metafiles, and sends all of this
information to RIS-Info. Once the process is complete the
button is disabled to prevent you from accidentally
pressing it again and having to start the whole process
over.

  ! .,.




 
     Confidential

 
-$$)


Note: After the transfer completes the RIS-Info

application is maximized.

Stop Plot
Enables the Start Plot button.


This section documents the menus for the PDriver
application. See Figure 3-248.

 "%4 !


+
See Figure 3-249.

 "%5  !



Exlog/Inteq Export…
Exports the raw curve data in ASCII format. This options
is only available after the curve data has been sent to RIS-
Info.
Note:
1. The Time vertical plotting key is not exported.

.,.
"# $!%& '()*
Confidential


 
    

 
-$$)


2. Raw is intended to mean that missing data is not

interpolated.
LAS Export…
Exports the curve data in LAS format. You can specify the
starting depth, ending depth, and depth increment. This
options is only available after the curve data has been sent
to RIS-Info.

Note: The Time vertical plotting key is not

exported. Also, there is a program called
reformat.exe that ships with RIS-Info which
can be used to reverse the depth direction,
extract specific curves, change the depth
increment, etc.… of the export file.

Properties…
Displays the current data object tree selections.
Page Setup…
Allows the page size to be toggled between 8.75 x 6.25
inches and 8.75 x 6.50 inches. This option is only of use
when fanfold paper is being used.
Exit
Exits the application.

=*
See Figure 3-250.

 ",6 ' !



  ! .,.



 
     Confidential

 
-$$)

Toolbar
Display/Hide the application toolbar.
Status Bar
Display/Hide the application status bar.


See Figure 3-251.

 ",
* !


Update Header/Trailer EMFs

This option allows the log plot headers and trailers to be
changed after they have been created and sent to RIS-Info.
Make whatever changes are necessary to the headers and
trailers then select this menu item to get the changes loaded
into RIS-Info without resending the curve data.
Extract Lithology from Exported Annotations
This menu command will read an annotations file that was
exported separately from RIS-Info and extract the
lithology information into a comma-separated data file
suitable for importing into RIS-Info. Refer to the
Annotation Lithology Import description located in the
RIS-Info Help system for a detailed description of the file’s
contents.

.,.- "# $!%& '()*

Confidential


 
    

 
-$$)


 
See Figure 3-252.

 ", /$

The Help Menu offers the following commands, which

provide you assistance with this application.
Help Topics
Offers you an index to topics on which you can get help.
About PDriver…
Displays the version number of this application.


See Figure 3-253.

 "," & !



The Edit Menu offers the following commands:

  ! .,..



 
     Confidential

 
-$$)


Bit Run Data…

Used to view and edit bit run data. See Figure 3-254.

 ",% 9 


This dialog box is used to enter and view the bit run data.
Columns of data can be added, deleted, inserted, cleared,
copied, and pasted. Select an entire column then do a right
click to view the context menu.
DSeries compatibility:
This application currently reads and writes the file
bitdata.cfg. See Also: Spread Sheet Context Menu.
Calibration Data…
Used to view and edit calibration data. See Figure 3-255.

.,./ "# $!%& '()*

Confidential


 
    

 
-$$)


 ",, 

')

This dialog box is used to enter and view the calibration

data. Columns of data can be added, deleted, inserted,
cleared, copied, and pasted. Select an entire column then
do a right-click to view the context menu.
DSeries compatibility:
This application currently reads and writes the file
calibdat.cfg. See Also: Spread Sheet Context Menu.
Environmental Parameters…
Used to view and edit environmental parameters.
See Figure 3-256.

  ! .,.0



 
     Confidential

 
-$$)


 ",1 &



 0

This dialog box is used to enter and view the environmental

data. Rows of data can be added, deleted, inserted, cleared,
copied, and pasted. Select an entire row then do a right-
click to view the context menu.
DSeries compatibility:
This application currently reads and writes the file
envirdat.cfg. See Also: Spread Sheet Context Menu.
Header Configuration…
Used to view and edit log plot header strings.
The header and trailer type selection specified in the main
window part of the application determines whether the
property sheet for an abbreviated header or a full header is
displayed or maybe none at all.
Abbreviated Header
See Figure 3-257.

.,.1 "# $!%& '()*

Confidential


 
    

 
-$$)


 ",2 !; /

For information specific to one of the tabs on this property

sheet select a link below.
• Header Strings Property Page
• Location Property Page
Full Header (See Figure 3-258).

  ! .,.



 
     Confidential

 
-$$)


 ",4 #++ / 0$

All the pages on this property sheet are used to define the
contents of the first page of the log header.
For information specific to one of the tabs on this property
sheet see below.
Header Strings Property Page
This dialog displays assorted header text strings.
The Defaults… button displays a dialog box that allows
the user to select one of six different application defined
default header strings.
The Load… button displays a list box containing the titles

.,. "# $!%& '()*

Confidential


 
    

 
-$$)


of any saved log plot format settings. Select the desired

configuration to load.
The Save… button allows the current log plot format to be
saved under the user supplied title.
The Delete… button allows you to delete the selected log
plot format.
The Print Type Caption combo box provides a list of
application defined settings as well as offers the ability to
handle user defined text. To enter a user defined text string,
simply type the text into the combo box instead of
selecting from the list. This text string will then appear in
the log header.
The Comments File combo box provides a list of *.fil files
to select from. Pressing the New… button will create a
skeleton remarks file that already contains the curve
mnemonics, their descriptions, and units of measurement.
Abbreviated Header vs. Full Header:
The 4 line Other Services field is only available when
configuring a Full header. The Date and Time fields are
only available when configuring an Abbreviated header.
DSeries compatibility:
Most of this information is obtained by reading the
reghead.cfg and log.fil files.
Only the data within the plot configuration grouping, (the
large rectangle that surrounds the Defaults…, Load…,
Save…, and Delete… buttons), is saved to the log plot
format file log.fil.
See also the Header & Trailer Options Property Page.

  ! .,.



 
     Confidential

 
-$$)


Location Property Page (see Figure 3-259).

 ",5 +)

0$ 0

This dialog displays well location information. The data in

the grayed out fields is obtained from the database unless
the Load log header values from database option is
unchecked.
The Reference # Caption combo box provides a list of
application defined settings as well as offers the ability to
handle user defined text. To enter a user defined text string,
simply type the text into the combo box instead of selecting
from the list. This text string will then appear in the log
header.
The Other User Defined Captions fields are two arbitrary
lines of text that can be used at the user’s discretion. These

.,.-
"# $!%& '()*
Confidential


 
    

 
-$$)


two lines of text will be shown at the location where

previous log plots displayed the section, township, and
range information. Blank entries are acceptable.
Abbreviated Header versus Full Header:
The 4 line Well Location field, the Reference # Caption
and value, as well as the two user defined captions are only
available when configuring a Full header.
DSeries compatibility:
If the Load log header values from database option is
unchecked then some of the information is obtained by
reading the reghead.cfg file. The 4 line Well Location field
obtains it’s information from the file log.fil. The
information for the Reference # Caption and value, as well
as the two user defined captions must be supplied by the
user since this is a new feature.
See also the Header & Trailer Options Property Page

  ! .,.-



 
     Confidential

 
-$$)


Reference Measurements Property Page

(see Figure 3-260).

 "16 

) !


This dialog displays wellsite reference measurements. The

data in the grayed out fields is obtained from the database
unless the Load log header values from database option is
unchecked.
The Depth Out Permanent Datum field provides a list of
application defined settings as well as offering the ability
to handle user defined text. To enter a user defined text
string, simply type the text into the field instead of
selecting from the list. This text string will then appear in
the log header.

.,.-- "# $!%& '()*

Confidential


 
    

 
-$$)


User Defined Rig Reference Points:

There are three user definable rig reference points. If the
selected caption happens to be either Elev. RKB, Elev.
DF, Elev. RT, or Sea Bed/GL the data is loaded from the
database.
To make any of these fields print as white space, enter a
blank text string in the combo box and for the value.
DSeries compatibility:
If the Load log header values from database option is
unchecked the information is obtained by reading the
reghead.cfg file.
See also the Header & Trailer Options Property Page.

  ! .,.-.



 
     Confidential

 
-$$)


Bore Hole Record Property Page (see Figure 3-261).

 "1 9 / )

This dialog displays the bore hole record information. The

data is obtained from the database unless the Load log
header values from database option is unchecked.
DSeries compatibility:
If the Load log header values from database option is
unchecked the information is obtained by reading the
reghead.cfg file.
See also the Header & Trailer Options Property Page.

.,.-/ "# $!%& '()*

Confidential


 
    

 
-$$)


Casing Record Property Page (see Figure 3-262).

 "1 
 )

This dialog displays the casing record information. The

data is obtained from the database unless the Load log
header values from database option is unchecked.
DSeries compatibility:
If the Load log header values from database option is
unchecked the information is obtained by reading the
reghead.cfg file.
See also the Header & Trailer Options Property Page.

  ! .,.-0



 
     Confidential

 
-$$)


Company Information Property Page (see Figure 3-263).

 "1" $

 


This dialog displays company information. The data in the

grayed out fields is obtained from the database unless the
Load log header values from database option is
unchecked.
DSeries compatibility:
If the Load log header values from database option is
unchecked the information is obtained by reading the
reghead.cfg file.
See also the Header & Trailer Options Property Page.

.,.-1 "# $!%& '()*

Confidential


 
    

 
-$$)

Tool Data… (see Figure 3-264).

 "1%
 

This window is used to enter and view the MWD tool

configuration data (Serial Numbers, Sensor Offsets to Bit,
Acquisition Rates, and other miscellaneous tool
information). Columns of data can be added, deleted,
inserted, cleared, copied, and pasted. Select an entire
column then do a right click to view the context menu.
DSeries compatibility:
This application currently reads and writes the file
equipdat.cfg.
See also the Spread Sheet Context Menu.
Curve Properties…
Used to view and edit the Averaging and Smoothing
intervals defined for the curve mnemonics.
See Figure 3-265.

  ! .,.-



 
     Confidential

 
-$$)


 "1,  0$

This dialog allows you to specify averaging intervals and

smoothing intervals for any of the curves defined in the
plot template. The averaging interval is specified by
selecting one of the predefined entries from the drop down
list. The smoothing interval is a user defined value. As in
MPLOT, a smoothing interval of 0.0 performs no
smoothing.
The selected plot type will determine whether the
averaging interval uses the measured depth, true vertical
depth, or time values as the averaging range. In the case of
time plots, the averaging interval specified is in terms of
minutes. See also the Template Options.

.,.- "# $!%& '()*

Confidential


 
    

 
-$$)



Options…
Displays the application’s Options tabbed window.
Header & Trailer Pages tab (see Figure 3-266).

 "11 / 
 0

Load log header values from database

When this option is checked, all relevant information
currently available from the database will be extracted and
inserted into the appropriate header string. This option
causes many entries on the Header Configuration property
sheet to become read-only.

  ! .,.-



 
     Confidential

 
-$$)


Note: If you want to customize the data after

loading from the database, load the data
from the database, uncheck this item, then
make your changes by hand. When doing
so, special care should be taken because the
setting will be saved in the Windows
registry and restored the next time the
application is started.

Abbreviated Headers & Trailers

Remarks Page
Toggles whether or not the Remark or Comment page(s) is
generated as part of the Abbrev log header output.
Add Surveys
Toggles whether or not the Survey page(s) are generated as
part of the Abbrev log header output.

Note: The survey data is loaded from the database.

There is not a survey data entry screen in
this version of the program.

Full Headers & Trailers

Bit Run Page
Toggles whether or not the Bit Run page(s) are generated
as part of the FULL log header output.
Equipment Page
Toggles whether or not the Equipment page(s) are
generated as part of the FULL log header output.
Environmental Page
Toggles whether or not the Environmental parameters
page(s) are generated as part of the FULL log header
output.

.,..
"# $!%& '()*
Confidential


 
    

 
-$$)


Calibration Page
Toggles whether or not the Calibration Verification
page(s) are generated as part of the FULL log header
output.
Remarks Page
Toggles whether or not the Remark or Comment page(s)
are generated as part of the FULL log header output.
Add Surveys
Toggles whether or not the survey page(s) are generated as
part of the FULL log header output.

Note: The survey data is loaded from the

database. There is not a survey data entry
screen in this version of the program.

RIS-Info Options tab (see Figure 3-267).

  ! .,..



 
     Confidential

 
-$$)


 "12  
 $


RIS-Info determines plot range from log data

When this option is enabled, the curve data is extracted
only at the time the information is sent to RIS-Info. If this
option is disabled, the data extraction occurs whenever the
plot template is changed, a well is selected, etc… This
becomes very time consuming but it allows you to set a
range of interest outside of RIS-Info. Having this option
enabled is the preferred choice. Changing the range of
interest in RIS-Info is very easy.
Enable DDE logging
Facilitates the logging of DDE events for debugging
purposes. After enabling this option you must restart the
application. Output is written to a log file located in your
temp directory. The file is called PlotDriverDDELog.txt.

.,..- "# $!%& '()*

Confidential


 
    

 
-$$)


Note: Always prompt with Curve Properties

dialog before sending data to RIS-Info.

When this option is enabled, the Curve Properties dialog

will be displayed prior to sending the curve data to RIS-
Info. This allows you to double-check the averaging and
smoothing intervals before plotting.
See also: the Curve Properties Dialog.

- >>>

 =

The plotter should be configured as follows:
Using the menu button located on the front panel of the
plotter set as follows:
scaling = +6/64 Inches
vertical emu = 203 dpi

(6
The selected plot template determines what curve data gets
extracted from the INTEQ data stores and subsequently
plotted.

(61 
First you configure the type of headers and trailers to
generate. Then select the desired pages to include from the
Header & Trailer Options Property Page.

&
RIS-Info uses a units dictionary that allows curve data
units to be converted at run time. As long as the from and
to units are defined in RIS-Info’s units dictionary you can
convert on the fly within the plot. Ideally, you would make
a copy of units.ini then edit the copy to prevent future
installations from overwriting. The trick is to put any

  ! .,...



 
     Confidential

 
-$$)


custom unit mnemonics/labels into the file

(case insensitive).
Of course you need to configure RIS-Info to use the new
units-dictionary. This is accomplished by changing your
RIS-Info global preferences project settings as depicted in
the dialog box in Figure 3-268.

 "14 : 0

)

2 

From the main menu, select    - 

!
" then press the Edit… button located on
the Header Strings property page.
See also the Header Strings Property Page.

.,../ "# $!%& '()*

Confidential


 
    

 
-$$)



 ! 
First make the necessary changes to the header contents
then select .  7  - 2 &
from the main menu. This will force RIS-Info to load the
new headers and trailers without the burden of resending
the curve data.
This is a fast and efficient way to create multiple plots
using different scale factors or plot types. Simply make the
desired changes in RIS-Info, synchronize the header string
captions with the changes, then use the main menu item
.  7  - 2 & to propagate
the changes to RIS-Info.

  ! .,..0



 
     Confidential

 
-$$)


•Notes•

.,..1 "# $!%& '()*

Confidential


 
    

 
-$$)


•Notes•

  ! .,..



 
     Confidential

 
-$$)


•Notes•

.,.. "# $!%& '()*

Confidential


 
    
  4

 

Chapter 4 covers details and procedures

for setting up MSS for the first time.


 

For operation of MSS programs it is always necessary to
start and configure the Message Server (MsgSvr) program
on the 1of3 real-time computer first.

  
  *+, &

 &
%
The Client and Server properties must first be defined.
Under normal circumstances where the INTEQ computers
are on their own network the default setup of Server being
Local and Clients being Any, will work fine. In other
situations where the INTEQ computers are on a broader
scope of network it may be necessary to define the server
specifically and restrict client access to specific IP
addresses, (see Applications section on Message Server for
more details). While it is not strictly necessary to change
the CDA name in MsgSvr, it is recommended that you
change it to an intuitive name, usually the well name.
Open the Message Server properties, select the Server Tab
and select the Local button.
&
% 
  
"
%  ;
$
From the Properties window, select the Clients Tab and
select the Any button.
&
% 
  
"    #
  ! /,



 
     Confidential

 

 $
Change the CDA name to an intuitive unique name
(e.g., well name).
&
% 
  
" #  ;
$
# 
Apply the changes and close the properties window.
&
% 
  
Minimize the MsgSvr window by selecting the - button at
the top left of the MsgSvr window.

  #
With the SARA and HAZARA systems, all sensor
calibration is performed from within the ReadOpto
program.

  
  *+, &

  

Calibration is divided up into two main groups, digital

sensors and analog sensors. All digital calibrations are
performed via the Digital Sensor Calibration window.
Open the window by selecting it from the ReadOpto
Configuration menu.
 

!
" 
'
"
All analog calibrations are performed via the Analog
Sensor Calibration window. Open the window by selecting
it from the ReadOpto Configuration menu.
 

!
" #

'
"

/,- "# $!%& '()*

Confidential


 
    

 

 $

+
  #

6
It is essential to get an accurate calibration of Block Height
in order to maintain accurate depth tracking. Taking care
and a little extra time to get an accurate Block Height
calibration at the start of a job will save a lot of problems
later on. A 100 feet (30 meter) strapping tape will be
required for simple, accurate calibration. There are various
ways to get an accurate calibration. The following
describes one way.
Some legacy Block Height encoder systems have involved
two types of calibration points, Height and Layer Change.
Although the MSS hardware and software original
specification included these two types of points, it was
decided that using layer change was somewhat redundant
assuming the following.
1. Height change per revolution remains linear between
Draw Works Layer changes.
2. Accurate calibration requires taking a height
calibration point at the layer change.
Calibration of Block Height requires a calibration at the
lowest point of travel of the travelling blocks, the highest
point and exactly at the points of all layer changes in
between the high/low points, (usually about 3 or 4 points).
Note that unlike some legacy systems, it is irrelevant to
MSS whether encoder counts increase or decrease as the
blocks travel in either direction, so it makes no difference
which way round the encoder is installed on Draw Works.
Also note that Block Height is a somewhat arbitrary
measurement. Depending on where you measure from it
will vary the value of the lowest (zero) point. Hence “zero”
is unlikely to be actually 0.00 m. As such, at any given
block position, the MSS block height value will be a
different value to any other system in use by the drilling
contractor or other service companies. It may vary by a few

  ! /,.



 
     Confidential

 

 $
meters, make note of the difference but do not
subsequently reset the calibration to coincide with some
one else’s value.
Probably the most convenient time for calibrating block
height will be while tripping in. With the Blocks at the
lowest position, secure the end of a 100+ feet/30+ meter
strapping tape to an appropriate point on the travelling
blocks. Note that chances are there will be some wind
blowing which will bow the tape out and potentially
introduce some considerable error into the calibration. It
may be necessary to put some tension on the tape to make
sure the measurement is accurate with a perfectly straight,
vertical tape. Therefore, when securing the end of the tape
make sure that it is securely fastened and that if you pull
hard on it that it will not be able to slip. A good way to do
this is to tightly tie the tape to the bottom of the bails or to
hook the end of the tape over and then tie and tape it, to the
clamp on the bails that secures the rubber straps that go
between the bails and the elevators. If the tape is only 100
feet and the total block travel is a bit more than this, you
can extend the reach of the tape with a small length of rope,
tying one end to the bottom of the bails and the other to the
strapping tape. Obviously ensure that everything is tied
securely and that, if necessary, you take into account the
exact distance from the bails to the start of the tape.
After taking the lowest calibration point, get the driller to
lift the block to the first drill line layer change on the
drawworks drum. Make sure the driller stops exactly at the
point of layer change. Take the next Height measurement.
Repeat for all subsequent layer changes and for the highest
point of travel of the Blocks.

Note: Make sure the strapping tape is perfectly

straight and vertical when taking each
Height measurement.

/,/ "# $!%& '()*

Confidential


 
    

 

 $

(*
Start the ReadOpto program and open the Digital
Calibration window.

  
  *+, &

  


!
   '

Choose BLOCKHEIGHT.
Assuming that the calibration points are either the default
points or old incorrect calibration points, delete all lines of
the encoder calibration table:
Select each row by clicking with the left mouse button on
the row number, pull up the Sort Rows/Delete Rows menu
by clicking the right mouse button and select Delete Rows.


 '
  $
 '

<
$ 


=  

Start calibrating by pressing the Start Calibrating button.


 '
  $
 '


 '
Go to the drill floor, with the calibration switch connected
to the LEMO junction box (SARA and P&F systems), or
HAZARA unit (HAZARA systems), calibrate at each
calibration point by pressing the HT switch. Write down
the exact height measurement for each point. (see the
above Procedural Considerations).
Return to the MSS cabin and stop the calibration routine by
selecting the Stop Calibrating button.


 '
  $
 '



 '
Enter the height value for each of the calibration points
directly into the Height Column:


 '
  $
 '

 -*8-
The calibration is now complete. Close the calibration

  ! /,0



 
     Confidential

 

 $
window by selecting the OK button.
Click :

6
#2  
Counts are tracked by the M4RTU in the SARA or
HAZARA units, therefore the ReadOpto program receives
counts as a total number. If HAZARA or SARA loses
power then their internal counts will be reset to zero. When
the drilling contractor cuts and slips the drill line, the
encoder will change counts even though the block height
will not be moving. Both of these situations result in the
ReadOpto calibration table becoming invalid. ReadOpto
has a Reset Digital Counters option to get around these
events.
When you reset the digital counters, a height is entered for
the current number of counts. ReadOpto calculates from
the original calibration table what the counts should have
been for that height, subtracts the two and then applies that
difference to all the counts in the calibration table; i.e., does
a relative counts shift on the calibration table.
To reset counts accurately, the blocks should be exactly
positioned at a known position. The block height must be
entered as per the MSS original height calibration and not
the contractors or other service company height. A good
position for resetting counts would be at the exact layer
change; e.g., if power is lost to HAZARA while drilling a
single down, restore power to HAZARA and then get the
driller to pick up to the closest layer change and briefly
hold the pipe there while the counts are reset.
To reset counts, open the Reset Digital Counters window.
 

!
   



With the blocks at a known reference height, enter the

block height.
 
  
$. -/

/,1 "# $!%& '()*

Confidential


 
    

 

 $
Apply the change, and exit the window.
Click :

2
Calibration of the RPM sensor is a simple case of entering
counts per revolution in the Digital Sensor Calibration
window. This is the number of counts that the RPM will
read each time the drillstring rotates once, normally 1.
From the Digital Sensor Calibration Window enter the
counts per revolution.


 '
  & 
 
%


Exit the calibration window by selecting OK.
Click :

 
  #
Calibration of the 4-20 mA sensors involves a two point
(high and low) calibration. The low point for each sensor
should be zero or as close to zero as possible and a high
point which should be the full scale value for the sensor or
as close to full scale as is possible.

6

6( 
Block Separation was intended for depth tracking on a
floating rig where the input would come from the drilling
contractors sensor. If rigged up, the low and high points
will be taken directly from the contractors calibrated
values. It is unlikely that this sensor value will be used
since the preferred method of depth tracking will probably
be by using a Motion Compensation (Rig Heave) sensor in
conjunction with a wireline retriever (Geolograph line)
encoder.

  ! /,



 
     Confidential

 

 $


Take the low point when there is nothing being suspended
from the Blocks. The Low value will be the weight of the
blocks as taken from the driller’s instruments. Take the
High value point when the largest possible weight is being
suspended from the blocks, usually the full bottom hole
assembly and drillstring, in an off bottom position and
preferably with drillstring being rotated slowly. Again the
High value will be taken from the driller’s instruments.

(
Standpipe pressure will normally be disabled, since the
value is sent to the CDA by MWDecode via the MsgSvr.
The calibration is performed in MWDecode program
which is discussed later in this chapter.

A

Note: Torque (0-1,000 amp, 2-10 volt).

Take the low point when the drill pipe is not being rotated
from the surface This will be the 0 (zero) value. Take the
high value when the drillstring is being rotated by the
rotary table or top drive. Take the high value from the
driller’s instruments. The current may vary so much when
rotating that it will often be hard to calibrate accurately. In
this case, a more accurate calibration would probably be to
just enter the sensors specified range for the calibration. In
the case of MSS this would be 2.0 volts = 0 amps and 10.0
volts = 1,000 amps.

(*
With regard to software, calibration of the analog sensors
involves the same steps for all sensors and are covered later
in this section.
To calibrate an analog sensor, from the analog sensor
calibration window, select the sensor to be calibrated
/, "# $!%& '()*
Confidential


 
    

 

 $
(Block Separation, Hookload, SPP or Torque) from the
Sensor combo box:

!
  #


 '
 



Select the sensor as being enabled by selecting the Enabled
check box:
#


 '
  '
When the sensor is at its low (zero or as close to it as
possible), select the Set Low Volts Now button. Note that
the sensor voltage is being read continuously and is
updated in the Current Volts data field.
#


 '
 
 ;
 9
 +

Enter the calibrated value that corresponds to the Low
Voltage point in the Low Value entry field.
#


 '
  ;
 9
When the sensor is at its high (full scale or as high as
possible), select the Set High Volts Now button.
#


 '
 
 - 9
 +

Enter the calibrated value that corresponds to the High
Voltage point in the High Value entry field.
#


 '
  - 9
Select OK to finish the calibration and close the calibration
window:

  ! /,



 
     Confidential

 

 $

  )  +


Start DSeries and enter all the necessary tool and BHA
data.

  
  *+, &

 

• Select the Units of Measure
• Enter Drillstring Components
• Build Bottom Hole Assembly
• Enter Correction Factors
• Write MSS File

4  - 

At the start of a job, you will need to enter certain
“environment” information. Included in this information
are the Client, Field, Facility, Well and Hole names, as well
as other data associated with these entities, such as location
details. These data are important to correctly identify the
real-time information saved to the database during
monitoring operations. They will also be used for log
headings and reports. The entry fields are:
• Client: this will normally be the oil company that is
operating the well.
• Field: allows you to specify the field name. The
Details... button allows you to enter additional
information.
• Facility: allows you to specify a facility name.
• Well: enter the well name.
• Hole: a single hole should be used throughout the
duration of the well unless a sidetrack occurs. If
sidetracks occur, new Hole entries are created with
appropriate names (Sidetrack 1, for example).
These data are input via the MSS program start-up Wizard.
/,
"# $!%& '()*
Confidential


 
    

 

 $
Start the MSS program.

  
  *+, &

 &


This starts an MSS Wizard (consists of six pages) to setup
the Well/Hole parameters and Survey parameters for
calculations. These pages are headed as follows:
1. MSS: Database/Location
2. MSS: Service Level
3. MSS: Processes
4. MSS: MWD Tool Configuration
5. MSS: Survey Reference
6. MSS: Summary
1. MSS: Database/Location
Click on 7::: and choose either FPS or Metric, then
.
A list of conversion IDs can be edited to a specific operator
needs. (All data are stored internally in S.I. units). Selected
units set can be created for each user. Click OK.
Client: Name of Client. Can be chosen from the drop
down menu. If the client name is not present in the list then
type it in, it will then be added to the catalog list.
Field: Type Field Name.
If required enter Location data such as Name, Country, etc.
and Long./Lat. Position. Check box for “offshore”. Click
OK.
Facility:
Enter Facility name. Click “Populate with Field Location
Data” to update similar entries as above. Click OK.
Enter Water Depth for offshore operations. Click OK.
Well:
"   1 

Enter Well Short name, Well, Lease Name and Job

  ! /,



 
     Confidential

 

 $
Number. Click OK.
"   1 
  ;
$


Select the Populate with Field Location Data button to

update similar entries as above.
"   1 
  

Enter Contractor, Rig name, and Datum information.

> Details > Well Properties > Rig > Pumps…
…>
Enter Rig Pumps Setup. Click OK.
This completes page 1of6 of the MSS Wizard pages.
Click +:
2. MSS: Service Level
Choose the service level being provided.
Check MWD and the corresponding service type.
Check DAQ/COMMS and the Acquisition type for surface
sensors.
Click Next
3. MSS: Processes
Choose the following minimum processes to run at start-
up and select the Auto Restart check box to have the
program restarted.
a. RtProc
b. ReadOpto
c. MWDecode
d. SvcPrc
e. ReadSpm: If monitoring SPM.
Any other processes can be added to this list as required.
Click Next

/,- "# $!%& '()*

Confidential


 
    

 

 $
4. MSS: MWD Tool Configuration
Choose the current path for DSeries and the MSS file.
Click Next.
5. MSS: Survey Reference
Enter all Survey related entries and Directional
corrections. Check the DRAW Corrections box, if
applicable.
Click on the BGGM Calculations button to display the
window for calculating Declination, Dip angle, and Total
Magnetic Field. Enter the required data and click on the
Apply button, or press the [ENTER] key in the last entry,
to make the calculations.
Click on the Cancel button to abandon your work or click
on the OK button to save the calculations.
Click on the “Survey Reference Data” button to enter
Declination, Grid Convergence, Survey Calculation, and
Well Coordinate information.
Click on the “Cancel” button to abandon your work or
click on the “OK” button to save the calculations.
Click on the SAG Calculations button to display the dialog
for SAG. Enter the required data and click on the Apply
button to view the calculations.
Click on the Cancel button to abandon your work or click
on the OK button to save the calculations.
Click on the OK button in the Survey Setup screen to close
the window.
BGGM Calculations
This performs the British Geological Survey Geomagnetic
Model (BGGM). This calculates declination, dip, and
magnetic field based on the well location latitude and
longitude.

  ! /,.



 
     Confidential

 

 $
Sag Calculations
Allows you to perform Sag calculations based on the
stabilizer position in the bottom hole assembly.
Click Next.
6. MSS: Summary
Confirm all data in summary screen and click OK.
The MSS: Configuration & Monitoring window appears
and the programs listed in section 3. MSS Processes will
now start.

/,/ "# $!%& '()*

Confidential


 
    

 

 $

4+
This program performs the filtering and decoding of the
MWD signal. It is one of the programs that starts
automatically at the end of the MSS Wizard.

  
  *+, &

 &1$

Choose the Master UFT file and tool family.
Enter the Maximum Pressure for the Transducer, usually
5,000 psi, and the Pump-On Threshold usually 200 or 300
psi.
Click Next.
MWDecode > Transmission Type > Select either Non-
Combinatorial or Combinatorial
Click Next.
For Non Combinatorial:
&1$
  
   +
)

'

Select the Transmission Format, Data rate, and filtering.
For Combinatorial:
&1$
  
  
'

Select Pulse width, Sync Window, and Sync delay.
Click Next.
Confirm the MWDecode: Settings Summary and Click
OK.

 + /

From RtProc configure the drilling setpoints and start the
depth tracking process.

$  
$   $."
Use the Tabs to enter setpoints especially the critical ones

  ! /,0



 
     Confidential

 

 $
for drilling - see below.
 $. 

 
  $.
Critical Setpoints:
• Pump Pressure Cutoff: Pump pressure must be
above this value to drill.
• In Slips Hookload: Hookload must be below
this value to recognize connections.
• Additionally, Hookload must be above this
value to recognize bit movement.

$  
$   $. 

 



Enter a value for DRILLDEPTH and (GEN)TIME
(if required) to save data to database.

 4+ 

$  
$  &1 
$"
Click Start.
This will start MWD processing and storage to database.

/,1 "# $!%& '()*

Confidential


 
    

 

 $

- 
MSS is capable of providing online hydraulics
calculations. This is accomplished by reading pump
strokes and calculating a value for FLOWIN. This can be
performed using either the ReadSPM program or the
Hydraulics Process in RtProc. The ReadSPM program
reads a data stream that is sent from the TOTCO™ gauge
to one of the Serial Ports. Each gauge is capable of sending
data from two pumps simultaneously.
Start ReadSPM.

  
  *+, &

 
&
The pump, annulus and drillstring data are entered from
MSS Configuration & Monitoring window. For more
details on this application refer to Chapter 3.
Annulus
&

   #  + #"
Enter all the necessary Annulus data; i.e., Annulus Name,
Date/Time, M. Depth Csg Shoe and annulus details, etc.
Drillstring
&

      
  + "
Enter all necessary data i.e., Run Name, Run Number,
Start Depth, and BHA details, etc.
Pumps
&

      
  
Enter all the necessary pump details; i.e., Name, Status,
Type, etc.
Start Hydraulics (Only if required).

$  
$  - $"

  ! /,



 
     Confidential

 

 $
Select the appropriate Tabs to enter the Mud Properties,
Rheology, and Cuttings properties.

  
  *+, &

  ;
 

 
2

 

This will save Hydraulics data to the database at specified
intervals.

/, "# $!%& '()*

Confidential


 
    

 

 $

 &
(
1. Start and configure Message Server.
2. Start ReadOpto and calibrate all sensors.
3. Create Tool Run in DSeries on 2of3 (offline
computer booted in Windows 95).
a. Select Units of Measurement
b. Enter Drillstring Components
c. Build Bottom Hole Assembly
d. Enter Correction Factors
e. Write MSS File
6. Start MSS on 1of3 (real-time computer booted in
NT).
a. Create Well and Hole - A default well and hole
are created automatically
b. Verify tool run data
c. Survey Setup - Enter directional corrections
d. Verify data acquisition program starts
e. Calibrate sensors
6. Follow the MWDecode Wizard through and set up
start the decode process.
7. From RtProc start the Depth Tracking and MWD
process.
8. Configure and start Hydraulics (if required).
a. Enter new annulus specs
b. Enter new drillstring specs.
c. Enter pump specs.
d. Enter Rheology and cuttings specs.
e. Start the Hydraulics process

  ! /,



 
     Confidential

 

 $

•Notes•

/,-
"# $!%& '()*
Confidential


 
    
  5



Chapter 5 covers day-to-day operating

procedures for MSS.

This chapter describes a quick look “how to” procedures

for many of the day-to-day tasks that you will perform with
MSS. It assumes a working knowledge of the system and
familiarity with the individual applications. For more
details on each application, refer to Chapter 3:
Applications and also to the online help which is available
for each application.
The format of the Operating Procedures section is
restricted to the menu bar items. It should be noted that in
many cases you can make use of the tool bar buttons. If you
are uncertain what a particular button does, simply move
the cursor over it, and a short description will usually
appear in a yellow box by the cursor and a slightly longer
description will appear in the status bar along the bottom
left hand side of the Main Window.

  ! 0,



 
     Confidential

 
$
 0)

5/ )
Start MsgSvr:

  
  *+, &

 &
%
Start MSS:

  
  *+, &

 &


• Click Finish on the Wizard Window, and OK on
the Summary Window to display the MSS Main
Window
• Verify tool run data


 
!
"
Double-click on MWD Tool Run and MWD Data, then
click on each item to verify.
• Verify directional corrections

% 
"
• Verify that all necessary processes monitored by
MSS have started (the box in front of each process
should be green checked)
Start Depth Tracking:

$  
$   $."
In the status bar, the DT indicator changes from red cross
in black box to green light.
Critical setpoints:
• Pump Pressure Cutoff: pump pressure must be
above this value to drill.
• In Slips Hookload: Hookload must be below this
value to recognize connections. And above this
value to track bit depth.
Start MWD processing:

$  
$  &1 
$"
0,- "# $!%& '()*
Confidential


 
    

 
$
 0)

In the status bar, the MWD indicator changes from red

cross in black box to green light
• Verify that all directional corrections (ACOR,
FCOR, Nominal GT/HT/Dip) are correct as
displayed in the SvyProc program.
Start the MWDecode process:
&1$
 <1>  $=  
&1$
 <1>
 $=  


- 
Start ReadSPM:

  
  *+, &

 
&
Start the hydraulics process:

$  
$  - $"

- $

  ! 0,.



 
     Confidential

 
$
 0)

 # /
In the event of a power loss to either SARA, HAZARA or
the P&F Rack, sensor calibrations should not be lost. The
one thing that should require attention in both systems is
the block height. When power is lost the number of counts
from the shaft encoder is also lost. Even though the
calibration is still intact the physical position is not known
and must be reset.

) $ / -
)1-.)

Start ReadOpto and under configuration select reset digital
counters.

  
  *+,&

  

Type in the exact block position and press . The

calibration table will be altered to make the current count
match the current height.

) $ / - 

Start P&F Setup and then press the [ESC] key, and the
following window should appear:
BLOCK HEIGHT SYSTEM
(Press ESC to reset I/O)
1. System Configuration Menu
2. Rig Data Menu
3. Shaft Encoder Calibration Menu
4. Other Sensors Calibration Menu
5. Operation/status Display
6. Real Time Sensor Display
7. Version
New Selection(1,2,3,4,5,6 Or 7):

0,/ "# $!%& '()*

Confidential


 
    

 
$
 0)

Type in the number 2 and the following will appear:

RIG DATA MENU
(Press ESC to exit menu)
Block Height Offset: 0.00 Ft
Count Set: 23498
Cable Diameter: 1.500 In
No. Of Sheave: 2
Length (Riser): 0.00 Ft
No. Of Sheave(Riser): 1
Press [ENTER] and the cursor will be at the count set
position. Enter the number of counts corresponding to the
current block position.

 ' )
To start a new run, first enter all the tool, calibration, and
bottom hole assembly information in DSeries. This would
normally be done on 2of3 but can also be done on 1of3
since DSeries is configured on 1of3 to access files on drive
L: (i.e., drive C: on 2of3).
Start DSeries:

  
  *+, &

 

Enter all the Drillstring Components for the new run, make
sure that you enter all the constants and factors for each
MWD tool component:

  : 


Build the MWD bottom hole assembly, selecting all the
correct components:

  5: 

 -
 #'
Enter any pertinent correction factors such as mud weight
and mud resistivity, etc.:

  4:
$
 $

Write out the MSS file for applications to access, selecting
the correct run (BHA) number, and entering the correct

  ! 0,0



 
     Confidential

 
$
 0)

hole size when prompted:


  ?: 1 &


Exit DSeries:

  @: 

0,1 "# $!%& '()*

Confidential


 
    

 
$
 0)

 
/
Make sure that RtProc is not currently running. Start MSS.

  
  *+, &

 &


The RtProc Wizard displays the Well/Hole setup window.
Enter a sidetrack name in the Hole: data entry field:
&

/ '2;
$
  -
/
After making a new entry in Hole, as soon as focus is lost
from the field (by tabbing out of it or by clicking outside of
it) a new database hole record is created and the Sidetrack
Hole Specification window is displayed. Either enter the
New Path name or preferably accept the default name
provided:
&

/
 $. -

$!$
  + /
Select the path from which the new sidetrack is being
kicked off from:
&

/
 $. -

$!$
 
 $.
!
 /
Enter the sidetrack Kick Off Measured Depth:
&

/
 $. -

$!$
  $. !! &:
/
Accept the entries and exit the Sidetrack Hole
Specification window:
&

/
 $. -

$!$
  
Complete MSS wizard start-up and press  on the
Summary screen to display the MSS and MWDecode
windows.
Start the Survey Editor program:

  
  *+, &


%  

Load the sidetrack hole survey data:

%  
    
  ! 0,



 
     Confidential

 
$
 0)

The Well & Paths window appears, highlight the sidetrack

well, accept the choice, and exit the window:
1 A   <   $. =  
If there is a new Tie on survey for the sidetrack then enter
it.

%  
     * )
Save the changes.

%  
   
%
Exit Survey Editor.

%  
    
  ) 
If a section of hole is re-logged with the MWD tool, the
data being recorded into the database must be assigned a
different relog number. This is so that MWD data covering
the same depth range can be correctly identified for
processing and plotting. It is important to change the relog
number at the correct time since this will avoid
unnecessary subsequent editing. After relogging a section
make sure that the relog number is returned to zero prior to
drilling new formation.
To change the relog number open the Relog Number
window:

$  &1  
 +'
Either type in directly or use the up and down scroll arrows
to select the correct relog number:

 +'  
 +'
Accept the entry and close the Relog Number Window:


0, "# $!%& '()*

Confidential


 
    

 
$
 0)

   $ -  )

A resistivity calculator is available in RtProc for
calculating downhole resistivities from either surface Rm
measurements of from fluid Chlorides content. Start the
Real-time Processing program.

  
  *+, &

 )

$
Start the Bottom Hole Resistivity Calculator:

$  &1  $ - 
Enter the measured depth:
$ 

 -
 %  &

Select either Surf Rm or Chlorides from the Calc BH Rm
from toggle button:
$ 

 -
 %  $ - 
!
/
Enter the chlorides (if from Chlorides selected) or Surface
Rm and Rm Surface temperature (if from Surf Rm
selected):
$ 

 -
 %  
 /


!$ / A 
!$ :/
Enter the bottom hole temperature:
$ 

 -
 %  

 -

:/
Calculate bottom hole resistivities by pressing the
Calculate BH Rm/Rmf button:
Exit the Calculate Bottom Hole resistivity window:
$ 

 -
 %  

  ! 0,



 
     Confidential

 
$
 0)

    

There is no direct Potassium calculator included in MSS,
however, there is a simple Excel spreadsheet which can be
used to calculate potassium concentration in % from
lbs/bbl, called Gamma%k.xls.
Start Excel:

  
  &$

! $
Open the Gamma%k spreadsheet:
&$

! $     B$/C&

$C8D.:E
Enter the pound per barrel concentration of either KCl,
KOH or K-Lignite, press [ENTER] and the K% will be
calculated.
Exit Microsoft Excel:
&$

! $    
 * 
The System conversion set is used by all applications,
except Mobn and WITS. The System Set should be
configured during initial setup from the first screen of the
MSS Wizard.

  
  *+, &

 7
Select either FPS or Metric units to use as the default
system set.
To make individual changes to the System set, then:
*+, &

 7 
%

With the System Set option button selected, highlight the
conversion ID that you want to change from the
Conversion Type scrolling menu:

$
%

 
%
 
Select the units to be used for the Conversion ID previously
0,
"# $!%& '()*
Confidential


 
    

 
$
 0)

selected:

$
%

  7
Select the number of decimals to be displayed:

$
%

  $ $
Accept Changes: OK.

   0<

Use the CDA Setup program to assign alternate
equipments. Start the CDA Setup program.

  
  *+, &

 #

Turn off the update of the spreadsheet.
#
   7  !!
To assign DAVG_ROP to ROP for example type
DAVG_ROP in the alternate column in the row containing
ROP.
#
   7  
/  :    ;
It is possible to view the various log files generated by the
MSS system from within RtProc by choosing the
appropriate item from the View menu, or by pressing one
of the four Log toolbar buttons.

  ! 0,



 
     Confidential

 
$
 0)

Table 5-1 Toolbar Buttons

Button Description

M indicates the MWD log (generated

by the MWD processing thread)
D indicates the Depth Tracking log
(generated by the Depth Tracking
thread)
A indicates the ADAM log
(generated by the MWDSERV
program)
E indicates the Error Log (generated
by all MSS applications)

The log file name is displayed at the top of the window.

The Close button removes the window. The log details are
displayed in the scrollable list box.

Note: The log display is not dynamic and does not

update as new entries are added to the log
file. It is necessary to close the listing and
re-open it to get an update.

You can choose to view errors from the entire system or

from any one application and can also order the list
ascending or descending (based on the time tag of the error
messages).

0  


Start the Survey Editor program to enter Tie-On surveys:

  
  *+, &


%  

Select the line that you want the Tie-On survey inserting
above by clicking in the right hand column cell: Survey

0,- "# $!%& '()*

Confidential


 
    

 
$
 0)

Editor (Select the line you want to insert above).

Insert a blank Tie-On survey line:

%  
     * )
A blank line will be inserted, fill in the Tie-On survey data
in the appropriate cells of the spreadsheet.
Save the changes:

%  
   
%
Exit Survey Editor:

%  
    

  ! 0,.



 
     Confidential

 
$
 0)

 

All decoded surveys are displayed in the Unposted Surveys
spreadsheet of the main Survey Processing window. You
must select which surveys are to be posted by clicking on
it. Note that all previous unposted surveys to the one
chosen will be removed from the spreadsheet. If more than
one survey is to be posted then you must post the shallower
survey first.
To post a survey select the survey by clicking on it with the
left mouse button:

% 
$  7

%
<$  % 
' 
 =
The Survey posting window appears. Confirm and/or edit
the Measured Depth, Inclination, and Azimuth fields.
Select Calculate Positional Data to recalculate the
positional data if required, e.g., if the survey data are
manually rounded to 1 decimal place.


%  $ 

 
Accept the data, record it to the database and exit the Post
Survey window.


%  

0,/ "# $!%& '()*

Confidential


 
    

 
$
 0)

0 

Start the Survey editor to edit a survey.

  
  *+, &


%  

Edit the survey by selecting the cell to edit and entering the
new survey data directly. The surveys will be re-calculated
after focus is moved to another cell.
Save the changes:

%  
   
%
Exit Survey Editor:

%  
    
 
 )
Start the Survey editor and choose Print Setup.

  
  *+, &


%  
 


Choose the required print format by selecting the check
boxes. Options include:
• Final Copy Prints FINAL COPY in the header
• Inclination Use 2 Decimal places Prints Inclination
using 2 decimal places
• Azimuth Use 2 decimal places Prints Azimuth
using 2 decimal places
• Print Plane Vsect Prints Plane rather than
Incremental Vertical Section

%  
    
Select whether to view/print only valid surveys or all
surveys.
Print the survey report.

  ! 0,0



 
     Confidential

 
$
 0)

  +  )

The release of MSS does not include its own daily
reporting package. The release CDs include the standard
Lafayette and Aberdeen Excel reports which should be
used for generating reports.

  )   

);/  
RLPlot is the plotting program based on the RigLink
software. The three biggest advantages are that there are no
files to delete, this program can be run from any computer
on the network (i.e., company man, rig floor monitors,
etc.), and there are many more options on how data is
presented.
First the RigLink Server program must be started, it should
be run on offline computer (2of3). This program must
remain running while RLPlot is in use:

  
  *+, ;.
% 
;.
A DOS shell and the RigLink Server screen will appear.
On the real-time computer (1of3), first make sure that
Message Server is running, then start CDAFeed:

  
  *+, &

 #
CDAFeed window will appear. Open the Properties
window:
#    

Enter the well name. Default is fine.
# 
  ;.
%  1
+
Input the IP address of the server. This will be the 2of3
computer in most cases 147.108.0.222. To change,

0,1 "# $!%& '()*

Confidential


 
    

 
$
 0)

highlight the address that appears and click the edit button.
# 
  ;.
%   
Note: It is important not to delete the last server
address. Edit this address, if the address is
deleted then the c:\inteq\res\ctl\mssrig.ctl
file will be corrupted and the CDA Feed
program will crash.

Enter minutes to pre-buffer, 5 minutes is a good choice.

# 
  ;.
%  &

'!!
Save this information by clicking OK.
# 
  ;.
%  
The items being transferred can also be edited. In most
cases the default will be sufficient. Go to the CDA items:
# 
  # *
Highlight the item to be edited or deleted and press the
appropriate button. Mnemonics can also be added by
clicking the Add button. The CDA Item Entry screen will
appear:
# 
  # *  #F *F

;
The mnemonics can be changed and the trigger can be
selected either a time interval, change in value or depth
interval. Then click OK to save.
# *   
The CDA Feed window will have the location of the
RigLink Server and the status of that server will be
connected in the CDAFeed window. The server on the
offline computer will also show the well name that was
entered.
Start RLPlot, this can be done from any MSS computer on

  ! 0,



 
     Confidential

 
$
 0)

the network:

  
  *+, &

 ;

Input the server address of the RigLink Server computer
(2of3), well name, choose time or depth log, buffer size
(200 feet), format file to run (c:\inteq\res\ctl\RLPlot\*.rlp),
and user name (this should be the computer that RLPlot is
running on) once all of this information is correct click
Apply.
The plot will appear.
To edit the plot formats, double click on the log itself. The
Edit FELog Format window will appear. Choose the track
etc. and the changes to be made and Apply.

0, "# $!%& '()*

Confidential


 
    

 
$
 0)

 +  +


Hard copy plots and MWD memory processing are all
done via DSeries, usually on the offline computer. It is
therefore necessary to transfer data from the INTEQ RES
database on the real-time computer (1of3) to the HPUTIL
directory on offline computer. Data can be transferred
using either of two programs, DbEdit, or MPSetup. DbEdit
transfer is a simplified method while MPSetup is for more
detailed custom transfer of data.

+#0 
Start DbEdit.

  
  *+, &

 '  

<' =
Open the DSeries transfer window.
'  
$  1 
 "
You are prompted to supply the path to the HPUTIL
directory, usually this will be D:\HPUTIL when working
on the online computer. Acknowledge the entry and close
the pop up window:
OK.
Select the run number to transfer from the Run Number
combo box.

  
$
   +'
If required, adjust the required time range, note that the
depth display field will not update until focus leaves the
From or To data fields.

  
$
  
/ 2 
/
Select the data type to transfer, (MWD/SURFACE DATA,
SURVEY DATA and/or TIME/DEPTH (SPOOL FILE)
DATA), by selecting the appropriate check boxes.

  ! 0,



 
     Confidential

 
$
 0)


  
$

 
$ 
0   
!
Select the append check box if the data is to be appended
to existing DSeries files, (note this option is only available
for MWD/SURFACE DATA at present).

  
$
  &1 2
7 # 
## #
Accept the data range selection and begin the data transfer.
OK.
A pop up window appears for each of the data types
selected showing the progress of the transfer. Completion
of data transfer is indicated when the pop up windows
close.



Start MPSetup.

  
  *+, &

 &

Select the Well that contains the required data from the
Well Identifier combo box.
&
  1 * !/
Select Hole that contains the required data from the Hole
Identifier combo box.
&
  -
 * !/
Select the data range from the Run Number, Relog No,
Start Date/Time, and End Date/Time data fields.
&
   +'/ ) 
 +
/ )
 2
/ )  2/
Select the data category(ies) to transfer from the Available
Categories scrolling list.

0,-
"# $!%& '()*
Confidential


 
    

 
$
 0)

Add the configuration to the MPSetup spreadsheet using

the Insert Top, Insert Bottom, Insert Before, or Insert After
Buttons.
&
  * 
 ) * 

 ) *
!
 ) * #!
Repeat the above steps until you have specified all the data
to be transferred.
If required, save the configuration, enter the name to use
for the configuration.
&
  +/
Save the configuration.
&
   
%
Transfer the files to DSeries, this is done in separate steps
for each of the data categories, (MWD/Surface data, Time-
Depth data and Survey data).
&
  
$  1 B&12
!$ ) )
 )
%E 

  ! 0,-



 
     Confidential

 
$
 0)

$/
 )
The Access database can slow down and perform poorly if
it has a considerable amount of data. On long wells it is
recommended to back up previous runs to the hard drive
and to a Zip disk and then delete them from the database.
Start the Backup and Restore program:

  
  *+, &

 $. 


A message will appear requesting if the directory
C:\INTEQ\res\data\backup_runs should be created.
$.  
  (
To backup the well to disk:
$.  
  '  $.
 
$ 1  $.
To backup the well to Zip:
$.  
  
  
$
" < (/C'$.G=
$.  
  '  $.
 
$ 1  $.
To delete an individual run:
$.  
  '  <$ 

 =   !
 '
To restore a run to the database:
$.  
  .  <$ 

 =  

When a run is deleted from the database it is necessary at
an appropriate time to compact the database to retrieve disk
space.

  &$

! !!$  &$

! #$$
Ensure that all applications are closed.

0,-- "# $!%& '()*

Confidential


 
    

 
$
 0)

&$

! #$$     ' 
$
Compact the Database.
&$

! #$$  

  ' 7 

$ '"
Select the RES database at
C:\INTEQ\res\database\access\res.mdb.
&$

! #$$ 
%
This will create a compacted database called db1.mdb.
Rename the file RES.mdb and then rename db1.mdb to
RES.mdb and restart MSS.

  ! 0,-.



 
     Confidential

 
$
 0)

 + $/
There is no difference between end of well backups and
regular backups performed during the well. Just follow the
procedures outlined previously for backing up data from
DSeries and MSS. Ensure that you have made backups of
all the data that will be deleted and most importantly that
you can read these backups. You might want to test the
integrity of the Zip files with the command pkunzip -t
y:\filename.zip. You should keep at least 2 copies of the
data.

+  4 +
Prior to removing data, double check that you have made
backups of all the data that will be deleted and that you can
read these backups.
To remove well data from DSeries at the completion of a
job, you need to run the batch file
c:\hputil\exe\cleanup.bat. This script will remove the
following:
\HPUTIL\BACKUP\*.*// Get Data Files
\HPUTIL\DSERIES\*.*// DSeries Backup Files
\HPUTIL\RUN??\*.* // Memory Dump Files
\HPUTIL\BINARY.* // Binary Files
\HPUTIL\*.fil // *.fil
\HPUTIL\xfer.* // Xfer Files
\HPUTIL\spool.* // Spool Files
\HPUTIL\*.eqp // DSeries Drill String Components
\HPUTIL\*.fac // DSeries Correction Factors
\HPUTIL\*.cfg // Header Files
\HPUTIL\*.ver // Verification Files
\HPUTIL\fwr*.* // Final Well Reports
To remove data from MSS at the completion of a job, you
need to run the batch file c:\inteq\res\cleanup.bat. This
script will copy the default database over the top of the
active database and remove all files from the
c:\inteq\res\data directory hierarchy. It will also optionally

0,-/ "# $!%& '()*

Confidential


 
    

 
$
 0)

run the DSeries cleanup batch file afterwards. If this is run

on Online it will call the cleanup script on the mounted
copy of DSeries on drive D: otherwise it will cleanup the
copy on drive C.
You must manually remove any files/directories below
C:\My Documents or wherever else the final well reports
were stored.

  ! 0,-0



 
     Confidential

 
$
 0)

•Notes•

0,-1 "# $!%& '()*

Confidential


 
    
 


("5

“Reghead.cfg” 3-321 BackRest 3-286
“Scale” 3-305 backup 2-23
“Time” 3-305 Backup Data 3-289
Baud Rate 3-242
6 BGGM 3-22, 3-112, 4-13
Bin 2-3
10BaseFL 1-45 Bingham 3-140
1of3 1-8, 2-1, 5-16, 5-19 BIOS 1-15
2of3 1-7, 2-1, 5-16 block height 2-23
3of3 2-2 Block Separation 4-7
4of3 2-2 Browse 1-25
Buckling 3-188
 Buckling Model 3-167

Advanced Properties 1-6 

Alternate 3-57
analog sensor 4-8 Calibration 4-2
Annulus 4-17 calibration switch 1-37
ARCnet 1-22, 1-45, 3-194 CDA 2-11, 3-37, 3-125, 3-127,
ARCnet card 1-32 3-151, 3-170, 3-245, 3-257, 4-2,
ARCnet node 1-32 5-11
ASCII 2-6, 3-253 CDAFeed 3-228, 5-16
ASCII configuration file 1-53 CDAFeed Tab 3-53
ASurvey 3-105 CDASetup 2-13, 3-54
ASurvey Mode 3-101 channel 1-39
ATCtl 3-91 channel A 1-39
ATDisp 3-95 checksum errors 3-204
AUI 1-50 chlorides 5-9
AUI LED 1-50 CID 3-57, 3-59
AUI port 1-48 Client 2-3, 4-1, 4-11
client computer 3-50
Client List 3-39

  !  
 ,



 
     Confidential

 

CMOS 1-20 +
collision 1-49
Collision LED 1-50 Fatigue Safety Factor 3-191
Combinatorial 3-68, 3-77 FELog 5-18
COMM 1 1-39 FFT 3-80, 3-86
COMM 2 1-39 fiber optic 1-22
Connection 2-21 Fiber Optic Hub 1-49
controller 3-194 FID 3-79
Correlate 3-70 Friction 3-157
crosstalk 1-45
ctl 2-11, 3-36, 3-54, 3-223, 3-267 8
Current View 3-103
Geolograph 4-7
ghost 1-5

Data 2-6 
Data Bits 3-242
Data Views 3-105 HAZARA 1-22, 1-27, 1-36, 4-2,
Database 2-6, 5-23 5-4
DB-9 1-29 helical buckling 3-168
DbEdit 3-264, 3-282, 5-19 Help 3-36, 3-123, 3-146, 3-227
DCI 1-2, 1-10 Hole cleaning 3-181
depth tracking 2-17 Hole Properties 3-8
Dlogger 2-10, 3-15, 3-147 hookload 3-134
DLS 3-95 HPUTIL 3-297
Documents 2-7 HT 1-37
DRAW 3-105 hydraulics 4-17
DrillByte 2-8
Drillstring 4-17 
DSeries 1-8, 1-35, 2-23, 3-18,
3-264, 3-276, 3-297, 4-10, 5-5, IDE 1-19
5-19 In Slips 2-21
Incremental FF method 3-157
indicator LEDs 1-33
 INTEQ_RTS 3-109
E/R jumper 1-31 IP address 1-7, 1-53, 3-231, 5-16
EC*Trak 3-112, 3-157
Edit Mode 3-58 0
encoder 4-3
Error Log 3-30, 3-144 KCl 5-10
Ethernet 1-43 kernel 1-29
K-Lignite 5-10

 
 ,- "# $!%& '()*
Confidential


 
    

 

KOH 5-10 MWDGraph 3-80

!
Label Applet 3-207 Network Options 3-51
LC 1-37 new hole 3-4
LEMO 1-36, 1-38, 1-40 new run 5-5
Log Listings 3-35 No Monitor 2-17
Log Options 3-51 NRZ 3-66, 3-73
logo files 2-3
'

Off Bottom 2-21
M4RTU 1-22, 1-27, 1-36, 4-6 OK 1-25
MagCorr Mode 3-101 Online Hydraulics 3-136
MD 3-111 Ontad 3-157, 3-175, 3-185
MDP 3-165 Open 1-25, 1-26
media converter 1-48 Options Tab 3-50
menu bar 3-222 Opto 3-15
Message Log 3-40 OPTO22 1-37
Message Server 3-99 OPTO22 kernel 1-22
Mnemonic 3-56 OptoControl 1-31
mnemonic 3-100 OptoTerm 1-25
Mnemonics 5-17 OptoTerm program 1-31
Mobil 3-15
Mobil Comms 3-253 
MOBM 3-253
Monitoring 3-30 P&F 3-198, 4-5, 5-4
MPLOT 3-298 Packet LED 1-50
MPSetup 3-298, 5-19, 5-21 Parity 3-242
MPT pulses 3-83 Parse Window 3-78
MsgServer 3-1, 3-178 Partition 1 1-7
MsgSvr 2-11, 3-39, 3-243, 4-1, Partition 2 1-7
5-2 path 3-5
MSS 3-99 PDriver 3-303
MSS Data Backup 2-22, 3-296 Peak Detection 3-70
MSS Wizard 4-11, 5-10 Performance 3-42
Mud Lubricity 3-181 Performance Tab 3-52
Mud Packets 3-138 ping 1-34, 1-48
MWD 3-14, 3-29, 5-8 Pod 1-38
MWDecode 3-62, 3-79, 3-99, polyphase filter 3-66
3-118, 4-15, 5-3 pop up 5-20

  !  
 ,.



 
      

 

Port Properties 3-240 serial line 3-194

Posted 3-105 serial port 3-203
Potassium 5-10 Server 2-3, 4-1
Power Law 3-140 Setup 3-1
Power LED 1-51 Sidetrack 5-7
PowerComms 1-38, 1-42 sidetrack 2-8
Processes Setup 3-16 splash screen 3-1
Pulse Width 3-68 spreadsheet 5-11
Pump Properties 3-11 Spy List 3-40
Pumps 4-17 ST bayonet 1-46
ST connectors 1-31
2 Star arrangement 1-44
status bar 3-222
RDD 3-100, 3-118 status LED 1-48
ReadOpto 3-193, 4-5, 4-19, 5-4 Status LEDs 1-50
ReadOpto program 1-35 Sticking Pipe 3-181
ReadPF 3-15, 3-197 Stop Bits 3-242
ReadSPM 5-3 strapping tape 4-3
ReadSpm 3-201 strategy 1-26, 1-29
Reaming 2-21 Stress Analysis 3-191
Receive (RX) 1-22 SUCOP 3-28, 3-100, 3-110
relog 5-8 SUCOP Mode 3-102
RES 3-157 SUIT 3-89
Res 2-3 Surface Logging 3-15
Rig Properties 3-10 survey 5-15
RigDisp 3-222 Survey Editor 5-7
RigLink 2-3, 3-230 SvyEdit 3-111
RIS-Info 3-303 SvyPrc 3-100, 3-101, 3-109,
RLPlot 3-205, 3-228, 5-16 3-118
ROD 3-88 SWWP 3-62
RPM sensor 1-36 SWWP/DAS 3-64
RtProc 2-10, 3-35, 3-64, 3-124, symb 2-7
3-204, 3-276, 4-15, 5-7, 5-11
Run Number 3-284 
RZ 3-65
threshold setting 3-67
( Tie-On 5-12
TMI 1-5, 1-10, 1-22
Sag 3-25, 4-14 Tmp 2-7
SARA 4-2, 5-4 toolbar 3-30
scandisk 1-10 torque sensor 1-37
Serial controllers 1-32 Trace 3-225

 
 ,/ "# $!%& '()*
Confidential


 
    

 

Trace Log 3-41 well name 4-10

track 3-216 Windows 95 1-8, 1-54
transceiver 1-48, 1-50 Windows NT 1-8, 1-55
Transmit (TX) 1-22 WITS 3-199, 3-237, 5-10
Tree Controls 3-288
B
&
X1 jumper 1-32
UFT 3-62, 4-15
Update Mode 3-58 C
UTP 1-44
Yes 1-27
= Yield Safety Factor 3-191

viscometer 3-140 <

 Zip 1-8, 2-22

Well FF method 3-158

  !  
 ,0