![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image003.jpg")
Control Expert Guide Lines
|
The aim of this document is to provide to the=
users
of Control Expert some advices on :
|
Versions
|
|
Date |
Author |
comment |
|
1.0 |
|
JP F |
creation |
|
|
2014 Nov 28th |
JP F |
DFB mono instantiation page10 -Upload Infos
page 28 -Data dictionary &nbs=
p;
page 34 |
|
2.0 |
2016 August 17th |
M A |
Updated chapter “To improve Build On Line performance”,=
and
“To improve Build Off Line performance” |
|
2.2 |
2016 Sept 2nd |
M A |
Update chapter “On Line modification” |
|
2.3 |
2020 March 1st |
M L |
Add info on Program Units |
|
2.4 |
2021 Feb 4th |
M L |
Add FBD link (PEP034572R) |
Contents
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image004.jpg")
Con=
tents<=
!--[if supportFields]>=
Multitasking to Optimize Processing.
User Elementary Function Blocks (EFBs)=
Derived Function Blocks (DFBs)
User Elementary Functions (EFs)
Performance of Languages in Run tIme
Mod=
ules and
Functional View
Phy=
sical
Station configuration
Derived Data=
Types
for Input/Output Modules (IODDTs)
Download the project in the PLC..
To improve Build On Line performance
To improve Build Off Line performance
Management
of the variable current values.
Migration
of Control Expert projects.
How to duplicate a FB instance in a graphical sectio=
n
OFS \
Control Expert synchronization.
How to
control the customer XML files.
Modification
of the IP address
PC configuration |
See Control Expert ReadMe delivered with prod=
uct. |
Acronyms |
PLC
: Programmable Logic
Controller CPU:
Control Processing Unit I\O
: Inputs \
Outputs ST
: Structu=
red
Text language LD
: Ladder language IL
: I=
nstruction
List language FBD
: Functional Blocks D=
iagram
language SFC
: Sequential Functional Chart langu=
age EDT
: Elementary Data Type DDT
: Derived Data Type IODDT
: Input Output Derived Data Type EFB
: Elementary Function=
Block DFB
: Derived Function Block EF
: Element=
ary Function FDT
: Field Device Tool DTM
: Device Type Manager DCS : Distributed Contr=
ol
System PRM : Profibus Remote Master XML : Extensible Markup Language XSD : Extensible Schema
Definition |
Program organization
Introduction |
Control Expert enables to use a modular
programming approach by the organization of code into:
|
Multitasking to Optimize Processing<= /span> |
Several tasks can b=
e used
to distribute the code, the Control Expert tasks are :
The following diagram shows the tasks in a mu=
ltitasking
structure and their level of priority:
Note 1 :=
The multitask system enables to =
optimize
the PLC performance and adapt the program to best meet the requirements of
the process to be automated. |
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image006.jpg")
Sections |
A section can be programmed in one of the five
IEC languages of Control Expert
A section can only belong to one task (Mast,
Fast, Aux…). Note 1 : You are advised to =
use
small sections wherever possible in order to facilitate program maintenan=
ce
and optimize performance when performing online modifications. The size o=
f a
section should be limited by the application structure to around 300 Lines in LD, 1000 lines of code=
in ST
and IL, 300 Blocks in FBD Note 2 : The
execution of the Sections can be controlled by a conditional bit (configu=
red
in the properties of the Sections), if the process doesn’t need to =
execute
one or several Sections at each PLC cycle, the use of this features allow=
s to
optimize the Scan Time. Note 3 : For confidentiali=
ty or
security raisons the code of the sections can be protected by Password in
Read or Write mode. |
Sub-routines (SRs) |
An SR section can be programmed in one of the
following four languages: LD, IL, ST, FBD. An SR section can only belong to one single t=
ask.
We do not recommend use of SR in new program =
(SR
are mainly used to allow smooth migration of converted application from o=
ur
legacy products) Note 1 : SRs are used for
recurrent types of processing that always act on the same global applicat=
ion
variables. |
Program Units |
A Program Unit is made up of: -&=
nbsp;
Parameters -&=
nbsp;
Local variables -&=
nbsp;
Set of sections You can build a very modular application using
Program Units. Online modifications are more effective becau=
se changes
are localized in a small area of the application. It is recommended to use Program Units as muc=
h as
possible. |
Data types and Variables
Introduction |
Control Expert allows to use two categories o=
f variable:
Note 1 : We recommend the u=
se of
Unlocated variables because they offer the following advantages:
|
Data Types (EDTs) |
The Elementary Data Types (EDTs) are :
Note 1 : Control Expert allows the use of extra=
cted
bit of word (type Int, Word and Byte). Sometimes it can be preferable to =
use
extracted bits of word instead of Bool Types. As it allows working direct=
ly
on the word instead of each bit. It saves also
memory, as for 16 extracted bits from a Word, memory space is 2 bytes, wh=
ile
16 BOOL take 16 bytes. |
Derived Data Types (DDTs)= |
DDTs are defined by the user as sets of other
data types. DDTs generally allow the structure and legibility of an
application to be optimized by making DDT variables corresponding to
application objects (motor, valve, etc…). A DDT "structure" is a data type which contains elements =
of
different types. A DDT "array" is a data type which contains elements of = same type.<= o:p> Note 1 : Any modification o=
f a
DDT type (addition or deletion of elements) is automatically propagated to
all of its corresponding instances in the program -> Save time in Build
time, Note 2 : It is highly
recommended to use DDT structures as much as possible. This enables to li=
mit
the number of variables and optimize the performance of the variable edit=
or
in Control Expert -> Save time in Build time, Note 3 : Avoid the large DDT=
structures
including several objects, prefer to define one structure for one object
(motor, valve, etc…) -> Best legibility of the application, |
Function Blocks
User Elementary Function Blocks (EFB= s) |
<=
span
style=3D'font-size:10.0pt;color:black'> The EFB function blocks are written by the user in C language.
The Control Expert =
EFB
ToolKit option, which integrates Microsoft’s C compiler, is require=
d in
order to implement EFBs. Note 1 :<=
/u> If the application requires very complex algo=
rithmic
processing, using C language allows to take advantage of the complete set=
of
instructions offered by this language. To optimize the Run=
time, it
should be noted that the code generated by the EFB ToolKit is executed by=
the
Intel 32 bit (Premium legacy) and Pentium (Premium and Quantum H-End)
processors that are fitted to our CPUs. <=
span
style=3D'font-size:10.0pt;color:black'> Note 2 : EFBs allow to
standardize specific functions of the procedure to be automated or to
standardize application devices (Motor, Valve, etc.) by offering:
Note 3 : Run time Note 4 : The fact that the code of the EFB is written in C languages
it’s protected naturally in Control Expert (not visible), very
interesting for confidentially raisons. |
Derived Function Blocks (DFBs) |
The Derived Function Blocks types are develop=
ed
by the user using one or more languages (according to the number of
sections). These languages are:
The advantage of the DFBs is that they enable=
to
standardize specific functions of the procedure to be automated or to
standardize application devices (Motor, Valve, etc.). More generally the =
DFBs
allow to :
Note 1 : Limit the size of D=
FB
sections (see Section chapter) in order to optimize performance when
performing Online modifications. For performance, prefer to use ST langua=
ge
than LD or FBD language. Note 2 : Run time performance
will be better if the DFB uses Boolean instructions, linear instructions =
(no
loops) and instructions acting on tables (arrays) Note 3 : Run time will be p=
articularly
degraded when using Loops (For Next, While DO…), programming with I=
ndex
( array[index] ), Upstream jump, big move of data memory, use of several =
level
of nested DFBs.
Note 4 : Same instance of a DFB can be used several time in the program, it
saves data memory, but to avoid in the application a data conflicts some =
rules
must be respected: -No
Data conflict problem if: - The DFB contains Inputs, Outp=
uts
and Inputs/Outputs parameters. -The DFB contains Privates
variables where the stored value doesn’t need t=
o be
maintained after the execution of the DFB Instance. -Possible
Data conflict problem if: - The DFB contains Privates
Variables where the stored value needs to be maintained after the executi=
on of
the DFB Instance. - The DFB has Init values
configured in the Public, Privates variables or in the Inputs parameters.=
-The DFB contains Timer, Counte=
rs.
Note 5 :<=
/u> DFB Addressing mode =
:
*=
2 *=
1 *=
4 *=
3
|
||||||||
User Elementary Functions (EFs) |
<=
span
style=3D'font-size:10.0pt;color:black'> The EF function blocks are functions used in a
program which perform a predefined software function. Control Expert provides a set of system EFs. =
It
is also possible to develop your own EFs in C language using the EFB Tool=
Kit
option, which integrates Microsoft's C compiler. It should be noted that EFs have no internal
Latch of variables. This operating mode is used to limit memory u=
sage
in the data area. <=
span
style=3D'font-size:10.0pt;mso-bidi-font-family:Arial;color:green'> Note 1 : For applications requiring more
memory capacity in the data zone, it is preferable to use EF rather than =
EFB
if the desired function is proposed in both types. |
||||||||
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image008.jpg")
Cleanup application |
When programming, it
happens that several functions or variables become useless are removed fr=
om
application. Even if they are no more in the programming sections, these
functions or data always belong to the application. They must be purged f=
rom
the application to free memory. To perform Function=
s (FB,
EFB, DFB) purge in the right way :
This allows&=
nbsp;
to:
To perform Variable=
s purge:
Note 1 : It is also possible to cleanup all D=
FB
types of their useless private variables
It is recommended to
perform this action at the end of the DFB programming to decrease the mem=
ory
consumption of instances. |
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image009.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image011.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image012.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image013.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image015.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image016.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image018.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image019.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image021.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image022.gif")
Programming languages
Introduction |
Control Expert incl=
udes
the five IEC61131-6 languages as standard:
<=
/span> |
Performance of Languages in Run tIme= |
For applications using Boolean and numerical
instructions:
Note 1 : If you use the Ladd=
er
language (LD) to optimize the Run=
time performance
uncheck in the Control Expert Project Setting the option ‘Generate with LD l=
ink
animation’. Note 2: If you use the structured Text language (ST): ·
Use
the loops “WHILE DO” against the loops “FOR NEXT”=
(if
possible) which are more consuming in cycle times, ·
Use
the functions of Libset dedicated to the Arrays management (e.g. use MOVE_AREBOOL_INT rather than the assignment or the loops
“FOR”), these functions allow the optimization of the cycle t=
ime. Note 3: Avoid the variables
assignment with Constant Values, prefer the use of Init values defined in=
the
Data Editor. Note 4: Avoid the exchange of Structure information element by element (MyStruct1.Element1 :=3D My_Struct2.Element1, ect…), if possible pr= efer to use directly the address (My_Struct :=3D My_Struc2) which perform the complete element exchanges.<= o:p> Note 5: We do not
recommend massive use of the following functions : ·
BIT_T0_WORD() -> Use the assignment=
on
extract bits, ·
WORD_T0_BIT() -> Use the assignment=
on
extract bits, ·
SEL() -> Use the function MOVE(), (These functions wi=
ll
be optimized in Control Expert V6.0) Note 6: Avoid a <=
/u>big
SFC chart (section), prefer to define several SFC sections (Master Chart \
Slave Charts). |
FBD Language Best Pratice |
To exchange data between blocks, you can use
variables or wire. Wire provide an easy way to read code interaction
for small size application. If EDT data are exchanged, you can animate value=
s of
TEST_DFB.IN. Copy is done by value in this case.
Note: In this case animation of
complex structure will be impossible. If Complex Data are exchanged (structured variab=
le such
as DDT), we strongly recommend using variables to avoid any performance i=
mpact.
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image024.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image026.jpg")
Modules and Functional View
Principle and Advantages<= /h2> |
A functional module=
is a
group of program elements intended to perform a PLC function. A functional module is comprised of:
Note
1 : You =
are
advised to adopt a development approach using modules and the functional
view, because this enables you: ·
To not be
limited by the structure imposed by the PLC system, ·
To develo=
p in a
consistent and reusable way for all projects, ·
To have d=
irect
access to automation functions. Note 2 : The representation=
of
the application in functional view does not take into account the order in
which the PLC executes the program. The secti=
ons
contained within the functional modules are executed in the order in which
they are organized in the tasks of conventional structural view (from top=
to
bottom). |
<= o:p>
Physical Station configuration
<= o:p>
<= o:p>
Inputs / Outputs modules
|
Moving an application-specific module
within the configuration (change of position) results in the automatic
re-allocation of all the references to this module in the program. This m=
eans
it is possible to modify the configuration of these modules at any time
without any impact on the program. If the same type of mo=
dule
must be used several times in the configuration, simply configure it once=
and
then Copy\Paste it to the other desired locations. The module configurati=
on
parameters are copied for each module. You can then adjust them if necess=
ary. |
Deri=
ved Data
Types for Input/Output Modules (IODDTs)
|
The purpose of DDTs=
for I/Os
is to encapsulate variables corresponding to the modules'
application-specific channels in data structures. These data structures a=
re
predefined and supplied in Control Expert for the various modules of the =
PLC
station. Using IODDTs:
IODDTs =
are
accessed via the library by selecting the <Catalog> section. Note:=
IODDT instances are automatically allocated to
physiques addresses (%MW etc.). Example: =
the "Input_Pressure" instance of a s=
tandard
"T_DIS_IN_STD" IODDT used with discrete input modules: The
link between this instance and the discrete input module located in slot =
2 of
rack 0 is shown below. The physical addresses are automatically assigned =
by Control
Expert for each element of the data structure.
In the screen shown below, two Aliases (symbols)
have been defined by the user (Erreur_Voie and Value_Pression) to corresp=
ond
to the two elements of the I/O DDT structure shown above.
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image028.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image030.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image032.jpg")
Communication Configuration =
|
From the "Communi=
cation"
directory of the project browser, you can define the logical configuratio=
n of
the networks to which the PLC station is connected: Ethernet, Modbus Plus, Fipway, e=
tc. The method to be used
involves the following four steps: · =
Creation of a logical network, · =
Configuration of the logical network,
· =
Association of the card or of the module =
with
the logical network. The advantage of this
approach is that once steps 1 & 2 (creation and configuration of the =
logical
network) have been performed, you can start programming without having to
first perform steps 3 & 4. These two steps can then be performed at a=
ny
time, once the physical location of the network modules has been determin=
ed
in the station configuration.
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image034.jpg")
<= o:p>
FDT / DTM technology |
The FDT/DTM (Field Device Tool / Dev=
ice
type Manager) technology in introduced in the early 2000s due to the need=
to
simplify the integration of field devices in distributed control system
(DCS). This
technology has the following advantages: <=
span
style=3D'mso-list:Ignore'>·
<=
span
lang=3DEN-GB style=3D'font-size:12.0pt;font-family:"Times New Roman",seri=
f;
color:black;mso-ansi-language:EN-GB'>Open communication interface =
to integrate third party equipment f=
rom
different manufacturers using descriptive files called DTM to configure,
monitor and manage the lifecycle of such equipment · &nbs=
p;
<=
span
lang=3DEN-GB style=3D'font-size:12.0pt;mso-bidi-font-family:Arial;color:b=
lack;
mso-ansi-language:EN-GB'>Standard user interfaces to operate the equipment (engineering, operations, maintenance, · &nbs=
p;
<=
span
lang=3DEN-GB style=3D'font-size:12.0pt;mso-bidi-font-family:Arial;color:b=
lack;
mso-ansi-language:EN-GB'>Platform independent, depending on the user need the DTM of the different devices are
accessed on the same way whether it’s a simple configurator or a
sophisticated life cycle management system, · &nbs=
p;
<=
span
lang=3DEN-GB style=3D'font-size:12.0pt;mso-bidi-font-family:Arial;color:b=
lack;
mso-ansi-language:EN-GB'>Independent of the protocol, the FDT Container and the DTM Devices have
communication interfaces for HART, PROFIBUS, FUNDATION fielbus, AS-I and
other insdustrial protocols. · &nbs=
p;
Example
of architecture managed by FDT/DTM: =
· &nbs=
p;
<=
span
style=3D'font-size:12.0pt;font-family:"Times New Roman",serif;color:black=
'>Ethernet
IP &nbs=
p;
<=
span
style=3D'font-size:12.0pt;font-family:"Times New Roman",serif;color:black=
'>ModBus
TCP \ Profibus DP for the PRM Gateway
After the installation of the DTM, the CONTROL EXPERT DTM
Catalog must be updated. After their configuration in the CONTROL EXPERT project the DTM are
present in the DTM
Browser.
For the Devices on Profibus DP \ PA connected to the PRM Gateway itself connec=
ted to
Modbus TCP the IOScanning table is automatically filled
The
Devices variables managed by the DTMs are automatically generated in CONT=
ROL
EXPERT.
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image036.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image038.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image040.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image042.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image044.jpg")
Project management
Building a project |
It is mandatory to build the whole project (Rebuild All Project) =
in
the following cases:
The inc=
remental
generation (Build Project) must be used preferably in local mode to optim=
ize
the generation time, it is obligatory in connected mode PLC in Run (On li=
ne
modification) or PLC in Stop. Note 1: <=
span
style=3D'font-size:12.0pt'>Once the application is debugged and "def=
initive",
it is advisable to perform a Rebuild all, to free memory as much as possi=
ble. Note 2: Once the progra=
m has
been built do not forget to regularly check memory usage (PLC -> Memory Consumption... menu). =
When Control
Expert detects excessive memory fragmentation the "Pack" button
becomes active to enable you to perform a defragmentation. Note 3: The option “Virtual connected mode” in the zone "General -> Build settings" (menu Tool=
s -
> Project Settings) allo=
ws to modify the
project in your office and transfer it later without stop the PLC. In this
mode the Build \ Rebuild commands are disabled (to avoid the modification=
of
the project signature before the PLC connection) and this mode warn you if
the modification you are doing is forbidden in On line mode. In the attached fil=
e there
are additional information on the project generation
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image046.gif")
Download the project in the PLC |
The optimum perform=
ance
of communications between the PC and the PLC is achieved via USB port or
Ethernet port for all PLCs embedding these ports. For Quantum PLC wit=
hout
embedded Ethernet, use of Modbus+ is recommended For Premium PLC wit=
hout
embedded Ethernet, you are advise=
d to
use an Ethernet module during the design and the commissioning phases. The
module can be removed for operation. |
On line modification |
Control Expert enab=
les
to modify the different sections of the program, with the PLC in RUN.
Note 1 :=
I/O Events are not modifiable in=
run
mode Note 2 <=
u>: It
is recommended to perform several small consistent sections modification =
at
once. Note
3 : Modification of SFC actions or transitions of on=
e SFC
section results in the transfer of all Action sections and Transition
sections of the corresponding SFC section. |
To improve Build On Line performance |
To
optimize the time of On Line modification you may set the following Proje=
ct
Settings (menu Tools - > Project Settings) :
To secure applicati=
on
modification we rec=
ommend
to Set “Save STA”.
To optim=
ize
the On Line modification the option must be put on “On user
request” mode, the Upload information will be transferred manually =
in the
PLC before the Off Line mode by the user (menu
PLC -> Update upload information). To secure applicati=
on
modification we recommend to set “Automatic mode”
General recommendations :
|
To improve Build Off Line performance |
To
optimize the Build time (off line) performance you may set the following
Project Settings (menu Tools - > Project Settings) :
General recommendations :
|
Import functions |
An Control Expert allows to
export / Import, whole or parts of the application, using xml file format=
:
Note 1 : To keep consistency of the exported files, Cont=
rol
Expert exports also all the used data in the exported file, user can also
select export options to export SR, DDT type and DFB used .
· =
Avoid the used of the partial import |
Management
of the variable current values
|
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image048.gif")
Migration
of Control Expert projects
|
The STU file (Control Expert project=
) cannot
be used to migrate a project from an Control Expert Version to another Co=
ntrol
Expert version because the database embedded must be rebuilded on each
different Control Expert version. The STA file (Control Expert project
archive) must be used to migrate a project to a new version of Control Ex=
pert,
it present also the following advantages:
After the installation of Control Expert, all the
libraries belonging to the different Control Expert versions are present =
on
the station. When the STA file is opened it’s necessary to generate=
and
download the project only if the original project library (coming with the
STA file) is changed, with the original library the previous application =
functional
level is maintained. The version of the library is selected during the opening of the STA fi=
le:
|
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image049.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image051.jpg")
<= o:p>
<= o:p>
<= o:p>
Additional information
How to duplicate a FB instance in a graphical section |
In the graphic=
al
languages (LD \ FBD), a Copy
&& Paste of a functional block instance (EFB \ DFB) increments
automatically the name of the instance, “My_Instance_Name” be=
comes
“My_Instance_Name_0”. Sometimes, it’s useful to use sev=
eral
times the same instance in the program, for that it’s necessary to =
call
the “FFB Input Assistant=
221;
from the contextual menu of the section.
The FFB Type and the Instance name must be
selected, the same instance block in now present in the section. <=
!--[if gte vml 1]> |
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image052.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image054.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image056.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image057.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image058.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image060.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image062.jpg")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image063.gif")
![](3D"ControlExpert_UnityProGuideLines_EN_2.4_files/image065.jpg")
How
to control the customer XML files
|
Before =
to
import customer XML files in UNTY PRO, it’s interesting to control =
them
in order to apply correction if errors are detected. CONTROL=
EXPERT
provides XSD files (eXtensible Schema Definition) corresponding to differ=
ent
parts of the application. A
Microsoft.Net Class ‘XML URL Resolver” p=
rovides
functions using the XSD fil=
es to
check the validity of an XML customer file, information about errors found
are published. |
Modification
of the IP address
|
To take=
into
account a new processor IP address it’s necessary to put it Off the=
n On.
It is also imperative that the connector is present on the processor to a=
void
that the previous IP address stays valid |
Jean-Pi=
erre
Ferrero/Aut/Schneider@Europe