Defective internal system error - Исправление ошибок и поиск оптимальных решений проблем

Hi, i’ve got something funny and disturbing… I’ve made a Sivacon switchgear PLC project, used in many PLCs across 2 years.

To make a new project i simply do Save As,change the name, change HW devices, replace HMI functions according to devices used and… rest remains the same.

After last time, doing it — downloading project to PLC Sim — causes it to flash all the leds and diagnose buffer outputs:

Event 1 of 10: Event ID 16# 4550
DEFECTIVE: internal system error
No relevance for user (Z1): 201e
No relevance for user (Z2): 01f4 (Z3): 0060
Previous operating mode: RUN
Requested operating mode: DEFECTIVE
Internal error, Incoming event
09:11:40.609 PM 10/12/2015
(Coding: 16# 4550 FF8D C050 201E 01F4 0060)

Memory clearing and powering off plcsim doesn’t do anything, it needs to be closed and started again.

Disabling functions that access PIW/PQW doesn’t help FB3-FB7.

Still — i’m able to run original project in PLCSim with no problem.

Removing networked devices from hw doesn’t solve the issue.

Hardware used between project differs ( Simocode and pDrive drives, ABB drives,etc ) but was used in other projects and is confirmed as working.

Can anyone tell me, what have i done to create such a PLC Sim fault ?

I don’t have real CPU to test it, but this seems really strange to me and i don’t know if it will crash real plc.

PLCSim V5.4 + SP6
Step7 V5.5 + SP4
PLC 317-2DP FW3.3 — 6ES7317-2AK14-0AB0.

I’d be grateful if You can help me track down the issue or just download it to real plc as I am unable to test it at the moment.

As the project exceeds forum’s limit, i’m posting it to dropbox (1,6 MB) — You don’t need to log in.

https://www.dropbox.com/sh/qpmzqdal0…-GafLJ7Ea?dl=0

Thanks!

Источник

Siemens S7 Error Codes, error number, error description and error cause.

Error number:	Text:	Cause:	Remedy:
34:178	Block call invalid because interface was changed in the meantime.	With Step7 V5.0 the instance DB of the DB type is entered in the symbol list for an FB call. This is no longer permitted with Step7 V5.0. In this case the “Update Call” function doesn’t work.	Enter the instance DB of the FB type in the symbol list.
34:4321	Error in column 1, distribute the program in little blocks.
34:4355	F Ze %2!06d! Sp %3!03d!: No PLC type description found for called or addressed block %4.	The block called is not available.	The block is to be compiled before the call.
			In the case of SFB/SFC calls, please copy into your offline database with the SIMATIC Manager (block container).
			If the SFB/SFC is not available on the CPU addressed, then it should not be called!
34:4461	The block %4 that was called/used is protected or created by S7-GRAPH and cannot be generated.	You are trying to generate a KNOW_HOW_PROTECT block into an STL source.	The block named is protected and cannot be generated into an STL source.
34:4469	The declaration range of your formal parameter does not match the declaration range of the actual parameter, for example, no OUTPUT paramater from the actual end can be assigned to an INPUT parameter from the formal end.	It is not allowed, that an OUT variable of the calling function block is parameterized with the IN variable of the function block called.	We recommend first saving the data temporarily on a static variable. In a further network this static variable is parameterized with the IN variable of the FB called. The output variable of the higher-level block, the static variable and the input variable of the lower-level block must be of the same data type.
34:4485		The parameter assignments can be specified in any order in the ASCII source. The comments, however, are stored separately from the actual online block in the order entered. Thus, when exchanging parameters in the source, the order of comments might then be wrong. When the block is opened, the comments are then assigned incorrectly. In the worst case comments might even be lost. The following comments in the network are also affected, even when the exchanged parameters are not even commented.	If you have entered comments for parameters, then when assigning the parameters, please keep to the order in which the parameters of the block called are declared.
		Message appears when opening a VAT. The directory S7USS is missing in the SIEMENSSTEP7 directory.	Reinstall STEP 7.
88:47	Unable to reach the module %1 by means of the online interface that is set.	Programming device is connected to the MPI interface of the CPU.	Check whether the CPU is routing-compatible. If Not, then please set your MPI driver to PROFIBUS and connect up with the PROFIBUS DP. Then repeat the desired function.

Error number:	Text:	Cause:	Remedy:
256:24	Function open Environment is not implemetiert	Multiple start of the SIMATIC Manager	In the STEP7_V2/S7met directory delete the files S7CacheA.dat and S7ser.dat with Win95 Explorer. The ending .dat can be left out; depending on the options package, there is also an S7CacheB -E.dat
256:26	Internal OLE Error.	Not enough space on the hard disk, the database cannot be started.	Create space on the hard disk and set user-defined virtual memory.
		Wrong DLL in Windows/System and/or wrong Registry entry.	Start program editor via Explorer and evaluate error message.
			If the following message appears: “The file S7HRVERX.DLL is linked with the missing export S7OTBLDX.DLL: s7_set_password.”, then check whether the file ‘S7OTBLDX.DLL’ is in the Windows system directory. When implementing STEP 7 V4.02, you must delete this file from the Windows system directory.
			If the following message appears: “The file S7KAFAPX is linked with the missing export OT5050R.DLL:4224”, check whether the OT5050R 2x is on the computer. Rename all except those that are in the S7BIN directory.
		With V3.1 when printing	With V3.1 copy block comment into network comment.
		WIN 95: the OLE was not installed properly when installing WINDOWS.	Delete Windows directory and then reinstall WINDOWS.
		Message appears when opening a VAT. The S7USS directory is missing in the directory SIEMENSSTEP7.	Reinstall STEP 7.
256:30	SCL: Programming of S7 moduls. The object was deleted.	Error occurs when you export an SCL source, delete it in the SIMATIC Manager and then import it again and compile it.	Delete the block contained in the source in the SIMATIC Manager first and only then compile.
256:31	This object was not found.	An object that fulfills the criteria specified is not available. The function triggered cannot be executed. The assignments in the OFFLINE database with regard to the HW configuration are no longer consistent.	You can reorganize the addresses with key combination <CTRL>+<ALT>+<F11>.
256:32	Not valid objects.	A link has obviously been lost.	In V2.1 projects the solution is to use “Save As with Reorganization”
256:35	Internal system error is not repairable.
256:49	The quoted entry is not in the registry by Windows or contains a not valid value.	Error occurred when downloading SDBs into a remote CPU via TeleService. The cause here was a bad telephone line connection (analog) (in the USA). After several attempts to set up an ONLINE connection, the SDBs could be transferred without this error message. An attempt was also made to achieve a higher transmission rate with the ONLINE connection.	Set up the connection over and over again and wait for a better line quality. Try to get a higher transmission rate (<- indicator for better line quality at the time of connection set up).

Error number:	Text:	Cause:		Remedy:
256:53	Internal error: Not valid pointer.	In PLCSIM an attempt was made to load the last simulation in PLCSIM via the menu item Simulation -> Last Simulation. Since the old project data (e.g. also block interfaces) has perhaps changed in the meantime, some of the data of the simulation originally created no longer matches the current project.	Create a new simulation via Simulation -> New PLC. The next time you run the last simulation the latest new simulation will be loaded without error message.
256:56	There is an internal error in the system.	Project might be damaged.	Terminate application and restart.
			If the error re-occurs, restart Windows.
	STEP 7 V5.x: There is an internal error in the system.		Send project in to the Technical SIMATIC Customer Support.
256:57	There is an not repairable error in the system during the programming. The function can not be implemented.	ProjID.pro might possibly exist when dearchiving.	Copy/move ProjID.pro.
256:62	Not repairable internal system error in refer to the file “symlist.dbf”.	Project might be damaged.	Computer might have crashed.	Save as … with consistency check or recreate the project.
256:63			Please see the remedies by errror number 258:15.
256:68	The object … cannot be edited because it is currently opened by another application or another user.	This message appears when you start the “File > Save as…” function together with the “With reorganization (slowly)” option if there are still applications open (e.g. Symbol Table) in the project which is being reorganized.	Before reorganizing, close all the applications in the project.
256:85		SIMATIC Manager expects formatted names.	Enter correct name with VAT<digit>.
256:89	The version 513 of the objekt XR00001 is not compatible in refer to the installed software.	Legacy from V2 in XUTIL catalog	Delete the XUTIL directory in the project path
256:92	The data can only be read.	This might be data, for example, from a project or library. The cause might be that there are no write rights for the directory or drive in which the data are located.	Make sure that you have the appropriate rights to access the drive or directory where the data is located. Remedy: Using a virus scanner in Runtime mode can lead to faults. Do the virus scanning offline (i.e. at times when you are not working on your STEP 7 project) or disable the virus scanner on your computer.
		The data is being processed by a different application or by a different user.	Save the modifications made in a different application and make sure that no other user processes this data at the time in question.

Error number:	Text:	Cause:	Remedy:
	The data are read-only.	You have copied a data backup of a project from a CD onto your hard disk and now cannot open this project. The reason for this is that all the files of the project have the attribute “write-protected” set. There are various ways of removing the write-protection from files. One such is described below.	1. Mark the project in the explorer, where is saved in the folder and click on the right mouse botton (example: D:…SiemensStep7S7Proj<Project>). 2. Open in the context menu the “Properties” and select “Security”. 3. Here you can allow the “Read” and other functions by “Permissions for Administrators”. 4. Click after on “Apply” and “OK”.
256:93	The rights of write is missing in the directory.	The directory in which the S7P file is located is write-protected.	Remove the write-protection from all directories that have to do with the project.
		Not enough space on the disk < 100 bytes
		If STEP 7 V4.x is concerned, then it might be that a file has not been deleted, which still specifies that the project is still on a write-protected drive.	Delete S7APROMX.TXT in the root directory of the project.
256:94	Problems with the offline folder.	This message may be due to the fact that the project has been dearchived on a computer and edited with an options package whose version is no longer compatible with the current STEP 7 version.	First of all check the versions of all the options packages installed on your computer which are required for editing the project. You may need to install one or other update (service pack) or upgrade (new version). You can find information about compatibility with SIMATIC software packages for your STEP 7 version in Entry ID 18734363. Then make a copy of your project with “File > Save as…” and the option “With reorganization (slow)”.
256:100	Authorization of STEP 7 is not found.	No Basic Authorization installed. Error occurs when attempting to start an installed options package. Probably STEP 7 is only authorized as Mini.	Install Basic Authorization
256:104	Authorization of optional package is not found.	No user rights (authorization) found for the options software on drive C:.	Install the options authorization from the authorization floppy disk included in the delivery package. If you have lost the authorization (e.g. through a fault on the hard disk), you can install the emergency authorization to be able continue working for a limited period of time. You must then procure a replacement for the lost authorization during this limited time.
		WIN NT: insufficient access rights.	To operate S7 software under NT you need at least main user rights.
256:107		The object specified could not be copied. There might not be enough space left on the data medium. Possibly the target directory is momentarily blocked by another application.	Press the “Yes” button to continue the copy or save operation for the remaining objects. The copied objects might possibly be incomplete or defective in the new environment. If you press the “No” button, the copy or save operation is aborted.

Error number:	Text:	Cause:	Remedy:
		Possibly another STEP 7 application has opened the object to be copied and has thus blocked it. In this case, close all other STEP 7 applications and trigger the process again.
256:111	Access denied	Your have repeatedly loaded a program in the SPS and now it is not possible to load the program again, also not after a new start.	Start the service “Server” in the control panel.
256:119	There is no authorization for STEP 7. To operate this optional package, you require the authorization for “STEP 7 V4.x”.	No authorization installed or the path in which the STEP 7 project is located is too long.	Install the authorization or shorten the project path as appropriate.
257:5	One or more objects of a type cannot be represented. Unable to load the server ‘s7uvpomx.dll’ for _S7UV_LIST_CT-objects. Make sure that the required optional packages are installed.	The process variable server cannot be started. Installation problem with STEP 7. There must not be any incompatible version of WinCC installed on the computer.	Please check the version of the software package installed against the compatibility list. This is located in your STEP 7 directory as the file S7KOMP_x.PDF. x stands for the language: a=German b=English, c=French, d=Spanish, e=Italian.
		Mixed installation, a V4.0 or V4.01 was installed before the installation STEP 7 V5.x.	Deinstall STEP 7 manually and then reinstall it. See FAQ 189025
		Paths in Autoexec.bat are not set.	Edit Autoexec.bat so that the paths are set or not overwritten, as the case may be.
	One or more objects of a type cannot be represented. Unable to load the server ‘s7hkdmax.dll’ for _S7H_DP_ETCR_INTGR_414_2_ROCF_CT- objects. Make sure that the required optional packages are installed.	A file required by STEP 7 has not been found. Probably the project contains objects for which you need an options package that is not installed to process them.	Reinstall the DVA_S7 package.
	One or more objects of a type cannot be represented. Unable to load the server ‘p7spumax.dll’ for _SIPROM_CONTAINER_CT-objects. Make sure that the required optional packages are installed.	There is no authorization permitting you to integrate SIMATIC PDM in STEP 7. This authorization is an options authorization which has to be installed in addition to the basic authorization of SIMATIC PDM.	You must install the options authorization for integrating SIMATIC PDM in STEP 7.

Error number:	Text:	Cause:	Remedy:
	One or more objects of a type cannot be represented. Unable to load the server ‘s7jthomx.dll’ for _AUT_TH_AT-objects. Make sure that the required optional packages are installed.	The S7 project to be opened contains an object that has been created with the options package Technological Hierarchies. This package is not installed or has not been recognized properly after an over-installation of STEP 7.	Reinstall the options package Technological Hierarchies.
	One or more objects of a type cannot be represented. Unable to load the server ‘s7hk31ax.dll’ for _S7H_PLC315_2DPD_Modul_CT-objects. Make sure that the required optional packages are installed.	Toolbox of SINUMERIK 840D is missing or is badly installed.	Reinstall the toolbox for SINUMERIK 840 D.
		The S7 project is opened with STEP 7 V5.x and the SINUMERIK 840D toolbox is installed with version under V5.	The SINUMERIK 840 D V4.x toolbox is incompatible with STEP 7 V5. Please install the toolbox for SINUMERIK 840 D V5.
	One or more objects of a type cannot be represented. Unable to load the server S7HK31AX.DLL for _S7H_6ES7_315_1AF03_0AB0_CT – objects. Make sure that the required optional packages are installed.	Your project contains objects that have been created with the options package C7_626P, but this options package is now not installed.	Please install the options packages concerned; in this case C7_626P.
		The message appears with each project you open, even if it doesn’t contain a C7_626P object.	In STEP 7 you have installed the options package C7_626P with an older version than the version of STEP 7. Please upgrade the package C7_626P.
	One or more objects of a type cannot be represented.Unable to load the server ‘s7wb53ax dll’ for _S7H_6GK7_443_1BX00_0Xe_CT-objects. Make sure that the required optional packages are installed.	The NCM package is not installed and the S7 project contains corresponding objects.	Please install the options packages concerned; in this case the NCM options package.
	One or more objects of a type cannot be represented.Unable to load the server S7HK31AX.DLL for _S7H_PLC314_Modul_CT_objects. Make sure that the required optional packages are installed.	Toolbox of SINUMERIK 810 is missing or badly installed.	Reinstall the toolbox for SINUMERIK 810.

Error number:	Text:	Cause:	Remedy:
	One or more objects of a type cannot be represented.Unable to load the server “s7hsl7ax.dll” for _S7H_DP_PA_LINK_1_ETER_CT-objects. Make sure that the required optional packages are installed.	The error is probably caused by the permanent upgrading of STEP 7. There are several older versions of STEP 7 one on top of the other.	Deinstall STEP 7 manually and then reinstall it.
	One or more objects of a type cannot be represented.Unable to load the server “p7ss357x.dll” for _P7_FM357_6ES7_4AH00_0AE0_CT-objects. Make sure that the required optional packages are installed.
	One or more objects of a type cannot be represented. Unable to load the server S7HK31AX.DLL for _P7_PUSTCH_CPU 314_CT_objects. Make sure that the required optional packages are installed.
	One or more objects of a type cannot be represented.Unable to load the server S7HK31AX.DLL for _P7_POSTECH_CPU 314_CT_objects. Make sure that the required optional packages are installed.	Either the tool MCU-Pit is not installed at all (product of Simodrive/Sinumerik) or the tool MCU-Pit V4.x has been installed in combination with STEP 7 V5.x. Warning: only the version V4.10 of MCU-Pit is released for STEP 7 V5.x.	Install the tool MCU-Pit V4.10. Also, in the directory Drive: SiemensStep7S7MET you must change the name of the file “p7skmcux.mv5” to “p7skmcux.met”. Then you must delete all the remaining *.DAT files in this directory and restart STEP 7 (so that the metafiles can be recompiled).
257:7	Type of object is not declared	A file needed by STEP 7 has not been found. Possibly the project contains objects for which you need an options package that is not installed to process them.
257:8	One or more objects of a type (%1!X!) cannot be represented. Make sure that the required optional packages are installed.	There is an object in the project that has to be parameterized with an S7 options package. This options package is not installed.	Install the missing S7 options package.
	One or more objects of a type (%1!X!) cannot be represented. Make sure that the required optional packages are installed.	There is an object in the project that has to be parameterized with an S7 options package. This options package is not installed.	Please import the type file for the sensor module IF961-ENC4 configured on the FM456.
257:9	The project contains objects of the optional package ‘xxxx’ that cannot be processed because the optional package is not installed or an outdated version is installed.	The project probably contains objects for which you need an options package that is not installed to process them, or a newer version of the options package.	Please install the options package concerned.

Error number:	Text:	Cause:	Remedy:
			In the SIMATIC Manager create a copy of your project (with File > Save as…, Option “With Reorganization (slow)”). Here, the objects that belong to non-installed options packages are deleted in the target project. This error message will then no longer be issued when working with the copy of the project.
257:24	creat environment is not implemented.	SIMATIC Manager has been started double or computer has crashed.	With V2.x, delete the *.dat files in the S7met directory. In any case, procure the latest correction version.
257:26	Not repairable internal system error. The link could not be inserted.	Message appears when you trigger the function “Display Reference Data”. Links are distorted in the project.	Use the function “Save as” together with the option “With Reorganization (slowly)”.
		Message also appears when forwarding a project in conjunction with the symbol table.
257:79	The project or parts of it are currently being edited by another application.	This message appears when you start the “File > Reorganize…” function if there is still an application open (e.g. Symbol Table) in the project which is being reorganized.	Before reorganizing, close all the applications in the project.
257:90	The project ‘%1’ contains errors in the internal data structure.	Project data damage by a crash/power failure on the computer. With the “Details” button you can receive more information on the error, if available.	1. Close all the STEP 7 applications except the SIMATIC Manager. 2. With the menu command “File > Save as (with reorganization (slow)) ” create a of the project which you can then continue to work with. Because of the faults in the existing project, this copy might not contain all the data of the original project.
257:94	Open of project: <Date and Time> S7fupos: Internal error during save of data of server S7ombstx.dll.	Inconsistent project. Application FM 453 has registered errors when saving the machine DBs. A possible cause is the shortage of storage space on the computer.	1. Close all the STEP 7 applications except the SIMATIC Manager. 2. With the menu command “File > Save as (with reorganization (slow)) ” create a of the project which you can then continue to work with. Because of the faults in the existing project, this copy might not contain all the data of the original project.
258:1	Unable to open project data %1.	IDB defined as GDB in the symbol table.	Define IDB correctly. In the case of V2.1, use Save as… for the project.
258:17	The directory C:SiemensSTEP7S7projtemp exist already.	The temporary SDBDATA directory created must have been destroyed by the crash.	In the directory [DRIVE]:SiemensSTEP7S7TEMP delete the directory SDBDATA including subdirectories.
258:20			After archiving call File > Title Field and note the Title Field specifications. After dearchiving you can reestablish these specifications manually via File > Title Field.
258:15		Some files or data blocks are write-protected and, therefore, the data can only be accessed on a read-only basis. This may be due to the fact that write access does not exist for the directory or drive where this data is located, or the block may have been saved as write-protected for reference purposes.	Ensure that you are authorized to access the drive or folder where the data is located.

Error number:	Text:	Cause:	Remedy:
		There are still blocks (FCs, FBs, DBs and/or OBs) open and, as a result, the associated projects and directories cannot be deleted.	Close any STEP 7 (and WinCC flex) editors which are still open. We also advise you to close STEP 7 (and WinCC flex). Go to the Task Manager to check whether there are still any S7 processes in operation and, if so, close them. Then start STEP 7 again and delete the project via “File > Delete”.
			If the remedies under the last above points do not help, close STEP 7 again and delete the project in the Explorer. You can find the folder for the saved project in Fig. 01 under “<Drive>Program FilesSiemensStep7S7Proj<Project> It is possible that the data areas of the HW Config, NetPro, Symbol Table or other STEP 7 components have not been released again completely after being closed. You should be able to delete the projects again after rebooting your PC.
		If the last remedy point does not help either and the project which you wish to delete is still present under the menu commands “File > Open…” and “File > Delete…”, some of the files in the SIMATIC software may be damaged. In most cases, the repair function on the STEP 7 CD can be used to restore the software status on your PC.	Otherwise, we recommend that you uninstall STEP 7 completely beforehand and also delete the directories in the Registry Editor. Follow the procedure precisely as described in our FAQ on “Complete Deinstallation of STEP 7 including all Software Packages”. You can find this FAQ in Entry ID 189025.
275:5020	There is an internal error in the file S7nlvblx.dll.	Save your entries and close the application. Switch your computer off/on and restart the application. If the error reoccurs, then please get in touch with your system administrator.
276:27		No valid connection path between local and remote partners (e.g. because of missing network connection or exhausted resources).	HotFix 1 for SP2 clears this problem. This error is still in SP3 at the moment, but will be cleared by another Add On.
276:42	Loopback – Connecting are not allowed!	Loopback connections are not permitted. You can specify an identical address as local and remote user address, but then SDB generation is rejected with an error message.	Problem (V4.02 and higher) is cleared with correction release K4.02.5. You can ignore this error message, because the communication functions despite this error message.
276:5020	An internal error occurred. (Call: AUTReloadObject)
288:48	Unable to reach the module (z.B.) 413-2DP by means of the subnet assigned to the programming device/PC.	In a new project, for example, a hardware upload was made from the CPU to the PG. In the attempt to immediately download this upload, this error message appears. Problem: under Properties in Options -> Set PG/PC interface, 1 is preset as local user address on the MPI bus. But this does not match the address configured in the hardware upload and hence the error message.	Under Properties in Options -> Set PG/PC interface, set the local user address to 0 (or the one configured previously).

Error number:	Text:	Cause:	Remedy:
289:2	The data base is write-protected or there are not enough memory.	XREF with V2.1.0 + standard control	->Correction K2.1.3 or higher
289:25	Two modules could not be translated back.	XREF with V2.1.0 + standard control	->Correction K2.1.3 or higher
289:35	The selected button can not be executed for the selected menu.	You have selected a block folder and triggered printing.	This is how you print out the reference data for the blocks contained in the folder: 1. Mark the block folder. 2. Select the menu command Options > Reference Data > Display. In this way you display the reference data first. A check is made as to whether reference data is available and whether it is up to date. If necessary you can have the data updated. You can choose which table you want to have printed with which filter setting.
			This is how you print out the all the blocks of the container with the editor with which they have been created: 1. Open the block folder. 2. Select all the blocks (e.g. via the menu command Edit > Select All). 3. Select the menu command File > Print > Object.
291:416		The file is occupied by another application for writing.	Close all the applications that have opened the symbol table and restart the function.
291:416	The symbol table is being by another process.	In the window that opens, the symbols are greyed out since editing is not possible. The Symbol Editor does not show any changes (it is not possible to save the table) and it is not possible to access the symbols.	Editing the entries in the symbol editor is still possible. Make the changes directly in the symbol table and save it. After saving the table, you can edit the symbols in the LAD/FBD/STL editor after closing and opening the dialog box again. If you want to edit the symbols directly in the LAD/FBD/STL editor, close the symbol editor and reopen the dialog box “Edit symbols” in the LAD/FBD/STL editor. Editing is now possible. You can also simultaneously open the symbol table. Changes in other applications are automatically applied in the table.

Error number:	Text:	Cause:	Remedy:
291:416	The symbol table is occupied by another process	In this case you can no longer edit, delete or import the symbol table. The symbol table is not occupied by any other application for writing. You have stored the project locally on the hard disk. The same error is also displayed with the “Save with Reorganization” function of the project.	One possible cause of the error is that after a program crash of the symbol editor, temporary files are not deleted in the S7 data management. In order to control this, check your project: 1. In each project there is a “..YDBs” directory where all the symbol lists are stored. 2. Use Explorer to find files with the suffix .dbf tmp in this and all subordinate directories. 3. Terminate the STEP7 applications and delete these files. Then you can edit all the symbol lists again. It is imperative to make sure that you do not delete other files by mistake in the project, because this could destroy the project.
			1. First of all try closing all the STEP 7 applications including the SIMATIC Manager. If the symbol table is then opened via the SIMATIC Manager, an attempt is first made to clear any inconsistencies in the symbol table through a sort of internal “repair” service. 2. If editing the symbol table continues to be impossible, then please reboot your computer to make sure that all the STEP 7 applications have been closed. Then open the symbol table again. 3. If none of the above steps is successful, open the “..YDB” path mentioned above in the project directory. In this directory delete any files with the file name “deleted.txt” and “update.txt” and a size of 0 KB and any empty folders. You will then be able to edit the symbol table again
291:560	Internal error: Incorrect object ID.	The symtabs function has failed – ambiguous entry in the symbol list for FC names.	Delete the line for the FC in the symbol table.
		When calling an FB, a DB was assigned that is already assigned to another FB in the symbol table.	Assign a different DB in the call or correct the assignment in the symbol table.
			Copy out the symbol table, then open and close the block, and then copy back the symbol table.
291:1392	No symbol table found. No symbol could be created.
292:19	Error by opening of a file.	The file either has no valid B+C287trieve format or it is damaged.	Replace the file or delete it.
293:1	The reference data could no be generated.	The data medium is write-protected.	Remove write-protection.
		Under NT: possibly insufficient access rights.	You need at least main user rights.
293:2	The reference data could no be generated for the SFC14 or the FC22.		Use the function “Save as” together with the option “With Reorganization (slowly)”.

Error number:	Text:	Cause:	Remedy:
294:6	Unable to copy the block %2.	The OBxy is not supported by the CPU.	This OBxy cannot and must not be downloaded into this CPU. You can possibly use another OBxy with a similar function, which is suitable for this CPU and then download it.
		When programming an EPROM via an external prommer: the prommer cable is plugged in incorrectly.	Plug in the prommer cable so that the connector with the yellow sticker is connected to the prommer.
	Illegal command in the modul	The module FCxx could not be copied. (D280) Error during compiling of module in the S7-300.	This message appears, if your program has a marker (example M8000.0) which address is not supported in the CPU. Change the address and repeat the download. If the SF LED is not still erased after download, switch the CPU into STOP and after in RUN again.
294:23	Unable to copy the block %2. Do you want to continue the copy procedure?	A block of this type already exists and it may not be overwritten.	Delete the equivalent block in the ONLINE database and repeat the transfer.
		The automation system is in the RUN operating mode.	Put the automation system into an operating mode that permits copying.
			SDBs can only be transferred in the STOP mode.
		A block of this type and number is not permitted on the automation system.	Check whether a block of this type and this number may be copied onto an automation system of the present type.
		The block is using operands beyond the area of the CPU (e.g. EW 128 with S7-300 CPU).	Check the block with reference to the addresses used whether they do not exceed the permitted address area in the CPU implemented.
		The block is using statements that are not realized in the CPU (e.g. ENT with S7-300 CPU).	Check the block with reference to the commands used based on the operations list for the CPU implemented.
		The block has to much local data (e.g. more than 256 bytes with S7-300 CPU).	When implementing an S7-300, you must reduce the local data area for this block. If you implement an S7-400 CPU, you can parameterize the necessary local data area for each run level.
		Referenced block SFC, SFB is not permitted in this module.	Check whether the blocks that are to be downloaded are permitted on the CPU concerned.
294:27	The block %2 is being processed by another application or another user at the moment.nDo you want to create the reference data for the saved version of the block?	Multi-users: the block specified is being processed at the moment by another application or by another user. You can create a copy of the last version saved or cancel the function.	If you are working with several colleagues on your S7 project, then it is recommended not to process this block without prior synchronization with your colleagues.
		Single Users: the block is opened ONLINE as OFFLINE.	Close the block once; ONLINE or OFFLINE.
295:17240
295:17248	The order was interrupted to the TS-Adapter because of transmission error.	The initialization string is not correct or in this form does not work together with the modem connected to the system.	The initialization string in the TS adapter must be modified in the direct operating mode so that it matches the modem.

Error number:	Text:	Cause:	Remedy:
		On the system there is not a TS adapter but a PC adapter on the modem. The TS adapter has order number 6ES7972-0CA3x-0XA0	Exchange the adapter for a TS adapter.
		Possibly the terminator on the PROFIBUS cable on the system side (TeleService) is switched on.	Switch off the bus terminator.
		Possible the modem is sending too much information to the TS adapter so that it doesn’t get the CONNECT. (Occurs with V5 adapters)	Add W0 to the Initstring in the adapter (this suppresses the sending of extended data)
		If you attempt to get connected via long telephone routes (abroad), then it might happen that some feedback messages have too long a runtime.	In TeleService under Options -> Settings -> Monitoring Times, change the value for Acknowledgment/Signal from Automatic to 5000ms / 4000ms.
295:20484	There is not installed a modem which is compatible with teleservice.		Install a suitable modem and set the modem to correspond with your configuration. Define the TeleService-specific properties of your installed modem in the menu command Options > Settings.
295:20486	The TAPI-Order was closed with the error “Order failure”.	Basically communication between (local) PC and modem (via the serial connection) is not correct or cannot even be started.	Check the connection between the (local) PC and modem for both hardware and software/driver faults.
		Under Windows (Start –> Settings –> Control Panel –> Modems) an incorrect (or no) modem driver has been installed, which does not work in conjunction with the modem connected.	Install the appropriate modem driver for this modem. Also set this new modem in TeleService under Set Connection —> Modem (double-click the telephone book entry and then select the Modem item).
		The wrong modem driver was selected under TeleService from the selection list of modems that are already installed under Windows.	Set the correct modem driver in the selection list.
		The modem is not connected to a serial interface (or to the wrong one).	Connect the modem to the correct serial interface.
		The modem is switched off.	Switch on the modem.
295:32768	TAPI-subsystem dues supply not expected error code <TAPI-Error-Code>
		ALLOCATED 0x80000001
		INVALDEVICECLASS 0x80000023
296:5309	The variables of the instance data block which contain system attributes for messages are not aggree with the variables in the function block.	Clearance: check the function block and save it again if necessary.

Error number:	Text:	Cause:	Remedy:
300:13	Data basis could not be started.	Occurs as a consequence of message 256:94 and details 256:24/256:63 when executing the function “Reorganize” or “Save as… with consistency check”. This occurs when a link is lost in the SYBASE database.	The problem can be solved by deleting the file AMDBASE.LOG. Search in your project path for the log file of the SYBASE database (Amdbase.db). WARNING: if this file does not exist, then search the project for LOG or LOC files.
			If you cannot find this file, then proceed as follows. Restore the log file by entering the following start line via “Start/Run…” on the Windows user interface: dbsrv50 -f D:..Project path..ProjectAMOBJSAmdbase.db For example, for the “Deissw01” project on drive “C” in the standard STEP 7 project directory you enter dbsrv50 -f c:Siemensstep7S7projdeissw01AmobjsAmdbase.db The -f (force) switch has the effect that the DB file is recovered to the last status saved even if the necessary log file is not available.
		Occurs after dearchiving a project in STEP 7 V5.0. It has been created in the version V4.02.x.	After <Save as…><with reorganization> again clears the problem.
314:8	At least one of the selected variables cannot be inserted at this point.	If, while you are processing a project in STEP 7 V5.3 which has been created with STEP 7 V5.1 and the error message described above appears in the LAD/STL/FBD editor when you insert a declaration line within an FB or FC, please check the names of the formal parameters in the declaration line for the block in question. This could be due to the fact that the name “Ret_Val” has been assigned to a formal parameter (IN, OUT, IN_OUT, STAT or TEMP variable).	In this event, the name “Ret_Val” must be renamed. 1. From STEP 7 version V5.2 onwards, users may no longer define the key term “Ret_Val” for the formal parameters. Version V5.2 still supported the entry “Ret_Val” in the declaration line in STEP 7 projects which were created in V5.1 and did not stop the block. 2. However, STEP 7 version V5.3 no longer supports the name “Ret_Val” in the declaration line, and the behavior described above occurs.
724:21	OM TD/OP: Data basis conflict of version file: C:[step7-pfad][Projektname]S7TDOP.DBF has the version 50000. This program expected the version 10000.	The versions of STEP 7 and ProTool are incompatible with those of the project. STEP 7 is V4.02.x and ProTool V5.	Upgrade STEP 7 to V5.x or deinstall ProTool and install V4.02 of ProTool
1230:1001	Opening of the station failed.
1230:2001	Unable to insert the object.	You have tried to slot an object that is not available (e.g. the header for an object group or module class).	Select an object (subrack, module, interface module…) from the hardware catalog, which you can slot in the required location.

Error number:	Text:	Cause:	Remedy:
1230:2009	Changes cannot be made. Save your changes in other applications	The error message indicates that access to the object is not possible at the moment and that the object could not be blocked. This error message can have various causes: 1. The object is currently being processed by another application or user and has therefore been blocked. 2. There is insufficient memory available.	The following steps permit you to process the object: 1. Save the changes made in all other applications and make sure that no other user is currently processing this object. 2. Make sure that there is sufficient virtual memory on your computer, see in this case the informations of the Readme file of STEP 7 by 3.2 Memory Requirements. Notes: Please consider the requirements of the actual installed STEP 7 software in refer to your PC, which are described in the readme file.
1230:2015	Creating the configuration data failed.	Hard disk is full.	Deleted all the unnecessary files on the hard disk.
		No folder “…SIEMENSSTEP7S7TMP” available or the folder is write- protected.	Remove the write-protection from the folder “…SIEMENSSTEP7S7TMP” or create the folder.
		S7 program or M7 program container is missing.	Create S7 program or M7 program container.
		Defective project?	Use “Save as… with reorganization”
		The compilation (= creation of the configuration data) has been interrupted.	Reinstall STEP 7.
	Error attempting to generate the configuration data. Message refers to the V2-projects by Save as with Reorganization.	Subnet addresses of different networks are identical.	Check the subnet addresses and make appropriate corrections in the case of identical subnet addresses.
1230:2016	No changes can be made in this station.	No more modules can be inserted in the HW Config.	Use “Save as… with reorganization” for the project. Please see also the instruction by the error message 256:92.
1230:2018	Another application made changes to your station. Close this station and re-open it.	Another S7 application has changed, for example, via network, the station currently being processed. The changed objects (subrack, modules, slaves, etc.) can no longer be displayed. The station has been blocked for further processing.	You can remove the block by closing the station and re-opening it. This makes the changes of the other application effective.
1230:3000	The system data could not be recreated because the configuration is inconsistent.		Check consistency.
2508:1099	Error by programming of error diagnostic data for <name of variable>.	Group message, behind it detailed messages are listed that occurred during the last function executed.	Please press the “Details” button and analyze the detailed messages.

Error number:	Text:	Cause:	Remedy:
2517:5	The start of an application has occurred an error.	Message appears when opening a HIGRAPH source. With the following software constellation: STEP 7 V5.0 + SP 3 S7-HIGRAPH V4.01.1 S7 project created with S7-Higraph V5.x	Cleared with K4.01.2.
2665:4156	Because of the changes made to the configuration, the configuration file for this SIMATIC PC station has to be created again with NetPro. To do this, use the NetPro menu command “Network > Save and Compile …”
2760:11	communication to higraph cannnot be accessed
2775:777	Address is not correct.	You have selected a user address that is already occupied.	Please select another address or connect your user to another subnetwork.
2775:785	The bit rate of 187,5 kbit/s for the modul MBK-P is not supported in station SIMATIC 400(1).	In STEP7 V5+SP3 and higher the baud rate must not be written with a comma, e.g. 187,5_supp =1	Open and edit the file: enter ‘187.5_supp =1’ instead of ‘187,5_supp =1’. Execute Options -> UPDATE CATALOG.
2775:1829	The data management of “Set PG/PC interface” can not save the requested value.	An attempt was made to save a parameter value in the database of the program “Set PG/PC interface”. This write procedure could not be concluded successfully.
2775:1860	Caution: there are other active nodes (sender parameter assignment master) in station %1 which also have to be reloaded.
3020:13	File name entered is not valid, or Project is invalid, if you attempt to open a project.	This message appears when you stored your project on a network drive which is connected to the following path via the Internet Explorer or a logon script: \<Servername>.<DNS-Suffix><Share> (Example: \computer.siemens.deshare) or \<IP address><share> (Example: \192.168.1.1share). However, this path cannot be found since the network connection is stored only symbolically in the registry.	In order to be able to open your project, please connect the share (without the domain name) via \<Servername><share> (Example: \COMPUTERshare). Note: If you have to enter the pathname via the IP address, you can establish a connection between the IP address and the computer name in the “hosts” file. The file can be found with the Windows path “system32driversetc” (Example: C:WINNTsystem32driversetc).

Error number:	Text:	Cause:	Remedy:
3020:25	Projects which are opened can not be archived. Make sure that in non STEP 7 application objects of the projects … are opened in the directory C:…	The reason for this error message are blocked files, which are also blocked though all the windows of editors and projects are closed. This is possible when the program is activ and the last access was to the archived project. Souch programs are not always to see as user window.	With WinCC or WinCC flexible will be started a SQL server which should be stopped. You will find this in the task bar. You will also find here icons of WinCC flexible, which are mini web or smart server. If you will stop these applications the archiving should be possible again. If not, then start the task manager and check in the process list whether the process “hmies.exe” is activ. If you delete this process, then the archiving should be possible again.
3020:47		This processing status is triggered by PKUnZip in different situations, in particular always when an existing project is overwritten during dearchiving and in the dearchiving options the entry “Overwrite objects with identical names” is not set to “All Files”.	In this – most common – case you can ignore the message.
		The archive file has not been created with PKZip. In particular archives that have been created with WinZip or “PKZip for Windows” and contain “long file names” can lead to this error.	Execute dearchiving with the archiving program used to create the archive.
		The archive file has been created with a version of PKZip that is newer than the version of PKUnZip that is installed on the computer.	If you are using an old version of PKUnZip, install the latest version.
		The archive file is damaged. Checksum errors (so-called CRC errors) have been detected for one or more files. Therefore the files could not be dearchived correctly. The cause of such checksum errors can in particular be: damaged floppy disks, transfer errors when copying, in particular with network drives, file transfer or e-mail, or at the time of archiving the project or parts of it were still open.	Try to get a good copy of your archive file. If this is not possible, you can try to save what is possible to save using the repair option of PKZip. Start the MS-DOS prompt and enter the command ‘pkzipfix archiv’. A file is created called pkfixed.zip – if pkzipfix can even identify the file as being ZIP- compatible. From the SIMATIC Manager dearchive the file pkfixed.zip instead of your original archive file.
		The directories in the archive file have too great a nesting depth to be able to be unpacked under the specified target directory. PKUnZip cannot create any directories whose absolute path name is longer than 66 characters (from the drive designation to the ‘’ at the end of the path).	You can either dearchive the archive file with PKUnZip as follows: select the target directory for dearchiving the Root directory of drive. Close all the STEP 7 applications. Move the dearchived project directory with the Explorer to the location where the project is to be stored. Start the SIMATIC Manager and open the project via the “Browse” button in the “Open” dialog. Or you can use WinZip or PKZIP 2.50 directly at the required location.
		The project already exists and individual files could not be overwritten when dearchiving, because they are write-protected.	Delete the file attribute “write-protected”. You can do this for example for individual files from the Explorer via the file properties, or you start the MS- DOS prompt, get into the project directory using “cd” and then enter the command “attrib -r /s”. Now repeat the dearchiving procedure. D330

Error number:	Text:	Cause:	Remedy:
		The project already exists and individual files could not be overwritten when dearchiving, because the project or objects from the project are already open.	Close all the STEP 7 applications, restart the SIMATIC Manager and dearchive the project without opening the project to be overwritten beforehand.


3020:49	Unable to retrieve the project. The archive file might be defective.	The archive file has not been created with PKZip. In particular archives that have been created with WinZip or “PKZip for Windows” and include “long file names” can lead to this error.	Dearchive using the archiving program with which the archive was created.
		The archive file has been created with a version of PKZip that is newer than the version of PKUnZip installed on this computer.	If you are using an old version of PKUnZip, then install the latest version.
		The archive file is damaged.	Try to get a good copy of your archive file. If this is not possible, you can try to save what is possible to save using the repair option of PKZip. 1. Start the MS-DOS prompt and enter the command ‘pkzipfix archiv’. A file is created called pkfixed.zip – if pkzipfix can even identify the file as being ZIP-compatible. From the SIMATIC Manager dearchive the file pkfixed.zip instead of your original archive file.
		The data medium or the directory in which the dearchived project is to be stored is write-protected, or you have no write authorization for the network drive.	Remove the write-protection or obtain write authorization for the network drive or dearchive the project into a different directory.
3022:4121	The FB is not available The instance declaration is missing	If during compilation in S7-PDIAG the mentioned error message, then it is probably the case that the S7-PDIAG blocks have also been copied from another STEP 7 during the copying procedure. This is not permissible, because the associated SFBs are then no longer up to date.	1. Delete all SFBs. Open and save the FBs, FCs and OBs, which fetches the SFBs from the current library. 2. Now compile the blocks of the S7 program again with S7-DIAG, which should solve the problem.
			Make the Check Block Consistency and compile the complete STEP 7 program.
3022:4121	Invalid data type…”,	The error message is probably caused by an associated value with an invalid data type. Please also refer to the information in the Online Help of S7-DIAG concerning the data types that are valid for associated values.	Excerpt of the Online Help of S7-PDIAG: “This associated value can have a parameter of the type BOOL, BYTE, CHAR, WORD, INT, DWORD, DINT or REAL from the E, A, M or DB areas. Likewise you can enter local variables of an FB to which an error definition is attached. These are extended upon generation according to the type instance concept.
3280:503	The registry database is not set up correctly for the SIMATIC Manager. Install STEP 7 again.	Installation is faulty.

Error number:	Text:	Cause:	Remedy:
3280:708	No objects can be copied or moved from projects/libraries of the current version to projects/libraries of version 2.x.	In STEP 7 there is no downward compatibility, the data management in V2 and >V3 is not the same, so blocks created with STEP 7 V3 or higher cannot be copied or moved into V2.x projects .	An attempt was made to copy or move an object from a version V3 project or from a version V3 library into a version V2 project or library. This is not possible because of incompatibility.
3280:709	The project or the library ‘%1’ is on a write- protected medium.	The project is either located on a write-protected floppy disk or you do not have write authorization for the drive.	Remove the write-protection if you want to modify objects in this project. Please see the instruction by error message 256:92.
		The project catalog was released in the Windows Explorer with read/write access.	Release higher-level catalog of the project (e.g. Step7S7Proj) for access via network drive.
3280:712	File name entered is not valid. Project is invalid. (If you attempt to open a project)		Please see the informations by error message 3020:13.
3280:999	The internet explorer is not installed in your PC.	STEP 7 V5 has been installed without the Internet Explorer and you are trying to start the ONLINE Help.	Please install the Internet Explorer V4.0 and then reinstall STEP 7.
		The ONLINE Help was started and the Internet Explorer was installed after the installation of STEP 7.	Reinstall STEP 7.
3531:1	The diagnostic block could not be created.	Standard blocks in the program originate from the PLC and not from the library. If the project has been created per upload by the PLC with an earlier version of STEP 7 or standard blocks have been copied from the PLC into the offline program, then the interface of the SFBs and SFCs in the project only has a Default Symbolic (parameter name = “IN0”, “IN1” etc. instead of symbolic names as described in the Help). In this case the same error is reported.	Check your interface to the user block. If your user program contains standard blocks with Default Symbolic, then please delete these SFBs and SFCs and reinsert them from the library. This corrects the interface of these blocks.
3534:63	While reporting a system error: an internal error has ocurred	To be able to generate the reference data without this message, proceed as follows: 1. Delete Diagnostics-FB49 and Diagnostics-DB49 from your STEP 7 Project resp. Block container. 2. Newly generate the reference data by selecting the block container and the menu task Extras > Reference data > generate. This message does no longer appear when generating reference data.	You can regenerate the FB49 and DB49 in the Hardware-configuration as follows: 1. Highlight the CPU with the cursor. Under “Extras > reporting system errors… > Register: General”, you can now newly generate the Diagnostics- FB and the Diagnostics-DB. Finally, save and translate the Hardware configuration once more. 2. You can also newly generate the Diagnostics-FB and the Diagnostics-DB by means of “Save and translate” if you change the following setting: Under “Station > Properties … > Register: Settings” the option “Calling when saving and translating” has to be activated.
3534:94	Inconsistent of hardware configuration	The hardware configuration is either inconsistent or it was made changing which are not still save and compiled.	If it is not possible to compile the hardware configuration after this message, so make a little change in the hardware configuration. After it is possible again to save and compile.

Error number:	Text:	Cause:	Remedy:
4050:1		The resources file for this language is not in the directory in which you have installed this program. This is why the menus, dialog boxes and the online Help are in English in S7-PLCSIM.	Install the files that are required for the language desired. If necessary, reinstall S7-PLCSIM and select the required language.
4050:2		Closing the subwindow “CPU” simultaneously closes the simulation session. However, you can close a CPU and start a new simulation session with another CPU.	Make sure that you always have on subwindow open in S7-PLCSIM. If you need more space on your screen, you can reduce the subwindow to icon size.
4050:3		You can only change the MPI address if there are no applications linked with the simulation.	Close all the associated applications or disconnect from the simulation.
4050:4		You can only ever have one simulated automation system activated. If you open a second simulated automation system, the one opened first is closed. If you want to continue the function, press “Yes”. Press “No” to cancel.
4050:5		You cannot exit S7-PLCSIM if there is still a connection set up to STEP 7 (e.g. SIMATIC Manager, variable table, program editor). STEP 7 indicates in a message that the connection to the CPU has been interrupted. You can then continue working offline.	Before exiting S7-PLCSIM you must close the associated applications in STEP 7 or clear down the connection to STEP 7. (In order to disconnect the SIMATIC Manager from S7-PLCSIM you must close both the online program and the offline program.)
4050:6		When doing an overall reset (MRES), all the blocks are deleted and the memory of the simulated automation system is reset.	If you want to abort the overall reset, click “No”. If you wish to do an overall reset, click “Yes” to continue the function.
4050:7		You have attempted to open a simulation that has just recently been used, but which is no longer available or cannot be found. S7-PLCSIM deletes the file name from the menu.	Find the simulated program using the menu command Simulation > Open PLC. If the program is no longer available, you must recreate the simulation.
4050:100		The address you have specified has a format that STEP 7 does not support.	Enter the address in a format that is supported by STEP 7 (IEC or SIMATIC). Examples: IEC: PIB0, PQB0, PIW2, PQW2, I0.0, Q0.0 C1SIMATIC: PEB0, PAB0, PEW2, PAW2, E0.0, A0.0, Z1
4050:101		The value you have entered is not in the valid range for the selected format. For example, you cannot enter “FF” (hexadecimal value) in a field in which binary values are supposed to be entered.	Enter the value in a valid format or change the format of the field.
4050:102		The value you have entered is not a decimal number.	Enter decimal number (e.g. 0, 1, 13).
4050:200		Since there is a danger of changing an actual online program by mistake, you cannot communicate with “real” CPUs whilst the simulation is activated.	Close all the windows and applications that have been used in the simulation of your program before going online with an actual CPU.
4299:158	No connection to FM355/455.	Old firmware on the FM.	Upgrade the firmware of FM.

Error number:	Text:	Cause:	Remedy:
4431:2011	The Authorisation for SIMATIC PDM is not installed. SIMATIC PDM could not be started.	Authorization permitting you to integrate SIMATIC PDM in STEP 7 is missing. This authorization is an option authorization that has to be installed in addition to the basic authorization of SIMATIC PDM.	You must install the additional authorization for integrating SIMATIC PDM in STEP 7.
4502:298	System error 33	This meesage appears during the upload of the hardware configuration. It is possible that the load of the SDBs was not complete or incorrect.	Make a reset of the CPU modul and load the hardware configuration of the offline project again.
4502:625	An error occured while creating or interpreting the system SDB’s. “. Error while creating systemdata………………………………. “.	Regarding mentioned messages occur while saving and translating in HW config if the following applies: 1. You projected and assigned a CP to a subnet in your Hardware configuration. Files with the extension .”err” are missing in the folder “<Siemens-index>Step7S7WBXRUL”. 2. Files with the extension .”err” will be deleted by some optimization programs – like e.g. TuneUp.	Step7 has to be reinstalled or the missing “.err” files have to be copied from a different computer in order to be able to translate the hardware configuration again. Attention: If you copy the files from a second STEP 7 installation, please make sure that this installation contains exactly the same STEP 7 version, the same servicepack and the same hotfix.
4561:142	The Authorisation for Standard PID Control is not installed.	..	..
Meldung von Baugruppen
D033	Error of protokol	Job jam on the CPU.	In the HW Config increase the setting for the communications load for the CPU.
D042	Error during notice by module status of CPU400.	A PQW is being monitored. You cannot read back PQWs, the CPU then reports this error.	Monitor values with VAT and wait for new CPUs.
D043	Error of data: The reference order is not available.	When controlling using Variable Monitoring it might happen that if too many control jobs are sent to the CPU, they are rejected by the CPU because its buffer is full.	Acknowledge the message and reduce the frequency of control jobs.
D062	Resources error, job list is too full.		Please see the informations by error message 33:53346.
D063			Same as D064
D064		CPU 300 does not delete trigger events, the events then build up.	Switch CPU off/on. Problem cleared in the following CPUs: 6ES7 313-1AD01-0AB0 6ES7 314-5AE01-0AB0 6ES7 314-1AE02-0AB0 6ES7 315-1AF01-0AB0 6ES7 315-2AF01-0AB0
D0AA	D0AA: The time limit is exceeded in process operating.	Communications load is too high.	Increase the communications load of the CPU from (default) 20% to 50%.

Error number:	Text:	Cause:	Remedy:
		Message appears with the function “Control via VAT” to an address from the memory areas I, O, M, Timer, Counter, DB, which is not available in the broadest sense.	Please check the syntax of the address in the VAT, or whether the address is available in the system or perhaps not addressable (wiring fault, hardware fault).
D204	D204: An error in the rules of coordinating has occured.	When attempting to load system data, in the background a variable table was still open online.	Close the variable table and retransfer the system data.
D20C	The OB can not be copied because the belong layer is not available.	Message comes from a CPU. An attempt is being made to transfer an OB onto this CPU, which is not permissible.	If possible, rename the OB or even delete it in the OFFLINE database and retrigger the transfer.
D240	An error in the rules of coordinating has occured.	Occurs if a block that is to be overwritten online is still being accessed. In V4.01 with blocks in the call environment.	Deactivate the setting “Call path with test/call environment”, then the block can be downloaded.
	An error in the rules of coordinating has occured.	Occurs when an object is accessed online (also VAT).	Close everything except HW Config.
	Error during opening of a empty document. Error during opening of a symbolic table.	An incompatible OPC Manager is installed. In the system path of Windows vcf1.lic is responsible for this.	Delete this file and the file vcf132.ocx and reinstall STEP 7.
	Setup does not start with error message: in function “Sdbitmap”:unable to crate dialog make sure the _isres.dll is in _setup.lib	The _isres.dll is needed for switching languages.	Start Setup with the extension ol:b, then the Setup is forced to start in English.
D280	Error during compilation of a modul in S7-300. The module OB1 could not be copied.	This message appears, when the defined variable (marker, in- or output) in a module is not in the power range of the CPU.	Example, this message appears if the number of outputs is 8192 byte by the CPU and you have defined a variable outside of this range. Check the addresses with the definition of your variables.
D406	The requested informations are not available.	Number of possible connections has been exceeded.	Check the connections and reduce where appropriate. Static connections can be converted into dynamic connections.
EA 02	The protocols of communication software (S7DOS) and the interface module (CP) are not compatible.	The customer has a STEP 7 V5+SP1 + recent PDM and a CP 443-5 Ext > V2.7. The new RPC 7 protocol is used for data record routing between the CP and S7DOS. Unfortunately the CP up to version V2.7 does not support this function.	Upgrade CP 443-5 to a version >V2.7.
		The user is using the correct components STEP 7 V5 + SP2 + PDM, but has a CP that does not have the DSGW.	Check the configuration and replace the CP being used with a different CP that has this function.
Set PG/PC interface
None	Error message by diagnostic: “Profibus/MPI Network diagnostic”. Error: requested parameter could not be read from the register data basis!	Firmware/driver error	This behavior no longer occurs in SOFTNET PROFIBUS S7 V5.0.
Message without numerical order
S7OTBLSTX	Incompatible versionen by S7OTBLDX.DLL and S7OTBLSX.DLL.	S7 applications are still running at Setup of STEP 7.	Please close all S7 applications and restart SETUP.

Error number:	Text:	Cause:	Remedy:
		STEP 7 has been installed on a computer on which an S7 options package or version of ProTool /WIN CC is already installed which is not compatible with the version of STEP 7.	Please search for “S7OT.” on all your local drives and delete them. Then please restart the Setup of STEP 7.

Источник

5 Окт 2019

Здравствуйте! Есть старенький фрезерный обрабатывающий центр Samag cs400-w с simenurik 810m. В документации не хватает страниц с распечатками MD и PLC, дискеты нет. Вся инфа продублирована в ASM модуле, но он не читается (ошибка 11- asm пуст). Вытащив из модуля ПЗУ-шки считали их программатором. Инфа есть, но нечитаемая. Возможно ли это восстановить?

ASM.zip

41 КБ

· Посмотрено: 113

11 Окт 2019

Доброго времени суток. Есть станок с системой 840С, вышел из строя маховичок
6FX2007-1AB11, может кто подскажет, как его отсоединить, чтобы система не ругалась.
Заранее спасибо.

11 Окт 2019

После обработки модуля (ASM-на фото) вот, что получилось. Кодировку брал «ia5 irv международный алфавит №5». Но все равно не все читается. Не вижу программ PLC. Может другая кодировка нужна?

сумма1-4.zip

216,8 КБ

· Посмотрено: 84
IMG_20180504_173848.1.jpg

626,8 КБ

· Посмотрено: 315

14 Окт 2019

andreieinav, Приветствую!
В наличии модуль 6FC5410-0AY01-0AA1 (предыдущий 6FC5410-0AY00-0BA0 вышел из строя), но в нём версия ПО 2.4, а электроавтоматика написана под версию 1.3. Процессор с CPU315 на CPU314 уже поменяли.

При подключении через Simatic Manager выдаёт ошибку FF80
Event 6 of 100: Event ID 16# 4550
DEFECTIVE: internal system error
No relevance for user (Z1): ff80
Previous operating mode: No voltage
Requested operating mode: No voltage
Internal error, Incoming event
12:26:24.342 AM 02/07/1994
(Coding: 16# 4550 FFFF 0000 FF80 2211 AFFE)

Если есть у кого-нибудь PCMCIA карта с заказным номером 6FC5450-1AX00-3AH0, поделитесь пожалуйста образом… или готов купить карту.

19 Окт 2019

anatoly_k_57, у нас их ремонтят. Не я.
Если ремонтят , то для чего то же он нужен.
Как отсоединяется — не в курсе.
Что видел , так это часто кабеля меняют.
Попробуй с другого на подкид.

20 Окт 2019

Так уже выяснили — там платка вставная сдохла (вроде это MPI интерфейс или ещё что),
хотели пока новую найдут или сам пульт купят, чтобы так поработали.

19 Ноя 2019

Доброго времени суток, попросили запустить… 810T GA3, токарный станок.
‘вещь’ вижу второй раз,(первый всё сбросилось и заработало более года назад).
прочитал тему, скачал разных pdf, на батарею не жалуется, но режимы не переключает…
куда копать…
не исключаю, что до меня там уже кто-то заглядывал…
шнур и PCIN , не смог связать чтобы увидеть что есть в машине, как слить с неё в комп, странные настройки интерфейса (относительно pdf)
документации нет от слова ВООБЩЕ…
понимаю , что изготовитель имеет право вносить изменения не ухудшающие характеристики…

IMG_20191119_131631.jpg

1,1 МБ

· Посмотрено: 397
IMG_20191119_131646.jpg

1 МБ

· Посмотрено: 334
IMG_20191119_131749.jpg

1,1 МБ

· Посмотрено: 298
IMG_20191119_131756.jpg

1,1 МБ

· Посмотрено: 371
IMG_20191119_131805.jpg

1,1 МБ

· Посмотрено: 248
IMG_20191119_132650.jpg

1 МБ

· Посмотрено: 307
IMG_20191119_140646.jpg

1,1 МБ

· Посмотрено: 360
IMG_20191119_140730.jpg

1,1 МБ

· Посмотрено: 361

20 Ноя 2019

Добрый вечер всем. Вопрос к знающим и ко всем кто может чем то помочь. Имеется гибочный станок конца девяностых изготовленный в германии с 880м 18 осей. Привезли только что и собрали неделю назад. Включили.пытались запустить. Вывели почти все оси в референт. Потом перестал реагировать на снятие барьера. В чпу сигнал приходит а пишет что барьер не сброшен. Решили переустановить. Выкачали все файлы что были.загрузили три по инструкции с данного сайта.после инсталяции догрузили остальное. Сейчас машина обнуляется.но при попытке запустить программу ведет себя не адекватно. Выводит две оси в позицию.после этого делает не нужное движение и самое непонятное после этого отрубает плц 43 PLC-CPU fault. После выключения рубильником и последующем включении работоспособность восстанавливается. Отсюда вопрос.что может заставить отрубить PLC? Ошибка в программировании.не правильная работа чпу в следствии его неисправности или ошибки в файлах ТЕА1.ТЕА2.SEA? Кстати в выкачанных файлах был еще ТЕА3. Весь форум прочитал.ничего не нашел про него. Залил его после первых трех.
И еще. В документации на это чудо есть распечатка первых трех системных файлов. При сравнении с теми что были в станке есть различия. Не анализировали пока.завтра этим будем заниматься. Не знаю как это может помочь.посмотрим.
Есть какие мысли у кого по этому поводу? Буду крайне признателен всем откликнувшемся.

13 Дек 2019

Добрый день, станок фрезерный Eagle 1000, ЧПУ siemens d810 . При обработке детали встает перемещение координатного стола на 4-5 сек пишет вот эту ошибку» 510009 waiting for spindel speed arrive». Потом далее продолжает работу. И так все повторяется ну не сказать что очень часто, но за смену раза 4-5. Иногда не встает но тоже появляется сообщение какое то но пока сам не засек. Может кто то сталкивался с такой проблемой. В описании ошибок ничего не нашли.

IMG-20191213-WA0004.jpg

65,7 КБ

· Посмотрено: 271

23 Дек 2019

добрый день! уважаемые форумчане прошу помощи есть синумерик 810T GA3 … машинные данные взял с аналогичного станка…но вот одно но что относительно нулевой точки есть смещение 3 мм…подскажите в каком параметре подкоректировать это? и заодно ось X…спасибо

14 Янв 2020

Слетели управляющие программы на станке weiler DZ32 стойка sinumerik 820t ga3, у кого-нибудь есть установочные файлы на подобную машину,обращались на weiler пока ответа нет.

2 Мар 2020

DMU35M 810DE CCU1
регулярно с некоторой частотой (от пол года до 2 месяцев) выкидывал ошибку по неправильным обротам шпинделя.
Любое его движение даже рукой приводило стойку в ступор. Перезагрузка помогала только до следующей попытки движения шпинделя.
Остальные оси в выходили в рефрент и двигались.
Причин такого поведения пока не выявлено.
Стойку снимал разбирал — батарею менял для перестраховки.
Лечилось только перезаливкой архивов. Соответсвенно процедура была изучена, описана в небольшой мануал и проходила быстро.
Загружались только два архива NCK и PLC.

И вот пришел тот день когда архивы «не лезут» нивкакую. Стойка сбрасывается, прога заливки ожидает от стойки продолжения.
Удалось на стойке подсмотреть то что происходит в момент попытки загрузки.

На дискетах к станку кроме двух архивов на диске 0 еще присутствуют файлы на дисках 1 и 2.
Этих файлов никогда не использовали. Куда и как их заливать нету никакой инфы.

Вопрос что еще предпринять для оживления станка?

П.С. Когдато Kirill.tex писал от проблеме остановки загрузки при заливке NCK.
Я тоже столкнулся с этим при первой переустановке — лечилось отключением бита определения конца файла в в настройках связи (прикрепленный pdf). Но тогда архивы грузились и останавливалось в процессе. А сейчас загрузка останавливается в самом начале. Не успевает даже на экране статуса загрузки чтото появится.

DMU35_FDD0.rar

128 КБ

· Посмотрено: 44
DMU35_FDD1.rar

192,1 КБ

· Посмотрено: 48
DMU35_FDD2.rar

6,4 КБ

· Посмотрено: 44
Data Loading_810D_840D.pdf

515,9 КБ

· Посмотрено: 41

7 Мар 2020

Сегодня удалось запустить DMU35M 810DE CCU1 используя HMI Advanced + MPI карта 5511 + NCK и PLC файлы архивов + прямое соединение с CCU1 по MPI порту (X122).
Архивы встали с первого раза. После перезаливки удалось залить обратно копии рабочих программ через тот же порт который
в упор не воспринимал архивов.
Времени на эксперименты с перезагрузкой штатным способом небыло. Время покажет как поведет себя стойка в будущем…

10 Мар 2020

Добрый вечер. Подскажите пожалуйста. Возможно ли склонировать карту из NCU ?
И второй вопрос — на панели PCU20 есть разъем PCMCIA и в меню ввода-вывода есть кнопка ATA Card. Если купить переходник PCMCIA на CF можно будет туда вывести архивы? Подойдёт ли обычная cf карта на 128 мб? Спасибо.

11 Мар 2020

Vitali1980, могу ответить по второму вопросу У нас на станках Spinner в PCU20 стоят PCMCIA карты на которые операторы скидывают программы. На одном станке карта вышла из строя и была заменена CF картой с переходником. Правда у меня не получилось правильно отформатировать карту ( В биосе карта видна а после загрузки системы уже нет). Поэтому сделал образ PCMCIA карты с соседнего станка и перенес его на CF карту. После чего все заработало

11 Мар 2020

andrez сказал(а):

Vitali1980, могу ответить по второму вопросу У нас на станках Spinner в PCU20 стоят PCMCIA карты на которые операторы скидывают программы. На одном станке карта вышла из строя и была заменена CF картой с переходником. Правда у меня не получилось правильно отформатировать карту ( В биосе карта видна а после загрузки системы уже нет). Поэтому сделал образ PCMCIA карты с соседнего станка и перенес его на CF карту. После чего все заработало

Какой программой делали образ и на каком оборудовании? Не поделитесь образом? Как на экране в меню она обзывается? ATA Card ?

Может у кого нибудь есть образ NC карты с номером: 6fc5250-6bx10-4ah0

11 Мар 2020

Vitali1980, эээ а мы разговариваем о карте которая стоит в PCU20 или о карте которая стоит в NCU 6fc5250-6bx10-4ah0 это как 8mB PCMCIA карта стоящая в NCU. Если речь идет о карте в PCU20 то образ я делал программой Winimage или можно использовать win32diskimager. на экране отображается ATA-CARD

11 Мар 2020

andrez сказал(а):

Vitali1980, эээ а мы разговариваем о карте которая стоит в PCU20 или о карте которая стоит в NCU 6fc5250-6bx10-4ah0 это как 8mB PCMCIA карта стоящая в NCU. Если речь идет о карте в PCU20 то образ я делал программой Winimage или можно использовать win32diskimager. на экране отображается ATA-CARD

Да да про карту которая в pcu20. Про ncu это я так спросил. Просто боюсь ее трогать, подумал может кто делал образ ее).
А на каком железе делали и под какой системой? Можете образ дать? Там адресация на карте памяти не lba, поэтому думаю и у меня не получится ее правильно отформатировать. Буду идти по вашему пути. Заранее спасибо

12 Мар 2020

Vitali1980, вот ссылка на образ карты сделанный Winimage ( ссылка скрыта от публикации ) На карте записана куча ненужных вам программ., удалите их уже на станке.

12 Мар 2020

andrez сказал(а):

Vitali1980, вот ссылка на образ карты сделанный Winimage ( ссылка скрыта от публикации ) На карте записана куча ненужных вам программ., удалите их уже на станке.

Спасибо. А какой размер CF карты у вас и какого производителя карта?

12 Мар 2020

Какая то китайская на 256 мб вроде. Давно это было Сейчас на станке стоит уже несколько лет работает.

12 Мар 2020

А на чем записывали образ? Через PCMCIA адаптер или через USB картридер.

12 Мар 2020

образ я делал через PCMCIA адаптер ( вот такой

Текст скрыт от гостей. Для просмотра войдите в свой аккаунт.

через него и записывал на CF карту с переходником на PCMCIA

12 Мар 2020

kratmel сказал(а):

В инструкции к Sinucom FFS
указано что нужно установить драйвера
Cardware.

В сети валяется архив с CardWare 07.00.011.
С генератором ключа.

После установки надо прописать строчки конфигурации Sinucom FFS как описано в ниже приложеном файле.

► siemense.txt

Можете подробней написать как правильно настроить конфигурацию?

Cardware for Windows 2000/XP (version 1.00.003 or newer):
— Writer: <WINDOWSDIR>SYSTEM32CWMEMCTL.EXE /ES:<SOCKET> «/DF:%1» /WS:<SOCKET> /Y
— Reader: <WINDOWSDIR>SYSTEM32CWMEMCTL.EXE «/DF:%1» /RS:<SOCKET> /Y

Я установил Cardware 7 на XP но по указанным путям нет файла CWMEMCTL.EXE

SonFar сказал(а):

Уххх… Получилось только с двадцатого раза. Спасибо kratmel за разъяснение. На заметку, получилось провернуть с trial версией CardWare, т.е. без ключей и кряков.

Судя по надписи «CheckSum is OK» с картой все в порядке.

Однако во вкладке «Serial Number» картина отличается от представленной выше. В моем случае там одни нули.

1. Интересно, откуда Sinucom знает какая у моей карты должна быть контрольная сумма.
2. И это контрольная сумма чего. Полностью карты или какого-то его раздела.
3. На карте отчетливо видно два раздела. Первый похоже что это все параметры станка. А второй состоит из папки Архивы и еще что-то.

Можете и мне разъяснить как правильно настроить программу? Спасибо

13 Мар 2020

— Writer: <WINDOWSDIR>SYSTEM32CWMEMCTL.EXE /ES:<SOCKET> «/DF:%1» /WS:<SOCKET> /Y

C:WINDOWSSYSTEM32CWMEMCTL.EXE /ES:1 «/DF:%1» /WS:1 /Y

— Reader: <WINDOWSDIR>SYSTEM32CWMEMCTL.EXE «/DF:%1» /RS:<SOCKET> /Y

C:WINDOWSSYSTEM32CWMEMCTL.EXE «/DF:%1» /RS:1 /Y

<SOCKET> может принимать значение 0 или 1 в зависимости какой кардридер.

CWMEMCTL.EXE просто поищите поиском и вставте путь вместо <WINDOWSDIR>SYSTEM32CWMEMCTL.EXE который получится.

Источник

Events 34.5 Event Class 4 — Stop Events and Other Mode Changes Event ID Event W#16#4300 Backed-up power on W#16#4301 Mode transition from STOP to STARTUP W#16#4302 Mode transition from STARTUP to RUN W#16#4303 STOP caused by stop switch being activated W#16#4304 STOP caused by PG STOP operation or by SFB 20 «STOP» W#16#4305 HOLD: breakpoint reached W#16#4306 HOLD: breakpoint exited W#16#4307 Memory reset started by PG operation W#16#4308 Memory reset started by switch setting W#16#4309 Memory reset started automatically (power on not backed up) W#16#430A HOLD exited, transition to STOP W#16#430D STOP caused by other CPU in multicomputing W#16#430E Memory reset executed W#16#430F STOP on the module due to STOP on a CPU W#16#4510 STOP violation of the CPU’s data range W#16#4318 Start of CiR W#16#4319 CiR completed W#16#4520 DEFECTIVE: STOP not possible W#16#4521 DEFECTIVE: failure of instruction processing processor W#16#4522 DEFECTIVE: failure of clock chip W#16#4523 DEFECTIVE: failure of clock pulse generator W#16#4524 DEFECTIVE: failure of timer update function W#16#4525 DEFECTIVE: failure of multicomputing synchronization W#16#4926 DEFECTIVE: failure of the watchdog for I/O access W#16#4527 DEFECTIVE: failure of I/O access monitoring W#16#4528 DEFECTIVE: failure of scan time monitoring W#16#4530 DEFECTIVE: memory test error in internal memory W#16#4931 STOP or DEFECTIVE: memory test error in memory submodule W#16#4532 DEFECTIVE: failure of core resources W#16#4933 Checksum error W#16#4934 DEFECTIVE: memory not available W#16#4935 DEFECTIVE: cancelled by watchdog/processor exceptions W#16#4536 DEFECTIVE: switch defective W#16#4540 STOP: Memory expansion of the internal work memory has gaps. First memory expansion too small or missing. W#16#4541 STOP caused by priority class system W#16#4542 STOP caused by object management system W#16#4543 STOP caused by test functions W#16#4544 STOP caused by diagnostic system W#16#4545 STOP caused by communication system W#16#4546 STOP caused by CPU memory management W#16#4547 STOP caused by process image management W#16#4548 STOP caused by I/O management W#16#4949 STOP caused by continuous hardware interrupt W#16#454A STOP caused by configuration: an OB deselected with STEP 7 was being loaded into the CPU during STARTUP W#16#494D STOP caused by I/O error System Software for S7-300/400 System and Standard Functions — Volume 2/2 34-8 A5E00739858-01

Events Event ID Event W#16#494E STOP caused by power failure W#16#494F STOP caused by configuration error W#16#4550 DEFECTIVE: internal system error W#16#4555 No restart possible, monitoring time elapsed W#16#4556 STOP: memory reset request from communication system / due to data inconsistency W#16#4357 Module watchdog started W#16#4358 All modules are ready for operation W#16#4959 One or more modules not ready for operation W#16#4562 STOP caused by programming error (OB not loaded or not possible W#16#4563 STOP caused by I/O access error (OB not loaded or not possible W#16#4567 STOP caused by H event W#16#4568 STOP caused by time error (OB not loaded or not possible) W#16#456A STOP caused by diagnostic interrupt (OB not loaded or not possible) W#16#456B STOP caused by removing/inserting module (OB not loaded or not possible) W#16#456C STOP caused by CPU hardware error (OB not loaded or not possible, or no FRB)STOP W#16#456D STOP caused by program sequence error (OB not loaded or not possible) W#16#456E STOP caused by communication error (OB not loaded or not possible) W#16#456F STOP caused by rack failure OB (OB not loaded or not possible) W#16#4570 STOP caused by process interrupt (OB not loaded or not possible) W#16#4571 STOP caused by nesting stack error W#16#4572 STOP caused by master control relay stack error W#16#4573 STOP caused by exceeding the nesting depth for synchronous errors W#16#4574 STOP caused by exceeding interrupt stack nesting depth in the priority class stack W#16#4575 STOP caused by exceeding block stack nesting depth in the priority class stack W#16#4576 STOP caused by error when allocating the local data W#16#4578 STOP caused by unknown opcode W#16#457A STOP caused by code length error W#16#457B STOP caused by DB not being loaded on on-board I/Os W#16#497C STOP caused by integrated technology W#16#457D Reset/clear request because the version of the internal interface to the integrated technology was changed. W#16#457F STOP caused by STOP command W#16#4580 STOP: back-up buffer contents inconsistent (no transition to RUN) W#16#4590 STOP caused by overloading the internal functions W#16#49A0 STOP caused by parameter assignment error or non-permissible variation of setpoint and actual extension: Start-up blocked. W#16#49A1 STOP caused by parameter assignment error: memory reset request W#16#49A2 STOP caused by error in parameter modification: startup disabled W#16#49A3 STOP caused by error in parameter modification: memory reset request W#16#49A4 STOP: inconsistency in configuration data W#16#49A5 STOP: distributed I/Os: inconsistency in the loaded configuration information W#16#49A6 STOP: distributed I/Os: invalid configuration information W#16#49A7 STOP: distributed I/Os: no configuration information W#16#49A8 STOP: error indicated by the interface module for the distributed I/Os System Software for S7-300/400 System and Standard Functions — Volume 2/2 A5E00739858-01 34-9

Page 1 and 2:
s SIMATIC System Software for S7-30
Page 3 and 4:
Preface Purpose Audience This manua
Page 5 and 6:
Online Help Preface The manual Volu
Page 7 and 8:
Technical Support You can reach the
Page 9 and 10:
Contents 1 Organization Blocks 1-3
Page 11 and 12:
Contents 10 SFCs for Handling Time-
Page 13 and 14:
1 Organization Blocks 1.1 Overview
Page 15 and 16:
OB Start Event Default Priority Cla
Page 17 and 18:
Local Data for OB1 Organization Blo
Page 19 and 20:
Understanding the Operation of Time
Page 21 and 22:
Local Data for Time-of-Day Interrup
Page 23 and 24:
Local Data for Time-Delay Interrupt
Page 25 and 26:
Local Data for Cyclic Interrupt OBs
Page 27 and 28:
Organization Blocks If a hardware i
Page 29 and 30:
1.8 Update Interrupt OB (OB 56) Des
Page 31 and 32:
Organization Blocks 1.10 Multicompu
Page 33 and 34:
Organization Blocks 1.11 Synchronou
Page 35 and 36:
1.13 I/O Redundancy Error OB (OB70)
Page 37 and 38:
1.14 CPU Redundancy Error OB (OB72)
Page 39 and 40:
The following table shows which eve
Page 41 and 42:
1.16 Time Error Organization Block
Page 43 and 44:
Error code Bit Meaning • B#16#0A
Page 45 and 46:
Organization Blocks The variables O
Page 47 and 48:
Variable Type Description OB82_MDL_
Page 49 and 50:
Reconfiguring modules Organization
Page 51 and 52:
OB83_EV_CLASS OB83_FLT_ID Meaning B
Page 53 and 54:
1.21 Priority Class Error Organizat
Page 55 and 56:
OB85_EV_CLASS OB85_FLT_ID Meaning O
Page 57 and 58:
1.22 Rack Failure Organization Bloc
Page 59 and 60:
OB86_EV_CLASS OB86_FLT_ID Meaning O
Page 61 and 62:
OB86_EV_CLASS OB86_FLT_ID Meaning O
Page 63 and 64:
The variables dependent on the erro
Page 65 and 66:
Variable Data type Description Orga
Page 67 and 68:
Local Data for OB90 Organization Bl
Page 69 and 70:
Local Data for Startup OBs Organiza
Page 71 and 72:
Bit No. Meaning Possible Binary Val
Page 73 and 74:
1.27 Programming Error Organization
Page 75 and 76:
Organization Blocks Error code Mean
Page 77 and 78:
Local Data for the I/O Access Error
Page 79 and 80:
2 Common Parameters for SFCs 2.1 Ev
Page 81 and 82:
General Error Information Common Pa
Page 83 and 84:
Common Parameters for SFCs Error Co
Page 85 and 86:
Identifying the Job Common Paramete
Page 87 and 88:
Overview Common Parameters for SFCs
Page 89 and 90:
3 Copy and Block Functions 3.1 Copy
Page 91 and 92:
Error Information Error Code (W#16#
Page 93 and 94:
Error Information Copy and Block Fu
Page 95 and 96:
Exceptions The following cannot be
Page 97 and 98:
Error Information Copy and Block Fu
Page 99 and 100:
Error Information Error Code (W#16#
Page 101 and 102:
3.7 Compressing the User Memory wit
Page 103 and 104:
Copy and Block Functions 3.8 Transf
Page 105 and 106:
Operating principle Copy and Block
Page 107 and 108:
Copy and Block Functions 3.10 Readi
Page 109 and 110:
Copy and Block Functions 3.11 Writi
Page 111 and 112:
Copy and Block Functions 3.12 Creat
Page 113 and 114:
4 SFCs for Controlling Program Exec
Page 115 and 116:
SFCs for Controlling Program Execut
Page 117 and 118:
Error information Error code (W#16#
Page 119 and 120:
5 SFCs for Handling the System Cloc
Page 121 and 122:
SFCs for Handling the System Clock
Page 123 and 124:
Parameters Declaration Data type Me
Page 125 and 126:
6 SFCs for Handling Run-Time Meters
Page 127 and 128:
Error information Error code W#16#.
Page 129 and 130:
SFCs for Handling Run-Time Meters 6
Page 131 and 132:
SFCs for Handling Run-Time Meters 6
Page 133 and 134:
7 SFCs/SFBs for Transferring Data R
Page 135 and 136:
System Resources SFCs/SFBs for Tran
Page 137 and 138:
SFCs/SFBs for Transferring Data Rec
Page 139 and 140:
SFCs/SFBs for Transferring Data Rec
Page 141 and 142:
Error Code (W#16#…) SFCs/SFBs for
Page 143 and 144:
SFCs/SFBs for Transferring Data Rec
Page 145 and 146:
SFCs/SFBs for Transferring Data Rec
Page 147 and 148:
Using Old S7-300 FMs and CPs with D
Page 149 and 150:
Error Code (W#16#…) Explanation 8
Page 151 and 152:
8 DPV1 SFBs According to PNO AK 113
Page 153 and 154:
DPV1 SFBs According to PNO AK 1131
Page 155 and 156:
DPV1 SFBs According to PNO AK 1131
Page 157 and 158:
Structure of the address (bytes 20
Page 159 and 160:
Byte no. for TINFO Data type 24 BYT
Page 161 and 162:
DPV1 SFBs According to PNO AK 1131
Page 163 and 164:
DPV1 SFBs According to PNO AK 1131
Page 165 and 166:
DPV1 SFBs According to PNO AK 1131
Page 167 and 168:
Error Information DPV1 SFBs Accordi
Page 169 and 170:
Error_Decode (B#16#…) Error_Code_
Page 171 and 172:
DPV1 SFBs According to PNO AK 1131
Page 173 and 174:
ATYPE parameter DPV1 SFBs According
Page 175 and 176:
DPV1 SFBs According to PNO AK 1131
Page 177 and 178:
ERROR STATUS[2,3] (W#16# …) Expla
Page 179 and 180:
9 SFCs for Handling Time-of-Day Int
Page 181 and 182:
Executing the Time-of-Day Interrupt
Page 183 and 184:
SFCs for Handling Time-of-Day Inter
Page 185:
SFCs for Handling Time-of-Day Inter
Page 188 and 189:
SFCs for Handling Time-Delay Interr
Page 190 and 191:
SFCs for Handling Time-Delay Interr
Page 192 and 193:
SFCs for Handling Time-Delay Interr
Page 194 and 195:
SFCs for Handling Synchronous Error
Page 196 and 197:
SFCs for Handling Synchronous Error
Page 198 and 199:
SFCs for Handling Synchronous Error
Page 200 and 201:
SFCs for Handling Synchronous Error
Page 202 and 203:
SFCs for Handling Synchronous Error
Page 204 and 205:
SFCs for Handling Interrupts and As
Page 206 and 207:
SFCs for Handling Interrupts and As
Page 208 and 209:
SFCs for Handling Interrupts and As
Page 210 and 211:
SFCs for Handling Interrupts and As
Page 212 and 213:
SFCs for Diagnostics TOP_SI and STA
Page 214 and 215:
SFCs for Diagnostics 13.3 Reading a
Page 216 and 217:
SFCs for Diagnostics SSL_IDs Note F
Page 218 and 219:
SFCs for Diagnostics SSL_ID (W#16#.
Page 220 and 221:
SFCs for Diagnostics 13.4 Writing a
Page 222 and 223:
SFCs for Diagnostics SEND EVENTN IN
Page 224 and 225:
SFCs for Diagnostics 13.5 Determini
Page 226 and 227:
SFCs for Diagnostics Parameter Decl
Page 228 and 229:
SFCs for Diagnostics 13.6 Diagnosis
Page 230 and 231:
SFCs for Diagnostics Parameters Dec
Page 232 and 233:
SFCs for Diagnostics Parameters Dat
Page 234 and 235:
SFCs for Diagnostics Operating meth
Page 236 and 237:
SFCs for Diagnostics System Softwar
Page 238 and 239:
SFCs and SFBs for Updating the Proc
Page 240 and 241:
SFCs and SFBs for Updating the Proc
Page 242 and 243:
SFCs and SFBs for Updating the Proc
Page 244 and 245:
SFCs and SFBs for Updating the Proc
Page 246 and 247:
SFCs and SFBs for Updating the Proc
Page 248 and 249:
SFCs and SFBs for Updating the Proc
Page 250 and 251:
System Functions for Addressing Mod
Page 252 and 253:
System Functions for Addressing Mod
Page 254 and 255:
System Functions for Addressing Mod
Page 256 and 257:
System Functions for Addressing Mod
Page 258 and 259:
System Functions for Addressing Mod
Page 260 and 261:
SFCs for Distributed I/Os or PROFIN
Page 262 and 263:
SFCs for Distributed I/Os or PROFIN
Page 264 and 265:
SFCs for Distributed I/Os or PROFIN
Page 266 and 267:
SFCs for Distributed I/Os or PROFIN
Page 268 and 269:
SFCs for Distributed I/Os or PROFIN
Page 270 and 271:
SFCs for Distributed I/Os or PROFIN
Page 272 and 273:
SFCs for Distributed I/Os or PROFIN
Page 274 and 275:
SFCs for Distributed I/Os or PROFIN
Page 276 and 277:
SFCs for Distributed I/Os or PROFIN
Page 278 and 279:
SFCs for Distributed I/Os or PROFIN
Page 280 and 281:
SFCs for Distributed I/Os or PROFIN
Page 282 and 283:
SFCs for Distributed I/Os or PROFIN
Page 284 and 285:
PROFInet Updating the PROFInet Inte
Page 286 and 287:
PROFInet 17.2 Updating the Inputs o
Page 288 and 289:
PROFInet 17.4 Updating DP Interconn
Page 290 and 291:
FBs for Cyclical Access to User Dat
Page 292 and 293:
FBs for Cyclical Access to User Dat
Page 294 and 295:
FBs for Cyclical Access to User Dat
Page 296 and 297:
FBs for Cyclical Access to User Dat
Page 298 and 299:
Safety Guidelines This manual conta
Page 300 and 301:
Contents 22.7 Aborting an Existing
Page 302 and 303:
Contents 31 Plastics Techology 31-3
Page 304 and 305:
Contents System Software for S7-300
Page 306 and 307:
SFCs for Global Data Communication
Page 308 and 309:
SFCs for Global Data Communication
Page 310 and 311:
SFCs for Global Data Communication
Page 312 and 313:
Overview over the S7 Communication
Page 314 and 315:
Overview over the S7 Communication
Page 316 and 317:
Overview over the S7 Communication
Page 318 and 319:
Overview over the S7 Communication
Page 320 and 321:
Overview over the S7 Communication
Page 322 and 323:
Overview over the S7 Communication
Page 324 and 325:
S7 Communication Addressing Paramet
Page 326 and 327:
S7 Communication Exact User Data Si
Page 328 and 329:
S7 Communication Warm Restart and C
Page 330 and 331:
S7 Communication Error Interface to
Page 332 and 333:
S7 Communication Parameter Declarat
Page 334 and 335:
S7 Communication 21.5 Uncoordinated
Page 336 and 337:
S7 Communication ERROR STATUS (Deci
Page 338 and 339:
S7 Communication Due to the asynchr
Page 340 and 341:
S7 Communication ERROR STATUS (Deci
Page 342 and 343:
S7 Communication Parameter Declarat
Page 344 and 345:
S7 Communication Data Consistency T
Page 346 and 347:
S7 Communication Parameter Declarat
Page 348 and 349:
S7 Communication 21.9 Read Data fro
Page 350 and 351:
S7 Communication ERROR STATUS (Deci
Page 352 and 353:
S7 Communication In_out Parameter F
Page 354 and 355:
S7 Communication Representation Pos
Page 356 and 357:
S7 Communication If you attempt to
Page 358 and 359:
S7 Communication 21.11 Initiating a
Page 360 and 361:
S7 Communication ERROR STATUS (Deci
Page 362 and 363:
S7 Communication Parameter Declarat
Page 364 and 365:
S7 Communication Error Information
Page 366 and 367:
S7 Communication In/Out Parameter L
Page 368 and 369:
S7 Communication In/Out Parameter L
Page 370 and 371:
S7 Communication Output Parameter I
Page 372 and 373:
S7 Communication Error Information
Page 374 and 375:
S7 Communication System Software fo
Page 376 and 377:
Communication SFCs for Non-Configur
Page 378 and 379:
Communication SFCs for Non-Configur
Page 380 and 381:
Communication SFCs for Non-Configur
Page 382 and 383:
Communication SFCs for Non-Configur
Page 384 and 385:
Communication SFCs for Non-Configur
Page 386 and 387:
Communication SFCs for Non-Configur
Page 388 and 389:
Communication SFCs for Non-Configur
Page 390 and 391:
Communication SFCs for Non-Configur
Page 392 and 393:
Communication SFCs for Non-Configur
Page 394 and 395:
Communication SFCs for Non-Configur
Page 396 and 397:
Communication SFCs for Non-Configur
Page 398 and 399:
Open Communication via Industrial E
Page 400 and 401:
Open Communication via Industrial E
Page 402 and 403:
Open Communication via Industrial E
Page 404 and 405:
Open Communication via Industrial E
Page 406 and 407:
Open Communication via Industrial E
Page 408 and 409:
Open Communication via Industrial E
Page 410 and 411:
Open Communication via Industrial E
Page 412 and 413:
Open Communication via Industrial E
Page 414 and 415:
Open Communication via Industrial E
Page 416 and 417:
Open Communication via Industrial E
Page 418 and 419:
Open Communication via Industrial E
Page 420 and 421:
Open Communication via Industrial E
Page 422 and 423:
Open Communication via Industrial E
Page 424 and 425:
Open Communication via Industrial E
Page 426 and 427:
Open Communication via Industrial E
Page 428 and 429:
Open Communication via Industrial E
Page 430 and 431:
Open Communication via Industrial E
Page 432 and 433:
Open Communication via Industrial E
Page 434 and 435:
Open Communication via Industrial E
Page 436 and 437:
Generating Block-Related Messages L
Page 438 and 439:
Generating Block-Related Messages A
Page 440 and 441:
Generating Block-Related Messages P
Page 442 and 443:
Generating Block-Related Messages P
Page 444 and 445:
Generating Block-Related Messages 2
Page 446 and 447:
Generating Block-Related Messages E
Page 448 and 449:
Generating Block-Related Messages P
Page 450 and 451:
Generating Block-Related Messages 2
Page 452 and 453:
Generating Block-Related Messages 2
Page 454 and 455:
Generating Block-Related Messages 2
Page 456 and 457:
Generating Block-Related Messages 2
Page 458 and 459:
Generating Block-Related Messages 2
Page 460 and 461:
Generating Block-Related Messages 2
Page 462 and 463:
Generating Block-Related Messages A
Page 464 and 465:
Generating Block-Related Messages A
Page 466 and 467:
Generating Block-Related Messages 2
Page 468 and 469:
Generating Block-Related Messages P
Page 470 and 471:
Generating Block-Related Messages 2
Page 472 and 473:
Generating Block-Related Messages P
Page 474 and 475:
Generating Block-Related Messages E
Page 476 and 477:
IEC Timers and IEC Counters Paramet
Page 478 and 479:
IEC Timers and IEC Counters 25.3 Ge
Page 480 and 481:
IEC Timers and IEC Counters 25.5 Co
Page 482 and 483:
IEC Timers and IEC Counters The ope
Page 484 and 485:
IEC Functions Name IEC Block Family
Page 486 and 487:
IEC Functions FC No. Name Size (No.
Page 488 and 489:
IEC Functions 26.4 Time-of-Day Func
Page 490 and 491:
IEC Functions Description FC8 DT_TO
Page 492 and 493:
IEC Functions 26.5 Comparing DATE_A
Page 494 and 495:
IEC Functions Description FC23 LT_D
Page 496 and 497:
IEC Functions Description FC15 GT_S
Page 498 and 499:
IEC Functions 26.7 Editing Number V
Page 500 and 501:
IEC Functions 26.9 Example in STL C
Page 502 and 503:
IEC Functions Description FC11 FIND
Page 504 and 505:
IEC Functions Description FC26 MID
Page 506 and 507:
IEC Functions 26.11 Converting Data
Page 508 and 509:
IEC Functions Description FC38 STRN
Page 510 and 511:
SFBs for Integrated Control Descrip
Page 512 and 513:
SFBs for Integrated Control CONT_C
Page 514 and 515:
SFBs for Integrated Control Paramet
Page 516 and 517:
SFBs for Integrated Control Output
Page 518 and 519:
SFBs for Integrated Control Descrip
Page 520 and 521:
SFBs for Integrated Control Input P
Page 522 and 523:
SFBs for Integrated Control Output
Page 524 and 525:
SFBs for Integrated Control Descrip
Page 526 and 527:
SFBs for Integrated Control CYCLE o
Page 528 and 529:
SFBs for Integrated Control The dur
Page 530 and 531:
SFBs for Integrated Control Two-Ste
Page 532 and 533:
SFBs for Integrated Control Input P
Page 534 and 535:
SFBs for Integrated Control 27.4 Ex
Page 536 and 537:
SFBs for Integrated Control STL Pro
Page 538 and 539:
SFBs for Compact CPUs Parameter Dec
Page 540 and 541:
SFBs for Compact CPUs Parameters no
Page 542 and 543:
SFBs for Compact CPUs Parameters fo
Page 544 and 545:
SFBs for Compact CPUs Parameters fo
Page 546 and 547:
SFBs for Compact CPUs Parameters fo
Page 548 and 549:
SFBs for Compact CPUs Event class E
Page 550 and 551:
SFBs for Compact CPUs 28.2 Position
Page 552 and 553:
SFBs for Compact CPUs Parameter Dec
Page 554 and 555:
SFBs for Compact CPUs Parameter Dec
Page 556 and 557:
SFBs for Compact CPUs Parameters fo
Page 558 and 559:
SFBs for Compact CPUs Parameters fo
Page 560 and 561:
SFBs for Compact CPUs Event class E
Page 562 and 563:
SFBs for Compact CPUs 28.3 Controll
Page 564 and 565:
SFBs for Compact CPUs Parameter Dec
Page 566 and 567:
SFBs for Compact CPUs Parameter Dec
Page 568 and 569:
SFBs for Compact CPUs 28.4 Controll
Page 570 and 571:
SFBs for Compact CPUs Parameter Dec
Page 572 and 573:
SFBs for Compact CPUs Job Error Eve
Page 574 and 575:
SFBs for Compact CPUs Parameter Dec
Page 576 and 577:
SFBs for Compact CPUs 28.6 Sending
Page 578 and 579:
SFBs for Compact CPUs Parameters De
Page 580 and 581:
SFBs for Compact CPUs Parameters Pa
Page 582 and 583:
SFBs for Compact CPUs 28.8 Deleting
Page 584 and 585:
SFBs for Compact CPUs 28.9 Sending
Page 586 and 587:
SFBs for Compact CPUs Parameters De
Page 588 and 589:
SFBs for Compact CPUs 28.10 Fetchin
Page 590 and 591:
SFBs for Compact CPUs Parameters De
Page 592 and 593:
SFBs for Compact CPUs Parameter in
Page 594 and 595:
SFBs for Compact CPUs 28.11 Receivi
Page 596 and 597:
SFBs for Compact CPUs Example: SEND
Page 598 and 599:
SFBs for Compact CPUs Parameters De
Page 600 and 601:
SFBs for Compact CPUs 28.12 Additio
Page 602 and 603:
SFBs for Compact CPUs Error in the
Page 604 and 605:
SFBs for Compact CPUs Error in the
Page 606 and 607:
SFBs for Compact CPUs Error in the
Page 608 and 609:
SFCs for H CPUs Job The following t
Page 610 and 611:
SFCs for H CPUs Example of Using SF
Page 612 and 613:
Integrated Functions (for CPUs with
Page 614 and 615:
Integrated Functions (for CPUs with
Page 616 and 617:
Integrated Functions (for CPUs with
Page 618 and 619:
Plastics Techology System Software
Page 620 and 621:
Diagnostic Data 32.2 Diagnostic Dat
Page 622 and 623:
Diagnostic Data 32.3 Structure of C
Page 624 and 625:
Diagnostic Data System Software for
Page 626 and 627:
System Status Lists (SSL) Module St
Page 628 and 629:
System Status Lists (SSL) 33.3 SSL-
Page 630 and 631:
System Status Lists (SSL) 33.5 SSL-
Page 632 and 633:
System Status Lists (SSL) Character
Page 634 and 635:
System Status Lists (SSL) 33.7 SSL-
Page 636 and 637:
System Status Lists (SSL) Name Leng
Page 638 and 639:
System Status Lists (SSL) 33.10 SSL
Page 640 and 641:
System Status Lists (SSL) 33.11 SSL
Page 642 and 643:
System Status Lists (SSL) • INDEX
Page 644 and 645:
System Status Lists (SSL) • INDEX
Page 646 and 647:
System Status Lists (SSL) Data Reco
Page 648 and 649:
System Status Lists (SSL) Data Reco
Page 650 and 651: System Status Lists (SSL) 33.14 SSL
Page 652 and 653: System Status Lists (SSL) 33.16 Dat
Page 654 and 655: System Status Lists (SSL) 33.17 Dat
Page 656 and 657: System Status Lists (SSL) 33.19 Dat
Page 658 and 659: System Status Lists (SSL) Data Reco
Page 660 and 661: System Status Lists (SSL) 33.21 SSL
Page 662 and 663: System Status Lists (SSL) Contents
Page 664 and 665: System Status Lists (SSL) Data Reco
Page 666 and 667: System Status Lists (SSL) Name Leng
Page 668 and 669: System Status Lists (SSL) Data Reco
Page 670 and 671: System Status Lists (SSL) Contents
Page 672 and 673: System Status Lists (SSL) Name Leng
Page 674 and 675: System Status Lists (SSL) Parameter
Page 676 and 677: System Status Lists (SSL) Header Th
Page 678 and 679: System Status Lists (SSL) Contents
Page 680 and 681: System Status Lists (SSL) Data Reco
Page 682 and 683: System Status Lists (SSL) Data reco
Page 684 and 685: System Status Lists (SSL) Data Reco
Page 686 and 687: System Status Lists (SSL) 33.30 SSL
Page 688 and 689: System Status Lists (SSL) Name Leng
Page 690 and 691: System Status Lists (SSL) 33.33 SSL
Page 692 and 693: System Status Lists (SSL) System So
Page 694 and 695: Events Identifier The identifier is
Page 696 and 697: Events 34.3 Event Class 2 — Synchro
Page 698 and 699: Events Event ID Event OB W#16#3961
Page 702 and 703: Events Event ID Event W#16#43B0 Fir
Page 704 and 705: Events 34.7 Event Class 6 — Communi
Page 706 and 707: Events Event ID Event OB W#16#75DF/
Page 708 and 709: Events Event ID Event Module type W
Page 710 and 711: Events Event ID Event W#16#9×53 Low
Page 712 and 713: Events System Software for S7-300/4
Page 714 and 715: List of SFCs, and SFBs No. Short Na
Page 716 and 717: List of SFCs, and SFBs 35.2 List of
Page 718 and 719: List of SFCs, and SFBs Short Name N
Page 720 and 721: List of SFCs, and SFBs No. Short Na
Page 722 and 723: List of SFCs, and SFBs Short Name N
Page 724 and 725: Bibliography System Software for S7
Page 726 and 727: Glossary Blending Control Blending
Page 728 and 729: Glossary Continuous Controller Cont
Page 730 and 731: Glossary Error, Synchronous Error,
Page 732 and 733: Glossary Logic Block Message In SIM
Page 734 and 735: Glossary Parameter, Dynamic Paramet
Page 736 and 737: Glossary Ratio Control • Single l
Page 738 and 739: Glossary Statement List STEP 7 The
Page 740 and 741: Glossary User Program User Program
Page 742 and 743: Index Changing the CPU to STOP with
Page 744 and 745: Index DPNRM_DG:………………..
Page 746 and 747: Index GT_DT……………………
Page 748 and 749: Index Processing Interrupt OB (OB 8
Page 750 and 751:
Index with SFC 51 RDSYSST ………
Page 752 and 753:
Index SFB DIGITAL………………
Page 754 and 755:
Index Clock:…………………..
Page 756:
Index System Software for S7-300/40

Источник

Читайте также: