-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ORB-Slam3 for ROS2 stops after receiving 1 frame #2
Comments
I guess it was problem of less feature extraction from your camera image. |
This camera image works fine with the ROS1 ORB slam but not with the ORB slam for ros2. Do you have any idea what is wrong? |
Then, i don't know what is the problem.. exactly. I need to test it on the same evironment to figure out. |
I have the same problem with stereo-inertial mode. |
I solved the problem by replacing the default version 4.5.5 OpenCV of Jetpack 5.0.2 with the version 4.2.0 OpenCV. For me, the problem is the version conflict of the cv-bridge. The default version of the cv-bridge in ROS2 box is version 4.2.0, so the ORB-SLAM3 source code needs to be compiled using OpenCV4.2.0. |
Hi, @ZhaoDidididi. |
Thanks guys for your reply. I have reinstalled Opencv 4.2.0 but having new issue
This is in my laptop. Any idea what is wrong? |
hello,i solved this problem by replacing opencv4.5.0 with opencv 4.2.0 when i run mono mode, but when i run the RGBD mode i still face the problem: "ORBSLAM3-for-ROS2 stops working as soon as it receives one frame", i am confused, do u have any idea? |
Compile a separate cv_bridge for ORBSLAM3_ROS2. |
Thanks a lot for this beautiful work. I am publishing the sensor.image/Image type message from my one ROS2 node and trying to run ORB-Slam3 for the published topics. I have also edited the topic name in the monocular-slam-node.cpp. Even though I can see the stream of images as a video(continous frames) from the subscriber, the ORBSLAM3-for-ROS2 stops working as soon as it receives one frame. Any idea what I am doing wrong?
The text was updated successfully, but these errors were encountered: