Program processing and
system time
03/05 AWB2724-1453GB
34
Interrupt processing
In the XC100 it is possible to program and parameterize up to
seven 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 44 are available:
If an interrupt occurs, the runtime module executes the program
organisational unit (POU) which is linked to the interrupt source.
Execution of the POU is time-monitored. The parameterized cycle
time is used for this cycle time. The interrupts are enabled when
changed to the RUN state and inhibited when changed to the
STOP state. Interrupt sources which are not enabled in the
configuration do not initiate an interrupt. If a POU is not assigned
to an enabled interrupt source, the interrupt is recognised and
executed but without running a POU.
Frequent occurrence of an interrupt during a cycle can cause the
cycle time to time-out and result in a reset being initiated by the
Watchdog.
User interrupts can be inhibited and re-enabled from the program.
The “DisableInterrupt” and “EnableInterrupt” functions are
provided for this purpose. A call parameter in the XSoft determines
if an individual interrupt or all interrupts are enabled or inhibited.
Enabling of an inhibited interrupt must be performed with the
same parameter used to inhibit it.
Both the “DisableInterrupt” and “EnableInterrupt” functions are
components of the “XC100_Util.lib” library. This library must – if
not already done so – be integrated into the library manager of the
XSoft.
Figure 44: User events
To Next Page
Loading...
Need help?
General
