show the entry list
STEP 7 -- Setting up and parameterizing hardware -- Configuring Hardware
How do you update the STEP 7 hardware catalog in STEP 7 V5.2 onwards?
How can you update the hardware catalog without direct internet access?
What can you do if required modules are missing in the module catalog of the STEP 7 hardware configuration?
Inconsistent system data when removing a PROFIBUS DP master system from the network
Establishing an online connection to an S7-300/S7-400 CPU through several Ethernet interfaces
How can you set or change the resolution of the analog module SM331 (6ES7331-7K..)?
How do you parameterize the communication resources of S7-300 CPUs so that WinCC stations and S7-300 stations do not have connection failures?
Information on the topic of "Initializing and parameterizing modules"
Why is OB82 no longer called in an S7-300 DP CPU module whenever the diagnostic interrupt is called in the CPU's STOP mode?
How can you activate the protection level with a password in the HW Config for an S7 CPU?
How can you modify the data that was configured with STEP 7 "HW Config" for the time-of-day interrupt in the user program?
Why is OB82 no longer called in an S7-300 DP CPU module whenever the diagnostic interrupt is called in the CPU's STOP mode?
Part number:

Description
OB 82 is called by the CPU's operating system whenever

  • The diagnostic interrupt has been enabled in a diagnostics-compatible module.
  • The diagnostics-compatible module recognizes a change in the diagnostics state.
  • The diagnostics-compatible module issues a diagnostics request to the CPU.
  • And the CPU is in RUN mode.

If OB 82 is not programmed, the CPU goes into STOP mode.

With DPV1-integration in the S7-300 CPU-DP modules (CPU 31xC / 31x from V2.0.0, CPU 318 2DP from V3.0.0), the processing and acknowledgement of the interrupts in CPU STOP mode is changed in accordance with the DPV1 standard.

When DPV1 is integrated, the diagnostic interrupts are acknowledged when the CPU is in STOP mode and, wherever this is the case, lead to a corresponding entry in the diagnostic buffer.

  • This also applies to interrupts that are reported in the STOP mode of the CPU.
  • However, no OB82 call occurs because the CPU is in STOP mode.
  • A diagnostic interrupt which is received in STOP mode is not executed subsequently if the CPU is in RUN mode again.

Whether or not a slave reports interrupts to the master CPU when it is in STOP mode depends on the slave. Users can ascertain the status of the distributed modules for themselves by outputting relevant system status list IDs (e.g. 0x692) with SFC51.

Note
A description of system function SFC51 is available in the manual in Entry ID: 44240604 or in the Online Help of STEP 7 (select block and press "F1").

 

 Entry ID:18458895   Date:2011-07-11 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour