3. C80-35 Engineer Doc.pdf

8/11/2019 3. C80-35 Engineer Doc.pdf

1/151

P320 SERIES 4 EL-C

ENGINEERING OF A C8035 AUTOMATION CELL

USING OGIV-8035 / CADEPA / P8

DIFFUSION : CONFIDENTIELLE RESTREINTE CONTROLEE LIBRE ACCESSIBILITY CONFIDENTIAL RESTRICTED CONTROLLED FREE

DATE12/12/00

NOMNAME SIGNATURE

ETABLIESTABLISHED AUBARBIER

VERIFIECHECKED TOTH

APPROUVEAPPROVED GRISIER

H T G - E N - 2 0 - W I G - P G 0 0 2 M S M 0 1 A 4 0 0 2 8REV STAT. F/FFIN

SH/SH END Nb F

N of SH

A PROVISOIRE

1/146 146

M A 4 0 0 / 1 A

C e d o c u

m e n t p r o p r i t d A L S T O M

n e d o i t p a s t r e u

t i l i s

, c o p i o u

c o m m u

n i q u

d e s t i e r s s a n s s o n a u

t o r i s a t i o n

T h i s d o c u

m e n t i s t h e e x c

l u s i v e

p r o p

e r t y

o f A L S T O M

a n d s h a l l n o t b e u

s e d

, c o p i e d o r c o m m u

n i c a t e d t o t h i r d p a r t i e s w

i t h o u

t t h e i r p r i o r


2/151

_______________________________________________________________________________________AA M-SM01-A40028.2/A

TABLE DES MODIFICATIONS / MODIFICATIONS TABLE

REV ETABLIESTABLISHED VERIFIECHECKED

APPROUVEAPPROVED DATE MODIFICATIONS STAT.

A AUBARBIER TOTH GRISIER 12/12/00 CREATION OF THE DOCUMENT BPE

7

P A

4 0 1 A


3/151

_______________________________________________________________________________________AA M-SM01-A40028.3/A

CONTENTS

1 PRESENTATION OF ALSPA P320 SERIES EL 4-C USED IN HYDRO SYSTEMS ............ ............ ............. 71.1 ARCHITECTURE.................................................................................................................................................7

Global architecture ............. ............. ............. .............. ............. ............ .............. ............. ............ .............. .............. ... 7 Detail of an automation cell......... ............. ............ .............. ............. .............. ............ ............. .............. ............. ........ 9

1.1.2.1 Simple automation cell ...................................................................................................................................... 9Redundant automation cell .................................................................................................................................................. 9

1.1.3 Limitations .................................................................................................................................................... 91.1.3.1 S8000 ................................................................................................................................................................... 91.1.3.2 Automation cell ................................................................................................................................................. 10

1.1.4 Selected modules............. ............. ............ .............. ............. .............. ............ ............. .............. ............. ...... 111.1.4.1 Baseplates ......................................................................................................................................................... 111.1.4.2 Power supplies ................................................................................................................................................. 111.1.4.3 Processing unit ................................................................................................................................................. 121.1.4.4 S8000 Communication module ...................................................................................................................... 121.1.4.5 F8000 Communication module ...................................................................................................................... 121.1.4.6 SNP Communication modules ....................................................................................................................... 121.1.4.7 MODBUS communication module ................................................................................................................. 131.1.4.8 Discrete input modules .................................................................................................................................... 141.1.4.9 Discrete output modules .................................................................................................................................. 141.1.4.10 Analog input modules ...................................................................................................................................... 141.1.4.11 Analog output modules .................................................................................................................................... 151.1.4.12 Tools to implement the automation cells ....................................................................................................... 15

1.2 ENGINEERING TOOLS..................................................................................................................................... 16

1.2.1 ALSPA P8 software............. ............. .............. ............. ............ .............. ............. ............ .............. ............. .. 171.2.2 CADEPA engineering tool ............ .............. ............. .............. ............ .............. ............. ............ .............. .... 171.2.3 OGIV-8035 database manager ............ .............. ............. ............ .............. ............. .............. ............ ........... 181.2.4 CENTRALOG database customization tool ............. .............. ............ .............. ............. ............ .............. .... 18

1.3 DOMAIN STANDARD PROGRAMS................................................................................................................ 19

1.4 ENGINEERING STAGES .................................................................................................................................. 20

2 DECLARATION AND CONFIGURATION OF THE AUTOMATION CELL....... ............. .............. ............ 22

2.1 PRINCIPLES ........................................................................................................................................................... 22

2.2 PROCEDURE .............. ............. ............ .............. ............. .............. ............ .............. ............. ............ .............. .... 23

2.2.1 Needed tools..... ............ ............. .............. ............. ............. ............. .............. ............. ............ .............. ........ 232.2.2 Stage 1 : declaration of the PLC(s).......... .............. ............. .............. ............ ............. .............. ............. ...... 232.2.3 Declaration of the F8000 exchange areas ........... ............. ............. .............. ............. ............ .............. ........ 27

3 DECLARATION OF THE INPUTS/OUTPUTS ................................................................................................ 28

3.1 PRINCIPLES....................................................................................................................................................... 28

3.1.1 Principles common to all type of I/O ............. ............. ............ .............. ............. .............. ............ .............. . 283.1.2 Discrete inputs ............................................................................................................................................ 293.1.3 Analog inputs .............................................................................................................................................. 303.1.4 Discrete outputs .............. ............. ............ .............. ............. .............. ............ ............. .............. .............. ..... 33

3.1.5 Analog outputs ............................................................................................................................................ 333.2 PROCEDURE .............. ............. ............ .............. ............. .............. ............ .............. ............. ............ .............. .... 343.2.1 Needed tools..... ............. ............ .............. ............. .............. ............ .............. ............. ............ .............. ........ 343.2.2 Stage 2 : declaration of the PLC configuration ............ ............. .............. ............ ............. .............. ............ 343.2.3 Stage 3 : declaration of the inputs/outputs............... .............. ............ .............. ............. ............ .............. .... 363.2.4 Modifications .............. ............. ............ .............. ............. ............ .............. ............. .............. ............ ........... 38

3.2.4.1 Change the 1st reference address or the type of a module ....................................................................... 383.2.4.2 Move an input or an output ............................................................................................................................. 38Move a whole module ......................................................................................................................................................... 39

3.2.5 Stage 4 : printing of the input/output list ............. ............. ............. .............. ............. ............ .............. ........ 39

4 MODBUS IMPLEMENTATION ........... .............. ............. .............. ............ .............. ............. ............ .............. .... 41


4/151

_______________________________________________________________________________________AA M-SM01-A40028.4/A

4.1 INTRODUCTION...............................................................................................................................................41

4.2 DECLARATION OF THE MODBUS INPUTS/OUTPUTS............................................................................... 43

4.2.1 Needed tools..... ............ ............. .............. ............. ............. ............. .............. ............. ............ .............. ........ 434.2.2 Stage 1 : declaration of the Modbus exchange units........... .............. ............ ............. .............. ............. ...... 434.2.3 Stage 2 : declaration of the Modbus slave devices ............. .............. ............ ............. .............. ............. ...... 44

4.2.3.1 Configuration of a PECA or EVA device ....................................................................................................... 46

4.2.3.2 Configuration of a CHESSELL device ........................................................................................................... 484.2.3.3 Configuration of an OTHER device ............................................................................................................... 49

4.2.4 Stage 3 : declaration of the Modbus inputs/outputs.... ............ .............. ............. .............. ............ .............. . 504.2.5 Stage 4 : printing of the Modbus input/output list........ .............. ............ .............. ............. .............. ............ 50

4.3 CONFIGURATION OF MODBUS MODULE ...................................................................................................... 51

4.3.1 In P8 configuration software ............ .............. .............. ............. ............ .............. ............. .............. ............ 514.3.2 pcmexec.bat (for PCM301 only) ............. ............. ............. ............. .............. ............. ............ .............. ........ 514.3.3 hardexec.bat (for PCM301 only) ............ ............. ............. ............. .............. ............. ............ .............. ........ 524.3.4 Procedure to load MBPCMV13, PCMEXEC and HARDEXEC into PCM301.... ............. .............. ............ 53

4.3.4.1 Needed tools ..................................................................................................................................................... 534.3.4.2 Procedure .......................................................................................................................................................... 53

5 F8000 IMPLEMENTATION ............. ............ .............. ............. ............ .............. ............. .............. ............ ........... 54

5.1 DECLARATION OF F 8000 EXCHANGE AREAS .......................................................................................................... 55

5.2 UPDATING OF F 8000 VARIABLES ........................................................................................................................... 59

5.2.1 Extraction of the variables to send on F8000 ............. ............ .............. ............. .............. ............ .............. . 595.2.2 Import F8000 variables ............ .............. ............. ............. ............. .............. ............. ............ .............. ........ 61

5.3 CONSULTATION AND CUSTOMISATION OF F 8000 VARIABLES ................................................................................ 63

5.4 PRINTING OF THE F8000 I NPUT LIST ...................................................................................................................... 64

6 S8000 IMPLEMENTATION ................................................................................................................................ 65

6.1 DECLARATION OF S8000 EXCHANGE AREAS............................................................................................ 66

6.2 UPDATING OF S8000 VARIABLES ..................................................................................................................... 68

6.2.1 Extraction of the variables to send on S8000......... ............. .............. ............ ............. .............. ............. ...... 686.2.2 Import of S8000 variables..... .............. ............ .............. ............. ............ .............. ............. .............. ............ 686.2.3 S8000 exchanges to, from or between unit cells ............. ............ .............. ............. .............. ............ ........... 69

6.3 DECLARATION OF S8000 INPUTS ................................................................................................................. 70

6.4 PRINTING OF THE S8000 INPUT LIST............................................................................................................ 70

7 DUALITY ............................................................................................................................................................... 71

7.1 INTRODUCTION...............................................................................................................................................71

7.1.1 Definition .................................................................................................................................................... 717.1.2 Hardware architecture.......... .............. ............ .............. ............. .............. ............ ............. .............. ............ 717.1.3 Principles ............. ............. ............ .............. ............. .............. ............ .............. ............. ............ .............. .... 72

7.1.3.1 Telecommands and Televalues Centralog updating. .................................................................................. 727.1.3.2 Telecommands and Televalues local HMI updating. .................................................................................. 737.1.3.3 Logical and numerical memories updating. .................................................................................................. 737.1.3.4 Insertion mode control. .................................................................................................................................... 75

7.1.4 Duality safety mode......... ............. ............ .............. ............. .............. ............ ............. .............. .............. ..... 757.1.4.1 Taking over inhibition ....................................................................................................................................... 767.1.4.2 Stopping request ( controller in insertion) ..................................................................................................... 767.1.4.3 Application stopping request (loss of messages) ........................................................................................ 767.1.4.4 Application insertion mode request (loss of messages) ............................................................................. 76

8 EXPORT TO CENTRALOG........ ............. .............. ............. ............ .............. ............. ............ .............. .............. . 77

8.1 E XPORT TO M ICROETE ........................................................................................................................................77

8.2 EXPORT TO CONTROCAD .............................................................................................................................. 78

9 EXPORT TO MAN MACHINE INTERFACE.............. ............. .............. ............ ............. .............. .............. ..... 79

9.1 G ENERATION OF MMI EXPORT FILES ................................................................................................................... 80

10 DUPLICATION OF EXPORTED PROJECT DATA ............ ............ .............. ............. .............. ............ ........... 81

10.1 DUPL ICATION OF S 8000 DATAS ....................................................................................................................... 81

10.2 DUPL ICATION OF F8000 DATAS ...................................................................................................................... 82


5/151

_______________________________________________________________________________________AA M-SM01-A40028.5/A

10.3 D UPLICATION OF CENTRALOG FILE .................................................................................................................. 82

10.3.1 Case of using Controcad ............. .............. ............. ............ .............. ............. ............ .............. .............. . 8210.3.2 Case of using Microete ............ ............ .............. ............. .............. ............ ............. .............. ............. ...... 83

IMPORT / EXPORT TO CADEPA ............ .............. ............. ............. ............. .............. ............. ............ .............. ........ 83

11.1 P RINCIPLES ...................................................................................................................................................... 83

11.1.1 Generation of OGIV_PJ.mne file......... .............. ............. .............. ............ ............. .............. ............. ...... 8311.1.2 Import from CADEPA ............. ............ .............. ............. .............. ............ ............. .............. .............. ..... 8511.1.3 Other programs generated by OGIV-8035............. ............ .............. ............. .............. ............ .............. . 85

12 PROGRAMMING WITH CADEPA ............ .............. ............. ............ .............. ............. .............. ............ ........... 86

12.1 INTRODUCTION.... ............. ............ .............. ............. .............. ............ .............. ............. ............ .............. .... 86

12.1.1 Programs written with CADEPA............ ............. .............. ............ .............. ............. ............ .............. .... 8612.1.2 Interface between CADEPA and OGIV-8035.. ............. ............. .............. ............. ............ .............. ........ 87

12.1.2.1 Variables ............................................................................................................................................................ 8712.1.2.2 Programs generated by OGIV-8035 .............................................................................................................. 87

12.2 PROCEDURE ................................................................................................................................................. 88

12.2.1 Configuring CADEPA ............. ............ .............. ............. .............. ............ ............. .............. .............. ..... 8812.2.1.1 Declaration of default attributes for the projects .......................................................................................... 8812.2.1.2 Setting of the default PLC memory mapping ................................................................................................ 90

12.2.1.3 Page setup for the documentation issued from the main menu ................................................................ 9212.2.2 Creation of a project............ ............ .............. ............. ............ .............. ............. .............. ............ ........... 9312.2.3 Creation and configuration of applications.............. ............. ............ .............. ............. .............. ............ 93

12.2.3.1 Attributes of the applications ........................................................................................................................... 9412.2.3.2 Page setup of the application in Graphite ..................................................................................................... 9512.2.3.3 Preferences to display variables in Graphite ................................................................................................ 95

12.2.4 Import of all the project variables already declared in OGIV-8035 ............. .............. ............ .............. . 9612.2.5 Edition of programs........ ............. .............. ............. ............ .............. ............. ............ .............. .............. . 9612.2.6 Export to OGIV-8035 ........... .............. ............. ............. ............. .............. ............. ............ .............. ........ 97

12.2.6.1 Page setup for the documentation issued from the main menu ................................................................ 97

13 OGIV-8035 UTILITIES ........................................................................................................................................99

13.1 C OHERENCE OF AD D RESSES .............................................................................................................................99

13.2 P ROCESS BITS OR WORDS FREES ....................................................................................................................... 99

13.3 U PDATING OF WORDINGS FROM OTHER PROJECT .............................................................................................. 99

13.4 D ATABASE OPTIMIZATION .............................................................................................................................. 10013.5 FONT .............................................................................................................................................................. 100

13.6 T RANSLATE .................................................................................................................................................... 100

13.7 A DDRESSING UTILITIES .................................................................................................................................. 101

13.7.1 Partial addressing ............ ............ .............. .............. ............. ............ .............. ............. .............. .......... 10113.7.2 Reset Ranks........ ............. ............. .............. ............. ............ .............. ............. .............. ............ ............. 10113.7.3 Display file......... ............. ............. .............. ............. ............ .............. ............. .............. ............ ............. 10213.7.4 Browser database ............. ............ .............. ............. .............. ............ .............. ............. .............. .......... 10213.7.5 Loading CADEPA....... ............. ............ .............. ............. .............. ............ ............. .............. .............. ... 10213.7.6 Saving ................................................................................................................................................... 103

13.7.6.1 OGIV-8035 ...................................................................................................................................................... 10313.7.6.2 CADEPA .......................................................................................................................................................... 103

13.7.7 Restoring.............. ............. ............ .............. ............. .............. ............ .............. ............. .............. .......... 10313.7.7.1 OGIV-8035 ...................................................................................................................................................... 104

13.7.7.2 CADEPA .......................................................................................................................................................... 10414 TEST ..................................................................................................................................................................... 105

14.1 I NTRODUCTION .............................................................................................................................................. 105

14.2 P ROCEDURE ................................................................................................................................................... 106


6/151

_______________________________________________________________________________________AA M-SM01-A40028.6/A

RELATED DOCUMENTS

[1] ALS 52102 c Alspa C85-35 and 80-25 PLCs Reference Manual

[2] ALS 52117 e Alspa C85-35 PLC Installation Manual

[3] ALS 52118 b Alspa C85-35 PLC I/O Module Specifications

[4] ALS 52201 b1 Alspa P8-25/35 programming software for Alspa C80-35 and 80-25PLC User Manual

[5] ALS 52202 a Hand-Held Programmer for Alspa C80-35, C80-25 and C80-05PLCs User's Manual

[6] ALS 52519 e FIP bus controller (FBC) for Alspa C80-35

[7] ALS 52402 d Programmable Coprocessor Module (PCM) and support software for

ALSPA 8000 PLCs Users Manual

[8] HSC000CAT97A APG HORNER ELECTRIC Product Catalogue (Pages 1 to 16)

[9] HFK-90XXX Technical sheets related to HORNER I/O modules HE693

[10] FA-DOC-50725 CADEPA Windows version 6e User Guide

[11] FA-DOC-55103 GRAPHITE Windows version 2.2 User Guide (Graphite editor)

[12] FA-DOC-50718 CADEPA Windows version 6.0 User Guide for ALSPA 8000 seriePLCs

[13] FA-DOC-50736 CADEPA Windows Installation Procedure

[14] P-TP11-A43510eA P320 EL Domaine 4-C for S8000-E. INSTALLATION AND USER'SGUIDE

[15] P-TP11-A43511eA P320 EL Domaine 4-C for S8000-F. INSTALLATION AND USER'SGUIDE


7/151

_______________________________________________________________________________________AA M-SM01-A40028.7/A

1 PRESENTATION OF ALSPA P320 SERIES EL 4-C USED IN HYDRO SYSTEMS

1.1 ARCHITECTURE

1.1.1 Global architecture

A C80-35 automation cell may be composed of:

- "MAIN" = cell controller

A simple automation cell has only one MAIN PLC.

A redundant automation cell is a cell with 2 MAIN PLCs

The MAIN PLC houses the application program (generated by CADEPAengineering tool). It receives orders (TC) and set points (TVC) from CENTRALOGand sends discrete (TS) and analog (TM) variables to CENTRALOG. Those TSare 100 ms-timetagged.

The "MAIN" PLCs can exchange inter-controller variables through S8000 network.

- "IHR" (Input - High Resolution)

The IHR PLCs time-tag discrete inputs with a 1ms resolution. They don't haveany application program but house a software which performs :

. the time-tagging of up to 247 inputs ( Refer to 1.1.3.2)

SNPNETWORK MAIN

IHRi

S8000 SITE NETWORK

F8000 FIELDNETWORK

MAIN MAIN MAINMMI

IHRi

SUBi

CENTRALOG


8/151

_______________________________________________________________________________________AA M-SM01-A40028.8/A

. the updating of the messages of 1 ms time-tagged events sent toCENTRALOG through the MAIN PLC.

The current state of their inputs is available in MAIN PLC to use in the application

program.

IHR PLC are not redundant.

- "SUB" = field controller

The SUB PLCs contain the I/O of the redundant cells (except 1ms time-taggedinputs). The SUB PLCs may also perform delocalized subfunctions of MAINPLC. They house application programs (generated by CADEPA). Theycommunicate with MAIN PLC through F8000 network and are not linked to S8000network. TS and TM from those PLCs are therefore sent to CENTRALOG throughMAIN PLC. The TS are timetagged in MAIN PLC.

In hydro standard architectures, SUB PLC are not redundant.

- S8000 NETWORK

The S8000 site network is used to link all the PLCs of a project to CENTRALOG.This network can be of 2 types:

. S8000-E ETHERNET network with a speed of 10 or 100 Mbits/s

. S8000-F FIP network with a speed of 1 Mbit/s

- F8000 network

The F8000 field network with a speed of 1 Mbit/s is used to link all the entities of aC80-35 automation cell (MAIN, IHR, SUB).

- SNP network

The SNP network is used to link the PLC to the local Man Machine Interface.


9/151

_______________________________________________________________________________________AA M-SM01-A40028.9/A

1.1.2 Detail of an automation cell

1.1.2.1 Simple automation cell

1.1.2.2 Redundant automation cell

1.1.3 Limitations

1.1.3.1 S8000

Maximum number of automation cells linked to S8000 : 16 One of them may be a regrouping PLC ie receive more variables than the others.

Maximum number of TS, not including high-resolution timetagged inputs, from anautomation cell:

- 1024 for a S8000-F network

- 1024 for a S8000-E network

SNP

SNP

MMI

SUB-1

F8000

S8000-E or F

Simple automation cell withhigh resolution inputs and sub-controllers

MBUS

P8 orHHP

MAINrack 1

MAIN

rack 2

MAIN rack 3

MAIN rack 0

MBUS

SUB-3

SUB-2

IHR-1

IHR-2

S8000-E or F

SNP SNP

MMI

MAIN

SUB-1

SUB-2

IHR-1

IHR-2

F8000

STANDBY

Redundant automation cell withhi h resolution in uts and sub-controllers

MBUS

P8 orHHP

SUB-3


10/151

_______________________________________________________________________________________AA M-SM01-A40028.10/A

Maximum number of TC to an automation cell:

- 256 for a simple automation cell

- 224 for a redundant automation cell

Maximum number of TM from an automation cell: 222

Maximum number of TVC: 32 to a standard cell (192 to a regrouping PLC)

Maximum size of an inter-controller message broadcast to a MAIN PLC to theother MAIN PLCs: 20 words (the 1st one is an utility word processed by theDOMAIN standard blocks)

Maximum size of an inter-controller message sent by a MAIN PLC to theregrouping MAIN PLC: 64 words (the 1st word is an utility word processed by theDOMAIN standard blocks).

1.1.3.2 Automation cell

The standard F8000 configuration available for hydro applications allows up to 2IHRs and up to 3 SUBs in an automation cell.

Should more IHR or SUB be needed, a special F8000 configuration could bedeveloped.

An IHR PLC can't have any expansion rack. The number of discrete inputs time-tagged by an IHR PLC is therefore limited to :

- 8x32 - 1 (SYNCHRO) - 8x2 (polarity control) = 239 when 32-input modules areused and 1 input out of 16 is dedicated to polarity control.

- 8x32 - 1 (SYNCHRO) - 8 (polarity control) = 247 when 32-input modules areused and 1 input out of 32 is dedicated to polarity control.

- 8x16 - 1 (SYNCHRO) - 7 = 119 when 16-input modules are used.


11/151

_______________________________________________________________________________________AA M-SM01-A40028.11/A

1.1.4 Selected modules

1.1.4.1 Baseplates

- IC693CHS391 : 10-slot CPU baseplate

- IC693CHS397 : 5-slot CPU baseplate (to use on redundant MAIN PLC)

- IC693CHS392 : 10-slot expansion baseplate

- IC693CHS393 : 10-slot remote baseplate (when there is more than 15 m betweenthe CPU baseplate and the I/O baseplate)

1.1.4.2 Power supplies

- IC693PWR324 : supplies 30W (15W in 5 Vdc and 15 W in 24 Vdc) from 120 to240 Vac or 125 Vdc.

- IC693PWR330 : also supplies 30W (15W in 5 Vdc and 15 W in 24 Vdc) from 120to 240 Vac or 125 Vdc but those 30 W may be all consumed on the 5 Vdc polarity.

- IC693PWR331 : supplies 30W (15W in 5 Vdc and 15 W in 24 Vdc) from 24 Vdc.Those 30 W may be all consumed on the 5 Vdc polarity.

In most cases, more than 15 W are needed in 5 Vdc and PWR324 power supplydoes not fit. Therefore the load consumption must be estimated before choosingthis power supply card.


12/151

_______________________________________________________________________________________AA M-SM01-A40028.12/A

1.1.4.3 Processing unit

ReferenceCommunication

ports UseProgram

space

IC693CPU363 SNP serial ports S8000-F MAIN PLC with MMI

SUB PLC with MMI

240 K

IC693CPU364 Ethernet S8000-E MAIN PLC 240 K

IC693CPU350 None IHR

SUB PLC without MMI and withsmall application program*

32 K

IC693CPU360 None S8000-F MAIN PLC without MMI

SUB PLC without MMI and withbig application program

240 K

* A CPU350 for a SUB PLC with MODBUS communication and analog conversionand filtering still have room for a little application program

1.1.4.4 S8000 Communication module

- IC693BEM340 (also called FBC30) must be used in MAIN PLC connected toS8000-F network

1.1.4.5 F8000 Communication module

- IC693BEM340 (also called FBC30) must be used in MAIN , IHR and SUB PLCs

1.1.4.6 SNP Communication modules

P8 software, the Hand Held Programmer (IC693PRG301) and MMI pieces ofsoftware (INTERACT, CITECT) use SNP protocol to communicate with C80-35controllers.

On each C80-35 controller, a serial port is available on the power supply module tocommunicate with P8 or HHP.


13/151

_______________________________________________________________________________________AA M-SM01-A40028.13/A

On CPU363 card, 2 serial ports are available, allowing SNP protocol. They can beused to communicate with MMI.

On CPU364, CPU350 and CPU360 cards no SNP serial port is available.

- IC693CMM311 must be used in these cases to communicate with MMI.Thismodule provides 1 RS232 and 1 RS232/485 serial ports on witch SNP protocol isavailable.

To link a C80-35 PLC serial port to the PC on which P8 or MMI software is running,

- IC690ACC901 converter + cable may be used.

1.1.4.7 MODBUS communication module

