Software Requirements

Software Requirements

1.1                 Operating Environment

Operating systems

STEP 7 V5.4 including SP3 is a 32-bit application that is released for the following operating systems:

Operating System	Service Pack
MS Windows 2000 Professional	SP4
MS Windows XP Professional	SP2

·         MS Windows Server 2003 SP2 Standard Edition with or without R2 as workstation
computer (exception: SIMATIC M7, see also, instructions in Section 6.18)

·         MS Windows Vista 32 Bit Ultimate and Business

You can find information about the operating systems on the Internet at Microsoft.

STEP 7 V5.4 including SP3 will not run in:

·         MS Windows 3.1

·         MS Windows for Workgroups 3.11

·         MS Windows XP Home

·         MS Windows Vista Home Basic and Premium

The operating systems MS Windows 95, MS Windows 98SE, MS Windows Millennium and MS Windows NT 4.0 are no longer supported since STEP 7 V5.3.

Important additional information:

An operating system update from MS Windows XP to MS Windows Vista is not allowed or possible for existing STEP 7 installation.

Internet Explorer

All operating systems must be using MS Internet Explorer 6.0 (or higher).

User rights

Regarding user rights as of STEP 7 V5.4 including SP3, please observe the following:

To be able to work with STEP 7, you must have logged on at least as the user (not as a guest).

You need administrator rights to be able to install the STEP 7 software and HSPs, set up user groups and change the settings using "Set PG/PC Interface" function.

When using optional packages please observe the rights required by the respective optional packages.

If projects are saved on NTFS drives, the users must be granted full access here. This also applies to the folders with the HSP updates (default: C:/HWUPDATES). Access within the standard project directory S7PROJ is automatically granted to all users.

Note: The executability under user rights is only enabled for STEP 7 itself. Operation under user rights for optional packages is not guaranteed. Administrator or primary user rights may be required here. After installing / uninstalling new hardware, the computer must be run at least once under administrator rights.

File systems

STEP 7 achieves a slightly lower performance when operating on a MS Windows NT file system (NTFS) as opposed to a FAT file system.

Hibernation mode

Shifting to hibernation mode is generally allowed by STEP 7. However, hibernation must not be triggered if online connections are open or projects are being accessed by STEP 7 applications via a network.

In such case, online connections could be unintentionally terminated, and open projects on networks may experience data loss.

For these reasons, the energy options for the operating system in the Windows Control Panel should be set so that hibernation is not automatically triggered (by timer). Hibernation should not be triggered manually by the user in the cases mentioned above.

Hardware Requirements

     Hardware Requirements

In order to work with the STEP 7 V5.4 including SP3 software, you need a programming device or a PC with the following minimum requirements for processor speed/performance, RAM and graphics capability:

Operating System	Minimum Requirements for:
	Processor	RAM	Graphics
MS Windows 2000 Professional	600MHz	512 MB *)	XGA 1024x768 16-bit color depth
MS Windows XP Professional	600MHz	512 MB *)	XGA 1024x768 16-bit color depth
MS Windows Server 2003	2.4 GHz	1 GB	XGA 1024x768 16-bit color depth
MS Windows Vista Business	1 GHz	1GB **)	XGA 1024x768 16-bit color depth
MS Windows Vista Ultimate	1 GHz	1GB **)	XGA 1024x768 16-bit color depth
MS Windows Vista Enterprise	1 GHz	1GB **)	XGA 1024x768 16-bit color depth
*) At least 1 GB RAM is recommended **) At least 2 GB RAM is recommended

Use a programming device or PC with the latest performance capabilities if you are editing extensive STEP 7 projects or working with hardware configurations containing several hundred modules (CPUs, slaves, I/O devices, etc.).

In addition, you will need an external prommer for SIMATIC memory cards / MMC if you are using a PC and want to save your user programs to EPROMs and a SIMATIC NET interface if you want to use online functions to the PLC system with your personal computer.

Additional Style” can only be used with a high-performance graphic adapter. It requires:

·         DirectX9 capability

information on Windows Vista:

The “Aero Glass 128 MB separate graphic memory

·         The performance of the graphics system architecture can have a substantial affect on the performance of STEP 7.

Canceling the License Key Transfer of Automation License Manager

Canceling the License Key Transfer

When license keys are transferred between a computer on which an older version of the Automation License Manager is installed and a computer with a newer Automation License Manager, an error message sometimes is displayed and the transfer is canceled.

Remedy: The computer on which an older version of the Automation License Manager is installed has to be updated to a current Automation License Manager version.

Using Earlier Software Product Versions with a New License Key

Software products, which are activated with a License Key

Software products to be activated for operation with license keys can also use later license keys. The following applies to these products:

·      "Later" versions of license keys can always be used to operate different software versions.

·      It is therefore not necessary to downgrade a license key in order to use "earlier" versions.

Note You can recognize a license key in the Automation License Manager by the 20-digit license number.

Software products, which are activated with an authorization

These software versions cannot be operated with a license key. License keys for later versions can only be used for software versions in which a license key is used.

Note You can recognize an authorization in the Automation License Manager by the 10-digit license number.

License Upgrade of Automation License Manager

License Upgrade

The following steps show you how to upgrade a license key and an authorization. The actions are the same for the license key and authorization,  however reference is made to license key only in the text.

1.   Select the view via the menu command View > Management.

2.   Transfer the License Keys of the previous version and the Upgrade License Keys to the hard disk, on which the upgrade is to be performed.

3.   In the navigation area, select the location of the license key for which the upgrade is to be performed (previous version).

4.   In the object area, select the license key for which the upgrade is to be performed.

5.   Select the menu command License Key > Upgrade.

Result: Upgrade is executed.

Upgrading and Using "Older Software Products"

Upgrading and Using "Older Software Products"

Note You have to distinguish between: ·          Upgrading a license key to a new license key ·          Upgrading an authorization to a license key ·          Upgrading an authorization to a new authorization

1.1                 Upgrade Requirements

Earlier License Key → New License Key

You require:

·      the CoL (Certificate of License) and the license key of the earlier version

·      the CoL (Certificate of License) and the upgrade license key of the target version

Earlier Authorization → New License Key

You require:

·      the earlier authorization

·      the CoL (Certificate of License) and the upgrade license key of the target version

Earlier Authorization → New Authorization

You require:

·      the earlier authorization

·      the CoL (Certificate of License) and the upgrade authorization of the target version

Note You can recognize a license key in the Automation License Manager by the 20-digit license number.

How to Remove the Automation License Manager

  How to Remove the Automation License Manager

The removal of the Automation License Managers must conform to the standard Windows routine for removing programs. To do this, select the menu command

Start > Settings > Control Panel > Add/remove software

and then select the "Automation License Manager" program from the list of installed software. This is the only way to correctly remove the program under Windows.

How to Install the Automation License Manager

1.1                 How to Install the Automation License Manager

The Automation License Manager is installed with a setup program.

Note Close all other programs before starting the setup from the supplied CD.

Installation

The setup program will guide you through the installation.

How to Transfer License Keys and Authorizations

1                     How to Transfer License Keys and Authorizations

The License Manager can be used to transfer license keys and authorizations that:

·      not transferred during the setup of a product (for example, STEP 7),

·      which belong to licenses bought at a later period.

Note The easiest way to transfer the license keys is by Drag & Drop.

1.1                 Drag-and-Drop

1.   Select the view via the menu command View > Management.

2.   Open the storage location on the local or network computer you wish to transfer the license keys to.

3.   Open the storage location on the local or network computer where you wish to remove the license keys.

4.   Select the license keys and drag them to the folder where you wish to save the license keys.

Result: The license keys are transferred.

1.2                 Connect Computer

With the Automation License Manager, you can connect computers on the network, on which the Automation License Manager is also installed. To do this, right-click on "My Computer" in the navigation area and select "Connect Computer" in the context-sensitive menu. A dialog box is displayed, in which you can:

·      specify the name of the computer you want to connect or

·      browse the network for computers.

In the "Display Name" dialog box, enter the name under which the computer is to be displayed. Then click on "OK".

Result: The computer is connected.

Software Requirements of Automation License Manager

Software Requirements

The Automation License Manager is a 32-bit application which is released for the following operating systems:

Operating System

·      MS Windows 2000 Professional SP4

·      MS Windows 2000 Server SP4 as a workstation computer

·      MS Windows XP Professional SP1, SP1a or SP2

·      Windows Server 2003 Standard Edition as a workstation computer.

·      MS Windows Server 2003 SP1 Standard Edition with or without R2 as a  
workstation computer.

·      MS Windows Server 2003 SP2 Standard Edition with or without R2 as a
workstation computer

·      MS Windows Vista32 Bit Business

·      MS Windows Vista32 Bit Ultimate

Hardware Requirements of Automation License Manager

  Hardware Requirements

You will need approximately 25 MB of space on your hard disk for the installation of the files. You will need additional space for your projects and database.

Any graphics-capable printer supported by your operating system can be used as the printer.

Automation License Manager V3.0 SP1

Automation License Manager V3.0 SP1

1.1                 Introduction

The Automation License Manager is a product of Siemens AG Automation & Drives Group and is the successor product of AuthorsW. It is used to manage license keys and the "authorizations" used in the past.

1.2                 Scope of Delivery

The software is provided on a CD.

License keys or authorizations are provided on specially created red or yellow diskettes that come with the software product, on USB memory sticks or as download-license keys via internet. A diskette may also contain authorizations with the counter state "0". These authorizations cannot be installed.

Working with fail-safe modules STEP 7, Version 5.4

Working with fail-safe modules

·         As of V5.4 SP 2, you can use the Options > Customize > View to set custom background colors for the display of non-fail-safe addresses in F blocks, which were created with the programming languages F-LAD or F-FBD. Requirement: S7 Distributed Safety >= V5.2 is installed.

·         As of V5.4 SP 2, you can also save F blocks, which were created with the programming languages F-LAD or F-FBD, as read-only. Requirement: S7 Distributed Safety >= V5.2 is installed.

·         As of V5.4 SP 2, you can also rewire F blocks, which were created with the programming languages F-LAD or F-FBD. Requirement: S7 Distributed Safety V5.4 SP2 and F #Configuration Pack V5.5 SP1 are installed.

·         As of V5.4 SP 2, you can also hide F blocks, which were created with the programming languages F-LAD or F-FBD, with a user-specific block filter in the list. When the "Also show F block" check box is activated, the selected object types are displayed with F blocks. When the "Also show F block" check box is not activated, the selected object types are displayed without F blocks. Requirement: S7 Distributed Safety >= V5.2 is installed.

---

# PDIAG