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

wiki: update supported_hardware page (again) #32

Open
gavanderhoorn opened this issue Oct 13, 2014 · 9 comments
Open

wiki: update supported_hardware page (again) #32

gavanderhoorn opened this issue Oct 13, 2014 · 9 comments

Comments

@gavanderhoorn
Copy link
Member

As per subject. Motoman and Fanuc entries seem rather out of date.

Formatting of the Definitions sections could perhaps be looked at as well?

@gavanderhoorn gavanderhoorn added this to the indigo milestone Oct 13, 2014
@gavanderhoorn
Copy link
Member Author

As an alternative to a central page on the wiki, we could migrate the information to package-specific pages and / or to the readmes of the repositories.

@gavanderhoorn
Copy link
Member Author

Suggestion: make a dedicated industrial robot hw support page and remove the other sections.

@hsd-dev
Copy link

hsd-dev commented Jun 19, 2019

This seems to be an updated list: https://robots.ros.org/tags/#industrial
Is this page this still relevant? http://wiki.ros.org/action/fullsearch/Industrial/supported_hardware
Or can they be merged?

@gavanderhoorn
Copy link
Member Author

This seems to be an updated list: https://robots.ros.org/tags/#industrial

that's a page dependent on community contributions and as such lists robots for which community members thought the tag industrial would fit.

It does not reflect the status of supported hw "within ros-industrial".

Is this page this still relevant? http://wiki.ros.org/action/fullsearch/Industrial/supported_hardware
Or can they be merged?

That page specifically documents the compatibility of specific robot & controllers with industrial_robot_client and/or their drivers. There are a few other sections on the page, but those are vestigial I believe.

We might just want to have a short list that links to the wiki pages of the various robot and other packages that we have.

We could opt for removing those pages completely and use robots.ros.org but seeing the current list of robots that are listed for the industrial tag I'm not sure whether that would not be confusing.

@robinsonmm
Copy link
Member

I had a request from KEBA to be added to the supported_hardware page.... since they are now offering a controller that works on Hiwin and Comau robots... we could include others that offer nominal and advertised ROS interfaces.

We could seek to add Kawasaki, Epson, Staubli, and Pilz, etc...

I agree I would like it to contain the same info as the existing table, and nominally have engagement/supporting data/resources from the OEM side. I believe the table in the Wiki is more complete and therefore different than hwat is at ros.org/robots under the "industrial manipulator" category... thoughts?

@gavanderhoorn
Copy link
Member Author

we could include others that offer nominal and advertised ROS interfaces.

We could seek to add Kawasaki, Epson, Staubli, and Pilz, etc...

I'm not sure I would do this: the pages under wiki/Industrial specifically document the state of "our" packages.

None of the OEMs you list there are supported "by us".

If they have ROS interfaces available those should be listed / advertised on pages outside wiki/Industrial I feel.

@robinsonmm
Copy link
Member

Thanks for clarifying the intent regarding "our" packages. Ok, I think it is good to point those promotional opportunities for those companies.

@gavanderhoorn
Copy link
Member Author

The pages would still need some cleaning up and/or updating, so I'll still mark this as a WRID19 issue.

It'll probably have to be one of us (RIC-NA, RIC-EU, RIC-APAC) that takes this one though.

@robinsonmm
Copy link
Member

robinsonmm commented Jun 29, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants