Fantastic and very informative video!! Thank you for the flowers Darren but you forgot to mention that it was YOU that made this fantastic programming PID profile happened :) Thank you again for your great work! love it
Im new to Inav and flashed 4.0 to my F411 WSE FC and couldnt get my pwm elrs receiver working so I put in a CRSF instead. Now I know exactly why the pwm didn't work lmao. Thanks so much for this deep dive into Inav 4.0. so much good content
No problem Jonathan, I’m glad the video was helpful. 100% go with the serial connection. They’re so much better than PWM, even when it used to work. You get everything over those 2 wires. Hope you have some great flights.
Darren, thank you very much for your dedication and the great collaboration that your videos give us to our projects and knowledge. This is much easier, hahaha. Greetings from CRC Pura Vida !!!!
It’s pretty nice now that it does less 🤣 It tunes the rates and FF, which are the most important parts. The default PID settings are going to be fine for most planes.
Thanks for the effort making this video. I'm still missing the option to calibrate the airspeed sensor. auto calibration rutin will be a dreame but the minimum is the option to enter a factor to correct the airspeed reading. I wish you all iNav developers a Merry Christmas and Happy New Year.
You’re welcome Itzik. I had a quick look in the CLI and there is pitot_scale. Which sounds like it would be used to correct the airspeed reading. However, it’s labelled with TODO in the docs, so there may not be anything behind it. I’ll have a check of the code to see. github.com/iNavFlight/inav/blob/master/docs/Settings.md#pitot_scale
I’ve not used this before. But I’d guess you’d take the speed in to wind and with the wind, divide them with each other, and that should give you the scale.
Hello! excellent video. Check, my GPS burned out in flight, and my aircraft suddenly landed in an emergency. Is there a possibility to configure that emergency mode?
No, there is no configuration for emergency land. The first thing to check would be why the GPS burned out. Too much voltage? I guess this was in a navigation mode at the time? There’s no reason why you shouldn’t have been able to fly it back in a regular flight mode.
This great. Thank you D. I know this takes up a lot of time. Is an update of the transmitter set up for 4.0 on the fixed wing group page coming to compliment the new changes coming as well? That would be nice. It's a little behind in that regard. Thanks again mate. Cheers.
Thanks Charles. To be honest, as far as the INAV Fixed Wing Group models go, there aren’t any real differences between iNav 3.0 and iNav 4.0. Though, you may find the next Wing Talk interesting.
Another fine video, thank you very much. Can I use iNav 4.0 configurator to update parameters in a model that has iNav 3.x software without upgrading the model to iNav 4.0?
Glad you enjoyed the video. No, you should match the configurator to the firmware. So iNav 3.a.b Configurator should use the iNav 3.a. Firmware, 4.a.b should use 4.a.
I'm wanting to get my grandpa into scale fpv fixed-wing flights. He used to fly airplanes but had some health issues. Return to home, loiter, osd, and iNAV lua script for simulated instruments are all things he would be interested in. There is always a strong prevailing crosswind at the field where he flies, so a compass is definitely a good idea to set up. I have been having a hard time finding anyone willing to discuss how to set it up and ensure interference is minimized from electric motors and servos on a fixed wing scale airplane. Do you have any "use at your own risk" advice that might help? Edit: will an airspeed sensor reduce the need for compass in high wind? (Up to 20 mph)
Hi Chuck. It's great that you are looking to get your grandpa in to scale FPV. The view will be amazing from that cockpit. As far as a compass goes. Nobody mentions it for fixed wing as it's not recommended. The compass actually makes the navigation modes less accurate in a crosswind. With the compass, they end up getting pushed sideways, and spiral in to the destination. Whereas GPS only will fly straight to the destination. So my advice would be to not use a compass at all. Navigation will work better without it.
Hi John. There’s not really a lot to it. You set the nav_fw_launch_idle_motor_delay to the time you want in ms. For example a 5 second delay would be set nav_fw_launch_idle_motor_delay = 5000 Then when you go through the launch procedure, the delay will be added before the idle throttle is applied. So: 1. Be in a non-navigation flight mode 2. Enable launch mode (if not permanent) 3. Arm 4. Select post-launch flight mode 5. Raise the throttle to post launch throttle - At this point the delay will start. If you have a beeper, the double beep will change to a quadruple beep, just before the idle throttle comes in. 6. Throw the plane. If you need to abort and any stage, lower the throttle, then disarm. github.com/iNavFlight/inav/blob/master/docs/Settings.md#nav_fw_launch_idle_motor_delay
First of all thank you for your massively informative and comprehensive videos! I updated my Dolphin to 4.0 after the maiden flight, which was shortly before 4.0 came out. No Issues, flew pretty well on stock PIDs yesterday as it also did on 3.0.2. Today I tried Autotune and it tuned the Feed Forward but the rates where untouched. I am pretty sure the Dolphin can do more than 180. I did not bang the sticks excessively, I stopped after I felt it becoming more responsive. I am new to fixed wings after having flown freestyle copters for years and it is a completely different kind of animal and I have to get used to airodynamics playing a role in what I want do do ;). My question now is if I have to do Autotune longer or even apply full rolls and loops to get the rates tuned?
Thanks Bernhard, and welcome to the rebellion 😁 It sounds like you didn’t do enough with the autotune. But, you didn’t say if the 180 was pitch or roll. Pitch is maybe a little low, but pretty close as a guess. With autotune, you want to do full stick deflections. The movements will start off slow, but increase as the tune progresses. I usually start with the roll axis, then move on to the pitch. That way I can roll 90 degrees, then pull hard back on the pitch. This way stall isn’t an issue. In the description, I linked to a video by Marc Hoffmann. He goes through the tuning process there. It’s a great video and covers the PID aspect too.
@@MrD Thank you for the quick reply. It was 180 Degrees Roll. The rates were left untuched after the tuning process only Feed Forward was changed and it was noticeable. I did some more flying in Acro mode for the rest of the pack to get more comfortable with the craft and will try again next time. I have to say I massively enjoy the more analogue feel of wings compared to copters additional to the significantly longer flight times.
To be honest, the lower rates may have been handy for that flight and making the transition from quads to fixed wing. Once it’s fully tuned, it’ll be a level up again. Flight times, yep, massive difference. I guess the dolphin is good for 20-30 mins depending on how you fly and the battery.
@@MrD I think you are perfectly right here. Your guess is also extremely accurate. 22 minutes wit two 4s 1300 in parallel and Just shy of 30% capacity left according to the Lipo checker. The efficiency was 77 mAh/km at an average speed of 69 km/h. Pretty efficient with a T-Motor F80 2200 kV, Gemfan 6042 and a takeoff weight of 940 Gramms (120 mil laminate ond both wings and stabilisers adds around 40 to 60 gramms). Max Speed was 160 km/h with a pair of five year old Lipos on a straight line. There is room for more with fresh Lipos. So i guess this is a pretty damn good allrounder.
Sounds pretty good. Sounds like plenty more mAh would fit in there too. You could easily double that flight time with a more plane oriented battery or LiIon pack.
Hello I have a drone and when throttle between -75 to -100% the yaw, roll and pitch do not work. When throttle stick is in up position to -74% and more then yaw , pitch and roll work. Where is the parameter in CLI that controls this behavior. I would like to change it to have yaw, pitch and roll work when Throttle at lowest position -100%. Thanks.
This sounds strange. The roll, pitch, and yaw should work all the time. No matter what the throttle is set to. What happens on the receiver page? Do you have any mixing in your transmitter?
f405-wing plus crossfire I hadn't used this INAV model for 3 years- b4 crossfire was sending fc telemetry to my tx perfectly. Was attempting to use an R9mm never got it right. Now trying to get back to crossfire- tried everything I can but no fc telemetry is going to my tx. Is there anything critical to set up with crossfire to ensure fc telemetry coming over? Always seemed automatically came over on all my fc's. Might be a stupid question but at wit's end here now!
If you're using UART 2, I would bet that SmartAudio is still enabled on SoftSerial. That will stop the telemetry working on Crossfire. You could either disable SmartPort on the ports page, or just disable CPU serial ports on the configuration page. The easiest way with an R9MM is to set it up to use F.Port. Then use the "Inverter S.Port" pad, connected to Tx2 on an F405-WING. Still disable CPU based serial ports. Then set the receiver protocol to FPORT and turn inverted protocol ON. Half duplex could be left on AUTO.
I tried your advice on the R9- managed to flash the R9mm to ACCST fport from flex. Then discovered NO ACCST firmware for the R9 module would bind to the rx. Was going to try flashing ACCESS firmware to both- and there is NO fport firmware on the site. There is always something with frsky to tear your hair out. lol UPDATE- th R9 unit I bought in 2018 is red- the color they now assign to the R9M 2019. But it is NOT 2019 firmware I guess. how confusing. They later offered me an upgrade if I traded it in. ridiculous. Using the oldest firmware for an R9M I was able to bind with similar age Fport firmware for the R9mm. One battle won now to try for original goal to get fc tlmtry onto my QX7!!!
Yes, there are 2 models of R9M modules. The 2019 supports ACCESS and ACCST (you have to choose one or the other); whereas the original R9M only supports ACCST. To use ACCESS, your transmitter also has to support ACCESS. You should be able to use the latest ACCST firmware on both the receiver and module, and they’ll sync up. Having said that, the last time I looked, the latest firmware is from early 2019. But it’s solid. F.Port on flex is the firmware option to go for. As a side note, with ACCESS there is no longer a separate F.Port firmware. It is simply an option on the receiver. Making everything much simpler. This tool may help you in seeing which receivers and transmitters are compatible. Plus which firmware version is needed on them www.mrd-rc.com/tutorials-tools-and-testing/useful-tools/frsky-receiver-compatibility-tool/
@@MrD your therapy is bonafide- and it WAS a matter of mental health if I didn't get this model in the air would die trying! the migraines were killing me and now thx to you all systems up and running- grabbed the latest ACCST fport flex I had overlooked like you said and presto
Can Inav be setup simmilar to Spectrum Safe A3230 controller for begging pilots. My daughter got a Apprentice STS 1.5 and we have 2 Radiomaster TX16S Max's that I wanted to eventually use to do some FPV combat with her. I guess I know it has Geofence, but is there a keep upright, and bank angle limiting features. Anyone know of any vids on these subjects. Thank you.
Hi Edward. I’m working on an OpenTX model for LOS. That has a basic geofence, plus minimum and maximum altitudes. This is using the iNav programming for the most part. Angle flight mode self levels the plane when you take your hands off the sticks. Once that’s ready it will be up on INAVFixedWingGroup.com
To be honest, it depends on what version you’re running. And if pre-3.0 how well you tuned the rates. Personally, I’m putting everything on 4.0 because of the better rates and FF tuning, better defaults, the new RTH climb option, continuous servo trim, and auto level. Those features all make the update worth it for me.
So that would be on 2.4 or 2.5 I guess. In which case, I would update. Maybe try the AR Pro first and see how you get on. But unless you’ve spent a fair amount of time tuning it, I think it would probably fly better on defaults after an autotune.
@@MrD Yes i think your right. im only asking because some times certain firmware updates can be worse, then better. Iv had plenty of that with Betaflight in the past,which is totally different i know. i shall give it a try then if its any good. Thank you
@@MrD Bummer, just tried flashing my F411 multiple times, and I'm getting is the dreaded bootloader failure. The boards fine and already has 2.5 still on it...after 10 tries iv give up ..😔
Please, I’m about to change to Ardupilot, I need to use the 2 motors in a wing in a way it’s giro stabilized so I can fly a wing without vertical stabilizer fins, please anyone, how do I do it????? If even possible a VTOL tail sitter!
Wings without vertical stabilisers are supposed to have stabilising properties built in to the airfoil. Such as the Prandtl. Another option would be split elevons, like on the B2. Relying on motors for yaw stability it not ideal, as they are usually pretty inbound.
@@MrD I understand, my project needs only for the 2 motors to be giro stabilized, just like the elevators and ailerons in horizon or angle mode, I enabled the thrust vectoring, I can yaw, ok, but the giro and acc have no command on motors, and I really need that! Is there a mixer that makes that? Thanks 🙏🏼 I really need the motors compensating for yaw like in a quad! 🥺
@@MrD I need something like this, my project is not wingtip motors and it’s not efficiency related, but the motor yaw stabilization is exactly this in 5:35 of the following video ua-cam.com/video/Vi9FqIAG0Rg/v-deo.html
That’s an interesting video. Though it didn’t seem to really add any benefits over using vertical stabilisers. The 2% better efficiency isn’t really statistically significant, and could simply be through different conditions. I’ve not checked the code. But if you’ve tested the differential thrust and it’s not stabilised. There will not be a simple way of just switching it on. It will need to be coded. So the earliest it would be available would be iNav 5.0, if someone takes up the task. iNav 5.0 would likely be mid 2022. I saw the PR and discussions on GitHub. But this should really have been raised as an issue. That is the place to put bugs, problems, and also feature requests. I have moved the discussion in to the issues area for developers to check out.
@@MrD yeah, sorry about it, new on GitHub and no clue in coding 😪 But you guys fixed it, thanks So I’ll wait for 5.0, it’s not about efficiency, I have a project that asks for an almost strait wing as low profile as possible, also want to benefit of a takeoff of just releasing the wing vertically and auto launch controlling also the yaw axis in the first seconds so it does not tip to the side, and also would be great to lock the yaw instability giving one less axis of turbulence, at least yaw would not oscillate,… it would be really a good add on, in the options of wing thrust vectoring a wing thrust vectoring giro stabilized yaw or something like that for choosing, in my testings with wings, found out that puller motor upfront is way better than a push design, but it gets props in front of FPV but 2 2306 quad motors gives all the goo things, no prop in view, better stability and handling, easier to launch (no motors in hand) thrust vectoring (finally yaw on wings) and the possibility of stabilizing the yaw axis to have a better stable FPV flight experience ;) And thanks for answering 🙏🏼
Fantastic and very informative video!! Thank you for the flowers Darren but you forgot to mention that it was YOU that made this fantastic programming PID profile happened :) Thank you again for your great work! love it
Thanks mate. I’m not really one to blow my own trumpet. Paweł also was involved in the profiles too. I’m sure quite a few pilots will find it useful.
@@MrD :) I know you're not, that's why I mentioned it. You deserve all the credits! Well done mate
Let's go to the therapist. Thanks, Darren. Cheers from a beach in Brazil
I think we’re all beyond that Silvio 🤣
@@MrD yeahhh Happy New Year, my friend
Im new to Inav and flashed 4.0 to my F411 WSE FC and couldnt get my pwm elrs receiver working so I put in a CRSF instead. Now I know exactly why the pwm didn't work lmao. Thanks so much for this deep dive into Inav 4.0. so much good content
No problem Jonathan, I’m glad the video was helpful. 100% go with the serial connection. They’re so much better than PWM, even when it used to work. You get everything over those 2 wires.
Hope you have some great flights.
Darren, thank you very much for your dedication and the great collaboration that your videos give us to our projects and knowledge. This is much easier, hahaha.
Greetings from CRC Pura Vida !!!!
No problem. The 2.6 and 3.0 videos seemed to help show the new features. It’s easier commenting on some of it too, especially when you’ve coded it 🤣
Thanks so much. These inav releases just get better and better worth updating for sure
You’re welcome. Enjoy iNav 4.0 🙂
thanks
I'm excited about the auto-tune
It’s pretty nice now that it does less 🤣 It tunes the rates and FF, which are the most important parts. The default PID settings are going to be fine for most planes.
Great! Thanks for your video. Very Very helpful. :O)
You’re welcome Ard 👍🏻
Loved I NAV wish I could have flew once :( you have a great day! 👊👊💪💪
Thanks. I hope you had a good Christmas. I hope one day you will get in the air.
@@MrD one day I hope to meet in heaven.. 👊👊💪💪
Thanks for the effort making this video. I'm still missing the option to calibrate the airspeed sensor. auto calibration rutin will be a dreame but the minimum is the option to enter a factor to correct the airspeed reading. I wish you all iNav developers a Merry Christmas and Happy New Year.
You’re welcome Itzik.
I had a quick look in the CLI and there is pitot_scale. Which sounds like it would be used to correct the airspeed reading. However, it’s labelled with TODO in the docs, so there may not be anything behind it. I’ll have a check of the code to see.
github.com/iNavFlight/inav/blob/master/docs/Settings.md#pitot_scale
I just had a look at the code, and it should be taken in to consideration for the IAS calculation.
@@MrD you are the best! I'll play with it and see. Thanks.
I’ve not used this before. But I’d guess you’d take the speed in to wind and with the wind, divide them with each other, and that should give you the scale.
Hello! excellent video. Check, my GPS burned out in flight, and my aircraft suddenly landed in an emergency. Is there a possibility to configure that emergency mode?
No, there is no configuration for emergency land. The first thing to check would be why the GPS burned out. Too much voltage? I guess this was in a navigation mode at the time? There’s no reason why you shouldn’t have been able to fly it back in a regular flight mode.
This great. Thank you D. I know this takes up a lot of time. Is an update of the transmitter set up for 4.0 on the fixed wing group page coming to compliment the new changes coming as well? That would be nice. It's a little behind in that regard. Thanks again mate. Cheers.
Thanks Charles. To be honest, as far as the INAV Fixed Wing Group models go, there aren’t any real differences between iNav 3.0 and iNav 4.0. Though, you may find the next Wing Talk interesting.
@@MrD I'll be certain to have a listen.
Another fine video, thank you very much. Can I use iNav 4.0 configurator to update parameters in a model that has iNav 3.x software without upgrading the model to iNav 4.0?
Glad you enjoyed the video. No, you should match the configurator to the firmware. So iNav 3.a.b Configurator should use the iNav 3.a. Firmware, 4.a.b should use 4.a.
I'm wanting to get my grandpa into scale fpv fixed-wing flights. He used to fly airplanes but had some health issues. Return to home, loiter, osd, and iNAV lua script for simulated instruments are all things he would be interested in. There is always a strong prevailing crosswind at the field where he flies, so a compass is definitely a good idea to set up. I have been having a hard time finding anyone willing to discuss how to set it up and ensure interference is minimized from electric motors and servos on a fixed wing scale airplane. Do you have any "use at your own risk" advice that might help?
Edit: will an airspeed sensor reduce the need for compass in high wind? (Up to 20 mph)
Hi Chuck. It's great that you are looking to get your grandpa in to scale FPV. The view will be amazing from that cockpit.
As far as a compass goes. Nobody mentions it for fixed wing as it's not recommended. The compass actually makes the navigation modes less accurate in a crosswind. With the compass, they end up getting pushed sideways, and spiral in to the destination. Whereas GPS only will fly straight to the destination. So my advice would be to not use a compass at all. Navigation will work better without it.
was wondering how to set up the countdown in inav launch? is there any info that explains the launch settings in detail ?
Hi John. There’s not really a lot to it. You set the nav_fw_launch_idle_motor_delay to the time you want in ms. For example a 5 second delay would be
set nav_fw_launch_idle_motor_delay = 5000
Then when you go through the launch procedure, the delay will be added before the idle throttle is applied. So:
1. Be in a non-navigation flight mode
2. Enable launch mode (if not permanent)
3. Arm
4. Select post-launch flight mode
5. Raise the throttle to post launch throttle
- At this point the delay will start. If you have a beeper, the double beep will change to a quadruple beep, just before the idle throttle comes in.
6. Throw the plane.
If you need to abort and any stage, lower the throttle, then disarm.
github.com/iNavFlight/inav/blob/master/docs/Settings.md#nav_fw_launch_idle_motor_delay
@@MrD thank you so much for your clarification on this it was a little confusing for me.
No problem John 👍🏻
First of all thank you for your massively informative and comprehensive videos!
I updated my Dolphin to 4.0 after the maiden flight, which was shortly before 4.0 came out. No Issues, flew pretty well on stock PIDs yesterday as it also did on 3.0.2. Today I tried Autotune and it tuned the Feed Forward but the rates where untouched. I am pretty sure the Dolphin can do more than 180. I did not bang the sticks excessively, I stopped after I felt it becoming more responsive. I am new to fixed wings after having flown freestyle copters for years and it is a completely different kind of animal and I have to get used to airodynamics playing a role in what I want do do ;). My question now is if I have to do Autotune longer or even apply full rolls and loops to get the rates tuned?
Thanks Bernhard, and welcome to the rebellion 😁
It sounds like you didn’t do enough with the autotune. But, you didn’t say if the 180 was pitch or roll. Pitch is maybe a little low, but pretty close as a guess. With autotune, you want to do full stick deflections. The movements will start off slow, but increase as the tune progresses. I usually start with the roll axis, then move on to the pitch. That way I can roll 90 degrees, then pull hard back on the pitch. This way stall isn’t an issue. In the description, I linked to a video by Marc Hoffmann. He goes through the tuning process there. It’s a great video and covers the PID aspect too.
@@MrD Thank you for the quick reply. It was 180 Degrees Roll. The rates were left untuched after the tuning process only Feed Forward was changed and it was noticeable. I did some more flying in Acro mode for the rest of the pack to get more comfortable with the craft and will try again next time. I have to say I massively enjoy the more analogue feel of wings compared to copters additional to the significantly longer flight times.
To be honest, the lower rates may have been handy for that flight and making the transition from quads to fixed wing. Once it’s fully tuned, it’ll be a level up again. Flight times, yep, massive difference. I guess the dolphin is good for 20-30 mins depending on how you fly and the battery.
@@MrD I think you are perfectly right here. Your guess is also extremely accurate. 22 minutes wit two 4s 1300 in parallel and Just shy of 30% capacity left according to the Lipo checker. The efficiency was 77 mAh/km at an average speed of 69 km/h. Pretty efficient with a T-Motor F80 2200 kV, Gemfan 6042 and a takeoff weight of 940 Gramms (120 mil laminate ond both wings and stabilisers adds around 40 to 60 gramms). Max Speed was 160 km/h with a pair of five year old Lipos on a straight line. There is room for more with fresh Lipos. So i guess this is a pretty damn good allrounder.
Sounds pretty good. Sounds like plenty more mAh would fit in there too. You could easily double that flight time with a more plane oriented battery or LiIon pack.
Hello I have a drone and when throttle between -75 to -100% the yaw, roll and pitch do not work. When throttle stick is in up position to -74% and more then yaw , pitch and roll work. Where is the parameter in CLI that controls this behavior. I would like to change it to have yaw, pitch and roll work when Throttle at lowest position -100%. Thanks.
This sounds strange. The roll, pitch, and yaw should work all the time. No matter what the throttle is set to. What happens on the receiver page? Do you have any mixing in your transmitter?
f405-wing plus crossfire
I hadn't used this INAV model for 3 years- b4 crossfire was sending fc telemetry to my tx perfectly. Was attempting to use an R9mm never got it right.
Now trying to get back to crossfire- tried everything I can but no fc telemetry is going to my tx.
Is there anything critical to set up with crossfire to ensure fc telemetry coming over? Always seemed automatically came over on all my fc's.
Might be a stupid question but at wit's end here now!
If you're using UART 2, I would bet that SmartAudio is still enabled on SoftSerial. That will stop the telemetry working on Crossfire. You could either disable SmartPort on the ports page, or just disable CPU serial ports on the configuration page.
The easiest way with an R9MM is to set it up to use F.Port. Then use the "Inverter S.Port" pad, connected to Tx2 on an F405-WING. Still disable CPU based serial ports. Then set the receiver protocol to FPORT and turn inverted protocol ON. Half duplex could be left on AUTO.
I tried your advice on the R9- managed to flash the R9mm to ACCST fport from flex.
Then discovered NO ACCST firmware for the R9 module would bind to the rx.
Was going to try flashing ACCESS firmware to both- and there is NO fport firmware on the site.
There is always something with frsky to tear your hair out. lol
UPDATE- th R9 unit I bought in 2018 is red- the color they now assign to the R9M 2019. But it is NOT 2019 firmware I guess. how confusing. They later offered me an upgrade if I traded it in. ridiculous. Using the oldest firmware for an R9M I was able to bind with similar age Fport firmware for the R9mm. One battle won now to try for original goal to get fc tlmtry onto my QX7!!!
Yes, there are 2 models of R9M modules. The 2019 supports ACCESS and ACCST (you have to choose one or the other); whereas the original R9M only supports ACCST. To use ACCESS, your transmitter also has to support ACCESS.
You should be able to use the latest ACCST firmware on both the receiver and module, and they’ll sync up. Having said that, the last time I looked, the latest firmware is from early 2019. But it’s solid. F.Port on flex is the firmware option to go for.
As a side note, with ACCESS there is no longer a separate F.Port firmware. It is simply an option on the receiver. Making everything much simpler.
This tool may help you in seeing which receivers and transmitters are compatible. Plus which firmware version is needed on them www.mrd-rc.com/tutorials-tools-and-testing/useful-tools/frsky-receiver-compatibility-tool/
@@MrD your therapy is bonafide- and it WAS a matter of mental health
if I didn't get this model in the air would die trying! the migraines were killing me
and now thx to you all systems up and running- grabbed the latest ACCST fport flex I had overlooked like you said and presto
Awesome! I'm glad it's all working for you. Now I hope you have some enjoyable flights :)
Can Inav be setup simmilar to Spectrum Safe A3230 controller for begging pilots. My daughter got a Apprentice STS 1.5 and we have 2 Radiomaster TX16S Max's that I wanted to eventually use to do some FPV combat with her. I guess I know it has Geofence, but is there a keep upright, and bank angle limiting features. Anyone know of any vids on these subjects. Thank you.
Hi Edward. I’m working on an OpenTX model for LOS. That has a basic geofence, plus minimum and maximum altitudes. This is using the iNav programming for the most part. Angle flight mode self levels the plane when you take your hands off the sticks. Once that’s ready it will be up on INAVFixedWingGroup.com
@@MrD sounds great! Thank you.
I agree version# much better not sure about red kite
It’ll be interesting to see what people think about this. So far, most people I have asked prefer the number.
if im still running older inav versions, and my wings are flying fine. Is there any point in upgrading? Cheers
To be honest, it depends on what version you’re running. And if pre-3.0 how well you tuned the rates.
Personally, I’m putting everything on 4.0 because of the better rates and FF tuning, better defaults, the new RTH climb option, continuous servo trim, and auto level. Those features all make the update worth it for me.
@@MrD I'm still running 2019 or 2020 settings.. she still powers up and fly's. Ar 900 pro and also Zohd Xl pro.
So that would be on 2.4 or 2.5 I guess. In which case, I would update. Maybe try the AR Pro first and see how you get on. But unless you’ve spent a fair amount of time tuning it, I think it would probably fly better on defaults after an autotune.
@@MrD Yes i think your right. im only asking because some times certain firmware updates can be worse, then better. Iv had plenty of that with Betaflight in the past,which is totally different i know. i shall give it a try then if its any good. Thank you
@@MrD Bummer, just tried flashing my F411 multiple times, and I'm getting is the dreaded bootloader failure. The boards fine and already has 2.5 still on it...after 10 tries iv give up ..😔
Please, I’m about to change to Ardupilot, I need to use the 2 motors in a wing in a way it’s giro stabilized so I can fly a wing without vertical stabilizer fins, please anyone, how do I do it?????
If even possible a VTOL tail sitter!
Wings without vertical stabilisers are supposed to have stabilising properties built in to the airfoil. Such as the Prandtl. Another option would be split elevons, like on the B2. Relying on motors for yaw stability it not ideal, as they are usually pretty inbound.
@@MrD I understand, my project needs only for the 2 motors to be giro stabilized, just like the elevators and ailerons in horizon or angle mode, I enabled the thrust vectoring, I can yaw, ok, but the giro and acc have no command on motors, and I really need that! Is there a mixer that makes that?
Thanks 🙏🏼
I really need the motors compensating for yaw like in a quad! 🥺
@@MrD I need something like this, my project is not wingtip motors and it’s not efficiency related, but the motor yaw stabilization is exactly this in 5:35 of the following video
ua-cam.com/video/Vi9FqIAG0Rg/v-deo.html
That’s an interesting video. Though it didn’t seem to really add any benefits over using vertical stabilisers. The 2% better efficiency isn’t really statistically significant, and could simply be through different conditions.
I’ve not checked the code. But if you’ve tested the differential thrust and it’s not stabilised. There will not be a simple way of just switching it on. It will need to be coded. So the earliest it would be available would be iNav 5.0, if someone takes up the task. iNav 5.0 would likely be mid 2022.
I saw the PR and discussions on GitHub. But this should really have been raised as an issue. That is the place to put bugs, problems, and also feature requests. I have moved the discussion in to the issues area for developers to check out.
@@MrD yeah, sorry about it, new on GitHub and no clue in coding 😪
But you guys fixed it, thanks
So I’ll wait for 5.0, it’s not about efficiency, I have a project that asks for an almost strait wing as low profile as possible, also want to benefit of a takeoff of just releasing the wing vertically and auto launch controlling also the yaw axis in the first seconds so it does not tip to the side, and also would be great to lock the yaw instability giving one less axis of turbulence, at least yaw would not oscillate,… it would be really a good add on, in the options of wing thrust vectoring a wing thrust vectoring giro stabilized yaw or something like that for choosing, in my testings with wings, found out that puller motor upfront is way better than a push design, but it gets props in front of FPV but 2 2306 quad motors gives all the goo things, no prop in view, better stability and handling, easier to launch (no motors in hand) thrust vectoring (finally yaw on wings) and the possibility of stabilizing the yaw axis to have a better stable FPV flight experience ;)
And thanks for answering 🙏🏼