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 |
You can get a snapshot build from the SVN snapshot directory which will have getTurnRate in it. However, nxt_lcp_proxy does not work very well, and I may remove it. getTurnRate was a mistake and I will get rid of it some time. You are better off running nxt_proxy, which should work with lejos 0.9.1. This requires that you run the ROSResponder sample on the NXT. It works quite well for me. You will need to get ROSResponder from SVN. I need to find a solution to the hard-coded dependencies in the gradle build file. I am currently waiting for a response of my "rosjava message serialization problems" query before I do further work on nxt_lejos as it is stopping odometry and imu messages working properly, which means that parts of the navigation stack do not work.
| | 2 | No.2 Revision |
You can get a snapshot build from the SVN snapshot directory which will have getTurnRate in it. However, nxt_lcp_proxy nxt_lejos_lcp_proxy does not work very well, and I may remove it. getTurnRate was a mistake and I will get rid of it some time. You are better off running nxt_proxy, nxt_lejos_proxy, which should work with lejos 0.9.1. This requires that you run the ROSResponder sample on the NXT. It works quite well for me. You will need to get ROSResponder from SVN. I need to find a solution to the hard-coded dependencies in the gradle build file. I am currently waiting for a response of my "rosjava message serialization problems" query before I do further work on nxt_lejos as it is stopping odometry and imu messages working properly, which means that parts of the navigation stack do not work.
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.
