Variable Type Description
OB35_OB_NUMBR BYTE OB number (28, 29, 32 ... 35)
OB35_RESERVED_1 BYTE reserved
OB35_RESERVED_2 BYTE reserved
OB35_PHASE_OFFSET WORD Phase offset in ms
OB35_RESERVED_3 INT reserved
OB35_EXC_FREQ INT Interval in ms
OB35_DATE_TIME DATE_AND_TIME Date and time of day when the OB was called
Information to access the local data can be found at the description of the OB 1.
Since the blocks SFC58/59 respectively SFB52/53 for reading and writing
data blocks cannot be interrupted, in conjunction with OB 28 and OB 29
the CPU may change to STOP state!
6.8 Hardware Interrupts
6.8.1 OB 40, OB 41 - HW_INTx - Hardware Interrupt
Hardware interrupts are used to enable the immediate detection in the user program of
events in the controlled process, making it possible to respond with an appropriate inter-
rupt handling routine. Here OB 40 and OB 41 can be used. Within the configuration you
specify for each module, which channels release a hardware interrupt during which condi-
tions. With the system functions SFC 55 WR_PARM, SFC 56 WR_DPARM and SFC 57
PARM_MOD you can (re)parameterize the modules with hardware interrupt capability
even in RUN.
Ä
Chap. 14.1.43 ‘SFC 55 - WR_PARM - Write dynamic parameter’
page 692
Ä
Chap. 14.1.44 ‘SFC 56 - WR_DPARM - Write default parameter’
page 694
Ä
Chap. 14.1.45 ‘SFC 57 - PARM_MOD - Parameterize module’ page 696
The hardware interrupt processing of the CPU is always active. So that a module can
release a hardware interrupt, you have to activate the hardware interrupt on the appro-
priate module by a hardware configuration. Here you can specify whether the hardware
interrupt should be generated for a coming event, a leaving event or both.
Description
Activation
VIPA SPEED7
Organization Blocks
Hardware Interrupts > OB 40, OB 41 - HW_INTx - Hardware Interrupt
HB00 | OPL_SP7 | Operation list | en | 18-30 82
To Next Page
Loading...
