A quick bump for this video in early 2021 - My Tx was on fast / Rx was normal, used SET SBUS_BAUD_FAST = ON, and now everything is working perfectly. Thank you.
If anyone is having problems doing this as of today, running Betaflight 4.2.8, things are a little different than in this video. I was about to lose my mind, and finally figured out how to change the protocol in the goggles, under the settings. I was clicking on the protocol tab, and instead of getting a list of the two protocols, i was getting a banner that would pop up saying to make sure you have the correct firmware set in betaflight, with the only option being to click the OK button. The ONLY way you can get the protocols to show you the choice of protocols, is to first do what was said in the video above... THEN go into your goggles, scroll up to the Transmission tab, and set the 50MBS to 25MBS. Then you'll likely get put into the Public channel (Channel 8) so make sure you check that and put it back into a normal channel. Then scroll back down to settings>protocols, then you should have a choice of protocols, and can choose Fast Sbus protocol. Then go back, scroll back up to Transmission tab, and change back to 50MBS. That should allow you to get it set to fast sbus, and keep it at 50mbs.
@@5zero7RC Yea man, I was really starting to lose my mind. Missed out on the one day of good weather, trying to figure it out at the spot I go fly. Two days later, I got it worked out. Still need all of your steps leading up to that part though!! So thank you!!
@@devonpolsin4850 One other user here in the comments mentioned something similar and eventually posted a fix, but that link no longer works. What error message do you get when you run that command in the CLI?
Does this only work for betaflight 4.1? I'm on betaflight 4.2 on an iflight rtf quad. I am using the DJI controller and FPV googles. Betaflight says it's on sbus but goggles only respond in normal mode. when I switch to sbus I get nothing.
It should work the same on 4.2. Have you run the cli command "set sbus_baud_fast = ON" then save and reboot? If it only works when the goggles are in normal mode, that means betaflight is using normal sbus, not fast sbus.
Hello sr I have a problem that the controll binds green light, but on recivier TB in bf nothing moves. Also in osd I se information of the controller and in calibration in googles i can move the sticks and calibrate but in servo control in googles it doesn't move either. Hope you can help me out
If I'm running Betaflight 4.1.1, I'm seeing just two options in my DJI Goggles; "NORMAL" and *"SBUS BAUD FAST"* only. No option for "DJI HDL" protocol. Am I missing something or is it because I'm using BetaFlight 4.1.1 ?
Reading through other comments looks like you already answered this. Found your previous response; "Ah, yes, thanks for pointing that out. That was a change DJI made in the recent firmware update. I like it because it helps stay consistent with Betaflight now."................. So, looks like I'm good to go...
Reading through other comments looks like you already answered this. Found your previous response; "Ah, yes, thanks for pointing that out. That was a change DJI made in the recent firmware update. I like it because it helps stay consistent with Betaflight now."................. So, looks like I'm good to go...
Thanks for the video. I just updated the firmware on my DJI FPV system and the only thing I noticed on the goggles it doesn't say DJI HDL protocol instead it says Sbus Fast protocol. I am assuming because of the latest firmware update.
Ah, yes, thanks for pointing that out. That was a change DJI made in the recent firmware update. I like it because it helps stay consistent with Betaflight now.
@@MindRiderFPV The firmware update changes the wording you see in the goggles to make it consistent with what Betaflight has in its interface. If you want to use the 7ms protocol for the radio you need to make sure both betaflight and the dji system are set to the sbus fast protocol.
5zero7 RC Ok. I have 4.1 on my IFlight DC3, DJI but I can’t see the fast protocol option in BF. Only the usual ones. Do I have to have quad and radio powered on to see that option in the scroll down menu? ( yes DJI radio)
I would like to ask about ports if you want to bind the dji remote to the megabee. Which config or serial to enable? USB VCP, UART1, UART2, UART3, UART6?
Don't change USB VCP or you will lose your ability to connect to your computer. The rest depends on your flight controller and where you wired up the radio control wires. If you have a flight controller that is designed for the DJI system, this has been predetermined for you. If you are using any other flight controller you need to look at that flight controllers documentation to see where the UARTS are, then choose one, solder the correct wires from the DJI air unit to that UART pad on the flight controller, then configure that specific UART for serial control. Hope that helps.
5zero7 RC I have issue when Im doing a test to the DJI remote to the beta flight, it doesn’t detect what I do on the remote controller. Can you check again if its correct: USB VCP: Configuration/MSP = On UART2: SerialRx = On UART3 l: Configuration/MSP = On The rest is off. Receiver: Receiver Mode: Serial Bus Receiver Serial Receiver Provider: SBUS Channel Map: TAER1234 Is this correct? Or am I missing any settings? Thanks in advance. 🙏🏻
@@AldenDiazTV Do you have the DJI system configured to use the sbus, or "Normal" protocol? Have you updated your DJI gear to the latest firmware update? Do you know the brand and model of your flight controller?
5zero7 RC hello sir, i configure it using sbus. The megabee is prebuilt by iflight so im not sure the brand of the flight controller. 🙁 All 3 dji system are updated to the latest firmware.
@@AldenDiazTV I assume your radio is bound to the air unit and you can change settings in your goggles by using the buttons on your radio? I would also suggest watching Le Drib's setup video. It might help. ruclips.net/video/mA9eAroS_6I/видео.html
So I have a Caddx Vista with the iflight succex-d mini f7. DJI radio is bound and I have battery telemetry in my DJI goggle and an image. My dji controller isn’t working though. No signal under receiver in betaflight config. I’ve tried the sbus fast mode, but betaflight 4.1.1 doesn’t have anything that say DJI or sbus fast. I turned it back off in my goggles and kept normal sbus mode under receiver in betaflight but still nothing. Any ideas?
To use sbus fast you need to enter a cli command because it is not listed in the GUI drop down. But regular sbus should also work. Have you configured which UART is connected to the radio? It may be different than what I have in this video and you may have to look that up in the manual for the FC.
I think the settings are stored in the vista or air unit on the drone. So I don't think you would have to switch, but I have never tried having one drone using the fast mode and one not using it.
I have a question, and I think I might have waste a bunch of money on this, my elevator is inverted, so when my right hand push up, my quad tilts back, and push down on my radio, my quad goes forward, how can I change that, I can just change the weight on my Taranis in the mixer page, how do I do it for this?????
Sounds like you are using the DJI radio correct? If I remember correctly, you can go into the menu in the goggles and adjust the settings for the radio. You should be able to invert the sticks there.
I'm having problems with my Titan dc5 I feel like it has no range and the transmission connection is sporadic. On the HUD the drone icon at the bottom left the bars start to drop off even 50 yards awayI checked all my connections and they're tight and good I even switch to the DJI mmcx connectors and just ran them out the side. Do you think entering in this command could have affected the connection somehow..
@@5zero7RC how do you switch back to regular when I switch back in the goggles I don't get any response out of the controller. Am I doing something wrong. I'm pretty sure I have to go into betaflight and probably set it back but wouldn't that put me back at square one with the controller not working
You have to match the protocol the DJI radio is sending with the protocol betaflight is expecting. So in this case to switch back you would go into the betaflight CLI and enter ""set sbus_baud_fast = OFF", then save and restart. Then in the DJI goggles switch back to sbus. After that you should have control working again with the normal sbus.
@@5zero7RCokay I was able to switch it back to normal and I got it to respond but the connection still drops off at about three hundred meters away down to one red bar I tested my cinewhoop back-to-back and no bars lost in the same flight pattern
@@5zero7RC thank you for your help. I changed out the fpv air unit and that had no change either. So so far I've switchedthe antennas and put it back and then the sbus bod and then put it back and then switched out the fpv air unit and it still does not have a good connection it must be the FCU
Good question. I only have one air unit so I can't test that. Maybe someone else has the answer? I wonder if that setting is saved in the air unit and switches depending on which one the radio is connected to. Hopefully that is how it works.
@@5zero7RC It's when you don't want to update an earlier version of Betaflight when the quad flys good now and the speed controller is on BLHELI that does not do rpm filtering..
I am running a T-Motor F4 HD FC with the T-Motor P60 32BIT 6S ESC and Caddx Vista HD DJI system. I have bound the caddx system to my dji goggles and my dji controller. When i run betaflight everything seems to be working but it doesnt recognize my receiver. I have done practically everything i googled with no luck. Whats weird is when i power off the receiver and turn it back on, before the receiver binds to the caddx system, betaflight responds. But once the led turns green, betaflight doesnt respond to the receiver. Any idea what the problem may be?
Do you get correct drone battery voltage in the goggles? I wonder if your radio is set to use fast sbus but betaflight is expecting regular sbus? If that is not it, then I would double check with the FC manual that the settings for the radio UART are all correct.
@Alex Ou Correct battery voltage is whatever voltage the battery is on your drone at the time. For example a fully charged 4s battery when the drone is powered on will be just under 16.8v. Yes, if you have rx2 and tx2 connected to the air unit for OSD information ( not radio control) then you need to set UART2 to be MSP. That allows data to flow back to the air unit and gets your betaflight OSD and battery voltage to the DJI goggles. If you have a Flight Controller designed for the DJI system, hopefully they have all these details and more in their manual.
Unfortunately T-motor does not appear to have a nice manual to go with that FC. However this diagram does help: en.tmotor.com/uploadfile/2019/0903/20190903095855234.jpg I see that uart 5 is indeed the one for radio control and uart 2 is for the MSP connection. Uart 4 would be used for esc data. The ESC uart won't have anything to do with your radio control or OSD information.
hi! great video - i have an challenge with my dji controller not being able to connect to betaflight, everythign is updated and green but still no movement in betaflight :( - help! PS: im running everything on a Holybro Kakute F7 HDV & Tekko32 F3 HDV 40A 4in1 ESC 30x30 Stack/Combo for DJI (with a DJI unit )
Sounds like you have the exact same stack as I do. Be sure you have the radio protocol matched. So in the goggles if you have sbus, use sbus in the FC. If you have fast sbus selected in the goggles, under device -> protocol, make sure you run the CLI command "set sbus_baud_fast = ON" and save it.
@@5zero7RC no thats not the problem :/ its something with the RXLOSS and i dont know how to fix it :/ (its my first build :) ) - PS i dont have yet the motor connected to the fc - maybe it could be because of that?
Since you are using the same components as me, maybe you can skim through this build video and find a clue that might help you figure out what might be different? ruclips.net/video/zWFeI_SN1Vk/видео.html
@@5zero7RC i did watched this video a couple of time! thanks :) the problem is with RXLOSS NOPREARM CLI MSP i just dont know how to fix it, if its fixable
I just did a quick test with mine, and that is exactly what you will see if you have the protocol mismatched. Go into your goggles, go to device, then protocol and switch it. If you have it at "normal" switch it to sbus baud fast. If you have it at sbus baud fast, switch it to normal. After that hopefully the RXLOSS status will disappear.
How do I get my voltage on kwad to read?? I just get 0.0v on kwad the googles show the voltage of battery powering goggles but I get no voltage on kwad through osd!!
That means the MSP connection between your air unit ( or vista ) and the flight controller is not working so the flight controller can't send data like voltage and OSD info to the air unit and then get passed on to your goggles. How you do that depends on your flight controller, but you need to have the grey and white wires from the air unit connected to a UART on your flight controller. Then in betaflight you need to set that UART to be MSP like I do in this video. Hope that helps!
@@5zero7RC thank you sir..... so if I’m using the air unit with crossfire control link will there be any lag in my flight characteristics? Forgive me , I just got the package yesterday and I’m trying to educate myself in a rapid fashion .....
@@endliberalism4305 The DJI video system typically has 25-30ms of lag. It will show you that in the bottom right corner of the goggles. I have not used crossfire but I believe that has 15ms or so average latency. Both are well within the range needed to fly FPV accurately.
@@5zero7RC thank you sir. I just got my Tx, Rx, air unit all updated and bound, I did the power hack for the goggles and low latency in the CLI command, everything looks good and I’m surprised everything works because when I received my goods the boxes were partially crushed after the trip from banggood , I saved about $150 purchasing it from them but Whew- close call.
@@5zero7RC Sorry, my question is about telemetry of the flight controller. I could not find any documentation about how to setup this. I tried all telemetry protocols and it didn't work
@@kerleston Since this FC is designed to work with the DJI system, the only "telemetry" data I use is what the DJI goggles can display. At this time that is only the battery voltage and if the FC is armed or not. My guess is that enabling the telemetry option on the FC does not do anything. But I'm not sure about that.
As of the December DJI firmware update DJI changed the display to show Fast SBUS to be consistent with Betaflight. Basically HDL and Fast SBUS are the same thing.
@@5zero7RC That makes so much since! I got fast sbus in my goggles but I don't see it in my config menu. (I switched back to sbus because I couldn't get any receiver response when they are different i guess). Im a newb BTW. Thanks for the quick reply (subbed)
So you just need to type that command into the CLI and switch the protocol in the Goggles? You don't need to change the settings to DJI HDL in the Receiver settings section of the Config page?
Correct. With the final release of Betaflight 4.1, you need the cli command to enable the DJI HDL or sbus fast protocol. In some of the early 4.1 release candidates HDL was in the drop down box, but that was removed. Hopefully it comes back in some future update to make this easier for beginners.
That is correct. I believe the goggles will display the video latency. The HDL protocol is just the radio transmitter link and its latency is not displayed anywhere.
@@h975 As far as I know that error means the variable you are trying to set does not exist. So there must be a typo, or you included the " or something like that.
iam about to be the one to thro this junk out I've try just about everything and looked at this video and thought it was what I needed to getting my sticks moving......but nothing I follow all the steps and nothing is happening green light on the radio all software on all three devices are updated and is a nice drone iam dying to fly from flywoo.....it's been a most frustrating experience......all devices communication seems to be OK green light everywhere picture on goggles but sticks not moving for nothing.......anyone out there please help save me from throwing this out to the trash
The important thing to remember is that the radio and betaflight have to be set the same, or they won't talk. The simple test is to change the protocol option in the goggles and see if that fixes the issue. If not, you likely have an issue with the connection between the flight controller and the DJI system. Either the wires are connected backwards, or you don't have the right UART set as the one where your radio is connected.
The HDL or sbus_baud_fast protocol is only for the DJI FPV radio right now. Crossfire uses its own fast protocol. If you have a crossfire compatible radio then you need a crossfire receiver in your drone. In that case the DJI FPV system is just like any other video transmitter. Hope that helps.
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
A quick bump for this video in early 2021 - My Tx was on fast / Rx was normal, used SET SBUS_BAUD_FAST = ON, and now everything is working perfectly. Thank you.
If anyone is having problems doing this as of today, running Betaflight 4.2.8, things are a little different than in this video. I was about to lose my mind, and finally figured out how to change the protocol in the goggles, under the settings. I was clicking on the protocol tab, and instead of getting a list of the two protocols, i was getting a banner that would pop up saying to make sure you have the correct firmware set in betaflight, with the only option being to click the OK button. The ONLY way you can get the protocols to show you the choice of protocols, is to first do what was said in the video above... THEN go into your goggles, scroll up to the Transmission tab, and set the 50MBS to 25MBS. Then you'll likely get put into the Public channel (Channel 8) so make sure you check that and put it back into a normal channel. Then scroll back down to settings>protocols, then you should have a choice of protocols, and can choose Fast Sbus protocol. Then go back, scroll back up to Transmission tab, and change back to 50MBS. That should allow you to get it set to fast sbus, and keep it at 50mbs.
Interesting. Thanks for the update. I have not tried to change the protocol in a long time.
@@5zero7RC Yea man, I was really starting to lose my mind. Missed out on the one day of good weather, trying to figure it out at the spot I go fly. Two days later, I got it worked out. Still need all of your steps leading up to that part though!! So thank you!!
Also having problems with this In beta flight 4.2 Cli will not accept the command and shows error?
@@devonpolsin4850 One other user here in the comments mentioned something similar and eventually posted a fix, but that link no longer works. What error message do you get when you run that command in the CLI?
You're amazing. I've been searching for hours on why the controller is not working and all I had to do is update the setting in the goggles
I'm curious. What setting was the default on your setup and what did you need to change it to?
typing save after entering the command is what I was missing, thanks
You a genius! I was ready to give DJI a piece of my mind! 😂 thank you so much for making this video!
Thank you very much! Your video is clear and concise. Now my CineBee works with SBUS BAUD FAST 👍You have a new subscriber! 😉Thanks!
How do you know if it is active?
Does this only work for betaflight 4.1? I'm on betaflight 4.2 on an iflight rtf quad. I am using the DJI controller and FPV googles. Betaflight says it's on sbus but goggles only respond in normal mode. when I switch to sbus I get nothing.
It should work the same on 4.2. Have you run the cli command "set sbus_baud_fast = ON" then save and reboot? If it only works when the goggles are in normal mode, that means betaflight is using normal sbus, not fast sbus.
Hello sr I have a problem that the controll binds green light, but on recivier TB in bf nothing moves. Also in osd I se information of the controller and in calibration in googles i can move the sticks and calibrate but in servo control in googles it doesn't move either. Hope you can help me out
Perfect. Thanks for this!!
Thank you, very helpful.
If I'm running Betaflight 4.1.1, I'm seeing just two options in my DJI Goggles; "NORMAL" and *"SBUS BAUD FAST"* only. No option for "DJI HDL"
protocol. Am I missing something or is it because I'm using BetaFlight 4.1.1 ?
Reading through other comments looks like you already answered this. Found your previous response; "Ah, yes, thanks for pointing that out. That was a change DJI made in
the recent firmware update. I like it because it helps stay consistent with Betaflight now."................. So, looks like I'm good to go...
Reading through other comments looks like you already answered this. Found your previous response; "Ah, yes, thanks for pointing that out. That was a change DJI made in
the recent firmware update. I like it because it helps stay consistent with Betaflight now."................. So, looks like I'm good to go...
Very helpful, thanks for sharing!
谢谢，非常有用，我一直以为大疆或者飞控开发人员放弃HDL，感谢教学，thanks！！！！！！！！！！！！！！！！！
Did this fast s-bus have any impact regarding the « flying range » ?
Not that I have noticed. But I have not pushed the range of the system to its limits with or without the 7ms latency protocol.
GOOD JOB !!!👍👍😎😎
Thanks for the video. I just updated the firmware on my DJI FPV system and the only thing I noticed on the goggles it doesn't say DJI HDL protocol instead it says Sbus Fast protocol. I am assuming because of the latest firmware update.
Ah, yes, thanks for pointing that out. That was a change DJI made in the recent firmware update. I like it because it helps stay consistent with Betaflight now.
5zero7 RC
So I don’t need to do that after the FW update?
@@MindRiderFPV The firmware update changes the wording you see in the goggles to make it consistent with what Betaflight has in its interface. If you want to use the 7ms protocol for the radio you need to make sure both betaflight and the dji system are set to the sbus fast protocol.
5zero7 RC
Ok. I have 4.1 on my IFlight DC3, DJI but I can’t see the fast protocol option in BF. Only the usual ones.
Do I have to have quad and radio powered on to see that option in the scroll down menu? ( yes DJI radio)
@@MindRiderFPV You won't see it in the drop down list. You need to enable it with the CLI command.
I would like to ask about ports if you want to bind the dji remote to the megabee. Which config or serial to enable? USB VCP, UART1, UART2, UART3, UART6?
Don't change USB VCP or you will lose your ability to connect to your computer. The rest depends on your flight controller and where you wired up the radio control wires. If you have a flight controller that is designed for the DJI system, this has been predetermined for you. If you are using any other flight controller you need to look at that flight controllers documentation to see where the UARTS are, then choose one, solder the correct wires from the DJI air unit to that UART pad on the flight controller, then configure that specific UART for serial control. Hope that helps.
5zero7 RC I have issue when Im doing a test to the DJI remote to the beta flight, it doesn’t detect what I do on the remote controller.
Can you check again if its correct:
USB VCP: Configuration/MSP = On
UART2: SerialRx = On
UART3 l: Configuration/MSP = On
The rest is off.
Receiver:
Receiver Mode: Serial Bus Receiver
Serial Receiver Provider: SBUS
Channel Map: TAER1234
Is this correct? Or am I missing any settings?
Thanks in advance. 🙏🏻
@@AldenDiazTV Do you have the DJI system configured to use the sbus, or "Normal" protocol? Have you updated your DJI gear to the latest firmware update? Do you know the brand and model of your flight controller?
5zero7 RC hello sir, i configure it using sbus. The megabee is prebuilt by iflight so im not sure the brand of the flight controller. 🙁 All 3 dji system are updated to the latest firmware.
@@AldenDiazTV I assume your radio is bound to the air unit and you can change settings in your goggles by using the buttons on your radio? I would also suggest watching Le Drib's setup video. It might help. ruclips.net/video/mA9eAroS_6I/видео.html
So I have a Caddx Vista with the iflight succex-d mini f7. DJI radio is bound and I have battery telemetry in my DJI goggle and an image. My dji controller isn’t working though. No signal under receiver in betaflight config. I’ve tried the sbus fast mode, but betaflight 4.1.1 doesn’t have anything that say DJI or sbus fast. I turned it back off in my goggles and kept normal sbus mode under receiver in betaflight but still nothing. Any ideas?
To use sbus fast you need to enter a cli command because it is not listed in the GUI drop down. But regular sbus should also work. Have you configured which UART is connected to the radio? It may be different than what I have in this video and you may have to look that up in the manual for the FC.
Are there any drawbacks to doing this in Betaflight?
Nope, there are no downsides that I know of.
@@5zero7RC Cool, thanks for the reply. I’m changing them all then!
Do you have to do this with all quads or do u have to switch back and forth for the ones that are not updated the DHL
I think the settings are stored in the vista or air unit on the drone. So I don't think you would have to switch, but I have never tried having one drone using the fast mode and one not using it.
@@5zero7RC Thanks for sharing :)
I have a question, and I think I might have waste a bunch of money on this, my elevator is inverted, so when my right hand push up, my quad tilts back, and push down on my radio, my quad goes forward, how can I change that, I can just change the weight on my Taranis in the mixer page, how do I do it for this?????
Sounds like you are using the DJI radio correct? If I remember correctly, you can go into the menu in the goggles and adjust the settings for the radio. You should be able to invert the sticks there.
I'm having problems with my Titan dc5 I feel like it has no range and the transmission connection is sporadic. On the HUD the drone icon at the bottom left the bars start to drop off even 50 yards awayI checked all my connections and they're tight and good I even switch to the DJI mmcx connectors and just ran them out the side. Do you think entering in this command could have affected the connection somehow..
I don't think so, but you could check by switching back to regular sbus and see if your range improves.
@@5zero7RC how do you switch back to regular when I switch back in the goggles I don't get any response out of the controller. Am I doing something wrong. I'm pretty sure I have to go into betaflight and probably set it back but wouldn't that put me back at square one with the controller not working
You have to match the protocol the DJI radio is sending with the protocol betaflight is expecting. So in this case to switch back you would go into the betaflight CLI and enter ""set sbus_baud_fast = OFF", then save and restart. Then in the DJI goggles switch back to sbus. After that you should have control working again with the normal sbus.
@@5zero7RCokay I was able to switch it back to normal and I got it to respond but the connection still drops off at about three hundred meters away down to one red bar I tested my cinewhoop back-to-back and no bars lost in the same flight pattern
@@5zero7RC thank you for your help. I changed out the fpv air unit and that had no change either. So so far I've switchedthe antennas and put it back and then the sbus bod and then put it back and then switched out the fpv air unit and it still does not have a good connection it must be the FCU
If you had one quad on Sbus and one on fast ... do you have to go back and fourth in the goggles to connect or dies the goggles remember?
Good question. I only have one air unit so I can't test that. Maybe someone else has the answer? I wonder if that setting is saved in the air unit and switches depending on which one the radio is connected to. Hopefully that is how it works.
@@5zero7RC It's when you don't want to update an earlier version of Betaflight when the quad flys good now and the speed controller is on BLHELI that does not do rpm filtering..
I am running a T-Motor F4 HD FC with the T-Motor P60 32BIT 6S ESC and Caddx Vista HD DJI system. I have bound the caddx system to my dji goggles and my dji controller. When i run betaflight everything seems to be working but it doesnt recognize my receiver. I have done practically everything i googled with no luck. Whats weird is when i power off the receiver and turn it back on, before the receiver binds to the caddx system, betaflight responds. But once the led turns green, betaflight doesnt respond to the receiver. Any idea what the problem may be?
Do you get correct drone battery voltage in the goggles? I wonder if your radio is set to use fast sbus but betaflight is expecting regular sbus? If that is not it, then I would double check with the FC manual that the settings for the radio UART are all correct.
@Alex Ou Correct battery voltage is whatever voltage the battery is on your drone at the time. For example a fully charged 4s battery when the drone is powered on will be just under 16.8v.
Yes, if you have rx2 and tx2 connected to the air unit for OSD information ( not radio control) then you need to set UART2 to be MSP. That allows data to flow back to the air unit and gets your betaflight OSD and battery voltage to the DJI goggles. If you have a Flight Controller designed for the DJI system, hopefully they have all these details and more in their manual.
@Alex Ou Do you know what Flight controller and ESC you have? If not, what is the RTF you bought?
Unfortunately T-motor does not appear to have a nice manual to go with that FC. However this diagram does help: en.tmotor.com/uploadfile/2019/0903/20190903095855234.jpg
I see that uart 5 is indeed the one for radio control and uart 2 is for the MSP connection. Uart 4 would be used for esc data. The ESC uart won't have anything to do with your radio control or OSD information.
@Alex Ou You do not need MSP on uart 4. I think you would set uart4 as sensor input ESC.
hi! great video - i have an challenge with my dji controller not being able to connect to betaflight, everythign is updated and green but still no movement in betaflight :( - help!
PS: im running everything on a Holybro Kakute F7 HDV & Tekko32 F3 HDV 40A 4in1 ESC 30x30 Stack/Combo for DJI (with a DJI unit )
Sounds like you have the exact same stack as I do. Be sure you have the radio protocol matched. So in the goggles if you have sbus, use sbus in the FC. If you have fast sbus selected in the goggles, under device -> protocol, make sure you run the CLI command "set sbus_baud_fast = ON" and save it.
@@5zero7RC no thats not the problem :/ its something with the RXLOSS and i dont know how to fix it :/ (its my first build :) ) - PS i dont have yet the motor connected to the fc - maybe it could be because of that?
Since you are using the same components as me, maybe you can skim through this build video and find a clue that might help you figure out what might be different? ruclips.net/video/zWFeI_SN1Vk/видео.html
@@5zero7RC i did watched this video a couple of time! thanks :) the problem is with RXLOSS NOPREARM CLI MSP i just dont know how to fix it, if its fixable
I just did a quick test with mine, and that is exactly what you will see if you have the protocol mismatched. Go into your goggles, go to device, then protocol and switch it. If you have it at "normal" switch it to sbus baud fast. If you have it at sbus baud fast, switch it to normal. After that hopefully the RXLOSS status will disappear.
How do I get my voltage on kwad to read?? I just get 0.0v on kwad the googles show the voltage of battery powering goggles but I get no voltage on kwad through osd!!
That means the MSP connection between your air unit ( or vista ) and the flight controller is not working so the flight controller can't send data like voltage and OSD info to the air unit and then get passed on to your goggles. How you do that depends on your flight controller, but you need to have the grey and white wires from the air unit connected to a UART on your flight controller. Then in betaflight you need to set that UART to be MSP like I do in this video. Hope that helps!
What if I’m using the air unit for a fixed wing only and using my own transmitter.
Do I get 7ms latency on the video ?
No, the 7ms latency is for the radio control signal only and requires you to use the DJI radio.
@@5zero7RC thank you sir..... so if I’m using the air unit with crossfire control link will there be any lag in my flight characteristics? Forgive me , I just got the package yesterday and I’m trying to educate myself in a rapid fashion .....
@@endliberalism4305 The DJI video system typically has 25-30ms of lag. It will show you that in the bottom right corner of the goggles.
I have not used crossfire but I believe that has 15ms or so average latency. Both are well within the range needed to fly FPV accurately.
@@5zero7RC thank you sir. I just got my Tx, Rx, air unit all updated and bound, I did the power hack for the goggles and low latency in the CLI command, everything looks good and I’m surprised everything works because when I received my goods the boxes were partially crushed after the trip from banggood , I saved about $150 purchasing it from them but Whew- close call.
Hi. Were you able to configure telemetry?
I'm not sure I understand your question. The DJI radio does not do telemetry data like an OpenTX radio.
@@5zero7RC Sorry, my question is about telemetry of the flight controller. I could not find any documentation about how to setup this.
I tried all telemetry protocols and it didn't work
@@kerleston Since this FC is designed to work with the DJI system, the only "telemetry" data I use is what the DJI goggles can display. At this time that is only the battery voltage and if the FC is armed or not. My guess is that enabling the telemetry option on the FC does not do anything. But I'm not sure about that.
@@5zero7RC Ok, Thank you
In the goggles mine just says Fast SBUS not DJI HDL. Any ideas?
As of the December DJI firmware update DJI changed the display to show Fast SBUS to be consistent with Betaflight. Basically HDL and Fast SBUS are the same thing.
@@5zero7RC That makes so much since! I got fast sbus in my goggles but I don't see it in my config menu. (I switched back to sbus because I couldn't get any receiver response when they are different i guess). Im a newb BTW. Thanks for the quick reply (subbed)
So you just need to type that command into the CLI and switch the protocol in the Goggles? You don't need to change the settings to DJI HDL in the Receiver settings section of the Config page?
Correct. With the final release of Betaflight 4.1, you need the cli command to enable the DJI HDL or sbus fast protocol. In some of the early 4.1 release candidates HDL was in the drop down box, but that was removed. Hopefully it comes back in some future update to make this easier for beginners.
Thumbs up and a subscribe from me bro thanks for the info I could not get it to arm or anyting
I’m not seeing the 7ms in goggles?
That is correct. I believe the goggles will display the video latency. The HDL protocol is just the radio transmitter link and its latency is not displayed anywhere.
Than You much just need time to test,,
did not work for me
I place set sbus_baud_fast = ON”
But receive ###ERROR: INVALID NAME###
Any idea?
Are you positive you have betaflight version 4.1 on your flight controller?
@@5zero7RC yes BTF 4.1.0
@@h975 As far as I know that error means the variable you are trying to set does not exist. So there must be a typo, or you included the " or something like that.
5zero7 RC
Same issue.
@@MindRiderFPV What version of the Betaflight configurator are you using?
iam about to be the one to thro this junk out I've try just about everything and looked at this video and thought it was what I needed to getting my sticks moving......but nothing I follow all the steps and nothing is happening green light on the radio all software on all three devices are updated and is a nice drone iam dying to fly from flywoo.....it's been a most frustrating experience......all devices communication seems to be OK green light everywhere picture on goggles but sticks not moving for nothing.......anyone out there please help save me from throwing this out to the trash
The important thing to remember is that the radio and betaflight have to be set the same, or they won't talk. The simple test is to change the protocol option in the goggles and see if that fixes the issue. If not, you likely have an issue with the connection between the flight controller and the DJI system. Either the wires are connected backwards, or you don't have the right UART set as the one where your radio is connected.
Would you happen to know if i can use crossfire as my receiver?
The HDL or sbus_baud_fast protocol is only for the DJI FPV radio right now. Crossfire uses its own fast protocol. If you have a crossfire compatible radio then you need a crossfire receiver in your drone. In that case the DJI FPV system is just like any other video transmitter. Hope that helps.