Skip to content

Conversation

@sasabot
Copy link
Collaborator

@sasabot sasabot commented Dec 10, 2018

with a discussion with @YoheiKakiuchi
it is better to set the urdf limits to the actual hardware limits

and for other models with different limits, limit the range on the software side using the yaml file

@sasabot sasabot requested a review from y-shiigi December 10, 2018 08:27
@y-shiigi
Copy link
Collaborator

I understand, it's no problem.
But is the joint_limits.yaml working? Do I need to load at aero_bringup?

@sasabot
Copy link
Collaborator Author

sasabot commented Dec 11, 2018

it should be set once running setup.sh
I confirmed that it works on our robot but please check just in case

@y-shiigi
Copy link
Collaborator

I don't have the hand-yaw parts, so I changed elbow's limit as below:

  r_elbow_joint:
    has_velocity_limits: true
    max_velocity: 1.2
    has_acceleration_limits: false
    max_acceleration: 0
    min_position: -0.1
    max_position: 0

After running setup.sh typeFCESy and catkin build aero_samples, the sample motion(fullbody_test_node and ik_sample_node) are not changed. I thought the elbow will not be moved in this parameter.
Am I misunderstanding?

@sasabot
Copy link
Collaborator Author

sasabot commented Dec 11, 2018

hmm... i think i see the problem
the setting only changes the software limit. inside the code you have to check the bounds yourself
perhaps we need a boundary check inside some of the aero_std functions...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants