2. 2
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Table of content
Why standard function bloc
Presentation of Standard Function bloc
Program organization
Rules for symbolic names
3. 3
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Why standard function blocs ?
To improve readability :
Standard function blocs contributes to a better readability of a program.
They mask parts of program which are identical or which are not useful for a better
understanding.
They can be used for
function used more than once
complex function
Several OEM can work on a same project. With standard function bloc,
they use the same function bloc for a same mechanical function.
R
EA
D
A
B
ILITY
R
EA
D
A
B
ILITY
Note : Explanations can be found in the Renault guide EB03.07.010.
This guide describes all the rules for quality programming
4. 4
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Why standard function blocs ?
To improve quality :
FB used by OEM are tested, validated and optimized to
work with SCUBE environment (HMI, safety, monitoring tool,
production order, …)
To reduce time limit of programming
Up to 80% of PLC programming is made from standard subroutines
Most than 80% of HMI screens is standardized
Q
U
A
LITY
Q
U
A
LITY
TIM
E
LIM
IT
TIM
E
LIM
IT
5. 5
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Why standard function bloc ?
FB have been created to be in
accordance with the Renault guide
EB03.07.010.
This guide describes all the rules
for quality programming
Extract of chapter 6
6. 6
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
What is a standard function bloc ?
A function bloc is a program that can be used by the OEM when a mechanical function is
installed in a plant. This function bloc has inputs (ex : safety datas), outputs (ex : diagnosis).
The function has been tested, validated and is ready to use by the OEM
An integration guide explains how to use the function bloc
Each FB starts with a short explanation of it’s own aim
An HMI (IHMP or WinCC screens) is delivered with some of function blocs
Creation
Specification of each FB has been done by Renault
Development is done by Siemens
Validation is done by Renault
Improvement
If an improvement is necessary, Renault asks for a modification
Siemens modify the standard function bloc
The change is validated by Renault
7. 7
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
What is a standard function bloc ?
Example
A standard function bloc has been developped to manage the identification system
BF_ident (n°
2015) : read / write RF300 Id tag
The OEM installs an identification system.
Identification components chosen for SCUBE are :
RF340R
RF180C
RF360T
PN
The OEM can manage this system in his program by using the standard function
bloc n°2015
Inputs to complete :
- mode (write or read)
- DBNR (DB which contents the data to write)
- ASMAddr (address of the RF180C)
- …
Ouputs to complete :
- diagnosis
- …
8. 8
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
What is a standard function bloc ?
Standard function blocs are integrated in their environment. Some inputs and
outputs are dedicated to special functions
Input « com » for safety informations
Input « pilot » and output « diag » for HMI exchanges
Other inputs or outputs are used for the animation of the program
Example : BF_MOUV2P1 (n°
2042) : Positions movement c ontrol
DB SAFETY
HMI screens for exploitation and
maintenance (IHMP or WinCC)
9. 9
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
Types of screens linked with standard function blocs :
Exploitation screens (IHMP for MOP, WinCC for LOP)
Display of defaults
Help to restart installation
Operation mode selection
Flux management
Manuel product line order
Maintenance screens (WinCC for MOP and LOP)
Display exchange informations between components (robot, jig, …)
Display state of a component
Selection of special functions for maintenance operations (unactivate
robot hanger, …)
…
10. 10
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
Input pilot
This input receives informations directly from HMI screens to the standard function
bloc.
START
Input « pilot » and output « diag » are used for exchanges between
standard FB and HMI screens
11. 11
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
Output diag
This output sends directly informations from the standard function bloc to HMI screens
Default management
Display of the default on the default screen
Display of reasons and solutions screens
Display of location screens
12. 12
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
BF_MOUV2P1 (n°
2042) : Positions movement control
Exploitation screen : display of default
Click on the text
for more detail
Fitting fault on zone n°
1
13. 13
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
BF_MOUV2P1 (n°
2042) : Positions movement control
Help to restart installation
Backward
connected
Reasons of the
problem
Solutions to solve the problem
Location
14. 14
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
BF_MOUV2P1 (n°
2042) : Positions movement control
Help to restart installation (location of the default)
Backward
connected
15. 15
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
BF_MOUV2P1 (n°
2042) : Positions movement control
Help to restart installation (location of the default)
16. 16
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by a standard function bloc
output diag
This output sends directly informations from the standard function bloc to HMI
Default management
Display management for HMI
Display of the default on the default screen
Display of reasons and solutions screens
Display of location screens
Display exploitation screen
Display maintenance screen
17. 17
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by standard function bloc
BF_MOUV2P1 (n°
2042) : Positions movement control
Exploitation screen : selection of movement
Movement 1
Movement 2
Movement 3
Backward
Forward
Sub assembly n°
1
19. 19
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by standard function bloc
Maintenance screen : display of informations for a component
ex : robot
Order
Order for
robot’s tool
Events
Events for tool
Welding state
Position of robot
20. 20
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
HMI management by standard function bloc
Maintenance screen for a LOP : PROFINET diagnosis
I/O Device number
on the network
Error
Help
Network name
21. 21
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
List of standard function blocs
FB are used to manage :
SAFETY
SAFETY HMI
NETWORK LEVELS
OPERATION MODE
PART MANAGEMENT
HMI
IDENTIFICATION
ROBOT
CONVEYOR FUNCTION
MOVEMENT CONTROL
Liste_BF.xls
22. 22
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
List of standard function blocs
BFS_came_robot- 1706- Safety robot cam control
GE03.FP.300
1706
BFS_came_Robot
Safety
BFS_CR -1705- Safety relay control
GE03.FP.297
1705
BFS_CR
Safety
BF_CRM -1704- Safety ground fault relais control
GE03.FP.296
1704
BFS_CRM
Safety
BFS_Air -1703- Pneumatic panel check control
GE03.FP.295
1703
BFS_Air
Safety
BFS_Porte 1702 Service panel on access fence control
GE03.FP.294
1702
BFS_Porte (BI)
Safety
BFS_Bsect r-1701- Safety delayed loop check and control
GE03.FP.293
1701
BFS_Bsectr
Safety
BFS_Bsec-1700- Safety loop check and control
GE03.FP.292
1700
BFS_Bsec
Safety
BF_Ihmair -1948- Pneumatic safety panel MMI control
GE03.FP.285
1948
BF_Ihmair
Safety_HMI
BF_Ihmporte -1947- Safety SAP MMI control
GE03.FP.286
1947
BF_Ihmporte (BI)
Safety_HMI
BF_IHMBsec -1944- Safety loop MMI
GE03.FP.289
1944
BF_IHMBsec
Safety_HMI
BF_IHMBsectr -1943- Safety loop delayed MMI control
GE03.FP.290
1943
BF_IHMBsectr
Safety_HMI
BF_IHMCRM -1942- Ground fault relay MMI control
GE03.FP.291
1942
BF_IHMCRM
Safety_HMI
BF_IHMCR - 1941- Relay check MMI control
GE03FP298
1941
BF_IHMCR
Safety_HMI
BF_IHMcame_robot -1940- Robot cam MMI control
GE03.FP.299
1940
BF_IHMcame_robot
Safety_HMI
BF_IHM_F_MUT_P -1934- HMI management for anti-
intrusion
GE03.FP.307
1934
BF_IHM_F_MUT_P
Safety_HMI
BF_IHM_F_2H_EN -1933- HMI management for bi-
manual command
GE03.FP.308
1933
BF_IHM_F_2H_EN
Safety_HMI
Description
PEGI number
Number
Name
Category
23. 23
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
List of standard function blocs
BF_Robot-2016- Interface PLC == Robots
GE03.FP.227
2016
BF_Robot
Robot control
BF_RB_SERVICE-1997- Robots to service position control
GE03.FP.242
1997
BF_RB_SERVICE
Robot control
BF_RB_COD_PREH_API-1953- Robot tooling control through PLC
GE03.FP.284
1953
BF_RB_COD_PREH_API
Robot control
BF_Butee_convoyeur2-2007- Overhead stop station control
GE03.FP.232
2007
BF_Butee_convoyeur2
Conveyor
BF_MB_BUTEE1-2002- Part stock device stop station control
GE03.FP.237
2002
BF_MB_BUTEE1
Conveyor
BF_MB_CHAINE1-2001- Part stock device motor control
GE03.FP.238
2001
BF_MB_CHAINE1
Conveyor
BF_Tab_stock2-1996- Stop and go roller table control
GE03.FP.243
1996
BF_Tab_stock2
Conveyor
BF_G120S - 1939- Command and HMI for Safety G120 Motor drive
GE03.FP.305
1939
BF_G120S
Conveyor
BF_Mouv_PL4M-1938- 4 positions turnplate 2 directions control
GE03.FP.301
1938
BF_Mouv_PL4M
Conveyor
BF_MouPL2M- 1937- 2 positions turnplate 2 directions control
GE03.FP.302
1937
BF_MouPL2M
Conveyor
BF_TAB_PAS- 1936- Stop and go roller bed table control
GE03.FP.303
1936
BF_TAB_PAS
Conveyor
BF_G120DS - 1935- Command and HMI for Safety G120D Motor
drive
GE03.FP.306
1935
BF_G120DS
Conveyor
BF_MOUV2P1-2042-2 Positions movement control
GE03.FP.207
2042
BF_MOUV2P1
Movement
control
BF_MOUVMP1-2041-Multi positions movement control
GE03.FP.208
2041
BF_MOUVMP1
Movement
control
BF_MVSE2P1-2040-single effect movement control
GE03.FP.209
2040
BF_MVSE2P1
Movement
control
BF_ILOT-2004- Information Islet attached management
GE03.FP.235
2004
BF_ILOT
Operation Mode
BF_Zone_Mode_IHMP-1963- Area: Panels modes and adjusment
command control
GE03.FP.274
1963
BF_Zone_Mode_IHMP
Operation Mode
Description
PEGI number
Number
Name
Category
24. 24
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
List of standard function blocs
BF_DIAG_PROFINET-2036- Profinet diagnosis
GE03.FP.213
2036
BF_DIAG_PROFINET
network_level 0
BF_act_desact-2033- Set and inhibit of profinet segment
GE03.FP.215
2033
BF_act_desact
network_level 0
BF_mt -2029- ETH PLCs exchanges control
GE03.FP.218
2029
BF_mt
Network_level 1
BF_B_VIEAPI-2006- Communication check between PLCs
GE03.FP.233
2006
BF_B_VIEAPI
network_level 1
BF_Modbus slave CP340-1959- Modbus slave with 340 board
GE03.FP.278
1959
BF_Modbus slave
CP340
network_level 1
BF_API_MAITRE_CAL-2031- Exchange PLC -- Plant host computer
control ( PLC management )
GE03.FP.216
2031
BF_API_MAITRE_CA
L
Network_level 2
BF_CPT_PIECE-2021- Jobs counter
GE03.FP.224
2021
BF_CPT_PIECE
Network_level 2
BF_TCY_SUIV-2019- SMP Jobs cycle times control
GE03.FP.226
2019
BF_TCY_SUIV
Network_level 2
BF_MobusTCPIPslave-1961- Modbus Tcpip slave with 343-1-lean board
GE03.FP.276
1961
BF_MobusTCPIPslave
Network_management
save_ DB to Winccflex- MOP part database back-up control
GE03.FP.283
Pas de
FB
Sauvegarde_ DB sur
Winccflex
Part_management
BF_DFB_FIFO-2039- FIFO stack control
GE03.FP.210
2039
BF_DFB_FIFO
Part_management
BF_TF_MP-2038- Transfer 16 bits structure and delete
GE03.FP.211
2038
BF_TF_MP
Part_management
BF_TF_TP-2037- Transfer of memory part tables
GE03.FP.212
2037
BF_TF_TP
Part_management
BF_RUP_FLU-2020- SMP flow break management
GE03.FP.225
2020
BF_RUP_FLU
Part_management
BF_DATABASE1-2005- Database management control
GE03.FP.234
2005
BF_DATABASE1
Part_management
BF_MARIAGE_API-2003- PLCs management control for parts mariage
GE03.FP.236
2003
BF_MARIAGE_API
Part_management
BF_MMC-2000- Back-up and restore on MMC
GE03.FP.239
2000
BF_MMC
Part_management
BF_RECALAGE-1998- Reinitializing prod.order points management control
GE03.FP.241
1998
BF_RECALAGE
Part_management
Description
PEGI number
Numb
er
Name
Category
25. 25
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
List of standard function blocs
BF_ident-2015- Read / write of RF300 Id tag ( RFID )
GE03.FP.228
2015
BF_ident
RFID
BF_PFLEX_PUP-1999- Re-encoding pallett panel control
GE03.FP.240
1999
BF_PFLEX_PUP
HMI
BF_IHM_wincc-1962- Winccflexible screens send and
receive control
GE03.FP.275
1962
BF_IHM_wincc
HMI
BF_AFF_ ALPHA NUM -1955-gestion afficheur alpha_Num
26 caractères
GE03.FP.282
1955
BF_AFFICHEUR ALPHA
NUM (2*13)
HMI
BF_Opmaint-2022- LOPs maintenance screens and forcing
tags control
GE03.FP.223
2022
BF_Opmaint
LOP
Maintenance
Description
PEGI number
Number
Name
Category
26. 26
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
The PLC program structure and
the installation organisation are
related :
Level « ilot » (management of
datas common to all the
installation)
Level « Zone » (management of
datas common to a zone – the
definition of a zone is linked to
the safety )
Level « Assembly »
(management of datas common
to an assembly ex : robot)
The order of those levels in the
PLC program depends of de
piece flow
Zone 1 Zone 2
Assembly 1
Assembly 2
27. 27
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
FB100,DB100: management zone 1
FB101, DB101 : management assembly 1
FB102, DB102 : management assembly 2
FB180, DB180 : …
There is
one FB to manage each zone
one FB to manage each assembly
Example :
FB100/DB100 manage the zone 1
FB102/DB102 manage the assembly 2 of the zone 1
Each FB is linked with one DB. The DB has got the
same number to find it quickly
Why FB instead of FC ?
Because when you use an FB, the DB instance is automatically build by STEP7
28. 28
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
FB1, DB1 à FB79, DB79
FB100,DB100: management zone 1
FB101, DB101 : management assembly 1
FB102, DB102 : management assembly 2
FB180, DB180 : …
FB 1 to 79 are used to managed datas which
concerned all the « îlot »
Each FB is linked with one DB. The DB has got the
same number
29. 29
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
FC900, : zone 9
FB1, DB1 à FB79, DB79
FC1 ilot
FC100 : zone 1
FB100,DB100: management zone 1
FB101, DB101 : management assembly 1
FB102, DB102 : management assembly 2
FB180, DB180 : …
All FB are called by an FC. There is
FC1 called all FB which manage the « îlot »
FC100 called all FB which manage the zone 1 and her sub-
assemblies
FC200 called all FB which manage the zone 2 and her sub-
assemblies
…
30. 30
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
OB1
FC900, : zone 9
FB1, DB1 à FB79, DB79
FC1 ilot
FC100 : zone 1
FB100,DB100: management zone 1
FB101, DB101 : management assembly 1
FB102, DB102 : management assembly 2
FB180, DB180 : …
All FC are called by the OB1
31. 31
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
PLC Program organization
OB1
FB100,DB100: gestion zone 1
FB101, DB101 : Table1
FB102, DB102 : Robot 1
FB180, DB180 : …
FC900, : zone 9
FBxx : BF_Mouv2p
FBxx : BF_Mouv2p
FB1, DB1 à FB79, DB79
FC1 ilot
FC100 : zone 1
Standard function blocs can be called from FB
which managed a zone or an assembly
Standard function blocs are multi-instance (no DB
of instance, variables are stored in the DB linked to
the FB which called the standard function bloc)
ex : FB101 call BF_Mouv2p. So variables used by
BF_Mouv2p are stored in DB101. Those variables
are created automatically
Several instances of BF_Mouv2p can be used in the
FB101
32. 32
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Labels standardization for bloc
To identify the type of function bloc in a program, the names will be as below :
FB standard Renault :
BF_ Title of the function (ex : BF_ident)
FB standard Safety :
BFS_ Title of the function
FB OEM :
BI_ Title of the function
Number are reserved for each type of function bloc
1600 to 1649 : FB OEM
1650 to 1699 : FB Siemens (Standard FB already in STEP7 to manage communication, …)
1700 to 2047 : FB Renault
33. 33
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Labels standardization for bloc
Each blocs has got a symbolic name. This name has been chosen to display blocs on Simatic Manager
in an order similar to the flux of production.
FB
X_YYYW_ZZZZZZZZZZ
X : number of zone
YYYW : order of succession in the flux
ZZZZ : name of the mechanical function
DB linked to an ilôt
Ixx
xx : number of the FB
DB linked to a zone
Zy
Y : number of zone
DB linked to an assembly
Z$yyy
$ : number of zone
Yyy : number of assembly
34. 34
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
1°Variables which doesn’t belong to a standard FB :
Name of DB
instance
Variable name
FB1 :
S1dfapi S2dfapi
FB2004
BF_Ilot
Def_api
instance =
Ilot
S1dfapi
Dcihmp
S1ihmdc
OB1
FB1,’’0_01_ILOT’’ FB2004 = BF_ilot
DB1 ‘’I01’’,instance des BF niveau ilot
FC 100 (1_00_CycleZ1)
1
1
2
2
Labels standardization for variables
I01.S1dfapi
I01.S2dfapi
I01.S1ihmdc
35. 35
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
2°Variables belonging to a standard FB :
Name of DB
instance
Name of standard
FB instance
Name of variable
Labels standardization for variables
OB1
FB100,’’1_01_zone 1’’ FB1962 = BF_Zone_modes_ihm
DB100 ‘’Z1’’,instance des BF niveau Zone 1
FB1962BF_Zone_mo
des_ihm
Diag
instance =
Z1Modes
FC 100 (1_00_CycleZ1)
Z1.Z1modes.Diag
1
2
1
2
3
3
The names of instance for BF must be respected to insure the links
between the program machine and the IHMP + software
36. 36
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Labels standardization for bloc
OB1
FB1,’’0_01_ILOT’’ BF_ilot
DB1 ‘’I01’’, instance des BF (DFB) niveau ilot
DB99 ‘’IG’’,
general info ilot
DB98 ‘’IIP’’,
Word part info
BF_diag_profinet
available DB94 à
DB93 for RF 300
or other part
information
FC1 , (0_00_cycle Ilot), définition cyclique Ilot
FB2, (0_02_’mmc) BF_mmc
DB2 ‘’I02’’, instance des BF (DFB)fonction Pcmcia
DB2036 ’’DB_PN’’, DB instance for BF profinet
DB97 ‘’IIS’’,
wort Support info
DB96 ‘’IIT’’,
Array part info
DB95 ‘’IBD’’,
data base part
info
Or
And / without
Or /And/ Without
FB3, (0_03_’xOP) BF_IHM_WINCC
DB3 ‘’I03’’, instance des BF
DB90 ‘’Pile’’,
for Fifo info
DB89 à 80‘Sipx’’,
siptol data
information
DB2005 “TALO”
local data base part
info
available DB92 à
DB 91
Type of Part information:
- 16 bools / part:
- 20 Words / part
-120 Words / part (or more)
Ilot Informations used by all zones
In Blue, informations are in Global Data Block
This DB is made manually
Example
37. 37
26/02/2008
Presentation function blocs
SCUBE
DIRECTION DES
AUTOMATISMES ET DU
DEVELOPPEMENT DU SPR
Labels standardization for bloc
FB100, (1_01_zone 1)
FB101 :(1_A0_ Table1)
FB102 : ‘’1_A01_Montbrid’’
BF_Mouv2P1
FB103 : ‘’1_R1_Robsoud1’’
BF_Mouv2P1
BF_RB_abb_kuka
BF_Zone_modes_IHMP
DB100 ‘’Z1’’, BF(DBF) Level Zone 1
DB101 ‘’Z1A0’’, BF(DBF) instance assembly
DB102 ‘’Z1A01’’, BF(DBF) Instance Assembly
DB103 ‘’Z1R1’’, BF(DBF) Instance Assembly
FC100 , (1_00_cycle Z1), définition cyclique zone1
BF_Mouv2p1
FB200, (2_01_zone 2) BF_Zone_modes_IHMP
DB200 ‘’Z2’’, BF(DBF) Level Zone 1
FC200 , (2_00_cycle Z2), définition cyclique zone2
Example OB1
DB199 ‘’Z1G’’,
Zone1 information
DB299 ‘’Z2G’’,
Zone2 information
DB198 ‘’Z1IT’’,
Z1 time movement
DB298 ‘’Z2IT’’,
Z1 time movement