The following table describes the start information of the OB 40 and OB 41 with default
names of the variables and its data types:
Variable Type Description
OB40_EV_CLASS BYTE Event class and identifiers:
11h: Interrupt is active
OB40_STRT_INF BYTE 41h: Interrupt via Interrupt line 1
OB40_PRIORITY BYTE Assigned priority class:
Default: 16 (OB 40)
Default: 17 (OB 41)
OB40_OB_NUMBR BYTE OB number (40, 41)
OB40_RESERVED_1 BYTE reserved
OB40_IO_FLAG BYTE Input Module: 54h
Output Module: 55h
OB40_MDL_ADDR WORD Logical base address of the module that triggers the inter-
rupt
OB40_POINT_ADDR DWORD
n For digital modules
– Bit field with the states of the inputs on the module
(bit 0 corresponds to the first input).
n For analog modules
– Bit field with information which channel has
exceeded which limit.
n For CPs or IMs
– Informs about the module interrupt status.
OB40_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.
6.9 Asynchronous error Interrupts
6.9.1 OB 80 - CYCL_FLT - Time Error
The operating system of the CPU calls OB 80 whenever an error occurs like:
n Cycle monitoring time exceeded
n OB request error i.e. the requested OB is still executed or an OB was requested too
frequently within a given priority class.
n Time-of-day interrupt error i.e. interrupt time past because clock was set forward or
after transition to RUN.
The time error OB can be blocked, respectively delayed and released by means of SFC
39 ... 42.
If OB 80 has not been programmed, the CPU changes to the STOP
mode. If OB 80 is called twice during the same scan cycle due to the
scan time being exceeded, the CPU changes to the STOP mode. You
can prevent this by calling SFC 43 RE_TRIGR at a suitable point in the
program.
Local data
Description
VIPA SPEED7
Organization Blocks
Asynchronous error Interrupts > OB 80 - CYCL_FLT - Time Error
HB00 | OPL_SP7 | Operation list | en | 18-30 84
To Next Page
Loading...
