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. 2006 ABB

© Copyright

ADVANT CONTROL

DESIGN RUL RUL ES Revisi vi sion on 6

CONTENTS 1.

Revisio Revisio n Index and and Signatures ................................................................................. .................................................................................6 6

2.

General General Descrip Descrip tion ................................................................................................... ...................................................................................................7 7 2.1 2.2 2.3

3.

Control system hardware configuration configuration (Typical) (Typical) .. ......................................... .........................................7 7 Control Control system overview overview ................................................................................ ................................................................................7 7 Abbreviations used: ........................................................................................ .. ......................................................................................7 7

Design Design Principles ....................................................................................................... .......................................................................................................8 8 3.1 Engineering units (European)......................................................................... (European)........................... ..............................................8 8 3.2 Implemented APC software functions/ f unctions/options.. options................................................ ..............................................8 8 3.3 Process Sectioning Sectioning on HSI (Typical) .............................................................. .. ............................................................9 9 3.4 Alarming and Event Handling............ Handling... .................................................................... ...........................................................10 10 3.4.1 Alarm & Event Categories Categories .............................................................. ..............................................................10 10 3.4.2 Concept for setting Limits of Analogue signals signals AC450... ................10 ................ 10 3.4.3 PIDCONA Controller Alarming AC450 ............................. .............. .............. 10 3.4.4 Event handling handling of I/O-Signal and and PC generated Alarms Alarms AC450 ... . 11 3.4.5 Standard APC APC EVENT elements. elements. (Nrs: 101 … 200) ...................... ... ...................11 11 3.4.6 Standard Project specific Event Ele E leme ment nt ... ....................................... ....................................12 12 3.5 KKS Naming of Signals ( Signal Codes) Codes) ...................................................... ... ...................................................13 13 3.5.1 For Analogue Hardware Inputs/Outputs, Conditioned & Calculated Signals.......................................................................... Signals..........................................................................13 13 3.5.2 For Limit Values (derived from Analogue values) and direct Binary inputs................................................................................... inputs... ................................................................................14 14 3.5.3 For Drive / Function Group Group Feedbacks Feedbacks / Commands ..................... ........... ..........15 15

CONTENTS 1.

Revisio Revisio n Index and and Signatures ................................................................................. .................................................................................6 6

2.

General General Descrip Descrip tion ................................................................................................... ...................................................................................................7 7 2.1 2.2 2.3

3.

Control system hardware configuration configuration (Typical) (Typical) .. ......................................... .........................................7 7 Control Control system overview overview ................................................................................ ................................................................................7 7 Abbreviations used: ........................................................................................ .. ......................................................................................7 7

Design Design Principles ....................................................................................................... .......................................................................................................8 8 3.1 Engineering units (European)......................................................................... (European)........................... ..............................................8 8 3.2 Implemented APC software functions/ f unctions/options.. options................................................ ..............................................8 8 3.3 Process Sectioning Sectioning on HSI (Typical) .............................................................. .. ............................................................9 9 3.4 Alarming and Event Handling............ Handling... .................................................................... ...........................................................10 10 3.4.1 Alarm & Event Categories Categories .............................................................. ..............................................................10 10 3.4.2 Concept for setting Limits of Analogue signals signals AC450... ................10 ................ 10 3.4.3 PIDCONA Controller Alarming AC450 ............................. .............. .............. 10 3.4.4 Event handling handling of I/O-Signal and and PC generated Alarms Alarms AC450 ... . 11 3.4.5 Standard APC APC EVENT elements. elements. (Nrs: 101 … 200) ...................... ... ...................11 11 3.4.6 Standard Project specific Event Ele E leme ment nt ... ....................................... ....................................12 12 3.5 KKS Naming of Signals ( Signal Codes) Codes) ...................................................... ... ...................................................13 13 3.5.1 For Analogue Hardware Inputs/Outputs, Conditioned & Calculated Signals.......................................................................... Signals..........................................................................13 13 3.5.2 For Limit Values (derived from Analogue values) and direct Binary inputs................................................................................... inputs... ................................................................................14 14 3.5.3 For Drive / Function Group Group Feedbacks Feedbacks / Commands ..................... ........... ..........15 15

4.5

4.6

4.7

APC-Element Settings.................................................................................. Settings..................................................................................31 31 4.5.1 PIDCONA PID Control Function..................................................... Function.....................................................31 31 4.5.2 CV with fault indication indication ................................................................... ...................................................................32 32 4.5.3 SOV/MOV with fault indi in dicat cation ion ....................................................... .......................................................33 33 4.5.4 Unidirec Unidirection tional al Drive ........................................................................ ........................................................................34 34 4.5.5 Simple Logic (e.g. FlipFlop FlipFlo p )........................................................... )...........................................................35 35 Database Element Configuration.................................................................. Configuration................... ...............................................36 36 4.6.1 AF100 scantime scantime settings for S800.................................................. S800... ...............................................36 36 4.6.2 Analogue Output Output Module (e.g. (e.g. AO810, …)..................................... …)... ..................................36 36 4.6.3 Analogue Outputs Outputs AOS (e.g. AOS810, AOS810, …).......... …)......... ............................36 ........................... 36 4.6.4 Analogue Input Input Module (e.g. AI810, AI810, AI830, …)... ...........................37 ........................... 37 4.6.5 Analogue Inputs Inputs AIS (e.g. AIS810):................................................ AIS810):..... ...........................................37 37 4.6.6 Binary Input Module Module (e.g. DI830, …) .............................................. ... ...........................................38 38 4.6.7 Binary Inputs DIS (e.g. DIS830, …)................................................ …)... .............................................38 38 4.6.8 Binary Output Module (e.g. DO815, DO810,..)............................... DO810,..).......... .....................38 38 4.6.9 Binary Outputs DOS (e.g. DOS815, DOS810, …) ........................ ........................39 39 4.6.10 S800 I-O-Station (e.g. CI820)......................................................... CI820)... ......................................................39 39 4.6.11 S600 Communication Communication Cards for AF100 AF100 (e.g. CI610, CI631) .......... ... .......39 39 4.6.12 Speed Measurement Measurement DPS640... DPS640 ........................................................ .....................................................39 39 4.6.13 Analogue Input Input Calculated (AIC (AIC on AC450): .................................. ... ............................... 40 4.6.14 Digital Input Calculated Calculated (DIC on AC450): AC450): ....................................... ... ....................................40 40 4.6.15 Analogue Output Output Calculated (AOC): (AOC): .............................................. ... ...........................................40 40 4.6.16 Digital Output Calculated Calculated (DOC): ................................................... ...................................................40 40 AC450 Hard- and Software Software Limits ................................................................ ................................................................41 41 4.7.1 S800-Stations S800-Stations ................................................................................. ... ..............................................................................41 41 4.7.2 Signals............................................................................................ Signals... .........................................................................................41 41 4.7.3 DB Obje Objects cts ..................................................................................... .....................................................................................41 41 4.7.4 TTD Logs........................................................................................ Logs........................................................................................41 41

7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 8.

MOVE-RED ..................................................................................................50 Integrator ......................................................................................................50 CONTRM cycle time: On-Line changes .......................................................50 Deleting Type Circuits ..................................................................................50 Changing DSP parameters on-line...............................................................50 SYSDIAG (System Diagnosis) .....................................................................51 Missing values during debugging (“x“)... .......................................................51 Calculation of SPDGRD (for RSM)...............................................................51 DIC Scantime .............................. .................................................................51 Usage of ERR Terminal of DB-Element DI651X ..........................................52 Checks required after Generate Target Code ..............................................52

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. At tac hm ent s..............................................................................................................57 9.1 9.2 9.3 9.4 9.5

H251

H261

H271

Attachment 1: Analogue Signal Error Handling AC450 to AC160 X................ 58 Attachment 2: Analogue Signal Error Handling AC160 to AC450 X................ 59 X Attachment 3: Communication Routes between AC160 Nodes X................... 60 X Attachment 4: AC450 Node to Node Interface (Typical)X.............................. 61 X Attachment 5: AC450 Node to Node DS naming convention 62 H23

H23

H243

H253

9.32

H51

Attachment 32: MS settings for standard Modbus configuration X (SSD/AVR)X...................................................................................................89 Attachment 33: MS settings for standard Modbus configuration (DCS) X....... 90 X Attachment 34: Modbus PC-Program settings (Line, Network) X.................... 91 X Attachment 35: Modbus PC-Program settings (Registers)X........................... 92 X Attachment 36: Modbus PC-Program settings (flow control) X........................ 93 X Attachment 37: CI513 DIP-Switch settings for MB300X................................. 94 X H53

9.33 9.34 9.35 9.36 9.37

H561

H571

H581

H591

H601

H543

H53

H563

H573

H583

1. Revisi on Index and Signatur es Rev. ind.

Page (P) Descripti on Chapt. (C)

0

Date Dept./Init.

First issue for use by KWGLA3 for AL-Hidd (based on internal 98-03-30 API Design Guide) KWGLA3-S.Waller KWGLA3-A.Jenney

1

All

Revised for use by all KWGLA groups

98-06-23 KWGLA3-A.Jenney 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.Jenney NPE2 D.Looser NPE1-P.Schori NPE1J.C.Rey NPE1-D.Lüönd

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

2. General Descr ipt ion 2.1 Control system hardware confi guration (Typical) UNIT 1: Service

Equipment

GT 11

AC450+AC160

Node Nr CCPP (example) u1

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 Connectivity Connectivity Connectivity

Server CS1 Server CS2 Server CS3 Server CS4

RTA CS001 RTA CS002 RTA CS003 RTA CS004

51 52 53 54

Node Nr. ICS / OK 15

3. Design Principles 3.1 Engineerin g uni ts (European) Unit

Remark

Unit

Remark

A bar bara cm degC GJ/h h Hz J K kA kcal kg kg/h kg/m3 kg/s kJ kJ/s kpa

Ampere Gauge or diff. press. Absolute pressure

mbar mbara mg/kg mg/m3 min mm mmHg mmWC Mpa MVAr MW MW/min MWh ohm pa pH ppb ppm rpm

Gauge or differential press. Absolute pressure

ºC hour Joule Kelvin

Level/Press. (Mercury Column) Level/Press. (Water Column)

W pascal parts per billion parts per million

3.3 Process Secti oni ng on HSI (Typical) Section Nr

Area (Multis haft p lants)

Ar ea (ICS pl ants)

Ar ea (OK pl ants)

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

12

GT2 + HRSG2 unit 3

13

GT3 + HRSG3 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.

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.

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 Al arms Event AUDIB AL _ Pro per ty Nr . PRIO Tex t 201 1 2 >MAX1 MAX2 MAX1 210 1 2 >MAX2 211 1 2 >MAX3 212 1 2 >MAX4 213 1 2 TRIP 214 2 3 BDQ 215 2 3 SEN UNEQ 216 2 3 DIST 217 2 3 TORQUE 218 2 3 NOT OK 219 2 3 FAILURE 220 2 3 MIN1 224 2 3 BLOCKED 225 2 3 CH DIFF 226 2 3 TEST 227 2 3 ALARM

Events Stat us A ct i ve AlarmEVTE1 AlarmEVTE2 AlarmEVTE1 AlarmEVTE2 Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm Alarm

Stat us n ot A ct i ve NormalEVTE3 NormalEVTE4 NormalEVTE3 NormalEVTE4 Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal Normal

Even t AUDIB AL _ Pro per ty Nr . PRIO Tex t 240 0 4 CLOSED 241 0 4 LOCAL 242 0 4 OFF 243 0 4 ON 244 0 4 OPEN 245 0 4 NOT TRIP 246 0 4 AUTO 247 0 4 MANUAL 248 0 4 STOP 249 0 4 ACTIVE 250 0 4 REMOTE 251 0 4 DSENGA 252 0 4 STANDSTILL 253 0 4 ACK 254 0 4 INTMD 255 0 4 LOWER 256 0 4 REACHED 257 0 4 OPR POS 258 0 4 RAISE 259 0 4 READY 260 0 4 RELEASE 261 0 4 NOT READY 262 0 4 SELECTED 263 0 4 SUCSFUL 264 0 4 DETECTED 265 0 4 TEST 266 0 4 ENGAGED 267 0 4
Stat us A c ti v e

Stat us n ot A c ti v e

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 c is character

0...9. A...Z

3.5.1 For Analogue Hardware Inputs/Outputs, Conditioned & Calculated Signals Main KKS

Ccnnn_ or Fcnnn_ or FFnnn or FUnnn Ccnnn_ or Fcnnn_ or FFnnn or FUnnn

Ext.

Used for

Notes

XQ50 XQ60 XQ63 XJ50 XJ60

Analogue Input Analogue Signal Analogue signal Error Analogue Output “Corrected” or “Combined” value

Hardware Input After 4-20mA Transmitter superv. Input disturbance of XQ60 signal Hardware output ”Corrected” Flow, Level,.. Analogue signal, 2oo3 etc.

XJ63

Error of “Corr.” or “Comb.” Value (2o3)

“Corrected” or “Combined” analogue disturb. Signal. Normally event FAILURE

XJ64

Error of one signal (1o3)

Can include drift alarm! Normally event SEN UNEQ

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

Correction

FF009

CP011

Example 2: Temperature corrected flow measurement with 2 out 3 CT001 CT002 CT003

2oo3

CF001 CF002 CF003

2oo3

CT901

CF901 Correction

FF951

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

inverse Status

3.5.3 For Drive / Function Group Feedbacks / Commands Binary Analogue UNIDIR DRIVES and VALVES signal signal

ELECTRICAL SWITCHGEAR (Breakers, Isolators etc)

Xc01 Xc02 Xc03

CLOSED (ON) OPEN (OFF)

ON/OPEN OFF/CLOSED ON 2 / FAST/REVERSE nd (2 Speed of 2-speed drive) ON TORQUE P

P

Xc06 Xc35 Xc37 Xc38 Xc39 Xc40

DISTURBED LOCAL REMOTE

Xc91 Xc92 Xc93

CMD ON / CMD OPEN CMD OFF / CMD CLOSE CMD RELEASE or CMD 2 ON: nd (2 Speed of 2-speed drive) Xc95 CMD STOP (Hold) XJ13 Xc97 Positioning output to Control Valve XJ50 PIDCON Output XJ51 PIDCON Deviation Where: Xc = XA for function groups / selectors Xc = XB for open loop drives P

P

3.5.4 From/To Pushbuttons, Lamps and Indicators (Hardwired)

TRIPPED TEST position DISTURBED LOCAL REMOTE (normally not required – not according REEP) CMD CLOSE (ON) CMD OPEN (OFF)

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 Commun icati on Refer to Attachment 4: AC450 Node to Node Interface (Typical) HT236X

XT

•

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 T

H36X

TX

HT436X

XT

KKS for Signals being transferred from one Node to another: source: sink:

nncccnnccnnn_ccnn nncccnnccnnn_ccnn_NODENUMBER (of sending Node)

3.6.2 Binary signals transferred between nodes Refer also to Attachment 5 H536X

X

KKS for Signals being transferred from one Node to another: source: sink:

nncccnnccnnn_ccnn nncccnnccnnn_ccnn_NODENUMBER (of sending Node)

ST

(Note: the 1 ‘_’ must be replaced by any 13th character in the KKS (according note above) P

P

Alarm List, Event List, Object Display

DIS 18MAJ10DP001_XG11

CONV-BI

Functional Logic

DAT 171801S.IL1

DIC 18MAJ10DP001_XU01

DS 171801S

HSI

DS 171801R DAT 171801R.IL1

CONV-IB

DOC 18MAJ10DP001_XG11_17

Read by all PC Programs within this node which

•

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). H63X

•

X

If more th an 2 DS’s 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 DAT of a DS must be an IL.

st P

P

st

(Note: Bits 1 to 22 of the 1 IL will be used to transmit the error signals of the REALs 1 to 22.) P

P

nd

•

The 2 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.

P

P

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

3.7 DSP Data Trans fer 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

CL

P3

01

As with DS, the associated DAT’s ( .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 st

In AC160 “KKS“ is (normally) without the equipment unit code (i.e. the 1 2 numbers of actual KKS P

P

P1 (AC160) AIS: KKS _XQ50

DIS: KKS _XG01

Meco/Functional Logic:

Meco/Functional Logic:

DAT / DSP

Node 15 (AC450)

DAT / DSP

DIC / EVS

3.7.3 AC160 Station Numbering Generally a Turbo Group will consist of 4 to 6 processors in 3 stations: GT

ST

Control ler Descript ion

10 10 10 20 20 30

11 11

P1 C1 or CL C2 P2 OL P3

21 31

Protection channel 1 (& IP/LP Bypass Stop valves if applicable) Closed Loop Closed Loop 2 (for GT24/26 only) Protection channel 2 (& LP Stop Valves) Open Loop (for GT only) Protection channel 3 (& IP/LP Bypass Control valve if applicable)

3.7.4 Typical Definition of DSP’s 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

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

1…50

02

DCS to P2

DCSP201..50

1…50

03

DCS to P3

DCSP301..50

1…50

04

DCS to HMI

n.a.

05

DCS to OL

DCSOL01

1…50

06

DCS to CL

DCSCL01

1…50

GT24/26 use “C1“ instead of “CL“

07

DCS to C2

DCSC201

1…50

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 (Act ual Station 11) Virt. Stat. Data from

DSP-Nrs.

Ident-Nrs.

Remark

10

P1 to DCS

P1DCS01..50

1…50

11

P1 to P1

n.a.

12

P1 to P2

n.a.

Data Transfer via HSL

13

P1 to P3

n.a.

Data Transfer via HSL

14

P1 to HMI

P1HMI01..50

1…50

15

P1 to OL

P1OL01..50

1…50

16

P1 to CL

n.a.

Data Transfer via MDAT

17

P1 to C2

n.a.


HMI: Drive si gnals i nterface of A C450 (Act ual Station 40) Virt. Stat. Data from

DSP-Nrs.

Ident-Nrs.

Remark

40

HMI to DCS

n.a.

41

HMI to P1

HMIP101..50

1…50

42

HMI to P2

HMIP201..50

1…50

43

HMI to P3

HMIP301..50

1…50

44

HMI to HMI

n.a.

45

HMI to OL

HMIOL01..50

1…50

46

HMI to CL

HMICL01..50

1…50


47

HMI to C2

HMIC201..50

1…50

For GT24/26 only

Remark

OL: Open Loop Control (Actual Station 22) Virt. Stat. Data from

DSP-Nrs.

Ident-Nrs.

50

OL to DCS

OLDCS01..50

1…50

51

OL to P1

OLP101..50

52

OL to P2

n.a.

53

OL to P3

OLP301..50

54

OL to HMI

OLHMI01..50

1…50

55

OL to OL

n.a.

1…50

56

OL to CL

OLCL01..50

1…50


57

OL to C2

OLC201..50

1…50

For GT24/26 only


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 OL

PX

PX

.

B

01

Example: The following single DAT might be “broadcast“.to multiple destinations via multiple DSPs. DAT Type: DAT(B) DAT(B)

DAT Ident: OLPXB01 OLPXB01

Via DSP Ident: OLP101 OLP301

From: OL OL

To: P1 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.

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] [

]

[

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

[P3IL01]

IL

2

3

HSLR

[P3R01]

R

2

3

HSLS

[P1IL01]

IL

n.a.

1

HSLS

[P1R01]

R

n.a.

1

Protection Channel 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 Landsc ape Englis h 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 landsc ape Englis h

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 Conf igur ation 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 Progr am Struc tur e Error! Objects cannot be created from editing field c odes. 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 MECO

1

Transmitter Supervision Red 1

2


3


4

Meas. Conditioning, Signal Limits

5

Meas. Conditioning, Signal Limits

6

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

21


22


23

Signalcond. CLC1-AC450

24

Signalcond. CLC2-AC450

Remark

4.3 Correct ion Funct ion s (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

AIS2.1 (XQ50)

Wire Break Supervision Redund. 2 PC Program 2

AIC2 (XQ60)

4.4 Typic al PC str uct ure 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 x.11

(for General Input Logic) st (for 1 FunctionGroup) (Application logic FunctionGroup) (Application logic SEL)

x.11.11.1 through n x.11.11.50 x.11.11.m through 20

CONTRM CONTRM FUNCM FUNCM FUNCM MOVES TC FG MOVES

x.11.12.1 through n x.11.12.50 x.11.12.m through 20

MOVES TC SEL MOVES

(Inputs to TC)

CONTRM FUNCM

(for 1 Drive) (Application logic for Drive)

x.11.1 x.11.2 x.11.11

P

P

(Inputs to TC) (Outputs from TC)

x.11.12

x.21 x.21.1

(Outputs from TC) ST

P

P

4.5 APC-Element Setting s 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 fo r Drives: (See following Tables for further info) Driv e

GU-Type

DRVSV1 DRVSV2 DRVMOV DRVPMP DRVBRK DRVFAN FG SEL

GU4 GU5 GU5 GU3 GU3 GU6 GU2 GU2

Remarks

4.5.1 PIDCONA PID Control Function PC Element: Terminal BUMPLESS MV MANENBL MANFL

Value

Remarks

XQ60 / XJ60 XA03 XQ63/XJ63

1 Measured Value Funct.Grp Hold Cntrl variable dist (XQ63/XJ63) "OR"ed with 10s delay

4.5.2 CV with fault indication Valves with intermediate position PC Element (GENUSD-I): Terminal

Value

ALQ1 ALF2 INTLU3 IND1 IND2 IND3 IND4

Remark Sign Error POS Ind Error (XQ63) OR Pos. Discrepancy (+/- 5% delayed 10 sec) or only analogue feedback error (XQ63) Safety Control

XG01 XG02 Intermediate: not open AND not closed D=1

DB Element: Terminal

Value

NAME VAR

KKS (13) GU5

VALALWD ORDALWD MVH1 MVL1 RP_BLK

H’FFFF H’FFFF 512 128 0

Remark 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)

Depends on visualisation in object display

4.5.3 SOV/MOV with fault indication ShutOff Valves or Motor Operated Valves with or without intermediate position PC Element (GENUSD-I): Terminal

Value

Remark

ALQ1 ALF1 ALF2 ALF3 ALF6 INTLU3 IND1 IND2 IND3

XB38

Sign Error (Disturbed) Posn. Discrepancy Open Posn. Ind Error Switching Fault Posn. Discrepancy Close Safety Control Open position Closed position Intermediate position:Inverted XG01 ANDed with Inverted XG02 Set IND4=0 and BLK to D=1 to display a green "C" by object on OS otherwise a yellow "P" is displayed. Order Open/On Order Close/Off

IND4

XQ63

XB35 XG01 XG02

D=0

ORDC1 ORDC3 DB Element: Terminal

Value

Remarks

NAME VAR

KKS (13) GU4

In general

OS

GU4… display element for SOV,

4.5.4 Unidirectional Drive Used for position feedbacks where more than one feedback is available. PC ELEMENT (GENUSD-I) Terminal

Value

ALQ1 ALQ2 ALF1 ALF2 ALF3 ALF6 M1 BLK

D=1 D=1

IND1 IND2 IND3 IND4

XG01 XG02 D=00 D=0

Remarks Sign Error Power Failure Posn. Discrepancy On Posn. Ind Error (Disturbed) Switchgear Fault Posn Discrepancy Off Set IND4=0 and BLK to D=1 to display a green "C" by object on OS otherwise a yellow "P" is displayed. Position ON Position OFF Allow C with Block

DB Element: Terminal

Value

Remarks

NAME VAR

KKS (13) GU3

In general use on OS any GU3… display element

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) Terminal

Value

Remark

ORDC1 ORDC3

XB91 XB92

ORDER ON ORDER OFF

PC ELEMENT (GENUSD-I) Teminal

Value

Remark

M1 BLK IND1 IND2 IND3 IND4

D=1 D=1 XG01 XG02 D=0 D=0

ON OFF

Terminal

Value

Remark

NAME VAR

KKS (13) GU3

Use on OS either GU3GO or a DIC / DOC solution

DB Element:

4.6 Database Element Confi gur ation 4.6.1 AF100 scantime settings for S800 AC450-Sys tem s (S800 co nnect ed to CI522) The following standard settings must be used for good performance-CPU-load relation: Parameter

Settings

Remark

AF100 scantime (INSCANT/OUTSCANT) AF100 scantime (INSCANT/OUTSCANT)

Analog: 32ms, Digital 16ms

Calculated AF100 bus load <70% with up to 9 Stations. Calculated AF100 bus load <70% with 9 to 12 Stations.

Input Scanning time CI522 (SCANT)

Analog Input: 64ms Analog Output: 32ms, Digital Input 32ms Digital Output 16ms Analog: 200ms, Digital 100ms

AC160-Sys tem s (S800 co nnect ed to CI631) The following standard settings for Egatrol must be used: Parameter

Settings

AF100 scantime (INSCANT) Input Scanning time CI820 (INSCANT)

Analog: 64ms, Digital 32ms 32ms

Remark

4.6.4 Analogue Input Module (e.g. AI810, AI830, …) Terminal

Value

Remark

IMPL GRIDFREQ CONV_PAR INSCANT INSCANT

1 50Hz 4..20mA 32ms 64ms

Only for used cards, otherwise 0 for AI830: Pt100,850C Fieldbus scantime on AC450 systems. 64ms for 9..12 stations! Fieldbus scantime on AC160 (Egatrol). For AI830: 256ms

4.6.5 Analogue Inputs AIS (e.g. AIS810): Terminal

Value

Remark

ACT CONV_PAR SCANT LIN_CODE FILTER_P DEADB ERR_CTRL

1 4..20mA 200ms 0 0 0.2% 0

Only for used channels, otherwise 0

ERR_VAL DEC NORM_TR H2_R_FCL

0.0 1 1

Input scanning CI522 (only AC450).

Last valid value to be held when the error bit is set (only AC160) (only AC450) Nr. of decimals to be shown on the HMI. See table below To allow ‘event driven’ updating of the HMI (only AC160) 1 to avoid repeat alarms from filling the buffers (only AC450)

4.6.6 Binary Input Module (e.g. DI830, …) Terminal

Value

Remark

IMPL INSCANT INSCANT SCANT SENSOR SPS_MODE ERR_SUP SUP FILT

1 16ms 32ms 100ms 0 24V external NO YES 8

MODE SHUTPER SHUTTRI RECTIME

SOE 0 0 0

Only for used cards, otherwise 0 Fieldbus scantime on AC450 systems. 32ms if 9..12 stations! Fieldbus scantime on AC160 (Egatrol) Input scanning CI522 (only AC450). (Only AC160) (Only AC160) (Only AC160) Sensor power Supervision minimum pulse length required at input to be detected as a signal (Only on AC450) (Only AC450) (Only AC450) (Only AC450) (Only AC450)

4.6.7 Binary Inputs DIS (e.g. DIS830, …) Terminal NORM_POS

Value

Remark Used to define the ‘Normal Signal Value’, the default value of ‘0’ is used when the binary signal non-active state is 0 (nonactive= when the status text associated with the VALUE_TR

4.6.9 Binary Outputs DOS (e.g. DOS815, DOS810, …) Terminal

Value

Remark

ACT OSP_CTRL

1 0

Only for used channels, otherwise 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) Terminal

Value

Remark

CABLE REDUND SUP_PS SUP_PS_E EXT_TIME TIM_SYNC INSCANT CH_OVER BUS

R YES YES NO YES SLAVE 32ms NO 2

Redundant cable Redundant station

(only AC160) (only AC160) (only AC160) (only AC450) Normally 2

4.6.11 S600 Communication Cards for AF100 (e.g. CI610, CI631) Terminal

Value

MASTER

1

Remark

4.6.13 Analogue Input Calculated (AIC on AC450): PC Programs WRITE to :CALC_VAL,

PC Programs READ from VALUE

AIC’s 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):. H37X

X

4.6.14 Digital Input Calculated (DIC on AC450): PC Programs WRITE to :CALC_VAL

PC Programs READ from :VALUE

DIC’s can be written from the HSI if the signal source is connected to :CALC_VAL and the Database Update is Blocked (same as DI) DIC’s 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. AOC’s do NOT have any Value Treatment. Set ERR_TR =0 (Err_Tr terminal has no effect)

4.7 AC450 Hard- and Softw are Lim its 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. 4H7X3T

X

H537X

X

T

On one Station a maximum of 12 I/O-Modules can be connected, 24 modules if there is a busextension installed. If you want to do a non-standard configuration with more than 12 S800-stations, use the busloadcalculation 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 DOS + DOC AIS + AIC + AIEV AOS + AOC

2300 1489 910 963

4.7.3 DB Objects Object

Max

4.8 AC160 Hard- and Softw are Lim its 4.8.1 Cards & Racks Card Type

Max

Recommended

I/O cards per basic station (includes extension rack) Basic station (CPUs + I/Os) I/O stations I/O station extension rack S600 I/O Bus Extension cable I/O cards Modbus cards (CI532) AF100 Links

10 + 10

18

HSL (High Speed Link)

1 7 1 per stn. 20 metres 151 2 2 (1xRed) 8 (4xRed)* 2 per cpu

4

Note1

75

Note 1 * 8 links from Firmware version 2.1/x

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

Remarks

5. Hardware Supervisio n 5.1 Transmi tter and Wire-break Supervi sio n in AC450 Refer to Attachment 7: AC450 Transmitter and Wire-Break Supervision for PC Program printout HT637X

XT

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 FUNCM’s (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.

5.2 Analog ue Sign al Transf er 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. HT73X

XT

Refer to Attachment 1: Analogue Signal Error Handling AC450 to AC160 for AC450 to AC160 communication HT837X

XT

Refer to Attachment 2: Analogue Signal Error Handling AC160 to AC450 for AC160 to AC450 communication HT937X

5.3 Transmi tter and Wire-break Supervi sio n in AC160 5.3.1 Wire-break Supervision for S600 (e.g. AI625)

XT

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 . HT438X

XT

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. HT538X

XT

HT638X

XT

Fault Categories defined by Alstom: Damage caused by a fault Energy set free very high high low none

Extent of injury or damage Persons Plant highly likely severe less likely extensive not likely medium none slight

Downtime* >6 months months weeks days

Fault Category (FC) Timing of event

Event

FC

immediate almost immediate moderately delayed easy to control

major accident accident fault disturbance

1 2 3 4

* = time to repair

Switching options and required Error-Handling for protection logic: Protection Method

Ac ti on if 1 signal is disturbed

Ac ti on if mult ip le signals are disturbed

comments

6. Tips and Tricks fo r AC450 plannin g 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.

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-G’s and the Balance input is used on the FUNG-1V, the set of values used in the REG_G’s 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. 7H8X3T

X

H83X

TX

FUNCM

6.7 TTDLogs & TTDVars and Renumberi ng 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 pro gram Names:

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 Hardw are Dimensio nin g 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

7. Tips and Tricks fo r AC160 plannin g 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 us ed by mul tip le CPUs in the same station All I/O cards which are configured to produce SOE (Sequence Of Events) mustNOT 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

7.8 SYSDIAG (System Diagnos is) 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 Calculati on of SPDGRD (for RSM)

7.12 Usage of ERR Termi nal 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.

DI1:SPE_ERR (Process Error)

OR

11CRC20BB013_XM01 (DI651 I/O-CARD DIST)

OR

CRC20BA000_XU54 (DI651 TIME SYNC ALARM)

DI1:SDE_ERR (Device Error)

DI1:SSE_ERR (SOE Error) DI2:SSE_ERR (SOE Error) DI3:SSE_ERR (SOE Error)

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 DBelements)

•

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.

8. Tips & Tric ks: General 8.1 SI-ANSI Conversi on parameters SI Unit

Factor

Offset

ANSI Unit

cal kcal bar mbar bara mbara barg Rmbar kg/s kg/h m3/h l/s sm3/h m3/h g kg mm m um umpp l

4.1868 4.1868 14.5038 0.40146 14.5038 0.02992 14.5038 1 2.20462 2.20462 35.3147 0.2642 0.58858 0.58858 15.4324 2.20462 0.03937 3.28084 0.03937 0.03937 0.03531

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

J kJ psi inWC psia inHG psig Rmbar lb/s lb/h cfh gal/s scfm cfm gr lb in ft mil milpp ft3

8.2 Sourc e Code Naming con venti on 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 C2 CL O1 O2 OL P1 P2 P3 nn

Closed Loop Controller 1 Closed Loop Controller 2 Closed Loop Controller Open Loop Controller 1 Open Loop Controller 2 Open Loop Controller Protection 1 Protection 2 Protection 3 AC450 node nn

If 2 Closed Loop Controllers present (eg GT) If 1 Closed Loop Controller present (eg ST) If 2 Open Loop Controllers present (eg GT) If 1 Open Loop Controller present (eg ST)

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

Month

Day Code

Day

1 2 3 4 5 6

January February March April May June

1 2 3 4 5 6

1 2 3 4 5 6

8.3 Time Synchroni sation 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!

Master Clock Minute Pulse

OS500 or CS Time Master

OS500 or PPA

CLS Setting: CLK_MAST = 0 LOC_TIME = 3 CLK_SEND = 1

CLS Setting: CLK_MAST = 0 LOC_TIME = 3 CLK_SEND:= 0 MB300

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

AF100 AC160 RACK PM6xx:

AC160 RACK PM6xx:

AC160 RACK PM6xx:

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 Editi ng TIX fil es 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 commun icti on 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. H139X

CONV-IB

modbus data

Analog-Signal Error

DAT(IL)

Bit1 of Modbus Status word

X

DIC (XQ63) (PLC ALIVE)

OR

AIC:ERR (XQ60)

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 H61

H923

H621

H93

H631

H943

H641

H953

H651

H963

H61

H973

H671

H983

H681

H93

H691

H04

H701

H014

H71

H024

H721

H034

H731

H04

H741

H054

H751

H064

H761

H074

H71

H084

H781

H094

H791

H104

H801

H14

H81

H124

9.1 At tac hm ent 1: A nal ogue Si gnal Er ro r Handl in g A C450 to AC160 H942X

X

Attachment 1: Analogue Signal Error Handling AC450 to AC160 Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

58

9.2 At tac hm ent 2: A nal ogue Si gnal Er ro r Handl in g A C160 to AC450 H043X

X

Attachment 2: Analogue Signal Error Handling AC160 to AC450 Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

59

9.3 At tac hm ent 3: Co mm unic ati on Routes bet ween AC160 Nod es H143X

X

Attachment 3: Communication Routes between AC160 Nodes Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

60

9.4 At tac hm ent 4: A C450 Node t o Node In ter fac e (Typic al) H243X

X

Attachment 4: AC450 Node to Node Interface (Typical) Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

61

9.5 At tac hm ent 5: A C450 Node t o Node DS naming co nv ent io n H34X

X

Attachment 5: AC450 Node to Node DS naming convention Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

62

9.6 At tac hm ent 6: A C450 Node t o Node No de A nalog nal og ue Sign Si gn al Er ro r Handl Han dl in g H43X

X

Attachment 6: AC450 AC450 Node to Node Node Analogue Signal Signal Error Handling Handling Doc. no.

ABB Switzerland Ltd Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

63

9.7 At tac hm ent 7: A C450 Trans mi tt er and an d Wi re-B reak Sup erv is io n H534X

X

Attachment 7: AC450 AC450 Transmitter and Wire-Break Supervision Supervision

Doc. no.


Lang.

1AHL 102 709

en

Rev. ind.

6

Page

64

9.8 At tac hm ent 8: A C160 MECO for S600 H634X

X

Attachment 8: AC160 AC160 MECO for S600

Doc. no.


Lang.

1AHL 102 709

en

Rev. ind.

6

Page

65

9.9 At tac hm ent 9: A C160 MECO for AI810 H743X

X

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

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

66


X

Attachment 10: AC160 MECO for AI830 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

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

67


X

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

Pt100 Compensation measurement on channel 8

Attachment 11: AC160 MECO for AI835 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 -270degC…1300degC). 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

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

68

9.12 At tac hm ent 12: A nalog ue Lim it s f or Hardwar e I/Os i n A C450 H04X

X

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 di splay use (HMI). Do not use them for any switching functions. The DICs of the 2 or 3 separate signal l imits must be used. st 4: Only write to the 1oo2 or 2oo3 AIC Limits from the 1 source signal. P

P

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

69

9.13 At tac hm ent 13: 2oo3 A nalog ue s ig nal and alar m h andli ng H14X

X

Attachment 13: 2oo3 Analogue signal and alarm handling Notes: - XJ63: 2oo3 Sensors disturbed or drift, Event Treatment 219 (FAILURE). Description: ...2o3 (e.g. P LPT EXHAUST 2o3). - XJ64: 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). H42

H43

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

70

9.14 At tac hm ent 14: 2oo3 TRIP Sign al Handl in g FC2 (AC450) H4X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

71

9.15 At tac hm ent 15: 2oo3 TRIP Sign al Handl in g (Sign al f ro m A C160, Logi c i n A C450) H54X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

72

9.16 At tac hm ent 16: 1oo2 TRIP Sign al Handl in g (A C450) H64X

X

Attachment 16: 1oo2 TRIP Signal Handling (AC450) Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

73

9.17 At tac hm ent 17: 1oo1TRIP Alar ms and Events (AC160) H74X

X

Attachment 17: 1oo1TRIP Alarms and Events (AC160) Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

74

9.18 At tac hm ent 18: 1oo2 PLS/PLST/TRIP Sign al Handl in g (A C160) H84X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

75

9.19 At tac hm ent 19: 1oo2 ST-TRIP wit h r elat io n t o CLC (AC160) H94X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

76

9.20 At tac hm ent 20: 2oo3 PLS/PLST/TRIP Alar ms (AC160) H045X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

77

9.21 At tac hm ent 21: 2oo3 TRIP Sign al Handl in g (Hardw ir ed betw een AC160's) H145X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

78

9.22 At tac hm ent 22: Si gnal Redundancy Gui delin es p art 1 H245X

X

Attachment 22: Signal Redundancy Guidelines part 1 Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

79

9.23 At tac hm ent 23: Si gnal Redundancy Gui delin es p art 2 H345X

X

Attachment 23: Signal Redundancy Guidelines part 2 Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

80

9.24 At tac hm ent 24: Cont ro ll er Release Log ic H45X

X

Attachment 24: Controller Release Logic Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

81

9.25 At tac hm ent 25: Cont ro ll er In ter lo ck s & Ind ic ati on H54X

X

Attachment 25: Controller Interlocks & Indication Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

82

9.26 At tac hm ent 26: Manual Stat io n as SetPoin t St ati on H645X

X

Attachment 26: Manual Station as SetPoint Station Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

83

9.27 At tac hm ent 27: Cont ro ll er Direc t / Reverse A ct io n & Fail -Safe H745X

X

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

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

84

9.28 At tac hm ent 28: Cont ro ll er L im it ati on H845X

X

Attachment 28: Controller Limitation Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

85

9.31 At tac hm ent 31: MS sett s ett in gs fo r s tan dar d Modb Mo db us co nf ig ur ati on (Vib rat io n Mo ni to r) H164X

MS

NAME

X

ACT IDENT IDENT NO_BREC NO_BREC NO_INT NO_INT NO_INT NO_INTL L NO_REAL NO_REAL USER SOURCE SOURCE BLKD NET NODE NODE SCAN SORT SORT

MS1

V1_INIT

1

MS2

V1_NETW

MS3

V1_STAT V1_STAT

MS4

V1_REG

MS5

V1_CMD_R

MS6

V1_DAT1_S

MS7

V1_DAT1_ V1_DAT1_R R

MS8

V1_DAT2_S

MS9

1

0

0

1

2

0

0

1

3

8

0

1

4

0

0

1

203

0

0

1

1

0

1

101

0

1

2

0

14

SEND

1

7

-3

1

REF1 REF1

YES V1_INIT.IL1

...

...

REF8 REF8

...

REF9 REF9

...

...

REF24 REF24

0

3

V1_INIT.IL14

24

0

3

SEND

1

7

-3

1

YES V1_NETW.IL1 ...

...

...

...

V1_NETW.IL24

16

0

3

RECEIVE RECEIVE

0

7

-3

1

YES V1_STAT V1_STAT.B1 .B1

...

...

...

...

V1_STAT V1_STAT.IL16 .IL16

24

0

3

SEND

1

7

-3

1

YES V1_REG.IL1

...

V1_REG.IL8 V1_REG.IL9 ...

V1_REG.IL24

2

0

3

SEND

1

1

1

1

YES V1_CMD_R.IL1 V1_CMD_R.IL2

24

0

0

3

SEND

1

1

1

1

YES V1_DAT1.I1

...

...

...

...

V1_DAT1.I24

24

0

0

3

RECEIVE RECEIVE

0

1

1

1

YES V1_DAT1. V1_DAT1.I1 I1

...

...

...

...

V1_DAT1. V1_DAT1.I24 I24

24

0

0

3

SEND

1

1

1

1

YES V1_DAT2.I1

...

...

...

...

V1_DAT2.I24

V1_DAT2_ V1_DAT2_R R

1

102

0

24

0

0

3

RECEIVE RECEIVE

0

1

1

1


...

...

...

...


MS10 V1_DAT3_S

1

3

0

24

0

0

3

SEND

1

1

1

1

YES V1_DAT3.I1

...

...

...

...

V1_DAT3.I24

MS11 V1_DAT3_ V1_DAT3_R R

1

103

0

24

0

0

3

RECEIVE RECEIVE

0

1

1

1


...

...

...

...


Attachment 31: MS settings settings for standard standard Modbus configuration configuration (Vibration (Vibration Monitor) Note: 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: Note: For ST-link to Vibration Monitor only MVI1 (Pos. 6, Subpos. 1, upper port) is used. Leave all settings as shown here.

Doc. no.


Lang.

1AHL 102 709

en

Rev. ind.

6

Page

88

9.32 At tac hm ent 32: MS sett in gs fo r s tan dar d Modb us co nf ig ur ati on (SSD/AVR) H246X

MS

NAME

MS*1

U1_INIT

MS*2 MS*3

X

ACT IDENT NO_BREC NO_INT NO_INTL NO_REAL USER SOURCE BLCK NET NODE SCAN SORT

REF1

...

REF8

REF9

...

REF24

1

11

0

0

14

0

3

SEND

1

8

-3

1

YES U1_INIT.IL1

...

...

...

U1_INIT.IL14

U1_NETW

1

12

0

0

24

0

3

SEND

1

8

-3

1

YES U1_NETW.IL1 ...

...

...

...

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 ...

...

...

...

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)!

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

89

U1_NETW.IL24

U2_NETW.IL24

9.33 At tac hm ent 33: MS sett in gs fo r s tan dar d Modb us co nf ig ur ati on (DCS) H346X

MS

X

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

...

...

...

MS*2

T1_NETW

1

2

0

24

0

3

SEND

1

8

-3

1

YES T1_NETW.IL1 ...

...

...

...

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

...

...

...

MS*8

T2_NETW

1

2

0

24

0

3

SEND

1

9

-3

1

YES T2_NETW.IL1 ...

...

...

...

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

MS*13 T1_DATA2_R

1

102

0

24

0

0

3

RECEIVE

0

5

3

1

YES T1_DATA2.I1

...

...

...

...

T1_DATA2.I24

MS*14 T1_DATA2_S

1

2

0

24

0

0

3

SEND

1

3

3

1

YES T1_DATA2.I1

...

...

...

...

T1_DATA2.I24

MS*15 T1_DATA3_R

1

103

0

24

0

0

3

RECEIVE

0

3

3

1

YES T1_DATA3.I1

...

...

...

...

T1_DATA3.I24

MS*16 T1_DATA3_S

1

3

0

24

0

0

3

SEND

1

3

3

1

YES T1_DATA3.I1

...

...

...

...

T1_DATA3.I24

MS*17 T1_DATA4_R

1

104

0

24

0

0

3

RECEIVE

0

3

3

1

YES T1_DATA4.I1

...

...

...

...

T1_DATA4.I24

MS*18 T1_DATA4_S

1

4

0

24

0

0

3

SEND

1

3

3

1

YES T1_DATA4.I1

...

...

...

...

T1_DATA4.I24

Attachment 33: MS settings for standard Modbus configuration (DCS) Note: All these MS can be deleted if no DCS-Link is needed!

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

90

T1_INIT.IL14 T1_NETW.IL24

T2_INIT.IL14 T2_NETW.IL24

9.34 At tac hm ent 34: Modb us PC-Progr am s ett in gs (Li ne, Netwo rk ) H46X

X

Standard Configuration: PLC Type Master Bitrate Char length Stopbit No Parity Full doplex Pre idle time Post idle time Char timeout Turnaround time Retransmission Poll cycle time Adress model large PLC node number

Bently 3 1 9600 8 10 0 1 3 0 3 100 3 12 0 1

SSD/AVR 3 1 19200 8 10 0 1 3 0 3 100 2 5 0 2

DCS 3 1 19200 8 10 0 1 3 0 3 100 2 5 0 3

Net number

1

4

3

Remark 3= RTU, 4 =ASCI

10=1 stopbit 0=no parity, 1=odd, 2=even

Must be same as node in Data/Cmd MS-db-element and the flow-control page! 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) Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

91

9.35 At tac hm ent 35: Modb us PC-Progr am s ett in gs (Regist ers ) H546X

Standard Modbus configuration: Bently (single) Registers x1_CMD_R.IL1 45001 x1_CMD_R.IL2 72 x1_CMD_S.IL1 n.a. x1_CMD_S.IL2 n.a.

X

SSD/AVR DCS (redundant) (redundant) 40021 20 40001 20

40001 24 30001 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 Bentl y 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)

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

92

9.36 At tac hm ent 36: Modb us PC-Progr am s ett in gs (fl ow co nt ro l) H64X

X

Read and Write (e.g. SSD/AVR and DCS link)

PLC Status ok Queue

Standard Modbus configuration: Bentl y Write Data IDENT n.a. Read Data IDENT 203

SSD/AVR 216 203

redundant

DCS 216 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!

Not redundant

Only Read (e.g. Bently link)

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

Doc. no.

ABB Switzerland Ltd

Lang.

1AHL 102 709

en

Rev. ind.

6

Page

93

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

Recommend Documents