Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

ROBOMATH.POINT_AXIS_2_POSE DOES NOT EXIST

#1
In `robomath.py`, `point_Zaxis_2_pose()` exists, but `point_Xaxis_2_pose()`and `point_Yaxis_2_pose()` do not exist, even though they are documented in the API reference: https://robodk.com/doc/en/PythonAPI/robo...xis_2_pose
#2
These additions are fairly recent. Did you update the robodk package?
pip install robodk --upgrade

You can see they are present in the source code:
https://github.com/RoboDK/RoboDK-API/blo...th.py#L233
Please read the Forum Guidelines before posting!
Find useful information about RoboDK by visiting our Online Documentation.
#3
Thanks, Sam.

I'm on 5.5.5. It looks like `pip install robodk --upgrade` did nothing, unfortunately.

Pip has been problematic for me lately, so I'm just going to copy-paste the GitHub code.

Would you be able to provide additional information for how this method works? Specifically:
1. What reference frame is the returned pose in?
2. What reference frame is the hint assumed to be in?

If you have an example use, that would be very helpful. I am having some trouble figuring out why it is behaving like it is behaving.
#4
You can use point_Zaxis_2_pose() when converting from a point with a normal vector (xyzijk) to a pose.
As points don't have orientation around the normal axis, this function will attempt to align the Y axis to the axis hints.
Attempt, as it can fail if the z axis and the axis hint are the parallel.
To point the Z axis of a pose along IJK, and attempt to point the Y axis to Z+, you would use point_Zaxis_2_pose(xyz, ijk, [0,0,1])

Here's an example:
https://github.com/RoboDK/Plug-In-Interf...ets.py#L78

I agree they should be better documented.
Please read the Forum Guidelines before posting!
Find useful information about RoboDK by visiting our Online Documentation.
#5
Thanks, Sam. That makes sense.

Looks like this is behaving as-expected. The problem is in another part of my code.
  




Users browsing this thread:
1 Guest(s)