@MrD, I'm not sure if this matters, but at 23 min, you started talking about ground course vs. heading. In full-scale aviation when I plan a flight, especially instrument flight, with approaches to get out of the clouds. Before launch. Bearing is the direction we want to go. After launch, course is the degree to the waypoint. Heading is, as you know, the direction the nose faces in degrees relative to north. Bearing is the always updating degree to the waypoint. (Ground) track is the actual path over the earth. Heading vs. track is how I explain it when teaching instrument flying. I hope this helps.
So in relation to INAV, ground course is what you call track, and heading is still heading.. It's interesting to hear the full size terminology. Thanks for sharing 👍
Yes. Bearing is the path from point to point. Course, (future), is where you want to go. It is always a straight line. Heading, (current), is the direction your nose points with continuous correction for relative wind. Track, (past), is the path you have taken. Future, present, & past are milliseconds apart.
Thanks for the INAV project progress update Darren. Lots of fantastic upgrades and new features! The X-Plane integration wasn't something I was aware of and it appears might be useful for testing and simulation, perhaps even planning waypoint missions. BTW: Seeing X-Plane 12 is now listed.
Oh 100% waypoint missions work. Anything that you can do in INAV will work on the HITL. I’ve even seen Marc using autolaunch 🤣 I’m sure it has been used with X-Plane 12. But there were some issues. Roman’s repo for the integration plugin is here github.com/RomanLut/INAV-X-Plane-HITL There is a lot of useful information on that page.
great video and overview about what is going on and what to expect. Can not wait to see the horizont drift been gone - hopefully forever. Still a great video as it has been last year too even though this one was not about a released. But gave me a quite full update about the progress and features coming . thanks a lot - also to Marc for finding the secrets in the log.
Impressive work. 💪 The large amount of improvements are well worth the waiting. Wind estimator, ground course and cross track error, Glide time, glide distance, and climb efficiency and so on. Walksnail implementation has convinced me to go that way because OSD is most helpful to fly FC wings. And I don't like hack's, compatibility questions and other restrictions. Thanks for all the new goodies.
There will be basic support for O3 in INAV 6.0. It will mimic the BetaFlight OSD, like how ArduPilot works with O3. However, there will be a lot of elements that will not display correctly. The only way for a proper, fully featured OSD is if DJI fully implemented MSP DisplayPort (it would be nice if they stopped calling it canvas too) and allowed pilots to upload fonts to the goggles. The only other way would be another hack, like the WTF DJI OSD for the last generation of goggles and airunits.
It will be a very handy feature. It does have its limitations. But for the first up to 2km, it will definitely help. Of course, the RTH should still be set up for the flying environment. After that 2km (max), it will revert to a standard RTH.
@@MrD mine was less than 1 KM away. It just went behind a hill and tried to RTH when it got my control signal. I wasn't thinking about the hill being a problem. That was the test flight to try RTH. It was still set to drop as failsafe. Then we got 2 feet of snow. It is private land, so it isn't a big deal. I'll find it someday. I lost my brand new Upgrade Energy Dark Lithium pack and my Runcam 2 4k. I guess it was all new, but those were the expensive parts. And the Mamba stack.... hopefully someday I can recover and salvage something.
Ah, that sucks. I hope you find it. But, I don’t think the RTH trackback will work if failsafe is set to drop. I can ask. But I believe in that situation it would still drop.
@@MrD I am even more interested in that idea. Yes, failsafe should drop as intended. However if my RTH command were following the "track back" path, my command link should have been reestablished well enough fly in a different direction.
Thanks for the update. Not gonna lie though, bummed about extra arming safety. I read the github log on it, feels like an unnecessary restriction on a genuinely helpful feature
You're welcome. To be honest. I don't see any reason to have extra arming safety off for normal flying. I can only see it causing more problems than being useful. allow_bypass is still there, which should cover all bases where off would have been used previously. disabling the extra arming safety is only really supposed to be used for testing, or if you have a drone that you may occasionally fly indoors.
This is pretty straightforward. You just setup an airplane mixer, then add the flaps to the mixer. This may help with the flaps setup th-cam.com/video/qY1TwINNX6c/w-d-xo.html I don’t get what you mean by 7 channels for your airplane and 2 for FPV. I’m hurt you mean 7 for the full house glider setup. You don’t need 7 channels for that. The mixing is done in INAV. Only 2 channels for everything else seems like hardly any to be honest. I can think of at least 3 for the most basic setup. You at least need arm, modes, and tuning.
Hi Darren, maybe you can give me a tip. I have a Ranger T1 with 2 engines. I use INAV 6 . Everything works fine except for the motors. One motor starts at 2% the other at 18%. What is the reason and is there anything I can set in INAV 6? Greetings Didi
March damn I was hoping for January. WP sound great I use my planes to take pictures of our crops. So the days of walking into corn fields are a thing of the past. Kinda wish we could save more WP but I make due. Can’t wait on 6.0. So the other day I contacted you in regards of a current censor issue thought I had it fixed but no😢. No when I first plug in batt read 130amp then slowly drops down to 30amps and fluctuates for 18 to 30amps kinda strage. I’ve had problems with both h743 wing v1 fc that I have don’t like em at all. No pdb board now and still same problem I have a 470uf on esc one one battery lead that may be the issue cause I usually put cap on f/c on esc out maybe I got to many capacitors. Only have two on hole system. Only thing new to my set up is Maytek xt60 pdb w/voltage filter. Must be the cause of all this. Not big deal now cause still in testing. May be a problem when I start working this spring last year I used xuav cloud with 3.5 to 4 hour flights so u can understand why I need to figure this out. I mean technically I could stil fly with out amp meter but I like have all the info I can get in osd. Current set up maytek h743 wing v1 inav 5.1 Ps has to be that pcb voltage filter u know they slip over a xt 60 plug no wait I put them on other planes and no problems he’ll I don’t know I believe I got two bad f/c from Maytek no big deal have a good one and thanks again for all the help and videos
Hi Aaron. There are more cool things in the pipeline for waypoints too. There is the ability to add user actions to waypoints. In the INAV programming tab, you can use the user actions to trigger things to happen, like operating a PWM channel to start recording on a camera. The advantage of the user action over doing this using the waypoint index is that you can use the same user action on multiple waypoints, so only need the programming once. This wasn't in the video because it hasn't been merged yet. But it is very close now. You can't have too many capacitors on power lines. All they will do is smooth it out. So I don't believe that's a problem. Though, you should only really need on on the ESC (not the ESC pads on the FC), to reduce noise from the ESC to the FC. I've not seen the XT60 with voltage filter before. If this is just a TVS diode, that won't cause a problem. It just protects the battery and other components from voltage spikes.
@@MrD so your saying that I’ll be able to drop a WP say when I want a picture and it will take the pic on its own I was gonna make that suggestion this summer but got busy and didn’t plus I wasn’t real familiar with WP at the time and wasn’t sure if was already available. And to be honest still not familiar with WP or had the time to explore all available options. What I did was use two crossfire receivers set WP mission and then operated the camera with second controller sure wish cross fire would come out with a sixteen channel receiver. Worked pretty good I think I needed six channels to run cam zoom,start stop vid,still pictures required a channel, pan and tilt was something else maybe menu very nice only thing I wish I had was gps position on pictures in dvr. Not sure if that is even possible. And continuous recording instead of 12 min files gets confusing after 6000 acres. Would like to have a more professional way to keep track of what field I’m in. But for now spray paint work great paint a big number on the road and problem fixed long as it’s asphalt and not gravel any way thanks man wish I could help out more maybe next year I don’t see things getting any better though they are predicting a 30% increase next year per acre from plant to harvest so moneys kinda tight
Hi Daren I've just see the latest Painless 360 video about iNav 6.0. Please don't telme the maiden video of lesson 8 of your iNav setup series, you ar going to up date to the iNav 6.0... I'd sugest to finich and at the hend, say the word! OK?
Great work and thanks to all involved. I do however have a problem with "Targets" and as I think you have modified a few you seem to be my only hope. I have a T-Motor Pacer F7 board and it will not connect to iNav 5 or 6, targets when both TMOTORF7 and TMOTORF7V2.targets are flashed. In Betaflight, sorry to mention it, a target exists for T-Motor pacer F7, TMPACERF7. I need iNav for its GPS functionality can you help or should I donate my board to the scrap bin and invest in a supported board.
BetaFlight targets are not the same as INAV targets. So you can’t flash a BetaFlight target and have it work in INAV. The only T-Motor targets that exists in INAV is TMOTORF7 and TMOTORF7V2. For other targets to be supported, T-Motor would need to reach out and work with the INAV developers to get their targets added. There are policies for adding new targets to INAV github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md
@@MrD Thanks for that so quick well done! To summarise then unless T-motor asks for the targets to be written it's the "scrap bin" for my flight controller. Do you know of any developer who has an "unofficial" modified target that may work? if so I am prepared to risk it, waste some time, and try it out, if not, do you know of a charity that can use a brand new T-Motor Pacer F7 let me know and I will donate. meanwhile, keep up the good work. Regards John
Unfortunately not for that target. The best thing to do is contact T-motor. Unless they know there’s a demand. They have no impetus to make or commission a target.
Thanks for your further support. I have returned the board to Ali Express as I considered it is not fit for purpose. I should get a refund . Regards and hanks John
I always find the AHI a bit distracting TBH, a ladder variant would be a Nightmare...If they've finally fixed it, I'll have it on an alternative OSD for in cloud flying ...Will it work with Walksnail HD yet?...😳😳🙄🙄🇬🇧
5.1 works with Walksnail. There are a couple of minor issues. But, these will be addressed. I’m hoping to have sorted a couple of things before 6.0 is released. Like the order for switching on the goggles and VTx, and the artefacting characters that you can get with packet loss. I’m currently building an AR Pro to test.
@@MrD Great, thanks for the information. It's going into a quad first off using BF and I know that works. I have a Ranger G2 with 1.2g video and CRSF but I'd like iNAV and WSnail on it this coming Summer...😳😏😏🇬🇧
Well, hopefully it all goes well in that week we call summer 🤣 I’m just starting a new quad build no. I’m tempted to get a WS VTx for it. However, I’ve noticed that Caddx have lowered the price now. So I may wait for the UK vendors to catch up. It should be about £129 for the micro set.
@@MrD Yes, I'm building a new 5 inch quad with the 19mm WS camera..I also recently got the WS Goggles too...Then I pre ordered the new VRX and another 19 mm camera and VTX. They have now shipped that and I'm waiting for it. I have a big 10 inch monitor with HDMI input for the VRX and FW flying...😳😏🇬🇧
Removing the NAV arm safety option is a bad call IMO. People using this sort of thing are doing it partially because they want control over how it all works. If we want a bunch of safety guard rails we can just buy a DJI. Please leave the user in control as much as possible.
Omg I'm so dumb. I thought the changes to HD zero where in the preview it had said something about keeping the elements in the center so I spent like a day moving them closer together flying closer flying and was doing it through the cli because speedybee doesn't work with 6.0 yet, ended up getting frustrated and ordered the walksnail vrx.
To be fair to Speedybee. It's not out properly for another 3 to 4 months. But I can see how that would get really frustrating, changing that in the CLI. How are you liking the FP other than that though Ruby?
Hi Stephen. The feature preview has been used for a while. And so far, there have only been a couple of minor bugs found. The main one off the top of my head is the incorrect ESC temperatures in the OSD. The flying aspect of it has been great. I would say it’s as safe as any release candidate. So if you’re happy with release candidates, you may like to try 6.0 out. Check the release notes though. There are some settings to update after you have restored your diff. Also, my tool I show in the video is not needed for the feature preview.
@@MrD Thanks Darren, much apreciated. I'm in process of loading it on a WingWing Z84 🙂 On a different subject is Konstantin still an active INAV developer ?
I’m adding a zoom able cam to one of my builds would it be possible in global functions to slow the pan servo down when cam is zoomed in. If not possible in inav . If not can I do programming in radio. Can u add mixing to a channel 5-12 could I program a mix I. Radio as long as it’s not AETR. I’m not exactly sure how to do it but I think I have an idea 19:4919:53
The problem is the slow functions will only really add lag. I guess what you need is more resolution from the input (slider or head tracker). For this, you need the camera to move less for the same amount of movement of the input. You could do that in INAV using the programming tab to detect when the camera is zoomed in or not. Then in the mixer, for the pan mix, use the logic conditions to switch between 100% weight on the pan servo and 50% weight.
@@MrD I’ll try it out still need to get a base tune I’m adding all this to that rmrc anaconda this plane is awesome leading edge flaps wow. Super slow flyer be good for lost cattle and crop reviews. Anyway might be a few before I get it all worked out. I’ll let you know how it turns out thanks man
Firstly, ArduPilot’s OSD is not supported by DJI 03. ArduPilot mimics BetaFlight’s OSD which is why 03 “works”. In reality it is a cut down OSD with lots of missing elements and bad symbol substitutes. It is not ideal at all. There is a PR in INAV now, which also mimics the BetaFlight OSD. Again, this has hugely reduced functionality (even more so than ArduPilot, as INAV has more OSD features in the first place). You will see symbols not supported by BetaFlight as ?. If you want a proper, fully supported OSD on any firmware other than BetaFlight. You need to complain to DJI. Get them to fully implement MSP DisplayPort (and stop calling it canvas, that is something else entirely), with pilot uploadable and selectable fonts. Without that, DJI will only ever be a hack on anything other than BetaFlight.
Thanks Darren for your work. I do fly a month with inav 6 pre release, I am so thrilled that i have flashed my main planes with this nice piece of programming. Still there are occasions auto launch is not always successful (with smaller delta aircraft,) Really funny example here: th-cam.com/video/66tJLms3VEY/w-d-xo.html I want to combine auto level with extra up elevator for an easier start (and skip the autolaunch) Now I would like to learn how to program inav (logical variables etc) Can you point me in the right direction or help me out on how to do this
Hi Peter. You don’t need to add extra up with autolaunch. It will already be trying to achieve the launch angle specified in the settings. If its a smaller, lighter plane, reducing the detection parameters may help. Also if there is plenty of thrust, you could increase the launch angle. The old default of 18 degrees is very sedate. It’s mainly for flat launching planes like a mini talon. I’m sure the new default is 25 degrees. Glad you’re enjoying the 6.0 feature preview.
X-Plane integration is incredible! Thank you, all!
It is so useful. There’s more information here for anyone interested github.com/RomanLut/INAV-X-Plane-HITL
That Xplane shit is rad. Seriously one of the coolest things I have ever seen in this hobby.
It is really cool. It's great for trying things out, and can speed up development of new features.
@MrD, I'm not sure if this matters, but at 23 min, you started talking about ground course vs. heading. In full-scale aviation when I plan a flight, especially instrument flight, with approaches to get out of the clouds.
Before launch. Bearing is the direction we want to go. After launch, course is the degree to the waypoint. Heading is, as you know, the direction the nose faces in degrees relative to north. Bearing is the always updating degree to the waypoint. (Ground) track is the actual path over the earth. Heading vs. track is how I explain it when teaching instrument flying. I hope this helps.
So in relation to INAV, ground course is what you call track, and heading is still heading.. It's interesting to hear the full size terminology. Thanks for sharing 👍
Yes. Bearing is the path from point to point. Course, (future), is where you want to go. It is always a straight line. Heading, (current), is the direction your nose points with continuous correction for relative wind. Track, (past), is the path you have taken. Future, present, & past are milliseconds apart.
As always. Great work from yourself and the guys in the iNAV team.
Thanks James. Glad you’re enjoying INAV.
Fantastic update! Thank you very much for taking the time to explain some of the changes/new features.
Thanks Carl. I just wanted to let folks know that it is coming, and there are some great improvements in there. Glad you enjoyed the video.
Thanks for the update. Been using fp1 for while now with no issues. Look forward to full release, great work for you and all the devs.
Glad to hear you're having good results with FP1 Daryl 👍
Thanks!
Thank you Jim
great work
Thanks Ryan 👍🏻
Thanks for the INAV project progress update Darren. Lots of fantastic upgrades and new features!
The X-Plane integration wasn't something I was aware of and it appears might be useful for testing and simulation, perhaps even planning waypoint missions. BTW: Seeing X-Plane 12 is now listed.
Oh 100% waypoint missions work. Anything that you can do in INAV will work on the HITL. I’ve even seen Marc using autolaunch 🤣
I’m sure it has been used with X-Plane 12. But there were some issues. Roman’s repo for the integration plugin is here github.com/RomanLut/INAV-X-Plane-HITL There is a lot of useful information on that page.
great video and overview about what is going on and what to expect. Can not wait to see the horizont drift been gone - hopefully forever.
Still a great video as it has been last year too even though this one was not about a released. But gave me a quite full update about the progress and features coming .
thanks a lot - also to Marc for finding the secrets in the log.
The horizon has been very good through all the testing, so it's safe to say it's gone. Unless you have a very bad physical vibration.
Thanks so much for the update video .
You’re welcome Allen.
Impressive work. 💪 The large amount of improvements are well worth the waiting.
Wind estimator, ground course and cross track error, Glide time, glide distance, and climb efficiency and so on.
Walksnail implementation has convinced me to go that way because OSD is most helpful to fly FC wings. And I don't like hack's, compatibility questions and other restrictions. Thanks for all the new goodies.
It’s definitely going to be a milestone release. Hope you enjoy it 👍🏻
I fly the 6 fw quite a while with great succes
I hope dji will help us to get OSD support for the inav 6.0 on the 03 unit
There will be basic support for O3 in INAV 6.0. It will mimic the BetaFlight OSD, like how ArduPilot works with O3. However, there will be a lot of elements that will not display correctly. The only way for a proper, fully featured OSD is if DJI fully implemented MSP DisplayPort (it would be nice if they stopped calling it canvas too) and allowed pilots to upload fonts to the goggles. The only other way would be another hack, like the WTF DJI OSD for the last generation of goggles and airunits.
@@MrD and what do you mean by basic?
I have enough on direction distance and battery use
If it’s just that, you’ll be fine.
The rth way point tracking would have saved my quad last week.
It will be a very handy feature. It does have its limitations. But for the first up to 2km, it will definitely help. Of course, the RTH should still be set up for the flying environment. After that 2km (max), it will revert to a standard RTH.
@@MrD mine was less than 1 KM away. It just went behind a hill and tried to RTH when it got my control signal. I wasn't thinking about the hill being a problem. That was the test flight to try RTH. It was still set to drop as failsafe. Then we got 2 feet of snow. It is private land, so it isn't a big deal. I'll find it someday. I lost my brand new Upgrade Energy Dark Lithium pack and my Runcam 2 4k. I guess it was all new, but those were the expensive parts. And the Mamba stack.... hopefully someday I can recover and salvage something.
Ah, that sucks. I hope you find it. But, I don’t think the RTH trackback will work if failsafe is set to drop. I can ask. But I believe in that situation it would still drop.
@@MrD I am even more interested in that idea. Yes, failsafe should drop as intended. However if my RTH command were following the "track back" path, my command link should have been reestablished well enough fly in a different direction.
Thanks for the update.
Not gonna lie though, bummed about extra arming safety. I read the github log on it, feels like an unnecessary restriction on a genuinely helpful feature
You're welcome.
To be honest. I don't see any reason to have extra arming safety off for normal flying. I can only see it causing more problems than being useful. allow_bypass is still there, which should cover all bases where off would have been used previously. disabling the extra arming safety is only really supposed to be used for testing, or if you have a drone that you may occasionally fly indoors.
On the next update please make it easier to program wing with tail and flaps. I need seven channels in my airplane and two for my fpv how do I do that
This is pretty straightforward. You just setup an airplane mixer, then add the flaps to the mixer. This may help with the flaps setup th-cam.com/video/qY1TwINNX6c/w-d-xo.html
I don’t get what you mean by 7 channels for your airplane and 2 for FPV. I’m hurt you mean 7 for the full house glider setup. You don’t need 7 channels for that. The mixing is done in INAV. Only 2 channels for everything else seems like hardly any to be honest. I can think of at least 3 for the most basic setup. You at least need arm, modes, and tuning.
@@MrD will that work with the Spectrum ix12
Hi Darren, maybe you can give me a tip. I have a Ranger T1 with 2 engines. I use INAV 6 . Everything works fine except for the motors. One motor starts at 2% the other at 18%. What is the reason and is there anything I can set in INAV 6? Greetings Didi
March damn I was hoping for January. WP sound great I use my planes to take pictures of our crops. So the days of walking into corn fields are a thing of the past. Kinda wish we could save more WP but I make due. Can’t wait on 6.0.
So the other day I contacted you in regards of a current censor issue thought I had it fixed but no😢. No when I first plug in batt read 130amp then slowly drops down to 30amps and fluctuates for 18 to 30amps kinda strage. I’ve had problems with both h743 wing v1 fc that I have don’t like em at all. No pdb board now and still same problem I have a 470uf on esc one one battery lead that may be the issue cause I usually put cap on f/c on esc out maybe I got to many capacitors. Only have two on hole system. Only thing new to my set up is Maytek xt60 pdb w/voltage filter. Must be the cause of all this. Not big deal now cause still in testing. May be a problem when I start working this spring last year I used xuav cloud with 3.5 to 4 hour flights so u can understand why I need to figure this out. I mean technically I could stil fly with out amp meter but I like have all the info I can get in osd. Current set up maytek h743 wing v1 inav 5.1 Ps has to be that pcb voltage filter u know they slip over a xt 60 plug no wait I put them on other planes and no problems he’ll I don’t know I believe I got two bad f/c from Maytek no big deal have a good one and thanks again for all the help and videos
Hi Aaron. There are more cool things in the pipeline for waypoints too. There is the ability to add user actions to waypoints. In the INAV programming tab, you can use the user actions to trigger things to happen, like operating a PWM channel to start recording on a camera. The advantage of the user action over doing this using the waypoint index is that you can use the same user action on multiple waypoints, so only need the programming once. This wasn't in the video because it hasn't been merged yet. But it is very close now.
You can't have too many capacitors on power lines. All they will do is smooth it out. So I don't believe that's a problem. Though, you should only really need on on the ESC (not the ESC pads on the FC), to reduce noise from the ESC to the FC. I've not seen the XT60 with voltage filter before. If this is just a TVS diode, that won't cause a problem. It just protects the battery and other components from voltage spikes.
@@MrD so your saying that I’ll be able to drop a WP say when I want a picture and it will take the pic on its own I was gonna make that suggestion this summer but got busy and didn’t plus I wasn’t real familiar with WP at the time and wasn’t sure if was already available. And to be honest still not familiar with WP or had the time to explore all available options. What I did was use two crossfire receivers set WP mission and then operated the camera with second controller sure wish cross fire would come out with a sixteen channel receiver. Worked pretty good I think I needed six channels to run cam zoom,start stop vid,still pictures required a channel, pan and tilt was something else maybe menu very nice only thing I wish I had was gps position on pictures in dvr. Not sure if that is even possible. And continuous recording instead of 12 min files gets confusing after 6000 acres. Would like to have a more professional way to keep track of what field I’m in. But for now spray paint work great paint a big number on the road and problem fixed long as it’s asphalt and not gravel any way thanks man wish I could help out more maybe next year I don’t see things getting any better though they are predicting a 30% increase next year per acre from plant to harvest so moneys kinda tight
Hi Daren
I've just see the latest Painless 360 video about iNav 6.0.
Please don't telme the maiden video of lesson 8 of your iNav setup series, you ar going to up date to the iNav 6.0... I'd sugest to finich and at the hend, say the word!
OK?
Hi, Great video. How can I get IRC Ghost LQ and rssi dBm on OSD in INAV?
Great work and thanks to all involved. I do however have a problem with "Targets" and as I think you have modified a few you seem to be my only hope. I have a T-Motor Pacer F7 board and it will not connect to iNav 5 or 6, targets when both TMOTORF7 and TMOTORF7V2.targets are flashed. In Betaflight, sorry to mention it, a target exists for T-Motor pacer F7, TMPACERF7. I need iNav for its GPS functionality can you help or should I donate my board to the scrap bin and invest in a supported board.
BetaFlight targets are not the same as INAV targets. So you can’t flash a BetaFlight target and have it work in INAV.
The only T-Motor targets that exists in INAV is TMOTORF7 and TMOTORF7V2. For other targets to be supported, T-Motor would need to reach out and work with the INAV developers to get their targets added. There are policies for adding new targets to INAV github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md
@@MrD Thanks for that so quick well done! To summarise then unless T-motor asks for the targets to be written it's the "scrap bin" for my flight controller. Do you know of any developer who has an "unofficial" modified target that may work? if so I am prepared to risk it, waste some time, and try it out, if not, do you know of a charity that can use a brand new T-Motor Pacer F7 let me know and I will donate. meanwhile, keep up the good work. Regards John
Unfortunately not for that target. The best thing to do is contact T-motor. Unless they know there’s a demand. They have no impetus to make or commission a target.
Thanks for your further support. I have returned the board to Ali Express as I considered it is not fit for purpose. I should get a refund .
Regards and hanks John
I always find the AHI a bit distracting TBH, a ladder variant would be a Nightmare...If they've finally fixed it, I'll have it on an alternative OSD for in cloud flying ...Will it work with Walksnail HD yet?...😳😳🙄🙄🇬🇧
5.1 works with Walksnail. There are a couple of minor issues. But, these will be addressed. I’m hoping to have sorted a couple of things before 6.0 is released. Like the order for switching on the goggles and VTx, and the artefacting characters that you can get with packet loss. I’m currently building an AR Pro to test.
@@MrD Great, thanks for the information. It's going into a quad first off using BF and I know that works. I have a Ranger G2 with 1.2g video and CRSF but I'd like iNAV and WSnail on it this coming Summer...😳😏😏🇬🇧
Well, hopefully it all goes well in that week we call summer 🤣 I’m just starting a new quad build no. I’m tempted to get a WS VTx for it. However, I’ve noticed that Caddx have lowered the price now. So I may wait for the UK vendors to catch up. It should be about £129 for the micro set.
@@MrD Yes, I'm building a new 5 inch quad with the 19mm WS camera..I also recently got the WS Goggles too...Then I pre ordered the new VRX and another 19 mm camera and VTX. They have now shipped that and I'm waiting for it. I have a big 10 inch monitor with HDMI input for the VRX and FW flying...😳😏🇬🇧
Hi ! When the dolphin's Maiden video Will be released?
I'm waiting on my work schedule and the weather to play ball at the moment. The Dolphin is good to go.
Removing the NAV arm safety option is a bad call IMO. People using this sort of thing are doing it partially because they want control over how it all works. If we want a bunch of safety guard rails we can just buy a DJI. Please leave the user in control as much as possible.
Need a link to download 6.0 Configurator "Pretty PLEASE!!!"
Omg I'm so dumb. I thought the changes to HD zero where in the preview it had said something about keeping the elements in the center so I spent like a day moving them closer together flying closer flying and was doing it through the cli because speedybee doesn't work with 6.0 yet, ended up getting frustrated and ordered the walksnail vrx.
To be fair to Speedybee. It's not out properly for another 3 to 4 months. But I can see how that would get really frustrating, changing that in the CLI. How are you liking the FP other than that though Ruby?
Hi Darren, is the Feature Preview version available now safe to use in wings and planes? Thanks for what you do, much appreciated 🙂
Hi Stephen. The feature preview has been used for a while. And so far, there have only been a couple of minor bugs found. The main one off the top of my head is the incorrect ESC temperatures in the OSD. The flying aspect of it has been great. I would say it’s as safe as any release candidate. So if you’re happy with release candidates, you may like to try 6.0 out. Check the release notes though. There are some settings to update after you have restored your diff. Also, my tool I show in the video is not needed for the feature preview.
@@MrD Thanks Darren, much apreciated. I'm in process of loading it on a WingWing Z84 🙂 On a different subject is Konstantin still an active INAV developer ?
Konstantin is still about. But not very active. He has submitted 3 commits in the last year.
inav6 will be called the easter egg ?
No, it's called Horizon Hawk ;) ...seriously. Quite a fitting name :)
I’m adding a zoom able cam to one of my builds would it be possible in global functions to slow the pan servo down when cam is zoomed in. If not possible in inav . If not can I do programming in radio. Can u add mixing to a channel 5-12 could I program a mix I. Radio as long as it’s not AETR. I’m not exactly sure how to do it but I think I have an idea 19:49 19:53
The problem is the slow functions will only really add lag. I guess what you need is more resolution from the input (slider or head tracker). For this, you need the camera to move less for the same amount of movement of the input. You could do that in INAV using the programming tab to detect when the camera is zoomed in or not. Then in the mixer, for the pan mix, use the logic conditions to switch between 100% weight on the pan servo and 50% weight.
@@MrD I’ll try it out still need to get a base tune I’m adding all this to that rmrc anaconda this plane is awesome leading edge flaps wow. Super slow flyer be good for lost cattle and crop reviews. Anyway might be a few before I get it all worked out. I’ll let you know how it turns out thanks man
我想咨询下，什么时候发布正式的6.0版本
Around March for the stable release.
Development freeze is the 29th of January. So i would expect to see release candidate 1 in early February.
Almost as boring as a glider video. Well done, mate 👏
It would have been far more drowsy if I’d mentioned soaring mode.
@@MrD 🤣 I fell asleep at DJI OSD anyway, was 2:30 am
@@grumpyoldnerd8727 well I’m glad I helped you get some rest. You deserve it after all the effort you’ve been putting in to get the Mini Drak reborn.
What about a migration script to ardupilot as only inav 6 killer feature if you do not come up with o3 support?
Firstly, ArduPilot’s OSD is not supported by DJI 03. ArduPilot mimics BetaFlight’s OSD which is why 03 “works”. In reality it is a cut down OSD with lots of missing elements and bad symbol substitutes. It is not ideal at all.
There is a PR in INAV now, which also mimics the BetaFlight OSD. Again, this has hugely reduced functionality (even more so than ArduPilot, as INAV has more OSD features in the first place). You will see symbols not supported by BetaFlight as ?.
If you want a proper, fully supported OSD on any firmware other than BetaFlight. You need to complain to DJI. Get them to fully implement MSP DisplayPort (and stop calling it canvas, that is something else entirely), with pilot uploadable and selectable fonts. Without that, DJI will only ever be a hack on anything other than BetaFlight.
Vtol
Maybe in 7. Who knows.
Assume it’s being delayed for my 765-wse SD card fix 👍
Thanks Darren for your work. I do fly a month with inav 6 pre release, I am so thrilled that i have flashed my main planes with this nice piece of programming. Still there are occasions auto launch is not always successful (with smaller delta aircraft,) Really funny example here: th-cam.com/video/66tJLms3VEY/w-d-xo.html
I want to combine auto level with extra up elevator for an easier start (and skip the autolaunch)
Now I would like to learn how to program inav (logical variables etc)
Can you point me in the right direction or help me out on how to do this
Hi Peter. You don’t need to add extra up with autolaunch. It will already be trying to achieve the launch angle specified in the settings. If its a smaller, lighter plane, reducing the detection parameters may help. Also if there is plenty of thrust, you could increase the launch angle. The old default of 18 degrees is very sedate. It’s mainly for flat launching planes like a mini talon. I’m sure the new default is 25 degrees.
Glad you’re enjoying the 6.0 feature preview.