show the entry list

STEP 7 -- Analyzing error messages -- Diagnosing errors 
In STEP 7 (TIA Portal), how do you format an MMC or MC and why does a message appear saying that the SDB 7 is not loaded? 
How do you use the "SIMATIC Diagnostics Tool" (SDT) to collect diagnostics and system data? 
Information about the topic of "Diagnosing errors" 
How can you clear the error message 257:5 in STEP 7? 
How can you clear the error message "Abnormal Program Termination"? 
What is the meaning of the error codes (xxxx:yyyy) in STEP 7? 
How do you clear message 256:26 "An OLE error has occurred"? 
How do Diagnostics and Remedy work in STEP 7 when an online connection with the CP5511 is not possible? 
What is the remedy for error message 13:76? 
Why does the area length error warning appear in STEP 7 V5.5 with indirect addressing or when using FC100 "SWR_START"? 
Why does the message "S7tgtopx.exe has caused an error and will be closed" appear? 
What is the meaning of the error codes (like W#16#8081) of the return value RET_VAL in STEP 7 V5.5? 

In STEP 7 (TIA Portal), how do you format an MMC or MC and why does a message appear saying that the SDB 7 is not loaded?Go to beginning
Part number:

Description
Micro memory cards (MMC) or memory cards (MC) are used in TIA Portal projects with an S7-300/S7-400 CPU. We describe the following topics in this entry.

  1. Formatting a Micro Memory Card or Memory Card with a USB Prommer
  2. Message: Cannot load SDB 7 for S7-300

Formatting a Micro Memory Card or Memory Card with a USB Prommer

Instructions
You must execute the following steps to format a micro memory card or memory card in TIA Portal using an external USB prommer.
 
No. Procedure
1 The prommer must be connected to the programming device by USB.
 
2 Check which interface is forwarded to STEP 7 (go to "Control Panel" of the Windows operating system and then "Parameterize Memory Card").


Fig. 01

The "External prommer" options must be enabled here (At the connection: USB).

3 Now it is possible to delete the MMC or MC with the menu (if everything has been set correctly).


Fig. 02

If the setting has not been made as in Fig. 1, you get the message shown below.


Fig. 03

4 Confirm the next dialog field with "Yes".


Fig. 04

5 Once the procedure has been completed successfully, the following lines are entered in the "General" tab of the inspector window.


Fig. 05

Table 01

Message: Cannot load SDB 7 for S7-300
Below are reasons why you get the messages indicating that block SDB 7 cannot be loaded or that the block/OS update is too big when downloading with STEP 7 V5.x or STEP 7 (TIA Portal).

  • No MMC. Slot an MMC that has sufficient capacity into the CPU.
  • MMC is defective. Replace the existing MMC with a new MMC.
  • CPU is defective and MMC is not recognized. You should consider this last possibility only if you have already replaced the MMC with a new one.

Creation environment
The screens in this FAQ response were created with STEP 7 (TIA Portal) V12.

Additional Keywords
13:4589

How do you use the "SIMATIC Diagnostics Tool" (SDT) to collect diagnostics and system data?Go to beginning
Part number:

Introduction
The SIMATIC Diagnostics Tool enables you to gather diagnostics and system information from your components.
The SIMATIC Diagnostics Tool acquires the information from a local computer or from multiple computers over a network.

Description
Scope of functions of the SIMATIC Diagnostics Tool:

  • Acquisition of diagnostics data.
  • Acquisition of system data.
  • Archiving of acquired information sorted according to computer in the ZIP format.
  • Configuration of the information to be acquired using the "Settings Manager".
    • Which diagnostics files?
    • Which system information?
    • From which computers is this information required?
  • Creation of a configuration file with the "Settings Manager".

Advantages of using the SIMATIC Diagnostics Tool

  • You do not have to install the tool.
  • You do not have to collect the data manually from each computer; a "click" is all that is needed.
  • The configuration files of the tool only have to be created once and can be used over again if the identical files have to be acquired at another point in time.
  • You can generate the configuration files offline and then forward them to the staff on site. This saves having to make any further settings in the customer plant.
  • The information from all the computers is available on one computer when the tool has completed its run.

Note
The second version of the SIMATIC Diagnostics Tool is available. Refer to the table below for operating system dependencies.

SIMATIC Diagnostics Tool Versions and Software Requirements
 
Operating
system
MS Windows
2000 Server
MS Windows
2003 Server
MS Windows
XP < SP3
MS Windows
XP SP3 incl.
.Net Framework >= 2.0
MS Windows
2008 Server
MS Windows 7
SDT_2013       X X X
SDT_2011 X X X X    
Table 01

Note on McAfee Application Control
When using McAfee Application Control, the participating systems must be in Update mode.
This can be run from the central McAfee Server (ePO).
For configurations without a central server, you must make changes on the participating systems. For this, please get in touch with Technical Support.

"SIMATIC Diagnostics Tool 2013"
 
Contents of the downloads Download
SIMATIC Diagnostics Tool 2013
Packed version of the SIMATIC Diagnostics Tool 2013
Download the "SDT2013_3.zip" file from this page to your system and unpack it in a folder of your choice, "D:\SDT", for example. Use this password for decoding: "12345678".

SDT2013_3.zip
( 1368 KB )
XML files
To ensure that the required diagnostics data is complete, the reference lists (diagsets.xml, locallall.xml and SCOUT+STARTER.xml) are made available immediately.

Download the current XML files (date: 2014-07) and replace the existing files in the subfolder ...\bin of the SIMATIC Diagnostics Tool.


diagsets.xml ( 41 KB )


localall.xml ( 41 KB )

Instructions
Here you will find detailed instructions for the following:
  • Local collection of diagnostics files.
  • Distributed collection of diagnostics files.
  • Collection of STARTER / SCOUT-relevant diagnostics files
  • Creating a memory dump at runtime.
 
UsingSDT.pdf
( 836 KB )
STARTER / SCOUT
Here you will find a predefined configuration file.
 
SCOUT_STARTER.xml  ( 10 KB )
Table 02

Instructions for local collection
 
No. Procedure
1 Start the SIMATIC Diagnostics Tool and click "Start Collecting".
Table 03

Instructions for distributed collection
 
No. Procedure
1 Download the "PSTools.zip" file from the Microsoft internet site
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
and unpack the PsExec.exe file in the subfolder "...\bin" of the SIMATIC Diagnostics Tool.

2

Start the SIMATIC Diagnostics Tool and configure as required.
Table 04

Instructions for creating User Dumps during runtime
 
No. Procedure
1 Download the "Procdump.zip" file from the Microsoft internet site:
http://technet.microsoft.com/en-us/sysinternals/dd996900
and unpack the "procdump.exe" file into the subfolder "...\bin" of the SIMATIC Diagnostics Tool.
Table 05

SDT_2011
 
Contents of the downloads Download
SIMATIC Diagnostics Tool 2011
Packed version of the SIMATIC Diagnostics Tool 2011
Download the "SDT2011_3.zip" file from this page to your Engineering Station and unpack it in a folder of your choice, "D:\SDT", for example. Use this password for decoding: "12345678".

SDT2011_3.zip ( 3952 KB )
Instructions for the SIMATIC Diagnostics Tool 2011
Instructions for the basic configuration of the SIMATIC Diagnostics Tool 2011

Basic_Config_SDT.pdf ( 282 KB )
XML files
Configuration files for local and remote stations
Download the "general-configs.zip" file from this page to your Engineering Station and unpack it in a folder of your choice, "D:\SDT", for example.

general-configs.zip ( 1 KB )
Table 06  

Instructions
 
No. Procedure
1 Download the "PSTools.zip" file from the Microsoft internet site
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
and unpack the PsExec.exe file in the subfolder "...\bin" of the SIMATIC Diagnostics Tool.
2 Download the "Userdump" tool from the Microsoft internet site
http://www.microsoft.com/downloads/details.aspx?FamilyID=E089CA41-6A87-40C8-BF69-28AC08570B7E
and start the self-extracting file. Retain the path and click "Unzip". You do not have to install this tool.

Note
In the case of 32-bit systems, you must copy the userdump.exe + dbghelp.dll files from the ...kktools\x86 folder into the ...\bin folder of the SIMATIC Diagnostics Tool.
In the case of 64-bit systems, you must copy the userdump.exe + dbghelp.dll files from the ...kktools\x64 folder into the ...\bin folder of the SIMATIC Diagnostics Tool.

3 Start the "SettingsManager.exe" in the "D:\SDT" folder. You use this tool to configure the basic settings of the SIMATIC Diagnostics Tool to acquire data from the local or other stations. For this you use the All_local.xml and All_remote.xml files from the "D:\SDT" folder.
4 Start the SIMATIC Diagnostics Tool (SimaticDiagnoseTool.exe) with the settings you made in step 3.
Table 07

Additional Keywords
44029135, Log files, Log file, Diagnostics data, Hotline request, WinCC, PCS 7, Analysis, Troubleshooting, Diagnostics file

Information about the topic of "Diagnosing errors"Go to beginning
Part number:

Instructions:
Information about "Diagnosing errors" is available in the following manuals and chapters / sections.
 
Manual

Edition

Chapter / Section Entry ID
Programming with STEP 7 V5.5 05/2010 21  Testing Using Program Status
23  Diagnostics
45531107
Working with STEP 7 V5.5 Getting Started 05/2010 07  Downloading and Debugging the Program 45531551
System Software for S7-300/400 System and Standard Functions 03/2006 01 to 35 1214574

How can you clear the error message 257:5 in STEP 7?Go to beginning
Part number:

Description  
The error message described above:

  • "257:5  One or more objects of a type cannot be displayed. ..."

is complemented by a second error text that refers to the server or also a file that cannot be found or recognized by STEP 7. The error message appears when you open the SIMATIC Manager, a block (FB, FC, OB or DB) or the hardware configuration. The following reasons might be the cause.

  • You are processing a STEP 7 project that has been created with one or more software options packages. Either these software options packages have been installed on your computer with an old version or not at all.
  • You are processing a project that has been installed with a higher version of STEP 7 and contains functions or modules that are not yet included in the previous version of STEP 7 you have installed.
  • You do not have enough storage space on your hard disk or your swap file (virtual main memory) is too small.
  • Your STEP 7 project or program sections from your project have been destroyed.
  • Your STEP 7 installation is defective or some of your SIMATIC software files are damaged.

Remedies are described in the table below.
 
No. Remedies for error message 257:5
1 Missing options packages
  1. Check which options packages are required for processing your project. A detailed description of the procedure is available in Entry ID: 18631373.
  2. Install the required options package and check compatibility between the options packages, your installed version of STEP 7 and the operating system. Information is available in Entry ID: 18734363*.
  3. Install the licenses and authorizations required for your options packages.

*If you have installed STEP 7, this list is also in the subdirectory "Start > SIMATIC > Information > English > STEP 7 Compatibility List".

2 Missing operating system update
Check the compatibility between your version of STEP 7 and the MS Windows operating system. You might have to install an update for your version of STEP 7. For example, you need STEP 7 V5.4 with at least SP4 for MS Windows XP Professional SP3. More information is available in our Entry ID: 8250891.
3 STEP 7 version conflict
STEP 7 projects are downwards compatible to previous versions. Projects created in version V5.4 can also be edited in version V5.3, for example. However, the project created in STEP 7 V5.4 must not contain any components and functions not supported by the previous version, like new CPU modules or new functions (such as access protection or SIMATIC Version Trail).
  • If a STEP 7 V5.4 project is to be processed, for example with STEP 7 V5.3, then you can only use module order numbers that are known in version V5.3 in the V5.4 project. It might be necessary to configure new modules with the "predecessor order number".
  • From STEP 7 V5.2 onwards, you will be able to load new modules via Hardware Support Packages (HSP). Information is available in our Entry IDs 17581199 and 22374877.

Note
Refer also to the information in the readme file in section 6.6 "Changing between the different versions of STEP 7", "New modules in old versions of STEP 7".

4 Insufficient memory
STEP 7 V5.4 requires between about 650 and 900 MB of free memory on your hard disk.

The Windows operating systems supported require additional memory on the hard disk (typically disk C:) for the swap file, depending on the memory expansion available. You should keep at least twice the size of the main memory free. (Example: with a main memory expansion of 512 MB you need another 1024 MB of free memory on the hard disk for the swap file after installing STEP 7). Depending on the project size, you might need a larger swap file when copying an entire project, for example (twice the project size in addition on the hard disk). If the memory for the swap file is too small, errors might occur (or the program might even crash). Other Windows applications (e.g. MS Word) running simultaneously with STEP 7 V5.4 also require additional hard disk space for the swap file.

More information on setting the virtual main memory in the Windows operating systems is available in our Entry ID: 20440472.

5 Defective STEP 7 project
It is possible to restore the project by reorganizing the project. Reorganizing compresses the project and the gaps resulting from deletions are removed from the project. This method reduces the project's memory requirement.
  1. Open the "File > Save as..." dialog.
  2. Activate the option "With Reorganization (slow)".
  3. Change the name of your project and confirm with OK.

If the remedy described does not help, create a new STEP 7 project via "File > New..." and copy the blocks from the old project into the new project. Also transfer the hardware configuration from the old project into the new project with the functions "Station > Export..." and "Station > Import...".

6 Defective installation of STEP 7
The message described above is also displayed when some of the files of the SIMATIC STEP 7 software are damaged or if the installation of the STEP 7 software has been aborted. In most cases, the repair function on the STEP 7 CD can be used to restore the software status on your PC.

If it is not possible to restore the software status on your PC using the repair function on the STEP 7 CD or by reinstalling STEP 7, we recommend completely uninstalling STEP 7 and also deleting the entries in the Registry. For this we recommend consulting our Entry ID: 189025. Then you can reinstall STEP 7.

How can you clear the error message "Abnormal Program Termination"?Go to beginning
Part number:

Instructions:
The error message described above:

    "Abnormal Program Termination"

is complemented by a second message text that refers to a server, driver and/or also a file. The table below describes a number of examples and remedies for the Runtime error that might occur in combination with the message described above and which can be cleared.
 
No. Procedure
1 When installation of the SIMATIC STEP 7 software is aborted with the error message "Abnormal Program Termination" and the message:
  • Runtime Error!
    Program: D:\Siemens\STEP7\s7bin\S7ALIBXX.EXE,

the reasons are the following:

  • You do not have access rights to the TEMP directory or
  • The TEMP directory is not available.

Remedy:
Set up the TEMP directory in the system root directory (e.g. directly under C:\) so that every user on this computer has full access rights to that directory.

Note:
For the installation of STEP 7 you need local administrator rights.

2 If when you open the hardware catalog or when you save and compile the hardware configuration the error message "Abnormal Program Termination" is displayed together with the message:
  • Runtime Error!
    Program: C:\Program Files\Siemens\STEP7\s7bin\S7HWCNFX.EXE,

then the reason for the behavior described might be the incorporation or installation of a third-party GSD file (e.g. syntax error in the third-party GSD file).

Remedy:
Close the hardware catalog and terminate STEP 7. Delete in the Explorer under

  •  <Drive>:\SIEMENS\STEP7\S7DATA\GSD

all files with the ending ".xml" (example as in Fig. 01). Then when you restart STEP 7 and open the hardware configuration, you can open the hardware catalog again.


Fig. 01

3 If the remedies described above do not help and the error message "Abnormal Program Termination" is displayed again, then install STEP 7 again.
  • Insert the STEP 7 CD into the CD-ROM drive and start the Setup by double-clicking on the "setup.exe" file. 
  • In the installation menu that opens you select the "Repair" function and then follow the installation program instructions step by step. 
  • The program guides you step by step through the installation process. Then you must reboot your PC.

This method should also be selected when the error message described above keeps being displayed sporadically.

Keywords:
Setup, Program termination

What is the meaning of the error codes (xxxx:yyyy) in STEP 7?Go to beginning
Part number:

Description
In some cases in STEP 7 you are presented with warnings, notes and error messages with an error code (xxxx:yyyy).
The following table shows you the most important error codes, their meanings and possible remedies.

STEP7_ErrorCode_e.pdf ( 107 KB )  

Note
More information is available in the STEP 7 Online Help. When the error code is displayed, click the "Help" button for information about how to remedy the error indicated by the error code. If you need more information about an error code, "13:4468", for example, click the "Index" button. In the "Help Topics: Help on Messages" dialog below you are presented with a list of all the codes in group "13:" . To find a remedy for the error indicated by error code "13:121", for example, mark the code "121" in the list and click "Display".

Additional Keywords
D280

How do you clear message 256:26 "An OLE error has occurred"?Go to beginning
Part number:

Instructions:
The message "An OLE error has occurred" can be displayed, for example, when opening blocks or starting functions STEP 7 or the options packages if the start of a Windows application has failed.

OLE (Object Link Embedding) is a central Windows mechanism that is used internally when starting applications.

This error can have very different causes, e.g. incorrect installation or incorrect registry entries or even corrupt files in the Windows system.

The table below describes a number of causes and remedies for these messages.
 
No. Causes and remedies for internal OLE errors
1 There is not enough space on the hard disk. The database cannot be started.

Remedy:
Create free space on the hard disk (>100MB) and set the virtual main memory to user-defined (information on this is available in the STEP 7 readme file). More information on setting the virtual memory is available in our Entry:

  • "How do you make the settings for the virtual memory in MS Windows XP/2000/ME/NT/9x?" Entry ID: 20440472.
2 Check whether the internal STEP 7 database was started when the PC was booted and also the function Start/stop server in the SIMATIC workstation. For this, in Windows you open the dialog "Start > SIMATIC > STEP 7 > Configure SIMATIC workstation". In order to be able to start the internal STEP 7 database, the following entries must be available and executed in the autoexec.bat in Win95/98:
  • SET PATH=.......,C:\SIEMENS\COMMON\SQLANY";PATH%;........
  • SET SQLANY=C:\SIEMENS\common\Sqlany
  • SET S7TMP=C:\SIEMENS\STEP7\S7TMP
3 Incorrect DLL in Windows/System and/or incorrect registry entries:
In the Explorer you start the program editor "c:\siemens\step7\ska\s7kafapx.exe" and evaluate the error message. If the following message appears:
  • "The file S7HRVERX.DLL is linked with the missing export S7OTBLDX.DLL: s7_set_password",

then please check whether the file "S7OTBLDX.DLL" is in the Windows system directory. When using STEP 7 V4.02, this file must be deleted from the Windows system directory. If the following message is displayed:

  • "The file S7KAFAPX is linked with the missing export OT5050R.DLL:4224",

then please check whether the file "OT5050R 2x " is on the computer. Change the names of all the files except those in the S7BIN directory.

4 WIN 95a or b: when WINDOWS was installed, the OLE was installed incorrectly .

Remedy:
Delete the Windows directory and then reinstall WINDOWS.

5 The message appears when opening a VAT.
The "S7USS" directory is missing in the "SIEMENS\STEP7" directory.

Remedy:
Reinstall STEP 7.

6 S7 project is defective and cannot be cleared by "Save as... -> With reorganization".
If it is not possible to copy the STEP 7 project with "Save as..." together with the "With reorganization (slow)", then first check whether there is enough space on the hard disk or drive on which you want to save the STEP 7 project. The reason might also be a missing options package or defective data of an object, for example.

Remedy: 
Create a new STEP 7 project and insert an S7-300 or S7-400 station or an S7 program in your project. Copy the blocks from the old STEP 7 project into the newly created STEP 7 project.

7 If you open blocks from the SIMATIC Manager or you open the same blocks via the dialog "LAD/FBD/STL - Program S7 blocks", the following message is displayed:
  • "Cannot find the required DLL file S7AAAPIX.dll".

Remedy:
Check your computer for virus attacks, in particular for the virus type "INTERNET WORM". If the computer has no viruses, then try deactivating the virus scanner and other applications.

8 If you are still using STEP 7 V5.1 and when you open a block, you get an OLE error even though the paths are correctly set in the "autoexec.bat", then you cannot open the HW Config and the metafiles are compiled each time you start the SIMATIC Manager.

Cause:
An incorrect system date is set.
Remedy:
Correct the system date and restart the SIMATIC Manager.

9 Incorrect or inconsistent installation of STEP 7
Information on this is available in our entry: Tips and tricks for installing and upgrading software in STEP 7" Entry ID: 23568401.
10 A domain user has been added in the Properties of the DCOM configuration.
Start > Run > "dcomcnfg" was called. In the tab: Default Properties > Field: Default Authentication Level a domain user was added via the field: "Edit/change default".

Remedy:
Remove this new domain user and restart the computer. You delete the new domain user in the same field in which you inserted it. Proceed as described above to the "Edit/change default" and mark the user concerned. Delete the access authorization of the user via the "Remove" field. Then reboot your computer to activate the new setting.

11 Another cause for the error message 256:26 could be that in the DCOM configuration, in the "Default Properties" tab, the entry in "Default Impersonation Level:" has been changed from "Identify" to "Anonymous". This conversion might have been done automatically by third-party software. The connection with the internal OLE error has only occurred until now in Microsoft Windows XP.
  1. In Windows you open the dialog "Component Service" via "Start > Run... > Input: dcomcnfg" and open the folder "Component Service".
  2. Right-click the My Computer icon and select "Properties" in the pop-up menu that opens.
  3. In the "Default Properties" tab, change the entry in "Default Impersonation Level:" from "Anonymous" to "Identify".


Fig. 01

Keywords:
Error message, Installation problem

How do Diagnostics and Remedy work in STEP 7 when an online connection with the CP5511 is not possible?Go to beginning
Part number:

Instructions:
Using this diagnostics function in the PG/PC interface you can check whether your communications module is ready for operation. If the CP5511 is ready for operation, the module's bus parameters and version data are displayed. You get to the PG/PC interface mask in the SIMATIC Manager via the menu item "Tools > Set PG/PC Interface".


Fig. 01

Then please click on the "Diagnostics..." button to open the "SIMATIC NET diagnostics" mask.


Fig. 02

Click on the "Test" button to check the operating status. If the module is not ready for operation, an error message is displayed with error number and error text. The table below describes the error messages and remedies that are possible.
 
No. Procedure
1 0x0300 module not found:
  • Check whether the CP5511 is installed/slotted correctly.
  • Check the interrupt and address assignments. Information on the further procedure is also available in the STEP 7 Online Help under "Set PG/PC Interface", in the paragraph entitled: "Check the interrupt and address assignments". More information is also available in the STEP 7 readme file ("Start > SIMATIC > Product notes"), section 4.4.1 under "Integrated MPI on-board and the MPI PC module -> Set interrupt and address".
2 0x0312 incorrect configuration parameters:

Uninstall the CP5511 and then reinstall it. For this you click on the "Select..." button in the Set PG/PC Interface dialog (Fig. 01). Mark the CP5511 with the cursor in the right window (Fig. 03) and then click on the "Uninstall" button. Restart STEP 7 and then in the left window you mark the CP5511 and click on the "Install" button. For this activity you must have administrator rights on your PC (see STEP 7 - readme file, section: 3.1).


Fig. 03

If this first recommendation does not help, if you are using STEP 7 up to version V5.2 SPx, we recommend completely uninstalling STEP 7 (including the options packages) as described in the FAQ "Complete uninstallation of STEP 7" in Entry ID 189025 in the Internet. Then reinstall your SIMATIC software.

3 0x0313 Baud rate doesn't match the network or incorrect interrupt:
  • Check the transmission rate (baud rate) in the PG/PC interface and in the hardware configuration. The baud rate must not be greater than the baud rate supported by the slowest node. The PROFIBUS addresses configured in the hardware configuration must match the addresses of the system configuration.
  • Check the interrupt and address assignments. Information on the further procedure is available in the STEP 7 Online Help under "Set PG/PC Interface", in the paragraph entitled: "Check the interrupt and address assignments" (Index: Check interrupt assignment). More information is also available in the STEP 7 readme file, section 4.4.1 (Integrated MPI on-board and the MPI PC module -> Set interrupt and address).
4 0x0316 Hardware resource already occupied:
  • If you get this error message after installing the CP5511 in "Set PG/PC Interface", proceed as described in Entry ID: 9853739 .
5 0x031a Cannot find active PB/MPI network:

Activate the function "PG/PC is the only master on the bus" in the Properties dialog of the PG/PC interface (see Fig. 04). In doing so you deactivate an additional function that protects against bus errors. You get to this mask by clicking on the "Properties" button - see Fig. 01. The requirement is that the interface used is set to: "CP5511(MPI)".


Fig. 04

If the first remedy doesn't help, in the PG/PC interface you should set the parameters of the interface used to "CP5511(Auto)" - automatic recognition of the bus parameters. You then parameterize the bus parameters via the "Properties" button (Fig. 05). More information on this is available in the Online Help (F1 key).


Fig. 05

6 0x0318 Interrupt occupied:
  • This message occurs in most cases in Windows NT. In your computer's BIOS, change the "PnP" setting to "No". You get to your computer's BIOS by restarting your PC and pressing the F2 key.
  • If this message occurs when using the CP5511 in Windows XP SP2, then disable IRQ Sharing. Refer to the Microsoft Support and Help website for how to disable IRQ Sharing. 
    http://support.microsoft.com/kb/279256
7 0x031b Synchronization error:
  • Check the bus parameters on the bus. They must match the bus parameters configured in the hardware configuration.
  • Check the installation of the bus cable.
8 0x031c AMPRO2 system error:
  • Activate the function "PG/PC is the only master on the bus" in the Properties dialog of the PG/PC interface (see Fig. 04).
  • Where applicable, check whether all the terminators are switched correctly in the PROFIBUS network.
  • It is also possible that not all the STEP 7 are installed or some have been deleted, or that a wrong driver is installed. In this case we recommend sending the CITAMIS.str file to Customer Support for inspection.
  • Another possible cause would be defective hardware.
9 0x0320 DLL/VXD not found as file:
If the 0x0320 message appears indicating a file with the extension "dll" or "vxd" (e.g. <file_name>.dll), we recommend the following remedy.
  • On your PC, find the file specified (<file_name>.dll or <file_name>.vxd) in the Windows Explorer via "Options > Search > Files/Folders". Either the file is not on your computer or you'll find it twice. If the file specified by the system is not available, we recommend installing the driver again. But if this file is found twice in the Explorer, you must rename the file in the Windows system folder and then restart Windows.
  • The references to this file are missing in the Registry. It is not possible to access the parameters required from the Registry. You might not have the access authorization required or the system database is damaged.
  • The drivers don't match the operating system.

More information is available in the Diagnostics function (Fig. 02) and in the Online Help (F1 key) under the keyword "Error message".

Notes on utilization with CP5511:
The more recent notebooks have card bus interfaces with 32 bits, which no longer support CP5511 (only for 16 bits). You must use the CP5512 (for 32 bits). Please also refer to the information in the "Readme" file:

  • You cannot operate the CP5511 in notebooks that are equipped with a PCMCIA controller of the Omega Bridge II or TI1130 type.
  • Apart from that, the CPU5511 (Advanced Configuration and Power Interfaces) not complete.
  • The CP5511 is not supported in MS Windows Server 2003 and MS Windows Vista.

We also recommend reading the information in our FAQs that are available in the following Entry IDs in the Internet:

  • Entry ID: 12259435 Check list for using a CP5511.
  • Entry ID: 2331034 CP5511 under Windows 98

  • Entry ID: 856884 Installation of CP5511 under Windows 98 with conflict

  • Entry ID: 2304046 CP5511 under Windows NT

  • Entry ID: 9853739 CP5511 is not addressed correctly in Windows 2000

  • Entry ID: 6721667 Blue screen when setting up an Online connection CP5511 in Windows 2000 + SP1

  • Entry ID: 382155 Installation instructions for CP5511 in conjunction with COM PROFIBUS.

Keywords:
Network diagnostics

What is the remedy for error message 13:76?Go to beginning
Part number:

Instructions:
The error message 13:76, which appears during saving and compiling in the HW Config, is most commonly due to inconsistency in the hardware configuration. The cause of the error message can be analyzed via the menu command "Station > Check Consistency". Other possible causes for the error message:

  1. Missing or write-protected folders "...\Siemens\Step7\S7tmp" or "...Siemens\SIMATIC_NCM\S7tmp".
  2. No authorization or license for an options package, as a result of which the SDBs cannot be created for a particular module.
  3. An operator panel has been inserted in the HW Config but not linked to any communication partner.
  4. The STEP 7 environment variable is either not set at all or not set correctly.
  5. Some of the STEP 7 software files are damaged.
  6. Incompatible software version.
The table below contains some remedies for situations where the above error message appears, despite consistency in the hardware configuration:
 
No. Remedies for error message 13:76:
1 Check whether the folders "...\Siemens\Step7\S7tmp" or "...Siemens\SIMATIC_NCM\S7tmp" exist and are not write-protected. If necessary, create the necessary folder.


Fig. 01

2 Mark the name of the project in the SIMATIC Manager and right-click it. Open "Properties..." in the pop-up menu which then appears and select the "Required software packages" tab. The software option packages, which are required for editing your current STEP 7 project, are displayed.


Fig. 02

If you haven't already done so, install the requisite authorizations and licenses.

3 Check whether the the operator panel was configured in ProTool prior to compilation in the HW Config. Otherwise the message below appears during saving and compilation
  • "(20) Error generating the system data. Do you wish to continue?".

This involves specifying the address of the operator panel in the ProTool configuration and assigning parameters to the connection to the communication partner. You can then restore the link to the CPU in the hardware configuration, enabling you to save and compile again without encountering errors.

Note:
Please bear in mind that a panel only has to be configured in the HW Config if you wish to use the DP direct keys. In this procedure, the keys have a direct influence on a bit in the controller's I/O area. You can find further information about the configuration of the DP direct keys in the user manual

  • "Communication for Windows-based Systems, Part 1",
    Section 6.5 "Configuration of the DP Direct Keys for the Operator Panel".
    ID: 1405528.
4 Check whether the environment variable is set in the Control Panel. Otherwise, the error message
  • "(20) Error generating the system data. Do you wish to continue?" also appears here.

To do this, open the "System" properties in the Control Panel and select the "Advanced" tab. Click "Environment Variables" and check whether the variable

  • S7TMP=C:\SIEMENS\STEP7\S7TMP

is set under "System variables". You can edit the environment variables using the "New", "Edit" and "Delete" buttons.


Fig. 03

5 Another cause of the behavior described above could be that some files of the SIMATIC STEP 7 software are damaged or that installation of the STEP 7 software has been interrupted. In most cases, the repair function on the STEP 7 CD can be used to restore the software version on your PC.
6 Incompatible software version
You are editing your STEP 7 project with an options package version which is incompatible with the STEP 7 software currently installed. Check the compatibility list to determine whether the options software which you have installed (e.g. Drive ES) is compatible with the STEP 7 software which you have installed and with the operating system. You can find which version of the SIMATIC software you have installed using the command "Help > Info > Display" in the SIMATIC Manager. You can also access the compatibility list on the Internet in Entry ID 18734363 ("Which SIMATIC software packages are compatible with which Microsoft Windows operating system and with STEP 7 V5.5?").

Install the version of the software which is required for your options package. Following installation, the error message described above, which appears during saving and compilation, should have cleared.

Note:
If there are a number of users working on a project (multi-user mode), the same version of the software must be installed for every PC on which the project is being loaded and edited.

Why does the area length error warning appear in STEP 7 V5.5 with indirect addressing or when using FC100 "SWR_START"?Go to beginning
Part number:

Description
The area length error appears if references are made to addresses that do not exist in the STEP 7 program or when parameterizing the block call. The Online Help in STEP 7 gives two reasons for this:

  • The value addressed by the access address is outside or not entirely inside the permissible address area (CPU-specific size).
  • Due to an incorrect address calculation the addressed value is >65535. In the case of indirect addressing, an address value of greater than 65535 might occur through incorrect calculation. This value can no longer be entered correctly in the detail information of the event. Then for S7-300 a 0 is entered and displayed as access address and the calculated value module 65535 for S7-400.

Example 1 (Indirect Addressing)
You have programmed a function block or function with indirect addressing that reads data from a data block (DB20, for example), processes the data and then writes the data to a data block (DB23, for example). If now, when you call the block with the parameterization of the ANY pointer, the address areas of the data blocks called are exceeded, there is an "Area length error when reading" and / or an "Area length error when writing" if the address area of DB20 or DB23 in the example described above is less than the byte length of the ANY pointer parameterized.

Fig. 01 shows the example here of incorrect programming.


Fig. 01

The ANY pointer "P#DB23.DBX0.0 BYTE 30" on the "PointerOutput" parameter of the called function block FB10 points to the addresses DB23.DBX0.0 to DB23.DBX29.7, because the length of the ANY pointer is 30 bytes (repeat factor). The repeat factor identifies the volume of the data type identified for transfer by the parameter type ANY. Here there is an "Area length error when writing", because the DB23 now only has a defined address area of 10 bytes (DB23.DBX0.0 to DB23.DBX9.7).

Remedy

  1. Change the access address so that the addressed value lies entirely in the address area permitted in each case.
  2. Check the defined address area. According to the example above, either the length of the ANY pointer must be reduced by 20 bytes or the length of data block DB23 must be defined as 30 bytes (ARRAY[1..30]) or more.

Example 2 (FC100 "SWR_START")
With the two parameters "DB_A_B_NO_LEN" and "DB_B_A_NO_LEN" of the FC100 "SWR_START" from the software redundancy you enter the number of data bytes used in the data blocks ("DB_A_B_NO" and "DB_B_A_NO"). The number must be equal to or greater than 4 bytes. If, for example, you specify only 2 bytes, this might lead to the cycle time being exceeded by read and write errors. The CPU switches to STOP mode and you get the messages below displayed in the diagnostics buffer:

  • Area length error when reading
  • Area length error when writing

More information about parameterizing FC100 "SWR_START" is available in the manual "Software Redundancy for SIMATIC S7", under "Programmable Logic Controllers S7-300 Module Data" in Entry ID: 1137637.

Why does the message "S7tgtopx.exe has caused an error and will be closed" appear?Go to beginning
Part number:

Description:
Upon appearance of the message described above, the SIMATIC Manager closes and STEP 7 terminates. The table below describes the causes and remedies for this.
 
No. Causes and remedies for the error message "S7tgtopx.exe has caused an error and will be closed"
1 Destroyed STEP 7 project or destroyed STEP 7 blocks
If the error message described above appears upon opening, closing or saving of FBs, FCs, OBs and DBs, then probably the STEP 7 project or part of it has been destroyed. It is possible to restore the project by saving the project under a different name. In the SIMATIC Manager you open the dialog "File > Save as..." and activate the option "With reorganization (slow)". Change the name and acknowledge with OK.


Fig. 01

If the remedy described does not help, create a new STEP 7 project via "File > New..." and copy the blocks from the old project into the new project. Also transfer the hardware configuration from the old project into the new project with the functions "Station > Export..." and "Station > Import...".

2

Incorrectly set system time:
If the system time in the Control Panel was not set to the actual date prior to the installation of the STEP 7 software, but had been set to a date in the future instead, and the installation was performed with the system set to this date, the following error messages may appear when you exit the hardware configuration or close the SIMATIC Manager:

  • "The instruction in ... refers to the memory in 0x00000014. The read action could not be performed on the memory".
    Click OK to close the program".
  • "This application will be closed due to an invalid procedure"
  • "S7tgtopx causes an error through an invalid side in module xxxx".

As the system date is set incorrectly, some files are incorrectly time-stamped, triggering the above error message. Open the "Date and Time" dialog box in the Control Panel for your operating system and set the correct date and time in the "Date & Time" tab using the scroll functions.


Fig. 02

Then click the "Apply" button, followed by "OK" to confirm.

3 Incompatibility with operating systems, SIMATIC software packages and Internet Explorer
Check the compatibility of one or more of the SIMATIC software products installed with your current version of STEP 7 and your operating system. Information on compatibility of STEP 7 with the operating systems, SIMATIC software packages and Internet Explorer is available in the following entries:
  • "Which version of STEP 7 is compatible with which version of Microsoft Windows operating system?", Entry ID: 8250891.
  • "Which SIMATIC software packages are compatible with which Microsoft Windows operating system and with STEP 7 V5.5?, Entry ID: 18734363.
  • "Which version of STEP 7 is compatible with which Internet Explorer?", Entry ID: 24254820.
4 Insufficient memory
Check the space on the hard disk and the settings of the virtual main memory. STEP 7 V5.5 requires between about 650 and 900 MB of free memory on your hard disk. Information on setting the virtual memory is available in our Entry:
  • "How do you make the settings for the virtual memory in MS Windows XP/2000/ME/NT/9x?", Entry ID: 20440472
5 Message: "Internal OLE error 256:26"
If the message "Internal OLE error" with the number 256:26 also appears when you open the SIMATIC Manager or a STEP 7 block, we recommend you consult our entry:
  • "How do you clear message 256:26 "An OLE error has occurred"?", Entry ID: 10208766.
6 Defective installation of STEP 7
The message described above is also displayed when some of the files of the SIMATIC STEP 7 software are damaged or if the installation of the STEP 7 software has been aborted. In most cases, the repair function on the STEP 7 CD can be used to restore the software status on your PC.

If it is not possible to restore the software status on your PC using the repair function on the STEP 7 CD or by reinstalling STEP 7, we recommend completely uninstalling STEP 7 and also deleting the entries in the Registry. For this we recommend consulting our entry:

  • "How do you uninstall STEP 7 completely, including all the software packages?", Entry ID: 189025.

Then you can reinstall STEP 7.

Keywords:
System message, Access violation

What is the meaning of the error codes (like W#16#8081) of the return value RET_VAL in STEP 7 V5.5?Go to beginning
Part number:

Configuration Notes
The general error codes are described in detail in the manual for the system software of the S7-300/400 system and standard functions. You can tell from the return value whether you are dealing with a general or an SFC-specific error: RET_VAL = W#16#8xYZ.
 
Code General error information for the RET_VAL = W#16#8xYZ:
8 The "8" indicates that an error has occurred.
x General and specific error information
  • if x = 0, then it is an SFC-specific error code
  • if x > 0, then it is a general error code
    x in this case is the number of the SFC parameter that caused the error.
Y,Z Event number or error class and individual errors
  • Number of the error (if SFC-specific)
  • Number of the event (if general error).

Examples
The return value W#16#8081 is a SFC-specific error code.
The return value W#16#823A is a general error code; the error was caused by parameter no. 2.

Counting direction for SFC parameters
With STL: from top to bottom
With LAD and FBD: from top left to bottom left and from top right to bottom right.

General and specific error codes
The table below explains the general and specific error codes of a return value. The error code is displayed in hexadecimal format. The letter x in the code numbers is just a placeholder for the number of the system function parameter that caused the error.

Error information
 
Error code
(hexadecimal)
W#16#...
Explanation
8x7F Internal error
This error code indicates an internal error in parameter x. The error has not been caused by the user and cannot be cleared by the user.
8x22 Range length error when reading a parameter.
8x23 Range length error when writing a parameter.
This error code indicates that the parameter x is completely or partly outside the address area or that the length of a bit field of an ANY parameter is not divisible by 8.
8x24 Area error when reading a parameter.
8x25 Area error when writing a parameter.
This error code indicates that the parameter x is in an area that is not permissible for the system function. The description of the function in each case specifies the areas that are not permissible for the function.
8x26 The parameter includes a time cell number that is too high.
The error code indicates that the time cell specified by the parameter x is not available.
8x27 The parameter includes a counter cell number that is too high (number error of the counter).
The error code indicates that the counter cell specified by the parameter x is not available.
8x28 Alignment error when reading a parameter.
8x29 Alignment error when writing a parameter.
This error code indicates that the reference to the parameter x is an operand whose bit address is not equal to 0.
8x30 The parameter is in a write-protected global data block.
8x31 The parameter is in a write-protected instance DB.
This error code indicates that the parameter x is in a write-protected data block. If the data block is opened by the system function itself, the system function always returns the value W#16#8x30.
8x32 The parameter includes a DB number that is too high (number error of the DB).
8x34 The parameter includes an FC number that is too high (number error of the FC).
8x35 The parameter includes an FB number that is too high (number error of the FB).
This error code indicates that the parameter x includes a block number that is higher than the maximum permissible block number.
8x3A The parameter includes the number of a DB that is not loaded.
8x3C The parameter includes the number of an FC that is not loaded.
8x3E The parameter includes the number of an FB that is not loaded.
8x42 An access error has occurred as the system wanted to read out a parameter from the I/O area of the inputs.
8x43 An access error has occurred as the system wanted to write a parameter to the I/O area of the outputs.
8x44 Error at the nth (n > 1) read access after the occurrence of an error.
8x45 Error at the nth (n > 1) write access after the occurrence of an error.
This error code indicates that access to the required parameters is denied.
8304 The error code indicates connection problems between WinCC and the S7 controller. As a result, for example, the picture currently in WinCC Runtime may no longer be refreshed. More information about the remedy is available in Entry ID: 22558461.
80C0 The error code W#16#80C0 is output if you attempt to transfer a DB or area of a DB from the CPU's main memory to the same DB or area of the DB in the load memory. This indicates that the target is currently being processed by another system function or communication function.
80C3 If, for example, you attempt to create more than three data blocks at the same time with SFC82 "CREA_DBL". The block can only be used again when the "BUSY" output shows a value of 0. In order to restore resources, you should analyze the block's "BUSY" output. Once the "BUSY" output has been reset, the "REQ" input must also be canceled to free the SFC call and the resources assigned to it again.  This procedure also applies to the functions SFC 83 "READ_DBL" and SFC 84 "WRIT_DBL".
80C4 This error message is issued during communication with IO modules (like the FM 351) if the job could not be executed. The reason for this behavior is that the communication is overloaded, in particular in combination with fast CPU modules and the associated fast OB1 cycles. You can also tell from the status of the BR bit whether an error has occurred.

Remedy
Reduce the frequency of the job execution by reducing the cycle, for example.

More information is available in our manual:

  • "System software for S7-300/400 system and standard functions" in Entry ID: 1214574.

Addition Keywords
Error evaluation

 Entry ID:22820577   Date:2014-07-31 
I regard this article....as helpfulas not helpful                                 






























related links
System Software for S7-300/400 Sy ...
Why can projects, blocks or the H ...
System Software for S7-300/400 Sy ...
MOBY FC 55, Technical Description
STEP 7 Professional V11.0 SP1
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Themen
Help
Online Help
Guided Tour