Commissioning Guide MDA Cell - support.industry.siemens… · 4.5 Password of the Windows user ......

MDA Cell

Commissioning Guide Edition 10/2007

Archiving History

Machine Data Acquisition

Machine Data Evaluation

Commissioning Guide MDA Cell

1 General

2Standard Software for Production Automation

Installation

MDA Cell 3Further Actions

Commissioning Guide

4Tips & Tricks

5Glossary

6Appendix

7

8

Edition 10/2007


Trademark

® is a registered trademark of Siemens SIMATIC

OPC™ (OLE for Process Control) is a trademark of the OPC Foundation®

MDA Cell Commissioning Guide

Table of Contents

1 General.............................................................................................. 1-1

1.1 .......................................................................................................... 1-1 References

1.2 ........................................................................................................ 1-1 Prerequisites

1.3 ............................................................................................... 1-2 MDA Components1.3.1 System overview............................................................................................... 1-2

2 Installation ......................................................................................... 2-1

2.1 .............................................................................................................. 2-1 Overview

2.2 ................................. 2-2 Backing up the Databases and Settings of Older Versions2.2.1 ......................................................................................... 2-2 Upgrading MDA Cell

2.3 ................................................................................................. 2-3 Preparatory Step

2.4 ...................................................... 2-4 Use of eastern european or asian languages

2.5 .................................................. 2-4 Supplementary installation of further languages

2.6 ................................................................... 2-5 Installation of the database program2.6.1 ............................................................. 2-5 Microsoft SQL Server Desktop Engine2.6.2 ....................................................................................... 2-5 Microsoft SQL Server2.6.3 ............................................................................................................... 2-5 Oracle

2.7 .............................................................................................. 2-6 Starting Installation

2.8 ................................................................................. 2-6 Installation Dialogs (Step 1)

2.9 ................................ 2-8 Installation Microsoft SQL Server Desktop Engine (Step 2)

............................. 2-9 2.10 Installation of Microsoft Data Access Components (Step 3)

................................................................................... 2-10 2.11 Installing MDA (Step 4)

............................................................................. 2-11 2.12 Directory structure of MDA

........................................................... 2-12 2.13 Creating the Oracle database (Step 5)

...................................... 2-12 2.14 Creating of local Windows group MDAGRP (Step 6)

............................................................ 2-12 2.15 Customizing of Data Backup (Step 7)2.15.1 ........................................................................................................ 2-12 General2.15.2 .................................................................................................. 2-12 SQL Server

I&S IS E&C IT OOP 3 © Siemens AG 2007 All Rights Reserved i


............................... 2-12 2.16 Maintenance of Microsoft SQL Server database (Step 8)

............................................. 2-13 2.17 MDA Startservice and DCOM Settings (Step 9)

........................................................................................... 2-14 2.18 Shared directories2.18.1 .......................................................................................................... 2-14 Server2.18.2 ................................................................................................ 2-15 Workstations

........................................................................................................... 2-15 2.19 Firewall

..................................... 2-15 2.20 Restoring Earlier Databases and Settings (Optional)2.20.1 .................................................................................... 2-15 Upgrading MDA Cell

.................................................................................................. 2-17 2.21 Starting MDA

...................................................................................................... 2-17 2.22 Demo data

..................................................................................................... 2-17 2.23 Uninstalling

............................................................................................... 2-17 2.24 Works calendar

............................................................. 2-1 2.25 MDA server with MDA data acquisition2.25.1 ............................... 2-1 Starting of MDA data acquisition within the start service2.25.2 ............................. 2-1 Starting of MDA data acquisition outside the start service

3 Further Actions .................................................................................. 3-1

4 Tips & Tricks...................................................................................... 4-1

4.1 .......................... 4-1 Missing Write Permissions as of Windows 2000 / Windows XP

4.2 ............................................................................................ 4-1 Extending Database

4.3 .............................................................. 4-1 Computer name of the MDA Server self

4.4 ..................................................................................................... 4-1 Windows User

4.5 .............................................. 4-1 Password of the Windows user PDA has changed

4.6 ................................................... 4-1 Password of Database user PDA has changed

4.7 ......................................................................................... 4-2 Log files of Installation

5 Appendix............................................................................................ 5-1

5.1 ............................................................ 5-1 Database size of MSDE and SQL Server

I&S IS E&C IT OOP 3 ii © Siemens AG 2007 All Rights Reserved


1 General

This document describes the installation of MDA Cell and MDA Plant. For editorial reasons some functions are described which are not part of the product MDA Cell but are intended for use within projects. These chapters are to be ignored for installation of MDA Cell. This is the case especially for the use of Microsoft SQL Server or Oracle as database server. 1.1 References

With reference to the following documents within the folder docu at the CD

/1/ Commissioning Guide MDA Machine, Edition 10/2007 /2/ Installation of Oracle for MDA /3/ Customizing MDA, Edition 10/2007

1.2 Prerequisites

General

MDA collects its data with the Microsoft SQL Server Desktop Engine (MSDE) 2000 or SQL Server 2005 Express. If it is not installed, the set up can be started during the MDA set up. Alternatively in projects (MDA Plant) Microsoft SQL Server or Oracle can be used as database server.

The MDA installation requires approximately 200 MB of hard disk space. Additionally the hard disk space for the database is needed (Standard for MSDE: 100 MB).

Any previous version must be removed before installing the new version (see chapter entitled 2.23 “Uninstalling“).

Administrator rights are required for installing. Demo

Standard PC (Pentium III)

512 MByte of RAM

Windows XP Professional, Windows Vista

Cell

Standard PC (Pentium III)

512 MByte of RAM

Ethernet connection

Windows XP Professional, Windows 2003, Windows Vista

I&S IS E&C IT OOP 3 © Siemens AG 2007 All Rights Reserved 1-1


1.3 MDA Components

1.3.1 System overview MDA is designed for a group solution. In a Group one superordinate host (MDA Cell or MDA Plant) and several workstations (Acquisition PCs/MMCs) work together. The acquisition data of the worksta-tions are transfered to the MDA server, so centralized and comparative evaluations can be done.



2 Installation

2.1 Overview

The installation of the total cell system is completed in several separate steps:

Installation of MDA IFC or MDA Machine at the workstations (see MDA Machine Commissioning Guide /1/)

Installation of MDA Cell at MDA Server (chap. 2)

Customizing of the complete system at MDA server including thecustomizings for the workstations (see Customizing MDA /3/). This contains the customizing of the process interface (/3/, chap. “Interfaces”)

SW-Update of the workstations centrally from MDA Server. Not before this update the communcation software for data transfer to MDA Server is activated at the workstations. (see Customizing MDA /3/)

Transfer of the customizing from MDA Server to the workstations (see Customizing MDA /3/)

Installation is completed in several separate steps, which are handled by the Setup.exe installation routine:

Installation of Microsoft SQL Server Desktop Engine 2000 respectively Microsoft SQL Server 2005 Express on Windows Vista (if not installed yet)

Installing database interfaces (MDAC Version 2.8) (if not installed yet)

Installing MDA

If the installation routine detects that MSDE 2000, SQL Server 2005 Express or MDAC is already installed on the computer, it automatically skips this part of the installation and immediately goes over to installing MDA. If one of the packages also needs to be installed, the installation routine prompts you to reboot the computer on completing installation.

During installation of MDA, amongst other things, you must enter a product key that the installation routine uses to detect the variant that is to be installed.

Considering paths it is assumed in this documentation that MDA is installed into the directory C:\Siemens\MCIS. In the sections below this MCIS installation path is referred to as <MCISDIR> and the subdirectory MDA as <MDADIR>.

User inputs of the dialogs and some internal function calls are written to the log file <MDADIR>\Install\aSetup.log. If there are any errors during installation this file may help you.



2.2 Backing up the Databases and Settings of Older Versions

If an older Version of MDA Cell is already installed on the computer on which you want to install MDA Cell, and you want to import the data, you must proceed as described below before installing the new version.

2.2.1 Upgrading MDA Cell

Save your old MDA database OSFDB_Transfer.mdb for MDA V2 or MDA.mdb for MDA V1 respectively so that the system can apply this data later in the new version. For doing that start the script CopyMDADB.bat in directory <MCISDIR>\tools.

