Release Notes AdvaSoft for Windows Version 1.3 4

8/10/2019 Release Notes AdvaSoft for Windows Version 1.3 4

http://slidepdf.com/reader/full/release-notes-advasoft-for-windows-version-13-4 1/38

Advant® OCS

AdvaSoft™ for WindowsVersion1.3/4

Release Notes

3BSE011611D0005



3BSE011611D0005

3 B S E 0 0 1 2 6 4 / C



AdvaSoft for Windows Table of Contents

3BSE011611D0005 iii

Chapter 1 - Introduction

1.1 Executive Summary................................................................................................. 1-1

1.2 How to Use This Document..................................................................................... 1-1

1.3 Version Designation................................................................................................. 1-1

1.4 Revision Record....................................................................................................... 1-2

1.5 Compatibility........................................................................................................... 1-3

1.6 Restrictions .............................................................................................................. 1-4

1.6.1 AdvaCommand for Windows ................................................................. 1-4

1.6.2 Advant Fieldbus 100 Interface................................................................ 1-4

1.6.3 GCOM Interface ..................................................................................... 1-5

1.6.4 SQL*Net TCP/IP for Windows .............................................................. 1-5

1.7 Related Documentation............................................................................................ 1-5

Chapter 2 - Functionality

2.1 New Functions......................................................................................................... 2-12.1.1 AF 100 Interface ..................................................................................... 2-1

2.1.2 GCOM Interface ..................................................................................... 2-1

2.1.3 AdvaCommand....................................................................................... 2-1

2.2 Corrected Errors....................................................................................................... 2-2

2.2.1 AdvaCommand....................................................................................... 2-2

2.2.2 AF100 Interface...................................................................................... 2-2

2.2.3 GCOM .................................................................................................... 2-3

2.3 Known Problems and Work Arounds ...................................................................... 2-3

2.3.1 AdvaSoft Basic Unit............................................................................... 2-3

2.3.2 AdvaCommand for Windows ................................................................. 2-3

2.3.2.1 AdvaCommand for Windows User’s Guides................... 2-4

2.3.3 Advant Fieldbus 100 Interface................................................................ 2-6

2.3.3.1 AF100 Interface User’s Guide ......................................... 2-7

2.3.4 GCOM Interface ..................................................................................... 2-8

2.3.4.1 GCOM Interface Advasoft for Windows User’s Guides2-10

2.3.5 AdvaInform DDE Server ...................................................................... 2-10

2.4 Recommendations...................................................................................................2-11

2.4.1 AdvaSoft Basic Unit ............................................................................. 2-12

2.4.1.1 User API......................................................................... 2-12

2.4.2 AdvaCommand for Windows ............................................................... 2-132.4.3 Advant Fieldbus 100 Interface.............................................................. 2-13

2.4.4 GCOM Interface ................................................................................... 2-14

2.4.5 SQL*Net TCP/IP for Windows ............................................................ 2-15

Chapter 3 - Installation

Copyright © ABB Automation Products AB August 25,




iv 3BSE011611D0005

3.1 Initial Installation.....................................................................................................3-1

3.2 Upgrading................................................................................................................. 3-2

3.3 Backup and Restore.................................................................................................. 3-3

Chapter 4 - Miscellaneous4.1 Capacity and Performance ....................................................................................... 4-1

4.2 How to modify the MV table in MP200 and AC400...............................................4-4

4.2.1 How to correct the MV table................................................................... 4-4

4.2.1.1 Normal way ...................................................................... 4-4

4.2.1.2 Using OnLine Builder from an AS 500 OS in a system with 16

or 32 entries (MP200/1 SW*5.0 and later).......................4-4

4.2.1.3 Using MA215 ................................................................... 4-4

4.2.2 Using System and Database Maintenance (or Expert commands) and TP014-

5

4.2.2.1 System with 8 entries (MP200/1 SW*4.0 and earlier).....4-5

4.2.2.2 System with 16 or 32 entries (MP200/1 SW*5.0 and later)4-6




3BSE011611D0005 v

TABLES

Table 1-1. Version Designation...................................................................................... 1-1

Table 1-2. Actual Revisions........................................................................................... 1-2

Table 1-3. Price List and Product guide......................................................................... 1-5

Table 1-4. Valid Manuals............................................................................................... 1-5

Table 1-5. AdvaCommand Development Documentation Binder................................. 1-6

Table 1-6. AdvaCommand Runtime Documentation Binder ........................................ 1-6

Table 2-1. AdvaCommand predefined dynamos ........................................................... 2-5

Table 2-2. Supported operations for DAT Based objects and Extended DB Elements . 2-6

Table 2-3. Configuration on AF 100.............................................................................2-11

Table 2-4. Recommended system configuration on GCOM ........................................2-11

Table 2-5. Recommended system configuration on SQL*Net TCP/IP....................... 2-12

Table 3-1. Installation Descriptions for Options............................................................ 3-1




3BSE011611D0005 vi

ILLUSTRATIONS

Figure 2-1. Sending time tagged events via AC 450 transit node................................... 2-9

Figure 2-2. Subscription cycle time .............................................................................. 2-13

Figure 2-3. Sending time tagged events via AC 110 transit station .............................. 2-14

Figure 4-1. Display exchange time performance of AdvaCommand and GCOM.......... 4-1

Figure 4-2. Display exchange time performance of AdvaCommand and AF 100 with DAT

Based objects ................................................................................................ 4-2

Figure 4-3. Display exchange time performance of AdvaCommand and AF 100 with

Extended DB Elements................................................................................. 4-3



AdvaSoft for Windows Section 1.1 Executive Summary

3BSE011611D0005 1-1

Chapter 1 Introduction

1.1 Executive SummaryAdvaSoft for Windows is the Advant OCS platform software product for applications using

IBM-compatible personal computers under Microsoft Windows.

AdvaSoft for Windows includes AdvaInform for Windows (information management)

functionality, AdvaCommand for Windows (operator interaction) functionality, AdvaBuild for

Windows (engineering) functionality and basic functions. AdvaSoft for Windows is packaged

as a basic unit with options available separately.

If you already have installed AdvaSoft version 1.x/x, make sure that you have backup data

saved before you start the new installation, see Chapter 3 Installation.

If you intend to use the Advant Fieldbus 100 Interface together with a previously installed

AdvaBuild for Windows version, please make sure that you have AdvaBuild for Windowsversion 1.3/1 or later (FCB 4.3/1, BCB 2.3 and APB 2.3).

1.2 How to Use This Document

These Release Notes give you advice when installing and using the product AdvaSoft for

Windows Version 1.3/4. It also describes known problems for the product.

Read this document before you install the software on your PC.

Compatibility with other Advant OCS products and restrictions in functionality is listed in this

chapter.

Chapter 2 describes new functions in AdvaSoft for Windows version 1.3. Chapter 2 also

describes known problems and workarounds and recommendations regarding the use of the

product.

