Volantex Ranger 1600 or 2000. I don'r remember which wings I used because I have both. I think it I was using the 1600 wings.

I didn't have this issue until now.

Ardu is great for many thins and I have used it before, but there are two things that I just can't accept from Ardupilot: 1) The configirator interface from 2003 2) The limited flight modes So, when Ardupilot changes that, I would be happy to go back to it, but until then INAV rules!

Very interesting, this is quite an achievement! I'm not sure why but my experience with the iFlight patch antennas is just horrible, to say the least! If I want to go really long range, I use the TrueRC X-AIR MK2 or the Maple Wireless Mjolnir Pro. Mjolnir Pro are obviously more compact, but the reception I have with them is very good. I will be doing a new video of a range test with Goggles V2 and Goggles 2 with the O3 Air Unit very soon! Stay tuned!

I achieved that range on a 21km out and back autonomous mission. I'm using crossfire with 1w on 868mhz so no interference with the 5,8ghz video. The FCC hack also helps. I definitely recommend holding a sufficient altitude so that the signal doesn't bounce back and causes interference 300m should be good. Also check that your patch antennas are connected to the bottom sma connectors (V2 Googles). What also helps is putting the antenna the furthest away from your receiver antenna and any cables etc. With this I was easily able to achieve 11km with 15mbs. For a fair range test id recommend flying an autonomous mission out 20km or so so the two results are comparable. I'm really looking forward to that comparison tho. :)

@@deruhu9163 Excellent ideas! Thank you very much for that! Will take them on board when I make a proper plan for the video. :))

Regarding the flight stats: The goggles stop the recording very quickly after you disarm and the end screen does not show. I have the same issues. The only way is to start the recording before you arm and then it will continue recording after you disarm. It works on the Vista running the O3-compatible firmware, not sure if it will work for an O3, I have to try this. Regarding the icon: I'm not sure what you mean. Form what I understand, you don't see the characters in flight, but then you do see them in the recording? Is that correct? maybe you can try to explain it again or upload a video.

@@DZARO I only see the numbers but not the unit appear, neither in flight nor in the recording, I having this issue only with the Wh/Km icon. It's a shame not to be able to record the stats because it's very useful for comparing different configurations.😃 EDIT: I have a second issue with the power (W) the value not always match the power, I guess when the power exceeds 100W the problem appear. I have published a video here: kzfaq.info/get/bejne/nNabrbR9ma2VmYE.html

OK, so I looked into this and here is a detailed explanation: The [mAh/km] is made up of two symbols: *SYM_MAH_KM_0* and *SYM_MAH_KM_1* These have been substituted with the following: *[mAh]* symbol and the letter [E], standing for efficiency. It is up to the user to know that the units symbolise "mAh of Efficiency". In case of the [Wh/km], there is only one part to the symbol: *SYM_WH_KM* This means that it can only be substituted with one character, not two. I have left this one as blank because there is no adequate way to symbolise "Wh of Efficiency" My suggestion to you is to use [mAh/km] as the efficinecy units, so that you don't have blank spaces. I know the solution is not perfect, but there is no alternative at the moment. If you look at the following image below, you'll see that the [mAh/km] is made of two characters and the [Wh/km] is made of only one. The rest of the code is based on how these are being used and combined. github.com/iNavFlight/inav-configurator/blob/master/resources/osd/analogue/default.png?raw=true

I understand it is a software limitation, not a bug. Thank you! Have you seen my video with the W unit which disappear when I guess exceeds 100W? Maybe the same software limitation?

You need a USB to UART module to set the baud rate fo the BLE module first and then pick the same baud rate in the radio.

@@DZARO what is a BLE baud rate?

It must be, but I jave not worked on this modification yet.

Angle mode does not allow your plane to pitch or roll more than a predefined angle. This means that you can't do a full 360 degrees turn on these axees and the calculation for the rates and the feed forwards will not yeild the correct result (at least from my experience).

Would love to but I'm not a coder. It would take me a considerable amount of time to learn this. But maybe, maybe in the future, you never know . . .

@@DZARO I understand, but you have the right mindset. Thank you! Hope this gets merged!

Sadly, this is not possible at the moment.

Thank you 🙌

@@DZARO Can you please add Matek 765SE ??

Added, check the Google Drive Firmware folder!

​@@DZAROthanks!!

Thanks!

Motor, prop and ESC are same as in the PNP version, just stock. FC is MATEKF405TE. Air unit is standard Caddx Vista with original DJI camera. Battery is Tattu 2200mAh 3S. (The battery was a 4S, but one cell died and I made it into a 3S hahaha)

@@DZARO Thanks a lot 👍

How much do you want to bet that it will not be merged?

You can just put the "altitude" symbol on everything and achieve essentially the same result. They won't be labeled with a question mark, they be labeled "altitude" instead.

@@senseisecurityschool9337 Yeah, but I chose icons that make sense to a cetain degree. Ofc it's not perfect, but it's acceptable give what the alternative is.

@@DZARO You chose icons that mean something else. You choose "K" for distance in METERS. THen when we told you that you made the change in the wrong file and you should move your changes to the appropriate place, and that M would better than K, you started slandering us.

@@senseisecurityschool9337 And what is written in this PR is not slander of DJI for example: github.com/iNavFlight/inav/pull/10046 🤣

Thanks 😁

Only one font availabe, DJI's font. You can't change this sadly.

Danke fuer die lieben Worte :)

It's already there. Check the name of your target in your diff. I think it should be ATOMRCF405NAVI. This FC's HEX is in the firmware folder.

@@DZARO hmm I see it but getting - Could not Download ... HTTP Error. I still can download others

@@techlock5406 What about this link? drive.google.com/file/d/1E1ZRply8qfYlU6yGjcc7lGDFifvWclPu/view?usp=drive_link

@@DZARO this one works just fine. Thanks!

@@techlock5406 I might be making a few more little changes and updates this weekend, just want to get it perfect.

No, you can use the WTF.OS hack.

Can this be used without WTF.OS? For example: 03 Air Unit and Googles 2 or later on INAV.

@@johnrobert6378 That is the purpose of the whole thing. It's because there is no WTF.OS for Goggles 2 that this workaround was created.

Oh, great! Would it be possible to post a set of instructions on how to make this change. I’m familiar with INAV but not that familiar. Thank you!

@@johnrobert6378 hi, DZARO also did the tutorial for this purpose, it is very easy to do: kzfaq.info/get/bejne/Y7xzla6Ks8yUhnU.html

Versuch's, sollte klappen. An sonsten, Discord!

Let me know how it goes and what you think of it after you give it a try!

@@DZARO Will do!

Just do a "diff all" before you flash, save your file and you can keep all your settings. Follow the steps as shown in the video and everything will work fine.

I will try this. Thanks

@@DZARO I tested this special version, no more question marks on the OSD, This is a great improvement for the FPV community. Thank you so much!

@@sebseb-cw6bl I'm glad you like it !

Yeah, but guess what: I unplugged the battery, bent back the prop, plugged the battery back in and it armed and flew fine. WHAT THE ACTUAL F*** HAPPEND ONLY LORD KNOWS!

You are correct, I have forgotten to add that to the video. Here is is: github.com/iNavFlight/inav/blob/master/docs/Settings.md#osd_msp_displayport_fullframe_interval

@@DZARO Thank You 🙂

@@stevietee10 No problem at all. I changed the value to 5, just FYI.

On the first point: I've been trying to argue that same point with the INAV devs. They want to keep the '?' to remove ambiguity, but in fact is has the polar oposite effect because now you are just looking at abunch of '?' and you are even more puzzled. Their idea behind keeping the '?' is to show that the system is actually only partially compatible. FYI, have a look at my latest build of the firmware binaries from the 7.1.1 Google Drive folder. You'll find some interesting things, such as multiple crosshairs available. On the second point: I don't know if that is possible and how someone might go about it. Maybe the WTF.OS team are already working on this, who knows. If they manage to get a crack for the O3 AU, they might even crack the Goggles 2. But is that really necessary? Should we, the users, have to go through that trouble? The point is that DJI should have done a proper implementation of canvas mode and they should have implemented at least three tables of symbols/icons, one for Betaflight, one for INAV and one for Ardupilot! That would be the correct approach in my opinion.

@@DZARO yea I've seen your other comments, it really sounds like they're keeping it like that just to spite DJI. Which is incredibly annoying. I spoke with the wtf developers on discord, they say the V2 goggles are fully unlocked and the air unit doesn't need to be unlocked because it is already sending the msp stream anyways. So it would just need someone to write some code to implement a different font set and enable the recording on the v2. Then you can use the existing wtf modules to load the code onto the goggles. I would do it, they even offered some support for loading it onto the goggles, but unfortunately it's too hard for me with my limited coding knowledge. And they will not do this, most have moved on to other projects. Of course it's on dji to fix this, but they don't care and so it's probably never gonna happen:/ it's just frustrating to know that it's so close and it could be so great but it's just out of reach.

Come to Discord and we'll sort it out together. discord.com/channels/1082026163746115645/1082027032390672405

We had problems with a buddy this week, couldn't flash, no idea why. He went home, tried it on his own PC, and it worked straight away.

Have a look at this: kzfaq.info/get/bejne/Y7xzla6Ks8yUhnU.html

@@DZARO Thank you for thinking of me.👌👍👍👍😀

As mentioned, join my discord link so that we can talk and I'll talk you through it step by step. Sharing screen would also help.

@@DZARO ok lets try, Do you have the link again please?! the other one doesn't work somehow

@@sandro9389 discord.gg/TmRJwSc7

Glad to hear it! Have a look at the latest builds in the 7.1.1 Google drive folder. I added a few things such as multiple crosshairs.

Man, I tried everything. I'm not giving up yet, but it didn't lead anywhere because they didn't want to accept it. And I get it, it's not that it's their fault. At the end of the day, it is DJI's fault. But they could just accept the couple of changes that I proposed and just let everyone get on with their business. They blame me for making it "political", but at the end of the day, they added those annoying questionmarks, not me. I'm just the loudest voice at the moment challening their decisions. None of us (DJI O3 and Goggles 2 users) agree with their reasoning, but's ok. In time, everything will get resolved one way or the other.

@@DZARO Sadly, it's not a "new" fight. It has been going on for more than a year. Check Inav's PR numbers 8926, 8928 and 9389, which were made by me. Read the discussion in them. They were met with the same fierce resistance and hostility that you were met with. You are probably the fourth or fifth person to try to improve the O3 OSD and face this non-sensical gatekeeping, and it's always by the same people. It really is sad and lamentable. I run my own custom version with almost all OSD elements fixed, there are no ambiguities and no question marks at all in my OSD. It has all been replaced by a combination of the available icons and letters. This shows it's possible to have a fully working O3 OSD with Inav. It just required some changes to the osd.c file code that, although simple and well organized, would never get past the current gatekeeping standards. Really unfortunate for the whole Inav community.

@@Rmaia3d Today I was wondering why the up and down sidebar scrolling arrows were missing. Surprisingly it was a simple mistake that someone made in the naming of the defines. In once case they used DECORATION, in the other DIRECTION. Ambiguity can be removed, but they do have a point that DJI has done a piss-poor job of implementing any sort of reasonable font. I pointed this out to Mosca, but he completey ignored the fact that the bf_osd_symbols.h, bcause neither of the BF fonts actually match what is used by DJI. DJI just did a mix-and-match of whatever they wanted, which is also stupid. When I shared this with Darren, he made a table comparing the DJI fornt set with the other two font sets that are used by BF. I made some changes to that table so here is the link: docs.google.com/spreadsheets/d/1QnSLL68rN3doS0G9fcQBSaIkM589n1OF/edit I made the image below the DJI heading and it's a combination of BF1 and BF2. This would be a PNG of what DJI is actually using. I don't support their perspective, but DJI has screwed us over with this garbage font from over 5 years ago for sure, so it's not fair to blame the INAV devs for that. What I would say is thay they should rename the whole thing to DJICOMPAT mode and just mention in the release that this is just a workaround and that not everything is perfect. Because all that DJI did was to extend the OSD to a wider 16:9 canvas. The font is still the same one used by the V1 and V2 goggles. I would love to see how you implemented the efficiency symbol! Could you share a link to your fork?

You have two options: 1. Use the INAV-FWG's (Fixed Wing Group's) Model for OpenTX or EdgeTX. I have not used this model because I make my own models for each type of airplane that I'm flying. 2. Use one of my EdgeTX models which has this programmed in a slightly better way. I will be doing a tutrial on how I set this up as well as how it is to be used in the near future.

@@DZARO owh great will waiting for those setting thanks in advance 😁

@@DZARO I’d be interested in a video about your EdgeTX model for in-flight PID tuning as well!

@@brubakerjm No problem, I'll make a video onn this very soon! Stay tuned!

Yup !

There are some other settings you might be able to change instead of this one. In my case I cound out that the baro doesn't drift as much as the pressure inside the Volantex Ranger fuselage changes at different speeds. This is because the Ranger has two holes in the front for cooling, so the pressure builds up at a greater speed and there is no place to vent it.

I can't understand how developers of an open project have such a closed mind. It's not fair to close your PR. They are unable to see the big picture, too much testosterone and too little intelligence. my two cents.

@@moriwaky And now they restricted my comments on the PD as well hahahahahaha

Nope, I have no idea. It was not a disarm, I have no idea what it was. When I re-plugged the battery at home, everything was working fine.

ESC dsync?

@@arpan.sarkar Yeah, but the OSD froze and then went away as well so that might not be the cause.

Absolutely, my last PID tune was excellent. I had no nasty surprises at all!

Yep! There is a small "A" added in front of the regular symbol. You can see it when I take off using auto-launch.

What do I do with this HEX file now? How do I use it?

​@@DZARO perfect!! Thanks again

@@sandro9389 You just flash your FC with that hex file. In the bottom corner on the firmware flashing page you have an icon called "Load firmware [local]". Just pick the HEX file and press flash. Obviously, you need to be in DFU mode.

@@DZARO Thank you. That's exactly how I did it. The FC is also flashed with the official INAV 7.1.1 but when I select your hex it doesn't do anything. It just says: "USB device successfully closed" 😃 Do you have another tip for me?

This is the Heewing T2 Cruza! It's an excellent model!

I agree with you 100% !