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

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?

How can you recognize whether an I/O access error occurs several times from the error code in the OB122?

Part number:

Description:
The evaluation of I/O access errors has been changed in the SIMATIC S7-400 series CPU generation. Now, no difference is made with regard to the memory area (I/O area / process image). This also means that it is now no longer possible to have information about I/O access errors that occur multiple times (error codes B#16#44 and B#16#45).
All I/O access errors are imaged on error codes B#16#42 and B#16#43. It is therefore no longer possible to count the number of I/O access errors based on the error code in OB 122.

The change is valid for the following releases and higher:

CPU 412

- 1XF03

- 2XG00

CPU 414

- 2XG03

- 3XJ00

CPU 416

- 2XK02

- 3XL00

CPU 417

- 4XL00

- 4HL00

Entry ID:5708202

Date:2000-12-01

I regard this article....

as helpful

as not helpful

Copy link

Suggestion for the entry

Send to a friend