Você está na página 1de 27

WITS HELP Notes The following documents outline setting up WITS correctly and also outline some of the

common problems which can occur and the workarounds which are recommended. Much of this information has been summarised from discussions on the KEEP and thanks are given to the authors of the documents themselves. I would recommend utilising the KEEP and searching for the original discussions if more information on situations where fixes are required is needed. Most of the problems seen are due to the fact that WITS is a standard, but no-one appears to stick to that standard. Therefore, data is specified, in the standard, to be sent or received in specific units and our WITS program is set up to send or receive only those units. The program is (rightly) non-user-configurable since, if everyone stuck to the standard, flexibility would not be an issue. However, knowing this is of no use to you when under pressure on a job to get things working. So, to help, there are a couple of workarounds in the following documentation. Some of these workarounds involve editing text files which are used to define units. It is therefore highly recommended that a backup of the files are made before you start. WITS Help - Initial Setup - PowerPoint A PowerPoint presentation which guides you through how to set up WITS. WITS Help - Initial Setup - Notes The notes pages which go with the above PowerPoint presentation explaining things in more detail. Receiving WITS data in INSITE A step by step method of starting an INSITE machine Receiving Mixed Units Fix This document will show you a method for editing the text file which controls what INSITE WITS is expecting to see. It allows you to change the units for those frequent occasions when other service companies diverge from the standard. Changing units in the sending map file This document will give a method for changing what is being sent. For the same reasons as outlined above when having difficulty receiving. Wits DDU This document shows how to set up a DDU via WITS, should you need to. (can be useful in RTO centres, etc).

WITS Operational Overview


Overview

Wellsite
Information Transfer Specification

Serial Communications Set-up Network Communications Set-up Configuration Mapping Viewing Trouble-shooting Additional Information

The WELLSITE INFORMATION TRANSFER SPECIFICATION (WITS) is an industry standard communications format that can be used for the transfer of wellsite data from one computer system to another. Typically, with INSITE it is used for communications to and from different vendors data acquisition systems; such as a surface data logging system to an MWD system or vice versa. WITS can also be used for communications between different versions of INSITE that might be required to run new tools. This prevents a clash of versions and on-going system trouble.

Overview
Discrete Data Records relate to Rig Activities 25 Pre-defined Standard Records Allows User-defined Custom Records

A WITS data stream consists of discrete data records that generally relate to specific rig activities or vendor services. The rig activity usually determines which records are applicable at any given time such that only appropriate data is transmitted. As WITS has been implemented in INSITE, some records will not transmit unless the WITS activity matches the activity required by that particular record. This is usually automatic, but might sometimes require that the WITS activity be manually overridden before a record type will transmit. As well as specifying a format for data transmission, WITS also defines a basic set of 25 pre-defined Standard records to which user-defined Custom record types may be added.

Channel Setting

Configure Channel Settings. INSITE WITS supports up to four channels. Each channel can be Sending or Receiving.

To set up a Sending or Receiving Channel, select one of the channels from the main WITS interface and then go to File>Channel Setting on the menu bar to configure the channel. INSITE WITS can currently support up to four channels and each channel can be either Sending or Receiving.

Serial Communications Set-up


Baud Rate and Flow Control selections must be identical on Sender and Receiver Null Modem Adapter or crossed cable might be needed for direct serial cable connections Current Loop Adapter or Short-Range Modem can be used for cable distances that are too long for direct serial cable connections

Select the communications medium, in this case Serial, the Serial port ID, the Baud Rate and the Flow Control. The baud rate and flow control settings must be identical on the sender and receiver systems. Make sure that you are selecting the correct com (serial) port on the PC. This should be the port to which the serial cable is physically attached. The interface should only show com ports that are currently not in use by other applications. WITS serial transfer uses the RS232 transmission protocol. In this protocol cable connector pins 2 and 3 are used for data transfer. It is sometimes necessary to use a device such as a Null Modem Adapter to switch pins two and three in order for the two systems to communicate. For distances greater that 15 feet, a Short-Range Modem is recommended. A ShortRange Modem allows the data to be sent over any standard, rig approved, 4conductor cable over distances of several hundred feet. You will need a device at each end of the 4-conductor cable.

Network Communications Set-up


Port Number must be identical on Sender and Receiver

