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

“Configuration/Movement/Safety-critical" interfaces definition and use #50

Open
destogl opened this issue Feb 9, 2022 · 2 comments · May be fixed by #51
Open

“Configuration/Movement/Safety-critical" interfaces definition and use #50

destogl opened this issue Feb 9, 2022 · 2 comments · May be fixed by #51
Assignees

Comments

@destogl
Copy link
Member

destogl commented Feb 9, 2022

No description provided.

@destogl destogl self-assigned this Feb 9, 2022
@destogl
Copy link
Member Author

destogl commented Dec 6, 2023

This covers also the following proposals:

  • @fmauch: Proper connection of ports and lifecycle (Configure “writable in inactive”)
  • @christophfroehlich / @saikishor: Fix the HW command interfaces being available in the configured state, rather they should be only marked available upon activation of the HW

Proposal from @destogl

We add an additional method write_when_inactive, and this is called from the INACTIVE state check in the hardware components. Maybe we also can have multiple lists of command interfaces (depending on storage) and we give only those at argument (map or list) that are accessible then. This depends on change from me and @mamueluth

@destogl
Copy link
Member Author

destogl commented Mar 11, 2024

Adding new class and new tag:

Add a new tag in the URDF:

<joint name="${prefix}joint2">
    <configuration_interface name="position">
      <param name="min">-1</param>
      <param name="max">1</param>
    </configuration_interface>
    <state_interface name="position"/>
  </joint>

Then, add a new field in the CommandInterface, marking this for RM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Jazzy
Development

Successfully merging a pull request may close this issue.

1 participant