FrozenCh's profile - activity

Have you tried that doing 'apt purge' all melodic and reinstall?

http://wiki.ros.org/opencv3 I think you met opencv3 migration issue, try the configuration in the link.

try this: use_map_topic: true

I made a link from 3.1 to 3.2 and it is workable. (just a temperate way to solve this issue)

Localization problem may be caused by amcl setting. Do you have proper setting about your odom model type? <param na

Localization problem may be caused by amcl setting. Do you have proper setting about your odom model type? or

try this in your launch to link base_link and imu_frame in tf. <node pkg="tf2_ros" type="static_transform_publisher"

I agree with what @PeteBlackerThe3rd said, your scan points are not aligned with the wall on your map, so we see that as

It looks like these is something wrong with the scan topic and your cost map just reflects to the bad data. and besides

check your video_device. I guess that there are three devices and one of them belongs to your laptop cam.

Email is good, but I think if we solve this issue on this forum is better for this community.

Can you print screen on the rviz, in which showing the local cost map and footprint at the place your collision failed?

If you use the navigation stack, the collision detection would be processed into two parts, local cost map and local planner. Local cost map would use your footprint, inflation_radius, map etc. to generate a cost map. Thus, local planner can use the cost map to move robot.

The joint type for wheel should be continuous. You can see this as reference. http://wiki.ros.org/urdf/XML/joint

I think the footprint should be little bigger than your robot size. It will effect the dilation area of obstacles.

you can post your code or error messages then we can help you more

You can create and operate the publish/subscribe things by the ros messages defined by yourself. http://wiki.ros.org/ROS/Tutorials/Cre...

differential_drive_controller is a plug, by using which we can use cmd_vel, a common topic name for navigation stack, to control your robot model in Gazebo. However, if you just need a model appearance in rviz, then never mind the plugin.

I wrote okay that means not okay actually. Sorry for misleading, just like that it is dangerous to replace the fuse to other regular conductivity material. Messing up with the exception is dangerous.

try to shrink the inflation_radius in local cost map, or make the foot print smaller.

Have you tried the "clean build", which means deleting the devel/ and build/ then build again.

Besides, all in all, the exception is like the fuse to the electric circuit. It is some kind of protection from server crash, so it is okay to move out the exception area until you meet some weird bug.

If he checked that fixed type is okay with his robot and wheel, I think the next step is to change the type from "fixed" to "continuous" so that he can use the "differential_drive_controller" plugin.