3BSE079156-600 AC 800M 6.0 Burner Library Safety and User Manual PDF

AC 800M
Burner Library
Safety and User Manual
System Version 6.0
Power and productivity

for a better world™
AC 800M
Burner Library
Safety and User Manual
System Version 6.0

NOTICE
This document contains information about one or more ABB products and may include a description
of or a reference to one or more standards that may be generally relevant to the ABB products. The
presence of any such description of a standard or reference to a standard is not a representation that
all of the ABB products referenced in this document support all of the features of the described or ref-
erenced standard. In order to determine the specific features supported by a particular ABB product,
the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property
in the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as
a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate
information and data via a secure network. It is the sole responsibility of the system/product owner to
provide and continuously ensure a secure connection between the product and the system network
and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not lim-
ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-
tion of antivirus programs, and so on, to protect the system, its products and networks, against security
breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.
ABB verifies the function of released products and updates. However system/product owners are ulti-
mately responsible to ensure that any system update (including but not limited to code changes, con-
figuration file changes, third-party software updates or patches, hardware change out, and so on) is
compatible with the security measures implemented. The system/product owners must verify that the
system and associated products function as expected in the environment they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any
nature or kind arising from the use of this document, nor shall ABB be liable for incidental or conse-
quential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from
ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-
pose.
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license. This product meets the require-
ments specified in EMC Directive 2014/30/EU and in Low Voltage Directive 2014/35/EU.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2014-2016 by ABB.

All rights reserved.
Release: April 2016

Document number: 3BSE079156-600
Safety Summary
Electrostatic Sensitive Device

Devices labeled with this symbol require special handling precautions as
described in the installation section.
GENERAL Equipment Environment

WARNINGS All components, whether in transportation, operation or storage, must be
in a noncorrosive environment.
Electrical Shock Hazard During Maintenance

Disconnect power or take precautions to insure that contact with ener-
gized parts is avoided when servicing.
SPECIFIC Warnings related to About This User Manual on page 17

WARNINGS
The End-User shall comply with all restrictions and conditions for the
safety system that is provided by the Safety Manuals or by other manda-
tory documents referred to by the Safety Manual. This includes all
aspects of installation, configuration, operation and maintenance. on
page 17
3BSE079156-600
Safety Summary (continued)
SPECIFIC Warnings related to System and Software Requirements on page 31

WARNINGS
The development process for the Burner application/management appli-
(continued)
cation shall comply with the requirements of the related standards and
regulations, e.g. with IEC 61508 2nd edition SIL3. The correct implemen-
tation shall be subject of a functional validation. on page 31
All persons involved in the use of the Burner Library shall have sufficient
competence in their associated activity and shall have enough safety
knowledge about the AC 800M HI safety system. on page 31
It is assumed that the application software is subject to safety analysis to

determine the level of reliance of the Burner Lib Function Blocks. Safety
measures might be required to ensure the safety integrity of the applica-
tion software. For security reasons an additional thread analysis might be
required. on page 31
Never use AC 800M High Integrity software- or hardware components,

that are not covered by the TÜV SÜD certificate/TÜV SÜD letter of confor-
mance or the DGC certificate covering the Burner related safety stan-
dards, within the safety system used in Burner applications. The
construction of any additional functions included in the system, program-
ming unit or flame detector device for which no provisions exist, shall be
such that they do not degrade the safe and correct operation of the sys-
tem, programming unit or flame detector device. on page 32
The hints and warnings for recommended use of the Safety and User
Manual shall be considered for parametrization and for integration of the
function blocks into the user program, as well as for installation, commis-
sioning, operation and validation. on page 32
The Burner Library is capable for the use in SIL3 (or lower) applications.
The Burner Library makes use of "SIL restricted" functionality for the
alarm and event functionalities, which may not be used to be part of any
safety related control loop. on page 32
6 3BSE079156-600
SPECIFIC Warnings related to Recommended use on page 70

WARNINGS
Always set the Fault Detection and Reaction diagnostics cycle to <2 sec-
(continued)
onds for burner applications. This will lead to an allowed warning (FDRT
time below default value) in the Task Analysis tool. FDRT (Fault Detection
and Reaction Time) is the maximum time from an internal error occur in
the controller, to the defined action is taken. on page 70
The Start-up sequence may only occur if the potential source for the
cause of the safety-shut-down conditions disappears. Connect the safety
shut-down conditions to PriorityCmdStop. on page 70
Always make the interval between safety-shutdown and the next start
attempt to >30 seconds for oil burner control systems which are not pro-
vided with a pre-purge function. on page 70
The start flame proving period shall be no less than that declared by the
manufacturer. Configure the pilot flame proving period to Config.Pilot-
FlameProvingTime. Configure the main flame proving period to Con-
fig.MainFlameProvingTime. on page 70
If the lock-out function is used it shall be checked for proper operation

during each start-up sequence. The capability of the burner control sys-
tem to store the non-volatile lock-out status shall be checked at least
during each main power restoration. Connect the lock-out function to
StartCond on page 70
The application shall implement the Start Condition for the burner start in
accordance with EN 12952-8, EN 746-2 and EN 12953-7. In case of an
abnormal situation the application shall interrupt the 'Burner' function
block by use of the Priority Stop command. on page 70
The application shall implement the shutdown of a burner in accordance

with EN12952-9, EN 746-2 and EN 12953-7 using the Start Condition,
stop and priority stop command of the 'Burner' function block. on page 70
3BSE079156-600 7

WARNINGS
External flame detector devices shall conform to EN 298 for permanent
(continued)
operation. Their flame failure response time shall not exceed 1 second. on
page 71
The function block ‘Burner’ shall be configured such that reaction on loss
of flame during start or during operation conforms to the applicable func-
tional requirements of the individual application. on page 71
During online download (normal application update or Load Evaluate Go),

the user shall take appropriate precautions dependent on the properties
and the time demands of the process under control. on page 71
The parameter Config.CheckFlameGuardsBeforeStart needs to be set to

true always, except when a specific standard can be pointed out to state
the contrary. on page 71
The supervision of the success of closing the FuelValve1 (at the begin-
ning of the Cleaning sequence) is in the users responsibility. on page 71
It is not allowed to connect the same flame guard to the parameters

FlameGuardPilot and FlameGuardMain as the function block expects
separate flame guards. If only one flame guard is used it is necessary to
add logic to at least one of the parameters. This logic is the users respon-
sibility. on page 71
8 3BSE079156-600

WARNINGS
Always set the Fault Detection and Reaction diagnostics cycle to <3 sec-
(continued)
onds for Tightness Test applications. FDRT (Fault Detection and Reaction
Time) is the maximum time from an internal error occur in the controller,
to the defined action is taken. on page 84
Set the parameter Config.TestTime to the leakage testing time as

declared by the manufacturer. on page 84
The response time to achieve safety shutdown, whenever this is required,

shall not exceed 1 second after a functional failure has been detected.
Connect the functional failure conditions to PriorityCmdStop. on page 84
After a fault is detected the valve proving system shall execute safety
actions according to EN1643. on page 84
It is the responsibility of the application engineer and implementation of

the burner management system to set the correct pressure limits and
reaction time for the Tightness Test. on page 84
Depending on the volume between the main gas valves, the gas pressure
and the set points of the gas pressure monitoring device, the leakage
testing time must be adjusted in a way that a leakage rate of 0,1 % of the
burner heat input, at least 50 dm³/h, will be safely detected. on page 84
A leak gas flow rate of 0,1 % of the nominal volume flow at maximum fir-
ing rate, but at least 50 dm³/h, shall be safely detected. on page 84
The application shall implement diagnostics of the pressure switches. on

page 84
It is the responsibility of the application engineer to define the amount of

Gas used during the tightness test. Limits are defined for discharging into
the combustion chamber according to EN1643. on page 84
3BSE079156-600 9

WARNINGS
All the input values must be of the right unit for the calculation to be cor-
(continued)
rect. For example, all gas flows are in Nm3. If the measured values are of
different units, the values must be corrected to the right measure units
before connected to the function block. on page 92
There is one high limit and three low limits; low, lowlow and lowlowlow for
the lambda value, which are all configurable. If the calculated lambda
value is outside of these limits, the function block will set the LambdaError
signal and generate an alarm for the condition. on page 92
To enable the supervision and the calculation it is necessary to set the

parameter Enable to true. When the input Enable is set to false the super-
vision will be disabled and the output value set to the Config.Predeter-
minedValue. on page 92
Warnings related to Recommended use on page 100
The setting of both the Config.DeviationLimit and the Config.DelayTime

shall be in accordance with the requirements for the specific application.
on page 100
The discrepancy timer shall be taken into account for the Fault Detection
and Reaction time of the related safety loop. on page 100
Warnings related to Recommended use on page 105
The Config.DiscrepancyTime shall be taken into account for the Fault

Detection and Reaction time of the related safety loop. on page 105
10 3BSE079156-600
SPECIFIC Warnings related to Safety precautions on page 107

WARNINGS
The application shall be in accordance with the details provided by the
(continued)
manufacturer's instructions. on page 107
The application shall implement the Lock Out function and the process to
restart the system. This includes for instance the mandatory use of man-
ual reset devices for a restart. on page 107
The application shall implement functionality in accordance with EN 267:

“In the case of permanent loss of the actuating energy the burner shall
proceed to a safe condition. If an on/off control, switch or limiter operates,
the fuel oil supply shall be automatically cut off immediately.“ on page 107
As far as practicable the application design shall minimize the

safety-related part of the software. This means that the End User shall as
far as possible, split safety and non-safety functions in different applica-
tions. on page 107
If external safety devices are used, the application shall be able to pro-
cess a requested shutdown independent from the actions of the Burner
Library elements. on page 107
The sum of the safety times and the closing time of the shut off valve/final
element shall be less than the fault tolerance time of the relevant process
function. This fault tolerance time shall be defined by the End User and in
compliance with the relevant application standard, the configurable safety
times according to applicable standards and the application cycle times
have to be adjusted accordingly. on page 108
Reset from lock-out shall be implemented in the external safety logic such
that static or dynamic failures of the reset device do not cause the system
to operate outside the requirements of the applicable standards or regula-
tions (e.g. by evaluating the logical and temporal properties of the reset
signal). on page 108
3BSE079156-600 11
SPECIFIC Warnings related to Safety precautions on page 107

WARNINGS All safety functions of the individual application which are not covered by
(continued) the function blocks (such as purging, protection of the heat generator, flue
gas discharge, fuel system, etc.) shall be implemented in the external
safety logic according to the requirements of the applicable standards or
regulations. on page 108
It is the users responsibility to check the ParError outputs of each function

block and make appropriate and necessary actions in case an error is
indicated by these outputs. on page 108
The configuration parameters of all function blocks shall be confirmed

(including the default values) by the users. on page 108
The error output from any function blocks shall be treated by the safety
application to react on the detected error appropriately. on page 108
12 3BSE079156-600
Table of Contents
Table of Contents
Safety Summary ................................................................................................................5
About This User Manual

General ............................................................................................................................17
User Manual Conventions ...............................................................................................18
Warning, Caution, Information, and Tip Icons ....................................................18
Terminology.....................................................................................................................19
Applicable Specifications ................................................................................................20
General Safety Standards .....................................................................................20
Application Standards (to the extent applicable) .................................................21
Gas Appliance Directive (GAD) ..........................................................................22
Related Documentation ...................................................................................................23
Section 1 - Burner Management Introduction

Burner Management Systems Defined ............................................................................25
Functionality ........................................................................................................26
Trip Causes...........................................................................................................27
Using AC 800M High Integrity as a BMS ......................................................................28
Burner Management Library................................................................................29
Combined Safety and Control ..............................................................................30
High Integrity Instrumentation.............................................................................30
Section 2 - System and Software Requirements

Processes..........................................................................................................................31
Personnel .........................................................................................................................31
Risk Mitigation and Impact Assessments........................................................................31
Software and Hardware ...................................................................................................32
SIL Restrictions with Burner Library..............................................................................32
3BSE079156-600 13
Table of Contents
Section 3 - Library Overview

Introduction to Burner Library........................................................................................ 33
Dependencies to other Objects and Libraries.................................................................. 35
Field Connection ............................................................................................................. 36
Feedback Objects ................................................................................................. 36
Single Analog Input ............................................................................................. 36
2oo3 Analog Inputs.............................................................................................. 36
Single Boolean Input ........................................................................................... 36
Complementary Boolean Inputs .......................................................................... 36
Memory Usage and Execution Times ............................................................................. 36
Section 4 - Function Block Types

Burner ............................................................................................................................. 39
Parameters............................................................................................................ 42
Configuration ....................................................................................................... 47
Functionality ........................................................................................................ 49
Alarms and Errors ................................................................................................ 67
Recommended use ............................................................................................... 70
TightnessTest................................................................................................................... 72
Parameters............................................................................................................ 73
Configuration ....................................................................................................... 75
Functionality ........................................................................................................ 76
Recommended use ............................................................................................... 84
Lambda............................................................................................................................ 85
Parameters............................................................................................................ 86
Configuration ....................................................................................................... 89
Functionality ........................................................................................................ 90
Recommended use ............................................................................................... 92
RealIn2oo3 ...................................................................................................................... 93
Parameters............................................................................................................ 93
14 3BSE079156-600
Table of Contents
Configuration .......................................................................................................96
Functionality ........................................................................................................97
Alarms and Errors ................................................................................................98
Recommended use .............................................................................................100
ComplementIn ...............................................................................................................101
Parameters ..........................................................................................................102
Configuration .....................................................................................................103
Functionality ......................................................................................................104
Alarms and Errors ..............................................................................................105
Recommended use .............................................................................................105
Section 5 - Create Safety Logic

Safety precautions .........................................................................................................107
Documentation of the Approved Application Version ..................................................109
Section 6 - Graphical User Interface

Overview........................................................................................................................113
Common functionality .......................................................................................113
Graphic Display .................................................................................................117
Faceplates ...........................................................................................................118
Display Elements ...............................................................................................121
Burner ............................................................................................................................121
Faceplate ...........................................................................................................121
Tightness Test ................................................................................................................134
Faceplate ...........................................................................................................134
Lambda ..........................................................................................................................141
Faceplate ...........................................................................................................141
RealIn2oo3 ....................................................................................................................148
Faceplate ...........................................................................................................148
3BSE079156-600 15
Table of Contents
ComplementIn............................................................................................................... 155
Faceplate .......................................................................................................... 155
Display Elements ............................................................................................... 158
Section 7 - Application Examples

Gas burner ..................................................................................................................... 160
Diagram .......................................................................................................... 161
Structured Text................................................................................................... 165
Oil Burner with Master and Slave................................................................................. 167
Pilot Valve Requires Fuel Feed from the Main Supply................................................. 170
TightnessTest with Three or More Fuel Valves in Series.............................................. 171
Section 8 - Debugging
Program step.................................................................................................................. 173
Alarms ........................................................................................................................... 174
Troubleshooting............................................................................................................. 174
Section 9 - Support
ABB Website................................................................................................................. 177
ABB SolutionsBank ...................................................................................................... 177
Control Systems Application and Knowledge Store..................................................... 177
Index
Revision History
Introduction ................................................................................................................... 181
Revision History............................................................................................................ 181
16 3BSE079156-600
About This User Manual General
About This User Manual
General
Any security measures described in this User Manual, for example, for user
access, password security, network security, firewalls, virus protection, etc.,
represent possible steps that a user of an 800xA System may want to consider
based on a risk assessment for a particular application and installation. This risk
assessment, as well as the proper implementation, configuration, installation,
operation, administration, and maintenance of all relevant security related
equipment, software, and procedures, are the responsibility of the user of the
800xA System.
This manual describes Burner Library and is valid for version 1.1 which can be used
as the basic building blocks for burner management systems. The description is
made from a user manual perspective and a safety perspective.
All warnings and cautions in AC 800M High Integrity Safety Manual
(3BNP004865*) are generally valid and shall be adhered to.
The End-User shall comply with all restrictions and conditions for the safety
system that is provided by the Safety Manuals or by other mandatory documents
referred to by the Safety Manual. This includes all aspects of installation,
configuration, operation and maintenance.
Before running SIL certified applications in a High Integrity controller, refer to

System 800xA Control AC 800M Getting Started (3BSE041880*) manual.
3BSE079156-600 17
User Manual Conventions About This User Manual
The user shall verify that installed versions of hardware, software modules and
documentation System 800xA Safety AC 800M High Integrity Manual
(3BNP004865*) and System 800xA Safety AC 800M High Integrity, Reliability
and Availability (3BSE034876*) are in compliance with the valid version of
System 800xA Safety AV84798C-A_A Annex A, DGC Annex (3BSE084011), TÜV
Certificate report, (3BSE074100) of the Report on the certificate Z10 13 07
29902 006. Annex A is also referred to from the Machine Safety certificate M6A
13 07 29902 008. These certificates are issued by TÜV Product Service GmbH
and they are available through ABB web services.
User Manual Conventions

Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.
Warning, Caution, Information, and Tip Icons

This User Manual includes Warning, Caution, and Information where appropriate to
point out safety related or other important information. It also includes Tip to point
out useful hints to the reader. The corresponding symbols should be interpreted as
follows:
Electrical warning icon indicates the presence of a hazard that could result in
electrical shock.
Warning icon indicates the presence of a hazard that could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard that could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
18 3BSE079156-600
About This User Manual Terminology
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.
Terminology
A complete and comprehensive list of terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms.
3BSE079156-600 19
Applicable Specifications About This User Manual
Applicable Specifications
This product meets the following standards.
General Safety Standards
Standard Description
IEC 61508:2010 Functional safety of electrical/electronic/programmable
electronic safety-related systems
IEC 61511:2003 Functional safety - Safety Instrumented Systems for the
process industry sector
IEC 62061:2005 Safety of machinery – Functional safety of safety-related
electrical, electronic and programmable electronic control
systems
ISO 13849-1:2006 Safety of machinery - Safety-related parts of control systems
Part 1: General principles for design
EN 50156-1:2004 Electrical equipment for furnaces
20 3BSE079156-600
About This User Manual Application Standards (to the extent applicable)
Application Standards (to the extent applicable)
Standard Description
EN 13611:2007+A2:2011 Safety and control devices for gas burners and gas burning
appliances – General requirements
EN 298:2012 Automatic burner control systems for burners and appliances
burning gaseous or liquid fuels
EN 267:2009+A1:2011 Automatic forced draught burners for liquid fuels
EN 676+A2:2008 Automatic forced draught burners for gaseous fuels
EN 1643:2000 Valve proving systems for automatic shut-off valves for gas
burners and gas appliances
EN 746-2:2010 Industrial thermoprocessing equipment - Part 2: Safety
requirements for combustion and fuel handling systems
EN 12952-8:2002 Water-tube boilers and auxiliary installations – Part 8:
Requirements for firing systems for liquid and gaseous fuels for
the boiler
EN 12952-9:2002 Water-tube boilers and auxiliary installations – Part 9:
Requirements for firing systems for pulverized solid fuels for
the boiler
EN 12953-7:2002 Shell boilers – Part 7: Requirements for firing systems for liquid
and gaseous fuels for the boiler
3BSE079156-600 21
Gas Appliance Directive (GAD) About This User Manual
Gas Appliance Directive (GAD)

The Function Blocks 'Burner', 'TightnessTest' and 'Lambda' (Air to Fuel Ratio) are
certified for EN 298, EN 1643, EN 13611 and EN 676 by Danish Gas Technology
Centre A/S (DGC), a Notified Body under GAD.
The certification is based on, and an addition to, the TÜV IEC 61508:2010
certificates.
Figure 1. AC 800M Burner Management Library DGC Certificate
22 3BSE079156-600
About This User Manual Related Documentation
Related Documentation
A complete list of all User Manuals and Release Notes applicable to System 800xA
is provided in System 800xA Released User Documents (3BUA000263*).
System 800xA Released User Documents (3BUA000263*) is updated each time a
document is updated or a new document is released. It is in pdf format and is
provided in the following ways:
• Included on the documentation media provided with the system and published
to ABB SolutionsBank when released as part of a major or minor release,
Service Pack, Feature Pack, or System Revision.
• Published to ABB SolutionsBank when a User Manual or Release Note is
updated in between any of the release cycles listed in the first bullet.
A product bulletin is published each time System 800xA Released User
Documents (3BUA000263*) is updated and published to ABB SolutionsBank.
The table below lists all product documents referenced in this instruction.
Table 1.
Category Title Description

System System 800xA Released User
Documents, 3BUA000263*
System 800xA System Guide Functional
Description, 3BSE038018*
System 800xA Operations,
3BSE036904*
3BSE079156-600 23
Related Documentation About This User Manual
Table 1.
Category Title Description

Safety AC 800M High Integrity, 3BNP004865* Safety Manual
System 800xA Safety AV84798C-
A_A Annex A
TÜV Certificate report, 3BSE074100 TÜV Certificate
DGC Annex, 3BSE084011 DGC Certificate
CBS Annex, 3BSE079245 CBS Certificate
Software System 800xA Control AC 800M, Getting Started

3BSE041880*
24 3BSE079156-600
Section 1 Burner Management Introduction Burner Management Systems Defined
Section 1 Burner Management Introduction
A Burner Management System (BMS) is designed to prevent boiler explosions, and

to improve plant operation by providing safe and reliable:
• Start-up (Continuous demand)
• Operation (Low demand)
• Process and emergency shutdowns
A BMS can be from a simple boiler to a complex, multi-burner process-fired heater
unit or power generation boiler. It can control different boiler and fuel types.
Burner Management Systems Defined

Burner Management Systems (BMS) are a subset of industrial automation and
control systems that are employed in the process industries to provide interlocks and
permissives to prevent misoperation of equipment and to safely handle faults caused
by equipment failure. These events potentially result in uncontrolled fires,
explosions, or implosions and in the unintended release of the materials being
heated.
Fired equipment is found throughout the process industries in many applications,
including various types of heaters and boilers, the hazards associated with burner
operation are managed by an instrumented system commonly referred to as the
Burner Management System (BMS).
A Burner Management System is defined as the field devices, logic system, and
final control elements dedicated to combustion safety and operator assistance in the
starting and stopping of fuel preparation and burning equipment and for preventing
misoperation of and damage to fuel preparation and burning equipment.
BMS applications are found in different industries including Power Generation,
Thermal Power Plants, District Heating, Pulp and Paper, Chemical and
Petrochemical, Refining and Upstream Oil & Gas production.
3BSE079156-600 25
Functionality Section 1 Burner Management Introduction
Functionality
Typical functionality of a BMS application include:
• Purge Commence Confirmation - Requirements
– Drum Level Ok, All Burner Valves Ok, Control Energies Ok, Fuel
Systems Healthy, Oxygen Analyzer Healthy, All Igniter Systems Off, No
Flame Detected
• Monitor Start-Up Sequence
– Purge Completed ? Leak Check of Fuel System? Start Igniter / Burner
• Preventing Unburned Fuel Entering Furnace
– Monitoring of Valve Positions
– Flame Monitoring (On-line)
– Oxygen Analyzer Monitoring (On-line)
• Emergency Shutdowns / Trips
– Activate inerting System
– De-energize all ignition sources and valves
– Manage fans (depending on cause of trip)
• Monitor Shut-Down Sequence (Reverse of Start-Up)
26 3BSE079156-600
Section 1 Burner Management Introduction Trip Causes
Trip Causes
Common trip causes are:
• Master Fuel Trip (MFT)
– Fuel System Problem
– Combustion Air Flow Low
– Loss of fans
– Excessive furnace pressure
– All fuel inputs zero
– Loss of flame
– Manual trip switch activated
• Igniter Trip
– Loss of igniter flame
– Igniter fuel pressure unstable
• Burner Trip
– Loss of burner flame
– Burner valves out of position
3BSE079156-600 27
Using AC 800M High Integrity as a BMS Section 1 Burner Management Introduction
Using AC 800M High Integrity as a BMS

Burner Management Systems have historical been implemented by using traditional
fuel dispensers. The fuel dispenser is in charge of the firing process, but is a “black
box” and as an operator you have no control over the process.
The AC 800M High Integrity BMS safety system is, on the other hand, fully
integrated with a System 800xA process control system. This enables common,
plant-wide operations, engineering and information environments across both the
Basic Process Control System (BPCS) and the Safety Instrumented System (SIS).
AC800M HI AC800M
BMS DCS
Controller Controller
Figure 2. AC 800M High Integrity Burner Management System
The AC 800M High Integrity and the AC 800M process controller utilize common
engineering tools as well as operator interface, historian, audit trail, asset and device
management applications and instruments.
28 3BSE079156-600
Section 1 Burner Management Introduction Burner Management Library
Burner Management Library

The AC 800M High Integrity Burner Management Library is a fully integrated
application in System 800xA.
It provides the complete control over the startup and operation.
• Monitoring of the ignition sequence
• Leak testing of valves
• Control of the air/fuel mixture and the fuel supply
By using the library, there is no longer the need for a separate Burner-system.
Integrated Operation and Alarm Handling

The Library has built in Alarm Handling, and ready-made 800xA Faceplates and
Display Elements. It fulfills all relevant standards, while making it possible to
visualize what happens during the process.
The “black box” is gone and regardless of why the machine stops, there is a clear
message that show what is wrong and the operator can go directly to the error.
3BSE079156-600 29
Combined Safety and Control Section 1 Burner Management Introduction
Combined Safety and Control

The AC 800M High Integrity design offers the added flexibility of hosting both
safety and process control applications in a combined controller.
Figure 3. Certified firewalls isolate SIL and non-SIL applications
Consequently, the complete boiler process control as well as the BMS can quite
often be hosted within one single AC 800M High Integrity controller.
High Integrity Instrumentation

ABB can provide a wide range of safety-certified sensors and positioners. Various
solutions are available ranging from full-redundancy, high-integrity transmitters
designed and certified by TÜV against IEC 61508 requirements to standard
transmitters with enhanced internal diagnostics to minimize the Probability of
Failure on Demand.
30 3BSE079156-600
Section 2 System and Software Requirements Processes
Section 2 System and Software Requirements
This section presents general system requirements.
A license is required for the use of the library.
Processes
The development process for the Burner application/management application

shall comply with the requirements of the related standards and regulations, e.g.
with IEC 61508 2nd edition SIL3. The correct implementation shall be subject of
a functional validation.
Personnel
All persons involved in the use of the Burner Library shall have sufficient
competence in their associated activity and shall have enough safety knowledge
about the AC 800M HI safety system.
Risk Mitigation and Impact Assessments
It is assumed that the application software is subject to safety analysis to

determine the level of reliance of the Burner Lib Function Blocks. Safety
measures might be required to ensure the safety integrity of the application
software. For security reasons an additional thread analysis might be required.
3BSE079156-600 31
Software and Hardware Section 2 System and Software Requirements
Software and Hardware
Never use AC 800M High Integrity software- or hardware components, that are
not covered by the TÜV SÜD certificate/TÜV SÜD letter of conformance or the
DGC certificate covering the Burner related safety standards, within the safety
system used in Burner applications.
The construction of any additional functions included in the system,
programming unit or flame detector device for which no provisions exist, shall be
such that they do not degrade the safe and correct operation of the system,
programming unit or flame detector device.
The hints and warnings for recommended use of the Safety and User Manual
shall be considered for parametrization and for integration of the function blocks
into the user program, as well as for installation, commissioning, operation and
validation.
SIL Restrictions with Burner Library
The Burner Library is capable for the use in SIL3 (or lower) applications. The
Burner Library makes use of "SIL restricted" functionality for the alarm and
event functionalities, which may not be used to be part of any safety related
control loop.
32 3BSE079156-600
Section 3 Library Overview Introduction to Burner Library
Section 3 Library Overview
This section presents an overview of the Burner Library.
Introduction to Burner Library

The 'BurnerLib' library contains SIL3 classified function block types that are used to
define control logic for burner control in the Program Organization Units (POU’s) in
Control Builder M Professional.
The objects in the Burner library are used to define control logic for safety
requirements like:
• Close down due to violation of safety times
• Close down due to violation of different conditions
• Burner does not start up without operator interaction when it is in safe state
• Lambda calculation to calculate air-to-fuel ratio and generating alarms/errors
• Start up burners with/without pilot burners
• Carry out a tightness test of the fuel/safety valves
3BSE079156-600 33
Introduction to Burner Library Section 3 Library Overview
Table 2 presents the function blocks available in the 'BurnerLib' library.
Table 2. Function blocks in 'BurnerLib'
Name Type Description

Burner SIL3 Start-up sequence and supervision/monitoring of a Burner
TightnessTest SIL3 Tightness test for gas supply valves
Lambda SIL3 Calculation of air-to-fuel ratio
RealIn2oo3 SIL3 2 out of 3 voting function for real inputs
ComplementIn SIL3 Handling of two complementary Boolean inputs
The function blocks, connected libraries and data types in BurnerLib are shown in
Figure 4.
Figure 4. BurnerLib as shown in Control Builder M Professional
34 3BSE079156-600
Section 3 Library Overview Dependencies to other Objects and Libraries
Figure 5 shows the setup of a pilot ignited burner with a cleaning valve. The power
of the burner utilizes the fuel flow and airflow. Application code outside the burner
function block controls the fuel/air flow.
Pressurized air
AtomizingValve
Cleaning media
Main flame
guard
CleaningValve
Main fuel
FuelValve1 FuelValve2
Air supply
AirValve
Pilot flame guard
Oxygen supply
OxygenValve Igniter
Pilot fuel
Pilot fuel valve
Figure 5. Pilot ignited burner with cleaning function
Dependencies to other Objects and Libraries

The objects in 'BurnerLib' use different SIL3 restricted objects from
AlarmEventLib.
3BSE079156-600 35
Field Connection Section 3 Library Overview
Field Connection
The objects 'TightnessTest', 'Lambda' and 'Burner' in 'BurnerLib' are designed to
handle simple data types such as bool and real. This means that these data types
need to be converted before being connected to the field. Examples of field
connections are presented in Section 7, Application Examples.
The mentioned recommended objects for field connection is a suggestion of what

to use.
Feedback Objects
It is recommended to use the SDValve object from SupervisionBasicLib library to
connect the outputs from the 'BurnerLib' library objects. The outputs can be
commands to valves and igniter.
Single Analog Input

It is recommended to use the SignalBasicInReal object from SignalBasicLib to
connect single analog input to the objects in 'BurnerLib'.
2oo3 Analog Inputs

Use the 'RealIn2oo3' object to achieve a single signal based on three analog inputs.
Single Boolean Input

It is recommended to use the SignalBasicInBool object from SignalBasicLib to
connect single boolean input to the objects in 'BurnerLib'.
Complementary Boolean Inputs

Use the 'ComplementIn' object in 'BurnerLib' for complementary boolean inputs.
Memory Usage and Execution Times

Memory is reserved for each function block type defined. When another instance is
created, the amount of memory reserved for the instance is very small in relation to
36 3BSE079156-600
Section 3 Library Overview Memory Usage and Execution Times
the type. This means that the memory consumed by the type itself is of great
importance.
The following tables show memory usage and execution time for AC 800M High
Integrity controller, for a number of common function blocks and control modules
in Burner Library.
In the Table 3 the 1st instance column shows the required memory for the object
type and one function block or control module, 2nd instance and 6th instance
columns shows the required memory for every further function block or control
module.
Table 4 contains execution times for function blocks in a PM865 High Integrity. The
column show the average execution time in μs.
Table 3. AC 800M Memory usage for Burner Library
Memory Usage kbytes

Library Object
1st instance 2nd instance 6th instance
BurnerLib Burner 78.0 17.2 17.6

BurnerLib TightnessTest 36.7 3.2 4.3
BurnerLib Lambda 33.0 7.9 4.8
BurnerLib RealIn2oo3 31.8 3.2 4.9
BurnerLib ComplementIn 29.1 2.6 4.2
Table 4. AC 800M Execution time for Burner Library in PM865 SIL3 controller
Average
Library Object execution time
(PM865 SIL3) μs
BurnerLib Burner 384
BurnerLib TightnessTest 164
BurnerLib Lambda 174
3BSE079156-600 37
Memory Usage and Execution Times Section 3 Library Overview
Table 4. AC 800M Execution time for Burner Library in PM865 SIL3 controller
Average
Library Object execution time
(PM865 SIL3) μs
BurnerLib RealIn2oo3 138
BurnerLib ComplementIn 92
38 3BSE079156-600
Section 4 Function Block Types Burner
Section 4 Function Block Types
This section describes the function block types available in the 'BurnerLib'
Library.All function blocks in the 'BurnerLib' library are SIL3 classified and can be
used in both SIL1, SIL2 and SIL3 applications. They can also be used in non-SIL
applications.
All function block types are programmed using ST language.
Burner
The 'Burner' function block includes the following functionality:
• Burner start-up and supervision/monitoring
• Automatic re-ignition during start, running and intermittent mode
• Cleaning of the oil lance and fuel pipes
• Test of pilot burner for manually testing/setting/trimming of the flame guard
• Ignition types:
– Intermittent
– Interrupted
– Direct
The 'Burner' function block is intended to be used for starting up and monitoring of
one or multiple gas burners, liquid fueled burners or solid fueled burners or a
combination of the aforementioned. The function block can start and stop a burner
in a safe manner. The 'Burner' function block will handle step 5 to 9 from the start-
up sequence shown in Figure 6. After the start-up sequence, the burner management
3BSE079156-600 39
Burner Section 4 Function Block Types
system will continue to monitor process variables, such as temperature and flame
guards.
Damper position
2 3 4
0 1 5 6 7 8 9
Time
Figure 6. Start-up sequence
0. Safety interlock OK
1. Check air pressure switch (in idle), set damper to purging position
2. Check damper in purging position
3. Air pressure switch active
4. Set damper to start position, end of purging
5. Damper in starting position
6. Activate spark igniter
7. Activate pilot flame
8. Activate main burner
9. Release for modulation and monitoring of process variables
The function block can be instantiated in Function block diagram, Structured text or
Diagram. It is recommended to use Diagram.
Simple data types are used on the inputs and outputs, which allows for easy
development of logic outside the burner. The 'Burner' object can be operated from a
faceplate or from application logic. Control from application logic is highly
recommended in systems where two or more burners need to be started
simultaneously; the burners can then be started in the correct order from a sequence
40 3BSE079156-600
Section 4 Function Block Types Burner
in the application. The correct order can be in series or parallell at the same time.
This is depending on the actual plant where the BurnerLib is used.
All configurations are made in the Config parameter, these parameters can only be
changed off-line and require a new download (cold or warm) if changed.
The operator is given full overview of the process and information if there is a fault.
This function block type can be used in time-critical tasks. However, time-critical
tasks are not allowed in a high integrity controller.
3BSE079156-600 41
Parameters Section 4 Function Block Types
Parameters
This section describes the input- and output parameters of the 'Burner' function
block.
Input
Table 5 on page 42 describes the input parameters for the 'Burner' function block.
Table 5. Input parameters for the 'Burner' function block
Name Data Type Description

Name* string[30] EDIT Name of the object. Edit for alarm.
Description string[40] Object Description.
SafeTempReached* bool Safe temperature reached, flame guards ignored
if set
FlameGuardMain* bool Flame guard
FlameGuardPilot* bool Pilot flame guard
IgniterInOperation* bool Running feedback from the electrical igniter
PilotValveClosed bool Closed, feedback from Pilot valve
FuelValve1Closed bool Closed, feedback from Fuel valve 1
FuelValve2Closed bool Closed, feedback from Fuel valve 2
StartCond* bool Start condition, must be TRUE to start object
PriorityCmdStop* bool Forcing object to a stop when TRUE
AutoStart* bool Start command
AutoStop* bool Stop command
AutoStartMainBurner bool Start command to main burner in intermittent
mode
*Functional Diagram (FD) Port visible by default
**In/Out
42 3BSE079156-600
Section 4 Function Block Types Parameters

AutoStopMainBurner bool Stop command to main burner in intermittent
mode
AutoStartCleaning bool Start cleaning command
SetAuto bool Set automatic mode
SetOutOfService bool Set Object to Out of Service mode
Reset bool Acknowledge object error and priority stop
AEConfigMainBurnerError dint Config error handling (1=Alarm, 2=Event,
3=Event1, 4=Level, else Alarm + ParError)
AESevMainBurnerError dint Severity for error. Range 1 - 1000 else ParError +
(Alarms: Prev valid value used else no alarm
created; Events: No event generated).
EnableMainBurnerError bool Enable error handling alarm/event
AEConfigPilotBurnerError dint Config error handling (1=Alarm, 2=Event,
AESevPilotBurnerError dint Severity for error. Range 1 - 1000 else ParError +
EnablePilotBurnerError bool Enable error handling alarm/event
AEConfigIgniterError dint Config error handling (1=Alarm, 2=Event,
AESevIgniterError dint Severity for error. Range 1 - 1000 else ParError +
EnableIgniterError bool Enable error handling alarm/event
AEConfigValvePositionError dint Config error handling (1=Alarm, 2=Event,
**In/Out
3BSE079156-600 43

AESevValvePositionError dint Severity for error. Range 1 - 1000 else ParError +
EnableValvePositionError bool Enable error handling alarm/event
AEConfigReignitionError dint Config error handling (1=Alarm, 2=Event,
AESevReignitionError dint Severity for error. Range 1 - 1000 else ParError +
EnableReignitionError bool Enable error handling alarm/event
AEConfigFlameError dint Config error handling (1=Alarm, 2=Event,
AESevFlameError dint Severity for error. Range 1 - 1000 else ParError +
EnableFlameError bool Enable error handling alarm/event
AEClass dint Class alarms/events. Range 1 - 9999 else
ParError + (Alarms: Prev valid value used else no
alarm created; Events: No event generated).
AEAckAll bool Acknowledge alarm condition on positive edge
Config* BurnerConfig EDIT Configuration data
InteractionPar** BurnerPar Interaction parameter
**In/Out
44 3BSE079156-600
Output
Table 6 on page 45 describes the output parameters for the 'Burner' function block.
Table 6. Output parameters for the 'Burner' function block
Name Data Type Description SIL

AtomizingValve* bool Order open to the atomizing valve 3
CleaningValve* bool Order open to the cleaning valve 3
AirValve* bool Order open to the air valve 3
OxygenValve* bool Order open to the oxygen valve 3
Igniter* bool Order start to the electrical igniter 3
PilotValve* bool Order open to the Pilot valve 3
FuelValve1* bool Order open to the Fuel valve 1 3
FuelValve2* bool Order open to the Fuel valve 2 3
Starting bool Indicate that the burner is starting up 3
Running* bool Indicate if burner is running 3
Cleaning bool Indicate that cleaning is running 3
CleaningDone bool Indicate that cleaning has been completed 3
AutoMode bool Automatic mode indicator 3
OutOfServiceMode bool Out of service mode indicator 3
Error* bool Indicates summary error 3
MainBurnerErrorEnabled bool Error handling alarm/event enabled 3
AlStateMainBurnerError dint NONSIL CondState from Error AlarmCond (0-6) Non
PilotBurnerErrorEnabled bool Error handling alarm/event enabled 3
AlStatePilotBurnerError dint NONSIL CondState from Error AlarmCond (0-6) Non
IgniterErrorEnabled bool Error handling alarm/event enabled 3
3BSE079156-600 45
Table 6. Output parameters for the 'Burner' function block
Name Data Type Description SIL

AlStateIgniterError dint NONSIL CondState from Error AlarmCond (0-6) Non
ValvePositionErrorEnabled bool Error handling alarm/event enabled 3
AlStateValvePositionError dint NONSIL CondState from Error AlarmCond (0-6) Non
ReignitionErrorEnabled bool Error handling alarm/event enabled 3
AlStateReignitionError dint NONSIL CondState from Error AlarmCond (0-6) Non
FlameErrorEnabled bool Error handling alarm/event enabled 3
AlStateFlameError dint NONSIL CondState from Error AlarmCond (0-6) Non
AEError bool NONSIL Used to signal alarm/event error Non
ParError* bool Indicates parameter range error. 3
46 3BSE079156-600
Section 4 Function Block Types Configuration
Configuration
The Config parameter is a structured data type (BurnerConfig) containing
components for all configuration data for the function block. The parametrized
configuration data must comply with corresponding safety standards. Any changes
to the data will be activated only after a download of the changes. Table 7 on page
47 describes the configuration parameters for the 'Burner' function block.
Table 7. Configuration parameters for the 'Burner' function block

IgnitionType dint • 1=Direct - Main fuel is ignited by an electrical
igniter
• 2=Intermittent - Main fuel is ignited by an
intermittent pilot burner. The pilot burner is
ignited by an electrical igniter, which in turn
ignites the main fuel. The pilot burner
remains on until the burner is stopped. This
mode is useful for pulsed burners that can
quickly be started and stopped.
• 3=Interrupted - Main fuel is ignited by an
interrupted pilot burner. The pilot burner is
ignited by an electrical igniter, which in turn
ignites the main fuel. The pilot burner will be
extinguished once the main fuel is ignited
and after the second safety time.
Range 1-3 else last good value + ParError
FirstSafetyTime time First safety time. Range 2-10s else last good
value + ParError
SecondSafetyTime time Second safety time. Range 2-10s else last good
value + ParError
FillingTime time Time to fill empty pipes with fuel. Range 0-120s
else last good value + ParError
ReactionTime time Reaction time on flame guard (pilot flame and
main flame). Range: 0-2s else last good value +
ParError
3BSE079156-600 47
Configuration Section 4 Function Block Types
Table 7. Configuration parameters for the 'Burner' function block

PreIgnitionTime time Time between electrical igniter and activation of
fuel valve. Range 0-10s else last good value +
ParError
CleaningTime time Open time for the cleaning valve. Range 5-30s
PilotFlameProvingTime time Time for proving of pilot flame. Range 0 -10s else
last good value + ParError
MainFlameProvingTime time Time for proving of main flame. Range 0 -10s else
DepressurizeTime time Time between closing the cleaning valve and fuel
valve 2. Range 1-5s else last good value +
ParError
EnableCleaning bool Cleaning will run during a normal stop (not during
PriorityCmdStop)
CheckFlameGuardsBeforeStart bool The flame guards are ckecked to be false before
opening fuel valve 1 and fuel valve 2
BetweenReignitionTime time Time between ignition attempts. Range 1-10s else
MaxIgnitionAttemptsStart dint Max number of ignition attempts during start.
MaxIgnitionAttemptsRunning dint Max number of reignition attempts during running.
MaxIgnitionAttemptsInterm dint Max number of reignition attempts of pilot flame in
intermittent mode. Range 0-3 else last good value
+ ParError
48 3BSE079156-600
Section 4 Function Block Types Functionality
Functionality
The 'Burner' function block has extra functions that can be enabled by parameters in
the configuration data:
• Automatic reignition during start, running and intermittent pilot mode
(Config.MaxIgnitionAttemptsStart, Config.MaxIgnitionAttemptsRunning and
Config.MaxIgnitionAttemptsInterm)
• Cleaning of the oil lance and fuel pipes (Config.EnableCleaning)
• Test of pilot burner (Config.IgnitionType = 2 or 3)
• Intermittent pilot mode (Config.IgnitionType = 2)
Operating Modes
The 'Burner' function block has two operating modes, automatic and manual. The
burner can be started in manual mode from the faceplate or in automatic mode from
the code. The parameters AutoStart and AutoStop are used to start and stop the
burner in automatic mode.
The priority stop command PriorityCmdStop will stop the burner independent of
mode.
The module has one non-operational mode, which can be set if maintenance is being
carried out on the burner, the mode is called OutOfServiceMode. No output orders
are activated when the burner is in OutOfServiceMode.
Set the burner into manual mode to return from OutOfServiceMode.
The modes can be changed from the faceplate by the corresponding button.
Changing mode to auto can also be done from code, but not when the burner is in
OutOfServiceMode.
3BSE079156-600 49
Functionality Section 4 Function Block Types
Initial condition
The StartCond parameter must be true during start and should be a summarized
signal of all prerequisites to start the burner. The prerequisites to start a burner are
dependent on the selected burner solution and must be handled outside the 'Burner'
function block. The StartCond parameter is checked only when start or re-ignition is
initiated from the faceplate or when the AutoStart parameter is set. The transitions
that are not allowed if StartCond is false are from state 100: Idle  state 200:
Starting, state 100: Idle  state 400: Cleaning and from state 100: Idle  state 700:
PilotTest.
The parameter PriorityCmdStop shall be false to enable the transition from state
100: Idle to any other state. If this parameter is true when trying to start, the function
block will remain in state 100: Idle.
States
A state machine of burner operation is described in Figure 7 followed by Table 8 on
page 52 which describes each transition. State 900: Fault can be reached from any of
the other states depending on if there is a fault. The following states contain sub-
steps:
• State 200: Starting, see Table 10 on page 56 and Table 11 on page 58
• State 400: Cleaning, see Table 13 on page 61
• State 700: Pilot test see, Table 17 on page 65.
Output orders, that are not included in the sequence diagrams in this section, are
inactive if nothing else is stated.
The 'Burner' object will always be in state 100: Idle after controller power-up.
50 3BSE079156-600
100 Idle Reset 900 Fault
StartPilotTest StartCleaning
Start
Stop & Cleaning

700 Pilot test 200 Starting 400 Cleaning
Automatic Stop & Cleaning
300 Running Stop & Cleaning

StopPilotTest
ManStopMainBurner
Stop ManStartMainBurner
600 Intermittent Automatic

Automatic mode
Stop
Stop
500 Normal stop
Figure 7. State machine of the 'Burner' function block
3BSE079156-600 51
Table 8. Transitions of the 'Burner' function object State machine
Transition Description
Start Start of the cleaning sequence is initiated from the operator interface or with
the parameter AutoStart
Stop Stop is initiated from the operator interface or with the parameter AutoStop.
The configuration parameter Config.EnableCleaning is not set. Stop has a
higher priority than Start.
StartCleaning Start is initiated from the operator interface or with the parameter
AutoStartCleaning
Stop & Cleaning Stop is initiated from the operator interface or with the parameter AutoStop.
The configuration parameter Config.EnableCleaning shall be set to enable
this transition.
Reset Acknowledge of object error and priority stop. A reset is required before the
burner can be restarted. Reset is initiated from the operator interface or with
the parameter Reset.
StartPilotTest Start of the pilot test is initiated from the operator interface
StopPilotTest Stop of the pilot test is initiated from the operator interface
Automatic This transition occurs without operator interaction when the step is
successfully completed
ManStartMainBurner Manual start of main burner in intermittent mode
ManStopMainBurner Manual stop of main burner in intermittent mode
52 3BSE079156-600
State 100: Idle - The burner is waiting for a start command. All orders are reset.
Table 9. State 100: Idle
Output Order
AtomizingValve Inactive
CleaningValve Inactive
AirValve Inactive
OxygenValve Inactive
Igniter Inactive
PilotValve Inactive
FuelValve1 Inactive
FuelValve2 Inactive
State 200: Starting - The start sequence will be initiated when a positive edge is
detected on the AutoStart parameter or when start is activated from the faceplate.
The precondition StartCond must be true to start the burner.
Depending on the configuration parameter Config.IgnitionType, the burner will start
either with an electrical igniter or with a pilot burner as ignition source for the main
fuel (See Figure 8 and Figure 9 for a graphical representation of the start sequence,
see Table 10 on page 56 and Table 11 on page 58 for detailed Step descriptions).
There are two types of ignition with a pilot burner, they are called intermittent mode
and interrupted mode. In intermittent mode, the pilot burner remains on until the
burner is stopped while in interrupted mode the pilot burner is deactivated once the
main burner is running and after the second safety time has expired.
If an ignition attempt fails during the start, the burner will make a new attempt to
restart (as long as the StartCond is true). The maximum number of ignition attempts
is configurable by the parameter Config.MaxIgnitionAttemptsStart. All re-ignition
attempts start by setting all valve and igniter orders to false; the sequence will then
begin from step 215 (see Table 10 on page 56) in the starting sequence. A re-
ignition can be triggered by the absence of a signal on the FlameGuardPilot or the
FlameGuardMain parameters.
3BSE079156-600 53
If the burner is unable to detect a flame after the last attempt the burner will jump to
state 900: Fault and set the alarm ReignitionFault.
The number of executed ignition attempts will be reset once the main flame has
been reestablished and stable during the main flame-proving period.
Flame guards are used to monitor the startup and operation of the pilot flame and the
main flame. The signal SafeTempReached is used to indicate to the burner that the
temperature inside the boiler is high enough for the fuel to self-ignite.
SafeTempReached has a higher priority than flame guards. If SafeTempReached is
reached the loss of flame guards will be ignored. The SafeTempReached is a digital
signal and should be generated outside the 'Burner' function block. The burner
management system controls this parameter.
Some burners require a check for no flame prior to start. This is done in all steps
before the fuel valves are opened. The functionality can be disabled and enabled by
the Config.CheckFlameGuardsBeforeStart. An alarm will be generated and the
burner will go to safe state if there is a signal on any flame guard when starting.
54 3BSE079156-600
Figure 8 shows the start sequence of a burner with an electrical igniter as ignition
source for the main fuel.
FuelValve1
FuelValve2
CleaningValve
AirValve
OxygenValve
AtomizingValve
Igniter
PilotValve
PreIgnitionTime
FuelFillingTime
FirstSafetyTime
MainFlameProvingTime
Step Number 200 215 270 275 285 300

Figure 8. Example of a start sequence with an electrical igniter as ignition source
for the main fuel
3BSE079156-600 55
Table 10. Step description of start sequence with an electrical igniter as ignition source for the main
fuel
Step Number Description

215 Start Igniter and wait Config.PreIgnitionTime. Supervise IgniterInOperation
when exiting the step.
270 Open FuelValve1, FuelValve2, AtomizingValve, AirValve, OxygenValve and wait
FuelFillingTime.
275 Wait Config.FirstSafetyTime. Supervise FlameGuardMain and SafeTemp.
285 Stop Igniter and wait Config.MainFlameProvingTime. Supervise
FlameGuardMain and SafeTemp.
56 3BSE079156-600
Figure 9 shows the start sequence of a burner with a pilot burner as ignition source
for the main fuel
FuelValve1
FuelValve2
CleaningValve
AirValve
OxygenValve
AtomizingValve
Igniter
PilotValve
PreIgnitionTime
FirstSafetyTime
PilotFlameProvingTime
FuelFillingTime
SecondSafetyTime
MainFlameProvingTime
Step Number 200 215 225 235 245 250 285 300
Figure 9. Example of a start sequence with a pilot burner as ignition source for the
main fuel
3BSE079156-600 57
Table 11. Step description of start sequence with a pilot burner as ignition source for the main fuel
Step Description
215 Start Igniter and wait Config.PreIgnitionTime
225 Open PilotValve and wait Config.FirstSafetyTime. Supervise FlameGuardPilot and
SafeTemp.
235 Stop Igniter and wait Config.PilotFlameProvingTime. Supervise FlameGuardPilot and
SafeTemp.
245 Open FuelValve1, FuelValve2, AtomizingValve, AirValve, OxygenValve and wait
FuelFillingTime
250 Wait Config.SecondSafetyTime. Supervise FlameGuardMain and SafeTemp.
285 Close PilotValve and wait Config.MainFlameProvingTime
State 300: Running - Once the start-up sequence is finalized, the 'Burner' function
block will change state from state 200: Starting to state 300: Running (State 300
corresponds to step 9 in Figure 6).
During state 300: Running the function block monitors several process values and
can set alarms to alert the operator, the burner can perform a re-ignition if the flame
is lost as well as cleaning of the oil lance and fuel pipes.
Depending on the setting on the configuration parameter
Config.MaxIgnitionAttemptsRunning (if set to 0 no reigintion when up and running
is allowed) there is a possibility for reignition. Reignition is done when there is no
signal detected on the FlameGuardMain parameter when in state 300: Running.
This condition will force the burner to jump to state 200: Starting. All valve and
igniter orders will be set to false during a delay time Config.BetweenReignitionTime
before a new ignition attempt is performed. The maximum number of re-ignition
attempts during state 300: Running is configurable by the parameter
Config.MaxIgnitionAttemptsRunning.
Supervision of the pilot burner is done for burners with an intermittent pilot burner.
An alarm is set if the FlameGuardPilot is lost during state 300: Running and the
number of re-ignition attempts is equal to Config.MaxIgnitionAttemptsRunning.
58 3BSE079156-600
Note however that the flame is not supervised when the SafeTempReached
parameter is true.
Table 12. State 300: Running
Output Order
AtomizingValve Active
AirValve Active
OxygenValve Active
Igniter Inactive
PilotValve Active (Config.IgnitionType = 2, Intermittent)
Inactive (Config.IgnitionType = 1 or 3, Direct or Interrupted)
FuelValve1 Active
FuelValve2 Active
State 400: Cleaning - The cleaning sequence is used to prevent fuel, such as heavy
oil from clogging the pipes and the lance. The sequence is launched when a stop
command is given to the burner during Running. Once the cleaning is done, the
burner will deactivate all outputs. The faceplate enables the operator to start the
cleaning manually, the cleaning sequence can also be started from logic. This is
possible only when the burner is in state 100: Idle and when the start condition
StartCond is set.
The cleaning will not run if the burner was stopped by the PriorityCmdStop
parameter. The parameter CleaningDone indicates if the cleaning has been
performed, the status of CleaningDone is presented on the faceplate. The parameter
CleaningDone is reset once the fuel valves have been opened. The configuration
parameter Config.EnableCleaning enables or disables the possibility (both by
operator interaction and automatically) to run the cleaning sequence.
3BSE079156-600 59
The cleaning sequence for a burner configured as Pilot Intermittent/Pilot Interrupted

is presented in Figure 10..
FuelValve1
FuelValve2
CleaningValve
AirValve
OxygenValve
AtomizingValve
Igniter
PilotValve
PreIgnitionTime
FirstSafetyTime
CleaningTime
DepressurizeTime
Step Number 400 415 425 435 445 500

Figure 10. Cleaning of a burner when coming from state 300: Running and
configured as Pilot Intermittent/Pilot Interrupted
60 3BSE079156-600
Table 13. Step description for state 400: Cleaning of a burner configured as Pilot Intermittent/Pilot
Interrupted
Step Description
415 Send close order to FuelValve1, Start the Igniter and wait Config.PreIgnitionTime
425 Send open order to PilotValve and wait Config.FirstSafetyTime. Supervise
FlameGuardPilot.
435 Send open order to CleaningValve and FuelValve2 and wait Config.CleaningTime.
Supervise FlameGuardPilot.
445 Send close order to CleaningValve and wait Config.DepressurizeTime
500 Send close order to AtomizingValve, CleaningValve, AirValve, OxygenValve,
PilotValve, FuelValve1 and FuelValve2. Stop the Igniter. CleaningDone is set.
3BSE079156-600 61
The cleaning sequence for a burner configured as direct ignition is presented in

Figure 11.
FuelValve1
FuelValve2
CleaningValve
AirValve
OxygenValve
AtomizingValve
Igniter
PreIgnitionTime
CleaningTime
DepressurizeTime
Step Number 400 415 435 445 500

Figure 11. Cleaning of a burner when coming from the state 300: Running and
configured as direct ignition
Table 14. Step description for state 400: Cleaning of a burner configured as direct ignition
Step Description
415 Send close order to FuelValve1 and start the Igniter and wait Config.PreIgnitionTime
435 Send open order to CleaningValve and FuelValve2 and wait Config.CleaningTime
445 Send close order to CleaningValve and wait Config.DepressurizeTime
500 Send close order to AtomizingValve, CleaningValve, AirValve, OxygenValve,
PilotValve, FuelValve1 and FuelValve2. Stop the Igniter. CleaningDone is set.
62 3BSE079156-600
State 500: Stop - A controlled stop is performed. All orders are reset.
Table 15. State 500: Stop
Output Order
AirValve Inactive
Igniter Inactive
PilotValve Inactive
FuelValve1 Inactive
FuelValve2 Inactive
3BSE079156-600 63
State 600: Intermittent mode - This state is only available if the configuration
parameter Config.IgnitionType is set to 2.
If the burner is in state 300: Running it is possible to de-energize FuelValve1 and
FuelValve2 while the pilot valve remains energized. This is done by setting the
AutoStopMainBurner parameter or by pressing the “Stop main burner in intermittent
mode” on the faceplate.
When AutoStopMainBurner is reset and AutoStartMainBurner is set or if the “Start
main burner in intermittent mode” button on the faceplate is pressed, the burner will
change back to state 300: Running and the fuel valves will be energized.
The atomizing valve, air valve and oxygen valve will follow the fuel valves.
Table 16. State 600: Intermittent mode
Output Order
AirValve Inactive
Igniter Inactive
PilotValve Active
FuelValve1 Inactive
FuelValve2 Inactive
If the pilot flame FlameGuardPilot is extinguished after the Config.ReactionTime,

the electrical igniter will energize (Step 610 is active when the igniter is energized
but not active during the Config.FirstSafetyTime) during a Config.FirstSafetyTime
(Step 620 is active during this time) and try to reestablish the pilot flame. After the
Config.FirstSafetyTime, a check of the pilot flame is performed and if it is not
present the PilotBurnerError alarm will be set.
64 3BSE079156-600
The maximum number of attempts to reignite the pilot flame is set by the
configuration parameter Config.MaxIgnitionAttemptsInterm. The counter that keeps
track of the number of ignition attempts will be reset when the burner changes state.
State 700: Pilot test - This state is initiated when StartPilotTest is pressed on the
faceplate. It is stopped when StopPilotTest is pressed. It is only possible to use this
functionality if the burner is configured as a burner with pilot burner
(Config.IgnitionType is 2 or 3).
The Pilot Test sequence for a burner is presented in Figure 12.
Igniter
PilotValve
PreIgnitionTime
FirstSafetyTime
Step Number 700 710 720 725

Figure 12. Pilot test sequence of a burner
Table 17. Step description for state 700: Pilot test
Step Description
710 Activate Igniter and wait Config.PreIgnitionTime. Supervise IgniterInOperation.
720 Activate the PilotValve and wait Config.FirstSafetyTime. Supervise FlameGuardPilot.
725 Deactivate Igniter and wait for stop command. Supervise FlameGuardPilot.
3BSE079156-600 65
State 900: Fault - Any alarm or error as described in Alarms and Errors on page 67,
or a PriorityCmdStop generates a transition to state 900: Fault. In case of a
PriorityCmdStop the parameter Error is not set. All orders are inactive. A Reset is
required to go from state 900: Fault to state 100: Idle.
Table 18. State 900: Fault
Output Order
AirValve Inactive
Igniter Inactive
PilotValve Inactive
FuelValve1 Inactive
FuelValve2 Inactive
66 3BSE079156-600
Section 4 Function Block Types Alarms and Errors
Alarms and Errors

Common for all error cases and ParError is that the object will set the parameter
Error, set all output orders to false and go to state 900: Fault, except for state 100:
Idle where the object will stay in this state. The operator is then required to
acknowledge all alarms on the faceplate and to press the reset button to restart the
object.
Table 19 on page 67 describes the Alarms in the 'Burner' function block.
Table 19. 'Burner' function block Alarms
Name Condition CondName Message

MainBurnerError "Max ignition attempts" not reached and BurnerError Main Flame
no signal on FlameGuardMain or Feedback Error
SafeTemp and after timer in step 250
(SecondSafetyTime), 275
(FirstSafetyTime), 285
(MainFlameProvingTime), 300
(ReactionTime).
PilotBurnerError “Max ignition attempts” not reached and PilotError Pilot Flame
no signal on FlameGuardPilot or Feedback Error
(PilotFlameProvingTime)
No signal on FlameGuardPilot or
(FirstSafetyTime), 435 (CleaningTime)
No signal on FlameGuardPilot and after
timer in step 720 (FirstSafetyTime), 725
(ReactionTimer, started when
FlameGuardPilot is lost).
“Max ignition attempts” reached and no
signal on FlameGuardPilot or SafeTemp
and after timer in step 610
(ReactionTimer)
After timer in step 620 (FirstSafetyTime)
3BSE079156-600 67
Alarms and Errors Section 4 Function Block Types
Table 19. 'Burner' function block Alarms

IgniterError No signal on IgniterInOperation and IgniterError Igniter Feedback
after timer in step 215 (PreIgnitionTime) Error
or 710 (PreIgnitionTime).
No signal on StartCond and reignition
during starting in step 215.
ReignitionError “Max ignition attempts” reached and no ReigniteError Max Reignition
signal on FlameGuardMain or SafeTemp Attempts
and after timer in step 250 Reached
(SecondSafetyTime), 275
(MainFlameProvingTime)
“Max ignition attempts” reached and no
signal on FlameGuardPilot or SafeTemp
and after timer in step 225
(PilotFlameProvingTime)
PilotValveError No signal on PilotValveClosed in step ValveError Pilot Valve Not
200 or 215 Closed Before
Start
FuelValve1Error No signal on FuelValve1Closed in step ValveError Fuel Valve 1 Not
200, 215, 225 or 235 Closed Before
Start
FuelValve2Error No signal on FuelValve2Closed and in ValveError Fuel Valve 2 Not
step 200, 215, 225 or 235 Closed Before
Start
FlameError FlameGuardMain (in step 200, 215, 225, FlameError Flame Present
235, 700) or FlameGuardPilot (in step Before Start
200, 215, 700) and Config.
CheckFlameGuardsBeforeStart and not
SafeTempReached
68 3BSE079156-600
ParError
A parameter range check is always done to verify that all configuration parameters
are entered within a valid range. The parameter ParError is set to true if a
configuration parameter is set to a value outside the range. This is indicated by a red
triangle on the faceplate. The last good value will be used by the function block.
3BSE079156-600 69
Recommended use Section 4 Function Block Types
Recommended use
Always set the Fault Detection and Reaction diagnostics cycle to <2 seconds for
burner applications. This will lead to an allowed warning (FDRT time below
default value) in the Task Analysis tool.
FDRT (Fault Detection and Reaction Time) is the maximum time from an
internal error occur in the controller, to the defined action is taken.
The Start-up sequence may only occur if the potential source for the cause of the
safety-shut-down conditions disappears.
Connect the safety shut-down conditions to PriorityCmdStop.
Always make the interval between safety-shutdown and the next start attempt to
>30 seconds for oil burner control systems which are not provided with a pre-
purge function.
The start flame proving period shall be no less than that declared by the
manufacturer.
Configure the pilot flame proving period to Config.PilotFlameProvingTime.
Configure the main flame proving period to Config.MainFlameProvingTime.
If the lock-out function is used it shall be checked for proper operation during
each start-up sequence. The capability of the burner control system to store the
non-volatile lock-out status shall be checked at least during each main power
restoration.
Connect the lock-out function to StartCond
The application shall implement the Start Condition for the burner start in
accordance with EN 12952-8, EN 746-2 and EN 12953-7. In case of an abnormal
situation the application shall interrupt the 'Burner' function block by use of the
Priority Stop command.
The application shall implement the shutdown of a burner in accordance with

EN12952-9, EN 746-2 and EN 12953-7 using the Start Condition, stop and
priority stop command of the 'Burner' function block.
70 3BSE079156-600
Section 4 Function Block Types Recommended use
External flame detector devices shall conform to EN 298 for permanent

operation. Their flame failure response time shall not exceed 1 second.
The function block ‘Burner’ shall be configured such that reaction on loss of
flame during start or during operation conforms to the applicable functional
requirements of the individual application.
During online download (normal application update or Load Evaluate Go), the
user shall take appropriate precautions dependent on the properties and the time
demands of the process under control.
The parameter Config.CheckFlameGuardsBeforeStart needs to be set to true

always, except when a specific standard can be pointed out to state the contrary.
The supervision of the success of closing the FuelValve1 (at the beginning of the
Cleaning sequence) is in the users responsibility.
It is not allowed to connect the same flame guard to the parameters

FlameGuardPilot and FlameGuardMain as the function block expects separate
flame guards. If only one flame guard is used it is necessary to add logic to at
least one of the parameters. This logic is the users responsibility.
The application engineer shall use the output for the pilot valve to open specific
air-/oxygen valves outside the Burner block if required by the process.
Lock-out can mean non-volatile lock-out or volatile lock-out. The meaning of

these are as follows: (from EN 298)
non-volatile lock-out: safety-shut-down condition of the system, where a restart
can only be accomplished by the manual reset of the system and by no other
means
volatile lock-out: safety-shut-down condition of the system, where a restart can
only be accomplished by either the manual reset of the system, or an interruption
of the main power and its subsequent restoration
3BSE079156-600 71
TightnessTest Section 4 Function Block Types
TightnessTest
This function block is intended to be used in a valve proving system for a gas burner
section with at least two valves. The test is done in two ways:
• By checking that the pressure between the valves does not rise above the
corresponding pressure limit when the valves are closed.
• By checking that the pressure does not fall below the corresponding pressure
limit when the valves are closed.
The block has connections for valve orders and pressure measurements to and from
the process. Simple data types are used on the inputs and outputs, which allows for
easy development of logic outside the function block. This means that supervision
of the signal quality and status must be handled outside this function block.
All configuration of the function block is made in the Config parameter. The values
of the configuration will be active only after a download to the controller. No online
configuration of the function block is possible. If configuration parameters values
are not valid, the ParError parameter will be set to true.
EnablePartial is a component in the Config parameter. The Config.EnablePartial is
a way to shorten the time of the tightness test when certain conditions are fulfilled.
When Config.EnablePartial is activated, the supervision of the pressure levels will
be activated. If the pressure is above PH (Pressure detector High) at the start of the
test, the high-pressure condition is OK. The tightness test will then consider the high
pressure test case as passed and only perform the low pressure test case.
72 3BSE079156-600
Parameters
This section describes the input- and output parameters of the 'TightnessTest'
function block.
Input
Table 20 on page 73 describes the input parameters for the 'TightnessTest' function
block.
Table 20. Input parameters for the 'TightnessTest' function block.
Name Data type Description

PressureHigh* bool High pressure level activated
PressureLow* bool Low pressure level activated
StartCond* bool Start condition, must be TRUE to start object
PriorityCmdStop* bool Forcing object to a stop when TRUE
AutoStart* bool Start object on positive edge
AutoStop* bool Stop object on positive edge
SetAuto bool Set automatic mode
SetOutOfService bool Set Object to Out of Service mode
Reset* bool Reset of object
AEConfig dint Config error handling (1=Alarm, 2=Event, 3=Event1,
4=Level, else Alarm + ParError)
AESev dint Severity for error. Range 1 - 1000 else ParError +
(Alarms: Prev valid value used else no alarm created;
Events: No event generated).
**In/Out
3BSE079156-600 73
Table 20. Input parameters for the 'TightnessTest' function block.

EnableAE bool Enable error handling alarm/event
AEClass dint Class alarms/events. Range 1 - 9999 else ParError +
Config* TightnessTestConfig EDIT Configuration data
InteractionPar** TightnessTestPar Interaction parameter
**In/Out
Output
Table 21 on page 74 describes the output parameters for the 'TightnessTest' function
block.
Table 21. Output parameters for the 'TightnessTest' function block.
Name Data type Description SIL

FillValve* bool Order to open the Fill valve. The valve closest to the fuel 3
supply (Pressure side)
VentValve* bool Order to the ventilation valve. The Valve on to the burner 3
side. The valve draining the fuel.
Running* bool Indicates if tightness test is running 3
Passed* bool Tightness OK 3
UpstreamError* bool Indication of error on the safety valve or other valve on the 3
pressure side.
DownstreamError* bool Indication of error on the fuel valve or other valves on the 3
burner side.
74 3BSE079156-600
Table 21. Output parameters for the 'TightnessTest' function block.

AutoMode bool Automatic mode indicator 3
OutOfServiceMode bool Indication Out of Service mode 3
AEEnabled bool Error handling alarm/event enabled 3
AlState dint NONSIL CondState from Error AlarmCond (0-6) Non
Configuration
The Config parameter is a structured data type (TightnessTestConfig) containing
components for all configuration data for the 'TightnessTest' function block. The
Config parameter is an EDIT parameter. Any change of the Config data will be
activated only after a download of the changes.
Table 22. Configuration parameters for the 'TightnessTest' function block

ActTimeFillValve time Actuating time for the fill valve. Range 3 - 120s else last good
value + ParError
ActTimeVentValve time Actuating time for ventilation valve. Range 3 - 120s else last good
value + ParError
TestTime time Duration for the tightness test for each valve. Range 15 - 1200s
EnablePartial bool Enable partial tightness test if condition fulfilled
3BSE079156-600 75
Functionality
The 'TightnessTest' function block performs a sequence of tests in a valve proving
system. The purpose is to detect leakage of the valves in the system.
When the Tightness Test has passed it will remain in this state until the function
block is reset.
The tightness test of the valves on the downstream side (FuelValve2 and VentValve
in Figure 13 is done by opening the FillValve for pressurizing the volume between
the valves. The FillValve is then closed and the pressure is monitored during a
specified test time. The pressure is not allowed to fall under PH (Pressure detector
High) during that time. If the pressure falls below PH, the test fails.
The tightness test of upstream side (FuelValve1 and FillValve in the Figure 13) is
done by opening VentValve to drain the volume between the valves from pressure.
Then VentValve is closed and the pressure is monitored during a specified test time.
The pressure is not allowed to rise above PL (Pressure detector Low) during that
time. If the pressure rises above PL, the test fails.
It is only the FillValve and the VentValve that are controlled by the 'TightnessTest'
function block.
EnablePartial is a component in the Config parameter. The EnablePartial is a way
to shorten the time of the tightness test if certain conditions are fulfilled. When
enable partial is activated, the supervision of the pressure levels will be activated. If
the pressure is above PH at the start of the test, the high-pressure conditions are
considered as OK. The tightness test will then consider the high pressure test case as
passed and only perform the low pressure test case when the tightness.
76 3BSE079156-600
When the pressure is below PH at the start of the test, it is only the High-pressure
test that will be performed..
FillValve VentValve
Ventilation
Gas (P) Gas Burner

FuelValve1 FuelValve2
PH PL
Upstream Downstream
Figure 13. 'TightnessTest' functionality
3BSE079156-600 77
Operating Modes
The 'TightnessTest' function block has two operating modes, automatic and manual.
The function block can be started in manual mode from the faceplate or in automatic
mode from the code. The parameters AutoStart and AutoStop are used to start and
stop the function block in automatic mode.
The priority stop command PriorityCmdStop will stop the function block
independent of mode. If this parameter is true when trying to start, the function
block will remain in state 100: Idle.
The module has one non-operational mode, which can be set if maintenance is being
carried out, the mode is called OutOfServiceMode. No output orders are activated
when the function block is in OutOfServiceMode.
Set the function block into manual mode to return from OutOfServiceMode.
The modes can be changed from the faceplate by the corresponding button.
Changing mode to auto can also be done from code, but not when the function block
is in OutOfServiceMode.
Initial Condition
To be able to start the tightness test the input parameter StartCond must be true.
After the start has been activated, the start condition can go to false without
affecting the progress of the tightness test.
78 3BSE079156-600
States
A state machine of 'TightnessTest' is described in Figure 14 followed by Table 23 on
page 80 which describes each transition.
The 'TightnessTest' object will always be in state 100: Idle after controller power-
up.
100 Idle
Reset Start
Reset
Reset
400 PriorityStop 900 TestFailed 300 TestPassed
Start
Stop
Failed Passed
PriorityCmdStop
200 Running
Figure 14. State machine of the 'TightnessTest' function object
3BSE079156-600 79
Table 23. Transitions of the 'TightnessTest' function object State machine
Transition Description
Start Start is either made from the operator interface or with the parameter AutoStart
Stop Stop is either made from the operator interface or with the parameter AutoStop
Passed Test passed
Failed Test failed due to either upstream error or downstream error
Reset Acknowledge of object error and priority stop. Needs to be done before the
burner can be restarted. Reset is either made from the operator interface or
with the parameter Reset.
PriorityCmdStop This transition is initiated by an external fault
State 100: Idle - This is the default state of the tightness test. All result indications
(TestPassed, TestFailed) are false, and the function block is ready for a start. If a
start order is given to the tightness test the function block will go to state 200:
Running.
80 3BSE079156-600
State 200: Running - In this state, the main sequence is executed (see Figure 15,
Figure 16, Figure 17, Figure 18 for sequence diagrams and Table 24 on page 82 for
step descriptions). Depending on the result of the tightness test, the function block
will go to state 900: TestFailed or state 300: TestPassed. If the parameter
PriorityCmdStop is set during the test the block will go to state 400: Priority Stop.
FillValve
VentValve
ActTimeFillValve
ActTimeVentValve
TestTime
Step Number 100 221 222 211 212 300

Figure 15. 'TightnessTest' main sequence, Config.EnablePartial is false,
PressureHigh is not activated
FillValve
VentValve
ActTimeFillValve
ActTimeVentValve
TestTime
Step Number 100 211 212 221 222 300

Figure 16. 'TightnessTest' main sequence, Config.EnablePartial is false,
PressureHigh is activated
3BSE079156-600 81
FillValve
ActTimeFillValve
TestTime
Step Number 100 211 212 300

Figure 17. 'TightnessTest' main sequence, Config.EnablePartial is true,
PressureHigh is not activated
VentValve
ActTimeVentValve
TestTime
Step Number 100 221 222 300

Figure 18. 'TightnessTest' main sequence, Config.EnablePartial is true,
PressureHigh is activated
Table 24. Step description for 'TightnessTest' main sequence
Step Description
100 Idle
211 Open the FillValve and wait Config.ActTimeFillValve
212 Close the FillValve and wait Config.TestTime. Supervise PressureHigh when in this
step.
221 Open the VentValve and wait Config.ActTimeVentValve
222 Close the VentValve and wait Config.TestTime. Supervise PressureLow when in this
the step.
300 Test passed
82 3BSE079156-600
State 300: Test Passed - The function block will be in this state if the test has
passed. The function block will go to state 100: Idle on a reset order from the
faceplate or from the parameter reset. No orders are set in this state.
If a new start order is given, the function block will go to state 200: Running.
State 400: Priority Stop - The function block will be in this state if the parameter
PriorityCmdStop has been set to true when the test is running. The function block
will go to state 100: Idle on a reset order from the faceplate or from the parameter
Reset. All orders are reset in this state.
State 900: Test Failed - The function block will be in this state if the test has failed.
The function block will go to state 100: Idle on a reset order from the faceplate or
from the parameter Reset. No orders are set in this state.
Alarms and Errors

Table 25 on page 83 describes the Alarms in the 'TightnessTest' function block.
Table 25. 'TightnessTest' function block Alarms

UpstreamError PressureLow is not active during tests Object error In Valve Leakage
after activation of VentValve
DownstreamError PressureHigh is not active during tests Object error Ventilation or Out
after activation of FillValve Valve Leakage
ParError
3BSE079156-600 83
Recommended use
Always set the Fault Detection and Reaction diagnostics cycle to <3 seconds for
Tightness Test applications.
FDRT (Fault Detection and Reaction Time) is the maximum time from an
internal error occur in the controller, to the defined action is taken.
Set the parameter Config.TestTime to the leakage testing time as declared by the
manufacturer.
The response time to achieve safety shutdown, whenever this is required, shall
not exceed 1 second after a functional failure has been detected.
Connect the functional failure conditions to PriorityCmdStop.
After a fault is detected the valve proving system shall execute safety actions
according to EN1643.
It is the responsibility of the application engineer and implementation of the

burner management system to set the correct pressure limits and reaction time for
the Tightness Test.
Depending on the volume between the main gas valves, the gas pressure and the
set points of the gas pressure monitoring device, the leakage testing time must be
adjusted in a way that a leakage rate of 0,1 % of the burner heat input, at least 50
dm³/h, will be safely detected.
A leak gas flow rate of 0,1 % of the nominal volume flow at maximum firing
rate, but at least 50 dm³/h, shall be safely detected.
The application shall implement diagnostics of the pressure switches.
It is the responsibility of the application engineer to define the amount of Gas

used during the tightness test. Limits are defined for discharging into the
combustion chamber according to EN1643.
84 3BSE079156-600
Section 4 Function Block Types Lambda
Lambda
The 'Lambda' function block is intended to be used for calculating and supervising
the air to fuel ratio lambda in a burner management system. The calculation is made
by comparing the fuel flow and energy density with the airflow in to the process.
The calculation is based on the fact that 1 Nm3 of air is required for burning 1 kWh
of fuel. A correction factor must be used for deviations from the mentioned
assumption. If the lambda value is outside a configurable range the function block
sets an alarm and output parameters indicating the deviation.
The calculated Lambda value is limited to 1000.
The function block can handle up to three different inputs of fuel, one for gas and
two for solid or liquid fuel. Additional to the airflow in to the process there is an
input on the function block for oxygen flow.
3BSE079156-600 85
Parameters
This section describes the input- and output parameters of the 'Lambda' function
block.
Input
Table 26 on page 86 describes the input parameters for the 'Lambda' function block.
Table 26. Input parameters for the 'Lambda' function block.

Enable* bool Enables the Lambda calculation. If False Lambda =
Config.PredeterminedValue
AirFlow* real AirFlow Unit: Nm3/h. Range 0 - 1.0e10 else last good value
+ ParError
OxygenFlow* real OxygenFlow Unit: Nm3/h. Range 0 - 1.0e10 else last good
value + ParError
GasFlow* real GasFlow Unit: Nm3/h. Range 0 - 1.0e10 else last good
value + ParError
GasEnergy* real GasEnergy Unit: kWh/Nm3. Range 0 - 1.0e10 else last
good value + ParError
GasCorrection* real Correction factor for energy density of fuel. Range 0 -
1.0e10 else last good value + ParError
OilFlow* real OilFlow Unit: kg/h. Range 0 - 1.0e10 else last good value +
ParError
OilEnergy* real OilEnergy Unit: kWh/kg. Range 0 - 1.0e10 else last good
value + ParError
**In/Out
86 3BSE079156-600
Table 26. Input parameters for the 'Lambda' function block.

OilCorrection* real Correction factor for energy density of fuel. Range 0 -
FuelFlow real FuelFlow Unit: kg/h. Range 0 - 1.0e10 else last good value
+ ParError
FuelEnergy real FuelEnergy Unit: kWh/kg. Range 0 - 1.0e10 else last good
value + ParError
FuelCorrection real Correction factor for energy density of fuel. Range 0 -
SignalError* bool Fault on external inputs used by this module (xFlow,
xEnergy, xCorrection)
Reset bool Reset object error
AESev dint Severity for error. Range 1 - 1000 else ParError + (Alarms:
Prev valid value used else no alarm created; Events: No
event generated).
Config* LambdaConfig EDIT Configuration data
InteractionPar** LambdaPar Interaction parameter
**In/Out
3BSE079156-600 87
Output
Table 27 on page 88 describes the input parameters for the 'Lambda' function block.
Table 27. Output parameters for the 'Lambda' function block.

Enabled* real Lambda value calculation is enabled 3
Lambda* real Lambda value (maximum output 1000) 3
LambdaError* bool Lambda any limit (H, L, LL, LLL) activated 3
LambdaH bool Lambda value > Config.LimitLambdaH 3
LambdaL bool Lambda value < Config.LimitLambdaL, Longer than 3
Config.TimeLambdaL
LambdaLL bool Lambda value < Config.LimitLambdaLL, Longer than 3
Config.TimeLambdaLL
LambdaLLL bool Lambda value < Config.LimitLambdaLLL 3
88 3BSE079156-600
Configuration
Table 28 on page 89 describes the configuration parameters for the 'Lambda'
function block.
Table 28. Configuration parameters for the 'Lambda' function block.

LimitLambdaH real High limit for Lambda value. Range: LimitLambdaL - 1000.0
LimitLambdaL real Low limit for Lambda value. Range: LimitLambdaLL -
LimitLambdaH else last good value + ParError
TimeLambdaL time Max time for low Lambda value. Range 0 - 60s else last
LimitLambdaLL real Low low limit for Lambda value. Range: LimitLambdaLLL -
LimitLambdaL else last good value + ParError
TimeLambdaLL time Max time for low low Lambda value. Range 0 - 60s else last
LimitLambdaLLL real Low low low limit for Lambda value. Range: 0.0 - LambdaLL
PredeterminedValue real Lambda value if SignalError or not Enable. Range 0.0 -
1000.0 else last good value + ParError
3BSE079156-600 89
Functionality
The 'Lambda' function block calculates the Lambda value by dividing the airflow
with the energy flow. The units of the gaseous fuel are in Nm3. The units for energy
density are kWh/kg for fluid and solid fuel, and kWh/Nm3 for gas. The units for the
flow are kg/h for fluid and solid fuel, and Nm3/h for gas.
The unit Nm3 (normal cubic meter) is the volume of a gas in m3 measured at a
temperature of 0 °C and a pressure of 1 bar.
The air fuel ratio is calculated according to the following formula.
Qair = Air Flow
QO2 = Oxygen flow
Q = Fuel flow
E = Energy Density
C = correction factor for the energy density
′ = Fuel 1
″ = Fuel 2
‴ = Fuel 3
4.762 = ratio oxygen in air. (21% oxygen in air => 100/21)
Qair + 4.762 × Q02

=
E × C × Q + E × C × Q + E × C × Q
The correction factor for the different fuels can either be a fixed value set by the
application engineer or connected to measurement equipment in the process.
90 3BSE079156-600
There are four different limit conditions for the lambda value.
• Lambda is > Config.LambdaH
• Lambda < Config.LambdaL more than Config.TimeLambdaL
• Lambda < Config.LambdaLL more than Config.TimeLambdaLL
• Lambda < Config.LambdaLLL
When any of these conditions are violated the LambdaError is set.
Alarms and Errors

Table 29 on page 91 describes the Alarms in the 'Lambda' function block.
Table 29. 'Lambda' function block Alarms

LambdaH Enabled = True and Lambda value is Object error LambdaH
above configured Lambda high limit.
LambdaL Enabled = True and Lambda value is Object error LambdaL
below configured Lambda low limit.
LambdaLL Enabled = True and Lambda value is Object error LambdaLL
below configured Lambda low low limit
more than the configured time for the
limit.
LambdaLLL Enabled = True and Lambda value is Object error LambdaLLL
below configured Lambda low low low
limit more than the configured time for
the limit.
Signal error Set when parameter SignalError is set. Object error Signal error
ParError
3BSE079156-600 91
Recommended use
All the input values must be of the right unit for the calculation to be correct. For
example, all gas flows are in Nm3. If the measured values are of different units,
the values must be corrected to the right measure units before connected to the
function block.
There is one high limit and three low limits; low, lowlow and lowlowlow for the
lambda value, which are all configurable. If the calculated lambda value is
outside of these limits, the function block will set the LambdaError signal and
generate an alarm for the condition.
To enable the supervision and the calculation it is necessary to set the parameter
Enable to true. When the input Enable is set to false the supervision will be
disabled and the output value set to the Config.PredeterminedValue.
92 3BSE079156-600
Section 4 Function Block Types RealIn2oo3
RealIn2oo3
'RealIn2oo3' analyzes the inputs In1, In2 and In3 and calculates the maximum-,
minimum- and average values of the valid inputs and copies them to the outputs
HighestInputValue, LowestInputValue and AverageInputValue.
'RealIn2oo3' monitors the statuses of the inputs and their deviation from each other
to decide which inputs are valid.
If one input is invalid, it is excluded from the calculation of the output signals. If
more inputs are invalid, Error is set and Config.PredeterminedValue is set at the
outputs.
Signals from process objects such as a temperature transmitter can use the
Realn2oo3 object.
Parameters
This section describes the input- and output parameters of the 'RealIn2oo3' function
block.
Input
Table 30 on page 93 describes the input parameters for the 'RealIn2oo3' function
block.
Table 30. Input parameters for the 'RealIn2oo3' function block.

Description string[40] Object description.
In1* ** RealIO Input for the first signal
In2* ** RealIO Input for the second signal
**In/Out
3BSE079156-600 93
Table 30. Input parameters for the 'RealIn2oo3' function block.

In3* ** RealIO Input for the third signal
Reset bool Reset object error
Config* RealIn2oo3Config EDIT Configuration data
InteractionPar** RealIn2oo3Par Interaction parameter
**In/Out
94 3BSE079156-600
Output
Table 31 on page 95 describes the output parameters for the 'RealIn2oo3' function
block.
Table 31. Output parameters for the 'RealIn2oo3' function block.

AverageInputValue* real Output that gives the average value of the three (or two 3
in case one input is deemed invalid) inputs
HighestInputValue* real Output that gives the maximum value of the three (or two 3
LowestInputValue* real Output that gives the minimum value of the three (or two 3
Fault1oo3* bool Output that is set when one input deviates and the delay 3
time has expired, or when status of one input is bad
Error* bool Indicates error, set when three inputs deviate and the 3
delay time has expired, or when status of more than one
input is bad
3BSE079156-600 95
Configuration Section 4 Function Block Types
Configuration
Table 32 on page 96 describes the configuration parameters for the 'RealIn2oo3'
function block.
Table 32. Configuration parameters for the 'RealIn2oo3' function block

DeviationLimit real Maximum allowed deviation between (RealIO) input values.
Range 0.0 - 1.0e10 else last good value + ParError
DelayTime time A time limit for how long an input is allowed to exceed the
deviation limit. Range 0 - 15s else last good value + ParError
QualityConfig dint 0=IOStatus considered only, 1=Overrides or bad status gives
bad quality, 2=Overrides or good status gives good quality, else
PredeterminedValue real Value of parameters AverageInputValue, HighestInputValue and
LowestInputValue if Error. Range -1.0e10 - 1.0e10 else last
96 3BSE079156-600
Functionality
The object calculates the three outputs AverageInputValue, HighestInputValue and
LowestInputValue. These are calculated with actual values of valid input signals. An
input cannot be valid unless the IO signal status is good. Validity is also checked
concerning the difference between the input signals and the Config.DeviationLimit.
The following different cases exist:
• A: no inputs are within Config.DeviationLimit from each other
• B: two inputs are within Config.DeviationLimit from each other and both have
IO signal status that is good
• C: not possible to decide which two are within Config.DeviationLimit from
each other
• D: all inputs are valid and within Config.DeviationLimit from each other and all
have IO signal status that is good
The object uses the following internal calculation:
Diff12 = |In1 - In2| ≤ Config.DeviationLimit AND In1.Status = Good AND
In2.Status = Good
In3.Status = Good
In3.Status = Good
3BSE079156-600 97
Alarms and Errors Section 4 Function Block Types
The validity (Valid[1-3]) of the inputs is created according to table Table 33 on page
98 (0-false, 1-true).
Table 33. Cases and Vadility
Case Diff12 Diff13 Diff23 Valid1 Valid2 Valid3 Error Fault1oo3

A 0 0 0 0 0 0 1 0
B 0 0 1 0 1 1 0 1
B 0 1 0 1 0 1 0 1
C 0 1 1 1 1 1 0 1
B 1 0 0 1 1 0 0 1
C 1 0 1 1 1 1 0 1
C 1 1 0 1 1 1 0 1
D 1 1 1 1 1 1 0 0
When there are valid inputs (case B, C & D) the parameter AverageInputValue is
calculated according to the following formula:
Valid1 × In1 + Valid2 × In2 + Valid3 × In3

Average Value =
Valid1 + Valid2 + Valid3
Both the parameters HighestInputValue and LowestInputValue are calculated with

only the valid inputs, for example if only Valid2 and Valid3 are set then it is only In2
and In3 that are used.
When there is no validity (case A) of the inputs, the three outputs are set to the
predetermined value configured by the parameter Config.PredeterminedValue.
Alarms and Errors

Table 34 on page 99 describes the Alarms in the 'RealIn2oo3' function block.
98 3BSE079156-600
Only one of the alarms in Table 34 on page 99 will be shown in the eventlog at
any given time.
Table 34. 'RealIn2oo3' function block Alarms

Fault1oo3 Immediately when a signal status is bad. Status nnn - Signal
One input signal deviates more than the Warning
Config.DeviationLimit from one of the
others after Config.DelayTime has
elapsed.
Dependent on which signal that is faulty,
the message 'nnn' will be 'In1', 'In2' or
'In3'.
Error Immediately if two signal or more have Status nnn - Signal error
bad status.
Three input signals deviates more than
the Config.DeviationLimit from each
other after Config.DelayTime has
elapsed.
One input has bad quality and the other
inputs deviates more than the
Config.DeviationLimit from each other
after Config.DelayTime has elapsed.
Dependent on the error situation the
message 'nnn' will display the signals
that generates the error:
'In1; In2;', 'In1; In3;', 'In2; In3;' or 'In1;
In2; In3;'.
The 'nnn' will be blank in case the error
is due to that three input signals
deviates.
3BSE079156-600 99
ParError
Recommended use
The setting of both the Config.DeviationLimit and the Config.DelayTime shall be

in accordance with the requirements for the specific application.
The discrepancy timer shall be taken into account for the Fault Detection and
Reaction time of the related safety loop.
When a degradation of the 2oo3 voting element leads to a corruption of

application Software architectural requirements, the Fault1oo3 output can be
used to control the situation (e.g. by starting a timer for a shutdown after the
Mean Time to Restoration).
100 3BSE079156-600
Section 4 Function Block Types ComplementIn
ComplementIn
Use 'ComplementIn' to monitor a digital input where the quality of the input is
important. This object is able to detect short-circuit and an open-circuit by
analyzing a second input. Signals from process objects such as flame detectors can
use the object.
'ComplementIn' analyzes the inputs In1 and In2 and copies In1.Value to Out as long
as the inputs are valid.
'ComplementIn' monitors the statuses of the inputs (In1 and In2) and checks that
their values are inverted in relation to each other to decide if the inputs are valid.
This means that the value of In2 always shall be the opposite to In1.
If the inputs are invalid, Error is set and Config.PredeterminedValue is set at the
output.
3BSE079156-600 101
Parameters
This section describes the input- and output parameters of the 'ComplementIn'
function block.
Input
Table 35 on page 102 describes the input parameters for the 'ComplementIn'
function block.
Table 35. Input parameters for the 'ComplementIn' function block.

In1* ** BoolIO Input for the first signal
In2* ** BoolIO Input for the second signal
Reset bool Acknowledge of Object Error
Config* ComplementInConfig EDIT Configuration data
InteractionPar** ComplementInPar Interaction parameter
**In/Out
102 3BSE079156-600
Output
Table 36 on page 103 describes the output parameters for the 'ComplementIn'
function block.
Table 36. Output parameters for the 'ComplementIn' function block.

Out* bool Output 3
Error* bool Indicates error, set when the discrepancy time has expired or 3
when status of at least one input signal is bad
Configuration
Table 37 on page 103 describes the configuration parameters for the 'ComplementIn'
function block.
Table 37. Configuration parameters for the 'ComplementIn' function block

DiscrepancyTime time Maximum time for discrepancy of both inputs. Range 0 - 15s
QualityConfig dint 0=IOStatus considered only, 1=Overrides or bad status gives
bad quality, 2=Overrides or good status gives good quality, else
PredeterminedValue bool Value of parameter Out if Error
3BSE079156-600 103
Functionality
The ‘ComplementIn’ object turns two Boolean inputs to one output. The first input
shall be connected to In1 and is copied directly to the output Out. If Error is true, a
predetermined value is copied to Out. The predetermined value is configurable and
connected as a value to the input Config.PredeterminedValue.
The second input shall be connected to In2 and acts as a check. In2 shall always be
inverted in relation to In1. In1 and In2 are allowed to be equal for a certain period.
The duration of this period is configurable and connected as a value to the input
Config.DiscrepancyTime.
The discrepancy timer starts when the signals are equal. If the discrepancy time
elapses and the signals are not complement to each other the Error and an alarm
inside the object is set, if complementary at this time no action is made. If the signal
quality of any of the inputs is not good, Error is set immediately. Error is reset when
the inputs are inverted to each other, both their qualities are good and the error has
been acknowledged on the faceplate or with the parameter Reset.
104 3BSE079156-600
Alarms and Errors

Table 38 on page 105 describes the Alarms in the 'ComplementIn' function block
Table 38. 'ComplementIn' function block Alarm

DiscrepancyError Config.DiscrepancyTime has expired. Object error Discrepancy
Error
Error Status of at least one input signal is bad Object error Signal error
(depending on Config.QualityConfig).
ParError
Recommended use
The Config.DiscrepancyTime shall be taken into account for the Fault Detection
and Reaction time of the related safety loop.
3BSE079156-600 105
106 3BSE079156-600
Section 5 Create Safety Logic Safety precautions
Section 5 Create Safety Logic
This section describes the necessary precautions required to implement the burner
management application in a safe manner.
For function block specific safety notes refer to the Recommended Use chapter for
the corresponding function block.
All warnings and cautions in AC 800M High Integrity Safety Manual
(3BNP004865*) are generally valid and shall be adhered to.
Safety precautions
The application shall be in accordance with the details provided by the
manufacturer's instructions.
The application shall implement the Lock Out function and the process to restart
the system. This includes for instance the mandatory use of manual reset devices
for a restart.
The application shall implement functionality in accordance with EN 267:

“In the case of permanent loss of the actuating energy the burner shall proceed to
a safe condition. If an on/off control, switch or limiter operates, the fuel oil
supply shall be automatically cut off immediately.“
As far as practicable the application design shall minimize the safety-related part
of the software. This means that the End User shall as far as possible, split safety
and non-safety functions in different applications.
If external safety devices are used, the application shall be able to process a
requested shutdown independent from the actions of the Burner Library
elements.
3BSE079156-600 107
Safety precautions Section 5 Create Safety Logic
The sum of the safety times and the closing time of the shut off valve/final
element shall be less than the fault tolerance time of the relevant process
function.
This fault tolerance time shall be defined by the End User and in compliance with
the relevant application standard, the configurable safety times according to
applicable standards and the application cycle times have to be adjusted
accordingly.
Reset from lock-out shall be implemented in the external safety logic such that
static or dynamic failures of the reset device do not cause the system to operate
outside the requirements of the applicable standards or regulations (e.g. by
evaluating the logical and temporal properties of the reset signal).
All safety functions of the individual application which are not covered by the
function blocks (such as purging, protection of the heat generator, flue gas
discharge, fuel system, etc.) shall be implemented in the external safety logic
according to the requirements of the applicable standards or regulations.
It is the users responsibility to check the ParError outputs of each function block
and make appropriate and necessary actions in case an error is indicated by these
outputs.
The configuration parameters of all function blocks shall be confirmed (including

the default values) by the users.
The error output from any function blocks shall be treated by the safety
application to react on the detected error appropriately.
108 3BSE079156-600
Section 5 Create Safety Logic Documentation of the Approved Application Version
Documentation of the Approved Application Version

To be able to determine the version of the application which has been approved the
checksum of the application can be used. This checksum shall be documented and
stored for future use. Any change in the application results in a new checksum for
the application.
The checksum for an application can be found in the BuildInfo. The build info is
fetched from the Statistics information found in the menu for the application. See
Figure 19 on page 109.
Figure 19. Statistics
3BSE079156-600 109
Documentation of the Approved Application Version Section 5 Create Safety Logic
The actual information regarding the check sum is seen in Figure 20 on page 110.
Figure 20. Checksum information in BuildInfo
110 3BSE079156-600
Section 5 Create Safety Logic Documentation of the Approved Application Version
The checksum for the downloaded application in the controller is found in “Show
Downloaded Items” in the dialog for remote system. As seen in Figure 21 on page
111.
Figure 21. Remote System information
3BSE079156-600 111
Documentation of the Approved Application Version Section 5 Create Safety Logic
If the application check sum in the Control Builder M Professional is the same as
the check sum in the downloaded application in the controller. Numbers in the
signature shall match the numbers of the application checksum except for the first
number/letter. See Figure 20 on page 110 and Figure 22 on page 112. In this
example the checksums are:
• BuildInfo: 1613048496
• Downloaded Items: R613048496.
These checksums matches which means that it is the approved application version
that also is running on the controller..
Figure 22. Checksum information from Downloaded Items
112 3BSE079156-600
Section 6 Graphical User Interface Overview
Section 6 Graphical User Interface
This section describes the graphical user interface.
Overview
The user interface consists of the Graphic Display, which is the main operator
window. From the Graphic Display the operator can access different Faceplates to
control each function block. Display Elements are graphical components used to
create the content of the Graphic Display.
Common functionality
Functionality is accessed mainly by the use of control buttons located in the lower
section of the faceplates. Many of the faceplates use the same buttons, see Table 39
on page 113. Indicators located on the upper part of the faceplate inform the user
about different aspects of the process. Most faceplates use the same indicators, see
Table 40 on page 115.
Buttons
Table 39 on page 113 descibes the common faceplate buttons.
Table 39. Common buttons
Button Description
Sets object in manual mode
Sets object in auto mode
3BSE079156-600 113
Common functionality Section 6 Graphical User Interface
Table 39. Common buttons
Button Description
Starts the object
Stops the object
Resets the object
Sets the object in out of service
Acknowledge order
View detailed trend display
Create or read operator notes
114 3BSE079156-600
Section 6 Graphical User Interface Common functionality
Indicators
Table 40 on page 115 describes the common faceplate indicators.
Table 40. Common indicators
Icon Description
Forced IO in simulated mode
Simulated mode
Forced IO
Forced IO and parameter error
Parameter error
Manual mode
Automatic service mode
Out of service mode
Manual mode and parameter error
3BSE079156-600 115
Common functionality Section 6 Graphical User Interface
Table 40. Common indicators
Icon Description
Automatic mode and parameter error
Out of service and parameter error
Off
On
Asset optimization Severity 1–250
Fault state
116 3BSE079156-600
Section 6 Graphical User Interface Graphic Display
Graphic Display
The Graphic Display provides an overview of the process. It also gives access to the
different Faceplates. Figure 23 on page 117 presents and example of a Graphic
Display.
Figure 23. Example of a Graphic Display
For more information about the Graphic Display, refer to System 800xA Operations
(3BSE036904*).
3BSE079156-600 117
Faceplates Section 6 Graphical User Interface
Faceplates
A Faceplate is a process dialog for supervision and control. There are three types of
faceplates; Reduced Faceplate, Faceplate and Extended Faceplate. For more
information about Faceplates, refer to System 800xA Operations (3BSE036904*).
Reduced Faceplate
The Reduced Faceplate provides only the most necessary functionality and presents
only a minimal amount of information to the operator. It basically consists of five
sections, described in Table 41 on page 118.
Table 41. Reduced Faceplate overview
Item Description
A Instance name and Alarm indicator
A B Indicators (see Table 40 on page 115) and Create operator note

button
B
C Process values
C
D Control buttons (see Table 39 on page 113)
D
E Selection of faceplate type (Reduced Faceplate, Faceplate,
E
Extended Faceplate
Faceplate
This is usually the default view. The Faceplate provides the most commonly used
functionality. It also presents information about the process to the operator. It
118 3BSE079156-600
Section 6 Graphical User Interface Faceplates
basically consists of five sections, described in Table 42 on page 119.
Table 42. Faceplate overview
Item Description
A B Indicators (see Table 40 on page 115) and Create operator

note button
B
C Process values
C D Control buttons (see Table 39 on page 113)
E Selection of faceplate type (Reduced Faceplate, Normal
Faceplate, Extended Faceplate
D
E
3BSE079156-600 119
Faceplates Section 6 Graphical User Interface
Extended Faceplate
The Extended Faceplate provides the complete set of functionality for the object. It
also presents all the available information about the process related to the object. It
basically consists of six sections, described in Table 43 on page 120.
Table 43. Extended Faceplate overview
Item Description
A B Indicators (see Table 40 on page

115) and Create operator note button
B
C Tab group 1, process values
D Tab group 2, process values
E Control buttons (see Table 39 on
page 113)
C D
F Selection of faceplate type (Reduced
Faceplate, Faceplate, Extended
Faceplate
E
F
The tab content is generally structured in the following categories:

• Control - Shows the main sequence or the process values
• Signals - Shows active output- or input signals
• Configuration - Shows the values of all configuration parameters
• Trim Step - Shows a graph of a value
• Errors - Shows alarms and errors
• Override - Makes it possible to override alarms
120 3BSE079156-600
Section 6 Graphical User Interface Display Elements
Display Elements
Display elements represent different function block objects in the Graphic Display.
They provide access to the corresponding Faceplates as well as information about
process status. For more information about Display Elements, refer to System 800xA
Operations (3BSE036904*).
Burner
This section describes the Faceplates and Display elements related to the Burner
object.
Faceplate
The Burner object offers a Faceplate and an extended Faceplate.
3BSE079156-600 121
Faceplate Section 6 Graphical User Interface
Faceplate
The Burner Faceplate displays the status of the main burner sequence, see Table 44
on page 122. For information about control button functionality see Table 39 on
page 113.
Table 44. Burner Faceplate
Item Description
Preignition Time* See PreIgnitionTime, Table 7 on
page 47. Remaining time is
displayed when this item is active
Pilot Burner Ignition** Active in step 210, see Figure 8 on
page 55 and Table 10 on page 56
First Safety Time* See FirstSafetyTime, Table 7 on
Pilot Flame Proving Time** See PilotFlameProvingTime, Table 7
on page 47. Remaining time is
Main Burner Ignition* Active in step 210 and 215, see
Figure 8 on page 55, Table 10 on
page 56, Figure 9 on page 57 and
Table 11 on page 58
Fuel Filling Time* See FillingTime, Table 7 on page 47.
Remaining time is displayed when
this item is active
Second Safety Time** See SecondSafetyTime, Table 7 on
Main Flame Proving Time* See MainFlameProvingTime, Table 7
*Always enabled.
**Enabled only when the burner is configured as intermittent or interrupted.
122 3BSE079156-600
Section 6 Graphical User Interface Faceplate
Extended Faceplate
The extended faceplate provides an overview of the sequence and the status of the
inputs and outputs. It includes a number of tabs presented in the tables below. It also
offers the faceplate specific control buttons and indicators described in Table 45 on
page 123 and Table 46 on page 124 respectively. For information about common
control button functionality see Table 39 on page 113.
Table 45. Control buttons specific to the Extended Burner Faceplate
Button Description
Start cleaning sequence, button is available when the burner is in state 100: Idle
Start the pilot test, function is available in state 100: Idle
Stop the pilot test
Start main burner in intermittent mode
Stop main burner in intermittent mode, button is available when the burner is in state 300:
Running
3BSE079156-600 123
Table 46. Indicators specific to the Extended Burner Faceplate
Icon Description
Performing pilot test
Performing cleaning
124 3BSE079156-600
Table 47. Control tab on the Burner Extended Faceplate
Item Description
Preignition Time See PreIgnitionTime, Table 7 on
Pilot Burner Ignition Active in step 210, see Table 8 on
page 55 and Table 10 on page 56
First Safety Time See FirstSafetyTime, Table 7 on
Pilot Flame Proving Time See PilotFlameProvingTime, Table 7
Main Burner Ignition Active in step 210 and 215, see
Table 8 on page 55, Table 10 on
page 56, Table 9 on page 57 and
Table 11 on page 58
Fuel Filling Time See FillingTime, Table 7 on page 47.
Remaining time is displayed when
this item is active
Second Safety Time See SecondSafetyTime, Table 7 on
Main Flame Proving Time See MainFlameProvingTime, Table 7
3BSE079156-600 125
The content of the Cleaning tab is visible only when the configuration parameter
Config.EnableCleaning is set.
Table 48. Cleaning tab on the Burner Extended Faceplate
Item Description
Pilot Burner Ignition Active in step 210, see Figure 8 on page 55
and Table 10 on page 56
First Safety Time See FirstSafetyTime, Table 7 on page 47.
Remaining time is displayed when this item
is active
Cleaning Time See CleaningTime, Table 7 on page 47.
Remaining time is displayed when this item
is active.
Depressurize Time See DepressurizeTime, Table 7 on page
47. Remaining time is displayed when this
item is active.
Cleaning Done Active in step 455, see Table 13 on page 61
126 3BSE079156-600
Table 49. Input Signals tab on the Burner Extended Faceplate
Item Description
Initial Start Condition See StartCond, Table 5 on page 42
Priority Command Stop See PriorityCmdStop, Table 5 on
page 42
Safe Temperature Reached See SafeTempReached, Table 5 on
page 42
Main Flame Guard See FlameGuardMain, Table 5 on
page 42
Pilot Flame Guard See FlameGuardPilot, Table 5 on
page 42
Table 50. Output Signals tab on the Burner Extended Faceplate
Item Description
Igniter See Igniter, Table 6 on page 45
Atomizing Valve See AtomizingValve, Table 6 on page 45
Cleaning Valve See CleaningValve, Table 6 on page 45
Air Valve See AirValve, Table 6 on page 45
Oxygen Valve See OxygenValve, Table 6 on page 45
Pilot Fuel Valve See PilotValve, Table 6 on page 45
Fuel Valve 1 See FuelValve1, Table 6 on page 45
Fuel Valve 2 See FuelValve2, Table 6 on page 45
3BSE079156-600 127
Table 51. Configuration 1 tab on the Burner Extended Faceplate
Item Description
First Safety Time See FirstSafetyTime, Table 7 on
page 47
Second Safety Time See SecondSafetyTime, Table 7 on
page 47
Fuel Filling Time See FillingTime, Table 7 on page 47
Reaction Time See ReactionTime, Table 7 on page
47
Preignition Time See PreIgnitionTime, Table 7 on
page 47
Cleaning Time See CleaningTime, Table 7 on page
47
Pilot Flame Proving Time See PilotFlameProvingTime, Table 7
on page 47
Main Flame Proving Time See MainFlameProvingTime, Table 7
on page 47
Depressurize Time See DepressurizeTime, Table 7 on
page 47
Between Reignition Time See BetweenReignitionTime, Table 7
on page 47
128 3BSE079156-600
Table 52. Configuration 2 tab on the Burner Extended Faceplate
Item Description
Type of Ignition See IgnitionType, Table 7 on page
47
Cleaning Enabled See EnableCleaning, Table 7 on
page 47
Flame Present Check Enabled See
CheckFlameGuardsBeforeStart,
Table 7 on page 47
Max Ignition Attempts Start See MaxIgnitionAttemptsStart,
Table 7 on page 47
Max Ignition Attempts Running See
MaxIgnitionAttemptsRunning,
Table 7 on page 47
Max Ignition Attempts See MaxIgnitionAttemptsInterm,
Intermittent Table 7 on page 47
3BSE079156-600 129
Table 53. Program Step tab on the Burner Extended Faceplate
Item Description
Step Shows step number as a stepped graph according
to time diagrams, see States on page 50
130 3BSE079156-600
Table 54. Errors tab on the Burner Extended Faceplate
Item Description
Main Burner Error See MainBurnerError, Table 19 on
page 67
Pilot Burner Error See PilotBurnerError, Table 19 on
page 67
Ignitor Feedback Missing See IgniterError, Table 19 on page
67
Pilot Valve Not Closed See PilotValveError, Table 19 on
page 67
Fuel Valve 1 Not Closed See FuelValve1Error, Table 19 on
page 67
Fuel Valve 2 Not Closed See FuelValve2Error, Table 19 on
page 67
Reignition Error See ReignitionError, Table 19 on
page 67
Flame Present Before Start See FlameError, Table 19 on page
67
3BSE079156-600 131
Table 55. Override 1 tab on the Burner Extended Faceplate
Item Description
Main Burner Alarm See MainBurnerError, Table 19 on
page 67
Pilot Burner Alarm See PilotBurnerError, Table 19 on
page 67
Flame Alarm See FlameError, Table 19 on page
67
Table 56. Override 2 tab on the Burner Extended Faceplate
Item Description
Igniter Alarm See IgniterError, Table 19 on page
67
Valve Position Alarm See PilotValveError,
FuelValve1Error, FuelValve2Error
Table 19 on page 67
Reignition Alarm See ReignitionError, Table 19 on
page 67
132 3BSE079156-600
Display Elements
Table 57 on page 133 describes the Display Elements available for the Burner
object.
Table 57. Display Elements in the Burner Object
Display Element Description

Appearance of the Burner Display Element icon in state 100: Idle
Appearance of the Burner Display Element icon in state 200: Starting
Appearance of the Burner Display Element icon in state 300: Running
Burner Display Element Tag
3BSE079156-600 133
Tightness Test Section 6 Graphical User Interface
Tightness Test
This section describes the Faceplates and Display elements related to the
'TightnessTest' object.
Faceplate
The 'TightnessTest' object offers a Reduced Faceplate, a Faceplate and an extended
Faceplate.
Reduced Faceplate
The 'TightnessTest' Reduced Faceplate displays the result of the main test sequence,
see Table 58 on page 134. For information about control button functionality see
Table 58. 'TightnessTest' Reduced Faceplate
Item Description
Tightness Test Passed Step 300: Test passed, see States on
page 79
Tightness Test Failed Step 900: Test failed, see States on
page 79
Faceplate
The 'TightnessTest' Faceplate displays the status of the main test sequence, see
Table 59 on page 135. For information about control button functionality see
134 3BSE079156-600
Table 59. 'TightnessTest' Faceplate
Item Description
Idle Step 100: Idle, see States on page
79
Running Test Step 200: Running, see States on
page 79
page 79
page 79
Extended Faceplate
The 'TightnessTest' Extended Faceplate includes a number of tabs presented in the
tables below. For information about control button functionality see Table 39 on
3BSE079156-600 135
page 113.
Table 60. Control tab on the 'TightnessTest' Extended Faceplate
Item Description
Idle Step 100: Idle, see States on page
79
Running Test Step 200: Running, see States on
page 79
page 79
page 79
Table 61. Signals tab on the 'TightnessTest' Extended Faceplate
Item Description
Start Condition See StartCond, Table 20 on page 73
Priority Command Stop See PriorityCmdStop, Table 20 on
page 73
Pressure High See PressureHigh, Table 20 on page
73
Pressure Low See PressureLow, Table 20 on page
73
Open Fill Valve See FillValve, Table 21 on page 74
Open Ventilation Valve See VentValve, Table 21 on page 74
136 3BSE079156-600
Table 62. Configuration tab on the 'TightnessTest' Extended Faceplate
Item Description
Fill Valve Actuating Time See ActTimeFillValve, Table 22 on
page 75
Ventilation Valve Actuating See ActTimeVentValve, Table 22 on
Time page 75
Test Time See TestTime, Table 22 on page 75
Enable Partial See EnablePartial, Table 22 on page
75
Table 63. Program Step tab on the 'TightnessTest' Extended Faceplate
Item Description
Step Shows step number as a stepped graph according
to time diagrams, see States on page 79
3BSE079156-600 137
Table 64. Errors tab on the 'TightnessTest' Extended Faceplate
Item Description
Upstream Error See UpstreamError, Table 25 on page 83
Downstream Error See DownstreamError, Table 25 on page
83
Table 65. Override tab on the 'TightnessTest' Extended Faceplate
Item Description
Alarm disabled See UpstreamError, DownStreamError
Table 25 on page 83
138 3BSE079156-600
Display Elements
Table 66 on page 139 describes the Display Elements available for the
'TightnessTest' object.
Table 66. Display Elements in the 'TightnessTest' Object

Appearance of the 'TightnessTest' Display Element icon in state 100: Idle
Appearance of the 'TightnessTest' Display Element icon in state 200:

Running
Appearance of the 'TightnessTest' Display Element icon in state 300: Test

Passed
'TightnessTest' Display Element Tag
3BSE079156-600 139
Lambda Section 6 Graphical User Interface
Lambda
This section describes the Faceplates and Display elements related to the 'Lambda'
object.
Faceplate
The 'Lambda' object offers a faceplate and an extended Faceplate.
Faceplate
The 'Lambda' Faceplate displays the calculated Lambda value. For information
about control button functionality see Table 39 on page 113.
Table 67. 'Lambda' Faceplate
Item Description
Lambda Calculated Lambda value, see Functionality on
page 90
140 3BSE079156-600
Extended Faceplate
The 'Lambda' Extended Faceplate includes a number of tabs presented in the tables
below. For information about control button functionality see Table 39 on page 113.
Table 68. Control tab on the 'Lambda' Extended Faceplate
Item Description
Lambda Calculated Lambda value, see Functionality on
page 90
3BSE079156-600 141
Table 69. Trim Curves tab on the 'Lambda' Extended Faceplate
Item Description
Lambda Shows the Calculated Lambda value, see
Functionality on page 90
142 3BSE079156-600
Table 70. Signals tab on the 'Lambda' Extended Faceplate
Item Description
Enable See Enable, Table 26 on page 86
Air Flow See AirFlow, Table 26 on page 86
Oxygen Flow See OxygenFlow, Table 26 on page 86
Gas Flow See GasFlow, Table 26 on page 86
Gas Energy See GasEnergy, Table 26 on page 86
Gas See GasCorrection, Table 26 on page 86
Correction
Oil Flow See OilFlow, Table 26 on page 86
Oil Energy See OilEnergy, Table 26 on page 86
Oil Correction See OilCorrection, Table 26 on page 86
Fuel Flow See FuelFlow, Table 26 on page 86
Fuel Energy See FuelEnergy, Table 26 on page 86
Fuel See FuelCorrection, Table 26 on page 86
Correction
3BSE079156-600 143
Table 71. Configuration tab on the 'Lambda' Extended Faceplate
Item Description
Limit Lambda H See LimitLambdaH, Table 28 on
page 89
Limit Lambda L See LimitLambdaL, Table 28 on
page 89
Time Lambda L See TimeLambdaL, Table 28 on
page 89
Limit Lambda LL See LimitLambdaLL, Table 28 on
page 89
Time Lambda LL See TimeLambdaLL, Table 28 on
page 89
Limit Lambda LLL See LimitLambdaLLL, Table 28 on
page 89
Predetermined Value See PredeterminedValue, Table 28
on page 89
144 3BSE079156-600
Table 72. Parameters tab on the 'Lambda' Extended Faceplate
Item Description
Fraction Sets the number of decimals to be displayed in
the Faceplate. Configurable from 0–6
Table 73. Errors tab on the 'Lambda' Extended Faceplate
Item Description
Lambda H See LambdaH, Table 29 on page 91
Lambda L See LambdaL, Table 29 on page 91
Lambda LL See LambdaLL, Table 29 on page 91
Lambda LLL See LambdaLLL, Table 29 on page
91
3BSE079156-600 145
Display Elements Section 6 Graphical User Interface
Table 74. Override tab on the 'Lambda' Extended Faceplate
Item Description
Alarm disabled See LambdaH, LambdaL,
LambdaLL, LambdaLLL Table 29 on
page 91
Display Elements
Table 75 on page 147 describes the Display Elements available for the 'Lambda'
object.
Table 75. Display Elements in the 'Lambda' Object

Appearance of the 'Lambda' Display Element icon when disabled.
Appearance of the 'Lambda' Display Element icon when enabled.
Lambda Display Element tag
146 3BSE079156-600
Section 6 Graphical User Interface RealIn2oo3
RealIn2oo3
'RealIn2oo3' object.
Faceplate
The 'RealIn2oo3' object offers a Reduced Faceplate, a Faceplate and an extended
Faceplate.
Reduced Faceplate
The 'RealIn2oo3' Reduced Faceplate displays the input values and the average of the
input values, see Table 76 on page 148. For information about control button
functionality see Table 39 on page 113.
Table 76. 'RealIn2oo3' Reduced Faceplate
Item Description
In1 See In1, Table 30 on page 93
Average See AverageInputValue, Table 31 on page 95
3BSE079156-600 147
Faceplate
The 'RealIn2oo3' Faceplate shows a graphical representation of the input values (IO
values are displayed), the highest and lowest input values and the average of the
input values, see Table 77 on page 149. For information about control button
Table 77. 'RealIn2oo3' Faceplate
Item Description
Highest See HighestInputValue, Table 31 on page 95
Lowest See LowestInputValue, Table 31 on page 95
Extended Faceplate
The 'RealIn2oo3' Extended Faceplate includes a number of tabs presented in the
148 3BSE079156-600
page 113.
Table 78. Control tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Highest See HighestInputValue, Table 31 on page 95
Lowest See LowestInputValue, Table 31 on page 95
Table 79. Control tab on the 'RealIn2oo3' Extended Faceplate
Item Description
IO In1 See In1, Table 30 on page 93
3BSE079156-600 149
Table 80. IN - Trim Curves tab on the 'RealIn2oo3' Extended Faceplate
Item Description
In1 Display In1.IOValue
Table 81. OUT - Trim Curves tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Highest Display Highest value (HighestInputValue) see
calculation in Functionality on page 97
Lowest Display Lowest value (LowestInputValue) see
Average Display Average value (AverageInputValue) see
150 3BSE079156-600
Table 82. Configuration tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Deviation Limit See DeviationLimit, Table 32 on page 96
Delay Time See DelayTime, Table 32 on page 96
Quality Configuration See QualityConfig, Table 32 on page 96
Predetermined Value See PredeterminedValue, Table 32 on
page 96
Table 83. Parameters tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Fraction Sets the number of decimals to be
displayed in the Faceplate. Configurable
from 0–6
Last Discrepancy Time Shows elapsed time when one or more
signals are deviating more than
DeviationLimit from each other
3BSE079156-600 151
Table 84. Errors tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Fault on one input signal See Fault1oo3, Table 34 on page 99
Fault on more than one See Error, Table 34 on page 99
input signal
Table 85. Override tab on the 'RealIn2oo3' Extended Faceplate
Item Description
Alarm disabled See Fault1oo3, Error Table 34 on
page 99
152 3BSE079156-600
Display Elements
Table 86 on page 154 describes the Display Elements available for the 'RealIn2oo3'
object.
Table 86. Display Elements in the 'RealIn2oo3' Object

'RealIn2oo3' Display Element icon
'RealIn2oo3' Display Element tag
ComplementIn
'ComplementIn' object.
Faceplate
The 'ComplementIn' object offers a Faceplate and an extended Faceplate.
Faceplate
The 'ComplementIn' Faceplate displays Output signal of the 'ComplementIn'
function block, see Table 87 on page 155. For information about control button
3BSE079156-600 153
Table 87. 'ComplementIn' Faceplate
Item Description
Out See Out, Table 36 on page 103
Extended Faceplate
The 'ComplementIn' Extended Faceplate includes a number of tabs presented in the
154 3BSE079156-600
page 113.
Table 88. IO Status tab on the 'ComplementIn' Extended Faceplate
Item Description
Table 89. Configuration tab on the 'ComplementIn' Extended Faceplate
Item Description
Discrepancy Time See DiscrepancyTime, Table 37 on
page 103
Quality Configuration See QualityConfig, Table 37 on page
103
Predetermined Value See PredeterminedValue, Table 37 on
page 103
3BSE079156-600 155
Table 90. Override tab on the 'ComplementIn' Extended Faceplate
Item Description
Alarm disabled See DiscrepancyError and Error
Table 38 on page 105
Table 91. Errors tab on the 'ComplementIn' Extended Faceplate
Item Description
Discrepancy Error See DiscrepancyError, Table 38 on page
105
IO Error See Error, Table 38 on page 105
156 3BSE079156-600
Display Elements
Table 92 on page 158 describes the Display Elements available for the
'ComplementIn' object.
Table 92. Display Elements in the 'ComplementIn' Object

Appearance of the 'ComplementIn' Display Element icon for Out value, false
Appearance of the 'ComplementIn' Display Element icon for Out value, true
'ComplementIn' Display Element Tag
3BSE079156-600 157
Display Elements Section 6 Graphical User Interface
158 3BSE079156-600
Section 7 Application Examples
Section 7 Application Examples
The examples presented in the following sections demonstrates use of the

'BurnerLib'. The main burner sequence is presented in Figure 8 on page 55, Table 10
on page 56, Figure 9 on page 57 and Table 11 on page 58.
The parameter StartCond needs to be active to initiate the start sequence. This
means that the burner management system shall handle the necessary prerequisites
(emergency stop, feedback of valves and other application specific things) for the
burner to start. After these are fulfilled, the burner management system shall send a
command to start the Burner (AutoStart). When this command is set, the Burner
will initiate its start sequence.
The I/Os for FlameGuard and FlameGuardPilot use the 'ComplementIn' object
which means that for each of the flame guards there are two signals that shall be
complimentary to each other. The ‘ComplementIn’ Out [Boolean] parameter from
the flame guards are then connected to the Burner object.
On the Burner object there is a parameter called SafeTempReached [Boolean] which
is used to control the safe temperature functionality when needed. This means that
the comparison (between the actual temperature and the set safe temperature) shall
be done before connecting this to the Burner object. When SafeTempReached is set
it overrides the flame guards.
The parameter PriorityCmdStop on the Burner object is used to force the Burner
object to a safe state, in this case to the state 900: Fault as described earlier. The
parameter PriorityCmdStop can be set when there is a ParError on any of the
objects/signals that are being used by the object Burner or emergency stop activated.
This is application specific.
Configuration of the Burner object is done via the parameter Config
[BurnerConfig]. This parameter contains all configuration settings that can be made
for the object.
As output on the Burner object there are some modes (Running, Starting,
OutOfServiceMode, etc.) and also some parameters (AtomizingValve,
CleaningValve, AirValve, etc.) that shall be connected to equipment in the field.
3BSE079156-600 159
Gas burner Section 7 Application Examples
Before connecting these Boolean command signals to I/Os, they need to be handled
in an appropriate way. This means that it is highly recommended to use an object
which can handle interlocks, feedback checks and also have a parameter that can be
set directly to I/Os.
The parameter StartCond is set in the examples below.
Gas burner
The burner only uses gas as fuel and direct ignition (Config.IgnitionType = 1). The
'TightnessTest' object is used to verify that there is no leakage before start-up. The
output TightnessTestPassed shall be used as one of the inputs that are connected to
StartCond. The example is illustrated in Figure 24 on page 160.
Ventilation
Fill Valve Vent Valve
Flame Guard Main
Gas Burner
Gas
Gas Valve 1 Gas Valve 2
Flame Guard Pilot

Igniter
Pilot
Pilot fuel valve
Figure 24. Gas burner application example
160 3BSE079156-600
Section 7 Application Examples Diagram
Diagram
This section presents the diagram code for the Gas Burner application Example. The
Diagram is structured into the following pages:
• Configuration, see Figure 25 on page 161
• Lambda Calculation and 'TightnessTest', see Figure 26 on page 162
• Burner, see Figure 27 on page 163
• Valves and Igniter, see Figure 28 on page 164
• Summary, see Figure 29 on page 165
This is the configuration page, All configurations of the function blocks are done on this page.
TightnessTestConfig:1 FurnaceTempConfig:4
TightnessTestConfig RealIn2oo3Config
5s ActTimeFillValve 2:TightnessTestConfig 100.0 DeviationLimit 3:FurnaceTempConfig
8s ActTimeVentValve 5s DelayTime
3m TestTime 0 QualityConfig
false EnablePartial 20.0 PredeterminedValue
LambdaConfig:2 FlameGuardMainConfigJoin_4:5
LambdaConfig ComplementInConfig
1.0 LimitLambdaH 2:LambdaConfig 3s DiscrepancyTime 3:FlameGuardMainConfig
0.95 LimitLambdaL 1 QualityConfig
10s TimeLambdaL false PredeterminedValue
0.85 LimitLambdaLL
3s TimeLambdaLL
FlameGuardPilotConfig:6
0.8 LimitLambdaLLL
ComplementInConfig
0.0 PredeterminedValue
3s DiscrepancyTime 3:FlameGuardPilotConfig
1 QualityConfig
BurnerConfig:3
false PredeterminedValue
BurnerConfig
3 IgnitionType 3:BurnerConfig
8s FirstSafetyTime
10s SecondSafetyTime
5s FillingTime
2s ReactionTime
10s PreIgnitionTime
5s CleaningTime
5s PilotFlameProvingTime
5s MainFlameProvingTime
4s DepressurizeTime
false EnableCleaning
false CheckFlameGuardsBeforeStart
5s BetweenReignitionTime
2 MaxIgnitionAttemptsStart
0 MaxIgnitionAttemptsRunning
2 MaxIgnitionAttemptsInterm
Figure 25. Configuration Diagram page
3BSE079156-600 161
Diagram Section 7 Application Examples
TightnessTest
Pressure limit for VPS PH, PL

SignalBasicInReal_1:7 gt:8
SignalBasicInReal gt TightnessTest:11
'P001' Name Out IN1 TightnessTest
IO.VPSPressure In Error 6.0 IN2 'TightnessTest' Name FillValve 4:OpenFuelValve1
PresssurePar InteractionPar PressureHigh VentValve 4:OpenVentValve
PressureLow Passed 3:TightnessTestPassed
and:9
StartCond UpstreamError 5:UpstreamError
and
PriorityCmdStop DownstreamError 5:DownstreamError
4:VentValveClosed IN1
BMSStartTightness AutoStart OutOfServiceMode 5:TightnessTestOutOfService
4:FuelValve1Closed IN2
BMSStopTightness AutoStop AEError 5:TightnessTestAEError
or:10 MainSetAuto SetAuto ParError 5:TightnessTestParError
or MainAckAll AEAckAll
IN1 1:TightnessTestConfig Config
4:VentValveObjectError IN2 TightnessTestPar InteractionPar
4:FuelValve1ObjError IN3
Lambda Calculaion
TOn_1:12
TOn
3:BurnerRunning In Q Lambda_1:17
10s PT Lambda
'L001' Name Lambda BMSLambdaValue
SignalBasicInReal_3:13 'LambdaBoiler1' Description LambdaError 5:LambdaError
SignalBasicInReal Enable AEError 3:LambdaError
'F002' Name Out AirFlow ParError 5:LambdaAEError
IO.AirFlow In Error OxygenFlow 5:LambdaParError
AirFlowPar InteractionPar GasFlow
11.2 GasEnergy
SignalBasicInReal_4:14
SignalError
SignalBasicInReal
1:LambdaConfig Config
'F003' Name Out
LambdaPar InteractionPar
IO.OxygenFlow In Error
OxygenFlowPar InteractionPar
SignalBasicInReal_2:15
SignalBasicInReal or:16
'F001' Name Out or
IO.FuelFlow In Error IN1
FuelFlowPar InteractionPar IN2
IN3
Figure 26. 'TightnessTest' and Lambda Calculation Diagram page
162 3BSE079156-600
Section 7 Application Examples Diagram
Burner IO input
FurnaceTemp:18
RealIn2oo3
'T123' Name AverageInputValue
IO.FurnaceTemp1 In1 Error
IO.FurnaceTemp2 In2 AEError 5:FurnaceTempAEError
IO.FurnaceTemp3 In3 ParError 5:FurnaceTempParError
MainReset Reset
1:FurnaceTempConfig Config
FurnaceTempPar InteractionPar
FlameGuardMain:20
ComplementIn
'FG001' Name Out
IO.FlameGuardMainActive In1 Error
IO.FlameGuardMainActiveC In2 AEError 5:FlameGuardMainAEError
MainReset Reset ParError 5:FlameGuardMainParError
1:FlameGuardMainConfig Config
FlameGuardMainPar InteractionPar
FlameGuardPilot:21
ComplementIn
'FG002' Name Out
IO.FlameGuardPilotActive In1 Error
IO.FlameGuardPilotActiveC In2 AEError 5:FlameGuardPilotAEError
MainReset Reset ParError 5:FlameGuardPilotParError
1:FlameGuardPilotConfig Config
FlameGuardPilotePar InteractionPar
Burner
SafetTemp
GasBurner:24
gt:19
Burner
gt
'BRN001' Name Igniter 4:StartIgniter
IN1
'GasBurner001' Description PilotValve 4:OpenPilotValve
750.0 IN2
SafeTempReached FuelValve1 4:OpenFuelValve1
FlameGuardMain FuelValve2 4:OpenFuelValve2
FlameGuardPilot Running 2:BurnerRunning
4:IgniterRunning IgniterInOperation OutOfServiceMode 5:BurnerOutOfService
Burner Start Condition 4:PilotValveClosed PilotValveClosed Error 5:BurnerError
and:22 4:FuelValve1Closed FuelValve1Closed AEError 5:BurnerAEError
and 4:FuelValve2Closed FuelValve2Closed ParError 5:BurnerParError
2:TightnessTestPassed IN1 StartCond
PurgingDone IN2 PriorityCmdStop
BMSStartBurner AutoStart
BMSStopBurner AutoStop
Priority command stop
MainSetAuto SetAuto
or:23
MainReset Reset
or
2:LambdaError 1:BurnerConfig Config
IN1
BurnerPar InteractionPar
IN2
IN3
IN4
4:IgniterObjError IN5
4:PilotValveObjectError IN6
EmergencyStop IN9
Figure 27. Burner Diagram page
3BSE079156-600 163
Diagram Section 7 Application Examples
Ventilation Valve
VentValve:25
SDValve
'V002' Name Out IO.OpenVentValve
'VentilationValve' Description ObjError 2:VentValveObjectError
3s FBTime EffectiveFBClose 5:VentValveObjectError
MainSetAuto SetAuto AEError 2:VentValveClosed
2:OpenVentValve AutoOpen ParError 5:VentValveAEError
AutoClose 5:VentValveParError
FBConfig4 FBConfig
IO.VentValveClosed FBOpen
IO.VentValveClosed FBClose
VentValvePar InteractionPar
Pilot valve
PilotValve:26
SDValve
'V007' Name Out IO.OpenPilotValve
'PilotValve' Description ObjError 3:PilotValveObjectError
3s FBTime EffectiveFBClose 5:PilotValveObjectError
MainSetAuto SetAuto AEError 3:PilotValveClosed
3:OpenPilotValve AutoOpen ParError 5:PilotValveAEError
AutoClose 5:PilotValveParError
FBConfig4 FBConfig
IO.PilotValveClosed FBOpen
IO.PilotValveClosed FBClose
PilotValvePar InteractionPar
Fuel valve 1
FuelValve1:28
SDValve
'V008' Name Out IO.OpenFuelValve1
Order to Fuel valve 1 'FuelValve1' Description ObjError 2:FuelValve1ObjError
sel:27 3s FBTime EffectiveFBClose 5:FuelValve1ObjError
sel MainSetAuto SetAuto AEError 3:FuelValve1ObjError
BMSStartTightness g AutoOpen ParError 2:FuelValve1Closed
3:OpenFuelValve1 in0 AutoClose 3:FuelValve1Closed
2:OpenFuelValve1 in1 FBConfig4 FBConfig 5:FuelValve1AEError
IO.FuelValve1Closed FBOpen 5:FuelValve1ParError
IO.FuelValve1Closed FBClose
FuelValve1Par InteractionPar
Fuel valve 2
FuelValve2:29
SDValve
'V009' Name Out IO.OpenFuelValve2
'FuelValve2' Description ObjError 5:FuelValve2ObjError
3s FBTime EffectiveFBClose 3:FuelValve2ObjError
MainSetAuto SetAuto AEError 3:FuelValve2Closed
3:OpenFuelValve2 AutoOpen ParError 5:FuelValve2AEError
AutoClose 5:FuelValve2ParError
FBConfig4 FBConfig
IO.FuelValve2Closed FBOpen
IO.FuelValve2Closed FBClose
FuelValve2Par InteractionPar
Igniter
Igniter:30
SDValve
'IG001' Name Out IO.StartIgniter
'Igniter' Description ObjError 5:IgniterObjError
3s FBTime EffectiveFBOpen 3:IgniterObjError
MainSetAuto SetAuto AEError 3:IgniterRunning
3:StartIgniter AutoOpen ParError 5:IgniterAEError
AutoClose 5:IgniterParError
FBConfig1 FBConfig
IO.IgniterRunning FBOpen
IO.IgniterRunningC FBClose
IgniterPar InteractionPar
Figure 28. Valves and Igniter Diagram page
164 3BSE079156-600
Section 7 Application Examples Structured Text
Summary Indications / Errors / Status
or:33
or:31 or
or 2:TightnessTestParError
2:TightnessTestAEError IN1 BMSParError
IN1 BMSAEError
2:LambdaParError IN2
2:LambdaAEError IN2
3:BurnerParError IN3
3:BurnerAEError IN3
4:VentValveParError IN4
4:VentValveAEError IN4
4:PilotValveParError IN5
4:PilotValveAEError IN5
4:FuelValve1ParError IN6
4:FuelValve1AEError IN6
4:FuelValve2ParError IN7
4:FuelValve2AEError IN7
4:IgniterParError IN8
4:IgniterAEError IN8
3:FurnaceTempParError IN9
3:FurnaceTempAEError IN9
3:FlameGuardMainParError IN10
3:FlameGuardMainAEError IN10
3:FlameGuardPilotParError IN11
3:FlameGuardPilotAEError IN11
or:32
or or:34
2:UpstreamError or
IN1 BMSObjError
2:TightnessTestOutOfService IN1 BMSOutOfService
2:DownstreamError IN2
3:BurnerOutOfService IN2
2:LambdaError IN3
3:BurnerError IN4
or:38
4:VentValveObjectError IN5
or
4:PilotValveObjectError IN6
BMSAEError IN1 BMSError
BMSParError IN2
BMSObjError IN3
4:IgniterObjError IN9
Reset of operator orders
move:35
move
0 IN1 MainSetAuto
move:36
move
0 IN1 MainReset
move:37
move
0 IN1 MainAckAll
Figure 29. Summary Diagram page
Structured Text
Below is the structured text code for the main sequence of the Gas Burner
application Example.
(************ This is the main sequence for the BMS *************)

(* It is this sequense that starts upp the burner by performing *)
(* all the nessecearly steps like Check Start conditions, *)
(* Purging, Tightnes test, Start Burner, stop burner *)
(****************************************************************)
(* Step 100 Idle *)
IF MainStep = 100 THEN
3BSE079156-600 165
Structured Text Section 7 Application Examples
IF MainStart AND NOT BMSError AND NOT BMSOutOfService THEN

MainSetAuto := True;
MainStart := False;
MainStep := 200;
END_IF;
BMSStartTightness := False;
BMSStopTightness := False;
BMSStartBurner := False;
BMSStopBurner := False;
MainStop := False;
MainStart := False;
END_IF;
(* Step 200 Tightness Test *)

IF TightnessTest.DownstreamError or TightnessTest.UpstreamError OR
MainReset THEN
MainStep := 100;
ELSIF NOT TightnessTest.Passed THEN
BMSStartTightness := True;
ELSIF TightnessTest.Passed THEN
BMSStartTightness := False;
MainStep := 300;
END_IF;
END_IF;
(* Step 300 Purging *)

(* Add code for start of purging *)
(* Add code for transition to next step when purging done *)
MainStep := 400;
END_IF;
(* Step 400 StartBurner *)

BMSStartBurner := True;
IF GasBurner.Running THEN
MainStart := False;
MainStep := 500;
ELSIF MainReset OR GasBurner.Error THEN
MainStep := 600;
BMSStartBurner := False;
END_IF;
END_IF;
166 3BSE079156-600
Section 7 Application Examples Oil Burner with Master and Slave
(* Step 500 Running *)

IF MainStop THEN
MainStop := false;
MainStep := 600;
ELSIF MainReset OR GasBurner.Error or not GasBurner.Running THEN
MainStep := 100;
END_IF;
END_IF;
(* Step 600 StopBurner *)

BMSStopBurner := True;
IF GasBurner.CleaningDone OR MainReset THEN
MainStep := 100;
END_IF;
END_IF;
Oil Burner with Master and Slave

The burner consists of a master- and a slave burner. It is only oil that is used as fuel
and the pilot is intermittent (Config.IgnitionType = 2) on the slave and interrupted
(Config.IgnitionType = 3) on the master. The slave burner shall start when Running
is active on the master burner. Cleaning can also be performed on the burners.
The FuelValve1 is common for both master and slave. The order to FuelValve1 shall
be connected with an OR operand from both master and slave. Since both
FuelValve1 and FuelValve2 are controlled at the same time in the Starting and Main
burner off in intermittent mode the signal FuelValve1Closed shall be connected to
the same signal as FuelValve2Closed on the slave burner.
3BSE079156-600 167
Oil Burner with Master and Slave Section 7 Application Examples
The example is illustrated in Figure 30 on page 168.
Pressurized air
AtomizingValve
Cleaning media
CleaningValve
Main flame guard
Main fuel
FuelValve 1 FuelValve 2
Air supply
AirValve Pilot flame guard
Oxygen supply
OxygenValve Igniter
Pilot fuel
Pilot fuel valve
Pressurized air
AtomizingValve
Cleaning media
CleaningValve
Main flame guard
FuelValve 2
Air supply
AirValve Pilot flame guard
Oxygen supply
OxygenValve Igniter
Pilot fuel
Pilot fuel valve
Figure 30. Oil burner with Master and Slave Application example
168 3BSE079156-600
Section 7 Application Examples Oil Burner with Master and Slave
The only difference is that when the slave burner is in state 300: Running it is
possible to set AutoStopMainBurner to close the fuel valves and
AutoStartMainBurner to open them again.
Before starting the Burner some prerequisites need to be fulfilled. They are
application dependent and among others the valves should be in a correct position
and emergency stop OK. All of the start conditions shall be connected to StartCond.
3BSE079156-600 169
Pilot Valve Requires Fuel Feed from the Main Supply Section 7 Application Examples
Pilot Valve Requires Fuel Feed from the Main Supply

In some cases the fuel system is configured in such a way that the fuel feed for the
pilot flame is between the two shutoff valves (FuelValve1 and FuelValve2) as in the
figure below (Gas Valve1 and Gas Valve2). Since the ‘Burner’ function block only
opens the two gas valves when the main flame is to be ignited the control and
supervision of the first shutoff valve (Gas Valve1) has to be taken care of outside the
‘Burner’ function block. The example is illustrated in Figure 31 on page 170.
Figure 31. PilotValve requires FuelValve1 to be opened
The burner block also supervises the valve position of the two valves during startup.
During the startup sequence the valve positions of the two valves are expected to be
closed up till the moment when the main flame is to be ignited. To handle this the
feedback signal from the second shutoff valve (Gas Valve 2) needs to be connected
to both FuelValve1Closed and FuelValve2Closed on the ‘Burner’ function block.
When the first shutoff valve (Gas Valve1) is handled outside the ‘Burner’ function
block all errors on the valve has to be connected to the StartCond and
PriorityCmdStop for the ‘Burner’ function block.
170 3BSE079156-600
Section 7 Application Examples TightnessTest with Three or More Fuel Valves in Series
TightnessTest with Three or More Fuel Valves in Series

In the case the valve proving system contains three or more fuel valves in series it
can be desirable to test all valves when doing the tightness test. An example is
shown in Figure 32 on page 171 where there are three valves in series. The
‘TightnessTest’ function block can still be used to handle this situation.
The example is illustrated in Figure 32 on page 171.
Figure 32. TightnessTest with two FuelValve2
It is then recommended to alternate which valve that is used for performing the
tightness test. The first time the tightness test is performed the FuelValve22 is
opened and kept open during the tightness test. This means that the tightness of
FuelValve21 is evaluated. The next time the tightness test is performed FuelValve21
is kept open and the tightness of FuelValve22 is evaluated.
The solution with alternating the valve to perform the test on has to be handled
outside the ‘TightnessTest’ function block. One way to achieve this is to have a
counter that keeps track of the number of performed tightness tests. Every time the
counter is an even number FuelValve21 shall be kept open during the test and when
the counter is an odd number FuelValve22 shall be kept opened.
The passive valve shall open at the same time as an open order is given to
FuelValve1 from the ‘TightnessTest’ function block. The reset order to close the
passive valve is given when the ‘TightnessTest’ function block returns the results
Passed, UpstreamError or DownstreamError or if PriorityCmdStop is given to the
TightnessTest.
3BSE079156-600 171
TightnessTest with Three or More Fuel Valves in Series Section 7 Application Examples
172 3BSE079156-600
Section 8 Debugging Program step
Section 8 Debugging
This manual along with tools provided by the graphical user interface allows the
user to debug the burner application.
Program step
Use the program step to analyze the cause of an error by identifying which step the
current sequence (refer to the sequence diagram for the corresponding sequence)
was in when an alarm occurs.
The program step graphs are presented on the Program Step tab on the extended
faceplates, see Extended Faceplate on page 120
Figure 33 shows a trim curve for the 'Burner' object when it goes from step 225 to
step 900: Fault.
Figure 33. Example of a trim curve
3BSE079156-600 173
Alarms Section 8 Debugging
Alarms
An alarm is generated when an error occurs. Refer to the Alarms and Errors chapter
in this manual for the corresponding function block to identify in which steps an
error can occur.
Troubleshooting
Table 93 on page 174 presents probable causes and solutions to the most common
problems that may occur.
Table 93. Troubleshooting
Problem Probable Cause Solution

'Burner' does not 'Burner' is in state 900: Fault. The Clear alarm conditions and reset the
start Fault state indicator (see Table 40 on 'Burner'
page 115) appears on the faceplate
Priority command stop Check Priority command stop and verify
(PriorityCmdStop) is active that the green indicator is not active on
the 'Burner' faceplate, see Table 49 on
page 127
Start condition (StartCond) is Check start conditions and verify that
missing the green indicator is active on the
'Burner' faceplate, see Table 49 on page
127
The 'Burner' is in out of service mode Verify that the 'Burner' can be started.
Set the 'Burner' in manual mode and
then in auto mode if required
ParError is active Verify that the parameters are within the
defined ranges
174 3BSE079156-600
Section 8 Debugging Troubleshooting

'Burner' stops An error has occurred and the Clear alarm conditions and reset the
during operation 'Burner' is in state 900: Fault. The 'Burner'
Fault state indicator (see Table 40 on
page 115) appears on the faceplate
(PriorityCmdStop) has been that the green indicator is not active on
activated the 'Burner' faceplate, see Table 49 on
page 127
'TightnessTest' 'TightnessTest' is in state 900: Fault. Clear alarm conditions and reset the
does not start The Fault state indicator (see 'TightnessTest'
Table 40 on page 115) appears on
the faceplate
(PriorityCmdStop) is active that the green indicator is not active on
the 'TightnessTest' faceplate, see
Start condition (StartCond) is Check start conditions and verify that
missing the green indicator is active on the
'TightnessTest' faceplate, see Table 61
on page 136
The 'TightnessTest' is in out of Verify that the 'TightnessTest' can be
service mode started. Set the 'TightnessTest' in
manual mode and then in auto mode if
required
ParError is active Verify that the parameters are within the
defined ranges
3BSE079156-600 175
Troubleshooting Section 8 Debugging

'TightnessTest' An error has occurred and the Clear alarm conditions and reset the
stops during 'TightnessTest' is in state 900: Fault. 'TightnessTest'
operation The Fault state indicator (see
Table 40 on page 115) appears on
the faceplate
(PriorityCmdStop) has been that the green indicator is not active on
activated the 'TightnessTest' faceplate, see
176 3BSE079156-600
Section 9 Support ABB Website
Section 9 Support
ABB provides a number of different ways of web-based self-service support.
ABB Website
For information on ABB in Safety and the Independent High Integrity offering, visit
www.abb.com/highintegritysafety.
ABB SolutionsBank
ABB SolutionsBank (solutionsbank.abb.com) is a global Internet portal to customer
support and knowledge management, that enables customers to quickly locate
manuals, documents, field reports, troubleshooting guides and software updates
specific to ABB products and systems.
Control Systems Application and Knowledge Store

Control Systems Application and Knowledge Store
(www.abb.com/knowledgestore) is a community-driven question-and-answer
(Q&A) site that allows users to submit questions to be answered as well as answer
questions asked by other users. The system supports adding attachments to both
questions and answers, to help facilitate effective communication. There is also an
app feature where members can share their knowledge artifact that can help
members use ABB control systems and jump-start projects. The site also gives users
the chance to earn points as a way to encourage participation.
3BSE079156-600 177
Control Systems Application and Knowledge Store Section 9 Support
178 3BSE079156-600
Index
A EN 12952-9 21, 70
AKS 177 EN 12953-7 21, 70
Alarms and Errors EN 13611 21 to 22
Burner 67
ComplementIn 105
EN 1643 21 to 22, 84
EN 267 21, 107
Index
Lambda 91 EN 298 21 to 22, 71
RealIn2oo3 98 EN 50156-1 20
TightnessTest 83 EN 676 21 to 22
EN 746-2 21, 70
B
Black box 28 F
BMS 25 Faceplate
BPCS 28 Burner 121
Burner 39 ComplementIn 155
Burner Library 33 Lambda 141
RealIn2oo3 148
C TightnessTest 134
Combined Safety 30 First Safety Time 47
ComplementIn 100 to 101 Fuel dispenser 28
Configuration Function Block
Burner 47 Burner 39
ComplementIn 103 ComplementIn 101
Lambda 89 Lambda 85
RealIn2oo3 96 RealIn2oo3 93
TightnessTest 75 TightnessTest 72
Continuous demand 25 Functionality
Burner 49
ComplementIn 104
D
Lambda 90
Danish Gas Technology Centre A/S 22
RealIn2oo3 97
DGC 22
TightnessTest 76
Display Elements
Burner 133
ComplementIn 158 G
Lambda 147 GAD 22
RealIn2oo3 154 Gas Appliance Directive 22
TightnessTest 139
I
E IEC 61508 20, 22, 30 to 31
EN 12952-8 21, 70 IEC 61511 20
IEC 62061 20
3BSE079156-600 179
Index
Instrumentation 30
ISO 13849-1 20
L
Lambda 85
Low demand 25
N
Notified Body under GAD 22
P
Parameters
Burner 42
ComplementIn 102
Lambda 86
RealIn2oo3 93
TightnessTest 73
R
RealIn2oo3 93
Recommended use
Burner 70
ComplementIn 105
Lambda 92
RealIn2oo3 100
TightnessTest 84
S
Safety Summary 5
Second Safety Time 47
SIS 28
SolutionsBank 177
T
TightnessTest 72
180 3BSE079156-600
Introduction
Revision History
Introduction
This section provides information on the revision history of this User Manual.
The revision index of this User Manual is not related to the 800xA 6.0 System
Revision.
Revision History
The following table lists the revision history of this User Manual.
Revision
Description Date
Index
- First edition published for 800xA 6.0. April 2016
Library version 1.1.
Major changes compared with the -510 edition
and library version 1.0 are:
• Added information on the Gas Appliance
Directive.
• New 'Running' output on 'TightnessTest' that
indicates if a tightness test is in progress.
• Improved alarm handling in 'RealIn2oo3'.
3BSE079156-600 181
Revision History
182 3BSE079156-600
Contact us
Copyright© 2014-2016 ABB.
3BSE079156-600
www.abb.com/800xA
www.abb.com/controlsystems All rights reserved.
www.abb.com/highintegritysafety
Power and productivity

for a better worldTM

3BSE079156-600 AC 800M 6.0 Burner Library Safety and User Manual PDF

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

3BSE079156-600 AC 800M 6.0 Burner Library Safety and User Manual PDF

Uploaded by

Copyright:

Available Formats

AC 800M

Power and productivity

System Version 6.0

Copyright © 2014-2016 by ABB.

Release: April 2016

Electrostatic Sensitive Device

GENERAL Equipment Environment

Electrical Shock Hazard During Maintenance

SPECIFIC Warnings related to About This User Manual on page 17

SPECIFIC Warnings related to System and Software Requirements on page 31

It is assumed that the application software is subject to safety analysis to

Never use AC 800M High Integrity software- or hardware components,

SPECIFIC Warnings related to Recommended use on page 70

If the lock-out function is used it shall be checked for proper operation

The application shall implement the shutdown of a burner in accordance

SPECIFIC Warnings related to Recommended use on page 70

During online download (normal application update or Load Evaluate Go),

The parameter Config.CheckFlameGuardsBeforeStart needs to be set to

It is not allowed to connect the same flame guard to the parameters

SPECIFIC Warnings related to Recommended use on page 84

Set the parameter Config.TestTime to the leakage testing time as

The response time to achieve safety shutdown, whenever this is required,

It is the responsibility of the application engineer and implementation of

The application shall implement diagnostics of the pressure switches. on

It is the responsibility of the application engineer to define the amount of

SPECIFIC Warnings related to Recommended use on page 92

To enable the supervision and the calculation it is necessary to set the

Warnings related to Recommended use on page 100

The setting of both the Config.DeviationLimit and the Config.DelayTime

Warnings related to Recommended use on page 105

The Config.DiscrepancyTime shall be taken into account for the Fault

SPECIFIC Warnings related to Safety precautions on page 107

The application shall implement functionality in accordance with EN 267:

As far as practicable the application design shall minimize the

SPECIFIC Warnings related to Safety precautions on page 107

It is the users responsibility to check the ParError outputs of each function

The configuration parameters of all function blocks shall be confirmed

Safety Summary ................................................................................................................5

About This User Manual

Section 1 - Burner Management Introduction

Section 2 - System and Software Requirements

Section 3 - Library Overview

Section 4 - Function Block Types

Section 5 - Create Safety Logic

Section 6 - Graphical User Interface

Section 7 - Application Examples

About This User Manual

Before running SIL certified applications in a High Integrity controller, refer to

User Manual Conventions

Warning, Caution, Information, and Tip Icons

General Safety Standards

Application Standards (to the extent applicable)

Gas Appliance Directive (GAD)

Figure 1. AC 800M Burner Management Library DGC Certificate

Category Title Description

Category Title Description

CBS Annex, 3BSE079245 CBS Certificate

Software System 800xA Control AC 800M, Getting Started

Section 1 Burner Management Introduction

A Burner Management System (BMS) is designed to prevent boiler explosions, and

Burner Management Systems Defined

Using AC 800M High Integrity as a BMS

Figure 2. AC 800M High Integrity Burner Management System