amjack's profile - activity

Worked for me on noetic

Works for me in Noetic.

This worked for me on Noetic, Thanks.

This worked for me on Noetic, Thanks.

This worked for on Noetic, Thanks

The sensor could also detect the ground as an obstacle. Change the p value in rpy="0 0 0" as rpy="0 -0.5 0" or something

works for me on Noetic.

Hi @LoopingCollider Can you tell us which Ultrasonic sensor did you use ?

worked for me on ROS noetic! Thanks

Hi , Any update on this issue ?

Thanks. This worked for me on ROS noetic.

Thanks for your reply, But I suspect laser_scan_matcher is not a maintained repository. Although, I tried hector_slam an

@Mike Scheutzow I would like to generate the map of an indoor environment. I am not trying to localize the sensor, so I

@MikeScheutzow I would like to generate the map of an indoor environment. I am not trying to localize the sensor, so I

I am using, ROS Noetic + 20.04. Lidar hardware: rplidar_a3m1

• I installed slam_toolbox package via sudo apt install ros-noetic-slam-toolboxand it is working fine
• I installed rplidar driver via rplidar git

I want to create an indoor map using slam_toolbox with lidar ONLY. I do not have wheel odometry.

First I do,

• roslaunch rplidar_ros rplidar_a3.launch This starts publishing on the /scan topic.
• roslaunch slam_toolbox online_sync.launch I launch the slam_toolbox with default config.

Initially, I encounter that map did not grow after its initialization #438

Then, I provided a dynamic frame as per Broadcasting a moving frame. Which looks like this tf publisher

But I see my map is not generated correctly. It is moving in a circle (which I guess due to the dynamic tf I provided). The circle get smaller if I reduce the amplitude. I do not know what is the correct way of providing the dynamic tf between frames when I want to move the sensor with hand and create a map.

And this is how my tf tree looks like when running, rosrun tf2_tools view_frames.py

frames.pdf

Regards,

@WarTurtle Thanks for commenting. Would you recommend hector_slam as better solution than slam_toolbox?. As hector_slam

@WarTurtle Thanks for commenting. Would you recommend hector_slam as better solution than slam_toolbox?.

creating the map with only Lidar I am using, ROS Noetic + 20.04. Lidar hardware: rplidar_a3m1 I installed slam_toolbo

creating the map with only Lidar I am using, ROS Noetic + 20.04. Lidar hardware: rplidar_a3m1 I installed slam_toolbo

For 20.04 ros noetic, use: rosrun tf2_tools view_frames.py

For 20.04 , ros noetic, use rosrun tf2_tools view_frames.py

I tried 3D Localization and mapping using hdl_graph_slam. Just using the Lidar scan and odometry and I was able to local

I tried 3D Localizing and mapping using hdl_graph_slam. Just using the Lidar scan and odometry and I was able to localiz

Check this out, serial package. Link or goto http://wjwwood.io/serial/ After installing, make sure to, cd cat

Check this out, serial package. Link or goto http://wjwwood.io/serial/ After installing, make sure to, cd cat

Check this out, serial package. Link or goto http://wjwwood.io/serial/ and after installing, make sure to, sou

Check this out, serial package. Link or goto http://wjwwood.io/serial/ and after installing, make sure to sourc

Check this out, serial package. Link or goto http://wjwwood.io/serial/

As you said, your trajectory are executed correctly, but it's not smooth. To have the smooth trajectory you need to hav

Yeah , No log warnings. Let's see , may be an issue with interface as you described. But, I need to find a solution and

Yeah , No log warnings. Let's see , may be a issue with interface as you described. But, I need to find a solution and m

should_pan_joint is first joint, I tried various values on all the joints, behavior is same , its jerky for all joints.

This can be an issue, have a look at my repo . I think I have defined them correctly, look here @Dragonslayer

x axis is the time which is scaled by default by rqt_multiplot. It's just one command, Yes you are seeing right, 60 Nm.

x axis is the time which scaled by default by rqt_multiplot. It's just one command, Yes you are seeing right, 60 Nm. It

initially I thought there is some issue with my server-client but this problem is there with rostopic pub /. When I read

initially I thought there is some issue with my server-client but this problem is there with rostopic pub /. When I read

initially I thought there is some issue with my server-client but this problem is there with rostopic pub /. When I read