inavflight / blackbox-tools Goto Github PK

HI, big fan of the blackbox tool project, having trouble with the latest INAV 7.1.1 updates. Any release updates for 7.1.1? Thanks.

Hi,

I tried blackbox logging and then decode the logged data to .csv files with blackbox tools.

However, the two output file for gps data lacks any meaningful timestamp. In the csv file, the 'time (us)' field is constant zero. In the gps file, 2000-01-01T00:00:00.000000Z is the timestamp in every row. On the other csv file there is correct time data.

Does anyone know why is this happening, or how can it be solved?

Thanks in advance for any help.

The project is licensed under GPL-3, but the LICENSE file is missing.

It would be useful to have the option to select a different mode, apart from Mode 2, for the on-screen overlay of the sticks. In Italy, Mode 1 is widely used for model aircraft.

blackbox_decode genarate a gpx file with not corresponds to the correct timestamp from log.txt file. It always some minutes above the correct time. Like 10, 8 or 3 minutes above correct time. Another observation: The osd displays the correct datetime!!!! :(

When decoding the attached log with blackbox_decode it prints

Log 1 of 1Statistics
I frames       1  112.0 bytes avg      112 bytes total
H frames       9    1.0 bytes avg        9 bytes total
G frames      13    1.0 bytes avg       13 bytes total
E frames       2    4.5 bytes avg        9 bytes total
S frames      10    1.0 bytes avg       10 bytes total
Frames         1  112.0 bytes avg      112 bytes total
Data rate: Unknown, no timing information available.

29011 frames failed to decode, rendering 31805 loop iterations unreadable.

and produces a CSV file that's only a few KB in size. However, when I open the log in INAV Blackbox Explorer I am not able to find any problems with the log (only a few dropped frames at 00:09.210). Betaflight Blackbox Explorer on the other hand is also not able to open the log.

I am using a serial logger and I know I am pushing it with the 250Hz logging rate but I would think if I can view the log I would be able to decode it. Is this a problem with my log?

LOG009.TXT

Hi,
My Inav BlackBox logs look strange, there are no graphs but boxes.
I already reflashed the Matek F722SE with Inav 2.5.1 but the issue stays.
Can you help me fix this issue?

Google drive link to one of my logs:
https://drive.google.com/file/d/1Xm7KhXEFCu-ZXsyHw_plfClZgWB8W8uF/view?usp=sharing

Screenshot:

I get a wrong value (-2147483648) of "energyCumulative (mAh)" in the second flight of a blackbox file produced by INAV 5.1.0.

Attached the blackbox.
blackbox_log_2022-10-08_114352.TXT

Hi. Currently blackbox decode for inav does not export debug variables as far as I can tell. It'd be great to add this.
cheers! -Brian (PIDtoolbox) https://github.com/bw1129/PIDtoolbox

Hi there.

I've noticed that in the headers of the exported CSV file using the blackbox_decode have a space before the heading name.
For example, "axisRate[0]" will actually be " axisRate[0]"

There is a problem with blackbox_decode 4.0 where a bogus column can appear in some records on a large log.

The release is withdrawn until this is fixed.

I notice that yaw set point and yaw RC command are not being logging in INAV 7. Tried logfiles from serveral different sources. It just shows a string of zeros. roll and pitch are fine. here is a screenshot of an example, zoomed 500%. yaw (YELLOW) is perfectly flat with no deviation from 0.

Current Behavior
Ground speed in various units, alt in cm

Desired Behavior
3D Speed is several units

Suggested Solution
Coded into inav BB decoder

Who does this impact? Who is this for?
All

Please.

I noticed that GPS altitude in the GPX files produced by INAV blackbox decoder appear multiplied by 10. E.G. if altitude in the goggles was 100 meters, the GPX file reports 1000. I played doing some tests crossing - Betaflight and INAV produced blackbox files - with - Betaflight and INAV blackbox decoders -. All codes and files were relatively recent. The test results have been:

decoder blackbox altitude

INAV INAV NOK
INAV Betaflight NOK
Betaflight Betaflight OK
Betaflight INAV OK

I did not debug code but I have seen in the Betaflight decoder source, commented that from rel. 4 onward "GPS_altitude" is coded in the blackbox in decimeters, not centimeters. The decoder for Betaflight does therefore correctly the conversion in meters.
The INAV decoder does no conversion.
An hypothesis: also INAV encodes now "GPS_altitude" in the blackbox in decimeters (and this is the reason the actual decoder reports it x10) ?

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Decoding log '/home/jrh/dl/LOG00017.TXT' to '/home/jrh/dl/LOG00017.01.csv'...

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7db7505 in __strlen_avx2 () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff7db7505 in __strlen_avx2 () from /usr/lib/libc.so.6
#1  0x00007ffff7cc3408 in __vfprintf_internal () from /usr/lib/libc.so.6
#2  0x00007ffff7cae56a in fprintf () from /usr/lib/libc.so.6
#3  0x000055555555dfbd in onEvent (log=0x7ffff7b4f010, event=0x55555556c6d8)
    at .//src/blackbox_decode.c:344
#4  0x000055555555ad04 in completeEventFrame (log=0x7ffff7b4f010, 
    stream=0x55555556cf30, frameType=69 'E', 
    frameStart=0x7ffff4ebfc4e "E\r\037\062P\316\002", 
    frameEnd=0x7ffff4ebfc52 "P\316\002", raw=false) at .//src/parser.c:1324
#5  0x000055555555b5c0 in flightLogParse (log=0x7ffff7b4f010, logIndex=0, 
    onMetadataReady=0x555555560001 <onMetadataReady>, 
    onFrameReady=0x55555555f608 <onFrameReady>, 
    onEvent=0x55555555dc79 <onEvent>, raw=false) at .//src/parser.c:1526
#6  0x0000555555560e95 in decodeFlightLog (log=0x7ffff7b4f010, 
    filename=0x7fffffffe143 "/home/jrh/dl/LOG00017.TXT", logIndex=0)
    at .//src/blackbox_decode.c:1195
#7  0x0000555555561855 in main (argc=3, argv=0x7fffffffdd38)
    at .//src/blackbox_decode.c:1493
(gdb) quit

Alas, not my log and I don't have permission to share it.