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

ROS Listener (Hydro) Not Working

asked 2014-02-13 11:11:12 -0500

Hon Ng gravatar image

updated 2014-04-20 14:09:27 -0500

ngrennan gravatar image

Android 4.2.2, Android 4.1.2, Ubuntu 12.04, Android Studio 0.4.4, ROS Hydro

Hi, I have recently tried to run the listener (obtained from Google Play) through Robot Remocon, but after the "Starting Listener" dialog box disappeared, no new view (window) is opened, it is still on the main layout of the Remocon, with the Listener highlighted blue (indicating running app), and the ability to stop the app. Apart from that, even though a new ROS topic is created under "/turtlebot/chatter", I can't see any data on my device (since apparently the rosTextView has failed to be opened?).

I would really appreciate it if anyone can look into this.

PS: I have tried to compile the code from "android_apps" under Android Studio myself, and the same problem has occurred.

edit retag flag offensive close merge delete


Do you have your ROS_IP/ROS_HOSTNAME variables set?

Daniel Stonier gravatar image Daniel Stonier  ( 2014-02-17 18:23:17 -0500 )edit

Yes, otherwise, the Robot Remocon App will not connect successfully to the turtlebot, right?

Hon Ng gravatar image Hon Ng  ( 2014-02-18 12:44:36 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-02-18 20:51:17 -0500

Daniel Stonier gravatar image

The robot remocon is not just a way of starting android apps, you can also use it to just fire up launch configurations on the robot. That's what you are seeing here (albeit unintentionally). You'll note that there are two rocon rapps available, one is talker, one is listener.

The talker rapp has a launcher that starts a ros tutorials talker on the robot. In that configuration file, you'll also see it has a defined pairing client for android - a listener android app. i.e. the robot starts the launcher, the android starts the pairing client.

The listener rapp doesn't have a pairing client (yet - simply because we never got around to writing it). So it fires up the listener on the robot, but doesn't do anything on the robot side.

This behaviour can be useful if you just want to use the robot remocon for starting and stopping launch configurations on your robot.

edit flag offensive delete link more


Ok, I see, thank you. But unfortunately, the source code for the talker is not on here: Or did I missed something?

Hon Ng gravatar image Hon Ng  ( 2014-02-19 14:38:15 -0500 )edit

It's the The robot side runs the 'talker', the android side is the 'listener'. It's a bit confusing, but we went with the convention of naming robot apps from the robot's perspective for this pairing mode.

Daniel Stonier gravatar image Daniel Stonier  ( 2014-02-19 14:58:33 -0500 )edit

Ok, that makes more sense. Cheers! =D

Hon Ng gravatar image Hon Ng  ( 2014-02-23 17:46:54 -0500 )edit

Question Tools


Asked: 2014-02-13 11:11:12 -0500

Seen: 975 times

Last updated: Feb 18 '14