Ask Your Question

Karthikeya Parunandi's profile - activity

2020-03-22 08:00:08 -0500 received badge  Nice Answer (source)
2018-07-23 09:13:32 -0500 received badge  Famous Question (source)
2018-05-25 02:39:59 -0500 received badge  Notable Question (source)
2018-04-13 21:28:03 -0500 marked best answer robot_localization ignores pose data input

Hi, My system description is as follows: Turtlebot - ros-kinetic - Ubuntu 16.04

I am running two instances of robot_localization, odometry in the first instance and 'odometry and global pose' in the second.

1) odom--> base_footprint (this is my equivalent of base_link). I'm adding a high noise (std_dev = 1) to the /odom and publishing it as /odom_noisy : frequency: 100 two_d_mode: true

map_frame: map              # Defaults to "map" if unspecified

odom_frame: odom            # Defaults to "odom" if unspecified

 base_link_frame: base_footprint  # Defaults to "base_link" if unspecified

 world_frame: odom           # Defaults to the value of odom_frame if unspecified

odom0: /odom_noisy

odom0_config: [false, false,  false,
               false, false, false,
               true, true, false,
               false, false, true,
               false, false, false]
odom0_queue_size: 5
odom0_nodelay: false
odom0_differential: false
odom0_relative: false

use_control: true
# Whether the input (assumed to be cmd_vel) is a geometry_msgs/Twist or geometry_msgs/TwistStamped message. Defaults to
# false.
stamped_control: false
# The last issued control command will be used in prediction for this period. Defaults to 0.2.
control_timeout: 0.1
# Which velocities are being controlled. Order is vx, vy, vz, vroll, vpitch, vyaw.
control_config: [true, false, false, false, false, true]
# Places limits on how large the acceleration term will be. Should match your robot's kinematics.
acceleration_limits: [1.3, 0.0, 0.0, 0.0, 0.0, 3.4]
# Acceleration and deceleration limits are not always the same for robots.
deceleration_limits: [1.3, 0.0, 0.0, 0.0, 0.0, 4.5]
# If your robot cannot instantaneously reach its acceleration limit, the permitted change can be controlled with these
# gains
acceleration_gains: [0.8, 0.0, 0.0, 0.0, 0.0, 0.9]
# If your robot cannot instantaneously reach its deceleration limit, the permitted change can be controlled with these
# gains
deceleration_gains: [1.0, 0.0, 0.0, 0.0, 0.0, 1.0]
process_noise_covariance: [0.05, 0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0.05, 0,    0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0.5, 0,    0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0.05, 0,    0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0.05, 0,    0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0.005, 0,     0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0.05, 0,     0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0.05, 0,    0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0,     0.05, 0,    0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0,     0,    0.05, 0,    0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0.05, 0,    0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0.04, 0,    0,    0,
                           0,    0,    0,    0,    0,    0,    0,     0,     0,    0,    0,    0 ...
(more)
2018-04-13 21:28:03 -0500 received badge  Scholar (source)
2018-04-13 17:59:34 -0500 commented answer robot_localization ignores pose data input

Filling the time stamps did the trick. Thanks a lot!

2018-04-13 12:28:04 -0500 received badge  Popular Question (source)
2018-04-13 10:14:04 -0500 commented answer robot_localization ignores pose data input

Yes, I have a static transform from map to world. The two_d_mode is also on (Sorry, forgot to copy that in the question)

2018-04-13 10:10:38 -0500 commented answer robot_localization ignores pose data input

Yes, I have a static transform from map to world. The two_d_mode is also on (Sorry, forgot to copy that in the question)

2018-04-13 10:10:07 -0500 edited question robot_localization ignores pose data input

robot_localization ignores pose data input Hi, My system description is as follows: Turtlebot - ros-kinetic - Ubuntu 16

2018-04-13 10:08:55 -0500 commented answer robot_localization ignores pose data input

Yes, I have a static transform from map to world. The two_d_mode is also on (Forgot to copy that here). Updated.

2018-04-13 10:07:43 -0500 edited question robot_localization ignores pose data input

robot_localization ignores pose data input Hi, My system description is as follows: Turtlebot - ros-kinetic - Ubuntu 16

2018-04-13 10:07:43 -0500 received badge  Editor (source)
2018-04-13 10:04:24 -0500 commented answer robot_localization ignores pose data input

Yes, I have a static transform from map to world. The two_d_mode is also on (Forgot to copy that here).

2018-04-13 09:30:03 -0500 edited question robot_localization ignores pose data input

robot_localization ignores pose data input Hi, My system description is as follows: Turtlebot - ros-kinetic - Ubuntu 16

2018-04-13 09:28:26 -0500 asked a question robot_localization ignores pose data input

robot_localization ignores pose data input Hi, My system description is as follows: Turtlebot - ros-kinetic - Ubuntu 16

2018-04-12 16:04:17 -0500 commented answer robot_localization ignores pose topic

I have a very similar problem. I'm using pose data in the map->odom instance of ekf_localization_node and it ignores

2018-04-12 16:02:30 -0500 commented question robot_localization ignores pose topic

Hi! I have a very similar problem to yours. I'm using pose data in the map->odom instance of ekf_localization and it

2018-03-04 17:19:44 -0500 received badge  Famous Question (source)
2017-10-24 04:10:07 -0500 received badge  Nice Answer (source)
2017-06-21 12:20:09 -0500 received badge  Notable Question (source)
2017-06-12 16:40:02 -0500 received badge  Necromancer (source)
2017-05-22 06:14:32 -0500 received badge  Popular Question (source)
2017-04-01 01:28:14 -0500 asked a question Pixhawk not publishing the local position of my Quadrotor

I am on Ubuntu 14.04 (ROS Indigo). I run "roslaunch mavros px4.launch" and am able to successfully connect to my quadrotor. I have a working GPS signal and also could see the data being published on "/mavros/global_position/local". However, no data is being published on "/mavros/local_position/pose". When I run the gazebo simulation, data is being published on "/mavros/local_position/pose". What could be the possible solution to this?

Thanks in advance

2017-03-16 06:51:54 -0500 received badge  Enthusiast
2017-03-14 09:33:01 -0500 commented answer [rosrun] Couldn't find executable named mavsys

@YingHua Thanks a lot! That solved my problem too. But, the first time I executed, I don't remember doing this. why are the permissions lost?

2016-08-30 17:38:42 -0500 received badge  Necromancer (source)
2016-08-30 17:38:42 -0500 received badge  Teacher (source)
2016-07-15 08:38:04 -0500 received badge  Student (source)
2016-06-17 11:13:57 -0500 received badge  Famous Question (source)
2016-06-07 09:48:27 -0500 received badge  Notable Question (source)
2016-06-07 09:48:27 -0500 received badge  Popular Question (source)
2016-06-02 10:43:54 -0500 commented answer [ERROR] [WallTime: 1448195093.843222] Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino

Hi! In my case, it was set or rather changed in my code already. If it is not, as in your case, I guess it would be a default of 57600 which means you need not enter your baud rate. Again, this is my guess!

2016-05-31 11:15:55 -0500 answered a question ros arduino "hello world"

Hi! I too encountered the same problem. After a number of clueless frustrated hours, I deleted build file in catkin workspace and re-builded it by running catkin_make , then, catkin_make install and then source by source ~/catkin_ws/devel/setup.bash in the workspace. I donĀ“t know what went wrong, but finally it worked.

Cheers!

2016-05-30 14:42:39 -0500 received badge  Supporter (source)
2016-05-30 14:04:14 -0500 asked a question How to install rosserial for Arduino on ROS-Kinetic?

There official website states that no information is contained regarding rosserial for Arduino on the latest verion of ROS i.e, Kinetic. Can I install manually? If so, please help me.

2016-05-27 04:48:42 -0500 answered a question [ERROR] [WallTime: 1448195093.843222] Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino

Hi! I also encountered the same problem and fixed it, finally. It displays "Connecting to /dev/ttyACM0 at 57600 baud" while the baud rate in my Arduino code was set to be 115200. Hence, set the baud rate as it was in your arduino code (In my case it is 115200) by adding _baud:=X (where 'X' is the baud rate between your computer and the Arduino) to the same command as follows:

rosrun rosserial_python serial_node.py _port:=/dev/ttyACM0 _baud:=115200

The other reason could be that your port is different from that of the above command. For example, check if your port to which the Arduino is connected, is as entered in the above command i.e, ttyACM0 or ttyACM1 etc . Hope this helps!

2016-05-27 04:46:31 -0500 answered a question Arduino rosserial - Unable to sync with device

Hi! I also encountered the same problem and fixed it finally. It displays "Connecting to /dev/ttyACM0 at 57600 baud" while the baud rate in my Arduino code was set to be 115200. Hence, set the baud rate as it was in your arduino code (In my case it is 115200) by adding_baud:=X (where 'X' is the baud rate between your computer and the Arduino) to the same command as follows:

rosrun rosserial_python serial_node.py _port:=/dev/ttyACM0 _baud:=115200

The other reason could be that your port is different from that of the above command. For example, check if your port to which the Arduino is connected, is as entered in the above command i.e, ttyACM0 or ttyACM1 etc .

Hope this helps!

2016-05-27 04:45:00 -0500 answered a question Unable to sync with device (arduino uno)

Hi! I also encountered the same problem and fixed it finally. It displays "Connecting to /dev/ttyACM0 at 57600 baud" while the baud rate in my Arduino code was set to be 115200. Hence, set the baud rate as it was in your arduino code (In my case it is 115200) by adding _baud:=X (where 'X' is the baud rate between your computer and the Arduino) to the same command as follows:

rosrun rosserial_python serial_node.py _port:=/dev/ttyACM0 _baud:=115200

The other reason could be that your port is different from that of the above command. For example, check if your port to which the Arduino is connected, is as entered in the above command i.e, ttyACM0 or ttyACM1 etc . Hope this helps!