Robert

This is issue to summarize new features & bring UI concept, so thx for adding older ones. I just repeated concept 'Recent' system label. :) After reading it seems that...

Hey @druckgott, Did some tests lastly on iNav MSP over CRSF and there are few problems with current implementation

1. Missing proper MSP version in response's CRSF status byte . When Master (radio) sends MSP packet with version 1, Slave (FC) should respond with same version number (ie 1)...

2. Missing MSP command in response.  Just after payload size (ie 3rd byte in response) there should be MSP command ID before actual payload. Again It is missing comparing...

3. Padding CRSF Frame containing MSP response shorter than CRSF frame is not needed. It only slows down processing with non relevant information. 

4. MSP checksum is optional. CRSF frame is protected by it's own CRC, so no need to add MSP checksum. EdgeTX is checking only CRSF frame checksum (CRC) Haven't checked...

Basically iNav MSP even in ver 1 is missing changes that was done to BF two years ago :) But you mentioned BF PR in first post. To test v2...

1. We have a little space here so I'd add CODENAME under VERS if build is release or RC (same scheme as in splash) 2. Since QR code is in...

> Left side: > Up = OK, RADIO SETTINGS > Down = OK, SCREEN SETTINGS > Left = OK, MODEL SETTINGS > Right = NONE > Press = OK, RTN...

Then it should be sent when FC is in disarmed state not when Configurator is connected via usb. For safety reasons I disable anyway in LUA script all MSP requests...