Académique Documents
Professionnel Documents
Culture Documents
ETABLI
AUBARBIER
ESTABLISHED
VERIFIE TOTH
CHECKED
APPROUVE
GRISIER
APPROVED
IRE
TABLE DES MODIFICATIONS / MODIFICATIONS TABLE
_______________________________________________________________________________________
AA M-SM01-A40028.2/A
PA 401 A
CONTENTS
_______________________________________________________________________________________
AA M-SM01-A40028.5/A
RELATED DOCUMENTS
[1] ALS 52102 c Alspa C85-35 and 80-25 PLCs Reference Manual
[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
[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
[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
CENTRALOG
S8000
SITE N ETW OR K
SNP
MMI NETWORK M AIN M AIN M AIN
M AIN
F8000
FIELD
NETWORK
IHRi SUBi
IHRi
The "MAIN" PLCs can exchange inter-controller variables through S8000 network.
The “IHR’’ PLCs time-tag discrete inputs with a 1ms resolution. They don't have
any application program but house a software which performs :
_______________________________________________________________________________________
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.
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.
- 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:
- 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
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
1.1.3 Limitations
1.1.3.1 S8000
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.
_______________________________________________________________________________________
AA M-SM01-A40028.10/A
1.1.4 Selected modules
1.1.4.1 Baseplates
- 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.
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
* A CPU350 for a SUB PLC with MODBUS communication and analog conversion
and filtering still have room for a little application program
- IC693BEM340 (also called FBC30) must be used in MAIN , IHR and SUB PLCs
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.
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
- 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".
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.
Refer to document [3] (ALS 52118) for the description of all the available I/O
modules.
- IC693MDL753 : 32 static outputs, 12/24 Vdc positive logic, 0,5A max. Same
comment as IC693MDL655 for output wiring.
Refer to :
- Document [3] (ALS 52118) for the description of all the available IC693XXX
analog input modules
- 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.
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
- 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)
CADEPA ALSPA 8000 translator translates programs written with CADEPA in SFC
or textual language into C80-35 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.
_______________________________________________________________________________________
AA M-SM01-A40028.17/A
1.2.3 OGIV-8035 database manager
- Idem for the consistency of the variables between the PLCs and their MMI.
_______________________________________________________________________________________
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.
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.
_______________________________________________________________________________________
AA M-SM01-A40028.19/A
1.4 ENGINEERING STAGES
CADEPA
OGIV
P8
Stage Comment Related document
6. MMI programmation
_______________________________________________________________________________________
AA M-SM01-A40028.20/A
CADEPA
OGIV
P8
Stage Comment Related document
9. Tests
_______________________________________________________________________________________
AA M-SM01-A40028.21/A
2 DECLARATION AND CONFIGURATION OF THE AUTOMATION CELL
2.1 PRINCIPLES
- 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
OGIV-8035 only.
Use TAB. key to move from one field to the next one.
Designation: 40 characters
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).
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.
_______________________________________________________________________________________
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
_______________________________________________________________________________________
AA M-SM01-A40028.25/A
- Declare a SUB1 PLS as follow:
- Once all the controller of the cell are declared, click on the “Exit” button. Then,
verify that OGIV has automatically created all the declared controllers. To do
this, select “Project”, “Select”:
- 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 :
_______________________________________________________________________________________
AA M-SM01-A40028.27/A
3 DECLARATION OF THE INPUTS/OUTPUTS
3.1 PRINCIPLES
- 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).
• capture of the mnemonic, label and possibly other attributes (refer to appendix
C for the list of attributes of the I/O references),
- 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
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.
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.
_______________________________________________________________________________________
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.
- For each analog input, OGIV-8035 generates 3 references. They are the DOMAIN
outputs:
. 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):
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.
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.
_______________________________________________________________________________________
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.
- 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.
_______________________________________________________________________________________
AA M-SM01-A40028.32/A
3.1.4 Discrete outputs
_______________________________________________________________________________________
AA M-SM01-A40028.33/A
3.2 PROCEDURE
OGIV-8035 only.
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.
_______________________________________________________________________________________
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:
• 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
- 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
- For each record, the fields of the following table are displayed. Refer to appendix
C to know their meaning and format.
- 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)
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.
_______________________________________________________________________________________
AA M-SM01-A40028.36/A
FIELD Logical Inputs Logical Outputs Analog Inputs Analog Outputs
Unit Not applicable Type any letter to display the list of the
valid units and select one of them.
Validation bit=state_1
S ( =TS ) for
validation bits
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
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.
- 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
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 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".
- 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 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)
_______________________________________________________________________________________
AA M-SM01-A40028.40/A
4 MODBUS IMPLEMENTATION
4.1 INTRODUCTION
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.
An "Y cable" is supplied with the module to split the 2 ports on 2 separate
connectors.
• Port 1 provides an RS-232 interface
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.
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.
• Declaration of the slave devices. OGIV-8035 then generates all the Modbus
I/O references
• 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
OGIV-8035 only.
The following screen is displayed. Use TAB to move from one field to the next.
PCM Slot : 2 to 10. Slot of CPU rack where the PCM301 module supporting the
EU is located.
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
Name : Up to 12 characters
Name of the slave device. It appears in attribute location of the
MODBUS inputs/outputs.
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.
_______________________________________________________________________________________
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.
- 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.
- 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.
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.
_______________________________________________________________________________________
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 currents, in amps
- Frequency, in 0.1 Hz
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,
_______________________________________________________________________________________
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:
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.
Period: The measurements are read in the slave device every x * 500 ms (x =
value entered by the user).
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
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).
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.
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
- 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_".
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
Choose PCM CFG (It means that PCM configuration will be performed thanks to
files loaded into the module : pcmexec.bat and hardexec.bat).
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.
Lines 4 and 5 are the configuration of User 1 and User 2 front side LEDs:
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.
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.2 Procedure
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.
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>.
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
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.
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.
(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
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 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
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
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.
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….).
- 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”.
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”.
. Mnemonic
. Label
_______________________________________________________________________________________
AA M-SM01-A40028.59/A
. State_1 message
. STD
. V mini / V maxi
. Acq. rate
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:
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.
_______________________________________________________________________________________
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”
- 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:
• 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_).
• 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:
(That case occurs when the variable has been renamed in the
sending PLC).
_______________________________________________________________________________________
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:
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 )
* Press the spacebar to scroll through the list then validates with Enter.
- 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.
- 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
The following screen is displayed: Use “TAB” to move from one field to the next.
- From Project : Issuer project name. Only the projects declared on the PC (in
local or remote) are displayed .
. 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.
_______________________________________________________________________________________
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".
_______________________________________________________________________________________
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:
- 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.
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
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 )
* Press the spacebar to scroll through the list then validate with Enter.
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
- Redundancy: defines the hardware structure for dual communication, for F8000
taking over and for basic exchanges.
- 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.
_______________________________________________________________________________________
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:
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: 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.
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.
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
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
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.
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.
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).
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.
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
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
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
• 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.
• og_tm_i.gig
_______________________________________________________________________________________
AA M-SM01-A40028.79/A
Refer to Appendix C for the list of attributes of the variables exported to MMI.
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>
_______________________________________________________________________________________
AA M-SM01-A40028.80/A
10 DUPLICATION OF EXPORTED PROJECT DATA
First you have to select the file where are located the datas to duplicate. Once the
file selected, a screen is displayed
. 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.
_______________________________________________________________________________________
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
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
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.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.
_______________________________________________________________________________________
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:
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
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).
• 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
The whole application program of the PLC should be written with CADEPA.
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.
• 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 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.
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:\)
"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:
_______________________________________________________________________________________
AA M-SM01-A40028.88/A
The technical comment is currently not used in our standards.
_______________________________________________________________________________________
AA M-SM01-A40028.89/A
12.2.1.2 Setting of the default PLC memory mapping
• 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.
- 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:
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).
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).
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.
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.
• "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.
Click on "Fonts":
_______________________________________________________________________________________
AA M-SM01-A40028.92/A
12.2.2 Creation of a project
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.
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 variables
The attributes PLC manufacturer and PLC type must be respectively set to "ALSPA-
8000", "80 - 35/351" or "80 - 35/363".
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.
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.
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.
This operation allows to display the titles of the variables in CADEPA and helps
avoiding spelling mistakes when using the variables in the 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:
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.
_______________________________________________________________________________________
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.
This operation will allow ogiv8035 to address all process variables created in CADEPA
application graphs.
- Select "File" "Export", then choose “.mne files ” at the bottom of the window (list
files of type :).
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
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
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.
• 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
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.
_______________________________________________________________________________________
AA M-SM01-A40028.100/A
13.7 ADDRESSING UTILITIES
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
“?”
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.
_______________________________________________________________________________________
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.
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.
_______________________________________________________________________________________
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
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
_______________________________________________________________________________________
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.
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
In OGIV8035
In P8
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.
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.
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.
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.
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.
_______________________________________________________________________________________
AA M-SM01-A40028.108/A
APPENDIX B : MNEMONICS OF THE VARIABLES
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.
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 :
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.
The operative unit or its 3 letters must begin character 4 of the mnemonic.
Examples :
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
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.
____________________________________________________________________________________________________________________________________
AA M-SM01-A40028.111/A
ATTRIBUTE FORMAT CADEP OGIV MMI CLOG APPLIES TO
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.
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.
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
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.
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
For internal processing, the additional "ALARM" column must be set to 0 when
URGENCY = 0 and to 1 otherwise.
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
- 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 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:
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.
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:
- 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).
- 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.
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:
The validity bit, physical value and copy of raw value of an input are updated at the same time every:
_______________________________________________________________________________________
AA M-SM01-A40028.120/A
Validation and conversion of ALG222/223 analog inputs DAI_ALG
"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:
_______________________________________________________________________________________
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.
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.
_______________________________________________________________________________________
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.
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.
_______________________________________________________________________________________
AA M-SM01-A40028.123/A
Validation of RTD inputs DAI_RTD
PROCESSING:
- DAI_RTD copies the 6 channels into 6 other %AI to be consistent with DAI_ALx modules.
PARAMETERS:
* 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:
_______________________________________________________________________________________
AA M-SM01-A40028.124/A
Duality updating control DDU_CTR
PROCESSING:
PARAMETERS: none
INPUTS:
OUTPUTS:
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:
OUTPUTS: none
_______________________________________________________________________________________
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:
OUTPUTS: none
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.
- 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)
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:
OUTPUTS:
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
_______________________________________________________________________________________
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.
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)
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:
OUTPUTS:
_______________________________________________________________________________________
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:
(2)
dd_f8000_1st_iword_to_send Rank of the 1st %I word to send to MAIN %R0031
(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:
(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:
_______________________________________________________________________________________
AA M-SM01-A40028.133/A
Communication with a CHESSELL temperature acquisition unit DMB_CHS
PROCESSING:
- The alarms are reset and the measurements set to -32768 (8000H) when the
communication with CHESSELL is lost.
PARAMETERS:
(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:
- DMB_CHS must be used with DMB_UE and DMB_PER and called after DMB_PER and
before the application program.
_______________________________________________________________________________________
AA M-SM01-A40028.135/A
Communication with PECA or EVA devices DMB_EVA
- 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_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:
OUTPUTS:
_______________________________________________________________________________________
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.
PARAMETERS:
(1)
dd_mbus_ue_slave_09 Number of the Exchange Unit on which SLG %R1279
is connected. 1 to 4.
(1)
Those parameters must be filled in a CADEPA graph in application AF_FST.
INPUTS: none.
OUTPUTS:
- 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:
- 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.
(1)
Those parameters must be filled in a CADEPA graph in application AF_FST.
INPUTS:
OUTPUTS:
- 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:
- Starts the EUs one after the other 6 to 12 seconds after the PLC start-up or on request.
- Sends the exchange requests issued from the slave blocks (DMB_EVA, DMB_CHS,...) to
their related EUs.
PARAMETERS:
(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:
OUTPUTS:
- 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:
- 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.
_______________________________________________________________________________________
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.
PARAMETERS: none
INPUTS: none
OUTPUTS:
_______________________________________________________________________________________
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:
OUTPUTS:
_______________________________________________________________________________________
AA M-SM01-A40028.144/A
Monitoring of INTERACT MMI DPC_MMI
_______________________________________________________________________________________
AA M-SM01-A40028.145/A
Stops the controller DPC_OUT
PROCESSING:
PARAMETERS: none
INPUTS:
OUTPUTS: none
_______________________________________________________________________________________
AA M-SM01-A40028.146/A
Interface with S8000 communication utilities (reception) DS8_IN
PROCESSING
- 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
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
- 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:
- 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.
PARAMETERS
(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.
(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).
- 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
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
_______________________________________________________________________________________
AA M-SM01-A40028.151/A