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

Praseen's profile - activity

2015-06-22 01:02:43 -0500 marked best answer getting basic hardware on Raspberry Pi working with ROS

Hello, I have a ROS Groovy Galapagos bare bones installation from binary on the Raspberry Pi which has a Raspbian wheezy running on it. Please let know how to use it for some simple hardware like a switch and an LED connected to to the RPi. I would like the switch to switch on/off the LED through the ROS installation on the RPi.

Thanks in advance, Praseen

2015-01-18 21:56:45 -0500 received badge  Famous Question (source)
2013-10-29 04:26:42 -0500 received badge  Famous Question (source)
2013-10-29 04:26:42 -0500 received badge  Notable Question (source)
2013-09-04 10:33:21 -0500 received badge  Famous Question (source)
2013-08-31 00:13:57 -0500 received badge  Popular Question (source)
2013-08-30 08:37:15 -0500 commented answer starting up roscore automatically on boot

will update after I try it

2013-08-30 08:34:11 -0500 received badge  Commentator
2013-08-30 08:34:11 -0500 commented answer starting up roscore automatically on boot

yes I am currently launching roscore as root manually. I have installed ROS as root on this system.

2013-08-30 02:51:57 -0500 asked a question starting up roscore automatically on boot

Hi guys, I have got a basic ROS running on a some hardware successfully, thanks to helpful pointers from this community (love you guys for that). Right now I am facing another seemingly difficult issue. I am trying to get the roscore process to autostart at boot so that I can get my robot to move about freely in the room. I have tried updating rc.local, crontab, and init.d update and also the autologin script. All of them fail to work. I am using Raspberry Pi hardware with raspbian wheezy linux and I need to start roscore as root on this hardware at boot up automatically. Please guide me towards accomplishing this.

Thanks and Regards to all, Praseen

2013-08-13 14:19:01 -0500 received badge  Famous Question (source)
2013-07-12 00:01:25 -0500 received badge  Notable Question (source)
2013-07-10 06:29:21 -0500 commented answer Error with catkin_make when building package beginner_tutorials

Hi William, thank you for your response. I am installing from source so that I will be able to modify the existing source and I can hopefully use this experience to get this working on the Raspberry Pi board on which I am working.

2013-07-08 09:50:42 -0500 received badge  Famous Question (source)
2013-07-07 13:53:33 -0500 commented question Error with catkin_make when building package beginner_tutorials

The wiki needs to be updated please. The command catkin_make_isolated works, but it builds all the packages in the catkin workspace and can take some time. Thanks a lot all, especially joq, for the response and support

2013-07-07 13:51:11 -0500 received badge  Notable Question (source)
2013-07-07 13:50:26 -0500 received badge  Supporter (source)
2013-07-07 11:58:46 -0500 commented question Error with catkin_make when building package beginner_tutorials

Hi joq, Thanks a ton for your response. Well I have two work spaces, one for catkin packages and the other for non-catkin packages. This file structure was created by Groovy itself. Please let me know how to proceed.

2013-07-07 11:51:11 -0500 received badge  Popular Question (source)
2013-07-05 11:48:47 -0500 received badge  Editor (source)
2013-07-05 08:14:04 -0500 asked a question Error with catkin_make when building package beginner_tutorials

Hi, I have installed a ROS groovy from source on Ubuntu 12.04 and working on the basic tutorial to get familiarised with ROS. As part of creating a message and service for the beginner_tutorials package mentioned in the basic tutorial I am getting the following error when I run catkin_make, given below is the error. Please let me know how to proceed.

