Can anybody give me an explanation of how monitor statements work and maybe an example of how they have used them? PalletTool uses them alot and I would like to understand them before I monitor them.
Monitor statements.
-
MooseHorns -
February 9, 2019 at 12:27 AM -
Thread is Resolved
-
-
If you have access to a manual, look up condition monitor.
A monitor is a program that waits for a condition to happen, then calls an action program. For example,
ConditionProgram:
when DI[1] = on, call ActionProgramActionProgram:
UALM[1]
DO[3]=on
Monitor ConditionProgramThen in your main program you can use the monitor statement to start a program monitor.
The monitor runs in the background and just contains "when" statements. The action program is called when that event happens. Action programs cannot contain motion (there is a special workaround).
There are 2 types, system monitor and program monitor.
In my opinion BGlogic is the better method for event based programming.
Sent from my SM-G930V using Tapatalk