Siemens Industry Online Support - Automation Service, Automation Support, Simatic Service, Simatic Support, Technical Support, Technical Consulting

S7-300 CPU 31x -- Operation and maintenance -- Diagnosing errors

	When the CPU starts up how can you identify a previous stop event and process it in the program (even after an overall reset)?
	Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails?
	What should you do upon display of the error message 33:8580 "MMC defective"
	With MMC (Micro Memory Card) slotted, why does the STOP LED blink on the SIMATIC S7-300 CPU?
	Which organization blocks do you need for error handling?
	How do you find out the status of the stations of a DP master system or of a PROFINET IO system?
	Why are devices not correctly displayed in the topology view of the web server?
	Capturing module and diagnostics data of the automation system
	CPU switches to STOP when a PG/PC goes online via PROFIBUS
	How do you get an overview of the SIMATIC automation system and what solutions are there for undesired operating states?
	What do you have to do if the SIMATIC S7-300 CPU no longer goes into RUN mode after adding a CP or FM module?
	Why does the EXTF LED light continuously on a CPU 300 (V1.0.0)/CPU 400 (V1.1.0) after occurrence of a diagnostics alarm?
	Which information is entered in the diagnostic buffer of the SIMATIC S7 CPU in STEP 7 V5.x?
	Memory reset request by the CPU
	Why does the "SF DP" LED light on the CPU 315-2 DP (6ES7 315-2AF0x-0AB0; x = 0,1,2) although no DP configuration has been loaded into the CPU?
	Why does the CPU remain in STOP after voltage recovery following complete loss of voltage for the entire system?
	Why does the LED BF2 light with PROFINET CPUs S7-315/317-2PN/DP V2.3 even though no bus fault can be determined?
	Why does my SIMATIC S7-300 CPU go into STOP with error 16#4548 "Stop by I/O administration"?
	How can you avoid diagnostics problems when implementing dummy module DM 370?

S7-400 CPU 41x -- Operation and maintenance -- Diagnosing errors

	Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails?
	How can you recognize whether an I/O access error occurs several times from the error code in the OB122?
	Battery error with the S7-400: OB81 is not called
	Which organization blocks do you need for error handling?
	How do you find out the status of the stations of a DP master system or of a PROFINET IO system?
	Capturing module and diagnostics data of the automation system
	CPU switches to STOP when a PG/PC goes online via PROFIBUS
	Why after power off/on or after return of a DP standard slave does the EXTF LED on the CPU 300/400 remain on and doesn't go out?
	When the CPU starts up how can you identify a previous stop event and process it in the program (even after an overall reset)?
	Why won't the IM and/or the CP with a CPU S7-400 go into RUN mode when the event ID 530D appears in the diagnostics buffer?
	Why does the CPU remain in STOP after voltage recovery following complete loss of voltage for the entire system?
	What should you watch out for when using the blocks SFC 17 "ALARM_SQ", SFC 18 "ALARM_S", SFC 107 "ALARM_DQ" and SFC 108 "ALARM_D"?
	What should you watch out for when you use the SFC20 "BLKMOV", SFC81 "UBLKMOV" or SFC21 "FILL" blocks?

Capturing module and diagnostics data of the automation system

Part number:

Contents
When using a PLC, you often need information during operation about events and their causes.
These instructions show how you can read out module and diagnostics data from the SIMATIC controllers S7-300 and S7-400.

Instuctions (PDF) ( 1572 KB )

Keywords:
Plant state, Diagnostics buffer, Diagnostics messages, Diagnostics data, Event entries, Events, Module data, Release

Entry ID:29801480

Date:2008-12-15

I regard this article....

as helpful

as not helpful

Copy link

Suggestion for the entry

Send to a friend