Difference between revisions of "AXY:Element Coordination/Multi Dimensional Tracking Algorithm (Position)"
(→Multi Dimensional Tracking Algorithm) |
(→State: Full Synchronization follow the master) |
||
Line 18: | Line 18: | ||
* Check if master velocity or acceleration exceeds max master frame's values if yes return an error | * Check if master velocity or acceleration exceeds max master frame's values if yes return an error | ||
− | * <math>\overrightarrow {tack} := \overrightarrow {master}</math> | + | * <math>\overrightarrow {tack} := \overrightarrow {master}</math> ''copying all derivatives'' |
* ''reset:'' '''flopstime = flops = 0''' | * ''reset:'' '''flopstime = flops = 0''' |
Revision as of 13:07, 24 April 2012
Contents
- 1 Multi Dimensional Tracking Algorithm
- 1.1 State: Full Synchronization follow the master
- 1.2 State: Tracking process
- 1.2.1 Initial Setup and testing
- 1.2.2 Time-to-Reach initial estimation
- 1.2.3 Prediction of the Rendezvous-Point
- 1.2.4 Next SamplePosition
- 1.2.5 Velocity, Acceleration and Jerk Filter
- 1.3 State: Stopping (de-synchronization process)
Multi Dimensional Tracking Algorithm
This algorithm is used for multi-dimensional robot based MF tracking.
In this document position-tracking is presented.
Position is considered to be a 3-dimensional vector with it's derivatives (velocity, acceleration, jerk): , ,
The algorithm consist of a state machine with the following states:
- Tracking process
- Full Synchronization follow the master
- Stopping (de-synchronization process)
State: Full Synchronization follow the master
- Check if master velocity or acceleration exceeds max master frame's values if yes return an error
- copying all derivatives
- reset: flopstime = flops = 0
State: Tracking process
Initial Setup and testing
Value of AccMaxTran (or AccMaxRot) is used of checking of acceleration limit. |
Value of VelMaxTran (or VelMaxRot) is used of checking of velocity limit. |
- Check if master velocity or acceleration exceeds max master frame's values if yes return an error
- Compute differences:
pure delta-position
pure delta-velocity
Time-to-Reach initial estimation
defined as SyncJerkTran |
defined as SyncAcclerationTran |
This is an estimation of time needed to reach the target. It is not an exact formula
if the slave velocity is lower then master's we need more time: once to get to a higher velocity then the masters and once
to get from that (higher) velocity to the masters - therefore the multiplication by 2
where
DampingFactor - user defined by: MF.DAMPINGFACTOR |
Additionaly we mutliply by a prediction factor - to decrease acc/jerk
(rounding to integer number of samples):
time_to_reach *= DampingFactor time_to_reach = T*int(time_to_reach/T+1)
Prediction of the Rendezvous-Point
The predicted position of the rendezvous (minus T, if it will happen in this sample!)
: position prediction assuming constant acceleration
: Predicted position difference
: velocity prediction
Assuming the acceleration will be zero:
Polynomial coefficients of 5-degree polynom connecting the current p,v,a to the randevous p,v,a
- not used, directly written into code
- not used, directly written into code
- not used, directly written into code
Next SamplePosition
The position at the next sample will be:
Initial increment (full displacement):
The accleration and jerk increments could be computed in this way also.
But they are computed as average values for the time of sample duration, this approach doeas fit more to
the tools we are using to test this feature, (BMDS...) as they all compute accleration & jerk by numeric differentiation
inside one sample.
The side effect of all this is that we can have a change in jerk/acc sign inside one sample and the average value we are using
ddp,dddp could have an opposite sign, so we are seeing effects like jerk or accleeration is limited from a "wrong side" i.e. instead
using jmax -jmax is used. There is not much we can do against it, using exact jerk/acc values (from polynom) returns than wrong avergae values
we observe as jerk/acc exceed over theri max values. So the avergae value approach is not perefect but gives results within the given limits.
Initial setting of predicted time and the filter limit flag (if the filter did work - this flag will be on)
limit = false state.satVel = false state.satAcc = false state.satJrk = false
Velocity, Acceleration and Jerk Filter
sync_vel defined as VelSyncTran |
sync_acc defined as AccSyncTran |
sync_jrk defined as JrkSyncTran |
T is sampling time |
where i.e. unit vector
Setting Initial velocity delta
Setting Initial acceleration delta
New position is:
If the filter was activated then:
if the velocity,accleration or jerk is limited (limit = true) then the velocity computed using polynomials does
Velocity & Accleration will be computed exactly not using dp and ddp, it has been shown that this
approach is much better - means more stable
keep the old values for next sample
System is synchronized if NEW delta's are under certesian thresholds:
; - keep the previous dv
syncGain defined by the user with: MF.FilterFactor |
Successful tracking completion
if and
Synchronization
Take the middle for an additional smoothing:
ResetFilter(); // Reset the filter state.tracking = MOT_MASTER_SYNC; // System synchronized<br>
else if( dv0*dv < 0)
Check against over-oscillation
if (flops == -1) flops = 0; // ignore the first sample else flops++; flopstime = 0;
Over-Oscillation Check
maxFlops defined by the user with: MF.MaxFlops |
if (flops > maxFlops && (flopstime > maxFlopsTime && fabs(dv) > syncGain * sync_accT2))
state.tracking = MOT_MASTER_OSC; // OScilationss
else
flopstime++;
State: Stopping (de-synchronization process)
flopstime = flops = 0;
- De-Syncing profile, follow the given profile, ignore the real source
desync.Profile(); track_pos = track_pos_0+master_direction*desync.path.curr_pos; track_vel = master_direction*desync.path.vel; track_acc = master_direction*desync.path.acc; if(desync.path.Status.stop) // if stopped,change the state to OFF SetState(MOT_MASTER_OFF);