MN Uwmemlog e
MN Uwmemlog e
Document: MN-UWMemlog-E
Ultrawire™ Memlog
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Created August 12, 2010
UWMemlog
Ultrawire™ Memlog Contents
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 Description..............................................................................................................1-1
1.2 System Requirements ............................................................................................1-1
1.3 Supported Hardware & Software ............................................................................1-2
1.3.1 Memory Tools 1-2
1.3.2 Memory Control Units 1-2
1.3.3 Depth Time Recorders 1-2
1.3.4 Warrior Software 1-2
1.3.5 USB Ports 1-3
1.3.6 Serial Ports 1-3
2 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 i
UWMemlog
Ultrawire™ Memlog Contents
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 ii
UWMemlog
Ultrawire™ Memlog Contents
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 iii
UWMemlog
Ultrawire™ Memlog Contents
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 iv
UWMemlog
Ultrawire™ Memlog Chapter 0. About This Manual
Consult the CD Directory for the appropriate Manual Updates to be used with this Manual.
0.4 FEEDBACK
Please help us improve future issues of this manual by adding your comments or corrections to
www.ge-energy.com/oilfield, referencing the document number.
Thank you.
Photographs and sketches are for illustration purposes only. Depending on the tool
model that you have, certain features or dimensions may differ from those shown.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 0-1
UWMemlog
Ultrawire™ Memlog Chapter 1. Introduction
1 INTRODUCTION
1.1 DESCRIPTION
Sondex Ultrawire™ Memlog (UWMemlog) is designed to control all Sondex Ultrawire™ Memory
Tools (UMTs), and to download data from the Depth Time Recorder during slickline logging. It
controls all aspects of the logging operation, from programming the memory tool and downloading
the data, to merging the raw tool and depth data and outputting directly into the Warrior database
format for post processing.
Note: Sondex Ultrawire™ Memlog does not support the previous generation of Sondex memory logging
tools (MPLs), and only displays raw tool data during merge. All tool definitions, service
configuration, calibrations and post processing are controlled by the Warrior Logging System, to
which UWMemlog directly exports the raw memory data.
Ultrawire™ Memlog runs on Windows 2000, Windows XP, Windows Vista* and Windows 7*. Only
32-bit editions can be used, 64-bit editions are not supported. The user must have local
administrator rights.
• Help files use the WinHlp32 system which is not distributed with Windows Vista or
Windows 7. Users must download and install the WinHlp32 package from Microsoft.
• User Account Control (UAC) must be switched to Off (Windows Vista) or Never
Notify (Windows 7).
Operators need to be familiar with Windows® and memory logging. The software has a similar
layout and functionality to all Windows® based programmes.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 1-1
UWMemlog
Ultrawire™ Memlog Chapter 1. Introduction
Sondex Ultrawire™ Memlog (UWMemlog) is designed solely for use with Sondex Ultrawire™
Memory Tools (UMTs) in combination with Ultrawire™ toolstrings.
It does not support the old type of Sondex memory tool (MPL) or non-Ultrawire™ logging tools.
These continue to be supported by the existing Sondex Memlog program.
Type 1 UMTs contain 128MB of logging memory (2 boards, each containing 2 hybrid 32MB
modules, each of which has 16 2MB chips).
Type 2 UMTs contain 1GB of logging memory (2 boards each containing a single 512MB chip).
Each chip is divided into 4096 128kB blocks, and each block contains 64 2kB pages. In addition to
the logging memory, there is extra capacity in each page to store a Cyclic Redundancy Check
(CRC) for each 64 bytes of logged data. The logging memory can be configured from UWMemlog
as a continuous 1GB memory space or as 2 redundant 512MB chips. In redundant mode, data is
written to both chips simultaneously, so if one fails data can be downloaded from the other. It is
expected that most jobs will be run in redundant mode.
Note: Check the Sondex website (www.sondex.com/downloads) or the CD for UMT firmware updates.
New firmware can be uploaded to the tool using UWMemlog.
Only USB MCUs are supported by UWMemlog. The older parallel port MCUs cannot be used.
Note: The UMU is powered from the USB bus and it in turn supplies power to the UMT (Type 2)
electronics. No additional power supply is needed for programming and downloading operations.
However, for monitoring, the Ultrawire™ toolbus also needs power and this is supplied by the 18V
power supply which needs to be connected to the UMU.
Both the DTR004 and DTR005 depth time recorders are supported although other depth time text
files can be imported.
A Warrior V7 installation is required for this program to operate. Certain functions will work with
Warrior in demo mode but creation of a database with the merged output requires a licensed
installation.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 1-2
UWMemlog
Ultrawire™ Memlog Chapter 1. Introduction
The MCU is a USB 1.1 device. It will operate equally well on a USB 1.1 or a USB 2.0 port.
The UMU is a USB 2.0 device. It will operate best on a USB 2.0 port, but will still function on a USB
1.1 port although at a much reduced speed. A USB 2.0 port is strongly recommended.
The DTR004 and DTR005 connect to the PC via a serial port. If a serial port is not available, then a
USB to serial converter must be used.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 1-3
UWMemlog
Ultrawire™ Memlog Chapter 2. Safety
2 SAFETY
Refer to Section 2 of the relevant tool manuals for additional safety before using the tools.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 2-1
UWMemlog
Ultrawire™ Memlog Chapter 3. Getting Started
3 GETTING STARTED
3.1 INSTALLATION
Follow all the on-screen prompts and UWMemlog will install correctly.
Note: Any old version of Ultrawire™ Memlog must be uninstalled before the latest version can be
installed.
Once installed, the operator can start Ultrawire™ Memlog from the Windows Start Menu, or by
using the link found in Sondex Warrior Utilities.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 3-1
UWMemlog
Ultrawire™ Memlog Chapter 3. Getting Started
Note: Each time that Ultrawire™ Memlog is run, it will check the versions of various Warrior files and will
notify the user and update any files that are out of date. No Warrior program should be running
whilst the update takes place.
The MCU or UMU is connected to the PC via USB, and to the UMT via a proprietary cable.
Drivers for the MCU and UMU are provided by Sondex as executable files which pre-install the
drivers in the Windows Driver Store. The MCU driver files are contained in SNDXUSB.EXE and the
UMU ones in SXFTDI.EXE. The executable files should be run before the devices are plugged into
the PC.
The first time the MCU or UMU is plugged into a USB port the operating system will recognise the
new hardware and prompt the user to automatically install the required device drivers from the
Windows Driver Store. The user should follow all on-screen prompts.
Note: Occasionally the USB device drivers are updated. Check on the Sondex website
(www.sondex.com/downloads) for any updates. When a new device driver is installed the device
must be powered down and powered up to ensure the latest device driver is recognised
All the Ultrawire™ memory tools (UMT, MBH, etc.) must be added to the Warrior tools database,
along with the Sondex Memory Services (Sondex Ultrawire™ MIT/MTT, etc.). For information on
importing tools and services, consult MN-WARRIOR.
The current UMT and MBH tool information is distributed with UWMemlog in the Masters directory,
in the file UMT-MBH.wcf. An example service, with just a UMT and an MBH, is also provided, in the
file UMT-MBH.wsv, to show the memory device and sensors.
The memory device must also be added to Warrior. This must be manually added in Warrior.ini
(Configuration file). This file is located in the Warrior Config directory, but can be opened by using
the Sondex Utilities application in the main Warrior Program group.
[Device Alias]
DAMU=BASE
DIU=CYAUX
ULD=USBULD
UWD=UWMEMORY
The Warrior service can then be configured for the exact tool string that is being run in the normal
way.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 3-2
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
4.1 DISPLAY
The window (see Figure 4.1), is the main Ultrawire™ Memlog user interface. From this window it is
possible to access all functions that program and download the toolstring, download the depth data
from the DTR, merge the two sets of data and eventually output merged data to Warrior.
Tool Bar
Main
Menu
Service
Type
Project &
Profile
Selection
UMT Type
Workspace
Status
Bar
Main Menu: The main menu presents the user with a list of options that can be used in Ultrawire™
Memlog. These include options to program and download the tool, and merge the depth & tool data.
Toolbar: The options on the tool bar can also be found within the Main Menu, but the toolbar acts
as a short cut to the most common functions.
Statusbar: This line provides hints and prompts depending on the function the user is currently
using.
Project and Profile Selection: The two drop-down lists allow the user to select the project they
wish to use and the profile to program the tool.
Service Name: This displays the current project's service name as selected in Warrior when the
project files are created.
UMT Type: This displays the type of UMT (1 or 2) that was configured in Warrior when the project
files were created
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-1
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
The profile editor is used to create the set of instructions, used to operate the toolstring while
logging. The user interface contains a toolbar for shortcuts to the most commonly used menu items.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-2
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Merge data allows the user to view the raw tool and depth data. The application has a toolbar to
access all the common functions.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-3
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
The output pass display allows the operator to select the logged passes to output directly into
Warrior.
File
• New Project: Creates a new project and prompts the user to enter a name (Section
5.3).
• Create Project Files: Extracts service and calibration information from Warrior
and adds it to the current project directory (Section 5.4).
• Create Variables Database: Copies the zoned variable information from Warrior
into the current project directory (Section 5.5).
• New Profile: Opens the Profile Editor with a blank, unnamed Profile. See Section 9
Profile Editor.
• Change Projects Directory: Allows the user to pick a new Projects directory
(Section 7.1).
• Exit: Exits Ultrawire™ Memlog.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-4
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Edit
• Profile: Loads the Profile Editor with the current Profile. If no profiles exist, the Pro-
file Editor is opened with a blank profile named after the current project. See Section
9 Profile Editor.
• Memory Configuration: User option to edit the memory tool size and memory
configuration (Section 7.2).
• DPT Settings: Option to set units and filters for depth output (Section 7.3).
View
• Project Directory Files: Shows all the files in the current Project directory
(Section 7.4).
• Set Editor Name: Allows the user to enter the name of the text editor, used to view
the project files (Section 7.5).
Tool
• Program Tool: Programs the tool with the current Profile. (The current Profile is
displayed in the drop-down list on the main window.) See Section 5.8 Memory Tool
Programming.
• Check Erased Memory: Checks that the logging memory has been erased
(Section 7.13).
• Download Tool Data: See options below and Section 6.1 Downloading the Mem-
ory Tool.
- Save Data: This downloads all the data until the tool detects that blank memory
has been reached.
- Save All: Downloads the whole of the configured memory of the tool. This is only
required if something has gone wrong in the tool and the data appears to end early
for some reason.
- Save All Including Bad blocks (UMT2 only): Downloads the whole of the
configured memory of the tool including blocks that have been marked as bad. This
is only required if something has gone terribly wrong in the tool and the memory must
be examined in its entirety. The file will probably not be usable without manual
editing by Sondex.
• Monitor Tool: Entering monitor mode starts the tool running as if a battery were
attached. The tool data is recorded to memory and exported into Warrior simultane-
ously (Section 5.9).
• Get Tool Info: Gets information from the tool, including its memory size (Section
7.6).
• Enter Command Mode: In Command Mode, Ultrawire™ commands and settings
can be sent to the toolstring via the Warrior interface (Section 5.7).
Depth
• Download/ Convert DTR Data: Opens the DTR interface. From this window the
DTR data can be downloaded, the raw data converted to DPT format and the time
can be set on the DTR.
Merge
• Merge Data: Opens the Merge Data window where the DPT and DAT data are
visually displayed, and passes can be selected. See Section 11 Merge Data.
• Output Passes: Opens the Output Passes window, where the Passes selected in
Merge Data are listed. Warrior database files are created from the selected passes.
See Section 12 Output Passes.
• Output Calibrations: The Calibration Pass utility exports downloaded memory
tool data files (dat files) real-time into Warrior (Section 7.7).
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-5
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Utilities
• DAT to text: Converts DAT files into Text files (Section 7.8).
• DPT to text: Converts DPT files into Text files (Section 7.8).
• Text to DPT: Converts correctly formatted Text files into DPT files (Section 7.8).
• Merge DPT Files: Merges multiple DPT files into a single file (Section 7.9).
• Job Sheet: Accesses the Job Sheet utility. (Section 7.10).
Diagnostic
Help
File
• Open Profile: Allows the user to select and load a previously created profile.
• Save Profile: Saves the current profile. If unnamed, the user is prompted to enter a
name.
• Save Profile As: Saves the current profile as a different (user defined) name.
• Exit: Exits profile editor.
Profile
• Insert Below: Inserts a blank profile line below the line in focus.
• Insert Above: Inserts a blank profile line above the line in focus.
• Copy: Inserts an identical line below the line currently in focus.
• Delete: Deletes the line in focus.
• Clear: Clears the profile.
File
• Save Picked Passes to MRG File: Saves the passes, selected in Merge Data, to
a MRG file (i.e. Profilename.mrg). If Merge Data is re-entered using the same DAT
and DPT files, the picked pass and tie-in data saved in the MRG file will be output on
the plot.
• Exit: Exits Merge Data.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-6
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Edit
• Set Tie-Ins: Using a single cursor in each of the depth and tool data plots, the user
selects a common feature that is easily identifiable in both plots. Once the feature is
highlighted with the cursors, the tie-in option should be selected. The 'out of focus'
plot will be aligned to the plot with the focus. These 'tie-in' points are stored and
saved to the MRG file (Section 11.8).
• Align Time Axis: Once both graphs have been tied in, the Align Time Axis option
aligns the 'out of focus' plot with the 'in focus' plot, using the most recent tie-in
(Section 11.9).
• Two Point Merge: Two-Point Merges should only be used once the data has been
tied in. The user should select a pass by placing one cursor at the beginning of the
pass and another at the end of the pass.
Once the Two-Point merge option is selected, the graph, out of focus, will be aligned
to the graph, in focus, and the pass will be highlighted in grey (Section 11.10).
• Three Point Merge: Three point merges can be selected without a tie-in being set.
The user should select a pass by placing a cursor at the beginning of the pass and
another at the end. Once the cursors are positioned, the 3-Point Merge option should
be selected and the user should place a cursor at the beginning of the same pass in
the other plot. Once all three cursors are positioned, the Complete Three Point
Merge option is enabled and the user can complete the pass (Section 11.11).
• Complete Three Point Merge: See Three Point Merge above. This option is only
available once the start and finish points (of a pass) are selected and the Three Point
Merge option is selected. The user should use this option once the 3rd cursor has
been positioned at the other start point (Section 11.11).
• Delete Cursor: Deletes the most recently drawn cursor on the plot in focus
(Section 11.4).
• Delete Pass: Loads a window, listing all the picked passes. Select the pass to
delete and click the OK button (Section 11.12).
• Rename Pass: Loads a window, listing all the picked passes. Select the pass that
needs renaming and enter the new name in the text box provided. Click the OK but-
ton to confirm the name change (Section 11.12).
View
• Zoom In: This function zooms into the centre at 50% of the current view. However if
two cursors are present on the plot (even if one or both are outside of the current
view) the function plots the range between the cursors (Section 11.5).
• Zoom Out: Zooms out from the centre, displaying 50% more than the current view
(25% on each side of the plot). See Section 11.5.
• Previous View: Returns to the previous view.
• Pan Left: Moves the plotted data 50% to the left, keeping the same range (Section
11.5).
• Pan Right: Moves the plotted data 50% to the right, keeping the same range
(Section 11.5).
• Shift Left: Moves the plotted data 25% to the left, keeping the same range (Section
11.5).
• Shift Right: Moves the plotted data 25% to the right, keeping the same range.
• All Data: Shows all available data on the plot in focus (Section 11.6).
• Display Curves Values: Opens a floating window containing all the curves
selected to plot and their values at the current cursor position (Section 11.3).
Select
• Displayed Curves: Allows the user to select the curves to be viewed (Section
11.2).
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-7
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Options
• Edit Start Times: Allows the user to over-ride the log start times, set in the Depth
file and DAT file. The values are stored in the MRG file and used when exporting the
memory data in Output Passes. See Section 12 Output Passes.
• Invert Depth: Inverts the depth curve plot.
• Keep Data Aligned: Should only be selected once a tie-in has been set. This
option locks the range and position of the depth and tool data plots together. If the
graph in focus is shifted, the out of focus graph is immediately aligned (Section 11.9).
Window
Help
Popup Menu: This menu is loaded if the user clicks the right mouse button or places a second
cursor on one of the plots. It is also used during a 3-point merge, when positioning of the final start
point cursor.
Zoom in: This function zooms into the centre 50% of the current view. However, if two cursors are
present on the plot (even if one or both are outside of the current view), the function plots the range
between the cursors (Section 11.5).
Set Tie-ins: Using a single cursor in each of the depth and tool data plots, the user selects a
common feature that is easily identifiable in both plots. Once the feature is highlighted with the cur-
sors, the tie-in option should be selected. The 'out of focus' plot will then be aligned to the plot with
the focus. These 'tie-in' points are stored and saved to the MRG file (Section 11.8).
Align Time Axis: Once both graphs have been tied in, the Align Time Axis option aligns the 'out
of focus' plot with the 'in focus' plot, using the most recent tie-in (Section 11.9).
2 Point Merge: 2 Point Merges should only be used once the data has been tied in. The user
should select a pass by placing one cursor at the beginning of the pass and another at the end of
the pass. Once the 2 Point merge option is selected, the graph out of focus will be aligned to the
graph in focus and the pass will be highlighted in grey (Section 11.10).
3 Point Merge: 3 point merges can be selected without a tie-in being set. The user should select
a pass by placing a cursor at the beginning of the pass and another at the end. Once the cursors
are positioned, the 3 Point Merge option should be selected and the user should place a cursor at
the beginning of the same pass in the other plot. Once all three cursors are positioned, the
Complete 3 Point Merge option is enabled and the user can complete the pass (Section 11.11).
Complete 3 Point Merge: See 3 Point Merge above. This option is only available once the start
and finish points (of a pass) are selected and the 3 Point Merge option is selected. The user should
use this option once the 3rd cursor has been positioned at the other start point (Section 11.11).
Delete Cursor: Deletes the most recently drawn cursor on the plot in focus.
Delete Pass: Loads a window, listing all the picked passes. Select the pass to delete and click the
OK button (Section 11.12).
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-8
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
Rename Pass: Loads a window, listing all the picked passes. Select the pass that needs
renaming and enter the new name in the text box provided. Click the OK button to confirm the name
change (Section 11.12).
File
• Send Calibration Data to Warrior: Sends the data from the picked pass to War-
rior, see Section 7.7.
• Exit: Exits Calibration Pass.
Edit
• Calibration Pass: Once cursors are placed at the start and finish of the section of
data to be sent to Warrior, this option becomes available. It highlights the section in
grey.
• Delete Cursor: Deletes the most recently drawn cursor on the plot in focus.
• Delete Pass: Deletes the calibration pass.
View
• Zoom In: This function zooms into the centre at 50% of the current view. However if
two cursors are present on the plot (even if one or both are outside of the current
view), the function plots the range between the cursors (Section 11.5).
• Zoom Out: Zooms out from the centre, displaying 50% more than the current view
(25% on each side of the plot). See Section 11.5.
• Previous View: Returns to the previous view.
• Pan Left: Moves the plotted data 50% to the left, keeping the same range (Section
11.5).
• Pan Right: Moves the plotted data 50% to the right, keeping the same range
(Section 11.5).
• Shift Left: Moves the plotted data 25% to the left, keeping the same range (Section
11.5).
• Shift Right: Moves the plotted data 25% to the right, keeping the same range.
• All Data: Shows all available data on the plot in focus (Section 11.6).
• Display Curves Values: Opens a floating window, containing all the curves
selected to plot and their values at the current cursor position (Section 11.3).
Select
• Displayed Curves: Allows the user to select the curves to be viewed (Section
11.2).
Help
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-9
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
File
• Output Passes: Outputs the selected passes into the Warrior database format.
See Section 12 Output Passes.
• Exit: Exits Output Passes.
• New Project
• Copy Project Files
• Profile Editor
• Command Mode
• Programme Tool
• Monitor Tool
• Download Tool
• Download/Convert DTR Data
• Calibration Pass
• Merge Data
• Output Passes
• DAT to text
• DPT to text
• Text to DPT
• Help
• Open Profile
• Save Profile
• Insert below
• Insert above
• Copy
• Delete
• Clear
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-10
UWMemlog
Ultrawire™ Memlog Chapter 4. Display, Menus & Toolbars
• Zoom in
• Zoom out
• Previous view
• View all data
• Set Tie-In
• Align axes
• Two Point Merge
• Start three point merge
• Complete three point merger
• Delete Cursor
• Delete Pass
• Rename Pass
• Pan left
• Shift left
• Shift right
• Pan right
• Select Curves to view
• Help
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 4-11
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
5 JOB SETUP
The Warrior Logging System is used to build the toolstring that is going to be used for the job.
Consult the Warrior manual MN-WARRIOR for detailed information. A Sondex Ultrawire™ Memory
service must be selected in Warrior Acquisition.
All the individual tools in the actual toolstring, with the correct serial numbers, must be present to
get the correct sensor calibrations and offsets. Filters should also be configured at this point. Any
other tool or software parameters should also be set here.
The configuration of the UMT being used must also be set in Warrior.
There are two types of UMT, Type 1 uses the MCU for programming and downloading, Type 2 uses
the UMU. The correct tool type must be selected in the Warrior service before the project files are
created in UWMemlog as the program operates in a different way depending on the UMT type.
In addition, the memory size of the UMT and its configuration (Type 2 UMTs only) must be set.
Normally, Type 2 UMTs are set to Redundant mode, where both memory chips record the same
data in case one of them has problems.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-1
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
From the Edit menu, select Edit DPT Settings. In the DPT setup Editor, the user specifies
whether the depth and tension data are output in metric or imperial units. These settings are usually
set up first on a system. It is essential that the options in this window match those on the DTR, oth-
erwise Ultrawire™ Memlog will not output the correct depth.
Note: These settings just tell Ultrawire™ Memlog how the DTR has been configured; to get the correct
depth and data units on the final plots, Warrior must also be configured with the desired unit
system, using Warrior Control Panel.
The Speed settings allow the direction of line speed to be changed, and also allows a filter to be
applied to smooth out speed fluctuations. The filter is a two-stage adaptive time filter. The first stage
has a time constant, which depends on whether the change in speed is small or large. If it is small
then TC1S is the time constant, otherwise TC1L is the time constant. The limit of speed change
where small becomes large is Limit S/L. The second filter stage has a fixed time constant TC2. The
user may have to experiment to obtain the best compromise between a smooth curve and a rea-
sonable response to speed changes.
When editing is finished, the Save as Default button saves the settings globally to UWMemlog
configuration file. Once saved to the UWMemlog configuration file, all new Projects will automati-
cally use the selected settings. The Save to Project button saves the settings to the current
Project and the current global settings are not overwritten.
Note: Users, familiar with the standard Memlog, will notice that the Ultrawire™ Memlog does not contain
an editor for the extra DPT channel settings. These are now defined in Warrior. The Ultrawire™
Device (UWD) allows for 8 DPT channels.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-2
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
The first 4 DPT channels are set to ELTIM (Elapsed Time), ADPTH (Actual Depth), LSPD (Line
speed) and LTEN (Line tension). The other 4 are set to DPT5 to 8 and these channels can be
defined to the user's requirements in Warrior. For example, during post processing DPT5 can be
converted to WPRES (Wellhead pressure) and a calibration can be attached to output a curve.
A project is usually associated with a single run in the well. There will usually be one main tool data
file per project downloaded after the run.
Enter the name of the new project and a new directory is created in the Projects directory, which
becomes the 'current' project. If Warrior Acquisition is running, the user is given the option to create
the project files. Only create these files if the correct memory service with the required toolstring
has been selected in Warrior.
If Warrior Acquisition is not running, start Warrior Acquisition and select the required Memory
Service, i.e. Sondex Ultrawire™ Memory. Once the Service setup is complete, the UWMemlog
project files can be created by selecting Create Project Files… in the File menu.
Note: Sondex recommends that Warrior Acquisition is run in the background while all UWMemlog
configuration functions are performed.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-3
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
Once a new project has been named, the project files must be generated. These files are
saved to the project directory and contain all the service, tool and calibration information for
the project.
Ultrawire™ Memlog gets the information to create the project files from Warrior. Project files can
only be created when Warrior Acquisition is running and an Ultrawire™ memory Service is
selected, e.g. Sondex Ultrawire™ Memory MIT. The Service must match the toolstring that will be
programmed by UWMemlog, including correct serial numbers and tool types, to ensure all calibra-
tion and telemetry information is accurate.
Note: If any of the service, tool or calibration information (including filter definitions) is changed in Warrior,
the project files must be recreated to update UWMemlog.
The zoned variables can be imported from Warrior via the File menu by using Create Variables
Database. By selecting this option, the zoned variable information, currently set up in Warrior
Acquisition, is copied into the current UWMemlog project directory (vars.db). If the zoned variable
information has been copied, all the zoned variable information is automatically embedded into the
Warrior database when passes are output from UWMemlog.
Note: It is possible to change the zoned variable information during post processing should the informa-
tion not be available prior to the memory job, but it has to be done pass by pass.
A profile is a set of instructions that define the sampling periods and rates for each tool in
the toolstring. The memory tool is programmed with the instructions in a single profile file;
subsequent programming operations erase the previous instructions. When the tool is con-
nected to the battery (or the MCU/UMU in monitor mode), the tool's clock starts running and the
samples are recorded in the sequence that has been programmed. There is no way to reset the
sequence other than programming the tool again.
There may be more than one profile file for a project. For instance, if a calibration or test is required
before a job, the user can set up a profile just to record the test and use a separate profile for the
log.
Command Mode allows the user to send Ultrawire™ commands to the toolstring in real-
time via the Warrior interface, without having to program the UMT.
A typical use of Command mode is setting up the MIT configuration. The Compression
mode, Sample type and Sample rate can all be changed in the tool using Warrior. The MIT can also
be commanded to open and close.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-4
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
The currently selected profile will be programmed into the memory tool (UMT) and the
logging memory will be erased. A progress screen displays the current state of the
programming operation.
First of all, the profile is checked for consistency and that the logging memory used by the profile is
less than the memory size of the tool.
Then an operations log file is created (if it already exists, then the old one will be renamed).
Various tests are then performed on the UMT to check that communications have been established
correctly.
Next the profile is converted into a binary file, the Slang (.slg) file, that the tool can read and the file
is uploaded to the UMT.
Then the logging memory is erased, chip by chip, and the progress shown:
When the operation is finished, a dialog appears showing the actual amount of memory erased and
the name of the profile programmed.
An erase check can also be performed at this point if desired. This downloads all the logging
memory without writing a file and checks that each bit has been erased. This should be performed if
time permits.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-5
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
Then an operations log file is created (if it already exists, then the old one will be renamed).
Various tests are then performed on the UMT to check that communications have been established
correctly.
Next the whole of the logging memory is erased in one operation and the progress shown:
Then the erase status of each block of memory is checked. If a block reports it hasn't erased, the
user is given the option of adding the block to the Bad Block Table so that it won't be used for
logging. If the user decides not to mark the block as bad, then programming will be aborted and
must be repeated to see if the block consistently fails.
Next the profile is converted into a binary file, the Slang (.slg) file, that the tool can read and the file
is uploaded to the UMT. At this point a check is made that the logging memory used by the profile is
less than the usable memory in the tool.
Then a dialog appears showing the amount of memory erased, the usable memory in the tool and
the name of the profile programmed.
Note that the option of performing an erase check is not given for a UMT Type 2. It should not
normally be necessary to do an erase check, as the memory chips check themselves during the
erase operation. It also takes a considerable amount of time to perform.
However, the user can do an erase check manually, if desired, from the Tool main menu.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-6
UWMemlog
Ultrawire™ Memlog Chapter 5. Job Setup
Selecting this function starts the tool running as if a battery were attached. The monitor
window displays the tool power, byte count, monitor time, memory time and profile type.
To view the tool values, Warrior Acquisition must be running with the correct memory
service. The user can then select Warrior's sensor and output monitor screens.
To see the memory time and the profile type (and the tool power when using a UMU) in
UWMemlog, Warrior Acquisition must also be running with the correct memory service.
During monitoring, the tool data is simultaneously being recorded to memory and passed to
Warrior. This provides the user with the opportunity to perform tool calibrations using the Warrior
calibration routines.
Note: The monitor time is the time that the tool has been running on this power up whereas the memory
time is decoded from the data stream so includes previous power ups as well.
The 18V power supply must be connected to the UMU when monitoring a UMT Type 2 as the
Ultrawire™ toolbus is powered from this supply.
The tool current as shown on the monitor window is only approximate (generally +/- 20mA) for a
UMU (UMT Type 2) because of tolerances in the ADC used to measure it. If power consumption is
critical then it is recommended that a battery or power supply be used with an ammeter to measure
exact current usage
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 5-7
UWMemlog
Ultrawire™ Memlog Chapter 6. Logging & Downloading Logged Data
Once the memory tool has been programmed with the profile for the logging job, the DTR has been
set up, and all pre-job calibrations completed, the well can be logged. As soon as the batteries are
connected to the top of the toolstring, the internal clock starts and the data is recorded to memory.
Ultrawire™ Memlog downloads the memory tool data to a raw data (*.dat) file. If the current
profile is Test.pfl, the data file will be Test.dat. If the data file already exists on disk, it will be
renamed rather than overwritten.
The data is downloaded from the tool until the program detects that blank memory has been
reached. At the end of the download the user is informed how much of the memory has been saved
UWMemlog then indexes the data and the whole file is then read and checked for data consistency.
Any errors are reported to the user.
Note: The UMT records data in logical blocks (not related to physical blocks of memory). A new block is
started for every profile line and approximately every 32kB if no profile line change has occurred.
Each logical block starts with a Sondex~ marker, on an 8-byte boundary. If block errors are
reported during indexing and checking then the program is referring to these logical blocks, not
physical blocks.
The user can then view the statistics file which shows detailed information about the data logged for
each tool.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 6-1
UWMemlog
Ultrawire™ Memlog Chapter 6. Logging & Downloading Logged Data
For a full diagnostic check the DAT to Text Utility can be used, but this requires in-depth
knowledge of the memory layout and Ultrawire™ data formats.
From the Tool main menu, additional download options are available. These differ between the two
UMT types:
UMT Type 1
Save Data is the one normally used. This downloads all the data until the program detects
that blank memory has been reached.
Save All downloads the whole programmed memory of the tool. This is only required if some
thing has gone wrong in the tool and the data appears to end early for some reason. For
example, it is possible that a block of memory goes bad during a job and the tool thinks this is
the end of the data. Saving all the data can get past this bad block and into good data again.
There will be a gap in the data, but most of the log will be recovered.
As part of both download processes, the Cyclic Redundancy Checks (CRCs) embedded in the data
are checked. If CRC errors are detected, parts of the memory will be downloaded again to see if
this fixes the problem; if it does the bad data is replaced with the good data.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 6-2
UWMemlog
Ultrawire™ Memlog Chapter 6. Logging & Downloading Logged Data
UMT Type 2
Save Data is the one normally used. This downloads all the data until the program detects
that blank memory has been reached. As part of the process, the Cyclic Redundancy Checks
(CRCs) in each page of data are checked. If CRC errors are detected, that page of data will
be downloaded again to see if this fixes the problem; if it does the bad data is replaced with
the good data.If operating in redundant memory mode, the repeat download will be done from
the redundant memory chip, otherwise it will be from the same chip. If the repeat download
fails to fix the problem, then an algorithm is used to see if a single bit error can be repaired
using the CRC values.
Save All downloads the whole usable memory of the tool. This is only required if something
has gone wrong in the tool and the data appears to end early for some reason. For example,
it is possible that a block of memory goes bad during a job and the tool thinks this is the end
of the data. Saving all the data can get past this bad block and into good data again. There
will be a gap in the data, but most of the log will be recovered. If operating in redundant
memory mode, the user must choose which chip to save from, either Chip 1 or Chip 2. CRCs
are checked during the download but no attempt is made fix them, they are just reported to
the user.
Save All Including Bad Blocks downloads the whole memory of the tool, including blocks
that have been marked as bad in the Bad Block Table. This is only required if something has
gone terribly wrong in the tool and the memory must be examined in its entirety. The file will
probably not be usable without manual editing. Again, if operating in redundant memory
mode, the user must choose which chip to Save All from, either Chip 1 or Chip 2, and CRCs
are just checked.
The Depth Time Recorder is downloaded using the depth interface, found in the Depth
menu. The depth interface fully controls all aspects of the depth recorder.
Once the raw depth file has been downloaded, it must be converted to the calibrated depth
file (*.dpt) before it can be viewed in Merge Data.
Open the Merge Data option found in the Merge menu. The depth and raw tool data is
displayed with options available to tie-in the two data sets and pick the logged passes to
export into Warrior. The picked passes are saved to a merge file, which is used by the
Output Passes utility for the final export into Warrior.
See Section 11 Merge Data for a comprehensive explanation of the merging and pass picking
process.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 6-3
UWMemlog
Ultrawire™ Memlog Chapter 6. Logging & Downloading Logged Data
To export the merged data to Warrior, use the Output Passes utility found in the Merge
menu. Output Passes takes the picked pass information from Merge Data and exports the
depth and raw tool data into a Warrior database.
Ultrawire™ Memlog outputs the depth and raw tool data directly into the Warrior database. When
using the Output Passes function the database created by UWMemlog contains a single pass of
raw data for each pass picked in Merge.
To compute the calibrated curves from the raw values the Warrior Recalculation program must be
used. When recalculating the pass, Warrior reads the raw data and applies all the calibrations and
zoned variable information and generates the calibrated tool curves in a new pass.
Once the calibrated curves are produced, post processing of the logged data can begin using
Warrior's suite of applications.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 6-4
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
7 ADDITIONAL FEATURES
Each UWMemlog project stores the Ultrawire™ Memory Tool's configuration. To edit or view the
configuration, select Memory Configuration from the Edit main menu.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-1
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
For a UMT Type 1, the only setting that can be changed is the memory size. Select the size from
the drop down list and click the Save button to update the current project settings.
For a UMT Type 2, the memory size is fixed at 1024MB (1GB), but the configuration can be
switched between Simple (1GB of memory space) and Redundant (512MB of memory space, both
chips containing the same data). Redundant is the recommended choice unless huge amounts of
memory are needed.
Note: The UMT type cannot be changed from UWMemlog. It must be changed in Warrior and then the
project files must be re-copied.
This option in the UWMemlog Edit menu sets the Projects depth settings and is explained in
Section 5.2 DPT Setup.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-2
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
By selecting the View Project Files option in the View menu it is possible to see all the files in
the current project directory.
From the Files in Project window the user can open the files by either double clicking on the
selected file, or highlighting the file and pressing the Carriage Return key. The file will be opened in
which ever Editor the user has chosen. Refer to Section 7.5 Setting the Editor Name.
To enter the name of the text Editor, use Set Editor Name in the View menu. Type the full path of
the Editor or else leave the text box blank, and Ultrawire™ Memlog will default to Notepad.
The editor should be able to open large binary and ASCII files. Sondex recommends UltraEdit
(http://www.ultraedit.com) to open the large DAT and text files produced in Ultrawire™ Memlog.
In the Tool menu, there is an option to Get Tool Info. This function communicates with the UMT
and responds with various information including the memory size, Slang (Sondex logging language)
version and firmware version.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-3
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
The Calibration Pass utility exports downloaded memory tool data files (dat files) real-time
into Warrior. It is designed to allow users to perform Warrior calibrations with pre-recorded
memory data.
Open the Calibration Pass utility by selecting Merge menu and clicking on Output Calibrations.
The window looks very similar to the Merge Data utility and has similar functionality. The user must
select the section of data to send to Warrior by placing cursors at either end of the section. Once
the cursors are positioned, the option to create a Calibration Pass in the Edit menu becomes
available, or the same option can be selected from the popup menu. The selected section will be
highlighted and labelled 'Calibration Pass'. See the figure below.
To send the tool data to Warrior, select the Send Calibration to Warrior option from the File
menu.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-4
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
Note: Warrior Acquisition must be running to send the data, and the correct memory service should be
selected, e.g. Sondex Ultrawire™ Memory MIT.
While data is being sent to Warrior, a cursor steps through the tool data, showing the user the data
being sent at that time. When the cursor reaches the end of the calibration pass, it loops back to the
being of the pass. The tool data is sent in an endless loop, until the user selects the Cancel button
to stop the transmission of data.
While data is being sent to Warrior, it can be viewed in Warrior's sensor and output monitors and all
Warrior calibrations can be performed.
DAT to Text: This produces a text listing of a tool data file. Either a full or a summary listing
can be produced. A summary listing shows all the memory block headers and
trailers plus any errors that have been detected.
Text to DPT: This produces a depth (dpt) file from a text file and can be used to import data
from other types of depth-time recorders.The recalculate speed option allows
the line speed to be recalculated from depth and time for those cases where the
supplied speed is not accurate enough. If no speed is supplied, it will be
calculated automatically.
This option in the Utilities menu is used to join depth (*.dpt) files together.
First select two depth files by using the Select Files button. The start and end times of the two
files are shown on the window.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-5
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
Also displayed is the apparent time gap between the end of the first depth file, and the start of the
second depth file. If this time gap is correct, the user can merge the depth files by selecting the
Merge Files button.
Note: When the two files are merged, the time gap is filled with the final curve values from the first depth
file. Hence, if Line Speed was 5ft/min at the final sample in the first depth file, the Line Speed will
remain at 5ft/min for the time gap. (Time will continue to increment as normal.)
If the displayed time gap between the files is incorrect it is possible to enter an adjusted gap (in sec-
onds). If the gap is manually entered, the time values in the second depth file are adjusted to allow
for this new gap.
Note: If the time gap is positive there will be a gap between the end of the first depth file and the second
depth file where data is duplicated. If, however, the time gap is negative the first depth file will be
truncated, i.e. the last n seconds will be overwritten with data from the second depth file, where n is
the time gap.
The Job Sheet utility takes all the information from the profile file (*.pfl) and allows the user to enter
comments and actions that are appropriate for each line.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-6
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
These comments and the profile information can be saved to a job file (profilename.jbs) that is
copied to the project directory. This text file can be printed, if the user wishes to have a reference at
the wellsite.
The utility has the option to enter the start time for the job; this calculates the 'real' time each profile
will begin. Once the start time has been entered, the job sheet uses its internal clock to highlight the
profile line currently being executed.
In the Diagnostic menu, there is an option to Test MCU Connection or Test UMU
Connection, depending on the UMT type configured in the project.
This function simply tests that Ultrawire™ Memlog can communicate with the MCU or UMU through
the USB port and it displays the installed driver version.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-7
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
The microprocessor firmware in the UMT can be updated using Ultrawire™ Memlog. In addition, for
type 2 UMTs, the CPLDs can also be updated.
Select Diagnostics from the main menu and click on the option to Upload Tool Firmware. Then
select Microprocessor Firmware or CPLD Firmware (UMT Type 2 only).
Navigate to the firmware binary file and click OK; the new firmware will then be uploaded to the
UMT.
For the UMT Type 2, there is a further option, Microprocessor Firmware (Cold Boot).
Uploading firmware to a UMT Type 2 in the normal manner requires that the microprocessor is
running the existing code first. In cases that a previous upload has failed and the microprocessor
isn't running, the cold boot option can be used. After selecting the firmware file, the user is
prompted to disconnect the UMU cable from the UMT (so powering down the UMT) and to
reconnect it again within 30 seconds. On power up, the UMT detects that a cold boot has been
requested and enters a mode where the firmware can be uploaded without the processor running
the existing firmware.
Note: Do not upload UMT Type 1 firmware to a UMT Type 2 or vice versa.
This will download the memory (without writing a file) checking that each location has been fully
erased.
For a UMT Type 1, the user should perform an erase check at the end of each programming
operation if time permits.
For a UMT Type 2, it should not normally be necessary to perform this check every time the tool is
programmed (as the erase status is checked by the memory chip itself), but should be run from time
to time as part of a maintenance schedule or before high-profile jobs. If, during the erase check, a
block of memory is detected as not having been erased properly, the option of adding the block to
the Bad Block Table (see Section 7.15) is given.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-8
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
This utility displays the logged passes selected in the Merge Data utility.
The user can enter comments for each pass and the displayed data can be written to a comma-
separated text file (projectname.pss). This file can be viewed in Microsoft Excel or Notepad.
To enter comments the user must double-click on the comments cell. A flashing cursor indicates
that text can be entered. To save the text to the cell the user must press the carriage return key
before selecting another cell.
Type 2 UMTs contain 1GB of logging memory, on 2 boards each containing a single 512MB chip.
Each chip is divided into 4096 128kB blocks and each block contains 64 2kB pages.
Over the lifetime of a chip, the device may develop blocks that cannot be erased or written to
successfully. This is normal and is not considered to be a failure.
The UMT maintains a list of bad blocks in its Bad Block Table. The table can be viewed by selecting
Bad Block Table from the Diagnostics menu.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-9
UWMemlog
Ultrawire™ Memlog Chapter 7. Additional Features
Blocks that are marked as bad will not be used for logged data, the UMT will skip them
automatically. During a download of the logged data, UWMemlog skips the bad blocks as well.
Blocks can be added to the table automatically during programming of the tool. If the chip detects
that a block cannot be erased properly, UWMemlog reports it to the user and gives the option of
adding it to the table (the user must answer Yes to continue with the programming operation).
The option to add a block is also given on the Bad Block Table screen. This could be used if a block
consistently gives a CRC error on recorded data, but the erase process hasn't detected a failure.
There is also the facility to completely erase the table. This would normally only be used when
replacing a memory board. Make a note of the existing bad blocks entries first so that the entries
can be restored for the board that is not being replaced.
When operating in redundant mode, the same data is written to both chips simultaneously. If a
block is marked as bad in one chip, the UMT will not use the corresponding block in the other chip
either, so data redundancy is preserved.
Bad blocks will reduce the usable memory of the tool slightly (by 128kB for each bad block). During
programming, UWMemlog checks that the profile will fit in the usable memory of the tool and warns
the user if it doesn't.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 7-10
UWMemlog
Ultrawire™ Memlog Chapter 8. Services & Project Information
8.1 OVERVIEW
Ultrawire™ Memlog gets all its service and tool information from Warrior. Hence, it is essential
when creating a new project in UWMemlog that Warrior Acquisition is running with the required
memory service.
Before running Ultrawire™ Memlog for the first time, Warrior must be updated with the new Sondex
Memory Services and memory tools, which are available on the Sondex website or on the CD
provided.
The toolstring and service must be set up in Warrior, this includes all tool calibrations that need to
be performed before the job, and the zoned variables required. Once the Warrior service and
toolstring setup is completed, Ultrawire™ Memlog can be started.
When a new project is created in UWMemlog, the user is prompted to create the project files.
These files are saved to the project directory; they include the service.ini and project.ini, as well as
any Warrior calibration files associated with the specific tools in the toolstring. For example, the MIT
(Multi fingered imaging tool) has 3 Warrior calibration files, the finger calibration, inclinometer cali-
bration and temperature compensation. These are all tool serial number specific and are copied
into the project directory.
Note that when the merged tool and depth data is output into the Warrior database, the tool
calibration files in the UWMemlog project are embedded into the database. This ensures that the
correct calibrations are used during post-processing.
The project files can be updated at anytime, should a calibration be updated, or a tool serial number
changed. By using Create Project Files in the File menu, the current project files are over-
written, and the new calibration files are copied into the directory.
8.2 DEFINITIONS
8.2.1 PROJECTS
A project is usually associated with a single run in the well. There will usually be one main tool data
file per project downloaded after the run.
The default Projects directory is located in the main Ultrawire™ Memlog program directory and
contains all the user created projects (*.prj).
All the raw data, toolstring, service and calibration information from a job is stored in the directory,
allowing the user to recreate the job for post-processing at anytime, as the original calibrations and
tool serial numbers are all saved. This means projects can be archived and the output from an old
job can easily and quickly be recreated.
8.2.2 SERVICES
A service is defined as a set of tool types that are run in the well as one string, e.g. CFB-GR-CCL-
QPS-UMT-MBH. If, on a particular run, the GR is not present, there is no need to define a separate
service for this string, that tool can simply be excluded from the service for this run. Hence the
service is usually defined with the maximum set of tools, which may be run together.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 8-1
UWMemlog
Ultrawire™ Memlog Chapter 8. Services & Project Information
All service editing and defining is performed in Warrior. Ultrawire™ Memlog simply copies across all
the information into the project directory.
8.2.3 PROJECT.INI
The Project.ini file contains all the setup information Ultrawire™ Memlog needs for a project. It
holds general tool and channel information, including tool names and addresses, as well as the
DPT settings.
Note that the UWMemlog Project.ini file differs greatly from the standard UWMemlog equivalent,
and should not be confused as performing the same function. There is no longer a complete
description of the toolstring, incorporating calibrations etc.; this function has been passed to the
Service.ini file.
8.2.4 SERVICE.INI
The Service.ini file contains all the service and tool information extracted from Warrior. It holds the
tool definitions, service, device, filter and calibration information required for building the exported
Warrior database.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 8-2
UWMemlog
Ultrawire™ Memlog Chapter 9. Profile Editor
9 PROFILE EDITOR
9.1 OVERVIEW
The Profile Editor is used to create the Profile file (*.pfl). A profile is the set of instructions
sent to the memory tool, controlling when tools should be logged and the sample rate the
tools should be recording at. Each tool can have its own sample rate, and tools with motor-
ised arms can be opened or closed.
The Ultrawire™ Memlog Profile Editor lists all the tools in the service that contain sensors, together
with their Ultrawire™ address and default sampling rate.
Each profile (programming) line has a start time, length and type. Plus each tool has its own
sampling rate.
The start time is an accumulative time calculated from the length of all the preceding profiles. The
time is expressed as a combination of DD days, HH hours, MM minutes, SS seconds. This is gen-
erated automatically by the software each time a profile length is altered.
Start times are consecutive from when the batteries are connected, hence the start time of succes-
sive profile lines will increase. At each new start time the previous profile will terminate.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 9-1
UWMemlog
Ultrawire™ Memlog Chapter 9. Profile Editor
The profile length is entered by the user and determines the period of time the profile line will be
used.
The profile type defines the tool mode for the particular profile. There are currently five profile types
available: LOG, OPEN, CLOSE, SLEEP and SETUP.
The rate section of the profile line contains a cell for each tool, where the user can select or enter
the sampling rate of the tool or program a tool to open, close or setup.
The memory size displayed is taken from the current Project.ini file setting. It is essential that the
memory used does not exceed the memory size or the whole data set will not fit into the memory
tool.
The amount of memory being used is calculated from the profile lengths, types and sample rates.
The profile length is entered by the user and determines the period of time the profile line will be
used. By default the length should be entered in minutes, with quarter minutes (15 seconds) the
smallest period available. Should the user wish to enter the profile length using hours or days then
UWMemlog can convert entered values that are appended with an "h" or "d".
a.
Converted by UWMemlog.
The profile type defines the tool mode for the particular profile. There are currently five profile types
available: LOG, OPEN, CLOSE, SLEEP and SETUP.
LOG is the default type; this option records all the tools at their selected sample rates. If a tool has
a zero sample rate selected, then it will not be recorded.
The OPEN and CLOSE profile types should only be used when the toolstring includes tools with
motorised sections, for example the Ultrawire™ MIT with its motorised fingers.
Note: Only one tool can be opened or closed in a single profile. The Ultrawire™ memory tool does not
have enough power to open or close more than one tool at a time. While a motorised tool is being
opened or closed no tools are sampled.
Sondex recommends that each OPEN and CLOSE profile is 3 minutes in length to allow the tool to
fully open or close.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 9-2
UWMemlog
Ultrawire™ Memlog Chapter 9. Profile Editor
The SLEEP profile type puts the toolstring in hibernation mode. The toolstring draws minimal
current and sampling of the tools is stopped, hence it is not possible to select a sample rate on a
SLEEP profile.
The SETUP profile type is similar to the OPEN and CLOSE profile types in that only certain tools
have the option available. Tools, such as the MTT and MIT, require 'setting up' prior to logging and
the SETUP profile type allows the user to pick the best set up for the job.
Unlike the OPEN and CLOSE profile types it is possible to set up multiple tools in each SETUP
profile line. Sondex recommends that each SETUP profile is at least 1 minute in length to allow
time for the set up commands to be sent to selected tools.
The MTT is currently unique in the Sondex Ultrawire™ memory tool suite as set up commands
must be sent to the tool prior to logging. It is essential that the transmitter and auto gain are turned
on and the excitation frequency is set to allow the MTT to record thickness correctly.
The MIT set up options, unlike the MTT, are not essential prior to logging. The option available to
MIT users is to select the recorded data compression mode. The compression mode for MITs is
stored in the tool's memory and can alternatively be set in Warrior while UWMemlog is in Command
Mode.
However, by using the SETUP profile type, the user can set the compression mode in the profile.
The upside of this is that when the compression mode is set within the profile, the calculated
memory usage no longer has a Min and Max value. The user can view the precise amount of
memory being used.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 9-3
UWMemlog
Ultrawire™ Memlog Chapter 9. Profile Editor
The rate section of the profile line contains a cell for each tool where the user can select or enter the
sampling rate of the tool, in a LOG profile, or select other actions in other profile types.
When a LOG profile type is selected, clicking on the individual cells produces a drop-down list of
sample rate options. Once a rate is selected, the cell is loaded with the value. The user can also
manually edit the cell using the keyboard.
The sample rates that appear in the drop-down list are taken from UWMemlog.ini and this file can
be edited to suit the user's requirements if necessary.
Each tool can have a different rate that must be divisible by 20ms (0.02s). Each tool has a
maximum sampling rate that cannot be exceeded. Some tools like the MIT can be sampled at
0.02s, but the maximum rate for the UMT and others is 0.1s. It is not possible to save the profile
should any of the maximum sample rates be out of range.
It is important to select a sample rate that is consistent with the desired tool resolution (in samples/
ft) that has been set up in the Warrior service and the desired logging speed. For instance, the
default rate for the MIT is 0.02s (50 samples/s) and Warrior is normally set up to record the MIT at
100 samples/ft so the matching logging speed is 30 ft/min.
When the OPEN or CLOSE profile types are selected, the option to open or close specific tools
becomes available to the user. Only tools with motorised sections will be user selectable, and the
drop-down list in the Rate cell alters to reflect this. The list contains 2 options, one is blank and the
other is either open or close depending on the profile type. The open or close option must be
selected and displayed in the rate cell to command the motorised tool to open or close.
This reports the memory used to complete the profile. If a profile begins to exceed the maximum
memory the user should reduce sample rates to save memory.
This value is updated whenever an alteration occurs within the profile. The memory tool capacity is
defined in the Project INI file and must be set correctly. The tool's physical memory size can be
read directly from the tool by using the Get Tool Info function.
If a tool, which has a variable dataset size (such as an MIT), is included in the project, there will be
two memory usage values, a maximum and a minimum. To get an accurate memory usage value,
click on the Details… button and select the mode that the tool is set to (this does not set the
mode, the user must do this manually).
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 9-4
UWMemlog
Ultrawire™ Memlog Chapter 9. Profile Editor
Alternatively, for the MIT, a SETUP profile can be used to set the MIT dataset size. By selecting the
MIT compression mode at the start of a profile, UWMemlog reports a precise memory usage value.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 9-5
UWMemlog
Ultrawire™ Memlog Chapter 10. Download / Convert DTR Data
Note: Only the DTR004 and DTR005 are supported in Ultrawire™ Memlog.
This function brings up the main DTR004/005 screen, where the serial port and baud rate can
be chosen. The baud rate must match the setting on the DTR.
To download the data, the DTR must be at the top-level menu. By default, if the current project is
Example.prj, the downloaded file will be Example.raw, although the name can be changed.
At the end of the download, the program automatically goes into the conversion to dpt format
screen although re-conversion can take place without downloading again.
The DTR is capable of recording 8 analog channels apart from depth and time. The analog channel
settings are displayed on the screen. However, the dpt format is only capable of supporting 8
channels in total (Depth, Time, Speed, Tension and 4 others) so the user cannot convert all the
available analog channels. The O/P selection boxes define which channels are to be converted.
The Tens selection tells the system which of the channels is the Tension channel.
The Pulses per Revolution and Wheel Circumference settings are used to convert encoder
ticks to actual depth.
The Tool Start Time is the time at which the battery is connected to the tool. It is used to provide
an initial data alignment when visually merging the tool and depth data later on. Any error in this
time can be corrected for later.
The Speed Change Threshold is used to filter out single erroneous depth records in recorded
DTR data. A bad depth record will produce a positive spike in speed followed by a similar negative
spike, or vice versa. If such a pair of spikes is detected, with amplitudes greater than the Speed
Change Threshold, then the depth record will be ignored.
Each time the DTR starts recording, a separate record is created. The user has to select which
record is to be converted to DPT format. If the raw data file is called Example.raw, the DPT file will
be Example.dpt by default, although the name can be changed.
The only way to merge DTR records is to convert each one to a DPT file, and use the Merge DPT
files function.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 10-1
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
11 MERGE DATA
11.1 OVERVIEW
The Merge Data utility allows the user to view the Depth and Tool data files, pick the passes
within the data, and save them to a MRG file for use in Output Passes. Merge Data can be
used to check each tool has logged correctly by viewing its data over the entire log, it is also
possible to zoom in on specific areas for more detailed analysis.
When Merge Data is selected, the user is first prompted for the Depth and Tool channels to view.
By default the first 2 channels selected will appear on the axes. However, an option is available to
pick the axes separately. Once the channels are selected, the main Merge Data window is loaded,
displaying the Depth and Tool data.
• Main Menu: The main menu presents the user with a list of options that can be
used in Merge Data. These include options to display Tool and Depth data sepa-
rately, select different channels to view, and highlight the passes in the data.
• Toolbar: The options on the tool bar can also be found within the Main Menu, but
the Tool bar acts as a shortcut to the most common functions.
• Statusbar: This line provides hints and prompts depending on the function the user
is currently using.
• Active Window indication: This area of the screen informs the user which of the
windows is currently in focus. It also contains the channel values of the current
cursor position, and houses the grid option.
• The remaining window area: Displays scales, and curve titles.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-1
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
The features and functions in Merge Data can all be accessed through the main menu, with the
most common features available in the tool bar. A pop up menu is also accessible via the right
mouse button.
This feature is first encountered when entering Merge Data. The user is prompted to select the
curves that they wish to view. By default the first two curves selected are placed on the axes,
however by checking the axes option the user can select the viewed axes manually. Once inside
the Merge Data window different curves can be selected by using the Select menu option.
In addition, if merging MIT or MTT data, a further option is available. In the Select menu of the
Merge Data window the user can select to view either the average finger value or the average
inclinometer reading for the MIT, or the frequency or real average readings for the MTT. Both these
options help to locate the starting point of a logged pass.
The title bar of the data windows can display up to 2 curve values. The values relate to the current
cursor position.
If more than 2 curves are being viewed, it is possibly to display all the curve values in a separate
window. By selecting the View menu and clicking on Display Curve Values, a window listing all
the curve names and their current values is loaded.
A cursor can be placed on either graph by clicking the mouse inside the graph axes. Once a cursor
has been drawn, it can be moved along the x-axis by using the left and right arrow keys, or by
placing the mouse pointer above the cursor. If the later occurs, the mouse pointer will become an
East-West arrow, and by holding down the left button on the mouse, the cursor can be dragged into
a new position. Whenever a cursor is moved the output coordinates in the graph's header are
updated to give the user accurate data values at the cursor position.
Cursors can be deleted in the main menu by selecting the Edit menu. If two cursors are on the
graph, the most recently drawn cursor will be deleted.
There are multiple functions that allow the user to select the area of data they wish to view. All the
functions are available in the main menu under View. Zoom in zooms into the central at 50% of
the current view, while Zoom out pans out to show double the range of the current view, with the
centre point remaining the same.
If two cursors are placed on the graph and the Zoom In function is selected, Merge Data will
zoom into the area between the cursors, even when one or both of the cursors are not visible in the
current view.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-2
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
It is possible to pan and shift the current view left and right. If the pan option is selected the
current view is moved 50% in the direction selected. When shift is chosen the view is moved 25% in
the direction selected.
This function in the View menu resets the plot to show all tool and depth data.
This function, found in the Options menu, allows the user to over-ride the log start times as con-
tained in the depth (DPT) file and tool data (DAT) file. These values are saved to the MRG file and
used in outputting the merged data in Output Passes.
The user should tie-in the depth and tool data before any passes are picked from the data. The
'tie-in' points are a single point in each graph that correspond to each other, i.e. the start of the first
up pass. The user should select these points by placing a cursor in each window at the same point
in the data. It is important to chose a point that is easily recognisable in both depth and tool data.
Once the tie-in points are selected, the user should click the tie-in option in the Edit menu. The
graphs will automatically align themselves. The last 'tie-in', set by the user, is saved into the MRG
file.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-3
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
Once the Tie-In points are set, it is possible for the user to align the out of focus graph to the graph
in focus. (This option is found in the Edit menu). It is also possible to keep the two graphs perma-
nently aligned by selecting the Keep Data Aligned in the Options menu.
Two Point Merges should only be used once the data has been tied in. The user should select a
pass by placing one cursor at the beginning of the pass and another at the end of the pass.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-4
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
When the Two Point merge option in the Edit menu is selected, the graph out of focus will be
aligned to the graph in focus and the pass will be highlighted in grey. The user is prompted to name
the selected pass.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-5
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
Three point merges can be selected without a Tie-In being set. The user should select a pass by
placing a cursor at the beginning of the pass and another at the end.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-6
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
Once the cursors are positioned, the 3 Point Merge option should be selected from the Edit
menu. The user should then place a cursor at the beginning of the same pass in the other window.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-7
UWMemlog
Ultrawire™ Memlog Chapter 11. Merge Data
Once all the cursors are positioned, the Complete Three Point Merge option will be enabled
and the user can complete the pass by clicking on the Complete Three Point Merge option in
the Edit menu. The pass will be highlighted, and the user is prompted to name the pass.
It is possible to delete or rename any pass that has been created. These two options are available
from the Edit menu. When selected, the user can choose the pass they wish to delete or rename.
It is also possible to delete a pass using the right mouse button if the mouse pointer is on top of a
pass. In this case the pass under the mouse pointer will be deleted.
It is essential that the passes are saved once all the passes have been selected from a dataset.
The option in the File menu allows the user to save the passes to an ASCII file, also referred to as
the MRG file. This merge file is named Profilename.MRG and is used by Output Passes to create
the merged output from UWMemlog.
This document contains proprietary information. Copyright © Sondex. Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 11-8
UWMemlog
Ultrawire™ Memlog Chapter 12. Output Passes
12 OUTPUT PASSES
12.1 OVERVIEW
The Output Passes function generates the merged depth and tool data output. The
passes, selected in Merge Data, are displayed and the user can choose which passes are
to be output to the Warrior database.
Entering Output Passes is only possible once the raw tool and depth data are tied in and the
logging passes are selected in Merge Data.
UWMemlog outputs raw data into the Warrior database and each raw data pass gets a ".0" added
to its name. The program embeds all the information from the project directory, including the zoned
variables database and any tool calibration files.
Once all the raw data passes are written, Warrior Recalculation must be run on each pass to
produce the final calibrated data. By default the recalculated pass will have a ".1" added to its
name, but this can be changed.
For certain tools it will be necessary to edit some default logging settings in Recalculation, e.g. for
the RBT the user must set up the gate positions before the pass is actually started.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 12-1
UWMemlog
Ultrawire™ Memlog Chapter 12. Output Passes
The correction from logging depth to reference depth (e.g. RKB) may be entered.
Every chosen pass is listed in Output Passes by the name entered in Merge Data. A check box next
to each picked pass allows the user to select the passes to output. If the box is checked, the pass
will be output.
The Output names displayed are taken from the merge file, created in Merge Data. They can be
edited here and will become the raw pass name (with a ".0" added) when exported to the Warrior
database.
Note: It is not possible to generate the merged output if two Output names are the same.
There are two Output type options available to the user, one is depth, the other time.
When the passes are picked in Merge Data, the default output type is determined by the change in
depth over the pass. If the change is greater than 1 depth unit, the pass is considered to be a
Depth pass, less than 1 unit a Time pass. When Output Passes are entered, it uses these
assumptions to select the default Output type. The user should check that the types are correct
before generating the merged output and alter the type as necessary.
The time-based options only relate to time-based outputs. The user selects the sample rate at
which the data will be written into the Warrior database. The option is identical to the Warrior
prompt before starting a pass recording on Time.
If slow sampling is selected, the user is prompted to enter the number of seconds per sample, while
fast sampling is the number of samples per second.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 12-2
UWMemlog
Ultrawire™ Memlog Chapter 12. Output Passes
Note: If reselecting a database, the new pass names must not have a name that is already in use by
another pass. It is not possible to overwrite the Warrior database in UWMemlog.
Once all the options are set, click on the OK button to proceed.
When the dataset is created the user is prompted to automatically start Warrior Recalculation. The
recalculation process extracts the calibrated outputs from the raw memory data.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 12-3
UWMemlog
Ultrawire™ Memlog Chapter 13. Data Presentation
13 DATA PRESENTATION
The Warrior Logging Suite is used to present data, recorded by Ultrawire™ Memlog. For a
comprehensive guide to using Warrior, see MN-WARRIOR. MN-WARRIOR can be found on the
Sondex website.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 13-1
UWMemlog
Ultrawire™ Memlog Chapter 14. Operational Tips
14 OPERATIONAL TIPS
For operational reasons, it may be necessary to connect some of the tools in the tool string to the
UMT after the battery has been connected and the UMT is running.
This can cause problems for some Ultrawire tools because any toolbus activity during power up of
the tool can cause a latch-up of the electronics.
To avoid a latch-up becoming a problem for the log, include a short duration SLEEP line in the
profile, timed for after all the tools are connected. This will switch off the toolbus power and when it
comes back on at the next profile line, there will be no toolbus activity to cause a latch-up.
When the battery is connected to the UMT for the first time after programming, the UMT starts its
clock at time zero. If the battery is subsequently disconnected for more than a few seconds, the
current clock setting is lost. If it is then connected again, the UMT has to work out where to restart
from. It does this by reading the data recorded in memory.
The UMT records data in logical blocks (not related to physical blocks of memory). A new block is
started for every profile line and approximately every 32kB if no profile line change has occurred.
On a battery reconnect, the UMT will restart at the last logical block start time; data (and time) in the
partially recorded block can be lost, making it difficult to predict what the restarted UMT time will be.
To avoid this, if a UMT restart is planned, arrange it so that the battery is disconnected during a
SLEEP profile line. Then, when the battery is reconnected, the UMT will restart at the beginning of
the SLEEP period.
The number of memory tool restarts is reported to the user as part of the checking process after
downloading the data from the tool.
For a UMT Type 2, data is written to flash memory a page at a time. A page is 2kB of logged data.
When the battery is disconnected, any data that hasn't been written to flash yet is lost. That means
up to 2kB of data can be lost at the end of a job (or at any battery disconnect).
Normally this isn't a problem, as the user will allow plenty of recording time beyond the expected
logging interval of the well. However it could have unwelcome side effects if, for instance, a tool is
calibrated before a job and then the battery is disconnected.
To avoid the loss of data in these circumstances, add a SLEEP profile line and disconnect the
battery during the SLEEP period. Every time the UMT sleeps, it writes any partial pages to memory.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 14-1
UWMemlog
Ultrawire™ Memlog APPENDIX A. Troubleshooting
APPENDIX A TROUBLESHOOTING
Problem Solution
Operator cannot open Warrior. Check that the Warrior dongle is connected correctly
and its key code has been entered in Warrior Control
Panel. Check that the Hardlock drivers have been
installed (the Hardlock drivers are available to
download from the Sondex website).
UWMemlog cannot find Warrior. Make sure Warrior is installed on the PC, and that it
is V7.00 or later.
UWMemlog fails to communicate with the Check that the appropriate USB device drivers have
MCU or UMU. been loaded in Windows Device Manager. See
Section 3.2. Check that the correct UMT type was set
in Warrior before the project files were copied.` See
Section 5.1.
MCU or UMU fails to communicate with the Check that the cable is plugged in securely to the
UMT. UMT. Check that the correct UMT type was set in
Warrior before the project files were copied. See
Section 5.1.
Failure downloading data from UMT. Check that the cable is plugged in securely to the
UMT. Try the Save All option, see Section 6.1.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 A-1
UWMemlog
Ultrawire™ Memlog APPENDIX B. File Structure
B.1 DIRECTORIES
Masters directory
This directory contains a master copy of UWMemlog.ini, and other files. The UWMemlog.ini is copied to the
main program directory when the program is first run, but is subsequently never used. They should not be
edited.
Whenever a new distribution of UWMemlog is released, only the files in the Masters directory will be over-
written, thereby preserving the user's current copies of these files.
Projects directory
The Projects directory houses the individual Project directories created by the user, e.g. Test.prj. Within each
Project directory are a number of files, which are described in Appendix B.2 File Formats.
Project.ini
Project.ini is unique to each project and is created when Service information is extracted from Warrior. It
contains specific tool information, such as the data type and size. It also includes channel definitions for each
tool and their data types and sizes. Do not attempt to manually edit this file.
Service.ini
Service.ini is created from the Service information in the currently selected Warrior Service, i.e. Sondex
Ultrawire™ Memory MIT. This file contains the Ultrawire™ information for each tool in the string, along with
calibration, filter and presentation information. Do not attempt to manually edit this file.
Vars.db
This file holds all the zoned variable information extracted from Warrior.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 B-1
UWMemlog
Ultrawire™ Memlog APPENDIX B. File Structure
*.pfl
Profile files are created by the Profile Editor. They store the profile lengths, types and sample rates used to
program the memory tool.
*.slg
Slang files are the binary version of the profile files that get uploaded to the memory tool.
*.log
The log file is created during tool programming and can give useful diagnostic information to Sondex if prob-
lems are encountered. The file contains driver version information and memory size.
*.dat
These are raw tool data files downloaded from the memory tool. If the current profile file is Test.pfl, the
downloaded data file will be Test.dat. Note that backups of existing dat files are automatically made to avoid
overwriting previously downloaded tool data.
*.crc
These are raw tool Cyclic Redundancy Check (CRC) files downloaded from the memory tool (for UMT Type 2
tools only).
*.raw
These are raw depth data files downloaded from the Depth Time Recorder. If the current project is Test.prj,
the downloaded depth file will be Test.raw by default.
*.dpt
Depth files are the calibrated version of raw files. If the raw file was called Test.raw, the depth file will be
named Test.dpt.
*.dxt
These are text files containing depth file (*.dpt) listing information.
*.txd
These are text files containing tool data file (*.dat) listing information.
*.mrg
Merge files are created during the visual merging of the tool and depth data. They contain tie-in and pass
information. If the current profile is Test.pfl, the merge file will be called Test.mrg.
Other Files…
All other files in the Project directory are copies of the Warrior calibration files used by the tools in the current
Service. These files are copied to Project directory when the Service and tool information is extracted from
Warrior.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 B-2
UWMemlog
Ultrawire™ Memlog APPENDIX C. Customising Software
A customer's logo can be placed in the workspace section of the main Ultrawire™ Memlog window, replacing
the default logo.
Logos must be sent to Sondex in bmp, gif, jpg, emf or wmf format and must be no larger than 500 pixels wide
by 250 pixels high. Sondex will then provide instructions on how to proceed.
This document contains proprietary information. Copyright © Sondex Wireline Limited 2005-2010. All rights reserved.
Document: MN-UWMemlog-E Created August 12, 2010 C-1