Professional Documents
Culture Documents
OrionNET en
OrionNET en
Version: 3.0
Publication Date: August 07, 2018
While every precaution has been taken in the preparation of this documentation, the publisher assumes no responsibility
for errors or omissions. Information in this documentation is subject to change without notice. No liability is assumed for
damages resulting from the use of the information contained herein.
NOV CTES
3770 Pollok Dr
Conroe, Texas 77303
Phone: 1-936-777-6200
Fax: 1-936-777-6312
After hours technical support: 1-936-777-6200
Email: CTESSales@nov.com
OR
CTESSupport@nov.com
Website: http://www.nov.com/ctes
United Kingdom
NOV Completion & Product Solutions
Intervention & Stimulation Equipment
Tofthills Avenue
Midmill Business Park
Kintore
Aberdeenshire
AB51 0QP
Phone: 44-1224-748797
Middle East
B-17, Oilfield Supply Centre
Jebel Ali Free Zone
P.O. Box 18633
Dubai
United Arab Emirates
Phone: 971-481-0132
Fax: 971-883-7087
CONTACT US ......................................................................................................................................................................................II
UNITED STATES .......................................................................................................................................................................................... II
UNITED KINGDOM ...................................................................................................................................................................................... II
MIDDLE EAST ............................................................................................................................................................................................ II
CHAPTER 1.........................................................................................................................................................................................2
ABOUT THE ORIONNET SOFTWARE ............................................................................................................................................................... 2
About OrionNET ................................................................................................................................................................................ 3
About the OrionNET Acquisition Server/Component ........................................................................................................................ 3
CHAPTER 2.........................................................................................................................................................................................4
INSTALLING ORIONNET SOFTWARE ............................................................................................................................................................... 4
System Requirements ........................................................................................................................................................................ 5
Hardware Controller ......................................................................................................................................................................... 5
Installing OrionNET Software ............................................................................................................................................................ 6
Connecting to an Acquisition Source .................................................................................................................................................. 9
Local Connection................................................................................................................................................................................ 9
CHAPTER 3....................................................................................................................................................................................... 10
USING THE CONFIGURATION UTILITY ............................................................................................................................................................ 10
About the Configuration Utility ........................................................................................................................................................ 11
Launching the Configuration Utility ................................................................................................................................................. 12
Configuration Settings ..................................................................................................................................................................... 13
Acquisition-componentConfigurations ............................................................................................................................................ 15
Creating a New Acquisition Configuration ....................................................................................................................................... 16
Data Sources and Outputs in Acquisition Configurations ................................................................................................................ 17
Using Equations ............................................................................................................................................................................... 48
Importing/ExportingConfigurations ................................................................................................................................................ 50
CHAPTER 4....................................................................................................................................................................................... 52
CALIBRATING CHANNELS ............................................................................................................................................................................ 52
About Calibration............................................................................................................................................................................. 53
Calibrating Channels ........................................................................................................................................................................ 54
Chapter 1
About the OrionNET Software
This chapter describes the capabilities of the OrionNET™ Software.
Certain NOV CTES products incorporate a modified version of OrionNET software. When this is the case, the
altered OrionNET functionality is described solely within the mentioned product user guide. No alteration to the
description of the base functionality of OrionNET software is found within this guide.
About OrionNET
Residing on a laptop or desktop PC, OrionNET software acquires and stores sensor data in a database. With the OrionNET
software's Graphical User Interface (GUI), a user can:
With Cerberus™ (version 9.x or above) software, monitor real-time measured values compared to predicted values,
monitor channels in relation to each other, and monitor real-time fatigue life calculations and real-time burst and collapse.
Because OrionNET software is Ethernet-based, modular, and configurable to individual requirements, almost unlimited
freedom to share data is now within reach.
Only one acquisition component can reside on a single computer. The acquisition component can have one or more local
network data sources. When multiple data sources are present, the acquisition component gathers data simultaneously
from each source.
Chapter 2
Installing OrionNET Software
This chapter describes the system requirements and tasks necessary to install OrionNET.
System Requirements
Table 1- Basic Requirements
Available Storage 10 GB
Display Resolution 1280 x 1024
Hardware Controller
If an older OrionTM controller model is in use, some features of OrionNET may not be available. Please contact NOV CTES
if the currently used Orion DAS was built before year 2000.
Immediately upon launching the Viewer, the software “looks” for locations – on the local network and on the computer
where the Viewer is running – that are running the OrionNET Acquisition component.
A popup may appear indicating that the user must obtain authorization to use the software. If this is the case, follow the
procedure described in To Authorize OrionNET after Installation.
• Click the “Internet” button (Option 1) to authorize OrionNET software via the Internet
• If the user is not connected to the Internet, or if Internet authorization fails (likely due to local firewall security
settings), use email or the telephone (Option 2) to obtain authorization. If possible, remain in front of the
computer when contacting NOV CTES.
7. Provide the Authorization Code to NOV CTES staff. Note that the [normally automatically filled] proprietary
information in the Authorization Code field above has been removed.
8. Enter the Access Key provided by NOV CTES staff
9. Click Verify to begin the authorization process
The user’s computer’s security and firewall configurations may block the authorization process. If notification is received
that either OrionNET or the Orion Acquisition Shell program is blocked, click Unblock to continue.
The first time OrionNET Acquisition is started, the Unit Description dialog appears requesting a name or description to
identify the computer on which the software is installed.
1. Enter an identifier that distinguishes this computer from any other on the network running OrionNET software. This
name is used to select an acquisition source (connection) with which to view acquired data via OrionNET.
Change the Computer Description by editing Settings from the Orion Configuration utility.
2. Verify that OrionNET Acquisition is authorized and acquiring data by observing a green light within the OrionNET icon
in the system tray
OrionNET v3.0 Software User Guide NOV CTES 8
2 | Installing OrionNET Software
• The user selects the menu option Orion > Connection from an open Viewer
• The user has lost connection with an acquisition source and automatic attempts to reconnect have failed
Local Connection
When the dialog initially opens, the software searches for local acquisition servers and populates the Select a local
acquisition source to connect to list with the servers it finds.
When the user clicks Refresh List, the software clears the list and scans the network again, repopulating the list with the
local-network servers it finds.
The acquisition Unit Description defined (see To set the OrionNET Acquisition Computer ID) is displayed with the
notation “(this computer).”
Chapter 3
Using the Configuration Utility
This chapter describes the activities necessary to successfully use OrionNET’s configuration utility.
The Configuration Utility can be password-protected to prevent unauthorized personnel from modifying the
configurations. See Security Preferences for more information.
When any of the above methods are used to access the configuration utility, a dialog similar to the following appears:
Configuration Settings
The user can determine the way OrionNET behaves with regard to:
1. From the menu bar in the configuration utility dialog, select Setup > Settings. The OrionNET Settings dialog appears.
1. To change the Computer ID, input the desired identifier in the associated field
2. To change the Startup/Shutdown style, click (to toggle) either Start/stop Acquisition with OrionNET Viewer or
Start/stop Acquisition with Windows
3. To determine when OrionNET applies Acquisition configuration changes, click (to toggle) Apply when restarting or
Apply Immediately
4. To select the configuration to use at startup, click (to check) Select configuration on Acquisition Shell startup
The ability to select configuration on Acquisition Shell startup is especially useful for technicians who move
between different hardware systems/units while using the same computer to start OrionNET.
5. To enable the ability to pause and restart Acquisition, click (to check) Enable Pausing and Resuming of Acquisition.
When this option is checked, two items become available (after Viewer/Acquisition restart) underneath the Acquisition
menu option in the Viewer: Pause and Resume.
6. Job based recording is a new feature for OrionNET 3.0. It instructs OrionNET to continue recording in the same database
each time OrionNET is started until the user indicates the job is complete. To return to the previous database method,
uncheck the Use job based recording of database checkbox.
Acquisition-componentConfigurations
Three configurations are standard with OrionNET software: Default (see Default Configuration), the Orion IV Simulator,
and the Orion V Simulator (see Orion IV and Orion V Simulator Configuration):
1. The Default configuration is pre-defined using the CTES Orion Network as its data source. The Default configuration
automatically connects to any Orion IV/ Orion V data acquisition system on the local network. The user should ensure
that computer network settings are correctly established before using this configuration. See Configuring the Local
Network for Communication with CTES Hardware for additional information regarding network settings.
2. The Orion IV and Orion V Simulators are predefined configurations. These emulate the Orion IV or Orion V Data
Acquisition System without actual hardware being present.
Selecting a Configuration
To select a configuration
1. From the configuration utility dialog, use the Configuration dropdown field to select from existing configurations
OR
Select Acquisition > Select Configuration from the Viewer (see Setting Up and Using the OrionNET Viewer)
menu bar
The Orion IV and Orion V simulators provide new users the opportunity to learn how the software interacts with the
hardware without the need for connection to a “live” Orion. Configuration, data recording, data display, and calibration
features all function as they do when a real hardware system is connected. Most diagnostic features function in relation to
the Orion V simulator, though diagnostic features are not as detailed as those found within the actual hardware system.
The Data Source Name is filled automatically; the user can change this name if desired.
6. Choose the data source from the dropdown list of available data source types. See Data Sources and Outputs in
Acquisition Configurations for a description of the standard data source types.
7. For each data source, the user must complete the following:
8. Configure its properties (see Configuring Data Source Properties for more information).
9. If applicable, add channels and configure their properties; configure channel properties for existing channels (see
Adding/Editing Channels for more information).
Data sources are any type of data input to the OrionNET system. This input could be a CTES hardware system,
third-party acquisition system, or calculated channels. Outputs are the lists (streams) of data sent out from the
OrionNET software to other data consumers. This could be any data consumer that uses a WITS or ASCII data
stream.
The standard OrionNET installation can acquire data from the following sources:
• ASCII via Serial: ASCII data (including text characters) transmitted via a serial connection (third-party
controllers)
• ASCII via TCP/IP: ASCII data (including text characters) transmitted via Transmission Control Protocol/Internet
Protocol
• Derived Channels: calculated channels based on an equation that uses one or more existing channels (from the
same data source or a different data source) as inputs. A derived channel can also be a calculation that doesn’t
necessarily use another channel for input, or it can simply be a random-number generator.
• OPC Client: reads data from an OPC (OLE for Process Control) server
• CTES Controller (Direct V2): an Orion III hardware system using a serial-based controller
• CTES Orion IV: an Orion IV hardware system using a single Ethernet-based controller
• CTES Orion V: an Orion V hardware system using a single Ethernet-based controller
• CTES Orion Network: a local network of Orion IV or Orion V controllers that conforms to the properties specified
in the configuration utility
• WITS Level 0 via Serial: Wellsite Information Transfer Specification Level 0 serial input
Data sources may be added and configured when the acquisition-component configuration is created (see Creating a New
Acquisition Configuration) or after the acquisition-component configuration is in place. See Adding/Editing a Data
Source for information about including a data source when the acquisition configuration is established. See Configuring
Data Source Properties for information about configuring these properties.
The standard OrionNET installation can output the following data types:
• ASCII via Serial: ASCII data transmitted via a serial connection (third-party controllers)
• WITS Level 0 via Serial: Wellsite Information Transfer Specification Level 0 serial output
Outputs may be added and configured similarly to the manner in which data sources are added and configured. See
Adding/Editing an Output for general information about adding/editing outputs. See Configuring Output Properties for
further information about configuring these properties.
Configure the properties of the data source by selecting the data source name from the configuration tree. The properties
for the data source appear in the right-hand portion of the dialog. Properties differ depending upon the data source type. See
the various data source types listed in Data Sources and Outputs in Acquisition Configurations for more information about
general differences between data source types.
If the hardware configuration is changed (for example, to add a sensor), the user must also make the
corresponding change in OrionNET’s Configuration utility.
If the selected configuration type is a stand-alone CTES Orion V data acquisition system, a dialog similar to the following
figure appears when the user selects a data source name from the configuration tree:
This message indicates that the computer network settings are incorrect and OrionNET is unable to communicate with the
Orion hardware.
This message indicates that OrionNET cannot locate the Orion controller specified in the configuration.
This message indicates that OrionNET can communicate with the Orion controller specified in the configuration.
To ensure that OrionNET can communicate with the controller, see Configuring the Local Network for
Communication with CTES Hardware.
4. If the user enters an incorrect fourth number and then selects Get configuration from controller or Save
configuration to controller, a red error message appears at the bottom of the OrionNET Configuration Utility dialog
5. If the user enters a correct fourth number, a dialog similar to the following figure appears:
TCP/IP addresses for Orion V data sources are prefaced with the first three octets being “192.168.5.”
6. Enter an Interval (between .1 and 3600) for how often the OrionNET software acquires data from the controller
7. Check the associated box to Automatically save [the present] configuration to [the] controller on startup, indicating
that the channel settings for the current data source are saved automatically and restored on startup
Use this function with caution! The Automatically save configuration to controller on startup option (when checked)
saves the configuration (including calibration settings) presently defined on the computer to the controller for
restoration when OrionNET is opened.
8. If the Orion V will be reading or sending a serial data stream, select Configure hardware serial ports to set up the
Orion V serial ports. See Setting Up Orion Hardware to Read Serial Data for details.
9. Select Configure hardware outputs to configure a digital output to sound an alert, shut down a system, and so forth.
See Orion V and OrionNET Hardware Outputs for more information.
10. Obtain all channels from a controller (removing any channel that was manually added to this data source) by selecting
Get configuration from controller.
11. Overwrite all the controller channels with those that were manually added to this data source by selecting Save
configuration to controller.
If the selected configuration type is a stand-alone CTES Orion IV data acquisition system, a dialog similar to the
following appears when the user selects a data source name from the configuration tree:
This message indicates that the computer network settings are incorrect and OrionNET is unable to communicate with the
Orion hardware.
This message indicates that OrionNET cannot locate the Orion controller specified in the configuration.
This message indicates that OrionNET can communicate with the Orion controller specified in the configuration.
To ensure that OrionNET can communicate with the controller, see Configuring the Local Network for
Communication with CTES Hardware.
4. If the user enters an incorrect fourth number and then selects Get configuration from controller or Save
configuration to controller, a red error message appears at the bottom of the OrionNET Configuration Utility dialog
5. If the user enters a correct fourth number, a dialog similar to the following figure appears:
TCP/IP addresses for Orion IV data sources are prefaced with the first three octets being “192.168.4.”
6. Enter an Interval for how often the OrionNET software acquires data from the controller
7. Check the associated box to Allow [the] user to override default alarm/warning settings in OrionNET with the
alarm/warning settings on the ROVer™ (field equipment)
8. Check the associated box to Automatically save [the present] configuration to [the] controller on startup, indicating
that the channel settings for the current data source are saved automatically and restored on startup
Use this function with caution! The Automatically save configuration to controller on startup option (when checked)
saves the configuration (including calibration settings) presently defined on the computer to the controller for
restoration when OrionNET is opened.
9. To send a serial stream to the Orion IV data acquisition system (via another acquisition system), or to output a serial
stream from the Orion data acquisition system, select Configure hardware serial ports. See Setting Up Orion
Hardware to Read Serial Data for details.
10. Select Configure hardware outputs to configure a digital output to sound an alert, shut down a system, and so forth
11. Obtain all channels from a controller (removing any channel that was manually added to this data source) by selecting
Get configuration from controller
12. Overwrite all the controller channels with those that were manually added to this data source by selecting Save
configuration to controller
If the configuration type is a CTES Orion Network, a dialog similar to the following figure appears:
1. Enter an Interval for how often the OrionNET software acquires data from the controller
2. The Controller Type field determines what type of Orion systems to communicate with. Choices are Orion IV systems
only, Orion V systems only or both via the All Controller Types selection.
3. The Start IP address and End IP address fields provide the acquisition software a range of IP addresses in which to
find controllers
If the configuration type is Derived Channels, a dialog similar to the following appears when a data source name is
selected from the configuration tree:
1. Enter an Interval for how often the OrionNET software acquires data from the controller
Channels selected as rates calculated from other channels will be calculated at a fixed interval of one second.
2. Add channels to the data source (see Adding/Editing Channels for additional information)
If a configuration type is ASCII via Serial, a dialog similar to the following appears when a data source name is selected
from the configuration tree:
1. Enter an Interval (between .1 and 3600) for how often the OrionNET software acquires data from the controller
2. Enter or select from the associated dropdown the COM Port, Bits per second, Data bits, number of Retries, Parity,
and Stop bits for the data transmission
3. Click to select the appropriate radio button for the Stream delimiter and Stream separator
4. The Retain last channel value checkbox instructs OrionNET how to treat missing data. When unchecked, data source
channels will indicate an error state and be stored as such. When checked, data source channels will keep their last value
until data is successfully read again.
5. The Use date and time from incoming data stream checkbox instructs OrionNET how to handle dates and times.
When unchecked, OrionNET ignores the date and time and stores data at the current computer time. When checked,
OrionNET will store data at the nearest date/time in the database as the date/time in the data stream.
6. Add ASCII via Serial channels to the data source (see Adding/Editing Channels for additional information)
If a configuration type is CTES Controller (Direct V2), a dialog similar to the following appears when a data source name
is selected from the configuration tree:
1. Enter an Interval (between .1 and 3600) for how often the OrionNET software acquires data from the controller
2. Enter or select from the associated dropdown the Controller name
3. Click (to check) the associated radio button to enable WITS level 0 output, or to automatically save the configuration to
the controller on startup
4. To remove all source channels and replace them with those in the controller, click the Get configuration from
controller button. This is a good idea for this particular data source in cases where the user inadvertently shuts down the
Orion box prior to shutting down OrionNET.
5. To overwrite channels in the controller with the channels in the current configuration, click the Save configuration to
controller button.
6. To manually add or remove channels, see Adding/Editing Channels
If the configuration type is OPC Client, a dialog similar to the following appears when a data source name is selected from
the configuration tree:
1. Enter an Interval (between 0.1 and 3600 seconds) for how often the OrionNET software acquires data from the
controller
2. Enter the OPC server name
3. If the OPC server resides on a computer other than the computer OrionNET is installed on, check the OPC server is on
another computer checkbox and enter the name of the computer
The OPC server must be on the same network as OrionNET to work. Also, some OPC server installations have
security settings and require permissions to be set to allow OrionNET to read data.
4. Add OPC channels to the data source (see Adding/Editing Channels for additional information)
If the configuration type is WITS Level 0, a dialog similar to the following appears when a data source name is selected
from the configuration tree:
1. Enter an Interval (between 0.1 and 3600 seconds) for how often the OrionNET software acquires data from the
controller
2. Select the COM Port from the associated dropdown
3. Enter the possible number of Retries (a positive integer between 0 and 10)
4. Select the Bits per second from the associated dropdown
5. Select the Parity from the associated dropdown
6. Select the Data bits from the associated dropdown
7. Select the Stop bits from the associated dropdown
8. Add WITS Level 0 channels to the data source (see Adding/Editing Channels for additional information)
If the configuration type is ASCII via TCP/IP, a dialog similar to the following appears when a data source name is
selected from the configuration tree:
1. Enter an Interval (between 0.1 and 3600 seconds) for how often the OrionNET software acquires data from the
controller
2. Enter the possible number of Retries (a positive integer between 0 and 10)
3. Input the TCP/IP address
4. Input the TCP/IP Port
5. Click (to toggle) the Stream delimiter (comma, space, or tab)
6. Click (to toggle) the Stream separator (carriage return, line feed, carriage return plus line feed, or other)
7. The Retain last channel value checkbox instructs OrionNET how to treat missing data. When unchecked, data source
channels will indicate an error state and be stored as such. When checked, data source channels will keep their last value
until data is successfully read again.
8. The Use date and time from incoming data stream checkbox instructs OrionNET how to handle dates and times.
When unchecked, OrionNET ignores the date and time and stores data at the current computer time. When checked,
OrionNET will store data at the nearest date/time in the database as the date/time in the data stream.
Configure the properties of an output by clicking the output name in the configuration tree. The properties for the output
appear in the right-hand portion of the dialog. Properties differ depending upon the output type. See the potential output
types listed in Data Sources and Outputs in Acquisition Configurations.
One of two dialog types appear when the user selects an output name from the configuration tree: ASCII Serial Output or
WITS0 Serial Output.
If the output type is ASCII Serial Output, a dialog similar to the following appears.
Figure 31 - Configuration Utility: CTES Orion V Properties; Output Dialog ASCII Serial
4. Click (to check) Output in WITS ID order if desired (Using this feature helps to guarantee the data output order – this
is especially pertinent if more than one data source is used)
5. Click (to check) Fill WITS Output Gaps if desired (Using this feature inserts placeholder values in the data)
If the output type is WITS0 Serial Output, a dialog similar to the following appears.
Figure 32 - Configuration Utility: CTES Orion V Properties; Output Dialog WITS0 Serial
3. Click (to check) Include date and time in WITS output if desired
For WITS output to work, you must enter a WITS ID number for each channel to be output. To set the WITS ID
numbers, choose the channel(s) from one or more of the data sources in this configuration and enter a value
greater than 0.
When date and time are included in the WITS stream, they use WITS ID 105 and 106. Make sure no other
channels use these WITS ID numbers.
WITS0 Serial Output automatically sorts by WITS ID, so Output in WITS ID order is not a necessary or available
selection.
To . . . Do this . . .
Right-click the configuration name or a data source
name in the tree.
Add a data source Select Add Data Source from the menu.
Enter the name of the data source.
Adding/Editing an Output
To . . . Do this . . .
Right-click the configuration name in the tree.
Select Add Output from the menu.
Add an output Enter the name of the output.
Select the output type from the dropdown.
Adding/Editing Channels
Each data source has one or more channels associated with it.
The user can also add/edit channels in either of the simulated configurations: the Orion IV Simulator or the Orion V
Simulator.
ASCII via Serial and ASCII via TCP/IP data source types allow for setting the Data Type as Numeric Data or Text
Data.
To . . . Do this . . .
Click the channels icon ( ) in the Configuration
Utility toolbar, or right-click 1010 Channels under the
Add a channel appropriate data source.
Enter the name of the channel.
Channels from different data sources have different properties. Observe the current properties of a channel by selecting the
channel name in the tree on the left-hand side of the dialog.
OrionNET supports duplicate channel names across data-engine sources in a single configuration, but does not allow
duplicate names in the same data source. For example, Derived Channels cannot have two channels named Weight.
When a data source is selected in the tree, the Channel Properties dialog is disabled.
Property Notes
Channel type is required when the data is used for
modeling purposes. Cerberus software needs to know
what channels to use for Depth, Wellhead Pressure,
Circulating Pressure, and Weight.
No two channels should have the same type, except type
Channel type
"Other," even if they are from different data sources. If,
for example, there are two weight readings, select
"Weight" as the type for one channel, and "Other" as the
type for the other channel.
Advanced
Turning this option “on” enables data averaging.
Enable data averaging It is used to “smooth out” data fluctuations to allow the
trend to become apparent.
The dialog below is a representation of the ASCII via Serial channel configuration.
Property Notes
The type of data can be either Numeric Data or Text
Data Type Character Data used for the Channel Digital boxes in the
OrionNET Viewer.
The initial low end of the range used for gauges and
Scale low charts in the OrionNET Viewer. (Numeric data only)
The initial high end of the range used for gauges and
Scale high charts in the OrionNET Viewer. (Numeric data only)
The dialog below is a representation of the ASCII via TCP/IP channel configuration.
Property Notes
The type of data can be either Numeric Data or Text
Data Type Character Data used; for the Channel Digital boxes in
the OrionNET Viewer.
The initial low end of the range used for gauges and
Scale low charts in the OrionNET Viewer. (Numeric data only)
The initial high end of the range used for gauges and
Scale high charts in the OrionNET Viewer. (Numeric data only)
Property Notes
Analog, Counter, Rate, Quadrature, Thermocouple,
Calculated Rate, Calculated Rate (Quadrature), Calculated
Counter, Calculated Counter (Analog), CTES FWA,
Sensor Type CTES FWA Rate, and External. NOTE: CTES FWA and
CTES FWA Rate is a separate option available for
purchase. Contact CTES for more information.
The initial low end of the range used for gauges and
Scale low charts in the OrionNET Viewer.
The initial high end of the range used for gauges and
Scale high charts in the OrionNET Viewer.
Property Notes
Analog, Counter, Rate, Quadrature, Thermocouple,
Calculated Rate, Calculated Rate (Quadrature),
Sensor Type Calculated Counter, Calculated Counter (Analog), and
External.
In the dialog below, the configuration is ready for channel setup (see Adding/Editing Channels). The user can create and
alter the properties of various channels to best fit operational needs. See Derived Channel Properties for more information.
Property Notes
In certain situations, the user may want to monitor data
that is not calculated from sensor inputs from the Orion
IV or Orion V hardware system; for example, fluid
volumes during job stages, cumulative fluid volumes
from multiple pumps throughout a job, and differential
Derived channel type pressures. However, the OrionNET software provides
for adding derived channels that are calculated from any
number of channels that OrionNET is monitoring. The
channels used in the calculations can be sensor inputs or
other derived channels.
Property Notes
Here, channels are derived from an equation that can be
entered in the Orion Configuration Utility. See Using
Equation Equations, below, for more information.
Using Equations
The use of equations is one method for calculating a derived channel.
Addition, subtraction, multiplication, and division are supported in the equations. Standard mathematical order of
operations rules apply.
The equation can consist of any combination of numbers and channels. Channels must be enclosed in curly brackets {}.
When it is time to calculate the derived channel's value, Orion scans the equation for the curly brackets. It matches up the
names of the channels in the brackets and substitutes their current values into the equation. It then calculates the value of
the resulting expression.
Example: Let's assume we have 3 individual pump volume channels and would like to monitor the total volume in a
derived channel. The equation for this channel would be:
Other functions supported are described in the table in Calculating Derived Channels with Equations.
Property Notes
The item in the OPC server where this channel’s value
OPC item is found.
Property Notes
The WITS ID that points to the channel’s value. The
data source does not acquire data for channels with no
WITS ID
WITS ID specified (WITS ID =0).
Importing/Exporting Configurations
The user may import/export configurations.
To import a configuration
1. Within the OrionNET Configuration Utility, select File > Import from the menu bar. The Open Windows Explorer®
dialog appears.
OR
To prepare all configurations for import, click the double right-pointing arrow icon
6. Click OK
A Windows file dialog appears from which the user selects the destination for the imported file(s), and then completes the
import process.
To export a configuration
1. Within the OrionNET Configuration Utility, select File > Export from the menu bar. The Export Configurations dialog
appears.
The Export Configuration(s) Windows Explorer dialog appears, from which the user selects the destination for the
exported file(s), and then completes the export process.
Chapter 4
Calibrating Channels
This chapter describes the activities necessary to successfully calibrate input sensor channels for an Orion V and IV data
acquisition system.
About Calibration
The OrionNET software can read data from varied sources; these sources are set up for OrionNET acquisition within the
OrionNET Configuration Utility (see Using the Configuration Utility for more information).
The user’s ability to calibrate channels depends on the type of data source from which data is acquired. CTES hardware
systems are the only systems that support calibration.
The user may calibrate channels only when the OrionNET software is connected to the Orion data acquisition
system running on the same machine as the Viewer.
Calibrating Channels
To calibrate channels
1. Ensure that the OrionNET acquisition component is acquiring and recording data by observing the green light on the
Acquisition icon in the system tray
2. From the Viewer menu bar, select Orion > Calibrate. A dialog similar to the following appears:
Figure 44 - Calibrate
As noted in the dialog, only channels that can be calibrated are displayed in the list on the left-hand side of the
dialog.
3. Select the channel to calibrate. Information for calibrating the channel appears within the righthand side of the dialog
4. Make changes to the existing channel information as needed. Examples follow below.
5. Click Set to finalize changes.
Due to limitations and varied capabilities of physical hardware systems, the channel calibration process varies among the
different data sources from which OrionNET can acquire. This section covers the calibration of channels from CTES Orion
V / Orion IV hardware systems. To calibrate channels from other data sources that support calibration, follow the on-screen
instructions.
Analog channels receive data from analog sensors connected to CTES hardware. Typically, these analog sensors are 4-20
mA. Circulating pressure, wellhead pressure, and weight are common examples of analog channels.
The Orion V / Orion IV data source provides two methods for calibration: fine-tune and standard.
The fine-tune calibration method is used to adjust a channel’s calibration table when its value is within the scale-range of
its sensor. This method is intended for use when a channel’s calibration is close, yet differs from the gauge reading the
channel mirrors.
This method adds a data point in the calibration table of the selected channel. If a data point exists in the
calibration table that is within 0.1 mA of the new point, this previously existing point is replaced with the newly
added point.
The fine-tune calibration method cannot be used if the channel value is currently outside the sensor range. This
can occur if the channel’s sensor is not functioning or is disconnected. In either case, a message appears
indicating the sensor is not functioning, and it is suggested that the standard calibration method (the only
remaining available method) be used.
The value entered must be within the sensor range displayed on the calibration panel. If an adjustment to the
sensor range is required, select the Standard Calibration method.
A channel’s calibration table is limited to 30 data points. If the user attempts to exceed the maximum number of
data points, an error message appears.
The standard calibration method is used when a channel’s senor range requires modification. This would occur if a sensor is
replaced with a sensor of a different range.
4. Click the Insert button to add a new row to the table. When scaling a non- linear channel (as in the dialog above), the
user may add more (up to 30) calibration points. The new row is filled with the current signal-value of the new point.
5. Click within the corresponding Scaled value field and enter the scaled value for the new point. The user may also alter
the Raw value (mA) field.
6. Click the Set button to save and activate the calibration settings
If there are more than two data points in the calibration table, the Advanced mode is the only option available for
standard calibration.
Quadrature channels receive data from quadrature encoder sensors connected to CTES hardware. Depth is the most
common type of quadrature channel.
The red arrow indicates the current step in the calibration process. The process automatically determines which
step it is performing.
Remain on the default Calibrate screen (Fine Tune calibration), and complete the following:
If there is no depth change for one minute after clicking the Start button, the calibration process times out and
must be restarted.
The calibration process calculates the correct calibration factors based on the inputs received and sets the current depth to
the new depth value.
OR
If you know the Gain value, the Diameter or Circumference of the measuring wheel, and the Encoder pulses per one full
revolution of the wheel, select Standard Calibration.
Figure 48 - Calibrate
Counter channels count non-directional pulses. These sensors are typically proximity switches or magnetic pickup sensors.
A pump volume is an example of a counter channel.
2. Before clicking Set to finalize changes, verify that the Proposed value corresponds to expected results
Calibrate other channels by setting a gain and an offset. The gain and offset for each channel is stored in the hardware, and
can be read and changed from within the OrionNET software.
1. As noted in the Calibrate dialog, set the Gain and Offset according to the following:
2. Volume channels: gain is the amount of volume for one count of the sensor
3. Rate channels: gain is the gain of the associated volume/depth channel, multiplied by 60
Chapter 5
Setting Up and Using the OrionNET Viewer
This chapter describes the procedures necessary to set up and to alter the way information is displayed within the
OrionNET Viewer.
The user may set up the Viewer to display acquired and recorded data in arrangements (views) that are most meaningful for
an operation.
The user may open multiple Viewers, each with a connection to a different acquisition source. See Connecting to
an Acquisition Source for more information.
Figure 52 - Preferences
1. Go to the Viewer menu item File => New Database (Start new job) to start one immediately
OR
When exiting OrionNET, click the Yes button when prompted on the status of the job database. A new database will be
created when OrionNET is next launched.
1. In the Viewer Main Menu go to Setup => Preferences. On the General Tab, click on the blue text below “Database
Naming Template” to access the naming format options window.
2. Click (to toggle) the default naming template to be used by OrionNET when acquiring and saving job data
OR
1. Continue a previous job
1. From the Viewer main menu, select File => Exit an exit dialog box is displayed. The question shown is “Do you want to
end this job?”. If the user wants to continue a previous job, click on “No” for “Continue this job next time.”
1. Select a tab or hover over any tab [with the mouse]; the tab’s contents “slide” out (to the right) and onto the left-hand
portion of the Viewer
2. A small “pin” icon appears in the upper right-hand corner of the tab contents area
3. Mouse over (hover over) the pin with the mouse to see the “tool tip” text Click to pin
4. Click the pin icon; the pin points downward and the tool tip text becomes Click to Unpin
When the contents of the tab stay in the View Manager, they are “pinned” in place.
While the tab contents are pinned/visible in the View Manager, the corresponding tab label is not available in the left-side
tabs; however, the label is visible in the management area next to the pin. The label of the active View is highlighted in
blue.
When different tab-contents are pinned open in the View Manager, they appear stacked (one on top of the other) or
immediately next to each other. To allow more or less area to be displayed within each area, click and drag (using the
mouse) on the gray, horizontal line above the tab-content name to adjust its size.
Pinned tabs can be resized. Hover the mouse near the right edge of a pinned tab. The cursor changes shape. Click and drag
(using the mouse) on the altered cursor to horizontally resize the pinned tab.
The Comments tab has a filtering capability, so that comments can be viewed according to the application- groups
to which they belong.
See Defining Predefined Comments for information about how the application-groups are created and maintained.
Using Views
The following image shows the Views tab-contents pinned to the management area.
When the Views tab-contents are pinned to the View-manager area, selectable icons for each of the currently available View
designs appear (see Views Pinned). Three default Views are standard with OrionNET: Chart, Digital Gauge, and Limits.
To see a View name, mouse over (hover over with the mouse) an icon.
The Options button in the Limits view allows the user to change settings for Stress Envelop safety factors, collapse
models and helical buckling.
Figure 62 - Options
To use a view
Using Data
If the software is connected to a local acquisition source, a Data tab is included in the left-hand Viewer tabs. When the
Data tab is clicked or pinned to the view-management area, selectable icons for each of the currently available Data Log
types are visible. Four types of data log are available:
Hover over [with the mouse] each icon to reveal the data-log type; then select the icon corresponding to the log-type
desired. Table-formatted log-type data becomes available.
Within the Job Log, hover over a channel-name column heading (top of the display screen) to reveal the data source and
channel name separated by a hyphen (data source-channel name). This is of importance when duplicate channel
names exist within multiple data sources in a single configuration.
The Data Tab does not show diagnostics messages that appear on digital displays.
Local and Global alarms and warnings are set up by the user in the Channel Properties dialog (see Channel Properties).
These are the actual alarm/warning numbers present at the time the alarm/warning was activated. Only Global alarms are
visible; these are stored in the database and are monitored by all remote Viewers.
In relation to alarm and warning flags, the Time column represents the point in time when an alarm/warning
becomes active, or goes “in state.
When large job logs are opened for the first time, the user can still perform other actions in OrionNET while the log
is opening in the background.
To see active alarm/warning information, click the Alarm/Warning icon when it appears in the lower right-hand corner of
the Job Log.
Only global alarms are shown. Local alarms are not shown here.
1. Click the associated buttons at the top of the log area, or right-click a comment and select an action
2. Click Select All to perform an action on all comments
3. See Using Chart Comments for additional information
Comments may be added to a chart by typing the comment individually or by inserting it as a predefined comment.
Predefined comments are available as selections from a list in the Comment dialog or as buttons on the Comments tab in
the Viewer.
2. Click the Manual Comment button at the bottom of the open/pinned Comments tab in the View Manager (see
After completing one of the four methods of accessing the Comment dialog described above, continue the process as
follows:
1. Enter a comment or select a predefined comment from the dropdown associated with Enter Comment (See To define a
comment for the predefined comment list for more information)
2. Associate a comment with a channel by selecting the channel from the Associate with Channel dropdown
3. If desired, click (to check) Display comment on the chart. If the Manual Comment button is used, the box is not
checked by default.
4. Select a category for the type of comment to help organize or group comments. This feature can be used for customized
reports to provide a time summary for the job.
5. Click on the ellipsis button to access the Manage Comment Categories dialog box:
6. Click OK after making desired selections from the Comment dialog box
1. Comments “predefined” in the Comments Editor become available within the Comments tab of the Viewer. Click on a
Viewer comment button to add that comment to the chart.
Set up in “comment pairs” to print (in Reports) the range of data between the first comment and the second
comment in the pair.
1. Open the Comment dialog (See To add comments to a chart using the Comment dialog)
2. Click Edit comment list
a. The Comments Editor dialog appears
1. Click the ellipsis button to the right of the Application field. The Edit Applications dialog appears.
2. Add, edit, or delete an application by clicking the associated button. Click Close when done. The added application is
available from the Application dropdown.
Comment pairs allow the printing (in Reports) of the range of data between the first and last comment in a pair. These
comment pairs are set up in the Viewer.
1. Within the Comments Editor dialog, click Set up Comment Pairs under Advanced. The Set up Comment Pairs dialog
appears.
2. Select Start Comment and End Comment from the associated dropdowns
3. Click the Add button
The comment is deleted from the Paired Comments list after the user confirms the deletion.
Importing/Exporting Comments
To import/export comments
1. Within the Comments Editor dialog, click either Import or Export under the Import/Export portion of the dialog
2. Use the Windows dialog to Import or Export the file
Comment Categories
1. The Category is also exported with the comments. The Category is used to focus a report on Plug Milling operations, the
Comment Category is added. Also included within the Comments Editor is the Comment Function setting that specified
if the comment with be associated with a Plug Milling operation that is ether Plug Start or Plug Stop, or None if the
comment is not related to plug milling.
The user may start a new job by way of the File menu option. See To start a new job (create a new database).
Rename Database
The user may rename the current database using the Rename Database dialog.
To rename a database
1. Select File > Rename Database to reveal a dialog similar to the following:
2. Select Make New Folder to create a new folder for better organization of job databases
3. Click (to check) Set my default datalog directory to . . .
4. Click to select an Existing Folder. The default datalog directory changes to reflect the selected folder
5. Click (to check) Set my default datalog director to . . .
6. To rename the current database, enter new or additional information in the DataLog Name field and click OK
7. The default Database Naming Template is initially available in the DataLog Name field
8. To change the default Database Naming Template, select the link associated with the field Database Naming Template
to reveal the related dialog
9. Click (to toggle) the default naming template to be used by OrionNET when acquiring and saving job data
Open Database
When the user opens an existing database, the data collected by OrionNET from that point forward is appended to that
database.
1. Select File > Open Database to reveal a dialog similar to the following:
Back Up Database(s)
To back up databases
1. Select File > Backup Database(s)... to reveal a dialog similar to the following:
2. Use the ellipsis to select the path where the data log(s) are to be backed up
3. Click (to check) individual data logs or use the Select All button to select all data logs
4. Unselect All using the same-named button
5. Click Save
Job Information
1. Select File > Job Information to reveal a dialog similar to the following:
2. Enter the job information most relevant for the operation. Use dropdown boxes to select from existing information; enter
information in the dropdown fields to be stored and “remembered” for future use; enter other information as needed.
Job Information is only available when the Viewer and the Acquisition component to which the Viewer is
connected are running on the same computer.
Connection
See Connecting to an Acquisition Source for information concerning use of the menu option
Select a job to be used in relation to these monitors by selecting, from the menu bar, Orion > Monitors > Set Job.
Channels
To set channel display properties for the current data source, select Orion > Channels from the menu bar. See Configuring
Channel Properties for more information.
Calibrate
To calibrate channels for the current data source, select Orion > Calibrate from the menu bar. See Calibrating Channels for
more information.
To pause Acquisition
In the Acquisition Menu option, click Acquisition > Pause. Click the dropdown list to specify the amount of time to
pause Acquisition (maximum one hour). Also input the reason for pausing. An entry will be added to the Event Log
indicating when acquisition was paused.
To resume Acquisition
Authorize
Select Configuration
By selecting a configuration, the user “tells” the acquisition server/component the type of hardware it will “talk to.” See
Using the Configuration Utility for additional information.
To select a configuration
1. Select, from the Viewer menu bar, Acquisition > Select Configuration
OR
Right-click the Acquisition icon in the system tray
2. Click Select Configuration
The Orion IV and Orion V simulators provide new users the opportunity to learn how the software interacts with the
hardware without the need for connection to a “live” Orion. Configuration, data recording, data display, and calibration
features all function as they do when a real hardware system is connected. Most diagnostic features function in relation to
the Orion V simulator, through diagnostic features are not as detailed as those found within the actual hardware system.
If the Orion IV or Orion V simulator is the selected configuration (see Select Configuration), the OrionNET Simulator
Mode popup appears, indicating that either the Orion IV or Orion V simulator is in use.
To view the simulator console, click Show Simulator Console within the popup.
Click the “X” in the upper right-hand corner of the console to minimize it.
If the simulator console becomes hidden behind other screens, or if it is minimized, click Show Simulator Console to
bring it back to the top.
When the simulator console is showing, a simulator icon appears in the task bar.
The simulator console allows users to adjust signal and counter inputs that provide simulated data for OrionNET to read,
display, and record. The simulator also allows the user to simulate whether or not the EMU device is functioning
correctly. Note that the simulator does not actually simulate an EMU, in that the user cannot download EMU files from
the simulator configuration. Rather, it provides the simulation of whether or not an EMU is responding to the system.
Users can edit the simulator configurations to add or remove channels just as in CTES hardware systems. Users can also
save settings to the controller, which saves them to the simulator.
Only channels whose sensor types are hardware sensor types (analog, quadrature, counter) can be manipulated
through the Simulator Console.
Two modes are available for controlling simulator input: manual and automatic.
The manual mode provides controls (input fields, as used elsewhere in the Viewer) for the manual adjustment of input
values for both analog and other channel types, such as digital channels.
The automatic mode generates input data automatically for each channel. Analog channels start updating immediately by
cycling through the scale range (Low/High). Other channels, including digital channels, require user input to generate the
automatic-mode data.
The automatic mode provides sliders for analog channels that show each channel’s (Low/ High) scale range (as set up by
the user in the Configuration utility). The user can adjust the sliders to change analog-channel input values, or can change
the control input fields, which then adjusts the sliders to correspond to the input values.
To input all data using one mode or the other, click either the Automatic (All) button or the Manual (All) button.
Even if the Automatic (All) or Manual (All) button is clicked, the user can still select the mode to input individual
channel information: Click (to toggle) either Automatic Mode or Manual Mode within the settings for each
channel.
High and Low values can exceed the actual high and low scales via text-box inputs. This allows the user to input
values outside the expected range. An example might be the user simulating an mA value less than 4.0.
When working with real Orion systems AND with Orion IV or Orion V Simulators, the user can change the default
channels included in the configuration. In all cases (whether real Orion systems or simulated Orion systems), it is
necessary to Save Configuration to Controller in the Configuration Utility (see Launching the Configuration Utility for
instructions) for the changes to take effect.
1. Select, from the Viewer menu bar, Acquisition > Select Configuration
The Launch OrionNET Reports menu option launches OrionNET Reports directly from the Viewer. See Using OrionNET
Reports for information about OrionNET Reports.
Print Report
Available reports are determined in the Report Designer (see Report Designer).
The Monitors menu contains items to link OrionNET data with Cerberus fatigue and forces models in real-time. Fatigue
and forces projects are also stored in the OrionNET database for use with OrionNET Reporting.
1. In the “Select a Fatigue Project” Dialog box the Coiled Tubing Projects icon
1. In the “Select an Orpheus Project” Dialog box, select Coiled Tubing Projects
Force Monitor
Launches Orpheus in real-time Force Monitor mode. The Orpheus project prompt will be displayed if an Orpheus project
has not yet been selected for the current job.
Fatigue Monitor
Launches Reel-Trak in to calculate fatigue in real-time. The Fatigue project prompt will be displayed if a fatigue project
has not yet been selected for the current job.
Preferences
1. Select Setup > Preferences to reveal the Preferences dialog, which contains four tabs: General, Alarms, Security, and
Display
2. Select the General tab within the Preferences dialog to complete the following:
3. Change the rate (in seconds) at which the Viewer receives data from the Acquisition server
1. Enter a decimal number greater than zero in the Viewer data rate field and click OK
2. Launch Quick Start on OrionNET startup, for the purpose of:
3. Selecting an existing OrionNET database and appending to it newly acquired data
4. Launching real-time monitors (Force Monitor and/or Fatigue Monitor). See Accessing the Viewer for more information
about using Quick Start.
5. Prompt the user to select an Orpheus project if/when the user starts the Force Monitor
6. Choose a Database Naming Template
7. Set the system date and time
8. Select the Alarms tab within the Preferences dialog to complete the following:
9. Enable sounds (to be heard through the computer speakers) for Alarms and/or Warnings.
Alarm sounds are discontinued when the alarm is acknowledged, even when the alarm condition persists
Security Preferences
1. Select the Security tab within the Preferences dialog to complete the following:
2. Enable a View Designer password, a Configuration Utility password, or a Reporting password, or any combination
thereof
3. When the Enable View Designer Password or the Enable Reporting Password checkbox is clicked, a Change button
appears within the Security-tab dialog. Click the Change button to update the password.
4. In order to change a password, the user must know, and input, the most current pre-existing password
5. To remove the password requirement, click (to uncheck the previously checked) Enable View Designer Password or
the Enable Reporting Password checkbox, and input the current password
Display Preferences
1. Select the Display tab within the Preferences dialog to complete the following:
2. Choose from among four Viewer display themes: Classic, Shadow, Metal, or Windows
3. Choose from among three font sizes to determine the appearance of the on-screen text: Small Fonts, Medium Fonts, or
Large Fonts
4. Click (to check) to Enable Touch Screen Support
Language Set-up
The user may set the language to use in the OrionNET Viewer interface. Russian, English, and Chinese are available.
Changes made to the current, operative view are automatically saved, so the next time the view is accessed, the changes
remain in place.
Changes made via the View Designer may be saved to the current, operative view, or saved to create a new view.
See Working with Controls in the View Designer or Viewer to ensure that work is saved in adherence with the
desired purpose
Use the View Designer to place and define the controls that define the appearance of data within a view; in other words, use
the View Designer to customize the way OrionNET displays acquired data.
To launch the View Designer, click the Start View Designer icon in the lower left-hand corner of the OrionNET Viewer
within the Views tab (located on the lower left-hand side of the OrionNET Viewer within the Views tab).
By default, the View Designer opens the currently selected View in edit mode. If the goal is to create a new View, select File
> Save As... from the View Designer’s menu bar; otherwise, the existing View is replaced with any changes.
The user may add controls to a selected view only via the View Designer. The user may edit the various controls
associated with a selected view either within the View Designer or the Viewer. These controls include chart displays,
digital displays, gauge displays, level displays, state controls, button displays, labels, images, and limits monitors.
The left-hand side of the View Designer provides a View Manager area similar to the one in the Viewer, except the only
tab available is the Toolbox tab. See Using the View Manager for information about tabs and the use of pins.
The toolbox contains the various controls that the user can use to modify a View.
Optional controls are not part of the OrionNET software plug-ins loaded at startup. Optional controls other than the
limits monitor may be included in future releases of OrionNET. All optional controls require user authorization prior
to their appearance in the View Designer toolbar.
Undo or redo the adding/deleting of controls or the moving/resizing of controls in the View Designer: Click Edit >
Undo or Edit > Redo from the menu bar OR press Ctrl Z or Ctrl Y.
1. Click once on the desired control. This places the control on the designer form in the default location
2. To reposition a control, select and drag the control
3. To resize a control, drag the handles surrounding a control
4. To delete a control, click the control and tap the Delete key
5. To copy and paste a control, click the control; then select, from the menu bar, Edit > Copy or Edit > Paste. To copy
and paste, the user may also use the typical Windows™- based functionalities Ctrl-C (copy) and Ctrl-V (paste).
6. Multiple controls may be copied/pasted/deleted/resized/repositioned simultaneously
1. To select multiple controls simultaneously, click one control; hold down the Ctrl key; while clicking other controls.
OR
Select Edit > Select All from the menu bar.
2. To de-select one of multiple selected controls, click on a selected control while pressing the Ctrl key
3. To de-select all controls, click any unfilled/empty area of the View Designer display screen, or press Esc
1. To place and align View Designer controls using the built-in grid, select Options > Show Grid, Snap to Grid, or Grid
Interval from the menu bar. Click (to check/uncheck) these options to turn them on/off.
2. To align multiple controls, select Layout > Align from the menu bar
3. To make multiple controls the same size, select Layout > Make Same Size from the menu bar
4. To alter the order in which controls appear (front to back), select a control; then select Layout > Order from the menu
bar
The View Designer notifies the user if any control is hidden behind another, so that the user may delete the hidden
control, if desired. This helps to prevent unnecessary use of resources while running OrionNET.
To save Views
1. Save changes to the current, operative View by clicking, from the View Designer menu bar, File > Save View
2. Save the current View’s changes as a new view by clicking, from the View Designer menu bar, File > Save View As...
Chart controls are powerful and flexible. A single chart control can support multiple chart configurations and can display
multiple channels on one or more rows.
As mentioned previously, the user may add controls to a selected view only by way of the View Designer. The user may,
however, edit the various controls associated with a selected view either within the View Designer or the Viewer.
This section describes the procedure for configuring controls that are already in place, whether in the View Designer or in
the Viewer.
If the control type allows it to be associated with channels (which is not the case with labels, images, and limits monitors),
the user may select a channel using the procedure described here.
See Orion V and OrionNET Hardware Outputs for information concerning Orion output states controls.
To change the foreground color of a control name, right-click the control, and click Select Forecolor.
3. Within the dialog, select desired Units and Precision from the associated dropdown boxes
4. Enter Scales Low and High (in bbl/minute)
5. Within Alarms and Warnings, click (to check) associated checkboxes and enter Local and Global Alarms and
Warnings
The OrionNET Viewer on the “master” computer, or the PC that is running the OrionNET acquisition component,
has the ability to set global alarms/warnings that are seen by all OrionNET Viewers (local and remote). Global
alarms and warnings are monitored by all remote Viewers.
The OrionNET Viewer can also set Local alarms/warnings, which are only visible to the local PC; not visible to any
other Viewer. Local alarms are not recorded in the alarm log. Only global alarms are recorded in this log.
This capability is available only for Orion V or Orion IV channels (sensors) that have no diagnostic errors active/
displayed. For additional Orion V diagnostic information, see Using Diagnostic Views.
2. Select Set…
3. A Channel Name dialog appears
The optional Limits Monitor control combines real-time data with the calculations of Cerberus’ Hercules Tubing Limits
application to assist the user in determining coiled tubing burst and collapse limits. The control may be placed in any View
(see Placing Controls in the View Designer). The following must be in place for the Limits Monitor to function:
1. Required channel types are set up in OrionNET’s Configuration Utility (see Configuring Channel Properties)
a. Required channel types are CT Depth, Wellhead Pressure, Circulating Pressure, and Weight
When all the prerequisites are in place, the user may set up the limits monitor to best view the data needed for the
operation.
2. Input parameters as needed. Click (to check) the desired collapse model(s) to display
3. Click OK
4. The limits model appears in the Viewer with data displayed as defined
Data is represented as the relationship between the Axial Force (lbs) and the Differential Pressure [Pi - Po] (psi).
To avoid yielding the coiled tubing, field job operating parameters must be controlled such that the red (Below Stripper)
and green (Above Stripper) dots appear inside the Limit (yield) Curve.
To avoid coiled tubing collapse, field job operating parameters must be controlled such that the red and green dots appear
above the Collapse curve(s).
After adding and positioning a 3D Well Survey [control] diagram using the View Designer, a job must be set in the
Viewer in order to display coiled tubing depth details.
Coiled tubing depth details may only be displayed when a depth channel is available within the [set] job.
To set a job
1. From the Viewer menu-bar, select Orion > Monitors > Set Job
Use the survey buttons in the bottom portion of the diagram to pan, move and zoom the survey plotting area.
To undo zoom
After adding and positioning a Well Diagram control using the View Designer, a job must be set in the Viewer to display the
well-profile and coiled tubing depth details. See To set a job for additional information concerning setting a job in the
Viewer.
Coiled tubing depth details may only be displayed when a depth channel is available within the [set] job.
When the job is set, and it contains a depth channel, the Well Diagram control (Well Profile) appears similarly to the
following. The software plots the current coiled tubing depth and renders it in red.
If the job contains no coiled tubing depth channel, the Well Diagram control graphically reflects this lack of coiled tubing.
The horizontal charts supported by OrionNET plot channel data from left to right.
Chart set-up options within the View Designer differ somewhat from the set-up options within the Viewer.
Using Chart Properties is perhaps the least intuitive of all the chart menu items. It refers to the way channels are
displayed within a chart.
If the chart contains more than one row, the Chart Properties dialog appears in accordance with the row clicked.
Change any of the available parameters and click OK to finalize the changes.
Click (to check) the Show Elapsed Time on Chart option to enable the appearance of a timeline above the Viewer
chart. This timeline shows how much time has elapsed since job inception.
3. Change any of the available parameters and click OK to finalize the changes.
OR
Click the desired channel name to the left of the chart.
4. The Chart Properties dialog for the selected channel-name appears
5. Change any of the available parameters and click OK to finalize the changes
The Chart Scale is chart-specific and is independent of the Low or High Scales found in the Viewer’s Channel
Property dialog.
Acknowledging Alarms
When the user has set up alarm and warning criteria in relation to channels included within the OrionNET Viewer, the
alarm(s) may be acknowledged. (See To edit or review channel properties to set alarms/warnings.)
To acknowledge an alarm
Alarm sounds are discontinued when the alarm is acknowledged, even when the alarm condition persists.
Diagnostic views and functions within OrionNET assist the user and NOV CTES with the troubleshooting of problems
encountered in acquisition from four types of data source: Orion V, Orion IV, ASCII via Serial, and Derived Channels.
(For information about configuring the Acquisition component, see Acquisition-component Configurations.)
Within the Viewer, the Show Diagnostics button (control) appears continuously in the lower left-hand corner of the display
screen:
The Show Diagnostics button flashes red when any channel whose data is being acquired has an error code. The button
flashes yellow for non-critical acquisition issues.
EMU not recording data causes the diagnostics button to flash yellow. All other conditions cause the diagnostics
button to flash red.
2. Internal temperature of the unit exceeding safe limits – both positive and negative
3. Voltages exceeding maximum/minimum limits for 5v, 12v, and 24v power sources
4. Analog sensors not working and therefore showing out of range values
5. Blown fuses or open circuits
6. Serial data not meeting criteria of the parameters that were set for the stream. For example, invalid baud rate, incorrect
delimiters or end of stream markers, and so forth.
7. Hardware connection issues
EMU not recording data causes the diagnostics button to flash yellow. All other conditions cause the diagnostics
button to flash red.
2. Analog sensors not working and therefore showing out of range values
3. Serial data not meeting criteria of the parameters that were set for the stream. For example, invalid baud rate, incorrect
delimiters or end of stream markers, and so forth.
4. Hardware connection issues
The diagnostics display for the Orion V or the Orion IV data source appears somewhat differently than those previously
described (ASCII via Serial or Derived Channels), though the same procedure is followed for its becoming visible.
The circuit board displayed on the left of the diagnostics display contains 7 slots where modules/sensors can be connected.
The diagnostics module (present in slot 0) may be considered the DAS’s “brains” for diagnostic functions.
The status of the Emergency Stop System (Supported/Not Supported) is displayed, as well as the state of the EMU on the
Orion DAS, and the Orion Strategy version.
When a module contains a channel that has an error code displayed (for example, an Orion channel that is Out of range), it
is rendered with an exclamation icon, indicating potential trouble on the module.
1. Click the error icon (exclamation point) to reveal the channel containing an error. Also, if any channels are “bound” to
the errored channel, a link becomes available describing Bound Channels.
Not all fuses are monitored by the OrionNET diagnostic tools. Only four fuses can be monitored on any instrumentation.
The default configuration is for the monitoring of three analog fuses and one encoder fuse. The three analog fuses typically
monitored are Wellhead Pressure, Circulating Pressure, and Pipe Heavy or Pipe Weight (depending on truck
configuration).
Serial-port diagnostics available on the Orion V provide technicians and operators with timesaving RS232 and RS485
debugging tools.
• Real-time view of serial port settings, such as IO mode, BAUD rate, delimiter, and stream separator (EOL
characters)
• List of channel names and stream positions associated with the port
• Real-time port test functionality to view the port’s raw serial stream
Figure 118 - Orion V Serial Diagnostics View with Test Serial Stream Displayed
The serial port test function provides real-time serial stream debugging functionality.
Use the serial port test function tool as described below to determine if the input port’s BAUD rate (Bits per Second)
matches the output device’s setting:
1. Select the serial module and port of interest from the diagnostics screen
2. Select the Text button; wait 1-10 seconds
3. Verify that the data displayed in the text box (below the Test button) appears as understandable information, such as that
shown in the image Orion V Serial Diagnostics View with Test Serial Stream Displayed. If the data appears as various
unintelligible characters or as a series of question marks (?), similar to that shown in the image Orion V Serial
Diagnostics Displaying Unintelligible Test Serial Stream (Incorrect BAUD Rate – Note the ???????? in the Test Text
Box), then change the port’s BAUD rate to match the output device’s settings (this may require several iterations if the
required settings are not known).
If the output device’s BAUD rate is significantly slower than that of the port (such as 115,200 vs. 2,400), then the
test function may not display characters. Try reducing the port’s BAUD rate to receive actionable information.
4. When the BAUD rate is correct, the Test port function can provide the operator with indicators for critical information,
such as the output device’s stream type (ASCII or WITS), separator and delimiter (typically appear as [CR] and/or
[LF]).
For instance, in the image Orion V Serial Diagnostics View with Test Serial Stream Displayed, the test data clearly
shows that comma is used as the stream separator with ASCII-type formatting.
5. If all of the port settings are known to be correct, but the channels associated with the port are “Unable to read” or static,
then the Test button can help verify if the Orion’s port is (or is not) receiving data from the output device. Typically,
this is an issue with cabling that can be corrected by ensuring the cables are connected and the output device and Orion
port wiring are compatible.
OrionNET displays the Hardware Error message any time a sensor error occurs. For additional sensor and channel error
information, check the OrionNET Diagnostics display.
Out of Range error occurs if a 4-20mA sensor’s output signal is beyond expected operating ranges (greater than 20.5mA
or less than 3.7mA). If fuse diagnostic monitoring is not available for the sensor, then this is a general Analog channel
error.
1. Verify there are no fuse blown indicators lit in the enclosure: If fuse blown indicators are on then replace them as
described in “Locating Blown/Overloaded Fuses” in the Orion V User Guide
2. Swap the channel’s associated sensor with a known good sensor. Replace if necessary.
3. Ensure loop resistance is less than the maximum value specified by the sensor manufacturer (typically 800 ohm)
Unable to Read error presents when communications are interrupted between the OrionNET PC and the Orion electronics
enclosure.
1. Check that the Orion enclosure’s power switch is ON and the Power indicator lights are ON. If not, go to “Orion Does
Not Power ON / Power Indicator Lights (up to 3) in Orion Enclosure Window are Not Lit” in the Orion V User Guide.
2. Verify that communications LEDs on the Orion enclosure are lit. If not, then ensure that the Ethernet cables are not
damaged between the Orion enclosure and the computer or ROVer and connections are firmly seated.
3. If network equipment is present between the Orion and PC, then verify the power is on for these devices. Also verify that
the Orion and PC are on the same LAN connection (i.e. a router is not interposed between the two devices.)
1. Open Circuit error indicates the sensor and/or cable(s) associated with the channel is disconnected or damaged, causing
the electronic diagnostic test to register as no load/open circuit
2. Verify there are no fuse blown indicators lit in the enclosure: If fuse blown indicators are on then replace them as
described in “Locating Blown/Overloaded Fuses” in the Orion V User Guide
3. Verify the sensor cables are connected to the appropriate receptacle on the Orion enclosure
4. Verify the sensor is functioning as expected
Typically, Short Circuit errors occur when the associated cable is damaged or wires are terminated improperly to the
sensor.
1. Visually inspect the cable associated with the channel for damage such as cuts or crush spots; this is frequent with depth-
encoder cables
2. Repair any electrical shorts as necessary and replace spent fuses
Fuse Blown errors occur in the OrionNET and ROVer when a sensor’s perceived power use exceeds that set by the inline
fuse between voltage supply and ground.
Check sensor indicates a general malfunction for analog sensors. This occurs if a 4-20mA channel’s signal is less than
3.5mA and greater than 0.1mA.
1. Locate the sensor associated to the channel and swap with a known good sensor. Replace if necessary.
2. Verify loop resistance is not over the maximum specified by the sensor (typically 800 ohm). If so, determine if another
device is adding to the resistance and remove it from the current loop by adding a signal splitter.
Connection Errors Occur While Using the Orion with the PC and OrionNET
When OrionNET software is unable to read data from the Orion V or Orion IV Data Acquisition System, a disconnect
dialog becomes available. The dialog provides a series of steps to help the user re-establish OrionNET connection to the
hardware.
Chapter 6
System/Product Operation
This chapter describes the Reports capabilities of OrionNET.
3. Within the dialog, select the desired database for reporting purposes.
OR
In the OrionNET Viewer, select Reports > Launch OrionNET Reports from the menu bar. (See Using the Reports
Menu Option).
4. The OrionNET Reports display screen appears, loading the database that is currently recording data/displayed in the
Viewer.
1. From the OrionNET Reports display screen, select File > Open Database from the menu bar
2. The Open [database] dialog appears. Select any OrionNET database (this may be a file in
C:\ProgramData\CTES\OrionData\Datalogs or another file residing on the user’s hard drive).
3. Within the dialog, select a database
1. Open Database
a. Use the typical Windows dialog to open an OrionNET database
2. Save As
a. Save the current information as an OrionNET v2.5 database using a Windows dialog
3. Print
a. Select from among the available reports
The user may modify a database for successful import into Cerberus (for example, for use with Cerberus’ Reel-TrakTM or
OrpheusTM, since these programs use data based on channel types) by way of modifying the Channel Type associated
with an OrionNET channel. This functionality is only available (from the Horizontal Charts tab) for OrionNET databases.
1. Select File > Modify Channel Types from the OrionNET Reports menu bar.
2. Use the down-arrow next to any Channel Name to select another available channel name to associate with a Channel
Type and click OK
If two channels are associated with the same channel type, a red asterisk appears next to the channel type. The
first channel found [by the software] to be associated with the channel type is used [by the software] (when the
user clicks OK), and the remaining channels (associated with the same channel type) are changed to be of
channel type Other.
3. If duplicate channel-associations are found, the user is given an opportunity to Cancel after clicking OK
Merge Databases
The user may merge databases of similar kind into one database. This is used when one job has been recorded in several
separate databases because the acquisition unit was restarted during the job.
The purpose of this functionality is to merge databases from the same unit – not from two different units.
This functionality is only available for OrionNET databases (and not for Orion v8.0 databases).
1. Select File > Merge Databases from the OrionNET Reports menu bar
3. Select the ‘plus’ button to access the Datalogs file folder. Then, select a database to add to the to-be-merged
databases.
4. To remove a database from the to-be-merged databases, select the database for removal; then select the ‘minus’ button
The first database in the list of to-be-merged databases is used to create the structure for the merged data- base.
Use the 1st button to move a selected database to first position in the list.
5. Select the ellipsis button to determine the location to save the merged database, and the merged-database file
name.
6. Click the Merge button
7. The merged database is displayed in OrionNET Reports
Split Databases
OrionNET databases can become very large. This can cause difficulty when trying to send a database via email. The Split
Database function can be used to break a large database into smaller pieces that can be emailed individually. When the
split database files reach their destination, they can be merged back into an OrionNET database.
To split databases
1. Select File > Split Databases from the OrionNET Reports menu bar
2. From the Split Database tab (default), select a datalog (*.onet) to split using the associated ellipses
3. Select the Output Directory using the associated ellipses
4. Select the Max[imum] Size Per File (in megabytes)
5. Click the Split button
6. The split databases are displayed in OrionNET Reports
The user may merge databases that were previously split. The purpose for splitting databases is to allow small files to be
emailed. When the split files reach their destination, they may be merged as follows:
1. Select File > Merge Databases from the OrionNET Reports menu bar
2. Select Split Files
3. From the Merge Database tab (default), select the first file (*.001) from the group of split files to merge using the
associated ellipses
4. Select the Output Directory using the associated ellipses
5. Click the Merge button
6. The merged database is displayed in OrionNET Reports
1. Select File > Import EMU Data from the menu bar
3. If desired, limit the range of IP addresses through which the reports software searches for available data acquisition
systems/EMUs
4. To limit the range of IP addresses:
5. Click the Settings button to reveal the Preferences dialog. The Preferences dialog is also available from the Setup Menu
Option.
The available controllers are shown in the dialog. Click the “+” associated with a controller to see the EMU files
associated with it.
11. Click (to check) a controller ID to automatically select all EMU files located there
OR
Click (to check) individual EMU files
12. Click (to check) Remove files after downloading or Convert files after downloading as desired. See To convert an
EMU file to an OrionNET database for more information about converting EMU files to OrionNET databases.
13. Click the Download Files button
When downloading Orion V-specific EMU files, the Orion DAS controller activity is suspended until the download is
complete.
1. From the Import & Convert EMU Files dialog, select the Convert EMU Files tab
2. Select the EMU data file to convert: Click the ellipses to access a Windows Explorer interface to browse among
available files
3. Select a database to place the converted EMU data file: Click the ellipses to access a Windows Explorer interface to
browse potential locations and input a file name
4. Click the Convert button to proceed with the conversion
Company Info
Input the Company Name and click the image to change the existing logo.
EMU Locator
Security
Secure advanced options in Reports by enabling a password via the Preferences Security tab. Options protected by this
password include the Comments Editor, Custom Fields Editor, and Reports Designer.
Display
Change Language
2. Click (to select) the language of choice from those available and click OK. The language-change takes effect when the
software is re-started.
Comments Editor
The comment pairs set up in the Comments Editor in the Viewer are used when creating or editing a report in the Report
Designer. When the Automatic Range Mode is selected in the Report Designer, the report is set up to print the range of
data (between the start and end points) of selected comment pairs. This data range derived from comment pairs may be
used when printing a Chart, Comment Log, or Job Log.
Use the Custom Fields Editor to specify the displayed fields in the Job Information dialog in both the Viewer and in
Reports.
There are some Custom Field labels that are not edited and cannot be deleted by the user: Job Name, Client
Company, Client Contact, Well, Unique Well ID, Job Type.
• To access Job Information in the Viewer, select File > Job Information
• To access Job Information in Reports, click the Job Info button under the Data tab
1. Select Setup > Custom Fields from the Reports menu bar. The Custom Fields Editor appears.
Import/Export
Use Custom Fields from other computers on the local computer, or use Custom Fields from the local computer on other
computers by way of a Windows Explorer interface.
1. Click and hold on an item in the list and then drag and drop to its desired location
Parent Field – Determines whether another field’s value is required in order for this field to be enabled.
Report Designer
The Report Designer provides capabilities for creating custom reports (see Working with the Page Designer), for editing
existing reports, and for editing the range of data to print (after a report is selected to print).
The reports designed in the Report Designer are selectable as buttons in the Reports tab of the Reports Manager. See
Using the Reports Buttons in Reports Manager.
To specify settings
The Range Mode is not saved with the report. When printing a report, select a Reports report-name button (see
Understanding the Reports Manager and the Work Area) before opening the Report Designer and selecting the
Range Mode described here.
3. Select the Range Margin from the dropdown (only applies to Automatic Range Mode reports).
Determines the amount of time to be added on each side of the data timeline when printing an Automatic report.
In the Pages section, click (to check) each page desired for inclusion in a report.
To edit a page
To delete a page
Authorization
To change authorization
1. OrionNET Updates
a. Check for updates
i. Runs a software service to check for updates to OrionNET software
b. Update Settings
i. Allows user to enable automatic updates and how often the system checks for updates
ii. Allows user to roll-back OrionNET back to an earlier version that was working in case of update failure
iii. Allows option for testing of the AutoUpdater to diagnose user problems with updates
About
The OrionNET version number and product support/sales information is found here.
The Page Designer is comprised of a menu bar, a Toolbox tab in the Reports Manager area (see Understanding the
Reports Manager and the Work Area for information about the Reports Manager), and a graphical representation of the
page design on the right-hand side, called the Design Area.
Create a new page, save a page, save a page as an XML file, or exit the application.
Edit
Cut, copy, paste, delete, or select all editable controls in the Design area. The undo/redo functionality allows recovery
from inadvertent design changes.
Options
Display a grid, snap/unsnap controls to/from the grid, set the grid’s display interval, or copy headers from other pages.
Layout
Align controls, make controls the same size, or center controls in the form.
Page Name
Page Type
The Page Type determines the type of page that is created/edited, the data that is printed, and the controls that are
displayed. The following page types are available:
Custom Page
Its toolbox contains custom and system fields (distinguishable by the “%” signs surrounding the field name). The page
body is editable, but the footer is static.
Label:
Line:
Box:
Chart
The Chart page-type includes controls; custom and system fields; an editable header; an un-editable body (because it is an
example, static image); and a static footer.
Figure 148
Comments
The Comments page-type includes controls; custom and system fields; Automatic Range comment-pair selection (see
Comments Editor); an editable header; an un-editable body (because it is an example, static image); and a static footer.
Create a Treatment Comments Page from the Comments page-type to mimic handwritten job reports.
Job Log
The Job Log page-type includes controls; custom and system fields; Automatic Range comment- pair selection (see
Comments Editor); column selection (by available channel); an editable header; and a static footer.
Alarms
The Alarms page-type includes controls; custom and system fields; column selection (by available channel); an editable
header; and a static footer.
Events
The Events page-type includes controls; custom and system fields; column selection (by available channel); an editable
header; and a static footer.
Orientation
The page Orientation provides a selection for the page to be displayed or printed in a portrait or landscape orientation.
Controls
Controls can be editable or originated by the system (not editable). System controls are distinguishable by the “%” signs
surrounding the control.
To use controls
Editable Controls
Custom/System fields are not editable here. Their text is replaced as the report is printed.
Custom Fields
Custom fields from the Job Information dialog are added to this list. When added to a page, their text contains {} symbols.
See Custom Fields Editor for more information about custom fields.
System Fields
• %CompanyName%: The company name that was set in the Preferences menu (see Preferences to set up
preferences)
• %PageNum%: The current page number
• %DBName%: The name of the current database
• %PreparedBy%: The name of the person running the report and the current date
• %JobLogStartDate%: The first date/time entry of the Job Log
• %JobLogEndDate%: The last date/time entry of the Job Log
Select Chart
Only available when the Page Type is set to Chart, this section lists all available local and database charts that the user
can select for printing.
Automatic Range
Automatic Range lists all available comment pairs that were set using the Comments Editor. This only applies when the
Range Mode of the report is set to Automatic. The report generates a page for each comment pair it finds depending on
the value selected in the dropdown.
Columns
This lists all available columns that can be displayed on a grid and is only applicable to Comments, Job Logs, Alarms, and
Events pages.
Page
1. Right-click a Job Log column header and select the appropriate option. This is only available for columns that allow data
precision.
Plug Summary
The Plug Summary page-type includes controls; custom and system fields; Automatic Range comment-pair selection (see
Comments Editor) column selection (by available channel); an editable header; and a static footer.
The tabs in the Reports Manager behave identically to the tabs in the View Manager (see To access and use tabs).
The Work Area is located to the right of the Reports Manager. The tabs in the Work Area behave similar to the tabs in
the View Manager, except they vary in content depending on the button selected in the Reports Manager.
For example, the image below shows the Charts button selected in the Reports Manager, and the Horizontal Charts tab
in the Work Area with the Charts and Channels tabs pinned.
In the below image, the Job Log button is selected in the Data tab of the Reports Manager, and the Job Log tab is
visible/pinned in the Reports Work Area.
In the image below, the Alarms button is selected in the Data tab of the Reports Manager, and the Alarm tab is displayed
in the Work Area.
When selected, the Alarm and Events buttons in the Report Manager display as tabs without additional Work
Area editing options.
Using the Reports Manager and Work Area to Affect the Display Area
The Reports Manager and Work Area work together to affect the Reports Display Area.
Click any Reports button to print a report as defined in the Report Designer. (See Report Designer for information.)
When a report button is selected, Page Thumbnails become available in the Work Area and the report becomes available
in the Display Area.
Maximize or minimize the Page Thumbnails by clicking the arrow associated with the Page Thumbnail icon.
Click any thumbnail to see its associated report page appear in the Display Area.
Use the toolbar in the Work Area to perform the following functions in relation to the report shown in the Display Area:
Save As: Causes the Save As Windows Explorer dialog to appear, from which the user may select a location for a PDF
report to be saved.
Print: Causes the Print dialog to appear, from which the user may select they type of print output, preferences, and so
forth common to Windows applications.
Previous Page or Next Page Arrows: Causes the report page in the Display Area to change according to the selection.
Page Number Entry: Causes the report page in the Display Area to change according to the input page number.
Pan: When this icon is selected, click-and-drag the mouse to move from page to page or sideways on a page.
Selection: When this icon is selected, click and drag the mouse over text to select it.
Zoom Out and Zoom In: Click these icons to zoom out and in on the Display Area.
2. The Horizontal Charts tab becomes available in the Work Area. Underneath the Horizontal Charts tab are displayed
the Charts and Channels tabs
3. Pin the Charts and Channels tabs to the Work Area (see To access and use tabs)
4. A horizontal chart becomes available in the Display Area (See Horizontal Chart)
The Charts tab, when pinned, allows a choice between displaying Local or Database charts in the Display Area. Click
(to toggle) either Default chart included with the software to view that chart.
Local charts are saved on the hard drive and may be a configuration that is used repeatedly by the creator only. Database
charts are more universal in nature and are saved differently than Local charts (though this is not transparent to the user).
1. Under the pinned Charts tab, click to select either a Local or Database chart
2. Right-click the Display Area. A chart menu appears
Save Chart As... Save the current chart with a new name
The settings contained within the Chart Properties menu control the way channels are displayed within a chart.
1. Under the pinned Charts tab, click to select either a Local or Database chart
2. Right-click the Display Area
3. Select Chart Properties. The Chart Properties dialog for the channel nearest to the chart appears.
4. Change any of the available parameters and click OK to finalize the changes
1. Under the pinned Charts tab, click to select either a Local or Database chart
OR
Right-click the Display Area
2. Click Select Chart; select the desired chart
1. Under the pinned Charts tab, click to select either a Local or Database chart
2. Right-click the Display Area
3. Click New Chart and input the chart name
The channels become visible in the Display Area and the new chart retains the channel selection without saving.
OR
Double-click anywhere on the chart grid
a. The Comment dialog appears
After completing one of the two methods of accessing the Comment dialog described above, continue the process as
follows:
1. Enter a comment or select a predefined comment from the associated dropdown. See Defining Predefined Comments for
information concerning predefined comments.
2. Click OK
EMU data can be imported into OrionNET Reports and the user can add, delete, and modify comments. How-
ever, the comments can only be edited, deleted, and so forth from the Comment Log in OrionNET Reports
(assuming EMU-imported data).
2. The Job Log tab becomes available in the Work Area. Underneath the Job Log tab is displayed the Options tab.
3. Pin the Options tab to the Work Area (see To access and use tabs)
A job log becomes available in the Display Area (See Job Log).
Selecting Channels
Select channel-data (click to check Channels) for inclusion in the Display Area (the default is all channels displayed in
the log).
1. Within either Start Date/Time or End Date/Time, click to select any portion of the date or time, and then click the up-
or-down arrows associated with the field
a. Instead of using the available up-or-down arrows, input the desired value after selecting any portion of the date or
time
2. Click the Reload Data button to correlate the data displayed in the Display Area job log with the selections for date or
time
3. Click the Reset button to return dates/time to the default
Using Comments
2. The Comments tab becomes available in the Work Area. Underneath the Comments tab is displayed the Options tab
3. Pin the Options tab to the Work Area (see To access and use tabs)
Add Comment
Edit Comment
Delete Comment
Renumber Comments
The Renumber Comments option renumbers all comments for which the auto-number property is enabled (See To
define a comment for the predefined comment list for information about setting a comment’s auto-numbering property).
1. Click the Renumber Comments button. The Auto # Comments dialog appears
Using Alarms
Using Events
Job information input in the Viewer is automatically displayed in Reports (See Job Information for additional
information).
To see job information that is revised in Reports in the Viewer, save the job information in Reports; then close and
reopen the Viewer.
Trim the data range by altering the timeframe reported for data within an existing OrionNET database.
The data range may be trimmed in relation to either a chart or a job log as selected in the Data tab.
Data range trimming may only occur through the saving of original database changes to a modified database; an original
database may not be altered.
2. Click Yes; then use the Save As... Windows Explorer dialog to save a database as “modified”
The new database name is comprised of the original database name, with an appended underscore character
followed by the word “Modified.”
4. Within either Starting Date/Time or Ending Date/Time, click to select any portion of the date or time, and then click
the up-or-down arrows associated with the field
5. Click OK to continue.
Another Trim Data Range dialog appears, warning the user that trimming the data range will delete data from the
modified database.
6. Click Yes to continue
7. A dialog appears with the modified database name in the tagline, asking whether the user would like to open the
modified OrionNET data file
8. Click Yes to continue.
The modified version of the database is displayed.
The Events Log also registers the modification of the database, showing the date and time of modification. See also Using
Events.
Using Modify
Modify data values or units for data within an existing OrionNET database.
The data values/units may be modified in relation to either a chart or a job log as selected in the Data tab.
Data value/unit modification may only occur through the saving of original database changes to a modified database; an
original database may not be altered.
2. Click Yes; then use the Save As... Windows Explorer dialog to save a database as “modified”
The new database name is comprised of the original database name, with an appended underscore character
followed by the word “Modified.”
4. Click (to toggle) either Apply changes to entire database range or Apply changes to specified range
5. If Apply changes to specified range was selected, click to select any portion of the date or time within either Starting
Date/Time or Ending Date/Time, and then click the up-or-down arrows associated with the field
6. Click within a Data Multiplier or Data Offset field that is associated with the Channel Source and Name for
modification
7. Input a positive or negative number into the field. Data Multipliers multiply the channel value by the number input;
Data Offsets add (or subtract) to/from the channel value according to the number input.
8. Click OK
To modify units
1. Within the Modify Data Values Dialog, select the Modify Units tab
2. Under System Units, select, from the dropdown, English Units, Metric Units, Canadian Metric Units, or User Defined
3. If User Defined is selected, use the dropdown associated with each field to individually select units
4. Any field within User Defined Units may be individually set as to unit type, but if any main type other than User
Defined is selected, then choosing an individual type other than that consistent with the main type results in changing the
main type to User Defined
5. Click OK
Using Filter
The data may be filtered in relation to either a chart or a job log as selected in the Data tab.
Data filtering may only occur through the saving of original database changes to a modified database; an original database
may not be altered.
To filter data
2. Click Yes; then use the Save As... Windows Explorer dialog to save a database as “modified”
a. The Filter Data dialog appears
3. Click (to toggle) the filtering of data By Time, By Data Rows, or By Channel Criteria
a. If filtering data By Time is selected, input the data increment, and use the dropdown to determine whether the
data is shown by Second(s) or by Minute(s)
b. If filtering data By Data Rows is selected, input a number that specifies how often data is shown. In other words,
data is shown every X rows.
c. If filtering By Channel Criteria, click (to check) a channel or channels by which to filter data. When a channel is
selected, a field becomes available where the user can input a number (corresponding to the unit type) indicating
that the filtered data will be saved only if that number is exceeded.
4. Click OK
Using Export
The data may be exported in relation to alarms, events, or job information as selected in the Data tab.
Data export may only occur through the saving of original database changes to a modified database; an original database
may not be altered.
To export data
2. Click Yes; then use the Save As... Windows Explorer dialog to save a database as “modified”
a. A popup appears indicating that data is being exported to CSV
3. When the data is exported, a dialog appears asking if the user would like to open the exported data file
4. Select Yes or No. If Yes is selected, a spreadsheet opens, in which the data is visible.
Using Copy
The data may be copied in relation to a job log, comments, alarms, or events as selected in the Data tab.
To copy data
3. Click OK
4. Paste the data into the destination of choice using Ctrl-V
Copy and Export functions copy/export any data selected in the currently viewed grid. In other words, if 10 rows
are selected, then only those 10 rows are copied/exported. If no data is selected, then the entire grid is
copied/exported.
Appendix A
Configuring the Local Network for Communication with CTES Hardware
If an “Invalid Network Settings” message is received, complete the process described here.
To ensure that the controller and OrionNET software are communicating properly, complete the following:
1. Obtain and record the Orion IP address from the label inside the door of the Orion box (for Orion IV) or from the outside
front panel of the box (for Orion V). If the address is not available for any reason, contact NOV CTES.
2. After obtaining the controller IP Address, set up the Ethernet for OrionNET:
a. Open the OrionNET configuration utility (see To launch the Configuration utility)
b. Select Setup > Settings from the menu bar. The OrionNET Settings dialog appears.
3. Click the Open Network Connections link in the bottom left-hand side of the dialog
4. Right-click Local Area Connection; click Properties
5. Select Internet Protocol (TCP/IP); click Properties
6. Toggle the radio button Use the following IP address:
7. Enter the IP Address recorded earlier; change the third number to “1” (the IP Address should be 192.168.1.n, where n is a
number from 1 to 254 and should be unique on the network)
8. Set the Subnet mask value to 255.255.0.0; click OK
Appendix B
Calculating Derived Channels with Equations
The use of equations is one method for calculating a derived channel. Basic use of equations for this purpose is described
in Using Equations. Supported functions not described there are included here.
Property Notes
abs(expression) Returns absolute value of expression
acos(expression) Returns the angle whose cosine is specified by expression.
asin(expression) Returns the angle whose sine is specified by expression.
atan2(expression y, expression x) Returns the angle whose tangent is the quotient expression y /
expression x.
max(expression 1,…, expression n) Returns the maximum value in the expression list.
min(expression 1,…, expression n) Returns the minimum value in the expression list.
pi Returns the value of Pi to 8 decimal places.
rand(expression min, expression max) Returns a random number between
<expression min> and <expression max>.
Appendix C
Using the Panel PC for Orion V Pumpers
The Orion V Data Acquisition System (DAS) for Pumping from NOV CTES is equipped with a dedicated panel PC that
has a bright screen and enhanced touch-screen operation. This panel PC is provided specifically for the purpose of using
the OrionNET data acquisition software in conjunction with the NOV CTES Orion V DAS; no other application or
functionality is available through the PC.
The touch-screen-capable version of the OrionNET Viewer interface is somewhat modified from the usual OrionNET
software interface, though the functionality is similar. Most, though not all, of the full-version OrionNET capabilities are
available.
As of the publication date of this guide, the following functionalities are not available when using the panel PC:
• Force or Fatigue data monitors, since Cerberus modeling software is not yet available through the panel PC (See
Monitors for information about these)
• The usual OrionNET Reports functionality, though a Job Report may be sent via email to various designated
recipients if an Internet connection is available (see Acknowledging Alarms for additional information)
Only the current open and recording data file may be sent via email.
• Data acquisition restart from the display. The user must shut down and restart the PC for changes to take effect
when a change is made to the configuration.
If the appearance or screen organization of the Viewer requires modification, use the touch- screen techniques (see Using
the Touch Screen) to complete these changes. See Setting Up and Using the OrionNET Viewer for more general
information about setting up the OrionNET Viewer.
The basic techniques for using the PC-panel touch screen are provided here.
1. Expand (stretch outwardly) or contract (draw together) two fingertips (or a fingertip and a thumb) within a control (see
Working with the View Designer for information about controls). This activity results in different behavior depending on
the control:
a. For a channel control containing digits, expand the fingertips (spread fingertips apart) to increase the precision
(number of decimal points) within that control. Contract the fingertips (bring fingertips together) to decrease the
precision.
b. For a horizontal-chart control, expand the fingertips horizontally to zoom in focus, spreading the data points
further apart. Conversely, contract the fingertips to zoom out the area of focus, bringing the data points closer
together.
c. For channel controls to the left of horizontal charts, expand the fingertips vertically to spread the data points
further apart (zoom in), and contract the fingertips vertically to bring the data points closer together (zoom out)
2. Within a horizontal chart [control], flick (scroll quickly side-to-side) to change the time-period displayed
3. Press and hold one finger down to right-click
4. Drag controls or other items (like the keypad) around the screen using a fingertip as a mouse
5. To input data, touch the field into which data is to be entered. When a small keyboard icon appears, touch it to bring up a
full-scale keypad.
6. The $123 keypad button in the lower left-hand corner toggles the keypad between alpha and numeric characters
7. Touch the keypad icon in the lower right-hand corner [of the keypad] to configure the appearance of the keypad or to
remove the keypad from view (exit the keypad)
The user may also touch the “X” in the upper right-hand corner of the keypad to exit, or may touch the
minimize/maximize button (next to the “X” button) to make the key- pad smaller or larger.
The PC-panel touch screen includes the following functionalities underneath the main menu bar titles:
1. File:
2. New database (Start new job)... (See New Database (Start New Job))
a. Rename database... (See Rename Database)
b. Open database... (See Open Database)
c. Job information... (See Job Information)
3. Orion:
4. Connection... (see Connection)
a. Channels... (see Channels)
b. Calibrate... (see Calibrate)
5. Setup
a. Configure (By selecting a configuration, the user “tells” the acquisition server/component the type of hardware it
will “talk to.” See Using the Configuration Utility for additional information.)
6. Preferences... (see Preferences)
7. Help
a. OrionNET User Guide
b. OrionNET Quick Start
c. About
Appendix D
Orion V and OrionNET Hardware Outputs
This appendix describes the OrionNET setup of Orion V output configuration properties, as well as the setup and use of
the OrionNET output-states control (see Working with the View Designer for information about controls) for the
automatic threshold-based control of audible and visible alarms and equipment shutdown triggers.
Each output has several parameters that may be modified using the OrionNET Configuration Utility.
1. Click Setup > Configure from the menu bar of the main OrionNET dialog
2. Click to select the Orion V data source name (typically “Data Engine 1”)
3. Click the Configure hardware outputs... button. The configuration parameters appear.
4. Click (to check) Enable Output 1 to control the nth relay in the Orion system. The applicable properties become
available.
1. Select the channel name from the dropdown related to Turn on output when Channel Name
To automatically set the output when the monitored parameter value is greater than X
1. Click (to check) is greater than and input the variable in the related field
To automatically set the output when the monitored parameter value is less than X
1. Click (to check) is less than and input the variable in the related field
To allow operators to modify the set threshold from the OrionNET Viewer dialog using the Orion V Output
States control
Users cannot reset an output whose target channel-value is still in the enable range.
2. [Appearing only on the last output] After clicking (to check) the last listed output to enable it, click (to check) Output is
a hardware alarm. When checked, this output sets and resets based on a logical AND operation on all configured
outputs. In other words, if any other output is set, then this output automatically sets.
After making modifications to output parameters, the following operations MUST be performed for the
modifications to take effect on the Orion hardware.
3. Select File > Save from the menu bar (or select the Save toolbar icon) to save the configuration to the computer
4. Save the configuration to the controller: From DataSourceName Properties, click the Save configuration to
controller button
5. See To configure CTES Orion V data source properties for more information
6. Restart Orion hardware and OrionNET (use the dashboard power switch for embedded PCs)
The Output states control provides a tool for the unit operator to view output states, to reset outputs, and to modify
output thresholds. (See Working with the View Designer for information about controls.)
Within the OrionNET View Designer, click the Orion V Output Status toolbar icon to place the control on the View.
In the above image, Lube Oil Pressure and <Alarm> are set outputs; Discharge Pressure and Lube Oil Temp are clear.
To reset outputs (see To set Output Type: for information about who may reset outputs)
3. To close the status popup, click any blank space on the Output states panel
This requires the configuration to allow the user setting the thresholds. (see To allow operators to modify the set threshold
from the OrionNET Viewer dialog using the Orion V Output States control)
Appendix E
Setting Up Orion Hardware to Read Serial Data
This appendix describes the process of setting up Orion hardware to read external serial data. This process applies to both
Orion IV and Orion V Data Acquisition Systems.
1. Set up hardware port(s) (see Setting up Hardware Ports to Read External Data via Serial)
2. Add channels to the configuration to designate serial ports as inputs
3. Save the settings to the controller
Each serial module installed in the Orion hardware contains 2 serial ports. The CTES hardware programming
limits the number of serial ports that can be used to 8.
When using a serial port as an input, ASCII is the only type that works. The input mode currently cannot read
WITS Level 0 data.
When using a serial port for ASCII output, ALL channels defined in the controller are transmitted.
When using a serial port for WITS Level 0 output, only channels stored in the controller with a WITS ID that is
greater than 0 are transmitted.
The delimiter and separator settings do not apply when using the serial port for output with WITS Level 0 selected
as the Output type.
1. Add a channel to the configuration (see Adding/Editing Channels for additional information)
2. Select External from the dropdown as the Sensor type
3. In the Position field, enter the value found in the data stream that is the value for this channel
4. In the from input field, enter the serial port from which the value above is read
5. The user may select System units and enter Scale low/Scale high information
6. Repeat the above five steps for all channels to be read via serial input
After completing the serial-port settings and any input channels have been added, click the Save configuration to
controller button on the [data source] Properties dialog.
Appendix F
Orion V Fastest Wheel Algorithm Feature
This appendix describes an optional feature for Orion V systems called the Fastest Wheel Algorithm (FWA). When this
feature is authorized, users can create a depth channel that applies an algorithm to detect pipe slip and minimize its effect
on depth measurement.
Overview
The FWA feature continuously compares two to four quadrature depth encoder inputs already being measured by the
Orion hardware to determine if one of the inputs is moving significantly faster than the others. The measurement from the
fastest input is then added to the depth maintained by the FWA function.
To use this feature, a channel of sensor type ‘CTES FWA’ must be added to an Orion system that has at least two
quadrature depth encoder inputs.
Access to this feature is controlled by the OrionNET software authorization. If an Orion system is not authorized for the
FWA feature, any CTES FWA channels created will not function.
For the FWA feature to return reliable results, the quadrature sensors used as its inputs must be mounted in close
proximity to each other. This helps to eliminate movement from slack pipe and/or pipe stretch from the
measurements. Having two quadrature depth encoders mounted at the reel or two quadrature encoders mounted
on the injector is acceptable since the distances between encoders will be small. Having an encoder mounted at
the reel, and on the injector, is not acceptable because the distance between encoders is large and one encoder
can be turning while the other is not.
3. Right-click the Channels item under the data source and select Add Channel
4. Enter a channel name and click OK
5. Select the appropriate system units
6. Select CTES FWA as the sensor type
7. Select the quadrature depth encoder inputs to be used as the source for the channel
The order of the quadrature selections is important to the calculation process. The algorithm is designed to use the
first selection as its primary result unless the next input is moving significantly faster.
1. Open the OrionNET Configuration Utility and select the appropriate configuration
2. From the Orion V data source properties panel, click the Get configuration from controller button
3. Right-click the Channels item under the data source and select Add Channel
4. Enter a channel name and click OK
5. Select the appropriate system units
6. Select CTES FWA Rate as the sensor type
7. Select CTES FWA channel to use as the channel from which to calculate rate
Appendix G
Setting Up OrionNET Cloud Data Communication
This appendix describes the process of setting up Orion hardware to read external serial data. This process applies to both
Orion IV and Orion V Data Acquisition Systems.
1. Provide CTES (CTESSupport@nov.com) with Coil Tubing Unit number and associated Orion serial number that will be
conducting the job. This information will be used to provide a unique identifier for the data on the Internet.
2. Provide a connection from the OrionNET computer to the Internet
1. Obtain authorization key that includes internet mode setup by CTES Keys
2. If taking data in from a non-CTES third party, have the third-party hardware option turned on in the key by CTES Keys
3. In the Job Info table, Pre-job testing should use “Test” for the Well Name and “Test” for the Unique Well ID so that
testing data will be distinguishable from the actual Job data
4. In the configuration that will be used, turn on the Enable OrionNET LDT (Live Data Transfer)
5. The OrionNET LDT option will cause several fields in the OrionNET Viewer Job Info to become required fields. After
starting each new job, the user must enter the fields marked an asterisk (*) beside it. The Unique Well ID should be
obtained from the well operating company prior to the job:
6. After you click OK you must select the name of your unit assigned prior to the job and whether you are sharing your
data with the operating company or not, if simply testing equipment, software settings and internet connectivity: