I am using ssh to connect two computer under one ROS system. and I am using Moveit! plugin to plan path.but when I launch it, an error occurs
"MoveItSimpleControllerManager: Action client not connected: /joint_trajectory_action"
but when I do not launch SSH, it can work well.
So I suppose it's because of ssh. Maybe ip I am not sure.
Any comment will be appreciated. Thanks.
↧
run RViz under ssh but return an error"MoveItSimpleControllerManager: Action client not connected: /joint_trajectory_action"
↧
Rviz shows wrong world frame
I'm trying to add the camera to a scene (separated with the robot). I can receive the image and point cloud from simulation, but the world frame looks very wrong in Rviz, while it looks ok in Gazebo.
[This image](https://drive.google.com/file/d/1t6cfZ_j-drS49e8ez2HZ7f7ylx0fK2HU/view?usp=sharing) is the scene in Gazebo (world frame is around the table). And [this image](https://drive.google.com/file/d/1csRLRFdEiqtHjSNzAhVgDwbSdV363Oo3/view?usp=sharing) is from Rviz, which shows not correct frame (the robot model did not overlap with the point cloud of the robot recorded by the camera).
I did add a static tf transform from world to camera link in the launch file. Do we have a way to fix this?
↧
↧
Creating a subscriber
Hello guys, I'm trying to follow the tutorial here:[Markers: Basic shapes](http://wiki.ros.org/rviz/Tutorials/Markers:%20Basic%20Shapes)
I managed to get it to work until I do: **rosrun using_markers basic_shapes**
Then I get the following error:
> [ WARN] [1525948815.172388772]: Please create a subscriber to the marker
I open rviz, create a marker (as suggested on another discussion) but get an error message in rviz:
basic_shapes/0 frame [/my_frame]: Fixed Frame [map] does not exist
as well as this error in the terminal
[WARN] [1525951105.819784112]: MessageFilter [target=map ]: Dropped 100.00% of messages so far. Please turn the [ros.rviz.message_notifier] rosconsole logger to DEBUG for more information.
Thank you
↧
Error of Rviz: can't load class 'moveit_rviz_plugin/MotionPlanning'
Before what I did is introducing a new planner to ompl and building source moveit with source ompl. I already changed `ompl_planning.yaml` for pr2 robot and now I want to test my new planner for pr2 robot. After I launched `demo.launch` of pr2 robot, I met the following error:
ERROR: cannot launch node of type [moveit_ros_move_group/move_group]: can't locate node [move_group] in package [moveit_ros_move_group]
[ERROR] [1496781973.824232913]: PluginlibFactory: The plugin for class 'moveit_rviz_plugin/MotionPlanning' failed to load. Error: Could not find library corresponding to plugin moveit_rviz_plugin/MotionPlanning. Make sure the plugin description XML file has the correct name of the library and that the library actually exists.
Is this error because of my new adding planner? I followed the tutorial of ompl of how to add a new planner, there is no step to change any file for rviz. Do I need to modify any file of rviz in order to load motion planning? Appreciate it if anybody can give me some suggestion.
↧
Could not load panel in rviz -- PluginlibFactory: The plugin for class ...
Hello,
I have heavy problems with developing own panel i rviz. I have prepared everything, it compiles without warning but while loading, the rviz writes
> PluginlibFactory: The plugin for class> 'assistant_panel/Widget_interface'> failed to load. Error: Failed to load> library> /home/xxx/ws/ws_linux/devel/lib/libassistant_panel.so.> Make sure that you are calling the> PLUGINLIB_EXPORT_CLASS macro in the> library code, and that names are> consistent between this macro and your> XML. Error string: Could not load> library (Poco exception => /home/xxx/ws/ws_linux/devel/lib/libassistant_panel.so:> undefined symbol:> _ZTVN15assistant_panel16Widget_interfaceE)
Eveyrthing looks ok, but I am trying to solve it for last two days but I am failing.
link for the soft: https://drive.google.com/file/d/0B5_3aKfZ-sqNVHpQQ3o3YkV0S0k/view?usp=sharing
Files:
CMakeLists.txt
##############################################################################
# CMake
##############################################################################
cmake_minimum_required(VERSION 2.8.0)
project(assistant_panel)
##############################################################################
# Catkin
##############################################################################
# qt_build provides the qt cmake glue, roscpp the comms for a default talker
find_package(catkin REQUIRED COMPONENTS qt_build roscpp rviz)
include_directories(${catkin_INCLUDE_DIRS})
# Use this to define what the package will export (e.g. libs, headers).
# Since the default here is to produce only a binary, we don't worry about
# exporting anything.
catkin_package()
##############################################################################
# Qt Environment
##############################################################################
# this comes from qt_build's qt-ros.cmake which is automatically
# included via the dependency call in package.xml
rosbuild_prepare_qt4(QtCore QtGui) # Add the appropriate components to the component list here
##############################################################################
# Sections
##############################################################################
file(GLOB QT_FORMS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} ui/*.ui)
file(GLOB QT_RESOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} resources/*.qrc)
file(GLOB_RECURSE QT_MOC RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS include/assistant_panel/*.hpp)
QT4_ADD_RESOURCES(QT_RESOURCES_CPP ${QT_RESOURCES})
QT4_WRAP_UI(QT_FORMS_HPP ${QT_FORMS})
QT4_WRAP_CPP(QT_MOC_HPP ${QT_MOC})
##############################################################################
# Sources
##############################################################################
file(GLOB_RECURSE QT_SOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS src/*.cpp)
##############################################################################
# Binaries
##############################################################################
#add_executable(assistant_panel ${QT_SOURCES} ${QT_RESOURCES_CPP} ${QT_FORMS_HPP} ${QT_MOC_HPP} ${QT_MOC})
add_library(${PROJECT_NAME} ${QT_SOURCES} ${QT_RESOURCES_CPP} ${QT_MOC})
target_link_libraries(assistant_panel ${QT_LIBRARIES} ${catkin_LIBRARIES})
#install(TARGETS assistant_panel RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION})
install(TARGETS
${PROJECT_NAME}
ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
)
install(FILES
plugin_description.xml
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})
install(DIRECTORY media/
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}/media)
install(DIRECTORY icons/
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}/icons)
install(PROGRAMS scripts/send_test_msgs.py
DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION})
Package.xml
assistant_panel 0.1.0
assistant_panel ReMeDi ReMeDi BSD catkin qt_build roscpp libqt4-dev rviz rviz qt_build roscpp libqt4-dev
sddfsrfrfvg.
#include "ui_main_window.h"
#include "qnode.hpp"
#include
#include
#include
/*****************************************************************************
** Namespace
*****************************************************************************/
namespace assistant_panel {
/*****************************************************************************
** Interface [Widget_interface]
*****************************************************************************/
/**
* @brief Qt central, all operations relating to the view part here.
*/
class Widget_interface : public rviz::Panel {
Q_OBJECT
public:
// Widget_interface();
Widget_interface(QWidget *parent = 0);
~Widget_interface();
public Q_SLOTS:
/******************************************
** Auto-connections (connectSlotsByName())
*******************************************/
/******************************************
** Manual connections
*******************************************/
private:
Ui::Widget_interface ui;
//QNode qnode;
};
} // namespace assistant_panel
#endif // assistant_panel_MAIN_WINDOW_H
main_window.cpp
/**
* @file /src/main_window.cpp
*
* @brief Implementation for the qt gui.
*
* @date February 2011
**/
/*****************************************************************************
** Includes
*****************************************************************************/
#include
#include
#include
#include "../include/assistant_panel/main_window.hpp"
/*****************************************************************************
** Namespaces
*****************************************************************************/
namespace assistant_panel {
//using namespace Qt;
/*****************************************************************************
** Implementation [Widget_interface]
*****************************************************************************/
Widget_interface::Widget_interface(QWidget *parent)
: rviz::Panel(parent)
{
ui.setupUi(this); // Calling this incidentally connects all ui's triggers to on_...() callbacks in this class.
setWindowIcon(QIcon(":/images/icon.png"));
}
} // namespace assistant_panel
#include
PLUGINLIB_EXPORT_CLASS(assistant_panel::Widget_interface, rviz::Panel)
CMakeLists.txt
##############################################################################
# CMake
###################################################################
cmake_minimum_required(VERSION 2.8.0)
project(assistant_panel)
##############################################################################
# Catkin
##############################################################################
# qt_build provides the qt cmake glue, roscpp the comms for a default talker
find_package(catkin REQUIRED COMPONENTS qt_build roscpp rviz)
include_directories(${catkin_INCLUDE_DIRS})
# Use this to define what the package will export (e.g. libs, headers).
# Since the default here is to produce only a binary, we don't worry about
# exporting anything.
catkin_package()
##############################################################################
# Qt Environment
##############################################################################
# this comes from qt_build's qt-ros.cmake which is automatically
# included via the dependency call in package.xml
rosbuild_prepare_qt4(QtCore QtGui) # Add the appropriate components to the component list here
##############################################################################
# Sections
##############################################################################
file(GLOB QT_FORMS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} ui/*.ui)
file(GLOB QT_RESOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} resources/*.qrc)
file(GLOB_RECURSE QT_MOC RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS include/assistant_panel/*.hpp)
QT4_ADD_RESOURCES(QT_RESOURCES_CPP ${QT_RESOURCES})
QT4_WRAP_UI(QT_FORMS_HPP ${QT_FORMS})
QT4_WRAP_CPP(QT_MOC_HPP ${QT_MOC})
##############################################################################
# Sources
##############################################################################
file(GLOB_RECURSE QT_SOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS src/*.cpp)
##############################################################################
# Binaries
##############################################################################
#add_executable(assistant_panel ${QT_SOURCES} ${QT_RESOURCES_CPP} ${QT_FORMS_HPP} ${QT_MOC_HPP} ${QT_MOC})
add_library(${PROJECT_NAME} ${QT_SOURCES} ${QT_RESOURCES_CPP} ${QT_MOC})
target_link_libraries(assistant_panel ${QT_LIBRARIES} ${catkin_LIBRARIES})
#install(TARGETS assistant_panel RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION})
install(TARGETS
${PROJECT_NAME}
ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
)
install(FILES
plugin_description.xml
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION})
install(DIRECTORY media/
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}/media)
install(DIRECTORY icons/
DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}/icons)
install(PROGRAMS scripts/send_test_msgs.py
DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION})
Package.xml
assistant_panel 0.1.0
assistant_panel ReMeDi ReMeDi BSD catkin qt_build roscpp libqt4-dev rviz rviz qt_build roscpp libqt4-dev
sddfsrfrfvg.
#include "ui_main_window.h"
#include "qnode.hpp"
#include
#include
#include
/*****************************************************************************
** Namespace
*****************************************************************************/
namespace assistant_panel {
/*****************************************************************************
** Interface [Widget_interface]
*****************************************************************************/
/**
* @brief Qt central, all operations relating to the view part here.
*/
class Widget_interface : public rviz::Panel {
Q_OBJECT
public:
// Widget_interface();
Widget_interface(QWidget *parent = 0);
~Widget_interface();
public Q_SLOTS:
/******************************************
** Auto-connections (connectSlotsByName())
*******************************************/
/******************************************
** Manual connections
*******************************************/
private:
Ui::Widget_interface ui;
//QNode qnode;
};
} // namespace assistant_panel
#endif // assistant_panel_MAIN_WINDOW_H
main_window.cpp
/**
* @file /src/main_window.cpp
*
* @brief Implementation for the qt gui.
*
* @date February 2011
**/
/*****************************************************************************
** Includes
*****************************************************************************/
#include
#include
#include
#include "../include/assistant_panel/main_window.hpp"
/*****************************************************************************
** Namespaces
*****************************************************************************/
namespace assistant_panel {
//using namespace Qt;
/*****************************************************************************
** Implementation [Widget_interface]
*****************************************************************************/
Widget_interface::Widget_interface(QWidget *parent)
: rviz::Panel(parent)
{
ui.setupUi(this); // Calling this incidentally connects all ui's triggers to on_...() callbacks in this class.
setWindowIcon(QIcon(":/images/icon.png"));
}
} // namespace assistant_panel
#include
PLUGINLIB_EXPORT_CLASS(assistant_panel::Widget_interface, rviz::Panel)
↧
↧
Rviz receives LaserScan messages but doesn't display them
Hi there
I made a dummy package that is publishing fake laser scan messages (following this code: http://wiki.ros.org/navigation/Tutorials/RobotSetup/Sensors#Writing_Code_to_Publish_a_LaserScan_Message ).
I use this command to launch my package:
roslaunch beginner_tutorials fakeLaserScan.launch
Then, I try to display it with:
rosrun rviz rviz
Finally, I use this command in order to avoid fixed-frame related errors,:
rosrun tf static_transform_publisher 0 0 0 0 0 0 1 map fake_laser_frame 10
I set global_frame as "fake_laser_frame" and I add the topic /fakeScan (type LaserScan).
Everything seems to work great, only green checks and I can see the number of receives messages increase.
But I don't see my laser scan displayed ! I tried with a kinect and package "laserscan_kinect", it works.
What am I missing ?
More info:
What I'm trying to do : for the moment, juste learning really. My final is goal to use a Lidar Lite v3 to generate Laser Scan messages.
My code: https://github.com/erenaud3/fakeLaserScan
Screenshot: (I tried, but not enough reputation).
↧
rviz keeps displaying initial pose
When I use rviz, the initial state of the robot persists throughout the entire session. In the picture below, the robot started stretched out parallel to the ground then moved up into the higher pose. Everything in rviz seems to work fine but it would be nice to (a) know what's causing this artifact, and (b) not have that pose cluttering the view. Can you help me?
↧
What is the "Creating 1 swatches" info message ?
Hello,
I was debugging my program and I kept seeing a message displayed by rviz : "Creating 1 swatches".
With `rqt_console` here's what the message viewer says :
Node: /rviz
Time: 01:01:36.647000000 (1970-01-01)
Severity: Info
Published Topics: /initialpose, /move_base_simple/goal, /rosout
Creating 1 swatches
Location:
/tmp/binarydeb/ros-kinetic-rviz-1.12.15/src/rviz/default_plugin/map_display.cpp:MapDisplay::createSwatches:604
So I checked the [MapDisplay (line 604)](http://docs.ros.org/kinetic/api/rviz/html/c++/map__display_8cpp_source.html). I'm not sure to really get what this is exactly (from my understanding it's not related to my issue it's simply the creation of the views in rviz).
Can someone explain it to me ?
↧
subscribe field of message array
Hey there,
I would like to subscribe a field of a message array.
E.g. if my message looks like this:
**BallStates.msg:**
BallState[] ball_states
**BallState.msg:**
std_msgs/Header header
uint32 uid
geometry_msgs/Point position
Only the BallStates.msg is published. And I would like to subscribe to the first ball in this message with **message_filters**
self.topic2_sub = message_filters.Subscriber("/ball_states[0]/ball_state" , BallState)
ts = message_filters.TimeSynchronizer([self.topic1_sub, self.topic2_sub], 10)
ts.registerCallback(self.topic12_cb)
For that however I get this error:
ball_states[0]/ball_state' is not a legal ROS graph resource name. This may cause problems with other ROS tools
super(Subscriber, self).__init__(name, data_class, Registration.SUB)
However if I echo that topic in a terminal by **rostopic echo /ball_states[0]/ball_state** it works :)
Does anyone know a fast workaround to this?
I mean of course I can kind of publish the first ball in an extra message and subscribe to that one but this is actually not what I want.....
I would like to have a fast short solution that does not cost time....
Note something like this:
tag: remap from [/turtlebot3/ball_tracking/ball_states[0]] is not a valid ROS name.
XML is
↧
↧
"[ERROR]:link 'camera_link' is not unique" when trying to send sensor data from grazebo to moveit!
Hi,
I'm trying to send sensor data from Gazebo to MoveIt! to monitor the motion of a KUKA robot. In order to make a connection between the camera and the robot's coordinate system, I am trying to integrate the camera in the robot model by ...
- adding "
include filename="$(find kuka_kr16_support)/kinect_test_cam/camera_robot.xacro" /" to my kr16_2_macro.xacro file
- adding "xacro:include filename="$(find abb_irb1600id_support)/kinect_test_cam/camera_robot.xacro" / " to my kr16_2.xacro file
When I try to launch my launch file, I get the mentioned error. Can anybody help me please?
ROS environment variables:
declare -x ROSLISP_PACKAGE_DIRECTORIES="/home/rossystem/ws_mrk_fk/devel/share/common-lisp"
declare -x ROS_DISTRO="kinetic"
declare -x ROS_ETC_DIR="/opt/ros/kinetic/etc/ros"
declare -x ROS_MASTER_URI="http://localhost:11311"
declare -x ROS_PACKAGE_PATH="/home/rossystem/ws_mrk_fk/src/kr16_2_gazebo:/home/rossystem/ws_mrk_fk/src/kuka_kr16_support:/home/rossystem/ws_mrk_fk/src/kr16_2_moveit:/home/rossystem/ws_mrk_fk/src/launch_files:/opt/ros/kinetic/share"
declare -x ROS_ROOT="/opt/ros/kinetic/share/ros"
declare -x ROS_VERSION="1
My camera_robot.xacro:
↧
"No map recieved" in Rviz with RTABMap remote mapping
Hello!
I'm trying to do 3D mapping and navigation with ROS using Raspberry Pi 3 and XBOX Kinect 360 camera on Pioneer robot and laptop as a workstation from where I will be able to visualize and send commands to RPi3.
On my laptop, I am running Ubuntu 14.04 LTS 32-bit with ROS Kinetic, and on RPi3 Ubuntu Mate with ROS Kinetic also.
I had some success when launching RTABMap on RPi3, and using laptop for visualization only, but now I want to do it remotely, so for start I modified these two launch files:
https://github.com/introlab/rtabmap_ros/blob/master/launch/azimut3/az3_remote_mapping_robot.launch
https://github.com/introlab/rtabmap_ros/blob/master/launch/azimut3/az3_remote_mapping_rviz.launch
I'm providing the content of modified launch files below:
remote_robot.launch
↧
rviz couldn't display laserscan data correctly
I use gazebo as my simulation tool to generate data, and rviz to visualize the data, as I put camera or pointcloud into rviz it works well, but when it comes to laserscan it dosen't. I try to look into the information of the topic of laserscan, it tells me the topic was subscribed by rviz already, I don't know where the problem is? Furthermore, I use "rostopic echo /scan" to check out the data of the topic, then ranges are all -inf and intensities are all 1.0, was that normal? What should I do?
Thank you in advance
↧
hector_slam simulation has impredictable result
Hi everyone !
I am quite new to ROS and I'm trying to simulate hector_slam witout odom (only with laser scan). So I have this launch file:
↧
↧
Generate trajectory with moveIt based on sensor inputs
Hey there,
I would like to ask if it is possible to use MoveIt and generate a trajectory control law.
I would like to be able to write some Cpp Code using the MoveIt Library and some sensor Input topics (img or point clouds) and control according to these sensor inputs the endefector [of this kuka arm.](https://github.com/CesMak/kuka_arm)
Now what I already achieved was to connect RVIZ (moveIt) and gazebo. You also can check this out by checking [this link.](https://github.com/CesMak/kuka_arm) I am able to plan and execute a trajectory in moveit and it also will be executed in gazebo.
Now if somebody knows some examples on **how to control a trajectory with moveit library based on sensor input** I would be glat to here them.
Meanwhile I read [here](https://moveit.ros.org/documentation/concepts/):
> move_group talks to the robot through
> ROS topics and actions. It
> communicates with the robot to get
> current state information (positions
> of the joints, etc.), to get point
> clouds and other sensor data from the
> robot sensors and to talk to the
> controllers on the robot.
>> Controller Interface
>> move_group talks to the controllers on
> the robot using the
> FollowJointTrajectoryAction interface.
> This is a ROS action interface. A
> server on the robot needs to service
> this action - this server is not
> provided by move_group itself.
> move_group will only instantiate a
> client to talk to this controller
> action server on your robot.
If I also start my current kuka arm via:
roslaunch kuka_kr5_gazebo rviz_connected_with_gz_using_moveit.launch
I use currently use this controller (http://wiki.ros.org/joint_trajectory_controller) and an action server to connect rviz with gazebo:
/arm_controller/command
/arm_controller/follow_joint_trajectory/cancel
/arm_controller/follow_joint_trajectory/feedback
/arm_controller/follow_joint_trajectory/goal
/arm_controller/follow_joint_trajectory/result
/arm_controller/follow_joint_trajectory/status
should I also use this action server to execute a continuous trajectory with it according to my sensor input?
rostopic info /arm_controller/follow_joint_trajectory/goal
Type: control_msgs/FollowJointTrajectoryActionGoal
Publishers:
* /move_group (http://markus:44193/)
Subscribers:
* /gazebo (http://markus:46419/)
I also have several more topics running (just for additional information)
/joint_states
/move_group/cancel
/move_group/display_contacts
/move_group/display_planned_path
/move_group/feedback
/move_group/goal
/move_group/monitored_planning_scene
/move_group/ompl/parameter_descriptions
/move_group/ompl/parameter_updates
/move_group/plan_execution/parameter_descriptions
/move_group/plan_execution/parameter_updates
/move_group/planning_scene_monitor/parameter_descriptions
/move_group/planning_scene_monitor/parameter_updates
/move_group/result
/move_group/sense_for_plan/parameter_descriptions
/move_group/sense_for_plan/parameter_updates
/move_group/status
/move_group/trajectory_execution/parameter_descriptions
/move_group/trajectory_execution/parameter_updates
I just found some sources which do similar things I wanna do:
* http://wiki.ros.org/robotican/Tutorials/Arm%20manipulation
* http://wiki.ros.org/Industrial/Tutorials
* https://answers.ros.org/question/217959/movegroup-init-object-issue/
* http://wiki.ros.org/descartes/Tutorials/Getting%20Started%20with%20Descartes
↧
How to give Octomap data to the Planning Scene? (MoveIt!)
Hello,
I'm relatively new to MoveIt and ROS. For the past week, I have been trying to configure the 3D sensor (a Kinect) on my robot model to work in MoveIt!, following the tutorial [here](http://docs.ros.org/kinetic/api/moveit_tutorials/html/doc/pr2_tutorials/planning/src/doc/perception_configuration.html). Additionally, I created a node to launch the Octomap Server.
However, after completing these steps and firing up MoveIt!/Rviz with Gazebo, the Planning Scene doesn't contain any 3D data. I have checked the topics list, and my simulated robot is publishing the correct PointCloud2 data, and the Octomap server is running and publishing correct occupancy maps. What else is needed to get Octomap to publish the data to the Planning Scene?
Code:
config/sensors_kinect.yaml
sensors:
- sensor_plugin: occupancy_map_monitor/PointCloudOctomapUpdater
point_cloud_topic: /kinect/depth/points
max_range: 5.0
point_subsample: 1
padding_offset: 0.1
padding_scale: 1.0
filtered_cloud_topic: filtered_cloud
launch/sensor_manager.launch.xml
↧
Collada model axes
Hello guys,
Is there a way to display the axes of a collada model imported to rviz, like shown in the picture below
Will the axes display at the origin of the model (local axes) or at center of the world, and how about their orientation
↧
Problem with two huskies in navigation
I followed this https://answers.ros.org/question/41433/multiple-robots-simulation-and-navigation/ to make two huskies in navigation stack. When i launch navigation file and rviz I can set the map and both robots. TFs are all fine and I type correct tf_prefix to see robots, but they are always in the centre of the map and not in their correct position and models are not looking correctly because wheels are not showing. I tried using 2D pose and 2D nav goal and i changed topic for those actions. Using rostopic echo /husky1/move_base_simple/goal it shows change but robot is not moving. Both robots stay in the same place in gazebo and in rviz there's still only one robot in map.
↧
↧
Why the map color in RVIZ become yellow
The map color in RVIZ became yellow. I have no idea. Anyone can help me? plz.
↧
rviz Camera display incorporating CameraInfo operational parameters?
Does rviz support incorporating the operational parameters described in the camera_info message ([sensor_msgs/CameraInfo](http://www.ros.org/doc/api/sensor_msgs/html/msg/CameraInfo.html "CameraInfo")) when overlaying the data from elsewhere (robot model, tf, markers) while displaying a camera feed?
The source ([rviz camera display](https://github.com/ros-visualization/rviz/blob/groovy-devel/src/rviz/default_plugin/camera_display.cpp "rviz camera display")) shows creating a projection based on the camera height and width fields, as well as the projection camera matrix P - the calibration parameters. These are typically described by full camera frame calibration data [rep 104](http://www.ros.org/reps/rep-0104.html "rep 104"). Is rviz not following the CameraInfo rep? Should it create the projection matrix based on the roi and binning parameters?
↧
How to clear the OccupancyGrid map
Hi, I am using rviz to show real time OccupancyGrid map that is converted through pointcloud. The pointcloud is generated by current frame,but OccupancyGrid maps are constantly produced. Now, I just need to show OccupancyGrid of two consecutive frames.Therefore,other OccupancyGrid of outdated frames need to be cleared,otherwise the OccupancyGrid is getting bigger and bigger
This is my launch file:
↧