-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
drivers/optical_flow/paw3902: backup scheduling to fetch 0 flow #22086
Conversation
Do we need to update the PAA3905 driver to match? |
Yes if this checks out. |
Hard to tell if its better. It was always slowly yawing to the north. Did a mag cal and this is slightly better. Still has the bug where it slowly descends until it lands. I can see it now will publish 0,0 pixel flow. |
2a8093d
to
be92142
Compare
be92142
to
cf20203
Compare
- this sensor provides a MOTION interrupt used for default scheduling, but we also need to publish zero flow information
- this sensor provides a MOTION interrupt used for default scheduling, but we also need to publish zero flow information
cf20203
to
105318e
Compare
This is definitely better. This PR on the FC and ARK Flow. EKF_HGT_REF set to baro. There are times in a hover where the gyro noise causes a 0 flow value to have a compensated velocity. I wonder if we want to ignore the gyro when the pixel flow is 0? |
Added logic to only compensate when pixel flow if non zero and it flies great. I'm current doing it if either pixel flow value is non zero to compensate both axis. But it might be better to do it per axis? |
Great, that much better than before, the position is now rock solid while hovering. |
@AlexKlimaj I'm not sure if adding this logic is really necessary, the gyro noise should be centered around 0 so it isn't an issue. Did you see an improvement by adding that conditional gyro compensation? (I flew with it and it worked well, but I didn't try without) |
b6e0fad
to
105318e
Compare
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: https://discuss.px4.io/t/optical-flow-oscillating-position/34470/2 |
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: https://discuss.px4.io/t/holybro-optical-flow-sensor-thoneflow-oscillations-on-main/34768/1 |
The core issue here is that if there isn't motion we don't have a mechanism to know if the current 0 flow readings aren't stale.