There is now a tool to let you roll back the firmware on your goggles so you can root, even if you flashed to a firmware that locks out root! ua-cam.com/video/63Smmc0bNcg/v-deo.html
Donate! Donate! These guys are busting their butts to give us what DJI couldn’t, the least we can do is show them how much we appreciate their hard work!
There is some wrong information floating around here in the comments: - DVR is working, please stop spreading misinformation - Root is working for V1 and V2 googles (and all air units). - Live Audio works for OG air-unit and V1 goggles
DJI easely could`ve done it a long long time ago. People would praise them for listening to the community and they would be the good guys. Would be a win-win for both parties. HUGE THANKS to the whole FPVWTF team for doing all this work and even bringing more features than we ever expected to have! You guys are true heroes! Thank you!
Never happy some people. Dji have given us freestylers the best most stable clearest system yet. No one else has. I don’t get the whole hate dji thing. If they didn’t give us awesome video there’s no additional features like this. V1’s for the win.
A few notes from the main author of msp-osd (me): * Yes, DVR works fine. I re-introduced this functionality in August when I re-wrote the MSP DisplayPort overlay to co-exist with the DJI goggles overlay. No functionality should be lost by using msp-osd (although there is a known bug, see below:) * Low Power Mode is always on before arming right now. Full power unlocks when you arm, as it always has. Most people fly this way anyway, if you don't know which way you fly, this is the way it already works for you. But for those who turn Low Power Mode Off intentionally using the Auto Temperature Control option, right now you need to re-select Auto Temperature Control Off each time you boot. I am working on fixing this sometime this week - this video caught me a bit by surprise and I'd hoped to have it done earlier so I could say "no known bugs" :) * It is very unlikely to be possible to record the OSD into the video directly from the goggles. The V1/V2 FPV Goggles don't have a lot of CPU power available, and software compositing high resolution video is quite CPU and memory bandwidth intensive. However, what we plan to do in the future is to write the OSD data to a file alongside the video (similar to the .srt files DJI uses today), and build a companion application which can "burn" the OSD data into the video on a computer later.
Sweet! I'm excited to try this. I use v1 goggles and an analog module for tinywhoops and the awesome dvr on analog module. Any concerns or changes on analog module usage? Latency? DVR?
@@nigelolympia NP. i thought after update to 0606 mine did a reboot and not auto reconnect to DJI software, so i was able to connect to wtf. i have to delete my upper comment, just not helpful... :-)
couple of years i've been flying dji now, and still, when under any pressure, i struggle to see my voltage and timer, wish i could get mbs more in the center too. great stuff wtf team, this kinda project makes this hobby possible.
Fantastic, Joshua! Thanks a lot for the tutorial! 😃 If (IF) DJI was smart, they wouldn't fight this. They would incorporate it! But do you want to bet what's going to happen? Anyway, stay safe there with your family! 🖖😊
Just FYI there is still a bug in the OSD code where the vista will go into low power mode regardless of whether the auto temp control is set to off or on in the googles, this is only really a problem if you run your vista with auto temp control off and like it start recording manually, if you run it on you won’t notice any difference. The present solution is to go into the googles menu, select auto temp control and change it to on, then change it to off and the vista will then respect the setting until the next power cycle (yeah you have to do this every time). They are working on it, but it’s only just been discovered so won’t be fixed quickly.
@@REAL_N3W that’s correct, whatever your setting in the googles it’ll arm and unlock as normal once you arm. I personally like to run with auto temp control off because if I get stuck in a tree, I can still get video and turtle out of the tree after I’ve disarmed. If you run with it on when you disarm the vista goes into low power mode and 90% of the time the googles will loose sync from the vista and loose the video signal, which can depending how high you are in the tree or how far away the tree is, can make it difficult to turtle out.
msp-osd got updated to v0.6.5 today and the issue should be fixed. You should update both goggles and air side. Please let us know if the problem still occurs after updating.
So stoked that this is a thing. Been waiting ever since I first heard about the root hack. Personally, I'm not super interested in the osd, but I really hope we see the 60 Mbps plug in at some point. Thanks to everyone involved for their hard work. 🙏🏻
Hey JB, have you ever considered running a fan under the table with duct work tube to the table top? If the fan noise really bothers you, that could be a clever fix.
Very nice. Works as advertised. The only thing I ran into was having to root twice, both the goggles and the vista. After the first time the configurator couldn't find a device to connect to. Apart from that, I just followed the video, didn't need to go to the github repo for anything. Very polished tools for a v1 root hack. Thank you everyone involved.
@@JoshuaBardwell What I meant was I has to root the goggles twice, and the vista twice, even though the first time said success and Windows said the device was connected the wtf code couldn't connect. After the second time it worked fine.
Patience pays off, once again. I have been waiting on this to pull the trigger on rooting mine. I have v2s -AND- a DJI FPV drone, so I didn't risk it while experimental, and didn't want anything to update and lock me out.
I did it a few weeks ago. It’s seamless but I would advice if you can use a power supply rather than a battery and have a desk fan pointing at the gear while rooting. Also rooting can take a few minutes and during the process you might get a “cannot find device” message, just ignore it and don’t be tempted to start fiddling, the configurator will find the headset after a few seconds.
For those thinking of doing this, but are dreading the task of having to convert all air units, let me assure you that the assumption is incorrect. You can, in fact, root, install WTFOS and install the MSP OSD package on the goggles and an unrooted air unit will still send its custom OSD. There is one downside in that the WTFOS blinks "Waiting for OSD..." in the bottom right corner. It isn't completely in the way, but would be nice if that didn't happen while Custom OSD was turned on!
Their FAQ states that this would be very difficult because of how the video layers and focus mode work. What you could always do though is creating OSD text from blackbox data and adding that as an overlay in a video editing software. IIRC there are scripts that automate that process that even give you fancy gauges for speed and current. What developers could propably do without too much effort is writing subtitle files onto the internal storage of a Vista, just like the Air Unit does.
Thank you JB and the WTF team. Just a side question... if for some reason DJI releases a feature that interests the FPV world in a future release and we decide to apply an official release after rooting... do we just use the Bind and Power step to revert back... or once we are rooted... do we have to stay in the rooted world? Not that I expect DJI would release something worthy of potentially not having what WTF built... but was just wondering.
Great video thanks Josh for bringing this to us asap. Was wondering if there was any update on being able to record the OSD elements in either google DVR / using the digiview app? That be the real game changer, so sad we cant do this as of now.
Okay so what actually changes when you turned off custom OSD in the goggles? There was like mah, and something ae that went away.... Why were those there in the first place? I guess that's all that confused me. Great vid JB! Also, I wonder if when the update comes to make the v2 goggles work with the O3AU, if they will lock out root or whatever 🤔
What that takes away is the few supporedt OSD elements that DJI supports over MSP, like battery voltage, GPS info and a few others. And it will be shown in DJI goggles font. Custom OSD isn't needed anymore since you have direct access to betaflgiht OSD.
Awesome! This is what fixed wing has always wanted since hd fpv! Live audio and full betaflight/Inav support❤️ Is live audio available for V2 goggles now? I heard they were working on it a while back
Live audio is currently only available for the V1 Goggles, because we re-enabled some dormant audio code DJI had left around. This code is not present on the V2 firmware. For V1s it's actually missing from the configurator currently, but it will return soon. For the V2 Goggles someone would need to write a new audio system from scratch. There were some early experiments but latency was bad. Like half a second bad. So it's a lot of work.
Unable to get this to work.. when attempting to connect to my googles i get "NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface." Anyone else gettng this error? any idea how to fix it?
Nice Mod...have done it ...everything seems to work perfekt ....but at the air units e had some issues with restoring space 1...or 2 at the savetydevice of the unit...and had to root it 2 and 3 times...until it worked ...now the testingperiod is started....we will see ! Thanks mr Bardwell for all the googd vids and infos!! Crazy guy with crazy connections! Would love to come one day to the rampage camp.. greatings from Germany
Interesting but premature, I will wait till it's officially released and watch Madrc's stream on Friday with Joonas before risking my goggles, I can hold out for a couple more days plus by then I may see how many people brick their goggles if any.
Dang you are one lucky man, found a way to make a living doing something that's you like and looks fun. My first drone , was last seen flying northwest ... something failed . Expensive mistake , but lesson learned next venture was smaller but lacked function , by the 4th venture, full functions were realized. Since that time improvements have been made, but the project that has vexed me, has wings, and duct fans , and requires 13 of 16 channels , oh , it's a, YRF-4E. It was an experimental F4b Phantom, with cannards , it lived just up the road at WPAFB. I saw it first in 1967 or 8 , and made a decision to model it. Time with 6 kids , and money for such, well it became a retirement project. For a dozen years I have built and crashed ... went to WPAFB to capture details 2 cameras and lots of memory cards. They lost the plane, along with the staff we looked high and low. Wrote on FB about losing a prototype aircraft, gosh the airforce got mad ...lol . Yea well they didn't drag their wife around the base for hours looking for the plane. In a cranky letter , they explained it was out for paint. Several years went by and it was still out for paint. So I offered to come up and help after all I had some slightly used paint brushes out in the shed ... you know they still have no sense of humor. Now it's status is in storage . My tiny prototype flew across the yard and into the neighbors yard, ... since then every try has met with disaster, exploding fan units , failed servos, burnt wiring ...currently 3 new attempts lay about my work area, but I got old, hand and eyes ... ifvi build it , I don't trust myself to fly it. Well at least thevprototype flew, and is on rc groups ..., it was destroyed when I moved, oh well .
Great info. I like your ability to dumb down the info for us noobs to understand. I am really playing catchup at the moment and trying to crash course FPV. A sub $100 analog system opened Pandora's box for me. I am putting together a FPV trail truck to start, fast stuff later. I went full in and got a pair of Dji Googles 2 and 03 air unit. I am mounting the camera on a Motionsic B.A.G. and the vtx will be heatsinked + fans to aid cooling. Vehicle control will be handled by a Radiolink RC8X, which is head tracker compatible, and up to 800 meter range. Where I am having issues is getting the OSD functions I want. I really want vehicle speed on screen and pitch/roll would be a nice bonus as well. There doesn`t appear to be any surface specific hardware available so I am looking at drone parts. I think I need to install a flight controller and gps module to get the OSD I want so I can then also use beta flight for settings. I think I could also power the two 5v fans from the flight controller?? I have step down modules on hand if not. Any recommendations for a FC + GPS module that may serve my needs?? Any issues I may see with the RC8FG rx and FC interacting? I believe I will need to "arm" the FC to unlock the airunits powerswitching?? Obviously not a budget minded build and the chassis won`t notice the extra weight. I will have the camera system mounted and working soon, should still be a ton of fun without the OSD, but I am hoping to work out the osd.
Great vid - looking forward to doing this along. Been researching this (since one of my FPV buddies showed off his OSD) and also felt that now it looks really easy to do. The thing holding me off until now was DVR recording. But looks like now it works? greets, Mario
Yes, as noted by @bri3d (comment above), and from Ian's interview of WTF team, just camera video will be recorded in goggles DVR. Goggles hardware does not have power to re-encode video with OSD. One possible future feature is being able to do this re-encoding post-flight on a personal computer. (OSD MSP data would be saved like the DJI SRT is now)
Thanks JB for taking us through this and thanks to the FPV-WTF Team. So far I'm sticking with Digital Font, that is until you tell us the one you prefer.
@@JoshuaBardwell A few people are working on bringing font installation and selection to the configurator. Hopefully some time soon after launch. That'll make it easier to find one you like. But there's another side to this coin, which is the fact that BF doesn't yet support an HD MSP DP grid (unlike iNav and Ardu). This means while we can make the characters smaller on the SD grid, the positioning remains exactly the same. So character spacing grows in a weird way, when the font gets smaller. At one point it starts looking ridiculous. We're talking to the BF devs about solutions.
I forgot to add - todays msp-osd v0.6.3 update brings an optional "fakehd" mode which does funny things to the grid and chops it up. Parts of the screen become dead zones and the rest have a higher resolution grid available. Check it out, details in msp-osd README.
That is Awesome! Now DJI has to think about what feature they have to give us to exclude us again with the next update. DJI your turn... O3 Air unit with Canvas Mode support? Buy new stuff to get the feature?
Great video again Mr Bardwell! Have you ever tetsed the DLNA wireless broadcast of the DJI 2 goggles? Cos if the latency is low enough this could allow those of us that love crazy wide FOV to make their own box style goggles with NICE BIG FOV 😁
This was one of the big reasons I chose not to buy from them. Had they simply shown that they cared, I would likely be shelling out another $100-150 per quad just for their video system. Instead, they showed me that it's better to choose small/community driven projects, even if they lack can a few things. Still happy with analog and HDZero.
Hey joshua what should I do when I'm going to put in the cli set displayport_msp_serial = allowed range -1 - 40 when I use uart 1 on my aio should I put -1 then to make this work if I had uart 2 I would have to sat uart 1 but I'm using uart 1 so I'm not fully aware of this I hope for an answer Thank you so much for doing this you're the best greetings from Norway ❤️
Many thanks for answers love people like you who take time for people and help us who have just started with this hobby love you bardwell ❤️ because now I only get font font bin font font bin in dji goggels v2 dkal test and set display port on uart 0 as long as I I have msp on uart 1 Thank you
This is my first time using CLI, even though I have been using some Python and C++/Arduino for a few years now. It still took me a half hour to figure out that I had to type 'save' after entering the commands, if I wanted it to take effect. ugghh! 💀
I did root and ... no OSD. I can see that fonts are being loaded and other stuff, but no osd. Probably I've missed the SAVE command. But... Josua also missed it in tutorial I guess...? ;)
@@paw288 for sure, that is fair. Good ol' JB keeping us on our toes! But I did have same issue with my second quad, not showing OSD, after rooting. So, this was after I had already done it successfully, earlier that day. Today I re-rooted the Air Unit of the one that would not show OSD and that fixed the issue.
It would be cool if these guys could hack the code on DJI's GPS camera drones. Allowing people to power them with regular batteries and no longer have to buy proprietary and over priced DJI batteries. Allowing us to have full manual control on a switch. Wouldn't that be cool? Maybe even have control over whether or not DJI is sent the flight data.
The OSD doesn't look that good as the font is too big and low res. Also the osd doesn't go to the edges even after changing to PAL. Still this is a huge achievement by the fpv wtf team, thank you for implementing this!
Part of this is the size of the grid of characters that BetaFlight has implemented for the OSD overlay. ArduPilot and INAV have implemented a larger grid, so characters appear are smaller. (think BF uses ~30 characters across, where others support 50 character grid width) Using a smaller font in BF will leave larger gaps between OSD characters, as the grid size will not have changed. If want to know more on this topic, it was coved in Ian's interview with FPV-WTF team.
Looking forward to rooting my goggles. Will the OSD record on the goggles thou? Much needed for long range flying being able to see my GPS coordinates in the playback
A few notes from the root process from my experience on V01.00.0608 - close DJI assistant app! If you have it open, it will appear on COM portXX but will not start the root process. - takes about 2-3 minutes total, goggles will reboot several times. There are 5 steps in total, and if you've done it correctly the root text should look like this: 00:02 Attempting Step 1... 00:16 - Found Device: GL150, Version: 01.00.0608 00:16 Step 1 - Success! Rebooting... 00:32 Attempting Step 2... 00:49 Step 2 - Success! Rebooting... 01:05 Attempting Step 3... 01:15 Step 3 - Success! 01:15 Attempting Step 4... 01:20 Step 4 - Success! Rebooting... 01:20 Device went away... 01:20 Device came back... 01:39 Attempting Step 5... 01:41 Device went away... 01:42 Device came back... 01:44 Step 5 - Success! Rebooting... 01:57 All done - your device has been successfully rooted!
Have any of the steps changed with the Betaflight CLI commands, since the newest Beta Flight 4.4 update? I'm getting the following error, '###ERROR IN set: INVALID NAME: displayport_msp_serial = 1###', after I enter, 'set displayport_msp_serial = 1', when typing in the second CLI command. My VTX is on UART2, and my ELRS receiver is on UART1. I was able to successfully root both Goggles V2, and my Caddx Vista, and this is the only issue I have had in the whole process. What do you think I should do? If anyone else has had this issue, please let me know what you did to resolve it. Thank you in advance for your help.
After posting this, I looked in the comments and found Joshua responded to this very issue. He has created video addressing it titled, 'Betaflight HD OSD with DJI Walksnail & HDZero // HOW TO SET UP'. Thank you JB!!
HI JB great fan from germany! I missed something all the time about the digital HD OSD and just got it right. I had to change the font from "standart" to "digital" in the OSD tab. that and only that made the magic happen fpr me: Maybe I missed it in this video. Happy Flying Frank
I just completed my WTF OSD and I had to complete the Butter update. My goggles are from the DJI FPV kit. Now after completing all the updates and test flights everything worked as it should. Now today 2 days latter I went out to fly and found I had 2 sets of OSD in two different founts. I pulled the SD card out as your Video states that the OSD was on the SD card only. Still with no SD card I have OSD.
There is now a tool to let you roll back the firmware on your goggles so you can root, even if you flashed to a firmware that locks out root! ua-cam.com/video/63Smmc0bNcg/v-deo.html
Is it time for an update video???
Are there any news on how to update?
@@PowerThumb.When will this be available for the 03 air unit?????
Donate! Donate! These guys are busting their butts to give us what DJI couldn’t, the least we can do is show them how much we appreciate their hard work!
Thank you 🙂
Never they should be open source
@@EMDRONES It would be better if it was open source and monetisable
@@EMDRONES What are you talking about - 100% of our code is open source.
Donation is a must for this great developers and I hope they keeps supporting it. Amazing job.
There is some wrong information floating around here in the comments:
- DVR is working, please stop spreading misinformation
- Root is working for V1 and V2 googles (and all air units).
- Live Audio works for OG air-unit and V1 goggles
Ans live audio works perfect for the air unit and v1s
@@squaddingquads awesome. Glad I hung onto my V1s!
Me too
Can confirm DVR is working, been using this for the past month without issue, brilliant work.
It used to be that dvr was working but it wouldn't record bf osd. However may be they enabled this feature.
DJI easely could`ve done it a long long time ago. People would praise them for listening to the community and they would be the good guys. Would be a win-win for both parties.
HUGE THANKS to the whole FPVWTF team for doing all this work and even bringing more features than we ever expected to have! You guys are true heroes! Thank you!
Never happy some people. Dji have given us freestylers the best most stable clearest system yet. No one else has. I don’t get the whole hate dji thing. If they didn’t give us awesome video there’s no additional features like this. V1’s for the win.
A few notes from the main author of msp-osd (me):
* Yes, DVR works fine. I re-introduced this functionality in August when I re-wrote the MSP DisplayPort overlay to co-exist with the DJI goggles overlay. No functionality should be lost by using msp-osd (although there is a known bug, see below:)
* Low Power Mode is always on before arming right now. Full power unlocks when you arm, as it always has. Most people fly this way anyway, if you don't know which way you fly, this is the way it already works for you. But for those who turn Low Power Mode Off intentionally using the Auto Temperature Control option, right now you need to re-select Auto Temperature Control Off each time you boot. I am working on fixing this sometime this week - this video caught me a bit by surprise and I'd hoped to have it done earlier so I could say "no known bugs" :)
* It is very unlikely to be possible to record the OSD into the video directly from the goggles. The V1/V2 FPV Goggles don't have a lot of CPU power available, and software compositing high resolution video is quite CPU and memory bandwidth intensive. However, what we plan to do in the future is to write the OSD data to a file alongside the video (similar to the .srt files DJI uses today), and build a companion application which can "burn" the OSD data into the video on a computer later.
It would be really good addition if we can record the osd. Thanks for the great work !!
Sweet! I'm excited to try this. I use v1 goggles and an analog module for tinywhoops and the awesome dvr on analog module. Any concerns or changes on analog module usage? Latency? DVR?
Oh and .srt files are read as a subtitle track in most video editors so you could have it spot..srt and not need a companion app.
love the idea of having a separate OSD text data
do things like the compass and artificial horizon work or is it just text ????
Huge shout out to the FPVWTF devs for their hard work!!! Thanks you all VERY much!
Thanks to the FPV community and especially FPV-WTF who have done what a multinational company could not/would not do.
PRO TIP: If you’ve just updated to 0606 to do the root, make sure you close DJI Assistant or the rooting will fail.
thanks a lot, i was wondering why it wouldnt root my goggles
deleted my useless comment
Fucking THANK YOU!
@@rolliseventeen It was for me just now. Closed it and rooted just fine.
@@nigelolympia NP. i thought after update to 0606 mine did a reboot and not auto reconnect to DJI software, so i was able to connect to wtf. i have to delete my upper comment, just not helpful... :-)
As a newbie I learn the most from your videos. I like the way you cut the bullshj*t and get to the point.
I'm using rooted goggles for 2+ months and it is becoming better and better.
couple of years i've been flying dji now, and still, when under any pressure, i struggle to see my voltage and timer, wish i could get mbs more in the center too. great stuff wtf team, this kinda project makes this hobby possible.
This is amazing! Whyyyyyyy wouldn't DJI support this natively if it seems so possible? Blows my mind
Yes, would have been way easier for them to implement than having us do it :-D
China
DJI are like apple, don't expect anything from them
Completely agree!!
Why would DJI just give you this feature when they can make you buy a new set of goggles to get it?
Thanks! So much for making this video, it really helped me out!
Such a great hack. Huge thanks to FPVWTF and Bardwell for sharing.
Why now, tho? Ugh. DJI should have done this 2 years ago.
I've been waiting a long time for this and I'm so glad it's here! I will be contributing to the project
Fantastic, Joshua! Thanks a lot for the tutorial! 😃
If (IF) DJI was smart, they wouldn't fight this. They would incorporate it! But do you want to bet what's going to happen?
Anyway, stay safe there with your family! 🖖😊
You are the King JB, never getting tired of listening to you 🤗
Just FYI there is still a bug in the OSD code where the vista will go into low power mode regardless of whether the auto temp control is set to off or on in the googles, this is only really a problem if you run your vista with auto temp control off and like it start recording manually, if you run it on you won’t notice any difference.
The present solution is to go into the googles menu, select auto temp control and change it to on, then change it to off and the vista will then respect the setting until the next power cycle (yeah you have to do this every time).
They are working on it, but it’s only just been discovered so won’t be fixed quickly.
I thought it was just my unit. Good to know
So just set it to ON ? But it wont be on low power mode after arming?
I appreciate this comment so much thank you! Been trying to play around to get rid of that low power bs. Thanks for the fix!!!
@@REAL_N3W that’s correct, whatever your setting in the googles it’ll arm and unlock as normal once you arm.
I personally like to run with auto temp control off because if I get stuck in a tree, I can still get video and turtle out of the tree after I’ve disarmed. If you run with it on when you disarm the vista goes into low power mode and 90% of the time the googles will loose sync from the vista and loose the video signal, which can depending how high you are in the tree or how far away the tree is, can make it difficult to turtle out.
msp-osd got updated to v0.6.5 today and the issue should be fixed. You should update both goggles and air side. Please let us know if the problem still occurs after updating.
So stoked that this is a thing. Been waiting ever since I first heard about the root hack. Personally, I'm not super interested in the osd, but I really hope we see the 60 Mbps plug in at some point. Thanks to everyone involved for their hard work. 🙏🏻
Hey JB, have you ever considered running a fan under the table with duct work tube to the table top? If the fan noise really bothers you, that could be a clever fix.
Very nice. Works as advertised. The only thing I ran into was having to root twice, both the goggles and the vista. After the first time the configurator couldn't find a device to connect to. Apart from that, I just followed the video, didn't need to go to the github repo for anything. Very polished tools for a v1 root hack. Thank you everyone involved.
Yeah you have to root both. Otherwise you can't install the plug ins
@@JoshuaBardwell What I meant was I has to root the goggles twice, and the vista twice, even though the first time said success and Windows said the device was connected the wtf code couldn't connect. After the second time it worked fine.
Patience pays off, once again. I have been waiting on this to pull the trigger on rooting mine. I have v2s -AND- a DJI FPV drone, so I didn't risk it while experimental, and didn't want anything to update and lock me out.
I did it a few weeks ago. It’s seamless but I would advice if you can use a power supply rather than a battery and have a desk fan pointing at the gear while rooting. Also rooting can take a few minutes and during the process you might get a “cannot find device” message, just ignore it and don’t be tempted to start fiddling, the configurator will find the headset after a few seconds.
For those thinking of doing this, but are dreading the task of having to convert all air units, let me assure you that the assumption is incorrect. You can, in fact, root, install WTFOS and install the MSP OSD package on the goggles and an unrooted air unit will still send its custom OSD. There is one downside in that the WTFOS blinks "Waiting for OSD..." in the bottom right corner. It isn't completely in the way, but would be nice if that didn't happen while Custom OSD was turned on!
have the same issue
The killer feature I want is recording the OSD overlay on the video stream from the goggles. I want the OSD recorded on my video just like on analog.
If they do do that I hope it’s optional.
There probably will be a feature in the future to record OSD and then compose it over DVR footage.
@@stylesuxx Thanks for your reply and contributions to the project.
Their FAQ states that this would be very difficult because of how the video layers and focus mode work. What you could always do though is creating OSD text from blackbox data and adding that as an overlay in a video editing software. IIRC there are scripts that automate that process that even give you fancy gauges for speed and current. What developers could propably do without too much effort is writing subtitle files onto the internal storage of a Vista, just like the Air Unit does.
Use hdmi out and a capture card if you want it bad enough.
Definitely would be a cool feature if it was optional.
WOW!!! what an amazing development!!!! FINALLY!!!
THANK YOU !!!!
Thank you JB and the WTF team. Just a side question... if for some reason DJI releases a feature that interests the FPV world in a future release and we decide to apply an official release after rooting... do we just use the Bind and Power step to revert back... or once we are rooted... do we have to stay in the rooted world? Not that I expect DJI would release something worthy of potentially not having what WTF built... but was just wondering.
omg it works! it really works! thank you 10000000 times. never thought i'd see the day that i would see full osd in my dji goggles.
Great video thanks Josh for bringing this to us asap. Was wondering if there was any update on being able to record the OSD elements in either google DVR / using the digiview app? That be the real game changer, so sad we cant do this as of now.
Finally got around to this - thanks for the tutorials! Also, the reminder to donate to the project is appreciated :D
Anyone getting this error?
NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.
Been waiting for this video!
I wonder if DJI will release another firmware blocking this modification
Wow!!! Great Job devs!! I cannot wait to do this tonight.
Okay so what actually changes when you turned off custom OSD in the goggles? There was like mah, and something ae that went away.... Why were those there in the first place? I guess that's all that confused me. Great vid JB!
Also, I wonder if when the update comes to make the v2 goggles work with the O3AU, if they will lock out root or whatever 🤔
What that takes away is the few supporedt OSD elements that DJI supports over MSP, like battery voltage, GPS info and a few others. And it will be shown in DJI goggles font. Custom OSD isn't needed anymore since you have direct access to betaflgiht OSD.
More pressure to DJI to make the Goggles 2 compatible with the old air units, love it! 😂👍
Awesome! This is what fixed wing has always wanted since hd fpv! Live audio and full betaflight/Inav support❤️ Is live audio available for V2 goggles now? I heard they were working on it a while back
Yes, what about live audio? Do you need to do something extra or just this one thing and yoi get both full OSD and live audio?
Live audio is currently only available for the V1 Goggles, because we re-enabled some dormant audio code DJI had left around. This code is not present on the V2 firmware. For V1s it's actually missing from the configurator currently, but it will return soon. For the V2 Goggles someone would need to write a new audio system from scratch. There were some early experiments but latency was bad. Like half a second bad. So it's a lot of work.
@@j005u i hope you get enough support from the community so that someone wants to do the job🙏😍 Would love this feature for the V2's 🙏
Excited to test it
Unable to get this to work.. when attempting to connect to my googles i get "NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface."
Anyone else gettng this error? any idea how to fix it?
Seems the website is not quite ready yet.. if you use the "testing" url as in JBs video it works fine
Yeah me too, any fix?
Secret source: Displayport settings in the CLI... I've no idea how I would have found that out without this video!
Could have waited for the official release on the 23rd before releasing this video.
I believe that I had consent from Joonas to release this early. If he wants to make a statement about that he can.
As someome who ever only flew DJI HD this si so exciting to get all the missing features!
I'm Very sad as my DJI Goggles v2 are on 0015 😢
This is a godsend, thank you devs and JB
I wonder if DJI will take their code and finally implement it officially in their own firmware lol
Doubt it, the system is over 1 year old, and normally they have no interest in doing anything with something that is "old"
Nice Mod...have done it ...everything seems to work perfekt ....but at the air units e had some issues with restoring space 1...or 2 at the savetydevice of the unit...and had to root it 2 and 3 times...until it worked ...now the testingperiod is started....we will see !
Thanks mr Bardwell for all the googd vids and infos!! Crazy guy with crazy connections! Would love to come one day to the rampage camp.. greatings from Germany
Interesting but premature, I will wait till it's officially released and watch Madrc's stream on Friday with Joonas before risking my goggles, I can hold out for a couple more days plus by then I may see how many people brick their goggles if any.
Yeah, let's hope there are no bricks. We have so many fail-safes in place - I mean, never say never...
@@JoshuaBardwell My mistake, I thought it hadn't been released yet.
It hasn't. But it's ready to go and my video is ready to go and people have been waiting weeks for it, so here it is 😊
@@JoshuaBardwell well congratulations.
I believe that I had Joonas consent to release this early. If he decides to make a statement about that he can.
OMG - JB is a kid in a candy store! That look when it all displayed in your goggles was hilarious and classic! Someone please make a meme of that! 🤣👋
Nice, now we just need EdgeTX for the TBS Mambo, and all my wishes will be granted for christmas :)
Dang you are one lucky man, found a way to make a living doing something that's you like and looks fun. My first drone , was last seen flying northwest ... something failed . Expensive mistake , but lesson learned next venture was smaller but lacked function , by the 4th venture, full functions were realized. Since that time improvements have been made, but the project that has vexed me, has wings, and duct fans , and requires 13 of 16 channels , oh , it's a, YRF-4E. It was an experimental F4b Phantom, with cannards , it lived just up the road at WPAFB. I saw it first in 1967 or 8 , and made a decision to model it. Time with 6 kids , and money for such, well it became a retirement project. For a dozen years I have built and crashed ... went to WPAFB to capture details 2 cameras and lots of memory cards. They lost the plane, along with the staff we looked high and low. Wrote on FB about losing a prototype aircraft, gosh the airforce got mad ...lol . Yea well they didn't drag their wife around the base for hours looking for the plane. In a cranky letter , they explained it was out for paint. Several years went by and it was still out for paint. So I offered to come up and help after all I had some slightly used paint brushes out in the shed ... you know they still have no sense of humor. Now it's status is in storage . My tiny prototype flew across the yard and into the neighbors yard, ... since then every try has met with disaster, exploding fan units , failed servos, burnt wiring ...currently 3 new attempts lay about my work area, but I got old, hand and eyes ... ifvi build it , I don't trust myself to fly it. Well at least thevprototype flew, and is on rc groups ..., it was destroyed when I moved, oh well .
Great info. I like your ability to dumb down the info for us noobs to understand. I am really playing catchup at the moment and trying to crash course FPV. A sub $100 analog system opened Pandora's box for me. I am putting together a FPV trail truck to start, fast stuff later. I went full in and got a pair of Dji Googles 2 and 03 air unit. I am mounting the camera on a Motionsic B.A.G. and the vtx will be heatsinked + fans to aid cooling. Vehicle control will be handled by a Radiolink RC8X, which is head tracker compatible, and up to 800 meter range. Where I am having issues is getting the OSD functions I want. I really want vehicle speed on screen and pitch/roll would be a nice bonus as well. There doesn`t appear to be any surface specific hardware available so I am looking at drone parts. I think I need to install a flight controller and gps module to get the OSD I want so I can then also use beta flight for settings. I think I could also power the two 5v fans from the flight controller?? I have step down modules on hand if not. Any recommendations for a FC + GPS module that may serve my needs?? Any issues I may see with the RC8FG rx and FC interacting? I believe I will need to "arm" the FC to unlock the airunits powerswitching?? Obviously not a budget minded build and the chassis won`t notice the extra weight. I will have the camera system mounted and working soon, should still be a ton of fun without the OSD, but I am hoping to work out the osd.
I've been holding off on this for a while. With winter coming, this is something i'm going to do.
OMG...Yaaaaaaay.......Been waiting a long time for this......Those guys rock!!!
This is huge. I’m installing right away
Jeah nice - finally out now! Thx Joshua!!
My new v2 googles got so much better in a blink, yessss I like. 👍👍
I did not fall for DJI system and happy I waited long enough to see competitors getting on a marked (Wlaksnail and HDZero)
It is so nice to finally this basic feature right before these goggles are made obsolete!
The best news all day.
Thanks JB, this is awesome 👍😎
Just joined your PATRION thanks for your help! And very helpful videos too.
Thank you!
Thanks JB! This is so great! Let those other systems come out! I have another reason to stick with The DJI FPV System! Cheers!
I was so excited to see this notification today! …but then remembered that my goggles came on the latest firmware 😭
Great vid - looking forward to doing this along. Been researching this (since one of my FPV buddies showed off his OSD) and also felt that now it looks really easy to do.
The thing holding me off until now was DVR recording. But looks like now it works?
greets, Mario
Yes, recording works. Just OSD will not be recorded. (AFAIK recording always worked)
Yes, as noted by @bri3d (comment above), and from Ian's interview of WTF team, just camera video will be recorded in goggles DVR. Goggles hardware does not have power to re-encode video with OSD. One possible future feature is being able to do this re-encoding post-flight on a personal computer. (OSD MSP data would be saved like the DJI SRT is now)
1:54 you had me at "idiot proof" 👀
Thanks JB for taking us through this and thanks to the FPV-WTF Team.
So far I'm sticking with Digital Font, that is until you tell us the one you prefer.
I wish there was a really good high definition font that gave thinner text. For now, I can't decide which one i like the least.
@@JoshuaBardwell A few people are working on bringing font installation and selection to the configurator. Hopefully some time soon after launch. That'll make it easier to find one you like. But there's another side to this coin, which is the fact that BF doesn't yet support an HD MSP DP grid (unlike iNav and Ardu). This means while we can make the characters smaller on the SD grid, the positioning remains exactly the same. So character spacing grows in a weird way, when the font gets smaller. At one point it starts looking ridiculous. We're talking to the BF devs about solutions.
I forgot to add - todays msp-osd v0.6.3 update brings an optional "fakehd" mode which does funny things to the grid and chops it up. Parts of the screen become dead zones and the rest have a higher resolution grid available. Check it out, details in msp-osd README.
this is great, will test soon
That is Awesome! Now DJI has to think about what feature they have to give us to exclude us again with the next update. DJI your turn... O3 Air unit with Canvas Mode support? Buy new stuff to get the feature?
Great video again Mr Bardwell!
Have you ever tetsed the DLNA wireless broadcast of the DJI 2 goggles?
Cos if the latency is low enough this could allow those of us that love crazy wide FOV to make their own box style goggles with NICE BIG FOV 😁
hey joshua i have watched the video several times but i didn't get it what button or how do you enter full oad setting? ps like you did at 14:25
Knoxville, Tennesse ...represent!!!
This was one of the big reasons I chose not to buy from them. Had they simply shown that they cared, I would likely be shelling out another $100-150 per quad just for their video system. Instead, they showed me that it's better to choose small/community driven projects, even if they lack can a few things. Still happy with analog and HDZero.
Hey joshua what should I do when I'm going to put in the cli set displayport_msp_serial = allowed range -1 - 40 when I use uart 1 on my aio should I put -1 then to make this work if I had uart 2 I would have to sat uart 1 but I'm using uart 1 so I'm not fully aware of this I hope for an answer Thank you so much for doing this you're the best greetings from Norway ❤️
If you're using UART 1 then 1 - 1 = 0 so you would put 0.
Many thanks for answers love people like you who take time for people and help us who have just started with this hobby love you bardwell ❤️ because now I only get font font bin font font bin in dji goggels v2 dkal test and set display port on uart 0 as long as I I have msp on uart 1 Thank you
I’m on uart 1 I put 0 but says error in set invalid name I put set DisplayPort_msp_serial = 0
BEST BEST VIDEO ! thank you so much JB ! DJI are so bad for the hobby and are just about churning the next product.
ooh it appears that mine arte on the correct firmware for this
never updating them was a good idea
It will be fantastic to have full screen 👀 for AV-IN. I also fly some analog drones.
Rooting something definitely means something very different where I live....
SWEET! So does this mean that DJI was listening to the community? Or more so YOU and Blunty's conversation! lol
Awesome, thank you!
Another great Video Joshua ❤️💯.... Thank you so much...... Greetings from Germany 🇩🇪
Awesome now I can put a boombox on my drone, listen to my tunes while I see how quickly the 12" sub woofers are using up the battery! 😜
Great news!!! Thanks!!!
This is my first time using CLI, even though I have been using some Python and C++/Arduino for a few years now. It still took me a half hour to figure out that I had to type 'save' after entering the commands, if I wanted it to take effect. ugghh! 💀
I did root and ... no OSD. I can see that fonts are being loaded and other stuff, but no osd. Probably I've missed the SAVE command. But... Josua also missed it in tutorial I guess...? ;)
@@paw288 for sure, that is fair. Good ol' JB keeping us on our toes! But I did have same issue with my second quad, not showing OSD, after rooting. So, this was after I had already done it successfully, earlier that day. Today I re-rooted the Air Unit of the one that would not show OSD and that fixed the issue.
@@Inertia888 Just checked one of my quads - yep - SAVE solved the problem!
@@paw288 for sure i love to hear that🎯
Sweet 💕
Excellent tutorial. 👏🤓
Thats great ! Now we need a way to downgrade the GoogleV2 if you are on V01.02.0015 / V01.03.0000
Iam on 1.03 :/ so have to wait
Finally!
Very cool!
It would be cool if these guys could hack the code on DJI's GPS camera drones. Allowing people to power them with regular batteries and no longer have to buy proprietary and over priced DJI batteries. Allowing us to have full manual control on a switch. Wouldn't that be cool? Maybe even have control over whether or not DJI is sent the flight data.
Awesomeness!!!!!!!!!!!!!!!!!!!
The OSD doesn't look that good as the font is too big and low res. Also the osd doesn't go to the edges even after changing to PAL. Still this is a huge achievement by the fpv wtf team, thank you for implementing this!
The font can be changed to a smaller one, but IDK if it has an HD version.
Part of this is the size of the grid of characters that BetaFlight has implemented for the OSD overlay. ArduPilot and INAV have implemented a larger grid, so characters appear are smaller. (think BF uses ~30 characters across, where others support 50 character grid width)
Using a smaller font in BF will leave larger gaps between OSD characters, as the grid size will not have changed.
If want to know more on this topic, it was coved in Ian's interview with FPV-WTF team.
És grande moço!
Excellent work dude!
I would like meet you one day on some Rc Big Event like mine :)
Best regards
Looking forward to rooting my goggles. Will the OSD record on the goggles thou? Much needed for long range flying being able to see my GPS coordinates in the playback
It does not record. The team has said they would like to record the OSD separately, and make a tool to overlay it on the DVR.
A few notes from the root process from my experience on V01.00.0608
- close DJI assistant app! If you have it open, it will appear on COM portXX but will not start the root process.
- takes about 2-3 minutes total, goggles will reboot several times. There are 5 steps in total, and if you've done it correctly the root text should look like this:
00:02 Attempting Step 1...
00:16 - Found Device: GL150, Version: 01.00.0608
00:16 Step 1 - Success! Rebooting...
00:32 Attempting Step 2...
00:49 Step 2 - Success! Rebooting...
01:05 Attempting Step 3...
01:15 Step 3 - Success!
01:15 Attempting Step 4...
01:20 Step 4 - Success! Rebooting...
01:20 Device went away...
01:20 Device came back...
01:39 Attempting Step 5...
01:41 Device went away...
01:42 Device came back...
01:44 Step 5 - Success! Rebooting...
01:57 All done - your device has been successfully rooted!
So no problems with 608 ?
@@LCSRacing worked for me
Have any of the steps changed with the Betaflight CLI commands, since the newest Beta Flight 4.4 update? I'm getting the following error, '###ERROR IN set: INVALID NAME: displayport_msp_serial = 1###', after I enter, 'set displayport_msp_serial = 1', when typing in the second CLI command. My VTX is on UART2, and my ELRS receiver is on UART1. I was able to successfully root both Goggles V2, and my Caddx Vista, and this is the only issue I have had in the whole process. What do you think I should do? If anyone else has had this issue, please let me know what you did to resolve it. Thank you in advance for your help.
After posting this, I looked in the comments and found Joshua responded to this very issue. He has created video addressing it titled, 'Betaflight HD OSD with DJI Walksnail & HDZero // HOW TO SET UP'.
Thank you JB!!
What do I do if my msp is on uart1 because my vista is plugged in the speedybee f405 v3 plug and play module? Do I have to move it to another uart?
if it does not have inav not interested so glad walksnail has done this
My goggles are at Firmware V01.03.0000. Will there be any way in the future to root them? I really want to use the WTFOS
Thank you for the information!
HI JB
great fan from germany!
I missed something all the time about the digital HD OSD and just got it right. I had to change the font from "standart" to "digital" in the OSD tab. that and only that made the magic happen fpr me: Maybe I missed it in this video.
Happy Flying
Frank
I just completed my WTF OSD and I had to complete the Butter update. My goggles are from the DJI FPV kit. Now after completing all the updates and test flights everything worked as it should. Now today 2 days latter I went out to fly and found I had 2 sets of OSD in two different founts. I pulled the SD card out as your Video states that the OSD was on the SD card only. Still with no SD card I have OSD.
Having an issue
Config ver. 10.9.0
Firmware 4.4.2
"Set displayport_msp_serial"
Doesn't seem to still be a command??