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!
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.
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
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... :-)
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.
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.
i'm so lost!!! i've been following the whole video! was on the right firmware for my v2, rooted, updated v2 to newst firm wear like you said to do and reinstalled wtfos. but how are you still on 606 after updating??? 8:52 mines saying the new updated version
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.
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.
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.
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
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.
Hi Joshua,thanks for the guide,it was all easy to follow. I have a digital drone with crossfire receiver,but after doing and buyng the procedure,i have the link quality item in the osd flashing,as i have no signal,when can i do? thank you si hearth
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?
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 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.
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!!
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! 🖖😊
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.
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.
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
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.
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.
So I am one of the few that has the dji fpv drone. I did get on the dji assistant and it shows I’m on the 0015 firmware. There is a video on downgrading. Is that a legit option?
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.
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
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.
Hi Joshua, in the ports tab for me, no ports had msp checked on, and uart 3 was missing, i tried manually turning uart 4 on, typed your script and the 'displayport_msp_serial = 3' script didn't work. It wouldn't even show the 'serial' option. Now my betaflight isn't really working when I connect to my drone, it won't even load the ports. could i please have some help? this is so time consuming and I have no idea what I've done wrong.
Thank you so much for this tutorial! In my current Betaflight (Configurator: 10.9.0 Firmware: 4.4.2) there is no command "set displayport_msp_serial". Is this step (10:19) still necessary?
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!
Hey Joshua, I update my DJI V2 to version 0606 (is the correct fimware ) but I can't ROOT my goggles since it gives me an error in step 3. I did the virification that you did in DJI Assistant and everithing that you did but the problem still there. Any help ? Thanks for this great video.
hey JB, can you ask the devs if there is any way to "remove" the 13km range cap? maybe it is something that is inherit of the protocol design and cant be changed but... maybe they can?
why do you need betaflight OSD on my I flight drone connects like the Avata I see all the same rssi and battery like the avata or i can use beta flight it all just starting working out of nowhere even the timer is working now like the avata but what's the difference I have double readings now 2 battery levels 2 signal levels from my ELRS transmitter with skystar hd pro 7 although I like the double readings n each side works good
Great video thanks so much! When you rooted the vista, do you plug the USB cable into the flight controller board or directly into the vista video controller?
@@JoshuaBardwell thank you. I'm gonna join your patreon. I have been meaning to for so long lol. Keep up the good work mate 👍 The firmware update on the v2 goggles in order to bind to the o3 I meant, does that affect the 1200mw mod? I'm building a supafly sync mode new quad and its fits the o3 beautifully
The firmware update is for the Vista, not the V2 goggles. it makes the Vista compatible with the Goggles 2 and not compatible with the V2 goggles. After that point, the old naco hacks don't work, but the ham_cfg hack that works on Avata and O3 now also works on Vista.
Hello, I do not get on at minute 10:00. the command: "set displayport_msp_serial = 0" does not work. no matter what number I enter. For me, under Ports -> Configuration/MSP is enabled under UART1. I have Betaflight 4.4.1. please help me.
my goggles are showing me i have version 1.00.0607 , does this mean i am locked out of the wtf os root? this whole switch over to where i need to be for use with the 03 is just insane and frustrating
Awesome Video! I had a question, This worked on 1 out of 3 of my drones. The step that I'm having trouble with would be when in CLI setting up the (set displayport_msp_serial ) SERIAL option will not come up. If working correctly I would use set displayport_msp_serial = 0 as I did on the drone that did work. Any one have advice?
Followed directions, got WTFOS installed on my goggles (V1) and air unit. Set BF settings, got my OSD setup, and now when I plug in all I get it a message at the bottom right that reads "OSD WAITING"...... nothing else. Thoughts?
@@derelictfpv Was having issues with a lot of software at that time. Did an update on my OS and then things worked. Not sure, but I was having repeat crash issues with Solidworks and MasterCam at the time too. Seems to all work after windows update.
I can't get usb to connect to the cofiguarator. chrome, mac m1, usb settings in chrome are on, not devices. I use chrome and esc config to update escs so that aspect works, and the goggles and air units connect to dji fpv app. Just nothin on mac with m1...
I have an error when installing the osd on the air unit. I put version V01.00.0608 on the vista. When I want to downgrade to V01.00.0606 on the vista, impossible I no longer have access to anything on DJI assistant 2. Any idea?
So after rooting like in the video, will we have the audio or is that a separate mod? I miss the audio so much. I flew the DJI FPV Drone with audio and it worked really well. Was so nice to be able to hear what the drone is doing at distance.
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)
Does this osd to have it all in DJI goggles have to do if the FC has or not the osd chip set? Most of them have it but for example the t-motor f7 HD doesn't have it.. will it work with it? I just bought all the best T-motor parts FC f7 Pro (with WiFi Bluetooth etc) the F55A pro and f60pro motors...the weirdest thing happened...i carefully soldered the motors and battery and i tested the drone without add the DJI air unit And it was flying perfect...the only thing I had was to add with the plug n play harness the unit And have video....but then proof smoke came out... I was shocked I rechecked And nothing was touching anything or any naked wire.... finally I noticed that the plug caused it cause the plug in the 5th wire was burned and got black from the heat...i didn't wait to tell the Chinese store and I bought almost double price the same ESC cause the other was dead and now the drone powers up but that plug for the air unit isn't working as the rest of the pads which I could solder it at least....some regulator is dead and on the FC... WiFi and the pads from the side where the crossfire reciever is connected is working... so I can fly but without air unit or any camera....what can I do is this repairable? I mean this small part on the FC which caused me this damages and I so disappointed and frustrated i had to buy new ESC from local store 128euros when from Chinese store I got it 78usd... also now I can't fly without camera....can I replace from other t-motor f7 HD the regulator to maybe fix it cause I can't wait any longer to fly and the store isn't reply fast....i should get refund for the ESC and at least re-send me a new FC pro again cause they have it the cheapest in the world too...67usd when in other stores I see it around 100usd or more.....
I am super stuck. I was able to get some betaflight text to pop up on my OSD while powering on, but once it completes the power on I get no betaflight OSD. The real issue is that according to my RC I'm bound and have signal but I get no response from the quad in or out of betaflight. I'm not sure where I went wrong so I'm not sure what to reset. All I want is to be able to monitor my LQ...
Hey @joshua Bardwell Can you use this if you're running something like the eichine analog adaptor to dji goggles? I'm currently using my dji goggles with an analog drone.
Great video JB very informative, I am very new to this hobby and have a problem I need help with. I bought the new DJI O3 air unit, Goggles V2 & RC 2. I have updated the firmwares to current on all modes in the goggles, air unit and the controller. When trying to bind them all, I can see the O3 in the goggles but not the RC. The FC/ESC is T-Motor F7 HD (DJI version) I bought from RDQ. I cannot get my RC 2 to bind and i am getting a message saying that the firmware for the RC is too early an i need to update it using Assistant CD. I dont know what else to do. Ive been itching to fly my quad to get some experience.
@Joshua Bardwell - trying to connect my goggles to FPV.WTF, but I am getting "No compatible device found" error. goggles can be detected by DJI FPV app and was updated to 0606 version per your video
Hello, I have a problem going from analog to digital OSD to Google 2, and I put analog to drone again and I have no way to go back to zero OSD in my fatshark. An advice please. Thank you
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.
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.
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.
Thanks! So much for making this video, it really helped me out!
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.
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
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.
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.
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.
I'm using rooted goggles for 2+ months and it is becoming better and better.
i'm so lost!!! i've been following the whole video! was on the right firmware for my v2, rooted, updated v2 to newst firm wear like you said to do and reinstalled wtfos. but how are you still on 606 after updating??? 8:52 mines saying the new updated version
At the time I did this 0606 was the latest.
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.
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?
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.
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.
Such a great hack. Huge thanks to FPVWTF and Bardwell for sharing.
Why now, tho? Ugh. DJI should have done this 2 years ago.
Hows it going Bardwell. It looks like osd_displayport_device set to MSP has been removed in BF 4.4.
Any suggestions on how to go about this now?
Check the how to I posted to my channel Monday.
Anyone getting this error?
NetworkError: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface.
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.
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?
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
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.
I've been waiting a long time for this and I'm so glad it's here! I will be contributing to the project
I wonder if DJI will release another firmware blocking this modification
Hi Joshua,thanks for the guide,it was all easy to follow.
I have a digital drone with crossfire receiver,but after doing and buyng the procedure,i have the link quality item in the osd flashing,as i have no signal,when can i do?
thank you si hearth
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?
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 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.
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!!
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! 🖖😊
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.
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.
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
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.
Secret source: Displayport settings in the CLI... I've no idea how I would have found that out without this video!
I'm Very sad as my DJI Goggles v2 are on 0015 😢
Finally got around to this - thanks for the tutorials! Also, the reminder to donate to the project is appreciated :D
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"
Thanks!
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 🙏
So I am one of the few that has the dji fpv drone. I did get on the dji assistant and it shows I’m on the 0015 firmware. There is a video on downgrading. Is that a legit option?
If you have the 0015 firmware, there is currently no path to root. You're just out of luck at this time.
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.
Having an issue
Config ver. 10.9.0
Firmware 4.4.2
"Set displayport_msp_serial"
Doesn't seem to still be a command??
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.
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.
Thanks
As someome who ever only flew DJI HD this si so exciting to get all the missing features!
WOW!!! what an amazing development!!!! FINALLY!!!
THANK YOU !!!!
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.
Hi Joshua, in the ports tab for me, no ports had msp checked on, and uart 3 was missing, i tried manually turning uart 4 on, typed your script and the 'displayport_msp_serial = 3' script didn't work. It wouldn't even show the 'serial' option. Now my betaflight isn't really working when I connect to my drone, it won't even load the ports. could i please have some help? this is so time consuming and I have no idea what I've done wrong.
Thank you so much for this tutorial! In my current Betaflight (Configurator: 10.9.0 Firmware: 4.4.2) there is no command "set displayport_msp_serial". Is this step (10:19) still necessary?
If using Betaflight 4.4 then the instructions have changed. The simplest thing is to load the OSD preset from the presets tab.
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
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
How do I see the full osd menu like jb has towards end of video
I've been holding off on this for a while. With winter coming, this is something i'm going to do.
Hey Joshua, I update my DJI V2 to version 0606 (is the correct fimware ) but I can't ROOT my goggles since it gives me an error in step 3. I did the virification that you did in DJI Assistant and everithing that you did but the problem still there.
Any help ? Thanks for this great video.
hey JB, can you ask the devs if there is any way to "remove" the 13km range cap? maybe it is something that is inherit of the protocol design and cant be changed but... maybe they can?
They say that is in the list.
there was someone on youtube working on that , cant find his channel
Wow!!! Great Job devs!! I cannot wait to do this tonight.
why do you need betaflight OSD on my I flight drone connects like the Avata I see all the same rssi and battery like the avata or i can use beta flight it all just starting working out of nowhere even the timer is working now like the avata but what's the difference I have double readings now 2 battery levels 2 signal levels from my ELRS transmitter with skystar hd pro 7 although I like the double readings n each side works good
Great video thanks so much! When you rooted the vista, do you plug the USB cable into the flight controller board or directly into the vista video controller?
Directly into the Vista.
@@JoshuaBardwell thanks. I have firmware 607 and apparently it doesn’t play nice with FOVWTF hacks? Can I update too 608 to be able too root safer?
I believe 607 can be rooted the same as 606 have you tried?
Bear in mind you need to be checking version with the goggles in DJI FPV drone mode.
@@JoshuaBardwell thanks so much for your help! I just joined your Patreon as a means of thanking you for your help.
I'm stuck at the end to type the cli with serial = # doesn't work on 4.4
ua-cam.com/video/Kti-6lWcJQU/v-deo.html
Does this work with goggles 2 as well or just the fpv goggles 2?
Goggles 2 don't need this because they support OSD natively. But no, there's no root for them.
Will doing this affect the mod to increase output power? Same for doing the update on them to pair with the o3 unit? I have the v2 goggles
No it doesn't affect the 1200 mW hack at all. It also doesn't affect compatibility withj O3.
@@JoshuaBardwell thank you. I'm gonna join your patreon. I have been meaning to for so long lol. Keep up the good work mate 👍
The firmware update on the v2 goggles in order to bind to the o3 I meant, does that affect the 1200mw mod? I'm building a supafly sync mode new quad and its fits the o3 beautifully
The firmware update is for the Vista, not the V2 goggles. it makes the Vista compatible with the Goggles 2 and not compatible with the V2 goggles. After that point, the old naco hacks don't work, but the ham_cfg hack that works on Avata and O3 now also works on Vista.
Hello, I do not get on at minute 10:00. the command: "set displayport_msp_serial = 0" does not work. no matter what number I enter. For me, under Ports -> Configuration/MSP is enabled under UART1. I have Betaflight 4.4.1. please help me.
The instructions changed in 4.4. ua-cam.com/video/Kti-6lWcJQU/v-deo.html
###ERROR IN set: INVALID NAME: displayport_msp_serial = 0###
THE INSTRUCTIONS CHANGED IN 4.4 GO WATCH THE VIDEO I LINKED YOU ABOVE IT HAS THE UPDATED INSTRUCTIONS.
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!
my goggles are showing me i have version 1.00.0607 , does this mean i am locked out of the wtf os root? this whole switch over to where i need to be for use with the 03 is just insane and frustrating
If you're using the O3 you don't need root. If your firmware has locked you out, look up "FPV.wtf butter" which is a tool to roll back your firmware.
@@JoshuaBardwell appreciated 🙏
You are the King JB, never getting tired of listening to you 🤗
got everything working, just don't know how to access this menu 14:26? thanks in advance!
Center throttle yaw left pitch forward.
@@JoshuaBardwell thanks a lot!
Ok my problem is I don't have video format options. At 10:29 you don't have it either then at 11:26 you do have it. Was it because of the preset?
How to Enable MSP OSD In INAV? I can't get it to work in INAV because the CLI commands are not accepted in INAV. What I'm missing?
Awesome Video! I had a question, This worked on 1 out of 3 of my drones. The step that I'm having trouble with would be when in CLI setting up the (set displayport_msp_serial ) SERIAL option will not come up. If working correctly I would use set displayport_msp_serial = 0 as I did on the drone that did work. Any one have advice?
same isuue here on BF4.4 - variable "displayport_msp_serial" is not found so cannot set it. Can anyone advise please?
Followed directions, got WTFOS installed on my goggles (V1) and air unit. Set BF settings, got my OSD setup, and now when I plug in all I get it a message at the bottom right that reads "OSD WAITING"...... nothing else. Thoughts?
Figured it out. Alls well.
How did you figure this out? What did you do?
@@derelictfpv Was having issues with a lot of software at that time. Did an update on my OS and then things worked. Not sure, but I was having repeat crash issues with Solidworks and MasterCam at the time too. Seems to all work after windows update.
@@j.c.m5168 Ok thanks. My goggles and vista are rooted and wtf and osd package installed but it's not working
@@derelictfpv Did you go thru and set it up in BF per directions?
I can't get usb to connect to the cofiguarator. chrome, mac m1, usb settings in chrome are on, not devices. I use chrome and esc config to update escs so that aspect works, and the goggles and air units connect to dji fpv app. Just nothin on mac with m1...
So on a newly activated air unit Caddex vista nebula pro I must root the unit as well.
Been waiting for this video!
I have an error when installing the osd on the air unit. I put version V01.00.0608 on the vista. When I want to downgrade to V01.00.0606 on the vista, impossible I no longer have access to anything on DJI assistant 2. Any idea?
From my understanding, the audio mod only works for the V1 goggles. Any way to get audio to V2 goggles from an OG air unit?
So after rooting like in the video, will we have the audio or is that a separate mod? I miss the audio so much. I flew the DJI FPV Drone with audio and it worked really well. Was so nice to be able to hear what the drone is doing at distance.
Audio is a separate mod, but I'll release that video after Friday so as to not create any more work for the devs.
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)
Nice, now we just need EdgeTX for the TBS Mambo, and all my wishes will be granted for christmas :)
Does this osd to have it all in DJI goggles have to do if the FC has or not the osd chip set? Most of them have it but for example the t-motor f7 HD doesn't have it.. will it work with it? I just bought all the best T-motor parts FC f7 Pro (with WiFi Bluetooth etc) the F55A pro and f60pro motors...the weirdest thing happened...i carefully soldered the motors and battery and i tested the drone without add the DJI air unit And it was flying perfect...the only thing I had was to add with the plug n play harness the unit And have video....but then proof smoke came out... I was shocked I rechecked And nothing was touching anything or any naked wire.... finally I noticed that the plug caused it cause the plug in the 5th wire was burned and got black from the heat...i didn't wait to tell the Chinese store and I bought almost double price the same ESC cause the other was dead and now the drone powers up but that plug for the air unit isn't working as the rest of the pads which I could solder it at least....some regulator is dead and on the FC... WiFi and the pads from the side where the crossfire reciever is connected is working... so I can fly but without air unit or any camera....what can I do is this repairable? I mean this small part on the FC which caused me this damages and I so disappointed and frustrated i had to buy new ESC from local store 128euros when from Chinese store I got it 78usd... also now I can't fly without camera....can I replace from other t-motor f7 HD the regulator to maybe fix it cause I can't wait any longer to fly and the store isn't reply fast....i should get refund for the ESC and at least re-send me a new FC pro again cause they have it the cheapest in the world too...67usd when in other stores I see it around 100usd or more.....
my googles dont come up in the device list? but come up in assistant? any idea how to troubleshoot? thanks!
I am super stuck.
I was able to get some betaflight text to pop up on my OSD while powering on, but once it completes the power on I get no betaflight OSD.
The real issue is that according to my RC I'm bound and have signal but I get no response from the quad in or out of betaflight.
I'm not sure where I went wrong so I'm not sure what to reset.
All I want is to be able to monitor my LQ...
Hello, thank you very much for your work, but how can I reverse the process in the air unit, the dji pc apk cannot read the unit's signature
ua-cam.com/video/vubarw7BJkw/v-deo.html
@@JoshuaBardwell thanks; )
Joshua where did you get the fan from for the cooling the vista tia
I tried to root an it says
01:11 Attempting Step 3...
01:31 Failed after 10 retries.
what should i do now?
Did you check your firmware version? Are you booted to DIY mode?
Ok I figured out you can just try again. Worked for me.
Link to the video that allows us to move the default osd menu in the dji goggles v2? Because my edges are blurry. Wanna move everything inwards.
Hey @joshua Bardwell Can you use this if you're running something like the eichine analog adaptor to dji goggles? I'm currently using my dji goggles with an analog drone.
I have double everything exempt satellites. How do I add sats so I can switch fully?
Is it possible to make adjustment inside the DJI goggles 2 with O3 air unit combination like TBS Smart Audio ？
Great video JB very informative, I am very new to this hobby and have a problem I need help with. I bought the new DJI O3 air unit, Goggles V2 & RC 2. I have updated the firmwares to current on all modes in the goggles, air unit and the controller. When trying to bind them all, I can see the O3 in the goggles but not the RC. The FC/ESC is T-Motor F7 HD (DJI version) I bought from RDQ. I cannot get my RC 2 to bind and i am getting a message saying that the firmware for the RC is too early an i need to update it using Assistant CD. I dont know what else to do. Ive been itching to fly my quad to get some experience.
@Joshua Bardwell - trying to connect my goggles to FPV.WTF, but I am getting "No compatible device found" error. goggles can be detected by DJI FPV app and was updated to 0606 version per your video
Hello, I have a problem going from analog to digital OSD to Google 2, and I put analog to drone again and I have no way to go back to zero OSD in my fatshark. An advice please. Thank you
What about the audio output? You mentioned it in the beginning of the video.