Base path: /home/neo/ros_catkin_ws
Source space: /home/neo/ros_catkin_ws/src
Build space: /home/neo/ros_catkin_ws/build
Devel space: /home/neo/ros_catkin_ws/devel
Install space: /home/neo/ros_catkin_ws/install
WARNING: Metapackage "vision_opencv" must buildtool_depend on catkin.
WARNING: Metapackage "image_transport_plugins" must buildtool_depend on catkin.
WARNING: Metapackage "geometry" must buildtool_depend on catkin.
WARNING: Metapackage "perception_pcl" must buildtool_depend on catkin.
WARNING: Metapackage "image_common" must buildtool_depend on catkin.
WARNING: Metapackage "diagnostics" must buildtool_depend on catkin.
WARNING: Metapackage "geometry_experimental" must buildtool_depend on catkin.
WARNING: Metapackage "nodelet_core" must buildtool_depend on catkin.
####
#### Running command: "cmake /home/neo/ros_catkin_ws/src -DCATKIN_DEVEL_PREFIX=/home/neo/ros_catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/home/neo/ros_catkin_ws/install" in "/home/neo/ros_catkin_ws/build"
####
-- Using CATKIN_DEVEL_PREFIX: /home/neo/ros_catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/neo/ros_catkin_ws/install_isolated
-- This workspace overlays: /home/neo/ros_catkin_ws/install_isolated
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using CATKIN_TEST_RESULTS_DIR: /home/neo/ros_catkin_ws/build/test_results
-- catkin 0.5.66
-- BUILD_SHARED_LIBS is on
WARNING: Metapackage "vision_opencv" must buildtool_depend on catkin.
WARNING: Metapackage "image_transport_plugins" must buildtool_depend on catkin.
WARNING: Metapackage "geometry" must buildtool_depend on catkin.
WARNING: Metapackage "perception_pcl" must buildtool_depend on catkin.
WARNING: Metapackage "image_common" must buildtool_depend on catkin.
WARNING: Metapackage "diagnostics" must buildtool_depend on catkin.
WARNING: Metapackage "geometry_experimental" must buildtool_depend on catkin.
WARNING: Metapackage "nodelet_core" must buildtool_depend on catkin.
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 181 packages in topological order:
-- ~~  - bfl (plain cmake)
-- ~~  - angles
-- ~~  - bond_core (metapackage)
-- ~~  - camera_calibration
-- ~~  - common_msgs (metapackage)
-- ~~  - console_bridge
-- ~~  - class_loader
-- ~~  - convex_decomposition
-- ~~  - cpp_common
-- ~~  - diagnostics (metapackage)
WARNING: The metapackage 'diagnostics' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/diagnostics/CMakeLists.txt
-- ~~  - driver_common (metapackage)
-- ~~  - flann (plain cmake)
-- ~~  - genmsg
-- ~~  - gencpp
-- ~~  - genlisp
-- ~~  - genpy
-- ~~  - geometry (metapackage)
WARNING: The metapackage 'geometry' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/geometry/CMakeLists.txt
-- ~~  - geometry_experimental (metapackage)
WARNING: The metapackage 'geometry_experimental' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/geometry_experimental/CMakeLists.txt
-- ~~  - image_common (metapackage)
WARNING: The metapackage 'image_common' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/image_common/CMakeLists.txt
-- ~~  - image_pipeline (metapackage)
-- ~~  - image_transport_plugins (metapackage)
WARNING: The metapackage 'image_transport_plugins' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/image_transport_plugins/CMakeLists.txt
-- ~~  - ivcon
-- ~~  - message_generation
-- ~~  - message_runtime
-- ~~  - mk
-- ~~  - nodelet_core (metapackage)
WARNING: The metapackage 'nodelet_core' has no CMakeLists.txt. Please add one to the package source. You can use the following file: /home/neo/ros_catkin_ws/build/catkin_generated/metapackages/nodelet_core/CMakeLists.txt
-- ~~  - opencv2 (plain cmake)
-- ~~  - orocos_kdl ...
(more)
2013-07-04 11:13:01 -0500 received badge  Notable Question (source)
2013-06-27 06:14:54 -0500 received badge  Notable Question (source)
2013-06-26 13:21:43 -0500 received badge  Popular Question (source)
2013-06-26 01:04:48 -0500 asked a question porting ROS onto an autonomous Robot

Hi, I am working for sometime now (around 4 weeks) to try and port ROS onto a robot we have built using the Raspberry Pi as the main controller. This Robot has a variety of peripherals on it like a USB camera , Wifi Router, etc. All the peripherals are connected to the RPi (main controller) using I2C connectors. I am attempting to port the ROS onto this custom built robot. All the drivers for this robot are functional as such. But how do I get the robot vehicle to run ROS. Please let me know of some effective starting point/ link. I know that in this forum many have already done what I intend to do, please help me to get started in the right direction. Until now I have got ROS installed on my Ubuntu 12.04 laptop and onto an RPi board. I am currently working on the ROS basics tutorial, however it does'nt seem to cover, how to port ROS onto a custom built autonomous robot.

As part of this porting procedure, I feel that I need to do this step by step, as a result I am trying to first get ROS on the RPi working between a switch and an LED as a publisher/subscriber. I am not sure, how I need to go about doing this. Please let me know if my approach to solve the porting problem is correct too.

2013-06-25 05:06:10 -0500 received badge  Popular Question (source)
2013-06-25 02:07:54 -0500 commented answer Connecting ROS to external hardware

Hi dornhege, I am building this system as part of a building block for a robot, that is the reason why I wanted to use an I2C interface. However right now I am happy to just use some GPIOs to connect the LED and switch to the RPi. I would eventually want to use an I2C connector later.

2013-06-25 01:25:40 -0500 commented answer Connecting ROS to external hardware

Hi dornhege, I would be indebted, if it would be possible to let me know of a step by step procedure or a link containing an example solution for such a problem? So in this case the thread which you talk of should be used to implement an I2C send/receive?

2013-06-25 01:11:24 -0500 marked best answer Connecting ROS to external hardware

Hello, I have a ROS Groovy Galapagos bare bones installation from binary on the Raspberry Pi which has a Raspbian wheezy running on it. I intend to first connect an LED via an I2C connector to the Raspberry Pi, after this I intend to connect a simple switch via an I2C connector to the Raspberry Pi. How do I configure The ROS middleware installed on the Raspberry Pi to accept commands like ON/OFF from the switch and then convey it to the LED?. I am a beginner in ROS, with my limited understanding I believe I would need to make both the hardware switch and LED as nodes in ROS and the node for the LED as a subscriber and the node for the switch as a publisher. Please let know if I am wrong, else how can I go about doing what I require?

Thanks in advance, Praseen

2013-06-25 01:11:18 -0500 commented answer Connecting ROS to external hardware

Hi dornhege, How do I go about creating the ROS node required Which part of the tutorial tells how to create a node? I am working on the Basic Tutorial now. As mentioned in the question I also have an I2C connector connecting the Rasberry Pi and the switches and the LED. Will that make a difference?

2013-06-25 01:07:09 -0500 received badge  Scholar (source)