Experion MX MD Controls R700.1 Traditional Control: Configuration and System Build Manual

Experion MX MD Controls
R700.1 Traditional Control

Configuration and System Build Manual
6510020582 Rev 00
Configuration and System
Build Manual
March, 2017
Confidentiality Statement
This manual is a product of Honeywell. It is intended for use only by Honeywell and customer personnel in connection with
Honeywell products. It is strictly prohibited to copy this manual or any part thereof or to transfer this manual or any part
thereof to any non-Honeywell person or entity, except customer personnel for use in connection with Honeywell products.
Persons employed by a third-party service company shall not have access to this manual.
Notice
All information and specifications contained in this manual have been carefully researched and prepared according to the best
efforts of Honeywell, and are believed to be true and correct as of the time of this printing. However, due to continued efforts
in product improvement, we reserve the right to make changes at any time without notice.
Trademarks
All trademarks and registered trademarks are the properties of their respective holders.
Copyright
© 2017 Honeywell
500 Brooksbank Avenue, North Vancouver, BC Canada V7J 3S4
All rights reserved. No part of this publication may be reproduced or translated, stored in a database or retrieval system, or
transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior
written permission of Honeywell.
Table of Contents
Introduction ................................................................................................................................... v
Audience ..................................................................................................................................... v
About This Manual .................................................................................................................... vi
Related Reading ......................................................................................................................... vi
Conventions ............................................................................................................................... vi
1. MD Traditional Control Overview ...................................................................................... 1-1

1.1. Software Components ................................................................................................... 1-1
1.2. RTDR Database Structure ............................................................................................. 1-1
1.3. Configuration & Build Code ......................................................................................... 1-2
1.4. Application Code .......................................................................................................... 1-2
1.5. System Configuration and Build Overview .................................................................. 1-3
2. MD Traditional Control Configuration and Build Process .............................................. 2-1

2.1. Build & Load Configuration Environment ................................................................... 2-1
2.2. Import and Translate System Setup File ....................................................................... 2-2
2.3. Adding MD Traditional Control Objects ...................................................................... 2-3
2.4. Export DRG File ........................................................................................................... 2-3
2.5. Build RTDR Load Files ................................................................................................ 2-3
3. MD Traditional Control Configuration Components ....................................................... 3-1

3.1. Configuration Macros ................................................................................................... 3-1
3.2. Configuration Hierarchy ............................................................................................... 3-2
3.3. General Instructions ...................................................................................................... 3-2
3.3.1. General HMI Configuration: controldisplayline ............................................... 3-3
3.4. Configuration Objects ................................................................................................... 3-4
3.4.1. PerformanceMDCtlPkg..................................................................................... 3-5
3.4.1.1. Attributes ...................................................................................................... 3-5
3.4.1.2. Child Objects ................................................................................................ 3-5
P/N 6510020582 Rev 00 3/9/17 i

Configuration and System Build Manual Table of Contents
3.4.2. PerfMDControl ................................................................................................. 3-5

3.4.2.1. Child Objects ............................................................................................... 3-6
3.4.3. MDCtlPkg ......................................................................................................... 3-7
3.4.3.1. Attributes...................................................................................................... 3-7
3.4.3.2. Option Mask................................................................................................. 3-8
3.4.3.3. Child Objects ............................................................................................... 3-8
3.4.4. MDVariable ...................................................................................................... 3-9
3.4.4.1. Attributes...................................................................................................... 3-9
3.4.4.2. Option Mask............................................................................................... 3-10
3.4.4.3. Child Objects ............................................................................................. 3-10
3.4.5. BrokeFlowFFwd ............................................................................................. 3-11
3.4.5.1. Attributes.................................................................................................... 3-11
3.4.6. BasisWeightData ............................................................................................ 3-11
3.4.6.1. Attributes.................................................................................................... 3-11
3.4.6.2. Option Mask............................................................................................... 3-12
3.4.7. AshData .......................................................................................................... 3-12
3.4.7.1. Attributes.................................................................................................... 3-13
3.4.8. AshInStockFfwd ............................................................................................. 3-13
3.4.8.1. Attributes.................................................................................................... 3-13
3.4.8.2. Child Objects ............................................................................................. 3-13
3.4.9. GlossCtlCascade ............................................................................................. 3-13
3.4.10. GlossCoupling ................................................................................................ 3-13
3.4.11. DistributeDecouple ......................................................................................... 3-14
3.4.12. VIO (in MDCtlPkg) ........................................................................................ 3-14
3.4.13. RatioBiasControl (in MDCtlPkg) ................................................................... 3-14
3.4.14. ControlLoop (in MDCtlPkg) .......................................................................... 3-14
3.4.15. MDPackage ..................................................................................................... 3-15
3.4.15.1. Attributes.................................................................................................. 3-15
3.4.16. Drystock .......................................................................................................... 3-15
3.4.16.1. Attributes.................................................................................................. 3-16
3.4.16.2. Child Objects ........................................................................................... 3-16
3.4.17. HeadboxCtlPkg ............................................................................................... 3-16
3.4.17.1. Attributes.................................................................................................. 3-18
3.4.17.2. Option Mask............................................................................................. 3-19
3.4.17.3. Child Objects ........................................................................................... 3-19
3.4.18. JetToWire........................................................................................................ 3-20
3.4.18.1. Attributes.................................................................................................. 3-20
3.4.18.2. Child Objects ........................................................................................... 3-20
3.4.19. TotalheadIOData ............................................................................................. 3-21
3.4.19.1. Attributes.................................................................................................. 3-21
3.4.20. HbxCons ......................................................................................................... 3-21
3.4.20.1. Attributes.................................................................................................. 3-22
3.4.20.2. Child Objects ........................................................................................... 3-22
3.4.21. VIO (in HeadboxCtlPkg) ................................................................................ 3-22
3.4.22. ShutDownPkg (in PerfMDControl) ................................................................ 3-22
3.4.22.1. Attributes.................................................................................................. 3-23
ii 3/9/17 P/N 6510020582 Rev 00
3.4.22.2. Child Objects ............................................................................................ 3-23

3.4.23. ShutDownSection............................................................................................ 3-23
3.4.23.1. Attributes .................................................................................................. 3-24
3.4.23.2. Option Mask ............................................................................................. 3-24
3.4.23.3. Child Objects ............................................................................................ 3-24
3.4.24. Break ............................................................................................................... 3-24
3.4.24.1. Attributes .................................................................................................. 3-24
3.4.25. Crepe ............................................................................................................... 3-25
3.4.25.1. Attributes .................................................................................................. 3-25
3.4.25.2. Child Objects ............................................................................................ 3-25
3.4.26. Multiply........................................................................................................... 3-25
3.4.26.1. Attributes .................................................................................................. 3-26
3.4.26.2. Option Mask ............................................................................................. 3-26
3.4.26.3. Child Objects ............................................................................................ 3-26
3.4.27. MPlySheetWidth ............................................................................................. 3-27
3.4.27.1. Attributes .................................................................................................. 3-27
3.4.28. PlyData ............................................................................................................ 3-27
3.4.28.1. Attributes .................................................................................................. 3-28
3.4.29. FurnishData ..................................................................................................... 3-28
3.4.29.1. Attributes .................................................................................................. 3-28
3.4.30. ControlLoop (in Multiply) .............................................................................. 3-28
3.4.31. Ratio ................................................................................................................ 3-29
3.4.31.1. Attributes .................................................................................................. 3-30
3.4.31.2. Child Objects ............................................................................................ 3-30
3.4.32. Bias.................................................................................................................. 3-30
3.4.32.1. Attributes .................................................................................................. 3-31
3.4.32.2. Child Objects ............................................................................................ 3-31
3.4.33. Midrange ......................................................................................................... 3-31
3.4.33.1. Attributes .................................................................................................. 3-32
3.4.33.2. Child Objects ............................................................................................ 3-32
3.4.34. Feedforward .................................................................................................... 3-32
3.4.34.1. Attributes .................................................................................................. 3-33
3.4.34.2. Child Objects ............................................................................................ 3-33
3.4.35. MDCommonPkg ............................................................................................. 3-33
3.4.35.1. Child Objects ............................................................................................ 3-34
3.4.36. MDGradeChange ............................................................................................ 3-35
3.4.36.1. Attributes .................................................................................................. 3-35
3.4.37. WeightConversion .......................................................................................... 3-35
3.4.37.1. Attributes .................................................................................................. 3-35
3.4.38. ProductionRate ................................................................................................ 3-36
3.4.38.1. Attributes .................................................................................................. 3-36
4. MD Traditional Control Testing.......................................................................................... 4-1

4.1. Loading RTDR .............................................................................................................. 4-1
4.2. Full System Testing ...................................................................................................... 4-1
P/N 6510020582 Rev 00 3/9/17 iii

5. Glossary ................................................................................................................................. 5-1
List of Figures
Figure 3-1 MD Traditional Control Configuration Hierarchy ................................................................. 3-2
Figure 3-2 Template Help ...................................................................................................................... 3-17
Figure 3-3 Headbox Control Object ...................................................................................................... 3-18
Figure 3-4 Control Loop Object for Multiply........................................................................................ 3-29
Figure 3-5 MD Common Package Object ............................................................................................. 3-34
iv 3/9/17 P/N 6510020582 Rev 00

Introduction
Experion MX MD Controls R700.1 is the machine direction (MD) control

software for paper-making processes, which runs on Honeywell quality control
system (QCS) Experion MX release version R700 or higher, as an optional
advanced control package. It is released on a separate single media (DVD) titled
Experion MX MD Controls R700.1.
Experion MX MD Controls provides two control options – MD Multivariable

(MDMV) Control and MD Traditional Control. A system must be installed with
only one of the two control options.
This manual provides information and instructions on how to configure and build
an Experion MX QCS system with the Traditional Control option in Experion
MX MD Controls R700.1.
All references to MD Controls in this document are to Experion MX MD Controls

R700.1 unless otherwise specified.
All references to MD Traditional Control or Traditional Control in this document are to

Experion MX MD Controls R700.1 Traditional Control unless otherwise specified.
Audience
This manual is intended for use by Honeywell software control engineers (SCEs)
and site service representatives who are responsible for configuring and building
the MD Traditional Control systems. It is assumed that the reader is familiar with
MD control concepts and the QCS in general.
P/N 6510020582 Rev 00 3/9/17 v

Introduction
About This Manual

This manual contains five chapters.
Chapter 1, MD Traditional Control Overview, provides an overview of the

software components, the Real-Time Data Repository (RTDR), the file
structure and the configuration and build process of MD Traditional Control.
Chapter 2, MD Traditional Control Configuration and Build Process,

describes the steps used to configure and build a MD Traditional Control
system.
Chapter 3, MD Traditional Control Configuration Components, describes

the definitions and details of the configuration objects in MD Traditional
Control.
Chapter 4, MD Traditional Control Testing, describes the high-level

approach for verifying a successful MD Traditional Control system build.
Chapter 5, Glossary, defines the terms and acronyms used in this manual.
Related Reading
The following documents contain related reading material.
Honeywell Part Document Title / Description
Number
6510020599 Real-Time Application Environment (RAE) R700.1 for Experion
PKS R500.1 Software Change Notice
6510020594 Real-Time Application Environment (RAE) R700.1 for Experion
PKS R500.1 Release and Installation Notes
6510020590 Experion MX MD Controls R700.1 Software Change Notice
6510020585 Experion MX MD Controls R700.1 Automatic Grade Change
Control User Manual
Conventions
The following conventions are used in this manual:
Text may appear in uppercase or lowercase except as specified in these conventions.
Boldface Boldface characters in this special type indicate your input.

vi 3/9/17 P/N: 6510020582 Rev 00
Introduction Conventions
Special Type Characters in this special type that are not boldfaced indicate system prompts,
responses, messages, or characters that appear on displays, keypads, or as menu
selections.
Italics In a command line or error message, words and numbers shown in italics represent
filenames, words, or numbers that can vary; for example, filename represents any
filename.
In text, words shown in italics are manual titles, key terms, notes, cautions, or
warnings.
Boldface Boldface characters in this special type indicate button names, button menus, fields
on a display, parameters, or commands that must be entered exactly as they
appear.
lowercase In an error message, words in lowercase are filenames or words that can vary. In a
command line, words in lowercase indicate variable input.
Type Type means to type the text on a keypad or keyboard.
Press Press means to press a key or a button.
[ENTER] [ENTER] is the key you press to enter characters or commands into the system, or
or [RETURN] to accept a default option. In a command line, square brackets are included; for
example:
SXDEF 1 [ENTER]
[CTRL] [CTRL] is the key you press simultaneously with another key. This key is called
different names on different systems; for example,
[CONTROL], or [CTL].
[KEY-1]-KEY-2 Connected keys indicate that you must press the keys simultaneously; for example,
[CTRL]-C.
Click Click means to position the mouse pointer on an item, then quickly depress and
release the mouse button. This action highlights or “selects,” the item clicked.
Double-click Double-click means to position the mouse pointer on an item, and then click the item
twice in rapid succession. This action selects the item “double-clicked.”
Drag X Drag X means to move the mouse pointer to X, then press the mouse button and
hold it down, while keeping the button down, move the mouse pointer.
Press X Press X means to move the mouse pointer to the X button, then press the mouse
button and hold it down.
The attention icon appears beside a note box containing information that is
important.
The caution icon appears beside a note box containing information that cautions you
about potential equipment or material damage.
The warning icon appears beside a note box containing information that warns you
about potential bodily harm or catastrophic equipment damage.
P/N 6510020582 Rev 00 3/9/17 vii

1. MD Traditional Control Overview
The Traditional Control option in Experion MX MD Controls provides MD

control using the traditional single-input-single-output controllers. It also provides
a collection of supplementary functions, such as automatic grade change control,
feed-forward control, ratio control, bias control, dry stock control, multiply
control, coordinated speed change control, headbox control, shutdown/restore
control, gain and delay retune function, and so on.
1.1. Software Components

The main software components that make up the MD Traditional Control package
are:
• Real-Time Data Repository (RTDR) configuration and build macro

files
• DLLs, executable and LabVIEW VIs for control functions
• HMIWeb and LabVIEW human machine interfaces (HMIs)
1.2. RTDR Database Structure

The MD Traditional Control RTDR database structure is created when a QCS
system is configured and built with the MD Traditional Control package. The
database structure varies with the number and types of MD Traditional Control
objects configured, such as the number of control loops, the type of Distributed
Control System (DCS) link, the optional packages, and so on.
MD Traditional Control adds the following top-level database records to the

RTDR:
P/N 6510020582 Rev 00 3/9/17 1-1

Configuration and System Build Manual MD Traditional Control Overview
• Process setup definitions for MD Control are located under ./Process

setup
• Records of top-level VIs to be called by RAE scheduler are under

./Application packages/Base system/Event setup/{event
name}/Control/Event objects
• Records of top-level VIs to be called upon system startup are under

./Application packages/Md control/VI list
• Records of human machine interfaces (HMIs) are located under

./Application packages/Md control/Displays
• Supervisory control loop records and direct digital control (DDC) loop
records are located under ./Controls/Control loops
• Remote controller regulatory loop records are located under

./Controls/Remote controllers
• MD Control function parameters and records are located under ./Md

control
1.3. Configuration & Build Code

The files that define the configuration objects and build the required RTDR
structure for MD Traditional Control are located under C:\Program Files
(x86)\Honeywell\Experion MX\Quantum\DRGeneration and its subdirectories.
These files contain the following components:
• Configuration object definitions and templates
• Configuration object rules
• Cruncher build macros
1.4. Application Code

The algorithm and HMI code for MD Traditional Control are mainly located in
these directories:
• C:\Program Files (x86)\Honeywell\Experion MX\MD

Controls\Common and its subdirectories
1-2 3/9/17 P/N: 6510020582 Rev 00

MD Traditional Control Overview System Configuration and Build Overview
• C:\Program Files (x86)\Honeywell\Experion MX\MD

Controls\Performance MD and its subdirectories
• C:\Program Files (x86)\Honeywell\Experion PKS\RAE\Displays and

its subdirectories
1.5. System Configuration and Build Overview

Provided that Experion MX (RAE) QCS and Experion MX MD Controls
Traditional Control option are installed already, the high-level process in creating
a MD Traditional Control system is:
1. On the Experion MX QCS server, use the Configuration Browser

provided by RAE to build and load the configuration environment to
include MD Traditional Control configuration objects, templates and
rules.
2. Configure the MD Traditional Control top-level objects and all

required child objects. Alternately, import an existing system
configuration (DRG) file containing MD Traditional Control.
3. Export the system configuration (DRG) file.
4. Build the RTDR load files for the MD Traditional Control system.
5. Copy the RTDR load files from the server to all operator stations.
6. Start up the server and operator stations. MD Traditional Control runs

as one of the applications.
Due to possible changes in configuration objects and templates, an existing system

configuration (DRG) file may not be completely migrated to the new configuration
environment when imported into the RAE Configuration Browser. In this case, the
DRG file may need to be modified before the import, or some configuration objects
may need to be added, deleted, or modified after the import.
P/N 6510020582 Rev 00 3/9/17 1-3

2. MD Traditional Control Configuration
and Build Process
The system configuration and build process is required to generate the portion of
the RTDR for MD Traditional Control. Configuration of scanners, measurements
and virtual input/outputs (VIO) must be completed prior to configuring MD
Traditional Control. Follow the steps in the subsequent sections to configure and
build the MD Traditional Control system.
2.1. Build & Load Configuration Environment

The RAE configuration browser must have a configuration environment loaded
after MD Traditional Control has been installed. This environment contains all of
the configuration object definitions and templates that can be added to the system
configuration.
On loading the configuration environment, the configuration rules files are loaded
and become active. Some of those rules are provided by RAE, and others by MD
Traditional Control. The rules automate certain parts of the configuration, and
ensure that the objects are configured correctly by providing warning messages or
forbidding incorrect configuration.
Follow these steps to build and load the configuration environment:
1. In the RAE configuration browser, select Options… from the View

menu.
2. Ensure that under the General tab, the Configuration Environment

option is set to Standard Da Vinci Configuration Environment.
3. On the same tab, check that the Config DR Size (MB) is set to 64 to
accommodate the number of configuration objects and templates. The
P/N 6510020582 Rev 00 3/9/17 2-1

Configuration and System Build Manual MD Traditional Control Configuration and Build Process
config DR size may need to be increased further if there are a large

number of configuration objects and templates involved.
4. Verify that the folders and files under the User Defined Settings tab
are correctly set.
5. From the File menu, select the Build & Load Config Environment
option to load the configuration object definitions, templates and rules.
2.2. Import and Translate System Setup File

Often there will be a starting system configuration (system setup) file, referred to
as the DRG file, which defines the top-level configuration of a system prior to the
addition of the MD Traditional Control objects. When upgrading an existing MD
Traditional Control system, this configuration file already contains configuration
objects of an earlier version of MD Traditional Control. Before an existing DRG
file can be imported into the RAE configuration browser, it may need to be
translated (change of DRG level) and then retranslated (change of individual
object versions).
DRG files created in RAE version 2.00 or earlier are at DRG level 19 or lower. They
need to be translated up to DRG20 level by selecting the Translate System Setup
File option from the Cruncher menu. The DRG revision level is incremented by
one during each translation, so this operation may have to be repeated a number
of times to get the file to the DRG20 level.
The DRG file will need to be retranslated if the versions of the MD Traditional
Control objects are older than those in the current MD Traditional Control.
Retranslation is automatically done when you import the DRG file.
The DRG file can then be imported into the configuration environment by
selecting the Import System Setup File option from the Cruncher menu.
2-2 3/9/17 P/N: 6510020582 Rev 00
MD Traditional Control Configuration and Build Process Adding MD Traditional Control Objects
2.3. Adding MD Traditional Control Objects

The addition of MD Traditional Control into a DRG file should begin with the
addition of the top-level object named PerformanceMDCtrlPkg. Child objects are
then added under this top-level object depending on the number of control loops
and control packages required, etc. Refer to Chapter 3 for details on the MD
Traditional Control configuration objects.
2.4. Export DRG File

After the MD Traditional Control objects have been added and configured, the
DRG file must be first saved by selecting the Export System Setup File option
from the Cruncher menu.
2.5. Build RTDR Load Files

The RTDR load files are text files used by the RAE database browser to load the
RTDR for a system. The DRG file is used in conjunction with the build macros to
generate these text files to create the RTDR. The top-level build file for MD
Traditional Control is PerfMD_includes.mac. This file calls the rest of the MD
build macros. The MD RTDR build macros are located in the directory
C:\Program Files (x86)\Honeywell\Experion MX\Quantum\DRGeneration\Build.
After the DRG file is exported, the RTDR can be built by selecting the Build DR
Load Files for SysXXXX (where XXXX is the system number) option from the
Cruncher menu. The RTDR will be loaded into memory when the Experion MX
(RAE) QCS starts up. To make sure the RTDR generated can be loaded without
any problems, you can manually load the RTDR using the RTDR database
browser or RAE browser before starting up RAE.
P/N 6510020582 Rev 00 3/9/17 2-3

3. MD Traditional Control Configuration
Components
The MD Traditional Control configuration environment are made up of

configuration macros, template macros and rules. The configuration macros
contain the definitions of the configuration objects. The templates are pre-
configured objects that have been customized for typical cases. The rules are for
automating some of the configuration and checking the correctness of the
configuration objects by providing warnings or forbidding incorrect entries.
3.1. Configuration Macros

The top-level configuration macro is performancemdsuite_CfgIncludes.mac,
which is loaded by the RAE CfgIncludes.mac. This top-level file and the rest of
the MD Traditional Control configuration macros are located in the directory
C:\Program Files (x86)\Honeywell\Experion
MX\Quantum\DRGeneration\ConfigDR.
The configuration rules files are located in the directory C:\Program Files
(x86)\Honeywell\Experion MX\Quantum\DRGeneration\ConfigDR\Rules.
P/N 6510020582 Rev 00 3/9/17 3-1

Configuration and System Build Manual MD Traditional Control Configuration Components
3.2. Configuration Hierarchy

The hierarchy that relates all the MD Traditional Control objects is shown in
Figure 3-1. The configuration starts with adding the 5903 MD Traditional Control
object under the PerformanceMDCtlPkgs object list.
Figure 3-1 MD Traditional Control Configuration Hierarchy
3.3. General Instructions

Here are some general guidelines for configuring the MD Traditional Control
system:
• Remote controllers/ DDC control loops must be configured first as

virtual inputs/outputs (VIOs). The VIOs configuration should be based
on the I/O list of the customer site. Measurements that are calculated
internally or come from external sources other than scanners can be
configured as analog input VIOs. The VIOs are prerequisites to many
MD Traditional Control configuration objects as they provide inputs
and outputs to supervisory control and other control packages.
• Configure the sheet quality variables to be controlled and the

corresponding DDC/regulatory loops under the mdctlpkgs list.
3-2 3/9/17 P/N: 6510020582 Rev 00
MD Traditional Control Configuration Components General Instructions
• Add optional control packages such as coordinated speed change

control and throughput maximization under the mdpackages list.
• Add optional control functions such as dry stock control, headbox

control, shutdown control, ratio control, bias control, midrange control
and feedforward control if required. DO NOT configure these
functions if they are already implemented at the VIO level or inside
the DCS.
• Configure the multiply object for multiformer machines with multiple

headboxes and plies.
• Configure the optional automatic grade change control package by

adding the parent object under the mdcommonpkgs list and the
mdgradechange and mdprocessmodel child objects.
3.3.1. General HMI Configuration: controldisplayline

There is a generic configuration object called controldisplayline for defining
control lines on various HMIs that support the control line display object. The
control line is used primarily to show a controlled variable (CV), typically a sheet
quality variable (which also represents a supervisory control loop), or a
manipulated variable (MV), typically a remote controller or DDC loop for a
physical field device that impacts one or more CVs. The operator can enter
setpoints, view current values or change the modes of the controlled variables
(CVs) or manipulated variables (MVs) through the control lines. The
controldisplayline object has the following attributes:
Display Name
The two main operator displays in MD Traditional Control are :
• MD Control display
• Headbox Control display
For MD Traditional Control, select the display name to be either Weight Control
or Headbox Control. For headbox-related controls, select Headbox Control. For
others, select Weight Control.
Each of these displays has a selection for set number (page). Each page has ten
control lines to the left of the display used for supervisory type controls, and ten
control lines to the right used for DDC/remote controllers corresponding to the
supervisory controls defined on the left.
Set Number
P/N 6510020582 Rev 00 3/9/17 3-3
This is used like a page number. For example, if there are two headbox control
packages, headbox package 1 can be defined in set 1 and headbox package 2 can
be defined in set 2.
Line Number
Control lines to the left are numbered 1 through 10, and control lines to the right
are numbered 11 through 20.
3.4. Configuration Objects

A configuration object typically has the following components:
Attributes
An attribute is a field that is used to define the characteristics of the object such as
ID, name, description, unit, and so on. An attribute can be mandatory or optional.
Option Mask
An option mask is an optional behavior definition for an object. The option mask
consists of 32 bits, allowing a maximum of 32 options for each object. The option
is selected by checking the corresponding check box on the dialog for editing
options.
Child Objects
A child object is an object contained in another object (the parent object). A child
object provides further definitions for its parent object. A configuration object can
have one or more child objects that are mandatory or optional.
A configuration object can be added from scratch by configuring all the required
components one by one. However, if an object is known to have a specific
configuration, the object can be added through the use of templates such that its
components are automatically configured. A configuration object with templates
provides a list of predefined object types to choose from when being added.
The configuration objects for MD Traditional Control are described in this

chapter. For most objects, the default entry values of their attributes are shown.
The default entry value is the one that shows up when adding the object. It is not
the value that comes with the parent object template.
3-4 3/9/17 P/N: 6510020582 Rev 00

MD Traditional Control Configuration Components Configuration Objects
3.4.1. PerformanceMDCtlPkg
At the top level of the MD Traditional Control configuration hierarchy is the
PerformanceMDCtlPkg object. There can only be one PerformanceMDCtlPkg
added to a given system.
This object consists of the child object list PerfMDControls.
There are two configured templates available for this object:
• 5903 - MD Traditional Control template
• 5903 - MD Control Green Belt template (must be used only if the

system-level object is a Green Belt 4-scanner system)
3.4.1.1. Attributes
Attribute Description
Type This attribute indicates MD Traditional Control (model number 5903).
3.4.1.2. Child Objects

• PerfMDControl: See Subsection 3.4.2.
3.4.2. PerfMDControl
This object represents the MD Traditional Control top-level object. It includes the
traditional supervisory control functions as well as these optional packages:
• Dry Stock Control
• Headbox Control
• Shutdown Control
• Crepe Control
• Multiply Control
• Ratio Control
• Bias Control
P/N 6510020582 Rev 00 3/9/17 3-5
• Midrange Control
• Feedforward Control
For the perfmdcontrol object, there are three available templates:
• DualSidedGloss - Dual Sided Supercalender Control
• SingleSidedGloss - One Sided Supercalender Control
• New (unconfigured) perfmdcontrol
The first two templates are only for supercalendar gloss control. It is
recommended that you start by adding the performancemdctlpkg template which
will automatically add the perfmdcontrol child object.
If you start from a new unconfigured performancemdctlpkg template, you will

have to add a new unconfigured perfmdcontrol object.

• MDCtlPkg: See Subsection 3.4.3
• MDPackage: See Subsection 3.4.15.
• DryStock: See Subsection 3.4.16.
• HeadboxCtlPkg: See Subsection 3.4.17.
• ShutDownPkg: See Subsection 3.4.22.
• Crepe: See Subsection 3.4.25.
• Multiply: See Subsection 3.4.26.
• Ratio: See Subsection 3.4.31.
• Bias: See Subsection 3.4.32.
• Midrange: See Subsection 3.4.33.
• Feedforward: See Subsection 3.4.34.
3-6 3/9/17 P/N: 6510020582 Rev 00

3.4.3. MDCtlPkg
There are nine configured templates available for configuring the mdctlpkg
object.
• MDCtlPkg1: one basis weight control and one moisture control.
• MDCtlPkg2: one basis weight control and two moisture controls.
• MDCtlPkg3: one basis weight control, one moisture control, and an

ash control.
• MDCtlPkg4: one basis weight control, two moisture controls, and an

ash control.
• MDCtlPkg5: two basis weight controls, two moisture controls, and an

ash control. The basis weight controls are switchable (that is, they
share the same MV and are mutually exclusive). Only one basis weight
control can be on at any given point in time during normal running
operation.
• MDCtlPkg6: two basis weight controls, two moisture controls, and an

ash control. The basis weight controls are configured for cascade-type
control.
• MDCtlPkg7: Off machine coat control with decoupled moisture.
• On machine tofcon coater: base sheet basis weight and moisture and
two coat weight (Tofcon) and moisture control.
• Onmachtofconcoaterreelbwtgt: base sheet basis weight (reel target

entry) and moisture and coat weight (Tofcon) and moisture control.
3.4.3.1. Attributes
SpeedId ID of the machine speed object (typically, VIO defined in the viomap)
This is used as the reference for speed retune.
Default = MSSpd
Name Name of the MD control package
Default = MD1
FrameNumberForDryerLimitExec Frame number associated with the moisture loop that is known to be
dryer limited. This attribute is used to define the control execution of the
dryer limit control package (Throughput Maximization Package: see
Subsection 3.4.15 MDPackage for the configuration of this package).
P/N 6510020582 Rev 00 3/9/17 3-7

Default = 1
DispLineForCoordSpd Control line number for displaying coordinated speed control in the MD
Control display. Used only if the Coordinated Speed Control package is
configured.
Default = 10
DispLineDryerLimit Control line number for displaying Throughput Max in the MD Control
display. Used only if the Throughput Max / Dryer Limit control package
is configured.
Default = 9
FinalBWControlId ID of the basis weight CV to be defined as an object in the mdvariable
object. The final basis weight control also known as the closest weight
control to the headbox is the weight control that supervises the
stockflow loop. Used in coordinated speed control and as the reference
to calculated time delay for feedforward effects of decoupled loops
(Machine speed, Stockflow and steam).
Default = BW1
FinalMoiControlId ID of the moisture CV to be defined as an object in mdvariable. The final
moisture control also known as pre-moisture control is the moisture
control that supervises the steam pressure or steam flow loop. Used in
coordinated speed control.
Default = MS1
3.4.3.2. Option Mask

FastMD
Set this option for Fast MD Control. Fast MD Control requires that the scanner
frames from which MD Control receives measurements have the option Fast Now
Event Generated For This Frame selected and that all measurements have the
options Fast Now Results and Fast MD Results selected. Verify the
configuration of the scanner frames and measurements in the Frame and
Measurement configuration objects.
OffMachine
Set this option for Non Paper Machine Control (common examples are Off
Machine Coater control application and Supercalender control).

• MDVariable: See Subsection 3.4.4.
• VIO: See Subsection 3.4.12.
3-8 3/9/17 P/N: 6510020582 Rev 00

• RatioBiasControl: See Subsection 3.4.13.
• ControlLoop: See Subsection 3.4.14.
3.4.4. MDVariable
The MDVariable object represents one traditional supervisory MD Control loop.
The generic MDVariable object is described in this chapter. Additional objects
need to be defined in the mdvariable hierarchy, depending on the type of
mdvariable being defined, such as basis weight, moisture, or ash.
3.4.4.1. Attributes
Id ID of the MD control variable

Default = BW1
Name Name/description of the MD CV
Default = Basis weight
InputId ID of the input measurement to be used for the supervisory controller
Default = BW11
InputTable Name of the RTDR table in which the input ID is to be searched
Default = Measurement
InputPath This is the RTDR path relative to the match record matching the input
ID in the input table
Default = ./last scan/now/average
The value for this attribute will be automatically assigned to: ./Fast
now/Fast Md/Average if the FastMD option is selected
Section The process section to which this control variable belongs
Default = Reel
Unit Unit of the MD CV
Default = GSM
CascadeId ID of the controller to which this supervisory MD controller should write
its output
Default = blank
If the MD variable being defined is a downstream supervisory loop
cascaded to an upstream supervisory loop, the CascadeId is the ID of
the regulatory loop that the downstream loop will supervise when the
upstream loop is not on control. For example, if the MD variable is reel
weight that supervises the size press weight, the CascadeId is the ID of
the stockflow loop. In this case, the reel weight control directly
supervises the stockflow loop when the size press weight loop is not on
control.
FrameNumberForExec Number of the scanner from which this supervisory MD controller gets
its input. If the input source is external to the Experion MX system, a
VIO needs to be defined for the measurement.
P/N 6510020582 Rev 00 3/9/17 3-9

The FrameNumberForExec will also need to be defined corresponding
to the scanner number in the external measurement system. In this
case, the end-of-scan event is created by the MD control package.
Default = 1
CascadeControlSupvCascObjId Only change this attribute if the MD supervisory controller being defined
is for cascade control. Used only when supervisory MD controller is
cascading to another supervisory MD controller. Set it with the ID of the
supervisory MD controller that this cascade control supervises.
Default = xxxx

Dynatune
Set this option flag for moisture control variable if the Dynatune feature is desired
for that moisture control variable.
Opacity control?
Set this option flag if the control variable being defined is an opacity loop. This is
used for a specific gain retune for the opacity loop to take care of a non-linear
relationship between TiO2 and opacity.
Production rate retune option
Set this option flag if a production retune is desired for gain retune for the MD
Control variable being defined.
Setpoint deviation
Set this option flag to add support for limiting the control loop set point to a
fraction or delta of the nominal. This calculation is done at recipe load time.
Participate in startup shutdown?
Set this option flag if the configuration is for off machine application with startup
and shutdown. The typical variables for supercalender are top and bottom gloss.
For off machine coater, the variables are coat weight and moisture.

• ControlDisplayLine: See Section 3.3.1.
• BrokeFlowFFwd: See Subsection 3.4.5.
• BasisWeightData: See Subsection 3.4.6.

3-10 3/9/17 P/N: 6510020582 Rev 00
• AshData: See Subsection 3.4.7.
• AshInStockFfwd: See Subsection 3.4.8.
• GlossCtlCascade: See Subsection 3.4.9.
• GlossCoupling: See Subsection 3.4.10.
• DistributeDecouple: See Subsection 3.4.11.
3.4.5. BrokeFlowFFwd
This object defines the feedforward from broke flow to MD Control variable.
Brokeflowffwd is typically defined for ash and opacity control variables.
3.4.5.1. Attributes
BrokeFlowVIOId ID of the broke flow

Default = BrokeFl
3.4.6. BasisWeightData
This object is only defined for a Basis Weight MD Variable. The basisweightdata
object collects the necessary information to compute the dry weight or
conditioned weight. Basis weight control can have operator entry in basis weight,
dry weight, or conditioned weight. The internal controller is always dry weight.
In the case of basis weight control, additional setup must be done from the MD
Control Setup and Tuning display for the mode of setpoint entry (BW, DW,
or CW).
3.4.6.1. Attributes
Moiloopid ID of the moisture control variable. This is the moisture setpoint and pv
used in the computation of the dry weight, conditioned weight.
Default = MS1
Bwmeasid ID of the basis weight measurement
Default = BW11
P/N 6510020582 Rev 00 3/9/17 3-11
Bwmeastablename Name of the table where the basis weight measurement is defined
Bwmeaspath Relative path of the data field, relative to the match record matching the
input ID in the input table
Dwmeasid ID of the dry weight measurement
Default = DW11
Dwmeastablename Name of the table where the dry weight measurement is defined
Dwmeaspath Relative path of the data field, relative to the match record matching the
Cwmeasid ID of the conditioned weight measurement
Default = CW11
Cwmeastablename Name of the table where the dry weight measurement is defined
Cwmeaspath Relative path of the data field, relative to the match record matching the
ConsistencyVIOId ID of the consistency VIO. The consistency defined here is used in the
drystock to wet stock flow conversion
Default = ConsIn

No moisture meas use nominal
Set this option flag if there is no moisture associated with this basis weight
control.
Moisture is typically required with basis weight control to calculate dry weight
because the controller for basis weight internally is dry weight. Sometimes it is
possible for there to be only basis weight gauge, in which case the controller
internally will use basis weight control. To obtain dry weight control using a
nominal moisture, set this flag in the MD Setup and Tuning display along with
the nominal value for moisture. The nominal moisture is then used in the dry
weight calculation.
3.4.7. AshData
This object defines the ash control variable. The control of ash is done in terms of
ash weight, and basis weight ID is required to calculate the ash weight (defined as
percentage of basis weight).
3-12 3/9/17 P/N: 6510020582 Rev 00
3.4.7.1. Attributes
BWLoopId ID of the Basis Weight Variable

Default = BW1
3.4.8. AshInStockFfwd
This object defines the feedforward from ash-in-stock measurement to fillerflow.
This feedforward is different from the decoupling between stockflow and
fillerflow where the ash-in-stock percentage is considered constant and fillerflow
is compensated for changes in stockflow.
3.4.8.1. Attributes
StockFlowId ID of stockflow used in calculation of the feedforward

Default = StkFl
ConsistencyId ID of thick stock consistency, also used in calculation of the feedforward
Default = ConsIn
AshInStockId ID of the VIO for ash-in-stock measurement
Default = AshInStock

3.4.9. GlossCtlCascade
This object is used by Supercalender Control.
3.4.10. GlossCoupling
P/N 6510020582 Rev 00 3/9/17 3-13

3.4.11. DistributeDecouple
3.4.12. VIO (in MDCtlPkg)

This object represents a VIO used to isolate the control features from the actual
input and output. The typical VIOs are analog inputs, digital inputs, analog
outputs, digital outputs, remote controllers, and remote measurements. If the
regulatory control loops (that is, stock flow control or steam pressure) that are
supervised by the MD Controls are implemented in the DCS system, add a remote
controller VIO. Add the VIOs under /VIOMaps/VIOs instead of MDCtlPkgs/VIOs
because VIOs may be used by other control features, and it makes more sense to
configure them at the system level.
3.4.13. RatioBiasControl (in MDCtlPkg)

This object represents the ratio bias control used when there are multiple MVs to
coordinate for the control of one CV. In this case, the MV setpoints can ratio or
offset each other by biases.
3.4.14. ControlLoop (in MDCtlPkg)

A standard object that represents a closed loop control implemented in Experion
MX. If the regulatory loop is not implemented in an external system such as a
DCS, add a control loop to handle the regulatory loop in Experion MX. This has
been referred to as a DDC loop. For example, a DDC loop can be added to control
the stock flow.
The ControlLoop has four templates:
• DDC Loop
• Supv Loop for Scanner Measurement
• TAD Loop for Scanner Measurement
• Throughput Control to VS1ddc & VL0ddc (This template includes

references to two VS1ddc and VL0ddc loops as example. The VS1ddc
represents the Master Screw Speed and VL0ddc represents the Line
Speed.)
3-14 3/9/17 P/N: 6510020582 Rev 00

3.4.15. MDPackage
This object represents any optional MD Control package such as Coordinated
Speed Control.
There are five templates available for this object:
• 09-5947-00 Coordinated Speed Change
• 09-5948-00 Throughput Maximization
• 09-5951-00 Coordinated Grade Change
• 09-5957-00 Supercalender Speed Optimization
• 09-5969-00 Off Machine Startup Shutdown
Please note that MD package 09-5951-00 Coordinated Grade Change is no

longer available, and has been replaced by the Automatic Grade Change
Control Package which is common to both MD Traditional Control and MD
Multivariable Control. To add the Automatic Grade Change Control Package,
you need to configure the MDCommonPkg object and its child objects as
described in Section 3.4.35.
3.4.15.1. Attributes
Model The model number of the package. This cannot be changed at

configuration
Default = blank
Model Description
The description of the package. This cannot be changed at configuration
Default = blank
ModelId The ID of the package. This cannot be changed at configuration
Default = blank
3.4.16. Drystock
The Drystock feature can be defined for any combination of IO types for
consistency and stock flow. In other words, the consistency can be either an
P/N 6510020582 Rev 00 3/9/17 3-15

analog input or controller, and of type remote or local. The stock flow can also be
either remote controller or local controller type.
ConsistencyVIOId ID of consistency VIO

Default = blank
StockFlowVIOId ID of stock flow VIO
Default = blank
Description Description of the DryStock Object
Default = Drystock Control
Option Mask
consistency nominal to be used?
Set this option flag if the consistency VIO defined in this drystock object is used
for basis weight control, and the consistency nominal is used for conversion from
dry stock to wet stock flow in the output of the weight controller.

3.4.17. HeadboxCtlPkg
Headbox control consists of two major controls:
• rush-drag or jet-to-wire control
• Headbox consistency control
The two templates available are:
• jet-to-wire control and headbox consistency control
• jet-to-wire control with no headbox consistency control
When selecting a template for the headboxctlpkg object, if Show Template Help
is selected, Template Help as shown in Figure 3-2 appears. This is useful in
3-16 3/9/17 P/N: 6510020582 Rev 00

determining the 2g constant used in the jet speed and total head setpoint
vioformulanode calculations.
Figure 3-2 Template Help
P/N 6510020582 Rev 00 3/9/17 3-17

The configuration shown in Figure 3-3 is for jet-to-wire control and headbox
consistency control.
Figure 3-3 Headbox Control Object
JWTgtEntryMode Target entry mode for this controller. 0 = jet-to-wire, and 1 = rush-drag
Default = 0
Id ID of the headbox control package object
Default = HBX1
JetSpeedVIOId ID of the jet speed VIO input
Default = JetSpeed
3-18 3/9/17 P/N: 6510020582 Rev 00

Both of the templates have the definition for this VIO, a local analog
input type VIO. This analog input VIO has a formula defined and has the
default formula for 2 g.h where 2g and total head are two formula
inputs. The output of the formula is the jet speed. Enter and construct
any headbox-specific formula here.
Section Name of the machine section to which this headbox object is tied. Each
machine section is an area of the paper machine that a scanner frame is
associated with.
Default = Reel
Only jet speed input needs to be computed. The system uses this jet speed
input, and computes the ratio or difference together with wire speed input for
jet-to-wire and rush-drag control, respectively.

Device switch at grade change
The headbox totalhead can be controlled by devices such as bypass valve, fan
pump, stream valve, or slice. Set this option flag if the device that controls the
totalhead is switched during a grade change (not implemented).
Total head is NOT controlled by slice
Set if total head is controlled by fan pump or stream flow or bypass valve or the
like.
Slice is the ONLY ddc available for control of total head
Set if total head is to be controlled by SLICE, and SLICE is the only actuator.

• JetToWire: See Subsection 3.4.18.
• HbxCons: See Subsection 3.4.20.
• VIO: See Subsection 3.4.21.
P/N 6510020582 Rev 00 3/9/17 3-19

3.4.18. JetToWire
This object represents either a jet-to-wire supervisory loop that controls the ratio
of jet speed to wire speed, or a rush-drag supervisory loop that controls the
difference between the jet speed and wire speed.
JWLoopId ID of the supervisory controller for jet-to-wire (or rush-drag)

Default = JW1
TotalheadLoopId ID of the total head VIO. The VIO for total head has to be defined in a
viomap.
Default = blank
WireSpeedVIOId ID of the wire speed VIO. The VIO should be defined in a viomap.
Default = blank
TotalheadSPVIOId ID of the total head setpoint VIO that is created in the headbox control
package
Default = THead1SP
There is another VIO to be defined for calculating the total head setpoint.
Because the formula for the jet-to-wire or rush-drag can be specific to a
headbox, and is not always the same, total head setpoint has to be calculated
from the jet-to-wire or rush-drag control setpoint corresponding to the equation
used in the jet speed input calculation.
(JWSP × V ) 2
H SP =
In the template, the VIO is defined, and has the formula of 2g
where:
H SP is the totalhead setpoint
JWSP is the jet-to-wire setpoint

g is the gravitational constant
There is a table for the 2g constant in Template Help.

ControlDisplayLine: See Subsection 3.3.1.
3-20 3/9/17 P/N: 6510020582 Rev 00

TotalheadIOData: See Subsection 3.4.19
3.4.19. TotalheadIOData
Add this object if total head is not the final output element for jet-to-wire or rush-
drag control. If total head cascade to another controller (for example, fan pump),
then enter the information for (fan pump) in this object. Also enter the input (AI)
for total head.
CascadeId ID of the control loop to cascade to

Default = blank
CascadeName Name of the control loop to cascade to. If the cascade object is a
remote controller, then enter the id (of the remote controller).
Default = blank
TotalheadInputId VIO ID of total head input
Default = THead1In
3.4.20. HbxCons
This object represents a headbox consistency supervisory control. Headbox
consistency is controlled by any of these devices:
• bypass valve
• fan pump
• stream valve
• slice
Typically, slice is used as the control device.
P/N 6510020582 Rev 00 3/9/17 3-21

HbxConsLoopId ID of the supervisory controller for headbox consistency

Default = HbxCons
SliceLoopId ID of the VIO for the slice controller. The VIO for slice has to be defined
in a viomap.
Default = blank
StockFlowVIOId ID of the stock flow VIO
Default = blank
ConsVIOId ID of the consistency VIO
Default = blank
CtlLineForLabEntry The control line number for the lab entry of the headbox consistency
Default = blank

• ControlDisplayLine: See Subsection 3.3.1.
3.4.21. VIO (in HeadboxCtlPkg)

Two VIOs need to be defined, one for calculating the jet speed and the other one
for calculating the jet-to-wire setpoint. The configured VIOs are included in the
HeadboxCtlPkg templates.
3.4.22. ShutDownPkg (in PerfMDControl)

Shutdown Control (also known as Steam Reduction) is an optional package for
MD Control. If Shutdown Control is not a part of your system, skip this section.
The Shutdown Control package is a control strategy that allows steam sections to
be ramped down during sheet breaks, and ramped back up after the break is
cleared. The ramping can occur in several phases so that the ramps can take effect
gradually–this is set up by the engineer. Each steam section that must be
controlled during a break can monitor multiple break signals.
If Steam Bias control has been configured in the system, both the master and
slave steam sections should be added to the Shutdown Control package. The
Steam Bias control will suspend during a break, and the Shutdown Control
package will manage both the master and the slave independently.
Shutdown configuration is performed in two steps:

3-22 3/9/17 P/N: 6510020582 Rev 00
1. Add the main shutdown control package.
2. Define the sections and the break signal, steam, and moisture VIO IDs
for each steam section.
There are two templates available for this object:
• Dye Shutdown: Used for reducing the flow of the dye pumps during
break.
• MDMV Shutdown: Used for Multivariable MD control.
There is no shutdown control template available for MD control.
Description Description of the Shutdown Control package. This description shows

up as the description of the shutdown control package on the HMI
displays.
Default = Shutdown Package
Number of phases Number of transitions during and after break sessions. This is a global
definition and applies to all sections to be defined next.
Default = 6
During system runtime, the phases can be disabled to reduce the
number of phases

• ShutDownSection: See Subsection 3.4.23.
3.4.23. ShutDownSection
For each steam section that can be controlled during sheet break, you need to have
a shutdown section object under
PerfMDControls/ShutDownPkgs/ShutDownSections.
P/N 6510020582 Rev 00 3/9/17 3-23

ID ID of the steam section

Default = blank
Ddc VIOId ID of the VIO for steam pressure for this section
Default = blank
Supv VIOId ID of the VIO for the moisture control variable for this section
Default = blank

Controller is of type Rmpct
Set to 1 if the supervisory control of this shutdown section is RMPCT.

DSR Is not used
By default, DSR records are added to support shutdown controls. By setting this
option to a 1, the DSR support is not added for this section only.

• Break: See Subsection 3.4.24.
3.4.24. Break
Multiple break signals can be monitored for a given steam section. For each break
signal, you need to have a break object under
PerfMDControls/ShutDownPkgs/ShutDownSections/Breaks.
VIOId ID of the VIO for the break signal to be used for detecting the break
transitions for this section
Default = break1
3-24 3/9/17 P/N: 6510020582 Rev 00

3.4.25. Crepe
Crepe control is a supervisory control feature typically used in tissue machine
application to control the crumpling or bunching of the paper. It uses Yankee
Speed and Reel Speed input, and supervises the reel speed. When requesting
crepe control on, the reel speed is forced to cascade mode. The setpoint for the
reel speed is computed based on the type of the calculation of the crepe ratio.
There are three types of calculation of the crepe ratio:
• Yankee speed/Reel speed
• 100 * (Yankee speed - reel speed)/Yankee speed
• 100 * (Yankee speed - reel speed)/Reel speed
Crepe VIO Id ID of the supervisory crepe control

Default = CREPE
Section Id ID of the process section to which this supervisory control belongs
Default = REEL
Crepe Calc Type A selection list to select one of the three types of crepe ratio calculation
as described previously
Default = 1
Yankee Speed VIO Id ID of the VIO for Yankee speed
Default = MACHSPD
Reel Speed VIO Id ID of the VIO for Reel speed
REELSPD

ControlDisplayLine: See Section 3.3.1.
3.4.26. Multiply
Multiply Control is a control package that provides regulation of the dry weight of
paper board by adjusting the total dry flow.
The total dry flow is comprised of multiple layers (plys) with different furnish as
well as different levels of participation. The VIOs for the ply stock flows and
P/N 6510020582 Rev 00 3/9/17 3-25

consistency need to be defined in a viomap. They can be either remote controller

or local controller type.
There is one template available for Multiply object:
• 4 Ply-3 Furnish MultiplyControl - Multiply Control with 4 Plys and 3

Furnishes.
Id ID of the multiply control

Default = MPLYCTL
Name Name of the control package
Default = Multiply1
Section Name of the section
Default = Reel
Weight Control Id ID of the basis weight controller whose output is to the total stock flow
Default = BW1
Total Stock Flow VIOId ID of the total stock flow control. A VIO must be created of type
controlloop for the total stock flow. Also, the mdvariable for basis weight
should point to this stock flow ID in its attribute for cascadeid.
Default = StkFl
For a multiply system, the total stock flow ID defined in the multiply object
should be used as the cascadeid attribute of the basis weight control mdvariable.

StockFlowDSRLoad
If set, the stock flow targets will be updated from recipe at recipe load.

• MPlySheetWidth: See Subsection 3.4.27.
• PlyData: See Subsection 3.4.28.
• FurnishData: See Subsection 3.4.29.
• ControlLoop: See Subsection 3.4.30.
3-26 3/9/17 P/N: 6510020582 Rev 00

3.4.27. MPlySheetWidth
Used to define the sheet width source.
Record type Frame or VIO

Default = blank
Record id ID of the sheet width object
Default = blank
Relative path Path pointing to the sheet width value relative to the Record ID
Default = blank
Record name Name used for mplysheetwidth object
Default = blank
If a constant sheet width value representing pond width or web width is to be

used, the Multiply Control package has an option flag that can be set up from
the Multiply Control Setup display. In such a case, there is no need to configure
the mplysheetwidth object.
3.4.28. PlyData
Define one PlyData object for each ply.
P/N 6510020582 Rev 00 3/9/17 3-27

Id ID of the ply (should be limited to three characters because it is also

used in the Multiply Control display, and any ply ID with more than
three characters will not show up properly on the display).
Default = blank
Stock Flow VIO Id ID of the stock flow controlled by this ply. The stock flow VIO needs to
be created under the VIO map object list. It can be either a remote
controller or local controller type.
Default = blank
Display Line Number Used to sort the plys for presentation on the main Multiply Control
display. For example, if there are three plys with IDs of p1, p2, and p3,
and with display line numbers 3, 2, 1, then the Multiply Control display
will present the plys in the order of p3, p2, and p1.
Default = 0
3.4.29. FurnishData
Define one FurnishData object for each furnish.
Id ID of the furnish (should be limited to 8 characters because it is also

used in the Multiply Control display, and any furnish ID with more than
8 characters will not show up properly on the display).
Default = blank
Consistency VIO Id ID of the VIO for consistency for this furnish
Default = blank
3.4.30. ControlLoop (in Multiply)

ControlLoop is the standard configuration object (with these specifications):
• When adding the control loop for the total stock flow, select the supv
control template.
• Set the execution event attribute to R1SEC.
• Set the option mask for these two options:
3-28 3/9/17 P/N: 6510020582 Rev 00

This VIO Controller uses non-standard execution.
This VIO Controller uses non-standard logic.
• Remove any ctlinput objects.
Add one ctlcascade object for each ply, defining the stock flow controller of the
ply.
A sample control loop configuration is shown in Figure 3-4.
Figure 3-4 Control Loop Object for Multiply
3.4.31. Ratio
Ratio control is a supervisory control feature that provides ratioing between two
controllers. The VIOs for the two controllers to be ratioed must be defined in a
viomap and can be either a remote controller or local controller type.
For example the ratio control can be used when two steam sections need to be
coordinated to control a moisture CV. In this case, the ratio control ratios the
setpoint of one steam loop (Slave) according to the setpoint of the other steam
loop (Master).
P/N 6510020582 Rev 00 3/9/17 3-29

There is one template available for this object:
• Ratio1 - Ratio Control
Id ID of the supervisory ratio controller

Default = StmRat1
Name Name of the supervisory ratio controller
Default = Steam ratio 1
ExecEvent Name of the event when the ratio controller has to execute
Default = R1SEC
The event must be pre-defined. The ratio object does not create any
event. Because the R1SEC event comes by default with the RAE
platform, the default is set to R1SEC. If a 5 second instead of a 1
second execution rate is desired, change the value for multiple field to 5
in the execution object for the ratio controller in the RTDR.
Section Name of the section to which the ratio controller belongs
Default = Reel
MasterVIOId ID of the VIO for the master controller. The VIO for the master controller
should be defined in a viomap. The setpoint from the master controller is
used as the reference to ratio to the slave controller.
Default = blank
SlaveVIOId ID of the VIO for the slave controller. The slave controller should also be
defined in a viomap.
Default = blank

3.4.32. Bias
Bias control is a supervisory control feature that provides offset or bias
calculation in setpoint between two controllers. The VIOs for the two controllers
to be in bias control must be defined in a viomap and can be either remote
controller or local controller type.
For example the bias control can be used when two steam sections need to be
coordinated to control a moisture CV. In this case, the bias control offsets the
setpoint of one steam loop (Slave) according to the setpoint of the other steam
loop (Master).
3-30 3/9/17 P/N: 6510020582 Rev 00

• Bias1 - Bias Control
Id ID of the supervisory bias controller

Default = StmBias1
Name Name of the supervisory bias controller
Default = Steam bias 1
ExecEvent Name of the event which the bias controller has to execute
Default = R1SEC
The event must be pre-defined. The bias object does not create any
event. Because the R1SEC event comes by default with the RAE
platform, the default is set to R1SEC. If a 5 second instead of a 1
second execution rate is desired, change the value for multiple field to 5
in the execution object for the bias controller in the RTDR.
Section Name of the section to which the bias controller belongs
Default = Reel
MasterVIOId ID of the VIO for the master controller. The VIO for the master controller
should be defined in a viomap. The setpoint from the master controller is
used as the reference to bias to the slave controller.
Default = blank
SlaveVIOId ID of the VIO for the slave controller. The slave controller should also be
defined in a viomap.
Default = blank

3.4.33. Midrange
Midrange control is used when two controllers known as Coarse and Fine
controllers control one CV. The midrange control changes the setpoints of the two
controllers to ensure that the process value of the fine controller is maintained
within a range.
The VIOs for the coarse and fine controllers to be in midrange control must be
defined in a viomap and can be either a remote controller or local controller type.
P/N 6510020582 Rev 00 3/9/17 3-31

• Midrange1 - Midrange Control
Control Loop Id ID of the controller whose process value is monitored to remain within
the midrange limit. This is also called the fine controller.
Default = blank
Midrange Id ID of the midrange object
Default = MR1
Midrange Name Name of the midrange object
Default = blank
CascadeId ID of the controller that gets the corrective action when the control loop
that is monitored for process value to be within midrange limit goes out
of limit. This object is also known as the coarse controller.
Default = blank

3.4.34. Feedforward
Feedforward control is a supervisory control feature that monitors the process
value of a disturbance variable and makes corrective actions to a defined control
loop so that the effects of the disturbance are not passed along to the final product.
• Feedforward1 - Feedforward control
3-32 3/9/17 P/N: 6510020582 Rev 00

FfwdSource ID of the VIO whose process value is monitored for any source of
change. This is the disturbance variable (DV). An example would be
stock consistency.
Default = blank
FfwdDest ID of the VIO controller that receives the corrective action from the
feedforward control when a change in the ffwdsource is detected. An
example would be stockflow.
Default = blank

3.4.35. MDCommonPkg
The MDCommonPkgs list encompasses the optional automatic grade change
control object. When you add an object under the mdcommonpkgs list, this brings
P/N 6510020582 Rev 00 3/9/17 3-33

up a new (unconfigured) mdcommonpkg template with child objects and

attributes as shown in Figure 3-5.
Figure 3-5 MD Common Package Object
The automatic grade change control package is an optional package. If the

grade change control package is required, the mdcommonpkg object must be
added and its child object mdgradechange must be configured.
Configure the MDGradeChange object only if the grade change package is

required.

• MDGradeChange: See Subsection 3.4.36.
• WeightConversion: See Subsection 3.4.37.
• ProductionRate: See Subsection 3.4.38.
3-34 3/9/17 P/N: 6510020582 Rev 00

3.4.36. MDGradeChange
This object adds the MD Grade Change Package. Add and configure this object
only if grade change control is required.
Name Name of MD Grade Change Package

Default = MDGradeChange
SheetBreakId ID of the sheet break VIO
Default = blank
3.4.37. WeightConversion
This object is used to configure setpoint conversion between the basis weight, dry
weight and conditioned weight. For example, in case of a system that is running
in the mode where the controller is controlling a weight CV (e.g. dry weight) and
the setpoint of the CV is input through another weight variable (e.g. basis weight
or conditioned weight), the setpoint conversion function converts the input weight
setpoint to the corresponding setpoint of the weight variable that is controlled by
the controller. The conversion function performs the conversion when the setpoint
is entered on the main MDMV Controls display or the grade change display or
loaded from the recipe.
The WeightConversion object is NOT required for MD Traditional Controls

because the traditional controllers perform weight conversion internally. The
WeightConversion object should not be configured for MD Traditional
Controls.
Main Weight Id This is a unique Id among weight conversion objects.

Default = blank
Description This is the description of this weight conversion object.
Default = blank
P/N 6510020582 Rev 00 3/9/17 3-35

Main Weight Type This is the type of the main weight. The operator enters the weight
setpoint through this loop.
Default = 0
0 = Basis Weight
1 = Conditioned Weight
2 = Dry Weight
Basis Weight Id This is the Id of the basis weight that is used in this conversion.
Example = BasisWeight
Conditioned Weight Id This is the Id of the conditioned weight that is used in this conversion.
Example = CondWeight
Dry Weight Id This is the Id of the dry weight that is used in this conversion.
Example = DryWeight
Moisture Id This is the Id of the moisture that is used in this conversion.
Example = Moisture
3.4.38. ProductionRate
The object is used to configure the production rate calculation. Every time that the
sheet width, machine speed or weight setpoint is changed on the grade change
display, the conversion function calculates and updates the production rate
setpoint. The conversion function also calculates and updates the process value of
the production rate every time that the sheet width, process value of the machine
speed or weight changes.
Production Rate Id This is a unique Id among production rate objects.

Default = blank
Production Rate Unit This is the unit of production rate.
Example = tph
Description This is the description of this production rate object.

Default = blank
Calculation Type This is the type of the production rate calculation.
Default = 0
3-36 3/9/17 P/N: 6510020582 Rev 00

0 = Based on Basis Weight

1 = Based on Dry Weight and Moisture
2 = Based on Conditioned Weight
Basis Weight Id This is the Id of the basis weight that is used in this calculation.
Example = BasisWeight
Conditioned Weight Id This is the Id of the conditioned weight that is used in this calculation.
Example = CondWeight
Dry Weight Id This is the iI of the dry weight that is used in this calculation.
Example = DryWeight
Moisture Id This is the Id of the moisture that is used in this calculation.
Example = Moisture
Machine Speed Id This is the Id of the machine speed that is used in this calculation.
Example = MachSpeed
P/N 6510020582 Rev 00 3/9/17 3-37

4. MD Traditional Control Testing
After the MD Traditional Control system is configured and built, it should be

tested to make sure that the configuration is correct and feasible without any
incompatibilities, and that all the functions and packages work as expected
without any errors.
4.1. Loading RTDR

Although a DRG file can be configured, exported and built without any apparent
errors, the RTDR may fail to load if there are conflicts and errors in the database
records. Therefore, it is important to verify the health of the RTDR before starting
up the QCS. This can be done by loading the RTDR first using the RTDR
database browser or RAE browser. This is the first place where an error resulting
in an aborted system load can occur. The RAE browser will point to the RTDR
load file where the load error occurs. This helps identify the configuration errors
that cause the load failure. Another source of error information is the Windows
Event Viewer. Any RTDR load errors will be written to the Application log in the
Event Viewer.
4.2. Full System Testing

A full system test requires that the Experion MX QCS be started. This launches
all the required MD Traditional Control functions, packages, HMIs and
communication links. Once again, the Event Viewer can be a good tool to identify
any errors or problems. Once the QCS is started, logon with the manager account
to gain access to the engineering displays for MD Traditional Control. These
displays can often be used to identify and troubleshoot any configuration-related
problems.
It is important to get scanner measurements and establish communication to the

remote controllers and control loops in the DCS in order to fully verify the
P/N 6510020582 Rev 00 3/9/17 4-1
Configuration and System Build Manual MD Traditional Control Testing
supervisory control function and other control packages. For scanner

measurements, the most ideal way is to connect to an actual scanner that is
measuring the paper. If a scanner is not available, a scanner simulator can be used
to simulate the measurements. For the remote controllers and control loops, the
most ideal way is to connect to the actual DCS through the specified
communication link. If such connection is unavailable, a DCS simulator can be
used to simulate the communication between QCS and DCS.
Even if there are scanner or simulated measurements and actual or simulated DCS
links, it is difficult to test out supervisory control and other control functions
without the actual paper machine process to provide the responses to control
actions. Honeywell Vancouver has developed a paper machine simulator which
can simulate scanner measurements, DCS links to remote controllers and control
loops, and process responses through predefined process models between CVs
and MVs and those between CVs and DVs. The paper machine simulator is
beyond the scope of this manual.
4-2 3/9/17 P/N: 6510020582 Rev 00

5. Glossary
Controlled Variable A variable in the paper-making process, typically a paper sheet property, being
(CV) controlled by a supervisory control system to a specific target. Some common
CVs are basis weight, dry weight, moisture, and ash.
Distributed Control A control system usually of a manufacturing system, process or any kind of
System (DCS) dynamic system, in which the controller elements are not central in location but
are distributed throughout the system with each component sub-system
controlled by one or more controllers. The controllers are connected by a
network for communication and monitoring.
Data Storage and A mechanism provided in real-time application environment (RAE) for storing
Retrieval (DSR) recipe-dependent data, such as tuning, calibration, and setup values, and
retrieving them when a recipe is loaded.
Disturbance Variable A measurable or non-measurable variable, not controlled by a supervisory
(DV) control system, that has impact on one or more CVs. A measurable
disturbance variable can be used as an input to a supervisory control system to
provide feedforward control on CVs.
Experion MX The product name for Honeywell’s latest quality control system (QCS), of
which Experion MX MD Controls is one of the applications.
Experion Process Honeywell process automation system
Knowledge System
(PKS)
Grade A set of quality parameters and properties used to define the type of paper.
The term is used interchangeably with the term recipe to refer to a collection of
grade-dependent parameters stored in the recipes database.
Machine Direction The direction in which paper travels down the paper machine.
(MD)
Management A mechanism provided in RAE to accumulate and manipulate production data,

Information System and to generate reports for mill wide management.
(MIS)
Manipulated Variable A variable in the paper-making process representing manipulated by a

(MV) supervisory control system to control certain paper properties. The variable
typically represents a physical entity. Some common MVs are stock flow, filler
flow, and steam pressure.
PAR Product Anomaly Report
P/N 6510020582 Rev 00 3/9/17 5-1

Configuration and System Build Manual Glossary
Permanents A database provided by RAE to store the last values of certain process
Database parameters so that these values can be restored when the QCS starts up from
a previous shutdown.
Process Value (PV) The current value of a CV, MV, or DV if the DV is measurable.
Quality Control A computer system which manages the quality of the paper produced.
System (QCS)
Real-Time The system software used by Experion MX QCS to manage data exchange
Application between applications (with Performance MD Multivariable being one of them).
Environment (RAE)
Recipe Literally means a list of pulp chemicals, additives, and dyes blended together
to make a particular grade of paper. In the Experion MX QCS, a recipe refers
to a group of data in the recipes database which stores for a given grade of
paper the grade-dependent parameters such as sensor calibration, operating
limits, and controller tuning.
Recipes Database A database provided by RAE to store recipe-dependent parameters.
Real-Time Data The database managed by RAE to store system data and data for individual
Repository (RTDR) applications.
Software Control A Honeywell engineer responsible for configuring, building, and commissioning
Engineer Honeywell control systems for customers.
Setpoint (SP) Target value (desired value). Setpoints are defined process values that can be
modified by entering new values through the monitor, loading grade data, and
changing a supervisory target.
SISO Single Input Single Output
Virtual Input/Output A mechanism provided in RAE to provide a virtual interface to applications

(VIO) (with MD Multivariable being one of them) to physical inputs and outputs of the
QCS.
5-2 3/9/17 P/N: 6510020582 Rev 00

Experion MX MD Controls R700.1 Traditional Control: Configuration and System Build Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Experion MX MD Controls R700.1 Traditional Control: Configuration and System Build Manual

Uploaded by

Copyright:

Available Formats

Experion MX MD Controls

R700.1 Traditional Control

1. MD Traditional Control Overview ...................................................................................... 1-1

2. MD Traditional Control Configuration and Build Process .............................................. 2-1

3. MD Traditional Control Configuration Components ....................................................... 3-1

P/N 6510020582 Rev 00 3/9/17 i

3.4.2. PerfMDControl ................................................................................................. 3-5

3.4.22.2. Child Objects ............................................................................................ 3-23

4. MD Traditional Control Testing.......................................................................................... 4-1

P/N 6510020582 Rev 00 3/9/17 iii

5. Glossary ................................................................................................................................. 5-1

iv 3/9/17 P/N 6510020582 Rev 00

Experion MX MD Controls R700.1 is the machine direction (MD) control

Experion MX MD Controls provides two control options – MD Multivariable

All references to MD Controls in this document are to Experion MX MD Controls

All references to MD Traditional Control or Traditional Control in this document are to

P/N 6510020582 Rev 00 3/9/17 v

About This Manual

Chapter 1, MD Traditional Control Overview, provides an overview of the

Chapter 2, MD Traditional Control Configuration and Build Process,

Chapter 3, MD Traditional Control Configuration Components, describes

Chapter 4, MD Traditional Control Testing, describes the high-level

Text may appear in uppercase or lowercase except as specified in these conventions.

Boldface Boldface characters in this special type indicate your input.

P/N 6510020582 Rev 00 3/9/17 vii

The Traditional Control option in Experion MX MD Controls provides MD

1.1. Software Components

• Real-Time Data Repository (RTDR) configuration and build macro

• DLLs, executable and LabVIEW VIs for control functions

• HMIWeb and LabVIEW human machine interfaces (HMIs)

1.2. RTDR Database Structure

MD Traditional Control adds the following top-level database records to the

P/N 6510020582 Rev 00 3/9/17 1-1

• Process setup definitions for MD Control are located under ./Process

• Records of top-level VIs to be called by RAE scheduler are under

• Records of top-level VIs to be called upon system startup are under

• Records of human machine interfaces (HMIs) are located under

• Remote controller regulatory loop records are located under

• MD Control function parameters and records are located under ./Md

1.3. Configuration & Build Code

• Configuration object definitions and templates

• Configuration object rules

• Cruncher build macros

1.4. Application Code

• C:\Program Files (x86)\Honeywell\Experion MX\MD

1-2 3/9/17 P/N: 6510020582 Rev 00

• C:\Program Files (x86)\Honeywell\Experion MX\MD

• C:\Program Files (x86)\Honeywell\Experion PKS\RAE\Displays and

1.5. System Configuration and Build Overview

1. On the Experion MX QCS server, use the Configuration Browser

2. Configure the MD Traditional Control top-level objects and all

3. Export the system configuration (DRG) file.

6. Start up the server and operator stations. MD Traditional Control runs

Due to possible changes in configuration objects and templates, an existing system

P/N 6510020582 Rev 00 3/9/17 1-3

2.1. Build & Load Configuration Environment

Follow these steps to build and load the configuration environment:

1. In the RAE configuration browser, select Options… from the View

2. Ensure that under the General tab, the Configuration Environment

P/N 6510020582 Rev 00 3/9/17 2-1

config DR size may need to be increased further if there are a large

2.2. Import and Translate System Setup File

2.3. Adding MD Traditional Control Objects