-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Drone fails mid-air on second run #531
Comments
reverting back to: 199e558 does indeed solve the problem. |
Hi! It is not impossible I messed something up when I converted to static memory. It seems as the assert you hit is in xQueueSemaphoreTake() which indicates that it is a semaphore that causes the problem. Does it happen to all your Crazyflies at the same time? Can it be reproduced with the unmodified synchronizedSequence? If not, is is possible for you to share the script you use? |
I can confirm this problem. How to reproduce:
|
It turned out that it was a stack overflow in the high level commander task. #509 moved the task stack from the heap to static memory and this cased an overwrite of the lockTrajBuffer semaphore buffer that is located next to it in the memory map. This can not be a new problem as the stack size has not changed, and it is good that we found it! |
@Yoyasp Please verify that it works for you as well |
@Yoyasp, can you please confirm so that we can close this issue? |
I've not had the issue since. Not sure how to test it extensively though... |
FlightTab: Remove unused flightmode.ratepid param
My drones seem to be failing mid air when i do a second run.
I use a modified version of the synchronizedSequence example.
When i look at the console output i get the following messages:
The drone falls to the ground and Led 1 starts blinking red in bursts of 5-8 (to fast to count)
Im using a lighthouse deck with 2 V1 basestations, i've tried both methods (with EKF and with crossbeam), i also tried with and without the mellinger controller.
It seems to happening consistently 3 seconds after takeoff (on the second run)
Might have something to do with the latest commit?
The text was updated successfully, but these errors were encountered: