SIMATIC

STEP 7- Micro/WIN 32 V3.2

Copyright (c) Siemens Energy & Automation Inc., 2002
Contents
Notes on Installation
1
2
3

Hardware Requirements
Operating Environment
Installation

Notes on Usage
1

What's New in V3.2

1.1

What's New in V3.2

Known Problems and Remedies

2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3

Problems
WIPEOUT.EXE
National Languages
General Communications
Multi-Master Communications
PPI Communications
MPI Communications

Using the Force Function

Notes on Installation
1

Hardware Requirements

Microsoft Windows 95, Windows 98, Windows 2000, Windows Me, or Windows NT
A personal computer (PC) capable of running one of the above operating systems, refer to Microsoft's specifications
for more information.
At least 50 Mbytes of free hard disk space
Screen resolution of 1024x768 pixels
Any mouse supported by Microsoft Windows
For communicating with the S7-200 you will need one of the following:
1. A PC/PPI Cable connected to your serial communications port (PC COM1 or COM2)
2. A communications processor (CP) card and multipoint interface (MPI) cable
3. A multipoint interface (MPI) card and communications cable
Note: You must have at least a Pentium II 400 MHz class computer in order to use the PC/PPI Cable communication
option under multi-master mode on a Windows Me or a Windows 2000 operation system.
Note: STEP 7-Micro/WIN 32 is a 32-bit application that requires Microsoft Windows 95, Windows 98, Windows Me,
Windows NT or Windows 2000 as its operating system. It cannot run under Microsoft Windows 3.1, Microsoft
Windows for Workgroups 3.11, or any version of Windows NT prior to V4.0.
Note: Existing STEP 7-Micro/WIN configurations using Intelligent expansion modules (EM 253, EM2 41, EM 277)
should review the Intranet Simatic Update 9261022. In general, PLCs with firmware Version 1.2.1 (or greater) can use
the EM 253/EM 241/EM 277 module in any PLC slot. If PLCs with earlier firmware are used with the EM 253/EM

241, the EM must be adjacent to the PLC, or only other intelligent modules (such as EM 241, EM 253, EM 277) can
be between your EM 253 or EM 241 and the S7-200 PLC.

Operating Environment

To be able to work with STEP 7-Micro/WIN 32 software under Windows NT/2000, you must have logged on at least as
a power user. You must have administrator rights for the installation of the STEP 7-Micro/WIN 32 software and also
for setting up modules using the Set PG/PC Interface application.
It is recommended that you disable hibernation mode when using STEP 7-Micro/WIN. Entering hibernation mode
while online connections are open or while projects are being accessed by STEP 7-Micro/WIN 32 through a network
can cause the following errors:
unintentional termination of online connections
data loss in any open projects opened through a PC network
To avoid these errors, set the energy saving options for the operating system in the Windows Control Panel to manual
trigger, so that hibernation is not automatically triggered by a timer. Do not manually trigger hibernation mode during
a communication task, as described above.
STEP 7-Micro/WIN 32 Version 3.2 has been tested under the following operating system versions:
Windows 95
Windows 98, 2nd Edition
Windows NT, Version 4.0, SP5 and SP6
Windows Me Edition
Windows 2000, SP2
STEP 7-Micro/WIN32 V3.2 is not designed for use with 16-bit operating systems such as Windows 3.1 or Windows
3.11.

Installation

1. Close all applications including the MS-Office Toolbar.

2. Insert the STEP 7-Micro/WIN 32 CD into the CD-Rom drive. The Setup program will run automatically if you have
not disabled the auto start option. You can manually start the Setup program by double clicking the file "Setup.exe"
located on the CD.
3. Follow the instructions displayed to complete the installation.
Note: To install STEP7-Micro/WIN 32 on a Windows NT or Windows 2000 operating system, you must log in with
administrator rights. The new STEP 7-Micro/WIN 32 V3.2 is not tested, and therefore, not guaranteed to work on the
Windows XP operating system.
Note: When the user installs STEP 7-Micro/WIN32 Version 3.2 from a CD ROM, the installation prompts the
user for the target directory. If a previous STEP 7-Micro/WIN32 version is already installed on the system, an uninstall of the previous version occurs if the same directory name is selected for both versions. Installing to another
directory results in two different versions of STEP 7-Micro/WIN32 being successfully installed on the same PC. Two
identical versions of STEP 7-Micro/WIN32 cannot exist on the same PC.

Notes on Usage
1

What's New in V3.2

User-defined Library support

Ability to create User-defined Libraries to protect and re-use selected parts of your programs

Ability for password protection

Portability between projects
Ability for code dependency checks
Ability for user-assignments for properties such as the title, version, and directory path
Ability for each user-defined library to have its own library symbol table that is optionally shown
New Instructions
String instructions* for tasks such as string copies, length calculation, string and character searches, and string
concatenation, etc. that are frequently needed with Freeport, Modem, and other string-oriented tasks.
Conditional Sequence Control Relay End (CSCRE)* instruction marks the end of an SCR segment only when power is
applied to the input.
Reset/Set and Set/Reset Bi-stable latch instructions* are now in the SIMATIC editors.
Execution Status with Power Flow* provides network-by-network real-time status.
POU (Program Organizational Unit) Editing Improvements:
Create hidden POUs using passwords, allowing protection of your customer's proprietary code segments
Right click on the POU tab provides new options for editing: Easy Cut, Copy and Paste between POUs including the
LVT (Local Variable Table), access to the POU properties, ability to rename, to delete, etc.
Visible POU comments are placed in the POU header and have unlimited length. They can be optionally toggled
On/Off from the toolbar icon.
Configure or modify standard POU functions from a right-mouse click on the tab; rename any tab by double clicking
on it.
Print Improvements offer world-class printing for Micro/WIN project documentation:
Print wrapping with the LAD and FBD Network rungs.
Optional Print Settings for:
Local Variable Table
System Block
Cross Reference
Properties of the program editor or data block
Split Network option for LAD and FBD editors
Print small sections by simply Highlighting partial networks (print dialog settings for ranges still available)
Improved Print Preview with options to select individual project entities using tabs and icons.
New Wizards for the Position control and Modem expansion
Makes complex application tasks quick and easy and reduces long hours of configuration time down to just minutes.
The NEW EM 253 Position control module configures parameters such as acceleration and deceleration rates,
reference point seeks, Jerk (S-curve), up to 25 motion profiles with 4-step per profile, etc.
The NEW EM 241Modem expansion module configures parameters such as: PPI or MODBUS protocol, messaging
(paging), callback, module password, etc.
The NEW Modem Expansion Wizard has the option to program a remote analog or cell phone modem.
The NEW Position Control Wizard has the option to program the onboard S7-200 PTO/PWM outputs.
Wizards improvements offer added parameterization assistance plus the ability to be re-read:
Wizard configurations (with the exception of the HSC wizard) can now be 'reloaded' or 're-read' from existing projects.
Wizards can now check for program memory overlaps (excluding the data block).
Wizard fields now supply the default names for the programmer.
Wizards suggest the subroutine numbers automatically.
TD 200 Wizard has the ability to navigate directly to any other TD 200 configured messages.
TD 200 Wizard has the ability to copy TD 200 messages within the wizard by specifying the target message number.
HSC (High Speed Counter) Wizard now allows the programmer to enter addresses for PV and CV.
Graphical representation of NETR/NETW makes programming PLC transfers simple.
All configured PIDs share the same INT, which will improve performance. Each PID uses 1 SBR, and a maximum of
8 PIDs are allowed; the PID digital output minimum value is 0.1 second.
STL Editor Improvements
Allows switching between editors even if errors in the program logic exist.
Allows drag and drop from the instruction tree in all editors.

Numerous STL improvements now make STL more consistent with LAD and FBD: Symbolic and absolute are fully
supported, tab stop selection, ability to identify an operand, system information table, network comments, Drop &
Drag from Instruction Tree, etc.
Usability Improvements
After instruction is dropped in LAD or FBD editor, the editing cursor placement is determined by an option setting (to
match any programming style).
You can switch between editors even if errors in program logic exist.
Editors are now fully configurable with all modifiable settings available under options.
Data block format is maintained during the PLC upload (comments not included).
Environment (Frame settings) are now retained after closing and then re-opening projects.
The height of LAD and FBD Instructions are changed by modifying the program editor's font size (under options).
A ruler grid in upper border of the edit window allows you to see the width of the networks. For example, the ruler
grid is an indication of where the LAD/FBD network wrapping occur in a printout (shown in cm or inches depending
on the Option settings)
The 'File Save' default path name can be set under the 'Project' option.
Configurable options for font type, font size, colors of each program element type (constants, addresses, symbols,
comments, etc.).
Each network can has a text comment field with unlimited space (in addition to the 1-line network title).
Symbols and Symbol Table Improvements
System symbol table can be automatically generated for projects.
Improved visual indicators for detecting project errors, such as unused and overlapping symbols.
Automatic entry (into the symbol table) for undefined symbol names.
All Symbols used (in any editor) for a network are placed in a Symbol Information Table beneath each network rung
(optionally toggled On/Off from the toolbar icon).
Debugging improvements
Execution Status with Power Flow provides network-by-network real-time status in LAD and FBD.
Status chart modifications are possible without turning off status execution.
It is possible to build a status charts from simply highlighting a section of networks followed by a right mouse click.
Bookmarks are now available in all editors, with bookmarks retained after compiles, saves, and during status.
Triggered pauses added to the LAD and FBD editors (for gathering a snapshot during execution status).
Ability to Writing and Force PLC values using a right mouse click during execution status.
Standard Communications
Ability to find all networked CPUs at all baud rates
Improved communication through performance
The system block parameter settings are enabled or disabled to match the project's PLC Type setting.
In Micro/WIN, a change in a project's CPU type can be made from the communication dialog by selecting a PLC in
the communication 'life-list'
PLC types in Micro/WIN are now represented with the firmware revision in addition to the CPU model number.
New CPU models can be recognized by the Micro/WIN software without having to upgrade the S/W.
Modem setup is extended by the use of a new TAPI driver interface
Faster Baud Rate capability due to use of TAPI drivers
Support for Cell modems & Radio Modems (for the local Micro/WIN connection)
Standard windows TAPI provides support for multiple 'connections'
Support for the S7-300/400 STEP 7-Manager Tele-Service Adapter
Standard windows TAPI provides support for standard windows modem drivers (both internal and external)
* = Requires the latest S7-200 CPU Firmware: 221 Firmware Ver.1.2.0, 222, 224, 226, 226XM Firmware Ver.1.2.1
V3.2 Instruction Libraries
The new libraries installed with STEP 7-Micro/WIN32 Version 3.2 are supported on all 22x series CPUs, (CPU221,
CPU222, CPU224, CPU226 and CPU226XM at present). The 21x series CPU's do not support the libraries.
The new libraries will not work on versions of Micro/WIN prior to Version 3.2. Projects containing instructions from
the previous libraries will allow those instructions to be modified (copied, moved, etc.) within the project as necessary
without problems. However, the previous library instructions (i.e., USS Protocol version 1.0) cannot be used in the
same project with the new library instructions (i.e., USS Protocol version 2.0). When Micro/WIN is upgraded, any

instruction library that is already installed is upgraded automatically and the older library instructions will no longer
appear in the Micro/WIN instruction tree.
USS Protocol V1.0 instructions cannot be used in the same project with USS Protocol V2.0 instructions. The USS
instructions in each project must be of the same version. You may open an existing project and modify the old USS
instructions if needed; however, you will not be able to add more USS instructions because the old-style USS
instructions would not be compatible with the new-style instructions. Do not delete old instructions from your project
unless you want to upgrade to the new instructions because there is no way to re-insert them.
If you have to use USS Protocol V1.0 instructions in a previous project and you would like to upgrade to USS Protocol
V2.0 instructions, you have two alternatives:
1. Copy the existing project that contains the USS Protocol V1.0 instructions to a different project file. Delete all the
subroutines and interrupt routines created for the USS Protocol (USS_INIT, DRV_CTRL, READ_PM, WRITE_PM,
USS1, USS2, USS3, USS4, USS5, USS6, and USS7).
Search your project for each occurrence of the old USS Protocol instructions and replace these occurrences with the
new instructions (USS_INIT with USS_INIT, DRV_CTRL with USS_CTRL, READ_PM with USS_RPM_W, and
WRITE_PM with USS_WPM_W). Delete the old USS Protocol Symbol Table and assign the new V memory starting
address for the USS Protocol V2.0 instructions.
2. Create a new project and build the USS protocol interface with the USS V2.0 instructions.
The USS Protocol V1.0 library supported the Siemens Micro-master 3 (MM3) drives. The USS Protocol V2.0 library
supports both the Siemens Micro-master 3 (MM3) drives and the Siemens Micro-master 4 (MM4) drives. Because the
communications protocol for the new MM4 drives is significantly different from the previous MM3 drives, the added
support for multiple drive types will require more program memory in the PLC project: The old USS protocol library
required from 1250 to 1750 bytes of user program space. The new library requires 1970 to 3050 bytes of user program
space. The amount of V-memory space is not affected by the use of the library.
Any user defined library subroutine(s) or POU(s) cannot have the same name as those from the STEP 7-Micro/WIN
Instruction Library CD.
2

Known Problems and Remedies

2.1

Problems

1. It is possible to install more than one version of STEP 7-Micro/WIN 32 on a PC. However, after deinstallation of
one of the different versions, a reinstallation of the other versions of STEP 7-Micro/WIN 32 is necessary.
2. Windows 2000 auto-detection of a serial port mouse.
When starting a computer with the Windows 2000 operating system, it will try and auto-detect a serial port mouse. If
your computer is attached to a S7-200 multi-master network when the operating system starts, then it will incorrectly
report the S7-200 network traffic as a serial port mouse. In this state, random mouse movement and right clicks will
appear on the Windows 2000 desktop. You must disconnect the S7-200 network to stop the incorrect data
transmission. This Windows 2000 problem is known to exist on Windows 2000 versions SP1 and SP2 and is discussed
in Microsoft Knowledge Base article Q283063.
If you experience this problem, please try:
Disconnecting the S7-200 serial port connector before powering up or rebooting Windows 2000. After the boot
process is complete and you are logged in, then reconnect the computer to the S7-200 network.
If you do not use a serial mouse, then you can modify your boot.ini file to include the /NoSerialMouse switch option.
Use the Notepad text editor to modify [operating system] lines in the boot.ini file. The boot.ini file is located in the
root directory of the boot drive (typically C:\).
For example, if the boot.ini lists:
[operating system]
multi (0) disk (0) rdisk (0) partition (1) \WINNT="Microsoft Windows 2000 Professional" /fastdetect /noguiboot
Then add the /NoSerialMouse switch, as shown below:
multi (0) disk (0) rdisk (0) partition (1) \WINNT="Microsoft Windows 2000 Professional" /fastdetect /noguiboot
/NoSerialMouse
3.

Dell Notebook and Windows 2000 ACPI

Certain Dell Notebooks turn on the transmit line of COM port 1 while starting Windows 2000. If this occurs when
connected to a S7-200 multi-master network, then token circulation is stopped and the S7-200 network will no longer
function. This is a problem of the ACPI (Advanced Configuration and Power Interface) support of the machine/OS. If

you experience this kind of problem it is recommended that you purchase a CP5511 card for communications to the
S7-200 network or you can re-install Windows 2000.
If you already have Windows 2000 loaded, you can check if the ACPI is installed:
1.
2.
3.
4.

Select Start->Settings->Control Panel and double click on the item "System".

Choose the "Hardware" tab.
Click the button "Device Manager".
Expand the "Computer" tree node.

If you see an "ACPI" string in the computer description, then ACPI support is installed and you will have to
completely re-install Windows 2000 in order to be able to use the serial port.
To turn ACPI support off:
1. Insert Windows 2000 installation CD and follow the installation instructions.
2. During the startup of the installation you will see a message which prompts you to press F6 in order to install
additional SCSI/storage drivers. When you see this message you have to press F7, not F6. Please note: this option is
not documented.
3. Complete the installation process and then check the computer type. ACPI should no longer be present, and you
will be able to use your serial port for connecting to a S7-200 network.
4. CP5511 Card on Notebook PC
Internally, the CP5511 card is ISA based, and the new technology of Plug & Play does not work properly. STEP 7Micro/WIN and all SIMATIC products install a .inf file that contain the most common configurations for most PCs.
However, not all PCs are designed the same and therefore you may need to obtain a different .inf file from the S7-200
hotline. If you experience problems getting the CP5511 card to install or function properly, please call the Siemens S7200 hotline.
5. Windows 2000 Multi-Master Serial Port Communications
On lower performance computers, you may experience communication timeouts if you load the computer while
running STEP 7-Micro/WIN. For example, executing a print job from another application while running STEP 7Micro/WIN simutaneously may prompt you with communications timeout errors.
It is not recommended that you run other applications while issuing communication requests from within STEP 7Micro/WIN.
6. Installing CP Cards
You should always install STEP 7-Micro/WIN before inserting and installing any CP Card. STEP 7-Micro/WIN
contains the drivers that the cards need and therefore a CP card should be installed after STEP 7-Micro/WIN.
7.

Managing Applications Access to the Serial Port

If you use the STEP 7-Micro/WIN 32 Communications Setup or the PC/PG Interface under the PC's Control Panel to
set up the PC COM PORT parameters, certain conditions will cause the COM Port selection field to be shown with an
asterisk beside the COM Port number. This asterisk indicates that the user's PC setup has already assigned another
application to use the same COM Port. For example, if the Palm Pilot software is installed on the PC and you try to
install STEP 7-Micro/WIN, this asterisk will appear because Palm Pilot software typically loads each time the PC is
booted up. You must unload (not un-install) the other application to free up the COM Port so that STEP 7-Micro/WIN
can gain access to the port.
8. HP DeskJet Color Printers
If you are experiencing problems with a HP DeskJet color printer, or you are experiencing problems with other
printers, try downloading the newest available drivers from the printer manufacturer. Otherwise you can change the
printer driver to the Windows universal driver for your printer. For example, in the case of the DeskJet, the universal
driver is the 550c driver.
9.

Out of Date System Files

If STEP 7-Micro/WIN 32 exhibits strange behavior (for example, wide dialogs) or an application fault occurs while
using the Find/Replace/Goto functionality on a Windows 95 operating system, the most likely problem is out-of-date

system files. The Microsoft update for these files is located on the STEP 7-Micro/WIN 32 installation CD in the file
COM32UPD.exe. Run this file to update your system. If STEP 7-Micro/WIN 32 still exhibits the same behavior after
this, contact customer support.
10. PPI Multi-Master Communications
If you are experiencing problems using the SIEMENS PPI Multi-Master Configuration you may need to fix the port
settings on your computer.
Note: If you are using Windows NT and a PC/PPI cable, no other master can be present on the network. Therefore,
you cannot edit your port settings using the following method.
a) Right click My Computer on the Desktop and select Properties
b) Select the Device manager Tab (For a Windows 2000 OS, select the Hardware Tab and then click the Device
Manager Button)
c) Double click the Ports (COM & LPT)
d) Select the Communications Port (i.e. COM1) that you are currently using
e) On the Port Settings tab - click the "Advanced" button in bottom left
f) In the new window, set the Receive Buffer and the Transmit Buffer to the MINIMUM value.
g) Reboot your computer to set these new settings
11. Compatibility with Prior Version of STEP 7-Micro/WIN
Once STEP 7-Micro/WIN 32 V3.2x is installed, STEP 7-Micro/WIN 32 V2.x will not be able to communicate via the
PPI multiple master network option.
Programs downloaded to a PLC with STEP 7-Micro/WIN 32 V3.2x cannot be uploaded with STEP 7-Micro/WIN 32
V3.0x or earlier. To successfully upload these programs, it will be necessary to use STEP 7-Micro/WIN 32 V3.1 or
later.
12. TD200 Communication
A possible problem can occur during downloading or uploading a program using a CPU 215 or CPU 216 when an
older TD 200 (pre-v1.2) is polling the CPU. The current time-out error on the TD 200 is no longer appropriate for new
CPU models. To work around this error, temporarily disconnect the TD 200 from the network, download or upload the
program, and then reconnect the TD 200 to the network.
13. TC35 Cell Phone Modems
Certain Dell laptops used with a Siemens TC-35 modem, will not properly communicate. The problem is seen with
some Dell laptops that drive the transmit line high when the serial port is not in use. Because of this, the Siemens TC35 (and possibly other industry standard modems) resets causing initialization sequencing problems followed by
communication errors.
14. TC35 Cell Phone Modem Remote Programming
Remote modem programming of a Siemens TC-35 modem uses an &W AT-command. Early firmware versions of this
modem do not support this command. Programming of this modem will fail, if this command is not supported.
2.2

WIPEOUT.EXE

The WIPEOUT utility is a DOS-based application, which restores the PLC to factory defaults. This program is useful
if you have a PLC at an unknown address or baud rate and you cannot communicate to the PLC using STEP 7Micro/WIN 32. The WIPEOUT utility will delete the user program (OB1), the data block (DB1), and all configuration
information (SDB). The PLC will then be set at address 2 at 9600 baud. The WIPEOUT utility is not installed with
STEP 7-Micro/WIN 32. A copy of the utility is included on the STEP 7-Micro/WIN 32 installation CD. The utility
may be run from the CD or copied and run from the hard drive. To run the WIPEOUT utility, open a DOS Window
and type "WIPEOUT," and follow the directions.
2.3

National Languages

STEP 7-Micro/WIN 32 uses several Microsoft common dialog boxes. The text in these dialogs appear in the national
language of the operating system, regardless of the language you have chosen for STEP 7-Micro/WIN 32.
2.4

General Communications

Note: All of the following information is explained in detail in the S7-200 Programmable Controller System Manual.

1 Supports external modem using PPI connection

(PC COM port-RS232 cable-local modem-telephone/wireless connection-remote modem-PC/PPI cable-S7-200)
2 Advanced PPI protocol compared to multi-master PPI protocol:
Pro: The Advanced PPI setting establishes a more direct logical connection between programmer and CPU. Advanced
PPI protocol can improve communication, for complex networks, when several CPUs are using the NETR (Network
Read) and NETW (Network Write) instructions.
Con: Advanced PPI limits the number of available connections compared to multi-master PPI
3 MPI protocol does not support 9.6 Kbps. 19.2 Kbps is the lowest rate supported.

3 MPI protocol does not support 9.6 Kbps. 19.2 Kbps is the lowest rate supported.

1 Supports external modem using PPI connection

(PC COM port-RS232 cable-local modem-telephone/wireless connection-remote modem-PC/PPI cable-S7-200)
2 Advanced PPI protocol compared to multi-master PPI protocol:
Pro: The Advanced PPI setting establishes a more direct logical connection between programmer and CPU. Advanced
PPI protocol can improve communication, for complex networks, when several CPUs are using the NETR (Network
Read) and NETW (Network Write) instructions.
Con: CPUs 212 and 214 must be release 1.10 or later. Advanced PPI limits the number of available connections
compared to multi-master PPI
3 MPI protocol does not support 9.6 Kbps. 19.2 Kbps is the lowest rate supported.
2.4.1

Multi-Master Communications

Note: When using Multi-Master communications on networks with several masters (including TDs, or OPs), the
hardware takes several seconds to initialize onto the PLC network. If communication is attempted before this
initialization is complete, an error may occur. Retrying the last request should correct it.
Setting STEP 7-Micro/WIN 32 Network Addresses:
As a general rule, use the lower available addresses for masters and the higher available addresses for slaves. It is
preferable, but not required, to use consecutive addresses for the masters on a network. For example:
Network Components

Possible Addresses

STEP 7-Micro/WIN 32 0
TD 200
1
OP15
2
Several S7-200s 3, 4, and 5 You could leave these numbers free for additional masters and start the numbering of the
S7-200s at 16.
TD 200/MPI:
A possible problem can occur during downloading or uploading a program with a CPU 215 or CPU 216 when an older
TD 200 (pre-v1.2) is polling the CPU. The current time-out error on the TD 200 is no longer appropriate for new CPU
models. To workaround this error, temporarily disconnect the TD 200 from the network, download or upload the
program, and then reconnect the TD 200 to the network.
Master Mode Communications Error:

STEP 7-Micro/WIN 32 might report erroneous communications time-out errors when the PLC is in Master mode. For
example, using STEP 7-Micro/WIN 32 to put the CPU in STOP mode might return this time-out error even though the
CPU did in fact go to STOP mode.
2.4.2

PPI Communications: Using PPI Multi-Master Configuration

If you start another application that uses the same COM port as STEP 7-Micro/WIN 32 when Multi-Master is checked
on the PPI Network tab and STEP 7-Micro/WIN 32 is communicating through COM1 or COM2, neither application
will operate correctly. If this occurs, close both applications, then restart only one.
2.4.3

MPI Communications: Setting up the MPI Cards with STEP 7-Micro/WIN 32

In order to communicate using the MPI card, the STEP 7-Micro/WIN 32 MPI driver requires that the memory space
used by the card be reserved (excluded) by the system. This prevents the memory manager from allocating this area of
memory to another application. SIMATIC STEP 7 does not require this memory to be excluded and should operate
properly with the memory either included or excluded.
The memory space used by the MPI card is selected by using the switches on the card. The default address space on
the MPI card is 0xDC000-0xDC407 on a PC, which is the recommended address space. On a PG, the default is
0xCC000-0xCC407. The procedure for excluding this memory depends upon the memory manager in use.
Case 1: MPI Card on a PG or PC running Windows 95/98 and Windows Me
1.
In the CONFIG.SYS file, look for a line of code similar to the following that loads the
memory manager:
DEVICE=EMM386.EXE X=A000-BFFF I=C000-CCFF I=CD00-DFFF X=E000-EFFF FRAME=D000
2.
Change the I=C000-CCFF to X=C000-CCFF and save the file.
3. The end result should look as follows: DEVICE=EMM386.EXE X=A000-BFFF X=C000-CCFF I=CD00-DFFF
X=E000-EFFF FRAME=D000
Please note that this configuration example assumes that the MPI card is at address 0xCC00, which is the default for a
PG. If the settings are different, then the address range to be excluded should be changed to match the card.
MPI Cards for STEP 7-Micro/WIN 32 using Windows 95/98 and Windows Me
Case 1 CP5511, CP5611: These cards are Plug-and-Play; they are automatically detected and self-initializing.
Case 2 CP5411, MPI-ISA Card, MPI-ISA Card on Board: These cards are installed from the communications setup.
The address ranges and interrupt are detected by Windows and set up automatically.
MPI Cards for STEP 7-Micro/WIN 32 using Windows NT
Case 1 CP5511, CP5611: These cards are automatically detected and self-initializing.
Case 2 CP5411, MPI-ISA Card, MPI-ISA Card on Board: These cards are installed from the communications setup. It
is necessary to specify the resources (addresses space and interrupt) used by the card from the communications setup.
3

Using the Force Function

Warning!
When you force a value in your program, the operand is reset to that value with each scan of your program, regardless
of input/ output conditions or other program logic that would ordinarily have an effect on the operand value. Forcing
can cause your process to operate unpredictably, and unpredictable process operation can cause death or serious injury
to personnel, and/ or damage to equipment. The Force function is an aid for debugging your program; never force a
value to compensate for problems with your process equipment. Only qualified personnel should use the Force
function. Be sure that all personnel who have authority to maintain or debug your process are aware when program
values have been forced.
The following should be considered when using the Force function:
Any Forced values will remain Forced even when the PLC is in STOP mode.
The Force function overrides an output that has been configured to go to a specified value when the PLC transitions to
STOP mode.
If the PLC is power cycled, any Forced values will be reapplied when power is restored to the PLC.

For more information regarding the Force function, consult the S7-200 Programmable Controller System Manual.