Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 09-Apr-2021, 03:14 AM (This post was last modified: 09-Apr-2021, 03:15 AM by jay0o0.) So the betafpv website says the firmware for this board is called Batefight-BETAFPV405-4.2.X (BETAFPV F405 2-4S AIO 12A V3 0 https://betafpv.com/products/f405-20a-ai...9934347398)
It's not called that, nor is it called just BETAFPV405. It may be BETAFPVF405 though. I'm stupid and didn't realize I could find out for sure in the CLI just by running "version". So I've already flashed both of these boards with BETAFPVF405. I'm having an issue with crossfire on these boards. I got the 2nd one thinking maybe I fried something on the 1st board but I'm having the same problem (with multiple receivers). Now I'm wondering if I installed the wrong firmware on both. Does anyone know if BETAFPVF405 is the correct firmware for this board? and if not what is? ![[-]](https://intofpv.com/images/collapse.png) • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 The firmware should be correct. If Crossfire is not working, the it is likely settings. Can you post your wiring and dump file. • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 (09-Apr-2021, 03:58 AM)voodoo614 Wrote: The firmware should be correct. If Crossfire is not working, the it is likely settings. Can you post your wiring and dump file. CLI dump and some pics attached. This board has a 4 pin connector on the board for the receiver. I'm using TBS Tracer Nano receivers and the pins are wired in the same order on the nanos as the connecor (1 = ground, 2 = 5V, 3 = CRSF TX, 4 = CRSF RX). The black stuff on the nano is just liquid electrical tape. I've actually got a 3rd nano RX unit I'm going to try today just in case, but I don't think that is the issue. I have bridged/soldered the DSM side of the DSM/SBUS bridge as per the diagrams. At some point I know I tried it on the other side just in case. I have a BN-220 GPS wired to TX1/RX1 (which is working correctly). Yes, receiver output is set to output CRSF TX on channel 1 and CRSF RX on channel 2. I have a Fat Shark Shark Byte TX5S.1 wired to the other pre-soldered port (TX4/RX4) which is also working properly. I have 2 other quads running BetaFlight and a fixed wing running iNav (all using nano tracer RXs and the same transmitter). I usually encounter some kind of challenge in setup of a board, but it's usually not crossfire. • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 The photo of the connector is misleading. Is it black, green, white then red. Or black, white, green then red? So you are using black for ground and white for 5V?
On a side note, the red wire you soldered on the FC has stray wires that might be causing a short.
I also recommend that you use silicone wire. You will not get those insulation burn. • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 (09-Apr-2021, 04:45 PM)voodoo614 Wrote: The photo of the connector is misleading. Is it black, green, white then red. Or black, white, green then red? So you are using black for ground and white for 5V?
On a side note, the red wire you soldered on the FC has stray wires that might be causing a short.
I also recommend that you use silicone wire. You will not get those insulation burn. Yeah that connector's wire colors are mismatched. Black is ground, white is 5V, CH1 is green, CH2 is red. I'll check the stray strand(s) on the TX1/RX1 pads. The other board I have has nothing soldered to it at the moment and it's having the same issue though. Thanks for the tip on wire types! Another thing I was thinking of trying is changing the output RX's output to SBUS... • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 I don't see anything wrong. Maybe someone saw something I didn't. • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 (09-Apr-2021, 05:27 PM)voodoo614 Wrote: I don't see anything wrong. Maybe someone saw something I didn't. I really appreciate your time in looking at this. Just knowing I have the right firmware and nothing in the config looks wrong helps a lot. I'll do some more testing and post my solution for others if I can figure this out. BTW, I know there are some debug features but I didn't see anything that would allow me to monitor serial traffic on the ports. Is there any way to do that? Or anything in the logging functionality that might help me see what is (or is not) going on? I'm a programmer (with quite a bit of experience with arduino boards) but I haven't really looked into if I can connect via ADB (or other tools) to these boards and get any additional data. • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 (09-Apr-2021, 06:48 PM)jay0o0 Wrote: I really appreciate your time in looking at this. Just knowing I have the right firmware and nothing in the config looks wrong helps a lot.
I'll do some more testing and post my solution for others if I can figure this out.
BTW, I know there are some debug features but I didn't see anything that would allow me to monitor serial traffic on the ports. Is there any way to do that? Or anything in the logging functionality that might help me see what is (or is not) going on? I'm a programmer (with quite a bit of experience with arduino boards) but I haven't really looked into if I can connect via ADB (or other tools) to these boards and get any additional data. Just following up in case it helps anyone else... I tried yet another crossfire on that UART3 port and I got nothing. I (re)tried switching the solder jumper to the other side and outputting an SBUS signal and an non-inverted SBUS signal and still nothing (tried on both sides of the jumper actually). Tried DSMX (both sides of the jumper as well). The crossfire works fine on UART1 though. I decided I really don't need a GPS on this micro quad so I'm just moving to UART1 and calling it a day. I did try to get the GPS working on UART3 but that didn't work any better on that port than the crossfire. It's not impossible I somehow fried the same chip or pad or idk what on both of these devices (or I got 2 from the same batch with a defect? grasping at straws obviously), but I'm still suspect of this firmware either not being quite the right one or having some kind of an issue (I did try one version back but that didn't help) because I have the same problem on two boards. In any case I was only putting a GPS on this quad cause I had one lying around and I like being able to see my speed but it's not even that useful or accurate anyway so I give up :  Thank you for your help and I hope this somehow helps someone else if they run into an issue on UART3 with this board • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 Good find. But I am very curious why UART 3 is not working. I wonder if it is just poor connection. Have you checked continuity from the receiver to the back of the connector of the FC port? • Posts: 8 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2021 Reputation: 0 (09-Apr-2021, 11:51 PM)voodoo614 Wrote: Good find. But I am very curious why UART 3 is not working. I wonder if it is just poor connection. Have you checked continuity from the receiver to the back of the connector of the FC port? You mean from the receiver TX pin on the nano to the pin on the FC? I didn't test that, but I used more than one FC, more than one cable and more than one nano so it seems unlikely that's the case. I'll check it when I get a chance though. Ideally I'd like to test the continuity from that TX pin on the receiver to the actual pin on the F405 chip that it's mapped to. I couldn't find a detailed blueprint for that board to figure out which pin is B10. I suppose I can just look up the chip and try to figure it out. Do you know what that solder jumper is actually doing? My guess is that it routes that pin through an inverter (or not) based on which way it is jumped. Just trying to confirm my assumptions. • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 Yes, the Jumper just reroute the pin through an inverter.
As for continuity, I check the back of the port from the receiver to the back of the port on the FC. • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 • Posts: 2 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Jan 2022 Reputation: 0 Hello guys, I just bumped into the same problem with my new betafpv f405 20a v3. The tracer rx is connected to tx and led is green but no connection to betaflight. I am going to try uart1 and hope it works. But I am also curios what is the problem. • |