In Chapter 3 you will find information regarding installation and upgrading of AdvaSoft for

Windows.

Chapter 4 includes some performance figures not included in the User’s Guide, and informationhow to modify the MasterView table.

1.3 Version Designation

The AdvaSoft for Windows Version 1.3/4 consists of a Basic Unit and a number of Options.

Table 1-1. Version Designation

Product/Option Ordering No. Actual revision Release Date

Basic Unit(1) 3BSE012023R4 1.3/4 September 2000

AdvaCommand Development(2) 3BSE012024R3 1.3/0 98-05-08



AdvaSoft for Windows Section 1.4 Revision Record

3BSE011611D0005 1-2

1.4 Revision Record

AdvaCommand Runtime 3BSE012025R3 1.3/0 98-05-08

AdvaCommand Development with FIXdatabase(2)

3BSE012028R3 1.3/0 98-05-08

AdvaCommand Runtime with FIX data-base

3BSE012029R3 1.3/0 98-05-08

AdvaInform DDE Server 3BSE005803R5 1.0/4 97-06-09

SQL*Net TCP/IP(3) (4) 3BSE008943R1 2.0/0 96-02-26

AdvaBuild for WindowsAC 110/70/55(5), (7)

Refer to Advant Engineering Products/Win3.11 price list.

AF 100 Interface, Single Coaxial bus

cable(6)

3BSE012032R3 1.2/3 Sep, 2000

AF 100 Interface, Redundant Coaxial buscable

3BSE012033R3 1.2/3 Sep, 2000

AF 100 Interface, Single Twisted pair buscable

3BSE012030R3 1.2/3 Sep, 2000

AF 100 Interface, Redundant Twisted

pair

3BSE012031R3 1.2/3 Sep, 2000

GCOM Interface(7) 3BSE012695R4 1.1/3 Sep, 2000

(1) Must always be ordered

(2) AdvaCommand development also includes runtime functionality

(3) Standard TCP/IP software is not included

(4) Not available in AdvaSoft for Windows 1.3/0.

(5) Advant Controller 55 via RCOM is not supported

(6) AF 100 with coaxial bus cable is not supported by AC 70. AC 70 only supports twisted pair bus cable.

(7) Requires an IEEE 802.3 communication board with NDIS Interface support. This board is not included

Table 1-2. Actual Revisions

Revision Release Date Status Report

AdvaSoft for Windows 1.0/0 95-03-07 SR 5025

AdvaSoft for Windows 1.0/1 95-07-14 SR 5025/1


AdvaSoft for Windows 1.1/0 96-02-26 SR 6010

Table 1-1. Version Designation

Product/Option Ordering No. Actual revision Release Date



AdvaSoft for Windows Section 1.5 Compatibility

3BSE011611D0005 1-3

1.5 Compatibility

Following option versions are compatible with Basic Unit 1.3/4.

The AdvaSoft for Windows 1.3/4 can operate with the following ABB Advant OCS products on

the Advant Fieldbus 100 network:

• Advant Controller 110 with Master software version 2.0 or later, except for AC 110*2.0/2.Version 2.0 only supports for DAT based objects.Recommended version 2.0/5 or later.

• Advant Controller 110 with Master software version 2.1 or later.Support for both Extended Database elements and DAT based objects.

Recommended version 2.1/2 or later.• Advant Controller 410 with Master software version 1.0 or later.

• Advant Controller 450 with Master software version 1.0 or later.

• Advant Controller 160 version 1.0 or later.

• Advant Controller 70 version 1.0 or later. Recommended version 1.1/2.


AdvaSoft for Windows 1.2/0 96-12-15 SR6078/0

AdvaSoft for Windows 1.3/0 97-06-09 SR7029




AdvaSoft for Windows 1.3/4 September, 2000 SR7029/4

Option Actual revision

AdvaCommand 1.2, 1.3/0

AdvaInform DDE Server 1.0/4

SQL*Net TCP/IP 2.0/0

AdvaBuild for WindowsAC 110/70/55

1.3, 1.4(1), 1.5(1)

(1) Not verified in Product Type Test

AF 100 Interface 1.2/0, 1.2/1, 1.2/2, 1.2/3

GCOM Interface 1.1/0, 1.1/1 1.1/2 1.1/3

Table 1-2. Actual Revisions

Revision Release Date Status Report



AdvaSoft for Windows Section 1.6 Restrictions

3BSE011611D0005 1-4

On the TCP/IP network the following ABB products are supported:

• Advant Station 500 Series IMS with Master software version 1.2 or later. See also chapter1.6.4.

• Advant Station 500 Series IMS with MOD 300 software version 1.2 or later. See alsochapter 1.6.4.

On the GCOM network:

• MasterGate 230/1

• MasterPiece 200/1 with software version 5.0 or later

• Advant Controller 450 with Master software version 1.0 or later

1.6 Restrictions

1.6.1 AdvaCommand for Windows

• If you intend to use the predefined Excel Report macros for AdvaCommand you must usean english version of Excel.

• Dynamos and dialogs for DAT objects are not included.

• The predefined dynamos for the Advant OCS system process objects can not be used forpresentation of data from the FIX database.

• Data from the Advant Fieldbus 100 network and from the GCOM network is accessedfrom AdvaCommand via the AdvaInform User API. Advant Fieldbus 100 and GCOM datais not directly available in the FIX database. To operate with Advant Fieldbus 100 orGCOM data you must build a separate application (FIX DDE Server or FIX Easy DatabaseAccess (EDA)) that copies the data to the FIX database or make a script in View.

• You can not mix objects created with ABB dynamos from AdvaCommand for Windowsversion 1.0 with objects created with the new ABB dynamos from AdvaCommand forWindows version 1.3, in the same display. The dynamos in AdvaCommand for Windows1.1, 1.2 and 1.3 are used in the same way. See also description of installation in Chapter 3Installation.

1.6.2 Advant Fieldbus 100 Interface

• The AdvaSoft for Windows Advant Fieldbus 100 interface supports only the functions fordata subscription and commands using sending Data Set Peripherals towards AC 410 andAC 450 nodes. The AC 410 and AC 450 does not have any sending Event Sets (EVS-S).

• You must have the CI526 board to have the clock synchronization in slave mode.

• The AdvaSoft for Windows Advant Fieldbus 100 Interface can only communicate with



AdvaSoft for Windows Section 1.6.3 GCOM Interface

3BSE011611D0005 1-5

stations configured on the same bus number. Also only one bus number is supported but

this number is configurable.

• If EV_STAT is set to 0 for an object, no ACKNOWLEDGE event is sent from thecontroller, when the alarm is acknowledged. Consequently, AdvaSoft does not notice thatthe alarm of the object has been acknowledged.

1.6.3 GCOM Interface

• The clock synchronization in the GCOM Interface does not support high precision clocksynchronization.

• Subscription of data from AS 500 Series IMS does not work.

• There is no time-out supervision on object select in GCOM.

1.6.4 SQL*Net TCP/IP for Windows

• You can not write data to the AS 500IMS from a process display in AdvaCommand, i.e.the SQL command UPDATE can not be used.

• You can not collect historical data to AdvaCommand from AdvaInform 2.0/0. TheNUMCONFIG view is not supported in AdvaInform 2.0/0.

1.7 Related Documentation

.

Table 1-3. Price List and Product guide

Document Ordering/Id. No.

Advant OCS Product Guide 3BSE008434R0401

AdvaSoft for Windows Price List 3BSE007595/H

Table 1-4. Valid Manuals

Document Ordering No.

AdvaSoft for Windows 3BSE006236R0301

AdvaCommand DevelopmentAdvaCommand RuntimeAdvaCommand for Windows

3BSE006237R0201

AdvaCommand DevelopmentDocumentation Binder

3BSE006221R0101



AdvaSoft for Windows Section 1.7 Related Documentation

3BSE011611D0005 1-6

The User’s Guides included in AdvaCommand development and runtime documentationbinders are also available as separate documents. See below.

AdvaCommand Runtime

Documentation Binder

3BSE006226R0201

AdvaCommand for Windows Database Builder 3BSE008229R0001

AdvaCommand for Windows Database Reference 3BSE008230R0001

AdvaCommand for Windows, Upgrade 3BSE012036R0001

SQL*Net TCP/IPAdvaSoft for Windows

3BSE006239R0101

Advant Fieldbus 100 InterfaceAdvaSoft for Windows

3BSE006238R0201

Advant Fieldbus 100 3BSE000506R0701

GCOM InterfaceAdvaSoft for Windows

3BSE008227R0101

AdvaBuild for Windows Application Builder 3BSE007031R0301

AdvaBuild for Windows Function Chart Builder 3BSE007149R0401

Table 1-5. AdvaCommand Development Documentation Binder

Document Ordering No.AdvaCommand for Windows Draw 3BSE006222R0101

AdvaCommand for Windows Macro Editor 3BSE006223R0101

AdvaCommand for Windows Command Language 3BSE006224R0101

AdvaCommand for Windows Tag Group Editor 3BSE006225R0101

Table 1-6. AdvaCommand Runtime Documentation Binder


AdvaCommand for Windows Environment Setup 3BSE006227R0101

AdvaCommand for Windows Network 3BSE006228R0101

AdvaCommand for Windows System Configuration 3BSE006229R0101

AdvaCommand for Windows Alarming and Messaging 3BSE006230R0101

Table 1-4. Valid Manuals




AdvaSoft for Windows Section 1.7 Related Documentation

3BSE011611D0005 1-7

AdvaCommand for Windows Security 3BSE006231R0101

AdvaCommand for Windows Historical Trending 3BSE006233R0101

AdvaCommand for Windows View 3BSE006234R0101

AdvaCommand for Windows DDE Support 3BSE006235R0101

AdvaCommand for Windows Upgrade 3BSE012036R0001

Table 1-6. AdvaCommand Runtime Documentation Binder




AdvaSoft for Windows Section 2.1 New Functions

3BSE011611D0005 2-1

Chapter 2 Functionality

2.1 New FunctionsThis chapter describes functions added since AdvaSoft for Windows version 1.2.

2.1.1 AF 100 Interface

• Support for both Extended Database (XDB) elements and DAT based objects. (Previousversion only supported DAT based objects.). The Extended DB element group offers amore complete object type support with a simplified configuration compared with the DATbased object. AI, AO, DI and DO objects are supported as Extended DB elements. TheXDB are only supported in AC110 2.1 and AC160.

• Support for clock synchronization in slave mode (only if you have the CI526 board).

• Improved status supervision.

• Application Version Control. This function ensure that on- and off-line changes, done withAdvaBuild in the controllers is automatically reflected to the AdvaSoft station.

• Support for AC 160 with multiple CPU units.


With the GCOM communication you have access to the TTD (Time Tagged Data) logs in theAC 400 Series and MP 200/1 controllers. TTD logs can be accessed via the AdvaInform UserAPI.

2.1.3 AdvaCommand

AdvaCommand 1.3 is based on FIX 5.65 (year 2000 compliant). Previous FIX 5.6

• Improvements to Draw/View compared with AdvaCommand 1.1 (FIX 5.5) are:

– Picture compatibility with FIX for Windows NT and Windows 95.

– A new Command Language Editor

– Off disk picture read performance

– Right Mouse Button support

– New Picture Types functionality– Saving color threshold and grid settings

• Change in AdvaCommand 1.3 ABB Close up display

The command on opening script in the ABB Close up display includes the RESOLVEVARcommand. This command will ensure correct update of the status information. The statusinformation has an indirect reference to data. When the RESOLVEVAR command is



AdvaSoft for Windows Section 2.2 Corrected Errors

3BSE011611D0005 2-2

executed it goes out, gets the data and puts it in the variable instead of leaving it as an

indirect reference.

2.2 Corrected Errors

This chapter describes problems fixed since version 1.2/0.

The AdvaSoft for Windows *1.3/2 is Year 2000 compliant.

2.2.1 AdvaCommand

• Alarms could disappear from Alarm Summary if the alarm condition was very short. (I.e.an object goes to an alarm state but back to normal within a second). This would onlyoccur after a restart of AdvaCommand and an alarm is generated before the object hasbeen displayed in a process display. Corrected in AdvaCommand *1.2/0.

• If an alarm left the signal error state the object could be incorrectly set to normal even ifthe object was still in an other alarm state. Corrected in AdvaCommand *1.2/0.

• Minor corrections in the DO function keys display. Corrected in AdvaCommand* 1.2/0.

• AdvaCommand for Windows 1.2/0 could not provide a graphical SQL user interface forAdvant Station 500 Series IMS, i.e. the SQL*Net option could not be used together withAdvaCommand for Windows. Corrected in AdvaCommand*1.2/1.

• If you were using AdvaCommand in a FIX network configuration, it was not possible torun the FIX View application in the node connected to the ABB network (AF100 andGCOM). Commands towards objects from this node could result in an error message boxwith the text “Invalid handle passed”. For the View client nodes the problem did not occur.The problem did also not occur in a FIX standalone configuration, but you could also havethe “invalid handle passed” problem described above if you used a configuration withSQL*Net TCP/IP together with the AF 100 Interface or the GCOM Interface.Also described in SR7083. Corrected in AdvaCommand*1.3/0.

• It has not been possible to use the search and replace utility in Draw on the AdvaSoft forWindows dynamos, due to the use of a string variable for the object name. The newdynamos in AdvaCommand 1.3 does not use the string variable.

2.2.2 AF100 Interface

• It has not been possible to perform acknowledge of DAT based objects between twoAdvaSoft stations.Corrected in AF100 Interface*1.2/1.

• DAT based DI/DO could only be configured to generate alarms.Corrected in AF100 Interface*1.2/1.

• The time synchronization did not work as expected when the power supply wasdisconnected from a modem TC513 on the bus.Corrected in AF100 Interface*1.2/1.

• The status bit for cable 1 was incorrectly set when cable 2 failed.Corrected in AF100 Interface*1.2/1.



AdvaSoft for Windows Section 2.2.3 GCOM

3BSE011611D0005 2-3

• The redundant line support flag was in certain situations, incorrectly read as no even if setto yes in the coil0000.c00.Corrected in AF100 Interface*1.2/1.

• If a DAT based DI object with normal value =1 went into alarm state, i.e. value=0, whenAdvaSoft for Windows had been restarted, the alarm was not sent to the client application,until the next time an alarm was generated on that object.Corrected in AF100 Interface*1.2/1.

• Namelenghts of CI and PM DB elements could not be longer than 10 characters.Corrected in AF100 Interface*1.2/2.

• The CPU position could not be greater than 6.Corrected in AF100 Interface*1.2/2.

• Events stopped coming and commands could not be sent to the controller in certainsituations, as a SCADA configuration with configuration errors and high load.Corrected in AF100 Interface*1.2/2.

• If a DAT DI or DIS object with normal value =1 went into normal state, i.e. value=1, when

AdvaSoft for Windows had been restarted, the alarm was not reported to the AlarmHistory until the next time an event was generated on that object.Corrected in AF100 Interface*1.2/3.

2.2.3 GCOM

• It was a bad time stamp in Alarm Summary on events/alarms coming from GCOM.The rightmost three digits were wrong.Corrected in GCOM Interface*1.1/1.

• The swedish characters åÅäÄöÖ were not presented correctly in the description attribute.Corrected in GCOM Interface*1.2/2.

NOTE

For swedish signs set Language=2 in the[GCOMProfile] section of theAdvaSoft.ini file.

• When setting the time in a Masterbus 300 network to 2000-02-29, the AdvaSoft forWindows did not accept time synchronization through GCOM.Corrected in GCOM Interface*1.1/2.

2.3 Known Problems and Work Arounds

2.3.1 AdvaSoft Basic Unit• The installed options in the AdvaSoft station are listed in the ADVASOFT.INI file (resides

in the MS-Windows directory). If you remove the installation of the AdvaCommandand/or the SQL*Net for TCP/IP option you must manually update the list of installedoptions in ADVASOFT.INI file, otherwise you will have wrong information when youcheck installed options from the AdvaSoft Main Window.



AdvaSoft for Windows Section 2.3.2 AdvaCommand for Windows

3BSE011611D0005 2-4


• In cases where you use a Command script to update AI or AO objects, please note thefollowing:Do not try to set the value above the Range Max or below the Range Min. If you set

the value out of range, the result of the operation will be unpredictable. The sameproblem will occur if you try to set a value larger than 99999.99 or if you try to use

more than 7 significant figures.

• If you use a Tag with ‘;’ in the Tag string (for example in AdvaCommand HistoricalAssign, HTA) and refer to this tag in an Excel report the ‘;’ will be treated as new columnand the layout of the report will not be OK.

You can select the separator used when defining subscription cycle time for a Tag. Defaultis ‘;’ used as separator. You select the separator in the ADVASOFT.INI file (residing in theMS-Windows directory). Change the parameter ‘SubsSeparator’ in the [Communication]

section.

• AdvaCommand must always be restarted if you have changed object type, with the AF 100Object Configuration Tool, for a previously used object. For example DAT changed to AIwith the Object configuration tool.

• Objects that are in alarm state before start-up of AdvaCommand may not be presented inthe AdvaCommand Alarm List.

• Do not use more than 800 dynamic links in a process display. If you have a display withmore than 800 dynamic links you will have an unpredictable behavior of the system. Youcan’t copy dynamos in the display etc. See also Chapter 2.3.2.1 below.

• An object in a process display is indicated as selected with a white frame. Sometime is thisframe marked even though the object isn’t selected.

• Default network is NetBeui. If you uses TCP/IP and want to enable the network after

installation, use the program C:\WDMACS\PROTCFG.EXE to change current protocol.• If an object has left alarm state, went to normal state and been acknowledged, the next time

the object goes into alarm state the time is incorrectly set to the old time in AlarmSummary. The problem does not occur if you have an active subscription for the object.You can circumvent the problem by making the topline link for the Alarm Summary aslarge as the Alarm Summary window and keep it in the background. I.e. edit the display_TOPLINE with Draw.

2.3.2.1 AdvaCommand for Windows User’s Guides

• AdvaCommand RuntimeAdvaCommand DevelopmentAdvaCommand for Windows3BSE 006 237R0201

– To be able to install the FIX DDE Driver or other I/O Drivers check the following




3BSE011611D0005 2-5

option.

– The performance figures is not included for the GCOM Interface. Performancefigures are included in Chapter 4 in this document.

– You can use maximum 800 dynamic links in each process display. In the User´sGuide are the number of links in the ABB dynamos (display elements) not specified.A standard link to access the value will use two dynamic links for update. To verifythe number of dynamic links used in a display press <Ctrl>+<Shift>+L within theDraw application. This will pop up a message box with a number for “Active links”which reflects the number of dynamic links used in the display. The Table 2-1 belowshows the number of dynamic links in the predefined dynamos in the ABB dynamosets (ABBAIDE, ABBAODE, ABBDIDE and ABBDODE).

Table 2-1. AdvaCommand predefined dynamos

Dynamo name Description Number of links

AIPD01 Analog Input signal value 8

AIPD51 Analog Input signal bar graph 7

AIGR01 Analog Input signal group display 15

AOPD01 Analog Output signal value 7

AOPD51 Analog Output signal bar graph 5

AOGR01 Analog Output signal group display 11

DIPD01 Digital Input signal value (rectangle) 7

DIGR01 Digital Input signal group display 11

DOPD01 Digital Output signal value (rectangle) 5

DOGR01 Digital Output signal group display 8

FIX Software Options

Report Generator

Sample System

FIX Support

Historical Trending

Database Access Toolkit(s)

Please select the options to install.

Recipe Package

I/O Drivers

Diagnostics

QuickStart Tutorial

Option Diskettes

Update Diskettes

OK Cancel

Select this option toinstall the driver



AdvaSoft for Windows Section 2.3.3 Advant Fieldbus 100 Interface

3BSE011611D0005 2-6

– The predefined dynamos for the Advant OCS system process objects can not be usedfor presentation of data from the FIX database. Some of the Advant OCS objectattributes have no corresponding FIX field name.

• The Dialog Button Sets are designed to cover the functionality you have if you operate onprocess objects via the GCOM Interface.Table 2-2 shows supported commands via the Advant Fieldbus 100 Interface for DATBased objects (AI, AO, DI, DO and DAT) and for Extended DB Elements (AIS, AOS,DIS, DOS, DAT, MR, MB, MI and ML).

