anax500core manual

ANAX 500 BSD Core Manual

To be a Worldwide leader in providing drilling and geological monitoring solutions to the oil andgas industry, by utilizing innovative technologies and delivering exceptional customer service.

Version 1.0 May 2006

Written by: Mark Pickell and Todd Parsons

BSD Software ManualI

© <2006> <Datalog Technology Inc.>

Table of Contents

Foreword 0

Part I WellWizard Software Manual 1

................................................................................................................................... 11 Server Software Installation and Configuration

................................................................................................................................... 12 The OpenBSD Operating System

.......................................................................................................................................................... 1So Why OpenBSD

.......................................................................................................................................................... 2BSD Differences per Hardware platform

......................................................................................................................................................... 2EDR/UBD Servers

......................................................................................................................................................... 2Mini-Server

.......................................................................................................................................................... 2For users of the QNX system

.......................................................................................................................................................... 3WellWizard Components

.......................................................................................................................................................... 5General BSD Commands

.......................................................................................................................................................... 8Important Commands

......................................................................................................................................................... 8Shell

......................................................................................................................................................... 9RAID

......................................................................................................................................................... 9Shutdown / Boot

......................................................................................................................................................... 10Single User Mode

......................................................................................................................................................... 11Lost Root Password

......................................................................................................................................................... 11DMESG

......................................................................................................................................................... 11Adding other users

......................................................................................................................................................... 11File Attributes

......................................................................................................................................... 12chmod

......................................................................................................................................... 12chown

......................................................................................................................................................... 12Apropos

......................................................................................................................................................... 13find

......................................................................................................................................................... 13nano

......................................................................................................................................................... 13mount

......................................................................................................................................... 13Mount USB Drives

......................................................................................................................................... 13Mount Drives for KERNEL updates

......................................................................................................................................................... 14top

................................................................................................................................... 143 The Mysql Database

................................................................................................................................... 144 WellWizard Control Panel

.......................................................................................................................................................... 15Initialization

................................................................................................................................... 155 Server Information

.......................................................................................................................................................... 16Server Type

.......................................................................................................................................................... 16Time Zone

.......................................................................................................................................................... 17Time & Date

.......................................................................................................................................................... 17Drill Floor Monitors 1 & 2

.......................................................................................................................................................... 17Horn Output

.......................................................................................................................................................... 17AC Failure Shutdown

.......................................................................................................................................................... 18Default Well template

.......................................................................................................................................................... 18Well Control Button

.......................................................................................................................................................... 18Well Configuration Password

.......................................................................................................................................................... 18Server Info Text Mode

................................................................................................................................... 196 Wells

.......................................................................................................................................................... 20Definitions

.......................................................................................................................................................... 21Create a New Well

IIContents

II


......................................................................................................................................................... 22Create a New Well - Text Mode

.......................................................................................................................................................... 22Enable Well Logging

......................................................................................................................................................... 23Enable Well Logging - Text Mode

.......................................................................................................................................................... 23Disable Well Logging

......................................................................................................................................................... 24Disable Well Logging - Text Mode

.......................................................................................................................................................... 24Stop Well

......................................................................................................................................................... 24Stop Well - Text Mode

.......................................................................................................................................................... 25Changing Well properties

.......................................................................................................................................................... 25TENSOR Configuration

......................................................................................................................................................... 26TENSOR configuration - Text Mode

.......................................................................................................................................................... 26Delete Well

......................................................................................................................................................... 27Delete Well - Text Mode

.......................................................................................................................................................... 27Rename Well

.......................................................................................................................................................... 28Well Templates

......................................................................................................................................................... 28Modifications to Default Templates

.......................................................................................................................................................... 29Archive

.......................................................................................................................................................... 30Restore

................................................................................................................................... 307 Users

.......................................................................................................................................................... 31Create New User

.......................................................................................................................................................... 32Clone User

.......................................................................................................................................................... 33Delete User

.......................................................................................................................................................... 34Well Permissions

................................................................................................................................... 368 WITS

.......................................................................................................................................................... 36How does Wits Work

.......................................................................................................................................................... 38Advanced Wits

.......................................................................................................................................................... 39Wits via TCP/IP

.......................................................................................................................................................... 42wits_diag

.......................................................................................................................................................... 43TroubleShooting Wits

......................................................................................................................................................... 43No WITS data is being sent or received

......................................................................................................................................................... 44Data has the wrong values

......................................................................................................................................................... 44How do I record the incoming data

......................................................................................................................................................... 44I have edited the wits file but nothing is working

................................................................................................................................... 449 Lags

.......................................................................................................................................................... 45Basic Requirements for lags

......................................................................................................................................................... 45Time-Based Lags

......................................................................................................................................................... 46Stroke Based Lags

......................................................................................................................................................... 47Air-Based

......................................................................................................................................................... 48Volume Based Lags

......................................................................................................................................................... 49Override Lags

.......................................................................................................................................................... 49Trigger Lag

......................................................................................................................................................... 50GasLag

......................................................................................................................................................... 52Mudlag

.......................................................................................................................................................... 52Troubleshooting Trigger_lag

......................................................................................................................................................... 52Everything has been overwritten with a straight line

......................................................................................................................................................... 52My Lag is Ok, but my Gas value is lower than it should be

......................................................................................................................................................... 52I'm Not Receiving my Lags

.......................................................................................................................................................... 52Check that the lag is Working

................................................................................................................................... 5210 Creating Channels

.......................................................................................................................................................... 53WWtext

.......................................................................................................................................................... 54Adding a new channel or editing an exiting channel

................................................................................................................................... 5711 Sensor Configuration

.......................................................................................................................................................... 57Hardware Calibration Procedures

BSD Software ManualIII


.......................................................................................................................................................... 58Channel Calibration

......................................................................................................................................................... 59Channel Mapping

......................................................................................................................................................... 63Channel Calibration Analog

......................................................................................................................................... 65Example Calibration - DeLaval Pit Volume Sensor

......................................................................................................................................................... 66Channel Calibration Digital

......................................................................................................................................................... 67Set Function Calibrations

......................................................................................................................................... 69Example Calibration - Block Movement

.......................................................................................................................................................... 69Channel Configuration

.......................................................................................................................................................... 70Calibration Log

.......................................................................................................................................................... 70Depth and Weight Calibrations

.......................................................................................................................................................... 71Weight On Bit

................................................................................................................................... 7212 Mirroring

.......................................................................................................................................................... 72What is a Mirror

.......................................................................................................................................................... 73Mirror Configuration

.......................................................................................................................................................... 73Wellsite Server Setup

.......................................................................................................................................................... 74Mirror Server Setup

.......................................................................................................................................................... 75Starting the Link

................................................................................................................................... 7613 Interface

.......................................................................................................................................................... 76Requirements

.......................................................................................................................................................... 76Command to Start Interface

.......................................................................................................................................................... 77Mapping Channels between QLOG and WellWizard

.......................................................................................................................................................... 78Troubleshooting

................................................................................................................................... 8014 WellWizard Client Software Installation

.......................................................................................................................................................... 80Modifying WellWizard from Default to Driller's Terminal

.......................................................................................................................................................... 80EDR Version Client

................................................................................................................................... 8115 Security

Part II Advanced Commands 82

................................................................................................................................... 821 client_tcp

.......................................................................................................................................................... 82Time and Depth Queries

.......................................................................................................................................................... 83Realtime Viewing

.......................................................................................................................................................... 83Setting Variables

................................................................................................................................... 832 WWpad

................................................................................................................................... 843 WWsim

................................................................................................................................... 854 Registry

.......................................................................................................................................................... 86Example usage of Registry

Part III Networking 88

................................................................................................................................... 881 Terminology

................................................................................................................................... 902 BSD Networking

.......................................................................................................................................................... 90Setting IP

.......................................................................................................................................................... 90Setting Gateway

.......................................................................................................................................................... 90netstat

.......................................................................................................................................................... 91ifconfig

.......................................................................................................................................................... 92route

................................................................................................................................... 933 Secure Telnet / Putty

.......................................................................................................................................................... 95SSH

.......................................................................................................................................................... 95.ssh

................................................................................................................................... 964 Secure FTP / WinSCP

IVContents

IV


.......................................................................................................................................................... 98SCP

.......................................................................................................................................................... 98.ssh

................................................................................................................................... 995 Test Network Connections with Ping

................................................................................................................................... 996 Test to Isolate Network

................................................................................................................................... 997 No Network Communication

Part IV APPENDIX 101

................................................................................................................................... 1011 Standard Units

................................................................................................................................... 1012 Parameter Definitions

................................................................................................................................... 1033 nano

................................................................................................................................... 1084 Wits records

Index 0

BSD Software Manual1


1 WellWizard Software Manual

This section covers all software aspects of the WellWizard server. This includes:

Software calibration of sensorsSoftware mapping of sensorsAll aspects of Well and User control

1.1 Server Software Installation and Configuration

The WellWizard server software is used to support many different hardware and software variationsand thus it is very important that the server is correctly configured prior to first usage. After initialconfiguration is complete the only requirement in configuration is Enabling and Disabling differentWells as required. Configuring the Server for first time usage is done through the WellWizard ControlPanel. The Server Information should be configured first.

Other consideration to be made is do you have existing templates that should be brought in to bemade the defaults. The EDR template by default is fairly inclusive but every job has various items thatrequire tweaking or configuration such as sensor calibration or software channels added or wits fileconfigurations. If any of these items is modified and a new well is created the modifications won't bebrought over from well to well. If you do have existing templates you wish to bring over or create thiswill need to be done on the server side and should be done prior to Enabling a new well. Forinstructions on how to copy out default templates please refer to Modifications to Default Templates.

After you have enabled your well to logging you will want to connect to it with your client which can beobtained by following the instructions in the section WellWizard Client Software Installationandconnecting using the login and password as defined in the section Users. Once connected you canfollow the instructions in Software Calibration Section to add and configure your hardware sensors.

Please refer to the WellWizard User manual for details on how to use the WellWizard client and itsvarious operations.

1.2 The OpenBSD Operating System

The old manual had tons of pages describing everything under the sun about the QNX4 operatingsystem. I have opted to not include all that information here as it is readily available fromhttp://www.openbsd.org. I suggest reading the About OpenBSD section and the OpenBSD Resourcesections. Any question you may have or plain curiosity can be answered there. Also there is a largeonline community with tons of posts that you can search through for specific questions or problemsyou may be having. And as always Datalog Head Office can be utilized as we have a long experiencewith the OpenBSD platform.

1.2.1 So Why OpenBSD

The OpenBSD platform has proven itself to be an extremely secure and stable operating system --both attributes required for the collection of extremely sensitive wellsite data. The Head Office hasbeen using OpenBSD for some time now in various roles

· As the corporate website· Corporate Email· Firewall protection· Chromat GasWizard· Depth Processing Unit· All IDS mirrors· Now all wellsite ops.

WellWizard Software Manual 2


By bringing all our operations under one Operating System all users can move from one application tothe other without a learning curve and development can concentrate on one overall operating system

1.2.2 BSD Differences per Hardware platform

1.2.2.1 EDR/UBD Servers

Converting a Mini-Wizard from a QNX system to OpenBSD system requires the following BIOSchanges:

HARD Drive 0 - should be set to auto physical LBA. Com 3 - set to IRQ 10Com 4- set to IRQ 11LPT - set to IRQ 7ETHERNET - set to IRQ 9

1.2.2.2 Mini-Server

Converting a Mini-Wizard from a QNX system to OpenBSD system requires the following BIOSchanges:

HARD Drive 0 - should be set to auto physical LBA. Com 3 - set to IRQ 10Com 4- set to IRQ 11LPT - set to IRQ 7ETHERNET - set to IRQ 9

1.2.3 For users of the QNX system

The migration from QNX to BSD has been designed to be as painless as possible but not everythingcould stay the same. In point form some of the more major changes that you need to be aware of:

· pico is no longer available, use nano -- same structure· dac_sw,dac_hw are all gone and all sensor configs are now stored in /ww/well/UWID/config/well.cfg· databases are now stored in mysql at /ww/db/wwdata. No independent databases (no size limitation

either)· WWdac_rtd5408 is now WWdac· qtalk is no longer available, all terminal control is now through wits_diag· telnet/ftp are being phased out, now use scp,ssh,PuTTy and WinSCP· chkfsys in longer required, system is self checking on startup· dual drives now running in raid 1 software (mirror)· /etc/hosts is now replaced by wwnet.conf· /etc/netstart is now replaced by mygate· wwmon is a new program monitoring for failure of the database· boot -s (single user mode) giving more options on startup· ps ax instead of sin (fi)· pkill instead of slay· wwmysql now part of shut down procedure (manual)· reboot now works for reboots.

BIGGEST CHANGE -- Do not update your systems with any new



updates unless instructed to do so. The BSD system uses the Kernelfile (/bsd) which is paired with the software and must be updatedtogether. Updating files without checking on the kernel can causedisastrous effects. Also please note that you can't just update /bsd aswe now have two drives running raid 1 which need to be updatedindependently.

1.2.4 WellWizard Components

WWcpu - controls a digital I/O card.- used to control the operation of the hardware (keyswitch, power control board,heartbeat light).- controls the horn, based on commands from "engine".- controls the digital output pulses, based on commands from "WWpulser".- during shutdown, it orders the OS to stop, and then kills the CPU power.

WWos - monitors the operations of the entire WW system.- detects if a process is killed or dies and restarts that process.- must be running before attempting to start WW

WWengine WellWizard Well Data Dissemination EngineThis program is used to calculate and disseminate data for the specified Well. It isactually two programs in one - the ENGINE program and the IO program. These twopieces work together to provide access to well data in an efficient, prioritized manner. - Trigger for lagging data is also handled by the WWengine program.- two copies run simultaneously.- "engine" gathers data from all sources, performs calculations.- "I/O" is the interface between the system and the mysql database server.- "engine" distributes data to requesting local processes

WWtcpip WellWizard TCP/IP ServerThis program handles communication between Windows clients and the server.

- handles communication, with remote clients, via TCPIP.- listens on port 4999 for connection requests.- handles requests from clients for configurations, realtime and database data.- provides the only data path from client to server.

WWdac WellWizard DAM/DACDriver file for Data Acquisition cards in both Merlin and EDR.

- hardware data acquisition controller and processor.- splits into two copies- higher priority process communicates with the RTD5408 acquisition board, withprocessing occurring 1000 times per second.- lower priority process performs calculations and passes them to the "engine", withprocessing occurring once per second.



WWwits WellWizard WITS ProgramThis program is used to send and/or receive WITS data.- WITS controller- sends data to "engine" once per second for calculations.- receives data from "engine" once per second for distribution to external systems.- one process can control several serial ports.

WWdown Well Wizard Shutdown programThis program is used to shutdown the logging functions on the WellWizardsystem. It does not stop any of the underlining OpenBSD structure or the baseWellWizard system. Items such as WWreg are left running so you can continue to work with yourwells.

WWboot This shell script is used to boot a WW server. Starts up the wells and theappropriate programs associated with each

WWtext WellWizard Channel Manager Command used to add channels, change categories, hide/unhide set alarmsstatus etc.

WWconfig WellWizard ConfigThis program is the configuration server. It listens to requestsfrom WellWizard clients that have the ability to configure the server.

WWdac_sim WellWizard DAC Simulator Simulation program used by demo wells to create a fake well

WWdbm Well Wizard Well Database Manager program This program is used to backup and restore entire wells in a proprietary format. The wells may then be restored in another WellWizard server stored for futureusage.

WWhart WellWizard HART protocol data acquisition manager. Used in UBD wells

WWinterface QLOG-to-WellWizard Interface Program

WWreload WellWizard Reload Utility Use this program to reload certain supported configuration file instead ofrestarting programs. Typically, this program is invoked from the command line bysimply running the command specifying the file to reload as a command lineargument.

WWlink WW <-> WW Link ManagerThis program establishes connections to remote systems to perform datareplication (aka Mirroring). Both batch and live updates are handled. NOTE: The WWlinkup program is used in conjunction with this program to trigger ascheduled update to/from a remote system.



WWlinkup WellWizard Server Linkup Use to initiate connection between two WellWizard servers for data mirroring. The registry settings for a well will determine how and when this connectiontakes place.

WWpassword WellWizard Administrator Password ProgramThis program is used to display the WellWizard administrator password that isused to calibrate, configure, and manage the system password that is requiredfrom Client to access configurations.

WWreg WellWizard Registry Manager Used to edit the registry. STAY OUT OF REG. Must be running to see wells.

WWtestlink Wellwizard to Mirror test program Used to test link status between two servers.

WWtensor The daemon for Tensor tools.Used in conjunction with WWtensorc to listen and accept input from tensor tools.

WWtensorc WWtensor configuration tool. Used to setup up offsets and incoming ports for tensor data.

wwmon This program monitors for the mysql database and if not present will reboot theserver in an effort to repair itself.

wwmysql down Takes the mysql server down

wwmysql boot Starts up the mysql database server

1.2.5 General BSD Commands

To use OpenBSD commands you must open a PuTTY session to the server. (Note that Telnet stilldoes work but as a good general practice don't use it)

All OpenBSD commands are stored on the system drive in the /bin directory. BSD uses the forwardslash (/) as a directory separator (opposite to the DOS (\) backslash), with / representing the rootdirectory.

BSD is case sensitive. Lower case is predominant for BSD commands with third party executablesoften comprised of mixed or all upper case letters.

To find out how to use a BSD command, type man command where command is the executable youare seeking full usage instruction for. All usage dictates that you use spaces between the commandand each of its subsequent parameters. Here are some typical examples:

·Listing files



ls

ls dac*

ls –l (lowercase L)

ls –D

List all files in the current directoryList all files beginning with dac in the current dirList all files in long formatLists only directories

· Copying filescp al.txt al.txt.bak

cp *.txt * .txt.bak

cp –cvpRO

Copy file al.txt to al.txt.bak (al.txt still exists)Copy all files with a txt extension to files with a txt.bak extensionCopy recursive directories plus links

·Moving files (can use like rename)mv al.txt al.txt.bak

mv dbms dbms.old

Move al.txt to al.txt.bak (al.txt no longer exists)Move the directory dbms to dbms.old (dbms folder no longer exists)

·Make directory (actually a sub directory)mkdir dbms

mkdir myfiles

Make a new dbms sub directory in the current directoryMake a new directory called myfiles in the current directory

·Using the Output Pipe (vertical bar | )ls | less lists the output through the more utility.

Use the spacebar to view each screen of output

·Display running tasksps ax

ps ax |grep WW

ps ax |grep h

ps ax |less

Display all running tasksFilter list of tasks to those starting with WW piped through grep utilityFilter list of tasks to those starting with h piped through grep utilityList running tasks - only so many per page

·Find text stringgrep send wits

grep recv *

Find all occurrences of send in the wits fileFind all occurrences of recv in any file in the current directory

·Redirection symbol >cat /dev/ser1 > /tmp/filetxt

client_tcp -cdata_test -d"1DMEA" > /tmp/output.txt

Redirect output from serial port 1 to /tmp/file.txtRedirect output from the client_tcp program to /tmp/output.txt



·List the last "n" lines of a text filetail –50 witstail –500 dump.log

tail –500 dump.log >mydump.txttail -f /ww/debug/..ww..

List the last 50 lines of wits to the screenList last 500 lines of dump.log to screen or…. ……redirect to mydump.txtAs data is written to /ww/debug/..ww.. it will update on your screen

·Permanently delete a file (very powerful - use with caution)rm al.txt

rm *.bak

rm –r data*

Delete al.txtDelete all files in the current directory with a bak extensionremove all files AND directories starting with letters "data"

·Stop/end running taskspkill WWwits

pkill –9 WWdac

Some of the common pkillsignal options;1 HUP Hangup2 INT Interrupt9 KILL Non-ignorable kill

Stop the WWwits task; and restarts itStop all running copies of the given task permanently

·BSD editor (nano)nano wits

nano dac_sw.txt

Edit the wits fileEdit the named txt file

NOTES on the use of nano keys:Ctrl-F Ctrl-B Ctrl-N Ctrl-P Ctrl-Backspace Ctrl-H

Moves cursor forward one characterMoves cursor backward one characterMoves cursor to the next lineMoves cursor to the previous lineBackspaceBackspace

Remember man nano for more assistance.

NOTE: This editor does NOT support a mouse. The delete key works like the backspace key.

·BSD file compression utility (tar - zip utility)tar –zcvf al.tgz *tar –zxvf al.tgztar –ztvf al.tgz

Compress (zip) the current directory into a single file - al.tgz Extract the contents of /al.tgz into current directory.List the contents of the file al.tgz



NOTES:

The switches copy all files in all subdirectories while preserving symbolic links, user privileges, and fileproperties.

The only switch parameter that varies between the compress and extract functionality is the secondone in the list: c for compress and x for extract.

Table of Dos Commands vs. BSD commands.DOS Command BSD Command

display list of files

display contents of file display file with pauses copy file find string in file

compare files rename file delete file delete directory change file protection create directory change working directory line editorget help display date and time display free disk space backup or winzip styleprint file display print queue

dir/w dirtypetype filename | morecopyfind

comprename OR renerase OR delrmdir OR rdattribmkdir OR md chdir OR cdedithelpdate, timechkdskbackupprint print

lsls -l or lcat or lesslesscpgrepfgrepdiffmvrmrmdir or rm -Rchmodmkdircdnanousedatedftarlprlpq

Commands located in /bin - part of the BSD build – not WellWizard specific

1.2.6 Important Commands

Beyond the General Commands that are used on a regular basis there are many commands that canbe used for other purposes. These commands are not meant for the General User but for theTechnical User. Please do not use any of these commands without Tech Consent. As with allcommands do a "man command" in order to get a better understanding or other options available.

1.2.6.1 Shell

When you login into your server you are working in the KORN shell. This shell is the default for BSDsystems and has some limitations that will eventually drive you nuts. You will probably and I suggestthat upon logging in type "sh"

sh - the public domain Bourne Shell.

This shell has the advantage of allowing you to backspace or use up/down arrows to bring up previouscommands. It is also the shell that allows for most advanced commands to work.



1.2.6.2 RAID

The BSD system is designed to run with two drives in a raid 1 (mirror) configuration. If only one driveis present the system will disable the raid functions.

If the system does have two drives they must be the same size. If the system is taken out of sync forany reasons the system will need to be rebuilt and this will occur automatically.

To check the status of the raid type:

raidctl -s raid0

A system that is clean (or in sync) will return:

If the parity status returns as Dirty then the system will start to rebuid itself.

To view the rebuild status realtime go to a sh shell and type :

while sleep 5; do raidctl -s raid0; done

During the rebuild process particularly from 0-2% rebuild the system will not respond to WellWizardcommands as during this time the WellWizard regsitry is being rebuilt.

If a drive does fail it is recommended to backup all data from the still running drive and swap out bothdrives when time allows.

NOTE: Never reboot the system while the raid is rebuilding. Theraid takes about 32 seconds per GB -- be patient. The system willcontinue to collect data and function during this time, though itmay be a bit slow backside.

1.2.6.3 Shutdown / Boot

When the system is started up the /etc/rc file fires up first the mysql database and then the mainWellWizard system. If firing up manually the process is :

1. fire up mysql -- wwmysql boot2. fire up WW system -- WWboot

To take the system down completely

1. Take down main WW system -- WWdown2. Take down remaining WW system -- pkill WWsys WWtdm WWtran WWuser WWreg WWcpu3. Take down mysql -- wwmysql down

Generally the system never needs to be taken down completely and a WWdown is normally all that is



required.

1.2.6.4 Single User Mode

Single User Mode allows users to access the system without starting up any of the normal processes. This includes all WellWizard processes and network. This must be done with a keyboard and monitorattached. When the boot> option appears type in boot -s and hit <enter>

BSD will go through it's normal boot-up sequence and rather than issue you a login it asks you for thepathname of shell. Hit <enter> here.

Terminal Type: Choose vt220 at this pointYou are then given the command line and you can move around the system. At this point you are in



read-only mode. To make any changes to the system you must first mount the system and then youare free to make changes.

mount /

1.2.6.5 Lost Root Password

Losing the ROOT Password is not a good thing -- as all access is via ROOT. If this occurs you mustboot into single user mode. Mount the drive as instructed and then type "passwd". This will allow youto change the password for the Root user. Once finished type reboot.

1.2.6.6 DMESG

dmesg displays the contents of the system message buffer. It is most commonly used to reviewsystem startup messages.

dmesg | less or dmesg > file.txt

dmesg is an important file that contains all the startup information that can be used to troubleshootproblems. The contents of this file are the same thing you would see if booting up with a monitorattached. It shows what network cards were found, serial devices, and harddrives. If something isamiss you can always refer to dmesg to see what happened on startup.

1.2.6.7 Adding other users

You can always add other users to the system other than root by using:

adduser

Adduser will take you through the questions required and will setup a new user. This is similiar to whathas been done on the main servers. If you make the user a part of the group wheel they can they loginin as themselves and the do a "su" (superuser) to the root user. This is considered the proper methodof connecting to a criticial server.

Please note that if you do add other users they will not be able to login into the WellWizard system untilyou do the following as root:

cd /etcchmod 775 ..

1.2.6.8 File Attributes

All files on the BSD system are assigned an owner, a group and then general users. These are thenbroken down into read,write and execute.

As an example /ww contains the following directories: (do an ls -l)

drwxrwx--- 2 ww ww 512 Oct 2 2000 defaultdrw-r----- 4 root ww 512 Dec 15 13:00 ll

The d signifies directory.r=readw=writex=execute

So for the directory default the owner is user "ww" and this user has read,write and execute. Thegroup is group "ww" which also has read,write, and execute. All other uses have no read,write or



execute ability.The directory ll is owned by user "root" and this user can read or write to the file but not execute. Group "ww" can only read and no one else can do anything.

The other contents shown by "ls -l" show number of blocks used by this directory (2), block size (512)and date of creation (no year indicates current)

The command "chmod" and "chown" control these file attributes.

1.2.6.8.1 chmod

chmod - Change mode

usage: chmod 777 file

The value 777 in the example above would give read,write and execute to owner,group and users. Todetermine the value that should be used follow the table below.

Each number is based on a binary value going from 0 to 7.

--- (000) 0 no permissions at all--x (001) 1 execute permission-w- (010) 2 write permission-wx (011) 3 write/executer-- (100) 4 read permissionr-x (101) 5 read/executerw- (110) 6 read/writerwx (111) 7 read/write/execute

A value of 640 would give owner read/write, group read only and everyone else nothing.

1.2.6.8.2 chown

chown controls who is the user and/or group assigned to a file.

usage: chown owner:group fileusage: chown owner file

You can set either the owner or both owner and group at one time. If I were to send you a file calledfile.txt that I created as user root and you wanted to change it's ownership to ww so it coud be run byWellWizard you would type:

chown ww:ww file.txt

This would change both the owner and group to ww.

(chgrp can change the group independently)

1.2.6.9 Apropos

apropos shows which manual pages contain instances of any of the given keyword(s) in their title line. (taken from man)

usage: apropos tdm (you remember tdm, but not the command)



This command returns all man pages containing the content tdm. Useful if you can't remember anexact command but you remember what it does.

1.2.6.10 find

To find a file you must be in the sh shell.

man find

find . -name filename

Take note that their is a period between find and -name.

1.2.6.11 nano

Text Editor -- see appendix nano

1.2.6.12 mount

UNIX systems require you to mount devices to a directory in order for you to access them. BSD givesus many options in this area.

1.2.6.12.1 Mount USB Drives

To mount a USB 2.0 device (memory stick)

ssh into your systemInsert stick into system:You should now see several lines of code appear, the line of interest will look like:

sd0: 248MB, 248 cyl, 64 head, 32 sec, 512 bytes/sec, 507904 sec total

If you do not see this line then your stick will not work.

"mkdir /mnt/usb" (creating mount point)"mount -t msdos /dev/sd0i /mnt/usb"

Now you can "cd /mnt/usb" and copy files in and out.

When finished leave the /mnt/usb directory (cd to anywhere) and type "umount /mnt/usb". Itis best to umount these drives prior to pulling them out as Unix systems often will buffer datathat should be written, so pulling out may give you incomplete data.

1.2.6.12.2 Mount Drives for KERNEL updates

To mount your harddrives to change BSD kernel (for update)

mkdir /mnt/wdmount /dev/wd0a /mnt/wd(do your thing)



umount /mnt/wdmount /dev/wd1a /mnt/wd(do your thing)umount /mnt/wd

1.2.6.13 top

The top command is used to display and update information about the current CPU processes. It isonly used for troubleshooting purposes.

Basic command is:

top -s1 -osize --- this will update the list every second and show the largest users of CPU time atthe top of the list.

Processes from time to time will use upwards of a 100% CPU but these will never last longer than afew seconds and any process using upwards of a 100% for a long period of time has essentially lost itsmind and will need to be reset.

1.3 The Mysql Database

The BSD WellWizard system uses the mysql database to store all time and depth data files. Unlikethe previous system which stored the files in a SyBase database in the /ww/well/UWID/data directoriesthe database is now stored in a file called /ww/db/data/wwdata. This file contains both time and depthfor all wells on the system. Unlike the previous system each well on the system is stored in the samedatabase. This causes some difference in operation.

· WWdbm will be a bit slower as the data needs to be extracted and compressed whereas the oldsystem was already independent and compressed.

· All wells on a system are stored together.· File limitiations are removed and issues with 2GB database size or no longer relevant, so we can

record at 1sec time interval if required.

In order to ensure that the database is up and running prior to the rest of the system (see shutdown/boot) a process called "wwmon" monitors the status of the mysql daemon. If the mysqldaemon is not present or fails the wwmon program will reboot the system in an effort to startup theauto-correction that occurs on boot-up. If this fails again the system will keep rebooting over and overagain. To get out of this cycle the user must boot into single user mode and mount / the drive andnano /etc/rc and # (pound) out the wwmon references. Rebooting after this will allow the system tocome up without wwmon rebooting it. If any of this occurs I would suggest contacting Datalog for helpfrom a senior Technician. Under normal operations this should never occur but we have seen systemsthat the processer has failed (fans failed) and this caused an spiralling system death. Under thesecircumstances the database needed to be rebuilt and fired up manually before it was functional again. On my test server I have improperly pulled the AC well over a 100 times during the writing of thismanual and not once did I have a database failure. So I only raise this issue as it has occurred,though I doubt we will see it very often.

To backup your database the WWdbm command is still the best choice.

1.4 WellWizard Control Panel

The WellWizard Control Panel is the Datalog GUI (Graphical User Interface) to assist wellsite users inthe configuration of their Datalog system without having to access OpenBSD command lines. Many ofthe functions are now available in the WWCP but many are still in the process of being ported over.



As the process are ported over I will update this manual for that particular section.

1.4.1 Initialization

· Install WellWizard Server software version 5.1 or newer into the system. This can be done by eitherinstalling a hard disk drive supplied by Datalog that contains the software or by a software patch asrequired.

· Power up the server using the power button or key switch, as appropriate.· For EDR/UBD Systems or Mini-Servers, wait for the external LED (heart beat) to start flashing

before proceeding.· Double click Internet Explorer icon.· If you are accessing the WellWizard Control Panel interface from the default Datalog wellsite

network, in the web browser type: http://207.216.230.180 and hit enter.· The Datalog page will open.· If you are using the WellWizard Control Panel for the first time and you do not have a Java 2

Runtime installed on your system, click on the Download Java 2 Runtime hyperlink in the webbrowser, save the file to your local hard drive then, once the file is downloaded, click on Open andfollow the installation instructions.

· After you have installed the Java 2 Runtime on your system, go back to the web page.· Click on the WWCP hyperlink.· The first time you enter you will be asked to trust the software, to continue, Click start.· In the user box type admin.· In the password box type admin.· Click OK.· The system will prompt you to change the password.· Type your new password.· Confirm the new password.· Click OK.

The system currently can only support English. If your system is not setup as English default or doesnot include English in your browser settings it will fail.

1.5 Server Information

To setup up the Server parameters please use the WellWizard Control Panel where possible. Thisoperation can also be accomplished on the server side in text mode and the instructions anddefinitions for each choice remain the same but method is slightly different. Please refer to the section- Server Info Text Mode for detailed instructions.

A Server Information display panel is displayed, under this panel is a series of server parameters aredesigned to setup your server for your unique well.



After configuring each of the following parameters click Apply. Server Type Time Zone Time & Date Drill Floor Monitors 1 & 2 Horn OutputAC Failure ShutdownDefault Well templateWell Control ButtonWell Configuration Password

1.5.1 Server Type

Click the down arrow to the right, a drop down list of server types will appear. Select the server typeyou are using.

· WW Server System - This option is for all EDR/UBD systems· WW Mini-Wizard System – this is the blue box systems, or the suitcase style Mini-Server.· Other (PC/Desktop/Laptop/...) – this option is for any system you install WellWizard into that does

not have Datalog's proprietary power-control hardware.

1.5.2 Time Zone

Choose the server's Time Zone by clicking on the down arrow on the right, scrolling through the list,and making the appropriate selection. Once the server information has been applied, the selectedTime Zone will be used by the server and all wells create after the Time Zone was set. Note that eachwell has its own Time Zone setting which is inherited from the server at the time that the well iscreated. To change the Time Zone setting for an existing well, the change must be done in the well's



properties page.

&Note: Changing the time zone will have no effect on server operation. Any WITS data being sent outby the server, however, will have its timestamp updated accordingly.

IMPORTANT: Any WellWizard Clients connected to the server when the time zone is changed willneed to be restarted to get the new time zone information.

1.5.3 Time & Date

The date and time should be set to the correct information for the selected time zone. Selecting eachtime field with the mouse and clicking on the up/down arrows will adjust each value accordingly. Additionally, once a field is selected, the up, down, right, and left arrow keys can be used to adjustvalues and switch fields.

WARNING: The WellWizard Server stores time-based records using the current date and time. Consequently, if the server's time is adjusted forward, large gaps will appear in the time-based datarecords. Conversely, if the server's time is adjusted backwards, time-based records may beoverwritten thus causing data-loss. To help prevent these types of problems, the time and date mayonly be modified if there are no wells currently logging data. It is also recommended that the date andtime be checked and any corrections made prior to commencing well logging.

1.5.4 Drill Floor Monitors 1 & 2

If the WellWizard Server is supplying power for Drill Floor Monitors, enter the numeric IP address ofeach monitor into the respective edit box. The server will use this information to coordinate theshutdown of the Drill Floor Monitor(s) in the event that the rig losses power. For the default Datalogwellsite network, the default IP address of Drill Floor Monitor 1 is 207.216.230.78. Drill Floor Monitor 2is at IP address 207.216.230.179 by default. If not using Drill Floor Monitors or if the Drill FloorMonitors are not powered by the WellWizard Server, the IP addresses should be cleared.

PLEASE NOTE: The EDR/UBD server is capable of powering up one DFM only at this time. It isrecommended that any secondary Drill Floor Monitors be AC models or DC models with an external powersupply.

1.5.5 Horn Output

Click the down arrow to the right, and choose a horn output. · None indicates the alarm horn WILL NOT sound a WellWizard External Alarm.· Default Horn indicates the alarm horn WILL sound on the WW Server System or WW Mini-Wizard

system.

In addition to the above, there are also Serial Port and Parallel Port horn output selections. Theseselection required that special hardware be connected to the server and typically only used by theANAX systems. Anax systems use the serial port to tie to the ANAX DAU to fire the external horn.

IMPORTANT: The horn will only sound when the following conditions are met: a) the horn output isnot 'None', b) there is a Drill Floor Monitor connected to the server and, c) an alarm threshold on theDrill Floor Monitor is triggered.

1.5.6 AC Failure Shutdown

Click the down arrow to the right and select normal or immediate shut down.

· Normal shutdown is the default and should be used in most cases. Normal refers to the process



that the system will go through when AC power is lost. In Normal mode, the server will continuerunning until the battery starts to run out of power. At that point, the server will automaticallyshutdown to prevent database corruption.

· Immediate shutdown will cause the server to begin shutdown immediately if AC power is lost. Thiswas implemented for offshore areas where the server was deemed non-critical to remain poweredup during AC power cutoff for safety reasons.

This option only makes any difference to systems with battery backup such as the EDR/UBD systems. The shuttles and ANAX 500 systems should have UPS's connected to them to ensure continuousoperation.

1.5.7 Default Well template

Click the down arrow to the right, scroll down the drop down list and select the well template that willbe used to create new wells. All wells created using either the control panel or the Well Control buttonin a connected WellWizard Client will be created using the specified template.

See the Well Templates for further details.

1.5.8 Well Control Button

Click the button to the right to enable or disable well control. When enabled, a button will appear in theWellWizard client software which will do the following when pressed by the user:

· Shutdown the currently active well.· Create a new well using the default well template.· Start the new well logging data.

&Note: The button is primarily intended for use in GEOLOGGER mode.

IMPORTANT: Any WellWizard clients connected to the server will have to be restarted to get the newsetting.

1.5.9 Well Configuration Password

This password is to used to control access to the channel mappings and sensor calibrations of a wellwhen using the WellWizard Client software.

Note: Selecting WellWizard -> Configure in the WellWizard Client menu bar and using this passwordwill allow access to the channel mappings and calibrations

1.5.10 Server Info Text Mode

ssh into the server and issue the following command:

[1]root@server(/) # WWsetupSelect Command - use arrow keys and ENTER to select. Press 'X' to exit.Command: Server Setup

The right/left arrow keys work here and allow you to choose Server Setup; which is the first optionalways given. Press <enter> to go into to Server Setup. If Server Setup hasn't been run before it willautomatically take you to the options. Note that "x" will exit you at any point.

The options presented are scrolled through using the right/left arrow keys followed by <enter> whenyou are happy with your choice.



Some changes and Shortcuts in the WWsetup - Server Setup screen.

Timezone: Use the "d" character to move ahead 24 entries or "u" to move back 24 entries to bring youcloser to your desired region.

Time & Date: Use the left/right arrow keys to change from year, month, day, hour, minute, and thensecond. The use the up/down arrow key to adjust the time.

Note if your unsure on the setup you may run it again to verify.

1.6 Wells

The WellWizard Control Panel should be used whenever possible for working with wells. Please referto each sub-section for information on how to perform the same task from within Text Mode.From the Well menu you can Create a New Well.

After the well is created right mouse click on the well or click on the Well menu to: Enable well logging Disable well logging Stop Well Changing well properties Tensor Configuration Delete Well Rename Well

The functions may also be accessed by left-clicking on the desired well and selecting the appropriateicon in the toolbar.



1.6.1 Definitions

Delete well: remove the entire well, including all data and configuration files, from the server.

Rename well: change the name of the well.

Enable well logging: change the well state to 'logging' and start server acquiring data for the well. Theserver will continue to acquire data for the well until such time as logging is specifically disabled. Evenif the server is shutdown or rebooted, it will start acquiring data for the well again once the system isrestarted. To permanently stop a well from acquiring data the 'Disable Well Logging' button should beused.

WARNING: If logging is enabled on two or more wells that require the same acquisition hardware likea serial port or analog card, only the first well so enabled will have access. The remaining well(s) willbe marked logging but will fail to acquire the hardware and hence the data. Typically, there shouldonly be one well logging although it is possible for the server to acquire data for several wellssimultaneously if properly configured. If in doubt, disable logging on all wells except for the one ofinterest.

Disable well logging: stops the server acquiring data for the specified well.

Stop well: shutdown the specified well. Wells that are 'logging' when stopped will start logging again ifthe server is rebooted. To permanently stop a well from acquiring data the 'Disable Well Logging'button should be chosen.

UWID - Unique Well Identifier : Each well you create will have a UWID or Unique Well Identifier. ThisUWID allows for every well in the world to be unique. This UWID is based upon your computer'snetwork card MAC address and a time stamp. So no two wells will ever be the same. This UWID



becomes very important when you have multiple wells on a server as it helps keep things organized.

LWID - Logical Well Identifier : The Logical Well Identifier is also assigned to any wells on the systemin numerical order with one being the lowest possible value. This information is used along with theUWID to keep wells seperated on the system and to allow for ease in adminstration. The LWID isassigned to every well using the lowest value, ie. If well 1 is created and then well 2 is created, well 1is deleted the next well created will be well 1. Then the next well will be three, four, five, and so on.

1.6.2 Create a New Well

The Well tab displays the all the wells on the server and their operational state. To create a new wellthere are three methods:

Method 1:· Click on Well on the top menu bar.· Select Create Well from the drop down list.· Enter well name (must be 4 or more characters in length).· Click OK

Method 2:

· Click Create New Well Icon.· Enter the well name (must be 4 or more characters in length).· Click OK

Method 3:· Right click anywhere in the well display to bring up a context menu· Select Create Well in the context menu· Enter well name (must be 4 or more characters in length).· Click OK

Your newly created well will be listed in the well info panel. Under the info panel you can see Type,Status and Well Name.

Well Types: There are two types of wells: Local and Remote. Local wells are wells that have eitherbeen created on the local server or have been restored from an archive on to the local server. Remotewells are wells that are or have been mirrored from another WellWizard server. Remote wells can nothave well logging enabled nor can their properties be changed.

Well Statuses: Five different statuses indicate the operational state of a well:

WARNING: NEVER create a EDR, UBD or Mudlog well on system unless a Data Acquisition boardhas been connected to it.



By default, only a full-size WellWizard Server has a Data Acquisition board (DAC). If a well is createdfrom a template that requires a DAC and that well is started, the well will fail to function correctly.

See the Well Templates section for further details on well templates and their requirements.

1.6.2.1 Create a New Well - Text Mode


WWsetup

Using the right/left arrow keys scroll to the right until you see "Well Management" <enter>. This iswhere we can create or delete or modify a well's status. In order to create a well you must scrollthrough the existing wells to the right until you see "Well: Create New Well Entry" <enter>.

Select Well Template - use arrow keys to change and ENTER when done. Please refer to WellTemplates for assistance in choosing the correct template.

Enter New Well Name: Give your well its name, this is the default name given to the client.

Successfully created well 'mark1': Well Template: Demo Well Logical Well Identifier: 2 Unique Well Identifier: W0004BF0003B2GIEE7H

As you can see my well is named mark1, it's a demo well, it's the second well on my system and itsUnique well identifier is W0004BF0003B2GIEE7H .

Now at this point your well is created, but its not activated. If you have a previous well on this serverand it already has special configurations, or channels, or wits changes, you will want to copy thosechanges into your well, but only if you need them. Remember that each well is unique from each otherso these changes don't automatically happen. You will want to exit (remembering the "x" will alwaysback you out to the previous step) and copy the proper /config directory files to the newly created well. See section below "SAVING CHANGES" for information on which files to copy and to where.

Use the 'x' twice to back out to a command line. Once to get back to sub-menu. Use the 'i' for moreinformation.

1.6.3 Enable Well Logging

There are three ways to enable well logging:

Method 1:· Right click on the desired well to bring up a context menu.· Select Enable Well Logging in the context menu.

Method 2:· Click on desired well in the well list to select it.

· Then click the Enable Well Logging icon.

Method 3:· Click on desired well in well list to select it.· Click on Well on the top menu bar.· Select Enable Well Logging from the Well menu.



Your well will now display Logging which means the new well is active and collecting data.

WARNING: If logging is enabled on two or more wells that require the same acquisition hardware likea serial port or analog card, only the first well so enabled will have access. The remaining well(s) willbe marked logging but will fail to acquire the hardware and hence the data. Typically, there shouldonly be one well logging although it is possible for the server to acquire data for several wellssimultaneously if properly configured. If in doubt, disable logging on all wells except for the one ofinterest.

1.6.3.1 Enable Well Logging - Text Mode

If your still in WWsetup from creating the well then jumped down skip the next few lines regardinggetting back to your well.


WWsetup

Using the right/left arrow keys scroll to the right until you see "Well Management" <enter>. Use thearrow keys to find the well you wish to Enable well logging on.

When the name of the well you wish to Enable is listed hit <enter>. This will bring up the options foryour well with the first one being "Enable Well Logging". If you hit <enter> at this point the well willchange states from active or inactive to Logging.


1.6.4 Disable Well Logging

Three methods exist to disable well logging:

Method 1:· Right click on the desired well to bring up a context menu.· Select Disable Well Logging in the context menu.

Method 2:· Click on desired well in well list to select it.

· Then click the Disable Well Logging icon.

Method 3:· Click on desired well in the well list to select it.· Click on Well on the top menu bar.· Select Disable Well Logging from the Well menu.

The well will now display Active indicating that the well is still running but is not acquiring data.

Once logging has been disabled on a well, the well will continue to remain active to allow userscurrently connected to the well to continue to view the historical well data. After the last userdisconnects from the well, the server will wait for 5 minutes of inactivity before automatically stoppingthe well. The well may also be stopped by performing a Well Stop.



1.6.4.1 Disable Well Logging - Text Mode


WWsetup

Using the right/left arrow keys scroll to the right until you see "Well Management" <enter>. Use thearrow keys to find the well you wish to Disable well logging on.

When the name of the well you wish to Disable is listed hit <enter>. This will bring up the options foryour well with the first one being "Disable Well Logging" -- this is assuming the well is currentlyEnabled for Well Logging. If you hit <enter> at this point the well will change states from Logging toactive or inactive.


1.6.5 Stop Well

There are three methods of stopping a well:

Method 1:· Right click on the desired well to bring up a context menu.· Select Stop Well in the context menu.


· Then click the Stop Well icon.

Method 3:· Click on desired well in the well list to select it.· Click on Well on the top menu bar.· Select Stop Well from the Well menu.

The well will change status to Stopping for roughly 10 seconds then finally show Inactive indicating thatthe well has shutdown completely.

IMPORTANT: Stopping a well will cause all programs running on the server associated with thespecified well to shutdown. If the well was Logging, however, those programs will restart if the serveris restarted or rebooted. To permanently disabling logging on a well, use Disable Well Logginginstead.

1.6.5.1 Stop Well - Text Mode


WWsetup

Using the right/left arrow keys scroll to the right until you see "Well Management" <enter>. Use thearrow keys to find the well you wish to Stop well logging on.

When the name of the well you wish to Stop is listed hit <enter>. This will bring up the options for yourwell with the first one being "Disable Well Logging" -- this is assuming the well is currently Enabled forWell Logging. Scrolling further to the right you will see two more options; stop and kill. These both doessentially the same task but Stop is the nice one of the two. It will wait until all users finish up before



stopping the well; kill doesn't care and will kick all users off the system now.


Important: Stopping a well will cause all programs running on the server associated with the specifiedwell to shutdown. If the well was Logging, however, those programs will restart if the server isrestarted or rebooted. To permanently disabling logging on a well, use Disable Well Logging instead.

1.6.6 Changing Well properties

Bringing up the Well properties can be accomplished by using one of the following three methods:

Method 1:· Right click on the desired well to bring up a context menu.· Select Well Properties in the context menu.


· Then click the Well Properties icon.

Method 3:· Click on desired well in the well list to select it.· Click on Well on the top menu bar.· Select Well Properties from the Well menu.

Note that the Well Properties are currently limited to the TENSOR configuration. See TENSORConfiguration for further details.

1.6.7 TENSOR Configuration

The Tensor Configuration panel will allow you view/change your well properties accordingly.

Auto Survey Enable: Check the box on the right to enable automatic survey entry. As information isreceived either via the TENSOR tool or via WITS, survey records will automatically be created in thedatabase.

Ream Lag Enable: Check the box on the right to enable lagging while reaming. This will allow asection of the hole to be re-logged for various information like gamma. Note that the rig status for thewell must be reaming and ream lagging enabled for relogging of the data to occur. Reaming isenabled through the Rig Status gauge in the WellWizard client software.

WARNING: Ream Lag Enable should ONLY be enabled if a section of the hole needs to be re-loggedand ONLY while Reaming. After reaming is complete, be sure to disable the Ream Lag Enable;otherwise, data will be overwritten. Also, be careful not to run with Ream Lag Enabled while drillingnew hole as it will not create any new depth records.

Serial Port: Click on the down arrow on the right to bring up a list and select the serial port on theWellWizard server which is to receive data from the TENSOR tool. The default is serial port 4.

Gamma Scaling Factor: Correction factor applied to gamma value coming in from the TENSOR tool. The default value is 1. The factor is applied using the following formula:



Gamma Scaling Offset: Correction offset applied to gamma value coming in from the TENSOR tool. The default value is 0. The offset is applied using the following formula:

Survey Method: Click the down arrow on the right and select the survey method to use for autosurveys. The possible selections are to use either the TENSOR Survey Depth for the survey depth oruse the current Bit Depth for the survey depth. The Survey Offset is applied to the selected surveydepth to determine the depth that the WellWizard will use to generate automatic survey records.

Survey Offset: Correction offset applied to the incoming survey depth information to obtain the actualsurvey depth. The value entered should be a positive offset in meters and the Survey Depth isdetermined as follows:

Tool Offset: Correction offset applied to the bit depth to determine the actual depth of the MWD tool. The value entered should be a positive offset in meters and the Tool Depth is determined as follows:

WITS template: Left click on the down arrow and select the desired WITS configuration file.

Once all the necessary modifications have been made to the configuration, click Apply to inform theserver of the changes.

Click the Cancel button at any time to exit from the Well Properties dialog. This will discard anychanges that were made to the Well Properties.

For more detailed information which template you should be using if unsure contact your localOperations department.

1.6.7.1 TENSOR configuration - Text Mode

The command from the text line is WWtensorc. The command will bring up a wells option list; scrollthrough until you find the well you wish to configure the TENSOR options on and hit <enter>. Theoptions presented are the same as those presented in the GUI TENSOR Configuration. Use the arrowkeys to scroll through the options and then use the <enter> key to make changes to any of the values. When your finished hit the 's' key to save and then 'x' to exit.

1.6.8 Delete Well

To delete a well use one of the following three methods:

Method 1:· Right click to desired well to highlight it and bring up a context menu.· Click Delete in the context menu.· System will ask you if you are sure you want to delete this well?· Click OK.

Method 2:· Click on desired well to select it.· Click on Well In the top menu bar to bring up the Well menu.



· Select Delete Well from the well menu.· System will ask you if you are sure you want to delete this well?· Click OK.

Final Method:· Click on desired well to select it.

· Click on the Delete Well icon. · System will ask you if you are sure you want to delete this well?· Click OK.

WARNING: Deleting a well will permanently remove it and all its associated data from the server. There is no way to recover a well after it has been deleted.

1.6.8.1 Delete Well - Text Mode


WWsetup

Using the right/left arrow keys scroll to the right until you see "Well Management" <enter>. Use thearrow keys to find the well you wish to Delete.

When the name of the well you wish to Delete is listed hit <del>. This will ask you if your sure youwant to delete this well if the well is already in a inactive state. If it tells you it can't delete the well thenhit <enter> and kill the well (see Stop Well - Text Mode). Once the well is killed you can then scrollonce more to the right to highlight Delete and hit <enter>.


1.6.9 Rename Well

Use one of the following three methods to rename a well:

Method 1:· Right click on the desired well to select it and bring up a content menu.· Select Rename Well from the context menu.· A pop up dialog will appear prompting for the new well name.· Enter new well name.· Click OK.

Method 2:· Click on desired well to select it.· Click on Well in the top menu bar to bring up the Well menu.· Select Rename Well in the Well menu.· A pop up dialog will appear prompting for the new well name.· Enter new well name.· Click OK.

Method 3:· Click on desired well to select it.



· Click on the Rename Well icon. · Enter new well name.· Click OK.

1.6.10 Well Templates

The following table lists some of the primary well templates:

TemplateName

/ww/well/default

Programs Notes

ElectronicDrillingRecorder

EDR WWdac_rtd5408WWpulserWWwits

Used for all full-size EDR functions

Geologger GEOLOGGER

WWwits Used for all Geological and basic IDS jobs. Not to be usedfor MWD IDS

Under-Balanced

UBD WWwitsWWhartWWpulser

Used on all Under-Balanced jobs. Has the calculationsand Hart sensor configs.

Tensor TENSOR WWtensor Used when only Tensor is bring brought in - no EDR data

Tensor + Wits TENSOR_WITS

WWtensorWWwits

Used on Tensor jobs with EDR data

Maerk Well (QLOG-WW)

MAERSK WWinterface Configurations specific to the Maersk Work

Petrobras Well PETROBRAS

WWinterfaceWWpb

Configured for usage on Petrobras rigs

PHS Well PHS WWwitsWWdac_rtd5408

Used in conjunctions with standalone ph/ps jobs

QLOG-WWInterface

INTERFACE

WWinterface Standard for all QLOG interface work.

QLOG-WWBatch

QLOG_BATCH

none Used in Batchup jobs on main servers.

Demo Well DEMO WWdac_sim Simulation Wells

DemoMudloggingWell

DEMO_MUDLOG

WWdac_sim Mudlogging Simulation Well.

Mudlog MUDLOG WWwitsWWdac_rtd5408

Main well template for ANAX systems

Northland UBD NORTHLAND

WWwitsWWhartWWpulser

Northland Specific Configurations

1.6.10.1 Modifications to Default Templates

It may be necessary to modify the default templates under the following circumstances and/or have abackup of the important configuration files in case of failure:



· Changes were made to an existing well and you wish them to also appear in newer wells· You have a file from you wish to have in case of server failure as a backup· You have a file you wish to restore

In order to copy out the files you will need to tar the necessary files only. Copying out the entiredirectory will cause many issues and should never be done. The files you wish to copy are:

/ww/well/UWID/config/

programs -- alerts the system as to which processes to start for this templaterealtime.map -- this holds all the available channels (modified by WWtext)realtime.txt -- used alongside realtime.maptranslations -- holds the translated data, must be matched with the realtime.mapwits -- holds the current wits configuration files (note copy out any other wits files used)triggers -- configuration for the lagscalculations/resources/zeros -- special files used to hold calculations used.well.cfg -- these are the dac calibration used in EDR/UBD/Mudlogging/Anax

Once the tar file is created copy it to the /tmp directory where you can WinSCP it onto your windowsbox for safe keeping or copy it to the defaults. "cp filename.tgz /tmp". To copy the file to the defaultyou must do the following:

1. cp filename.tgz /ww/well/default/(template)/config -- in the case of EDR type:/ww/well/default/EDR/config

2. cd /ww/well/default/(template)/config3. gtar -zcvf original.tgz * -- this creates a backup file with the original default configs4. gtar -zxvf filename.tgz -- this will extract your modified files into the default template.

Now that the defaults are extracted you can create any number of new wells and maintain the previousconfigurations.

1.6.11 Archive

The archive command is not yet available from the WellWizard Control Panel and must be preformedon the server itself. Use ssh to gain access to the server and then follow the instructions on how toarchive your well.

Command Usage: WWdbm

Type WWdbm and your presented with the following options:

Select Command (use arrow keys): Archive

Using the arrow keys you have a choice of Archive, Restore or Exit

Archiving a Database

When you wish to archive your database simply type WWdbm, and choose Archive. Choose thedesired well and whether you wish to archive time, depth or both time and depth. Finally your asked togive the archive a name, please choose something relevant like well name. The command will thenprocess the database and store it along with all necessary config files to the requested file name – thiscan take a while, so please be patient. Once completed you can WinSCPthis file out to be stored orrestored on another server. The Archived file will be in the current directory using the name you gaveit with the extension of .dbm. The well is not removed at this time and can continue to be used asnormal, the archive is simply a copy of it. The WWdbm archive command can be run with the system



logging and as many times as felt is necessary. It's a good idea to run the Archive feature when at asidetrack point, as routine data maintenance and whenever changes are going to be made.

The option for archiving depth and time should always be used regardless if you only need depth orjust time. By grabbing both you ensure that you have a complete record of your well and if you onlygrab one or the other restoring into an existing database will be difficult.

1.6.12 Restore

The restore command is not yet available from the WellWizard Control Panel and must be preformedon the server itself. Use ssh to gain access to the server and then follow the instructions on how toarchive your well.

Command Usage: WWdbm

Type WWdbm and your presented with the following options:

Select Command (use arrow keys): Restore

Using the arrow keys you have a choice of Archive, Restore or Exit

The file is restored back into a well that it creates based on the original UWID. If you restore back tothe original server it will recreate the well with the original UWID unless that well is still active, then itwill ask to overwrite, or to create a new well with a new UWID. Make your choice and press enter. Now the file is extracted and created.

1.7 Users

The Users tab can be used to perform user management including creating and deleting users as wellas modifying their well access permissions. The major operations are as follows:

· Create New User· Clone User· Delete User· Edit User Well Access Permissions



1.7.1 Create New User

Creating a new user is a simple procedure and is outlined below. One primary aspect of user creation,however, is configuring a user's well access permissions. In many cases, several users often have thesame well access privileges. If this is the case, the easiest way to create new users is to create asingle user entry with the desired permissions, then clone that user multiple times to create theremaining users.See Clone User for more information.

To create a new user, use one of the following methods while in the User tab:

Method 1:· Click User on the top menu bar to bring up the User menu. · Select Create User in the User menu.· A pop up dialog will appear prompting for the new user name.· Enter the new user name.· Click OK.

Method 2:· In the User List on the left-hand side, right-click to bring up a context menu.· Select Create User in the context menu.· A pop up dialog will appear prompt for the new user name.· Enter the new user name.· Click OK.

Method 3:

· Click on the Create User icon in the tool bar.



· A pop up dialog will appear prompt for the new user name.· Enter the new user name.· Click OK.

After the one of above has been completed, the User Info will show the new user information.Fill in the missing information and click Apply to finish creating the user.

A unique password should be entered for the user and must meet the following requirements:· Must be 5 or more characters in length, but less then 100 characters· Characters must be alphanumeric or punctuation characters.· The password may NOT be 'admin'.· The password may NOT be the same as the user name.

The Comment field, while not required, should also be completed. The user's full name,company, and job title are suggested.

UserType should be set as:· Normal - these users are normal users who do not need access to Control Panel, WW Tour Sheet

or configuring Trip Monitoring.· Administrator - these users will have access to Control panel, Tour Sheet and to configure Trip

Monitoring· Administrator (locked) - this user cannot be deleted by other administrator users accounts. This

should be the primary admin account

Well Access is the last, but also the most important, user information to configure. If no well access isgranted, the user will be able to connect to the server, but won't be able to get any data. Simply checkor uncheck the box next to the desired wells to enable and disable access. Click on the 'DefaultPermissions' field for a well to customize a user's access to the selected well. Note that thepermissions can only be accessed if access to the well has been enabled: that is, there is a check nextto the well.

See Well Permissions for further details on how to customize well accesses.

1.7.2 Clone User

Cloning a user is essentially a copy operation: an existing user entry is duplicated, renamed, and givena new password to create a new user entry in the system. Using cloning, adding several users withthe same well access permissions is greatly simplified. To clone a user, perform one of the following:

Method 1:· Click User on the top menu bar to bring up the User menu. · Select Clone User in the User menu.· A pop up dialog will appear prompting for the new user name.· Enter the new user name.· Click OK.

Method 2:· In the User List on the left-hand side, right-click on desired user entry to clone to bring up a context

menu.· Select Clone User in the context menu.· A pop up dialog will appear prompting for the new user name.· Enter the new user name.· Click OK.

Method 3:



· Click on the Clone User icon in the tool bar.· A pop up dialog will appear prompting for the new user name.· Enter the new user name.· Click OK.

After the one of above has been completed, the User Info will show the new user information. Cloning,while it does preserve well access permissions, does not preserve the password or commentinformation from the original user entry. That information, which should be different from the originaluser entry, must be manually entered. Fill in the missing information.

A unique password should be entered for the cloned user and must meet the following requirements:· Must be 5 or more characters in length, but less then 100 characters· Characters must be alphanumeric or punctuation characters.· The password may NOT be 'admin'.· The password may NOT be the same as the user name.

The Comment field, while not required, should also be completed. The user's full name,company, and job title are suggested.

The Well Permissions may also be modified, if necessary.

Click on the Apply button to finish the operation. The newly created user, cloned from the originaluser, is added to the User List.

1.7.3 Delete User

Use this operation to completely remove a user from the system. If only access to a particular well orwell is required, simply modify the user's well access permissions.

To delete a user, use one of the following:

Method 1:· Select the user to delete in the User List by scrolling through the list and left-clicking on the user

name.· Click User on the top menu bar to bring up the User menu. · Select Delete User in the User menu.· A pop up dialog will appear prompting for confirmation.· Click OK.

Method 2:· In the User List on the left-hand side, right-click on user entry to delete to bring up a context menu.· Select Delete User in the context menu.· A pop up dialog will appear prompt for confirmation.· Click OK.

Method 3:· Select the user to delete in the User List by scrolling through the list and left-clicking on the user

name.

· Click on the Delete User icon in the tool bar.· A pop up dialog will appear prompting for confirmation.· Click OK.



1.7.4 Well Permissions

A User's access to a well can be controlled in a number of ways. Database editing can be disabled,access to real-time data denied, and a number of other options. Currently, the selections are asfollows:

· Allow Realtime Data: User can see the real-time data a well is generating. Note that only a well thatis Logging will have realtime data.

· Allow Database Editing: User is able to edit data in the time and depth database tables using theWellWizard Client Software (WWC). Note that certain locked fields cannot be edited. This includesthe key fields of Time and Depth, Memos, and certain other parameters.

· Allow Resource Editing: If enabled, the user is allowed to access the Set context menu option ofcertain parameters of the well when using the WellWizard Client software. For example, being ableto set the Hole Depth and Bit Depth - rightclicking on these gauges in the WellWizard Client willbring up the menu.

· Allow Comment Picklist Editing: If allowed, the user can edit the comment pick list for the well usingthe WellWizard Client software.

· Allow Lithology Bitmap Editing: The user is able to specify the bitmaps used to render the lithologyin the WellWizard Client software if this option is enabled. Lithology bitmaps are accessed in theWellWizard client by choosing Edit- >Lithlogy Bitmaps from the main menu bar.

· Allow Well Info Editing: As expected, this option grants the user the ability to modify the Well Info likeWell Operator, Well Name, Personnel Information, etcetera using in the WellWizard Client.

· Allow Pipe Tally Editing, Allow Pipe Type Editing, & Allow Survey Editing permit the user to edit thePipe Tally, the Pipe Types, and the Survey Table, respectively, using the WellWizard Client.

· Allow Well Grant: This option permits the user to grant access to a well to other users. This optionis primarily intended for use with Wellhub to allow Wellhub to create user entries in a secure fashionon mirror servers.

· Use Wellhub Permissions: This option is actually a combination of several of the other permissionsand essentially disables all of the user's editing capabilities. Enabling this option will cause severalother options to be automatically disabled and unconfigurable. This option is primarily intendedfor use by Wellhub and should not need to be utilized.

A Non-Wellhub User has the following access by default:



A Wellhub User, by contrast, has the following default permissions:



1.8 WITS

WITS (Wellsite Information Transfer Specification) is the standard method of communication for all oiland gas companies. It allows for the quick and easy transfer of data between all companies.

Type "man WWwits" for detailed flags and options.

Also see the appendix for the standard wits codes.

1.8.1 How does Wits Work

WITS is sent from system to system using the following format.

&&0140123.45!!

&& signifies start of record0140 denotes Total Gas 123.45 is the Total Gas value !! signifies end of record segment.

So, if this is sent to the EDR or IDS, it would show 123.45 in it's Total Gas gauge. The 0140 is astandard that all companies use and allows for quick and easy communication between us and othersand even ourselves.

So, how do I send 0140?

The file that controls WITS is simply called "wits" and is found in /ww/well/UWID/config directory.

If you do a "more" command on this file, you will see something similar to this:

## Specify Default Timeout#TIMEOUT=5#PORT=1,serial,/dev/ser1,9600,N,8,1PORT=2,serial,/dev/ser2,9600,N,8,1## SEND identifies the start of the parameters to be sent.# SEND=Options## Options conditions:# port=IO port Port to Send/Receive data on# receive=WITS record WITS Record to receive before sending data# receive=WITS item WITS Item to receiving before sending data# time=second Time between data transmissions# depth=depth(m) Depth Interval in meters between data transmissions# timeout=seconds Time in seconds before data is invalidated## NOTE: receive and time options are conditions which trigger when# a record is sent and are mutually exclusive. The last trigger option# specified will take precedence on when data is sent.



SEND=port=1,time=5## Data parameters are described as follows:## rree,mnemonic,unit,options comment# rr = WITS record number (must have leading '0' if < 10# ee = WITS element number (must have leading '0' if < 10# mnemonic = WellWizard Channel Mnemonic# unit = WellWizard Unit Conversion for specified data# options = optional parameters that specify special handling# comment = Description of the WellWizard channel. Not required.## supported options:# Iinterval - data is rounded to nearest interval (eg. I0.2)# Cfactor - correction factor is applied to data (eg. C1.07)#0108,DBTM,0 Bit Depth0110,DMEA,0 Hole Depth0112,BPOS,0 Block Position## RECV identifies the start of the parameters to be received.# RECV,Options# # Options conditions:# port=IO Port Port to Receive data on.# timeout=seconds Time in seconds before data is invalidated.#RECV=port=1,timeout=300##0123,SPM1,0 Pump Stroke Rate#10124,SPM2,0 Pump Stroke Rate#20125,SPM3,0 Pump Stroke Rate#30140,GASS,0 Total Gas##

