07 3BHS161559-612 MinLib Communication Objects

—
R E FE R E NC E MA NUA L
Communication Objects
Control – AC800M – Minerals Library
PREPARED STATUS SECURITY LEVEL
2021-10-05 N. Carvalho Draft Public

APPROVED DOCUMENT KIND
2021-12-03 G.Schuetz Manual

OWNING ORGANIZATION DOCUMENT ID. REV. LANG. PAGE
IAPI ABB Switzerland 3BHS161559-612 L en 1/28

© Copyright 2021 ABB. All rights reserved.
COM MU NI CAT I O N OB J ECTS
Contents
1. Summary ...................................................................................................................................... 3
2. PCC_Com_Drive ........................................................................................................................... 3
2.1. Basic description .........................................................................................................................3
2.2. Control ............................................................................................................................................3
2.2.1. Diagram Graphical Representation........................................................................3
2.2.2. Parameter Description ............................................................................................. 4
2.2.3. Data Type Definition .................................................................................................5
2.2.4. Application Example ................................................................................................. 6
2.2.5. Communication Error Control ................................................................................. 7
2.3. Operation..................................................................................................................................... 12
2.3.1. Alarm & Event List .................................................................................................... 12
3. PCC_Com_Signal ....................................................................................................................... 13
3.1. Basic description ....................................................................................................................... 13
3.2. Control .......................................................................................................................................... 13
3.2.1. Diagram Graphical Representation...................................................................... 13
3.2.2. Parameter Description ............................................................................................ 13
3.2.3. Data Type Definition ............................................................................................... 13
3.2.4. Application Example ................................................................................................14
4. GCC_Com_M .............................................................................................................................. 15
4.2. Control .......................................................................................................................................... 15
4.2.3. Communication Error Handling Options via ComErrCtrl ................................ 16
4.2.4. Data Type Definition ...............................................................................................18
4.2.5. Application Example ................................................................................................18
5. GCC_Com_S ............................................................................................................................... 19
5.2. Control .......................................................................................................................................... 19
5.2.3. Data Type Definition ............................................................................................... 21
5.2.4. Application Example ................................................................................................ 21
6. MMS_COM .................................................................................................................................. 22
6.1. Basic description .......................................................................................................................22
6.2. Control ..........................................................................................................................................22
6.2.1. Control Module location .........................................................................................22
6.2.2. Parameter description ............................................................................................22
6.2.3. Data Type description.............................................................................................23
6.3. Data types ...................................................................................................................................23
6.3.1. Data types for MMS Communication between Controllers ............................23
6.3.2. Data types connection in the application ......................................................... 25
6.3.3. Application Example ............................................................................................... 26
7. Revisions ................................................................................................................................... 28
STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE
Draft Public 3BHS161559-612 L en 2/28

We reserve all rights in this document and the information contained therein. Reproduction, use or disclosure to third parties without express authority is strictly forbidden.
© Copyright 2021 ABB Switzerland Lt
COM MU NI CAT IO N OB J ECTS
1. Summary
This document contains a detailed description of the following communication modules:
– PCC_Com_Drive
– PCC_Com_Signal
– GCC_Com_M
– GCC_Com_S
– MMS_COM
2. PCC_Com_Drive
2.1. Basic description

The Control Module Type PCC_Com_Drive extends the PCC bus to another diagram and/or
application by communication variable.
The PCC_Com_Drive supports the following functions:
– Transfers the Interlock Action and Alarm State from the Communication Variable to PCC
Bus
– Transfers the Drive State in PCC Bus to the Communication Variable
– Indication of blocked signals from connected signals is transferred via PCC_Com_Drive for
indication in the faceplate and graphic element of the consumer /parent object.
– Alarm and indication in parent/drive FPL for communication Error.
– Configurable behaviour during communication Error.
– Configurable supervision time and Alarm Delay for communication error.
Note that fast interlock is not executed in Fast Task when PCC is connected via
PCC_Com, the Interlock Action is however still forwarded thru PCC Bus.
Fast interlocking is only executed in the “Fast” Task if the DIS is connected directly
to a parent in the same diagram.
2.2. Control
2.2.1. Diagram Graphical Representation
The default view is shown, it’s possible to modify the visible ports in CBM.

2.2.2. Parameter Description

No Name Data Direc- FD Initial Description
Type tion Port Value
1 PCCComSignalDi- string in 1 INIT: Enter the Name (max 15 Char) of the

agName [15] Diagram holding the PCC_Com_Signal Dia-
gram Name (blank not allowed)
2 DrivePCC PCCCom out 1 OUT: Connecttion to motor etc PCC bus

Data
3 PCC_ComIn PCC_Co in 1 IN: Connect to communication variable and

mData shall define in diagram where Parent is as
"IN" var with same Data Type as
"PCC_ComData"
4 ComErrTr dint in 1 3 INIT: Communication Error Alarm treatment:

1,2,3 = ALPrio# (1=lowest)
5 IntlkTypeComErr dint in 1 IC_Saf INIT:

ety PCC_Disabled;No_Interlock;PD_PrevDrive;IA
_Pro-
cess;IA_Process_RFS;IB_Equipment;IB_Equi
pment_RFS;IC_Safety;IC_Safety_RFS;Auto_S
tart
6 IntlkDirComErr dint in 1 DirXY INIT: DirX; DirXStart; DirY; DirYStart; DirXY;

DirXYStart
7 ComErrCtrl dint in 1 2 IN: Com error action: 0=no ErrCtrl, PCC will
disconnect if ComError,1=keep last
value,2=apply "IntlkTypeComErr" and
"IntlkDirComErr" value
8 AlarmDelay time in 1 cBMI.Ti INIT: ComError delay time

me2s
9 Class dint in no 1 INIT: AE Class 1 ... 9999 (Section)
10 ComWDTime time in no cBMI.Ti INIT: Communication Watchdog Supervision

me10s Time
11 ComErrAlarm BoolAL out 1 default OUT: Communication Error, Available to use

as interlock group or other members
For more information on how to use Interlock Parameters, see chapter PCC Interlock Param-
eter Description in the Basic Objects Manual.

2.2.3. Data Type Definition

Together with the PCC_Com_Drive Control Module Type a structured Data Type
PCC_ComData is available. This makes it possible to create one communication variable in
the application for each PCC_Com_Drive instance.
PCC_ComData contains the two components Forward, Reverse
PCC_ComData; components:
Name Data Type Attributes Initial ISP Description

Value Value
1 Forward PCC_ComFwdData retain hidden PCC Data from Master to Slave
2 Reverse PCC_ComRevData retain hidden PCC Data from Slave to Master

reverse
PCC_ComFwdData; components:
Name Data Attrib- Initial Value ISP Description

Type utes Value
1 Action1 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for H2 (AIS/PID)
sort onst.NoInterlock or Alarm (DIS) to be executed
2 Action2 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for H1 (AIS/PID)
sort onst.NoInterlock or Warning (DIS) to be executed
3 Action3 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for PHi (AIS/PID)
sort onst.NoInterlock to be executed
4 Action4 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for PLo
sort onst.NoInterlock (AIS/PID) to be executed
5 Action5 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for L1 (AIS/PID)
6 Action6 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for L2 (AIS/PID)
7 Action7 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for ROC (AIS) to
sort onst.NoInterlock be executed
8 Action8 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for DEVH (PID)
9 Action9 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for DEVL (PID) to
sort onst.NoInterlock be executed
10 Action10 dword retain no- cBMI.PCC_ActionC 16#0 IN Interlock Action for Fast to be
sort onst.NoInterlock executed
11 AEInd PCCAEI retain no- Indication of most actual object

nd sort dis- with warning or error to be pre-
playvalue sented on higher level
12 Watch- dint hidden 1 -999 WatchDog to indicate that commu-

Dog nication still alive, if it's not count-
ing means communication lost

13 Child- bool nosort false IN: Summary indication to parent

Forced hidden that at least one child is blocked /
forced
14 Intlk- bool retain no- false IN: Summary indication to parent

ParamErr sort that at least one child has "PCC
Intlk Parameter Error"
PCC_ComRevData; components:
No Name Data Type Attrib- Initial ISP Description

utes Value Value
1 Name string [32] retain '' OUT PCC Bus main device. Eg. Motor,
nosort Valve, Group, etc.
2 Status1 dword retain 0 OUT Status of the Motor, Group or

nosort Valve to be submitted to the IO Device
e.g., AIS or DIS to Control the AE be-
haviour, first fault detection
3 Status2 dword retain 0 OUT Status of the Motor, Group or

nosort Valve to be submitted to the IO Device
4 ConnectState dword nosort 0 0 OUT: Set to Connected in Start_Code,

hidden used to decide if PCC is connected
(but not working until after
Start_Code obviously)
5 ResetChildForced bool nosort false OUT: Reset "ChildForced" bit in

hidden PCC_Com_Signal
6 ResetIntlkParamErr bool nosort false OUT: Reset "IntlkParamErr" bit in

hidden PCC_Com_Signal
2.2.4. Application Example

In the Application Code, the PCC_Com_Drive Block takes the same Position as a Basic Object
(e.g., DIS), connected via PCC to a Drive. It is connected to exactly one PCC_Com_Signal Block
using a Communication Variable.
An example for PCC_Com is given by following schematic drawing of the Blocks involved.
The Signal 550-BC1.R1_F is connected via D550_1_550BC1_PCC to the Consumer 550-BC1.M2

located in another Diagram.
D_550_1 Unique Commu- D_550_2

First Diagram nication Variable Second Diagram
D_550_1 is including DIS signal and PCC_Com_Signal (Refer to chapter PCC_Com_Signal).

A Communication Variable is required to have a Name unique within the System, and defined
Direction out on the PCC_Com_Signal side:
D_550_2 is including PCC_Com_Drive and MOT2VVVF.
The Communication Variable is defined with the same Name, but with Direction in. Note that
it is not allowed to connect the Communication Variable to multiple PCC_Com_Drive or
PCC_Com_Signal Blocks. Each PCC_Com_Drive / PCC_Com_Signal Pair must be connected
with its own individual Communication Variable.
2.2.5. Communication Error Control

The behaviour of the CM in case of communication error can be adjusted via Parameters.
With the ComErrCtrl Parameter the PCC action is defined, which will be sent over PCC in case
of communication error:
ComErrCtrl Description
0 PCC interlock will be disconnected (No Interlock)
1 Last forwarded value via PCC_Com_Signal will remain on parent PCC bus and it
will be kept until communication is available again
2 Apply the action defined by "IntlkTypeComErr"/"IntlkDirComErr" Parameter
To extend the supervision time for communication use the “ComWDTime” parameter.
To extend the delay until a Communication error is generated use the “AlarmDelay” parame-
ter.
To achieve different error treatment (color) configure the “ComErrTr”.
The Parameter “ComErrAlarm” is available in CM and it can be used in glue logic.
Additionally, simulation is available for PCC_Com_Drive to simulate the communication error

in the Control module independent of the Communication Variable State. This is only possible
for the application engineer by access to "IntPar.SimComErr" variable in CBM online mode in
the CM instance.

COM MU NI CAT IO N O B J ECTS
This test must only be done in simulated Controllers or with disconnected Fieldbus.
Scenario is first communication fail and then rope switch fail. In this example Norm position
for rope switch signal is false.

Because of communication failure (e.g. Controller halt), rope switch disconnect from
PCC_Com_Drive. As shown in above screenshot the Rope Switch failure does not trip the belt
conveyor.

