#New Drone will not show receiver channels in Betaflight even though receiver is bound to Radio

1 messages · Page 1 of 1 (latest)

strange juniper
#

10.90 Configurator
4.4.1 Firmware, flashed to Fport protocol, Dshot motor, Smartport telemetry
Iflight Blitz F7 Mini + BLITZ Mini E55 4-IN-1 ESC

Radio: Frsky Tandem x18S
Receiver: Frsky TD-MX wired for Fport

This is my third drone, first two work flawlessly with the same setup, TD-MX on my x18S radio using Fport, however I used Holybro 30x30 and 20x20 FC's with my first two.

I'm wondering if this is a issue with the specific FC from Iflight here? I bound the receiver on the drone to my radio fine, and then flashed the latest formware update to the TD-MX, so that obviously works great, the LED's flash correctly and mirror my functioning drones using the same systems. RSSI telemetry is transmitted correctly, etc
Motors and GPS work correctly in betalight, I tried reflashing to 4.4 and then back to 4.4.1 again with no change as I thought maybe the new version broke something.

O3 air unit also hooked up and works correctly. It seems the only thing I can't make work is the actual radio link for the channels. I have tried entering the iflight recommended cli settings

"set serialrx_provider=fport, set serialrx_inverted=on, set serialrx_halfduplex=on" as well as tried enabling and disabling them in combinations with no luck.

There are no shorts my multimeter and smoke stopper can detect and everything appears to be working correctly. I'm baffled at this point.

Everything is wired and configured to match this diagram
https://shop.iflight-rc.com/image/catalog/Test-Report/BF11373、BF12000_BLITZ Mini F7 FC Wiring Diagram_20230320.png

beta1.PNG 📎 diffall.txt
patent ridge
strange juniper
#

I tried it for kicks but that does not work and the ports will revert to default if i try it, so that cant be right with that setting, the documentation for Iflight shows this? And it states that fport needs to have serial enabled

beta3.PNG
strange juniper
#

I went through all the serial and UART tabs and toggled them all 1 at a time, nothing worked out of them

strange juniper
#

I have triple checked all the reciever wiring, it is wired exactly as stated in the iflight diagram, sport to R2, GND to GND, 5v to 5v

patent ridge
#

i screencapped that based on your document saying to solder to UART2 and the fact that your dump did not contain that particular serial as enabled.

#

when you cloud-build your hex, you did enable FPORT as the radio protocol correct?

strange juniper
#

yes i did put fport in as the protocol

#

I might have put a dump where i was fiddling accidently sorry about that

patent ridge
strange juniper
#

I am really confused as the wiring to me looks correct, I wired up my other drones just fine as well with the same basic system, maybe I should forget the fport on the iflight fc and try and wire it for normal sbus 4 wire?

patent ridge
#

i dont know, sorry. i exited the whole FrSky ecosystem and never looked back.

thorny sparrow
#

I had this happen and the UART in question was bad. Try moving to a new UART

patent ridge
#

i'm finding out a lot of FC's dont like UART1 for anything. usually because it may be shared with VCB(USB)

strange juniper
#

thanks i will try wiring to a diff uart tonight and see what happens

strange juniper
#

I soldered the reciever to the uart3 and got the same results =/

patent ridge
#

FrSky sucks, a ton of people fight setting it up. I think TweetFPV has some videos that could be helpful, but i dont recall if he has fport vids or not. sometone has to know the solution, FrSky and FPort were used by many in the past.