mnsis interface manual opc...rcu remote control unit local control unit with pushbutton and...

MNS iS Motor Control CenterInterface Manual OPC Server 7.0System Release V7.3

MNS is a registered trademark.

Product names of other products are registered trademarks of theirmanufacturers.

This document relates to the MNS iS System Release 7.3.

The information in this document is subject to change without notice andshould not be construed as a commitment by ABB. ABB assumes noresponsibility for any errors that may appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental, orconsequential damages of any nature or kind arising from the use of thisdocument, nor shall ABB be liable for incidental or consequential damagesarising from use of any software or hardware described in this document.

This document and parts thereof must not be reproduced or copied withoutABB's written permission, and the contents thereof must not be imparted to athird party nor be used for any unauthorized purpose. The software describedin this document is furnished under a license and may be used, copied, ordisclosed only in accordance with the terms of such license.

All rights reserved.

Copyright © 2013 ABB Automation Products GmbH, Ladenburg, Germany

MNS iS Interface Manual OPC Server Content

1TGC910231M0203 – Release V7.3 3

Table of content

General ........................................................................................................................... 5Target Group .................................................................................................................................... 5

Use of Warning, Caution, Information and Tip icon ............................................................................ 5

Terminology ...................................................................................................................................... 6

Related System Version .................................................................................................................. 10

Related OPC Software Version ....................................................................................................... 10

Document Revision History ............................................................................................................. 10

Introduction .................................................................................................................. 11What is OPC? ................................................................................................................................. 11

OPC History .................................................................................................................................... 11

OPC Specifications ......................................................................................................................... 11

System Structure ......................................................................................................... 12OPC DA .......................................................................................................................................... 14

Data exchange ......................................................................................................................... 14

OPC AE .......................................................................................................................................... 16

Installation .................................................................................................................... 17Hardware requirements ................................................................................................................... 17

Software requirements .................................................................................................................... 17

Restrictions ..................................................................................................................................... 18

Redundancy ............................................................................................................................. 18

Installation procedure ...................................................................................................................... 19

Configuration .................................................................................................................................. 27

Windows Operating System ..................................................................................................... 27

DCOM Configuration ................................................................................................................ 29

Security Setting ........................................................................................................................ 33

User Account Control (UAC) ..................................................................................................... 36

MNSiS OPC Server .................................................................................................................. 38

Performance ................................................................................................................. 39Performance Figures ....................................................................................................................... 39

MNS iS OPC Server Diagnostic Tool.......................................................................... 41Driver .............................................................................................................................................. 42

OPC DA Server............................................................................................................................... 43

OPC AE Server ............................................................................................................................... 43

Configuration .................................................................................................................................. 44

Content MNS iS Interface Manual OPC Server

4 1TGC910231M0203 – Release V7.3

Set OPC ID .............................................................................................................................. 44

Set Language ........................................................................................................................... 46

Set Refresh Rate...................................................................................................................... 47

OPC Server Name Space ............................................................................................ 48MLink .............................................................................................................................................. 48

Primary .................................................................................................................................... 48

Backup ..................................................................................................................................... 51

MControl ......................................................................................................................................... 51

QualityCode ............................................................................................................................. 51

DeviceStatus ............................................................................................................................ 52

Starter dependent status bits .................................................................................................... 54

Measurement Values ............................................................................................................... 55

Diagnostics .............................................................................................................................. 57

AlarmEvent .............................................................................................................................. 58

ComState ................................................................................................................................. 62

Troubleshooting .......................................................................................................... 63

MNS iS Interface Manual OPC Server Introduction

1TGC910231M0203 – Release V7.3 5

General

Target Group

This document describes communication and control interfaces used in MNS iS. The manual isprimarily intended for those requiring information on accessing information and data providedfrom MNS iS. Furthermore the document provides information for integration of MNS iS as dataprovider for SCADA or Plant Asset management systems.

It is assumed that the reader of this manual is familiar with basic terms of automation systems,data communication and computer networks based on TCP/IP.

Use of Warning, Caution, Information and Tip icon

Introduction MNS iS Interface Manual OPC Server

6 1TGC910231M0203 – Release V7.3

Terminology

List of the terms, acronyms, abbreviations and definitions that are used in this document:

Abbreviation Term Description

Aspect Object ABB technology. An Aspect Object is a computerrepresentation of a real object such as a pump, a valve, anorder or a virtual object such as a service or an object type.An Aspect Object is described by its aspects and isorganized in structures.

Alarm Alarm is defined as status transition from any state toabnormal state. Status transition to abnormal state can bedata crossing over the pre-defined alarm limit.

Bus Local A Control Access term describing that the MControl acceptsits commands from a device on the switchgear controlnetwork, e.g. the Web Interface, MView.

COTS Commercial off theshelf

Commercial off the shelf product, term to describe productsavailable on the market, ready to use

DCS Distributed ControlSystem

See also PCS

DTM Device TypeManager

Software module used to manage devices via 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. TheEthernet standard specifies the physical medium, accesscontrol rules and the message frames.

Event An event is a status transition from one state to another. Itcan be defined as alarm, if the state is defined as abnormalor as warning as a pre-alarm state.

FD Field Device Term for devices connected to the Fieldbus (e.g. motorcontrol units or circuit breaker protection)

GSD file Geräte Stamm Datei(Germanabbreviation)

A hardware description file for a PROFIBUS-DP orPROFIBUS-DP/V1 slave type

GPS Global PositioningSystem

System to detect local position, universal time and timezone, GPS technology provides accurate time to a system

Hardware Local A Control Access term describing that the MControl acceptsits commands from the Hardwired inputs, when therespective Local control input is set to true.


1TGC910231M0203 – Release V7.3 7


HMI Human MachineInterface

Generic expression

LVS Low voltageswitchgear

A factory built assembly built to conform with IEC 60439-1

MCC Motor ControlCentre

Common term for switchgear used for motor control andprotection.

MNS Modular Low Voltage Switchgear family from ABB

MNS iS The integrated intelligent switchgear solution from ABB

MStartMFeedMControlMLinkMViewMNavigate

MNS iS components integrated in the switchgear, see theMNS iS System Guide for technical details

MODBUS Fieldbus communication protocol

MODBUS RTU Fieldbus communication protocol

Motor Starter Consists of motor controller and electrical components tocontrol and protect a motor, part of Motor Control Center

NLS Native LanguageSupport

Providing the ability to change the language of softwaretools in order to support native languages (English is basis,others are optional)

OPC OLE for Process Control, an industrial standard forexchange of information between components and processcontrol application

PCS Process ControlSystem

High level process control system

PLC Programmable LocalController

Low level control unit

PROFIBUS-DP Fieldbus communication protocol with cyclic data transfer(V0).

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


8 1TGC910231M0203 – Release V7.3


PROFIBUS-DP/V2 Fieldbus communication protocol, extension of PROFIBUS-DP allowing time stamp and communication betweenmaster and slave (V2).

PROFINET PROFINET is an open standard for Industrial Ethernet andstandardized in IEC 61158 and IEC 61784.

PNIO PROFINET IO PROFINET for decentralized periphery and distributedautomation

RCU Remote Control Unit Local control unit with pushbutton and indicator to operate adevice (e.g. motor) from field level.

RS232 Standard No. 232 for PC communication, established byEIA (Electronics Industries Association, USA)

RS485 Communication interface standard from EIA (ElectronicsIndustries Association, USA), operating on voltagesbetween 0V and +5V. RS-485 is more noise resistant thanRS-232C, handles data transmission over longer distances,and can drive more receivers.

RTC Real Time Clock Integrated clock function in devices used to generate timeand date information if a remote clock system is not present

Software Local A Control Access term describing that the MControl acceptsits commands from the hardwired inputs as a result of eitherthe PCS or MView passing the Control Access Authority toSoft-Local.

Note: Does not require the hardwired local input to be set totrue.

SNTP Simple NetworkTime Protocol

a protocol used for time synchronization in Control Networkthrough Ethernet

Switchgear BusNetwork

Term used to describe the internal switchgearcommunication network, between MLink and MControl.

TCP/IP TransmissionControl Protocol /Internet Protocol

TCP/IP is a high-level connection oriented, reliable, fullduplex communication protocol developed for integration ofthe heterogeneous systems.

Trip A consequence of an alarm activated or an external tripcommand from another device to stop the motor or trip thecircuit breaker.


1TGC910231M0203 – Release V7.3 9


UTC CoordinatedUniversal Time

Coordinated Universal Time is the international timestandard. It is the current term for what was commonlyreferred to as Greenwich Meridian Time (GMT). Zero (0)hours UTC is midnight in Greenwich England, which lies onthe zero longitudinal meridian. Universal time is based on a24 hour clock.

Warning A warning is defined as status transition from any state topre-alarm state to inform in advance before an alarm level isreached.


10 1TGC910231M0203 – Release V7.3

MNS iS1TGC910211 M0201 MNS iS Interface Manual MLink, Release 7.0

1TGC910111 M0201 MNS iS MLink Upgrade Kit Manual

1TGC910221 M0201 MNS iS Interface Manual Web Interface, Release 7.0

1TGC910241 M0201 MNS iS Interface Manual Profibus, Release 7.0

1TGC910251 M0201 MNS iS Interface Manual Modbus, Release 7.0

1TGC910291 M0201 MNS iS Interface Manual PROFINET IO, Release 7.0

1TGC910281 M0201 MNS iS MControl Interface Manual Profibus Direct, Release 7.0

1TGC910261 M0201 MNS iS Interface Manual Redundancy, Release 7.0

1TGC910271 M0201 MNS iS MConnect Interface Manual, Release 7.0

1TGC910001 B0204 MNS iS System Guide

1TGC910201 M0201 MNS iS Quick Guide Installation and System Setup, Release 7.0

1TGC910090 M0201 MNavigate Help file V7.0

1TGC910018 M0208 MNS iS ATEX – Enhancements for Safety

Related System Version

The content of this document is related to MNS iS System Release 7.3.

The described functions are designed but may not be fully implemented in all details. Pleaserefer to the current system guides and release notes regarding possible restrictions.

Related OPC Software Version

The MNS iS OPC Software version related to this release has the following identifier numberand description.

1TGE160007R1000 E OPC Server 7.0e for DA and AE

Document Revision History

Rev. Chapter Description of change Date

M0201 all Initial document for OPC Server 7.0c June 2012

M0202 OPC Server Name Space Update for OPC Server 7.0e

Data item MLink HW version added

March 2013

M0203 OPC Server Name Space Removed MNSiS internal data types Sep 2013


1TGC910231M0203 – Release V7.3 11

Introduction

What is OPC?

OPC is an open industrial standard for process control and information system interconnectivity.Information exchange is possible without directly accessing hardware and software componentsinside the switchgear system. OPC Server software resides in the process control environment.

To ensure common understanding and interoperability the OPC Foundation (founded in 1996)coordinates specification and development issues. http://www.opcfoundation.org

OPC History

Historically, OPC was an acronym for OLE for Process Control and is based on the componentmodel from Microsoft’ ActiveX, COM and DCOM technology.

OPC development started in 1990 based on Windows 3.0 technology. In 1992 OLE 2.0 wasreleased by Microsoft.

Year Event

1995 OPC Task Force formed

1996 OPC Foundation

1998 OPC DA 2.0 Release

2003 OPC DA 3.0 Release

2005 OPC XMLDA 1.0Release

OPC Specifications

Following OPC specification are available (2005 released versions):· Data Access 3.00 (DA)· Data Access 1.01 (XMLDA)· Complex Data 1.00 (CPX)· Historical Data Access 1.20 (HDA)· Alarms & Events 1.10 (AE)· Data Exchange 1.00 (DX)· Batch 2.00· Security 1.00· Unified Architecture (UA)

Due to its data format and requirements in MNS iS only OPC DA 3.00 and OPC A&E 1.10 aresupported. Historical Data OPC HDA is NOT supported

OPC ensures compatibility that means, OPC DA 3.00 is compatible to upcoming newversions of OPC DA. However, it will not be fully compatible to e.g. former versions ofOPC e.g. OPC DA 2.05.

http://www.opcfoundation.org/

System Structure MNS iS Interface Manual OPC Server

12 1TGC910231M0203 – Release V7.3

System StructureOPC is based on a client / server architecture. The OPC Server provides data collected from itssource (e.g. own device or other devices and components). OPC Clients can access the serverthrough a standard network and interfaces.

OPC Client Level

Different applicationutilising same serverinterface.

OPC Server Level

Different subsystems utilising thesame client interface.

Fig. 1 System Structure

MNS iS Interface Manual OPC Server System Structure

1TGC910231M0203 – Release V7.3 13

MNS iS OPC Overview

The MNSiS OPC Server resides in a Microsoft Windows based PC. It is connected with onenetwork interface to the MNSiS switchgear network. Another network might be connected tohigher level plant or control networks. Those are customer and project specific.

Fig. 2 MNS iS OPC network topology sample

The MNS iS OPC Server supports redundant MLinks. Should a redundancy switch-overhappen, this action is handled internally within the MLinks and the OPC Server, and istransparent to the OPC clients.


14 1TGC910231M0203 – Release V7.3

OPC DA

Data exchange

This mechanism functions on a request and response mechanism as detailed below. WithinMNS iS the MLink is the data provider for the MNS iS OPC Server. Once the OPC client isstarted and connects to the server the MLink automatically updates the information available inOPC Server.

Request

The OPC Client (e.g.SCADA application)sends a request tothe OPC Server

Response

The OPC Server respondsto the client with therequested data.

Fig. 3 Data Exchange

OPC DA provides a standardized method for real-time data access. It decouplesimplementation of a device, controller, system or application from its data points. Every dataitem in an OPC DA Server comprises data like an item name, value(s) of different specified datatypes and some mandatory or optional properties (e.g. timestamp, quality, access rights, scanrate etc.).

OPC DA enables real-time (not hard real-time!) access to data items. The data transfer can beconfigured to a synchronous or asynchronous access. In case of the asynchronous method, theOPC data item variables are refreshed asynchronous to the application (source) related dataupdate rate.

Main application of OPC DA is to exchange data between the PLC level and the HMI level. Theuser gets a real-time picture of current process related data and is able to interact with the hardreal-time control application via entering commands or adopting parameters. Today OPC DA isalso use to feed Plant Asset Management systems, to continuously supervise and assess thehealth status of the production and equipment. OPC DA Server are part of almost every processcontrol system today as well as OPC DA Clients are available for almost every process controlapplication too.

MNS iS Interface Manual OPC Server System Structure

1TGC910231M0203 – Release V7.3 15

Beside value and quality the OPC Server provides a time stamp, which is a mandatoryproperty of an OPC item. All MNS iS DA items (available in OPC name space) are timestamped by OPC Server system time. The time stamp itself is reflecting the time of lastupdate of the value.

Data format:

Fig. 4 OPC DA


16 1TGC910231M0203 – Release V7.3

OPC AE

Alarm and event servers are used for reporting alarms and events to operator stations, loggersystems or management subsystems. The Alarm and Event server describes a condition as adefinable state for all of its objects (process values, process condition). An event (stateless) is adetectable occurrence of significance to the Alarm and Event Server and alarms are abnormalconditions (with state).

The clients are informed of an occurrence of an alarm or event via call-backs, thus an eventdriven and not polling communication is implemented.

MNS iS always provides MControl generated time stamps for alarms and events.

Alarms and trips can be acknowledged by the user (OPC client). In case of a trip thisacknowledgement results in trip reset command sent to the MControl. If the MControl is incontrol access ‘Bus-local’ the trip reset is executed.

Fig. 5 OPC AE

MNS iS Interface Manual OPC Server Installation

1TGC910231M0203 – Release V7.3 17

InstallationMNS iS OPC Server is typically installed on one PC or Server available from process controlsystems. The Server is integrated into the MNS iS switchgear control network as shown below:

Fig. 6 Network Configuration

Hardware requirements

· IBM compatible PC (1.83 GHz processor clock, 1 GB Ram min)

· Ethernet interface card (10/100/1000-Base-T)

· 50 MB hard disk space required for all software modulesincl. data for one MLink with 60 MControl

Software requirements

OPC Server can be installed in any one of below OS:Operating system Service PackWindows XP Professional (32Bit) SP3Windows XP Professional (32Bit) SP2Windows XP Professional (64Bit)Windows Server 2003 (32Bit) R2 enterprises with SP2Windows Server 2003 (64Bit) R2 enterprises with SP2Windows 7 (32Bit) Enterprises SP1Windows 7 (64Bit) Enterprises SP1Windows Server 2008 (32Bit) SP2Windows Server 2008 (64Bit) R2 with SP1

Installation MNS iS Interface Manual OPC Server

18 1TGC910231M0203 – Release V7.3

The following components are needed and configured properly:

· Microsoft Message Queue (MSMQ)

à Activation of this component is done during installation procedure

· DCOM enabled and Security level configured to allow remote access via “Connection-oriented TCP/IP”

à Please see page 29 for details

· On Windows 7 the ‘User Account Control’ (UAC) has to be disabled.

à Please see page 36 for details

Restrictions

Redundancy

1. The maximum number of OPC Server communication channels per MLink is restrictedto 2. That means 2 OPC Server (DA/AE)*** can be connected to a dedicated MLink.

2. Redundant OPC Servers are not supported.

3. Communication switchover between active to non active MLink handled automatically(takes max. 10 seconds) when ever Ethernet communication breakdown between activeMLink & OPC Server. Due to communication interruption all DA values and AEmessages are lost during this switchover time. After switchover procedure the updateprocess is resumed.

4. There are two instances of OPC Component in task manager for Windows Server 2008when first OPC client run through services and second OPC client started by usermanually.

5. User has to Install OPC server by Run as Administrator for Windows 7 & WindowsServer 2008.

*** MNSiS OPC Server > V6.0


1TGC910231M0203 – Release V7.3 19

Installation procedure

1. If there is an older OPC Server version installed, this version has to be uninstalled first.Therefore open Control Panel, and select Uninstall Programs (If it is an initialinstallation please proceed with step 4.)

2. Select ABB MNSiS OPC Server and select Uninstall


20 1TGC910231M0203 – Release V7.3

3. Select OK

NOTE: Remove OPC_Pctrl folder manually (C:\Programme Files\ABB\ABB MNSiS OPC Server)

4. Install the new OPC Server – open the Installer file and select the Setup.exe file1

1User has to Install OPC server by Run as Administrator for Windows 7 & Windows Server 2008.


1TGC910231M0203 – Release V7.3 21

5. Select Next

6. Accept the license agreement and select Next


22 1TGC910231M0203 – Release V7.3

7. Insert a User Name and a Company and select Next

8. Select Next9. If OPC DA & OPC AE is required select Next (proceed with 14)


1TGC910231M0203 – Release V7.3 23

10. If only OPC DA or OPC AE has to be installed select Custom and select Next

11. Select Next


24 1TGC910231M0203 – Release V7.3

12. Unselect one of the OPC Servers by selecting Entire feature will be unavailable

Note: In this example option ABB MNSiS OPC AE Server is disabled.

Note: In this example option ABB MNSiS OPC DA Server is disabled.


1TGC910231M0203 – Release V7.3 25

13. Select Next14. Select Install

15 While installing


26 1TGC910231M0203 – Release V7.3

16. Select Finish

MNS iS Interface Manual OPC Server Performance

1TGC910231M0203 – Release V7.3 27

Configuration

Windows Operating System

Firewall

If a firewall is used the following processes have to get access to Ethernet network:

Process Usage

MNSiSOPCDriver.exe Communication between MLink and MNSiS OPCServer

MNSiSDAServer.exe Communication between MNSiS OPC DA Server andOPC DA Client

MNSiSAEServer.exe Communication between MNSiS OPC AE Server andOPC AE Client

MNSiSOPCServerDiagnostic.exe Visualization of MNSiS OPC Server status information

In addition to the processes the following ports have to get access to the Ethernet network:

Port Usage

20020 Communication Channel between MLink and OPCServer

20002 Automatic detection of newly inserted MLink devices

22 Upload of configuration files

Performance MNS iS Interface Manual OPC Server

28 1TGC910231M0203 – Release V7.3

For Windows 7 the following steps have to be done to adjust firewall settings:

1. Select Window Firewall

2. Click Allow a program or features through Windows Firewall and mark the followingentries:

· MNSiS OPC Data Access Server

· MNSiS OPC Alarm Event Server

· MNSiS OPC Driver


1TGC910231M0203 – Release V7.3 29

DCOM Configuration

DCOM uses security settings to protect client and server from unauthorized access. Thesecurity settings could be changed with the program DCOMCNFG. You need to haveadministrator rights to use the program.

The following table contains all parameter that have to be checked / adjusted:

The following steps have to be done to enable a setup DCOM properly

1. Open Component service by click start run and type DCOMCNFG

Parameter Setting

Default Protocols Connection Oriented-TCP/IP

Default Authentication Level None

Default Impersonation Level Impersonate

Launch and Activation Permission Everyone

Access Permissions Everyone


30 1TGC910231M0203 – Release V7.3

2. Open Computersà My Computers and select Properties

3. Select tab Default Protocols and verify the Connection-oriented TCP/IP available, Ifnot add It as per below image by Add button


1TGC910231M0203 – Release V7.3 31

4. Select tab Default Properties. Set None for Default Authentication Level and setImpersonate for Default Impersonate Level and click apply, ok

5. Select tab COM Security and click Edit Default… for Access Permission6. In Access Permission wizard click Add


32 1TGC910231M0203 – Release V7.3

7. In “Select Users or Groups” wizard, Type “Everyone” and click Check Names andclick ok

8. User “Everyone” is added to wizard Access Permission now selects Everyone andverifies the permission. Remote Access should be checked, if not then check it and clickok.


1TGC910231M0203 – Release V7.3 33

9. Click Edit Limits… in Access Permissions, select ”Everyone” and verify RemoteAccess is checked, if not check and click ok

10. Repeat the Step 5 to 9 for “Launch and Activation permission”

Security Setting

The default installation for PC forces remote users to authenticate as Guest. This means thatDCOM clients cannot connect to a server running on an XP machine unless the Guest accountis enabled and has enough rights to launch the server. The following steps have to be done toadjust Security Options:

1. Click on Startà Control Panel2. Select System and Security


34 1TGC910231M0203 – Release V7.3

3. Select Administrative Tools

4. Select Local Security Policy


1TGC910231M0203 – Release V7.3 35

5. Select Security Options in Local Policies and select Network access: Sharing andsecurity model for local accounts and change it to Classic- local users authenticate asthemselves

6. Select Network access : Let Everyone permissions apply to anonymous user andchange it to Enabled

Please note:DCOM settings apply only when the OPC Client and Server are installed on separate PCs.


36 1TGC910231M0203 – Release V7.3

User Account Control (UAC)

On Windows 7 the ‘User Account Control’ (UAC) has to be disabled. Please follow the followingsteps to disable UAC:

1. Click on Startà Settingsà Control Panel

2. Select System and Security


1TGC910231M0203 – Release V7.3 37

3. Select Change User Account Control settings

4. Move the slider to Never notify position, and click OK.

5. Restart your computer to activate the setting


38 1TGC910231M0203 – Release V7.3

MNSiS OPC Server

All OPC Server related configuration can be done by using MNSiS OPC Server Diagnosticutility. The following parameter can be adjusted in OPC Server:

· OPC ID (OPC Communication Channels)

MNSiS supports an auto-detection of all connected MLinks. This means that every OPCServer in the same network can create a communication channel to all connected MLinkdevices. As soon as the OPC Client connects to a particular MNSiS OPC Server theserver is creating the namespace of all available MLinks. The maximum number of OPCServer communication channels per MLink is restricted to 2. That means 2 OPC Server(DA/AE)*** can be connected to a dedicated MLink. To reduce the number of MLinkavailable in the name space of a particular OPC Server the following actions can betaken:

o Physical Ethernet segmentation

o IP Segmentation (Creation of Ethernet subnets)

o Usage of OPC ID (for details please refer page: 44)

· OPC AE message language (for details please refer page: 46)

· OPC refresh time (for details please refer page: 47)

*** MNSiS OPC Server > V6.0


1TGC910231M0203 – Release V7.3 39

PerformanceThe data refresh rate between MNS iS system and OPC Server is independent of therequest rate from the OPC Client to the OPC Server. The refresh rate between MLinkand OPC Server can be configured in MNSiS OPC Server Diagnostic tool (see section

Set Refresh Rate) and is relevant for all OPC DA items. For all OPC AE messages an eventdriven mechanism is implemented. The event is fired as soon as it detected on MLink side.

Requests from OPC clients for OPC items with simultaneous access from the OPC Server areworked through in sequence. Depending on bus usage, the configured update rate may not beattained, in which case the OPC Server will return the last valid value. The new value will thenbe accessible during the next access to the OPC item.

Real time values cannot be achieved for parallel OPC requests from the client, as theserequests are worked through in sequence.

After a configuration change in the MNS iS system (MNavigate download) the OPCClient has to be reconnected to MNSiS OPC Server, because the name space was re-created.

Refresh rate in the client side should be confirmed as per Client provider. Server &Client refresh rate should be reduced to 3Sec in case of 20 or more MLink connectedwith 15 changeable tags per MControl for 60 MControls. This can be set in Diagnostic

utility.

Performance Figures

The figures below are based on an Intel Core2 Duo CPU at 2.33 GHz, 4GB RAM 32bit system

Number ofMLinks

Number ofMControls

Number ofsubscriptions /MControl

Total number ofsubscribed DAitems

