Difference between revisions of "AXY:Note in case of spontaneous disable of drive/axis"
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Issue related to: | + | <!-- Issue related to: {{Bugzilla|3930}} --> |
| − | This is | + | |
| + | This is implemented from version 4.5.19 and later | ||
The check which detects entering into following mode. | The check which detects entering into following mode. | ||
| Line 38: | Line 39: | ||
| − | [[Category | + | [[Category:Motion Control]] |
| + | |||
--[[User:Miborich|Mirko]] 10:41, 15 November 2010 (CET) | --[[User:Miborich|Mirko]] 10:41, 15 November 2010 (CET) | ||
Latest revision as of 09:19, 22 May 2014
This is implemented from version 4.5.19 and later
The check which detects entering into following mode.
Following state table shall illustrate it:
| Attach | Motion | Reaction on spontaneous disable of drive |
|---|---|---|
| Yes | Yes | Fire 3115 asynchronous exception |
| Yes | No | Fire 3115 note |
| No | No | Do nothing |
- Being ACTIVE without being in use, is not a reason to fire a note.This would massively blow up the note-history.
- If axes are belonging to a group and this group is attached. Exception will be sent from the group only (the axes exceptions will be suppressed). This is the same functionality as it is today, made to prevent message avalanches.
Element is ACTIVE iff
- It is an axis
- It is a group which is currently being attached (explicitly by "attach" command or implicitly by executing motion command from the monitor.)
--Mirko 10:41, 15 November 2010 (CET)