If you have changed the interfaces to the process and you wish to use them again, you have to save the files Pit*.ini und Amt.ini.

After this, uninstall the older MDA Cell version.



2.3 Preparatory Step

Computer name (Network identification)

For the operation of MDA on the MDA server a host name with a maximal length of eight characters is necessary (due to Message Manager). You should use a definite name, otherwise later manual modifications are necessary later on (see chapter 4.3 ”Computer name of the MDA Server self“). It is possible to use any customer specific computer name and to establish an additional alias name.

For example: computer name = NBGM27665234 and alias = pdaservr.

User administration

In the Windows User Manager create the group MDAGRP and the following users:

User Password *1 Groups Usage / Comment MDAGRP Group for MDA processes and

users which operate MDA or access network shares. Here you must add the Windows internal user account INTERACTIVE.

*2PDA PDA User MDA Server-Prozesse

*3PDASYSTEM (Domain) Administrators MDAGRP

Installations, teleservicing of MDA

*4AUDUSER Users MDAGRP

Remote control of MDA workstations;

Xxxx Xxxx Users MDAGRP

All users which operate MDA

*1 The Password listed above are only suggested values to make an optional teleservice more easy. *2 User PDA or any other user used for starting MDA needs the privilege „Logon as a Service“ which can give to him via the local security policies. *3 User PDASYSTEM or any other user is used for teleservice only. *4 The password of user AUDUSER must confirm to that at SINUMERIK 840D. This user is needed only if SINUMERIK 840D workstations will be connected. To simplify creation of group MDAGRP you can start Create_MDA_group.bat in the directory <MCISDIR>\tools. In case of a operating system with system language not equal English or German you must add the Windows internal user account INTERACTIVE manually. Check if normal MDA users respectively group MDAGRP have write permissions in the root directory of the MDA target drive (e.g. C:\). If they don’t have this permission, create the MDA target root directory, e.g. C:\Siemens and grant the write permissions accordingly (see chapter 4.1). If you use Oracle please check permissions on the Oracle directories (program and data directory) too.



2.4 Use of eastern european or asian languages

For using eastern European or asian languages, e. g. Chinese, within the user interfaces the language settings of the operating system have to be set up. Windows XP / Windows 2003:

In Control Panel in Regional and Language Options set chinese in tab Advanced as Language for non-Unicode programs.

This practice is valid for other languages than chinese language analogous.

2.5 Supplementary installation of further languages

If you need the texts of a further language after completed installation, this can be done by starting the program CopyDatabase.exe in directory <MDADIR>\Install. With the select language dialog you choose the additional languages:



2.6 Installation of the database program

Alternatively to the the database management with Microsoft SQL Server Desktop Engine a database with Microsoft SQL Server or ORACLE can be used project-specifically (MDA Plant). In this case these database management systems must be established ready before the MDA installation.

Released versions:

• Microsoft SQL Server 2000 / 2005

• Oracle Version 9.2.0

2.6.1 Microsoft SQL Server Desktop Engine SQL Server Desktop Engine 2000 is the default database server of MDA Cell. You can install it your-self in advance or with the MDA setup program. The installation in advance is advisable if the newest service pack is necessary. The actual version on CD is SP3a.

At PCs running with Windows Vista operating system SQL Server 2005 Express is used instead of MSDE 2000. This database engine requires .NET runtime V2.0 as well as Microsoft Installer V 3.1. The use on older operating systems is abstained from therefore.

If you wish to use SQL Server 2005 Express at a PC running without Windows Vista operating system you have to install SQL Server 2005 Express first. MDA setup finds the existing database program and uses it.

2.6.2 Microsoft SQL Server Install SQL Server 2000 or 2005 using its setup program. The necessary steps are described in the Help for SQL Server Setup. As authentication mode you should use Mixed Mode Authentication.

2.6.3 Oracle Install Oracle version 9.2.0 with its setup program. The necessary Steps are described in the Help for Oracle Setup. In all path specifications of this document we assume that Oracle is installed in directory D:\Oracle\Ora92. Further information concerning the ORACLE installation you can find in /2/ chapter “Installation of Oracle 9.2.0” and “Installing Oracle 9.2.0 Client Standard”.

Note: After installation of Oracle you have to make sure, that the Windows group “Users” has read permissions to the Oracle directory. Otherwise the MDA programs can not access the database.



2.7 Starting Installation

Start the Setup.exe program

from the MDA drive (local, CD-drive or network).

2.8 Installation Dialogs (Step 1)

During the first step all necessary dialogs are called:

Continue installation by clicking the Next button.

Accept the license conditions with clicking the Yes button.

Check that all other programs are finished and continue with clicking the Next button.

Now enter the license key in the following screen forms. This information determines the MDA variant that is installed (Demo version product key: 01-01-01-059940).

Enter name and company of the registrated user and continue with clicking the Next button.

You can specify the installation directory of MCIS in the next dialog window. Enter the directory or accept the default directory and continue installation by clicking the Next button.

In the next screen you select the database program. MSDE is used by default. Within projects (MDA Plant) you can select SQL Server or ORACLE. Then you continue the installation by clicking the Next button.

In the next screens the size of the database is determined. At this the initial value, the maximal size and the extension step first for the data area and subsequently for the index area are to be



specified. The index area should have approximately the size of the data area. If you do not ex-pect a particularly high emerge of data you can accept the suggested values. Otherwise you must calculate the database size that is expected. Then you continue the installation by clicking the Next button.

Enter the path to the database files. Bear in mind that the data space requirement can be very high on the specified drive especially using SQL Server or ORACLE databases. In the case of a manual creation of an ORACLE database the input will not be considered. If there are MCIS products already installed you have to accept the default directory. Otherwise you can change the path. Please continue now by clicking the Next button.

In the next screen form, you can choose to use further MCIS packages. If yes a general MCIS database will be created additionally to the MCIS MDA database. Choose and continue installation by clicking the Next button.

In the next screen form the own computer name is determined and showed. Continue the installation by clicking the Next button.

In the next screen the IP address of the own computer is determined and showed. Check it and continue installation by clicking the Next button.

In the next screen form, you can choose to install Unicode user interfaces of MDA. This is only for asian languages like Chinese necessary. Choose and continue installation by clicking the Next button.

In the next screen form, you can choose the program folder in which you want to enter MDA. Accept the default settings and continue installation by clicking the Next button.

All input data is stored. Then MDA setup continues with the external packets in the next steps. Thereby it is always verified whether the packet is already installed.



2.9 Installation Microsoft SQL Server Desktop Engine (Step 2)

(only if necessary – not for demo version and Oracle or SQL Server database)

The MDA data administration is performed by the Microsoft SQL Server Desktop Engine (MSDE).

At PCs running with Windows Vista operating system SQL Server 2005 Express is used instead of MSDE 2000. The installation is be done analogous.

In this step the installation program checks if a sufficiently new version already exists on your computer. If not a current version can be installed automatically.

Notice: It is not possible to automatically uninstall MSDE. You can uninstall MSDE manually within control panel. It is retained even if you uninstall MDA on the target system!

Continue the installation by clicking the OK button.

Now the installation program installs MSDE. In some cases the following dialog appears: „The following applications should be closed before continuing the install: MDA x.x”. Continue with „Ignore“.

Finish the installation of MDA after installation of MSDE.

The restart of the PC is carried out automatically.

After restart of the PC the MDA setup will be started automatically. If the setup does not come up automatically please start Setup.exe manually again.

Note: Installation at computer with Windows XP without SP2: After executing the Setup of MSDE-Database the following message appears:

" Windows File Protection: Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stabilty, Windows must restore the original versions of these files. "

Insert your Windows XP Professional CD-ROM now.

Retry More Information Cancel "

Please press "Cancel" and confirm the following message:

" You choose not to restore the original versions of the files. This may affect Windows stability Are you sure you want to keep these unrecognized file Versions ? "

with "YES".

After the necessary Reboot the MSDE-Database is working without problems.



2.10 Installation of Microsoft Data Access Components (Step 3)

(only if necessary)

If necessary the installation program installs the database interfaces of Microsoft Data Access Components (MDAC) V2.8 in this st.

With the appearance of the message box “installing Microsoft Data Access Components (MDAC)...“ the database interfaces (MDAC V2.8) are installed.

Notice: It is not possible to automatically uninstall MDAC. It is retained even if you uninstall MDA on the target system!



2.11 Installing MDA (Step 4)

In this step the installation program installs MDA.

Now all the MDA components are installed.

In the case of MSDE or SQL Server being used as database system:

Now the message “Creating MDA Database ...“ is shown and the MDA database is established. Afterwards the data of the delivery is copied – this process takes some time. Notice: MDA supports several languages. To avoid always copying of all languages to the destination database you have to choose the wished languages within a dialog:

Preset values are German (DEUTSCH) and English. For eastern european or asian languages attend to chapter 2.4 „Use of eastern european or asian languages “. Please do not change checkbox „Installation mode“.

In the case of the ORACLE database management system being used, the database has to be created separately (see chapter 2.13 ”Creating the Oracle database (Step 5)“).

Finish the installation in the next form by clicking the Finish button.

Check date and time and adjust them if necessary.



2.12 Directory structure of MDA

During installation the following directory structure was created:

<MCISDIR> Common

Errors

Etc

MDA

Terminals Software update of workstations

Tools

-

+

Bitmaps Bitmaps, Icons

save database backup

Install installation files

Transfer directory for data transfer to workstations

+

Program files of MDA server

DATA MCIS data directory -

MDA MDA database files

The structure of directory Terminals for software update is described in see Customizing MDA /3/.



2.13 Creating the Oracle database (Step 5)

(only if using Oracle database)

If Oracle is used as database program, the database has to be created separately (see /2/ chapter “Create OSFDB Database”).

Afterwards copy the delivered MDA data into the database. For this you execute the script InitDB.bat in the installation directory <MDADIR>\MDA\Install.

2.14 Creating of local Windows group MDAGRP (Step 6)

The local Windows group MDAGRP is used for the access permissions to MDA components and shared directories. This group is created during setup automatically. To simplify adding further users or groups to group MDAGRP you can start Create_MDA_group.bat in the directory <MCISDIR>\tools. In case of a operating system with system language not equal English or German you must add the Windows internal user account INTERACTIVE manually.

2.15 Customizing of Data Backup (Step 7)

2.15.1 General Insert time-controlled functions for data backup. To do this start Control Panel application “Scheduled Tasks”. With the help of the assistant you can add a new task to start script pdaexp.bat in <MDADIR>. This script generates a database backup in directory <MDADIR>/save.

2.15.2 SQL Server For Microsoft SQL Server there exists a second variant, back up using the SQL Server Enterprise Manager. In general, preventive maintenance personnel carries out this type of data backup and it needs no further support. 2.16 Maintenance of Microsoft SQL Server database (Step 8)

If you use a Microsoft SQL Server database and the data traffic is very high you should start a function for reorganizing the database indices at regular intervals (e. g. once a week). To do this start Control Panel application “Scheduled Tasks”. With the help of the assistant you can add a new task to start script ReIndexAll.bat in <MDADIR>\Install. For Oracle databases this issue is not relevant. When using MSDE it is not relevant too, because in any case with such huge data traffic it is recommended to use Microsoft SQL Server.



2.17 MDA Startservice and DCOM Settings (Step 9)

MDA Cell shall run without logged in user, e. g. the MDA server PC is placed in a server room and the collecting data must be done permanently. For that a MDA start service is to be activated and some DCOM settings are to be configured. To simplify this you can start Create_MDA_Service.bat in the directory <MCISDIR>\tools. Then you should check access and launch rights for the MDA DCOM objects: Since Windows XP regardingly Windows 2003: • You find the general DCOM settings in Component Services of Control Panel with following

sequence: Component Services -> Computer -> My Computer Right-click Properties in the pop-up menu.

• Tab “Default Properties”: √ Enable Distributed COM on this computer

• Tab “Default COM Security”: Check Access Permissions – Edit Default... for the following items:

• SELF

• SYSTEM

• MDAGRP

Check Launch Permissions - Edit Default... for the following items:

• Administrators

• INTERACTIVE

• SYSTEM

• MDAGRP



2.18 Shared directories

2.18.1 Server During setup of MDA Cell or Plant the following directories are shared for network access: Directory share name comment <MDADIR>\Transfer Transfer Transfer point for MdeTransfer <MCISDIR>\Terminals\Reply Reply Answer of software update <MCISDIR>\Terminals\Update Update Transfer point for software update The security settings for these shares are full control for local group MDAGRP. The file sharing permission for this group must be “full control” and the file security “modify”. In cooperation with the IT network administration it must be guaranteed that the MDA workstations have “Full Control” of these directories. This means, the users MDA is running at the workstations are member of group MDAGRP. Here different cases with respect to MDA workstations have to be kept in mind.

MMC 103

The MMC103 is a computer with Windows 95 operating system. The user which is used for the network login must be configured on the server as a local user with the same password and with membership in group MDAGRP.

PCU 50

The PCU50 (e.g. OP012) is a computer with Windows NT or Windows XP operating system. The standard system start takes place under the local user “AUDUSER”. Here it must be decided whether the MDA workstation is to be started under a domain user (Autologon) or if a local user AUDUSER is established on the MDA server as well with membership in group MDAGRP. In case of using local user the password at the server and at the PCU 50 must be identical. Therefore it is not possible to connect a PCU 50 running under an AUDUSER user with a different password! For the Autologon under Windows NT the following registry entries are crucial:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "DefaultUserName"="AUDUSER" "DefaultPassword"="????" "DefaultDomainName"="xxxx"

Standard PC

Standard PCs should always be configured in the same Windows domain as the MDA server. MDA should run under a domain user (e.g. <domain>\PDA). Here the “Full Control” permission of the shared directories for these special domain user or membership in group MDAGRP is then sufficient. Alternatively to use a domain the PCs may be member of the same workgroup.



2.18.2 Workstations For remote control of software update of the acquisition workstations the shared directory Update$ must exist on these workstations with write permission for the user on the MDA server (normally user PDA or AUDUSER for SINUMERIK respectively). Directory Share name comment <MDADIR>\RemoteControl Update$ Remote control of software update 2.19 Firewall

Since Windows XP you have to switch on the Windows Firewall File and Printer Sharing.

Additionally for Windows Vista you have to activate the Public folder sharing with the Network and Sharing Center.

For opening of TCP/IP port 3501, which is used for the online connection of the MDA workstations to the server, you can start the script MDA_Cell_Firewall.bat in directory <MCISDIR>\tools. Port 3409 is used for testing the PC connections.

2.20 Restoring Earlier Databases and Settings (Optional)

2.20.1 Upgrading MDA Cell

If a MDA Cell upgrade has been installed on the computer, the previous MDA database (OSFDB_Transfer.mdb for MDA V2.0 and later or MDA.mdb for MDA V1) backed up before the installation can now be taken over.

You can either copy the complete database without changes or upgrade it in case of different MDA versions.

Database upgrade: (in case of different MDA versions necessary)

Procedure:

Rename the previous MDA database by prefixing the previous database names with OLD_ ( OLD_OSFDB_Transfer.mdb or OLD_MDA.mdb.

Copy the databases to the MDA installation directory.

Start the MdaUpgradeDbs.exe program.

Operate the Execute button.

The MdaUpgradeDbs.exe program copies all acquired data, statistics, status definitions, evaluation definitions, the works calendar and the work centres into the new database. Only the active configuration data is taken over. All screen form texts, error texts, user rights and the screen form layout are not taken over. General settings are partly updated so that you need to check them with the user interface “Customizing (User)” afterwards.



Copy complete Database without changes: (only in case of identical MDA versions)

Procedure:

Rename the previous MDA database by prefixing the previous database names with OLD_ (OLD_OSFDB_Transfer.mdb).

Copy the database to the directory <MCISDIR>\Tools.

Start program <MCISDIR>\Tools\CopyDatabase.exe.

Select as Source database : Provider: MSDASQL Connection: DRIVER={Microsoft Access Driver (*.mdb)};UID=;PWD=;DBQ=.\OLD_OSFDB_Transfer.mdb; and as Destination database: Provider: SQLOLEDB Connection: driver={SQL Server};Server=(local);Database=OSFDB;User Id=OSF;Password=4SF;

Operate the OK button.

Operate the buttons (De)Select All, Delete existing records at start copying and finally OK.

The CopyDatabase.exe program copies all acquired data and all configuration data into the new database.



2.21 Starting MDA

The background programs of MDA are started automatically during system start. The user interfaces you can activate with the Start menu (Start > Program Files > MCIS MDA).

With the installation a Customizing comes, which can be adjusted to the customer plant.

2.22 Demo data

th thIf the Demo version of MDA has been installed, the demo data from 28 November 2006 to 24 March 2007 can be viewed and analysed in MDA. There are alarms only for „Machine 1“.

2.23 Uninstalling

Backup the old MDA database, if you wish to transfer the data to a new version at a later date. For that start the script CopyMDADB.bat in the tools-directory. The data are stored in the file OSFDB_Transfer.mdb and can be copied into the new database with the program CopyDatabese.exe later.

Delete the MDA database, if you used Oracle, using the Oracle Database Configuration assistant.

Run the script Uninstall_MDA.bat. This starts Control Panel Add/Remove Programs or Software first. Using this uninstall MDA. Afterwards the database and the MDA installation directory will be deleted.

Reboot the computer.

2.24 Works calendar

Using the MDA Works Calendar program (Start > Program Files > MCIS MDA > Works Calendar) you have to define the calendar into the future according to the default week (see /3/). Otherwise no shift specific evaluations are possible. For the current shift always shift number 0 will be reported. Notice: Modifications in the works calendar will not be valid before the next day.



2.25 MDA server with MDA data acquisition

In contrast to earlier versions of MDA, there exists no separate installation of MDA acquisition (MDA Machine or IFC) and evaluation (MDA Cell or Plant) at the same PC. Within MDA Cell configuration the data acquisition will be activated by the user interface Customizing (User) with tree node “Theme-related Parameters” instead (see /3/, chapter 2.11 “Overview of Important General Parameters”). You have to notice that MDA Cell is running within a service and not all data acquisition interfaces can be run within a service ! For these interfaces a separate data acquisition PC with MDA IFC is recommented.

2.25.1 Starting of MDA data acquisition within the start service This start method must not be used for the following interfaces:

• OPC interface ProTool/Pro and WinCC flexible • Test interface

To start the data acquisition programs, you have to activate the following entry in file <MDADIR>\MDAStartService.ini with deleting the semicolon at X_FILE_1:

[START_ACTIVE_X] ;X_FILE_1=MdeServer.MdeMethods

2.25.2 Starting of MDA data acquisition outside the start service The data acquisition programs are started not until a user logs on to Windows with this starting type. To do so you have to put a link to program <MDADIR>\StartMDE.exe into the autostart folder of all users. If you want to force the logging on of an user to Windows on system start up you may use the possibility of Windows’ autologon. You can configure that a specific user will be logged on without any loggin mask during system start up automatically. You can also change the shell, which is the systems graphical user interface. For that you can use the tool MDA_Autologon.hta in directory <MCISDIR>\tools.



3 Further Actions

After the installation of MDA the following actions have to be done:

Customizing of the complete system with the customizing of the workstations (see /3/). This includes the customizing of the process interface (chapter “Interfaces”).

Software update of the workstations from MDA server, centrally. The communication software for data transfer to the MDA server will be activated by this update (see /3/).

Transfer of the MDA server’s customizing to the workstations (see /3/).



4 Tips & Tricks

4.1 Missing Write Permissions as of Windows 2000 / Windows XP

As of Windows 2000 it can happen that normal users don’t have write permissions for the directory C:\ . This leads to the situation that the directory tree for MDA being created during the installation has also no write permissions for normal users. If now MDA is to be operated by such a normal user without the priviliges of an administrator or power user errors occur. After the installation you should check and assure in the Windows Explorer if also normal users (especially group MDAGRP) have write permissions in the MDA directories! 4.2 Extending Database

If the actaul database size is not sufficient the maximum size can be increased by script. For that the script <MDADIR>\Install\ExpandDBsize.bat is used. As start parameter the password of database user sa is passed. In file ExpandDBsize.sql the maximum database size can be changed. 4.3 Computer name of the MDA Server self

During the installation of MDA Cell or Plant the name of the computer self is determined, prompted and put into several configuration files. If the computer name is modified later on these files have to be adjusted:

Search in path <MCISDIR>\Terminals for files, which contain the old computer name. Replace it with the new one.

<MCISDIR>\etc\function

Making these changes can be done with the program ChangeServerPCName.exe in the tools-directory <MCISDIR>\tools.

4.4 Windows User

Per default a Windows user, e. g. “PDA“, should be created for MDA. Under this user the MDA server processes are started. The user on the MDA HMI workstations can logon under any user.

At the workstations the MDA processes must be started by a Windows Power User, because for software update and time synchronistation functionality advanced privileges and permissions are necessary. These privileges and permissions are owned by members of local groups Power User and Administrators. Power User permissions are sufficient for MDA. 4.5 Password of the Windows user PDA has changed

The password of the user PDA is stored for the PDA start service as well as the DCOM settings for the event handler and MdeServer if necessary. Here the password must be re-entered.

4.6 Password of Database user PDA has changed



The password of the ORACLE user PDA is important for the database access. The affected files are:

<MDADIR>\MdeServer.ini <MCISDIR>\Common\MdeServer.ini <MCISDIR>\Tools\MdeServer.ini <MDADIR>\pdaimp.bat <MDADIR>\pdaexp.bat <MDADIR>\pdaimp_user_new.sql <MDADIR>\Install\Oracle_Create_Tables_Triggers.bat <MDADIR>\Install\Oracle_DoAll.bat <MDADIR>\Install\Oracle_Create_Users.sql

Using the SQL server the following scripts must be modified in the respective folders:

<MDADIR>\MdeServer.ini <MCISDIR>\Common\MdeServer.ini <MCISDIR>\Tools\MdeServer.ini <MDADIR>\pdaimp.bat <MDADIR>\pdaexp.bat

4.7 Log files of Installation

User inputs of the dialogs and some internal function calls are written to the log file <MDADIR>\Install\aSetup.log. If there are any errors during installation this file may help you.

Logging iformations of MSDE setup are in file msde.log.

Further log files contain informations of the database scripts.



5 Appendix

5.1 Database size of MSDE and SQL Server

In the case of very big data volumina or if your data shall be stored over a large time period (longer than 3 years for month and year statistics and longer than 1 year for weak, day and shift data), calculate the database size with following table.

Define number of machine logbook and protocol entries

Forecast parameter N, M and O

Choose their time units

Table Formula Result

Logbook 440 Byte * Number

Machine statuses (MDA)

Protokoll 340 Byte * Number

PrioProtokoll 360 Byte * Number

Schichtsumme 200 Byte * N * Number Shifts

Tagessumme 200 Byte * N * Number Days

Wochensumme 200 Byte * N * Number Weeks

Monatssumme 200 Byte * N * Number Months

Jahressumme 200 Byte * N * Number Years

N = Sum of all machine statuses of all work centres

Part data (PDA)


Schichtumme 260 Byte * M * Number Shifts

Tagessumme 260 Byte * M * Number Days

Wochensumme 260 Byte * M * Number Weeks

Monatssumme 260 Byte * M * Number Months

Jahressumme 260 Byte * M * Number Years

M = Number of all part types in this time for all work centres

Alarm data

Texts 300 Byte * Number of all alarm texts for all work centres

Logbook 300 Byte * Number


Schichtumme 200 Byte * O * Number Shifts

Tagessumme 200 Byte * O * Number Days




Wochensumme 200 Byte * O * Number Weeks

Monatssumme 200 Byte * O * Number Months

Jahressumme 200 Byte * O * Number Years

O = Number of all alarms in this time for all work centres

Sum

.

Commissioning Guide MDA Cell - support.industry.siemens… · 4.5 Password of the Windows user ......

Documents

Transcript of Commissioning Guide MDA Cell - support.industry.siemens… · 4.5 Password of the Windows user ......