Danfoss MCO 305 Design Manual page 110

MCO 305 Design Guide
Command Group
Cross Reference
Syntax Examples
110
__ Software Reference __
Interrupt handling within an Interrupt
During the execution of an interrupt subroutine at first a DISABLE ALL will
automatically be done internally. This blocks the execution of all other interrupts,
but keeps upcoming interrupt requests still in mind. At the end of the 'current'
interrupt subroutine an ENABLE ALL will be again executed automatically. With the
completion of the 'current' interrupt the upcoming stored interrupts will be executed
yet. Therefore the execution of the commands DISABLE ALL and ENABLE ALL within
an interrupt is not necessary and not meaningful, too.
The selective blocking of single interrupts within an interrupt subroutine can be
necessary, depending on the application. Think of the following example: If the
execution of an interrupt should lock the request and execution of other interrupt
types, a selective DISABLE (e.g. DISABLE INT) can be done. In this case the
selective interrupt blockage must be cleared (e.g. ENABLE INT) by the application
program later on again. Typically this is done at the end of the current interrupt
subroutine and enables the execution of corresponding interrupt requests in future
again. All edge triggered interrupts, which were received between the correspon-
ding selective DISABLE and ENABLE, will be ignored and not executed any longer
(nor later). All interrupts, which were received before the selective blocking (e.g.
DISABLE INT) or after the new selective release (e.g. ENABLE INT) will be
processed after the completion of the "first" interrupt.
INT
ON INT, ON COMBIT, ON STATBIT, ON PARAM, ON PERIOD, ON TIME, ENABLE ..
Interrupts
DISABLE ALL /* Switch off all interrupts */
DISABLE STATBIT /* Switch off the interrupt for the status bit */
®
MG.33.L4.02 – VLT is a registered Danfoss trademark