Cell Loader - Ptp21a41011-Ec

ALSPA Controcad
Version 4.5
Cell Loader R2
User's Manual 11
PTP21A41011 en Rev. C
Format A4
Edition 2008-07-31
ALSPA Control System
PTP21A41011
Edition 2008-07-31
Template PTP20A44502 en Rev B – Copyright © ALSTOM 2007. We reserve all rights in this document and in the
information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden
ALSTOM, the ALSTOM logo and any alternative version thereof are trademarks and service marks of ALSTOM. The other
names mentioned, registered or not, are the property of their respective companies.
The technical and other data contained in this document is provided for information only. Neither ALSTOM, its officers and
employees accept responsibility for or should be taken as making any representation or warranty (whether express or
implied) as to the accuracy or completeness of such data or the achievement of any projected performance criteria where
these are indicated.
You are authorized to copy this document. The authorization is limited to:
(i) Non–commercial use within your
(ii) organization
(ii) Use for informational purposes only
This authorization is given on condition that any copy of these documents or extracts there from made by you shall retain all
proprietary notices, including this Intellectual Property Notice.
Note that any product, process or technology described in the document may be the subject of other Intellectual Property
Rights reserved by ALSTOM or a third party. No right to use such Intellectual Property Rights is granted hereunder.
ALSTOM provides access to internationally used ALSTOM data and, therefore, may include references to ALSTOM
products, processes, programs and services not available in your country. This does not mean that ALSTOM intends to offer
such products, processes, programs and services in your country.
This publication is PROVIDED ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON–INFRINGEMENT.
This publication may include technical inaccuracies or typographical errors. Changes may be periodically made to the
information herein and will be incorporated in new editions of this publication.
ALSTOM reserves the right to revise or changes data, processes or the programs described in this publication at any time
without further notice.
SOMMAIRE / TABLE OF CONTENTS
Section 1 Introduction ............................................................................................................ 6

1.1 Presentation of Cell Loader ......................................................................................................................6
1.2 Users ........................................................................................................................................................6
1.3 Reference Documents..............................................................................................................................6
1.4 Definitions .................................................................................................................................................7
1.5 Accessing Cell Loader..............................................................................................................................7
Section 2 Description of Cell Loader..................................................................................... 9
2.1 Version Management Zone ....................................................................................................................10
2.1.1 Selecting the Generation Version .....................................................................................................10
2.1.2 Choosing the Generation Versions to be Saved...............................................................................11
2.1.3 Number of Generation Versions Saved (External to Cell Loader) ....................................................11
2.1.4 Deleting a Generation Version (External to Cell Loader)..................................................................12
2.1.5 Version Control Zone ........................................................................................................................12
2.2 Tools .......................................................................................................................................................17
2.2.1 Select configurations entities ............................................................................................................17
2.2.2 Settings .............................................................................................................................................17
2.3 Display....................................................................................................................................................18
2.3.1 Log.....................................................................................................................................................18
2.3.2 Tooltips ..............................................................................................................................................18
2.4 Producing the Automation Cell Configuration ........................................................................................19
2.5 Indicators in the Loading Interface Zone ................................................................................................19
2.5.1 Indicator of presence of the device on S8000...................................................................................19
2.5.2 Indicator of presence of the device on F8000 ...................................................................................19
2.5.3 Functional indicators of the device....................................................................................................20
2.5.4 Indicators associated to Ign. functionality .........................................................................................20
2.5.5 Indicators associated to Appli. functionality ......................................................................................20
2.5.6 Indicators associated to Rdn functionality.........................................................................................21
2.5.7 Indicators associated to M/S functionality .........................................................................................21
2.5.8 Indicators associated to Forcing I/O or Forcing Var functionality ....................................................22
2.5.9 Signification of checkboxes...............................................................................................................22
2.5.10 Toolbar ..............................................................................................................................................23
2.6 Loading/Reading the Firmware Version Controller ................................................................................25
2.6.1 C80-75...............................................................................................................................................25
2.6.2 MFC3000...........................................................................................................................................26
2.6.3 C80-35 and RX3i Field Controllers ...................................................................................................27
2.6.4 CE2000 .............................................................................................................................................28
2.6.5 DI103 .................................................................................................................................................28
2.7 Loading the Initial Configuration.............................................................................................................28
2.7.1 C80-75 (by serial link) .......................................................................................................................28
2.7.2 MFC3000...........................................................................................................................................29
2.7.3 C80-35 and RX3i Field Controllers (by serial link) ............................................................................30
2.8 Properties of a Device ............................................................................................................................35
2.8.1 C80-75...............................................................................................................................................35
2.8.2 MFC3000...........................................................................................................................................37
Copyright © ALSTOM 2007. We reserve all rights in this document and in the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden
ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Cell Loader R2 User's Manual 11 3/96
2.9 Loading the Configuration ......................................................................................................................40
2.9.1 C80-75 and MFC3000.......................................................................................................................40
2.9.2 C80-35 and RX3I Field Controllers ...................................................................................................44
2.9.3 CE2000 .............................................................................................................................................45
2.9.4 DI103 .................................................................................................................................................45
2.10 Loading after Modifying the Controller Application.................................................................................46
2.10.1 C80-75 and MFC3000.......................................................................................................................46
2.11 Loading after Modifying the Tuning Parameters ....................................................................................46
2.11.1 C80-75...............................................................................................................................................46
2.11.2 MFC3000...........................................................................................................................................47
2.12 Running the Application .........................................................................................................................48
2.13 Running the Application on a Redundant Device...................................................................................49
2.14 Stopping the Application.........................................................................................................................50
2.15 Stopping the Application on a Redundant Device..................................................................................50
2.16 Switching Over a Redundant Device......................................................................................................51
2.17 Switching to Cycle to Cycle Mode ..........................................................................................................52
2.18 Inserting a Device...................................................................................................................................53
2.18.1 C80-35 and RX3i field controllers .....................................................................................................53
2.18.2 CE2000 .............................................................................................................................................54
2.18.3 DI103 .................................................................................................................................................54
2.19 Standalone RX3i Controller ....................................................................................................................55
2.20 DI80 ........................................................................................................................................................55
2.21 GEMSTART............................................................................................................................................55
2.22 DI-OPC ...................................................................................................................................................56
Section 3 Full Loading on the C80-75 and MFC3000 Cell .................................................. 57
3.1.1 Rule for Selecting the Configuration Entities ....................................................................................57
3.1.2 Loading a Cell without Adding a Device............................................................................................57
Section 4 Startup/Shutdown of C80-75 and MFC3000 Cell Devices .................................. 59
Section 5 On-line Modification of the Controller Application ............................................ 61
5.1 On-line Modification of the C80-x5-RX3i Controller Application ............................................................61
5.1.1 Definition ...........................................................................................................................................61
5.1.2 Operating Mode.................................................................................................................................62
5.2 On-line Modification of the MFC3000 Controller Application .................................................................66
5.2.1 Definition ...........................................................................................................................................66
5.2.2 Operating Mode.................................................................................................................................66
Section 6 Stopping M/S Transfers for On-line Modification of Tuning Parameters
(C80-35, MFC3000 and RX3I) ............................................................................... 71
6.1 Definition.................................................................................................................................................71
6.2 Operating mode......................................................................................................................................71
6.2.1 C80-35 and RX3I Controllers ............................................................................................................71
6.2.2 MFC3000 Controller ..........................................................................................................................73
6.3 Backnoting Tuning Parameters (C80-x5 - RX3i -MFC3000)..................................................................74
6.3.1 Definition ...........................................................................................................................................74
6.3.2 Operating Mode.................................................................................................................................77

Section 7 Clearing Forced Values ....................................................................................... 79
7.1 Definition.................................................................................................................................................79
7.2 Forcing Command on C80-x5 and Rx3i Devices ...................................................................................80
7.3 Forcing Command on the MFC3000 Controller .....................................................................................80
7.4 Forcing Command on the CE2000 Field Controller ...............................................................................80
7.5 Forcing Command on AVR/SLG/IHR Controllers ..................................................................................81
Section 8 Accessing the Device Fault Tables..................................................................... 83
8.1 Reading Faults on C80-x5 and Rx3i Controllers....................................................................................83
8.2 Reading Faults on a MFC3000 Controller..............................................................................................84
8.3 Reading Serious CE2000 Controller Faults ...........................................................................................85
Section 9 Devices Simulated by SI80 .................................................................................. 87
9.1 Exporting Files for SI80 ..........................................................................................................................87
Section 10 System Information Zone .................................................................................... 88
10.1 C80-75 Cell Controller ............................................................................................................................88
10.2 MFC3000 Cell Controller ........................................................................................................................90
10.3 C80-35-AVR-SLG-IHR Field Controller..................................................................................................91
10.4 CE2000 r7 TRX Controller Field.............................................................................................................93

Section 1 Introduction
1.1 Presentation of Cell Loader
The on-line mode window designated as Cell Loader is used to:

 Present the overall state of the cell,
 Identify any requirement for loading,
 Indicate the reasons for the need for storage (difference between
CONTROCAD and target configurations),
 Store all the devices of a P320 phase 5.0 C8075 cell or P320 phase 5.1
MFC3000,
 Store the tuning parameters,
 Display system information,
 Perform on-line program and parameter modification operations,
 Indicate and delete any forced values present,
 Back-note the tuning parameters from the target to saved CONTROCAD
generation versions.
For a commissioning engineer the tool is doubly useful:
 On the one hand, Cell Loader can be used to automate tedious tasks that may
be sources of error (partial/total cell loading, managing ALSPA P80 PLC
folders, P80 PRO, CIMPLICITY Machine Edition),
 On the other hand, the tool also centralizes the help functions during the
commissioning phase once a project has been configured and generated by
CONTROCAD.
1.2 Users
This document is intended for P320 control & supervision system test engineers and
all system commissioning personnel.
1.3 Reference Documents
User's Manual PTP21A41010 [MEX10CCAD]

CONTROCAD V4.3 - Volume 10 – Commissioning Tools
User's Guide PTP21A41051 [GUICHGTCCAD]
CONTROCAD V4.3 - Loading Guide
PCX R1.2 User's Manual PSM-49 A40148 [MULPCX]

1.4 Definitions
Current version: Non-archived cell generation version.

Saved version: Archived cell generation version; only this version type is used by
Cell Loader.
Persistent variable: application variable whose value is determined by the current
controller cycle. A persistent variable maintains its current value through a controller
RUN/STOP or POWER OFF/ON cycle.
Tuning parameter (or tuning variable): variable defined with an initialization value
(Setting in the CONTROCAD variable grid is "Yes" ) and that can normally be
modified on-line after a parameter loading operation. This variable maintains its
value through a controller STOP/RUN cycle.
For a C80-X5, the tuning parameters are persistent.
For a CE2000, the tuning parameters are lost after a RUN/STOP and POWER/OFF
cycle.
Configuration entity: entity that symbolizes the device configuration categories.
Workspace: space within a single hardware architecture used to manage different
programs (from one workspace to another) on the same device.
SDA: Control Data Server supplied by Controcad that currently supports the E900
and HCT protocols (providing tuning, readout and observation functionalities); the
SDA also drives an application Watch window. These tools are described in the
document [MEX10CCAD].
1.5 Accessing Cell Loader
Before running Cell Loader, close all ALSPA P80 PLC, ALSPA P80 PRO and
CIMPLICITY Machine Edition programs.
The Cell Loader tool is accessible from the CONTROCAD hardware tree via the cell
name and the Store Cell menu.
START CELL LOADER

To close the Cell Loader window, click on File  Exit or .
Cell Loader execution error

 If the following error is generated, a Cell Loader process is still active; wait for
all the processes to stop.
 Otherwise open the Windows task manager and end the following processes if
are running: woml.exe, HCTsrv.exe, WB.exe

Section 2 Description of Cell Loader
CELL LOADER
Cell Loader opens as shown below. The elements shown in the diagram are
described in detail in the following chapters.
Selecting the Generation Version( See §2.1.1)

Toolbar ( See §2.5.10.)
Display( See §2.3.)
Functional indicators of a device( See §2.5.3.)
Version Control Zone( See §2.1.5.)
System Information Zone( See §Section 10.)

2.1 Version Management Zone
2.1.1 Selecting the Generation Version
CELL LOADER  Versions  Select

The generation version management zone is used to list all the generation versions
that the user can store into the controllers. The name of the workspace, and the
date and time of the CONTROCAD code generation are listed by version number.
Loading a version prior to the last generation is limited by the following

constraints:
 No animation (partial animation is possible if the addresses are
compatible), as the current generation version corresponds to the last
saved version.
 If the version to be stored is several versions back, the link with the
HMI Database may no longer exist due to the compatibility modes
used for code generation.
Choosing the Generation Versions to be Saved( See §2.1.2.)
Number of Generation Versions Saved (External to Cell Loader) ( See §2.1.3.)
Deleting a Generation Version (External to Cell Loader) ( See §2.1.4.)

2.1.2 Choosing the Generation Versions to be Saved
CELL LOADER  Versions  Keep

The user can decide to save a generation version despite the fact that multiple
generations will need to be produced during the commissioning phase. In this case
the icon is used to choose the versions to be saved. A version that is selected for
saving will remain available for loading as necessary.
2.1.3 Number of Generation Versions Saved (External to Cell Loader)
The number of generation versions that can be listed in this screen as available for
loading is configured in CONTROCAD in the Maximum Version column accessible
from the CONTROCAD  Edit Workspace  All Workspaces menu via the project
name Hard tab; this number must be defined for each of the workspaces.
The following options are also available from this tab:

 selection of the current workspace by checking the Current box. After
validation, the name of the chosen workspace will appear in brackets to right
of the name of the project in the hardware tree. The programs associated to
this workspace will be visible in the hardware tree.
 creation of a new workspace by selecting the "New" button and by inputting a
name and a label. The program is associated to a workspace either
automatically in the current workspace during the creation of a program, or by
importing an existing program from another workspace.
 destruction of a workspace and of the programs that are associated to it via
the "Delete" button .

2.1.4 Deleting a Generation Version (External to Cell Loader)
CONTROCAD  Display Cell Version

A generation version can be deleted from the Display Cell Version window
accessible in CONTROCAD from the cell Hard tab. If the version had been flagged
as "To be saved" from Cell Store, the user will be asked to confirm before the delete
operation can proceed.
The Version label field in the window is used to write a comment on each
generation. This simplifies management of the generation versions.
2.1.5 Version Control Zone
The version zone displays a set of data associated to the controller selected. When
the controller is redundant, this data concerns both the primary and secondary
devices.
The following information is available:
 The loading unit generation data produced by the CONTROCAD configuration
and the target devices,
 The versions of the loading units produced by the CONTROCAD configuration
and the target devices,
 Additional information produced by the target devices.
The variables in the version window and the equality/inequality states of the
configuration units will be updated on the occurrence of the following events :
 Establishment of a connection with the device
 End of the loading procedure
When data produced by a device is invalid (access impossible, device absent etc.) it
is shown with the symbol '?'.
When the selected device is simulated by SI80, all the data displayed as produced
by the devices is invalidated and is shown with the symbol '?'.

The name of the device is shown in the header (e.g. CC80-75). This name is
produced by the Cell Loader configuration and may be different from the target
device.
Tabs provide information on:
 Hardware (configuration unit),
 Program (configuration unit),
 Parameters (configuration unit),
 Misc. (additional information).
 Drivers (configuration unit S8000,F8000…).
Information provided by the tabs is produced by the active device (single or
redundant CE2000), by the primary and secondary devices when the device is
redundant (MFC3000, C80-35, C80-75, RX3I), and from the CONTROCAD
database when available.
Definition of the information (information not included in the version window)
Data Definition
Cell Version Version of the cell

Configuration Type Configuration of the DI80
Controller name Name of the controller associated to the
generation of the configuration unit
F8000 Firmware revision Version of the F8000 interface software
F8000 ICR/IVC Index of F8000 bus compatibility :
ICR network compatibility index (major
modification on the network)
IVC configuration version index (modification on
the controller)
FB library version CE2000 library version number
FB library revision CE2000 library revision number
FB library compatibility CE2000 library compatibility number
Generation date Date of generation of the configuration unit
Generation time Time of generation of the configuration unit
Protection Version DI103 protection version
Redundancy addresses version Version of compatibility of the addresses of the
F8000 and S8000 network variables .
Safe mode Cell Loader indicates whether or not the CE2000
R5 (UT129) TRX is configured in safe mode
Type UT Cell Loader displays the CE2000 module type
= UT129 < version M.07.00 or UT150
= UT129 < version M.07.00 ou UT150
= UT129 >= version M.07.00

Data Definition
UT Version CE2000 UT129 version number

UT Revision CE2000 UT129 revision number
UT Compatibility CE2000UT129 compatibility number
Variable addresses version Version of compatibility of the addresses of the
variables of the application
Version Version of the configuration unit
Workspace of generation Name of the workspace associated to the
generation of the configuration unit
If the device does not support at least one configuration unit, the non-significant tabs
are invisible.
Single and redundant C80-75
S8000 tab F8000 tab Hardware tab Program tab
Generation date Generation date Generation date Generation date

Generation time Generation time Generation time Generation time
Workspace of generation Workspace of Workspace of Workspace of
generation generation generation
Version Version Version Version
Controller name Controller name Controller name Variable
addresses version
Cell Version Redundancy
addresses version
Controller name
Tab Misc. tab
Generation date F8000 Firmware

revision
Generation time F8000 ICR/IVC
Workspace of generation
Version
Controller name
Redundant MFC3000
F8000 tab Hardware tab Program tab
Generation date Generation date Generation date

Generation time Generation time Generation time
Workspace of generation Workspace of generation Workspace of generation
Version Version Version
Controller name Controller name Variable addresses version

Cell Version Redundancy addresses version

Controller name
Tab Misc. tab
Generation date F8000 Firmware revision

Version
Controller name
Single and redundant C80-35, Rx3I

Generation date Generation date Generation date

Generation time Generation time Generation time
Workspace of generation Workspace of generation Workspace of generation
Controller name Controller name Variable addresses
version
Cell Version Redundancy addresses
version
Controller name
Tab Misc. tab
Generation date F8000 Firmware revision

Version
Controller name
I/O modules IHR
F8000 tab Hardware tab Program tab Misc. tab
Generation date Generation date Generation date F8000

Firmware
revision
Generation time Generation time Generation time F8000 ICR/IVC
Workspace of generation Workspace of Workspace of
generation generation

F8000 tab Hardware tab Program tab Misc. tab
Controller name Controller name Controller name

Cell Version
Single, redundant CE2000 with and without TRX

F8000 tab Hardware tab Program tab (if Parameters tab
TRX) (if TRX)
Generation date Generation date Generation date Generation

date
Generation time Generation time Generation time Generation
time
Workspace of generation Workspace of Workspace of Workspace of
generation generation generation
Version Version Version Controller
name
Controller name Controller name Controller name
Cell Version Variable addresses
version
Misc. tab Misc. tab Misc. tab Misc. tab

For CE2000 R5 For CE2000 R7 For CE2000 R5 TRX For CE2000 R7
TRX
F8000 ICR/IVC F8000 ICR/IVC F8000 ICR/IVC F8000 ICR/IVC

Type UT Type UT Type UT Type UT
Safe mode
UT Version(*) UT Version(*)
UT Revision(*) UT Revision(*)
UT Compatibility(*) UT Compatibility(*)
FB library version (*) FB library version (*) TRX FB library
version (*)
FB library revision (*) FB library revision (*) TRX FB library
revision (*)
FB library compatibility (*) FB library TRX FB library
compatibility (*) compatibility (*)
(*) from Version M.07.00
DI103
F8000 tab Hardware tab Misc. tab
Generation date Generation date F8000 Firmware Revsion

Generation time Generation time F8000 ICR/IVC
Workspace of generation Workspace of generation Protection Version(**)
Version Version
Controller name Controller name
Cell Version
(**) from version R5 of the DI103
DI80
Misc. tab
F8000 Firmware revision

Configuration Type
GEMSTART
No information available.
DI-OPC
No information available.
In this version, after loading the device, the view may sometimes have to be
updated by changing tabs.
2.2 Tools
CELL LOADER  Tools  Select all Driver Conf ( See §2.2.1)

CELL LOADER  Tools  Select all HW Conf ( See §2.2.1)
CELL LOADER  Tools  Select all Prog ( See §2.2.1)
CELL LOADER  Tools  Select all Parameters Conf ( See §2.2.1)
CELL LOADER  Tools  Settings ( See §2.2.2.)
2.2.1 Select configurations entities
The function selects automatically all the selected configurations of the present
devices and select automatically all the dependent configuration units. The selection
of a checkbox results in the selection of the checkboxes of the entities.
2.2.2 Settings
The first option disables the stop device command during the loading phase for C80-
75 and C80-35 field controllers, and AVR, IHR and SLG devices.
The second option is used to access the Cell Loader debug mode (not possible).

The choice of checkboxes is not memorized; the options are unchecked each time
the Cell Loader is run.
2.3 Display
CELL LOADER  Display  Log

Show or hide the log view
CELL LOADER  Display  Toolbar
Show or hide the toolbar
CELL LOADER  Display  Status bar
Show or hide the status
The status bar is not completely operational.
CELL LOADER  Display  Watch Window
Display the system watch window of the selected equipments, if the equipment has
variables to read and write.
The watch Windows system has a human/machine interface which makes it
possible the user to reach information of the cell and to act on the cell ( See
§Section 10.)
CELL LOADER  Display  Tooltips
Show or hide the tooltips. When the mouse cursor is over an item a description is
given in a tooltip.
2.3.1 Log
Show or hide the log view ( See §2.2.)

CELL LOADER  Tools  Clear Log
The size of the error file is not limited, and its content is deleted only when
you select a previous project version generated by Controcad.
2.3.2 Tooltips
Show or hide the tooltips. When the mouse cursor is over an item a description is
given in a tooltip.

2.4 Producing the Automation Cell Configuration
The entire configuration (hardware and software) of the cell must have been
generated, before the loading and commissioning phases can be executed.
Use the Controcad software to produce the files to be stored into the cell.
The principal operations are:
 Creation in the hardware branch of a controller from a standard configuration,
 Customization of the hardware configuration (addition of input-output boards or
modification of the controller parameters),
 Development of the cell controller and sub-controller programs,
 Generation of the cell code.
To ensure these operations are executed correctly, please refer to the Controcad
User's Manuals.
2.5 Indicators in the Loading Interface Zone
When the mouse cursor is over the communication indicator, click on F1 to have a
description :.
2.5.1 Indicator of presence of the device on S8000
All the devices are accessible (ping on all S8000 interface)

S8000 communication is not operational for the device
None communication on S8000
2.5.2 Indicator of presence of the device on F8000
F8000 communication operational (interface operational) IP communication

possible if supported
F8000 communication operational (interface operational) IP communication
impossible
F8000 communication stopped (interface in configured mode) IP
communication possible if supported
F8000 communication stopped (interface in configured mode) IP
communication impossible
F8000 communication initialized (interface in idle mode) IP communication
possible if supported
F8000 communication initialized (interface in idle mode) IP communication
impossible
No F8000 communication (absent remote device not supporting the IP
communication)
No F8000 communication possible (absent remote device supporting IP

communication)
F8000 communication unknown (unknown F8000 fieldbus operating state )
IP communication impossible if supported and unknown F8000 operating

state
Unknown F8000 communication
IP communication possible for AVR RX3I not remote
Unknown F8000 communication
IP communication possible for remote device
Device not recognized by Cell Loader
2.5.3 Functional indicators of the device
The functional indicators of a device are divided into the 6 categories shown below:
Category Description
Ign. Indicates whether or not a device is recognized by Cell Loader

Appli. Indicates the operating state of the application
M/S Indicates the state (master or standby) of a redundant device
Rdn Indicates the redundancy state for a redundant device
Forcing I\O Indicates the presence of forced values on the input/output
variables in the F8000 sense
Forcing Var. Indicates the presence of forced values on the application
variables
Not all these functional aspects are supported on all the devices.
These indicators are not signaled when the device is simulated by SI80:
When the mouse cursor is over an indicator, click on F1 to have a description:
2.5.4 Indicators associated to Ign. functionality
Device not recognized by Cell Loader
Real device or device simulated by SI80
2.5.5 Indicators associated to Appli. functionality
State of the application is operational

State of the application is cycle to cycle mode
Application state is stopped

Application state is stopped and malfunctioning; startup will be impossible (in
this case, rectify then acknowledge the fault in the device fault table)
State not significant as not supported by the device or device simulated
State unknown as the information enabling the state to be established is
inaccessible
2.5.6 Indicators associated to Rdn functionality
The control function is managed by the redundant device

The control function is managed by both devices
The control function is managed by neither of the two devices
inaccessible
Online modification of the application with transfers of retained variables and
parameters for the MFC3000 equipment or with transfers of the redundancy
variables for C8075,C8035, RX3I equipments.
On line modification of the application with transfers of retained variables and
without transfers of parameters for the MC3000 equipment.
On line modification of the application without transfers of retained variables
and parameters for the MFC3000, or without transfers of the redundancy
variables for C8075,C8035, RX3I equipments
The function indicates that the transfer of the tuned parameter is inhibited
2.5.7 Indicators associated to M/S functionality
Master device
Standby device capable of becoming master
Standby device not ready (typically the standby device is being inserted)
When primary is on the left:
Primary device master
Secondary device standby
When primary is on the left:
Secondary device master
Primary device standby
When primary is shown on the left:
Primary device master
Serious secondary slave device fault.

Secondary device master
Serious Primary slave device fault.
Serious primary master device fault
Secondary device undetermined
Undetermined primary device
Serious secondary master device fault
inaccessible
2.5.8 Indicators associated to Forcing I/O or Forcing Var functionality
I/O : Presence of a forced value on the input-output variables

Var : Presence of a forced value on the internal program variables (voir §7.1)
I/O : No forced value present on the input-output variables
Var : No forced value present on the internal program variables(voir §7.1)
inaccessible
2.5.9 Signification of checkboxes
The checkboxes indicate differences between the configuration of the tool and that
of the actual device.
Signification of synthesis’ checkboxes for devices whose configuration can be stored
from Cell Loader :
The version and the date of all the configuration units to be stored and the
target are identical
The version and/or the date of a configuration unit to be stored and the target
are different
The version data and unit configuration date in a target are unknown (a
device absent, or loss of communication with a device).

Signification of checkboxes for devices whose configuration can be stored from Cell
Loader :
The version and the date of the configuration unit to be stored and the target
are identical
The version and/or the date of the configuration unit to be stored and the
target are different
The version data and unit configuration date in the target are unknown
(device absent, loss of communication with the device).
Absence of configuration in the target
Significance of checkboxes for the DI80 device
The version data and unit configuration date in the target are unknown
(device absent, loss of communication with the device
The DI80 configuration type supplied in the device configuration and the type
of configuration produced from the STAT-IO of the device are the same
The DI80 configuration type supplied in device configuration and the type of
configuration produced from the STAT-IO of the device are different
No checkboxes are displayed for GEMSTART and DI-OPC devices,
Indicators associated to the back-noting of tuned channels (HW entity )
Tuning performed from the ALSPA P80 PLC tool. Back-noting for this
type of tuning is not supported by Cell Loader.
No tuning performed, not supported or simulated by SI80, state
unknown
Indicators associated to the back-noting of tuned parameters (Param entity )
Tuning performed on the program parameters (C80-x5 or CE2000
TRX program), back-noting required to save the tuned parameters in
the current CONTROCAD table
No tuning performed, not supported, unknown state
Signification of checkboxes (voir §2.5.9)
2.5.10 Toolbar
A button is shown as inactive when the associated function is not available for the
current selection (device or driver or application concerned) or when the state of the
controller does not allow the action to be initiated.
When the mouse cursor is over a button, click on F1 to have a description :.
The actions that can be executed from the button bar are described in the table
below
Buttons Associated function
Global run automation cell request

Global stop automation cell request
Global Store automation cell by ETHERNET protocol request
Request to export the configurations from the cell devices to a directory

for the SI80.( See §9.1)
Request for initial Store (by serial link)For C80-75 controllers ( See
§2.7.1.)For MFC3000 controller ( See §2.7.2.)For C80-35 and RX3I
controllers ( See §2.7.3.)
Request to switch the application to RUN state.For a simplex controller (
See §2.12.)For a redundant controller ( See §2.13.)
Request to switch the application to STOP mode : For a simplex
controller ( See §2.14)For a redundant controller ( See §2.15.)
Request to switch the application to cycle to cycle mode ( See §2.17)
Request to execute a cycle of the application in cycle to cycle mode (

See §2.17)
Request to switch the applications on both redundant controllers to RUN
state ( See §2.13.)
Request to switch the applications on both redundant controllers to STOP
state ( See §2.15.)
Request to switch-over a redundant structure, this command is
accessible if and only if the state of the Standby controller is operational
(Rdn State indicator ). In the case of the CE2000 field controller the
switch-over request can be performed even if the Rdn State indicator is
.
However the switch-over request may be refused by the device in the
following cases:
 synchronization fault,
 F8000 exchange fault (loss of update)
Request to back-note the tuning parameters; (See §6.3.2)
Request to clear all the forced values present on a device (See § 7.1)
Request to insert a device on F8000. Insertion of the CE2000 allows the

I/Os and the TRX program of the device to be switched from configured
state to operational state (if the device possesses a TRX application).
Request to update the date and time properties of target MFC3000 cell
controller with date and time of the system, where cell loader is running.
This setting needs to be done on the master equipment and on the stand
by equipment, if it is present.
In case of error in updating system date and time in target MFC3000 cell
controller, error message box is shown to the user.
Request to see the equipment communication properties;

Request to display all the faults of a device On line modification of the

application without transfers;
For C80-x5 and RX3I Controllers: (See § 8.1) .For MFC3000 Controller:
(See §8.2),
Request to display the system tables of CE2000 PLC(See §8.3)
On line modification of application with full transfers. Definition for C80-x5

and RX3I Controllers: (See § 5.1.1) . And operating mode (See § 5.1.2).
Definition for MFC3000 Controller: (See §5.2.1), and operating mode (See §
5.2.2)
On line modification of application with partial transfer. Definition : (See
§5.2.1), and operating mode (See § 5.2.2)
On line modification of the application without transfers Definition for
C80-x5 and RX3I Controllers: (See § 5.1.1) . And operating mode (See §
5.1.2). Definition for MFC3000 Controller: (See §5.2.1), and operating mode
(See § 5.2.2)
Validate the On Line Modified application program Definition for C80-x5
and RX3I Controllers: (See § 5.1.1) . And operating mode (See § 5.1.2).
Definition for MFC3000 Controller: (See §5.2.1), And operating mode (See
§ 5.2.2)
Stop the On line modification of the application Definition for C80-x5 and
RX3I Controllers: (See § 5.1.1) . And operating mode (See § 5.1.2).
Definition for MFC3000 Controller: (See §5.2.1), And operating mode (See
§ 5.2.2)
Run transfers of tuning variables from Master to Slave. Operating mode
for C80-x5 and RX3I Controllers: (See §6.2.1) .Operating mode for
MFC3000 Controller: (See §6.2.2),
Stop transfers of tuning variables from Master to Slave. Operating mode
for C80-x5 and RX3I Controllers: (See §6.2.1) .Operating mode for
MFC3000 Controller: (See §6.2.2)
2.6 Loading/Reading the Firmware Version Controller
2.6.1 C80-75
2.6.1.1 Loading firmware
Cell Loader must be closed during the loading of the EX7 board or the
FBC70 board firmware.
 Loading the EX7 board firmware
This operation is necessary only once; the software is stored permanently in the
IC697CMM 742 interface board.
 Loading the FBC70 board firmware

FIP FBC70 interface board .
The loading procedure of these two firmware packages is described in the document
[GUICHGTCCAD].
2.6.1.2 Reading the FBC70 board version on target
The "F8000 firmware revision" is read in the target and available via Cell Loader in
the "MISC" tab of the version control zone. This information is available when the
selected device is configured; otherwise use the procedure described in the
[GUICHGTCCAD].
Reading the C80-75 firmware revision on target
2.6.2 MFC3000
2.6.2.1 Loading MFC3000 firmware
MFC3000.
The firmware loading procedure is described in the document [GUICHGTCCAD].
2.6.2.2 Reading the MFC3000 version on target
The version of the components constituting the MFC3000 software can be read via
the maintenance server accessible via the RAS (see following paragraph)

MFC3000 Components Versions
2.6.3 C80-35 and RX3i Field Controllers
2.6.3.1 Loading/Reading the C80-35 SLG AVR IHR Firmware Revision (external to Cell
Loader)
FIP FBC30 interface board.
2.6.3.2 Reading the FBC30 Firmware Revision on Target (to be confirmed for RX3I)
The F8000 firmware revision is read in the target and made available via Cell
Loader in the "Misc" tab in the version control zone. This information is available
when the selected device is configured, otherwise use the procedure described in
the [GUICHGTCCAD].

Reading the C80-35/RX3I firmware revision on target
2.6.4 CE2000
Loading the firmware

CE2000.
Reading the firmware revision on target
The firmware revision cannot be read from Cell Loader. See the procedure
described in the [GUICHGTCCAD].
2.6.5 DI103
Loading the firmware

DI103.
Reading the firmware revision on target
The firmware revision cannot be read from Cell Loader. See the procedure
described in the [GUICHGTCCAD].
2.7 Loading the Initial Configuration
2.7.1 C80-75 (by serial link)
The first time the device configuration is stored, the hardware configuration must be
stored by serial link. We emphasize that it is not possible to store a device by
Ethernet link if its IP address is different from that defined in the configuration of the
device.
Loading by serial link is always accessible , the connection can be established

via the COM1, COM2, COM3 or COM4 serial ports. Loading by serial link does not
use the SNP ID identifiers, which makes the use of multi-points impossible.

It is advisable to perform the following operations in order to avoid creating
conflicting IP addresses or conflicting F8000 fieldbus exchanges due to
incompatibilities of configuration :
1. Disconnect the F8000 fieldbus from all the C80-75, C80-35, RX3I or CE2000
field devices (on both the primary and secondary if the device is redundant).
2. Disconnect the Ethernet network from all the RX3I devices (on both the primary
and secondary if the device is redundant).
3. Connect the serial link between the COM1 port (or COM2) of the Controcad
station and the 15-point connector on the front of the CPXxxx (c80-75 Primary) .
4. Run Cell Loader (See § 1.5)
5. Select the C80-75 device (the primary)
It is unnecessary to select of the configurations entities ; the HWC and F8000
configurations are stored automatically .
6. Store the configuration by the C80-75 serial link by means of
7. Reconnect the F8000 fieldbus from the C80-75 stored
Check, after the store procedure, that the device is seen as shown below :
If it is not successful, check the controller properties that the access route to the
F8000 fieldbus is defined, by selecting the on the controller. See§ Properties of
the C80-75 cell controller .
8. Repeat actions 5 to 7 on the secondary C80-75
2.7.2 MFC3000
The Initial loading is accessible when the MFC3000 has no configuration. Although
Cell Loader displays only one interface for a redundant MFC3000, the operation
must be performed physically on both units, the primary device first then the
secondary device.
When the MFC3000 is delivered, it has a FIXED IP address 195.0.0.128
Do not forget that this operation is only valid when the MFC3000 has never
been configured; after this, it can no longer be accessed through the
address 195.0.0.50 and the new configured address must be used.
1. Power off the secondary MFC3000 device

2. Disconnect the primary MFC3000 from the F8000 fieldbus
3. Power up the primary MFC3000 device

4. Select the primary MFC3000 device
It is unnecessary to select configurations entities; the HWC configuration is
stored automatically.
5. Store the initial configuration of the MFC3000 by clicking on the icon after
having first selected the ENET port then the primary device
6. Repeat actions 1 to 5 on the secondary MFC3000
Check, after the Store procedure, that the device is seen as shown below:
If it is not successful, check the controller properties that the access route to the
F8000 fieldbus is defined, by selecting the on the controller. (voir §2.8).
2.7.3 C80-35 and RX3i Field Controllers (by serial link)
During the first loading of the cell configuration, the Hardware configuration must be
loaded by serial link. We emphasize that it is not possible to Store a device by
Ethernet link if its IP address is different from that defined in the configuration of the
device.
1. If the cell contains RX3I devices, add the network connection for access to the
Ethernet network of the RX3I on the PC Cell loader :

Connection of the RX3Icontroller
The IP address and the sub-network mask of each of the RX3I controllers must be
added in the network connection parameters of the Ethernet coupler on the CCAD
PC.
Configuration of ‘RX3i’ network
 Open Network properties of 195.5.0.0 network : Start  control panel 
Network  properties (on S8000 network)

The next window opens
 Click on Advanced

 Click on Add (on the top window)

 Write the Rx3i network with address 63

 Click on Add

The next window open, and check that the new address of RX3i network is taking
into account
 For certain PC, its necessary to ‘Restart’ the PC

Route configuration of RX3i network
 Open ‘DOS’ window and check the nest command (for the up example)
 Route add –p 196.5.238.0 mask 255.255.255.0 196.5.238.63
If the C8035 RX3i connection is not possible, put in off/on power, then restore the
configuration by serial link.
Loading by serial link is always accessible , the connection can be established

via the COM1, COM2, COM3 or COM4 serial ports. Loading by serial link does not
use the SNP ID identifiers , which makes the use of multi-points impossible.
The following operations must be performed in order to avoid creating conflicting IP
addresses or conflicting F8000 fieldbus exchanges due to incompatibilities of
configuration:
1. Disconnect the C80-35/RX3I from the F8000 fieldbus and the RX3I from the
Ethernet network
2. Connect the serial link between the COM1 port (or COM2) of the Controcad
station, and the 15-point connector on the front of the CPUxxx (e.g. CPU360)

3. Select the C80-35/RX3I device (on both primary and secondary) then Store the
configuration via the C80-35 serial link by selecting
4. It is unnecessary to select of the configurations entities ; the HWC and F8000
configurations are stored automatically .
5. Reconnect the F8000 fieldbus to the C80-35/RX3I and the Ethernet network to
the RX3I
6. Check, after the loading procedure, that the device is seen as shown below :
If connection with the C80-35/RX3I is impossible see the (see §2.8.3).
2.8 Properties of a Device
For C80-75 controller: ( See §2.8.1.)

For MFC3000 controller : ( See §2.8.2.)
For C80-35 and RX3i Field Controllers : ( See §2.8.3.)
2.8.1 C80-75
Properties of the C80-75 cell controller

The route must be defined by a shell command. This command is described in the
cell controller properties, by right clicking after selecting the C80-75 controller.

route add –p <@F8000 fieldbus destination> mask <F8000 fieldbus
mask> <@IP S8000 gateway>
where
–p: indicates that the route is saved even after a reset of the machine
<@F8000 fieldbus destination>: is the address of the F8000 fieldbus to be
reached
<F8000 fieldbus mask>: is the mask of the F8000 fieldbus (ex 255.255.255.0)
<@IP S8000 gateway>: is the IP address of the S8000 interface that processes the
routing. When the device is single, this address is the fixed IP address . When the
device is redundant, this address is the redundant IP address .
The C80-75 cell controller supplies the routing function to remote devices via the
F8000 fieldbus. For this function to operate, S8000 and F8000 communications with
the cell controller must be correct.
Click on
A DOS window displays the result of the “ping” commands ; the device must
respond on all the IP addresses.
If the device does not respond on one of the addresses, check the following points:
 Check the connection of the Ethernet and FIP cables on the device,
 Check the connection of the Ethernet cable on the Controcad PC,
 Check that the CPU type corresponds to the type configured,
 Check the routing table of the Controcad PC, and if necessary define the route
for access to the F8000 fieldbus ( See §2.7.2.)
If communication is still not possible:

 Disconnect and Reconnect the F8000 fielbus on the C80-75.
 Power off the C80-75 rack, disconnect the CPU battery, wait several seconds,
reconnect the battery then power up the rack.
 ReStore the Hardware configuration by serial link.
If communication is correct:
 Close Cell Loader
 Close the ALSPA P80 PLC P80 if open
 Check that none of the following processes is active in the task manager:
WB.exe, hctsrv.exe, snpsrv.exe
 Close the Explorer manually rather than by the task manager .
Finally execute the loading procedure after a modification of the configuration.

(see §2.9.1)
2.8.2 MFC3000
Properties of the MFC3000 cell controller

The MFC3000 cell controller supplies the routing function to remote devices via the
F8000 fieldbus. For this function to operate, S8000 and F8000 communications with
the cell controller must be correct.
1. Select the MFC3000 device, then right click to select the Properties menu of
the device
2. Click on
.A DOS window displays the result of the “ping” commands ; the device must

If the device does not respond on one of the addresses, check the following points:
 Check the Ethernet and FIP cable connections on the device

 Check the Ethernet cable connection on the Controcad PC
 Check the routing table of the Controcad PC, and if necessary define the route
for access to the F8000 fieldbus ( See First load of a cell)
 Power cycle the MFC3000

 Close the Explorer manually rather than by the task manager
Finally execute the loading procedure after a modification of the configuration
(see §2.9.1)
Properties of a C80-35/RX3I device

To ensure that communication with the C80-35/RX3I device is functioning correctly,
follow the procedure detailed below :
1. Select the C80-35/RX3I device, then right click to select the Properties menu
of the device.
2. For RX3I device if 'Write configuration unit to flash memory' option is checked,
then all three configurations are written into the device flash memory.
3. <Context Help Cell Loader> Click on

A DOS window displays the result of the “ping” commands ; the device must
If the C80-35 device does not respond on one of the F8000 addresses, check the
following points:

 Check the F8000 cable connection on the device,
 Check the F8000 cable,
 Check that the F8000 configuration has not been refused by the device .
 Check that the Cell controller responds correctly to the ping on its redundant IP
address (See § 2.6.3).
 Check the F8000 Network route
 Open Dos Windows
 >route print
 Display : 195.5.238.0 255.255.255.0 195.5.167 (in the example above)
If the RX3I device does not respond on one of the S8000 addresses, check the
following points:
 Check the F8000 cable connection on the device,
 Check the S8000 cable,
 Check that there are no faults signaled by the device

 Check that a communication port has been created on the PC Cell Loader
with the IP address of the RX3I (See above)
 Check the F8000 routes table (in DOS window >route print)
 Power off the C80-35/RX3I rack, disconnect the CPU battery, wait several
seconds, reconnect the battery then power up the rack.
 Reload the Hardware configuration by serial link.
 Close the Explorer manually rather than by the task manager .
Then follow the procedure (see §2.9.2).
Note : When the configuration is stored by serial link, the F8000
configuration of the device is deleted by loading the hardware
configuration of the ClearFBC30xxx folders; the configuration
specific to the device is then stored.
2.9 Loading the Configuration
2.9.1 C80-75 and MFC3000
After the configuration is generated from CONTROCAD and the initial loading has
been performed by serial link, the configuration can be stored by Ethernet link.

1. Check the configuration entities to be stored, then click on the command
The following C80-75 configuration units can be stored by Ethernet link:
 HWC, F8000, S8000, PROG and PARAM*
The following MFC3000 configuration units can be stored by Ethernet link:
 HWC, F8000, PROG and PARAM*
The dependences between the configuration units are as follows:
 the loading of the PROG and PARAM* units is independent from the other
units.
 the F8000, S8000 and HWC units are dependent on each other. None of
the 3 units can be stored without reloading the others.
*if the parameters are present in the CONTROCAD configuration.
2. The application must be stopped.
The occurrence of an error is signaled in the log view.
If an error occurs during one of the steps of the loading procedure, the procedure
is interrupted and subsequent loading operations are not processed.
Responding to a loading error
 Check communication with the cell controller: See § 2.6.3 or § 2.7.2.
 Acknowledge the faults on the primary and secondary devices, (See § Section
8)
 ReStore the configurations in the primary and secondary devices
An error may be signaled during the full loading procedure (Program and
Hardware Configuration). (See § 3.1.2).
Note : The program of the secondary C80-75 is stored via the folder of
the primary C80-75 as the redundancy mechanism uses
checksums to ensure that the programs are identical. If the folder
of the secondary C80-75 is used, the checksums are different
even if the programs are identical.
2.9.1.1 Loading a MFC3000 Configuration with new IP addresses in a MFC3000

containing a configuration
For this operation its necessary to

 Disconnect the primary MFC3000 from the F8000 fieldbus
 Power off the secondary MFC3000 device
1. With Controcad, open ‘MFC3000 Maintenance server’ on ‘Primary’

2.
3. With ‘Administrative tools’, log-in in ‘admin’ and password ‘pcxadmin’
4.
5. Modify the cell IP addresses, with addresses of the new cell
6.

With the new name of the cell
for example :
 195.0.0.1 to 195.0.0.4 and 195.10.0.4
 195.0.0.65 to 195.0.0.68 and 195.10.0.68
 195.0.0.129 to 195.0.0.132 and 195.10.0.132
4. select ‘and Reboot’ and click on ‘Validate’
7. With Controcad, open ‘MFC3000 Maintenance server’ on ‘Primary’ of NEW

Cell
8. Select ‘Restart’ of MFC3000 ‘Primary’ with ‘MFC3000 Maintenance server’
Admin tools  Configuration  Firmware Update  Restart
9. With “Cell Loader” select ‘HWC’, ‘F8000’ and ‘PROG’ configuration of PCS
Cell then click on the command .

10. Power up the Secondary MFC3000 device
11. Open ‘MFC3000 Maintenance server’ on ‘Secondary’ on ‘Old Cell’
12. Modify the cell IP addresses, with addresses of the NEW cell (see 3) ‘Reboot’
and ‘Validate’
13. Connect on ‘MFC3000 Maintenance server’ on ‘Secondary’ on ‘New Cell’
14. Made a ‘Restart’ on MFC3000 ‘Secondary’ with ‘MFC3000 Maintenance
server’
Admin tools  Configuration  Firmware Update  Restart
15. Connect FIP F8000 mediums on the cell
16. Store the rest of the Cell

2.9.2 C80-35 and RX3I Field Controllers
After the configuration is generated from CONTROCAD, it can be stored by Ethernet

link.
For C80-35, SLG, AVR devices, if the program is to be stored and if the version of
the variable addresses in the new program supplied by the "Variable address
version" below the CCAD tab is different from that in the target device, the forced
values on the device are deleted.
Check the configuration entities to be stored, then click on the command . The
application must be stopped.
The following C80-35/RX3I configuration units can be stored by Ethernet link:
 HWC, F8000, PROG and PARAM*
The dependences between the configuration units are as follows:
 the PROG and PARAM units are stored independently of each other,
 The F8000 and HWC units are dependent on each other. Neither of the 2
units can be stored without reloading the other.
A the end of the loading procedure, the interface is put into operational state
independently of the state of the cell controller.
* The parameters of the SLG and AVR devices cannot be stored by Cell Loader;
use the ALSPA P80 PLC Tool instead (store Global Vars). The IHR device has
no parameters.
Note : The program of the secondary C80-35/RX3I is stored by means of
the folder of the primary C80-35/RX3I as the redundancy
mechanism uses checksums to ensure that the programs are
identical. If the folder of the secondary C80-35/RX3I is used, the
checksums are different even if the programs are identical.
If an error occurs during loading on an RX3I device, an additional log containing
the error is supplied by Machine Edition; the name of this log is shown in the Cell
Loader log. This xml format file <controller_name>Log.xml is located in the
controller directory.
The hardware configuration of a redundant C80-35 device must be stored
separately: loading the primary device first then the secondary device.

 Check communication with the device: See § 2.8.
 Acknowledge the faults on the primary and secondary devices, See § Section
8.
 Reload loading the configurations in the primary and secondary devices
 Specific case of the Rx3I controller:

This device implements a link dedicated to the Ethernet network to receive the
configuration; check that the Ethernet module of your PC has the IP address
of the Rx3I Ethernet module.
2.9.3 CE2000
After being generated from CONTROCAD, the configuration must be stored by the
Ethernet link. If the device is redundant, the configuration of the standby is stored by
the master device.
The device will be inserted automatically and the application will be started if the cell
controller application is running.
1. Check the configuration entities of the device to be stored
The following CE2000 configuration units can be stored by Ethernet link:
 HWC, F8000 for non-TRX CE2000 devices
 HWC, F8000, PROG, PARAM for TRX CE2000 devices
The configuration units of the device are inter-dependent.
2. Then click on the command .

3. For a CE2000 TRX configured in safe mode in the target, the application must
be shut down by inputting the password entered during the configuration of
this device by the Administrator or the Configurator.
Special case of a CE2000 in safe mode:
If the password is the old password hard configured in the Controcad tool, the
TRX application will be stopped and the F8000 coupler of the CE2000 will be
shut down.
2.9.4 DI103
After being generated from CONTROCAD, the configuration must be stored by the
Ethernet link.
The HWC and F8000 configuration units of the DI103 can be stored by
Ethernet link.
The configuration units of the device are inter-dependent.
2. Then click on the command

The device will be inserted automatically if the cell controller application is
operational.

If an error occurs during one of the steps of the loading procedure, the
procedure is interrupted and subsequent loading operations are not
processed.
2.10 Loading after Modifying the Controller Application
2.10.1 C80-75 and MFC3000
After the configuration is generated from CONTROCAD, the programs are stored by
Ethernet link.
When the on-line modification buttons are active ( , , ) the program can
be stored by executing the on-line modification loading procedure, otherwise :
1. Select the entities marked by a red cross or a question mark
2. Then select
3. The target application must be stopped
 Check communication with the cell controller: See § 2.8
 Acknowledge the faults on the primary and secondary devices, (see § Section
8)
 ReStore the programs in the primary and secondary devices
When the on-line modification indicators are active ( , ) the program can be
stored by following the on-line modification loading procedure. See § Section 5.
1. Check communication with the device:See § 2.8
2. Acknowledge the faults on the primary and secondary devices, See § Section
8
3. Reloading the programs in the primary and secondary devices
2.11 Loading after Modifying the Tuning Parameters
2.11.1 C80-75
After the configuration is generated from CONTROCAD, the parameters are stored
by Ethernet link. On-line modification of tuning parameters with M/S transfers
stopped is not available for the C80-75.

The tuning parameters of a device are stored by updating the parameters of the
target device with the parameter values of the CONTROCAD configuration to be
stored.
The parameters of the standby are periodically updated on the basis of the
parameters of the master via the redundancy link.
1. Check the configuration entities of the device to be stored,
2. When the C80-75 device is redundant, the parameters of the master and
standby C80-75 are stored in accordance with dependency requirements.
3. Then select
4. The target application must be stopped
The occurrence of an error is signaled in the log file.
 Check communication with the cell controller: See § 2.8.
 Acknowledge the faults on the primary and secondary devices (See § Section
8).
When a problem appears, a byt of the parameters may have been been
updated. It is consequently advisable to reStore the parameters before
starting the device.
2.11.2 MFC3000
The function is not operational for the MFC3000 device.
After being generated from CONTROCAD, the configuration is stored by Ethernet

link.
The tuning parameters of a C80-35/RX3I device (except SLG, AVR and IHR) are
stored by updating the parameters of the target device from the parameter values of
the CONTROCAD configuration to be stored.
The parameters of the standby are periodically updated from the parameters of the
master via the redundancy link, unless this function is inhibited.
When the C80-35/RX3I device is redundant, the parameters of the master and
standby devices are stored in accordance with dependency requirements.
2. Click on the command

3. The application must be stopped

When a problem occurs, some of the parameters may be modified. It is
consequently advisable to reload the parameters before starting the device.
 Check communication with the device: See § 2.8.
 Acknowledge the faults on the primary and secondary devices, See § Section
8.
 Check that the parameters on the target device can still be listed (generation
version of the cell is still stored in CONTROCAD).
 Reload the programs in the primary and secondary devices
2.12 Running the Application
The application can only be started up if the device C80-75,MFC3000,C80-35, SLG,

AVR or IHR is in a state that allows startup. When the device is redundant, this
command can be used to start the application either on the master or standby
device, which is not possible on a MFC3000 device.
For the CE2000 TRX application, the startup request is processed by the TRX R7 or
TRX R5 CE2000 and requires the user to supply a password. The redundant
characteristic of a CE2000 is transparent with regard to the startup of the CE2000
application.
1. Select the device to be started,
2. Then select
For a C80-35, SLG or AVR device this icon is accessible if the application is
stopped or in cycle to cycle mode:
For an IHR, MFC3000 and CE2000 TRX devices this icon is accessible if the
application is stopped:
Running the application can result in a C80-x5 master/standby switch-over if the

device is redundant.
Updating the state of the device can take several seconds.
Starting the C80-75 cell controller application starts subsidiary devices such
as the CE2000 and potentially the DI103. Running the application can
result in a C80-75 master/standby switch-over if the device is redundant.
The C80-75 application startup report only covers the C80-75 device.

When the device receives the startup request, the request can be rejected if for
example there are any unacknowledged blocking faults.
Responding to errors
 Acknowledge the faults on the device, (See § Section 8)
 Execute the procedure to be followed in case of error. (See § Section 4).
2.13 Running the Application on a Redundant Device
The startup of a redundant device consists in asking each device C80-

75,MFC3000,C80-35, SLG, AVR or IHR device to start its application.
In order to preclude any unnecessary switchovers during the startup of the
applications on a redundant C80-x5 device, the application on the master C80-x5
device is started before that on the standby device.
The MFC3000 application can only be started if the device is in a state that allows
startup. The startup request is run on both units of the redundant MFC3000 device;
it is not possible to start the application on the Master or Standby device
independently.
1. Select the device to be started,
2. Then select
This icon is accessible if both applications are stopped:

Starting the C80-75 cell controller application starts subsidiary devices such
as the CE2000 and potentially the DI103. The C80-75 application startup
report only covers the C80-75 device.
When the C80-75 receives the startup request, the request can be rejected if for
example there are any unacknowledged blocking faults.
If for any reason a subsidiary device is not started by the C80-75 cell controller,
the fault is signaled in the C80-75 fault table.
 Acknowledge the faults on the device, See (§Section 8).
The application on the standby C80-75 device can be shut down by the
master application in the event of incompatibility of program. See the
paragraph concerning on-line modification § Section 5.

2.14 Stopping the Application
The application can only be stopped if the device is in a state that allows it to be
stopped. The stop request is processed by the C80-75 device selected. When the
C80-75 device is redundant, this command can be used to stop the application
independently on the master or standby device, which is not the case for a
MFC3000 controller.
Stopping the application can result in a master/standby C80-75 switch-over if the
device is redundant.
For the CE2000 TRX application, the stop request is processed by the selected TRX
R7 or TRX R5 CE2000 (safe mode or not) (*) and requires the user to input a
password. The redundant characteristic of a CE2000 is transparent with regard to
stopping the CE2000 application.
(*) Note: The function of stopping the application is operational for a non-TRX
configuration being stored, in order to be able to stop the target TRX applications
before loading the CE2000.
1. Select the device to be stopped,
2. Then select
This icon is accessible if the application is in cycle to cycle or real time mode:
For an MFC3000 and IHR device this icon is accessible if the application is
stopped:

When the C80-75 receives the stop request, the request may not be processed
after, for example, a problem of internal overflow.
If the application remains operational, a message indicates that the application
has not been able to stop.
If the request is acknowledged negatively, the sequence is aborted and an error
message signals the problem.
 Acknowledge the faults on the device, (See § Section 8).
2.15 Stopping the Application on a Redundant Device
The application can only be stopped on both devices if both devices are in a state
that allows them to be stopped.

Stopping a redundant device consists in asking each device to stop its application.
Following the same principle as that for stopping a application, the stop request is
processed by each device.
In order to prevent any unnecessary switch-over while stopping applications on a
standby device, the application is stopped on the standby device before the
application on the master device.
1. Select the redundant device to be stopped (master or standby),
2. Then select
This icon is accessible if both applications are in cycle to cycle or real time mode
independently of each other:

When the device receives the stop request, the request may not be processed
following, for example, a problem of internal overflow.
If the master device remains operational, the stopping of the standby is not
processed and an error message signals the anomaly. The choice of not stopping
the standby is justified by safety requirements. If the operator still wishes to stop
the standby device, he must issue an explicit request to the device.
2.16 Switching Over a Redundant Device
The switch-over is processed exclusively by the master device. However, the

request is processed independently of the master or standby device selected by the
operator.
When the device is redundant, the switch-over is only possible if the device is in a
state that allows the switch-over.
The switch-over is processed by the CE2000 R7 or R5 by means of a CE2000 TCP-
IP/FIP-S switch-over message.
1. Select the device (master or standby) to switch over,
2. Then select
This icon is accessible only if Rdn State is in the one of the following states:
, , , , .

For the CE2000 TRX, this icon is accessible only if Rdn State is in the one of the
2 following states: ,
and if the application is operational
When the CE2000 signals a consumed TRX ComV fault, the Rdn State is
ORANGE; the switch-over can nevertheless go ahead. In this case operator
confirmation is requested to enable the switch-over command to be transmitted to
the device. The CE2000 can however refuse the command if other faults are
present:
 Time sync fault on the standby PU
 Total loss of F8000 activity on the standby PU
 Consumed ComV I/O fault on the standby PU
3. The occurrence of an error is signaled in the log view
 Acknowledge the faults on the device (See § Section 8).
 Execute the procedure to be followed in case of error, (see § Section 4).
2.17 Switching to Cycle to Cycle Mode
The request to switch to cycle to cycle mode is operational for C80-75,C80-35,

RX3I, SLG or AVR controller application if the current mode is real time or stopped.
When the device is redundant, this command is only executed on the selected
primary or secondary device, independently of the Master/Standby state.
1. Select the device (master or standby in the case of a redundant device) to be

switched to cycle to cycle mode
2. Then select
This icon is accessible if the state of the application is stopped or real time:

3. To stop cycle to cycle mode without stopping the application, restart the
application .
message signals the problem

2.17.1.1 Executing a Cycle
The request to switch to cycle to cycle is operational if the current mode of the
application is in cycle to cycle mode.
When the device is redundant, this command is only executed on the selected
primary or secondary device, independently of the Master/Standby state.
1. Select the device (master or standby in the case of a redundant device),
2. Then select
This icon is accessible if the application is in cycle to cycle mode:
The number of cycles executed is visible in the system information zone,

select CELL LOADER  Display  Watch Window
in the General tab "Steps since start of step by step"
The value is equal to 1 during the switch to cycle to cycle mode then is
incremented by 1 on each cycle execution.
3. The occurrence of an error is signaled in the log view .
message signals the problem.
2.18 Inserting a Device
2.18.1 C80-35 and RX3i field controllers
The request to insert a C80-35 , SLG, AVR or IHR device is issued from Cell Loader
after stopping the F8000 interface (stop command from ALSPA P80 PLC).
1. Select the device to be inserted (master or standby),
2. Then select
This icon is only accessible if the interface is in configured state (mode=
CONFIGURE=2).

If the device does not go operational, a message indicates that the device has
not been inserted.
2.18.2 CE2000
The CE2000 device must be inserted when the device is powered up with a
consistent configuration and when the cell controller application has been running
for more than one minute. During the startup of the application on the cell controller,
the CE2000 devices managed are inserted automatically and the TRX applications
are started automatically. The redundant characteristic of a CE2000 is transparent
as regards the CE2000 insertion procedure.
1. Select the device to be inserted,
2. Then select
CONFIGURE=2).
not been inserted.
2.18.3 DI103
The request to insert a DI103 device is necessary when the device is powered up
with a consistent configuration and when the application of the ES cell controller has
been running for more than one minute. During the startup of the cell controller
application, the DI103 devices managed are inserted automatically.
1. Select the device to be inserted,
2. Then select
CONFIGURE=2).
not been inserted.

2.19 Standalone RX3i Controller
A standalone RX3I controller behaves in the same way as the RX3I field controller.
2.20 DI80
The configuration of the DI80 is not stored from Cell Loader. However after reading
the STATE of the device, then the CONTROCAD configuration, the following data is
updated:
 The state of the device: See § 2.5.1.
 Checkboxes of the configuration entities: See § 2.5.9.
 MISC. tab: See § 2.1.5.
The DI80 device has an IP address. This address is not used to process the setup
of the device, but to run a specific calibration tool.
Loading/reading the DI80 Firmware Revision
DI80.
The F8000 firmware revision is read in the target and is available to Cell Loader
in the "MISC"" tab in the Version Control Zone. This information is available when
the selected device is configured, otherwise use the procedure described in the
[GUICHGTCCAD].
Reading the DI80firmware revision on target
2.21 GEMSTART
The GEMSTART configuration is not stored from Cell Loader. However by first
reading the STATE of the device then the CONTROCAD configuration, the state of
the device is updated: See § 2.5.1.
The GEMSTART device has an IP address. This address is not used to process the
setup of the device, but to run a specific calibration tool.

2.22 DI-OPC
The DI-OPC configuration is not stored from Cell Loader. No presence indicators
are updated for this device.

Section 3 Full Loading on the C80-75 and MFC3000 Cell
After loading the Initial configuration by serial link, the cell is ready to be stored by
the Ethernet link following the procedure described in this chapter.
3.1.1 Rule for Selecting the Configuration Entities
The indicators of the configuration entities to be stored are shown by a red cross
or a question mark or if the device is present on F8000.
When the user selects a configuration unit checkbox. Cell Loader analyzes the inter-
dependence that exists between this configuration unit and the others. If the
configuration unit selected is linked to one or more configuration units, the
configuration units in question are also selected.
The checkboxes relative to programs and parameters do not interfere with the other
indicators and are therefore controlled exclusively by the user (see §2.5.9)
The configuration entities can be selected :
CELL LOADER  Tools  Select all Driver Conf.
CELL LOADER  Tools  Select all HW Conf.
CELL LOADER  Tools  Select all Prog Conf.
CELL LOADER  Tools  Select all Parameters Conf.
 or by selecting the checkboxes entity by entity from the device state window.
3.1.2 Loading a Cell without Adding a Device
The following actions are applicable for a cell ready to be stored by Ethernet link
whose code has been generated on all the cells and where no device has been
added in the hardware configuration.
1. Check the entities to be stored (entities with the symbol ),
The HW and F8000 configuration cannot be stored onto both units of a
redundant C80-35 at the same time: load the configuration of the primary
first then load the secondary in a second phase.
2. The applications must be stopped:
 Allow Stop command without confirm message during the loading phase
(CELL LOADER  Tools  Settings).
Or
 Stop the application when requested
3. Click on the Reload by Ethernet link command .

The command is executed by increasing order of the F8000 subscriber number.

The cell controller slave F8000 devices (CE2000, DI103 etc.) are inserted if the cell
controller application of the master C80-75 or the MFC3000 is in operational state
(real time or cycle to cycle mode).
If problems occur during the reloading procedure, the loading procedure will
terminate or will be aborted. The result of the loading is transmitted to the operator,
with an indication of one of three possible cases:
 loading terminate successfully
 loading terminated with error (please refer to the log view)
 loading aborted (please refer to the log view)
An error may be signaled during full loading (Hardware Configuration and
program) of a C80-75 on configuration of a device managed by the cell
controller (CE2000, DI103). This is due to the fact that the C80-75
reinitializes after loading the Hardware configuration, and is not ready to
manage the remote devices. In this case, acknowledge the faults then
continue the subsequent loading having unchecked the correctly stored
entities (green checkbox). The initialization time depends on the
configuration. So you need to load the Conf-HW-drivers at first and the
program-parameters after.
 Reload the configuration by following the steps indicated below
 For other errors, please refer to the individual loading procedures of the
devices outlined in previous chapters.
 If an error occurs during loading on an RX3I device, an additional log
containing the error is supplied by Machine Edition; the name of this log is
shown in the Cell Loader log. This file in xml format
<controller_name>Log.xml is located below the controller directory.

Section 4 Startup/Shutdown of C80-75 and MFC3000 Cell Devices
The following devices can be started and stopped by Cell Loader when the master
cell controller device is operational:
 C80-75 (primary and/or secondary)
 MFC3000 (primary and secondary)
 C80-35 - SLG - AVR - RX3I (primary and/or secondary)
 I/O modules IHR
 CE2000 R5 TRX (primary and secondary)
 CE2000 R7 TRX (primary and secondary)
The stop/start sequence is based on the stop/start procedures of the devices
described in previous chapters.
 The run command of the cell is executed via
 The stop command of the cell is executed via

Stopping or starting the cell opens the 'Stop/Run Cell Interface' dialogue box :
 Which devices are present in the list?
Only devices whose application is operational for , and devices whose

application is stopped for .
 Modify the order of the list by Drag and Drop
Select the device to be moved by means of the mouse, then move it by a left
click. The Start/Stop commands will be transmitted to the devices in the order
selected.
It is not possible to move a device in the last position.
CELL LOADER imposes no restrictions on the stop/start order of the
redundant devices. The standby device can thus be started before the
master or the master device can be stopped before the standby. This
results in a switch-over in redundant devices.

 Interruption of the stop/start sequence
The OK button validates and executes the stop / start sequence , the Cancel
button quits the dialogue box without performing any action.
A stop/start sequence that is in progress cannot be interrupted.
 Special case of the CE2000 TRX and DI103 devices:
These devices are started by Cell Loader or by the C80-75/MFC3000 cell
controller in accordance with the order selected in the list:
 The C80-75 PLC/MFC3000 is placed before the CE2000 TRX ( R5 or R7 )
or DI103:
the CE2000 and DI103 will be started by the C80-75 PLC cell controller
 The CE2000 TRX (R5 or R7), DI103 is placed before the C80-75
PLC/MFC3000: the CE2000 and DI103 will be started by Cell Loader.
 The application of the C80-75 PLC/MFC3000 is operational and is therefore
not in the list:
CE2000 and DI103 will be started by Cell Loader.
If a problem occurs during any of the device stop or start sequences, the
sequence is interrupted.
If a problem occurs during the stop or start sequence of a master device, the
command is not transmitted to the standby device for safety reasons. The
operator can do this by executing an explicit request on the device.
If the application Start/Stop order fails to execute on a device…
 For a C80-75, check that the switch on the CPX module is set to "Run with
outputs enabled".
 If HCT connection errors are signaled in the log view., restart the operation.
 Check the device fault table for error messages.
 Acknowledge the message (on the master in the case of a redundant device)
and redo the Start/Stop. (See § Section 8).
 If necessary Re-running Cell Loader
Check that none of the following processes is active in the task manager:
Close the Explorer manually rather than by the task manager .
 If necessary power up the cell controller:
 switch over the cell controller, then power off and power up the new
standby
 switch over the cell controller device then power cycle the new standby so
that the two devices are powered up.
The application on the standby device can be shut down by the master
application in case of incompatibility of program. (See § Section 5).

Section 5 On-line Modification of the Controller Application
On line modification definition for C80-x5 and RX3I Controllers : (See § 5.1.1) and
operating mode (See § 5.1.2).
On-line modification for MFC3000 Controller: (See §5.2.1) and operating mode (See §
5.2.2)
Cancel the line modification definition for C80-x5 and RX3I Controllers : (See § 5.1.1)
and operating mode (See § 5.1.2).
Cancel the On-line modification for MFC3000 Controller: (See §5.2.1) and operating
mode (See § 5.2.2)
5.1 On-line Modification of the C80-x5-RX3i Controller Application
5.1.1 Definition
The operation of modifying the controller application on-line takes advantage of the
redundancy of the C80-X5 controllers to put a new version of the controller
application into service without losing control and oversight of the process.
Before generating the CONTROCAD configuration in order to execute an
on-line modification, it is advisable to read the introduction to on-line
modification in the document [GUICHGTCCAD].
The program stored in the equipment should have the “Allow incompatible
Online Modif” parameter set to be able to do an on-line modification without
transfer.
The program to be load in the equipment should have generated for on-line
modification without transfer.
On-line modification with transfer
On-line modification with transfer can only be executed if the program versions
(External adder. version and Redundancy addr. vers.) corresponding to the version
stored on the target and the version to be stored are identical. In the case of a
generation implementing on-line modification with transfer, CONTROCAD does not
upgrade the versions.These address version numbers are presented to the user in
the version control zone (Program).
Type of address and version Generation Generation

number V(n) V(n+1)
External addr. version 8 8

Redundancy addr. vers. 8 8
Both types of on-line modification are possible. Both and buttons are
accessible.

On-line modification without transfer
On-line modification without transfer can only be executed if the program version
(External addr. version) corresponding to the version stored on the target and the
version of the program to be stored are identical. In the case of a generation
implementing on-line modification without transfer, CONTROCAD does not upgrade
the version.
The button is accessible.

number V(n) V(n+1)

The Redundancy address version has changed. Only modification without transfer is
possible. The button accessing on-line modification with transfer is desactivated.
Non-authorized on-line modification
number V(n) V(n+1)

Both versions have changed. No on-line modification is possible. Both buttons are
desactivated.
In CCAD versions <= 4.2, if both on-line modifications, one with transfer
and one without transfer, are authorized, only the on-line modification with
transfer will be accepted by the device: in a on-line modification without
transfer the application of the standby will not switch to RUN.
5.1.2 Operating Mode
The purpose of this function is to store a new program in a C80-35, C80-75 or RX3I
controller without stopping the process.
A controller has:
 2 dynamic states (designated M/S in the table below): Master or Stand by
 2 modes: App =run (operational) or App=stop (stopped)
In order to execute the on-line modification of programs it is advisable to follow the
steps outlined below after having modified the applications. The controller that is the
object of the on-line modification operation must be operational, i.e. both entities
(Master and Standby) must be in RUN mode with operational redundancy .
Both entities must have the same program and address version numbers.
No on-line modification request can be executed if the M/S transfers are
stopped.

The table shown below presupposes that, at the start of the sequence, the primary
is the master and the secondary is the standby. However the same principle can
also be applied in the opposite case by permuting the primary and secondary
devices.
The steps marked by an asterisk (*) are optional; they are designed to enable the
master/standby state of the device to be reset to the state prior to the on-line
modification operation.
The term "Version" in the table below designates the program version stored (read
in the version window).
In the table below, the timeout T seconds is not specified as it is
dependent on the application (VCOM redundancy timeout and slow
application system). It is important to specify T during the platform tests.
The minimum value is 20 seconds.

ON-LINE MODIFICATION OF C80-X5 and RX3I APPLICATIONS
Ste ACTION
PRIMARY SECONDARY
ps LABEL BUTTON
1 Initial state: App: run App: run
The code generation mode has been defined in the M/S: Master M/S: Standby
CONTROCAD workspace (cf. [GUICHGTCCAD]). Version N Version N
Check the Allow incompatible Online Modif
parameter to be able to do an on-line modification
without transfer (cf. [GUICHGTCCAD]). The generation
for on-line modification terminates without error
(cf.[GUICHGTCCAD]).
2 Run Cell Loader, then select the device (independently
primary or secondary)
3 Select the type of on-line modification (no tick to do) App: run App: stop
The icons are only available if on-line modification is M/S: Master M/S: Standby
authorized (See.§ 5.1.1) Version N Version N
When the command is accepted by the device, the
RdnState is modified in both units:
It is possible to return to the selection of on-line

modification or to cancel the command. See Step 20
4 Store the new program on the standby after having App: run App: stop
ticked the PROG checkbox marked with a red cross M/S: Master M/S: Standby
on the standby Version N Version N+1
5 Start the standby after selection App: run App: run
M/S: Master M/S: Standby
Version N Version N+1
6 Wait T seconds, and check that the standby controller
with the new version has not stopped
If the Standby application does not remain in

Run, on-line modification is not authorized on the
Master (See § 5.1.1). See errors in the device fault
table.
7 Select the controller, switch over App : run App : run

Check the process and the modification. If the M/S : Standby M/S : Master
modification is OK continue, otherwise go to step 14 Version : N Version : N+1
8 Wait T seconds to see if the new master controller is
maintained.
If the Standby application does not remain in

Run, on-line modification is not authorized on the
Master (See § 5.1.1). See errors in the device fault
table.
9 Select the new standby then stop it. App : stop App : run
M/S : Standby M/S : Master
Version : N Version : N+1
10 Store the new program on the standby, tick the PROG App : stop App : run

Ste ACTION
PRIMARY SECONDARY
ps LABEL BUTTON
box on the standby (red cross) Version : N+1 Version : N+1
Then remove the tick in PROG boxes on the new
master.
11 Select the Standby controller. Put the standby App : run App : run
controller application back in RUN mode. The new M/S : Standby M/S : Master
version of the controller application can now be put into Version : N+1 Version : N+1
service; the CONTROCAD database and the
controllers have the same version number
The current on-line modification indicators in the
RdnStat state disappear
12 Wait T seconds, and check that the standby controller
with the new version has not stopped.
13 App : run App : run
To go back to the initial M/S state
M/S : Master M/S : Standby
select the controller then switch over
Version : N+1 Version : N+1
Case where the modification is not correct from the point of view of the process (continued from step 7)
14 The modification of the program in the new master is App : run App : run
not OK M/S : Standby M/S : Master
15 Select the controller and redo a switch-over request . App : run App : run
The master controller is running the old version of the M/S : Master M/S : Standby
controller application Version : N Version : N+1
16 Select the standby and stop it. App : run App : stop
17 Choose the previous version
generated in the pull-down list in
CELL LOADER  Versions  Select
18 Store the program of the standby, after selecting the App : run App : stop
PROG checkbox marked with a red cross on the M/S : Master M/S : Standby
standby. Version : N Version : N
19 Select the Standby controller. Put the standby App : run App : run
controller application back in RUN mode. The old M/S : Master M/S : Standby
version of the controller application is now in service; Version : N Version : N
the database and the controllers have the same
version number
The current on-line modification indicators in the
RdnStat state disappear
20 To go back to the initial M/S state, select the controller App : run App : run
then switch over M/S : Standby M/S : Master
Version : N Version : N
21 As long as the standby controller has not been
restarted it is possible to interrupt an on-line
modification request on the controller application and
return to the selection of on-line modification when
both types (with and without transfer) are authorized.
At the end of an of on-line modification operation this
indicator is no longer accessible.

5.2 On-line Modification of the MFC3000 Controller Application
5.2.1 Definition
The on-line modification of the controller application takes advantage of the

redundancy of the MFC3000 controllers to put a new version of the controller
application into service without losing control and oversight of the process.
Before generating the CONTROCAD configuration in order to do an on-line
modification, it is advisable to read the introduction to on-line modification in
the document [GUICHGTCCAD].
On-line modification with transfer or with partial transfer can only be executed if the
program versions corresponding to the version stored on the target and the program
version to be stored are identical. In the case of a generation implementing on-line
modification with transfer, CONTROCAD does not upgrade the versions.
On-line modification with transfer
In the case of an on-line modification with transfer (icon ), the program will be
equalized directly in the standby device.
On-line modification with partial transfer
In the case of an on-line modification with partial transfer (icon ), the program
will equalized directly in the standby device;
It is possible to cancel an on-line modification if the modification is not

satisfactory. In order to equalize the program in the redundant device with
the previous program, select the Master device which has the previous
program and click on (icon ).
It is possible to validate an on-line modification if the modification is
satisfactory when it was previously aborted. In order to equalize the
program in the redundant device with the new program, select the Master
device which has the new program and click on (icon ).
The purpose of this method is to store a MFC3000 controller without stopping the
process.
A controller has:
In order to execute the on-line modification of programs it is advisable to follow the
steps outlined below after having modified the applications. Controller that are the
object of the on-line modification operation must be operational, i.e. the application
must be in RUN state with operational redundancy Both entities must have the
same program and address version numbers.

devices.

ON-LINE MODIFICATION OF THE MFC3000 APPLICATION
Steps ACTION
PRIMARY SECONDARY
LABEL BUTTON
Initial state: App : run App : run
1
The code generation mode has been defined in the M/S : Master M/S : Standby
CONTROCAD workspace (cf. [GUICHGTCCAD]). Version : N Version : N
The generation for on-line modification terminates
without error (cf.[GUICHGTCCAD]).
Run Cell Loader, then select the program on the App : run App : run
2
standby device (no tick to do) M/S : Master M/S : Standby
The icons are only available if on-line modification is Version : N Version : N+1
authorized (See.§5.2.1).
The Standby RdnSate swithes to to
Case of continue, otherwise go to step 3 bis

The MFC3000 is switched. App : run App : run
3
M/S : Stand by M/S : Master
The Master RdnSate swithes to to . Version : N Version : N+1
If the modification is correct from the standpoint of

the process, go to step 4, otherwise go to step 4bis
Case of continue, the Standby program will be egalized

The program modification is OK, on the master : App : run App : run
4 M/S : Stand by M/S : Master
then select the program on the standby device and Version : N+1 Version : N+1
press the button (no tick to do)

a green checkmark on the program entity indicates
that the program is equalized
To go back to the initial M/S state App : run App : run
5* select the controller then switch over. M/S : Stand by M/S : Master
Version : N+1 Version : N+1
Case of abort before the switch over

The program modification is not OK, cancel the
3bis modification in the standby :
App : run App : run
Select the master program and click on (no check to

do)
App : run App : run

4bis* To go back to the initial M/S state App : run App : run
select the controller then switch over. Version : N Version : N
Case of abort modification from the standpoint of the process after the switch over
The program modification is not OK, cancel the
4thd modification App : run App : run
App : run App : run

Select the master and click on (no check to do) M/S : Master M/S : Stand by
5thd Select the master program and click on (no tick to App : run App : run
do) M/S : Master M/S Stand by
6thd* To go back to the initial M/S state App : run App : run
select the controller then switch over. Version : N Version : N

Section 6 Stopping M/S Transfers for On-line Modification of Tuning
Parameters (C80-35, MFC3000 and RX3I)
6.1 Definition
The on-line tuning parameter modification operation enables the user to test a new
set of tuning parameters. The function of stopping the M/S transfers is only available
for redundant MFC3000, C80-35, SLG, AVR or RX3I devices.
Before modifying the tuning parameters in a C80-35 or RX3I, the "Allow
Inhib Tuning Values Transf" parameter of the device in the CONTROCAD
configuration must be equal to 1 before the generation of the configuration.
See the introduction to on-line modification in the document
[GUICHGTCCAD].
The modification of tuning parameters is explained in the document
[GUICHGTCCAD].
6.2 Operating mode
The on-line modification of the tuning parameters necessitates the utilization of

services provided by the SDA.
It is not possible to stop M/S transfers if an on-line modification of the
application is in progress.
A controller has:
The application must be in RUN with operational redundancy . Both entities
must have the same program and address version numbers.
devices.
6.2.1 C80-35 and RX3I Controllers
STOPPING M/S TRANSFERS FOR ON-LINE MODIFICATION OF TUNING PARAMETERS

(C80-35 and RX3I)

Step ACTION PRIMARY SECONDARY
LABEL BUTTON
1
Check the Allow Inhib Tuning Values Transf M/S : Master M/S : Standby
parameters to be able to stop transfers (cf. Version : N Version : N
[GUICHGTCCAD]). Parameters
transferred
The applications of the controllers Master and
Standby are in Run mode.
The programs versions are the same.
Select the master device then stop the transfer of the App : run App : run
2
tuning parameters. M/S : Master M/S : Standby
When the command is accepted by the device, the Version : N Version : N
RdnState is modified in both units: Parameters
not
transferred
Tune the parameters on the master controller on line
3
from an application Watch window
The indicator appears on the Param entity on

the master and standby devices; this indicates that at
least 1 parameter has been modified and that a back-
noting operation can be run to save the tuning
parameters in the CONTROCAD database (See
Back-noting Tuning Parameters § 6.3)If the new
parameters are considered valid, continue, otherwise
go to step 5
The new parameters are OK: App : run App : run

4
Select the master device then reactivate the transfer M/S : Master M/S : Standby
of parameters; this activates the standby controller Version : N Version : N
insertion process. New
The "Transfer stopped" indicators in RdnStat parameters
disappear. transferred to
the standby
App : run App : run

5 If the new parameters are judged not OK:
It is necessary to switch over for the controller with the
old parameters to become master
Old
parameters
The "Transfer stopped" indicators in RdnStat transferred
disappear but the indicators remain.
Note that this indicator does not mean that the parameters in the target and
in the configuration tool are different; it shows that a tuning operation has
been done.
App : run App : run

6* Switch-over to return to the initial M/S state
Old
parameters
transferred

6.2.2 MFC3000 Controller
STOPPING M/S TRANSFERS FOR ON-LINE MODIFICATION
OF TUNING PARAMETERS (MFC3000)
Step ACTION PRIMARY SECONDARY
LABEL BUTTON
1
The applications of the controllers Master and M/S : Master M/S : Standby
Standby are in Run mode. Version : N Version : N
The programs versions are the same. Parameters
transferred
Select the master device then stop the transfer of the App : run App : run
2
tuning parameters. M/S : Master M/S : Standby
When the command is accepted by the device, the Version : N Version : N
RdnState is modified in both units: Parameters
not
transferred
Tune the parameters on the master controller on line App : run App : run
3
from an application Watch window M/S : Master M/S : Standby
The indicator appears on the Par. entity on the Version : N Version : N
master device; this indicates that at least 1 parameter New
has been modified and that a back-noting operation parameters
can be run to save the tuning parameters in the not
CONTROCAD database (See Back-noting Tuning transferred to
Parameters § 6.3) the standby
If the new parameters are considered valid, continue,
otherwise go to step 4bis
Note that this indicator does not mean that the

parameters in the target and in the configuration tool
are different; it shows that a tuning operation has
been done.
The new parameters are OK: App : run App : run
4
Select the master device then reactivate the transfer M/S : Master M/S : Standby
of parameters; this activates the standby controller Version : N Version : N
insertion process. New param New
The "Transfer stopped" indicators in RdnStat transferred to parameters
disappear, the Rdn State is on both MFC3000 the standby
If you want to backnote the parameters in CCAD
database refer to § 6.3.
App : run App : run
4bis If the new parameters are judged not OK:
It is necessary to switch over for the controller with the
old parameters to become master
New Old param not
parameters transferred
App : run App : run
5 Enable transfer of settings : select the master
application and select the button
The indicator disappears on the Par. entity on the Old Old param
master device parameters transferred
App : run App : run

6* Switch-over to return to the initial M/S state

6.3 Backnoting Tuning Parameters (C80-x5 - RX3i -MFC3000)
6.3.1 Definition
The tuning parameters of a device are back-noted by updating the parameters of the
current CONTROCAD generation version, of the saved version and of other recent
saved generation versions if required. Only the parameters common to these
versions and to the device are updated from the values of the parameters read in
the active device (the active device corresponds to the master device when the
device is redundant).
The operation of backnoting necessitates the use of services provided by the SDA.
For the MFC3000 Controller, it is not possible to backnote the parameters values on
the old versions, the operation of backnoting is done on the version stored in the
controller.
For c80-x5 and rx3i, If CONTROCAD code has been generated without reloading
the configuration and/or the programs Cell Loader offers the possibility of back-
noting to the "saved" version generations
Selection of Cell version
In the example below, 3 cell generations are saved; they correspond respectively
to the generations V30, V31, V37.
State before back-noting: The configuration of the tuning parameters stored in
the target corresponds to that produced by the generation of cell 31. However,
tuning operations have been performed and, for certain parameters, the values
differ.
State before back-noting
Generation versions saved Current TARGET

generation
version
Generation 30 31 37 37 31
Program version 11 11 11 11 11
Date program version 10/07/03 10/07/03 10/07/03 10/07/03 10/07/03

State before back-noting

generation
version
Parameter version 8 9 10 10 9
Date parameter version 10/07/03 12/07/03 13/07/03 13/07/03 12/07/03
A=1 A=1 A=1 A=1 A=3
B=2 B=2 B=2 B=7 B=9
Tuning parameters C=6 D=4 E=2 F=3 D=4
D=4 E=2 F=3 G= 8 E=1
F=3 F=6
State after back-noting that is not extended to the more recent generation
versions saved:
When the back-noting done, the values of tuning parameters are identical in the
target, in the generation current and in the generation saved (corresponding to
the generation version stored in the target).
The "Date version parameters » and « version parameters » are identical in the
target and in the generation saved: the "Date version parameters » is update with
the date of the modification, the value of the « version parameters "correspond to
that of the generation saved incremented of 1 (modulo 256).
Note that in generation version current, only the parameters common are
updated:
State after back-noting without extending the back-noting

to the most recent generation versions saved

generation
version
Parameter version 8 9 10 10 10 9 10
A=1 A=13 A=1 A=13 A=3
B=2 B=29 B=2 B=79 B=9
D=4 E=21 F=3 G= 8 E=1
F=36 F=6
State after a back-noting that is extended to the most recent generations saved:

When the back-noting is done, the values of tuning parameters are identical in
the target, in the current generation, in the saved generation (corresponding to
the generation version stored in the target) and in generations saved with
program version numbers and parameters equal to or higher than those in the
target.
The value of "Date version parameters" is identical in the target and for all the
saved generations: the "Date version parameters" is updated with the date of the
modification.
The "Version parameters" correspond to those of the generation saved
incremented by 1 (modulo 256), and by incrementing the previous generation
version (modulo 256) for the more recent versions. Note that in the current
generation version and in the most recent saved generation versions, only the
common parameters are updated:
State after back-noting with the back-noting extended

to the most recent generation versions saved

generation
version
Parameter version 8 9 10 10 11 10 9 10
A=1 A=13 A=13 A=13 A=3
B=2 B=29 B=29 B=79 B=9
D=4 E=21 F=36 G= 8 E=1
F=36 F=6
After the back-noting operation, the indicator disappears. These new parameter
values correspond to the new initialization values in the case of a new Store.
Note that the back-noting of parameters may be inhibited if the list of
parameters of the target device can no longer be built (generation version
deleted in CONTROCAD).
In the context of back-noting tuning parameters in an array, the parameter array
must be visible in the CONTROCAD screen accessible from the Array Initial Value
menu of the CONTROCAD variable grid.

The command used to backnote parameters from the Cell loader tool is only
available for MFC3000, C80-75, C80-35 and RX3I controllers.
Special case of the CE2000:
 when a module parameter has been tuned from the ALSPA P80 PLC tool on the
Hardware configuration of a CE2000controller, the "Backnoting required"
indication is displayed on the HW entity of the device; backnoting is executed
from the ALSPA P80 PLC tool and the configuration must be regenerated after
the P80 Hardware Configuration has been updated and stored so that the
modification can be applied the next time the device is started.
 when a TRX program parameter has been tuned from the SDA, the "Backnoting
required" indicator is shown on the Param entity of the device; backnoting is
executed from the SDA and the configuration must be regenerated and stored for
the modification to be applied the next time the device is started.
The following protocol must be complied with:

BACK-NOTING TUNING PARAMETERS (C80-X5-MFC3000)
ACTION
Steps PRIMARY SECONDARY
LABEL BUTTON
App : run App : run
1 Initial state:
The applications of the controllers Master and Parameters: Paramètres :
Standby are in Run mode. Generation Génération
date date
The programs versions are the same. Generation Génération
The tuning parameters have been modified on-line time Version time Version
(see the steps 1 to 4 in by a graph § 5.1.1 On-line New New
modification of tuning parameters with transfer of parameters parameters
tuning parameters stopped. transferred to received
standby
The "Back-noting required" indicator is active on
the Par. entity of both the master and standby
controllers (case of a redundant structure)
2 Select the master controller application, then execute
the back-noting operation
App : run App : run
3 Select versions that you want to backnote the current
parameters :
Parameters: Parameters:
Once the current and selected versions have been Generation Generation
updated, the version and the date of the parameters date ++ date
are updated as follows: Generation Generation
time ++ time ++
 The parameter time is initialized with the time of Version +1 Version+1
the back-noting operation New New
The parameter version is initialized with the value of Parameters parameters
the saved generation version incremented by 1 transferred to received
modulo 256 (the value of the version is between the standby
[0..255])
The indicator disappears on the Par. entity of

both the master and standby controllers

Section 7 Clearing Forced Values
7.1 Definition
Forcing a variable in a controller necessitates the utilization of the services provided

by the SDA.
In an Application watch window, the forced attribute "F" appears beside the
forced value in the input screen.
In Cell Loader, the indicator appears on the Master and Standby controllers
in the For I/O or For Var entity, depending on the variable forced.
The Clear forced values command is then available from the Cell Loader tool
bar. This command can be used to go back to the value prior to forcing and to erase
the forced value indicator in the Watch Window and on Cell Loader.
The Clear forced values operation performed from Cell Loader consists in deleting
all the forced values executed on a controller (Master or Standby if the structure is
redundant).
In an application watch window, the forced attribute "F" beside the forced
values in the input screen disappears.

If no values have been forced by CONTROCAD and the indicators nevertheless
signal the presence of a forced value , it is probable that a value has been
forced by the ALSPA P80 PLC or CIMPLICITY Machine Edition tools. The Clear
forced values command can also be used to erase these forced values. A value that
has been forced by ALSPA P80 PLC or CIMPLICITY Machine Edition is shown by
the presence of the indicator at the level of the For Var functional indicator.
If a data have been forced by CONTROCAD on the Standby, the forced

data will be erase by the Master if the data isn’t forced in the Master (the
data can be transfered by the redundancy link).
Forcing Command on C80-x5 and Rx3i Devices : (voir §7.2).
Forcing Command on the MFC3000 Controller (voir §7.3).
Forcing Command on the CE2000 Field Controller(voir §7.4).
Forcing Command on AVR/SLG/IHR Controllers(voir §7.5)
7.2 Forcing Command on C80-x5 and Rx3i Devices
The zones of C80-75, C80-35 and RX3I devices that can be forced by a user are
described in the document [MEX10CCAD].
When the device is redundant, the "Clear forced values" command is only
transmitted on the selected device. If the clear command is run on the Standby
device and if forced values are active in the Master device on variables transmitted
via the redundancy zone, the forced values will be transferred from the Master to the
Standby.
On the display system watch window C80-75 equipment, a over writing counter
indicates the number of forced values on the application variables.
7.3 Forcing Command on the MFC3000 Controller
The I/O or Variables values on MFC3000 devices can be forced by a user, see
document [MEX10CCAD].
Cell Loader indicates the presence or the absence of forced I/O or Var
values, the Clear forced value command clear the all Variables and I/O forced
values.
7.4 Forcing Command on the CE2000 Field Controller
The forcing function is not operational on CE2000 R5 TRX devices configured in

safe mode.
The zones of CE2000 devices that can be forced by a user via the ALSPA P80 PLC
tool are described in the document [MEX10CCAD].
Cell Loader indicates only the presence or the absence of forced I/O or
Variables values , but the Clear forced value command is not operational.

The connection with the CE2000 controller via the ALSPA P80 PLC tool is
only possible if the Cell Loader window is closed.
7.5 Forcing Command on AVR/SLG/IHR Controllers
The user does not have access to the diagrams (controller application) of the
AVR/SLG and IHR controllers. It is therefore not possible to execute a forcing
operation or to execute a Clear forced values command on these controllers.

Section 8 Accessing the Device Fault Tables
Read the fault table in the CE2000 (See §8.3).

Refresh the fault table in the CE2000 (See §8.3).
Quit the fault table in the CE2000 (See §8.3).
Save the fault table in the CE2000 (See §8.3).
8.1 Reading Faults on C80-x5 and Rx3i Controllers
The fault window shows the alarms logged by the C80-X5 and RX3I controllers.
When the device is redundant, the fault window is opened in associated mode,
which facilitates the visualization of faults on redundant controllers.
The fault table of the C80-75 cell controller is displayed for CE2000, DI103,
GEMSTART and DI80 devices. Faults on devices managed by the C80-75 cell
controller are signaled in the I/O fault table of the C80-75.
The presence of a blocking fault on the device is signaled by the App state ,
until this fault is corrected and acknowledged, the application cannot start.
The fault table is always accessible, either by Ethernet connection when the device
is configured or by serial link.
1. Select the device
2. The fault window is opened by clicking on in the button bar
3. Select the communication port

4. Select the PLC or I/O fault table
 The PLC fault table is specific to internal C80-x5 faults
 The I/O fault table concerns the faults seen on the cell devices (bus faults,
device non-operational, I/O module faults etc.)
5. The fault tables can be erased; only the faults still present remain ( edit =>
clear table or F9).
6. This window always remains accessible; it can be closed by the operator after
use
8.2 Reading Faults on a MFC3000 Controller
The fault window shows the alarms logged by the MFC3000 controller. When the
device is redundant, the fault window is open on the Master device. Faults on
devices managed by the MFC3000 cell controller are signaled in the I/O fault table
of the MFC3000.
The fault table is always accessible via the Ethernet connection when the MFC3000
possesses the IP address of the Controcad configuration.
In Controcad versions <= 4.2, faults cannot be read from Cell Loader by the
serial link.
1. Select the device (independently primary or secondary)
2. The fault window is opened by clicking on in the button bar

3. The fault tables can be erased; only the faults still present will remain (see
document [MULPCX])
4. The fault table of the Standby device can be accessed from the fault table of the
Master device and vice-versa (see document [MULPCX])
5. This window always remains accessible; it can be closed by the operator after
use.
8.3 Reading Serious CE2000 Controller Faults
Before shutting down completely, the PU saves the serious fault at the origin of the
transition in the Serious Fault table. The number of the first error at the origin of the
transition is saved for the local display function.
Reading the Serious Fault table via Cell Loader:
If the fault is transitory the PU is power cycled and switched to Master state (if the
CE2000 is redundant): the Serious Fault table is stored in the saved memory of
the PU, and can be read by a command.
1. Right click on the faulty device
If the device is redundant, the faulty unit must be the Master, so
acknowledge the error, see above then switch over the redundant device.

2. Select the "Display System Table" option
3. The "Address Zone" field must be equal to 200
4. Refresh to display the zone
5. The fault table can be saved in a text file by the "Save" command
Displaying the error locally on the defective PU:
The number of a Serious Error is between 1 and 999 (not all values are
implemented). A LED (SYN) is used to count the hundreds (H: 0 thru 9),
another (CPU) for the tens (T: 0 thru 9) and a third (USR) for the Units (U: 0
thru 9)
2 LEDs (CNF and I/O) are used as Separators between the number displays.
A display cycle executes as follows (i.e.. number 206):
6. start of display: the Separator lights for 1 second
7. the number is displayed by flashing at a frequency of 1 Hz for N period(s)
depending on the figure to be represented (if 0: no light):
8. display of hundreds: C lights (2 periods in this example)
9. display of tens: D lights (0 periods, so no light in this example)
10. display of units: U lights (6 periods in this example)
11. start over at 1. and so on.
Acknowledgement of the error:

To acknowledge the error, the PU must be removed physically from the CE2000
rack at a precise moment in the display cycle, then re-inserted. This moment is
defined by a time window represented by the flashing of the Separator LEDs at
a high frequency (10 Hz) for 5 seconds. This window is reproduced cyclically
every 5 display cycles of the error number.

Section 9 Devices Simulated by SI80
In previous versions of Cell Loader, a device simulated by SI80 was signaled as

such in order to be ignored, as most of the functions provided by Cell loader were
not previously available on a device simulated by SI80.
This function has not been deleted as it can be useful during the debug of the cell;
select the simulated state in the communication indicators of the previously
selected device. Deselect to indicate that the device should no longer be ignored.
For redundant devices actually composed of two interfaces, i.e. a redundant C80-35
but not a redundant CE2000, the simulation indicator is replicated on the redundant
device. The simulation of such a controller concerns both devices.
The C80-75 device cannot be simulated by SI80. Any request is refused by the tool.
When a device is simulated by SI80, the associated indicators are not significant.
9.1 Exporting Files for SI80
The cell device configuration can be exported to an import directory for SI80 by
selecting .
The export directory path must not contain names with blank characters.
System information zone

Section 10 System Information Zone
The window is accessed by select CELL LOADER  Display  Watch Window

The name of the device is shown in the header (e.g. CC80-75). This is produced by
the configuration of the Cell Loader and may differ from the target device.
Activation of the instrumentation increases the execution time of the
program on the controller.
C80-75 Cell Controller : ( See §10.1.)
MFC3000 Cell Controller : ( See §10.2.)
C80-35-AVR-SLG-IHR Field Controller : ( See §10.3.)
CE2000 r7 TRX Controller Field : ( See §10.4.)
10.1 C80-75 Cell Controller
For the redundant C80-75, a selected primary or secondary unit is updated

every 5 seconds, the data concerning the other unit is also updated.
System information zone of a C80-75
Two tabs are input:

General
Execution time
A pull-down in the Execution time tab can be used to select the different views.
 The General tab
 Number of startups indicates the number of insertions of the controller in
standby mode since the last reset to 0 of the insertion counter.

 Steps since start of step by step indicates the number of cycles executed in
cycle to cycle mode. This field equals 0 in continuous mode.
 Over Writing Counter indicates the number of forced variables stored in %M
 The Execution time tab
For the C80-75, instrumentation is always active. There is therefore no start/stop
instrumentation button.
The current minimum, maximum and average execution times are given for the
D1, D2 and D3 domaines and for the logic (OpLoop) and analog (CLoop)
programs.
The type of execution time to be displayed is selected in a pull-down list.
 Current execution time indicates the current execution time on the selected
controller.
 Minimum execution time indicates the minimum execution time on the
selected controller.
 Maximum execution time indicates the maximum execution time on the
 First Cycle execution time indicates the execution time of the first cycle on
the selected controller.
 Average execution time indicates the average execution time on the selected
controller.
 Number of cycles indicates the number of cycles over which the evaluation of
the average cycle time is calculated.
 CPU LOAD represents the percentage of the total system load consumed.
 APPLI LOAD represents the percentage consumed of the total load reserved
to the application.
APPLI LOAD=[(Σ on last 3 cycles(D1+D2+ Oploop)+D3+Cloop)/[3*(logic cycle
period - system cycle time )]]*100 where system cycle time = 20% of the logic
cycle period
CPU LOAD=(Σ on last 3 cycles(D1+D2+ Oploop)+D3+Cloop + (3* time of system
cycle))/ [3*(period of the logic cycle]
The period of the logic cycle is:
 100ms for an C8075 cell with a 100/300 PU
 50ms for an C8075 cell with a 50/150 PU
E.g.
The values used are those of the screen above and the period of the logic
cycle is 100ms
APPLI LOAD=[(3(0.3+2.2+6)+(0.1 +0.7))/(3*(100 - 20))]*100 =10.9 %
CPU LOAD=[(3(0.3+2.2+6)+(0.1 +0.7 + (3*20))) /3*100 =28.8
In this example, the application consumes only 11% of the total load
reserved for it.
 Number of logic cycles indicates the number of cycles on which the
evaluation of the average cycle time has been calculated.

 Number of regul cycles indicates the number of cycles on which the
Commands are provided to update the variables in the target device. The command
is executed by the operator and the request is transmitted only on the selected
device. When the device is redundant, the command is transmitted on the selected
unit (master or standby); the command is transmitted from the master to the standby
by means of the transfer of redundancy variables.
 The General tab
 The command "insert_cnt" reinitializes the "Number of startups" counter

The "INIT_INSTRUM" command reinitializes the minimum, maximum and

average execution time by resetting the INIT_INSTRUM variable to 1
10.2 MFC3000 Cell Controller
System information zone of a MFC3000
Two tabs are input:

General
Execution time
 The General tab
For the MFC3000, instrumentation is always active. There is therefore no
start/stop instrumentation button.
The current minimum, maximum and average execution times are given for the
program.
controller.

controller.
Number of cycles indicates the number of cycles over which the evaluation of the
average cycle time is calculated.
10.3 C80-35-AVR-SLG-IHR Field Controller
For the redundant devices, a selected primary or secondary unit is updated

every 5 seconds, but data concerning the other unit is not updated (the
values displayed are the last values read when the device was selected).
System information zone of a C80-35
Two tabs are input:

 General
 Execution time
 The General tab
 Number of startups indicates the number of insertions of the standby
controller since the last reset to 0 of the insertion counter. This parameter
appears only if the device is redundant.
 Over Writing Counter indicates the number of forced variables stored in %M

For the C80-75, instrumentation is always active. There is therefore no start/stop
instrumentation button.
The current, minimum, maximum and average execution times are given for the
D1, D2 and D3 domaines and for the logic (OpLoop) and analog (CLoop)
programs.
The type of execution time to be displayed is selected in a pull-down list.
controller.
 First Cycle execution time indicates the execution time of the first cycle on
the selected controller.
controller.
 Number of cycles indicates the number of cycles on which the evaluation of
the average cycle time has been calculated.
 CPU LOAD represents the percentage of the total system load consumed.
 APPLI LOAD represents the percentage consumed of the total load reserved
to the application.
APPLI LOAD=[(Σ on last 3 cycles(D1+D2+ Oploop)+D3+Cloop)/[3*(period of
the logic cycle - time of system cycle)]]*100 where the time of system cycle =
20% of the period of logic cycle
CPU LOAD=(Σ on last 3 cycles(D1+D2+ Oploop)+D3+Cloop + (3* time of
system cycle))/ [3*(period of the logic cycle]
The period of the logic cycle is:
 100ms for an ES cell with a 100/300 PU
 50ms for an ES cell with a 50/150 PU
E.g.
The values used are those of the screen above and the period of the logic
cycle is 100ms
APPLI LOAD=[(3(0.3+2.2+6)+(0.1 +0.7))/(3*(100 - 20))]*100 =10.9 %
CPU LOAD=[(3(0.3+2.2+6)+(0.1 +0.7 + (3*20))) /3*100 =28.8
In this example, the application consumes only 11% of the total load
reserved to it.
 Number of logic cycles indicates the number of cycle on which the evaluation
of the average cycle time has been calculated.
 Number of regul cycles indicates the number of cycles on which the

Commands are provided to update the variables in the target device. The command
is executed by the operator and the request is transmitted on the selected device.
When the device is redundant, the command is transmitted on the other unit
(master and standby).
 The General tab
 The command "insert_cnt" reinitializes the "Number of startups"

counter
 The "INIT_INSTRUM" command reinitializes the minimum, maximum and

average execution time by resetting the INIT_INSTRUM variable to 1
 The "ON_" "OFF" command: "ON" trips the instrumentation of the

remote C80-35, "OFF" deactivates instrumentation.
10.4 CE2000 r7 TRX Controller Field
Only a single or redundant CE2000 R7 TRX is provided with a system information

zone.
System information zone of a CE2000
The name of the device is shown in the header (CE2KRTRX_2). This is produced by
the Cell Loader configuration and may differ from the target device.
Two tabs are input:
 The General tab
Intrusion Counter counts each reception of command with a wrong
password.

 CPU Load indicates the percentage of load consumed.
 Constant sweep time indicates the duration of the TRX application cycle
configured in tenths of a ms
 Exceed sweep time indicates the number of TRX application overshoots
These values are reset to 0 only when a CE2000 is started without context.

France
ALSTOM Power Systems
EMB - PCS
9, rue Ampère
91345 MASSY Cedex
Assistance Customer: +33 1 60 13 43 91
helpdesk.control-systems@power.alstom.com
www.power.alstom.com

Cell Loader - Ptp21a41011-Ec

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cell Loader - Ptp21a41011-Ec

Uploaded by

Copyright:

Available Formats

ALSPA Controcad

Section 1 Introduction ............................................................................................................ 6

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

1.1 Presentation of Cell Loader

The on-line mode window designated as Cell Loader is used to:

1.3 Reference Documents

User's Manual PTP21A41010 [MEX10CCAD]

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Current version: Non-archived cell generation version.

1.5 Accessing Cell Loader

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Cell Loader execution error

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Selecting the Generation Version( See §2.1.1)

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

2.1.1 Selecting the Generation Version

CELL LOADER  Versions  Select

Loading a version prior to the last generation is limited by the following

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

CELL LOADER  Versions  Keep

2.1.3 Number of Generation Versions Saved (External to Cell Loader)

The following options are also available from this tab:

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

CONTROCAD  Display Cell Version

2.1.5 Version Control Zone

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Cell Version Version of the cell

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

UT Version CE2000 UT129 version number

Generation date Generation date Generation date Generation date

Tab Misc. tab

Generation date F8000 Firmware

Generation date Generation date Generation date

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Cell Version Redundancy addresses version

Tab Misc. tab

Generation date F8000 Firmware revision

Single and redundant C80-35, Rx3I

Generation date Generation date Generation date

Tab Misc. tab

Generation date F8000 Firmware revision

Generation date Generation date Generation date F8000

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

Controller name Controller name Controller name

Single, redundant CE2000 with and without TRX

Generation date Generation date Generation date Generation

Misc. tab Misc. tab Misc. tab Misc. tab

F8000 ICR/IVC F8000 ICR/IVC F8000 ICR/IVC F8000 ICR/IVC

Generation date Generation date F8000 Firmware Revsion

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

F8000 Firmware revision

CELL LOADER  Tools  Select all Driver Conf ( See §2.2.1)

2.2.1 Select configurations entities

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

CELL LOADER  Display  Log

Show or hide the log view ( See §2.2.)

ALSPA Controcad Version 4.5 PTP21A41011-en Rev.C

2.5 Indicators in the Loading Interface Zone

2.5.1 Indicator of presence of the device on S8000

All the devices are accessible (ping on all S8000 interface)

2.5.2 Indicator of presence of the device on F8000