ABB BMI library 07 Minerals Library Communication Objects 5p1s4a

8/19/2019 ABB BMI library 07 Minerals Library Communication Objects 5p1s4a

1/25

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.Ó Copyright 2013 ABB. All rights reserved.

Based on Project BU Minerals LibraryPrep. ATBPA/P.Topfmeyer, N.Beringer 18.01.2006

Appr. ATBPA/M.Knabenhans 18.01.2006Doc. kind Reference Manual Doc. ItemTitle Communication Objects des. des.

I System 800xA Minerals Library 5.1/4 Resp. dept. CHIND / ATBPADocument identity Lang. Rev. ind. Sheet 1

ABB Switzerland Ltd 3BHS 161559 en I No. of sh. 25Template: Design Description_1,1_A4h_en_standard.dot; Filename: 07 Minerals Library Communication Objects 5p1s4a.docx; Print: 9/16/2013 9:29:00 AM; Save: 9/14/2013 4:36:00 PM; CHIND No. 3BHS102547 ZAB E01 Rev A. -; I-Q

Communication Objects

Reference Manual

Control – AC800M – Minerals Library

Operation – Process Portal A - AC800M Connect – Minerals Library

Version 5.1/4a


2/25


Doc. kind Reference Manual Project BU Minerals Library

Title Communication ObjectsIIT System 800xA Minerals Library 5.1/4

Document number Lang. Rev. ind. Pages 2

ABB Switzerland Ltd 3BHS 161559 en I No. of p. 25

CONTENT

1 SUMMARY ................................................................................................................ 3

2 PCC_Com_Drive ...................................................................................................... 32.1 Basic Description ............................................................................................. 32.2 CONTROL ....................................................................................................... 4

2.2.1 Diagram Graphical Representation ..................................................... 42.2.2 Parameter Description......................................................................... 4

2.2.3 Data Type Definition ............................................................................ 52.2.4 Application Example ............................................................................ 62.2.5 Communication Error Control .............................................................. 7

2.3 OPERATION.................................................................................................. 112.3.1 Alarm & Event List ............................................................................. 11

2.3.1.1 Status ................................................................................ 112.3.1.2 Alarm Message .................................................................. 11

3 PCC_Com_Signal ................................................................................................... 123.1 Basic Description ........................................................................................... 123.2 CONTROL ..................................................................................................... 12

3.2.1 Diagram Graphical Representation ................................................... 12

3.2.2 Parameter Description....................................................................... 123.2.3 Data Type Definition .......................................................................... 123.2.4 Application Example .......................................................................... 12

4 GCC_Com_M .......................................................................................................... 134.1 Basic Description ........................................................................................... 134.2 CONTROL ..................................................................................................... 13

4.2.1 Diagram Graphical Representation ................................................... 134.2.2 Parameter Description....................................................................... 134.2.3 Commmunication Error Handling Options via ComErrCtrl ................. 144.2.4 Data Type Definition .......................................................................... 154.2.5 Application Example .......................................................................... 15

5 GCC_Com_S .......................................................................................................... 165.1 Basic Description ........................................................................................... 165.2 CONTROL ..................................................................................................... 16

5.2.1 Diagram Graphical Representation ................................................... 165.2.2 Parameter Description....................................................................... 165.2.3 Data Type Definition .......................................................................... 185.2.4 Application Example .......................................................................... 18

6 MMS_COM .............................................................................................................. 196.1 BASIC DESCRIPTION ................................................................................... 196.2 CONTROL ..................................................................................................... 19

6.2.1 Control Module location ..................................................................... 19

6.2.2 Parameter description ....................................................................... 196.2.3 Data Type description ....................................................................... 206.3 Data types...................................................................................................... 20

6.3.1 Data types for MMS Communication between controllers ................. 206.3.2 Data types connection in the application ........................................... 226.3.3 Application Example .......................................................................... 23

7 DOCUMENT REVISION HISTORY.......................................................................... 25


3/25






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 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 toPCC Bus

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

· Indication of blocked signals from connected signals is transferred viaPCC_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.

· Support forwarding PCC.Action10 (which is presented for fast interlocking) to PCC

bus.

Note that fast interlock is not fast when signal connected to parent viaPCC_Com. But Action10 still forwarding thru PCC Bus.

Fast interlocking is only executed in the “Fast” Task if the DIS is connecteddirectly to a parent in the same diagram.


4/25






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 Type Direction

FDPort

Init ial Value Descr iption

1 PCCComSignalDiagName string[15] in 1 INIT: Enter the Name (max 15 Char) of theDiagram holding the PCC_Com_SignalDiagram Name (blank not allowed)

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

3 PCC_ComIn PCC_ComData in 1 IN: Connect to communication variable andshall 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_Safety INIT:PCC_Disabled;No_Interlock;PD_PrevDrive;IA

_Process;IA_Process_RFS;IB_Equipment;IB_Equipment_RFS;IC_Safety;IC_Safety_RFS;Auto_Start

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 willdisconnect if ComError,1=keep lastvalue,2=apply "IntlkTypeComErr" and"IntlkDirComErr" value

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

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

10 ComWDTime time in no cBMI.Time10s INIT: Communication Watchdog SupervisionTime

11 ComErrAlarm BoolAL out 1 default OUT: Communication Error, Available to useas interlock group or other members

For more information on how to use Interlock Parameters, see chapter PCC Interlock Parameter Description in.theBasic Objects Manual.


5/25






2.2.3 Data Type Definition

Together with the PCC_Com_Drive Control Module Type a structured Data TypePCC_ComData is available. This make it possible to create one global communicationvariable in the application for each PCC_Com_Drive instance.

PCC_ComData contains the two components Forward, Reverse

PCC_ComData; components

Name Data Type Attributes InitialValue

ISPValue

Description

1 Forward PCC_ComFwdData retain hidden PCC Data from Master to Slave2 Reverse PCC_ComRevData retain hidden

reversePCC Data from Slave to Master

PCC_ComFwdData; components

Name DataType

Att ributes Ini tial Value ISPValue

Description

1 Action1 dword retain nosort cBMI.PCC_ActionConst.NoInterlock

16#0 IN Interlock Action for H2(AIS/PID) or Alarm (DIS) to beexecuted

2 Action2 dword retain nosort cBMI.PCC_ActionC

onst.NoInterlock

16#0 IN Interlock Action for H1

(AIS/PID) or Warning (DIS) to beexecuted


16#0 IN Interlock Action for PHi(AIS/PID) to be executed


16#0 IN Interlock Action for PLo(AIS/PID) to be executed


16#0 IN Interlock Action for L1(AIS/PID) to be executed


16#0 IN Interlock Action for L2(AIS/PID) to be executed


16#0 IN Interlock Action for ROC (AIS)to be executed


16#0 IN Interlock Action for DEVH (PID)to be executed

9 Action9 dword retain nosort cBMI.PCC_ActionC

onst.NoInterlock

16#0 IN Interlock Action for DEVL (PID)

to be executed10

Action10 dword retain nosort cBMI.PCC_ActionConst.NoInterlock

16#0 IN Interlock Action for Fast to beexecuted

11

AEInd PCCAEInd

retain nosortdisplayvalue

Indication of most actual objectwith warning or error to bepresented on higher level

12

WatchDog

dint hidden 1 -999 WatchDog to indicate thatcommunication still alive, if it's notcounting means communicationlost

13

ChildFor ced

bool nosorthidden

false IN: Summary indication to parentthat at least one child is blocked /forced

14

IntlkParamErr

bool retain nosort false IN: Summary indication to parentthat at least one child has "PCC

Intlk Parameter Error"

PCC_ComRevData; components

Name DataType


Description

1 Name string[32]

retain nosort '' OUT PCC Bus main device. Eg.Motor, Valve, Group, etc.

2 Status1 dword retain nosort 0 OUT Status of the Motor, Group or Valve to be submitted to the IODevice e.g. AIS or DIS to controlthe AE behaviour, first faultdetection


6/25






Name DataType


Description

3 Status2 dword retain nosort 0 OUT Status of the Motor, Group or Valve to be submitted to the IODevice

4 ConnectState

dword nosorthidden

0 0 OUT: Set to Connected inStart_Code, used to decide if PCCis connected (but not working untilafter Start_Code obviously)

5 ResetChildForced

bool nosorthidden

false OUT: Reset "ChildForced" bit inPCC_Com_Signal

6 ResetIntlkParamErr

bool nosorthidden

false OUT: Reset "IntlkParamErr" bit inPCC_Com_Signal

2.2.4 Application Example

In the Application Code, the PCC_Com_Drive Block takes the same Position as a BasicObject (e.g. DIS), connected via PCC to a Drive. It is connected to exactly onePCC_Com_Signal Block using a Communiation Variable.The example for PCC_Com presented by following basic model.The 550_BC1.R1_F connected via D550_1_550BC1_PCC to 550_BC1.M2.

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

Communication variables is a unique Tag, defined as Output variable

D_550_2 is including PCC_Com_Drive and MOT2VVVF.

Same communication variable Tag, but defined as Input variable.

D_550_1First Diagram

UniqueCommunication

Variable

D_550_2Second Diagram


7/25






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 incase 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 again2 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”parameter.

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 communicationerror in the control module independent of the Communication Variable State. This is onlypossible for the application engineer by access to "IntPar.SimComErr" variable in CBMonline mode in the CM instance.

This test must only be done in simulated Controllers or with disconnectedFieldbus.


8/25






Scenario is first communication fail and then rope switch fail. In this example Normposition for rope switch signal is false.

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


9/25






If ComErrCtrl is configured as 1, this would mean the Last forwarded value viaPCC_Com_Signal will remain on parent PCC bus and it will not update until thecommunication be available again.

In this case if the rope switch fails and trips the drive and then communication fails, theInterlock will remain on the Drive as long as the Communication is not available as inbelow screenshot>.

.


10/25






In case the Parameter ComErrCtrl is configured as 2, the predefined action configured viathe "IntlkTypeComErr"/"IntlkDirComErr" Parameter is applied. This is the correct way todefine the communication error for any Safety or Machine Interlock.

In below screenshot, the communication failed and the drive tripped as by the followingconfiguration on the PCC_Com_Drive: IntlkTypeComErr = IC_Safety_RFSIntlkDirComErr = DirXY

Drive trip by communication failure.

A

For person and equipment safety, the interlock configuration must alwaysequal the highest configured PCC Interlock connected to thePCC_Com_Signal, and the PCC_Com_Drive must use ComErrCtrl=2.


11/25






2.3 OPERATION

2.3.1 Alarm & Event List

2.3.1.1 Status

The following conditions creates an event message for PCC_Com_Drive on parent eventlist.

· Communication Error. The Communication Failure can be a Failure, Warning or Event depending on ComErrTr Parameter value.

2.3.1.2 Alarm Message

An alarm message is generated by communication error and the AlarmDelay timeelapsed. Then the message is the following:

[PCCComSignalDiagName] + [cBMI.AE.PCCComErrTxt] + [Severity]

Where PCCComSignalDiagName is a parameter defined at the PCC_Com_Drive CM inthe Control Builder, while cBMI.AE.PCCComErrTxt and Severity texts are ProjectConstants.


12/25






3 PCC_Com_Signal


The Control Module Type PCC_Com_Signal extends the PCC bus to another diagramand/or application by communication variable.

The PCC_Com_Signal supports the following functions:

· Transfers the Interlock Action and Alarm State from PCC Bus to CommunicationVariable

· 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 PCCbus.

Note that fast interlock is not fast when signal connected to parent viaPCC_Com. But Action10 still forwarding thru PCC Bus.

Fast interlocking is only fast when DIS connected directly to parent in samediagram.

3.2 CONTROL


The default view is shown. It’s possible to modify the visible ports in CBM.


No

Name Data Type Direction

FDPort

Ini tial Value Descr ipt ion

1 PCC_ComOut PCC_ComData Out 1 default OUT: Connect to communication variable andshall 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 signals,PCC Connect etc


Together with the PCC_Com_Signal Control Module Type a structured Data TypePCC_ComData is available. This make it possible to create one global communicationvariable in the application for each PCC_Com_Signal instance.

For the data type definition refer to chapter PCC_Com_Drive.


For an example refer to chapter PCC_Com_Drive.


13/25






4 GCC_Com_M


The Control Module Type GCC_Com_M extends the GrpDrvBus to another diagramand/or application 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 fromGrpCycleCtrl will not be transferred to the GCC_Com_S CM.

.

4.2 CONTROL





FDPort


1 GCCComSlaveDiagName

string[15] in yes INIT: Enter the Name (max 15 Char)of the Diagram holding theGCC_Com_S Diagram Name (blanknot allowed)

2 GrpDrvConIn GrpDrvCon in_out

yesleft

IN/OUT: Connection to GrpDrvConfrom Group

3 GCC_ComOut GCC_ComData

out yes OUT: Connect to communicationvariable. This Com Var shall define inmaster 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. Treatedwith ComErrCtrl = 3 andSlaveDiagSelected = false : -1 no AE;0 = Event ; 1,2,3 = ALPrio#(1=lowest)


14/25







FDPort


6 SlaveDiagSelected

bool in no true IN: Select / Deselect execution of Slave Diagram incase of ComErrCtrl =3 and ComErrAlarm is active. (Workslike pre-selection)

7 SlaveDiagPreSel string[50] in yes cBMI.Empty_str

IN: PreBins the Slave Diagram isassigned to. Syntax: P1&P2|P3&N4 (=

P1 AND P2 OR P3 AND NOT P4). AND before OR. Max 5x OR. NoSpaces allowed

8 ComErrCtrl dint in no 3 IN: 0=Excl slave diag,1=keep lastvalue;2=not RFS,3=not RFS, applySlaveDiag(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 WatchdogSupervision Time

12 ComErrAlarm BoolAL out no default OUT: Communication Error, Availableto use as interlock group or other members

4.2.3 Commmunication Error Handling Options via ComErrCtrl

There are different possibilities to handle a communication error regarding the Indicationfor the Group, depending on what Equipment is located in the other Diagram. The defaultbehaviour 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 Diagram

disconnected. There is no indication to the Operator that anything is not running exceptthe Alarm of this Block itself. This Option is useful if the Equipment in the other Diagram is supplementary and not required to run the Group.

1 Freeze last Value The current values are kept while the communication is lost.

2 Not Ready The Group receives the Drives not Ready indication and will not be available to startfor the Operator.

3 Not Ready if Presel

If the Block is Pre-selected, the Group will indicate not Ready, otherwise the Group willbe ready and can be started. The Pre-selection should match with all Pre-selections for the Group Members placed in the connected Diagram, then it will still be possible toselect and start all Pre-selections depending on if they are affected by thecommunication breakdown.

4 Activate Standby Similar to 3, but the Group will start the Standby Pre-selection in case the Block isselected running and there is a standby selection active when the CommunicationError gets active. For this case the Consumers in the Slave Diagram should beconfigured to stop at a Communication Error (Interlock from GCC_Com_SComErrAlarm Output).

Note that QuickStop, SeqIntX and SeqIntY (i.e. Sequence Interlocks fromDriveGroup) are not forwarded anymore in case of communication error.

If these are used, the Equipment on the Slave Diagram side needs to beconfigured to stop with the ComErrAlarm Output of GCC_Com_S.


15/25







Together with the GCC_Com_S Control Module Type a structured Data TypeGCC_ComData is available. This make it possible to create one global communicationvariable in the application for each GCC_Com_M instance.

GCC_ComData contains the two components Forward, Reverse

PCC_ComData; components

Name Data Type Attributes InitialValue

ISPValue

Description

1 Forward GCC_ComFwdData retain hidden GCC Data from Master to Slave2 Reverse GCC_ComRevData retain hidden

reverseGCC Data from Slave to Master


This screenshot shows a Group with 2 Devices in the same Diagram, connected directlyto 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.


16/25






5 GCC_Com_S


The Control Module Type GCC_Com_S extends the GrpDrvBus to another diagramand/or application 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 theBlock, connecting PREBIN Blocks to GCC_Com_S is not supported andthe 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.



FDPort


1 GCCComSlaveDiagName

string[15] in yes INIT: Enter the Name (max 15 Char)of the Diagram holding theGCC_Com_S Diagram Name (blanknot allowed)

2 GrpDrvConIn GrpDrvCon in_ou

t

yes

left

IN/OUT: Connection to GrpDrvCon

from Group

3 GCC_ComOut GCC_ComData

out yes OUT: Connect to communicationvariable. This Com Var shall define inmaster diagram as "OUT" var withsame Data Type as "GCC_ComData"

4 ComErrTr dint in no 3 INIT: Com Error Alarm treatment:1,2,3 = ALPrio# (1=lowest)


17/25







FDPort

Init ial Value Descr iption

5 ComWarnTr dint in no 2 INIT: Com Error treatment. Treatedwith ComErrCtrl = 3 andSlaveDiagSelected = false : -1 no AE;0 = Event ; 1,2,3 = ALPrio#(1=lowest)

6 SlaveDiagSelecte

d

bool in no true IN: Select / Deselect execution of

Slave Diagram incase of ComErrCtrl =3 and ComErrAlarm is active. (Workslike pre-selection)

7 SlaveDiagPreSel string[50] in yes cBMI.Empty_str

IN: PreBins the Slave Diagram isassigned to. Syntax: P1&P2|P3&N4 (=P1 AND P2 OR P3 AND NOT P4). AND before OR. Max 5x OR. NoSpaces allowe

8 ComErrCtrl dint in no 3 IN: 0=Excl slave diag,1=keep lastvalue;2=not RFS,3=not RFS, applySlaveDiag(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 WatchdogSupervision Time

12 ComErrAlarm BoolAL out no default OUT: Communication Error, Availableto use as interlock group or other members


18/25







Together with the GCC_Com_M Control Module Type a structured Data TypeGCC_ComData is available. This make it possible to create one global communicationvariable in the application for each GCC_Com_S instance.


This screenshot shows a GCC_Com_S with a Communication Variable as Input and 2Devices connected to its GrpDrvConOut.

Note: To connect multiple Groups to a consumer, use the GroupStep Function Block asdescribed in the Group Objects Manual.


19/25






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.

6.1 BASIC DESCRIPTIONThe MMS_COM Control Module Type is used to establish and supervise thecommunication between two AC800M controllers. One sending and one receiving variableof 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 MProfessional.

6.2.2 Parameter descriptionNo Name Data Type Initial Value Description

1 Name string[20] 'Name' INIT: Tag name of the MMS Object. USE SAME ASReceiveDataName !! (. : - ok, no blanks allowed!)

2 Description string[40] 'Description' IN: Description text for the MMS object

3 IO MMSComData IN/OUT: Connection to MMSComData variable

4 PartnerTCPIP string[40] INIT: Name of the remote System5 SendData AnyType IN/OUT: Connection to the structured variable for sending data6 SendDataName string[32] INIT: Name of the structured variable in the remote system7 ReceiveData AnyType IN/OUT: Connection to the structured variable for receiving data8 ReceiveData

Namestring[32] INIT: Name of the structured variable in the remote system

9 ReadCycleTime time 2s INIT: MMS Read Cycle Time10 ReadTimeOut time 15s INIT: Time Out for reading data

11 Class dint 1 INIT: AE Class 1 ... 9999 (Section)12 Severity dint 950 INIT: AE Severity for MMS Communication Alarm (1...1000)


20/25






6.2.3 Data Type description

Together with MMS_COM Control Module Type a Structured Data Type MMS_COMDatais available.

MMS_COMData; componentsName Data Type Attributes Initial

ValueDescription

1 EnCom bool retain true IN: Enabling of Communication and Supervision2 ComError bool retain

nosort

OUT: Summary indication of a comunication 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 communicationlibrary shall be built up.

The Name of the library shall be: MMS_

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:· N_N e.g. Sending data from N1 to N2

· N_N e.g. Receiving data in N1 from N2

The variables of structured data type might contain any type of components / variables butthe structure must not exceed 1000 bytes.


21/25


22/25






The project specific communication data type might contain any type of components / variables but thestructure must not exceed 1000 bytes. In the following example, the controller B1 sends 2 digital outputsto 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 followingexample, the controller N1 exchanges data with controllers N2, N3, N4, N5 and N6.

Project Specific

Data Types

Standard

Data Types


23/25







The following example shows how can be a consumer, i.e. one-direction Motor, controlledfrom two different controller.

The controller N1 sends the needed digital outputs to the controller N2.

The controller N2 receives the needed signals


24/25






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


25/25





7 DOCUMENT REVISION HISTORY

Rev.ind.

Page (P)Chapt. (C)

Description Date/Initials

A Initial Version 20.05.2003/PVGB Update for Minerals Library Release 2.0/1 09.09.2003/GPCC Update for Minerals Library Release 2.1/1 05.04.2004/GPCD 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/GPCF Update for Minerals Library Release 4.0/0 27.05.2005/HTG Update for Minerals Library Release 5.0/0 16.01.2006/N.BH Update for Minerals Library Release 5.1/4

Introduce PCC_Com_Drive and SignalIntroduce GCC_Com_M / S

02.05.2013/YM

I 4.2.3 Describe ComErrCtrl Options for GCC_Com_M 02.09.2013/LK

Documents

ABB BMI library 07 Minerals Library Communication Objects 5p1s4a