Vous êtes sur la page 1sur 151

P320 SERIES 4 EL-C

ENGINEERING OF A C8035 AUTOMATION CELL


USING OGIV-8035 / CADEPA / P8
This document is the exclusive property of ALSTOM and shall not be used, copied or communicated to third parties without their prior
Ce document propriété d’ ALSTOM ne doit pas être utilisé, copié ou communiqué à des tiers sans son autorisation

DIFFUSION : CONFIDENTIELLE  RESTREINTE  CONTROLEE  LIBRE 


ACCESSIBILITY CONFIDENTIAL RESTRICTED CONTROLLED FREE
authorization

DATE NOM SIGNATURE


NAME
12/12/00

ETABLI
AUBARBIER
ESTABLISHED

VERIFIE TOTH
CHECKED

APPROUVE
GRISIER
APPROVED

REV STAT. F°/F° FIN Nb F°


SH/SH END N of SH
H T G - E N - 2 0 - W I G - PG 0 0 2 M S M 0 1 A 4 0 0 2 8
A PROVISO 1/146 146
MA 400/1 A

IRE
TABLE DES MODIFICATIONS / MODIFICATIONS TABLE

REV ETABLI VERIFIE APPROUVE DATE MODIFICATIONS STAT.


ESTABLISHED CHECKED APPROVED

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

_______________________________________________________________________________________
AA M-SM01-A40028.2/A
PA 401 A
CONTENTS

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


1.1 ARCHITECTURE................................................................................................................................................. 7
Global architecture .................................................................................................................................................... 7
Detail of an automation cell....................................................................................................................................... 9
1.1.2.1 Simple automation cell ...................................................................................................................................... 9
Redundant automation cell .................................................................................................................................................. 9
1.1.3 Limitations .................................................................................................................................................... 9
1.1.3.1 S8000................................................................................................................................................................... 9
1.1.3.2 Automation cell ................................................................................................................................................. 10
1.1.4 Selected modules ......................................................................................................................................... 11
1.1.4.1 Baseplates......................................................................................................................................................... 11
1.1.4.2 Power supplies ................................................................................................................................................. 11
1.1.4.3 Processing unit ................................................................................................................................................. 12
1.1.4.4 S8000 Communication module ...................................................................................................................... 12
1.1.4.5 F8000 Communication module ...................................................................................................................... 12
1.1.4.6 SNP Communication modules ....................................................................................................................... 12
1.1.4.7 MODBUS communication module ................................................................................................................. 13
1.1.4.8 Discrete input modules .................................................................................................................................... 14
1.1.4.9 Discrete output modules.................................................................................................................................. 14
1.1.4.10 Analog input modules ...................................................................................................................................... 14
1.1.4.11 Analog output modules.................................................................................................................................... 15
1.1.4.12 Tools to implement the automation cells....................................................................................................... 15
1.2 ENGINEERING TOOLS..................................................................................................................................... 16
1.2.1 ALSPA P8 software..................................................................................................................................... 17
1.2.2 CADEPA engineering tool .......................................................................................................................... 17
1.2.3 OGIV-8035 database manager ................................................................................................................... 18
1.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................................................................................................................................................ 23
2.2.2 Stage 1 : declaration of the PLC(s)............................................................................................................. 23
2.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 .......................................................................................................... 28
3.1.2 Discrete inputs ............................................................................................................................................ 29
3.1.3 Analog inputs .............................................................................................................................................. 30
3.1.4 Discrete outputs .......................................................................................................................................... 33
3.1.5 Analog outputs ............................................................................................................................................ 33
3.2 PROCEDURE ..................................................................................................................................................... 34
3.2.1 Needed tools................................................................................................................................................ 34
3.2.2 Stage 2 : declaration of the PLC configuration .......................................................................................... 34
3.2.3 Stage 3 : declaration of the inputs/outputs.................................................................................................. 36
3.2.4 Modifications .............................................................................................................................................. 38
3.2.4.1 Change the 1st reference address or the type of a module ....................................................................... 38
3.2.4.2 Move an input or an output ............................................................................................................................. 38
Move a whole module ......................................................................................................................................................... 39
3.2.5 Stage 4 : printing of the input/output list .................................................................................................... 39
4 MODBUS IMPLEMENTATION ......................................................................................................................... 41
_______________________________________________________________________________________
AA M-SM01-A40028.3/A
4.1 INTRODUCTION ............................................................................................................................................... 41
4.2 DECLARATION OF THE MODBUS INPUTS/OUTPUTS ............................................................................... 43
4.2.1 Needed tools................................................................................................................................................ 43
4.2.2 Stage 1 : declaration of the Modbus exchange units................................................................................... 43
4.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........................................................................................................... 48
4.2.3.3 Configuration of an OTHER device ............................................................................................................... 49
4.2.4 Stage 3 : declaration of the Modbus inputs/outputs.................................................................................... 50
4.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 ...................................................................................................................... 51
4.3.2 pcmexec.bat (for PCM301 only) ................................................................................................................. 51
4.3.3 hardexec.bat (for PCM301 only) ................................................................................................................ 52
4.3.4 Procedure to load MBPCMV13, PCMEXEC and HARDEXEC into PCM301........................................... 53
4.3.4.1 Needed tools..................................................................................................................................................... 53
4.3.4.2 Procedure.......................................................................................................................................................... 53
5 F8000 IMPLEMENTATION ................................................................................................................................ 54
5.1 DECLARATION OF F8000 EXCHANGE AREAS .......................................................................................................... 55
5.2 UPDATING OF F8000 VARIABLES ........................................................................................................................... 59
5.2.1 Extraction of the variables to send on F8000 ............................................................................................. 59
5.2.2 Import F8000 variables .............................................................................................................................. 61
5.3 CONSULTATION AND CUSTOMISATION OF F8000 VARIABLES ................................................................................ 63
5.4 PRINTING OF THE F8000 INPUT 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.............................................................................................. 68
6.2.2 Import of S8000 variables........................................................................................................................... 68
6.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 .................................................................................................................................................... 71
7.1.2 Hardware architecture................................................................................................................................ 71
7.1.3 Principles .................................................................................................................................................... 72
7.1.3.1 Telecommands and Televalues Centralog updating................................................................................... 72
7.1.3.2 Telecommands and Televalues local HMI updating. .................................................................................. 73
7.1.3.3 Logical and numerical memories updating. .................................................................................................. 73
7.1.3.4 Insertion mode control. .................................................................................................................................... 75
7.1.4 Duality safety mode..................................................................................................................................... 75
7.1.4.1 Taking over inhibition....................................................................................................................................... 76
7.1.4.2 Stopping request ( controller in insertion) ..................................................................................................... 76
7.1.4.3 Application stopping request (loss of messages) ........................................................................................ 76
7.1.4.4 Application insertion mode request (loss of messages) ............................................................................. 76
8 EXPORT TO CENTRALOG................................................................................................................................ 77
8.1 EXPORT TO MICROETE ........................................................................................................................................ 77
8.2 EXPORT TO CONTROCAD .............................................................................................................................. 78
9 EXPORT TO MAN MACHINE INTERFACE................................................................................................... 79
9.1 GENERATION OF MMI EXPORT FILES ................................................................................................................... 80
10 DUPLICATION OF EXPORTED PROJECT DATA ........................................................................................ 81
10.1 DUPLICATION OF S8000 DATAS....................................................................................................................... 81
10.2 DUPLICATION OF F8000 DATAS ...................................................................................................................... 82
_______________________________________________________________________________________
AA M-SM01-A40028.4/A
10.3 DUPLICATION OF CENTRALOG FILE .................................................................................................................. 82
10.3.1 Case of using Controcad ........................................................................................................................ 82
10.3.2 Case of using Microete ........................................................................................................................... 83
IMPORT / EXPORT TO CADEPA .............................................................................................................................. 83
11.1 PRINCIPLES ...................................................................................................................................................... 83
11.1.1 Generation of OGIV_PJ.mne file............................................................................................................ 83
11.1.2 Import from CADEPA ............................................................................................................................ 85
11.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............................................................................................................ 86
12.1.2 Interface between CADEPA and OGIV-8035......................................................................................... 87
12.1.2.1 Variables............................................................................................................................................................ 87
12.1.2.2 Programs generated by OGIV-8035.............................................................................................................. 87
12.2 PROCEDURE ................................................................................................................................................. 88
12.2.1 Configuring CADEPA ............................................................................................................................ 88
12.2.1.1 Declaration of default attributes for the projects .......................................................................................... 88
12.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 ................................................................ 92
12.2.2 Creation of a project............................................................................................................................... 93
12.2.3 Creation and configuration of applications............................................................................................ 93
12.2.3.1 Attributes of the applications........................................................................................................................... 94
12.2.3.2 Page setup of the application in Graphite..................................................................................................... 95
12.2.3.3 Preferences to display variables in Graphite................................................................................................ 95
12.2.4 Import of all the project variables already declared in OGIV-8035 ...................................................... 96
12.2.5 Edition of programs................................................................................................................................ 96
12.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 COHERENCE OF ADDRESSES ............................................................................................................................. 99
13.2 PROCESS BITS OR WORDS FREES ....................................................................................................................... 99
13.3 UPDATING OF WORDINGS FROM OTHER PROJECT .............................................................................................. 99
13.4 DATABASE OPTIMIZATION .............................................................................................................................. 100
13.5 FONT .............................................................................................................................................................. 100
13.6 TRANSLATE .................................................................................................................................................... 100
13.7 ADDRESSING UTILITIES .................................................................................................................................. 101
13.7.1 Partial addressing ................................................................................................................................ 101
13.7.2 Reset Ranks........................................................................................................................................... 101
13.7.3 Display file............................................................................................................................................ 102
13.7.4 Browser database ................................................................................................................................. 102
13.7.5 Loading CADEPA................................................................................................................................. 102
13.7.6 Saving ................................................................................................................................................... 103
13.7.6.1 OGIV-8035 ...................................................................................................................................................... 103
13.7.6.2 CADEPA .......................................................................................................................................................... 103
13.7.7 Restoring............................................................................................................................................... 103
13.7.7.1 OGIV-8035 ...................................................................................................................................................... 104
13.7.7.2 CADEPA .......................................................................................................................................................... 104
14 TEST ..................................................................................................................................................................... 105
14.1 INTRODUCTION .............................................................................................................................................. 105
14.2 PROCEDURE ................................................................................................................................................... 106

_______________________________________________________________________________________
AA M-SM01-A40028.5/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-25
PLC User Manual

[5] ALS 52202 a Hand-Held Programmer for Alspa C80-35, C80-25 and C80-05
PLCs 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 User’s 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 serie
PLCs

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

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

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

_______________________________________________________________________________________
AA M-SM01-A40028.6/A
1 PRESENTATION OF ALSPA P320 SERIES EL 4-C USED IN HYDRO SYSTEMS

1.1 ARCHITECTURE

1.1.1 Global architecture

CENTRALOG

S8000
SITE N ETW OR K

SNP
MMI NETWORK M AIN M AIN M AIN
M AIN

F8000
FIELD
NETWORK

IHRi SUBi

IHRi

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 CADEPA


engineering tool). It receives orders (TC) and set points (TVC) from CENTRALOG
and sends discrete (TS) and analog (TM) variables to CENTRALOG. Those TS
are 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 have
any application program but house a software which performs :

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

_______________________________________________________________________________________
AA M-SM01-A40028.7/A
. the updating of the messages of 1 ms time-tagged events sent to
CENTRALOG 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-tagged
inputs). The “SUB” PLCs may also perform delocalized subfunctions of MAIN
PLC. They house application programs (generated by CADEPA). They
communicate with MAIN PLC through F8000 network and are not linked to S8000
network. TS and TM from those PLCs are therefore sent to CENTRALOG through
MAIN 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 a
C80-35 automation cell (MAIN, IHR, SUB).

- SNP network

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

_______________________________________________________________________________________
AA M-SM01-A40028.8/A
1.1.2 Detail of an automation cell

1.1.2.1 Simple automation cell

S8000-E or F

MMI
SNP
M AIN
P8 or S8000-E or F
SNP rack 0
HHP
F8000 MMI MBUS

P8 or SNP SNP
M AIN STANDBY
HHP M AIN
SUB-1 MBUS rack 1
F8000

M AIN
SUB-2
SUB-1 rack 2
MBUS

M AIN
SUB-3
SUB-2 rack 3

IHR-1
SUB-3

IHR-2IHR-1

Simple automation cell with


high resolution inputs and sub-controllers
IHR-2

Redundant automation cell with


high resolution inputs and sub-controllers

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 an


automation cell:
- 1024 for a S8000-F network

- 1024 for a S8000-E network


_______________________________________________________________________________________
AA M-SM01-A40028.9/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 the


other MAIN PLCs: 20 words (the 1st one is an utility word processed by the
DOMAIN standard blocks)

• Maximum size of an inter-controller message sent by a MAIN PLC to the


regrouping MAIN PLC: 64 words (the 1st word is an utility word processed by the
DOMAIN standard blocks).

1.1.3.2 Automation cell

The standard F8000 configuration available for hydro applications allows up to 2


IHRs and up to 3 SUBs in an automation cell.

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


developed.

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 are
used and 1 input out of 16 is dedicated to polarity control.

- 8x32 - 1 (SYNCHRO) - 8 (polarity control) = 247 when 32-input modules are


used and 1 input out of 32 is dedicated to polarity control.

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

_______________________________________________________________________________________
AA M-SM01-A40028.10/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 between


the 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 to


240 Vac or 125 Vdc.

- IC693PWR330 : also supplies 30W (15W in 5 Vdc and 15 W in 24 Vdc) from 120
to 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 supply
does not fit. Therefore the load consumption must be estimated before choosing
this power supply card.

_______________________________________________________________________________________
AA M-SM01-A40028.11/A
1.1.4.3 Processing unit

Communication Program
Reference Use
ports space

IC693CPU363 SNP serial ports • S8000-F MAIN PLC with MMI 240 K

• SUB PLC with MMI

IC693CPU364 Ethernet • S8000-E MAIN PLC 240 K

IC693CPU350 None • IHR 32 K


• SUB PLC without MMI and with
small application program*
IC693CPU360 None • S8000-F MAIN PLC without MMI 240 K
• SUB PLC without MMI and with
big application program

* A CPU350 for a SUB PLC with MODBUS communication and analog conversion
and 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 to


S8000-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 of


software (INTERACT, CITECT) use SNP protocol to communicate with C80-35
controllers.

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

_______________________________________________________________________________________
AA M-SM01-A40028.12/A
On CPU363 card, 2 serial ports are available, allowing SNP protocol. They can be
used 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.This


module provides 1 RS232 and 1 RS232/485 serial ports on witch SNP protocol is
available.

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

AC C 901 PWR330

RS232, 2m

- IC690ACC901 converter + cable may be used.

1.1.4.7 MODBUS communication module

The Programmable Coprocessor Module (PCM) IC693PCM301, loaded with


MBPCMV16 software allows the C80-35 PLC to be the master subscriber on 1 or 2
MODBUS networks. It has 2 serial ports; one supporting RS232 only, the other one
RS232 or RS485.

The software IC641SWP023 (TERM F) is needed to load MBPCMV14 and other


files in PCM. TERM F has to be loaded in a PC that may be connected to PCM
module 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 first
serial port supports RS232 only, its second serial port supports RS485 only. No
file have to be loaded in MBM100 card. Therefore, SWP023 and CBL702 are not
needed.

_______________________________________________________________________________________
AA M-SM01-A40028.13/A
1.1.4.8 Discrete input modules

The numerous discrete input modules available for a C80-35 PLC are described in
document [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 inputs
but 2 24-point male connectors. Therefore interface modules must be used for
input 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 of
a mimic board).

1.1.4.9 Discrete output modules

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

The discrete output module chosen for standard is:

- IC693MDL753 : 32 static outputs, 12/24 Vdc positive logic, 0,5A max. Same
comment 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 tests
as 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 IC693XXX
analog input modules

- HFK-90XXX technical sheets for HE693XXX modules.

The analog input module chosen for standards is:


_______________________________________________________________________________________
AA M-SM01-A40028.14/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 inputs
are 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 50


Hz 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) (see
chapter 1.2)

- The Hand Held Programmer (HHP) IC693PRG301 is absolutely needed to


configure F8000 or S8000-F communication module.

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

_______________________________________________________________________________________
AA M-SM01-A40028.15/A
1.2 ENGINEERING TOOLS

CENTRALOG
customisation tool

MMI

DATABASE

DATABASE

OGIV8035

DATABASE
AND DATABASE
PROGRAM

CADEPA

LADDER CODE

P8

_______________________________________________________________________________________
AA M-SM01-A40028.16/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 the
application program : DOMAIN blocks and application blocks (the DOMAIN blocks
are available on a floppy disk ; the content of application blocks is generated by
CADEPA 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 8000


translator.

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

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


English.

The reasons for using CADEPA are:

1. The programming document, written with SFC standardised language, textual


language, 27 characters mnemonics for the variables and as many comments
as needed, is clear enough to serve as a detailed specification document.
That allows to ensure the coherence between the detailed specification and
the program running in the PLC and avoids the manual translation of the
detailed 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 and
associated with OGIV-8035 allows to address variables more efficiently than P8.

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

_______________________________________________________________________________________
AA M-SM01-A40028.17/A
1.2.3 OGIV-8035 database manager

OGIV-8035 is a database tool running on Microsoft FOXPRO database


management system. It manages the variables of each controller.

The databases of CENTRALOG customisation tool, CITECT or INTERACT Man


Machine Interface and CADEPA are updated from OGIV-8035 databases. That
ensures 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 exchanged
on the various networks ...
This function may be used even when the controller is not programmed with
CADEPA.
- Assigns addresses to all the variables of a controller. This function is
absolutely needed when the process of a controller is split into several
applications in CADEPA.

- Ensures the consistency of the variables between the PLCs and


CENTRALOG. For that, OGIV-8035 updates CENTRALOG with all the variables
flagged to be TS, TC, TM or TVC. The attributes loaded into CENTRALOG by
OGIV-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 the
comprehensive list of those attributes. OGIV-8035 automatically assigns
addresses to TC and TVC according to their row. OGIV-8035 affects rows to TS
and TM then generates CADEPA program files to arrange them accordingly in the
TS 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 S8000


networks. The variables sent by a PLC on F8000 or S8000 networks are
declared in OGIV-8035. OGIV-8035 then generates CADEPA program files to
arrange those variables in the F8000 or S8000 messages. It updates accordingly
the 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).They


allow declaring all the variables processed by CENTRALOG with all their attributes.

_______________________________________________________________________________________
AA M-SM01-A40028.18/A
Some of those attributes may be updated by OGIV-8035 (Refer to 2.1.3). The other
ones (such as threshold values, appearance in a log ...) have to be declared using
CENTRALOG customisation tool.

CENTRALOG customisation tool is not described in this document as it is not a


engineering tool for the PLC but for CENTRALOG.

1.3 DOMAIN STANDARD PROGRAMS

The DOMAIN is a set of programs, written with P8 programming software, which


carry out system functions often implemented in our PLCs. Their aim is to :
- reduce the application studies by sparing the user the programming of system
functions,

- provide well-optimised and well-tested functions,

The DOMAIN consists of a P8 folders called STD_S8E (MAIN controllers with


ETHERNET 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, other
processings can be added:
- PLC management : reset of the PLC data memory (at 1st scan), monitoring of
PLC 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 the


analog 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 in
word messages, into discrete references easily accessible for the application
program.

- MODBUS: Communication with PECA or EVA electric measurement acquisition


unit, with CHESSELL temperature acquisition unit and many other devices.

_______________________________________________________________________________________
AA M-SM01-A40028.19/A
1.4 ENGINEERING STAGES

(M = Manual operation ; A = Automatic operation)

CADEPA
OGIV

P8
Stage Comment Related document

1. Definition of PLC Composition of each rack and Included in the PLC


configuration M I/O address of the modules I/O list

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

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


Functional
4. Functional specification M specification
document.
5. Detailed specification
= programing
• Operations (SFC + textual M Programming
language) document (CADEPA)

• Creation of variables (except A Variables used in operations Cross references


I/O variables) are automatically created (OGIV-8035)
• Comments M

• Exchange programming M The variables to send are Exchange lists


(F8000, S8000, MMI) flagged in OGIV which (OGIV-8035)
generates programs for
CADEPA accordingly
• Variable addressing A

6. MMI programmation

• Mimic views Tool = INTERACT or CITECT

• Database A Imported in INTERACT or


CITECT from OGIV

• Alarms A OGIV generates the alarm files


for those 2 MMI.

_______________________________________________________________________________________
AA M-SM01-A40028.20/A
CADEPA
OGIV

P8
Stage Comment Related document

7. Update of CENTRALOG A Loaded by OGIV-8035


database Refer to appendix C for the list
of attributes updated by OGIV.

8. Building-up of the folder


(program + configuration) to
load into the PLC
• Configuration M

• “_main” program M Call of DOMAIN and CADEPA Listing of “_main”


program blocks program
• contents of the program
blocks :
• DOMAIN M From DOMAIN floppy disk The listing of the
blocks is not useful, as
• CADEPA A it’s the translation of
• Others M Operations not available in CADEPA program.
CADEPA (double-integers for
ex.) must be written with P8.

9. Tests

• Load program and M


configuration into the PLC
• Write a simulation program M A
• On-line visualisation of the M M
program, reading and writing
of variables.
• Modifications M M OGIV-8035 is needed only if
new variables are created or if
flags are modified (TS, TC, …)

10. Duplication of UNIT PLC The use of discrete inputs to


encode the PLC number avoids
duplication of CADEPA
program P8 folders, and OGIV
database: they are valid for all
the units.

• CENTRALOG database A Duplicated by OGIV-8035

11. Storage M M Variables databases, programs,


P8 folders

_______________________________________________________________________________________
AA M-SM01-A40028.21/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 the
IHR PLC as they do not house any application program.
The MAIN and SUB projects declared in OGIV-8035, are automatically created
by OGIV-8035 in CADEPA.
- For the 2 MAIN PLC of a redundant cell, 1 project only is created in
OGIV/CADEPA/P8.

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

- The user must then configure the F8000 exchange areas in the MAIN and SUB
PLCs of the automation cell
This operation should be performed prior to the I/O declaration as it allows OGIV
to know which areas are available for inputs and outputs

_______________________________________________________________________________________
AA M-SM01-A40028.22/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 PLCs
16 = regrouping PLC (MIMIC)

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

_______________________________________________________________________________________
AA M-SM01-A40028.23/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 be
declared if they send variables to local project through
F8000 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 modify
Designation, 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:

_______________________________________________________________________________________
AA M-SM01-A40028.24/A
- Declare the cell architecture by a click on the “white square” of the desired
controllers ( 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

_______________________________________________________________________________________
AA M-SM01-A40028.25/A
- Declare a SUB1 PLS as follow:

SUB1 PLC DATA TO DECLARE

- Name of the SUB1 PLC, 7 characters max.


- Designation of the SUB1 PLC, 40 characters
- Operating unit reference

- 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 do
this, select “Project”, “Select”:

GTA01_I, GTA01_S and


GTA01 controllers are
created

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

_______________________________________________________________________________________
AA M-SM01-A40028.26/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).

_______________________________________________________________________________________
AA M-SM01-A40028.27/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 in
the PLC data memory (I/O variables for I/O modules, state bits for communication
modules).

When entering the PLC configuration in P8 configuration software, the user


declares 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 all


the I/O references,

• capture of the mnemonic, label and possibly other attributes (refer to appendix
C 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 individual
I/O list is issued for each of them (but they may be gathered in a single
document).

_______________________________________________________________________________________
AA M-SM01-A40028.28/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 must P8 C


be %I(8n+1) with n = integer from 0 to 255.

2 The PLC %I data memory assigned to discrete OGIV-8035 won't accept inputs C
inputs is configured in OGIV when declaring the out of this area.
F8000 and the S8000 exchanges.

3 The 1ms time-tagged inputs of an IHR PLC must IHR software C


have references from %I0001 to %I0256.

4 %I0002 is the synchronisation signal. S8000 communication C


software
5 The mnemonics of the inputs (name in CADEPA OGIV-8035 C
and OGIV) must begin with "li_".
Ex: li_91lrl001jd_o
6 Some inputs should be dedicated to polarity To be used as validation bits C
acquisition. There are 2 options: for CENTRALOG

1. One input out of 16 is dedicated to polarity IHR software needs those


acquisition: %I0001 is the validation bit for inputs to process the validation
%I0002-16; %I0017 for %I0018-32 … bits of the 1ms-timetagged
inputs.
It allows to detect the loss of the input module,
of the acquisition polarity or of the interface
module
OGIV-8035 needs them to
2. The 1st input of each module acquires the process the validation bits of
acquisition polarity and validates the other the inputs acquired by the
inputs. For 32-input modules, the loss of the MAIN or SUB PLCs.
module or of the acquisition polarity is
detected, not the loss of the 2nd interface
module or of its flat cable.

7 For MAIN or SUB PLCs to duplicate (ex : units), Trick to avoid duplication. A
inputs should be used to encode PLC number.
(%I0001 to 16 are not reset by
It allows writing instructions dependent on the PLC DOMAIN at 1st scan)
number for processing specific to a particular unit.

Those inputs must be chosen from %I0003 to 16.

_______________________________________________________________________________________
AA M-SM01-A40028.29/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 used
and 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 32000
points.

The 3 least significant bits are not used. Therefore the resolution is 8 points which
for 0-20mA channels gives 20mA / (32000/8) = 5µA 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 threshold
detection is not performed by DOMAIN). Refer to its technical sheet in appendix
E.

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

. 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 the
customisation of analog inputs at first scan: rack, slot and last channel number of
each analog input module, min/max values of the analog inputs to convert into
physical units...

_______________________________________________________________________________________
AA M-SM01-A40028.30/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 signal DAI_ALG: detection of the loss A
should be 4-20mA whereas the channels of the of the signal.
input modules are configured to 0-20 mA. The
normal range of an input in then 6400-32000
points.

2 The 1st register reference assigned to an analog DAI_ALG C


input module in the PLC configuration must be
%AI0001 / 17 / 33 / 49 / 65 / 81 / 97 / 113.
Only 8 analog input modules can be handled.

3 When configuring the PLC in P8, the %I address DAI_ALG C


of %AI(16(n-1)+1) module, 1 ≤ n ≤ 8, must be :
%I(8(n-1)+1777) and the %I size = 8

4 The mnemonics of the raw and physical values OGIV-8035 C


must begin with "di_", of the fault bit with "li_"

5 The raw value must have a mnemonic, label and OGIV-8035: the raw value is C
unit in OGIV-8035 (except spare inputs). printed in the I/O list not the
physical value.

6 To differentiate raw values from physical values: The maximum number of A


add "_pts" at the end of raw value mnemonics or characters for a data mnemonic
in the CENTRALOG is 20.
"_phy" at the end of physical value mnemonics.
Avoid different conversion in
Both solutions are possible. But, for inputs both
CENTRALOG and MMI.
sent to CENTRALOG and MMI, the best one is
“_pts” at the end of raw values. Because, the TM
for CENTRALOG and the TM for MMI have
better be the physical values.

7 V mini and V maxi attributes must be filled for Given by OGIV-8035 to C


variables sent to CENTRALOG or MMI. CENTRALOG and MMI

_______________________________________________________________________________________
AA M-SM01-A40028.31/A
RULES FOR ANALOG INPUTS Due to C/A

9 The validation bit must have a mnemonic if the OGIV-8035 uses it to process C
analog input is sent to CENTRALOG. It can not be the invalidating bit of the TM.
flagged as TS for CENTRALOG.

10 The PLC mini and PLC maxi attributes of the OGIV-8035 generates a
RAW VALUES is 6400 (possibly 0 or –32000) and program file for CADEPA with
32000. They are automatically written by OGIV- the customisation of the analog
8035), but may be modified. input modules.

The PLC mini and PLC maxi attributes of the


PHYSICAL VALUES are the min. and max.
physical values used by DAI_ALG to convert the
input:
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 = 0


V maxi = 13,80 PLC maxi = 1380

- RTD modules may occasionally be used. The raw values of the RTD inputs are
not 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 updates
the raw value and validation bit of each input. DAI_RTD does not convert the raw
values into physical values.

If the physical value is needed in the application program, the user must write in a
CADEPA graph the instructions to update at each scan the physical value
(generated by OGIV-8035) with the raw value divided by the proper coefficient. If
it is not needed in the application program but has to be sent to INTERACT, the
better 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 1st
%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).

_______________________________________________________________________________________
AA M-SM01-A40028.32/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 module P8 C


must be %Q (8n+1) with n = integer from 0 to
255.

2 The PLC data memory assigned to discrete OGIV-8035 won't accept C


outputs is %Q0001 to %Qxxx with xxx = 384 by outputs out of this area.
default.

3 The mnemonics of the outputs (names in OGIV-8035 C


CADEPA and OGIV) begin with "lo_". Ex:
lo_91lrl001jd_o

4 An output of the MAIN PLC may be used as A


watchdog. To do so, the application program has
to copy the bit “ld_plc_run” in this output.

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: To avoid conversion of analog A


6400-32000 points for 4-20mA signal or 0-32000 inputs due to be also outputed.
for 0-10V signals.

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

_______________________________________________________________________________________
AA M-SM01-A40028.33/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 to


polarity acquisition in order to validate the 15 following inputs.
32: 1 discrete input out of 32 is dedicated to polarity acquisition.

_______________________________________________________________________________________
AA M-SM01-A40028.34/A
A new project is created with a default configuration including CPU363, S8000-F
and 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 other
configuration (S8000-E). In this case, It has to be changed with the correct CPU and
communication modules. In all case, it has to be complemented with discrete input
modules 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) and
enter the desired address. OGIV-8035 automatically calculates the last
reference 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 were


already declared they are then deleted!

- To move a module, if its I/O have not yet been generated, just replace it by
SPARE 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 all
the I/O references.

_______________________________________________________________________________________
AA M-SM01-A40028.35/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 appendix
C 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 a
record in another record: use ALT C / ALT V (ALT V only updates the empty
fields)

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

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

Mnemonic Needn't be entered for spare I/O. Refer to appendix B for the syntax.
li_... lo_... di_... for point and do_...
physical values,
Don't use the
same li_... for fault bit.
mnemonics in
IHR and MAIN
(synchro top or
polarity for ex.)
as IHR inputs
are copied in
MAIN

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 to
shorten (to reach the word quickly, type its 1st letters) then click on the HELP button
to display its short name.

Acq. Rate (s) Not applicable Automatically filled by OGIV-8035


according to unit. Can be modified.

_______________________________________________________________________________________
AA M-SM01-A40028.36/A
FIELD Logical Inputs Logical Outputs Analog Inputs Analog Outputs

State 1 It must not be typed by the user but


selected in the popup list.
Type any letter to display the list of
the valid state_1/state_0 couples and Not applicable
select one of them. To reach quickly
the desired state_1 message, type its
1st letter once the list is displayed.

Unit Not applicable Type any letter to display the list of the
valid 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 ) for
validation bits

V mini /Vmaxi 6400 / 32000 by


default for the values
Not applicable in points.
Not for the fault bit.

PLC mini / Not for the validation


PLC maxi Not applicable bit

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

S ( =TS ) for
validation bits

To S8000 * In MAIN PLCs only


BLANK ( = not sent ) BLANK ( = not sent )
BS ( = broadcast TS ) BM ( = broadcast TM )
PS ( = TS sent to PLC 16** only ) 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. If
variables of SUB or IHR PLCs have to be displayed on a MMI connected to MAIN
PLC, they have to be flagged To MMI in MAIN PLC.

_______________________________________________________________________________________
AA M-SM01-A40028.37/A
FIELD Logical Inputs Logical Outputs Analog Inputs Analog Outputs
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 MDL655
or ALG223 with ALG222) or its 1st reference address may be changed without
loosing the inputs/outputs already declared.

In "PLC config." "Hardware": click on the module to modify and click on its 1st
reference 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 the
I/O variable to move and press F10 key. OGIV-8035 then displays a small screen
allowing 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 of
the same type as the previous one. If the location (or address) is already assigned
to 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 press
ALT P: all the attributes of the variable are moved to the new location.

_______________________________________________________________________________________
AA M-SM01-A40028.38/A
3.2.4.3 Move a whole module

In "PLC config." "Switching modules", enter


the original rack and slot numbers, then the target
rack and slot numbers.

The rack and slot attributes of all the inputs or


outputs 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 for
internal documents. As the projects always need customised title sheet, the one
generated 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 first
report + 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 or
modify the internal number of the document, its revision or the number of its first
page. The number of the 1st page should be "3" as sheet 1 is the title sheet and
sheet 2 should be the "modifications table".

- Click on "Ok" to validate. If those 3 parameters needn’t 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 allowing
to 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

_______________________________________________________________________________________
AA M-SM01-A40028.39/A
• page 2 is the 1st page of OGIV-8035 document (ie the PLC
configuration)

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 !

_______________________________________________________________________________________
AA M-SM01-A40028.40/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 execute


programs written in BASIC or C language

• MBPCM : C software to load into PCM module to implement master Modbus


protocol 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 Modbus
Exchange Units could theoretically be implemented in a C80-35 PLC. Our
standards limit the number of Modbus EU to 4: 4 PCM with one channel each or 2
PCM 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 separate
connectors.
• 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-485
converter is systematically used for multipoint links. The 2 serial ports are then
configured in RS-232. When only 1 Modbus Exchange Unit is needed, port 2
should be chosen as port 1 is by default dedicated to PCM configuration from a
PC.

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

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

_______________________________________________________________________________________
AA M-SM01-A40028.41/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 8
STOP BITS : 1 or 2
PHYSICAL PROTOCOL : RS-232 (converted into RS-485 by an external
converter) or RS485
LINE 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 Modbus


network(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 with


specific slave devices. They monitor their slave devices, trigger the questions sent
to them and supply the application program with easily accessible interface tables
containing 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 (ie


variables 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 Modbus
I/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 the
customisation of the Modbus EUs and of the PECA/EVA, and CHESSELL slave
devices according to the parameters entered during the declaration of EU and
slave devices.

_______________________________________________________________________________________
AA M-SM01-A40028.42/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 the
EU 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 the


instructions 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 the
generation of a new og_mbus.gig, which must be imported in CADEPA.

_______________________________________________________________________________________
AA M-SM01-A40028.43/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-8035


automatically 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 characters
Name of the slave device. It appears in attribute location of the
MODBUS inputs/outputs.

Designation: Comment on 32 characters.

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

Subs. Nr : 1 to 255
Subscriber number on the Modbus network. Slave devices connected
to 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 same


PLC.

_______________________________________________________________________________________
AA M-SM01-A40028.44/A
Each of them must have a different Equipt. Nr. OGIV automatically
assigns a number to each slave: they may be modified except for
CHESSELL (Nr 32). When a CHESSELL is declared, equipment
numbers 28 to 32 are no more available. For OTHER devices refer to
the technical sheet of their DOMAIN block to check the rules for their
equipment number.

PECA or EVA electrical measurements acquisition units and CHESSELL


temperature acquisition units are the slave devices most commonly used in our
projects. The parameters of the DOMAIN blocks managing the communication with
those 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 the
project, 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 communication
with 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/O
variables.

- Write in AP_FST application (in CADEPA) the customisation of the DOMAIN block
using 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 stored
in AP_FST CADEPA application.

For PECA-EVA devices which do not follow the default configuration described next
paragraph and for all the CHESSELL and OTHER devices, further parameters must
be fixed.

The cursor being on the device to configure, use "Modbus devices"


"Configuration" or ALT C to do so.

_______________________________________________________________________________________
AA M-SM01-A40028.45/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 (ie
1 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 for
the 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 each
energy) = 21 analog inputs.

_______________________________________________________________________________________
AA M-SM01-A40028.46/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 : Standard
configuration described above. It
generates 21 analog inputs. If the
whole 21 inputs are not needed, click
on the related buttons to select or
remove the 1st or the last
measurement.

Units: Weight of the integer provided


by DMB_EVA. Click on the chosen
unit.
Be sure that the maximum value of
the measurement expressed in the
chosen 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 on
MODBUS network.

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

_______________________________________________________________________________________
AA M-SM01-A40028.47/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 current


slave device.

Number of measurements:
1 to 96.
Number of measurements
from CHESSELL.

Nbr of alarms/measurements
Number of thresholds for each
measurement (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 to


customise DMB_CHS block. The numbers of words and 16-bit words also allow
OGIV-8035 to generate the proper number of analog and logical inputs from
CHESSELL.

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

_______________________________________________________________________________________
AA M-SM01-A40028.48/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 parameters
have to be filled according to the technical sheet
of the DOMAIN block managing the
communication with the slave device.

Number of words/bits : Number of consecutive


analog or discrete variables received from or
sent to the slave device.

First address : Address in the PLC of the first


word or bit received from or sent to the device.

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

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

_______________________________________________________________________________________
AA M-SM01-A40028.49/A
4.2.4 Stage 3 : declaration of the Modbus inputs/outputs

- Select "Variables" "Modbus Inputs" or "Modbus Outputs" "Logical" or


"Analog". Fox Pro standard browse window is displayed.

- For each record, the same fields as for hardware inputs/outputs are displayed.
Refer to appendix C to know their meaning and format. Also refer to 2.2.4
(declaration of the hardware inputs/outputs) to have the rules for filling each field
and the way to copy, move, … variables.

- In addition to the analog and discrete inputs and outputs to and from the slave
devices, OGIV-8035 also generates one validation bit per device. This variable
is the output of the DOMAIN block managing the communication with the related
slave device. It is set to 1 by the block when the communication with the slave
device is OK and reset when the device does not communicate anymore.

Those validation bits are used by OGIV-8035 to validate the MODBUS I/O sent to
CENTRALOG (TS,TM). They have to be filled in the same way as discrete inputs.
In particular, their mnemonic must begin with "li_".

4.2.5 Stage 4 : printing of the Modbus input/output list

To print the Modbus I/O list, select "Printing" "Modbus" then proceed in the
same way as for the hardware I/O list (refer to 2.2.6).

_______________________________________________________________________________________
AA M-SM01-A40028.50/A
4.3 CONFIGURATION OF MODBUS MODULE

This configuration should be performed when building up the P8 folder of the


controller (stage 8 of chapter 2.3).

4.3.1 In P8 configuration software

- To declare a PCM module, choose F8 “others”, F1 “pcm” then PCM301.

In P8 configuration software when zooming in the PCM module, several


configuration modes may be chosen : CCM ONLY, BASIC, BAS/CCM, PCM CFG,
PROG PRT, PROG/CCM or CCM/PROG.

Choose PCM CFG (It means that PCM configuration will be performed thanks to
files loaded into the module : pcmexec.bat and hardexec.bat).

- To declare a MBM module, choose F8 “others”, F1 “pcm” then PCM300. “Config


Mode” must be declared as PROG PRT.
The communication parameters may then be modified (typically: Data rate =
‘19200’, Flow control = ‘none’, Parity = ‘none’, Stop bits = ‘1’, Bits/char =’1’)

4.3.2 pcmexec.bat (for PCM301 only)

This file is automatically executed by PCM :


- at power up

- at software initialisation ie after having pressed the RESTART pushbutton


(located just behind the front side cover of PCM module) less than 5 seconds.

The standard pcmexec.bat, available on PSM29D10015 floppy disk:


- configures the 2 serial ports of the module

- configures its 2 front side LEDS

- Launches MBPCM software.

It contains the following instructions:

I COM1: 19200,N,8,1,N,232
I COM2: 19200,N,8,1,N,232
R MBPCMV14.EXE /I5
B 1 01
B 2 04

_______________________________________________________________________________________
AA M-SM01-A40028.51/A
Lines 1 and 2 are the configuration of serial ports 1 and 2.

19200 : Baud rate


N : without parity (O for ODD, E for EVEN)
8 : 8 data bits
1 : 1 stop bits
N : no flow control (H for hardware flow control)
232 : RS232 (485,4 for full duplex RS-485)

Line 3 is the launching of MBPCMV13 software

Lines 4 and 5 are the configuration of User 1 and User 2 front side LEDs:

01 : the LED will flash when emitting on port 1


04 : the LED will flash when emitting on port 2

This file can be modified by means of any ASCII text editor such as Dos, Norton,
Fox Pro text editor or WINDOWS notepad. To have details about all the possible
commands, refer to document [5], appendix C.

4.3.3 hardexec.bat (for PCM301 only)

This file is automatically executed by PCM at hardware initialization ie after having


pressed the RESTART pushbutton more than 5 seconds.

The standard HARDEXEC.bat, available on PSM29D10015 floppy disk:


- Configure the 1st serial port to be ready to communicate with TERM F software

- Configure User 1 LED to flash when receiving signals on serial port 1.

It contains the following instructions:

I COM1: 19200,N,8,1,N,232
B 01 02

_______________________________________________________________________________________
AA M-SM01-A40028.52/A
4.3.4 Procedure to load MBPCMV13, PCMEXEC and HARDEXEC into PCM301

4.3.4.1 Needed tools

TERM F (IC641SWP023) software and IC690CBL702 cable to connect the PC to


PCM.

4.3.4.2 Procedure

1. If not already done, install TERM F on the PC (a:/install). It creates c:\PCOP

2. Copy mbpcmv14.exe, pcmexec.bat and hardexec.bat to c:/PCOP

3. Connect COM1 of the PC to the port 1 of PCM with CBL702 cable.

4. With P8 or HHP, stop the CPU of the CPU rack where PCM is located.

5. Launch TERM F (type "termf" in PCOP directory). The screen becomes black.

6. Remove PCM cover and press the RESTART pushbutton longer than 5s. ">"
should be displayed. If needed, press "ENTER". It after several attempts, ">"
is not displayed yet, power off the CPU rack, remove the PCM module,
disconnect the battery and short-circuit its 2 pins with a screwdriver. It resets
PCM memory and puts it back in its factory configuration, ready to
communicate with TERM F.

7. Type "!!" to be in interactive mode

8. Load the 3 files into PCM by typing :


"L pcmexec.bat"
"L hardexec.bat"
"L mbpcmv13.exe" (this latter takes time !).

9. D" to check that those 3 files are actually stored in PCM module and that they
are the only ones. If PCM returns other files, delete them by typing:
X <name of the file to delete>.

10 . Use ALT Z to quit TERM F

11 . Restart PCM by pressing its RESTART pushbutton less than 5s then restart
the CPU. If PCM doesn't try to communicate on Modbus network about 6s
later (US1/2 LEDs never light) and P8 indicates "Comm-req fault_wrong
number of ID task", then power off the PLC and up again a few seconds later.

For more details about TERM F and PCM commands, refer to document [5]: appendix
C, D and chapter 2, 4.

_______________________________________________________________________________________
AA M-SM01-A40028.53/A
5 F8000 IMPLEMENTATION

- F8000 network allows to exchange data inside an automation cell, between


SUB, IHR and MAIN PLCs.

- 2 standards F8000 configurations are provided for hydraulic applications in


Domain P320 EL 4-C

. a redundant cell with 2 IHR and 2 SUBs

. a redundant cell with 2 IHR and 3 SUBs

They are described in documents [14] (S8000_E) and [15] (S8000_F), chapter 4,
tables 1 and 2.

- For redundant or not redundant cells with up ot 2 IHR and up to 2 SUBs, the first
configuration should be used.

- For redundant or not redundant cells with up ot 2 IHR and up to 3 SUBs, the
second configuration should be used.

- If more than 2 IHR or more than 3 SUBs are needed or if the exchanges
implemented in the 2 standard configurations do not fit, additional configurations
may be developed. But, this is a complex operation which requires to study the
load on the F8000, the load of the CPUs and to fit fill many parameters.It should
therefore be avoided as far as possible.

As shown in documents [14] and [15], chapter 4, tables 1 and 2:

The variables exchanged on F8000 are taken or received in word areas (%AQ,
%AI).

This prevents having waste bit areas (%I, %Q) dedicated to pre-configured
exchanges not used on the project.
Standard P8 programs from Hydro Domain, DF8_IN for MAIN and DF8_I_S for
SUBs, copy in %I area the Boolean variable received from the F8000 in %AQ
area. So that the application program can easily work on them. DF8_OUT copies
in %AQ area the Boolean variables to send on F8000 stored by the application
program in %Q area.
- The tables of analog variables exchanged between MAIN and SUBs on F8000,
only contains 62 variables. As more variables may need to be exchanged,
DF8_IN and DF8_I_S multiplex a table of 244 variables into the F8000 62 word
message. DF8_OUT de-multiplex the 62 word message into a 244 word table in
the receiving controller.

_______________________________________________________________________________________
AA M-SM01-A40028.54/A
5.1 DECLARATION OF F8000 EXCHANGE AREAS

This operation is performed when creating the project. The customisation of the
exchange areas may be modified at any time.

Select “Networks” “F8000” “Exchange areas definition”.

The following table is displayed

(example of a MAIN controller)

(example of a SUB controller)

The user must customise it according to the following table :

(The parameters which cannot be modified are in italics .Those which may be modified are
in bold characters. The values indicated in the table are the default values)

_______________________________________________________________________________________
AA M-SM01-A40028.55/A
Type of Area in Current PLC Area in receiving/sending PLC
current Function From/To
PLC 1st address Nb Possible range 1st address Possible range
MAIN Main discrete inputs %I0001 32 %I0001-1648

- Area dedicated to MAIN wired inputs.


- There must be at least one discrete input module in the MAIN PLC to acquire the synchronisation top signal in
%I0002.
- In a redundant cell, MAIN has only one discrete input module, therefore this area is %I0001 – 0032.
- In a non-redundant cell, this area has to be extended

MAIN IHR1 discrete inputs %I0033 ≤ 256 %I0033-1648 From IHR1 %I0001 %I0001-0256
SUB
- Reception of IHR1 discrete inputs

MAIN IHR2 discrete inputs %I0289 ≤ 256 %I0033-1648 From IHR2 %I0001 %I0001-0256
SUB
- Reception of IHR1 discrete inputs

MAIN SUB1 discrete inputs %I0545 N (≤ 512) %I0033-1648 From SUB1 %I0001 %I0001-1648

- Reception of SUB1 wired discrete inputs


MAIN SUB1 discrete inputs %I0545 + N M (≤ 512-N) %I0033-1648 From SUB1 %Q1025 %Q1025 - 1280

- Reception of SUB1 processed bits (ie variables flagged “To F8000” in SUB1 except the discrete inputs above)
- This area MUST BE CONTIGUOUS to “SUB1 discrete inputs”
- The number of SUB1 discrete inputs + process bits must not exceed 512

___________________________________________________________________________________________________________________________________________
AA M-SM01-A40028.56/A
Type of Area in Current PLC Area in receiving/sending PLC
current Function From/To
PLC 1st address Nb Possible range 1st address Possible range
MAIN SUB1 discrete inputs
SUB2 process bits
SUB3 discrete inputs - idem SUB1
SUB3 process bits

MAIN SUB1 discrete outputs %Q0001 N1 %Q001 – 0512 To SUB1 %Q0001 %Q001 – 0512
SUB2 discrete outputs %Qxxxx N2 %Q001 – 0512 To SUB2 %Qxxxx %Q001 – 0512
SUB3 discrete outputs %Qyyyy N3 %Q001 – 0512 To SUB3 %Qyyyy %Q001 – 0512
MAIN process bits %Qzzzz N4 %Q001 – 0512 To SUB1 %Qzzzz %Q001 – 0512
MAIN process bits %Qzzzz N4 %Q001 – 0512 To SUB2 %Qzzzz %Q001 – 0512
MAIN process bits %Qzzzz N4 %Q001 – 0512 To SUB3 %Qzzzz %Q001 – 0512

- %Q0001-0512 of MAIN PLC are broadcast into %Q0001-0512 of all the SUB PLCs.They are used to activate SUB
wired discrete outputs directly from MAIN PLC and also to send process bits (orders for example) to SUB PLCs.
- the user must customise the sharing out of %Q0001 – 0512 between SUBi discrete outputs (%Q0001 to %Q0001 +
N1-1 must be references assigned to discrete output modules in SUB1; %Qxxxx to %Qxxxx + N2-1 idem in SUB2;
%Qyyyy to %Qyyyy + N3-1 idem in SUB3) and MAIN process bits sent to SUBs ( OGIV displays one “Main process
bits” area per SUB but there is only one area : its 1st address, %Qzzzz, and number of bits, is the same on the 3 lines).
- The SUB discrete outputs must be declared in SUB PLCs then imported in MAIN.

MAIN MAIN analog variables %AI1537 244 %AI1537- 1780 To SUB1 %AI1793 %AI1793 – 2036
MAIN analog variables %AI1537 244 %AI1537- 1780 To SUB2 %AI1793 %AI1793 – 2036
MAIN analog variables %AI1537 244 %AI1537- 1780 To SUB3 %AI1793 %AI1793 - 2036

- OGIV displays one “Main analog variables” per SUB but there is only one area broadcast to all the SUBs.
- OGIV copies in this area all the analog variables flagged “To F8000”.
- This area is processed by Domain standard programs DF8_IN, DF8_I_S and DF8_OUT. When fewer than 62
variables are copied in the area, they are broadcast every 100 ms. When there are more than 62 variables, they are
multiplexed. Each analog variables is then sent approximately every 250 * n ms, with n = number of 62 variables blocks
(n=2 if there are between 63 and 122 variables, n=3 between 123 and 183 variables, n=4 between 184 and 244
variables)

___________________________________________________________________________________________________________________________________________
AA M-SM01-A40028.57/A
Type of Area in Current PLC Area in receiving/sending PLC
current Function From/To
PLC 1st address Nb Possible range 1st address Possible range
MAIN SUB1 analog variables %AI1793 244 %AI1793 – 2036 From SUB1 %AI1537 %AI1537- 1780

- Reception of the analog variables (wired or modbus inputs, processed variables) flagged “To F8000” in SUB1.

MAIN SUB2 analog variables %AI2049 244 %AI2049 - 2308 From SUB2 %AI1537 %AI1537- 1780

- Reception of the analog variables (wired or modbus inputs, processed variables) flagged “To F8000” in SUB1.
- In case, there are 3 SUBs, this area must be limited to 188 variables.

MAIN SUB3 analog variables %AI2321 188 %AI2321 - 2484 From SUB3 %AI1537 %AI1537- 1724

SUB SUB1 discrete variables %I1025 128 %I0001 - 1648 From SUB1 %Q1281 %Q1281 - 1408

- Discrete variables broadcast by SUB1 to the other SUBs.


- OGIV copies in %Q1281 – 1408 the variables flagged “Intersub” in SUB
- This area is not displayed in SUB1

SUB SUB2 discrete variables %I1153 128 %I0001 - 1648 From SUB2 %Q1281 %Q1281 - 1408

SUB SUB3 discrete variables %I1281 128 %I0001 - 1648 From SUB3 %Q1281 %Q1281 - 1408

SUB SUB1 analog variables %AI1377 8 %AI1377 - 1384 From SUB1 %AQ0409 %AQ0409 - 0416

- Analog variables broadcast by SUB1 to the other SUBs.


- OGIV copies in %AQ0409- 0416, the variables flagged “Intersub” in SUBs.
- This area is not displayed in SUB1

SUB SUB2 analog variables %AI1441 8 %AI1441 – 1448 From SUB2 %AQ0409 %AQ0409 - 0416

SUB SUB3 analog variables %AI1489 8 %AI1489 - 1496 From SUB3 %AQ0409 %AQ0409 - 0416

___________________________________________________________________________________________________________________________________________
AA M-SM01-A40028.58/A
Once the configuration is performed, press “Esc” or “CTRL W” to validate. The
F8000 inputs references are then generated (with no attribute filled yet). The SUB
discrete outputs references directly activated by MAIN are also generated (with no
attribute filled yet) in MAIN PLC.

5.2 UPDATING OF F8000 VARIABLES

The variables are declared (mnemonic, label, state message, unit…) in the sending
PLC…
The only exception are the wired outputs of Subs directly activated by MAIN. They
must be declared in the SUBs.

Once the variables have been declared in the issuer PLC, they must be exported
from this PLC then imported in the addressee PLC.

This procedure must be performed after each addition/deletion of a “To F8000” flag
or each modification of an exchanged variable (level, unit….).

5.2.1 Extraction of the variables to send on F8000

- Must be flagged ‘S’ (discrete variables) or ‘M’ (analog variables) in the field ‘To
F8000 ’.

The discrete inputs of an IHR PLC and the SUB discrete inputs and outputs
belonging needn’t be flagged ‘To F8000’: they are systematically sent on F8000 to
the areas defined in the “Exchange Area definition”.

- The variables which don’t belong to those discrete inputs/outputs areas above,
must be flagged “To F8000” to be exchanged between MAIn and SUB or
“Intersub” to be exchanged between 2 SUBs. They will be copied in the
exchanged area “Process bits” or “Analog variables”.

- Select “Network” “F8000” “Export” to process the variables to send. Then:

- OGIV-8035 assigns a rank to each variable ( = order in the exchange area ).

When a variable is no more flagged ‘To F8000’ or ‘Intersub’ its rank becomes
free. The address of the other variables sent on F8000 is not changed so that the
other variables keep their current address in all the receiving PLCs.

If many “To F8000” flags have been removed, the user may wish to gather the
remaining variables at the beginning of the message. To do so, the ranks must be
reset (refer to 11.6.2) before launching “Network” “F8000” “Export”.

- OGIV-8035 generates < Project name >.f80 file with :

. Mnemonic

. Label

_______________________________________________________________________________________
AA M-SM01-A40028.59/A
. State_1 message

. STD

. Address in the exchange area


Ex: %AI(1537 + r) for analog variables (r is the rank)
%Q(1025 + r) for SUB process bits sent to MAIN.
. Unit

. V mini / V maxi

. PLC mini / PLC maxi

. Acq. rate

of all the variables flagged ‘To F8000’.

Flag ‘To MMI ’ is not exported as the variable may be displayed on the MMI of
the sending PLC but not on the MMI of the receiving PLC.

- In this file is also stored, in a transparent way for the user the validation bit of
each variable:

. The input of the module dedicated to polarity acquisition for discrete


inputs

. The validating bit for the analog inputs

. « Communication OK » for MODBUS inputs

. ld_f80_subs_run_xx for the other variables (xx is the F8000 subscriber


number of the current PLC)

Those information will be used in MAIN PLC to validate the F8000 inputs
flagged “To Ctrlog”. Therefore, do not forget in SUB PLC to send (ie flag “To
F8000”) the validation bits of the variables due to be sent to CENTRALOG
by MAIN PLC.

That file is available under the directory \OGIV-8035\<project name>.prj

- OGIV-8035 generates the following files under the directory \cadepa\<project


name>.prj\ap_fst.apl. Those graphs must be imported in CADEPA, application
AP_OUT:

_______________________________________________________________________________________
AA M-SM01-A40028.60/A
. og_f8do.gig : copies the analog variables to send on F8000 in the word
area of the broadcast message :
[dd_f80_e_xxx = di_…] with dd_f80_e_xxx = %AI(1984+xxx)
di_… variable flagged “To F8000”

. og_f8lo.gig : idem for discrete variables.


ld_f80_e_xxx = li_… with ld_f80_e_xxx = %Q(257+xxx)
li_… variable flagged “To F8000”
- OGIV-8035 also generates og_f8.gig to import in application AP_FST. This graph
customises the Domain blocks DF8_IN, DF8_I_S, DF8_OUT.

5.2.2 Import F8000 variables

It updates the F8000 input references generated by “Network exchange areas”


screen with the attributes already declared in the sending PLC and stored in
<sending project>. f80.

Select “Network” “F8000” “Import”.

- For each sending PLC declared in “Network exchange areas”, OGIV tries to find
the related .f80 file under the OGIV-8035 directory of the sending project:

• If OGIV finds \ogiv8035\<sending project>.prj\<sending project>.f80, it


displays: « Updating from <sending project>.prj ? (y/n) »
Answer “y” to actually launch the update.
Press any other key to avoid the update from that particular sending PLC.

• Otherwise (sending PLC is not local or « F8000 export » has not yet been
performed in the sending PLC), OGIV-8035 indicates « <Sending project >.prj
not declared in local » and displays FoxPro standard screen to open files.

If the .f80 file is available on a floppy disk or elsewhere, select it from that
screen to launch the update.
_______________________________________________________________________________________
AA M-SM01-A40028.61/A
If the .f80 file of the related sending PLC is not available or if the update is not
needed, click on “Cancel”.
- At the 1st update, the empty F80 inputs generated by the Exchange areas screen
are filled with the attributes contained in <sending project>.f80 (Refer to 4.2.1)

The first 3 characters of the mnemonics in the sending PLC are replaced with li_
or di_ in the receiving PLC (except for the discrete outputs of SUB controllers
which is lo_).

- At the next updates, OGIV-8035 proceeds as follows:

• For variables which mnemonic in the new imported .f80 file already exist in
the F8000 received variables of the current project :

Their attributes in the current PLC are replaced with those of the new .f80 file.
The additional attributes («To MMI», «To S8000», «To Ctrlog») keep their
value.

• A variable which mnemonic in the imported .f80 file does not exist in the
current project is added, except if its rank is occupied in the receiving PLC by
a variable which mnemonic does not exist any longer in the .f80 file. In such
case, the following screen appears:

If the user answers:

R 1. The mnemonic of the variable in the current PLC is


replaced by the mnemonic in the sending PLC.

2. The attributes are updating according to the sending PLC.

1. The additional attributes («To MMI», «To S8000», «To


Ctrlog») keep their value.

(That case occurs when the variable has been renamed in the
sending PLC).

A Idem R except for the additonal attributes which are reset.

(That case occurs when a variable previously sent by the


receiving PLC is not sent any more and its rank is assigned to
a new variable).

_______________________________________________________________________________________
AA M-SM01-A40028.62/A
K Idem R but the mnemonic in the current PLC is not changed.

(That case occurs when the user has renamed the variable in
the receiving PLC).
- Once the update is performed, a report is displayed. It indicates which variables
have been deleted, added, renamed or shifted from an address to another.

To validate the update, the user must then answer “y” to the question:

The report \OGIV-8035\<project name >\link_f80.txt may be consulted with the


option “Display file” of “Utilities” menu.

5.3 CONSULTATION AND CUSTOMISATION OF F8000 VARIABLES

FIELD Logical Inputs Analog Inputs

To S8000 *
In Main PLCs only
BLANK ( = not sent ) BLANK ( = not sent )
BS ( = broadcast TS ) BM ( = broadcast TM )
PS ( = TS sent to PLC 16** only ) PM ( = TM sent to PLC 16** only )

To MMI *
In Main or SUB PLCs only
BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )

** PLC 16 = regrouping PLC (Mimic for example)

* Press the spacebar to scroll through the list then validates with Enter.

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

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

_______________________________________________________________________________________
AA M-SM01-A40028.63/A
5.4 PRINTING OF THE F8000 INPUT LIST

To print the f8000 or S8000 Input list, select "Printing" "Network" “F8000” then
proceed in the same way as for the hardware I/O list (refer to chapter 2.2.6 ).

_______________________________________________________________________________________
AA M-SM01-A40028.64/A
6 S8000 IMPLEMENTATION

S8000 network allows to exchange data between the automation cells, and to
exchange data with the CENTRALOG. The present chapter only deals with the
exchanges between automation cells.

- The number of data sent on the S8000 network by a cell to the other cells is
limited. These limits are fixed to:

. 20 words for the broadcast variables. They include the analog variables
type “BM” (1 variable = 1 word) and the discrete variables type “BS” (16
variables = 1 word). The 1st bit of the message is used to check the presence
of the cell on S8000. Therefore, the max number of BM is 19 and the 1st word
of BS only contains 15 bits.

. 64 words for the point to point variables (sent to the regrouping cell). They
include the analog variables type “PM” (1 variable = 1 word) and the discrete
variables type “PS” (16 variables = 1 word). The 1st bit of the message is used
to detect the arrival of a new message. Therefore, the max number of PM is
63 and the 1st word of PS only contains 15 bits.

. Furthermore, the total number of discrete variables broadcast or sent by a cell


can not exceed 256 : Number of “BS” + number of “PS” ≤ 256 .

- The number of data received from the S8000 network by a controller from the
other controllers is configured by the user. This procedure is described hereafter.

_______________________________________________________________________________________
AA M-SM01-A40028.65/A
6.1 DECLARATION OF S8000 EXCHANGE AREAS

Select “Networks” “S8000” “Exchange areas definition”.

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

- Exchange : - S8000-BS = discrete variables broadcast to all cells,


- S8000-BM = analog variables broadcast to all cells,
- S8000-PS = discrete variables sent to the regrouping cell *
- S8000-PM = analog variables sent to the regrouping cell *
* S8000-PS / PM are available in the regrouping cell only.

- From Project : Issuer project name. Only the projects declared on the PC (in
local or remote) are displayed .

- Range : Number of the received bits or words.

- Receiving Area : First and last addresses of the receiving area.

. For discrete variables, the user has to enter the 1st address according to
the following rules:
→ the receiving area must be included in %I33 – %I1648.
→ there must be no common address with the F8000 exchange areas.
THE USER HAS TO CHECK THAT BY HIMSELF as it is not tested by OGIV.
. For analog variables, OGIV fills the receiving area automatically as it can
not be customised by the user.

- Sending Area : Not used

_______________________________________________________________________________________
AA M-SM01-A40028.66/A
Once the exchange areas are entered, click on ‘Ok’ to validate:

→ The variables received from S8000 are automatically created in the project and
available in "Variables" "S8000".

→ OGIV-8035 automatically generates og_s8.gig in cadepa \ <project name>.prj


\ ap_fst.apl . This graph contains the customisation of Domain block DS8_IN. It
must be imported in CADEPA, AP_FST application.

OGIV-8035 then propose to import the S8000 variables as described in §6.2.2.

_______________________________________________________________________________________
AA M-SM01-A40028.67/A
6.2 UPDATING OF S8000 VARIABLES

To make the update for the first time or to ensure the consistency of the exchanged
variables between issuer and receiving PLCs at each modification, addition or
deletion of a network variable, follow the procedure hereafter:

6.2.1 Extraction of the variables to send on S8000

In the sending PLC, select “Networks” “S8000” “Export”.

- This function extracts all the variables that are flagged in the field “to S8000”.
These variables are stored in a file located in the directory of the OGIV-8035
current project and named < Project name >.s80.

- If the receiving project is not located on the same PC as the current project, the
user has to copy these files onto a diskette to import them on the PC of the
receiving project.

- OGIV-8035 also automatically generates og_s8o.gig in cadepa\


<nom_projet>.prj\ ap_out.apl. This graph must be imported in CADEPA AP_OUT
application after each export.

- OGIV-8035 checks that: (Rank of last BS) / 16 + Number of BM ≤ 20


and (Rank of last PS) / 16 + Number of PM ≤ 64.
If it is not the case, OGIV-8035 displays "BM out of range". og_s8o.gig is
nevertheless generated but the inter-controller exchanges won't work properly.

6.2.2 Import of S8000 variables

In the receiving PLC, select “Networks” “S8000” “Import”.

Please refer to §5.2.2 "Import F8000 variables" for details about the procedure
which is the same for S8000 and F8000.

The imported variables are renamed. The first 3 characters of the mnemonics are
replaced with li_ or di_. If the 4 and 5th character are not numeric, OGIV-8035 adds
the UO number before them. This to avoid identical mnemonics in the receiving
PLCs when several issuers send the same variable (case of unit PLCs).
Ex: Mnemonic sent by a PLC which UO number is 02 : lv_gta_titi
Mnemonic in receiving PLC : li_02gta_titi.

_______________________________________________________________________________________
AA M-SM01-A40028.68/A
6.2.3 S8000 exchanges to, from or between unit cells

- If a MAIN controller has to receive variables from unit cells (and only one unit cell
is actually implemented in OGIV-8035 and CADEPA), all the unit projects must be
declared on the PC on which this MAIN PLC is implemented. For example,
GTA01 is declared 'Local', GTA02 and GTA03 are not flagged 'Local'.

- In unit project, once the S8000 export is performed, use "Project" "Duplication"
to duplicate the .s80 file. Refer to chapter 10 "DUPLICATION OF EXPORTED
PROJECT DATA".

- In the S8000 exchange areas definition of the receiving PLC, the discrete and
analog variables received from each unit controller must be declared:

- The variables from the reference unit cell are then imported directly from the PC if
the receiving controller is on the same PC as the unit project, from a floppy disk
otherwise.

- The variables from the duplicated unit cells are imported via a floppy disk.

_______________________________________________________________________________________
AA M-SM01-A40028.69/A
6.3 DECLARATION OF S8000 INPUTS

- Select "Variables" "S8000 Inputs” "Logical" or "Analog". FoxPro standard


browse window is displayed.

FIELD Logical Inputs Analog Inputs

Location Name of the issuer project. Can't be modified.


Address Idem
Initialised by import from issuer PLC. They may be modified (but it is not
Mnemonic recommended)
Ii_... DI_...

Label
State 1
STD
Initialised by import from issuer PLC.
Unit May be modified but will be lost at next import !
Acq. Rate
PLC mini /
PLC maxi
V mini /
Not applicable From issuer PLC. Cannot be modified.
V maxi
To Ctrlog * BLANK ( = not sent ) or S ( = TS ) BLANK ( = not sent ) or M ( = TM )

Var Ref Not imported from issuer PLC.


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

* Press the spacebar to scroll through the list then validate with Enter.

6.4 PRINTING OF THE S8000 INPUT LIST

To print the S8000 Input list, select "Printing" "Network" “S8000” then proceed
in the same way as for the hardware I/O list (refer to § 3.2.5 ).

_______________________________________________________________________________________
AA M-SM01-A40028.70/A
7 DUALITY

7.1 INTRODUCTION

7.1.1 Definition

About the vocabulary used:

- Redundancy: defines the hardware structure for dual communication, for F8000
taking over and for basic exchanges.

- Duality: defines the control of the redundancy according to the application


process.

- Primary: defines the controller in the redundancy structure who controls the
application process.

- Secondary: defines the controller in the redundancy structure who doesn't control
the application process.

- Insertion: intermediary mode during the difference of data status between the
dual controllers. A controller in insertion mode is unavailable for controlling the
process.

The redundancy is not detailed in this document.; for this refer to :

- Guide d'INSTALLATION et d'UTILISATION du domaine P320 EL 4-C pour


S8000-F (P-TP11-A43511a)
Ou
- Guide d'INSTALLATION et d'UTILISATION du domaine P320 EL 4-C pour
S8000-E (P-TP11-A43510a)

7.1.2 Hardware architecture

For system based on Fip unit network, refer to: P-TP11-A43511a

_______________________________________________________________________________________
AA M-SM01-A40028.71/A
For system based on Ethernet unit network, refer to: P-TP11-A43510a
7.1.3 Principles

A main controller declared redundand (two controllers with the same hardware and
software structure) has specific exchanges for redundancy control. The duality uses
these resources for optimizing the redundancy in accordance with the applications
running into the controllers.
In function of the network architecture and the possibilities of each system, the
duality controls several services:

7.1.3.1 Telecommands and Televalues Centralog updating.

On the S8000 network, the two controllers of the redundancy structure have their
own subscriber number. The Centralog can only exchange TCs and TVCs to only
one controller (the primary). The duality service update the secondary for each new
TC or TVC received due to permit to the secondary to follow the process and update
its application software.

CENTRALOG

TC & TVC
S8000- E o r F

M A IN Update STANDBY

F8000

SUB- 1

For exchanging theses informations, the application has to inform the duality
domain by setting to "1" the bit "ld_mod_remote" (DC_REM (%M738)) if the process
runs in Centralog mode and by "0" if not.

Nota: the variable "ld_mod_remote" is created into Cadepa and addressed by


import into Ogiv. This variable is not initialized by duality domain.

Nota: in case of regrouping cell, the duality can manage the 128 TVCs by a mux-
demux principle in function of the number of usefull TVCs.

_______________________________________________________________________________________
AA M-SM01-A40028.72/A
7.1.3.2 Telecommands and Televalues local HMI updating.

Some local HMI cannot communicate to the two controllers of the redundancy
structure. We suppose that the communication is set between the local HMI and the
primary. The duality service update the secondary for each new TC or TVC received
due to permit to the secondary to follow the process and update its application
software.

TC & TVC S8000- E o r F

Local HMI
M A IN Update ST ANDBY

F8000

SUB- 1

For exchanging theses informations, the application has to inform the duality domain
by setting to "1" the bit "ld_mod_local" (DC_LOC (%M737)) if the process runs in local
mode and by "0" if not.

Nota: the variable "ld_mod_local" is created into Cadepa and addressed by import
into Ogiv. This variable is not initialized by duality domain.

7.1.3.3 Logical and numerical memories updating.

The application can define logical memories and numerical memories by filling the
field "dual" of Ogiv with "S" (logical) or "M" (numerical).

_______________________________________________________________________________________
AA M-SM01-A40028.73/A
These informations will be exchanged from primary controller to secondary
controller in a particulary way. The cell can be started with only the primary
controller (the secondary can be out of order or its software cycle can be in stop
mode); the application is executed and the process has been modified from its initial
status.

When the secondary controller starts, this controller will be positionned in insertion
mode and will be updated by the primary through the duality service. In this case,
the memories will be exchanged till the full update (check up of memories received
into the secondary by feed back processing).

S8000- E or F

STEP 1: Memories updating M A IN


Memories
ST ANDBY

F8000

SUB- 1

S 800 0- E o r F

Memories
STEP 2: Feed Back M A IN ST ANDBY

F8000

SUB- 1

S8000- E o r F

Memories

STEP 3: Control of coherency M AIN ST ANDBY

F8000

SUB- 1

_______________________________________________________________________________________
AA M-SM01-A40028.74/A
7.1.3.4 Insertion mode control.

The basic redundancy only controls the network availability of the controllers. In
case of failure of the primary, the secondary take over the control of process
whithout looking at the possibility of following the application. This is not enough
safety for hydro application (sequence running, mechanical failure…). The duality
instores a "insertion mode" for the secondary controller who just start in the
configuration. During this mode, the controller is considered as inefficient to follow
the application.
While the insertion mode of the secondary, the duality exchanges informations from
the primary and does some checks:

- checking of the "stable status" indicator (for a unit application). This indicator is
filled by the application and is tested by duality. If the indicator is not in
accordance, the secondary is kept in insertion mode. The indicator name in
Cadepa is "dd_dual_st_stus". It is created into Cadepa and addressed by import
into Ogiv. If the indicator is not filled, the accordance will be applied.

- checking of the "requested status" indicator (for a unit application). This indicator
is filled by the application and is tested by duality. If the indicator is not in
accordance, the secondary is kept in insertion mode. The indicator name in
Cadepa is "dd_dual_rq_stus". It is created into Cadepa and addressed by import
into Ogiv. If the indicator is not filled, the accordance will be applied.

- checking of the "sequence status" indicator (for a unit application). This indicator
is filled by the application and is tested by duality. If the indicator is not in
accordance, the secondary is kept in insertion mode. The indicator name in
Cadepa is "dd_dual_seq_stus". It is created into Cadepa and addressed by
import into Ogiv. If the indicator is not filled, the accordance will be applied.

- checking of logical & numerical memories. If the memory datas are not in
accordance, the secondary is kept in insertion mode. If none memories are
declared into Ogiv, the accordance will be applied.

7.1.4 Duality safety mode.

In relation with the process, the duality performs some specific action on controller
to prevent malfunctions and to avoid damage on mechanical or electrical systems.

_______________________________________________________________________________________
AA M-SM01-A40028.75/A
7.1.4.1 Taking over inhibition

The application can inhibit temporarily the taking over by setting to "1" the indicator
"ld_inst_stus" if the main controller is in an instable status. The indicator is created
into Cadepa and addressed by import into Ogiv.This function is to avoid taking over
following to another faults than F8000 network faults and if necessary in accordance
with application principles. The taking over will be authorised again when the
indicator will be set to "0".

Warning: The system domain erases automatically this indicator to "0" if the
primary controller is no more master according to F8000
administration.

7.1.4.2 Stopping request ( controller in insertion)

If the main controller is in the status "master" for primary and "insertion" for the
secondary, and if a taking over is detected, the secondary is stopped by duality
(duality considers that a controller in insertion mode is not able to follow correctly the
process).

7.1.4.3 Application stopping request (loss of messages)

The application controls during the phase "master" "slave" the update exchanges
between the primary and the secondary. If one loss is detected, the duality set to "1"
the indicator "ld_dual_update_flt" which can be used by application. The indicator
is created into Cadepa and addressed by import into Ogiv.

In case of loss of messages, the application can decide to stop the secondary
controller. The application has to set to "1" the indicator "ld_dual_stop_req" which
authorizes the stopping order. The indicator is created into Cadepa and addressed
by import into Ogiv.

7.1.4.4 Application insertion mode request (loss of messages)

In case of loss of messages, the application can decide to put the secondary
controller in insertion mode (tentative of general updating). The application has to
set to "1" the indicator "ld_dual_ins_req" which authorizes the insertion mode
order. The indicator is created into Cadepa and addressed by import into Ogiv.

_______________________________________________________________________________________
AA M-SM01-A40028.76/A
8 EXPORT TO CENTRALOG

From variables flagged to be TS, TM, TC and TVC, OGIV-8035 generates exchange
files to update CENTRALOG. Depending of the project, the database management
tool for Centralog, can be MICROETE or CONTROCAD

8.1 EXPORT TO MICROETE

Select “Import / Export” “CENTRALOG”. The following screen is displayed:

TS : When flagged, program files og_ts_c.gig


is created in AP_OUT application of CADEPA
project.

TM : When flagged, program files


og_tm_c.gig is created in AP_OUT
application of CADEPA project.

CENTRALOG files : Defines the location


where will be written export tables for
CENTRALOG.

After validation by clicking on « Ok » OGIV-8035 generates 5 files

<PLC name in Centralog >ts.dbf (list of Logical variables sent to Centralog)


<PLC name in Centralog >th.dbf (list of Timetag discrete inputs sent to Centralog)
<PLC name in Centralog >tm.dbf (list of Analog variables sent to Centralog)
<PLC name in Centralog >tc.dbf (list of Logical variables received from Centralog)
<PLC name in Centralog >tm.dbf (list of Analog variables received from Centralog)

Refer to Appendix C to know the other attributes exported to update CENTRALOG.

After processing, all details about Export are recorded in imex.txt file and displayed
on screen. Only one error is sufficient to prevent CENTRALOG from importing the
whole of the variables. More, the updating is global, therefore CENTRALOG needs
5 OGIV-8035 files.

_______________________________________________________________________________________
AA M-SM01-A40028.77/A
The instructions about the utilisation of the 5 files generated by OGIV-8035 are
described in note printable from CENTRALOG:

00KIT
GENERAL POWER PLANT
COMPUTER SYSTEM
DATA BASE CREATING
USER GUIDE

8.2 EXPORT TO CONTROCAD

Select “Import / Export” “CENTRALOG”. The screen and the function is


approximately the same as described hereabove:

After validation by clicking on « Ok » OGIV-8035 generates only 1 file

<PLC name in Centralog >.txt (list of all variables sent to Centralog)


Refer to Appendix C to know the other attributes exported to update CENTRALOG.

After processing, all details about Export are recorded in imex.txt file and displayed
on screen as the export to Microete. The instructions about the utilisation of the file
generated by OGIV-8035 are described in note printable from CENTRALOG:

00KIT
GENERAL POWER PLANT
COMPUTER SYSTEM
DATA BASE CREATING
USER GUIDE

_______________________________________________________________________________________
AA M-SM01-A40028.78/A
9 EXPORT TO MAN MACHINE INTERFACE

OGIV-8035 ensures the interface with 2 types of MMI:

• CITECT

• INTERACT

The variables flagged to be TS or TM are copied in the memory area sent onto SNP
network to CITECT or INTERACT MMI.

OGIV-8035 automatically assigns address when a variable is flagged TC or TVC.

Associated CADEPA program files are created in AP_OUT.


• og_ts_i.gig

• og_tm_i.gig

Moreover, OGIV-8035 generated database files allowing creation or updating of


CITECT or INTERACT data. The attributes of variables sent or received from MMI
are arranged:
- in 3 files for CITECT

. <PLC name in CENTRALOG>al.dbf (List of alarms sent to MMI)

. <PLC name in CENTRALOG>vr.dbf (List of variables sent or received from


MMI)

. <PLC name in CENTRALOG>ch.dbf (English/Chinese translation table)

The instructions about the utilisation in CITECT of the 3 tables generated by


OGIV8035 are described in note:

LOCAL MAN/MACHINE INTERFACE


SOFTWARE INSTALLATION
USER’S MANUAL
CGEGBZ00SKITPG505

- in 2 files for INTERACT

. amm.dat (List of alarms sent to MMI)

. interact.tag (List of variables sent or received from MMI)

_______________________________________________________________________________________
AA M-SM01-A40028.79/A
Refer to Appendix C for the list of attributes of the variables exported to MMI.

9.1 GENERATION OF MMI EXPORT FILES

Select “Import /export” “MMI”; The following screen is displayed:

TS : When flagged, program files og_ts_i.gig is created in AP_OUT application of


CADEPA project.

TM : When flagged, program files og_tm_i.gig is created in AP_OUT application of


CADEPA project.

These two files contained only variables which are sent to MMI.
Variables which are sent to MMI and also to Centralog are in og_ts_c.gig and
og_tm_c.gig. The MMI rank is the same as Centralog rank. Therefore, when a
variable is flagged “MMI” and “Centralog”, it is necessary to proceed to an export
Centralog then, an export to MMI.

Interact Directory : Defines the location where will be written Interact export files.
Usually : \Machshop\projects\interact\< Project Name >\appfiles\< Appl. Name>

To launch Export click on “Ok”.

_______________________________________________________________________________________
AA M-SM01-A40028.80/A
10 DUPLICATION OF EXPORTED PROJECT DATA

In case of projects strictly identical, it is possible to declare only one project in


reference and to duplicate his exported data’s, in particular to CENTRALOG or to
other projects on a same network.

10.1 DUPLICATION OF S8000 DATAS

First you have to select the file where are located the datas to duplicate. Once the
file selected, a screen is displayed

. Project : project target name

. S8000 Subscriber : Subscriber Nr of the new project

. Operating Units : In the left of this area appears the Operating Units list
contained in the .s80 file of the current project. These Operating Unit names
are extracted from the mnemonic :

. from the 4th characters up to 9th when the 4th characters is a digit or

. from the 4th characters up to 7th when the 4th characters is a letter

. In the right of this area appears the corresponding list of the new operating
units that you have defined in the bottom of this screen.

After clicked on Duplication button, a new file .s80 is generated in which,


“Mnemonic”, “Subscriber Nr” and “Var Ref” are renamed in accordance with the list
defined in this screen.

_______________________________________________________________________________________
AA M-SM01-A40028.81/A
10.2 DUPLICATION OF F8000 DATAS

The aim of this function is to duplicate f8000 datas from current project to an identical
project by renaming the Operating Units.
Follows the same procedure as indicate in 10.1

10.3 DUPLICATION OF CENTRALOG FILE

10.3.1 Case of using Controcad

First you have to select the file (<CCAD cell name>.txt) of the current project. Once
the file selected, a screen is displayed :

On the left of the window is represented the architecture of the current project. You
have to rename the cell name of the main controller and IHRs associated. On the
right of the window, appears the list of Operating Units of the current project defined
in the field “Var Ref”. As the same way you have to define the new values of
Operating Units to avoid sending to Centralog identical variables.

To rename O.U.,
double-click on
the line

Controcad then,
Cell names

Input the target


value of O.U.

After clicking on Ok a file named < Main cell name >.txt is created on the same directory as
the origin file.

_______________________________________________________________________________________
AA M-SM01-A40028.82/A
10.3.2 Case of using Microete

In that case the screen is split in two windows. One, to define the cell name of the
new project, and the other to input the new values of Operating Units to replace.

Before clicked on “Duplication” Button, verify that 5 files of current project (See 8)
are on the floppy disk drive A:

11 IMPORT / EXPORT TO CADEPA

11.1 PRINCIPLES

OGIV-8035 constitutes exchange file with CADEPA containing all the variables of
the current project allowing creation or updating of CADEPA data.

From .gig files issued from process programs written with CADEPA, OGIV-8035
append process variables appearing in these programs.

11.1.1 Generation of OGIV_PJ.mne file

_______________________________________________________________________________________
AA M-SM01-A40028.83/A
OGIV-8035 generates OGIV_PJ.mne under the directory of each application
(\CADEPA\ <project name>.prj \ <application name>.apl ). To obtain this file from
OGIV-8035, proceed as follows. Select “Import / Export” “CADEPA”
“Import/Export (.mne file)”. The following screen is displayed:

On the left panel (“Applications”), select the applications which must be exported
(they have to appear on the right panel (“Selected”) after clicking on “append”,
“append all” button or double clicking on an application. Then click on Export to
create OGIV_PJ.mne file(s). CADEPA generates <application name>.mne under
the directory : \CADEPA\ <project name>.prj \ <application name>.app.

.mne files contain the variables of the related applications and they have the
following structure:

From OGIV-8035 From Graphite From CADEPA


01 to 13 Address Address

14 to 40 Mnemonic Mnemonic Mnemonic

41 to 80 Label^state_1 * Title Functional


comment

81 to 120 Technical comment

Note: OGIV-8035 concatenates the attributes label and state_1 and separates them
with "^". When the label has 32 characters and the state_1 message 8 characters,
the last letter of the state_1 message cannot be exported to CADEPA.

The procedure about the utilisation in CADEPA of the .mne file generated by
OGIV-8035 is described in 10.4.

_______________________________________________________________________________________
AA M-SM01-A40028.84/A
11.1.2 Import from CADEPA

The procedure is the same as export (Refer to 9.1.1 Generation of OGIV_PJ.mne


file), except click on “Import “ button instead of “Export”. At the end of import a report
is displayed on the screen, where appear all the variables added and possible errors
encountered during import.

After each Import, it is recommended to proceed to an automatic addressing with


the aim to address new variables.

To address variables, OGIV8035 gives 3 ways:

• Automatic addressing: Select “Variables” “ Automatic addressing”. This function


addresses all process and domain variables without address. The process
variables already addressed are not re-addressed.

• Complete re-addressing: Select “Variables” “Complete re-addressing”. This


function addresses all process and domain variables. The process variables are
re-addressed to optimise address area.

• Partial addressing: Select “Utilities” “Addressing utilities” “Partial addressing”.


This function addresses a group of variables that mnemonic satisfy to a filter
defined by user. (Refer to 11.6.1).This function is only available in administrator
mode.

11.1.3 Other programs generated by OGIV-8035

OGIV-8035 generates .gig files for the customisation of DOMAIN functions or the
update of TS, TM, and network variables... The content of those files is described in
the chapters dealing with the related DOMAIN functions or network.

Additional programs:
• Horn (og_horn.gig) : In AP_OUT, generates rising edges for Horn activation from
variables with attribute Std’s horn =1 (Refer to List of default STD codes).

• Analog inputs (og_anai.gig) : In AP_FST, records the customisation of each


Analog input when PLC mini or maxi is not equal to 0). Refer to 2.2.4.

• Modbus (og_mbus.gig): In AP_FST, records the customisation of Modbus


Exchange Units. This file is also automatically generated after validation of
Modbus Devices Declaration. Refer to 3.2.2 and 3.2.3.

• Dual (og_dual.gig): In AP_FST, records the result of variables (Nr of TVC, TC,
LM…) exchanged between Master and Standby Plc.

Note : Those files have to be imported into CADEPA from the graph editor.

_______________________________________________________________________________________
AA M-SM01-A40028.85/A
12 PROGRAMMING WITH CADEPA

12.1 INTRODUCTION

12.1.1 Programs written with CADEPA

The whole application program of the PLC should be written with CADEPA.

Nonetheless some operations, not available in CADEPA may have to be written


directly with P8. For example: calculations on double-integers and array handling

The program may be written using Sequential Function Charts (SFC) or stand-alone
actions (ie processing performed outside the SFC steps). There may be no SFC at
all. Refer to the syntax description in appendix H-3 to have all the possible
operations.

Do not refrain from using comments: they are not transferred to P8 and therefore
not loaded into the PLC.

Note : the main parts of CADEPA are called as follows:

• CADEPA main menu: PROJECT / APPLICATION MANAGER

• GRAPHITE is launched from the main menu by: "Tools" "Grafcet"

• The GRAPH EDITOR is launched from Graphite by entering into a graph (open
an existing graph or create a new one by clicking on the 1st icon).

• The TABLE EDITOR is launched from Graphite by entering into a table (open an
existing table or create a new one by clicking on the 2nd icon).

_______________________________________________________________________________________
AA M-SM01-A40028.86/A
12.1.2 Interface between CADEPA and OGIV-8035

12.1.2.1 Variables

OGIV-8035 generates OGIV_PJ.mne under the directory of each application


\CADEPA \ <project name>.prj \ <application name>.apl
It contains all the variables of the project.

CADEPA generates <application name>.mne under the directory


\CADEPA\ <project_name>.prj \ <application_name>.app
They contain the variables of the related applications. Those .mne files have the
following structure:

Characters from OGIV-8035 from Graphite From CADEPA


01 to 13 address address

14 to 40 mnemonic Mnemonic mnemonic

41 to 80 label^state_1 * Title Functional


comment

81 to 120 technical comment

* OGIV-8035 concatenates the attributes label and state_1 and separates them with
"^". When the label has 32 characters and the state_1 message 8 characters, the
last letter of the state_1 message cannot be exported to CADEPA.

12.1.2.2 Programs generated by OGIV-8035

OGIV-8035 generates .gig files for the customisation of DOMAIN functions or the
update of TS, TM, and network variables... The content of those files is described in
the chapters dealing with the related DOMAIN functions or network. Those files
have to be imported into CADEPA from the graph editor.

_______________________________________________________________________________________
AA M-SM01-A40028.87/A
12.2 PROCEDURE

CADEPA and OGIV-8035 must be installed on the same logical partition (Ex. C:\)

12.2.1 Configuring CADEPA

Some items of the application "CADEPA" of project "CADEPA" are automatically


copied in the new projects or applications at their creation. They should therefore be
fixed prior to the creation of projects.

Those items are:


- "Author", "Customer" and "Options" of a project,

- The PLC memory mapping (references allocated to CADEPA internal variables)


of an application.

12.2.1.1 Declaration of default attributes for the projects

"File" "Open" (or double click on project window with left button): select
"CADEPA",

"Edit" "Edit the project" (or double click on project window with right button):
the attributes of CADEPA project are displayed:

Then click on "Options":

Maximum length for mnemonics: 27 (maximum possible length)

It is no use configuring a smaller length, as there is no on-line warning in


CADEPA when creating a longer mnemonic. Furthermore some of the
mnemonics assigned to DOMAIN parameters reach the 27 characters.

Maximum length for functional comments: 40 (maximum possible length)

The functional comment is called "Title" in Graphite. It must contain the 32


characters of OGIV-8035 label plus the 8 of the state_1 message.

Maximum length for technical comments: 40

_______________________________________________________________________________________
AA M-SM01-A40028.88/A
The technical comment is currently not used in our standards.

Keyboard locked: yes

Otherwise, import into CADEPA of addressed variables from OGIV-8035 won't


succeed.

Variable name control: no

Otherwise, the mnemonics would be limited to 18 characters.

Default type for variables: external

It does not seem to have any influence

Default type for numerical variables: short (only possible choice)

CADEPA does not know the double-integers.

Disable functional comment modification: no

Disable technical comment modification: no

_______________________________________________________________________________________
AA M-SM01-A40028.89/A
12.2.1.2 Setting of the default PLC memory mapping

To translate its graphs (SFC or stand-alone actions) into P8 language, CADEPA


generates "work" bits and registers and automatically assigns addresses to them.
To do so, some areas of the PLC data memory (not used by OGIV-8035 or
DOMAIN standard programs) must be allocated to CADEPA, and declared in the
"PLC memory mapping".

Those work variables are:


• Steps: each step of the application program generates 1 bit in the PLC

• Transitions: the transition bits are used to process the transitions ready to be
cleared before discriminating the active steps. When the option "multiple coils" is
selected for the translation, those bits can be overwritten after the active step
discrimination. Transition bits are thus equivalent to translator bits.

• Translators: intermediate bits or registers used to process other variables. They


don't have to be stored between 2 controller cycles.

• Timers: 3 registers are generated for each timer.

To declare the default PLC memory mapping, select "CADEPA" application of


"CADEPA" project and check that its attributes PLC manufacturer and PLC type are
respectively "ALSPA-8000", "80 - 35/351" or "80 - 35/363".

Use "PLC" "PLC memory mapping" and proceed as follows:


- Select "Boolean" or "Numerical"

- Enter the Start address (with "%")

- Enter the End address

- Click on "Select" and select the type of variable

- Use PAGE DOWN key or "Edit" "Next" to move to the next area

- When all the 4 areas described below are declared, delete the remaining ones
with Ctrl X or "Edit" "Delete"

_______________________________________________________________________________________
AA M-SM01-A40028.90/A
Here are the 4 areas to declare:

1 - Boolean %G0001 to %G0256 for steps

This area may have to be modified in the applications defined by the user as it
must be different for each application of the same project (when Sequencial
Function Charts are used).

2 - Numerical %R3001 to %R3600 for timers

This area may have to be modified in the applications defined by the user as it
must be different for each application of the same project (when timers are
used).

Its size must be a multiple of 3 as a timer takes 3 words.

3 - Boolean %G0257 to %G1280 for transitions and translators and


Init bit

This area may be common to all the applications of a project. It therefore won't
have to be modified in the applications defined by the user.

4 - Numerical %R3601 to %R4000 for translators

This area may be common to all the applications of a project. It therefore won't
have to be modified in the applications defined by the user.

For the other types of variables, no memory need to be allocated:

• "Init bit" and "Modules" are not used for ALSPA 8000 PLCs.

• "Internals", "On/off and numerical inputs", "On/off and numerical outputs" should
not be automatically addressed by CADEPA. Their addressing is either
automatically performed by OGIV-8035 or manually performed by the user in
OGIV-8035 or CADEPA.

_______________________________________________________________________________________
AA M-SM01-A40028.91/A
12.2.1.3 Page setup for the documentation issued from the main menu

In project "CADEPA", select "File" "Page setup" : the page setup screen is
displayed. It should be filled as shown below. Refer to appendix H-3 to have an
example of documents printed with this page setup.

Margins: 32 / 16 / 19 / 21 are the standard


margins. They allow to print "ALSTOM" header
on top of the sheet.
32

16 Title block: block at the bottom of the sheet


giving the page number, the date and
19 indication about the content (name of the
project, of the application, of the graph). It
21 also contains the attribute "author" in which
the document internal number should have
been entered.

Frame: (to add a frame around the sheet) and


Page footer (fixed text at the bottom of the
sheet) are not necessary.

Click on "Fonts":

Contents: Click on "Contents"


then "Modify" to change from
12 to 10 the Arial size applied
to the sheet of contents.

Title block: Do not increase


the Arial size of the title block
because the size of the block
is not incremented
accordingly!

Semi-graphic : This font is used to print cross-references. Be sure that MS


LineDraw has been installed as indicated 10.1 of document [9].
Do not bother about the other items.

_______________________________________________________________________________________
AA M-SM01-A40028.92/A
12.2.2 Creation of a project

A project is a controller. Therefore one project is automatically created by OGIV-


8035 in CADEPA software for each PLC.

The name of the project must be exactly the same in OGIV-8035 and in
CADEPA. The attributes of the project are:

Author: This item is printed in the title block at the bottom of each page of the
documents generated by CADEPA. It should therefore be used to indicate the
internal number of the programming document, as there are no other way to print
this number on each page.

A comment on 49 characters may be given to the project but it does not appear on
the screen nor on the documents! It may therefore be more convenient to enter a
small comment (on 15 characters) in the attribute customer that is displayed on the
main screen (its first 15 characters only!).

The options of the project are the copy of those of CADEPA project. They don't have
to be modified. Refer to 10.2.1.1 for details about them.

12.2.3 Creation and configuration of applications

The advantages of splitting the application program of a PLC into several


applications are:
• Make sure that some pieces of the processing are performed in a specific
order: the content of a CADEPA application is translated in at least one P8
program block; the user calls the blocks generated by the different applications
in the order of his choice.

• Smaller applications are easier to handle

• Make the program easier to understand

The drawback is that the user must be very careful not to forget to import the new
.mne file produced by OGIV in all the applications (this operation has to be
performed application by application) each time of the address, the label or state_1
message of a variable shared by several applications is modified in OGIV-8035.

_______________________________________________________________________________________
AA M-SM01-A40028.93/A
The size of an application is limited to:

• 4095 graphs + steps

• 4095 Transitions + stand-alone actions

• 4095 variables

At least 3 applications must be included in each project:


• AP_FST (automatically declared by OGIV) where the .gig files generated by
OGIV-8035 to customize the DOMAIN functions must be imported. The user can
also write his own graphs in it. The P8 program block(s) generated by this
application should be called at 1st scan only in "_main" program.

• AP_OUT (automatically declared by OGIV) where the .gig files generated by


OGIV-8035 to update TS, TM ... must be imported. The P8 program block(s)
generated by this application must be the last application blocks called in
"_main" program. The user should not write his own graphs in this application
because the processing of all the variables due to be TS, TM (to MMI or
CENTRALOG) or due to be sent on networks must be written in other
applications to be sure it is performed before the TS/TM... update.

• “PROCESS” application (manually declared by the programmer) where the


user writes his own graphs.

The applications should be configured as defined in the next chapter.

12.2.3.1 Attributes of the applications

The name of the application must be limited to 7 characters because OGIV-8035


doesn't accept more (nor does P8).

The attributes PLC manufacturer and PLC type must be respectively set to "ALSPA-
8000", "80 - 35/351" or "80 - 35/363".

.For comment, refer to the previous paragraph.

The options of the application are the copy of those of the project. They don't have
to be modified. Refer to 10.2.1.1 for details about them.

_______________________________________________________________________________________
AA M-SM01-A40028.94/A
Applications also have attributes in Graphite: title, comment, revision, author,
company but they are independent of those declared in Program Application
Manager and only appear in the documents issued from Graphite. As we issue our
documentation from Program Application Manager., we don't need to fill these
attributes.

12.2.3.2 Page setup of the application in Graphite

The application page setup is copied in the graphs of the application at their
creation. It had therefore better be set prior to the creation of graphs.

The application/graph page setup is independent of the project page setup set in
CADEPA main menu (Program ApplicationManager).

The space available on a page for writing the program depends on the graph
page setup.

When the project page setup allows less margin than the graph page setup,
CADEPA reduces the size of the drawing so that the whole content of a graph
sheet can still be printed on a single page in the documents issued from CADEPA
main menu.

To define the application page setup: select "Tools" "Grafcet" "File" "Page
setup".

To have the largest possible work sheet, enter '0' in all the margins and do not
validate "Page header" nor "Page footer" nor "Title block".

Refer to appendix H-3 to have an example of a graph with that page setup and
printed from CADEPA main menu with the project page setup described in 5.2.1.2.

12.2.3.3 Preferences to display variables in Graphite

It allows defining how to display and print the variables in the program.

Choose “File” “Preferences” and validate “Display title”. It allows to display and
print the title (label^state_1 from OGIV-8035) of each variable after its mnemonic.

_______________________________________________________________________________________
AA M-SM01-A40028.95/A
: Display address may also be validated. It allows to display and print the
address of each variable after its mnemonic or title. But to actually display the
addresses, ogiv_pj.mne must be imported in "PLC" "Symbol table" of
CADEPA main menu as well as in Graphite and ALSPA 8000 console must be
active in Graphite.

12.2.4 Import of all the project variables already declared in OGIV-8035

This operation allows to display the titles of the variables in CADEPA and helps
avoiding spelling mistakes when using the variables in the programs.

To perform the import (from Graphite):


1. "File" "Import"

2. Choose ".mne" files at the bottom of the window

3. Check that the "Options" : Import the existing variables too


: Create the new variables are validated
: Create a new import table allows to display
the imported variables in a table

4. Select OGIV_PJ.mne under


\CADEPA\<project name>.prj\<application Name>.apl\

12.2.5 Edition of programs

In CADEPA, the applications are divided into graphs. Theoretically, the size or
number of pages of a graph is not limited. At the creation of a graph, the following
operations should be performed:

1 - Create the graph by clicking on the 1st icon,

2 - "View" "Page Separator" to visualise on the screen the limit of the pages. The
options "View" "Grid" and "Page Numbers" may also be useful.

3 - "Edit" "Attributes" to give a name to the graph,

4 - Check that the page setup is as described in 10.2.3.2.

_______________________________________________________________________________________
AA M-SM01-A40028.96/A
Here are some advices to set up a graph:
- Validate "Variable" "Display title" in the application preferences (Refer to 5.2.3.3)
to avoid spelling error in the mnemonic (if no title is displayed, the variable is a
new one or its mnemonic is misspelled) and to make the program easier to
understand.

- Write only one variable per line, leave blanks in the operations to make the
program easier to read.

Refer to appendix H-3 to have an example of this setup.

12.2.6 Export to OGIV-8035

This operation will allow ogiv8035 to address all process variables created in CADEPA
application graphs.

To perform the export (from Graphite),

- Delete the unused variables by select "Variable" "Delete unused variables"

- Select "File" "Export", then choose “.mne files ” at the bottom of the window (list
files of type :).

The file \CADEPA\<project_name>.prj\<appli_name>.apl\<appli_name>.mne is


created.

12.2.6.1 Page setup for the documentation issued from the main menu

In project "CADEPA", select "File" "Page setup" : the page setup screen is
displayed. It should be filled as shown below. Refer to appendix H-3 to have an
example of documents printed with this page setup.

Margins: 32/16/19/21 are the standard margins. They allow to print "ALSTOM"
header on top of the sheet.

Title Block: block at the bottom of the sheet giving the page number, the date and
indication about the content (Name of the project, of the application, of the
graph). It also contains the attribute "author" in which the document internal
number should have been entered.

_______________________________________________________________________________________
AA M-SM01-A40028.97/A
Frame (to add a frame around the sheet) and Page footer (fixed text at the
bottom of the sheet) are not necessary.

Click on "Fonts":

Contents Click on "Contents" then "Modify" to change from 12 to 10 the Arial size
applied to the sheet of contents.

Title block Do not increase the Arial size of the title block because the size of
the block is not incremented accordingly!

Semi-graphic his font is used to print cross references. Be sure that MS LineDraw
has been installed as indicated 10.1 of document [9]. Do not bother about the other
items.

_______________________________________________________________________________________
AA M-SM01-A40028.98/A
13 OGIV-8035 UTILITIES

13.1 COHERENCE OF ADDRESSES

To display the list of variables with duplicated mnemonics, duplicated address or


without address. This list is recorded in doublon.txt file, located in the ogiv8035
project directory.

BEFORE EACH :
- EXPORT CADEPA, CENTRALOG, MMI or NETWORKS

AFTER EACH :
- EXPORT CENTRALOG, MMI or NETWORKS
- CONFIGURATION of MODBUS EQUIPMENT
- AUTOMATIC ADDRESSING,
- MODIFICATION of PLC MEMORY MAPPING

RUN THE FUNCTION “COHERENCE OF ADDRESSES”

13.2 PROCESS BITS OR WORDS FREES

To display the list of process addresses frees from the process areas. This list is
stored in limits.txt file, located in the ogiv8035 project directory.

13.3 UPDATING OF WORDINGS FROM OTHER PROJECT

In comparison with mnemonics of an other project, execute the updating of fields:


• Label

• State 1

• Var Ref

To select the issuing project, use the Open File dialog that is displayed after clicking
this option.

_______________________________________________________________________________________
AA M-SM01-A40028.99/A
13.4 DATABASE OPTIMIZATION

To permanently removes all unused variables in the project.

To improve performance of OGIV-8035, in particular after a lot of exchanges with


modifications between OGIV-8035 and CADEPA, use this option.

Note: There is no way to retrieve deleted variables after this option has been run.

13.5 FONT

Change the used font in case of bilingual project (and only in this case).

13.6 TRANSLATE

Only when printing have to be bilinguals. After selection of this option a FoxPro
standard browse window is displayed. Line 1 to 3 appears the variable in the basic
language (read only), the next are reserved to the translation by using an external
text editor. Fields State 1 or unit are translated in CENTRALOG.

Only 3 external text editors are validated by OGIV-8035.


• Wind East or Twin link for Cyrillic characters

• RichWin 97 for Chinese characters

_______________________________________________________________________________________
AA M-SM01-A40028.100/A
13.7 ADDRESSING UTILITIES

13.7.1 Partial addressing

This function addresses a group of variables that mnemonic satisfy to a filter defined
by user. Only the variables that match the condition are displayed. Enter the first
address and validate. The addresses are then incremented by 1 from current
variable to the end of displayed variables (This function is only available in
“Administrator mode”). The mnemonic skeleton can contain the wildcard character
“?”

13.7.2 Reset Ranks

To optimise the reading performance of MMI, CENTRALOG or others PLCs, it is


possible to make contiguous sending areas.

OGIV-8035 gives 4 possibilities in accordance with the sending areas:


- Reset CENTRALOG ranks

- Reset S8000 ranks

- Reset F8000 ranks

- Reset MMI ranks

The using of reset ranks options can damage the variables in the issuer
system. The attributes entered with other tools as CENTRALOG or INTERACT can
be loose.

Use these options while any CENTRALOG, MMI or network attributes has not been
defined.

To prevent the accidents , this function is only available when the


“Administrator mode” is selected.

_______________________________________________________________________________________
AA M-SM01-A40028.101/A
13.7.3 Display file

When clicking on this option the Open file dialog displays all the files with extension
.mne and .txt, located in the current OGIV-8035 project. To display a file, select it
from the scrollable list and choose Open or double-click on the file name with the
mouse or the Spacebar. It is possible to change drive, directory or type of file by
clicking in the related scrollable list.

Press Ctrl W to save the file when it has been modified or Esc to exit without
saving.

13.7.4 Browser database

When clicking on this option the Open file dialog displays all the files with extension
.dbf , located in the current OGIV-8035 project. To display a database, select it from
the scrollable list and choose Open or double-click on the file name with the mouse
or the Spacebar. It is possible to change drive, directory or type of file by clicking in
the related scrollable list.

To prevent the accidents , this function is only available when the


“Administrator mode” is selected.

13.7.5 Loading CADEPA

To load CADEPA from OGIV-8035

_______________________________________________________________________________________
AA M-SM01-A40028.102/A
13.7.6 Saving

13.7.6.1 OGIV-8035

To save on floppy the OGIV-8035 current project. This procedure needs at least 3
diskettes. Click on “Project” “Save on floppy a:” “OGIV-8035”.
It is not necessary to format the diskettes before saving, because OGIV-8035 erase
all files before writing project files.

13.7.6.2 CADEPA

To save on floppy the CADEPA applications related to OGIV-8035 current project.


Click on “Project” “Save on floppy a:” “CADEPA”. The following screen is
displayed:

After choosing the CADEPA applications to save, click on “Save”. The files saved
are :
• <Appl. Name>.cm
• <Appl. Name>.rii
• <Appl. Name>.rid
• option.tra
• cadepa.enc
• liste.cmd
• traducti.cmd
• assemble.cmd
• adr_mne.cmd
• docum.cmd
• prnsvr.cmd

13.7.7 Restoring

The name of the current project selected in OGIV8035 must be the same than the
one on diskettes.

_______________________________________________________________________________________
AA M-SM01-A40028.103/A
13.7.7.1 OGIV-8035

To restore from floppy the project saved by OGIV-8035 saving procedure. Click on
“Project” “Restore” “OGIV-8035”.

13.7.7.2 CADEPA

To restore from floppy the CADEPA applications saved by OGIV8035 saving


procedure. Click on “Project” “Restore” “CADEPA”, then proceed as describe in
11.6.5.2.

_______________________________________________________________________________________
AA M-SM01-A40028.104/A
14 TEST

14.1 INTRODUCTION

To simulate the actions of the electrical or mechanical devices linked to the I/O PLC.

To perform this function the user should create an application where will be write the
simulation program. The aim of this program is to set the inputs in function of the
outputs activated by the application programs.
CADEPA don’t have any instruction to write into discrete references (%I). Therefore
the simulation program will use discrete inputs renamed from li_….. to lø_….. and
addressed in %Q.

After an import from CADEPA, OGIV-8035 automatically addresses (refer to 5.1.2)


all the variables that the beginning of the mnemonic is lø_. Meanwhile the user must
write in P8, before all the application programs, a “move word” instruction to copy
the simulation %Q area into the %I discrete input area.

DISCRETE INPUTS
P8
Move Word

%I %Q
li_input_1 l 0_input_1
li_input_2 l 0_input_2 OGIV8035

li_input_n l 0_input_n

CADEPA
Process
ProcessApplications
Applicatio ns Simul.
Simul.AA
pplication
pplication
DISCRETE OUTPUTS

%Q
lo_output_1
lo_output_2

lo_output_n

The simulation area by default for discrete inputs is localised between %Q1025 and
%Q2048. But if it already uses, it may be change.

_______________________________________________________________________________________
AA M-SM01-A40028.105/A
14.2 PROCEDURE

In CADEPA

1. Create a simulation application in CADEPA.


2. Write the simulation program, using lø_… instead of li_…
3. Generate <Simul. application name>.mne.

In OGIV8035

1. Create the same application in OGIV-8035.


2. Import from CADEPA.
3. Automatic addressing.
4. Export to CADEPA (Generation of OGIV_PJ.mne).

In P8

1. Create the simulation block program.


2. Write the Move Word instruction.

In CADEPA
1. Generate of the simulation application with taking account OGIV_PJ.mne.

In CADEPA/P8
1. Load the program into PLC
2. Test

_______________________________________________________________________________________
AA M-SM01-A40028.106/A
APPENDIX A : GLOSSARY OF TERMS

Application Program : The program written by the user for control of a machine or
process, i.e., the application.

Baseplate : A frame containing the backplane for the system bus, and connectors
into which modules are inserted.

Baud : A unit of data transmission. Baud rate is the number of bits per second
transmitted.

C80-35/CENTRALOG communication environment : Set of standard program


blocks and configuration files to load in a C80-35 PLC and in its S8000
communication module to allow the PLC to exchange messages on S8000 with
CENTRALOG and with the other C80-35 PLCs.

CPU (Central Processing Unit) : The central device or controller that interprets
user instructions, makes decisions, and executes the functions based on a stored
application program.

CPU Baseplate : The baseplate in which the CPU is installed. This baseplate must
always be included in a system and is always assigned rack number "0".

Discrete : The term "discrete" includes both real and internal I/O that are one-bit
user references.

DOMAIN : Set of standard program blocks written P8 software and performing


commonly used functions such as PLC monitoring, analog input convertion,
interface with S8000 communication environment, management of the
communication with MODBUS subscribers ...

Expansion baseplate : A 10-slot baseplate added to a Model 341 or Model 351


when the application calls for more modules than the CPU baseplate can contain. A
Model 341 system can have up to four expansion baseplates ; a Model 351 up to 7
expansion baseplates.

Input module : An I/O module that converts signals from user devices to logic
levels that can be used by the CPU.

I/O module : A printed circuit assembly that interfaces between user devices and
the Alpsa 80-35 PLC.

Module : A replaceable electronic subassembly usually plugged into connectors on


a backplane and secured in place, but easily removed in case of a failure or system
redesign.

O.U. : (Operating Unit) set of number use to differentiate elementary systems (Ex;
01gta, 02gta, 20kkl, …).

_______________________________________________________________________________________
AA M-SM01-A40028.107/A
Output : Data transferred from the CPU, through a module for level conversion, to
be used for controlling an external device or process.

Output module : An I/O module that converts logic level signal within the CPU to
usable output signals a machine or process.

Program block : A unit of an application program that can consist of up to 8K


words of ladder logic and 8K words of local registers.

Programmable Logic Controller (PLC) : A solid-state industrial control device


which receives signals from user supplied control devices such as switches and
sensors, implements them in a precise pattern determined by ladder diagram based
application programs stored in user memory, and provides outputs for control of
processes or user supplied devices such as relays or motors starters. It is usually
programmed in relay ladder logic and is designed to operate in an industrial
environment.

Rack : An Alspa 80-35 baseplate when it has modules installed in it.

Reference type : A specific group of memory type in the ALSPA C80-35 plc, e.g.
%I references discrete inputs and %Q references discrete outputs. The % symbol is
used to distinguish machine references from nicknames.

Register : A group of 16 consecutive bits in register memory, referenced as %R.


Each register is numbered, beginning at 0001. Register memory is used for
temporary storage of numerical values, and for bit manipulation.

TC (Telecommand) : Variable representing a logical command sent to a PLC.

TM (Telemeasure) : Analog variable sent by a PLC.

TS (Telesignal) : Discrete variable sent by a PLC.

TVC (Setpoint command) : Variable representing an analog command sent to a


PLC.

_______________________________________________________________________________________
AA M-SM01-A40028.108/A
APPENDIX B : MNEMONICS OF THE VARIABLES

(RULES TO NAME THE VARIABLES)

1. The maximum size of a mnemonic is 27 characters.

2. To prevent error, the option "keyboard locked" has to be chosen in CADEPA.


"LI_GTA_titi" is thus the same variable as "li_gta_TITI", "li_gta_titi" ...

To standardise the mnemonics and make it easier for OGIV-8035, it has been
chosen to use only lowercase letters as it avoids to change from CAPS LOCK
to normal to type character "_". OGIV-8035 converts all the uppercase letters of
the mnemonics into lowercase letters.

3. The only authorised characters are : a to z, 0 to 9 and _.

4. Each mnemonic must begin with 2 letters + "_"

The first letter is : l for discrete (logical) variables


d for registers (digital variables)

The 2nd letter is :

Type of variables Comment


d Parameters, inputs or outputs To spare the user the manual addressing of
of DOMAIN standard blocks those variables, a mnemonic beginning with
"ld_" or "dd_" has been assigned to each of
them. The mnemonics and related addresses
are stored in OGIV-8035 which can thus
address automatically the DOMAIN variables.

i Wired inputs, variables They must be declared in OGIV-8035 prior to


received from networks. their import from CADEPA to OGIV-8035.
OGIV-8035 won't accept from CADEPA any
unknown variable beginning with "li_" or "di_".

o Wired and MODBUS outputs idem as "i"

0 Test (Simulate variables ) idem as "i"

z System variables same as "d"

For the other variables, ie the variables created in CADEPA and imported
into OGIV-8035 to be addressed, any other 2nd letter may be used. For
example, c for TC to CENTRALOG, k for TC to MMI, v for variables
processed by the application program …
_______________________________________________________________________________________
AA M-SM01-A40028.109/A
5. The var ref attribute of a variable is elaborated from its mnemonic by OGIV-
8035.

As the first 5 characters of var ref must be the operative unit of the variable, the
mnemonic must also contain the operative unit or at least its 3 letters :

operative unit = FFLLL (FF = 2 figure number, LLL = 3 letters)

The 3 letters of the operative unit must appear in the mnemonic.

The 2 figures of the operative unit of a PLC are declared at the creation of the PLC in OGIV-8035.

If the variable belongs to an operative unit with the same 2 figure number, it
needn't be repeated in its mnemonic.

Otherwise, the full operative unit must appear in the mnemonic.

The operative unit or its 3 letters must begin character 4 of the mnemonic.

Examples :

a) Unit PLC : 2 figures of the operative unit = 01


mnemonic : li_gta_yyy → var ref : 01GTA_YYY
mnemonic : di_gex_yyy → var ref : 01GEX_YYY

b) Switchyard PLC: 2 figures of the operative unit = 90


mnemonic : li_lrx_yyy → var ref : 90LRX_YYY
mnemonic : li_91lrl_yyy → var ref : 91LRL_YYY

The maximum number of characters of var ref is 20 but the mnemonic may
have up to 27 characters. (It is no use selecting a smaller number of
characters in CADEPA: in any case during the edition of a graph, the user is
only warned when a mnemonic is longer than 27 characters !).

Once having removed the first 3 characters (li_) and, when needed, added
the 2 figures of the operative unit, if the mnemonic still has more than 20
characters, OGIV-8035 removes the 1st "_", then the 2nd one ... to elaborate
var ref. If it's not enough yet, the last letters of the mnemonic are not copied
in var ref and the user is warned that var ref has been truncated.

_______________________________________________________________________________________
AA M-SM01-A40028.110/A
APPENDIX C : ATTRIBUTES OF THE VARIABLES IN OGIV-8035

Symbols used: E = Entered by the user, P = Processed by OGIV-8035, R = Received.

ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO

Mnemonic 27 char. R E R All the variables = name of the variable in CADEPA

E R l/di_xxx, l/do_xxx are entered in OGIV-8035 by the user, they


cannot be imported from CADEPA to OGIV-8035.

The other variables are imported into OGIV from CADEPA.

Refer to appendix B for its syntax.

Address R P R = address of the variable in the PLC

Label 32 char. R E R R All the variables = label of the variable in OGIV-8035, CADEPA,
CENTRALOG and MMI

State 1 8 char. E R R All the TS / TC = message displayed when the state of the variable is 1.

The valid state 1 / state 0 couples are declared in


CENTRALOG and available in etat_al.dbf file which must
be copied into OGIV each time messages are modified or
added.

____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.111/A
ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO

Unit 8 char. E R R All the TM/TVC = unit of the measurement.

The valid units are declared in CENTRALOG and available in


unit_vm.dbf file. This file must be copied from
CENTRALOG to OGIV-8035 each time units are modified or
added in CENTRALOG.

Acquisition E R All the TM to CENTRALOG = Update rate of the measure in CENTRALOG.


rate
A default value is defined according to the unit in
unit_vm.dbf file.

V mini Real E R R Any register sent to = Min and max physical values of the measurement
V maxi CENTRALOG or CITECT

PLC mini Int E R R - Registers sent to CITECT or = min and max values in the PLC
PLC maxi CENTRALOG
Used by CITECT and CENTRALOG to convert the value
received from the PLC.
Ex : voltage received from MODBUS in V and displayed in
kV in CITECT or CENTRALOG :
PLC mini/maxi = 1000 * V mini/maxi

- Physical value of analog Used by DAI_ALG to convert in the PLC the value in points.
inputs

____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.112/A
ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO

STD 1 to 99 E R** R* All the discrete variables sent STD regroups 7 CENTRALOG attributes:
to MMI or CENTRALOG - URGENCY : 1 to 4 (0 = no alarm)
- DIRECTION : 1 or 0 (=fault state)
- HORN : 1 or 0
- ACK : 1 or 0 (0 means that once acknowledged, the alarm
is not displayed any longer even if it has not
disappeared yet)
- ED.A : 1 or 0 (1=printed at rising edge)
- ED.D : 1 or 0 (1=printed at falling edge)
- REINIT : 1 or 0 (1=printed at start-up)
* OGIV-8035 gives the 7 attributes to CENTRALOG. It
doesn't give STD.

** MMI only needs ALARM (=1 if URGENCY>0)

Centralog C=TC E R Any MAIN PLC logical variable OGIV-8035 assigns them an address and a row.
except li_xxx or lo_xxx
V=TVC Any MAIN PLC analog Idem
variable except di_xxx or
do_xxx
M=TM Any MAIN PLC analog OGIV-8035 assigns them a row and generates the CADEPA
variable program file to arrange them in the TM table and process
their validating bits.
S=TS Any MAIN PLC logical variable Idem
except those received from
%I0001to %I0224 of an IHR
PLC

____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.113/A
ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO

Var ref 20 char. R P or E R R All the variables exchanged = name of the variable in CENTRALOG and MMI.
with CENTRALOG
It is elaborated automatically by OGIV-8035 according to the
mnemonic of the variable as soon as the Centralog flag is set
to S or M or by pressing ALT R.
It can be modified by the user.
Refer to appendix B to know how Var ref is elaborated from
the mnemonic.

Location P « li_ », « di_ », « lo_ », « do_ Updated by OGIV-8035 according to the PLC configuration.
»
Rack 0 to 4 Wired I/O variables = Rack of the I/O module in PLC.
Slot 1 to 10 Idem = Slot of the I/O module in Rack.
Point 1 to 32 Idem = Rank of the I/O on the module.

Plc 0 to 5 Variables received from F8000 = Number of the sending PLC on F8000
Address Idem = Address in the sending PLC.

Device 5 char. Modbus I/O variables = Name of the sending/receiving device.


Point = Rank in the interface table

To F8000 S = TS E Any discrete variable Means that the variable has to be copied into the bit or word
table broadcast on F8000.

____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.114/A
ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO

M= TM Any register OGIV-8035 generates the CADEPA program file to arrange


those variables in the message broadcast on F8000.

MMI C=TC E Any discrete variable except OGIV-8035 assigns them an address and in the area
li_xxx or lo_xxx dedicated to TC MMI.

V=TVC Any register except di_xxx or Idem


do_xxx

S=TS Any discrete variable OGIV-8035 generates the CADEPA program file to copy
them in the area dedicated to TS MMI.
M=TM Any register Idem

____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.115/A
APPENDIX D : LIST OF STD CODES

This is the standard list provided by OGIV-8035. It can be customised on each


project in std_vl.dbf file.

For internal processing, the additional "ALARM" column must be set to 0 when
URGENCY = 0 and to 1 otherwise.

STD URGENC DIRECTIO HORN ACK ED-A ED-D REINIT ALAR


Y N M
1 0 - - - 0 0 0 0

2 0 - - - 1 1 0 0

3 0 - - - 1 0 0 0

4 0 - - - 0 1 0 0

5 0 - - - 1 0 1 0

11 1
21 2
31 3 1 1 1 1 1 0 1
41 4

12 1
22 2
32 3 0 1 1 1 1 0 1
42 4

13 1
23 2
33 3 1 0 1 1 1 0 1
43 4

14 1
24 2
34 3 0 0 1 1 1 0 1
44 4

_______________________________________________________________________________________
AA M-SM01-A40028.116/A
APPENDIX E : IMPLEMENTATION OF DOMAIN FUNCTIONS

DOMAIN-8035 is a set of programs written with P8 programming software in


LADDER language and carrying out system functions.

To use DOMAIN functions:

- The DOMAIN program blocks must be called from the PLC "_main" program
(written with P8),

- When a customisation is needed, the chosen values must be written at first scan in
the parameters,

- The input references of the DOMAIN program blocks must be updated and their
output references read at each scan.

For the user of CADEPA and OGIV-8035, the DOMAIN parameters and I/O
references are of 3 types:

- Type 1 references, for example analog inputs (outputs from DAI_ALG), MODBUS
I/O (from DMB_EVA ...) ..., are automatically generated by OGIV-8035
according to the PLC and MODBUS configuration. No specific mnemonics are
assigned to them: the user assigns mnemonics according to his choice.

- Type 2 references have been assigned specific mnemonics (beginning with


"ld_" or ”dd_”). The user does not have to bother about their addresses: he uses
the pre-set mnemonics in his CADEPA applications; OGIV-8035 will assign the
proper addresses to them.

For some of them, such as parameters, TS, TM to CENTRALOG..., OGIV-8035


automatically writes the instructions to update them in .gig files.

- Type 3 references are useful only for test purpose. They are not known by OGIV-
8035 as they are not needed by the application program..

DOMAIN functions can also be used in PLCs which are not implemented with
CADEPA and OGIV-8035. The interface with the application program is then
performed by using the references of the parameters and inputs/outputs.

This appendix explains how to use the DOMAIN functions from CADEPA programs
and with OGIV-8035.

_______________________________________________________________________________________
AA M-SM01-A40028.117/A
It is set out as technical leaflets, one per DOMAIN program block, describing:

- the processing performed by each block,

- its parameters (variables to customise at first scan), inputs (variables to update


before each call), outputs (variables updated by the block).

For each of them, a description, a range of values, default value and reference
address in the PLC is given.

For type 1 references, as their mnemonics are chosen by the user, only their 3
pulsory 1st characters are indicated.

For type 2 references, the assigned mnemonics are given. When OGIV-8035
automatically writes their update instructions the related .gig file is indicated.

Type 3 references don't have any mnemonics.

When a parameter has a default value, the application program needn’t customise it,
except if the default value does not fit.

_______________________________________________________________________________________
AA M-SM01-A40028.118/A
Validation and conversion of ALG222/223 analog inputs DAI_ALG

PROCESSING:

- Deals with up to 128 analog inputs from ALG222 or ALG223 modules.

- Periodically reads each input, checks its validity and converts it into physical value.

- In order not to load the PLC too much, all the inputs are not scanned at each cycle, the
number of inputs scanned per cycle has to be customised by the user (dd_alg_per_cyc).

- DAI_ALG converts %AI0xxx into physical value according to:


 its MIN / MAX physical values (dd_ana_inp_min_0xxx / dd_ana_inp_max_0xxx)
 the minimum and maximum raw values common to all the inputs processed by
DAI_ALG (dd_alg_raw_min/max).
The conversion is performed if: MAX - MIN > 0.

- The validity bit of an analog input:


=1 when its module is OK and its raw value higher than the minimum valid raw value
(dd_alg_raw_limit).
=0 otherwise.

- When a module is missing or NOK, the raw and physical values of all its channels are set
to - 32768.

- When the raw value is higher than the minimum valid raw value, it is still converted into
physical units.

PARAMETERS:

dd_alg_raw_min (2) Minimum raw value of all the inputs processed %R0101
by DAI_ALG.
Example: 0 or 6400 or -32000.

dd_alg_raw_max (2) Maximum raw value of all the inputs processed %R0103
by DAI_ALG.
Example: 32000.

dd_alg_raw_limit (2) Raw value under which the input is declared invalid. %R0105
(2)
dd_alg_per_cyc Number of inputs to scan per cycle. %R0106
(Execution time of DAI_ALG ~ dd_alg_per_cyc / 2 ms)

_______________________________________________________________________________________
AA M-SM01-A40028.119/A
Validation and conversion of ALG222/223 analog inputs DAI_ALG

PARAMETERS (FOLLOWING):

(2)
dd_alg_mask_mdl_000n 1 ≤ n ≤ 8. Mask for inputs processed by DAI_ALG. %R0107-114
Bit i of dd_alg_mask_mdl_00n = 1 if channel i of
module n, %AI[16(n-1) + i], exists and has a raw value
between dd_alg_raw_min and dd_alg_raw_max.

Value of bit i: i= 1 → 1 i= 9 → 256


2 → 2 10 → 512
3 → 4 11 → 1024
4 → 8 12 → 2048
5 → 16 13 → 4096
6 → 32 14 → 8192
7 → 64 15 → 16384
8 → 128 16 → -32768

dd_ana_inp_min_0xxx (1) Minimum physical value of input %AI0xxx, %AI( 0129 +


i.e. physical value for dd_alg_raw_min points. 8(xxx-1) )
1≤ xxx ≤ 128.

dd_ana_inp_max_0xxx (1) Maximum physical value for input %AI0xxx %AI( 0130 +
i.e. physical value for dd_alg_raw_max points. 8(xxx-1) )
1≤ xxx ≤ 128

(1)
updated by OGIV-8035 in og_anai.gig file to import in CADEPA, application AP_FST.
(2)
must be updated by the user in cnf_alg.gig file to import in CADEPA, application AP_FST.

INPUTS: none

OUTPUTS:

di_... Raw value of channel %AI0xxx. %AI( 0135 +


(= copy of %AI0xxx). 8(xxx-1) )

di_... Physical value of channel %AI0xxx %AI( 0136 +


8(xxx-1) )

li_... Validity bit of channel %AI0xxx %I( 1649


+ (xxx-1) )

The validity bit, physical value and copy of raw value of an input are updated at the same time every:

total number of inputs processed by DAI_ALG


——————————————————— x 100 ms
dd_alg_per_cyc

_______________________________________________________________________________________
AA M-SM01-A40028.120/A
Validation and conversion of ALG222/223 analog inputs DAI_ALG

RULES FOR IMPLEMENTATION:

1 - CONFIGURATION OF THE ALG222 / 223 MODULES WITH P8:

"Active Chan": 1 to 16 "Ref Adr": %AI (16(n-1)+1) "Ref Adr": %I (1777+8(n-1))


1≤n≤8 "%I size": 8

"Channel i": as needed "Alarm Low": not useful "Alarm High": not useful
(4-20 mA, 0-10V ...)

2 - The minimum and maximum raw values must be the same for all the inputs processed
by DAI_ALG (dd_alg_raw_min / dd_alg_raw_max).

If all the ALG222/223 analog inputs of the PLC don't have the same minimum or
maximum raw values, several DAI_ALX blocks must be used, one for each raw_min /
raw_max couple.

Presently, 3 different couples may be used (for example: 0 / 32000, 6400 / 32000,
-32000 / 32000) as 3 blocks are available: DAI_ALG, DAI_AL2 and DAI_AL3.

EXAMPLE:

There are 2 ALG222 modules in the PLC.


Their configuration in P8 must be: Module 1: %AI0001 / %I1777
Module 2: %AI0017 / %I1785.

If: - %AI0001 / 2 / 9 / 16 / 17 to 32 are between 0 and 32000 points,


- %AI0003 / 4 between -32000 and 32000 points,
- all the other channels are spare,

Then: dd_alg_raw_min = 0, dd_alg_raw_max = 32000,


dd_alg_mask_mdl_0001 = - 32509 ( = 1 + 2 + 256 - 32768)
dd_alg_mask_mdl_0002 = - 1 ( = 1 + 2 + ... + 16384 - 32768)

And: DAI_AL2 must be called for %AI3 and %AI4 with:


dd_al2_raw_min = -32000, dd_al2_raw_max = 32000
dd_al2_mask_mdl_0001 = 4 + 8 = 12.

The variables to use in the application program are:


For channel %AI0002: - %AI0143 to work on the value in points,
- %AI0144 to use the converted value,
- its validity bit is %I1650,

For channel %AI0003: - %AI0151 to work on the value in points,


- %AI0152 to use the converted value,
- its validity bit is %I1651

_______________________________________________________________________________________
AA M-SM01-A40028.121/A
Validation and conversion of ALG222/223 analog inputs DAI_AL2

PROCESSING:

- DAI_AL2 should be used in addition to DAI_ALG when all the ALG222/223 analog inputs
of the PLC do not have the same minimum or maximum raw value.

- The maximum number of inputs processed by DAI_ALG + DAI_AL2 + DAI_AL3 is 128.

PARAMETERS:

(2)
dd_al2_raw_min Minimum raw value of all the inputs processed %R0131
by DAI_AL2. Example: 0 or 6400 or -32000.
(2)
dd_al2_raw_max Maximum raw value of all the inputs processed. %R0133
by DAI_AL2. Example: 32000.

dd_al2_raw_limit (2) Raw value under which the input is declared invalid. %R0135
(2)
dd_al2_per_cyc Number of inputs to scan per cycle. %R0136
(Execution time of DAI_AL2 < dd_al2_per_cyc / 2 ms)
(2)
dd_al2_mask_mdl_000n 1 ≤ n ≤ 8. Mask for inputs processed by DAI_AL2. %R0137-144
Bit i of dd_al2_mask_mdl_000n = 1 if channel i of
module n, %AI[16(n-1) + i], exists and has a raw value
between dd_al2_raw_min and dd_al2_raw_max.
(1)
dd_ana_inp_min_0xxx Minimum physical value of input %AI0xxx, %AI( 0129 +
i.e. physical value for dd_al2_raw_min points. 8(xxx-1) )
1≤ xxx ≤ 128.

dd_ana_inp_max_0xxx (1) Maximum physical value for input %AI0xxx %AI( 0130 +
i.e. physical value for dd_al2_raw_max points. 8(xxx-1) )
1≤ xxx ≤ 128.

(1)
updated by OGIV-8035 in og_anai.gig file to import in CADEPA, application AP_FST.
(2)
must be updated by the user in cnf_al2.gig file to import in CADEPA, application AP_FST.

OUTPUTS: same as DAI_ALG

RULES FOR IMPLEMENTATION: Refer to DAI_ALG.

_______________________________________________________________________________________
AA M-SM01-A40028.122/A
Validation and conversion of ALG222/223 analog inputs DAI_AL3

PROCESSING:

- DAI_AL3 should be used in addition to DAI_ALG when all the ALG222/223 analog inputs
of the PLC do not have the same minimum or maximum raw value.

- The maximum number of inputs processed by DAI_ALG + DAI_AL2 + DAI_AL3 is 128.

PARAMETERS:

(2)
dd_al3_raw_min Minimum raw value of all the inputs processed %R0151
by DAI_AL3. Example: 0 or 6400 or -32000.
(2)
dd_al3_raw_max Maximum raw value of all the inputs processed. %R0153
by DAI_AL3. Example: 32000.

dd_al3_raw_limit (2) Raw value under which the input is declared invalid. %R0155
(2)
dd_al3_per_cyc Number of inputs to scan per cycle. %R0156
(Execution time of DAI_AL3 < dd_al3_per_cyc / 2 ms)
(2)
dd_al3_mask_mdl_000n 1 ≤ n ≤ 8. Mask for inputs processed by DAI_AL3. %R0157-164
Bit i of dd_al3_mask_mdl_000n = 1 if channel i of
module n, %AI[16(n-1) + i], exists and has a raw value
between dd_al3_raw_min and dd_al3_raw_max.
(1)
dd_ana_inp_min_0xxx Minimum physical value of input %AI0xxx, %AI( 0129 +
i.e. physical value for dd_al3_raw_min points. 8(xxx-1) )
1≤ xxx ≤ 128.

dd_ana_inp_max_0xxx (1) Maximum physical value for input %AI0xxx %AI( 0130 +
i.e. physical value for dd_al3_raw_max points. 8(xxx-1) )
1≤ xxx ≤ 128.

(1)
updated by OGIV-8035 in og_anai.gig file to import in CADEPA, application AP_FST.
(2)
must be updated by the user in cnf_al3.gig file to import in CADEPA, application AP_FST.

OUTPUTS: same as DAI_ALG

RULES FOR IMPLEMENTATION: Refer to DAI_ALG.

_______________________________________________________________________________________
AA M-SM01-A40028.123/A
Validation of RTD inputs DAI_RTD

PROCESSING:

- Deals with up to 7 RTD66x modules which input references are:


%AI0001-6, %AI0017-22, %AI0033-38, %AI0049-54, %AI0065-70, %AI0081-86,
%AI0097-102.

- DAI_RTD updates a validity bit for each RTD channel


=1 when its module is OK and the RTD channel neither open nor over the maximum
readable temperature.
=0 otherwise.

- DAI_RTD copies the 6 channels into 6 other %AI to be consistent with DAI_ALx modules.

PARAMETERS:

dd_rtd_rack_aixx xx = 01 , 17 , 33 , 49 , 65 , 81 or 97. %R( 171 +


Rack number (1 to 8) of RTD module %AI00xx. 2(i-1) ) *

dd_rtd_slot_aixx xx = 01 , 17 , 33 , 49 , 65 , 81 or 97. %R( 172 +


Slot number (1 to 10) of RTD module %AI00xx. 2(i-1) ) *

* i = 1 for xx = 01, 2 for xx = 17, 3 for xx = 33, 4 for xx = 49, 5 for xx = 65, 6 for xx = 81, 7 for xx = 97.

OUTPUTS:

di_... Copy of %AI0xxx. %AI( 0135 + 8(xxx-1) )

li_... Validity bit of channel %AI0xxx %I( 1648 + (xxx-1) )

RULES FOR IMPLEMENTATION:

- The 16 discrete references of RTD module %AI(16n+1) must be %I(1649+16n) to


%I(1664+16n), 0 ≤ n ≤ 6.

- The processing of the 7 possible RTD66x modules is implemented in DAI_RTD. THE


USER MUST ZOOM INSIDE DAI_RTD AND DELETE THE RUNGS RELATED TO NON
EXISTING MODULES (there are 1 "COMMENT" + 4 rungs per module).

_______________________________________________________________________________________
AA M-SM01-A40028.124/A
Duality updating control DDU_CTR

PROCESSING:

- Makes the elaboration of "insertion mode".

- Supervises with controls the exchanges between dual controller.

- Elaborates cheksum for analizing

PARAMETERS: none

INPUTS:

dd_dual_st_stus Stable status word %R0193

dd_dual_rq_stus Requested status word %R0194

dd_dual_sq_stus Sequence status word %R0195

ld_inst_stus Instable applicative status %M0747

ld_dual_stop_req Application stop requested %M0746

ld_dual_ins_req Application insertion mode requested %M0754

OUTPUTS:

ld_dual_update_flt Exchanges lost %M0742

RULES FOR IMPLEMENTATION:

Must be used with macro DDU_SND & DDU_RCV.

Position in software: - just before application and before DDU_SND & DDU_RCV

_______________________________________________________________________________________
AA M-SM01-A40028.125/A
Duality updating sending DDU_SND

PROCESSING:

- Makes the updating by sending data between primary controller and secondary controller
of redundant main controller.

PARAMETERS: none

INPUTS:

ld_mod_local Application local control mode %M0737

ld_mod_remote Application remote control mode %M0738

OUTPUTS: none

RULES FOR IMPLEMENTATION:

Must be used with macro DDU_CTR & DDU_RCV.

Position in software: - just before application and between DDU_CTR &


DDU_RCV

_______________________________________________________________________________________
AA M-SM01-A40028.126/A
Duality updating receiving DDU_RCV

PROCESSING:

- Makes the updating by receiving data between primary controller and secondary controller
of redundant main controller.

PARAMETERS: none

INPUTS:

ld_mod_local Application local control mode %M0737

ld_mod_remote Application remote control mode %M0738

OUTPUTS: none

RULES FOR IMPLEMENTATION:

Must be used with macro DDU_CTR & DDU_SND.

Position in software: - just before application and after DDU_CTR & DDU_SND

_______________________________________________________________________________________
AA M-SM01-A40028.127/A
Processing of application variables received from F8000 DF8_IN

PROCESSING

- Copies in %I area the discrete variable received from F8000 in %AI words.

- Demultiplex the analog variables received from F8000

- The variables exchanged between the 2 dual PLC are not processed by DF8_IN but by
DDU_xxx blocks.

PARAMETERS:

dd_f8000_1st_iword_ihr1 (1) First %I word where are copied the discrete variables R0041
received from IHR 1 in %AI.
1st Address – 1
= ———————— + 1
16

( = 1 for %I0001, 2 for %I0017, 3 for %I0033 ... )

dd_f8000_nbr_iword_ihr1 (1) Number of words of 16 bits received from IHR 1 %R0042


(1)
dd_f8000_1st_iword_ihr2 First %I word to copy bits from IHR 2 %R0043

dd_f8000_nbr_iword_ihr2 (1) Number of words of 16 bits received from IHR 2 %R0044


(1)
dd_f8000_1st_iword_subi First %I word where are copied the bits %R(0045
received from SUB i in %AI (1 ≤ i ≤ 3) + 2(i-1) )

dd_f8000_nbr_iword_subi (1) Number of words of 16 bits received from SUBi %R(0045


+ 2(i-1) )

(1)
Updated by OGIV-8035 in og_f8i.gig according to "Networks F8000 Exchange areas
definition". og_f8i.gig must be imported into CADEPA, application AF_FST.

_______________________________________________________________________________________
AA M-SM01-A40028.128/A
Processing of application variables received from F8000 DF8_IN

INPUTS:

IHR1 is running and on F8000 %I1905


IHR2is running and on F8000 %I1889
SUB1 is running and on F8000 %I1873
SUB2 is running and on F8000 %I1857
SUB3 is running and on F8000 %I1841
256 bits from IHR1 %AI1153-1168
256 bits from IHR2 %AI1185-1200
256 bits from SUB1 %AI1217-1248
256 bits from SUB2 %AI1249-1280
256 bits from SUB3 %AI1281-1312
1 service word + 61 multiplexed words from SUB1 %AI1377-1438
1 service word + 61 multiplexed words from SUB2 %AI1441-1502
(only 47 multiplexed words if the cell has 3 SUBs)
1 service word + 47 multiplexed words from SUB3 %AI1489-1536

OUTPUTS:

li_… 16*dd_f8000_nbr_iword_ihri bits received from IHRi, %I


and available for application program

li_… 16*dd_f8000_nbr_iword_subi bits received from SUBi, %I


and available for application program

di_… Up to 244 analog variables received from SUB1, %AI1793-2036


demultiplexed and available for application program

di_… Up to 244 (188 only if the cell has 3 SUBs) analog %AI2049-2292
variables received from SUB2, demultiplexed
and available for application program

di_… Up to 188 analog variables received from SUB3, %AI2321-2508


demultiplexed and available for application program

RULES FOR IMPLEMENTATION:

DF8_IN must be used in MAIN controllers only

_______________________________________________________________________________________
AA M-SM01-A40028.129/A
Processing of application variables received from F8000 DF8_I_S

PROCESSING

- Copies in %I area the discrete variable received from F8000 in %AI words.

- Demultiplex the analog variables received from MAIN PLC

PARAMETERS:

(1)
dd_f8000_1st_iword_ihr1 First %I word where are copied the discrete variables R0041
received from IHR 1 in %AI.
1st Address – 1
= ———————— + 1
16

( = 1 for %I0001, 2 for %I0017, 3 for %I0033 ... )

dd_f8000_nbr_iword_ihr1 (1) Number of words of 16 bits received from IHR 1 %R0042


(1)
dd_f8000_1st_iword_ihr2 First %I word to copy bits from IHR 2 %R0043

dd_f8000_nbr_iword_ihr2 (1) Number of words of 16 bits received from IHR 2 %R0044


(1)
dd_f8000_1st_iword_subi First %I word where are copied the bits %R(0045
received from SUB i in %AI (1 ≤ i ≤ 3) + 2(i-1) )

dd_f8000_nbr_iword_subi (1) Number of words of 16 bits received from SUBi %R(0045


+ 2(i-1) )

(1)
Updated by OGIV-8035 in og_f8i.gig according to "Networks F8000 Exchange areas
definition". og_f8i.gig must be imported into CADEPA, application AF_FST.

_______________________________________________________________________________________
AA M-SM01-A40028.130/A
Processing of application variables received from F8000 DF8_I_S

INPUTS:

MAIN is running and on F8000 %I1921


IHR1 is running and on F8000 %I1905
IHR2is running and on F8000 %I1889
SUB1 is running and on F8000 %I1873
SUB2 is running and on F8000 %I1857
SUB3 is running and on F8000 %I1841
256 bits from IHR1 %AI1153-1168
256 bits from IHR2 %AI1185-1200
128 bits from SUB1 %AI1217-1224
128 bits from SUB2 %AI1249-1256
128 bits from SUB3 %AI1281-1288
512 bits from MAIN %AI1393-1424
1 service word + 61 multiplexed words from MAIN %AI1313-1374

OUTPUTS:

li_… Up to 512 bits received from MAIN, %Q0001-0512

li_… 16*dd_f8000_nbr_iword_ihri bits received from IHRi, %I


and available for application program

li_… 16*dd_f8000_nbr_iword_subi bits received from SUBi, %I


and available for application program

di_… Up to 244 analog variables received from MAIN, %AI1793-2036


demultiplexed and available for application program

RULES FOR IMPLEMENTATION:

DF8_I_S must be used in SUB controllers only

_______________________________________________________________________________________
AA M-SM01-A40028.131/A
Multiplexing and update of the areas to send on F8000 DF8_OUT

PROCESSING:

- Copies the bits to send on F8000 into the F8000 network variables.

- Multiplex up to 244 analog variables into the F8000 “application words” network variables.

PARAMETERS:

B_MAIN (1) = 0 in SUB, = 1 in MAIN %M0811


(2)
dd_f8000_size_of_mlplx_blk Size of the analog variable multiplexed blocks %R0034
61 in MAIN and SUB1
61 in SUB2 if there is no SUB3
47 in SUB2 and SUB3 if it exists

dd_f8000_nbr_of_mlplx_blk (2) Number of blocks of analog variables to send %R0035


on F8000. ≤ 4.

dd_f8000_mlpx_period Time between 2 updates of the multiplexed %R0037


network variable.
Default value : 26 = 260 ms.

IN SUB PLC ONLY

(2)
dd_f8000_1st_iword_to_send Rank of the 1st %I word to send to MAIN %R0031

dd_f8000_nbr_iword_to_send (2)(3) Number of 16-%I words to send to MAIN %R0032


(2)(3)
dd_f8000_nbr_qword_to_send Number of 16 process bits to MAIN %R0033

(1)
Set to 1 in _main program of STD_S8E and STD_S8F
(2)
Updated by OGIV-8035 in og_f8i.gig file to import in CADEPA, application AP_FST.
(3)
dd_f8000_nbr_iword_to_send + dd_f8000_nbr_qword_to_send must be ≤ 32

_______________________________________________________________________________________
AA M-SM01-A40028.132/A
Multiplexing and update of the areas to send on F8000 DF8_OUT

INPUTS:

IN MAIN PLC ONLY:


(5)
dd_f8000_s_xxxx Up to 244 analog variables to broadcast to SUBs %AI1537-1780

ld_f8000_s_xxxx (4) Up to 512 bits to broadcast to SUBs %Q0001-512

IN SUB PLC ONLY:


(5)
dd_f8000_to_main_xxxx Up to 244 analog variables to send to MAIN %AI1537-1780

li_… 16*dd_f8000_nbr_iword_to_send discrete inputs %I


to send to MAIN
(4)
ld_f8000_to_main_xxxx 16*dd_f8000_nbr_qword_to_send process bits %Q1025-1280
to send to MAIN
(4)
ld_f8000_to_sub_xxxx Up to 128 bits to broadcast to the other SUBs %Q1281-1408

(4)
Processed by OGIV-8035 in og_f8lo.gig file to import in CADEPA, application AP_OUT.
(5)
Processed by OGIV-8035 in og_f8do.gig file to import in CADEPA, application AP_OUT.

OUTPUTS:

512 bits sent from SUB to MAIN %AQ417-448


or broadcast from MAIN to SUBs

Service word for the multiplexed message %AQ449

61 multiplexed words to send %AQ450-510

IN SUB PLC ONLY:


128 bits broadcast to the other SUBs %AQ401-416

RULES FOR IMPLEMENTATION:

DF8_OUT must be used in MAIN and SUB controllers

_______________________________________________________________________________________
AA M-SM01-A40028.133/A
Communication with a CHESSELL temperature acquisition unit DMB_CHS

PROCESSING:

- Reads up to 96 measurements in CHESSELL (channels 1 to 96) and converts them from


0 – FFFF to physical values according to the MIN / MAX physical values entered by the
user.

- Reads up to 3 alarms per measurements (alarm 1 to 3).

- The alarms are reset and the measurements set to -32768 (8000H) when the
communication with CHESSELL is lost.

PARAMETERS:

dd_mbus_ue_ches (1) Number of the related Modbus Exchange Unit %R1624


1 to 4.

dd_mbus_subs_nb_ches (1) Subscriber number on Modbus network %R1631


1 to 31.
(1)
dd_mbus_period_ches Reading period for the measurements %R1625
0 (default value) = as soon as possible
X: period = X*500 ms
(1)
dd_mbus_nb_of_words_ches Number of analog inputs to read in CHESSELL %R1620
1 to 96.
(1)
dd_mbus_nb_of_alarm_ches Number of alarms per analog input %R2601
1 to 3.

dd_mbus_adr_ala1_ches (1) Address of alarm 1 in CHESSELL %R1604


Typically 250

dd_mbus_adr_ala2_ches (1) Address of alarm 2 in CHESSELL %R1589


Typically 500 or 1250
(1)
dd_mbus_adr_ala3_ches Address of alarm 3 in CHESSELL %R1574

dd_mbus_ches_inp_min_xxx (1) Minimum physical value of channel xxx %R( 2701


+ 2(xxx-1) )

dd_mbus_ches_inp_max_xxx (1) Maximum physical value of channel xxx %R( 2702


+ 2(xxx-1) )

(1)
Updated by OGIV-8035 in og_mbus.gig to import into CADEPA, application AF_FST.

INPUTS: none.

_______________________________________________________________________________________
AA M-SM01-A40028.134/A
Communication with a CHESSELL temperature acquisition unit DMB_CHS
INPUTS / OUTPUTS:

For test purpose: to start the question reading the words, %R0744
enter 32. To start the question reading alarm i, enter 32 - i.
It is then reset automatically.

For test purpose: to stop the question reading the words, %R0745
enter 32. To stop the question reading alarm i, enter 32 - i.
It is then reset automatically.

OUTPUTS:

li_... CHESSELL communicates properly on MODBUS %M0864

di_... Channels 1 to 96 in physical units %R2605 to %R2700

li_... Alarm 1 of channels 1 to 96 %M3489 to %M3584

li_... Alarm 2 of channels 1 to 96 %M3393 to %M3488

li_... Alarm 3 of channels 1 to 96 %M3297 to %M3393

Counters of OK / NOK answers to measurements reading %R1627-8


Last NOK report to measurements reading %R1630
Counter of answer without error code to meas. reading %R1632

Idem for alarm 1 reading %R1612-3, %R1615

Idem for alarm 2 reading %R1597-8, %R1600

Idem for alarm 3 reading %R1582-3, %R1585

RULES FOR IMPLEMENTATION:

- DMB_CHS must be used with DMB_UE and DMB_PER and called after DMB_PER and
before the application program.

- CHESSELL is slave 32 ie its equipment number in OGIV-8035 must be 32. Slaves 29 to


31 are used to read alarms 1 to 3 in CHESSELL therefore equipment numbers 29 to 31
can not be allocated to any slave device in OGIV-8035.

- If CHESSELL is on MODBUS Exchange Unit 1, up to 96 measurements may be read. If


its on E.U. 3 or 4, only 36 measurements may be read. On E.U.2, 96 measurements may
be read if there is no E.U.3 or 4, 90 only if there are 3 exchange units, 52 if there are 4
exchange units.

_______________________________________________________________________________________
AA M-SM01-A40028.135/A
Communication with PECA or EVA devices DMB_EVA

PROCESSING: handles up to 32 PECA or EVA electrical measurements acquisition units.

- Periodically reads the electrical values measured by PECA or EVA units (from V1 address
0 to ErIN address 34) and converts them into integers except the energies which remain
in double-integers.

- Monitors all the PECA/EVA units and writes -32768 (8000H) in all the measurements
(except energies) of the PECA/EVA which don't communicate.

PARAMETERS:

(2)
dd_mbus_mask_eva_1 Mask for existing PECA/EVA %R1639
dd_mbus_mask_eva_2 (2) Bit j, 1 ≤ j ≤ 32, = 1 if slave j is a PECA or EVA device %R1640
(1) (2)
dd_mbus_eu_eva_j Number of the related Modbus Exchange Unit %R( 1159
1 to 4. + 15 * (j-1) )

dd_mbus_subs_nb_eva_j (1) (2) Subscriber number on Modbus network %R( 1166


1 to 31. + 15 * (j-1) )

dd_mbus_period_eva_j (1) (2) Reading period for the measurements %R( 1160
0 (default value) = as soon as possible + 15 * (j-1) )
X: period = X*500 ms

dd_mbus_coef_u_eva_j (1) (2) Integer coefficient for the voltages %R( 1641
1 or 0 (default value) = voltages in volts + 30 * (j-1) )
X = voltages in X volts

dd_mbus_coef_i_eva_j (1) (2) Integer coefficient for the currents %R( 1643
1 or 0 (default value) = currents in amps + 30 * (j-1) )
X = currents in X amps

dd_mbus_coef_p_eva_j (1) (2) Double integer coefficient for the powers %R( 1645
1 or 0 (default value) = powers in W, Var + 30 * (j-1) )
X = powers in X W, Var

dd_mbus_addr_read_eva_j (1) (2) Address in the PECA or EVA device of the 1st word %R( 1154
to read (0 to 34) + 15 * (j-1) )
(1) (2)
dd_mbus_nb_words_eva_j Number of words to read in PECA/EVA %R( 1155
30 (default value) = 3U, 3I, P, Q, S, cos, Hz, 4E + 15 * (j-1) )
2X, X<15 = X measurements from address 6

(1)
j = (01 ≤ j ≤ 32) number of the PECA/EVA device. It is used for internal processing and
must be unique for the PLC: 2 PECA/EVA can't have the same number even if they are
connected to different channels or PCMs.
(2)
Updated by OGIV-8035 in og_mbus.gig to import into CADEPA, application AF_FST.

_______________________________________________________________________________________
AA M-SM01-A40028.136/A
Communication with PECA or EVA devices DMB_EVA

INPUTS: none.

INPUTS / OUTPUTS:

For test purpose only: to start the periodic or cyclic %R0744


question sent to a PECA/ EVA, enter the PECA/EVA
number in this word which is then reset automatically

For test purpose only: to stop the periodic or cyclic %R0745


question sent to a PECA/ EVA, enter the PECA/EVA
number in this word which is then reset automatically

OUTPUTS:

di_... Measurements from PECA/EVA number j: %R( 1650 to 1670


Integers: + 30 * (j-1) )
V1, V2, V3, U12, U23, U31, I1, I2, I3, P, Q, cos, Hz
double-integers:
Ea+, Ea-, Er+, Er-.

li_... PECA/EVA n j communicates properly on MODBUS %M( 0832


network. + (j-1) )

Counter of correct answers from PECA/EVA n j. %R( 1162


+ 15 * (j-1) )

Counter of faulty answers from PECA/EVA n j. %R( 1163


+ 15 * (j-1) )

Last NOK report from PECA/EVA n j. %R( 1165


+ 15 * (j-1) )

RULES FOR IMPLEMENTATION:

- DMB_EVA must be used with DMB_UE and DMB_PER.

- It should be called after DMB_PER and before the application program.

_______________________________________________________________________________________
AA M-SM01-A40028.137/A
Modbus reception from Neyrpic SLG DMB_SLI

PROCESSING:

- Reads bits 60H to 8FH in SLG and copies bits 60H to 6FH and 80H to 8FH in %M area.

- Reads words 60H to 71H in SLG.

PARAMETERS:

(1)
dd_mbus_ue_slave_09 Number of the Exchange Unit on which SLG %R1279
is connected. 1 to 4.

dd_mbus_subs_nb_slave_09 (1) SLG subscriber number on Modbus network %R1286


1 to 31. (as customised inside SLG)

dd_mbus_period_ slave_09 (1) Period for reading the bits %R1280


0 (default value) = as soon as possible
X: period = X*500 ms

dd_mbus_period_ slave_10 (1) Period for reading the words %R1295


0 (default value) = as soon as possible
X: period = X*500 ms

(1)
Those parameters must be filled in a CADEPA graph in application AF_FST.

INPUTS: none.

OUTPUTS:

li_... SLG communicates properly on MODBUS %M0841

li_... Bits 60H to 6FH read in SLG %M0769-784


li_... Bits 80H to 8FH read in SLG %M0785-800

di_... Words 60H to 71H read in SLG %R1913-1928

Counters of OK answers to bit/word reading %R1282/%R1297


Counters of NOK answers to bit/word reading %R1283/%R1298
Last NOK report to bit/word reading %R1285/%R1300

RULES FOR IMPLEMENTATION:

- DMB_SLI must be used with DMB_UE and DMB_PER and called after DMB_PER and
before the application program.

- Neyrpic SLG is slave 9 ie its "equipt number" in OGIV-8035 must be 9. Slaves 10 to 12 are
also used by DMB_SLI/SLO and can not be allocated to any slave device in OGIV-8035.

_______________________________________________________________________________________
AA M-SM01-A40028.138/A
Modbus sending to Neyrpic SLG DMB_SLO

PROCESSING:

- Writes order 80H to 1 at each scan,

- Sends orders 80H to 8FH when they are different from bits 80-8FH received from SLG

- Periodically triggers through DMB_PER the periodic writing of words 80H to 90H.

PARAMETERS:

(1)
dd_mbus_ue_slave_09 Number of the Exchange Unit on which SLG %R1279
is connected. 1 to 4.

dd_mbus_subs_nb_slave_09 (1) SLG subscriber number on Modbus network %R1286


1 to 31. (as customised inside SLG)

dd_mbus_period_slave_11 (1) Period to send words 80H to 8FH %R1310


0 (default value) = as soon as possible
X: period = X*500 ms

(1)
Those parameters must be filled in a CADEPA graph in application AF_FST.

INPUTS:

lo_… 16 bits to send to SLG at address 80H to 8F %M3265-3280

do_… 17 words to send to SLG at address 80H to 90H %R1944-1960

OUTPUTS:

Counters of OK answers to word writing %R1312


Counters of NOK answers to word writing %R1313
Last NOK report to word writing %R1315

RULES FOR IMPLEMENTATION:

- DMB_SLO must be used with DMB_UE and DMB_PER and called after the application
program and before DMB_UE.

- Neyrpic SLG is slave 9 ie its "equipt number" in OGIV-8035 must be 9. Slaves 10 to 12 are
also used by DMB_SLI/SLO and can not be allocated to any slave device in OGIV-8035.

_______________________________________________________________________________________
AA M-SM01-A40028.139/A
Management of Modbus exchange units DMB_UE

PROCESSING:

- Handles up to 4 MODBUS Exchange Units (a MODBUS EU is a channel of a PCM


module).

- Starts the EUs one after the other 6 to 12 seconds after the PLC start-up or on request.

- Periodically checks whether an EU is still running.

- Stops the EUs at last scan or on request.

- Sends the exchange requests issued from the slave blocks (DMB_EVA, DMB_CHS,...) to
their related EUs.

PARAMETERS:

dd_mbus_nb_of_eu (2) Number of MODBUS Exchange Units %R0764


1 to 4
(1) (2)
dd_mbus_slot_eu_i Slot of the PCM module supporting EU n° i, 1≤ i ≤4 %R( 834
2 to 10. + 15 * (i-1) )
(1) (2)
dd_mbus_channel_eu_i Channel of EU n° i on the PCM module, 1≤ i ≤4 %R( 835
1 or 2. + 15 * (i-1) )
(3)
dd_mbus_turnaround_delay Turnaround time delay, in ms. Delay between the %R0756
reception of a message and the sending of an other.
It allows the slave device to get ready for reception.
Default value: 60 ms.
(3)
dd_mbus_waiting_time Time during which the EU waits for the slave answer. %R0757
Default value: 500 ms.
(3)
dd_mbus_nbr_reemissions Number of reemissions after an incorrect answer. %R0758
When a slave is NOK, the time wasted by a question sent
to it is: (dd_mbus_nbr_reemissions + 1)*dd_mbus_waiting_time.
Default value: 1.

(1)
i = logical number of the MODBUS EU, used for internal processing.
(2)
Updated by OGIV-8035 in og_mbus.gig to import into CADEPA (AP_FST).
(3)
Those parameters are common to all the MODBUS EUs of the controller.
If their default values do not fit, the user may modify them in cnf_mbu.gig which must
then be imported into CADEPA (AP_FST).

_______________________________________________________________________________________
AA M-SM01-A40028.140/A
Management of Modbus exchange units DMB_UE

INPUTS:

Number of the EU to start. %R0762


For test purpose only

Number of the EU to stop. %R0763


For test purpose only

OUTPUTS:

Communication OK with slave i, 1 ≤ i ≤32. %M(0833¨+


i –1 )

RULES FOR IMPLEMENTATION:

- Must be called after all the program blocks handling the exchanges with slave devices.

_______________________________________________________________________________________
AA M-SM01-A40028.141/A
Resets PLC data memory DPC_FST

PROCESSING:

- Resets : %I 0017 to %I 1984,


%Q 0001 to %Q 2000,
%G 0001 to %G 1280,
%M 0449 to %M 0816 and %M 0833 to %M 4096
%AI 0001 to %AI 2560,
%AQ 001 to %AQ 512,
%R 0016 to %R 5500.

- Doesn't reset : %I0001 to %I0015 to allow the user to encode the unit
number.
%T0001 to %T0256 as they are not retentive (automatically
reset)
%M0001 to %M0448 Processed by CS domain.
%M0817 to %M0832 to allow domain to use retentive %M.
%I1985 to %I2048 Processed by CS domain.
%Q2001 to %Q2048 Processed by CS domain.
%R5501 to %R9999 Processed by CS domain.
%R0001 to %R0009 the table of the missing modules must be
kept when the PLC is stopped.

PARAMETERS: none.

INPUTS: none.

OUTPUTS: none.

RULES FOR IMPLEMENTATION:

- DPC_FST must be called at first scan only.

- It must be the first block called at first scan.

_______________________________________________________________________________________
AA M-SM01-A40028.142/A
Monitoring of the controller DPC_IN

PROCESSING:

- On loss of an I/O or coprocessor module, updates the table of the missing modules
and resets it when the faults are erased from P8.

- Provides the date and time in BCD.

PARAMETERS: none

INPUTS: none

OUTPUTS:

dd_faulty_modules_rack_000x Table of the missing modules %R000x


Bit i of word x = 1 when the module located
slot i of rack x is missing or faulty.
x = 1 to 8.

dd_bcd_month_year Least Significant Byte (LSB) = year in BCD: 00 to 99 %R0011


Most Significant Byte (MSB) = month in BCD: 01 to 12

dd_bcd_hour_day LSB = day in BCD: 01 to 31 %R0012


MSB = hour in BCD: 00 to 23

dd_bcd_sec_min LSB = minutes in BCD: 00 to 59 %R0013


MSB = seconds in BCD: 00 to 59

dd_bcd_day_nbr Day of the week: 1 = Sunday to 7 = Saturday %R0014

RULES FOR IMPLEMENTATION:

DPC_IN must be called before the application program.

_______________________________________________________________________________________
AA M-SM01-A40028.143/A
Monitoring of INTERACT MMI DPC_MMI

PROCESSING:

- Checks MMI presence. Sets MMI presence bit each time a new value is received in
%R0028 and resets it when no new value has been received for 7 s.

- Updates the decimal time and date every minute and triggers its update in
INTERACT.

PARAMETERS: none

INPUTS:

INTERACT must regularly change the value of this %R0028


Word. For example send INTERACT seconds in it.

OUTPUTS:

ld_mmi_ok Communication with INTERACT MMI is OK %M0803

Hour in decimal. 0 to 23. %R0021

Minutes in decimal. 0 to 59. %R0022

Seconds in decimal. 0 to 59 %R0023

Month in decimal. 1 to 12 %R0024

Day in decimal. 1 to 31 %R0025

Year in decimal. 0 to 99 %R0026

When a new date and time is written in %R0021-26, %R0027


%R0027 changes from 0 to 1 for 1s in order to trigger
the update of hour and date in INTERACT.

_______________________________________________________________________________________
AA M-SM01-A40028.144/A
Monitoring of INTERACT MMI DPC_MMI

RULES FOR IMPLEMENTATION:

- DPC_MMI must be called after DPC_OUT.

- The following customisation must be written in INTERACT PROJECT MANAGER:

- “Application settings” “Start-up settings” “Time and date”


Read Time Reference: GESN\<ID SNP>:R21
Read Date Reference: GESN\<ID SNP>:R24
Read Time and Date Trigger: GESN\<ID SNP>:R27

Send Time/Date … parameters keep “none”

- “Application settings” “Driver set-up”


Watchdog Reference: <ID SNP>:R28
Watchdog Interval: 1 second

_______________________________________________________________________________________
AA M-SM01-A40028.145/A
Stops the controller DPC_OUT

PROCESSING:

- Stops the controller on application request.

PARAMETERS: none

INPUTS:

ld_plc_stop_req Order to stop the PLC. %T0256


May be set by the application program or directly
received from MMI.

OUTPUTS: none

RULES FOR IMPLEMENTATION:

_______________________________________________________________________________________
AA M-SM01-A40028.146/A
Interface with S8000 communication utilities (reception) DS8_IN

PROCESSING

- Monitors the presence of the other S8000 subscribers:


- the presence of a subscriber is detected on reception of its broadcast message,
- a subscriber is declared absent when its broadcast message has not been
received for 1.1s minimum to 2.2s max.

- On loss of a subscriber, resets the 20-word and 64-word messages from the lost
subscriber i.e. resets all the variables previously received from it.

- Copies in discrete references (%I) the inter-controller bits received from the other
subscribers. (the bits and words sent by the other subscribers are received in %R
references but the application program written with CADEPA can not easily use discrete
variables stored in %R)

PARAMETERS:

dd_S8000_iab_adr_li_00xx (1) Word rank in %I area where DS8_IN copies the %R( 311 +
broadcast bits received from subscriber xx (1≤ xx ≤ 16) 2(xx-1) ).
1st Address – 1
= ———————— + 1
16

( = 1 for %I0001, 2 for %I0017, 3 for %I0033 ... )


(1)
dd_S8000_iab_nbr_16li_00xx Number of words of 16 BS (broadcast bits) %R( 312 +
received from subscriber xx (1≤ xx ≤ 16) 2(xx-1) )

dd_S8000_iap_adr_li_00xx (1) In the group cell (subscriber 16) only. %R( 343 +
Word rank in %I area where DS8_IN copies the bits 2(xx-1) ).
sent by subscriber xx (1≤ xx ≤ 15) to PLC 16.
(1)
dd_S8000_iap_nbr_16li_00xx In the group cell (subscriber 16) only. %R( 344 +
Number of words of 16 bits sent by subscriber 2(xx-1) )
xx (1≤ xx ≤ 15) to PLC 16.

(1)
updated by OGIV-8035 in og_s8i.gig file to import in CADEPA (AP_FST).

_______________________________________________________________________________________
AA M-SM01-A40028.147/A
Interface with S8000 communication utilities (reception) DS8_IN

INPUTS / OUTPUTS: from S8000 communication utilities (FM_RECV):

- FR_IDxx and FR_IPxx Their 1st bit is reset by DS8_IN once read.
FR_ID/Pxx is reset by DS8_IN on detection of the loss of
subscriber xx.

OUTPUTS:

ld_S8000_subs_run_00xx Subscriber xx (1 ≤ xx ≤ 16) is running and %M( 865 +


communicates properly on S8000. xx - 1 )

li_... dd_S8000_iab_nbr_16li_00xx BS (broadcast bits) %I


received from subscriber xx at address
%I(dd_S8000_iab_nbr_16li_00xx *16 - 15)

li_... In PLC 16 only. %I


dd_S8000_iap_nbr_16li_00xx PS (point-to-point bits)
received from subscriber xx at address
%I(dd_S8000_iap_nbr_16li_00xx *16 - 15)

RULES FOR IMPLEMENTATION:

- DS8_IN detect the arrival of a new message thanks to the 1st bit of the message which
must be set to 1 by the issuer PLC. This is performed by DS8_OUT.

_______________________________________________________________________________________
AA M-SM01-A40028.148/A
Interface with S8000 communication utilities (emission) DS8_OUT

PROCESSING:

- Sets to 1 the 1st bit of the 20-word broadcast message and of the 64-word message sent
to the group cell.

- Copies the 1024-TS, 1024-TS-invalidating-bits and 222-TM-invalidating-bits, updated


by the application program, in the %R messages sent to CENTRALOG by S8000
communication utilities.

- Copies the 16 *dd_S8000_iab_nbr_16bits BS (inter-controller bits to broadcast),


updated by the application program, in the dd_S8000_iab_nbr_16bits first words of the
%R message broadcast on S8000.

- Copies the 16 *dd_S8000_iap_nbr_16bits PS (point-to-point inter-controller bits),


updated by the application program, in the dd_S8000_iab_nbr_16bits first words of the
%R message sent to the regrouping controller (subscriber 16).

PARAMETERS

dd_S8000_iab_16bits (1) Number of words of 16 BS (bits to broadcast %R0301


to all S8000 subscribers).

dd_S8000_iap_16bits (1) Number of words of 16 PS (bits to send on S8000 %R0303


to the regrouping PLC only).
(1)
dd_S8000_iap_1st_word_ps Rank of the first word of PS in the inter-controller %R0302
bit table (%Q1521 table).
(1) st
ld_S8000_1024_ts Must be set after 1 scan if there are more than 512 TS %M0810

(1)
Updated by OGIV-8035 in og_s8o.gig to import in CADEPA (AP_OUT).

_______________________________________________________________________________________
AA M-SM01-A40028.149/A
Interface with S8000 communication utilities (emission) DS8_OUT

INPUTS

(2)
ld_S8000_ts_xxxx TS xxxx to send to CENTRALOG
1 ≤ xxxx ≤ 1024 %M1905-2928
(2)
ld_S8000_invalid_ts_xxxx Invalidating bit of TS xxxx
1 ≤ xxxx ≤ 1024 %M0881-1904
(3)
ld_S8000_invalid_tm_0xxx Invalidating bit of TM xxx %Q1777-2000
1 ≤ xxx ≤ 222.

ld_S8000_iab_e_0xxx (1) Inter-PLC bits to broadcast on S8000 %Q1521-1776


1 ≤ xxx ≤ 256.

(1)
Updated by OGIV-8035 in og_s8o.gig to import in CADEPA (AP_OUT).
(2)
Updated by OGIV-8035 in og_ts_c.gig to import in CADEPA (AP_OUT).
(3)
Updated by OGIV-8035 in og_tm_c.gig to import in CADEPA (AP_OUT).

OUTPUTS for FM_SEND

FO_E1TS, FO_E2TS TS registers


FO_V1TS, FO_V2TS TS invalidating bit registers
FS_VLTM TM invalidating bit registers
FS_IADF 20-word inter-PLC message to broadcast

RULES FOR IMPLEMENTATION:

- The 1st broadcast bit and the 1st point to point bit sent to the group cell are both set to 1 by
DS8_OUT. The application program should therefore not write in them.

- The intercontroller broadcast message is sent every 500 ms; the point to point message to
group cell every 1s. To send state changes shorter than 500 ms / 1s, the application
program must store them until the falling edge of FS_E_IA (%M86) / FS_E_RG (%M87).

_______________________________________________________________________________________
AA M-SM01-A40028.150/A
APPENDIX F : LIST OF .gig FILES FOR THE CUSTOMISATION OF DOMAIN

NAME DESCRIPTION PLC From COMMENTS APPL.

Declaration of min/max phy-


Og_anai S/M O AP_FST
sical value for analog inputs
Configuration of analog inputs
Cnf_alg processing for ALG222/223 S/M C AP_FST
modules
Configuration of analog inputs Only used in addition of cnf_alg
Cnf_al1 processing for ALG222/223 S/M C if the plc have 2 different AP_FST
modules min/max raw value
Configuration of analog inputs Only used in addition of cnf_alg
Cnf_al2 processing for ALG222/223 S/M C and cnf_al2 if the plc have 3 AP_FST
modules different min/max raw value
Declaration of Modbus
Cnf_mbu S/M C AP_FST
communication parameters

Configuration of Modbus
Og_mbus S/M O AP_FST
exchanges
Configuration of S8000 inter-
Og_s8in controller exchanges M O AP_FST
(Receiving)
Configuration of F8000 network
Cnf_F8 S/M O AP_OUT
system exchanges

Declaration of TS transmitted to
og_ts_i M O AP_OUT
the M.M.I

Declaration of TM transmitted
og_tm_i M O AP_OUT
to the M.M.I

Declaration of TS transmitted to
og_ts_c M O AP_OUT
Centralog

Declaration of TM transmitted
og_tm_c M O AP_OUT
to Centralog

Configuration of S8000 inter-


og_s8o M O AP_OUT
controller exchanges (Sending)

Pulse elaboration for horn


og_horn S/M O AP_OUT
activation

Legend : S : Used in SUB controller M : Used in MAIN controller


C: File available on Domain disk under A:\CADEPA
O: File generated by OGIV-8035

_______________________________________________________________________________________
AA M-SM01-A40028.151/A