Difference between revisions of "AXY:Element Synchronization/Design"

From SoftMC-Wiki
Jump to: navigation, search
(Master Profile)
(Master Profile)
Line 45: Line 45:
 
The complete system of the sync-list motion profiles will be executed together just be scaling each of them by the factor of: <math>\frac{L_i}{\sqrt{\sum L_i ^2}}</math>
 
The complete system of the sync-list motion profiles will be executed together just be scaling each of them by the factor of: <math>\frac{L_i}{\sqrt{\sum L_i ^2}}</math>
  
 +
{{Note/Caution| What happens if profiler changes it's type?}}
 +
 +
{{Note/Caution| What happens in case of extremely short motions?}}
  
 
<center>
 
<center>

Revision as of 11:26, 27 March 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:

Master Profile

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:

CAUTION.svgCAUTION
What happens if profiler changes it's type?
CAUTION.svgCAUTION
What happens in case of extremely short motions?