Proposal - sensor_msgs/msg/Contact.msg
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 393
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Description
Simple message for contact sensors, that defines if contact between sensor and some unknown object was detected.
Motivation
I could not find simple message that defines whether there is contact between some defined sensor and other undefined object/objects. Messages like /ros_gz_interfaces/msg/Contact.msg are too complicated and simulator specific for simple contact detection. For contact sensor with force and torque readings geometry_msgs/WrenchStamped.msg would be enough.
Design / Implementation Considerations
# This is a message to hold data from simple contact
std_msgs/Header header # timestamp is the time the contact was measured
# frame_id is the location of the contact sensor
bool contact # True if there is contact
Additional Information
I believe that this message could be used for creating future hardware interfaces and broadcasters for ros2_control framework. It also would be helpful for fields where contact sensors are widely used, such as legged robotics.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed sensor_msgs/msg/Contact.msg definition and its std_msgs/Header dependency, then compare it with geometry_msgs/WrenchStamped.msg and ros_gz_interfaces/msg/Contact.msg. Confirm whether the simple contact-only interface fits common_interfaces and the stated hardware-interface use cases; done means the interface design is agreed and the new message is accepted for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100