inav
inav copied to clipboard
iNavFlight
INAV 5: After Landing not able to arm due to "CLI ACTIVE"
Current Behavior
I was flying my fresh configured INAV 5 Wing yesterday and landed it after 50m (launch aborted- to little throttle). After having the wing at hand again I wanted to ARM and launch it again.
This wasn't possible at that moment as the OSD reported "unable to ARM CLI ACTIVE". I repowered the wing and everything was ok again.
Steps to Reproduce
currently I don't know how to reproduce this without just mumbling speculations -
Expected behavior
don't block the arming as no USB was connected and CLI wasn't used.
Suggested solution(s)
ARM :) ...
Additional context
Here is a video of it
https://user-images.githubusercontent.com/8381714/177255416-e0b77922-10b3-427e-899a-7cb6795b6ff1.mov
- FC Board name and vendor: MATEKF405SE
- INAV version string: 5.0.0 (3a379a7)
This is quite strange! The flight controller only enters CLI mode when it receives the # command via the MSP port. I don't know how this command was interpreted...
The only thing that can comes in mind while hearing MSP is that the ESP32-RADAR was connected to a free UART (MSP). That talks to INAV via MSP ... but we fly this pretty much and it never happened for us! I don't know if that could be the case. But others than that I could not build the bridge to MSP ...
@OlivierC-FR ... could this be possible?
The only thing that can comes in mind while hearing MSP is that the ESP32-RADAR was connected to a free UART (MSP). That talks to INAV via MSP ... but we fly this pretty much and it never happened for us! I don't know if that could be the case. But others than that I could not build the bridge to MSP ...
@OlivierC-FR ... could this be possible?
Well the ESP is not sending any # (on purpose at least), but I don't know what are the exact conditions for entering CLI mode, I'll try to have a look at the code INAV side. Ive never seen such message, I have ESP32 on almost all my aircrafts, but I don't think I ever had the case to relaunch after a nav landing so...
I don't any FC with INAV 5 yet to test that
The conditions for entering CLI are:
- There is no pending MSP processing (so it's not part of an MSP payload)
- 100ms elapses prior to the
#being received with no other activity on the port.
So it is unlikely that normal MSP processing caused this. Some noisy glitch on the serial connection (cosmic rays, sun-spots etc.) ???
As the X6 has detachable wings and it landed pretty rough, the right wing connecter perhaps came off - in the right wing the VTX is hidden. It has a serial connection to the fc ... disconnecting these for a super short time ... could that perhaps cause it?