@ProviderType public interface FixedPositionDefinedWaypointNodeConfig extends FixedPositionWaypointNodeConfig
FixedPositionWaypointNodeConfig.PositionDefinition
WaypointNodeConfig.ConfigType
Modifier and Type | Method and Description |
---|---|
Optional<JointPositions> |
getJointPositions()
This method returns the joint positions corresponding to the defined Cartesian location of the waypoint (accessible
through
getPose() ). |
Pose |
getPose()
This method returns the pose for the Cartesian location of the Waypoint node, i.e.
|
getBlendParameters, getMotionParameters, getPositionDefinition
getConfigType
Pose getPose()
Optional<JointPositions> getJointPositions()
This method returns the joint positions corresponding to the defined Cartesian location of the waypoint (accessible
through getPose()
).
The waypoint's joint positions depend on the TCP and feature selection in the Move node, that is parent to the Waypoint node in the program tree. The joint positions will change accordingly, when these selections are changed in the parent Move node, or when the Cartesian position and/or orientation of the TCP/feature are changed in the installation. They can also change as a result of the end user loading a different installation. Note that this means that the joint positions can be subject to change after this method has been called.
The waypoint's joint positions will not be available when:TreeNode
interface).
Because of this, the returned joint positions are wrapped in an Optional
, which will not have any value
available in the situations described above. Always use Optional.isPresent()
to check if the waypoint's
joint positions are available before accessing them using Optional.get()
.
Note: If the parent Move node is configured to use the active TCP (i.e. the 'Use Active TCP' option), the
returned joint positions will depend on which TCP is currently active.
Note: Even though the returned joint positions correspond to the Cartesian location of the waypoint, they
can differ from the joint positions used at runtime of the robot program, as many things influence the joint
positions during the execution of a program. For instance, during execution of a MoveL parent node, the achieved
joint positions for the Waypoint node depend on the current position of the robot (e.g. determined by a previous
executed Waypoint node) when computing the joint positions corresponding to the waypoint's Cartesian location
(using inverse kinematics). Joint positions can also depend on the currently active TCP if the parent Move node
is configured to use that.
Optional
. Always use Optional.isPresent()
to verify that the
waypoint's joint positions are available before using Optional.get()
to retrieve them.Copyright © 2023. All rights reserved.