Please Help!!! First Tyro 119 Build no RX signal

jiggsy

New Member
Hi, i’ve tried posting this to reddit with no luck so far and i’m starting to run out of hope and ideas with how to fix this, so i’ve created an account here and hopeuflly you guys can help.

Im building my first drone at the moment (tyro 119 DIY Kit) and i’m using a FS-a8S RX wired to IBus and a fsi6x TX.
As far as i’m aware the RX seems to be bound to the TX based on the LED behaviour however the FC does three quick flashes followed by a continuous blink which i’m guessing means no RX signal. i’m genuinely at a loss now and i really want to get this quad air worthy for the weekend. PLEASE HELP GUYS XXX
 
You'll need to grab betaflight configurator to see what's going on with receiver input and to check out the modes you can change into with switches from your tx etc.

 
You'll need to grab betaflight configurator to see what's going on with receiver input and to check out the modes you can change into with switches from your tx etc.

I have beta flight.... The TX does not move any channel or work when in the receiver tab. Please help i’m at a loss
 
If no motion in receiver tab a couple possible issues:

1. Binding didn't work, try to use the bind button in the receiver tab (should be near the bottom) to try to get the receiver into binding mode and try to tell tx to bind again.

2. You may have not yet configured the receiver in the ports tab in betaflight you need to check which pad on fc the rx signal wire is hooked to (should be labelled like RX1 or rx2 on the FC pad). In the ports tab need to hit the serial rx toggle for the "UART" that corresponds to the RX number on the FC (RX1=uart1)

3. In the configuration tab need to make sure you have the correct protocol selected for the receiver (can guess and check if it isn't obvious which to pick no harm being wrong here)

Once have 2 and 3 above should check receiver tab again to see if getting any movement. If mapping looks wrong change the taer to aetr (usually is one of these two channel mappings)

In betaflight always save after changes in any tab you want persisted and made effective.
 
If no motion in receiver tab a couple possible issues:

1. Binding didn't work, try to use the bind button in the receiver tab (should be near the bottom) to try to get the receiver into binding mode and try to tell tx to bind again.

2. You may have not yet configured the receiver in the ports tab in betaflight you need to check which pad on fc the rx signal wire is hooked to (should be labelled like RX1 or rx2 on the FC pad). In the ports tab need to hit the serial rx toggle for the "UART" that corresponds to the RX number on the FC (RX1=uart1)

3. In the configuration tab need to make sure you have the correct protocol selected for the receiver (can guess and check if it isn't obvious which to pick no harm being wrong here)

Once have 2 and 3 above should check receiver tab again to see if getting any movement. If mapping looks wrong change the taer to aetr (usually is one of these two channel mappings)

In betaflight always save after changes in any tab you want persisted and made effective.
I’ve tried rebounding and selecting the correct UART slots, as well as trying a different RX slot on the FC to no avail. I’m starting to run out of steam and ideas i’m not sure what else can even be possibly wrong?
 
Did you check 3 the configuration tab receiver protocol drop down as well?

Only other thing I can think of related to receivers is inversion where the highs and lows are swapped when sending a digital signal, but I've not really had to deal with that myself, maybe @Dugdog47 or someone else on forum here has worked with that specific receiver and some BF FC and could tell ya more specifically. Some boards can only "read" certain protocols on specific rx inputs for reasons (timers/clock related details on mcu). But I am new to the FS receivers have one here and works well from what I can tell but on a plane I'm still learning to fly (I'm much more capable on a quad).
 
I’ve tried rebounding and selecting the correct UART slots, as well as trying a different RX slot on the FC to no avail. I’m starting to run out of steam and ideas i’m not sure what else can even be possibly wrong?
Also try not to get too frustrated receivers are always a pain it's partially why I've stuck with spektrum ones (do what you know works and happens to be what I started with because originally bought dx6i a couple years before all the openTX options rolled out)
 
Also also if you can link the manual to the receiver it helps tons with debugging that and FC manual if possible or link to store purchase/banggood link or whatever.

Also also also pic worth 1000 words show us wiring you'll need to resize to upload here still I think.
 
Did you check 3 the configuration tab receiver protocol drop down as well?

Only other thing I can think of related to receivers is inversion where the highs and lows are swapped when sending a digital signal, but I've not really had to deal with that myself, maybe @Dugdog47 or someone else on forum here has worked with that specific receiver and some BF FC and could tell ya more specifically. Some boards can only "read" certain protocols on specific rx inputs for reasons (timers/clock related details on mcu). But I am new to the FS receivers have one here and works well from what I can tell but on a plane I'm still learning to fly (I'm much more capable on a quad).
i tried switching everything to sbus and it seems to work. now the only problem is my motors aren’t in the correct order according to QUADX but they all spin the right direction just not the right motor corresponds
 
If your only problem is the motors are out of order you can use betaflight to re-source your motors. This page tells all:

 
i tried switching everything to sbus and it seems to work. now the only problem is my motors aren’t in the correct order according to QUADX but they all spin the right direction just not the right motor corresponds
If your only problem is the motors are out of order you can use betaflight to re-source your motors. This page tells all:

Were you able to get it working?
 
Back
Top