The following table describes the start information of the OB 40 and OB 41 with defaultnames of the variables and its data types:Variable Type DescriptionOB40_EV_CLASS BYTE Event class and identifiers:11h: Interrupt is activeOB40_STRT_INF BYTE 41h: Interrupt via Interrupt line 1OB40_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 reservedOB40_IO_FLAG BYTE Input Module: 54hOutput Module: 55hOB40_MDL_ADDR WORD Logical base address of the module that triggers the inter-ruptOB40_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 hasexceeded 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 calledInformation to access the local data can be found at the description of the OB 1.6.9 Asynchronous error Interrupts6.9.1 OB 80 - CYCL_FLT - Time ErrorThe operating system of the CPU calls OB 80 whenever an error occurs like:n Cycle monitoring time exceededn OB request error i.e. the requested OB is still executed or an OB was requested toofrequently within a given priority class.n Time-of-day interrupt error i.e. interrupt time past because clock was set forward orafter transition to RUN.The time error OB can be blocked, respectively delayed and released by means of SFC39 ... 42.If OB 80 has not been programmed, the CPU changes to the STOPmode. If OB 80 is called twice during the same scan cycle due to thescan time being exceeded, the CPU changes to the STOP mode. Youcan prevent this by calling SFC 43 RE_TRIGR at a suitable point in theprogram.Local dataDescriptionVIPA SPEED7Organization BlocksAsynchronous error Interrupts > OB 80 - CYCL_FLT - Time ErrorHB00 | OPL_SP7 | Operation list | en | 18-3084
