David Galdeano's profile - activity

It works but maybe not in your case, as explained here: https://stackoverflow.com/questions/4...

No, since raspberry pi 2 (armv7), you can install pre build packages on Raspbian too using the Ubuntu arm installation. No need to build from sources.

Hi!

You should use rosserial_arduino package; It has a lot of tutorials and can be easily extended:

http://wiki.ros.org/rosserial_arduino...

Hi!

On raspberry pi 2 with raspbian, you should follow the arm installation:

http://wiki.ros.org/indigo/Installati...

and you can't have the desktop version, because all package haven't be build for arm processor. You can check package availability here:

http://repositories.ros.org/status_pa...

0 to 255 is the range of char; to use ascii use atoi() function (ascii to integer) or equivalent to make a char.

ok, try to upgrade only the 280 (or 150) to 512 part. You can try to lower the use of nh.spinOnce() by using larger delay in your code, to be sure that the spped of usb com is not the bottleneck.

if you just make the change on sketchbook/Libraries/ros_lib/ros.h it should be ok! Run rosrun rosserial_arduino make_libraries.py is only for the case of changing the original sources of the rosserial lib.

changing from 6,6,150,150 to 100,100,150,150 will change the number of Publishers/Subscribers from 6 to 100 and do not change the buffer size (150). try to change:

typedef NodeHandle_<arduinohardware, 25,="" 280="" 280,=""> NodeHandle;

to

typedef NodeHandle_<arduinohardware, 25,="" 512="" 512,=""> NodeHandle;

in 'rosserial/rosserial_arduino/src/ros_lib/ros.h' if you use the ATmega328P. Dont forget to run make_libraries.py. If you are using an arduino uno, think of upgrading to a arduino mega.</arduinohardware,&gt;<>

Downvote a question or an answer make you loose 2 karma points.

You must create a sketchbook/libraries folder in your home folder. The rosrun rosserial_arduino make_libraries.py can be then executed to create ros_lib directory.

To make a 3D point cloud to sense the environement.

This is realy precise.

Some explaination and results here: http://www.ais.uni-bonn.de/papers/SSRR_2013_Schadler_3D_Laser_Mapping_Tracking.pdf

Kinematics loop crated in parallel robots contain physical constraints which must be solve at high rate, maybe ROS is not adapted for these constraints and cant separate the command algorithms and the motor control. You can write a small controller (IK) for the robot an take advantage of the ROS framework by using its own communication mechanisms.

Hello, See here: http://answers.ros.org/question/9050/using-ros-for-a-delta-robot/

I think that your: pub_data.publish(tw); and publisher related stuff must go in tour callback function.

Something like that:

class PublishData
{
  ros::NodeHandle n;
  ros::NodeHandle n1;
  geometry_msgs::Twist tw;
public:
  PublishData()
  {
    tw.linear.x = 0.1;
    ros::Publisher pub_data = n.advertise<geometry_msgs::Twist>("/mobile_base/commands/velocity", 10);
    ros::Subscriber bumper = n.subscribe("/mobile_base/events/bumper",1,callback);
    ROS_INFO("DataPublished");
    while(ros::ok())
    {
        //ROS_WARN("In Loop.");
        ros::spin();
    }
  }
  void callback(const kobuki_msgs::BumperEventConstPtr msg)
  {
     ROS_ERROR("MOVE!!! Bumper pressed.");
     ROS_INFO("MOVE!!! Bumper pressed.");
     pub_data.publish(tw);
  }
};

For numpy use: http://wiki.ros.org/rospy_tutorials/Tutorials/numpy For syncronisation of several topics use: http://wiki.ros.org/message_filters#Policy-Based_Synchronizer_.5BROS_1.1.2B-.5D

I do not understand, why would you access the data on the rosbag file, while you have the real time data published? If you still need to manipulate bag files, use: http://wiki.ros.org/rosbag/Code%20API#cpp_api but as said in the begin of the document: 'Note that the rosbag API's are not thread-safe for reading and writing any given bag file. Users of the APIs must ensure no concurrent input/output operations are performed on different threads.' So you can't read and write at the same time.

Hello, you can subscribe to /chatter1 and /chatter1 with a node while rosbag is running. You can have many subscriber to one publisher.

Hello, use the command tool rosbag record -a to record in a bag file.

See: http://wiki.ros.org/rosbag/Tutorials/Recording%20and%20playing%20back%20data

If you really need the API for python, see: http://wiki.ros.org/rosbag/Code%20API where read and write from python to a bag file are detailled.

Hello, you should create an intermediate node wich subscribe to /mobile_base/events/bumper and publish on /mobile_base/commands/velocity. In this node, create your reactive behaviour.

No need of pipes and sockets, the publisher/subscriber mechanism is develloped to allows the communications.

Declare the lib:

#include <std_msgs/Float64MultiArray.h> //include the lib

use it:

std_msgs::Float64MultiArray Atest; //declare Atest
Atest.data.resize(5); //resize the array to assign to existent values
Atest.data[4] = 5; //put the desired value

Mostly because it is too heavy to run on the beableboard, since it is useless to take time to do the port. Some tried: http://answers.ros.org/question/52098/unable-to-compile-rviz-on-ubuntu-armhf/ but i have no echo of a succesful build.

The Beableboard runs on an arm processor.

Rviz is likely too heavy to run on the Beaglebone.

However, you can launch rviz on a distant computer and visualise data on the distant computer using: http://wiki.ros.org/ROS/Tutorials/MultipleMachines

Hello, if you want to visualize them on rviz (ROS 3D viewer), this tread can help: http://answers.ros.org/question/10177/query-on-urdfxacro-file/

This can help too: http://wiki.ros.org/sw_urdf_exporter

Hello, in http://wiki.ros.org/rosserial_arduino/Tutorials/Arduino%20IDE%20Setup follows the steps "3.2 Installing from Source onto the ROS workstation" and "3.3 Install ros_lib into the Arduino Environment" when you install rosserial on the raspberry pi.

Instalation from binaries is broken ("3.1 Installing Binaries on the ROS workstation"). This is due to https://github.com/ros-drivers/rosserial/issues/79 and have been fixed on sources but not in the raspbian build farm.

This works with rosserial/groovy/raspbian