luketheduke's profile - activity

I guess that's try, I'll have to try that out and see how it works...

I understand that, so make the unknown space untraversable, but there's two situations where I think I need to use unkno

Robot radius is 0.22m. Which is correct to the size of the robot. I checked the segment of the wall where it was trying

Navigation stack planning global path through large unknown wall segments of map I'm running a Turtlebot type platform w

I am working on writing some code for a project, but I have a node that will be continuously publishing(30 Hz) to a topic while also subscribing to the same topic to listen for a different pub from a different node. Basically, node A is listening to topic X and publishing to topic X. Meanwhile another node, node B, will at some time, publish a message to topic X. Will the subscriber callback in node A be triggered every time it publishes sometime? Also, will it be able to pick up the message if node B only publishes once? Thanks, luketheduke

I'm trying to run laser_scan_matcher, but I'm getting a tf extrapolation error, except that the requested lookup time varies wildly and doesn't line up at all with my system clock. All these nodes are running on one machine. This is the error message:

    [ WARN] [1593725386.115952617]: Could not get initial transform from base to laser frame, Lookup would require extrapolation into the past.  Requested time 609813920.000032765 but the earliest data is at time 1593725383.147062831, when looking up transform from frame [velodyne] to frame [base_link]
[ WARN] [1593725386.116032217]: Skipping scan

I've launched it several times and I've gotten several different requested times, not including the one above:

• 1534859248.000032764
• 1166446240.000032764
• 900842032.000032766

It seems like the node is just requesting random times, which is what's throwing me off. The message is being generated by one of two TF lookups in line 780-783 of the source file: https://github.com/ccny-ros-pkg/scan_...

My launch file:

<launch>
<node pkg="pointcloud_to_laserscan" type="pointcloud_to_laserscan_node" name="slam_p2l">
    <remap from="cloud_in" to="/velodyne_points"/>
    <remap from="p2l_scan" to="slam/scan"/>
    <rosparam>
        min_height: -0.5
        max_height: 0.15
        angle_min: -3.14
        angle_max: 3.14 
        angle_increment: 0.01

        range_min: 0.60
        range_max: 130.0
        use_inf: true
        concurrency_level: 0
    </rosparam>
</node>
<node pkg="laser_scan_matcher" type="laser_scan_matcher_node" 
name="laser_scan_matcher_node" output="screen">

    <param name="fixed_frame" value = "world"/>
    <param name="max_iterations" value="10"/>
    <param name="publish_tf" value="false"/>
    <param name="publish_pose_stamped" value="true"/>
    <param name="use_cloud_input" value="false"/>
    <remap from="imu/data" to="imu"/>
    <remap from="scan" to="slam/scan"/>
</node>

</launch>

TF Frames: Any ideas on how to fix this?

System details: ROS Kinetic

Ubuntu 16.04

scan_tools v0.3.2 installed via apt.

Still haven't figured out what caused it, but the issue went away when I built from source, so it's possible there's an

Node clock is off in TF lookup I'm trying to run laser_scan_matcher, but I'm getting a tf extrapolation error, except th

Node clock is off in TF lookup I'm trying to run laser_scan_matcher, but I'm getting a tf extrapolation error, except th

I have a node where I need to wait for a specific amount of time. Can I just use time.sleep() in python or do I need something else? Thanks, luketheduke

As gvdhoorn pointed out, I wasn't recording /tf_static and that meant that I wasn't recording any static TF transforms,

I didn't know those existed. I relaunched the sim and echoed the /tf_static topic and all the missing transforms are the

It depends on what approach you want to take, you could either integrate GPIO into every package that needed it or make

Husky Gazebo robot_state_publisher not broadcasting transforms I'm trying to record a bag from the Husky Gazebo simulati

There are several different approaches to controlling GPIO with the Jetson. Because C++ is such a low level language her

Hi, I am trying to view Kinect data in RVIZ on a remote client in ROS. I have exported the ROS_MASTER_URI to set to the machine with the roscore running but it won't send back any data. Rviz gives this error:

[ WARN] [1427845377.406032758]: ROS_HOSTNAME / ROS_IP is set to only allow local connections, so a requested connection to 'lukas-Inspiron-N7010' is being rejected.

How can I fix this? Both machines are running Ubuntu 14.04 with Indigo. I followed this tutorial and I couldn't get them talking to each other although I can see the topics being published with rostopic echo. All help is appreciated. Thanks, luketheduke

When I launch usb_cam from a launch file with robot_upstart on boot, the node fails saying:

[usb_cam-4] process has died [pid 3136, exit code 1, cmd /opt/ros/indigo/lib/usb_cam/usb_cam_node __name:=usb_cam __log:=/home/ubuntu/.ros/log/68608950-115a-11e6-805a-544a16bf53a7/usb_cam-4.log].
log file: /home/ubuntu/.ros/log/68608950-115a-11e6-805a-544a16bf53a7/usb_cam-4*.log

When I look at that log it says:

[ WARN] [1462299217.838001270]: Shutdown request received.
[ WARN] [1462299217.874595145]: Reason given for shutdown: [new node registered with same name]
[ WARN] [1462299240.126186614]: Shutdown request received.
[ WARN] [1462299240.141871614]: Reason given for shutdown: [new node registered with same name]
[ WARN] [1462299353.880653169]: Shutdown request received.
[ WARN] [1462299353.909079127]: Reason given for shutdown: [new node registered with same name]

When I launch the node using rosrun, it works perfectly. What could be causing this issue? I am running ROS Indigo on a Beaglebone Black and Ubuntu 14.04.