Академический Документы
Профессиональный Документы
Культура Документы
3BSE011611D0005
3BSE001264/C
3BSE011611D0005
Chapter 1 - Introduction
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.6.1
1.6.2
1.6.3
1.6.4
Chapter 2 - Functionality
2.1
2.2
2.3
2.1.2
2.1.3
2.2.2
2.2.3
2.3.2
2.3.3
2.3.2.1
2.3.3.1
2.3.4
2.3.5
2.3.4.1
2.4
Recommendations...................................................................................................2-11
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.1.1
Chapter 3 - Installation
Copyright
3BSE011611D0005
iii
3.1
3.2
Upgrading................................................................................................................. 3-2
3.3
Chapter 4 - Miscellaneous
4.1
4.2
4.2.2
iv
4.2.1.2
4.2.1.3
Using System and Database Maintenance (or Expert commands) and TP0145
4.2.2.1
4.2.2.2
3BSE011611D0005
TABLES
3BSE011611D0005
Table 1-1.
Table 1-2.
Table 1-3.
Table 1-4.
Table 1-5.
Table 1-6.
Table 2-1.
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.
Table 2-5.
Table 3-1.
ILLUSTRATIONS
3BSE011611D0005
Figure 2-1.
Figure 2-2.
Figure 2-3.
Sending time tagged events via AC 110 transit station .............................. 2-14
Figure 4-1.
Figure 4-2.
Figure 4-3.
vi
Chapter 1 Introduction
Ordering No.
Actual revision
Release Date
Basic Unit
3BSE012023R4
1.3/4
September 2000
AdvaCommand Development(2)
3BSE012024R3
1.3/0
98-05-08
3BSE011611D0005
1-1
Ordering No.
Actual revision
Release Date
AdvaCommand Runtime
3BSE012025R3
1.3/0
98-05-08
3BSE012028R3
1.3/0
98-05-08
3BSE012029R3
1.3/0
98-05-08
3BSE005803R5
1.0/4
97-06-09
3BSE008943R1
2.0/0
96-02-26
3BSE012032R3
1.2/3
Sep, 2000
1.2/3
Sep, 2000
1.2/3
Sep, 2000
3BSE012031R3
1.2/3
Sep, 2000
GCOM Interface(7)
3BSE012695R4
1.1/3
Sep, 2000
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Release Date
Status Report
95-03-07
SR 5025
95-07-14
SR 5025/1
95-10-20
SR 5025/2
96-02-26
SR 6010
3BSE011611D0005
1-2
Release Date
Status Report
96-09-23
SR 6010/1
96-12-15
SR6078/0
97-06-09
SR7029
97-10-28
SR7029/1
98-05-08
SR7029/2
98-08-20
SR7029/3
September, 2000
SR7029/4
1.5 Compatibility
Following option versions are compatible with Basic Unit 1.3/4.
Option
Actual revision
AdvaCommand
1.2, 1.3/0
1.0/4
SQL*Net TCP/IP
2.0/0
AF 100 Interface
GCOM Interface
The AdvaSoft for Windows 1.3/4 can operate with the following ABB Advant OCS products on
the Advant Fieldbus 100 network:
3BSE011611D0005
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.
1-3
Advant Station 500 Series IMS with Master software version 1.2 or later. See also chapter
1.6.4.
Advant Station 500 Series IMS with MOD 300 software version 1.2 or later. See also
chapter 1.6.4.
MasterGate 230/1
1.6 Restrictions
1.6.1 AdvaCommand for Windows
If you intend to use the predefined Excel Report macros for AdvaCommand you must use
an english version of Excel.
The predefined dynamos for the Advant OCS system process objects can not be used for
presentation of data from the FIX database.
Data from the Advant Fieldbus 100 network and from the GCOM network is accessed
from AdvaCommand via the AdvaInform User API. Advant Fieldbus 100 and GCOM data
is not directly available in the FIX database. To operate with Advant Fieldbus 100 or
GCOM data you must build a separate application (FIX DDE Server or FIX Easy Database
Access (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 Windows
version 1.0 with objects created with the new ABB dynamos from AdvaCommand for
Windows version 1.3, in the same display. The dynamos in AdvaCommand for Windows
1.1, 1.2 and 1.3 are used in the same way. See also description of installation in Chapter 3
Installation.
3BSE011611D0005
The AdvaSoft for Windows Advant Fieldbus 100 interface supports only the functions for
data subscription and commands using sending Data Set Peripherals towards AC 410 and
AC 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
1-4
stations configured on the same bus number. Also only one bus number is supported but
this number is configurable.
The clock synchronization in the GCOM Interface does not support high precision clock
synchronization.
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. The
NUMCONFIG view is not supported in AdvaInform 2.0/0.
Ordering/Id. No.
3BSE008434R0401
3BSE007595/H
Ordering No.
3BSE006236R0301
AdvaCommand Development
AdvaCommand Runtime
AdvaCommand for Windows
3BSE006237R0201
AdvaCommand Development
Documentation Binder
3BSE006221R0101
3BSE011611D0005
1-5
Ordering No.
AdvaCommand Runtime
Documentation Binder
3BSE006226R0201
3BSE008229R0001
3BSE008230R0001
3BSE012036R0001
SQL*Net TCP/IP
AdvaSoft for Windows
3BSE006239R0101
3BSE006238R0201
3BSE000506R0701
GCOM Interface
AdvaSoft for Windows
3BSE008227R0101
3BSE007031R0301
3BSE007149R0401
Ordering No.
3BSE006222R0101
3BSE006223R0101
3BSE006224R0101
3BSE006225R0101
Ordering No.
3BSE006227R0101
3BSE006228R0101
3BSE006229R0101
3BSE006230R0101
3BSE011611D0005
1-6
Ordering No.
3BSE006231R0101
3BSE006233R0101
3BSE006234R0101
3BSE006235R0101
3BSE012036R0001
3BSE011611D0005
1-7
Chapter 2 Functionality
Support for both Extended Database (XDB) elements and DAT based objects. (Previous
version only supported DAT based objects.). The Extended DB element group offers a
more complete object type support with a simplified configuration compared with the DAT
based object. AI, AO, DI and DO objects are supported as Extended DB elements. The
XDB are only supported in AC110 2.1 and AC160.
Support for clock synchronization in slave mode (only if you have the CI526 board).
Application Version Control. This function ensure that on- and off-line changes, done with
AdvaBuild in the controllers is automatically reflected to the AdvaSoft station.
2.1.3 AdvaCommand
AdvaCommand 1.3 is based on FIX 5.65 (year 2000 compliant). Previous FIX 5.6
3BSE011611D0005
2-1
executed it goes out, gets the data and puts it in the variable instead of leaving it as an
indirect reference.
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 only
occur after a restart of AdvaCommand and an alarm is generated before the object has
been 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 if
the object was still in an other alarm state. Corrected in AdvaCommand *1.2/0.
AdvaCommand for Windows 1.2/0 could not provide a graphical SQL user interface for
Advant Station 500 Series IMS, i.e. the SQL*Net option could not be used together with
AdvaCommand for Windows. Corrected in AdvaCommand*1.2/1.
If you were using AdvaCommand in a FIX network configuration, it was not possible to
run the FIX View application in the node connected to the ABB network (AF100 and
GCOM). Commands towards objects from this node could result in an error message box
with 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 have
the invalid handle passed problem described above if you used a configuration with
SQL*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 for
Windows dynamos, due to the use of a string variable for the object name. The new
dynamos in AdvaCommand 1.3 does not use the string variable.
3BSE011611D0005
It has not been possible to perform acknowledge of DAT based objects between two
AdvaSoft stations.
Corrected in AF100 Interface*1.2/1.
The time synchronization did not work as expected when the power supply was
disconnected 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.
2-2
The redundant line support flag was in certain situations, incorrectly read as no even if set
to 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, when
AdvaSoft 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.
Events stopped coming and commands could not be sent to the controller in certain
situations, 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 Alarm
History until the next time an event was generated on that object.
Corrected in AF100 Interface*1.2/3.
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.
2.2.3 GCOM
NOTE
For swedish signs set Language=2 in the[GCOMProfile] section of the
AdvaSoft.ini file.
When setting the time in a Masterbus 300 network to 2000-02-29, the AdvaSoft for
Windows did not accept time synchronization through GCOM.
Corrected in GCOM Interface*1.1/2.
3BSE011611D0005
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 AdvaCommand
and/or the SQL*Net for TCP/IP option you must manually update the list of installed
options in ADVASOFT.INI file, otherwise you will have wrong information when you
check installed options from the AdvaSoft Main Window.
2-3
In cases where you use a Command script to update AI or AO objects, please note the
following:
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 same
problem 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 Historical
Assign, HTA) and refer to this tag in an Excel report the ; will be treated as new column
and the layout of the report will not be OK.
You can select the separator used when defining subscription cycle time for a Tag. Default
is ; used as separator. You select the separator in the ADVASOFT.INI file (residing in the
MS-Windows directory). Change the parameter SubsSeparator in the [Communication]
section.
AdvaCommand must always be restarted if you have changed object type, with the AF 100
Object Configuration Tool, for a previously used object. For example DAT changed to AI
with the Object configuration tool.
Objects that are in alarm state before start-up of AdvaCommand may not be presented in
the AdvaCommand Alarm List.
Do not use more than 800 dynamic links in a process display. If you have a display with
more than 800 dynamic links you will have an unpredictable behavior of the system. You
cant 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 this
frame marked even though the object isnt 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 Alarm
Summary. 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 as
large as the Alarm Summary window and keep it in the background. I.e. edit the display
_TOPLINE with Draw.
AdvaCommand Runtime
AdvaCommand Development
AdvaCommand for Windows
3BSE 006 237R0201
3BSE011611D0005
To be able to install the FIX DDE Driver or other I/O Drivers check the following
2-4
option.
FIX Software Options
Please select the options to install.
FIX Support
Historical Trending
Recipe Package
Select this option to
install the driver
Report Generator
I/O Drivers
Database Access Toolkit(s)
Diagnostics
Sample System
QuickStart Tutorial
Option Diskettes
Update Diskettes
OK
Cancel
The performance figures is not included for the GCOM Interface. Performance
figures are included in Chapter 4 in this document.
You can use maximum 800 dynamic links in each process display. In the Users
Guide 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 verify
the number of dynamic links used in a display press <Ctrl>+<Shift>+L within the
Draw 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 below
shows the number of dynamic links in the predefined dynamos in the ABB dynamo
sets (ABBAIDE, ABBAODE, ABBDIDE and ABBDODE).
3BSE011611D0005
Description
Number of links
AIPD01
AIPD51
AIGR01
15
AOPD01
AOPD51
AOGR01
11
DIPD01
DIGR01
11
DOPD01
DOGR01
2-5
The predefined dynamos for the Advant OCS system process objects can not be used
for presentation of data from the FIX database. Some of the Advant OCS object
attributes have no corresponding FIX field name.
The Dialog Button Sets are designed to cover the functionality you have if you operate on
process objects via the GCOM Interface.
Table 2-2 shows supported commands via the Advant Fieldbus 100 Interface for DAT
Based objects (AI, AO, DI, DO and DAT) and for Extended DB Elements (AIS, AOS,
DIS, DOS, DAT, MR, MB, MI and ML).
Table 2-2. Supported operations for DAT Based objects and Extended DB Elements
AI/AIS
AO/AOS
DI/DIS
DO/DOS
DAT(1)
Select/Deselect(2)
yes
yes
yes
yes
no
Block/Deblock Print(2)
yes
no
yes
no
no
Block/Deblock Alarm(3)
Operation
yes
no
yes
no
no
(3)
Block/Deblock Input
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
no/yes
no
no
no
no
yes
yes
yes
yes
no
(1) The object types MR, MB, MI and ML supports the same commands as the DAT object.
(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.
(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.
(4) For DAT Based objects the Acknowledge signal is only sent to other AdvaSoft for Windows Stations
on the same Advant Fieldbus 100 bus.
You can use your old displays created with ABB dynamos from AdvaCommand for
Windows version 1.0. The new dialogues in AdvaCommand for Windows version 1.3
can be used both for old and new displays. Do not mix objects created with ABB
dynamos from AdvaCommand for Windows version 1.0 with objects created with the
new ABB dynamos from AdvaCommand for Windows version 1.3 (1.1, 1.2), in the
same display. See also description of installation in Chapter 3
3BSE011611D0005
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 restart
again. 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
2-6
In clock master mode a synchronization signal must be sent cyclically every second. The
cycle 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 to
open the CI525 Configuration dialog box. Time synchronization = Off.
b.
Reconfigure the CI525 board by clicking the Disconnect button followed by the
Connect button.
The AF 100 Object Configuration Tool can maximum handle 2730 Event Channels if you
use Event Channel names with maximum length (20 characters). If you need to configure
more Event channels, use shorter names or use the default name. Note also the
recommendations 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 are
sent 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 ident
numbers 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 as
expected. The scaling factor 100 incorrectly functions as 0.1 and the scaling factor 1000 as
0.01.
When you use 2 Byte DAT objects, use receiving DSP in the controller, to get correct
mapping of data in the DAT.
3BSE011611D0005
Service Data Protocol communication failure may result in different error messages.
The most common are:
2-7
* 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 typing
InterruptSupervise=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 Users Guide Appendix B
-Object Attributes and Commands, page B-5 and B-6.
* OUTP_BLK is not supported for extended DB Elements.
3BSE011611D0005
If you have objects configured with event treat = 2, the text in Alarm History will not be
the same as in the Event list for the Advant Station 500 OS. The Alarm History shows both
the 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 and
AIEV in the AC 450. The DIEV and AIEV database elements sends the alarms to the
AdvaSoft station via the GCOM Interface. From the AdvaSoft station Acknowledge of
AIEV/DIEV Alarms in the AC 450 node doesnt work if you dont have a MasterBus 300
network connected to the AC 450. I.e. in a configuration shown in Figure 2-1, you cant
2-8
ASfW
GCOM
AC 450
AF 100
AC 110
AC 110
Figure 2-1. Sending time tagged events via AC 450 transit node
If AdvaSoft for Windows is the only operator station in a network with AC400/MP200
controllers, it needs to update the AL_UNACK bit for AI and DI database elements. The
AL_UNACK bit indicates that an unacknowledged alarm exists in the database element.
The AdvaSoft for Windows unacknowledge function is by default disabled and it is
activated 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 database
elements.
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 the
AdvaSoft.ini file:
[GCOMProfile]
OperatorTreat=1
See the GCOM Interface AdvaSoft for Windows Users Guide, for more details.
3BSE011611D0005
The GCOM (CI543) does not work with slave number 7 or 8 on CS513 when used with
AC410/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 the
MasterView table of the controller not being updated.
If you have this problem, try the following measures:
2-9
update the table by choosing Force NODE INIT signal from the GCOM-menu
More...
Switch To...
Ctrl+Esc
Resolve
Reset Diagnostics
Configure...
Status...
Select this
option
or
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 API
function. This is not correct.
3BSE011611D0005
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 the
Client Application before you shutdown Windows.
The AdvaInform DDE Server doesnt indicate lost communication to the client
application. The last updated value is just frozen. If you restart your client application you
will have indication of lost communication.
2-10
2.4 Recommendations
The Table 2-3 gives configuration guidelines when AdvaSoft for Windows is used on the
Advant Fieldbus 100 network.
Table 2-3. Configuration on AF 100
Maximum recommended
configuration
Number of AdvaSoft for
Windows
Number of objects on
AF 100
10
5000
50
4
1
Total number of
messages/second(2)
50
10
3BSE011611D0005
2-11
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.
Table 2-5. Recommended system configuration on SQL*Net TCP/IP
Maximum recommended
configuration
Number of AdvaSoft for
Windows stations
Number of AS 500IMS
Server nodes
NOTE
From a process display in AdvaCommand you can only read data from the
AS 500 IMS.
3BSE011611D0005
The cycle time you define as subscription cycle time will not include the time needed by
2-12
Time
Subscription
cycle time
Execution
time
If you want to use the Dynamo Sets delivered with the standard FIX product you will find
them 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 some
video driver you need more primary memory. This also depends on the number of cached
displays.
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 Server
option you can use an Excel sheet to initiate symbolic name translation for all the objects
you intend to use in the AdvaSoft Station.
3BSE011611D0005
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 Users 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 and
locate 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
2-13
ASfW
Stn. 30
EVS(R)
AF 100
AC 110
Station 20
EVS(T)
RCOM
AC 110
Station 10 EVS(S)
Figure 2-3. Sending time tagged events via AC 110 transit station
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 Users Guide 3BSE006238R0201 Appendix - Settings in the
ADVASOFT.INI file, for more details.
If the AdvaSoft station is connected via GCOM to a transit node with a MasterBus 300
network 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. The
GCOM Interface doesnt support the stand-by mode as clock master, i.e. if you have
selected the GCOM Interface to be clock master it will stay as clock master until it is
reconfigured. On the MB 300 network you can have two precision levels for clock
synchronization, normal precision (1 s) and high precision (10 ms). The clock
synchronization in the GCOM Interface only supports normal precision. If you use the
high precision clock synchronization you must always select a node with high precision
time synchronization as clock master.
3BSE011611D0005
2-14
3BSE011611D0005
The Option SQL*Net TCP/IP for Windows has been tested together with the TCP/IP
software Microsoft TCP/IP 3.11a. Microsoft TCP/IP is available free of charge if you
use 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 PC
will 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 the
AS 500IMS stations AdvaInform SQL*Connect Location Table. You can add objects to
the Location Table by sending a SELECT statement with only one object. For further
information please refer to the AS 500IMS Users Guide AdvaInform Basic Functions.
2-15
Chapter 3 Installation
Users Guide
AdvaCommand Development
AdvaCommand Runtime Users Guide
AdvaCommand Upgrade Users Guide
3BSE011611D0005
GCOM Interface
GCOM Interface
AdvaSoft for Windows Users Guide
SQL*Net TCP/IP
AdvaSoft for Windows
Users Guide
3-1
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 Windows
version 1.0/x or 1.1/x. The new dialogues in AdvaSoft for Windows version 1.3 (1.2) can
be used both for old and new displays. Do not mix objects created with ABB dynamos
from AdvaSoft for Windows version 1.0/x or 1.1/x with objects created with the new ABB
dynamos, in the same display.
If you intend to continue using the old standard dynamos from the AdvaSoft for Windows
1.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 are
concerned:
3BSE011611D0005
ABBAIDE.SBL
ABBAODE.SBL
ABBDIDE.SBL
ABBDODE.SBL
4.
If you have created your displays with the ABB dynamos from the AdvaSoft for Windows
1.0/x or 1.1/x version you have to rebuild your displays with the new ABB dynamos to
fully support data from the GCOM Interface and the Extended DB elements via the
Advant Fieldbus 100 Interlace.
5.
6.
If you have reinstalled the GCOM Interface please check the System files according to the
Users Guide. In same cases you can get duplicate device lines=. lines in the
CONFIG.SYS file. Remove the duplicate line.
3-2
AF100SYM.DTA
COIL0000.C00
COLSERV.B00
COILESET.B00
The best thing to backup is the .BAX and the .AAX file created by FCB since these files can
generate all files mentioned above (except the .DTA file)
3BSE011611D0005
GCOMSYM.DTA
All your own Displays and Predefined Displays that have been changed
(_DSPMENU, _GR1PG1, _GR2PG2 etc.)
HTD.INI (If you have defined SQL statements for historical data collection.)
3-3
Chapter 4 Miscellaneous
The capacity figures in the Section 3.2 in the AdvaCommand for Windows Users 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 the
Display menu until all attributes in the display have been updated.
Performance for display exchange time, AdvaCommand and GCOM
Display exchange time
sec
VL/32
5
4
3
No Cache and Not Resolved
2
40
60
80
3BSE011611D0005
4-1
7
6
VL/32
AIPD01 DAT Based
5
4
3
No Cache and not Resolved
2
40
60
80
100
Figure 4-2. Display exchange time performance of AdvaCommand and AF 100 with DAT Based objects
Performance for display exchange time, AdvaCommand and AF100
3BSE011611D0005
4-2
VL/32
AIPD01 Extended DB Element
40
60
80
100
Figure 4-3. Display exchange time performance of AdvaCommand and AF 100 with Extended DB Elements
NOTE
(1) Each AIPD01 contains 8 data links.
3BSE011611D0005
4-3
On the OS500, start the ONLINE BUILDER and connect to the MP200 you want to patch
VERSION
OS
MV*5.0
MV*4.0
3BSE011611D0005
There is a special diskette (TP01) available for the R&D personal. This diskette include
the command LMVT (List MasterView Table) which will allow you to obtain the address
of the DC$MVTAB and proceed as chapter 4.2.2.2 below.
4-4
4.2.2 Using System and Database Maintenance (or Expert commands) and
TP01
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 command
OMVT, List function or LMVT to find the DC$MVTAB address.
Example:
* OMVT
1
DC$MVTAB = H'00487F12
--------------------Max table size
= 8
= 3
Entry number 1
Entry number 2
= 11, 1 version 0
Entry number 3
= 11, 6 version 0
...
Open the MVTAB this way and enter 0 instead of 0B03 if you want to remove
Net 1Node 3.You also have to edit address H'487F12 to H'0208, witch mean that you use 2
of 8 positions in the MVTAB instead of 3.
*O UWH,H'00487F12
H'00487F12 UWH = H'0308 = 0208>
H'00487F14 UWH = H'0B03 = 0B01
H'00487F16 UWH = H'0B01 = 0B06
H'00487F18 UWH = H'0B06 = 0
H'00487F1A UWH = H'0000 =
H'00487F1C UWH = H'0000 =
H'00487F1E UWH = H'0000 =
H'00487F20 UWH = H'0000 =
H'00487F22 UWH = H'0000 = !
3BSE011611D0005
4-5
= 1
Entry number 1
= 11, 3 version 4
Entry number 2
0, 0 version 0
Entry number 3
0, 0 version 0
...
Open the MVTAB this way and enter 0 instead of 0B03 (11,3) and 0004 (version 4) if you
want to remove Net 11 Node 3.You also have to edit address H'487F12 to H'0010, witch
mean that you use 0 of 16 positions in the MVTAB instead of 1.
*O UWH,H'00487F12
H'00487F12 UWH = H'0110 = 0010>
H'00487F14UWH = H'0000 =
H'00487F16 UWH = H'0B03 = 0
H'00487F18 UWH = H'0004 = 0
H'00487F1A UWH = H'0000 = !
3BSE011611D0005
Use the command LMVT again to verify that the corrections you made are correct.
4-6
3BSE011611D0005
September 2000