Freyr's profile - activity

Multiple visuals work in rviz but seem to pick up the material of the first visual element defined. Not sure if that is a bug or just not supported. Anyway I can define fewer links and joints which was the point.

That is certainly useful to know. I'll try it out for visuals and see what happens.

I'm in the process of creating a URDF description for my quadruped robot. I have a bunch of bioloids frames and motor models but if I define the leg chains using them I end up with a bunch of fixed joints that do nothing except allow me to define geometries and visuals. Is that to be expected? Should I try to 'bake' the models into single shapes? How do the fixed joints affect KDL chains generated from the description? Does the performance suffer?

Are there any best practices in this regards?

Worked for me pretty much as is. I stuck to the ros-comm package to save build time mostly and that worked fined. Are you using the vanilla Raspbian Wheezy image as base? Most of the actual ROS packages are build locally. Could you point to the actual part/line where the install failed?

I followed the indigo ROS raspberry pi tutorial from the wiki with my B+ and it is working pretty good so far. I have been avoiding running the desktop and operate in command line via SSH (putty) using wifi.

As mentioned the Raspberry Pi 2 is out now at the same price point with an ARM7 architecture. A member of the ROS community has been working on ready packages for the ARM7 but there are currently no plans for ARM6 support that I know of. Building from source works for most of the part thought but it takes a while.

Raspberry Pi 2 is being announced these days with a quad 900Mhz ARMv7 and 1GB RAM so maybe I will have the entire cake and eat it in the end. I'll be looking for your packages when I get my hands on one :)

Operation was a success. Pull request made. Life is good again, many thanks.

I'm trying to add the arbotix stack to my raspberry pi jessie/indigo setup and rosdep is failing to resolve the following

ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
warehouse_ros: No definition of [mongodb] for OS [debian]
diagnostic_common_diagnostics: No definition of [libsensors4-dev] for OS [debian]

Both of these are installed via apt-get but that does not seem to satisfy rosdep. I'm at a loss as to how I can resolve these. Do I have to get the source directly and build them?

I'm using the following to resolve the dependencies

rosdep install --from-paths src --ignore-src --rosdistro indigo -y --os=debian:jessie

Are there any plans for building and providing a standard repository for armhf packages compatible with the likes of Rasbian?

Raspberry Pi seem like a great gateway drug for getting into ROS given how cheap, relatively powerful and well supported platform it is. Seem like a very sensible/obvious first choice when upgrading a robot to include a computer capable of running a full blown OS. The rather convoluted, shaky and time consuming process of building the environment and trying to get different packages is pretty intimidating if your not already a ROS veteran and a competent linux buff. I can claim neither.

I have come across a willow garage effort by Paul Mathieu in mid 2013 for groovy (including buildfarm instructions) which looks great but I don't see any indication that it was ever taken further or updated since.

Having prowled through the ROS tutorials (via ROS in a VM) and being thoroughly impressed by it's capabilities I only imagine the satisfaction of being able to start operating ROS on a fresh $40 RPi with in minutes of powering it on for the first time.

I myself am one of those amateur robot builder trying to upgrade from a arduino based arbotix include a RPi and I know it has all the tools I need but getting them to work remains a pretty convoluted process still.

I just want to tank you for this image as it seems to fit my needs very will right now. I'm a ROS n00b and have been having problems getting a stable ros image setup from the default wheezy image. I shall give it a spin tonight. Not sure what the significance of going for Jessie over Wheezy has especially since it is not yet released.

looks like the pcl does not list the indigo distribution. Is it not available yet? Would expect a lot of the top level stacks to break if that was the case. Should I be trying out the hydro distribution instead?

I'm trying to setup the ros stack for indigo on my raspberry pi B+ according to

http://wiki.ros.org/ROSberryPi/Instal...

I deviate from the script and specified the robot and perception package and during the actual building of the workspace I get problems from the pcl_conversions package. FindPCL.cmake seems to be missing causing tears.

This is what I get:

By not providing "FindPCL.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "PCL", but
CMake did not find one.

Could not find a package configuration file provided by "PCL" with any of
the following names:

 PCLConfig.cmake
 pcl-config.cmake

Add the installation prefix of "PCL" to CMAKE_PREFIX_PATH or set "PCL_DIR"
to a directory containing one of the above files.  If "PCL" provides a
separate development package or SDK, be sure it has been installed.

I'm quite new to ros so this is a major stumbling block for me. I found some references that PCL needed to tweek some flags in the build scripts in src/pcl but there is no sorce code there for pcl. Where should pcl be coming from? shouldn't the dependency resolve step figure out I need this one?

At a loss here, any help appreciated.