Thank you much Mr. D! Very useful, especially when there isn't a windsock. I really appreciate you and the INAV team members for fulfilling my childhood and upward dreams of flight. I have one FC a Radiolink Mini that only runs AP. It flies like a robot. But Been growing with INAV since 1.5 with a Paris Sirius Air 3 on a Bixler2.
Thanks Darren! Great stuff! This has had me confused and I just gave up and left it there 😂. I think I’ll just enable the virtual sensor now and see if it helps.
Virtual airspeed together with the actual wind direction estimation works great and is essential for flying close to stall speed and planning landing direction. Also useful to see how windspeed and direction changes at higher altitudes. GPS ground speed is in my OSD for distance range estimation.
I completely agree. They are all really useful. I have Air Speed and Horizontal wind on my OSD. The accuracy is pretty good now too. I was flying last week with INAV, and my friend was flying the same route with ArduPilot. We saw very close values on the wind speed and direction.
The default receiver protocol is a per-target preference. A lot of more recent targets do default to CRSF. If CRSF is the protocol, the CRSF elements will be enabled on the OSD by default. So they would need to be removed before changing the receiver protocol.
Dead reckoning will be in INAV 8.0. You can read about it’s setup in advance here github.com/RomanLut/inav/blob/submit-gps-fix-estimation/docs/GPS_fix_estimation.md
Thank you much Mr. D! Very useful, especially when there isn't a windsock. I really appreciate you and the INAV team members for fulfilling my childhood and upward dreams of flight. I have one FC a Radiolink Mini that only runs AP. It flies like a robot. But Been growing with INAV since 1.5 with a Paris Sirius Air 3 on a Bixler2.
Thank You! I was beginning to think my OSD had ghosts! For my part I will use it and your great explanation makes it much easier.
Thanks Darren! Great stuff! This has had me confused and I just gave up and left it there 😂. I think I’ll just enable the virtual sensor now and see if it helps.
Virtual Pitot can be very handy.
Virtual airspeed together with the actual wind direction estimation works great and is essential for flying close to stall speed and planning landing direction. Also useful to see how windspeed and direction changes at higher altitudes. GPS ground speed is in my OSD for distance range estimation.
I completely agree. They are all really useful. I have Air Speed and Horizontal wind on my OSD. The accuracy is pretty good now too. I was flying last week with INAV, and my friend was flying the same route with ArduPilot. We saw very close values on the wind speed and direction.
Great solution, many thanks.
Great video. I just turned mine on.
Thanks, glad it helped 👍🏻
Your the best !😘
This happens a lot with CrossFire as many FCs are still set to CrossFire by default.
The default receiver protocol is a per-target preference. A lot of more recent targets do default to CRSF. If CRSF is the protocol, the CRSF elements will be enabled on the OSD by default. So they would need to be removed before changing the receiver protocol.
can you show how to setup dead reckoning RTH in case GPS is lost?
Dead reckoning will be in INAV 8.0. You can read about it’s setup in advance here github.com/RomanLut/inav/blob/submit-gps-fix-estimation/docs/GPS_fix_estimation.md
❤❤❤❤❤ happy times again,hope you keep well Darren.
CRSH ? With INAV
Yes, Course Hold has been in INAV for quite a while now.
Glad it isn't Crash?@@MrD
Is Marc ok Darren,havnt seen or heard in a while.