Cosmo Borsky

Try adjusting the values in the Dynamic Reconfigure starting with the filtered cloud and cluster sizes. Also check the output of the lidar_body_tracking node in your terminal. You may need...

In the **lidar_body_tracking.launch** (top-left) try changing `scan_topic` to `/QP308/pc_QP308` /QP308/pc_QP308 is the Point Cloud topic published by the Quanergy Lidar driver. Welcome to ROS!

Can you do a `rostopic info` on both: - `/QP308/pc_QP308` - `/Sensor/points`

The *frame_id* in the topic is set to `Sensor`. The URDF robot_name should be set to the same frame_id as the topic: https://github.com/MyNameIsCosmo/lidar_body_tracking/blob/master/urdf/m8.urdf.xacro#L2 Try changing `name="sensor_m8"` to `name="Sensor"`

Nah, the macro name is irrelevant to this issue. In fact, the macro is redundant for the Xacro file and is confusing, but that's an issue for a later date.

I derped The actual value you need to change in the urdf is the **link**: https://github.com/MyNameIsCosmo/lidar_body_tracking/blob/master/urdf/m8.urdf.xacro#L8-L10 ``` ```

Height shouldn't be a reason since height should remain independent of the data. Try putting some debug info like `ROS_INFO('cloud_cb')` into the [cloud_cb](https://github.com/MyNameIsCosmo/lidar_body_tracking/blob/master/src/pcl_body_tracking.cpp#L143) function, and work your way from there....

They should look like the same pointcloud message from `Sensor/points` except with less data

Hi @saberclaw1213 Check out issue #1 Rosbag will just advertise the topic, so make sure you set the subscriber topic accordingly. All this package does is take input from a...

I've had a similar issue with the `auto_reloader` not supporting relative imports, so using the following in my entry point failed: `from . import __description__ as description, __title__ as title,...