Skip to content
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

Frames Problem #5

Open
Haydar1990 opened this issue Feb 2, 2023 · 2 comments
Open

Frames Problem #5

Haydar1990 opened this issue Feb 2, 2023 · 2 comments

Comments

@Haydar1990
Copy link

Haydar1990 commented Feb 2, 2023

Hello, First of all thank you for the great work.
i have a problem and i hope you can help me.
i run realsense d435i with rs_rgbd.launch and i am trying to estimate the speed of it through orb slam
so i run this launch file rs_d435i_rgbd_inertial.launch but i am having a problem that the camera and imu frames in rviz always spinning and returninh to the world frame so they are moving little bit and then returning to the world frame and keep spinning.
and when the frames return to the fixed frame "world" repeated on the screen this message:

mnFirstFrameId = 3731
mnInitialFrameId = 3729
3373 Frames set to lost
not IMU meas
Map point vector is empty!
First KF:488; Map init KF:477
New Map created with 1206 points
Not enough motion for initializing. Reseting...
TRACK: Reset map because local mapper set the bad imu flag
LM: Reseting current map in Local Mapping...
LM: End reseting Local Mapping...
LM: Reset free the mutex
LM: Active map reset recieved
LM: Active map reset, waiting...
LM: Reseting current map in Local Mapping...
LM: End reseting Local Mapping...
LM: Reset free the mutex
LM: Active map reset, Done!!!

but i noticed that when i active the localization mode it moves normal.
can you please help me to know what i'm doing wrong.

@Haydar1990 Haydar1990 changed the title Frqmes Problem Frames Problem Feb 2, 2023
@Hamidraei23
Copy link

I have the exact same issue

@Mechazo11
Copy link

@Haydar1990 ORB-SLAM3 is a complex code. Until very recently I too have been facing something similar. I ended up using GNU Debugger (GDN) to systematically track my code's problem. That tool might help you in this case.

In my case, I have taken this repo and heavily modified the whole system hence I had a different type of exit code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants