ABB - KKS - Design Description - Advant Control - Design Rules - Rev 6 - 2006

We reserve all rights in this document and in the information contained therein.
Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
Copyright 2006 ABB

Type des. Part no.
Prep. PSPE / Rainer Ott 2006-06-01 Doc. kind Design Description
No. of p.
Appr. / see signature page Approved
Resp. dept PSPE
Title Advant Control Design Rules
94
Doc. no. Lang. Rev. ind. Page

ABB Switzerland Ltd 1AHL 102 709 en 6 1
FILE: 1AHL102709r6_DesignRules_Rev6.doc; TEMPLATE: Techn_Doc_Stand_P.dot A; SKELETON: ; SAVEDATE: 2006-06-02 11:42

ADVANT CONTROL

DESIGN RULES
Revision 6



CONTENTS
1. Revision Index and Signatures .................................................................................6
2. General Description ...................................................................................................7
2.1 Control system hardware configuration (Typical) ...........................................7
2.2 Control system overview................................................................................7
2.3 Abbreviations used:........................................................................................7
3. Design Principles .......................................................................................................8
3.1 Engineering units (European).........................................................................8
3.2 Implemented APC software functions/options................................................8
3.3 Process Sectioning on HSI (Typical)..............................................................9
3.4 Alarming and Event Handling.......................................................................10
3.4.1 Alarm & Event Categories ..............................................................10
3.4.2 Concept for setting Limits of Analogue signals AC450...................10
3.4.3 PIDCONA Controller Alarming AC450...........................................10
3.4.4 Event handling of I/O-Signal and PC generated Alarms AC450 ....11
3.4.5 Standard APC EVENT elements. (Nrs: 101 200) ......................11
3.4.6 Standard Project specific Event Element .......................................12
3.5 KKS Naming of Signals ( Signal Codes) ......................................................13
3.5.1 For Analogue Hardware Inputs/Outputs, Conditioned &
Calculated Signals..........................................................................13
3.5.2 For Limit Values (derived from Analogue values) and direct
Binary inputs...................................................................................14
3.5.3 For Drive / Function Group Feedbacks / Commands.....................15
3.5.4 From/To Pushbuttons, Lamps and Indicators (Hardwired).............15
3.5.5 For a signal generated within Advant.............................................16
3.5.6 Function Group, Selector & Sequencer..........................................16
3.6 AC450 Node to Node Communication.........................................................17
3.6.1 Analogue Signals transferred between nodes................................17
3.6.2 Binary signals transferred between nodes .....................................18
3.6.3 DS Node to Node Communication: ................................................18
3.6.4 DAT for DS (AC450).......................................................................19
3.6.5 Analogue and Binary signals transferred between PC
programs (AC450)..........................................................................19
3.7 DSP Data Transfer between AC160 and AC450..........................................20
3.7.1 Signals Transferred from AC160 to AC450....................................20
3.7.2 DSPs for Process signals...............................................................20
3.7.3 AC160 Station Numbering..............................................................21
3.7.4 Typical Definition of DSPs .............................................................21
3.7.5 DSPs used in Broadcast mode: ...................................................24
3.7.6 EVS Data transfer between AC160 stations and AC450................24
3.7.7 MDATs (AC160) .............................................................................24
3.7.8 High Speed Link: HSL (AC160)......................................................25
3.8 FCB and OLB: ..............................................................................................26
3.8.1 FCB page layout setup...................................................................26
3.8.2 OLB page layout setup...................................................................26
3.8.3 TPX (Header) file and Required Information..................................26
4. Basic Configuration of DCS ....................................................................................27
4.1 AC450 PC Program Structure......................................................................27
4.2 PC-Program-numbering...............................................................................28
4.3 Correction Functions (AC450)......................................................................29
4.4 Typical PC structure.....................................................................................30


4.5 APC-Element Settings..................................................................................31
4.5.1 PIDCONA PID Control Function.....................................................31
4.5.2 CV with fault indication...................................................................32
4.5.3 SOV/MOV with fault indication.......................................................33
4.5.4 Unidirectional Drive ........................................................................34
4.5.5 Simple Logic (e.g. FlipFlop )...........................................................35
4.6 Database Element Configuration..................................................................36
4.6.1 AF100 scantime settings for S800..................................................36
4.6.2 Analogue Output Module (e.g. AO810, ).....................................36
4.6.3 Analogue Outputs AOS (e.g. AOS810, ).....................................36
4.6.4 Analogue Input Module (e.g. AI810, AI830, )..............................37
4.6.5 Analogue Inputs AIS (e.g. AIS810):................................................37
4.6.6 Binary Input Module (e.g. DI830, )..............................................38
4.6.7 Binary Inputs DIS (e.g. DIS830, )................................................38
4.6.8 Binary Output Module (e.g. DO815, DO810,..)...............................38
4.6.9 Binary Outputs DOS (e.g. DOS815, DOS810, ) ........................39
4.6.10 S800 I-O-Station (e.g. CI820).........................................................39
4.6.11 S600 Communication Cards for AF100 (e.g. CI610, CI631) ..........39
4.6.12 Speed Measurement DPS640........................................................39
4.6.13 Analogue Input Calculated (AIC on AC450):..................................40
4.6.14 Digital Input Calculated (DIC on AC450):.......................................40
4.6.15 Analogue Output Calculated (AOC): ..............................................40
4.6.16 Digital Output Calculated (DOC): ...................................................40
4.7 AC450 Hard- and Software Limits................................................................41
4.7.1 S800-Stations.................................................................................41
4.7.2 Signals............................................................................................41
4.7.3 DB Objects .....................................................................................41
4.7.4 TTD Logs........................................................................................41
4.8 AC160 Hard- and Software Limits................................................................42
4.8.1 Cards & Racks................................................................................42
4.8.2 Signals............................................................................................42
4.8.3 DB objects ......................................................................................42
4.8.4 PC elements...................................................................................42
5. Hardware Supervision .............................................................................................43
5.1 Transmitter and Wire-break Supervision in AC450......................................43
5.2 Analogue Signal Transfer Between Nodes (AC160,AC450) ........................44
5.3 Transmitter and Wire-break Supervision in AC160......................................44
5.3.1 Wire-break Supervision for S600 (e.g. AI625)................................44
5.3.2 Wire-break Supervision for S800 (e.g. AI810, AI830, AI835).........44
5.4 Multiple measured Analogue process variables (Drift alarm).......................45
5.5 Error-Handling of signals used for Protection...............................................45
6. Tips and Tricks for AC450 planning .......................................................................46
6.1 MANSTN......................................................................................................46
6.2 PIDCONA.....................................................................................................46
6.3 Event and Alarm List - system time-sync errors...........................................47
6.4 REG-G & FUNG-1V......................................................................................47
6.5 Using TCs.....................................................................................................47
6.6 Deleting Database elements On-Line...........................................................47
6.7 TTDLogs & TTDVars and Renumbering Database Elements......................48
6.8 PC program Names:.....................................................................................48
6.9 Setpoints Common to multiple PC programs ...............................................48
6.10 Hardware Dimensioning...............................................................................49
7. Tips and Tricks for AC160 planning .......................................................................50
7.1 REG-G-UT....................................................................................................50
7.2 I/O Cards used by multiple CPUs in the same station..................................50


7.3 MOVE-RED..................................................................................................50
7.4 Integrator......................................................................................................50
7.5 CONTRM cycle time: On-Line changes .......................................................50
7.6 Deleting Type Circuits ..................................................................................50
7.7 Changing DSP parameters on-line...............................................................50
7.8 SYSDIAG (System Diagnosis) .....................................................................51
7.9 Missing values during debugging (x)..........................................................51
7.10 Calculation of SPDGRD (for RSM)...............................................................51
7.11 DIC Scantime...............................................................................................51
7.12 Usage of ERR Terminal of DB-Element DI651X..........................................52
7.13 Checks required after Generate Target Code..............................................52
8. Tips & Tricks: General .............................................................................................53
8.1 SI-ANSI Conversion parameters ..................................................................53
8.2 Source Code Naming convention.................................................................54
8.3 Time Synchronisation...................................................................................55
8.3.1 AC450 Systems and AC450/AC160 Systems................................55
8.3.2 AC160 Systems..............................................................................55
8.4 Swapping PC Elements................................................................................56
8.5 Editing TIX files.............................................................................................56
8.6 Modbus communiction Error signal handling................................................56
8.7 Profibus setup for FCB.................................................................................56
9. Attachments..............................................................................................................57
9.1 Attachment 1: Analogue Signal Error Handling AC450 to AC160................58
9.2 Attachment 2: Analogue Signal Error Handling AC160 to AC450................59
9.3 Attachment 3: Communication Routes between AC160 Nodes...................60
9.4 Attachment 4: AC450 Node to Node Interface (Typical)..............................61
9.5 Attachment 5: AC450 Node to Node DS naming convention.......................62
9.6 Attachment 6: AC450 Node to Node Analogue Signal Error Handling.........63
9.7 Attachment 7: AC450 Transmitter and Wire-Break Supervision..................64
9.8 Attachment 8: AC160 MECO for S600.........................................................65
9.9 Attachment 9: AC160 MECO for AI810........................................................66
9.10 Attachment 10: AC160 MECO for AI830......................................................67
9.11 Attachment 11: AC160 MECO for AI835......................................................68
9.12 Attachment 12: Analogue Limits for Hardware I/Os in AC450......................69
9.13 Attachment 13: 2oo3 Analogue signal and alarm handling..........................70
9.14 Attachment 14: 2oo3 TRIP Signal Handling FC2 (AC450)...........................71
9.15 Attachment 15: 2oo3 TRIP Signal Handling (Signal from AC160, Logic
in AC450)......................................................................................................72
9.16 Attachment 16: 1oo2 TRIP Signal Handling (AC450)...................................73
9.17 Attachment 17: 1oo1TRIP Alarms and Events (AC160)...............................74
9.18 Attachment 18: 1oo2 PLS/PLST/TRIP Signal Handling (AC160).................75
9.19 Attachment 19: 1oo2 ST-TRIP with relation to CLC (AC160).......................76
9.20 Attachment 20: 2oo3 PLS/PLST/TRIP Alarms (AC160)...............................77
9.21 Attachment 21: 2oo3 TRIP Signal Handling (Hardwired between
AC160's).......................................................................................................78
9.22 Attachment 22: Signal Redundancy Guidelines part 1.................................79
9.23 Attachment 23: Signal Redundancy Guidelines part 2.................................80
9.24 Attachment 24: Controller Release Logic.....................................................81
9.25 Attachment 25: Controller Interlocks & Indication.........................................82
9.26 Attachment 26: Manual Station as SetPoint Station.....................................83
9.27 Attachment 27: Controller Direct / Reverse Action & Fail-Safe....................84
9.28 Attachment 28: Controller Limitation............................................................85
9.29 Attachment 29: System Diagnosis AC160 Alarms/Events...........................86
9.30 Attachment 30: MVI settings for standard Modbus configuration.................87
9.31 Attachment 31: MS settings for standard Modbus configuration
(Vibration Monitor)........................................................................................88


9.32 Attachment 32: MS settings for standard Modbus configuration
(SSD/AVR)...................................................................................................89
9.33 Attachment 33: MS settings for standard Modbus configuration (DCS).......90
9.34 Attachment 34: Modbus PC-Program settings (Line, Network)....................91
9.35 Attachment 35: Modbus PC-Program settings (Registers)...........................92
9.36 Attachment 36: Modbus PC-Program settings (flow control)........................93
9.37 Attachment 37: CI513 DIP-Switch settings for MB300.................................94


1. Revision Index and Signatures
Rev.
ind.
Page (P)
Chapt. (C)
Description Date Dept./Init.
0
First issue for use by KWGLA3 for AL-Hidd (based on internal
API Design Guide)
98-03-30
KWGLA3-S.Waller
KWGLA3-A.J enney
1
All Revised for use by all KWGLA groups 98-06-23
KWGLA3-A.J enney
KWGLA3-S.Waller
2
Most Intermediate Revision 98-11-01
KWGLA3-S.Waller
KWGLA2-P.Schori
3
All General Revision:
Corrections, additions and improvements.
GENUSD parameters removed, Attachments added.
99-06-10
NPE2-S.Waller
NPE2 A.J enney
NPE2 D.Looser
NPE1-P.Schori
NPE1J .C.Rey
NPE1-D.Lnd
4
All Major changes in all sections including:
General Corrections and new comments included
Expanded signal extension definitions
Event & Alarm Table changes
Changes to Alarm/Eventing principles
Signal Redundancy definitions
Additional controller related Attachments
00-11-20
Inputs from:
NPA: various
NPE: various
NPS: various
5
Most Various additions and corrections
High-burnout supervision of analogue transmitters added
Redundant signal processing requirements added.
Revised analogue signal limits alarm/event concept for AC450

03-07-18 Inputs
from:
PTUPA1: S.Waller
PTUPA1:M.Layes
PTUPA2: A.J enney
PTUPE: R.Blumer
PTUPE1: J .C.Rey
PTUPE1: R.Egloff
PTUPE2: T.Benz
PTUPE3: P.Schori
PTUPE3: M.Schmitt
6
all Various additions and corrections
Layout corrected
MECO S800 added
DB settings for S800 added
Timesync settings added
System Diagnosis DB-Elements added
PC Program numbering simplified
Modbus settings added
2006-05-31
PSPE: R.Ott
PSPE: S.Wolf
PSPE: Venkat
PSPE: M.Calva
PSPE: I.Loete
PSPE: J .C.Rey


2. General Description
2.1 Control system hardware configuration (Typical)
UNIT 1:
Service Equipment Node Nr
CCPP (example)
Node Nr.
ICS / OK
GT 11 AC450+AC160 u1 15
GT 12 AC450+AC160 u2
GT 13 AC450+AC160 u3
HRSG 11 AC450 u4
HRSG 12 AC450 u5
HRSG 13 AC450 u6
WSC AC450 u7 16
ST 18 AC450+AC160 u8 17
BOP & ELECTRICAL AC450 u9 18
Where: u =Unit Nr (e.g.: 1, 2 etc.)
HIS:
Connectivity Server CS1 RTA CS001 51

Engineering Station 1 RTA ES001 61
Where: n =Nr of Units +1
Refer to Project specific specifications to Design Rules for details.
2.2 Control system overview
Refer to: Project specific control system overview drawing.
2.3 Abbreviations used:
HSI Human System Interface
OS Operator Station
ES Engineering Station
IMS Information Management Station (PRIMA, PGIM)
GT Gas Turbine
ST Steam Turbine
HRSG Heat Recovery Steam Generator
WSC Water Steam Cycle
BOP Balance of Plant
CLC Closed Loop Control
OLC Open Loop Control
P1..P3 Protection 1 through 3



3. Design Principles
3.1 Engineering units (European)
Unit Remark Unit Remark
A Ampere mbar Gauge or differential press.
bar Gauge or diff. press. mbara Absolute pressure
bara Absolute pressure mg/kg
cm mg/m3
degC C min
GJ /h mm
h hour mmHg Level/Press. (Mercury Column)
Hz mmWC Level/Press. (Water Column)
J J oule Mpa
K Kelvin MVAr
kA MW
kcal MW/min
kg MWh
kg/h ohm W
kg/m3 pa pascal
kg/s pH
kJ ppb parts per billion
kJ /s ppm parts per million
kpa rpm
kV s second
kW S Siemens
l Litre t/h
l/s ug/kg
m um meter
m/s um pp meter peak to peak
m/s2 uS Siemens
m2 uS/cm Siemens/centimetre
m3 V
m3/h W
m3/s

3.2 Implemented APC software functions/options
PC elements for various objects
Extended functions for sequencers
Extended EVENT handling
APC Parameter displays
Display link
Runtime
Number of starts
Drive current


3.3 Process Sectioning on HSI (Typical)
Section
Nr
Area
(Multishaft plants)
Area
(ICS plants)
Area
(OK plants)
0 BOP common
1 GT1 +HRSG1 unit 1 Unit 1 GT
2 GT2 +HRSG2 unit 1 Unit 2 HRSG
3 GT3 +HRSG3 unit 1 Unit 3 WSC
4 WSC +ST unit 1 Unit 4 ST
5 BOP +EL unit 1 Unit 5 BOP
6 GT1 +HRSG1 unit 2 Unit 6 EL
7 GT2 +HRSG2 unit 2 Unit 7
8 GT3 +HRSG3 unit 2 Unit 8
9 WSC +ST unit 2 HV Switchyard, BOP
10 BOP +EL unit 3
11 GT1 +HRSG1 unit 3
14 WSC +ST unit 3
15 BOP +EL unit 3
16

A maximum of 18 Process sections can be defined, access to 16 of these (1..16) can be configured
via the OS.
If the process Section is set to 0 (Zero) it is accessible from ALL other sections (often used for
common systems).
If the process Section is set to -1 (minus 1) it is hidden from ALL operator stations (could be used
for node to node database elements or setpoint elements (eg: AOCs) which are then only
adjustable from Engineering station.
Refer to Project specific specifications to Design Rules for details.


3.4 Alarming and Event Handling
3.4.1 Alarm & Event Categories
There are 2 different types of alarm and events:
System Alarm/Events
System alarms include internal supervision of I/O, peripheral devices and database elements.
In general all database elements are supervised (error treatment).
For most db-elements the value for ERR_TR should be set to 2 (default is 0), this initialises event
reporting and alarm handling in the Operator Station for signal errors and operator commands.
Process Alarm/Events
In addition to drive feedback signals to DCS, All output orders from the DCS are shown in the event
list.
To reduce the number of events and alarms (Operator Overload) the following rules will be
followed:
Events and alarms will ONLY be generated at source.
For drive feedbacks, ON/OFF (or OPEN/CLOSE), and for motor/breaker feedbacks TEST,
the eventing is achieved using the DIC/DIS database Elements VALUE_TR(eatment)
property Refer to table on following pages.
The standard functionality of the APC PC/DB elements will create events for the remaining
feedbacks and orders (such as Torque, Local, Disturbed etc.).
Where APC PC/DB elements are not used, events for all signals must be generated by
using DIS and DIC database elements.
3.4.2 Concept for setting Limits of Analogue signals AC450
A basic design concept is that all analogue derived alarms are shown as a colour change on the
appropriate Object Display. This is achieved by setting the following AIC database parameters:
EN_L1=1 for Low alarm limit indication arrow to appear in analogue displays
EN_L2=1 for Low-Low alarm (or trip) limit indication arrow in analogue displays
EN_H1=1 for High alarm limit indication arrow to appear in analogue displays
EN_H2=1 for High-High alarm (or trip) limit indication arrow in analogue displays
LIM_1_TR=0 if no events are required, otherwise select an analogue specific value treatment
eg: 201
LIM_2_TR=0 if no events are required, otherwise select an analogue specific value treatment
eg: 202
Note that this colour change should only be used for Alarms and pre-alarms where the operator
attention is required ( i.e. where an alarm is shown in the Settings list, PFuP, I/O-List etc.).
Note: A setting of 0 for LIM1_TR or LIM_2_TR causes the analogue display to change to RED
(without flashing) irrespective of the required alarm Priority. All switch points, alarms and trip
settings are generated using COMParators writing to DICs and these DICs are given the correct
priority and colour via the VALue_TReatment setting.
For Hardware inputs, the COMParators and Limit settings can be defined in the same PC programs
(1 through 4) used for the input signal at CONTRM Nr 33 or higher or in PC 7 through 9 (preferred
method as PC1 can get too large to load into the controller) .
Also refer to Section 5 Hardware Supervision and Attachment 12: Analogue Limits for Hardware
I/Os in AC450 for an example of a PC program for generating analogue limits.
3.4.3 PIDCONA Controller Alarming AC450
Deviation alarms (SP-PV) are internally generated within the PIDCONA and the alarm limit is set in
the dBase element.


Only deviation alarms or internal faults are shown by a colour change in the PID Object Display.
3.4.4 Event handling of I/O-Signal and PC generated Alarms AC450
There are two priorities for alarm signals and one for events:
Note that the numbers refer to the required settings in the Alarm and Event list on following pages
Priority 2 High Priority:
These are displayed in red in the operator station alarm
and event list.
- Signals as pre-warning prior to trip
- Signals that have caused a trip
- Tripped status of main equipment / sub-systems.
Priority 3 Low Priority:
These are displayed in yellow in the operator station
alarm and event list.
- All remaining process alarm signals
Priority 4 Events:
These are displayed in green in the operator station
event lists.
- All status signals (ON, OPEN, ENGAGED etc.)
Signal
alarms
System generated
These are displayed in red in the Operator station alarm
and event list.
- Signal errors/POS Ind error, etc

3.4.5 Standard APC EVENT elements. (Nrs: 101 200)
For a description of the EVENT element with number 101-200 see APC FUNCTIONAL
DESCRIPTION


3.4.6 Standard Project specific Event Element
Alarms Events
Event AUDIB AL_ Property Status Status Event AUDIB AL_ Property Status Status
Nr. PRIO Text Acti ve not Acti ve Nr. PRIO Text Acti ve not Acti ve
201 1 2 >MAX1 AlarmEVTE1 NormalEVTE3 240 0 4 CLOSED
<MIN1 AlarmEVTE2 NormalEVTE4 241 0 4 LOCAL
202 1 2 >MAX2 AlarmEVTE1 NormalEVTE3 242 0 4 OFF
<MIN2 AlarmEVTE2 NormalEVTE4 243 0 4 ON
203 2 3 <MIN1 Alarm Normal 244 0 4 OPEN
204 2 3 <MIN2 Alarm Normal 245 0 4 NOT TRIP
205 1 2 <MIN1 Alarm Normal 246 0 4 AUTO
206 1 2 <MIN2 Alarm Normal 247 0 4 MANUAL
207 1 2 <MIN3 Alarm Normal 248 0 4 STOP
208 1 2 <MIN4 Alarm Normal 249 0 4 ACTIVE
209 1 2 >MAX1 Alarm Normal 250 0 4 REMOTE
210 1 2 >MAX2 Alarm Normal 251 0 4 DSENGA
211 1 2 >MAX3 Alarm Normal 252 0 4 STANDSTILL
212 1 2 >MAX4 Alarm Normal 253 0 4 ACK
213 1 2 TRIP Alarm Normal 254 0 4 INTMD
214 2 3 BDQ Alarm Normal 255 0 4 LOWER
215 2 3 SEN UNEQ Alarm Normal 256 0 4 REACHED
216 2 3 DIST Alarm Normal 257 0 4 OPR POS
217 2 3 TORQUE Alarm Normal 258 0 4 RAISE
218 2 3 NOT OK Alarm Normal 259 0 4 READY
219 2 3 FAILURE Alarm Normal 260 0 4 RELEASE
220 2 3 <MIN3 Alarm Normal 261 0 4 NOT READY
221 2 3 ACTIVE Alarm Normal 262 0 4 SELECTED
222 2 3 <MAX1 Alarm Normal 263 0 4 SUCSFUL
223 2 3 >MIN1 Alarm Normal 264 0 4 DETECTED
224 2 3 BLOCKED Alarm Normal 265 0 4 TEST
225 2 3 CH DIFF Alarm Normal 266 0 4 ENGAGED
226 2 3 TEST Alarm Normal 267 0 4 <MIN5
227 2 3 ALARM Alarm Normal 268 0 4 <MIN1
228 2 3 >MAX1 Alarm Normal 269 0 4 <MIN2
231 2 3 >MAX3 Alarm Normal 272 0 4 >MAX1
232 1 2 <MIN5 Alarm Normal 273 0 4 >MAX2
233 2 3 DRIFT Alarm Normal 274 0 4 >MAX3
234 1 2 FAILURE Alarm Normal 275 0 4 >MAX4
235 2 3 EXCEEDED Alarm Normal 276 0 4 >MAX5
236 1 2 ACTIVE Alarm Normal 277 0 4 >MIN1
237 2 3 N ACTIVE Alarm Normal 278 0 4 >MIN2
238 1 2 DIST Alarm Normal 279 0 4 >MIN3
239 2 3 TRIP Alarm Normal 280 0 4 >MIN4
281 0 4 <MAX1
282 0 4 <MAX2
283 0 4 <MAX3
284 0 4 <MAX4
285 0 4 LOADED
286 0 4 PREPARED
287 0 4 OK
288 2 3 NOT ON Alarm Normal
289 2 3 NOT READY Alarm Normal
290 2 3 NOT OPEN Alarm Normal
291 0 4 (spare)
292 0 4 (spare)
293 0 4 (spare)
294 0 4 (spare)
295 0 4 (spare)
296 0 4 (spare)
297 0 4 (spare)
298 0 4 (spare)
299 0 4 (spare)
Notes:
1) AL_PRIO=2: Red Alarm, AL_PRIO=3 Yellow Alarm, AL_PRIO=4 Event
2) Event Nrs: 291 ... 299 are free for definition as required on a per project basis as either Events or
Alarms.
3) Refer to Project specific specifications to Design Rules for details.



3.5 KKS Naming of Signals ( Signal Codes)
ALL non-communication database elements must be given a KKS Nr (do not use a Clear Text
name).
When not otherwise stated signal codes may be used for external (hardware I/O) or for internal
signals
In this section: n is numeric 0...9.
c is character A...Z
3.5.1 For Analogue Hardware Inputs/Outputs, Conditioned & Calculated Signals
Main KKS Ext. Used for Notes
XQ50 Analogue Input Hardware Input
XQ60 Analogue Signal After 4-20mA Transmitter superv.
XQ63 Analogue signal Error Input disturbance of XQ60 signal
XJ 50 Analogue Output Hardware output
Ccnnn_ or
Fcnnn_ or
FFnnn or
FUnnn
XJ 60 Corrected or Combined
value
Corrected Flow, Level,.. Analogue
signal, 2oo3 etc.
Ccnnn_ or
Fcnnn_ or
FFnnn or
FUnnn
XJ 63 Error of Corr. or Comb.
Value (2o3)
Corrected or Combined analogue
disturb. Signal. Normally event
FAILURE
XJ 64 Error of one signal (1o3) Can include drift alarm! Normally
event SEN UNEQ
XJ 65 Drift between Comb values Analogue deviation between inputs
exceeded, no BDQ included!
Normally event DRIFT
XJ xx Difference between Comb
Limits
Difference between Limit outputs of
individual signals used in a 2oo3 etc.
where "xx" =same number as the
supervised Limit (XHxx).
XJ 01..99 Analogue Signal General calculated values

c & nnn is taken from the KKS of the main input signal
The last 3 digits of the KKS Nr which is the result of 1oo2 or 2oo3 etc. signals will normally
be 9nn
where nn is taken from the lowest number in the KKS of the input signals
eg: The output of a 1oo2 using CF051_XQ60 & CF052_XQ60 would be
CF951_XJ 60
The output of a correction function using CF051_XQ60 & CP052_XQ60 would be
FF951_XJ 60
The 1st character in a KKS can be a character (permitted by KKS and required for some
projects with more than 8 units (Note:0 is not used and 9 is reserved for common
systems)
In general (unless otherwise defined in signal I/O List) Valve position signals have the
same KKS number as the signal source i.e. the Valve KKS with signal extension as
applicable from above table.


Examples from KKS manual
Example 1: Pressure and temperature corrected flow measurement

CF009
CT015
FF009
Corr ect i on
CP011

Example 2: Temperature corrected flow measurement with 2 out 3

2oo3

2oo3

CF001
CF002
CF003
CT901
CF901
Correction FF951
CT001
CT002
CT003

Example 3: Calculated value from 2 different measurements
CT001
CP002
Y=fn(T&P)
FU001

3.5.2 For Limit Values (derived from Analogue values) and direct Binary inputs
Binary
signal
inverse
signal
Status
(Inverse in brackets)

XH07
XH05
XH03
XH01
XH57
XH55
XH53
XH51
>MAX4 (<MAX4 )
>MAX3 (<MAX3 )
>MAX2 (<MAX2 )
>MAX1 or MAX(<MAX1/MAX )
Above Limit values from Comparator
(Analogue source)

XH52
XH54
XH56
XH58
XH02
XH04
XH06
XH08
<MIN1 or MIN (>MIN1/MIN)
<MIN2 (>MIN2)
<MIN3 (>MIN3)
<MIN4 (>MIN4)
Below Limit values from Comparator
(Analogue source)
XG01
XG02
XG51
XG52
OPEN, ON NOPEN, NON)
CLOSED, OFF (NCLSD, NOFF)
Exception is for Electrical Switches where:
XG01 is Switch CLOSED (ON) and XG02 is
Switch OPEN (OFF)
XG01 XG51 eg: >MAX (<MAX) Above limit (>MAX etc.) Binary signal via
hardware DI Module for and other status
texts.
XG51 XG01 eg: <MIN (>MIN) Below limit (<MIN etc.) Binary signal via
hardware DI Module.
XG02 XG52 Normally only XG01 or XG51 is used.
XG03 XG53 If the same signal KKS has more than one
BINARY Signal, then it is allowed to use
additional numbers eg: XG02,03,04 etc.
Use XG03, XG52, etc. in the same way as
for the Analogue derived limits (XH..) if
these additional signals refer to >MAX2,
<MIN etc. signals.


3.5.3 For Drive / Function Group Feedbacks / Commands
Binary
signal
Analogue
signal
UNIDIR DRIVES and VALVES ELECTRICAL SWITCHGEAR
(Breakers, Isolators etc)
Xc01
Xc02
Xc03

Xc06
Xc35
Xc37
Xc38
Xc39
Xc40
ON/OPEN
OFF/CLOSED
ON 2 / FAST/REVERSE
(2
nd
Speed of 2-speed drive) ON
TORQUE

DISTURBED
LOCAL
REMOTE
CLOSED (ON)
OPEN (OFF)

TRIPPED
TEST position
DISTURBED
LOCAL
REMOTE (normally not required
not according REEP)
Xc91
Xc92
Xc93

Xc95
Xc97

XJ 13
XJ 50
XJ 51
CMD ON / CMD OPEN
CMD OFF / CMD CLOSE
CMD RELEASE or CMD 2 ON:
(2
nd
Speed of 2-speed drive)
CMD STOP (Hold)
Positioning output to Control Valve
PIDCON Output
PIDCON Deviation
CMD CLOSE (ON)
CMD OPEN (OFF)

Where: Xc =XA for function groups / selectors
Xc =XB for open loop drives
3.5.4 From/To Pushbuttons, Lamps and Indicators (Hardwired)
(Input)
Pushbu
tton
(Output)
Lamp
(Output)
Indicator
UNIDIR DRIVES / VALVES /
Selectors / Control / General.
ELECTRICAL
SWITCHGEAR (Breakers,
Isolators etc)
Xc11
Xc12
n/a
Xc13
Xc14
Xc15

Xc16
Xc17

Xc19
Xc81
Xc82
Xc83
n/a

Xc85
Xc84
Xc86
Xc87
Xc88
Xc89
OPEN/ON/AUTO/SELECT-1
CLOSE/OFF/MANUAL/SELECT-2
DISTURBED
RELEASE/RAISE/SELECT-3
ACKNOWLEDGE/LOWER
STOPPED
TORQUE
AUTO

DISTURBED/DISCREPENCY
LOCAL
CLOSE (ON)
OPEN (OFF)

TRIP/TRIPPED

AUTO
TEST position
DIST./DISCREPENCY
LOCAL
XJ 50
XJ 80
XJ 81
General Use
PIDCON Control Value
PIDCON Deviation

Where: Source/Destination For: Signal type:
Xc =XA BU, Local, Loc.Pnl Function Groups/Selectors Binary In/Outputs
Xc =XB BU, Local, Loc.Pnl Open Loop Drive Binary In/Outputs
Xc =XG BU, Local, Loc.Pnl General use (Pushbutton) Binary Inputs
Xc =XL BU, Local, Loc.Pnl General use (status Lamp) Binary Outputs
Xc =XU* BU, Local, Loc.Pnl General use (eg alarms) Binary Outputs
Xc =XJ * BU, Local, Loc.Pnl General use (Indicator) Analogue Outputs
BU=Backup Panel (Mimic)
(*): When XA,XB,XG,XL signals are not applicable



3.5.5 For a signal generated within Advant
Signals written to a database element:
Unless the signal is hardwired and has been otherwise defined in a signal I/O list, the
signal will normally take the KKS of the signal source DG, SEL, DRIVE, etc. plus a suitable
signal extension. eg.: 11LAF40EA100_XA91.
Signals used internally in a PC program:
These are given a NAME which is the KKS/Extension as described above preceded by I_.
A clear text description may also be used.
A combination of KKS and Clear Text may also be used. eg: I_11MAN10AA002_RCLS
The KKS number prefix should be removed (to ease copying nodes) if signals do not
require it.
eg: I_MAN10AA002_RCLS
All Signals between pages of a PC program should be given names (exception is between
the MOVES around type Circuits where the TC pins clearly identify the signal source).
3.5.6 Function Group, Selector & Sequencer
Function Group (TC or CFG) EA100
Selector SEL EA111
SEQuence Header CFGSEQ EA201
SEQuencer SEQ XX_EA201
AOC for SEQuencers using STEPGR QXX_EA201
If additional elements are required, these should use a similar construction but with a higher
number following EA


3.6 AC450 Node to Node Communication
Refer to Attachment 4: AC450 Node to Node Interface (Typical)
A minimum of 2 Sending and 2 Receiving DS's with the corresponding DATs is required in
each node, for the communication to every other node of the same unit.
A direct node to node communication shall be used between nodes of different units.
In each node, and for each unit, two PC programs are defined for the node to node
communication:
Communications within same unit: PC10 for incoming signals,
PC 90 for outgoing signals.
Communication to other units: PC11 and PC91,
PC12 and PC92 etc.
This segregation is to enable unit for unit automatic generation of DS communications at a
later date and to simplify node copying
Sending Node PC program (eg:PC90),:
- There is one CONTRM for the communication to each receiving node.
- All DS/DSPs between these 2 nodes are written in this CONTRM.
- The structural element FUNCM (function module) will be used for further structuring of
individual Datasets.
Redundant signals do not have to be sent over different Datasets.
3.6.1 Analogue Signals transferred between nodes
Refer also to Attachment 5 and Attachment 6 for more details of method
KKS for Signals being transferred from one Node to another:
source: nncccnnccnnn_ccnn
sink: nncccnnccnnn_ccnn_NODENUMBER (of sending Node)
Note: The 1
ST
_ may be replaced by a characters explained below).
When 2 similar KKS have been configured in 2 different nodes, it is possible that OS may not
recognize both KKS numbers. This case is usually found in node to node signals. To distinguish
these 2 signals it is advised to use a letter in place 18
th
KKS Character The suggested letters are (
G GT, W WSC, H HRSG, E- ELECT, B BOP, S ST).

Read by all PC
Programs
within this node
which need this
signal.
AIC
18MAJ 10CP001AXQ60
DAT
171801S.R1
DS
171801S
DS
171801R
DAT
171801R.R1
AOC
18MAJ 10CP001AXQ60_17
NODE 17
NODE 18
HSI
Object Display,
Trend,
IMS
(all HSI signals taken from source Node)

Note: Always use AOCs on the receiving side not AICs.


3.6.2 Binary signals transferred between nodes
Refer also to Attachment 5
KKS for Signals being transferred from one Node to another:
source: nncccnnccnnn_ccnn
sink: nncccnnccnnn_ccnn_NODENUMBER (of sending Node)
(Note: the 1
ST
_ must be replaced by any 13th character in the KKS (according note above)
Read by all PC
Programs within
this node which
need this signal.
DIS
18MAJ 10DP001_XG11
DAT
171801S.IL1
DS
171801S
DS
171801R
DAT
171801R.IL1
DOC
18MAJ 10DP001_XG11_17
NODE 17
NODE 18
DIC
18MAJ 10DP001_XU01
Functional Logic
CONV-BI
CONV-IB

HSI
Alarm List,
Event List,
Object Display

Note: Always use DOCs on the receiving side not DICs.
3.6.3 DS Node to Node Communication:
DataSets (DS) are used for Data Transfer over MB300 between all AC450 nodes
General naming template: e.g. 171802R
<From Node> <To Node> <Ident>. Send or Receive
17 18 02 R

DS Name: 171802S

SEND/RECEIVE - S
NODE - 18
ID - 9
DS Name: 181701R

SEND/RECEIVE - R
NODE - 18
ID - 10
DS Name: 171802R

SEND/RECEIVE - R
NODE - 17
ID - 9
DS Name: 181701S

SEND/RECEIVE - S
NODE - 17
ID - 10
Node 17
Node 18

The associated DATs ( .ILnn, Rnn ) are automatically generated when the DS is created.


The ID Nr Together with the SEND or RECEIVE, NET and opposite NODE information is
the unique address for the Dataset.
It is therefore permitted to have the same ID Nr defined multiple times in one Node (refer to
Attachment 5).
If more than 2 DSs are transmitted between the same Nodes the SCAN_FTR must be
different to prevent delays in transmission (refer to DS in Database Element reference
manual).
For the Node to Node communications, the following defaults are used:
SORTREF =NO
The 1
st
DAT of a DS must be an IL.
(Note: Bits 1 to 22 of the 1
st
IL will be used to transmit the error signals of the REALs 1 to 22.)
The 2
nd
DAT is normally IL also but can be used for REALs if required.
The remaining DATs are normally R but can be used for ILs if required.
SCAN_FTR has to be the same for sender and receiver. Normally set to 1.
In order to reduce the re-engineering effort due to inconsistent Send and Receive DS parameters,
it is highly recommended to use the Normal configuration at all times.
2 @ IL (max 31x2 binary inputs) Send Data: CONV-BI (IL,5,31),
Receive Data: CONV-IB (IL,4,31)
22 @ R (max of 22 analogue values)
3.6.4 DAT for DS (AC450)
Communication between PC programs in different nodes are made with DAT elements which are
packed in dataset (DS) and transferred via the Master bus.
Naming of DAT is SSRRIDD.ILn or SSRRIDD.Rnn
where :
SS: number of the sending node, for example 16 for WSC
RR: number of the receiving node, for example 17 for ST
ID: Ident number, for example 02
D: S for Send, R for Receive.
IL: Integer Long, R is for Real number and n, nn is a running number.
3.6.5 Analogue and Binary signals transferred between PC programs (AC450)
Use AOC and DOC DB-Elements for signal-transfer between PC programs in the same Node. If
value should not be accessible from the OS then set the PROC_SECtion value to -1.


3.7 DSP Data Transfer between AC160 and AC450
Data Set Peripheral (DSP) is used for Data Transfer via AF100 between AC160 stations and
AC450 and between AC160 cpus in different AC160 stations.
General naming template: e.g. CLP301
<From Node> <To Node> <Ident>
CL P3 01

As with DS, the associated DATs ( .ILnn, Rnn, .Bnn ) are automatically generated when the DSP is
created:
The ID Nr is the unique address for the Data Transfer TOGETHER with the SEND/RECEIVE and
STATION.
DSPs which send/receive signals to/from type circuits do not carry normal process signals.
3.7.1 Signals Transferred from AC160 to AC450
In AC160 KKS is (normally) without the equipment unit code (i.e. the 1
st
2 numbers of actual KKS
Node 15 (AC450)
P1 (AC160)
AIS: KKS_XQ50
Meco/Functional Logic:
DSP / DAT
AIC: 11KKS_XQ60
Meco/Functional Logic:
DIS: KKS_XG01
DAT / DSP DIC / EVS
EVS DSP / DAT
DIEV: 11KKS_XG01
Value Event
DAT / DSP
EVS to DIEV is an Automatic connection

3.7.2 DSPs for Process signals
Generally for the Station to Station communications, the following defaults are used:
1 @ IL (max of 31 Binary inputs) Send Data: CONV-BI (IL,5,31)
Receive Data: CONV-IB (IL,4,31)
7 @ R (max of 7 Analogue values)
This ratio is free to change as required, however a minimum of 1 IL must be defined per DSP.
The first 7 bits of the first IL will be used to transmit the error signals of the REALs 1 to 7.
A maximum of different 50 DSP Idents can be defined in each Processor Module* but a
maximum of 200 DSPs per processor module* and per physical AF100 bus are supported
(250 DSPs from Firmware version 2.1/x).
The Station Number used by DSPs is virtual, it does not have to be the same as the
RSTA1/RSTA2 Station number defined in the PM6xx, so a physical station can be
subdivided into several virtual stations to increase the number of DSPs (i.e from 50 up to
200 or 250 that can be sent/received from from a single controller module on 1 AF100
bus).
A maximum of 2 AF100s (4 AF100s from AC160 Firmware version 2.1/x) can be
connected per physical station
Refer to section TX3.7.4Typical Definition of DSPs


3.7.3 AC160 Station Numbering
Generally a Turbo Group will consist of 4 to 6 processors in 3 stations:
GT ST Controller Description
10 11 P1 Protection channel 1 (& IP/LP Bypass Stop valves if applicable)
10 11 C1 or CL Closed Loop
10 C2 Closed Loop 2 (for GT24/26 only)
20 21 P2 Protection channel 2 (& LP Stop Valves)
20 OL Open Loop (for GT only)
30 31 P3 Protection channel 3 (& IP/LP Bypass Control valve if applicable)

3.7.4 Typical Definition of DSPs
Due to the quantity of drives used and the limitation of 50 DSP Idents per processor module it has
been necessary to use Virtual Station Nrs instead of actual station Nrs in defining the DSPs.
A maximum of 200 DSPs (250 from Firmware version 2.1/x) can be Sent/Received over one
physical AF100 bus. This allows an average of 5 (6) DSPs per virtual station to virtual station
connection.
The main reason for the high quantity of DSPs is due to the data transmission between Operator
Station (HMI) and the drives in AC160. The DSP format for these HMI DSPs is also different from
those for Process signal exchange to DCS. For these reasons 2 separate destinations (HMI and
DCS) have been defined.
Source Ident. Virt. Stat.
DCS 0 01 .. 07
P1 1 10 .. 17
P2 2 20 .. 27
P3 3 30 .. 37
HSI 4 40 .. 47
OL 5 50 .. 57
C1 6 60 .. 67
C2 7 70 .. 76
Note: 1st digit identifies the Source-Ident Nr of DSP Source, 2nd digit identifies the Source-Ident Nr
of the Destination. i.e. OL is defined as 5, CL as 6 therefore virtual station Nr used for DSP
transmission from OL to CL is 56, from CL to OL is 65


DCS: Process signals interface of AC450 (Actual Station 0)
Virt. Stat. Data from DSP-Nrs. Ident-Nrs. Remark
00 DCS to DCS n.a.
01 DCS to P1 DCSP101..50 150
02 DCS to P2 DCSP201..50 150
03 DCS to P3 DCSP301..50 150
04 DCS to HMI n.a.
05 DCS to OL DCSOL01 150
06 DCS to CL DCSCL01 150 GT24/26 use C1 instead of CL
07 DCS to C2 DCSC201 150 For GT24/26 only
Note: Leading zeros entered as virtual station number are ignored by Advant (0 through 7 will be
displayed)

P1: Protection Channel 1 (Actual Station 11)
10 P1 to DCS P1DCS01..50 150
11 P1 to P1 n.a.
12 P1 to P2 n.a. Data Transfer via HSL
14 P1 to HMI P1HMI01..50 150
15 P1 to OL P1OL01..50 150
16 P1 to CL n.a. Data Transfer via MDAT
17 P1 to C2 n.a. Data Transfer via MDAT

20 P2 to DCS P2DCS01..50 150
22 P2 to P2 n.a.
24 P2 to HMI P2HMI01..50 150
25 P2 to OL n.a. Data Transfer via MDAT
26 P2 to CL P2CL01..50 150 GT24/26 use C1 instead of CL
27 P2 to C2 P2C201..50 150 For GT24/26 only

30 P3 to DCS P3DCS01..50 150
33 P3 to P3 n.a.
34 P3 to HMI P3HMI01..50 150
35 P3 to OL P3OL01..50 150
36 P3 to CL P3CL01..50 150 GT24/26 use C1 instead of CL
37 P3 to C2 P3C201..50 150 For GT24/26 only



HMI: Drive signals interface of AC450 (Actual Station 40)
40 HMI to DCS n.a.
41 HMI to P1 HMIP101..50 150
42 HMI to P2 HMIP201..50 150
43 HMI to P3 HMIP301..50 150
44 HMI to HMI n.a.
45 HMI to OL HMIOL01..50 150
46 HMI to CL HMICL01..50 150 GT24/26 use C1 instead of CL
47 HMI to C2 HMIC201..50 150 For GT24/26 only

OL: Open Loop Control (Actual Station 22)
50 OL to DCS OLDCS01..50 150
51 OL to P1 OLP101..50
52 OL to P2 n.a. Data Transfer via MDAT
53 OL to P3 OLP301..50
54 OL to HMI OLHMI01..50 150
55 OL to OL n.a. 150
56 OL to CL OLCL01..50 150 GT24/26 use C1 instead of CL
57 OL to C2 OLC201..50 150 For GT24/26 only

CL (C1): Closed Loop Control (Actual Station 12)
60 CL to DCS CLDCS01..50 150
61 CL to P1 n.a. Data Transfer via MDAT
62 CL to P2 CLP201..50 150
63 CL to P3 CLP301..50 150
64 CL to HMI CLHMI01..50 150
65 CL to OL CLOL01..50 150
66 CL to CL n.a.
67 CL to C2 n.a. Data Transfer via MDAT

C2: Closed Loop Control 2 (Actual Station 13)
70 C2 to DCS C2DCS01..50 150
71 C2 to P1 n.a. Data Transfer via MDAT
72 C2 to P2 C2P201..50 150
73 C2 to P3 C2P301..50 150
74 C2 to HMI C2HMI01..50 150
75 C2 to OL C2OL01..50 150
76 C2 to CL n.a. Data Transfer via MDAT
77 C2 to C2 n.a.



3.7.5 DSPs used in Broadcast mode:
Although AF100 is used as a point to point communications bus the AF100 can be used in
broadcast mode.
We do not use broadcast mode directly. We use a multiple Point to Point method.
If a broadcast is required, a single DAT source is sent via several Point to Point DSPs.
DATs with this usage are named differently to other DATs used for single Point to Point DSP
communication but are sent over DSPs using the standard Point to Point naming convention
General naming template: e.g. OLPXB01
<From Node> PX <Type> <Virt.Stat>.
OL PX B 01

Example:
The following single DAT might be broadcast.to multiple destinations via multiple DSPs.
DAT Type: DAT Ident: Via DSP Ident: From: To:
DAT(B) OLPXB01 OLP101 OL P1
DAT(B) OLPXB01 OLP301 OL P3

3.7.6 EVS Data transfer between AC160 stations and AC450
Event Set (EVS) elements are used only for transport of time-tagged events from DIC or DIS
database elements in AC160 to AC450. For DI boards the sequence of events parameter must be
activated.
An EventSet element groups a set of Event Channels for sending (AC160) or receiving (AC450)
events.
Events from DIC signals must be transferred in separate EVSs from those used for DIS signals.
A maximum of 32 EVS can be sent from each AC160 CPU (or pair of CPUs) over a single physical
AF100.
General naming template: e.g. EHWCL01
E HW/SW <from Node> <Ident>
E HW CL 01
E SW CL 01
Where: HW is used for transmitting signals from Hardware inputs (DIS)
SW is used for transmitting signals from Software generated signals (DIC)
3.7.7 MDATs (AC160)
For Data transfer between processors in the same BIOB MDATs are used.
Unlike other Advant elements, MDATs are referenced by their Number not their name.The MDAT
Names may be duplicated but MDAT Numbers must be unique.The MDAT Nrs must be the same
in both processor databases.
MDATs have the same name as the source signal but without the signal extension:
e.g: An MDAT(R) would be named: MAC10CP001 if it had MAC10CP001_XQ60 as its source.



3.7.8 High Speed Link: HSL (AC160)
For High Speed Data transfer between AC160 stations HSLs are used.
HSLs are connected between CPUs. If High speed Links are used It is not possible to connect
them to Redundant CPUs as the redundant CPUs use the HSL for synchronising their Data/status.
For this reason they are only used between the Protection CPUs P1, P2 and P3.
The Database elements used for this communicating are HSLS (send) and HSLR (Receive).
General naming template: e.g. [P1IL01]
[ <source> <Type> <Ident> ]
[ P1 IL 01 ]

Typical DB Configration:
Protection Channel 1:
Element Name Type Channel Ident
HSLR [P2IL01] IL 1 2
HSLR [P2R01] R 1 2
HSLR [P3R01] R 2 3
HSLS [P1IL01] IL n.a. 1
HSLS [P1R01] R n.a. 1

HSLR [P1R01] R 1 1
HSLR [P3R01] R 2 3

HSLR [P1R01] R 1 1
HSLR [P2R01] R 2 2


3.8 FCB and OLB:
3.8.1 FCB page layout setup
The following page setup shall be used:
Page Layout Template: DIN 6771 A4 Landscape English
Height: 100 Columns
Width: 200 Rows
3.8.2 OLB page layout setup
Go to Page Setup in the Commands bar of the OnlineBuilder
Select DIN6771 A4 landscape English
Set Width x Height to 100 x 200
Enter seom
3.8.3 TPX (Header) file and Required Information
The following standard .TPX file should be used, it contains the required format for the DIN6771 A4
page setup:
Copy to the FCB project root directory and delete any "foot001.bin" file otherwise the tpx file will not
have any affect.


4. Basic Configuration of DCS

All PC program PCPGMs are expected to have the same time setting (40ms) therefore the
execution order of the PC programs will be deterministic if loaded into the controller in order of PC
number

4.1 AC450 PC Program Structure

Error! Objects cannot be created from editing field codes.
Note: PC1..3 is used for input signals handling (Redundant channels). Due to limitations on Local
Data Area, If a large number of inputs exist in any of these PC programs (.AAX file larger than approx
300kb) it may be necessary to split it up (use PC4)


4.2 PC-Program-numbering
PC. Name Remark
MECO
1 Transmitter Supervision Red 1
4 Meas. Conditioning, Signal Limits
Communication Input
10 Node To Node Input
11 Node To Node Input From Other Units
12 Node To Node Input From Other Units
17 Modbus to SFC
18 Modbus to DCS
19 Modbus to Vibration Monitor
Inputs from AC160
20 Signalcond. PROT1-AC450
23 Signalcond. CLC1-AC450
24 Signalcond. CLC2-AC450
25 Signalcond. OLC-AC450
26 Signalcond. OLC-AC450 Only GT24/26
Sequencers
30 Main Sequencer
3139 All other sequencers e.g. BSCD, LubeOil,..
Process Systems
4079 All process systems e.g. Gland Steam, Fans,..
Interface HMI/AC160/AC450
8088 All INTF e.g. INTFMOV, INTFBCL,..
89 System Diagnosis
Communication Output
90 Node To Node Output
91 Node To Node Output to other Units
92 Node To Node Output to other Units
94 Process-Simulator (for FAT) To be deleted after FAT
98 Signals AC450-AC160
Simulator/Simulations
99 Drive-Simulator (for FAT) To be deleted after FAT


4.3 Correction Functions (AC450)
Correction functions of individual analogue inputs may be implemented in PC1 to 3 (dependant on
the redundancy) or in PC4 to 6 (which are recommended for containing the hardware I/O analogue
limits logic).
If PC1 to 3 is used then CONTRM numbers higher than 32 must be used for these correction
functions as CONTRM 1..32 are reserved for the analogue input card signals.
In order for PC program 1 to 3 to be updated at any time by in-house tools, the signal exchange
between Supervision output signal (XQ60) and correction input MUST be made via the Database
not via internal connection or Name.

1oo2, 2oo3 or AVERAGE values of analogue input signals are implemented in PC4.

AIS1.1
(XQ50)
Wire Break Supervision
Redund. 1
AIC1
(XQ60)
PC Program 1
In PC4 (using corrected or uncorrected signals)
2oo3
etc.
AIC4
(XQ60)
AIS2.1
(XQ50)
Redund. 2
AIC2
(XQ60)
PC Program 2
AIS3.1
(XQ50)
Redund. 3
AIC3
(XQ60)
PC Program 3

Note:Refer to note on PC1..3 program sizes in previous section.
Refer to section 3.4.2 and Attachment 12 for method of implementing limits


4.4 Typical PC structure
In AC450 Contents are divided per PC-program according to process function .
A limit of approximately 20..25 drives or Large functions in each PC-program will avoid reaching
the limit of the Local Data Table. Note that analogue f(x) Curves use up a large amount of Local
Data Area.
Having a structure is more important than attempting to force a particular structure for all projects.
The PC element numbers used below are an example only but should be followed unless there is a
compelling reason why they are not feasible for a particular application.
The actual PC element numbers used can be determined on a per project or even per node basis.
PCx
x.1 CONTRM (for General Input Logic)
x.11 CONTRM (for 1
st
FunctionGroup)
x.11.1 FUNCM (Application logic FunctionGroup)
x.11.2 FUNCM (Application logic SEL)
x.11.11 FUNCM
x.11.11.1 through n MOVES (Inputs to TC)
x.11.11.50 TC FG
x.11.11.m through 20 MOVES (Outputs from TC)
x.11.12
x.11.12.50 TC SEL

x.21 CONTRM (for 1
ST
Drive)
x.21.1 FUNCM (Application logic for Drive)
x.21.11 FUNCM
x.21.11.50 TC DRIVE

x.22 CONTRM (for 2nd Drive)

x.51 CONTRM (for 1
st
Analogue drive)
x.51.1
x.51.11 PIDCONA
x.51.11.21 GENUSD (for visualisation)

x.52 CONTRM (for 2nd Analogue drive)

x.91 CONTRM (for Outputs/General Output Logic)

Note:
To make sure any TC can be exchanged properly by a new version at any time (see 1AHL105876,
Exchanging Type Circuits Design Directive) it is essential that the PC element number of the TC is
higher than the highest number used by the Logic PC elements, e.g. as shown here above .50.


4.5 APC-Element Settings
The following is valid for the raw APC elements, as Type Circuits (containing these APC functions)
are used, the Input and output names will be different and may be inverted compared to those
shown in the following tables.
Refer to Engineering Solutions and Type-circuits documentation for Database and PC settings for
all APC elements.
GEN-types for Drives: (See following Tables for further info)
Drive GU-Type Remarks
DRVSV1 GU4
DRVSV2 GU5
DRVMOV GU5
DRVPMP GU3
DRVBRK GU3
DRVFAN GU6
FG GU2
SEL GU2
4.5.1 PIDCONA PID Control Function
PC Element:
Terminal Value Remarks
BUMPLESS 1
MV XQ60 / XJ 60 Measured Value
MANENBL XA03 Funct.Grp Hold
MANFL XQ63/XJ 63 Cntrl variable dist (XQ63/XJ 63) "OR"ed with 10s delay
REVACT 0: when MV >SP =>OUT is raising;
1: when MV <SP =>OUT is raising
OUT XJ 13
DB-Element:
NAME KKS
DEC 1 1)
UNIT % 1)
MAX 100.0 1)
MIN 0.000 1)
AI_ERR Never use this
ACT_DIR OPENING Always OPENING
SHOW_ACT 1 to be used when POSition transmitter is available, related with
DB-input ACTPOS
E1NAME
E2NAME
E3NAME
PC element call parameters C1 to C6: depend on use (Typical 1,1,1,0,1,0)
MANENBL/AUTOENBL =0 and E1ENBL/E1REF1 =1 :=>for control without operator access and
SP fixed or external.
TRACKEXT =2 for tracking AUTOSP in mode E1 or E2
Limits and alarm/event treatments will be not used on PIDCONA.
For CVs with reverse action (fail safe open), the signal OUT is subtracted from 100% before
connection to AOS.
Use a GENUSD-I to indicate valve position (refer to next section):


4.5.2 CV with fault indication
Valves with intermediate position
PC Element (GENUSD-I):
Terminal Value Remark
ALQ1 Sign Error
ALF2 POS Ind Error (XQ63) OR Pos. Discrepancy (+/- 5% delayed
10 sec) or only analogue feedback error (XQ63)
INTLU3 Safety Control
IND1 XG01
IND2 XG02
IND3 Intermediate: not open AND not closed
IND4 D=1

DB Element:
NAME KKS (13)
VAR GU5 In general use on OS any GU5 display element For devices
with only 1 feedback signal (Open or Closed) use DIVV or
DIVH display elements)
VALALWD HFFFF
ORDALWD HFFFF
MVH1 512 Depends on visualisation in object display
MVL1 128
RP_BLK 0
AL_TR 129
INTL_TR 131
IND_TR 124
BLK_TR 140
VAL_TR 139
ORD_TR 144



4.5.3 SOV/MOV with fault indication
ShutOff Valves or Motor Operated Valves with or without intermediate position
PC Element (GENUSD-I):
ALQ1 XB38 Sign Error (Disturbed)
ALF1 Posn. Discrepancy Open
ALF2 XQ63 Posn. Ind Error
ALF3 Switching Fault
ALF6 Posn. Discrepancy Close
INTLU3 XB35 Safety Control
IND1 XG01 Open position
IND2 XG02 Closed position
IND3 Intermediate position:Inverted XG01 ANDed with Inverted
XG02
IND4 D=0 Set IND4=0 and BLK to D=1 to display a green "C" by object on
OS otherwise a yellow "P" is displayed.
ORDC1 Order Open/On
ORDC3 Order Close/Off

DB Element:
NAME KKS (13)
VAR GU4 In general use on OS any GU4 display element for SOV, or
any GU5.. for MOV
VALALWD HFFFF
ORDALWD HFFFF
MVH1 0 Parameter depends on visualisation in object display
MVL1 128 or 0 or 1 Set to 0 if ON/OFF commands are required or to 1 if
OPEN/CLOSE commands are required
RP_BLK 0
AL_TR 123
INTL_TR 121
IND_TR 124
BLK_TR 140
VAL_TR 139
ORD_TR 142



4.5.4 Unidirectional Drive
Used for position feedbacks where more than one feedback is available.
PC ELEMENT (GENUSD-I)
ALQ1 Sign Error
ALQ2 Power Failure
ALF1 Posn. Discrepancy On
ALF2 Posn. Ind Error (Disturbed)
ALF3 Switchgear Fault
ALF6 Posn Discrepancy Off
M1 D=1
BLK D=1 Set IND4=0 and BLK to D=1 to display a green "C" by object on
OS otherwise a yellow "P" is displayed.
IND1 XG01 Position ON
IND2 XG02 Position OFF
IND3 D=00
IND4 D=0 Allow C with Block

DB Element:
NAME KKS (13)
VAR GU3 In general use on OS any GU3 display element
VALALWD HFFFF
ORDALWD HFFFF
MVL1 128
RP_BLK 0
AL_TR 120
INTL_TR 121
IND_TR 122
BLK_TR 140
VAL_TR 139
ORD_TR 141


4.5.5 Simple Logic (e.g. FlipFlop )
Use for any pushbutton commands where the standard APC PC/DB display elements are not
required (eg: Set or Reset commands, Acknowledge, Lamp Test etc.
If feedback criteria are not available then a solution based on a DOC database element can be
used.
PC ELEMENT (GENUSD-O)
ORDC1 XB91 ORDER ON
ORDC3 XB92 ORDER OFF

PC ELEMENT (GENUSD-I)
Teminal Value Remark
M1 D=1
BLK D=1
IND1 XG01 ON
IND2 XG02 OFF
IND3 D=0
IND4 D=0

DB Element:
NAME KKS (13)
VAR GU3 Use on OS either GU3GO or a DIC / DOC solution
VALALWD HFFFF
ORDALWD HFFFF
MVL1 0 Set to 0 if ON/OFF commands are required or to 1 if
OPEN/CLOSE commands are required
RP_BLK 0
AL_TR 120 Only if functionality is used. Normally set to 0
INTL_TR 131 Only if functionality is used. Normally set to 0
IND_TR 132 Only if functionality is used. Normally set to 0
BLK_TR 140 Only if functionality is used. Normally set to 0
VAL_TR 139 Only if functionality is used. Normally set to 0
ORD_TR 141 Only if functionality is used. Normally set to 0


4.6 Database Element Configuration
4.6.1 AF100 scantime settings for S800
AC450-Systems (S800 connected to CI522)
The following standard settings must be used for good performance-CPU-load relation:
Parameter Settings Remark
AF100 scantime
(INSCANT/OUTSCANT)
Analog: 32ms, Digital 16ms Calculated AF100 bus load
<70% with up to 9 Stations.
AF100 scantime
(INSCANT/OUTSCANT)
Analog Input: 64ms
Analog Output: 32ms,
Digital Input 32ms
Digital Output 16ms
Calculated AF100 bus load
<70% with 9 to 12 Stations.
Input Scanning time CI522
(SCANT)
Analog: 200ms, Digital 100ms

AC160-Systems (S800 connected to CI631)
The following standard settings for Egatrol must be used:
Parameter Settings Remark
AF100 scantime
(INSCANT)
Analog: 64ms, Digital 32ms
Input Scanning time CI820
(INSCANT)
32ms

4.6.2 Analogue Output Module (e.g. AO810, )
IMPL 1 Only for used cards, otherwise 0
GRIDFREQ 50Hz
CONV_PAR 4..20mA
OUTSCANT 32ms Fieldbus scantime on AC450 systems
OUTSCANT 64ms Fieldbus scantime on AC160 (Egatrol)
INSCANT 64ms Fieldbus scantime on AC160 (Egatrol) INSCANT=OUTSCANT

4.6.3 Analogue Outputs AOS (e.g. AOS810, )
As these signals are primarily used for Control valve output signals, the following values are to be
set.
CONV_PAR 4..20mA
RESTART STVAL Used for applications where a predefined output value is
required by initialization.The default is that the cards start up
with STVAL =0.0 except in specific instances
STVAL 0 See above
ERR_TR 0 Not used



4.6.4 Analogue Input Module (e.g. AI810, AI830, )
GRIDFREQ 50Hz
CONV_PAR 4..20mA for AI830: Pt100,850C
INSCANT 32ms Fieldbus scantime on AC450 systems. 64ms for 9..12 stations!
INSCANT 64ms Fieldbus scantime on AC160 (Egatrol). For AI830: 256ms

4.6.5 Analogue Inputs AIS (e.g. AIS810):
ACT 1 Only for used channels, otherwise 0
CONV_PAR 4..20mA
SCANT 200ms Input scanning CI522 (only AC450).
LIN_CODE 0
FILTER_P 0
DEADB 0.2%
ERR_CTRL 0 Last valid value to be held when the error bit is set (only
AC160)
ERR_VAL 0.0 (only AC450)
DEC Nr. of decimals to be shown on the HMI. See table below
NORM_TR 1 To allow event driven updating of the HMI (only AC160)
H2_R_FCL 1 1 to avoid repeat alarms from filling the buffers (only AC450)
H1_R_FCL 1 1 to avoid repeat alarms from filling the buffers (only AC450)
L1_R_FCL 1 1 to avoid repeat alarms from filling the buffers (only AC450)
L2_R_FCL 1 1 to avoid repeat alarms from filling the buffers (only AC450)
ER_R_FCL 1 1 to avoid repeat alarms from filling the buffers (only AC450)
ERR_TR 2 (only AC450)
LIM_1_TR 0 Process alarms are by COMParators to DICs not AIS (only
AC450)
LIM_2_TR 0 Process alarms are by COMParators to DICs not AIS (only
AC450)
HYST approx 0.5 % of meas. Range (only AC450)

Setting for DEC of decimals to give 4 significant figures within the measuring range:
Range (Max-Min) DEC Display Example
0 0.1 4 0.0345
0.1 1 3 0.655
1 10 2 7.55
10 100 1 88.5
>100 0 600

Missing Range Values: When input parameters are not known during the Engineering; the values
999, -999 or 0.000999 will be entered in place of the missing values to show that a value is
expected later.
These values must be replaced as and when they become available or during commissioning
Use of Limits: Generally the limits of the AIS and AIC should only be used for Alarm Values, not
for normal non-alarmed switch points.



4.6.6 Binary Input Module (e.g. DI830, )
INSCANT 16ms Fieldbus scantime on AC450 systems. 32ms if 9..12 stations!
INSCANT 32ms Fieldbus scantime on AC160 (Egatrol)
SCANT 100ms Input scanning CI522 (only AC450).
SENSOR 0 (Only AC160)
SPS_MODE 24V external (Only AC160)
ERR_SUP NO (Only AC160)
SUP YES Sensor power Supervision
FILT 8 minimum pulse length required at input to be detected as a
signal (Only on AC450)
MODE SOE (Only AC450)
SHUTPER 0 (Only AC450)
SHUTTRI 0 (Only AC450)
RECTIME 0 (Only AC450)

4.6.7 Binary Inputs DIS (e.g. DIS830, )
NORM_POS Used to define the Normal Signal Value, the default value of
0 is used when the binary signal non-active state is 0 (non-
active=when the status text associated with the VALUE_TR
pointer is NOT True)
NORM_TR 1
RP_F_CTL 1 1 to avoid repeat alarms from filling the buffers (Only AC450)
ERR_TR 2
ERR_CTRL 0 The input will either be frozen when the card error card occurs
if ERR_CTRL=0 or set to the inverted value of NORM_POS if
ERR_CTRL=1
MODE SOE (Only AC160)
FILT 8ms minimum pulse length required at input to be detected as a
signal (Only AC160)
ERR_TR 2
SHUT_PER 0 (Only AC160)
SHUT_TRI 0 (Only AC160)
REC_TIME 0 (Only AC150)

4.6.8 Binary Output Module (e.g. DO815, DO810,..)
IMPL 1

Only for used cards, otherwise 0
OUTSCANT 16ms Fieldbus scantime on AC450 systems
OUTSCANT 64ms Fieldbus scantime on AC160 systems (Egatrol)
INSCANT 64ms (Only AC160) INSCANT=OUTSCANT
SUP YES Sensor power Supervision



4.6.9 Binary Outputs DOS (e.g. DOS815, DOS810, )
ACT 1 Only for used channels, otherwise 0
OSP_CTRL 0 Keep current Value in case of failure (OSP_CTRL=1 ->take
OSP_VAL
OSP_VAL 0
4.6.10 S800 I-O-Station (e.g. CI820)
CABLE R Redundant cable
REDUND YES Redundant station
SUP_PS YES
SUP_PS_E NO
EXT_TIME YES (only AC160)
TIM_SYNC SLAVE (only AC160)
INSCANT 32ms (only AC160)
CH_OVER NO (only AC450)
BUS 2 Normally 2
4.6.11 S600 Communication Cards for AF100 (e.g. CI610, CI631)
MASTER 1
TIMESYNC SLAVE for CI631 which connects to S800-I/O set to MASTER!
REDUND 1
CABLE 2 Redundant cable
BUS 1 For CI631 which connects to S800-I/O normally 2
STATION See section 3.7.3 AC160 Station Numbering
For CI631 which connects to S800-I/O normally 19
4.6.12 Speed Measurement DPS640
ACT 1 DPS640 in other PM on same Rack must be set to 0
MODE ROTATION
MONTYPE UT386 Otherwise GENERAL
MEAS_PER 20
HIGH_PREC ON
MAXGRAD 100
POWERMON 1
DELTAVAL 120
DELTALIM 4
Refer to the following documents for latest SIL3 requirements:
For GTs:Implementation Guide for AC160 SIL3 Turbine Overspeed Protection for Gas
Turbines": 1KHZ 102 005
For STs: "Implementation Guide for AC160 SIL3 Turbine Overspeed Protection for Steam
Turbines": 1KHZ 101 994
Deviations from the settings in these documents are in principle not permitted. Any such deviations
must be agreed in writing with our platform group PTUPA in order to comply with the SIL3
certificate


4.6.13 Analogue Input Calculated (AIC on AC450):
PC Programs WRITE to :CALC_VAL, PC Programs READ from VALUE
AICs can be written from the HSI if the signal source is connected to :CALC_VAL and the
Database Update is Blocked (same as AI)
Database settings refer to AIS, section Analogue Inputs AIS (e.g. AIS810):.
4.6.14 Digital Input Calculated (DIC on AC450):
PC Programs WRITE to :CALC_VAL PC Programs READ from :VALUE
DICs can be written from the HSI if the signal source is connected to :CALC_VAL and the
Database Update is Blocked (same as DI)
DICs can be given VALUE TREATMENT (Alarm List, Event List)
Set ERR_TR =2
Note: in AC160 the SCANTIME setting of DICs has a huge affect on system load. If a single DIC is set
to a fast scantime, then the EVENTSET task runs at this speed also. As an example: a scantime of
640ms instead of 80ms can reduce the cpu load by approx. 20% (on a PM645) depending on the
quantity of EVS's used.
4.6.15 Analogue Output Calculated (AOC):
PC Programs and HSI: READ and WRITE to VALUE
In AUTO the value is written from the PC program, in MAN the value can be changed by the
Operator Station.
AOCs do NOT have any Value Treatment.
Set ERR_TR =0 (Err_Tr terminal has no effect)
4.6.16 Digital Output Calculated (DOC):
PC Programs and HSI READ and WRITE to VALUE
In AUTO the value is written from the PC program, in MAN the value can be changed by the
Operator Station.
DOCs have NO value Treatment.
Set ERR_TR =0 (Err_Tr terminal has no effect)
Note: setting and comment are also valid for DOS



4.7 AC450 Hard- and Software Limits
4.7.1 S800-Stations
In a normal configuration up to 12 Stations can be used on one AF100-bus. Be aware that if you
use more than 9 stations, the INSCANT has to be redused! Always use the defined scantimes in
section 4.6.1: AF100 scantime settings for S800.
On one Station a maximum of 12 I/O-Modules can be connected, 24 modules if there is a bus-
extension installed.
If you want to do a non-standard configuration with more than 12 S800-stations, use the busload-
calculation excel-sheets to verify your configuration. There is no limitation in the number of stations,
but you have to adjust the scantimes to have the bus-load below 70%.
4.7.2 Signals
Signal Max
DIS +DIC +DIEV 2300
DOS +DOC 1489
AIS +AIC +AIEV 910
AOS +AOC 963

4.7.3 DB Objects
Object Max
SEQ 173
GENOBJ (GENUSD +
GENBIN +GENCON)
528 (in total)
MOTCON +VALVECON +
GROUP +MMCX
595 (in total)
PIDCON 234
PIDCONA 203
MANSTN 420
RATIOSTN 330
GRPALARM 330
GRPMEMB 2'978
DAT 32'000
DSP 4'000

4.7.4 TTD Logs
Item Max
Logs 15
Variables/log 127


4.8 AC160 Hard- and Software Limits
4.8.1 Cards & Racks
Card Type Max Recommended Remarks
I/O cards per basic station
(includes extension rack)
10 +10 18
Basic station (CPUs +I/Os) 1
I/O stations 7 4 Note1
I/O station extension rack 1 per stn.
S600 I/O Bus Extension
cable
20 metres
I/O cards 151 75 Note 1
Modbus cards (CI532) 2
AF100 Links 2 (1xRed)
8 (4xRed)*
* 8 links from Firmware version
2.1/x
HSL (High Speed Link) 2 per cpu Note 2
Note 1: Using the basic station +extension rack plus 4
I/O-stations with extension racks, the recommended
maximum number of cards (75) can be accommodated.
Note 2: It is possible to use one Link to connect 2
CPUs as a redundant pair and additionally use the
second link as a "normal" HSL to communicate with
another redundant pair of CPUs in another station as
shown on the right
4.8.2 Signals
Signal Max
DIS 4812 (Notes 1 & 2)
DOS 4812 (Notes 1 & 2)
AIS 4812 (Notes 1 & 2)
AOS 2416 (Notes 1 & 3)
Note 1: For performance reasons, a max of 75 I/O cards and 1500 I/O channels is recommended.
Note 2: If only this type of I/O card is used. (=approx. 151 cards x 32 channels)
Note 3: If only this type of I/O card is used. (=approx. 151 cards x 16 channels)
4.8.3 DB objects
Object Max
EVS 32
DSP 200 per controller and per AF100 Link (250
from from FW vers. 2.1/x)
DAT 5'461 (8'191 for PM665)
Modbus Interfaces via
CI532
4 Links (as Master) or 2 Links as Slave
4.8.4 PC elements
Object Max
Total of: CONTRM +
SEQ +MASTER
31 ( 63 for PM665)
Total of FUNCM +
STEP +SLAVE
999 per Structure Level (max 9 Levels)
Terminals 7'000 per CONTRM



5. Hardware Supervision
5.1 Transmitter and Wire-break Supervision in AC450
Refer to Attachment 7: AC450 Transmitter and Wire-Break Supervision for PC Program printout
Note: This does not apply to RTD (pt100) or TC input connection unit signals AI830 (S100: DSTA146,
DSTA155).
The Advant standard for supervising differential channel analogue inputs is part of the AI810 (for
S100: DSTA133/135) firmware and gives an alarm when a signal falls 2,4% below the
RANGE_MIN value of the signal range (equivalent to 3.62mA). This can only be considered as wire
break supervision for the Rosemount transmitters which fail to various signal levels above this (eg:
3.75mA. depending on the model). A similar situation can occur at the top end of the transmitter
range if the transmitter is set for upscale burnout.
For supervising transmitter failure, the PTUP standard value of 1.25% of Meas. Range below 4mA
(equivalent to 3.8mA) and 5.625% above 20mA (equivalent to 20.9mA) is required, a software
solution must therefore be implemented.
For each Analogue input-card a separate CONTRM will be used (numbered according to AI card
number). The CONTRM will head 16 FUNCMs (numbered according to the AI Channel numbers).
Each FUNCTM will contain a program which supervises the signal received from the Analogue
Input card. It sets the :ERR pin (disturbance bit) of an AIC in the database if the signal falls below
the 3.8mA limit, or rises above the 20.9mA limit or if the Analogue Input Card is DISTURBED.
At the same time all the AIC Limits are DISABLED.
The disturbed signal is allocated the signal name extension _XQ63.
The Analogue signal used by the DCS will be the AIC signal, and will be identified by the signal
name extension _XQ60.

To avoid inconsistencies between AIS and AIC ranges etc, the program writes the following signals
from the AIS Database Element to the AIC:
RANGE_MIN to DISPMIN
RANGE_MAX to DISPMAX
LIM_L1 to LIM_L1
LIM_L2 to LIM_L2
LIM_H1 to LIM_H1
LIM_H2 to LIM_H2
HYS to HYS
All changes to measurement ranges, Limits and Hysterisis must be made on the AIS
database Element or in a PC program which writes to the AIS. (PC4)
If the AIS supervision has not detected an error, the program writes the following signals from the
AIS Database Element to the AIC to enable the alarms:
EN_L1
EN_L2
EN_H1
EN_H2
Notes:
1) Any previously exceeded limit output of the AIC remains set to 1.
2) If it is required that limit signals which were already active before the disturbance are switched off
(similar to Procontrol method) then the XQ63 signal should be used to block unwanted limit signals in
the destination PC program or in the PC program where the limits are generated (eg. PC 7..9) In this
case, the AIC limits displayed on the HSI can have a different status to the DIC alarm.
3) If the Limit status should stay as it was before the disturbance, then the XQ63 interlock is not
required.



5.2 Analogue Signal Transfer Between Nodes (AC160,AC450)
In applications where Analogue Values are transferred between Nodes, supervision of Signal
failure must be implemented.
Signal Failure (No Updating of the Receiving Database Element) will occur if :
Node-Node communication is lost. (no connection for more than the number of cycles
stated below)
- for sending Node type: AC450 3x CYCLETIM;
- for sending Node AC160 (DSP) 8x CYCLTIM when REDUNDANT CI522's are used i.e.
AC450<->AC160)
Input signal Error: Process input signal error bit :ERR of the AIS or AIC database element
is set or the process input signal is less than the transmitter supervision limit.
Note:
Refer to Attachment 6: AC450 Node to Node Analogue Signal Error Handling for AC450 to AC450
communication.
Refer to Attachment 1: Analogue Signal Error Handling AC450 to AC160 for AC450 to AC160
communication
Refer to Attachment 2: Analogue Signal Error Handling AC160 to AC450 for AC160 to AC450
communication

5.3 Transmitter and Wire-break Supervision in AC160
5.3.1 Wire-break Supervision for S600 (e.g. AI625)
For supervising transmitter failure, the same values as required in AC450 cards 3.8mA and 20.9mA
is required. In order to carry this out, a software solution is therefore being implemented.
The input LO_LIM2 of the Analogue Input channel (AIS) is set to 1.25
The input HI_LIM2 of the Analogue Input channel (AIS) is set to 105.625
Set Hysterisis to 0.1
The output VALUE<L2 plus the "VALUE>H2" plus the Error signal from the AI card is then
combined via an OR function to create a disturbance signal (XQ63) (refer also to Attachment 8:
AC160 MECO for S600).
5.3.2 Wire-break Supervision for S800 (e.g. AI810, AI830, AI835)
AI810
For AI810 I/O the same principle is used as for S600 I/O, but the limit-supervision has to be done
with extra COMP-R elements because the AIS810 has no LO_LIM or HI_LIM terminals.
See Attachment 9: AC160 MECO for AI810 for detailed info.
AI830
RTD-elements (resistive elements e.g. Pt100) use the AI830 card. No scaling is needed, the range
is defined by the element type (e.g. Pt100,850C).In the AIC on AC450 the DISPMIN and DISPMAX
is set to the Adjusted Range (defined in instrumentation list). For BDQ only the :ERR b it is used.
See Attachment 10: AC160 MECO for AI830 for detailed information.
AI835
No scaling is needed for Thermocouples (see AI830 above). On channel 8 normally a PT100
compensation measurement (cold junction) is used. For the BDQ the :ERR of the thermocouple
and :ERR of the compensation is used.
See Attachment 11: AC160 MECO for AI835 for more detailed information.


5.4 Multiple measured Analogue process variables (Drift alarm)
If the same analogue process variable is measured multiple times for use in control or protection
logic, then the drift (difference) between these signals must be supervised and alarmed if it
exceeds a defined limit (the standard limit is 10% of measuring range. If a different value is
required, this must be specified in the PFuP).
This supervision is to be performed even if not specifically defined in the PFuPs.
For implementation refer to Attachment 13: 2oo3 Analogue signal and alarm handling.
5.5 Error-Handling of signals used for Protection
This section relates to Alstom requirements. Requirements for other customers may differ.
Refer to Attachment 14 through Attachment 21 for detailed methods.
Fault Categories defined by Alstom:
Damage caused by a fault Fault Category (FC)
Extent of injury or damage Energy
set free Persons Plant Downtime*
Timing of event Event FC
very high highly likely severe >6 months immediate major accident 1
high less likely extensive months almost immediate accident 2
low not likely medium weeks moderately delayed fault 3
none none slight days easy to control disturbance 4
* =time to repair
Switching options and required Error-Handling for protection logic:
Protection
Method
Action if 1
signal is
disturbed
Action if multiple
signals are
disturbed
comments
2oo3 Active 0
(FailSafe)
Alarm 2oo3 Err ==>Trip Refer to Notes 1 & 2
1 chan. disturbed +1 chan. Trip =Trip
Output
2oo3 Active 1 Alarm 2oo3 Err ==>Trip Refer to Notes 1 & 2
1 chan. disturbed +1 chan. Trip =Trip
Output
1oo2 Active 1 Alarm 2oo2 Err ==>Trip Refer to Notes 1 & 2
1 chan. disturbed +1 chan. Trip =NO
Trip Output
2oo2 Active 1 Alarm No Action Not used for FC1 and FC2
1oo1 Active 1 Alarm Not Applicable
1oo1 Active 0
(FailSafe)
Trip Not Applicable Only rarely used when defined by the
Process Engineer as the availability is
highly reduced.
1oo2 Active 0
(FailSafe)
Trip (Already Tripped)

Only rarely used when defined by the
Process Engineer as the availability is
highly reduced.
2oo2 Active 0
(FailSafe)
* * *Do not use as 2oo2 with Active 1
covers this.
Notes:
1) General: The use of error signals in the trip logic is a requirement for FC1 and FC2 protection only
2) For reasons of consistancy, the 2oo3 and 1oo2 trip logic methods (with error signals) used for FC1
and FC2 will be used for all Fault category protection levels where 2oo3 and 1oo2 methods are
implemented.
Basically every measurement error is alarmed either via the measurement or via the card
disturbance, therefore no additional engineering is required for alarming of the individual signal
errors.
These switching options with their error-handling are valid for protection logic and are to be used
for both analogue and for binary logic.


6. Tips and Tricks for AC450 planning
6.1 MANSTN
Text entered in the Database element E1_NAME is displayed on the object display.
The PC Element :OUTPUT must be connected to the database Element input :POUT for correct
visualisation.
The inputs PO_MIN & PO_MAX as well as MIN & MAX and OUTP_HL and OUTP_LL should be
used to ensure the correct output of the MANSTN.
Inputs to either MAN or E1 are converted to PULSES inside the macro!!!
Any constant signals will block EXTERNAL switching!!
For Manual Stations which are ALWAYS in MANUAL MODE but which have ONLY SUPERVISOR
ACCESS, the MANSTN HSI Object is specified as Dialog =NONE then the Supervisor has access
to the Manual Station Output ONLY via the Engineering Station (modify database element
OUTPUT pin).
6.2 PIDCONA
The limits from the OS only function when the PC Element pin EOLIM (Enable Outside Limits) is
set to 0.
When External Limits are enabled there is no indication to the Operator and changing the limit from
the screen HAS NO EFFECT on the Output!!!
The AOS/AOC Output connected to the PIDCONA/MANSTN Output must have its limits set 0 to
100% to ensure correct HSI representation.
If Measured Value or Deviation Alarms are not required the PC Element pin ALCBLK must be set
to 1.
Default settings for Controller parameters: (These rule of thumb values must be optimised during
the plant startup):
Variable Type of Control Proportional (K) Integral (I) Derivative (D)
Level P I 20 % * 2 min
Temperature P I D 10 % * 2 min 1 min
Pressure (Liquid) P I 100 % * 0.25 min
Pressure (Gas) P I 3.5 % * 0.5 min
Pressure (Vapour) P I D 35 % * 0.3 min 0.1 min
Flow P I 200 % * 0.15 min
Analyser P I 200 % * 0.2 min
Cascade (Master) P I D 1.5 x applicable
variable Type
2 x applicable
variable Type

Cascade (Slave) According to
variable
1.5 x applicable
variable Type
2 x applicable
variable Type

* or applicable unit used in PIDCONA
The default value for the HOT INITialisation pin in the PC Element must be set to 2. This ensures
that the controller starts in MANUAL and the Output is set to 0 (minimum).

Fail Open Control Valves
The Outputs from PIDCONA or MANSTN which are used on fail-open control valves are inverted in
the PC program between the final element and the AOS.
This helps the transparency since the standard ABB philosophy for Control Valve operation is that
the 100% position shown on the HSI means VALVE OPEN.


6.3 Event and Alarm List - system time-sync errors
There are only two possible characters for the last character in the alarm list (a character which
follows the time stamp),
U =Indication of uncertain time tagging
S =Indication of missing time tagging (The "S" tag is not described in any Advant manual.)
If either of these characters appear then there is a problem with the Time synchronisation within
the system.
6.4 REG-G & FUNG-1V
For applications where a FUNG-1V is used with REG-Gs and the Balance input is used on the
FUNG-1V, the set of values used in the REG_Gs must begin 5% below the usable range and
finish 5% above.
This avoids the setting of the error Flag and possible incorrect values being processed by the
system.
Avoid using excessive numbers of inputs to these elements: They use up large amounts of Local
Data Area.
6.5 Using TCs
Use a FUNCM containing only MOVEs around a single type circuit.
This is to ease making and checking values on TC connections when using the on-line builder for
FAT and commissioning.
Give the TC the highest item number. This will simplify the exchange of the TC if required.
Refer to section 4.4 Typical PC structure for details of PC element numbering proposals.
FUNCM
MOVE (B)
TC
MOVE (R)
MOVE (B)
MOVE (R)
MOVE (T)

6.6 Deleting Database elements On-Line
Never use the DDB command to delete a database element. Unpredictable behaviour of the
controller can result after using this command.
If database objects need to be deleted, rename it to indicate it is spare, delete any references to it
from the Operator Station/s reference list. Then delete it when possible using the FCB (i.e. off-line).
It is possible to create a naming convention for spare to be deleted objects, however this should
not be required, J ust rename them to the Advant default name for unused objects eg:
DIEV11
DIC234
AI1.1
etc.


6.7 TTDLogs & TTDVars and Renumbering Database Elements
Once signals names have been entered into TTDVars in the database (either by SASAK or
manually from the Operator Station), Never renumber any of the following database elements:
AIC
AOC
AOS
MANSTN
PIDCON
PIDCONA
DIC (if used in TTDvars)
DIS (if used in TTDvars)
Contiguous Database element Numbering:
The following database elements must have contiguous numbers (i.e. the first element must be 1
and there must not be any gaps).
DS
DSP
MS
PIDCONA
This is one more reason to be careful when deleting database elements.
If DataSets (DS) are used:
DAT1 must exist
At system startup, there is a check if DAT1 exist. If not, the DS communication task (CXAA000) is
not started.

6.8 PC program Names:
For FCB versions which support this feature, it is recommended to identify each PC program with
an applicable "Instance Name" (description).

The name can be entered on creation or, from the ODB window by selecting the program and
pressing the F5 key.
6.9 Setpoints Common to multiple PC programs
PC specific setpoints which should not be manipulated by operators should be defined via a MOVE
at the top of the PC program in which they are used. (Note: Measurement Units must be clearly
entered with the value). The signal/s at the output of the MOVE must be given names equal to the
setpoint ID in the PFuP.


Where the setpoint list covers all PC programs it is recommended to have a single location for
changing setpoints. Such setpoints should be defined in a specific PC program (eg PC5) again via
a MOVE but with an output to an AOC having PROC_SECtion set to -1 to hide it from the operator.
Only the following terminals need to be defined in the AOC: NAME, DESCR, UNITS, PROC_SEC

6.10 Hardware Dimensioning
The Database of the AC450 can be dimensioned using the values shown at the bottom of the BAX
source code file generated by the Function Chart Builder (these values are the quantities actually
required without any spare). A quantity of spare must be added to these quantities.
It is strongly recommended to have a lot of spare (at least 25 % is recommended) to avoid any
future redimensioning.
Always dimension for a minimum of 10 DataSets (DS) plus the associated 240 DATs
The BAX file does not show how many AF100 Stations are required. This parameter must
be set to the same value as AF100 Fieldbuses for GT and ST Nodes (2 are required,
normally set to 4)
Always dimension a minimum of 2 MVI-Modules (Modbus)
Size of Data Tables: 2kB (not necessarily needed, can be 0kB)
Number of File Elements: 13 (used for APC)
Size of file Data: 200kB (used for APC)
After DIM command:
Spare Area 2kb. In older Advant systems (Masterpiece) there was some uncertainty about
the amount of memory required during initialisation (DICONFIG) of database elements and
they took up more memory than "normally" required. The spare area setting was used to
compensate for this. AC450 systems have supposedly solved this problem and in principle
the spare area can now be set to zero in AC450 systems but a setting of 2kB is
recommended - just in case
Size of PC Program Tables: 2000kB
Number of scan places interpreter A: 200, Interpreter B: 200, Interpreter C: 400
Size of user Disk Area: 1500kB (Disk size on ES for Document texts, PC programs)
MSTABS symbol Table size: 400 (for Variables and Names)


7. Tips and Tricks for AC160 planning
7.1 REG-G-UT
In order to reduce past value traffic to the redundant bus, REG-G-UT should be used in place of
REG-G when the inputs are constants (normal case). Note: This element is not described in the
current DB/PC reference manuals.
7.2 I/O Cards used by multiple CPUs in the same station
All I/O cards which are configured to produce SOE (Sequence Of Events) must NOT be used by
(configured in) multiple CPUs (Configured means IMPL=1).
DP640
DI65x (If it is configured for sequence of event i.e. MODE=SOE )
For other I/O cards which are configured by multiple CPUs, the configuration of ALL channels must
be identical in each CPU (database). This prevents multiple CPUs which access the card from
cyclically re-configuring the card if the card settings in CPUs differ.
It is not necessary and not desirable to configure non-shared I/O cards in any other CPUs which
share the I/O bus.
7.3 MOVE-RED
In order that Tail-biting logic functions correctly in AC160 with Redundant CPUs it is necessary to
use MOVE-RED instead of MOVE.

7.4 Integrator
When the upper limit is set to be less than the lower limit, the Integrator will go into disturbance.
This can be overcome by running both limit signals through a MIN element and using this as the
lower limit and over a MAX element for the Upper Limit. Refer also to section 7.5 CONTRM cycle
time: On-Line changes

7.5 CONTRM cycle time: On-Line changes
When the cycle time of a CONTRM containing an INTEGRATOR is changed on-line (with SAVE &
LOAD command), then the integrator will not operate correctly. To avoid this, leave the on-line
mode, generate target code and perform a complete new download.

7.6 Deleting Type Circuits
When a Type circuit which generates DATs is deleted then the DATs are also deleted. If these
DATs are directly connected to a DSP then all the connections are deleted and all the following
signals on the DSP slide down to fill the gap. This completely messes up the communication and
requires that the DSP is changed by hand on the other side.
To avoid the slide rename the DATs before deleting the Type circuit.

7.7 Changing DSP parameters on-line
In AC160 it is possible to change the number of inputs/outputs on-line without restarting the node.
In AC450 a Cold Start is required after performing such changes.


7.8 SYSDIAG (System Diagnosis)
This TC supervises amongst other things the heartbeat of another CPU. However it only reacts to
the +ve flank and therefore only half of the information is evaluated. The TC SYSDIAG2 solves this
problem. SYSDIAG3 has the same functionality as SYSDIAG2 but only PC-Elements that comply
with SILx.
7.9 Missing values during debugging ( x )
If during debugging, values are only displayed with an x then the CPU does not find them. This
has various causes.
The PC program is Blocked
The CONTRM is not running (Pin ON must have a 1 or database connection with value
1 connected.
7.10 Calculation of SPDGRD (for RSM)

Calculation of SPDGRD:
Assuming number of teeth is: 132
Then: SPDGRD should be 1,5* (( 1/132) /20ms)*60 =34.090 rpm
(where 20ms =CONTRM cycle time)
CONTRM cycle time:
This must be set so that a cycle corresponds to a multiple of the time of a full rotation (Tr) e.g.:
50 Hz machine: 1000ms/50Hz gives Tr=20ms. Therefore 20ms, 40ms, 60ms, 80 ms
CONTRMs can be used.
60 Hz machine: 1000ms/60Hz gives Tr=16.666ms. Therefore 50ms, 100ms CONTRMs
can be used (3x or 6x Tr).
7.11 DIC Scantime
The SCANTIME setting of DICs has a huge affect on system load. If a single DIC is set to a fast
scantime, then the EVENTSET task runs at this speed also. As an example: a scantime of 640ms
instead of 80ms can reduce the CPU load by approx. 20% (on a PM645) depending on the quantity
of EVS's used.


7.12 Usage of ERR Terminal of DB-Element DI651X
To avoid a DI651 card disturbance alarm in case of a time jitter, the :ERR terminal of the DI651
should not be used for alarming the card disturbance.
The normally used :ERR terminal for card disturbance is replaced by an OR-gate with the
terminals SPE_ERR and SDE_ERR.
The SOE_ERR of every DI-Card is collected on one TIME SYNC ALARM.

OR
DI1:SPE_ERR (Process Error)
DI1:SDE_ERR (Device Error)
11CRC20BB013_XM01 (DI651 I/O-CARD DIST)
OR
DI1:SSE_ERR (SOE Error)
CRC20BA000_XU54 (DI651 TIME SYNC ALARM)

To use this functionality following requirements have to be fulfilled:
CBA 1.2/1 bzw. FCB 6.2/1
Base Software AC160 2.2/1
Option "DI65x for ProtSyst" (this option generates the new DI651X and DIS651X DB-
elements)
Only DI651 PR >=G use this functionality (older revisions will show the terminals but will
not use them)
The same is applicable for DI650 and DI652 Cards.
7.13 Checks required after Generate Target Code
After Generate Target Code has been succesfully performed check that the following limits are not
exceeded:
Unplanned Tracking: <=5 kbyte (per CONTRM or MASTER)
Total Unplanned Tracking: <=32 kbyte (sum of all CONTRMs and MASTERs)


8. Tips & Tricks: General
8.1 SI-ANSI Conversion parameters
SI Unit Factor Offset ANSI Unit
cal 4.1868 0 J
kcal 4.1868 0 kJ
bar 14.5038 0 psi
mbar 0.40146 0 inWC
bara 14.5038 0 psia
mbara 0.02992 0 inHG
barg 14.5038 0 psig
Rmbar 1 0 Rmbar
kg/s 2.20462 0 lb/s
kg/h 2.20462 0 lb/h
m3/h 35.3147 0 cfh
l/s 0.2642 0 gal/s
sm3/h 0.58858 0 scfm
m3/h 0.58858 0 cfm
g 15.4324 0 gr
kg 2.20462 0 lb
mm 0.03937 0 in
m 3.28084 0 ft
um 0.03937 0 mil
umpp 0.03937 0 milpp
l 0.03531 0 ft3
m3 35.31466 0 ft3
mm/s 39.37 0 mils/s
mm/s2 39.37 0 mil/s2
Hz 1 0 Hz
1/min 1 0 rpm
1/min2 1 0 rpmm
W 1 0 W
kW 1 0 kW
MW 1 0 MW
MVA 1 0 MVA
MVAr 1 0 MVAr
% 1 0 %
mV 1 0 mV
V 1 0 V
kV 1 0 kV
mA 1 0 mA
A 1 0 A
kA 1 0 kA
deg 1 0 deg
uS/cm 2.54 0 uS/in
ug/kg 7 0 ugr/lb
ppmvd 1 0 ppmvd
degC 1.8 32 degF



8.2 Source Code Naming convention
Source codes (*.aax and *.bax files) are named using the scheme nnmd :
Where the first two letters (nn) represent the node identification:
Code Node Remark
C1 Closed Loop Controller 1
C2 Closed Loop Controller 2
If 2 Closed Loop Controllers present (eg
GT)
CL Closed Loop Controller If 1 Closed Loop Controller present (eg ST)
O1 Open Loop Controller 1
O2 Open Loop Controller 2
If 2 Open Loop Controllers present (eg GT)
OL Open Loop Controller If 1 Open Loop Controller present (eg ST)
P1 Protection 1
P2 Protection 2
P3 Protection 3
nn AC450 node nn

The next two characters code the month and the day.
Month Code Month

Day Code Day

1 J anuary 1 1
2 February 2 2
3 March 3 3
4 April 4 4
5 May 5 5
6 J une 6 6
7 J uly 7 7
8 August 8 8
9 September 9 9
A October A 10
B November B 11
C December C 12
D 13
E 14
F 15
G 16
H 17
I Not used
J 18
K 19
L 20
M 21
N 22
O 23
P 24
Q 25
R 26
S 27
T 28
U 29
V 30
W 31


8.3 Time Synchronisation
8.3.1 AC450 Systems and AC450/AC160 Systems
On the OS500 or Connectivity Server which is Time Master, the time has to be set via Date and
Time settings on OS500 or Windows Time on PPA Systems. When the next minute pulse on one of
the clock master nodes is recognised, all nodes will get the time-telegram of the time master. Be
sure to set the time to the next full minute (.00 seconds). You should have at least two AC450
nodes with minute pulse. They have to be set as clock master (CLK_MAST =1). That means that
each of this Nodes is allowed to be clock master. The system defines by itself which is master,
normally the lowest Node-number which has CLK_MAST=1. If there is an AC160 Station
connected with AF100, no change in the AC450 CLS is required. In the CI522-Cardsetting
(AF100_1 DB-element), TIMESYNC =1 must be set. In the AC160 all PM6xx TSYNC=NO and on
all CI6xx TIMESINC=SLAVE must be set. CI631 to S800 I/O-stations need TIMESYNC=MASTER!

OS500 or CS
Time Master

CLS Setting:
CLK_MAST =0
LOC_TIME =3
CLK_SEND =1
OS500 or PPA

CLS Setting:
CLK_MAST =0
LOC_TIME =3
CLK_SEND:=0
AC450
Clock Master

CLS Setting:
CLK_MAST =1
LOC_TIME =1
CLK_SEND =1
AC450
Backup Clk Mstr

CLS Setting:
CLK_MAST =1
LOC_TIME =1
CLK_SEND =1
AC450
AF100 Setting:
TIMESYNC=1
CLS Setting:
CLK_MAST =0
LOC_TIME =3
CLK_SEND =0
AC160 RACK

PM6xx:
TSYNC =NO
EXT_CLK=NO

CI6xx:
TIMESYNC=SLAVE
AC160 RACK

PM6xx:
TSYNC =NO
EXT_CLK=NO

CI6xx:
TIMESYNC=SLAVE
AC160 RACK

PM6xx:
TSYNC =NO
EXT_CLK=NO

CI6xx:
TIMESYNC=SLAVE

CI631 to S800:
TIMESYNC=MASTER
Master Clock
Minute Pulse
MB300
AF100
S800 I/O Station

CI820:
EXT_TIME =YES
TIM_SYNC=SLAVE
AF100

8.3.2 AC160 Systems
On the PM with minute pulse connected, Time Sync has to be activated (TSYNC =YES). On this
AC160 Station the CI6xx (both if redundant) has to be set as timesync-master (TIMESYNC =
MASTER). All other PM must be set to TSYNC=NO and all other CI6xx to TIMESYNC=SLAVE.
The time has to be set on the PM which is time-master via the ES to the next full minute (00
seconds). On the next pulse all stations will be synchronised. It is also possible to set the time on a
OS160 with the GPS-tool.
AC160OS or
PPA AC100Connect

CIxxx:
TIMESYNC=SLAVE
AC160 RACK
Time Master
PM6xx:
TSYNC =YES
EXT_CLK=NO

CI6xx:
TIMESYNC=MASTER
AC160 RACK

PM6xx:
TSYNC =NO
EXT_CLK=NO

CI6xx:
TIMESYNC=SLAVE
AC160 RACK

PM6xx:
TSYNC =NO
EXT_CLK=NO

CI6xx:
TIMESYNC=SLAVE
Master Clock
Minute Pulse
AF100
AC160OS or
PPA AC100Connect

CIxxx:
TIMESYNC=SLAVE



8.4 Swapping PC Elements
If the output of a PC element is connected to multiple destinations the easiest method for copying
this to a new element is as follows:
Add the new PC element, select the old element output and in PC-Terminal connect dialog box
Cut the data. Then paste it into the output of the new element.
8.5 Editing TIX files
The TIX files must not be edited using the AdvaBuild editor (HIGHCVPP:EXE) because the High-
ASCII characters will be lost. Use MS WORD with the "Show-All characters selected and be
careful not to delete the Square (non-displayable characters.)
Best is to use NOTEPAD.
When backtranslating source files the .TIX file must have the same name as the .AAX file.
8.6 Modbus communiction Error signal handling
Error handling of modbus interfaces must be configured in a similar way to that of the AC160-
AC450 signal transfer error handling (Attachment 2). i.e. the error of an analog signal is alarmed
via a DIC, This signal together with modbus "PLC not alive" signal is connected to the ERR pin of
the Analog value (AIC) to provide error indication to the operator.
Analog-Signal Error
OR
CONV-IB
AIC:ERR (XQ60)
modbus data
DAT(IL)
DIC (XQ63)
(PLC ALIVE)
Bit1 of Modbus Status word

8.7 Profibus setup for FCB
To setup a Profibus connection, do the following steps.
You need the GSD-file. Save it /Proj/Nodes/OLC2/List.
Check if C:\pb_lib is empty.If not, delete all files in it.

Open the Program Profibus Library Editor (under Programs//CBA/Utilities/).
File ->New. Select preferred Mode, normally Optimized for AC100.
Save (in C:/pb_lib).
Edit ->Create ->from GSD ->browse your gsd-file ->OK ->OK. You see now your
modules.
Actions ->Generate DED for AC100 ->Select target type, checkmark Compile ->OK

Open your node with FCB, the new Elements should now be there. (e.g. PBS1, PB1, AXPB1)
This has to be done on every ES you want to open the FCB with the Profibus node.



9. Attachments

Attachment 1: Analogue Signal Error Handling AC450 to AC160.....................................58
Attachment 2: Analogue Signal Error Handling AC160 to AC450.....................................59
Attachment 3: Communication Routes between AC160 Nodes ........................................60
Attachment 4: AC450 Node to Node Interface (Typical)....................................................61
Attachment 5: AC450 Node to Node DS naming convention............................................62
Attachment 6: AC450 Node to Node Analogue Signal Error Handling..............................63
Attachment 7: AC450 Transmitter and Wire-Break Supervision........................................64
Attachment 8: AC160 MECO for S600..............................................................................65
Attachment 9: AC160 MECO for AI810.............................................................................66
Attachment 10: AC160 MECO for AI830...........................................................................67
Attachment 11: AC160 MECO for AI835...........................................................................68
Attachment 12: Analogue Limits for Hardware I/Os in AC450...........................................69
Attachment 13: 2oo3 Analogue signal and alarm handling...............................................70
Attachment 14: 2oo3 TRIP Signal Handling FC2 (AC450)................................................71
Attachment 15: 2oo3 TRIP Signal Handling (Signal from AC160, Logic in AC450) ..........72
Attachment 16: 1oo2 TRIP Signal Handling (AC450)........................................................73
Attachment 17: 1oo1TRIP Alarms and Events (AC160)....................................................74
Attachment 18: 1oo2 PLS/PLST/TRIP Signal Handling (AC160)......................................75
Attachment 19: 1oo2 ST-TRIP with relation to CLC (AC160)............................................76
Attachment 20: 2oo3 PLS/PLST/TRIP Alarms (AC160)....................................................77
Attachment 21: 2oo3 TRIP Signal Handling (Hardwired between AC160's) .....................78
Attachment 22: Signal Redundancy Guidelines part 1......................................................79
Attachment 23: Signal Redundancy Guidelines part 2......................................................80
Attachment 24: Controller Release Logic ..........................................................................81
Attachment 25: Controller Interlocks & Indication..............................................................82
Attachment 26: Manual Station as SetPoint Station..........................................................83
Attachment 27: Controller Direct / Reverse Action & Fail-Safe..........................................84
Attachment 28: Controller Limitation..................................................................................85
Attachment 29: System Diagnosis AC160 Alarms/Events.................................................86
Attachment 30: MVI settings for standard Modbus configuration......................................87
Attachment 31: MS settings for standard Modbus configuration (Vibration Monitor).........88
Attachment 32: MS settings for standard Modbus configuration (SSD/AVR) ....................89
Attachment 33: MS settings for standard Modbus configuration (DCS) ............................90
Attachment 34: Modbus PC-Program settings (Line, Network).........................................91
Attachment 35: Modbus PC-Program settings (Registers)................................................92
Attachment 36: Modbus PC-Program settings (flow control).............................................93
Attachment 37: CI513 DIP-Switch settings for MB300......................................................94


FILE: 1AHL102709r6_DesignRules_Rev6.doc; TEMPLATE: Techn_Doc_Stand_P.dot A; SKELETON: ; SAVEDATE: 6/2/2006 11:42:00 AM
9.1 Attachment 1: Analogue Signal Error Handling AC450 to AC160

Attachment 1: Analogue Signal Error Handling AC450 to AC160


9.2 Attachment 2: Analogue Signal Error Handling AC160 to AC450

Attachment 2: Analogue Signal Error Handling AC160 to AC450


9.3 Attachment 3: Communication Routes between AC160 Nodes

Attachment 3: Communication Routes between AC160 Nodes


9.4 Attachment 4: AC450 Node to Node Interface (Typical)

Attachment 4: AC450 Node to Node Interface (Typical)


9.5 Attachment 5: AC450 Node to Node DS naming convention

Attachment 5: AC450 Node to Node DS naming convention


9.6 Attachment 6: AC450 Node to Node Analogue Signal Error Handling

Attachment 6: AC450 Node to Node Analogue Signal Error Handling



9.7 Attachment 7: AC450 Transmitter and Wire-Break Supervision

Attachment 7: AC450 Transmitter and Wire-Break Supervision


9.8 Attachment 8: AC160 MECO for S600

Attachment 8: AC160 MECO for S600


9.9 Attachment 9: AC160 MECO for AI810

Attachment 9: AC160 MECO for AI810
Note: Set DEADB to -1




Note:
1) Only :ERR Terminal is used for BDQ
2) No LINSCAL is needed. Range is defined by RTD-element type (e.g. CONV_PAR=Pt100,850C). The AIC Range (DISPMIN, DISPMAX) on AC450 is set to the Adjusted
Range (noted in Instrumentation List) not the whole thermoelement range
3) Set DEADB to -1



N,C measurement (-270..1300degC)

Pt100 Compensation measurement on channel 8

Note:
1) for BDQ the :ERR Terminal of the Thermocouple and :ERR of the Pt100 compensation measurement (normally located at channel 8 of the card).
2) No LINSCAL is needed. Range is defined by Thermocouple-type (e.g. TC_TYPE=N,C has -270degC1300degC). The AIC Range (DISPMIN, DISPMAX) on AC450 is
set to the Adjusted Range (noted in Instrumentation List) not the whole thermocouple range
3) Set DEADB to -1


9.12 Attachment 12: Analogue Limits for Hardware I/Os in AC450

Attachment 12: Analogue Limits for Hardware I/Os in AC450
Notes:1: Do not use the inverse signal outputs of the Comparator - It is possible to get pin 20 and 21 or 40 and 41 High at the same time
2: Blocking of the Limit signals must be defined on a per project basis (Advant generally stays at last good state i.e. freezes existing signal level on signal error)
3: The 1oo2 or 2oo3 AIC limits are only for display use (HMI). Do not use them for any switching functions. The DICs of the 2 or 3 separate signal limits must be used.
4: Only write to the 1oo2 or 2oo3 AIC Limits from the 1
st
source signal.


9.13 Attachment 13: 2oo3 Analogue signal and alarm handling

Attachment 13: 2oo3 Analogue signal and alarm handling
Notes:
- XJ 63: 2oo3 Sensors disturbed or drift, Event Treatment 219 (FAILURE). Description: ...2o3 (e.g. P LPT EXHAUST 2o3).
- XJ 64: 1oo3 Sensors disturbed or drift, Event Treatment 215 (SEN UNEQ).
- For FC2 Trip logic and channel alarming is done in AC450 according Attachment 14: 2oo3 TRIP Signal Handling FC2 (AC450).
- For FC1 Trip logic and channel alarming is done in AC160 protection channels according Attachment 20: 2oo3 PLS/PLST/TRIP Alarms (AC160).


9.14 Attachment 14: 2oo3 TRIP Signal Handling FC2 (AC450)

Attachment 14: 2oo3 TRIP Signal Handling FC2 (AC450)


9.15 Attachment 15: 2oo3 TRIP Signal Handling (Signal from AC160, Logic in AC450)

Attachment 15: 2oo3 TRIP Signal Handling (Signal from AC160, Logic in AC450)


9.16 Attachment 16: 1oo2 TRIP Signal Handling (AC450)

Attachment 16: 1oo2 TRIP Signal Handling (AC450)


9.17 Attachment 17: 1oo1TRIP Alarms and Events (AC160)

Attachment 17: 1oo1TRIP Alarms and Events (AC160)


9.18 Attachment 18: 1oo2 PLS/PLST/TRIP Signal Handling (AC160)

Attachment 18: 1oo2 PLS/PLST/TRIP Signal Handling (AC160)


9.19 Attachment 19: 1oo2 ST-TRIP with relation to CLC (AC160)

Attachment 19: 1oo2 ST-TRIP with relation to CLC (AC160)


9.20 Attachment 20: 2oo3 PLS/PLST/TRIP Alarms (AC160)

Attachment 20: 2oo3 PLS/PLST/TRIP Alarms (AC160)


9.21 Attachment 21: 2oo3 TRIP Signal Handling (Hardwired between AC160's)

Attachment 21: 2oo3 TRIP Signal Handling (Hardwired between AC160's)


9.22 Attachment 22: Signal Redundancy Guidelines part 1

Attachment 22: Signal Redundancy Guidelines part 1


9.23 Attachment 23: Signal Redundancy Guidelines part 2

Attachment 23: Signal Redundancy Guidelines part 2


9.24 Attachment 24: Controller Release Logic

Attachment 24: Controller Release Logic


9.25 Attachment 25: Controller Interlocks & Indication

Attachment 25: Controller Interlocks & Indication


9.26 Attachment 26: Manual Station as SetPoint Station

Attachment 26: Manual Station as SetPoint Station


9.27 Attachment 27: Controller Direct / Reverse Action & Fail-Safe

Attachment 27: Controller Direct / Reverse Action & Fail-Safe


9.28 Attachment 28: Controller Limitation

Attachment 28: Controller Limitation


9.29 Attachment 29: System Diagnosis AC160 Alarms/Events
KKS (example) DESCRIPTION STATUS EVENT NORM Remark KKS (example) DESCRIPTION STATUS EVENT NORM Remark
AC160 CPU Diagnosis POS HSL Diagnosis POS
CRC30BA003_XM01 PM665 MODULE DIST 216 0 CRC30BA008_XU06 HSL ST10 SEND ALARM 227 0
CRC30BA003_XM11 CLC1 CPU1 DEFECT ALARM 227 0 CRC30BA008_XU21 HSL ST20 TO ST10 ALARM 227 0
CRC30BA003_XM12 CLC1 CPU1 INIT ALARM 227 0 CRC30BA008_XU31 HSL ST30 TO ST10 ALARM 227 0
CRC30BA003_XM13 CLC1 CPU1 MASTER ACTIVE 249 0 CRC40BA008_XU06 HSL ST20 SEND ALARM 227 0
CRC30BA003_XM14 CLC1 CPU1 TOOL ALARM 227 0 CRC40BA008_XU12 HSL ST10 TO ST20 ALARM 227 0
CRC30BA003_XM21 CLC1 CPU2 DEFECT ALARM 227 0 CRC40BA008_XU32 HSL ST30 TO ST20 ALARM 227 0
CRC30BA003_XM22 CLC1 CPU2 INIT ALARM 227 0 Only for Redundant CRC50BA008_XU06 HSL ST30 SEND ALARM 227 0
CRC30BA003_XM23 CLC1 CPU2 MASTER ACTIVE 249 0 Only for Redundant CRC50BA108_XU13 HSL ST10 TO ST30 ALARM 227 0 (att.: BA108_XU13)
CRC30BA003_XM24 CLC1 CPU2 TOOL ALARM 227 0 Only for Redundant CRC50BA008_XU23 HSL ST20 TO ST30 ALARM 227 0
CRC30BA003_XM02 CLC1 CPU ERROR ALARM 227 0
CRC30BA003_XM03 CLC1 CPU HIGH LOAD ALARM 227 0 Cubicle Diagnosis
CRC30BA003_XM05 CLC1 CPU OVERLOAD ALARM 227 0 CRC20DB001_XG01 24VDC CTRL MCBS DIST 218 0
CRC30BA003_XU01 CLC1 CPU RUNNING ALARM 227 1 CRC20GB001_XG01 24VDC CONVERTER DIST 216 1
CRC30BA003_XU13 CLC1 HARDWARE ERROR ALARM 227 0 CRC60J A002_XG01 24VDC CONVERTER DIST 216 1
CRC30BA003_XU14 CLC1 I/O FAIL ALARM 227 0 CRC60J A001_XG01 48VDC CONVERTER DIST 216 1
CRC30BA003_XU15 CLC1 I/O PROC FAIL ALARM 227 0 CRC60J A001_XG01 P&F SPLY FAILURE 219 0
CRC30BA003_XU16 CLC1 I/O APPLIC ERR ALARM 227 0 CRC60J C001_XG01 P&F AMPL ALARM 227 0

AC160 Card Diagnosis Hopf Master Clock
CRC30BA001_XM01 ST10 CI630 COM CARD DIST 216 0 CYF10EG001_XG01 MASTER CLOCK SYS DIST 216 1
CRC30BA002_XM01 ST10 CI630 COM CARD DIST 216 0 CYF10EG002_XG01 CLOCK NOT RADIO CTRL ALARM 227 1
CRC30BA007_XM01 ST10 DP640 SPD CARD DIST 216 0
CRC30BA009_XM01 ST10 CI615 COM CARD DIST 216 0 Bentl y Nevada
CRC30BA010_XM01 ST10 CI615 COM CARD DIST 216 0 MBA30CY001_XQ63 KEYPHASOR DIST 216 0
CRC30GA009_XM01 ST10 DO620 I/O-CARD DIST 216 0 MBD00CY000_XU01 BENTLY RIM RACK DIST 216 0
CRC30BB012_XM01 ST10 AI625 I/O-CARD DIST 216 0 MBD00CY000_XU02 BENTLY UPPER PWRSPLY DIST 216 0
MBD00CY000_XU03 BENTLY LOWER PWRSPLY DIST 216 0
Communication Diag MBD00CY000_XU04 BENTLY RIM MODULE DIST 216 0
CRC30BA008_XU51 DSP TO PROT1 ALARM 227 1 MBD00CY000_XU05 BENTLY RELAY CH1 ACTIVE 249 0 Not shown in DiagDispl
CRC40BA008_XU51 DSP TO PROT2 ALARM 227 1 MBD00CY000_XU06 BENTLY RELAY MODULE1 DIST 216 0
CRC50BA008_XU51 DSP TO PROT3 ALARM 227 1 MBD00CY000_XU07 BENTLY RELAY CH2 ACTIVE 249 0 Not shown in DiagDisp
CRC40BA003_XU51 DSP TO OLC ALARM 227 1 MBD00CY000_XU08 BENTLY RELAY MODULE2 DIST 216 0
CRC30BA003_XU51 DSP TO CLC1 ALARM 227 1 MBD00CY000_XU09 BENTLY KEYPHAS MODUL DIST 216 0
CRC30BA005_XU51 DSP TO CLC2 ALARM 227 1 MBD00CY000_XU10 BENTLY MODBUS MODUL DIST 216 0
CRC20BA000_XU51 DSP AC160 TO AC450 ALARM 227 1 MBD00CY000_XU11 MODBUS AC450-BENTLY DIST 216 0
CRC20BA000_XU02 EVS AC160 TO AC450 ALARM 227 0 MBD00CY000_XU12 BENTLY TRIP MULTIPLY ON 243 0 Feedback from Bently
CRC20BA000_XU53 DS TO NODE xx ALARM 227 0 MBD00CY361_XU01 VIBR THRES MULTIPLY DIST 216 0
CRC20BA000_XU54 DI651 TIME SYNC ALARM 227 0 TimeJ itter supervis MBD00CY361_XU02 VIBR MONITORING DIST ACTIVE 249 0
MBD00CY361_XU03 VIBR THRES SENSITIVE ACTIVE 249 0 Command to Bently
MBD00CY361_XU04 VIB THRES INSENSITIV ACTIVE 249 0 Inverse of _XU03
Attachment 29: System Diagnosis AC160 Alarms/Events


9.30 Attachment 30: MVI settings for standard Modbus configuration
V1: Vibration Mon. (singl e)
Config MS: Net=7, Node=-3
ID=17
Data MS: Net=1, Node=1
T1: DCS link (redundant)
ID=17
U1: SSD/AVR (redundant)
ID=1117
T2: DCS link (redundant)
ID=17
No Data MS for 2
nd
redundant
M
B
3
0
0

C
I
5
1
3

A
F
1
0
0

C
I
5
2
2

Pos4
M
B
3
0
0

C
I
5
1
3

A
F
1
0
0

C
I
5
2
2

Pos5
C
I
5
3
2

C
I
5
3
2

Pos6
U2: SSD/AVR (redundant)
ID=1117
No Data MS for 2
nd
redundant
M
V
I
3
:

N
e
t
1
=
5
,

N
e
t
2
=
6

Pos3
SYS
SW
C
I
5
3
2

M
V
I
2
:

N
e
t
1
=
3

N
e
t
2
=
4

M
V
I
1
:

N
e
t
1
=
1

N
e
t
2
=
0

Standard AC450 configuration Egatrol
Pos1
Pos7 Pos2
Net number of Config-MS (xy_INIT, xy_NETW, xy_STAT,
xy_REG) must be 7 for MVI1, 8 for MVI2 and 9 for MVI3.
Do not renumber the MVIs!
Node number for the config-MS must be -3.
Ident number of the config-MS of the upper ports must
be 1 to 7, of the lower ports 11 to 17.
Net Number of the Cmd- and Data-MS have to be the
same as in the corresponding MVI (first of redundant):
VIB: Net 1, Node 1
SSD: Net 4, Node 2
DCS: Net 3, Node 3
All sending MS must be blocked
The MVI-terminal SET_NETx is to enable the port. e.g 1
=enabled. If it is not enabled set also Net to 0 (see MVI1
Bently).
Cmd-MS have Ident 203 or 204 for read, 216 for write.
203 means read-adresses 4xxxxx, 204 ->3xxxx, 216
means write-addresses 4xxxx. They must be the same
in the flow-control PC-Elements.
If no DC-link is used, connect the Vibration Mon. to MVI2
upper port. Do not renumber the MVIs if you delete
MVI1. Best is to leave MVI1 in, only set IMPL to 0! All MS
for DCS (Tx_xxx..) can be deleted.
DCS-Nodes (e.g. ST) which use only one Modbus to
Vibration Monitor use only MVI1 (Pos.6, Subpos.1), all
other MVI can be deleted. Only the Vib. MS are used.

Standard configuration with single Vibration Monitor, redundant SFC/AVR and redundant DCS-Link
CI532 NAME POSITION SUBPOS IMPL SERVICE TYPE VARIANT NODE CONSOLE NET1 SET_NET1 NET2 SET_NET2
MVI1 MVI1_VIBRATION 6 1 1 1 CI532 V02 OFF 1 1 0 0
MVI2 MVI2_DCS-SSD\AVR 6 2 1 1 CI532 V02 OFF 3 1 4 1
MVI3 MVI3_DCS-SSD\AVR 3 2 1 1 CI532 V02 OFF 5 1 6 1

Standard configuration with single Vibration Monitor and redundant SFC/AVR
MVI1 MVI1_DUMMY 6 1 0 0 CI532 V02 OFF 0 0 0 0
MVI2 MVI2_VIB-SSD\AVR 6 2 1 1 CI532 V02 OFF 1 1 4 1
MVI3 MVI3_SSD\AVR 3 2 1 1 CI532 V02 OFF 0 0 6 1

Standard configuration for ST (onl y single Vibration Monitor link)
MVI1 MVI1_VIBRATION 6 1 1 0 CI532 V02 OFF 1 1 0 0
Attachment 30: MVI settings for standard Modbus configuration


9.31 Attachment 31: MS settings for standard Modbus configuration (Vibration Monitor)

MS NAME ACT IDENT NO_BREC NO_INT NO_INTL NO_REAL USER SOURCE BLKD NET NODE SCAN SORT REF1 ... REF8 REF9 ... REF24
MS1 V1_INIT 1 1 0 0 14 0 3 SEND 1 7 -3 1 YES V1_INIT.IL1 ... ... ... V1_INIT.IL14
MS2 V1_NETW 1 2 0 0 24 0 3 SEND 1 7 -3 1 YES V1_NETW.IL1 ... ... ... ... V1_NETW.IL24
MS3 V1_STAT 1 3 8 0 16 0 3 RECEIVE 0 7 -3 1 YES V1_STAT.B1 ... ... ... ... V1_STAT.IL16
MS4 V1_REG 1 4 0 0 24 0 3 SEND 1 7 -3 1 YES V1_REG.IL1 ... V1_REG.IL8 V1_REG.IL9 ... V1_REG.IL24
MS5 V1_CMD_R 1 203 0 0 2 0 3 SEND 1 1 1 1 YES V1_CMD_R.IL1V1_CMD_R.IL2
MS6 V1_DAT1_S 1 1 0 24 0 0 3 SEND 1 1 1 1 YES V1_DAT1.I1 ... ... ... ... V1_DAT1.I24
MS7 V1_DAT1_R 1 101 0 24 0 0 3 RECEIVE 0 1 1 1 YES V1_DAT1.I1 ... ... ... ... V1_DAT1.I24
Attachment 31: MS settings for standard Modbus configuration (Vibration Monitor)
Note: If No DCS-Link is connected and Vibration Monitor is connected on MVI2 (Pos. 6, Subpos. 2, upper port, (Egatrol without DCS-Link)), set NET of the
Config-MS from 7 to 8!
Note: For ST-link to Vibration Monitor only MVI1 (Pos. 6, Subpos. 1, upper port) is used. Leave all settings as shown here.



9.32 Attachment 32: MS settings for standard Modbus configuration (SSD/AVR)

MS NAME ACT IDENT NO_BREC NO_INT NO_INTL NO_REAL USER SOURCE BLCK NET NODE SCAN SORT REF1 ... REF8 REF9 ... REF24
MS*1 U1_INIT 1 11 0 0 14 0 3 SEND 1 8 -3 1 YES U1_INIT.IL1 ... ... ... U1_INIT.IL14
MS*2 U1_NETW 1 12 0 0 24 0 3 SEND 1 8 -3 1 YES U1_NETW.IL1 ... ... ... ... U1_NETW.IL24
MS*3 U1_REG1 1 13 0 0 24 0 3 SEND 1 8 -3 1 YES U1_REG1.IL1 ... ... ... ... U1_REG1.IL24
MS*4 U1_STAT 1 14 8 0 16 0 3 RECEIVE 0 8 -3 1 YES U1_STAT.B1 ... U1_STAT.B8 U1_STAT.IL1 ... U1_STAT.IL16
MS*5 U1_CMD_R 1 203 0 0 2 0 3 SEND 1 4 2 1 YES U1_CMD_R.IL1 U1_CMD_R.IL2
MS*6 U1_CMD_S 1 216 0 0 2 0 3 SEND 1 4 2 1 YES U1_CMD_S.IL1 U1_CMD_S.IL2
MS*7 U2_INIT 1 11 0 0 14 0 3 SEND 1 9 -3 1 YES U2_INIT.IL1 ... ... ... U2_INIT.IL14
MS*8 U2_NETW 1 12 0 0 24 0 3 SEND 1 9 -3 1 YES U2_NETW.IL1 ... ... ... ... U2_NETW.IL24
MS*9 U2_REG1 1 13 0 0 24 0 3 SEND 1 9 -3 1 YES U2_REG1.IL1 ... ... ... ... U2_REG1.IL24
MS*10 U2_STAT 1 14 8 0 16 0 3 RECEIVE 0 9 -3 1 YES U2_STAT.B1 ... U2_STAT.B8 U2_STAT.IL1 ... U2_STAT.IL16
MS*11 U1_DATA1_R 1 101 0 24 0 0 3 RECEIVE 0 4 2 1 YES U1_DATA1.I1 ... ... ... ... U1_DATA1.I24
MS*12 U1_DATA1_S 1 1 0 24 0 0 3 SEND 1 4 2 1 YES U1_DATA1.I1 ... ... ... ... U1_DATA1.I24
MS*13 U1_DATA2_R 1 102 0 24 0 0 3 RECEIVE 0 4 2 1 YES U1_DATA2.I1 ... ... ... ... U1_DATA2.I24
MS*14 U1_DATA2_S 1 2 0 24 0 0 3 SEND 1 4 2 1 YES U1_DATA2.I1 ... ... ... ... U1_DATA2.I24
Attachment 32: MS settings for standard Modbus configuration (SSD/AVR)
Note: All these MS can be deleted if no SSD-Link is needed (e.g. ST)!


9.33 Attachment 33: MS settings for standard Modbus configuration (DCS)

MS NAME ACT IDENT NO_BREC NO_INT NO_INTL NO_REAL USER SOURCE BLKD NET NODE SCAN SORT REF1 ... REF8 REF9 ... REF24
MS*1 T1_INIT 1 1 0 14 0 3 SEND 1 8 -3 1 YES T1_INIT.IL1 ... ... ... T1_INIT.IL14
MS*2 T1_NETW 1 2 0 24 0 3 SEND 1 8 -3 1 YES T1_NETW.IL1 ... ... ... ... T1_NETW.IL24
MS*3 T1_REG1 1 3 0 24 0 3 SEND 1 8 -3 1 YES T1_REG1.IL1 ... ... ... ... T1_REG1.IL24
MS*4 T1_STAT 1 4 8 16 0 3 RECEIVE 0 8 -3 1 YES T1_STAT.B1 ... T1_STAT.B8 T1_STAT.IL1 ... T1_STAT.IL16
MS*5 T1_CMD_R 1 204 0 2 0 3 SEND 1 3 3 1 YES T1_CMD_R.IL1 T1_CMD_R.IL2
MS*6 T1_CMD_S 1 216 0 2 0 3 SEND 1 3 3 1 YES T1_CMD_S.IL1 T1_CMD_S.IL2
MS*7 T2_INIT 1 1 0 14 0 3 SEND 1 9 -3 1 YES T2_INIT.IL1 ... ... ... T2_INIT.IL14
MS*8 T2_NETW 1 2 0 24 0 3 SEND 1 9 -3 1 YES T2_NETW.IL1 ... ... ... ... T2_NETW.IL24
MS*9 T2_REG1 1 3 0 24 0 3 SEND 1 9 -3 1 YES T2_REG1.IL1 ... ... ... ... T2_REG1.IL24
MS*10 T2_STAT 1 4 8 16 0 3 RECEIVE 0 9 -3 1 YES T2_STAT.B1 ... T2_STAT.B8 T2_STAT.IL1 ... T2_STAT.IL16
MS*11 T1_DATA1_R 1 101 0 24 0 0 3 RECEIVE 0 3 3 1 YES T1_DATA1.I1 ... ... ... ... T1_DATA1.I24
MS*12 T1_DATA1_S 1 1 0 24 0 0 3 SEND 1 3 3 1 YES T1_DATA1.I1 ... ... ... ... T1_DATA1.I24
Attachment 33: MS settings for standard Modbus configuration (DCS)
Note: All these MS can be deleted if no DCS-Link is needed!


9.34 Attachment 34: Modbus PC-Program settings (Line, Network)

Standard Configuration:
Bentl y SSD/AVR DCS Remark
PLC Type 3 3 3 3=RTU, 4 =ASCI
Master 1 1 1
Bitrate 9600 19200 19200
Char length 8 8 8
Stopbit 10 10 10 10=1 stopbit
No Parity 0 0 0 0=no parity, 1=odd, 2=even
Full doplex 1 1 1
Pre idle time 3 3 3
Post idle time 0 0 0
Char timeout 3 3 3
Turnaround time 100 100 100
Retransmission 3 2 2
Poll cycle time 12 5 5
Adress model large 0 0 0
PLC node number 1 2 3 Must be same as node in Data/Cmd
MS-db-element and the flow-control
page!
Net number 1 4 3 First Net of redundant.
Must be same as node in Data/Cmd
MS-db-element and the flow-control
page!
Note:
For non redundant links connect only one DAT.
E.g. only U1_INIT.IL1 instead of U1_INIT.IL1 and U2_INIT.IL1

Attachment 34: Modbus PC-Program settings (Line, Network)


9.35 Attachment 35: Modbus PC-Program settings (Registers)

Standard Modbus confi gurati on:
Bentl y
(si ngle)
SSD/AVR
(redundant)
DCS
(redundant)
Regi sters
x1_CMD_R.IL1 45001 40021 40001
x1_CMD_R.IL2 72 20 24
x1_CMD_S.IL1 n.a. 40001 30001
x1_CMD_S.IL2 n.a. 20 72

Reg. Addresses
x1_REG1.IL1 45001 40001 30001
x2_REG1.IL1 n.a. 40001 30001
x1_REG1.IL2 45025 40021 30025
x2_REG1.IL2 n.a. 40021 30025
x1_REG1.IL3 45049 0 30049
x2_REG1.IL3 n.a. 0 30049
0 0 0
Where x=U for SSD/AVR; x=T for DCS; x=V for Bently
Note:
1) For non redundant links connect only one DAT.
E.g. only U1_REG1.IL1 instead of U1_REG1.IL1 and U2_REG1.IL1
2) For Bently only read-registers are needed! (no xx_CMD_S.ILx are used)

Attachment 35: Modbus PC-Program settings (Registers)


9.36 Attachment 36: Modbus PC-Program settings (flow control)

Standard Modbus confi gurati on:
Bentl y SSD/AVR DCS
Write Data IDENT n.a. 216 216
Read Data IDENT 203 203 204

Note:
1) IDENT must be the same as IDENT terminal in
MS DB-Element x1_CMD_R and x1_CMD_S!
2) Net and Node number must be the same as defined in network page
and in Data/Cmd MS db-elements!
3) For Bently only read-registers are needed!
4) Set the CONTRM-Cycletime for the flow-control to 100ms!
Read and Write
(e.g. SSD/AVR and DCS link)
Only Read
(e.g. Bently link)
PLC Status ok
Queue
redundant
Not redundant

Attachment 36: Modbus PC-Program settings (flow control)



9.37 Attachment 37: CI513 DIP-Switch settings for MB300

DIP-Switch setting Card 1

Network

Node

Sl aveno. - - MB300

S 3

S2

S1

2
7
2
6
2
5
2
4
2
3
2
2
2
1
2
0

2
7
2
6
2
5
2
4
2
3
2
2
2
1
2
0

2
3
2
2
2
1
2
0
2
3
2
2
2
1
2
0

(128) (64) (32) (16) (8) (4) (2) (1)

(128) (64) (32) (16) (8) (4) (2) (1)

(8) (4) (2) (1) (8) (4) (2) (1)

Position 1

Position 1

Position 1

Position 2

Position 2

Position 2

Sl aveno. MB300

Example: Network 11

Example: Node 13

DIP-Switch setting Card 2

Network

Node

Sl aveno. - - MB300

S 3

S2

S1

2
7
2
6
2
5
2
4
2
3
2
2
2
1
2
0

2
7
2
6
2
5
2
4
2
3
2
2
2
1
2
0

2
3
2
2
2
1
2
0
2
3
2
2
2
1
2
0

(128) (64) (32) (16) (8) (4) (2) (1)

(128) (64) (32) (16) (8) (4) (2) (1)

(8) (4) (2) (1) (8) (4) (2) (1)

Position 1

Position 1

Position 1

Position 2

Position 2

Position 2

Sl aveno. MB300

Example: Network 12

Example: Node 13

Attachment 37: CI513 DIP-Switch settings for MB300

ABB - KKS - Design Description - Advant Control - Design Rules - Rev 6 - 2006

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ABB - KKS - Design Description - Advant Control - Design Rules - Rev 6 - 2006

Caricato da

Copyright:

Formati disponibili

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

Potrebbero piacerti anche