Permanent Software

Changes

Copyright 2020 Baker Hughes Company. All rights reserved. The information contained in this document is company confidential and proprietary
property of Baker Hughes and its affiliates. It is to be used only for the benefit of Baker Hughes and may not be distributed, transmitted,
reproduced, altered, or used for any purpose without the express written consent of Baker Hughes.
Objectives

• Learn how to make permanent software

changes to the MarkVIe controller

• Learn how to make a change to a control

constant permanent

Confidential. Not to be copied, distributed, or reproduced without prior approval.

2
Overview

•To make a software change permanent we must

• Change the Software
• Build the Software
• Download the Software

Confidential. Not to be copied, distributed, or reproduced without prior approval.

3
 Making Software Changes
•In most cases you may select an object in the tree or
summary view of the component editor, then make any
changes in the properties view.

•To make a permanent constant change

• Select the signal name in the component editor

Confidential. Not to be copied, distributed, or reproduced without prior approval.

4
Making Software Changes –2
• Select the where used tab in the component info
view area

> Double click on the first result (pin Variable)

Confidential. Not to be copied, distributed, or reproduced without prior approval.

5
 Making Software Changes –3
•In the properties area change the initial value to the
value desired

Confidential. Not to be copied, distributed, or reproduced without prior approval.

6
 Build MarkVIe application Code
•The build icon in the component editor creates several
binary files which are the application code layer of
software for the controller.

A build will result in a major or minor difference

between the controller application software and
ToolboxST application software.

Confidential. Not to be copied, distributed, or reproduced without prior approval.

7
 Build MarkVIe application Code –2
•The determination of what level application software
changes comprise a major or minor difference is
decided by ToolboxST.

•Major Difference – the controller will automatically

be rebooted after the download

Minor Difference – the controller doesn’t need to be

restarted . The controller will start using the new
software without a reboot after the download
Confidential. Not to be copied, distributed, or reproduced without prior approval.

8
Major Difference Criteria
• Adding the first I/O pack to a controller, removing the last I/O module,
or deleting all I/O modules
• Compressing variables\non-volatile RAM (NovRAM)
• Changing the background blockware period\ frame rate
• Changing controller redundancy\ IONet network redundancy
• Changing the platform type
• Changing any NTP configuration
• Changing any controller Network Adapter IP addresses, subnet mask,
gateway IP address, scope, media, or transport
• Delete or rename a Network Adapter that the controller was using
• Adding or redirecting optional block library references
• Changing Frame state timeouts
• Removing last point off Modbus slave
• Adding the first FOUNDATION Fieldbus linking device,
removing the last FOUNDATION Fieldbus device, or removing all
FOUNDATION Fieldbus devices.
Confidential. Not to be copied, distributed, or reproduced without prior approval.

9
Downloading to Controller
The ToolboxST application is used to configure both a Mark VIe component and its
distributed I/O modules. Both the component and the I/O modules have four items
of software that can be downloaded :
• Boot Loader: to configure Controller IP address and starts the OS. Changes are
infrequent
• Base Load contains the operating system for the controller and I/O modules.
Changes are infrequent.
• Firmware provides the functionality of the controller and I/O modules. It can be
updated over the lifetime of the controller to incorporate new features and bug
fixes.
• Application Code contains the configuration of the controller as created in the
ToolboxST application. Whenever a change is made to the configuration, the
application code must be downloaded. There are two types of application code
download, online and offline. An online download, which is common, changes the
configuration without interrupting control; the new configuration takes effect
between control frames. An offline download requires a controller restart, and is
much less frequent. The type of download needed is determined by the types of
changes that have been made to the controller configuration.

Confidential. Not to be copied, distributed, or reproduced without prior approval.

10
 Downloading Software
•In the component editor select the download icon

The download wizard appears –follow the prompts

The download wizard checks
the controller and IOPacks to
see if any software needs to be
downloaded. The not equal
sign is the software that will be
downloaded. You may force a
download by checking the box
in the download wizard
Confidential. Not to be copied, distributed, or reproduced without prior approval.

11
Downloading Software

Confidential. Not to be copied, distributed, or reproduced without prior approval.

12
 Downloading Software

When the download has completed, click Finish to close the wizard. In the
Component InfoView, click the Log tab and review the status messages to check
For potential warnings or errors that may have occurred during the download

Confidential. Not to be copied, distributed, or reproduced without prior approval.

13
 Verifying Changes
•Verify that the controller is equal in the component
editor Status Tab

Verify that the controller is in the controlling state

Verify that the software change produced the
desired result.

Confidential. Not to be copied, distributed, or reproduced without prior approval.

14