This re-upload corrects a mistake in the flashing process. At 5:10 in this video, you DO need to select the correct target in the pulldown menu before flashing the generic target hex file that you downloaded. The original video left this step out. Thanks to the folks who pointed out that I got this wrong.
You don’t technically have to select the target, but selecting it saves you the hassle of applying the unified target config in CLI. That’s what apply custom defaults does I think
After switching to DJI goggles, I crashed twice due to low battery, and was used to have the alert message in my (analog) goggles. Thank's Josh ! You saved my life again
As always, a great episode, and as always, everything is presented in a form that does not allow me to even make a mistake. Thanks, "I learned (again) something today" from you :) ..and I would like to add that I really appreciate the lack of ads during the movie, until they are still not there, as usual, I will play the first ones so that they can be played to the end , keep it up, others should learn from you how to create and manage their channels on youtube :)
Thank you, the how to man! Have not had warnings since DJI came out and have not missed it. But love this hobby cause there always someone there to help others.
So after re-upload, I have to point out again, that the Warning OSD element is not in the MSP data stream, thus DJI had no access to it. They asked for it, and the Betaflight devs refused to add it to MSP stream. BF devs told DJI to implement Displayport instead. Your response to my previous comment was also (paraphrased) "they should implement Displayport like Shark Byte [just] did". Problem is, Displayport is still not documented, is much more complex to implement and until the very latest BF firmware, didn't actually work (which Carl @ Divimath had to find out the hard way). In other words, at the time BF told DJI to do it that way, it wouldn't have worked. And even if they did it today, it only works with latest version of Betaflight, and it's incompatible with iNav, and with all other flight controllers that have implemented the much simpler MSP protocol to talk to DJI's OSD (Pitlab, SN-L, SN-Navi, and the Mavlink -> MSP converter that can work with any other FC that outputs Mavlink stream). If the MSP stream can't be changed, then re-purposing the craft name really seems like the simplest, and most widely compatible method to address the problem.
When etracer updated Displayport_MSP he said DJI had been lazy and not done what was needed. But then if Displayport_MSP was working fine why did it need updating and then suddenly become functional for Sharkbyte to use? Is it possible DJI simply couldn't do anything with Displayport_MSP in a broken state? In which case why did etracer accuse them of being lazy? Also this means that DJI could come through and fix the OSD now we can see Displayport_MSP works properly hence Sharkbyte's implementation. etracer did say DJI had been informed of this change so maybe we will see another firmware.
@@changeagent228 Regardless of the changes that etracer made for displayPort, we all know full well that DJI are never going to implement displayPort into their goggles and let other 3rd party software have control over writing to their interface, and any firmware changes like that are even less likely to happen now that DJI appear to have lost interest in the standalone FPV system and have re-focused all their efforts on the new FPV Drone. As much as I respect the Betaflight devs for what they do for our community, by pulling the "out of principal" card they are just punishing their user base and creating unnecessary resentment. The INAV and EmuFlight devs had no problem accepting similar implementations into those projects which has hugely benefited their user base. It's such a waste of time and effort for mbilozub to have to maintain a separate repository for the modified Betaflight firmware just so that users can have this much needed and requested functionality, and an unnecessary hassle for users to have to go through those additional steps in JB's video in order to get the functionality they want. The PR containing this functionality should just be accepted into Betaflight like it has into INAV and EmuFlight.
@@snowleopardfpv I live in hope lol. Ferdinand Wolf, DJI's creative director said in a recent interview that they had plans to continue supporting updates to the Air unit FPV system which included but were not limited to adding support for the motion and v2 controller. I see no reason why they can't add a protection routine that prevents Displayport_MSP from accessing anything beyond the OSD overlay if they are that worried. I accept that there is still a chance DJI have given up on us though. That said I agree that the Betaflight devs should work with the Craft_Name hack so folks can get on and use the OSD features in the meantime like iNav and Emuflight have done. Indeed it should not be necessary for mbilozub to maintain a separate repository.
@@changeagent228 I heard what Ferdinand Wolf said but I don't believe him. He also said that DJI had plans to make the Motion Controller work with the Air Units but that is BS IMO. They haven't even come up with an activation fix for the V2 goggles 6 weeks after all the issues began, and they have now taken down the rollback firmware which was the only workaround unless you also happened to own their FPV Drone. I really hope I'm wrong but I think DJI are now done with any further development and support of the standalone FPV system and have moved on. I'll be surprised if we see any more firmware updates TBH. They very likely made more money on sales of their new FPV Drone in the first few weeks than they made on all of the standalone FPV hardware they sold in the last 18 months, and they lose interest fast in anything that doesn't make them much money. I believe the only reason that DJI made an 11th hour decision to hand over continued manufacturing of the Vista (and maybe Air Units) to Caddx was to quash some of the backlash and to buy a bit of time until things subsided. When DJI decide it's no longer worth their time and money to continue producing the custom ASICs needed for the Vista and Air Unit it will then be game over, and even Caddx won't be able to do anything about that. I do own DJI gear for the standalone FPV system but I'm beginning to regret having given any of my money to DJI.
If the devs won't implement a simple workaround which a major portion of the users actually need, then Betaflight has run it's course and it's time to fork it.
I remember that 2 years ago Betaflight devs wanted to add features like DJI support as pluggable modules or sort of like that. Seems it is time to release that thing already.
I just became crazy in the last 2 hours seeing the post in my Feedly but not being able to watch it 😂😂😂 thank you as always Joshua I learned something really useful today! 👍 keep the good work going!
Max, thank you so much for the work around. I am struggling to get the warnings to display in the DJI Goggles. I have followed the video step by step and tried it a few times. I am running BF 4.2.8. Do you have any idea what could be wrong? Thanks
The iNav version is officially supported and also has lots of other features like mAh/KM, 3D speed and throttle that can be enabled by adding WDTSE in the craft name field. I asked etracer about adding it into Betaflight but instead he updated Displayport_MSP and insisted it is up to DJI to fix it not the Betaflight devs hence the unofficial hex modification by mbilozub. mbilozub's version only includes warnings but I have asked if it's possible to integrate the iNav functionality at some point.
Question - I bought a ready to fly Roma F5 with the DJI AU installed. If I do anything within Betaflight to the quad, does it overwrite anyone that has already been programmed by RDQ?
I had noticed that if you plug the battery in before connecting to BF It will work with usb plugged in. The same thing happened with the Mag BF would always pick up the Mag if I plugged in the battery before connecting. It was hit or miss if already in BF when connecting.
Not sure what I'm doing wrong. I switch FCs and I can't get my V2s to work. I followed this video step for step...and nothing. I'm sure it's something super basic that I missed or something I didn't-know-I-didn't-know......Is there a button/switch that I need to check to get this to work?
Hello Joshua! Im very new to the hobby but I would really like these warnings on my goggles. I tried flashing but it fails every time. I unplug everything and plug it back in and everything is just as it was. Any step I am missing? I downloaded the hex file, copied the diff, matched the board name and target version (I think). but no luck. Thanks!
It works but I found it to be a little glitchy, sometimes the warning don't come up( like if leaving the throttle up a little when arming) ? I unplugged my gps and it said failsafe but would let me arm it? then when I unplug my battery and plug it back it in it would work better, the throttle warning would work and then it would say gps and it wouldn't let me arm? still better than nothing...
@@JoshuaBardwell ahh. Thanks for the prompt reply. I've watched a ton of your videos. Super helpful on every topic. I give every single one a thumbs up. I got a dji fpv a few weeks back. Had a small wreck broke both the front arms. Super weak plastic. Bought a nazgul 5fd that same night. Have been learning from you ever since! Thank you kindly. You do a terrific job and are truely funny.
Not work with omnibus f4. Betaflight 4.1 target 4.1. Elements appears in osd like warning battery and throttle. But when you want to arm, always appear throttle and don't arm. Also before i done the diff all and so on... So finally I go back to the normal configuration and it arm... Maybe a bug?
I am running into the same issue where my osd isn't showing up, I have it on uart3, and MSP is turned on, on uart3, osd display is turned on in configuration tab, display tab on, and I made sure TX to RX and RX to TX, in the googles I have custom osd turned on. Am I missing something? I am getting an error message saying low power mode, unable to record. I found out I can turn off auto temp control, but even when I do that, the error goes away but the osd doesn’t come up.
I get the message "hex file is corrupted" when I try to flash this to my iflight Titan with Succex F7 TwinG flight controller. Its the STM32F7X2 processor. Anyone who knows a fix for this? I have opened an issue on github. Thanks!
I need help, I have assembled a drone with the AIRUNIT and everything is fine, except that I cannot show the drone's battery charge, GPS data, etc. on the screen, of course, in the glasses it is configured as CUSTOM OSD: ON Help
Hey Joshua thanks for all your contributions to the hobby you’re my go to guy!! Question : should I power my DJI goggles without the antennas???? I have heard that it won’t cause damage. I’m wondering if it’s better to power them on with antennas? Could it cause any damage ?
I am driving an hour west to meet someone i met in the DJI Digital FPV users group. She has the DJI FPV drone. I have a question before I make this trip. I have attempted to update and also downgrade the firmware with my Apple home computer I’ve also tried with a Windows computer. It makes it through the first part of the update then when it gets to the next part the numbers stays at zero then the update fails giving me a DJI V2 update failed. 5-100-4 upload error log. I had Tace Day Quads walk me through the process to no avail. My question is is there’s something wrong on my end like with my computer or with the goggles? Is this consistent with the activation problems others are having?
@@JoshuaBardwell I GOT IT !!!!!!!!!!!!!!!!! I got them fixed!!!!! Thanks for your help !!!! #1 I had to use a windows computer. #2 I did not use the supplied DJI usb to C cable. Not sure if it’s for data. #3 my goggles were already activated!!!!! I never completed the activation process I don’t know how they got activated. Maybe they came that way???? I do not know regardless they work thank you for all your help.
Hey guys I’m having a problem with my dji air unit... I’ve flown it 100+ flights and out of nowhere it stoped binding to the controller/goggles. It’s in bind mode (flashing blue w/ steady red light) and I’ve tried multiple times to bind it. Just tried to plug it into my computer and it keeps disconnecting and connecting every 5 seconds or so. Cable is good. Pls help :(
thanks again for another great lesson, i couldnt get my settings back on the fc after i reflashed tho :X kinda a bummer any idea how to not have this happen if i do it on my 5innch quad?
@@JoshuaBardwell done,, on the 5inch all settings the same, thanks again bro... i wasnt kidding about you makin a shirttt with "YOU GONNA LEARN SOMETHIN TODAY" and ur face or ur quad or even ur signature logo, this was a quick idea . id rock it, i know many others would love to have it also u a true g thanks for the loyal wisdom we love u.
is there a hex i can add to my radix v2 ? i believe these warnings are a critical part of the osd information. next critical piece of the dji goggle puzzle is that it would be really really nice if we were able to have DVR that includes BF / INAV OSD information without having to log telemetry and go to a computer and overlay the info onto a video , surely in 2021 one day we can just record the full custom osd ??
A bit unusual, but I use craft_name as a way to put a serial number for my insurance, which is mandatory. Is the original craft_name put back after a warning is given?
Is it true there is a bug with using this patch. I seen somewhere it stating this can cause your quad to not be able to disarm and failsafe issues. Is this true? I'm currently on 4.2.8 dji warn patch on Couple my quads.
Joshua i lost my dji osd after swapping fc from bf fc to kiss fc.. literally the dji uarts now dead. after done wiring i get my full dji osd with kiss fc.. but then after i want to go fly the osd is gone and no voltage reading from dji airunkt uart. Like i said everything is fine before, no wrong wiring etc..i already switch to different serial (1 and 3 on kiss v2 board) and no osd. Both serial are working fine with my gps (so no broken/loose connectors). i ask alex fedorov about can kiss fw kills dji uart? He said it will never kills uarts. But as i did some searchig many kiss/fettec user losses their osd and voltage and this means dji uarts reading getting screwed up.. and even switch back to other bf fc wont bring back the dji osd and voltage.. can you do a research about this.. i cant find ppl having this problem with betaflight/flightone board. Only kiss/fettec users do. Thanks
I been wondering why BF won't do this since my iNav plane does. It's nice others can fork it and implement this. But honestly seems ridiculous that you need to since the other open source FC firmwares have already adopted it. Maybe it's time to fly emu on all my quads. BF dev push back on a feature was the whole reason butterflight started.
I'm thinking the same thing. I'm planning on flashing Emu on one or two of my quads to check it out. If all goes well, I'll convert them all to Emu. I understand that the firmware is donated to the community free of charge, and alot of work goes into it. But the childish crap about not adding in a feature, or features, that would greatly benefit the whole BF community, just because you don't like a certain company, kinda irks me. I'd rather support devs that care more about the quality & usability of their firmware, than ones that don't because of personal feelings.
Interesting, when I accidentially flashed my Rekon 5 with the standard target instead of the HGLRC I did brick my flightcontroller. The flightcotroller did work with sporadic crashes, but was nolonger flshable due to USB errors ( And I tried everything ZADIG, immersion RC ...)
Hi Joshua, Thank you for all the great tutorials! All the FC,s I am flying have STM32H743 as the target but I cannot find a firmware for this target. Do you have any Idea if one will be available or if there is any other way I can make it work? Thank you
JB need some help here. Just tried this on baby croc HD that was on 4.2.4. Tried both 4.2.8 and 4.2.9 on my STM32F7X2 but uarts 1 and 2 are missing, System beeps for motor checks are not there. Also if I enable OSD in Betaflight I can't get back into Betaflight unless I DFU and start all over again. Drove is dead in the water. Any suggestions would be great
I have been trying this for an hour and a half. No matter what I do, Betaflight gives a message of "Hex file appears to be corrupted" and refuses to load the betaflight_4.2.8_STM32F745_norevision.hex file. I have tried the 4.2.1, 4.2.0 and 4.3.0 files and deleted Betaflight Configurator and reinstalled the latest version. No luck. Too bad, I'd love to have the warnings.
I’m sure my opinion would be different had I experienced a DJI video feed. But, I am so tired of hearing about DJI! Just keep doing what you do. I’ll get over it!
Hey Joshua, is there any way to record the Betaflight OSD with the V2 Goggles? My problem is to find the quad with the GPS location that is shown while flying, but if you want to rewatch the recording on the SD-card, there is only the DJI OSD.
No unfortunately this isn't possible. What most DJI pilots do is leave the goggles powered up, showing the last known GPS coordinate in the OSD, then take a photo with their phone.
@@JoshuaBardwell thanks for the quick response. Does this mean the last picture gets frozen when i lost conection to the googles, so you can see the coordinates ?
Yo Joshua ( first off, your insights have been essential to get me going with FPV thanks much!) I had to replace my flight stack on my Nazgul 5 HD 6s. Up and flying but my goggles show n/a for batt voltage. Custome osd is on. Went into betaflight, set osd pref., saved, and yet, still no batt voltage indicator. It was there before Any advice for this newby question would be much appreciated, thanks
@@alessandromazzarella7799 No I have not found problem. I am thinking I blew a diode in the vista, not sure. I turn temp control off in dji goggles. Flying great. I just don't fly too long:)
Thanks for the info Joshua!! I'm assuming the loss of the craft name in the Betaflight Configuration settings is an expected outcome of this mod? I notice that unchecking "Unknown 1" in the OSD warnings brings the craft name back, but when it's selected the craft name goes blank (it's actually filled with 11 spaces). Obviously not a big deal, but for those who care, it does remove the craft name from CLI diffs/dumps.
@@AmatuerHourCoding Not by the Betaflight devs it's not. Etracer65 has said there is no chance of ever supporting it in Betaflight. Inav on the otherhand has it officially integrated and is a selectable feature.
Am I alone having this not working? I followed all the instructions and end up with the craft name being displayed instead of warning. Should you empty the craft name string for that to work properly? Thank you for your answers
Does anyone know how to download the Github file from a Mac? It seems to always save as a txt file and I'm unable to use this in the "Load Firmware" part. Thank you
Can anyone else not see the date created on JB's videos? On my PC chrome browser window it's usually to the right of the view count but it seems to only be his videos that doesn't have it.
Hi maybe a stupid question, but after you made this mode/flash will you be able to use it as normal on Analog for what ever reason?! Or is it only for DJI and if you want to use Analog you have to flash it back to normal?! 😵🙃
hex is simply a text file with a .hex file extension. So you can save and then rename. Or maybe beta flight will let you import the text file. In Windows if you type *.* in the file browse pop-up then it will show all file types.
this video really helped me, thank you! I killed my battery during my very first flight because I thought the goggles will warn about the flat battery..
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
This re-upload corrects a mistake in the flashing process. At 5:10 in this video, you DO need to select the correct target in the pulldown menu before flashing the generic target hex file that you downloaded. The original video left this step out. Thanks to the folks who pointed out that I got this wrong.
Thanks for fixing that!
Yep, I came up against this problem when following the first video
You don’t technically have to select the target, but selecting it saves you the hassle of applying the unified target config in CLI.
That’s what apply custom defaults does I think
@@josh8106 you get errors when you paste in the cli dump if the target isn't right
Also, thanks JB for updating the title to something less drama-filled, and more positive :)
After switching to DJI goggles, I crashed twice due to low battery, and was used to have the alert message in my (analog) goggles. Thank's Josh ! You saved my life again
Set a lowbat alarm on your controller. Works perfect on my Tango 2
@@Life_a_bike how to?
Thanks
As always, a great episode, and as always, everything is presented in a form that does not allow me to even make a mistake. Thanks, "I learned (again) something today" from you :)
..and I would like to add that I really appreciate the lack of ads during the movie, until they are still not there, as usual, I will play the first ones so that they can be played to the end , keep it up, others should learn from you how to create and manage their channels on youtube :)
Thanks, Joshua! It's worth supporting you Mate
Thank you, the how to man! Have not had warnings since DJI came out and have not missed it. But love this hobby cause there always someone there to help others.
I finally got it to work. I realized I was saving the hex file incorrectly. Thank JB. Keep up the good work.
Hey Joshua, is there an update for this on 4.4?
So after re-upload, I have to point out again, that the Warning OSD element is not in the MSP data stream, thus DJI had no access to it.
They asked for it, and the Betaflight devs refused to add it to MSP stream. BF devs told DJI to implement Displayport instead.
Your response to my previous comment was also (paraphrased) "they should implement Displayport like Shark Byte [just] did".
Problem is, Displayport is still not documented, is much more complex to implement and until the very latest BF firmware, didn't actually work (which Carl @ Divimath had to find out the hard way). In other words, at the time BF told DJI to do it that way, it wouldn't have worked.
And even if they did it today, it only works with latest version of Betaflight, and it's incompatible with iNav, and with all other flight controllers that have implemented the much simpler MSP protocol to talk to DJI's OSD (Pitlab, SN-L, SN-Navi, and the Mavlink -> MSP converter that can work with any other FC that outputs Mavlink stream).
If the MSP stream can't be changed, then re-purposing the craft name really seems like the simplest, and most widely compatible method to address the problem.
When etracer updated Displayport_MSP he said DJI had been lazy and not done what was needed. But then if Displayport_MSP was working fine why did it need updating and then suddenly become functional for Sharkbyte to use? Is it possible DJI simply couldn't do anything with Displayport_MSP in a broken state? In which case why did etracer accuse them of being lazy? Also this means that DJI could come through and fix the OSD now we can see Displayport_MSP works properly hence Sharkbyte's implementation. etracer did say DJI had been informed of this change so maybe we will see another firmware.
@@changeagent228 Regardless of the changes that etracer made for displayPort, we all know full well that DJI are never going to implement displayPort into their goggles and let other 3rd party software have control over writing to their interface, and any firmware changes like that are even less likely to happen now that DJI appear to have lost interest in the standalone FPV system and have re-focused all their efforts on the new FPV Drone. As much as I respect the Betaflight devs for what they do for our community, by pulling the "out of principal" card they are just punishing their user base and creating unnecessary resentment. The INAV and EmuFlight devs had no problem accepting similar implementations into those projects which has hugely benefited their user base.
It's such a waste of time and effort for mbilozub to have to maintain a separate repository for the modified Betaflight firmware just so that users can have this much needed and requested functionality, and an unnecessary hassle for users to have to go through those additional steps in JB's video in order to get the functionality they want. The PR containing this functionality should just be accepted into Betaflight like it has into INAV and EmuFlight.
@@snowleopardfpv I live in hope lol. Ferdinand Wolf, DJI's creative director said in a recent interview that they had plans to continue supporting updates to the Air unit FPV system which included but were not limited to adding support for the motion and v2 controller. I see no reason why they can't add a protection routine that prevents Displayport_MSP from accessing anything beyond the OSD overlay if they are that worried. I accept that there is still a chance DJI have given up on us though.
That said I agree that the Betaflight devs should work with the Craft_Name hack so folks can get on and use the OSD features in the meantime like iNav and Emuflight have done. Indeed it should not be necessary for mbilozub to maintain a separate repository.
@@changeagent228 I heard what Ferdinand Wolf said but I don't believe him. He also said that DJI had plans to make the Motion Controller work with the Air Units but that is BS IMO. They haven't even come up with an activation fix for the V2 goggles 6 weeks after all the issues began, and they have now taken down the rollback firmware which was the only workaround unless you also happened to own their FPV Drone.
I really hope I'm wrong but I think DJI are now done with any further development and support of the standalone FPV system and have moved on. I'll be surprised if we see any more firmware updates TBH. They very likely made more money on sales of their new FPV Drone in the first few weeks than they made on all of the standalone FPV hardware they sold in the last 18 months, and they lose interest fast in anything that doesn't make them much money. I believe the only reason that DJI made an 11th hour decision to hand over continued manufacturing of the Vista (and maybe Air Units) to Caddx was to quash some of the backlash and to buy a bit of time until things subsided. When DJI decide it's no longer worth their time and money to continue producing the custom ASICs needed for the Vista and Air Unit it will then be game over, and even Caddx won't be able to do anything about that.
I do own DJI gear for the standalone FPV system but I'm beginning to regret having given any of my money to DJI.
DJI and Betaflight both of them what a poser!
Hey Joshua, I was wondering if there is a work around for BF 4.3 as this doesn’t seem to work anymore?
If the devs won't implement a simple workaround which a major portion of the users actually need, then Betaflight has run it's course and it's time to fork it.
I remember that 2 years ago Betaflight devs wanted to add features like DJI support as pluggable modules or sort of like that. Seems it is time to release that thing already.
Not working anymore on 4.3 final release, is there any other solution ?
Thanks for this, thought i was going crazy when the warnings weren't showing up!
i love those dramatic intros :)
I just became crazy in the last 2 hours seeing the post in my Feedly but not being able to watch it 😂😂😂 thank you as always Joshua I learned something really useful today! 👍 keep the good work going!
Fantastic, Joshua! Thanks a lot! 😊
Stay safe there with your family! 🖖😊
I'm glad it was helpful 🤘
Nice work man! Thank you. This is so needed :)
Interesting. Are the betaflight devs pretty strict about accepting pull requests?
Max, thank you so much for the work around. I am struggling to get the warnings to display in the DJI Goggles. I have followed the video step by step and tried it a few times. I am running BF 4.2.8. Do you have any idea what could be wrong? Thanks
If you go looking through the code (why not), it's the "Pilot Name" (from MSP) not the Craft name, even though we call it that.
Let's hope that duder keeps updating as new versions of BF are released!
Does this mode working with BT 4.3?
The iNav version is officially supported and also has lots of other features like mAh/KM, 3D speed and throttle that can be enabled by adding WDTSE in the craft name field.
I asked etracer about adding it into Betaflight but instead he updated Displayport_MSP and insisted it is up to DJI to fix it not the Betaflight devs hence the unofficial hex modification by mbilozub. mbilozub's version only includes warnings but I have asked if it's possible to integrate the iNav functionality at some point.
Hi, Joshua it’s possible a toutorial about the building this feature in every BF version? 4.3 rc1 isn’t avaiable with this feature. Thank you.
Question - I bought a ready to fly Roma F5 with the DJI AU installed. If I do anything within Betaflight to the quad, does it overwrite anyone that has already been programmed by RDQ?
Bro I bought the same quad, what you did? RSSI works directly in your googles or you have to select a channel for that? Cheers!
A gentleman and a scholar.
Is it possible to get the osd warnings on the radio? Maybe with an audio slot?
Does this hack also brings the turtle mode arrow back in the osd? 2nd important osd element after cell voltage...
No it isn't supported.
@@JoshuaBardwell Ok, so i hope that DJI is coming with an update soon. I never would use turtle mode without this arrow.
I had noticed that if you plug the battery in before connecting to BF It will work with usb plugged in. The same thing happened with the Mag
BF would always pick up the Mag if I plugged in the battery before connecting. It was hit or miss if already in BF when connecting.
That was a "damn I'm good" chuckle😆
I think it was more: " we are at this point in the hobby"..
I’ve noticed I can’t get the smart audio OSD menu to show. It’s one of those things where I never knew if it was my setup or not.
Not sure what I'm doing wrong. I switch FCs and I can't get my V2s to work. I followed this video step for step...and nothing. I'm sure it's something super basic that I missed or something I didn't-know-I-didn't-know......Is there a button/switch that I need to check to get this to work?
YEAH... FORK IT!!! Your best quote of the year. :) Thanks for the info as always.
Hello Joshua!
Im very new to the hobby but I would really like these warnings on my goggles. I tried flashing but it fails every time. I unplug everything and plug it back in and everything is just as it was. Any step I am missing? I downloaded the hex file, copied the diff, matched the board name and target version (I think). but no luck. Thanks!
IT JUST WORKS! Thank you Joshua! Another helpful learning experience.
Great info, as usual. Thanks Josh. Will be referencing this later I'm sure
It works but I found it to be a little glitchy, sometimes the warning don't come up( like if leaving the throttle up a little when arming) ? I unplugged my gps and it said failsafe but would let me arm it? then when I unplug my battery and plug it back it in it would work better, the throttle warning would work and then it would say gps and it wouldn't let me arm? still better than nothing...
Philosopher and FPV Guru 🌞🙏
You have these little light blocker channels on your actual lens in the dji goggles. What are those? i can barely see those. What accessory is that?
They're 3d printed holders for fat shark style corrective lenses.
@@JoshuaBardwell ahh. Thanks for the prompt reply. I've watched a ton of your videos. Super helpful on every topic. I give every single one a thumbs up. I got a dji fpv a few weeks back. Had a small wreck broke both the front arms. Super weak plastic. Bought a nazgul 5fd that same night. Have been learning from you ever since! Thank you kindly. You do a terrific job and are truely funny.
Not work with omnibus f4. Betaflight 4.1 target 4.1. Elements appears in osd like warning battery and throttle.
But when you want to arm, always appear throttle and don't arm. Also before i done the diff all and so on...
So finally I go back to the normal configuration and it arm...
Maybe a bug?
So.... A similar workaround like this LQ from CRSF could be done?
ruclips.net/video/sYafWt-c7dQ/видео.html
I am running into the same issue where my osd isn't showing up, I have it on uart3, and MSP is turned on, on uart3, osd display is turned on in configuration tab, display tab on, and I made sure TX to RX and RX to TX, in the googles I have custom osd turned on. Am I missing something? I am getting an error message saying low power mode, unable to record. I found out I can turn off auto temp control, but even when I do that, the error goes away but the osd doesn’t come up.
I get the message "hex file is corrupted" when I try to flash this to my iflight Titan with Succex F7 TwinG flight controller.
Its the STM32F7X2 processor.
Anyone who knows a fix for this?
I have opened an issue on github.
Thanks!
Did you figure this out
can we use the custom logo for betaflight in the dji googles?
I need help, I have assembled a drone with the AIRUNIT and everything is fine, except that I cannot show the drone's battery charge, GPS data, etc. on the screen, of course, in the glasses it is configured as CUSTOM OSD: ON
Help
Hey Joshua thanks for all your contributions to the hobby you’re my go to guy!! Question : should I power my DJI goggles without the antennas????
I have heard that it won’t cause damage. I’m wondering if it’s better to power them on with antennas? Could it cause any damage ?
The DJI goggles are protected from this failure mode. I still wouldn't make a habit of it.
I am driving an hour west to meet someone i met in the DJI Digital FPV users group. She has the DJI FPV drone.
I have a question before I make this trip. I have attempted to update and also downgrade the firmware with my Apple home computer I’ve also tried with a Windows computer. It makes it through the first part of the update then when it gets to the next part the numbers stays at zero then the update fails giving me a DJI V2 update failed. 5-100-4 upload error log.
I had Tace Day Quads walk me through the process to no avail.
My question is is there’s something wrong on my end like with my computer or with the goggles?
Is this consistent with the activation problems others are having?
No, this is not the activation problem that others are having. It could be your computer. Hard to say.
@@JoshuaBardwell I GOT IT !!!!!!!!!!!!!!!!! I got them fixed!!!!!
Thanks for your help !!!!
#1 I had to use a windows computer.
#2 I did not use the supplied DJI usb to C cable. Not sure if it’s for data.
#3 my goggles were already activated!!!!!
I never completed the activation process I don’t know how they got activated. Maybe they came that way???? I do not know regardless they work thank you for all your help.
Hey guys I’m having a problem with my dji air unit... I’ve flown it 100+ flights and out of nowhere it stoped binding to the controller/goggles. It’s in bind mode (flashing blue w/ steady red light) and I’ve tried multiple times to bind it. Just tried to plug it into my computer and it keeps disconnecting and connecting every 5 seconds or so. Cable is good. Pls help :(
Hope they just implement this in the official 4.3. Come on BF devs.
should i set something in ports tab ? .. what to select there ? thanks
You need MSP enabled for the UART that the DJI TX/RX wires are connected to.
@@JoshuaBardwell Thank you !! i just found that out in another site. this was the last part i was missing .. now it works. :)
Man this intro gettin REAL! 😁
Sir, could you upload your and factory setup for iflight protek 35 to your paste bin ? thank you
thanks again for another great lesson, i couldnt get my settings back on the fc after i reflashed tho :X kinda a bummer any idea how to not have this happen if i do it on my 5innch quad?
You have to save the settings. Use the Presets tab. Then load them after.
@@JoshuaBardwell done,, on the 5inch all settings the same, thanks again bro... i wasnt kidding about you makin a shirttt with "YOU GONNA LEARN SOMETHIN TODAY" and ur face or ur quad or even ur signature logo, this was a quick idea . id rock it, i know many others would love to have it also u a true g thanks for the loyal wisdom we love u.
is there a hex i can add to my radix v2 ?
i believe these warnings are a critical part of the osd information. next critical piece of the dji goggle puzzle is that it would be really really nice if we were able to have DVR that includes BF / INAV OSD information without having to log telemetry and go to a computer and overlay the info onto a video , surely in 2021 one day we can just record the full custom osd ??
A bit unusual, but I use craft_name as a way to put a serial number for my insurance, which is mandatory. Is the original craft_name put back after a warning is given?
No. Craft_name is gone.
@@JoshuaBardwell Oh, too bad. Thx for the quick reply though!
@@JoshuaBardwell Any other way to paste a custom text string with a self made-up serial number into the FC? Maybe some unused parameter or so.
Is it true there is a bug with using this patch. I seen somewhere it stating this can cause your quad to not be able to disarm and failsafe issues. Is this true? I'm currently on 4.2.8 dji warn patch on Couple my quads.
Joshua i lost my dji osd after swapping fc from bf fc to kiss fc.. literally the dji uarts now dead. after done wiring i get my full dji osd with kiss fc.. but then after i want to go fly the osd is gone and no voltage reading from dji airunkt uart. Like i said everything is fine before, no wrong wiring etc..i already switch to different serial (1 and 3 on kiss v2 board) and no osd. Both serial are working fine with my gps (so no broken/loose connectors). i ask alex fedorov about can kiss fw kills dji uart? He said it will never kills uarts. But as i did some searchig many kiss/fettec user losses their osd and voltage and this means dji uarts reading getting screwed up.. and even switch back to other bf fc wont bring back the dji osd and voltage.. can you do a research about this.. i cant find ppl having this problem with betaflight/flightone board. Only kiss/fettec users do. Thanks
Thanks JB, excellent video! I will implement on my DJI BF quads.
I been wondering why BF won't do this since my iNav plane does. It's nice others can fork it and implement this. But honestly seems ridiculous that you need to since the other open source FC firmwares have already adopted it. Maybe it's time to fly emu on all my quads. BF dev push back on a feature was the whole reason butterflight started.
I'm thinking the same thing. I'm planning on flashing Emu on one or two of my quads to check it out. If all goes well, I'll convert them all to Emu. I understand that the firmware is donated to the community free of charge, and alot of work goes into it. But the childish crap about not adding in a feature, or features, that would greatly benefit the whole BF community, just because you don't like a certain company, kinda irks me. I'd rather support devs that care more about the quality & usability of their firmware, than ones that don't because of personal feelings.
Interesting, when I accidentially flashed my Rekon 5 with the standard target instead of the HGLRC I did brick my flightcontroller. The flightcotroller did work with sporadic crashes, but was nolonger flshable due to USB errors ( And I tried everything ZADIG, immersion RC ...)
Thanks man, we keep learning
Ha ha, intro is amazing! Thanks for what you are doing!
Hi Joshua, Thank you for all the great tutorials! All the FC,s I am flying have STM32H743 as the target but I cannot find a firmware for this target. Do you have any Idea if one will be available or if there is any other way I can make it work? Thank you
Did you every find a STM32H743 file?
Can you share your configuration?
JB need some help here. Just tried this on baby croc HD that was on 4.2.4. Tried both 4.2.8 and 4.2.9 on my STM32F7X2 but uarts 1 and 2 are missing, System beeps for motor checks are not there. Also if I enable OSD in Betaflight I can't get back into Betaflight unless I DFU and start all over again. Drove is dead in the water. Any suggestions would be great
My best guess is that your FC is not actually stm32f7x2 but some other target.
I have been trying this for an hour and a half. No matter what I do, Betaflight gives a message of "Hex file appears to be corrupted" and refuses to load the betaflight_4.2.8_STM32F745_norevision.hex file. I have tried the 4.2.1, 4.2.0 and 4.3.0 files and deleted Betaflight Configurator and reinstalled the latest version. No luck. Too bad, I'd love to have the warnings.
I finally got it to work by downloading the whole archive here: github.com/mbilozub/fpv_custom_mods/archive/refs/heads/master.zip Thanks mbilozub
@@subzero674 DUDE you saved me!
@@fernandofaixa I'm glad it worked!
Perfect!
I’m sure my opinion would be different had I experienced a DJI video feed. But, I am so tired of hearing about DJI!
Just keep doing what you do. I’ll get over it!
yet you here watching a dji video
It's not DJI's fault Eachine and Fatshark's R&D is smashing rocks together pretending VHS analog is relevant in 2021.
Hey Joshua, is there any way to record the Betaflight OSD with the V2 Goggles? My problem is to find the quad with the GPS location that is shown while flying, but if you want to rewatch the recording on the SD-card, there is only the DJI OSD.
No unfortunately this isn't possible. What most DJI pilots do is leave the goggles powered up, showing the last known GPS coordinate in the OSD, then take a photo with their phone.
@@JoshuaBardwell thanks for the quick response. Does this mean the last picture gets frozen when i lost conection to the googles, so you can see the coordinates ?
The OSD gets frozen but the picture does not.
I did everything as per the video, i named my drone "MSP" now my osd shows "MSP" not LQ value?
hi, what happen if we load a dump instead of the diff all, will it erase the warning trick ?
No
@@JoshuaBardwell Thanks josh, and be carrefull, don't forget that now, sometimes you carry a baby and not a quad on your back bag !
Can we get a hack for video out to iPhone from air unit or vista video :)
I dont have unknown tab?
I'm using betaflight 4.2 and I cant find horizon mode? And idea what I can do?
Awesome video JB!!!
Hey JB, any idea on why my craft name would read LINK QUALITY even though I never set a name? Reads that even after deleting and saving. weird
Yo Joshua ( first off, your insights have been essential to get me going with FPV thanks much!) I had to replace my flight stack on my Nazgul 5 HD 6s. Up and flying but my goggles show n/a for batt voltage. Custome osd is on. Went into betaflight, set osd pref., saved, and yet, still no batt voltage indicator. It was there before Any advice for this newby question would be much appreciated, thanks
Hello Jason, same problem, same quad, i've tried to buy another FC but the problem still exist, i tried to change the caddx but same problem.
@@alessandromazzarella7799 Hmm, interesting. So are you still flying without Vbatt read in goggles?
@@jasonnovak7229 no in this moment i don't fly! do you find the problem?
@@alessandromazzarella7799 No I have not found problem. I am thinking I blew a diode in the vista, not sure. I turn temp control off in dji goggles. Flying great. I just don't fly too long:)
Thanks for the info Joshua!! I'm assuming the loss of the craft name in the Betaflight Configuration settings is an expected outcome of this mod? I notice that unchecking "Unknown 1" in the OSD warnings brings the craft name back, but when it's selected the craft name goes blank (it's actually filled with 11 spaces). Obviously not a big deal, but for those who care, it does remove the craft name from CLI diffs/dumps.
Cool video!
Is there a way to get the GPS arrow into the DJI goggles? My Rekon5 doesn't show anything GPS in the DJI goggles.
Arrow is fully supported
@@DronoTron Yes, found it a few months ago, some switch in the goggles.
Download files on GitHub is annoying because GitHub isn't file storage :D This file should be available from the Releases page :)
It is not officially supported by the devs. Use at own risk.
It kinda is tho... use git
@@AmatuerHourCoding Not by the Betaflight devs it's not. Etracer65 has said there is no chance of ever supporting it in Betaflight. Inav on the otherhand has it officially integrated and is a selectable feature.
Am I alone having this not working? I followed all the instructions and end up with the craft name being displayed instead of warning. Should you empty the craft name string for that to work properly? Thank you for your answers
me too. I got my craft name constantly changed to LINK QUALITY. Don't know what the heck is wrong. you got any solution yet?
Hi
My DJI V2 audience mode is grayed out. Can you help me how to fix this issue.
Thanks
If your vTX is in 50 Mbps mode, audience mode is disabled. Switch to 25 Mbps
Does anyone know how to download the Github file from a Mac? It seems to always save as a txt file and I'm unable to use this in the "Load Firmware" part. Thank you
Can anyone else not see the date created on JB's videos? On my PC chrome browser window it's usually to the right of the view count but it seems to only be his videos that doesn't have it.
Unknown 1 is not an option on my warnings list 🤔
You have to download the modified hex file and flash it as shown in this video for that to appear.
@@JoshuaBardwell thank you 🙏🏻
Both quads now have warnings, stoked! 🙌🏻
Hi maybe a stupid question, but after you made this mode/flash will you be able to use it as normal on Analog for what ever reason?! Or is it only for DJI and if you want to use Analog you have to flash it back to normal?! 😵🙃
If you have Analog, just disable the User1 warning and functionality will go back to normal.
Spot on, thanks@@JoshuaBardwell
How do i save it as a hex file om a macbook? It jeeps savning it as txt
hex is simply a text file with a .hex file extension. So you can save and then rename. Or maybe beta flight will let you import the text file. In Windows if you type *.* in the file browse pop-up then it will show all file types.
perfect, as always .. great helpfull... thanks so many
Can we get rssi LQ on dji osd?
ruclips.net/video/sYafWt-c7dQ/видео.html
Can you make a video for geprc smart
Works with JBF7-DJI but not with the one on the geprc smart
Lol... I am abusing pilot name since day one on kiss without any fuzz... ;) Freaking funny ;)
Great video. Just no beer in fridge
Hey JB, I see other pilots OSD in audio mode? I mean their Betaflight OSD, same with people watching me. Done it on Sunday
What do you mean? I never said that didn't work! I have no idea what you're talking about ;-)
@@JoshuaBardwell cheeee-kay
Great video! I'm wondering, though, if you know a way to record the OSD in the DJI 2 Goggles?
No. There's no way to record the Betaflight OSD unfortunately.
“Never works out that way does it” LOL!
Thank you! You are the best
Brilliant stuff. Thank you.
Can i use this for protek25?
Does this work with Mac os? I'm trying to save file as but its always saving as a hex.txt or hex.html.
Any help would be appreciated.
I've figured it out! Safari was being a pain. Had to use Firefox.
very nice! Thank you
this video really helped me, thank you! I killed my battery during my very first flight because I thought the goggles will warn about the flat battery..
Anyone know how to change bataflight pid profiles using dji goggles ?
its not working for me on matek f405 std. it says the hex file is corrupt
I had the same problem here. Tks
@@davicarboni7025 i figured it out. You are downloading it from github the wrong way. Follow the video exactly
2:13 aaaaand the Kiss FC Dev has done it as well.