Eaton XC-CPU101 Series Instruction Leaflet

Contents

Program processing andsystem time12/14 MN05003004Z-EN34Interrupt processingIn the XC100 it is possible to program and parameterize up toseven interrupt events. Interrupts can be activated by:• physical inputs I0.0 to I0.3 of the XC-CPU101• XIOC signal modules with interrupt features• TIMER_Interrupt.The interrupt events listed in figure 45 are available:If an interrupt occurs, the runtime module executes the programorganisational unit (POU) which is linked to the interrupt source.Execution of the POU is time-monitored. The parameterized cycletime is used for this cycle time. The interrupts are enabled whenchanged to the RUN state and inhibited when changed to theSTOP state. Interrupt sources which are not enabled in theconfiguration do not initiate an interrupt. If a POU is not assignedto an enabled interrupt source, the interrupt is recognised andexecuted but without running a POU.Frequent occurrence of an interrupt during a cycle can cause thecycle time to time-out and result in a reset being initiated by theWatchdog.User interrupts can be inhibited and re-enabled from the program.The functions “DisableInterrup” and “EnableInterrupt” areprovided for this purpose. A call parameter in the easySoftCoDeSys determines if an individual interrupt or all interrupts areenabled or inhibited. Enabling of an inhibited interrupt must beperformed with the same parameter used to inhibit it.Both the “DisableInterrupt” and “EnableInterrupt” functions arecomponents of the “XC100_Util.lib” library. This library must – ifnot already done so – be integrated into the library manager of theeasySoft CoDeSys.Interrupt prioritisingIn task configuration you can assign a physical interrupt input I0.0,I0.1, I0.2 or I0.3 to an interuppt channel. Three channels areavailable. Channels 1 to 3 have a high priority, channels 4 to 6have a low priority.Lower priority interrupts can be interrupted by those with higherpriority.Figure 45: User events