If ComErrCtrl is configured as 1, this would mean the Last forwarded value via
PCC_Com_Signal will remain on parent PCC bus and it will not update until the communica-
tion be available again.
In this case if the rope switch fails and trips the drive and then communication fails, the Inter-
lock will remain on the Drive as long as the Communication is not available as in below
screenshot>.

In case the Parameter ComErrCtrl is configured as 2, the predefined action configured via the
"IntlkTypeComErr"/"IntlkDirComErr" Parameter is applied. This is the correct way to define
the communication error for any Safety or Machine Interlock.
In below screenshot, the communication failed and the drive tripped as by the following con-
figuration on the PCC_Com_Drive:
IntlkTypeComErr = IC_Safety_RFS
IntlkDirComErr = DirXY
Figure 1 - Drive trip by communication failure.
For person and equipment safety, the interlock configuration must always equal
the highest configured PCC Interlock connected to the PCC_Com_Signal, and the
PCC_Com_Drive should use ComErrCtrl=2.

2.3. Operation
There are no Faceplates or Graphic Elements for PCC_Com_Drive. The Block is “transparent”
for the Operator.
2.3.1. Alarm & Event List
2.3.1.1. Status
The following conditions creates an event message for PCC_Com_Drive on parent event list.
– Communication Error. The Communication Failure can be a Failure, Warning or Event de-
pending on ComErrTr Parameter value.
2.3.1.2. Alarm Message
An alarm message is generated by communication error and the AlarmDelay time elapsed.
Then the message is the following:
[PCCComSignalDiagName] + [cBMI.AE.PCCComErrTxt] + [Severity]
Where PCCComSignalDiagName is a parameter defined at the PCC_Com_Drive CM in the Con-

trol Builder, while cBMI.AE.PCCComErrTxt and Severity texts are Project Constants.

3. PCC_Com_Signal

The Control Module Type PCC_Com_Signal extends the PCC bus to another diagram and/or
application by communication variable.
The PCC_Com_Signal supports the following functions:
– Transfers the Interlock Action and Alarm State from PCC Bus to Communication Variable
– Transfers the Drive State from Communication Variable to PCC Bus
– Indication of blocked signals from connected signals is transferred via PCC for indication
in the faceplate and graphic element of the consumer /parent object.
– Supports forwarding PCC.Action10 (which is presented for fast interlocking) via PCC bus.
Note that Direction fast Interlocks are not fast when a signal is connected to the
parent via PCC_Com. but it is still forwarded thru PCC Bus.
Fast interlocking is only fast when a DIS connected directly to the parent in the
same diagram.
3.2. Control
The default view is shown. It’s possible to modify the visible ports in CBM.

No Name Data Type Direc- FD Initial Description
tion Port Value
1 PCC_ComOut PCC_ComData Out 1 default OUT: Connect to communication variable
and shall define in diagram where Signals
are as "OUT" var with same Data Type as
"PCC_ComData"
2 SignalPCC PCCComData in_out 1 default IN/OUT: Connecttion to PCC bus of sig-

nals, PCC Connect etc

Together with the PCC_Com_Signal Control Module Type a structured Data Type
PCC_ComData is available. This makes it possible to create one global communication varia-
ble in the application for each PCC_Com_Signal instance.

COM MU NI CAT IO N OB J EC TS
For the data type definition refer to chapter PCC_Com_Drive.

For an example refer to chapter PCC_Com_Drive.

4. GCC_Com_M

The Control Module Type GCC_Com_M extends the GrpDrvBus to another diagram and/or ap-
plication by communication variable.
The GCC_Com_M supports the following functions:
– Transfers GrpDrvBus to a Communication Variable
– Supports all Functions of the GROUP.
GrpCycleCtrl is not supported as a Master, and the Commands from GrpCycleCtrl

will not be transferred to the GCC_Com_S CM.
4.2. Control

No Name Data Type Direc- FD Initial Description
tion Port Value
1 GCCCom- string [15] in yes INIT: Enter the Name (max 15
SlaveDiagNam Char) of the Diagram holding the
e GCC_Com_S Diagram Name
(blank not allowed)
2 GrpDrvConIn Grp- in_out yes IN/OUT: Connection to Grp-
DrvCon left DrvCon from Group
3 GCC_ComOut GCC_Com out yes OUT: Connect to communication
Data variable. This Com Var shall de-
fine in master diagram as "OUT"
var with same Data Type as
"GCC_ComData"
4 ComErrTr dint in no 3 INIT: Com Error Alarm treatment:
1,2,3 = ALPrio# (1=lowest)

5 ComWarnTr dint in no 2 INIT: Com Error treatment.

Treated with ComErrCtrl = 3 and
SlaveDiagSelected = false: -1 no
AE; 0 = Event ; 1,2,3 = ALPrio#
(1=lowest)
6 SlaveDiagSelec bool in no true IN: Select / Deselect execution of
ted Slave Diagram in case of
ComErrCtrl = 3 and ComErrAlarm
is active. (Works like pre-selec-
tion)
7 SlaveDiag- string [50] in yes cBMI. IN: PreBins the Slave Diagram is
PreSel Empt assigned to. Syntax:
y_str P1&P2|P3&N4 (= P1 AND P2 OR P3
AND NOT P4). AND before OR.
Max 5x OR. No Spaces allowed
8 ComErrCtrl dint in no 3 IN: 0=Excl slave diag,1=keep last
value;2=not RFS,3=not RFS, apply
SlaveDiag(Pre)Sel ,4=not RFS, ac-
tivate stby as in SlaveDiagPreSel
9 AlarmDelay time in no cBMI. IN: ComError delay time
Time
2s
11 ComWDTime time in no cBMI. INIT: Communication Watchdog
Time1 Supervision Time
0s
12 ComErrAlarm BoolAL out no de- OUT: Communication Error,
fault Available to use as interlock
group or other members
4.2.3. Communication Error Handling Options via ComErrCtrl

There are different possibilities to handle a communication error regarding the Indication for
the Group, depending on what Equipment is located in the other Diagram. The default behav-
iour is to indicate “Not Ready” in case the Block is Preselected (Option 3).
No Name Description
0 None The Group is continuing to work with all the Consumers in the other Dia-
gram disconnected. There is no indication to the Operator that anything
is not running except the Alarm of this Block itself. This Option is useful
if the Equipment in the other Diagram is supplementary and not re-
quired to run the Group.
1 Freeze last The current values are kept while the communication is lost.
Value
2 Not Ready The Group receives the Drives not Ready indication and will not be avail-
able to start for the Operator.

3 Not Ready if If the Block is Pre-selected, the Group will indicate not Ready, otherwise
Presel the Group will be ready and can be started. The Pre-selection should
match with all Pre-selections for the Group Members placed in the con-
nected Diagram, then it will still be possible to select and start all Pre-
selections depending on if they are affected by the communication
breakdown.
4 Activate Similar to 3, but the Group will start the Standby Pre-selection in case
Standby the Block is selected running and there is a standby selection active
when the Communication Error gets active. For this case the Consumers
in the Slave Diagram should be configured to stop at a Communication
Error (Interlock from GCC_Com_S ComErrAlarm Output).
Note that QuickStop, SeqIntX and SeqIntY (i.e. Sequence Interlocks from Drive-
Group) are not forwarded anymore in case of communication error.
If these are used, the Equipment on the Slave Diagram side needs to be configured
to stop with the ComErrAlarm Output of GCC_Com_S.


Together with the GCC_Com_S Control Module Type a structured Data Type GCC_ComData is
available. This makes it possible to create one global communication variable in the applica-
tion for each GCC_Com_M instance.
GCC_ComData contains the two components Forward, Reverse
PCC_ComData; components:
Name Data Type Attributes Initial ISP Description

Value Value
1 Forward GCC_ComFwdData retain hidden GCC Data from Master to Slave
2 Reverse GCC_ComRevData retain hidden GCC Data from Slave to Master

reverse

This screenshot shows a Group with 2 Devices in the same Diagram, connected directly to the
IOGrpDrvCon and a GCC_Com_M Block that extends the Group to another Diagram via the
“GR_555_1_D_555_3_GCC” Communication Variable.
There must always be a pair of Control Modules GCC_Com_M and GCC_Com_S connected to-
gether with an individual Communication Variable. It is not allowed to interconnect multiple
GCC_Com_M with multiple GCC_Com_S Blocks.

5. GCC_Com_S

The Control Module Type GCC_Com_S extends the GrpDrvBus to another diagram and/or ap-
plication by communication variable.
The GCC_Com_S supports the following functions:
– Transfers a Communication Variable to GrpDrvBus
– Supports multiple Drives connected to the GrpDrvBus similar to the GROUP itself
5.2. Control
While the GrpDrvConOut Port is configured to show on both sides of the Block, con-
necting PREBIN Blocks to GCC_Com_S is not supported and the Preselection will
not be transferred to the Group via GCC_Com_M.
All Pre-selections must be contained in the Main Diagram, directly connected to the GROUP.

No Name Data Type Direc- FD Initial Value Description
tion Port
1 GCCCom- string[15] in yes INIT: Enter the Name (max 15

SlaveDiagName Char) of the Diagram holding
the GCC_Com_S Diagram Name
(blank not allowed)
2 GrpDrvConIn GrpDrvCon in_out yes IN/OUT: Connection to Grp-

left DrvCon from Group
3 GCC_ComOut GCC_ComData out yes OUT: Connect to communication

variable. This Com Var shall de-
fine in master diagram as "OUT"
var with same Data Type as
"GCC_ComData"

4 ComErrTr dint in no 3 INIT: Com Error Alarm treat-

ment: 1,2,3 = ALPrio# (1=lowest)
5 ComWarnTr dint in no 2 INIT: Com Error treatment.

Treated with ComErrCtrl = 3 and
SlaveDiagSelected = false : -1 no
AE; 0 = Event ; 1,2,3 = ALPrio#
(1=lowest)
6 SlaveDiagSelected bool in no true IN: Select / Deselect execution

of Slave Diagram incase of
ComErrCtrl = 3 and ComEr-
rAlarm is active. (Works like pre-
selection)
7 SlaveDiagPreSel string[50] in yes cBMI.Empty_str IN: PreBins the Slave Diagram is

assigned to. Syntax:
P1&P2|P3&N4 (= P1 AND P2 OR
P3 AND NOT P4). AND before
OR. Max 5x OR. No Spaces al-
lowe
8 ComErrCtrl dint in no 3 IN: 0=Excl slave diag,1=keep last

value;2=not RFS,3=not RFS, ap-
ply SlaveDiag(Pre)Sel ,4=not
RFS, activate stby as in
SlaveDiagPreSel
9 AlarmDelay time in no cBMI.Time2s IN: ComError delay time
11 ComWDTime time in no cBMI.Time10s INIT: Communication Watchdog

Supervision Time
12 ComErrAlarm BoolAL out no default OUT: Communication Error,

Available to use as interlock
group or other members


Together with the GCC_Com_M Control Module Type a structured Data Type GCC_ComData
is available. This makes it possible to create one communication variable in the application
for each GCC_Com_S instance.

This screenshot shows a GCC_Com_S with a Communication Variable with Direction in and 2
Devices connected to its GrpDrvConOut.
Note: To connect multiple Groups to a consumer, use the GroupConnect or GroupStep Blocks
as described in the Group Objects Manual.

6. MMS_COM
This Function Block should not be used in new Projects.
The new standard way for MMS, to define Communication Variables (IAC) in Control
Builder M should be used instead.

The MMS_COM Control Module Type is used to establish and supervise the communication
between two AC800M Controllers. One sending and one receiving variable of structured data
type, with up to 1000 bytes, is handled by one MMS_COM instance.
6.2. Control
6.2.1. Control Module location
The Control Module Type is located in the library BMIStandard for Control Builder M Profes-
sional.
6.2.2. Parameter description

No Name Data Type Initial Value Description
1 Name string [20] 'Name' INIT: Tag name of the MMS Object. USE
SAME AS ReceiveDataName !! (. : - ok, no
blanks allowed!)
2 Description string[40] 'Description' IN: Description text for the MMS object
3 IO MMSComData IN/OUT: Connection to MMSComData varia-
ble
4 Part- string [40] INIT: Name of the remote System
nerTCPIP
5 SendData AnyType IN/OUT: Connection to the structured varia-
ble for sending data
6 SendDat- string [32] INIT: Name of the structured variable in the
aName remote system
7 ReceiveData AnyType IN/OUT: Connection to the structured varia-
ble for receiving data
8 ReceiveData string [32] INIT: Name of the structured variable in the
Name remote system
9 Read- time 2s INIT: MMS Read Cycle Time
CycleTime
10 Read- time 15s INIT: Time Out for reading data
TimeOut
11 Class dint 1 INIT: AE Class 1 ... 9999 (Section)
12 Severity dint 950 INIT: AE Severity for MMS Communication
Alarm (1...1000)

6.2.3. Data Type description

Together with MMS_COM Control Module Type a Structured Data Type MMS_COMData is
available.
MMS_COMData; components
Name Data Attributes Initial Description

Type Value
1 EnCom bool retain true IN: Enabling of Communication and
Supervision
2 ComError bool retain no- OUT: Summary indication of a com-
sort munication error
6.3. Data types

6.3.1. Data types for MMS Communication between Controllers
For the MMS Communication between the Controllers a project specific communication li-
brary shall be built up.
The Name of the library shall be: MMS_<ProjectName>
For every node-to-node link two data types (one sending and one receiving) shall be created.
The names of the data type should be:
1. N<NodeNr1>_N<NodeNr2> e.g., Sending data from N1 to N2
2. N<NodeNr2>_N<NodeNr1> e.g., Receiving data in N1 from N2
The variables of structured data type might contain any type of components / variables, but
the structure must not exceed 1000 bytes.

The required structure for the communication is shown below:
Project Specific
Communication
Library
Data Types:
If N1_N2 is de-
fined, N2_N1
needs to be cre-
ated also
N1 corresponds
to Node 1
N2 corresponds
to Node 2
Standard
Communication
Data Type

The project specific communication data type might contain any type of components / varia-
bles, but the structure must not exceed 1000 bytes. In the following example, the Controller
B1 sends 2 digital outputs to the Controller B2.
6.3.2. Data types connection in the application

In the Application, the MMS_Type data type contains the sending and receiving links for each
Controller. The transmission is checked for each receiving channel. In the following example,
the Controller N1 exchanges data with Controllers N2, N3, N4, N5 and N6.
Project Specific Standard

Data Types Data Types


The following example shows how can be a consumer, i.e., one-direction Motor, Controlled
from two different Controller.
The Controller N1 sends the needed digital outputs to the Controller N2.
The Controller N2 receives the needed signals

The information exchange via the MMS Communication is used into the glue logic

7. Revisions
Rev. Page (P) Description Date Dept./Init.
Chapt. (C)
A Initial Version 20.05.2003/PVG
B Update for Minerals Library Release 2.0/1 09.09.2003/GPC
C Update for Minerals Library Release 2.1/1 05.04.2004/GPC
D Further Update for Minerals Library Release 2.1/1 11.07.2004/GPC
E Update for Minerals Library Release 3.1/1 04.08.2004/GPC
F Update for Minerals Library Release 4.0/0 27.05.2005/HT
G Update for Minerals Library Release 5.0/0 16.01.2006/N.B
H Update for Minerals Library Release 5.1/4 02.05.2013/YM
Introduce PCC_Com_Drive and Signal
Introduce GCC_Com_M / S
I 4.2.3 Describe ComErrCtrl Options for GCC_Com_M 02.09.2013/LK
J Formal changes for Release 6.0 13.09.2016/GS
K Update for Release 6.0/3 24.10.2018/LK
L All Update for Release 6.1/2 01.12.2021 / JM


07 3BHS161559-612 MinLib Communication Objects

Uploaded by

Document Information

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

07 3BHS161559-612 MinLib Communication Objects

Uploaded by

Copyright:

Available Formats

—

PREPARED STATUS SECURITY LEVEL

2021-10-05 N. Carvalho Draft Public

2021-12-03 G.Schuetz Manual

IAPI ABB Switzerland 3BHS161559-612 L en 1/28

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 2/28

2.1. Basic description

The PCC_Com_Drive supports the following functions:

– Transfers the Drive State in PCC Bus to the Communication Variable

– Alarm and indication in parent/drive FPL for communication Error.

– Configurable behaviour during communication Error.

– Configurable supervision time and Alarm Delay for communication error.

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 3/28

2.2.2. Parameter Description

1 PCCComSignalDi- string in 1 INIT: Enter the Name (max 15 Char) of the

2 DrivePCC PCCCom out 1 OUT: Connecttion to motor etc PCC bus

3 PCC_ComIn PCC_Co in 1 IN: Connect to communication variable and

4 ComErrTr dint in 1 3 INIT: Communication Error Alarm treatment:

5 IntlkTypeComErr dint in 1 IC_Saf INIT:

6 IntlkDirComErr dint in 1 DirXY INIT: DirX; DirXStart; DirY; DirYStart; DirXY;

8 AlarmDelay time in 1 cBMI.Ti INIT: ComError delay time

9 Class dint in no 1 INIT: AE Class 1 ... 9999 (Section)

10 ComWDTime time in no cBMI.Ti INIT: Communication Watchdog Supervision

11 ComErrAlarm BoolAL out 1 default OUT: Communication Error, Available to use

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 4/28

2.2.3. Data Type Definition

PCC_ComData contains the two components Forward, Reverse

Name Data Type Attributes Initial ISP Description

1 Forward PCC_ComFwdData retain hidden PCC Data from Master to Slave

2 Reverse PCC_ComRevData retain hidden PCC Data from Slave to Master

Name Data Attrib- Initial Value ISP Description

11 AEInd PCCAEI retain no- Indication of most actual object

12 Watch- dint hidden 1 -999 WatchDog to indicate that commu-

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 5/28

13 Child- bool nosort false IN: Summary indication to parent

14 Intlk- bool retain no- false IN: Summary indication to parent

No Name Data Type Attrib- Initial ISP Description

2 Status1 dword retain 0 OUT Status of the Motor, Group or

3 Status2 dword retain 0 OUT Status of the Motor, Group or

4 ConnectState dword nosort 0 0 OUT: Set to Connected in Start_Code,

5 ResetChildForced bool nosort false OUT: Reset "ChildForced" bit in

6 ResetIntlkParamErr bool nosort false OUT: Reset "IntlkParamErr" bit in

2.2.4. Application Example

The Signal 550-BC1.R1_F is connected via D550_1_550BC1_PCC to the Consumer 550-BC1.M2

D_550_1 Unique Commu- D_550_2

D_550_1 is including DIS signal and PCC_Com_Signal (Refer to chapter PCC_Com_Signal).

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 6/28

D_550_2 is including PCC_Com_Drive and MOT2VVVF.

2.2.5. Communication Error Control

To achieve different error treatment (color) configure the “ComErrTr”.

The Parameter “ComErrAlarm” is available in CM and it can be used in glue logic.

Additionally, simulation is available for PCC_Com_Drive to simulate the communication error

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 7/28

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 8/28

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE

Draft Public 3BHS161559-612 L en 9/28

STATUS SECURITY LEVEL DOCUMENT ID. REV. LANG. PAGE