2016-01-05 16:53:38 -0500 | received badge | ● Famous Question
(source)
|
2015-11-19 21:07:46 -0500 | received badge | ● Famous Question
(source)
|
2015-11-19 21:07:46 -0500 | received badge | ● Notable Question
(source)
|
2015-11-19 00:31:34 -0500 | received badge | ● Notable Question
(source)
|
2015-08-31 06:51:38 -0500 | received badge | ● Popular Question
(source)
|
2015-08-28 01:39:04 -0500 | commented question | rosout was not build during indigo install on raspberry Pi Rosdistro unknown? May this be the reason? |
2015-08-28 01:33:28 -0500 | received badge | ● Popular Question
(source)
|
2015-08-27 14:50:15 -0500 | asked a question | rosout was not build during indigo install on raspberry Pi I get the following error when starting roscore: pi@RPiMower /opt/ros/indigo/bin $ ./roscore
... logging to /home/pi/.ros/log/52a0cc44-4cf0-11e5-a624-74da3854767b/roslaunch-RPiMower-24065.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://RPiMower:53800/
ros_comm version 1.11.13
SUMMARY
========
PARAMETERS
* /rosdistro: <unknown>
* /rosversion: 1.11.13
NODES
auto-starting new master
process[master]: started with pid [24078]
ROS_MASTER_URI=http://RPiMower:11311/
setting /run_id to 52a0cc44-4cf0-11e5-a624-74da3854767b
ERROR: rosout is not built. Please run 'rosmake rosout'
failed to start core service [/rosout]
The traceback for the exception was written to the log file
[master] killing on exit
rosmake rosout gives a Long output, but does nothing. pi@RPiMower /opt/ros/indigo $ rosmake rosout
[ rosmake ] rosmake starting...
[ rosmake ] Packages requested are: ['rosout']
[ rosmake ] Logging to directory /home/pi/.ros/rosmake/rosmake_output-20150827-193526
[ rosmake ] Expanded args ['rosout'] to:
['rosout']
[rosmake-0] Starting >>> catkin [ make ]
[rosmake-0] Finished <<< catkin ROS_NOBUILD in package catkin
No Makefile in package catkin
[rosmake-0] Starting >>> genmsg [ make ]
[rosmake-1] Starting >>> cpp_common [ make ]
[rosmake-2] Starting >>> cmake_modules [ make ]
[rosmake-0] Finished <<< genmsg ROS_NOBUILD in package genmsg
No Makefile in package genmsg
[rosmake-1] Finished <<< cpp_common ROS_NOBUILD in package cpp_common
No Makefile in package cpp_common
[rosmake-1] Starting >>> rostime [ make ]
[rosmake-0] Starting >>> genlisp [ make ]
[rosmake-3] Starting >>> genpy [ make ]
[rosmake-1] Finished <<< rostime ROS_NOBUILD in package rostime
No Makefile in package rostime
[rosmake-2] Finished <<< cmake_modules ROS_NOBUILD in package cmake_modules
No Makefile in package cmake_modules
[rosmake-2] Starting >>> gencpp [ make ]
[rosmake-1] Starting >>> roscpp_traits [ make ]
[rosmake-0] Finished <<< genlisp ROS_NOBUILD in package genlisp
No Makefile in package genlisp
[rosmake-2] Finished <<< gencpp ROS_NOBUILD in package gencpp
No Makefile in package gencpp
[rosmake-0] Starting >>> rospack [ make ]
[rosmake-1] Finished <<< roscpp_traits ROS_NOBUILD in package roscpp_traits
No Makefile in package roscpp_traits
[rosmake-2] Starting >>> roslang [ make ]
[rosmake-3] Finished <<< genpy ROS_NOBUILD in package genpy
No Makefile in package genpy
[rosmake-1] Starting >>> roscpp_serialization [ make ]
[rosmake-3] Starting >>> message_generation [ make ]
[rosmake-0] Finished <<< rospack ROS_NOBUILD in package rospack[ roscpp_serialization: 0.0 sec ] [ message_generation: 0.0 sec ] [ 4 Active 9/23 Complete ]
No Makefile in package rospack
[rosmake-0] Starting >>> roslib [ make ]
[rosmake-1] Finished <<< roscpp_serialization ROS_NOBUILD in package roscpp_serialization
No Makefile in package roscpp_serialization
[rosmake-2] Finished <<< roslang ROS_NOBUILD in package roslang
No Makefile in package roslang
[rosmake-1] Starting >>> message_runtime [ make ]
[rosmake-2] Starting >>> xmlrpcpp [ make ]
[rosmake-3] Finished <<< message_generation ROS_NOBUILD in package message_generation
No Makefile in package message_generation
[rosmake-0] Finished <<< roslib ROS_NOBUILD in package roslib
No Makefile in package roslib
[rosmake-0] Starting >>> rosunit [ make ]
[rosmake-2] Finished <<< xmlrpcpp ROS_NOBUILD in package xmlrpcpp
No Makefile in package xmlrpcpp
[rosmake-0] Finished <<< rosunit ROS_NOBUILD in package rosunit
No Makefile in package rosunit
[rosmake-1] Finished <<< message_runtime ROS_NOBUILD in package message_runtime
No Makefile in package message_runtime
[rosmake-1] Starting >>> std_msgs [ make ]
[rosmake-2] Starting >>> rosbuild [ make ]
[rosmake-1] Finished <<< std_msgs ROS_NOBUILD in package std_msgs
No Makefile in package std_msgs
[rosmake-1] Starting >>> rosgraph_msgs [ make ]
[rosmake-2] Finished <<< rosbuild ROS_NOBUILD in package rosbuild
No Makefile in package rosbuild
[rosmake-1] Finished <<< rosgraph_msgs ROS_NOBUILD in package rosgraph_msgs
No Makefile in package rosgraph_msgs
[rosmake-2] Starting >>> rosconsole [ make ]
[rosmake-2] Finished <<< rosconsole ROS_NOBUILD in package rosconsole
No Makefile in ... (more) |
2015-08-27 14:39:24 -0500 | commented question | rosout is not built as you run roscore on raspberry pi Got the same isue with Indigo on raspbian wheezy right now. Was there a solution? |
2015-08-27 14:24:26 -0500 | received badge | ● Scholar
(source)
|
2015-08-27 14:24:25 -0500 | received badge | ● Supporter
(source)
|
2015-08-27 14:22:36 -0500 | commented question | ros indigo on a raspberry pi won't start because of missing roslaunch found out that export can do all that from the commandline - but is that really the way to do it? No config file or something like that? |
2015-08-27 13:34:35 -0500 | commented question | ros indigo on a raspberry pi won't start because of missing roslaunch Now i found export PYTHONPATH=$PYTHONPATH:/opt/ros/indigo/lib/python2.7/dist-packages
to solve that. Where would you put that line in? But now i get ROS master URI is not set
and will go on searching... |
2015-08-27 12:41:09 -0500 | received badge | ● Editor
(source)
|
2015-08-27 12:39:44 -0500 | asked a question | ros indigo on a raspberry pi won't start because of missing roslaunch I installed ros Indigo on a brand new raspbian wheezy follwing the tutorial from the wiki. I get this pi@RPiMower /opt/ros/indigo/bin $ sudo ./roscore
Traceback (most recent call last):
File "./roscore", line 62, in <module>
import roslaunch
ImportError: No module named roslaunch
but when i start python i can Import roslaunch without Problems. pi@RPiMower /opt/ros/indigo/bin $ python
Python 2.7.3 (default, Mar 18 2014, 05:13:23)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import roslaunch
>>>
What's wrong? |
2015-08-25 00:00:42 -0500 | answered a question | Why am I getting "python:any (>= 2.7.1-0ubuntu2) but it is not installable" on Raspian Wheezy? On a brand new Raspian Wheezy I geht this: The following packages have unmet dependencies:
python-rosdep : Depends: python:any (>= 2.7.1-0ubuntu2) but it is not installable
Depends: python-catkin-pkg but it is not going to be installed
Depends: python-rospkg (>= 1.0.34) but it is not going to be installed
Depends: python-rosdistro (>= 0.4.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
ERROR: the following rosdeps failed to install
apt: command [sudo -H apt-get install -y python-rospkg] failed
apt: command [sudo -H apt-get install -y python-catkin-pkg] failed
apt: command [sudo -H apt-get install -y python-rosdep] failed
apt: Failed to detect successful installation of [python-rospkg]
apt: Failed to detect successful installation of [python-catkin-pkg]
apt: Failed to detect successful installation of [python-
The unmet dependencies can't be ignored, right? |