ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

0

"unable to load manifest" error after subscribe via RosSharp/RosBridge

asked 2018-03-23 16:11:28 -0500

Lane
3 ●1 ●1 ●2

Using Unity and the RosSharp library I'm able to connect but unable to subscribe to any custom .msg types. The types are correctly named in the RosSharp dictionary and builds fine on the ROS side. After requesting to subscribe it will throw the error on the rosbridge socket terminal:

unable to load the manifest for package ####. Caused by ####

ROS path [0]=/opt/ros/kinetic/share/ros

ROS path [1]=/opt/ros/kinetic/share

Any thoughts?

Thanks, Lane

edit retag flag offensive close merge delete

Comments

Is package ### present in your workspace / installed on your system? Does rospack find #### return the expected output (in the same terminal as where you start the RosBridge nodes)? I don't see any Catkin workspace in the error output, so did you source it?

gvdhoorn ( 2018-03-24 02:58:33 -0500 )edit

the package is present, rospack find identifies it and i did source ./devel/setup.bash after the catkin_make.

Lane ( 2018-03-26 08:20:37 -0500 )edit

This works on a linux box, but fails on my VirtualBox VM - identical projects.

Lane ( 2018-03-27 11:58:29 -0500 )edit

1 Answer

Sort by » oldest newest most voted

0

answered 2018-03-27 11:59:29 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

updated 2018-03-27 12:20:34 -0500

Just making sure: the terminal where you started rosbridge also had sourced the workspace setup.bash?

Edit:

Wow, did not realize that was required for each new terminal.

Yes, that is needed in every terminal. See #q286466 for a recent question about this.

edit flag offensive delete link

Comments

Wow, did not realize that was required for each new terminal. Seems to be working fine, thanks =)

Lane ( 2018-03-27 12:08:48 -0500 )edit

run source catkin_ws/devel/setup.bash in the bridge terminal window.

Lane ( 2018-03-27 12:09:37 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2018-03-23 16:11:28 -0500

Seen: 662 times

Last updated: Mar 27 '18

Related questions

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2