Difference between revisions of "MC-Basic:WDCYCLE"
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Languages|MC-Basic:WDCYCLE}} | ||
{{MC-Basic | {{MC-Basic | ||
|SHORT FORM= | |SHORT FORM= | ||
| Line 39: | Line 40: | ||
* [[MC-Basic:WDINIT|WDINIT]] | * [[MC-Basic:WDINIT|WDINIT]] | ||
| − | [[Category | + | [[Category:Obsolete|WDCYCLE]] |
}} | }} | ||
Latest revision as of 16:24, 2 May 2017
| Language: | English • 中文（简体） |
|---|
Once a task has been attached to the watch dog mechanism (with the WDINIT), the watch dog must be serviced using WDCYCLE. The watch dog begins to Terminal the task after it is serviced for the first time. Thereafter, WDCYCLE is issued periodically, within the specified cycle time. Otherwise, a Watch Dog fault is generated (1006: “Task Stuck”).
Syntax
WDCycle(<watch dog variable>)
Availability
All versions
Type
<watch dog variable>: Long
Range
The value of the variable is given by WDINIT.
Scope
Task or Terminal
Limitations
- Write only
- Not supported in EtherCAT system
Examples
WdCycle(MyVar) ‘service the watch dog