Not looking for anything specifically - I recently inherited a dev role for the MavLink_FrSkySPort teensy telemetry convertor project. I am just going through the code trying to make it more efficient and trying to spot any issues. I am not a dev by trade, so its taking me time to get a good understanding of the code. I have already applied a bunch of improvements and fixes, and from a -next branch (developed by another guy on the project) I have taken and integrated some code which listens for the STATUSTEXT messages and displays these on a dedicated LUA screen on the Taranis. It works to a point, but occasionally there is corruption in the message text. I've also done a tonne of changes to allow this project to integrate with the Ultimate LRS Tx/Rx and have the Teensy ground based now, feeding directly into the Taranis using sensor polling (and DIY Tx/Rx and antennas), so there are a lot of improvements to the teensy code - and also a re-design of the LUA telemetry screens also. Liknk is here if you are interested: https://github.com/Clooney82/MavLink_FrSkySPort/wiki
The reason I was asking about streams and messages belonging to them, is that the code sets up the stream rates, but only for three of them, and I have since added some additional telemetry to the code, so wanted to make sure I had all the required stream rates catered for in the rate configuration code. As ULRS means sharing a telem port between the Teensy and Mission Planner, I have only the MP connection with full bi-directional Mavlink, so the teensy only listens, so there is no way using ULRS to have the Teensy configure those stream rates anyway, so I have added a compile time option in the code to disable the stream rate config if that's preferred. Mission planner configures these anyway with its bi-directional connection (over bluetooth).
Anyway, I've gone on enough! Thanks for the interest and response, and have a great weekend, Paul