Yes you can use a depth câmera plugin (for Gazebo simulator) to test it. I have already done this for my simulation actu

Hi I summary of the idea 1 -Face Recognition: Use the ROS2 package for face recognition. https://www.theconstructsim.c

Hi I have summarized an idea: 1-Face Recognition: Use the ROS2 package for face recognition: https://www.theconstructs

Hi I have summarized an idea: 1-Face Recognition: Use the ROS2 package for face recognition: https://www.theconstructs

Issues with Goal Pose Setting using SLAM in Nav2 Stack for GPS-based Navigation Hi, I am currently working on a GPS-bas

Issues with Goal Pose Setting using SLAM in Nav2 Stack for GPS-based Navigation Hi, I am currently working on a GPS-bas

Crazy behavior I have spent hours trying to see the /imu topic being subscribed by navsat_transform_node and nave saw it

Crazy behavior I have spent hours trying to see the /imu topic being subscribed by navsat_transform_node and nave saw it

Then it seems a robot state publisher or joint state publisher issue. Do you have these packages installed? Is your TF o

Did you try to fine-tuning the params, such as change the "z_origin" on nav2_params.yaml? Or increase the mapping capabi

If you are using ROS2 probably is a QoS issue ( Quality of service) You must open rviz2 1- ros2 run rviz2 rviz2 2- Go

If you are using ROS2 probably is a QoS issue ( Quality of service) You must open rviz2 1- rosrun rviz2 rviz2 2- Go t

If you are using ROS2 probably is a QoS issue ( Quality of service) You must open rviz2 1- rosrun rviz2 rviz2 2- Go t

Hello,

I am trying to convert a depth image to a laser scan using the depthimage_to_laserscan package in ROS2 Galactic, but I am having trouble getting the node to publish the converted LaserScan data. Despite being able to subscribe to the input depth image topic (/kinect_sensor/depth/image_raw), the node doesn't seem to be publishing the converted data to the /kinect_scan topic. Or the node is not properly doing its task: converting the data...

Here's the launch file snippet for the depthimage_to_laserscan node:

Kinect depthimage to laserscan conversion node

depthimage_to_laserscan_node = Node(
    package='depthimage_to_laserscan',
    executable='depthimage_to_laserscan_node',
    name='depthimage_to_laserscan',
    parameters=[kinect_params_file, {'use_sim_time': use_sim_time}],
    remappings=[('depth', '/kinect_sensor/depth/image_raw'),
                ('scan', '/kinect_scan')],
    output='screen')

And my kinect_params.yaml file:

depthimage_to_laserscan_node:
  ros__parameters:
    output_frame: kinect_depth_frame
    scan_height: 1
    range_min: 0.45
    range_max: 10.0
    scan_topic: /kinect_scan

When I inspect the /depthimage_to_laserscan node using ros2 node info, it shows that the node subscribes to /kinect_sensor/depth/image_raw and publishes to /kinect_scan. However, when I echo the /kinect_scan topic, it is empty and produces no output.

Here is a LINK to a video demonstrating the issue.

I have already tried changing the scan_topic to the original /scan topic in the parameter file and have also checked that the frame_id in the header of the depth image messages is consistent with the output_frame parameter, but these didn't solve the issue.

Could anyone please help me to understand what might be going wrong and how to get the depthimage_to_laserscan node to publish the LaserScan data correctly?

I am facing a similar issue and behavior using other packages image-proc, as related here: https://github.com/ros-perception/ima...

Thank you in advance for your help.

Real Kinect Scan Data not Generating Local Costmap in Nav2 I am currently working on a project that involves integrating

Real Kinect Scan Data not Generating Local Costmap in Nav2 I am currently working on a project that involves integrating

Real Kinect Scan Data not Generating Local Costmap in Nav2 I am currently working on a project that involves integrating

Real Kinect Scan Data not Generating Local Costmap in Nav2 I am currently working on a project where I am integrating re

Real Kinect Scan Data not Generating Local Costmap in Nav2 I am currently working on a project where I am integrating re

Solving QoS mismatch and compatibility issues when compiling depthimage_to_laserscan package for ROS2 Galactic The dept

Solving QoS mismatch and compatibility issues when compiling depthimage_to_laserscan package for ROS2 Galactic The dept

depth_image_to_laserscan not publishing to /kinect_scan topic in ROS2 Galactic Hello, I am trying to convert a depth im

depth_image_to_laserscan not publishing to /kinect_scan topic in ROS2 Galactic Hello, I am trying to convert a depth im

depth_image_to_laserscan not publishing to /kinect_scan topic in ROS2 Galactic Hello, I am trying to convert a depth im

Hi I also need to simulate a kinect within ROS2. Did you figure out how?

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103. However, the planner could only be trig

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103. However, the planner could only be trig

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103. However, the planner could only be trig

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103. However, the planner could only be trig

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103, but the planner issues persisted in the

Steve, I fixed pose localization errors by aligning my robot's SDF with REP 103, but the planner issues persisted in the

While implementing SLAM with Nav2 on my Ackermann-style truck robot, I've run into an issue where the initial localization starts with my vehicle facing in the opposite direction (x orientation reversed). Specifically, the truck's front bumper and rear end are inverted in the RViz visualization, leading to mislocalization when the vehicle starts moving.

This issue is demonstrated in this video: lnverted Localization Rviz, I highlight the misalignment by adding an obstacle in Gazebo. The obstacle in front of the truck incorrectly appears at the rear end in RViz due to this localization error.

I am unsure how to address this problem. Could the solution involve inverting a specific TF in the Xacro file related to the IMU origin, or should I consider another possible solution?

Any assistance in resolving this inverted localization issue would be greatly appreciated.