Furious 215 Arming & OSD Issue

Hey Walkera-Fans,

so i got myself a F215 and been flying it for straight a month now, nearly every day. I really like it because im new in FPV and its the best RTF copter.

The standard Props are kinda messed up right now. They brake really fast, so i replaced them with DAL T5046C Props and Gemfan 5055. Both of them are excellent. You only have to screw them onto the motors, because the motor threads are a little bigger than normal. But everythings working fine. I also upgraded the camera to a Runcam Eagle 2. Its just unplugging the old one and plug in the new one. You can even put in a cable for audio, so you are able to hear prop noise.

But there is my first question:
The Eagle has a second port for osd configuration. I can choose between NTSC 60 Hz, theres no OSD, and i can choose PAL 50 Hz, OSD is working. Everything good so far. The Point is, i switched to Betaflight 3.3.0, OSD is still working perfect instead of the Warnings like Armed/Disarmed and Low Voltage. Why do only the warnings not appear? I added the feature OSD in BF Configuration Tab, I tried to configure the OSD, but it is still the standard OSD without the warnings. The only difference is the camera, but the OSD is not paced in the camera, so why are the warnings missing?! Anybody got a solution?

Second Question: After flashing BF 3.3.0, my Gyro doesnt let me arm for 10-15 secs. After this period of time, the beeper beeps and i can arm and fly. Is it caused through DSHOT600? I already compared CF and BF CLI Dumps, but i cannot find a solution. At Github, someone said its caused through a HardwareFilter gyro_lpf and too high Gyro and Loop Cycles. I turned everything down to 2,67 but it still takes 10-15 secs till i can arm.

I would be so damn happy if someone can help me with those topics.

Greetings from Germany!

 

Hi there,

is there any option how to config the OSD on F215? The configuration tab in BF (last actual vs.) dose not affect the default Walkera OSD on the board. Is there any chance to configure it?
And the next: If I cannot config it in BF, could I do it thru the cable and connection port? There is nothing wrote about that by Walker except "tuning the OSD", but what it means? Why I can't modify the OSD by BF or CF in fact that I can modify SP3 board?! I do not understand Walkera. Or am I wrong in some option?

Thanks to anybody who has any experience.
Andrew

 

Thank You for explanation. Thats a Walkera problem. As the time goes by and you want to upgrade or take advantage of this entertainment, the Walkera will stop you. No support, no updates, no compatibility. It's shame. 90% of this forum deals with issues like this one. So if there is anybody new, and starts with this hobby be careful. If you want to be trapped to Walkera non open equipment, look for something else. The best way is build the quad from compatible parts, Frsky receiver etc. After you get better and you begin to understand it more, you will have open options. Something like Mac versus Microsoft, but Mac is pretty good, Walkera not so far...

 

I agree, but... the presentation by Walkera is not reliable. Are drones like F210, 215, Runner, Rodeo racing drones? No, they not! Is the FC really F3 protocol? No it isn't. Can be fully configured in CF or BF as the shoes the presentation? No, it is not fully opened a compatible with the software. I am not saying, that those quads are bad, but they only want reach the category which they want to achieve and the Walkera is deceiving us. Eachine, Furibee etc. are also RTF or BNF, but they clear job. I wonder that Walkera is not willing to pay licence of the protocol or open her product for 3rd party. Walkera takes the FC F3 protocol and modifies it to its own and says "we have F3". Look on the official website. Racing "racing drones" and read... "unlimited possibilitie od upgradable". So nothing is like it seems and that is the hook. I am unhappy to solve some problems of incompatibility at a time when this segment progresses so fast. Then it ends with pleasure and fun, and you just have your hair rave. All the community think about it.

 

Have you ever fixed the OSD problem?
I've got the same problem after updating nu firmware tot the latest betaflight.

I hope to hear from you, or someone else who van help me.

Kind regards, Robin