#analyze my blackbox for me?
37 messages · Page 1 of 1 (latest)
i'll be more than happy to provide more info.
also it was a very windy day but it held like a damn champ
Honestly it looks pretty good and clean. It's a bit hard to tell because the logging rate is so low though
It looks like it's using an F7 FC, I'd expect that to be able to log at least at 1/4 sample rate
ok good to know. yeah for some reason it was at 1/16 which is ridiculous.
i’ll record at 1/2 next time.
is 1/2 safe for the f7?
Should be, but check your CPU usage before you bump up the logging rate
how would i do that?
what’s a safe CPU load? will it even matter, since it starts logging only after arm?
Depends on the fc. I aim for 30% or less on the bench. And yes it does matter, if your CPU hits 100% when you arm, the quad becomes unpredictable and any number of things can happen including it not disarming when you tell it to
well yeah that’s what i meant. it only logs when I arm, and i can’t tell what % the CPU is at on the bench since i can’t arm on the bench.
that’s what i meant by doesn’t matter lol, not that it doesn’t matter that CPU is being tortured
Yea I kinda want to add a CPU indicator to the OSD elements for stuff like this. Wouldn't be used often, but it'd be nice to have
yeah for sure
but like setting the logging to 1/2 or 1/16 wouldn’t reflect on the bench though, right?
only when you arm
so you can’t tell if it’s too high
Correct, AFAIK there isn't a way to tell when you're out flying
Other than weird behavior
Hmmm
this is a problem the submersible industry saw before :>
FWIW I've run 1/4 on both an F722 and an F405 before with no adverse effects
great! i'll run 1/4. should i try 1/2? or is it too risky
ok good to know. thanks. i’ll do a flight sometime and send it here again :)
hey @desert jackal !! I have another log now, with 1/4 logging rate.
here it is:
not sure what the "all" file is supposed to represent. i also have the 1,2,3,4,5 files as well
"all" is a single file that contains all of the blackbox logs, instead of having them in separate files. I'll use the one you sent. I won't be able to look at it until I'm back at my PC later tonight though, probably after 9PM Eastern
no problem. for some reason this "all" file is shorter than the other files...
take your time, you're doing me a favor :)
All in all this looks pretty good to me--not sure if there was something specific you were looking to fix
The only thing I see that I might consider playing with would be the TPA settings
Nothing specific. Just wanted to make sure it looks clean. What's a TPA setting? Why do you say I need to play with it?
should i bring it back? like lower it?
also i get some nice prop wash when using a gopro
TPA stands for Throttle PID Attenuation. It basically dampens the PID gains as you raise the throttle in order to keep everything stable. If you notice bad PID behavior in the high throttle range, that's an indicator that TPA gain needs to be turned up. I did notice some wobble in your D gain in the high throttle, which is why I mentioned it, but it really isn't that bad. Only if you want to spend a bunch of time getting that tune perfect
I'm not surprised that you get more prop wash with a Gopro vs without. The extra weight makes the PIDs work harder. Try copying your existing PID profile to a new profile, and turn the D gain up a little on the new profile to use when you're flying with the gopro