MasterNet User S Guide 3BSE003839R301

ABB Automation
3BSE002142R1
CONTENTS
1 GENERAL INFORMATION ................................ 3

1.1 Scope and Objectives ............................ 3
1.2 Related documents .............................. 3
2 HARDWARE .......................................... 4
2.1 Location of the circuit boards .................. 4
2.2 CPU board DSPC 172/172H ........................ 5
2.2.1 Strapping on CPU board DSPC 172, board DSPC
172-1 (Single CPU) .......................... 6
2.2.2 Strapping on CPU board DSPC 172H, board DSPC
172-1 (Redundant CPU) ........................ 6
2.2.2.1 Strapping on RWM Memory board DSMB 175 .... 7
2.3 Communication board DSCS 116 .................... 8
2.3.1 Strapping on communication board DSCS 116 .... 9
2.4 Communication board DSCA 114 .................... 10
2.4.1 Strapping on communication board DSCA 114 .... 10
2.5 Communication board DSCA 125 .................... 11
2.5.1 Strapping on communication board DSCA 125 .... 11
2.6 Communication board DSCS 140 and DSCS 145 ...... 12
2.6.1 Strapping on communication board DSCS 140 and
DSCS 145 .................................... 12
2.7 Communication board DSCS 150 .................... 13
2.7.1 Strapping on communication board DSCS 150 .... 14
3 INITIALIZING AND STARTUP .......................... 16

3.1 Database ........................................ 16
4 SYSTEM MESSAGES .................................... 17

4.1 CLAA01 .......................................... 17
4.1.1 Introduction ................................ 17
4.1.2 System messages .............................. 19
4.2 CLAA02 .......................................... 24
4.2.1 Introduction ................................ 24
4.2.2 System messages .............................. 25
4.3 CLAA03 .......................................... 26
4.3.1 Introduction ................................ 26
4.3.2 System messages .............................. 27
4.4 CLAA05 .......................................... 29
4.4.1 Introduction ................................ 29
4.4.2 System messages .............................. 30
3BSE002142R1 1(61)
ABB Automation
4.5 CLAA06 .......................................... 34

4.5.1 Introduction ................................ 34
4.5.2 System messages .............................. 35
4.6 CLAA07 .......................................... 36
4.6.1 Introduction ................................ 36
4.6.2 System messages .............................. 37
4.7 CLBA01 .......................................... 38
4.7.1 Introduction ................................ 38
4.7.2 System messages .............................. 38
4.8 CLBA02 .......................................... 39
4.8.1 Introduction ................................ 39
4.8.2 System messages .............................. 40
4.9 CLBA03 .......................................... 41
4.9.1 Introduction ................................ 41
4.9.2 System messages .............................. 42
4.10 CLBA04 .......................................... 43
4.10.1 Introduction ................................ 43
4.10.2 System messages .............................. 44
4.11 CLCA70 .......................................... 47
4.11.1 Introduction ................................ 47
4.11.2 System messages .............................. 47
4.12 CLEA00 .......................................... 48
4.12.1 Introduction ................................ 48
4.12.2 System messages .............................. 50
4.13 Appendix ........................................ 58
3BSE002142R1 2
ABB Automation
1
GENERAL INFORMATION
1.1
Scope and Objectives
This manual is a complement for the MasterGate 230/1 to the

MasterPiece 200/1 "INSTALLATION, COMMISSIONING AND SERVICE MANUAL".
1.2
Related documents
MasterGate 230/1 Technical description 3BSE002141R1

MasterPiece 200/1 Installation, Commissioning and
Service Manual 7650 043-205
MasterPiece 200/1 Design Manual 7650 099-203
MasterPiece 200/1 Configuration and Programming 7650 100-203
MasterNet User’s Manual 7650 107-202
3BSE002142R1 3
ABB Automation
2
HARDWARE
The hardware described in the MasterPiece 200/1 Design Manual is

not described in this manual.
2.1
Location of the circuit boards
Single CPU unit

―w―――w―w―w―――――――――――――――――――――――――――――――――――w―w―
| D |D|D| | D|
| S |S|S| | S|
| P |R|R| FREE TO USE FOR |B|
| C |B|B| COMMUNICATION BOARDS |C|
| 1 |1|1| |1|
| 7 |1|1| |7|
| 2 |0|0| |2|
| | | | | |
| | | | | |
| | | | | |
―v―――v―v―v―――――――――――――――――――――――――――――――――――v―v―
Dual CPU unit
―w―――w―w―w―――w―w―w―――w―――――――――――――――――――――――w―w―
| D |D|D| D |D|D| D | | D|
| S |S|S| S |S|S| S | |S|
| P |M|R| C |R|M| P | FREE TO USE FOR | B|
| C |B|B| L |B|B| C | COMMUNICATION BOARDS |C|
| 1 |1|1| 1 |1|1| 1 | | 1|
| 7 |7|1| 1 |1|7| 7 | |7|
| 2 |5|0| 0 |0|5| 2 | |2|
| H | | | A | | | H | | |
| | | | | | | | | |
| | | | | | | | | |
―v―――v―v―v―――v―v―v―――v―――――――――――――――――――――――v―v―
Communication boards :
All communication boards should be placed directly after the

shielding boards (DSRB 110) or the CPU board, with no space
between the communication boards, in the following order:
DSCS 116
DSCA 114
DSCA 125
DSCS 140
DSCS 145
DSCS 150
NOTE: DSCS 116 is not supported in a Dual CPU configuration.
3BSE002142R1 4
ABB Automation
2.2
CPU board DSPC 172/172H
Both the PROM and RWM memory is placed on the CPU board DSPC 172.
The PROM memory consists of one memory module DSMB 178 (1 MB)
mounted as shown below. In single configuration the required RWM
memory consists of the memory present on the DSPC 172-2 (0.5 MB).
l―――――――――――――――――――――――――――――――――――k
| DSPC 172-2 tk
| l――――――――――k l――――――――k ||
| | | | | ||
| | | | | W1 ||
| | QMG230/1 | | RWM | || strap W1 o-o
| | | | | ||
| | | | | ||
| | | | | tj
| m――――――――――j m――――――――j tk
| ||
| ||
| ||
| ||
| ||
| ||
| tj
m―――――――――――――――――――――――――――――――――――j
Figure 1 CPU board DSPC 172, board DSPC 172-2 and memory (Single CPU)
In redundant configuration the required RWM memory is contained in

two memory boards (DSMB 175).
l―――――――――――――――――――――――――――――――――――k
| DSPC 172-2 tk
| l――――――――――k ||
| | | ||
| | | W1 ||
| | QMG230/1 | || strap W1 o o
| | | ||
| | | ||
| | | tj
| m――――――――――j tk
| ||
| ||
| ||
| ||
| ||
| ||
| tj
m―――――――――――――――――――――――――――――――――――j
Figure 2 CPU board DSPC 172H, board DSPC 172-2 (Redundant CPU)
3BSE002142R1 5
ABB Automation
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | DSPC 172-1 tk
m――k| ||
|| S3 S11 ||
|| ||
|| S4 S6 S5 S8 ||
|| ||
|| tj
|| S13 tk
|| S10 ||
|| ||
|| ||
|| S9 ||
l――j| ||
| | S12 S1 tj
m――kt―――――――――――――――――――――――――――――――――――j
mj
Figure 3 CPU board DSPC 172/172H, board DSPC 172-1
2.2.1
Strapping on CPU board DSPC 172, board DSPC 172-1 (Single CPU)
S1 o o S3 o-o S4 o o o o S5 o o S6 o o S8 o-o
| | | |
o o o o o o o o o o o o o o
S9 o o S10 o-o S11 o o o o S12 o o S13 o o

| | | |
o o o o o o o o o o o o
2.2.2
Strapping on CPU board DSPC 172H, board DSPC 172-1 (Redundant CPU)
S1 o o S3 o-o S4 o o o o S5 o o S6 o o S8 o-o
| | | |
o o o o o o o o o o o o o o
S9 o o S10 o-o S11 o o o o S12 o o S13 o o

| | | |
o o o o o o o o o o o o
3BSE002142R1 6
ABB Automation
2.2.2.1
Strapping on RWM Memory board DSMB 175
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| ||
|| S6 ||
|| ||
|| S2 ||
|| ||
|| tj
|| S1 tk
|| ||
|| ||
|| ||
|| ||
l――j| ||
| | S3 S5 S4 tj
m――kt―――――――――――――――――――――――――――――――――――j
mj
S1 o-o o S3 o-o o S4 o-o S5 o-o S6 o o

o o-o o-o o o o o o o-o
o o-o o o
o o-o
o o-o
o o-o
o-o o
o o-o
S2 (Applies to CPU-left) S2 (Applies to CPU-right)
o o-o o o-o
o o-o o-o o
o-o o o o-o
o-o o o-o o
o-o o o-o o
o-o o o-o o
o-o o o-o o
o-o o o-o o
3BSE002142R1 7
ABB Automation
2.3
Communication board DSCS 116
The DSCS 116 board is used for synchronous communication

(X25.2 LAPB) with external computers.
NOTE: The DSCS 116 board is not supported in configurations
with dual CPU.
l―――――――――――k
| DSCS 116 | l―――k
| tk Cable DSTK 154 lu |
| |t――w――――――――――――――――――u| |...... External computer 1
| tj | Channel 0 mu |
m―――――――――――j | m―――j
| l―――k
| lu |
m――――――――――――――――――u| |...... External computer 2
Channel 1 mu |
m―――j
Connection unit DSTC 150 for 19,2 kbit/s
RS 232 and DSTC 141 for 50 kbit/s (coax)
3BSE002142R1 8
ABB Automation
2.3.1
Strapping on communication board DSCS 116
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| S5 S2 S4 S7 ||
|| S1 ||
|| S3 ||
|| ||
|| ||
|| S6 tj
|| tk
|| ||
|| ||
|| ||
|| ||
l――j| ||
| | tj
m――kt―――――――――――――――――――――――――――――――――――j
mj
S2 o o o S3 o o S4 o S5 o o S6 o o S7 o-o
| | | | |
o o o o o o o o o o
Board address (S1)

S1 Ext.comp ($30)
o o-o
o o-o
o o-o
o-o o
o-o o
o o-o
o o-o
o o o
3BSE002142R1 9
ABB Automation
2.4
Communication board DSCA 114
The DSCA 114 board is used for asynchronous communication

(ADLP-10 and EXCOM) with external computers.
l―――――――――――k
| DSCA 114 | l―――k
| |t――w―――――――――――――――――――u| |...... External computer
| tj | Channel 0 and 1 mu |
m―――――――――――j | m―――j
|
| l―――k
| Cable DSTK 152 lu |
m―――――――――――――――――――u| |...... External computer
Channel 2 and 3 mu |
m―――j
Connection unit DSTC 120 .
EXCOM = channel 0
ADLP-10 = channel 2 (ext.comp 3)
ADLP-10 = channel 3 (ext.comp 4)
2.4.1
Strapping on communication board DSCA 114
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| ||
|| ||
|| ||
|| ||
|| ||
|| S1 tj
|| tk
|| ||
|| ||
|| ||
|| ||
l――j| ||
| | tj
m――kt―――――――――――――――――――――――――――――――――――j
mj
S1 Board address
S1
o o o o o o o o 1
| | |
o o o o o o o o
| | | | |
o o o o o o o o 0
3BSE002142R1 10
ABB Automation
2.5
Communication board DSCA 125
The DSCA 125 board is used for MB 200 communication to own control
network.
l―――――――――――k
| DSCA 125 | l―――k
| tk Cable DSTK 114 lu t――――― Bus 0
| |t――――――――――――――――――――――u| |
| tj Channel 0 and 1 mu t――――― Bus 1
m―――――――――――j m―――j
Connection unit DSTC 160 .
2.5.1
Strapping on communication board DSCA 125
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| ||
|| ||
|| ||
|| S1 ||
|| ||
|| S2 tj
|| tk
|| ||
|| ||
|| ||
|| ||
l――j| ||
| | tj
m――kt―――――――――――――――――――――――――――――――――――j
mj
Board address (S1)
S1 First board ($10) Second board ($12)
o-o o o-o o
o o-o o-o o
o o-o o o-o
o o-o o o-o
o-o o o-o o
o o-o o o-o
o o-o o o-o
o o-o o o-o
S2
o-o
o-o
o-o
o-o
o-o
3BSE002142R1 11
ABB Automation
2.6
Communication board DSCS 140 and DSCS 145
The DSCS 140 board is used for MasterBus 300 and DSCS 145 for
MasterBus 300E communication. The DSCS 140/145 board is used for
communication to the own control network, to other MG 230/1 and to
Advant Station 500 nodes in the plant network.
l―――――――――――k
| DSCS 140/ | l―――k
| 145 tk Cable DSTK 126 lu |
| |t――――――――――――――――――――――u| |...... Transceiver
| tj Channel 0 mu |
m―――――――――――j m―――j
Connection unit DSTC 190.
2.6.1
Strapping on communication board DSCS 140 and DSCS 145
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| S12 ||
|| ||
|| ||
|| S10 S3 ||
|| ||
|| tj
|| S1 S14 S11 tk
|| ||
|| ||
|| S5 ||
|| S6 ||
l――j| S13 ||
| | tj
m――kt―――――――――――――――――――――――――――――――――――j
mj S8 S9 S10 S11
3BSE002142R1 12
ABB Automation
S1 o o S10 o-o S11 o-o S12 o o S13 o o S14 o o

| o o |
o o o o o o o-o o o o-o
o-o
o o
o-o
Base address (S3)

Board 1 ($57) Board 2 ($5F) Board 3 ($67) Board 4 ($6F)
o o-o o o-o o o-o o o-o
o-o o o o-o o-o o o o-o
o o-o o o-o o-o o o-o o
o-o o o-o o o o-o o o-o
o-o o o-o o o-o o o-o o
Network and node number for MB 300/300E is defined with switches

S5, S6, S8 and S9 according to below:
S5 defines bit 0-3 of the node number

S9 defines bit 0-3 of the network number

MG 230/1 node number in own control network should always be 127

($7F).
The switches S10 and S11 defines the MAC (Medium Access Control)
frame size according to below:
l―――――w―――――w――――――――――――k
| S10 | S11 | Frame size |
t―――――n―――――n――――――――――――u
| 0 | 0 | Fixed |
| $F | $F | Variable *)|
m―――――v―――――v――――――――――――j
*) For DSCS 140 valid from Rev.8.
2.7
Communication board DSCS 150
The DSCS 150 board is used for multidrop synchronous communication

(IEEE 802.3) with SuperView, Advant Station 800 and
external computers.
l―――――――――――k
| DSCS 150 | l―――k
| |t――――――――――――――――――――――u| |...... Transceiver
| tj Channel 0 mu |
m―――――――――――j m―――j
Connection unit DSTC 190.
3BSE002142R1 13
ABB Automation
2.7.1
Strapping on communication board DSCS 150
lk
l――jt―――――――――――――――――――――――――――――――――――k
| | tk
m――k| S12 ||
|| ||
|| ||
|| S10 S3 ||
|| ||
|| tj
|| S1 S14 S11 tk
|| ||
|| ||
|| S5 ||
|| S6 ||
l――j| S13 ||
| | tj
m――kt―――――――――――――――――――――――――――――――――――j
mj S8 S9 S10 S11
S1 o o S10 o-o S11 o-o S12 o o S13 o o S14 o o
| o o |
o o o o o o o-o o o o-o
o-o
o o
o-o
Base address (S3)1)

Board 1 ($87) Board 2 ($8F)
o o-o o o-o
o o-o o o-o
o o-o o o-o
o-o o o o-o
o-o o o-o o
o-o o o-o o
o-o o o-o o
o o-o o o-o
1)NOTE:
The DSCS 150 board used in an MP 200/1 system can not use the same
Base addresses as in an MG 230/1. The base addresses in an
MP 200/1 must be $57, $5F, $67, $6F, $77 or $7F. In the MP 200/1
the Base addresses are shared by DSCS 140, DSCS 145, DSCS 150 and
DSCA 180x.
3BSE002142R1 14
ABB Automation
Network and node number on the multidrop link are defined with
switches S5, S6, S8 and S9 according to below:


NOTE:
MG 230/1 network number on the multidrop link shall be in the
range 110..119. Node number should be equal to the own control
network number, i.e. network DIV 10 of any of the control network
buses. The external computers connected to the multidrop link
shall use node numbers between (control network * 10) and
(control network * 10 + 9). This means that external multidrop
computers can use node numbers 10..19 if they are connected
to MasterGate in control network 1, and 20..29 if connected
to MasterGate in control network 2, a.s.o.
EXAMPLE:
A DSCS 150 board that is installed in a MasterGate 230/1 in
control network number 3 (Control network address 31,127), shall
use network number in the range 110..119 and node number 3.
The external computers on this multidrop link can use the
node numbers 30..39.
Which MAC (Medium Access Control) frame size and SAP’s

(Service Access Point) that will be used are defined
with switches S10 and S11 according to below:
l―――――w―――――w―――――――――――――w――――――――――――――――――――――――――――k
| S10 | S11 | SAP’s (Hex) | MIN and MAX MAC frame size |
t―――――n―――――n―――――――――――――n――――――――――――――――――――――――――――u
| 0 | 0 | $10, $14 | 510 |
| 1 | 0 | $10, $14 | 64 - 1518 |
| 2 | 0 | $20, $24 | 64 - 1518 (Tesselator) |
m―――――v―――――v―――――――――――――v――――――――――――――――――――――――――――j
3BSE002142R1 15
ABB Automation
3
INITIALIZING AND STARTUP
The MG 230/1 will start after a cold start in

"configuration mode".
The MG 230/1 will act similar to a standard MP 200/1 except that

the database is not configured and dimensioned.
The database can not be reconfigured.
3.1
Database
The user database is configured and dimensioned for :

4 MB200 ( MB200A - MB200D )
1 EXCOM ( XCOM_1 )
The database must be populated (using MDB) for MB200 and EXCOM
in the same way as for MP 200/1.
The database can be dumped/loaded using one of the following

MasterAid commands :
1) DUAP : Dump Application Program

LOAP : Load Application Program
2) DURWM : Dump RWM

LORWM : Load RWM
3) DUDB : Dump database logical file 108 and 116

LODB : Load database logical file 108 and 116
LOAP must be done after coldstart (CLEAR) using the U option,

that turns off node identity checking between target and dump.
DURWM and LORWM must be done in off-line session.
Please note that the commands DUTDB and LOTDB can not be used with
MG 230/1.
3BSE002142R1 16
ABB Automation
4
SYSTEM MESSAGES
This part of the document lists all system messages that might
be generated from the MG 230/1 unique tasks.
System messages from the MasterBase SW package are not included.
(See the MP 200/1 INSTALLATION, COMMISSIONING AND SERVICE MANUAL).
System message printouts have the following appearance:
01 23S04*13:25:09 19 114 CXCC030 A H’FF37A1 H’00000025 3781

! ! ! ! ! ! ! ! ! ! !
! ! ! ! ! ! ! ! ! ! !
netw ! ! time ! ! task ! address data1 data2
node ! ! code aborted
slave number mtype
See the appendix for interpretations of the following variables in

the system messages:
- syserr
- acb.code
- bufstatu
- dlstatu
4.1
CLAA01
4.1.1
Introduction
The channel multiplexer, CLAA01, of MG 230/1 can report a number

of erroneous situations through system messages. A system message
from CLAA01 indicates a specific error condition, either in the
system itself or in the content of the database. The mtype and
mcodes used are listed below.
(* System messages trace identities *)
clmtype = 34
cldberr = 1 mcode for database errors

clstructerr= 3 mcode for structure errors in system or contents
of database.
clchanerr = 5 mcode for error at signal send
In the event of a database error during initiation the task will

be set up to pass all signals without any filtering. Still, this
is a serious error that has to be examined. In the case of a
structure error in the database, please change the illegal values
in the instance defined by dest_ch_id in the system message. Other
structure errors could be caused by faulty configuration signals
3BSE002142R1 17
ABB Automation
from point-to-point connected external computers. Signal send

errors are mostly queue full messages. These errors are only
reported once if repeated.
If the task aborts during initiation it means that one of two

possible errors has occurred. The actual abort reason is found as
data 1 in the abort message from the kernel. See below.
(* Abort error parameters *)
NoParamp = 2 Illegal pointer to parameter area

NoNetwNode = 3 Illegal netw or nodeno
Data 1 and Data 2 contains useful information about the

error. Data 1 often contains the type of error, see appendix,
whereas Data 2 shows various information depending on trace
number.
3BSE002142R1 18
ABB Automation
4.1.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| Trace no | Program/ | Procedure/ | Parameter description | Comments |
| (HEX) | subpgm | function | ( 1 = mtype, 2 = mcode,| |
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 01000001 | CLAA01 | init | 1: clmtype | Failed to |
| | | | 2: cldberr | get physinfo |
| | | | 3: acb.ccode | for log.file |
| | | | 4: logical file no | MG_FILTER_CTR |
| | | | | |
| 01000002 | CLAA01 | init | 1: clmtype | Failed to find|
| | | | 2: cldberr | first instance|
| | | | 3: acb.ccode | in log. file |
| | | | 4: logical file no | MG_FILTER_CTR |
| | | | | |
| | | | 4: logical file no | MG_FILTER_PLT |
| | | | | |
| | | | 4: logical file no | MG_FILTER_PLT |
| | | | | |
| 01000005 | CLAA01 | init | 1: clmtype | Failed to get |
| | | | 2: cldberr | conceptinfo |
| | | | 3: acb.ccode | for concept |
| | | | 4: - | MG_FILTER_CTR |
| | | | | |
| | | | 4: - | MG_FILTER_PLT |
| | | | | |
| | | | 4: logical file no | FLOW_CONTROL |
| | | | | |
| | | | 4: - | FLOW_CONTROL |
| | | | | |
| 01300001 | CLAA01 | main | 1: clmtype | Spec. filter |
| | | | 2: clstructerr | not defined |
| | | | 3: VALUE | for this VALUE|
| | | | 4: - | for DCSC00 |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 19
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 3: VALUE | for this VALUE|
| | | | 4: - | for DCTC50 |
| | | | | |
| | | | 3: dest_ch_id | for this |
| | | | 4: - | dest_ch_id. |
| | | | | |
| 01400001 | CLAA01 | local_send | 1: clmtype | Failed to send|
| | | | 2: clchanerr | signal to own |
| | | | 3: ORD (cxsyserr) | node DCWC10. |
| | | | 4: destination | |
| | | | | |
| | | | 3: ORD (cxsyserr) | node DCSC20. |
| | | | | |
| | | | 3: ORD (cxsyserr) | node CLAC10. |
| | | | 4: destination | (DCBCL0) |
| | | | | |
| 01400031 | CLAA01 | main | 1: clmtype | Illegal |
| | | | 2: clstructerr | dest_ch_id for|
| | | | 3: dest_ch_id | signal to own |
| | | | 4: - | node. |
| | | | | |
| 01401001 | CLAA01 | get_event | 1: clmtype | Illegal value |
| | | outports | 2: clstructerr | for event for |
| | | | 3: event | one external |
| | | | 4: ext comp no | computer ptp. |
| | | | | |
| 01401011 | CLAA01 | ptp_send | 1: clmtype | Failed to send|
| | | | 2: clchanerr | signal to ext |
| | | | 3: ORD (cxsyserr) | computer 1 ptp|
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 20
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | | |
| | | | | |
| 01402021 | CLAA01 | explicit | 1: clmtype | Failed to send|
| | | send | 2: clchanerr | ttd signal to |
| | | | 3: ORD (cxsyserr) | own ctrlnetw. |
| | | | 4: destination | High prio. |
| | | | | |
| | | | 4: destination | Normal prio. |
| | | | | |
| | | | 4: destination | Low prio. |
| | | | | |
| | | send | 2: clchanerr | signal to own |
| | | | 3: ORD (cxsyserr) | control netw. |
| | | | | |
| | | | | |
| 014020A1 | CLAA01 | explicit | 1: clmtype | Failed to send|
| | | | | |
| | | send | 2: clchanerr | signal to |
| | | | 3: ORD (cxsyserr) | other network.|
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 21
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | | |
| | | | | |
| 01404001 | CLAA01 | explicit | 1: clmtype | Failed to |
| | | send | 2: clchanerr | retransmit |
| | | | 3: ORD (cxsyserr) | previous sig. |
| | | | | |
| | | | | |
| | | | | |
| | | | 2: clchanerr | subsig to own |
| | | | 4: destination | From port 0. |
| | | | | |
| | | | 2: clchanerr | ttd_request to|
| | | | 3: ORD (cxsyserr) | own node |
| | | | 4: destination | CLAC5. |
| | | | | From port 0. |
| | | | | |
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 22
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | | From port 1. |
| | | | | |
| | | | | |
| | | | | From port 2. |
| | | | | |
| | | | | |
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 23
ABB Automation
4.2
CLAA02
4.2.1
Introduction
The event subscription handler, CLAA02, of MG 230/1 can report a

number of erroneous situations through system messages. A system
message from CLAA02 indicates a specific error condition in the
system itself or in the subscription request from the external
computer. The mtype and mcodes used are listed below.
clmtype = 34
clstructerr= 3 mcode for structure errors in system

Structure errors occur when the request signal’s resp_ch_id can

not be found in the internal xref table. This is an error that can
be caused by the external computer using wrong network and node
number. Illegal values on DSP_start and DSP_end in a DSP
configuration request is also reported as a structure error.
Signal send errors are mostly queue full messages. These errors
are only reported once if repeated.

error. Data 1 often contains the type of error, see appendix
whereas Data 2 shows various information depending on trace
number.
If the task aborts during initiation it means that no pointer to

parameter area was found. The actual abort reason is found as
data1 in the abort message from the kernel. See below.
NoParamp = 2 Illegal pointer to parameter
3BSE002142R1 24
ABB Automation
4.2.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 02200001 | CLAA02 | RecInitNode| 1: clmtype | Illegal |
| | | | 2: clstructerr | resp_ch_id in |
| | | | 3: resp_ch_id | event subscr |
| | | | 4: - | request. |
| | | | | |
| 02200011 | CLAA02 | RecDSPconf | 1: clmtype | Illegal |
| | | | 2: clstructerr | resp_ch_id in |
| | | | 3: resp_ch_id | DSP configur. |
| | | | 4: - | request. |
| | | | | |
| 02200012 | CLAA02 | RecDSPconf | 1: clmtype | Illegal values|
| | | | 2: clstructerr | on DSP_start |
| | | | 3: DSP_start | and DSP_end in|
| | | | 4: DSP_end | conf request. |
| | | | | |
| 02300001 | CLAA02 | SendSignal | 1: clmtype | Failed to send|
| | | | 2: clchanerr | response sign.|
| | | | 3: ORD(cxsyserr) | to external |
| | | | 4: destination | computer. |
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 25
ABB Automation
4.3
CLAA03
4.3.1
Introduction
The MG system status init task, CLAA03, can report a number of

different erroneous situations through system messages.
A system message from CLAA03 normally indicate a failed signal

sending or that some error occurred at initiation. The mtype
and mcode used are listed below.
clmtype = 34

clothererr = 11 mcode for other undefined errors
cliniterr = 12 mcode for initiation errors
clparerr = 15 mcode for send parameter errors
clcomerr = 16 mcode for send communication errors
clprierr = 17 mcode for send priority errors
clillid = 20 mcode for illegal signal received
Data 1 and Data 2 contains useful information about the error.
If the task aborts itself during initiation it means that

it can not continue due to lack of some data or resources.
If so, one of the following abort reasons is found as Data 1
in the abort message from the kernel.

DataBaseError = 10 Failed to access crucial database
TableError = 11 Failed to read or write to table
3BSE002142R1 26
ABB Automation
4.3.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| (HEX) | subpgm | function | ( 1 = mtype, 2 = code, | |
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 03000001 | CLAA03 | Main | 1: clmtype | Error when |
| | | | 2: cldberr | accessing the |
| | | | 3: acb.ccode | MG_FILTER_PLT |
| | | | 4: - | concept |
| | | | | |
| 03000002 | CLAA03 | Main | 1: clmtype | Error when |
| | | | 2: cldberr | accessing the |
| | | | 3: acb.ccode | MG_FILTER_PLT |
| | | | 4: - | concept |
| | | | | |
| 03000003 | CLAA03 | Main | 1: clmtype | Error accessing |
| | | | 2: cldberr | the record for |
| | | | 3: acb.ccode | DCCC20 in |
| | | | 4: - | MG_FILTER_PLT |
| | | | | |
| 03000004 | CLAA03 | Main | 1: clmtype | Node could not |
| | | | 2: cliniterr | be initiated |
| | | | 3: network | |
| | | | 4: node | |
| | | | | |
| 03000005 | CLAA03 | Main | 1: clmtype | Unexpected node |
| | | | 2: clothererr | response signal |
| | | | 3: network | received |
| | | | 4: node | |
| | | | | |
| 03000006 | CLAA03 | Main | 1: clmtype | Illegal signal |
| | | | 2: clillid | id received on |
| | | | 3: signal id | port 0 |
| | | | 4: - | |
| | | | | |
| 03000101 | CLAA03 | dcwbinit | 1: clmtype | Failed to send |
| | | | 2: cliniterr | init signal to |
| | | | 3: network | this node |
| | | | 4: node | |
| | | | | |
| 03000102 | CLAA03 | dcwbinit | 1: clmtype | Channel full |
| | | | 2: clchanerr | |
| | | | 3: signal id | |
| | | | 4: dest. channel id | |
| | | | | |
| 03000103 | CLAA03 | dcwbinit | 1: clmtype | Network,node |
| | | | 2: clcomerr | not found |
| | | | 3: network | |
| | | | 4: node | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 27
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 03000104 | CLAA03 | dcwbinit | 1: clmtype | Illegal signal |
| | | | 2: clprierr | priority |
| | | | 3: signal id | |
| | | | 4: ORD(priority) | |
| 03000105 | CLAA03 | dcwbinit | 1: clmtype | Error in signal |
| | | | 2: clparerr | or channel |
| | | | 3: signal id | |
| | | | 4: ORD(cxsyserr) | |
| | | | | |
| 03000106 | CLAA03 | dcwbinit | 1: clmtype | Other parameter |
| | | | 2: clparerr | error when |
| | | | 3: signal id | sending signal |
| | | | 4: ORD(cxsyserr) | |
| | | | | |
| 03000107 | CLAA03 | dcwbinit | 1: clmtype | Unexpected |
| | | | 2: clothererr | response signal |
| | | | 3: network | received |
| | | | 4: node | |
| | | | | |
| 03000108 | CLAA03 | dcwbinit | 1: clmtype | Illegal signal |
| | | | 2: clillid | id received on |
| | | | 3: signal id | port 0 |
| | | | 4: - | |
| 03000201 | CLAA03 | dcwbiner | 1: clmtype | None of the |
| | | | 2: clothererr | nodes has been |
| | | | 3: no of nodes | treated |
| | | | 4: - | |
| | | | | |
| 03000202 | CLAA03 | dcwbiner | 1: clmtype | The node could |
| | | | 2: cliniterr | not be initiated|
| | | | 3: network | |
| | | | 4: node | |
| | | | | |
| 03000301 | CLAA03 | nodetab_ | 1: clmtype | The node could |
| | | update | 2: clothererr | not be placed |
| | | | 3: entry number | in the nodetab |
| | | | 4: network,node | as it was full |
| | | | | |
| 03000401 | CLAA03 | dcwbnode | 1: clmtype | The node could |
| | | | 2: cliniterr | not be initiated|
| | | | 3: network | |
| | | | 4: node | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 28
ABB Automation
4.4
CLAA05
4.4.1
Introduction
The subscription supervisor, CLAA05, can report a number of

erroneous situations through system messages.
A system message from CLAA05 always indicates a serious error

condition which normally requires some further actions to be
taken. The mtype and mcode used are listed below.
clmtype = 34

clstructerr = 3 mcode for structure errors in system
clchanerr = 5 mcode for errors at signal send
Data base errors can occur during startup when accessing the
MG_SUBS_PAR file. This is a serious error but the task will
however continue to work using the default values CTR_MAX_MMI = 2
and PLT_MAX_MMI = 4. Structure errors can occur if there is not
enough RWM memory space available for task internal data
structure. Check that sufficient RWM modules are installed in the
system. Other structure errors should be reported to ABB. Signal
send errors are mostly queue full messages. If repeated they are
only reported once.

Please see the following trace number list and the appendix.
If aborted during initiation one of the following abort reasons

apply. They are found as Data 1 in the abort message from the
kernel.

NoNetwNode = 3 Illegal network or node number in system
3BSE002142R1 29
ABB Automation
4.4.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00605001 | CLAA05 | send_ | 1: clmtype | Failed to send|
| | | explicit | 2: clchanerr | OMF_NSTATU |
| | | | 3: ORD (cxsyserr) | signal to |
| | | | 4: destination | other MG 230/1|
| | | | | |
| | | | 3: ORD (cxsyserr) | signal to OMF |
| | | | 4: destination | node in own |
| | | | | control netw. |
| | | | | |
| | | | 3: ORD (cxsyserr) | signal to OMF |
| | | | 4: destination | node on plant |
| | | | | network |
| | | | | |
| 05000001 | CLAA05 | db_info | 1: clmtype | Illegal values|
| | | | 2: cldberr | for ctr_max & |
| | | | 3: ctr_max_mmi | plt_max in |
| | | | 4: plt_max_mmi | database |
| | | | | |
| 05000002 | CLAA05 | db_info | 1: clmtype | Data base |
| | | | 2: cldberr | instance not |
| | | | 3: 0 | implemented |
| | | | 4: 0 | |
| | | | | |
| 05000003 | CLAA05 | db_info | 1: clmtype | Failed to find|
| | | | 2: cldberr | instance in |
| | | | 3: acb.ccode | MG_SUBS_PAR |
| | | | 4: 0 | |
| | | | | |
| 05000004 | CLAA05 | db_info | 1: clmtype | Failed to get |
| | | | 4: 0 | MG_SUBS_PAR |
| | | | | |
| | | | 4: 0 | MG_SUBS_PAR |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 30
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 4: 0 | MG_SUBS_PAR |
| | | | | |
| 05000011 | CLAA05 | init | 1: clmtype | Not enough |
| | | | 2: clstructerr | memory for int|
| | | | 3: ByteSize | data struct. |
| | | | 4: ctr_max + plt_max | ctr, plt_max 0|
| | | | | |
| 05101001 | CLAA05 | send_signal| 1: clmtype | Failed to send|
| | | | 2: clchanerr | sub_req signal|
| | | | 3: ORD (cxsyserr) | |
| | | | | |
| | | | 3: ORD (cxsyserr) | |
| | | | | |
| | | mmi_text | 2: clchanerr | mmi_text to |
| | | | 3: ORD (cxsyserr) | subscribing |
| | | | 4: destination | node |
| | | | | |
| | | | 3: ORD (cxsyserr) | |
| | | | | |
| | | | | |
| | | | 3: ORD (cxsyserr) | |
| | | | | |
| | | | 2: clchanerr | mmi_clear |
| | | | 3: ORD (cxsyserr) | signal |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 31
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 2: clchanerr | sub_clear |
| | | | | |
| | | | 2: clchanerr | sub_clear |
| | | | | |
| | | | 2: clchanerr | mmi_clear |
| | | | | |
| | | | 2: clchanerr | ttd_request |
| | | | 3: ORD (cxsyserr) | cyclic request|
| | | | | |
| | | | 3: ORD (cxsyserr) | demand request|
| | | | | |
| | | | | |
| | | | 3: ORD (cxsyserr) | clear request |
| | | | | |
| | | | 3: ORD (cxsyserr) | clear request |
| | | | | |
| | | | | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 32
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | | |
| 05501011 | CLAA05 | other_node | 1: clmtype | Failed to send|
| | | down | 2: clchanerr | mmi_clear |
| | | | 3: ORD (cxsyserr) | signal when |
| | | | 4: destination | node disconn |
| | | | | |
| | | down | 2: clchanerr | ttd_clear |
| | | | | |
| | | plt_nstatu | 2: clchanerr | plt_nstatu |
| | | | 3: ORD (cxsyserr) |signal to other|
| | | | 4: destination | MG 230/1 |
| | | | | |
| | | | 4: destination | MG 230/1 |
| | | | | |
| | | down | 2: clchanerr | mmi_clear |
| | | | | |
| | | down | 2: clchanerr | ttd_clear |
| | | | | |
| | | | 4: destination | MG 230/1 |
| | | | | |
| 05700001 | CLAA05 | main | 1: clmtype | Illegal signal|
| | | | 2: clstructerr | received |
| | | | 3: sig_id | |
| | | | 4: - | |
| | | | | |
| 05A00041 | CLAA05 | Aloc_mmi | 1: clmtype | Failed to aloc|
| | | | 2: clstructerr | mmi_entry in |
| | | | 3: MP_index in table | internal struc|
| | | | 4: 0 | for MP_index |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 33
ABB Automation
4.5
CLAA06
4.5.1
Introduction
The symbol translation distributor CLAA06, of MG 230/1 can report

a number of erroneous situations through system messages at the
init phase of the task. A system message from CLAA06 indicates
error conditions in the content of the database. The mtype and
Mtype:
clmtype = 34
Mcode:

clchanerr = 5 mcode for error on signal send
In the event of a database error the task will continue but will
not distribute any symbol translation requests from or to any node
in the local control network. In this case the database and in
particular the instance for channel ’CXNMC2’ should be checked.
Signal send errors are mostly queue full messages. These errors
are only reported once if repeated.
If the task aborts during initiation it means that one of two

possible errors has occurred. The actual abort reason is found as
data1 in the abort message from the kernel. See below.

Data 1 and Data 2 contain useful information about the error.

Data 1 often contains the type of error, see appendix, whereas
Data 2 shows various information depending on trace number.
3BSE002142R1 34
ABB Automation
4.5.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 4: logical file no | MG_FILTER_PAR |
| | | | | |
| | | | 2: cldberr | instance for |
| | | | 3: acb.ccode | CXNMC2 in log.|
| | | | 4: logical file no | file. |
| | | | | |
| | | | 2: cldberr | concept info |
| | | | 4: - | MG_FILTER_PAR |
| | | | | |
| 06200001 | CLAA06 | rem_MG_ctrl| 1: clmtype | Failed to send|
| | | _send | 2: clchanerr | signal to node|
| | | | 3: ORD(cxsyserr) | in remote |
| | | | 4: destination | controlnetwork|
| | | | | |
| 06201001 | CLAA06 | rem_MG_plt | 1: clmtype | Failed to send|
| | | | 3: ORD(cxsyserr) | in remote |
| | | | 4: destination | plantnetwork |
| | | | | |
| 06203001 | CLAA06 | local_ctrl | 1: clmtype | Failed to send|
| | | | 3: ORD(cxsyserr) | in local |
| | | | 4: destination | controlnetwork|
| | | | | |
| 06204001 | CLAA06 | local_plt | 1: clmtype | Failed to send|
| | | _send | 2: clchanerr | to ptp node in|
| | | | 3: ORD(cxsyserr) | local pltnetw |
| | | | 4: destination | src=local_ctrl|
| | | | | |
| 06205001 | CLAA06 | local_plt | 1: clmtype | Failed to send|
| | | | 3: ORD(cxsyserr) | in local pltnw|
| | | | 4: destination | src=local_ctrl|
| | | | | |
| | | explicit | 2: clchanerr | symbolic name |
| | | | 3: ORD (cxsyserr) | trans. req. to|
| | | | 4: destination | OMF node on |
| | | | | netw.126/127 |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 35
ABB Automation
4.6
CLAA07
4.6.1
Introduction
The database init task, CLAA07, of MG 230/1 can report a number

of erroneous situations through system messages. A system message
from CLAA07 indicates different kind of error condition, either in
the system itself or in the content of the database. The mtype and
clmtype = 34

clstructerr= 3 mcode for structure errors in system or contents
of database.
A database error during initiation means that the filter database

of MG 230/1 can’t be accessed. Structure error can occur if the
network and node numbers of all connected networks are
nonconsistent with the rules for network and node numbering.
Please change any erroneous value and restart the system.
If aborted during initiation, an illegal parameter pointer has

been found. The actual abort reason is found as Data 1 in the
abort message from the kernel.
(* Abort error parameter *)
3BSE002142R1 36
ABB Automation
4.6.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 07000001 | CLAA07 | main | 1: clmtype | Failed to |
| | | | 2: clstructerr | determine own |
| | | | 3: - | control netw |
| | | | 4: - | number |
| | | | | |
| | | | 2: cldberr | coninfo for |
| | | | 3: acb.ccode | concept |
| | | | 4: - | MG_FILTER_CTR |
| | | | | |
| | | | 4: - | MG_FILTER_PLT |
| | | | | |
| | | | 4: - | MG_FILTER_CNC |
| | | | | |
| 07300001 | CLAA07 | modify | 1: clmtype | Failed to find|
| | | netnod | 2: clstructerr | reusable or |
| | | | 3: - | free entry in |
| | | | 4: - | NETNOD struct.|
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 37
ABB Automation
4.7
CLBA01
4.7.1
Introduction
The function multiplexer, CLBA01, can report a number of

A system message from CLBA01 normally indicates a failed signal

sending. The main reason for this is a full queue which can occur
under heavy load conditions. If signal sending fail is repeated it
is only reported once. The mtype and mcode used are listed
below.
clmtype = 34
Data 1 and Data 2 contains information about the source and

destination for the signal the program was trying to send.

kernel.

NoNetwNode = 3 Illegal network or node number in system
4.7.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 11100011 | CLBA01 | error_ | 1: clmtype | Failed to send|
| | | telegram | 2: clchanerr | error telegram|
| | | | 3: ORD (cxsyserr) | to external |
| | | | 4: destination | ptp computer. |
| | | | | |
| 11200001 | CLBA01 | send_signal| 1: clmtype | Failed to |
| | | | 2: clchanerr | forward signal|
| | | | 3: ORD (cxsyserr) | received from |
| | | | 4: destination | ptp computer. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 38
ABB Automation
4.8
CLBA02
4.8.1
Introduction
The clock service task, CLBA02, can report a number of


sending or an illegal signal received. The main reason for a
signal sending to fail is a full queue, which can result
under heavy load conditions. The mtype and mcode used are listed
below.
clmtype = 34

If the task aborts itself during initiation it means that it

received an illegal pointer to its parameter area, and the
following abort reason is found as Data 1 in the abort message
from the kernel.
(* Abort error parameter *)
3BSE002142R1 39
ABB Automation
4.8.2
System messages
MASTERGATE CLOCK (CLBA02)
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 12000020 | CLBA02 | replyquick | 1: clmtype | Channel is full |
| | | | 2: clchanerr | |
| | | | 3: signalid | |
| | | | 4: dest_netw,dest_node,| |
| | | | dest_ch_id | |
| | | | | |
| 12000021 | CLBA02 | replyquick | 1: clmtype | Other error than|
| | | | 2: clparerr | full channel |
| | | | 3: sig_id,ORD(cxsyserr)| when trying to |
| | | | 4: dest_netw,dest_node,| send a signal. |
| | | | dest_ch_id | |
| | | | | |
| 12000030 | CLBA02 | send_signal| 1: clmtype | Channel is full |
| | | | 2: clchanerr | |
| | | | 3: 0 | |
| | | | 4: outport number | |
| | | | | |
| 12000031 | CLBA02 | send_signal| 1: clmtype | Other error than|
| | | | 3: ORD(cxsyserr) | when trying to |
| | | | 4: outport number | send a signal. |
| | | | | |
| 12000100 | CLBA02 | main | 1: clmtype | No task para- |
| | | | 2: cliniterr | meters |
| | | | 3: 0 | |
| | | | 4: 0 | |
| | | | | |
| 12000102 | CLBA02 | main | 1: clmtype | Illegal signal |
| | | | 2: clillid | identity in the |
| | | | 3: signal identity | signal received |
| | | | 4: src_netw, src_node, | on inport 1 |
| | | | resp_ch_id | |
| | | | | |
| 12000104 | CLBA02 | main | 1: clmtype | Illegal signal |
| | | | resp_ch_id | |
| | | | | |
| 12000106 | CLBA02 | main | 1: clmtype | Illegal inport |
| | | | 2: clothererr | number received |
| | | | 3: inport number | |
| | | | 4: 0 | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 40
ABB Automation
4.9
CLBA03
4.9.1
Introduction
The application multiplexer, CLBA03, can report a number of


signal sending to fail is a full queue, which can result under
heavy load conditions. The mtype and mcode used are listed
below.
clmtype = 34
clstructerr = 3 mcode for data structure errors

If the task aborts itself during initiation it means that it

can not handle the data in the parameter area, and one of
the following abort reasons is found as Data 1 in the abort
message from the kernel.

ParamError = 12 Illegal data in parameter area
3BSE002142R1 41
ABB Automation
4.9.2
System messages
APPLICATION MULTIPLEXER (CLBA03)
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 13000010 | CLBA03 | send_signal| 1: clmtype | Channel is full |
| | | | 2: clchanerr | |
| | | | 3: 0 | |
| | | | 4: outport number | |
| | | | | |
| 13000011 | CLBA03 | send_signal| 1: clmtype | Other error than|
| | | | 3: ORD(cxsyserr) | when trying to |
| | | | 4: outport number | send a signal. |
| | | | | |
| 13000030 | CLBA03 | init | 1: clmtype | No task para- |
| | | | 3: 0 | |
| | | | 4: 0 | |
| | | | | |
| 13000031 | CLBA03 | init | 1: clmtype | Taskmode = |
| | | | 2: cliniterr | IL timesync and |
| | | | 3: 0 | IL timesync task|
| | | | 4: 0 | not found |
| | | | | |
| 13000032 | CLBA03 | init | 1: clmtype | Error in IADBP3 |
| | | | 2: cliniterr | table |
| | | | 3: 0 | |
| | | | 4: 0 | |
| | | | | |
| 13000040 | CLBA03 | get_resp_ | 1: clmtype | Response channel|
| | | chid | 2: clstructerr | id for channel |
| | | | 3: src_netw, src_node, | DCPC1x not found|
| | | | resp_ch_id | Where x is dep. |
| | | | 4: place in ext. desc | on place in ext.|
| | | | table | descr table or |
| | | | | portno in ext. |
| | | | | descr table dont|
| | | | | match |
| | | | | |
| 13000050 | CLBA03 | mux_signal | 1: clmtype | Illegal signal |
| | | | resp_ch_id | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 42
ABB Automation
4.10
CLBA04
4.10.1
Introduction
The communication status task, CLBA04, can report a number of


signal sending to fail is a full queue, which can result under
heavy load conditions. The mtype and mcode used are listed
below.
clmtype = 34

If the task aborts itself during initiation or execution it

means that it can not continue safely as some data is erroneous.
If so, one of the following abort reasons is found as Data 1
in the abort message from the kernel.

DataBaseError = 10 Failed to access crucial database
TableError = 11 Failed to read or write to table
ParamError = 12 Illegal data in parameter area
ChannelError = 13 Error in channel or port detected
3BSE002142R1 43
ABB Automation
4.10.2
System messages
COMMUNICATION STATUS FUNCTION (CLBA04)
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 14000000 | CLBA04 | iaexh | 1: 10 | Abort or killed,|
| | | | 2: 19 | sysmess from |
| | | | 3: netw, netwtype, | exception |
| | | | code, ORD(cxsyserr) | handler, status |
| | | | 4: 0 | is controlled |
| | | | | for netw |
| | | | | |
| 14000020 | CLBA04 | send_ereply| 1: clmtype | Channel is full |
| | | | 2: clchanerr | |
| | | | 3: signalid | |
| | | | dest_ch_id | |
| | | | | |
| 14000021 | CLBA04 | send_ereply| 1: clmtype | Other error than|
| | | | dest_ch_id | |
| | | | | |
| 14000030 | CLBA04 |send_signal_| 1: clmtype | Channel is full |
| | |to_node | 2: clchanerr | |
| | | | 3: signalid | |
| | | | dest_ch_id | |
| | | | | |
| 14000031 | CLBA04 |send_signal_| 1: clmtype | Other error than|
| | |to_node | 2: clparerr | full channel |
| | | | dest_ch_id | |
| | | | | |
| 14000040 | CLBA04 | get_DI_ | 1: clmtype | Error accessing |
| | | fileinfo | 2: cldberr | the DI concept |
| | | | 3: H’00010000 | |
| | | | 4: 0 | |
| | | | | |
| 14000050 | CLBA04 | get_netw_ | 1: clmtype | Netw not found |
| | | type | 2: clothererr | |
| | | | 3: netw, node, 0, 0 | |
| | | | 4: 0 | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 44
ABB Automation
COMMUNICATION STATUS FUNCTION (CLBA04) Cont.
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 14000060 | CLBA04 | get_DI_ | 1: clmtype | Error when DI:s |
| | | implemented| 2: cldberr | IMPLEMENTED flag|
| | | | 3: dbind | is accessed |
| | | | 4: propno | |
| | | | | |
| 14000070 | CLBA04 | put_value_ | 1: clmtype | Error when DI:s |
| | | into_file | 2: cldberr | CALC_VALUE or |
| | | | 3: dbind | SEC_VALUE is |
| | | | 4: propno | updated |
| | | | | |
| 14000080 | CLBA04 | init | 1: clmtype | Illegal network |
| | | | 2: clothererr | type |
| | | | 3: netw type | |
| | | | 4: 0 | |
| | | | | |
| 14000081 | CLBA04 | init | 1: clmtype | Number of nodes |
| | | | 2: clothererr | specified in |
| | | | 3: noof_nodes in task | task parameter |
| | | | parameter area | area greater |
| | | | 4: allowed no of nodes | than allowed for|
| | | | for actual netw type| actual netwtype |
| | | | | |
| 14000100 | CLBA04 | main | 1: clmtype | No task para- |
| | | | 3: 0 | |
| | | | 4: 0 | |
| | | | | |
| 14000102 | CLBA04 | main | 1: clmtype | Number of nodes |
| | | | 2: cliniterr | specified in |
| | | | 3: noof nodes | task parameter |
| | | | 4: 0 | area negative |
| | | | | |
| 14000104 | CLBA04 | main | 1: clmtype | Cycle limit |
| | | | 2: cliniterr | specified in |
| | | | 3: cycle limit | task parameter |
| | | | 4: 0 | area <= 0 |
| | | | | |
| 14000106 | CLBA04 | main | 1: clmtype | Channel id for |
| | | | 2: clothererr | inport 1 not |
| | | | 3: channel id | found |
| | | | 4: chan status | |
| | | | | |
| 14000108 | CLBA04 | main | 1: clmtype | Channel id for |
| | | | 2: clothererr | channel IBCX41 |
| | | | 3: channel id | not found |
| | | | 4: chan status | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 45
ABB Automation
COMMUNICATION STATUS FUNCTION (CLBA04) Cont.
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――――k
| | | | 3 = data1, 4 = data2 | |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――――u
| 1400010A | CLBA04 | main | 1: clmtype | Illegal task |
| | | | 2: cliniterr | mode specified |
| | | | 3: task mode | in task para- |
| | | | 4: 0 | meter area |
| | | | | |
| 1400010C | CLBA04 | main | 1: clmtype | Illegal signal |
| | | | resp_ch_id | |
| | | | | |
| 1400010E | CLBA04 | main | 1: clmtype | Illegal signal |
| | | | resp_ch_id | |
| | | | | |
| 14000110 | CLBA04 | main | 1: clmtype | Illegal inport |
| | | | 2: clothererr | number received |
| | | | 3: inport number | |
| | | | 4: 0 | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――――j
3BSE002142R1 46
ABB Automation
4.11
CLCA70
4.11.1
Introduction
The GCOM handler for point-to-point connected external computers,

CLCA70, can report a number of erroneous situations through system
messages.
A system message from CLCA70 normally indicates a failed signal

sending. The main reason for this is a full queue which can result
under heavy load conditions. If signal sending fail is repeated it
is only reported once. The mtype and mcode used are listed
below.
clmtype = 34
clstructerr = 3 mcode for inport error



kernel.
NoSyncTask = 3174400 System task missing or dormant

NoAttach = 3174416 Failed to attach to data link
NoInfo = 3174448 Failed to get info about connection
4.11.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 2F007000 | CLCA70 | ort70init | 1: clmtype | Illegal status|
| | | | 2: clstructerr | on channel |
| | | | 3: idle_ch_id | connected to |
| | | | 4: ORD (chan_status) | inport 0. |
| | | | | |
| 2F007100 | CLCA70 | ort71ddti | 1: clmtype | Failed to send|
| | | | 2: clchanerr | signal recvd |
| | | | 3: dest_ch_id | from external |
| | | | 4: sig_id | ptp computer. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 47
ABB Automation
4.12
CLEA00
4.12.1
Introduction
The GCOM handler for multidrop bus, CLEA00, can report

a number of erroneous situations through system messages.
A system message from CLEA00 always indicates a serious
error condition which normally requires some further
actions to be taken. The mtype and mcodes used are
listed below.
clmtype = 34
cldatalerr = 2 mcode for datalink errors

clXLerr = 4 mcode for gen. interface errors
clDLerr = 6 mcode for own errors
clrouterr = 8 mcode for send rout.vector errors
clbuferr = 10 mcode for buffer errors
In the event of a buffer error the communication board

should be restarted. The same applies to errors with
mcode = clDLerr or clXLerr. Message with mcode =
clrouterr may be caused by some error in the main
processor. Some system messages precedes abort and gives
more detailed information about what caused the abort.
This is the case for all messages with mcode =
cldatalerr. The actual abort reason is found as data1
in the abort message from the kernel. See below.
NoAllocate = 0 Failed to allocate buffer

NoWrite = 1 Failed to write buffer
NmroutNotFound = 4 Illegal channel index for NMROUT
NoAttach = 5 Failed to attach to DLSAP or DSX_XL
NoConnect = 6 Failed to connect to DLSAP clea00
NoInfo = 7 No info from Data Link layer
ToManyNodes = 8 To many entries in DL table
GlobDisconn = 9 Global disconnect DL handler aborted
3BSE002142R1 48
ABB Automation

error. Data 1 often contains the remote nodes
nodenumber, if relevant, whereas Data 2 shows the type
of error, see appendix.
Description of variables in system messages :
sn = slave number
syserr = cxsyserr
bufst = bufstatus
dlst = dlstatus
sapgr = DLSAP group number
3BSE002142R1 49
ABB Automation
4.12.2
System messages
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00000001 | CLEA00 | init | 1: clmtype | Failed to |
| | | | 2: clbuferr | allocate ACK |
| | | | 3: 0 | buffer. Pre- |
| | | | 4: sn:00 00:bufst | ceding abort |
| | | | | |
| | | | 2: clbuferr | write ACK |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| | | | 2: clbuferr | allocate INIT |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| | | | 2: clbuferr | write INIT_S |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| | | | 2: clbuferr | allocate INIT |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| | | | 2: clbuferr | write INIT_R |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| 00000301 | CLEA00 | init | 1: clmtype | Failed to atch|
| | | | 2: cldatalerr | to DLSAP1. |
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:dlst | abort. |
| | | | | |
| 00000302 | CLEA00 | init | 1: clmtype | Failed to atch|
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:dlst | abort. |
| | | | | |
| 00000303 | CLEA00 | init | 1: clmtype | Not allowed |
| | | | 2: cldatalerr | hexswitch No |
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:sapgr | abort. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 50
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00000401 | CLEA00 | init | 1: clmtype | Failed to conn|
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:dlst | abort. |
| | | | | |
| 00000402 | CLEA00 | init | 1: clmtype | Failed to conn|
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:dlst | abort. |
| | | | | |
| 00000501 | CLEA00 | init | 1: clmtype | Failed to get |
| | | | 2: cldatalerr | connect. info |
| | | | 3: 0 | Preceding |
| | | | 4: sn:00 00:dlst | abort |
| | | | | |
| | | | 2: clbuferr | allocate TRV |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| | | | 2: clbuferr | write TRV |
| | | | 3: 0 | buffer. Pre- |
| | | | | |
| 00000701 | CLEA00 | init | 1: clmtype | Failed to re- |
| | | | 3: 0 | buffer to send|
| | | | 4: sn:00 00:bufst | on DLSAP1. |
| | | | | |
| 00000801 | CLEA00 | init | 1: clmtype | Failed to send|
| | | | 2: clrouterr | first routing―u
| | | | 3: node (-1) | vector to host|
| | | | 4: sn:00 00:syserr | processor. |
| | | | | |
| 00101001 | CLEA00 | main | 1: clmtype | Failed to de- |
| | | | 2: clbuferr | allocate buff |
| | | | 3: 0 | received at |
| | | | 4: sn:00 00:bufst | DLSAP1. |
| | | | | |
| 00101002 | CLEA00 | main | 1: clmtype | Failed to read|
| | | | 2: clbuferr | buffer receiv.|
| | | | 3: 0 | at DLSAP1. |
| | | | 4: sn:00 00:bufst | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 51
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00101101 | CLEA00 | main | 1: clmtype | Failed to send|
| | | | 2: clrouterr | routingvetcor |
| | | | 3: node | to host pro- |
| | | | 4: sn:00 00:syserr | cessor. |
| | | | | |
| 00101201 | CLEA00 | AlocNewNode| 1: clmtype | Failed to send|
| | | | 4: sn:00 00:syserr | cessor. |
| | | | | |
| 00101202 | CLEA00 | AlocNewNode| 1: clmtype | All DLentries |
| | | | 2: clDLerr | are occupied |
| | | | 3: node | |
| | | | 4: sn:00 0000 | |
| | | | | |
| 00101203 | CLEA00 | AlocNewNode| 1: clmtype | Failed to send|
| | | | 4: sn:00 00:syserr | cessor. |
| | | | | |
| | | | 2: clbuferr | allocate data |
| | | | 3: node | buffer receiv.|
| | | | 4: sn:00 00:bufst | at DLSAP2. |
| | | | | |
| | | | 2: clbuferr | data buffer |
| | | | 3: node | rec. at DLSAP2|
| | | | 4: sn:00 00:bufst | Signal lost. |
| | | | | |
| | | | 2: clbuferr | header buffer |
| | | | 3: node | rec. at DLSAP2|
| | | | | |
| | | | 3: 0 | buffer receiv.|
| | | | 4: sn:00 00:bufst | at DLSAP2. |
| | | | | |
| 00102101 | CLEA00 | send | 1: clmtype | Failed to |
| | | | 2: clbuferr | write ACK buf |
| | | | 3: node | to send on |
| | | | 4: sn:00 00:bufst | DLSAP2. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 52
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00102102 | CLEA00 | send | 1: clmtype | Failed to re- |
| | | | 3: node | buffer to send|
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 2: clbuferr | write ACK buf |
| | | | 3: node | to send on |
| | | | 4: sn:00 00:bufst | DLSAP2. |
| | | | | |
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 2: clbuferr | write INIT_S |
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 2: clbuferr | allocate INITS|
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 3: node | buffer receiv.|
| | | | 4: sn:00 00:bufst | at DLSAP2. |
| | | | | |
| | | | 3: 0 | buffer already|
| | | | 4: sn:00 00:bufst | sent. |
| | | | | |
| 00103101 | CLEA00 | sendDATA | 1: clmtype | Failed to de- |
| | | | 2: clbuferr | allocate |
| | | | 3: 0 | faulty buffer |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| 00103102 | CLEA00 | sendDATA | 1: clmtype | Failed to re- |
| | | | 3: node | buf. to send. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 53
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 3: node | faulty buffer |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| 00103104 | CLEA00 | sendDATA | 1: clmtype | Failed to |
| | | | 2: clbuferr | write data |
| | | | 3: node | buf. to send. |
| | | | | |
| | | | 2: clbuferr | write INIT_R |
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 2: clbuferr | allocate INITR|
| | | | 4: sn:00 00:bufst | on DLSAP2. |
| | | | | |
| | | | 3: 0 | INIT_R buffer |
| | | | 4: sn:00 00:bufst | received. |
| | | | | |
| | | | 3: node | INIT_S buffer |
| | | | | |
| 00105002 | CLEA00 | resetbufseq| 1: clmtype | Failed to re- |
| | | | 2: clbuferr | set seqno in |
| | | | 3: node | send buffer |
| | | | 4: sn:00 00:bufst | after INIT_S. |
| | | | | |
| 00106001 | CLEA00 | disconnect | 1: clmtype | Failed to de- |
| | | | 2: clbuferr | allocate disc.|
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 2: clXLerr | allocate XL |
| | | | 3: node | entries. |
| | | | 4: sn:00 00:bufst | |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 54
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| 00106003 | CLEA00 | disconnect | 1: clmtype | Failed to send|
| | | | 3: node (-1) | to host pro- |
| | | | 4: sn:00 00:syserr | cessor. |
| | | | | |
| 00106004 | CLEA00 | disconnect | 1: clmtype | Failed to re- |
| | | | 2: cldatalerr | connect to |
| | | | 3: ORD (error) | data link. Pre|
| | | | 4: sn:00 00:dlst | ceding abort. |
| | | | | |
| | | | 2: clbuferr | allocate disc.|
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 3: 0 | buff. receiv. |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 2: clbuferr | allocate il- |
| | | | 3: 0 | legal tpdu |
| | | | | |
| | | | 2: clbuferr | allac. buffer |
| | | | 3: 0 | with unknown |
| | | | 4: sn:00 00:bufst | source node. |
| | | | | |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 2: clbuferr | buffer receiv.|
| | | | 3: 0 | at DLSAP2. |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 2: clbuferr | allocate buf. |
| | | | 3: 0 | with illegal |
| | | | 4: sn:00 00:bufst | DLSAP addr. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 55
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 2: clbuferr | allocate buff.|
| | | | 3: 0 | with NoEvent. |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 3: node | buf. to send. |
| | | | | |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 3: node | buf. to send. |
| | | | | |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 3: node | buf. to send. |
| | | | | |
| | | | 4: sn:00 00:bufst | |
| | | | | |
| | | | 3: node | buf. to send. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 56
ABB Automation
l――――――――――w――――――――――w――――――――――――w――――――――――――――――――――――――w―――――――――――――――k
| | | | 3 = data1, 4 = data2)| |
t――――――――――n――――――――――n――――――――――――n――――――――――――――――――――――――n―――――――――――――――u
| | | | 3: 0 | buffer already|
| | | | 4: sn:00 00:bufst | sent. |
| | | | | |
| | | | 3: node | buffer before |
| | | | 4: sn:00 00:bufst | dealloc. node |
| | | | | |
| | | | 2: clDLerr | allocate DL |
| | | | 3: node | entries. |
| | | | 4: sn:00 0000 | |
| | | | | |
| 00302003 | CLEA00 | main | 1: clmtype | Failed to send|
| | | | 4: sn:00 00:syserr | cessor. |
| | | | | |
| 00401001 | CLEA00 | sendTrv | 1: clmtype | Failed to re- |
| | | | 3: 0 | buffer to send|
| | | | 4: sn:00 00:bufst | on DLSAP1. |
m――――――――――v――――――――――v――――――――――――v――――――――――――――――――――――――v―――――――――――――――j
3BSE002142R1 57
ABB Automation
4.13
Appendix
Interpretation of syserr
0 = No error,warm start
1 = Cold start
2 = Power failure
3 = Error in port no
4 = Error in signal priority
5 = No sqb (queue full)
6 = No tqb (sendt)
7 = No reply within time for sendw
8 =
9 = Error when signal data (resp) was accessed
10 = Error in time parameter
11 = Response already given

12 = Inport not in expected state
13 = No inport selected
14 = Stack overflow
15 = Error in bios system service parameter
16 = No iqb with right state available

17 = Task has already a reserved device
18 = Error reported from handler
19 = Abort (system service call)
20 = Bus error ;param #1 ps #2 effective address
21 = The task has been killed

22 = Error trap ;param #1 ps #2 trap vector address/
effective address (odd) address error
23 = Illegal trap ;param #1 ps #2 trap vector addr
24 = Pascal runtime error;param #1 pascal runtime
error code ,if #2 statement no
25 = Access control block error
26 = Illegal concept
27 = Illegal logical file
28 = Illegal logical record
29 = Illegal property number
30 = Illegal member number
31 = Illegal variant
32 = Illegal physical file
33 = Illegal group
34 = Error in action routine
35 = Routine not implemented in system
3BSE002142R1 58
ABB Automation
36 = Floating point illegal operation

37 = Floating point overflow
38 = Floating point underflow
39 = Floating point zero divide
40 = Floating point inexact result
41 = Floating point to integer overflow

42 = Illegal network or node number
43 = Not used
44 = Illegal message length
45 = Illegal destination channel id
46 = System overloaded
Interpretation of acb.ccode
-128 = end of group

-127 = end of file
-126 = instance occupied
-125 = instance unoccupied
-124 = key already exists
-123 = space is insufficient
-122 = end of structure
-121 = illegal concept
-120 = logical file not dimensioned
-119 = logical file has no instance name
Interpretation of source and destination for system messages

concerning signals. Data 1 and Data 2 containing data about source
and destination are always formatted as an 8 digit hex number as
follows:
H’XX YY ZZZZ
XX stands for MasterNet network number.

YY stands for MasterNet node number.
ZZZZ stands for destination or response channel index.
Note that each part is hexadecimal, eg XX = 1F means network 31.
3BSE002142R1 59
ABB Automation
Interpretation of bufstatus and dlstatus:
0 = no errors found, function performed
1 = send acknowledge tpdu

2 = one block in the buffer is stolen
3 = the buffer is too small
4 = list of buffers to small
5 = connection attempt failed
6 = connection is already established

7 = connection attempt has started
8 = connect request timeout
9 = send disconnect xpdu
10= send error xpdu
11= not valid address

12= wrong callerlayer, no action taken
13= illegal send condition in DTF specification
record for this command
14= illegal task
15= insufficient resource, no action taken
16= internal error

17= last event in eventqueue
18= last tsdu to receive
19= send/receive length error
20= too low network quality
21= more data to read

22= lack of tpdu buffers
23= the eventqueue is empty
24= no detailed status to read in tccb
25= tccb sendqueue is full
26= DTF specification record is not active

27= calling task not attached to sap
28= no tsdu to receive
29= lack of virtucal circuit (tccb)
30= hardware not working
31= received old npdu in network layer

32= parameter error
33= in tr.handler : protocol error
34= proposed length of tpdu to receive is too short
35= received disconnect from remote node
36= proposed length of tpdu to send is too long or zero

37= illegal status of control block
38= DTF structure is still referenced
39= referenced structure unknown to DTF
40= proposed value is illegal
41= resend data tpdu
3BSE002142R1 60
ABB Automation
End of Manual 3BSE002142R1
"MasterGate 230/1 - Installation and Error Codes"
3BSE002142R1 61

MasterNet User S Guide 3BSE003839R301

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MasterNet User S Guide 3BSE003839R301

Diunggah oleh

Hak Cipta:

Format Tersedia

ABB Automation

1 GENERAL INFORMATION ................................ 3

3 INITIALIZING AND STARTUP .......................... 16

4 SYSTEM MESSAGES .................................... 17

4.5 CLAA06 .......................................... 34

This manual is a complement for the MasterGate 230/1 to the

MasterGate 230/1 Technical description 3BSE002141R1

The hardware described in the MasterPiece 200/1 Design Manual is

Single CPU unit

All communication boards should be placed directly after the

NOTE: DSCS 116 is not supported in a Dual CPU configuration.

In redundant configuration the required RWM memory is contained in

S9 o o S10 o-o S11 o o o o S12 o o S13 o o

S9 o o S10 o-o S11 o o o o S12 o o S13 o o

S1 o-o o S3 o-o o S4 o-o S5 o-o S6 o o

S2 (Applies to CPU-left) S2 (Applies to CPU-right)

The DSCS 116 board is used for synchronous communication

Board address (S1)

The DSCA 114 board is used for asynchronous communication

S1 o o S10 o-o S11 o-o S12 o o S13 o o S14 o o

Base address (S3)

Network and node number for MB 300/300E is defined with switches

S5 defines bit 0-3 of the node number

S9 defines bit 0-3 of the network number

MG 230/1 node number in own control network should always be 127

The DSCS 150 board is used for multidrop synchronous communication

Base address (S3)1)

S5 defines bit 0-3 of the node number

S9 defines bit 0-3 of the network number

Which MAC (Medium Access Control) frame size and SAP’s

The MG 230/1 will start after a cold start in

The MG 230/1 will act similar to a standard MP 200/1 except that

The user database is configured and dimensioned for :

The database can be dumped/loaded using one of the following

1) DUAP : Dump Application Program

2) DURWM : Dump RWM

3) DUDB : Dump database logical file 108 and 116

LOAP must be done after coldstart (CLEAR) using the U option,

System message printouts have the following appearance:

01 23S04*13:25:09 19 114 CXCC030 A H’FF37A1 H’00000025 3781

See the appendix for interpretations of the following variables in

The channel multiplexer, CLAA01, of MG 230/1 can report a number

(* System messages trace identities *)

cldberr = 1 mcode for database errors

In the event of a database error during initiation the task will

from point-to-point connected external computers. Signal send

If the task aborts during initiation it means that one of two

(* Abort error parameters *)

NoParamp = 2 Illegal pointer to parameter area

Data 1 and Data 2 contains useful information about the

The event subscription handler, CLAA02, of MG 230/1 can report a

(* System messages trace identities *)

clstructerr= 3 mcode for structure errors in system

Structure errors occur when the request signal’s resp_ch_id can

Data 1 and Data 2 contains useful information about the

If the task aborts during initiation it means that no pointer to

(* Abort error parameters *)

NoParamp = 2 Illegal pointer to parameter

The MG system status init task, CLAA03, can report a number of

A system message from CLAA03 normally indicate a failed signal

(* System messages trace identities *)

cldberr = 1 mcode for database errors