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

Marc's profile - activity

2016-05-08 15:18:06 -0500 received badge  Famous Question (source)
2014-12-17 10:03:16 -0500 answered a question AR DRONE 2.0 Tracking

Hi,

I think this is a multi-faceted problem... First, you'll have to make sure you know how to implement high-level control with ardrone_autonomy (which is pretty straight forward if you look at https://github.com/AutonomyLab/ardron... ). Then you'll have to use the stream from the camera (which is either the bottom camera or the front camera, but I believe definitely not both at the same time) and forward it to/subscribe to it from your node which does the OpenCV stuff. There you'll also generate the high level commands based on what you figure out with OpenCV. If you then transform everything correctly from the camera frame to the ardrone frame you should be able to send it cmd_vel commands based on the output of your OpenCV algorithm. Re. the two different cameras, I think there is a service you can call to switch between the active cameras to be transmitted over wifi, if I remember correctly.

Those are just my first thoughts, but I think if you go that route it should be easily doable... Just read into ardrone_autonomy documentation and also have a look at the tum_ardrone package. It uses PTAM for localization, which is an old method but a good start.

Best Regards, Marc

2014-12-16 13:19:07 -0500 answered a question Alternate source of repositories for ROS on UbuntuARM

Just found this: http://answers.ros.org/question/19942... should be back up soon.

2014-12-16 13:15:30 -0500 answered a question how a subscriber can chage a subscribed topic?

Hi, take a look at remapping arguments.

2014-12-16 12:58:08 -0500 received badge  Supporter (source)
2014-12-16 11:49:38 -0500 answered a question How to convert from geometry_msgs PoseWithCovariance to nav_msgs Odometry?

Look into the ETHZASL_MSF package...

2014-12-16 11:49:38 -0500 answered a question Alternate source of repositories for ROS on UbuntuARM

Having the same issue here with a Jetson TK1. Is there some alternative source somewhere?

Thanks, Marc

2014-11-21 12:34:52 -0500 received badge  Enthusiast
2014-09-04 04:10:36 -0500 received badge  Notable Question (source)
2014-06-29 06:52:50 -0500 received badge  Popular Question (source)
2014-06-25 03:48:35 -0500 commented answer Problems when installing segway-rmp package

Is it possible the setup.bash is corrupted? Is there a way to reset it together with the other files in /opt/ros/hydro? Thanks a lot!

2014-06-25 03:45:59 -0500 commented answer Problems when installing segway-rmp package

I got onto that route after searching... I reset my .bashrc file by copying an original from etc/skel. With that setup, I am able to start a new terminal, but obviously I lost all my ROS stuff since the environmental vars are not there anymore. I try to re-add ROS source, but the terminal hangs.

2014-06-25 03:03:54 -0500 asked a question Problems when installing segway-rmp package

Hi!

I am using ROS Hydro on Ubuntu 12.04. I downloaded the segway-rmp-ros-pkg from here:

http://wiki.ros.org/segway_rmp

I followed all the steps up until doing the rosinstall. I put in the wrong path to the ros directory and got the according error message, until I realized that it was in /opt/ros/hydro. After running that command succesfuly, I was prompted to run a "source" command by rosinstall. After doing so, I was not able to proceed to the next step, which is running roscd segway_rmp. This is, however, not the main issue. I closed the terminal and tried opening a new one, but whenever I now open a Terminal, I don't get the $ sign with username, but the terminal is completely empty. Only when I hit ctrl-c do I get the command line back. Sometimes, when I hit ctrl-c, I get a message telling me about latest tracebacks, all going to python files. I am unsure what went wrong here, maybe someone can help me!

I already restarted the computer, but I keep getting the same issue with every new terminal I open.

Thanks, Marc