The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Have you checked the standard pubsub tutorial?
From what I can see, you need to specify the message type to the ROS text view: https://github.com/rosjava/android_core/blob/0.3.3/android_tutorial_pubsub/src/org/ros/android/android_tutorial_pubsub/MainActivity.java#L43-L55. Other than that, the message callable looks OK.
| | 2 | No.2 Revision |
Have you checked the standard pubsub tutorial?
From what I can see, you need to specify the message type to the ROS text view: https://github.com/rosjava/android_core/blob/0.3.3/android_tutorial_pubsub/src/org/ros/android/android_tutorial_pubsub/MainActivity.java#L43-L55. Other than that, the message callable looks OK.
You could also use a single node that parses the whole NavSatFix message and builds a single string representation out of it.
| | 3 | No.3 Revision |
Have you checked the standard pubsub tutorial?
From what I can see, you need to specify the message type to the ROS text view: https://github.com/rosjava/android_core/blob/0.3.3/android_tutorial_pubsub/src/org/ros/android/android_tutorial_pubsub/MainActivity.java#L43-L55. Other than that, the message callable looks OK.
You could also use a single node that parses the whole NavSatFix message and builds a single string representation out of it.
EDIT: Yes, the problem probably is that the Android device is not solving the hostname.
Try using ROS_IP environment variable on the publisher side. See http://wiki.ros.org/ROS/NetworkSetup and https://github.com/rosjava/android_core/issues/301 for reference.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