The Programmable Coprocessor Module (PCM) IC693PCM301 , loaded withMBPCMV16 software allows the C80-35 PLC to be the master subscriber on 1 or 2MODBUS networks. It has 2 serial ports; one supporting RS232 only, the other oneRS232 or RS485.

The software IC641SWP023 (TERM F) is needed to load MBPCMV14 and otherfiles in PCM. TERM F has to be loaded in a PC that may be connected to PCMmodule by means of IC690CBL702 cable. Only one set of IC693SWP023 software+ IC690CBL702 cable is needed for a whole project.

- CF693MBM100 is a PCM module already loaded with MBPCM software. Its firstserial port supports RS232 only, its second serial port supports RS485 only. Nofile have to be loaded in MBM100 card. Therefore, SWP023 and CBL702 are notneeded.

PWR330ACC901

RS232, 2m


14/151

_______________________________________________________________________________________AA M-SM01-A40028.14/A

1.1.4.8 Discrete input modules

The numerous discrete input modules available for a C80-35 PLC are described indocument [3]: ALS 52118 "Alspa C80-35 PLC I/O Module Specifications".

Those chosen for standards are:

- IC693MDL655 : 32 fast discrete inputs, 24 Vdc positive/negative logic.

Those inputs are fast enough to be 1ms - timetagged in IHR PLCs.

The front side of the module doesn't have any terminal board to wire the inputsbut 2 24-point male connectors. Therefore interface modules must be used forinput wiring.

- The 16-discrete 24 Vdc input modules IC693MDL645 (slow) and IC693MDL646(fast) have also been used. Their front side terminal block may avoid to use

interface modules to wire the inputs (ex. C80-35 PLCs located on the rear side ofa mimic board).

1.1.4.9 Discrete output modules

Refer to document [3] (ALS 52118) for the description of all the available I/Omodules.

The discrete output module chosen for standard is:

- IC693MDL753 : 32 static outputs, 12/24 Vdc positive logic, 0,5A max. Samecomment as IC693MDL655 for output wiring.

The following modules have also been used:

- IC693MDL740: 16 static outputs, 12/24 Vdc positive logic, 0,5 max, used for testsas its front side terminal board makes it easy to wire.

- IC693MDL940: 16 relay outputs, 2A max

1.1.4.10 Analog input modules

Refer to :

- Document [3] (ALS 52118) for the description of all the available IC693XXXanalog input modules

- HFK-90XXX technical sheets for HE693XXX modules.

The analog input module chosen for standards is:


15/151

_______________________________________________________________________________________AA M-SM01-A40028.15/A

- IC693ALG223 : 16 analog inputs 0/4-20mA (1 common point for the 16 inputs).

- IC693ALG222 : 16 analog inputs 0-10V may also be used when voltage inputsare needed but the loss of signal won't be detected anymore.

- HE693RTD66x is also used. It provides 6 isolated RTD inputs with or without a 50Hz or 60 Hz filter.

1.1.4.11 Analog output modules

The analog output modules chosen for standards is:

- IC693ALG392 : 8 analog outputs 0/4-20 mA or -10V/0-10V.

- HE693DAC420 : 4 isolated analog outputs, 0/4-20mA, has also been used

1.1.4.12 Tools to implement the automation cells

The tools needed to implement the automation cell are:

- Alspa P8 software : IC641SWP326 (+ IC690ACC901 converter and cable) (seechapter 1.2)

- The Hand Held Programmer (HHP) IC693PRG301 is absolutely needed toconfigure F8000 or S8000-F communication module.

HHP is also very useful for test purpose as it's a convenient means to start/stopthe PLC and read/write variables in the PLC without using P8.


16/151

_______________________________________________________________________________________AA M-SM01-A40028.16/A

OGIV8035

CADEPA

P8

1.2 ENGINEERING TOOLS

MMI

CENTRALOGcustomisation tool

DATABASE

DATABASE

DATABASEAND

PROGRAM

LADDER CODE

DATABASE


17/151

_______________________________________________________________________________________AA M-SM01-A40028.17/A

1.2.1 ALSPA P8 software

P8 is the configuration and programming software of the C80-35 PLCs. It is

absolutely necessary to :- Declare the PLC configuration and load it into the PLC

- Write the PLC "_main" block and declare all the program blocks used by theapplication program : DOMAIN blocks and application blocks (the DOMAIN blocksare available on a floppy disk ; the content of application blocks is generated byCADEPA software)

- Load the whole program into the PLC

1.2.2 CADEPA engineering tool

CADEPA is a SFC (Sequential Function Chart) editor with an ALSPA 8000translator.

CADEPA ALSPA 8000 translator translates programs written with CADEPA in SFCor textual language into C80-35 language.

It runs under WINDOWS 95, 98 or NT environment and is available in French orEnglish.

The reasons for using CADEPA are:

1. The programming document , written with SFC standardised language, textuallanguage, 27 characters mnemonics for the variables and as many commentsas needed, is clear enough to serve as a detailed specification document. That allows to ensure the coherence between the detailed specification andthe program running in the PLC and avoids the manual translation of thedetailed specification into a programming language.

2. The SFC of the functional description may also be designed with CADEPA.

3. CADEPA offers "copy" facilities much better than those provided by P8 andassociated with OGIV-8035 allows to address variables more efficiently than P8.

4. OGIV-8035 is interfaced with CADEPA not with P8.


18/151

_______________________________________________________________________________________AA M-SM01-A40028.18/A

1.2.3 OGIV-8035 database manager

OGIV-8035 is a database tool running on Microsoft FOXPRO databasemanagement system. It manages the variables of each controller.

The databases of CENTRALOG customisation tool, CITECT or INTERACT ManMachine Interface and CADEPA are updated from OGIV-8035 databases. Thatensures the consistency of the variables in the PLCs, CENTRALOG and MMI .

For each PLC, OGIV-8035:

- Prints lists of selected variables : I/O list, MODBUS I/O list, variables exchangedon the various networks ...

This function may be used even when the controller is not programmed withCADEPA.

- Assigns addresses to all the variables of a controller. This function isabsolutely needed when the process of a controller is split into severalapplications in CADEPA.

- Ensures the consistency of the variables between the PLCs andCENTRALOG. For that, OGIV-8035 updates CENTRALOG with all the variablesflagged to be TS, TC, TM or TVC. The attributes loaded into CENTRALOG byOGIV-8035 are for example the name ( Var ref ) of the variable, its label , row ,state_1 message, related controller, operative unit ... Refer to appendix C for thecomprehensive list of those attributes. OGIV-8035 automatically assignsaddresses to TC and TVC according to their row. OGIV-8035 affects rows to TSand TM then generates CADEPA program files to arrange them accordingly in theTS and TM tables sent to CENTRALOG.

- Idem for the consistency of the variables between the PLCs and their MMI.

- Ensures the consistency of the variables exchanged on F8000 and S8000networks. The variables sent by a PLC on F8000 or S8000 networks aredeclared in OGIV-8035. OGIV-8035 then generates CADEPA program files toarrange those variables in the F8000 or S8000 messages. It updates accordinglythe received variables in the receiving PLCs.

- Generates cross-references for a whole PLC.

1.2.4 CENTRALOG database customization tool

It may be MICROETE (DOS environment) or CONTROCAD (NT environment).Theyallow declaring all the variables processed by CENTRALOG with all their attributes.


19/151

_______________________________________________________________________________________AA M-SM01-A40028.19/A

Some of those attributes may be updated by OGIV-8035 (Refer to 2.1.3). The otherones (such as threshold values, appearance in a log ...) have to be declared usingCENTRALOG customisation tool.

CENTRALOG customisation tool is not described in this document as it is not aengineering tool for the PLC but for CENTRALOG.

1.3 DOMAIN STANDARD PROGRAMS

The DOMAIN is a set of programs, written with P8 programming software, whichcarry out system functions often implemented in our PLCs. Their aim is to :

- reduce the application studies by sparing the user the programming of systemfunctions,

- provide well-optimised and well-tested functions,

The DOMAIN consists of a P8 folders called STD_S8E (MAIN controllers withETHERNET network), STD_S8F (MAIN controllers with FIP network) and STD_SUB(sub-controllers) with :

- "_main" program where all the DOMAIN blocks are called in the proper order,

- all the DOMAIN program blocks.

Refer to appendix E for the detailed description of each DOMAIN block.

Below is the list of functions currently available in the DOMAIN. On request, otherprocessings can be added:

- PLC management : reset of the PLC data memory (at 1st scan), monitoring ofPLC faults, interface with MMI

- Validation of analog inputs and conversion of raw values into physical units.

- F8000: detection of the presence of the other subscribers. Multiplexing of theanalog data exchanged between the sub-controllers and the main controllers.

