1TGC910032M0201 MNSiS 800xa SV5 - 1 ConditionMonitoring OperationManual

MNS iS Motor Control Center
Condition Monitoring System with 800xA SV5.1

Operation Manual
MNS is a registered trademark.
Microsoft, Windows 2008 and Windows 7 are registered trademarks of
Microsoft Corporation.
Product names of other products are registered trademarks of their

manufacturers.
This document relates to the MNS iS System Release 6.0/0 and to the MNS
iS Condition Monitoring System Release 6.0/0.
The information in this document is subject to change without notice and

should not be construed as a commitment by ABB.
ABB assumes no responsibility for any errors that may appear in this
document.
In no event shall ABB be liable for direct, indirect, special, incidental, or
consequential damages of any nature or kind arising from the use of this
document, nor shall ABB be liable for incidental or consequential damages
arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without
ABB's written permission, and the contents thereof must not be imparted to a
third party nor be used for any unauthorized purpose. The software described
in this document is furnished under a license and may be used, copied, or
disclosed only in accordance with the terms of such license.
All rights reserved.
Copyright © 2011 ABB Automation Products GmbH, Ladenburg, Germany

Content
Table of content
1 General ............................................................................................................... 6
1.1 Target Group ......................................................................................................6
1.2 Use of Warning, Caution, Information and Tip icon ............................................6
1.3 Terminology ........................................................................................................7
1.4 References .........................................................................................................9
2 Installation of Asset Monitors, Faceplates and other standard functions .. 10
2.1 Backup & restore ..............................................................................................10
3 General usage of AssetMonitor Aspects ....................................................... 11
3.1 Operation ..........................................................................................................11
3.1.1 Main view ...................................................................................................11
3.1.2 Condition mark-up and access to further functionality................................12
3.1.3 Some examples from the MStart AssetMonitor ..........................................14
3.1.4 Available menus for AssetMonitor aspects.................................................17
3.2 Settings, Configuration and Parameterization of Asset Monitors ......................20
3.2.1 Settings ......................................................................................................21
3.2.2 Configuration and parameterization ...........................................................24
3.2.3 Changing Settings on Object instance vs on Object Type vs on Aspect
Category .................................................................................................................43
3.3 Activating Asset Monitors and their setting, configuration and parameters.......47
3.3.1 Activating a single Asset monitor ...............................................................48
3.3.2 Bulk changing for many Asset Monitors .....................................................50
4 MStart Asset Monitor ....................................................................................... 55
4.1 Conditions .........................................................................................................55
4.2 Layout and Definitions ......................................................................................55
4.3 Sub-Conditions and Severity ............................................................................56
4.4 Operation ..........................................................................................................57
4.5 Parameter .........................................................................................................57
4.6 Functionality......................................................................................................61
4.6.1 Condition Monitoring functions ...................................................................61
4.6.2 Protection functions....................................................................................71
4.6.3 General Purpose Functions........................................................................76
4.7 MStart Maintenance Faceplate .........................................................................79
4.7.1 Functionality ...............................................................................................79
1TGC910032M0201 3
Content
4.7.2 Graphic Display ..........................................................................................80

4.7.3 Reset of Alarms..........................................................................................82
5 MFeed Asset Monitor ...................................................................................... 84
5.1 Conditions .........................................................................................................84
5.2 Layout and Definitions ......................................................................................84
5.3 Sub-Conditions and Severity ............................................................................85
5.4 Operation ..........................................................................................................86
5.5 Parameter .........................................................................................................86
5.6 Functionality......................................................................................................90
5.6.1 Condition Monitoring functions ...................................................................90
5.6.2 Protection functions..................................................................................100
5.6.3 General Purpose Functions......................................................................105
5.7 MFeed Maintenance Faceplate ......................................................................107
5.7.1 Functionality .............................................................................................107
5.7.2 Graphic Display ........................................................................................109
5.7.3 Reset of Alarms........................................................................................111
6 MLink Asset Monitor ..................................................................................... 113
6.1 Conditions .......................................................................................................113
6.2 Layout and Definitions ....................................................................................113
6.3 Sub-Conditions and Severity ..........................................................................114
6.4 Operation ........................................................................................................114
6.5 Parameter .......................................................................................................115
6.6 Functionality....................................................................................................115
6.6.1 Condition Monitoring functions .................................................................116
7 Cubicle Asset Monitor ................................................................................... 119
7.1 Conditions .......................................................................................................119
7.2 Layout and Definitions ....................................................................................119
7.3 Sub-Conditions and Severity ..........................................................................120
7.4 Operation ........................................................................................................120
7.5 Parameter .......................................................................................................120
7.6 Functionality....................................................................................................121
7.6.1 Condition Monitoring functions .................................................................121
8 Related and used 800xA Functionality ........................................................ 123
8.1 Trend Display..................................................................................................123
8.2 History Log .....................................................................................................131
4 1TGC910032M0201
Content
8.3 Alarm- and Eventlist........................................................................................147

8.4 Different Structures .........................................................................................151
8.5 Control Connection .........................................................................................153
9 Error Correction ............................................................................................. 156
9.1 Basic error procedure .....................................................................................156
9.1.1 ABB 800xA OPC Client ............................................................................156
9.1.2 Softing OPC Client ...................................................................................165
9.2 Path not found ................................................................................................173
9.3 Error initializing logic .......................................................................................174
9.4 National Language Support does not work in Asset Monitor ..........................177
9.5 Description field of Asset Monitor starts with a ‘dot’ ........................................179
9.6 Unhandled exception in Logic, object variable not set [91] .............................182
9.7 Asset Monitor ‘bad” .........................................................................................183
9.8 Asset Monitor ‘good’ but unexpected messages.............................................193
9.9 Can’t acknowledge alarms in 800xA ...............................................................194
9.10 National Language Support does not work in Faceplate .............................194
9.11 Error Correction: Too many files [67] ...........................................................194
9.12 Error Correction: Event Collector .................................................................194
9.13 Maintenance Faceplate not proper displayed ..............................................198
1TGC910032M0201 5
Operation
1 General
1.1 Target Group

This document describes the operation of MNS iS Condition Monitoring System.
The manual is primarily intended for engineering, commissioning and maintenance staff
requiring information about operation of this system.
It is assumed that the reader of this manual is familiar with basic terms and features of
low-voltage switchgear and MCC, especially MNS iS and Automation products like ABB’s
800xA and its use and operation.
It is not necessary that the reader is an ABB 800xA expert, but in case of any doubt,
please contact your responsible support.
It is further assumed that the reader of this manual is familiar with basic terms of fieldbus
and control communication (e.g. basic knowledge about PROFIBUS, Modbus etc.).
1.2 Use of Warning, Caution, Information and Tip icon
6 1TGC910032M0201
Operation
1.3 Terminology
List of the terms, acronyms, abbreviations and definitions that the document uses.
Abbreviation Term Description
CMMS Computerized Computerized Maintenance Management System,

Maintenance like e.g. Maximo, SAP Plant, and others. Systems
Management which are used to store spare parts, to organize
System maintenance stuff, to schedule maintenance tasks,
to store and analyze maintenance reports and faulty
assets, etc.
DCS Distributed See also PCS

Control System
DTM Device Type Software module used to manage devices via

Manager fieldbus (e.g. PROFIBUS) using frame application
environment (e.g. PactWare, ABB Fieldbus Builder
etc.)
Eth. Ethernet Ethernet is a local area network (LAN) technology.

The Ethernet standard specifies the physical
medium, access control rules and the message
frames.
FBP FieldBusPlug ABB technology for exchangeable fieldbus interface

on intelligent field devices (e.g. transmitter, simple
motor starter)
FD Field Device Term for devices connected to the fieldbus (e.g.

motor control units or circuit breaker protection)
HMI Human Machine Generic expression

Interface
LVS Low voltage A factory built assembly built to conform with IEC
switchgear 60439-1
MCC Motor Control Common term for switchgear used for motor control
Centre and protection.
MNS Modular Low Voltage Switchgear family from ABB
MNS iS The integrated intelligent switchgear solution from

ABB
1TGC910032M0201 7
Operation
MStart MNS iS components integrated in the switchgear,

MFeed see the MNS iS System Guide for technical details
MControl
MLink
MView
MNavigate
MODBUS Fieldbus communication protocol
MODBUS RTU Fieldbus communication protocol
Motor Starter Consists of motor controller and electrical

components to control and protect a motor, part of
Motor Control Center
NLS Native Language Providing the ability to change the language of

Support software tools in order to support native languages
(English is basis, others are optional)
OPC OLE for Process Control, an industrial standard for

exchange of information between components and
process control application
PCS Process Control High level process control system

System
PLC Programmable Low level control unit

Local Controller
PROFIBUS-DP Fieldbus communication protocol with cyclic data

transfer (V0).
PROFIBUS- Fieldbus communication protocol, extension of

DP/V1 PROFIBUS- DP allowing acyclic data transfer and
multi master (V1).
PROFIBUS- Fieldbus communication protocol, extension of

DP/V2 PROFIBUS- DP allowing time stamp and
communication between master and slave (V2).
RCU Remote Control Local control unit with pushbutton and indicator to
Unit operate a device (e.g. motor) from field level.
RTC Real Time Clock Integrated clock function in devices used to generate
time and date information if a remote clock system is
not present
TCP/IP Transmission TCP/IP is a high-level connection oriented , reliable,

Control Protocol / full duplex communication protocol developed for
8 1TGC910032M0201
Operation

Internet Protocol integration of the heterogenous systems.
800xA ABB’s Extended ABB’s Extended Automation System is a software

Automation platform for various ‘functional blocks’ like
System 800xA
• Core
Always required as a base, basic system
functionality
• Connectivity
How are the sub-systems connected to
800xA, e.g. OPC, Profibus, Modbus, etc.
• Control
Operation and Automation
• Information Management
Extended data-recording and visualization,
database-functions
• Asset Optimization
• Production, Batch and Manufacturing
Management
1.4 References
[1] MNS iS Interface Manual OPC Server 1TGC910149M0201
[2] 800xA Documentation SV5.1 as delivered together with Software
[3] MNS iS Condition Monitoring R6.0
Quick Guide 1TGC910023M0201
[4] MNS iS Condition Monitoring R6.0
Installation Manual 1TGC910031M0201
1TGC910032M0201 9
Operation
2 Installation of Asset Monitors, Faceplates and other

standard functions
All functions described in this document are standard functions delivered with MNS iS
object types. Only ‘options‘ are not included in the standard.
As described in [7], it is highly recommended to use MNS iS object types. A pure import of
the aspect ‘Asset Monitor’ or ‘Faceplate’ will not work properly. Reasons are required reset
of alarms, setting of parameters, faceplate and most important the control connection to
the MNS iS OPC Server.
For the details of the installation see [7]
2.1 Backup & restore

A safe operation of a software system includes a proper backup strategy. This is to be
prepared for situations where a hardware failure or a change in the system configuration
has led to the need to restore the system to a previous state without the need to reinstall
every package from scratch.
The backup strategy is a task of the IT infrastructure team and this manual only describes
some general recommendations.
A low-level backup of the system shall be performed
• after initial installation (as described in [7])
• before installation of other software packages on the PC
• on a regular basis to prevent loss of recent configurations and data after hardware
failures
There are several tools available for the task to backup a whole hard disc. (such as
Acronis, Ghost, …)
Thos tools usually support the various backup scenarios
• Full backup
saves a complete partition or hard disc
• Incremental backup
using the information from the backup history, the incremental backup only saves
latest changes.
• Differential backup
using the information from a single full backup only the differences are saved.
Which of the strategies is the best and appropriate schedule settings depends on company
rules, given IT infrastructure and cannot be recommended in general.
10 1TGC910032M0201
Operation
3 General usage of AssetMonitor Aspects

This section explains the common usage of all kind of Asset Monitor Aspects, which are
used in the 800xA AssetOptimizer Environment.
The explanation is not limited to the MNS iS Asset Monitors for MStart, MFeed, MLink and
Cubicle objects, but also valid for other Asset Monitors such as the ones delivered as
Basic Asset Monitors together with the 800xA AO basic installation.
However, the screen shots are taken from a running MStart AssetMonitor.
3.1 Operation
3.1.1 Main view

When selecting an Asset Monitoring Aspect of an 800xA Object, the main view of the
Asset Monitor will be shown which looks like a table.
In general the table view is self-explaining. In first line of the table, the topics are named
belonging to the column.
For the MNS iS Asset Monitors, the TimeStamp is taken directly from MNS iS, other AM
usually uses the timestamp of the PC system.
1TGC910032M0201 11
Operation
3.1.2 Condition mark-up and access to further functionality

If a condition is raised, severity, condition, sub-condition, description, timestamp and
quality status are updated and severity is coloured.
Move now the mouse to this cell and click with right mouse button, a menu will appear.
12 1TGC910032M0201
Operation
Click on ‘Condition Details’ to receive further details to the issue occurred. A new view will
be shown with all information for this issue available in the system.
If a Maximo connection is installed a separate button will appear on the top line. Clicking
on this button, all details about this issue will be transferred to Maximo. See [5].
1TGC910032M0201 13
Operation
Maximo
This functionality is available as well in the menus via right mouse click.
3.1.3 Some examples from the MStart AssetMonitor

• Example ‘Undervoltage alarm”
14 1TGC910032M0201
Operation
• Example “ TOL Trip”
1TGC910032M0201 15
Operation
16 1TGC910032M0201
Operation
3.1.4 Available menus for AssetMonitor aspects
• Window pinning
If the Asset Monitor is opened with double-click, a separate window will be opened. With
icon ‘Pin / Unpin the Display’ this window can be fixed and will not be closed if another
window will be opened.
• Main view / configuration view

With below marked icon, it is possible to open ‘Configuration View’ or ‘Main View’ of the
Asset Monitor.
Configuration view enables editing of settings, parameter, input records, output records
and others.
Do not change in the configuration view input records, output records, conditions or
logic.
For our MNS iS Asset Monitors: Do never set the ‘Logic Execution Interval’ to
values lower than 60 seconds.
‘Main view’ is the normal operation view of the Asset Monitor.
1TGC910032M0201 17
Operation
• Other functions
With the below marked icon, it is possible to open a menu for different other functions.
Here is another one interesting, ‘Print’ functions.
18 1TGC910032M0201
Operation
Do select connected printer in the lists or print out in Microsoft XPS format.
1TGC910032M0201 19
Operation
3.2 Settings, Configuration and Parameterization of Asset Monitors

In general, settings and parameters are modified within the ‘Config View’ of an ‘Asset
Monitor”.
Please note that the 800xA Aspect Object technology allows for modifying settings in
different places of the system with different consequences.
Remember the following object relations:
A MNS iS Object (e.g. a Motor Starter) has an Object Type (e.g. MStart_log03s). This
Object type contains a list of preconfigured Aspect Categories, to be instantiated on the
object instances.
The Motor Starter Object inherits the settings for its Aspects from the Object Type.
A preconfigured Aspect on the Object type again inherits its parameters from its Aspect
Category.
The engineer has the possibility to break the inheritance and define his own values on
each level.
This results in the following schema of the reach of changes:
20 1TGC910032M0201
Operation
MNS iS Object type Aspect category

Object
Example Motor_N1 Is of type MStart_log03s Has an aspect of category ABB_MNSiS_AM_MStart

Feed_F23 Is of type MFeed_NoLog Has an aspect of category ABB_MNSiS_AM_MFeed
MLink_00091 Is of type MLink_R Has an aspect of category ABB_MNSiS_MLink_primary
Primary Control Object Type Aspect System Structure

structure in Structure Structure
800xA
Scope of Exactly the All instances All instances of the

Changes Object created from AssetMonitor respecting the
instance this type ‘inherited’ flag
respecting the
‘inherit’ flag
The following sections differentiate ‘settings’ from ‘configuration’ and ‘parameter’ data.
‘Settings’ influence the behaviour of the AssetMonitor in relation to the Asset Optimization
environment. e.g. execution interval of the AssetMonitor.
‘Configuration data’ reflect the function of the MNS iS device in the process (e.g. Mstart is
configured as NR_DOL, an MLink is configured as redundant) and the adoption to the
configured protection and alarm applications running on that device.
‘Parameter data’ finally define certain levels or constraints defining the algorithmic
behaviour of the Asset Monitoring logic, e.g. the limits of the contact temperature
supervision.
3.2.1 Settings
For settings it is recommended to edit those in the ‘Aspect System Structure’ or in the
‘Object Type Structure”. As an option individual settings might be set for each MStart,
MFeed, MLink or Cubicle in the Control Structure.
Following Settings are available:

• Server Assignment:
‘Default’ for single-nodes or single Asset Optimization Server Applications.
In multi-node systems, please select correct Asset Optimization Server for the
Asset Monitors. This might be required for each Asset Monitor in multi Asset
Optimization Server Applications.
• Logic Execution Interval for MStart and MFeed Asset Monitor:
Value in seconds. Minimum value for these Asset Monitors is 60 seconds.
Values smaller than 60 seconds are neither supported nor guaranteed and may
result in malfunction of the whole Asset optimizer environment.
1TGC910032M0201 21
Operation
• Logic Execution Interval for Cubicle Asset Monitor:

Value in seconds. Minimum value for this Asset Monitor is 600 seconds.
Values smaller than 600 seconds are neither supported nor guaranteed and may
result in malfunction of the whole Asset optimizer environment.
• Logic Execution Interval for MLink Asset Monitor
Value in seconds. Default is 60000. There is no need to change this time, since the
logic of the Asset Monitor uses a new trigger feature and is executed each time the
input data changes.
3.2.1.1 Modification of Settings in ‘Aspect System Structure”

All modifications done in Aspect System Structure are valid for all Asset Monitors of this
category in the 800xA system. Use this method to make changes for settings of all Asset
Monitors like i.e. ‘Logic Execution Interval”.
The following procedure is done on the MStart Asset Monitor ABB_MNSiS_AM_MStart”. It
is, of course, valid for all types of AssetMonitors.
• Navigate to the ‘Aspect System

Structure’ – Aspect System ‘Asset
Monitoring’ – Aspect Type ‘Asset
Monitors’ – Aspect Category
‘ABB_MNSiS_AM_MStart”
• Click on aspect
‘ABB_MNSiS_AM_MStart”.
• In the Aspect System Structure the
Configuration View of the Asset
Monitor will be opened.
22 1TGC910032M0201
Operation
• Go to relevant tab, in this example here ‘Asset Monitor’, change the setting,
• Do not forget to click ‘apply’ in the lower right area of the view
1TGC910032M0201 23
Operation
To activate those changes, please read sec 3.3
3.2.2 Configuration and parameterization

In this section we discuss how to reflect the actual configuration of a MNS iS device into
the configuration of the AssetMonitor, so that the logic can act accordingly.
We will use the term ‘parameters’ including both, the configuration settings and the logic
parameters as defined earlier.
There are two main ways to change the Asset Monitor parameterization: One via the
‘configuration view’ of the Asset Monitor, the second via a bulk data interface based on MS
Excel workbooks. Since it is assumed, that the majority of applications deals with the
parameterization of many motors, the Bulk Data approach is described first.
Please read sec 3.2.3 to understand, in which situations parameters are changed on the
Aspect Category, The Object Type, or the Object instance.
3.2.2.1 Modification of parameters with Bulk Data Manager

The 800xA engineering tools include a mechanism to upload bulk data from an MS Excel
workbook into 800xA objects. This tool is called ‘Bulk Data Manager’ (BDM)
The main workflow consists of
• exporting object identifications and parameter lists from 800xA into MS Excel,
• change the data using the rich functionality of Excel,
• and save the changed values back into 800xA
To enable efficient use several template MS Excel workbooks are provided as part of the
MNS iS Condition Monitoring package.
To find them, navigate with Windows Explorer to ABB MNS iS Files for 800xA, where the
dll-file of Asset Monitor and afw-file of Object Types are located.
Open Sub-directory ‘BDM Templates”. There are 5 Templates available:
• ‘MNSiS MStart BDM Template’ for MStart Asset Monitor
• ‘MNSiS MFeed BDM Template’ for MFeed Asset Monitor
• ‘MNSiS MCubicle BDM Template’ for Cubicle Asset Monitor
• ‘MNSiS MLink BDM Template NonRedundant’ for MLink Asset Monitor
• ‘MNSiS MLink BDM Template Redundant’ for MLink Asset Monitor
Double-click on the relevant BDM Template to open MS Excel with it.
It is assumed that Bulk Data Manager is proper installed at your 800xA

Engineering Workplace, see [5]
24 1TGC910032M0201
Operation
1TGC910032M0201 25
Operation
MS Excel may be opened with an error message. This error message only indicates that
connection to 800xA is not yet established for this document.
Click ‘ok’ and continue.
26 1TGC910032M0201
Operation
Navigate to ‘Add-Ins’ tab, click on ‘No System’ of the Bulk Data Manager menu inside MS
Excel.
Take care:
The BDM Template for MStart, MFeed, and MLink Asset Monitors must be
connected to Control Structure as described here.
The BDM Template for Cubicle Asset Monitors must be connected to Location
Structure. This is important!
A new window will open to attach a 800xA system.

Click on ‘Root, Domain’ and afterwards on ‘ok’.
1TGC910032M0201 27
Operation
Select Control Structure for MStart and

MFeed and MLink Asset Monitors.
Select Location Structure for Cubicle
Asset Monitors.
MS Excel looks like this now.
28 1TGC910032M0201
Operation
Leave MS Excel open, change to 800xA workplace and navigate to relevant structure
where the objects are located which are intended to edit Asset Monitor Parameters.
Drag&Drop with the mouse the relevant ‘ABB MNSiS OPC Server Network’ object or the
‘root’ object into MS Excel, leftmost column.
The Bulk Data Manager is looking now for all relevant objects which are of the correct type
and contain the right Asset Monitor. Only these Asset Monitor Parameters are possible to
edit.
Depending on the number of objects this may take some seconds.
All Asset Monitor Objects of the matching type are now in the Bulk Data Manager MS
Excel sheet listed.
1TGC910032M0201 29
Operation
Navigate to the row of the object to be edited. Lookup the fifth column named
‘AssetParamsInheritFromParent”. Change text in cell from TRUE to FALSE. This disables
the automatic inheritance of the asset monitor parameters from the object type.
30 1TGC910032M0201
Operation
Please note: If you change later parameters on the Object Type or on the Aspect
category, those object you modify here will not be affected!
Repeat this for all objects for which you want to edit Asset Monitor Parameters.
1TGC910032M0201 31
Operation
32 1TGC910032M0201
Operation
If all ‘InheritFromParent’ parameters are set correctly, click on icon ‘Save All Objects’ of
Bulk Data Manager menu. This will transfer these data and enable in general the
changeability of the other parameters.
Navigate now through the MS Excel sheet and edit all parameters. In the coloured line
(see ‘1’ in figure) all Asset Monitor Parameter Names are listed, below all parameter
values for the objects are displayed.
1TGC910032M0201 33
Operation
Changed parameter
Do ignore the”Error” tab.
If all parameters are updated and correct, click again on icon ‘Save All Objects’. Now all
parameters are transferred to all relevant Asset Monitors inside 800xA.
34 1TGC910032M0201
Operation
Following window displays the data transfer.
1TGC910032M0201 35
Operation
Data transfer is finalized. The”Error” tab is disappeared.
The orange frame shows whenever the AMs parameter has modified and pending
download to AO Server. It will be disappeared when the AMs completely downloads into
AO Server.
36 1TGC910032M0201
Operation
You can confirm now in 800xA, ‘config view’ of the Asset Monitor, that the parameters are
changed.
1TGC910032M0201 37
Operation
3.2.2.2 Modification of parameters in Asset Monitor

To change parameters on a single object the ‘Configuration View’ of the Asset Monitor is
used.
Go to tab ‘Asset Parameters”.
38 1TGC910032M0201
Operation
Uncheck ‘inherit configuration”.
1TGC910032M0201 39
Operation
Change the parameter settings and click on ‘apply”. Scroll down the window if you don’t
find the parameter you are looking for.
40 1TGC910032M0201
Operation
Go to Asset Monitor tab then click ‘Load Configuration to AO Server’ button.
Click on ‘Continue’.
1TGC910032M0201 41
Operation
The new settings of the Asset Monitor are loaded to the AO Server and now valid.
42 1TGC910032M0201
Operation
3.2.3 Changing Settings on Object instance vs on Object Type vs on Aspect

Category
As described earlier, the nature of the 800xA objects allows for modifying settings on three
layers: On the Aspect category, On the Object Type, or on the Object instance.
We can only give some general rules how to decide, where to change actually.
• Changes on Aspect Category
o Pro
 System wide change for all instances of this Asset Monitor
 Therefore single point of change
o Contra
 Maybe overwritten in case of updates of the MNS iS Condition
Monitoring package
o Not recommended, feasible for changing settings like ‘execution interval’
• Changes on Object Type
o Pro
 System wide change for all instances of this Object Type. Remember,
that an Aspect Category can be used on several Object Types, e.g.
category ‘ABB_MNSiS_MLink_primary’ is used on Object Types
‘MLink’ and ‘MLink_R’
 Central point of change for large class of instances
o Contra
 Maybe overwritten in case of updates of the MNS iS Conditrion
Monitoring package
o Recommended e.g. for systems with a dominant type of Starter, eg. 70% of
all starters are REV_DOL, 400V, 8.5A, and a defined set of protection
function. The other starters can afterwards be adopted on instance level.
• Changes on Object instance
o Pro
 Individual setting and optimizing of functionality
o Contra
 increased effort to get all data changed
 need for careful tracking of changes
o Recommended for small systems and, of course, to adjust to special types of
applications on single instances.
1TGC910032M0201 43
Operation
3.2.3.1 Modification of Settings in ‘Aspect System Structure”

All modifications done in Aspect System Structure are valid for all Asset Monitors of this
category in the 800xA system. Use this method to make changes for settings of all Asset
Monitors like i.e. ‘Logic Execution Interval”.
The following procedure is done on the MStart Asset Monitor category
‘ABB_MNSiS_AM_MStart”. Obviously this is valid for all types of AssetMonitors.
• Navigate to the ‘Aspect

System Structure’ – Aspect
System ‘Asset Monitoring’ –
Aspect Type ‘Asset
Monitors’ – Aspect Category
‘ABB_MNSiS_AM_MStart”
• Click on aspect
‘ABB_MNSiS_AM_MStart”.
• In the Aspect System
Structure the Configuration
View of the Asset Monitor
will be opened.
• Go to relevant tab, in this example here ‘Asset Monitor’, change the setting,
• Do not forget to click ‘apply’ in the lower right area of the view
44 1TGC910032M0201
Operation
3.2.3.2 Modification of Settings in ‘Object Type Structure”

All modifications done in Object Type Structure are valid for all Asset monitors belonging
to this individual Object Type. Use this method to make changes for settings or parameters
of all Asset Monitors like i.e. ‘opt_NR_DOL’ in smaller systems.
The following procedure is done on the MStart Asset Monitor category
‘ABB_MNSiS_AM_MStart”. It is, of course, valid for all types of AssetMonitors and Object
Types
• Navigate to the
‘Object Type Structure’ – Object Type Group ‘ABB MNSiS Objects’ – Object Type
‘ABB_MNSiS_MStart_AM_Log03s’
or your individual Object Type to be modified.
• Click on Asset Monitor aspect, e.g. ‘ABB_MNSiS_AM_MStart”. In the Object Type
Structure the Configuration View of the Asset Monitor will be opened.
1TGC910032M0201 45
Operation
• Go to relevant tab, in this example here ‘Asset Monitor’, disable ‘Inherit

configuration”, arrow ‘1”.
• Change the settings, arrow ‘2”.
• Click on ‘apply”, arrow ‘3”.
46 1TGC910032M0201
Operation
1 2
3.2.3.3 Modification of Settings in ‘Config View’ of individual ‘Asset Monitor”

All modifications done in Control Structure are valid for this special Asset Monitor. Use this
method to make changes for settings or parameters individual for one Asset Monitors like
i.e. ‘opt_NR_Dahlander”.
Sec 3.2.2.2 describes how to change parameters on the instance level.
3.3 Activating Asset Monitors and their setting, configuration and

parameters
After initial installation and after each change of the configuration of the Asset Monitors the
configuration has to be activated to be operational. This process transfers the
configuration into the Asset Optimizer Engine, which controls and schedules the execution
of the Asset Monitor Logic.
Again, there are two ways to activate, the one operates on a single instance, the other
operates on a collection of Asset Monitors.
1TGC910032M0201 47
Operation
3.3.1 Activating a single Asset monitor

Navigate in Control Structure to the Object, on which the Aset Monitor needs to be
activated / updated. If you open the ‘config view’ of the Asset Monitor Aspect, you get the
following ‘AssetMonitor’ tab.
(Please note the slight differences to the view in object Type structure or Aspect System
structure)
Let’s have a look at the ‘Asset Monitor Configuration Lifecyle’ part. It shows primarily the
current status of the Asset Monitor:
• Disabled
Excluded from execution on any Asset Optimizer Server
• Enabled, Not Loaded
ready for operation, but not activated
• Loaded, current
activated and operational
• Loaded, not current
activated and operational, but configuration changes are pending.
Those pending actions may arise from changing parameters on category, object
type or object level.
48 1TGC910032M0201
Operation
In order to activate an AssetMonitor or update the active configuration,

• press the button ‘Load Configuration to AO server’.
• The following window pops up.
• And the progress is shown in an overlay, which is closed using the cross in the
upper right corner.
The ‘LifeCycle’ section shows the time of the last successful configuration activation.
1TGC910032M0201 49
Operation
3.3.2 Bulk changing for many Asset Monitors

For the case of many changed Asset Monitors in the 800xA system, e.g. after initial
instantiation or after a bulk upload of parameters from MS Excel, a bulk activation
procedure is available.
This procedure uses the Object, representing the Asset Optimizer Server in control
structure.
• For Single Node systems
o Navigate to ‘Control Structure’ – Root – Asset Optimization – AO Server.
• For multi Node Systems
o Navigate to ‘Control Structure’ – Root – Asset Optimization
o There are several server objects
o Navigate to the server object you want to update.
• Click on aspect ‘Asset Optimization Server”.
• Go to tab ‘Asset Monitors’
• If you want an unconditional update of all active AssetMonitors on that server, click
on ‘Load all AMs”.
• Wait until all Asset Monitors are loaded and wait until function is finalized.
50 1TGC910032M0201
Operation
• If you do not needto update all Asset Monitors you can select a sub-set of the
shown objects with the mouse. The list can be sorted column wise to facilitate the
selection process.
1TGC910032M0201 51
Operation
• Right mouse click, select out of menu ‘Load selected AM configuration’.
• Click on ‘Continue’ in new window.
52 1TGC910032M0201
Operation
1TGC910032M0201 53
Operation
• Wait until lower window displays ‘Load operation successful’. Function now
finalized.
54 1TGC910032M0201
Operation
4 MStart Asset Monitor
4.1 Conditions
Following conditions are used in the Asset Monitor:
• MControl, electrical
• MStart, electrical
• Motor, electrical
• Motor, mechanical
• Operating Conditions
• General Purpose
• Supply side, electrical
All conditions give a first indication about the device involved (MControl, MStart, Motor,
Supply side) and type of problem (electrical, mechanical) or a general information
(Operating Condition, General Purpose).
4.2 Layout and Definitions

The layout, used colors and wording is specified according NAMUR guidelines and fixed
for ABB 800xA.
All relevant information is divided into 7 ‘conditions’ (2nd column to the left). The ‘severity’
of the condition is shown between 1 and 1000 (1000 most severe problem) in the 1st
column to the left. The column ‘sub-condition’ classifies together with severity the type of
1TGC910032M0201 55
Operation
problem. The following columns show the description of the problem, the timestamp (MNS
iS timestamp) and the quality status of the information (good = trust, bad = not valid).
For more information, see [6]
4.3 Sub-Conditions and Severity
Severity Sub-Condition Description

1 Normal Motor is available. Status is ‘normal”.
Asset functionality is fully available. No
maintenance is required.
2 Failure General Purpose Input

As this is a customer specific function the severity
as well as the condition details ‘description”,
‘possible cause’ and ‘suggested action’ might be
defined by the customer.
The logo will depend on selected severity.
100 Maintenance required Motor is available. Status is ‘maintenance
(soon) required (soon)”.
Asset functionality fully available but maintenance
required soon to avoid functional restrictions, e.g.
caused by a nearly exhausted wear reserve or
operating conditions.
250 Maintenance required Motor is available. Status is ‘maintenance
(now) required (now)”.
required now to avoid functional restrictions, e.g.
caused by an exhausted wear reserve or
operating conditions.
400 Out of Specification Motor is still available. Status is ‘out of
specification”.
Asset functionality available but decreased due to
operating conditions outside the specified limits.
500 Out of Specification Motor is still available. Status is ‘out of
specification”.
internal problems.
750 Function Check Motor has been stopped. Operation is not
possible. Status is ‘function check”.
Asset functionality might be temporarily restricted,
due to on-going work on the asset, e.g. as local
operation, maintenance (main-switch off),
simulation or a function check (test-position).
900 Failure Motor has been stopped. Status is ‘failure”.
Asset Functionality lost due to malfunction of its
peripherals or due to operating conditions.
56 1TGC910032M0201
Operation

1000 Failure Motor has been stopped. Status is ‘failure”.
Asset Functionality lost due to malfunction in the
asset itself.
4.4 Operation
The general operation is described in sec 3.1
The TimeStamp is taken directly from MNS iS.
If you modify settings, do not reduce the execution interval time below 60sec
4.5 Parameter
Following parameters are available:
Default
Parameter name value Description
Inhibit value for Asset Monitor. Set to
INHIBIT_VALUE TRUE FALSE will stop the Asset Monitor.
National Language Support Setting,
Default_Language en-us language to be used in Asset Monitor
# Specific limits
400 Rated voltage [V] of MNS iS in existing
RATED VOLTAGE (integer) system
105 Rated contact temperature in [°C]
CONTACT_TEMPERATURE_MAX (integer) Do not change!
Supervision period for all functions
8760 ‘operation supervision 1 and 2’ given in
MSTART_OPERATION_CHECK_MIN_TIME (integer) [hours]
Minimum limit of operating hours below
the function ‘operation supervision 1’ will
be active. Value will be referenced against
supervision period.
Value will be referenced in addition if
switch cycles of all contactors are smaller
50 than parameter
OPERATING_HOURS_MIN (integer) SWITCH_CYCLES_K_MIN.
Absolute minimum limit of switch cycles for
all contactors below the function ‘operation
supervision 2’ will be active. Value will be
referenced against supervision period.
SWITCH_CYCLES_K_ABSMIN 1 (integer) Operation supervision for no switch cycles!
Minimum limit of switch cycles for all
contactors below the function ‘operation
50 Value will be referenced in addition if
SWITCH_CYCLES_K_MIN (integer) switch cycles of all contactors are smaller
1TGC910032M0201 57
Operation
Default
than parameter
OPERATING_HOURS_MIN.
Maximum limit above function ‘too many
10 start limitations’ will be active. Value will
START_LIMITATION_COUNTER_MAX integer) be referenced against supervision period.
24 Supervision period for function ‘too many
START_LIMITATION_TIMER_MAX (integer) start limitations’ given in [hours]
10 thermal overloads’ will be active. Value will
TOL_COUNTER_MAX (integer) be referenced against supervision period.
TOL_TIMER_MAX (integer) thermal overloads’ given in [hours]
Maximum limit above function ‘Electronic
Failures’ will be active. Value will be
3 referenced against supervision period.
EF_COUNTER_MAX (integer) Do not change!
EF_TIMER_MAX Supervision period for function ‘Electronic
1344 Failures’ given in [hours].
(integer) Do not change!
TIME_TO_TRIP_EVENT Diagnostic-value ‘time to trip’ must drop
14400 below this level in order to activate
(integer) maintenance function, given in [seconds]
COSPHI_ALARM_LEVEL Maximum limit above function ‘cos ϕ
supervision (max. value of last hour)’ will
be active. This is the limit for supervision
0.9 of the maximum value of cos ϕ reached
(float) during the last hour.
COSPHI_ALARM_TIMEDELAY Supervision period for function ‘cos ϕ
supervision (max. value of last hour)”. The
cos ϕ value exceeded during this
1 supervision period the maximum allowed
(float) level, given in [hours]
COSPHI_ALARM_AV_LEVEL Maximum limit above function ‘cos ϕ
supervision (average value of last hour)’
will be active. This is the limit for
0.9 supervision of the average value of cos ϕ
(float) reached during the last hour.
COSPHI_ALARM_AV_TIMEDELAY Supervision period for function ‘cos ϕ
supervision (average value of last hour)”.
The cos ϕ value exceeded during this
# Configuration: Installed options
opt_NR_DOL MStart is a non-reversing direct-on-line
TRUE starter
opt_NR_DOL_HD MStart is a non-reversing direct-on-line
FALSE starter with heavy-duty startup
opt_DOL_REV FALSE MStart is a reversing direct-on-line starter
58 1TGC910032M0201
Operation
Default
opt_2N_DOL MStart is a 2 speed motorstarter with
FALSE isolated windings
opt_SD FALSE MStart is a star-delta starter
opt_Dahlander FALSE MStart is a Dahlander starter
opt_fused TRUE MStart has fused short-circuit protection
opt_Softstarter A Softstarter is connected to MStart. This
parameter is an addition to the above ones
which describe the motorstarter
FALSE application.
# installed Alarms and Trips - Others
ae_others_Watchdog_IRF_HW_SW TRUE MControl with Watchdog function
ae_others_ProgrammableLogicRegister TRUE MControl with programmable logic register
ae_others_GPI_MSDV_valid MControl with function ‘MSDV supervision
FALSE of MStart”
ae_others_GPI_MSDV 1 GPI-Register MSDV is connected to
(integer
1 .. 16)
ae_Others_GPI_MSDM_valid MControl with function ‘MSDM supervision
FALSE of MStart”
ae_others_GPI_MSDM 2 GPI-Register MSDM is connected to
(integer
1 .. 16)
ae_others_ExternalTrip1 TRUE MControl with function ‘External Trip 1”
ae_others_ExternalTrip1_MSD_Alarm Any MSDM or MSDV is connected to
FALSE function ‘External Trip 1’ as Alarm
ae_others_ExternalTrip1_MSD_Trip Any MSDM or MSDV is connected to
FALSE function ‘External Trip 1’ as Trip
# installed Alarms and Trips –
Maintenance
ae_maint_OperatingHoursSup MControl with Operating Hours
TRUE Supervision for the motor
ae_maint_MStartSup TRUE MControl with MStart Supervision
ae_maint_MStartInsertionCycleSup MControl with MStart Insertion Cycle
TRUE Supervision
ae_maint_LocationSup TRUE MControl Location Supervision
ae_maint_ContactorSwitchCycleSup MControl with Contactor Switch Cycle
TRUE Supervision for all contactors
ae_maint_FuseSup MControl with Fuse Supervision. Attention:
TRUE Parameter ‘opt_fused’ must be TRUE!
ae_maint_ControlVoltageSup TRUE MControl with Control Voltage Supervision
ae_maint_ContactTempUnbalance MControl with Contact Temperature
TRUE Unbalance Supervision
1TGC910032M0201 59
Operation
Default
ae_maint_ContactTempSup MControl with Contact Temperature
TRUE Supervision
# installed Alarms and Trips - Protection
ae_prot_Temperature2 Historical parameter.
FALSE Do not change!
ae_prot_ThermalOverload TRUE MControl with Thermal overload protection
ae_prot_Stall TRUE MControl with Stall protection
ae_prot_PTCSup Motor equipped with PTC sensor,
MControl with PTC protection. Attention:
TRUE hardware required!
ae_prot_PhaseLossUnbalance MControl with Phase Loss, Phase
TRUE Unbalance protection
ae_prot_UnderloadCosPhi TRUE MControl with Underload cos φ protection
ae_prot_NoLoad_Underload MControl with No Load, Underload
TRUE protection
ae_prot_EarthLeakage TRUE MControl with Residual Current protection
Ae_prot_EarthLeakage_externalTrip2 MControl with external Residual Current
protection relay connected to function
FALSE ‘External Trip 2”
Ae_prot_UnderVoltage TRUE MControl with Under Voltage protection
# installed Alarms and Trips - Control
ae_ctrl_StartLimitation TRUE MControl with Start Limitation supervision
ae_ctrl_MainSwitchSup TRUE MControl with Main-switch supervision
ae_ctrl_ControlAccess TRUE MControl with Control Access supervision
# Measurement Values
mv_MStartInsertionCycle Measurement Value ‘MStart Insertion
TRUE Cycles’ available through OPC
mv_ContactTemperatures Measurement Values ‘Contact
TRUE Temperatures’ available through OPC
mv_SwitchCycles Measurement Values ‘Switch Cycles Kx’
TRUE for all contactors available through OPC
mv_OperatingHours Measurement Value ‘Operating Hours’ for
TRUE the motor available through OPC
Mv_Rated Voltage Measurement Value ‘Rated Voltage’ for all
TRUE phases available through OPC
Mv_ContactTemperatures_Negative When TRUE, enable function ‘Supervision
TRUE of negative contact temperatures”
Mv_cosphi_max When TRUE, enables function ‘cos ϕ
FALSE supervision (max. value of last hour)”
Mv_cosphi_average When TRUE, enables function ‘cos ϕ
FALSE supervision (average value of last hour)”
# Powerloss Supervision
60 1TGC910032M0201
Operation
Default
RatedCurrent 8.50 Rated Current of MStart defined in MNS
(float) Engineer, given in [A]
Pv_Current_Dependent 3.09 Current Dependent Powerlosses of MStart
(float) defined in MNS Engineer, given in [W]
Pv_Current_Independent Current Independent Powerlosses of
8.50 MStart defined in MNS Engineer, given in
(float) [W]
Pv_Diag_Powerloss_Calc When TRUE, enable function ‘Online
FALSE Powerloss Calculation”
DiversityFactor 0.6 Diversity Factor of MStart defined in MNS
(float) Engineer
4.6 Functionality
See also MNavigate help file.
For each function it is described,
• what the functionality is,
• which Asset-Monitor Parameters are related to it,
• which OPC items are related to it
• what are the required MNS Engineer selections
• and which MControl/MStart applications are related
4.6.1 Condition Monitoring functions
4.6.1.1 Contact Temperature Monitoring

Available for outgoing contacts of MStart. Alarm and Trip handling is based on the limit
values and time delay settings in MNavigate. Special issue is the Contact Temperature
Unbalance function for MStart for low loaded MStart. The difference between Maximum
and Minimum of Contact Temperatures is recognized.
AM-Parameter: (definitions see 4.5)

ae_maint_ContactTempSup = TRUE
ae_maint_ContactTempUnbalance = TRUE
ae_prot_Temperature2 = FALSE
OPC-group/-variable: AlarmEvent/ …
ContactTemperatureL1A, ContactTemperatureL2A,
ContactTemperatureL3A, ContactTemperatureL1B,
ContactTemperatureL2B, ContactTemperatureL3B,
AlarmEvent/ ContactTemperatureUnbalance
1TGC910032M0201 61
Operation
MNS Engineer: Contact Temperature Supervision

Contact Temperature Unbalance
Application: All MStart
4.6.1.2 Insertion Cycles

Insertion cycles of MStart are observed. Maintenance required every 100 cycles. Alarm will
be set. Small maintenance work until 500 cycles, higher effort maintenance work 600 –
1000, finally end of lifetime at 1000 cycles / exchange MStart. Reset of alarms with
faceplate.

mv_MStartInsertionCycles = TRUE
ae_maint_MStart_InsertionCycleSup = TRUE
OPC-group/-variable: MeasurementValues/ InsertionCycles
MNS Engineer: MeasurementValues/ Insertion Cycles
Disable in MNavigate the Alarm for function ‘MStart Insertion Cycles”. This function
is not used by the Asset Monitor and would lead to confusion.
62 1TGC910032M0201
Operation
4.6.1.3 Switch-cycles supervision for all contactors

The number of switch-cycles for all contactors is supervised. Available for all contactors of
MStart depending on the application. These applications are defined with parameter ‘opt_’
specifying the drive-type (i.e. NR-DOL, DOL-REV). Alarm handling is based on the limit
values and time delay settings in MNavigate.
The parameter ‘opt_Softstarter’ is an additional parameter to the other ‘opt_”-parameters
and only used if a softstarter is connected to MStart.
AM-Parameter: (definitions see 4.5)¶

ae_maint_ContactorSwitchCycleSup = TRUE
Select the motor type with following ‘opt_”-parameters:
opt_NR_DOL (only K1) = TRUE
opt_NR_DOL_HD (only K1) = TRUE
opt_DOL_REV (only K1, K2) = TRUE
opt_2N_DOL (only K1, K2) = TRUE
opt_SD (K1, K2, K3) = TRUE
opt_Dahlander (K1, K2, K3) = TRUE
1TGC910032M0201 63
Operation
SwitchCycleSupervisionK1,
SwitchCycleSupervisionK2,
SwitchCycleSupervisionK3
MNS Engineer: Switch Cycle Supervision K1,
Switch Cycle Supervision K2,
Switch Cycle Supervision K3
4.6.1.4 Switch-operation supervision for all contactors

The proper switch-operation of all contactors is supervised. This function is available for all
contactors of MStart depending on the application. These applications are defined with
parameter ‘opt_’ specifying the drive-type (i.e. NR-DOL, DOL-REV). Alarm and Trip
handling is based on the standard functionality.
The parameter ‘opt_Softstarter’ is an additional parameter to the other ‘opt_”-parameters
and only used if a softstarter is connected to MStart.
AM-Parameter: Select the motor type with following ‘opt_”-parameters:

opt_NR_DOL (only K1) = TRUE
opt_NR_DOL_HD (only K1) = TRUE
opt_DOL_REV (only K1, K2) = TRUE
opt_2N_DOL (only K1, K2) = TRUE
opt_SD (K1, K2, K3) = TRUE
opt_Dahlander (K1, K2, K3) = TRUE
FeedbackSupervisionCfK1, FeedbackSupervisionCfK2,
FeedbackSupervisionCfK3
MNS Engineer: Starter Function
4.6.1.5 Welded contactor

A welded contactor will be recognized. Function is available for all contactors of MStart
depending on the application. These applications are defined with parameter ‘opt_’
specifying the drive-type (i.e. NR-DOL, DOL-REV). Trip handling is based on the standard
functionality.

Always active
64 1TGC910032M0201
Operation
OPC-group/-variable: AlarmEvent/ Welded

4.6.1.6 Operating hours supervision for motor

The operating hours of the motor are supervised. Alarm handling is based on the limit
values and time delay settings in MNavigate. Be aware that MStart operating hours and
motor operating hours are always the same with the first motor. If the motor is changed,
the MStart operating hours are much higher.

ae_maint_OperatingHoursSup= TRUE
OPC-group/-variable: AlarmEvent/ OperatingHours
MNS Engineer: Operating Hours
4.6.1.7 Operation Supervision 1

This function is purely running inside 800xA.
Motors which are running with low switching cycles and low operating hours during the
observation period. Only if both conditions are fulfilled the alarm will be set.
AM-Parameters: (definitions see 4.5)

MStart_Operation_Check_Min_Time
Switch_Cycles_K_Min
Operating_Hours_Min
mv_SwitchCycles = TRUE
mv_OperatingHours = TRUE
OPC-group/-variable: Diagnostics/ OperatingHours
MeasurementValues/ …
SwitchCyclesK1, SwitchCyclesK2, SwitchCyclesK3
MNS Engineer: Operating Hours,
Application: Fire protection pumps
Seldom used motors
1TGC910032M0201 65
Operation

Motors which are never switched during the observation period.

Switch_Cycles_K_AbsMin
Application: Continuously running motors
4.6.1.9 Not ready for operation

If the MStart is not ready for operation the Asset Monitor will indicate this. Criteria are
main-switch off, test position active or local control access.

ae_ctrl_MainSwitchSup = TRUE
ae_ctrl_ControlAccess = TRUE
OPC-group/-variable: AlarmEvent/ TestPositionActivated
AlarmEvent/ MainSwitchOff
MNS Engineer: Main Switch Supervision
Control Access
4.6.1.10 MStart Supervision 1

Three different security packages are observing the electronic components in MStart and
raise alarms and trips if required.
• A trip will be raised if the MStart Identnumber does not fit to the identnumber setting
in MControl.
66 1TGC910032M0201
Operation
• A trip will be raised if the motor current setting downloaded from MNavigate does
not fit to the inserted MStart.
• An alarm will be raised if communication is lost between MControl and MStart while
motor is not running.
• A trip will be raised if communication is lost between MControl and MStart while
motor is running.
• An alarm will be raised if there is a risk that the communication will be lost soon due
too high internal temperatures and a trip will be raised if communication is lost
inside the MStart due to too high internal temperatures.

ae_maint_MStartSup = TRUE
mv_ContactTemperatures = TRUE
CONTACT_TEMPERATURE_MAX
OPC-group/-variable: AlarmEvent/ PowerModuleSupervision
AlarmEvent/ PowerModuleSupervision1
AlarmEvent/ TestPositionActivated
Temp11, Temp12, Temp13, Temp21, Temp22, Temp23
MNS Engineer: MStart Type Supervision
Contact Temperature Supervision
MControl Base Software
4.6.1.11 MStart Supervision 2 (MSDM, MSDV and External Trip)

There is one additional security package observing the electronic components in MStart
and raise alarms and trips if required.
• An alarm will be raised if MSDM and/ or MSDV detection is active and linked to
GPI-registers. This is a method to differentiate between MSDM and MSDV. GPI-
registers are preset with default 1 (MSDV) and 2 (MSDM) but can be changed with
parameters.
• MSDM and MSDV can also be connected as an alternative to External Trip 1 as an
alarm or a trip depending on application inside MControl. This required function
‘External Trip 1”. In this case it can be not be differentiated between MSDM and
MSDV.
1TGC910032M0201 67
Operation
ae_others_GPI_MSDV_valid = TRUE
ae_others_GPI_MSDV
ae_others_GPI_MSDM_valid = TRUE
ae_others_GPI_MSDM
ae_others_ExternalTrip1 = TRUE
ae_others_ExternalTrip1_MSD_Alarm = TRUE
ae_others_ExternalTrip1_MSD_Trip = TRUE
OPC-group/-variable: DeviceStatus / GPI
AlarmEvent/ ExternalTrip1
MNS Engineer: MControl Base Software
External Trip 1
4.6.1.12 MStart Supervision 3

Additional security package is observing the electronic components in MStart and raise
alarms if required.
• An alarm will be raised if negative contact temperatures are measured as this
indicates electronic malfunction. After 3 counted negative contact temperatures in a
given time period, exchange of MStart is required.

mv_ContactTemperatures_Negative = TRUE
EF_COUNTER_MAX
EF_TIMER_MAX
OPC-group/-variable: MeasurementValues/ …
MNS Engineer: MeasurementValues/
68 1TGC910032M0201
Operation
4.6.1.13 MControl Supervision

Security packages are observing the electronic components in MControl (Hardware and
Software) and raise alarms and trips if required.
• An alarm will be raised if an internal Software error occurs.
• A trip will be raised if a configuration error occurs in the Software.
• If any Hardware problem occurs a trip is raised.
AM-Parameters: ae_others_Watchdog_IRF_HW_SW = TRUE

OPC-group/-variable: AlarmEvent/ IRFHardware
AlarmEvent/ IRFSoftware
4.6.1.14 MControl Location Supervision

If the MControl Hardware and the loaded functional modules are inserted in the wrong
location a trip is raised.

ae_maint_LocationSup = TRUE
OPC-group/-variable: AlarmEvent/ LocationSupervision
MNS Engineer: MControl Location Supervision
4.6.1.15 ‘Too many’ verification

Thermal overload alarm and trips as well as start limitation alarm and trips are counted
and referred to an observation period. In case of exceeded limits, additional information is
provided.

Tol_Counter_Max
Tol_Timer_Max
Start_Limitation_Counter_Max
Start_Limitation _Timer_Max
OPC-group/-variable: AlarmEvent/ TOL
AlarmEvent/ StartLimitation
MNS Engineer: Thermal Overload
1TGC910032M0201 69
Operation
Start Limitation
4.6.1.16 Cosphi Supervision

The history log of cosphi of the last hour is observed. It is verified and supervised if it
exceeds a limit longer than a given time period. If yes, a maintenance alarm will be raised.
2 functions are available:
• based on a cosphi maximum value of the last hour
• based on an cosphi average value of the last hour
Please, be aware that a time period setting of 1 hour leads to maximum 3 hours, as the
maximum and the average value of cosphi is built during the last hour.
These alarms are not available inside MNS iS, there is also no trip available or a
configuration inside MNavigate.

mv_cosphi_max = TRUE
COSPHI_ALARM_LEVEL
COSPHI_ALARM_TIMEDELAY
mv_cosphi_average = TRUE
COSPHI_ALARM_AV_LEVEL
COSPHI_ALARM_AV_TIME_DELAY = TRUE
OPC-group/-variable: MeasurementValues/ Cosphi
MNS Engineer: MeasurementValues/ Cosphi
4.6.1.17 Online Powerloss Supervision

This function is purely running inside 800xA and requires Cubicle Asset Monitor as well.
The history log of each phase current average value of the last hour is observed. With this
value the powerlosses of the MStart module is calculated and transferred as output record
to Cubicle Asset Monitor. Take care on correct parameter ‘opt_’ as these are influencing
the calculation method.
configuration inside MNavigate. It never leads directly to any trip of MStart.

RatedCurrent
Pv_Current_Dependent
70 1TGC910032M0201
Operation
Pv_Current_Independent
Pv_Diag_Powerloss_Calc = TRUE
DiversityFactor
Select the drive type with following ‘opt_”-parameters:
opt_NR_DOL = TRUE
opt_NR_DOL_HD = TRUE
opt_DOL_REV = TRUE
opt_2N_DOL = TRUE
opt_SD = TRUE
opt_Dahlander = TRUE
OPC-group/-variable: MeasurementValues/ IL1, IL2, IL3
MNS Engineer: MeasurementValues/ IL1, IL2, IL3
4.6.1.18 Time to Trip Supervision

This function is purely running inside 800xA
The diagnostic value ‘time to trip’ is supervised and in case it is lower than a given limit, a
maintenance alarm will be given.

TIME_TO_TRIP_EVENT = 14400
OPC-group/-variable: Diagnostics/ TimeToTrip
Thermal Overload
Diagnostics/ TimeToTrip
4.6.2 Protection functions

Alarm and trip-’handling’ is available from the Asset Monitor for following protection
functions.
With the Asset Monitor only observation of a system is provided, no control and
operation. Therefore, all resets required for these functions must be done via
MView or the PLC.
1TGC910032M0201 71
Operation
4.6.2.1 Thermal Overload

Thermal overload alarm and trips are standard protection functions. See standard
documentation.

ae_prot_ThermalOverload = TRUE
4.6.2.2 Start Limitation

Start Limitation alarm and trips are standard protection functions. See standard
documentation.

ae_ctrl_StartLimitation = TRUE
OPC-group/-variable: AlarmEvent/ StartLimitation
MNS Engineer: Start Limitation
4.6.2.3 Stall
Stall alarm and trips are standard protection functions. See standard documentation.

ae_prot_Stall = TRUE
OPC-group/-variable: AlarmEvent/ Stall
MNS Engineer: Stall
4.6.2.4 Underload / No load / Underload cosphi

Underload and No Load alarm and trips are standard protection functions and are
combined to one message in the Asset Monitor. For the protection functions see standard
documentation.

ae_prot_NoLoad_Underload = TRUE
OPC-group/-variable: AlarmEvent/ Underload
72 1TGC910032M0201
Operation
AlarmEvent/ NoLoad
MNS Engineer: No Load,
Underload
4.6.2.5 Underload cosphi

Underload cosphi alarm and trips are standard protection functions. See standard
documentation.

ae_prot_UnderloadCosPhi = TRUE
MNS Engineer: Underload
4.6.2.6 Residual current

Residual current alarm and trips are standard protection functions. See standard
documentation.

ae_prot_EarthLeakage = TRUE
OPC-group/-variable: AlarmEvent/ EarthLeakage
MNS Engineer: Earth Leakage
4.6.2.7 Residual current with external Relay

In some applications an external residual current relay is connected to function ‘External
Trip 2”. Alarm and trips are standard protection functions of ‘External Trip 2”. See standard
documentation.

ae_prot_EarthLeakage_externalTrip2 = TRUE
OPC-group/-variable: AlarmEvent/ ExternalTrip2
MNS Engineer: External Trip 2
1TGC910032M0201 73
Operation
4.6.2.8 PTC
PTC1 alarm and trips are standard protection functions. See standard documentation.

ae_prot_PTCSup = TRUE
OPC-group/-variable: AlarmEvent/ PTCsupervision
AlarmEvent/ PTCsupervisionOpenCircuit
AlarmEvent/ PTCsupervisionShortCircuit
MNS Engineer: PTC Supervision
4.6.2.9 Phase Unbalance / Phase loss / Fuse Supervision

Three different standard protection functions are combined to one message:
• Phase Unbalance, indicates phase unbalance through the phase currents,
unbalance between all 3 phases
• Phase Loss, indicates phase loss through the phase currents
• Fuse Supervision, indicates a tripped fuse in one phase
See standard documentation.

For fused short-circuit protection:
opt_fused = TRUE
ae_maint_FuseSup = TRUE
(for unfused both are FALSE)
ae_prot_PhaseLossUnbalance = TRUE
FuseSupervisionL1, FuseSupervisionL2,
FuseSupervisionL3
AlarmEvent/ PhaseFailure
AlarmEvent/ PhaseUnbalance
MNS Engineer: Fuse Supervision
Phase Loss
1
PTC: Positive Temperature Coefficient Sensor in the Motor. This sensor
indicates a too high temperature inside the motor. Usually more than one sensor is
installed inside the motor. Critical points are the ‘heads’ of the windings.
74 1TGC910032M0201
Operation
Phase Unbalance
4.6.2.10 Motor not running

Motor not running alarm and trips are standard protection functions. See standard
documentation. Basically, following conditions are observed and separately raised in an
alarm:
• If a motor is not at all connected or the safety switch is still open
• If a motor is not properly connected
• If all 3 fuses or the main-breaker tripped

RATEDVOLTAGE
Rated Votlage of MNS iS, given in [V]. Default is 400.
mv_RatedVoltage = TRUE
Voltage Measurement Values are available through
OPC.
OPC-group/-variable: AlarmEvent/ MotorNotRunning
MeasurementValues/ U12, U23, U31
4.6.2.11 Motor still running

Motor still running alarm and trips are standard protection functions. See standard
documentation.

none
OPC-group/-variable: AlarmEvent/ MotorStillRunning
1TGC910032M0201 75
Operation
4.6.2.12 Control Voltage Supervision

The Contactor Control Voltage 230V AC is observed. Control Voltage Supervision alarm
and trips are standard protection functions. See standard documentation.

ae_maint_ControlVoltageSup TRUE
OPC-group/-variable: AlarmEvent/ ControlVoltage
MNS Engineer: Control Voltage Supervision
4.6.2.13 Testmode Failure

If any phase current is detected in test position, this failure is indicated. Testmode failure
alarm and trips are standard protection functions. See standard documentation.

none
OPC-group/-variable: AlarmEvent/ TestModeFailure
4.6.2.14 Undervoltage
If undervoltage is detected, this failure is indicated. Failure alarm and trips are standard
protection functions. See standard documentation.

ae_prot_UnderVoltage = TRUE
OPC-group/-variable: AlarmEvent/ UnderVoltage
Under Voltage
4.6.3 General Purpose Functions
4.6.3.1 General Purpose Input

General Purpose Input 1 … 16 are possible to be used for condition monitoring,
maintenance issues.
As this is a customer specific function
76 1TGC910032M0201
Operation
• Severity,
• Description,
• Possible cause,
• Suggested action
might be defined by the customer. These definitions can be done in the ‘Config View’ of
the Asset Monitor – tab ‘conditions”.
When using National Language Support, the text fields for ‘Description”, ‘Possible
Cause’ and ‘Suggested Action’ must be modified in the relevant Excel-Sheet. See
therefore chapter ‘National language support’ in [7].
All other settings like ‘Severity’ must be modified within the ‘Config View’ of the
Asset Monitor described in this chapter.
When National Language Support is not used, all settings can be changed within
the ‘Config View”.

ae_others_ProgrammableLogicRegister TRUE
OPC-group/-variable: DeviceStatus/ GPI1, GPI2, … , GPI16
MNS Engineer: Programmable Logic Register
DIDO
4.6.3.2 External Trip

External Trip 1 and 2 are possible to be used for condition monitoring, maintenance or
other issues. See also 4.6.1.11 and 4.6.2.7.
• Severity,
• Description,
• Possible cause,
must be defined by the customer. These definitions can be done in the ‘Config View’ of
1TGC910032M0201 77
Operation

ae_others_ExternalTrip1 TRUE
External Trip 2
How to do these settings and how to edit parameters, see chapter 3.2.
78 1TGC910032M0201
Operation
4.7 MStart Maintenance Faceplate
4.7.1 Functionality
The faceplate is an additional functionality to operate the Asset Monitor in a smart way. It
enables easy overview of maintenance type and does not require MNS iS expert
knowhow. Furthermore it enables certain functions which are required inside 800xA for
MNS iS.
This faceplate is a pure Asset Monitor faceplate and is not used for operation and
control purposes.
The faceplate contains the name of the MStart object in the center top line and it contains
2 tabs ‘Asset Monitor’ and ‘Reset’ and several icons.
6 4
3
name 1 5
2
1TGC910032M0201 79
Operation
Depending on the chosen system option, up to seven different icons are selectable at
the top line.
1. Open ‘configuration view’ of Asset Monitor
2. Open Alarm list
3. Open Event list
4. Open Trend Display 1 with Operation Data
5. Open Trend Display 2 with Diagnostic Data
6. Open Log configuration
7. Open ‘main view’ of Asset Monitor
4.7.2 Graphic Display
Status information of MStart:

• Main-switch on/ off
• Test position on/ off
• Local operation on/ off
Status of Undervoltage Supervision
Single line diagram of MStart including

communication bus and MControl.
Herewith it is possible to see which main
component is affected:
• Switchgear communication
• MControl
• Internal communication
• MStart in total
• Main-switch
• Any of the contactors
• Sensor, main contact
• Motor and attached load or
machine
The main components will be coloured
acc. the highest severity of a present
condition.
It will be displayed if the motor has been
tripped or not.
Measurement values for maintenance

purposes:
• General Purpose Index
• External Trip
• Operating Cycles of Contactors
• Insertion Cycles
• Contact Temperatures
Pin / Unpin the Display • Operating Hours
• Measured Motor Start Time
• Thermal Image of the Motor
Version number of
• Asset Monitor logic
• Faceplate
80 1TGC910032M0201
Operation
As an example in the left picture the MStart is affected by a ‘failure’ with severity higher
than 750. In the right picture MStart is affected by an ‘out of specification’ issue with
severity between 251 and 500.
In order to verify details click on the right upper button to open the Asset Monitor.
Following pictures occur. Proceed with Asset Monitor operation like ‘condition details’ and
others.
1TGC910032M0201 81
Operation
4.7.3 Reset of Alarms

For following maintenance alarms the reset must be done in the faceplate – tab ‘reset”.
This is valid for:
• Too many Start Limitations Alarm and Trip
• Too many Thermal Overload Alarm and Trip
• Insertion Cycle Alarm
• New Module inserted
For both trips ‘too many start limitations’ and ‘too many thermal overloads’ the
single trip must be reset as well inside your PLC system or with MView.
The possible reset will be indicated with an activated and not grew colored ‘button”, in the
view below it is visible with black letters and white button. Click it after the performed
maintenance.
82 1TGC910032M0201
Operation
The click and reset of Insertion Cycle Alarm here will be notified in the system event
list as ‘maintenance successfully performed”! So it is assumed that maintenance
was properly done according the suggested action and MNS Service Manual.
If a MStart is inserted new, the relevant icon has to be clicked with mouse in order
to reset all maintenance functions which are referring to MStart values. If this will
not be done, these functions cause errors.
1TGC910032M0201 83
Operation
5 MFeed Asset Monitor
5.1 Conditions
• MControl, electrical
• MFeed, electrical
• Load, electrical
• Load, mechanical
• Operating Conditions
• General Purpose
• Supply side, electrical
All conditions give a first indication about the device involved (MControl, MFeed, Motor,
Supply side) and type of problem (electrical, mechanical) or a general information
(Operating Condition, General Purpose).

for ABB 800xA.
84 1TGC910032M0201
Operation
All relevant information is divided into 7 ‘conditions’ (2nd column to the left). The ‘severity’
of the condition is shown between 1 and 1000 (1000 most severe problem) in the 1st
column to the left. The column ‘sub-condition’ classifies together with severity the type of
problem. The following columns show the description of the problem, the timestamp (MNS
iS timestamp) and the quality status of the information (good = trust, bad = not valid).
For more information, see [6].

Normal
Load is available. Status is ‘normal”.
1 Asset functionality is fully available. No
General Purpose Input
As this is a customer specific function the severity
Failure as well as the condition details ‘description”,
2
‘possible cause’ and ‘suggested action’ might be
defined by the customer.
The logo will depend on selected severity.
Maintenance required Load is available. Status is ‘maintenance
(soon) required (soon)”.
100 Asset functionality fully available but maintenance
required soon to avoid functional restrictions, e.g.
caused by operating conditions.
Maintenance required Load is available. Status is ‘maintenance
(now) required (now)”.
250 Asset functionality fully available but maintenance
required now to avoid functional restrictions, e.g.
caused by operating conditions.
Out of Specification Load is still available. Status is ‘out of
specification”.
400
Out of Specification Load is still available. Status is ‘out of
specification”.
500
internal problems.
Load has been stopped. Operation is not
Function Check possible. Status is ‘function check”.
750
due to on-going work on the asset, e.g. as local
operation, maintenance (main-switch off),
simulation or a function check (test-position).
Load has been stopped. Status is ‘failure”.
900 Failure
Asset Functionality lost due to malfunction of its
1TGC910032M0201 85
Operation

peripherals or due to operating conditions.
Failure
Load has been stopped. Status is ‘failure”.
1000 Asset Functionality lost due to malfunction in the
asset itself.
5.4 Operation
The TimeStamp is taken directly from MNS iS.
If you modify settings, do not reduce the execution interval time below 60sec
5.5 Parameter
Default
# Specific limits
400 Rated voltage [V] of MNS iS in existing
RATED VOLTAGE (integer) system
105 Rated contact temperature in [°C]
CONTACT_TEMPERATURE_MAX (integer) Do not change!
Supervision period for all functions
8760 ‘operation supervision 1 and 2’ given in
MSTART_OPERATION_CHECK_MIN_TIME (integer) [hours]
Minimum limit of operating hours below
the function ‘operation supervision 1’ will
be active. Value will be referenced against
supervision period.
50 than parameter
OPERATING_HOURS_MIN (integer) SWITCH_CYCLES_K_MIN.
Absolute minimum limit of switch cycles for
all contactors below the function ‘operation
SWITCH_CYCLES_K_ABSMIN 1 (integer) Operation supervision for no switch cycles!
SWITCH_CYCLES_K_MIN 50 Minimum limit of switch cycles for all
86 1TGC910032M0201
Operation
Default
(integer) contactors below the function ‘operation
than parameter
OPERATING_HOURS_MIN.
10 start limitations’ will be active. Value will
START_LIMITATION_COUNTER_MAX integer) be referenced against supervision period.
START_LIMITATION_TIMER_MAX (integer) start limitations’ given in [hours]
10 thermal overloads’ will be active. Value will
TOL_COUNTER_MAX (integer) be referenced against supervision period.
TOL_TIMER_MAX (integer) thermal overloads’ given in [hours]
Maximum limit above function ‘Electronic
Failures’ will be active. Value will be
3 referenced against supervision period.
EF_COUNTER_MAX (integer) Do not change!
EF_TIMER_MAX Supervision period for function ‘Electronic
1344 Failures’ given in [hours].
(integer) Do not change!
TIME_TO_TRIP_EVENT Diagnostic-value ‘time to trip’ must drop
14400 below this level in order to activate
(integer) maintenance function, given in [seconds]
COSPHI_ALARM_LEVEL Maximum limit above function ‘cos ϕ
supervision (max. value of last hour)’ will
be active. This is the limit for supervision
0.9 of the maximum value of cos ϕ reached
(float) during the last hour.
COSPHI_ALARM_TIMEDELAY Supervision period for function ‘cos ϕ
supervision (max. value of last hour)”. The
cos ϕ value exceeded during this
COSPHI_ALARM_AV_LEVEL Maximum limit above function ‘cos ϕ
supervision (average value of last hour)’
will be active. This is the limit for
0.9 supervision of the average value of cos ϕ
(float) reached during the last hour.
COSPHI_ALARM_AV_TIMEDELAY Supervision period for function ‘cos ϕ
supervision (average value of last hour)”.
The cos ϕ value exceeded during this
# Configuration: Installed options
opt_fused TRUE MFeed has fused short-circuit protection
1TGC910032M0201 87
Operation
Default
opt_ContactorFeeder FALSE MFeed is a contactor feeder
opt_ED TRUE MFeed is an energy distribution feeder
opt_Transparent FALSE MFeed is transparent starter
# installed Alarms and Trips - Others
ae_others_Watchdog_IRF_HW_SW TRUE MControl with Watchdog function
ae_others_ProgrammableLogicRegister TRUE MControl with programmable logic register
ae_others_GPI_MSDV_valid MControl with function ‘MSDV supervision
FALSE of MFeed”
ae_others_GPI_MSDV 1 GPI-Register MSDV is connected to
(integer
1 .. 16)
ae_Others_GPI_MSDM_valid MControl with function ‘MSDM supervision
FALSE of MFeed”
ae_others_GPI_MSDM 2 GPI-Register MSDM is connected to
(integer
1 .. 16)
ae_others_ExternalTrip1_MSD_Alarm Any MSDM or MSDV is connected to
FALSE function ‘External Trip 1’ as Alarm
ae_others_ExternalTrip1_MSD_Trip Any MSDM or MSDV is connected to
FALSE function ‘External Trip 1’ as Trip
# installed Alarms and Trips –
Maintenance
ae_maint_OperatingHoursSup MControl with Operating Hours
TRUE Supervision for the motor
ae_maint_MStartSup TRUE MControl with MFeed Supervision
ae_maint_MStartInsertionCycleSup MControl with MFeed Insertion Cycle
TRUE Supervision
ae_maint_LocationSup TRUE MControl Location Supervision
ae_maint_ContactorSwitchCycleSup MControl with Contactor Switch Cycle
TRUE Supervision for all contactors
ae_maint_FuseSup MControl with Fuse Supervision. Attention:
TRUE Parameter ‘opt_fused’ must be TRUE!
ae_maint_ControlVoltageSup TRUE MControl with Control Voltage Supervision
ae_maint_ContactTempUnbalance MControl with Contact Temperature
TRUE Unbalance Supervision
ae_maint_ContactTempSup MControl with Contact Temperature
TRUE Supervision
# installed Alarms and Trips - Protection
ae_prot_Temperature2 Historical parameter.
FALSE Do not change!
88 1TGC910032M0201
Operation
Default
ae_prot_ThermalOverload TRUE MControl with Thermal overload protection
ae_prot_Stall TRUE MControl with Stall protection
ae_prot_PTCSup Motor equipped with PTC sensor,
MControl with PTC protection. Attention:
TRUE hardware required!
ae_prot_PhaseLossUnbalance MControl with Phase Loss, Phase
TRUE Unbalance protection
ae_prot_UnderloadCosPhi TRUE MControl with Underload cos φ protection
ae_prot_NoLoad_Underload MControl with No Load, Underload
TRUE protection
ae_prot_EarthLeakage TRUE MControl with Residual Current protection
Ae_prot_EarthLeakage_externalTrip2 MControl with external Residual Current
protection relay connected to function
FALSE ‘External Trip 2”
Ae_prot_UnderVoltage TRUE MControl with Under Voltage protection
# installed Alarms and Trips - Control
ae_ctrl_StartLimitation TRUE MControl with Start Limitation supervision
ae_ctrl_MainSwitchSup TRUE MControl with Main-switch supervision
ae_ctrl_ControlAccess TRUE MControl with Control Access supervision
# Measurement Values
mv_MStartInsertionCycle Measurement Value ‘MFeed Insertion
TRUE Cycles’ available through OPC
mv_ContactTemperatures Measurement Values ‘Contact
TRUE Temperatures’ available through OPC
mv_SwitchCycles Measurement Values ‘Switch Cycles Kx’
TRUE for all contactors available through OPC
mv_OperatingHours Measurement Value ‘Operating Hours’ for
TRUE the motor available through OPC
Mv_Rated Voltage Measurement Value ‘Rated Voltage’ for all
TRUE phases available through OPC
Mv_ContactTemperatures_Negative When TRUE, enable function ‘Supervision
TRUE of negative contact temperatures”
Mv_cosphi_max When TRUE, enables function ‘cos ϕ
FALSE supervision (max. value of last hour)”
Mv_cosphi_average When TRUE, enables function ‘cos ϕ
FALSE supervision (average value of last hour)”
# Powerloss Supervision
RatedCurrent 8.50 Rated Current of MFeed defined in MNS
(float) Engineer, given in [A]
Pv_Current_Dependent 3.09 Current Dependent Powerlosses of MFeed
(float) defined in MNS Engineer, given in [W]
Pv_Current_Independent 8.50 Current Independent Powerlosses of
1TGC910032M0201 89
Operation
Default
(float) MFeed defined in MNS Engineer, given in
[W]
Pv_Diag_Powerloss_Calc When TRUE, enable function ‘Online
FALSE Powerloss Calculation”
DiversityFactor 0.6 Diversity Factor of MFeed defined in MNS
(float) Engineer
5.6 Functionality
See also MNavigate help file.
• and which MControl/MFeed applications are related
5.6.1.1 Contact Temperature Monitoring

Available for outgoing contacts of MFeed. Alarm and Trip handling is based on the limit
values and time delay settings in MNavigate. Special issue is the Contact Temperature
Unbalance function for MFeed for low loaded MFeed. The difference between Maximum
and Minimum of Contact Temperatures is recognized.

ae_maint_ContactTempSup = TRUE
ae_maint_ContactTempUnbalance = TRUE
ContactTemperatureL1A, ContactTemperatureL2A,
ContactTemperatureL3A, ContactTemperatureL1B,
ContactTemperatureL2B, ContactTemperatureL3B,
AlarmEvent/ ContactTemperatureUnbalance
MNS Engineer: Contact Temperature Supervision
Contact Temperature Unbalance
Application: All MFeed
90 1TGC910032M0201
Operation
5.6.1.2 Insertion Cycles

Insertion cycles of MFeed are observed. Maintenance required every 100 cycles. Alarm
will be set. Small maintenance work until 500 cycles, higher effort maintenance work 600 –
1000, finally end of lifetime at 1000 cycles / exchange MFeed. Reset of alarms with
faceplate.

mv_MStartInsertionCycles = TRUE
ae_maint_MStart_InsertionCycleSup = TRUE
OPC-group/-variable: MeasurementValues/ InsertionCycles
MNS Engineer: MeasurementValues/ Insertion Cycles 2
Disable in MNavigate the Alarm for function ‘MFeed Insertion Cycles”. This
function is not used by the Asset Monitor and would lead to confusion.
5.6.1.3 Switch-cycles supervision for all contactors

The number of switch-cycles for all contactors is supervised. Available for all contactors of
MFeed as Contactor Feeders or Transparent. These applications are defined with
2
The MNavigate function for Alarm of ‘MStart Insertion Cycles’ is not used. When using Asset Monitors,
please disable this function in MNavigate
1TGC910032M0201 91
Operation
parameter ‘opt_’ specifying the drive-type (ContactorFeeder, Tranparent). Alarm handling

is based on the limit values and time delay settings in MNavigate.

ae_maint_ContactorSwitchCycleSup = TRUE
Select the feeder type with following ‘opt_”-parameters:
opt_ContactorFeeder (only K1) = TRUE
opt_Transparent (K1, K2, K3) = TRUE
SwitchCycleSupervisionK1, SwitchCycleSupervisionK2,
SwitchCycleSupervisionK3
MNS Engineer: Switch Cycle Supervision K1,
Application: All MFeed as ContactorFeeder and Transparent
5.6.1.4 Switch-operation supervision for all contactors

The proper switch-operation of all contactors is supervised. This function is available for all
contactors of MFeed as Contactor Feeders or Transparent. These applications are defined
with parameter ‘opt_’ specifying the feeder type (ContactorFeeder, Transparent). Alarm
and Trip handling is based on the standard functionality.

FeedbackSupervisionCfK1, FeedbackSupervisionCfK2,
FeedbackSupervisionCfK3
5.6.1.5 Welded contactor

A welded contactor will be recognized. Function is available for all contactors of MFeed as
Contactor Feeders or Transparent. These applications are defined with parameter ‘opt_’
specifying the feeder type (Contactor Feeder, Transparent). Trip handling is based on the
standard functionality.
92 1TGC910032M0201
Operation

OPC-group/-variable: AlarmEvent/ Welded
5.6.1.6 Operating hours supervision for load

The operating hours of the load is supervised. Alarm handling is based on the limit values
and time delay settings in MNavigate. Be aware that MFeed operating hours and load
operating hours are always the same with the first motor. If the load is changed, the
MFeed operating hours are much higher.

ae_maint_OperatingHoursSup = TRUE
OPC-group/-variable: AlarmEvent/ OperatingHours
MNS Engineer: Operating Hours

This function is available for all contactors of MFeed as Contactor Feeders or Transparent.
These applications are defined with parameter ‘opt_’ specifying the feeder type
(ContactorFeeder, Transparent).
Loads which are running with low switching cycles and low operating hours during the
observation period. Only if both conditions are fulfilled the alarm will be set.

Switch_Cycles_K_Min
Operating_Hours_Min
1TGC910032M0201 93
Operation

Application: Seldom used loads

This function is available for all contactors of MFeed as Contactor Feeders or Transparent.
These applications are defined with parameter ‘opt_’ specifying the feeder type
(ContactorFeeder, Transparent).
Loads which are never switched during the observation period.

Switch_Cycles_K_AbsMin
Application: Continuously running loads
5.6.1.9 Not ready for operation

If the MFeed is not ready for operation the Asset Monitor will indicate this. Criteria are
main-switch off, test position active or local control access.

ae_ctrl_MainSwitchSup = TRUE
ae_ctrl_ControlAccess = TRUE
94 1TGC910032M0201
Operation
OPC-group/-variable: AlarmEvent/ TestPositionActivated

MNS Engineer: Main Switch Supervision
Control Access
5.6.1.10 MFeed Supervision 1

Three different security packages are observing the electronic components in MFeed and
raise alarms and trips if required.
A trip will be raised if the MFeed Identnumber does not fit to the identnumber setting
in MControl.
A trip will be raised if the motor current setting downloaded from MNavigate does
not fit to the inserted MFeed
An alarm will be raised if communication is lost between MControl and MFeed while
motor is not running.
A trip will be raised if communication is lost between MControl and MFeed while
motor is running.
An alarm will be raised if there is a risk that the communication will be lost soon due
too high internal temperatures and a trip will be raised if communication is lost
inside the MFeed due to too high internal temperatures.

ae_maint_MStartSup = TRUE
ae_prot_Temperature2
CONTACT_TEMPERATURE_MAX
OPC-group/-variable: AlarmEvent/ PowerModuleSupervision
AlarmEvent/ PowerModuleSupervision1
AlarmEvent/ TestPositionActivated
MNS Engineer: MFeedt Type Supervision
1TGC910032M0201 95
Operation
5.6.1.11 MFeed Supervision 2 (MSDM, MSDV and External Trip)

There is one additional security package observing the electronic components in MFeed
and raise alarms and trips if required.
An alarm will be raised if MSDM and/ or MSDV detection is active and linked to
GPI-registers. This is a method to differentiate between MSDM and MSDV. GPI-
registers are preset with default 1 (MSDV) and 2 (MSDM) but can be changed with
parameters.
MSDM and MSDV can also be connected as an alternative to External Trip 1 as an
alarm or a trip depending on application inside MControl. This required function
‘External Trip 1”. In this case it can be not be differentiated between MSDM and
MSDV.

ae_others_GPI_MSDV_valid = TRUE
ae_others_GPI_MSDV
ae_others_GPI_MSDM_valid = TRUE
ae_others_GPI_MSDM
ae_others_ExternalTrip1_MSD_Alarm = TRUE
ae_others_ExternalTrip1_MSD_Trip = TRUE
OPC-group/-variable: DeviceStatus / GPI
External Trip 1
5.6.1.12 MFeed Supervision 3

Additional security package is observing the electronic components in MFeed and raise
alarms if required.
An alarm will be raised if negative contact temperatures are measured as this
indicates electronic malfunction. After 3 counted negative contact temperatures in a
given time period, exchange of MFeed is required.

mv_ContactTemperatures_Negative = TRUE
EF_COUNTER_MAX
EF_TIMER_MAX
96 1TGC910032M0201
Operation
ae_prot_Temperature2
OPC-group/-variable: MeasurementValues/ …
MNS Engineer: MeasurementValues/
5.6.1.13 MControl Supervision

Security packages are observing the electronic components in MControl (Hardware and
Software) and raise alarms and trips if required.
An alarm will be raised if an internal Software error occurs.
A trip will be raised if a configuration error occurs in the Software.
If any Hardware problem occurs a trip is raised.
AM-Parameters: ae_others_Watchdog_IRF_HW_SW = TRUE

OPC-group/-variable: AlarmEvent/ IRFHardware
AlarmEvent/ IRFSoftware
5.6.1.14 MControl Location Supervision

If the MControl Hardware and the loaded functional modules are inserted in the wrong
location a trip is raised.

ae_maint_LocationSup = TRUE
OPC-group/-variable: AlarmEvent/ LocationSupervision
MNS Engineer: MControl Location Supervision
5.6.1.15 ‘Too many’ verification

1TGC910032M0201 97
Operation
Thermal overload alarm and trips as well as start limitation alarm and trips are counted
and referred to an observation period. In case of exceeded limits, additional information is
provided.

Tol_Counter_Max
Tol_Timer_Max
Start_Limitation_Counter_Max
Start_Limitation _Timer_Max
AlarmEvent/ StartLimitation
Start Limitation
Application: MFeed as Transparent
5.6.1.16 Cosphi Supervision

The history log of cosphi of the last hour is observed. It is verified and supervised if it
exceeds a limit longer than a given time period. If yes, a maintenance alarm will be raised.
2 functions are available:
• based on a cosphi maximum value of the last hour
• based on an cosphi average value of the last hour
Please, be aware that a time period setting of 1 hour leads to maximum 3 hours, as the
maximum and the average value of cosphi is built during the last hour.
configuration inside MNavigate.

mv_cosphi_max = TRUE
COSPHI_ALARM_LEVEL
COSPHI_ALARM_TIMEDELAY
mv_cosphi_average = TRUE
COSPHI_ALARM_AV_LEVEL
COSPHI_ALARM_AV_TIME_DELAY = TRUE
OPC-group/-variable: MeasurementValues/ Cosphi
MNS Engineer: MeasurementValues/ Cosphi
Application: MFeed as Contactor Feeder and Transparent
98 1TGC910032M0201
Operation

This function is purely running inside 800xA and requires Cubicle Asset Monitor as well.
The history log of each phase current average value of the last hour is observed. With this
value the powerlosses of the MFeed module is calculated and transferred as output record
to Cubicle Asset Monitor. Take care on correct parameter ‘opt_’ as these are influencing
the calculation method.
configuration inside MNavigate. It never leads directly to any trip of MFeed.

RatedCurrent
Pv_Current_Dependent
Pv_Current_Independent
Pv_Diag_Powerloss_Calc = TRUE
DiversityFactor
opt_ContactorFeeder = TRUE
opt_ED = TRUE
opt_Transparent = TRUE
OPC-group/-variable: MeasurementValues/ IL1, IL2, IL3
MNS Engineer: MeasurementValues/ IL1, IL2, IL3
5.6.1.18 Time to Trip Supervision

This function is purely running inside 800xA
The diagnostic value ‘time to trip’ is supervised and in case it is lower than a given limit, a
maintenance alarm will be given.

TIME_TO_TRIP_EVENT = 14400
OPC-group/-variable: Diagnostics/ TimeToTrip
Thermal Overload
Diagnostics/ TimeToTrip
1TGC910032M0201 99
Operation
5.6.2 Protection functions

Alarm and trip-’handling’ is available from the Asset Monitor for following protection
functions.
With the Asset Monitor only observation of a system is provided, no control and
operation. Therefore, all resets required for these functions must be done via
MView or the PLC.
5.6.2.1 Thermal Overload

Thermal overload alarm and trips are standard protection functions. See standard
documentation.

ae_prot_ThermalOverload = TRUE
5.6.2.2 Start Limitation

Start Limitation alarm and trips are standard protection functions. See standard
documentation.

ae_ctrl_StartLimitation = TRUE
OPC-group/-variable: AlarmEvent/ StartLimitation
MNS Engineer: Start Limitation
Application: MFeed as Contactor Feeder or Transparent
5.6.2.3 Stall
Stall alarm and trips are standard protection functions. See standard documentation.

ae_prot_Stall = TRUE
OPC-group/-variable: AlarmEvent/ Stall
MNS Engineer: Stall
100 1TGC910032M0201
Operation
5.6.2.4 Underload / No load / Underload cosphi

Underload and No Load alarm and trips are standard protection functions and are
combined to one message in the Asset Monitor. For the protection functions see standard
documentation.

ae_prot_NoLoad_Underload = TRUE
AlarmEvent/ NoLoad
MNS Engineer: No Load,
Underload
5.6.2.5 Underload cosphi

Underload cosphi alarm and trips are standard protection functions. See standard
documentation.

ae_prot_UnderloadCosPhi = TRUE
MNS Engineer: Underload
Application: MFeed as Contactor Feeder and Transparent
5.6.2.6 Residual current

Residual current alarm and trips are standard protection functions. See standard
documentation.

ae_prot_EarthLeakage = TRUE
OPC-group/-variable: AlarmEvent/ EarthLeakage
MNS Engineer: Earth Leakage
5.6.2.7 Residual current with external Relay

In some applications an external residual current relay is connected to function ‘External
Trip 2”. Alarm and trips are standard protection functions of ‘External Trip 2”. See standard
documentation.
1TGC910032M0201 101
Operation

ae_prot_EarthLeakage_externalTrip2 = TRUE
5.6.2.8 PTC
PTC3 alarm and trips are standard protection functions. See standard documentation.

ae_prot_PTCSup = TRUE
OPC-group/-variable: AlarmEvent/ PTCsupervision
AlarmEvent/ PTCsupervisionOpenCircuit
AlarmEvent/ PTCsupervisionShortCircuit
MNS Engineer: PTC Supervision
5.6.2.9 Phase Unbalance / Phase loss / Fuse Supervision

Three different standard protection functions are combined to one message:
• Phase Unbalance, indicates phase unbalance through the phase currents,
unbalance between all 3 phases
• Phase Loss, indicates phase loss through the phase currents
• Fuse Supervision, indicates a tripped fuse in one phase
See standard documentation.

opt_fused = TRUE
ae_maint_FuseSup = TRUE
(for unfused both are FALSE)
ae_prot_PhaseLossUnbalance = TRUE
3
PTC: Positive Temperature Coefficient Sensor in the Motor. This sensor indicates a too high temperature
inside the motor. Usually more than one sensor is installed inside the motor. Critical points are the ‘heads’ of
the windings.
102 1TGC910032M0201
Operation
FuseSupervisionL1, FuseSupervisionL2,
FuseSupervisionL3
AlarmEvent/ PhaseFailure
AlarmEvent/ PhaseUnbalance
MNS Engineer: Fuse Supervision
Phase Loss
Phase Unbalance
5.6.2.10 Load not running

Load not running alarm and trips are standard protection functions. See standard
documentation. Basically, following conditions are observed and separately raised in an
alarm:
• If a motor is not at all connected or the safety switch is still open
• If a motor is not properly connected
• If all 3 fuses or the main-breaker tripped

RATEDVOLTAGE
mv_RatedVoltage = TRUE
OPC-group/-variable: AlarmEvent/ MotorNotRunning
5.6.2.11 Load still running

Load still running alarm and trips are standard protection functions. See standard
documentation.

none
OPC-group/-variable: AlarmEvent/ MotorStillRunning
1TGC910032M0201 103
Operation
Application: All MFeed as Contactor Feeder or Transparent
5.6.2.12 Control Voltage Supervision

The Contactor Control Voltage 230V AC is observed. Control Voltage Supervision alarm
and trips are standard protection functions. See standard documentation.

ae_maint_ControlVoltageSup TRUE
opt_ContactorFeeder = TRUE
opt_Transparent = TRUE
OPC-group/-variable: AlarmEvent/ ControlVoltage
MNS Engineer: Control Voltage Supervision
5.6.2.13 Testmode Failure

If any phase current is detected in test position, this failure is indicated. Testmode failure
alarm and trips are standard protection functions. See standard documentation.

none
OPC-group/-variable: AlarmEvent/ TestModeFailure
5.6.2.14 Undervoltage
If undervoltage is detected, this failure is indicated. Failure alarm and trips are standard
protection functions. See standard documentation.

ae_prot_UnderVoltage = TRUE
OPC-group/-variable: AlarmEvent/ UnderVoltage
Under Voltage
104 1TGC910032M0201
Operation
5.6.3 General Purpose Functions
5.6.3.1 General Purpose Input

General Purpose Input 1 … 16 are possible to be used for condition monitoring,
maintenance issues.
• Severity,
• Description,
• Possible cause,
might be defined by the customer. These definitions can be done in the ‘Config View’ of

ae_others_ProgrammableLogicRegister TRUE
OPC-group/-variable: DeviceStatus/ GPI1, GPI2, … , GPI16
MNS Engineer: Programmable Logic Register
DIDO
5.6.3.2 External Trip

External Trip 1 and 2 are possible to be used for condition monitoring, maintenance or
other issues. See also 5.6.1.11 and 5.6.2.7.
• Severity,
• Description,
• Possible cause,
must be defined by the customer. These definitions can be done in the ‘Config View’ of
1TGC910032M0201 105
Operation

External Trip 2
How to do these settings and how to edit parameters, see chapter 3.2.
106 1TGC910032M0201
Operation
5.7 MFeed Maintenance Faceplate
5.7.1 Functionality
The faceplate is an additional functionality to operate the Asset Monitor in a smart way. It
enables easy overview of maintenance type and does not require MNS iS expert
knowhow. Furthermore it enables certain functions which are required inside 800xA for
MNS iS.
This faceplate is a pure Asset Monitor faceplate and is not used for operation and
control purposes.
The faceplate contains the name of the MFeed object in the center top line and it contains
2 tabs ‘Asset Monitor’ and ‘Reset’ and several icons.
6
4
3
name
1 5
2
1TGC910032M0201 107
Operation
Seven different icons are selectable at the top line.

1. Open ‘configuration view’ of Asset Monitor
2. Open Alarm list
3. Open Event list
4. Open Trend Display 1 with Operation Data
5. Open Trend Display 2 with Diagnostic Data
6. Open Log configuration
7. Open ‘main view’ of Asset Monitor
If parameter ‘opt_ED’ is TRUE for energy distribution feeder, the faceplate is changed and
the contactor is replaced by a straight line. All other functions are un-changed.
108 1TGC910032M0201
Operation
5.7.2 Graphic Display

Status information of MFeed:
• Main-switch on/ off
• Test position on/ off
• Local operation on/ off
Status of Undervoltage Supervision
Single line diagram of MFeed including

communication bus and MControl.
Herewith it is possible to see which main
component is affected:
• Switchgear communication
• MControl
• Internal communication
• MFeed in total
• Main-switch
• Any of the contactors
• Sensor, main contact
• Motor and attached load or
machine
The main components will be coloured
acc. the highest severity of a present
condition.
It will be displayed if the motor has been
tripped or not.
Measurement values for maintenance

purposes:
• General Purpose Index
• External Trip
• Operating Cycles of Contactors
• Insertion Cycles
• Contact Temperatures
• Operating Hours
• Measured Motor Start Time
• Thermal Image of the Motor
Pin / Unpin the Display
Version number of
• Asset Monitor logic
• Faceplate
1TGC910032M0201 109
Operation
As an example in the left picture the MFeed is affected by a ‘failure’ with severity higher
than 750. In the right picture MFeed is affected by an ‘out of specification’ issue with
severity between 251 and 500.
In order to verify details click on the right upper button to open the Asset Monitor.
Following pictures occur. Proceed with Asset Monitor operation like ‘condition details’ and
others.
110 1TGC910032M0201
Operation
5.7.3 Reset of Alarms

For following maintenance alarms the reset must be done in the faceplate – tab ‘reset”.
This is valid for:
• Too many Start Limitations Alarm and Trip
• Too many Thermal Overload Alarm and Trip
• Insertion Cycle Alarm
• New Module inserted
For both trips ‘too many start limitations’ and ‘too many thermal overloads’ the trip
must be reset as well inside your PLC system or with MView.
The possible reset will be indicated with an activated and not grew colored ‘button”, in the
view below it is visible with black letters and white button. Click it after the performed
maintenance.
1TGC910032M0201 111
Operation
The click and reset of Insertion Cycle Alarm here will be notified in the system event
list as ‘maintenance successfully performed”! So it is assumed that maintenance
was properly done according the suggested action and MNS Service Manual.
If a MFeed is inserted new, the relevant icon has to be clicked with mouse in order
to reset all maintenance functions which are referring to MFeed values. If this will
not be done, these functions cause errors.
112 1TGC910032M0201
Operation
6 MLink Asset Monitor

The MLink AssetMonitor is used to supervise the correct function of the MLink in its role as
the central communication device for its cubicles.
To reflect the different configuration in redundant MLink installations, the MLink
AssetMonitor comes in three flavours:
• MLink_AM, used for non-redundant Mlinks
• MLink_primary, supervising the Primary of two redundant Mlinks
• MLink_backup, supervising the Backup of two redundant Mlinks
They show the same behaviour, but are differently preconfigured.
6.1 Conditions
• MLink, electrical
• DCS Communication
• Switchgearbus, other
• MNavigate Server, other
• Redundancy, other
• MLink Supervision, other

for ABB 800xA.
All relevant information is fed into the 6 ‘conditions’ (2nd column to the left). The ‘severity’ of
the condition is shown between 1 and 1000 (1000 most severe problem) in the 1st column
to the left. The column ‘sub-condition’ classifies together with severity the type of problem.
The remaining columns show the description of the problem, the timestamp (MNS iS
timestamp) and the quality status of the information (good = trust, bad = not valid).
1TGC910032M0201 113
Operation
For more background information, see [6].

The MLink Asset monitor uses the following severities:
Normal MLink is available.
Status is ‘normal”.
1
Asset functionality is fully available. No
Maintenance required
(soon) MLink is available.
Status is ‘maintenance required (soon)”.
100
required soon to avoid functional restrictions.
Maintenance required
(now) MLink is available.
Status is ‘maintenance required (now)”.
250
required now to avoid functional restrictions.
Out of Specification MLink is still available.

Status is ‘out of specification”.
500
MLink or essential applications are not yet
Function Check operational.
Operation is not possible.
750
Status is ‘function check”.
e.g. due to on-going start-up.
MLink or essential applications are not
Failure operational.
Operation is not possible.
1000
Status is ‘failure”.
Asset Functionality lost due to malfunction in the
asset itself.
6.4 Operation
The Timestamp is taken directly from MNS iS.
The MLink Asset Monitor uses the triggered execution approach. This new functionality in
the 800XA Asset optimizer environment allows for execution of the Asset Monitor based
on changes in the input data. The logic is executed each time the input records with the
‘trigger execution’ flag change their values.
114 1TGC910032M0201
Operation
Therefore the setting ‘execution cycle time’ is set to 60000s to run the logic at least each
16.6h. It is not necessary to reduce this value.
6.5 Parameter
Default
# Specific values
DCS_COMM_ERR_MAX 2 DCS Communication Counter Limit Values
DCS Communication Counter Observation
DCS_COMM_TIMER_MAX 60 Time Setting [minutes]
#Application
Is the status information inside OPC
StatusInformation True server available?
Redundancy False/True Is this a redundant application
6.6 Functionality
All MLink AssetMonitor functions have the following dependencies:
AM Parameters: (definitions see 6.5)
Default_Language, ref [7], sec ‘NLS”
InhibitValue, ref XXX
Redundancy
OPC-group/-variable: MLinkData.Primary.StatusValue
MLinkData.Primary.IPAddressLan2
1TGC910032M0201 115
Operation
MLinkData.Backup.StatusValue (only redundant MLink)

MLinkData.Backup.IPAdressLan2 (only redundant MLink)
MNS Engineer: Nothing specific related to AM functions
Application: Nothing specific related to AM functions
6.6.1.1 Condition MLink, electrical

This condition assesses certain operational condition of the related MLink
• CPU temperature supervision
The MLinkSupervision application running on the MLink itself has two different
states related to the temperature measurements on the MLink CPU
o #1.1 Temperature high, Severity 250, maintenance required (now)
o #1.2 Temperature critical, Severity 500, out of specification

The temperature limits are product specific and not changeable by the user.
• #1.3 Application start-up supervision, severity 750, Function Check

During start-up of the MLink this sub condition may be active, when some of the
supervised applications (see below) did not yet report normal state.
• Problems with the Ethernet Connection between OPC server and MLink
If there is some issue with the connectivity, one of two conditions may be raised
o #1.4 Ethernet communication is completely lost,

Severity 1000, Failure
Communication to the MLink is completely lost.
o #1.5 Ethernet comm. not properly established,

Severity 1, Failure
Some configuration problem is detected, which prevents complete
transmission MLink status information
6.6.1.2 DCS Communication

This condition reacts on certain problems on the communication between MLink and the
process control system via a fieldbus connection.
• Errors based on hardware failure such as Profibus card error or broken cables are
indicated.
o #2.1 Fatal error for Profibus, Severity 1000, failure
116 1TGC910032M0201
Operation
o #2.3 Too many DCS errors

Severity 250, Maintenance required (now)
This sub condition is raised, when more than DCS_COMM_ERROR_MAX
within the DCS_COMM_TIMER_MAX time period occurred.
o #2.4 DCS communication error due to broken cable,

Severity 100, maintenance requirement (soon)
• Errors due to a missing configuration file is indicated
o #2.2 Fatal error for application, Severity 1000, failure
6.6.1.3 Switchgearbus
This condition signals issues concerning the communication within the switchgear between
MLink and the MControls
• #3.1 Fatal error in application, e.g. due to broken cable in the 10Base-I link
• #3.2 MLink does not receive any responses,

Severity 100, Maintenance required (soon)
6.6.1.4 MNavigate Server

This application enables the download of configuration and parameter data from the
MNavigate PC to the switchgear.
• #4.1 Fatal error in application, Severity 1000, Failure
6.6.1.5 Redundancy
This condition shows the role and activity for the related MLink in its ‘normal’ sub-
condition:
• #5.0 The message indicates,

o if the MLink is configured as redundant or non-redundant MLink,
o if its start-up role is primary or backup
o and if its current state is active or inactive
o and its IP Address on the switchgear network (Lan2)
The redundancy application has a couple of error states reported in this condition:
• #5.1 Redundancy not running, even if enabled; Severity 1000, Failure
• #5.2 General Software error, Severity 1000, Failure
1TGC910032M0201 117
Operation
• #5.3 Redundant MLink is not alive,

Severity 250, Maintenance required (soon)
• #5.4 Parameter Files error, Severity 1000, Failure
• #5.5 MLink configuration mismatch, Severity 1000, Failure
• #5.6 MControl file mismatch, Severity 1000, Failure
• #5.7 MLink lost switchgear communication,

6.6.1.6 MLink Supervision

The Mlink Supervision application supervises all other applications and signals certain
errors into this condition
• #6.1 CPU Temperature supervision is running but not working properly,

• #6.2 MLink supervision application itself is not working

• #6.3 Parameter File missing, Severity 1000, failure
• #6.4 Data map missing,

• #6.5 CPU temperature supervision is not running

• #6.6 Generic failure of an Software application

118 1TGC910032M0201
Operation
7 Cubicle Asset Monitor

The Cubicle Asset Monitor is located in the 800xA Location Structure. This is
essential for its function as this is the only structure where the correlation between
MStart, MFeed and its cubicle is organized.
The Cubicle Asset Monitor must be also inserted from Location Structure into
Control Structure, but this has only Asset Optimization Server reasons. The function
is only running in Location Structure.
7.1 Conditions
Following condition is used in the Asset Monitor:
• Cubicle, electrical
All conditions give a first indication about the device involved (i.e. Cubicle) and type of
problem (i.e. electrical).

for ABB 800xA.
All relevant information is divided into 1 ‘condition’ (2nd column to the left). The ‘severity’ of
the condition is shown between 1 and 1000 (1000 most severe problem) in the 1st column
to the left. The column ‘sub-condition’ classifies together with severity the type of problem.
The following columns show the description of the problem, the timestamp (AO server
time) and the quality status of the information (good = trust, bad = not valid).
For more information, see [6].
1TGC910032M0201 119
Operation

Normal
Cubicle is available. Status is ‘normal”.
1 Asset functionality is fully available. No
Out of Specification Cubicle is still available. Status is ‘out of
specification”.
300
specification”.
400 Asset functionality available but decreased due to
operating conditions outside the specified limits
and due to internal problems.
specification”.
500 Asset functionality available but decreased due to
operating conditions outside the specified limits
and due to increased internal problems.
No condition of the cubicle asset monitor will cause a trip of a MStart or MFeed.
Those are only tripped by own protection functions.
7.4 Operation
The TimeStamp is taken directly from 800xA AO server PC.
7.5 Parameter
Default
# Specific limits
30 Protection class of MNS iS acc. MNS
pv_IP_Switchgear (integer) Engineer as IP-rating acc. IEC 60529
35 Ambient temperature in [°C] of MNS iS
pv_AmbientTemp_Switchgear (integer) acc. MNS Engineer
0 Offset Powerlosses of this MNS iS cubicle
pv_Offset_Powerlosses (integer) acc. MNS Engineer of devices not
120 1TGC910032M0201
Operation
Default
incorporated in MNS iS communication
like i.e. Slimline, RPC-units or non-
communicating Circuitbreakers
Maximum allowed Powerlosses of this
MNS iS cubicle acc. MNS Engineer as
550 limit for the function ‘online powerloss
pv_Max_Powerlosses (integer) supervision”
Enables function ‘online powerloss
pv_Diag_Powerloss_Calc FALSE supervision’ if TRUE.
7.6 Functionality
• and which MControl/MStart applications are related

This function is only available with a working location structure.
The MStart and MFeed Asset Monitor is calculating with the average phase current of L1 –
L3 of the last complete hour the online powerlosses (current dependent and current
independent). The Cubicle Asset Monitor is collecting all those powerlosses which are
located in his cubicle and with all summed-up and compare it to the maximum allowed
power losses acc. MNS iS engineering rules.
Temperature problems like i.e. contact temperature alarm in MStart and MFeed are
influencing the severity, possible cause and suggested action of the message.
This function will never lead to trips of single MStart or MFeed! All trips are caused
by protection functions of relevant MStart or MFeed.
AM-Parameter: (definition see 7.5)

pv_IP_Switchgear
Protection class of MNS iS acc. MNS Engineer as IP-
rating acc. IEC 60529, default is IP30.
pv_AmbientTemp_Switchgear
1TGC910032M0201 121
Operation
Ambient temperature in [°C] of MNS iS acc. MNS

Engineer, default is 35°C.
pv_Offset_Powerlosses
Offset Powerlosses in [W] of this MNS iS cubicle acc.
MNS Engineer of devices not incorporated in MNS iS
communication like i.e. Slimline, RPC-units or non-
communicating Circuitbreakers, default is 0W.
pv_Max_Powerlosses
Maximum allowed Powerlosses in [W] of this MNS iS
cubicle acc. MNS Engineer as limit for this, default is
550W
pv_Diag_Powerloss_Calc = TRUE
OPC-group/-variable: for all MStart and MFeed:
MeasurementValues/ IL1, IL2, IL3
MNS Engineer: for all MStart and MFeed:
MeasurementValues/ IL1, IL2, IL3
Application: All Cubicles, all MFeed and MStart
122 1TGC910032M0201
Operation
8 Related and used 800xA Functionality

This section describes some functions of the System 880xA, which are used to provide
additional information about the MNS iS Objects. This allows e.g. for digging into the
history of operational and diagnostic data as well as handling the alarm and event lists.
8.1 Trend Display

In order to view and verify measured values of operational data, trend display aspects are
used. Navigate to the faceplate aspect of an object. Click on below marked icon.
Most important functions are described herein, see also [5].
A separate window will open, zoom it to full screen size with normal windows operation.
1TGC910032M0201 123
Operation
See below a description of the elements of the toolbar.
124 1TGC910032M0201
Operation
Define ruler type:

• ‘|’ – standard ruler, values
will be displayed at
location
• ‘||’ marked timeline will be
zoomed in
• ‘_’ – standard rule, values
will be displayed at
location
• ‘=‘ marked valueline will be
zoomed in
• ‘ ‘ marked area will be
Zoom out timeline of window
zoomed in, timeline and
valueline
Zoom in timeline of window
Help and documentation
Move window to the right
Move window to the left
Move ruler down
Move ruler up
Move ruler to the right
Move ruler to the left
Block / Unblock
Hide/Show table
Reset the template
Cancel changes
Save your settings
1TGC910032M0201 125
Operation
Example:
‘Ruler – zoom in timeline’
126 1TGC910032M0201
Operation
‘Ruler – zoom in valueline’
1TGC910032M0201 127
Operation
Those two operations result in:
This can be repeated until the desired portion of the trend is shown.
128 1TGC910032M0201
Operation
In order to view and verify measured values of diagnostic data, trend display aspects are
used. Navigate to the faceplate aspect of an object. Click on below marked icon.
1TGC910032M0201 129
Operation
A separate window will open, zoom it to full screen size with normal windows operation.
Use same functions as described above.
130 1TGC910032M0201
Operation
8.2 History Log

Historical data are stored in log configuration aspects. Navigate to the faceplate aspect of
an object. Click on below marked icon. Now access to historical data is possible.
1TGC910032M0201 131
Operation
A separate window will open.
Log is enabled
Navigate to the value to be accessed
Server node name of basic history log of 800xA and

‘green’ log ok, ‘red’ log not ok.
132 1TGC910032M0201
Operation
Navigate to value to be accessed.
1TGC910032M0201 133
Operation
Open the log configuration by ‘click’ on ‘+’.
134 1TGC910032M0201
Operation
‘Click’ on log configuration, tab ‘log definition’ will open to get access to general log
definition data.
1TGC910032M0201 135
Operation
‘Click’ on next tab with name ‘data collection’ to get access to the general data of the log
template.
136 1TGC910032M0201
Operation
‘Click’ on next tab with name ‘presentation’ to get access to the value presentation.
1TGC910032M0201 137
Operation
‘Click’ on next tab with name ‘status’ to get access to the stored data.
To get access to the last 1000 stored values, click on ‘read”, values will be displayed. If
other values are to be displayed, click on ‘settings”.
138 1TGC910032M0201
Operation
Change ‘number of points’ and ‘time frame’ values acc. to your needs.
Click ‘ok’ if your finished the settings.
1TGC910032M0201 139
Operation
Click now on ‘Read’ to display the values.
140 1TGC910032M0201
Operation
Click on ‘Action’ to open menu, to export the data, select ‘Export Data to file’.
1TGC910032M0201 141
Operation
New window will open, click ‘next’.
Select ‘Browse’ fort the filename.
142 1TGC910032M0201
Operation
After selecting the filename and its location, click ‘Save’.
Click ‘Finish’ to finalize the export.
1TGC910032M0201 143
Operation
144 1TGC910032M0201
Operation
Return to aspect ‘log configuration’ automatically. Close it.
1TGC910032M0201 145
Operation
Open MS Excel and load the exported *.csv file.
Continue your work.
146 1TGC910032M0201
Operation
8.3 Alarm- and Eventlist

To access the alarm lists navigate to the faceplate aspect of an object. Click on below
marked icon.
1TGC910032M0201 147
Operation
A separate window will open with alarm lists.
To navigate further on, click on the respective line where more information is required and
right mouse click. A menu will open where you are able to select several aspects like
‘Asset Monitor”, ‘Faceplate”, etc. Select by left mouse click.
To access the event list navigate to the faceplate aspect of an object. Click on below
marked icon.
148 1TGC910032M0201
Operation
1TGC910032M0201 149
Operation
A separate window will open with event lists.
To navigate further on, click on the respective line where more information is required and
right mouse click. A menu will open where you are able to select several aspects like
‘Asset Monitor”, ‘Faceplate”, etc. Select by left mouse click.
150 1TGC910032M0201
Operation
8.4 Different Structures

A central part of the object philosophy is the possibility to organize the same object
representing e.g. a starter in several structures following different organizational criteria.
Within MNS iS Condition Monitoring the following structure are used:
• Control Structure
This organizes the objects in the communication hierarchy: The OPC server object
has all connected MLinks as children, which have the configured MStart or MFeed
objects as children
• Location Structure
Here the location organization is used: Switchgear Room  Switchgear  Cubicle
 MStart/MFeed
(MLinks are currently not included in the Location Structure)
• Asset Structure
This Structure organizes the devices along their function, which is denoted by their
Starter Type and their Firmware-ID.
• Documentation Structure
Here only one central object is placed, representing the MNS iS system and holding
links to all needed documentation pdf files.
The Maintenance Workplace allows for switching between these structures. See the
following picture.
Alternatively it is always possible to use the context menu of an object via right mouse
click to access the available structure aspects to navigate to other views. This is useful if
you detect a problem with an Starter and need to know quickly, where this starter is
located.
1TGC910032M0201 151
Operation
Select different structures
Active instance
Available Aspects,
active one is selected
Content/ function of
active Aspect
152 1TGC910032M0201
Operation
8.5 Control Connection

In order to see actual and active values, navigate to the aspect ‘control connection’ of any
object.
This is also useful to debug the communication in case of missing values in the
maintenance display or in the asset monitor.
1TGC910032M0201 153
Operation
Double-click on the aspect opens it in an own window.
154 1TGC910032M0201
Operation
Activate at the bottom left ‘Subscribe to live data’ in order to see the actual data. In the first
line you see the titles of the column. All required data are displayed. Scroll down if you
want see other values.
1TGC910032M0201 155
Operation
9 Error Correction
This section describes commonly known problems, which in many cases are caused by
some misconfiguration such as missing licenses.
9.1 Basic error procedure

In case of any error with Asset Monitors it is important to check first, if MNS iS works
proper.
So, please check before any further action following points:

1. Go to relevant MView and check:
• Is the relevant MStart or MFeed online?
• Is the relevant MStart or MFeed communicating (actual and changing measuring
values, is on and off working proper)?
• Are any alarms or trips valid for the relevant MStart or MFeed?
2. Go to the relevant 800xA Connectivity Server and check:

• Is the MNS iS OPC Server Software running proper (Task Manager, Software-
Window, Manual)?
• Check the availability of all MLinks and MStart or MFeed with an OPC Client
(see section 9.1.1 ‘ABB 800xA OPC Client‘ or 9.1.2 ‘Softing OPC Client”)
3. If MLinks are not available this is typically a network issue. Check with ‘ping’ via
‘cmd’ if you can reach those MLink.
4. If MStart or MFeed are not available, check with MView, check if MControl is
working proper. Check Communication-Bus-Wiring.
9.1.1 ABB 800xA OPC Client

The standard 800xA installation provides for connectivity test a simple OPC client.
Select ‘AdvDsOPCClient.exe’ out of ‘ProgramFiles\ABB Industrial IT\Operate IT\Process
Portal A\bin”.
<Double click> to start.
156 1TGC910032M0201
Operation
Select ‘Browse’ to search for an OPC Server.
1TGC910032M0201 157
Operation
A new window will open. Open ‘Local’ or ‘Remote’ and select ABB MNSiS OPC Sever (DA
part).
<Click> ‘Ok”.
Small window will be closed. <Click> on ‘Connect’ and wait until window changes to next
one.
158 1TGC910032M0201
Operation
<Click> on ‘Add’ to open a new group.
A new small window will open.
1TGC910032M0201 159
Operation
Edit the name of the group.
<Click> ‘Ok’.
<Click> ‘Add’.
160 1TGC910032M0201
Operation
Select ‘Browse OPC Server’.
1TGC910032M0201 161
Operation
Open ‘Root’ and navigate to the relevant MLink or even deeper.

Are all connected MLink visible?
Are all connected MStart or MFeed visible?
162 1TGC910032M0201
Operation
Select in the right window subscriptions you want to connect to and <click> every time on
‘Add’.
If you are done, <click> ‘done’. Window will close.
1TGC910032M0201 163
Operation
<Click> now ‘Advise’.
164 1TGC910032M0201
Operation
All connected subscriptions will be continuously updated (acc. update rate of group).
Values are displayed under ‘Subscribe Value”.
To disconnect <click> ‘Disconnect”.
9.1.2 Softing OPC Client
This is no shareware. A proper license is required!
Run the software ‘Softing OPC Client”. The main window is opened:
1TGC910032M0201 165
Operation
Open ‘local’ with a click on the ‘+’ to the left of ‘local”. Afterwards open ‘DataAccessV3”.
Now you should see minimum one ‘ABB MNS iS OPC DA Server”. Double-click it.
The ‘ABB MNS iS OPC DA Server’ is now visible at the left side of the window and after
being a short while ‘red’ it turns to ‘green”.
166 1TGC910032M0201
Operation
If it doesn’t turn to ‘green’ the communication between this software and the ‘ABB MNS iS
OPC DA Server’ is not GOOD.
In this case check, if the ‘ABB MNS iS OPC DA Server’ Software on the same PC as the
Softing OPC Client? If not, change configuration to it.
If it is the case, de-install both software (‘ABB MNS iS OPC DA Server”, ‘Softing OPC
Client”) and try it again.
See [1].for details how to diagnose the status of the MNS iS OPC server.
If this does not work, please contact Support.
1TGC910032M0201 167
Operation
Change to tab ‘DA Browse’ and click to the ‘+’ on the left of the ‘ABB MNS iS OPC DA
Server”.
168 1TGC910032M0201
Operation
Are all connected MLink visible?
Are all connected MStart visible?
1TGC910032M0201 169
Operation
Right click on ‘ABB MNS iS OPC DA Server”. Select ‘add items to all tags”
In huge plants be aware that this will lead now to huge data-transfer of app. 150
variables for each MStart.
170 1TGC910032M0201
Operation
Change over to tab ‘DA items’ After a while the ‘red’ will turn to ‘green”.
1TGC910032M0201 171
Operation
Check special values if you like by scrolling down.
172 1TGC910032M0201
Operation
9.2 Path not found

If Asset Monitor shows error message ‘Path not found’ then a required sub-directory path
for the Asset Monitor is missing.
Asset Monitor:
With right mouse click on Asset Monitor, select Asset Monitor Status.
Asset Monitor Status:
Double-check if following sub-directory exists on the right node (AO Server Node):
C:\ABB Industrial IT Data\Optimize IT Data\ABB MNSiS AM Data\
If not, create it.
1TGC910032M0201 173
Operation
If this does not help at all, you might have registered a dll-file which was at an
external hard disk or USB-stick. So, double-check if the correct dll-file is saved at
the local PC hard disk and double-check if this dll-file is registered or register it
again.
Please, take care on un-registering the old, not working, dll-file correctly ! You risk
that this might cause additional problems.
9.3 Error initializing logic

If Asset Monitor shows error message ‘bad, out of service’ after enabling and loading it to
the AO server.
Check in Control Structure object ‘AO Server’ – aspect ‘Asset Optimization Server’ for an
error message.
If there is an error message like ‘error initializing logic”, then first check if the language file
‘MNSiS_AM_MStart_Language.txt’ of the Asset Monitor Package is missing or in a
different sub-directory path as the registered dll-file.
174 1TGC910032M0201
Operation
Double-check the location of ‘MNSiS_AM_MStart_Language.txt’ and

‘MNSiS_AM_MStart_Language.xls’ and correct it if necessary.
1TGC910032M0201 175
Operation
If this does not help or was ok from the beginning, then check if proper MNS iS License is
missing.
Open the ‘Asset Monitor Status’ of relevant Asset Monitor (with right mouse <click> on the
Asset Monitor Main View and selection of menu item).
Compare the message with below one. If identical the MNS iS License is missing.
Open the ABB 800xA License Entry Program. Open ‘800xA Asset Optimization’ and check
for code ‘AO_MNSIS_AM”. If this is missing the MNS iS License is missing and all Asset
Monitors will not work.
176 1TGC910032M0201
Operation
MNS iS Licenses can be bought using ABB 800xA Wizard via ABB Automation
Orderbox and verified through ABB 800xA Software Factory.
9.4 National Language Support does not work in Asset Monitor

The Asset Monitor does not show the language you selected? Please, check following
points:
1. The Asset Monitor View looks like this:
Then, please go to chapter ‘9.5 Description field of Asset Monitor”
1TGC910032M0201 177
Operation
2. If Asset Monitor shows error message ‘bad, out of service” or “BadNotConnected”
Check in Control Structure object ‘AO Server’ – aspect ‘Asset Optimization Server’
for an error message.
Then, please go to chapter ‘9.3 Error initializing logic”.
178 1TGC910032M0201
Operation
9.5 Description field of Asset Monitor starts with a ‘dot’

The Asset Monitor View looks like below mentioned screenshot:
The National Language Support is not working and the default language English is used.
1TGC910032M0201 179
Operation
Double-check the settings in field ‘Value’ of Aspect ‘ABB_MNSiS_AM_Settings’ for object

‘Asset Optimization”. There might be a wrong or mistyped input.
180 1TGC910032M0201
Operation
Compare it with name of sheet in Excel-file ‘MNSiS_AM_MStart_Language.xls”.
Double-check, that the language text files was created and is available in the same
directory as the asset monitor dll files.
1TGC910032M0201 181
Operation
9.6 Unhandled exception in Logic, object variable not set [91]

If below error message ‘unhandled exception in logic, object variable not set [91]’ occurs
then not all logic-files (*.dll) are registered.
Following asset monitor view:
Right mouse <click> on any line of the asset monitor opens menu, select ‘asset monitor
status”.
Following window will be opened:
182 1TGC910032M0201
Operation
This issue is clearly related to logic-files responsible for historical data access or system
alarm manager.
Please double-check if following dll-files are registered, if not please register:

• AfwMessageServiceWrapper.dll
(logic to transfer messages from Asset Monitor directly to System Message Server)
9.7 Asset Monitor ‘bad”

Asset Monitor shows a bad status in all lines in column ‘Quality Status”.
1TGC910032M0201 183
Operation
Select Aspect ‘Asset Viewer’ of relevant MNS iS OPC Server Network or MLink
Connection to the MLink is BAD. Check communication between ‘ABB MNS iS OPC DA
Server’ and MLink.
If the MLink status is ok (no red cross for lost communication) and single MStart
have still the red cross, there might be a capacity problem on the communication
bus down to MLink. Check, if it disappears by after some time and observe this
issue for any repetition.
If communication is ok (no red cross at all for MLink and MStart), then go to the faceplate
and re-load the Asset Monitor: Open the config view using the left button in the button bar (
1 ) and then press the ‘load configuration to AO server’ button ( 2 )
184 1TGC910032M0201
Operation
1TGC910032M0201 185
Operation
A new window opens indicating the reload process to the server. Click ‘continue’ (or abort
if you wish to abort).
The config view shows, if the re-load was successful..
186 1TGC910032M0201
Operation
1TGC910032M0201 187
Operation
If this does not help, perform following steps.
Right click on severity of the Asset Monitor and select ‘Asset Monitor Status’ out of the
shown menu.
For the Asset Monitor Status, 2 possibilities might happen:

1. GOOD: The logic is running properly, all inputs, outputs and parameters are ok.
BAD: Click button ‘Input Records”, check whether all input records are GOOD 4.
Check if Asset Monitor Parameter ‘ae_prot_Temperature2’ is set to
FALSE. Check if other parameters fit to the MNS Engineer application. If
not, this is a problem between 800xA – MNS iS OPC DA Server – MLink.
2. GOOD: The logic is running properly.
BAD: Selection of Asset Monitors:
Ask for support
All Asset Monitors:
Is the correct dll-file loaded and registered?
Is the old dll-file un-registered?
4
All input records GOOD means all besides measuring values Temp21, Temp22, Temp23 and Event Alarm
ContactTemperatureL1B, ContactTemperatureL2B, ContactTemperatureL3B which might be
‘BadNotConnected”.
188 1TGC910032M0201
Operation
1TGC910032M0201 189
Operation
View of input records.
190 1TGC910032M0201
Operation
If this does not help, perform following steps.
Go to the Control Structure and select object ‘Asset Optimization’ and relevant sub-object
‘AO Server…”. Select tab ‘AO Server’ of the aspect ‘Asset Optimization Server”. Check
‘Asset Monitoring Engine”. Is the engine running? Is the engine time still working? Is the
engine status good?
In case of any doubt, click on ‘navigate to Asset Monitoring Service Provider”.
1TGC910032M0201 191
Operation
Go to tab ‘configuration”.
In case of any doubts,
• uncheck ‘enable’ and press ’apply‘.
• Wait until current status changes to ‘undefined’,
• check ’enable‘, press ’apply‘,
• current status shall switch through ‘initialise’, ‘ready’ to ’service‘ in a few seconds
Check, if the ‘Quality Status’ of the relevant Asset Monitor is now GOOD.
If not, ask for support.
192 1TGC910032M0201
Operation
9.8 Asset Monitor ‘good’ but unexpected messages

Asset Monitor shows a good status but does not work proper or shows strange messages
in the table view.
Go to the Aspect ‘Control Connection’ of the MStart / MFeed object.

Check with active ‘subscribe for life data’ if the Quality is GOOD and the Values are
changing.
As an example the Control Connection Aspect is shown here:
1TGC910032M0201 193
Operation
If any problem is shown here, delete the object and install it new. If problem persists, ask
for support.
9.9 Can’t acknowledge alarms in 800xA

If it is not possible for you to acknowledge any alarms in the 800xA alarm lists, then please
check if your user account has an operator function. If not, it is normal. Correct this if
required.
9.10 National Language Support does not work in Faceplate

This function is not yet implemented. In the faceplate only English Language is used.
9.11 Error Correction: Too many files [67]

Currently under clarification! Ask for Support!
9.12 Error Correction: Event Collector

The Asset Alarm Band shows the red cross due to the Event Collector_ABB 800xA Soft
Alarms OPC Server_<Node name>, service provider is disable.
194 1TGC910032M0201
Operation
Open Enginnering Workpalce, go to “Service Structure“, open tree “Event Collector,

service“ object, and look for Event Collector_ABB 800xA Soft Alarms OPC Server_<Node
name>, service provider.
Go to“Special Configuration“ tab and check that the configure is correct.
1TGC910032M0201 195
Operation
Back to“Configuration“ tab , click“Enable“ then click“Apply“ button.
196 1TGC910032M0201
Operation
Wait until the status changes to service.
The result will show as below.
1TGC910032M0201 197
Operation
9.13 Maintenance Faceplate not proper displayed

After import of MNS iS object types it happens in seldom cases that a faceplate is not
properly displayed.
If display is as below, then follow described procedure.
Check some of the faceplates in the control structure, if all are not proper displayed, check
aspect ‘…_Faceplate’ for each MNS iS object type in object type structure.
Before continuing, please check Windows – Regional Options. If they are not set to
‘English (United States)”. Please correct!
198 1TGC910032M0201
Operation
Open the config view of the aspect ‘…_Faceplate’.
1TGC910032M0201 199
Operation
Select tab ‘Element’.
You may see the Aspect are empty.
200 1TGC910032M0201
Operation
Make AssetMonitor and Reset aspect available for everyone as below.
If column ‘View’ is empty in this window, then select in column ‘Aspect’ both
relevant aspects new (1. ‘…_Display”, 2. ‘…_ResetElmt”) and select Main View in
column ‘View’ and fill other cells as shown above.
1TGC910032M0201 201
Operation
Move it with the arrows on the left line 1 step up and 1 step down again.
After finalizing this, picture should be unchanged as below.

Click ‘apply”.
Change to main view again.
202 1TGC910032M0201
Operation
Display is as follows and ok again.
1TGC910032M0201 203
Operation
Select tab ‘Reset’ and check if display is as below.
Repeat this for faceplates which are incorrect displayed in the ‘object type structure”.
204 1TGC910032M0201
Contact us
ABB Low Voltage Systems Copyright© 2011 ABB

Publication Editor: All rights reserved.
ABB Automation Products GmbH
Ladenburg, Germany Publication No.
1TGC910032M0201
Local Contacts on
www.abb.com/mns

1TGC910032M0201 MNSiS 800xa SV5 - 1 ConditionMonitoring OperationManual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1TGC910032M0201 MNSiS 800xa SV5 - 1 ConditionMonitoring OperationManual

Uploaded by

Copyright:

Available Formats

MNS iS Motor Control Center

Condition Monitoring System with 800xA SV5.1

Product names of other products are registered trademarks of their

The information in this document is subject to change without notice and

All rights reserved.

Copyright © 2011 ABB Automation Products GmbH, Ladenburg, Germany

4.7.2 Graphic Display ..........................................................................................80

8.3 Alarm- and Eventlist........................................................................................147

1.1 Target Group

1.2 Use of Warning, Caution, Information and Tip icon

Abbreviation Term Description

CMMS Computerized Computerized Maintenance Management System,

DCS Distributed See also PCS

DTM Device Type Software module used to manage devices via

Eth. Ethernet Ethernet is a local area network (LAN) technology.

FBP FieldBusPlug ABB technology for exchangeable fieldbus interface

FD Field Device Term for devices connected to the fieldbus (e.g.

HMI Human Machine Generic expression

MNS Modular Low Voltage Switchgear family from ABB

MNS iS The integrated intelligent switchgear solution from

Abbreviation Term Description

MStart MNS iS components integrated in the switchgear,

MODBUS Fieldbus communication protocol

MODBUS RTU Fieldbus communication protocol

Motor Starter Consists of motor controller and electrical

NLS Native Language Providing the ability to change the language of

OPC OLE for Process Control, an industrial standard for

PCS Process Control High level process control system

PLC Programmable Low level control unit

PROFIBUS-DP Fieldbus communication protocol with cyclic data

PROFIBUS- Fieldbus communication protocol, extension of

PROFIBUS- Fieldbus communication protocol, extension of

TCP/IP Transmission TCP/IP is a high-level connection oriented , reliable,

Abbreviation Term Description

800xA ABB’s Extended ABB’s Extended Automation System is a software

2 Installation of Asset Monitors, Faceplates and other

For the details of the installation see [7]

2.1 Backup & restore

3 General usage of AssetMonitor Aspects

3.1.1 Main view

3.1.2 Condition mark-up and access to further functionality

3.1.3 Some examples from the MStart AssetMonitor

• Example “ TOL Trip”

3.1.4 Available menus for AssetMonitor aspects

• Main view / configuration view

‘Main view’ is the normal operation view of the Asset Monitor.

3.2 Settings, Configuration and Parameterization of Asset Monitors

MNS iS Object type Aspect category

Example Motor_N1 Is of type MStart_log03s Has an aspect of category ABB_MNSiS_AM_MStart

Primary Control Object Type Aspect System Structure

Scope of Exactly the All instances All instances of the

Following Settings are available:

• Logic Execution Interval for Cubicle Asset Monitor:

3.2.1.1 Modification of Settings in ‘Aspect System Structure”

• Navigate to the ‘Aspect System

To activate those changes, please read sec 3.3

3.2.2 Configuration and parameterization

3.2.2.1 Modification of parameters with Bulk Data Manager

Double-click on the relevant BDM Template to open MS Excel with it.

It is assumed that Bulk Data Manager is proper installed at your 800xA

Click ‘ok’ and continue.

A new window will open to attach a 800xA system.

Select Control Structure for MStart and