Amphion Level 0

STUDENT HANDBOOK
04-Amphion Disc Level 0
Document number 96747643

Revision 4
PP revision
Document number 96747643 Page 2 of 292
Revision 4
Table of Contents
Introduction to Amphion and Single Board Computers ................................................................ 6

Introductions and Expectations.......................................................................................... 7
Lesson Objectives ............................................................................................................. 8
Safety Precautions ............................................................................................................ 9
Working Safely ...................................................................................................... 10
NOV Control System History ........................................................................................... 12
Automation / Relay Logic ...................................................................................... 13
PLC ....................................................................................................................... 16
EDS ...................................................................................................................... 17
VICIS .................................................................................................................... 19
SCADA ................................................................................................................. 21
Cyberbase............................................................................................................. 23
Amphion System Overview.............................................................................................. 27
Amphion Concept ................................................................................................. 28
Single Board Computer ................................................................................................... 30
Concept................................................................................................................. 31
Use Cases ............................................................................................................ 32
Hardware Types.................................................................................................... 33
Hardware Brick ......................................................................................... 33
Hardware Rack......................................................................................... 37
Hardware Beckhoff ................................................................................... 40
MTC Cabinet ......................................................................................................... 42
Switching on.......................................................................................................... 44
Terminology and Abbreviations ....................................................................................... 45
System Level ........................................................................................................ 46
Debug Level .......................................................................................................... 49
Lesson Review ................................................................................................................ 54
Documentation ........................................................................................................................... 57
Lesson Objectives ........................................................................................................... 58
NOV Resources............................................................................................................... 59
Software Products Server ..................................................................................... 60
Documentation Portal ........................................................................................... 61
Amphion Software Network................................................................................... 62
Old Wiki* ............................................................................................................... 64
New Wiki ............................................................................................................... 65
Drawing / Manuals ........................................................................................................... 66
Teamcenter ........................................................................................................... 67
Rig Doc / Rig Office .............................................................................................. 77
Revision 4
Drawings / Manuals .............................................................................................. 93

Lesson Review .............................................................................................................. 103
PC Requirements ..................................................................................................................... 105
Lesson Objectives ......................................................................................................... 106
Administrator Rights ............................................................................................ 108
Java .................................................................................................................... 109
Java Versions ..................................................................................................... 111
Java Settings ...................................................................................................... 115
Browser ......................................................................................................................... 116
Browser Settings ................................................................................................. 118
IP Connection ................................................................................................................ 119
Firewall .......................................................................................................................... 121
Lesson Review .............................................................................................................. 124
Compact Flash Structure, Creation, and Backup ..................................................................... 126
Amphion Software Components .................................................................................... 128
Amphion Software Components ......................................................................... 129
Golden Image ..................................................................................................... 129
Platform............................................................................................................... 130
Base Layout ........................................................................................................ 131
Controller ............................................................................................................ 132
WWW .................................................................................................................. 133
Varball ................................................................................................................. 134
NOV Software Product Server ....................................................................................... 135
Firmware ............................................................................................................. 139
Applications......................................................................................................... 149
Creating a Compact Flash ............................................................................................. 155
Compact Flash Image ......................................................................................... 156
Win2Flash V2.0................................................................................................... 156
Ghost 3FIP00286 ................................................................................................ 158
R-Linux ............................................................................................................... 159
SelfImage ............................................................................................................ 160
Testing Compact Flash in SBC...................................................................................... 161
Safety .................................................................................................................. 162
Do’s and Don'ts ................................................................................................... 164
Lesson Review .............................................................................................................. 167
SBC / Tool Controller Service Pages ....................................................................................... 170
Main Page ..................................................................................................................... 172
White Main Page................................................................................................. 173
Flares Main Page ................................................................................................ 175
IP Network ..................................................................................................................... 179
Revision 4
Devices and Navigation ...................................................................................... 180

Edit Address List ................................................................................................. 181
Show IP Address ................................................................................................ 182
Investigate Address ............................................................................................ 183
Software Management .................................................................................................. 186
Restricted Functions ........................................................................................... 187
Software Versions ............................................................................................... 188
Backup and Restore ........................................................................................... 189
Software Installer ................................................................................................ 196
Transfer Files ...................................................................................................... 198
Software Manager............................................................................................... 205
Diagnostics .................................................................................................................... 210
Debug Monitor .................................................................................................... 211
I/O Diagnostics.................................................................................................... 220
Profibus Diagnostics ........................................................................................... 236
Download Alarms ................................................................................................ 238
Collect Debug Info .............................................................................................. 239
Configuration ................................................................................................................. 240
Consistency Checker .......................................................................................... 241
Set Date and Time .............................................................................................. 245
Simulation Control............................................................................................... 247
Controller ....................................................................................................................... 248
Status Window / Dashboard................................................................................ 249
Log Manager Viewer ........................................................................................... 250
Restart JVM ........................................................................................................ 252
Flash Applicom Card ........................................................................................... 253
Restart Controller ................................................................................................ 256
Halt Controller ................................................................................................................. 257
Operator Screen ................................................................................................. 258
Documentation .................................................................................................... 259
Lesson Review .............................................................................................................. 260
Remote Troubleshooting .......................................................................................................... 264
Debug Monitor URL ....................................................................................................... 266
I/O Diagnostics .............................................................................................................. 271
Check / Change Address - Addressing Conflicts ................................................ 272
Copying Data Logging Files to PC ...................................................................... 280
Check I/O Function ............................................................................................. 283
Lesson Review .............................................................................................................. 284
Laptop Simulation .................................................................................................................... 286
Virtual box...................................................................................................................... 288
Revision 4
Lesson Review .............................................................................................................. 291

Revision 4
Revision 4
STUDENT NOTES:
Course Completion Certificate

The course has a final online checkout test. A course certificate will be issued if the final test is satisfactory
passed by 80%.
Course Description
This course is designed to train internal personnel on the Amphion Control System, single board
computers, PC requirements, and troubleshooting. Locating technical documentation relevant to the
control system will be covered. Participants will use simulation to navigate SBC service pages, create a
compact flash, and demonstrate basic troubleshooting techniques remotely. This course also aims at
preparing participants for an online checkout test, which they need to complete in order to obtain
Amphion Discipline Level 0.
Course Goals
At the conclusion of this course, the participants should be able to:
Recognize the Amphion structure in comparison to other control systems used by NOV.
Set up and maintain their PC for working in an Amphion environment using prescribed documentation.
Create a working compact flash card.
Utilize the basic functions of SBC service pages for troubleshooting using a Flares Main Page under
instruction.
Carry out basic troubleshooting techniques given instructions.
Demonstrate capabilities and limitations of SBC simulation on laptop using virtual box.
Revision 4
Revision 4
Safety Precautions
Revision 4
STUDENT NOTES:
General Safety
Safety Requirements
NOV equipment is installed and operated in a controlled drilling rig environment involving hazardous
situations. Proper maintenance is important for safe and reliable operation. Procedures outlined in NOV
manuals are the recommended methods of performing operations and maintenance.
Personnel Training
All personnel performing installation, operations, repair, or maintenance procedures on the equipment,
or those in the vicinity of the equipment, should be trained on rig safety, tool operation, and maintenance
to ensure their safety. Contact the NOV training department for more information about equipment
operation and maintenance training.
Recommended Tools
Service operations may require the use of tools designed specifically for the purpose described. NOV
recommends that only those tools specified be used when stated. Ensure that personnel and equipment
safety are not jeopardized when following service procedures or using tools not specifically
recommended by NOV.
General System Safety Practices

The equipment discussed in this manual may require or contain one or more utilities, such as electrical,
hydraulic, pneumatic, or cooling water.
 Isolate all energy sources before beginning work.
 Avoid performing maintenance or repairs while the equipment is in operation.
 Wear proper protective equipment during equipment installation, maintenance, or repair.
Revision 4
Replacing Components
 Verify that all components (such as cables, hoses, etc.) are tagged and labelled during disassembly and
reassembly of equipment to ensure correct instalment.
 Replace failed or damaged components with NOV certified parts. Failure to do so could result in
equipment damage, or personal injury.
Routine Maintenance
Equipment must be maintained on a regular and routine basis. See the service manual for maintenance
recommendations.
Proper Use of Equipment

NOV equipment is designed for specific functions and applications, and should be used only for their
intended purpose.
Revision 4
NOV Control System History

Revision 4
STUDENT NOTES:
Automation / Relay Logic

Due to the rising demand for flexibility in the U.S. automotive industry in the 1960's, there was a need
for new control system for production machines, which could replace the relay and timer management.
The process of updating the control system for the annual model change was both time-
consuming, expensive and requires experienced electricians.
General Motors Hydra Matic (the part of General Motors that stood for automatic
transmission) produced in 1968 some specifications they wanted to be met:
- Programmable control for the sake of flexibility for rapid restructuring of the production equipment. -
Management to work in an industrial environment. - Input and output will be digital, and the
voltage should be within the areas in typical industrial applications.
- Management should be able to handle analog inputs and outputs, to be modular so that extension or
replacement shall be made easily and efficiently. - The programming will be easy and
could change rapidly, so that it can be a fast training of maintenance personnel.
The winning proposal came from Bedford Associates of Bedford, Massachusetts. The result was the
first PLC and called MODICON (MOdular Digital CONtroller) 084, because it was the eighty fourth
project to Bedford Associates. MODICON was sold to Gould Electronics, and later to Schneider Electric,
which still owns the brand today.
NOV supplied SCR systems are one of the few areas in which hardwired relay (contactor) logic is still used
for control and interlocking. Typically there is a PLC fitted which does ancillary control and monitoring.
Source: automationmag - http://www.automationmag.com/features/the-father-of-invention-dick-morley-

looks-back-on-the-40th-anniversary-of-the-plc.html
Revision 4
STUDENT NOTES:
Automation / Relay Logic

In the past many machines were controlled by relays. Relays are electromechanical switches that are
controlled by energizing a coil which will open or close a mechanical switch / contact.
The term normally open (NO) means when the relay is in the rest position (coil is not energized); the
contact would be in the open state.
The term normally closed (NC) means when the relay is in the rest position (coil is not energized); the
contact would be in the closed state.
Relays have different ratings. A relay with a 24VDC and 5A rating means the coil can be energized with
24VDC and the contact is able to conduct 5A. Relays were used in different combinations along with timers
and counters to perform logical operations. Control tasks were solved with contact and relay controls. The
function of a controller was thereby defined through the wiring and combination of the switching
elements. Such a controller is called a hard-wired programmed controller.
Circuit diagrams, terminal connection diagram and wiring lists served as the foundation. Yet, the system
could only be installed after it was known which tasks had to be solved and which function blocks, e.g.
switches, contacts etc., were available. If a mistake was made, the wiring had to be disconnected and
reconnected correctly. Every change or expansion in function was always associated with changes in
components parts, rewiring and installation works.
Revision 4
STUDENT NOTES:
Relays
The term normally open (NO) means when the relay is in the rest position (coil is not energized); the
contact is in the open state.
The term normally closed (NC) means when the relay is in the rest position (coil is not energized); the
contact is in the closed state.
Revision 4
STUDENT NOTES:
PLC
The abbreviation for PLC stands for Programmable Logic Controller. A PLC can be compared to a human
brain. The CPU would be the brain that reacts to input signals from your eyes, nose or ears. Your brain
calculates what would be the best action to take and sends the output signals to your muscles, mouth etc.
for action. Similarly a PLC executes a program that controls outputs like pumps, valves, motors, alarms,
lights etc. based on the input signals it receives from the field devices like buttons, proximity sensors,
sensors and switches.
A PLC can also be referred to as a PLS (Programmable Logic System) or PC (Programmable Controller),
depending on manufacturer and geographical location.
Revision 4
STUDENT NOTES:
EDS
Comprises of a control system and an EDS V-Series Disc Brake installed on the Drawworks.
Controls include a Touch-screen HMI, Joystick Assembly, Remote I/O Assembly, PLC/SBC Assembly,
Pneumatic & Hydraulic Control Assembly and Instrumentation.
 Fault tolerant and smart control system, takes prompt action to control the load in the event of
failures (e.g. sensor failures).
 Easy to operate Joystick control reduces driller fatigue.
 User friendly driller interface
HMI
The HMI is a sunlight viewable rig-floor graphical user interface for the driller. It is a temperature
controlled, environmentally sealed single board computer with flat panel display and touch-screen input.
Its standard features include a Pentium™ computer. As standard, the HMI is rated for installation into
Zone-2 hazardous areas. Zone-1 is available as an option. The panel assembly is supplied with a floor
mounted stand. Alternately, the panel may be mounted into a drilling console. The HMI comes standard
as CE marked.
The HMI communicates with the PLC via Ethernet. Both cat-5 cable and fibre-optic connection is
supported.
Key Specifications:
 Display size 15” (nominal) diagonal viewing area
 Voltage Input 85 – 256VAC
 Frequency 47 – 63 Hz
 Ingress Protection IP 56 / NEMA 4
 Operating Temperature -40 degF to 122 degF
Revision 4
 Storage Temperature -4 degF to 140 degF

 Max Dimensions 16.5” (W) x 14.75”(H) x 7.5” (D)
Driller’s Control Console (Drill Floor Console)

The EDS controls are typically located within the Driller’s Console.
Joystick Assembly and Controls

The joystick pedestal assembly contains:
1) Heavy Duty Joystick.
2) E-Stop button.
3) Horn Silence / Override pushbutton
4) Autodrill enable pushbutton
As standard these components come pre-assembled into a stainless steel pedestal assembly which has a
hammer union at the bottom of the pedestal. The hammer union is usually welded to the floor, and
allows for easy removal of the pedestal should the need arise to access other equipment.
Alternately, the individual components may be installed into an integrated driller’s console. All signals to
and from the joystick assembly are I.S. protected. The joystick is rated to be installed into Zone-1
hazardous areas.
Remote I/O Panel (PLC Control Assembly)

All of the I/O and associated equipment for the control system is mounted within an electrical panel. This
panel is usually installed in an SCR or VFD control house. Dual power supplies with UPS are provided to
ensure control system power is maintained in the event of either rig power failure, UPS failure, or power
supply failure. Multi-core cables are run from the PLC panel to Junction boxes located on the drill-floor.
Reference Documents
SM01063 (EDS Controls Service Manual)
SM00890 (Varco Disc Brake Assembly Service Manual)
D811000135-FDS-001/D251001953-FDS-001
Revision 4
STUDENT NOTES:
VICIS
Key:
1. Drillers Work Station
2. Assistant Drillers Work Station
3. Server Cabinet
4. DWS Cabinet
5. HMI PC Cabinet
6. DWS Cabinet
7. Server Cabinet
8. Ethernet Switch
9. VSR PLC’s
10. VDE Ethernet Switch Cabinet
11. Individual Tool ATC (Advanced Technology Controller) or SBC (Single Board Controller) Enclosures
V-ICIS
In the late 1990s Varco and National Oilwell had traditional competing SCADA based systems – VICIS
(Varco Integrated Control and Information System) and Cyberbase respectively. These were based on the
usual layered structure of controllers, PCs and HMIs. These systems were labour intensive, both in
creation and maintenance, with specialists required for different areas and/or technologies.
WonderWare was the SCADA package used, which required licenses and software to view/debug/update.
Diagnostic Works Stations (DWS) were of some use but consisted of preconfigured SCADA screens. PLC
manufacturers, types and models could vary but were primarily Siemens S7-3/400 and/or Directlogic
2/3/400.
Revision 4
VICIS was also integrated with a number of third party systems. For service engineers it was impossible to
have enough knowledge to a suitable depth in all areas for unsupported troubleshooting.
Varco developed the ATC, later known as an SBC, an industrial PC with a Linux operating system running
Java machine code and a web interface for operation and maintenance.
Operator Workstations
The V-ICIS workstation is the user's interface to the control network and tools. Workstations consist of
integrated control panels and an ergonomic chair designed to reduce the effects of stress and strain
associated with long periods of sitting.
Touchscreens
Each operator workstation provides two to four touchscreens, sometimes referred to as an HMI (Human
Machine Interface) or MMI (Man Machine Interface). Touchscreens display the software application used
to manage operator requests.
Touchscreens display V-ICIS tool control, drilling operations, alarms, and status information. By default,
the screens present only the information pertinent to the current activity. This allows the operator to
concentrate on the job at hand without the distraction of extraneous data.
Touchscreens communicate through computers located in one of two computer cabinets. One computer
is used per touchscreen. The display signals and serial feedback (touch) are communicated between the
touchscreen and its computer by a pair of fibre optic strands. To facilitate this, each touchscreen
computer contains a fibre optic transceiver card. Fibre optic media for this signal eliminates noise
interference potential.
Wonderware® software is used for the touchscreen interface. Each touchscreen computer uses the same
Wonderware application, which contains all screens for operating various tools and processes on the rig.
Network System
The network ties tool controllers and status information together to allow both control and monitoring
capability from any operator workstation. Optionally, this information can be monitored from desktop
computers in other locations such as the tool pusher’s office. The network’s archiving system stores all
pertinent drilling information for review at a later date. Servers, DWS (Diagnostic Work Station)
computers, touchscreen computers, the VSR (Varco Signal Router), the Drilling Information Module (DIM),
RigSense computers (if present), and many of the tool controllers (PLCs and SBCs) connect to the
backbone switch via TCP/IP over Ethernet. Remote PC workstations such as RigSense computers connect
to the backbone switch via smaller Ethernet switches located near the computer.
A redundant backbone Ethernet switch ties the VICIS network together. Similar to a hub, it also provides
"collision protection" for your data. The switch is an Alcatel Omni Switch/Router, available in two size
configurations (depending on the number of computers, tools controllers, and other equipment
connected to the V-ICIS network).
Reference Documents
42V-100 Rev B (V-ICIS Technical Reference Manual)
40222926 (V-ICIS Work Station)
41E8105-0030 (V-ICIS Topology)
Revision 4
STUDENT NOTES:
SCADA
What is SCADA Used For?

SCADA (Supervisory control and data acquisition) is an industrial automation control system at the core of
many modern industries, including:
 Energy
 Food and beverage
 Manufacturing
 Oil and gas
 Power
 Recycling
 Transportation
 Water and waste water
 And many more
SCADA systems are used by private companies and public-sector service providers. SCADA works well in
many different types of enterprises because they can range from simple configurations to large, complex
projects.
Virtually anywhere you look in today's world, there is some type of SCADA system running behind the
scenes, whether at your local supermarket, refinery, waste water treatment plant, or even your own
home.
How Do SCADA Systems Work?

SCADA systems deploy multiple software and hardware elements that allow industrial organizations to:
 Monitor, gather, and process data
Revision 4
 Interact with and control machines and devices such as valves, pumps, motors, and more, which are
connected through HMI (human-machine interface) software
 Record events into a log file
In basic SCADA architectures, information from sensors or manual inputs are sent to PLCs (programmable
logic controllers) or RTUs (remote terminal units), which then send that information to computers with
SCADA software. SCADA software analyses and displays the data in order to help operators and other
workers to reduce waste and improve efficiency in the manufacturing process.
Typically the HMI is described as a thick client. A thick client can be described as an HMI running a
programmed software package which contains the screens designed for the process, with the HMI
communicating with a server to send/receive data.
The Evolution of SCADA

In the 1950s, the first mini-computers were first developed and used for industrial purposes. In the 1960s,
what were once mini-computers were now considered mid-sized and they were used for remote
monitoring and supervisory control.
The term “SCADA” was coined in the early 1970s, and the rise of microprocessors and programmable logic
controllers (PLCs) during that decade gave enterprises a greater ability to monitor and control automated
processes than ever before.
In the 1980s and 1990s, SCADA evolved again with the wide use of local area networks (LAN), which
enabled SCADA systems to be connected to other systems, and the introduction of PC-based HMI
software.
In the 1990s and early 2000s, structured query language (SQL) databases became the standard for IT
databases but were not adopted by SCADA developers. This resulted in a rift between the fields of
controls and IT, and SCADA technology became antiquated over time.
Revision 4
STUDENT NOTES:
Cyberbase
The Cyberbase Control Unit comprises a man-machine computer with software for monitoring and
controlling various machinery and processes. The computer is built into Cyberbase's ergonomically
designed chair/console for the operator. It has been adapted for drilling operations by including
interfaces to essential systems operated by the driller, such as BHA control, Drawwork, iron roughneck,
mud pumps and pipe handling machines. Operations such as installation of drill pipes, hoisting and
lowering of the drillstring, and presetting of drilling depth are handled by the control unit.
The idea was born in 1991-92. It originated from Jon Gjedebo the founder and Managing Director of
Hitec. He wanted create a user friendly and versatile HMI (Human Machine Interface) interface.
The first commercial product was delivered in 1995 to the PPCON 2/4X platform on the Ekofisk field.
The first chair design was a hardwired control surface. Each piece of equipment had multiple switches and
lights for activating and controlling the rig floor equipment. The next generation was the first step in
streamlining the control surfaces. The hardwired switches were removed and replaced with keypads and
joysticks in the arms. Lights and indicators were replaced with two monitors. The chair was mounted on
Military-style tank shock absorbers. The on-screen display was adjusted for maximum ease of use and
designed to be easily read by the operator.
Revision 4
STUDENT NOTES:
Cyberbase
The next development was to modify the monitors to a smaller, more compact unit. Height of the
monitors could now be adjusted. This newer design also allowed for a smaller chair footprint by moving
the chair server and PLC to an external cabinet. The latest revision has the two monitors coming out of
the chair arms. This allows the operator greater flexibility in the position of the monitors. A less
obstructed view of well center can be achieved.
The Cyberbase Drilling Control System consists of three main sections. The chair with two arm pads and
control surfaces. The monitors with two separate screens for displaying drilling data. The pedestal which
contains the central connection point to the rest of the rig. The pedestal may or may not contain the PLC
and Server for the chair. All signals are cabled through the pedestal.
Revision 4
STUDENT NOTES:
Cyberbase Structure
There are three major sections to the Cyberbase structure; Machinery and Instrumentation, PLC for
Automation, and Operator Stations. The Machinery and Instrumentation is the field device used for
running rig operations, these include motors, sensors, drives, and monitoring devices. The PLC for
Automation are the major rig equipment PLCs that control the equipment for drilling operations. The
Operator Stations are used to interface the Driller’s command for operating the equipment to all the
distributed PLC control systems.
Reference Document
S01F7467A-OPM-001
Revision 4
STUDENT NOTES:
Cyberbase Topology
All information in the system is distributed via computer networks.
Four types of communication networks/links are used:

CCTV system (1): Control signals on TCP/IP protocol on Ethernet and video signals on NTSC standard
Cyberbases (2) TCP/IP protocol on Ethernet.
PLC system (3) Industrial Ethernet. With the use of a ring network topology a full communication is
ensured even when there is a breach on a single point on the ring.
Four types of communication networks/links are used:
Profibus DP network, interconnecting remote I/O’s.
Remote I/O units communicate with dedicated PLC’s via Profibus DP links (Note: Not shown on topology)
Reference Document
S01F7467A-OPM-001
Revision 4
Amphion System Overview

Revision 4
STUDENT NOTES:
Amphion Concept
Key:
1. Driller Work Station
2. Assistant Drillers Work Station
3. Dual Fibre Ring
4. Multi Tool Controller
Amphion Concept
This concept reduces the hardware required, the number of communication paths, the software required
to configure and support, and the overall complexity, while still providing the core functionality required.
Initially SBCs were used on standalone tools, such as top drives, or replaced individual tool controllers
(PLCs) in VICIS systems. Some of the last VICIS systems had SBCs for all drill floor tools apart from
Drawworks.
Ultimately a networked SBC concept was developed which resulted in a dramatic reduction in hardware
and complexity. It was named Amphion. The HMIs are thin clients, as opposed to thick, as they have no
programmed software package loaded with screen configuration; screens are stored in the SBCs and
displayed through a browser.
Other benefits of SBC/Amphion over PLC/SCADA systems include:

 Reduced cabling;
 Lower cost of ownership;
 Space and weight savings;
 Scalable architecture allowing use on all types of rigs;
Revision 4
 Less 3rd party software;

 Built in diagnostics
Amphion Design Tenets

The Amphion control system tenets are fundamental principles used to guide design decisions in regards
to system hardware and software. These principles represent the high level design strategies and goals of
the Amphion system.
The tenets are listed below:

 Avoid the use of equipment that requires special hardware or software to setup or configure the
system. To ensure simple, fast field replacement, equipment requiring specialized knowledge, tools,
training or experience should be avoided. It is preferred that device setup functionality be made
available through Amphion single board computers (SBCs) via a wizard or similar method that is
intuitive to the user. Such systems must have a maintenance web-browser terminal available to
perform these functions at all times.
 Access to the control system for diagnostics and maintenance should be possible with virtually any
computer running no special software.
 Hide the complexity of the control system from the end user by providing an easy to understand web-
based interface for items such as diagnostics and setup.
 Configurability is the key to producing and maintaining quality software. Changes instigated by
specific rigs, tools or customers should utilize a design reassessment to achieve an overall approach
that accommodates future needs through configuration only.
 Ensure the system platform is abstracted from both the computing hardware and operating system
levels. This maintains flexibility and simplifies changes in hardware platforms that come as these
platforms run out their life cycles.
 To ensure remote connectivity for all systems, communication protocols for HMI access to the system
must be open Internet protocols that operate through VPN routers and firewalls.
 Minimize the number of special software development tools required for developing applications on
the system platform. Maintain simplicity in application development.
 Integrated rig supervisory control and data acquisition (SCADA) systems must be implemented in a
distributed manner that scales from one SBC to dozens of SBCs without the need for server services.
 The system should maintain a root mean square (RMS) cycle time of 20 milliseconds.
Reference Document - D6A1000576 2.1

Revision 4
Single Board Computer

Revision 4
STUDENT NOTES:
Concept
SBC/Amphion System Overview

The Amphion Software System is a configurable control system capable of running on multiple hardware
platforms and computer operating systems through use of the Java Virtual Machine.
Amphion controller hardware consists of a single board computer (SBC) with Ethernet and optional
Profibus DP communications ports. Primary storage for the SBC is on removable compact flash cards.
Additional hardware used as part of the Amphion system includes touch screen computers (generally
referred to as HMIs) with Ethernet communication and PLC I/O points and sensors with either Modbus or
Profibus communication.
Amphion system controllers currently run a variant of the Linux operating system. On the operating
system, the Linux version of the Java Virtual Machine (JVM) is running. Running as Java Applications on
the JVM are a web server, database and the Amphion tool control application. The tool control
application interfaces with the web server for communication to external items such as screens, other
SBC and I/O points. The database is used by the tool control application and web server for storing and
retrieving data during operation.
The touch screen HMIs used for Amphion user interface have integrated computers running a Windows
operating system with the Windows version of the JVM installed and using Internet Explorer as a client
application for interfacing with the Amphion controllers.
Revision 4
STUDENT NOTES:
Use Cases
The diagram illustrates the “actors” and “use cases” for the Control System. The SBC fulfills the role of the
“communicates relationships” (i.e. the arrows) between the various actors and use cases, along with the
high-level functions the system each of them will perform.
The use cases presented are:
 Rig Electronics Tech (ET)
 NOV Service Person
 Control System Operator
 Control System Engineer
 Peer Control System
The first four are humans and the fifth is a peer control system computer. The SBC will enable human
interaction with a control system and peer-to-peer communications between two control systems. Peer
to peer communications are usually handled by a dedicated SBC for each interface, known as a gateway
SBC.
Service Personnel and ET's will perform a variety of “read-only” functions including Installation and
Configuration of the Control System, Troubleshooting & Diagnostics, and Calibration. These functions are
typically available to any user without any security restrictions.
Control Systems Operators will have secure access to more sophisticated functionality using the
Operations Control subsystem. Operations Control allows setting and changing of control system modes
and operations complete with system feedback and indicator alarms.
Revision 4
STUDENT NOTES:
Hardware Types
Hardware Brick
Key:
1. Channel Transmission LED
2. Communication Status LED
3. Power Switch
4. Profibus DP1
5. Profibus DP2
6. Shock Mounts
7. COM1
8. Link LED
9. Transmit LED
10. Ethernet
11. Key Board/Mouse
12. SVGA
13. Reset
14. Compact Flash LED
15. Power LED
16. Ground
17. 24VDC +/-
18. Compact Flash Card
Revision 4
Brick (ATC – Advanced Technology Controller)

The original ‘brick’ format was custom made for NOV. It consisted of:
 CPU motherboard with (ported to the outside of the enclosure)
 Ethernet port, link and activity LEDs;
 slot for a Compact Flash (CF) based hard drive with activity LED;
 PS/2 keyboard/mouse port;
 VGA display port;
 Serial port
 Applicom PC104 Profibus master board (1 or two depending on tool) with LED viewing window
 External power (24Vdc) terminals/connector and LED
 Power switch
There were several minor variations over the years with ports and indicators moving around, changes in
CF slot orientation and internal motherboard changes.
The two main versions are known as Varco and NOV bricks and feature different motherboards. This has
an impact on which firmware versions can be used on each type.
The CF slot is on the right hand side of the enclosure and has a cover secured with two captive
thumbscrews – this is typically lost very soon after installation. The CF eject mechanism is liable to break
and this, in combination with the SBC being mounted close to trunking, necessitates the creation of a tab
on the CF, using insulation tape or similar.
The brick type is obsolete and should be replaced by the latest Beckhoff type where possible - see PIB
10669656-PIB.
The Advanced Technology Controller (ATC) or Single Board Computer (SBC) assembly, located in the
control system cabinet, is a high-speed CPU to which you can connect using a browser.
Power
Press the Power button to turn the ATC on or off.
Reset
Press the Reset button to restart the ATC.
CAUTION: Do not press the Reset button while the ATC is controlling a tool or communicating with other
devices on the network
Power Supply
A standard Varco cabinet contains a dedicated 24-volt DC power supply.
CompactFlash™ Card
The CompactFlash card cover is secured by a screw-down panel.
Communication Ports
 Ethernet (labelled ENET) connects the ATC to the local area network (LAN).
 Note: To communicate with standalone brick SBCs a crossover Ethernet cable may be required if
connecting directly. If the Ethernet connection is through an Ethernet switch then a straight through
Ethernet cable is required.
Revision 4
 PROFIBUS DP1 port connects the PROFIBUS network and all tool devices to the ATC. This network
includes all the devices on the tool.
 PROFIBUS DP2 port (optional) connects the second PROFIBUS network to the ATC. This network may
also connect another controller or PLC.
 COM1 can be used to connect a serial cable between a computer and the ATC.
 Mouse/Keyboard can be used to connect a keyboard or mouse to the ATC.
 Video can be used to connect an SVGA monitor to the ATC.
CAUTION: Connecting directly to the ATC using the COM1 or the Keyboard/Mouse and SVGA ports is a
non-standard procedure for this product. Do not experiment with these connections.
Shock Mounts
Shock mounts insulate the ATC from sudden movement of the control system cabinet.
Grounding
The Ground nut electrically grounds the ATC.
LED Indicators
PROFIBUS Channel Transmission Light

 This light is normally off.
 Steady green indicates that the PROFIBUS network is ready.
 Red indicates a communication error.
PROFIBUS Communication Status Light

 This light normally blinks green.
 Blinking green indicates that data is being transmitted or received.
 Steady green indicates that the unit is ready to communicate.
 Steady red indicates a PROFIBUS wiring problem, DP2 bus speed discrepancy or DP2 node addressing
conflict.
 Blinking red indicates a data exchange error.
Power
 The Power indicator displays green when the ATC is on.
CompactFlash
 The CompactFlash indicator blinks yellow when the CompactFlash is in use. The CompactFlash stores
information.
Transmit
 The Transmit indicator blinks yellow when the ATC is receiving data.
Link
 The Link indicator displays green when an Ethernet communication is established.
Reference Document
SM00998 – Rev B
Revision 4
STUDENT NOTES:
Hardware – Brick Enclosure
Key:
1. Circuit Breakers (Typical)
2. Terminal Blocks (Typical)
3. I/O Modules
4. Repeaters
5. Relays
6. Advanced Technology Controller
7. Power Supplies
8. External Controls
Brick
When the brick SBC began to replace PLCs it was placed in a cabinet of the same size, although the use of
Profibus and other changes in control system structure meant that a lot of space was unused.
It was realized that a lot of the hardware in individual panels was redundant, so a rack based SBC module
was created.
Revision 4
STUDENT NOTES:
Hardware Rack
Key:
1. COM 1
2. Ethernet Status Lights
3. Ethernet
4. Mouse/Keyboard
5. Video
6. Profibus DP1
7. Compact Flash Card
8. Power Status Light
9. Hard Disk Drive Status Light
10. Profibus Status Light
11. Fuse (10-Amp/250-Volt)
12. Power
Rack
The rack is housed in a cabinet known as a Multi Tool Controller cabinet (MTC) and can accommodate
nine SBCs. Again the rack type is custom built for NOV.
The rack is not a conventional PLC type which provides power and communication connections into which
modules are slotted. It merely provides a common, compact physical receptacle for SBC modules. There is
a common power supply (the rack type require 5Vdc) but the rack only provides a channel at the top to
route power cables.
Revision 4
Internally the components are very similar and external connections are the same, with the addition of a
replaceable fuse.
There are two upgrade kits for the rack type SBC due to obsolescence of hardware. See PIB ALL-06-01 and
document 10623355-PRO.
Power
Do not remove the CompactFlash® card before turning off power. Do not turn off the tool controller while
it is controlling a tool or communicating with other devices on the network
Press the Power button on the tool controller to turn it on or off.

The Power LEDs display green when the tool controller is on.
CompactFlash® Card
Tool controllers contain a processor and memory, and run a specialized version of the Linux™ operating
system. A Java™ Technology program is embedded on a removable device called a CompactFlash memory
card. On the Advantech tool controller, the CompactFlash card is installed in a slot in the tool controller
chassis, secured by a screw-down panel. The Beckhoff tool controller has a CompactFlash eject button.
The CompactFlash LED (HDD) blinks when the card is in use (information is being read or written).
Communication Ports
Although some tool controllers have keyboard, mouse, and monitor ports similar to a standard PC, they
should not be used during normal operations. Connecting directly to the tool controller using the COM1 or
the keyboard/mouse and video ports is a non-standard procedure for this product. To prevent possible
equipment damage, do not experiment with connections.
Ethernet (ENET)
Connects the tool controller to the local area network (LAN).
Note: To communicate with standalone brick SBCs a crossover Ethernet cable may be required if
A green light located near the port displays solid green when communication is established, and another
blinks yellow when the tool controller is sending or receiving data.
Profibus (Process Field Bus)

Profibus is optional. Connects the tool controller to remote I/Os. The Profibus communication status
indicator normally displays green, indicating a ready status. Blinking green indicates that data is being
transmitted or received. Blinking red LEDs indicate a data exchange error. Steady red indicates a wiring
problem, a bus speed discrepancy, or a node-address conflict. Blinking red and green indicates that the
Applicom card was flashed, but there is no Profibus hardware attached to it.
COM1
Can be used to connect a computer to the tool controller using a serial cable
Mouse/Keyboard
PS/2 port that can be used to connect a keyboard or mouse to the tool controller
Revision 4
Video
Can be used to connect an SVGA monitor to the tool controller
Reference Document
D811001117-MAN-001
Revision 4
STUDENT NOTES:
Hardware Beckhoff
Key:
1. Ethernet - Profibus Interface Card (APPLICOM Card)
2. Applicom Card Status Display
3. Profibus Connection
4. CPU Modules
5. Ethernet Connection (Port 1)
6. Ethernet Connection (Port 2)
7. Battery Compartment
8. Labeling Area
9. CPU Status Display
10. Compact Flash Card Insert
11. Compact Flash Card Eject
12. Power Supply Module
13. Power Supply Status Display
14. Status LCD Display
15. Power Supply Inputs (24vdc)
Beckhoff
The Beckhoff SBC is a commercially available modular embedded PC. The unit as used by NOV consists of
the following (shown right to left below):
 Power supply module (requires 24Vdc – up to 5A surge on power up)
 CPU
 Ethernet module (switch)
Revision 4
 Profibus (Applicom) module, also commonly known as Brad module (and yes, it is normally mounted
upside down).
Behind the flap between the two Ethernet ports is a button type battery for the date/time – this needs
replaced every five years.
When first adopted the digital display served no purpose but as of platform version 7 shows IP address.
Power
it is controlling a tool or communicating with other devices on the network
Press the tool controller’s individual circuit breaker located inside the MTC cabinet to turn it on or off.
The Power LEDs display green when the tool controller is on.
CompactFlash® Card
Tool controllers contain a processor and memory, and run a specialized version of the Linux™ operating
system. A Java™ Technology program is embedded on a removable device called a CompactFlash memory
card. On the Advantech tool controller, the CompactFlash card is installed in a slot in the tool controller
chassis, secured by a screw-down panel. The Beckhoff tool controller has a CompactFlash eject button.
The CompactFlash LED (HDD) blinks when the card is in use (information is being read or written).
Communication Ports
Ethernet (ENET)
Connects the tool controller to the local area network (LAN).
Note: To communicate with standalone brick SBCs a crossover Ethernet cable may be required if
LAN 1 or LAN 2 (related to Ethernet ports 1 and 2) displays solid green when communication is
established, and blinks when the tool controller is sending or receiving data.
Profibus (Process Field Bus)

Profibus is optional. Connects the tool controller to remote I/Os. The Profibus communication status
indicator normally displays green, indicating a ready status. Blinking green indicates that data is being
transmitted or received. Blinking red LEDs indicate a data exchange error. Steady red indicates a wiring
problem, a bus speed discrepancy, or a node-address conflict. Blinking red and green indicates that the
Applicom card was flashed, but there is no Profibus hardware attached to it.
Reference Document
D811001117-MAN-001
Revision 4
STUDENT NOTES:
Multi-Tool Controller (MTC) Cabinet

The MTC cabinet houses the workstation and network control components, and is normally located in the
drill floor local electrical room (LER).
Revision 4
STUDENT NOTES:
Network Switches
The MTC cabinet contains redundant network switches developed particularly for use in industrial
environments. They allow construction of switched Ethernet networks that conform to the IEEE 802 and
802.3u standard using copper wire or optical fibre in a ring topology. Switches are mounted by snapping
them onto a standard DIN rail.
Power Supplies
Two redundant 24-volt DC power supplies provide power via a common bus to most components inside
the MTC. In general, each component has its own circuit breaker to provide maximum maintenance
flexibility. There are also two 5-volt power supplies dedicated to the Advantech tool controllers, and two
24- volt power supplies dedicated to the Beckhoff tool controllers that work in parallel to share power
demands. One, however, is sufficient should the other fail. The multi-tool controller (MTC) cabinet
provides power distribution for workstation equipment, and supports dual redundant uninterruptible
power supply (UPS) feeds. It is designed for installation in a safe area, and supports bottom-entry cable
penetration.
Revision 4
STUDENT NOTES:
Switching on
The external indicators, power, drive activity, Ethernet link and activity, behave in similar ways on each
type of hardware. After power application the drive/HDD lamp should blink rapidly for approximately the
first minute and then blink intermittently. This may be repeated if anything has been transferred to the
‘to install’ folder.
The brick and rack type SBCs have the advantage of VGA and PS/2 ports. Through the use of a monitor the
boot sequence can be monitored for anomalies and errors.
With the keyboard commands can be entered for configuration and/or diagnostics.
The boot sequence can be monitored in VirtualBox.

Revision 4
Terminology and Abbreviations

Revision 4
STUDENT NOTES:
System Level
Revision 4
STUDENT NOTES:
Revision 4
STUDENT NOTES:
Revision 4
STUDENT NOTES:
Debug Level
Revision 4
STUDENT NOTES:
Revision 4
STUDENT NOTES:
Adapter
See Network adapter.
AR
Automated Roughneck: a tool that makes up and breaks out pipe connections.
ATC
Advanced Technology Controller, consists of a high-speed CPU with one or two
PROFIBUS cards mounted in the control system cabinet.
ATC program
The software running on the ATC used to manage the tool and diagnose problems.
Bus
A shared pathway or channel that is used by multiple devices.
C2C
Controller-to-controller. This abbreviation identifies communication between two ATCs.
Class
A method used to group data collected from points on the tool.
CompactFlash
A 50-pin connection standard used to connect to flash memory in the ATC.
Component
A part of a tool, or a tool used on a rig (i.e., a rig component).
Controller
Another name for the ATC.
Control system
See Electrical control system.
DCN
Drilling Control Network.
Revision 4
DHCP
Dynamic Host Configuration Protocol.
DP1
First Applicom card connected to the PROFIBUS DP network (typically used for tool
remote input/output)
DP2
Optional second Applicom card connected to the second PROFIBUS DP network
(Typically used to interface with other PLCs)
Electrical control system
The solenoids, J-boxes, service loops, sensors, ATC, and control stations that provide
feedback and issue commands to the tool.
E-Stop
Emergency Stop.
Ethernet
The name of a particular method for connecting computers together in a local area
network.
HMI
Human Machine Interface (touchscreen).
HTTP
HyperText Transfer Protocol.
Interlock
A condition that needs to be cleared.
IP address
A unique number that identifies a computer, such as an ATC, on the Internet.
Item
A piece of information stored in the ATC for each point or node on a tool. This
information may be persistent (stored in CompactFlash memory) or transient (lost when
the power to the tool and ATC is off).
J-box
Junction box.
Jar File
A collection of application program files.
JVM
Java Virtual Machine.
Main Web Page
The main page of the ATC program.
Network
A group of computers connected together.
Network adapter
A small computer, usually in the form of a board (or card) that controls a specific task,
connecting to a local area network.
MS-DOS
Microsoft Disk Operating System, a computer operating system.
Net
Refers to commands originating from the touchscreen of an HMI.
Node
A remote I/O device that communicates with a controller.
PCMCIA
Revision 4
Personal Computer Memory Card International, the association that defined the
standard for pocket-sized memory cards.
Persistent value
An analog or digital setting stored in the ATC that describes the current state or
configuration of a point or node on the tool. Persistent values remain after the tool and
ATC are powered off.
PID
Proportional Integral and Derivative, technology for performing closed loop control.
PID loop
The setpoint-feedback loop that controls some tool systems.
PLC
Programmable Logic Controller.
PPP
Dial up networking protocol.
PRS
Pipe Racking System.
PROFIBUS
Process Field Bus, a network that allows devices to communicate over a common bus
without the need for specially-designed interfaces.
Read-only
The state of a file or item of information that cannot be changed by the user.
Setpoint
The point at which a calibration or limiting value is set.
TCP/IP
Transmission Control Protocol/Internet Protocol, TCP enables two hosts to establish
communications and transmit data. IP defines the formatting of information packets and
the addressing scheme.
Tool
Varco equipment controlled by the ATC.
UML
Unified Modeling Language.
VFD
Variable Frequency Drive.
ZMS
Zone Management System, a tool for monitoring and managing the movement of
equipment within its predefined operational space to prevent interference and collisions
with the rig structure and other equipment.
Revision 4
Revision 4
Revision 4
Revision 4
Revision 4
Revision 4
NOV Resources
Revision 4
STUDENT NOTES:
Software Products Server

A central location exists to store engineering released varballs, field varball backups, and rig firmware
version information at the NOV Software Product Server (http://sps.nov.com/app). Installations organized
by customer and rig names are created in the Software Product Server by engineering prior to release of
software. On a go forward basis, the SHP job number will also be included as rig identifiers to help
manufacturing personnel identify the correct software. SHP is Sam Houston Parkway manufacturing
facility where many of the control panels are manufactured and tested. Each rig added to the server will
require firmware versions to be selected by engineering and download links to the firmware versions will
be provided on the rig page for easy access. Varball backups loaded to the server will be checked against
the firmware assigned to the rig and errors will be shown for each varball with an incorrect version.
Customers do not have access to SPS.
Documentation
Access to Documentation Portal. Information relating to Software Components, Creating Amphion
Images, Varball Backups and Versioning, Versioning Roles and Responsibilities
Revision 4
STUDENT NOTES:
Documentation Portal
The Documentation tab on the SPS main page takes you to the Documentation Portal
You will find information relating to the following topics

 What is Amphion?
 Amphion Versioning
 Support Systems
 Creating Compact Flash Images
 Control Systems
Information found within Wiki sites is not always updated and therefore should not be fully trusted; if in
doubt confirm information via a controlled document via RigDoc or TeamCentre
Revision 4
STUDENT NOTES:
Amphion Software Network

ASN contains links to various resources detailing
Platform (firmware) Development

Controller Development Trac (software engineering version of Tracker for tracking issues and updates)
WWW Development Trac (software engineering version of Tracker for tracking issues and updates)
Platform Repositories (master ‘vault’ containing all firmware and associated files, including for SBCs which
are pre-varball)
Applications Engineering
Applications Development Trac (software engineering version of Tracker for tracking issues and updates)
Applications Code Repositories (master code ‘vault’ containing all application (tool) code and associated
files, including for SBCs which are pre-varball)
Testing and Simulation
Testing Development
Amphion Infrastructure Management
Amphion Documentation (limited)
Amphion Project Guidelines
Amphion_Links
On the RHS we have several Amphion_Links
Varball Server takes you to SPS

Revision 4
Varco Software Wiki takes you to the ‘old’ Wiki site

Revision 4
STUDENT NOTES:
Old Wiki*
Links to Organizational Chart, Coding Conventions, Tenets, Downloads…
Abbreviations, Configuration Files, How to Documents, Controller Logs, I/O, SBC Software, WWW
Documentation
Revision 4
STUDENT NOTES:
New Wiki
Select Amphion, Applications Team, Platform Team, the Team, New Hires then the Amphion System
You will find information relating to The Amphion System, Common Abbreviations, Software Product
Server (SPS) and How to documents amongst others
Revision 4
Drawing / Manuals
Revision 4
STUDENT NOTES:
Teamcenter
Main Page
Revision 4
STUDENT NOTES:
Teamcenter
Enter all or part of an item ID, alternate ID, name, or description into the search box at the top of the
screen. Press ENTER to execute the search.
The list of documents/parts matching the search criteria is displayed. The total number of results returned
is displayed in red at the top of each table.
Narrow the search by using the filter search box, or by selecting the specific Type or Group(s) to filter
within the results
Key:
Results from the Part search
1. Enter Part Number into the search box
2. Results from search
3. Enter additional search criteria here
Revision 4
STUDENT NOTES:
Enter all or part of an item ID, alternate ID, name, or description into the search box at the top of the
screen. Press ENTER to execute the search.
The list of documents/parts matching the search criteria is displayed. The total number of results returned
is displayed in red at the top of each table.
Narrow the search by using the filter search box, or by selecting the specific Type or Group(s) to filter
within the results
Results from Document search
Key:
1. Click on documents then enter the document number, name or description into the search field
2. Results from search
3. To filter results select which Group(s) and/or types of Documents you want to see
Revision 4
STUDENT NOTES:
Search Parts and Documents at the same time when the all radio button is selected (default choice)
Documents datagrid: displays Document Number, Name, Description, CAT (Category) and Type
Parts datagrid: displays Part Number, Alternate ID, Name, and Description
The column displaying the group icon indicates permissions for that item:
 grey icon – indicates details are viewable, but the datasets cannot be opened
 coloured icon – indicates viewer access to download files/datasets
The Group column indicates the item's origin.
Click the Cart icon to place the part/document in the Item Cart. Multiple items may be added to the Cart
list. From here you can update your list and either Print or Create PDF.
Click the ECR icon to place the part/document in the ECR. Multiple items may be added to the ECR list
before making a final decision to open an ECR or delete the item from the list.
Revision 4
STUDENT NOTES:
Wildcards
You now have the option to use wildcard characters (*, %) in your searches to control how the portal
locates information.
Manually type in wildcard(s) into search:

 (asterisk) = wildcard, any number of characters
 ? (question mark) = one character wildcard
Image 1
Shows result when Wildcard search begins with ‘123’
Image 2
Shows result when Wildcard search begins with ‘123’ and end with ‘45’, * = any number of characters in
between
Revision 4
STUDENT NOTES:
Wildcard characters (, %, etc.) are NOT needed to run a search. If you don’t manually type wildcard(s)
into the search, they are automatically added at the beginning & end of your search.
Wildcard searching only works on the "Items" page (for Parts/Documents); it does not work on the
ECR/EN page.
Image 1
Shows the result when Wildcard search ends in ‘123 (any value) 45’, ? = one character
Image 2
Shows the result for Wildcard search, automatically added wildcards (*) to front and back of search
(*123?45*)
Revision 4
STUDENT NOTES:
Key:
1. Number of results
2. Click on the document found to view details
3. Access to previous revision
4. Select Datasets page to access files
5. Select Changes page to access change history
Document Details
Click on the document to open a new window displaying the document details
Previous Revisions: Depending on your viewing rights, previous revisions may be available using the
Revision pull down. For the example above, this document has 1 revision “3".
Datasets: You can select the dataset (file) type (AutoCAD, MS Excel, MS Word, etc.) to open for viewing.
ACAD datasets open in AutoVue (unless you have extended viewing rights). Click on the links under
Related Forms to view EN and ECR forms.
Where Referenced: Shows you other parts your particular document has been referenced as a Related or
Defining Document.
Changes: This is a log for all revisions of the part – it displays a complete history of changes.
Revision 4
ECR Function
Click on the ECR button to fill out & submit the Engineering Change Request form. Enter the basic
information (*red asterisks indicate required files).
See ECR Documentation for information regarding creating ECRs.
Note: Be aware there are regional variations for submitting document changes. Not all Service locations
use the ECR function, In the UK; changes are requested through the local Field Engineering department.
Check with Supervisor/Tech Support for local process.
Cart Function
The Cart function works in a new way after application updates. It no longer sends an email containing a
link, but sends an email letting you know that the cart contents are ready for viewing/download through
the ‘MyEng’ link (The link will appear after the ‘cart’ button has been pressed)
If you are uploading several documents at once, it may take a few seconds to generate.
Revision 4
STUDENT NOTES:
Request
The ‘Request’ button will be greyed out if you already have access to the document. If you do not have
access to the particular document press the Request button, fill in the details and submit
Revision 4
STUDENT NOTES:
The ‘Help’ link, Top Right Middle opens an ‘Engineering Web Portal’ with links to training videos and
details specific functions within the application
Revision 4
STUDENT NOTES:
Rig Doc / Rig Office

Team Centre drawings are now being replicated in RigDoc. If using the RigDoc advanced search or the full
RigOffice application this has the advantage that documents are presented in an organised tree like
structure. Only recently built rigs are found in RigDoc and it’s not yet clear if the revisions are being
maintained. Use of RigDoc to find Amphion related drawings should be limited to identifying the
document number – this should then be used in TeamCentre to ensure the latest revision is accessible.
RigDoc Web (rigdoc.nov.com ) allows you to search for documents without using RigDoc Client or
RigOffice/RigDocument.
There are two main tabs in RigDoc Web:
Key:
1. Documents Workspace - Smart Search, Advanced Search or Search by Rig.
2. Support/Help- Search tips, User's guide, Support, Comments and suggestions and Statistics
Revision 4
STUDENT NOTES:
Smart Search allows you to enter several keywords to find documents. The search is performed on the
fields Case, Rig, Doc. No., Doc. Id. or by keywords for Name, Title and Responsible. You can search by using
boolean operators such as AND and NOT and other operators like “ “, ( ) and *. See Search tips or
Support/Help for more information. Press Enter to perform the search.
Search Tips
Smart Search provides some search tips to help you in your search. Simply click on "Click here for search
tips" to expand the search tips.
Revision 4
STUDENT NOTES:
Search Result
Key:
1. Search Results are displayed in the "Search Result" sub-tab, listing documents matching the
entered search critera/input. The result is displayed with the columns: "Status, Case No., Case
Name, Folder, Doc.No, Doc.Name, Title, Revision and Responsible. The result can be sorted by
using the functions on the right side of the search result.
2. Click the drop down menu ‘Search Result Rank’ and select an attribute (Case Number, Document
Number, Document Responsible etc.), then select Ascending or Descending to organize the
documents. E.g. Select Document Responsible and Ascending, to list via Document Responsible A-
Z. This will make it easier to find a certain Document if you know who is the Document
Responsible.
3. To open a Document in RigOffice, simply click on the document icon on the left side. It requires
RigOffice to be installed. A pop-up window may open first, asking for permission to start an
external program, which is RigOffice. Click on "Start Program".
RigOffice will open, displaying the Document in the RigDocument module

Revision 4
STUDENT NOTES:
Open Document Details in RigDoc Web

To open a Documents details in RigDoc web, simply click on "Details" on the Document line.
Clicking on "Details" will open a new tab called "Document", where you can find additional information
about the document.
Double click on the document in the files list to open the document
Revision 4
STUDENT NOTES:
By Equipment Type:
From Advanced Search you can choose multiple attributes before searching for documents.
2500+ documents have been found from the criteria entered above
Case Type – Equipment, case no. – Amphion
The list can be shortened by filling in additional criteria

Doc. Type – User Manual (note you can select from a drop down menu after three letters are typed)
The list has now reduced to 94 documents

Revision 4
STUDENT NOTES:
By Rig/Plant
Case Type – Rig/Plant, case no. – R5744
This search also shows 2500+ documents which are associated with a particular rig, In this case the
Maersk Highlander (The Case no. R5744 is an identifier used within RigDoc/Office for that particular
installation)
By filling in the additional criteria

Uncheck Include child cases, child case type – Equipment, include child cases – L7361 – Amphion Control
System, folder - 0060 – Engineering documentation, archive binder - USM – User Manual
We can reduce the number of associated documents to 2 User manuals

Revision 4
STUDENT NOTES:
Select a Rig
Input Rig name attributes or select from dropdown menu
What do you want to do?

Select an option from the dropdown menu
The search can be more specific by populating Equipment Package, Document Type Group, Document
Type etc.…
The associated documents will be listed below the search parameters
Note: Legacy Varco/Amphion documents found in RigDoc/RigOffice should be cross checked in

TeamCentre (eng.nov.com) to ensure latest revision is obtained.
Revision 4
STUDENT NOTES:
RigDocument is a program within the RigOffice suite.

Team Centre drawings are now being replicated in RigDoc. If using the RigDoc advanced search or the full
RigOffice application this has the advantage that documents are presented in an organised tree like
structure. Only recently built rigs are found in RigDoc and it’s not yet clear if the revisions are being
maintained. Use of RigDoc to find Amphion related drawings should be limited to identifying the
document number – this should then be used in TeamCentre to ensure the latest revision is accessible.
RigOffice Home
My Start Page
RigOffice main page, including links to recently accessed documents
Settings
Edit user profile settings, including colour preferences
Resources
Report enhancements and User guide
Documents, Files Downloaded and To Do List

If a particular link shows a number within, you can navigate to files associated
Search for documents

The white space can be populated with information and a search instigated directly from RigOffice Home
Revision 4
Recent Cases
Listed here are cases which you have accessed previously, allows easy navigation back to view a particular
case
Favourite Cases
Individual cases can be manually added to your favourites, allows easy navigation back to view a
particular case
Department (HCM)
Cases and information sorted by department
Products
Cases and product information sorted by a particular product
Rig/Plant
Cases and product information sorted by a particular installation or rig
Open Users Guide

The ? Within a circle (top right) opens up a link to the open users guide, providing more in depth
information relating to the RigOffice application
Revision 4
STUDENT NOTES:
In RigDocument, you can easily search, create new, update, revise and comment on documents.
This is a similar search criterion as that for Smart Search via RigDoc Web
Select RigDocument, then Document Search and type Amphion into the search
The results can be filtered by selecting single or multiple choices from the drop down menu above each
associated column
Revision 4
STUDENT NOTES:
The results have been filtered to 152 documents by selecting User Manual from the Doc. Sub-type drop
down menu
Revision 4
STUDENT NOTES:
Double click on the first User Manual to navigate to the document, right click on the .pdf and select view
(Read Only)
The document should begin to download and will open once complete
The document can be saved to your desktop or a specified location
Revision 4
STUDENT NOTES:
This is a similar search criteria as that for Advanced Search via RigDoc Web, the results are filtered
depending on the number of fields and drop down menus you complete
Select Advanced Search, type Amphion into the Case field, check the Include Child cases check box and
select Equipment in the Child Case Type drop down menu
Revision 4
STUDENT NOTES:
250 Block Diagram drawings have been found by applying a few filters to the search criteria
Select 0060 – Engineering documentation from Folder drop down menu, select Drawing from Document
Index drop down menu and select Block Diagram from Document Type drop down menu
Revision 4
STUDENT NOTES:
RigMaster is a Rig Systems Information Services (RSIS) database whose objective is to be a comprehensive
master directory of all Land and Offshore Rigs worldwide. RigMaster, coupled with its User-friendly front
end application will serve as a resource for NOV employees, to be used for strategic planning, business
development and customer service strategies.
Populate Smart Search with search criteria, e.g. name
Double Click on a particular rig within the generated list to view information related to Location, Rig
Statistics, Linked Cases and Previous Owners amongst others
The Linked Case tab shows folders containing all rig documentation; this makes it easier to find a drawing
associated with a particular piece of equipment on a particular rig
Open Users Guide

The ? Within a circle (top right) opens up a link to the open users guide, providing more in depth
information relating to the RigMaster application
Revision 4
STUDENT NOTES:
Identifying via a previous name

Rigs often change owners and therefore names also change, it may be necessary in some cases to identify
a Rig using a previous name
There are several sources available to identify the previous name of a rig
Tracker
RigMaster
RigLogix/Rigzone
RigLogix is an external website which requires registration

Revision 4
STUDENT NOTES:
Drawings / Manuals
What Documents Do I Need?
Prior to starting the ‘job’, you should prepare as well as possible, this should include collating the required
documentation as thoroughly as possible
 Equipment/Parts-Lists
 Correct recording documentation
 Required procedures
 Specific Technical Documents, Technical Illustrations, Assembly Drawings, Data Charts etc. (Consider
revision, you will have access to various revisions in document systems – equipment may not be built
to latest revision)
 Relevant Product Information / Service Bulletins (PIBs)
 Software (SPS)
The example documentation is in relation to Amphion, be aware there are many other document types
available.
Revision 4
STUDENT NOTES:
Reference Document
11033026-DIA
11405400-DIA
Revision 4
STUDENT NOTES:
Reference Document
11405402-IDX
11405486-IDX
Revision 4
STUDENT NOTES:
Reference Document
11405401-DIA
Revision 4
STUDENT NOTES:
Reference Document
11033026-DIA
16502058-FDS
Revision 4
STUDENT NOTES:
Reference Document
10629862-GAD
11405403-PRO
Revision 4
STUDENT NOTES:
Reference Document
11405404-SPL
11405407-DIA
Revision 4
STUDENT NOTES:
Reference Document
D801001614-SPC-001
Revision 4
STUDENT NOTES:
Reference Document
11405405-DIA
16567212-FDD
Revision 4
STUDENT NOTES:
Revision 4
Revision 4
Revision 4
Revision 4
Revision 4
PC Requirements
Revision 4
STUDENT NOTES:
Administrator Rights
To check if you have admin rights on your PC, which are required for installation, updates and tweaks
required by electrical service engineers:
 Access the Windows control panel and select ‘User Accounts’.
 Click on ‘Manage User Accounts’ and ensure there is an entry in the list which matches your network
login on domain NOV and a member of the Administrators group.
 It is also wise at this stage to ensure that you also change the ‘User Account Control Settings’ to Never
Notify. This is also done from within the ‘User Accounts’ section.
 If this is not the case then please contact IT to arrange admin rights.
Windows Explorer
To find required folders and prevent issues with file extensions some settings have to be adjusted in
Windows Explorer. This needs to be done in W7 and XP VM.
 Open Windows Explorer e.g. My Documents.
 From the menu at the top of the window select Organise…Folder and Search Option
 Click on the View tab.
 Select the radio button for ‘Show hidden files, folders and drives’.
 Untick ‘Hide extensions for known file types’ (required for id.txt file when working with SBCs)
 Optional is unticking ‘Hide protected operating system files’. Sometimes need to poke around these if
there are unusual problems.
 Ok/Apply all.
Revision 4
STUDENT NOTES:
Java
When referring to ‘Java’ in relation to an FST laptop we typically mean the JRE (explained on next page).
Java is a programming language expressly designed for use in the distributed environment of the Internet.
It was designed to have the "look and feel" of the C++ language, but it is simpler to use than C++ and
enforces an object-oriented programming model. Java can be used to create complete applications that
may run on a single computer or be distributed among servers and clients in a network. It can also be
used to build a small application module or applet for use as part of a Web page. Applets make it possible
for a Web page user to interact with the page.
The major characteristics of Java are:

 The programs you create are portable in a network. (See portability.) Your source program is compiled
into what Java calls bytecode, which can be run anywhere in a network on a server or client that has a
Java virtual machine. The Java virtual machine interprets the bytecode into code that will run on the
real computer hardware. This means that individual computer platform differences such as instruction
lengths can be recognized and accommodated locally just as the program is being executed. Platform-
specific versions of your program are no longer needed.
 The code is robust, here meaning that, unlike programs written in C++ and perhaps some other
languages, the Java objects can contain no references to data external to themselves or other known
objects. This ensures that an instruction cannot contain the address of data storage in another
application or in the operating system itself, either of which would cause the program and perhaps
the operating system itself to terminate or "crash." The Java virtual machine makes a number of
checks on each object to ensure integrity.
 Java is object-oriented, which means that, among other characteristics, an object can take advantage
of being part of a class of objects and inherit code that is common to the class. Objects are thought of
Revision 4
as "nouns" that a user might relate to rather than the traditional procedural "verbs." A method can be
thought of as one of the object's capabilities or behaviors.
 In addition to being executed at the client rather than the server, a Java applet has other
characteristics designed to make it run fast.
 Relative to C++, Java is easier to learn. (However, it is not a language you'll pick up in an evening!)
Java was introduced by Sun Microsystems in 1995 and instantly created a new sense of the interactive
possibilities of the Web. Almost all major operating system developers (IBM, Microsoft, and others) have
added Java compilers as part of their product offerings.
The Java virtual machine includes an optional just-in-time compiler that dynamically compiles bytecode
into executable code as an alternative to interpreting one bytecode instruction at a time. In many cases,
the dynamic JIT compilation is faster than the virtual machine interpretation.
JavaScript should not be confused with Java. JavaScript, which originated at Netscape, is interpreted at a
higher level, is easier to learn than Java, but lacks some of the portability of Java and the speed of
bytecode. Because Java applets will run on almost any operating system without requiring recompilation
and because Java has no operating system-unique extensions or variations, Java is generally regarded as
the most strategic language in which to develop applications for the Web. (However, JavaScript can be
useful for very small applications that run on the Web client or server.)
http://searchsoa.techtarget.com/definition/Java
Revision 4
STUDENT NOTES:
Java Versions
In order to view the output of Java code it is necessary to have a Java Runtime Environment (JRE)
installed. The JRE is a software distribution containing a stand-alone Java VM (Virtual Machine), browser
plugin, Java standard libraries and a configuration tool.
When referring to ‘Java’ in relation to an FST laptop we typically mean the JRE. Note that the JRE files and
documentation refer to 32 bit version. 64 bit may work but are not covered/supported.
For many years Java 1.4.2_13 and 6u16 were the standard versions used. Installation of these is
straightforward i.e. run the exe and follow prompts. Following installation carry out the Java settings
checks described later in section 0.
These versions can be obtained/downloaded from RigDoc - Reference 80769930
Or
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase14-
419411.html#j2re-1.4.2_13-oth-JPR for JRE 1.4.2_13
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-
419409.html#jre-6u16-oth-JPR for JRE 6u16.
Installation Document - PC Settings for SBC/Amphion Use
Software Versions
Revision 4
 j2re-1_4_2_13-windows-i586-p
 jre-6u16-windows-i586
Revision 4
STUDENT NOTES:
Follow the steps below to install Java 8u25. It is recommended that the previous version installation files
(j2re-1_4_2_13-windows-i586-p.exe and jre-6u16-windows-i586.exe) are copied across to your laptop in
case issues are encountered – these versions have worked in the field for many years.
8u25 can be obtained/downloaded from RigDoc - Reference 80769930
Or
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Installation Document - PC Settings for SBC/Amphion Use
Software Version
 jre-8u25-windows-i586
 8u25.zip contains exception.sites and java.security files
Ensure all other versions of Java are removed (see section 3.4.3 for how to check versions).
Install Java 8u25 (see section 3.4.3 for how to check versions).
Copy the file exception.sites (available in the same RigDoc entry as this document) to
C:\Users\yourusername\AppData\LocalLow\Sun\Java\Deployment\security. This contains a list of
commonly used IP address ranges used on SBC/Amphion systems and prevents error messages. If you
come across a range that is not listed please inform tech support who will update the master copy.
Revision 4
Copy the file java.security (available in the same RigDoc entry as this document) to C:\Program
Files(x86)\Java\jre1.8.025\lib\security.
Revision 4
STUDENT NOTES:
Reference document 80769930 – PC Settings for SBC/Amphion Use

Revision 4
Browser
Revision 4
STUDENT NOTES:
Chrome should not be installed or used as an alternative browser!
IE11 32bit and Mozilla Firefox are the only recommended installs, IE11 64bit may cause issues with Debug
Monitor and other functions.
The latest IE11 install seems to switch automatically between 32 and 64bit as required.
Revision 4
STUDENT NOTES:
Browser Settings
Reference document 80769930 – PC Settings for SBC/Amphion Use – Section Browser section
Revision 4
IP Connection
Revision 4
STUDENT NOTES:
IP Connection
Reference document 80769930 – PC Settings for SBC/Amphion Use – PC IP address section
Revision 4
Firewall
Revision 4
STUDENT NOTES:
Firewall
Reference document 80769930 – PC Settings for SBC/Amphion Use – Firewall Profiles and Exceptions
sections
Revision 4
STUDENT NOTES:
Revision 4
Revision 4
Revision 4
Compact Flash Structure, Creation, and Backup

Revision 4
Revision 4
Amphion Software Components

Revision 4
STUDENT NOTES:
Amphion Software Components

Firmware components are the base software packages that exist on all AMPHION SBCs. On a typical
AMPHION installation, the firmware component versions will be consistent across all AMPHION SBCs on
the rig.
The collective firmware on an SBC is known as the Golden Image. This consists of four separate elements:
the platform, the base layout, the controller, and the WWW. The Golden Image also contains a partition
structure that allows the system to boot. Although a Golden Image contains a full set of AMPHION
firmware, the firmware on the Golden Image may not match the firmware assigned to a particular rig
installation. Consequently, installation of different firmware packages on an existing Golden Image
could be required. The engineering specified firmware and Golden Image versions for a particular rig can
be found on the Software Product Server (SPS). Use of the SPS will be demonstrated on the next page.
The components of the Golden Image break down as follows:
Golden Image
Firmware
A complete AMPHION tool consists of the Golden Image plus the Tool Identity, or varball. A varball is a
compressed file set that contains the “personality” of a given controller, outfitting that controller to work
with a specific tool or tools.
The Tool Identity contains task specific code and configurations. The varball is unique to each SBC.
Revision 4
STUDENT NOTES:
Platform
The Operating System and lower level driver interfaces (platform_version.tar.gz).
Revision 4
STUDENT NOTES:
Base Layout
The file system and start-up scripts (baselayout_version.tar.gz).
Revision 4
STUDENT NOTES:
Controller
The Java parent classes for communications protocols, alarming, logging, and tools
(controller_version.tar.gz).
Revision 4
STUDENT NOTES:
WWW
The Java parent classes for the user interface, HMI communication, diagnostics, and screen navigation
(www_version.tar.gz).
Revision 4
STUDENT NOTES:
Varball
The varball consists of:
 Application Code: Utilizes the Controller to execute logic and update communications
 Configuration Files: Allows generic code to be utilized for multiple purposes
 Persistent Value Files (objects.csv): Allows data to be persisted through a reboot of the SBC
 Screen Descriptor Files: An XML description of the screen function used by the WWW
 Version Information: The firmware versions installed on the AMPHION SBC
Resource - https://wiki.nov.com/display/AM/The+Amphion+System
Revision 4
NOV Software Product Server

Revision 4
STUDENT NOTES:
NOV Software Product Server

A central location exists to store engineering released varballs, field varball backups, and rig firmware
version information at the NOV Software Product Server (http://sps.nov.com/app). Installations organized
by customer and rig names are created in the Software Product Server by engineering prior to release of
software. On a go forward basis, the SHP job number will also be included as rig identifiers to help
manufacturing personnel identify the correct software. Each rig added to the server will require firmware
versions to be selected by engineering and download links to the firmware versions will be provided on
the rig page for easy access. Varball backups loaded to the server will be checked against the firmware
assigned to the rig and errors will be shown for each varball with an incorrect version.
The SHP (Sam Houston Parkway) job number is the unique number associated with the manufacture of
the SBC/Amphion control panel and/or drive house.
Revision 4
STUDENT NOTES:
Accessed via the Documentation link on SPS home page
Versioning Roles and Responsibilities

Every person – whether one who develops software, screens, and configurations; one who deploys
software components to the field; or one who changes a machine’s configurations through setup routines
and changes through the debug monitor – everyone is responsible for ensuring that:
 The fielded AMPHION system’s firmware EXACTLY match those versions specified on the NOV
Software Product Server.
 The firmware versions on all AMPHION SBCs installed on the rig are consistent.
 New varballs are generated on every fielded controller whenever a machine’s configuration is
changed, or another field component modification is performed. These generated varballs must be
uploaded and submitted to the Software Product Server.
NOV AMPHION Platform Group

The Platform Development Group is responsible for creation and support of the firmware versions,
installation mechanisms, backup and restore features, and Software Product Server.
NOV AMPHION Applications Group

The Applications Group is responsible for creating new rig projects in the Software Product Server. The rig
creation process includes defining the firmware packages required and releasing the initial varballs for
each tool. The firmware used for the rig creation will be either the latest released firmware or the
firmware set of a sister rig for fleet version consistency. Software upgrades/changes should be
accompanied by software change documentation.
Revision 4
NOV Manufacturing Group

The NOV Manufacturing Group is responsible for loading the engineering specified software versions onto
AMPHION SBCs for each rig project. The engineering specified versions are accessible through the
Software Product Server for viewing and download.
NOV Service/Installation and Commissioning

The Service/Installation and Commissioning Groups are responsible for creating new varball backups of
the fielded AMPHION SBCs and posting those varballs to the server. They are also responsible for running
a consistency check of the firmware versions installed on the rig each visit. If an installed firmware version
does not match the engineering specified version, the AMPHION Applications Group should be contacted
for approval to modify the AMPHION SBC to the engineering specified version.
When creating or restoring an AMPHION SBC, the Golden Image and firmware versions specified by
engineering for that rig should be used.
Reference Documentation
D4B1004329-PRO-001 – Registration and usage of the Amphion Software Product Server
NOV Service/Installation and Commissioning Role and Responsibilities -
http://sps.nov.com/docs/wiki_platform_overview/profile/?uuid=6
Revision 4
STUDENT NOTES:
Firmware
Individual pieces of Firmware, Golden Images or HMI Images can be selected from the ‘Products’ tab on
the LHS or the ‘Products’ dropdown menu.
Navigate to the correct version/s.
The Configuration tab shows (limited) information regarding the associated sub-topic.
The Portal Management has some miscellaneous links to a video and web-pages.
Revision 4
STUDENT NOTES:
BaseLayouts
Selecting BaseLayouts will take you to this screen. The name, description and details of last modification,
including ID are shown.
Navigate to a specific version by selecting BaseLayout 1.2, for example

Revision 4
STUDENT NOTES:
This will take you to a screen where the name, description (in greater detail) and date modified fields are
shown.
Navigate to a specific version by selecting 1.2.5, for example

Revision 4
STUDENT NOTES:
Steps:
From here screen you can download the individual piece of Firmware:
 Select ‘Download’ (blue-pill beside ‘Uploaded File’).
Note: You will be asked if you want to ‘open’ or ‘save.’
 Select ‘save as,’ then navigate to a folder or location where you wish to save.
Note: The selected file will download and appear in that location
Note: The process is repeated for each individual ‘Product’ Controllers, Platforms and WWWs. Data
Logging and Win2Flash are empty
Revision 4
STUDENT NOTES:
To Identify which GoldenImage is correct, we first need to identify the Firmware with which a Varball has
been created.
How do we identify these versions?

Revision 4
STUDENT NOTES:
Golden Image Identification

From the Applications side of SPS (described in detail later) we can also find Varballs and Firmware
associated with a particular Customer, Rig and Tool
Steps:
 Select Customer from drop down menu or tab on LHS
 Select Rig
 Finally select the individual Tool
The example shown is for Ensco E120 Top_Drive.
Varballs – Name, Description, Firmware, Date Created and Date Modified information is shown –
Information sometimes not available.
In particular we are interested in the Firmware versions used to create the particular varball (Controller
3.7.3.1_3812_tag-3.7.3.1, Baselayout 1.2.1 and www v1_7_4). We now need to identify the versions of
Firmware on a particular Golden Image to identify if it correct.
Amphion Platform Software – You can (sometimes) download all the Firmware and Golden Image by
selecting the Download link, this doesn’t always work though as the files aren’t always compiled in this
useful location.
The file size for E120 is 109MB and when downloaded will contain all the mentioned files (if the file size is
around 10KB you will be downloading an empty folder).
Revision 4
If the platform download link is not available or does not work then it may be necessary to manually
download the files from the firmware side of SPS. If the required revisions are not available on SPS then
contact technical support.
Revision 4
STUDENT NOTES:
Software versions can also be identified via the Service Pages (we will discuss later in course)
Varball file – WWW/Build.properties
Using the Software Versions and Transfer Files links, it is useful to have this information and files (Varball
etc.…) before you leave for a job, internet access may be restricted or poor limiting your access to SPS and
file downloads.
Revision 4
STUDENT NOTES:
With the Firmware versions noted (screen dump or other) navigate back to the Firmware Application and
then the GoldenImages. Open the various folders and compare the versions of Firmware used with a
particular GoldenImage to those previously noted.
The Firmware revision used on the GoldenImage should be equal to or lower than the version used to
create the Varball (it is preferable to upgrade the Firmware rather than try to downgrade).
Using this method the correct GoldenImage is Hercules 7.2 – Amphion Image 1201:
 Controller version is the same.
 www is a lower revision, Hercules 7.3.1 would take us beyond our required version and mean
downgrading the Firmware.
 BaseLayout is a lower revision, Hercules 7.3.1 would take us beyond our required version and mean
downgrading the Firmware.
Revision 4
STUDENT NOTES:
HMI’s
HMI Images can be downloaded according to the brand/version number of the associated device.
Select the ‘blue’ name on several screens to ultimately reach a screen showing detailed ‘Product
Information’ and containing a link (Blue-pill/Download) to download a copy of the image.
Revision 4
STUDENT NOTES:
Applications Portal
The Applications portal requires a separate registration and the username and password can be the same
as used for the Firmware portal.
Applications
Can be used to view/download Varballs or Firmware associated with a particular Rig or Customer:
 Select a Customer via the drop down menu or the link on the LHS.
 Select a Rig via the drop down menu or the link on the LHS.
 Select a Tool from the drop down menu.
Revision 4
STUDENT NOTES:
Product Information
Populated with information relating to that particular tool
Varballs – May not appear in correct order! Check date stamp and also revision number to confirm
correct version.
 Locate the Varball you are required to download.
Note: All of the Varballs for a specific Customer, Rig and Tool will be stored as shown in the figure below.
The comments box on the right will display the version of the controller, www and base layout that was
used to create the Varball as well as the user who uploaded the Varball on the server.
 Click on the “Download” link above the Varball name.

 Save the Varball in a desired location in your hard drive (i.e. Documents)
Note: Remember that the file extension should be “.tar.gz” as shown in the example below.
Note: Be aware that the browser is known to change the file extension from ‘‘.tgz’’ or “.tar.gz” on
download. ‘‘.tgz’’ and ‘‘.tar.gz’’ are the recognised file extensions
Amphion Platform Software

You can (sometimes) download all the Firmware and Golden Image by selecting the Download link, this
doesn’t always work though as the files aren’t always compiled in this useful location!
The file size for E120 is 109MB and when downloaded will contain all the mentioned files (if the file size is
around 10KB you will be downloading an empty folder).
Revision 4
Note: This will not include a Varball, if the platform download link is not available or does not work then
it may be necessary to manually download the files from the firmware side of SPS. If the required
revisions are not available on SPS then contact technical support.
Subscriptions
You can subscribe to a particular Rig or Varball by selecting the ‘subscribe’ link receive email notification
when a new revision is released/uploaded.
Revision 4
STUDENT NOTES:
Upload/Add New Varball

Varball to be uploaded should be downloaded from the rig and stored in your computer’s hard drive.
To perform the SPS upload procedure, the desired Customer, Rig and Tool should exist in the drop down
list as shown. Please contact the supervisor/tech support if any of those fields need to be created.
Procedure
 Select desired Customer, Rig and Tool.
 Click the “Add New” button to start adding new Varball.
 You will be directed to the “Add New Varball” page.
Note: a varball filename or extension should never be changed as it indicates customer, rig, tool and
revision. ‘‘.tgz’’ and ‘‘.tar.gz’’ the recognised file extensions
Revision 4
STUDENT NOTES:
After browsing to and selecting the Varball on the PC the File and Name fields populate with the Varball
name information.
The Description field is required and it is recommended to add a brief description of the Varball’s origin
and related information (e.g. software change document reference, Tracker ticket, job pack number etc.).
Click on the ‘Submit’ button.
You have successfully uploaded a new Varball to the rig.
Note: The warning sign will be shown under exceptions if the firmware versions listed in the description
do not match the firmware versions listed on the SPS for the rig. If the versions do not match, please take
a screen shot of the consistency checker from the rig and contact Amphion engineering.
Revision 4
STUDENT NOTES:
Configuration and Portal Management

These tabs contain limited information
Keyword Search
Can be used to locate a Rig using another name or ID (previous names for example).
Details of previous names can be found using methods discussed in presentation 3.2 - Documentation
B329 is the hull number used to identify the Ensco 120 when it was manufactured in Singapore.
Revision 4
Creating a Compact Flash

Revision 4
STUDENT NOTES:
Compact Flash
Compact Flash (CF) cards should be NOV supplied as these are of industrial standard (increased life/
read/write cycles). Sizes vary from 128mb on early bricks to 16Gb for the Beckhoff with data logging
enabled. Ideally replace like for like in terms of size as hardware and firmware may not function with
certain sizes.
If reusing a CF it may be necessary to delete partitions and format the CF so that the full size is recognised
by the PC, prior to burning the golden image. Sometimes deletion of partitions can be done using
Windows, otherwise source a freeware partition removal tool online.
The SBC CF structure consists of two Linux partitions and a Windows partition. In the Windows partition
are typically some Linux based tools and the version of Win2Flash (<V2.0) appropriate for the golden
image firmware.
Win2Flash V2.0
Reference Document D4B1004331-PRO-001
Prior to Win2Flash V2.0 two separate applications were provided for creating a CF. FlashImager was/is
used to burn the golden image to the CF; Win2Flash (<V2.0) was/is then used to interrogate the card
(firmware versions, varball) and transfer firmware files and varballs for installation on first boot. These
features are now integrated in Win2Flash V2.0.
Win2Flash-v2.0 is a NOV windows application that is used for burning Amphion images to removable
storage media such as Compact Flash (CF) cards, CFast and USB devices. The application provides a more
efficient way of creating images by providing a central place for accomplishing several tasks. Tasks that
Revision 4
were previously done by using multiple applications, like downloading varballs, burning golden images to
flash drives and copying varballs to Amphion images etc., can now be accomplished using just Win2Flash-
v2.0.
You can use the application to:
 View information about Amphion images on storage media.
 Burn Amphion golden image or any disk image of type img, img.gz, dsk and dsk.gz to a flash drive.
 Create Amphion image by using Win2Flash-v2.0 to automatically download and copy golden image,
firmware files and varballs to a flash drive.
 Use SHP job number to locate, download and burn appropriate Amphion image.
 Copy tar.gz/tgz archives to a flash drive containing Amphion Images.
Revision 4
STUDENT NOTES:
Ghost 3FIP00286
Reference Document 3FIP00286
This was used to create backup images of SBC CF and to write images to the CF before golden images,
firmware components and varballs were available. It is not used now though some of the only backups for
early SBCs exist in this format. It requires Windows ME/NT and a 3.5” floppy drive.
Imaging is not the preferred method of creating or backing up CF cards where it possible to create them
from an NOV golden image, firmware and varball.
Ghost (general hardware-oriented system transfer)

Is a disk cloning and backup tool originally developed by Murray Haszard in 1995 for Binary Research.
Ghost 7.5
Released December 14, 2001, Ghost 7.5 creates a virtual partition, a DOS partition which actually exists as
a file within a normal Windows file system.
Source - https://en.wikipedia.org/wiki/Ghost_%28software%29
Revision 4
STUDENT NOTES:
R-Linux
Reference Document 92654476
R-Linux was used in a similar way to Ghost but was easier to use and is compatible with later Windows
operating systems and USB card readers.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS file system used in the Linux OS and several
Unixes.
There are two variants of R-Linux: one is for Linux, the other is for Windows. They are the same in their
features, and differ only in their host OS.
Source - http://www.r-tt.com/free_linux_recovery/
Revision 4
STUDENT NOTES:
SelfImage
Reference Document 92654703
SelfImage was used in a similar way to R-Linux but was easier to use and is compatible with later Windows
operating systems and USB card readers.
SelfImage is capable of making an image of a hard disk partition and writing it to another - useful for
making backups. Use SelfImage to create a disk image of any partition and even partitions that Windows
does not recognize (Linux partitions, etc.).
Source - http://www.majorgeeks.com/files/details/selfimage.html
Revision 4
Testing Compact Flash in SBC

Revision 4
STUDENT NOTES:
Safety
 Documentation (provided with upgrades) should be followed explicitly, but not blindly.
 If in doubt, stop and ask the question. (Clarification should be sought before commencing any sort of
modification or upgrade)
 Ensure correct tool function, correct software versions have been installed/backed up.
 Suitable detail on procedures should be shown in reports for traceability.
Compact Flash
it is controlling a tool or communicating with other devices on the network.
External Keyboard, Mouse and Monitor

IP Address
Two computers on the same network cannot have the same IP address. Make sure the IP address for your
computer is not already in use.
Revision 4
Installing Files/Upgrading Firmware

Selecting “This Controller Only” installs software only to the currently-selected tool. Selecting “All
Controllers” installs software to all tool controllers listed in the current ownership.xml file. Use proper
lock and “tag out” procedures before implementing.
VDAQ/MSI
Ensure VDAQ/MSI tool controllers are disconnected from network when applying a network-wide
firmware upgrade; the files contained on VDAQ/MSI are unique and should not be modified as per other
tools
Revision 4
STUDENT NOTES:
Do’s and Don'ts

Test back-ups when created, don’t assume good.
Ensure back-ups are added to SPS and customer systems, where applicable.
Use spare flash cards, don’t overwrite running copies.
Revision 4
STUDENT NOTES:
Revision 4
STUDENT NOTES:
Revision 4
Revision 4
Revision 4
Revision 4
Revision 4
STUDENT NOTES:
Upon lesson completion, course participants will be able to utilize the basic functions of SBC service pages
for troubleshooting using a Flares Main page under instruction by being able to:
Describe the basic navigation for both White and Flare main pages.
Verifying the IP addresses against topology and communication status.
Verifying and modifying firmware and application versions.
Collect information from SBC diagnostics to interpret and modify values by given instructions.
Verifying firmware and files across Amphion network.
Demonstrate safely the correct process for shutting down or restarting a SBC and special functions that
affect operation.
Revision 4
Main Page
Revision 4
STUDENT NOTES:
White Main Page
Warning - Not all ‘are you sure’ prompts are present in earlier firmware revisions. Exercise caution on
SBCs with early firmware revisions.
Initially SBC service pages were as shown above, with a predominantly white background. After the
introduction of the ‘flares’ background, the older versions became known as ‘white page’ SBCs.
General
Contains links to advanced diagnostic screens.
Setup
Contains links to the SBC operator screen setup, tool calibration, and the configuration of other tool
parameters.
Documentation
Contains links to NOV Technical Support telephone numbers and technical documentation. In addition,
this section provides a link to the State Diagrams, a form of interactive documentation used to debug tool
problems.
Note: state diagrams are not up to date and should not be relied upon.
Note: telephone numbers and documentation are not maintained so should not be relied upon.
Revision 4
Alarms & Events

Contains links to alarm and event status screens primarily for use by maintenance personnel.
Also contains a link to the Trigger Editor, which provides a way for the technician to define conditions that
trigger alarms and events.
Diagnostics
Contains links to I/O and Communication Status screens.
Other Tools
Contains links to other tools on the rig network controlled by the SBC.
Reference Document – SM00998 and RevB

Revision 4
STUDENT NOTES:
Flares Main Page

Note that the manual was released in conjunction with www 1.6.0 in 2009.
Main Service Page

Type the appropriate tool controller’s IP address into your Web browser’s address field to connect to the
tool controller interface.
Click the IP Network link located on the left side of the page to display a grouped list of devices connected
to the network.
After selecting a link, click the Contents link to return to main service page.
You can also use the Back or Forward buttons in your browser to navigate between pages.
IP Network
Contains links and information about devices connected to the rig network, including IP address
assignments, communication status information, and IP configuration options.
See Chapter 4, titled "Network Links” for more information.
Software Management
Contains links to software version information and software installer and file transfer utilities (normally
used by rig technicians and software engineers).
See Chapter 5, titled "Software Management Links” for more information.
Revision 4
Diagnostics
Contains links to I/O and other communication status screens. Also contains a link to axis controllers and
state diagrams (where applicable), which are interactive documents used to debug tool problems. See the
following chapters in this manual for more information:
 Chapter 6, titled "Debug Monitor”
 Chapter 7, titled "I/O Diagnostics”
 Chapter 8, titled "Scheduler Diagnostics”
 Chapter 9, titled "Controller-to-Controller (C2C) Status”
 Chapter 10, titled "Cyberbase Status”
 Chapter 11, titled "Modbus Status”
 Chapter 12, titled "Profibus Network Status”
 Chapter 13, titled "Step 7 Status”
 Chapter 14, titled "State Diagrams”
 Chapter 15, titled "Axis Controller”
 Chapter 16, titled "Download Alarms”
Configuration
This section contains links to the following modules. See the appropriately-titled chapter for additional
information.
 Operator Screen Configuration
 Service Pages Configuration
 Ownership Configuration
 Simulation Control
 Array Manipulator
 Trigger Editor
 Consistency Checker
 Set Date and Time
 Path Editor
 Set IP Address on Network Device
Controller Links
Contains the Java Virtual Machine (JVM) status and restart controls, the current tool controller’s status,
halt, start, and restart controls, and Applicom card flash controls. Also contains a link to the current tool
controller’s log manager files, the operator’s drilling control touchscreen interface, and other NOV
technical documentation.
 See the rig-specific Amphion operator’s guide for information about the operator’s drilling control
(touchscreen) software interface.
 See Chapter 27, titled "Controller Links.”
Revision 4
New Additions
Software Manager, introduced with www_v1.7.0, does exactly what the name implies; it permits you to
view, backup, restore, update and otherwise manage all the software on every tool on the rig (except
VDAQ/MSI).
Preferences are new with www 1.7.0. It replaces the ownership file (ownership.xml is retained as a fall-
back in case preferences.obj should be missing or corrupt.)
Reference Document – D811001117-MAN-001

Revision 4
STUDENT NOTES:
Topics covered at Level 0 and 1

Revision 4
IP Network
Revision 4
STUDENT NOTES:
Devices and Navigation

Press IP Network to access the IP Network tools
Clicking on IP Network will drop down a menu with three panes. The top pane lists categories of devices
connected to the Amphion network, the second pane is for managing the address list and the third has a
couple of handy utilities.
Navigate the cursor to select a group and display a list of all known devices connected to the network
within that group.
Highlight NOV Tool Controllers, which shows a list of all Tool Controllers. Select one of the controllers in
the list to navigate to that controller.
Notice that the list shows each device in one of three colors.
When you first connect to any Tool Controller, it pings every other device on the network (every device
listed in ip_list.xml); the colors show the result of the ping:
 Black – If the ping is successful, the text display is black, and no status message appears.
 Red/Grey (firmware dependent) – Devices that do not respond to a ping display in red, along with an
“unresponsive to ping” status message.
 Orange/Yellow – If the network links system is still attempting to communicate with a device the text
displays in yellow, and the message “not yet tested” displays next to its name
Close and reopen the menu to refresh the ping status message displays
Revision 4
STUDENT NOTES:
Edit Address List
Warning – Don’t adjust/modify parameters/values while any tools are running. At level 0 this should
only be done when instructed.
The device names and their IP addresses are stored in a file called ip_list.xml
Revision 4
STUDENT NOTES:
Show or Hide IP Addresses

Click IP Network --> Show IP Addresses or Hide IP Addresses toggle menu command to display or hide
the assigned network device IP addresses.
Click the toggle menu command again to show or hide the IP address information.
Revision 4
STUDENT NOTES:
Investigate Address
Use the address investigator to evaluate the communication status of devices connected to the network
using the ping command, then (if successful) attempts to make an HTTP connection.
Click IP Network > Investigate Address, then type an IP address into the space provided.
Click OK to begin the investigation

Revision 4
STUDENT NOTES:
Older firmware revisions will show the pinging of the address four times before trying the HTTP
connection; the newest firmware revision skips that and displays the result.
 In the top (left) window, Address of the Drawworks controller. If the device responds to the ping
request, the system then attempts to make an HTTP connection. If the device responds with its name,
the device is likely an NOV tool controller.
 In the centre window, Address of user laptop. If the HTTP request returns error code 404 (file not
found), the system attempts to locate the device’s default web page. I/O devices and network
switches have their own Web servers, whereas an HMI or Laptop does not.
 In the bottom window, Address that isn’t being used or is offline
Revision 4
STUDENT NOTES:
Revision 4
Software Management
Revision 4
STUDENT NOTES:
Restricted Functions
Several functions within the Service Pages require an administrator password. Only trained, qualified
personnel should install or update tool controller software.
An administrative password is required the first time the user attempts to access a restricted function. A
password is not required again unless the browser is closed and restarted.
Type the password into the space provided (admin – all lowercase), then click Log In to continue.
Revision 4
STUDENT NOTES:
Software Versions
Software Versions displays the versions along with date compiled and other data about the software on
the tool controller. The only part of this file that concerns us is the very bottom, where the www, base
layout and controller and platform versions are shown.
Click Show Details to display additional information (LHS), such as software versions and error messages.
Beginning with www-v1.7.0 Software Versions looks like this (RHS). Only the Operating System, Java
version and the three Firmware types are listed; all the other information that would be of interest only
to programmers is now gathered in the two folders.
Revision 4
STUDENT NOTES:
Backup and Restore
Warning – Don’t adjust/modify parameters/values while tool is running.
Warning – Disk space available should be checked prior to using the page. Using page functions with low
disk space will almost certainly result in corruption of the CF.
Warning – Varballs from different tools and/or rigs should never be loaded onto an SBC. The only time
you should see various tools on one SBC is if it is a virtual SBC on a PC for testing/training.
From Backup and Restore we can back up the varball to our local hard drive, copy and install a varball
from a hard drive to the SBC and create a new varball based on what is currently running on the SBC.
Warning!!!! Do not Install or Create New Personality Archive while the tool is running! The ability to
maintain safe control of the tool may be degraded when creating or installing a personality archive. Ensure
that proper lock and tag-out procedures are followed when working on energized equipment. Failure to
follow safe work procedures could result in serious or fatal injury to personnel, significant equipment
damage, or extended rig downtime.
SBCs should only have varballs for that tool uploaded to it. The only time you should see various tools on
one SBC is if it is a virtual SBC on a PC for testing/training.
 To upload a new varball to the tool, first press Browse.
 A file selection window will open. Navigate to the location of the varball you want to upload and
double-click it or highlight it and press Open.
Revision 4
STUDENT NOTES:
 You’ll see the file path and name in the text box. Press Upload Varball
Revision 4
STUDENT NOTES:
Press Delete to delete a varball.
 As a general rule, it’s probably not a good idea to keep more than the current varball and one version
back (in case you need to revert). More than that not only takes up disk space but can be confusing.
 The screen will switch to Confirm: delete
 Be sure it’s what you want to do, the press Yes, Delete. (No, Cancel if you picked the wrong file or
change your mind.)
 Copies of any ‘extraneous’ varballs should be taken prior to deletion and uploaded to SPS if not
already present
Revision 4
STUDENT NOTES:
Press Download to copy a varball to your hard disk.
 In Amphion UP is always from you to the system, DOWN is always from the system to you.
 Press Save As on the File Download dialog.
 Navigate to the location where you want the file in the Save As dialog, then press Save.
Revision 4
STUDENT NOTES:
Uploading a varball to a controller only copies a file from your laptop hard drive to the controller’s
compact flash drive. It has no effect on operation. For the new varball to take control, it must be installed.
 Press Install next to the varball you want to install (presumably the new one unless you need to return
to a previous version).
 Install will de-compress the file, place each file within it in its proper location in the directory
structure, then reboot the controller so that it will come up running under the new varball.
 Note again the Warning!
 When it asks you “Is this what you want to do?”, if you’re sure, press Yes, install (caution on SBCs
with early firmware revisions may not apply)
 This list of files (there is more below) is confirmation that you’ve successfully installed the varball.
Revision 4
STUDENT NOTES:
Create New Personality Archive will copy all the personality files into a new archive and compress it,
creating a new varball. It does not download the varball to your laptop.
As before, Note the Warning.
 It firsts asks if you want to save the information in memory to persistent storage. As the whole reason
for creating a new varball is to capture and back up changes, it must be very rare that you would want
to answer No.
 Press Yes, save
Note the confirmation message at the top. (This is new with www_v1.7.0)
 Message usually appears quickly but can sometimes take between 10-15 seconds.
 Remember that the varballs are not always shown in order; so check the version number before
downloading or you’ll wind up with an old one on your backup.
Revision 4
STUDENT NOTES:
Click here to download varballs from multiple controllers at one time is something customers have
wanted for some time and we finally got it in www_v1.7.0.
Warning: Varballs should not be created while the tool is running. Using functions like this which affect
multiple SBCs should only be used by experienced personnel or in I&C /yard stay situations where all
tools are not in use
 Click on it to do exactly what it says

 Check the box next to any controller you want save the varball from. (The example only shows one
controller online, in reality you will have multiple)
 If you want to create new varballs to download, leave the Yes radio button selected (remember the
warning!)
 If you want to download existing varballs without saving persistent data, select No.
 Check them all and leave Yes selected.
 Press Download.
 Navigate to the folder where you want the varballs and press Save.
 Monitoring Progress will pop up to show you your progress.
 When completed, the progress bar will disappear and you’ll see all the varballs in the folder where
you saved them
Revision 4
STUDENT NOTES:
Software Installer
Warning – Don’t adjust/modify parameters/values while tool is running
The Software Installer permits upgrading specific software to this or all controllers.
To begin, select the type software to be installed from the drop-down listbox. The following steps indicate
how to install a new www.
Press Begin.
By default it will Purge previous installation (the option is new with www_v1.7.0 – previously it always
purged previous installation, i.e. removed all files associated with the existing version; you should
probably leave that alone) and operate on This Controller only.
 If you want to install software to all controllers, select the All Controllers radio button ( Warning:
functions like this which affect multiple SBCs should only be used by experienced personnel or in
I&C /yard stay situations where all tools are not in use.)
 Then Browse to pick the file to install from your hard drive
Revision 4
STUDENT NOTES:
 To install a new www to a controller, press Next (if all controller were selected be aware using
functions like this which affect multiple SBCs should only be used by experienced personnel or in
I&C /yard stay situations where all tools are not in use)
Note: This is going to take a few minutes
 Press Finish.
Note: VDAQ/SDAQ/MSI looks like an SBC but isn’t and will almost certainly contain different software
versions. Do not modify unless instructed. If rolling out changes across multiple tools ensure
VDAQ/SDAQ/MSI is not selected.
Revision 4
STUDENT NOTES:
Transfer Files
Warning – Don’t adjust/modify parameters/values while tool is running, Transfer file functions should
only be used under instruction – if inexperienced it is very easy to cause damage to the controller
files/folders which can result in the SBC crashing.
At the main service page, click the Transfer Files link to display the currently-selected controller’s File
Transfer page
Navigate to /varco directory

Select Show parent directory to navigate from /varco/data/persistent to /varco/data, select Show parent
directory again to navigate to /varco directory
To drill down through the folder structure click on the folder name (blue and underlined) in the name
column.
Transfer files was useful prior to the introduction of varball functionality; prior to that individual files
would be sent to/from the software department for updates.
Revision 4
Uploading Files to the Tool Controller

1. Click the Browse button to locate and select a file from your computer’s hard drive. The file displays in
the previously blank space to the right of the Upload File button.
2. Click Upload File to begin the process.
3. The uploaded filename displays at the bottom of the main Transfer Files page’s file list.
Tool Controller Files

Click the Show Parent Directory link to display the next-highest, or parent directory, of the currently-
selected directory.
 /varco/data
Click the Show Parent Directory link again to expand the directory.
 /varco
Revision 4
STUDENT NOTES:
Two directories are important to us:

 /varco/current, which contains the currently installed varball and other essential files;
 /varco/toinstall, where we can place any file we want installed (will install ‘‘.tar.gz’’ libraries e.g.
varballs and firmware but won’t work with single files e.g. objects.csv or applicom.zip).
 Current contains the controller, baselayout, www and varball files for this controller. It is the best
place from which to take backups to your hard drive because the files therein are copies of the ones
actually running. The controller, baselayout and www should be the same for all tools on the same rig,
so you need to copy them only once to your hard drive.
Click current
Backing Up Essential Files

To back up the baselayout, click on its name (not on modify file)
Use Windows File Manager to choose a location on your hard drive to store it. DO NOT rename the file in
order to avoid generating confusion later if you ever need to reinstall it. Navigate to your desired location
and press Save
Revision 4
STUDENT NOTES:
To Delete, Rename or Backup a file, press modify file next to the file name
 To delete the file, simply press Delete and answer Yes to the confirmation request
 To rename the file, type the new name in the text window next to Rename, then press Rename
 To back up a file (create a backup named *.bak in the same directory on the SBC), press Make Backup
(note that this does NOT back up the file to your hard drive)
Note: It is recommended that files are backed up and/or copied to laptop prior to deletion or
replacement and kept until changes have be verified as successful/no detrimental impact
Revision 4
STUDENT NOTES:
Click toInstall
Files to be installed should be copied into /varco/toInstall. (Use the same procedure as previously to go
up the tree to /varco, the click on toinstall) Press Browse to select the file to install
Select the file from Windows File Manager and press Open.
The file name will appear in the text window; press Upload File.
Revision 4
STUDENT NOTES:
A confirmation message will appear at the top left and the file will appear in the file list; to actually install
the file, return to Contents and Restart JVM.
Note: /toInstall will install ‘‘.tar.gz’’ libraries e.g. varballs and firmware but won’t work with single files
e.g. objects.csv or applicom.zip
Revision 4
STUDENT NOTES:
Quick Links
A group of links to commonly-used files display at the right hand side of the main File Transfer page.
Selecting a file will navigate to the location of the file
The file can be opened/saved by selecting from the list below name
Revision 4
STUDENT NOTES:
Warning: Don’t adjust/modify parameters/values while tool is running
Software Manager, introduced with www_v1.7.0, does exactly what the name implies; it permits you to
view, backup, restore, update and otherwise manage all the software on every tool on the rig (except
VDAQ/MSI). VDAQ/SDAQ/MSI looks like an SBC but is not and will almost certainly have different
versions. Don’t modify unless instructed. If rolling out changes across multiple tools ensure this tool is not
selected.
Notice the colors of the boxes.

When Software Manager is first invoked, the software in each controller is compared with that in the
“Master” (the controller from which it is invoked, in this case the Driller’s Chair) and the colors show the
results:
 Grey indicates software that is not expected to match; obviously, for instance, each Tool Controller
should have a different personality (the box will also be grey if the tool is offline)
 Green indicates a match
 Pink indicates a mismatch
 The buttons on the left – Download All, Install All, etc. – will be enabled only after Software Manager
has gathered the data from all the controllers. The progress bar at the bottom lists each controller as
its data is gathered (they are investigated and listed in alphabetical order) and indicates degree of
completion for the entire process.
Use the slider at the bottom to move across the page to see other tool controllers. The name of each
tool’s varball is on the button at the intersection of the tool’s column and the Personality row.
Select a ‘Personality’ and it opens up a page like this:

Revision 4
 Upload Personality Archive uploads a varball from your laptop to the Tool Controller; if Install after
Upload is checked, the varball will be installed as soon as it’s uploaded. If not, it will be copied to the
controller but not installed.
 Create New Personality Archive creates a new varball based on the current code and values. If
Download after Create is checked, the new varball will downloaded to your laptop automatically.
 Install, Download and Delete duplicates the functions of the same buttons in Backup/Restore and will
be discussed with that link.
 Warning: Install and Create Varball the ability to maintain safe control of the tool may be degraded
when creating or installing a personality archive. Ensure that proper lock and tag-out procedures are
followed when working on energized equipment. Failure to follow safe work procedures could result in
serious or fatal injury to personnel, significant equipment damage, or extended rig downtime. Do not
press either without first verifying that the tool is not in use. Review the warning on the
Backup/Restore page before using these buttons.
Download All opens the box for downloading all the varballs to your laptop at once with two options:
 Save Persistent Objects will rewrite the objects.csv and convertors.xml files to capture any changes
that have been made to persistent objects (will be discussed later)
 Create New Archives creates a new varball for each controller and download that to your laptop
 Select Set Options for Individual Controllers and press Set Options . . . to open the window on the
right and select those options for individual controllers.
 Warning: Install and Create Varball the ability to maintain safe control of the tool may be degraded
when creating or installing a personality archive. Ensure that proper lock and tag-out procedures are
followed when working on energized equipment. Failure to follow safe work procedures could result in
serious or fatal injury to personnel, significant equipment damage, or extended rig downtime. Do not
press either without first verifying that the tool is not in use. Review the warning on the
Backup/Restore page before using these buttons.
Warning: This combines several of the functions previously shown, however it can be easy to make
mistakes and should only be used by experienced personnel or in situations where no equipment is in use
e.g. I&C or yard stay. If using with multiple tools ensure network health is good otherwise corruption of
multiple tools can occur.
Revision 4
STUDENT NOTES:
Pressing any of the buttons in the blue highlighted area opens the Windows file-picker menu for you to
select a new version of that Firmware to upload to that controller.
Controller 3.7.3.1_3812_tag-3.7.3.1 (romized) selected, navigate to/select ‘correct’ firmware upgrade and
select open
A warning appear relating to the risk of installing Firmware while the tool is in operation
Install All does the same for all the controllers at once.
Revision 4
STUDENT NOTES:
Summary
Opens up this window showing the versions of all the files except ip_list.xml and ownership.xml.
Save to File
Opens a Windows file picker menu so you can save the data to a csv (comma-separated values, for
spreadsheets) file. The data is also put in your Windows system clipboard so you can paste it directly into
a text file or email.
The file can be saved/viewed as a text (.txt) or comma separated value (.csv) file
Revision 4
STUDENT NOTES:
Revision 4
Diagnostics
Revision 4
STUDENT NOTES:
Debug Monitor
Warning: Don’t adjust/modify parameters/values while tool is running/ Debug Monitor should only be
used when instructed.
Debug Monitor allows you to change values for items stored in the controller. Use extreme caution when
changing these values. Although some protections are built in, some changes may bypass safety
interlocks, allowing free movement of the tool, which can result in collisions, serious damage to
equipment, or serious or fatal injury to personnel. Use extreme caution
Debug Monitor is an advanced diagnostic and monitoring feature of the Amphion tool controller
interface. In addition to diagnosing problems and monitoring tool performance in real time, you can
change stored tool information, record, and graph tool performance data. It provides a way to display just
about every possible parameter stored on the controller.
An administrative password is required the first time the user attempts to access a restricted function
(admin, all lower case. A password is not required again unless the browser is closed and restarted.
To find a point or value, it is necessary to drill down the tree structure, clicking the + signs to open
branches
Locate the items you wish to monitor, and then click to select (The row will ‘highlight’ in black). Click again
to deselect if necessary
Click OK to display the next Debug Monitor screen.

Revision 4
Note that the values displayed are real-time and will update if they change.
Click Add Monitors to display the Chooser screen again if you wish to add items.
To remove items from the list, highlight, then click Remove.

Revision 4
STUDENT NOTES:
Enter the search phrase

The search window can be used to find points associated with that point
Information such as mts, which is used to identify a linear transducer (see Debug Abbreviations) or
buzzwords such as throttle or encoder can be used to narrow down search range
After information has been entered into field press Search
On later versions * can be used as a wildcard (similar to Teamcentre). Use count and count* as an
example
All points that appear on the list contain the buzzword

Revision 4
STUDENT NOTES:
Changing and Saving Values

Click the Edit button (items do not need to be highlighted).
Type a new value into the space provided, then press <Enter> to save the value, or press <Esc> to cancel
changes.
To change forceEnabled from F(alse) to T(rue), enter T in the text window and press the <enter> key on
your keyboard.
Now that forceEnabled is T, edit forceValue in the same manner to make it also T.
Note that value remains F even though we’ve forced the value to T; this is the case throughout the
Amphion system: whenever forceEnabled is T, Amphion will behave as if the forceValue is the actual value
but will still display the real value in the value line. This permits you to keep track of the real value even as
you fiddle with Amphion.
To end forcing, just edit forceEnabled to be F
If necessary, type the administrator’s password into the space provided (admin, all lower case), then click
OK to continue.
An alert message “Response is read only” displays if the user attempts to change a restricted item.
A persistent value remains stored in the tool controller after power to the tool and the controller are
turned off. The tool controller program uses those stored values as the initial item value upon start-up.
Revision 4
Click Save Objects to save all persistent values to the CompactFlash.
Type the administrator’s password into the space provided, then click OK.
A confirmation message displays.
Click anywhere on the screen to close the confirmation message.
Note: Forces will be cancelled if the controller is restarted

Revision 4
STUDENT NOTES:
Graphing an Object
The button to the left of Edit is the Graph button; it displays a graph just like the one shown.
Note that this is a live graph and will continually update.
As its value bumps the top or bottom of the chart its scale will adjust to keep it within the window.
The size of this graph is fixed and can’t be changed but you can move it.
As the box always opens at the top left of the screen, you’ll want to move the first one down if you’re
going to graph more than one object.
Revision 4
STUDENT NOTES:
The button to the right of Edit is the Record button. Pressing it highlights point to be recorded in red but
does not start recording.
Once any point is highlighted, the Start Recording button at the bottom will be enabled. To begin
recording, press Start Recording
Start Recording will be disabled and Stop Recording enabled. Unless you stop it by pressing Stop
Recording, recording will proceed for 40 seconds.
Up to 20 individual points can be recorded for up to 40 seconds (limits are lower in earlier versions, 10
items for 40secs)
Revision 4
STUDENT NOTES:
Recording and Graphing Data

As soon as recording is finished (or stopped by you), the Graph Viewer is displayed with graphs of all the
recorded points stacked.
The Graph Viewer can be closed and the recordings accessed again using the associated ‘button’ on the
right hand side, (‘Recording 1’, ‘2’ etc.…)
The recordings will be removed permanently if you navigate back to the main web page
From the Graph Viewer you can save the graphs for later viewing, save them as a CSV file for transfer to
Excel or another spread sheet, or load previously stored graphs.
*Only one person can record data from a controller at a time - controller.recording: Displays a Boolean
value, indicating whether the controller is recording data. Only one user can record data from the same
controller at any given time. Reference document D811001117-MAN-001 P80/298
**Reference document incorrectly indicates that ‘Twenty different parameters can be recorded at once,
lasting approximately 100 seconds’
Revision 4
STUDENT NOTES:
Saving Recorded Data

You can save recorded data in CSV format (comma-separated value, also called comma-delimited), which
can be opened and manipulated by other software, such as Microsoft® Excel.
At the Graph Viewer window, click File --> Save CSV File. Assign a name and location for the recorded
data, then click Save to confirm.
Click File --> Open CSV File, then click to select the appropriate file to display saved data in the Graph
Viewer window.
Revision 4
STUDENT NOTES:
I/O Diagnostics
Warning: Don’t adjust/modify parameters/values while tool is running/ forcing should only be done
under instruction. Rarely used on a working rig, but may be used during the I&C state or during an
upgrade.
Use extreme caution when forcing a value. Forcing a value bypasses safety interlocks, allowing free
movement of the tool. This can result in collisions and serious damage to equipment, or serious/fatal
injury to personnel. Use extreme caution
Changes via IO Diagnostic should only be carried out under instruction
Forces will be cancelled if the controller is restarted
Overview
The I/O Diagnostic module is intended to compliment the Debug Monitor, and separates I/O points by
type. While it provides similar functions, its emphasis is directed more on providing a tool to manipulate
I/O systems that reside within the tool controller. It also attempts to present each I/O point as a single
unit, whereas the Debug Monitor presents individual WebObjects that are part of an I/O point.
Revision 4
Older Style
I/O Diagnostics displays the current tool controller’s default I/O Diagnostics page
This page displays the top level directory of all I/O points on the current tool controller. Click the markers
located to the left of the directory to expand and display its contents.
Continue clicking the markers as necessary to expand each WebObject. Use the tabs located along the top
of the page to filter displayed I/O types.
Revision 4
STUDENT NOTES:
Newer Style
With controller version 3.7.0, I/O Diagnostics was completely redesigned, providing the service tech with
a much more useful tool than in the past.
At the top of the page are a group of tabs organizing the I/O by I/O type:
 Controller-to-Controller
 Modbus (Ethernet)
 Net
 Profibus
 I/O
Under each tab, the I/O is grouped by node, with each node color-coded to show its status:
 Green for good communication
 Red for offline or communication failure
 Grey for ignored
When the page is opened the first tab, Controller-to-Controller (if this controller has any C2C I/O) is
displayed by default.
Revision 4
STUDENT NOTES:
Tabs located across the top of the I/O Diagnostics page provide a way to display all I/O types at once, or
only those of a certain type. The tabs are created dynamically, so there may not be a tab for every
possible I/O type. In addition, different tabs may appear on different controllers. Within each tab, I/O
points are sorted alphabetically by WebObject name. Click the All I/O Points tab to display all I/O types.
Controller-to-Controller (C2C)
Click the Controller-to-Controller tab to display all C2C I/Os.
 Transmission: Ethernet
 I/O Type: C2C
 I/O Identifier: [remote controller name]:[remote controller WebObject name]
The purpose of this type is to receive input from the other controllers, as opposed to sending commands
to them. Therefore, only input classes are assigned to this I/O type.
A C2C request contains the remote controller name. When a remote controller receives a C2C data
request, it compares its own service name to the name contained in the request. If the service name does
not match the controller named in the request, then the controller will not respond. Therefore, it is critical
that all C2C configurations match one another
Modbus
Click the Modbus tab to display all Modbus I/Os. Modbus is a protocol suite designed for industrial
automation. Like Profibus, Modbus has nodes, however there are no cards. Profibus is byte-oriented,
whereas Modbus is word-oriented.
 I/O Type: MOD
Revision 4
 I/O Identifier: [Modbus node string][I/O Type code][Word Number]{.[Bit Number]}{_[String Length]}
Displays information regarding commands that originated from tools and other Ethernet devices
connected to the network.
The I/O Identifier refers to a specific word or bit at a given node. Only the digital inputs and outputs need
to specify the bit number. The range of word numbers is 0 to 125; the range of bit numbers (when given)
is 0 to 15.
Examples
 12DQ6.2: Refers to a digital output (DQ) point writing to bit 2 of byte 6 on Profibus node 12.
 8IR16: Refers to a (floating point) real input (IR) value that would be read from bytes 16 through 19 on
Profibus node 8.
 21SI4_30: Refers to a string input (SI) value that would be read from bytes 4 through 33 on Profibus
node 21.
Revision 4
STUDENT NOTES:
NET
Click the NET tab to display all Net I/O types.
 I/O Type: NET
 I/O Identifier: NET I/Os can be either Streamed, meaning that data is sent to them continually as long
as the source is active; or NonStreamed, meaning that data is sent once briefly for each activation of
the source. This corresponds to the action of the buttons on the HMI screens, the most frequent
activation source for NET I/O: a Streamed input will remain True so long as you hold the button down;
a NonStreamed input will flip True when you press the button then immediately False again, even if
you hold the button down.)Displays information regarding commands that originated from a
touchscreen or workstation control panel (console).
Net I/O will always be shown as Grey (ignored) since it requires external stimulation and no
communications test is done.
Profibus DP1 or DP2

Click the Profibus Card DP1 or Profibus Card DP2 tab to display Profibus DP1 or DP2 I/Os.
 Transmission: Profibus
 I/O Type: DP1 or DP2
 I/O Identifier: [Profibus node number][I/O type code][Byte number][.{Bit number}]/ {_String length]}
I/O Type DP1 refers to the first Applicom® card on the first Profibus DP network (typically used for
communication between the tool controller and hydraulic or pneumatic actuators that move mechanical
parts of the tool). DP2 refers to the optional second Applicom card on the second Profibus DP network
NOT very common on NOV equipment.
Revision 4
The I/O Identifier refers to a specific byte or bit at a given node. Only the digital inputs and outputs need
to specify the bit number. The range of byte numbers is 0 to 225; the range of bit numbers is 0 to 8.
Examples
 12DQ6.2: Refers to a digital output (DQ) point writing to bit 2 of byte 6 on Profibus node 12.
 8IR16: Refers to a (floating point) real input (IR) value that would be read from bytes 16 through 19 on
Modbus node 8.
 21SI4_30: Refers to a string input (SI) value that would be read from bytes 4 through 33 on Modbus
node 21.
No Type
Displays information regarding I/O points that have not been configured.
Note: The next two I/O not commonly used
Step7
 I/O Type: S7
 I/O Identifier: [Step7 node string][I/O type code][Byte number].[Bit number]
Displays information from programmable logic controllers (PLCs). This Ethernet communication protocol
is used on older systems
Cyberbase
Click the Cyberbase tab to display all Cyberbase I/Os.
 I/O Type: CY
 I/O Identifier: [Cyberbase Node String][I/O Type Code][Byte Number]{.[Bit Number]}{_[String Length]}
Displays communication information between various NOV® products; Ethernet communication protocol
(tab not shown here). A Cyberbase node represents a specific device on the Ethernet network that has its
own IP address. Cyberbase node names can have alphabetic characters
Revision 4
STUDENT NOTES:
I/O Identifiers
I/O Identifiers are unique names for the I/O item. The identifier may begin with a node name (or number),
followed by a two-character class abbreviation. There are 12 types of I/O device classes (6 input, and 6
output):
 DI: Digital Input (1 bit) items return a true or false result based on a condition (Boolean values). For
example, a proximity sensor detects metal and the digital input item displays a “True” value.
 DQ: Digital Output (1 bit) items display a zero or 1, off or on, false or true value representing a
command sent to the tool.
Revision 4
STUDENT NOTES:
 AI: Analog Input (2 byte, integer) items convert word input data and display a more meaningful unit.
For example, a pressure sensor may report values from 455 to 15,000, however 455 represents zero
pressure. This item would convert and report “0” (instead of “455”).
 AQ: Analog Output (2 byte, integer) items convert word output data to display a more meaningful
unit. For example, when an operator sends a command using inches through a touchscreen, the
analogue output device converts the inches to a value that the tool recognizes.
Revision 4
STUDENT NOTES:
 IR: Real Input items return a “real,” or “float” value (a 32-bit floating point number as opposed to an
integer).
 QR: Real Output items display a “real” value (a 32-bit floating point number), as opposed to an integer
representing a command sent to another device.
Revision 4
STUDENT NOTES:
 IW: Analog Word Input (2 bytes, integer) items return an integer that may indicate pressure or a tool
position. This may be a 16- or 32-bit integer, depending on the device or tool.
 QW: Analog Word Output (2 bytes, integer) items send commands to tools. This may be a 16- or 32-
bit integer, depending on the device or tool.
Revision 4
STUDENT NOTES:
I/O Identifiers
 ID: Analog Double Word Input (4 bytes, integer) items return an integer that may indicate pressure or
a tool position. This may be a 32-bit integer, depending on the device or tool.
 QD: Analog Double Word Output (4 bytes, integer) items send commands to tools. This may be a 32-
bit integer, depending on the device or tool.
 SI: String Input items return text, such as status messages.
 SQ: String Output items send text, such as status messages. Used on tools such as PRS and ST to
display operator messages on a Cyberbase front end.
Questions
The tab on the right lists I/O objects that are faulty for some reason, usually because the address is
undefined, doesn’t exist or, in the case of an output, conflicts with another
Revision 4
STUDENT NOTES:
Forced Items
The tab on the right lists I/O objects whose values have been forced; you’ll notice that forced objects are
also shown in red in the list pane.
If an object shown in Forced Items is not visible in the list pane, click on it with your mouse.
The page will jump to show it at the bottom.

Revision 4
STUDENT NOTES:
This also works with I/O objects shown on the Questions list.
Press the button to the right of its name.

Revision 4
STUDENT NOTES:
Change/Force Values
Warning: Forcing should only be done under instruction. Rarely used on a working rig, but may be used
during the I&C state or during an upgrade.
The pop up box shows information related to the point, we can see the status of the Current Value, Force
Value and also Force Enabled (similar to Debug)
The radio buttons can be used to unforce it or to change its forced value.
Press Details to see its I/O type and I/O Identifier (address)
di.LampTest is a NET I/O of type Streamed.
NET I/Os can be either Streamed, where data is sent to them continually as long as the source is active, or
NonStreamed, where data is sent once briefly for each activation of the source.
This corresponds to the action of the buttons on the HMI screens.
The most frequent activation source for NET I/O:

 A Streamed input will remain True so long as you hold the button down
 A NonStreamed input will flip True when you press the button then immediately False again, even if
you hold the button down.
Here we see the details of a Modbus (Ethernet) analogue input and a Modbus (Ethernet) digital input.
Revision 4
Forces will be cancelled if the controller is restarted

Revision 4
STUDENT NOTES:
Profibus Diagnostics
Warning: Don’t adjust/modify parameters/values while tool is running
Profibus Diagnostic
Warning: bulletin 10545760-PIB – check before using this function. Most affected rigs have been
upgraded but some may have slipped through.
Node 2 is the Profibus Master (Applicom card) and the fields to the right represent the Profibus nodes.
 Green nodes are working properly.
 Yellow nodes are communicating but there is an issue of some kind e.g. configuration mismatch
 Red nodes are faulty (usually poor or no communication).
Press Change Node Address
Change Node Address can be used, instead of the Siemens Profibus Repeater/Simulator, to set the
address of a Hengstler (Drawworks) encoder, an ATOS valve driver or any other Profibus device that
requires its address to be set in software:
 Install the replacement device
 Enter the device default address in Old Address: (‘Old Address’ is restricted to 126, value of brand
new device)
 Enter the address of the device being replace in New Address:
 Press OK
Revision 4
Change Node Address will not only permit you to set the correct address after installing the replacement
device but will also block certain common errors:
 It will not permit you to duplicate an existing address;
 It will not permit you to alter a correct address;
 It will not permit you to write to an Old Address that doesn’t exist.
 It will not permit you to enter an address that hasn’t been defined in firmware.
Select Change Node Address and you will see a Warning
Old Node Address should be device default address, new address is that being replaced
Revision 4
STUDENT NOTES:
Download Alarms
The Download Alarms module provides a way for the rig maintenance or NOV personnel to download a
text file containing a list of current system alarms.
Prior to www 1.6.0, Download Alarms only displayed alarms on the screen; the display could be
highlighted and copied to a file. Beginning with www1.6.0, Download Alarms actually creates a .csv file of
all alarms in the controller.
 Amphion stores 500 alarms in each controller but they are not saved across restarts; if you restart the
JVM, restart the Controller Computer or cycle power to the SBC, all existing alarm data is lost.
 Download Alarms permits you to download all alarm data from a controller to your laptop; pressing
Download Alarms will open up this dialog box.
 Press Save.
The default name supplied is AlarmEventServlet. However, you will need to supply your own file name,
including the extension “csv” (note that you will need to navigate to wherever on your laptop you want to
save the file).
Pick your filename carefully, especially if you frequently save your alarm data. Here the date and
controller name has been added the file name, making it easy to distinguish from other alarm files. Note
also the “csv” extension; you must provide that for Windows to know how to open the file.
 Press Save to save the file to your hard drive.
Revision 4
STUDENT NOTES:
Collect Debug Info

You may be asked at some point by tech support to collect and send them the debug information so that
they can better assist you. Collect Debug Information will gather all that into a file called into.zip that you
can email to tech support.
Press Collect Information.
Select Individual or multiple tools (If available) then press ‘Download’
You’ll be asked if you want to save the file to your local machine, select Save As then navigate to a
location on your laptop
Press Save.
The file will be in zip format; in this case it is called Top_Drive_info.zip

Revision 4
Configuration
Revision 4
STUDENT NOTES:
Consistency Checker
The Consistency Checker module provides a way for the user to determine the software versions for each
tool controller connected to the rig network. This is normally used by NOV personnel that set up the tool
controllers to ensure that the following are consistent:
 Base controller software
 Operating system scripts (“base layout”) version
 WWW version
 ownership.xml files
 ip_list.xml files
 Process screens
 Tool controller time settings
The currently-selected tool’s controller is used as a reference and compared with other controllers. The
reference controller’s background displays green. Items that contain the same information as the
reference controller display with a white background. Items that cannot be found or contain different
information display with a pink background.
Revision 4
STUDENT NOTES:
Click any cell displaying the text “No Match” in the columns labelled Ownership or IP List inside the table
to display the ownership and IP list Differences table
Files found on the reference tool controller display on the left side of the window, while files from the
other tool controller display on the right. Lines that appear in the file on the reference tool controller, but
not on the other controller display with a blue highlight. Lines that appear in the files on the other tool
controller, but not on the reference tool controller display with a yellow highlight. Lines that match are
not highlighted. Click OK to close the Differences window and return to the main Consistency Checker
window.
Revision 4
STUDENT NOTES:
Click any cell displaying the text “No Match” in the columns labelled Ownership or IP List inside the table
to display the ownership and IP list Differences table
Files found on the reference tool controller display on the left side of the window, while files from the
other tool controller display on the right. Lines that appear in the file on the reference tool controller, but
not on the other controller display with a blue highlight. Lines that appear in the files on the other tool
controller, but not on the reference tool controller display with a yellow highlight. Lines that match are
not highlighted. Click OK to close the Differences window and return to the main Consistency Checker
window.
Revision 4
STUDENT NOTES:
Click any cell displaying the text “No Match” in the column labelled Process Screens to display the process
screens Differences table.
This window displays a list of process screens found on both tool controllers, and those that are found on
one controller, but not the other. Click OK to close the Differences window and return to the main
Consistency Checker window. Click Refresh to refresh the Consistency Checker window.
Note: Ensure columns are resized to ensure all information is shown prior to taking a screenshot.
Alternatively use the Software Manager…Summary…Save to File to save an electronic version.
Note: VDAQ/SDAQ/MSI looks like an SBC but isn’t and will almost certainly contain different software
versions. Do not modify unless instructed. If rolling out changes across multiple tools ensure this tool is
not selected
Revision 4
STUDENT NOTES:
Set Date and Time
Warning: Don’t adjust/modify parameters/values while tool is running.
Copy Local Time to Controller to both set the time in this controller and make it the time master for the
entire system. It is not necessary any longer to set the time in every controller – once in one controller
will synchronize the entire Amphion system (but not the HMIs).
Starting with controller 3.6.7 not only is it possible to set all the controllers from one controller and to do
so while the tool is running, but the time will be synchronized in Greenwich MeanTime
Beginning with controller 3.7.3 it looks like this, with several options available.
 In the top pane you can not only copy the local time from your laptop to the controller but also
specify an offset. This permits you to keep time in GMT if you wish to do so (or any time zone,
actually) but the default offset of zero will make the local time your system time.
 It also can receive GPS time from your dynamic positioning system, which again can be offset (by
default, GPS is in GMT, so you would want to apply an offset to display it in local time).
 And the bottom pane permits an offset to the time displayed on the operator screens. This would
permit, say, updating the operator screens to show Daylight Savings Time without changing the
system time. Or to display local time on the operator screens while running the system in GMT.
 If you press Copy Local Time to Controller
You’ll get this warning, which basically says that future saved files and alarms will be stamped with your
new time and may overlap the times in files and alarms already stamped (for instance, if you “fall back”
Revision 4
for the end of DST). And recommends that, if all you want to do is change the time displayed on the
operator screens, you can change the operator screen offset instead. Press Yes.
Warning: The real time clock is used in calculations, e.g. TDS rpm, one particular occasion, reported by
Tech Support, a TDS SBC time and date was updated and the rpm took off and reached at least 350rpm!
Note: Co-ordinated time keeping was originally not very good, but has improved over the years and can
be made ‘bulletproof’ with the addition of a GPS module.
Note: If using logs files etc., from an SBC note the controller time. Any difference between it and the real
world time may need to be taken into account when examining logs. E.g. Operator reports alarm at 0309
but the SBC clock is off and the alarm is logged as 0257.
Revision 4
Simulation Control
When a tool controller is in simulation mode, it appears that it is operating with actual tools when it is
not. The Simulation Control module provides a way for the user to control the built-in simulation system
by performing the following actions: Enable and disable simulation mode Specify whether the controller is
a dedicated simulator Save simulation data to a file Load simulation data file onto a controller Specify
whether to simulate WebObjects only Warning: Simulation mode should not be used on a real SBC, but
can be used in conjunction with a virtual SBC (e.g. VirtualBox method, discussed in Presentation 3.7)
Revision 4
Controller
Revision 4
STUDENT NOTES:
Status Window / Dashboard

This applet (also referred to as the “dashboard”) displays the current state of the JVM and the tool
controller. The JVM is a program that runs on the tool controller. Java software consists of code that is
designed to run in a “virtual” machine. The JVM on the tool controller actually runs two separate Java
programs simultaneously. One is a tool controller program, and the other is a Web server. The controller
program interfaces with equipment outside of the tool controller. The Web server provides HTML Web
pages and runs servlets. The Web server and the controller communicate with one another, but they are
essentially independent programs. It is possible for one or both to operate without the other.
A green box in the upper right of the Service Page is called the Dashboard. It gives indications of the
condition of your controller.
 Dashboard as it normally appears: JVM up, Controller up, the name of the controller and value of the
Life Counter and “There are no forced values.” greyed out in the box at the bottom. (The Life Counter
is a 16-bit register in each controller that is incremented every software cycle – every 20ms – and is
used to ensure that the controller is online and running.)
 Controller down. If the JVM were down, that stripe would be red.
 Dashboard during a reboot
 View Forced Values will be enabled if there are existing values forced, selecting the tab will open up
another window detailing which values have been forced
In a new tab, open Debug Monitor and use the Forced Values dialog as a guide for navigating to, in this
case, Chair.di.EStop and set its forceEnabled to F.
 Press OK to dismiss the dialog.
 Note that, if you return to the first, “Service Pages” tab, it will still show “View Forced Values.” This is
because the system is only polled for forced values when the Service Page is opened. To clear it,
refresh the Service Page.
Revision 4
STUDENT NOTES:
Log Manager Viewer

Various subsections of the controller generate log entries when significant events occur (such as errors).
Click the Log Manager/Viewer link to display a list of log files stored on the current tool controller.
Copy logs to PC before deleting.
The main Log Manager/Viewer page displays the file size, date and time modified, and links to either
view or delete (reset) the log file.
Click the link located beneath View Log to display the log file.
Click the link located beneath Reset to delete the log file.
Most log files, with the exception of the j9.log file, have a fixed length (normally 100 KB). When the log
file exceeds this length, it is renamed (a “.1” is appended to the file name), and a new log file is created. If
the second log file exceeds the maximum size, it replaces the first log file, and another is created.
Most log files (with the exception of the j9.log file), are maintained between controller restarts, and
continue accumulating messages while the controller is running.
j9.log records all Java events and is an open file. If j9.log is larger than 10K, the system will have difficulty
finding a place to write to it, which can slow operations. (New software will actually generate an alarm if
j9.log gets bigger than 10K.)
J9.log should be deleted if it is larger than 10K, if the particular tool seems slow or unresponsive, or if the
J9 log file is large then send a copy to tech support/software prior to deleting.
Revision 4
Each entry in the log file follows a basic pattern. Entries begin with a keyword (debug, info, warn, error,
or fatal), followed by the date and time (hours:minutes:seconds, milliseconds), and the name of the code
entity that posted the entry (displayed in square brackets). This basic information is followed by the
message itself.
 The j9.log and j9.previous.log files are different from the other log files. They capture outputs from
the JVM itself, and record error messages resulting from serious controller program or Web server
failures. A new file is created every time the JVM starts up, and the previous j9.log file overwrites the
file named j9.previous.log. This file can be a useful troubleshooting tool when the tool controller is
not running.
 The io.log file contains messages from the subsystem that manages communications between the tool
controller and input/output devices. This file can be a useful troubleshooting tool when an input or
output point object could not be created, or not reading or writing, since it captures messages that do
not apply to other I/O logs.
 The ora.log file contains messages from the tool controller program itself. This file can also be a useful
troubleshooting tool when the controller is not running.
 The c2c.log file contains information related to inputs and outputs between the current tool controller
and other tool controllers.
 The step7.log file contains information related to inputs and outputs that use the Siemens® Step7
protocol.
 The alarm.log file contains errors messages from the alarm manager subsystem. This file does not
contain actual alarms.
 The varball.log file contains the name of the last varball installed, the controller version, the www
version, the base layout used to create the varball, and a list of files installed.
 The version.log file contains the date and time of every www version installed, as well as the name of
the file that was decompressed. It also records the date and time the varballs were created on the
tool controller.
Revision 4
STUDENT NOTES:
Restart JVM
Use this link to restart the controller’s Java program running inside the virtual machine. When you restart
the JVM, it restarts the software, without restarting the tool controller itself. This is often preferable, as it
takes less time and is less disruptive to operations.
Click the Restart JVM link to begin this process. A message displays, informing the user that the JVM is
restarting. This takes several minutes. During this time, you will be unable to access the controller using
the browser.
Note: Only to be carried out under instruction at Level 0

Revision 4
STUDENT NOTES:
Flash Applicom Card
Warning: Do not flash the Applicom card on a tool that is in use – you will shut down the controller and
disable all Profibus I/O while the flash is in process!
This procedure is intended for use on tool controllers that have an Applicom I/O card installed. Only tool
controllers that communicate using Profibus protocol with tool hardware have or need an Applicom I/O
board. The Applicom board provides an entry point for the tool controller to the Profibus network. This
network is separate from the Ethernet network used by other I/O protocols (such as Modbus, C2C, and
Cyberbase). Flashing the Applicom card loads the Profibus configuration into the flash memory on the
Applicom hardware.
When first introduced the Applicom cards for Beckhoff tool controllers did not come from the factory
already flashed. You had to burn an image to the card prior to installation. Current stock is not affected in
the same way but some spares on rigs may be the older type. The Beckhoff flasher image and instructions
can be found on the old Wiki.
Note: the Applicom configuration should be checked using Applicom IO prior to flashing. It has been
known for incorrect Applicom.zip files to be found on SBCs even though the correct configuration is on
the Applicom card.
Prepare the tool controller for communication with the Profibus network, if applicable.
Click the Flash Applicom Card link to display the Administrative Controls Login screen.
Type the administrative password into the space provided, and then click Log in to display the current
tool’s Flash Applicom Card page.
Revision 4
Click Proceed.

Revision 4
STUDENT NOTES:
Flash Applicom Card

The tool controller program pauses. After approximately ten seconds, the flashing process begins.
When flashing is complete, scroll to the bottom of the screen and ensure that the message: “Initialization
succeeded” displays, indicating a successful flash.
Click the Back button to return to the Flash Applicom Card page, and then click Cancel.
The tool controller program and Profibus Applicom card automatically restart after flashing is complete.
Click Contents to return to the main service page.
Verify that the Profibus Communication Status lights on the Profibus Applicom cards are blinking green

Revision 4
STUDENT NOTES:
Restart Controller
This link provides a way for service personnel to restart the tool controller hardware.
Restart Controller Computer performs a warm reboot of the hardware itself (similar to a Restart on a
Windows computer).
Click the Restart Controller Computer to restart the tool controller. The message beginning with the text,
“Reboot was successful” displays when the tool controller hardware has successfully shut down. After a
few minutes, the controller restarts and becomes available online.

Revision 4
STUDENT NOTES:
Halt Controller Computer

This link provides a way for service personnel to shut down the tool controller hardware.
Halt Controller Computer sends a HALT command to the microprocessor, causing the processor the shut
down – the computer can only be restarted by cycling the power.
Click the Halt Controller Computer to restart the tool controller. The message “System halt was
successful” displays when the tool controller hardware has successfully shut down.

Revision 4
STUDENT NOTES:
Operator Screen
Click Operator Screens to display the standard HTML operator tool screens. A typical top drive screen is
shown here.
Note: Only to be carried out under instruction at Level 0, Tech Support or Senior FST can provide detailed
instructions
Revision 4
STUDENT NOTES:
Documentation
Click Documentation to display available online documentation (if available). To view online
documentation, the manuals package must be installed
Older software usually no documents within this link
Newer software will have five documents within this link
Preferences document is shown as an example

Revision 4
Revision 4
Revision 4
Revision 4
Revision 4
Remote Troubleshooting
Revision 4
STUDENT NOTES:
Upon lesson completion, course participants will be able to carry out basic troubleshooting techniques
given instructions by being able to:
Demonstrate how to record data within a given URL for remote troubleshooting.
Verify operation of I/O and make changes under instruction.
Copying data logging files to PC.
Revision 4
Debug Monitor URL

Revision 4
STUDENT NOTES:
Debug Monitor URL

Tech Support may provide a link containing pre-selected points to monitor a particular operation. The link
will open directly in Debug Monitor allowing a recording of these points to be taken and emailed to assist
with troubleshooting.
Creating a Link to Monitored Items

 Select the items you wish to monitor, as described SBC/Tool Controller Service Page
 Click Generate URL to create a link to all items displayed.
Revision 4
STUDENT NOTES:
 Click Names, then click Favorites --> Add to Favorites. Assign a name and location for the URL in your
browser’s Favorites folder. (Indices may be the only option when creating a URL on an early SBC)
 By default, the link appears in Microsoft® Internet Explorer’s browser’s Favorites folder as Debug
Monitor. NOV recommends that you assign a more specific name to reflect this particular set of
parameters. In general, browsers have a limit of 256 characters for the URL name. If you have
numerous items to monitor, the browser may truncate the URL string, making it impossible to locate
the correct link. The character limit depends on the names themselves and the number of items you
choose. (See warning ‘Cannot generate URL’)
Revision 4
STUDENT NOTES:
 Click the appropriate URL (located in your Favorites folder) to launch the Debug Monitor using the
selected/linked items. A URL can be generated by WebObject name or WebObject index.
Note: WebObject index refers to the place in the tool controller where the object occurs. The indices of
WebObjects can change if the tool controller’s configuration changes. Therefore, a URL generated by
index may not display the same WebObjects on a similar, but differently-configured tool controller or on
the same controller if changes e.g. an upgrade, has resulted in a change to webobjects. A URL generated
by WebObject name is more accurate, and is therefore recommended by NOV.
The example shows points selected to monitor the position of the Dolly via linear transducer
Revision 4
STUDENT NOTES:
Revision 4
I/O Diagnostics
Revision 4
STUDENT NOTES:
Check / Change Address

Addressing should be confirmed using correct documentation associated with that particular installation
(obtain documentation using methods covered in ‘Documentation’ chapter)
The example screenshots show changing a digital output address associated with the simulation
equipment
Steps to changing I/O address:

 ZMS I/O Diagnostic – navigate to I/O point to modify
 Profibus Card, Node 9, 9DQ0.0 (dq.CPUOnLamp) – select button with three dots to open
change/force value window
 Select details to view/edit I/O type and address – can change node address, I/O type, byte and bit
information associated with point
 Change bit from 0 to 1
Revision 4
STUDENT NOTES:
 Changes will not take effect until configuration files have been saved and JVM has been restarted
– Show this to be true by forcing output off/on
 Saving changes to persistent storage – Objects.csv and converters.xml
 Restart Controller
 Waiting
 Navigate back to I/O Diagnostic, locate and confirm address change and function (force off/on)
Note: Changes should only be made under instruction and while the tool is not in use!
Revision 4
STUDENT NOTES:
Revision 4
STUDENT NOTES:
Addressing Conflicts
Inputs can have the same address but not Outputs.
 IO Diagnostic ZMS – Show initial addressing 9DQ0.0 and 9DQ0.7
 Create Conflict – Change first address to duplicate second
 Save configuration and restart JVM
Revision 4
STUDENT NOTES:
Addressing Conflicts Continued

 On restart note that Dashboard shows controller down… The output conflict that we have created
has caused this. With earlier revisions of Firmware…
 Select IO Diagnostic Link - The system will detect there is a problem and will check for an
addressing conflict
Revision 4
STUDENT NOTES:

 When the application restarts the I/O associated with the conflict will appear in the questions tab
 Select the I/O from the questions list, this will navigate you directly to that point
 Edit the address to remove the conflict, save the configuration files and restart the controller.
Addresses can be changed via Debug or I/O Diagnostics in the first instance, but can only be
corrected via the I/O Diagnostics link (try Debug and see what happens, the link will not open
correctly since the controller is down!)
 When you change the address back to its original or a non-conflicting address you will need to
enter the amphion password (Since the controller has been restarted)
Revision 4
STUDENT NOTES:

 The controller will restart and if all is well the Dashboard should look normal
Revision 4
STUDENT NOTES:
Revision 4
Copying Data Logging Files to PC

Revision 4
STUDENT NOTES:
Teamcentre doc # 16658757-MAN rev01 section 2.

There are several ways to get logged data off of an SBC. The method discussed here should be the
simplest approach
Revision 4
STUDENT NOTES:
In the top left hand corner select the File menu then select Copy Logged Data Files from Controllers
button from the File Menu This will bring up the Copy File From Controllers window. This window allows
the operator to select a range of datalog files on the controller and copy them to a local directory.
Revision 4
STUDENT NOTES:
Check I/O Function

Revision 4
Revision 4
Revision 4
Laptop Simulation
Revision 4
STUDENT NOTES:
Upon lesson completion, course participants will be able to demonstrate capabilities and limitations of
SBC simulation on laptop using virtual box by being able to:
Install and configure a virtual box program to run a specified tool controller / SBC.
Revision 4
STUDENT NOTES:
Virtual box
What is Virtual Box?

VirtualBox is a cross-platform virtualization application. It extends the capabilities of your existing
computer so that it can run multiple operating systems (inside multiple virtual machines) at the same
time. So, for example, you can run Windows and Linux on your Mac, run Windows Server 2008 on your
Linux server, run Linux on your Windows PC, and so on, all alongside your existing applications. You can
install and run as many virtual machines as you like -- the only practical limits are disk space and memory.
Why is Virtualization Useful?

The techniques and features that VirtualBox provides are useful for several scenarios:
 Running multiple operating systems simultaneously. VirtualBox allows you to run more than one
operating system at a time. This way, you can run multiple SBCs.
 Testing and disaster recovery. Once installed, a virtual machine and its virtual hard disks can be
considered a "container" that can be arbitrarily frozen, woken up, copied, backed up, and transported
between hosts.
 On top of that, with the use of another VirtualBox feature called "snapshots", one can save a
particular state of a virtual machine and revert back to that state, if necessary. This way, one can
freely experiment with a computing environment. If something goes wrong (e.g. after installing
misbehaving software or infecting the guest with a virus), one can easily switch back to a previous
snapshot and avoid the need of frequent backups and restores.
 Any number of snapshots can be created, allowing you to travel back and forward in virtual machine
time. You can delete snapshots while a VM is running to reclaim disk space.
Source - https://www.virtualbox.org/manual/ch01.html
Revision 4
STUDENT NOTES:
Reference Document –80879225

Revision 4
STUDENT NOTES:
Revision 4
Revision 4

Amphion Level 0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amphion Level 0

Uploaded by

Copyright:

Available Formats

STUDENT HANDBOOK

04-Amphion Disc Level 0

Document number 96747643

Introduction to Amphion and Single Board Computers ................................................................ 6

Drawings / Manuals .............................................................................................. 93

Devices and Navigation ...................................................................................... 180

Lesson Review .............................................................................................................. 291

Course Completion Certificate

General System Safety Practices

Proper Use of Equipment

NOV Control System History

Automation / Relay Logic

Source: automationmag - http://www.automationmag.com/features/the-father-of-invention-dick-morley-

Automation / Relay Logic

 Storage Temperature -4 degF to 140 degF

Driller’s Control Console (Drill Floor Console)

Joystick Assembly and Controls

Remote I/O Panel (PLC Control Assembly)

What is SCADA Used For?

How Do SCADA Systems Work?

The Evolution of SCADA

Four types of communication networks/links are used:

Amphion System Overview

Other benefits of SBC/Amphion over PLC/SCADA systems include:

 Less 3rd party software;

Amphion Design Tenets

The tenets are listed below:

Reference Document - D6A1000576 2.1

Single Board Computer

SBC/Amphion System Overview

Brick (ATC – Advanced Technology Controller)

PROFIBUS Channel Transmission Light

PROFIBUS Communication Status Light

Hardware – Brick Enclosure

Press the Power button on the tool controller to turn it on or off.

Profibus (Process Field Bus)

Profibus (Process Field Bus)

Multi-Tool Controller (MTC) Cabinet

The boot sequence can be monitored in VirtualBox.

Terminology and Abbreviations

Software Products Server

You will find information relating to the following topics

Amphion Software Network

Platform (firmware) Development

Varball Server takes you to SPS

Varco Software Wiki takes you to the ‘old’ Wiki site

Results from Document search

The Group column indicates the item's origin.

Manually type in wildcard(s) into search:

Rig Doc / Rig Office

There are two main tabs in RigDoc Web:

RigOffice will open, displaying the Document in the RigDocument module

Open Document Details in RigDoc Web

The list can be shortened by filling in additional criteria

The list has now reduced to 94 documents

By filling in the additional criteria

We can reduce the number of associated documents to 2 User manuals

What do you want to do?

The associated documents will be listed below the search parameters

Note: Legacy Varco/Amphion documents found in RigDoc/RigOffice should be cross checked in

RigDocument is a program within the RigOffice suite.

Documents, Files Downloaded and To Do List

Search for documents

Open Users Guide