Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add single fr3 #1885

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

add single fr3 #1885

wants to merge 4 commits into from

Conversation

yuki-asano
Copy link
Contributor

  • added minimum set of fr3 (franka research 3) model which is almost same with panda model (only name is different)
  • confirmed motions of the real robot by
(send *ri* :angle-vector (send *fr3* :angle-vector) 5000)
(send *ri* :start-grasp :rarm)
(send *ri* :stop-grasp :rarm)

Screenshot from 2023-10-31 12-31-44

@github-actions github-actions bot added the panda dual franka robot in JSK label Oct 31, 2023
Copy link
Contributor

@pazeshun pazeshun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JSK does not have real fr3, so I only confirmed that fr3.l seems correctly generated and the following procedure works on kinematics simulator:

(fr3-init)
(objects (list *fr3*))
(send *ri* :stop-grasp :rarm)
(send *ri* :start-grasp :rarm)
(send *fr3* :stop-grasp :rarm)
(send *fr3* :start-grasp :rarm)
(send *fr3* :init-pose)
(send *ri* :angle-vector (send *fr3* :angle-vector) 5000)

@k-okada
Copy link
Member

k-okada commented Nov 1, 2023 via email

@pazeshun
Copy link
Contributor

pazeshun commented Nov 1, 2023

@k-okada

if the only difference is name , why not load the existing lisp file and change robot name?

I think @yuki-asano 's explanation is incorrect.

At least, joint names are different, so we have to generate fr3.l:
https://github.com/jsk-ros-pkg/jsk_robot/pull/1885/files#diff-3518a932c47d029d01ebd0f0d3e9f8d0656adbca5d2c218f48b9e326124596e1R2-R8
vs.

- panda_joint1 : rarm-collar-y
- panda_joint2 : rarm-shoulder-p
- panda_joint3 : rarm-shoulder-y
- panda_joint4 : rarm-elbow-p
- panda_joint5 : rarm-wrist-r
- panda_joint6 : rarm-wrist-p
- panda_joint7 : rarm-wrist-y

So it is hard to reuse panda-utils.l in fr3-utils.l, because current panda-utils.l uses defmethod against panda-robot, not fr3-robot:
https://github.com/jsk-ros-pkg/jsk_robot/blob/ddf454dd5f4f4c1aa43b81fda6e17a24d96c721f/jsk_panda_robot/panda_eus/euslisp/panda-utils.l

As for fr3-interface.l, we may be able to reuse panda-interface.l by defining fr3-interface as a child class of panda-interface. I do not think this is a good idea because code uniformity (parent class of all franka robots' interfaces is franka-common-interface) becomes lost, but I'll follow @k-okada 's decision. I reconsidered and will make a PR for this. -> yuki-asano#5

Re-use panda-robot-interface in fr3-robot-interface & Add fr3 to README
Copy link
Contributor

@pazeshun pazeshun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k-okada Maybe I followed your comment. Could you check this PR again?

@pazeshun
Copy link
Contributor

@k-okada Kindly ping

2 similar comments
@pazeshun
Copy link
Contributor

@k-okada Kindly ping

@pazeshun
Copy link
Contributor

pazeshun commented Apr 5, 2024

@k-okada Kindly ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
panda dual franka robot in JSK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants