Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 04-Jan-2022, 07:31 PM (This post was last modified: 06-Aug-2022, 01:37 AM by SnowLeopardFPV. Edit Reason: Added "EDIT" line. ) EDIT (14th June 2022): Betaflight 4.3.0 is now a final release so links to the RC1-7 versions have now been removed. If any DJI FPV System users are running one of the Betaflight 4.3 releases and want Betaflight warnings in that version along with real Crossfire LQ values (instead of the RSSI workaround), someone has now released modified Betaflight 4.3.0 firmware to include those... Details of the official Betafight 4.3.0 release can be found in another thread HERE. EDIT: This functionality will be included natively in Betaflight 4.4 which will then negate the need to have to flash a custom modified build of Betaflight. Details are in post #13 of this thread. Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 JB posted the following video earlier today about the custom Betaflight firmware linked to in the first post and how to set it all up...
![[-]](https://intofpv.com/images/collapse.png) • Posts: 1 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Feb 2022 Reputation: 0 Hello,
whats about new Version Betaflight 4.3.0 RC3. I can not contact Howel. Please make a new Build with these awesome Patch. It is so great to finally see the data in the DJI glasses. • Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 I'm not sure if you saw the red warning note in the first post of this thread but there are still failsafe / disarm issues with Betaflight 4.3.0 RC3 so would advise caution with using any of the RC1-RC3 releases until those bugs have been fixed and tested. For Betaflight 4.2.x you can use mbilozub's solution at the link below (also demonstrated in JB's video at the bottom of this post). He didn't make a version for Betaflight 4.2.11 but 4.2.9 was working fine on my quads without ant issues so it should be good enough to use that slightly older version until the bugs in Betaflight 4.3.0 have been ironed out. https://github.com/mbilozub/fpv_custom_m...ight/4.2.9 • Posts: 2 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Feb 2022 Reputation: 0 Yes i read this Warnings. I tried this Version by mbilozub buts its different. I can see Warnings but I can not see Crossfire LQ & RSSI. Did I misunderstand something? • Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (21-Feb-2022, 11:13 AM)Alveran81 Wrote: Yes i read this Warnings. I tried this Version by mbilozub buts its different. I can see Warnings but I can not see Crossfire LQ & RSSI. Did I misunderstand something? With Betaflight 4.2.x you will need to use the method detailed in the video below to get Crossfire LQ values into the OSD of your DJI FPV Goggles. With that method the OSD element symbol in the goggles will be for RSSI but the value against it will actually be LQ and not RSSI. The value will show as a number from 0-100 rather than "RFMD:LQ" so you don't get to see the individual RFMD, LQ, or dBm values. That number remains at 100 until the RF Mode (RFMD) is at 1 which is the lowest refresh/packet rate, then the number will start to drop as Link Quality (LQ) drops off. If you are using TBS Crossfire with dynamic RF Mode enabled then 80 is the warning number you need to start taking notice of and 70 is the number where you need to turn around at and start heading back unless you want to risk a failsafe. • Posts: 2 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Feb 2022 Reputation: 0 Yes i know this way. I have it at all my copters. Its not nice but it works. But please Howel please do all new Builds of Betaflight 4.3 Like in poste Nr 1. This is realy cool.
Sorry for my English. • Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The only way is to keep hassling the Betaflight Devs to implement Crossfire LQ and Warnings functionality into Betaflight for the DJI FPV System.
If we have to keep relying on a forked custom build of Betaflight from a sole individual then it's going to be no good in the long term because he could decide to stop providing that at any time just like mbilozub seems to have done, and it's not fair you keep on hassling either of them for updated versions because they likely have a day job to do and a family to spend time with.
LQ and Warning functionality for the DJI FPV System needs to be baked into the main Betaflight firmware so it is properly supported and maintained by more that just a single developer. We all know that DJI have now abandoned the FPV System and will never provide any new firmware with feature updates in which means they are never going to implement Canvas Mode. The only real and permanent solution to this IMO is for the Betaflight devs to accept the situation and to allow mbilozub or howel's solution to be merged into the main Betaflight source code so that all DJI FPV System users can benefit without having to jump through hoops with the installation of custom firmware from an unofficial source. Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The new team of devs who are heading up the Betaflight 4.3 & 4.4 releases seem to be a bit more relaxed about workarounds being added to Betaflight and as a result they have now accepted howels pull request which gives the ability to utiise the craft name OSD element to add warnings and LQ values into the DJI goggles using a native Betaflight build rather than having to flash modified code from a separate a fork  Details are in the pull request below. The functionality is currently available in the nighty development builds for Betaflight 4.4 and will be released to the public as part of Betaflight 4.4. https://github.com/betaflight/betaflight/pull/11771 Posts: 4,550 Threads: 38 Likes Received: 1,245 in 1,064 posts Likes Given: 430 Joined: Aug 2020 Reputation: 118 06-Aug-2022, 02:41 AM (This post was last modified: 06-Aug-2022, 02:41 AM by kafie1980.) No idea why some devs put on this arrogance about not providing a feature to the user community. I mean its not like craft name affects flight performance And its not like an ethical issue • Posts: 7 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 1 Joined: Aug 2022 Reputation: 0 Hi guys,
I have installed the latest 4.3.0 version on two different quads and in both cases the LQ and DBM figures disappear as soon as the quad gets about 5 or 600' out. When I fly back towards me the figures come back once I get quite close in. I'm running the latest firmware of Express LRS at 915 mhz and 100hz refresh rate.
Has anyone heard or experienced this happening and if there might be a work around?
I was hoping that Howels would come out with a 4.3.1 version to try it appears he has a version that has to be compiled, I have no experience doing that and don't want to risk a quad on something that I don't have a knowlege doing. • Posts: 4,550 Threads: 38 Likes Received: 1,245 in 1,064 posts Likes Given: 430 Joined: Aug 2020 Reputation: 118 What ELRS receiver are you using?
You are probably loosing telemetry at that range.
Not all ELRS receivers are technically designed equally in that some don’t have a Power Amplifier (PA) that helps extend telemetry range. And there are different telemetry output powers of various receivers based on the PA onboard. • Posts: 1,505 Threads: 49 Likes Received: 713 in 524 posts Likes Given: 477 Joined: Oct 2020 Reputation: 93 (06-Aug-2022, 05:14 AM)kessellc Wrote: Hi guys,
I have installed the latest 4.3.0 version on two different quads and in both cases the LQ and DBM figures disappear as soon as the quad gets about 5 or 600' out. When I fly back towards me the figures come back once I get quite close in. I'm running the latest firmware of Express LRS at 915 mhz and 100hz refresh rate.
Has anyone heard or experienced this happening and if there might be a work around?
I was hoping that Howels would come out with a 4.3.1 version to try it appears he has a version that has to be compiled, I have no experience doing that and don't want to risk a quad on something that I don't have a knowlege doing. You can flash the latest nightly in Betaflight to get the hack now, no compiling necessary. Just go to Update Firmware in Betaflight, tick the Expert Mode box, select Development, then select your board. What hardware do you have? It does sound like you're losing telemetry, but at 915MHz even the lowest output receiver should be able to cover a few km. Have you done a bench test? What do you see for 1RSS and TRSS? • Posts: 21,189 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (06-Aug-2022, 02:41 AM)kafie1980 Wrote: No idea why some devs put on this arrogance about not providing a feature to the user community.
I mean its not like craft name affects flight performance
And its not like an ethical issue I think the previous set of Betaflight GitHub approvers might have been a bit old school and set in their ways unfortunately. INAV and Emuflight implemented workarounds almost since day one of the DJI FPV System being released and it was only the Betaflight devs who stuck their neck out and blocked any such functionality being added to Betaflight. Looking at the profiles of the newly appointed Betaflight approvers, some of them seem a bit younger so are likely more open-minded which is a good thing. There are promises of lots of new and exciting features in upcoming Betaflight releases, something that the original approvers might never have allowed. • Posts: 7 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 1 Joined: Aug 2022 Reputation: 0 06-Aug-2022, 07:41 PM (This post was last modified: 06-Aug-2022, 07:41 PM by kessellc.) (06-Aug-2022, 05:47 AM)kafie1980 Wrote: What ELRS receiver are you using?
You are probably loosing telemetry at that range.
Not all ELRS receivers are technically designed equally in that some don’t have a Power Amplifier (PA) that helps extend telemetry range. And there are different telemetry output powers of various receivers based on the PA onboard. I have telemetry out to as far as I want to fly which in the case of my 7" which has a R9 slim diversity RX flashed to the latest 3.0 version, I recently went out 1.44 miles and had everything on screen. The only telemetry I'm loosing is the Mods. • |
