Siemens CM343 Series Manual de servicio Pagina 105

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 140
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 104
6 Diagnostics and Interrrupts of the CP 343-2
105
CP 343−2 / CP 343−2 P AS−Interface Master
Release 08/2008
C79000−G8976−C149−04
S All changes to the AS-i slave configuration in the protected mode
S AS-i Power Fail in the protected mode
CP-internal interrupt events:
S EEPROM Error
Note
CP-internal interrupt events are always events entering the state. After a
CP-internal interrupt event occurs, the group error bit remains = TRUE. This is
only reset again after a restart on the S7-300.
6.3 Sequence of Diagnostic Interrupt Processing
If the CP 343-2 detects an interrupt event, it triggers a diagnostic interrupt. The
PLC CPU finds the source of the interrupt and reads data record 0 from the CP. It
then interrupts the cyclic user program and behaves as follows:
S If OB82 is not programmed, the PLC CPU changes to STOP as the default
reaction.
S If organization block OB82 his programmed, this is started. DS 0 is available in
the local data bytes 8 to 11 in the local data area of OB82. It is possible (but not
necessary) to read DS 1 that contains the delta list in OB82 using an SFC call
(SFC 51 “RDSYSST” or SFC 59 ”RD_REC”). When OB has been executed, the
PLC CPU acknowledges the diagnostic interrupt on the CP 342-2.
If interrupt events occur in a status in which they cannot be signaled by triggering a
diagnostic interrupt (for example, when the PLC is in the STOP mode or when an
older diagnostic interrupt is not yet been acknowledged), the CP 343-2 behaves as
follows:
S As soon as it becomes possible to trigger a diagnostic interrupt again, and if the
total CP configuration (in other words, AS-i slave configuration and CP-internal,
interrupt-relevant state) at this point in time is not the same as the configuration
signaled earlier with the diagnostic interrupt, a diagnostic interrupt with the
current configuration information is triggered.
S When it becomes possible again to trigger a diagnostic interrupt and if the total
CP configuration is the same as signaled earlier with the diagnostic interrupt, no
diagnostic interrupt is triggered. This means that brief slave failures (for
example, a bad contact) can go unnoticed.
CP-external interrupt events:
Vista de pagina 104
1 2 ... 100 101 102 103 104 105 106 107 108 109 110 ... 139 140

Comentarios a estos manuales

Sin comentarios