kuka_kuka's profile - activity

overview network karma followed questions activity

2019-01-27 04:19:40 -0500	received badge	● Famous Question (source)
2019-01-27 04:19:40 -0500	received badge	● Notable Question (source)
2018-12-01 16:27:43 -0500	received badge	● Famous Question (source)
2018-10-03 23:58:58 -0500	received badge	● Famous Question (source)
2018-09-06 04:15:12 -0500	received badge	● Famous Question (source)
2018-08-21 05:33:28 -0500	commented question	Navigation stack not working properly when running remotely ...: "The /base_scan observation buffer has not been updated for XX.XX seconds, and it should be updated every 0.20 seco
2018-08-21 05:33:22 -0500	commented question	Navigation stack not working properly when running remotely Latency is not high, I ping robot from my PC and mostly I get a latency of 1.5-5 ms and sometimes 30-50 ms. I can "solve
2018-08-21 05:33:05 -0500	commented question	Navigation stack not working properly when running remotely Latency is not high, I ping robot from my PC and mostly I get a latency of 1.5-5 ms and sometimes 30-50 ms. I can "solve
2018-08-21 05:32:53 -0500	commented question	Navigation stack not working properly when running remotely Latency is not high, I ping robot from my PC and mostly I get a latency of 1.5-5 ms and sometimes 30-50 ms. I can "solve
2018-08-21 05:31:56 -0500	commented question	Navigation stack not working properly when running remotely ...: "The /base_scan observation buffer has not been updated for XX.XX seconds, and it should be updated every 0.20 seco
2018-08-21 05:29:10 -0500	commented question	Navigation stack not working properly when running remotely Latency is not high, I ping robot from my PC and mostly I get a latency of 1.5-5 ms and sometimes 30-50 ms. I can "solve
2018-08-21 05:29:10 -0500	received badge	● Commentator
2018-08-20 08:11:01 -0500	received badge	● Notable Question (source)
2018-08-20 04:44:12 -0500	received badge	● Popular Question (source)
2018-08-20 04:38:28 -0500	edited question	Navigation stack not working properly when running remotely Navigation stack not working properly when running remotelyHi Hi comunity! When I execute "move_base" node in the local
2018-08-17 08:58:34 -0500	asked a question	Navigation stack not working properly when running remotely Navigation stack not working properly when running remotelyHi Hi comunity! When I execute "move_base" node in the local
2018-08-17 06:23:23 -0500	marked best answer	Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on my robot I would like to get only the topic "camera/depth_registered/image_raw" cause this is the only one I need right now. In case this is not posible, I would like to know if I can run freenect nodelet remotely. I try but as the camera is not connected to the PC running it I get the message "No devices connected". Is there any way by which I could execute it remotely? And another problem I have is that if I execute "depthimage_to_laserscan" module in the remote PC (after launching freenect in the robot connected to Kinect) it does not work (I do not get any errors or warnings but the /scan topic does not show anything), however, in the robot it does work. Could it be cause one of ROS versions is Kinetic and the other one Indigo? This is the launch file: <launch> <node pkg="depthimage_to_laserscan" type="depthimage_to_laserscan" name="depthima$ <param name=" scan_height"="" value="3"/> <remap from="image" to="camera/depth_registered/image_raw"/> </node> </launch> Thanks in advance.
2018-08-17 06:22:25 -0500	received badge	● Popular Question (source)
2018-08-16 07:49:06 -0500	edited question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-16 07:30:27 -0500	edited question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-16 07:25:45 -0500	edited question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-16 07:25:27 -0500	edited question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-16 07:22:43 -0500	edited question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-16 07:22:19 -0500	asked a question	Get only depth data from Kinect using libfreenect Get only depth data from Kinect using libfreenect Hi, In order to reduce the amount of CPU freenect nodelet is using on
2018-08-14 07:26:19 -0500	received badge	● Nice Answer (source)
2018-08-14 06:42:21 -0500	commented answer	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] As I am working with a Kinect and not with a real laser I use a package that simulates the usage of a laser from the de
2018-08-14 06:39:06 -0500	marked best answer	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] Hi, I am working with a real kuka youbot robot. When I run AMCL I get constantly the following warning and error: `[WARN] [1531475915.405190988]: Failed to compute odom pose, skipping scan (Lookup would require extrapolation into the future. Requested time 1531475915.373467473 but the latest data is at time 1531475915.371227514, when looking up transform from frame [base_link] to frame [odom]) [ERROR] [1531475915.405592384]: Couldn't determine robot's pose associated with laser scan` When I launch Rviz and set the initial pose with "2D Pose Estimate", /initialpose topic echo's the following: `header: seq: 0 stamp: secs: 1531476085 nsecs: 404504998 frame_id: "map" pose: pose: position: x: -0.121083259583 y: -0.0682992935181 z: 0.0 orientation: x: 0.0 y: 0.0 z: 0.00537968781778 w: 0.999985529375 covariance: [0.25, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.25, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.06853891945200942]` And in the terminal running AMCL appears: `[ INFO] [1531476085.547250607]: Setting pose (1531476085.547161): -0.121 -0.068 0.011` But after that it continues throwing same warning and error mentioned before. I can not attach TF tree, but it is: map -> odom -> base_footprint -> base_link -> ...And TF transformations are working right at a rate, respectively in those cases, (starting with map -> odom) of: 21.609, 42.11, 50.981. Here are the results of tf_monitor: RESULTS: for all Frames Frames: Frame: /camera_depth_frame published by unknown_publisher Average Delay: -0.2982 Max Delay: 0 Frame: /camera_depth_optical_frame published by unknown_publisher Average Delay: -0.297965 Max Delay: 0 Frame: /camera_rgb_frame published by unknown_publisher Average Delay: -0.297891 Max Delay: 0 Frame: /camera_rgb_optical_frame published by unknown_publisher Average Delay: -0.297604 Max Delay: 0 Frame: arm_link_0 published by unknown_publisher Average Delay: -0.696617 Max Delay: 0 Frame: arm_link_1 published by unknown_publisher Average Delay: -0.191182 Max Delay: 0 Frame: arm_link_2 published by unknown_publisher Average Delay: -0.19118 Max Delay: 0 Frame: arm_link_3 published by unknown_publisher Average Delay: -0.191179 Max Delay: 0 Frame: arm_link_4 published by unknown_publisher Average Delay: -0.191179 Max Delay: 0 Frame: arm_link_5 published by unknown_publisher Average Delay: -0.191178 Max Delay: 0 Frame: base_footprint published by unknown_publisher Average Delay: -0.190222 Max Delay: 0 Frame: base_laser_front_link published by unknown_publisher Average Delay: -0.696646 Max Delay: 0 Frame: base_link published by unknown_publisher Average Delay: -0.696637 Max Delay: 0 Frame: camera_link published by unknown_publisher Average Delay: -0.29782 Max Delay: 0 Frame: caster_link_bl published by unknown_publisher Average Delay: -0.189073 Max Delay: 0 Frame: caster_link_br published by unknown_publisher Average Delay: -0.189071 Max Delay: 0 Frame: caster_link_fl published by unknown_publisher Average Delay: -0.18907 Max Delay: 0 Frame: caster_link_fr published by unknown_publisher Average Delay: -0.189069 Max Delay: 0 Frame: gripper_finger_link_l ... (more)
2018-08-14 06:39:06 -0500	received badge	● Scholar (source)
2018-07-19 11:03:57 -0500	received badge	● Self-Learner (source)
2018-07-19 11:03:57 -0500	received badge	● Teacher (source)
2018-07-16 13:55:25 -0500	received badge	● Notable Question (source)
2018-07-16 09:03:49 -0500	answered a question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] Thanks to "Humpelstilzchen" I was able to solve this issue. Laser frame was set to /odom instead of to /camera_link. Aft
2018-07-16 08:56:49 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] Do I have to add an answer with the result? Or what am I suppose to do now for indicating the answer?
2018-07-16 08:55:58 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] I changed it to /odom some weeks ago...I have set it to camera_link again and it seems that amcl works correctly now! I
2018-07-16 07:22:27 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] ranges: [nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, nan, 3.2593
2018-07-16 07:21:57 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] Cheader: seq: 74 stamp: secs: 1531743667 nsecs: 581998729 frame_id: odom angle_min: -0.546698212624 angl
2018-07-16 06:45:34 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] .yaml file: image: my_map.pgm resolution: 0.050000 origin: [-5.000000, -5.000000, 0.000000] negate: 0 occupied_thresh:
2018-07-16 06:42:06 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] .yaml file: image: my_map.pgm resolution: 0.050000 origin: [-5.000000, -5.000000, 0.000000] negate: 0 occupied_thresh:
2018-07-16 06:40:20 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] Time difference varies between 0-5 ms. Transform tolerance is set to default (0.1) and modifying it to 0.5 does not make
2018-07-16 05:18:48 -0500	received badge	● Notable Question (source)
2018-07-16 05:16:41 -0500	commented question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] All nodes (except Rviz) are running on same machine
2018-07-13 13:10:35 -0500	received badge	● Popular Question (source)
2018-07-13 06:24:43 -0500	edited question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] AMCL: Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform
2018-07-13 06:24:43 -0500	received badge	● Associate Editor (source)
2018-07-13 06:24:39 -0500	edited question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] AMCL: Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform
2018-07-13 06:13:23 -0500	edited question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] AMCL: Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform
2018-07-13 06:12:51 -0500	edited question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] AMCL: Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform
2018-07-13 05:58:48 -0500	edited question	AMCL: Lookup would require extrapolation into the future. Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform from frame [base_link] to frame [odom] AMCL: Requested time 1531474550.521278314 but the latest data is at time 1531474550.516698594, when looking up transform