-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Vision position estimation fails depending on initial yaw (in Gazebo-SITL) #13116
Comments
@michael-p what version of the Firmware are you using? |
I tried this with the current master, but was also able to reproduce it with an older version (at commit 190c817). |
Why? You likely just need to remove FYI @kamilritz |
Yes I believe this was fixed in #12108, that's why I did not open an issue for it. I just confirmed that in v1.9.2 the problem exists as well, although the console output is slightly different: (the ERROR line is different)
|
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
I think I just ran into this as well. Pending further testing. @tzai can you try to reproduce using the iris_vision model in vanilla SITL (no ROS)? |
I think this should solve the issue: PX4/PX4-SITL_gazebo-classic#399 |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Describe the bug
Changing the initial rotation (yaw) of the copter
iris_vision
in Gazebo SITL causes the vision position estimation to fail. With different initial yaw like the default iniris_vision.world
it works, albeit very shaky.To Reproduce
Modify
iris_vision.world
by rotating the model:Run
make px4_sitl gazebo_iris_vision
, switch to position mode and take off, hover a few meters above ground. After a few seconds the copter flys away full speed, and then the failsafe kicks in and switches it to Altitude mode.Console output:
Expected behavior
Not sure, honestly :) Even with the default initial yaw of the model the copter is very unstable so maybe the noise/drift parameters of the Gazebo vision plugin are just too extreme? I don't know. However, I would at least expect the behavior to be independent of the initial yaw of the copter, that is, it should either always work or always fail (after some time maybe).
The text was updated successfully, but these errors were encountered: