Skip to content

Duration Parameter in Base Joint Speeds Messages #159

Open
@fleurssauvages

Description

@fleurssauvages

Hi,

I am controlling the arm to have Cartesian velocity control with joint constraints. The optimization is done with ROS and C++.
Everything works great but i have one issue.

After making my optimization, i send the desired joint velocity to the "/my_gen3/in/joint_velocity" topic.
As long as my trajectory is correct, everything works fine and the control is as desired.

Now lets image that my node or my Ethernet connection shutdown for an unknown reason.
It seems like the "duration" parameter in the message is not taken into account and the joints keep rotating forever.
I have tried many things: to modify both the duration in the BaseJointSpeeds and BaseJointSpeed (each joint of the list of jointspeeds) messages; i thought that the duration might be in ms, or seconds, but it still rotates forever no matter what the input value (i tried 1, 10, etc.)

This is of course a huge security issue, as a shutdown of my computer would lead to potential collisions due to undesired published velocities. And because i want to use my control with human interaction, this would lead to major potential risks.

Am I missing something obvious ? or is that parameter indeed not used ?
If so, how could I put another layer of security so that any joint velocity command is only followed for like 1s for example ?

Thank you in advance for any help

Metadata

Metadata

Assignees

No one assigned

    Labels

    not implemented yetIssue will be updated when the feature is accessible

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions