inavflight / blackbox-log-viewer Goto Github PK

Current Behavior

BB Spectrum Analizer fail to read INAV 5.0 bb txt file. And showed "infiniteHz" in its x axis.

Steps to Reproduce

1. Transfer log0001. txt file to pc
   2.open with INAV BB viewer 4.0
2. Open Analyzer graph

Expected behavior

Valid x axis frequency reading

Suggested solution(s)

Improve INAV Bb for 5.0

Additional context

• FC Board name and vendor: KakuteH7
• INAV version string: 5.0 RC3

The log is not readable ...
There were a lot of problems with RTH, how to look?
JNAV/FLYWOOF411 3.0.1.8
BB 3.4.0
Message error "Your video could not be loaded, your browser might not support this kind of video. Try Google Chrome instead."
blackbox_log_2021-07-16_164510.zip
INAV_cli_Mark4_7inch_20210716_164358(Bat_Cur-mAh_Calib).zip

The attached LOG is sourced on Inav 3.0.2

On BBox 3.4.0 -> PID_Sum fields are populated correctly.
On BBox 4.0.0 -> PID_Sum fields are shown as (NaN).

LOG00062.TXT

Thanks

Instead of redirecting to inav's 3.0.2 version

If there isnt a linux release, can you guide me through building on from the source code plzz?

I'm using the latest blackbox explorer (9333f41).

When I open a log file everything is fine, however the "View/hide analyser display" doesn't seem to work at all. When clicked, the window is not shown and the icon doesn't turn yellow.

Did it change? It used to work for me some time ago...
I'm on mac (if it matters), latest chrome.

I downloaded the latest version and tried to open a file. Nothing happens, there is no message. I've tried several other log files.
I can open the file with the Cleanflight/Blackbox-log-viewer just fine.

Using the attached file I cannot see any frequencies in the analyser display, it just says "InfinityHz".

Tested on windows and linux versions of latest blackbox log viewer, inav 2.5 (maybe 2.5.1?) on a F405-CTR
LOG00003.TXT

I wasn't able to debug raw gyro. Here the log I used from 1.8 OMNIBUS F3

LOG00004.TXT

Add debug_mode support as in Betaflight

I see "InfinitvHz" on frequency axis of spectrum analyser. My log:
LOG00010.TXT

Just created a bbox file and downloaded it on Matek F722 w/3.0.1, only 19MB (not the full 32MB). Gives the error seen in #58 and does nothing. Advice?

Application crashes while trying to load a logfile with following message:
ERROR:render_process_host_impl.cc(4723)] Terminating render process for bad Mojo message: Received bad user message: FileChooser: The default file name should not be an absolute path ERROR:bad_message.cc(27)] Terminating renderer for bad IPC message, reason 123

It happens only on the second file you try to load within blackbox explorer

As the title

When trying to load any video, I get "could not play this video, try Chrome". While it's odd that a desktop app asks me to try Chrome, I think this is actually not a video issue (it happens with many formats), but a path issue, because of the following steps:

1. I click "open video".
2. I select "/tmp/myvideo.mp4".
3. "Video could not be loaded, try Chrome".
4. I click "open video" again.
5. The dialog box says "_tmp_myvideo.mp4".

I think the explorer tries to sanitize the path and then can't find the video at the sanitized location, so it fails.

Would it be possible to add a convert/render osd (as configured on fc) function so you could lay this over your hd footage?

Long Blackbox log files seem to be recorded correctly in INAV. However, Blackbox Explorer (v3.4.0 tested) apparently uses a 32 bit value in an internal time representation, and apparently with 1uSec time quanta hits the limit of the 32 bit value and truncates the log at about 71 minutes. An older "Cleanflight" version does not show this issue. It is not yet clear if mwptools is OK.

BB Explorer should use 64 bit timestamps, that's gotta be good until we get much better batteries.

Attached is a sample log that in fact is about 140 min of runtime but shows up at ~71 min.
2021-04-03_140_min_decimated_200_blackbox_log_2021-04-03_204321.LOG

Note that this log file was recorded with blackbox_rate_denom=200 to drop the sample rate down to about 5Hz so that the log would fit into the small-ish FC dataflash.

The frequency axis in the analyzer view shows infinite frequency. I am using the latest release version of iNav7 and the Blackbox log viewer available at the time of posting. The data from iNav appears valid and I can do the FFT and plot in Octave, so this seems to be a problem with the blackbox log viewer.

When I click "View / hide analyser"
There is nothing. No any response.

My log file is from onboard data flash chip.

current state:
Debugging altitude issues is quite hard as the navPos[2] seems to be on a different Y-scale as the baro(m).

Here for example the readings are almost identical, but the lines are not close to eachother

A few seconds later, barometer reads 56m, so I would expect the green line higher than the red navPos[2].

expected behaviour:

It should more look like this (data exported and graphed), the red bar marks the same second/altitude as in the BBE above:

version:

• iNav 2.4
• BBE 3.4.0

rcCommand is mapped to dps, while should stay unitless. This creates confusion. Either map rcCommand to dps or remove unit

Hi,

Blackbox done with Inav 3.0.1 shows the wrong inflight adjustment. The value is right but the name of the setting is wrong. See attached image.

I was tuning pitch P, roll P, roll D, pitch D and got: Yaw I, Pitch I, rate profile, roll rate

I am trying to sync my video with the blackbox data stream and the instructions in the Syncing your log to your flight video section refer to a "start log here" button for which there is none.

Is this function implemented? If so, what is its purpose?
Before I close a BB log session I save the workspace, hoping that it saves log to video offset but the file generates is a null json

{
"graphConfig": [
null,
null,
null,
null,
null,
null,
null,
null,
null,
null
]
}

Could be neat is we can display the navPos[2] value in meters inside the brackets so it can be directly compared with baro.

Clicking on "3.0.2" button points to Betaflight Blackbox Explorer and not to iNavFlight Backbox Log Viewer.

All decimals do

The message "Error opening log: No logs in this file could be parsed successfully" shows up when I try to open LOG files created with INAV 2.2., all the older LOG files can still be opened and examined without problems.
LOG00103.TXT
INAV Blackbox Explorer! Version 3.2

Flown today, log not readable.
Too bad because there was a problem to analyze, a return to home where there was an anomalous behavior of the throttle.

blackbox_log_2021-06-13_183730.zip

iNAV 4.1.0
iNAV BlackboxExplorer 4.0.0 (do not see a newer version)
FC = Lumenier LUX-H7-HD
Logging works. Must remove SD card to retrieve logs. This happened last version and a minor version update to iNAV 4.1.0 or iNAV BlackboxExplorer fixed the issue.
Any additional data available upon request, happy to provide, just tell me what you looking for...
Regressed iNAV and Betaflight to see if was working in previous versions and it was. No hardware change, just new iNAV versions.

When more than 1 graph is setup and a single graph selected to view, the other graph setups are lost if Blackbox is closed with the single graph view still selected. You have to close the single graph view and return to the all graph view before closing Blackbox in order to save all the graphs that have been setup so they are available the next time BB Viewer is run. Export Workspaces doesn't seem to work so it's not possible to save graph setups.

Would be good if this could be fixed to avoid having to setup graphs again if you forget to deselect single graph view.

I set the yaw cutoff filter to 200hz but after BlackBox file check it's standing on 2hz

Got confused and originally posted to the cleanflight repo even though I am using the INAV blackbox log viewer.. so I'm reposting to the appropriate repo.

Hi all, I am running a Lumenier F7 dual gyro f7 controller with the Matek F422SE firmware on INAV. I recorded a flight using the blackbox logger with a Beitian 880 GPS and compass module and tried to view the log. The explorer is unable to parse the data and returns the following error:
Missing field encoding header for field #0 'GPS_fixType'

WIth Blackbox decode tools I was able to get three files out, but they are very short and do not contain the logs.

open attached bb produced by inav (a bug I think) and get noise

LOG00001.zip

File is correctly generated in apps forlder but fails packaging phase

Looking at logs, heading (yaw) values are randomic for some flight.
When ok, yaw heading shows a 70 (about) degrees offest added value to the range 0-360.
Many flights analyzed, always same behaviour.

Note (may help) : inav Mag configuration is not 0, it is cw 270 flip.
Setup:
FC mateksys F722-STD + magnetometer and gps
InavFlight 2.6.1
Inav log viewer 3.4 (bot Linux and Win32)

Any idea ?

Alfredo

I think there might be a mismatch in some parameters' name, between INAV and "INAV - Blackbox Explorer".
For instance:

• in inav source file blackbox.c there is this line

      BLACKBOX_PRINT_HEADER_LINE("min_throttle", "%d", motorConfig()->minthrottle)
  

• while in the "INAV - Blackbox Explorer" flightlog_parser.js file one finds

    case "minthrottle":
            that.sysConfig.minthrottle = parseInt(fieldValue, 10);
  

In other words inav's blackbox writes "min_throttle" in the header, while the viewer expects "minthrottle".

There are other parameters with the same problem.

Looking at logs, gps latitude and longitude are not shown, cannot find any value representing horizontal position.
Many flights analyzed, always same behaviour.

Setup:
FC mateksys F722-STD + magnetometer and gps
InavFlight 2.6.1
Inav log viewer 3.4 (bot Linux and Win32)

Any idea ?

Alfredo

LOG00016.TXT

Suspicious Log-file is included

Blackbox problem: "Error opening log: No logs in this file could be parsed successfully"
INAV Blackbox Explorer version v3.3.0
FC - Matek F405ctr
Changing the recording speed modes: 100/88/80/75/67/50 /% ... etc., as well as replacing the SD card and reformatting it, did not solve the problem.
Replacing the flight controller with a similar one did not solve the problem.
Plasmatree / PID-Analyzer - crash when trying to open a log file.
Your cakes are inedible gentlemen! It's time to start cooking normal food)))
LOG00001.TXT

If possible,please add time and date to the multiple entries inside a log file.For example i have a one log file that i copied from my internal flash which contains multiple entries from different flying sessions from different days.It would be nice if the entries can reflect the actual date and time when Flight controller added that entry to the log file.Thanks

I was trying to launch the latest release of the app on macOS BigSur. Unfortunately, the app is not opening. I can see the app menu in the top bar but when trying to open a file app closes. I was opening the app considering that it was not signed.

Also now with the new mixer configurator should be aware that we have only 1 motor on a wing.

INAV blackbox-log-viewer downloaded today 28 Dec 2018 starts in Chrome browser, allows me to select a log file to open but does not open it, does nothing !, no error messages etc..
Log files tried are 2,857KB and 10,096KB recorded yesterday on SDcard using MATEK F722 STD running v2.0.1
CHROME says I'm running latest version, Version 71.0.3578.98 (Official Build) (64-bit), on Win7 PRO on Intel i5
Assistance most welcome :-)
Thanks Steve

Matek F722-px .file blackbox log not opening. it says something like "this video can't be opened" it worked before a few days ago then suddenly doesn't.??????????????

I've got some strangeness going on with yaw heading readings in the log viewer:

Yaw heading reads up to about 430 degrees and then jumps to 70 degrees whilst rotating, so it appears to be displaying an offset of 70 degrees.

I have attached a 1/1 log of the issue, the log involves taking off, yawing 360 one way and then the other before landing.
I have been viewing it with mag and heading graphs.

blackbox_log_2017-10-14_104719.TXT

FrSky telemetry shows correct heading readings, OSD recording of test flight shows correct headings and iNav configurator shows correct headings: by correct I mean the compass moves smoothly through all normal (0-359) readings whilst rotating.
As far as I can tell the compass is calibrated:

INAV/SPRACINGF3 1.7.3 Oct 4 2017 / 18:19:22 (974440df)
align_mag = DEFAULT
mag_hardware = HMC5883
mag_declination = -30
magzero_x = 104
magzero_y = -191
magzero_z = -47
mag_calibration_time = 30

I have been debugging possible interference issues with the on-board compass and finding these readings in blackbox log viewer threw me a bit.

I wasn't sure where to post this but as the telemetry and MSP driven OSD seemed sane I thought that it might be a viewer issue or a case of bad calibration.
I have tried to re-calibrate the compass a few times but the issue has persisted.

When gyro task runs at different frequency than pid task, the frequencies on the analyser graph are shown incorrectly.

The following log was captured with 8k gyro loop and 4k pid loop. The oscillation period on gyro is ~7ms (~150Hz). The analyser shows peak at 4x lower freq (~38Hz):

LOG00008-gyro8k-pid4k.TXT

When using 8k gyro loop and 2k pid loop the peek was shown at 2x lower freq (~77Hz).

flight controller: MATEK H743
Inav 5.1

When I'm trying to open the files with debug_mode = GYRO I get the following message:
Error opening log: No logs in this file could be parsed successfully.

Spectrum graph shows gyro LPF 1Hz

Explorer 5
Telemetry data from inav 5.1

I have tried exporting a graph over video and it seems that the graph data is NOT zoomed or un-zoomed according to the display setting.

This results in a video where the graph data moves too quickly, losing some of its overall impact. It would be nice if it was more what you see on the display is what gets rendered in a video.