Reference Manual: 800xa - AC800M Connect - Minerals Library

We reserve all rights in this document and in the information contained therein.
Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
Ó Copyright 2018 ABB. All rights reserved.
Overview
Reference Manual
800xA - AC800M Connect - Minerals Library
Version 6.0/3
Based on Project Minerals Library, CoE Cement and Minerals

Prep. PIMIN-EA / Ch. Tschumi 26.03.2010
Appr. PIMIN-PD / G. Schuetz 12.09.2016
Doc. kind Reference Manual Doc. Item Overview
Title Overview des. des.
800xA Minerals Library Version 6.0/3 Resp. dept. CHIND / PIMIN-PD

Doc. no.
Lang. Rev. ind. Page 1
ABB Switzerland Ltd 3BHS161555-603 en AA No. of p. 68
We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
CONTENT
1. GENERAL ................................................................................................................. 3
1.1 SOFTWARE MODULE TYPICALS .................................................................. 3
1.2 DOCUMENT ORGANISATION ........................................................................ 4
2. DEFINITIONS AND ABBREVIATIONS ..................................................................... 5
3. OBJECT CATEGORIES ............................................................................................ 7
3.1 BASIC OBJECTS............................................................................................. 7
3.2 COMMUNICATION OBJECTS....................................................................... 10
3.3 CONSUMER OBJECTS................................................................................. 11
3.4 GROUP OBJECTS ........................................................................................ 12
3.5 LOOP OBJECTS ........................................................................................... 13
3.6 DOSING OBJECTS ....................................................................................... 13
3.7 POWER MONITORING OBJECTS ................................................................ 14
3.8 REPORT OBJECTS ...................................................................................... 15
3.9 COMPOSITE OBJECT TEMPLATES ............................................................ 16
4. LIBRARY CUSTOMIZATION .................................................................................. 17
4.1 LOOK AND FEEL .......................................................................................... 17
4.1.1 How to change between different standard types .............................. 21
4.2 PG2 EXPERT USER GRAPHIC APPEARANCE CUSTOMIZATION ............. 24
4.2.1 Workplace Specific Settings .............................................................. 24
4.2.2 Object Specific Settings .................................................................... 27
4.2.3 Logical Colors ................................................................................... 39
4.3 NLS CUSTOMIZATION ................................................................................. 46
4.3.1 Minerals Library NLS ......................................................................... 47
4.3.2 Project Specific NLS Support for Interlock and Alarm messages ....... 49
4.3.3 NLS support for Object Description ................................................... 52
4.4 ALARM AND EVENT APPEARANCE CUSTOMIZATION .............................. 53
4.4.1 Minerals Library AE handling relations .............................................. 53
4.4.2 NLS, AE and Event Log Project Constants........................................ 54
4.4.3 User Permission Configuration .......................................................... 57
5. PROGRAM STRUCTURE ....................................................................................... 59
5.1 Application and Diagram Structure with Minerals Library ............................... 59
5.2 Parameters and Variables.............................................................................. 59
5.3 Group and Process Control Connections ....................................................... 60
5.3.1 Overview ........................................................................................... 60
5.3.2 Control Builder Connections .............................................................. 61
5.4 800xA Functional Structure ............................................................................ 62
5.4.1 Functional Structure Uploader ........................................................... 62
5.5 Code Sorting .................................................................................................. 65
5.6 Settings in Control Builder M.......................................................................... 66
5.6.1 Task Definitions................................................................................. 66
5.6.2 CBM Compiler Switches.................................................................... 66
6. DOCUMENT REVISION HISTORY.......................................................................... 68
Doc. kind Reference Manual Project Minerals Library, CoE Cement and Minerals
Title Overview
800xA Minerals Library Version 6.0/3
Document number
Lang. Rev. ind. Pages 2
1. GENERAL
This document contains an overview of all controller software modules that are used to
configure applications for the Mining, Cement and Minerals Industries with 800xA and
AC800M controllers.
1.1 SOFTWARE MODULE TYPICALS

A set of tailor made software module typicals has been developed, supporting the
process requirements for Minerals application, in effort to increase quality and engineering
efficiency.
The software modules are developed with the Control Builder M Professional
programming tool, as Control Modules Types, to obtain the full benefits of object
orientation.
The software modules are grouped in eight different object categories:
· Basic Objects
· Communication Objects
· Consumer Objects
· Dosing Objects
· Group Objects
· Loop Objects
· Power Distribution Monitoring Objects
· Report Objects
Refer to a separate Reference Manual for each object category for more detail.
Title Overview
Document number
1.2 DOCUMENT ORGANISATION

The figure below shows the structure of all related documentation.
Function Description
MINERALS
FUNCTION DESCR 00
Project Documentation Documentation Guideline

<Project> <Project>
<Customer> <Customer>
Configuration Standard Minerals Library

MINERALS Standard Product Manuals
Software Design 00
Documentation
System 800xA
Manuals
Compact 800 -
Process Panel
Figure 1 Document Organisation
Title Overview
Document number
2. DEFINITIONS AND ABBREVIATIONS

This section gives on overview of all definitions and abbreviations used in this document.
800xA
Stands for ABB 800 extended Automation System.
AC800M
ABB Process Controller used for the Minerals Library AC800M Connect.
AC800M Connect
Connectivity of the AC800M controller family into system 800xAABB Process Controller
used for the Minerals Library AC800M Connect.
AI
Analog input signal.
AO
Analog output signal.
Consumer
A consumer is a physical process object controlled by the AC800M (e.g. motor, valve,
gate, damper). The number of consumers has a direct influence on the structure and
complexity of the system.
Control Module
Advanced (user defined) control object. Programmed in IEC 61131-3 standard languages.
Control Modules are an extension to the IEC 61131-3 as POUs definition.
CM
An abbreviation for Control Module.
CCM
An abbreviation for Composite Control Module.
CBM
An abbreviation for Control Builder M Professional. This is the engineering tool for the
AC800 M/C in 800xA.
CDE
An abbreviation for Control Builder Diagram Editor. This is a graphical control code editor
within CBM.
DI
Digital input signal.
DO
Digital output signal.
Data Type
Name of a structured variable in Control Builder M. Data types are defined as POUs in
CBM.
Function Block
User defined control function. Programmed in IEC 61131-3 standard languages. Function
Blocks are defined as POUs in CB M.
FB
An abbreviation for Function Block
Title Overview
Document number
GCC
Group Control Connection, GrpDrvBus (Datatype) connecting the consumers objects with
a group sequence
I/O
Input / Output device. (e.g. ABB S800 IO System)
LCC
Loop Control Connection, bus (Datatype) connecting Analog Loop Control objects
MS
MS stands for Microsoft Corporation
NG
New (Process) Graphics, often referred as PG2 - Process Graphics 2
OLE
Object Linking and Embedding. A technology, based on COM, developed by Microsoft
OPC
OLE for Process Control
PPA
Short form for OperateIT Process Portal A. The name of the standard ABB operator station
PC
Personal Computer
PCC
Process Control Connection, bus (Datatype) connecting the basic objects (signals) with
the consumer objects
PDA
ABB Automation Plant Design & Allocation tool
PG2
Process Graphics 2, often referred as NG - New Process Graphics.
POU
The IEC-61131 standard describes programs, function blocks and functions as Program
Organization Units or POUs. These units help you organize your automation project into
code blocks. CB M extends the standard with Data Types and Control Modules.
VBPG
Visual Basic Process Graphics. The old technology (SV 5.0 and earlier) for creating
process graphics in 800xA
VVVF
Variable Voltage, Variable Frequency speed controlled drive
Title Overview
Document number
3. OBJECT CATEGORIES
3.1 BASIC OBJECTS

The Basic Objects (AI, AO, DI, DO) provide access and control for process IO-signals and
calculated IO-signals.
Basic functions such as blocking and forcing of signals, control of output and limit level
changes are integrated in these objects.
Using the PCC (Priority Command Connection) concept input signal objects (AIS/AIC and
DIS/DIC) can propagate their alarm state to consumer objects. Depending on the
configuration, signals may send interlock actions to the connected consumer without using
binary interlock code. In addition it is possible to navigate between faceplates of signals
and consumers connected via PCC.
A detailed description of the basic objects and their interfaces is given in the reference
manual Basic Objects.
Reference Table: Basic Objects for process IO-signals
Name Type Function Data Type
AIS CM Analog input module for 1 process signal. The AISData
functions are blocking & forcing of input value, 6
limit levels, 3 alarm priorities, alarm delay, alarm
blocking, alarm disabling/enabling, configurable
interlock per limit level.
Write: use AIC control module
Read: IO.<TagName>.FilteredSignal.Value
Interlock: IO.<TagName>.<Limit>.Normal
AOS CM Analog output module for 1 process signal. The AOSData
functions are manual / auto mode, tracking of mode
and output changes, 2 output limits.
Write: IO.<TagName>.AutoValue
Together with IO.<TagName>.SetAuto
Read: IO.<TagName>.Signal.Value
DIS CM Digital input module for 1 process signal. The DISData
functions are blocking and forcing of input value, 3
alarm priorities, warning and alarm delay, alarm
blocking, alarm disabling/enabling from application
software, configurable interlock for pre-warning and
alarm.
Possibility for “Fast” Interlock action to Consumers.
Write: use DIC control module
Interlock: IO.<TagName>.Signal.Normal
DOS CM Digital output module for 1 process signal. The DOSData
functions are manual / auto mode, tracking of mode
and output changes.
Title Overview
Document number
Reference Table: Basic Objects for calculated IO-signals

AIC CM Analog input module for 1 calculated signal. The AISData
functions are the same as for the AIS. AIC uses
the same data type as AIS.
Write: IO.<TagName>.Signal.IOValue
Read: IO.<TagName>. FilteredSignal.Value
Interlock: IO.<TagName>.<Limit>.Normal
AOC CM Analog output module for 1 calculated signal. The AOSData
functions are the same as for the AOS. AOC uses
the same data type as AOS.
DIC CM Digital input module for 1 calculated signal. The DISData
functions are the same as for the DIS. DIC uses
the same data type as DIS.
Write: IO.<TagName>.SigHW.IOValue
Interlock: IO.<TagName>.Signal.Normal
DOC CM Digital output module for 1 calculated signal. The DOSData
functions are the same as for the DOS. DOC uses
the same data type as DOS.
Reference Table: Basic Objects for PCC

PCC_Connect FB The PCC Connect can be used if one signal shall PCCComData
be linked to multiple consumers thru PCC:
· Forwards alarm and interlock on signal to
all consumers depending on their state
· Individual interlock forwarding mask for
each consumer
PCC_Connect_6 CM Same Function as PCC_Connect but additionally PCCComData
supports forwarding the “Fast” Interlock between
DIS and consumers
PCC_ FB The PCC ThresholdAND3 allows defining Not defined
Threshold_AND3 complex interlock conditions thru PCC.
PCC_Intlk CM Single Interlock Condition thru PCC PCC_IntlkData
· Group several PCC Signals to one single
Interlock for a Drive
· Configurable Interlock and Ready Time
Delay
PCC_Connect_2 FB This Block is obsolete and replaced by PCCComData
PCC_Connect.
Title Overview
Document number

The PCC Connect2 can be used if one signal
shall be linked to 2 consumers thru PCC. PCC
Interlocks are not supported.
Title Overview
Document number
3.2 COMMUNICATION OBJECTS

Communications objects establish and supervise the communication between two
AC800M controllers or between different applications or diagrams.
A detail description of the objects and their interfaces is given in the reference manual
Communication Objects.
Reference Table: Communication Objects
GCC_Com_M CM The GCC_Com_M extends the group drive bus to GCC_ComD
another diagram and/or application ata
· Located in same diagram as Group
· Configurable action in case of
communication error
· Point-to-point communication to
GCC_Com_S via Communication Variable
GCC_Com_S CM The GCC_Com_S extends the group drive bus to GCC_ComD
another diagram and/or application ata
· Located in same diagram as Drives
· Point-to-point communication to
GCC_Com_M via Communication Variable
PCC_Com_D CM The PCC_Com_Drive is used to connect the PCC PCC_ComD
rive bus if the Signal and Drive are located in different ata
diagrams and/or applications:
· Located in same diagram as Drive
· Configurable error action in case of
communication error
· Can be connected to multiple Drives via
PCC_Connect
· Point-to-Point Communication via one
Communication Variable transferred to the
PCC_Com_Signal Block
PCC_Com_Si CM The PCC_Com_Signal is used to connect the PCC PCC_ComD
gnal bus if the Signal and Drive are located in different ata
diagrams and /or applications:
· Located in same diagram as Signal
· Standard PCC Signal connection from
PCC_Threshold_AND_3, PID, AIS, AIC,
DIS, DIC directly or by PCC_Connect
· Point-to-Point Communication via one
Communication Variable transferred to the
PCC_Com_Drive Block
MMS_COM CM Note: This Block is obsolete as Communication AnyType
Variables can be used instead
Establishes and supervises the communication
between two AC800 controllers. One sending and
one receiving structured variable, with up to 1000
bytes, is handled by one MMS_COM instance.
Title Overview
Document number
3.3 CONSUMER OBJECTS

Consumer objects provide access and control for the physical devices (consumers) in the
plant.
Basic functions such as operator orders, detailed interlock and alarm indication, tracking
of mode and status changes, are integrated in these objects.
Using the GCC (Group Control Connection) multiple consumers can be connected to a
group control function by one single connection. The sequential start and stop order can
be defined by parameters on the consumer object itself. The consumer object report their
actual state to the group object. In addition a link between the faceplates of the group and
its connected consumers is available.
A detailed description of the consumer objects and their interfaces is given in the
reference manual Consumer Objects.
Reference Table: Consumer Objects
Name Type Function DataTypes
MOT1 CM The Control Module Type MOT1 is used to control a MOT1Data
motor with one direction (one speed) in a drive
group or standalone.
MOT1_VVVF CM The Control Module Type MOT1_VVVF is used to MOT1VVVFD
control a motor with one direction and variable ata
speed in a drive group or standalone.
MOT2 CM The Control Module Type MOT2 is used to control a MOT2Data
motor with two directions (two speeds) in a drive
group or standalone.
MOT2_VVVF CM The Control Module Type MOT2_VVVF is used to MOT2VVVFD
control a motor with two direction and variable ata
speed in a drive group or standalone.
MOTP CM The Control Module Type MOTP is used to control MOTPData

a motorised valve or damper with or without
analog position feedback in a drive group or
standalone.
VLV1 CM The Control Module Type VLV1 is used to control a VLV1Data

normally-closed one-way valve with one or two
coils in a drive group or standalone. Up to two
position limit switches (open and closed) can be
supervised.
VLVNO1 CM The Control Module Type VLV1 is used to control a VLVNO1Data
normally open one-way valve with one or two
coils in a drive group or standalone. Up to two
position limit switches (open and closed) can be
supervised.
Actuator CM Actuator controls a positioner for a valve or ActuatorData
damper with analog position feedback, via analog
output.
Title Overview
Document number
3.4 GROUP OBJECTS

The Group Objects provide access and control for a process group or process group
related features.
Basic functions such as operator orders, detailed interlock and alarm indication, tracking
of mode and status changes, pre-selection of group members and startup warnings are
integrated in these objects.
A detail description of the group objects and their interfaces is given in the reference
manual Group Objects.
Reference Table: Group Objects
GROUP CM Group sequence. The functions are starting, GrpInput
stopping of group members in a sequential order, GrpOutput
summary status indication of all pre-selected group GrpDrvCon
members (ready, run, off), 4 start and 4 stop
interlocks, emergency quick stop.
Integrated duty – stand-by support
GrpCycleCtrl CM Cycle controller for the group. This control module GrpCycle
can be used for cyclic activation and deactivation of CntrlData
group members by means of a script (e.g. silo
aeration, cool down lubrication etc.). Several
GrpCycleCtrl objects can be added to one GROUP.
PREBIN CM Pre-selection module. The function is to activate or PreBinData
deactivate one or a set of group members such as
consumer objects or loops during the group start
up.
Pre-selection supports duty stand-by with automatic
or manual trip detection and group restart
STW CM Start Warning module. The function is to provide a STWData
start up warning for an individual consumer object
or a group.
DriveGroup CM Technological group to handle auxiliary equipment DriveGroupD
and main drives as one system ata
SubGroup CM Group Sequence. All the functions of a GROUP and SubGroupDa
can additionally be connected as group member to ta
a Master Group.
GroupStep CM The GroupStep function block can be used to: Not defined
· Start / Stop equipment not controlled by a
consumer object or loop. (e.g. valve
represented by a DOS)
· Start / Stop consumer objects located in
another controller.
· Start / Stop consumer objects controlled by
more than 2 groups.
Title Overview
Document number
3.5 LOOP OBJECTS

Loop objects provide access and control for analog closed control loops.
Basic functions such as operator orders, detailed alarm indication, tracking of mode and
status changes, are integrated in these objects.
Using the Loop Control Connection (LCC), Consumer objects handling an analog Setpoint
(MOTP, MOT1_VVVF etc.) can be controlled from Loop objects with one connection only,
forwarding the Setpoint and handling Range and Output Limitation (Backtracking).
A detailed description of the loop objects and their interfaces is given in the reference
manual Loop Objects.
Reference Table: Loop Objects
PIDCtrl CM State-of-the-art PID Closed loop controller with PIDCtrlData
feed forward, anti wind-up and limit handling
PIDAdvCtrl CM PID loop controller with advanced Features like PIDAdvCtrlData

Adaptive Control and Gain Scheduling
RatioCtrl CM Calculates an Output (Setpoint) by an Input RatioCtrlData
Signal with Gain and Offset
SplitRange CM Connect Setpoint from PIDCtrl or RatioCtrl to 2 SplitRangeData
Objects in parallel or split-range configuration
3.6 DOSING OBJECTS

Dosing objects provide access and control for Setpoint Values for weigh feeder
proportioning or other Analog Value controlled Objects.
A RecipeControl Block is provided to control multiple Dosing Objects operating with
relative Setpoints with a single Total Setpoint.
A detailed description of the dosing objects and their interfaces is given in the reference
manual Dosing Objects.
The Control Module Types RecipeControl and SetpointCommInterface and their
corresponding Structured Data Types are located in the library BMIRecipeControlBase
for Control Builder M Professional.
Reference Table: Dosing Objects
RecipeControl CM Main control object for a Recipe that handles up to RecipeContr
6 dosing object instances of the type olData
SetpointCommInterface.
Multiple RecipeControl Blocks can be connected
together to control a Recipe with more than 6
Setpoints.
SetpointCommI CM Dosing object instance (single feeder) that SetpointBus
nterface interfaces with the actual Controlled Object.
controls the actual feed setpoint (feed rate) for the
single feeder.
Title Overview
Document number
3.7 POWER MONITORING OBJECTS

Power monitoring objects are intended for supervision and control of power distribution
equipment such as switchgear, and protection relays using serial connectivity (e.g.
Profibus or Modbus). The objects are designed as composite control modules containing
one module for the communication. This module can be modified to adapt to the
requirements of the equipment.
A detail description of the objects and their interfaces is given in the module description
Power Monitoring Objects.
The Control Module Types for Power Distribution Monitoring objects and their
corresponding Structured Data Types are located in the library BMIEnergy for Control
Builder Professional.
Reference Table: Power Monitoring Objects
Circuit Breaker CM Control an IED Control Device with CircuitBreaker
1 Breaker with up to 2 Isolators and Data
Earth Switch in a drive group or
standalone
CircuitBreakerA Composite CM: Interface to an ABB REF542+ CircuitBreaker
BBREF542Plus connected via ModBus ABBREF542P
Circuit Breaker +
3 AIC (Current, lusData
Voltage, Power) + 1
Counter (Energy)
PFCCtrl CM Power Factor Correction Controller, PFCCtrlData
handling up to 8 Circuit Breakers
(Steps)
Title Overview
Document number
3.8 REPORT OBJECTS

Report objects provide access to Counter Values or summarize Analog Values over time
(integrator). The counters provide the following functions:
· 4 Modes: Pulse Counter, Integrator, Accumulator or Delta Accumulator
· Total and Shift value
· Reset to 0 from controller or Operator Station.
· Adjustment of counter value from the Operator Station.
A detail description of the report objects and their interfaces is given in the module
description Report Objects.
Reference Table: Report Objects
PulsCount CM Pulse Counter is used to count pulses and sum PulseCount
them up for production data reports. Data
ReportingCount CM Reporting Counter does add Shift, Day and Month ReportingCo
Log Values in addition to the PulsCount Features untData
Title Overview
Document number
3.9 COMPOSITE OBJECT TEMPLATES

The library contains a so called wrapper framework to compose project specific consumer
objects having serial communication interface (Profibus, Modbus, etc.) between control
system and device. The intention is to provide samples of how to implement project
specific serial devices. The samples included in the library shall be used as templates, i.e.
copied and adapted to the project specific requirements if required.
The Control Module Types and their corresponding Structured Data Types are located in
a dedicated Library per Interface like BMI_MNSIS, BMI_MNSiS_MBTCP, BMI_UMC22,
BMI_UMC100 and BMI_ACS8x0.
Reference Table: Serial Communication Objects
MOT1VVVF_ACS8x0 Composite CM: ABB Drive system with MOT1_VVVFData
MOT1_VVVF ProfibusDP interface
ACS500, ACS600,
ACS800 or ACS1000
MOT2VVVF_ACS8x0 Composite CM : ABB Drive system with MOT2VVVFData
MOT2_VVVF ProfibusDP interface
ACS500, ACS600,
ACS800 or ACS1000
UMC22 Composite CM ABB UMC22 MCC device MOT1UMCData
MOT1_MNSIS Composite CM ABB MNS iS MCC with MOT1_MNSISData

MOT2_MNSIS MOT1 + AIC (Current or Power) ProfibusDP Interface
MOTP_MNSIS MOT2 + AIC (Current or Power)
MOTP + AIC (Current or Power)
MOT1_MNSiS_MBTCP Composite CM: ABB MNS iS MCC with MOT1_MNSiS_MBT
MOT2_MNSIS_MBTCP MOT1, MOT2, MOTP Modbus over TCP/IP CPData
Interface
MOTP_MNSIS_MBTCP
MOT1_UMC100 Composite CM: ABB UMC100 with MOTx_UMC100Data
MOT2_UMC100 MOT1, MOT2, MOTP PROFIBUS Interface
MOTP_UMC100
Title Overview
Document number
4. LIBRARY CUSTOMIZATION
The Library can be customized at both the User Interface and the Control
Code to adapt to different Requirements. However in the Standard
Manuals only the default Configuration is described and the commonly
used Options are additionally mentioned. It is therefore important to
always document the deviations from the Default Configuration Options in
the System Specification.
4.1 LOOK AND FEEL

The library comes with predefined Themes that define the Settings for a certain Customer
or Industry:
Minerals Standard: The Classic Minerals Library look and feel
Holcim Standard: Holcim standard requirements
Title Overview
Document number
Hybrid Standard: Minerals Style with brighter Background Color
Crossed Not RFS: Classic Theme with red cross in case of Not Ready Status
Title Overview
Document number
VALE Standard: VALE Standard requirements
ASM White: Alarm Status Monitoring look and feel
Title Overview
Document number
ASM Green: Alarm Status Monitoring with pastel green color
For individual customization see chapter PG2 EXPERT USER GRAPHIC APPEARANCE
CUSTOMIZATION.
Title Overview
Document number
4.1.1 How to change between different standard types
1. Browse to “[ObjectType Structure] Object Types / ABB System / Process Graphics

/ BMI_GraphiXs_Customization / BMI Common Properties / GraphiXs
Configuration Settings” and press the “Resources Backup” Button to start the
“Resources Backup” Tool.
2. In case the current Settings have been changed already, please follow the
Description in the Release Notes to make a Backup of the current Settings before
the next Step.
3. In the Resources Backup Tool, choose the Folder as per the Standard required.
The Settings are found under C:\ABB Industrial IT Data\Minerals Library\
Title Overview
Document number
4. Choose the needed Resources as shown above and click the “Restore” Button to
load the Settings from the selected Folder. (The unselected Resources can be
loaded as well but are not defined in the Standard Themes).
5. For each Difference Report coming up, click “Proceed” to apply the changes.
It is only possible to replace the NLS Texts for one Language during the Restore.
To handle multiple Languages the Tool needs to be run multiple Times.
NOTE: The Holcim Standard does define different NLS Texts for the “en-us”
Locale only.
6. In case of switching to / from HOLCIM Standard, the following Settings need to be
changed in addition:
a. For all Operator Workplaces, change the Logical Colors
BMIngAlphaOffText and BMIngAlphaOffTextBack on the “BMI NG
Common Settings” Aspect to Black. This setting hides the DISTxt Labels
while no Alarm is present (Off state) – we propose to keep them enabled
for the Plant Explorer Workplace for the Engineer. (see chapter 4.2.1 for
a description of all the Settings with Logical Colors)+
b. In all Control Builder Projects, change the following Project Constant in
CBM by right mouse click on the Project (Root Object in Project Explorer)
and choose “Project Constants” in the Context Menu coming up:
cBMI.StdType = 0 Minerals Standard (and all other Standards)
cBMI.StdType = 1 HOLCIM
This setting enables the additional “Not Ready” Alarm Color used for
Alarming while a Motor is not selected or running.
Title Overview
Document number
Title Overview
Document number
4.2 PG2 EXPERT USER GRAPHIC APPEARANCE CUSTOMIZATION
4.2.1 Workplace Specific Settings

The Logical Color Aspect “BMI NG Common Settings” can be used to change workplace
specific defaults for the graphics. By this the amount of information can be reduced on
certain workplaces like large screens or visitor stations.
Name Description Range Default Value
Title Overview
Document number
BMIngAlpha Alpha transparency for BMI Process 0 … 255 255

Symbols., The alpha part is only active in
case the property “EnableLogicalColor” is
true in the graphic element. In case no
logical colors are used the alpha can be set
with the ARGB Function when defining the
color. The value is applied relative to the
setting of the “LogicalAlphaColor” in the
graphic element.
BMIngAlphaOffText Alpha transparency for dynamic texts (e.g. 0 … 255 160
the DISText). The transparency value is
applied in case the signal status is normal
and “AppearanceType” 0 = Alarm or 2 =
Value is selected in the graphic element.
BMIngAlphaOffTextBack Alpha transparency for the background of 0 … 255 35
dynamic texts (e.g. the DISText). Details
see “BMIngAlphaOffText”
BMIngAnalogEnableLimitLabel Enables the Limit Alarm Labels (e.g. HH) 0 / 255 255 = enabled
for analog objects. Individual disabling per
graphic element is possible.
BMIngAnalogEnableMode Enables the Mode Label (e.g. M) for analog 0 / 255 255 = enabled
output objects. Individual disabling per
BMIngAnalogROC Enables the Rate Of Change arrow for 0 / 255 255 = enabled
analog input objects. Individual settings can
be made from the faceplate.
BMIngDefaultSettings Stores current default setting, made with 0 … 99 1 = default
the “Default Configuration Tool”. Do not
change.
BMIngDigitalEnableMode Enables the Mode Label (e.g. M) for digital 0 / 255 255 = enabled
output objects. Individual disabling per
BMIngDriveEnableMode Enables the Mode Label (e.g. A or E) for 0 / 255 255 = enabled
consumer objects. Individual disabling per
BMIngEnableAlarmBlock Enables the indication of the status blocked 0 / 255 255 = enabled
alarm. Blocking the alarm from the FPL
disables all alarms of the object.
BMIngEnableBlock Enables the indication of the status Blocked 0 / 255 255 = enabled
/ Forced for basic objects. Usually this
parameter is only disabled for presentations
or FAT testing.
BMIngEnableColorBarAspectLink Enables the presentation of a colored line 0 / 255 255 = enabled
on top of the AspectLink button. The color
can be set by the logical color
“BMIngButtonBarAspectLink”. The idea of
the color is to differentiate between the
different types of buttons on the screen.
BMIngColorBarDigitalCmd Enables the presentation of a colored line 0 / 255 255 = enabled
on top of the DOS and DOC button. The
color can be set by the logical color
“BMIngButtonBarDigitalCmd”. The idea of
the color is to differentiate between the
different types of buttons on the screen.
Individual disabling per graphic element is
possible for cases a symbol shall be used
instead of text.
BMIngColorBarPreSel Enables the presentation of a colored line 0 / 255 0 = disabled
on top of the Pre-Selection button. The
color can be set by the logical color
“BMIngButtonBarPreSel”. The idea of the
color is to differentiate between the different
types of buttons on the screen.
BMIngEnableControlPoint Enables the Point Of Control Label (e.g. S, 0 / 255 255 = enabled
C or L) for group and consumer objects.
BMIngEnableOPNote Enables the Operator Note status symbol 0 / 255 255 = enabled
for DriveCore based elements e.g.
consumer objects
Title Overview
Document number
Name Description Range Default Value

BMIngEnablePrintBlock AC400 print block indication enabling 0 / 255 255 = enabled
BMIngEnableSelect AC400 selected frame indication enabling 0 / 255 255 = enabled
BMIngEnableSigError Enables the indication of the signal error for 0 / 255 255 = enabled
analog objects.
BMIngEnableStandardDEW Enable the standard direct entry window. 0 / 255 255 = enabled
The standard DEW can be invoked on left
mouse click.
BMIngEnableExtendedDEW Enable the extended direct entry window. 0 / 255 255 = enabled
The extended DEW can be invoked on right
mouse click
BMIngEnergyEnableCBGenAlarm Enabling of Circuit Breaker General Alarm 0 / 255 255 = enabled
indication on single line display
BMIngEnergyEnableFieldEarthAndS Enabling of Field Earth and Secure Label 0 / 255 255 = enabled
ecure for Circuit Breaker on single line display
BMIEnergyEnableSumIntrl Enabling of Circuit Breaker Interlock 0 / 255 255 = enabled
indication on single line display
BMIngFontSizeLabel Font size for all labels 6 … 12 8
BMIngFontSizeTagName Font size for the tag name presentation of 6 … 12 8
the consumer objects. The tag name can be
activated from the group FPL by pressing
the “Tag” button.
BMIngGroupEnableMode Enables the Mode Label (e.g. A) for group 0 / 255 255 = enabled
objects. Individual disabling per graphic
element is possible.
BMIngPIDEnableMode Enables the mode indication (e.g. Auto, 0 / 255 255 = enabled
Manual) in the status line of the PID
objects. Individual disabling of the status
line per graphic element is possible.
BMIngPIDEnableROC Not implemented yet 0 / 255 0 = disabled
BMIngPreSelEnableStatusOnSymbol Not implemented yet 0 / 255 255 = enabled
BMIngSizeLabelShadow Label shadow size in pixels for all labels 0…6 2
Title Overview
Document number
4.2.2 Object Specific Settings

The General Properties Aspect “BMI NG Common” located under [Object Type
Structure]\Process Graphics\BMI_GraphiXs_Customization\BMI Common Properties can
be used to change the general presentation style and behavior of the PG2 graphics.
Title Overview
Document number
Analog and PID Appearance

Using the Analog and PID appearance properties the presentation of those objects can be
adjusted to various customer standards. The PID can be a combination of its own and the
appearance of it’s values (e.g. raised PID with sunken measured value and raised set-
point entry etc.)
ValueandUnit
Appearance PID Back Value Back Bar Back
Back
0 = None
1 = Filled with
Frame
2 = Opaque
3 = Frame only
4 = Sunken
Title Overview
Document number
ValueandUnit
Appearance PID Back Value Back Bar Back
Back
5 = Raised
14 = Button Sunken
15 = Button Raised
Note: The result may be different depending on the logical color settings
Analog / PID Value and Unit Font Bold

Unlike the value and unit font size individually adjustable on every instance of the graphic
elements, the bold property can only be adjusted globally, thus to achieve a common style
on all the displays.
Setting PID Control Analog Value and Unit
ValueFontBold = true
UnitFontBold = true
ValueFontBold = false
UnitFontBold = false
ValueFontBold = true
UnitFontBold = false
Title Overview
Document number
Group Background Appearance

Appearance Group Back
0 = None
1 = Filled with Frame
4 = Sunken
5 = Raised
14 = Button Sunken
15 = Button Raised
Direct Entry Control

Important operator actions used for normal plant operation can be accessed by direct
entry without opening a faceplate. The direct entry for PID Control, Analog Output,
actuator and variable speed Drive set-points as well as Group start / stop can be globally
enabled / disabled per object type.
Direct Entry
PID and Drive Analog Output Group
Settings
EnableDirectEntry
= true
EnableDirectEntry
= false
To complete the entry either press the “Enter” Button on the keyboard,
or use the Graphic Element “Apply Button” additionally placed on the graphic
display.
For the group start / stop direct entry buttons the behavior can be configured to be direct
or applied for every instance of the graphic element.
The Analog Output may be controlled in addition by a Drag Handle
Drag Handel Settings Analog Output Bar
EnableDragHandle = true
EnableDragHandle = false
Title Overview
Document number
Standard and Extended Direct Entry Window

There are two different direct entry windows (DEW). The standard DEW opens on left
click on the object, the extended DEW invokes on right click. They can be individually
disabled for every workplace. See also 4.2.1 Workplace Specific Settings.
Standard DEW Extended DEW
invokes on left mouse click invokes on right mouse click

With the Extended DEW a keyboard-less input for PID Control, Analog Output, actuator
and variable speed Drive set-points is possible.
Example Description
Actual value and input value.
Click: Increase one step

Hold down: Increase continuously
Click: Decrease one step
Hold down: Decrease continuously
Clear input and restore actual value
Delete one digit
Apply input value.
The input value will not be set until this
button is pressed.
Use either the up/down-buttons, the

numbered buttons or the drag handle to
set a new input value.
The yellow marked area on the bar,
marks max- and/or min- input limits.
If the desired input value is not valid, a

short message will appear. In this case,
the apply button is disabled and the
input value can not be set.
Title Overview
Document number
PID Presentation Options

For the PID and consumer objects with analog control the graphic element can be
configured to present less or more information. Beside the below described general
settings the configuration can be changed individually on every instance as well.
Property true false
EnableTagName
EnableDescription
EnableStatus
Note: The table shows the deviation form the default, all settings can be combined to get
the desired look and feel.
Between 1 and 4 values can be presented, the default is 2 values, by default the second
value is auto selecting depending on the mode, e.g. in auto the set-point and in manual
the output is presented. Beside the below described general settings the configuration can
be changed individually on every instance as well.
Property true false
EnableValue1Ind
(Default = Measured Value)
EnableValue2Ind
(Default = SP or Output
depending on mode)
EnableValue3Ind
(Default = Output)
EnableValue3Ind
and
EnableValue4Ind
(Default = Actuator)
Note: The table shows the deviation form the default, all settings can be combined to get
the desired look and feel.
Title Overview
Document number
Analog / PID Alarm Appearance

The analog limit alarms can be presented with the following options
Appearance PID Control Analog Value
0 = None
1 = Filled Square
2 = Thick Frame
Note: The limit label can be enabled / disabled in addition either by Workplace Specific
Settings or individually in every instance.
Group Alarm and not Ready Appearance

The not ready for start or stop of a group might be caused by different reasons:
· Start Interlocks and Pre-Selection Errors -> Start Interlock
· Stop Interlocks -> Stop Interlock
· Group Drive Connection -> DrvNotReady
· IC Interlock and PCC connection -> NotReady
· Group Time Out Alarm -> Alarm
Start Stop
Appearance DrvNotReady NotReady Alarm
Interlock Interlock
0 = None
2 = Thick Frame
3 = Thin Frame
4 = Arrow n/a
Note: Recommended default is marked green in above table
DrvNotReady and NotReady can be disabled individually per instance as well.
Title Overview
Document number
Drive not Ready Appearance

In case EnableIndTr2 = true the Not Ready for Start presentation for the consumer objects
can be control by the NotReady for Start Appearance. The following consumer objects
conditions are included in the IndTr2 / NotReadyforStart:
· IC and IB Interlocks
· Summary warning or failure from connected PCC Signals
· FB1 and FB2 (e.g. Speed Switch) only MOT1, MOT2 and MOT1_VVVF
Off On
Off with Failure
NotRfsAppearance and On with Warning and
(not ready to start)
OK OK
3 = Thin Frame symbol off color symbol run color

frame failure color frame warning color
4 = Arrow symbol off color symbol run color

arrow failure color arrow warning color
5 = Cross symbol off color symbol run color

cross failure color cross warning color
6 = Slash symbol off color symbol run color

slash failure color slash warning color
100 = Apply to Symbol (off) symbol off with symbol off with
failure color warning color
101 = Apply to Symbol (on) symbol on with symbol on with

101 = Apply to Symbol

(depending on status) symbol off with symbol on with
Note 1: The color depends on the source causing the problem and can be either a
warning or a failure color.
Note 2: The consumer objects own alarms e.g. Availability, Contactor Feedback, Position
Limit switches etc. are handled by the IndTr1, and always presented as filled
square around the symbol.
Title Overview
Document number
CB Alarm Appearance
CB open and CB open with CB closed with CB closed
Alarm Appearance
ok failure warning and ok
0 = None
1 = Filled Square
2 = Thick Frame
(only available for
Status Appearance =
1)
Note: The color depends on the source causing the problem and can be either a
warning or a failure color.
CB Status Appearance
CB closed, CB closed,
CB open,
Status Appearance CB open Earth switch Isolator
Isolator closed
closed closed
0 = line only
When StatusAppearance = 0, no colored status indication is used. The line color is the
logical color BMIngHVLine (default is black). Note that alarm appearance as thick frame
(AlarmAppearance = 2) is only available for StatusAppearance = 1
CB open,
Isolator closed
closed closed
1 = colored status
indication on symbol
StatusAppearance = 1 indicates the object status as colored, rectangular symbol. The line
color can be selected with the OnColor property (default is A1_HVLine).
Title Overview
Document number
CB open,
Isolator closed
closed closed
2 = colored status
indication on line
With StatusAppearance = 2 the line color depends on the object status. Use the properties
OnColor and OffColor to change the default settings. Note that alarm appearance as thick
frame (AlarmAppearance = 2) is only available for StatusAppearance = 1
For more information see [08] Power Distribution Monitoring Objects (3BHS 253000).
Title Overview
Document number
Faceplate Settings
User defined settings for PG2 faceplates can be done in the resources listed below:
· General Property: “BMI NG Common”
Value back appearance and text indication settings are done here. See chapter
Common Settings for more details._Common_Settings
· Logical Color Table: “BMI NG Faceplate Colors”
This aspect defines colors for PG2 Faceplates. See chapter BMI NG Faceplate
Colors for detailed information._BMI_NG_Faceplate
· Resource Libraries: “BMI FPL Resources”
Font definition for all texts on PG2 faceplates and icon definition for extended info
link buttons (used on consumer, group and energy distribution object faceplates).
Common Settings
Text Setting
Appearance of all alarm, warning, interlock and block text indication can be changed with
the general property “TextIndicationType” and “EnableTextFrame”.
Text Indication
Enable Text Frame = False Enable Text Frame = True
Type
0
Text line with
background
color)
10
(Text line with
square in front)
Title Overview
Document number
The FontBold property is used only for texts which do not support logical fonts as
described in chapter Resource Libraries. These are mainly value input
fields._Resource_Libraries
Font Bold Example
True
False
Value Settings
General property ValueBackAppearance will change back appearance for all analog value
indication on PG2 Faceplate
Value Back
Example
Appearance
0 = None
1 = Filled with
Frame
2 = Opaque
3 = Frame only
4 = Sunken
5 = Raised
14 = Button
Sunken
15 = Button
Raised
Enable Input
Value Back Appearance = 0 Value Back Appearance = 2
Appearance
0 = None
4 = Sunken
5 = Raised
14 = Button
Sunken
15 = Button
Raised
Title Overview
Document number
Resource Libraries
The Resource Library Aspect “BMI FPL Resources” located under “[Library
Structure]\ResourceLibraries\MineralsLib FPL Resources\ BMI FPL Resources” can be
used to change fonts on PG2 faceplates. Extended Info icons for consumer, group and
energy distribution objects can be changed in this aspect as well.
BMI FPL Resources: Image definition BMI FPL Resources: Fonts definition
Font Name Description

BMIngFPLTrendAxis01 Trend axis font.
BMIngFPLTrendText01 Trend ruler font. Used for record time and value.
BMIngFPLText01 Smallest size and weight.
Used for: Descriptions, units, checkbox / option
button description
BMIngFPLText02 Medium size and weight.
Used for: Block / forced-, error-, simulated –indication
BMIngFPLText03 Largest size and weight.
Used for: Interlock-, Alarm-, Warning- texts and tag
names
4.2.3 Logical Colors

References to used logical colors are also given in the following Minerals Library Manuals:
· GraphiXs User Guide (3BHS 294896)
Title Overview
Document number
BMI NG Symbol 2 Colors

The logical colors definition “BMI NG Symbol 2 Colors” is used for all drive graphic
elements (MOT1, MOT1_VVVF, MOT2, MOT2_VVVF, MOTP, VLV1, VLVNO1) and DO /
DI graphic elements as well.
Logical Color Name Description
BMIngFillColorDOOff Off indication symbol fill color for DO graphic
elements. Only used when graphic element
property EnableObjectStatusColor is true.
BMIngFillColorDOOn On indication symbol fill color for DO graphic
BMIngFillColorIndCat01Dch Off indication symbol fill color for symbol indication
type category 01
BMIngFillColorIndCat01Off Off indication symbol fill color for symbol indication
type category 01
BMIngFillColorIndCat01On On indication symbol fill color for symbol indication
type category 01
BMIngFillColorIndCat01Starting On indication symbol fill color for symbol indication
type category 01
BMIngFillColorIndCat01Stopping On indication symbol fill color for symbol indication
type category 01
type category 02
type category 02
type category 02
type category 02
type category 02
type category 03
type category 03
type category 03
type category 03
type category 03
type category 04
type category 04
type category 04
type category 04
type category 04
Title Overview
Document number

type category 05
type category 05
type category 05
type category 05
type category 05
BMIngLineColorDOOff Off indication symbol line color for DO graphic
BMIngLineColorDOOn On indication symbol line color for DO graphic
BMIngLineColorIndCat01Dch Off indication symbol line color for symbol
indication type category 01
BMIngLineColorIndCat01Off Off indication symbol line color for symbol
BMIngLinelColorIndCat01On On indication symbol line color for symbol
BMIngLinelColorIndCat01Starting On indication symbol line color for symbol
BMIngLinelColorIndCat01Stopping On indication symbol line color for symbol
BMIngLinelColorIndCat02On On indication symbol line color for symbol
BMIngLinelColorIndCat02Starting On indication symbol line color for symbol
BMIngLinelColorIndCat02Stopping On indication symbol line color for symbol
BMIngLineColorIndCat03On On indication symbol line color for symbol
BMIngLineColorIndCat03Starting On indication symbol line color for symbol
BMIngLineColorIndCat03Stopping On indication symbol line color for symbol
Title Overview
Document number

Indication Type Category Indication Type

IndCat01
IndCat02
IndCat03
IndCat04
IndCat05
Title Overview
Document number
BMI NG Energy Colors

The logical colors definition “BMI NG Energy Colors” is used for the graphic element CB
and for the process symbols SingleLine and CircuitSymbol.
Line colors and symbol status colors are used as described in the table below.
BMIngCircuitBreakerOff Off symbol fill color for circuit breaker
BMIngCircuitBreakerOn On symbol fill color for circuit breaker
BMIngControlVoltageOff Control voltage line color, for status off
BMIngControlVoltageOn Control voltage line color, for status on
BMIngDisconnectorOff Off symbol fill color for isolators
BMIngDisconnetcotOn On symbol fill color for circuit breaker
BMIngEarthAndSecure Indication color for “Earth and Secure” message.
BMIngEarthingSwitchOff Off symbol fill color for earth switches
BMIngEarthingSwitchOn On symbol fill color for circuit breaker
BMIngEarthOff Earth line color, for status off
BMIngEarthOn Earth line color, for status on
BMIngHighVoltage01Off High voltage 01 line color, for status off
BMIngHighVoltage01On High voltage 01 line color, for status on
BMIngHVLine Line color for single line symbols.
BMIngLowVoltage01Off Low voltage 01 line color, for status off
BMIngLowVoltage01On Low voltage 01 line color, for status on
BMIngMediumVoltage01Off Medium voltage 01 line color, for status off
BMIngMediumVoltage01On Medium voltage 01 line color, for status on
BMIngUPSVoltageOff UPS voltage line color, for status off
BMIngUPSVoltageOn UPS voltage line color, for status on
BMIngControlVoltageOff Control voltage line color, for status off
BMIngControlVoltageOn Control voltage line color, for status on
Title Overview
Document number
BMI NG Faceplate Colors

The logical colors definition “BMI NG Faceplate Colors” is used for the PG2 Faceplates
and generic elements used for faceplates.
BMIngAlphaOffText Alpha transparency for text indication. Such as interlock
and alarm text when they are not active. Value Range is
0 = fully transparent to 255 = opaque. In case of an
active alarm / interlock, text color is always opaque.
BMIngAlphaOffTextBack Alpha transparency for text indications background.
Such as interlock and alarm text background when they
are not active. Value Range is 0 = fully transparent to
255 = opaque. In case of an active alarm / interlock, text
background color is always opaque.
BMIngButtonFillColor Button color on faceplate elements. Used for Aspect
Links, Command Button and Value Input Fields.
BMIngButtonFrameColor Button frame color on faceplate elements. Used for
Aspect Links, Command Button and Value Input Fields.
BMIngILArrowAbnormal Interlock Arrow color on alarm / interlock text lines, in
abnormal state (Interlock, Alarm or Warning is active)
BMIngILArrowNormal Interlock Arrow color on alarm / interlock text lines, in
normal state (Interlock, Alarm or Warning is not active)
BMIngTextButton Button text color on faceplate elements. Used for Aspect
Links, Command Button and Value Input Fields.
BMIngTextDynamic Text color for interlock, alarm, warning and block
indication.
BMIngTextFrame Frame color for interlock, alarm, warning and block
indication. Only used when General Property
EnableTextFrames is true.
BMIngTextNormalFillColor Text indication back color. Used for interlock, alarm,
warning and block texts. Only applied if texts
background color is not set to fully transparent
(BMIngAlphaOffTextBack = 0)
BMIngTextStatic Text color for descriptions.
BMIngTextValueOn Color for value indication on text elements.
BMIngTrendAnalogAuto Trace color: Analog auto value.
BMIngTrendAnalogIO Trace color: Analog IO value
BMIngTrendAnalogMV Trace color: Analog measured value
BMIngTrendAnalogOUT Trace color: Analog output color
BMIngTrendAnalogROC Trace color: Rate of change value
BMIngTrendAxis Trend axis and trend axis text color.
BMIngTrendBad Trace color when signals quality is bad.
BMIngTrendDigitalIO Trace color: Digital IO value
BMIngTrendDigitalMV Trace color: Digital measured value
BMIngTrendDigitalOUT Trace color: Digital output value
BMIngTrendFillColor Trend background color
BMIngTrendGrid Trend grid color
BMIngTrendPIDACT Trace color: PID actuator value
BMIngTrendPIDMV Trace color: PID measured value
BMIngTrendPIDOUT Trace color: PID output value
BMIngTrendPIDSP Trace color: PID set point value
Title Overview
Document number

BMIngTrendPIDWSP Trace color: PID Working set point value
BMIngTrendRuler Trend ruler color. Activated when mouse moves over
trend.
BMIngTrendUncertain Trace color when signals quality is uncertain
Title Overview
Document number
4.3 NLS CUSTOMIZATION

All NLS definitions can be found under Preferences & Customizations in the Library
Structure. New definitions shall also be done under this same path. Check in next
chapters how to create a project specific NLS definition.
The NLS translation when concerning to Regional Settings together with

plant workplace operations and Control Builder M engineering must be
done with care. Problems like corrupted applications, hanging operator
workplaces and failing data subscriptions to the controllers are possible
in case this work is not properly done.
Please, refer to the documents 3BSE041492 and 3BSE032791R101 before starting this
work. It is NOT recommended to start this activity during commissioning phase or in
running plants.
The next chapters are related to the configuration that can be done using the Minerals
Library.
Title Overview
Document number
4.3.1 Minerals Library NLS
F Do not create new pointers in the existing NLS aspects for Minerals Library,
only add entries in the NLS Aspects for project customization as detailed in the
next chapter.
Aspects related to the default Minerals Library NLS pointers are listed below.
Location (Object) Aspect Name Description
MineralsLib 5_0 Customization BMI NLS Resource Manager 5_0 Pointers related to almost all
indications in the faceplates and
in the graphic elements.
MineralsLib 5_0 Customization BMI NLS Alarm and Event Translator 5_0 Pointers related to the alarm
messages shown under event
lists, alarm lists and alarm lines
in the workplaces.
MineralsLib 5_0 AddOn Customization BMI NLS Resource Manager 5_0 AddOn Additional pointers for the
faceplates and graphic elements.
MineralsLib 5_0 MNSiS_MBTCP BMI NLS Alarm and Event Translator Pointers related to the alarm
Customization MNSiS_MBTCP messages for MNSiS shown
under event lists, alarm lists and
alarm lines in the workplaces.
MineralsLib 5_0_1 AddOn Customization BMI NLS Alarm and Event Translator 5_0_1 Pointers related to the alarm
AddOn messages shown under event
in the workplaces. Used for
Minerals Library release 5.0/1
and higher.
MineralsLib 5_0_1 AddOn Customization BMI NLS Resource Manager 5_0_1 AddOn Pointers related to indications on
graphic element and faceplates.
Used for Minerals Library
release 5.0/1 and higher.
MineralsLib BMI NLS Resource Manager 5_0_1 Counter Pointers related to counter
5_0_1 Counter AddOn Customization AddOn indications. Used for Minerals
Library release 5.0/1 and higher.
MineralsLib BMI NLS Resource Manager 5_1_2 IOStatus Pointers related to IO Status
5_1_2 IOStatus Customization indication on faceplates. Used
for Minerals Library release 5.1/2
and higher.
in the workplaces.
MineralsLib 5_1_4a AddOn Customization BMI NLS Resource Manager 5_1_4a AddOn Pointers related to indications on
release 5.1/4a and higher.
MineralsLib 5_1_4a AddOn Customization BMI NLS Alarm and Event Translator 5_1_4a Pointers related to the alarm
in the workplaces.
release 5.1/4a and higher.
Title Overview
Document number

in the workplaces.
MineralsLib KPI Commiss. NLS BMI KPI Comiss NLS Resource Manager Pointers related to
Commissioning Check KPI
Function in Minerals Library
MineralsLib PCC Bus BMI NLS Resource Manager PCC Bus Pointers related to PCC Bus
(Minerals PCC Viewer and
faceplates). Used for Minerals
MineralsLib PCC Bus 5_1_3 AddOn BMI NLS Resource Manager PCC Bus Pointers related to PCC Bus
(Minerals PCC Viewer and
MineralsLib PCC Bus 5_1_4 AddOn BMI NLS Resource Manager PCC Bus 5_1_4 Pointers related to PCC Bus
AddOn (Minerals PCC Viewer and
MineralsLib GroupDrive Bus BMI NLS Resource Manager GroupDrive Bus Pointers related to GroupDrive
Bus (Group Status Viewer).
MineralsLib BMI NLS Alarm and Event Translator 5_1_4 Pointers related to alarm and
5_1_4 UMC100 Customization UMC100 Customization event messages shown on the
UMC100 composite objects.
MineralsLib BMI NLS Resource Manager 5_1_4 UMC100 Pointers related to graphic
5_1_4 UMC100 Customization indication on UMC100 composite
objects.
Aspects related to project customization are listed below:

MineralsProj_AE_NLS BMI_Proj_AE_NLS Project Alarm and Event
Pointers, used for graphic
elements and faceplates.
MineralsProj_AE_NLS Project_AE_NLS_AETrans Project Alarm and Event
Pointers, related to the alarm
in the workplaces.
MineralsProj_IL_NLS BMI_Proj_IL_NLS Project Interlock Pointers, used
for graphic elements and
faceplates.
MineralsProj_IL_NLS Project_IL_NLS_AETrans Project Interlock Pointers,
related to the alarm messages
shown under event lists, alarm
lists and alarm lines in the
workplaces.
MineralsProj_NLSID BMI_Proj_NLSID Project Interlock and Alarm
Pointers, used for graphic
elements and faceplates.
MineralsProj_NLSID Project_NLSID_AETrans Project Interlock and Alarm
Pointers, related to the alarm
in the workplaces.
To customize the NLS pointers in your language, under the selected aspect, click the
button Add in Locale to define your language.
Title Overview
Document number
Now, go thru all the pointers and translate them into your language.
F Note that all your definitions will be lost in case of a library upgrade. To avoid
that, use the Resources Backup and Restore Tool as described in the Minerals
Library Upgrade Instructions.
When using NLS, a flag in the BMIConstAndVar must be set to true for all the projects.
4.3.2 Project Specific NLS Support for Interlock and Alarm messages
For some projects, it can be necessary to translate some interlock texts and alarm
messages shown in the faceplates.
As different Resources are used for the Alarm and Event List NLS than for the PG2
Graphic Text NLS, it is required to define the same pointers twice. There are 3 different
Customization Objects provided as MineralsProj_NLSID, MineralsProj_AE_NLS and
MineralsProj_IL_NLS with different Resource ID Prefixes supported in Minerals Library
Alarm Texts. In the following we assume only MineralsProj_NLSID is used and the Prefix
for all Texts is therefore “||NLSID_”.
Creating new NLS Support for Alarm and Interlock Texts in Faceplates
The standard procedure to implement NLS pointers contains the three points listed below:
1. The strings for the Interlock and alarm texts have to be defined as NLS pointers in
the Control Modules. Format is ||NLSID_<MyPointer>
2. The NLS pointers used in the control modules have to be defined in “Alarm and
Event Translator” aspects. The project specific texts shall be stored in the
“Project_NLSID_AETrans” Alarm and Event Translator aspect available under
Title Overview
Document number
the Library Structure / Preferences & Customizations / MineralsProj_NLSID.

This aspect will be used for event lists, alarm lists and alarm lines.
3. The same NLS Pointers must be defined in the same object (MineralsProj_NLSID)
in the Aspect BMI_Proj_NLSID of type NLS Resource Manager. This aspect will
be used for PG2 graphic elements and faceplates, and for the Minerals Library
Viewers like Extended Info Viewer.
F Make sure all pointers in both aspects (BMI_Proj_NLSID and

Project_NLSID_AETrans) are named the same and contain the same texts. It
is as well important to make sure that there are no duplicated Resource Keys
in the 3 MineralsProj_* Objects present!
F It is possible to use the XML Data extract option on the NLS aspects to copy all
NLS pointers from the “Alarm and Event Translator” aspect to the “NLS
Resource Manager” aspect.
Example
As an example, let’s create NLS supported texts for the interlocks of the Belt Conveyor
562-BC1.M1.
For the DIS, 562-BC1.DS1, the Alarm Text “Drift Switch” is given as NLS Resource Key
on the Parameter “AETxt”.
Note the special character “ | “, it has an ASCII code of 124.

Now let’s set the Interlock texts under the motor _562_BC1_M1 to be NLS supported:
Title Overview
Document number
It would be possible to use NLS Texts in the same way for the Alarms like M1Txt,
IOStatTxt etc. Parameters.
With everything defined, now we have to create the pointers in the library structure
Resource Aspects for defining the texts shown to the User.
Object path for NLS pointer is “[Library Structure] / Preferences & Customizations /
MineralsProj_NLSID”
1. The AE Texts need to be entered for all the used Resource Keys in
Project_NLSID_AETrans:
2. Use “XMLData” Tab Extract on the Alarm and Event Translator Aspect, and Load
the same xml file on the NLS Resource Manager Aspect BMI_Proj_NLSID:
Title Overview
Document number
The Result is matching localized Texts in all Aspects available to the Operator:
4.3.3 NLS support for Object Description

800xA allows the users to change the description of the objects to their current language
thru the NLS support under the name aspect of each object.
The new description defined will be shown in the operator workplaces when Regional
Options are set to the preferred language.
Title Overview
Document number
4.4 ALARM AND EVENT APPEARANCE CUSTOMIZATION
4.4.1 Minerals Library AE handling relations

The tables below show the relation between Minerals Library alarm treatment parameter
(LimTr, ALTr), Minerals Library indication treatment (IndTr), 800xA alarm list priority, OPC
AE severity, Minerals Library logical colors for AE and Minerals Library CBM project
constants.
Control Module instance Minerals Library global definitions

Minerals
LimTr/ Logical Colors Project AE List
Status ALTr IndTr BMI Event Colors Constants Priority Comment
no AE Handling -1 0 - - -
Modes, Status,
Control Module cBMI.AE. Forcing, Limit
Events - - BMIeventText Cmd_Sev 7 Changes
cBMI.AE.
Process Event 0 ##1 BMIevent* EV_* 6
cBMI.AE.
NotRFS 1,2,3,4 ##2 BMIalarmP1* ALP1_* 7 cBMI.Std_Type=1
cBMI.AE.
Warn Auto Ack 1 ##3 BMIalarmP2* ALP1_* 5
cBMI.AE.
Warning 2 ##4 BMIalarmP3* ALP2_* 4
cBMI.AE.
Alarm/Failure 3 ##5 BMIalarmP4* ALP3_* 3
Not supported by
cBMI.AE. MinLib default
Fatal 4 ##6 BMIalarmP5* ALP4_* 3 alarm mapping
cBMI.AE.
SigErrWarn 2 ##4 BMIalarmP3* SigErrWarn_* 4
Severity can be set
cBMI.AE. individually on
SigErr - ##9 BMIalarmP8* SigErr_* 2 each AIS
AC800 and IO cBMI.AE.
HWError - - BMIalarmSys* HWErr_* 1
Minerals Library Default Alarm Mapping Minerals Library Indication Treatment
OPC AE Severity IndTr Coding

Range 800xA AE List Priority XYZ
858 … 1000 1 X Unack Alarm
715 … 857 2 Y Value
572 … 714 3 Z AL Prio / Color
429 … 571 4
286 … 428 5 Example: 105 = Unack Alarm/Failure
143 … 285 6 4 = Acknowledged Warning
0 … 142 7
Title Overview
Document number
4.4.2 NLS, AE and Event Log Project Constants

Some Project Constants can be changed per Control Project to customize the Alarm and
Event Appearance and Message Texts.
Note that most Control Modules additionally have their own Project Constants for Alarm
and Event Messages, which are described in the respective Sections in the other
Manuals.
NLS Project Constants

Below constants are related to the Alarm and Event NLS handling, and do not need to be
changed with the exception of AE_NLS_Used. See also Section Project Specific NLS
Support for Interlock and Alarm messages_Project_Specific_NLS
Name Data Type Default Value
1 cBMI.AE.AE_NLS_Empty_Str string (string): ' '
2 cBMI.AE.AE_NLS_Preffix string (string): '||AE_NLS_'
3 cBMI.AE.AE_NLS_Space string (string): '_'
4 cBMI.AE.AE_NLS_SubMessageSpace string (string): '_'
5 cBMI.AE.AE_NLS_Used bool (bool): False
6 cBMI.AE.AE_NLS_Var1 string (string): '{1}'
7 cBMI.AE.AE_NLS_Var2 string (string): '{2}'
8 cBMI.AE.AE_NLS_Var_Delim string (string): '\'
9 cBMI.AE.IL_NLS_Preffix string (string): '||IL_NLS_'
AE Project Constants
Below Constants define the Severity and Acknowledge Rule (1= Normal, 2 = Auto Ack),
for Alarms generated by the Control Modules. Only change these constants if you have a
good reason to do so.
The Suffix Texts are added to the Alarm Messages and can be customized.
Note that these Text Strings are only added to the Alarm Messages if no NLS is used for
Alarm Messages (AE_NLS_Used is set to false). Else, the texts are customized later via
Alarm and Event Translator Aspects anyway.
1 cBMI.AE.AlarmTr dint (dint): 3
2 cBMI.AE.ALP1_AckRule dint (dint): 2
3 cBMI.AE.ALP1_Sev dint (dint): 300
4 cBMI.AE.ALP1_SubTxt string (string): 'Warning'
7 cBMI.AE.ALP2_SubTxt string (string): 'Warning'
10 cBMI.AE.ALP3_SubTxt string (string): 'Failure'
11 cBMI.AE.Cmd_Sev dint (dint): 100
12 cBMI.AE.EV_AckRule dint (dint): 2
13 cBMI.AE.EV_Sev dint (dint): 200
14 cBMI.AE.EV_SubTxt string (string): 'Event'
15 cBMI.AE.FB3XFail_Frc_SuffixTxt string (string): ‘Frc X’
16 cBMI.AE.FB3XFail_Off_SuffixTxt string (string): ‘Off X’
17 cBMI.AE.FB3XFail_On_SuffixTxt string (string): ‘On X’
18 cBMI.AE.FB3XFail_Trip_SuffixTxt string (string): ‘Trip X’
19 cBMI.AE.FB3YFail_Frc_SuffixTxt string (string): ‘Frc Y’
20 cBMI.AE.FB3YFail_Off_SuffixTxt string (string): ‘Off Y’
21 cBMI.AE.FB3YFail_On_SuffixTxt string (string): ‘On Y’
22 cBMI.AE.FB3YFail_Trip_SuffixTxt string (string): ‘Trip Y’
23 cBMI.AE.FBFail_Frc_SuffixTxt string (string): ' Frc'
24 cBMI.AE.FBFail_Off_SuffixTxt string (string): ' Off'
Title Overview
Document number

25 cBMI.AE.FBFail_On_SuffixTxt string (string): ' On'
26 cBMI.AE.FBFail_Trip_SuffixTxt string (string): ' Trip'
27 cBMI.AE.GCCComErrTxt string (string): ‘GCC Com’
28 cBMI.AE.HWErr_AckRule dint (dint): 1
29 cBMI.AE.HWErr_AlarmSubText string (string): 'Alarm'
30 cBMI.AE.HwErr_FailSubText string (string): 'Failure'
31 cBMI.AE.HWErr_Sev dint (dint): 950
32 cBMI.AE.HWErr_WarnSubText string (string): 'Warning'
33 cBMI.AE.InterlockTr dint (dint): 3
34 cBMI.AE.NotRDY_SubTxt string (string): 'not RFS'
35 cBMI.AE.SigErr_AckRule dint (dint): 1
36 cBMI.AE.SigErr_Sev dint (dint): 800
37 cBMI.AE.SigErrWarn_AckRule dint (dint): 1
38 cBMI.AE.SigErrWarn_Sev dint (dint): 550
39 cBMI.AE.SigErrWarnTr dint (dint): 2
Log Text Project Constants

Below strings define the Event Messages and must not be changed. Customization shall
be made in the BMI NLS Alarm and Event Translator Aspects see Minerals Library default
NLS usage and changing._Minerals_Library_default
1 cBMI.LogTxt.Aut string (string): 'AUT'
2 cBMI.LogTxt.Bal string (string): 'BAL'
3 cBMI.LogTxt.Blk string (string): 'Blk:'
4 cBMI.LogTxt.Cen string (string): 'CEN'
5 cBMI.LogTxt.Change string (string): '-->'
6 cBMI.LogTxt.Cmpl string (string): 'Cycle Completed'
7 cBMI.LogTxt.ConfigError string (string): 'Configuration Error'
8 cBMI.LogTxt.CSP string (string): 'CSP'
9 cBMI.LogTxt.Dbl string (string): 'DBL'
10 cBMI.LogTxt.Deselected string (string): 'Deselected'
11 cBMI.LogTxt.Dev_H_Txt string (string): 'Dev_H'
12 cBMI.LogTxt.Dev_L_Txt string (string): 'Dev_L'
13 cBMI.LogTxt.E1 string (string): 'E1'
14 cBMI.LogTxt.ExtAuto1 string (string): 'EA1'
15 cBMI.LogTxt.ExtAuto2 string (string): 'EA2'
16 cBMI.LogTxt.ExtMan1 string (string): 'EM1'
17 cBMI.LogTxt.ExtMan2 string (string): 'EM2'
18 cBMI.LogTxt.FB1 string (string): 'FB1'
19 cBMI.LogTxt.FB2 string (string): 'FB2'
20 cBMI.LogTxt.FB3X string (string): 'FB3X'
21 cBMI.LogTxt.FB3Y string (string): 'FB3Y'
22 cBMI.LogTxt.Frc string (string): 'FRC'
23 cBMI.LogTxt.FSP string (string): 'FSP'
24 cBMI.LogTxt.HighLoad string (string): 'High Load'
25 cBMI.LogTxt.Hold string (string): 'Hold'
26 cBMI.LogTxt.IA string (string): 'IA'
27 cBMI.LogTxt.IAX string (string): 'IAX'
28 cBMI.LogTxt.IAY string (string): 'IAY'
29 cBMI.LogTxt.IB1 string (string): 'IB1'
33 cBMI.LogTxt.IBX string (string): 'IBX'
34 cBMI.LogTxt.IBY string (string): 'IBY'
35 cBMI.LogTxt.IC string (string): 'IC'
36 cBMI.LogTxt.ICX string (string): 'ICX'
37 cBMI.LogTxt.ICY string (string): 'ICY'
38 cBMI.LogTxt.Interlock string (string): 'IntL'
39 cBMI.LogTxt.IOS string (string): 'IOS'
40 cBMI.LogTxt.Limit string (string): 'Limit'
41 cBMI.LogTxt.Loc string (string): 'LOC'
Title Overview
Document number

42 cBMI.LogTxt.Man string (string): 'MAN'
43 cBMI.LogTxt.ME string (string): 'ME'
44 cBMI.LogTxt.MMS_COM string (string): 'ComError'
45 cBMI.LogTxt.Mtc string (string): 'MTC'
46 cBMI.LogTxt.Next string (string): 'Next'
47 cBMI.LogTxt.NoBlockings string (string): '-'
48 cBMI.LogTxt.Off_Txt string (string): 'OFF'
49 cBMI.LogTxt.On_Txt string (string): 'ON'
50 cBMI.LogTxt.Out string (string): 'OUT'
51 cBMI.LogTxt.PD string (string): 'PD'
52 cBMI.LogTxt.PDX string (string): 'PDX'
53 cBMI.LogTxt.PDY string (string): 'PDY'
54 cBMI.LogTxt.PosCls string (string): 'Cls'
55 cBMI.LogTxt.PosOpn string (string): 'Opn'
56 cBMI.LogTxt.PosX string (string): 'PosX'
57 cBMI.LogTxt.PosY string (string): 'PosY'
58 cBMI.LogTxt.Prog string (string): 'Prog'
59 cBMI.LogTxt.PSP string (string): 'PSP'
60 cBMI.LogTxt.QSP string (string): 'QSP'
61 cBMI.LogTxt.QStop string (string): 'QuickStop'
62 cBMI.LogTxt.Run string (string): 'RUN'
63 cBMI.LogTxt.Run1 string (string): 'RUN1'
64 cBMI.LogTxt.Run2 string (string): 'RUN2'
65 cBMI.LogTxt.Selected string (string): 'Selected'
66 cBMI.LogTxt.Seq string (string): 'SEQ'
67 cBMI.LogTxt.SeqTime string (string): 'Sequence Time Exceeded'
68 cBMI.LogTxt.Skipped string (string): 'Skipped'
69 cBMI.LogTxt.SPExt string (string): 'SPExt'
70 cBMI.LogTxt.SPInt string (string): 'SPInt'
71 cBMI.LogTxt.SSP string (string): 'SSP'
72 cBMI.LogTxt.Start1_ILK string (string): 'Start1'
76 cBMI.LogTxt.Starting string (string): 'Starting'
77 cBMI.LogTxt.Step string (string): 'Step'
78 cBMI.LogTxt.Stop1_ILK string (string): 'Stop1'
82 cBMI.LogTxt.Stopping string (string): 'Stopping'
83 cBMI.LogTxt.UnkPos string (string): 'UNK'
84 cBMI.LogTxt.Valid string (string): 'Valid'
85 cBMI.LogTxt.Value string (string): 'Value:'
Title Overview
Document number
4.4.3 User Permission Configuration

User Permission in 800xA may be changed by using the “Property Attribute Override”
Aspect. This aspect can be placed on individual objects e.g. in the Control Structure or in
case all objects of a certain type shall be changed directly in the Object Type Structure.
Step 1: Create a Property Attribute Override Aspect on the object you want to change
user permissions:
Title Overview
Document number
Step 2: Select the property you like to change the user permission. All Faceplate
changeable properties in the Minerals Libarry start with IntPar.xxxx (Inter Action
Parameter)
Step 3: Change the Write Permission property as required.
Title Overview
Document number
5. PROGRAM STRUCTURE
This Section defines Rules and Considerations for Control Applications engineered with
Minerals Library. These are not always required to be followed but considered best
practice.
5.1 Application and Diagram Structure with Minerals Library

Minerals Library Control Modules and Function Blocks are designed to be used together
with Diagrams. Single Control Modules are still supported as well for upgrades and
extensions of existing Projects.
The Code shall be divided into Diagrams as per the Logical Structure of the Devices in the
Startup Sequence defined.
Physical Entity Entity in CBM
Plant Area Application
Group Sequence Diagram
Drive Diagram Page
Signals and Glue On the Diagram Page of the corresponding Drive , or on additional
Logic pages in front of the Drive Page if there are many Signals
The maximum Size of a Diagram in CBM is 100 Pages and 30 Objects (Control Modules,
Function Blocks, Functions) per Sheet. We recommend to put a maximum of 1 Consumer
(MOTx) combined with 3 Signals, or 6 Signals (AIS/DIS) on a Page.
We recommend to limit the size of an Application to have 2 Applications on PM866 and 3
Applications on the PM891 Controllers.
5.2 Parameters and Variables

The “Name” and “Description” Parameters on the Blocks are used by the “Name
Uploader” in 800xA to define the Object Name Aspect in the Control System. The Name
of the Object in needs to match with the Name Parameter and shall be unique in the
whole System as it is used for the Faceplate Links and References. The same Parameter
is used for the Alarm Condition Name as well therefore only a limited set of special
Characters is supported.
Variables should only be defined when they are required for connection to Hardware. All
other Parameters are defined with Initial Values in the Library. The AIS and DIS Blocks do
require a Variable for the IO Parameter, similar the Interface Parameter on Serial Interface
Object like MOT1VVVF_ACS8x0. The IO Parameter on a Consumer Block only needs to
be defined if the Interface to a Process Panel is required. This helps to minimize the
Blocks and Connections on the Diagram.
Communication Variables should use simple (not structured-) data types. This is to
simplify the application download after a change if multiple Controllers are involved. As a
rule of thumb, an entity that has a Tagname (e.g. Signal) should be a separately defined
Communication Variable.
Title Overview
Document number
5.3 Group and Process Control Connections
5.3.1 Overview
· Software Modules in the Minerals Library are able to exchange data on predefined
interface so called control connections – (data highway)
o The status form child objects are always reported to the parent object and vice versa
o Commands can be sent from parents to children and from children to parents
· Group Control Connection – GCC

o Executes the start and stop of consumers connected to the group in a given or dynamic
start / stop order
o Summarizes to status of all connected consumers and indicates it on the group object
o Pre-Selection objects for parameterized routing and duty standby applications
· Process Control Connection – PCC

o Connects consumer objects with their interlocking and process control signals
o Parameters on the signal modules define the interlock between the signal and the
consumer
o The operational status of the consumer is used to define the alarm behavior of the signal
PCC
Bus
Group
Selectors AIS
Routing
Duty/ Standby
Motor
DIS
AIS
GCC Motor
Bus DIS
AIS
PID
DIS
Title Overview
Document number
5.3.2 Control Builder Connections

The illustration below shows the relevant variable connections and parameter settings for GCC and PCC connections.
AI / DI
Group
Motor / PID / Valve
Title Overview
Document number
5.4 800xA Functional Structure

With the Application Program defined in CBM, the Objects will automatically be
instantiated into the Control Structure in 800xA matching the Program Structure. But
800xA consists of multiple Structures and allows to “insert” existing Objects into multiple
Structures
For Minerals Library, this Feature is used to document the actual Functional Structure of
the Control Program as defined by the PCC and GCC Bus Connections,
The following Figure shows an example Functional Structure Configuration:
In this Structure, any Signal Object Interlocking a Consumer via PCC Bus shall be placed
under the Consumer Object, and any Consumer started or stopped by a Group Sequence
shall be placed as a Child under the Group Sequence Object in Functional Structure.
Following Features are enabled by creating this additional Tree structure:
· Alarm List Filtering: By default the Alarm List will show Alarms for the Object and
all its Children from all Structures. Therefore, a Consumer Alarm List can show all
Alarms of Signals that it interacts with.
· Minerals Library Viewers: The PCC Viewer, Group Step Viewer and Status Viewer
require the Functional Structure to be configured according the Application
Program Structure.
5.4.1 Functional Structure Uploader

To create the Structure as required, the existing Program Structure can be read out via
OPC Data Connection. Note that this Operation reads the Tagnames transferred via the
PCC and GCC Bus and therefore requires both a completed Name Upload and Unique
Names for all Control Modules and Function Blocks in order to find the relations between
the blocks.
When this is fulfilled, the Functional Structure Upload Tool that is installed together with
Minerals Library can be used to automatically create the Structure. This Tool can be
accessed via the System 800xA Configuration Console under the “Minerals Library” Menu
Option.
Title Overview
Document number
This opens the “Minerals Library Functional Structure Uploader” Tool, that accesses
“Minerals Library Automatic Upload” Object placed under the Functional Structure Root:
The Functional Structure Upload consists of a Single Window divided into 4 Areas.
· Project/Application Selection. Here the Control Application can be selected to limit
the Upload to its children in Control Structure only.
Title Overview
Document number
· The Tree View shows the differences between the actual Functional Structure and
the Control Application Code as uploaded via OPC. Changes are marked with
Colors:
o Green: Object is in Application Code but not in Functional Structure
o Yellow: Object is in Functional Structure but not in Application Code
o Gray or Pink: Object Tagname is not found in 800xA or not yet initialized
o White (no color): Object is existing in both Application and Functional
Structure
· In the Button Area, the Upload can be executed in three Steps:
o Load Objects – this populates the Difference View by reading both the
Functional Structure in 800xA and Upload the OPC Values from the
selected Control Structure Objects
o Insert Added Objects – this adds all selected new Objects (green) into
Functional Structure
o Delete Obsolete Objects – this removes all selected removed Objects
(yellow) from Functional Structure
· The Status Box prints Log Messages and Errors about the Upload
Note that while the Uploader allows to select a part of the Control Structure only, always
the complete Functional Structure is uploaded to the Tool. Therefore parts of the
Functional Structure will be marked Obsolete if they are defined in Control Applications
not selected for Upload but have been created during earlier Upload Operations already.
In this case the User needs to take care to select only the required Objects for removal by
clearing the checkboxes of the Objects that shall be kept before the “Delete Obsolete
Objects” Step.
Title Overview
Document number
5.5 Code Sorting

The following diagram shows the interactions between the most common objects in the Minerals Library. It is very
important to understand how the code sorting works in the minerals library objects if the functionality shall be enhanced
with own Control Modules. Sort order is from left to right:
The lines and text in blue means the connection between the blocks thru logic connection, if exists. The lines in green
means the connection between the blocks thru the Group-Drive bus. And finally the lines in brown means the
connection between the blocks through PCC bus.
Title Overview
Document number
5.6 Settings in Control Builder M
5.6.1 Task Definitions

In general, all Blocks in one Diagram shall be executed in the same Task. All Blocks with
Connection to the same GCC or PCC Bus are required to be executed in the same Task
in order to work correctly.
The Library Blocks use pre-defined External Variables as Task Names assigned to
internal Control Modules for parts that should be executed in Tasks different to the Task of
the Diagram. Following Table shows the different Tasks that need to be defined:
Task Recommended Recommended Usage
Name Period Time Priority
Fast 50 2-High LCB (BMIAdaptions)
ConPu 250 2-High Pulse Control (MOTP, PIDCtrl)
Normal 500 3-Normal Normal Task as used for the
Application / Diagram itself
(MNSiS Library Only)
ModBus Dep. on Interface 1-Highest Serial Interface (REF542Plus,
MNSiS)
PreBin 2000 5-Lowest Preselection String Evaluation
(MOTx, PreBin)
These Tasks are mapped to the Library Blocks via Global Variables on the Application
holding the Name of the actual Task on the Controller. For a Controller with Name N1 and
Task Names as per the Default given above this results in the following Global Variable
that need to be defined on the Application:
Name Data Type Attributes Initial Value
FastTask string constant ‘N1.Fast’
ConPuTask string constant ‘N1.ConPu’
NormalTask string constant ‘N1.Normal’
ModBusTask string constant ‘N1.ModBus’
PreBinTask string constant ‘N1.PreBin’
5.6.2 CBM Compiler Switches

In the Project Settings - Compiler Switches, the option “Multiple calls to the same Function
Block” should be allowed for the Minerals Libraries, as there are multiple cases in the
Library Modules were this has been used to reduce the memory footprint. This can be
done by setting the Level for Global to “Allowed” or marking all the Libraries with names
starting with “BMI” as excluded for the check as visible in the following Screenshot.
Title Overview
Document number
Title Overview
Document number
6. DOCUMENT REVISION HISTORY

Rev. Page (P) Description Date/Initials
ind. Chapt. (C)
- Initial Version (Draft) 22.08.2002/KN
A Corrections after training
B Corrections in MMS, AIC, AOC, DIC, DOC, GrpCycleCtrl 12.10.2002/KN
C Compressed according to new document concept of dept. ATBA 14.05.2003/PVG
D Some Programming hints added 28.05.2003/KN
E Language corrections 24.07.2003/GPC
F Update for Minerals Library Release 2.0/1 09.09.2003/GPC
G Update for Minerals Library Release 2.1/1 05.04.2004/GPC
H Update for Minerals Library Release 3.1/1 11.07.2004/GPC
I Update for Minerals Library Release 4.0/0 27.05.2005/HT
J Update for Minerals Library Release 5.0/0 16.01.2006/N.B
K Added customization chapter 13.09.2006/WSV
L - Improved NLS customization part for Release 5.0/1 21.06.2007/WSV
- Added process panel for Release 5.0/1 27.06.2007/MB
M - NLS hint for performance improvement 5.0/1 SP1 09.08.2007 / KN
N Update for Minerals Library Release 5.0/2 05.11.2008 / LK
O Added cBMI.AE Project Constants Description 07.04.2009 / LK
P Customization Options for 5.1/0 PG2, new Abbreviations 10.07.2009/KN, LK
Q Customization Options for 5.1/1 PG2 10.11.2009/MS
R Updated with new PCC concept for 5.1/2 26.03.2010/CT
S Update for Minerals Library Release 5.1/3 25.10.2010/CT
T Update for Minerals Library Release 5.1/3a 23.03.2011/CT
U all Update for 5.1/4, Removed Code Structure examples for SCMs 03.05.2013/LK
V 4.6 Update for 5.1/4a, remove GDI Limit description 15.09.2013/LK
W all Update for 5.1/5, updated Program Structure 13.08.2013/LK
X 4,5 Remove VB Customization Description 30.01.2015/LK
Add Function Structure Description and Uploader
Y 3.3, 3.6 Add new Loop Objects for Release 5.1/5b 07.05.2015/LK
Z Formal changes for Release 6.0 23.08.2016/GS
AA 4.3 Update for Release 6.0-3, Clarify NLS handling 24.10.2018/LK
Title Overview
Document number

Reference Manual: 800xa - AC800M Connect - Minerals Library

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

Reference Manual: 800xa - AC800M Connect - Minerals Library

Uploaded by

Copyright:

Available Formats

We reserve all rights in this document and in the information contained therein.

800xA - AC800M Connect - Minerals Library

Based on Project Minerals Library, CoE Cement and Minerals

800xA Minerals Library Version 6.0/3 Resp. dept. CHIND / PIMIN-PD

1.1 SOFTWARE MODULE TYPICALS

1.2 DOCUMENT ORGANISATION

Project Documentation Documentation Guideline

Configuration Standard Minerals Library

Figure 1 Document Organisation

2. DEFINITIONS AND ABBREVIATIONS

3.1 BASIC OBJECTS

Reference Table: Basic Objects for calculated IO-signals

Reference Table: Basic Objects for PCC

Name Type Function Data Type

3.2 COMMUNICATION OBJECTS

3.3 CONSUMER OBJECTS

MOTP CM The Control Module Type MOTP is used to control MOTPData

VLV1 CM The Control Module Type VLV1 is used to control a VLV1Data

3.4 GROUP OBJECTS

3.5 LOOP OBJECTS

PIDAdvCtrl CM PID loop controller with advanced Features like PIDAdvCtrlData

3.6 DOSING OBJECTS

3.7 POWER MONITORING OBJECTS

3.8 REPORT OBJECTS

3.9 COMPOSITE OBJECT TEMPLATES

MOT1_MNSIS Composite CM ABB MNS iS MCC with MOT1_MNSISData

4.1 LOOK AND FEEL

Minerals Standard: The Classic Minerals Library look and feel

Holcim Standard: Holcim standard requirements

Hybrid Standard: Minerals Style with brighter Background Color

VALE Standard: VALE Standard requirements

ASM White: Alarm Status Monitoring look and feel

ASM Green: Alarm Status Monitoring with pastel green color

4.1.1 How to change between different standard types

1. Browse to “[ObjectType Structure] Object Types / ABB System / Process Graphics

4.2 PG2 EXPERT USER GRAPHIC APPEARANCE CUSTOMIZATION

4.2.1 Workplace Specific Settings

Name Description Range Default Value

BMIngAlpha Alpha transparency for BMI Process 0 … 255 255

Name Description Range Default Value

4.2.2 Object Specific Settings

Analog and PID Appearance

Analog / PID Value and Unit Font Bold

Group Background Appearance

Direct Entry Control

Standard and Extended Direct Entry Window

invokes on left mouse click invokes on right mouse click

Actual value and input value.

Click: Increase one step

Use either the up/down-buttons, the

If the desired input value is not valid, a

PID Presentation Options

Analog / PID Alarm Appearance

Group Alarm and not Ready Appearance

DrvNotReady and NotReady can be disabled individually per instance as well.

Drive not Ready Appearance

3 = Thin Frame symbol off color symbol run color

4 = Arrow symbol off color symbol run color

5 = Cross symbol off color symbol run color

6 = Slash symbol off color symbol run color

101 = Apply to Symbol (on) symbol on with symbol on with

101 = Apply to Symbol

Font Name Description