Difference between revisions of "AXY:Element Synchronization/Design"
(→Pre-Calculation) |
|||
Line 15: | Line 15: | ||
Is done in MotionManager task, initiated by message sent from SyncStart/All commands: | Is done in MotionManager task, initiated by message sent from SyncStart/All commands: | ||
− | In case of SyncStart we sperately execute MotCalc on every element from the sync-list: | + | In case of SyncStart we sperately execute MotCalc on every element from the '''sync-list''': (el<sub>1</sub> , el<sub>2</sub> , el<sub>3</sub> , ... el<sub>n</sub> ): |
<pre> | <pre> |
Revision as of 09:23, 31 January 2012
Element Synchronization Design
Common algorithms to both SyncStart and SyncAll:
Pre-Calculation
Is done in MotionManager task, initiated by message sent from SyncStart/All commands:
In case of SyncStart we sperately execute MotCalc on every element from the sync-list: (el1 , el2 , el3 , ... eln ):
FOR element FROM sync-list element->MotCalc() NEXT
In case of SyncAll it is little bit more complicated, every element is pre-calculated in order to estimate it's own max profile values:
FOR element FROM sync-list element->MotCalc() ==> Li , Vi , Ai , Di , Jai , Jdi NEXT
And then generate a master profile with the following parameters:
The master profile data-structure will be copied to the profile-data-structure of all other elements.
Master profile:
, , , , ,
where
The master profile data-structure will be copied to the profile-data-structure of all other elements.
The complete system of the sync-list motion profiles will be executed together just be scaling each of them by the factor of: