thank ya! still very relevant! started this mini-quad journey in 2017 haha too cheap to buy or setup the fpv system (all LOS)-- now I want to go fpv explore the freedoms we have while we still have them! sub 250g gonna take a minute at the local FPV workout kalub! I am using different fpv components but the same CL racing board; wiring should work out the same. thanks again
I was wondering about how you powered the camera .... looks like you took the red and black from the camera and the red and black from the VTX and soldered them together then just solder them to the pos and neg pads on the VTX pads so all power to the VTX and camera was done on common pads for the VTX? Did I see that right?
to get 5v to the cam and vtx pads, do you have to desolder the 9v pad after soldering the 5v pad or is just soldering the 5v pad somehow override the 9v being bridged?
Hey nice board I’m getting one soon! One thing what the version on it for betaflight? Is it the new version of firmware or will I need to flash to the newest beteflight?
3dkinson - I think your first question is how do you get audio sound when you're running smart audio? To answer your second question you don't need a uart for camera control to work, just solder it up the way I explained and when the multirotor is powered on but not armed, move the throttle to it's center stick position and then all the way to the right to access the fpv cameras menu.
Tristin Gilbert - Thanks for watching and commenting, and while I don't yet have experience with the Predator camera first hand to know the specific cli commands, I have one coming for testing and the information on how to get it working is in the Betaflight wiki link below, just scroll down the page until you see the bold Foxeer Predator setup guide: github.com/betaflight/betaflight/wiki/FPV-Camera-Control-(Joystick-Emulation)
SteelRainFPV thanks. I looked through the Github page and read all about it. Did you have to do any CLI commands with the RunCam though? I have 5 CL Racing F4S builds and all have RunCam’s but I never used cam control just because they are for racing.
Tristin Gilbert - It works on both my RunCam Eagle, Eagle 2 Pro, and Swift 2 without any further cli commands or hardware hacks, but I've read of people having issues getting it working on certain makes and brands of fpv camera's, like the RunCam micro swifts, sparrows, and some of the Foxeer camera's, along with different firmware versions of Betaflight that require the extra hardware resistor additions, Betaflight firmware updates, and additional cli commands.
thanks, ended up just soldering the controller connector back on. It will be a nice feature once all cameras and BF firmware updates will work with cam control.
Tristin Gilbert - Yeah it's not a perfectly refined feature yet since it's so new in Betaflight, sort of like 32khz gyro sampling and 32bit esc telemetry, they both are not fully supported without some issue's. Personally I just leave the osd dongle extension attached to my racing quads with micro cams, it's less of a headache and just about as fast to change fpv camera settings.
I use this FC and didn't even realize you could do this! I need to pop my quad back open and hook it up. I was always having to try and fish the dongle connector in and get to the back of my FPV cam. Huge pain! Are there any pre-requisites for the OSD to pop up besides throttle to center and yawing right? Seems like if that is the only thing to active it, it has the possibility of getting activated accidentally while flying. Now I don't generally yaw 100% to the right...almost ever, but still, what is stopping it from being activated in midair?
Thank you for your response! I got it all hooked up and good to go. Works like a charm. I ended up running into a snag that drove me nuts for about 15-20 minutes. "Throttle to mid point, and then yaw to the right" is actually based on the the channel values, and not their absolute position like you would think. In beta flight terms, to activate the OSD you need throttle at 1500 and yaw at 2000. (i.e. mid throttle and full right yaw). The issue happens though if you have different rates settings on your transmitter. (low - racing, high - stunts) I had it on my "low" setting which is 80% of normal, which only let my yaw get up to about 1800-1850, so it wouldn't trigger the OSD to activate. Drove me nuts! Finally figured it out, lol.
TomSpice - I'm glad that you got it working correctly, and if you use a camera that has the built in osd feature, you can access the menu to change that as well with a different stick command. Now depending on the Betaflight firmware version you have on the board, it's throttle set at it's mid point and pitch up for 5 seconds, or it's throttle set to it's lowest position and pitch up for 5 seconds.
I have BF 3.2 and am using a RunCam Swift Mini. The midpoint and yaw right worked, I just had to swap back to 100% rates and it worked immediately. I had seen all of the other comments around different stick positions to get it to activate and had tried all of them before I realized it was my rates that caused the issue!
TomSpice - Yeah that stick command that you're mentioning is to enter the camera settings menu, the other one I'm talking about is to access and change the cameras built in osd feature, the one that shows battery voltage, pilot name and on time.
Hi, newbie here and this is a nice video... I just have one question for example I have a frame kit with a PDB included and I want to use that not the PDB in this flight controller “CL Racing F4s” how do I setup the power connection? Thank you
Jarold Villanueva - The real question is why would you when this board has it all in one neat and tidy package? If you're still insistent on using a separate pdb, then you would just solder the main discharge and esc leads to the pdb, then solder the esc signal wires to this board, and run a positive and negative jumper wire from the pdb's main positive and negative pads to this boards main positive and negative pads.
SteelRainFPV - Thank you very much for the fast reply and actually that was really my first choice but when I saw this frame kit “ hobbyking.com/en_us/tyrant-s-215-framekit.html” it looks like very neat.... :-) And here is what I’m planning to get and build the quad VTX= Matek vtx-hv / Receiver= FrSky R-XSR / Motor= Emax 2205s 2400kv / ESC= Spedix ES30 HV / Camera= Foxeer Monster V2........... Will it match for the CL Racing F4S flight controller? Thank you in advance....
SteelRainFPV - Glad to hear that and I’ll try to work with it as soon as possible..... Again thank’s for the reply... love your videos and hope to see more... :-)
Thanks! I have a Turnigy Evolution on SBUS. How do FRSKY transmitters communicate withthe board to control the OSD . Is it through the telemetry. I don’t think that is possible with the Evolution. I’m a newbie so please be gentle.
Adriano Pangelinan - It's not a specific feature to any radio protocols, it's a built in feature of the Betaflight 3.2 firmware that eliminates the need for the dongle that plugs into the rear of your fpv camera to change it's settings, telemetry is a separate feature that has nothing to do with the camera control feature. So in short if you follow my setup video, the camera control feature will work with any radio protocol.
HYEonDEATHROW - That is the reason why I power my fpv camera's from the regulated and filtered 5v output of my vtx's, less video noise. If that still doesn't work try adding in a low esr 25volt 470uF-1000uF capacitor to the main power lead pads.
im using the AKK X2P and the Eagle 2 and have been getting diagonal static lines only when i arm the quad. i saw that you power the camera through the vtx and am hoping that'll solve my diagonal static line problems. also sometimes when im above 50% throttle, the osd just goes NUTS. im wondering if you thinkthat's because of the power to the camera or if it's the power to the vtx that's messing everything up? im also using the same CL Racing f4s chip
iamspanky FPV - I do believe that's why you're getting the video lines and osd breakups, which is why I have it setup the way I do in all of my builds, which is the vtx powered directly from the vbat pads, but only if the vtx can handle the voltage, and the fpv camera powered from the vtx's filtered and regulated 5 volt power source. I do have the AKK vtx powered from the dedicated 9 volt pad just for this specific video, and I'll leave it that way just to try it out in my next build, but if I have any issues then I'll switch it back to vbat power like I have always done.
So i have both a low esr capacitor and a lc filter on it right now. I'm going to try your method when my x2p arrives in the mail. I'm hoping the new one filters better and maybe the diagonal lines will disappear BUT if it doesn't, do you think I can still power my VTX off of the LC filter? I'm asking because I'd rather not resolder everything if i dont have to and the power to the vtx is already soldered to the lc filter. also does it matter that the ground for the vtx cam isn't connected to the ground on the cam directly? what if the ground for the vtx cam is already soldered to the lc filter's ground?
iamspanky FPV - The new vtx should work just fine powered off the lc filter, just make sure to power your fpv from the vtx's filtered and regulated power output and you should see an improvement. As for the fpv camera's ground wire being soldered to the lc filters ground, I'm not sure if that could be causing any of your current issues, but personally I'd use the ground wire from the vtx's provided fpv camera ground to eliminate that possibility.
Man I AM SO BUMMED!! So i got my new x2p VTX, powered the VTX off the LC FILTER and connected my cam to the filtered power coming from the VTX and..... Still diagonal lines.... BUT... at least now when i throttle more than 50%, my OSD doesn't get all wonky. the lines are still there, but i don't freak out in the air because i'm losing video. *sigh* i have no clue why i keep getting noise... I appreciate your video. I put a link to it in my rotorbuilds!!
iamspanky FPV - That is unfortunate that you're still getting video lines, have you tried a different lc filter to see if that's the problem? If it isn't then obviously you're getting some sort interference from the video in or out on the board, in which case I'd contact the vendor you bought the board from and let them know the situation and how you have things setup to avoid video noise, maybe a replacement is in order.
Frank Sarfino - For this board there's nothing more to setup in Betaflight, you just need to have firmware version 3.2 or later. Hook up your quad to Betaflight and go to the receiver tab, set your throttle stick to 1500 according to the program and push full right yaw and hold it. If your stick calibration is off a bit then it won't work right, meaning if you have your throttle stick at it's physical mid stick point and the Betaflight gui receiver tab isn't reading it at 1500 then you need to fix your throttle low, mid and high end points. If that still doesn't work, then you may need to add a resistor to the osd signal wire since some fpv camera's are configured a bit different. What fpv camera are you using?
This is with a swift on BF 3.2.2. I just spoke with Cheng the designer of the board. He told me this "Try to go to cli set camera_control_internal_resistor = 100." So I'm gonna give that a go when I get home tonight
Frank Sarfino - Yeah a full size swift should work without any problems, it's the mini and micros that are having the issues with the resistors, but I suppose if it's an older swift then it could be missing the needed hardware, hence Chengs suggestion. Make sure you try out what I suggested as well, it could just be a simple matter of your physical mid throttle stick position is not calibated or matching up to the 1500ms position needed to enter the camera control menu. Let me know what the results are if you figure it out.
Any idea on how you access the osd settings with CL racing F4S and the rotor riot runcam? To enter osd setting it requires holding up on the osd dongle. Can't figure out what stick command opens that menu. I can only get into the camera settings using yaw right and throttle mid center. Trying to turn the osd off as I am using betaflight osd instead.
dpg014 - According to the developers, it's throttle set to mid stick and pitch up for 5 seconds to enter the menu, if that doesn't work try throttle on lowest position and pitch up for 5 seconds.
Dario Viegas - If you mean can you configure a switch on your radio to access the menu, I don't think that it's possible from my understanding. The developers of the Betaflight code set it up in such a way that throttle has to be mid stick and yaw right to work, so I'm not sure why it's working on your elevator input unless your channel mapping on your radio is modified or different.
Evan Balbier - It's really just personal preference that I use the filtered 5 volt out from the vtx to power my fpv camera, I've had video issues and noise in the past when I've powered my camera using a flight controller's or pdb's power supply. If you connect smart audio to uart 4 instead of using the camera control feature, then you do the same steps for any normal uart, which is to go into the Betaflight ports tab, and select tbs smart audio in the drop down menu of the peripherals tab under uart 4.
I have this same flight controller and a runcam swift 2. I have it wired up and can not gain access to the cam settings. Any idea what could be causing it?
Pyro17059 - Without seeing your exact setup it's hard to tell, but my guess would be that your throttle stick isn't exactly calibrated so that your mid stick point reads the 1500ms position in Betaflight. Connect your quad to Betaflight and go into the receiver tab, move the throttle to mid stick to read 1500ms on the computer screen, then push the yaw all the way to the right to see if the camera's osd screen shows up, and make sure a flight battery is connected to provide power to the camera and vtx, and of course with props off for safety.
Pyro17059 i dont think it is supported yet. There is a wiki and a thread over on rcgroups. Some cameras require changes in the command line. I have the RR runcam swift 2 and it doesnt work either.
Unruly Rotors - The information to make hardware or software changes in the cli to get your specific fpv camera working with Betaflights camera control feature is detailed in the Betaflight wiki link below: github.com/betaflight/betaflight/wiki/FPV-Camera-Control-(Joystick-Emulation)
Pyro17059 SteelRainFPV yeah, had read all that. It didnt work a week ago, lol. But they have the stuff up on rcgroups now, link at the bottom of the wiki or right churrrrr www.rcgroups.com/forums/showthread.php?2961216-Betaflight-Camera-Control-Compatibility-Reports About to try it myself.
Iv just switched over to this AIO fc, from a dys f4pro. I used to get at the end of my flight (max current A) in my goggles, but now it just reads O Any ideas?
rumi geiger - In Betaflight 3.2 firmware you have to go into the osd tab inside the program and select what options you want it to show, I believe it's on the far right hand side. Also if you haven't yet, you have to go into the power tab of Betaflight and make sure that your current sensing function is turned on and configured properly.
Rumi G - Ok, make sure to go back and double check that everything is activated for current sensing and the osd readout inside of Betaflight in the configuration, power settings, and osd tab. My best guess without seeing your Betaflight gui or setup, is that It sounds like something isn't enabled or turned on causing the zero readout issue.
蔡宗憲 - This was more of a flight controller review than a vtx review, I have a separate review video on the AKK FX2 VTX on my channel if you're interested in it, but in short the vtx outputs an lc filtered 5 volts to the fpv camera, and the flight controller outputs a selectable 5 or 9 volts to power the vtx.
thank ya! still very relevant! started this mini-quad journey in 2017 haha too cheap to buy or setup the fpv system (all LOS)-- now I want to go fpv explore the freedoms we have while we still have them! sub 250g gonna take a minute at the local FPV workout kalub! I am using different fpv components but the same CL racing board; wiring should work out the same. thanks again
I was wondering about how you powered the camera .... looks like you took the red and black from the camera and the red and black from the VTX and soldered them together then just solder them to the pos and neg pads on the VTX pads so all power to the VTX and camera was done on common pads for the VTX? Did I see that right?
I power the vtx from the batteries main power and use the vtx's filtered power output to provide power to the camera, I get less video noise that way.
very nice and helpful video.... This is just what I'm thinking to build.... Thanks... :-)
Jarold Villanueva - This and the new Joshua Bardwell flight controllers are my go to boards now, you won't be disappointed.
Great job as expected :)
Thank you for this very fine description, on the spot, short and clear! Like that! Subbed :-)
Can hardly wait to get my build done with that FC =)
Wildpix FPV - Thank you for the support and kind words, stay tuned for more informative reviews and testing in future video's.
Thanks for making this very helpful video
to get 5v to the cam and vtx pads, do you have to desolder the 9v pad after soldering the 5v pad or is just soldering the 5v pad somehow override the 9v being bridged?
Thanks for thé vidéo do you think is possible connect a gps in this fc ???
Hey nice board I’m getting one soon! One thing what the version on it for betaflight? Is it the new version of firmware or will I need to flash to the newest beteflight?
Northern_ FPV - It should come with the new Betaflight 3.2 firmware since that's the version that works with the camera control feature.
SteelRainFPV thanks for the information!
cool vids. i see that uart 4 for smart audio for vtx but how to access from audio? , and what uart for camera control? thx
3dkinson - I think your first question is how do you get audio sound when you're running smart audio? To answer your second question you don't need a uart for camera control to work, just solder it up the way I explained and when the multirotor is powered on but not armed, move the throttle to it's center stick position and then all the way to the right to access the fpv cameras menu.
My question is I have a mic in my camera and I have smart audio . do I solder the audio wire to the same pad to hear sound??
Goooddddd :)
I order this fc.
I use crossfire on tx4 and rx4 how do i get smartaudio now
Did you have to do any CLI resourcing to get cam control to work? I have a predator micro and following your steps I get no cam control.
Tristin Gilbert - Thanks for watching and commenting, and while I don't yet have experience with the Predator camera first hand to know the specific cli commands, I have one coming for testing and the information on how to get it working is in the Betaflight wiki link below, just scroll down the page until you see the bold Foxeer Predator setup guide:
github.com/betaflight/betaflight/wiki/FPV-Camera-Control-(Joystick-Emulation)
SteelRainFPV thanks. I looked through the Github page and read all about it. Did you have to do any CLI commands with the RunCam though? I have 5 CL Racing F4S builds and all have RunCam’s but I never used cam control just because they are for racing.
Tristin Gilbert - It works on both my RunCam Eagle, Eagle 2 Pro, and Swift 2 without any further cli commands or hardware hacks, but I've read of people having issues getting it working on certain makes and brands of fpv camera's, like the RunCam micro swifts, sparrows, and some of the Foxeer camera's, along with different firmware versions of Betaflight that require the extra hardware resistor additions, Betaflight firmware updates, and additional cli commands.
thanks, ended up just soldering the controller connector back on. It will be a nice feature once all cameras and BF firmware updates will work with cam control.
Tristin Gilbert - Yeah it's not a perfectly refined feature yet since it's so new in Betaflight, sort of like 32khz gyro sampling and 32bit esc telemetry, they both are not fully supported without some issue's. Personally I just leave the osd dongle extension attached to my racing quads with micro cams, it's less of a headache and just about as fast to change fpv camera settings.
I use this FC and didn't even realize you could do this! I need to pop my quad back open and hook it up. I was always having to try and fish the dongle connector in and get to the back of my FPV cam. Huge pain!
Are there any pre-requisites for the OSD to pop up besides throttle to center and yawing right? Seems like if that is the only thing to active it, it has the possibility of getting activated accidentally while flying. Now I don't generally yaw 100% to the right...almost ever, but still, what is stopping it from being activated in midair?
TomSpice - The pop up osd display only occurs while in the disarmed state, once armed it's not an issue.
Thank you for your response! I got it all hooked up and good to go. Works like a charm. I ended up running into a snag that drove me nuts for about 15-20 minutes. "Throttle to mid point, and then yaw to the right" is actually based on the the channel values, and not their absolute position like you would think. In beta flight terms, to activate the OSD you need throttle at 1500 and yaw at 2000. (i.e. mid throttle and full right yaw). The issue happens though if you have different rates settings on your transmitter. (low - racing, high - stunts) I had it on my "low" setting which is 80% of normal, which only let my yaw get up to about 1800-1850, so it wouldn't trigger the OSD to activate. Drove me nuts! Finally figured it out, lol.
TomSpice - I'm glad that you got it working correctly, and if you use a camera that has the built in osd feature, you can access the menu to change that as well with a different stick command. Now depending on the Betaflight firmware version you have on the board, it's throttle set at it's mid point and pitch up for 5 seconds, or it's throttle set to it's lowest position and pitch up for 5 seconds.
I have BF 3.2 and am using a RunCam Swift Mini. The midpoint and yaw right worked, I just had to swap back to 100% rates and it worked immediately. I had seen all of the other comments around different stick positions to get it to activate and had tried all of them before I realized it was my rates that caused the issue!
TomSpice - Yeah that stick command that you're mentioning is to enter the camera settings menu, the other one I'm talking about is to access and change the cameras built in osd feature, the one that shows battery voltage, pilot name and on time.
Where you been??
Hi, newbie here and this is a nice video... I just have one question for example I have a frame kit with a PDB included and I want to use that not the PDB in this flight controller “CL Racing F4s” how do I setup the power connection? Thank you
Jarold Villanueva - The real question is why would you when this board has it all in one neat and tidy package? If you're still insistent on using a separate pdb, then you would just solder the main discharge and esc leads to the pdb, then solder the esc signal wires to this board, and run a positive and negative jumper wire from the pdb's main positive and negative pads to this boards main positive and negative pads.
SteelRainFPV - Thank you very much for the fast reply and actually that was really my first choice but when I saw this frame kit “ hobbyking.com/en_us/tyrant-s-215-framekit.html” it looks like very neat.... :-) And here is what I’m planning to get and build the quad VTX= Matek vtx-hv / Receiver= FrSky R-XSR / Motor= Emax 2205s 2400kv / ESC= Spedix ES30 HV / Camera= Foxeer Monster V2........... Will it match for the CL Racing F4S flight controller? Thank you in advance....
Jarold Villanueva - That's a pretty good list of components for a decent build, it will work just fine with the CL_RACINGF4S flight controller.
SteelRainFPV - Glad to hear that and I’ll try to work with it as soon as possible..... Again thank’s for the reply... love your videos and hope to see more... :-)
Thanks! I have a Turnigy Evolution on SBUS. How do FRSKY transmitters communicate withthe board to control the OSD . Is it through the telemetry. I don’t think that is possible with the Evolution. I’m a newbie so please be gentle.
Adriano Pangelinan - It's not a specific feature to any radio protocols, it's a built in feature of the Betaflight 3.2 firmware that eliminates the need for the dongle that plugs into the rear of your fpv camera to change it's settings, telemetry is a separate feature that has nothing to do with the camera control feature. So in short if you follow my setup video, the camera control feature will work with any radio protocol.
Adriano Pangelinan h
I get noise in my video and I have the camera hooked up to the board. Will try connecting it to my vtx. Thanks
HYEonDEATHROW - That is the reason why I power my fpv camera's from the regulated and filtered 5v output of my vtx's, less video noise. If that still doesn't work try adding in a low esr 25volt 470uF-1000uF capacitor to the main power lead pads.
SteelRainFPV
I’ll keep you posted. Might be a week or so before I get a chance
im using the AKK X2P and the Eagle 2 and have been getting diagonal static lines only when i arm the quad. i saw that you power the camera through the vtx and am hoping that'll solve my diagonal static line problems. also sometimes when im above 50% throttle, the osd just goes NUTS. im wondering if you thinkthat's because of the power to the camera or if it's the power to the vtx that's messing everything up? im also using the same CL Racing f4s chip
iamspanky FPV - I do believe that's why you're getting the video lines and osd breakups, which is why I have it setup the way I do in all of my builds, which is the vtx powered directly from the vbat pads, but only if the vtx can handle the voltage, and the fpv camera powered from the vtx's filtered and regulated 5 volt power source. I do have the AKK vtx powered from the dedicated 9 volt pad just for this specific video, and I'll leave it that way just to try it out in my next build, but if I have any issues then I'll switch it back to vbat power like I have always done.
So i have both a low esr capacitor and a lc filter on it right now. I'm going to try your method when my x2p arrives in the mail. I'm hoping the new one filters better and maybe the diagonal lines will disappear BUT if it doesn't, do you think I can still power my VTX off of the LC filter? I'm asking because I'd rather not resolder everything if i dont have to and the power to the vtx is already soldered to the lc filter. also does it matter that the ground for the vtx cam isn't connected to the ground on the cam directly? what if the ground for the vtx cam is already soldered to the lc filter's ground?
iamspanky FPV - The new vtx should work just fine powered off the lc filter, just make sure to power your fpv from the vtx's filtered and regulated power output and you should see an improvement. As for the fpv camera's ground wire being soldered to the lc filters ground, I'm not sure if that could be causing any of your current issues, but personally I'd use the ground wire from the vtx's provided fpv camera ground to eliminate that possibility.
Man I AM SO BUMMED!! So i got my new x2p VTX, powered the VTX off the LC FILTER and connected my cam to the filtered power coming from the VTX and..... Still diagonal lines.... BUT... at least now when i throttle more than 50%, my OSD doesn't get all wonky. the lines are still there, but i don't freak out in the air because i'm losing video. *sigh* i have no clue why i keep getting noise... I appreciate your video. I put a link to it in my rotorbuilds!!
iamspanky FPV - That is unfortunate that you're still getting video lines, have you tried a different lc filter to see if that's the problem? If it isn't then obviously you're getting some sort interference from the video in or out on the board, in which case I'd contact the vendor you bought the board from and let them know the situation and how you have things setup to avoid video noise, maybe a replacement is in order.
How can I control servo from cl racinf f4s
Is there some sort of setup for this to work in betaflight? I have everything wired correctly but haven't been able to access the camera's osd
Frank Sarfino - For this board there's nothing more to setup in Betaflight, you just need to have firmware version 3.2 or later. Hook up your quad to Betaflight and go to the receiver tab, set your throttle stick to 1500 according to the program and push full right yaw and hold it. If your stick calibration is off a bit then it won't work right, meaning if you have your throttle stick at it's physical mid stick point and the Betaflight gui receiver tab isn't reading it at 1500 then you need to fix your throttle low, mid and high end points. If that still doesn't work, then you may need to add a resistor to the osd signal wire since some fpv camera's are configured a bit different. What fpv camera are you using?
This is with a swift on BF 3.2.2. I just spoke with Cheng the designer of the board. He told me this "Try to go to cli set camera_control_internal_resistor = 100." So I'm gonna give that a go when I get home tonight
Frank Sarfino - Yeah a full size swift should work without any problems, it's the mini and micros that are having the issues with the resistors, but I suppose if it's an older swift then it could be missing the needed hardware, hence Chengs suggestion. Make sure you try out what I suggested as well, it could just be a simple matter of your physical mid throttle stick position is not calibated or matching up to the 1500ms position needed to enter the camera control menu. Let me know what the results are if you figure it out.
Any idea on how you access the osd settings with CL racing F4S and the rotor riot runcam? To enter osd setting it requires holding up on the osd dongle. Can't figure out what stick command opens that menu. I can only get into the camera settings using yaw right and throttle mid center. Trying to turn the osd off as I am using betaflight osd instead.
dpg014 - According to the developers, it's throttle set to mid stick and pitch up for 5 seconds to enter the menu, if that doesn't work try throttle on lowest position and pitch up for 5 seconds.
SteelRainFPV ok thanks I'll have to try that.
SteelRainFPV throttle at the lowest point and pitch up 5 times works. Thanks for the tip!
dpg014 - No problem at all, just be aware that stick command may change depending on what version of Betaflight firmware you're using.
I didnt connect my battery through the fc, will the camera still work?
Nils Nyberg - Yes it will
Is it possible to configure the button to the menu to show up? My menu only shows when i lift to full elevator, yaw right doesnt do anything
Dario Viegas - If you mean can you configure a switch on your radio to access the menu, I don't think that it's possible from my understanding. The developers of the Betaflight code set it up in such a way that throttle has to be mid stick and yaw right to work, so I'm not sure why it's working on your elevator input unless your channel mapping on your radio is modified or different.
How come you don’t have the vbat from the camera connected? Also, do I need to do anything special to use SmartAudio on UART 4.
Evan Balbier - It's really just personal preference that I use the filtered 5 volt out from the vtx to power my fpv camera, I've had video issues and noise in the past when I've powered my camera using a flight controller's or pdb's power supply. If you connect smart audio to uart 4 instead of using the camera control feature, then you do the same steps for any normal uart, which is to go into the Betaflight ports tab, and select tbs smart audio in the drop down menu of the peripherals tab under uart 4.
Thx. And you have the FrSky setup on uart1?
Evan Balbier - Currently I have this board in a long range 6" build, I have smart audio setup on tx1 and my TBS Crossfire setup on tx4 and rx4.
I have this same flight controller and a runcam swift 2. I have it wired up and can not gain access to the cam settings. Any idea what could be causing it?
Pyro17059 - Without seeing your exact setup it's hard to tell, but my guess would be that your throttle stick isn't exactly calibrated so that your mid stick point reads the 1500ms position in Betaflight. Connect your quad to Betaflight and go into the receiver tab, move the throttle to mid stick to read 1500ms on the computer screen, then push the yaw all the way to the right to see if the camera's osd screen shows up, and make sure a flight battery is connected to provide power to the camera and vtx, and of course with props off for safety.
Pyro17059 i dont think it is supported yet. There is a wiki and a thread over on rcgroups. Some cameras require changes in the command line.
I have the RR runcam swift 2 and it doesnt work either.
Unruly Rotors - The information to make hardware or software changes in the cli to get your specific fpv camera working with Betaflights camera control feature is detailed in the Betaflight wiki link below:
github.com/betaflight/betaflight/wiki/FPV-Camera-Control-(Joystick-Emulation)
Pyro17059 SteelRainFPV yeah, had read all that. It didnt work a week ago, lol. But they have the stuff up on rcgroups now, link at the bottom of the wiki or right churrrrr
www.rcgroups.com/forums/showthread.php?2961216-Betaflight-Camera-Control-Compatibility-Reports
About to try it myself.
Unruly Rotors - Cool, let me know if it does or doesn't work, and it may require the newest Betaflight firmware update to work properly as well.
Iv just switched over to this AIO fc, from a dys f4pro. I used to get at the end of my flight (max current A) in my goggles, but now it just reads O
Any ideas?
rumi geiger - In Betaflight 3.2 firmware you have to go into the osd tab inside the program and select what options you want it to show, I believe it's on the far right hand side. Also if you haven't yet, you have to go into the power tab of Betaflight and make sure that your current sensing function is turned on and configured properly.
Thanks, for the reply.
I have Onboard ADC in current meter sours. And in my goggles it shows up, but it just reads zero, after flight.
Rumi G - Ok, make sure to go back and double check that everything is activated for current sensing and the osd readout inside of Betaflight in the configuration, power settings, and osd tab. My best guess without seeing your Betaflight gui or setup, is that It sounds like something isn't enabled or turned on causing the zero readout issue.
Vtx output voltage is?
蔡宗憲 - This was more of a flight controller review than a vtx review, I have a separate review video on the AKK FX2 VTX on my channel if you're interested in it, but in short the vtx outputs an lc filtered 5 volts to the fpv camera, and the flight controller outputs a selectable 5 or 9 volts to power the vtx.
Anyone out thete tried racerstar 30amp lite ESC's with this board?