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

muin028's profile - activity

overview network karma followed questions activity
2020-05-31 04:04:17 -0500 received badge ● Famous Question (source)
2020-05-31 04:04:17 -0500 received badge ● Notable Question (source)
2015-12-08 04:15:21 -0500 received badge ● Famous Question (source)
2014-04-02 14:28:49 -0500 received badge ● Notable Question (source)
2014-01-28 17:26:51 -0500 marked best answer creation of cbp file

how to make cbp file for my ros package in order to run cmake file. more specifically i want to edit my CPP file in QtSDk IDE.can anybody help?

2014-01-28 17:26:45 -0500 marked best answer subscriber and publisher node

hello, i am tying to create two nodes-two topics,in which 1.node1 is publishing in topic1 and node2 is subscribing to topic1. 2.node2 is publishing in topic2 and node1 is subscribing to topic2. can anybody give some clue/hints
2013-10-06 21:28:13 -0500 received badge ● Famous Question (source)
2013-05-29 08:36:57 -0500 received badge ● Famous Question (source)
2013-02-02 00:41:28 -0500 received badge ● Famous Question (source)
2013-01-18 09:48:40 -0500 received badge ● Notable Question (source)
2013-01-02 13:20:56 -0500 received badge ● Popular Question (source)
2012-12-31 02:31:57 -0500 received badge ● Popular Question (source)
2012-12-28 08:42:01 -0500 received badge ● Editor (source)
2012-12-28 08:24:13 -0500 asked a question problem with package shape_msgs

common_msgs: actionlib_msgs | diagnostic_msgs | geometry_msgs | nav_msgs | sensor_msgs | shape_msgs | stereo_msgs | trajectory_msgs | visualization_msgs

rosws set common_msgs --git https://github.com/ros/common_msgs.git
rosws update commomn_msgs

the package shape_msgs, I have included it in my stack but, "rospack find" is not finding that package.

Robot_self_filter package has a dependency on the shape_msgs package.

so when i try to launch 

roslaunch erratic_navigation_apps demo_2dnav_slam.launch

it is showing the following error:

ERROR: cannot launch node of type [robot_self_filter/self_filter]: Cannot locate node of type [self_filter] in package [robot_self_filter]
2012-12-28 02:57:40 -0500 commented question Setting Up problem of rviz for the Erratic Navigation Stack

header: seq: 6 stamp: secs: 1646 nsecs: 698000000 frame_id: /map pose: position: x: 1.61775994301 y: 0.0917493700981 z: 0.0 orientation: x: 0.0 y: 0.0 z: 0.0264208326939

w: 0.999650908868
2012-12-28 02:07:24 -0500 commented question Setting Up problem of rviz for the Erratic Navigation Stack

fixed_frame is set to /map.and here is the output of rostopic echo /move_base_simple/goal WARNING: no messages received and simulated time is active. Is /clock being published?header: seq: 6 stamp: secs: 1646 nsecs: 698000000 frame_id: /map pose: position: x: 1.61775994301
2012-12-27 08:14:08 -0500 asked a question Setting Up problem of rviz for the Erratic Navigation Stack

Setting up 2dnav goal: "In the Tool Properties panel of rviz after setting the topic of 2D Nav Goal to the topic that your \move_base_node is subscribed to to receive goal states. In our case it is /move_base_simple/goal. You can now click 2d Nav Goal button and then draw an arrow on the map. Which specifies the position and the direction of the robot. The robot will try to move to achieve it."

I have drawn an arrow, but the robot is not moving..... Is there any bug in the erratic navigation apps package???

And also after giving the following command, i am getting some error which also been uploaded next-----------------------------------------------

roslaunch erratic_navigation_apps demo_2dnav_slam.launch

... logging to /home/muin/.ros/log/f166d278-512c-11e2-b1c6-003048da718e/roslaunch-Gaitlab-9184.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://Gaitlab:54654/

SUMMARY

PARAMETERS * /use_sim_time * /move_base_node/global_costmap/observation_sources * /slam_gmapping/sigma * /move_base_node/local_costmap/origin_y * /move_base_node/local_costmap/origin_x * /move_base_node/local_costmap/update_frequency * /move_base_node/global_costmap/base_scan/max_obstacle_height * /wg_walls * /slam_gmapping/lskip * /move_base_node/local_costmap/base_scan/marking * /move_base_node/local_costmap/observation_sources * /move_base_node/TrajectoryPlannerROS/vx_samples * /move_base_node/local_costmap/base_scan/clearing * /slam_gmapping/ogain * /move_base_node/global_costmap/base_scan/topic * /move_base_node/global_costmap/obstacle_range * /slam_gmapping/lasamplerange * /move_base_node/local_costmap/base_scan_marking/expected_update_rate * /move_base_node/TrajectoryPlannerROS/sim_time * /base_laser_self_filter/self_see_default_scale * /move_base_node/TrajectoryPlannerROS/max_vel_x * /slam_gmapping/map_update_interval * /move_base_node/global_costmap/base_scan_marking/data_type * /move_base_node/TrajectoryPlannerROS/acc_lim_th * /move_base_node/global_costmap/base_scan/observation_persistence * /slam_gmapping/temporalUpdate * /move_base_node/local_costmap/inflation_radius * /move_base_node/recovery_behaviors * /move_base_node/local_costmap/base_scan/sensor_frame * /move_base_node/global_costmap/map_type * /robot_state_publisher/publish_frequency * /move_base_node/TrajectoryPlannerROS/escape_vel * /slam_gmapping/lsigma * /move_base_node/TrajectoryPlannerROS/acc_lim_y * /move_base_node/TrajectoryPlannerROS/acc_lim_x * /move_base_node/global_costmap/static_map * /move_base_node/global_costmap/base_scan/data_type * /slam_gmapping/srt * /slam_gmapping/srr * /move_base_node/TrajectoryPlannerROS/sim_granularity * /move_base_node/local_costmap/base_scan/observation_persistence * /move_base_node/TrajectoryPlannerROS/min_vel_x * /move_base_node/local_costmap/map_type * /slam_gmapping/lasamplestep * /base_laser_self_filter/self_see_default_padding * /slam_gmapping/angularUpdate * /move_base_node/global_costmap/base_scan_marking/min_obstacle_height * /base_shadow_filter/scan_filter_chain * /move_base_node/global_costmap/inflation_radius * /move_base_node/local_costmap/base_scan_marking/sensor_frame * /move_base_node/local_costmap/base_scan/data_type * /move_base_node/global_costmap/base_scan_marking/max_obstacle_height * /move_base_node/global_costmap/robot_base_frame * /base_laser_self_filter/self_see_links * /slam_gmapping/particles * /rosdistro * /move_base_node/global_costmap/transform_tolerance * /move_base_node/global_costmap/unknown_cost_value * /move_base_node/global_costmap/base_scan_marking/expected_update_rate * /move_base_node/local_costmap/global_frame * /move_base_node/TrajectoryPlannerROS/holonomic_robot * /move_base_node/local_costmap/rolling_window * /move_base_node/TrajectoryPlannerROS/dwa * /move_base_node/global_costmap/base_scan/min_obstacle_height * /move_base_node/local_costmap/base_scan_marking/clearing * /move_base_node/global_costmap/base_scan_marking/observation_persistence * /move_base_node/local_costmap/width * /slam_gmapping/resampleThreshold * /move_base_node/global_costmap/base_scan/clearing * /move_base_node/local_costmap/publish_frequency * /move_base_node/local_costmap/base_scan_marking/observation_persistence * /move_base_node/local_costmap/base_scan_marking/marking * /slam_gmapping/linearUpdate * /move_base_node/local_costmap/base_scan_marking/min_obstacle_height * /move_base_node/local_costmap/base_scan_marking/topic * /move_base_node/global_costmap/base_scan_marking/clearing * /move_base_node/local_costmap/height * /move_base_node/local_costmap/static_map * /slam_gmapping/base_frame * /move_base_node/TrajectoryPlannerROS/yaw_goal_tolerance * /move_base_node/global_costmap/global_frame * /move_base_node/controller_frequency * /slam_gmapping/astep * /move_base_node/controller_patience * /base_shadow_filter/target_frame * /move_base_node/clearing_radius * /move_base_node/TrajectoryPlannerROS/max_rotational_vel * /robot_state_publisher/tf_prefix * /slam_gmapping/llsamplestep * /slam_gmapping/xmin * /move_base_node/global_costmap/publish_frequency * /move_base_node/TrajectoryPlannerROS/goal_distance_bias * /move_base_node/local_costmap/transform_tolerance * /slam_gmapping/delta * /move_base_node/global_costmap/raytrace_range * /move_base_node/global_costmap/base_scan_marking/sensor_frame * /slam_gmapping/xmax * /move_base_node/local_costmap/base_scan/max_obstacle_height * /move_base_node/local_costmap/obstacle_range * /move_base_node/TrajectoryPlannerROS/vtheta_samples * /move_base_node/local_costmap/robot_base_frame * /move_base_node/TrajectoryPlannerROS/heading_lookahead * /move_base_node/footprint * /slam_gmapping/stt * /slam_gmapping/ymax * /move_base_node/global_costmap/base_scan/sensor_frame * /slam_gmapping/lstep * /slam_gmapping/llsamplerange * /move_base_node/local_costmap/base_scan_marking/data_type * /slam_gmapping/maxUrange * /move_base_node/global_costmap/rolling_window * /move_base_node/global_costmap/base_scan/expected_update_rate * /move_base_node/local_costmap/raytrace_range * /robot_description * /move_base_node/TrajectoryPlannerROS/min_in_place_rotational_vel * /move_base_node/conservative_clear/reset_distance * /base_laser_self_filter/sensor_frame * /move_base_node/TrajectoryPlannerROS/path_distance_bias * /move_base_node/local_costmap/base_scan/min_obstacle_height * /move_base_node/global_costmap/base_scan ... (more)
2012-11-15 10:08:32 -0500 received badge ● Famous Question (source)
2012-10-12 11:28:35 -0500 commented question problem to launch gazebo

I am also getting the same kind of problem.My OS is----ubuntu 10.04 LTS(32bit deb),Graphics card and graphics card driver version:---00:02.0 VGA compatible controller: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller (rev 0c) and rosbuild_make_distribution(1.6.16)
2012-09-29 09:04:52 -0500 received badge ● Popular Question (source)
2012-09-20 01:11:50 -0500 received badge ● Notable Question (source)
2012-09-20 00:53:22 -0500 commented answer Regarding ros::WallTime

thanks for the reply.....ros::Time and ros::WallTime are both different classes.of them ros::Time can take time primitive type,ros::WallTime can not take time primitive type.Because i tried lots of time but its saying the same thing.I think there are some bug in ros::WallTime class.
2012-09-19 11:52:32 -0500 asked a question ROS_INFO("ros::time")

how can i show ros::time by ROS_INFO?
2012-09-19 10:52:51 -0500 commented answer Regarding ros::WallTime

"just put some time in there".can you please give some more definition/clarify about this sentence..............Thanks in advance.
2012-09-19 10:49:27 -0500 commented answer Regarding ros::WallTime

you said"There is no need to rename the parameter, if you want to use WallTime."error: no match for ‘operator=’ in ‘msg1.Test::Num_<std::allocator<void> >::header.std_msgs::Header_<std::allocator<void> >::stamp = ros::WallTime::now()()’......................but i am getting this kind of error.
2012-09-18 23:41:16 -0500 received badge ● Popular Question (source)
2012-09-18 06:05:28 -0500 received badge ● Notable Question (source)
2012-09-18 05:12:18 -0500 asked a question Regarding ros::WallTime

sequence1: this is my massage package:

Num.msg

Header header string data

this is my terminal massage,when i type $ rosmsg show Test/Num Header header

uint32 seq

time stamp

string frame_id

string data

Ques1:how to upgrade the "time" to "WallClock time",which will show the current time in "hr.min.sec" format??????????????

sequence2: this is my publisher node:

#include "ros/ros.h"
#include "Test/Num.h"
#include <sstream>

using namespace std;

int main(int argc, char **argv)
    {
        ros::init(argc, argv, "publisher");

        ros::NodeHandle m;

        ros::Publisher chatter_pub = m.advertise<Test::Num>("request", 1000);

        ros::Rate loop_rate(10);

        int counter = 0;
        while (ros::ok())
            {
                Test::Num msg1;
                msg1.header.stamp=ros::Time::now();
                msg1.header.frame_id="/current time";
                std::stringstream sst;
                sst << "Can you here me,hello..."<<counter;
                msg1.data = sst.str();

                ROS_INFO("%s", msg1.data);

                chatter_pub.publish(msg1);

                loop_rate.sleep();

                ++counter;

                ros::spinOnce();
            }


        return 0;
    }

ques2:in the above code "msg1.header.stamp=ros::Time::now();"--in this line what will be the member instead of "stamp" in case of ros::WallTime::now()?????????

sequence3: this is my subscriber node:

#include "ros/ros.h"
#include "Test/Num.h"
#include <sstream>

using namespace std;

void Request(const Test::Num& msg2)
    {
    Test::Num newMessage;
    newMessage.data = msg2.data;
    newMessage.header.stamp=ros::Time::now();
    newMessage.header.frame_id="/current time"; */
    ROS_INFO("I heard: [%s]", msg2.data);
    }

int main(int argc, char **argv)
{
   ros::init(argc, argv, "subscriber");

   ros::NodeHandle m;

   ros::Subscriber request_sub = m.subscribe("request", 1000, Request);

   ros::spin();

   return 0;
 }

ques3: if i want to add ros duration to subtract two time stamp to get the response time(time to publish massage in request topic-time to subscribe massage from request topi).what will be the command??????

ques4:in rosmake command i am getting following tewo errors: 1.warning: cannot pass objects of non-POD type ‘const struct std::basic_string<char, std::char_traits<char="">, std::allocator<char> >’ through ‘...’; call will abort at runtime 2.warning: format ‘%s’ expects type ‘char*’, but argument 8 has type ‘int’

Ques4:in rosrun Test publisher command ---it showing illigal instruction
2012-09-18 01:53:00 -0500 marked best answer ros::WallTime for cpp

how can i add a ros::wallTime stamp in my ros massage?
2012-09-18 01:52:59 -0500 commented answer ros::WallTime for cpp

but i found a error in "rosmake My_package". its showing that----- Call Stack (most recent call first): /opt/ros/fuerte/share/ros/core/rosbuild/public.cmake:203 (rosbuild_invoke_rospack) CMakeLists.txt:12 (rosbuild_init)

-- Configuring incomplete, errors occurred!
2012-09-18 01:37:59 -0500 commented answer How to use a message that I made?

In the message package's CMakeLists.txt you need rosbuild_genmsg(). I did that,but still it is showing that there is an error in my CMakeLists.txt.
2012-09-18 00:30:06 -0500 received badge ● Scholar (source)
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.
about | faq | help | privacy policy | terms of service
Powered by Askbot version 0.10.2