MSP_BOXNAMES

[glory727]

Through the serial port debugger, it is found that sending MSP_BOXNAMES returns：24 4D 3E FF 74 28 01 41 52 4D 3B 41 4E 47 4C 45 3B 48 4F 52 49 5A 4F 4E 3B 48 45 41 44 46 52 45 45 3B 46 41 49 4C 53 41 46 45 3B 48 45 41 44 41 44 4A 3B 42 45 45 50 45 52 3B 4F 53 44 20 44 49 53 41 42 4C 45 3B 54 45 4C 45 4D 45 54 52 59 3B 42 4C 41 43 4B 42 4F 58 3B 41 49 52 20 4D 4F 44 45 3B 46 50 56 20 41 4E 47 4C 45 20 4D 49 58 3B 43 41 4D 45 52 41 20 43 4F 4E 54 52 4F 4C 20 31 3B 43 41 4D 45 52 41 20 43 4F 4E 54 52 4F 4C 20 32 3B 43 41 4D 45 52 41 20 43 4F 4E 54 52 4F 4C 20 33 3B 46 4C 49 50 20 4F 56 45 52 20 41 46 54 45 52 20 43 52 41 53 48 3B 50 52 45 41 52 4D 3B 56 54 58 20 50 49 54 20 4D 4F 44 45 3B 50 41 52 41 4C 59 5A 45 3B 41 43 52 4F 20 54 52 41 49 4E 45 52 3B 56 54 58 20 43 4F 4E 54 52 4F 4C 20 44 49 53 41 42 4C 45 3B 4C 41 55 4E 43 48 20 43 4F 4E 54 52 4F 4C 3B 53 54 49 43 4B 20 43 4F 4D 4D 41 4E 44 53 20 44 49 53 41 42 4C 45 3B 42 45 45 50 45 52 20 4D 55 54 45 3B 52 45 41 44 59 3B BA。The payload size is greater than 255, but is FF, which causes it to fail the CRC. How to solve this problem?

[christianrauch]

Which firmware is this?

Via $M> the FC indicates that this is a MSP message for protocol version 1 (MSP v1), but MSP v1 only supports payload sizes up to 255 byte. A MSP v2 message starts with $X and supports payloads up to 2^16 bytes.

The payload has with ARM;ANGLE;HORIZON;HEADFREE;FAILSAFE;HEADADJ;BEEPER;OSD DISABLE;TELEMETRY;BLACKBOX;AIR MODE;FPV ANGLE MIX;CAMERA CONTROL 1;CAMERA CONTROL 2;CAMERA CONTROL 3;FLIP OVER AFTER CRASH;PREARM;VTX PIT MODE;PARALYZE;ACRO TRAINER;VTX CONTROL DISABLE;LAUNCH CONTROL;STICK COMMANDS DISABLE;BEEPER MUTE;READY; 296 characters, which does not fit in a MSP v1 message.

Maybe this is a bug in the firmware and it is supposed to either cut off the payload after 255 characters or switch to a MSP v2 message, which allows larger payload.