![ABB MTQ22-FBP.0 Скачать руководство пользователя страница 24](http://html.mh-extra.com/html/abb/mtq22-fbp-0/mtq22-fbp-0_manual_2750024.webp)
Diagnosis Data of UMC100 according to the UMC100 manual section
A1 Parameters and Data Structures on a Fieldbus
UMC at
port 1
UMC at
port 2
UMC at
port 3
UMC at
port 4
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit1
Bit 0
Address
0x0C00
dec
3072
0x0C20
dec
3104
0x0C40
dec
3136
0x0C60
dec
3168
Checkback
missing
PTC wiring
failure
PTC hot
Pre-
waring
thermal
model
Locked
rotor
during
start-up
(stall)
Phase
imbalance
1
Phase loss
1
Thermal
overload
trip
Actuator
problem
1
UMC self-
test error
Earth
fault
pre-
warning
Earth fault
trip
(internal
or
externally
triggered)
I above
high
current
warning
threshold
I above
high
current trip
threshold
I below low
current
warning
threshold
I below
low
current
trip
threshold
0x0C01
dec
3073
0xC021
dec
3105
0x0C41
dec
3137
0x0C61
dec
3167
Trip/
Warning
from
AuxFault
function
block input
5
2)
Trip/Warning
from
AuxFault
function
block input
4
2)
Trip/
Warning
from
AuxFault
function
block
input 3
2)
Trip/
Warning
from
AuxFault
function
block
input 2
2)
Trip/
Warning
from
AuxFault
function
block
input 1
2)
HW fault on
IO module
Custom
application
error
IO
module
missing
-
-
-
-
Trip
triggered
from
Multi-
function
input DI2
Trip
triggered
from Multi-
function
input DI1
Trip
triggered
from Multi-
function
input DI0
Trip /
Warning
from
AuxFault
function
block
input 6
2)
0x0C02
dec
3074
0x0C22
dec
3106
0x0C42
dec
3138
0x0C62
dec
3168
-
-
THD
Warning
Voltage
out of
spec
1
Overload
power
Underload
power
1
-
-
-
-
Cooling
Time
Running
Just one
start left
Num
Starts
Overrun
-
-
-
0x0C03
dec 3075
0x0C23
dec
3107
0x0C43
dec
3139
0x0C63
dec
3169
Extended
diagnosis
is
available
1)
.
Parameter
out of range
-
-
-
-
-
-
Fault code. See the section "Error Handling, Maintenance and Service-> Fault Messages" for a
description of the code.
1)
There is more than one root cause that triggers this diagnosis. For details see diagnosis byte seven.
2)
By default these diagnosis bits are triggered from the digital inputs of the DX111/DX122 IO module. If you have created an own custom application these diagnosis bits might
be triggered for other reasons (see manual "Custom Application Editor" for more details).
Data Access in one block ordered by device
This section explains how to access the data of the connected devices in one block. Only one Modbus TCP read request is
required to read all monitoring data, and only one request is necessary to write all command data.
Monitoring Data
This address map shows how the complete monitoring data from up to four UMCs can be read in one block. The data is
ordered without any gaps after each other in the following way.
24
U N I V ER S A L M OTO R CO N T R O L L ER U M C 10 0. 3 |
MTQ2 2- FB P.0 MODBUS TCP M A N UA L