Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:sw:01-mervis:task-definition-hidden [2024/04/23 14:32] – [Task types] avsetulaen:sw:01-mervis:task-definition-hidden [2024/04/23 15:07] (current) – [Task categories] avsetula
Line 63: Line 63:
 <WRAP center round info 90%> <WRAP center round info 90%>
 Mervis IDE allows you to create multiple NormalOperationTask categories, provided that the first one is of the Freewheeling type, or Cyclic and the other tasks in this category will be of type Event only. The task types are described in detail [[#tasks_types|below]]. Mervis IDE allows you to create multiple NormalOperationTask categories, provided that the first one is of the Freewheeling type, or Cyclic and the other tasks in this category will be of type Event only. The task types are described in detail [[#tasks_types|below]].
 +</WRAP>
 +
 +<WRAP center round important 90%>
 +If running the program continuously is a higher priority than running without errors and logging them, it is possible to disable the **Stop on Exception** option in the controller properties and never run a job of type ExecutionError:
 +
 +{{.:task-definition:stop-on-except.png?direct|}}
 </WRAP> </WRAP>
  
Line 126: Line 132:
  
 <WRAP center round important 90%> <WRAP center round important 90%>
-To run a task of the event type, it is necessary to select as the trigger variable a variable that is used in the main program. To use a variable in FBD, just connect it to itself:+To run a task of the event type, it is necessary to select as the trigger variable a variable that is used in the main program. To use a variable in FBD, just connect it to itself: 
  
 {{ :cs:sw:01-mervis:advanced-task-definition:commerrror-fix.png?direct |}} {{ :cs:sw:01-mervis:advanced-task-definition:commerrror-fix.png?direct |}}
  
-The same rule applies to commerror and other attributes.+The same rule applies to commerror and other attributes. 
 </WRAP> </WRAP>
  
Line 160: Line 166:
 <html><span class="kbBlueText">1. Example of a safe condition of the device "Sawmill"</span></html> <html><span class="kbBlueText">1. Example of a safe condition of the device "Sawmill"</span></html>
  
-The device operating the saw. When a program error occurs, the **NormalOperation** task is stopped and the **ExecutionError** task is started, which stops the saw blade and feed. This error condition treatment avoids potential injury to workers or saw damage.+The device operating the saw. When a program error occurs, the **NormalOperation** task is stopped and the **ExecutionError** task is started, which stops the saw blade and feeder. This error condition treatment avoids potential injury to workers or saw damage.
  
 <html><span class="kbBlueText">2. Example of a safe condition of the equipment "Cement Plant"</span></html> <html><span class="kbBlueText">2. Example of a safe condition of the equipment "Cement Plant"</span></html>
  
-Equipment operating a filler in a cement plant. When a program error occurs, the **NormalOperation** task stops and the **ExecutionError** task starts, which closes the bin flaps. This error condition treatment avoids unnecessary material loss.+A machine operating a filler in a cement plant. When a program error occurs, the **NormalOperation** task stops and the **ExecutionError** task starts, which closes the hopper flaps. This error condition treatment avoids unnecessary material loss.