1. There is some information that is not exported via mavlink (sensor temp, wind direction, Rx SNR levels, PID values), that is available via MSP Display Port. 2. Rendering is not that hard. More challenging is to create a good user-friendly configurator for that interface.
@@tipoman9317 fair point with configuration UI, PID values are available through param protocol, all of them instead of select ones like with MSP, Wind etc. are available, the only excption is custom temperature AFAIK. See SR parameters in Ardupilot
![ประสบการณ์ จ้าง Developer ที่ผมจะไม่มีวันลืม [ภาค1]](http://i.ytimg.com/vi/bzivN4KDg-k/mqdefault.jpg)
Hi , so you are working on Ardupilot. That's really great. Do post more videos about the setups
WOW, I love it!!!! When will it be available?
Yay finally 🎉
Great 🎉🎉
The font looks a little blurry.
It looks more organic on WTFOS. But well done anyway, some people probably like these fonts
How hard would it be to read MAVLink stream and render the HUD based on that instead of pretending to be an old analog OSD chip?
1. There is some information that is not exported via mavlink (sensor temp, wind direction, Rx SNR levels, PID values), that is available via MSP Display Port.
2. Rendering is not that hard. More challenging is to create a good user-friendly configurator for that interface.
@@tipoman9317 fair point with configuration UI,
PID values are available through param protocol, all of them instead of select ones like with MSP,
Wind etc. are available, the only excption is custom temperature AFAIK. See SR parameters in Ardupilot