This isn't, of course, how every file looks! The default has several sections to it, but they do all followthe same pattern, a send or receive followed by the desired data.

1. Timeout=5 This is the default timeout. If you don't specify a timeout for send or receive it will use this default

2. Port Definitions PORT=1,serial,/dev/ser1,9600,N,8,1 Set Port 1 to serial comm. (don't change) /dev/ser1 means mounted to serial port 1, baud=9600,parity=none, bits=8 and stopbits=1. Set for all relevant ports

3. SEND or RECV Can be either, depending on your requirements. Following the example above, we haveSEND=port=1,time=5. So, everything below this value will be sent on port 1 every 5 seconds.

4. SEND (SEND=port=1,time=5). Note RECV data follows same pattern - the WITS value you are looking for, where to store it, what unitis it in and then a short description for your usage.

So 0108,DBTM,0 means look for WITS record 0108, and get this data from DBTM using the unit of



meters. If your sending Gas, you would include a line that reads 0140,GASS,0 – this would send TotalGas, in percentage, on record 0140. (Note, the basic WITS records, that show you where these valuesof 0108 and 0140 come from, are included in Appendix 1).

So, following the example, I will send bit depth, hole depth and block position, every five seconds outof port 1.

5. RECV (RECV=port=1,timeout=300)Receive on port 1 and hold the last data sent for 300 seconds. The timeout allows for incoming datato be missed but not indicated on any gauge for 300s. You don't want this value set too high, as youwould not recognize a problem until after the timeout period, but, at the same time, you don't want thevalue set too low or you will often see –9999 on your gauges.

1.8.2 Advanced Wits

1. Multiple mapping of records

The same WITS record can be received and placed into more than one record. For instance, youcould take 0110 (Hole Depth) and map it to both Hole Depth and Bit Depth.

0110,DBTM,0 Bit Depth (really hole depth)0110,DMEA,0 Hole Depth 2.

2. Units conversions

Metric is the default unit for all channels. You will see a "0" (denoting metric) after 90% of all defaultWITS values. This unit can be changed, if necessary, in order to send/receive the correct unit orto/from other parties.

For instance, in the United States, feet are typically used, rather than meters.

So, if we were to include the line in the RECV section: 0110,DMEA,0 Hole Depth

....we would actually receive the Hole Depth value in meters, obviously a problem!

To ensure we receive the value correctly, in feet, we should change to line to read "0110,DMEA,1" -the value would be received in feet, and then converted to our metric database.

If we were sending Total Gas in US Gas Units, the line should be written 0140,GASS,4 – four beingthe fifth default unit, signifying US gas units.

The WITS unit code can be determined from the WW client drop down lists. For example, look atproperties on hole depth, and click on the down arrow for units. "m" is the first listed unit, equating toWITS zero; feet is listed second, equating to WITS one, etc, etc. The first unit in every list will equateto the WITS unit code "zero".

3. Multiplication

You can add a multiplication factor on to the end of a WITS line.

For example, with the line "0140,GASS,4,c10", Total Gas on 0140, is sent out in US Units and thenmultiplied by 10. You can use any value including decimal values here.

4. Offsetting Data



An offset factor can also be added on to the end of a WITS line.

For example, with the line "0110,DGRT,0,O-5", Hole Depth is received, on record 0110, and placedinto a depth holder that has been created for lagged Gamma. The depth would be the Hole Depthminus 5 meters (Datalog Canada has used this, for example, to receive the toolface depth fromSchlumberger).

5. RECV=

Sometimes it is desirable to only SEND some information once we receive specific information. Anexample of this being simulating Pason wits protocol. To use this option use the following syntax:SEND=port=1,receive=0140,timeout=180.

This line means to Send out port 1 all the configured channels only when we receive a valid 0140(gas). Until the system sees the 0140, nothing will be sent out.

6. LOG=

The LOG= option allows us to LOG all incoming and outgoing wits data via serial on any port to a filefor later viewing. This is very handy when trying to troubleshoot issues with WITS as often when aWITS problem occurs the data that caused it is already through the system. To use the LOG function,in your port definitions include the line LOG=/root/file.txt. This file will start to record everything comingand going until you remove the line and WWreload the wits file. Please don't forget about this file onceyou start recording as it can grow to be very large.

ie. PORT=1,serial,/dev/ser1,9600,n,8,1,LOG=/root/file.txt

The /tmp directory is also a good place to store temporary data like these log files but keep in mindthat the /tmp folder is cleared whenever the system is rebooted.

1.8.3 Wits via TCP/IP

The WellWizard server has been enhanced to support WITS communication via TCP/IP networkcommunications.

OVERVIEW:

While similar in many respects to serial WITS, TCP/IP WITS drastically alters the scope of WITS datatransferand careful thought should be given when utilizing it: both data security and data integrity must bemaintained at all times.

IMPORTANT TERMS:

Before getting into the thick of it, it is very important to be clear on the meaning of 'originate' and'answer' modes. The first thing to keep in mind is that these terms are in regard to the system you arecurrently working on. To 'originate' a connection request means that the local system you are currentlyon initiates the connection. To 'answer' a connection request means that a remote system is initiating aconnection to the local system. Actually, this terminology is not difficult in an of itself, but it does tendto become more muddled when adding the system references (local and remote) and the datareferences (send and receive) on top of it.

To prevent confusion, please do NOT use the terms client and server because they are applied tooliberally in most cases. As a good example of a bad example, if WellWizard originates a connection tosend depth data to a remote system, it could be said that the WellWizard is a client of the remotesystem even though the WellWizard is the one that is actually serving data. Confusing, eh? Onceagain, be sure everyone is clear before proceeding with any system modifications prior to using thisfunctionality.



AUTHENTICATION AND SECURITY:

Simply put, TCP/IP WITS has no authentication and no security. There is no encryption of data, nousername and passwords, no nothing. The only check is that the connecting IP address is the one thatis allowed to connect as specified in the 'allow=' part of the virtual port definition. If they're equal, you'rein; if not, you're out.

RECEIVED DATA:

An important consideration when configuring WITS to receive data via TCP/IP is that there should onlybe one source of incoming data. Multiple systems, typically, should NOT be allowed to connect to aport that is receiving data.To prevent problems and ensure that everyone plays nice, the recommended practice is to use asystem-centric approach to WITS configuration. While there are other acceptable approaches, theyare not easily understood (nor explained for that matter!) so we'll concentrate exclusively on thesystem-centric approach.

A system-centric approach is very similar to serial WITS communications. A virtual port is defined foreach system then each record to be sent and/or received to and/or from that system is defined. In thecase of multiple remote systems connecting to the local system, there may be similar data records thatwill be sent and/or received. This will make for a larger configuration file as each record definition iscopied to each port that want to receive it; however, it has several benefits as follows:

- Easy to tailor the data shared with any given system.- Easy to tailor unit conversions between systems.- Easy to control on a channel basis which ones are sent and received.- Easy to add special data processing options like offsets and factors.- Easy to enable/disable individual systems.- Lastly, as this is the only way to configure serial WITS communication, it is more consistent to handleTCP/IP WITS configuration similarly.

Sometimes it may be tempting to take what appears to be the easy road and configure one TCP/IPport that can do everything. DON'T!!! You'll save everyone a lot of hassle if you take the couple extraseconds to make a new port definition for the new system and setup the data items to it.

CONFIGURATION FILE FORMAT

The configuration file format remains largely unchanged from previous versions of WITS. The soledifference is the addition of a new virtual port type. To add a TCP/IP port, the format is as follows:

PORT=<n>,tcp,<port_id>,[[<allow=<hostname>>,...]|<host=<hostname>>]where:n is an arbitrarily assigned virtual port id number.port_id is the TCP port for dataallow=hostname allow remote connection from specified host.host=hostname connect to specified hosthostname an IP address in the format n.n.n.n. Names are NOT supported.

Sample Configuration Files:

Sample configuration file to receive gas data for incoming TCP/IP WITS on port 6000 from host10.10.10.10:

PORT=1,tcp,6000,allow=10.10.10.10RECV=port=1,timeout=300



0140,GASS,0

Sample configuration file to send depth data via TCPIP to host 10.10.10.10 on port 6002 with usinitiating or originating the connection:

PORT=1,tcp,6002,host=10.10.10.10SEND=port=1,time=50108,DBTM,00110,DMEA,0

Sample configuration file to send depth data via TCPIP to host 10.10.10.1 port 6001 where the remotehost has initiated the connection and receive gas data from 10.10.10.2 on port 6002 with usconnecting to the remote host would be as follows:

PORT=1,tcp,6001,allow=10.10.10.1PORT=2,tcp,6002,host=10.10.10.2SEND=port=1,time=50108,DBTM,00110,DMEA,0RECV=port=2,timeout=3000140,GASS,0

DIAGNOSTICS

The wits_diag program has also been enhanced to support TCP/IP WITS in both answer and originatemodes. As such, any number of checks can be performed to make sure that all communications areworking correctly. It may also be used to verify the proper operation of the WWwits program itself andcould even be used for doing basic system data overrides and data simulation. It is important to note,however, that in some cases the wits_diag programconflicts with the WWwits program. For example, it is NOT possible for both programs to be set toanswer incoming requests on the same port.

Security Note: The WITS program will answer all WITS connection requests initiated on the samecomputer so it is not necessary to specifically allow it in the WITS configuration file.

WITS TESTING PROCEDURE

To verify the proper operation of WITS in WellWizard, create a new Demo Well with WWdac_simdisabled and WWwits enabled. Create the following WITS configuration file in the well's configdirectory:

PORT=1,tcp,6001,allow=localhostPORT=2,tcp,6002,host=localhostRECV=port=1,timeout=100140,GASS,0SEND=port=1,time=50101,TIME,0RECV=port=2,timeout=100140,SPPI,0SEND=port=2,time=50101,TIME,0

Open two consoles under OpenBSD.

On the first console, issue the following command:



wits_diag -mo -p6001

On the second console, issue the command:wits_diag -ma -p6002

On the first console, the wits_diag program is originating a connection to the well sending data of 0.0on WITS channel 0140. You should see 0.0 in the Total Gas gauge in the WellWizard client. Youshould also see the TIME data of the WellWizard coming out on the console.

On the second console, the wits_diag program is answering incoming connections on port 6002. Youshould see the WellWizard connect to the wits_diag program and see TIME data of the WellWizardcoming out on the console. The wits_diag program, once the WellWizard connects to it, starts sendingWITS channel 0140 a value of 0.0 which is mapped to Standpipe Pressure. Looking in the WellWizardclient, you should see 0.0 in the Standpipe Pressure gauge.

Assuming that both these cases are true, this verifies that data can be both sent and received and thatthe WellWizard server is both answering and originating connection requests.

1.8.4 wits_diag

The wits_diag command is used now for all our troubleshooting and wits verification. For those whohave used the QNX4 system we used qtalk, but there is no such option in BSD so it was not broughtover.

"man wits_diag" for details.

Normal usage:

To enter a terminal mode which will allow you to send data down the line and to see what is comingback:

wits_diag -p/dev/ser1 -X

Please note that you can now do the following:!!01405.00&&

The wits_diag command will automatically include the carriage return/line feed that is required to makethis a valid wits packet. (Xod,Xoa)

wits_diag -p /dev/ser1

View the incoming wits feed using line feeds.

wits_diag -p /dev/ser1 -T

The way we are used to seeing wits_diag; in binary. (this is no longer default)

wits_diag -p /dev/ser1 -f /tmp/wits.txt

Plays back the file /tmp/wits.txt into the system -- great way to troubleshoot a recorded problem.



1.8.5 TroubleShooting Wits

This section covers most of the known problems that occur often with wits.

1.8.5.1 No WITS data is being sent or received

1. Verify that you have "wits" running on the WellWizard system on your active well.

Run the "qr" command and verify that "wits" is on the list; It will appear as /1/WITS – indicating WITS is active on well 1.

If it isn't you will want to verify why it isn't running. Try running wits from the command line by typing "WWwits –W1" (to start WITS on well #1) – thendoing the "qr" again.

If it still doesn't show up, this indicates that someone has edited the wits file and has caused an errorin the file. If there are any problems with the WITS file, it won't start. Possible problems to check, are:

· Check the very top of the file for any characters. This is easily done if you type somethingwithout noticing that the editor has started.

· A Send or Recv without anything to send or recv.· A # sign inadvertently removed from an explanation line.·2. Do you actually have a physical connection between the systems? You should check the following:

· Between RS-232 connections you need to null pins 2/3.· If connecting over 50', you should use RS-485. This also needs to be nulled.· If using current-loop, do you have an active or passive connection and are all LED

indicators activated?

3. Perform a loopback on our system to verify that WITS is working.

· If using a RS-232 port you will want to short out pins 2 and 3. Then do a "wits_diag-p/dev/ser1 -X" (/ser1 refers to port 1) and type yourself a message. If your typing appears on thescreen, your port is good. If nothing appears, check your ports connections inside the box.

· If using the RS-485 ports you will want to null these connections as follows: Jump pins 1-2and pins 3-4.. Then do a "wits_diag -p/dev/ser1 -X " (again ser1 is referring to port1). As with theRS-232 what you type should loop back.

· If using the Current loop port you will null by making an active connection to the port. Thisrequires an external power source. Take two 9V batteries and connect them in series. Connect thecombined positive to pin A, and the negative to Pin E. This creates the active loopback, as abovewhat you type should return.

All of these loopback tests can be performed up the line, and not just at the physical port. So you cantest the entire cable run by looping the opposite end.

If all WITS methods show a proper returning signal, than the other party should also test their ports. We have seen third party ports that are non-functioning. We can't do anything about that, but at leastwe can prove our ports are functioning.

With all loopbacks, it is best to do this as close to their system as possible. Eliminate as manyconnections as possible.



1.8.5.2 Data has the wrong values

1. Did you remember to include the proper unit conversion? If they are expecting hole depth infeet we have sent a metric unit, then, of course, the value will be wrong.

· Verify all unit conversions. This is also a good time to do a loop-back to yourself or to awindows box using HyperTerminal.

· Using HyperTerminal will show you the incoming raw data without the third party applying anyrules to it.

· If the data comes out wrong in HyperTerminal, it is because of the WellWizard system.

2. Are you sending data using the right mnemonic? Use the "WWtext" command to verify thatyou are really using the right value.

1.8.5.3 How do I record the incoming data

Often, there is a lot of data screaming across your screen and you can't pick out what you are lookingfor, or, you are receiving bad data and you want to make a hard copy to prove it.

Use the new LOG function for this operation. The old method would have required turning off WITSand use cat to collect the port information. Using the LOG function you can continue to collect theWITS data uninterrupted.

1.8.5.4 I have edited the wits file but nothing is working

You must Reload the "wits" command first, before it will accept any new changes. Simply make yourchanges to wits and then type the command "WWreload wits", followed by "qr", to see wits running onthe proper well. You should see WWwits listed. If you have turned off Wits for whatever reason aWWreload won't restart it. You will need to manually start as demonstrated below.

Alternatively you can "pkill -2 WWwits" and then restart it by "WWwits -Wx" with x being the wellnumber.

1.9 Lags

Lags in WellWizard are a fundamental part of displaying data in the correct locations. The term LAGrefers to the delay in reading your data and thusly the delay in displaying it.

Gas is the most common item that gets lagged. The concept here is that as we are drilling the Gasthat is being liberated at the current depth must travel up the hole and will be read at some later time;and we must know at which depth to place the Gas readings. We can't put the Gas readings at thecurrent hole depth as this would be wrong but we must have some way of knowing when to put thereadings in.

Other forms of Lag may be that of MWD. The MWD tool sits behind the bit generally from 10-20mbehind. Lag in this case then refers to taking the data recorded now and putting it "hole depth -tooldepth"; a simple form of lag.

Lag values are determined using one of several different methods. Basic Lag is time based lag; whereyou take a known lag time and you increase it by x amount of time as your drill deeper. The morecomplicated version and the standard for Mudlogging operations will be Volume Based lags whichtakes into account the hole size, pipe sizes, volumes, pumps, and velocity to determine a very preciselag depth.

Refer to the subsections for details on the different lag types and their usages.



1.9.1 Basic Requirements for lags

All the different lag methods use the basic set of rules to determine whether to process the laginformation or not.

You must be circulating for the lags to function. This is determined by:

1. SPM channel with a value equal to or greater than 6 strokes per minute

or

2. Mud Flow in with a value greater than 0, and StandPipe pressure with a value equal to or greaterthan 500 kpa

or

3. A physcial circulation switch connected to channel MC (mud circulating).

1.9.1.1 Time-Based Lags

Time-based lags is the simpliest form of lag in the system. Time-based is at is says - based on time,rather than pump rates or volumes. As long as a basic set of conditions are met (see conditions) thelag will advance. This lag method is used primarily for stand-alone or IDS jobs.

Channels of interest to pull up on your WellWizard screen:

Lag Depth - current lag depth and set function to set lagLag Time - current lag timeTime to Lag - counter to show how long at present conditions to next lag up

To set the lag time you must right click on the Lag Depth gauge:

The lag method you need to choose is the Time-based Method (other methods will be covered in their



respective sections)

Reference Lag depth refers to the lag depth at which all calculations will be done from. Normally thisis the current hole depth but it can be any depth at which a known lag can be calculated from.

Initial Lag time - At the reference lag depth what was the lag time

Lag Time Increment - over a 100m interval how much should the lag time increase. As you drill aheadthe lag time will increase as you go.

Gas in/Out Delays -- is their any delays added to the system to account for sample readings. Thiswould be used for Chromat systems that are connected to the mud system via poly-tubing with anincrease delay of getting the sample from the shaker to the chromat ie. 180seconds. Another usewould be for Tracer systems that can take up to 40seconds to sample a reading.

*** A very important channel to watch while doing Time-based lags is the Time to Lag channel underDrilling Parameters. It is basically a countdown that when reaches zero will update the lag depth. Ifthis value is decreasing than things are at least working but doesn't rule out improper calibration.

1.9.1.2 Stroke Based Lags

Stroke based lags are based on actual Strokes. Once the basic conditions are met the system willdetermine how many strokes are required to increment the lag depth. This method is more precisethan time based as it takes into effect the speed at which the pumps are moving.

Channels of Interest:

Lag Depth - set function and current lag depthLag Strokes- current value of strokes required for next lag up

To set the Stroke-based lags right click on the Lag Depth channel and choose set.



Using the drop down box choose Stroke based method

The reference lag depth is a depth at which the lag strokes is known and is the starting point for futurelag stroke increases.The Initial lag strokes is the number of strokes required to circulate a lag up based on the referencelag depthThe lag strokes increment is how many strokes to increase over the next 100m

The Gas In/Out sample delays add extra time to the lag processing for both the in/out channels toaccount for processing delays.

1.9.1.3 Air-Based

Air-based lags are different from the other types of lags in that no circulation condition is required. Therefore you don't need SPM's, StandPipe, Flow in order to process Air lags. The only requirementis setting the air-based lag parameters.

Channels of Interest

Lag Depth - shows current lag depth and set function to configure parametersLag Time - current lag time based on hole depthTime to Lag - current time remaining until next lag depth up

Configuration of Air-based is similar to time based. Choose Air Based from the drop down menu.

Reference Lag depth refers to the lag depth at which all calculations will be done from. Normally thisis the current hole depth but it can be any depth at which a known lag can be calculated from.

Initial Lag time - At the reference lag depth what was the lag time



Lag Time Increment - over a 100m interval how much should the lag time increase. As you drill aheadthe lag time will increase as you go.


*** A very important channel to watch while doing Time-based lags is the Time to Lag channel underDrilling Parameters. It is basically a countdown that when reaches zero will update the lag depth. Ifthis value is decreasing than things are at least working but doesn't rule out improper calibration.

1.9.1.4 Volume Based Lags

**note - the Mudlogging template must be used for Volume based lags.

Volume based lags are the most precise lags that can be used, but at the same time the mostcomplicated to configure. Unlike the previous methods where it was either time based or strokebased, this method calculates the volume of fluid in the hole and how long it will take to circulate to thesurface. This method is quite involved

Basic conditions must be met and then the following conditions are also required:

1. Configuring a hole and pipe profile in the Add pipe section under the Edit menu. Pipe types can beadded through the edit pipe type section under Edit. All information on the hole and pipe should beentered in here. Alternatively you can use the Jet Velocity channel and set the bit diameter on it. Thiswill create a hole profile for you.

3. Pump efficiences must be configured in the Pump Output channels

4. StandPipe pressure must be greater or equal to 500kpa.

ALTERNATIVELY

Bring in Mud Flow In and Standpipe to fit our basic circulating requirements and then bring in externallyAnnular Volume (TVA) and Pipe Volume (TVP).

Channels of Interest:

Lag Depth - current lag depth and set function to set lagLag Time - current lag timeTime to Lag - counter to show how long at present conditions to next lag upLag Volume Left -- like the Time to lag channel shows the decreasing volume left to be circulatedbefore lags up. Lag Volume Adjust - this shows the current value of Lag Volume Adjust as set by Lag Depth



Choose Volume Based from the drop down menu

Lag Volume Adjust -- sometimes there is a volume of mud in the system that the normal lags can'tcalculate and you don't want to modify profiles to account for it. By putting in a value here all new lagswill add this to the volume of mud to be moved.


1.9.1.5 Override Lags

Override lag method though it is an option isn't one that will be used. It's set automatically by theserver whenever a 3rd party brings their Lag Depth into the WellWizard system. This then removes allcalculation and processing down to calculate the lag depth. If the system is in override and it shouldn'tbe check your incoming wits files for Lag Depth (DRTM)

1.9.2 Trigger Lag

Trigger Lag is a program that is used alongside the WITS program and the internal Lag parameterwithin WellWizard itself.

It allows incoming data to be placed in the depth database at the appropriate value. If you receiveHookload by WITS, it will be databased into the time database at the current time and in the depthdatabase at the current depth.

But what about items such as gases (drilled depth continues to increase while gas is being circulatedup the hole), or gamma/resistivity (data is being recorded by the tool which is set some distancebehind the bit) which are received by WITS now, but actually correspond to a depth 5 meters previousor 50 meters previous to the current drilled depth.

Trigger lag, when executed, will take the data and place it back based on the following criteria:



a. a depth parameter (not hole depth)b. a real-time valuec. max or avg value received over interval.

So what is required to make the program work?

You need to have the lags defined in the file "triggers", which is located in /ww/well/UWID/config. You will need two channels for each lag: The realtime value as received through WITS and an associated depth - this can either be WITS overas well, or be an offset value from the current depth.

The following is an example "Triggers" file:

## This trigger.cfg is configured for the Geologger III## Store Maximum Gas for the intervalMUDLAG GASS:GASS> GASS:GASA=DGM MG:MG>

This trigger file performs the following commands:

· Take the value of GASS and store the maximum value received at the MUDLAG depth (whichis lag depth calculated by WW) and stores it to the depth database item GASS. · Take the same value and store it to GASA (Gas Average) and store the average value into thedepth database. · The next line shows Depth Gamma Ray as the depth trigger and to store real-time Gamma raymax value into the depth database.

You can have as many items as you like, being triggered by the same depth. You can also have as many different triggers as you want. But all have to follow the same pattern, and all have to be legitimate channels. If you include a channel that doesn't exist, the triggers file will fail. Remember that most third partycompanies will send you both required values, so we simply need to organize them into the system.

Like the WITS file, we also have different options that can be included with each line.

–DGM MG:MG> The "-" flag signifies not to trigger this item unless the system is on bottom.

+DGM MG:MG> The "+" option refers to the Newsco Ream lag option. This flag allows the item to be re-lagged for a whole section when the reamlag button is enabled. Thisbutton is currently only defaulted to the Newsco template.

Trigger_lag was previously controlled by the file "WWtrigger_lag". This has been modified recentlyand the process is now controlled directly by the WWengine program.

Therefore, if you make any changes to the Triggers file, you need to reload them into the engineprogram by using the command "WWreload triggers". Simply type the command in and all triggerchanges will be loaded.

1.9.2.1 GasLag

GASLAG should be used for all channels that are Gasses. There is extra logic applied to anyGASLAG triggered values to account for trips, connections and gas sample delays.

Also associated with GASLAG channels is a "Maximum Trigger" channel that must accompany allgasses. The common example would be chromat gasses. The chromat gasses would all be groupedtogether and a snapshot taken and databased whenever 'Total Hydrocarbons Out' reached a new



maximum over the gas interval. This is part of the recalculations to keep all the gasses properlyadding up. An example of how this would look like in trigger lag is as follows:

GASLAG:HYDC1 HYDC1 METH1 ETH1 PRP1 IBUT1 NBUT1 IPEN1 NPEN1 CO2_1 GASA1

From this example the trigger here is GASLAG which is determined from the DRTM channel (internalLag Depth). Whenever HYDC1 reaches a new maximum all the channels are then applied to thedatabase.

You can have multiple GASLAG configurations in the same triggers file.

Another example would be:

GASLAG:GASS1 GASS1

This would write GASS1 to the database whenever it reached a maximum value. (example ofGasWizard)

A clearer example of why GASLAG is used. In the above example we mentioned Hydrocarbons asbeing the trigger. Previous to this change your database would look like the following:

Depth Hydrocarbons

Methane Ethane Propane IsoButane IsoPentane

N-Butane N-Pentane

1000 10 5 3 0.5 0.3 0.2 0.2 0.11000.2 9 6 2 0.3 0.2 0.1 0.1 01000.4 10 7 1 0.3 0.3 0.2 0.1 0.11000.6 12 7 2 1 0.5 0.4 0.2 0.2

Table Gaslag 1 -- old method of databasing Gas

Notice how the data presented doesn't add up to the Hydrocarbons total. Hydrocarbons is supposedto be a total of all the gasses together -- yet often in your database you will see that this doesn't holdtrue. The reason is that during the same depth interval you recorded the maximum value for each ofthe different gasses and each gas may have reached a maximum interval at different points over therecorded interval. For instance at 1000m above we have a hydrocarbons with a value of 10%. Thisvalue is added from Methane, ethane ....but it is also the max Hydrocarbons over the 1000m interval. The highest Hydrocarbons may not have been the value of Methane max + ethane max + propanemax..... it is simply the highest calculated Hydrocarbons over the run.

So Gaslag now says, when you record the Max Hydrocarbon take the gasses for Methane, Ethane,propane and so on as well. So now in reality your database records the Hydrocarbon Max and theassociated gasses at the time, and not the max gas over the interval. By doing so all the gasses willadd up and appear proper. From the table "Gaslag 2" below you can see that the gasses all add upnow.

Depth Hydrocarbons

Methane Ethane Propane IsoButane IsoPentane

N-Butane N-Pentane

1000 10 5 4 0.5 0.3 0.1 0.1 0.11000.2 9 6 2 0.4 0.3 0.2 0.1 01000.4 10 6 2 0.7 0.4 0.3 0.4 0.2

Table Gaslag 2 -- Gaslag method

The GASLAG will take into consideration the gas out sample delay which maymake it a better choice to keep



1.9.2.2 Mudlag

MUDLAG refers to all parameters that are based on the "Lag Depth" channel directly. This is theequivalent of DRTM. Processed as a regular triggered-lag channel.

The proper usage would be:

MUDLAG MCIA>

1.9.3 Troubleshooting Trigger_lag

1.9.3.1 Everything has been overwritten with a straight line

This is an inherent flaw in WITS level O – the fact that there is no error checking.

Let's imagine you are receiving lagged data, Gamma, and the trigger is coming from the 3rd party. Ifthey send a bogus lag, our system will accept it and update the charts with that bogus data.

For example, let's say that from 100m to 200m you have an active Gamma curve. The 3rd party thensends 120m instead of 201m. The WellWizard system will take this data and connect the last twoknown points, in this case 200m to 140m, together, giving you the straight line.

Unfortunately, there is no simple way of recovering lost WITS data, all you can really do is import thedata again.

1.9.3.2 My Lag is Ok, but my Gas value is lower than it should be

You are victim to the long lag period and the average setting. If the trigger lag is set to use averageand you are at the depth in question for a long time, you can average 500 with many lower values,giving you a lower than expected value. Use Max values where possible.

1.9.3.3 I'm Not Receiving my Lags

In this situation, more than likely, the triggers file has not been setup properly.

· Confirm that all mnemonics exist and that they are the ones you intended to use. · Also, if you are using the Client Lag as provided by WW, then check to make sure that you arecirculating and that your time to lag is progressing to zero.

1.9.4 Check that the lag is Working

On the server side you can check the incoming lag status via a couple of methods:

1. WWtestlag -Wxxxx. This option will show you current settings for the Lag processing. By hittingthe "2" key you can watch the actual lag processing occuring. (-Wxxxx, with x being the LWID)

2. client_tcp -cdata_test -d"1 DMEA DRTM GASS" -- this command will allow you to login to thesystem as a client would (you will need a unique login/password). Whenever a lag event comes upyou should see a depth notify occur for your channels. The example line given shows well 1 and willdisplay hole depth, lag depth and Gas reading.

1.10 Creating Channels

The WellWizard system comes pre-configured with a basic set of channels which is used in mostcases. There is often though a need to add a new channel or hide some existing channels. Thecommand "WWtext" is used to add, modify or hide channels. You can never delete a channel once it



is created but you can hide it from view.

1.10.1 WWtext

Along with WITS and triggers you need to know how to add channels. It's not enough to simply usewhat is already in place, because the pre-programmed channels will not cover all circumstances andevents. There will be occasions where you will be asked to add channels that don't already exist, suchas new gamma tools, different well parameters or, perhaps, even multiple items a channel that alreadyexists.

Every channel must have an mnemonic. So how do we get these mnemonics and how do we createthem?

Type WWtext

[1]root@server(/) # WWtextSelect Well to ModifiyUse arrow keys to select and ENTER to view. Press 'X' to exitSelect Well 1: testv4 (LOCAL)

Use the right/left arrow keys to select the correct well. Remember that it doesn't help you to createnew channels in a well you are not using. When the right well is showing hit <enter>.

Successfully loaded text file '/ww/well/W0004BF0003B2GI6K6W/config/realtime.txt'Successfully loaded text file '/ww/well/W0004BF0003B2GI6K6W/config/category.txt'Use Arrow Keys and ENTER to select channel. Press '?' for HelpChannel AAFV : 'Accumulated Actual Fill' Unit: VOLUME, 'Pit Parameters'

The channels for my wells UWID are now successfully loaded, and the first channel appears. The channel is AAFV which is the mnemonic for Accumulated Actual Fill. The unit of this channel isVolume and can be found in the client under Pit Parameters. All channels will display this information.

Pressing the "?" button the following appears.

Arrow Keys select channel. Press ENTER to modify.A : Add channelC : Copy channel (adds a copy of the currently selected channel)L : Select LocaleT : Change Category textc : count channelsg : goto channele : position selector at last channelh : position selector at first channeln : advance selector to next channelp : advance selector to prev channelR : reloadS : savex : exit well? : help

These are the hot buttons that allow us do our jobs, so go ahead and try them.

e,h,n,p movement keys g Goto command - it will ask you for the mnemonic that you wish to goto (of course, you have toknow this!). So, by pressing "g", then entering "MG", I will be moved automatically to Gamma Ray or the closest



found channel with the mnemonic MG.

1.10.2 Adding a new channel or editing an exiting channel

Sometimes it becomes necessary to add a new channel because no existing channel fills therequirement. It's good practice, though, to scroll through WWtext, just to make sure that there reallyisn't any channel that fits the bill. Another usage for WWtext is to modify an existing channel to fit your need. Whenever you add a new channel you also increase the overall size of the database, so keep this inmind.

To add a new channel you first need to know some things:

· What will the new channel be called? i.e. Gamma2,· What will the new channel mnenomic be? i.e. MG2· Does any other channel fit the bill?· Is the mnemonic unique? Can't have two the same.· What units will the new channel have?· What style of channel will it be?· Will it be alarmed?· Where will it appear in the client? · Is it trigger_lagged?· Is it realtime, depth/time based? · Is it a calculated channel? · Will it be a editable channel?

Let's consider two different situations:

A) where you're required to add the channel Gamma2 and B) where you are editing channel UD2 to create Gamma 2

In situation A), you would want to run WWtext and hit the "A" button to add a new channel.

In situation B) you would want to scroll to UD2 and hit enter. Situation B) would not show the "Add newchannel" or "Enter channel mnemonic" as below, in this case you already have an existing mnemonic(UD2).

Add new channelEnter new channel mnemonic: Gamma2Enter new channel text: MG2 -- this shows up in both situations, for b) you would change thechannel from User Defined to MG2.

Everything else that follows is the same for both situations. If you are editing an existing channel, thepattern is slightly different than shown here. First it will ask you for the channel text, then the UnitClass, then Set Data Flags. It will not ask you Data Type. Please see the Unit Class section after theData Flags for instructions.

Data Type (use arrow keys): Double Precision Floating-Point Number (Double)

This section asks us what our Data Type is, your options are Double Precision Floating-Point Number(Double), String (ASC) , Binary/Bulk Data (BULK), Signed 32-Bit Integer (S32), or an Unsigned 32-BitInteger (U32).

Unless otherwise instructed to do so, always use the default value, Double Precision Floating-PointNumber.

Select Data Flags - use arrow keys to scroll through list of flags



setting and clearing the appropriate flags by pressing ENTER to toggle.

Select 'EXIT' and press ENTER to exit data flags selection.

Data Flag : Realtime a. Realtime does the channel appear in realtime gauges?-- always say yesb. Depth (Realtime-Depth) does the channel show up in depth databaserealtime? -- always say yesc. Time (Realtime-Time) does the channel show up in time databaserealtime? d. Depth-based (stored in Depth Database) is it stored in the depth database?e. Time-based (stored in Time Database) is it stored in the time database?f. Depth-Lagged (need Triggered-Lag entry) is this a triggered value?g. Calculated (need Calculation entry) is this a calculated value ** doesn'tautomatically allow you

to add calculated parameters – seek advicebefore usingh. Editable (Set-able - need Resource entry) unsure at time of this document i. Boolean (only two values – True/False) is this channel boolean controlled? j. Counter (data only increase - eg. pump strokes) as it saysk. Lock (parameter may not be edited) no user can edit this datal. Alarm High (High Alarm may be set on channel) will you allow a high alarm? m. Alarm Low (Low Alarm may be set on channel) will you allow a low alarm?n. Disable Error (channel won't be set to -9999) should the channel show –"Noincoming data"?o. Hide Channel (channel won't appear in list) should the user be able to see it?p. EXIT exit this channel section

Some notes on this section:

· You can use the right/left keys to move back and forth until your satisfied with your selections.· The word set should appear next to each selection you have set. · If you are editing an existing channel, this list would start with Triggered Lag or not; skips thetime/realtime section which we always turn on anyway.

For our examples:

A) Set items a-f and item p only. B) Will only give the option of choosing f through p.

Next it will ask what category this new channel or existing channel should be in.

Category (use arrow keys): Drilling Parameters

All pre-existing categories will appear, plus the ability to create a new category. If you wish to add a new category it will ask you for the category mnemonic plus the category name. Once created you can assign channels to it at anytime and they will appear in the client.

Next step for adding channels, but second step for editing channels is the Unit class.

Unit Class (use arrow keys): CONDUCTIVITY .

Here you choose one of the existing pre-determined units. There are several to choose from, so scrollthrough until an appropriate unit is chosen. If you are unsure, leave it as none and come back and edit



it later.

Situation A) and B) would both be none for gamma

Now, if editing a channel, you are finished and you can either edit more channels or skip to the Savesection at the end.

!!!WARNING!!! You are about to add a channel. It is very important that you choose the correct settings for theTime-Based and Depth-Based data flags. You will NOT be given another chance to change theseagain, as to do so later would corrupt any pre-existing database! BE SURE!!

Are you sure you wish to add channel 'DFDS' (Y/N)? Choosing yes will save your changes, no will abandon them.

OK, at this stage, you should have either successfully added a channel or successfully edited apre-existing channel. Now you can continue making changes as you wish, but when done and aftercreating every new channel , you must Save the channels. Press "S" to save – if all goes well, it willsay:

Successfully saved channel text!!!Successfully saved channel table!!!

Do this many times while in WWtext to ensure your changes get saved.

When finished:

hit "x" to exit Restart your client and you should see your new channels and categories. Now you can use these new channels to WITS data in, or trigger on.

An example:

Let's go through an entire example from beginning to end. The MWD company has a channel calledResitivity Medium. This data is being sent to you on WITS record 0843. The depth record is alsobeing sent to you on WITS record 0855.

Step 1. Does the channel exist in WW? Use the WWtext command to verify.

Step 2. Create the channel if it doesn't exist. You will need to add in two channels, and in this example I am going to use RMRT (Resistivity MediumRealtime) and RMDP (Resistivity Medium Depth).

Step 3. Edit the WITS program to include 0843,RMRT,0 and 0855,RMDP,0

Step 4. Edit triggers to read RMDP RMRT:RMRT>

This is now complete. Remember to do the following:

WWreload the triggers file WWreload WWwits the WITS file

Now let's take this example further. The MWD is now sending over another channel, called Sonic, onWITS record 0844. It's based on the same depth as Resistivity Medium.



Step 1. Check for channel Sonic.

Step 2. Create the channel Sonic if it doesn't exist. (SONI)

Step 3. Edit the WITS file to bring in 0844,SONI,0

Step 4. Edit the triggers file to now show: RMDP RMRT:RMRT> SONI:SONI>

As you can see, everything follows a pattern. You just need to put in the variables. Do keep in mind that if you are adding 10 channels, for example, that you will want to keep track ofyour progress and what changes you have made, to date. Remember that the next technician to work on the system or who is trying to fix a problem, will have todetermine what you have done, and your progress, before diagnosing the problem.

1.11 Sensor Configuration

All sensor calibration and controls are done through the client software. There are two primary waysthis is accomplished:

· either through the calibration screens which control the physical sensor mapping and the high andlow counts

· through set functions on each particular channel such as in/out slips or WOB.

This section will break down these connections into two main parts

1. Physical channel calibration and mappings2. Set(able) channels

IMPORTANT BSD UPDATE:

For those who are familiar with the older system you were used to the calibrations being saved in/ww/well/UWID/config/dac_sw,dac_hw.... files. The new system stores all the files now in the/ww/well/UWID/config/well.cfg file. This file is of XML format and can be modified directly but it is bestto use the Client configuration or the WWCP when it becomes available. Please make note of this fordefault well configs, etc. All prior templates from older system will not work when bringing theseconfigs over.

1.11.1 Hardware Calibration Procedures

The following channels should ALWAYS be calibrated:

Hookload (HKLI)Standpipe Pressure (SPPI)Casing Pressure (CHKP) (if used)Flowout Percent (MFOP) (if used)Pit Tanks 116 (TV1TV16) (if used)Table RPM (RPMI)SPM13 (SPM1SPM3) (if used)Slip Status (do through WellWizard under Slip Status)Ticks per 100m (do through WellWizard under Hook Position)

The following information should be obtained and entered through WellWizard:



Weight of blocks – enter under "hookload"Weight of Kelly – enter under "hookload"Pump efficiency and pump volume – enter under "pump output"

N.B. the geologist will set the appropriate lag time and lag time increments.

1.11.2 Channel Calibration

Before a channel can be calibrated please ensure that it has been connected and take note on whichbarrier the channel is connected.

The channel calibration and mapping screens are accessible by clicking on WellWizard on the mainmenu and choosing Configure.

It will now prompt you for a password. This password is generated by the server and is userconfigurable. Refer to Well Configuration Password for the password or how to change it.

Once successfully entered you will be given the Channel Mapping and Calibration screen.



Please refer to the sections Channel Mapping and Channel Calibration Analog,Channel CalibrationDigital for further instruction.

1.11.2.1 Channel Mapping

Before a sensor can be calibrated it needs to be mapped from the physical barrier connection to thesoftware. When you click on Channel Mapping it presents you with this screen.

From this screen you can either add a new channel to be mapped, delete an existing mapped channel,view the Real-time data feed to the server (hex values) or print out the current mappings.

ADDING A CHANNEL

Clicking on Add presents you with this screen asking you what type of channel do you wish to add.

Analog -- any sensor that outputs a 4-20mA signal into one of the Analog barriers (ie. hookload,pitsensor)Pulse Counter -- these are essentially digital channels that count 1 by 1 that can be zeroed. (ie.



Strokes 1,2,3)Digital -- any variable digital sensor (ie. SPM)Depth - this is reserved for the depth sensor.

When you click ok it presents you with a list of potential channels that can be matched to the chosencriteria. Pick the appropriate channel. In my example I am going to pick Analog and choose MudTemperature Out sensor.



When I hit OK it shows the channel now existing on Analog 13. If I wished to move this to anotherchannel I would simply input the correct barrier value into the Channel section. If there is any channelmapping errors it will present it to you at this time telling you the problem (such as another channel isalready assigned to this value....).

If you highlight any channel and click on Change Parameter it will give you the same list as the Addfunction and the channel you choose will replace the highlighted channel.

DELETING A CHANNEL

Deleting a mapped channel is as simple as highlighting the channel you wish to delete and then hittingdelete. You will be asked if your sure and if you answer yes the channel is removed from the mapping.

VIEW RT DATA

The real-time data viewed is the HEX values of each channel displayed in a GRID format. This view isuseful when troubleshooting channels that are reading incorrectly or to determine where a channel youhave just added has shown up if your unsure. Clicking on the View RT Data button presents you with



All the channels are listed from left to right starting at the value indicated to the left. The first rowcovers Digital D0 - D7 and will be shown as either 0's or 1's. The Analog channels go from A0 to A64(64 is available only on a extended DAC) with each row representing 8 channels. In this example allthe values are 0 indicating no physical channel is connected except for A13 which is reading roughly4mA in Hex. Please note that the data represented here is not high-speed data and should only beused for reference. High-speed data should be viewed using dac_test from the command line.

PRINT

The print function will make a printout of your mapped channels for your records and for easierviewing. When you click on Print it will ask you which printer to use and then will proceed to print out apage such as the following:



1.11.2.2 Channel Calibration Analog

Calibrating an ANALOG channel requires you to know the low and high values to calibrate the channelto. Generally you only configure one point at 4ma which is usually low but you can calibrate this as thehigh value, and 20ma which is normally your high point. Using a low and high point you create a linearcalibration for all readings regardless of their current value. You may also wish to calibrate more thantwo points and can add as many points as necessary. Multiple points can come in handy whencalibrations aren't so linear, such as when calibrating a Pit sensor and the tank isn't square orcylindrical.

To illustrate how to calibrate a Analog sensor I'm going calibrate Pit 1.

Choose Calibration from the Sensor Configuration menu

Highlight Pit1 and then click on Calibrate -- if you don't have the channel necessary to calibrate referto Channel Mapping on how to add it.

When you click on Calibrate you can now set the low and high points and up to 8 mid points.



1. New Point -- click on this will allow you to create another new point up to a total of 10.2. Delete Point - highlight any point and click on delete to remove that calibration point3. Take Sample -- when you highlight the calibration point you wish to calibrate the Realtime counts

