-
Notifications
You must be signed in to change notification settings - Fork 60
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
Spontaneous reboots (crossfire) #94
Comments
I noticed the BT module disconnecting and reconnecting from time to time (probably due data overflow or some other reason) and at the time the BT is reconnecting the reboot or cli screen seems to happen. But in most cases it just reconnects and tracking keeps working as it should |
possible solution: add some guard function: while a HomePosition is set, don't allow a reboot or entering Cli_mode |
Dear @skaman82, have you experienced new reboots after the Fix? |
In your video2 there is not a reboot, it simply enters in CLI mode because string 'RRR' is received. That is what evaluateOtherData function does, it waits string 'RRR', and if found, it enters CLI mode. Your fixes avoid checking 'RRR' string, that's a good solution for this scenario, but not for the reboot one. |
@raul-ortega no, I had no reboots after my fix |
I am experiencing some spontaneous reboots mid flight. Telemetry is coming in via BT (115200) from crossfire @ 10Hz. Either the racker just reboots and sets the new homepoint (somwhere where the Aircraft currently is in the sky) or it enters the CLI mode. Both is pretty unfortunate.
This happens not often but almost every 4-5th flight. I was able to reproduce it just with the OLED, FC and BT module - so the problem seems not to be electrical - most likely a code crash or some bug in the CRSF code or in the Serial Code. Maybe the hight telemetry rate (10-12Hz) is causing some unexpected behavior. I think somehow some code triggering the reboot or CLI mode. Sadly it is almost impossible to reproduce on purpose.
Unfortunately this is a big safety issue and I can't trust the tracker in this state as this can't happen mid-flight.
Ver. 11.0.1. spracingF3 and 11.0.0 naze32 - happening on both. CRSF version 2.42.
Video1 reboot mid-flight: https://youtu.be/Mv7_NI18nV8
Video2 Reboot and enters CLI mode on its own (usb is not connected to anythig): https://youtu.be/NGOIjhrDRl8
The text was updated successfully, but these errors were encountered: