-
Notifications
You must be signed in to change notification settings - Fork 1.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
Feature Request: Servo output logging in blackbox #1655
Comments
@miberlin PID_sum is more less equivalent to servo output |
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. |
Automatically closing as inactive. |
I would like this feature too. It would be nice to know what PWM value was sent to each output. Getting PID SUM isn't as transparent. I'm trying to see how much the FC is fighting to keep the plane flying flat and level on a calm day to work out elevon warping issues. |
@hali9 Your feature request have been closed by accident I will leave this one open instead if you don't mind. |
@shellixyz Ok. |
This can be closed |
Hey Guys,
coming from quads I am used to checking the motor outputs in my blackbox logs when I feel like one of the motors is broken. If I see that the quad tilts to one side even though the motor on that side is ramping up rapidly, I know that this motor is broken.
The same would apply to a plane - If the plane spins to one side and iNav tries to stabilize using the servos I could see in the blackbox file, which servo might be broken since this servo is going to get a higher signal than the others.
Is there any way we could get the servo output into blackbox?
Thanks a lot!
mi
The text was updated successfully, but these errors were encountered: