-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Camera frame moves crazy in RVIZ with D435i #114
Comments
As far as I know, many people have the same problem, including me. This phenomenon is very strange. Different cameras and different devices have encountered the same problem. I suspect that it is an algorithm problem or initialization. Troubled for a while, and do not know the solution. If you know some reasons or solve this problem, please let me know. |
Same here. It works great on MH_01_easy.bag. But when I use my own data, I got crazy camera trajectories. And every time the result is different with exactly the same setting. Could someone please give suggestions about how to identify and correct the problem? Thanks! |
I'm also having this issue from a rosbag file I created with an realsense R200. |
Any updates? I'm having the same problem? |
Perhaps you need to calibrate your IMU first |
I did it using the rs-imu-calibration tool by realsense. I also updated the IMU related parameters using Kalibr tool. |
I use realsense d455 to run VINS Fusion and get great result. I think d435i and d455 have similar config. There are some important points deciding whether the system is stable or not.
|
I used a RS415. I believe that the most important point, as mentioned by @dssdyx is the sync. After calibration with Klibr I got a value of 0.3 |
Thanks for sharing this great project!
When I tried it with RealSense D435i using your docker method and your d435i.yaml config file, it worked but while moving it very little movement I saw it moved crazy in RVIZ and didn't stop at all as shown in the attached
Note: I didn't change anything except for topics names and paths
The text was updated successfully, but these errors were encountered: