ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Smart Attachment Protocol

This is a repost.

Is there a standard or similar project that has smart attachments?

What standard would we use to communicate between a ROS system on an attachment and ROS system on a robot? Would there be multiple channels? (.ie wifi and CANbus)

Has this been solved in ROS Health, with multi-manufacturer robotic hospitals? Or Autoware with vehicle to vehicle communication?

Matt

I am not familiar with a “general” solution to this challenge, in ros-health (Hospitals) or other settings, for that matter. Coming up with an approach that works in many different application domains, physical bus protocols, classes of sensor and actuator attachments, impacts on motion planning, etc., is challenging in many ways.

It’s certainly a very interesting topic though! I’d suggest just rapid-prototyping lots of ideas to see what sticks, to avoid getting slowed down by a grand unified theory of attachments. But that’s just me :rofl:

Could you clarify what an “attachment” is here?

Is it a piece of hardware that may be connected and disconnected from a larger piece of equipment (ie: an implement attached to a tractor in an agricultural setting)?

Yes, a piece of hardware that may be connected and disconnected. For example could be a sprayer, seeder or mechanical weeder.

1 Like

In agriculture ISOBUS is king.
https://www.caseih.com/northamerica/en-us/innovations/isobus

I would say you would need a ROS ISOBUS node.

3 Likes

Since vehicle-to-vehicle communication is by nature wireless, most people these days are focusing on using Internet-over-5G-modem to achieve it. Autoware itself currently does not have any built-in capability for this but because it’s ROS 1, using native ROS is not feasible. Most commonly I have seen gateways that go between ROS and some common web communication technology.