Set Refresh rate inMNSiSOPCServerDiagnosticwizard

4 240 213 51120 1 s

6 360 252 9000 1 s

10 600 252 15000 2 s

20 1200 152 18000 3 s

303 1800 152 27000 3 s

The table above shows the total number of subscribed DA items in combination with the OPCclient refresh rate that is the limiting factor. If the shown update times are not sufficient for adedicated application the number of OPC Servers has to be increased.

2 Changeable tags3 Only DA


40 1TGC910231M0203 – Release V7.3

The first example above with 4 MLinks and 240 MControls shows the worst case situation whereall available items are subscribed from each MControl. The following examples show whatshould be expected for a normal usage of the OPC server and MControl, utilizing 25subscriptions, (data values).

MNS iS Interface Manual OPC Server Diagnostic Tool

1TGC910231M0203 – Release V7.3 41

MNS iS OPC Server Diagnostic ToolThis tool enables the user the possibility to retrieve more information regarding the status of theOPC server and the connected MLinks. The tool reports the detection of MLinks with the OPCfunctionality enabled, it supplies diagnostics when communication between the OPC Server óMLink is lost. In addition the tool is used to configure the OPC ID and Language.

User has to start diagnostic utility manually by double click the shortcut icon on the desktop. Adialog appears and informs about the upload progress in OPC Driver TAB. After successful fileupload the OPC name space is created. Following dialog entries are shown if the upload wassuccessful.

When the above icon is double clicked it opens the following dialog box opens.

Each of the tabs within the dialog box has the same properties.

When the tool is running events are then logged in the tool as shown in the next examples.Under the ‘Time’ Column date and time in which the action performed for that particular tab willbe displayed. Under ‘Type’ column Info and Errors are reported. ‘MLink IP’ column shows the IPaddress of the MLinks A description is reported for each Action and for certain errors a solutionis presented in Solution column.

Diagnostic Tool MNS iS Interface Manual OPC Server

42 1TGC910231M0203 – Release V7.3

Driver

This tab can be used to view which files were uploaded by the OPC Driver with matching OPCID within the network.


1TGC910231M0203 – Release V7.3 43

OPC DA Server

This tab can be used to view status of DA server and status of node structure for that particularMLink with IP and Quality of that MLink. This tab can be used to validate the OPC DAcommunication.

OPC AE Server

This tab can be used to view status of AE server and status of node structure for that particularMLink with IP and Quality of that MLink and also can be used to validate the OPC AEcommunication.


44 1TGC910231M0203 – Release V7.3

Configuration

Set OPC ID

The OPC ID enables the user to create MNS iS Ethernet network segments without the need ofphysical or IP Subnet splitting. This could be utilised in systems containing a large number ofMLinks. In these circumstances it may not be possible to handle all MLinks in one OPC server,because of performance reasons (number of OPC tags). By using the OPC ID the number ofaccessible MLinks can be reduced. Please refer to the Performance figures for moreinformation.

By using MNavigate an OPC ID can be configured for each MLink, following this the OPCServer has to be configured by using MNS iS OPC Server Diagnostic tool to set the connectivitysegment for the MLink and associated OPC Server.

This tab has to be used to change the OPC ID of the OPC Server.

Tab for setting of the OPC ID for the OPC Server in theDiagnostic tool

Dialog box for setting of the MLink OPC ID inMNavigate.

The OPC tags of a MLink are only available in a dedicated OPC server if the OPC ID matcheson both sides. The OPC ID is set after pressing the button Set OPC ID. If there are already OPCitems selected in the OPC client and these items are from MLinks with a no longer matchingOPC ID, these items are set to BAD quality!

MLinks having no OPC ID support (prior to V5.4) are available / visible in all logicalnetwork segments.


1TGC910231M0203 – Release V7.3 45

The example below describes the system behaviour if this function is used. The following OPCServer ó MLink relation has to be created by using OPC ID set in the Diagnostic Tool and inMNavigate.

MLink1 MLink2 MLink3 MLink4

OPC Server 1 yes Yes yes no

OPC Server 2 no No no yes

Therefore in MNavigate has to be used to set the following OPC IDs:

MLink1 MLink2 MLink3 MLink4

OPC ID 1 1 1 2

In addition the OPC Servers has to be configured as shown below:

OPC Server 1 Server 2

OPC ID 1 2

After downloading the configuration settings from MNavigate to MLink and setting the OPC IDas described above the following segmentation is created:

MLink1

visible

MLink2

visible

MLink3

visible

MLink4

visible

OPC Server 1 yes Yes yes no

OPC Server 2 no No no yes

Network diagram of the above example.


46 1TGC910231M0203 – Release V7.3

Set Language

Language can be select and set after pressing the button Set Language. After selecting thelanguage, all Diagnostic related information will be come in all TABS of diagnostic utility wizardwith selected language. Only English & German are supported with OPC Server version 7.0.

All Events in AE will be raised with respect to language if the MLink contain latestAEConfiguration file.


1TGC910231M0203 – Release V7.3 47

Set Refresh Rate

The refresh rate is used to set the update interval of all subscribed OPC tags. It defines thecommunication cycle time between the OPC Server and MLink. Presently user can select andset 1000ms, 2000ms & 3000ms as refresh rate for OPC Server. After selecting the regardingrefresh rate value the button Set Refresh Rate has to be pressed. After setting the refresh rate,all subscribed OPC tags of OPC Server name space are based on new refresh rate.

The refresh time between the OPC Client and MNSiS OPC Server is not influencing therefresh time between MNSiS OPC Server and MLink.

OPC Server Name Space MNS iS Interface Manual OPC Server

48 1TGC910231M0203 – Release V7.3

OPC Server Name SpaceThe OPC Server name space is automatically populated based on run-time information fromthe MLinks and MControls. Thus the OPC server does not show any OPC items until theOPC Server has detected connected MLinks and uploaded configuration data from thedetected MLinks.

The OPC Server name space will thus not be known until run-time and the followingparameters affect the final OPC server name space:

· The set of connected MLinks

· The set of connected and configured MControls

MLink

The name space for every MLink depends on the type of project4. In non redundant projectsthe namespace is populated in the following way:

· Name_of_MLink.MLinkData.Primary.

In redundant projects the namespace is populated in the following way:

· Name_of_MLink.MLinkData.Primary.

· Name_of_MLink.MLinkData.Backup

Primary

The values in this section are available here: Name_of_MLink.MLinkData.Primary.

Variable Name Item Description OPC DataType

Comment

IPAddressLan1 IP LAN 1 address EMPTY -

IPAddressLan2 IP LAN 2 address EMPTY -

StatusValue MLink status information32bits

UI4 Pls refer the following table “MLink StatusInformation Table” for details

ComState Communication status ofMLink

(MLinkó OPC Server)

UI1 1 => Communication running

0 => Communication broken

UUID EMPTY -

DeviceName1 Device name 1 of Mlink EMPTY -

DeviceName2 Device name 2 of Mlink EMPTY -

LocationId Location ID of MLink EMPTY Cubicle name in which the MLink is placed

HWVersion Identification of MLinkHW Version

VT_BSTR Pls refer the subsequent table “MLinkIdentnumbers” for details”

4 OPC tags in OPC Client for MLink will be based on the MLinkConfiguration file in the project

MNS iS Interface Manual OPC Server OPC Server Name Space

1TGC910231M0203 – Release V7.3 49

MLink Status Information TableBitNumber

MLink-Application Information

0 MLinkSupervision Processor Temperature monitoring is activated

1 MLinkSupervision Processor Temperature is ok.

2 MLinkSupervision Processor Temperature Alarm

3 MLinkSupervision Processor Temperature critical level Alarm

4 MLinkSupervision Application - Running

5 MLinkSupervision Application - Fatal Error

6 MLinkSupervision Parameter File Error

7 MLinkSupervision Data Map File Error

8 MLinkSupervision Main Board Status Data Read Error

9 MNavigate Server Application - Running

10 MNavigate Server Application - Fatal Error

11 SwitchGearBus Application - Running

12 SwitchGearBus Application - Fatal Error

13 SwitchGearBus SwitchGearBus - No Responses Received

14 Profibus / Modbus Application - Running

15 Profibus / Modbus Application - Fatal Error

16 Profibus / Modbus DCS Communication Running

17 Profibus / Modbus Fault - Data Mapping

18 Profibus / Modbus Fault - Profibus Card (only Profibus)

19 Redundancy Application - Running

20 Redundancy Application - Fatal Error

21 Redundancy Application - Redundancy Enabled

22 Redundancy MLink - Running As Primary

23 Redundancy Fault - Common Redundancy Fault

24 Redundancy Fault - Other MLink not alive

25 Redundancy Fault - Parameter “Startup as Primary” not different

26 Redundancy Fault - Files for DCS data image different (CRC)

27 Redundancy Fault - MControl Files different (CRC)


50 1TGC910231M0203 – Release V7.3

28 Redundancy Fault - No response from SwitchGearBus from backup MLink

29 MLinkSupervision MLink CPU Voltage below critical value

30 MLinkSupervision MLink CPU Usage above alarm level

31 MLinkSupervision Available MLink Memory below alarm level

MLink Identnumbers TableValue of data item “HWVersion” Information

1TGE102009R1001 MLink 1st generation, Profibus, non-redundant

1TGE102019R1001 MLink 1st generation, Profibus, redundant

1TGE102009R2300/4200/4800 MLink 1st generation, Modbus, non-redundant

1TGE102019R2300/4200/4800 MLink 1st generation, Modbus, redundant

1TGE102009R2300 MLink 1st generation, Profinet, non-redundant

1TGE102019R2300 MLink 1st generation, Profinet, redundant

1TGE120021R0110 MLink 2nd generation, Profibus, non-redundant or redundant

1TGE120021R0010 MLink 2nd generation, Modbus or Profinet, non-redundant orredundant


1TGC910231M0203 – Release V7.3 51

Backup

The values in this section are available here: Name_of_MLink.MLinkData.Backup. The contentof this section is the same as for Primary. The shown information is according the configuredbackup MLink.

The OPC Server name space for an individual MControl & MConnect is populated under theroot in the following way:

· Name_of_MLink.Name_of_MControl.Under each MControl the name space is dependent upon the MControl configuration but isnormally grouped in the following way:

· Name_of_MLink.Name_of_MControl.QualityCode

· Name_of_MLink.Name_of_MControl.DeviceStatus

· Name_of_MLink.Name_of_MControl.MeasurementValues

· Name_of_MLink.Name_of_MControl.Diagnostics· Name_of_MLink.Name_of_MControl.AlarmEvent

· Name_of_MLink.Name_of_MControl.Commands

· Name_of_MLink.Name_of_MControl.ComState

MControl

QualityCode

The values in this section are available here: Name_of_MLink.Name_of_MControl.QualityCode.


Comment

QualityCode1 Quality Code 1 Byte Field UI4Contains internal monitoringinformation on the status of themeasurement values.

QualityCode2 Quality Code 2 Byte Field UI4Contains internal monitoringinformation on the status of themeasurement values.


52 1TGC910231M0203 – Release V7.3

DeviceStatus

The values in this section are available here:Name_of_MLink.Name_of_MControl.DeviceStatus.

The availability of DeviceStatus values depends upon the project Application of the MControl.


Comment

Status Starter State UI4 An 32 bit unsigned integer representing all 32bits below

Status_Bit0 Status Bit0 UI1 Depending on Starter Type, see p.54








Status_Bit8 Status Bit8 UI1 Common Alarm

Status_Bit9 Status Bit9 UI1 Common Trip New

Status_Bit10 Status Bit10 UI1 Common Trip Acknowledged

Status_Bit11 Status Bit11 UI1 Common Trip Resettable

Status_Bit12 Status Bit12 UI1 Failsafe Activated




Status_Bit16 Status Bit16 UI1 Test Switch On

Status_Bit17 Status Bit17 UI1 Main Switch On

Status_Bit18 Status Bit18 UI1 Always 0


Status_Bit20 Status Bit20 UI1 Isolated

Status_Bit21 Status Bit21 UI1 Start Inhibit ( including TOL startup inhibit)

Status_Bit22 Status Bit22 UI1 TOL startup inhibit

Status_Bit23 Status Bit23 UI1 TOL bypass activated

Status_Bit24 Status Bit24 UI1 CA owner HW local

Status_Bit25 Status Bit25 UI1 CA owner SW local

Status_Bit26 Status Bit26 UI1 CA owner Bus local

Status_Bit27 Status Bit27 UI1 CA owner 2nd Fieldbus




1TGC910231M0203 – Release V7.3 53

(continued)Status_Bit30 Status Bit30 UI1 Always 0

Status_Bit31 Status Bit31 UI1 CA owner Remote

GPI GPI Status 1-16 UI2 16 bit unsigned integer representing the bitsbelow

GPI1 GPI1 Status UI1 General Purpose Input 1
















GPIA1 GPIA1 Status R4 General Purpose Analog Input 1

16 bit scaled value (multiplied by 10)

GPIA2 GPIA2 Status R4 General Purpose Analog Input 2

16 bit scaled value (multiplied by 10)


54 1TGC910231M0203 – Release V7.3

Starter dependent status bits

The following bits are dependent upon the Starter application used.

Star

terT

ype

NR

-DO

L

NR

-DO

L-R

CU

Rev

-DO

L

Rev

-DO

L-R

CU

NoS

tart

erM

odul

e

NrD

olSo

ftsta

rter

NrD

olS/

D

Act

uato

r

Tran

spar

ent

with

Con

trol

Tran

spar

entw

/oC

ontr

ol

MFe

ed/C

Feed

Bit

0 Stopped

Stopped

Stopped Stopped Stopped Stopped Stoppe

d Stopped 0 Off

1 Runs Runs Runs Runs Runs Runs Runs Runs 0 On

2 0 0 (Runs)CW

(Runs)CW 0 0 (Runs)

CW(Runs)Close K1 0

3 0 0 (Runs)CCW

(Runs)CCW 0 0 (Runs)

CCW(Runs)Open K2 0

4 0 0 0 0 0 0 0 0 K3 0

5 0 0 0 0 0 Softstop 0 ClosePosition 0 0

6 0 0 0 0 0 Softstart (Runs)Star

OpenPosition 0 0

7 Ready Ready Ready Ready Ready Ready Ready ReadyReady

(NoTrip)

Ready(CFeed

)

8 Common Alarm

9 CommonTrip New

10 Common Trip Acknowledged

11 Common Trip Resettable

12 Failsafe Activated

13 0 1 0 1 1 1 0 0 0 0

14 0 1 0 1 1 0 1 0 0 1

15 0 0 0 0 1 0 0 1 0 1

Note: Bits 13- 15 are utilised for internal system information.


1TGC910231M0203 – Release V7.3 55

Measurement Values

The values in this section are available here:Name_of_MLink.Name_of_MControl.MeasurementValues

Note:The availability of Measurement values depends upon the project Application of the MControl.

Variable Name OPC Item Description OPC DataType

Comment / physical Unit

ActiveEnergyCounter Active energy counter R4 kWh Kilowatt Hour value

ActivePower Active Power R4 kW Kilowatt

AI1Analog input value from AI1 R4

ApparentPower Apparent Power R4 VA

CosPhi Power Factor CosPhi R4

Frequency Frequency R4 Hz

IearthFault Residual Current R4 In cases where a 3 phaseMStart is configured as a 1phase, no value is available

IL1 Current Phase L1 R4 A



IL1Percent Current Phase L1 Percentage UI2 %



InsertionCycles Insertion Cycles MStart UI4

PT100Temperature PT100 1Ch Temperature R4 For 1CH PT100

PT100Temperature1 PT100 Temperature 1 R4 For 3CH PT100 Ch1

PT100Temperature2 PT100 Temperature 2 R4 For 3CH PT100 Ch 2

PT100Temperature3 PT100 Temperature 3 R4 For 3CH PT100 Ch 3

PTCresistance PTC Resistance UI2 Ω

ReactivePower Reactive Power R4 kVar

Reserved Reserved R4

SwitchCyclesK1 Switching Cycles K1 UI4


56 1TGC910231M0203 – Release V7.3



Temp11 Contact Temperature L1 R4 °C



ThermalImage Thermal Image UI2 -

U12 Phase Voltage L1-L2 R4 V




1TGC910231M0203 – Release V7.3 57

Diagnostics

The values in this section are available here: Name_of_MLink.Name_of_MControl.Diagnostics

The visibility and validity of values in this section depends on the project Application of theMControl.


Comment / physicalUnit

CurrentAtTripValid Current at Trip is valid(if value=1)

UI1 A

DcVersion MControl FirmwareVersion

R4

MeasuredMotorStartTime Measured MotorStartup Time

R4 s

MsDiagnostic MStart Diagnostic UI4

OperatingHours Operating Hours UI4

TimeToTrip Time To Trip UI2 s

TimeToReset Time To Reset UI2 s

TolDiagnostic TOL Diagnostic UI4

TripCurrentL1 Current At Trip L1 R4 A




58 1TGC910231M0203 – Release V7.3

AlarmEvent

The values in this section are available here: Name_of_MLink.Name_of_MControl.AlarmEvent.

The availability of the AlarmEvent values depends upon the project configuration.

EaroEntryTBit0: “Alarm New”

Bit1: “Trip New”

Bit2: “Trip Acknowledged”

Bit3: “Trip Resetable”FeederMCCB Feeder MCCB UI1 EaroEntryT

FuseSupervisionL1 Fuse Supervision L1 UI1 EaroEntryT



IRFHardware IRF Hardware UI1 EaroEntryT

IRFSoftware IRF Software UI1 EaroEntryT

LocationSupervision Location Supervision UI1 EaroEntryT

MainSwitchSupervision Main Switch Supervision UI1 EaroEntryT

MotorNotRunning Motor Not Running UI1 EaroEntryT

MotorStillRunning Motor Still Running UI1 EaroEntryT

NoLoad No Load UI1 EaroEntryT

OperatingHours Operating Hours UI1 EaroEntryT

PhaseFailure Phase Failure UI1 EaroEntryT

PhaseUnbalance Phase Unbalance UI1 EaroEntryT

PowerModuleInsertionCycles Insertion Cycle Supervision MStart UI1 EaroEntryT

PowerModuleSupervision MStart Communication Error UI1 EaroEntryT

PowerModuleSupervision1 MStart Id Number Or Range Error UI1 EaroEntryT

PT100_1CH_LowLevel PT100-1Ch Sensor1 Low Limit UI1 EaroEntryT

PT100_1CH_ShortCircuit PT100-1Ch Sensor1 Short Circuit UI1 EaroEntryT

PT100_1CH_HighLevel PT100-1Ch Sensor1 High Limit UI1 EaroEntryT

PT100_1CH_OpenCircuit PT100-1Ch Sensor Open Circuit UI1 EaroEntryT


1TGC910231M0203 – Release V7.3 59

PT100CardFailure3ch PT100-3Ch Card Failure UI1 EaroEntryT

PT100LowLevel1 PT100-3Ch Sensor1 Low Limit UI1 EaroEntryT

PT100ShortCircuit1 PT100-3Ch Sensor1 Short Circuit UI1 EaroEntryT

PT100HighLevel1 PT100-3Ch Sensor1 High Limit UI1 EaroEntryT

PT100OpenCircuit1 PT100-3Ch Sensor1 Open Circuit UI1 EaroEntryT









PTCsupervision PTC Supervision UI1 EaroEntryT

PTCsupervisionShortCircuit PTC Supervision Short Circuit UI1 EaroEntryT

PTCsupervisionOpenCircuit PTC Supervision Open Circuit UI1 EaroEntryT

Stall Stall Protection UI1 EaroEntryT

StarDeltaTransitionFailed StarDelta Transition Failed UI1 EaroEntryT

StartLimitation Start Limitation UI1 EaroEntryT

SwitchCycleSupervisionK1 Switch Cycle Supervision K1 UI1 EaroEntryT



TestModeFailure Test Mode Failure UI1 EaroEntryT

TOL TOL UI1 EaroEntryT

Underload Underload UI1 EaroEntryT

UnderloadCosPhi Underload CosPhi UI1 EaroEntryT

Undervoltage Undervoltage UI1 EaroEntryT


60 1TGC910231M0203 – Release V7.3

UnexpectedFeederCurrent 5 Unexpected Feeder Current UI1 EaroEntryT

Welded Welded UI1 EaroEntryT

EVENTS1 = event active

0 = event not active

ActuatorBothEndSwitchesActive Actuator Both Limit Switches Active UI1 Bit

ActuatorTorqueClose Actuator Torque Close UI1 Bit

ActuatorTorqueOpen Actuator Torque Open UI1 Bit

CA2ndFieldbus CA Switched to 2nd Fieldbus UI1 Bit

CAHMI CA Switched To Bus-Local UI1 Bit

CALocal CA Switched To Local UI1 Bit

CARemote CA Switched to Remote UI1 Bit

ConfigurationParameterChanged Flash: Configuration Parameter Changed UI1 Bit

FailsafeActivated Failsafe Activated UI1 Bit

MotorStopped Motor Stopped UI1 Bit

MotorStoppedPriority Motor Stopped By Priority Stop UI1 Bit

MotorStoppedRCU Motor Stopped By RCU UI1 Bit

MotorStarted Motor Started UI1 Bit

MotorStartedCCW Motor Started CCW UI1 Bit

MotorStartedCCWRCU Motor Started CCW By RCU UI1 Bit

MotorStartedClose Motor Started Close Direction UI1 Bit

MotorStartedCW Motor Started CW UI1 Bit

MotorStartedCWRCU Motor Started CW By RCU UI1 Bit

MotorStartedN1 Motor Started N1 UI1 Bit

MotorStartedN2 Motor Started N2 UI1 Bit

MotorStartedOpen Motor Started Open Direction UI1 Bit

MotorStartedRCU Motor Started By RCU UI1 Bit

MotorTripped Motor Tripped UI1 Bit

MainSwitchOff Main Switch Off UI1 Bit

5 > MNS iS Release V 5.4


1TGC910231M0203 – Release V7.3 61

(continued)

MainSwitchOn Mainswitch On UI1 Bit

ParameterChanged Flash: Parameter Changed UI1 Bit

SyncSystemClock Time Synchronization O.K. UI1 Bit

TestPositionActivated Test Position Activated UI1 Bit

TestPositionDeactivated Test Position Deactivated UI1 Bit

TimeSyncLost Time Synchronization Lost UI1 Bit

TOLBypassActivated TOL Bypass Activated UI1 Bit

TOLResetLevel TOL Reset Level Reached UI1 Bit

End


62 1TGC910231M0203 – Release V7.3

ComState

The values in this section are available under the description:Name_of_MLink.Name_of_MControl.ComState

The value shown details the current status of the MControl module.


Comment

ComState MControlCommunicationStatus

UI1 Communication status of MControl:

1 => init

2 => initializing

3 => present

4 => not present

5 => offline

MNS iS Interface Manual OPC Server Troubleshooting

1TGC910231M0203 – Release V7.3 63

Troubleshooting

Problem Solution

No access to OPCServer

Use an OPC Explorer (Client software to check if OPC Server is up and runningand providing data). Such an OPC Explorer is available for download fromMatrikon (http://www.matrikon.com/) or from Softing (www.softing.com)

Example Softing (for details refer to Softing software documentation):

1. The tab “OPC Server” displays all available OPC Server (could be more than one, depends on the other software installed on the PC).

The correct server must be selected (ABB MNS iS OPC DA Server), a group is defined automatically.

http://www.matrikon.com/

http://www.softing.com/

Troubleshooting MNS iS Interface Manual OPC Server

64 1TGC910231M0203 – Release V7.3

2. If the server is added to the tree on the left side, from “DA Browse” the items to be displayed can be selected.

The item can be selected and added to the group left.

3. With the tab “DA Items” the current value of the item is displayed dynamically,the proper function can be verified.

Using the OPCExplorer:

1. No MNS iSServer in the list

If the server is not listed, check the proper software installation in”Add/removeprograms”.

2. MLink in thenetwork but no (ornot all) MLink areavailable innamespace.

Check connection between OPC Server PC and MLink; ensure that the MLink isworking with correct device data and that the MLink is shown in OPC Driver tabof MNSiS OPC Server Diagnostic utility.

Check the OPC ID of Server and MLink, both must match.

Check if the network setting of OPC Server (set in Windows ‘Networkconnections’) is matching the network settings of MLink (set in MNavigate IPConfiguration).

COM / DCOMsettings

OPC Server requires correct COM settings in Microsoft Windows operatingsystem. If the OPC Server is not running correctly the DCOM settings should bechecked (see page 29).(Note: any modification requires administrator rights on the PC.)

MNS iS Interface Manual OPC Server Troubleshooting

1TGC910231M0203 – Release V7.3 65

Problem Solution

No access throughthe network to anOPC Server onanother PC

Check if the network configuration is correct; use a ping command to verify thatthe OPC Server PC is reachable. Open a command Windows on the PC:

Start / Run, then type in cmd and click Enter

Enter the ping command with the correct IP address: ping xxx.yyyy.zzz.aaa

If no reply is received, check the cable connection to the PC, router and firewallsettings If a reply is received the connection is ok.

Contact us

ABB Low Voltage SystemsPublication Editor:ABB Automation Products GmbHLadenburg, Germany

Local Contacts onwww.abb.com/mns

Copyright© 2013 ABBAll rights reserved.

Publication No.1TGC910231M0203

mnsis interface manual opc...rcu remote control unit local control unit with pushbutton and...

Documents