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

DSHOT + F7 falls from sky #6098

Closed
Xedos9er opened this issue Sep 4, 2020 · 6 comments · Fixed by #6127
Closed

DSHOT + F7 falls from sky #6098

Xedos9er opened this issue Sep 4, 2020 · 6 comments · Fixed by #6127
Labels
Milestone

Comments

@Xedos9er
Copy link

Xedos9er commented Sep 4, 2020

I switched to INAV after running this quad on BF for a long time.
Yesterday on my 3rd flight, the quad just crashed right after I took of and have done 2 rolls. I have attached the logfile from this flight, to me it looks like a desync on motor 3 ?? Am I right?
LOG00014.TXT

Setup I was running:
-Kakute F7 HDV
-BLHELI_32, 48khz, Demag High, Timing 20°
-2508 1200kv Motor
-2khz pid loop, 800khz I2C, DSHOT 300
-RPM Filter on

Throttle idle % is set to 7, wich is already higher than on BF. Never had issues with BF @ 4khz, DSHOT 300.
But on BF I was able to set Dshot min rpm, wich helps a lot to prevent desyncs.

@issue-label-bot issue-label-bot bot added the BUG label Sep 4, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label BUG to this issue, with a confidence of 0.69. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@DzikuVx
Copy link
Member

DzikuVx commented Sep 4, 2020

From the log I see that the board never rebooted or stalled and problems were with ESC connectivity. What's interesting is that it happened immediately after punch out and it looks like coincidence or electrical problem due to poor wiring. Please check Multishot

INAV has throttle_idle set to relatively high value by default and that prevents desync as well.

@DzikuVx DzikuVx added Support and removed BUG labels Sep 4, 2020
@Xedos9er
Copy link
Author

Xedos9er commented Sep 4, 2020

From the log I see that the board never rebooted or stalled and problems were with ESC connectivity. What's interesting is that it happened immediately after punch out and it looks like coincidence or electrical problem due to poor wiring. Please check Multishot

INAV has throttle_idle set to relatively high value by default and that prevents desync as well.

Hi Pawel,
thanks for the fast reply. Wiring is ok, I checked everything. But I noticed that motor 3 isn't running as freely as the other motors when spinning it by hand. It seems to have mechanical issues. Also notice the pitch wobble during a roll in the log, motor 3 has always to work harder. It also gets warmer than the other ones. This would also explain the nose pitching to the up left when Punchout, motor 3 doesn't accelerate as fast as the others. Seems like this mechanical issue leads to desync since motor 3 gets way to slow with 0 throttle on hard manouvers. I didn't notice this behaviour on BF since min_rpm (Wich is not available in INAV) compensates this issue. As far as I can remember, I always had this nose pitching in BF Wich never could be tuned out. Hope that makes sense what I discovered.
I would run multishot, but it doesn't support rpm filters.

@DzikuVx
Copy link
Member

DzikuVx commented Sep 9, 2020

Also verify Blackbox logging rate. If it's enabled with 1/1 it might be the reason

@Xedos9er
Copy link
Author

Xedos9er commented Sep 9, 2020

Yes, logging rate is at 1/1. What would you suggest

@DzikuVx
Copy link
Member

DzikuVx commented Sep 10, 2020

Set logging rate 1/2 or 1/4. SD Card operations are taking too much time and MCU has no time to process everything else.
On my hand, I will as a conditions that lowers the logging rate to safer levels

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.

2 participants