– You can use your old displays created with ABB dynamos from AdvaCommand forWindows version 1.0. The new dialogues in AdvaCommand for Windows version 1.3can be used both for old and new displays. Do not mix objects created with ABBdynamos from AdvaCommand for Windows version 1.0 with objects created with thenew ABB dynamos from AdvaCommand for Windows version 1.3 (1.1, 1.2), in thesame display. See also description of installation in Chapter 3

2.3.3 Advant Fieldbus 100 Interface• Start of the CI525/CI526 communication board sometimes fails and you have an Error

message ‘Failed to configure board ’. In these cases you must reset the CI525/CI526 board.This is made by Power off the PC and wait some seconds. Thereafter you can try to restartagain. After one or two restarts, the CI525/CI526 board will start.

• If the AdvaSoft station is configured as clock master, the clock master functionality can

Table 2-2. Supported operations for DAT Based objects and Extended DB Elements

Operation AI/AIS AO/AOS DI/DIS DO/DOS DAT(1)

(1) The object types MR, MB, MI and ML supports the same commands as the DAT object.

Select/Deselect(2)

(2) The command is only handled locally in the AdvaSoft for Windows Station, i.e. no information is sent

to the Advant Controller 110/70.

yes yes yes yes no

Block/Deblock Print(2) yes no yes no no

Block/Deblock Alarm(3)

(3) For DAT Based objects the command is only handled locally in the AdvaSoft for Windows Station,i.e. no information is sent to the Advant Controller 110/70.

yes no yes no no

Block/Deblock Input(3) yes no yes no no

Block/Deblock Output no no no no no

Man/Auto no no/yes no no/yes no

Change Value yes yes yes yes yes

Change Alarm Limit no/yes no no no no

Acknowledge Alarm(4)

(4) For DAT Based objects the Acknowledge signal is only sent to other AdvaSoft for Windows Stations

on the same Advant Fieldbus 100 bus.

yes yes yes yes no



AdvaSoft for Windows Section 2.3.3 Advant Fieldbus 100 Interface

3BSE011611D0005 2-7

not be guaranteed if a DOS application is started from Windows.

• In clock master mode a synchronization signal must be sent cyclically every second. Thecycle time for the synchronization from the AdvaSoft station is not always 1 second. This

jitter in the cycle time will result in error indications on the DI65x element in the AC 110.

• To disable the clock master function in a station with a CI525 board (corrected for CI526)previously defined as clock master you must do the following:

a. Click the Config... item from the AF100 Communication program Control menu toopen the CI525 Configuration dialog box. ‘Time synchronization = Off.

b. Reconfigure the CI525 board by clicking the Disconnect button followed by theConnect button.

The AF 100 Object Configuration Tool can maximum handle 2730 Event Channels if youuse Event Channel names with maximum length (20 characters). If you need to configuremore Event channels, use shorter names or use the default name. Note also therecommendations regarding number of Event Sets on the AF 100 bus Table 2-3.

• When using the disconnect button to disconnect a time master node, no error messages aresent to the slave PCs and the disconnected time master node continues to send time syncs.To disconnect a time master you must power off the PC.

• If you in runtime change an objects event communication from NONE to SEND (in FCB)AdvaSoft for Windows will not invoke this change until it has been restarted.

• Use only EVS identities with ident numbers smaller than 256. EVS identities with identnumbers greater than 255 are not enabled from the AdvaSoft.

• When you use 2 Byte DAT objects, the scaling factor 100 and 1000 do not work asexpected. The scaling factor 100 incorrectly functions as 0.1 and the scaling factor 1000 as0.01.

• When you use 2 Byte DAT objects, use receiving DSP in the controller, to get correct

mapping of data in the DAT.

2.3.3.1 AF100 Interface User’s Guide

• Advant Fieldbus 100 Interface3BSE006238R0201

– Set InterruptSupervise= On in the ADVASOFT.INI file to enable a pollingmechanism, if the IRQ mechanism of handling the CI526V01 board fails in the PC.If you have problems sending commands or receiving events you might need toactivate the polling mechanism. To find out if you need the polling mechanism, startthe trace by selecting the AF100 icon and press <Ctrl-T>. Check the standard checkbox in the AF100-Trace activation dialog box, and press OK. Select the CI statusfrom the AF100 popup menu. If the ISA IRQ Request <>0 the IRQ mechanism is notworking properly.Do not forget to stop the trace when not needed.

– Service Data Protocol communication failure may result in different error messages.The most common are:




3BSE011611D0005 2-8

* XIOBb_commTimeout -

The problem may occur due to temporary overload in the remote station. If however

XIOBb_commTimeout is returned for all SDP messages (i.e. all commands, all EVS

messages etc.) it could be that the AF100 software has lost the interrupt from the

CI526 board. In this case power off and on the PC (to make a hardware reset the

CI526 board) and enable the interrupt supervise for the AF100 software by typingInterruptSupervise=On in the ADVASOFT.INI file

* XIOBa_portTimeout -

The problem may occur due to temporary overload of the CI526 board.

*XIOBa_commTimeout -

The problem may occur due to temporary synchronization problems with the CI526

board.

– The following correction is needed in the AF100 Interface User’s Guide Appendix B-Object Attributes and Commands, page B-5 and B-6.

* OUTP_BLK is not supported for extended DB Elements.


• If you have objects configured with event treat = 2, the text in Alarm History will not bethe same as in the Event list for the Advant Station 500 OS. The Alarm History shows boththe ‘Alarm’ and ‘Normal’ state and the Event list in the OS only shows the ‘Alarm’ state.

• Time tagged events from the AF 100 network are sent to the database elements DIEV andAIEV in the AC 450. The DIEV and AIEV database elements sends the alarms to theAdvaSoft station via the GCOM Interface. From the AdvaSoft station Acknowledge ofAIEV/DIEV Alarms in the AC 450 node doesn’t work if you don’t have a MasterBus 300network connected to the AC 450. I.e. in a configuration shown in Figure 2-1, you can’t




3BSE011611D0005 2-9

acknowledge DIEV/AIEV alarms.

• If AdvaSoft for Windows is the only operator station in a network with AC400/MP200controllers, it needs to update the AL_UNACK bit for AI and DI database elements. TheAL_UNACK bit indicates that an unacknowledged alarm exists in the database element.The AdvaSoft for Windows unacknowledge function is by default disabled and it isactivated by adding following to the AdvaSoft.ini:

[AdvaCommand]SetUnAck=TRUE

• Historical Collect with GCOM must be started 2 times within 30 seconds to work.

• To be able to acknowledge alarms, set ERR_TR > 0 in the AI, AIC DI, DIC databaseelements.If set to 0, it is not possible to acknowledge alarms.

• Tracking of Block/Deblock events is only activated by adding the following profile to theAdvaSoft.ini file:

[GCOMProfile]

OperatorTreat=1

See the GCOM Interface AdvaSoft for Windows User’s Guide, for more details.

• The GCOM (CI543) does not work with slave number 7 or 8 on CS513 when used withAC410/450 1.3/3 or older with a few exceptions. See SR7069 for more details.

• If you do not get alarms from objects in the controllers this may be caused by theMasterView table of the controller not being updated.If you have this problem, try the following measures:

Figure 2-1. Sending time tagged events via AC 450 transit node

ASfW

AC 450

AC 110

GCOM

AF 100

)

AC 110



AdvaSoft for Windows Section 2.3.5 AdvaInform DDE Server

3BSE011611D0005 2-10

– update the table by choosing “Force NODE INIT signal” from the GCOM-menu

or

– start GCOM before you start AdvaCommand

2.3.4.1 GCOM Interface Advasoft for Windows User’s Guides• 3BSE 008 227R0101

The Section 3.5.2 states that only MasterGate 230/1 can act as transit node. This is not correct,also Advant Controller 450 and MasterPiece 200/1 can be transit nodes.

The Section 1.8.1.2, Table 1-2 states that System Status is a supported AdvaInform User APIfunction. This is not correct.

2.3.5 AdvaInform DDE Server

• If you try to shut down Windows with a Client application connected to the DDE Server

you sometimes will have an uncontrolled shutdown of Windows. To avoid this close theClient Application before you shutdown Windows.

• The AdvaInform DDE Server doesn’t indicate lost communication to the clientapplication. The last updated value is just frozen. If you restart your client application youwill have indication of lost communication.

Switch To...

Resolve

Reset DiagnosticsConfigure...

Status...

Force NODE INIT signal

Help...

About...

More...

Ctrl+Esc

Select thisoption



AdvaSoft for Windows Section 2.4 Recommendations

3BSE011611D0005 2-11

2.4 Recommendations

The Table 2-3 gives configuration guidelines when AdvaSoft for Windows is used on the

Advant Fieldbus 100 network.

One AdvaSoft for Windows can handle up to 15 Advant Controllers 110/70.

One Advant Fieldbus 100 bus (coax cable) can have up to 80 nodes connected. On Advant

Fieldbus 100 with twisted pair up to 32 nodes are possible per segment, several segments may

be connected via modems to handle up to 80 nodes.

One AC110, AC 70 can communicate with up to 10 AdvaSoft for Windows or Advant

Controller 400 Series nodes simultaneously.

Always when the system is configured the bus load on the Advant Fieldbus 100 must be

checked. See Advant Fieldbus 100 User’s Guide.

The Table 2-4 shows recommended configuration when AdvaSoft for Windows is used on theGCOM network

Table 2-3. Configuration on AF 100

Maximum recommendedconfiguration

Number of AdvaSoft forWindows

≤10

Number of objects onAF 100

≤5000

Number of Event Sets onAF100

≤50

Event message rate(EVS-S/second)

≤2

Table 2-4. Recommended system configuration on GCOM


Number of AdvaSoft forWindows stations

≤4

Number of transit nodes (1)

(1) Node handling transit between GCOM and MasterBus.

MG 230/1, AC 450 or MP 200/1 can be used as transit node

1

Total number ofmessages/second(2)

≤50

Event message rate(Time taggedEvents/second)

≤10



AdvaSoft for Windows Section 2.4.1 AdvaSoft Basic Unit

3BSE011611D0005 2-12

NOTE

The number of nodes on the plant network, that can have cyclic subscription for

data in a control network, is limited in the MasterGate 230/1. Default you can

have 4 nodes with cyclic subscription.

Do not use AdvaSoft on the plant network if you have more than 4 node on the

plant network with cyclic subscription. The MasterGate will convert the cyclic

subscription to demand subscription. This will cause extra load in the control

network because the AdvaSoft Station will repeat the subscription request if not a

cyclic response is received.

The Table 2-3 shows recommended configuration when AdvaSoft for Windows is used as an

Oracle Client towards an AS 500 IMS Server node on the TCP/IP network.

NOTE

From a process display in AdvaCommand you can only read data from the

AS 500 IMS.

2.4.1 AdvaSoft Basic Unit

2.4.1.1 User API

• The cycle time you define as subscription cycle time will not include the time needed by

(2) Example of messages are:

-One order signal

-Data subscription request with 1-16 objects

-Answer on data subscription which can contain 1-48 objects

depending of object type and access type.

Valid if MG 230/1 is used as transit node. If you use AC 450 or

MP 200/1 with high CPU load as transit nodes the message rate willbe reduced

Table 2-5. Recommended system configuration on SQL*Net TCP/IP


Number of AdvaSoft forWindows stations

≤4

Number of AS 500IMSServer nodes

1




3BSE011611D0005 2-13

the communication interface to execute the command. See Figure 2-2


• If you want to use the Dynamo Sets delivered with the standard FIX product you will findthem in directory C:\WDMACS\PIC. The ABB Dynamo Sets resides in directory

C:\WDMACS\PIC\ABBPIC.• In cases where you use maximum monitor resolution (1280*1024) we recommend you to

use >16 MB Primary Memory. In most cases16 MB memory is enough, but with somevideo driver you need more primary memory. This also depends on the number of cacheddisplays.

• Resolve of symbolic object names via the GCOM Interface can take quite a long time,depending on load in controllers etc. If you build a display you must select “Use anyway”for each unresolved object you use. If you have installed the AdvaInform DDE Serveroption you can use an Excel sheet to initiate symbolic name translation for all the objectsyou intend to use in the AdvaSoft Station.

2.4.3 Advant Fieldbus 100 InterfaceIf you intend to include time tagged events from a controller not directly connected to theAdvant Fieldbus 100, you have to modify the COILESET.B00 created by the Bus ConfigurationBuilder. Figure 2-3 shows an example where you transfer EVS from AC 110 station 10 viastation 20 to AdvaSoft station 30. To create a correct COILESET.B00 file for this example, dothe following:

1. Select the IDENT for the EVS in Station 10 to an IDENT not used in Station 20.

2. Create coil-files as described in the Advant Fieldbus 100 Interface User’s Guide. All

stations must be included in the same project and have the same bus number.

3. The Bus Configuration Builder have now created a COILESET.B00 file with EVS(R)

corresponding to all EVS(S) in the AC 110 stations. Open the COILESET.B00 file andlocate the EVS(R) corresponding to EVS(S) in Station 10.

4. Change Station number in these EVS(R) from 10 to 20 i.e to the station number of the

AC 110 used as transit station

Figure 2-2. Subscription cycle time

Time

Subscriptioncycle time

Execution time




3BSE011611D0005 2-14

.

NOTE

The AF100 Interface load all objects from the BOIL and COIL files at startup if

not limited in the ADVASOFT.INI file. This can give an unnecessary long startup

time of your AdvaSoft station. In the ADVASOFT.INI file you can define which

controllers (one BOIL file per controller) you want to communicate with. See

AF100 Interface User’s Guide 3BSE006238R0201 Appendix - Settings in theADVASOFT.INI file, for more details.


