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

Update FTS tcp and return FTS state parameters #32

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

Conversation

destogl
Copy link
Member

@destogl destogl commented Nov 10, 2020

There are often per-axis limits

This is often defined per-axis. see: https://www.ati-ia.com/products/ft/ft_models.aspx?id=Mini45

As disscussed in comment

There are often per-axis limits 

This is often defined per-axis. see: https://www.ati-ia.com/products/ft/ft_models.aspx?id=Mini45
@destogl destogl requested a review from bmagyar November 10, 2020 11:43
@destogl destogl changed the title Update FTS tcp and return FTS state paramters Update FTS tcp and return FTS state paramdters Jan 18, 2021
@destogl destogl changed the title Update FTS tcp and return FTS state paramdters Update FTS tcp and return FTS state parameters Jan 19, 2021
@destogl destogl requested a review from Karsten1987 February 20, 2021 18:36
@destogl
Copy link
Member Author

destogl commented Feb 20, 2021

Can you please review this. There is a PR for Example 3 in the ros-controls/ros2_control_demos#68 so we don't have to change the implementation later...

There is no reason to have 6-axis example sensors on 2-axis robot.
Are there FTS with asymmetric range?
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.

1 participant