and Rolling Average will display the current and average values for this particular channel. If youclick on Take Sample for either this value will populate into the counts field allowing you tocalibrate that point.

4. Decimal Drop down box -- you can view your counts in either decimal values, hex values or mAvalues.

5. Unit drop down box -- depending on the channel the available units you can use to calibrate withare shown.

6. Calibrate --- once you are happy with you calibrations you can apply them by clicking on Calibrate.

PIT 1 Example

This example shows me changing Calibration point 2 (normally high) using 20mA and giving it a valueof 5m3. If I were to take the rolling counts I would be calibrating 0.018mA to be some value. The



boxes above the unit and conversion value are the calibrated points. In this diagram 0mA is 0m3and 20mA is 5m3.

In this example I have three calibration points for my Pit Sensor all in Hex. My low point is 332B(roughly 4mA) and equals 0m3. I have a mid point calibration at 544F with a value of 3m3 and myhigh value of FF2B (roughly 4ma) at 5m3.

All Analog sensor calibrations are identical in form to these examples.

The usage of rolling average is generally a good idea when calibrating as it eliminates spikes in eitherdirection from your calibration. This isn't always a good idea though as rolling average can take afew seconds to catch up to fast moving signals.

Another suggestion here is to create a third point for the zero readings. If you create a zero reading at4.34mA and your sensor drops below that you will show negative numbers. To eliminate thisproblem create another point with 0mA being 0.

1.11.2.2.1 Example Calibration - DeLaval Pit Volume Sensor

· Run Channel Calibration Analog and select the Pit sensor in order to see the counts beinggenerated

· Move the float to the lower extent of the probe.

· Determine the volume of the tank to which this number equates, either by calculation or by someother volumetric indicator.

For example, the dimensions of the tank are 1.3m wide x 2.0m long x 1.5m deep. With the float in the lower position, the height from the bottom of the tank to mid-float = 20cm.Realtime counts shows = 3308 , hit take sample to move this count to the calibration window.Volume to mid-float = 1.3m x 2.0m x 0.20m (note the unit conversion from cm to m)V1 = 0.52m3, enter this value into the calibration screen.

· Next, move the float to the top of the probe, as high as it will go (typically stopped by the grating).

Height from the bottom of the tank to the mid-point of the float = 1.41m



Highlight the high count calibration and hit Take sample on the realtime counts.Volume to mid-float = 1.3m x 2.0m x 1.41m

V2 = 3.66m3, enter this value alongside the high realtime counts.

1.11.2.3 Channel Calibration Digital

Digital Calibration is really quite simple. Going into the Sensor Configuration choose Calibrate andthen highlight the digital sensor you wish to calibrate and hit calibrate.

When you hit calibrate you are presented with a simple ration screen such as



What this refers to is it takes physically 2 pulses to equal one tick. In this case the Pump Strokesensor would need to change state twice before we would register it as a signal pulse. For instancethe example given to me was a pump stroke sensor on the tri-plex pump located near the bottom ofthe shaft was set to a ratio of 1.6:1, as it was roughly 1.6 pulses to for complete stroke. This showsthat the value is not necessarily a whole number and must be determined.

1.11.2.4 Set Function Calibrations

Many of the channels along with the physical calibration of high and low points also have various setpoints that can be applied. A good example of this would be Hookload. You calibrate the Hookload sensor for it's high and lowcounts, but you also wish to use this same sensor for determining in and out of slip status. For theseparticular channels you have two options to set these variables. Either in the Set Screen or by clickingon the gauge in question and hitting set.

Channels which can be set are:

Hookload -- to set Block, Hook and Kelly WeightSlip Status -- set in/out of slips rangesTime Increment/Depth Increment -- how often should the time/depth database record data. Pleasenote here that a 1s time database will grow 30x more than average and will cause the system toeventually crash. Bit Depth - set current Bit depthHole Depth - set current Hole depthLag Depth - setup the lag depthWeight on Bit (WOB) - set current WOB value, or ZEROTorque - set current Torque value.Active PVT -- setup the pits to include in active PVT

VIEW/SET method

The View/Set method lists many of these channels above in a list that you can pick from. On themenu list choose View and then Sets. Highlight the item you wish to set and click on SET. In thepicture below I have chosen to set InSlip threshold which brings up the in/out slips screen.



Gauge SET Option

Right-click on the gauge you wish to set. In the picture below I am setting the in/out slips by rightclicking on the Slip Status-Out of slips gauge.



You can change your slip status and then click on SET. You can also create a shortcut key andchoose one of the function keys to jump quickly to this screen.

1.11.2.4.1 Example Calibration - Block Movement

Hook Position sets the ticks per hundred meters. This can be done through the Well Wizard Clientunder the Hook Position channel.

1.11.3 Channel Configuration

A typical channel configuration is as follows:

Analog Channel Channel Mnemonic Actual Channel Name1 HKLI Hookload2 SPPI Standpipe Pressure3 CHKP Casing Pressure4 MFOP Flowout Percent5 TV1 Pit Tank 1



6 TV2 Pit Tank 27 TV3 Pit Tank 38 TV4 Pit Tank 49 TV5 Pit Tank 510 TV6 Pit Tank 611 TV7 Pit Tank 712 131415 FUELF Fuel Flow16 TQI Torque

Digital Channel Channel Mnemonic Actual Channel Name1 BMT Block Movement (Depth Channel 1)2 BDIR Block Direction (Depth Channel 1)3(1) RPM1 Table RPM4(2) SPM1 Pump Strokes 15(3) SPM2 Pump Strokes 26(4) SPM3 Pump Strokes 3

Channels may not always be exactly as shown above.

To view your particular channel configuration you can check the dac_sw file (note: this is a binary file).

NOTE: All analog channels have a one to one correspondence with the hardware connector on thejunction box and the analog channel. I.e. junction box channel number = analog channel number.

Digital channels on the other hand, due to the two default depth channels, have a two-channel offsetbetween the hardware channel and the junction box. I.e, channel 1 on the digital junction box isactually channel 3; similarly, channel 2 on the junction box is channel 4, etc.

1.11.4 Calibration Log

Before commencing, it is a good idea to create a DAC Calibration Log in order to record individualcalibrations.

Example Calibration Log

Sensor Low Value Low Hex High Value High HexHKLDSPPIMFOPTV1TV2TV3TV4

1.11.5 Depth and Weight Calibrations

· Ticks per 100m Calibration:

Ticks per 100m = [100 x (#of lines on both sides) x (#of targets)] / [(diameter of sheave in m) X p ]

For example, on a 4ft sheave with 10 lines and 12 targets, the calculation is as follows:



4ft X 0.3048 m/ft = 1.2192 meters

(100 X 10 X 12) / (1.2192 X 3.1415927) = 3133 ticks per 100m

NOTE: measuring the sheave from the middle of cable to the middle of cable works very well; usingthe number stamped on outside does not work so well.

· Hookload Calibration:

The full, correct procedure is shown below, but in reality, calibrate the hookload sensor so that ourweight matches the weight shown on the rig's indicator.

25,000 lbs / 224.809lbs/ton = 111.2055 KN50,000 lbs / 224.809lbs/ton = 222.41 KN

Table of values for high point

Sensor Limit: 8-lines 10-lines 12-lines

25000lbs 889.64 1112.2055 1334.46650000lbs 1779.29 2224.11 2668.93

Low point = Hookload with no weight = 0.0 (counts should be around 3300)

High point = Maximum weight of hookload sensor and number of lines from above table (countsshould be around ff00).

Set the calibration to be the number from the above table using the number of lines on the blocks andthe sensor limit.

For a sensor with a limit of 25000lbs, and for a ten-line rig, the calibration should be:

3300 counts = 0.0 KNFF2B counts = 1112.2055KN

NOTE: The 4mA and 20mA points should already be calibrated before the unit leaves the shop, so thecounts for the Hookload channels shouldn't need to be changed - only the value.

1.11.6 Weight On Bit

You should set this value in WW through WOB settings.

Zero setting When the bit is just offbottom with slow rotation, set WOB to zero. This should bedone every few connections to make sure the weight is kept accurate. The driller's will perform thisstep routinely so it's not a problem



Clicking on the Shortcut Key will bring up the Function key shortcut menu allowing you to assign one ofthe Function keys to this set function.

1.12 Mirroring

Mirroring is the term given to any remote WellWizard servers which hosts a duplicate database. Theprocess of mirroring allows users who are not on location to view the same data without having toconnect through the generally slow connections to location. It saves bandwidth and provides the enduser with a much greater sense of the daily operations at wellsite.

Basic outline :

1.12.1 What is a Mirror

The mirror server is a mirror or a reflection of the wellsite server. It behaves much like a mirror andthat every detail is perfectly reflected, but unlike a mirror, everything is in the same order. The mirrorrefers to any OpenBSD server that is connected to another OpenBSD server and contains a real-timeworking copy of the connected database. So you now have two servers showing exactly the same



thing.

1.12.2 Mirror Configuration

First we need to establish a connection between the two servers. They can only maintain a connectionif they have a dedicated connection between the two. This can be by satellite or landline. Howeveryou do it, it needs to be there.

Secondly we need to determine the mirror configuration. Which well is going to be mirrored and whereare we going to mirror it to, and who is going to initiate the mirror?

Before you begin, be sure to have the IP's of both wells, and be sure each well can ping each other toensure a connection. This may not always be possible when going across remote networks as someadministrators block ping requests.

In order to make the process clear I am going to go through a hypothetical mirror configuration.

Wellsite Server is at IP 192.168.10.1 and contains a well called demo. I wish to mirror this well toanother server located at the main office. The server, which will show the mirror, is at IP64.201.174.36. They are connected via satellite.

One thing to keep in mind before going through the setups for each server is to know which server isgoing to initiate the connection. Default method is to have the wellsite system initiate the connection tothe mirror sitee; thus pushing the data out. The process can be reversed in situations where the mirrorsystem has full control of the wellsite system (remote administration).

1.12.3 Wellsite Server Setup

Assumption at this point is that you have a Logging Well on your wellsite server.

ssh into your server.

WWsetup – choose system managementSystem: Create New Remote System Entry

Choose to create a new remote system entry. You can create as many as you need but you mustkeep track of which is setup to mirror which wells. Best to keep this list to as minimum as possible. Ifyou make a mistake, finish creating the entry and then press delete to erase it entirely.

Enter System Name: This is where you enter a unique system name. This isn't used for anything elseother than for the users reference to keep things straight, so for my example I am going to call this"junior".

Enter System Username (used for login): This is used to ensure that the correct well is being mirroredby requiring both sides to know each other's login. This login must be unique to the mirror. Don't useroot. Use something relevant. In my case I am using "Bigbrother".

Enter System Password (used for login): What password will these systems use? I will use thepassword of "watching"

Will local system initiate connection? (y/N) : Now this is very important, which system will initiate theconnection, only one side is allowed to do so. As a rule the wellsite system will initiate so say Y(es) tothis option.

Use PROXY Server (y/N)? Is there a Proxy server involved.Tunnel over HTTP (y/N?) Do we wish to tunnel(SSL) over port 80 (www) Use SSL (Y/n?) This is the preferred connection over port 5001Enter IP of remote site: (this is the IP of the mirror system)



Enter Port to use: (hit enter for default port given)

Select Well(s) to Mirror to this systemWell Select - use arrow keys and ENTER to select. Select 'Exit' when doneWell 4: demo (W0004BF0003B2GIT75S) MIRRORED

This section allows you to choose which wells you want to mirror. When you have chosen the well youwant press enter and the word Mirrored will appear next to it. If you make a mistake here, it is best tofinish the process and then delete the entry by hitting the delete key. You can set as many wells hereas necessary, but generally you will only mirror the active well. Other wells you will wish to archive andrestore with WWdbm.

Now that were done creating the entry, the WWsetup program will show your newly created entry. Press "i" to show details.

System Name: junior LSID: 1 USID: Username: Bigbrother Password: watchingConnection Data: Type=LAN;Host=64.201.174.36Connection Rate: <connection rate currently not supported> Mirror Data: W0004BF0003B2GIT75S

I created system management entry junior, with logical system entry of 1. Username and password asshown, mirroring well W0004BF0003B2GIT75S, going to HOST 64.201.174.36

1.12.4 Mirror Server Setup

ssh into the server.

WWsetup – choose system managementSystem: Create New Remote System Entry

Choose to create a new remote system entry. You can create as many as you need but you mustkeep track of which is setup to mirror which wells. Best to keep this list to as minimum as possible. Ifyou make a mistake, finish creating the entry and then press delete to erase it entirely.

Enter System Name: This can be whatever you wish. I am calling mine SeniorEnter System Username (used for login): This must match the wellsite login. So "Bigbrother"

Enter System Password (used for login): Again, this must match the wellsite. "watching"Will local system initiate connection? (y/N): As the standard for all mirrored wells, the mirror shouldnot initiate the connection – so choose no.

Next it will ask you which well you wish to mirror. Usually the mirror server only receives data, but ifyou wished to share a local well with the wellsite server, choose your well UWID here. In the exampleof the junior/senior geologist, the junior could send his well to the senior, and the senior using thesame LSID could send his well to the junior.

System Name: Senior LSID: 1 USID: Username: Bigbrother Password: watchingConnection Data: Connection Rate: <connection rate currently not supported>



Mirror Data:

As you can see this is slightly different than the well server. Different system name, but sameusername/password. If I had chosen to mirror a well back it would be listed here.

1.12.5 Starting the Link

Now that both systems have been setup you will want to do the following:1. pkill WWlink on both servers2. On the server to initiate the connection "WWlinkup ?" where ? is the LSID of the system entry. Youcan have multiple ones setup so make sure you take note of which one is correct and use this one forall restarts.

If all is setup up properly you should almost instantly see the creation of a new well called Remote onthe mirror server. Do a "qw" and you should see the following style of entry.Remote Inactive W0050C202A6E8GGQ9NJ Demo

The creation of a well that isn't local will be Remote (meaning the data wasn't collected locally) andcontain the UWID of the sending server well and its name. Note that the UWID's are the same eventhough on different servers.

Now to see what it is actually doing type the following command:

WWtestlink

If no connection is made, it will say Link inactive. In this case, try slaying WWlink and restartingWWlinkup again. If this doesn't help, verify connection by pinging the opposite server and checkingthat passwords match.

If connection is good, the well is created and you will see:

Mirror#1 Status: System 2: mirror Well 4: demo Initiated LAN Link to 192.168.10.1:4999 State:Authenticated Update State: S100.00% T100.00% D100.00% F100.00% TX100.00% Last Realtime Received : Wed Aug 29 18:48:04 2001(999132484) Last Transaction Received: Wed Aug 29 18:47:55 2001(999132475)

This will repeat over and over again. What it tells you is that Link was initiated on the following IP andport and that it was authenticated – meaning login/password accepted. Update Status referencesseveral items:

S(chema) – config and registry from the wellsite system. 100% means it has come overcompletely

T(ime)D(epth)F(iles)TX(transaction total)

Last Realtime Recieved: like it says, when is the last time you received a real-time record.Last Transaction Received: transaction record received when. Good for troubleshooting when mirrorfails, as to when it failed.

Once the connection is made, the two wells will be identical in all ways. If connection is lost, either bynetwork going down, or a hiccup in the system you will not need to restart the link as a rule, as it willpick up when the connection is re-established. The mirror will also completely resync itself after



having been down for a period of eight hours.,so if your server is not mirroring;and then picks up eighthours later, expect to see it resyncing the schema and starting over.

If the mirror refuses to start I would suspect that the username and password are not equal on bothsides. This is a common mistake. If these are equal check that the proper ports are opened or thatthe IP's you are trying to use are correct and accessible. Please contact your IT department to verifythe ports and IP's. Many times this takes some back and forth calls to get the proper ports opened upand configured correctly. I have seen firewalls that will allow incoming but not outgoing; so our serverscan see each other one way but not the other. The same issue affects the clients to when goingoutside of networks.

When doing a mirror be sure to provide and or ask for the following:

1. What is the IP of the wellsite server?2. What is the IP of the mirror server -- firewalls are often restricted to certain IP's and ports.3. Port to be used is 5001 for SSL or 4999 for non-SSL unless Proxy is required.4. At least 16 KB/s of bandwidth. We can do with less but ask for this as a minimum.

1.13 Interface

One of the original uses for the WellWizard software outside of EDR is the use of the QLOG –WellWizard Interface. This is the means where the QLOG database is replicated to WellWizard,where several clients can connect, view data and use the power of the WW interface rather then theQLOG interface.

1.13.1 Requirements

- A server of some fashion can be a Mini-Wizard, EDR, and Desktop.- a well created with the QLOG-WW Interface- A qlog database- a null connection from QLOG to WW box – serial to serial- both sides set to 38400 baud, no parity, 1 stop bit, 8 bits- QLOG port cleared of all options – no etab, ers, edel, igate, oflow, and hflow.....

*** NOTE *** Port 4 is the default. If using a Mini-Wizard you will have to modify the registry to useport 1. See the registry note on how to make this specific change.

1.13.2 Command to Start Interface

Once the hardware and software are setup, you need to issue the following commands to QLOG:

1. Start QLOG as normal, starting all admins – including database admin2. Start "hotback +i &" - beings hotbacking the database to the interface3. Start "WWInterface p=port &" - starts the actual interface process from defined port

Command to use to sync over time: WWTSync & - use only under advisement.

Log into the WellWizard server, type the following command "WWtestint -Wx" (where x is LWID). Youshould see the message "cooked data ............." repeating every second and once a minute "time.....". If you see this than the physical connection is made and your data is being ported across. If not,check baud rates, options off, and restart the Interface up.



1.13.3 Mapping Channels between QLOG and WellWizard

Ok so now your data is streaming across, but where is item xxxxx that I just added into QLOG, whereis this other data, why does this data not add up. How do I add in new channels to WW that I havecreated in QLOG?

The art of mapping comes into play now. I suggest reviewing the notes on WWtext as this appliesheavily to this section. First let's discuss the QLOG side of the Interface.

MAPPING – QLOG SIDE OF INTERFACE

The QLOG side of the database controls the entire Interface operation. Whatever is done to QLOGautomatically happens to the WellWizard server. Keeping this in mind, any problems you see on theWellWizard screens should be checked first in QLOG to make sure that the problem doesn't exist firstat the source. If QLOG is wrong, WellWizard is wrong. Ok so what files control the Interface.

/datalog/text/display.txt

This is the only file we need to be concerned with when mapping over to WellWizard. Take a look atthe file and you'll notice the following structure:

QLOG database Number Unit Indicator Item Name0117 01 Hydrocarbons

This repeats all the way through from item 0000 to item 0350. When you add a channel to QLOG youmust edit this file and include that channel, so we use this file to help WellWizard to determine whatdata belongs to what item. I strongly suggest having this file displayed at all times when you actuallyperform the mapping, or at least a printout of the file.

MAPPING – WELLWIZARD SIDE OF INTERFACE

WellWizard receives from QLOG a string of data, and we need to tell WellWizard what is what in thissingle data stream. This is not unlike Wits, where we assign each incoming channel to a mnemonic,but in this case we assign a portion of a stream to each mnemonic. The file that this takes place inand again the only file of consequence is the qlog.map file located in /ww/well/UWID/config. By editingthis file we can take any part of the incoming stream and place it wherever we wish.

Excerpt from the qlog.map file:

# QLOG to Well Wizard Data Mapping# Format:# Well Wizard Mnemonic, QLOG Cooked Index, QLOG Data Offset, QLOG Data Type,# QLOG Data Size, QLOG Data Class, QLOG Data Unit, QLOG Decimals## NOTE: Decimals are loaded into the structure from the decimals file if# the Decimals is value is -1#RPMI,0,0,S32,4,1,0,-1 SPM1,1,4,S32,4,1,0,-1SPM2,2,8,S32,4,1,0,-1SPM3,3,12,S32,4,1,0,-1SPM4,4,16,S32,4,1,0,-1STK1,5,20,S32,4,0,0,-1TQI,46,184,S32,4,9,1,-1

So what does all this mean? Take the first line:

RPMI (rpm) is the channel for data to be mapped to or WW mnemonic,



0 is the QLOG cooked index -- basically this value means the first data item sent in the stream,remember datalog.txt0 is the offset, each data unit is 4 bits in length, so take the first number x 4 and you get the offsetvalueS32 – 32-bit integer, QLOG data type, all data we map will be this format4 is the data size, again all will be this size1 is the data class – as taken from datalog.txt in qlog0 means, place into the default units for this channel-1 is the indicator to take decimal places from QLOG – standard is 3 for all

All the channels we add will be copycats of the RPM, SPM's, etc, with the exception of Torque, whichyou see is located at index 48, offset 184 (48x4), unit class of 9 but take the data in as being in ft/lbinstead of amps. You can change this if necessary for running mappings.

MAPPING – BRINGING IT ALL TOGETHER

So I now I can follow the qlog.map file and I have my datalog.txt file from QLOG. If you take a look atthe datalog.txt file you will see the first item in it is RPM at item 0, you will see in qlog.map that rpmihas an cooked index of 0, datalog.txt rpm is 0, cooked index of 0, datalog.txt 0, cooked 0, see thepoint I'm trying to make. Each and every item in qlog.map has a cooked index that matches withdatalog.txt file locators. So let's say you add a channel into QLOG called Gamma2 into datalog.txt atitem 280. In datalog.txt line 280 would read, 0280 00 Gamma2. You would then input the data intothis new channel. But you will notice, no WW channel called Gamma2 and your data is going intoGamma Ray. How is this possible? Take a look at qlog.map and follow the cooked indexes downuntil you find 280, it reads MR,280,1120...... -- which means Gamma Ray is the 280th item in the datastream at bit 1120 for four bits. The qlog.map isn't smart enough to know that you changed the QLOGside so we need to take care of the mapping for WW. Obviously we would need a channel calledGamma2, for this demonstration let's give it a mnemonic of MR2 (making sure that you had a channelalready existing or created the channel using WWtext) we would proceed to edit qlog.map to showMR2,280,1120.... Restart the Interface and there it is, Gamma2 with Gamma2 data from QLOG. Thisis how it works for all channels. Now keep in mind that the basic default mappings are already takencare of for you, so as long as you don't modify QLOG you don't need to worry about mappings, but ifyou do modify any part of the datalog.txt file, you do need to worry about modification.

Let's do another example to help clarify things.

The example would be a GasWizard connected to QLOG being wits'd into channel 88. You edit thedatalog.txt file to show 0088 08 GasWizard. You start up the Interface and there is no channel calledGasWizard, so you create one. Still no data in GasWizard. Look at the channel CO in gasparameters, there you'll find your data. Why? In qlog.map the line shows CO1,88,.... which meanstake item 88 from datalog.txt and place into CO. So you either edit the qlog.map to show GW,88 (GWbeing the mnemonic created for GasWizard) or you could add the line:

CO1,88,352,S32,4,8,0,-1 GW,88,352,S32,4,8,0,-1

-- which would map the GasWizard data from QLOG to WellWizard in both locations of COand GW.

1.13.4 Troubleshooting

1. Where is the Triggers file, don't I need to edit it to lag my data.No, when using the Interface the WellWizard system does absolutely no data manipulation.

All data manipulation is done on the QLOG side. No triggers, no wits, no nothing other then WWInterface.

2. I am trying to Wits some data into another port, but my data won't show?



When using the Interface, everything else is invalid. First WWwits wouldn't be normallyrunning, and even if you did start it, remember that the WW is set to Interface

which mirrors the QLOG database completely, so any changes introduced by Wits would beignored. Wits all data in QLOG.

3. OK, I edited the qlog.map but my data is not showing up?Did you restart the Interface command on QLOG? Also check in the qlog.map for conflicting

lines where a mnemonic is assigned to more than one channel. The higher indexvalue will overwrite the lower value. i.e. MR,280.... should be the data you think your receiving

but further along in the qlog.map file is MR,328... which means the value from channel 280 will be replaced with the data from channel 328.

4. I start the Interface but nothing seems to be happening?Almost a guarantee that in QLOG you have the options on, if so remove them, or better yet

remove them permanently in /config under init.cti.8. If this isn't your problem, I suggest starting a qterm on the QLOG side and qtalk on the WW side and try to send data

back and forth. If you can, your comm. line is ok, if not, check to make sure line is nulled. If garbage comes across check your stty settings as they should be 38400,n,8,

and 1. Once confirmed cabling is good, restart the interface and run the command on WW "WWtestint -Wx". You can also keep the qtalk open and you should see

"8uxx" coming through every second.

5. My data in WellWizard just disappeared?First remember that WellWizard mirrors the QLOG database. Is the QLOG database there?

If you remove the QLOG database, make sure to shut off the interface, or else the QLOG says I have no database, and WW will remove its own database in response.

6. My readings in WW are wrong?Again, first check that they are correct in QLOG. If so, check qlog.map to make sure that they

are coming across in the right units and no special code has been applied to them such as the TQI example in the notes above. Did you remember to restart the

interface?

7. Ok, lost the QLOG database, had to recover and now I am starting a new well. Restarted theInterface and depth is there, but where is my time database?

In this case, the time database isn't being sent over, because it's historical and Interface ismore concerned about having the depth database in place. I would suggest letting

the Interface sync over until all depth records are caught up and then issue the commandWWTSync & from QLOG. This will start at record 1 of the QLOG database and

start to transfer it across. Remember this can take a long time depending on the size of thetime database, and you will have to have the time database handy and unzipped.

WWTSync r=xxxx & will start the time sync from the specified database record number. Useto fill in blanks. Once the Time is synced up be sure to slay it on the QLOG

side as it will continue to run and chew up resources.

8. OK, everything is setup, everything is coming across, still no data in WW.Ok, check the registry to make sure the interface is using the same port as your using. By

default this is port four, so all if using a system other than a Micro-Wizard check that your connected to port four, and the registry is set to port four. May be that the previous

job someone reset the registry to default to another port. See notes on theregistry for instructions on how to check.

9. My time in the Wellwizard is wrong, QLOG is ok though. The time is taken from QLOG so in reality the QLOG time is wrong. You may have issued the

date command to correct your time but your timezone is wrong causing the WW to pick up the wrong time. Fix your /config/timezone file and then adjust your date(time)

and then 'rtc at +s". Restart the interface and your time will be correct now.



1.14 WellWizard Client Software Installation

The first step is to download the software from the WellWizard server to the client's computer usingthe clients Browser (IE,Netscape,Mozilla) and connecting to the IP of the server which is generally192.168.10.10. This will bring up the servers apache webserver page and allow for direct download ofthe latest client installed on the system.

1. Enter in IP of the server (default is 192.168.10.10). If you have proper networking setup you will bepresented with the main webpage.

2. Click on Download WellWizard Client. The next page will ask you if you are using Internet Exploreror Netscape. If you wish to keep a copy of the installation file choose Netscape as this will allow you tospecify the location of the setup file to be saved. IE install will automatically start the installation.

For further details refer to the User manual of the WellWizard client.

1.14.1 Modifying WellWizard from Default to Driller's Terminal

The WellWizard client installs as either a Desktop or Touchscreen mode. The Touchscreen moderemoves many of the menu options and installs several controls optimized for Touchscreens and theDrillers requirements. To change an installation it is easier to modify the windows registry. Pleasetake all precaution when working in the registry.

HKEY_CURRENT_USER\Software\Datalog there is a key called DrillersTerminal. By default this keyvalue is 0. To make it a touch screen modify this key and remove the first 00 and replace with 10. Save and exit and restart your client. It will now be in Drillers Mode.

1.14.2 EDR Version Client

The EDR version of the client to be turned on must have the following key added to the registry.



[/System/Config/]"SystemMode",ASC,NONE,"EDR"

1.15 Security

The Server is protected by passwords. Not every user needs to know these passwords. Rememberby giving access to an user you are giving them access to the very core of your well. So please restrictthese following passwords to need to know only.

Server Password – default is root/root. Type passwd to change the password. I recommend allpasswords be changed for all servers. Use the same password for all and rotate them on a regularbasis. If a password is forgotten then you will not gain access, to correc this refer to Lost RootPassword.

Sensor Config Password - this is defaulted to some different gibberish value on server initialization.To set this password ssh into the server and type "WWpassword". This password will then be used inthe client software in the configuration page to gain access.

User login password - User logins are controlled either by the WellWizard Control Panel or thebackside (WWsetup). Each user must have a unique login and password to access the wells. Theservers enforce one-shot passwords which means no two users may connect with the same login.

Advanced Commands 82


2 Advanced Commands

2.1 client_tcp

The client_tcp command is basically a version of the WellWizard client that runs command line on theserver side. It is often used for troubleshooting the system or for setting variables that the official clienthasn't yet implemented.

Be sure to do a "man client_tcp" for further examples and other optional flags not covered here.

One of the most powerful features of client_tcp is that in fact it does behave like a WellWizard clientwould and will connect via the same process to the server. This is useful is you are having issues withthe clients connecting as you can make a direct connection yourself and eliminate the server frombeing the issue.

Also using it's get_set option we are able to set functions that are not yet released into the client. Thisis often the case with special request items or bug workarounds.

Refer to the examples for more ideas on how you could use this program. Please note that you doneed an available user to use client_tcp.

2.1.1 Time and Depth Queries

Time & Depth Database queries:client_tcp -cdb_query -d"lwid type start end channel_mnemonic_1 ..."

where:lwid is the logical well idtype is table type ( 0 for depth, 1 for time)start is the start of the query (-1 for start of dbase)end is the end of the query (-1 for end of dbase)channel_mnemonic_N are the mnemonics of the desired channels

NOTE that start and end times are specified the same way the 'date'command is used. Namely: [[[[CC]YY]MM]DD]HHMM[.SS]

Time database query to well 2 on the local system:client_tcp -cdb_query -d"2 1 -1 -1 TIME SPPI"

Time database query from 10am to 1pm today on well 7 on 207.153.34.111:client_tcp -cdb_query -d"7 1 1000 1300 TIME DMEA" 207.153.34.111

Depth database query from 1000 to 2000 meters on well 1 of localhost:client_tcp -cdb_query -d"1 0 1000.0 2000.0 DMEA MG"

Time Queries using both local time and GMT time: GMT using the -g optionclient_tcp -cdb_query -d"33 1 0000 -1 TIME" 192.168.3.34 (get all time database entries for currentday)client_tcp -cdb_query -d"33 1 0000 -1 TIME" -g 192.168.3.34 (get all time database entries for currentday in UTC).

When exporting data using the above examples you can also dictate the unit that the channel ispresented in. For example, to get Methane in ppm you would specify "METH:1" as the mnemonic. Theunit ids are the same as is used for WITS configuration.



2.1.2 Realtime Viewing

Realtime data of a well:

client_tcp -cdata_test -d"lwid channel_mnemonic_1 channel_mnemonic_2 ..."

where:lwid is the logical well idchannel_mnemonic_N are the mnemonics of the desired channels

eg.client_tcp -cdata_test -d"3 TIME DMEA DGM MG"

When viewing data using the above examples you can also dictate the unit that the channel ispresented in. For example, to get Methane in ppm you would specify "METH:1" as the mnemonic. Theunit ids are the same as is used for WITS configuration.

2.1.3 Setting Variables

This function of client_tcp is used to set variables for channels.

client_tcp -cget_set -d"lwid mnemonicI"

where:lwid is the logical well idchannel_mnemonic_N are the mnemonics of the desired channels

Example below is showing the setting of Hookload (HKLI) on well #2. Answer the questions as theyare presented for the particular channel to set the variables.

# client_tcp -cget_set -d"2 HKLI"Hostname:localhost, Port:4999Username: xxxxxxPassword: *******Server's version: 5.1.7 Mon Mar 13 09:43:20 MST 2006wid:2 cmd:'GET HKLI'msgw.get_reply.result: -1Command 'GET HKLI' SUCCEEDEDgot resource id#30 (size: 28)Hookload resource for 'GET HKLI'Block Weight: 0.000000 Hook Weight: -9999.000000Kelly Weight: 0.000000Enter New Block Weight(press Enter to skip):

2.2 WWpad

The WWpad command is useful for creating or removing time or depth entries from the database. This command should be used with caution as incorrect usage could cause you to lose all data points.The idea behind it is that if a section of data is missed either by the system not being present duringthat time or some sort of trouble on site causing depth or time data points to be missing you can'timport the missing data into the system as no records exist. WWpad helps in creating the missingrecords to allow a full log to be presented. It also has the option to remove records for sidetrackpurposes or any other reason required.

CREATING RECORDS:



command: WWpad

This will present you with a list of available wells. Pick the correct well to insert records into. It willthen ask you if you wish to pad depth or time. If you pick depth you will then be asked if padding inmeters or feet.

Then you pick your range. For time use the right/left arrow keys to switch between year,day,month,hour.... and up/down to make changes. Hit enter to enter the second point. \

Interval point - for depth this value is normally the interval of the existing data. For time it is normally30seconds. Any chosen variable though can be entered.

The system will then tell you what it will do, padding the records from point X to Y using interval Z. Doyou agree? If you say yes it will generate the records.

The system is smart enough that if a records already exists it will skip over it. But with depth bewarned that real intervals are never 100,101 they are 100.03228 and 101.334 and if you pad over thisinterval you will have records at both 100 and 100.03228 which will look very spiky on the client.

REMOVING RECORDS:

WWpad -P

This function will do the opposite of WWpad, it completely removes all records from point x to y. It isused the same as WWpad, you pick your well, prune depth or time and the upper/lower boudaries. Unlike WWpad though there is no interval - everything between the two points will be removed.

This feature is quite useful for sidetracks in that you can remove a previously recorded section andreplace with a new one. This feature is permanent so be sure to have a WWdbm backup of the wellprior to proceeding.

2.3 WWsim

WWsim is a useful command used to simulate desired data. I highly suggest reading the man pageson this command for detailed explanation.

Basic usage:

WWsim -Wlwid -dmnenomic:variable

withlwid being the logical well id of the well you wish to simulate data tomnenmoic being the server side mnenomic for the desired channel to simulate (SPM1 for pump stroke1)variable being the variable that you wish the value to present.

This command does not allow for a range of variable but only static values to be simulated. For arange please contact your local Datalog Tech support line for information on using WWdac_sim.

WWsim -W1 -dSPM1:100

This command would simulate SPM1 to show 100 on well 1 rather than no incoming data.

WWsim -W1 -dSPM1:100 -dSPM2:10

This command would simulate SPM1 to 100 and SPM2 to 10 on one command line.



2.4 Registry

The WellWizard registry holds all the relevant data on your system and must be protected at all costs.If your registry is lost you will lose easy access to your data. Your wells will appear to not even exist,even though the directories and files remain on the Harddrives.

The registry system backs itself up every night at 12:01am to a file called /ww/backup/backup.reg. This happens every night at midnight, so be sure to have your system turned off at midnight if youhave just lost your reg, because it will overwrite the previous backup with the corrupted copy. Theregistry now is partially self-healing and will fix itself automatically if powered off incorrectly. If you findthat you have no data available on a reboot be sure to type WWboot and verify that WWreg is running.If so and under advisement type the following command:

“reg –c import /ww/backup/backup.reg”, followed by “WWboot”

Now if you do need to do any work in the registry type the following command first:

“reg –c export /root//filename”. You then have a current backup of your system settings. You can thenalso do a less on this filename and browse through the settings without actually going into the registry. A SAFETY PRECAUTION.

Command: regImportant usages: “ls” will list the directory of the current position, “ls –l” will list the attached keys, “cd”will change directory in the reg, once executed use the up/down keys to navigate up/down the currentthread, use the left/right arrow keys to jump across threads.

Registry Commands:cd dir [sub] Change Directorycp src dst Copy Entryexport filename Export current directory to specified fileimport filename Import from specified fileln src link Create Symbolic Linkmd dir Make Directory (mkdir also works)mk key [options] Make Keyrd dir Remove Directory (rmdir also works)rm entry Remove Entryls [options] [entry ...] List Directoryfind entry ... Find Entrypwd Print Working Directoryevent [event] ... Generate Registry Event(s)? or help This Helpexit or x Exit

The Make Key command options are as follows:mk name [type] [class] [value]Output may be redirected to a file.

The List Directory options are as follows:-R Recurse-L Resolve symbolic links rather than showing them-a List entries whose name begins with a period-o same as -l-l List with data information Go ahead and type this command (but only on a non-used server, so if you screw up, no one is goingto care)

Once in you will see



/> ---- this is the root of the registry, type ls here and you will see the following list drop down:

/Wells//System//Systems/

When in the “reg” command, “x” will always back you out to the command line. Now the reg system iscontrolled by WWsetup. You will notice that the reg follows the WWsetup structure so if you have readyour notes and understand the setup of the server and the mirror section this will all make good senseto you.

/Wells/ are the wells you create. /System/ is the Server Setup section of WWsetup. /Systems/ is thesystem management section, which of course is the mirror handling section.

2.4.1 Example usage of Registry

An example usage of the Registry system would be modifying the registry to go into EDR mode fromnormal mode. This can be accomplished two different ways.

Example 1.

enter the registry by typing "reg"

1. #reg2. />cd --- type cd to change directory (we are going for the System directory)

At this point you need to envision the directory structure as a tree. The up/down arrows will take youup and down through the directory levels. The right/left arrow keys will take you back and forth throughthe file level.

3. Using the up/down keys navigate until you get to "CD: //System".4. Use the right/left keys to now navigate to the next directory level "CD: /System/." (one right arrowto .)5. Use the down keys to now navigate to "CD: /System/Config6. Now one more right arrow to navigate into the Config directory "CD: /System/Config/."7. Hit <enter> to exit cd mode8. type "ls -l" to see the current directories and files at this point in the registry9. Let's make the SystemMode entry if it doesn't exist --"mk SystemMode"

If you make any typos you can't correct them. Finish through and then simply "rm typo" and removethe typo and repeat.

10. Following the prompts, we wish to use "string" <enter>11. Value should be "EDR"12. Type "ls -l" and you should see /System/Config/SystemMode(string): EDR13. Exit out of the registry by typing "x"

Example 2.

Doing the same option via a file given to you. This example is used to demonstrate the use of theexport/import function of the registry.

As we mentioned earlier we do not want users messing around in the registry system as you couldpotentially lose all the data if you weren't sure on what you were doing. This registry system is nodifferent than the Windows Registry - it holds all the keys.

As such if a user required to do the change in Example 1 it would be better for a senior tech to send



them a file to be imported rather than manipulating the registry directly.

1. Senior tech does the change above to his test system2. "reg -c export /tmp/x"3. Edit /tmp/x to remove everything but

## WellWizard Registry File #[/System/Config/]"SystemMode",ASC,NONE,"EDR"#<<<FINSIHED>>>

4. tar the file up and send to user5. user untar's file and types "reg -c import /tmp/x" and the file will import

[/System/Config/]"SystemMode",ASC,NONE,"EDR"

Networking 88


3 Networking

This section covers the basics to get you up and running with your server on the network. Theinformation presented here is a reference only and for real understanding of how networking happensrefer to the many resources available online or at your local bookstores.

3.1 Terminology

TCP/IP Packets

· Data is encapsulated/enclosed in a special data carrier packet.· The packet has a source IP address and a destination IP address.· The packet also contains status information and a checksum.· A packet will always contain 20 to 24 bytes for addressing information.· It may contain from 1 to 1478 bytes of data.

Routing

· Communications between TCP/IP networks.· A router is a special host.· A router doesn't care what data TCP/IP packets contain.· A router only needs to know how to pass packets along to the next router.· Each host needs a "default route". · If the destination IP is not a part of the local network, the packet is passed to the router.

The Stack

· All TCP/IP aware hosts have a TCP/IP stack.· The stack routes data to and from applications on the host.· Socket (OpenBSD4), WINSOCK (Windows).· Applications push data on to the stack and pull data off of the stack.

Ports

· A port is used as a secondary address on a host.· A particular port is usually assigned to a particular function.· In WellWizard, the port is 4999, 5001 and 80.· Analogy: call an office number (IP address) and enter an extension (port).· Port numbers can range from 1 to 65535.· Port numbers below 1024 are usually reserved for "well-known services".

Services

· Port numbers are assigned to services.· The assignments are known to all systems.· ftp (port 21), telnet (port 23), smtp (sendmail) (port 25), web (80).· WellWizard uses 4999 which is only known to Datalog.

Client/Server

· Any application on a host which provides a service is a server.· Any application on a host which requests access to a service is a client.



· A server "listens" to a port, waiting for a client to request service.· The WellWizard client on Windows host requests service from the WellWizard server on a

OpenBSD4 host.

Daemons

· Usually distinguished by a "d" at the end of the name, e.g. sshd, ftpd, dhcpd, named..· They sit quietly in the background, listening on a port.· When a "master" daemon receives a request, it starts another copy of itself to handle the

service request, then goes back to listening.· It can also be started by inetd, which listens on many ports and starts daemons to handle

client/server communications with each client, depending on the port.· ssh client connects to sshd. · ftp client connects to ftpd.· "named" is the DNS name server.· "dhcpd" is the dynamic IP address assignment.

Firewall

· A special router that inspects TCP/IP packets as they pass through. · It will block packets that are destined for forbidden IP addresses or ports, or that contain

forbidden contents.· Firewalls must permit port 80, 4999, or 5001 to pass for a client behind the firewall to connect

to a WW server.

Security

· Standard UNIX username and password.· /etc/passwd contains the user account information.· /etc/smaster.passwd contains the user password.· DO NOT edit the password or shadow files, because if the root password is corrupted, no

logins to fix it will be possible.· Standard utilities (telnet, ftp, web) are plain text.· "Sniffers" look at network traffic and can extract the usernames and passwords.· Proper passwords are more of a concern when a system is live on the Internet.

Ping

· Sends a "test packet" to a destination IP.· A response indicates a valid connection exists.· Missing reply packets indicate a slow link.· No response indicates that there is a complete failure of any connection.

traceroute (tracert in Windows)

· Sends ping packets and determines all routers that handle the packets on the way to theselected destination IP.

· Very useful for determining where a link has failed.

Important files

/etc/wwnet.conf - contains definition of the network IP's (shortcut instead of using hostname.xxx)/etc/mygate - the gateway address used by the system.

Networking 90


3.2 BSD Networking

The OpenBSD system is built to be anything we need it to be and this includes a wide range ofnetworking options in order to connect to other systems.

For the majority of users being able to configure your IP and gateway will be the extent of yournetworking requirements. For others being able to build routes, troubles connections will require amuch higher level of knowledge.

3.2.1 Setting IP

The IP for your system is assigned through two files:

/etc/wwnet.conf -- sets the IP of your system/etc/mygate -- set the gateway value of your system.

The file wwnet.conf was specifically written for the WellWizard system to make it easy for all users tochange their IP's. Technically in the system every network card installed will be found on boot-up andare assigned an acronym. Generally in the Shuttle systems this will rl0. Intel cards are normally fxp0,dlink cards are eth0.... The file that these are associated with is hostname.xxx or in the examplesabove hostname.rl0, hostname.fxp0. For the general user to determine which hostname file togenerate and then to put the correct values into it was to much so wwnet.conf is used as a standardway to address this problem.

A default wwnet.conf contains two lines:

inet 192.168.10.10inet alias 207.216.230.180

This sets the primary IP to 192.168.10.10 with a secondary IP to 207.216.230.180. This means thatthis server will respond to requests on both IP's and can find addresses on both IP's that are local.

To edit your IP simply nano wwnet.conf and change the IP values to the desired values.

For these changes to take place you must reboot your server. To change the IP on the fly please referto ifconfig.

3.2.2 Setting Gateway

To set the gateway of your system edit the file /etc/mygate to be the correct value.

This file should only contain one line with your gateway -- NO #'s allowed, no keeping the old gateway-- one line and one line only.

3.2.3 netstat

The "Netstat" command symbolically displays the contents of various network-related data structures --as from the man page on netstat.

netstat command is useful to the WellWizard tech to verify that many of the networking optionsconfigured are actually inplace and working. As always do a "man netstat" to see the many differentoptions and feel free to mix and match to find what you need to know.

Basic netstat commands:

netstat -r | less - shows gateway address (see route for more details)



netstat -nI de0 -- shows all current connections for network device de0

3.2.4 ifconfig

Definition of ifconfig taken from BSD man pages:

"The ifconfig utility is used to assign an address to a network interface and/or configure networkinterface parameters. ifconfig must be used at boot-time to define the network address of eachinterface present on a machine; it may also be used at a later time to redefine an interface's addressor other operating parameters. "

Uses as they apply to the WellWizard BSD platform.

"ifconfig -a"

This command displays all the currently available network devices and their attributes. In the screenshot below (taken from my local demo box) you will see five different devices listed.

lo0 -- this is your localhost, loopback. It is assigned the IP address of 127.0.0.1 and is used for internalnetworking.de0 -- on my box the network device is detected as de0. Other units might show up as rl0, fxp0,en1.... depends on the driver best suited for your device. This will generally be the network device ofinterest as this is the one used to connect to the outside world. In my example below my device (de0)is assigned the IP 192.168.10.9. This IP is acquired from wwnet.conf which writes to the filehostname.de0.pflog0 - part of the internal networking. Packet Filter logging used by tcpdump or trafshowpfsync0 - like above part of the internal packet filtering logging.enc0 -- encrypted traffic, not used

For more detailed info on your network device instead of using -a flag (for all) specify your device.

In this example I issued the command ifconfig de0 and the details were returned.

You can see the difference in output and many important missing pieces of info that weren't availablein the ifconfig -a option. Here we can see the MAC address, the media type, and more importantly anyalias IP assigned to this device. In this case de0 has been assigned the primary IP of 192.168.10.9and a secondary alias of 207.216.230.180. This server will respond to either IP. Please note that all207.216.230 addresses will be routed locally but all external IP will be routed through the primary IP'sgateway. See Routing for more details on how to arrange this.

Networking 92


Other uses of ifconfig:

ifconfig de0 down -- will take network device de0 down. Doing a ifconfig de0 after issuing thiscommand will show the flag UP not being present.ifconfig de0 up -- brings the network device back online.ifconfig de0 inet 192.168.1.6 -- this will change the primary IP of de0 to 192.168.1.6 ifconfig de0 inet alias 192.168.2.6 -- assigns an alias IP to the device de0ifconfig de0 inet 192.168.1.22 netmask 255.255.255.248 - assigns IP to de0 and sets the subnet to255.255.255.248ifconfig de0 inet delete 192.168.1.6 -- will remove the assigned IP 192.168.1.6 from the NIC

NOTE: all of these ifconfig changes will only be active until the system is reset. At that time thechanges will be lost. To make them permanent you must edit the proper files, wwnet.conf or thehostname.xxx.

3.2.5 route

In order to see what your gateway is or your route for any assigned network device the command touse is route "man route".

route show:

In this picture we see the returned route table (in fact there is a lot more but only the top half is ofinterest, did a route show | less). The gateway address is listed on the first line directly under the word"Gateway". All other connections to the system are also listed and either show the MAC address iflocal or which link it's going through if not local.

Normal operations would call for a single gateway address to be assigned to the network device in usethrough the file /etc/mygate. If a secondary gateway was required or if you needed to modify thegateway on the fly you could do the following.

route add 192.168.3.4 192.168.3.3 ---- I added the IP 192.168.3.4 (see ifconfig) and then told the



system to route out to 192.168.3.3 for this address

route add 192.168.3 192.168.3.3 --- all 192.168.3.x addresses should use 192.168.3.3 as a gateway.

Another use of route is to find out specifically which address is the gateway for any of your assignedIP's.

route get address, ie route get 192.168.3.4 will return below indicating the mask used and the interfaceused to route out.

3.3 Secure Telnet / Putty

Unlike the older QNX4 system OpenBSD has a focus on security and has included many alternativesto the familiar telnet. Telnet in itself is unsecure as all communications are out in the open in plain textand can be read by anyone sniffing the line, and this includes reading the password. As an alternativeOpenBSD uses ssh for it's telnet like access. TELNET though is available for accessing the OpenBSDsystems but it is still recommended to get into the habit of using ssh.

Windows machines by default do not have ssh capable programs such as it does with TELNET. As aresult we have to install a third-party program to handle ssh connections. The program that is used byDATALOG is PuTTY. This program is freely available from:

http://www.chiark.greenend.org.uk/~sgtatham/putty/

What you need to install is the PuTTY.exe program. Once installed you can create a shortcut to theprogram on your desktop or taskbar and launch from there.

Usage

Networking 94


When you first fire up PuTTY you get a screen like below. On a fresh install you will not see any savedsessions other than default. To the left is a bunch of options that don't require touching so leave themalone as the defaults are fine. In the Host Name (or IP address) field you can enter the IP of yourserver such as 207.216.230.180. The Port for ssh is 22, unlike 23 for telnet. Once you have enteredin the IP address click on the saved sessions and give it a name to identify the connection either the IPagain or a word to identify and then click on Save. By doing so the next time you fire up PuTTY youcan simply double click on the saved session and it will connect for you without entering in the IP overand over.

Once you double-click your session or click on Open it will connect just like TELNET would andpresent you with the following screen (much smaller than default):

Enter your login name as provided by your Technical Support Team:



Your password will not echo back to you, hit enter when complete. (note you can use backspace)

Terminal Type -- Terminal Type refers to the style of emulation that your session will use. Xterm,vt100, vt220 are all acceptable styles. ANSI can also be used but any attempts to edit any files will fail(so avoid using). If you hit enter at this point you will now be logged in. If you type anything else (suchas a command) it will fail and ask you what type of terminal you want. At this point you can't use thedefault so use VT220 in this case.

You are now logged in.

3.3.1 SSH

If you are going from server to server you can use ssh to securely connect between the two:

ssh xxx.xxx.xxx.xxx ssh [email protected]

The two examples above show the two main methods of using ssh. "ssh xxx.xxx.xxx.xxx" will connectyou to the remote system using the same username that you are currently on the initiating system. Soif you were logged in as root on one system and then did ssh xxx.xxx.xxx.xxx it would connect you asroot to the other system. If you needed to connect as a different user then type "[email protected]" and you will connect as user johndoe on the other system.

3.3.2 .ssh

If you try to make a connection from one server to another and you get a message refusing you due toa conflicting entry in the known_hosts file you can remove the old entry prior to making a connection. This is a security layer that protects the system from connecting to another system that doesn't appear

Networking 96


to be correct. The concern here is that someone is now sitting in the middle and reading your traffic. Ifyou know this isn't the case and you can trust the other system go ahead and remove the offendingentry and it will work after that. You will have this problem if you switch server drives but assign thesame IP.

nano /root/.ssh/known_hosts

Remove the line with the IP you are trying to connect to and save.

3.4 Secure FTP / WinSCP

WinSCP is the program that we use to transfer files between Windows and Servers. FTP is frownedupon as it transfers all data including passwords in plain text available to anyone who wishes to view. WinSCP uses secure ssh connections to encrypt all data making for a far superiour method of filetransfer. It also has the added bonus of using PORT 22 like PuTTY so only one port needs to beopened remotely giving us both ssh and SCP access, unlike port 23 and 21 needed for telnet/ftp.

To get the software:

http://winscp.sourceforge.net/eng/index.php

Download the lastest version available and install.

To run simply click on the WinSCP link created. In the Host Name field enter either the IP of yourserver or the name of the server (most cases wellsite servers only use IP). Port number should be leftas 22. You must enter in the UserName and then at this point you can click on Login. If you wish tosave your session do so now before entering in the Password, do not save the session with thepassword --- this is a security breach. Always uses SFTP (allow SCP fallback) and click on Login. Ifyou have saved the session (without the password) double-click on the session to login.

If this is the first time you have connected to this computer via WinSCP you will be asked if you trustthe host, if you do hit YES if not NO.



You will now be prompted to enter a password for this session, fill it in and hit ok.

Once you connect you are presented with two sides, your local system on the left and the remotesystem on the right. You can drag files back and forth, move from directory to directory just like you would with WindowsExplorer.

Networking 98


3.4.1 SCP

SCP is used to transfer files between two systems much like ssh. This uses port 22 as does ssh.

Assuming you are logged in currently to System A:

To transfer file to System B - "scp file [email protected]:/directory_for_file_to_go_to"

To transfer file from System B - "scp [email protected]:/directory_of_file_to_get/file /destination_directory_on_local/filename" (note you can also use '.' for local directory)

3.4.2 .ssh

If you try to make a connection from one server to another and you get a message refusing you due toa conflicting entry in the known_hosts file you can remove the old entry prior to making a connection. This is a security layer that protects the system from connecting to another system that doesn't appearto be correct. The concern here is that someone is now sitting in the middle and reading your traffic. Ifyou know this isn't the case and you can trust the other system go ahead and remove the offendingentry and it will work after that. You will have this problem if you switch server drives but assign thesame IP.



nano /root/.ssh/known_hosts

Remove the line with the IP you are trying to connect to and save.

3.5 Test Network Connections with Ping

To test network connections, use ping. This will show whether your computer can communicate withthe server or with other clients.

e.g. ping 192.168.10.10 - to see if you have communication with the server.

ping -t query repeatedly until interrupted (instead of just 4 times) -control c to stopping -a resolve addresses to host nameping -w time out interval in millisecondsping –t 192.168.10.10

When preforming ping tests be sure to try to ping other systems as well to help narrow down who maybe having a problem and who isn't.

3.6 Test to Isolate Network

If the network is erratically hanging up or crashing, there may be a bad network card somewhere onthe network.

To test for this, hook all the computers up to the network and monitor the "out of windows" collisionerrors.

ssh 192.168.10.10rootrootnetinfo –1

On the list of recorded parameters, find the "out of windows" collision errors, and make a record of thecurrent number.

Wait for about 30 minutes, then recheck this number…

If the number has increased, then there is a problem with a network card.

If the number increases, you have to find the computer with the faulty network card. This can only bedone by removing one computer from the network and recording the "out of windows" errors, asdescribed above. When this is done, and no errors are recorded, you have found the problemcomputer with the faulty network card.

3.7 No Network Communication

If no network communication can be obtained, do the following checks:

· Integrity of network cables· Recheck the network connectors· Power supply to network hub· Are the hub lights on; are they correct?· A bad computer on the network may be isolated by the hub 99% of the time, but the other 1%,

it might bring the network down.

Networking 100


· Cable testers are not always accurate, so recheck with another method.· Make sure terminators (50ohm) and T's are on the ends of the 10base2 cable.



4 APPENDIX

4.1 Standard Units

4.2 Parameter Definitions

Name DescriptionSet Action

APPENDIX 102


Pit Parameters

Accumulated Actual Fill The sum of all fills since it was reset. This needs to be reset beforetripping. ZeroActive PVT The sum of all pit volume in the active system

Define the pits in the active systemActive PVT G/L The change in PVT since it was zeroed

Zeros the PVT G/LActive PVT G/L Rate The flow rate at which the mud is flowing into the pits or (negative)leaving the pits in the active system. NoneActual Fill The amount of taken from the trip tank

NonePit 0 to 15 Pit levels 0 to 15. The pit number may change to a label to describethe pit. I.e. Settling Tank NonePVT 2, 3 and 4 The WellWizard has 4 independent pit volume totals

Define the pits in each systemActive PVT G/L 2, 3 and 4 The change in PVT since it was zeroed in each system

Zero the PVT G/LActive PVT G/L rate 2,3, and 4 The flow rate at which the mud is flowing into the pits or (negative)leaving the pits in each system. NoneTrip Tank

None

Drilling ParametersBit Drilled Time The number of hours the bit has spent on bottom

NoneBit Reamed Time The number of hours the bit has spent reaming

NoneBit Total Time The number of hours the bit has spent in the hole Zero andenter the number of hoursCasing Pressure The measured pressure on the casing manifold.Hookload The measured force on the drilling line.Lag Time The amount of time from the bit to surface.Line Wear The amount of work undergone by the drilling line since last reset.

Rig Status The calculated status of the bit. If the bit depth equals the hole depththen status equals on bottom.RPM The measured speed of the rotary table.Slip Status The current slip status. The slip status is used to determine if the bitis moving when the blocks are moving so it is paramount that the slip status is correct, otherwise thedepth will not operate correctly.Standpipe Pressure The pressure measured by the sensor on the standpipe.Torque Torque as measured directly from a hydraulic sender unit or ascalculated from the current drawn.Torque Electric The torque measured by the amount of current drawn by the mainrotary drive electric motor. Reported in amps.WOB The weight on bit

MiscellaneousDay Number The number of days elapsed since spudFuel Flow The total fuel flow from the fuel tanksTime The current time of the serverTime Zone The time zone of the server

Depth ParametersBit Depth The current depth of the end of the drill pipe.Hole Depth The measured depth of the well-bore



Hook Position The position of the hook from the drill floor to the bottom of the hook

Lag Depth The lag depth currently at surface.ROP The instantaneous rate of penetrationROP average The rate of penetration over the last metreUser ROP The rate of penetration per user defined interval

Pump ParameterFlow G/L The change in flow rate since last resetFlow In The calculated flow rate entering the wellFlow Out The measured flow rate out of the wellFlow Out Percent The measured flow rate expressed as a percentage of fullness of theflow line.Pump Output 1,2,3 The WellWizard can monitor 3 pumps (1,2, and 3). The Pump Outputis the flow rate from each pumpSPM 1,2,3 The rate at which each pump is strokingStrokes 1,2,3 The number of strokes for each pump since resetTotal Strokes The total number of strokes from all pumps since last reset

Debug Parameters Used for testing purposes

4.3 nano

Introduction************

GNU `nano' is a small and friendly text editor. Besides basic textediting, `nano' offers many extra features like an interactive searchand replace, goto line number, auto-indentation, feature toggles,internationalization support, and filename tab completion.

Overview========

`nano' [GNU long option] [option] +LINE [ FILE ... ]

The original goal for `nano' was a complete bug-for-bug compatibleemulation of Pico, but consistency is now a slightly higher priority.There is a flag to implement (nearly) complete Pico emulation, (option-p or GNU long option -pico). This can also be toggled from within`nano' by typing Meta-P. *Note Pico Compatibility::, for more info.

Email bug reports to <[email protected]>.

Command Line Options====================

`nano' takes the following options from the command line:`-T [num, --tabsize=[num]' Set the displayed tab length to [num] columns.

`-R, --regexp' Turns on regular expression search and search/replace.

`-V, --version'

APPENDIX 104


Print the version number and copyright and quit.

`-c, --const' Constantly display the cursor posititon and line number on the statusbar.

`-h, --help' Print the usage and exit.

`-i, --autoindent' Automatically indent new lines to the same number of spaces and tabs as the previous line.

`-k, --cut' Makes ^K cut from the current cursor position to the end of the current line.

`-l, --nofollow' When writing files, if the given file is a symbolic link it is removed and a new file is created.

`-m, --mouse' Enables the use of the mouse to select text (currently only useful for running under the X window system).

`-p, --pico' Emulate Pico as closely as possible, sacrificing consistency for correct emulation. *Note Pico Compatibility::, for more info.

`-r [#cols], --fill=[#cols].' Wrap lines at column #cols. By default this is the width of the screen, less eight.

`-s [prog], --speller=[prog]' Invoke [prog] as the spell checker. By default, `nano' uses its own interactive spell checker that requires the `spell' program be installed on your system.

`-t, --tempfile' Do not ask whether or not to save the current contents of the file when exiting, assume yes. This is most useful when using `nano' as the composer of a mailer program.

`-x, --nohelp' In Expert Mode, the Shortcut Lists will not appear at the bottom of the screen. This affects the location of the statusbar as well, as in Expert Mode it is located at the very bottom of the editor.

Note: When accesing the help system, Expert Mode is temporarily disabled to display the help system navigation keys.

`-v, --view' Do not allow the contents of the file to be altered. Note that this flag should NOT be used in place of correct file permissions to implement a read-only file.

`-w, --nowrap' Do not wrap long lines at any length. This option overrides any value for -r.



`-z, --suspend' Enable suspend ability of `nano' using the system's suspend keystroke (usually ^Z).

`+LINE' Start at line number LINE instead of the default of line 1.

Editor Basics*************

Entering Text=============

All key sequences in `nano' are entered using the keyboard. `nano'is a "modeless" editor, all keys with the exception of Control and Metakey sequences will enter text into the file being edited.

Special Functions=================

Special functions use the Control key (displayed in the help andshotcut lists as ^) or the Meta key (displayed as M).

* Control key sequences are entered by holding down the Control key and pressing the desired letter.

* Meta key sequences can be entered in a number of possible ways: Pressing the Escape key, then releasing it and pressing the desired key, or holding down the Alt key while pressing the desired key. This varies from keyboard to keyboard, and certain commercial operating systems "swallow" the Alt key so that it never reaches the application. If your operating system does this, you should use the Escape key to generate Meta key sequences.

The Titlebar============

The titlebar is the line displayed at the top of the editor. Thereare three sections: left, center and right. The section on the leftdisplays the version of `nano' being used. The center section displaysthe current file name, or "New Buffer" if the file has not yet beennamed. The section on the right will display "Modified" if the filehas been modified since it ws last saved or opened.

Special modes: When nano is in "File browser" mode, the centersection will display the current directory instead of the filename.*Note The File Browser::.

The Statusbar=============

The statusbar is located three lines from the bottom of the screen(or the bottom line in Expert Mode. *Note Expert Mode::, for more info.

The Statusbar shows important and informational messages. Any errormessages that occur from using the editor will appear on the statusbar.Any questions that are asked of the user will be asked on the statusbar,and any user input (serch strings, file names, etc) will be input on thestatusbar.

APPENDIX 106


Shortcut Lists==============

The Shorcut Lists are the two lines at the bottom of the screenwhich show some of the more commonly used functions in the editor. Theexact functions which are displayed depend on whether PicoCompatibility Mode mode is enabled. *Note Pico Compatibility::, formore info.

Online Help***********

The online help system in `nano' is available by pressing ^G. It isfairly self explanatory, documenting the various parts of the editorand available keystrokes. Navigation is via the ^Y (Page Up) and ^V(Page Down) keys. ^X exits the help system.

Feature Toggles***************

Toggles allow you to change certain aspects of the editor that wouldnormally be done via command line flags. They are invoked via certainMeta key sequenced. *Note Special Functions::, for more info. Thefollowing toggles are available:

`Constant Update Toggle (Meta-C)' toggles the -c (-const) command line flag.

`Regular Expressions Toggle (Meta-E)' toggles the -R (-regexp) command line flag.

ÀutoIndent Toggle (Meta-I)' toggles the -i (-autoindent) command line flag.

`Cut To End Toggle (Meta-K)' toggles the -k (-cut) command line flag.

`Cut To End Toggle (Meta-M)' toggles the -m (-mouse) command line flag.

`Pico Mode Toggle (Meta-P)' toggles the -p (-pico) command line flag. *Note Pico Compatibility::, for more info.

ÀutoWrap Toggle (Meta-W)' toggles the -w (-nowrap) command line flag.

Èxpert/Nohelp Toggle (Meta-X)' toggles the -x (-nohelp) command line flag.

`Suspend Toggle (Meta-Z)' toggles the -z (-suspend) command line flag.

The File Browser****************

When reading or writilg files, pressing ^T will invoke the filebrowser. Here, one can navigate directories in a graphical manner inorder to find the desired file.



Basic movement in the file browser is accomplished with he arrow keysand page up/down. The behavior of the enter (or 's') key varies by whatis currently selected. If the currently selected object is a directory,the file browser will enter and display the contects of the directory.If the object is a file, this filename and path are copied to thestatusbar and the file browser is exited.

Pico Compatibility******************

Nano does not completely emulate Pico by default. The followingdifferences apply to the default mode and Pico Compatibility mode:

`Displayed Shortcuts' By default, the following shortcuts are displayed in the Shortcut Lists:

^G Ô ^\ ^Y ^K ^C ^X ^R ^W ^V Û ^T

Related functions are listed above or below each other by default. The Justify function is not listed, instead the "Replace" function is displayed. Also, he "Read File" and "WriteOut" functions are aligned for consistency.

In Pico Compatibility mode, the default Pico shortcuts are displayed:

^G Ô ^R ^Y ^K ^C ^X ^J ^W ^V Û ^T

`Previous String Text' By default, previously entered string for a function (search string, file name) will be placed on the statusbar, and is editable. This is done so there is consistency across all functions. For example: even if there is a previous replace string, it can always be deleted if one wishes to perform an empty string replace.

In Pico Compatibility Mode, the previously entered text in a search or replace will appear in brackets, and is not editable. It is not a simple matter to do an empty string replace when a previous replace string exists, for example. When writing a file, the previous filename will be displayed in the editable text portion of the editor.

Ìnteractive Replace and Spell Checker' It is worth noting that the `nano' replace function is interactive, i.e. it does not stop after one search string is found and automatically replace it. The `nano' implementation will stop at each search string found and query whether to replace this instance or not. The internal spell checker operates similarly. Note that these is no way to force these functions to behave in the Pico fashion.

APPENDIX 108


4.4 Wits records

For more information on the fields inside the records refer to the website http://home.sprynet.com/~carob/.

anax500core manual

Documents