Danfoss MCO 305 Design Manual page 109

MCO 305 Design Guide
DISABLE ... interrupts
Summary
Syntax
Parameter
Description
__ Software Reference __
Locks the execution of interrupts.
DISABLE inttyp
NB!:
DISABLE cannot be called up during interrupt procedures. (The system
automatically switches back to enabled after an interrupt.)
inttyp = ALL
INT
COMBIT
STATBIT
NB!:
The execution of error handling ON ERROR can not be locked with DISABLE. The
error interrupt has the highest priority and it also interrupts other active interrupts.
DISABLE switches off all or explicitly specified interrupts – apart from ON ERROR.
If the function DISABLE ... is used in the main program, it can prevent interrupts of
the corresponding type.
This is particularly useful if a variable, which is set in an interrupt procedure, is
used in the main program. To do this you should first switch off the corresponding
(or all) interrupts in the main program DISABLE ... alter the variable and then
switch the corresponding (or all) interrupts back on with ENABLE ...
NB!:
If an interrupt is disabled it still exist, but is not processed anymore (Exception:
DISABLE ALL).
The detection is still running in the background and the interrupt is captured in
case of a non (!) edge-sensitive or a message-oriented interrupt (ON PERIOD, ON
APOS, ON PARAM etc.). If the interrupt is ENABLEd again and there was a captured
(non edge-sensitive) interrupt before, this interrupt is processed immediately.
In case of edge-sensitive interrupts (e.g. ON INT, ON COMBIT, ON STATBIT), all
interrupts, which take place during the DISABLEd phase are not processed, even
not after switching on ENABLE again. These interrupts have no memory in case of
DISABLEd state. Edge-sensitive interrupts which take place after the anew
ENABLEing are still processed again.
NB!:
Exception: DISABLE ALL
In opposite to the selective disabling of edge-sensitive interrupts (e.g. DISABLE
INT) – these will be ignored and not executed after enabling – in case of DISABLE
ALL the request is stored (edge-sensitive interrupts too) and the interrupt are still
executed after enabling (ENABLE ALL)!
DISABLE ALL in combination with selective DISABLE
Please note, that an ENABLE ALL has no impact on simultaneous valid blockings
defined by selective DISABLE commands (e.g. DISABLE INT). Thus a selective
blocking must also be cleared by the corresponding selective ENABLE!
®
MG.33.L4.02 – VLT is a registered Danfoss trademark
PARAM
PERIOD
TIME
POSINT
109