Skip to content
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

Display BF4.3 log, gyro data not displayed correctly #589

Closed
jasc76 opened this issue Jul 15, 2022 · 1 comment · Fixed by betaflight/betaflight-configurator#3124
Closed
Labels

Comments

@jasc76
Copy link

jasc76 commented Jul 15, 2022

Describe the bug

I have a build with BF4.3 and the only thing that might be special is, that the fc is flipped upside down.
Gyro traces (here debug gyro scaled) but also the other gyro stuff is displayed totally wrong.
I randomly chose BBE 3.4 and it shows the data correctly
btfl_all.zip - Quad without props, armed and moved by hand
BBE3.6.0
BBe36
BBE3.4.0
BBE34

To Reproduce

Load attached log file in BBE 3.6 and 3.4

Expected behavior

Show data correctly

Betaflight Blackbox Explorer version

3.6.0

Add any other context about the problem that you think might be relevant here

btfl_all.zip

@haslinghuis
Copy link
Member

Please post a screenshot of your rates settings as it works fine with defaults settings.

The graph from your log would show up as before using the default case instead:

GraphConfig.getDefaultCurveForField = function(flightLog, fieldName) {
var
sysConfig = flightLog.getSysConfig();
var maxDegreesSecond = function(scale) {
switch(sysConfig["rates_type"]){
case RATES_TYPE.indexOf('ACTUAL'):
case RATES_TYPE.indexOf('QUICK'):
return Math.max(sysConfig["rates"][0] * 10.0 * scale,
sysConfig["rates"][1] * 10.0 * scale,
sysConfig["rates"][2] * 10.0 * scale);
default:
return Math.max(flightLog.rcCommandRawToDegreesPerSecond(500,0) * scale,
flightLog.rcCommandRawToDegreesPerSecond(500,1) * scale,
flightLog.rcCommandRawToDegreesPerSecond(500,2) * scale);
}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants