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

Python API: unable to read new logs (error in #2239

raemin opened this issue Jan 11, 2019 · 3 comments


None yet
2 participants
Copy link

commented Jan 11, 2019

  • Seen in Main Branch Scripts as of 21/12/2018
  • Logs produced by firmware 2038 night build
  • On flight controller Seppuku

Issue details: Can log older logs (presumably wired), but Inconceivable logs crash the logviewer. , error line 1017, no header signature
(edit : discard these, as I made a "better" test later, see comments)


@raemin raemin changed the title Python API: Python API: unable to read new logs (error in Jan 11, 2019


This comment has been minimized.

Copy link

commented Apr 9, 2019

I've reverted back to wired, made a clean install, formated the openlagger sdcard, generated the log and could read them with the "pip installed" logviewer. No crash, nice graphs.

From then on I upgraded the firmware to inconceivable (2126), made another log and attempted to read it with the python scripts hosted on github (branch next as of april 8th). The viewer does not crash anymore, but all the graphs are empty.

See corresponding sample logs and screenshots.


This comment has been minimized.

Copy link

commented Apr 10, 2019

Commenting again this issue ...
The problem seems to be related to the latest python source! In fact I was attempting to read wired logs with wired scripts and inconceivable logs with inconceivable scripts. It seems wired python scripts are capable to read both wired/inconceivable logs, but inconceivable scripts do only produce blank graphs.

If you take the samples provided in my previous post, all the logscan be viewed using the python scripts from the "wired" branch.


there are a few warnings though

2019-04-10 (1)

Now the same "inconceivable" log as displayed by the "next" python scripts (as of April 8th)

2019-04-10 (2)

No warning in the console with these latest scripts.


This comment has been minimized.

Copy link

commented Apr 11, 2019

Thanks for the report, and your work to narrow it down. When time permits I can have a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.