Variable Type DescriptionOB35_OB_NUMBR BYTE OB number (28, 29, 32 ... 35)OB35_RESERVED_1 BYTE reservedOB35_RESERVED_2 BYTE reservedOB35_PHASE_OFFSET WORD Phase offset in msOB35_RESERVED_3 INT reservedOB35_EXC_FREQ INT Interval in msOB35_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.Since the blocks SFC58/59 respectively SFB52/53 for reading and writingdata blocks cannot be interrupted, in conjunction with OB 28 and OB 29the CPU may change to STOP state!6.8 Hardware Interrupts6.8.1 OB 40, OB 41 - HW_INTx - Hardware InterruptHardware interrupts are used to enable the immediate detection in the user program ofevents 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 youspecify 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 57PARM_MOD you can (re)parameterize the modules with hardware interrupt capabilityeven 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 696The hardware interrupt processing of the CPU is always active. So that a module canrelease 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 hardwareinterrupt should be generated for a coming event, a leaving event or both.DescriptionActivationVIPA SPEED7Organization BlocksHardware Interrupts > OB 40, OB 41 - HW_INTx - Hardware InterruptHB00 | OPL_SP7 | Operation list | en | 18-3082
