Important Info - Donate to FPV.WTF -opencollective.com/fpv-wtf/donate?amount=10 WTFOS Configurator Link - fpv.wtf/ Betaflight Only OSD Instructions: How to Enable MSP OSD In Betaflight - Go to CLI tab to enable MSP Display Port. set osd_displayport_device = MSP set displayport_msp_serial = YOUR_UART_PORT_NUMBER - 1 save INAV and Ardupilot Instructions see github.com/fpv-wtf/msp-osd FAQ 1: V2 Goggles On V01.00.0606 In FPV Drone Mode. If your V2 goggles are showing V01.00.0606 in drone mode this is because your on VERY old original V2 firmware from before the FPV Drone actually launched. If your on this simply return to DIY FPV Mode and Root as per the video. Please support the project and donate to the FPV.WTF team for the amazing work they have done opencollective.com/fpv-wtf
Been using this and testing it for many months, have tried to tell friends how great it is and the leaps and bounds on discord the project would progress almost daily was astounding. Glad everyone now knows about it. 🙂Just wait for when the SD (as it is now) screen grid gets put into HD screen grid like Inav supports (for betaflight). Plus colored fonts lots of cool stuff
Haha you should have saw my big grin with this huge upgrade on my v1 goggles seeing the pretty blinking indicators and being able to use almost any OSD element, etc. I been waiting years for this. Love you all; donate to this amazing team!
Great info and insights. Amazing work by the FPV-WTF team. Hopefully DJI doesn't stomp on this great community focused effort. Too bad that DJI can give a node to this project, even if they can't officially support.
You are right. we spent so much money to dji. but these guys made it much more worth to use and made it also more secure according to have now lq and rssi without weird config channel tricks. we really have to send them a few bucks. really folks, wtf imagine what they did and its seems really stable now.
This is a question for Paweł Spychalski and the INAV dev team. There is a discord server linked in his videos that will help answer. Regarding the MSP setting, in INAV configuration this is a section on the Ports tab. Normally for DJI MSP is turned off. Since INAV 4.1 some DJI OSD stuff has been hidden and made automatic, so there may be more that need to be configured. (best to ask on INAV discord sever, or check for open thread on the topic)
Do you think its possible to add a microphone to a Vista for the Live Audio package? Maybe we are lucky and the pads that the mic is soldered to on the Air Units are somehow exposed/accessible on a Vista as well. Since you worked a lot with these products I figured you might be able to answer this. It would be so nice to have live audio on Vistas as well.
Thanks for your video, I have googles V2 and firmware 1.00.0606 and I'm trying on Macbook pro, but when connecting the USB cable, the page does not recognize any device like in the video, any ideas please?
great video! only thing is its not actually technically canvas mode... Canvas mode is pixel level. this is msp displayport which supports a predefined set of characters, as far as I understand. Canvas mode is decidedly different.
I dunno about that. DJI terminated all the connections with Caddx where Caddx promised canvas mode implementation. Does Caddx say they will still pursue in that development roadmap?
I am having trouble connecting to my DJI V2 goggle, USB device appearing as name Pigeon. But error message showing "NetworkError: Failed to execute 'Claiminterface' on 'USBDecice': Unable to claim interface." Tried it on 2 different PC and Mac machine and all having the same issues.
Thanks for this video. I keep meaning to do this. Is it possible to have both the Drone mode and DYI as firmware 1.00.0606. I went to both modes in the google. I update late last year early this. When I go to the assistant and the googles are in Drone mode I do see the firmware's in red available which of course I will stay away from.
Yes. I have the newest/last version of the goggles and just rooted it with an experimental version of the root from the discord. I use the analog module as well.
Does not work for inav I've tried everything I've can see my voltage so my rx tx is correct air unit and goggles on 606. No luck what,so ever. All I get is osd waiting flashing then font bin inav flash up and disappear any help would be grateful
I‘ve followed the procedure & the new layout from OSD was pretty nice. Unfortunately I can‘t switch after that anymore from old DJI FPV digital system to the O3-system in the V2 goggles. I had to upgrade refresh again V2-goggles firmware. You can choose the selection of systems or WTFOS. 😢😢😢
How do you check the Drone Mode version of the firmware? I'm in that menu and don't see it. I've NEVER connected my V2 goggles to any DJI drone. I have no need for that. Scared to plug it in to their software..lol
Hi,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
i did it! finally. rooted sicne this video came up but set the wrong port in betaflight and so wasnt getting any display. just watched again and realized my port was 2 figures less instead of 1 and viola!!!
tested yesterday on my fpv goggles v2 and love the solution. Now waiting for the flight details recording either embedded to the video or via srt file.. kudus to the developers!!
@@beeradfpv I found out that if you have 606 firmware on the fpv drone settings then it's old firmware you can flash the 606 DIY as normal it won't effect anything and you'll get it rooted
the DJI osd works now with FPV mode like the AVATA just plug in update firmware it shows all your levels automatic ???? your battery level ,, RSSI from ELRS system no need anymore for beta flight the vista runs through your FC like the AVATA all I use is RSSI and battery level and the Timer all that works thru DJI OSD like you r flying the Avata ?
I fly fixed wings and I use a monitor because I am not comfrotable flying with Googles. Is there an easy way to present digital video in a monitor? Under the previous considerations, is there any advantage on adopting digital video? Thank you.
Thanks Ian for covering this. When I switched to the DJI drone mode on my goggles V2, the firmware is V01.00.0606 (strange that it is the same as my DIY mode), and I am left with only the option to upgrade to V01.03.0000 and V01.02.0015, both seems to be the version impossible to be rooted. It seems that DJI has obsoleted the previous FPV drone firmware too. Am I out of luck?
@@MadRC Many thanks for clarifying Ian. My head was in my hands after your explanation in the video (as I'm in the same situation as BrokeMyFatStrap). I'd suggest adding an extra 'green' row to the top of the summary table to show that everything is hunky dory when both Drone & DIY firmware are V01.00.060. Thx again 🙂
@@MadRC thanks for this answer as well, I was like what's going on, both my firmwares are the same now and say 01.00.0606 what do I doooo??? Lol feel much better now
How dose the hack go with latancy dose it add heaps ? And if you wore to send out video through the usbc port dose it display the osd thruogh cosmo streemer
How can i downgrade the googles v1? I only see the curent version in dji assistant not ther earlier ones. On the airunit i see all the earlier versions
On the video description it says that iNAV is supported, but my question is, do iNAV users have to apply the following CLI commands? set osd_displayport_device = MSP set displayport_msp_serial = set vcd_video_system = PAL save
Hi,the latest firmware for the v2 goggles is v01.03.0000 and as we know is locked atm and we cannot downgrade.With this firmware the old air units,caddx vista etc.. are working?can you suggest a digital camera that works with this firmware? Thanks for your videos!
I have v01.02.001 and it will not root. Gets stuck at several places and I'm prompted to do a manual power cycle. I do and it acts as though it worked, even gets to the end and states root successful. However can go no further in the process as if it's not really rooted. They only thing I can do is root again. Stuck in a loop...
Thank you for the video! My goggles are not being recognized in nighter chrome or edge (windows 11) in device manager they appear as "CDC Serial (Interface 4) (COM4)" but in testing.fpv.wtf it says "no compatibile devices" I have v1 DJI goggles with 6060 firmware (confirmed) What am i missing? please help.
@@spikester I’ve checked the permissions several times and they are all set to be able to access the device. I can see the goggles on the dji app fine but the browsers just won’t see them. So frustrating
Thanks again for all you do. QUESTION: Do I still need to set the serial port if I updated to BF4.4, which now includes support for HD display and you can actually select MSP at the ports settings? I can get the display to show up, but the text is all shifted to the right side of the screen so anything text that is on that side if off-screen. I tried running this command but it's not a valid command in my version of BF. I'm sure I'm missing something elementary. Thanks for anyone who can help.
@@crezzlin I did get it to display correctly, but I'm not sure I "did" anything to fix it. What I did try was first allowing the goggles to fully boot up BEFORE plugging in and binding to the vista unit. Second, I shifted everything to the left side of the OSD in Betaflight to see if I could get it to fit in the screen. After that, it somehow "magically" started working and I could arrange the OSD elements all the way to both edges in Betaflight. Honestly, I think the fix was that I needed to allow the goggles to boot all the way up and let the fonts load before turning on the air unit. Good luck.
Center throttle, yaw left+pitch forward to open the menus. Use pitch stick to move up/down. Roll right to move forward (like pressing enter). Yaw left to go back to previous menu. Note: The above is true for a mode-2 radio, at least. Not sure about other modes…
is it easy to find out what firmware is on my v2's , i dont have the dji drone. do i have to put it in drone mode to find out? or does the dji config just tell me.
Hi, like some others I've managed to root the v2 goggles running v1.00.06060 (shown in both fpv and drone mode) , only I'm also unable to install wtfs - the site doesn't see the com port/USB. Tried on chrome/Edge/vivaldi to no avail.
How does this work with ardupilot? For example ardupilot already supports a limited OSD for the dji goggles. What would be the process with ardupilot to potentially get additional OSD functionality and features?
He’s talking about a different type of auto record, on this one as soon as your googles detected (connected) to your air unit it would start both recording. There is a bug though that puts vista units into low power mode regardless of auto temp control settings in the googles (present fix is to toggle the setting from on back to off and then the vista respects it).
@@testpilotian3188 No freaking way.. Do you know if this is still a bug?? I had this happen today, and exploded my hero8, a vista, a nebula pro cam, a motor, arm and a new lipo. I could not figure out why I my power setting didn't switch to 1200mw..
My Goggles v2 cannot connect to DJI Fly after it's been rooted. This may be important for people who use this goggles with DJI FPV or Avata. Does anyone has this experience? Is there a way to get around this problem?
When I click connect on the website it says ‘no compatible devices found’ I’ve allowed access to usb etc and it still won’t connect. Also tried a different PC and usb cable and still can’t connect. I’ve used chrome and edge too. Any suggestions?
I had to go into device manager (PC) and uninstall the USB driver then plug the goggles back in then it loaded a fresh driver then it connected, they have an awesome discord group as well
One question . Both modes ( FPV and DIY ) in my v2 goggles are in v01.00.0606 . Can I root them ? If yes , do I have to upgrade FPV mode to the green versions before the root ?
@@MadRC I tried to do it and I got an error message "No compatible device found". I used 3 different type C cables and nothing happend . I tried the same in air unit and I got the same message. I can hear the distinct sound from pc when I power up the goggles and air unit , but the configurator cant see them EDIT : The problem was with PC . Now it works
If read the replies to my comment’s in JB’s recent video on this very same topic, I asked the same question and here’s a response that I had from another viewer, N3W. N3W • 3 hours ago @Sam Avella i just tried my rooted goggle v1 with and not rooted airunit and it worked…. get a picture like always
I have just done the OSD mod, I am impressed and donated. But I noted the amount of donations is very low. Either people are not bothering or the FPV following is tiny. I hope the revinue picks up, $1000 is pitiful for the work done by the Devs.
I think they should put their 'donation encouragement screen' after the rooting procedure instead of before. People are more likely to donate once they see this actually works (which it does).
Each attempt ends with a message ,,Aborted! Device did not reboot in time, please power cycle and try again.,, Dji Gogles V2 FW 01.00.0606. what can I do?
I just need my battery volts ,ive tried everything.......im missing something im sure , ive done almost everything possible to my learning but no osd ......only osd waiting....amy help
I had an interesting time getting my goggles rooted. The version number initially came up as all zeros. Finally, just loaded the 10.00.0606 firmware on the DIY side of the goggles and the root went through. The FPV side of the goggles now reads 10.00.0606... I have no idea why. How do I get the OSD elements to move to the far left of the goggle scree. They seem stuck about a quarter of the way across the goggle from the left side? After changing the OSD to MSP in the CLI the option to change the camera to PAL disappeared from the OSD Tab. Anyone else seen this? I'm not sure if I changed it to PAL or not before changing the OSD in the CLI. It would be cool if BetaFlight update the OSD screen tool to reflect 16:9 MSP-OSD so its easier to set up stuff. lots of work to get LQ!
Does anyone know which firmware the V2 goggles are currently shipping with? I would assume the latest but that's not always the case with other hardware. These goggles were out of stock everywhere until recently so I guess there's not much hope to find new old stock with older firmware.
No, the V2 with the Avata are shipped with a none released FW version 01.02.0060 that’s not compatible with the root. It’s also not got drone mode either and needs to be updated to V1.3 to get everything back. However DIY Goggles V2 are still shipped with older compatible FW.
![Gucci Mane & Sexyy Red - You Don't Love Me [Official Music Video]](http://i.ytimg.com/vi/j7IBqyFKT4c/mqdefault.jpg)
Important Info -
Donate to FPV.WTF -opencollective.com/fpv-wtf/donate?amount=10
WTFOS Configurator Link - fpv.wtf/
Betaflight Only OSD Instructions:
How to Enable MSP OSD In Betaflight - Go to CLI tab to enable MSP Display Port.
set osd_displayport_device = MSP
set displayport_msp_serial = YOUR_UART_PORT_NUMBER - 1
save
INAV and Ardupilot Instructions see github.com/fpv-wtf/msp-osd
FAQ
1: V2 Goggles On V01.00.0606 In FPV Drone Mode.
If your V2 goggles are showing V01.00.0606 in drone mode this is because your on VERY old original V2 firmware from before the FPV Drone actually launched. If your on this simply return to DIY FPV Mode and Root as per the video.
Please support the project and donate to the FPV.WTF team for the amazing work they have done opencollective.com/fpv-wtf
Been using this and testing it for many months, have tried to tell friends how great it is and the leaps and bounds on discord the project would progress almost daily was astounding. Glad everyone now knows about it. 🙂Just wait for when the SD (as it is now) screen grid gets put into HD screen grid like Inav supports (for betaflight). Plus colored fonts lots of cool stuff
My wife asked me why r u smiling 😃 so much. Mad Tech made my year.
Haha you should have saw my big grin with this huge upgrade on my v1 goggles seeing the pretty blinking indicators and being able to use almost any OSD element, etc. I been waiting years for this. Love you all; donate to this amazing team!
Great info and insights. Amazing work by the FPV-WTF team. Hopefully DJI doesn't stomp on this great community focused effort. Too bad that DJI can give a node to this project, even if they can't officially support.
You are right. we spent so much money to dji. but these guys made it much more worth to use and made it also more secure according to have now lq and rssi without weird config channel tricks. we really have to send them a few bucks. really folks, wtf imagine what they did and its seems really stable now.
You are the king of FPV!
Is this working for INAV ? since the CLI commands are not accepted in INAV
This is a question for Paweł Spychalski and the INAV dev team. There is a discord server linked in his videos that will help answer.
Regarding the MSP setting, in INAV configuration this is a section on the Ports tab. Normally for DJI MSP is turned off. Since INAV 4.1 some DJI OSD stuff has been hidden and made automatic, so there may be more that need to be configured. (best to ask on INAV discord sever, or check for open thread on the topic)
See @reply to Flore Flyer's similar question below. The advise is to "select HDZero VTX and use HD mode in the osd section"
Bardwell stated in his livestream today that it works with INAV
@@msaunders300 maybe, but it did not work for me. The CLI commands are not accepted in INAV. I have to see what I'm missing
Do you think its possible to add a microphone to a Vista for the Live Audio package? Maybe we are lucky and the pads that the mic is soldered to on the Air Units are somehow exposed/accessible on a Vista as well. Since you worked a lot with these products I figured you might be able to answer this.
It would be so nice to have live audio on Vistas as well.
This is insane! I didn't fly much for several months but I got some new motivation!
Thanks for your video, I have googles V2 and firmware 1.00.0606 and I'm trying on Macbook pro, but when connecting the USB cable, the page does not recognize any device like in the video, any ideas please?
Would truly appreciate a ardupilot focused tutorial and content on this too 🙏🙏🙏
works like a charm - nice work devs! My V1 goggles look like they have many more years of service left in em!
Great run-though Ian!
Now... where's that >13km unlock package to install... 🤔
great video! only thing is its not actually technically canvas mode... Canvas mode is pixel level. this is msp displayport which supports a predefined set of characters, as far as I understand. Canvas mode is decidedly different.
I dunno about that. DJI terminated all the connections with Caddx where Caddx promised canvas mode implementation. Does Caddx say they will still pursue in that development roadmap?
@@kibbycabbit huh?
Excellent video, Ian! Thanks for the tutorial! 😃
Stay safe there with your family! 🖖😊
How about reliability of the software. Speaking of rooting for Cinelifters ? Any glitches or bugs beeing eported so far?
Hello. Amazing video simple and complete. Can I adjust the odd elements in the Betaflight odd section adding or removing? Thank you
Another great video Ian, I’m not too fussed about the OSD, but audio from air unit would be amazing.
I am having trouble connecting to my DJI V2 goggle, USB device appearing as name Pigeon. But error message showing "NetworkError: Failed to execute 'Claiminterface' on 'USBDecice': Unable to claim interface." Tried it on 2 different PC and Mac machine and all having the same issues.
I had this issue. Using a tool called Zadig to switch the usb driver from libusb0 to WinUsb solved the issue.
Thanks for this video. I keep meaning to do this. Is it possible to have both the Drone mode and DYI as firmware 1.00.0606. I went to both modes in the google. I update late last year early this. When I go to the assistant and the googles are in Drone mode I do see the firmware's in red available which of course I will stay away from.
This is unbelievable! Thanks Ian!
hi mad, i want to ask. can I still use the analog module on DJI Goggles v2 after rooting?
Yes. I have the newest/last version of the goggles and just rooted it with an experimental version of the root from the discord. I use the analog module as well.
First Thanks for your Videos! -So if you have some hacked and some not will they work together as before?
Does not work for inav I've tried everything I've can see my voltage so my rx tx is correct air unit and goggles on 606. No luck what,so ever. All I get is osd waiting flashing then font bin inav flash up and disappear any help would be grateful
Awesome! Would that by any chance will allow OSD output via the goggles video out?
I‘ve followed the procedure & the new layout from OSD was pretty nice. Unfortunately I can‘t switch after that anymore from old DJI FPV digital system to the O3-system in the V2 goggles. I had to upgrade refresh again V2-goggles firmware. You can choose the selection of systems or WTFOS. 😢😢😢
How do you check the Drone Mode version of the firmware? I'm in that menu and don't see it. I've NEVER connected my V2 goggles to any DJI drone. I have no need for that. Scared to plug it in to their software..lol
Hi,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
The link you provided, isnt that the testing link>? I think there is a public link now available. Can you please check and confirm?
i did it! finally. rooted sicne this video came up but set the wrong port in betaflight and so wasnt getting any display. just watched again and realized my port was 2 figures less instead of 1 and viola!!!
Got it working and contributed. Thanks Mad!
tested yesterday on my fpv goggles v2 and love the solution. Now waiting for the flight details recording either embedded to the video or via srt file.. kudus to the developers!!
This all works on ardupilot, confirmed? Port selection could be a trick, depending on your FC?
I'm a little confused, as I have 01.00.0606 in both drone and in diy mode?. What am I missing?
Ta for the info, is it possible to get the OSD on the usb-c out feed with this mod by any chance?
How do I check which firmware I have in drone mode?.. When I check it shows the 606 version which I have on the DIY version
Curious on this as well
@@beeradfpv I found out that if you have 606 firmware on the fpv drone settings then it's old firmware you can flash the 606 DIY as normal it won't effect anything and you'll get it rooted
I ❤ this hobby 😊
I love this and I contributed $ today! Thanks WTF devs. Hoping it works on Inav too
my dji v2 googles i bought last year has version 1.00.0600 am i still good, or do i need to upgrade slightly? I never upgraded them.
the DJI osd works now with FPV mode like the AVATA just plug in update firmware it shows all your levels automatic ???? your battery level ,, RSSI from ELRS system no need anymore for beta flight the vista runs through your FC like the AVATA all I use is RSSI and battery level and the Timer all that works thru DJI OSD like you r flying the Avata ?
I fly fixed wings and I use a monitor because I am not comfrotable flying with Googles.
Is there an easy way to present digital video in a monitor?
Under the previous considerations, is there any advantage on adopting digital video?
Thank you.
Thanks Ian for covering this. When I switched to the DJI drone mode on my goggles V2, the firmware is V01.00.0606 (strange that it is the same as my DIY mode), and I am left with only the option to upgrade to V01.03.0000 and V01.02.0015, both seems to be the version impossible to be rooted. It seems that DJI has obsoleted the previous FPV drone firmware too. Am I out of luck?
No just root off that. Your on a few older V2 firmware. Your fine.
@@MadRC great thank you!
Same. phew, glad we can root and fix our goggles.
@@MadRC Many thanks for clarifying Ian. My head was in my hands after your explanation in the video (as I'm in the same situation as BrokeMyFatStrap). I'd suggest adding an extra 'green' row to the top of the summary table to show that everything is hunky dory when both Drone & DIY firmware are V01.00.060. Thx again 🙂
@@MadRC thanks for this answer as well, I was like what's going on, both my firmwares are the same now and say 01.00.0606 what do I doooo??? Lol feel much better now
How dose the hack go with latancy dose it add heaps ? And if you wore to send out video through the usbc port dose it display the osd thruogh cosmo streemer
Hi I am on 102020 I am able to download however they have removed access to the lower firmware version when plugging into dji"s ass anyway to resolve?
Great video, finally it’s here 🎉
Great stuff. This really makes DJI look a bit like a bunch of muppets I have to say.
How can i downgrade the googles v1? I only see the curent version in dji assistant not ther earlier ones. On the airunit i see all the earlier versions
On the video description it says that iNAV is supported, but my question is, do iNAV users have to apply the following CLI commands? set osd_displayport_device = MSP
set displayport_msp_serial =
set vcd_video_system = PAL
save
No there are separate instruction for Inav. You need to follow what’s on the wiki here github.com/fpv-wtf/msp-osd
@@MadRC Thanks, I will check it out! Cheers!
How do I get to the menu that is at 12:09? I cant figure it out at all.
Hi,the latest firmware for the v2 goggles is v01.03.0000 and as we know is locked atm and we cannot downgrade.With this firmware the old air units,caddx vista etc.. are working?can you suggest a digital camera that works with this firmware?
Thanks for your videos!
Can you still do this if your using soft serial?
Yes but I have heard mixed results with OSD reliability. Some say it works ok.
got it and contributor. Throttle position not working for me (V2/ AU)
Hi Ian Im still waiting for Part 2 of the diatone roma hdzero setup.is there a new Video?
Thank you WTF! Thank you Mads Tech!
I did all this a few times, but get a message bottom right "OSD waiting" ?????
I have v01.02.001 and it will not root. Gets stuck at several places and I'm prompted to do a manual power cycle. I do and it acts as though it worked, even gets to the end and states root successful. However can go no further in the process as if it's not really rooted. They only thing I can do is root again. Stuck in a loop...
This is awesome .
Does anybody know how the fan speed mod can be configured?
Did they remove the third party packages section? I've been searching for it all over the wiki but cant find it
I connected to COM7 to root goggles V2 and nothing happened. No warnings or any instructions to try.
Thank you for the video! My goggles are not being recognized in nighter chrome or edge (windows 11) in device manager they appear as "CDC Serial (Interface 4) (COM4)" but in testing.fpv.wtf it says "no compatibile devices"
I have v1 DJI goggles with 6060 firmware (confirmed) What am i missing? please help.
I have exactly the same issue 😢
The rooting failed? If you cant install WTFOS retry the rooting first.
Thats if this isn't some device permissions issue of course, those are usually easy to deal with.
@@spikester I’ve checked the permissions several times and they are all set to be able to access the device. I can see the goggles on the dji app fine but the browsers just won’t see them. So frustrating
I had the same issue, deleting the com port had no effect. Eventually it worked after removing sd card from goggles and swapping to another usb port.
I wonder if this will compatible with Ardupilot
Thanks again for all you do.
QUESTION: Do I still need to set the serial port if I updated to BF4.4, which now includes support for HD display and you can actually select MSP at the ports settings? I can get the display to show up, but the text is all shifted to the right side of the screen so anything text that is on that side if off-screen. I tried running this command but it's not a valid command in my version of BF. I'm sure I'm missing something elementary. Thanks for anyone who can help.
Same problem here,, Did you find a fix? Thanks
@@crezzlin I did get it to display correctly, but I'm not sure I "did" anything to fix it. What I did try was first allowing the goggles to fully boot up BEFORE plugging in and binding to the vista unit. Second, I shifted everything to the left side of the OSD in Betaflight to see if I could get it to fit in the screen. After that, it somehow "magically" started working and I could arrange the OSD elements all the way to both edges in Betaflight. Honestly, I think the fix was that I needed to allow the goggles to boot all the way up and let the fonts load before turning on the air unit. Good luck.
Great video.. never flown analog so new to full BF OSD. How do you navigate the menus such as you do at 12:11
Center throttle, yaw left+pitch forward to open the menus.
Use pitch stick to move up/down.
Roll right to move forward (like pressing enter).
Yaw left to go back to previous menu.
Note: The above is true for a mode-2 radio, at least. Not sure about other modes…
@@abertheham gonna try this today. Thank you.
@@abertheham works like a charm thank you
@@Xavier-wo6ce happy to help!
Great video. nice it works on Betaflight...
Does it work on INAV also?
Yes there is instructions for it on the wiki
Is it now possible to fly past the 13km hard limit with FPV.WTF firmware?
I feel like the walksnail system seems like it has nothing else to offer now. DJI Vista with the WTFOS is a clear winner now.
From what I've heard, Walksnail also offers range beyond 13km, unlike DJI.
@@captainmarcin6105 Who flies beyond 13km ? This is a very small group of flyers
@@captainmarcin6105 For multi-rotor, it's not an easy feat to accomplish 26km round trip.. unless you fly fixed wing
is it easy to find out what firmware is on my v2's , i dont have the dji drone. do i have to put it in drone mode to find out? or does the dji config just tell me.
What does it look like on DVR recorded videos? Do they come OSD burn-in?
My question is already answered in 13:40 :)
Hi can I use the dji goggles V2 with the dji fpv drome after the goggles is rooted?
Hi, like some others I've managed to root the v2 goggles running v1.00.06060 (shown in both fpv and drone mode) , only I'm also unable to install wtfs - the site doesn't see the com port/USB. Tried on chrome/Edge/vivaldi to no avail.
Does it work in Betaflight 4.2.0?
How does this work with ardupilot? For example ardupilot already supports a limited OSD for the dji goggles. What would be the process with ardupilot to potentially get additional OSD functionality and features?
Ardupilot already supports MSP canvas OSD as well. There will be new fonts coming for this soon but you can use it in compatibility mode.
I have 01.02.0015 and v01.00.0606 in my goggles v2.. can i root it with wtf? Thanks in advance ..
Apparently not.
12:44 wait auto recording doesnt work by default? like when we arm and disarm it wont record like the stock goggles did?
He’s talking about a different type of auto record, on this one as soon as your googles detected (connected) to your air unit it would start both recording. There is a bug though that puts vista units into low power mode regardless of auto temp control settings in the googles (present fix is to toggle the setting from on back to off and then the vista respects it).
@@testpilotian3188 No freaking way.. Do you know if this is still a bug?? I had this happen today, and exploded my hero8, a vista, a nebula pro cam, a motor, arm and a new lipo. I could not figure out why I my power setting didn't switch to 1200mw..
How to flash if the newest version V2 is V01.04.0000?
weird my v2 says found gl 170 01.02.000 didnt work. booted in dji diy menu
Hello sir, is the root working if the v2 goggles are on firmware v01.00.0607?
My Goggles v2 cannot connect to DJI Fly after it's been rooted. This may be important for people who use this goggles with DJI FPV or Avata. Does anyone has this experience? Is there a way to get around this problem?
When I click connect on the website it says ‘no compatible devices found’ I’ve allowed access to usb etc and it still won’t connect. Also tried a different PC and usb cable and still can’t connect. I’ve used chrome and edge too. Any suggestions?
I had to go into device manager (PC) and uninstall the USB driver then plug the goggles back in then it loaded a fresh driver then it connected, they have an awesome discord group as well
One question . Both modes ( FPV and DIY ) in my v2 goggles are in v01.00.0606 . Can I root them ? If yes , do I have to upgrade FPV mode to the green versions before the root ?
No you should be ok just root as they are in DIY.
@@MadRC Thanks , I'll try
@@MadRC I tried to do it and I got an error message "No compatible device found". I used 3 different type C cables and nothing happend . I tried the same in air unit and I got the same message. I can hear the distinct sound from pc when I power up the goggles and air unit , but the configurator cant see them EDIT : The problem was with PC . Now it works
Do have to root all vista & air units or can you just do with one to test in out?
You can just do one to test that one.
If read the replies to my comment’s in JB’s recent video on this very same topic, I asked the same question and here’s a response that I had from another viewer, N3W.
N3W • 3 hours ago
@Sam Avella i just tried my rooted goggle v1 with and not rooted airunit and it worked…. get a picture like always
I have just done the OSD mod, I am impressed and donated. But I noted the amount of donations is very low. Either people are not bothering or the FPV following is tiny. I hope the revinue picks up, $1000 is pitiful for the work done by the Devs.
I think they should put their 'donation encouragement screen' after the rooting procedure instead of before. People are more likely to donate once they see this actually works (which it does).
What if I use a whoop to blow air on the Vista? 🤔
Haha it’s not a bad idea.
Wat is the temp and voltage reading on the side ...and can I move or remove it
Not yet but in the future.
@@MadRC it's now been removed in the latest update, but you can add it back in the CLI apparently.
Each attempt ends with a message ,,Aborted! Device did not reboot in time, please power cycle and try again.,, Dji Gogles V2 FW 01.00.0606.
what can I do?
I just need my battery volts ,ive tried everything.......im missing something im sure , ive done almost everything possible to my learning but no osd ......only osd waiting....amy help
Have you done it on both parts of the system ?you need to follow the same msposd setup as for HDZero and Avatar
I have new dji fpv in settings/about I see aircraft/headset firmware 1.02.00.00. I don’t see drone mode firmware or diy firmware anywhere
That is drone mode. You switch to diy mode by going to the device screen and scrolling down.
How do you get into the bf menu on the goggles?
Thank you!!
merci pour le travail
Does it work in Inav?
The CLI commands don't work on INAV. Is there another way to get this working in INAV ? thank you
You will need to follow what ever the process is for Inav. Those instructions are Betaflight.
@@MadRC thank you, I've follow the INAV instructions and it worked
Does this work only with Beta flight FC? Thanks
It will work with anything that supports MSP-DP. There is some quirks with Inav and Ardu and that are being worked on now n
I had an interesting time getting my goggles rooted. The version number initially came up as all zeros. Finally, just loaded the 10.00.0606 firmware on the DIY side of the goggles and the root went through. The FPV side of the goggles now reads 10.00.0606... I have no idea why.
How do I get the OSD elements to move to the far left of the goggle scree. They seem stuck about a quarter of the way across the goggle from the left side?
After changing the OSD to MSP in the CLI the option to change the camera to PAL disappeared from the OSD Tab. Anyone else seen this? I'm not sure if I changed it to PAL or not before changing the OSD in the CLI.
It would be cool if BetaFlight update the OSD screen tool to reflect 16:9 MSP-OSD so its easier to set up stuff.
lots of work to get LQ!
how to open window betaflay on OSD
So...??? No Options for iNav?? any one using iNav is a SOL???
Does this work with KISS as well?
I believe Ultra does.
why does mine only show some part of the osd? for example my LQ GPS SAT and others arent showing in the dji goggle
Have you configured it in Betaflight.
@@MadRC yes I have
@@MadRC I can see the betaflight osd but it just that some features like the LQ and GPS satellites doesn’t show in the goggle
i have the same problem, how did you fix it?
Does anyone know which firmware the V2 goggles are currently shipping with? I would assume the latest but that's not always the case with other hardware. These goggles were out of stock everywhere until recently so I guess there's not much hope to find new old stock with older firmware.
No, the V2 with the Avata are shipped with a none released FW version 01.02.0060 that’s not compatible with the root. It’s also not got drone mode either and needs to be updated to V1.3 to get everything back. However DIY Goggles V2 are still shipped with older compatible FW.
@@MadRC That's good to know! Thank you, sir!