• If the AdvaSoft station is connected via GCOM to a transit node with a MasterBus 300network you normally select a node on the Master Bus 300 network as clock master.

If you have the AdvaSoft station as clock master you will have some disadvantages. TheGCOM Interface doesn’t support the stand-by mode as clock master, i.e. if you haveselected the GCOM Interface to be clock master it will stay as clock master until it isreconfigured. On the MB 300 network you can have two precision levels for clock

synchronization, normal precision (1 s) and high precision (10 ms). The clocksynchronization in the GCOM Interface only supports normal precision. If you use thehigh precision clock synchronization you must always select a node with high precisiontime synchronization as clock master.

Figure 2-3. Sending time tagged events via AC 110 transit station

ASfW

AC 110Station 20

AC 110Station 10

AF 100

RCOM

EVS(S)

EVS(T)

EVS(R)Stn. 30



AdvaSoft for Windows Section 2.4.5 SQL*Net TCP/IP for Windows

3BSE011611D0005 2-15

2.4.5 SQL*Net TCP/IP for Windows

• The Option SQL*Net TCP/IP for Windows has been tested together with the TCP/IPsoftware ‘Microsoft® TCP/IP 3.11a’. Microsoft TCP/IP is available free of charge if youuse Microsoft® WindowsTM version 3.11 (Windows for Workgroups).

• If you try to access a not existing object from the Advant Station 500 IMS station the PCwill be locked 1 minute until the AS 500 IMS release the resources.

• All objects that you access via AdvaInform SQL*Connect must be defined in theAS 500IMS stations AdvaInform SQL*Connect Location Table. You can add objects tothe Location Table by sending a SELECT statement with only one object. For furtherinformation please refer to the AS 500IMS User’s Guide AdvaInform Basic Functions.



AdvaSoft for Windows Section 3.1 Initial Installation

3BSE011611D0005 3-1

Chapter 3 Installation

3.1 Initial InstallationYou will find the installation description in the ‘AdvaSoft for Windows User’s Guide’. For some

of the Option to AdvaSoft for Windows you also need additional installation descriptions, see

Table 3-1.

If you intend to use the Advant Fieldbus 100 Interface together with a previously installed

AdvaBuild for Windows version, please make sure that you have AdvaBuild for Windows

version 1.3/0 or later. Select installation of ‘AdvaBuild’ when you run the installation program.You will then have a correct setup of the communication interface for AdvaBuild.

Before you install the CI525/CI526 board, make sure that the I/O address and interrupt leveldoes not conflict with other installed devices in your PC, such as sound cards etc. To change thedefault settings of the CI525/CI526 board please refer to the Advant Fieldbus 100 Interface

AdvaSoft for Windows User’s Guide. If you during start-up of the Advant Fieldbus Interface get

an error message ‘Failed to initiate CI525/CI526 board’ you probably still have devices in yourPC that uses I/O address or interrupt level that are used by the CI525/CI526 interface board. Trythen to start-up the PC with only the CI525/CI526 board connected. If this is successful changethe settings of the CI525/CI526 or the other devices in your PC.

Table 3-1. Installation Descriptions for Options

Option User’s Guide

AdvaCommandDevelopment and Runtime

AdvaCommand DevelopmentAdvaCommand Runtime User’s Guide

AdvaCommand Upgrade User’s Guide

Advant Fieldbus 100 Interface Advant Fieldbus 100 InterfaceAdvaSoft for Windows User’s Guide andAdvant Fieldbus 100 User’s Guide

GCOM Interface GCOM InterfaceAdvaSoft for Windows User’s Guide

SQL*Net TCP/IP for Windows SQL*Net TCP/IPAdvaSoft for WindowsUser’s Guide

AdvaBuild for Windows AC 110/70/55 AdvaBuild for Windows ApplicationBuilder User’s Guide



AdvaSoft for Windows Section 3.2 Upgrading

3BSE011611D0005 3-2

3.2 Upgrading

If you already have installed AdvaSoft for Windows 1.x/x, make sure that you have backup data

saved before you start the new installation, see Section 3.3 Backup and Restore below.

1. When you have created backup data, you can use the same procedure as you use for an

Initial Installation, see Section 3.1 Initial Installation above. See also item 2 and 3 below.

2. When you install AdvaCommand for Windows you will have a choice to use the old FIX

software on your PC or reinstall FIX. You must select reinstall of FIX to get the correct

version of the AdvaCommand software.

NOTE

Some predefined displays and templates supplied with AdvaCommand for

Windows will be replaced with new initial versions during the installation. The

following predefined displays in the C:\WDMACS\PIC\ABBPIC directory, will

get extension ‘.EX’ if the corresponding ‘.ODF’ file exists:_MAIN

_DSPMENU_GR1PG1_GR2PG1

3. You can use your old displays created with ABB dynamos from AdvaSoft for Windowsversion 1.0/x or 1.1/x. The new dialogues in AdvaSoft for Windows version 1.3 (1.2) canbe used both for old and new displays. Do not mix objects created with ABB dynamosfrom AdvaSoft for Windows version 1.0/x or 1.1/x with objects created with the new ABBdynamos, in the same display.

If you intend to continue using the old standard dynamos from the AdvaSoft for Windows1.0/x or 1.1/x version you have to rename the old dynamo sets before you start the

installation. The following dynamo sets in the C:\WDMACS\PIC\ABBPIC directory areconcerned:

– ABBAIDE.SBL

– ABBAODE.SBL

– ABBDIDE.SBL

– ABBDODE.SBL

4. If you have created your displays with the ABB dynamos from the AdvaSoft for Windows1.0/x or 1.1/x version you have to rebuild your displays with the new ABB dynamos tofully support data from the GCOM Interface and the Extended DB elements via theAdvant Fieldbus 100 Interlace.

5. Delete the ADVACMD.XRF file in your AdvaSoft directory before startingAdvaCommand. Thereafter you must make a new Resolve of your pictures from Draw.

6. If you have reinstalled the GCOM Interface please check the System files according to theUser’s Guide. In same cases you can get duplicate ‘device lines=.’ lines in theCONFIG.SYS file. Remove the duplicate line.



AdvaSoft for Windows Section 3.3 Backup and Restore

3BSE011611D0005 3-3

3.3 Backup and Restore

We recommend that you regularly create backup data during application building and runtime

operation. For references to which files that are influenced during application building and

runtime operation, see Chapter 3 and Chapter 5 in each user’s guide.

Example of files necessary to backup are:

• Files for the AF 100 Interface in your C:\ADVASOFT\AF100\DATA directory

– AF100SYM.DTA

– COIL0000.C00

– COLSERV.B00

– COILESET.B00

– BOIL0000.C00(Make backup of the data generated by the AdvaBuild for Windows)

The best thing to backup is the .BAX and the .AAX file created by FCB since these files cangenerate all files mentioned above (except the .DTA file)

• Files for the GCOM Interface in your C:\ADVASOFT\GCOM\DATA directory

– GCOMSYM.DTA

• Files from your AdvaCommand Picture directory C:\WDMACS\PIC\ABBPIC

– All your own Displays and Predefined Displays that have been changed(_DSPMENU, _GR1PG1, _GR2PG2 etc.)

• Initiation files in the C:\WDMACS\LOCAL directory:

– HTD.INI (If you have defined SQL statements for historical data collection.)

– VIEW.INI (If you have changed Picture Cache size etc.)

• Historical Data and Configuration:– Files in C:\WDMACS\HTR (Configuration)

– Files in C:\WDMACS\HTRDATA (Data)



AdvaSoft for Windows Section 4.1 Capacity and Performance

3BSE011611D0005 4-1

Chapter 4 Miscellaneous

4.1 Capacity and Performance

PC’s used during performance test

The following Hewlett-Packard PC have been used during the performance tests:

• HP Vectra VL (referred to as VL/32), Pentium/166Matrox MGA Ultima Plus PCI-graphic with 2 MB video RAMImpression graphic board with 2 MB Video RAMCI526 communication board

The capacity figures in the Section 3.2 in the AdvaCommand for Windows User’s Guide(3BSE006237R0101) does not include figures for data via the GCOM Interface. Figure 4-1

shows the Display update time performance with AIPD01 links.

The Display update time is the time measured from when the display is selected from theDisplay menu until all attributes in the display have been updated.

Performance for display exchange time, AdvaCommand and GCOM

Figure 4-1. Display exchange time performance of AdvaCommand and GCOM

Display exchange time

20 8040 60

3

4

1

5

6

No Cache and Not Resolved

sec

No of AIPD01(1) display elements

Resolved Displays not in Cache

Resolved Displaysin Cache memory

VL/32

2




3BSE011611D0005 4-2

Performance for display exchange time, AdvaCommand and AF100

Performance for display exchange time, AdvaCommand and AF100

Figure 4-2. Display exchange time performance of AdvaCommand and AF 100 with DAT Based objects


20 8040 60

3

4

1

5

6

No Cache and not Resolved

sec

No of AIPD01 display elements


Resolved Displays

in Cache memory

VL/32

2

7

Each AIPD01 contains 8 data links.

AIPD01 DAT Based

100




3BSE011611D0005 4-3

NOTE

(1) Each AIPD01 contains 8 data links.

Figure 4-3. Display exchange time performance of AdvaCommand and AF 100 with Extended DB Elements


20 8040 60

No Cache and not Resolved

sec

No of AIPD01 display elements


Resolved Displaysin Cache memory

VL/32

Each AIPD01 contains 8 data links.

AIPD01 Extended DB Element

100



AdvaSoft for Windows Section 4.2 How to modify the MV table in MP200 and AC400

3BSE011611D0005 4-4

4.2 How to modify the MV table in MP200 and AC400

When you get a system message 24 16 DCBAG00 H’trace 18 H’NETWNODE... issued by a

MP200 or an AC400, it means hat there is a network and/or node which can not be recognized.

It often occurs after a MV/OS has, intentionally or not, been disconnected from the network.

When events occur, the MP200/AC400s are trying to send pro-event messages to all MV and

OS included in the MasterView Table. This table is present in all nodes and it contains

information regarding the MV and OS that are connected to the network.

The older MP200s have 8 entries in this table and each entry include the information network

and node. The more recent systems, MP200s and AC400s, have 16 entries and each entry

include the information network, node and version.

4.2.1 How to correct the MV table

4.2.1.1 Normal way

• Initiate (warm start) the MP200 or AC400.

4.2.1.2 Using OnLine Builder from an AS 500 OS in a system with 16 or 32 entries(MP200/1 SW*5.0 and later)

• On the OS500, start the ONLINE BUILDER and connect to the MP200 you want to patch

• Enter the command * LOCPSET CMDS:TP01.CT

• Enter the command * OMVT (Open MV Table)

– You will obtain a menu (1..5)

– The rest you will understand yourself

– Press <CTRL><C> to exit

• The version should be entered as follows :

TYPE OF MMI VERSION

OS 6

MV*5.0 5

MV*4.0 4

4.2.1.3 Using MA215

• There is a special diskette (TP01) available for the R&D personal. This diskette includethe command LMVT (List MasterView Table) which will allow you to obtain the addressof the DC$MVTAB and proceed as chapter 4.2.2.2 below.



AdvaSoft for Windows Section 4.2.2 Using System and Database Maintenance (or Expert commands) and TP01

3BSE011611D0005 4-5

4.2.2 Using System and Database Maintenance (or Expert commands) andTP01

4.2.2.1 System with 8 entries (MP200/1 SW*4.0 and earlier)

• You shall not use the complete OMVT menu towards these old 8 entries Master systems,you will receive wrong information in the entry numbers but you can use the commandOMVT, List function or LMVT to find the DC$MVTAB address.

Example:

* OMVT

1

DC$MVTAB = H'00487F12

---------------------

Max table size = 8

Current table size = 3

Entry number 1 = 11, 3 version 2817



...

Open the MVTAB this way and enter 0 instead of 0B03 if you want to removeNet 1Node 3.You also have to edit address H'487F12 to H'0208, witch mean that you use 2of 8 positions in the MVTAB instead of 3.

*O UWH,H'00487F12H'00487F12 UWH = H'0308 = 0208>H'00487F14 UWH = H'0B03 = 0B01H'00487F16 UWH = H'0B01 = 0B06H'00487F18 UWH = H'0B06 = 0H'00487F1A UWH = H'0000 =H'00487F1C UWH = H'0000 =H'00487F1E UWH = H'0000 =H'00487F20 UWH = H'0000 =H'00487F22 UWH = H'0000 = !



AdvaSoft for Windows Section 4.2.2 Using System and Database Maintenance (or Expert commands) and TP01

3BSE011611D0005 4-6

4.2.2.2 System with 16 or 32 entries (MP200/1 SW*5.0 and later)

• Use the command LMVT to find the DC$MVTAB address.

Example:

* LMVTDC$MVTAB = H'00487F12

---------------------

Max number of

Number of entries = 1




...

Open the MVTAB this way and enter 0 instead of 0B03 (11,3) and 0004 (version 4) if youwant to remove Net 11 Node 3.You also have to edit address H'487F12 to H'0010, witchmean that you use 0 of 16 positions in the MVTAB instead of 1.

*O UWH,H'00487F12H'00487F12 UWH = H'0110 = 0010> (zero entry out of 16 positions)H'00487F14UWH = H'0000 =H'00487F16 UWH = H'0B03 = 0 (Network, Node)H'00487F18 UWH = H'0004 = 0 (version)H'00487F1A UWH = H'0000 = !

• Use the command LMVT again to verify that the corrections you made are correct.



3BSE011611D0005

September 2000

Date post:	02-Jun-2018
Category:	Documents
Upload:	mivarv
View:	224 times
Download:	2 times

Release Notes AdvaSoft for Windows Version 1.3 4

Documents