- S8000: communication services (communication with CENTRALOG, inter-controller facilities) and transfer of discrete variables, received from S8000 inword messages, into discrete references easily accessible for the applicationprogram.

- MODBUS: Communication with PECA or EVA electric measurement acquisitionunit, with CHESSELL temperature acquisition unit and many other devices.


20/151

_______________________________________________________________________________________AA M-SM01-A40028.20/A

1.4 ENGINEERING STAGES

(M = Manual operation ; A = Automatic operation)

Stage O G I V

C A D E P A

P 8 Comment Related document

1. Definition of PLCconfiguration M

Composition of each rack andI/O address of the modules

Included in the PLCI/O list

2. I/O declaration M PLC I/O list

3. MODBUS I/O declaration M MODBUS I/O list

4. Functional specification M

Functional

specificationdocument.5. Detailed specification= programing

Operations (SFC + textuallanguage)

M Programmingdocument (CADEPA)

Creation of variables (exceptI/O variables)

A Variables used in operationsare automatically created

Cross references(OGIV-8035)

Comments M

Exchange programming(F8000, S8000, MMI)

M The variables to send are

flagged in OGIV whichgenerates programs forCADEPA accordingly

Exchange lists

(OGIV-8035)

Variable addressing A

6. MMI programmation

Mimic views Tool = INTERACT or CITECT

Database A Imported in INTERACT orCITECT from OGIV

Alarms A OGIV generates the alarm filesfor those 2 MMI.


21/151

_______________________________________________________________________________________AA M-SM01-A40028.21/A

Stage O G I V

C A D E P A

P 8 Comment Related document

7. Update of CENTRALOGdatabase

A Loaded by OGIV-8035Refer to appendix C for the listof attributes updated by OGIV.

8. Building-up of the folder(program + configuration) toload into the PLC

Configuration M

_main program M Call of DOMAIN and CADEPAprogram blocks

Listing of _mainprogram

contents of the programblocks : DOMAIN M From DOMAIN floppy disk

CADEPA A

Others M Operations not available inCADEPA (double-integers forex.) must be written with P8.

The listing of theblocks is not useful, asits the translation ofCADEPA program.

9. Tests

Load program andconfiguration into the PLC

M

Write a simulation program M A

On-line visualisation of theprogram, reading and writingof variables.

M M

Modifications M M OGIV-8035 is needed only ifnew variables are created or ifflags are modified (TS, TC, )

10. Duplication of UNIT PLC The use of discrete inputs toencode the PLC number avoidsduplication of CADEPAprogram P8 folders, and OGIVdatabase: they are valid for allthe units.

CENTRALOG database A Duplicated by OGIV-8035

11. Storage M M Variables databases, programs,P8 folders


22/151

_______________________________________________________________________________________AA M-SM01-A40028.22/A

2 DECLARATION AND CONFIGURATION OF THE AUTOMATION CELL

2.1 PRINCIPLES

- In OGIV-8035, each controller, MAIN, IHR or SUB is a project.

- In CADEPA, each MAIN and SUB PLC is a project. CADEPA does not know theIHR PLC as they do not house any application program.

The MAIN and SUB projects declared in OGIV-8035, are automatically createdby OGIV-8035 in CADEPA.

- For the 2 MAIN PLC of a redundant cell, 1 project only is created inOGIV/CADEPA/P8.

- To create an automation cell, the user first create it his MAIN PLC then declarethe cell architecture. The IHR or SUB are then automatically created.

- The user must then configure the F8000 exchange areas in the MAIN and SUBPLCs of the automation cell

This operation should be performed prior to the I/O declaration as it allows OGIVto know which areas are available for inputs and outputs


23/151

_______________________________________________________________________________________AA M-SM01-A40028.23/A

2.2 PROCEDURE

2.2.1 Needed tools

OGIV-8035 only.

2.2.2 Stage 1 : declaration of the PLC(s)

Select " Project " "New ". The following screen is displayed:

Use TAB. key to move from one field to the next one.

Name : Name of the MAIN project in OGIV-8035 and in CADEPA.7 characters

Designation : 40 characters

S8000 subscriber Nr : Number of the automation cell on S8000 :1 to 15 = standard MAIN PLCs16 = regrouping PLC (MIMIC)

PLC name for ETE : Name given to the automation cell in CENTRALOGFormat = XXXyyy, X = letter or number y = number. Mustbe filled for PLCs connected to S8000. Also used to nameexport files toward CITECT MMI.Must be unique on the PC


24/151

_______________________________________________________________________________________AA M-SM01-A40028.24/A

Operative Unit Ref.: 2-figure number of the operative unit. (Refer to Appendix B,to know its utilisation).

Local.: The local project are those implemented in the current PC

(OGIV-8035+CADEPA+P8).The projects implemented on other PCs must also bedeclared if they send variables to local project throughF8000 or S8000. They are not local.Only local projects can be selected in Project Select.

Note: Once the project is created, the project name can't be modified.

"Project " "Edit " allows to consult the parameters of the current PLC and to modifyDesignation, PLC name for ETE, OU number and S8000 Subscriber Number.

- Declare the new project as follow :

- Click on the Creation button, then:

- Click on the Cell architecture button, then:


25/151

_______________________________________________________________________________________AA M-SM01-A40028.25/A

- Declare the cell architecture by a click on the white square of the desiredcontrollers ( simple or redundant MAIN PLC with IHR1, IHR2, SUB1, SUB2,SUB3). Declare an IHR1 PLC as follow:

Redundant controller

IHR1 PLC DATA TO DECLARE

- Name of the IHR1 PLC, 7 characters max.- Designation of the IHR1 PLC, 40 characters- Operating unit reference


26/151

_______________________________________________________________________________________AA M-SM01-A40028.26/A

- Declare a SUB1 PLS as follow:

- Once all the controller of the cell are declared, click on the Exit button. Then,verify that OGIV has automatically created all the declared controllers. To dothis, select Project , Select :

- No project is created for the standby controller because the same program andvariables are loaded in the two MAIN controllers

SUB1 PLC DATA TO DECLARE

- Name of the SUB1 PLC, 7 characters max.- Designation of the SUB1 PLC, 40 characters- Operating unit reference

GTA01_I, GTA01_S andGTA01 controllers arecreated


27/151

_______________________________________________________________________________________AA M-SM01-A40028.27/A

2.2.3 Declaration of the F8000 exchange areas

- For each MAIN and SUB controller of the cell, the user must then :

. Select the project

. Customise its F8000 exchange areas ( refer to chapter 5 ).


28/151

_______________________________________________________________________________________AA M-SM01-A40028.28/A

3 DECLARATION OF THE INPUTS/OUTPUTS

3.1 PRINCIPLES

3.1.1 Principles common to all type of I/O

- There is no rule linking the location of a C80-35 module to its related references inthe PLC data memory (I/O variables for I/O modules, state bits for communicationmodules).

When entering the PLC configuration in P8 configuration software, the userdeclares the modules, their slots and the first reference assigned to each of them.

- The I/O declaration is performed using OGIV-8035. The steps are:

declaration of the PLC configuration in OGIV-8035 which then generates allthe I/O references,

capture of the mnemonic, label and possibly other attributes (refer to appendixC for the list of attributes of the I/O references),

printing of the standard I/O list : see extract appendix H-1.

- When an automation cell comprises several PLCs (MAIN, IHR ...), an individualI/O list is issued for each of them (but they may be gathered in a singledocument).


29/151

_______________________________________________________________________________________AA M-SM01-A40028.29/A

3.1.2 Discrete inputs

Below is a list of rules to follow (C = compulsory rule, A = advice only):

RULES FOR DISCRETE INPUTS Due to C/A

1 The 1st reference of a discrete input module mustbe %I(8n+1) with n = integer from 0 to 255.

P8 C

2 The PLC %I data memory assigned to discreteinputs is configured in OGIV when declaring theF8000 and the S8000 exchanges.

OGIV-8035 won't accept inputsout of this area.

C

3 The 1ms time-tagged inputs of an IHR PLC musthave references from %I0001 to %I0256 .

IHR software C

4 %I0002 is the synchronisation signal . S8000 communicationsoftware

C

5 The mnemonics of the inputs (name in CADEPAand OGIV) must begin with " li_ ".Ex: li_91lrl001jd_o

OGIV-8035 C

6 Some inputs should be dedicated to polarityacquisition. There are 2 options:

1. One input out of 16 is dedicated to polarityacquisition : %I0001 is the validation bit for%I0002-16; %I0017 for %I0018-32

It allows to detect the loss of the input module,of the acquisition polarity or of the interfacemodule

2. The 1st input of each module acquires theacquisition polarity and validates the otherinputs. For 32-input modules, the loss of themodule or of the acquisition polarity isdetected, not the loss of the 2 nd interfacemodule or of its flat cable.

To be used as validation bitsfor CENTRALOG

IHR software needs thoseinputs to process the validationbits of the 1ms-timetaggedinputs.

OGIV-8035 needs them toprocess the validation bits ofthe inputs acquired by theMAIN or SUB PLCs.

C

7 For MAIN or SUB PLCs to duplicate (ex : units),inputs should be used to encode PLC number.

It allows writing instructions dependent on the PLCnumber for processing specific to a particular unit.

Those inputs must be chosen from %I0003 to 16.

Trick to avoid duplication.

(%I0001 to 16 are not reset byDOMAIN at 1st scan)

A


30/151

_______________________________________________________________________________________AA M-SM01-A40028.30/A

3.1.3 Analog inputs

- The standard analog inputs are 4-20mA signals acquired on 0-20mA channels .Value "0" thus indicates the loss of the input signal.

0-10V input signals may also be acquired. In that case, 0-10V channels are usedand thus value "0" does not mean anymore a loss of signal.

The raw values for 0/4-20mA or 0-10V input modules range from 0 to 32000points.

The 3 least significant bits are not used. Therefore the resolution is 8 points whichfor 0-20mA channels gives 20mA / (32000/8) = 5A resolution.

- The analog inputs must be processed by DOMAIN program block ( DAI_ALG ) to

check their validity and possibly convert them into physical units. (The thresholddetection is not performed by DOMAIN). Refer to its technical sheet in appendixE.

- For each analog input, OGIV-8035 generates 3 references. They are the DOMAINoutputs:

. Raw value 0/6400 - 32000 points

. Physical value in physical units

. Validation bit

- OGIV-8035 generates a program file for CADEPA ( og_anai.gig file) with thecustomisation of analog inputs at first scan: rack, slot and last channel number ofeach analog input module, min/max values of the analog inputs to convert intophysical units...


31/151

_______________________________________________________________________________________AA M-SM01-A40028.31/A

- Below is a list of rules to follow (C = compulsory rule, A = advice only):

RULES FOR ANALOG INPUTS Due to C/A

1 To detect the loss of a channel, the input signalshould be 4-20mA whereas the channels of the input modules are configured to 0-20 mA . Thenormal range of an input in then 6400-32000points .

DAI_ALG: detection of the lossof the signal.

A

2 The 1 st register reference assigned to an analoginput module in the PLC configuration must be

%AI0001 / 17 / 33 / 49 / 65 / 81 / 97 / 113.Only 8 analog input modules can be handled.

DAI_ALG C

3 When configuring the PLC in P8, the %I addressof %AI(16(n-1)+1) module, 1 n 8, must be :%I(8(n-1)+1777) and the %I size = 8

DAI_ALG C

4 The mnemonics of the raw and physical valuesmust begin with " di_ ", of the fault bit with " li_ "

OGIV-8035 C

5 The raw value must have a mnemonic , label andunit in OGIV-8035 (except spare inputs). OGIV-8035: the raw value isprinted in the I/O list not thephysical value.

C

6 To differentiate raw values from physical values:add "_pts" at the end of raw value mnemonics or"_phy" at the end of physical value mnemonics .Both solutions are possible. But, for inputs bothsent to CENTRALOG and MMI, the best one is

_pts at the end of raw values . Because, the TMfor CENTRALOG and the TM for MMI havebetter be the physical values.

The maximum number ofcharacters for a data mnemonicin the CENTRALOG is 20.Avoid different conversion inCENTRALOG and MMI.

A

7 V mini and V maxi attributes must be filled forvariables sent to CENTRALOG or MMI.

Given by OGIV-8035 toCENTRALOG and MMI

C


32/151

_______________________________________________________________________________________AA M-SM01-A40028.32/A

RULES FOR ANALOG INPUTS Due to C/A

9 The validation bit must have a mnemonic if the

analog input is sent to CENTRALOG. It can not beflagged as TS for CENTRALOG.

OGIV-8035 uses it to process

the invalidating bit of the TM.

C

10 The PLC mini and PLC maxi attributes of theRAW VALUES is 6400 (possibly 0 or 32000) and32000. They are automatically written by OGIV-8035), but may be modified.

The PLC mini and PLC maxi attributes of thePHYSICAL VALUES are the min. and max.physical values used by DAI_ALG to convert theinput:

dd_ana_inp_min/max_0xxx ).

If n decimals are needed :PLC mini / PLC maxi = V mini / V maxi *10n

ex : n =2 V mini = 0 PLC mini = 0V maxi = 13,80 PLC maxi = 1380

OGIV-8035 generates aprogram file for CADEPA withthe customisation of the analoginput modules.

- RTD modules may occasionally be used. The raw values of the RTD inputs arenot expressed in points but are a multiple of the C or F physical value. The

multiplication coefficient depends on the configuration of the module.DOMAIN block DAI_RTD validates each channel of a RTD module and updatesthe raw value and validation bit of each input. DAI_RTD does not convert the rawvalues into physical values.

If the physical value is needed in the application program, the user must write in aCADEPA graph the instructions to update at each scan the physical value(generated by OGIV-8035) with the raw value divided by the proper coefficient. Ifit is not needed in the application program but has to be sent to INTERACT, thebetter is to sent the raw value to INTERACT and write the division in INTERACT.

Among the 8 possible analog input modules, 7 may be RTD modules. Their 1 st

%AI reference must be %AI(16n+1), 0 n 6.When configuring a RTD module in P8, the 16 %I bits of module %AI(16n+1)must be %I(16n+929).


33/151

_______________________________________________________________________________________AA M-SM01-A40028.33/A

3.1.4 Discrete outputs

Below is a list of rules to follow (C = compulsory rule, A = advice only):

RULES FOR DISCRETE OUTPUTS Due to C/A

1 The 1st reference of a discrete output modulemust be %Q (8n+1) with n = integer from 0 to255.

P8 C

2 The PLC data memory assigned to discreteoutputs is %Q0001 to %Qxxx with xxx = 384 bydefault.

OGIV-8035 won't acceptoutputs out of this area.

C

3 The mnemonics of the outputs (names inCADEPA and OGIV) begin with " lo_ ". Ex:lo_91lrl001jd_o

OGIV-8035 C

4 An output of the MAIN PLC may be used aswatchdog . To do so, the application program hasto copy the bit ld_plc_run in this output.

A

3.1.5 Analog outputs

Analog outputs are not processed by DOMAIN.

Below is a list of rules to follow (C = compulsory rule, A = advice only)

RULES FOR ANALOG OUTPUTS Due to C/A

1 They should be consistent with analog inputs:6400-32000 points for 4-20mA signal or 0-32000for 0-10V signals.

To avoid conversion of analoginputs due to be also outputed.

A

2 Their mnemonics must begin with " do_ ". OGIV-8035 C


34/151

_______________________________________________________________________________________AA M-SM01-A40028.34/A

3.2 PROCEDURE

3.2.1 Needed tools

OGIV-8035 only.

3.2.2 Stage 2 : declaration of the PLC configuration

- Select PLC config. Hardware

The configuration screen is displayed:

RACK: Number of the displayed rack: 0 to 3. To change rack, click on"next " or "previous " button

SLOT: Number of the current slot: 1 to 10. To select a slot, click on it.The radio button of the selected slot becomes black.

Input validation: 16 (default value) 1 discrete input out of 16 is dedicated topolarity acquisition in order to validate the 15 following inputs.

32 : 1 discrete input out of 32 is dedicated to polarity acquisition.


35/151

_______________________________________________________________________________________AA M-SM01-A40028.35/A

A new project is created with a default configuration including CPU363, S8000-Fand F8000 communication modules with the references assigned to their state bits.

The default configuration is not valid for the MAIN and IHR PLCs with an otherconfiguration (S8000-E). In this case, It has to be changed with the correct CPU andcommunication modules. In all case, it has to be complemented with discrete inputmodules for IHR, with Modbus and I/O modules for MAIN.

- To add a module:

click on the desired slot to select it

choose the module in the pop up list at the bottom of the screen

Click on the 1st reference address (triple click to select the whole field) andenter the desired address. OGIV-8035 automatically calculates the lastreference address. To assign addresses, refer to the rules described in 2.1.

- SUB PLCs don't have any S8000 communication module. To delete it from slot03:

click on slot 3

replace BEM34S module by the real desired module.

- To delete a module , replace it by SPARE. If its associated inputs or outputs werealready declared they are then deleted!

- To move a module , if its I/O have not yet been generated, just replace it bySPARE and declare it again in another slot. Otherwise, use " PLC config. ""Switching modules "

Once the configuration is completed, click on " Ok ": OGIV-8035 then generates allthe I/O references .


36/151

_______________________________________________________________________________________AA M-SM01-A40028.36/A

3.2.3 Stage 3 : declaration of the inputs/outputs

- Select " Variables " "Hardware Inputs " or "Hardware Outputs " "Logical " or"Analog ". FoxPro standard browse window is displayed.

- For each record, the fields of the following table are displayed. Refer to appendixC to know their meaning and format.

- To copy / paste a single field: use CTRL C / CTRL V .

- To copy / paste all the fields of a variable except location , address and var ref of arecord in another record: use ALT C / ALT V (ALT V only updates the emptyfields)

- To fill or modify var. ref. use ALT R (not operate when Centralog or MMI isempty)

FIELD Logical Inputs Logical Outputs Analog Inputs Analog Outputs

Location Filled by OGIV-8035 according to the PLC configuration. Can't be modified.

Address Idem

Needn't be entered for spare I/O. Refer to appendix B for the syntax.Mnemonic

li_...

Don't use thesamemnemonics inIHR and MAIN(synchro top orpolarity for ex.)as IHR inputsare copied inMAIN

lo_... di_... for point andphysical values,

li_... for fault bit.

do_...

Var. ref. Automatically filled by OGIV-8035 if the variable is flagged To Ctrlog or to MMI.Not necessary otherwise. It may be modified by the user.

Label Use F1 to call the dictionary of abbreviations. Choose among the list the word toshorten (to reach the word quickly, type its 1st letters) then click on the HELP buttonto display its short name.

Acq. Rate (s) Not applicable Automatically filled by OGIV-8035according to unit . Can be modified.


37/151

_______________________________________________________________________________________AA M-SM01-A40028.37/A


State 1 It must not be typed by the user butselected in the popup list.

Type any letter to display the list ofthe valid state_1/state_0 couples andselect one of them. To reach quicklythe desired state_1 message, type its1st letter once the list is displayed.

Not applicable

Unit Not applicable Type any letter to display the list of thevalid units and select one of them.Validation bit= state_1

To Ctrlog * Only in MAIN PLCs

BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )Validation bits:BLANK

Inter-sub * Only in SUB PLCs

BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )

S ( =TS ) forvalidation bits

V mini / Vmaxi

Not applicable

6400 / 32000 bydefault for the valuesin points.Not for the fault bit.

PLC mini /PLC maxi Not applicable

Not for the validationbit

To F8000 * BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )

S ( =TS ) forvalidation bits

To S8000 * In MAIN PLCs only

BLANK ( = not sent )BS ( = broadcast TS )PS ( = TS sent to PLC 16** only )

BLANK ( = not sent )BM ( = broadcast TM )PM ( = TM sent to PLC 16** only )Validation bits : BS ,PS

To MMI * Means that the variable has to be sent to the MMI connected to the current PLC. Ifvariables of SUB or IHR PLCs have to be displayed on a MMI connected to MAINPLC, they have to be flagged To MMI in MAIN PLC.


38/151

_______________________________________________________________________________________AA M-SM01-A40028.38/A


BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )

S ( =TS ) for fault bits.

* Press the spacebar to scroll through the list then validate with Enter.** PLC 16 = regrouping PLC (Mimic for example)

3.2.4 Modifications

The following modifications may be performed:

3.2.4.1 Change the 1st reference address or the type of a module

A module may be replaced by another of the same kind (ex: MDL646 with MDL655or ALG223 with ALG222) or its 1st reference address may be changed withoutloosing the inputs/outputs already declared.

In "PLC config. " "Hardware ": click on the module to modify and click on its 1streference address (triple click to select the whole field) and enter the new address.The new address mustn't be already assigned to another module.

After validation with " Ok ", OGIV changes the address of all the I/O of the module.

3.2.4.2 Move an input or an output

- In "Variable " "Input " or "Output " "Analog ", place the cursor on the record of theI/O variable to move and press F10 key. OGIV-8035 then displays a small screenallowing to choose the new rack/slot/point of the I/O.

There must be a module located in the chosen slot and that module must be ofthe same type as the previous one. If the location (or address) is already assignedto an input or output, the 2 inputs or outputs are switched .

- For other types of variables, place the cursor on a field of the variable to move ,press ALT M . Then place the cursor on the new location of the variable and pressALT P : all the attributes of the variable are moved to the new location.


39/151

_______________________________________________________________________________________AA M-SM01-A40028.39/A

3.2.4.3 Move a whole module

In "PLC config." "Switching modules" , enterthe original rack and slot numbers, then the target

rack and slot numbers.

The rack and slot attributes of all the inputs oroutputs of the module are then updated.

3.2.5 Stage 4 : printing of the input/output list

For each report, OGIV-8035 generates a title sheet that is the standard title sheet forinternal documents. As the projects always need customised title sheet, the onegenerated by OGIV-8035 can't be used. Moreover, some information defined on the

title sheet also appears on each page of the document: internal number(MXXXXA4XXXX), revision and number of the 1st page generated by OGIV-8035.The user must therefore enter them.

OGIV-8035 generates 2 separate reports for an IHR PLC and its related MAIN PLC.To gather them into a single document:

- Give the same internal number and revision to the 2 reports

- Enter a first page number for the second report equal to the last sheet of the firstreport + 1.

To print the I/O list:

- Select " Printing " "Inputs/Outputs "

- To the question " Modification of the title sheet (Y/N) ?", answer " Y" to enter ormodify the internal number of the document, its revision or the number of its firstpage. The number of the 1st page should be "3" as sheet 1 is the title sheet andsheet 2 should be the "modifications table" .

- Click on " Ok " to validate. If those 3 parameters neednt be changed, answer " N".

- Then type " S" to visualise the report on the screen or " P" to print it.

- When "P"rinting is chosen, the standard Fox Pro print screen is displayed allowingto select the pages to print.

To print the whole document, select " All"

To print some particular pages only, be careful that for Fox Pro:

page 1 is the title sheet


40/151

_______________________________________________________________________________________AA M-SM01-A40028.40/A

page 2 is the 1st page of OGIV-8035 document (ie the PLCconfiguration)

Therefore if the number of the 1st page has been set to X:

to print page X, enter "2" !

to print page X + n, enter 2 + n !


41/151

_______________________________________________________________________________________AA M-SM01-A40028.41/A

4 MODBUS IMPLEMENTATION

4.1 INTRODUCTION

- To behave as MASTER Modbus subscriber , C80-35 PLC needs :

PCM301 : coprocessor module with 2 serial ports which can executeprograms written in BASIC or C language

MBPCM : C software to load into PCM module to implement master Modbusprotocol on the 2 ports of the module. The release must be 1.6

A PCM module loaded with MBPCM software therefore handles 2 Modbus

Exchange Units .

A PCM module must be installed in the CPU rack, therefore up to 9x2 ModbusExchange Units could theoretically be implemented in a C80-35 PLC. Ourstandards limit the number of Modbus EU to 4: 4 PCM with one channel each or 2PCM with 2 channels each.

- The front side connector on PCM module supports 2 serial ports :

An "Y cable" is supplied with the module to split the 2 ports on 2 separateconnectors.

Port 1 provides an RS-232 interface

Port 2 provides either RS-232 or RS-485.

To isolate the 2 ports and isolate PCM from the outside, an RS-232/RS-485converter is systematically used for multipoint links. The 2 serial ports are thenconfigured in RS-232. When only 1 Modbus Exchange Unit is needed, port 2should be chosen as port 1 is by default dedicated to PCM configuration from aPC.

A PCM module preloaded with MBM software is also available. Its reference isCF693MBM100. When only one modbus link is needed , MBM100 should be usedas it is more convenient than PCM301 (no need of execution procedure describedchapter 4.3.1 ).

When 2 modbus links are needed , MBM100 may also be used but 2 differentconverters must be used RS232/RS485 on port 1, RS485/RS485 on port 2.


42/151

_______________________________________________________________________________________AA M-SM01-A40028.42/A

- The communication parameters are as follows :

BAUD RATE : 300, 600, 1200, 2400, 4800, 9600 or 19200 PARITY : NONE, ODD or EVEN

DATA BITS : 7 or 8STOP BITS : 1 or 2PHYSICAL PROTOCOL : RS-232 (converted into RS-485 by an external

converter) or RS485LINE PROTOCOL : RTU

All the devices connected to the same network must have the same parameters.The parameters may be different on the 2 channels of a PCM module.

- DOMAIN standard programs have been written to handle the Modbusnetwork(s).

DMB_UE manages the communication between the CPU and the PCM modules.It handles up to 4 Modbus EU and must be called once in "_main" program.

"Slave" blocks, such as DMB_EVA, DMB_CHS..., handle the exchanges withspecific slave devices. They monitor their slave devices, trigger the questions sentto them and supply the application program with easily accessible interface tablescontaining the variables read or to write in the slave devices.

Refer to appendix E for the description of those DOMAIN blocks.

- In the same way as wired inputs/outputs, the Modbus inputs/outputs (ievariables exchanged with Modbus slave devices) must be declared in OGIV-8035 before being used in CADEPA application programs. The steps are :

Declaration of the Modbus EU

Declaration of the slave devices. OGIV-8035 then generates all the ModbusI/O references

Capture of the mnemonics, labels and other attributes

Printing of the standard Modbus I/O list: see extract appendix H-2.

OGIV-8035 also generates a program file for CADEPA ( og_mbus.gig ) with thecustomisation of the Modbus EUs and of the PECA/EVA, and CHESSELL slavedevices according to the parameters entered during the declaration of EU andslave devices.


43/151

_______________________________________________________________________________________AA M-SM01-A40028.43/A

4.2 DECLARATION OF THE MODBUS INPUTS/OUTPUTS

4.2.1 Needed tools

OGIV-8035 only.

4.2.2 Stage 1 : declaration of the Modbus exchange units

Select " Network " "Modbus " "Exchange units ".

Up to 4 Modbus EUs can be declared.

The following screen is displayed. Use TAB to move from one field to the next.

UE Nr : Number used for DOMAIN internal processing.There must be no hole in the numbering. If the user leaves one, OGIV-8035 automatically moves back the UEs toward the smaller numbers.

PCM Slot : 2 to 10 . Slot of CPU rack where the PCM301 module supporting theEU is located.

Channel : 1 or 2 . Channel of the EU on the PCM module.

Those information are used by OGIV-8035 to generate in og_mbus.gig theinstructions to update at 1st scan all the parameters of DMB_UE program block.

Those parameters may be modified at any time. The only consequence is thegeneration of a new og_mbus.gig , which must be imported in CADEPA.


44/151

_______________________________________________________________________________________AA M-SM01-A40028.44/A

4.2.3 Stage 2 : declaration of the Modbus slave devices

Select " Network " "Modbus " "Slave devices ". The following screen is displayed.

Up to 32 slave devices may be declared.

Use " Modbus devices " "Add " or ALT A to declare a new device. OGIV-8035automatically fills some its fields but all of them can be modified.

Use " Modbus devices " "Delete " or ALT D to delete a device.

Name : Up to 12 charactersName of the slave device. It appears in attribute location of theMODBUS inputs/outputs.

Designation : Comment on 32 characters.

Exch. Unit : 1 to 4Number of the related exchange unit. The EU must be alreadydeclared.

Subs. Nr : 1 to 255

Subscriber number on the Modbus network. Slave devices connectedto the same EU cannot have the same subscriber number.

Type : : PECA-EVA , CHESSELL or OTHER

Equipt. Nr : There are up to 32 MODBUS slave devices connected to the samePLC.


45/151

_______________________________________________________________________________________AA M-SM01-A40028.45/A

Each of them must have a different Equipt. Nr. OGIV automaticallyassigns a number to each slave: they may be modified except forCHESSELL (Nr 32). When a CHESSELL is declared, equipmentnumbers 28 to 32 are no more available. For OTHER devices refer tothe technical sheet of their DOMAIN block to check the rules for their

equipment number.

PECA or EVA electrical measurements acquisition units and CHESSELLtemperature acquisition units are the slave devices most commonly used in ourprojects. The parameters of the DOMAIN blocks managing the communication withthose devices are therefore known by OGIV-8035 which:

- Generates automatically the variables received from those devices,

- Writes in og_mbus.gig file, stored under the AP_FST application directory of theproject, the instructions to update the parameters of DMB_UE, DMB_PER,DMB_EVA and DMB_CHS DOMAIN blocks.

For the devices of the OTHER type, the user must:

- Consult the technical sheet of the DOMAIN block managing the communicationwith the device then enter in OGIV-8035 the references of the bits and words sent

to or received from the device. OGIV-8035 can then generate the related I/Ovariables.

- Write in AP_FST application (in CADEPA) the customisation of the DOMAIN blockusing the cnf_xxx files available on the domain floppy disk.

Somme attributes as the communication parameters are performed by cnf_mbu.gig (see appendix F).

This file is available on domain floppy disk (under A:\CADEPA) and should be storedin AP_FST CADEPA application.

For PECA-EVA devices which do not follow the default configuration described nextparagraph and for all the CHESSELL and OTHER devices, further parameters mustbe fixed.

The cursor being on the device to configure, use " Modbus devices ""Configuration " or ALT C to do so.


46/151

_______________________________________________________________________________________AA M-SM01-A40028.46/A

4.2.3.1 Configuration of a PECA or EVA device

The measurements from a PECA or EVA device are in the double-integer format (ie1 value = 2 words) and in the following order:

- 3 phase to neutral voltages, in volts- 3 phase to phase voltages, in volts

- 3 currents, in amps

- Total active power, in W

- Total reactive power, in VAR

- Total apparent power, in VA

- Power factor, divided by 10

- Frequency, in 0.1 Hz

- Furnished active energy, in kWh

- Received active energy, in kWh

- Furnished reactive energy, in kVARh

- Received reactive energy, in kVARh total = 36 words.

DMB_EVA converts them into integers and copies them into an interface table forthe application program except for:

- the apparent power which is not copied in the application table,

- the energies which remain in double-integers.

The maximum number of Modbus inputs from a PECA or EVA is therefore 3 V + 3 U+ 3 I + P + Q + cos + Hz + 4*2 energies (most + least significant words of eachenergy) = 21 analog inputs .


47/151

_______________________________________________________________________________________AA M-SM01-A40028.47/A

The cursor being on the PECA-EVA device to configure, select " Modbus Devices ""Configuration " or use ALT C . The following screen is displayed:

DEVICE : Name of the current device.

3V,3U,3I,P,Q,Cos,Hz,4E : Standardconfiguration described above. Itgenerates 21 analog inputs. If thewhole 21 inputs are not needed, clickon the related buttons to select orremove the 1 st or the lastmeasurement.

Units : Weight of the integer providedby DMB_EVA. Click on the chosenunit.Be sure that the maximum value ofthe measurement expressed in thechosen unit does not exceed 32767.

Period : The measurements are read in the slave device every x * 500 ms ( x =value entered by the user).

Fault Byte : To read the fault byte in a PECA device.Flag it only if needed as it generates an additional message onMODBUS network.

All those parameters allow OGIV-8035 to write in og_mbus.gig file the instructionsto customise DMB_EVA DOMAIN block. When the standard parameters are kept,this configuration does not have to be performed. Once the proper parameters areentered, click on " Ok " to validate. The inputs from the Modbus device will becreated and og_mbus.gig generated after validation of the slave device declarationscreen only.


48/151

_______________________________________________________________________________________AA M-SM01-A40028.48/A

4.2.3.2 Configuration of a CHESSELL device

The cursor being on CHESSELL device, select " Modbus Devices " "Configuration "or use ALT C . The following screen is displayed:

DEVICE : Name of the currentslave device.

Number of measurements :

1 to 96 .Number of measurementsfrom CHESSELL.

Nbr of alarms/measurements Number of thresholds for eachmeasurement (Max. 3)

Reading Period : The measurements are read in the CHESSEL device every x *500 ms ( x = value entered by the user).

Those parameters allow OGIV-8035 to write in og_mbus.gig the instructions tocustomise DMB_CHS block. The numbers of words and 16-bit words also allowOGIV-8035 to generate the proper number of analog and logical inputs fromCHESSELL.

Once the proper parameters are entered, click on " Ok " to validate. The inputs fromthe Modbus device will be created and og_mbus.gig generated after validation ofthe slave device declaration screen only.


49/151

_______________________________________________________________________________________AA M-SM01-A40028.49/A

4.2.3.3 Configuration of an OTHER device

The cursor being on the OTHER device to configure, select " Modbus Devices ""Configuration " or use ALT C . The following screen is displayed.

Use " TAB " to move from a field to the next.

DEVICE : Name of the current slave device.For each type of variables, received or sent,analog or discrete, the following parametershave to be filled according to the technical sheetof the DOMAIN block managing thecommunication with the slave device.

Number of words/bits : Number of consecutiveanalog or discrete variables received from orsent to the slave device.

First address : Address in the PLC of the firstword or bit received from or sent to the device.

Those parameters allow OGIV-8035 to generate the proper number of analog andlogical inputs and outputs from or to the slave device.

Once the proper parameters are entered, click on " Ok " to validate. The analog andlogical inputs and outputs related to the device will be created after validation of theslave device declaration screen only.

Documents

3. C80-35 Engineer Doc.pdf