STUDENT HANDBOOK

Amphion Discipline Level 1

Document number 96780739

Revision 1
PP revision
Document number 96780739 Page 2 of 544
Revision 1
 Document number 96780739 Page 3 of 544
Revision 1

Table of Contents
Introduction to Amphion ........................................................................................................................... 12
Lesson Objectives ......................................................................................................................... 13
Amphion Overview ........................................................................................................................ 15
Amphion Overview ............................................................................................................ 16
Amphion Overview ............................................................................................................ 17
Amphion Overview ............................................................................................................ 18
Amphion Overview ............................................................................................................ 19
Amphion Overview ............................................................................................................ 20
Amphion Overview ............................................................................................................ 21
Amphion Overview ............................................................................................................ 22
Amphion Overview ............................................................................................................ 23
Amphion Overview ............................................................................................................ 24
Driller’s Cabin ..................................................................................................................... 25
Safety Precautions ........................................................................................................................ 26
Safety 24/7 ......................................................................................................................... 27
Testing Safety .................................................................................................................... 28
Operation and Maintenance ............................................................................................ 29
Fail-Safe Theory ................................................................................................................ 31
Drill Floor Shutdown – E-Stop ......................................................................................... 34
Zone Management System ............................................................................................. 37
Zone Management System ............................................................................................. 40
Lesson Review .................................................................................................................. 42
Lesson Review .................................................................................................................. 43
Equipment Overview ................................................................................................................................ 44
Lesson Objectives ......................................................................................................................... 45
Workstations .................................................................................................................................. 46
Front Entry Chair (Amphion-FEC) .................................................................................. 49
Wrap-Around Workstation (Amphion-WAW) ................................................................ 54
Amphion Hardware Hierarchy Overview ................................................................................... 59
Operator.......................................................................................................................................... 62
Amphion Generation 1/2 Differences......................................................................................... 70
Generation 1 Joysticks ..................................................................................................... 71
Generation 1 Control Panels ........................................................................................... 72
Generation 2 Joysticks ..................................................................................................... 73
Generation 2 Left Joystick ............................................................................................... 75
Generation 2 Left Joystick Directional Control ............................................................. 76
Generation 2 Right Joystick ............................................................................................. 77
Generation 2 Right Joystick Directional Control........................................................... 79
 Document number 96780739 Page 4 of 544
Revision 1

Generation 2 Left Control Panel Example..................................................................... 80

Generation 2 Right Control Panel Example .................................................................. 82
Generation 2 Joystick Help .............................................................................................. 83
Generation 1 (15 inch) and Generation 2 (19 inch) HMIs ........................................... 84
Generation 1 SBC Service Page .................................................................................... 86
Generation 1 Collect Debug Information ....................................................................... 87
Generation 1 Consistency Checker ............................................................................... 88
Generation 2 SBC Service Page 2 ................................................................................. 89
Generation 2 Collect Debug Information ....................................................................... 90
Consistency Checker Gen 2 ............................................................................................ 91
Ethernet .......................................................................................................................................... 92
Bridgeway Ethernet to J1939 Gateway ....................................................................... 103
Bridgeway Ethernet to J1939 Gateway – Status and Diagnostics .......................... 105
Modbus – Ethernet Programmable Fieldbus Controller ............................................ 107
Modbus – Ethernet Programmable Fieldbus Controller ............................................ 109
Profibus I/O .................................................................................................................................. 117
Profibus Network Media ................................................................................................. 122
Profibus Troubleshooting ............................................................................................... 126
Siemens OLM .................................................................................................................. 142
Bartec LWL....................................................................................................................... 143
Bartec Coupler ................................................................................................................. 144
Bartec MODEX I/O .......................................................................................................... 146
ATOS Driver ..................................................................................................................... 147
DMA Driver ....................................................................................................................... 149
Rig Tools ...................................................................................................................................... 150
I/O (Physical on Tool) ..................................................................................................... 152
Additional Hardware e.g. UPS .................................................................................................. 155
UPS System ..................................................................................................................... 156
UPS – Power Quality ...................................................................................................... 158
UPS Keypad..................................................................................................................... 159
Load Level Indicators ..................................................................................................... 162
UPS Status Indicators .................................................................................................... 163
UPS Homepage in Amphion ......................................................................................... 164
UPS Homepage in Amphion- Healthy ......................................................................... 165
UPS Homepage in Amphion- AC Mains Failure ........................................................ 166
Lesson Review ................................................................................................................ 167
Lesson Review ................................................................................................................ 168
Amphion Signal Path Overview ............................................................................................................ 169
Lesson Objectives ....................................................................................................................... 170
Operator Workstation to Ethernet ............................................................................................. 171
 Document number 96780739 Page 5 of 544
Revision 1

HMI > Ethernet................................................................................................................. 174

Physical Switch > I/O Module > Ethernet .................................................................... 176
Ethernet to SBC .......................................................................................................................... 179
SBC to Remote I/O ..................................................................................................................... 183
SBC > Profibus Remote I/O .......................................................................................... 185
SBC > Profibus Remote I/O .......................................................................................... 186
SBC > Ethernet Remote I/O .......................................................................................... 187
Remote I/O > Tool Control and Feedback .............................................................................. 188
Remote I/O > Tool Control and Feedback .................................................................. 190
Remote I/O > Tool Control and Feedback .................................................................. 191
Signal Path Overview ................................................................................................................. 193
Video for Signal Path ...................................................................................................... 194
Lesson Review ................................................................................................................ 195
Amphion Network and Communications ............................................................................................. 196
Lesson Objectives ....................................................................................................................... 197
Topology ....................................................................................................................................... 198
Topology ........................................................................................................................... 199
Topology – Ethernet Converters ................................................................................... 203
Topology – Profibus OLM .............................................................................................. 205
Topology ........................................................................................................................... 207
Topology ........................................................................................................................... 208
Profibus Remote I/O Applications ............................................................................................ 209
Modbus Remote I/O Applications ............................................................................................. 227
Modbus Applications – Chair Adjustments ................................................................. 228
Modbus Applications – Chair Adjustments ................................................................. 229
Modbus Applications – Chair Adjustments (C2 – 15) ................................................ 230
Modbus Applications – Chair Adjustments ................................................................. 231
Amphion Signal Path Detailed .............................................................................................................. 233
Lesson Objectives ....................................................................................................................... 234
Workstation Software ................................................................................................................. 235
HMI – Operator Pages ................................................................................................... 236
Widget Editor – Viewing Only OFFLINE ...................................................................... 239
Widget Editor – Viewing Only OFFLINE ...................................................................... 241
Screen Communication Logs ........................................................................................ 242
Tool Controller ................................................................................................................. 243
Configuration Files – ip_list.xml .................................................................................... 246
Configuration Files – io_config.xml .............................................................................. 248
Tool Controller Software - Netbeans ............................................................................ 254
Profibus I/O Addressing ............................................................................................................. 255
Modbus I/O Addressing.............................................................................................................. 260
 Document number 96780739 Page 6 of 544
Revision 1

Detailed Signal Path ................................................................................................................... 265

Digital Output ................................................................................................................... 266
Digital Output ................................................................................................................... 267
Digital Output ................................................................................................................... 268
Digital Output ................................................................................................................... 269
Digital Output ................................................................................................................... 270
Digital Input ...................................................................................................................... 271
Digital Input ...................................................................................................................... 272
Digital Input ...................................................................................................................... 273
Digital Input ...................................................................................................................... 274
Digital Input ...................................................................................................................... 275
Analog Output .................................................................................................................. 276
Analog Output .................................................................................................................. 277
Analog Output .................................................................................................................. 278
Analog Output .................................................................................................................. 279
Analog Output .................................................................................................................. 280
Analog Output .................................................................................................................. 281
Analog Input ..................................................................................................................... 282
Analog Input ..................................................................................................................... 283
Analog Input ..................................................................................................................... 284
Analog Input ..................................................................................................................... 285
Analog Input ..................................................................................................................... 286
Video for Signal Path Detail........................................................................................... 287
Signal Path Detail ............................................................................................................ 288
Signal Path Detail ............................................................................................................ 289
Signal Path Detail ............................................................................................................ 290
Lesson Review ................................................................................................................ 291
Diagnostics Tools and Software ........................................................................................................... 292
Lesson Objectives ....................................................................................................................... 293
Communication Port Number Setting ...................................................................................... 294
Communication Port Number Setting .......................................................................... 295
Communication Port Number Setting .......................................................................... 296
Ethernet Port Setting ...................................................................................................... 297
Brad Communications (Applicom I/O) ..................................................................................... 298
Brad Communications – Applicom I/O ......................................................................... 299
Brad Communications – Applicom I/O ......................................................................... 301
Brad Communications – Applicom I/O ......................................................................... 302
Brad Communications – Applicom I/O ......................................................................... 303
Brad Communications – Applicom I/O ......................................................................... 304
Brad Communications – Applicom I/O ......................................................................... 305
Document number 96780739 Page 7 of 544
Revision 1

Brad Communications (Applicom I/O) ......................................................................... 306

Brad Communications (Applicom I/O) ......................................................................... 307
Brad Communications (Applicom I/O) ......................................................................... 308
Brad Communications (Applicom I/O) ......................................................................... 309
Wago Ethernet Settings ............................................................................................................. 311
Wago Ethernet Setting ................................................................................................... 312
Wago Ethernet Setting – Wago Service Cable .......................................................... 313
Wago Ethernet Setting – Wago Service Cable .......................................................... 314
Wago Ethernet Setting – Wago Service Cable .......................................................... 315
Wago Ethernet Setting – Ethernet Cable .................................................................... 316
Wago Ethernet Setting – Ethernet Cable .................................................................... 317
Wago Ethernet Setting – Ethernet Cable .................................................................... 318
Wago Bus Coupler Webserver...................................................................................... 319
Wago Port Setting ........................................................................................................... 321
Wago Ethernet Setting ................................................................................................... 322
Wago Ethernet Setting ................................................................................................... 323
Wago BootP Method....................................................................................................... 324
Wago I/O Check .......................................................................................................................... 325
Wago IO Check V3 ......................................................................................................... 326
Communication Setting .................................................................................................. 329
Control Mode - Direct...................................................................................................... 330
Control Mode - Collect .................................................................................................... 331
Control Mode - Force ...................................................................................................... 332
Control Mode - Permanent ............................................................................................ 333
Control Mode - Error ....................................................................................................... 334
Monitor Mode ................................................................................................................... 335
EDS Configurator ........................................................................................................................ 337
edscfgui.exe ..................................................................................................................... 338
Broadcast Search ............................................................................................................ 340
Modify IP Address ........................................................................................................... 342
Upgrade Firmware .......................................................................................................... 343
Export/Import Configuration........................................................................................... 345
Discovering the Rig IP Domain ..................................................................................... 347
Moxa Configuration and Ring Diagnostic ................................................................................ 348
The Moxa Switch Web Page ......................................................................................... 349
Moxa Settings – Disable DIP Switches ....................................................................... 351
Moxa Settings - Communication Redundancy ........................................................... 353
Moxa Settings - Auto Warning ...................................................................................... 355
Moxa Settings - Factory Default ................................................................................... 357
Moxa Ring Diagnosis V2.3 ............................................................................................ 358
 Document number 96780739 Page 8 of 544
Revision 1

Moxa – Monitoring Network Status .............................................................................. 360

Moxa – Testing Ring Redundancy ............................................................................... 362
Moxa – Ring Break.......................................................................................................... 363
Profibus Master Simulator ......................................................................................................... 365
Profibus DP Master Simulator ....................................................................................... 366
Online Connection........................................................................................................... 367
Scanning for Slaves ........................................................................................................ 368
Addressing Slaves .......................................................................................................... 369
Verifying Slave Address ................................................................................................. 370
Testing Feedback ............................................................................................................ 371
BWConfig - Canbus Joystick ..................................................................................................... 373
BWConfig – User Interface ............................................................................................ 374
BWConfig – Setting the IP Address ............................................................................. 375
BWConfig - Joystick and Canbus ................................................................................. 377
BWConfig - Joystick and Canbus ................................................................................. 378
Verification of Indicators ............................................................................................................. 380
Verification of Indicators ................................................................................................. 381
Verification of Indicators ................................................................................................. 382
Verification of Indicators ................................................................................................. 384
Lesson Review ................................................................................................................ 385
Amphion Main Service Page ................................................................................................................. 386
Lesson Objectives ....................................................................................................................... 387
Devices and Navigation ............................................................................................................. 388
IP Network .................................................................................................................................... 389
Devices and Navigation ............................................................................................................. 390
Edit Address List ......................................................................................................................... 391
Edit Address List ......................................................................................................................... 392
Edit Address List ......................................................................................................................... 393
Edit Address List ......................................................................................................................... 394
Edit Address List ......................................................................................................................... 395
Edit Address List ......................................................................................................................... 396
Show IP Address ......................................................................................................................... 397
Investigate Address .................................................................................................................... 398
Software Management ............................................................................................................... 400
Restricted Functions ................................................................................................................... 401
Software Versions ....................................................................................................................... 402
Backup and Restore ................................................................................................................... 403
Backup and Restore ................................................................................................................... 404
Backup and Restore ................................................................................................................... 405
Backup and Restore ................................................................................................................... 406
Document number 96780739 Page 9 of 544
Revision 1

Backup and Restore ................................................................................................................... 407

Backup and Restore ................................................................................................................... 408
Backup and Restore ................................................................................................................... 409
Software Installer ........................................................................................................................ 411
Software Installer ........................................................................................................................ 412
Transfer Files ............................................................................................................................... 413
Transfer Files ............................................................................................................................... 415
Transfer Files ............................................................................................................................... 416
Transfer Files ............................................................................................................................... 417
Transfer Files ............................................................................................................................... 418
Transfer Files ............................................................................................................................... 419
Software Manager ....................................................................................................................... 420
Software Manager ....................................................................................................................... 422
Software Manager ....................................................................................................................... 423
Diagnostics ................................................................................................................................... 424
Debug Monitor ............................................................................................................................. 425
Debug Monitor ............................................................................................................................. 427
Debug Monitor ............................................................................................................................. 428
Debug Monitor ............................................................................................................................. 430
Debug Monitor ............................................................................................................................. 431
Debug Monitor ............................................................................................................................. 432
Debug Monitor ............................................................................................................................. 433
Manipulating Graphs....................................................................................................... 434
Manipulating Graphs....................................................................................................... 436
Manipulating Graphs....................................................................................................... 438
I/O Diagnostics ............................................................................................................................ 439
I/O Diagnostics ............................................................................................................................ 441
I/O Diagnostics ............................................................................................................................ 442
I/O Diagnostics ............................................................................................................................ 444
I/O Diagnostics ............................................................................................................................ 446
I/O Diagnostics ............................................................................................................................ 447
I/O Diagnostics ............................................................................................................................ 448
I/O Diagnostics ............................................................................................................................ 449
I/O Diagnostics ............................................................................................................................ 450
I/O Diagnostics ............................................................................................................................ 451
I/O Diagnostics ............................................................................................................................ 452
I/O Diagnostics ............................................................................................................................ 453
Check / Change Address ........................................................................................................... 455
I/O Diagnostics ............................................................................................................................ 456
Check / Change Address ........................................................................................................... 456
 Document number 96780739 Page 10 of 544
Revision 1

I/O Diagnostics ............................................................................................................................ 457

I/O Diagnostics ............................................................................................................................ 458
I/O Diagnostics ............................................................................................................................ 459
I/O Diagnostics ............................................................................................................................ 460
Data Logging................................................................................................................................ 461
Data Logging................................................................................................................................ 462
Profibus Diagnostics ................................................................................................................... 468
Profibus Diagnostics ................................................................................................................... 470
Configuration................................................................................................................................ 472
PC Security and Roles on Amphion ............................................................................. 473
Preferences ...................................................................................................................... 474
Preferences ...................................................................................................................... 476
Preferences ...................................................................................................................... 477
Preferences ...................................................................................................................... 478
Preferences ...................................................................................................................... 479
Preferences ...................................................................................................................... 480
Controller ...................................................................................................................................... 499
Status Window / Dashboard ...................................................................................................... 500
Log Manager Viewer .................................................................................................................. 502
Restart JVM ................................................................................................................................. 504
Flash Applicom Card .................................................................................................................. 505
Flash Applicom Card .................................................................................................................. 507
Restart Controller ........................................................................................................................ 508
Operator Pages ........................................................................................................................... 509
Documentation ............................................................................................................................ 510
Lesson Review ................................................................................................................ 511
Lesson Review ................................................................................................................ 512
Management of Change ........................................................................................................................ 513
Lesson Objectives ....................................................................................................................... 514
Available Documentation ........................................................................................................... 515
Software Products Server .......................................................................................................... 516
Documentation Portal ................................................................................................................. 517
Amphion Software Network ....................................................................................................... 518
Old Wiki* ....................................................................................................................................... 520
New Wiki ....................................................................................................................................... 521
Teamcenter – eng.nov.com ....................................................................................................... 522
Software Handling ....................................................................................................................... 533
Software Handling ....................................................................................................................... 534
SMOC ........................................................................................................................................... 535
Sourcing of Correct Software ........................................................................................ 537
 Document number 96780739 Page 11 of 544
Revision 1

Amphion Software Components ............................................................................................... 538

Amphion Software Components ........................................................................................................... 538
Golden Image .............................................................................................................................. 539
Points of Contact ......................................................................................................................... 540
Points of Contact (POC) ................................................................................................. 541
Redlines ........................................................................................................................................ 542
Redlines Documents....................................................................................................... 543
Lesson Review ................................................................................................................ 544
 Document number 96780739 Page 12 of 544
Revision 1

Introduction to Amphion

STUDENT NOTES:
 Document number 96780739 Page 13 of 544
Revision 1

Lesson Objectives

Course Completion Certificate

Students must attend the entire course and pass the final exam or practical with a minimum of an 80% in
order to receive a course certificate.

Course Description
This course is designed to train internal personnel on the hardware and software used in the workstation,
network and communications, diagnostic tools, Flares Main Page, ESTOPS, alarms, and troubleshooting.
Locating technical documentation relevant to the control system is covered. Participants will trace signal
paths, use third party tools for configuration, navigate SBC service pages, interpret alarms, 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 1.

Course Goals
At the conclusion of this course, the participants should be able to:
• Describe the Amphion system in general terms and safety aspects.
• Describe the hardware used in the Amphion system from the workstation down to remote I/O.
• Trace out signal paths in interconnection Schematic.
• Describe the Amphion main network and redundancy.
• Describe the different signal types in each network at each component.
• Trace out signal at addressing type level.
• Demonstrate use of third party tools for basic configuration and troubleshooting.
• Utilize the functions of SBC service pages for troubleshooting using a Flares Main page under
authorization
• Trace the cause and effect estops using DFSD documentation.
Document number 96780739 Page 14 of 544
Revision 1

• Interpret alarm severity when viewing the alarm screen.

• Discuss appropriate use of documentation related with service of Amphion.

STUDENT NOTES:
Document number 96780739 Page 15 of 544
Revision 1

Amphion Overview

STUDENT NOTES:
 Document number 96780739 Page 16 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Amphion Integrated Systems

Integrating rig controls and information improves the efficiency of rig operations while providing a safer
rig floor environment. Full Amphion Systems are furnished with one or more operator chairs allowing
operators to control the drilling process from a single location.

The Chair includes multiple Human Machine Interface (HMI) touch screens displaying the tool control
screens and alarm manager. Touchscreens are combined with carefully designed joysticks, discrete
controls and ergonomic workstations to allow "heads-up" control of moving equipment for maximum
operator efficiency. Graphically presented information and control screens are designed to optimize the
user interface, allowing rig equipment operators to focus on the crew and the drilling process, rather than
manual machine operation. Enhanced control, focus and decision-making increases rig safety and
efficiency, driving down drilling costs.
 Document number 96780739 Page 17 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Amphion is an Integrated Control System designed specifically for the demanding environment of a
drilling rig. Amphion is highly scalable and can be an effective solution to control a single tool application
or a dual-derrick drillship. The heart of the Amphion system is the embedded controller (SBC). The SBC
controller provides safe, reliable operation of equipment under its scope, delivering true multi-axes
machine control.

Amphion based control systems enable NOV tools to outperform competitive equipment, setting new
standards for functionality and ease of commissioning, Amphion Integrated Systems deliver SCADA
capability to new and existing rigs.
 Document number 96780739 Page 18 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Diagnostic functions are available from within the Amphion Service page, third party software and
licensing is not required.

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.

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.
Webobjects are the links between the real world (operator pages and I/O) and code, and allow viewing
and modifying of values.
 Document number 96780739 Page 19 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

On-screen joystick, buttons at top to adjust various parameters and set-points, push buttons to carry out
a specific function, Indicators on the right hand side of screens as well as status information shown in the
black bars at the bottom.
 Document number 96780739 Page 20 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

HMI’s can display any operator screen in any configuration to suit viewing preference.
An HMI failure doesn’t mean a tool can no longer be operated; it may be possible to use another HMI
until repair/replacement is carried out. There are structures in place (ownership and preferences) to
prevent any HMI/chair taking control of any tool. In extreme cases (full chair failure) NOV assistance may
be required to reconfigure a chair to restore/allow functionality.
 Document number 96780739 Page 21 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Several utilities are built into the Amphion Service Pages that provide software management functionality

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.

Software Installer permits upgrading specific software to a single or all controllers.

 Document number 96780739 Page 22 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Transfer Files link provides a way to navigate the various folders within the tool controller, and the ability
to copy, delete or modify the individual files contained within.

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).
 Document number 96780739 Page 23 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

Furthest right HMI can be used for CCTV allowing the operator to view all areas of the drill floor; the
individual cameras can be controlled directly from the HMI.
 Document number 96780739 Page 24 of 544
Revision 1

Amphion Overview

STUDENT NOTES:

In the oil industry, there is a growing appreciation of the importance of data logging. The ability to track
trends over time and to capture snapshots of well and tool behavior allows us to gain a better
understanding of the ever more complex tools and processes that we must use to continue to supply
energy to a growing world. National Oilwell Varco has a data logging system that is integrated into
National Oilwell Varco’s own Amphion control technology. The Amphion system can record data from
tools under its control.

The data logging graph viewer was designed as an engineering offline graphing application to allow
someone to display information obtained through the logging system.

User Manual D4B1000339-MAN-001

 Document number 96780739 Page 25 of 544
Revision 1

Driller’s Cabin

STUDENT NOTES:

NOV is customer driven company.

NOV can change and modify equipment to meet the customer need.
NOV has its standard design and these contents are based on the standard design.

Specially designed, climate controlled cabin that houses the operator workstation for the Amphion
System.
Basic features include: Heavy duty steel with a protection bumper in front, Protection grid for upper
windows, Electrical wipers with a high pressure wash system, HVAC unit, Non-slip floors, Recessed cable
routes with removable floor panels, BOP controls, Control and J-Boxes, Alarms horns, Telephone, PA
speakers, Thermostat and humidistat, HVAC control panels, Smoke detectors, CCTV monitors.

http://rigtours.nov.com/ME-2000.html
 Document number 96780739 Page 26 of 544
Revision 1

Safety Precautions

STUDENT NOTES:
 Document number 96780739 Page 27 of 544
Revision 1

Safety 24/7

STUDENT NOTES:

Culture of Safety 24/7

• Where everyone takes personal responsibility for their own safety, as well as those around them.
• Is a proven process that will help eliminate incidents, not only in the workplace, but in your
everyday life.
• To create an environment where individuals are motivated to work safely, are personally
accountable for his/her actions, and are willing to provide feedback to their teammates.
• A strong safety culture begins when we start making safety a habit – a habit we practice every
minute of the day. Since everything we do carries an element of risk, and our survival depends on
how well we manage those risks, even seemingly simple tasks – such as driving or how we sit at
our desk – should be risk assessed. The more hazards we can eliminate, the lower the risk.

Essential Concepts
• Having safety as a core value reduces turnover because people want to work for an organization
that genuinely cares about their safety.
• Policies, procedures, and equipment alone don’t make a strong safety culture, belief and trust do.
• All people are responsible for their own safety, as well as the safety of the people around them.
• To change a culture, we focus on peoples’ behaviors, consciously rewarding safe behaviors and
not tolerating at-risk behaviors.
• In a culture of safety, each of us has the right and responsibility to stop a job if we even suspect
there’s something unsafe about it.
 Document number 96780739 Page 28 of 544
Revision 1

Testing Safety

STUDENT NOTES:

Task is always about SAFETY!

The accompanying picture is a result of how fast things can go wrong.
Situation: Testing of Drawworks stop limits, Drawworks started a lowering operation from high position in
the derrick. Drawworks override functions were activated for stop limit, the operator let go the joystick
when the top drive was close to the floor, since the override was activated the top drive continue to
travel (coast to stop) causing the top drive to hit the drill floor.
Next time it can go way worse than this...
Ask yourself WHAT are you doing and WHY?! Are you 100% sure? Is what you are doing critical to
operation? Are there any alternative ways to solve this? What are my actions if things go horribly wrong?
And last but not least, WHAT can go wrong in a worst-case scenario and have I taken necessary
countermeasures?
Consider possible range of movement of equipment should a motor or cylinder ‘takes off’ at high speed,
and ensure the possible ‘swept’ area is cordoned off. When working with systems with devices spread
over a large area e.g. tanks with pumps and agitators consider if you can you see or ensure the area is
kept clear while you remotely operate equipment. If not involved, but in the area, beware that some
equipment can be started remotely/automatically – consider position and escape routes at all times.
Have a plan to revert to as found status if changes don't go as planned. There are SMOC processes in
place, but the same applies to hardware and troubleshooting.
 Document number 96780739 Page 29 of 544
Revision 1

Operation and Maintenance

STUDENT NOTES:

Safety considerations are covered within Amphion related documentation Chapter 1: General
Information, Conventions – Notes, Cautions and Warnings and Illustrations, Safety Requirements -
Personnel Training, Recommended Tools, General System Safety Practices, Replacing Components,
Routine Maintenance and Proper Use of Equipment.

Additional safety information is provided throughout documentation using the Notes, Cautions and
Warnings illustrations.

Notes, Cautions, and Warnings are used to provide readers with additional information and inform the
reader to take a specific action to protect personnel from potentially injurious or lethal conditions. They
may also inform the reader of an action necessary to protect equipment from damage.

Product Information Bulletins

Bulletins are initiated for the following reasons; Customer identifies an issue, Incident (DROPS, Tracker
Ticket), Issues identified during Product/Testing, Issues identified by Service/Repair, Product
improvement or obsolescence or Issues identified by warranty.

Bulletin Types, PIB – Product Information Bulletin, SA – Safety Alert, PIN – Product Improvement
Notification, POB – Product Obsolescence Bulletin and IPB – Internal Product Bulletin
 Document number 96780739 Page 30 of 544
Revision 1

A Product Information Bulletin (PIB) will be issued to a customer (end user) to communicate information
regarding proper operation, updated requirements, improved maintenance procedures, or retrofit
required for the product to meet the original functional specification.

A Safety Alert (SA) is a type of bulletin that specifically identifies a potential safety risk with the operation
of the equipment and, if known, corrective action. In an effort to quickly inform the end user of a possible
safety issue, an initial bulletin might be released before a full investigation is completed.

A Product Improvement Notification (PIN) is issued to a customer to specify product improvements for a
specific piece of equipment. A product improvement notification will be issued when there is an upgrade
available due to a new product development or new technology.

A Product Obsolescence Bulletin (POB) is released to inform the customer when NOV or our suppliers will
no longer supply a component, sub-component, or product. POBs will provide an NOV solution to the
obsolescence and provide customers with as much time as possible to implement the solution.

An Internal Product Bulletin (IPB) is distributed internally to advise Manufacturing, Spares and
Aftermarket of retrofit or upgrade opportunities and logistical or other equipment information. These
bulletins can be released in conjunction with a PIB or Safety Alert to inform NOV personnel of any
information or problems related to the equipment. This type of bulletin is NOT released to the customer
(end user) and does not require approval from NOV Legal.

*Service Engineers should have their own updated copies of PIB available before going to a job
 Document number 96780739 Page 31 of 544
Revision 1

Fail-Safe Theory

STUDENT NOTES:

A fail-safe in engineering is a design feature or practice that in the event of a specific type of failure,
inherently responds in a way that will cause no or minimal harm to other equipment, the environment or
to people. A system's being "fail-safe" means not that failure is impossible or improbable, but rather that
the system's design prevents or mitigates unsafe consequences of the system's failure. That is, if and
when a "fail-safe" system "fails", it is "safe" or at least no less safe than when it was operating correctly.

Example of Failsafe - ADS Brake

Depending on the hoisting capacity, the brake consists of between one and three water-cooled disc brake
plates coupled to a single air-cooled braking plate. Each disc has its own set of plates and brake pads that
are applied by either air or spring pressures. The air-cooled disc manages emergency stops and holds
loads while the water-cooled discs principally provide dynamic control. Air pressure must be applied to
compress the springs and release the brake. When air pressure is removed, the springs expand and the
brake is engaged. The brake applies braking torque to the drum assembly during both emergency stop
and parking operations. The brake assembly is mounted to one end of the drum shaft and is secured in a
brake support carriage.

The operators Emergency Stop button (located on the right control panel), is used in an emergency
situation. When pressed, the following events occur:
1. Shuts off power to the ADS.
2. Spring-applied brake actuator vented (brake applied).
3. Motor VFDs off.
 Document number 96780739 Page 32 of 544
Revision 1

EDS (Electronic Drilling System) is an example of a brake, which is from the same manufacturer and looks
similar, which is not failsafe as it is fitted as an auxiliary brake. It is air applied, spring release and there
have been instances of customers using the brake to hold the block and then carrying out maintenance or
switching off the air compressor and wondering why their blocks/TDS fall to the floor. Familiarize yourself
with equipment - looks the same but may not behave in the same way!

Equipment Protection
Various parameters are monitored to ensure that the equipment is operating properly and will not be
damaged by loss of utilities. Major parameters being monitored include:
• Lube oil pressure
• Brake air pressure
• Rig supply air pressure
• VFD and AC motor parameters
Loss of these services or components, or operation outside the recommended limits of these
components, may cause the control system to enter a fault mode and stop the ADS until the problem is
corrected. For some faults, a driller-initiated override is available to allow the block to move if the driller
determines that the overall safety of the rig is best served by continuing to operate the ADS, or associated
equipment.

See Alarm, Fault and Response Specification for faults and associated response (Example ADS-10SD, AC
Ideal Rig 163, 10862926-SPC)
 Document number 96780739 Page 33 of 544
Revision 1

Intrinsic Safety

STUDENT NOTES:

IS systems should not be bypassed or modified in any way without NOV engineering approval.

Intrinsically Safe (IS): is a protection technique for safe operation of electrical equipment in hazardous
area by limiting the energy, electrical and thermal, available for ignition in signal and control circuits that
can operate with low currents and voltages.

Areas with dangerous concentrations of flammable gases or dust are found on oil and gas installations in
areas such as drill floor, mud pits, and production areas. High-power circuits such as electric motors or
lighting cannot use intrinsic safety methods for protection.

For an explosion, all three of gas/dust, oxygen and source of ignition (spark or heat) need to be present.
Intrinsic Safety works on the principle of removing the source of ignition. This can be achieved by using a
Zener Barrier or Galvanic Isolator.

Principles of Intrinsic Safety - https://www.youtube.com/watch?v=7WkKw28QJZE

 Document number 96780739 Page 34 of 544
Revision 1

Drill Floor Shutdown – E-Stop

STUDENT NOTES:

System Overview
The DFSD system accommodates the required hardware and interface to facilitate an E-stop of NOV
supplied tools.
The DFSD system consists of, AC Circuit Breakers, Redundant 24 volt DC Power Supplies, Failsafe
Hardwired Relay Logic and Ethernet Remote I/O. The system provides a safe shut down of the interfaced
tools and equipment when required.

DFSD Theory of Operation / Control

E-Stop control is performed at 2 different levels:
• First, on a hardware level where by the relay logic in the DFSD system and in the individual tools
disables the load power from Remote I/O to all mechanical actuators. This is referenced as a
Category Zero E-Stop, (CAT 0).
• Secondly, in software where by the tools controller resets the logic to a safe state disabling the
outputs to the mechanical actuators. This is referenced as a Category Two E-Stop, (CAT 2).

Basic System Description

The DFSD system comes supplied with dual redundant 24 VDC power supplies. Each power supply is fed
from a different source which ensures full redundancy on the power supplies. The DFSD System is also
equipped with a Power Isolator Switch mounted on the DFSD Cabinet door which can be used to isolate
system power.
 Document number 96780739 Page 35 of 544
Revision 1

The DFSD system is designed with a series of control relays configured to provide either a CAT 0 or CAT 2
E-Stop to the various tools depending on how the E-Stop is activated. See the Cause and Effects Matrix to
determine for each E-Stop, which tools will be affected and what category Estop will be used.
Tools with Local E-Stop Push Buttons are supplied with control relays that monitor the status of the Local
E-Stop PB’s and provide an interface back to the DFSD system. Contacts from these control relays are
wired to a corresponding relay in the DFSD system. The Normally Open contacts of these DFSD relays are
connected in series so that the state of these relays will control a Master E-Stop relay. The Normally Open
contacts of the Master E-Stop relay are wired back to each tool to provide E-stop control of the tool, so
that if a local push button E-Stop is pressed the necessary stages of relays will be de-energized returning
the Master E-stop relay to its Normally Open State and disconnecting the load power from the tools
actuators as required for a CAT 0 E-Stop.
Select control relays within the DFSD system have contacts wired back to the DFSD Wago Ethernet I/O to
provide the control system with their status, this information is used by various controllers for either
control or information purposes.
The DFSD system also provides a signal interface back to the ADS tool controllers for the execution of a
CAT 2 control shut down when required. It should also be noted that there are some instances where the
ADS will be brought to a controlled stop only under certain E-Stop activation; this is to mitigate a
potentially more dangerous condition. The cause and effects matrix describes the various conditions.
After an E-Stop event has occurred and the E-Stop has been cleared all tools connected to the DFSD
system and Control System must be turned back “On” to regain control.

There are three kinds of tool emergency stop push buttons available:
• Locally by the tool
• The operator chair(s)
• Wireless remote control if applicable

If the rig has DFSD and more than one chair which can control the Drawworks or TopDrive, then a key
switch determines which chair can take ownership of that particular tool. This key switch also determines
the category of emergency stop applied to the tool when the controlling chair emergency stop is pressed.
Note that different tool responses to assigned and unassigned in the sample above and document linked
below.

A rig specific example can be viewed at http://eng.nov.com/TC_V3.swf?dn=11405486-IDX

Be aware that Estop/DFSD configuration can change for different installations

Document number 96780739 Page 36 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 37 of 544
Revision 1

Zone Management System

STUDENT NOTES:

The Zone Management System (ZMS) is a safety backup system that provides warning messages to
operators, and interlocks drill floor equipment in situations where collisions are likely to occur.
The system is software based and runs on an SBC within Amphion. It has few physical dedicated I/O and
relies on communication between the ZMS SBC and tool controllers and tool I/O.

General Operation
The ZMS system is either on or off. The ZMS On/Off key switch (Switch legend may indicate
Normal/Override as opposed to On/Off) is located on the front door of MTC where the ZMS SBC is
located. The switch digital input is used to indicate to the individual tool controllers whether the ZMS
System is on (enabled) or off (disabled). When ZMS is on, it automatically considers information being
received from all participants, notifies operators of any conflicts, and attempts to shut down any system
where a conflict exists or where communication has been lost.

System - On
When ZMS is operational the operators can have the ability to temporarily override ZMS system warnings,
enabling encroaching equipment to violate the safety buffer of other participant systems. The ZMS
operational mode is as follows:
• Unless ZMS is overridden, no two participating equipment systems are allowed to enter or occupy
the same physical space at the same time. Overriding ZMS can result in equipment collision,
possibly damaging equipment and jeopardizing personnel.
 Document number 96780739 Page 38 of 544
Revision 1

• If two participating systems are, inadvertently or by use of override, allowed to occupy the same
space, both equipment systems receive interlocking signals, and warning notifications are relayed
to their respective operators.
• When approaching any other participant, speed limiting and position limiting data are sent to the
encroaching system. In case the encroaching system does not respond or is not capable of
receiving these limits, the discrete enable signal is removed.
• When movement of encroaching equipment is toward another participant, prior to limits being
exceeded, ZMS notifies the operator of the encroaching system via existing communication
channels and operator interfaces.
• When movement of equipment is away from another participant, unless limits have been
exceeded, the equipment is allowed to retreat without limit, interlock or notification being sent to
the operator. If the limits have been exceeded, no movement is allowed, toward or away from the
conflict by either piece of equipment. Both systems are interlocked and appropriate messages are
sent to both systems.
• Individual tool overrides are physically located such that the operator of any participating
equipment does not also have access to the override for that equipment. The override should be
located near the operator of another piece of equipment such that a performance of cooperative
override is enforced. This means that both the operator of the encroaching equipment and the
operator of the equipment being encroached upon must both actively decide to enable movement
toward a participant system in order to continue. Note, however, that there are certain design
scenarios where a single operator may be required to control a machine and its corresponding
override for ZMS. These design scenarios include but are not limited to:
• Single chair systems
• Single console based systems
• Systems and equipment that a customer deems necessary for controlled manual intervention in
well control situations
• ZMS Tool lockouts are provided to facilitate maintenance or removal of any participant. When a
participant has been locked out, it does not receive an enable signal and has ZMS limits in all
directions so therefore cannot be operated due to ZMS interlocks. Additionally, the locked out tool
becomes essentially invisible to all other participants. This requires careful consideration of the
physical position of the participant being locked out prior to locking it out. If its physical position is
in the collision path of another participant, it will not be recognized and thus becomes a danger.

System - Off
ZMS provides an external ZMS Lockout input to all participants. When the system is OFF, all participants
will operate without Zone Management protection. This ZMS Lockout signal is independent of ZMS
controls and available to all participants for the specific case where ZMS control must be powered off. In
this case, it is impossible for ZMS to provide any information via interfaces, and all participants receive I/O
bus or dry contact status informing them that ZMS is OFF.

ZMS Visualizer
The ZMS Visualizer is a tool used by ZMS programmers and developers to ‘visualize’ the rig floor in the
ZMS virtual environment. It is used to give the programmer or developer a perspective of the drill floor
and to ‘see’ the environment as ZMS sees it, and it can also prove useful for troubleshooting by an FST.

The ZMS Visualizer should NOT be left running for any length of time longer than 5-10 minutes as it is very
resource intensive and can reduce the performance of parent SBC. This will NOT affect the ZMS integrity
 Document number 96780739 Page 39 of 544
Revision 1

(i.e. it will always result in stopping tools) but may result in slower operations of tools depending on its
feedback. As such it is not a tool that should be used in normal operational circumstances.
 Document number 96780739 Page 40 of 544
Revision 1

Zone Management System

STUDENT NOTES:

Equipment Override
Equipment overrides can be used to move equipment into zones where ZMS would normally prevent
movement. Operators can engage the override by using touchscreen controls or the workstation control
panel push button.
For safety reasons, the operator that has ownership of the tool cannot also engage its override.
This requires cooperation between the operator of the encroaching equipment and the operator of the
equipment being encroached upon to actively consent and maintain the decision to enable movement.

Note: Use equipment override controls with extreme caution. The tool ignores ZMS interlocks when its
override is engaged, allowing it to enter a zone already occupied or collide with another tool.
Significant risk of equipment damage and danger to personnel exists when an override is engaged.
Failure to follow safe work procedures could result in serious or fatal injury to personnel, significant
equipment damage, and extended rig down time.

Equipment Lockout
Use equipment lockouts (not ZMS lockout) to remove a tool from ZMS calculations (to perform
maintenance, for example). Tools locked out cannot receive “enable” signals from ZMS, and therefore
cannot be moved (except in maintenance mode). The tool becomes invisible to all other ZMS participants;
other tools can enter zones occupied by locked out equipment and collide with them.

Note: Locking out a tool using equipment lockout does not ensure that the tool will not move. Locked
out tools can be moved if the tool is in maintenance mode, or if ZMS is locked out (shut off; see below).
 Document number 96780739 Page 41 of 544
Revision 1

Never use ZMS Lockout to disable a tool for maintenance purposes. Proper lockout/tag out procedures
for electrical and hydraulic systems must be followed before performing tool maintenance.
Document number 96780739 Page 42 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 43 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 44 of 544
Revision 1

Equipment Overview

STUDENT NOTES:
 Document number 96780739 Page 45 of 544
Revision 1

Lesson Objectives

STUDENT NOTES:
Document number 96780739 Page 46 of 544
Revision 1

Workstations

STUDENT NOTES:
 Document number 96780739 Page 47 of 544
Revision 1

Swing Workstation/ Flex Workstation

STUDENT NOTES:

Overview
The Flex workstation is the user's interface to the control network and tools. Located in the driller’s cabin,
the Flex workstation contains:
• 3 touchscreens
• 1 WOB (weight on bit) indicator
• 2 joysticks
• 2 discrete switch control panels
• 1 chair

Ergonomics
• Foot rest bar
• Arm rest pads on consoles
• Seat assembly swings out so the operator can sit or stand
• Right console height adjustment
• Right console 20° to left and right
• Touchscreen height and tilt adjustment

Touchscreens
The Flex workstation contains three touchscreens, which are sometimes referred to as an HMI (human-
machine interface). They are rated for use in a safe area. Touchscreens display tool control, drilling
operation, alarm, and status information. By default, they display information pertinent to the activity
 Document number 96780739 Page 48 of 544
Revision 1

being performed, allowing the operator to concentrate on the job at hand without the distraction of
extraneous data.
Control Panels
Discrete switch controls are dedicated to frequently-used operations (such as opening and closing the
roughneck jaws). Joysticks are used for tools that require controlled movement.

Reference Document 42V-E8720-02 Revision A section 4-1

 Document number 96780739 Page 49 of 544
Revision 1

Front Entry Chair (Amphion-FEC)

STUDENT NOTES:

The Front Entry Chair, also known as the Amphion Sit Down Chair includes self-contained touchscreens
that display tool control, drilling operation, alarm, and status information. The Amphion Sit Down Chair
can accommodate up to four touchscreens, all with access to tools connected to the network; CCTV is also
available on the fourth touchscreen. On the back of the Amphion Sit Down Chair, the Backpack, contains
the SBC, disconnect switches, Moxa Ethernet Switches and all other components to allow for easy
installation and setup.

The chair is a maneuverable driller station which can be repositioned to enhance the driller’s awareness
depending on the function at hand. The chair assembly as a whole is an intelligent workstation comprised
of machinery controls because it includes all of the components necessary to allow the chair to function
as a standalone tool, down to the processor and I/O racks.
The HMIs can be set up to control many types of Amphion SBC based or third party equipment, including
but not limited to:
• Top Drives
• Drawworks
• Pipe Handling Equipment
• Fingerboard
• Iron Roughneck
• Pipe Racker
• Mud Pumps
• Power Slips
• Rotary Table
 Document number 96780739 Page 50 of 544
Revision 1

• Catheads
• HPU’s
• Rigsense
• CCTV
• Talkback System

General System Description

During normal operation, the Amphion Chair allows the driller to:
• Monitor and control multiple tools through the use of the HMIs and on-board controls.
• Adjust his position to allow for better views of the tool he is working with.
• Maximize his ability to perform multiple functions at the same time while maintaining safe
working conditions

Control System Chair Backpack Equipment

The Amphion Chair Backpack contains all of the control system equipment for the chair. This equipment
includes the Circuit Breakers, Power Supplies, a Redundant Power Module, the SBC, I/O Rack, and
Ethernet Switches.

19” HMIs
Each Amphion Chair comes standard with 19” Touchscreen HMIs. The chair can be configured to have 2, 3
or 4 HMIs mounted for operation. The number of tools on the network along with the additional optional
systems that were purchased for the rig will determine the number of screens. The typical setup is to
have two or three screens for tool control and instrumentation, and a fourth screen setup for the CCTV
system. Sometimes all four screens will be utilized for the tool control and a fifth CCTV HMI will be
remotely mounted in the Driller’s Cabin.

The HMI’s are connected to the tool network through Ethernet connections from the backpack. Any HMI
connected to this network can display any tool screens connected to the network. Since all of the 19”
HMIs are the same make and model, they can be easily interchanged in the case of a failure. The HMI’s
have customized screens for control of chair movement; Drawworks control, Auto Driller, Mud Pump
Control, Generator Status, MTC Cabinet Status, I/O status, Rigsense level etc. based on the Rig
configuration. The CCTV HMI is also connected through Ethernet connection from the backpack, but it is
on its own network, therefore it is unique and no other tool screens can be assigned to that HMI. If the
tools HMI screen fails, another screen can be assigned through a quick and easy wiring change in the chair
backpack.

Dual Axis Joysticks

The left and right armrests are both designed to house a dual axis joystick. The right arm will always have
a joystick, and depending on the Customer’s preferences a joystick may or may not be mounted in the left
arm. The joysticks are environmentally sealed with fighter grip handles and will spring back to center
position upon release. They are complete with pushbuttons, thumb wheels and Hall Effect sensors. The
joysticks are mirror images of each other and are oriented towards the side of the chair on which they are
mounted.

Deadman
The Deadman is a capacitive switch that is activated when the operator holds the joystick. If the Deadman
is not active during or before moving the joystick or pressing a button, then the Amphion Chair will not
 Document number 96780739 Page 51 of 544
Revision 1

send the command to the associated tool. This means that the Deadman must be activated before
attempting to use the joystick to control a tool. When the Deadman is active the buttons/thumbwheels
associated with a tool that is owned will light up white in addition the Amphion Chair operator screen has
a Deadman status associated with each joystick. When the Deadman is inactive, the joystick will not send
commands to a tool; however the Amphion Chair will always read the signals and display them on the
Amphion Chair operator screen.

AC Power Outlet and RJ-45 Jack

The chair comes standard with a remote access interface module that contains a single AC Outlet and a
RJ-45 Jack. This module is designed to give Field Service Technicians easy access to power and
communications for their laptops while troubleshooting. The outlet is a 120VAC or 220VAC, 3-wire outlet.
The entire assembly is housed in a base with a dust cover with securing latches that protects against dust
and splashing water.
The module is mounted on the underside of the left armrest. It is weatherproof and rated to IP54 when
the cover is locked down.

Alarm Horn
An alarm horn is mounted underneath the right armrest. This horn has an extra loud beep tone that
sounds at a medium rate. It is panel mounted with a volume control case and quick connects blades with
screw terminations. This alarm can be triggered by the Chair SBC for any tool on the network.

Auxiliary Equipment
The Amphion Chair is set up to control all of the major pieces of equipment currently controlled by
Amphion SBCs. It is flexible enough to incorporate other new pieces of equipment that are placed on the
tool network. For example, wiper system and chair adjustment controls and Talkback equipment for the
Driller’s Cabin will be integrated into the chair’s HMI controls on all NOV Driller’s Cabins.

Chair Adjustment
The seat frame of the chair is adjustable and it is not attached to the armrests. The chair has multiple
motors which allow the Driller to move the center column up and down and side to side. The armrests
and footrest are attached to the base, so the armrests remain fixed while the Driller adjusts his seat.
The chair is mounted on a ball bearing plate that allows it to have the ability to rotate up to 32 degrees in
either direction at the base. The footrest remains fixed to the center column with the chair as it rotates.
• Chair/Pedestal Up/Down
• Chair/Pedestal CW/CCW
• Chair Forward/Backward
• Chair Lean Forward/Backward
• Chair Seat Front Up/Down
• Chair Seat Back Up/Down
• Chair Foot Rest Up/Down
• Chair Traverse Left/Right

Talkback Equipment
Talkback Systems can easily be integrated into the Amphion Chair. A footswitch is integrated into the
footrest of the chair. The Driller will be able to press the switch with his foot and talk into a microphone
without having to do anything extra with his hands. The microphone is a unidirectional dynamic
microphone with a flexible stem.
 Document number 96780739 Page 52 of 544
Revision 1

A Volume control is provided for easy adjustment for the Driller on the chair left hand side. The Keypad
used for this is ideal for audio control without causing the sudden burst in volume or pop sound when
adjusted. This Keypad adjusts the gain of the pre-amplifier on the remotely mounted talk back Central
Junction Box in the Driller’s cabin.

Wiper System Controls

The wiper system controls are integrated into the Amphion Chair HMI screens. The wiper system is added
to the tool network by using a wiper interface junction box utilizing I/O Rack based system. The Junction
box is connected to the Amphion Chair backpack via Ethernet cable. The Driller will be able to control the
Cabin Wiper blades through the HMI soft buttons to perform all of the different wiper functions.

CCTV Auxiliary Equipment

Typical chair setups have two or three HMIs for tool control, instrumentation and a fourth screen setup
for the CCTV System. Additional HMI unit’s requirement due to space limitation on the chair is
accommodated by a remote HMI (fifth) for CCTV system on the Driller’s Cabin. This is typical when
additional tool controls are needed which cannot be covered by the four HMI’s. The remote HMI for CCTV
system needs a chair upgrade to house a CCTV Trackball with a USB Super Booster Extender. The trackball
and extender will allow the Driller to stay seated while controlling the remote CCTV screen.

Trackball
The trackball is constructed with a stainless steel ball, two stainless steel momentary pushbuttons and a
stainless steel carrier plate. A stainless steel trim protects the trackball and pushbutton sealing. The unit is
panel mounted and is sealed to the mounting with a silicone sponge. The ball diameter is 25mm. The IP
rating of the trackball is IP65 when the ball is static, and the resolution is 155 pulses per ball revolution.
The pushbuttons also have an IP65 rating, and they have gold plated contacts. No special device driver is
needed, as the trackball will easily interface with the HMI installed for the CCTV. The trackball is normally
located on the right hand joystick plate when this option is needed.

USB Superbooster Extender

The USB Superbooster Extender allows for CCTV Trackball to be installed at a distance up to 150 ft. from
the CCTV HMI. This Plug and Play device consists of a base unit and a remote unit connected together by a
standard Cat5, Cat5e, or Cat6 cable input and converts it to an Ethernet signal, and then the Base Unit
converts the Ethernet signal back into a Remote Unit signal to be plugged into the HMI. The extender will
be installed inside the right arm concealed from view.

Chair Cabling Details

The Amphion Chair requires many cables for the field interface. If an Interface Junction Box is installed, all
of these cables will come prewired through the Interface Junction Box allowing for easy installation. The
cable length normally comes with the chair has a length of 40 feet typically. If no Interface Junction Box is
installed, it will be up to the Customer to decide how many cables they would like to have preinstalled.
The three types of cables used are power cable, signal cables, and Fiber Optic cables. The power cables
are 3/C x 14AWG used for the UPSs and chair power. 12/C x 19AWG signal cables are used for talkback
components. Internal wiring for E-Stop functions is bundled in a 7C Signal cable for remote I/O cabinet.
Two fiber optic cables are used for the fiber ring network interface to the MTC cabinet. Ethernet cable is
used for the interface of chair wiper soft controls to the wiper interface box. Depending on the
configuration, additional Fiber and Ethernet cables may also be supplied for CCTV applications and
auxiliary controls.
 Document number 96780739 Page 53 of 544
Revision 1

The internal wiring of the chair is all done with cables. Ground wire is the only cable in the chair with
single conductor runs. Ethernet cable, Fiber, multicore 19AWG cable are the typical ones used in the
internal wiring of the chair. All the cables used are low smoke, zero halogen type.
The offshore Driller’s Cabins have the MTC cabinet installed remotely from the chair assembly. This is
achieved by providing an Interface Junction Box as part of standard supply due to the cable length
limitation from the chair. The interface box has terminal blocks, patch panels for interface of the cables
from chair to MTC cabinet. All the interfacing cables from the chair and MTC will be terminated in the
Interface Junction Box.

Reference Documents 10821106-FDS and 10625358-FDS

 Document number 96780739 Page 54 of 544
Revision 1

Wrap-Around Workstation (Amphion-WAW)

STUDENT NOTES:

The Wrap-Around Workstation, also known as the Amphion Sit Down/Stand Up Chair includes self-
contained touchscreens that display tool control, drilling operation, alarm, and status information. The
Amphion Sit Down/Stand Up Chair can accommodate up to four touchscreens, all with access to tools
connected to the network; CCTV is also available on the fourth touchscreen. The Pedestal of the Amphion
Sit Down/Stand Up Chair contains the SBC, disconnect switches, Moxa Ethernet Switches and all other
components to allow for easy installation and setup. The Amphion Sit Down/Stand Up Chair also has a
Hookload Gauge built in, and allows the operator to perform drilling operations while standing up or
sitting down.

Detailed information as per FEC chair on previous slide.

Reference Documents 10821106-FDS and 10625358-FDS

 Document number 96780739 Page 55 of 544
Revision 1

Rapid Rig Workstation (Amphion RRW)

STUDENT NOTES:

Operator Workstation
The operator workstation is the user's interface to the control network and tools.
Located in the driller’s cabin, the workstation typically contains:
• 1 Amphion touchscreen
• 1 joystick
• 3 control panels
• 1 chair
• 2 network switches

Touchscreen Computers
The workstation typically contains one self-contained touchscreen (sometimes referred to as an HMI, or a
human-machine interface). Touchscreens display tool control, drilling operation, alarm, and status
information. By default, it displays information pertinent to the activity being performed, allowing the
operator to concentrate on the job at hand without the distraction of extraneous data. All touchscreens
have access to any tool controller connected to the network.

Joystick
Joysticks are used for tools that require controlled movement, such as the Drawworks.
Unless the override is engaged, the trigger (also referred to as a “dead man switch”) mounted on the front
of the right joystick must be depressed in order to operate the equipment.
The joystick mounted near the right console controls the Drawworks, the funnels, and the power slips.
LEDs located along the bottom panel illuminate to indicate the current state of the power slips.
 Document number 96780739 Page 56 of 544
Revision 1

Workstation Consoles
All three consoles contain gauges and readings, in addition to tool controls. Controls are dedicated to
frequently-used operations (such as opening and closing roughneck jaws).
The left (centre) console contains controls for:
• Top Drive System (TDS):
• Enable
• Pipe Handler
• Mode
• IBOP
• Brakes
• Direction
• Speed Set point
• Drill and Makeup Torque Set point
• Alarm LED Test and Silence
• Drawworks Override
• Generator Emergency Stop
The bottom right console contains controls for:
• Mud Pump Throttle Set point
• Mud Pump Emergency Stop
• HPU Start/Stop
• ST-80 Roughneck:
• Torque Set point
• Enable
• Mode
• Arm Adjust
• Deploy
• Jaws
• Spin
• Torque Wrench
• Stabbing Arm
• Hoist

Reference Document D811000323-MAN-001

 Document number 96780739 Page 57 of 544
Revision 1

Cyberbase Workstation Versions 4, 6 and 7

STUDENT NOTES:

Introduction
The Cyberbase control system is a modern integrated and distributed control system based on industrial
computers interconnected in a network. From the Cyberbase operator stations, the drill crew will have full
control of drilling related machinery. These operations are monitored by on-screen instrumentation,
integrated with real-time video from CCTV cameras. The Cyberbase control system is designed with a high
level of attention paid to aspects such as security, ergonomics and operational efficiency.

Cyberbase Operator Station

The base of the chair holds the Cyberbase PLC, and fibre optic communication equipment. The Cyberbase
server is located in the network cabinet.

Components
Two screens, one mode switch, one machinery emergency stop button, two joysticks for machinery
control, two keypads with throttle wheels for machinery control, one trackball (mouse) and one numerical
keyboard with shortcut buttons.
Cyberbase has developed by 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 the two arm pads
and control surfaces. The monitors with two separate screens for displaying drilling data. The pedestal
 Document number 96780739 Page 58 of 544
Revision 1

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.
On some Cyberbase systems with SBC controlled tools the SBC pages may be accessed within the
Cyberbase screens, typically required for calibration.

Reference Document S01G8284-TD-001

Document number 96780739 Page 59 of 544
Revision 1

Amphion Hardware Hierarchy Overview

STUDENT NOTES:
 Document number 96780739 Page 60 of 544
Revision 1

Amphion Hierarchical Overview

STUDENT NOTES:

Key:
Blue - Ethernet (CAT 5e, RJ45 to RJ45)
Red - Fiber Optic
Purple - Industrial Bus (Profibus)
Black - Hard Wired
Green – Industrial Bus (various)

This slide shows the layout of an Amphion system split into four distinct areas: each component of which
will be discussed in greater detail in the slides that follow

Operator - Shows where the operator interacts with the Amphion system; via a Touch Screen HMI or the
chair mounted Joysticks, Switches and Controls.
The Touch Screen HMIs are connected to the Ethernet communications network via an RJ45 Ethernet
ports on the HMI and Moxa Ethernet switch.
The chair mounted Joysticks are connected to terminals on a J1939 (Canbus to Ethernet) converter, which
is connected to the Ethernet communications network via RJ45 ports on the converter and a Moxa
Ethernet switch.
The Switches and additional controls (e.g. Chair Arms) are directly connected or hard wired to the Wago
Ethernet I/O.

Ethernet – Ethernet communication is supported by the use of Moxa Ethernet Switches, Multiple switches
are used in several different locations including MTC Cabinet, MCC Cabinet, Driller Chair and Assistant
 Document number 96780739 Page 61 of 544
Revision 1

Driller Chair. The switches are connected to each other using Fiber Optic cable; each switch has six RJ45
ports which are used to connect hardware such as HMIs, SBCs and Wago Ethernet I/O.
Wago Ethernet I/O is connected to the Ethernet communications network using RJ45 ports on the Wago
BusCoupler and Moxa Ethernet Switch.
SBCs are connected to the Ethernet communications network via RJ45 ports on the SBC and Moxa
Ethernet Switch and can be referred to as either Tool Controllers (An SBC in which the Compact Flash card
is programmed to automate a specific piece of equipment) or a Gateway (An SBC which is programmed to
act as an interface or interpreter between Amphion and a non-Amphion controlled tool, e.g. Catwalk
Machine which is Siemens S7 controlled but can still be interacted with from an Amphion operator
screen), the physical hardware used in either case is the same.

Industrial Buses – There are several different communication buses. NOV as standard will always use
Profibus DP (Decentralized Periphery) to connect SBCs to their associated remote I/O. An SBC which has
Profibus remote I/O will have an additional piece of hardware called an Brad Communications Applicom
I/O Card, this allows the SBC to send commands to and/or receive status information from Profibus slave
devices connected to that piece of equipment. Other communications buses can be used where a
customer specifies, e.g. Modbus, Canbus or other when non NOV equipment is to be interfaced into the
Amphion system.

Rig Tools – This is where actual I/O is directly connected to a piece of equipment. A Profibus cable will be
ran to an electrical junction box mounted in close proximity to the tool. Contained within the junction box,
for example, is a bank of Wago Profibus I/O into which the individual sensors and output devices are
hardwired.

Scenarios shown in diagram (l-r)

Tool controller with Wago Programmable Field Controller e.g. power system with chopper and inverter
Wago controllers.
SBC gateway to third party control system – varies, but just about anything can be accommodated.
SBC gateway to Siemens PLC with Profibus I/O. See Ensco 120 series rigs for NOV supplied PLC controlled
catwalk machine integrated with Amphion.
SBC tool controller with VFDs and remote I/O on Profibus e.g. TDS or PRS.
Wago Ethernet I/O on main Amphion Ethernet ring e.g. common I/O such as MCC.
Document number 96780739 Page 62 of 544
Revision 1

Operator

STUDENT NOTES:
Document number 96780739 Page 63 of 544
Revision 1
 Document number 96780739 Page 64 of 544
Revision 1

Touch Screen (HMI)

STUDENT NOTES:

Operator Interface Overview

The Operator Interface in an Amphion System is a mix of physical discrete controls and controls that are
‘under glass’ that is controls that reside on an HMI touch screens. These touch screens allow the operator
to interact with and read data from the tool or tools that he currently has ‘ownership’ of.

Amphion Touch Screen controls

Amphion workstations can have between one and four HMIs... This depends on the customer
requirements and the application. It is important to differentiate between an Amphion Tool Page and an
Amphion HMI Touchscreen. The touchscreen is the hardware monitor that is used by the operator to call
up (or navigate to the various Amphion Tool Pages so that he can interact with that particular tool. The
Amphion Tool Page is the graphic virtual operator’s panel that is displayed on the Amphion Touchscreen
and allows the interaction.
Whilst every Amphion Tool Page is designed around its specific tool, there a number of things that are
common to all tools…

Main Operator Screen

This is the main page that the operator uses in order to operate the tool in its normal mode of operation.

Backup Screens
The backup page allows the operator to drive a particular tool complete from ‘under glass’ commands.
This allows the tools to still be driven in the unlikely event of a discrete or joystick control failure.
 Document number 96780739 Page 65 of 544
Revision 1

Touch Screen (HMI)

STUDENT NOTES:

Calibration and Setup Pages

All tools that have some form of calibration are supplied with basic calibration and setup page. Calibration
pages are known to cause problems. They are often not properly debugged during I&C, people use debug,
but then when in the field the customer uses calibration pages and end up with problems. Create a varball
or upload a copy of objects.csv prior to calibration in case a page issue is present. Report the issue to tech
support/engineering.

Diagnostics Screens
Where possible all tools have diagnostic screens to assist the operator and technical persons in
troubleshooting. There are two levels of diagnostic screens – Operator Diagnostics and Service Diagnostic
Screens. The Operator Diagnostics are available from the Operator Screens whereas the Service
Diagnostics are only available from the Service Pages. The Service pages can be navigated to via a laptop
(with no special software other than MS Windows and Internet Explorer.
 Document number 96780739 Page 66 of 544
Revision 1

Touch Screen (HMI) Ownership

STUDENT NOTES:

Ownership Philosophy
Ownership of a tool can only be taken when the tool is not Estopped and available. When one station
(such as the Driller or a Local station) owns a tool no other station, except a master local station, will be
able to take ownership away. Two stations cannot own a tool at the same time. Only when a station owns
a tool, will the associated Chair or Local station be allowed to write commands to that tool.

Tool Ownership
The term ownership refers to a tool or a number of tools that the operator currently has control of at the
workstation where they are currently situated. Some tools use the same controls as other tools (a Pipe
Racker and a Drawworks for example); because of this there are scenarios where the operator may not
take ownership of both these tools at the same time from the same location.
Every Tool has an ownership button that is used to take and release ownership of the tool. There is also a
‘Release All’ button that will allow all tools at that station to be released from ownership.
Whilst a tool is not owned or released from ownership it will not respond to any operator commands from
any of the available Operator Interfaces.

Ownership Exclusions
Due to the fact that some controls overlap on the Amphion Chair Joysticks, certain tools should not be
able to be owned at the same time by the same station. If by chance two tools that share the same
Joystick function (Axis, Button, or Thumbwheel), then the Chair will generate an alarm message on the
operator screen and the Joystick Error LED’s on both Joysticks will begin to flash.
 Document number 96780739 Page 67 of 544
Revision 1

Ownership Scheme

Available (Green)
A tool is Available when it is not in an Estop condition and it is not owned by the Driller, AD, or locally
owned. When a tool is Available, it will stop sending outputs and the workstation will not be able to send
commands to the tool. In this mode, it is possible for a station to take ownership of the tool.

Owned (Orange)
When a tool is owned, it becomes active and is able to receive commands from the workstation and send
outputs to IO and its drive(s). The operator screen for the tool does not need to be on an HMI for the tool
to remain active. Only removing ownership and returning it to an Available state or an Estop condition will
the tool be inactive.

Estop (Red)
A tool is in Estop when it stops receiving the Estop signal. This is done so if there is a wire-break in the
Estop circuit, then the system will shut down and give an alarm instead of appearing to be functional.
When a tool is in Estop, it will stop sending outputs and the workstation will not be able to send
commands to the tool. Workstations monitor Estop signals, but do not have an Estop condition.
 Document number 96780739 Page 68 of 544
Revision 1

Touch Screen (HMI) Alarms

STUDENT NOTES:

System Alarms
The navigation menu bars Alarms button flashes red when there is at least one active and
unacknowledged alarm. The button displays solid red when there is at least one active, but already
acknowledged, alarm. Otherwise the button displays solid blue.
Select a tool from the Alarms Menu, or choose a tool, and select Alarms to display the Alarms message
window.
The alarm system will displays and stores the most recent 200 alarms from the currently selected tool.
 Document number 96780739 Page 69 of 544
Revision 1

Touch Screen (HMI) Alarms

STUDENT NOTES:

Alarms display in the following order of importance:

• Red – Indicates that the alarm condition is active and the alarm has not been acknowledged.
(Unacknowledged/Active)
• Orange – Indicates that the alarm condition is inactive, but has not been acknowledged
(Unacknowledged/Inactive)
• Yellow – Indicates that the alarm condition was acknowledged, but the alarm condition is still
active (Acknowledged/Active)
• Grey – Indicates that the alarm condition is inactive and has been acknowledged
(Acknowledged/Inactive)

Pressing any of the sort buttons (located along the top of the Alarms screen) will sort by Default,
Description, Active date and Inactive Date

Pressing the Acknowledge Page button will acknowledge all alarms currently displayed on the page.
Alarms can be acknowledged individually by pressing any individual alarm, a pop up will appear displaying
the alarm in more detail along with buttons to Acknowledge the alarm or Close the pop up. The alarm
detail includes an alarm ID, a description of the alarm condition, the date and time that the alarm was
tripped, cleared, and acknowledged, as well as its group priority and status.
 Document number 96780739 Page 70 of 544
Revision 1

Amphion Generation 1/2 Differences

STUDENT NOTES:

Generation 1 is www 1.6.12 and below

Generation 2 is www 1.7.0 and above (available from approximately 2012, but not all rigs built after this
date will be gen 2).
Main differences other than firmware are joysticks and HMIs.
 Document number 96780739 Page 71 of 544
Revision 1

Generation 1 Joysticks

STUDENT NOTES:

Analogue Joystick Controls

Amphion workstations also have Analog Joysticks which are used to drive tools such as Automated
Roughnecks, Pipe Racking Systems and Drawworks. The joysticks always have ‘dead-man’ switches which
prevent accidentally actuation of the joystick and hence the accidental movement of a tool. The joysticks
are analogue in nature and are used where finite speed and/or torque control of a tool is required
dynamically.

Dead-man switches were mostly mechanical so not comfortable over extended periods of operation.
 Document number 96780739 Page 72 of 544
Revision 1

Generation 1 Control Panels

STUDENT NOTES:

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 73 of 544
Revision 1

Generation 2 Joysticks

STUDENT NOTES:

Deadman
The Deadman is a capacitive switch that is activated when the operator holds the joystick. If the Deadman
is not active during or before moving the joystick or pressing a button, then the Amphion Chair will not
send the command to the associated tool. This means that the Deadman must be activated before
attempting to use the joystick to control a tool. When the Deadman is active the buttons/thumbwheels
associated with a tool that is owned will light up white in addition the Amphion Chair operator screen has
a Deadman status associated with each joystick. When the Deadman is inactive, the joystick will not send
commands to a tool; however the Amphion Chair will always read the signals and display them on the
Amphion Chair operator screen.

Dual Axis Joysticks

The joysticks are bi-directional with +/-20 degrees of travel in the X and Y directions. Hall Effect sensors
are mounted on both axes to identify the position of the joystick at any time during movement. Y-axis
sensors are redundant for increased reliability. Five pushbuttons are mounted on the top of the handle.
Each pushbutton is multi-colored when the Joystick is activated, with white color as normal state and blue
color on touch. This color change indicates the status of the pushbutton controls. Between the top three
and bottom two pushbuttons are two thumb wheels. The thumb wheels are oriented to operate in the
North/South positions and will also light up according to the function they are controlling. They also
spring back to center position on release.
The back of the joystick also has a thumb wheel and another pushbutton. The thumb wheel springs to
center and is oriented in the East/West position.
 Document number 96780739 Page 74 of 544
Revision 1

The Joystick itself is capacitive in nature. It senses when hand wraps around the Joystick to activate the
input circuitry for the push buttons on the Joystick. This must be activated for the control system to
receive and act on any signals received from the joystick. It is a safety feature to ensure no movement on
any equipment if the Driller accidentally activates the joystick.
The joysticks connect to chair control via CANbus module using CAN J1939 protocol. The joystick comes
with a four conductor flying lead for the CANbus and power signals. All signals from the joystick handle
are gathered into the CANbus base and are terminated into the CANbus module. This simplifies cabling
significantly. The signals are then sent to a J1939 converter module. From there, the signals are sent over
Ethernet to the chair center column or backpack.

Axis Control

Proportional Commands
All axes on the Amphion Joysticks (X/Y axis or Thumbwheels) have the ability to send proportional signals
to the associated tool. When the Deadman is active and the tool is owned, as long as there are no error
indications (error input or position errors) the joystick will send a numeric command to the tool based on
the joystick position. By default the Amphion Chair will send a command of -100 to 100. This is used in the
Drawworks throttle command by default.

Incremental Throttle
All axes on the Amphion Chair (X/Y axis or Thumbwheels) have the ability to send incremental throttle
signals to the associated tool. When the Deadman is active and the tool is owned, as long as there are no
error indications (error input or position errors) the joystick will send a numeric command to the tool
based on the joystick position. By default the Amphion Chair will send a command of -100 to 100. This is
used in the Drawworks throttle command by default.

Negative/Positive Direction
All axes on the Amphion Chair (X/Y or Thumbwheels) have the ability to send bit signals to associated
tools. When the Deadman is active, the tool is owned, and the axis has been moved to +/- 95% of its
mechanical travel distance the Amphion Chair will send a bit command (as long as there are no error
indications). This is used in the Cathead Pay/Pull, the Top Drive Dolly Extend/Retract and the Top Drive
Links Drill/Tilt commands by default.

Button Control
All buttons on the have the same control scheme. When the Deadman is active and the tool is owned, the
Amphion Chair will send a bit command to the associated tool when the button is pressed. When that
happens, the button will also light up blue.
 Document number 96780739 Page 75 of 544
Revision 1

Generation 2 Left Joystick

STUDENT NOTES:

NOV Typical Left Control Joystick Button Functions of Gen 2

Key:
1. Top Drive INC/DEC
2. Top Drive Zero Throttle
3. Mud Pump INC/DEC
4. Mud Pump Pause/Resume
5. Active Mud Pump Select
6. Optional

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 76 of 544
Revision 1

Generation 2 Left Joystick Directional Control

STUDENT NOTES:

NOV Typical Left Control Joystick Directional Control

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 77 of 544
Revision 1

Generation 2 Right Joystick

STUDENT NOTES:

NOV Typical Right Control Joystick Button Functions

Key:
1. RLA Rotate CW/CCW
2. Drawworks Slow Mode
3. Elevators Open
4. Elevator Link Float
5. Power Slips Frame Raise
6. Dolly Auto Extend/Retract
7. Power Slips Frame Lower
8. Elevator Links Tilt/Drill Down
9. Elevator Arm/Close

The joystick mounted on the operator workstation’s right control panel can control:
• The Drawworks
• The Drawworks and the Power Slips
• The Racker

The tool or tools that a joystick controls depends upon your particular rig configuration and tool
ownership. Tool ownership logic prevents the operator from taking ownership of both the Drawworks and
the Racker simultaneously. Using the joystick to move the Racker affects its destination, which varies
depending on its current mode (selected via the user interface).
 Document number 96780739 Page 78 of 544
Revision 1

If the joystick does not offer Power Slip controls, then the workstation’s control panel normally contains a
discrete switch for opening and closing the slips. This is in addition to touchscreen controls.

If the joystick has the ability to control both the Power Slips and the Drawworks, the workstation’s control
panel will not contain controls for opening and closing the power slips. However, the control panel will
contain a button that must be pressed in order to enable the power slips and allow the operator to
control the slips by using either the joystick or touchscreen controls.

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 79 of 544
Revision 1

Generation 2 Right Joystick Directional Control

STUDENT NOTES:

NOV Typical Right Control Joystick Directional Control of Gen 2

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 80 of 544
Revision 1

Generation 2 Left Control Panel Example

STUDENT NOTES:

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.

Discrete controls
Amphion Work Stations usually consist of discrete controls that are used to control such functions as
brake release of Drawworks, Open Close of Tool Jaws and Clamps etc., and generally any function that
moves a tool or piece of heavy machinery in a motion where it’s not simply rotating. The discrete inputs
are digital inputs and always have a spring return to center. Hard wired switches can duplicate functions
available on the HMI screens and are “stateless”, so pushbuttons and Toggle switches are momentary-
contact and spring return to a neutral so that the switch does not “remember” its state). The state (on,
off, forward, reverse, whatever) is stored in the SBC and can be changed from either the mechanical
switch or the HMI.

E-Stop Pushbuttons
Each armrest will include E-Stop Pushbuttons. The left arm E-Stops will be reserved for the Mud Pump
Shutdown and the Generator E-Stops. The right arm E-Stop is assigned for the Drill Floor Shutdown.
Each E-Stop Pushbutton comes with two normally closed contacts which allows for multiple signal inputs
to the control system. They are hardwired into the control circuit and are monitored by the control
software.
 Document number 96780739 Page 81 of 544
Revision 1

Discrete Switch Option

The plate on the left and right arm side of the chair comes equipped with the option of joysticks and
Estops or with additional discrete switches and pushbuttons. The plates can house up to any combination
of six 22mm pushbutton and switches each. The number of discrete switches necessary will be
determined by the equipment installed on the rig. The plates can be easily removed and replaced, if
alterations are required due to equipment changes.
 Document number 96780739 Page 82 of 544
Revision 1

Generation 2 Right Control Panel Example

STUDENT NOTES:

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.

Analogue Encoder Controls

An Amphion workstation may also have Analog Encoder controls which are used in order to control
various tools such as the Top Drive, Rotary Table and Mud Pumps. These are predominantly used for
tactile speed control where the operator can make very minor but accurate changes to the speed setpoint
of these tools by turning the appropriate rotating knob on the Amphion Chair. These controls are always
duplicated under glass and either of the control methods can be used at any time whilst the tool is owned
at that specific chair.
 Document number 96780739 Page 83 of 544
Revision 1

Generation 2 Joystick Help

STUDENT NOTES:

Key:
1. Deadman
2. Rotary Table Jog CW
3. Cathead Pay
4. Cathead Pull
5. Rotary Table Jog CCW
6. Deadman

Various joystick controls are labeled on the Joystick Help screen. The labels on the joystick buttons and
sliders change, depending upon the currently-selected tool. For example, the cathead and rotary table
controls are labeled in the image shown here.

Functions shown are typical but the customer/rig can request customization of buttons and joystick
functions – ensure you familiarize yourself with any rig specific customization.
 Document number 96780739 Page 84 of 544
Revision 1

Generation 1 (15 inch) and Generation 2 (19 inch) HMIs

STUDENT NOTES:

Due to screen size and increasing complexity/functionality of tools, multiple operator pages were
required per tool for operation. This resulted in duplication of, or lack of information, on certain pages. In
the gen 1 displayed on the left the central buttons and indicators would change depending on which top
drive function was selected using the buttons to the right of the page.

With the introduction of 19 inch screens in generation 2 more information could be displayed on one
page, reducing the number of page swaps required by the operator to achieve the same control and view
the same information.

Images not to scale.

 Document number 96780739 Page 85 of 544
Revision 1

Diagnostic Work Station (DWS)

STUDENT NOTES:

The Diagnostic Workstation is an HMI providing ET or engineering access to the Amphion network. The
DWS is panel door mounted and can be found on the MTC or MCC cabinets, the panel also has a door
mounted keyboard and integrated mouse for interaction with the HMI/Amphion software.

The DWS allows viewing only access to tool control screens but is the only HMI whereby a Maintenance
Mode can be activated.

Amphion Service Pages can be accessed from this HMI, allowing software management, troubleshooting
or configuration to be carried out without need for an additional laptop. The ET can utilise the USB ports
to back-up, restore or upgrade Amphion software.

The ‘desktop’ features of this HMI are available as this HMI doesn’t operate in a kiosk mode. Kiosk mode is
an operating system (OS) feature that only allows one application to run. The operator HMI only allow the
Amphion operator screens to be shown and hide any of the other PC based features.
 Document number 96780739 Page 86 of 544
Revision 1

Generation 1 SBC Service Page

STUDENT NOTES:

This page is for the WWW 1.5 -1.6 version

 Document number 96780739 Page 87 of 544
Revision 1

Generation 1 Collect Debug Information

STUDENT NOTES:

This page is for the WWW 1.5 -1.6 version.

 Document number 96780739 Page 88 of 544
Revision 1

Generation 1 Consistency Checker

STUDENT NOTES:

This page is for the WWW 1.5 -1.6 version.

 Document number 96780739 Page 89 of 544
Revision 1

Generation 2 SBC Service Page 2

STUDENT NOTES:

This page is for the WWW 1.7.0 version and above.

The Software Manager link was introduced. This page merges several features into one page (consistency
checker, software versions, backup and restore) and allows these actions on more than one SBC at a time.
The Preferences function was introduced to provide more flexibility in managing the security, access and
profiles of workstations (HMI, DWS and laptops) connected to Amphion.
Caution should be exercised when using functions which affect several SBCs at once.
 Document number 96780739 Page 90 of 544
Revision 1

Generation 2 Collect Debug Information

STUDENT NOTES:

This page is for the WWW 1.7.0 version and above.

With gen 2 collect debug information can now be initiated on several SBCs at once. Caution should be
exercised when using functions which affect several SBCs at once.
 Document number 96780739 Page 91 of 544
Revision 1

Consistency Checker Gen 2

STUDENT NOTES:

This page is for the WWW 1.7.0 version and above.

Two new columns were added (highlighted above).
Document number 96780739 Page 92 of 544
Revision 1

Ethernet

STUDENT NOTES:
Document number 96780739 Page 93 of 544
Revision 1
 Document number 96780739 Page 94 of 544
Revision 1

Multi-tool Controller Cabinet (MTC)

STUDENT NOTES:

The MTC houses most of the electronic equipment, including:

• Single Board Computers (SBCs), both tool controllers and gateways
• Network switches (typically Moxa)
• Remote I/Os (typically Wago)
• Optical Link Modules (OLMs)
• Power supplies
• Circuit breakers
The MTCs are located in safe areas such as
• The Local Electronic Room (LER)
• Drillers cabin
• Power House
Some rigs have multiple MTCs for drill floor equipment and power systems i.e. Drillfloor MTC and Power
MTC.
 Document number 96780739 Page 95 of 544
Revision 1

Single Board Computers

STUDENT NOTES:

Single Board Computers (SBCs) are used both as tool controllers and as gateways (to tools not made for
Amphion). Each tool controller is programmed with the logic required to automate and monitor a specific
piece of rig equipment. The touch screen accesses the SBCs own web page, then the operator can send an
input to the SBC which in turn controls the tool.

Detailed information on various hardware versions can be found in level 0 student handbook, RigDoc
96747643.
 Document number 96780739 Page 96 of 544
Revision 1

Network Switches

STUDENT NOTES:

The network switches (typically Moxa switches), arranged in a redundant ring, are the backbone of the
Ethernet network.
 Document number 96780739 Page 97 of 544
Revision 1

Network Switches EDS 408A-MM-ST

STUDENT NOTES:

Key:
1. Grounding Screw
2. Terminal block for power input PWR1/PWR2 and relay output
3. Heat dissipation vents
4. Console port
5. DIP switches
6. Power input PWR1 LED
7. Power input PWR2 LED
8. Fault LED
9. MSTR/HEAD: LED indicator
10. CPLR/TAIL: LED indicator
11. TP port’s 100Mbps LED
12. TP port’s 10Mbps LED
13. Model name
14. 10/100BaseT(X) ports
15. 100BaseFX ports
16. FX port’s 100 Mbps LEDS

Wiring the Relay contact

The two middle contacts of the 6-contact terminal block connector are used to detect both power faults
and port faults. The two wires attached to the fault contacts form an open circuit when:
 Document number 96780739 Page 98 of 544
Revision 1

A relay warning event is triggered. OR The EDS-408A-MM-ST is the Master of this Turbo Ring, and the
Turbo Ring is broken. OR There is a start-up failure.
If none of these three conditions is satisfied, the fault circuit will remain closed.

Wiring the Redundant Power Inputs

The top two contacts and the bottom two contacts of the 6-contact terminal block connector on the EDS-
408A-MM-ST top panel are used for the two DC inputs. Both power inputs can be connected
simultaneously to live DC power sources. If one power source fails, the other live source acts as a backup,
and automatically supplies the EDS-408A-MM-ST with power.

Communication Connections
EDS-408A-MM-ST models have 6 10/100BaseT (X) Ethernet ports and 2 100BaseFX (ST-type connector)

10/100BaseT(X) Ethernet Port Connection

The 10/100BaseT(X) ports located on the EDS’s front panel are used to connect to Ethernet-enabled
devices

100BaseFX Ethernet Port Connection

The concept behind the ST port and cable is quite straightforward. Suppose you are connecting devices I
and II; contrary to electrical signals, optical signals do not require a circuit in order to transmit data.
Consequently, one of the optical lines is used to transmit data from device I to device II, and the other
optical line is used transmit data from device II to device I, for full-duplex transmission. Remember to
connect the Tx (transmit) port of device I to the Rx (receive) port of device II, and the Rx (receive) port of
device I to the Tx (transmit) port of device II.

Auto MDI/MDI-X Connection

The Auto MDI/MDI-X function allows users to connect the EDS-408A-MM-ST 10/100BaseTX ports to any
kind of Ethernet device, without needing to pay attention to the type of Ethernet cable being used for the
connection. This means that you can use either a straight-through cable or cross-over cable to connect the
EDS-405A/408A to Ethernet devices.
 Document number 96780739 Page 99 of 544
Revision 1

Network Switches EDS 408A-MM-ST

STUDENT NOTES:

Turbo Ring DIP Switch Settings

The proprietary Turbo Ring protocol was developed by Moxa to provide better network reliability and
faster recovery time. Moxa Turbo Ring’s recovery time is less than 300 ms (Turbo Ring) or 20 ms (Turbo
Ring V2)—decreasing the possible loss caused by network failures in an industrial setting.
There are 4 Hardware DIP Switches for Turbo Ring on the top panel of the EDS-408A-MM-ST that can be
used to set up the Turbo Ring easily within seconds. If you do not want to use a hardware DIP switch to set
up Turbo Ring, you can use a web browser, Telnet, or console to disable this function.

If you do not enable any of the EDS-408A-MM-ST switches to be the Ring Master, the Turbo Ring protocol
will automatically choose the EDS-408A-MM-ST with the smallest MAC address range to be the Ring
Master. If you accidentally enable more than one EDS-408A-MM-ST to be the Ring Master, the EDS-408A-
MM-ST switches will auto-negotiate to determine which switch will be the Ring Master.

To switch on the Master or Coupler functions of the DIP switch, you need to enable the Turbo Ring Pole
first.
 Document number 96780739 Page 100 of 544
Revision 1

Network Switches EDS 408A-MM-ST

STUDENT NOTES:

LED Indicators
1. PWR1/2 (Amber) On – Power is being supplied to power input. Off – Power is not being supplied to
power input
2. FAULT (Red) On – When a relay warning event is triggered, the EDS-408A-MM-ST is the Master of
this Turbo Ring, and the Turbo Ring is Broken, or start-up failure. Off – When a relay warning event
is not triggered
3. MSTR/HEAD (Green) On – When the EDS-408A-MM-ST is set as the Master of the Turbo Ring, or as
the Head of the Turbo Chain. Blinking – The EDS-408A-MM-ST has become the Ring Master of the
Turbo Ring, or the Head of the Turbo Chain, after the Turbo Ring or the Turbo Chain is down. Off –
When the EDS-408A-MM-ST is not the Master of this Turbo Ring or is set as the Member of the
Turbo Chain.
4. CPLR/TAIL (Green) On – When the EDS-405A/408A coupling function is enabled to form a back-up
path, or when it's set as the Tail of the Turbo Chain. Blinking – When the Turbo Chain is down. Off
– When the EDS-405A/408A disables the coupling function, or is set as the Member of the Turbo
Chain.
5. 10M (TP) (Green) On – TP port’s 10 Mbps link is active. Blinking – Data is being transmitted at 10
Mbps. Off – TP Port’s 10 Mbps link is inactive.
6. 100M (TP) (Green) On – TP port’s 100 Mbps link is active. Blinking – Data is being transmitted at
100 Mbps. Off – TP Port’s 100 Mbps link is inactive.
7. 100M (FX) (Green) On – FX port’s 100 Mbps link is active. Blinking – Data is being transmitted at
100 Mbps. Off – FX Port’s 100 Mbps link is inactive.
 Document number 96780739 Page 101 of 544
Revision 1

Ethernet – Network Switches

STUDENT NOTES:

Communication Redundancy
Setting up Communication Redundancy on your network helps protect critical links against failure,
protects against network loops, and keeps network downtime at a minimum.
Communication Redundancy allows you to set up redundant loops in the network to provide a backup
data transmission route in the event that a cable is inadvertently disconnected or damaged. This is a
particularly important feature for industrial applications, since it could take several minutes to locate the
disconnected or severed cable.
The Moxa switch supports three different protocols to support this communication redundancy function:
• Turbo Ring and Turbo Ring V2
• Turbo Chain
• Rapid Spanning Tree and Spanning Tree Protocols (IEEE 802.1W/802.1D-2004)
When configuring a redundant ring, all switches on the same ring must be configured to use the same
redundancy protocol. You cannot mix the Turbo Ring, Turbo Ring V2, and STP/RSTP protocols on the same
ring.
Turbo Ring refers to the original version of Moxa’s proprietary redundant ring protocol, which has a
recovery time of less than 300 ms.
Turbo Ring V2 refers to the new generation Turbo Ring, which has a recovery time of under 20 ms for Fast
Ethernet ports and under 50 ms for Gigabit Ethernet ports.

The Turbo Ring Concept

Moxa developed the proprietary Turbo Ring protocol to optimize communication redundancy and achieve
a faster recovery time on the network.
 Document number 96780739 Page 102 of 544
Revision 1

The Turbo Ring and Turbo Ring V2 protocols identify one switch as the master of the network, and then
automatically block packets from traveling through any of the network’s redundant loops. In the event
that one branch of the ring gets disconnected from the rest of the network, the protocol automatically
readjusts the ring so that the part of the network that was disconnected can re-establish contact with the
rest of the network.
The user does not need to configure any of the switches as the master to use Turbo Ring or Turbo Ring V2.
If none of the switches in the ring is configured as the master, then the protocol will automatically assign
master status to one of the switches. In fact, the master is only used to identify which segment in the
redundant ring acts as the backup path. The redundant segment (i.e., the segment that will be blocked
during normal operation) is determined by the number of switches in the ring, and where the ring master
is located. The Moxa switch with the lowest numerical MAC address is usually assigned as the master.

NOTE: The Turbo Ring DIP Switches located on the outer casing of EDS series switches can be used to
configure the switches’ Turbo Ring protocols (Turbo Ring or Turbo Ring V2). If the Turbo Ring DIP Switch is
enabled from any access interface (web-based UI, console, or Telnet), and the 4th DIP Switch on the
switch outer casing is set to ON, the Redundancy Protocol will be set automatically to the Turbo Ring
protocol based on the version configured in the Turbo Ring DIP Switch page and the corresponding
Redundant Ports, Coupling Ports, and Coupling Control Port will be fixed to the assigned factory default
port number automatically. In this case, you will not be able to use the web-based UI, console, or Telnet
interface to change the status of the DIP Switch and the Communication Redundancy settings will be
greyed out in the web browser

Broadcast Storms
What is likely to happen when you plug two ends of a network cable to a single switch/router? Will this
create problems on the network, or just be ignored?

Depends on the router/switch. If it's "Managed" or has STP (Spanning Tree Protocol) or one of its variants
enabled, there's a few seconds of absolute insanity, then the switch realises that there's a loop in the
network topology, and blocks one of the ports. If it's "Unmanaged” (a fair proportion of small 4-8 port
switches), then all hell breaks loose, as you've just created a loop in a network, and all the traffic tends to
just bounce about inside the loop.

The reason this happens is because switches rely on a process of MAC address learning to map MAC
addresses to physical ports. In a non-looped network, one MAC address will only be visible to the switch
on a given physical port. If you have a loop, then the switch will see multiple paths to the same MAC
address, and possibly multiple MAC addresses on multiple ports, so instead of the traffic being switched
efficiently, it will be broadcast to wherever it sees the MACs. This is known as a "Broadcast Storm".

This can quickly use up all of a switch's CPU power, fill the transmit and receive buffers, as well as polluting
the MAC address table.
Basically, if you create a loop in the network, you'll know about it, either through monitoring (detecting a
change in the STP topology), or in everything falling over dramatically.
If you look at a switch that has a broadcast storm on it, you tend to find that all of the port activity lights
are blinking all at the same time.
 Document number 96780739 Page 103 of 544
Revision 1

Bridgeway Ethernet to J1939 Gateway

STUDENT NOTES:

The module converts the joystick CanBus output (J1939 protocol) to Modbus over Ethernet. The module is
located under the removable armrests within the Amphion Chair.

The Anybus X-gateway provides centralized data storage, the “PassageWayTM”, for data that is shared
between the J1939 and Ethernet networks. Data is placed into the PassageWay by one network interface,
allowing the data to be read through the other network interface.

All connections, whether power or fieldbus, to the X-gateway are made on one end of the module.
Phoenix-style connectors are provided for power and J1939 connections. An RJ-style connector is
provided for Ethernet connection. There is a 9-pin D-Subminiature connector for the auxiliary RS-232 port
that is used for device configuration.
There is an 8 position DIP switch on the end of the module that can be used to select a portion of a
default IP address that may be used to permit an intranet connection.
On the front of the X-gateway module are 6 LEDs that are used for status indication. These LEDs provide
visual status for the overall module, the J1939 interface, and the Ethernet interface.

Power and Network Connections

The power and network connections to the X-gateway are made on the end of the module.

Connecting Power
The power connection is a 2-pin terminal block located on the end of the module. The female terminal
block connector is provided with the X-gateway.
 Document number 96780739 Page 104 of 544
Revision 1

Connecting J1939
The J1939 network connection is a 5-pin terminal block located next to the power connection on the end
of the module.

Connecting to Ethernet
The Ethernet connection uses a standard RJ45 connector (not provided). This is plugged into the socket on
the end of the module.

Connecting to the X-gateway Module

Connect the PC running BWConfig to the X-gateway module using a standard Null-Modem (pins 2 and 3
swapped) serial cable between the PC serial port or USB adapter and the 9-pin D-Sub connector on the
module. It does not matter which PC serial port you use, BWConfig will scan each available port and
detect the connection automatically. No serial port configuration is required; BWConfig will automatically
set the baud rate.

Reference Manual – 10511588-MAN

 Document number 96780739 Page 105 of 544
Revision 1

Bridgeway Ethernet to J1939 Gateway – Status and Diagnostics

STUDENT NOTES:

Anybus X-gateway LEDs

There is a group of LED indicators on the front of the X-gateway that is used to annunciate the current
status of the module and the network interfaces.

X-gateway Status
State Summary Description
Flashing Green Idle Module is in idle mode
Solid Green Run Module is in Run mode
Solid Orange Hardware The LED will be in this state immediately after power is
Initialization applied
Flashing Red/Green Error A major, unrecoverable fault has been detected
Red, Green, Orange Self-Test A self-test of the module is in progress
Alternate Flashing

J1939 Status
State Summary Description
Flashing Green Initializing The J1939 network interface is initializing and getting ready
to come online
Solid Green Online A J1939 network address has been successfully claimed and
the module is online and active
Flashing Red/Green Online with Faults The module is online and active on the J1939 network, but
faults have been detected. Check the J1939 status codes to
 Document number 96780739 Page 106 of 544
Revision 1

determine the cause of the fault

Solid Red Offline The module is not participating in the J1939 network
Flashing Red Offline with Faults The module is not participating in the J1939 network and
faults have been detected. Check the J1939 status codes to
determine the cause of the fault

Ethernet Activity LED

The Ethernet Activity LED flashes green as Ethernet packets are received or transmitted

Ethernet Link LED

The Ethernet Link LED indicates that he module is connected to an Ethernet network. The LED will display
solid green if there is a valid physical link

Ethernet Module Status LED

State Summary Description
Off No Power Not powered
Solid Green Normal The module is controlled by an Ether-Net/IP scanner in Run
mode.
Flashing Green Standby The module is not controlled by a scanner in Run mode. Note
that this is the normal state when using
Modbus/TCP masters.
Solid Red Unrecoverable fault A fault that requires user intervention has been detected.
Correct the problem and reset the X-gateway.
Flashing Red Recoverable fault A fault that can be corrected and does not require a X-
gateway reset has been detected.
Red/Green Self-Test A self-test of the module is in progress.
Alternate Flashing

Ethernet Network Status LED

State Summary Description
Off No Power The module has no power or no IP address assigned.
Solid Green Network OK and There is at least one EtherNet/IP connection. (Not affected
Communicating by Modbus/TCP connections.)
Flashing Green Network OK here are no active connections. (Not affected by Modbus/TCP
connections.)
Solid Red Address conflict The module’s IP address is already in use by another module.
Flashing Red Connection One or more of the connections in which this module is the
Time-out target has timed out. This state is only left if all timed out
connections are re-established or if the module is reset
Red/Green Self-Test A self-test of the module is in progress.
Alternate Flashing
 Document number 96780739 Page 107 of 544
Revision 1

Modbus – Ethernet Programmable Fieldbus Controller

STUDENT NOTES:

Key:
1. Address DIP switches
2. Fieldbus connection RJ-45
3. Fieldbus connection RJ-45
4. Configuration and programming interface
5. Marking area
6. Status voltage supply – system
7. Status voltage supply – power jumper contacts
8. Data contacts
9. 24V supply
10. 0V supply
11. 24V supply via jumper contacts
12. 0V supply via jumper contacts
13. Ground
14. Power jumper contacts

System Description
The WAGO-I/O-SYSTEM 750 is a modular, fieldbus independent I/O system. It is comprised of a fieldbus
coupler/controller and connected fieldbus modules for any type of signal. Together, these make up the
fieldbus node. The end module completes the node.
 Document number 96780739 Page 108 of 544
Revision 1

Couplers/controllers for fieldbus systems such as PROFIBUS, INTERBUS, ETHERNET TCP/IP, CAN
(CANopen, DeviceNet, CAL), MODBUS, LON and others are available.
The coupler/controller contains the fieldbus interface, electronics and a power supply terminal. The
fieldbus interface forms the physical interface to the relevant fieldbus. The electronics process the data of
the bus modules and make it available for the fieldbus communication. The 24 V system supply and the
24 V field supply are fed in via the integrated power supply terminal.
The fieldbus coupler communicates via the relevant fieldbus. The programmable fieldbus controller (PFC)
enables the implementation of additional PLC functions. Programming is done with the WAGO-I/O-PRO
32 in accordance with IEC 61131-3.
Bus modules for diverse digital and analog I/O functions as well as special functions can be connected to
the coupler/controller. The communication between the coupler/controller and the bus modules is
carried out via an internal bus.
The WAGO-I/O-SYSTEM 750 has a clear port level with LEDs for status indication, insert able mini WSB
markers and pullout group marker carriers.
The 3-wire technology supplemented by a ground wire connection allows for direct sensor/actuator
wiring.

Total Expansion
The length of the module assembly (including one end module of 12mm width) that can be connected to
the coupler/controller is 780mm. When assembled, the I/O modules have a maximum length of 768mm.
Examples:
• 64 I/O modules of 12mm width can be connected to one coupler/controller.
• 32 I/O modules of 24mm width can be connected to one coupler/controller.
Exception:
The number of connected I/O modules also depends on which type of coupler/controller is used. For
example, the maximum number of I/O modules that can be connected to a Profibus coupler/controller is
63 without end module.

Power Supply Unit

The WAGO-I/O-SYSTEM 750 requires a 24 V direct current system supply with a maximum deviation of -
15% or +20 %.
 Document number 96780739 Page 109 of 544
Revision 1

Modbus – Ethernet Programmable Fieldbus Controller

STUDENT NOTES:

Key:
1. LINK ACT 1 green indicates a connection to the physical network at port 1
1. LINK ACT 2 green indicates a connection to the physical network at port 2
2. MS red/green indicates the status of the node
3. NS red/green indicates the network status
4. I/O red/green/orange indicates the operation of the node and signals via a blink code
faults encountered
5. USR red/green/orange indicates information to the internal bus faults, controlled from
the user program according to the visualization programming.
A green indicates the status of the operating voltage – system
B green indicates the status of the operating voltage – power jumper contacts

The controller starts up after switching on the supply voltage. The "I/O" LED links. The "I/O" LED has a
steady light following a fault free run-up.
In the case of a fault the "I/O" LED continues blinking. The fault is cyclically displayed by the blink code.
Detailed fault messages are displayed with the aid of a blink code. A fault is cyclically displayed with up to
3 blink sequences.
• The first blink sequence (approx. 10 Hz) starts the fault display.
• The second blink sequence (approx. 1 Hz) following a pause. The number of blink pulses indicates
the fault code.
• The third blink sequence (approx. 1 Hz) follows after a further pause. The number of blink pulses
indicates the fault argument.
 Document number 96780739 Page 110 of 544
Revision 1

See User Manual for detailed Blink Code sequence identification

Example for a fault message; Fault: The 13th I/O module has been removed
1. The "I/O" LED starts the fault display with the first blink sequence (approx. 10 flashes/second).
2. The second blink sequence (1 flash/second) follows the first pause. The "I/O" LED blinks four times and
thus signals the fault code 4 (internal bus data fault).
3. The third blink sequence follows the second pause. The "I/O " LED blinks twelve times. The fault
argument 12 means that the internal bus is interrupted after the 12 th I/O module.
 Document number 96780739 Page 111 of 544
Revision 1

Modbus (Ethernet I/O)

STUDENT NOTES:

Wago 750 I/O modules are common to both the Profibus and Ethernet/Modbus couplers. I/O modules are
covered in detail in the Profibus section.

Key:
1. Fieldbus-connection RJ45
2. Flap open
3. Configuration Interface
4. Operating voltage status
5. Data Contacts
6. 24V Supply
7. 24V Supply for power jumper contacts
8. 0V for power jumper contacts
9. Ground for power jumper contacts
10. Power Jumper Contacts

Fieldbus Coupler 750-341

The fieldbus coupler 750-341 displays the peripheral data of all I/O modules in the WAGO-I/O-SYSTEM 750
on ETHERNET.
When power is applied to the fieldbus coupler, it automatically detects all I/O modules connected to the
coupler and creates a local process image. This can be a mixture of analogue and digital modules. The
process image is subdivided into an input and an output data area.
 Document number 96780739 Page 112 of 544
Revision 1

The data of the analogue modules is mapped first into the process image. The modules are mapped in the
order of their position after the coupler. The digital modules are grouped after the analogue modules, in
the form of words (16 bits per word). When the number of digital I/O’s exceeds 16 bits, the coupler
automatically starts another word.
The user has access to all field bus and I/O data.
All sensor input signals are grouped in the coupler (slave) and transferred to the higher ranking controls
(master) via the fieldbus. Process data linking is performed in the higher ranking controls. The controls put
out the resulting data to the actuators via the bus and the node. The ETHERNET fieldbus coupler is
suitable for data rates of 10 Mbit/s and 100 Mbit/s.
To be able to send/receive process data via ETHERNET, the coupler supports a series of network protocols.
For the exchange of process data, the MODBUS TCP (UDP) - protocol and the Ethernet/IP protocol are
available. However, the two communication protocols cannot be used together.
The protocol HTTP, BootP, DHCP, DNS, SNTP, FTP and SNMP are provided for the management and
diagnosis of the system.
The coupler has an internal server for web-based applications. By default, the coupler’s built-in HTML
pages contain information on the configuration and status of the fieldbus node, and can be read using a
normal web browser. In addition, a file system is implemented that allows you to store custom HTML
pages in the coupler using FTP download.

Fieldbus Connection
Connection to the fieldbus is by a RJ45 connector. The RJ45 socket on the fieldbus coupler is wired per the
100BaseTX standard. The specification for the connecting cable is a twisted pair cable of Category 5.
Cables of type SUTP (Screened-Unshielded Twisted Pair) and STP (Shielded Twisted Pair) with a maximum
segment length of 100 meters may be used.

Hardware Address (MAC-ID)

Each WAGO ETHERNET fieldbus coupler is provided from the factory with a unique and internationally
unambiguous physical Ethernet address, also referred to as MAC-ID (Media Access Control Identity). This
address is to be found on the rear of the coupler and on an adhesive tear-off label on the side of the
coupler. The address has a fixed length of 6 Bytes (48 Bit) and contains the address type, the
manufacturer’s ID, and the serial number.

Local Process Image

After switching on, the coupler recognises all I/O modules plugged into the node which supply or wait for
data (data width/bit width > 0). In nodes analogue and digital I/O modules can be mixed.
The coupler produces an internal process image from the data width and the type of type of I/O module
as well as the position of the I/O modules in the node. It is divided into an input and an output data area.
The data of the digital I/O modules is bit orientated, i.e. the data exchange is made bit for bit. The
analogue I/O modules are representative for all byte orientated I/O modules, i.e. those where the data
exchange is made byte for byte.
These I/O modules include for example the counter modules, I/O modules for angle and path
measurement as well as the communication modules.
The data of the I/O modules is separated for the local input and output process image in the sequence of
their position after the coupler in the individual process image.
 Document number 96780739 Page 113 of 544
Revision 1

Configuration
Only I/O modules with process data are relevant. The supply modules without diagnosis, bus internal
system supply module and the termination module are to be ignored for the configuration because they
do not provide any process data.

Addressing the I/O Modules

When addressing, first of all the more complex modules (modules occupying 1 or more bytes) are taken
into account in accordance with their physical order behind the fieldbus coupler. As such, they occupy the
addresses starting with word 0.
Following this, the data of the other modules (modules occupying less than 1 byte) follow, grouped into
bytes. In accordance with the physical byte-wise order this data is used to fill up the bytes. As soon as a
full byte is occupied by the bit-oriented modules, the next byte is automatically started.

Data width ≥ 1 Word / channel Data width = 1 Bit / channel

Analog input modules Digital input modules
Analog output modules Digital output modules
Input modules for thermal elements Digital output modules with diagnosis (2 Bit / channel)
Input modules for resistance sensors Power supply modules with fuse holder / diagnosis
Pulse width output modules Solid State power relay
Interface module Relay output modules
Up/down counter
I/O modules for angle and path
measurement
 Document number 96780739 Page 114 of 544
Revision 1

Wago Modbus/Ethernet Bus Coupler

STUDENT NOTES:

LED Display
The coupler possesses several LED’s for displaying the coupler operating status and the complete node
status.
The LEDs can be divided into three groups.
The first group of LEDs display the status of the Ethernet fieldbus. It contains both solid and two-colour
LEDs. They are labelled as: ‘LINK‘ (green), ‘MS‘ (red/green), ‘NS‘ (red/green), and ‘TxD/RxD‘ (green).
The second group of LEDs is a three-color LED (red/green/orange). This LED is labelled ‘I/O’, and displays
the status of the internal bus.
The third group uses solid coloured green LEDs. They are located on the right-hand side of the coupler
power supply. These display the status of the supply voltage.

Fieldbus status
The health of the ETHERNET Fieldbus is signalled through the top LED group (‘LINK‘, ‘MS‘, ‘NS‘and
‘TxD/RxD‘). The two-coloured LEDs ‘MS’ (module status) and ‘NS’ (network status) are solely used by the
Ethernet/IP protocol. These two LEDs conform to the Ethernet/IP specifications.
 Document number 96780739 Page 115 of 544
Revision 1

LED Meaning Trouble shooting

LINK
Green Link to a physical network exists
OFF No link to a physical network Check the fieldbus connection.

MS
Red/Green Self-test
flashing
Red The system indicates a not Restart the fieldbus coupler by turning the power
remediable error supply off and on again. If the error still exists,
please contact the I/O Support.
Green The system is not yet configures
flashing
Green Normal operation
OFF No system supply voltage Check the supply voltage (24V and 0V)

NS
Red/Green
flashing
Self-test
Red The system indicates a double Use an IP address that is not used yet.
IP-address in the network
Red flashing At least one connection Restart the fieldbus coupler by turning the power
announced a Timeout, where supply off and on again and develop a new
the coupler functions as target. connection.
Green No connection
flashing
Green At least one connection is
Developed (also connection
to the Message rout applies)
OFF No IP address is assigned to the Assign to the system an IP address by BootP,
system or there is no operating DHCP or the Ethernet Settings tool.
Voltage

TxD/RxD
Green Data exchange via ETHERNET
taking place
OFF No data exchange via ETHERNET

Node Status – Blink code from the ‘I/O’ LED

The ‘I/O‘-LED displays the communication status of the internal bus.
Additionally, this LED is used to display fault codes (blink codes) in the event of a system error.
 Document number 96780739 Page 116 of 544
Revision 1

LED Meaning Trouble shooting

I/O
Green Fieldbus coupler operating perfectly
Red a) During start-up of fieldbus coupler:
Internal bus being initialized,
Start-up displayed by LED flashing fast
for approx.1-2 seconds
Red b) After start-up of fieldbus coupler:
Errors, which occur, are indicated
by three consecutive flashing Evaluate the fault message (fault code and
sequences. There is a short pause fault argument).
between each sequential flash.

The coupler starts up after switching on the supply voltage. The "I/O" LED links. The "I/O" LED has a steady
light following a fault free run-up.
In the case of a fault the "I/O" LED continues blinking. The fault is cyclically displayed by the blink code.
Detailed fault messages are displayed with the aid of a blink code. A fault is cyclically displayed with up to
3 blink sequences.
• The first blink sequence (approx. 10 Hz) starts the fault display.
• The second blink sequence (approx. 1 Hz) following a pause. The number of blink pulses indicates
the fault code.
• The third blink sequence (approx. 1 Hz) follows after a further pause. The number of blink pulses
indicates the fault argument.
See User Manual for detailed Blink Code sequence identification

Example for a fault message; Fault: The 13th I/O module has been removed
1. The "I/O" LED starts the fault display with the first blink sequence (approx. 10 flashes/second).
2. The second blink sequence (1 flash/second) follows the first pause. The "I/O" LED blinks four times and
thus signals the fault code 4 (internal bus data fault).
3. The third blink sequence follows the second pause. The "I/O " LED blinks twelve times. The fault
argument 12 means that the internal bus is interrupted after the 12th I/O module.

Supply voltage status

The two green LED’s in the coupler supply section, display the status of the supply voltage. The left LED (A)
indicates the status of the 24 V supply for the coupler. The right hand LED (‘B‘ or ‘C‘) displays the status of
the field side supply (i.e., the power jumper contacts).

LED Meaning Trouble shooting

A
Green Operating voltage for the system exists.
OFF No operating voltage for the system. Check the supply voltage (24V and 0V).
B or C
Green Operating voltage for the power jumper
contacts exists.
OFF No operating voltage for the power Check the supply voltage (24V and 0V).
jumper contacts.
 Document number 96780739 Page 117 of 544
Revision 1

Profibus I/O

STUDENT NOTES:

Profibus is a type of fieldbus

• A digital communication system for field devices.
• Many devices on one cable – a network.
• The communication is two-way so that devices can receive information from controlling stations
and also can send information to controlling stations.
• The data can be simple – i.e. digital on/off signals,
• Or can be complex – i.e. from/to sophisticated instruments such as on-line process analyzers or
actuators such as variable-speed drives etc.

Advantages
• Significant reduction in the amount of wiring, cable trays etc.
• Centralized commissioning of devices (from control room).
• More extensive data to and from devices (i.e. diagnostic information, device parameters etc.
• Greater flexibility in system layout and design.
• Ease of future expansion and modification.

Disadvantages
• More sensitive to wiring and layout faults.
• Installers must understand that the cable is not “just a wire”!
Document number 96780739 Page 118 of 544
Revision 1
 Document number 96780739 Page 119 of 544
Revision 1

Profibus DP, I/O

STUDENT NOTES:

Process Field Bus (Profibus) refers to the hardware. Profibus DP is the communication protocol for
connecting multiple industrial devices on a shared pathway or channel (bus).
The Amphion network typically uses Profibus DP communication. Profibus communication protocol is an
international standard for communication between tool controllers, remote I/Os, drives, valves, operator
interfaces, and computers. Profibus supports communication speeds up to 12M baud over twisted-pair
copper or fiber optic cable.
Application layer interface/communication protocol for Profibus DP is between tool controllers and
associated remote I/Os. Remote I/Os gather data for tool controllers, and can be customized to address a
wide variety of local and remote I/O requirements. Tool sensors and controls are hardwired into the
remote I/O. From there, a single Profibus cable carries all communication from the remote I/O to the tool
controller or other device that processes the information.
For example, sensors on the top drive are hard-wired to a remote I/O module mounted near the tool. The
remote I/O communicates with the top drive tool controller over a Profibus DP link.

Profibus DP (Decentralized Periphery)

• Low cost, simple, high speed field-level communications.
• All modern PROFIBUS applications use DP.

Addressing
Within a network, every Profibus device or station is given an address through which communication is
directed. The address of every station must be set during commissioning, station addresses can be set in
several ways; A local switch on the device (binary dip switch or rotary switch), by software over the
 Document number 96780739 Page 120 of 544
Revision 1

Profibus network using a configuration tool (called a class 2 master) or using special software and a serial
link or hand held tool.
To set an address on a binary weighted switch we can work down from the most-significant switch
deciding whether each should be off or on.
e.g. To set a decimal address of 50, most significant switch (64) off, next switch (32) on, next switch (16)
th
on, next switch (8) off, next switch (4) off, next switch (2) on, 7 switch (1) off. Note that switches can be
labelled 0-6 or 1-7 on different devices, sometimes there are additional switches.
There are 128 different addresses available for devices (0-127); address 127 is reserved for broadcast
messages and cannot be used for a device, address 126 is used for generic (off the shelf/factory default)
devices whose address is set over the bus. The remaining 126 addresses (0-125) are available for Profibus
devices.

Network Configuration
Profibus stations have different capabilities and characteristics. E.g. number of I/O channels, diagnostic
messages, supported baud rate etc. before any Profibus system can operate the system must be
configured, that is the master must be made aware of the characteristics of the slaves. Configuration is
normally carried out using a proprietary software tool supplied for the Profibus master station.
All Profibus equipment suppliers provide standard General Station Descriptions or GSD files; these can be
read by the configuration tool to provide detailed information on the devices being used on the bus. Every
device is given a unique identification number which identifies the type of device and provides a simple
check that the configuration is correct; the GSD file is specific to a particular ID number. So if we know the
device ID we can easily identify the GSD file.

Bus Start up
The controlling master performs several checks before entering data exchange with the slave:
1. The master first checks that the slave is present on the bus and is not controlled by another master
with a diagnostic request. SBC Profibus Diagnostic page would show the node as red if not present.
2. The master next checks that the device is of the correct type by checking the ID number and
setting device parameters. SBC Profibus Diagnostic page would show the node as yellow if not the
correct type or configured incorrectly.
3. The master then checks that the allocated I/O is present and available on the slave.
4. A diagnostic request checks that all is ok.
5. The slave will only enter data exchange if the checks are passed without error. SBC Profibus
6. Diagnostic page would show the node as green if present and configured correctly.

Operation
Data is exchanged in all Profibus networks using messages or telegrams that pass between stations;
Master stations control the network communications, slave stations respond to telegrams from their
controlling master. During cyclic exchange, the master constantly checks that the slave is responding and
healthy.
• By looking for the slave responses, In addition each slave constantly checks that the master is
operational and healthy.
• By looking for the master requests, Should a slave detect a problem, the outputs will automatically
revert to a pre-selected state. Options vary by manufacturer but typically all output off, retain last
commanded state or revert to a preconfigured state.
 Document number 96780739 Page 121 of 544
Revision 1

Networks
When operating with a single master system, the ideal case is to have the master at one end of the
segment with the termination switched in, if the master loses power, for whatever reason, the network
will fail anyway so the loss of termination power is immaterial. At the other end of the segment a repeater
can be used to extend the network to another segment, a faulty station can be removed or replaced
without upsetting the bus termination. When a repeater is not used at the end of a segment the
termination must be on at the last device, the last device needs to be powered at all times to maintain the
supply to the termination network. If the last device needs to be replaced the whole network could
become unstable unless we have correctly wired isolating connectors.
Spur lines can cause reflections due to additional capacitance introduced by the cables, these reflections
have a small effect at low bit rates but can cause problems at high bit rates. Spur lines are not allowed
when using a baud rate >1.5Mbit/s, at lower baud rates spur lines are allowed up to a maximum
additional capacitance. Additional termination at the end of a spur line should NOT be used; the number
of terminations per segment should not exceed two.

High Speed Networks

Use of a baud rate greater than 1.5Mbit/s requires special connectors with built in inductors, a maximum
segment length of 100m is allowed and a minimum cable length between any two stations of 1m is
recommended, stations that are closely connected can cause reflections.

Fiber Optic Transmission

Fiber optic offers the following major advantages over copper, longer distances are possible at high speed,
total immunity to electromagnetic interference and electrical isolation (removes earth potential
differences and ground current problems) Several types of fiber optic transmission media are available;
plastic, which is low cost but limited to a distance of less than 50m, multi-mode glass fiber which can be
used over distances up to 2km and single mode glass fiber which can be used over distances up to 50km.
Glass fiber cables are more expensive and require specialized equipment to make up.
Optical Link Modules (OLMs) provide conversion between copper and fiber optics, like repeaters OLMs
also have the effect of splitting the network into isolated segments. When using OLMs to connect two
segments, two are required and a pair of fiber optic cables, one cable for the signal in each direction.
 Document number 96780739 Page 122 of 544
Revision 1

Profibus Network Media

STUDENT NOTES:

Wiring
On the PROFIBUS with RS 485 transmission technology all devices are connected in a line structure. The
bus line comprises of a twisted and screened pair of wires allowing up to 32 stations to be connected
together on a single cable (segment). Up to 126 devices can be connected together in one Profibus
network; segments are formed by using repeaters, couplers or fiber optic links.

Operation
Maximum line lengths for a bus segment dependent upon the transmission speed.

Transmission speed (kBaud) Max. bus segment length

9.6/19.2/45.45/93.75 1200m (Low Speed)
187.5 1000m
500 400m
1500 (1.5Mbits/s) 200m
3000/6000/12000 (3/6/12Mbits/s) 100m (High Speed)

Interference
There are two mechanisms for pickup of interference from other electrical cables or equipment
• Electrostatic pickup – where capacitive coupling induces electrical voltages in the cable
• Electromagnetic pickup – where magnetic fields induce currents in the cable via inductive coupling
Shielding or screening the signal cable can reduce electrostatic pickup. Shielding is only effective when
the shield is properly connected to earth (ground), unearthed screening has no effect whatsoever, and
 Document number 96780739 Page 123 of 544
Revision 1

in fact it can make the interference worse! Twisted core cable significantly reduces electromagnetic
pickup, however does not reduce electrostatic pickup and requires a properly earthed screen.
Installation within earthed, magnetically impervious ducting (steel tray or conduit) can further reduce
electrostatic and electromagnetic interference.

RS485 Transmission
RS485 uses shielded twisted pair cable, allowing communication at up to 12Mbit/s and can be used to
connect up to 32 devices in a single segment. Allowable segment length is dependent on the bit rate used,
from 100m maximum at high speed and 1000m at low speed.
Unbalanced transmission is where a signal and a zero volt reference wire is used, the signal wire can pick
up interference but the reference wire is connected to ground. Earthed screening can reduce electrostatic
pickup, but unbalanced transmission can give rise to ‘earth loops’ if the reference is earthed at both ends.
Unbalanced systems are best wired with the reference and shield connected at only one end.
In balanced transmission both wires carry the signal, one positive and one negative, small screen currents
have no effect on the signal. Balanced systems are best wired with the shield connected at both ends.
RS485 transmission is balanced to improve noise rejection; both ends of the screen cable should be
earthed to ensure effectiveness at high frequencies. Poor shielding or earthing is a very common wiring
error.
The limitation of 32 devices is overcome by splitting larger networks into segments that are electrically
isolated but communicate using repeaters or fiber optic links. Each segment is a separate piece of copper
cable that must adhere to RS485 rules. Within a segment all stations and repeaters count towards the 32
device limit.

Pin allocations for 9-pin, sub-D Profibus connectors

Pin Number Signal Function
1 Shield Ground Connection O
2 M24 Ground for 24v supply O
3 RxD/TxD-P Data Line Plus (B-Line) M
4 CNTR-P Repeater Direction Control Signal O
5 DGND Data Ground M
6 VP +5v Supply for Termination M
7 P24 +24v Supply O
8 RxD/TxD-N Data Line Minus (A-Line) M
9 CNTR-N Repeater Direction Control Signal O
*Case Shield Ground Connection O

M = Mandatory, O = Optional *Note that the cable shield should always be connected on every device,
even though the table shows optional

The two wires in the twisted-pair cable carry the data line plus (b-line) and data line minus (A-line) signals,
Profibus cable usually come color coded (red and green) however, other colors may be found. It is
essential that the color scheme for A and B is used consistently throughout the network. This is a common
wiring error in the field.

Reflections and Terminations

When electrical signals travel down a cable, any electrical discontinuity like a change in resistance,
capacitance or inductance can cause reflections to occur, In particular, the end of the wire is a major
discontinuity where the resistance suddenly increases to infinity. Like an echo, the reflected signal can
 Document number 96780739 Page 124 of 544
Revision 1

cause multiple signals to appear on the line. Reflections are bad news in high-speed communications
because signals are corrupted or distorted by the reflection.
To minimize reflections at the end of a cable the ends must be terminated with a specially chosen
resistance that matches the cable properties, the resistance absorbs the energy of the signal and
significantly reduces the reflection (theoretically to zero). Profibus RS485 uses active termination which
means the termination is a resistor network which is supplied with 5v. To avoid reflections from the ends
of the cable it is essential that each segment is terminated at the two ends and nowhere else, RS485
termination networks must be powered at all times (even when devices are switched off) otherwise
reflections can disrupt the remaining devices on the bus. It is common to find intermittent bus problems
caused by incorrect termination. Many Profibus devices incorporate built-in termination resistors that can
be switched in or out. In a such cases it is important that the device termination is switched out when not
required, another common error is to have additional termination resistors switched in giving additional
termination in the middle of a segment or double termination at the end of a segment, additional
termination(s) can cause reflections.
Spur-lines (also called stub or drop lines) should generally be avoided on RS485 wiring because they can
cause reflections; the cable should ideally daisy chain from device to device.

Plugs/connectors
The plugs available on the market offer the possibility that arriving and departing data cables can be
directly connected to the plug. In this manner drop cables are avoided and the bus plug can be connected
to or disconnected from the bus at any time without interrupting the data traffic.
• Built in termination resistors that can be switched in and out
• Quick and reliable connection of data wires and shield
• Special inductors built in for operation over 1.5Mbit/s
• Connections for incoming and outgoing cables
• Outgoing cable isolation when termination is switched on - Modern Profibus connectors normally
have marked cable entries for incoming and outgoing cables, the distinction can be important
where the outgoing cable is isolated when the termination is switched on. Isolating connectors are
useful for commissioning and testing the network and also for maintenance purposes, where they
allow sections of a segment to be isolated whilst retaining correct termination.
• Additional piggyback socket for connection of diagnostic or programming tools – Allows
monitoring or programming devices to be plugged in without disrupting the network, best
mounted at the end of each segment.

Type-A Cable
Parameter Value
Wave resistance 135 … 165 Ω at a frequency of 3 to 20 MHz
Operating capacity < 30 pF/m
Loop resistance 110 Ω/km (resistance measured if two cores connected at one end of
length)
Wire diameter > 0.64mm
Wire cross-section > 0.34mm²

Many different forms of this cable are available, standard Profibus solid core cable, stranded core cables
for flexibility, cables with special sheaths for the use in the food and chemical industries, armoured cables
for protection against rodent and other damage and zero halogen (low smoke) cables for use in confined
spaces.
 Document number 96780739 Page 125 of 544
Revision 1

It is important not to distort or damage bus cables since this can cause reflections, a bend radius of 10
times the cable diameter (typically 75mm) should be adhered to, cable should not be twisted, stretched
or squashed.
Profibus cables are considered as a Category I type cable (sensitive and safe cables) and should be
separated from other categories at the following distances, Category II ≥ 10cm, Category III ≥ 20cm and
Category IV ≥ 50cm.
 Document number 96780739 Page 126 of 544
Revision 1

Profibus Troubleshooting

STUDENT NOTES:

Faults
The most common Profibus problems are
Configuration faults
Wiring faults, including reflections, wire breaks and short circuits
Device removal
Interference pickup
Instrument or I/O failure
Addressing faults

Faults can be broken down into Communication or Peripheral faults, Communication faults disrupt
network communications and can be as a result of network wiring errors, interference pick up, reflections
etc. they are known as bus faults, Peripheral faults are usually concerned with I/O and can be as a result
of sensor wire breaks, loss of output power, sticking valves etc. network communications will be good,
they are not categorized as bus faults.

Communication faults are mainly caused by poor network wiring or layout or cable/connector
deterioration and can be permanent or intermittent. A BF (Bus Fault) light may illuminate when the
watchdog timer trips out, since the watchdog timer takes a specific period of time the BF light may not
illuminate when errors are intermittent. Communication faults require specialist tools such as a protocol
analyzer and diagnostic tools or Waveform visualization tools fault find. Communication errors do not
always produce loss of control; Profibus is very robust to errors that can corrupt data. Quite often users
are blissfully aware that their system has communication errors because of the robustness and fault
 Document number 96780739 Page 127 of 544
Revision 1

tolerance of Profibus, only when the rate of data corruption reaches a critical threshold will the fault
become apparent.

Peripheral faults are caused by sensor/actuator failures or wiring faults and again these faults can be
intermittent. A SF (System Fault) light may illuminate showing any peripheral errors, note that the Bus
Fault LED will be green indicating good communications. Since communication remains operational,
peripheral faults can often be located and diagnosed using the communications system. Tools and
techniques that are useful for locating peripheral fault include Diagnostic reporting using PLC software or
on-line SCADA system and Protocol analyzer. Modern intelligent devices incorporate extensive self-
diagnostic features that can identify or highlight many peripheral faults.

Permanent faults can be relatively easy to fix, the fault will disappear when it’s fixed! Intermittent faults
however, can be a nightmare, you can’t be sure you have fixed it; a problem may seem to be cured only
to return at a later date. Intermittent faults require long-term monitoring to check that the fault is cured.
Health checking is an important part of the commissioning and maintenance strategy for plant, it can help
find non-critical and intermittent fault that are not obvious. A health check should be carried out
immediately after installation and commissioning and be repeated at regular intervals.

Communication faults can be caused by

• Wiring errors – including termination problems, wrong/mismatched cable, cable routing, spurs
etc.
• Configuration errors (usually during commissioning)
• incorrect GSD files – GSD ID number does not match, GSD version does not match
• incorrect module configuration – Wrong module configured, Wrong module plugged in, Missing
modules
• addressing errors - Physical address is wrong, Configure address is wrong or Two devices at the
same address
• Device failures
• Power supply failures
Most of these are relatively easy to locate a fix, intermittent communication faults can be caused by
• A potential combination of some of the issues above plus the added effect of interference pickup,
these are often very difficult to diagnose and solve.

Reflections can cause communication errors since they corrupt the transmitted telegram and can be
caused by a number of different faults
• Termination problems – including missing terminations, additional terminations or un-powered
terminations
• Spur lines
• Damaged or incorrect cable
• Uncertified devices
Problems related to reflections can be very difficult to diagnose without the correct tools and a systematic
approach, intermittent faults in particular can be difficult to pin point. Part of the problem is that the
devices that are most affected are often found at the opposite end of the segment from the reflection
source. Reflections are best seen on an oscilloscope at a low baud rate.

Interference can cause communication errors because it corrupts the transmitted telegram and can be
caused by poor cable segregation, poor earthing, poor screening and use of uncertified devices.
 Document number 96780739 Page 128 of 544
Revision 1

Reflections result in a regular waveform corruption that is similar for each digital pulse, Interference
however, is fundamentally random in nature and is independent of transmitted pulses; interference can
be best seen in between telegrams during bus ‘quiet’ time.

Slave Diagnostics
The controlling master requests diagnostics from a slave during start up, after set_parameters and
check_configuration, the master will also ask for diagnostics should any fault appear during operation.
Slave diagnostic response contains standard diagnostics that are the same for every slave device, the
standard diagnostics can be followed by optional extended diagnostics, diagnostics can be interpreted by
an analyzer.
The first 6 data bytes in the slave diagnostic response, this response indicates
• Profibus ID number
• Whether the slave is locked to a master
• Address of that controlling master
• Parameterization faults
• Configuration faults
• Standard options that are enabled
The standard diagnostics may be followed by optional extended diagnostics from byte 7 onwards
• Device-related diagnostics – Vendor-specific data indicating a device problem, often defined in
GSD file
• Identifier-related diagnostics – Standardized diagnostics indicating which, of any, modules have a
problem
• Channel- related diagnostics – Indicating the channel number and type (digital/analogue) and type
of fault

Software such as Profitrace can be used to view and interrogate these diagnostics.
Network measurements can be obtained which includes
• Live list check – indicating configuration errors and unconfigured slaves
• Sync count – indicating missing slaves
• Retry count – indicating failed responses
• Illegal responses to requests – indicating corrupted telegrams
• Diagnostic requests to slaves whilst in data exchange – indicating intermittent communications or
peripheral faults
Segment measurements can include
• Waveform amplitude measurements
• Waveform quality measurements
Segment measurements should be carried out on individual segments since repeaters, couplers and
optical links isolate segment from each other, distorted or weak signals cannot be seen from another
segment.
 Document number 96780739 Page 129 of 544
Revision 1

Wago Profibus I/O

STUDENT NOTES:

General
The WAGO-I/O-SYSTEM consists of various components which are capable of providing modular and
application specific fieldbus nodes for various fieldbuses.
A fieldbus node consists in principle of a fieldbus coupler or Programmable Fieldbus Controller (1) at the
front end, a number of special I/O modules (2) and an End Module (3) which is placed at the other end.

Coupler/Controller (1)
The Coupler/Controller forms the link between the fieldbus and the field devices with their I/O functions.
All control functions required for the faultless operation of the I/O functions are carried out by the
Coupler/Controller. The connection to different fieldbus systems is established by each of the
corresponding Coupler/Controller, e.g. for PROFIBUS, INTERBUS, CAN, MODBUS etc. In this way a change
of the fieldbus system is possible.
The programmable fieldbus controller 750-833 combines the PROFIBUS DP functionality of the fieldbus
coupler 750-333 with the functionality of a Programmable
Logic Control (PLC). Programming of the application is done with WAGO-I/O-PRO in accordance with IEC
61131-3, covering all 5 programming languages. The programmer can access all fieldbus and I/O data.
Characteristics and use of the Controllers:
• The use of decentralized control can better support a PLC or PC
• Signal pre-processing reduces fieldbus transmissions
• Complex applications can be divided into multiple tasks
• Tasks can be prioritized
• Peripheral equipment can be controlled directly, resulting in faster system response times
 Document number 96780739 Page 130 of 544
Revision 1

• Programmable response in the event of a fieldbus failure

• Simple, self-sufficient control

I/O Modules (2)

In the I/O modules, the incoming process data is converted. Corresponding to the different requirements,
special I/O modules are available for a variety of functions. There are digital and analogue inputs and
outputs and modules for special functions (Counter modules, Terminal blocks for encoder and resolvers
and communication modules).

End Module (3)

An End Module is needed for faultless operation of the node. The termination module is always placed as
the last module in order to obtain a termination of the fieldbus node. This module has no I/O function.

Description
The fieldbus coupler 750-333 displays the peripheral data of all I/O modules in the WAGO-I/O-SYSTEM 750
on PROFIBUS DP.
In the initialisation phase the bus coupler determines the physical structure of the node and creates a
process image from this with all inputs and outputs. I/O modules with a bit width smaller than 8 can be
combined to form one byte in order to optimise the address space.
In addition the possibility exists to deactivate projected I/O modules. In this manner the physical structure
of the node can be individually designed with regard to the peripheral signals, without undertaking any
changes to an already existing control application.
The diagnosis concept is based on identification and channel based diagnosis in accordance with EN
50170. Thus it is not necessary to program modules for the evaluation of manufacturer specific diagnosis
information.
• Max. process data length 128 Byte (input and output process image)
• Automatic recognition of transmission speed on the PROFIBUS from 9.6 kBd to 12 MBd
• All I/O modules from the WAGO-I/O-SYSTEM 750 are supported
• Configuration modules can be parameterised as wildcards.
• Parameter able substitute value for each channel
• D-Sub 9 pole bus connection

Internal Bus/Data Contacts

Communication between the coupler/controller and the bus modules as well as the system supply of the
bus modules is carried out via the internal bus. It is comprised of 6 data contacts, which are available as
self-cleaning gold spring contacts.

Power Contacts
Self-cleaning power contacts are situated on the side of the components which further conduct the supply
voltage for the field side. These contacts come as touch proof spring contacts on the right side of the
coupler/controller and the bus module. As fitting counterparts the module has male contacts on the left
side. The design of some modules does not allow them to be physically assembled in rows, as the grooves
for the male contacts are closed at the top.
With the WAGO ProServe® Software smartDESIGNER, the assembly of a fieldbus node can be configured.
The configuration can be tested via the integrated accuracy check.
 Document number 96780739 Page 131 of 544
Revision 1

Wago Profibus Bus Coupler

STUDENT NOTES:

Key:
1. Fieldbus-connection D-Sub
2. Address rotary switch
3. Configuration Interface
4. Operating voltage status
5. Data Contacts
6. 24V Supply
7. 24V Supply for power jumper contacts
8. 0V for power jumper contacts
9. Ground for power jumper contacts
10. Power Jumper Contacts

The fieldbus coupler comprises of:

• Supply module with internal system supply module for the system supply as well as power jumper
contacts for the field supply via I/O module assemblies.
• Fieldbus interface with the bus connection
• 2 rotary switches for the station address (decimal)
• Display elements (LED’s) for status display of the operation, the bus communication, the operating
voltages as well as for fault messages and diagnosis
• Electronics for communication with the I/O modules (internal bus) and the fieldbus interface
 Document number 96780739 Page 132 of 544
Revision 1

Station Address
The station address (decimal) is determined using two rotary switches on the electronic module.
The switch .x1. determines the units’ position of the address. The switch .x10. determines the tens
positions of the address. Valid station addresses are between 1 and 99. The coupler also permits the
station address 0. The station address is taken over by the fieldbus coupler after switching on the device
(initialization phase). Adjustments of the switch have no effect during operation. Cycle power to the
coupler for address changes to take effect.

Configuration Interface
The configuration interface used for the communication with WAGO-I/OCHECK or for firmware upload is
located behind the cover flap.
The communication cable (750-920) is connected to the 4 pole header
 Document number 96780739 Page 133 of 544
Revision 1

Wago Profibus Bus Coupler

STUDENT NOTES:

Fieldbus Connection
The PROFIBUS interface is designed as a Sub-D connection in accordance with the US Standard EIA RS 485
for cable linked data transmission.

Pin Signal Description

3 RxD(TxD)-P Transmit (receive) signal
4 RTS Ready To Send
5 GND Supply ground (earth)
6 Vcc Voltage supply
8 RxD(TxD) N Transmit (receive) signal

Display Elements
The operating condition of the fieldbus coupler or node is signaled via light diodes (LED).

Key:
Run (Green), The ’RUN’ LED indicates to the operator if the fieldbus coupler/controller is correctly
initialized.
1. BF (Red), The ’BF’-LED indicates whether the communication functions via the PROFIBUS.
2. DIA (Red), The ’DIA’ LED indicates an external diagnosis. The signaling is not supported by all
devices.
3. BUS (Red), The ’BUS’-LED signals a projecting fault.
4. I/O (Green/Red/Orange), the ’I/O’-LED indicates the operation of the node and signals faults
encountered.
 Document number 96780739 Page 134 of 544
Revision 1

5. A (Green), Status of the operating voltage system

6. C (Green), Status of the operating voltage. power jumper contacts

Run BF DIA Bus

off off off off No operating voltage to the coupler (status LED of the bus coupler supply on
does not light up) or a hardware fault is present.
on on * off PROFIBUS interface started, baud rate was not yet recognized.
on blinks * off Baud rate recognized, station not yet parameterized and configured.
on blinks on cyclic Slave was incorrectly projected. Fault message via blink code.
blink
on off * off The coupler is exchanging data.
on * on * The coupler signals an existing diagnosis.

The ’I/O’ LED indicates the node operation and signals faults occurring
Green – Data cycle on the internal bus
Off – No data cycle on the internal bus
Red – Coupler hardware defective
Red (blinks) – When starting: internal bus is initialized, during operation: general internal bus fault
Red (cyclic blink) – Fault message during internal bus reset and internal fault
Orange – Flash access to bus coupler firmware
The coupler starts after switching on the supply voltage. The "I/O" LED flashes red. Following a fault free
run up the "I/O" LED changes to green steady light.
In the case of a fault the "I/O" LED continues blinking red. The fault is cyclically displayed with the blink
code.

Blink Code
Detailed fault messages are displayed with the aid of a blink code. A fault is cyclically displayed with up to
3 blink sequences.
• The first blink sequence (approx. 10 Hz) starts the fault display.
• The second blink sequence (approx. 1 Hz) following a pause. The number of blink pulses indicates
the fault code.
• The third blink sequence (approx. 1 Hz) follows after a further pause. The number of blink pulses
indicates the fault argument.

Fault Argument Fault Description

Fault code 1: Hardware and configuration fault
0 EEPROM check sum fault / check sum fault in parameter area of the flash memory
1 Overflow of the internal buffer memory for the inline code
2 Unknown data type
3 Module type of the flash program memory could not be determined/is incorrect
4 Fault during writing in the flash memory
5 Fault when deleting the FLASH memory
6 Changed I/O module configuration found after AUTORESET
7 Fault when writing in the serial EEPROM
8 Invalid firmware

Fault code 2: Fault is programmed configuration

0 Incorrect table entry
 Document number 96780739 Page 135 of 544
Revision 1

Fault code 3: Internal bus command faulted

0 I/O module(s) has (have) identified internal bus command as incorrect
Fault code 4: Internal bus data fault
0 Data fault on internal bus or internal bus interruption on coupler
n* (n>0) Internal bus interrupted after I/O module n
Fault code 5: Register communication fault
n* Internal bus fault during register communication with the I/O module n
Fault code 7: I/O module not supported
n* I/O module not supported at position n
* The number of blink pulses (n) indicates the position of the I/O module. I/O modules without data are
not counted (e.g. supply module without diagnosis)
th
Example: 13 I/O module is removed
1 The "I/O" LED generates a fault display with the first blink sequence (approx. 10 Hz).
2 The first pause is followed by the second blink sequence (approx. 1 Hz). The "I/O“
LED blinks four times and thus signals the fault code 4 (internal bus data fault).
3 The third blink sequence follows the second pause. The "I/O ERR" LED blinks twelve
times. The fault argument 12 means that the internal bus is interrupted after the
th
12 I/O module.

Supply Voltage Status

LED Color Meaning
A Green Status of the operating voltage – system
C Green Status of the operating voltage – power jumper contacts
There are two green LEDs in the coupler supply section to display the supply voltage. The left LED (A)
indicates the 24 V supply for the coupler. The right hand LED (C) signals the supply to the field side, i.e. the
power jumper contacts.
 Document number 96780739 Page 136 of 544
Revision 1

I/O Modules (4DI 24V DC & 4DO 24V DC)

STUDENT NOTES:

Wago 750 I/O modules are common to both the Profibus and Ethernet/Modbus couplers. I/O modules are
covered in detail in the Profibus section. These pages show just a few of the modules available and used
by NOV – please use the link at the bottom of the page to find information on other modules.

Connection
Sensors and actuators can be directly connected to the relevant channel of the bus module in 1-/4
conductor connection technology. The bus module supplies power to the sensors and actuators. The input
and output drivers of some bus modules require the field side supply voltage.
The coupler/controller provides field side power (DC 24V). In this case it is a passive power supply without
protection equipment. Power supply modules are available for other potentials, e.g. AC 230 V. Likewise,
with the aid of the power supply modules, various potentials can be set up. The connections are linked in
pairs with a power contact.
The supply voltage for the field side is automatically passed to the next module via the power jumper
contacts when assembling the bus modules.
The current load of the power contacts must not exceed 10 A on a continual basis. The current load
capacity between two connection terminals is identical to the load capacity of the connection wires.
By inserting an additional power supply module, the field supply via the power contacts is disrupted. From
there a new power supply occurs which may also contain a new voltage potential.
Some bus modules have no or very few power contacts (depending on the I/O function). Due to this, the
passing through of the relevant potential is disrupted. If a field supply is required for subsequent bus
modules, then a power supply module must be used.
 Document number 96780739 Page 137 of 544
Revision 1

Fusing
Internal fusing of the field supply is possible for various field voltages via an appropriate power supply
module.

750-432/3 4DI 24V DC (Reference Document m07500433_00000000_0en)

The digital input module 750-433 receives control signals from digital field (e.g. of sensors, transmitters,
switches or proximity switches).
I/O module has 4 input channels, providing a direct connection to 2-wire sensors.
The input signals are connected to the following terminals: DI 1 and 24 V ... DI 4 and 24 V.
Each input channel has an RC noise rejection filter with a time constant of 0.2 ms.
The I/O module inputs provide high-side switching. If the 24V potential for field power is switched to an
input connection, the signal status for the corresponding input channel is set to "high."
A green LED indicates the switched status of each channel.
The I/O module receives the 24V supply for the field level from an upstream I/O module or from the
fieldbus coupler/controller via the power contacts used as blade contacts. It then provides this potential
to subsequent I/O modules via the power contacts used as spring contacts.

Process Image
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
x x x x DI 4 DI 3 DI 2 DI 1
DI 1 Signal state DI 1 – Digital input channel 1
DI 2 Signal state DI 2 – Digital input channel 2
Di 3 Signal state DI 3 – Digital input channel 3
DI 4 Signal state DI 4 – Digital input channel 4
x Not in use

4DO 24V DC 0.5A (Reference document m07500531_xxxxxxxx_0en)

The 750-531 (4DO 24V DC 0.5A/ 2-conductor) Digital Output Module transmits binary control signals from
the automation device to the connected actuators (e.g., solenoid valves, contactors, transmitters, relays or
other electrical loads).
The module has four output channels. Four 2-conductor actuators may be directly connected to the
module.
The actuators can be connected using connection DO 1 or DO 2, DO 3, DO 4 and 0V
The output channels are electrically short-circuit-protected.
The I/O module outputs provide high-side switching. If the signal status of an output channel is at “high”
the 24 V potential for field power will be switched to the appropriate output connection.
The supply voltage for the field side is derived from an adjacent supply module by means of power jumper
contacts.

Process Image
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
x x x x DO 4 DO 3 DO 2 DO 1
DO 1 Signal state DO 1 – Digital output channel 1
DO 2 Signal state DO 2 – Digital output channel 2
DO 3 Signal state DO 3 – Digital output channel 3
DO 4 Signal state DO 4 – Digital output channel 4
x Not in use
Manuals and Data Sheets for individual modules are available via the Wago website
 Document number 96780739 Page 138 of 544
Revision 1

http://global.wago.com/en/services/downloads/download-search/index.jsp?q=750-
433&action=search&frontendId=frontendDownload_cms_de-en&lang=en
 Document number 96780739 Page 139 of 544
Revision 1

I/O Modules (2AI 4020mA & 2AO 0-10V DC)

STUDENT NOTES:

These pages show just a few of the modules available and used by NOV – please use the link at the
bottom of the page to find information on other modules.

750-465/6 2AI 4-20mA (Reference Document m07500466_xxxxxxxx_0en)

The Analog Input Module 750-466 (2AI 4-20mA S.E.) processes analogue signals with the normal value of
4 mA ... 20 mA.
Two- or three-wire transducers without power supply (e.g., adjustable resistors, pressure, flow and level
meters) can be connected directly.
The transducers are directly supplied with 24 V from the I/O module.
Two-wire transducers are supplied via 24 V terminals and 3-wire transducers via 24 V and 0 V terminals.
The I/O module has 2 input channels for field side signals. The sensors may be received via connections AI
1 or AI 2.
The input signal is electrically isolated and is transmitted with a resolution of 12 bits.
The operational readiness and the trouble-free internal data bus communication of the channels are
indicated via a green function LED.
A red fault LED per channel indicates a wire break or that the signal is outside the measuring range.

Process Image (Standard Data Format)

The 750-465/6 I/O module and its variants provide 1 status byte (8 bits) and 1 data word (16 bits).
Whether the status byte is read out via the fieldbus depends on how diagnostic information is transmitted
by the respective fieldbus or fieldbus couplers/controllers used. In any case, the status byte can be read
out using the WAGO-I/O-CHECK commissioning tool via the service port of the fieldbus coupler/controller.
 Document number 96780739 Page 140 of 544
Revision 1

The digitalized measured value is transmitted to the process image of the fieldbus coupler/controller in a
data word (16 bits) as an input byte 0 (low) and input byte 1 (high). This value is mapped with a resolution
of 12 bits on bit B3 ... B14. Status information, which can be evaluated for fault detection, is contained in
the three least significant bits (B0 ... B2).
If the measurement is above the measuring range, bit B0 is set = 1, and if the measurement is below the
measuring range or if a wire breaks, bits B0 and B1 are set = 1.

Input current Numercial value

4 mA - 20 mA binary Status - LED
Measured value byte hex. Error AI 1, 2
*⁾ XFÜ hex. dec.
<0 not possible (Reverse voltage protection)
<4- Δ**) ’0000.0000.0000.0 011’ 0x0003 3 0x41 on
<4 ‘0000.0000.0000.0 000’ 0x0000 0 0x00 off
4 ‘0000.0000.0000.0 000’ 0x0000 0 0x00 off
6 ‘0001.0000.0000.0 000’ 0x1000 4096 0x00 off
8 ‘0010.0000.0000.0 000’ 0x2000 8192 0x00 off
10 ‘0011.0000.0000.0 000’ 0x3000 12288 0x00 off
12 ‘0100.0000.0000.0 000’ 0x4000 16384 0x00 off
14 ‘0101.0000.0000.0 000’ 0x5000 20480 0x00 off
16 ‘0110.0000.0000.0 000’ 0x6000 24576 0x00 off
18 ‘0111.0000.0000.0 000’ 0x7000 28672 0x00 off
20 ‘0111.1111.1111.1 000’ 0x7FF8 32760 0x00 off
>20 ‘0111.1111.1111.1 001’ 0x7FF9 32761 0x42 off
>20+ Δ**) ‘0111.1111.1111.1 001’ 0x7FF9 32761 0x42 on

*⁾ status bits: X = not used, F = short-circuit, Ü= oversize

**⁾ Δ = 0.1 … 2.0mA

750-450 2AO 0-10V DC (Reference Document m07500550_00000000_0en)

The analogue output module 750-550 (2AO 0-10V DC) generates a standardized signal of 0 … 10 V for the
field area.
The I/O module has 2 short circuit protected output channels and enables the direct wiring of 2 2-
conductor actuators.
The actuators are connected to the connectors AO 1 and common (ground) or AO 2 and common
(ground).
Both output channels have a common (ground) and a shield connection.
The Output signal is electrically isolated and will be transmitted with a resolution of 12 bits.

Process Image (Standard Format)

The analogue output module 750-550 and its variants transmit 16-bit data and 8 status bits per channel.
The digitalized output value is transmitted in a data word (16 bits) as output byte 0 (low) and output byte
1 (high) via the process image of the fieldbus coupler/ controller.
This value is represented with a 12 bit resolution on bit B3 ... B14.
The three least significant bits (B0 ... B2) are not parsed.
For the standard module 750-550, the numerical values ranging from 0×0000 to 0×7FFF are scaled on the
output voltage ranging from 0 V to 10 V.
 Document number 96780739 Page 141 of 544
Revision 1

Output Value Numerical Value

0 V ... 10 V Binary Status-
Output Value Hex. Dec. byte Hex.
0.00 ’0000.0000.0000.0000’ 0x0000 0 0x00
1.25 ’0001.0000.0000.0000’ 0x1000 4096 0x00
2.50 ’0010.0000.0000.0000’ 0x2000 8192 0x00
3.75 ’0011.0000.0000.0000’ 0x3000 12288 0x00
5.00 ’0100.0000.0000.0000’ 0x4000 16384 0x00
6.25 ’0101.0000.0000.0000’ 0x5000 20480 0x00
7.50 ’0110.0000.0000.0000’ 0x6000 24576 0x00
8.75 ’0111.0000.0000.0000’ 0x7000 28672 0x00
10.00 ’0111.1111.1111.1111’ 0x7FFF 32767 0x00

Manuals and Data Sheets for individual modules are available via the Wago website
(http://global.wago.com/en/services/downloads/download-search/index.jsp?q=750-
433&action=search&frontendId=frontendDownload_cms_de-en&lang=en
 Document number 96780739 Page 142 of 544
Revision 1

Siemens OLM

STUDENT NOTES:

PROFIBUS OLMs are designed for use in optical PROFIBUS fieldbus networks. They allow the conversion of
electrical PROFIBUS interfaces (RS-485 level) into optical PROFIBUS interfaces and vice versa.
The modules can be integrated in existing PROFIBUS fieldbus networks with the known advantages of
optical transmission technology. A complete PROFIBUS fieldbus network can also be set up with modules
in a linear (bus), star or ring topology as well as any combination of these topologies.
To increase the reliability of the fieldbus network in case of failure, the redundant ring is supported.

Key:
1. Status LEDs
2. Channel 1 RS-485
3. Optical channel 2
4. Optical channel 3
5. DIL switch for modes
6. Operating voltage connections
7. Signaling contact connections
8. Signal level measuring points

Reference manual https://cache.industry.siemens.com/dl/files/560/5472560/att_19902/v1/olmv3e.pdf

for details of the LED status.
 Document number 96780739 Page 143 of 544
Revision 1

Bartec LWL

STUDENT NOTES:

The Bartec LWL performs the same function as the Siemens OLM described previously, but is designed for
use in safe areas (zones 1 and 2).

The RS485/PROFIBUS LWL Ring-coupler converts the PROFIBUS from copper conductors to fibers and vice
versa. The LWL Ring-coupler is a passive (transparent) bus participant.

Displays
Operation LED green
Active bus LED yellow
LWL segment fault channel 1 LED yellow
LWL segment fault channel 2 LED red
 Document number 96780739 Page 144 of 544
Revision 1

Bartec Coupler

STUDENT NOTES:

PROFIBUS couplers and PROFIBUS repeaters are used for the separation or generation of new segments,
converting the RS485 typical line structure into an open and flexible tree structure.

Couplers allow the creation of spurs on Profibus networks, such as for remote encoders and linear
transducers on Drawworks and Rackers, without introducing the interference and errors normally
associated with spurs.

In terms of functioning, the PROFIBUS coupler and PROFIBUS repeater are constructed in the same way.
The difference between the PROFIBUS coupler and PROFIBUS repeater lies in the software programmed
in the FPGA logic module. This module is factory programmed before the device is delivered. The devices
also differ in the following: The PROFIBUS coupler processes electrical signals. The PROFIBUS repeater
also processes the signal’s time status. PROFIBUS driver module is connected to every PROFIBUS
connection (AB; A1B1; A2B2...). The PROFIBUS driver module converts the PROFIBUS signals into logical
internal signals and vice versa. Three optocouplers galvanically isolate the input and the outputs.
Electrical, logical and time signals are processed in the FPGA module. The time processing can be adjusted
precisely by means of the S1 switch (baud rate). The FPGA module also generates signals to actuate the
operation status display (BA, BA1, BA2). The input is terminated with the aid of the S2 switch.
The entire circuitry is supplied with an internal power pack. The power pack is configured in accordance
with the valid Ex standard. The power pack galvanically isolates POWER supply/input/output.
 Document number 96780739 Page 145 of 544
Revision 1

See safety alert 11362052-PIB http://eng.nov.com/TC_V3.swf?dn=11362052-PIB for details of possible

faulty couplers which need to be replaced. Contact local tech support for clarification of checks and parts
as bulletin is not clear and does contain errors.
 Document number 96780739 Page 146 of 544
Revision 1

Bartec MODEX I/O

STUDENT NOTES:

MODular EXplosion protection modules are a range of intrinsically safe I/O modules for use in hazardous
areas. Profibus connections are via terminals rather than plug/socket. Terminating resistors are built in
and activated by adding external wire links.

VDR00072 http://eng.nov.com/TC_V3.swf?dn=VDR00072 contains an overview of the range. Use

VDR00072 to find basic info and part numbers, but check the Bartec website for up to date information.
https://www.bartec.de/en/products/automation-enterprise-mobility/bus-technology/modex-bus-
system/
 Document number 96780739 Page 147 of 544
Revision 1

ATOS Driver

STUDENT NOTES:

ATOS E-RI-AES-BP-0*H is an integral digital electronic driver, connected and programmed via PROFIBUS
DP.
These drivers supply Atos proportional valves type ZO-A with a switching current (PWM) regulating the
spool position, the flow or the pressure proportionally to the input reference signal.

Features
Integral digital electronic
Software adjustment of bias, scale, ramps and dither
Regulation characteristic may be optimized on the application to obtain the best specific performances
(linearization, adjustable control time response)
Cable connections, mainly used to provide 24VDC power supply to the driver, coil and enable
connections.

Cable Connections
Signal Description Color
Power Supply +24VDC White
Power Supply 0VDC Brown
Coil S1, side A Green and Yellow
Coil S2, side B Grey and Pink
Output Stage Enable Blue
Case Shield
 Document number 96780739 Page 148 of 544
Revision 1

9 poles D-SUB standard connector dedicated to the Profibus-DP connection

1 Shield
3 A-Line Profibus DP
4 RTS
6 +5V BUS
8 B-Line Profibus DP

2,5A maximum current to the coils

 Document number 96780739 Page 149 of 544
Revision 1

DMA Driver

STUDENT NOTES:

A DMA solenoid driver system typically consists of a Profibus coupler (shown on the right in the photo)
and one or more amplifier modules. The amplifier module DMA-2 is used for
• proportional directional valves direct and pilot operated with feedback
• proportional flow control valves with feedback
• proportional pressure reducing valves with feedback
• proportional pressure regulating valves with feedback

PWM output signals

Solenoid current 2 output stages per amplifier for up to 3.5 A; with over-energization and quick de-
energization

Status LED

Profibus DP:
Red Not connected or Error
Off OK

Status LED’s:
PW Power
EN Enable
ER Error
 Document number 96780739 Page 150 of 544
Revision 1

Rig Tools

STUDENT NOTES:
Document number 96780739 Page 151 of 544
Revision 1
 Document number 96780739 Page 152 of 544
Revision 1

I/O (Physical on Tool)

STUDENT NOTES:

These are a few of many devices used on the tools:

1. Proximity sensor for SPM / pressure switch
2. Solenoid valves for DWs brakes
3. Absolute encoders for DW drum
4. Stand pipe pressure
 Document number 96780739 Page 153 of 544
Revision 1

IS Barriers and Amplifiers

STUDENT NOTES:

IS systems should not be bypassed or modified in any way without NOV engineering approval.
Intrinsically Safe (IS): is a protection technique for safe operation of electrical equipment in hazardous
area by limiting the energy, electrical and thermal, available for ignition in signal and control circuits that
can operate with low currents and voltages.
Areas with dangerous concentrations of flammable gases or dust are found on oil and gas installations in
areas such as drill floor, mud pits, and production areas. High-power circuits such as electric motors or
lighting cannot use intrinsic safety methods for protection.

For an explosion, all three of gas/dust, oxygen and source of ignition (spark or heat) need to be present.
Intrinsic Safety works on the principle of removing the source of ignition. This can be achieved by using a
Zener Barrier or Galvanic Isolator.

A Zener barrier is a simple device where the voltage & current (Power, Energy) is limited into the
hazardous area. The voltage is limited/clamped by a Zener diode and the current limited by an output
resistor. The fuse is there to protect the Zener diode. The key to safety is the intrinsically safe earth.
Without it, there is no protection.

When Zener barriers are used, they need to be considered in 2 modes: Fault condition and operational.
In a fault condition, the input voltage Vi to the Zener barrier is higher than the Zener voltage Vz and the
Zener barrier has to ensure that the output to the hazardous area is limited for safety. Under these
conditions, the ‘Safety parameters’ Uo, Io, Po are the only parameters applicable. These parameters have
nothing to with operational characteristics and define the maximum output power/energy into the
hazardous area. The Zener diodes in the Zener Barrier are connected in the reverse direction. The
 Document number 96780739 Page 154 of 544
Revision 1

breakdown voltage of the diodes is not exceeded in normal operation. If this voltage is exceeded, due to a
fault in the safe area, the diodes start to conduct, If this condition is maintained, the Zener diode(s) is
likely to blow, so the fuse is there to protect it.
When operational, Vin is always less than Vz and minimal current flows through the Zener diode(s). In this
situation, the loop designer needs to take account of end-end resistance, maximum voltage at input
terminals & leakage current through the Zener diodes. A calculation has to be done to ensure that there is
sufficient voltage at the field device for it to function (don’t forget additional voltage required if Hart is
being used). So the voltage at the transmitter will be

Zener Barrier components are carefully specified and selected to ensure safety & operation. Components
cannot be replaced. Once a Zener barrier has done its job and the fuse is blown, a replacement barrier is
required.

Principles of Intrinsic Safety - https://www.youtube.com/watch?v=7WkKw28QJZE

 Document number 96780739 Page 155 of 544
Revision 1

Additional Hardware e.g. UPS

STUDENT NOTES:
 Document number 96780739 Page 156 of 544
Revision 1

UPS System

STUDENT NOTES:

UPS System
A UPS (Uninterruptible Power Supply) can be fitted between the incoming supply and sensitive devices
e.g. control systems. The main purposes of a UPS are to provide backup power through a battery in the
event of incoming power loss, and to clean up the power supply i.e. reduce spikes and ripples to minimize
the risk of damage to the control system.

Not all Amphion systems have a UPS fitted.

Surge Protection Devices (SPD) & EMI/RFI Filters

These UPS components provide surge protection and filter both electromagnetic interference (EMI) and
radio frequency interference (RFI). They minimize any surges or interference present in the mains line and
keep the sensitive equipment protected.

Rectifier/Power Factor Correction (PFC) Circuit

In normal operation, the rectifier/power factor correction (PFC) circuit converts incoming ac power to
regulated dc power for use by the inverter while ensuring that the wave shape of the input current used
by the UPS is near ideal. Extracting this sine wave input current achieves two objectives:
• The incoming power is used as efficiently as possible by the UPS.
• The amount of distortion reflected on the incoming is reduced.
This results in cleaner power being available to other devices in the building not being protected by the
UPS
 Document number 96780739 Page 157 of 544
Revision 1

Inverter
In normal operation, the inverter utilizes the dc output of the power factor correction circuit and inverts it
into precise, regulated sine wave ac power. Upon a mains power failure, the inverter receives its required
energy from the battery through the dc-to-dc converter. In both modes of operation, the UPS inverter is
on-line and continuously generating clean, precise, regulated ac output power.

Battery Charger
The battery charger utilizes energy from the mains power and precisely regulates it to continuously float
charge the batteries. The batteries are being charged whenever the UPS is connected to mains power.

Dc-to-Dc Converter
The dc-to-dc converter utilizes energy from the battery system and raises the dc voltage to the optimum
operating voltage for the inverter. This allows the inverter to operate continuously at its optimum
efficiency and voltage, thus increasing reliability.

Battery
The UPS utilizes valve-regulated, non-spillable, lead acid batteries. To maintain battery design life,
operate the UPS in an ambient temperature of -15°C to +25°C (+59°F to +77°F). Optional external battery
cabinets are available to extend battery backup times.

Dynamic Bypass
The UPS provides an alternate path for mains power to the connected load in the unlikely event of a UPS
malfunction. Should the UPS have an overload, over temperature, or any other UPS failure condition, the
UPS automatically transfers the connected load to bypass. Bypass operation is indicated by an audible
alarm and illuminated amber Bypass LED (other LEDs may be illuminated to indicate the diagnosed
problem). To manually transfer the connected load from the inverter to bypass, press the
Standby/Manual Bypass button once and hold it for about 2 seconds.
 Document number 96780739 Page 158 of 544
Revision 1

UPS – Power Quality

STUDENT NOTES:

Power Quality Problem Description Time scale

Temporary Interruption Planned or accidental loss of utility voltage Seconds to minutes
Long-Term Interruption Planned or accidental loss of utility voltage Minutes to Hours
Momentary Interruption Very short planned or unplanned Milliseconds to Seconds
loss of Utility voltage
Sag or Under-Voltage A decrease in utility voltage Milliseconds/Seconds Under-
Voltage – Longer than a few
seconds
Swell or Over-Voltage An increase in utility voltage Milliseconds/seconds Over-
Voltage – Longer than a few
seconds
Transient, Impulse or Spike A sudden voltage in voltage (several Microseconds
hundred to thousands of V)
Notch A disturbance of opposite polarity from Microseconds
a waveform
Noise An unwanted electrical signal of Sporadic
high frequency from other equipment
Harmonic Distortion An alteration of the pure sinewave, due
to nonlinear loads
 Document number 96780739 Page 159 of 544
Revision 1

UPS Keypad

STUDENT NOTES:

Key:
1. Battery Level Indicators
2. Load Level Indicators
3. Bypass Indicator
4. Inverter Indicator
5. Battery Indicator
6. Standby/Manual Bypass Button
7. On/Alarm Silence/Manual Battery Test Button
8. AC Input Indicator
9. Fault Indicator

On/Alarm Silence/Manual Battery Test Button

This button controls output power to connected load(s) and has three functions:
• On: Pressing this button for four seconds will start the UPS.
• Alarm Silence: To silence alarms, press this button for at least one second. After the alarm is
silenced, the UPS will reactivate the alarm system to alert of additional problems. NOTE: The Low
Battery and Bypass reminder alarms CANNOT be silenced.
• Manual Battery Test: To initiate a manual battery test, press the On button for at least one second
while operating from mains power with no alarm conditions present. If only three of the five
Battery LEDs illuminate, allow the UPS to recharge the batteries for 24 hours. After 24 hours,
retest the batteries.
 Document number 96780739 Page 160 of 544
Revision 1

After the batteries have been retested, if only three of the five Battery LEDs illuminate, contact your local
dealer, SolaHD representative, or SolaHD Technical Support.

Standby/Manual Bypass Button

This button controls output power to connected load(s) and has dual functions: Standby and Manual
Bypass.

NOTE: Pressing the Standby/Manual Bypass button once will transfer the load to bypass power and the
load will be unprotected from disturbances in the mains supply. Pressing the Standby/Manual Bypass
button twice within four seconds while on bypass will cut off power to the output sockets and connected
loads. Perform all necessary shutdown procedures on connected loads before pressing this button twice.

Reference Document 10516581 – S4KC Series Industrial On-line UPS

 Document number 96780739 Page 161 of 544
Revision 1

Battery Level Indicators

STUDENT NOTES:

The Battery Level indicator is composed of five sets of LED bars that illuminate and flash to indicate the
battery capacity level. The UPS battery capacity level is shown in 20% increments (± 5%). The Battery
Level indicators display approximate battery capacity at all times.

Reference Document 10516581 – S4KC Series Industrial On-line UPS

 Document number 96780739 Page 162 of 544
Revision 1

Load Level Indicators

STUDENT NOTES:

The Load Level indicator is composed of five sets of LED bars that illuminate to indicate the relative load
on the UPS output in 25% increments (± 5%). The Load Level indicators display the approximate electrical
load placed upon the UPS at all times.

Reference Document 10516581 – S4KC Series Industrial On-line UPS

 Document number 96780739 Page 163 of 544
Revision 1

UPS Status Indicators

STUDENT NOTES:

UPS status is indicated by five symbols: Fault indicator, Ac Input indicator, Battery indicator, Inverter
indicator and Bypass indicator

Reference Document 10516581 – S4KC Series Industrial On-line UPS

 Document number 96780739 Page 164 of 544
Revision 1

UPS Homepage in Amphion

STUDENT NOTES:

Information is available on a device webpage (if supported) and is split into 5 tabs, Monitor, Control,
Configure, Event Log and Support
Not all UPS systems will have this type of interface. Older systems may have digital/analogue I/O interface
or simple Ethernet connection for basic info. Features are manufacturer dependent.

http://www.emerson.com/catalog/en-us/solahd-multilink
 Document number 96780739 Page 165 of 544
Revision 1

UPS Homepage in Amphion- Healthy

STUDENT NOTES:

Monitor tab when looking at a healthy system

 Document number 96780739 Page 166 of 544
Revision 1

UPS Homepage in Amphion- AC Mains Failure

STUDENT NOTES:

Monitor tab during a fault condition (No incoming supply), system is running on battery back-up
Document number 96780739 Page 167 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 168 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 169 of 544
Revision 1

Amphion Signal Path Overview

STUDENT NOTES:
 Document number 96780739 Page 170 of 544
Revision 1

Lesson Objectives

STUDENT NOTES:
 Document number 96780739 Page 171 of 544
Revision 1

Operator Workstation to Ethernet

STUDENT NOTES:
Document number 96780739 Page 172 of 544
Revision 1
 Document number 96780739 Page 173 of 544
Revision 1

HMI > Ethernet

STUDENT NOTES:

Physical connection between HMI and Ethernet Network.

The HMI’s are connected to the tool network through Ethernet connections from the HMI’s centre column
or backpack. Any HMI connected to this network can display any tool pages connected to the network.
 Document number 96780739 Page 174 of 544
Revision 1

HMI > Ethernet

STUDENT NOTES:

Amphion WebObject is shown on LHS, no corresponding physical I/O identifier on RHS since NET I/O
doesn’t have any external references

Click the NET tab to display all Net I/O types.

Transmission: Ethernet
I/O Type: NET
I/O Identifier: Streamed or Non Streamed. 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).

Screenshots show Deadman Override via the operator screen and the tie in with Net I/O
 Document number 96780739 Page 175 of 544
Revision 1

Physical Switch > I/O Module > Ethernet

STUDENT NOTES:

Physical connection between hardwired switches/buttons and Ethernet I/O

 Document number 96780739 Page 176 of 544
Revision 1

Physical Switch > I/O Module > Ethernet

STUDENT NOTES:

Amphion WebObject on LHS, physically connected Ethernet identifier on RHS. Modbus nodes are given
‘string’ name as opposed to a number, ‘Chair’ is the same as Ethernet node 82, ‘ChairDI0.8’ is the same as
‘82DI0.8’

Modbus is a protocol suite designed for industrial automation as is Profibus. Profibus is byte-oriented,
whereas Modbus is word-oriented.

Transmission: Ethernet
I/O Type: MOD
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.
I/O identifier examples:
MCCDQ6.2: Refers to a digital output (DQ) point writing to bit 2 of byte 6 on Modbus name MCC
ChopperIR16: Refers to a (floating point) real input (IR) value that would be read from bytes 16 through
19 on Modbus name Chopper1Chopper2SI4_30: Refers to a string input (SI) value that would be read
from bytes 4 through 33 on Modbus name Chopper
 Document number 96780739 Page 177 of 544
Revision 1

Joystick > J1939 Converter > Ethernet

STUDENT NOTES:

Physical connection between Joystick, J1939 Converter (Gateway) and Ethernet

The joysticks connect to chair control via CANbus module using CAN J1939 protocol. The joystick comes
with a four conductor flying lead for the CANbus and power signals. All signals from the joystick handle are
gathered into the CANbus base and are terminated into the CANbus module. This simplifies cabling
significantly. The signals are then sent to a J1939 converter module. From there, the signals are sent over
Ethernet to the chair centre column or backpack.
 Document number 96780739 Page 178 of 544
Revision 1

Joystick > J1939 Converter > Ethernet

STUDENT NOTES:

Amphion WebObject on LHS, I/O address detailed on RHS

Modbus is a protocol suite designed for industrial automation as is Profibus. Profibus is byte-oriented,
whereas Modbus is word-oriented.

Transmission: Ethernet
I/O Type: MOD
I/O Identifier: [Modbus node string][I/O Type code][Word Number]{.[Bit Number]}{_[String Length]}
 Document number 96780739 Page 179 of 544
Revision 1

Ethernet to SBC

STUDENT NOTES:
Document number 96780739 Page 180 of 544
Revision 1
 Document number 96780739 Page 181 of 544
Revision 1

Ethernet > SBC

STUDENT NOTES:

LHS image is of Moxa Ethernet switches mounted inside the Multi Tool Control Cabinet (MTC #2), RHS
image shows Moxa Ethernet switch number 2 detailing the RJ45 ports used to directly connect to an SBC
 Document number 96780739 Page 182 of 544
Revision 1

C2C – Communications Between SBCs

STUDENT NOTES:

The purpose of this type is to receive inputs from the other controllers, as opposed to sending commands
to them. Therefore, only input classes are assigned to this I/O type. C2C is always input, never output;
every controller can read data from other controllers but no controller can write to another controller.

Transmission: Ethernet
I/O Type: C2C
I/O Identifier:[remote controller name]:[remote controller WebObject name]
LHS shows the Amphion WebObject used by the Drawworks controller adsblock.lo.BlockRetractedDI ; RHS
shows the identifier where that information is obtained TopDrive:TDS.Dolly.dq.Retracted.value

NOTE: 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.
Document number 96780739 Page 183 of 544
Revision 1

SBC to Remote I/O

STUDENT NOTES:
Document number 96780739 Page 184 of 544
Revision 1
 Document number 96780739 Page 185 of 544
Revision 1

SBC > Profibus Remote I/O

STUDENT NOTES:

Top shows Profibus connection from Applicom card to Optical Link Module (OLM) to fiber patch panel
then to Drawworks Remote I/O Junction Box

Bottom shows incoming fiber to fiber optic connector to OLM and back to Profibus
 Document number 96780739 Page 186 of 544
Revision 1

SBC > Profibus Remote I/O

STUDENT NOTES:

Shows Profibus ‘daisy chain’ to Bartec 16x DI N.I.S. Brick, Profibus node 10, continuation on next sheet of
interconnect
 Document number 96780739 Page 187 of 544
Revision 1

SBC > Ethernet Remote I/O

STUDENT NOTES:

Top shows Power Supply (PS-03 and PS-04) with status monitoring switches connected to DI 3.5 and 3.6
shown below

ZMS Lockout Switch mounted on the outside of the MTC cabinet is connected to DI 3.4
 Document number 96780739 Page 188 of 544
Revision 1

Remote I/O > Tool Control and Feedback

STUDENT NOTES:
Document number 96780739 Page 189 of 544
Revision 1
 Document number 96780739 Page 190 of 544
Revision 1

Remote I/O > Tool Control and Feedback

STUDENT NOTES:

Shows field devices physically connected to remote I/O module

 Document number 96780739 Page 191 of 544
Revision 1

Remote I/O > Tool Control and Feedback

STUDENT NOTES:

Profibus DP1 or DP2

Profibus is a common standard for control in industrial automation. Profibus I/O takes place over its own
network, separate from the Ethernet network. In order to connect a controller computer to a Profibus
network, we need to connect a PC104 card, a piece of hardware, to the controller. Our PC104 cards and
the drivers for them come from Applicom, a company in France. It is possible to connect two cards. With
two cards, the controller computer can participate in two different Profibus networks at once (typically
early ZMS SBCs).
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.
It’s possible for a controller computer to run without any Profibus card, but if there is a card, the first one
is always DP1. There would never be a DP2 card by itself. Note that DP1 and DP2 are distinct networks.
Each one has an entirely different address space. So, it might be possible to find an I/O identifier for DP1
that is exactly the same as an I/O identifier for DP2; it's not an address conflict.

Transmission: Profibus
I/O Type: DP1 or DP2
I/O Identifier: [Profibus Node Number][I/O type code][Byte Number]{.[Bit Number]}/{_[String Length]}

LHS shows the Amphion WebObject and the RHS shows the physically connected I/O address
 Document number 96780739 Page 192 of 544
Revision 1

Each Profibus network is divided into nodes. A node usually refers to some physical object, like a block of
I/O or a device. It might be a single Hengstler encoder or a drive. Each node has a number that is assigned
to it as its address. There can be up to 125 nodes on a single Profibus network, with addresses of 1 to 125.
However, our ProfibusManager class allows us to use only node addresses 4 to 125. Alec Faer (Principle
Software Engineer – Amphion) says that Node 1 is reserved for devices connected directly to the
controller. Node 2 is reserved for the controller itself. Node 3 is reserved as the default node that helps us
identify wrongly-assigned I/O.
The I/O identifier also uses an I/O type code that specifies whether the I/O point that is created is an input
or an output, and what type of data it will support. The allowed type codes for Profibus are:
• DI - digital input (1 bit)
• DQ - digital output (1 bit)
• AI - analogue input (2 byte, integer)
• AQ - analogue output (2 byte, integer)
• RI - real input (4 bytes, floating point)
• RQ - real output (4 bytes, floating point)
• IW - analogue word input (2 bytes, integer)
• QW - analogue word output (2 bytes, integer)
• ID - analogue double word input (4 bytes, integer)
• QD - analogue double word output (4 bytes, integer)
• SI - string input
• SQ - string output
The I/O identifier for a Profibus network refers to a specific byte (and sometimes a specific bit) at a given
node. Only the digital inputs and outputs need to specify the bit number. The range of byte numbers is
from 0 to 255. The range of bit numbers, when given, are from 0 to 7.
The string inputs and outputs are a little different. A string input or output needs to end with the byte
number followed by an underscore, followed by an integer that represents the length of the string in
bytes.
So, for example, an I/O identifier for a Profibus I/O point might be “12DQ6.2”—this would refer to a
digital output point writing to bit 2 of byte 6 on Profibus node 12. Another I/O identifier might be
“8RI16”—this would refer to a real (floating point) input value that would be read from bytes 16 through
19 on Profibus node 8. Another I/O identifier might be “21SI4_30”—this would refer to a string input
value that would be read on bytes 4 through 33 on Profibus node 21.
 Document number 96780739 Page 193 of 544
Revision 1

Signal Path Overview

STUDENT NOTES:
 Document number 96780739 Page 194 of 544
Revision 1

Video for Signal Path

STUDENT NOTES:

Video can be viewed/downloaded from http://rigflix.nov.com/RigFlix/Video/94916818?q=amphion in

Internet Explorer.
Document number 96780739 Page 195 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 196 of 544
Revision 1

Amphion Network and Communications

STUDENT NOTES:
 Document number 96780739 Page 197 of 544
Revision 1

Lesson Objectives
Document number 96780739 Page 198 of 544
Revision 1

Topology

STUDENT NOTES:
 Document number 96780739 Page 199 of 544
Revision 1

Topology

STUDENT NOTES:

Topology document shows hardware layout and communication cable type, additional pages detail
Ethernet Switch layout and configured IP Address range.
Drawing is spilt up into individual areas such as Drillers Cabin, Drive House, Drill Floor and Office. The
hardware components contained within each area are detailed.

EF – Ethernet Fiber Optic Cables, connecting Moxa Switches in a redundant ring. Also shown between
Moxa Industrial Media Converters in the Power System Control cabinet and Offices and Mud Pump
Remote I/O Systems

PF – Profibus Fiber Optic Cables, connecting Remote I/O to an SBC via an Optical Link Module (OLM)

Fiber Optic Cable Specification - Multimode Fiber – Reference Document D8011001614-SPC Amphion
Fiber Optic Cable Specification
Fiber Size 62.5/125 um
Capacity Data rates up to 100 Mbps
System Type Both data and voice
Distance Used for links less than 5 km in length
Operating Wavelength 850 nm (first window) 1300 nm (second window)
Attenuation 850 nm is 3.3 to 5.0 dB/km, 1300 nm is .9 to 3 dB/km
Fiber Type Glass only
Metal/Ceramic Connectors
 Document number 96780739 Page 200 of 544
Revision 1

NIS – Non-Intrinsically Safe cabling, Examples from drawing are between Drillers Workstation and Drill
Floor Remote I/O Cabinet and BOP Panel inside Drillers Cabin and BOP Remote I/O mounted on the BOP
Skid

E – Ethernet Network cables, connecting Ethernet devices to the Moxa network

RJ45 (8-Pin) to RJ45 (8-Pin) Straight-Through Cable Wiring

TX+ Pin 3 ---------- Pin 3 RX+
TX- Pin 6 ---------- Pin 6 RX-
RX+ Pin 1 ---------- Pin 1 TX+
RX- Pin 2 ---------- Pin 2 TX-

RJ45 (8-Pin) to RJ45 (8-Pin) Cross-Over Cable Wiring

(RX+) TX+ Pin 3 ---------- Pin 1 RX+ (TX+)
(RX-) TX- Pin 6 ---------- Pin 2 RX- (TX-)
(TX+) RX+ Pin 1 ---------- Pin 3 TX+ (RX+)
(TX-) RX- Pin 2 ---------- Pin 6 TX- (RX-)

Cat 5 Cable Specification – Supports category 5 applications such as; 10 Base-T, 100 Base-T, FDDI, ATM

Construction and Dimensions

Construction Shielded 4 twisted pairs
Conductor Stranded bare copper (7 x 0.16mm)
Conductor diameter AWG 26 (0.48mm)
Conductor insulation material Foam skin polyethylene (PE)
Diameter over insulation 0.95 ± 0.05mm
Drain wire Tinned copper 18 x 0.10mm
Shield Aluminum / polyester foil
Jacket material PVC (Flame retardant)
Outer diameter 5.2 ± 0.2mm

Color Code
Pair 1 White-Blue/Blue
Pair 2 White-Orange/Orange
Pair 3 White-Green/Green
Pair 4 White-Brown/Brown

DP – Profibus DP, connecting Remote I/O and Profibus devices to an SBC via an Applicom card

Profibus DP Cable – Specification – Reference Document – 1578138, Cable Profibus

Design
Shielded, Twisted-Pair Cable with Circular Cross Section 22AWG Solid Bare Copper Conductors
Sheath
Material PVC
Diameter 8.0 ± .4mm (.31 IN ± .02 IN)
Color Violet
Temperature -40°C to +60°C (-40°F to +140°F)
 Document number 96780739 Page 201 of 544
Revision 1

Bending Radius Greater Than 76mm (3 in)

Weight 76KG/KM (.045 LBS/FT)

UV Listing / 300V Rating / 600V Rating

UV Resistant
Fastconnect Cable Installation

Siemens Part Number 6XV1830-0EH10

Belden Cable Part Number 3079A
 Document number 96780739 Page 202 of 544
Revision 1

Topology example with visual representation

 Document number 96780739 Page 203 of 544
Revision 1

Topology – Ethernet Converters

STUDENT NOTES:

Ethernet Converters
Moxa Industrial Media Converter, which is specially designed for reliable and stable operation in harsh
industrial environments, provides industrial grade media conversion between 10/100BaseT(X) and
100BaseFX.

Key:
1. Grounding screw
2. Terminal Block for power input PWR1/PWR2 and relay output
3. Heat dissipation orifices
4. Dip switch
5. Power input PWR1 LED
6. Power input PWR2 LED
7. Fault LED
8. 100BaseFX (ST Connector) Port
9. FX ports 100 Mbps LED
10. FX ports Full Duplex/Collision LED
11. TP ports 100 Mbps LED
12. 10/100Base T(X)
13. TP ports 10 Mbps LED
14. Model Name

See Hardware Installation Guide for Dip Switch settings and LED Indicators
Document number 96780739 Page 204 of 544
Revision 1

Reference Documents 942922-055-MAN and 942922-055:58P-DAS

 Document number 96780739 Page 205 of 544
Revision 1

Topology – Profibus OLM

STUDENT NOTES:

Siemens Profibus OLM

PROFIBUS OLMs are designed to be used in optical PROFIBUS field bus networks. They enable electrical
PROFIBUS interfaces (RS 485 level) to be converted into optical PROFIBUS interfaces and vice-versa.
By profiting from the familiar advantages of optical transmission technology, the modules can be
integrated into existing PROFIBUS field bus networks. A complete PROFIBUS field bus network with
modules in line, star or ring topology, and an arbitrary combination of these, can also be built up.
The redundant ring is also supported, thereby increasing the fail-safety of the field bus network.
Each module has two or three mutually independent ports, which in turn consist of a transmitting and a
receiving component.
The device is powered by 24V DC voltage. A redundant feed increases operational safety.
The electric port is a 9-pole Sub-D socket (female). An RS 485 bus segment in line with the PROFIBUS
standard EN 50170 can be connected to this port.
The optical fibers are connected using BFOC1) /2.5 connectors.
Four multi-colored light-emitting diodes indicate the current operating status and possible operating
malfunctions.

Key:
1. Operating voltage supply/signaling contact 5-pole terminal block
2. LED Indicators
3. Measuring Sockets
4. Port 1 electric, sub-D socket
5. Port 2 optical, *BFOC/2.5 socket
 Document number 96780739 Page 206 of 544
Revision 1

6. Port 3 optical, *BFOC/2.5 socket

*BFOC stands for Bayonet Fiber Optic Connector. This connector type is functionally compatible with ST ®
connectors.

Reference Document including Dip Switches and LED Indicator reference

https://cache.industry.siemens.com/dl/files/560/5472560/att_19902/v1/olmv3e.pdf
 Document number 96780739 Page 207 of 544
Revision 1

Topology

STUDENT NOTES:

The Moxa Switch network layout is shown here, IP Addresses of individual switches and connected
devices are not detailed. The number of switches within each location is shown along with Cable ID
between locations. The Cable ID shows the Fiber Size – 62.5/125um and also the number of cores
 Document number 96780739 Page 208 of 544
Revision 1

Topology

STUDENT NOTES:

IP Address Configuration is shown here, should be a comprehensive list of all IP addresses used on a
particular installation.
 Document number 96780739 Page 209 of 544
Revision 1

Profibus Remote I/O Applications

STUDENT NOTES:
 Document number 96780739 Page 210 of 544
Revision 1

Profibus Applications – Proximity Sensor

STUDENT NOTES:

Reference Document – 93939, Sensor, Inductive Proximity

 Document number 96780739 Page 211 of 544
Revision 1

Profibus Applications – Proximity Sensor

STUDENT NOTES:

Reference Drawing – 10700488-DIA, Interconnect Diagram, Auxiliary

Sensor on tool, wired back to Up/Down Counter Module (750-404) via I.S. Junction Box and I.S. Switch
Isolator (P/N 10043273)
 Document number 96780739 Page 212 of 544
Revision 1

Profibus Applications – Proximity Sensor (I.S. Barrier)

STUDENT NOTES:

I.S. Barrier (P/N 10043273) and associated Data Sheet

 Document number 96780739 Page 213 of 544
Revision 1

Profibus Applications – Proximity Sensor (Wago 750-404)

STUDENT NOTES:

Device and Data Sheet – Available from Wago Website -

http://global.wago.com/en/services/downloads/download-search/index.jsp?q=750-
404&action=search&frontendId=frontendDownload_cms_de-en&lang=en

Up/Down Counter Module – Wago 750-404

Device Description
The Up/Down counter 750-404 and the variation 750-404/000-004 is capable of counting binary pulses of
DC 24 V at the input CLOCK and then transmits the data to the fieldbus.
The counter module 750-404/000-002 begins processing with pulses at the CLOCK input and counts the
pulses in a special time span. The time span is given as 10 s.
The changes from 0 V to 24 V are counted
The counter counts up, if the input U/D is set at 24 V. With an open circuit input or 0 V the counter counts
backwards
The counter can be set or reset with the control byte.
The digital outputs DO 1 and DO 2 of the counter module 750-404 and the variation 750-404/000-002 are
activated through bits in the control byte.
The digital outputs DO 1 and DO 2 of the counter module 750-404/000-004 are activated depending on
the counter reading or through bits in the control byte.
The outputs are short-circuit-protected.
The high states of the inputs U/D and CLOCK and the digital output channels are each indicated by a green
LED.
 Document number 96780739 Page 214 of 544
Revision 1

The up/down counter is capable of counting binary pulses of 24VDC and then transmitting the data to the
fieldbus.
A counter lock-out is also possible.

Process Image
Using the I/O module 750-404, a 5 byte input and output process image can be transferred to the fieldbus
coupler / controller via one logical channel.
The transfer of the setting counter value in binary format is made via 4 output bytes (D0 ... D3) and the
transfer of the counter reading in binary format is made via 4 input bytes (D0 ... D3). The control byte C0
serves for setting the counter and the outputs. The status byte S0 shows the status of the counter and the
inputs and outputs.

Input data Output data

S0 Status byte 0 C0 Control byte 0
D0 Counter value byte 0 (LSB) D0 Set value byte 0 (LSB)
D1 Counter value byte 1 D1 Set value byte 1
D2 Counter value byte 2 D2 Set value byte 2
D3 Counter value byte 3 (MSB) D3 Set value byte 3 (MSB)

Control / Status byte 750-404

The control byte C0 serves for setting and locking the counter and for setting the outputs. The status byte
S0 shows the status of the counter and the inputs and outputs.

Control byte
B7 B6 B5 B4 B3 B2 B1 B0
0 0 Set Lock Set Set 0 0
Counter Counter Output Output
DO 2 DO 1
0 This constant must be set to zero

Status byte
B7 B6 B5 B4 B3 B2 B1 B0
X X Counter Counter Actual Actual Actual Actual
is set is signal at signal at signal at signal at
blocked output output input input
DO 2 DO 1 U/D CLOCK
X This value is not evaluated
With the control and status byte the following tasks are possible:

Set Counter:
Put Bit 5 into the control byte. The counter with the 32 bit value is loaded into output bytes 0-3. As long as
the bits are set, the counter can stop and information is stored. The ensuing data of the counter will be
conveyed to the status byte.

Lock Counter:
Bit 4 is set into the control byte, and then the count process is suppressed. Bit 4 in the status byte
communicates the suppression of the counter.
 Document number 96780739 Page 215 of 544
Revision 1

Set/ Reset Outputs:

Bits 2 and 3 set the additional two outputs of the counter module.
 Document number 96780739 Page 216 of 544
Revision 1

Profibus Applications – Proximity Sensor

STUDENT NOTES:

Input/Output addressing shown via Applicom I/O ties in directly with addressing shown on schematic,
RotaryTable.ai.Speed.ioIdentifier can be found from within the NET I/O tab within I/O Diagnostic via the
Service Pages
 Document number 96780739 Page 217 of 544
Revision 1

Profibus Applications – Solenoid Valve

STUDENT NOTES:

Reference Document – 112554, Solenoid Valve (EExd)

 Document number 96780739 Page 218 of 544
Revision 1

Profibus Applications – Solenoid Valve

STUDENT NOTES:

Reference Document – 10667775-DIA, Interconnect Diagram, Rowan Gorilla VI PRS

Solenoid valve wiring from tool back to Digital Output module at Node 10
 Document number 96780739 Page 219 of 544
Revision 1

Profibus Application – Solenoid Valve (Bartec 16* digital out)

STUDENT NOTES:

Device and Data Sheet – Available from Bartec Website -

https://www.bartec.de/en/products/automation-enterprise-mobility/bus-technology/modex-bus-
system/profibus-interface-16-x-digital-out/

Device Description
This module allows the activation of 16 actuators in the hazardous area via PROFIBUS-DP.
For example, encapsulated solenoid valves or indicator lamps can be directly activated with 24 V/500 mA.
LEDs on the front of the module output bus status as well as output states.
 Document number 96780739 Page 220 of 544
Revision 1

Profibus Applications – Solenoid Valve

STUDENT NOTES:

Profibus Node 10 viewed from I/O Diagnostic

Amphion WebObject on LHS and physical wiring location on RHS, tailingArm.jaw.claw.dq.OPEN – 10DQ0.0
etc.
 Document number 96780739 Page 221 of 544
Revision 1

Profibus Applications – Absolute Encoder

STUDENT NOTES:

Device and associated part drawing, detailing Mechanical/Electrical data and hardware specific notes

Table 3 shows cable connection details

Black 0VDC Supply Voltage (Return)

Blue -10…30VDC Supply Voltage (Positive)
Grn/Y PE Earth (Connected Internally to Housing)
Green A Profibus Signal A
Red B Profibus Signal B
 Document number 96780739 Page 222 of 544
Revision 1

Profibus Applications – Absolute Encoder

STUDENT NOTES:

Reference Document – 10677058-DIA Interconnect Diagram, ADS-30Q

Device wiring to Profibus DP Coupler, which allows connection of three absolute encoders, single Profibus
cable is daisy chained to Profibus network. 24v Encoder supply is not through DP Coupler.
 Document number 96780739 Page 223 of 544
Revision 1

Profibus Applications – Absolute Encoder

STUDENT NOTES:

Profibus Node 20 via I/O Diagnostic, shows Amphion WebObject on LHS and Profibus address on RHS
 Document number 96780739 Page 224 of 544
Revision 1

Profibus Applications – Pressure Transmitter

STUDENT NOTES:

Reference Document 30156355-ASM, Press Xmtr PTX 651

 Document number 96780739 Page 225 of 544
Revision 1

Profibus Applications – Pressure Transmitter

STUDENT NOTES:

Reference Document 10677058-DIA and Interconnect Diagram, ADS-30Q

Shows Pressure Transmitter on tool directly wired to a Bartec AI module within a Transmitter J-Box
 Document number 96780739 Page 226 of 544
Revision 1

Profibus Applications – Pressure Transmitter

STUDENT NOTES:

Profibus Node 15 via I/O Diagnostics, Amphion WebObject shown on LHS and Physical address on RHS
Document number 96780739 Page 227 of 544
Revision 1

Modbus Remote I/O Applications

STUDENT NOTES:
 Document number 96780739 Page 228 of 544
Revision 1

Modbus Applications – Chair Adjustments

STUDENT NOTES:

Reference Document – 11405405-DIA Amphion, Drillers Workstation

Digital Outputs wired from chair backpack Wago Modules, Address 192.168.31.82 – Referred to as Node
‘Chair’
 Document number 96780739 Page 229 of 544
Revision 1

Modbus Applications – Chair Adjustments

STUDENT NOTES:

Reference Document – 11405405-DIA Amphion, Drillers Workstation

Wiring from Wago Digital Outputs to individual relays, then to 12V Chair Movements Controllers; Part
Number 10654076
 Document number 96780739 Page 230 of 544
Revision 1

Modbus Applications – Chair Adjustments (C2 – 15)

STUDENT NOTES:

No User Manual or Data Sheet available via Teamcentre using part number on previous drawing, however
a little bit of digging online and a manual was found which matches the part number; the wiring diagram
ties in directly with the electrical schematic

http://www.concens.com/sites/default/files/downloads/manual-c2-15-concens-ver-12-sep-2011_1.pdf
 Document number 96780739 Page 231 of 544
Revision 1

Modbus Applications – Chair Adjustments

STUDENT NOTES:

On screen buttons for individual movement Input and Digital Outputs shown via I/O Diagnostics. Amphion
WebObject shown on LHS and Physical address on RHS

WebObject's associated with on screen buttons and other functions can be found using WidgetEditor; the
use of this software will be covered later in later presentations
Document number 96780739 Page 232 of 544
Revision 1
 Document number 96780739 Page 233 of 544
Revision 1

Amphion Signal Path Detailed

STUDENT NOTES:
 Document number 96780739 Page 234 of 544
Revision 1

Lesson Objectives

STUDENT NOTES:
Document number 96780739 Page 235 of 544
Revision 1

Workstation Software

STUDENT NOTES:
 Document number 96780739 Page 236 of 544
Revision 1

HMI – Operator Pages

STUDENT NOTES:

Operator vs Service Pages

The user interface is divided into two broad sections: the operator pages and the service pages.

Operator pages are intended to be used by operators of NOV equipment during the normal course of
operations. The operator pages provide elements such as buttons, virtual joysticks, and sliders to control
the hardware tools (such as drill pipe handling equipment), and also lamps, gauges, graphs, read-outs,
and other indicators to allow the operator to see the current state of the tool or tools.
The screens that the operator sees are contained by one big Java applet which is designed to take over
the entire screen area and (with some exceptions) will not allow the operator to navigate away from it.
This "one big applet" is the "Widget" applet. It includes a navigation bar that allows the operator to
navigate within it from tool to tool and screen to screen. Each tool contains one or more operator or
diagnostic screens that allow the operator to control that tool. The operator screens are XML (eXtensible
Markup Language) documents that contain precise definitions of what controls or "widgets" are to be
displayed on the screen, where those controls are, and what those controls do. A tool screen designer can
use an editor (the "Widget Editor") to create any combination of buttons, lamps, read-outs, graphs, etc.
that the operator needs to control the tool.
Because our HMIs are usually touch-screen devices, the operator screens are designed to be used with a
touch-screen only. They are not intended to be used with a mouse and keyboard. Therefore, buttons
need to be larger than one normally might expect on a computer screen.
The standard screen sizes that we use are 1020 x 673 for a 15" XGA monitor (1024 x 786) and 1276 x 929
for a 19" SXGA monitor (1280 x 1024).
 Document number 96780739 Page 237 of 544
Revision 1

Service pages, on the other hand, are designed to be used by service and maintenance personnel, and not
by equipment operators. Service personnel are expected to interact with the tools and equipment in two
different ways: first, by working hands-on, out on the drill floor directly with the equipment, and second,
by interacting with tool software and screen interfaces, but in an environment away from the drill floor. It
seems a bit odd, but the service pages are intended to be used on a HMI or other computer outside of the
hazardous drill floor area. Therefore, they are designed to be used with a keyboard and mouse. The
service pages look and act more like standard HTML pages.

Where do all the screen files go?

One of the basic things that all developers should know is where to put the various screen files that they
have created. Screen files include operator, calibration, diagnostics, maintenance mode and backup
controls. Below is a list of paths and where each screen should be located.

/varco/www/operator
This folder should contain the standard operator screen as defined in the ownership.xml or
nav_config.xml. On older systems (pre www_1.6.0) the ownership_tattler.xml was also located here. It
has also been known for any backup control screens that allow a tool to be operated in the event of the
operator's console failing to be installed in the operator folder. If the SBC is networked with other tools
on a rig package, any process screens should also be installed here.
/varco/www/operator/Cathead (or /varco/www/operator/RotaryTable or...)
Operator screens that are specific to a tool on a multi-tool SBC are usually separated into sub-directories
of the operator directory and identified by tool name.
/varco/www/operator/maint
This folder should contain all maintenance mode control screens. These screens should be navigated to
from the main navigation menu at the bottom of the operator pages.
/varco/www/operator/maint/calib
This folder should contain any screens that are used for calibration. These include PID tuning, ATOS tuning
and axis calibration. Control of these screens should not be possible unless the tool is in maintenance
mode and switched on. These screens should also be navigated to from the main navigation menu at the
bottom of the operator pages.
/varco/www/operator/maint/diag
This folder should contain any screens used for diagnostics. These would include screens that provide
graphical or numerical information about an axis or tool component. These screens should also be
navigated to from the main navigation menu at the bottom of the operator pages.
/varco/www/maintenance
If you make screens for the service pages (Use the service page configuration link to make links for them.),
then these screens files can live in the maintenance directory.
(Historical Note: Yes, these directories have been traditionally used to organize various types of screens.
At the moment, screen files can actually be located anywhere on the SBC. For this reason, the file paths in
the navigation configuration XML files require that you give the full path name of the screen document.)
By convention, screen names are all lower-case letters (this is a standard Internet convention) and should
not include spaces (use a hyphen or underline instead). Any spaces or other "special" characters need to
be rendered into "URL-encoding" and that can be difficult to type or remember.

Amphion Operator Screens are created following the Amphion Software groups standards. The manual
details Amphion Touch Screen Standards in relation to Operator screens; Indicator Lamps, Message
Indicators, Display Panels, Pop-up Panels, Artist Panels and Co-ordinates and Colors. Status Screens,
Maintenance Screens, Calibration Screens, Back-up Screens and Guidelines for the Navigation Bar.
 Document number 96780739 Page 238 of 544
Revision 1

Examples of the guidelines are those in relation to indicator lamp colors;

• A green color should indicate that a positive action under normal tool operation has occurred.
• A yellow color should indicate that some action has occurred that would require the operator to
take some additional steps, be vigilant, or do some other action. This would be under normal tool
operation.
• A red color should indicate that some event has taken place outside the normal operations of the
tool or process and may present some sort of hazard or danger to the operator(s), machine, or
process.
• A gray color should indicate where the test description is not active.

Reference Document D6A-1000039-MAN-001, Amphion Software Group Touch Screen Standards

 Document number 96780739 Page 239 of 544
Revision 1

Widget Editor – Viewing Only OFFLINE

STUDENT NOTES:

Widget Editor
The Widget Editor is used to create operator screens. Operator screens run in a Java applet (the Widget
Applet) which is designed to take over the entire screen (with the web browser in "kiosk" mode, where
the operating system behind it becomes invisible and unavailable).
The operator screens are composed of "Widgets." A Widget is a semi-independent code module that
draws something on the screen and often performs some kind of input or output to or from the tool
controller. For example, a button is a Widget. An indicator light is a Widget. A text label is a Widget. A
panel is a Widget. Sometimes individual Widgets take up the entire screen (for example, the Zone
Management operator screen is a single, large Widget). Sometimes, larger Widgets contain smaller
Widgets.
An individual operator screen is an XML file which describes an arrangement of Widgets. The Widget
Applet reads in the XML file, creates Widgets that the document specifies, and arranges them on the
screen according to the description in the XML file. It also provides a system for those Widgets to
communicate with the tool controller.
The primary job of the Widget Editor is to create those screen XML files. Using the Widget Editor, a screen
designer can put together an arrangement of Widgets (the same ones that the screen applet uses) and
save the screen XML file. The XML file is then transferred to the tool controller flash card and the
navigation system is configured so that the applet can find the screen file when it needs to.
 Document number 96780739 Page 240 of 544
Revision 1

Installation & Setup

Widget Editor is a standalone .jar file which should run if executed in Windows. For each www version
listed on the firmware side of sps.nov.com there should be an accompanying Widget Editor jar file to
download. Where there is no Widget Editor there should be notes identifying which version(s) can be
used instead. Image at left shows example of Widget Editor Download links in sps.nov.com.

Varball
The varball with the pages to be examined should be saved to the PC and extracted. This varball, and the
files within it, should not be zipped up and used on an SBC to prevent any inadvertent changes made in
Widget Editor making their way on to an SBC. If necessary work with a copy of the varball, not the
original.

Determine File to be opened

The file to be opened can be determined by folder structure if familiar with the SBC page structure.
Alternatively determine the path of the page in question in Internet Explorer using either the HMI or
VirtualBox. The browser may show the path in the address bar (www version dependent – later versions
just show /page/navwidget.html) or determine the path using the ‘Configure Operator Pages’ link on the
main SBC page (right click on button which brings up the target screen, select ‘Edit’ and note the link
path)

Screen Structure
The Widget Editor screen is split into three panes.
• The main pane (red) is the graphical representation i.e. what will be seen on the HMI when the
page is called. The page is split into panels which may be static or active e.g. steps during
calibration (only one page is called but different panels are shown as calibration is progressed).
Clicking on a graphical object will jump to the object in the tree pane and show its detail in the
object window.
• The tree pane (yellow) shows the graphical objects structure. The tree reflects the grouping of
graphical objects. Clicking on a graphical object in the tree will shift focus to the object in the
graphical pane and show its detail in the object window.
• The object pane (green) shows the parameters associated with the graphics. This is essentially
where the link between the pages and the SBC objects is defined. Clicking on the various
parameters will allow the linked object to be determined.

Note: Any files associated with offline use of Widget Editor should not make their way on to an SBC i.e.
delete files/varball to prevent inadvertent changes making their way on to a working SBC.
Reference Document 97140431 – Offline Use of Widget Editor
 Document number 96780739 Page 241 of 544
Revision 1

Widget Editor – Viewing Only OFFLINE

STUDENT NOTES:
 Document number 96780739 Page 242 of 544
Revision 1

Screen Communication Logs

STUDENT NOTES:

Screen Communication Logs (accessible through operator pages…[tool name]…Common Diagnostics)

captures limited information under the Operator tab. Exercise caution if using this instead of Widget
Editor to try and establish signal path as functions may operate.

Startup shows profile creation log messages…

 Document number 96780739 Page 243 of 544
Revision 1

Tool Controller

STUDENT NOTES:

A better understanding of SBC code requires the use of Netbeans and is covered in level 2. This section
describes the files found on the controller which specify or aid understanding of the creation, addressing
and linking of I/O to code.

Manuals, Functional Design Specifications, Commissioning Documents and State Diagrams can be found in
Team Centre to further understanding of equipment operation until proficient at interpreting code.
 Document number 96780739 Page 244 of 544
Revision 1

Configuration Files – admin_config.xml

STUDENT NOTES:

admin_config.xml
The admin_config.xml file does two important items, it tells the platform software what class to call so
that tool code is executed and it also specifies the tool screen name. The class name must be the fully
qualified class name. The screen name must match one of the SBC names in the ownership.xml file, if it
does not the controller will fail to start. This name is displayed on the service screens as well as being
used to locate the IP address the SBC should be setup for in the ownership.xml file.

Admin_config.xml can be found within Transfer Files > varco/

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software
 Document number 96780739 Page 245 of 544
Revision 1

Configuration Files – ownership.xml

STUDENT NOTES:

ownership.xml
The ownership.xml file is responsible for several items. Primarily it is used to define ownership rules.
Additionally, this file defines the customer and rig names displayed on the service screen, all SBC names
and IP addresses, the network mask and gateway IP address that is used, all tool names and their host
SBC, the name of the appropriate owner web object, ownership groups and what tools they can control,
tools that cannot be controlled at the same time, process screens and where they can be found and
preconfigured navigation buttons each tool.

ownership.xml can be found within Transfer Files > varco/www

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software
 Document number 96780739 Page 246 of 544
Revision 1

Configuration Files – ip_list.xml

STUDENT NOTES:

ip_list.xml
A descriptive name and the IP address of every item on the Amphion network that is assigned an IP
address is listed in the ip_list.xml document. These items can be put into groups for display purposes.
This document does not assign any addresses, but it is used on the service page to list and link to any
device on the network, as well as displays the device’s IP address if desired.

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software

ip_list.xml
location: /varco/www
First used: Part of www 1.4.0, which was released February 7, 2006
description: XML file.
www versions: www 1.4.0 to present

This file should contain a comprehensive list of every device on the rig network that has an IP address. It is
generated by hand before the rig is delivered.

The ip_list.xml should be the same on every SBC on the rig network. The IP Network Menu applet
contains functionality to alter the ip_list.xml and to transfer the changed version to other SBCs.
 Document number 96780739 Page 247 of 544
Revision 1

This file is used exclusively by the IP Network Menu applet, the little black button that appears on the
service index page in the upper left corner. Clicking on this button pops up a menu that lists categories of
IP devices (Wago devices, HMIs, SBCs, etc.) and submenus of devices in each category. When the applet
starts up for the first time, it reads the ip_list.xml file and attempts to make contact with each of the
items in the list. It gives the operator information about whether that process was successful or not. It can
also allow the operator to navigate to the device.

A typical ip_list.xml looks something like this:

<ip_list> <group type='...'> <item name='...' address='...'/> ... </group> </ip_list> The group type attribute
gives the category name, like "Moxa Switches" or "NOV Tool Controllers." All of the devices of that type
should appear as items in the list within that group.
The item name attribute gives the name of the device, like "Drill Chair Switch 1" or "Auxilliary."
The item address attribute gives the IP address of the device, like "192.168.31.111."
 Document number 96780739 Page 248 of 544
Revision 1

Configuration Files – io_config.xml

STUDENT NOTES:

io_config.xml
The io_config.xml file defines node names, IP addresses and I/O word counts for I/O points
communicated to using Modbus communication. Step7, Cyberbase and a few parameters related to
Profibus communication can be defined here, though primary Profibus setup is in the applicom.zip file.
Masked reads and writes can be performed as well as specifying a communication protocol (TCP or UDP),
watchdog timer and byte order if desire

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software

io_config.xml
Location: /varco/data/config, but also found in /varco/data/persistent
First used: Officially, part of controller release 3.3.0 on December 13, 2005. This was released into the lib
project on January 27, 2006.
Description: XML file
Controller versions: 3.3.0 to present

This file contains configuration information used by I/O points in the controller. All of the information in
the io_config.xml used to be in the admin_config.xml prior to controller 3.3.0.

There is an "old type" Modbus configuration and a "new type" Modbus configuration.
The old type Modbus section of an io_config.xml file will look something like this:
 Document number 96780739 Page 249 of 544
Revision 1

<io> <modbus> <node id='...'> <ip>...</ip> <protocol>...</protocol>

<keep_socket_open>...</keep_socket_open> <read_word_offset>...</read_word_offset>
<read_word_count>...</read_word_count> <write_word_offset>...</write_word_offset>
<write_word_count>...</write_word_count> </node> </modbus> </io>
The node id attribute contains a text name of a Modbus node. It can be a text name, but is often just a
number like "90." This should be the same for a given IP address in all controllers, but has been known to
vary – see examples in slide.
The ip element contains the IP address of the Modbus node, like "192.168.31.95."
The keep_socket_open element can be either "yes," "true," "T," or "1" to indicated that we keep the
socket open and "no," "false," "F," or "0" to indicate that we keep the socket closed.
The read/write_word_offset is the start place to read/write words.
The read/write_word_count is the amount of word to read/write.
The read_word_count should include the total number of input words on the IO rack, including spares.
The write_word_count should include all the outputs being used, including spares.
The new type Modbus configuration looks more like this:
<io> <modbus> <node id='...' tool_name='...'> <ip>...</ip> <protocol>...</protocol>
<keep_socket_open>...</keep_socket_open>
<enabled_during_simulation>...</enabled_during_simulation> <normally_reflect>...</normally_reflect>
<watchdog_ms>...</watchdog_ms> <job> <read_word_offset>...</read_word_offset>
<read_word_count>...</read_word_count> <write_word_offset>...</write_word_offset>
<write_word_count>...</write_word_count> <delayTime>...</delayTime> <mask_write>...</mask_write>
<mask>...</mask> </job> ... <job> ... </job> </node> </modbus> </io> This just moves the read/write
offset/count information into one or more "jobs." There can be any number of job elements and each one
can have its own read/write offset/count elements.
The node tool_name attribute was added in controller 3.8.1 to configure the associated tool name for the
communication loss alarm that's created with this modbus node.
 Document number 96780739 Page 250 of 544
Revision 1

Configuration Files – converters.xml

STUDENT NOTES:

converters.xml
The converters.xml file is used to convert I/O points to web objects (copy their value) and vice versa. It is
generally used to add status or display inputs that are specific to a particular installation. In addition the
converters.xml file is a key component when interfacing with external systems since it is used to 3rd party
I/O in to Amphion I/O and web objects.

converters.xml can be found within Transfer Files > varco/data/persistent

 Document number 96780739 Page 251 of 544
Revision 1

Configuration Files – objects.csv

STUDENT NOTES:

objects.csv
The objects.csv file stores web objects and their value when they have been marked as persistent in code.
This persistent data storage allows saving of states and values in a nonvolatile memory location so that it
can be accessed again on startup. Generally the objects.csv file is written by the controller and indirectly
modified through web objects, however it sometimes modified directly. Direct file modification is
primarily done upon initial creation of software for a particular application.

objects.csv can be found within Transfer Files > varco/data/persistent

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software
 Document number 96780739 Page 252 of 544
Revision 1

Configuration Files – tool_config.xml

STUDENT NOTES:

tool_config.xml
The tool_config.xml file provides configuration information for a particular tool. The format of this file is
somewhat varied from tool type to tool type as options for each type vary. The platform level provides
for some standard functionality when dealing with tools that extend required classes, however this
functionality is not always all that is required to provide a proper configuration. An example of items that
would be listed in a tool_config.xml are how many mud pumps exist, what are their identifiers, what
motors do they use, etc.…

tool_config.xml can be found within Transfer Files > varco/data/config

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software
 Document number 96780739 Page 253 of 544
Revision 1

Configuration Files – applicom.zip

STUDENT NOTES:

applicom.zip
The applicom.zip file is used when configuring Profibus communication. An editing program must be used
to create this file which defines nodes, their number, and what I/O each nodes houses. Creation of this
file cannot be performed on an SBC.

Contents of applicom.zip can be found within Transfer Files > varco/data/applicom

Configuration Files are briefly detailed within D6A1000576-SPC-001, Amphion Software Specification for
Applications Level Software
 Document number 96780739 Page 254 of 544
Revision 1

Tool Controller Software - Netbeans

STUDENT NOTES:

Netbeans can be used to view SBC ‘running code’

Under no circumstances should SBC code be changed by anyone other than the Amphion software group.
NetBeans does not allow the compiling of code that has been changed.
Code should not be shown to the customer. If functionality has to be described or explained then
‘convert’ the code to a written description.
Customers are not prevented from accessing code but this is to be discouraged. Any customer access to
code should be reported to the Amphion group for them to discuss with the customer.

The usual entry method when using NetBeans is searching for the text of an alarm or message, or perhaps
a signal from debug monitor.
Right click on the highest common folder (usually the tool name folder) and select Find. Enter the search
text and click Find. All occurrences of the search text will be shown in the results pane.
Double clicking on the line in the search results will open up the relevant .java file.

Within a .java file it is possible to move between occurrences of a search text, or change the search text
as investigation continues.

Reference Document 95297015 – NetBeans and SBC Code

Reference Document 95066943 - ST Roughneck Auto Sequence Info
 Document number 96780739 Page 255 of 544
Revision 1

Profibus I/O Addressing

 Document number 96780739 Page 256 of 544
Revision 1

I/O Addressing: Profibus

STUDENT NOTES:

Positions on the node are counted from left to right, with the bus coupler itself being position 0; the end
module (position 17 on this example) is not read or written but is necessary for proper functioning of the
bus.
 Document number 96780739 Page 257 of 544
Revision 1

I/O Addressing: Profibus

STUDENT NOTES:

Profibus reads all inputs and writes all outputs from left to right, i.e.: from position 1 to the highest
position; position 1 will always have address 0.
 Document number 96780739 Page 258 of 544
Revision 1

I/O Addressing: Profibus

STUDENT NOTES:

Addressing from left to right: 12DI0.0 – 12DI1.7, 12DQ0.0 – 12DQ1.7, 12AI2 – 12AI16, 12AQ2 – 12AQ16
 Document number 96780739 Page 259 of 544
Revision 1

I/O Addressing: Profibus

STUDENT NOTES:
Document number 96780739 Page 260 of 544
Revision 1

Modbus I/O Addressing

STUDENT NOTES:
 Document number 96780739 Page 261 of 544
Revision 1

I/O Addressing: Modbus

STUDENT NOTES:

While Modbus, like Profibus, reads and writes from left to right, there is one big difference: Modbus first
reads in all Analogue inputs (beginning with the leftmost), then writes all Analogue outputs (beginning
with the leftmost), then reads/writes Digital (Discrete) Inputs/Outputs. No matter what order they may
be laid out physically on the bus.

Modbus Nodes are not numbers but names, though the name may be a number.
 Document number 96780739 Page 262 of 544
Revision 1

I/O Addressing: Modbus

STUDENT NOTES:

Modbus addresses begin with Analogues, even if the first analogue module is not in position 1; so the
addresses for this buss are: 124AI0 – 124AI7, 124AQ0 – 124AQ7, 124DI8.0 – 124DI8.15, 124DQ8.0 –
124DQ8.15

Also, addressing in Words rather than Bytes means that each Digital (Discrete) Address contains 16bits, 0 -
15.
Document number 96780739 Page 263 of 544
Revision 1

I/O Addressing: Modbus

STUDENT NOTES:
Document number 96780739 Page 264 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 265 of 544
Revision 1

Detailed Signal Path

STUDENT NOTES:
 Document number 96780739 Page 266 of 544
Revision 1

Digital Output

STUDENT NOTES:

http://eng.nov.com/TC_V3.swf?dn=11322732-DIA
 Document number 96780739 Page 267 of 544
Revision 1

Digital Output

STUDENT NOTES:

http://eng.nov.com/TC_V3.swf?dn=11322732-DIA
 Document number 96780739 Page 268 of 544
Revision 1

Digital Output

STUDENT NOTES:

http://eng.nov.com/TC_V3.swf?dn=11322732-DIA
 Document number 96780739 Page 269 of 544
Revision 1

Digital Output

STUDENT NOTES:

http://eng.nov.com/TC_V3.swf?dn=11322732-DIA
 Document number 96780739 Page 270 of 544
Revision 1

Digital Output

STUDENT NOTES:

http://eng.nov.com/TC_V3.swf?dn=11322732-DIA
 Document number 96780739 Page 271 of 544
Revision 1

Digital Input

STUDENT NOTES:
 Document number 96780739 Page 272 of 544
Revision 1

Digital Input

STUDENT NOTES:
 Document number 96780739 Page 273 of 544
Revision 1

Digital Input

STUDENT NOTES:
 Document number 96780739 Page 274 of 544
Revision 1

Digital Input

STUDENT NOTES:
 Document number 96780739 Page 275 of 544
Revision 1

Digital Input

STUDENT NOTES:
Document number 96780739 Page 276 of 544
Revision 1

Analog Output

STUDENT NOTES:
Document number 96780739 Page 277 of 544
Revision 1

Analog Output

STUDENT NOTES:
Document number 96780739 Page 278 of 544
Revision 1

Analog Output

STUDENT NOTES:
Document number 96780739 Page 279 of 544
Revision 1

Analog Output

STUDENT NOTES:
Document number 96780739 Page 280 of 544
Revision 1

Analog Output

STUDENT NOTES:
Document number 96780739 Page 281 of 544
Revision 1

Analog Output

STUDENT NOTES:
 Document number 96780739 Page 282 of 544
Revision 1

Analog Input

STUDENT NOTES:
 Document number 96780739 Page 283 of 544
Revision 1

Analog Input

STUDENT NOTES:
 Document number 96780739 Page 284 of 544
Revision 1

Analog Input

STUDENT NOTES:
 Document number 96780739 Page 285 of 544
Revision 1

Analog Input

STUDENT NOTES:
 Document number 96780739 Page 286 of 544
Revision 1

Analog Input

STUDENT NOTES:
 Document number 96780739 Page 287 of 544
Revision 1

Video for Signal Path Detail

STUDENT NOTES:

http://rigflix.nov.com/RigFlix/Video/94916818?q=amphion
 Document number 96780739 Page 288 of 544
Revision 1

Signal Path Detail

STUDENT NOTES:

LHS - Widget Editor shows the Torque Set ‘button’ action when released (press then release),
Centre – Shows the WebObject associated with the Torque Set ‘button’,
RHS – Shows the same WebObject viewed from Debug Monitor
 Document number 96780739 Page 289 of 544
Revision 1

Signal Path Detail

STUDENT NOTES:

Top Left – Shows the ATOS output signal viewed from Debug Monitor,
Top Right- Shows the actual Torque Pressure feedback signal view from Debug Monitor,
Bottom Left – Shows the Torque Setpoint viewed from Debug Monitor,
Bottom Right – Shows the Torque Setpoint viewed from Widget Editor
 Document number 96780739 Page 290 of 544
Revision 1

Signal Path Detail

STUDENT NOTES:

The graph shows the Torque/PSI relationship, from the information on the previous slide… a Torque
Setpoint of 35 Kft*Lbs should equate to around 600 PSI
Document number 96780739 Page 291 of 544
Revision 1

Lesson Review

STUDENT NOTES:
 Document number 96780739 Page 292 of 544
Revision 1

Diagnostics Tools and Software

STUDENT NOTES:
 Document number 96780739 Page 293 of 544
Revision 1

Lesson Objectives
Document number 96780739 Page 294 of 544
Revision 1

Communication Port Number Setting

STUDENT NOTES:
Document number 96780739 Page 295 of 544
Revision 1

Communication Port Number Setting

STUDENT NOTES:

Key:
1. Left Click on Windows Icon in the Task Bar
2. Right click on My Computer
3. Click on Properties
4. Select Device Manager
 Document number 96780739 Page 296 of 544
Revision 1

Communication Port Number Setting

STUDENT NOTES:

In Device Manager go to “ports” and you will see the ports for your laptop.
Usually the serial port is com1 if you have a db9 serial connector on your laptop.
If not and you are using a db9 to USB serial adapter, then it could be any com port.
If it does not appear or has a question mark, it is possible that the driver did not install correctly for the
specific USB to serial adapter.
Port settings, including number, can be adjusted by right clicking, selecting ‘Properties’, Port Settings tab
and then clicking on the Advanced button.
Some software packages require single digit COM numbers to operate.
 Document number 96780739 Page 297 of 544
Revision 1

Ethernet Port Setting

STUDENT NOTES:

Ensure that the IP address chosen for the PC to be connected is not already in use on the network. A
clash of IP addresses could result in unintended machine movement, loss of control and downtime.
Check topology drawing/list or ping from DWS to determine unused address (es).
1. Determine the IP address of the SBC(s) either through documentation or the PuTTY method
(RigDoc 92651817).
2. Select Start…Settings…Network Connections…Local Area Connection or if you have the icon in the
system tray at the right of the taskbar right click on that and select properties. Select the
properties (middle window in the screen capture and scroll down and select TCP/IP and select
properties.
3. Select ‘Use the following IP address’ and type in address as determined in step 1, where the last
number is unique on the network. Subnet mask should fill in automatically.
4. Ok/Accept all changes.

If connecting directly to a non-Beckhoff (white) SBC an Ethernet ‘crossover’ cable is required. Beckhoff
SBCs should have a built in switch which means a straight Ethernet cable can be used. Connecting to
either through an Ethernet switch requires a straight Ethernet cable.

Reference PC IP Address section of RigDoc 80769930 PC Settings for SBC/Amphion Use

Document number 96780739 Page 298 of 544
Revision 1

Brad Communications (Applicom I/O)

STUDENT NOTES:
 Document number 96780739 Page 299 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

Applicom I/O
The SBC uses the applicomIO PC104 DPIO card to communicate with the slave devices. This is in effect the
master on the NOV tool network. The slaves of the system are all components that adhere to the Profibus
DP protocol as passive devices. Each of these devices, in order to be included in a network configuration,
must have a file with the extension .GSD that can be used by a configuration tool or software (in this case
applicomIO Console) that describes the components relevant properties.

The applicomIO Console is the software that will allow you to create, modify, and export Profibus DP
network configurations that are to be used by an applicomIO PC104 DPIO card.

GSD Files
Each slave or master (Class 1) device on Profibus DP must be supplied with a device description file.
The characteristics of each slave device are described in this file, which is the devices GSD (General
Station Description) file. This file contains all the device specific parameters for a specific piece of
equipment:
• Unique device Identity Number.
• The Baud rates that are supported by the device.
• Supported message length.
• Number of bytes of input and output data.
• Meaning of diagnostic messages.
• Options that are available for modular devices.
 Document number 96780739 Page 300 of 544
Revision 1

The Applicom I/O Console

Key:
1. The Menu Bar: This gives access to all commands that can be used at the console. It gives access to
all commands relating to areas 2,4,5,6, and 8. The Menu Bar also gives access Global Commands
via the File menu. The commands required for initializing boards are also under this menu.
2. Configuration Description: Is used to declare the applicomIO boards used, and to navigate
between the various boards that have been declared. Boards can be added and deleted here.
From the example shown it can be seen that there is one board (board 1) installed (there can be
two board, named board 1 and board 2), the board is of type PC104 DPIO, and is in the
configuration named “E122_DRAWWORKS”. By clicking on the ‘Protocol’ node that is resident
under each board, the configuration of the individual board is displayed in the Protocol View area.
3. Resource area: Designates the area containing the Equipment Library and Network Detection tabs.
Resources that can be used in the building of a configuration.
4. Equipment Library tab: This tab allows all the available GSD files to be displayed in a graphical
manner. The desired equipment can be dragged from here and dropped in the Protocol View to
include it in the configuration of a board.
5. Network Detection tab: This tab allows the bus to be scanned to find any new equipment
connected to the bus. This function is only available if the boards are installed on the same
machine as the console. This function is not used by us at NOV as the applicomIO console is not
installed on the same machine in which the applicomIO boards are installed. We essentially use
the console in simulation mode where the configuration and initialization of the boards are carried
out first, and then the appropriate files are downloaded to the applicomIO board at a later date.
6. Message Window area: Displays error or information messages concerning the Equipment Library
and the Initializing of boards.
7. Protocol View area: Is the central configuration element of an applicomIO board. It is used to
configure the network, and to declare and configure the equipment added to that network. The
equipment is dragged and dropped from the Equipment Library. The example shows the board to
be configured on a network as the Master at address 2, and the baud rate of the bus is set to
1500kbits/s. The board is configured to have a network of 21 slaves with ABB Drives at node 5, 6, 7
and 8 followed by 16 x Digital Input and Output modules at address 10 and 12 and so on and so
forth.
8. Status Indicator: This shows the status of the boards. As the boards are not installed on your
machine these will be red. They will turn green after running and initialization and the board
simulator is opened. Once this is closed, the status indicators will return to red.

Reference Document 3FIP00367 – Using the Applicom I/O Console

 Document number 96780739 Page 301 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

Lists of Input or Output items can be viewed for each individual node by opening up the sub-folders using
the + symbol and selecting the ‘Data Block’ type node symbol
1. Shows the Inputs associated with the 16 x Digital Input
2. Shows the Outputs associated with the 16 x Digital Output
3. Right click on ‘Data Block’ and a pop up appears allowing you to view properties (or double click
the ‘Data Block’), this will open a pop up displaying the same information

Reference Applicom I/O help files (accessed via? symbol in toolbar) console help p31/35
 Document number 96780739 Page 302 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

Right click on individual stations and a pop up will appear allowing you to ‘Duplicate’, ‘Delete’ or view
station ‘Properties’

Selecting ‘Properties’ (or double clicking a station) reveals a pop up which lets you view information
related to General Configuration, GSD Information, Parameters and Modules Configuration
 Document number 96780739 Page 303 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

After installation of the program is complete, create a short cut to desk top and open Console IO.
Located on the left side Boards Configuration tab, right click then select configuration Manager.
In version 4.1 the folder location for working configurations is
C:\ProgramData\BradCommunications\applicomIO\4.1\configIO. It may be necessary to enable viewing
of hidden/system files and folders in Windows Explorer to see this path.
 Document number 96780739 Page 304 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

Right click on Board Configuration then Configuration Manager. A new window will open.
Copy the directory path without Config01
 Document number 96780739 Page 305 of 544
Revision 1

Brad Communications – Applicom I/O

STUDENT NOTES:

Locate the configuration path, highlight the path, right click and copy and go the path in the C drive.

Create a new folder and name it with this format (company name, rig name, tool name and varball).
Example: Highlander_Auxiliary _VB4_37
 Document number 96780739 Page 306 of 544
Revision 1

Brad Communications (Applicom I/O)

STUDENT NOTES:

Locate the Varball you want to view and open it in Winzip.

Locate the Applicom.ZIP file.

 Document number 96780739 Page 307 of 544
Revision 1

Brad Communications (Applicom I/O)

STUDENT NOTES:

Open the Applicom.zip file in Winzip.

Select Ctrl+A in the keyboard to select all and drag it to the folder you created for that rig and tool.
Close the folder and go back to your desktop.
 Document number 96780739 Page 308 of 544
Revision 1

Brad Communications (Applicom I/O)

STUDENT NOTES:

Open the Brad Communication (Console IO) and select File…Configuration Manager.
The folder you created previously should be listed – click on it and select Ok. If it is not listed then you
have the folder in the wrong location or have not placed the contents of the Applicom.zip file in the
correct location.

A pop up will appear with a warning that you need to restart the program. Click OK.
Restart Applicom IO Console.
Sometimes if the configuration being opened was created in an older version of Applicom I/O you will get
a warning and confirmation you want to convert. No issues have been observed with viewing
configurations with different versions. Click OK.

The Brad Communication program will open with the selected configuration, review the Profibus
configuration against the interconnect drawing of the tool.
 Document number 96780739 Page 309 of 544
Revision 1

Brad Communications (Applicom I/O)

STUDENT NOTES:

Two adjacent nodes of the same type which use four bits or less may share the same byte (byte-sharing).
The modules using the upper half of the byte are not shown in the Applicom node tree view (middle of
the page) and will only be visible by viewing the properties at the ‘Station’ (node) level and viewing the
Module Configuration tab. These modules are indicated by an asterisk * before the module.
The above manipulated image shows all Wago modules in the node 10 module configuration list (16 IO
modules plus the coupler), whereas in the tree view only 8 modules (positions) are shown.
Power supply and end modules are not shown in the configuration.

See Process Image section of Wago 750-341 Ethernet Coupler manual for a description and examples of
byte sharing as described by the manufacturer (also applies to Profibus process image).
Document number 96780739 Page 310 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 311 of 544
Revision 1

Wago Ethernet Settings

STUDENT NOTES:
 Document number 96780739 Page 312 of 544
Revision 1

Wago Ethernet Setting

STUDENT NOTES:

Use the previous section describing communication ports to check/change if required to establish
communication.

Wago Ethernet Settings is used to assign an IP address to a Wago Ethernet bus coupler. Several methods
are available to carry out this procedure. A Wago Communication (Service) cable (serial or USB) can be
used; the cable plugs into the Configuration Interface port and the other end to the PC running the
Ethernet setup program. An Ethernet cable can also be used, but is only supported by later firmware
versions. A BootP method can be used where no Wago Communication cable is available or the bus
coupler does not support Ethernet.

Software and a user guide for BootP Method is available from RigOffice - 95132020
 Document number 96780739 Page 313 of 544
Revision 1

Wago Ethernet Setting – Wago Service Cable

STUDENT NOTES:

Establish Communication
When the Wago Service cable is attached to a PC, device driver software is installed automatically, if this
does not happen the driver may have to be installed manually via ‘device manager’.
After installing the driver for the Wago Communication cable, the program needs to be configured
correctly.
1. Click on settings.
2. From the connection drop down menu select Serial ports and from the settings drop down menu
select the correct port number.
3. WAGO USB Service Cable option will only be available after correct driver installation.
 Document number 96780739 Page 314 of 544
Revision 1

Wago Ethernet Setting – Wago Service Cable

STUDENT NOTES:

Communication Established
Device information will populate when the connected device has been successfully identified.
Information displayed will include Item Number, Description, Firmware Version (FW), Hardware Version
(HW), Firmware Loader Version (FWL), Serial Number, MAC Address and current IP Address.
 Document number 96780739 Page 315 of 544
Revision 1

Wago Ethernet Setting – Wago Service Cable

STUDENT NOTES:

Modify IP Address
Fill in the desired IP-Address, Subnet Mask, and Gateway in the TCP/IP Configuration window frame.
Select the use the following Address radio button and fill in the correct IP address in the IP-Address Field.
If the Gateway address is not going to be used, leave the default settings.
1. Make sure you click Write to send the new IP address to the bus coupler.
 Document number 96780739 Page 316 of 544
Revision 1

Wago Ethernet Setting – Ethernet Cable

STUDENT NOTES:

Establishing Communication
The IP address needs to be modified via settings/communications to establish communication at a new IP
Address using Ethernet.
No communication with the device will be possible until the correct IP Address is entered.
Ensure connected PC laptop Ethernet address is set to an address in the same range to allow
communication. 192.168.31.9 through 16 are unused in typical Amphion networks and intended for
laptop use.
 Document number 96780739 Page 317 of 544
Revision 1

Wago Ethernet Setting – Ethernet Cable

STUDENT NOTES:

Establishing Communication
Navigate to Settings > Communications, select Ethernet (TCP/IP) from the Connection drop down menu.
Select the IP-Address radio button from the Settings menu and type the IP Address of device (if known).
Press Apply, you may have to press ‘Read’ several times to establish communications.

Or from the Communication Settings menu select the Search device button, in the pop up input an IP
address range (last octet).
If the show all devices radio button is checked all devices in the connected network will appear, in this
example my laptop is directly connected to the bus coupler (192.168.31.13 is my laptop).
Highlight/select the bus coupler within the Device List and press Apply, then press Apply on the previous
pop up.
 Document number 96780739 Page 318 of 544
Revision 1

Wago Ethernet Setting – Ethernet Cable

STUDENT NOTES:

Modify IP Address
To Modify the IP address we use the same method detailed previously for the Wago Service Cable
method.
Note the warning; this indicates that you will no longer be able to communicate with the device at the
original IP address!
To re-establish communications you need to enter the new IP address via Settings > Communications or
use the Webserver.
 Document number 96780739 Page 319 of 544
Revision 1

Wago Bus Coupler Webserver

STUDENT NOTES:

Webserver
Once you have assigned an IP address to the Modbus Wago bus coupler, you can access Wago
configuration using a web browser. Type the IP address in the address bar of Internet Explorer.
Various pages are available via the Navigation menu
Status Information - Coupler Details, Ethernet Details, IP Details and Module Status
Ethernet - This page is for the configuration of the Ethernet. The configuration is stored in an EEPROM.
Changes will take effect after the next software or hardware reset
TCP/IP - This page is for the configuration of the basic TCP/IP network parameters. The parameters are
stored in an EEPROM and changes will take effect after the next software or hardware reset.
Port - This page is for the configuration of the network protocols. The configuration is stored in an
EEPROM and changes will take effect after the next software or hardware reset.
SNMP - This page is dedicated to the SNMP configuration. The new configuration is stored in an EEPROM
and changes will take effect after the next software or hardware reset.
SNMP V3 - This page is dedicated to the SNMP configuration. The new configuration is stored in an
EEPROM and changes will take effect after the next software or hardware reset. 'Authentication Key' and
'Privacy Key' have to be at least 8 characters.
Watchdog - This page is for the configuration of the watchdogs. The configuration is stored in an
EEPROM. Changes of the Connection Time will take effect immediately. Changes of the Modbus
Watchdog will take effect after the next software or hardware reset. For more information see the
manual.
Clock -
 Document number 96780739 Page 320 of 544
Revision 1

Security - This page is intended to disable the basic authentication. Additionally you can set new
passwords for the existing user. The new values are stored in an EEPROM and changes will take effect
after the next software or hardware reset
Features - This page is for the configuration of additional features. The configuration is stored in an
EEPROM and changes will take effect after the next software or hardware reset.
IO Config - View the configuration of your fieldbus node.
Disk Info - This page is for informational purposes of the Flash filesystem.
 Document number 96780739 Page 321 of 544
Revision 1

Wago Port Setting

STUDENT NOTES:

Port Settings
Once the Wago bus coupler web page loads select ports. A log in pop up window will appear, log in by
using (admin) as a username and (wago) as a password (both lowercase). Make sure BootP is unchecked,
DHCP is unchecked and use IP from EEPROM checked, then select the SUBMIT button.

Web pages shown may vary depending on firmware and hardware versions.
 Document number 96780739 Page 322 of 544
Revision 1

Wago Ethernet Setting

STUDENT NOTES:

Status
1. Click on Status to view the Error and fault codes.
2. The blink code can be referenced back to the bus coupler User Manual.
 Document number 96780739 Page 323 of 544
Revision 1

Wago Ethernet Setting

STUDENT NOTES:

Date / Time
1. Set the date and time. This is optional.
2. Click Apply to apply the Computer setting to the Wago bus coupler.
 Document number 96780739 Page 324 of 544
Revision 1

Wago BootP Method

STUDENT NOTES:

An alternative to Ethernet Settings is the Wago BootP program. Details of how to use this can be found in
rdo:documentprop=80837013
Document number 96780739 Page 325 of 544
Revision 1

Wago I/O Check

STUDENT NOTES:
 Document number 96780739 Page 326 of 544
Revision 1

Wago IO Check V3

STUDENT NOTES:

Use the previous section describing communication ports to check/change if required to establish
communication.

Wago I/O Check is used to check the operation of I/O independent of the SBC. This can be useful just after
power is applied for the first time, or during troubleshooting. Inputs can be monitored and outputs can be
forced. Always exercise caution when forcing outputs! Wago I/O Check reads the configuration of a
connected node from the coupler and displays the node on the screen of your PC. The graphical
representation of the node can be printed out together with a configuration list. Wago I/O Check allows
the display and default entry of process data of individual I/O modules.

Standard Toolbar

Key
1. Exit
Terminates Wago I/O Check.
2. Open
Opens an existing node description. Use the Open file dialogue box to select a file name. The
corresponding pulldown menu shows the four last processed node descriptions.
3. Save
Saves the active node description. If you save a node the first time the Save As dialogue box will
prompt you for a filename. #
Document number 96780739 Page 327 of 544
Revision 1

4. Identify
Read the configuration of the connected node.
5. Control-Mode
Toggles the selected control-mode ON or OFF. Select the desired control-mode from the
corresponding pulldown menu.
6. Monitor-Mode
Toggles the monitor-mode ON or OFF.
7. Settings
Changes the parameters of the selected module. This command is only available if the parameters
of the selected module are changeable.
8. Process Data
Shows the process data of the selected module. This command is only available if a node
configuration has been read or a node description has been opened.
9. Zoom Down
Reduces the node display.
10. Zoom Up
Enlarges the node display.
11. Help
Opens the online-help for Wago I/O Check
12. Navigation Bar
The navigation bar displays the node in a tree structure with the coupler or controller, the
connected I/O modules and the corresponding channels.
Single branches of this structure can be displayed by clicking the symbol with the left mouse key.
Click the symbol with the left mouse key to hide a branch.
13. Node Display
The node display shows an image of the connected or loaded node. The LED display of the shown
modules corresponds to the LED status of the connected node.
14. Output Area
The output area displays the executed actions and occurred errors in chronological order.
The output lines are built up as follows: Date, Time - Description of actions or errors.
15. Status bar
The status bar is placed at the bottom of the Wago I/O Check window. It displays information on
commands, connection parameters and status and the operation mode.
As you move through the menu with the arrow keys the left area of the status bar describes the
function of the menu entries. In the same manner this area also describes the effect of the toolbar
buttons if these are clicked and held down. Release the mouse button when the cursor is no
longer on the toolbar button if you do not want to execute the command associated by the
toolbar button. A progress bar and a describing text appears displaying the progress of various
actions.
In the middle area of the status bar the parameters of the serial interface and the operation mode
of Wago I/O Check are displayed.
16. Display Description
The right area of the status bar shows the status of the connection to the coupler; Offline – The
connection to the coupler is not active, Online – Wago I/O Check is polling the process data out of
the connected node
 Document number 96780739 Page 328 of 544
Revision 1

17. LED Description

If all LED´s are switched off (gray), the node configuration has not been read and data is not being
exchanged between Wago I/O Check and the coupler.
The green LED (left side) is lit if the node configuration was successfully read.
The yellow LED (in the middle) is lit if Wago I/O Check is polling the process data out of the
connected node.
The red LED (right side) is lit either if the node was not successfully read or any other errors
occurred.

Control-Mode
Control Modes serve to display the input and output data of the connected node. Output data can be set
when the fieldbus is deactivated. For controllers the PLC functionalities also have to be deactivated.
By activating one Control Mode, the remaining Control Modes and the Monitor Mode are deactivated.
• Direct
Toggles the Control-Mode Direct ON or OFF. The activated status is immediately available at the
modules.
• Collect
Toggles the Control-Mode Collect ON or OFF. The activated states of the outputs are stored and
sent to the modules all at once on pressing a key.
• Force
Toggles the Control-Mode Force ON or OFF. The activated output states are available at the
modules only for the time of pressing a key.
• Permanent
Toggles the Control-Mode Permanent ON or OFF. The activated output states are immediately
available at the modules and remain active even after an interruption of the fieldbus connection
to the node.

Control mode can only be used while the Wago node is disconnected from the control network.

Monitor-Mode
Use this command to toggle the Monitor-Mode ON or OFF.
The Monitor-Mode exclusively displays input or output data of the connected node. Outputs cannot be
activated.

Monitor mode can be used while the Wago node is connected to the control network (Ethernet or
Profibus)

Open Wago IO Check program, Port number setting should be the only change required. Ethernet
communications is also supported.
Document number 96780739 Page 329 of 544
Revision 1

Communication Setting

STUDENT NOTES:

1. Click on ‘Settings’ then Select ‘Communication’

2. From the Connection drop down menu select ‘Serial Ports (COM, USB, Bluetooth…)
3. From the Settings drop down menu select ‘COMxx: WAGO USB Service Cable
4. Select ‘Ok’
 Document number 96780739 Page 330 of 544
Revision 1

Control Mode - Direct

STUDENT NOTES:

Note that the module LEDs in the software indicate selection, not necessarily the state of the outputs.
Always check physical output LEDs to ensure the desired state is being achieved.

Use this command to toggle the Control Mode Direct ON or OFF.

Digital outputs can be activated by clicking on the display field in the process data dialog box or on the
LED in the node display or by hitting the <space bar>. Clicking or hitting the <space bar> another time
deactivates the output.
Analog output values are set in the process data dialog box by moving the slides or by inputting a value
into the display field and hitting the <Enter> key.
Values for specialty modules are set in the process data dialog by inputting them into the display field and
hitting the <Enter> key.

To be able to force I/O in control mode you need to disconnect the master (Profibus or Ethernet cable).
 Document number 96780739 Page 331 of 544
Revision 1

Control Mode - Collect

STUDENT NOTES:

Note that the module LEDs in the software indicate selection, not necessarily the state of the outputs.
Always check physical output LEDs to ensure the desired state is being achieved.

Use this command to toggle the Control Mode Collect ON or OFF.

As long as this Mode is activated, an additional window called ‘Output Data’ with a SEND button is
opened
For selection of the digital outputs see Control Mode Direct.
However, the selected output states are not sent directly but are latched and send all together to the
coupler or controller after clicking on the button SEND.
This makes it possible to simulate the performance of a PLC when writing several outputs.

To be able to force I/O in control mode you need to disconnect the master (Profibus or Ethernet cable).
 Document number 96780739 Page 332 of 544
Revision 1

Control Mode - Force

STUDENT NOTES:

Note that the module LEDs in the software indicate selection, not necessarily the state of the outputs.
Always check physical output LEDs to ensure the desired state is being achieved.

Use this command to toggle the Control Mode Force ON or OFF.

A digital output is activated as long as the left mouse button or the space bar is pushed.

To be able to force I/O in control mode you need to disconnect the master (Profibus or Ethernet cable).
 Document number 96780739 Page 333 of 544
Revision 1

Control Mode - Permanent

STUDENT NOTES:

Note that the module LEDs in the software indicate selection, not necessarily the state of the outputs.
Always check physical output LEDs to ensure the desired state is being achieved.

Use this command to toggle the Control Mode Permanent ON or OFF.

This command is only enabled if this mode is supported by the coupler or controller used.
For activation and deactivation of the digital outputs see Control Mode Direct.
However, Control Mode Permanent and the activated outputs will not be deactivated automatically when
Wago I/O Check is quit.
The deactivation of the Control Mode Permanent, hence the deactivation of the outputs is possible at any
time through a coupler/controller reset. The controller also allows a deactivation by starting the PLC
application. When using Profibus, Interbus and Ethernet, the Control Mode Permanent will also be
deactivated when the master is booted up.
When Wago I/O Check is quit, the user is warned that activated outputs in this mode will still be
activated, even after terminating the connection to the node.

To be able to force I/O in control mode you need to disconnect the master (Profibus or Ethernet cable).
 Document number 96780739 Page 334 of 544
Revision 1

Control Mode - Error

STUDENT NOTES:

Selecting any Control-Mode with the master still connected will result in an error as shown.

To be able to force I/O in control mode you need to disconnect the master (Profibus or Ethernet cable).
 Document number 96780739 Page 335 of 544
Revision 1

Monitor Mode

STUDENT NOTES:

Use this command to toggle the Monitor-Mode ON or OFF.

The Monitor-Mode exclusively displays input or output data of the connected node. Outputs cannot be
activated.
Activation of the Monitor-Mode entails deactivation of the Control-Modes.
Monitor-Mode can be activated while the master is connected.
If the Monitor-Mode is activated, the symbol next to the menu item is framed and the symbol in the tool
bar is displayed in color.
When you exit Wago I/O Check, the Monitor-Mode will be deactivated, if still active. You will be asked to
confirm the interruption of the connection.
Document number 96780739 Page 336 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 337 of 544
Revision 1

EDS Configurator

STUDENT NOTES:

Download Moxa software from the web or

http://rigdoc.nov.com/Get.aspx?docid=95126076&LastReleasedFiles=1
 Document number 96780739 Page 338 of 544
Revision 1

edscfgui.exe

STUDENT NOTES:

EDS Configurator is a comprehensive Windows-based GUI that is used to configure and maintain multiple
Moxa switches. A suite of useful utilities is available to help you locate Moxa switches attached to the
same LAN as the PC host (regardless of whether or not you know the IP addresses of the switches),
connect to a Moxa switch whose IP address is known, modify the network configurations of one or
multiple Moxa switches, and update the firmware of one or more Moxa switch.

1. Broadcast Search
Use the Broadcast Search utility to search the LAN for all Moxa switches that are connected to the
LAN. Note that since the search is done by MAC address. Broadcast Search will not be able to
locate Moxa EtherDevice switches connected outside the PC host’s LAN.
2. Search by IP Address
Use the Search by IP Address utility to search for Moxa switches one at a time. Note that the
search is conducted by IP address, so you should be able to locate any Moxa switch that is
properly connected to your LAN, WAN, or the Internet.
3. Upgrade Firmware
Keep your Moxa switch up to date with the latest firmware from Moxa. Firmware should not be
updated on NOV systems without prior engineering approval.
4. Modify IP Address
You may use the Modify IP Address function to reconfigure the Moxa switch’s network settings.
5. Import Configuration
The Import Configuration function is used to import an entire configuration from a text file to the
Moxa switch. The utility can be used to transfer the configuration from one Moxa switch to
 Document number 96780739 Page 339 of 544
Revision 1

another, by first using the Export Configuration function (described in the previous section) to save
a switch configuration to a file, and then using the Import Configuration function.
6. Export Configuration
The Export Configuration utility is used to save the entire configuration of a particular Moxa switch
to a text file.

Note – it is possible to lock Moxa switches to prevent configuration changes. NOV do not lock switches.
It is possible to unlock a locked Moxa switch using EDS Configurator, but only if the password is known.
If the password is not known an exported configuration is required to determine the password; once
the switch is accessed the password should be removed if the customer consents.

Reference Document – Moxa_Managed_Switches_UM_v9.pdf available via Moxa Website

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)
 Document number 96780739 Page 340 of 544
Revision 1

Broadcast Search

STUDENT NOTES:

Use the Broadcast Search utility to search the LAN for all Moxa switches that are connected to the LAN.
Note that since the search is done by MAC address, Broadcast Search will not be able to locate Moxa
EtherDevice switches connected outside the PC host’s LAN.
1. Start by clicking the Broadcast Search icon, or select Broadcast Search under the List Server menu.
2. The Broadcast Search window will open and display a list of all switches located on the network.
Look in the Progress column to see the progress of the search. Once the search is complete, the
Configurator window will display a list of all switches that were located.

It may be necessary to disable all network adaptors other than local area connection for search to work
correctly/quickly. This application may need to let through the firewall and to be run as an administrator.

The result is shown in a pop up, press Stop when the switch you are looking for appears or just wait for
the search to complete and time out.

192.168.127.253 is the default IP address for new Moxa switches. If a new Moxa cannot be found it may
be necessary to set the PC local area connection address to one in the same range as the default Moxa IP.

If you install two new Moxa switches at the same time, edscfgui.exe can tell them apart because they
have different MAC addresses – but you cannot. Only attach one new Moxa switch to the network at a
time or connect directly to each Moxa switch before connecting it to the network.
 Document number 96780739 Page 341 of 544
Revision 1

Reference Document – Moxa_Managed_Switches_UM_v9.pdf available via Moxa Website

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 342 of 544
Revision 1

Modify IP Address

STUDENT NOTES:

After Broadcast Search completion, the search result will appear in the program windows in the left side
and details for the switch highlighted in the right side.
1. Highlight the new switch and select the Modify IP Address icon, select Configuration, Modify IP
Address or alternatively right click on the highlighted device and select Modify Configuration from
the menu.
2. Check IP Address, enter the desired IP address and netmask and press OK
3. A warning will be displayed regarding updating of a Moxa switch settings. Press Yes if you are
happy with the settings otherwise No and review.
4. When a pop up appears reading Modify IP OK, press Close. You have now successfully set the IP
address and can access the switch’s web page to complete setup.

Reference Document – Moxa_Managed_Switches_UM_v9.pdf available via Moxa Website

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 343 of 544
Revision 1

Upgrade Firmware

STUDENT NOTES:

Firmware should not be updated on NOV systems without prior engineering approval.
1. Download the updated firmware (*.rom) file from Moxa’s website (www.moxa.com)
2. Highlight the switch (from the left hand side of the device identification window) whose firmware
you wish to upgrade.
3. Select the Upgrade Firmware toolbar icon, or select Upgrade under the Firmware menu.
4. Use the Open window to navigate to the folder that contains the firmware upgrade file, and then
click the correct “*.rom” file (eds.rom in the example shown below) to select the file. Click Open to
activate the upgrade process. Upgrade progress will be detailed within the pop up.
5. Selecting yes on the pop up can potentially change the display order of the switches in the left
hand column.

Upgrading of firmware may be necessary if you are introducing a newer type Moxa switch into a network
of older type switches. ed6008-V2.9.rom is required to allow now obsolete ED6008-MM-SC to be
compatible within a network containing the newer EDS-408A-MM-ST

It is necessary to upgrade the firmware individually for each switch in the network

Reference Documents – D801003610-PRO-001, EDS – ED6008 Moxa Switches Integration Procedure.

Moxa_Managed_Switches_UM_v9.pdf available via Moxa Website
(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)
 Document number 96780739 Page 344 of 544
Revision 1

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 345 of 544
Revision 1

Export/Import Configuration

STUDENT NOTES:

Export
1. Highlight the switch (from the Server list in the Configurator window’s left pane), and then click
the Export toolbar icon or select Export Configuration from the Configuration menu. Use the Open
window to navigate to the folder in which you would like to store the configuration, and then type
the name of the file in the File name input box. Click Open to continue.
2. Click OK when the Export configuration to file OK message appears.
3. You may use a standard text editor, such as Notepad under Windows, to view and modify the
newly created configuration file.

Import
1. Highlight the server (from the Moxa EtherDevice Switch list in the Configurator window’s left
pane), and then click the Import toolbar icon, or select Import Configuration from the
Configuration menu.
2. Use the Open window to navigate to the text file that contains the desired configuration. Once the
file is selected, click Open to initiate the import procedure.
3. The Setup Configuration window will be displayed, with a special note attached at the bottom.
Parameters that have been changed will be indicated with a checkmark. You may make more
changes if necessary, and then click OK to accept the changes.
4. Click Yes in response to the following warning message to accept the new settings.

It is possible to export the configuration from the switch once setup is complete and save it as a backup or
send to technical support in a troubleshooting scenario. Select the switch and then Configuration…Export
 Document number 96780739 Page 346 of 544
Revision 1

Configuration. A suitable filename should be entered in the format CUSTOMER_RIG_IPADDRESS_DATE

e.g. Ensco_121_19216831101_24Aug2016. ini.
Reference Document – Moxa_Managed_Switches_UM_v9.pdf available via Moxa Website
(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 347 of 544
Revision 1

Discovering the Rig IP Domain

STUDENT NOTES:

Since edscfgui.exe is not dependent on the IP settings of your computer, it can be used to discover the IP
domain of the rig if unknown. In the example shown a Broadcast Search has found twenty four Moxa
switches all with domain address 192.168.31.XXX.
 Document number 96780739 Page 348 of 544
Revision 1

Moxa Configuration and Ring Diagnostic

STUDENT NOTES:
 Document number 96780739 Page 349 of 544
Revision 1

The Moxa Switch Web Page

STUDENT NOTES:

Configuration by Web Browser

The Moxa switch’s web console is a convenient platform for modifying the configuration and accessing
the built-in monitoring and network administration functions. You can open the Moxa switch’s web
console using a standard web browser, such as Internet Explorer.

The home page provides information about the Moxa switch along with links in the left column to the
various settings.

Connect your web browser to the Moxa switch’s IP address by entering it in the Address or URL field. It
can also be accessed from an SBC IP Network menu.

1. The Moxa switch’s web console will open, and you will be prompted to log in. Select admin and
leave the password blank.
2. Click on login and the configuration screen will be shown. If access is denied a password has been
set. It is possible to lock Moxa switches to prevent configuration changes. NOV do not lock
switches. It is possible to unlock a locked Moxa switch using EDS Configurator, but only if the
password is known. If the password is not known an exported configuration is required to
determine the password; once the switch is accessed the password should be removed if the
customer consents.

*Make sure that the LAN address of your laptop is in the same range as the Moxa Switch you are trying to
communicate with
 Document number 96780739 Page 350 of 544
Revision 1

Reference Document – Moxa_Managed_Switches_UM_v9.pdf

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 351 of 544
Revision 1

Moxa Settings – Disable DIP Switches

STUDENT NOTES:

Turbo Ring DIP Switch

The Turbo Ring DIP Switch page allows users to disable the 4th DIP switch located on the EDS’s outer
casing. The default is enabled with Turbo Ring v2 protocol. Once the user changes the 4th hardware DIP
switch configuration to ON, the switch will start to initiate the Turbo Ring redundancy protocol based on
the configuration. The detailed description is given below:

Setting Description Factory Default

Disable the Turbo Unchecked: The Turbo Ring protocol will be activated
Ring DIP switch automatically when the 4th DIP switch is moved to the
ON position. unchecked
Checked: The Turbo Ring protocol will not be
activated automatically, regardless of the position
of the 4th DIP switch.
Set DIP switch as If the DIP switch is enabled, Turbo Ring protocol
Turbo Ring will be enabled when the DIP switch is moved to
the ON position. Set DIP switch as
Turbo Ring v2
Set DIP switch as If the DIP switch is enabled, Turbo Ring v2
Turbo Ring v2 protocol will be enabled when the DIP switch is
moved to the ON position.
 Document number 96780739 Page 352 of 544
Revision 1

NOTE: If the 4th DIP switch (Turbo Ring) is configured to ON, you will not be able to disable the Turbo Ring
DIP switch from the web interface
1. Expand the + sign within Basic Settings to find the Turbo Ring DIP Switch settings tab.
2. Click Turbo Ring DIP Switch.
3. By default, the Turbo Ring Dip Switches are enabled. Check Disable the Turbo Ring DIP Switch then
select Activate.

*DIP Switches are not available on the now obsolete ED6008-MM-SC Moxa switches

Reference Document – Moxa_Managed_Switches_UM_v9.pdf

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 353 of 544
Revision 1

Moxa Settings - Communication Redundancy

STUDENT NOTES:

Configuring “Turbo Ring” and “Turbo Ring V2”

Use the Communication Redundancy page to select Turbo Ring, Turbo Ring V2, or Turbo Chain. Note that
configuration pages for these three protocols are different.

Redundancy Protocol
Setting Description Factory
Default Turbo Ring Select this item to change to the Turbo Ring None
configuration page.
Turbo Ring V2 Select this item to change to the Turbo Ring
V2 configuration page.
Turbo Ring V2 with
DRC (Dynamic Ring Coupling) Select this item to change to the Turbo Ring V2
with DRC configuration page.
Turbo Chain Select this item to change to the Turbo Chain
configuration page.
RSTP (IEEE 802.1W/ 802. Select this item to change to the RSTP
1D-2004) configuration page.
None Ring redundancy is not active

The default redundancy protocol is RSTP (IEEE 802.1W/D); from the drop-down menu select Turbo Ring or
Turbo Ring V2
 Document number 96780739 Page 354 of 544
Revision 1

1. Select Communication Redundancy

2. Select Turbo Ring or Turbo Ring V2 from dropdown menu
3. Select Activate

Note: Do NOT select Turbo Ring V2 unless every switch on the rig is an EDS-408A-MM-ST and you intend
to set them all to Turbo Ring V2. Turbo Ring V2 has a shorter recovery time than Turbo Ring but it is not
compatible with Turbo Ring or with older ED6008 switches. ED6008 networks are not normally configured
for Turbo Ring but can support it if enabled.

Reference Document – Communication_Redundancy_Users_Manual_v5.pdf

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 355 of 544
Revision 1

Moxa Settings - Auto Warning

STUDENT NOTES:

Using Auto Warning

Since industrial Ethernet devices are often located at the endpoints of a system, these devices will not
always know what is happening elsewhere on the network. This means that an industrial Ethernet switch
that connects to these devices must provide system maintainers with real-time alarm messages. Even
when control engineers are out of the control room for an extended period of time, they can still be
informed of the status of devices almost instantaneously when exceptions occur. The Moxa switch
supports different approaches to warn engineers automatically, such as email and relay output. It also
supports two digital Inputs to integrate sensors into your system to automate alarms by email and relay
output.

Configuring Relay Warning

The Auto Relay Warning function uses relay output to alert the user when certain user-configured events
take place. There are two basic steps required to set up the Relay Warning function:

Configure Relay Event Types

Select the desired Event types from the Console or Web Browser Event type page (a description of each
event type is given later in the Relay Alarm Events setting subsection).

Activate your settings

After completing the configuration procedure, you will need to activate your Moxa switch’s Relay Event
Types.
 Document number 96780739 Page 356 of 544
Revision 1

Configuring Event Types

Event Types can be divided into two basic groups: System Events and Port Events. System Events are
related to the overall function of the switch, whereas Port Events are related to the activity of a specific
port.
The Moxa switch supports two relay outputs. You can configure which relay output is related to which
events, which helps administrators identify the importance of the different events.

System Events Warning Relay output is triggered when…

Power Transition (On -> Off) Moxa switch is powered down
Power Transition (Off -> On) Moxa switch is powered up
DI1/DI2 (On -> Off) Digital Input 1/2 is triggered by on to off transition
DI1/DI2 (Off -> On) Digital Input 1/2 is triggered by off to on transition
Turbo Ring Break The Turbo Ring is broken. Only the MASTER switch of Turbo Ring will output
warning relay.

Port Events Warning Relay output is triggered when…

Link-ON The port is connected to another device.
Link-OFF The port is disconnected (e.g., the cable is pulled out, or the opposing device
shuts down).
Traffic-Overload The port’s traffic surpasses the Traffic-Threshold for that port (provided this
item is enabled).
Traffic-Threshold (%) Enter a nonzero number if the port’s Traffic-Overload item is enabled.
Traffic-Duration (sec.) A Traffic-Overload warning is sent every Traffic-Duration seconds if the
average Traffic-Threshold is surpassed during that time period.

1. Open Auto Warning, Relay Warning and Event Setup (+ sign).

2. Set Power Input 1 and Power Input 2 failure (On -> Off) to enable.
3. Set Turbo Ring Break (Ring Master Only) to disable.
4. Set Port 7 and 8 link to Off and traffic overload to enable.
5. Select Activate

Reference Document – Moxa_Managed_Switches_UM_v9.pdf

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 357 of 544
Revision 1

Moxa Settings - Factory Default

STUDENT NOTES:

All other settings not covered here should be kept at their factory defaults. If the switch is old (i.e.: not
shrink-wrapped inside box or ip address not 192.168.127.253), it should be set to its factory defaults
before beginning setup.

If you get lost, make a mistake or fear you have made a mistake, you can restore all settings to their
factory default values and start over.

Note: this includes the IP address, so you will lose your connection and have to start over with
edscfgui.exe

To restore factory default settings

1. Open Advanced Settings and select Factory Default
2. Select Activate

*go back to the beginning and start over… assign IP Address then configure via web browser

Reference Document – Moxa_Managed_Switches_UM_v9.pdf

(http://www.moxa.com/support/sarch_result.aspx?type=doc&prod_id=576&type_id=7)

Configuration using EDS CFG and the Moxa web page interface (described later) should be done with
the Moxa switch disconnected from the Amphion network. A new/updated/reconfigured Moxa should
only be introduced to the network after all configurations is done.
 Document number 96780739 Page 358 of 544
Revision 1

Moxa Ring Diagnosis V2.3

STUDENT NOTES:

Ring Diagnosis
The Ethernet Redundant Ring Diagnosis program can be used to diagnose connections of EDS series fast
redundant Ethernet ring, called a Moxa Turbo Ring, and collect its information.
Diagnosis by the Ethernet Redundant Ring Diagnosis program can help you check the network topology of
the Turbo Ring and the Turbo Ring information of the EDS series. It can detect connection failures or data
loss in the backbone of the Turbo Ring topology. It displays the topology of the Turbo Ring on the
Diagnosis page. Apart from a detailed result report, the program also provides further information of each
switch on the Diagnosis Report page.
The program is currently limited to display a maximum 50 switches on the Diagnosis page. You can find all
the switches information on the Diagnosis Report page.

WinPcap.exe
WinPcap is the industry-standard tool for link-layer network access in Windows environments: It allows
applications to capture and transmit network packets bypassing the protocol stack, and has additional
useful features, including kernel-level packet filtering, a network statistics engine and support for remote
packet capture.
Please make sure that you have installed WinPcap 4.1.3 or above.
 Document number 96780739 Page 359 of 544
Revision 1

1. Select the appropriate PC Ethernet Card from the drop-down menu (if you have only one, select it;
if you have more than one select the one with 192.168.31.xx address).
2. Select manual or auto update. Auto will refresh the information at the specified rate. If a single
scan to retrieve information and allow it to be studied is all that is required then set to manual.
3. Click on Diagnosis.

Reference Document – In program manual available via ‘Help’ tab

 Document number 96780739 Page 360 of 544
Revision 1

Moxa – Monitoring Network Status

STUDENT NOTES:

A graphic display of your network similar to the one above (but with more/less switches) will be shown.
1. A healthy network should look similar to the above. The number of Moxa switches shown should
reflect the actual physical number.
2. The Host is the Moxa switch the PC is connected to.
3. A ring Master switch should be identified.
4. The orange line represents the position of the break in the ring (controlled by the master) to
prevent looping (Broadcast Storms). The port number blocked is shown. The orange line will
always be shown in the position in the above screen capture. If the position of the break changes
then the switches and IP addresses will move accordingly.
5. The green lines indicate good communication between Moxa switches.
6. Older versions of Ring Diagnostics were designed to run on Windows XP and would contain errors
(packet loss and exclamation marks) on the report when ran on a Windows 7 operating system
even though the network is healthy. The new Ring Diagnostic V2.3 is fully compatible with
Windows and errors should only appear if there is a genuine fault.
 Document number 96780739 Page 361 of 544
Revision 1

Diagnosis Symbols
Red exclamation mark: The port possibly causes packet loss
Orange exclamation mark: The port is suspected to cable error
Master: The switch is the master of the ring
Host: The PC with the running Ring Diagnosis program is plugged into this switch

Reference Document – In program manual available via ‘Help’ tab

 Document number 96780739 Page 362 of 544
Revision 1

Moxa – Testing Ring Redundancy

STUDENT NOTES:

Testing ring redundancy should only be carried out on a network where no tools are in use. Coordinate
with customer to ensure minimal disruption.

A network with one fault (single or double fiber between two adjacent switches) should look similar to
the above. The number of Moxa shown should reflect the actual physical number.
1. The host is the Moxa the PC is connected to.
2. A master switch should be identified.
3. The red line represents the position of the break in the ring. The red line will always be shown in
the position in the above screen capture. If the position of the break changes then the switches
and IP addresses will move accordingly.
4. The green lines indicate good communication between Moxas.
 Document number 96780739 Page 363 of 544
Revision 1

Moxa – Ring Break

STUDENT NOTES:

Testing ring redundancy should only be carried out on a network where no tools are in use. Coordinate
with customer to ensure minimal disruption.

The above screenshot shows a network with two separate points of failure. No ring is shown. The number
of Moxa shown may vary depending on the location of the two points of failure.
Document number 96780739 Page 364 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 365 of 544
Revision 1

Profibus Master Simulator

 Document number 96780739 Page 366 of 544
Revision 1

Profibus DP Master Simulator

STUDENT NOTES:

NOV use Profibus networks on many of their control systems. Profibus is a 2 wire RS-485 based
communication system for automation networks. Components on the network (nodes) can include
remote I/O modules, inverters, encoders, HMIs, linear transducers and proportional solenoid drivers.
Each network has a master, typically a PLC or SBC (single board computer) that manages and controls the
network. DP Master Simulator is used in place of the PLC/SBC for setup and trouble shooting.

DP Master Simulator can be used online for independent verification of Profibus node status if there is
some doubt about the Applicom configuration and/or SBC Profibus diagnostics page., the program can
also be used to assign node addresses to Profibus programmable slave devices off the main network i.e.
spares before fitting.

Open the application and you will see the PROFIBUS Master Simulator (Searching) screen.

Reference Document - RigOffice 94652886

 Document number 96780739 Page 367 of 544
Revision 1

Online Connection

STUDENT NOTES:

Use the previous section describing communication ports to check/change if required to establish
communication.

Ensure the network is connected and powered up.

Ensure the drillfloor/tool is in a safe state/position to remove control.
Disconnect the PLC or SBC from the network (i.e. usual master is removed)
Connect the UART to the laptop and the communications cable between the UART and a ‘piggy back’
connector on a device such as an ET-200 or Siemens repeater. It may be necessary to temporarily replace
the existing connector with a piggy back type. The piggy back connection is required to power the UART
(NOV part number M871001492-ASM-001 is available which uses PC USB power for the UART and
provides more options when it comes to connecting to the network).
Open the DP Master Simulator software on the laptop.
1. Select the Communication tab then ‘Settings’
2. Select the Com Port that you want to use (COM 1 if your laptop has a serial port) or a different
COM for a USB to serial adapter.
Note: You should be able to use any Current master address

Reference Document - RigOffice 94652886

 Document number 96780739 Page 368 of 544
Revision 1

Scanning for Slaves

STUDENT NOTES:

1. Select ‘Address…Start Search Profibus Slave Address’ from the main menu.
2. The window that opens should show the UART and then each node as they are found.
If an error occurs check all connections, terminating resistors and the communications settings.

Reference Document - RigOffice 94652886

 Document number 96780739 Page 369 of 544
Revision 1

Addressing Slaves

STUDENT NOTES:

It is usually preferable to address spare/replacement nodes ‘offline’, i.e. not using the tool network
If replacing more than one node that is addressed through DP Master Simulator (as opposed to rotary or
DIP switches) then only one node should be added at a time to ensure that the correct address is being
sent to the correct node. The default ‘out of the box’ node address is typically 126.
Scan for slaves as described previously.
1. Select/Click on the Node so that a box appears around the outside
2. Select ‘Address…Change Profibus Slave Address…’ from the main menu.
3. Verify that the correct Old Slave Address is displayed, input the New Slave Address.
Devices may require power cycled for new address to take effect.
Dip switches take priority over software addresses so don’t play with switches.

Reference Document - RigOffice 94652886

 Document number 96780739 Page 370 of 544
Revision 1

Verifying Slave Address

STUDENT NOTES:

Cycle the 24VDC power supply to the node (if required).

1. Select ‘Address…Start Search Profibus Slave Address’ from the main menu.
2. The window that opens should show the UART and then each node as they are found. Verify that
the node address is correct.
Repeat as required for other new nodes.

Reference Document - RigOffice 94652886

 Document number 96780739 Page 371 of 544
Revision 1

Testing Feedback

STUDENT NOTES:

Node ID number is unique to particular devices and can be used to help identify node and/or GSD file
(Ident Number in GSD file).

It is possible to test the feedback from certain devices prior to installation or independent of the
controller (PLC/SBC).
1. Choose Address…Start Search Profibus Slave Address. Node(s) should appear after a short delay.
2. Choose File…Open GSD and browse to the correct GSD file for that device
3. Choose Communication…Start with GSD. Press Ok when the warning popup appears and then
monitor the values

GSD files can usually be sourced from the manufacturer’s website. If a GSD file does not work then it may
be there is a custom GSD file for NOV. Check with tech support or engineering.

Reference RigDoc 94652886

Document number 96780739 Page 372 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 373 of 544
Revision 1

BWConfig - Canbus Joystick

 Document number 96780739 Page 374 of 544
Revision 1

BWConfig – User Interface

STUDENT NOTES:

Display Panes
The BWConfig display is divided into 4 panes.
1. X-gateway Configuration
Module type and status information about the X-gateway module that was detected.
2. Ethernet Configuration
Configuration of Ethernet network parameters.
3. J1939 Configuration
Configuration of J1939 network parameters and status of the network interface.
4. J1939 I/O Configuration
Configuration of the content and layout of the I/O tables.

Reference Manual – 10511588-MAN

 Document number 96780739 Page 375 of 544
Revision 1

BWConfig – Setting the IP Address

STUDENT NOTES:

Setting the IP Address with the Configuration Switch (Dip switches)

If DHCP/BootP is not enabled or a server is not found and the Configuration Switch is non zero, on power
up the value of the switch is used to form an IP Address. The switch represents the binary value of the last
byte in the 4 byte IP address. In this case it is n.
IP address: 192.168.1.n
Subnet mask: 255.255.255.0
Gateway address: 0.0.0.0 (No gateway set)
This is a private address and can only be used on a local intranet. In such a case a Web Browser such as
Microsoft’s Internet Explorer can be used to access the Xgateway’s web page which allows changing the
IP Address, Subnet mask, and GateWay address settings.
Note: A non-zero DIP switch setting will override any other Ethernet configuration that is done.

Setting the IP Address Using DHCP/BootP

When DHCP/BootP is enabled and a DHCP or BootP server is found, the IP address, Subnet mask, and
Gateway address is automatically configured by the DHCP/BootP server. It can be enabled using
BWConfig or the X-gateway’s Settings web page.
Note: The use of DHCP is the default configuration for the Anybus X-gateway as shipped.
 Document number 96780739 Page 376 of 544
Revision 1

Setting the IP Address Using the Web Page

The Ethernet addresses can also be configured using the Status and Settings web page resident on the X-
gateway.
The gateway web interface also features pages that allow the data being sent/received to be viewed.

Reference Manual – 10511588-MAN

 Document number 96780739 Page 377 of 544
Revision 1

BWConfig - Joystick and Canbus

STUDENT NOTES:

Physically connect to the device using serial cable/serial to USB converter.

Open BW Config Program
1. Select File, Select Open
2. Choose the correct configuration file for the joystick you want to configure. (Driller, left/right or
AD, left/right)

Note: Cross-over serial cable required. Standard cable will not work
 Document number 96780739 Page 378 of 544
Revision 1

BWConfig - Joystick and Canbus

STUDENT NOTES:

No configuration is required for the BW Config Program; the software will connect to the device
automatically (as soon as the software is started) if the hardware is correctly connected.

The device parameters are set up by NOV engineering and do not need to change.

To check if the program is communicating correctly

1. Check the ONLINE status
2. Download to Module will be available.

It is also possible to upload if a backup is required or for remote troubleshooting purposes. Ensure the
function and IP address are in the filename e.g. DRILLCHAIR_LEFT_1921683180.cfg
Document number 96780739 Page 379 of 544
Revision 1

STUDENT NOTES:
 Document number 96780739 Page 380 of 544
Revision 1

Verification of Indicators

STUDENT NOTES:

It is good practice to become familiar with the healthy state of device indicators, not just look at them
when things go wrong. Make a note on drawings, take photos or add notes to the inside of a panel door
describing the device indicators when healthy. This helps identify a difference if something goes wrong
which can speed up troubleshooting.
The following slides show just a small sample of the devices used.
 Document number 96780739 Page 381 of 544
Revision 1

Verification of Indicators

STUDENT NOTES:

The PROFIBUS couplers and PROFIBUS repeaters have been particularly dimensioned for the industrial
requirements of hazardous areas of zone 1.
PROFIBUS couplers and PROFIBUS repeaters are used for the separation or generation of new segments,
converting the RS485 typical line structure into an open and flexible tree structure. Downstream stations
can be coupled to and de-coupled from the superior bus system in a non-reactive and break/short-circuit
tolerant manner, even during running bus operation.
The devices facilitate a duplication of the signal to realize a redundant connection to a master.

Looking for the LED lights and indicators help troubleshoot. In this picture, look at the light indication. It
can be said that all three absolute encoders has power and are sending signals. These couplers allow long
spurs on the Profibus DP network.
• S1 sets the baudrate (table in right hand image).
• S2 enables/disables the terminating resistor.

LED Displays
Color Description
Green Operational readiness
Green/Yellow Bus activity
 Document number 96780739 Page 382 of 544
Revision 1

Verification of Indicators

STUDENT NOTES:

PROFIBUS OLMs are designed for use in optical PROFIBUS fieldbus networks. They allow the conversion of
electrical PROFIBUS interfaces (RS-485 level) into optical PROFIBUS interfaces and vice versa.
The modules can be integrated in existing PROFIBUS fieldbus networks with the known advantages of
optical transmission technology. A complete PROFIBUS fieldbus network can also be set up with modules
in a linear (bus), star or ring topology as well as any combination of these topologies.
To increase the reliability of the fieldbus network in case of failure, the redundant ring is supported.

LED Displays
System
LED Display Possible Causes Signaling Contact
lit Green The transmission rate was detected and the voltage does not signal
supply is ok
Not Lit Voltage supply outage (complete outage, with a signals
redundant supply, outage down of both supply voltages)
Voltage supply connected wrongly
Module
defective
Flashes Red Transmission rate not yet detected does not signal
There is no transmitting bus node
No connection to a partner module sending frames
Transmit and receive fiber-optic cables are swapped over
Transmission rate does not correspond to the PROFIBUS standard
 Document number 96780739 Page 383 of 544
Revision 1

Only one single bus node is connected, which only sends token
to itself. After activation of a second bus node, the display must
change (token frames are not enough to set the transmission rate)
The connected RS-485 segment is only terminated at one side
Flashes Red/ Transmission rate detected but… does not signal
Green The slot time of the network could not be detected yet (network
parameter HSA set too low, there is no transmitting bus node)
One optical channel is set to “redundant optical ring“ mode but
the second one is not (this mode must always be set on both
optical channels)
The value for the slot time of the network is set too low

Reference Document - BA_OLM4_76.pdf

(https://support.industry.siemens.com/cs/document/56606534/simatic-net-profibus-optical-link-module-
olm-p11-v4-0-olm-p12-v4-0-olm-p22-v4-0-olm-g11-v4-0-olm-g12-v4-0-olm-g22-v4-0-olm-g12-eec-v4-0-
olm-g11-1300-v4-0-olm-g12-1300-v4-0-operating-instructions?dti=0&lc=en-WW)
 Document number 96780739 Page 384 of 544
Revision 1

Verification of Indicators

STUDENT NOTES:
Document number 96780739 Page 385 of 544
Revision 1

Lesson Review
Document number 96780739 Page 386 of 544
Revision 1

Amphion Main Service Page

STUDENT NOTES:
 Document number 96780739 Page 387 of 544
Revision 1

Lesson Objectives

STUDENT NOTES:
 Document number 96780739 Page 388 of 544
Revision 1

Devices and Navigation

STUDENT NOTES:

This diagram illustrates the SBC service page menu items covered in each level. For level 0 items please
reference level 0 student handbook, RigDoc 96747643.
Document number 96780739 Page 389 of 544
Revision 1

IP Network

STUDENT NOTES:
 Document number 96780739 Page 390 of 544
Revision 1

Devices and Navigation

STUDENT NOTES:

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
 Document number 96780739 Page 391 of 544
Revision 1

Edit Address List

STUDENT NOTES:

*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

Edit Address List opens a simple utility that allows us to add, delete or change entries in the file.
 Document number 96780739 Page 392 of 544
Revision 1

Edit Address List

STUDENT NOTES:

Click IP Network --> Edit Address List to display the device groups connected to the network.
From this window, you can add, delete, and rename device groups, or add, delete, and rename device
names within each group.

Click the icon located to the left of the group to expand and display the devices within the group.
Click OK or cancel to close the window and return to the main Web page.
 Document number 96780739 Page 393 of 544
Revision 1

Edit Address List

STUDENT NOTES:

Add a New Group

Right-click Network Device Groups, then click Add Group.
Type a group name into the space provided, then click OK to close the Add Group pop-up window. The
new group is now listed in the Edit Address List window.

Add a Group Device

Right-click the device group, then click Add Network Device.
Type the device name and valid IP address into the spaces provided, then click OK to return to the Edit
Address List window. The new device is listed within the group
 Document number 96780739 Page 394 of 544
Revision 1

Edit Address List

STUDENT NOTES:

Rename a Group
Right-click the device group, then click Edit Group Name.
Type a name into the space provided, then click OK to close the Change Group Name pop-up window.
The new group name is listed in the Edit Address List window.

Delete a Group
Right-click the device group, then click Delete Group.
Click Yes or No to confirm or cancel and return to the Edit Address List window.
 Document number 96780739 Page 395 of 544
Revision 1

Edit Address List

STUDENT NOTES:

Edit a Device
Right-click a network device, then click Edit Network Device.
Type the appropriate information into the spaces provided, then click OK to save changes and return to
the Edit Address List window.

Delete a Device
Right-click a network device, then click Delete Network Device.
Click Yes or No to confirm or cancel and return to the Edit Address List window.
 Document number 96780739 Page 396 of 544
Revision 1

Edit Address List

STUDENT NOTES:

Send Address List to Controllers

Click IP Network --> Send Address List to Other Controllers to update and store IP address information to
the tool controllers. After a few minutes the Copy Results confirmation window appears.
Click OK to close the window.

The device names and their IP addresses are stored in a file called ip_list.xml
 Document number 96780739 Page 397 of 544
Revision 1

Show IP Address

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.
 Document number 96780739 Page 398 of 544
Revision 1

Investigate Address

STUDENT NOTES:

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

 Document number 96780739 Page 399 of 544
Revision 1

Investigate Address

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

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 center 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
Document number 96780739 Page 400 of 544
Revision 1

Software Management

STUDENT NOTES:
 Document number 96780739 Page 401 of 544
Revision 1

Restricted Functions

STUDENT NOTES:

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.
 Document number 96780739 Page 402 of 544
Revision 1

Software Versions

STUDENT NOTES:

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.
 Document number 96780739 Page 403 of 544
Revision 1

Backup and Restore

STUDENT NOTES:

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.
• You’ll see the file path and name in the text box. Press Upload Varball
Document number 96780739 Page 404 of 544
Revision 1

Backup and Restore

STUDENT NOTES:

• You’ll see the file path and name in the text box. Press Upload Varball
 Document number 96780739 Page 405 of 544
Revision 1

Backup and Restore

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
 Document number 96780739 Page 406 of 544
Revision 1

Backup and Restore

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.
 Document number 96780739 Page 407 of 544
Revision 1

Backup and Restore

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.
 Document number 96780739 Page 408 of 544
Revision 1

Backup and Restore

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.
 Document number 96780739 Page 409 of 544
Revision 1

Backup and Restore

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
 Document number 96780739 Page 410 of 544
Revision 1

Backup and Restore – Error

STUDENT NOTES:

If one of the controllers fails to create a varball, an error file will be created, with the extension .err
 Document number 96780739 Page 411 of 544
Revision 1

Software Installer

STUDENT NOTES:

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 list box. 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
 Document number 96780739 Page 412 of 544
Revision 1

Software Installer

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.
 Document number 96780739 Page 413 of 544
Revision 1

Transfer Files

STUDENT NOTES:

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.
 Document number 96780739 Page 414 of 544
Revision 1

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
 Document number 96780739 Page 415 of 544
Revision 1

Transfer Files

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
 Document number 96780739 Page 416 of 544
Revision 1

Transfer Files

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
 Document number 96780739 Page 417 of 544
Revision 1

Transfer Files

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.
 Document number 96780739 Page 418 of 544
Revision 1

Transfer Files

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
 Document number 96780739 Page 419 of 544
Revision 1

Transfer Files

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
 Document number 96780739 Page 420 of 544
Revision 1

Software Manager

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.
 Document number 96780739 Page 421 of 544
Revision 1

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:

• 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 duplicate 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.
Note 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.
 Document number 96780739 Page 422 of 544
Revision 1

Software Manager

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.
 Document number 96780739 Page 423 of 544
Revision 1

Software Manager

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
 Document number 96780739 Page 424 of 544
Revision 1

Diagnostics

STUDENT NOTES:
 Document number 96780739 Page 425 of 544
Revision 1

Debug Monitor

STUDENT NOTES:

Warning – Don’t adjust/modify parameters/values while tool is running.

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, 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.

 Document number 96780739 Page 426 of 544
Revision 1

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.

 Document number 96780739 Page 427 of 544
Revision 1

Debug Monitor

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

 Document number 96780739 Page 428 of 544
Revision 1

Debug Monitor

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.
 Document number 96780739 Page 429 of 544
Revision 1

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.

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

 Document number 96780739 Page 430 of 544
Revision 1

Debug Monitor

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.
 Document number 96780739 Page 431 of 544
Revision 1

Debug Monitor

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)
 Document number 96780739 Page 432 of 544
Revision 1

Debug Monitor

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. Twenty different parameters can be recorded at
once, lasting approximately 100 seconds each. Only one user can record data from the same controller at
any given time. Reference document D811001117-MAN-001 P80/298
 Document number 96780739 Page 433 of 544
Revision 1

Debug Monitor

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.
 Document number 96780739 Page 434 of 544
Revision 1

Manipulating Graphs

STUDENT NOTES:

Graph Labels
Press and hold down the <Ctrl> button on your keyboard, then click anywhere inside the graph to display
an Add Graph Label pop-up option.
Click Add Graph Label to display the Add Graph Label pop-up window.
Use the space provided next to Graph Label to type custom text for the label.
Click Insert Value to insert the parameter’s value at that particular point on the graph.
Click Insert Time to insert a time stamp at that particular point on the graph.
Click Insert Name to insert the WebObject name at that particular point on the graph.
To edit, remove, or move a graph label, press and hold the <Ctrl> button on your keyboard, and click the
label to display the pop-up menu. (label now shown on graph)

Graph Display Options

Show All Graphs on Same Scale

Click Graph located in the menu bar to display the drop-down menu items. Click Show All Graphs on
Same Scale to display all WebObjects on the same scale.

Show All Graphs Stacked

Click Show All Graphs Stacked to display each WebObject separately, but stacked. (As shown)

Show All Graphs Full Height

 Document number 96780739 Page 435 of 544
Revision 1

Click Show All Graphs Full Height to display each WebObject at its maximum height, filling the screen
vertically.

Show All Graphs

Click Show All Graphs to display the graphs for all WebObjects recorded.

Plot One Object Against Another

Click Plot One Graph Against Another to display the selection pop-up window. Click the down-arrow
buttons to display and select the horizontal and vertical axis objects.
Click Animate to animate the WebObjects’ recordings from the beginning to the end. Click Close to close
the pop-up window.

Object Grouping
Click Graph Grouping to display the Graph Grouping pop-up window. Each WebObject displays on the top
left side of the Graph Grouping pop-up window. Click to assign a group to each object, then click to select
(check) or deselect (uncheck) group movement, resizing, and visibility options for each group. Click OK to
close the pop-up window.
 Document number 96780739 Page 436 of 544
Revision 1

Manipulating Graphs

STUDENT NOTES:

Key:
1. Thumbnail
2. WebObject

Plot Information Panel

The left side of the window contains one plot information panel for each graph plot (shown here). The
panel is labelled with the name of the WebObject plotted and graphed, as well as other controls that can
be used to manipulate the graph’s appearance.

Move, Size, Display (On/Off), and Line Width

Click the on/off button to toggle the display on or off.
The other arrow-up and -down buttons move, size, or change the line width (as labelled) by one pixel
each time it is clicked. Hold down one meta key <Shift>, <Alt>, or <Ctrl> to move, size, or change the line
width by ten pixels each time the arrow-up or -down key is clicked. Hold down two meta keys while to
move, size, or change the line width by 50 pixels each time the arrow-up or -down key is clicked. Hold
down all three meta keys to move, size, or change the line width by 100 pixels each time the arrow-up or -
down key is clicked.

Individual Graph Display Options

Click the color “thumbnail” to display the Change Graph Options pop-up window.
• Click Set Color to display the color selection pop-up window and define the WebObject’s graph
color.
Document number 96780739 Page 437 of 544
Revision 1

• Click Show Value Label to display each point’s actual value.

• Click Show Time Label to display each point’s time stamp.
• Click Isolate Graph to display only that WebObject on the graph (making all other graphed objects
invisible). See section titled "Show All Graphs" on page 6-14.
• Click Fill Screen to magnify that object’s graph to its maximum, filling the screen vertically.
• Click any of the Point Decoration radio buttons to change the way each data point is displayed;
normal (none), vertical line, plus signs, or dots. Click OK to close the Change Graph Options pop-
up window.
 Document number 96780739 Page 438 of 544
Revision 1

Manipulating Graphs

STUDENT NOTES:

Mousing Inside the Graph Area

When moving the mouse over the main graph area, a grey line appears, and moves along with the tip of
the mouse pointer.
A digital time displays in the top left portion of the Graph Viewer window, and changes accordingly with
mouse movement.
Each WebObject’s Plot Information Panel also displays a value in its lower left corner, which represents
its value where the grey line intersects with the graph plot.
Clicking and dragging inside the main graph area creates a grey rectangle.
A second and third reading displays inside each WebObject’s Plot Information Panel; the second
represents the width of the rectangle in graph time; the third represents the difference in value between
the top and the bottom of the rectangle in terms of space for individual plot.

Press <Ctrl> on your keyboard while clicking and dragging the mouse inside the graph area to display a
pop-up menu.
Click Zoom Into Rectangle to magnify the area, or click Show Data Inside Rectangle to display the Data
Sheet View pop-up window.
This table displays time, data points, and one or more plots in other columns. Click OK to close the Data
Sheet View pop-up window.
 Document number 96780739 Page 439 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

Warning – Don’t adjust/modify parameters/values while tool is running. 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

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.
 Document number 96780739 Page 440 of 544
Revision 1

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.
 Document number 96780739 Page 441 of 544
Revision 1

I/O Diagnostics

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 are 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.
 Document number 96780739 Page 442 of 544
Revision 1

I/O Diagnostics

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
 Document number 96780739 Page 443 of 544
Revision 1

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.
• Transmission: Ethernet
• I/O Type: MOD
• 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.
 Document number 96780739 Page 444 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

NET
Click the NET tab to display all Net I/O types.
• Transmission: Ethernet
• 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]}
 Document number 96780739 Page 445 of 544
Revision 1

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.

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
• Transmission: Ethernet
• 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.
• Transmission: Ethernet
• 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
 Document number 96780739 Page 446 of 544
Revision 1

I/O Diagnostics

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.
 Document number 96780739 Page 447 of 544
Revision 1

I/O Diagnostics

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.
 Document number 96780739 Page 448 of 544
Revision 1

I/O Diagnostics

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.
 Document number 96780739 Page 449 of 544
Revision 1

I/O Diagnostics

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.
 Document number 96780739 Page 450 of 544
Revision 1

I/O Diagnostics

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
 Document number 96780739 Page 451 of 544
Revision 1

I/O Diagnostics

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.

 Document number 96780739 Page 452 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

This also works with I/O objects shown on the Questions list.

Press the button to the right of its name.

 Document number 96780739 Page 453 of 544
Revision 1

I/O Diagnostics

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.

 Document number 96780739 Page 454 of 544
Revision 1

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.

Forces will be cancelled if the controller is restarted

 Document number 96780739 Page 455 of 544
Revision 1

Check / Change Address

STUDENT NOTES:

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
 Document number 96780739 Page 456 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

Check / Change Address

• 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!
 Document number 96780739 Page 457 of 544
Revision 1

I/O Diagnostics

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
 Document number 96780739 Page 458 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

Addressing Conflicts
• 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
 Document number 96780739 Page 459 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

Addressing Conflicts Continued

• 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)
 Document number 96780739 Page 460 of 544
Revision 1

I/O Diagnostics

STUDENT NOTES:

Addressing Conflicts Continued

• The controller will restart and if all is well the Dashboard should look normal
 Document number 96780739 Page 461 of 544
Revision 1

Data Logging

STUDENT NOTES:

The data logging graph viewer was designed as an offline graphing application to allow an engineer to
display information obtained through the logging system. The data logging system was originally intended
for engineering analysis on any SBC equipped rig without the need for a logging system such as eHawk,
however is proving popular with FSTs and tech support on rigs it is available on. The logging system is not
intended for use by customer maintenance personnel, except perhaps to retrieve the data files for
transmittal to NOV engineering/tech support.

The data logging graph viewer is part of the Amphion www package. It is available as part of www
versions 1.6.7 or later, though is not in general release due to ongoing refinements and discussions on
commercial implications.

It is possible to use the data logging graph viewer as a Java applet, which is embedded into an HTML page
hosted by an Amphion controller. It is accessible from the service page. On the same HTML page is a link
where the Windows executable version can be downloaded for offline use.

It is also available from National Oilwell Varco as an application, both as a Windows executable and a Java
jar file.

Reference document D4B1000339-MAN-001.

 Document number 96780739 Page 462 of 544
Revision 1

Data Logging

STUDENT NOTES:

The main screen shows the menu bar at the top, with an information bar below.
There is a large space in the middle for the graphs. Red and green vertical lines help determine the value
of a graph at a given mouse position and give an indication of the differences in time between the two.
There are time sliders at the bottom and a set of buttons below that which move the graph to the left and
right.

Reference document D4B1000339-MAN-001.

 Document number 96780739 Page 463 of 544
Revision 1

Scheduler Diagnostics

STUDENT NOTES:

Adjustments should not be made without consulting tech support or engineering during both I&C and
operational stages.
Key:
1. Tool Controller Name and IP Address
2. Device Name
3. Expected and Actual Communication Frequency
4. Change Frequency
Controllers run through a cycle once every twenty milliseconds (or 50 times per second). A cycle includes
all calculations, communications, inputs and outputs. The controller keeps track of its communication
schedule by organizing its obligations in its communications calendar.
The purpose of the Scheduler Diagnostic module is to provide information about the controllers’
communications calendars. If, for example a device is requesting information from a controller, but the
controller does not appear to be processing the requests often enough, the Scheduler Diagnostic module
provides a way to view the controller’s communication calendar, and also provides the option to modify
requests.

The main Scheduler Diagnostic page contains an information panel for each controller selected. Each
panel contains a list of devices with which the controller communicates.
The Expected and Actual communication frequency displays for each device. A pink background appears
in cases where the two frequencies differ by more than five percent.
 Document number 96780739 Page 464 of 544
Revision 1

Changing Communication Frequency

Click the appropriate controller’s Change button. If necessary, type the administrator’s password into the
space provided, then click OK to continue and display the Change pop-up window.
Type the desired change into the space provided, then click Make the Change.
Click Yes at the confirmation window to store the change and restart the tool controller.

Do not operate machinery when changing communication frequency. Doing so causes the tool
controller to restart. Failure to observe and follow proper procedures could result in serious or fatal
injury to personnel, significant property loss, or significant equipment damage.

Show Distribution Map

Click the appropriate controller’s Show Distribution Map to display its communications calendar in table
format.
Each cell contains a device name that the controller communicates with during each controller cycle. Cells
are color-coded by device (all instances of a specific Modbus device may be red, for example). If no device
is scheduled in a cell, it is labelled “available.” The map can be saved in Microsoft® Excel-compatible .csv
format. Click Save to File to assign a name and location for the data. Click OK to close the map.

Show C2C Inconsistencies

Click Show C2C Inconsistencies to display a text box with information about all instances of inconsistent
C2C communications.
If no inconsistencies exist, the button is disabled.
Reference Document – D811001117-MAN

Scheduler Diagnostics
The controller is designed to go through all of its calculations, communications, inputs, and outputs once
every twenty milliseconds (so, fifty times each second). In fact, the controller people have done quite a bit
of work to insure that every controller "cycle" takes no more than twenty milliseconds each. Every
controller gets requests (from other controllers, the screen system, or input and output devices) to
periodically send information. Often, these requests are for information at some other frequency than
twenty milliseconds. For example, a controller may receive a request from a Modbus device to send
information once every two hundred milliseconds. So, that controller would send information once every
ten cycles. Some other device might request information once every sixty milliseconds (so, once every
three cycles).
The controller keeps track of these requests by posting them in its "communications calendar." The
calendar is just a list of cycles. Each spot in the calendar might contain a marker to send a message to an
outside device. A calendar is designed to cover a full second and then repeat, so there are fifty spots, one
for each cycle. Because there might be multiple requests that fall into the same spot (the same cycle), the
calendar maintains a number of different "slots" for each cycle. In the current controller (3.7.0), there are
fifty slots for each cycle. So, the complete calendar can be thought of as a 50 x 50 grid. It contains fifty
cycles and for each cycle, the controller can schedule messages to be sent to fifty different places.
There are actually some hidden slots as well. The controller maintains one slot per cycle to communicate
with the operator screens. This slot does not appear in the calendar.
It's a flexible system, but sometimes things don't go the way we expect them to. For example, a Modbus
node might ask the controller to send it information once every fifty milliseconds. But the controller can
only schedule messages in twenty-millisecond chunks. Fifty milliseconds are not forty milliseconds and it's
not sixty milliseconds. So, what will the controller do? It will actually just schedule the request to be
serviced once every sixty milliseconds. If the controller gets a request to send information once every two
 Document number 96780739 Page 465 of 544
Revision 1

seconds, there's no way that it can service that request because its calendar only covers one second. So, it
will schedule the request to be serviced once per second. That's the best that it can do.
The purpose of the Scheduler Diagnostic is to provide some insight into the controller's communications
calendar. If you have a device that is requesting information from a controller and the controller isn't
servicing those requests as often as you might like, the Scheduler Diagnostic gives you a chance to look
inside the controller's communications calendar and see what it is actually doing. It will also give the
option to be able to modify requests.

Functional Requirements
View the communications calendar for a controller
Compare the frequency of communications requests that have are expected (as configured) against the
actual frequency at which they are scheduled to be serviced
Allow the operator to change the expected/configured frequency of a communications request.
Analyze configurations to determine inconsistencies between controllers

User Interface
The Scheduler Diagnostic shows the communications calendar on every controller. When it starts up, it
presents the operator with a list of the controllers known to it (it actually uses controller names rather
than tool names). The list contains checkboxes that allow the operator to select which controller
schedules to check. By default, all are selected except the V-DAQ. The Scheduler Diagnostic needs to send
queries to the controllers to find out about them, and this process can stall for a long time if the controller
is not communicating on the network. So the list allows the operator to narrow down the choices in case
there are some controllers that are known to be off line.
Once the list is dismissed, a progress dialog comes up to inform the operator of the progress of querying
and analyzing the controllers. Each controller is contacted at least twice, first to find out the name of the
controller in the controller-to-controller system of communications, and then to find more information
about how it is configured. This two-step process is necessary because we need to know the name of the
controller before we can determine whether other controllers are calling it correctly. Any controller that
cannot be contacted in the first step will not be contacted in the second step.
Once all of the available controllers have been contacted and analyzed, the Scheduler Diagnostic applet
shows its main window, which is a panel inside a scroll pane that has areas for each controller.
Inside the area for each controller, there are two buttons, one to show the communications calendar for
that controller and a second to look at configuration inconsistencies. Below that, there will be a number of
smaller rectangular areas.
Each of these smaller areas gives details about one device that the controller is scheduled to periodically
send information to. The kind of information doesn't matter. What matters for the purposes of the
Scheduler Diagnostic is how frequently the communication is scheduled to take place. Each smaller area
has a title telling the name of the device and two text fields: one for the "expected" communications
frequency (e.g., once every 50 milliseconds) and the "actual" frequency (e.g., once every 60 milliseconds).
There is also a "Change" button that will allow the operator to change the expected (configured)
communications frequency. If the expected frequency differs from the actual frequency by more than five
percent either way, then the background of the rectangular area will be pinkish. Otherwise, the
background of the rectangular area will be light blue. It should be easy for the operator to spot places
where the communications is not what was expected.
The controller's Show Distribution Map button will open a dialog box with a table showing the entire
communications calendar for that controller. This is the 50 x 50 grid that the controller uses to keep track
of who it will communicate with every controller cycle. In each cell in the table, there will be the name of
the device that will be communicated with, or, if there is no device for that cell, it will be marked
 Document number 96780739 Page 466 of 544
Revision 1

"available." The cells are color-coded so that each device will have the same color. All instances of a
specific Modbus device might be red, for example. All instances of a controller might be blue. This is
designed so that it should be relatively easy to see when a specific device is scheduled to be serviced. The
distribution map window has a "Save to File..." button that will allow the operator to save the map to their
local hard drive as a Microsoft Excel-compatible .csv file. There is also an "OK" button that will close the
window. If the communications calendar cannot be obtained from the controller, this button will be
disabled.
The controller's Show C2C Inconsistencies button will open a dialog box with a text field. Inside the text
field, there will be messages such as "On the Mud Pumps at 192.168.31.61, there is an entry in the c2c
configuration for a controller named VDAQ at 192.168.31.47, but there is no controller at that address
listed in the ownership.xml." Another sample message is "On the Auxiliary at 192.168.31.27, there is an
entry in the C2C configuration file for the controller at 192.168.31.40. The entry calls the controller
'Driller's Chair,' but the controller calls itself 'Chair.'" If there are no inconsistencies in the C2C
configuration, this button will be disabled.
The Change button on each device listing will actually write values to the controller, so this item is
password protected. If the operator has not already entered the administrative password, they will need
to enter it before making changes to the configuration. Once the password has been entered, the operator
will get a dialog box that will allow them to enter the requested delay time in milliseconds. This dialog
includes some description of what will happen, including which controller will be restarted after the
change has been made.

Implementation
Requests for information from the controller come from a few well-defined places. For example,
controller-to-controller requests are sent by actual demands from one controller to another to get it to
start sending information. However, external devices cannot call up the controller to ask that information
be sent. Instead, the controller is configured internally to send information to these external devices. This
can be done in a number of different ways, but the important thing is that the communications delay to an
external device is a persistent value in the controller itself. So, the controller configures itself to send a
periodic sequence of messages to some remote device (other than another controller).
Regardless of how it gets there, the message request has a delay time which is stored in the controller's
persistent data storage file, the objects.csv. The delay time will appear as one of the web objects on the
controller. When the applet is analyzing controllers, it does a request to get the names and values of every
web object on a controller using the DataServlet's "pretty" request. It sorts through the list and finds all
instances of "delayTime." As long as the name of the device appears in the same web object name, it
recognizes the web object as a communications frequency request. It uses the value of that web object as
the "expected" value.
The applet figures out the actual frequency by looking at the communications calendar (which it gets as an
array from the controller). The applet will run through the communications calendar ten times and mark
how many times an item appears. This gives it a pretty good idea of how often the communication is
actually scheduled. It uses that value as the "actual" value.
The applet changes the scheduled time by changing the value of the delay time web object, and then
asking the controller to save the changes to persistent storage. The controller needs to be restarted to
update the communications calendar.
This is true for locally configured (i.e., Modbus) and remotely configured (C2C) communications. But with
locally configured communications, the controller that sends the communications is restarted. With
remotely configured communications, the controller that receives the message (and sends the request for
the message) is restarted.
 Document number 96780739 Page 467 of 544
Revision 1

Scheduler Diagnostics

STUDENT NOTES:

Each “target” of communications (i.e.: the controller at the other end) is shown in a different color to
make it easier to get a picture of how frequently comm is carried out with that controller. (Note:
Amphicom refers to the adaptor card that communicates with Profibus I/O.)
 Document number 96780739 Page 468 of 544
Revision 1

Profibus Diagnostics

STUDENT NOTES:

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.
1. Green nodes are working properly (Applicom, node 2 will remain yellow).
2. Yellow nodes are communicating but there is an issue of some kind e.g. configuration mismatch
3. Red nodes are faulty (usually poor or no communication).
4. Grey nodes are devices found on the network but not configured.
5. Nodes will appear blue if using VirtualBox.

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:
 Document number 96780739 Page 469 of 544
Revision 1

• 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

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
 Document number 96780739 Page 470 of 544
Revision 1

Profibus Diagnostics

STUDENT NOTES:

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.

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

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:
 Document number 96780739 Page 471 of 544
Revision 1

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
 Document number 96780739 Page 472 of 544
Revision 1

Configuration

STUDENT NOTES:
 Document number 96780739 Page 473 of 544
Revision 1

PC Security and Roles on Amphion

STUDENT NOTES:

In order to govern what PCs, which include FST laptops, HMIs and DWSs, can and can’t do on the
Amphion network, various systems have been used over the years.

The different categories of PC defined are Driller, AD (assistant driller), Developer (internal use only),
Standby and Remote. The restrictions imposed on a particular type of PC are defined in ownership.xml
and the www for certain functions. Ownership.xml was configured and released by the software
department and knowledge of xml was required to make changes.

Initially a PC had to have a text file called id.txt in c:\varco, in which the required role had to be entered.
The SBC would then check this file when interrogated by the PC to determine what it could and couldn’t
do.

In www 1.7.0 the preferences function was introduced. It uses the PC MAC address to identify it. Through
the preferences link an interface allows permissions to be defined and then written to the ownership.xml
file.

In www 1.8 a graphical representation, shown above, has been introduced to convey the configured
preference information.

Reference RigDoc 100573683

 Document number 96780739 Page 474 of 544
Revision 1

Preferences

STUDENT NOTES:

Workstation Assignments
In www versions before 1.7, we identified the workstation type by using a special file, the id.txt file, which
had to go into a varco directory on the root of the HMI’s flash card. This file would contain the name of
the ownership group that the HMI was assigned to. When the operator screens applet started up on a
particular HMI, it would read the id.txt file and know that the HMI was assigned to a specific ownership
group (like “Driller” for example).

This made it difficult to configure an HMI. We usually ship HMIs with read-only flash cards, and a special
procedure was required to write the id.txt file to the flash card and insure that it would persist between
reboots. If we ever had to change out an HMI in the field, we would likely have to attach a keyboard to it
in order to set up the ownership association.
In www 1.7, we changed the way we identify workstations. Instead of a file on the flash card, we use the
Ethernet MAC address of the HMI’s network interface card. MAC addresses are unique for each device, so
it can be used as a “signature” to identify the HMI. The MAC address of each device is associated with a
profile, and a list of these associations is kept in a file on every controller. When the operator screens
applet starts up, it can read the association from the file on the controller and know that the workstation
whose MAC address it is running on has been assigned to a specific profile (for example, the Driller).

We no longer need to worry about saving a file to the HMI. However, we do need to set up these
associations when we are installing and commissioning HMIs.
In earlier versions of www 1.7.5, we tried various ways to set up the HMIs. In www 1.7.5, we refined the
way we do workstation assignments. The assignments are saved in their own file on the controller, in
 Document number 96780739 Page 475 of 544
Revision 1

/varco/data/persistent/workstation_assignments.obj. We can put the rig into a special mode, HMI

commissioning mode, where it is easy to make workstation assignments.
When the rig is not in HMI commissioning mode, we cannot permanently assign profiles to workstations.
An HMI or laptop that comes on the network outside of HMI commissioning mode can temporarily adopt
a profile using a password. Without the password, an HMI will not be allowed to write to the controllers.
We do this for security; we don’t want someone to be able to plug a laptop into the rig network and start
controlling tools.
 Document number 96780739 Page 476 of 544
Revision 1

Preferences

STUDENT NOTES:

Getting into HMI Commissioning Mode

1. We can put the rig into HMI commissioning mode using the preferences configuration applet,
which is located on the service page.
2. When the applet opens, click on the Workstations button to change to that screen. HMI
commissioning mode can be turned on by putting a check mark in the check box “In
Commissioning Mode.”
After we put a check mark in the check box or remove it, we need to save the settings to the controller
flash cards. We want the workstation_assignments.obj file to be the same on every controller on the rig.
Click on the Open/Save button, bring up the menu, and select Save Workstation Assignments to Network.
This will write the workstation_assignments.obj file to the controllers.
 Document number 96780739 Page 477 of 544
Revision 1

Preferences

STUDENT NOTES:

In HMI Commissioning Mode

1. When the system is in HMI commissioning mode, whenever the operator screens are started up
on an HMI, the operator will see a dialog asking for the HMI name and a profile assignment.
2. The first time the dialog comes up, a name will be chosen at random. It is recommended that the
workstation name be changed to something sensible.
Workstations are named because in www 1.7.4, we introduced a system to allow someone to see the
operator screens from a remote location, to “look over the shoulder” of the driller. Therefore, it helps to
know which HMI is which.
The assignment and name information are saved from one session to another, so the operator only
should need to enter the name and assignment once, unless something changes. In most cases, the
operator only needs to click the OK button.
The list of profiles includes a Read Only profile that can be more or less permanently assigned to a
workstation that we do not want to have write access to the tools on the rig.
This is useful because commissioning engineers like to swap HMIs from one position to another, and like
to be able to use any HMI to accomplish any task
 Document number 96780739 Page 478 of 544
Revision 1

Preferences

STUDENT NOTES:

Out of HMI Commissioning Mode

When we take the system out of HMI commissioning mode, any workstation assignments that have been
set when in HMI commissioning mode will be remembered. The HMI Settings dialog will no longer appear
on those HMIs.
1. When not in HMI commissioning mode, on HMIs whose assignments have not been set, a different
dialog will pop up.
2. This dialog pops up every time an unrecognized HMI attempts to use the operator screens. The
profile assignment and HMI name are not saved. Notice also that there is a small check box near
the bottom of the dialog box that allows the operator to request write access. If this box is
checked, then the operator will get a second dialog which asks them for a password.
If the check box is not checked or the password is not given, then the operator will have read-only access
to the operator screens. This is done to prevent unauthorized access to the operator screens.
To confirm the profile, the appropriate password (ProfileAdmin) needs to be entered in the text field.

Even though the new configuration system allows us to make some interesting changes in how rig
software is configured, no one has really used it. In fact, the “preferences” system tends to be very
unpopular. In www 1.7.4 we are introducing an alternative, which is to allow the rig software to use the
ownership.xml file. In this mode, no “preferences” need to be configured. The system will build its
configuration by reading the ownership.xml file every time the operator screens start up, as it did before
www 1.7. In fact, in www 1.7.4, this is the default mode.
3. We can switch this mode on and off using a check box on the system tab of the preferences
configuration applet.
 Document number 96780739 Page 479 of 544
Revision 1

Preferences

STUDENT NOTES:

Delete Profile
Checking the box in any workstation’s line will flag that workstation for deletion. Press Delete Selected to
delete it from Preferences.obj.
(Select All will select all workstations for deletion; Select None will clear all those already selected).
Press Open/Save.
Select Save Workstation Assignments to Network and press Yes to save the change to the other
controllers.
 Document number 96780739 Page 480 of 544
Revision 1

Preferences

STUDENT NOTES:

By default all the ‘online’ controllers are selected; just press OK.
 Document number 96780739 Page 481 of 544
Revision 1

Operator Screen Configuration

STUDENT NOTES:

The Operator Screen Configuration module provides a way for the user to modify the currently-selected
tool’s menu that displays on the operator workstation touchscreen (HMI). 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.

Main Page
The operator screens contain blue buttons used to navigate between tools and tool screens. Click the
Operator Screen Configuration link (located under Configuration) to display the Administrative Controls
login screen.
1. A green outline indicates the tool controller’s default screen button.

Current Tool Menu

Menus for each tool differ, depending on the tool selected. However, every tool menu contains the
following three standard buttons:
2. Utility: Displays the standard utility menu, such as Choose Units, Choose Language, and Clean
Screen buttons.
3. Common Diagnostics: Displays the standard diagnostic menu.
4. Alarms: Displays alarm information about tools connected to the control network...
Other tool menu buttons are specified by the software programmer, depending on the tool.
 Document number 96780739 Page 482 of 544
Revision 1

My Tools Menu
One tool controller is capable of hosting more than one tool. For example, the auxiliary tool controller (as
shown here) may host the cathead, the HPU, the power slips, and the rotary table; a top drive controller
may host both the top drive and the casing running tool.
5. Click the My Tools button* to display all tools hosted on the currently-selected tool controller.
*The My Tools button may be labelled differently, depending on your rig configuration.

Main Navigation Bar

The main navigation menu displays along the bottom of most operator screens. It is defined by the
software programmer, and may vary from rig to rig. However, every operator menu bar contains the
following three buttons:
6. Back: Displays the previous screen (functional from the touchscreens).
7. <Currently-Selected Tool>: Displays the currently-selected tool’s menu (Driller Chair is the
currently-selected tool shown below).
8. Alarms: Button displays blue under normal conditions; blinks red when there is at least one active
and unacknowledged alarm; solid red when there is at least one active but already acknowledged
alarm (functional from the touchscreens).
5. My Tools: Displays a menu for all available tools. This button’s label may vary depending on your
rig configuration (Driller Tools, or AD Tools, for example).

Reference Document – D811001117-MAN and RigDoc 100573683

 Document number 96780739 Page 483 of 544
Revision 1

Operator Screen Configuration

STUDENT NOTES:

Changing the Current Tool Menu

At the main Operator Navigation Configuration screen, click the screen or a tool menu button to display
one of the pop-up menus.
Tool button pop-up menus vary depending on configuration.
In general, you can add up to six vertical (main menu), and five horizontal (submenu) buttons to the tool
menu. However, you cannot change (such as add submenu buttons, edit labels, or delete) certain standard
menu items, or (such as Utilities, Common Diagnostics, and Alarms).

Adding a Button
Using one of the pop-up menus shown above:
Click Add Button to add a new button to the main (vertical) tool menu
Click Add Submenu to add a submenu (horizontal) button to one of the main (vertical) buttons.

Changing the Button Title and Link

Click the button to display its pop-up menu. Click to select Edit Button and display the Edit Button pop-up
window.
Type a button title into the space provided.
Click the arrow-down button to display a drop-down list of screen description files.
Click to select a file to link it to the button. Click OK to save changes and close the Edit Button pop-up
window.
 Document number 96780739 Page 484 of 544
Revision 1

Deleting a Button
Click the button to display its pop-up menu. Click to select Delete Button.

Moving a Button
Click the button to display its pop-up menu. Click to select Move Up, Move Down, Move Left, or Move
Right to change the button’s position in the menu.

Setting the Default Tool Screen

Click the button to display its pop-up menu. Click to select Set As Default Tool Screen to make the
selected button the default tool screen for the operator. The default tool screen is the first screen
displayed to the operator when the tool is selected. A green outline indicates the tool controller’s default
screen button.

Restoring Original Configuration

Click the button to display its pop-up menu. Click to select Restore Original Configuration to revert to the
original tool menu
Click the button to display its pop-up menu.

Saving Configuration
Click to select Save Configuration to save changes to the tool controller.

Reference Document – D811001117-MAN and RigDoc 100573683

 Document number 96780739 Page 485 of 544
Revision 1

Service Pages Configuration

STUDENT NOTES:

Only preconfigured links can be added/removed using this function.

The Service Pages Configuration module provides a way for the user to modify the following options on
the tool controller’s main service page:
Show or hide the Path Editor link
Show or hide the State Diagram viewer link
Add or delete custom links

Main Page
Click the Service Pages Configuration link (located under Configuration) to display the Administrative
Controls login screen.

Show or Hide the Path Editor Link

The Path Editor module allows the operator to edit paths for path-based equipment, such as pipe racking
systems. Click to select (or deselect) the box beside Show Path Editor to show (or hide) the Path Editor
link (located under Configuration) on the tool controller’s main service page.

Show or Hide the State Diagram Viewer Link

State Diagrams provide a UML (Universal Modeling Language) state-logic view of the internal tool code
itself, and can be used to diagnose problems. Click to select (or deselect) the box beside Show State
Diagram Viewer to show (or hide) the State Diagrams link (located under Diagnostics) on the tool
controller’s main service page.
 Document number 96780739 Page 486 of 544
Revision 1

Add or Delete Custom Links

The Service Pages Configuration page provides a place for the operator or service personnel to create or
delete custom links on the main service page.

Add a Custom Link

1. Type a display name into the space provided in the Display Name column.
2. Click the arrow-down button located beneath Link to File to display the drop-down list of available
HTML files on the currently-selected tool controller.
3. Click to select and link an HTML file.
4. Click to select Add This Link (located in the Add/Delete column), then click Save Changes. The new
link displays at the bottom of the Configuration column on the main service page.

Delete a Custom Link

Click to select Delete This Link (located in the Add/Delete column), then click Save Changes. The link no
longer appears in the tool controller’s Configuration column on the main service page.

Reference Document – D811001117-MAN and RigDoc 100573683

The links are often used by tool developers to add their own custom pages to the service index page,
often for debugging purposes. They can create an operator screen file in the WidgetEditor and then add a
matching HTML page to the service page for easy access
 Document number 96780739 Page 487 of 544
Revision 1

Ownership Configuration

STUDENT NOTES:

The Ownership Configuration module provides a way for the user to modify the ownership.xml file.

The primary purpose of the ownership.xml file is to define ownership rules, such as which operator
screens control which tool controller. The ownership lock-out system runs on the operator tool screens,
rather than on the tool controller, so the controller itself doesn’t determine who can write to it. In other
words, the operator screens determine whether it is possible to write values to one controller or another.
The ownership.xml file should contain the name (or ID) of each tool controller connected to the network.
This name does not appear in the operator screens, but it must match the assigned screen tool name. The
tool controller ID should be named logically, such as “Fore Racker” (spaces are allowed), as opposed to
abbreviations such as “PRS1.”
A script reads the tool controller name from the admin_config.xml file and compares it to the list of tool
controllers contained in the ownership.xml file. When a tool controller ID matches a screen tool name,
the corresponding IP address (from the ownership.xml file) is assigned to that tool controller.

Details on how to modify the ownership.xml from this applet can be found in Reference Document –
D811001117-MAN and RigDoc 100573683
 Document number 96780739 Page 488 of 544
Revision 1

Simulation Control

STUDENT NOTES:

LHS: baselayout-1.2.3, controller_3_7_3_3-4083, platform 7_2 and www-1_7_5_4 RHS: baselayout-1.2.5,

controller-3.8.4, platform 7_2 and www-1.7.15
This should never be used by an FST on a real SBC – virtual SBC only.
Controllers actually connect to real tools should never be run in simulation mode. So it should look as
above, with simulation Disabled. Your tools should always have simulation Disabled as shown above.

For reference:
Enabled enables the On and Off buttons so simulation can be turned on or off at will.
Dedicated puts the controller in permanent simulation mode (it will come up in simulation mode every
time it’s rebooted).
External puts the controller in what’s call HIL (Hardware In the Loop) simulation mode, wherein an
external SBC emulates the tool.
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

Reference Document – D118001117-MAN

 Document number 96780739 Page 489 of 544
Revision 1

Array Manipulator

STUDENT NOTES:

Changes to data in the array manipulator should only be carried out by, or under the instruction of,
Amphion engineering. Changes by FSTs may be allowed where stated in tool specific training/setup
material.

This applet allows the engineer/FST to view and change the values in WebObject arrays stored in memory
on the controller. This module compliments the Debug Monitor, which only allows the engineer/FST to
view and edit values of single WebObjects. The Array Manipulator allows the engineer/FST to view and
edit values in whole arrays.
Allow the engineer/FST to:
View the contents of any array in memory on the controller.
Change the value in an individual cell on an array and write it back down to the controller.

User Interface
It's not pretty. This is one of the oldest applets. The user interface could probably use an update.

Save Array
This button lets the operator save the changes to an array back to the controller.

Refresh
Reloads the currently selected array.
 Document number 96780739 Page 490 of 544
Revision 1

Select An Array
At the top center-right, there is a drop-down menu that contains the names of every available
WebObjectArray on the controller. Select an item from this list to load an array.
The central area is a scrollable panel that shows a spreadsheet-like view of the data in the array.
At the bottom is a Layer menu which only becomes active if a three-dimensional array is being edited.
When active, this popup allows the operator to navigate the third dimension of the array.

Editing
To edit a cell in the array, click on the cell. This will select the text in the cell and a new value can be
written. If nothing has been typed, you can use the arrow keys to navigate from cell to cell. If editing of a
cell has begun, then the arrow keys will move the cursor within the cell
 Document number 96780739 Page 491 of 544
Revision 1

Array Manipulator

STUDENT NOTES:

Here is the comms.distributionMap which is, in fact, the same array that was displayed by Scheduler
Diagnostics.
 Document number 96780739 Page 492 of 544
Revision 1

Trigger Editor

STUDENT NOTES:

Note that any edits/deletions/additions may be lost – firmware level dependent.

Trigger Editor accesses the alarm triggers, permitting the temporary editing of existing alarms. Any
changes are lost when the SBC is restarted.

Trigger Editor
This applet allows the operator to create, edit, and delete alarm and event triggers.

Functional Requirements
Create, edit, and delete alarm and event triggers
Check alarm and event triggers to be sure that they reference real WebObjects

User Interface
There is a tree view of the alarm triggers.
The triggers are sorted alphabetically by their messages. Opening a trigger will show the test that will be
used to trigger an alarm.
 Document number 96780739 Page 493 of 544
Revision 1

Creating an Event Trigger

1. Right-click the Triggers root node to display the Add Trigger menu item.
2. Click Add Trigger to display the Edit Trigger window (shown below).
3. Click Change to display the Choose Web Object pop-up window. Click the markers located to the
left of the directory to expand and display the contents.
4. Click to select a WebObject, then click OK to display the appropriate Edit Trigger window (both are
shown below).
The system determines whether the selected WebObject’s trigger is based on a Boolean value (true or
false), or a numerical value (greater than and/or less than).
• True: Triggers an alarm or event when the condition exists.
• False: Triggers an alarm or event when the condition does not exist.
• Greater Than: Triggers an alarm or event when the item exceeds the value.
• Less Than: Triggers an alarm or event when the item falls below the value.

Set the alarm priority. Critical alarms will trigger the horn. These alarms also will recur. That is, if the
operator acknowledges a critical alarm without doing something to make the alarm inactive (by rectifying
the condition), then the alarm will become unacknowledged after a few minutes.
Create an alarm message. Note that you cannot use the >, < or = symbols, they will crash the trigger
editor.

New alarms should be approved by tech support and/or engineering.

Reference Document D811001117-MAN

 Document number 96780739 Page 494 of 544
Revision 1

Trigger Editor

STUDENT NOTES:

To edit an existing alarm, right-click on the blue box to the left of the trigger and select Edit Trigger from
the pop-up menu.
Delete Trigger will permanently delete any trigger you have created; pre-existing triggers will be deleted
only until the next reboot as they are not stored but created as part of the boot process.

Editing a Trigger
Click the Trigger Editor link to display the Trigger Editor screen.
1. Click the markers located to the left of the directory to expand and display the contents, then right-
click an object to display the Edit or Delete Trigger menu. Click Edit Trigger to display the
appropriate Edit Trigger window.
2. Make desired changes to the trigger...
3. Click OK, then type the administrative password into the space provided.
Click OK again.

Boolean Value Triggers

4. At the Edit Trigger window, click to select an alarm priority.
5. Click the down-arrow and select a Boolean value (True or False) from the drop-down menu.
6. Type an alarm message into the space provided. Alarm descriptions are limited to 120 characters.
Click OK to close the Edit Trigger window.
 Document number 96780739 Page 495 of 544
Revision 1

Numeric Value Triggers

At the Edit Trigger window, click to select an alarm priority.
Type a Greater Than and/or Less Than value into the space(s) provided.
• Leave one field blank to deactivate that test.
• Enter a value into both spaces to trigger the alarm if either value is true.
Type an alarm message into the space provided. Alarm descriptions are limited to 120 characters.
Click OK to close the Edit Trigger window.

Deleting a Trigger
Click the Trigger Editor link to display the Trigger Editor.
Click the markers located to the left of the directory to expand and display the contents, then right-click an
object to display the Edit or Delete Trigger menu.
Click Delete Trigger to display a confirmation window.
Click Yes.
Click OK, then type the administrative password into the space provided.
Click OK again.

Reference Document D811001117-MAN

 Document number 96780739 Page 496 of 544
Revision 1

Trigger Editor

STUDENT NOTES:

It is a good idea to identify the object you want to test in Debug Monitor, then open up Trigger Editor in a
separate IE Window and follow the path downwards:
 Document number 96780739 Page 497 of 544
Revision 1

Set IP Address On Network Device

STUDENT NOTES:

The idea is to avoid the need for proprietary software to set the IP addresses for Ethernet BootP capable
devices. In an Amphion system only Wago Ethernet couplers have the capability/compatibility to allow this
to work.
It works on Wago buss couplers, provided that one and only one buss coupler without its address is in the
system and that that buss coupler is running a bootP client (which is the default). It is at present unable to
change the addresses of Moxa switches because Moxa switches do not run bootP – likewise it cannot set
the addresses of Wago buss couplers if bootP has been turned off (so you can’t use it, for instance, to
correct an error setting the address on a bus coupler); nor will it work if more than one Wago coupler
lacks its address since it won’t know which one to write the new address to.

Set the IP Address of a Network Device

This servlet presents a series of screens that allow the operator to set the IP address of a network device.
It is intended for rig technicians who have to replace a network device like a Wago I/O block. It is not
designed to set the IP address of an SBC (the IP address of an SBC must be set by changing the
ownership.xml file).
The scenario that this attempts to address is the problem of a rig technician who has to replace an I/O
block in the field. The technician can disconnect the old hardware and reconnect new hardware, but the
device needs to have its IP address set so that it can become a functioning member of the network. Out of
the box, these devices have no IP address, or if they do, then it's one that we probably wouldn't be able to
get to. A technician typically would need a special cable and special software running on a laptop in order
to connect to a special port on the device to set its IP address.
 Document number 96780739 Page 498 of 544
Revision 1

However, these devices do run a DHCP or BootP service at startup (these are standard network protocols
that let a device query other devices on the network and set their own IP addresses). The
AutoSetIpServlet will start up a BootP server temporarily on an SBC and conduct a transaction that will let
the new device set its IP address.

Functional Requirements
Allow the operator to set the IP address of a network device.

User Interface
The user interface is mostly text that attempts to explain what needs to be done.
There are two options.
1. One option is to just type in the correct IP address and press "Continue."
2. The other is to scan the network to determine if there are any devices that the SBC knows about
that are not on the network.
The network scan will use the controller's ip_list.xml file as a reference and check (perform a network
"ping" test on) each of the devices that are in the list to see if they are on the network. The list might look
something like this:
Instead of typing in an IP address, the technician could pick it from a list of devices that are expected to be
on the network but are not. It is assumed that there will be only one new device on the network that is
listening for a response from a BootP server, and that one will get the IP address selected.
 Document number 96780739 Page 499 of 544
Revision 1

Controller

STUDENT NOTES:
 Document number 96780739 Page 500 of 544
Revision 1

Status Window / Dashboard

STUDENT NOTES:

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
 Document number 96780739 Page 501 of 544
Revision 1

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.
 Document number 96780739 Page 502 of 544
Revision 1

Log Manager Viewer

STUDENT NOTES:

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.)
 Document number 96780739 Page 503 of 544
Revision 1

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.

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.
 Document number 96780739 Page 504 of 544
Revision 1

Restart JVM

STUDENT NOTES:

Warning – Don’t restart while tool is running and/or owned.

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 therefore 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

 Document number 96780739 Page 505 of 544
Revision 1

Flash Applicom Card

STUDENT NOTES:

Do not flash the Applicom card on a tool that is in use – this 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, then click Log in to display the current tool’s
Flash Applicom Card page.
 Document number 96780739 Page 506 of 544
Revision 1

Click Proceed.

Note: Only to be carried out under instruction at Level 0

Beckhoff Flasher

http://sps.nov.com/pmwiki/flashImages/Flasher.img.gz

This will flash a generic single card configuration to the Applicom cards when it boots.

A new Applicom card for a Beckhoff SBC doesn't come from the factory already flashed (Advantech
flashes the cards in the SBCs we get from them before they ship them). The lights on the Applicom card
won't be blinking and a tool that tries to access the Profibus network may take a very long time to boot or
not boot at all. This flash doesn't run a controller or a web server; it is only intended to initialize the
unflashed Beckhoff version Applicom cards.

To use this image simply burn it to a Compact Flash card (256 MB or greater), insert it in the SBC, and wait
for the lights on the Applicom card to start blinking. It shouldn't take longer than 5 minutes, if so you may
have a bad SBC or Applicom card. Then pull the power and replace the flash with the tool flash. Once the
tool is running, the Applicom card will need to be reflashed with the tool configuration.
 Document number 96780739 Page 507 of 544
Revision 1

Flash Applicom Card

STUDENT NOTES:

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, 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
 Document number 96780739 Page 508 of 544
Revision 1

Restart Controller

STUDENT NOTES:

Warning – Don’t restart while tool is running and/or owned.

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.
 Document number 96780739 Page 509 of 544
Revision 1

Operator Pages

STUDENT NOTES:

Click Operator Pages to display the standard HTML operator tool pages. A typical Racker page is shown
here.

Operator pages are not covered in the Amphion training except to explain the approach to identifying and
troubleshooting signal paths. Refer to product family training, service manuals, functional design
specifications, commissioning documents and user manuals for operation guidance.
 Document number 96780739 Page 510 of 544
Revision 1

Documentation

STUDENT NOTES:

As with the Wiki, documentation stored on controllers may be out of date. Refer to controlled documents
in Team Centre and RigDoc whenever possible.

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.

Document number 96780739 Page 511 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 512 of 544
Revision 1

Lesson Review

STUDENT NOTES:
Document number 96780739 Page 513 of 544
Revision 1

Management of Change

STUDENT NOTES:
 Document number 96780739 Page 514 of 544
Revision 1

Lesson Objectives

STUDENT NOTES:
Document number 96780739 Page 515 of 544
Revision 1

Available Documentation

STUDENT NOTES:
 Document number 96780739 Page 516 of 544
Revision 1

SPS

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
 Document number 96780739 Page 517 of 544
Revision 1

SPS – Documentation

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
 Document number 96780739 Page 518 of 544
Revision 1

ASN

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
 Document number 96780739 Page 519 of 544
Revision 1

Amphion_Links

On the RHS we have several Amphion_Links

Varball Server takes you to SPS

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

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
 Document number 96780739 Page 520 of 544
Revision 1

Old Wiki

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

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
 Document number 96780739 Page 521 of 544
Revision 1

New Wiki

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

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
Document number 96780739 Page 522 of 544
Revision 1

Teamcenter – eng.nov.com

STUDENT NOTES:
 Document number 96780739 Page 523 of 544
Revision 1

Rig Doc / Rig Office

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 organized 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 color 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
 Document number 96780739 Page 524 of 544
Revision 1

Recent Cases
Listed here are cases which you have accessed previously, allows easy navigation back to view a particular
case
Favorite Cases
Individual cases can be manually added to your favorites, 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
 Document number 96780739 Page 525 of 544
Revision 1

Drawings / Manuals – Topology – Block Diagrams

STUDENT NOTES:

Reference Document
11033026-DIA
11405400-DIA
 Document number 96780739 Page 526 of 544
Revision 1

Drawings / Manuals – Cable Schedule – Cause and Effect Diagram

STUDENT NOTES:

Reference Document
11405402-IDX
11405486-IDX
 Document number 96780739 Page 527 of 544
Revision 1

Drawings / Manuals – Data Sheets - Interconnect

STUDENT NOTES:

Reference Document
11405401-DIA
 Document number 96780739 Page 528 of 544
Revision 1

Drawings / Manuals – IP List – Function Design Specification

STUDENT NOTES:

Reference Document
11033026-DIA
16502058-FDS
Document number 96780739 Page 529 of 544
Revision 1

Drawings / Manuals – FAT – General Arrangement

STUDENT NOTES:

Reference Document
10629862-GAD
11405403-PRO
 Document number 96780739 Page 530 of 544
Revision 1

Drawings / Manuals – Schematic Diagram – Spare Parts

STUDENT NOTES:

Reference Document
11405404-SPL
11405407-DIA
 Document number 96780739 Page 531 of 544
Revision 1

Drawings / Manuals – Supplier Master Document List – Technical Document

STUDENT NOTES:

Reference Document
D801001614-SPC-001
 Document number 96780739 Page 532 of 544
Revision 1

Drawings / Manuals – User Manual – Wiring Diagram

STUDENT NOTES:

Reference Document
11405405-DIA
16567212-FDD
Document number 96780739 Page 533 of 544
Revision 1

Software Handling

STUDENT NOTES:
 Document number 96780739 Page 534 of 544
Revision 1

Software Handling

STUDENT NOTES:

Software is used to write code which is then executed by the firmware. Code and software are often
used interchangeably and within NOV software is used more often than not to describe code.

There are many NOV documents associated with software management of change and there are
initiatives to try and streamline the process. Always ensure you are aware which process is being followed
before commencing any work with software changes or upgrades and seek clarification on any steps, if
required, before commencing work. Tuning and minor changes may fall under management of change –
familiarize yourself with the processes governing changes on the type of control system you are working
on.

An example of a SMOC (Software Management of Change) process document

URL:rdo:documentprop=94398719

Follow software backup guidelines for the specific product line

Always document changes according to the product line.
• What was changed?
• Why was it changed?
• How was it verified?

Reason: To keep track of changes make sure not more than one person is making changes to the same
code at the same time.
 Document number 96780739 Page 535 of 544
Revision 1

SMOC

STUDENT NOTES:

SCOPE
The purpose of this procedure is to outline the responsibilities of all Rig Systems Aftermarket personnel
tasked with working on any NOV control system or tool controller to ensure accurate software version
control is implemented and maintained. This procedure governs the employment of the Software
Management of Change (SMOC) Form used to document the NOV Engineering approval, client’s review,
approval, installation, testing and acceptance of software changes.
Details herein also clearly define how and when to create backups, where to store backup software, how
to use backup software and how to use backup software for restoration of a control system if necessary.
Note that the various NOV Engineering groups maintain overall responsibility for source code for their
area and this document is intended to be a supplement to existing processes in place for those
Engineering groups.

RESPONSIBILITIES
All products in NOV have an “Engineering Responsible” defined in the Master Product Hierarchy (ref:
https://tracker.nov.com/emp/Equipment/EquipmentModelList.aspx) The “Product Engineering
Responsible” person for each product is responsible for the product’s design and the entire product’s
lifecycle. This includes the software “Engineering approval” in this process is defined as approval from the
“Engineer Responsible” for the specific product model or from the personnel/group with delegated
authority. Delegated authority may be granted to other Engineering departments, Field Engineering
and/or Technical Support groups or persons.
 Document number 96780739 Page 536 of 544
Revision 1

NOV Aftermarket Field Service and eHawk Remote Support Engineers/Technicians have responsibility to
ensure backups are taken as needed, and any code (parameter) changes are copied and provided back to
the appropriate Engineering group as needed.
NOV Aftermarket service personnel and their managers are responsible for ensuring this procedure is
followed.
NOV Aftermarket Service Vice Presidents have responsibility for this procedure.

SOFTWARE CHANGE DEFINITIONS AND APPROVAL REQUIREMENTS

Defining or classifying software change complexity and corresponding approval requirements will not
always be clear cut.
In principle, software changes should not be performed without NOV engineering approval.
The table above (full detail within the Reference Document) classifies and defines software changes, and
specifies requirements for engineering authorization to perform required modifications.
 Document number 96780739 Page 537 of 544
Revision 1

Sourcing of Correct Software

STUDENT NOTES:

There are many NOV documents associated with software management of change and there are
initiatives to try and streamline the process. Always ensure you are aware which process is being followed
before commencing any work with software changes or upgrades and seek clarification on any steps, if
required, before commencing any work.

After checking with the Project Manager or the engineer responsible for the project you are working on,
you should know which software is required. For varball SBCs it is necessary to access the NOV Varball
Server: http://sps.nov.com. (If you do not already have an account you will have to create one).
Prior to any troubleshooting or changes (including code updates supplied from an NOV Engineering
group), the Service Engineer or Technician will create a backup copy of the current software, this copy is
to be maintained by the Service Engineer or Technician and appropriately labelled at the date and time
when the backup was created; This backup should only be used again if the issue that prompted the need
to create the backup in the first place is unsuccessful.

Otherwise, that backup should be returned to the appropriate NOV Engineering group at the conclusion
of the job as described in the relevant group’s software control procedures or policies.
 Document number 96780739 Page 538 of 544
Revision 1

Amphion Software Components

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:

 Document number 96780739 Page 539 of 544
Revision 1

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.

Platform - the Operating System and lower level driver interfaces (platform_version.tar.gz).

Base Layout - the file system and start-up scripts (baselayout_version.tar.gz).

Controller - the Java parent classes for communications protocols, alarming, logging, and tools
(controller_version.tar.gz).

WWW - the Java parent classes for the user interface, HMI communication, diagnostics, and screen
navigation (www_version.tar.gz).
 Document number 96780739 Page 540 of 544
Revision 1

Points of Contact

STUDENT NOTES:
 Document number 96780739 Page 541 of 544
Revision 1

Points of Contact (POC)

STUDENT NOTES:

UK tech support
Use RigDoc form 95172810 to report issues
Office hours +44 (0)1382 735 300
Outside office hours (urgent issues) UK Tech Support (Mechanical/PCE) +44(0)7711 415 485
UK Tech Support (Electrical) +44(0)7711 415 484
 Document number 96780739 Page 542 of 544
Revision 1

Redlines

STUDENT NOTES:
 Document number 96780739 Page 543 of 544
Revision 1

Redlines Documents

STUDENT NOTES:

Redlines: capturing ‘as-is’ information (earlier changes not caught in documents or documents incorrect)
or showing changes made, following suitable approval from tech support or engineering.
A copy of the redlined document(s) should be left when departing the installation and a copy returned to
NOV ASAP (ideally email before departure in case it is required while travelling).
Local procedures for approval of redlines and updating of master copies may vary – ensure you are
familiar with the process at your location.
Document number 96780739 Page 544 of 544
Revision 1

Lesson Review