Steve Evans

Being able to run MSP over a half duplex link as typically already exists between FC and VTX is a neat idea. Why do we need additional CMS support though?

@phobos- We have multiple similar menus, `trampMenuEntries`, `saCmsMenuChanModeEntries`, `cmsx_menuVtxEntries` with additional menus such as `trampCmsMenuCommenceEntries`, `saCmsMenuCommenceEntries` and `saCmsMenuPORFreqEntries`, `saCmsMenuUserFreqEntries`. After this PR is approved I'll check to see if defining...

Just checked to see if there was an issue with duplication of strings in the CMS entries. The compiler did a better job than expected... I compared the following in...

Is this when powered from a battery/USB or both?

I've left a MATEKF722SE running overnight and the OSD is still running. Looks like this may be painful to reproduce. ``` # status MCU F722 Clock=216MHz, Vref=3.28V, Core temp=47degC Stack...

Still going strong with a fairly busy display. ``` # status MCU F722 Clock=216MHz, Vref=3.28V, Core temp=50degC Stack size: 2048, Stack address: 0x20010000 Configuration: CONFIGURED, size: 4028, max available: 16384...

I'm testing with a `osd_framerate_hz = 12` as that's the same rate at 4.2. That would perhaps explain why you see failure after 4 hours at 5 times the rate...

Not happening here after 44147 seconds. OSD still updating. Can you reproduce this on another FC with a non-PixelOSD display? ``` # status MCU H743 (Rev.V) Clock=480MHz, Vref=3.30V, Core temp=53degC...

@hydra What state is the OSD task in when it hangs, and what are it’s predicted state durations?

Turn off LED_STRIP. You weren’t using it with 4.3.0.