For TCP/IP network transfer of WITS, select File>Channel Settings from the menu bar on the main WITS window, then select the Network radio button. If you are sending, select the Server radio button and enter a TCP Port Number. The Target Host field is grayed-out. If you are receiving, select the Client radio button, enter the IP address of the machine that is sending, and enter the Port Number. The Port Number setting must match on the Sender and the Receiver machines. There have been reports that INSITE was unable to Send via the network to a nonINSITE system, and that an INSITE Windows 2000 system was unable to Send to an INSITE NT4 system. INSITE has successfully Received via the network on several occasions.

Edit Configuration

In the lower part of the Channel Settings interface make sure that the correct channel number is selected and click the Edit button in the Configuration area.

Edit Configuration
Each configuration can be named Select WITS Level Select Direction Select Units

By default all records are enabled. Delete or Disable all records that will not be used.

The WITS configuration determines which WITS records will be sent or received on a given channel. This interface shows the WITS records that are available in this configuration, whether they are enabled, on what basis they are transmitted (the Triggers) if sending, and how often they are transmitted if a time or depth trigger is set. Store, Real Time Distribution, Pass Through, and Block are not required for a Sending configuration. Store and Real Time Distribution are required for a receiving configuration. If Store is not enabled, INSITE will not store the received data in the INSITE database. If Real Time Distribution is not enabled the received data will not be broadcast for display by the various INSITE Real-Time applications. This particular configuration contains the Standard WITS Records 1 through 25 plus Custom Records 50 through 56. Note: WITS records are NOT the same as INSITE Records. By default, all records are enabled. However, it is recommended to delete or disable all records that are not needed. The next few slides describe how to delete or disable the Records that are not required.

Edit Configuration
To remove a Custom Record, select the record and then click Delete.

Custom Records may be deleted from the configuration. Select the record and click Delete. Click Yes. Repeat for each Custom Record that you wish to delete from this configuration. It is important to remember that the configuration file and the mapping file must contain the same records regardless of whether the records are actually used. If a record is removed from the configuration, it must also be removed from the mapping.

Edit Configuration
Standard 25 records cannot be deleted, but can be disabled. Double-click on the record line. Un-check Enable Click OK

The Standard 25 records cannot be deleted from the configuration, but can be disabled. To disable a record, double click on the record to open the Edit Record Attribute GUI. Un-check Enable and click on OK. Repeat for each WITS record that you want to disable. When you are through deleting and disabling records, click on Save to save this configuration. You also have the option of saving the configuration file to a different name.

Edit Map
Each mapping file may be named Select Units Edit mapping for each WITS record Time and Date may be un-mapped to allow INSITE timetagging of received data

The mapping file determines which INSITE variables are mapped to which WITS variables whether sending or receiving. When sending WITS, only one INSITE variable may be mapped to each WITS variable. When receiving WITS from another system, a single WITS variable may be mapped to multiple INSITE variables. This allows the same WITS variable to be stored in more than one INSITE record. In this example WITS record 1 variable 8, Depth Bit, is mapped to four different INSITE Record/Variable pairs. Custom records may be deleted from the mapping file. Click on the drop down arrow near the top of the Edit Map user interface to see the list of WITS records in the mapping file. Select the Custom Record to be deleted and click on the Delete button. Repeat for each custom record that you want to delete. The 25 Predefined Standard records may not be deleted. Remember that for a given channel, the Mapping file and the Configuration file must contain the same WITS records. When receiving WITS, it is recommended to un-map WITS variables Date and Time from any INSITE records. This will allow INSITE to time-tag the received data with the INSITE system Date and Time and avoid any problems arising from the sending and receiving systems having different system times. This is particularly useful when INSITE is acquiring data itself in addition to the WITS data. For example, if INSITE is acquiring PWD pressure data or DDS vibration data as a part of the LWD service and is receiving surface data such as Weight-on-Bit, RPM, and Torque from a third party vendor via WITS, it is essential that the WITS data and the LWD INSITE data correlate at the correct time for proper interpretation of rig events.

10

Edit Map
To un-map Select WITS Variable> Select UnMap To map Select un-mapped WITS Variable> Select Database Record> Select Database Variable> Select Map

Mapping within INSITE WITS is simply the correlation of a WITS variable to an INSITE database variable. In the case of Sending WITS, the map tells INSITE which database variable to send to represent the WITS variable. Only one database variable may be selected to represent the WITS variable. In the case of Receiving WITS, the map tells INSITE where in the database to store the incoming WITS variable. The same WITS variable may be stored in multiple INSITE records. WITS records and INSITE records are very similar in the way that they have been defined. For instance, the Time SDL Fast, Time SDL Slow, and Time SDL Stats records in INSITE are Time-Based records designed for Surface Data Logging information. This type of data corresponds to the type of data in WITS Record 1, General Time Based. Similarly, WITS Record 2 is much of the same data as WITS Record 1, but it is sent on a depth basis and this corresponds to the INSITE Logging Record. A basic understanding of the INSITE database records is essential to effectively modify the WITS mapping files.

11

View WITS Data

Transmission History

Last Record

Transmission Summary

Once the Configuration and Mapping are set up for a channel and the channel is started, the WITS data may be viewed through the provided viewing screens. The viewing screen may be accessed by three different methods depending on what type of information is desired. The viewing screen may be set to update or refresh in realtime.

12

Trouble-shooting with HyperTerminal

Launch HyperTerminal from Start>Programs Name connection Select connection medium (Com Port) Configure port settings to match the settings of the sender Sender should be sending with WITS Level 0 Try different Baud Rates and Flow Control settings if unsure of senders configuration. Try with or without Null Modem adapter

HyperTerminal can be a useful tool for troubleshooting WITS communications and set-up problems. It operates completely outside of the WITS application by reading the input on the selected Com port. Often third-party WITS providers are unsure of how to set up their WITS to properly send the correct data. HyperTerminal may be used to view the data that is being sent, or sometimes not sent by them, to see if it complies with the format that INSITE requires. If the sender has WITS level selections, Level 0 should be selected. If the sender does not have the option to select the level, the level is probably Level 0 by default as this represents the most basic form of WITS transfer. HyperTerminal provides a quick and easy way to test various Com port, baud rate, and flow control settings and to test with and without a Null Modem Adapter until data can be properly displayed. Once the data is properly displayed in HyperTerminal, the same Com port settings and cable configuration may be used for WITS, and the data should transfer correctly. If it does not, investigate the WITS configuration set-up. Also, once everything is working correctly at Level 0, the configuration may be changed to Level 2B if desired. Level selection must be the same on both the Sender and the Receiver systems.

13

Trouble-shooting with HyperTerminal


HyperTerminal will show the stream of WITS data being received at the com port if all settings and cabling are correct.

HyperTerminal will show the stream of WITS data being received at the com port once all settings and cabling are correct.

14

HyperTerminal Capture Text

To capture the input to a text file, choose Transfer>Capture Text from the HyperTerminal menu bar. The default file location is shown above right.

To capture the input to a text file, choose Transfer>Capture Text from the HyperTerminal menu bar. Choose the path to where you want the file to be saved. The default file location is shown.

15

View Captured Text


The captured file can be viewed with Notepad. The view at left shows the end of a record 73 transmission followed by a record 7 and another record 73. Note that && denotes the beginning of a new record and !! denotes the end of a record. The structure is that the first two numbers on a line are the record number, the second two numbers are the item number within the record, and the remaining numbers are the data value for the item.

The captured file can be viewed with Notepad. This example shows the end of a record 73 transmission followed by a record 7 and another record 73. Note that && denotes the beginning of a new record and !! denotes the end of a record. The structure is that the first two numbers on a line are the record number, the second two numbers are the item number within the record, and the remaining numbers are the data value for the item. Notice that the WITS variable name is not displayed. The naming of the WITS variable is not related to the transmission of data. It is up to the Sender to properly map the correct variables so that the correct data values are assigned to the WITS variables for sending. Likewise, it is up to the Receiver to properly map the WITS variables to the correct database variables. Another point to note is that the units of measurement are not transmitted by the WITS transfer. The sender and the receiver must be in agreement as to the proper units of measurement for each variable.

16

WITS Documentation
WITS Wellsite Information Transfer Specification http://home.sprynet.com/~carob/ INSITE Help Sperry KEEP
Ask a Question, Get an Answer

Some good sources of additional information are listed here. The first link is to a website that contains a thorough description of the WITS specification. It includes definitions of the WITS transfer Levels, Predefined Records, and Variables. INSITE Help can answer many general questions regarding set-up and defines most of the terms used. The Knowledge Base has questions and answers for several specific WITS issues.

17

Receiving WITS data in INSITE

1. Create new map file


Goto WITS/edit/map The Select Map dialog box opens, displaying a list of stored map files available for editing . To create a new map for receiving, click receive. The Edit Map dialog box opens, displaying WITS variables on the left side of the list box and INSITE (ADI) records and variables on the right side of the list box. Default mappings are automatically included Type a Map File Name in the text box. WITS is received as a package at a certain time interval. In most cases the general time based WITS record will hold the variables required. The variables are linked to channels, the number of which is standard in the particular WITS record. The time intervall is determined by the sending party. In the large list box, click to select the INSITE (ADI) variable you want to unmap i.e. the variable you dont want to receive. Click unmap. The INSITE (ADI) variable is unmapped from the WITS variable. Do this for all the variables you dont want. You are left with a set of variables you do want to receive. Highlight a variable and select the INSITE database Record and variable. This will decide where the data will be stored in the database. Click map to confirm. (A message will appear that variable has already been mapped.) Do this for all variables to be received. Click save to save the current mappings.

2 Create a new configuration file


Goto WITS/edit/configuration. The Select Configuration dialog box opens, displaying a list of stored configuration files available for editing. Click new. The Edit WITS Configuration dialog box opens, displaying a list of the available WITS records along with the transmission attributes associated with each record. Type the unique four-digit address identifying the remote computer. (If you are receiving, type the ID for the sending computer. If you are sending, type the ID for the receiving computer. If you dont know type 9999)

Select the WITS level you want to associate with the active configuration (level 0 is recommended as it is the simplest and most other parties will use this also use the other levels if required). WITS level 0 allows one-way transmission of data in ASCII format. WITS level 1 allows one-way transmission of data in binary format. WITS level 2 allows one-way transmission of data in binary format (from the sender), while also allowing controls to be sent in the opposite direction (from the receiver). WITS level 2B includes all the features of level 2, with the addition of 24 hours (or 30 MB) worth of data buffering in case of communication line loss. Select the WITS transmission direction. If receiving data from another computer, select Receive. Select the units to be sent or received with the WITS data. FPS (Feet, Pounds, Seconds) = English Metric

3 Attach a channel name to a WITS channel


Goto WITS/file/channel setting The channel settings dialog box opens Type your own channel name into the text box next to the channel you want to use. In the Configuration control, verify that the configuration file associated with the channel name is the one you want to use i.e. the one you created under 2. In the Map control, verify that the map file associated with the channel name is the one you want to use i.e. the one created under 1. Verify the communications settings Click the Communication tab. Verify that the correct medium (WITS output device) is selected. Serial Port is the default. If using a serial port as your communication medium, click Serial Port. Select an available port from the drop-down list. Verify that the correct Baud Rate is selected. The baud rates for the receiving machine and the sending machine must be identical. Verify that None is selected for Flow Control.

The Flow Control for the receiving machine and the sending machine must be identical. WITS is defaulted to receive data at GMT time. In most cases youll want to store the variables in the database at local time. Therefore goto WITS/file/channel settings and click the preference tab. Check Use Local Time box. This will store the data using the senders time without UCT conversion. Make sure time on your computer matches the senders time.

4 Load a channel
To load a channel means to make it available for transmission. On the WITS main window, click one of the small circles to select the channel you want to load (channels are arranged 1-4 from top to bottom). The associated channel name is displayed with that channel. Click to load more channels if sending/receiving WITS from multiple computers.

5 Start a channel
Click the small circle to the left of the channel you want to start. Goto WITS/Control/Start Channel. A green or red dot displays next to the selected channel, indicating that communication has been started on that channel. Double-click the dot to view an event log displaying any errors. Information on the last record sent/received displays to the left of each started channel.

WITS English & Metric Units


The following will fix the problem which might occur when mixed units are being sent to WITS from another service company. Outlined are the fixes for Pump Pressure, Torque and Density. The fix can be applied to any value being sent . 1. Make a backup of the wits folder, just incase. C:\Insite\Data\Wits. 2. Use explorer to open the its folder (C:\Insit\Data\Wits). 3. Once in the wits folder find the appropriate Receive file. If you are running if default it will be called receinig01. If you have made a custom file it will be the name01. Like Receive From Data Log01. This file is the mapping script file. The 01 corresponds to record 1 (Time Record) a 02 will correspond to record 2 (Logging record). 4. Open the file with Word Pad and scroll to the value you want to change. 5. Torque Surface avg is line 0118. What you are going to do is change the metric units to English. This way you can run WITS as Metric but the individual values will be English. 6. Altered line: 7. 0118 RotaryTorque(surf,avg)|TORQA|TQA|FLB|FLB|f-

p|f-p|F|4|74|A|0|Rotary torque
8. Pump Pressure is the same only the units have to be psig not psi as the Insite Units were changed to psig and WITS was not changed. 9. 0121 Standpipe Pressure

avg)|SPPA|SPPA|PSI|PSI|PSIG|psig|F|4|84|A|0|Pump pressure
10. Density In/OUT

0131 Mud Density Out (avg)|MDOA|MDOA|PPG|PPG|PPG|PPG|F|4|116|A|0|Mud density Time SDL Slow|Dens Mud Out Av 0132 Mud Density In (avg)|MDIA|MDIA|PPG|PPG|PPG|PPG|F|4|120|A|0|Mud densityTime SDL Slow|Dens Mud In Avg
11. If there are any other variables to change find the appropriate line and replace the metric appreviation and units with the English values. 12. Save the file 13. If you are bringing in record 2, Logging this will also have to be changed 14. Stop Wits if running and restart. 15. Check the Data Base after a few records to make sure you are receiving the right values. 16. Make a backup of the Wits folder. 17. Wits configure and mapping should be running as metric to facilitate the metric values being brought in.

18. To avoid the Pump Pressure problem if using the spare channels use notepad to open the file Wits to Adi Convert , find the KPA entry and change the kpa to kpag and save.

An Example of the modified file is below:

The following fix came from a job where it was discovered that INSITE was not sending the correct value to the receiver. The procedure below outlines how to change a value in the .map file. This procedure can be used to change any unit types in any maps but should be used with caution. Please also back up / rename the original file to make sure you can revert if you screw up !

EMW FIX The units abbreviation used in the WITS mappings on Insite 5.3.6 bld. 12 do not correspond to the unit set used by Insite. For Density conversion to kg/m3 the abbreviation Insite is looking for is kgm3. On the WITS mapping the abbreviation used is kpm. Since this does not exist in the Insite unitset, it defaults to the base unit (lb/ft3). To fix the problem use Note Pad to change the text kpm to kgm3 in the sending map file. (Remember to also change in any custom records such as PWD, so if you add this at a later date it will have the correct abbreviation). For PWD change the sending.map file (or whatever your map file is called): Original:

5516 PWD Ann ECD (On)|PWDANEON|PEON|PPG|KGM3|ppg|kpm|F|4|64|L|0|Mud density PWD Ann Press|Ann Press EMW

Corrected:

0016 PWD Ann ECD (On)|PWDANEON|PEON|PPG|KGM3|ppg|kgm3|F|4|64|L|0|Mud density PWD Ann Press|Ann Press - EMW

Once you have corrected and saved the map file, you may have to stop the WITS channel and restart to get the change to take effect. (Change all the map files that use the density unit of kg/m3) The abbreviation is wrong in both the sending and receiving maps. So change the appropriate map. Density as G/CC should be correct as it is using g/cc which matches the Insite unit set.

The following is to allow you to send toolface information via WITS INSITE can then display these toolfaces on a DDU screen:
Wits Tool face to Insite DDU Designed to get Insite DDU functional from a Wits input. Can then be used to Data Exchange to a Real-Time Operations Centre and the DDU will be functional. (Exception is that it will not have the TF Seq Number so will not update that on DDU) 1. Insite System Manager, Data Tab, Data Base Admin Icon. 2. Select View & Edit Config, then Record, scroll down to DDU Control record. You will see there are no variables. Double click the record and edit to obtain the GUI below:

3. Highlight the DDU Control record and select Insert Variable 4. Insert Time, Toolface Mag, Tool Face Grav

5. Save Database Changes 6. In the Wits, select the receive map and map the Gravity and magnetic Toolfaces to the DDU Control Record. You will find these Tool Faces in Record 7, variables 16 and 17:

Você também pode gostar