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 |
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that doesn't exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
| | 2 | No.2 Revision |
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that doesn't exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used
Ubuntu Lucid, electric /home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class | | 3 | No.3 Revision |
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that doesn't exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
| | 4 | No.4 Revision |
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that doesn't might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
| | 5 | No.5 Revision |
Regarding First of all, regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
More direct solution to your question could be that since ROS is distributed system, you could receive messages from your robot on different computers that run fuerte or higher where rqt is available.
| | 6 | No.6 Revision |
First of all, regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
More direct solution to your question could be that since ROS is distributed system, you could receive messages from your robot on different computers that run fuerte or higher where rqt is available.
| | 7 | No.7 Revision |
First of all, regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
More direct solution to your problem could be that since ROS is distributed system, you could receive messages from your robot (as long as they're published as ROS format) on different computers that run fuerte or higher where rqt is available.
| | 8 | No.8 Revision |
First of all, regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
More direct Direct solution to your problem could be that since ROS is distributed system, you could receive messages from your robot (as long as they're published as ROS format) on different computers that run fuerte or higher where rqt is available.
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So if you dare to workaround even further, rqt may work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
| | 9 | Clarify that the rqt branch I used was the oldest possible and there's probably no rqt that's intended for electric |
Direct solution to your problem could be that since ROS is distributed system, you could receive messages from your robot (as long as they're published as ROS format) on different computers that run fuerte or higher where rqt is available.
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that is the oldest branch afaik, and also doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So So, if you dare to workaround even further, rqt may or may not work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
| | 10 | Add rqt recommendation |
Direct solution to your problem could be that since ROS is distributed system, you could receive messages from your robot (as long as they're published as ROS format) on different computers that run fuerte or higher where rqt is available.
Regarding rqt as @joq suggests, I actually tried using it on electric recently and my answer is no it's impossible/not worth trying.
I used fuerte-devel branch (that is the oldest branch afaik, and also doesn't use catkin to build) of rqt which also requires qt_gui_core and python_qt_binding with same branch names on github. When I run rosmake qt_gui_core I got the following error which seems to depend on a pluginlib's function that might not exist in electric. So, if you dare to workaround even further, rqt may or may not work. I'm curious.
Used Ubuntu Lucid, electric
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/src/qt_gui_cpp/recursive_plugin_provider.cpp:68: instantiated from here
/home/rosuserian/ROS/qt_gui_core/qt_gui_cpp/include/qt_gui_cpp/ros_pluginlib_plugin_provider.h:237: error: ‘class pluginlib::ClassLoader<qt_gui_cpp::PluginProvider>’ has no member named ‘createInstance’
(Added on Jan 12) Another answer based on comments on @alfa_80's answer, is again, rqt. You can open RViz and dynamic_reconfigure's GUI called rqt_reconfigure at the same time on a single window. Using Groovy is ideal though.
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.