APIs, concepts, guides, and more
|
Stream data points for detailed motion control on single or multiple axes, using profiles tailored for precision and complexity. Adjust your motion dynamically.
Streaming point motion is when the controller is given a stream of data points which represent an entire motion profile. The controller executes the data points with the given times, down to the sample period. It can be used for a single Axis or several axes at the same time using a MultiAxis object. This document describes all the different ways to do streaming point motion and the advantages and disadvantages of each.
RSIMotionTypePT is recommended only when you are using time values equal to one controller sample period. The position for a PT move is continuous. However, the velocity is not continuous. Because of the discontinuity of velocity, PT motion should only be used when the time between points are small; otherwise spline (Bessel, Spline, BSpline, and BSpline2) or PVT motion should be used.
With RSIMotionTypeBESSEL motion, a user must specify the position and time values for a given motion at multiple points. This allows a user to create a smoother motion, but without the need to specify velocity values at each point.
For Bessel type motion, the velocity is continuous, but the acceleration is not. The velocity of Bessel type motion tends to be less smooth than the other spline motion types (Spline, B-Spline, and B-Spline2).
With RSIMotionTypeSPLINE, a user must specify the position and time values for a given motion at multiple points. This allows a user to create a smoother motion, but without the need to specify velocity values at each point.
For Spline type motion, the velocity and acceleration are continuous. However, the accelerations at the beginning and end of a motion are not discontinuous. Also, the velocity may be discontinuous at the end of motion β however, this can be easily remedied by specifying the final point twice.
With RSIMotionTypeBSPLINE (AKA Basis Spline) type motion, a user must specify the position and time values for a given motion at multiple points. This allows a user to create a smoother motion, but without the need to specify velocity values at each point.
With B-Spline motion, the generated trajectory is a 3rd order B-Spline. The velocity and acceleration are continuous. However, the accelerations at the beginning and end of motion are not discontinuous. Also, it is important to note that points specified to B-Spline motion are control pointsβthe trajectory of the axis usually does not pass through these points; the trajectory only approaches the points.
With RSIMotionTypeBSPLINE2, a user must specify the position and time values for a given motion at multiple points. This allows a user to create a smoother motion, but without the need to specify velocity values at each point.
With B-Spline2 motion, the generated trajectory is a 2nd order B-Spline. The velocity is continuous throughout motion, but does have a velocity jump at the start of motion. Thus it is best if the first several points in a B-Spline2 move are closely spaced in time. The acceleration is constant between control points, but discontinuous at the start and end points. Also, it is important to note that points specified to B-Spline2 motion are control pointsβthe trajectory of the axis usually does not pass through these points; the trajectory only approaches the points.
RSIMotionTypePVT is a bit more complicated to use because it requires an array of Positions, Velocities, and Time deltas. The controller is only responsible for figuring out the acceleration for each motion segment. This makes it more flexible and gives users more control over the motion path. The position and velocity for a PVT move are continuous. However, the acceleration and jerk values are not continuous. The jerk maintains a constant value between PVT points, but is discontinuous at the PVT points. Therefore, the acceleration is continuous between PVT points, but it also may be discontinuous at PVT points. See PVT Streaming Motion for more information.
This Streaming Motion is a lot more complicated to use because it requires an array of Positions, Velocities, Acceleration, Jerk, and Time deltas. The controller is not responsible for figuring out anything because it streams the arrays straight to the frame buffer. This makes it very flexible and gives users absolute control over the motion path. The controller does not do any interpolation or calculations because everything it needs is calculated beforehand in the PVAJT arrays. PVAJT motion must all be provided in advance and cannot be appended to. See PVAJT Streaming Motion for more information.
All motion streaming methods can be used for coordinated motion on MultiAxis objects. It is important that you set up your arrays appropriately for a MultiAxis object. See the examples in the different streaming method pages on how to structure your arrays for MultiAxis motion.
Motion Type | Must specify entire move | Segments may be appended | Passes through control points |
---|---|---|---|
PT | β | β | |
PVT | β | β | |
Bessel | β | β | |
Spline | β | β | |
B-Spline | β | ||
B-Spline2 | β | ||
PVAJT | β |
Motion Type | Continuous Velocity | Velocity Jump at Start of Motion | Velocity Jump at End of Motion | Continuous Acceleration | Acceleration Jump at Start of Motion | Acceleration Jump at End of Motion |
---|---|---|---|---|---|---|
PT | β | β | β | β | ||
PVT | β | β | β | |||
Bessel | β | β | β | |||
Splineβ‘ | β | β | β | β | ||
B-Spline | β | β | β | β | ||
B-Spline2 | β | β | β |
Does the column order of the motion points given to streaming methods (ex: MovePT) corresponds to the order in which the individual Axis objects were added to the MultiAxis?
Correct. The order in which you add the points will correspond to the order in which you added the axes to the MultiAxis object.