Robot_upstart can't find path in my package

asked 2016-01-19 10:02:49 -0600

109 ●30 ●35 ●43

updated 2016-01-26 03:02:24 -0600

Hi everyone, I got a bug using robot_upstart. I tried the install script with differents packages located in my catkin workspace and I get this :

Unable to locate path launch/example_lucos.launch in package teleopRoboteq. Installation aborted.

Is my catkin workspace corrupted ?

Thanks

Edit 26/01/2015: I just test with a new ROS instalation. I use a compiled package with catkin_make, roboteq_driver. The launcher and the job were correctly installed. I tried with my robot description package and robot_upstart doesnt find it for an install. How do you install your robot description package with ROS and, more importantly, where ?

edit retag flag offensive close merge delete

Comments

Can you also provide the rosrun command you used?

Akif ( 2016-01-19 12:23:40 -0600 )edit

Here it is (something like that):

rosrun robot_upstart install lucos/launch/lucos.launch --interface p1p1

I also try on a new install and I get the same error.

TomSon ( 2016-01-20 01:30:56 -0600 )edit

It seems that there is a conflict between this 2 lines on some of my installations (.bashrc):

source /opt/ros/indigo/setup.bash
source ~/catkin_ws/devel/setup.bash

TomSon ( 2016-01-20 03:31:20 -0600 )edit

I have problems in robot_upstart too, maybe to write a upstart job to start your roslaunch is better option.

crazymumu ( 2016-01-20 21:15:03 -0600 )edit

I have done the same installation (i'm using the two line script to install ROS) on another computer. I just got the source of "joystick driver" and made a launch that I used with robot_upstart and I didn't get any trouble.

TomSon ( 2016-01-21 04:26:12 -0600 )edit

@TomSon: please describe your workspace layout and contents for us. Also add how you build it and what files you source (including your .bashrc). Issues with your ROS_PACKAGE_PATH would seem to suggest there is something incorrect in your ws setup / interaction.

gvdhoorn ( 2016-02-02 02:08:55 -0600 )edit

add a comment

Comments

When I use rospack find , I dont find my package (here lucos).

TomSon ( 2016-01-20 06:33:34 -0600 )edit

Then it means that you have a problem with your workspace sourcing. Can you post the output of echo $ROS_PACKAGE_PATH ?

Akif ( 2016-01-20 06:51:10 -0600 )edit

Only the second source command is necessary. The first one should have been done before creating the catkin_ws initially. Perhaps that was not done correctly?

joq ( 2016-01-20 07:05:34 -0600 )edit

@joq, it is not a must but wiki states: "This process allows you to install several ROS distributions (e.g. fuerte and groovy) on the same computer and switch between them."

Akif ( 2016-01-20 07:33:03 -0600 )edit

@Akif: no, @joq is correct. You should never need to do what @TomSon is doing, provided you created your workspace correctly. The "switching" you refer to is not meant to be in-place switching, but rather allows you to source a different setup.bash in a new terminal. Not in the same.

gvdhoorn ( 2016-01-20 07:54:11 -0600 )edit

Although I do not think the problem is related with that, I updated my answer with feedbacks from you and @joq. Sorry for that.

Akif ( 2016-01-20 08:14:15 -0600 )edit

@gvdhoorn, so there is indeed an issue with my workspace freshly installed ?

TomSon ( 2016-01-21 04:30:48 -0600 )edit

Well it depends on how you set it up. In principle you only source the last workspace in a chain. In this case, I'd say that is your catkin_ws (which overlays /opt/ros/indigo/..). Sourcing more than one setup.bash is not recommended (if supported at all, without additional arguments).

gvdhoorn ( 2016-01-21 04:47:07 -0600 )edit

see more comments

Robot_upstart can't find path in my package

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Robot_upstart can't find path in my package edit

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Robot_upstart can't find path in my package