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

MATEK F405 MINI: Blackbox record is dangerous #3824

Closed
lossUAVes opened this issue Aug 29, 2018 · 12 comments
Closed

MATEK F405 MINI: Blackbox record is dangerous #3824

lossUAVes opened this issue Aug 29, 2018 · 12 comments
Labels

Comments

@lossUAVes
Copy link

Current Behavior

When I start a recording in Flash chip with switch (assigned in modes), I arm motors with no airmode neither motors spining on arming, and when I start to fly the motors go crazy. The recorded archive seems corrupted and I can´t open it in blackbox viewer.

Steps to Reproduce

  1. Blackbox switch ON
  2. Arm
  3. Fly
  4. Crash

Expected behavior

Blackbox logging on flash chip with switch should work correctly on MATEK F405 mini with MATEKF405 firmware.

Suggested solution(s)

I don´t know...

Additional context

https://pastebin.com/THLhjWgH
  • MATEK F405 Mini
  • INAV, version: 2.0.0
@artusmuc
Copy link

Hello,

I have also a F405 Mini with activated blackbox. I have reduced to 50 % logging frame rate.
(MAG-BARO-LED-SMARTPORT-IRCTRUMP-SBUS)
I have only some problems with unbalanced motors - but i have no crash.

@lossUAVes
Copy link
Author

Ok, thanks. I will check my settings.

@giacomo892
Copy link
Collaborator

I had the same issue on 2.0 with F405-CTR and a cheap Kingston class 10 sdcard.

The suggestion is to use a fast sdcard like a SanDisk A1 and reduce logging rate.

Still this needs to be investigated and solved.

@DzikuVx
Copy link
Member

DzikuVx commented Sep 4, 2018

Problem indeed seems to be related with the fact that gyro, looptime and SD card are working on high speed. Either lower looptime or sd card speed and test. Runnig blackbox on rates higher then 2kHz (1/2 rate in this case) does not makes much sense (we rather do not deal with frequencies above 1kHz). Even 1kHz (1/4 for this config) adds very little to the log.

@lossUAVes
Copy link
Author

lossUAVes commented Sep 4, 2018

I have slowed down to 1/32 and the quad is vibrating violently. I have tried to decrease the looptime and it also starts to vibrate. I imagine that this time it will be the PIDs. If I decrease the looptime it seems that I have to tune the PIDs again. At the moment I still can not record data.

@lossUAVes
Copy link
Author

The file that I was able to record yesterday I opened it with blackbox viewer, but it will not let me open it with Plasmatree analyzer. Is it possible?. I downloaded an inav txt file and it seemed that analyzer also works with inav.

@giacomo892
Copy link
Collaborator

May you post it here?

@lossUAVes
Copy link
Author

@lossUAVes
Copy link
Author

I have managed to use the blackbox and I have recorded some tests, but I can not open them with PlasmaTree Analyzer. I have also included axisD[2] to test but I still can not open them. I can not find anymore on the internet.

@stale
Copy link

stale bot commented Dec 31, 2018

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Dec 31, 2018
@shellixyz shellixyz removed the Inactive label Jan 3, 2019
@stale
Copy link

stale bot commented Mar 4, 2019

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Mar 4, 2019
@stale
Copy link

stale bot commented Mar 18, 2019

Automatically closing as inactive.

@stale stale bot closed this as completed Mar 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants