Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Crossfire input not showing in Betaflight
#1
Hi guys,
first post on this wonderful board! I got a Betafpv 95x v3 with a TBS Crossfire Nano module. I had to replace my FC after a crash and now my crossfire nano binds with a solid green light, but no inputs that are recognized in Betaflight. I sodered the battery connectors the wrong way round and connected it for like 0.3 seconds since I was paranoid about smoke. It seems to work fine in every way though. I also got a new crossfire nano module since I thought it might have been damaged by the wrong battery connection. I flashed the same firmware with the same target as on my previous FC where this exact setup worked. The Crossfire Nano gives me a solid green light (bound according to the manual), but no inputs in Betaflight register.  I also have the exact same model on my Tango II remote which runs firmware 6.10 (which previously worked). Can you give me any advice what might be wrong?

PS: a dump all should be attached. Smile
Reply
Login to remove this ad | Register Here
#2
There is no dump attached to your post. Can you please try attaching that again and also post a "diff all" as well.
Reply
#3
(21-Jan-2022, 10:10 PM)SnowLeopardFPV Wrote: There is no dump attached to your post. Can you please try attaching that again and also post a "diff all" as well.

Sorry, now it should be attached. I noticed that the target for the flight controller used to be BetaFPV405 (not OMNIBUSF4SD, as many internet posts suggest) and that used to work. So I reflashed the firmware and set everything else as described, but the problem persists.


Attached Files
.txt   troubleshooting_BTFL_cli_95x_v3_20220121_190555.txt (Size: 36.08 KB / Downloads: 60)
Reply
#4
What UART do you have the Crossfire Nano RX wired to?

Some good clear photos of the wiring and connections between the receiver and the FC would also be useful so we can double-check that your wiring all looks to be correct and in order.

EDIT: Your attached CLI dump also still shows the OMNIBUSF4SD Betaflight target. If you have now re-flashed the FC to the correct BETAFPVF405 Betaflight target, can you please attach a new CLI dump for that so we know we are looking at up-to-date settings.
Reply
#5
(22-Jan-2022, 08:11 PM)SnowLeopardFPV Wrote: What UART do you have the Crossfire Nano RX wired to?

Some good clear photos of the wiring and connections between the receiver and the FC would also be useful so we can double-check that your wiring all looks to be correct and in order.

EDIT: Your attached CLI dump also still shows the OMNIBUSF4SD Betaflight target. If you have now re-flashed the FC to the correct BETAFPVF405 Betaflight target, can you please attach a new CLI dump for that so we know we are looking at up-to-date settings.

Problem now solved, see Edit 2.

Hi again and thanks for your patience!
On my FC I use UART3, which is a plug. This used to work and I did not change the wiring from the original one, except that I soldered a cable for the SMO4k to another UART (1), see here:    


What I labeled as UART1 in the picture is R1/T1 on the FC, but I don't see those in Betaflights ports tab. Not sure what that should tell me. Lastly, the actual, new CLI dump is attached.
.txt   troubleshooting_BTFL_cli_95x_v3_20220124_100134.txt (Size: 35.66 KB / Downloads: 71)

I tried to find as much information about this as possible and think I should perhaps try another UART? Again, thank you so much for your help!

Edit: Here is the recommended wiring and Betaflight settings, which is exactly what I set up now.    

-----------------------------------------------------------------------
Edit 2: I solved it. It was both really easy and yet so well hidden for a beginner like me. On the screenshot of the setup manual it says "solder the pads as is shown" (at the DSM and SBUS pads). In the picture there is a black dot over two of those. When I looked at the new FC, there actually was some kind of small chip, connecting the other two. Luckily, I had my old FC lying around. That had no chip and the soldering done as in the picture. So I scraped off the small connecting chip and connected the pads as shown in the manual. Then it worked. I think it is not clearly communicated in the manual and the fact that I had to scratch off that small chip between two pads did not give me much confidence. Maybe another beginner sees this  and gets the problem solved. Thank you for taking my noob problem serious, SnowLeopardFPV! I feel kind of dumb about the solution, but yet it was kinda tricky.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Help Crossfire Nano RX bound to Tango II but no sticks/switches input in BF nor IRL illumn` 4 191 Yesterday, 10:23 PM
Last Post: illumn`
  Announcement TBS Crossfire / Tracer 6.36 Firmware Released SnowLeopardFPV 85 43,530 23-May-2024, 02:18 PM
Last Post: SnowLeopardFPV
  Help Nano RX not showing up in TBS agent majcyy 8 5,369 20-May-2024, 09:41 PM
Last Post: nolepic
  Thinking of ELRS over Crossfire Rob Axel 20 2,240 09-May-2024, 01:04 AM
Last Post: SeismicCWave
  Switching to FC expresslrs or crossfire transmitters zomer 1 135 01-May-2024, 07:54 PM
Last Post: matt0725


Login to remove this ad | Register Here