Skip to content
This repository has been archived by the owner on Mar 24, 2024. It is now read-only.

ROS 2 native connection support #715

Closed
amacneil opened this issue Apr 27, 2021 · 8 comments · Fixed by #1640
Closed

ROS 2 native connection support #715

amacneil opened this issue Apr 27, 2021 · 8 comments · Fixed by #1640
Assignees
Labels
feature Enhancement request

Comments

@amacneil
Copy link
Contributor

amacneil commented Apr 27, 2021

Placeholder ticket to discuss native ROS2 connections.

See also:

@amacneil amacneil added the feature Enhancement request label Apr 27, 2021
@vmanchal1
Copy link

+1

@jtbandes jtbandes pinned this issue Jun 18, 2021
@amacneil amacneil unpinned this issue Jun 29, 2021
@shoemakerlevy9
Copy link

Hi, my company Rover Robotics is launching a robot in September via Kickstarter that is going to ship with ROS2 Foxy by default. We are looking for an alternative to RVIZ because we don't like QT development. I really like the look of Foxglove and would like to try it out. Is there a work a round for getting it to work with ROS Foxy?

@amacneil
Copy link
Contributor Author

amacneil commented Jul 5, 2021

It is apparently possible to use Foxglove Studio with ROS 2 via the ros1 bridge (I haven't tried this myself but heard from someone doing it). If you try this we would love to hear back on how it works out for you.

Support for ROS 2 without needing the bridge is being actively worked on (e.g. 1 2 3). I can't give a concrete timeline for when it will be ready, but it should be 🔜.

@amacneil amacneil pinned this issue Jul 20, 2021
@ShawnSchaerer
Copy link

We use it with ROS1 bridge. Works fine but it's an added step.

@amacneil
Copy link
Contributor Author

amacneil commented Aug 10, 2021

Update on this ticket status:

  • ROS 2 bag playback (ROS 2 bag support #717) is launched
  • ROS 2 websocket (rosbridge) connection support is in progress complete (see ROS 2 rosbridge websocket connection support #716 - we are in the process of publishing a new version of rosbridge, and there are some minor issues to fix in studio)
  • ROS 2 native connection support is in progress, but will take a while (~months) since it requires reimplementing all of ROS 2 + DDS in JS. You can follow this development progress in our various ROS 2 typescript libraries. In the meantime rosbridge will be our recommended path for ROS 2 users.

@jhurliman
Copy link
Contributor

ROS 2 native connection progress can be tracked on the pull request at #1640

@jhurliman jhurliman linked a pull request Aug 14, 2021 that will close this issue
@jtbandes jtbandes unpinned this issue Sep 2, 2021
@jtbandes
Copy link
Member

jtbandes commented Sep 3, 2021

Gonna keep this issue open since it seems like the connection is not yet in a usable state (#1750)

@jtbandes jtbandes reopened this Sep 3, 2021
@jtbandes jtbandes pinned this issue Sep 3, 2021
@defunctzombie
Copy link
Contributor

We'll close this as the overall ROS2 Native support is in place. We have the new issues to track smaller features/bugs.

@jtbandes jtbandes unpinned this issue Sep 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Enhancement request
Development

Successfully merging a pull request may close this issue.

7 participants