Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 15-Oct-2023, 05:50 AM (This post was last modified: 15-Oct-2023, 05:51 AM by slffpv.) Hi everyone, I'm having a similar problem, on a bind & fly nazgul 5 with crossfire nano rx. I was flying it earlier today, with no issues. Came home and - in an attempt to run a custom OSD on my DJI Goggles v2 - backed up my betaflight settings, flashed the firmware (updating it by at least one version), and restored from those backed up settings, with a few CLI errors I figured I could manually go in and fix. I then attempted to do so, and I thought I got all the important ones, but perhaps not. I'm using a Tango 2 Pro, which I've tried un-binding and re-binding. I'm 100% sure I have Serial Rx toggled on the correct UART (UART2; UART1 is my caddx vista). But I get no inputs whatsoever in the Receiver tab. Here's my CLI dump: CLI Dump If anyone can take a second to look at it and tell me what I messed up, I would be extremely grateful. I've spent the past six hours googling, re-binding, re-flashing, and watching as many "set up from scratch" youtube videos as possible to compare my settings. Nothing has worked thus far. Thanks a ton. ![[-]](https://intofpv.com/images/collapse.png) • Posts: 12,099 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 When you compile the new firmware, did you make sure to include crsf protocol? Posts: 21,188 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (15-Oct-2023, 05:50 AM)slffpv Wrote: I'm having a similar problem, on a bind & fly nazgul 5 with crossfire nano rx. I was flying it earlier today, with no issues. Came home and - in an attempt to run a custom OSD on my DJI Goggles v2 - backed up my betaflight settings, flashed the firmware (updating it by at least one version), and restored from those backed up settings, with a few CLI errors I figured I could manually go in and fix. I then attempted to do so, and I thought I got all the important ones, but perhaps not. I'm using a Tango 2 Pro, which I've tried un-binding and re-binding. I'm 100% sure I have Serial Rx toggled on the correct UART (UART2; UART1 is my caddx vista). But I get no inputs whatsoever in the Receiver tab. Here's my CLI dump:
CLI Dump
If anyone can take a second to look at it and tell me what I messed up, I would be extremely grateful. I've spent the past six hours googling, re-binding, re-flashing, and watching as many "set up from scratch" youtube videos as possible to compare my settings. Nothing has worked thus far. I assume that you haven't messed with any of the receiver wiring? It would be worth having a quick look to see if the 4 wires going from the Crossfire Nano RX are still connected (soldered) at both ends and that none of them have come loose., If the wiring all checks out to be fine, please post the "diff all" output from your current firmware, and please post a copy of the original "diff" that you saved from the previous firmware version that was on the FC (the one that caused a load of errors when you tried to run it in). Please also run the "status" command and post the output from that. Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 (15-Oct-2023, 06:29 AM)voodoo614 Wrote: When you compile the new firmware, did you make sure to include crsf protocol? Yes. I initially flashed it with "CRSF, GHST, SBUS," and then tried again with just "CRSF," to no avail. • Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 (15-Oct-2023, 09:01 AM)SnowLeopardFPV Wrote: I assume that you haven't messed with any of the receiver wiring? It would be worth having a quick look to see if the 4 wires going from the Crossfire Nano RX are still connected (soldered) at both ends and that none of them have come loose.,
If the wiring all checks out to be fine, please post the "diff all" output from your current firmware, and please post a copy of the original "diff" that you saved from the previous firmware version that was on the FC (the one that caused a load of errors when you tried to run it in).
Please also run the "status" command and post the output from that. No, I didn't mess with any of the wiring, and I did take the frame apart to confirm that 1) the soldering is all still intact, and 2) the crossfire nano rx is indeed connected to UART2, as I remembered from before. Here are the uploads you requested: Prior Backup (Working) & Backup Error Screenshots (from trying to load that backup post-firmware update) Current Diff All (Not Working) Current Status (Not Working) Thank you SO MUCH for helping with this! • Posts: 21,188 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The "diff all" you posted for the newly flashed Betafight 4.4.2 firmware doesn't show "CRSF" as the Serial Receiver Provider which means that it will still be set to the default value of "SBUS", so go and check that in the Receiver tab and change it to "CRSF". • Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 (15-Oct-2023, 03:52 PM)SnowLeopardFPV Wrote: The "diff all" you posted for the newly flashed Betafight 4.4.2 firmware doesn't show "CRSF" as the Serial Receiver Provider which means that it will still be set to the default value of "SBUS", so go and check that in the Receiver tab and change it to "CRSF". I’ve set it to CRSF in the Receiver tab (now and confirmed several times last night), to no avail. It’s odd that’s not reflected in the diff all output, because it shows as CRSF in the betaflight interface. • Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 15-Oct-2023, 07:08 PM (This post was last modified: 15-Oct-2023, 07:25 PM by slffpv.) (15-Oct-2023, 03:52 PM)SnowLeopardFPV Wrote: The "diff all" you posted for the newly flashed Betafight 4.4.2 firmware doesn't show "CRSF" as the Serial Receiver Provider which means that it will still be set to the default value of "SBUS", so go and check that in the Receiver tab and change it to "CRSF". So, I've noticed a few things that might help diagnose: 1. When I click the Receiver tab in betaflight, the FC almost always disconnects and reconnects, after which I can access the Receiver tab normally. Is this common? 2. If I change the Serial Receiver Provider to SBUS in the Receiver tab, click Save and Reboot, and then run 'diff all' in the CLI, 'set serialrx_provider = SBUS" shows up under # master, but the same does not occur if I set the Serial Receiver Provider to CRSF in the Receiver tab ('set serialrx_provider = CRSF" is nowhere to be found). Flashing the firmware again doesn't help, whether I select 'CRSF' or 'CRSF, GHST, SBUS' under Radio Protocol. This is true whether I select 'CRSF' in the Receiver tab, or try to enable it in the CLI with: 'set serialrx_provider = CRSF" & "save." 3. Even though it doesn't show up in the 'diff all' output, if I type 'get serialrx_provider' in the CLI it returns: Code: # get serialrx_provider
serialrx_provider = CRSF
Allowed values: SPEK1024, SPEK2048, SBUS, SUMD, SUMH, XB-B, XB-B-RJ01, IBUS, JETIEXBUS, CRSF, SRXL, CUSTOM, FPORT, SRXL2, GHST
3.5. It also shows up in the 'dump' output: New Dump • Posts: 12,099 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 15-Oct-2023, 07:33 PM (This post was last modified: 15-Oct-2023, 07:34 PM by voodoo614.) "diff" only the difference between the original setting compared to any changes you made. The reason you don't see serial rx set to crsf is that it is in the original setting. Has nothing to do with your issue. Posts: 21,188 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 16-Oct-2023, 12:15 AM (This post was last modified: 16-Oct-2023, 08:00 PM by SnowLeopardFPV. Edit Reason: Typo corrections. ) (15-Oct-2023, 07:08 PM)slffpv Wrote: So, I've noticed a few things that might help diagnose:
1. When I click the Receiver tab in betaflight, the FC almost always disconnects and reconnects, after which I can access the Receiver tab normally. Is this common?
Yes, it is normal for Betaflight to disconnect if you click on the CLI tab and then click away from the CLI tab. Going to the CLI tab invokes MSP communication with the FC and to revert back out of that mode the FC needs to disconnect which then requires a manual reconnect.
2. If I change the Serial Receiver Provider to SBUS in the Receiver tab, click Save and Reboot, and then run 'diff all' in the CLI, 'set serialrx_provider = SBUS" shows up under # master, but the same does not occur if I set the Serial Receiver Provider to CRSF in the Receiver tab ('set serialrx_provider = CRSF" is nowhere to be found). Flashing the firmware again doesn't help, whether I select 'CRSF' or 'CRSF, GHST, SBUS' under Radio Protocol.
This is true whether I select 'CRSF' in the Receiver tab, or try to enable it in the CLI with: 'set serialrx_provider = CRSF" & "save."
3. Even though it doesn't show up in the 'diff all' output, if I type 'get serialrx_provider' in the CLI it returns:
Code: # get serialrx_provider
serialrx_provider = CRSF
Allowed values: SPEK1024, SPEK2048, SBUS, SUMD, SUMH, XB-B, XB-B-RJ01, IBUS, JETIEXBUS, CRSF, SRXL, CUSTOM, FPORT, SRXL2, GHST
3.5. It also shows up in the 'dump' output: New Dump
The default setting for serialrx_provider on the iFlight Succex-E F405 is SBUS (see the unified target file HERE), but I'm guessing if you select just CRSF for the Radio Protocol in the Build Options it probably changes the default to CRSF because it can't be SBUS if that hasn't been compiled into the firmware. See my answers in red above. I don't see anything wrong with your settings. Do you have the "Full chip erase" option selected when flashing the FC? If no then try again with that switched on. Failing the above, try flashing back to Betaflight 4.3.x or 4.2.x (neither of which required you to specify any specific build options) and see if it works fine under either of those. If it does then I suspect there is some kind of bug with the way the cloud build is compiling Betaflight 4.4.x for the IFLIGHT_SUCCEX_E_F4 Betaflight target. • Posts: 6 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Oct 2023 Reputation: 0 16-Oct-2023, 05:47 PM (This post was last modified: 16-Oct-2023, 05:48 PM by slffpv.) (16-Oct-2023, 12:15 AM)SnowLeopardFPV Wrote: Failing the above, try flashing back to Betaflight 4.3.x or 4.2.x (neither of which required you to specify any specific build options) and see if it works fine under either of those. If it does then I suspect there is some kind of bug with the way the cloud build is compiling Betaflight 4.4.x for the IFLIGHT_SUCCEX_E_F4 Betaflight target. Well, you nailed it here. I flashed back to 4.3.2, restored from my backup .txt file ignoring the errors, and it's back to working as intended. I won't be upgrading the firmware again any time soon! I guess I'll just have to live without a custom OSD in my DJI goggles. Thanks so much for your help. • Posts: 1 Threads: 0 Likes Received: 0 in 0 posts Likes Given: 0 Joined: Dec 2023 Reputation: 0 Hey guys, I'm having a similar issue. I went through the CLI dump but everything seems fine. Can you please check over my CLI dump to see if you can spot something? I have the Crossfire Nano RX set to UART5 and wired to RX5 and TX5 on a Flashhobby f405 https://drive.google.com/file/d/16QIxdJB...sp=sharing • Posts: 21,188 Threads: 582 Likes Received: 8,930 in 6,606 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (20-Dec-2023, 08:34 PM)trxzzy Wrote: Hey guys, I'm having a similar issue. I went through the CLI dump but everything seems fine. Can you please check over my CLI dump to see if you can spot something? I have the Crossfire Nano RX set to UART5 and wired to RX5 and TX5 on a Flashhobby f405
https://drive.google.com/file/d/16QIxdJB...sp=sharing Your Betaflight settings all look fine. Please post some good clear photos of the actual wiring and connections between your receiver and the flight controller. • |
