First Quad Build - Weird Issue, please help!

M

MattyB_Bstoke

New Member
Hello there, thanks for having a look at my thread, hopefully you can help here :)

I'm building my first drone, intentions were to use it for Cinematography ect but im at my wits end with getting it to actually fly, i've got a brand new PDB and FC (Matek PDB (not the AIO) and a Matek F405-STD (PPM input) running BTFL 4.1.5, Turnigy (FLYSKY) FS-IA6B (RX) and a FS-I6 (TX) if you watch the attched troubleshooting video it will show my issue but i will explain as best i can here!

I spent ages trying to get it to work, had one motor not working at all, sorted all that, couldn't get the receiver to show in the receiver tab in betaflight, fixed that with the correct receiver (did have a FS-IA6) so now it shows what i'm doing on the transmitter, obviously this means that the FC is receiving fine, i have the Arm set up, you can see that in the video, INCLUDING PREARM. but even when disconnected from USB no transmitter inputs are being processed, there's nothing from the motors to say its working, betaflight (as far as i know) says it should work, the motors tab allows me to spin the motors just not the damn transmitter.

Embedded media from this media site is no longer available

Any help is much appreciated, i am rather frustrated now as ive been stuck at this for the past week!

Thanks in advance,
Matt.
 
Dugdog47 said:
Your video is not working you might have to have a slightly higher post count to be able to post videos. Try a thread in the introduction section.
Click to expand...
Sorry mate, its just metacafe being slow, the video just shows the transmitter signal is being read by the flight controller along with no arming warnings, motors spin by USB control but no TX control. Hopefully Metacafe speeds it up a little as it is clearer on camera what i mean
 
It could be that the quad thinks it is angled if you have osd setup turn on "warnings" if it isn't on in there and should see a message about what is wrong (will say throttle or something else if throttle isn't 0, should give some sort of message though). If no OSD but has SD slot on FC or on board memory can activate black box logging and then download logs and load up to look for problems too. Would disable the check for angle mode though set it to 180 or whatever and make sure accelerometer calibration looks good on main config tab.

Sorry to hear about the frustration but it's not to uncommon around here especially with first build I can guarantee it gets easier the more you do it. Once your config is good go into CLI tab in the configutator and type "diff all" and hit enter then hit the save to file button in bottom right. That will save all the stuff you did to customize the config so far and can reapply to same type of FC or same FC if you replace it or upgrade firmware.

Also looks/sounds like you are super close to having it working just make sure quad moves as expected in the main configurator tab and motors and props are going right direction and you should be ready for take off soon.
 
Last edited:
I'm still new to this as well but I did notice something that I think helps. So I have the same transmitter you have and what i noticed is when you go into your receivers tab, the channels should be moving back and forth when you have your transmitter on. For example, the numbers shouldn't be sitting still like that they should switching between 1499, 1500, or 1501. Now your transmitter relays the information when you move the sticks but it's weird it's not fluctuating like how it should so it tells me the problem could be related to your receiver to transmitter connection. So you did use the receiver that came with the transmitter if I read correctly. Did you adjust the settings in the transmitter? Like, turn off PPM output or something? PPM output should be on for your transmitter and inside betaflight. I believe that's in the configuration tab where sbus and ibus would be.
If it isn't related to the transmitter, then the next thing i would think of is the arming mode. Go into modes and check and see that when you flip your arming switch on your transmitter, the arming range should turn yellow to signify that its armed. If not then it could be that.
 
My apologies if I missed it but do you have the battery connected and are the power LEDs on, on the FC?
Reason I ask is because you can make the motors spin all day long if plugged into USB but if your flight controller isn't powered than nothing will happen. Also how many beeps do you hear when you plug in battery?
 
Back
Top