SMT32WLE5 as Tx has link drops

[jlpoltrack]

When using STM32WLE5 as Tx, link drops are experienced when running code with the post-jitter changes.

Link drops occur every few minutes.

[olliw42]

foi https://discord.com/channels/1005096100572700794/1163909355234656267/1337748101527769128

[brad112358]

Is this reproducible without mavlinkx?

[jlpoltrack]

Few observations with E5 Mini

• Observed some drops on the commit prior to post-jitter, so potentially they aren't related
• Can't reproduce on regular MAVLink
• Tough to reproduce in general, usually happens once every 15 to 30 minutes
• Observed drops showed long time in mavlink/msp.do
• Not exactly helpful, but enabling the return here https://github.com/olliw42/mLRS/blob/main/mLRS/CommonTx/mavlink_interface_tx.h#L401 can run for multiple hours without issue

More of an FYI, G4 is 2.5x faster than WLE5 when measuring overall Tx loop time.

[jlpoltrack]

Doing some more testing, I see that even with regular MAVLink, Mission Planner reports missed packets when doing parameter download over MAVFTP. Not enough CPU?

[brad112358]

Doing some more testing, I see that even with regular MAVLink, Mission Planner reports missed packets when doing parameter download over MAVFTP. Not enough CPU?

Does enabling the return to do only one message per loop also avoid the missed packets with regular MAVLink?

[jlpoltrack]

Does enabling the return to do only one message per loop also avoid the missed packets with regular MAVLink?

I switched receivers from G4 using CAN to WLE5 using serial w/ Manu's settings. After ~15 minutes on the main branch, I saw a link drop. After only enabling the single message return, now been running for 100 minutes without issues:

[olliw42]

did b86cdf5
is not resolving the issue, but appears to mitigate it
see https://discord.com/channels/@me/1271130322460868650/1352355650818146477