Difference between revisions of "MC-Basic:element.PrecomputationMode"
m (Miborich moved page Axystems:MC-Basic:element.PrecomputationMode to MC-Basic:element.PrecomputationMode: Global renaming of Axystems: namespace into (Main):) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Languages|MC-Basic:element.PrecomputationMode}} | ||
{{MC-Basic | {{MC-Basic | ||
|SHORT FORM= | |SHORT FORM= | ||
| Line 19: | Line 20: | ||
This mode uses very little CPU time for the precomputation task. | This mode uses very little CPU time for the precomputation task. | ||
| − | The '''DYNAMIC''' mode is a new approach to which considers the [[ | + | The '''DYNAMIC''' mode is a new approach to which considers the [[Motion Dynamics|motion dynamics]] (IDM) in the precomputation. |
Cartesian motion limits are adjusted with respect to joint velocities, acceleration/deceleration, jerk and [[MC-Basic:axis.TorqueLimit|torque limit]]s. | Cartesian motion limits are adjusted with respect to joint velocities, acceleration/deceleration, jerk and [[MC-Basic:axis.TorqueLimit|torque limit]]s. | ||
This mode uses an iterative algorithm which very strictly obeys the joint limits but results in a relatively high computational cost <!-- (it can reach 3ms on a MIB CPU) -->. | This mode uses an iterative algorithm which very strictly obeys the joint limits but results in a relatively high computational cost <!-- (it can reach 3ms on a MIB CPU) -->. | ||
| Line 44: | Line 45: | ||
|LIMITATIONS= | |LIMITATIONS= | ||
| − | * The Dynamic Precomputation mode can only be used together with the Time Based Profiler ([[ | + | * The Dynamic Precomputation mode can only be used together with the Time Based Profiler ([[MC-Basic:element.PROFILERTYPE|PROFILERTYPE]] = 2). |
| Line 54: | Line 55: | ||
}} | }} | ||
| − | [[Category | + | [[Category:Motion Dynamics]] |
Latest revision as of 07:42, 27 October 2017
| Language: | English • 中文（简体） |
|---|
When a Cartesian movement is commanded (with MOVES or CIRCLE), the Cartesian motion limits (acceleration, deceleration, velocity, etc.) need to be adjusted by the system in the way that the joint limits are not exceeded during the motion. This adjustment before the motion execution is called "precomputation". Because the precomputation is not a trivial task, several approaches with different cost of CPU time are implemented in the system.
The DEFAULT mode is only for Cartesian motion commands (MOVES, CIRCLE). It considers only the joint velocity and acceleration/deceleration limits and leads to reasonable results as long the motion is far away from singularities. This mode uses very little CPU time for the precomputation task.
The DYNAMIC mode is a new approach to which considers the motion dynamics (IDM) in the precomputation. Cartesian motion limits are adjusted with respect to joint velocities, acceleration/deceleration, jerk and torque limits. This mode uses an iterative algorithm which very strictly obeys the joint limits but results in a relatively high computational cost .
Dynamic precomputation can also be used in combination with joint/axis motion to consider the torque limits.
Syntax
?<element>.PrecomputationMode
<element>.PrecomputationMode= <value>
Availability
Since Version 4.9.11
Type
Long
Range
- 0 = NONE
- 1 = DEFAULT
- 4 = DYNAMIC
Default
1
Scope
Task or Terminal
Limitations
- The Dynamic Precomputation mode can only be used together with the Time Based Profiler (PROFILERTYPE = 2).