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

pcler's profile - activity

2022-03-31 20:44:25 -0500 received badge  Good Question (source)
2021-01-06 04:01:40 -0500 received badge  Nice Question (source)
2019-12-27 05:44:06 -0500 received badge  Student (source)
2016-12-28 06:58:18 -0500 received badge  Famous Question (source)
2016-05-15 04:48:49 -0500 marked best answer About Subscriber Structure and “latch” on Publisher

Hi everyone. Recently I met a question when I read something about "latch" in Publisher. On the Publisher wiki page, "latch" is described as:(http://wiki.ros.org/rospy/Overview/Publishers%20and%20Subscribers)

    "Enable 'latching' on the connection. When a connection is latched, the last message published is saved and sent to any future subscribers that connect. This is useful for slow-changing or static data like a map."

Now I am so confused that [when a node subscribes a message from a topic, will this message disappears? If not, than what is "latch" for? Anyhow the last message will NOT disappear.]

PS. I have done some experiments. When several nodes subscribe a same topic, they always get the same messages content from that topic. And this can also explain how qrt_plot works.(It always subscribe messages from some topics but it never affects other nodes working)

2016-04-27 09:38:48 -0500 received badge  Notable Question (source)
2016-03-16 22:06:33 -0500 received badge  Popular Question (source)
2016-03-16 09:39:39 -0500 commented answer Fail to make hector_gazebo_thermal_camera

Yes, I can find the relative .py file of the message now. Now it seems that the pre-build of driver_base succeeded! Thank you so much!

2016-03-16 05:09:03 -0500 received badge  Commentator
2016-03-16 05:09:03 -0500 commented answer Fail to make hector_gazebo_thermal_camera

I use "catkin_make --pkg driver_base" to pre-build the pkg. But it doesn't work

2016-03-16 05:05:41 -0500 commented answer Fail to make hector_gazebo_thermal_camera

Thank you for your reply! I have download the driver_base source and placed it inside the ROS workspace. There has been a command "find_package(catkin REQUIRED COMPONENTS nodelet image_transport dynamic_reconfigure driver_base gazebo_plugins)" in the CMakeLists of hector_gazebo_thermal_camera

2016-03-15 23:10:01 -0500 asked a question Fail to make hector_gazebo_thermal_camera

Recently I am building hector_quadrotor(http://wiki.ros.org/hector_quadrotor) package. It needs another package named hector_gazebo_thermal_camera(inside http://wiki.ros.org/hector_gazebo ).

Using catkin_make, the building is successful on X86-Ubuntu14.04-Indigo, but failed on ARMv7l-Ubuntu14.04-Indigo. The error message is showed below:

[ 13%] Generating dynamic reconfigure files from cfg/GazeboRosThermalCamera.cfg: /home/chris/ros_ws/devel/include/hector_gazebo_thermal_camera/GazeboRosThermalCameraConfig.h /home/chris/ros_ws/devel/lib/python2.7/dist-packages/hector_gazebo_thermal_camera/cfg/GazeboRosThermalCameraConfig.py
Traceback (most recent call last):
File "/home/chris/ros_ws/src/hector_gazebo/hector_gazebo_thermal_camera/cfg/GazeboRosThermalCamera.cfg", line 5, in <module>
    from driver_base.msg import SensorLevels
ImportError: No module named msg
make[2]: *** [/home/chris/ros_ws/devel/include/hector_gazebo_thermal_camera/GazeboRosThermalCameraConfig.h] Error 1
make[1]: *** [hector_gazebo/hector_gazebo_thermal_camera/CMakeFiles/hector_gazebo_thermal_camera_gencfg.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

P.S. It is hard to install dependencies into ARM platform. Because most of them don't provide the ARM versions. I built a lot of dependencies from source. Will this error is leaded by the dependency mistaking installed?

Thank you for helping me out!

2016-01-07 00:53:23 -0500 received badge  Famous Question (source)
2015-10-28 04:07:24 -0500 received badge  Notable Question (source)
2015-10-28 02:31:32 -0500 received badge  Enthusiast
2015-10-27 02:25:43 -0500 commented answer Building mavros fail

Thank you so much! After I add 2G more swap then this error disappeared. The platform already owns 2G memory. I think the linking job of the package is really heavy

2015-10-27 02:21:58 -0500 received badge  Scholar (source)
2015-10-27 02:21:49 -0500 commented question Building mavros fail

Thank you so much! It does be the problem of memory limited! This error came out on different object file, so at first I was not sure whether it was the problem of compiler.

2015-10-27 01:10:58 -0500 received badge  Popular Question (source)
2015-10-26 09:50:33 -0500 received badge  Editor (source)
2015-10-26 09:48:51 -0500 asked a question Building mavros fail

Hi, all

I am having trouble with catkin_make mavros package error recently. It kept failing and saying:

c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [mavros/mavros/CMakeFiles/mavros.dir/src/lib/uas_stringify.cpp.o] Error 4
make[3]: *** Waiting for unfinished jobs....
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [mavros/mavros/CMakeFiles/mavros.dir/src/lib/uas_data.cpp.o] Error 4
make[2]: *** [mavros/mavros/CMakeFiles/mavros.dir/all] Error 2
make[1]: *** [mavros/mavros/CMakeFiles/mavros.dir/rule] Error 2
make: *** [mavros] Error 2
Invoking "make mavros -j4 -l4" failed

I am using an armv7l embed platform.

The mavros package is clone from https://github.com/mavlink/mavros , master branch.

Using ROS Indigo and Ubuntu 14.04

I would be really grateful if somebody can do any help. Thank you so much!

2015-07-27 22:37:06 -0500 received badge  Popular Question (source)
2015-07-27 22:37:06 -0500 received badge  Notable Question (source)
2015-07-21 21:53:57 -0500 received badge  Famous Question (source)
2015-03-03 01:41:17 -0500 received badge  Famous Question (source)