Documente Academic
Documente Profesional
Documente Cultură
Version 5
Installation/Administration
TRADEMARKS
MODBUS is a registered Trademark of Gould Electronics
ORACLE ® is a registered Trademark of Oracle Corp. USA
Windows 2000®, Windows XP Windows 2003®, Excel®, SQL-Server ®
are registered
Trademarks of Microsoft Corp. USA
PcAnywhere™ is a registered Trademark of Symantec Corporation
Pentium® is a registered Trademark of Intel Corporation
NOTE
The information in this document is subject to change without notice and should not be
construed, as a commitment by ABB AG. ABB AG assumes no responsibility for any errors
that may appear in this document.
In no event shall ABB AG be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB AG be
liable for incidental or consequential damages arising from use of any software or hardware
described in this document.
This document and parts thereof must not be reproduced or copied without written
permission of ABB AG, and the contents thereof must not be imparted to a third party nor
be used for any unauthorized purpose.
The software described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license.
Contact: ABB AG
Power Generation Products
www.abb.com/powergeneration
Copying of this document, and giving it to others and the use or communication of the contents thereof, are forbidden
without express authority. Offenders are liable to the payment of damages. All rights are reserved in the event of the
grant of a patent or the registration of a utility model or design. (DIN 34)
PGIM 5 Table of Contents
Installation/Administration
Table of Contents:
1 General ......................................................................................................................................12
1.1 Introduction...............................................................................................................................................12
1.1.1 Process data acquisition (scanner) ....................................................................................................13
1.1.2 Process Data Management (Server)..................................................................................................14
1.1.3 Process Data Evaluation (Clients)......................................................................................................15
1.1.3.1 Navigator ........................................................................................................................................15
1.1.3.2 SignalExplorer ................................................................................................................................15
1.1.3.3 Trend Analysis ................................................................................................................................15
1.1.3.4 Process graphic ..............................................................................................................................16
1.1.3.5 Logging ...........................................................................................................................................16
1.1.3.6 Technical calculations ....................................................................................................................16
1.1.3.7 Security Concept ............................................................................................................................16
1.2 Setup instruction ......................................................................................................................................18
1.2.1 PGIM Installation Kit ...........................................................................................................................18
1.2.2 Licensing.............................................................................................................................................18
1.2.3 Installation...........................................................................................................................................18
1.2.3.1 Requirements for installation ..........................................................................................................18
1.2.3.2 Installation of a component from the PGIM system software.........................................................19
1.2.3.2.1 Installation of a PGIM server or PGIM scanner..............................................................................22
1.2.3.2.2 Installation of a PGIM client............................................................................................................23
1.2.3.2.3 Installation of a demo system .........................................................................................................23
1.2.3.3 Update ............................................................................................................................................24
1.2.3.4 Folder structure...............................................................................................................................24
1.2.3.5 Initialization file PLACO.INI ............................................................................................................25
1.2.3.6 Installation of a component from the PGIM EventManagement.....................................................30
1.3 Security Concept ......................................................................................................................................31
1.3.1 Introduction .........................................................................................................................................31
1.3.2 Functionality........................................................................................................................................31
1.4 UserManager .............................................................................................................................................33
1.4.1 Introduction .........................................................................................................................................33
1.4.2 Call-in of the UserManager.................................................................................................................33
1.4.3 Arrangement of the different control elements in the UserManager ..................................................34
1.4.4 UserManager functionality:.................................................................................................................34
1.4.4.1 Display users and user groups.......................................................................................................34
1.4.4.2 Rename user group........................................................................................................................34
1.4.4.3 Add new user..................................................................................................................................34
1.4.4.4 Change password for users ...........................................................................................................35
1.4.4.5 Allocate users to another group .....................................................................................................35
1.4.4.6 Allocate rights for specific signals to specific user groups .............................................................35
1.4.4.7 Allocate application rights to a specific user group ........................................................................35
1.5 Signal Names ............................................................................................................................................37
2 Scanner .....................................................................................................................................46
2.1 Introduction...............................................................................................................................................46
4.1 Introduction.............................................................................................................................................177
5.1 Introduction.............................................................................................................................................211
6 Trend .......................................................................................................................................214
7 AutoMail ..................................................................................................................................218
8 WebClient................................................................................................................................223
8.1 Introduction.............................................................................................................................................223
9 Backup hints...........................................................................................................................227
9.1 Introduction.............................................................................................................................................227
9.1.1 Requirements and Preparations.......................................................................................................227
9.1.2 Backup Tools ....................................................................................................................................227
9.2 Windows Operating System..................................................................................................................228
9.2.1 Backup..............................................................................................................................................228
9.2.2 Recovery...........................................................................................................................................228
9.3 Office Applications and Other Tools ....................................................................................................229
9.3.1 Backup..............................................................................................................................................229
9.3.2 Recovery...........................................................................................................................................229
9.4 PGIM Server ............................................................................................................................................230
9.4.1 Backup of Basic Installation..............................................................................................................230
9.4.2 Recovery of Basic Installation ..........................................................................................................230
9.4.3 Backup of Continuously Changing Data...........................................................................................230
9.4.4 Recovery of Continuously Changing Data .......................................................................................230
9.4.5 PGIM Folder Structure......................................................................................................................231
9.5 PGIM Scanner .........................................................................................................................................231
10.1 Introduction.............................................................................................................................................233
10.2 Installation...............................................................................................................................................234
10.2.1 Initialization file .................................................................................................................................234
11 AutoUpdate .............................................................................................................................235
11.1 Introduction.............................................................................................................................................235
11.2 Preconditions..........................................................................................................................................236
13.1 ASCII-Export............................................................................................................................................254
13.1.1 Introduction .......................................................................................................................................254
13.1.2 Installation.........................................................................................................................................254
13.2 External Scheduler (legacy) ..................................................................................................................255
13.2.1 Introduction .......................................................................................................................................255
13.2.2 Installation.........................................................................................................................................255
13.2.2.1 Files required for the installation...................................................................................................255
13.2.2.2 Files required for the access to PGIM ..........................................................................................255
13.2.2.3 Files necessary for the access to the registry ..............................................................................255
13.3 System Router ........................................................................................................................................257
13.3.1 Introduction .......................................................................................................................................257
13.3.2 Installation.........................................................................................................................................257
13.3.3 Structure ...........................................................................................................................................257
13.3.4 Operation ..........................................................................................................................................258
13.3.5 Autostart / Initialization file................................................................................................................258
13.3.6 Configuration ....................................................................................................................................258
13.3.6.1 Module Connect............................................................................................................................259
13.3.6.2 Module DisConnectAlarm.............................................................................................................259
13.3.6.3 Module ODER (OR)......................................................................................................................260
13.3.6.4 Module 2ZU1 (2 to 1)....................................................................................................................261
13.4 AutoMailer ...............................................................................................................................................262
13.4.1 Introduction .......................................................................................................................................262
13.4.2 Installation.........................................................................................................................................262
13.4.3 Structure ...........................................................................................................................................262
13.4.4 Procedure during configuration, start and stop ................................................................................262
13.4.5 Operation ..........................................................................................................................................263
13.4.5.1 Setting Options .............................................................................................................................263
13.4.5.2 Create new folder .........................................................................................................................263
13.4.5.2.1 Set folder ......................................................................................................................................263
13.4.5.2.2 Active ............................................................................................................................................263
13.4.5.2.3 Add e-mail addresses to the folder...............................................................................................263
13.4.5.2.4 Delete e-mail addresses from the folder ......................................................................................263
13.4.5.3 Add, change or delete e-mail addresses in the internal AutoMail database ................................263
13.4.5.3.1 Delete e-mail addresses from the internal AutoMail database ....................................................264
13.4.5.3.2 Edit e-mail addresses in the internal AutoMail database .............................................................264
13.4.5.3.3 Add e-mail addresses to the internal AutoMail database.............................................................264
1 General
Power Generation Information Manager (PGIM) is the new name for the former known Plant
Information Management Software "PlantConnect". This document and also the PGIM Software
version 4.0 use both names.
1.1 Introduction
For the specific tasks of plant management, a Process Information Management System (PIMS) is
both the basis and also the tool to acquire and centrally evaluate all process data using one system
with one user interface.
Office
network
SQL
Counters interface
Process
communication
1.1.3.1 Navigator
The PGIM navigator manages logs, technical calculations, process graphics and trend analyses using
a familiar Windows tree-structure display. The structure can be changed and adapted individually to
create the optimum working environment for each staff member.
1.1.3.2 SignalExplorer
The SignalExplorer retrieves all configured process data from the connected servers. This data can be
filtered and sorted according to codes. Using drag-and-drop operations the signals are controlled by
the clients, i.e. the process data is connected with the client.
1.1.3.5 Logging
Current and historical process data is summarized in a log, and can be printed or saved. The logs are
automatically activated, either in a pre-determined cycle, or by events. Operator intervention is also
possible. Microsoft Excel is used as the front-end software.
Logs are based on templates:
Daily, weekly, monthly and yearly logs.
Accounting logs.
Maintenance logs.
Matrix logs.
The logging process fills in the templates with process data, processes them if necessary, and makes
the logs available for printing or storage as files.
The names and the description of the process data can be accessed through menus. This simplifies
the configuration of signal-connection and layout.
The integration of logging under Microsoft Excel opens log data to Office applications. Logs that have
been generated and stored can processed whenever necessary.
1.2.2 Licensing
The CD contains the entire PGIM software package. You are limited in portions of the package you
can use, based on the software protection module in the license file.
Monitoring the licensed scope of use is performed by the PGIM server. If your installation uses one
PGIM server, this server will also be the license server. If you installation uses several PGIM servers
(multi-server environment), you must determine which PGIM server to use as a license server.
1.2.3 Installation
Automatic installation needs a configuration file, which can be obtained from an ABB
representative for your system. This option is only applicable for PGIM in 800xA cpntrol system
installations. Please refer to the PGIM 800xA Installation Manual.
The next screen will show the status of a small system check if your computer hardware
complies with the PGIM minimum requirements. Please solve all problems before you continue
your installation.
Touch the “Start” button
On the next screen you will find the PGIM Installation Welcome page.
If you have already installed PGIM on this computer and are only re-installing a component now,
the target folder is recognized by the setup, and a reinstallation will be performed in the same
target folder.
Note: You can not perform a second installation in another folder. If you require another
installation path, you must remove then reinstall PGIM.
Click Next. The window for the selection of components appears. Now select the required
components.
Select those components which you would like to install. Client and Server come without an
extra option menu.
Scanner selection: Activate [D] Scanner and select one or several ScanDrivers via the
Details... button. Click ENTER after the detail selection in order to return to the Select
components window.
Selection of tools: Activate [D] Tools and select one or several PGIM tools via the
Details... button. Click ENTER after the detail selection in order to return to the Select
components window.
After having selected all the components, click Next.
This screen will give you the possibility to choose whether the system will be contructed
redundant or not. After selection press Next
All necessary files will be copied. This can take a few minutes. After that, some final
questions must be answered.
When the installation is complete and all software is loaded then hit Finish on this screen.
Update from OPC DA Server:
When upgrading a PGIM system from a prior version, which is using the OPC DA server, you
will see a message on your screen asking whether to upgrade to the never and improved
version of the OPC DA server. This is recommended but be aware that you will have to change
your OPC client assignments as well since the new OPC server does have a new GUID.
1.2.3.3 Update
If this is not a new installation, i.e. if there is already a previous version of PGIM on your computer,
observe the following items before you continue with the installation:
If a PGIM Server and/or a PGIM ScanManager (see Control panel / Services) has been installed on
your computer, stop these services.
Backup the folders:
.. PlantConnect
.. PlantConnect.bin
.. PlantConnect.sys
If you have added PGIM files after the installation, they will not be deleted when installing PGIM.
The installation is started by executing the autorun.exe file of the installation CD.
C:\PGIM
Folder for plant-specific applications (graphic charts, curves, logs and calculations). The subfolders of
this folder are displayed in the PGIM navigator.
C:\PGIM\PlantConnect.BIN
Folder for program-specific files of the PGIM software.
C:\PGIM\PlantConnect.SYS
The SYS folder includes different system subfolders.
C:\PGIM\PlantConnect.SYS\Temp
Temporary files are stored here which can all be deleted and will be recreated by the applications (for
example: Data.tmp).
C:\ PGIM\PlantConnect.SYS\Debug
Here further subfolders are created by the applications in which the log files for an error analysis will
be created (for example: \SignalExplorer\SignalExplorer.log).
C:\ PGIM\PlantConnect.SYS\Texte
Here further subfolders are created for the different languages in which the text files (one per
application) will be created (for example: \English\SignalExplorer_dt.csv).
C:\ PGIM\PlantConnect.SYS\SysKonfi
Configuration (ini) files are stored here.
C:\ PGIM\PlantConnect.SYS\Events
HDAlertIfLessThanMB = 200 If there is less than XX MB available on the hard disk, the file with
the parameter at "AtHDAlertPassMsgToApp" becomes active. If there is only 50% of the set value
available, the data collection of the Database Server stops
AtHDAlertPassMsgToApp = NetSend.bat In this file you can configure who should be informed
when this situation occurs.
Section [Server.Settings]
Paths for archive data:
The PGIM server archives all signal data (signal values and signal configurations) in the file system of
the computer. Therefore base paths for archive data must be preset here. The export paths designate
the external media to which the data will be transferred when the export time has been reached.
Roh.BasePath Æ Base path for the archives
Each signal in the server has its own RAM-Cache. The default size of a RAM-Cache can be set as
follows. It affects the RAM requirements of the server.
Generally, the following thumb rule applies:
RAM requirements in MB =
15+MaxSignals*RohCacheSize*18/10e6+MaxSignals*MMM.RAMCacheSize*30/10e6
Roh.RAMCacheSize Æ Random-access memory dedicated for raw data
MaxSignals Æ Maximum of signals to be stored in the database
Roh.LifeTimeDays Æ Default lifetime of all raw signals in days. This parameter can be
set individual for each signal in the SignalExplorer.
WEBPort = 8081 Æ TCP/IP-Port for the Web Client communication (optional)
WebClientAutoLogoffAfterMinutes=15 Æ Inactive Web Client connections are disconnected
after X Minutes.
Section [GED.Settings]
MainPath = C:\PlantConnect Æ Main folder for the navigator. Here the path
.\System\Autostart is created automatically.
AddPath = D:\Office\Data Æ Additional folder for the navigator. Also a network path is possible
Section [SignalExplorer]
XtraTools = Æ The entry at this place allows a user-defined pull-down menu
in the SignalExplorer under Extras.
Section [TREND.ATTRIBUTES]
Signal = _KB_SignalName,140
No = _INDEX,20
Current Value = _KB_VALUE,95
Y-MRB = _KB_MBA,75
Y-MRE = _KB_MBE,75
MRB KKS = mba,75
MRE KKS = mbe,75
Dim = Dimension,70
Description (long text) = Langtext,300
DB Calc function = _KB_DBACCESS,120
Value Transform = _KB_MX_PLUS_B,180
Scanner = ScanMan,85
Driver = ScanDriver,80
Comment =_COMMENT,100
Æ Name (keywords) and length of the fields in the legend of the curve
displays.
Note: Do not modify the keywords left to the equation sign.
Description to [TREND.ATTRIBUTES]:
This section the trend legend is defined. Each input describes one column. (The example above has
10 columns).
<Column Name> = <DBKEY>,<Pixel Length>
Example: Signal = _KB_SignalName,200
<Column Name> is the text in the legend what is set for the title of the column. <DBKEY> is the key
word for the database field and <Pixel Length> is the length of the column. For <DBKEY> all
reachable database fields are possible (also the user defined).
There are some additional keys <DBKEY>. These special keys are marked with a prefix _. There is no
database information. These keys are internal keys of the trend. The following inputs are necessary:
<DBKEY>
_INDEX Number of the signal in the trend
_KB_VALUE actual value on the right hand side of the trend
_KB_MBA Scale start in the trend
_KB_MBE Scale end in the trend
_KB_DBACCESS Used database function [Special].
_KB_MX_PLUS_B Used transformation [Special].
_KB_SignalName Name of the wanted Signal
_COMMENT,100 Field for user defined comments. These comments are available in this trend
Section [Trend]
VISUALMODE = NORMAL Æ The thickness of the letters in the curve display can be changed
from "NORMAL" to "BOLD".
[APIPRO]
APIPROIFPATH=D:\apipro\apipro42\work If the maintenance program APIPRO is in use, a direct
connection between PGIM and the data in APIPRo can be set. The path to APIPRO is set in this
section.
[GEDContextMenu]
Applikation1=Action.Bat
At each signal in the PGIM graphic a context menu appears if you click the right mouse button. This
example shows an "Applikation1". If you click this function the file "Action.Bat" is active.
A file with the name "CMD.INI" is created in the Client-folder (...PlantConnect.bin\client\). The following
information is set in that file:
[Tags]
A1=\\MIP311\SM\HyperPIMS\3D_Z
[Common]
CalledFrom=D:\PGIM\PlantConnect\Graphic1.ged
ScreenPosX=510
ScreenPosY=509
The input in [Tags] shows the signal, what you selected in the graphic.
"Action.Bat" can start a program that uses this information in the CMD.ini file as a parameter.
[1ANumContextMenu]
AlarmClient=default.eaf
[2ANumContextMenu]
[3ANumContextMenu]
3D-View=VIew3D.vbs
[nANumContextMenu]
Note:
In the trend, different context menus may be superimposed depending on the number of selected
signals. A distinction is made between:
- 1 signal selected,
- 2 signals selected,
- 3 signals selected,
- >3 signals selected.
For each of the above cases, a separate section is provided in the PlaCo.INI:
[1ANumContextMenu]
[2ANumContextMenu]
[3ANumContextMenu]
[nANumContextMenu]
Example:
[1ANumContextMenu]
Browse additional info ... = AppA.VBS
[2ANumContextMenu]
Browse additional info ... = AppA.VBS
Correlation ... = Correla.XLS
[3ANumContextMenu]
Browse additional info ... = AppA.VBS
[nANumContextMenu]
Browse additional info ... = AppA.VBS
3D representation = Do3DView.EXE
[PlantConnect]
Server=No
GED=Yes
KillNotUsedConnectionsAfterHours=48
[Server.Settings]
Roh.BasePath=C:\PlantConnect.ROH\
Roh.RAMCacheSize=200
MaxSignals=100
Roh.LifeTimeDays=1000
WebClientAutoLogoffAfterMinutes=15
[GED.Settings]
MainPath=D:\PlantConnect
;AddPath=z:\
GEDFont=Arial~0~400~0~0~0~ansi~4
[SignalExplorer]
XtraTools=C:\PIMS\PlantConnect.BIN\Dokumentation\Deutsch\ScreenShow\PlantCo.pps, PPT-Show
[TREND.ATTRIBUTES]
Name=_KB_SignalName,200
No=_INDEX,20
Value=_KB_VALUE,60
Scalebeg.=_KB_MBA,50
Scaleend=_KB_MBE,50
Scalebeg.=mba,50
Scaleend=mbe,50
Dim=Dimension,60
Longtext=Langtext,250
Scanner=ScanMan,80
Driver=ScanDriver,80
CalcFunc=_KB_DBACCESS,120
Dim_Conversion=_KB_MX_PLUS_B,180
Signal=_KB_SignalName,200
Nr=_INDEX,20
Wert=_KB_VALUE,60
MBA Scale=_KB_MBA,50
MBE Scale=_KB_MBE,50
MBA Org=mba,50
MBE Org=mbe,50
CalcFct=_KB_DBACCESS,120
Dim_Transform.=_KB_MX_PLUS_B,180
Comment =_COMMENT,100
[Trend]
VISUALMODE=NORMAL
[APIPRO]
APIPROIFPATH=D:\apipro\apipro42\work
[GEDContextMenu]
Applikation1=MachDas.Bat
[1ANumContextMenu]
AlarmClient=default.eaf
[2ANumContextMenu]
[3ANumContextMenu]
3D-View=View3D.vbs
[nANumContextMenu]
Note: If the first character is a semicolon, this entry is regarded as a comment and will not be
evaluated.
Example of a PlaCo.INI for a PGIM Server:
[PlantConnect]
Server = Yes
GED = No
; If You have a PlantConnect EventDB also, fill in the line below:
; EventServer = <ComputerName>
HDAlertIfLessThanMB = 200
AtHDAlertPassMsgToApp = NetSend.bat
[Server.Settings]
Roh.BasePath = D:\PlantConnect.Roh\
Roh.RAMCacheSize = 200
MaxSignals = 1500
Roh.LifeTimeDays = 1000
WEBPort = 8081
WebClientAutoLogoffAfterMinutes=15
[GED.Settings]
MainPath = C:\PlantConnect
; AddPath = d:\XYZ
[SignalExplorer]
;XtraTools=C:\PlantConnect\PPTShow\PlantCo_d.ppt, PPT-Show
[TREND.ATTRIBUTES]
Signal = _KB_SignalName,200
Nr = _INDEX,20
Wert = _KB_VALUE,60
MBA Skala = _KB_MBA,50
MBE Skala = _KB_MBE,50
MBA Org = mba,50
MBE Org = mbe,50
Dim = Dimension,60
Langtext = Langtext,350
Scanner = ScanMan,80
Driver = ScanDriver,80
BerFkt = _KB_DBACCESS,120
Dim_Umrechnung = _KB_MX_PLUS_B,180
[Trend]
VISUALMODE = NORMAL
1.3.1 Introduction
In PGIM it is possible to configure individual applications or signals with different rights and thus to
provide the following functionalities:
Data security
Data integrity
Different hierarchy levels
Different responsibilities
The "UserManager" serves for managing the PGIM user rights. By means of this "UserManager" the
PGIM system administrator (SysAdmin) can establish new users or user groups, assign passwords
and allocate the different rights to the individual user groups or to the signals.
1.3.2 Functionality
In order to be able to work within PGIM, each user must log on at the database by entering his name
and his password. In PGIM each user can be exactly allocated to a group. There are eight different
groups in PGIM and the group of system administrators. Only the system administrators are allowed to
connect signals from a ScanManager into the database. The system administrators can assign the
names of the eight user groups. All rights which are assigned in PGIM always refer to the user groups,
never to an individual user. In PGIM the rights are assigned to the individual signals. There are three
different rights per signal:
Read The right to read the signal and its values.
Write The right to write and to delete values for the signal.
The right to write and to delete the descriptions for the signal or to delete the signal itself
Confi
(including all archived values).
A specific right for a specific signal can be assigned to a user group, or it can be removed. Such an
assignment may only be performed by the PGIM system administrator (SysAdmin).
For each of the signals, the rights are stored in the database under the property "RTS". The storage is
done in a bit pattern.
RTS Bit pattern
Read Write Confi
PGIM user groups PGIM user groups PGIM user groups
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
3rd byte 2nd byte 1st byte
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Or binary
23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
9388608
4194304
2097152
1048576
524288
262144
131072
65536
32768
16384
8192
4096
2048
1024
512
256
128
64
32
16
8
4
2
1
Thus, for each signal the rights can arbitrarily be set for each of the groups.
• 1 (high) in the bit pattern means that the right has been assigned to the group.
1.4 UserManager
1.4.1 Introduction
The UserManager module manages the PGIM user rights. By means of this "UserManager" the PGIM
system administrator (SysAdmin) can establish new users or user groups, assign passwords and
allocate the different rights to the individual user groups or to the signals.
PCCS001E.GIF
In order to be able to start the UserManager, you must have the rights of a PGIM system administrator
for the indicated database.
To call up the UserManager the first time in order to get the rights of a PGIM system administrator you
must enter the user name "administrator" and the Password "PlantConnect".
PCCS002E.GIF
The figure shows the UserManager screen. The legends at the most important control elements of the
UserManager are defined here to get a uniform nomenclature. The UserManager is operated almost
exclusively via the context menu of the right mouse button or the "Drag and Drop" functionality of
Windows.
2 4 &H4 Invalid AU
1st Byte
The Status Information in PGIM can be different between the connected systems. See the
configuration of the control systems.
1
Only ScanDriver Maestro-UX
1.7.1.1.1 FileTime
- 64bit Integer.
- Beginning time is 01.01.1601.
- A 1 is equal to 100 ns
- Declared in Winbase.h; include Windows.h.
Return code:
0 : DLL proper initialized.
1 : TimeZone.txt not available.
2 : Error in TimeZone.txt, the first or second line is not correct.
3 : Error in TimeZone.txt, one or more of the lines are not correct.
These functions change the date to Unix and back. MyDate must be "double" complement to VB as
"Date"
1.7.1.6 BiasFlag
The BiasFlag is a return code that returns information about summer-(BiasFlag=2) or winter-
(BiasFlag=1) time.
EXCEPTION:
In the case of the Local2GMT-function the BiasFlag has a control function. It is in an output parameter.
This resolves a potential problem with the change between summer and winter time. In that moment
one hour is set two times. You must give the information for example 02:30 summer- (BiasFlag=2) or
winter time (BiasFlag=1) to change in GMT. (If you set BiasFlag=0, this parameter is set to BiasFlag=1
internally).
Meaning:
double mantissa:
14 digits, 13 digits if exponent is high negative
float mantissa:
Normally max. 6 - 7 digits. (6 in high negative exponent ranges)
8 digits only if no decimal places and value less equal 16500000:
Example:
16499998.0 + 1.0 = 16499999.0
16499999.0 + 1.0 = 16500000.0
16500000.0 + 1.0 = 1.65e7
->rounding calculation to 7 digits if above 16500000
16500000.0 + 4.0 = 1.65e7 <- rounded down
16500000.0 + 5.0 = 1.650001e7 <- rounded up
1e25 + 1e20 = 1.00001e25
1e26 + 1e20 = 1.000001e26
1e27 + 1e20 = 1.0e27 <- rounded
Enable gives you the ability to enable or disable (Enabled=no) the maintenance interval. Default is to
enable it.
DayofMonth describes on which day of the month the system will execute the service interval.
Hour tells you at what time of the day the maintenance is executed on the specific day (24hours).
By default this feature for new installations is enabled. For upgrade it is necessary that the file
<PGIM main path>\Server\PlaCo.INI
is not write protected.
For the maintenance interval, PGIM closes the internal IP Server for about 20 seconds. During this
time frame clients will not be able to contact the server. Since clients will use there “retry”-algorithm no
data will be lost.
On redundant servers all clients will be redirected immediately to the redundant partner. For this it is
important, that the maintenance interval is set differently on both servers, e.g. server 1 on the 10th of
each month, server 2 on the 20th.
2 Scanner
2.1 Introduction
The flexible architecture of the PGIM System allows for decentralized data acquisition on what are
generally called scanners. In the scanners, preprocessing of data can be done so that it is possible to
implement quantity, operating hours and switching cycle counters. By means of additional limit values
and the generation of messages resulting from limit value infringements or binary signals, the scanner
becomes a powerful tool.
The scanners are equipped with a configurable temporary storage (buffer) where data can be stored if
the connection to the server is interrupted. In this way, a loss of data, for example, in the case of
network problems, will be avoided. This mechanism allows the decentralized distribution of separate
scanner computers.
PGIM Server
PGIM Scanner
To acquire data, high-capacity scanners are available for various control systems:
The OPC scanner allows you to connect to all control and acquisition systems which provide an OPC
server. OPC is the standard for system connection which is supported by most of the systems.
2.2 ScanManager
2.2.1 Introduction
The ScanManager is the interface and the organizer for the connected ScanDrivers. A ScanDriver is
used for each connected system (data source).
The ScanManager is started as a Windows service and starts automatically at the start of Windows.
When required, the data acquired via the ScanDriver are provided with a time-stamp in the
ScanManager, sorted chronologically and transmitted via a TCP/IP interface to the server (database).
Depending on the system structure, the ScanManager can be installed on the same PC on which the
PGIM server is running. In distributed structures, the ScanManager can also be installed on a
separate PC.
If the connection between ScanManager and server is disrupted, the data will be stored temporarily in
a buffer and transmitted to the server when the connection has been restored. The size of the buffer
(temporary storage) depends on the hard disk storage of the computer.
2.2.2 Settings
Using system settings in an INI file, the ScanManager can be set for different applications. For the
standard application with PGIM, the ScanMan.INI file is not required. Changes in the settings should
be coordinated with ABB in order not to jeopardize the operation of PGIM.
ScanMan.INI
[ScanMan]
# Name of the ScanManager for the database(s)
# Name = demo
# Tolerance band for measured values in % of the measuring range
# DefaultDeadband = 1.0
# Name of the Eventserver
# EventServer = placo_1
# DisableOffscanFlag = TRUE
[Database]
# Portnumber = 4242
Protokoll = 1
[Name of Database]
Buffersize = 1000000
"Name = demo"
In addition to the KKS (power plant identification system) or AKZ (plant identification system)
description, the signal name of a PGIM signal also includes the name of the computer on which the
ScanManager has been installed. If this name is changed, it is possible to indicate the desired name in
the ScanMan.ini file under the entry "Name =". The name entered here overwrites the network name
of the computer, which is used by default for PGIM. Any free name can be used here.
Warning: The name of the ScanManager must be unique for PGIM.
"DefaultDeadband = 1.0"
This parameter sets a tolerance band when signals are connected for the first time. This tolerance
band is overwritten by settings done via the SignalExplorer.
"EventServer = placo_1"
If PGIM is to be used with an event management, it is necessary to indicate the name of the computer
on which the event acquisition is running (see the Event management chapter).
"DisableOffscanFlag = TRUE"
To activate this feature for a specific signal, you need to enable the leakage flow suppression. Do this
by adding a value in the “range” test box of the signal explorer’s ScanManager tab.
[ScanMan]
The restart file contains additional attributes for the started signals. The old file will be automatically
converted to the new format.
The file extension changes to *.fdb.
2.3 ScanDriver
2.3.1 Introduction
ScanDrivers are available for different distributed control systems to acquire process data. These
ScanDrivers are always adapted to the connected data source. They control the communication to the
control and data acquisition systems. The transferred data is edited to transmit in a standard form to
the ScanManager.
Additional ScanDrivers can be implemented for new systems.
In addition to on-line data transfer, manual inputs into the system (for example for laboratory data) are
also possible. The virtual ScanDriver is available for the management of signals generated locally in
PGIM.
2.4.1 Introduction
The virtual ScanDriver generates signals that are captured by the PGIM system (for example
Technical calculations). The configuration of the signals is performed via an associated configuration
file, which contains information on the signals.
To edit new signals in the Virtual ScanDriver (VSD) there is a VSD-Editor available in the
SignalExplorer. Refer to the configuration for the VSD-Editor in the SignalExplorer chapter.
MS Windows
PGIM Server
PGIM ScanManager
VSD ScanDriver
Applications such as
- PGIM Technical Calculations
- PGIM Manual Input
- Customer specific applications
2.4.2 Installation
By selecting the virtual ScanDriver in the user-defined installation of PGIM, the following subfolder will
be created:
…\PlantConnect.BIN\Scanner\ScanDriver
The ASCII-ScanDriver is listed here with the name VSD.DLL.
2.4.2.1 Configuration
In addition to the driver, one or several configuration files are required to provide necessary
information on the available signals to the PGIM system.
Te configuration folder exists in the setup system.
....\PlantConnect.BIN\Scanner\Konfi_VSDScanner\
Lower-level folders are interpreted as logical ScanDrivers, where the folder name corresponds to the
ScanDriver name. By default the folder name is VSD.
In this folder, a folder with the name "KONFI" must exist where the signal configuration file
KONFI.CSV resides.
To ensure that after a restart of the ScanManager, the last values of the scanner will be available
again, the VSD.rst file is created in the folder \PlantConnect.SYS\SysKonfi\Scanner\VSD. In this file,
all current measured values are saved in a binary form. When starting the scanner this information is
obtained and the time-stamps will be updated according to the algorithm described above.
[Main]
DelayTime = 90
PGIM Server
PGIM ScanManager
System ScanDriver
PGIM System
2.5.1 Installation
Choose the System ScanDriver in the user defined installation of PGIM and the following folder will be
created:
....\PlantConnect.BIN\Scanner\ScanDriver
The "System ScanDriver" has the name SystemScanner.dll.
In the scanner neighborhood the System ScanDriver is set with the name "SYS".
These parameters are available:
CPUUsage : Used CPU in percent
Usedspace_drive X : Used disc space on drive X in MB
Freespace_drive X : Free available space on drive X in MB
UsedPhyMemory : User physical memory in Percent
XXXXXXX_Ping : Reply time of the TCP/IP connection in ms
PhysMemory : free physical memory in MB
2.5.2 SystemScanner.ini
Settings are set in the SystemScanner.ini file. Up to 49 signals are possible to call via ping. Each of
these destinations must be reachable by TCP/IP. The network address is part of the signal name.
LAN (TCP/IP)
PGIM Server
LAN (TCP/IP)
Reading of current
Creating of two values
alternating signals
in the Scanner
PGIM ScanManager
WatchDog ScanDriver PGIM
2.6.1 Installation
Choose the WatchDog ScanDriver in the user defined installation of PGIM and the following folder will
be created:
....\PlantConnect.BIN\Scanner\ScanDriver
The "WatchDog ScanDriver" has the name WatchDogScanner.dll.
In the scanner neighborhood the System ScanDriver is set with the name "WDS". With the
WatchDogServer application it is possible to control the connection between the Scanner and the
Server.
In the case of one scanner it is enough to have one WatchDog signal. See the WatchDogServer
configuration for details.
In the case of two parallel scanners, each scanner can have in the configuration of the
WatchDogServer one signal. One is in use for one Scanner, the second for the parallel scanner.
For Example:
From scanner1 WatchDog01 is in use
From scanner2 WatchDog02 is in use
Special case: In the case of parallel Scanners, copy the restart file from one scanner to the other. This
will set back the settings.
2.7.1 Introduction
For connection of PGIM to the distributed control system Contronic 3 (C3), a driver is available for the
communication on the C3 cubicle bus.
Bus-capable C3 modules (MZ03, XU03/04, XU13/14, and SL04/05) can be addressed via the C3
cubicle bus and transmit signal data.
The PGIM PC is linked via a serial connection (V24/OWG transducer/OWG cable/HW81) with the C3
module HW81 that performs the communication between cubicle bus and V24 interface. As the C3
signals do not have time-stamps, each signal being transmitted is provided with a time-stamp in PGIM.
In the control system, no signal names have been assigned to the C3 signals. For processing in
PGIM, a signal name, text, dimension and measuring range must be added to each signal.
PGIM Server
PGIM ScanManager
Contronic 3 ScanDriver
Multiplexer/ PGIM
converter
HW81/82 HW81/82
no. 1 no. 16
Q535 BUS
NB
Txxx
T007
C100
C101
C102
C103
C104
C105
C106
C107
C108
C109
C110
C111
C112
C113
C114
C115
T008
Transmit block 7
shall be connectd
For the connection, transmit block 007 must be noted as follows in the
Excel configuration file.
Excel configuration
For the configuration, an Excel workbook is available which must be processed plant-related. For each
module, an Excel spreadsheet is opened. It is useful to choose the name of the module as the
spreadsheet name.
Structure of a configuration spreadsheet:
The division of the Excel spreadsheet is preset. The columns must not be changed. The first 7 lines
include descriptive information for the columns. In the 8th line, the configuration of the communication
begins.
The configuration of communication blocks in the connected Contronic 3 modules is described in the
C3 configuration.
2.8.1 Introduction
For connection of PGIM to the ABB control systems Contronic-E/EK (CEK), Contronic 3 Information
(C3I) and Contronic-P (CP), a Conlink-ScanDriver is available which organizes the serial
communication via the Conlink protocol with the CEK, C3I and CP operator stations. The physical
connection between the systems is established via serial interfaces (V24) between PGIM Scanner-PC
and the respective operator stations of the control systems (PCV24 or PCV02).
The connection of signals is based on a concept, which makes available to the user all accessible
signals of the plant after data balancing has been performed once. These signals are determined via a
short configuration procedure of the Contronic system and provided with further information in a
connection run.
Due to the fact that the capacity of the serial interfaces of the Contronic system is limited, the user
must decide, based on PGIM, which signals will really be selected from the total number of signals.
The user can make, for each interface, a selection from all available signals. The total number of
signals is stored after the connection run in the file "CONFI.TXT".
If PGIM is used as a replacement for a previous system (ConVisa), the configuration can be used for
connection to PGIM.
PGIM PGIM PGIM
Client Client Client
PGIM Server
PGIM ScanManager
Conlink ScanDriver
PGIM
Multiplexer
Contronic
Serial interface reading / writing of
current process values
The path entry for ConLinkServer indicates the path where the program "ConlinkServer.exe" exists.
The name indicated in "CONLINK-LINE X" is added in PGIM as a ScanDriverName to the connected
signal. Refer to chapter 1.5
Note:
We strongly recommend that you use only characters accepted by Windows operating
system to create a name. Use these characters to create folders with the Windows
Explorer.
To create this CONFI.TXT file, further programs are required.
Contains a software driver for the communication as well as the configuration tools for editing data.
The file "ConlinkServer.exe" is installed as service under the Windows utilities. Installation is
performed via a DOS box (On the taskbar, click the Start button, and then click Run). The program
ConlinkServer.exe is called with the parameter –install.
Call in the DOS box:
C:\PlantConnect.BIN\Scanner\ConlinkNT\ConlinkServer –install
In the same folder, the file conlinkx.ini exists which includes settings for the communication via
the serial interface.
Structure of the file conlinkx.ini
[CONLINK-LINE 1]
PORT=2 # COM1 = 1, COM2 = 2, etc.
TIMESYNC=TRUE
UNIT=4 # Station number
SYSTEMTYPE=CK # CK = CONTRONIC EK or 3I, CP = CONTRONIC P
SYSTEMVERSION=7 # Software version, 7 or 8 => 30 or 100 blocks
###########################################################################
#
# File : BLOCKDEF.DAT
# Location : ...\PlantConnect.BIN\Scanner\ConLinkNT\
# Description : Contronic blockdefinition as information for the Conlink
# communication service.
# Creation : 17.12.1996 (Gil)
#
###########################################################################
[Line 01]
[Line 02]
# Table on unit 3 Channel 8
# Note: Each Conlink inteface line can transfer 2 blocks per second
# block blocktype direction cycletime
# [0..100] [0:b,1:a,2:c] [0:rd,1:wr] [sec]
# -------------------------------------------------------------------------
00 1 0 5.000
01 0 0 5.000
02 2 0 5.000
03 1 0 5.000
04 0 0 5.000
05 2 0 5.000
06 1 0 5.000
07 0 0 5.000
08 2 0 5.000
09 1 0 5.000
F-T: DOKUF
STORE
EXECUTE (Y/N) <Y>
SELECTION: Y
STN-NO.: *
FCTTYPE *
ASCII *
PL.AREA *
SORT: Y
1. ALPHANUM. LENGTH: 20
2. *
3. *
OUTPUT: Y
O/P PERIPH: TALLY
L-UT-F: PPA01 L-LT-F: PPE01
P-UT-F: *
STORE
EXECUTE (Y/N) <Y>
Now the CONLINK-NT Service is in the waiting state. On the Contronic operator station, the
transfer of the file (SHORT) to the Conlink channel must be started.
EXT.MEMORY
COPY
MM
ROOT
FILE: <File of Short configuration procedure > (For Example: SHORT)
CONLINK
TR. : <1>
FILE: <any filename>
The transfer has been terminated when the operator station appears in the menu bar.
Now the communication is deactivated again by stopping in System control/Services:
• First the "PlantConnect ScanManager"
• Second the "CONLINK-NT Service".
On the PGIM PC, a folder "HuB" is automatically created in C:\. The short configuration procedure is
copied to this folder. The name of the file corresponds to the settings in Contronic. For further
processing, the file is renamed into "KDVAX" and copied to the folder
C:\PlantConnect.BIN\Scanner\ConlinkNT\
The information for the data direction must be set to writing from values to Contronic to the value 1.
F-T: DOKUF
SPEICHERN
<Ausführen (J/N) J>
SELEKTIERUNG: J
STN-NR.: n, m, k
FKT.ART *
ASCII *
ANL.BER *
SORTIERUNG: J
1. KURZNAME LAENGE: 20
4. *
5. *
AUSGABE: J
AUSG-GERAET: TALLY
P-UEB-F: PPA01 P-UNT-F: PPE01
S-UEB-F: *
SPEICHERN
<Ausführen (J/N) J>
Now the CONLINK-NT Service is in the waiting state. On the Contronic operator station, the
transfer of the file (KDVAX) to the Conlink channel must be started.
EXT.SPEICHER
COPY
MSP
<Datei: Kurzname Kurzdoku> (Bsp.: KDVAX)
PC-KOPPL (oder CONLINK)
<Spur: 1>
<Datei: Rechner-Nr. Kurzdoku+"_CP" ENTER>
<Ausführen (J/N) J>
The transfer has been terminated when the operator station appears in the menu bar.
The communication is deactivated again by stopping in System control/Services the "PlantConnect
ScanManager" and the "CONLINK-NT Service".
On the PGIM PC, a folder called "HuB" is automatically created in drive C: . The short configuration
procedure is copied to this folder. The name of the file corresponds to the settings in Contronic. For
further processing, the file is renamed into "KDVAX" and copied to the folder
C:\PlantConnect.BIN\Scanner\ConlinkNT\
The information for the data direction must be set to writing from values to Contronic to the value 1.
[CONLINK-LINE 2]
PORT=2
UNIT=3
SYSTEMTYPE=CK
SYSTEMVERSION=7
BAUDRATE=9600
STOPBIT=1
PARITY=ODD
BITS_PER_CHAR=8
TIMEOUT_QUIT=5000
TIMEOUT_ANSWER=10000
REPEAT_PROTOKOLL=5
EVENTBUFFER_SIZE=10
SHORTDOKU=KDVAX
BLOCKDEF=c:\conlinkserver\blockdef.dat ;Standard path C:\PlantConnect.Bin\scanner\conlinkNT\ blockdef.dat
ConlinkScanner.ini
[ConlinkServer]
#Please customize path=
Path=c:\conlinkserver; Standard C:\PlantConnect.Bin\scanner\Konfi_ConlinkScanner
[CONLINK-LINE 1]
Name=Line 00 ; for example: ZLS1_K4
[CONLINK-LINE 2]
Name=Line 01 ; for example: ZLS3_K8
2.9 OPC-Client
2.9.1 Introduction
For the connection of PGIM to an OPC-Server DA (Data Access) according to the OPC-Specification
2.0 an OPC-Client must exist.
The OPC-Scanner is implemented by using the "Data Access Custom Interface Standard Version
2.04". The following interfaces are usable (if the OPC-Server supports this).
IOPCServer
IConnectionPointContainer
IOPCCommon
IOPCGroupStateMgt
IOPCASyncIO2
IOPCAsyncIO
IOPCItemMgt
IConnectionPointContainer
IDataObject
Data transfer is exclusively event driven.
If the OPC-Scanner is installed on the same computer as the OPC-Server, you do not need the
configuration of the DCOM settings.
Known Installations
The following installation were successfully installed:
PGIM OPC-Scanner to IndustrialIT OperateIT Process Portal B (formerly Maestro NT)
PGIM OPC-Scanner to IndustrialIT ControlIT Process Portal F (formerly Freelance 2000)
PGIM OPC Scanner to ABB System 800xA
PGIM OPC-Scanner to IndustrialIT OperateIT Process Portal A (formerly Master Bus P280)
PGIM OPC-Scanner to SynoGate IP300 OPC with Teleperm ME
PGIM OPC-Scanner to WinCC with Siemens PCS
PGIM OPC-Scanner to Simatec with Siemens PCS
PGIM OPC-Scanner to SatLine
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
PGIM
OPC Client ScanDriver
reading/writing of
current process values
2.9.2 Prerequisites
The OPC-Server of the foreign System must be installed. Refer to the manufacturer‘s OPC
configuration.
If the OPC-Server is installed on another PC (Remote-OPC-Server), the following requirements are
needed:
A network connection to the PC, where the OPC-Server is running, must be established.
The Remote-OPC-Server must be known on the local PC (Windows-Registry).
Use the CSV-file to specify the signals that might be connected for the ScanDriver. The syntax
including upper and lower case must be followed strictly.
The "direction" READ or WRITE are both possible
The "unused" parameter is specified for reasons of compatibility to older versions. The entries do not
possess a function for this.
The "OPCdatatype" is registered in the case of the OPC connection with the WAGO system. The
appropriate signal processing maps are defined here. For more information refer to the "OPC-
Scanner at the WAGO I/O SYSTEM 750".
The "updaterate " parameter indicates the maximum speed the signal is to be updated. At the same
time signals are treated with same cycle time in the same OPC list (block).
The "aliasname" parameter can be used in the case of cryptic signal names from the OPC server into
standardized signal names for PGIM to change.
Run Windows Explorer to map the installation folder of the OPC-Server on the remote node as a
network drive. Do a search for the following files:
SymOPCServer.exe
Opcproxy.dll
Opccomn_ps.dll
You will need to create more entries. The following figures are just for informational purposes. Your
installation will be different.
Note: In the case of an Operate IT B update, the GUID may change. That means the client could not
communicate anymore with the OPC Server.
Make sure there is only one version of following DLL’s on your client machine. If there is more than
one, it should not be a problem if they are all same version. If they are not the same version, rename
all but the latest one, which you should keep in the \winnt\system32 folder.
regsvr32 Opcproxy.dll
regsvr32 Opccomn_ps.dll
The following dialog boxes should display:
DllRegisterServer in Opcproxy.dll succeeded.
DllRegisterServer in Opccomn_ps.dll succeeded.
Next invoke dcomcnfg by typing in the Command window (On the taskbar, click the Start button, and
then click Run) dcomcnfg.exe on the OPC Server machine. The following dialogs are displayed.
Select the OPC Server and click the Properties button.
Then click the Security tab and make sure it is configured as follows:
Click Edit for Custom Access Permissions. Make sure that all of the following accounts are there.
Add the account with which the PGIM ScanManager, which starts up the OPC Client, is using. The
Type of Access should be, of course, Allow Access. Click OK and proceed with Launch
Permissions in same way.
Select the OPCEnum and click on the Properties button. Repeat the above-mentioned procedure
exactly the same way, including adding access to the account on which PGIM ScanManager is
running.
Finally, verify the following Default DCOM Configuration Properties. If required, modify the Default
Protocols accordingly. It is possible that your Default Authentication Level is different that what is
shown.
As you have may be noticed, no DCOM configuration settings are required on the machine where
OPC Client (PGIM ScanManager) is running.
The following settings (OPC Scanner) are required to connect successfully to Operate IT B (formerly
Maestro NT):
OPCScanner.ini
[OPCScanner_1]
OPCServerTyp = Remote
RemoteHost = EE81SRV6
OPCServerName = ABBMaestroNT.OPCServer
UpDateRate = 0
Next, install the AC800F OPC Server as documented in the instruction manuals supplied with this
OPC Server. Make a note of the unique defined Resource-ID.
Upload all the required tags from the AC800F system to the OPC Server machine.
Next, install PGIM as licensed. Before you restart, edit the file OPCScanner.ini located in folder:
"....\PIMS\PlantConnect.BIN\Scanner\Konfi-OPCScanner\..."
For example:
Do not forget to insert the noted AC800F Resource-ID in the OPCServerName, separated by a dot.
Copy the previous prepared OPC tag list into the above-mentioned folder. If the name of this file
differs from "Demo.txt" either rename accordingly or modify the file OPCScanner.ini respectively.
Digital Inputs:
Typ 750-400 2-Canal DI, DC 24 V, 3,0 ms
Typ 750-401 2-Canal DI, DC 24 V, 0,2 ms
Typ 750-402 4-Canal DI, DC 24 V, 3,0 ms
Typ 750-403 4-Canal DI, DC 24 V, 0,2 ms
Typ 750-405 2-Canal Digital Input, AC 230 V
Typ 750-406 2-Canal Digital Input, AC 120 V
Typ 750-408 4-Canal Digital Input, DC 24 V, 3,0 ms
Typ 750-409 4-Canal Digital Input, DC 24 V, 0,2 ms
Typ 750-410 2-Canal Digital Input, DC 24 V, 3,0 ms
Typ 750-411 2-Canal Digital Input, DC 24 V, 0,2 ms
Typ 750-412 2-Canal Digital Input, DC 48 V, 3,0 ms
Typ 750-414 4-Canal Digital Input, DC 5 V, 0,2 ms
Typ 750-415 4-Canal Digital Input, AC/DC 24 V, 20 ms
Analoge Input:
Typ 750-452 2 Canal Analog Input, 0-20 mA Diff
Typ 750-454 2 Canal Analog Input, 4-20 mA Diff
Typ 750-456 2 Canal Analog Input, +-10 V Diff
Typ 750-461 2 Canal Input Pt 100, RTD
Typ 750-462 2 Canal Input Thermo
Typ 750-465 2 Canal Analog Input, 0-20 mA single-ended
Typ 750-466 2 Canal Analog Input, 4-20 mA single-ended
Typ 750-467 2 Canal Analog Input, 0-10 V single-ended
Typ 750-468 4 Canal Analog Input, 0-10 V single-ended
Typ 750-469 2 Canal Eingang Thermo Drahtbruch
Typ 750-472 2 Canal Analog Input, 0-20 mA single-ended 16 Bit
Typ 750-474 2 Canal Analog Input, 4-20 mA single-ended 16 Bit
Typ 750-476 2 Canal Analog Input, DC +-10 V single-ended
Typ 750-478 2 Canal Analog Input, DC 0-10 V single-ended
The data in the analog inputs are given as raw values from the WAGO-OPC Server. The scaling is
done in the Scanner. For this to work properly in the signal configuration file the parameter "OPC-
Datentyp (VT_*)" must be set. For Example:
The "OPC-Data type" parameters of the other analog inputs are similar.
The data in the analog values of the WAGO OPC server are raw values. These values must be
transferred by scaling. That scaling takes place in the scanner.
The binary signals are clearly and completely described in the ItemID. The VT_BOOL parameter is not
necessary.
For Example:
Binaer;Random.Boolean;READ;Random value.;;;;;;;;1000;Alias Name 01;
Analog;Saw-toothed Waves.Int1;READ/WRITE;Saw-toothed wave.;-100;100;;;;;;100;
The input in column 11 can set in WinCC Special format like the following example:
VT_WINCC0 is set for conversion without offset and VT_WINCC512 for conversion with offset 512.
2.10.1 Introduction
For the connection of PGIM to the ABB control system PROCONTROL P an XTC-ScanDriver is
available. It organizes the network communication with a PBS30 station of the PROCONTROL P
system.
At this time only the transfer of online data (read and write) is implemented.
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
XTC ScanDriver
PGIM
Reading / writing of
current process values
POS 30 LAN
XTC Interface
Stream Mode
PROCONTROL P Bus
Analog.csv
alphanumeric;longtext;MRS;MRE;dimension
50AP15E201XQ50; LEISTUNG HT;0,00;330,00;MW
50BA02E301XQ50; LEISTUNG SCHIENE BA/BB;0,00;30,00;MW
50BL05E301XQ50; LEISTUNG SCHIENE BL/BM;0,00;30,00;MW
50NA14T004XQ50;T SPEISEWASSER HI ECO 3;0,00;600,00;GRD C
50NA51T005XQ50;T DAMPF V HD-KUEHLER 1.1;0,00;600,00;GRD C
50NA52T005XQ50;T DAMPF V HD-KUEHLER 1.2;0,00;600,00;GRD C
Binary.csv
alphanumeric;longtext;coming;going
50NB40D010XA01; KESSELUMWAELZPUMPE;EIN;AUS
50NG00D010XA01; FRISCHLUFTGEBLAESE;EIN;AUS
50NG00D021XA01; OEL-PP1 FL-GEBLAESE;EIN;AUS
50NG00D022XA01; OEL-PP2 FL-GEBLAESE;EIN;AUS
Packedbool.csv
alphanumeric;longtext;datatype
HNA20 AS001 XC00;Checkb. cntr.FGD ind.drgt;23
HNA20 EA100 XA00;;19
HNB00 DP001 XR00;Checkback MST master cntr;22
HNB00 DU001 XR00;Checkback limit boil. 2+3;22
HNC01 AA001 XB00;;21
HNC01 AN001 XB00;;21
HNC01 AP001 XB00;Rückmeldungen;21
HNC01 AP002 XB00;Rückmeldungen;21
20;XA40;11
20;XA01;10
20;XA97;9
20;XA98;8
20;XA43;7
20;XA95;6
20;XA96;5
20;XA93;4
20;XA94;3
20;XA91;2
20;XA92;1
21;XB21;15
21;XB22;14
21;XB31;13
21;XB32;12
21;XB40;11
21;XB91;9
21;XB92;8
21;XB43;7
21;XB46;6
21;XB01;5
21;XB02;4
21;XB45;3
21;XB42;2
22;XR07;13
22;XR41;12
22;XR40;11
22;XR02;10
22;XR05;9
22;XR06;8
22;XR44;1
23;XC21;15
23;XC22;14
23;XC31;13
23;XC32;12
23;XC40;11
23;XR02;10
23;XR05;9
23;XR06;8
23;XC43;7
23;XC46;6
23;XC01;5
23;XC02;4
23;XC45;3
23;XC42;2
23;XC44;1
23;XC41;0
Write.txt
# Signal name
#
50NA14T004XQ50
50NA51T005XQ50
50NA52T005XQ50
50NG00D021XA01
The PGIM ScanManager gets all event-driven measured values from the PBS30. The configuration
files "analog.csv" und "binary.csv" are used to select the desired signals for the measured values
which must be send via the PGIM ScanManager to the PGIM database.
Configuring the back-signals is made by the files packedbool.csv and packedboolmap.txt. In the file
packedbool.csv the allocation of a signal to a data type takes place. This serves then as code into the
file packedboolmap.txt, from which then the bit locations and signal flags of the single bits come out.
2.10.4 XTCScanner.ini
Appropriate INI-files can be stored in ....\PlantConnect.bin\Scanner\Konfi_XTCScanner. The following
entries are possible:
[PBS30]
TimeSync = 1 time synchronization via XTC interface; 1=on 0=off
SnapShotCycle = 300 additionally cyclic request in seconds or 0 for no cyclic request
TimestampDelay = 120
#[PBS30-XTC 2] additional PBS30 Gateways
The entry TimestampDelay can control cyclic updating of the time-stamps in the XTC scanner.
The cyclic updating operates in a similar manner as the virtual ScanDriver, however the data source is
the PBS.
2.11.1 Introduction
Apart from the Symphony-ScanDriver (P-Protokoll-ScanDriver; O-Net, Melody, OperateIT B0/B1), a
connection can be established between the Maestro workstation and PGIM so that data is returned to
the control system. Current data can also be obtained from Symphony-Maestro.
As a physical interface, a network connection between the PGIM-PC and the BLE network is used.
The plant management level network is Ethernet with TCP/IP protocol. (See the Symphony
configuration)
PGIM
PGIM PGIM
Client
Client Client
LAN (TCP/IP)
Symphony
reading/writing of
current values
Symphony Maestro-UX
Operator Station
reading of process
values from history
LAN (TCP/IP)/BLEnet
For Example:
[Redundancy]
# Redundancy pair for the WSR1
WSR1 = WSR3
For Example:
ll list long Indication of files and folders in the long form
ll *.dat
mkdir make folder Creates a folder
mkdir temp
rmdir remove folder Deletes a folder
rmdir temp
rm remove Deletes files
rm *.old
cd change folder Changes to a folder
cd temp
The file Pexall.tar is transferred via FTP (binary file transfer) from the PC to the workstation.
#
# Kerberos (Project Athena/MIT) services
#
klogin 543/tcp # Kerberos rlogin -kfall
kshell 544/tcp krcmd # Kerberos remote shell -kfall
ekshell 545/tcp krcmd # Kerberos encrypted remote shell -kfall
--------------------------------------------------------------------------------
This procedure checks whether the process still runs netapisrv. If it runs, then everything is clear.
If not, then stop the program with the "Terminate APIM TA01" command and start with "Start APIM
TA01".
2.12.1 Introduction
The Symphony control system by ABB can be connected in two different ways. A fast and high-
capacity interface is set up via the P-Protocol-ScanDriver. As a physical interface, a network
connection between the PGIM PC and a CCO star coupler (see Symphony configuration) is used.
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
PProtocol ScanDriver
PGIM
Symphony
LAN (TCP/IP)
Onet (PProtocol)
2.12.2 Installation
On the computer where the PGIM ScanManager has been installed, the corresponding ScanDriver will
also be installed. By selecting the correct ScanDriver in the user-defined installation of PGIM, the
following subfolder is created:
C:\PlantConnect.BIN\Scanner\ScanDriver
The folders listed here include the drivers for the respective connections.
The Symphony ScanDriver is listed here with the name PProt-Scanner because it communicates via
the P-Protocol of the Symphony-Operation-Network. In the subfolder "PProtScanner", the driver DLL
"pprotscanner.dll" is included.
2.12.3 Configuration
In addition to the appropriate driver, a configuration file is required which provides the PGIM system
with all necessary information on the signals that are available in the Symphony control system.
In the set up system, the configuration file "Pconnect.txt" resides in the folder:
C:\PlantConnect.BIN\Scanner\Konfi_PprotScanner\
The configuration file includes all information on the signals which can be connected. The most
important ones are signal name (KKS or AKS), long text, dimension, measuring range start and end. If
changes are made in the control system, it may be necessary to update the configuration file.
An example of a configuration file:
#name;type;selektor;skz;comi;;mba;mbe;itxt;otxt;dimtext;kurztext;langtext;anlagenbereich;datatype;Aliasname
31MBA40EE010;$CSCBIN3;I1;XA01;ep121g09;;;;Ein;Ein;;31MBA00;TS Abblaseklappen;GT 31MBA00;31;Alias001
31MBA40EE010;$CSCBIN3;I2;XA02;ep121g09;;;;Aus;Aus;;31MBA00;TS Abblaseklappen;GT 31MBA00;31
31MBL20EE010;$CSCBIN3;I1;XA02;ep121g09;;;;Aus;Aus;;31MBA00;TS Klappe Luftansaugung;GT 31MBA00;31
31MBP01EC001X;$CSCBIN13;I1;XA11;ep121g09;;;;>LFZ;>LFZ;;31MBP00;UGS Erdgasversorgung;GT 31MBP00;31
31MBV01EC001;$CSCSFC;I4;XA11;ep121g09;;;;>LFZ;>LFZ;;31MBV00;UGS Ölverso/WelDreh;GT 31MBV00;31
40HAD00EB100;$CECOA;I1;XA64;ep029a29;;;;Soll<Ist;Soll<Ist;;40HAD00;UmsLogik Regelkessel 1-3;RK 40HAD00;31
40HAD00EB100;$CECOA;I2;XA66;ep029a29;;;;Soll>Ist;Soll>Ist;;40HAD00;UmsLogik Regelkessel 1-3;RK 40HAD00;31
The meaning of the different bits depends on the control system used. This can be found in the
respective configuration.
2.13 ASCII-File
2.13.1 Introduction
The ASCII-Import-ScanDriver imports measured values for different signals from one or several files.
With the function OVERWRITEHIST, the measured values are written directly into the database,
bypassing the ScanManager. The configuration of the signals is performed via a configuration file
where the information on the signals is available. The measured values reside in a value file, which is
evaluated and deleted after the import of the measured values.
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
PGIM
ASCII ScanDriver
Remote System
reading of current / historical
File Transfer
of ASCII Files process values
LAN (TCP/IP)
2.13.2 Installation
By selecting the ASCII-ScanDriver in the user-defined installation of PGIM, the following subfolder will
be created:
C:\PlantConnect.BIN\Scanner\ScanDriver
The ASCII-ScanDriver is listed here with the name ASCIIScanner.DLL.
2.13.3 Configuration
In addition to the driver, one or several configuration files are required to provide all the necessary
information on the available signals to the PGIM system.
In the set up system, this configuration folder exists:
C:\PlantConnect.BIN\Scanner\Konfi_ASCIIScanner\
Lower-level folders are interpreted as logic ScanDrivers, where the folder name corresponds to the
ScanDriver name.
Here the values are transmitted to the database server with the host name MIP311.
Another entry can be the name of the value file from which the measured values are to be read. This
entry is optional. If no entry exists, the file WERTE.CSV is searched by default in the folder WERTE.
For Example:
[MAIN]
Wertefile = \PlantConnect.BIN\Scanner\Werte_ASCIIScanner\BSP_ASC\Werte.csv
For Example:
;#class modul application;09.12.98 11:16:31
;#SignalKey;TimeStamp;Value;Status;FlagSommerWinterzeit
1LAB10CT001 XJ01;01.11.1998 08:50:00.100;1,2; 0;W
1LAB10CT001 XJ01;01.11.1998 09:20:00.020;2,5; 0;W
2.14.1 Introduction
The difference between the AsciiScanner and the AsciiOnlineScanner is that the AsciiOnlineScanner
is much faster than the AsciiScanner. The restriction to the AsciiScanner is that the
AsciiOnlineScanner can not overwrite values in the database.
Two files are important for the AsciiOnlineScanner. The value file and the signal configuration file.
PGIM PGIM PGIM
Client Client Client
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
PGIM
ASCII OnlineScanDriver
Remote System
reading of current / historical
File Transfer
of ASCII Files process values
LAN (TCP/IP)
werte.csv
#SignalKey;TimeStamp;Value;Status;FlagSommerWinterzeit
LSTWKGES_Z21;01.07.2002 08:50:00.100;1,2;0;W
LPREAGES_Z21;01.07.2002 09:20:00.020;2,5;0;S
206_G_____ZW_P;01.07.2002 09:50:00.003;2,6;0;
OSBEG_WETTWISK;01.07.2002 10:20:00.400;1,6;0;
CISCO SYSTEMS, INC. 07 ac 01;01.07.2002 10:50:00.050;1;0;
LSTWKGES_Z21;01.07.2002 10:50:00.100;1,2;0;W
OSBEG_WETTWISK;01.07.2002 10:51:01.000;1,6;0;
ABB can adjust each ASCII format for the AsciiOnlineScanner on request.
Type; Name; Direction; Description; MBA; MBE; Dimension; Status text OFF; Status text ON; a; b;
Alias name;
Valuefile
ValueFileFormat
Separator
DeleteAfterRead
EndOfLineChar
FTPServer
FTPUser
FTPPasswd
Pollcycle
RelStarttime
Explanation:
Valuefile
Name of the value file. If this information missing, the file
Konfi_AsciiOnlineScanner\FreeName\werte.csv is active.
Wildcards (? and *) are allowed in the file name. In the case of wildcards the files which are included
will be imported in sorted order.
For Example:
Valuefile = E:\PIMS\Scanner\Konfi_AsciiOnlineScanner\52756\GAS\EM_01.TXT
ValueFileFormat
Designate the parser to be used. If this information missing, the standard format is used.
Separator
Designate the separator to be used. If this information missing, the standard format Semicolon is
used.
For Example:
Separator = :
Separator = |
DeleteAfterRead
Here you can define that the file should be deleted after reading. Possible inputs are true or false. If
this information missing, the file will be not be deleted.
For Example:
EndOfLineChar
Define the character in use for the end-of-line information. This information can be in decimal or hex
notation. If this information missing the character 0x0d (13) is active.
For Example:
EndOfLineChar = 0x0a
EndOfLineChar = 0x0d
FTPServer
If this entry is defined, the value files are read from a server with the ftp. At the same time this
parameter must also define the entries for ftp user and FTP Password. This entry does not have a
default value.
For Example:
FTPServer = unixserver1
For Example:
FTPUser = user1
FTPPasswd = XXXX
Pollcycle
Define the cycle rate to search for files if no notification by the operating system is possible. The cycle
rate is indicated in seconds. If the entry is missing, then 60 seconds are used.
For Example:
Pollcycle = 60
RelStarttime
Defines a point of reference for the polling cycle. This allows you to look every 8 minutes after the full
hour for files. If the entry is missing, then midnight is used
For Example:
RelStarttime = 00:08:00
2.15 Teleperm-XP
2.15.1 Introduction
For the connection between PGIM and the control system Teleperm-XP from Siemens a separate
driver is available that allows you to read process data from the Teleperm-XP system and write values
from PGIM to the Teleperm-XP system. The PGIM Scanner TXP/XU is connected to the TXP/XU
gateway from Siemens.
PGIM PGIM PGIM
Client Client Client
PGIM Server
PGIM ScanManager
PGIM
TXPXU ScanDriver
reading / writing of
current process values Siemens
Network (TCP/IP)
TXP-XU
Terminal Bus
2.15.2 Installation
For the installation of the TXP/XU Scanner a network connection to the TXP/XU gateway from
Siemens must be established. The PGIM database may be located either on the same PC as the
TXP/XU Scanner or on a different one connected via an additional network card. The PGIM Scanner-
PC is able to buffer the incoming data in case the network connection to the PGIM Server that stores
the data is disturbed.
The PGIM ScanManager with the TXP/XU ScanDriver is installed on the PC. This PC is connected on
one side to the TXP/XU gateway station by a crossover cable. This is a direct connection between the
first network card of the PGIM Scanner PC and the network card of the TXP/XU gateway. The
connection of the PGIM Scanner to the PGIM Server is established using a second network card
The PGIM Scanner directly reads the values from the TXP/XU gateway. Values from PGIM to the
TXP/XU gateway station are written by a cyclic file transfer (with a cycle rate of approximately 5
seconds) to both redundant TXP process station "PUa" and "PUb".
If the network connection between the PGIM Scanner and the PGIM Server is lost, the scanner stores
the values read from the TXP/XU gateway on the local hard disk (buffering of the scanner data)
2.15.3 Configuration
The PGIM TXP/XU -ScanDriver creates the following folder structure during the installation:
....\PlantConnect.BIN\Scanner\Konfi_TXPXUScanner
In this folder a subfolder with the desired name of the ScanDriver must be created manually for
example "PBS30". Within this subfolder the following configuration files are expected to contain the
analog and binary signals to be read.
Each subfolder is interpreted as the name of a gateway station, for example
PlantConnect.Bin\Scanner\Konfi_TXPXUScanner\h01xu1
The name "h01xu1" is used as the name of a connected gateway station. This name must be
configured as an IP address, either by a name server or in the file "hosts" of the Scanner PC. The
command "ping" with the name "h01xu1" must be successful. Both these files are created at the
Siemens system and transferred to the Scanner PC by FTP.
In the subfolder "h01xu1" two files are located named "descr.txt" and "Signal2.txt". Both files together
describe all signals that can be read by this Scanner.
If values must be written to the Siemens system, two additional files named "analog_write.txt" and
"binary_write.txt" are necessary. Inside these two additional files the signals to which values must be
written are defined.
The file "TXPXUScanner.ini" must exist in the folder
"PlantConnect.Bin\Scanner\Konfi_TXPXUScanner". In this file the relevant information for the
communication is specified.
For Example:
[h01xu1]
# separator in the file Signal2.txt (this file contains the scaling information)
Seperator = |
# In general two gateway stations (XU) could exist, but this is not tested
Redundancy =
# ID for the communication with the XU, value defined during configuration of XU
ClientID = 10
# Name (IP-adress) of the process stations (PU)s, two which the write files must # be
transferred. The PU can be redundant, therefore two entries
ProcessUnit1 = pu35a
ProcessUnit2 = pu35b
# Username and password for the FTP connection
FTPUser = user
FTPPassword = password
# Name of the write files
WriteFileAnalog = analog.dat
WriteFileBinary = binary.dat
Explanation:
Lines starting with the character "#" are comments.
[h01xu1]: Name of the section in the ini-file. This must be the same as the name of the gateway
station (XU). The parameters for the respective scanner are defined in this section.
Separator: Separator of the columns in the file "Signal2.txt" that contains the scaling information.
All the configuration files are generated within the TXP system. These files must be obtained from the
customer.
The following configuration files are needed:
....\PlantConnect.BIN\Scanner\Konfi_TXPXUScanner\ha_xu1\
analog_write.txt
binary_write.txt
descr.txt
Signal2.txt
The file "Signal2.txt" forms an addition to the file "descr.txt" and contains the measuring ranges of the
different signals. The last column in the file "Signal2.txt" is not needed for the connection. The file is
delivered by Siemens.
- Signal2.txt
00 AZ01 E801 |XE01 | -400 | 400 | 1
00 AZ01 E802 |XE01 | -400 | 400 | 1
00 ES01 E001 |XQ02 | 0 | 50 | 100
00 ES01 E001 |XQ01 | 0 | 50 | 0.5
00 ES01 M001 |XQ01 | 0 | 120 | 100
00 HW05 U950 |XQ01 | 0 | 20000 | 1
00 HW05 U957 |XQ01 | 0 | 20000 | 1
00 VC65 F001 |XQ01 | 0 | 300 | 1667
00 VC65 P001 |XL01 | 0 | 2.0 | 500
00 VC65 P001 |XQ01 | 0 | 2 | 100
00 WS01 M001 |XQ01 | 0.5 | 50 | 500
The PGIM TXP/XU Scanner uses the following DLL as the ScanDriver:
....\PlantConnect.Bin\Scanner\ ScanDriver\TXPXUScanner.dll
2.16.1 Introduction
For the connection between PGIM and the Harmony control system a separate driver is available that
allows you to read process data from the Harmony system. The PGIM Scanner INFI90 is connected to
the Harmony network communication coupler using the semAPI Software (see the picture below).
The PGIM INFI90 Scanner therefore requires:
• The SemAPI Run-time kit Version 2.1, to be installed on the PC where the PGIM INFI90 Scanner
is running including the license for data acquisition (DA)
LAN (TCP/IP)
PGIM Server
PGIM ScanManager PGIM
INFI90 ScanDriver
sem API
Harmony
reading and writing of INFI90
RS 232 C current process values
or SCSI
INICI03
Interface
CNET
• The supported interface on the Harmony side. Currently only the INICI03 interface is tested and
supported.
2.16.2 Installation
For the installation of the PGIM INFI90 Scanner a RS-232-c or SCSI connection to the INICI03
interface must be established. The PGIM database may be located either on the same PC as the
INFI90 Scanner or on a different one connected via an additional network card. The PGIM Scanner-
PC is able to buffer the incoming data in case the network connection to the PGIM Server that stores
the data is disturbed.
2.16.3 Structure
On the PC the PGIM ScanManager with the INFI90 ScanDriver is installed. The INFI90 ScanDriver
uses the semAPI client function library. It gets the process values from the INICI03 Interface via a
device driver. The connection of the PGIM Scanner to the PGIM Server either uses local TCP/IP (if the
PGIM server is installed on the same PC as the ScanManager) or network TCP/IP.
Structure:
PGIM PC
PGIM Server
Local TCP/IP
PGIM ScanManager
INFI 90 ScanDriver
semAPI software
RS-232-C
Interface INICIO3
If the network connection between the PGIM Scanner and the PGIM Server is lost, the scanner stores
the values read by the INFI90 ScanDriver on the local hard disk (buffering of the scanner data)
2.16.4 Configuration
The PGIM INFI90-ScanDriver creates the following folder structure during the installation:
....\PlantConnect.BIN\Scanner\Konfi_INFI90Scanner
In this folder a subfolder with the desired name of the ScanDriver must be created manually for
example "INFI90".
Every subfolder is read by the driver and the name is used as a ScanDriver names, for example:
....\PlantConnect.bin\Scanner\Konfi_Infi90Scanner\INFI90
Results in a ScanDriver named INFI90.
[ProcessVariable]
[SetPoint]
[ControlPoint]
[RatioIndex]
[Analog]
[StationStatus]
[Digital]
[SetPointOutput]
[ControlOutput]
[RatioIndexWritten]
[StationMode]
[AnalogReport]
[DigitalReport]
[ModuleStatus]
[RCM]
[RCMReport]
[StationReport]
[RMSC]
[RMSCReport]
[Station]
[Real4AnalogRead]
[Real4AnalogReport]
[ExtendedModuleStatus]
[EnhancedTrend]
[DAANG]
[AsciiString]
[MSDD]
[DD]
[RMC]
[DADIG]
[TextSelector]
[HarmonyAnalogInput]
[HarmonyAnalogOutput]
[HarmonyDigitalInput]
Example of a INFI90Scanner.ini:
[INFI90]
LogICI = 1
TimeSync = 0
EstablishDelay = 50
OnlineStart = 1
ExceptionReportScreening=1
[ProcessVariable]
F_VALUE = 1
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[SetPoint]
F_VALUE = 1
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[ControlPoint]
F_VALUE = 1
# quality
Q = 0
# limit alarm
[RatioIndex]
F_VALUE = 1
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[Analog]
F_VALUE = 1
# quality
Q = 1
# limit alarm
LA = 1
# deviation alarm
DA = 1
# points red tagged
RT = 1
# point tracking
PT = 1
# calibration correction values
CCV = 1
[StationStatus]
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# process variable quality
PVQ = 0
# points red tagged
RT = 0
# set point tracking
[SetPointOutput]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[ControlOutput]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
[RatioIndexWritten]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[StationMode]
#
UC_STATION_MODE = 0
[AnalogReport]
#
F_VALUE = 1
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[DigitalReport]
# quality
Q = 0
# limit alarm
LA = 0
# value
V = 1
[ModuleStatus]
[RCM]
# quality
Q = 1
# alarm
ALM = 1
# tagged
TAG = 1
# output value
OV = 1
# logic set input received
SI = 1
# set permissive input received
SP = 1
# logic reset input received
RI = 1
# override
OR = 1
# feedback
FB = 1
# set command received
SC = 1
# reset command received
RC = 1
[RCMReport]
# quality
Q = 0
# alarm
ALM = 0
# tagged
TAG = 0
# output value
OV = 0
# logic set input received
SI = 0
# set permissive input received
SP = 0
# logic reset input received
RI = 0
# override
OR = 0
# feedback
FB = 0
# set command received
SC = 0
# reset command received
RC = 0
[StationReport]
[RMSC]
#
F_VALUE = 1
# quality
Q = 1
# limit alarm
LA = 1
# deviation alarm
DA = 1
# points red tagged
RT = 1
# point tracking
PT = 1
# calibration correction values
[RMSCReport]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[Station]
# process_variable_value
PV = 1
# set_point_value
SP = 1
# control_output_value
CO = 1
# ratio_index_value
RI = 1
# quality
Q = 1
# limit alarm
LA = 1
# deviation alarm
DA = 1
# process variable quality
PVQ = 1
# points red tagged
RT = 1
# set point tracking
SPT = 1
# bypassed
BYP = 1
# manual interlock
MI = 1
# output tracking
OT = 1
# digital station failure
DSF = 1
# computer OK signal
COK = 1
# control level
LEV = 1
[Real4AnalogRead]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[Real4AnalogReport]
#
F_VALUE = 0
# quality
Q = 0
# limit alarm
LA = 0
# deviation alarm
DA = 0
# points red tagged
RT = 0
# point tracking
PT = 0
# calibration correction values
CCV = 0
[ExtendedModuleStatus]
#
F_VALUE = 0
[EnhancedTrend]
# maximum reporting time exceeded
MXT = 0
# request for immediate notification
IMM = 0
# message size limitation exceeded
MSG = 0
# enhnaced trend block in alarm
ALM = 0
# quality
[DAANG]
# quality
Q = 1
# high alarm
HA = 1
# low alarm
LA = 1
# alarm level
AL = 1
#
X = 1
# block red tagged
TAG1 = 1
# auto/manual
AM1 = 1
#
UC_BYTE2 = 1
# constant value 1
CONSTANT_1 = 1
# block red tagged
TAG3 = 1
# hardware fault/bad quality of input signal
FQ3 = 1
# out of range
OR = 1
# limited
LIM = 1
# auto/manual
AM3 = 1
# calculated value
CAL3 = 1
# qualtiy override
QO = 1
# off scan/no report
SS = 1
# high deviation alarm
HDA = 1
# low deviation alarm
LDA = 1
# high rate
HR = 1
# low rate
LR = 1
# variable alarms
VA = 1
# alarm suppression indication
ASI = 1
[AsciiString]
#
UC_CLASS = 0
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
[MSDD]
# quality
Q = 1
# multistate device driver block alarm
ALM = 1
# status override value
SOR = 1
# control override value
COR = 1
# operating mode
M = 1
# block tagged
TAG = 1
# command output equal
CO = 1
# feedback state 1
FB1 = 1
# feedback state 2
FB2 = 1
# feedback state 3
[DD]
# quality
Q = 1
# device driver block alarm
ALM = 1
# device driver block tagged
TAG = 1
# output value
OV = 1
# feedback state 1
FB1 = 1
# feedback state 2
FB2 = 1
# feedbak status
FS = 1
# override value
OR = 1
# operationg mode
MODE = 1
[RMC]
# quality
Q = 0
# rmc block in alarm
ALM = 0
# feedback state 1
FB1 = 0
# feedback state 2
FB2 = 0
# rmc block tagged
TAG = 0
# output value
OV = 0
# bad start
BS = 0
# fault
F = 0
# start permissive state 1
SP1 = 0
# start permissive state 2
SP2 = 0
# error codes for bad start
RMC_ERR = 0
[DADIG]
# quality
Q = 0
# dadig block alarm
ALM = 0
# time in alarm re-alarm (bit is toggled)
REALM = 0
# alarms suppressed
SUP = 0
# output suspect
OS = 0
# point off scan (no report)
NR = 0
# red tagged
TAG = 0
# output value
OV = 0
# extended status transition latched
LAT = 0
# quality override
QO = 0
# set permissive
SP = 0
# primary input selected
PI = 0
# alternate input selected
AI = 0
[TextSelector]
#
C_COLOR_NUMBER = 0
#
C_BLINK = 0
#
L_MESSAGE_NUMBER = 0
# quality
Q = 0
[HarmonyAnalogInput]
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
#
F_DATA = 0
# value quality (0 = OK; 1 = BAD)
UC_Q = 0
# value is in high alarm (0 = NO; 1 = YES)
UC_H_ALRM = 0
# value is in low alarm (0 = NO; 1 = YES)
[HarmonyAnalogOutput]
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
#
F_DATA = 0
# value quality (0 = OK; 1 = BAD)
UC_Q = 0
# value is in high alarm (0 = NO; 1 = YES)
UC_H_ALRM = 0
# value is in low alarm (0 = NO; 1 = YES)
UC_L_ALRM = 0
# status errors are inhibited (0 = NO; 1 = YES)
UC_SEI = 0
# simulated value (0 = NO; 1 = YES)
UC_SIM = 0
# overridden value (0 = NO; 1 = YES)
UC_OE = 0
# value is suspect (0 = NO; 1 = YES)
UC_SUSP = 0
# is quality propogated (0 = NO; 1 = YES)
UC_PQ = 0
# extended range (valid if range = 11; 0 = overdriven low 1 = overdriven high)
UC_ER = 0
[HarmonyDigitalInput]
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
# value quality (0 = OK; 1 = BAD)
UC_Q = 0
# value is in alarm (0 = NO; 1 = YES)
UC_ALM = 0
# status error are inhibited (0 = NO; 1 = YES)
UC_SEI = 0
# simulated value (0 = NO; 1 = YES)
UC_SIM = 0
# overridden value (0 = NO; 1 = YES)
UC_OVVL = 0
# value is suspect (0 = NO; 1 = YES)
UC_SUSP = 0
# is quality propogated (0 = NO; 1 = YES)
UC_PQ = 0
# configuration error exists (0 = NO; 1 = YES)
UC_CERR = 0
# channel condition (range: 00 = OK, 01 = open, 10 = short, 11 = overdrive)
UC_RANGE = 0
# readback status (0 = OK; 1 - BAD)
UC_RBST = 0
# value
UC_VAL = 0
[HarmonyDigitalOutput]
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
# value quality (0 = OK; 1 = BAD)
UC_Q = 0
# value is in alarm (0 = NO; 1 = YES)
[PhaseX]
#
UC_FORMAT = 0
#
UC_STATUS_SIZE = 0
#
UC_DATA_SIZE = 0
#
UC_XRP_REVISION = 0
#
US_SLOW_EVENT_COUNTER = 0
#
US_FAST_EVENT_COUNTER = 0
#
F_FAULT_CODE = 0
#
F_FAULT_DATA = 0
#
S_STATE = 0
#
S_PHASE_NUMBER = 0
# value quality (0 = OK; 1 = BAD)
UC_Q = 0
# alarm status(level) (1 = user messages (future), 2 = user faults, 3 = system faults)
UC_ALM = 0
# XR confirmation (0 = not expected, 1 = expected)
UC_CNFXR = 0
# program status (0 = inactive, 1 = active)
UC_PROG = 0
# acquired status (0 = not acquired, 1 = acquired)
UC_ACQ = 0
2.17.1 Introduction
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
ConDas ScanDriver PGIM
reading/writing of
current values
ConDas Server
TCP/IP Server
2.17.2 Shortconfiguration
2.17.2.1 Introduction
To connect ConDas as a data supplier for ABB PGIM, a signal list (short configuration procedure) from
ConDas is required. This list is created by the ConDas program:
MED:SHORTDOCUMENTATION.EXE
This is a text file which will be transmitted, for example via FTP, to the PGIM system. In a short
configuration procedure, signals from several ConDas configurations may be combined, provided that
configuration-wide unique short names are used.
The program SHORTDOCUMENTATION is included in the distribution of ConDas version 7.71 and
higher, but it can also be used without any problem on previous ConDas versions 7.x.
RUN MED:SHORTDOCUMENTATION
Alternatively, you may also integrate it into ConDas as an external program, setting the sequence
mode to "Foreground".
The program has a simple user interface. After the start, the following outputs are displayed (the parts
in italics are examples; you can provide your own inputs):
This program creates a short configuration from one or more configurations and writes it to an output
file.
First, the program requests that you enter a file name for the text file in which the short configuration
procedure will be created. You can use any name. In the case of an empty input, the program will
abort.
Then enter a number for the configuration whose signals are to be included in the short configuration
procedure. All signals of the configuration are always documented.
After the selected configuration has been read and processed, you may either include another
configuration in the short configuration procedure, or terminate the inputs and then create the short
configuration procedure:
If "N" is entered, the short configuration procedure will be created in the selected file.
By entering "Y" or "J", you can include another configuration in the short configuration procedure. The
same configuration can not be selected a second time.
The signal names of the configurations included in the short configuration procedure are checked for
their configuration-wide uniqueness, i.e., each signal name may exist only once in the short
configuration procedure. If an infringement of this rule is detected, the program indicates the signal
name and removes the associated configuration completely from the short configuration procedure:
You can choose two possibilities: either you enter "N" to abort the program because of the error, or
you enter "Y" or "J" to ignore the error and have the short configuration procedure created for the
remaining configurations. You can also include other configurations.
After the program has created the short configuration procedure, it indicates the name of the file and
the number of documented signals:
The parameters of the signals follow in separate text blocks which are separated from each other by a
blank line. Each text block begins with a two-line header, followed by a blank line. Then the parameter
block follows indented by 2 blank spaces. It is composed of a different number of lines depending on
the signal type.
Type :: AI
Tag Name :: 01LAB01CP901/X1/SIG
DESCRIPTION :: 01LAB01CP901/X1/SIG
EGU TAG :: Grad C
LOW EGU LIMIT :: 0,0
HIGH EGU LIMIT :: 100,0
Each line includes a keyword for the parameter, which is separated by 2 colons from the following
proper parameter value. The table below lists all keywords used at present and their meaning:
Keyword K/P1 Meaning
Type K Signal type:
AI = Analog Input
AO = Analog Output
DI = Digital Input
DO = Digital Output
1
K/P: Use of keyword (K = header, P = parameter block)
2
Measuring range: Signals from ConDas without specific measuring range (for example virtual
channels) get the measuring range 0..100.
DESCRIPTION :: 01LAB01CP901/X1/SIG
EGU TAG :: Grad C
LOW EGU LIMIT :: 0,0
HIGH EGU LIMIT :: 100,0
Type :: DI
Tag Name :: 10AE00E007/VXA
DESCRIPTION :: 10AE00E007/VXA
OPEN TAG :: 0
CLOSE TAG :: 1
Type
Type of the signal:
AI,CI,VI,EX,HN => analog/read
AO,CO,MA => analog/read-write
DI => binary/read
DO => binary/read-write
Only these types are evaluated, signals of other types will be ignored.
Tag Name
Name of the signal
DESCRIPTION
For binary signals (ConDas types DI, DO), the following evaluations are additionally performed:
OPEN TAG
Status text for signal value 0 (status text "Off")
CLOSE TAG
Status text for signal value 1 (status text "On")
For analog signals (ConDas types AI,AO,CI,CO,VI,EX,HN,MA), the following evaluations are
additionally performed:
EGU TAG
Dimension of the measured values of the signal
The ConDasScanner.ini control file is created in the folder ...\Confi_ConDasScanner\. The file
includes one section for the configuration of the ConDasScanner as well as one or several sections for
the configuration of the ConDas systems.
For each ConDas system, one section [<ConDas-System>] may exist where
the <ConDas-System> must not be identical with "ConDasScanner". The name must correspond with
the name in the GDB file. The TCP/IP host name or the TCP/IP address of the ConDas system would
be appropriate.
In this section, the following variables are recognized:
Variable: nodename
Purpose: TCP/IP host name of the ConDas system
Default: Name of the ConDas system (from <ConDas-System>)
Variable: port
Purpose: TCP/IP port number of the ConDas network server
Default: 4000
Variable: timeout
Variable: Cycletime
Purpose: Length of the scanning cycle in milliseconds
Default: 10 milliseconds
Variable: separatorThousand
Purpose: Thousand separator of the .GDB file
Default: Thousand separator of the local Win32 system or "."
Variable: separatorDecimal
Purpose: Decimal separator of the .GDB file
Default: Decimal separator of the local Win32 system or ","
If a blank space is used as a value for the variables separatorThousand or separatorDecimal, the
program will ignore any spaces when reading in numbers (i.e. those for which the C function isspace()
delivers a true value).
The section [ConDasScanner] may exist only once. In this section, the following variable is
recognized:
Variable: debug
Purpose: Logging level
Values: 0 Only errors are logged (default).
1 Warnings are logged.
3 The most important non-iterative methods of CPhysicalScanner are logged.
4 Iterative methods (FindFirst / FindNext) of CPhysicalScanner are logged.
5 Start/Stop methods of CPhysicalScanner are logged.
6 Start/Stop methods of CLogicalScanner are logged.
2.18.1 Introduction
LAN (TCP/IP)
PGIM Server
PGIM ScanManager
FIX ScanDriver PGIM
Intellution iFIX
LAN (TCP/IP)
reading/writing of
current values
Intellution FIX
EDA interface
Type
Type of the signal:
AI,CI => analog/read
AO,AR => analog/read-write (AO actually write only)
DI,MDI => binary/read
DO,DR => binary/read-write (DO actually write only)
Only these types are evaluated; signals of other types will be ignored.
Tag Name
DESCRIPTION
Description of the signal (long text)
For binary signals (FIX types DI, DO, DR, MDI), the following evaluations are additionally performed:
OPEN TAG
Status text for signal value 0 (statustext0)
CLOSE TAG
Status text for signal value 1 (statustext1)
For analog signals (FIX types AI, AO, AR, CA), the following evaluations are additionally performed:
EGU TAG
Dimension of the measured values of the signal
Note that AO and DO signals in FIX are write-only!
Variable: Cycletime
Purpose: Length of the scanning cycle in milliseconds
Default: 10 milliseconds
Variable: separatorMillion
Purpose: Million- separator of the .GDB file
Default: Million - separator of the local Win32 system or "."
Variable: separatorDecimal
Purpose: Decimal separator of the .GDB file
Default: Decimal separator of the local Win32 system or ","
Nodename = Nodename
Type = Type
TagName = Tagname
The section [FIXScanner] may exist only once. In this section, the following variable is recognized:
Variable: debug
Purpose: Logging level
Values: 0 Only errors are logged (default).
1 Warnings are logged (at present "FIX is not running" only).
3 The most important non-iterative methods of CPhysicalScanner are logged.
4 Iterative methods (FindFirst / FindNext) of CPhysicalScanner are logged.
5 Start/Stop methods of CPhysicalScanner are logged.
6 Start/Stop methods of CLogicalScanner are logged.
7 The ReadThread is logged.
8 Constructors and destructors of CPhysicalScanner are logged.
9 All methods are logged.
20 The calls of WriteSignalToScanMan() are logged.
PGIM Server
PGIM ScanManager
PGIM
MARK IV ScanDriver
Multiplexer GE
reading of current process values
Serial interface
MARK IV
Serial data dump
Measured values are sent from the MarkIV system cyclically without any special requirements. They
are passed as a byte stream over a serial interface (the configuration of the interfaces is described in
the following section). The byte stream consists of binary-coded data without any special beginning or
final identifications. In order to make a synchronization possible, is assumed at the beginning of the
byte stream that the time-stamps are always in order, and consist of 6 bytes.
Seconds (0..59)
Minutes (0..59)
Hours (0..23)
Days (1..31)
Month (1..12)
Year (0..255) (+2000 if < 100, else +1900)
Starting from that 7th byte the measured values follow. A measured value can consist of an individual
bit or of two or three bytes.
2.19.2 MarkIVScanner.ini
The file MarkIVScanner.ini is located in the ...\Konfi_MarkIVScanner \ folder. It contains configuration
data for the logical scanners, for example the parameters of the serial interface. The file contains a
section for each logical scanner. The names of the sections correspond to the names of the logical
scanners, for example [ MarkIVScanner01 ], [ MarkIVScanner02 ] etc. In each section the following
variables are recognized:
Information Description
Log files are located in the ...\log\MarkIVScanner\ folder with the Name MarkIVScanner.log or
MarkIVScanner.log.old.
PGIM Server
PGIM ScanManager
PGIM
MARKV / VI ScanDriver
reading / writing of
current process values GE
Network (TCP/IP)
MARK V / VI
GSM protocol
Configuration file for measuring ranges added. In the past the scanner has set the low and high
measurement ranges based on the theoretical limits of the transferred values. Now the ranges could
be defined by a separate file named displayscale.txt. This file contains in each row
a signal name, the start and the end of measuring range and a dimension. E.g.
100_PCT;0.0;100.0;%
For this connection the Mark V/VI uses a so-called GSM server from which the PGIM scanner
transfers the data cyclically together with a timestamp to the PGIM system. Analog data can be
transferred up to 1 s cycle time.
Binary values transferred to PGIM will have a millisecond resolution since the PGIM scanner analyses
events coming from the Mark V and converts the event messages to binary data.
The GSM scanner fully supports the GSM messaging queue, which includes the bi-directional transfer
of messages and events (acknowledgements). Since this functionality is available also on the
connected PGIM OPC AE server and the PGIM OPC DA server this scanner can act as a complete
OPC gateway (connectivity server) to Mark V/VI.
2.20.1 MarkVScanner.ini
3 OPC-Servers
PGIM provides two different OPC DA servers:
1. OPC DA server which connects to the PGIM ScanManager (legacy)
2. OPC DA server which connects to the database
In the following both OPC DA servers will be described starting with
Scanner 1
Scanner n
PlaCo OPC
OPC Client
Server
Scanner 1
Scanner n
The OPC server for PGIM provides process data from systems which are connected via scan
managers and scanners. The OPC server complies with the OPC specifications 1.0 and 2.0. It is a
"Data Access" server, i.e., only process data is transmitted, no events.
The OPC server is started automatically ("OutProc Server") as an autonomous process as soon as a
client initiates a connection setup.
3.1.1 Installation
The installation of the OPC server is performed within the scope of the PGIM installation by selecting
the corresponding option.
After the installation, the initialization file of the OPC server must be customized. This file always
resides in the same folder as the OPC server itself. It is only read at the start of the OPC server.
[COMMON]
Sector [Common]
Debug The text output for program checking is controlled using this parameter.
On The text output logs a multitude of accesses and events within the OPC server.
Note: The performance of the program is affected !
Off Default value. Only errors and basic information at the start of the program will
be logged.
TraceFileSize Determines the size of the log file in bytes. At the start of the program, two files
are generated. The program changes to a new file when the set file size is
reached on the old file. The files are created in an automatically generated "log"
subfolder.
NoScanManager Number of connected ScanManagers. This also determines the number of the
following sectors because each ScanManager requires its own sector for
configuration.
Sector [ScanMan_n]
Each scan manager requires its own sector. If the sector is missing or if the designation of the sector
is faulty (n = number of the scan manager, consecutively numbered, beginning with 1), the OPC
server will not start.
ScanManName Name of the scan manager. The name is freely configurable. The OPC
server uses this name to form the name box when addressing the
process data. This name is the first hierarchy level of the name box.
ConnectHost Name of the computer on which the scan manager has been installed.
This name should also be entered in the file
\%SYSTEMROOT%\system32\drivers\etc\hosts.
PortNumber TCP port number for communication with the scan manager.
0x0815 Default port number in hexadecimal notation. (In this case, the format
would be "%x".)
I. Level
The names of the defined scan managers. The names of the scan managers used in the initialization
file are applied here. These names are static, and they cannot be modified during the runtime of the
OPC server.
II. Level
Name of the scanners. On request, these names are transmitted by the scan managers to the OPC
server. Newly added scanners are recognized and transmitted to the client in the case of a new
inquiry.
III. Level
Names of the process values of a scanner. On request (browsing) by the client, the names are
inquired by the OPC server from the respective scanner and dynamically added to the name box.
Depending on the connected subsystem, the transmission of the names may take some time. Newly
added measuring points can immediately be used without restarting the OPC server.
The character "\" is used as a separator between the hierarchy levels. This character is fixed and
cannot be changed.
Example of addressing:
PGIM DB
OPC Client PGIM
OPC DA
Server
The PGIM OPC DA server connects to the PGIM database. The advantage of this OPC server is that
clients can subscribe and read data immediately, since the database always has the relevant data
already in it memory caches. The OPC Server allows ready as well as writing.
Configuration of the OPC DA server is done through the following registry keys, which can be found in
\HKEY_LOCAL_MACHINE\SOFTWARE\Hartmann & Braun\PlantConnect
As the legacy OPC server the PGIM OPC DA server on the PGIM database needs a local PGIM client
with a valid local PGIM OPC server license.
3.3 Functionality
The OPC server operates with a dynamic name box (except for the connected scan managers) and
can process newly added scanners and measured values without restarting. The client may, at any
time, add measuring points to a group. The measuring point will then be transmitted to the
corresponding scanner and checked.
The OPC server also supports the browsing of measuring points. However, this may take time and
require computer capacity, depending on the system and on the number of measuring points in the
subsystem.
With started measuring points (OPC group and measuring point enabled), the OPC server operates
event-controlled. The process values are transmitted by the scan manager (legacy OPC server
behavior) in the case of a change (taking into account the tolerance set in the scan manager) and is
immediately signaled to the client (within the cycle time set for the group). In contrast to this the OPC
server on PGIM DB directly reeds the relevant information from the database.
In the case of fast value changes (less than one second), a special feature becomes evident. These
values are collected in the scan manager and then transmitted every second to the OPC server. This
implies that the OPC server will simultaneously receive several process values for one measuring
point. All process values are processed, and a change is signaled to the client. The client will receive
the current process value. Intermediate values are lost. For this reason, cycle times less than one
second are not appropriate for this OPC server.
If a client wants to read all values, including several changes within one second, the cycle time of the
OPC group must be set to zero (Report Mode). Then no process values will be lost. All process values
are stored in a queue and can be polled by the client. In this mode, the client must ensure that all
measured values are polled and processed without interruption.
IOPCCommon
HRESULT SetLocaleID ( dwLcid )
HRESULT GetLocaleID ( pdwLcid )
HRESULT QueryAvailableLocaleIDs ( pdwCount, pdwLcid )
HRESULT GetErrorString ( dwError, ppString)
HRESULT SetClientName (szName)
IOPCServer
HRESULT AddGroup(szName, bActive, dwRequestedUpdateRate, hClientGroup, pTimeBias, pPercentDeadband,
dwLCID, phServerGroup, pRevisedUpdateRate, riid, ppUnk)
HRESULT GetErrorString(dwError, dwLocale, ppString)
HRESULT GetGroupByName(szName, riid, ppUnk)
HRESULT GetStatus(ppServerStatus)
HRESULT RemoveGroup(hServerGroup, bForce)
HRESULT CreateGroupEnumerator(dwScope, riid, ppUnk)
IConnectionPointContainer
HRESULT EnumConnectionPoints( IEnumConnectionPoints ppEnum);
HRESULT FindConnectionPoint( REFIID riid, IConnectionPoint ppCP);
IOPCItemProperties
HRESULT QueryAvailableProperties(szItemID, pdwCount,
ppPropertyIDs, ppDescriptions, ppvtDataTypes );
HRESULT GetItemProperties (szItemID, dwCount, pdwPropertyIDs,
ppvData, ppErrors );
HRESULT LookupItemIDs( szItemID, dwCount, pdwPropertyIDs,
ppszNewItemIDs, ppErrors );
IOPCBrowseServerAddressSpace (optional)
HRESULT QueryOrganization(pNameSpaceType );
HRESULT ChangeBrowsePosition(dwBrowseDirection, szString );
HRESULT BrowseOPCItemIDs( dwBrowseFilterType, szFilterCriteria, vtDataTypeFilter, dwAccessRightsFilter,
ppIEnumString );
HRESULT GetItemID( szItemDataID, szItemID );
HRESULT BrowseAccessPaths( szItemID, ppIEnumString );
IOPCGroupStateMgt
HRESULT GetState(pUpdateRate, pActive, ppName, pTimeBias, pPercentDeadband, pLCID, phClientGroup,
phServerGroup)
HRESULT SetState(pRequestedUpdateRate, pRevisedUpdateRate, pActive, pTimeBias, pPercentDeadband,
pLCID, phClientGroup)
HRESULT SetName(szName);
HRESULT CloneGroup(szName, riid, ppUnk);
IOPCSyncIO
HRESULT Read(dwSource, dwCount, phServer, ppItemValues, ppErrors)
HRESULT Write(dwCount, phServer, pItemValues, ppErrors)
IOPCAsyncIO2
HRESULT Read(dwCount, phServer, dwTransactionID, pdwCancelID, ppErrors,)
HRESULT Write(dwCount, phServer, pItemValues, dwTransactionID, pdwCancelID, ppErrors);
HRESULT Cancel2 (dwCancelID);
HRESULT Refresh2(dwSource, dwTransactionID, pdwCancelID);
HRESULT SetEnable(bEnable);
HRESULT GetEnable(pbEnable);
IOPCItemMgt
HRESULT AddItems(dwCount, pItemArray, ppAddResults, ppErrors)
HRESULT ValidateItems(dwCount, pItemArray, bBlobUpdate, ppValidationResults, ppErrors)
HRESULT RemoveItems(dwCount, phServer, ppErrors)
HRESULT SetActiveState(dwCount, phServer, bActive, ppErrors)
HRESULT SetClientHandles(dwCount, phServer, phClient, ppErrors)
HRESULT SetDatatypes(dwCount, phServer, pRequestedDatatypes, ppErrors)
HRESULT CreateEnumerator(riid, ppUnk)
IConnectionPointContainer
HRESULT EnumConnectionPoints( IEnumConnectionPoints ppEnum);
HRESULT FindConnectionPoint( REFIID riid, IConnectionPoint ppCP);
IOPCAsyncIO (old)
HRESULT Read(dwConnection, dwSource, dwCount, phServer, pTransactionID, ppErrors,)
HRESULT Write(dwConnection, dwCount, phServer, pItemValues, pTransactionID, ppErrors);
HRESULT Cancel (dwTransactionID);
HRESULT Refresh(dwConnection, dwSource, pTransactionID);
IDataObject (old)
HRESULT Dadvise(pFmt, adv, pSnk, pConnection);
HRESULT Dunadvise(Connection);
Note: all other functions can be stubs which return E_NOTIMPL.
IEnumOPCItemAttributes
HRESULT Next(celt, ppItemArray, pceltFetched);
HRESULT Skip(celt);
HRESULT Reset( void);
HRESULT Clone(ppEnumItemAttributes);
4 Database / Server
4.1 Introduction
All signals which are made available within the PGIM system are stored in a database which is
optimized for the special requirements of plant management. That means that a large number of
signals (currently up to 100.000 signals per server, please refer to PGIM data sheet for actual
performance) can be managed in the PGIM database. Measured values with a high time resolution
are saved for these signals. They can easily be accessed by the evaluation functions.
The database is divided into the "static" information about signals and the actual measured value
sequences. These sequences are saved in a file system where the folder name for measured value
sequences is derived from the signal name.
"Static" information, which is not changed with each measured value, includes, for example,
measuring range start and measuring range end. Along from this information additional attributes
(such as "cost center") can be defined by the user for the signals, and parameterized immediately.
The PGIM server controls the data transfer from the PGIM database to the individual inquiring
applications. Inquiries regarding the representation of current process values in process displays or
trend displays can be take place. Inquiries can also include average values for characteristic value
calculations, as well as maximum or minimum values for logs. Communication is performed via
TCP/IP protocol.
The structure of the PGIM database is signal-oriented. First, the values are written by the
ScanManager into the random-access memory (RAM) in the PGIM database according to the changes
made.
A flash algorithm provides the optimal packet-oriented storage of the values on the hard disk. These
have been stored in the volatile memory before. Using additional cache algorithms data loss is
reduced when unexpected computer failures take place. The archives for the different signals have a
uniform fractionation which usually includes 1 day. Consequently, the size of the different archives
varies considerably depending on the plant operation and the adjusted tolerance band.
Progress state: Indicates the most important last status message of the server.
Input: at
Output on screen:
Input: at 1
Output on screen:
Task-ID: 1
Status: OK
Schedule: Every Mo Di Mi Do Fr Sa So
Time: 04:00 AM
Interactive: No
Command: C:\Programs\SyncTimeAt.cmd
4.4 Diagnosis
The PGIM server (database) can be analyzed with the help of a Web Browser (for example the
Internet Explorer). The web browser must be started and the name of the PGIM server must be
entered as sn address (for example http://PlaCoSrv). The Webport is adjusted to 89 by default. It can
be changed in the file PlaCo.INI, for example to 81. Only SysAdmin users are permitted to use this
address.
• Signalname
Name of the signal.
• Amount(Lifetime)
Number of all values over the lifetime of this signal. Values already exported are not considered.
Contains the up-to-date available values in the database.
• Ta[sec](cache,estimated)
Each signal has its own Cache in the RAM, in which about on the average 100 - 500 values are
stored. "Ta[sec](cache, estimated)" indicates the alteration rate of the values up-to-date available in
the Cache.
Calculation:
Ta[sec](cache,estimated) = (TimeOfLatestCacheValue - TimeOfFirstCVacheValue) /
Amount(Cache)
Note: If you optimize (change the deadband), then the result is first readable with these values. The
ranking in the list does not change however, since the whole list is still stored after "Ta[sec](Lifetime)"
The position in the list of the fastest signals (thus the "Ranking") will only change slowly over time.
• Deadband
The current deadband. Value in % of the scaling (= scale end – scale beginning).
• firstMW
The first (oldest) value in the database.
• lastMW
The last (youngest) value in the database.
4.5.1 Introduction
Two server computers as similar as possible (performance & HD capacity) with the same license data
(LCFG.INI) mutually mirror all writing logs. Incoming signal values of the scanners are mirrored, along
with all configuration actions such as signal creation, attribute changes, and signal deletion. Even
configuration changes regarding user accounts will be mirrored.
Two equal PGIM servers are connected in a Network, and additionally connected via a separate direct
network link between both servers. This separate link is necessary for the adjustment between the
redundant servers. For the PGIM clients the redundant server looks like one server. A PGIM client
contacts only the logical server SRV, not the SRV1.1 or SRV1.2 (see Picture 1
If a server fails, the IPSwitch gates the telegram to the second server.
A client application recognizes this by a short-time connection break which, depending on the client,
will either be reported (manual restart required depending on the respective client), or the client has
implemented an automatic restart. In that case, the user will not become aware of the switchover.
Picture 1: Example of a redundant PGIM system: Server and Scanner are on different computers
Note: The telegram being transmitted during a network break will be lost. This means that the client
must repeat this telegram.
The following settings are also possible with the "PGIM System Configuration" tool
(...PlantConnect.bin\tools\PlaCoConfiTool.exe).
Install PGIM server via setup.
Do NOT start the server (service: to manual)
Make the following entries in the PlaCo.INI for [Server.Settings] on SRV1.1:
:
[Server.Settings]
; === That is the redundancy counterpart:
RedundancyServer=SRV3.2
; === That is executed in the case of a failure:
AtRedundancyFailureDo=RedFailure.cmd
; === At the start, the server is waiting xx minutes for the redundancy peer.
; Default without specification: 30 min
AtRedundancyStartUpWaitMinutesForPeer=5
Make the following entries in the PlaCo.INI for [Server.Settings] on SRV1.2:
:
[Server.Settings]
; === That is the redundancy counterpart:
RedundancyServer=SRV3.1
; === That is executed in the case of a failure:
AtRedundancyFailureDo=RedFailure.cmd
; === At the start, the server is waiting xx minutes for the redundancy peer.
; Default without specification: 30 min
AtRedundancyStartUpWaitMinutesForPeer=5
Example:
Description Name IP Address
physical PGIM server 1 SRV1.1 192.168.10.1
physical PGIM server 2 SRV1.2 192.168.10.2
logic PGIM server SRV
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\LocalPortNumber 4242
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName1 SRV1.1
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber1 4242
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName2 SRV1.2
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber2 4242
You must change the example names SRV1.1, SRV1.2 and SRV to the real names.
The redproxy installation must be done on the Scanner computers also.
Note:
In this installation case the redproxy should not be installed on the servers.
The redproxy installation must be done on the Scanner computers in the same manner as the client.
PGIM Server database and Client applications are installed on the same
computer.
Example:
Description Name IP Address
physical PGIM server 1 SRV1.1 192.168.10.1
physical PGIM server 2 SRV1.2 192.168.10.2
logic PGIM server SRV
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\LocalPortNumber 4242
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName1 SRV1.1
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber1 4241
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName2 SRV1.2
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber2 4241
You must change the example names SRV1.1, SRV1.2 and SRV to the real names.
The redproxy installation must be done on the Scanner computers also.
Note:
In this installation case the redproxy must be installed on the servers also.
Example:
Description Name IP Address
physical PGIM server 1 SRV1.1 192.168.10.1
physical PGIM server 2 SRV1.2 192.168.10.2
logic PGIM server SRV
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\LocalPortNumber 4242
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName1 SRV1.1
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber1 4241
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName2 SRV1.2
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber2 4241
You must change the example names SRV1.1, SRV1.2 and SRV to the real names.
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\LocalPortNumber 2069
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName1 SRV1.1
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber1 2068
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemoteComputerName2 SRV1.2
HKEY_LOCAL_MACHINE\SOFTWARE\PlantConnect\RedProxy\RemotePortNumber2 2068
You must change the example names SRV1.1, SRV1.2 and SRV to the real names.
NOTE: Depending on the number of tags and the duration of failure, balancing may take a
few hours.
The balanced server will be reachable again for clients only after balancing is
complete.
You must decide which server has the better data. Then you must initiate manually balancing.
If both servers announce this status, then the following procedures must be accomplished:
1. Decide which server has the better data. Start this one (DOS NTA starting IP
server). Wait unit this server is available to receive data from the scanners and
from the PGIM Clients.
2. Start the alignment on the other server (see the "ManualBalancing" section)
After successful balancing (which may take some time), the balanced server will automatically be
online again.
A detailed analysis of the redundant server is displayed. The displayed text depends upon conditions
of the redundant server as explained below.
#[2]
- Short description:
IP-Server #1 is offline and server #2 cannot be achieved. NOTE: The Clients cannot reach the
server in this state!
- Measures:
* First check #1 and if everything is ok, start up the IP-Server #1 again.
* Check network and server #2. Then start server #2 again.
#[3]
- Short description:
ERROR!
Neither servers #1 nor #2 are attainable by Ping.
* Check the network connections and the configuration of both servers!
* Then boot both servers.
* Monitor the Startup.
#[4]
- Short description:
ERROR!
#1 is not accessible, server #2 is not attainable by Ping.
- Measures:
* Check server #2 and network locally.
* Start both servers at the same time again.
* Monitor the Startup.
#[5]
- Short description:
Normal operation. The servers are balanced and ok.
#[7]
- Short description:
NOTE: IP-Server on #1 is not running!
Check, why is the IP-Server is not running?
* Then start again.
#[8]
- Short description:
#1 switched to the alternative IP line #2 because the standard-IP-mirror-connection was not
available at the point in time #3.
* Perform a Network examination: Check the mirror line!
* #1 will try again to reach the standard IP line after 1 hour. Wait for this amount of time and check the
status again.
#[9]
- Short description:
#1 switched to the alternative IP line #2 because the standard IP mirror connection was not available
at the point in time #3.
* Perform a Network examination: Check the mirror line!
* #1 will try again to reach the standard IP line after 1 hour. Wait for this amount of time and check the
status again.
#[10]
- Short description:
Startup of server #1 is still running. Start was at # 3. NOTE: Server #2 is not started.
* NOTE: Start server #2 as soon as possible, otherwise server #1 will not be able to terminate its
startup!
#[11]
- Short description:
CONFUSING SITUATION.
#1 had a redundancy error, but the IP-Server is still running.
* Why is the IP-Server still running on #1? Check and if necessary switch off.
* Check locally #1, then start #1 again.
#[13]
- Short description:
Redundancy error.
Probably the server-service on #1 was stopped manually.
* Restart the server-service on #1.
#[14]
- Short description:
Redundancy error on # 1.
Server-service started but server #1 does not react. Reason unclear.
* Check locally then start server-service on #1 or boot #1.
#[15]
- Short description:
#2 detected a redundancy error on #1. Breakdown-time was #3
(Maybe the server-service on #1 was stopped manually or #1 is still in the starting procedure)
* Consider the further causes below following Analysis.
* Restart the server-service on #1 again.
#[16]
- Short description:
Redundancy error on # 1.
Main voltage or network or computer error on # 1.
* Check server and network locally.
* Then start server-service on #1 or restart #1.
#[17]
- Short description:
Startup of server #1 is still running. Start was at #2
* Wait for end of the starting procedure.
#[18]
#[19]
- Short description:
CONFUSING SITUATION on both servers. The reason is probably network problems when in the
starting phase or the nonexistence of the partner server during the whole starting phase.
- Description of details:
At the start of this server a connection to the redundancy-partner could not be recovered. This
occurred again after an xx minute waiting period. The redundancy-partner is available to the network
and the redundancy-partner-server is likewise accessible by the Redundancy Manager. The partner-
IP-Server is not running, is therefore not available. It indicates that the partner-server had problems
finding its partner while starting. - > NOTE: This is a critical situation because none of the two servers
is available online for Clients.
- Reasons:
The situation points to the fact that the network connections (as well the mirror connection as the
alternative IP connection which can be configured) were not available during the starting procedure.
- Measures:
* Check all network connections locally.
* Because none of the two servers is active the administrator must start the IP-server (DOS NTA
startIPServer) on the server that contains the more current and more correct data. The clues are in the
information about the number of tags, values and lastMW.
* After that start the balancing on the other server by using "DOS NTA balancMe".
#[20]
- Short description:
Startup at the redundancy-partner #1 is still running.
* Wait for the result...
#[21]
#[22]
- Short description:
Redundancy-partner #1 is started but the IP-Server is offline.
* Was the IP-Server perhaps set offline manually for maintenance? If so set it back online.
#[23]
- Short description:
Redundancy-partner #1 is not started (state=#2). Number of tags or values or indexes did not match
at the partner's start. (Partner is waiting for user's decision)
* Check the partner and repair.
#[24]
- Short description:
CONFUSING SITUATION
At the Startup the redundancy-partner #1 was not attainable by Ping.
* Check #1 locally. Then stop both servers and start again at the same point in time.
- Description of details:
- Situation:
At the start of this server a connection to the redundancy-partner could not be recovered. This
occurred again after an xx minute waiting period. The redundancy-partner is also not attainable by
Ping. Either no network connection to the redundancy-partner exists, or the computer is switched off.
-> NOTE: This is a critical situation because none of the two servers is available online for Clients.
- Measures:
1) Check network and hardware locally and check whether the partner-server-service stands on
"automatic".
2) Stop both server-services.
3) Now start the server-service again (as close as possible to the same time) or boot both servers
(as close as possible to the same time).
#[25]
- Short description:
Server #1 had a breakdown and/or was stopped but has more signals than the redundancy-partner
#2 now.
Information: The server #1 remains preliminarily closed for clients.(IPServer OFF)
- Description of details:
#[26]
- Short description:
Server #1 had a breakdown and/or was stopped but has more values than the redundancy-partner
now. Therefore the IP-Server at #1 remains offline (IPServer OFF).
- Description of details:
At the start of server #1 it was noticed that server #1 was shut down normally and that the partner-
server #2 took over at that time. Further on it was noticed that the partner-server has fewer signals
than this server. A reason could be a normal procedure: for example if signals were deleted on server
#2 during the "ServerDown"-time (ring - archive).
- Measures:
* If the breakdown-time was > 1 day and if old data will be deleted daily (ring - Archive) then the
balancing must be started manually on #1. (Open the Internet explorer and log in on http:\\#1, then
implement under Direct SQL the command "DOS NTA balanceMe").
* If signals were deleted by users during the breakdown-time then #1 must be adjusted as follows.
(Open the Internet explorer and log in on http:\\#1 then implement under Direct SQL the command
"DOS NTA balanceMe").
* If you are sure that despite this server-analysis this failed server #1 has data that is the most
current, then start the balancing on server #2.(Open the Internet explorer and log in on http:\\#2, then
implement under Direct SQL the command "DOS NTA balanceMe").
#[27]
- Short description:
Server #1 had a breakdown and/or was stopped but has more current values than the redundancy-
partner now. Therefore the IP-Server at #1 remains offline.
- Description of details:
At the start of this server it was noticed that this server was shut down normally and that the partner-
server took over for that time. Further on it was noticed that the partner-server has fewer tags than this
server. A reason could be a normal procedure: for example if tags were deleted by SignalExplorer on
the other server during the "ServerDown"-time. Because of fewer amounts of data on the partner this
means that during the balancing fewer amounts of data were reflected than were available on this
server. Check the accuracy of the conditions.
- Measures:
* Check data consistency on #1, compare with #2.
* Decide on which server to start the balancing.
#[28]
- Short description:
Server #1 had a breakdown and/or was stopped (regular breakdown).
Balancing supplied automatically now.
- Description of details:
- Situation:
At the start of this server it was noticed that this server had a breakdown and the partner-server took
over at that time. Balancing supplied automatically on this server now.
- Measures:
None
#[29]
- Short description:
This server had a breakdown. The redundancy-partner, however, had nothing to mirror in the
breakdown-time (this arises when a server is shut down and no Client writes occur during this time.)
Balancing is not necessary. The IP-Server automatically goes online.
- Description of details:
- Situation:
At the start of this server it was noticed that during the stop-time that the other server was active but
there were no writing operations which were completed. Therefore there was no redundancy error and
balancing must not be initiated. The data is still identical. This situation can occur if the Admin shuts
down the server for maintenance and during this time he stops all Clients (users and ScanManager)
from doing write operations. Thus the balancing is not necessary at the start, and the server is online
faster.
- Measures:
None
#[30]
- Short description:
This server had a breakdown and the redundancy-partner had nothing to mirror during the
breakdown down-time, but he has nevertheless more values.
(Possible because on #2 meanwhile fewer data exists because of an export) Balancing supplied
automatically now.
- Description of details:
- Situation:
At the start of this server it was noticed that this server was not shut down normally (for example
Main voltage error ?). But during the stop-time the other server was active. During the stop-time there
were no writing operations which could be reflected. Therefore this was no redundancy error. Because
the redundancy-partner has more data the balancing will be started automatically. (A reason may be
because of manual manipulation or cache loss on this server during a breakdown)
#[31]
- Short description:
Server #1 was switched off but #2 did not write in that time. Therefore the Servers are still balanced.
OK.
- Description of details:
- Situation:
At the start of this server it was noticed that this server was not shut down normally (for example
Main voltage error ?). But the redundancy-partner had not noticed a breakdown (because it was
stopped, or there were no writing operations which could be reflected). Therefore this was no
redundancy error. Because this server has more data (a reason could be manual manipulation on the
redundancy-partner) this server goes online now.
- Measures:
None
#[32]
- Short description:
#1 had failed. #2 noticed no breakdown. Primary-index-tables are however unequal! Check first who
the current server is. On the other one start the balancing manually.
- Description of details:
- Situation:
At the start of this server it was noticed that this server was not shut down normally (for example
Main voltage error ?). But the redundancy-partner had not noticed a breakdown (because it was
stopped, or there were no writing operations which could be reflected). The internal check showed that
the primary-index-tables are not identical. (A reason could be manual manipulation on the
redundancy-server by the configuration). This IP-Server does not go online.
- Measures:
1) Analyze and decide which server is the current one, and on which server the balancing must be
started.
2) Start the balancing on the selected server now. Start the IP-Server on the other server (if
stopped).
#[33]
- Short description:
Either:
a) #1 is started for the first time.
b) The machine was exchanged because of a hardware failure.
c) It was reconfigured manually (for example the drive was changed or the PlaCo.INI was incorrectly
changed, etc.).
1) Check whether #2 a) is online and b) whether #1 has the most current data.
2) If it (1) applies: Start the balancing on this computer.
#[34]
- Short description:
On server #1 is currently active and balancing with #2.
- Measures:
* For this time none measures. Wait for the end of the balancing and check the result.
#[35]
Server #1 adjusted itself on the other server at #2.
#[36]
- Short description:
Redundancy-configuration-error. #1 is not configured as a redundancy-server. Check both server
configurations (PlaCo.INI). Then start both server PCs at the same time again.
#[37]
- Short description:
Server #1 is running and is online. No errors are announced to server #2.
Server #2 is however not accessible from here.
* Check the network connection to server #2.
#[38]
- Short description:
Server #1 is running and is online. Server #2 is accessible by the network but is not responsive,
although the server-service is running. This situation is possibly caused by a manual stop of # 2, or an
unknown problem on server #2.
* Check server #2
* Then restart of #2!
#[39]
- Short description:
On #1 the balancing is running. Therefore the IP-Server is still stopped. Ok.
#[40]
- Short description:
On both redundancy-server-machines the PGIM server-services is not started.
* Start both server-services at the same time (approximately).
* Monitor the starting procedure.
* Information: Check also whether the server-services are adjusted to be "automatic".
Select the file and include with the Add-In-List. Click OK.
To integrate the Add-In in Excel, select the box on the left of "PcLogs". Quit the Add-In-Manager by
clicking OK. The new entry "Logs" will automatically be created in the Excel main menu.
PcLogs.xla
This file includes all formulas and dialogs required for the creation of logs.
PcLogs.ini
The settings made under the menu item "Options" are saved in this text file.
Scheduler.xls
This Excel workbook includes the Scheduler for the cyclic call of the logs.
Scheduler.ini
Here the Scheduler saves the data for the logs to be called cyclically.
6 Trend
6.1 Signal Colors
The colors for the selected curves are assigned according to a standard. The color chart is used in
PGIM.
The color 90 is used for the first signal in the trend. Further signals in the trend use the color 90 + and
index value. This applies up until the 10th trend signal. The 11th signal begins again with the color
index 90.
Colors in PGIM are specified in the COLIDX.CSV file under... \PlantConnect.BIN\Client \.
The goal is to call foreign applications using the context menu, then to hand the selected signal over
as a parameter. The foreign application must evaluate the parameter file CMD.INI and insert the
desired functionality.
The basic conditions for this goal are available in PGIM.
For example the foreign applications which can be started are called AppA.BAT, AppB.XLS, and
AppC.EXE. In the PlaCo.INI file you can make the following entries under the section
[GEDContextMenu]:
[GEDContextMenu]
Browse auxiliary info.... = AppA.VBS
Previous year month means = AppB.XLS
Search similar signals... = AppC.EXE
There are now three new menu options within the context menu (using the right mouse) in the display
for each signal:
Browse auxiliary info....
- previous year month means
- Search similar signals...
Select one of these points and the appropriate foreign application is started.
7 AutoMail
PGIM AutoMail is a program which continuously monitors particular folders. As soon as files and/or
further subdirectories appear in such a folder, they will automatically be sent as attachment to an e-
mail generated automatically. Each file will be sent by means of an e-mail.
IMPORTANT: The subdirectories of the monitored folder and the files will be deleted after they have
been sent.
Therefore you must take care that the right folders are selected and/or that the folders are filled
correctly (e.g. by copying) in order to prevent the deletion of important originals.
AutoMail works in the background and supports SMTP (Simple Mail Transfer Protocol).
To install AutoMail mark the „AutoMail“ option in the “Tools” menu of then PGIM setup.
On the first start of AutoMail the “Option” dialog appears: here you can make the base configuration of
AutoMail. This dialog can also be shown over the main menu “Extras” -> “Options”.
The standard port of a SMTP server is port 25. If another port must be used you can write the port
number behind the server separated by a “:” (e.g. mail.gmx.net:9025).
In the main windows of AutoMail the tasks of the application are shown. A task is a “monitor” job of
AutoMail. That means that a task describe which folder AutoMail monitors and to which addresses
AutoMail send the files.
Exit AutoMail Main menu -> “File” -> “Exit” Terminates the application
Add a task Main menu -> “File” -> “Add” Adds a task to the AutoMail main window and
opens the Task Configuration dialog (s.
Or Right mouse menu -> “Add”
Chapter 5)
Delete a task Select task and Deletes the task from the main window. The
configured folder is no longer monitored.
Main menu -> “File” -> “Delete”
Or Select task and
Right mouse menu -> “Delete”
Edit a task Select task and Opens the Task Configuration dialog (s.
In a task configuration it is specified which folder (with its subfolders) is monitored and to which
address(es) the found files are sent.
In the case of a new task (Add action in the main window) all fields are empty.
The folder to monitor can be set via the “…” button which opens a directory browser. In this browser
select the wanted directory and click the “OK” button.
With the checkbox “Active” you can specify if the task is active or not. Click in the box and the value
changes.
In the address list (recipient list) e-mail addresses can be added and deleted. To add an e-mail
address click in the list then open the right mouse menu and select “Add”. Another list will appear
where you can select an e-mail address and transfer it to the recipient list with the “Add to folder”
button. For more information about the e-mail list please refer to the next chapter. To delete an e-mail
from the list select the name field then open the right mouse menu and select “Delete”.
All e-mail addresses are collected and can be managed in a separate list. You can achieve this list via
the task configuration when adding an e-mail in the address list (s. Chapter 5). In the e-mail list e-mail
addresses can be added, deleted and selected for the transfer to the address list of the task
configuration.
In the e-mail list you can find a name and an address field.
The same dialog appears when you want to edit an entry. Therefore select a name then open the right
mouse menu and select “Edit”.
To delete an entry, select a name then open the right mouse menu and select “Delete”.
8 WebClient
8.1 Introduction
PGIM can be accessed from the Internet.
A WebClient is a normal PGIM-Client-PC with a correspondingly configured WebRouting.INI file.
All normal PGIM functions (Navigator, User Manager, SignalExplorer, GED, Trend, Logs, and TecBer)
may communicate via the internet server according to the WebRouting.INI.
A WebClient can continue to access the PGIM servers simultaneously available on the Intranet.
There is one difference with the WebClient. PGIM ScanManagers cannot be contacted via the
Internet. Consequently, the following message is displayed in the SignalExplorer during the "System
Update": "Cannot reach ScanDriver XY".
In order to allow a PGIM client to communicate via the Internet with a server it is possible to expand
the communication for the PGIM client by using a corresponding configuration (INI file) for the HTTP
Proxy operation. The configuration file defines the Proxy through which the client will reach a server,
as well as the respective server to be reached.
A client operation beyond the limits of the Intranet (WebClient) will be as follows:
Internet
[FirewallA] [FirewallB]
[CompB]
Proxy=MYFW
ProxyPort=8080
ServerIP=PGIMServerB
HostAuthentication=Mustermann:karin
NOTE:
If no HostAuthentication is required, the entry "must" be exactly "HostAuthentication=dummy", i.e. the
entry must not be dummy.
After that, the SignalExplorer may be started and the servers "CompA" and "CompB" can be added.
9 Backup hints
9.1 Introduction
This document describes the procedure for backup and recovery of a PGIM installation on a computer.
The first section describes the backup performed in single steps. A solution for backup and recovery of
the overall system is presented in the last section.
It is the task of the system administrator to ensure that the data is saved at regular intervals to the
extent necessary. The data should also be deposited in a safe place. The system administrator and/or
the company must bear the responsibility.
This description includes notes on the backup of the operating system and its components. No
warranty is given for the correctness of this information. The backup of the operating system is not the
primary task of this manual, and it is only mentioned for the sake of completeness. The system
administrator and/or the company are responsible for correct backups.
9.2.1 Backup
After the installation and after an update, even of single components, a backup of the operating
system must be performed by suitable means. Ensure that the tool being used will also copy and save
all settings (Registry, opened files, ...). If necessary, the system must be brought down.
Appropriate tools are available on the market.
In any case, the settings in the hard disk manager of the operating system must be recorded and
deposited at a safe place. They are required for a restoration of the system.
If a backup is not possible, all inputs made during the installation/update must be recorded exactly,
and deposited at a safe place. All data media (for example CD drivers) required for the
installation/update must also be secured and deposited. Magnetic data media (for example floppies)
only have a limited shelf life. Their contents must be refreshed in time.
9.2.2 Recovery
The recovery of the operating system is carried out according to the instructions of the backup tool
being used.
If no backup could be created, a reinstallation must be performed. For this, the recordings of the
installation/update and the corresponding data media (for example CD drivers) are required.
9.3.1 Backup
After the installation and after an update, even of single components, a backup of the Office
applications and of other tools must be performed by suitable means. Ensure that the tool being used
will also copy and save all settings (Registry, opened files, ...). If necessary, the system must be
brought down.
Appropriate tools are available on the market.
If a backup is not possible, all inputs made during the installation/update must be recorded exactly,
and deposited at a safe place. All data media (for example CD drivers) required for the
installation/update must also be secured and deposited. Magnetic data media (for example floppies)
only have a limited shelf life. Their contents must be refreshed in time.
9.3.2 Recovery
The recovery of the Office applications and of other tools is carried out according to the instructions of
the backup tool being used.
If no backup could be created, a reinstallation must be performed. For this, the recordings of the
installation/update and the corresponding data media (for example CD drivers) are required.
9.8.1 Backup
As an alternative to the single steps described above for the backup of software packages and basic
installation, the backup procedure can also be performed in one step using an appropriate tool after all
partial packages (operating system, Office applications, other tools, PGIM and Event Management)
have been installed. Usually, a so-called image backup of the hard disk(s) will then be created.
For this, the instructions of the backup tool must be followed. If necessary, the system must be
brought down.
In any case, the continuously changing data of PGIM and of the Event Management must be saved as
described above using the PGIM Ex/Import tool.
9.8.2 Recovery
If a backup of the overall system has been performed using one tool, it is possible to restore the
system after a failure using the same tool.
For this, the instructions of the backup tool must be followed. If necessary, the system must be
brought down.
In any case, the continuously changing data of PGIM and of the Event Management must be restored
as described above using the PGIM Ex/Import tool.
10 Ex/Import-Manager
10.1 Introduction
The program ExIm.exe is used to save the archived data stored in the PGIM database. It can either be
used for backup purposes, or for moving the data to external media. It is also possible to use this
program to delete the oldest data on the hard disk.
For data storage hardware normally a magneto-optical drive with the respective media is used. The
drive may be included in the PGIM server PC, connected to it as an external device or it may be
reachable via a network connection. For any drive where it is possible to read and write like a hard
disc, it is also possible to use this drive for data storage.
10.2 Installation
For the installation of the PGIM ExImport tool, the entry "ExImport" must be selected from the tools in
the PGIM Setup. The program is installed as a service and will be available under the name "PGIM
ExImport" in the list of services. During the runtime of the program, an icon in the system taskbar
refers to the program. It is possible to execute the program from the taskbar.
[Export]
SingleOpDelayMilliSec= Delay between the processing of two signals
EventServer= Name of the Event Server
EventMsgRepeatAfterMinutes=60 Delay time to wait before repeating the sending of messages to the
event server
DailyExportStart=04:00 Daily start time for the export.
DebugLevel=0 Level for the debug outputs:
0 means few outputs
5 means many outputs
(The default value is 0.)
[ShellProgram] Automatic call of any program when the capacity limit of the
export medium has been reached.
ProgName= Name of the program to be called.
ProgPath= Path to the program to be called.
ProgParameter= Call parameter for the program to be executed.
[ServerDataRoots]
DEUTAMINW1035=f:\ROH\ Folder for the PGIM archive data.
[SQLTasks]
WaitForExcecuteInSeconds=2000 Waiting time until the SQL server command has been executed
(Time out).
EventImportPath = If the entry is empty or not available, "PGIM-System path
\PlantConnect.BIN\Events\Import\" is entered for the path of the
EventImport-Ini file.
11 AutoUpdate
11.1 Introduction
The PGIM product is continuously improved to achieve the best possible functionality and operator
convenience. PGIM AutoUpdate can be used to distribute new versions of the product easily;
particularly in plants with several client installations.
PGIM setup files are saved on a central HTTP or FTP server. PGIM AutoUpdate is installed on each
client, and the address of the server is configured.
PGIM AutoUpdate copies the setup files to the individual clients, then automatically installs the
transmitted product version on these computers. Whenever PGIM is started on a client, PGIM
AutoUpdate will check whether a new version exists on a configured server. If there is a new version
available, you receive a notification. You can then choose to automatically update the PGIM version.
This ensures that the latest PGIM version is available on all clients of a plant.
Moreover, PGIM AutoUpdate also allows the installation of a new PGIM client via the FTP/HTTP
server.
11.2 Preconditions
PGIM AutoUpdate uses the HTTP or FTP protocol for transmitting the new versions. For this reason,
the existence of an FTP server or Web server (HTTP) is required.
An HTTP or FTP server is not included in the scope of supply, but by default Microsoft supplies
a FTP server with Win 2000 as a component of Internet Information Services IIS.
A freeware FTP server may also be used. The freeware server GuildFTPd, for example, has proved to
be sufficient for the purposes of PGIM AutoUpdate.
On the installed server, an update folder (for example ...PIMS\PlantConnect.SETUP) must be created
and released for all accessing clients. In this folder, the PGIM setup CD and information files are
saved (see Chapter 11.6).
An installation can also be performed manually via the available standard FTP program. After having
initiated the prompt, start the FTP program and download the AutoUpdateSetup.exe file from the FTP
server. Then execute AutoUpdateSetup.exe. The same procedure (download or direct execution of
the AutoUpdateSetup.exe file) can also be carried out in the same manner using the Internet Explorer
(HTTP basis).
The different fields show the current configuration of the client which has been selected in the Select
Client for Configuration field.
Click Add new Client to input the name or the IP number of a new client. Click OK. The system
checks if the client is reachable within the network, and whether PGIM AutoUpdate has been installed.
The client can only be found if PGIM AutoUpdate has been installed.
Client configurations can be displayed by selecting a client from the list. The following information is
displays about the PGIM software installed on the selected client:
The Current Version of the PGIM software is displayed.
The PGIM Path indicates the installation path of the software.
In the Installed Components view all installed modules of PGIM software are listed.
Use "Local Path" to select the folder to be used by AutoUpdate to save the setup file. It is
important that these folders already exist. Otherwise, no files can be transmitted from the
HTTP/FTP server.
Use "Select Protocol" to select the protocol which the server will use to transmit the setup files.
"ftp/http Server location" indicates the path of the folder where the setup files are residing on the
server. Click the Check Server Connection button to check the input, and also to find the version
number of the PGIM software available on the server. If the test is successful, the message
"Connection OK" appears, and the version of the PGIM software on the server is displayed in the
field "Available Update Version on Server". If not, the message "Connection failed" will be
displayed. If the test fails, this may have the following causes.
The folder in the field "Local Path" does not exist.
The path in the field "ftp/http Server location" is not identical to the path on the server.
You can create a Collection of Clients to avoid changing each client individually. By pressing the
Edit Collection of Clients button you can add a client into the collection or to remove it from the list.
In the "Known Clients" list all clients are shown that have been added with the Add new Client
button. A new client can only be added if a PGIM AutoUpdate has been installed on this client. By
marking the clients in the list Known Clients and pressing the >> button these clients will be added to
the Selected Clients list. To remove clients from the list Selected Clients you must select the clients
and press the << button.
For the clients in the "Collection", only those parameters will be applied which have been selected.
An update of the client can also be initiated immediately by selecting the Update localhost button in
the configuration view. This also allows reinstalling a PGIM client. However, this is only possible for
the "localhost" (i.e. the local client). You must ensure that the executed update is a full setup ( *.*.0).
You can decide whether you want to install the new version right now or later. If you decide not to
perform an update now, you will be asked again when starting the PGIM client next time. For detailed
information about the update, an information document is available by clicking the Readme button:
To ensure an optimum functionality and operator convenience, the update should be performed in all
cases. The update executes completely without further user inputs. It only takes a few minutes.
If the PGIM client is closed only on rare occasions, the availability of a new PGIM version can be
checked manually. On the taskbar select Start, Programs, PGIM, PGIM Update to perform an update
if possible.
With the installation of AutoUpdate, a new folder (....\PIMS\PlantConnect.SETUP) is created. Then the
PGIM setup files were copied to this folder (see Chapter 6). In the server software, the sub-folder
....\PIMS\PlantConnect.SETUP\PlantConnect\bin has been released on the virtual path
/PlaCoNewVersion for all clients (Anonymous).
Due to the fact that the PGIM version was already installed, and the AutoUpdateInstaller was used for
the installation, changes to the settings are not necessary now.
In the File Download dialog you can save the program to disk, or you can run the program from its
current location.
Select the option "Run this program from its current location". A security warning is displayed. Click
Yes. The download will begin and AutoUpdateSetup is launched.
During the setup, the installation path indicates where PGIM will be installed later.
The installation begins with a welcome message. Select the option "Install with Administration Tool"
and finish the setup.
After the installation, the configuration view of PGIM AutoUpdate was displayed.
Description:
3.1 Description:
Entry name : The name of the Excel-Report ( will be set automatic )
Exec path : The full qualified Excel-Report file
Parameter : Additional start parameter ( optional )
Button „Edit“ : The button „Edit“ opens the report
Button „Cancel“ : The button „Cancel” close the dialog without saving
Button „Save“ : The button „Save“ close the dialog with saving
IMPORTANT: The first time that you use the report scheduler under a service account, you
must open the Report with the “Edit” button after you have chosen your report it in the exec
path line. Excel will ask you this first time for your initials and you MUST answer this question
once to run the service later on in a service account.
This is the configuration tab for the cyclically execution of a PGIM report
Time priority : Set the priority for this report ( 1: high priority ;5: low priority)
Next run : Sets the date for the next execution of the configured report
Delay : Sets the delay (in seconds ) . The PGIM Report Scheduler waits
for this time, before executing the report
Last Run : Sets the date for the last execution of the configured report
This is the configuration tab for the event driven execution of a PGIM report
Event priority : Set the priority for this report ( 1: high priority ;5: low priority)
Begin scan at : Sets the date for the next scan interval
Stop scan at : Sets the date for the last scan of the configured report
Exec. Delay : Sets the delay (in seconds ) . The PGIM Report Scheduler waits
for this time after getting an event, before executing the report
To configure signals for an event driven execution, Drag&Drop a database signal from the
SignalExplorer ( not in service mode ) or write a full qualified PGIM item in the datagrid.
Rising:
Starts the report, if the signal value changed from “0” to “1”
Falling:
Starts the report, if the signal value changed from “1” to “0”
Both:
Starts the report, if the signal value changed
>Limit:
Starts the report, if the signal value is lager then the configured limit
value
<Limit:
Starts the report, if the signal value is smaller then the configured limit
value
Current value : the button “Current value” read the values for the signals at the “Begin scan at”
timestamp and displays them in the datagrid
Clear : the button “Clear” deletes all configured signals in the datagrid
Priority : Set the priority for this report ( 1: high priority ;5: low
priority)
12.3 Options
Autostart : En/Disable the autostart of the PGIM Report Scheduler after the startup
Scan cycle : Set the scan cycle for the event driven execution
Web-Job folder : Temporary folder for extra jobs from the PGIM WebClient
IIS root path : Root path for the Microsoft Internet Information Server
( Optional, if using PGIM WebClient )
13 Additional Programs
13.1 ASCII-Export
13.1.1 Introduction
The program PlaCoExport.exe is used to read information (signal descriptions as well as measured
values) from the PGIM databases and store this incorporation in files.
The format of the files depends on the application for which the file is created. Applications using
these files are, for example, the data reconciliation program "ConVali" (VALI III), or the lifetime
monitoring program "ConLife".
The amount of information that will be stored in the file as well as the format of the file is defined in a
configuration file that must be given as a parameter when the program is started.
13.1.2 Installation
To install the program the file PlaCoExport.exe and the respective configuration file (for example
"ConLife.txt") must be copied into the subfolder "PlaCoExport". This subfolder must be created in the
"PlantConnect.bin" folder.
In order to make the start of the program as easy as possible, the creation of a shortcut is
recommended. The following picture shows the properties of a shortcut for PlaCoExport to create files
for ConLife.
13.2.1 Introduction
The program PcSched.exe provides administration features for other programs that do not belong
directly to PGIM, but run in parallel to the scanning and analyzing programs of PGIM.
If you have never used this program, please refer to the section “PGIM Scheduler” instead of using
this program.
Those other programs may be developed by the customer, or may be special interface programs.
Normally those programs read the stored values from the PGIM databases, process these values and
perhaps write back results to the PGIM databases.
The external programs can be started once or cyclically with configurable cycles. The execution can
be automatically triggered by the configuration values or by an event (for example the changing of a
binary signal in one of the PGIM-ScanManagers).
Two types of programs can be started:
NT-batch files (Extension ".bat",".vbs","js",etc.)
Executable programs (Extension ".exe")
The programs to be started run in the background as separate applications. In this case no interaction
with the user is possible. Therefore the input parameters for the programs must be stored in a
configuration file. If the started program runs in the foreground interactions are possible via the
keyboard or the mouse.
13.2.2 Installation
The installation is carried out automatically after starting the program Setup.exe on the delivered
installation CD.
13.3.1 Introduction
The program PGIM Router (or PCRouter for short) is used to exchange process values between
different ScanDrivers. This data exchange is needed if two or more stand-alone control systems must
exchange information. The program PCRouter allows you to transfer data from control system A to
control system B and vice versa.
The program establishes the communication between two or more ScanManagers, and starts an
event driven data exchange.
13.3.2 Installation
The installation of the PGIM Router must be selected as an option of the tools during the installation of
the PGIM software. During the installation the following folders are created to store the files.
<Installation folder>\PlantConnect.BIN\PCRouter
PCRouter.EXE
KonfiPCRouter.CSV
13.3.3 Structure
External
Editor
e.g.
Notepad
Configu-
PCRouter
ration file
ScanManager
Scandriver 1 ScanDriver 2
(e.g. Modbus) (e.g. P-Protocol)
13.3.4 Operation
The program PCRouter can be started by double-clicking the file "PCRouter.exe", or a link to this file.
PC Router can also be installed as a service. Then it is accessible from the windows services.
Before the data transfer can be started a configuration file must be selected. The configuration file can
be selected by typing the name of the file into the field "Module File" or by selecting the file from a file
selection dialog located besides the input field.
The configuration file can be created or modified from the program PCRouter. Therefore an editor
must be selected. The selection of the editor works in the same way as the selection of the
configuration file.
The settings concerning the editor as well as the configuration file are stored when the program is
stopped. Those settings are available for the next start of the program.
In order to modify the configuration file the click the Edit Configuration file button.
The field "Test signal" allows you to specify a single or several signals for which the data exchange is
shown on screen. For all signals that contain the defined string in their names the data exchange is
logged in the debug window, if the checkbox "Logging for Testsignal active" is selected.
The data transfer is started by selecting the "Start the Router" checkbox.
The selection of "Output in log file" starts the logging of all actions of the program. The logging should
be activated if problems occur during the data transfer. The log file is located in the folder:
< Installation folder >\PlantConnect.SYS\Debug\PCRouter.
13.3.6 Configuration
The configuration file is structured by lines, each line containing a source and one or more sinks. The
columns are separated by semicolons. Each line starts with the type of the connection module. The
following types are possible:
Connect
DisConnectAlarm
ODER
2ZU1
Example:
Connect; Connect[Signal 1];1;2;\PCEAST\ep001e09\SIGNAL1;
\PCEAST\Modbus1\SIGNAL2;\PCWEST\Modbus2\SIGNAL3
PCRouter
Structure:
Column A DisConnectAlarm Keyword
Column B Module name unique identification of the connection, may only
exist once
Column C ScanManager Name of the ScanManager
Column D ScanDriver Name of the Scandriver
Column E Binärsignal Signal identification with the structure
\ScanManager\Scandriver\Signal
Example:
DisConnectAlarm; PCWEST ;ep001e09 ;PCWEST\MODBUS\Alarm/XM41;9
Structure:
Column A ODER Keyword
Column B Module name unique identification of the connection, may only
exist once
Column C Number of input signals 1-8
Column D Number of output signals 1
Column E Input signal 1 Signal identification with the structure
\ScanManager\Scandriver\Signal
(Column F Input signal 2 )
Example:
ODER;Oder1;2;1;\PCEAST\ep001e09\SIGNAL1; ¬
\PCEAST\Modbus1\SIGNAL2;\PCWEST\Modbus2\SIGNAL3
PCRouter
1
Structure:
Column A 2ZU1 Keyword
Column B Module name unique identification of the connection, may only
exist once
Column C Number of input signals 1
Column D Number of output signals 1
Column E Input signal 1 Signal identification with the structure
\ScanManager\Scandriver\Signal
Column F Output signal 1 same as input signal
Column G Value 1 numerical value
Column H Value 2 numerical value
Example:
2ZU1;Bed[F0LAB50EE002/COA/POS];1;1;\PCEAST\Modbus1\F0LAB50EE002/COA/POS;\PCEAST\e
p001e09\F0LAB50EE002/ZA95;0;131
13.4 AutoMailer
13.4.1 Introduction
The idea of AutoMail is simple, but it offers power features for information sharing.
The basic problem is this: How can files in specific folders be automatically sent as e-mail attachments
to a specific e-mail address? For example, a report (which might have been generated automatically)
can be forwarded by e-mail to the responsible person. AutoMail presents a solution to this problem.
AutoMail is a program that continuously monitors particular folders. As soon as files and/or further
subfolders appear in these folders, they are automatically sent as attachments to an e-mail. The email
message is also generated automatically. Each file will be sent using an e-mail message.
IMPORTANT: The subfolders of the monitored folder and the files will be deleted after they
have been sent. Therefore you must take care that the correct folders are selected. Also make sure
that the folders are filled in correctly (for example by copying) in order to prevent the deletion of
important original files.
13.4.2 Installation
To install AutoMail from the CD execute Setup.exe. You are guided by an installation Wizard. When
starting AutoMail for the first time, your e-mail address, subject and mail server are required. These
details are important to ensure that the program runs correctly. They can also be entered in the
Options menu of the AutoMail main screen.
13.4.3 Structure
The folders from which the files will be sent are displayed in the AutoMail main screen. The names
indicated in the main window are logical names.
Select Options from the main window of AutoMail to find the information required for sending files.
You can delete folders and terminate AutoMail in the AutoMail main window. Use the Properties or
Add menus to create folders or to change properties of existing folders. You can set properties such
as folder names, folders, active addresses and e-mail addresses.
From these menus you can display commands like Explorer and E-mail addresses. Folders can be
selected in the Explorer. The E-mail addresses commands shows the e-mail addresses that are
available in the internal AutoMail database. You can delete e-mail addresses from the database. If you
want to change or add e-mail addresses in the database, you must use the Change or Add menus.
13.4.5 Operation
13.4.5.2.2 Active
Select the Active check box to actively monitor the folder. Files in the folder will be sent and deleted
immediately.
13.4.5.6 Remarks
Each file in the folder is sent separately. Files above 1.2 MB are not sent, but deleted.
13.4.6.1 Options
The options information must have the correct sender e-mail address and the correct mail server. If
errors occur when sending e-mails, check the settings in the Options menu.
13.5.1 General
The setup monitor called “System Diagnosis” provides a quick overview about the PGIM components
installed on the local PC, along with their operating state. It can also be used for trouble shooting, and
for the preparation of a report of the current state of the installation.
13.5.2 Icons
The following icons with the mentioned meaning are used inside the program “System Diagnosis”
A problem occurred
Information
Further action
Error
13.5.3 Handling
A tree structure is used for displaying the information. The root of this tree structure is the local PC.
After the start of the program only the root and the main items are visible. The different symbols and
colors show the current operating state of the main items ScanManager, server and client. The last
main item in the tree structure is labeled "Setup Info".
Each main item contains further information (see chapter 3), that can be seen if the main item is
expanded (either by clicking on the "+" sign or by double-clicking the name of the main item).
Expanding any main item of the root node, as well as pressing the F5 button refreshes the displayed
information. During the time required for refreshing the information the cursor is shown as an hour
glass.
13.5.4.1 ScanManager
The main item ScanManager contains the sub items "Installed", "License
OK", "Operating" and "ScanDriver OK" with the remark
"yes" or "no".
The item "License OK" contains the sub item "Analysis" where the
license file can be inspected, the ScanManager folder
can be opened and the network card can be analyzed.
The item "Operating" contains the sub item "Analysis" where the log
file can be inspected, and the Scanner folder can be
opened.
The item "ScanDriver OK" contains all ScanDrivers as sub items that can
be found either in
<system path>\PlantConnect.BIN\Scanner\Scandriver or in the license
file <system path>\PlantConnect.BIN\Cfg\lcfg.ini.
These items contain information on whether the
respective ScanDriver is included in the license. The
respective configuration folder can also be opened.
A fifth sub item which is always red indicates a severe error (for
example if the license file lcfg.ini cannot be found).
13.5.4.2 Server
The main item Server contains the sub items "Installed", "License OK",
"Service started" and "Server operating" with the
remark "yes" or "no".
If the local server is running, the last item "Start webbrowser..."
allow you to create a connection to the server in an
internet browser.
Further information concerning the version, number of tags and the
number of licensed clients are displayed behind the
paper clip symbols if accessible. The large number of
clients showing the value "0" may indicate that the
TCP/IP server of the PGIM server is not running. The
TCP/IP server delivers the data for the clients.
The item "License OK" contains the sub item "Analysis" where the
license file can be inspected, and the network card
can be analyzed.
The item "Server operating" contains the sub item "Analysis" where the
initialization file "PlaCo.ini" can be inspected, and
the folder for the log files can be opened.
13.5.4.3 Client
The main item Client contains the sub items "Installed", "Client
operating" and "License server operating" with the
remark "yes" or "no".
Further information concerning the name and version of the license
server can be displayed behind the paper clip symbols
if accessible.
13.5.4.4 Info
13.6 WatchDog
13.6.1 Introduction
The PGIM Watch-Dog (PlaCoWD) monitors the sections from the control system via the PGIM
Scandriver and the PGIM ScanManager up to the PGIM database. In the case of a failure or
regeneration of the connection, corresponding messages are issued in the control system and in
PGIM so that an operator in the control system or in PGIM can initiate appropriate measures to
remove the fault. This requires that the procedure described in the following chapter can be
implemented in the control system.
13.6.2 Procedure
If the values change, the connection is OK, and PlaCoWD either writes a binary pulse for a
configurable duration or the value 0 on the ramp signal in the control system. In this way, the ramp in
the control system is reset, and the message will be suppressed. Writing can be performed via the
existing interface. You can also use another scanner to transmit the value, for example, via a direct
output card in the PC to the control system (The hardware extension is optionally available).
PlaCoWD also resets the ramp in the control system if the value of the ramp has exceeded an
adjustable maximum value. This is to avoid a situation where the ramp in the control system reaches a
limit where it will no longer change (for example 102.5%). This state may occur when the connection
to PGIM has been interrupted. Then the ramp in the control system exceeds the limit value initiating a
message up to the maximum value. The value remains at the maximum value until PlaCoWD resets
the value by comparing it with the adjusted maximum value.
If PlaCoWD detects that the value of the ramp does not change either in the ScanManager and/or in
the database, the ramp will not be reset in the control system, and the fault is automatically indicated
in the control system when exceeding the limit value of the ramp.
PlaCoWD additionally indicates failures in its LOG file, in the Windows event log and in the PGIM
alarm management. An error message in PGIM indicates whether there is a problem in the
ScanManager and/or the database. When PlaCoWD again recognizes a change of the ramp signal
13.6.3 Configuration
The configuration file for the Watch-Dog application resides in the folder
...\PlantConnect.BIN\Tools\WatchDog\ . The name is "PlaCoDW.ini".
PlaCoWD requires the following information, which is stored in the configuration file:
[WatchDogSignal 1]
# Cycle time in seconds for checking the ramp
cycle = 10
# Deviation of the ramp value from the last value
deviation = 5.0
# Name of the ramp signal
input = \\SRV01\SM01\SD01\SignalName01
# Maximum value of the ramp
maxvalue = 9999
# Name of the reset signal
output = \SM01\SD02\SignalName02
[WatchDogSignal 2]
# Cycle time in seconds for checking the ramp
cycle = 20
# Deviation of the ramp value from the last value
deviation = 2.0
# Name of the ramp signal
input = \\SRV02\SM02\SD01\SignalName01
# Maximum value of the ramp
maxvalue = 105
# Name of the reset pulse
reset = \SM03\SD02\ResetSignalName01
# Duration of the reset pulse
resetduration = 2
Legend
[WatchDogSignal 1]
It is possible to configure an arbitrary number of signals for monitoring (WatchDogSignal 1 ...n) which
can be acquired from different control systems via different ScanDrivers and ScanManagers. All the
following parameters in the section refer to this area.
cycle (Default = 10)
The cycle time in seconds during which the signal to be monitored is checked for changes.
deviation (Default = 1.0)
The minimum deviation of the ramp signal value from the last cycle.
input
reset
The name of the signal in the control system indicated in the PGIM notation. A pulse (reset) will be
written to this control system. This writing causes a reset of the ramp signal to 0 in the control system.
In contrast to "output", "reset" is written on 1 for a specific time and then on 0 again.
resetduration (Default = 1)
The time in seconds during which the reset signal will show a value of 1 before being set back to 0.
Acoustic message
When this option is activated, an acoustic signal (beep) on the PC is initiated in the case when a
message is received.
Click the Show messages button to display the log file in the standard Windows editor.
13.7.1 Introduction
The ABB DCS Symphony Maestro-UX is able to perform a medium-term storage of process data (over
several days) and to make the data available for evaluation purposes.
The data extraction of archive data from Maestro-UX is performed via a TCP/IP protocol network
connection:
Usually data is extracted from Melody to the PGIM system continuously, and PGIM stores the process
data in long-term archives if required.
If the PGIM server or the associated PGIM scanner must be stopped, for example for maintenance
purposes, the process data for the period during which the data acquisition was not available is
missing in the PGIM archives.
The program PlaCoArc (or also PGIM/MaestroArchiv) is used to store process data from the Maestro
system immediately in the PGIM archives.
To ensure the overall function of the PlaCoArc program, software portions are required in Maestro-UX
as well as in PGIM with the corresponding configuration.
E:\temp>dir PlaCo*
Data carrier in drive E: is Local Data
Data carrier number: EC1D-E909
E:\temp>ftp miw4
Connected to MIW4.
220 demo1 FTP server (Version 1.7.212.2 Tue Apr 21 12:14:46 GMT 1998) ready.
User (MIW4:(none)): pml
331 Password required for pml.
Password:
230 User pml logged in.
Ftp> pwd
257 "/usr/pml" is current folder.
Ftp> mkdir temp
257 MKD command successful.
Ftp> cd temp
250 CWD command successful.
Ftp> bin
200 Type set to I.
Ftp> put PlaCo_Inst.tar
200 PORT command successful.
150 Opening BINARY mode data connection for PlaCo_Inst.tar.
E:\temp>
#
# Kerberos (Project Athena/MIT) services
#
klogin 543/tcp # Kerberos rlogin –kfall
:::
13.8.1 Introduction
Decentralized plants are supervised from central control posts. Data from these plants become more
important in large interlaced systems. Timely control of the data in a central system is the basis for
evaluation, logging, analysis and optimization.
Decentralized plants are queried cyclically by the PGIM server over voice-grade channels.
13.8.2 Conditions
A telephone connection for each plant location.
PGIM ScanManager computer with an appropriate ScanDriver for the existing data acquisition.
A modem for each location.
PGIM server with modem and an Auto RAS Dialer software license.
13.8.3 Installation
The Auto RAS Dialer is installed on the PGIM server computer. The PGIM installation copies the
program to the ...PlantConnect.bin\AutoRasDialer\ folder. The program is added to the AutoStart
group of the computer. The application is started with the computer. The telecommunications
connections are furnished with the telecommunications monitor by Windows. You can also examine
whether you can make a connection to the desired location.
13.8.4 Configuration
The AutoRasDialer can be configured by the Auto-Dial-Configurator.
o Communications selection:
Select from the configured list of telecommunications providers.
o Active:
Each configured entry can be deactivated.
o Entry alias:
A detailed name can be registered for the connection.
o Start:
Indication of the first point of starting time. This indication is basis for the cycles configured.
o Option:
Daily(1x) A connection is opened once daily.
Cyclically all x minutes A connection is opened in the cycle of the adjusted
minutes.
Connect time: After the adjusted minutes the switched line is closed.
Delete:
The selected line can be deleted with this button. A safety inquiry protects against inadvertent
deletion.
Terminate:
Click the Terminate button to close the configuration screen.
13.8.5 Operation
After the start of the Auto-RAS-Dialer this screen appears.
A display similar to a traffic light shows the current condition of the program:
Green lamp: Program is started. No connection actively.
Yellow lamp flashing: Connection actively to the goal indicated on the top right
Red lamp: Connection failed.